From: "H. Peter Anvin" <hpa@transmeta.com>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Minors remaining in Major 10 ??
Date: Sat, 20 Jan 2001 14:13:55 -0800 [thread overview]
Message-ID: <3A6A0DA3.FF1EB559@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101200039590.609-100000@master.linux-ide.org>
Andre Hedrick wrote:
>
> HPA,
>
> Thoughts on granting all block subsystems a general access misc-char minor
> to do special service access that can not be down to a given device if it
> is open. There are some things you can not do to a device if you are
> using its device-point to gain entry. Also do the grab a neighboor and
> force the migration to find the desired major/minor is painful.
>
Hmmm... this would be better done using a dedicated major (and then minor
= block major.) This is something we can do in 2.5 once we have the
larger dev_t; at this point, I'd be really hesitant to allocate
additional that aren't obligatory.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-20 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-20 8:45 Minors remaining in Major 10 ?? Andre Hedrick
2001-01-20 22:13 ` H. Peter Anvin [this message]
2001-01-20 23:06 ` Andre Hedrick
2001-01-20 23:12 ` H. Peter Anvin
2001-01-20 23:40 ` Andre Hedrick
2001-01-21 0:42 ` Jens Axboe
[not found] <3A6A28B2.83807A1@transmeta.com>
2001-01-21 5:36 ` Andre Hedrick
2001-01-21 5:40 ` H. Peter Anvin
2001-01-21 5:44 ` Andre Hedrick
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=3A6A0DA3.FF1EB559@transmeta.com \
--to=hpa@transmeta.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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