From: Christoph Hellwig <hch@infradead.org>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
viro@parcelfarce.linux.theplanet.co.uk, Andi Kleen <ak@suse.de>,
Miquel van Smoorenburg <miquels@cistron.nl>
Subject: Re: [PATCH] fix tiocgdev 32/64bit emul
Date: Sun, 21 Mar 2004 20:26:55 +0000 [thread overview]
Message-ID: <20040321202655.A11330@infradead.org> (raw)
In-Reply-To: <405DF83C.2040703@gmx.net>; from c-d.hailfinger.kernel.2004@gmx.net on Sun, Mar 21, 2004 at 09:17:00PM +0100
On Sun, Mar 21, 2004 at 09:17:00PM +0100, Carl-Daniel Hailfinger wrote:
> > No, I'll leave that to Greg. If you want my 2 (Euro-) Cent I'd rather avoid
> > exposing a dev_t to userspace wherever possible.
>
> Understood. Especially since the recent upsizing of dev_t broke
> applications trying to be too clever about dev_t. However, look at this:
>
> # cat /sys/class/tty/console/dev
> 5:1
>
> Does this major:minor textfile export address your concerns?
No. I'd really love to avoid having any userspace (escept makedev/udev)
to use dev_t as anything but a cookie, i.e. trying to make sense from it.
Having a special raw, non-redirected console device as in Al's patch is
*much* cleaner.
prev parent reply other threads:[~2004-03-21 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 6:24 linguist
2004-03-21 16:45 ` [PATCH] fix tiocgdev 32/64bit emul Jeff Garzik
2004-03-21 16:57 ` Christoph Hellwig
2004-03-21 18:50 ` Carl-Daniel Hailfinger
2004-03-21 18:55 ` Christoph Hellwig
2004-03-21 19:57 ` Carl-Daniel Hailfinger
2004-03-21 20:02 ` Christoph Hellwig
2004-03-21 20:17 ` Carl-Daniel Hailfinger
2004-03-21 20:26 ` Christoph Hellwig [this message]
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=20040321202655.A11330@infradead.org \
--to=hch@infradead.org \
--cc=ak@suse.de \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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®