From: Dave Dillow <dave@thedillows.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Gene Heskett <gene.heskett@gmail.com>,
linux-kernel@vger.kernel.org, ray-gmail@madrabbit.org,
amanda-hackers@amanda.org, amanda-users@amanda.org
Subject: Re: plain 2.6.21-rc5 (1) vs amanda (0)
Date: Wed, 04 Apr 2007 17:55:28 -0400 [thread overview]
Message-ID: <1175723728.6274.2.camel@obelisk.thedillows.org> (raw)
In-Reply-To: <20070404132949.f6fbca9f.akpm@linux-foundation.org>
On Wed, 2007-04-04 at 13:29 -0700, Andrew Morton wrote:
> On Wed, 04 Apr 2007 14:17:13 -0400
> Dave Dillow <dave@thedillows.org> wrote:
> > The thing is, it's been broken for a long time -- this change just
> > highlighted it. This isn't the first time that device-mapper has moved
> > -- the introduction of mdp (before git, so haven't tracked down
> > timeframe) also moved it around. The dynamic major is not stable, so
> > should we be concerned if it moves for 2.6.21?
> >
> > I don't like the effect it has on the backups, but I don't think we
> > should hand out LOCAL/EXP majors to dynamic devices, either. There is a
> > module option to make the device-mapper and mdp majors stable, so
> > perhaps a compromise is possible? Revert for 2.6.21, and schedule the
> > patch for later addition, which gives distros time to use the DM major
> > option?
>
> hm, good points.
>
> Overall, the patch helps kernel developers and hurts the userbase. I tend
> to prefer to hurt kernel developers than our users ;)
>
> I don't think the protect-lanana-numbers thing is very important, really.
> If some kernel developer or someone who is maintaining an unofficial
> out-of-tree driver hits the problem, they are presumably able to handle
> it. Preferably by switching to a dynamically-assigned major.
Works for me; I don't really have a dog in the fight.
next prev parent reply other threads:[~2007-04-04 21:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 5:00 Gene Heskett
2007-04-01 6:51 ` Ingo Molnar
2007-04-01 14:44 ` Gene Heskett
2007-04-01 7:33 ` Ray Lee
2007-04-01 15:41 ` Gene Heskett
2007-04-02 4:20 ` Gene Heskett
2007-04-02 4:31 ` Dave Dillow
2007-04-04 4:34 ` Dave Dillow
2007-04-04 8:45 ` Ingo Molnar
2007-04-04 17:42 ` Andrew Morton
2007-04-04 18:17 ` Dave Dillow
2007-04-04 20:29 ` Andrew Morton
2007-04-04 21:55 ` Dave Dillow [this message]
2007-04-05 0:49 ` Gene Heskett
2007-04-09 15:33 ` Gene Heskett
2007-04-09 15:59 ` Dave Dillow
2007-04-09 16:12 ` Gene Heskett
2007-04-09 16:30 ` Gene Heskett
2007-04-09 16:00 ` Ingo Molnar
2007-04-09 17:05 ` Gene Heskett
2007-04-09 17:50 ` Ingo Molnar
2007-04-09 19:58 ` Gene Heskett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1175723728.6274.2.camel@obelisk.thedillows.org \
--to=dave@thedillows.org \
--cc=akpm@linux-foundation.org \
--cc=amanda-hackers@amanda.org \
--cc=amanda-users@amanda.org \
--cc=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ray-gmail@madrabbit.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®