From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [NFS] RE: [autofs] multiple servers per automount
Date: 14 Oct 2003 13:44:45 -0700 [thread overview]
Message-ID: <bmhn7t$odm$1@cesium.transmeta.com> (raw)
In-Reply-To: 3F8C1BB6.9010202@sun.com
Followup to: <3F8C1BB6.9010202@sun.com>
By author: Mike Waychison <Michael.Waychison@Sun.COM>
In newsgroup: linux.dev.kernel
>
> Here is the quick fix for this in RH 2.1AS kernels:
>
> http://www.kernelnewbies.org/kernels/rh21as/SOURCES/linux-2.4.9-moreunnamed.patch
>
> It makes unnamed block devices use majors 12, 14, 38, 39, as well as 0.
>
> I don't know if anyone is working out a better scheme for
> get_unnamed_dev in 2.6 yet. It does need to be done though. A simple
> patch for 2.6 would maybe see the unnamed_dev_in_use bitmap grow to
> PAGE_SIZE, automatically allowing for 32768 unnamed devices.
>
dev_t enlargement, which solves this without a bunch of auxilliary
majors, should be in 2.6.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
If you send me mail in HTML format I will assume it's spam.
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-10-14 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0310142131090.3044-100000@raven.themaw.net>
2003-10-14 15:52 ` [NFS] RE: [autofs] multiple servers per automount Mike Waychison
2003-10-14 20:44 ` H. Peter Anvin [this message]
2003-10-14 23:12 ` Mike Waychison
2003-10-15 10:28 ` Ingo Oeser
2003-10-15 16:16 ` Mike Waychison
2003-10-23 13:37 ` Ian Kent
2003-10-23 17:00 ` Mike Waychison
2003-10-23 17:09 ` Tim Hockin
2003-10-24 0:47 ` Ian Kent
2003-10-24 1:42 ` Tim Hockin
2003-10-15 7:22 ` Ian Kent
2003-10-15 14:31 Lever, Charles
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='bmhn7t$odm$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).