From: Miquel van Smoorenburg <miquels@cistron.nl>
To: Alexander Viro <viro@math.psu.edu>
Cc: Kurt Garloff <garloff@suse.de>,
Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: TIOCGDEV ioctl
Date: Sat, 16 Dec 2000 12:40:11 +0100 [thread overview]
Message-ID: <20001216124011.A14129@cistron.nl> (raw)
In-Reply-To: <20001216114645.A8944@cistron.nl> <Pine.GSO.4.21.0012160550240.15518-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0012160550240.15518-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Sat, Dec 16, 2000 at 06:15:51AM -0500
According to Alexander Viro:
> OK, I can see the point of finding out where the console is redirected
> to. How about the following:
>
> /proc/sys/vc -> /dev/tty<n>
> /proc/sys/console -> where the hell did we redirect it or
> vc if there's no redirect right now
> Will that be OK with you?
Well, I'd prefer the ioctl, but I can see the general direction the
kernel is heading to: get rid of numeric ioctls and sysctl()s and
put all that info under /proc.
However /proc/sys only contains directories now, it would look
kindof ugly to put 2 symlinks in there directly. Oh well.
Mike.
--
RAND USR 16514
-
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:[~2000-12-16 12:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 0:55 TIOCGDEV ioctl Kurt Garloff
2000-12-16 1:11 ` Linus Torvalds
2000-12-16 1:54 ` Alexander Viro
2000-12-16 10:46 ` Miquel van Smoorenburg
2000-12-16 11:15 ` Alexander Viro
2000-12-16 11:40 ` Miquel van Smoorenburg [this message]
2000-12-16 11:57 ` Alexander Viro
2000-12-19 11:34 ` Kurt Garloff
2000-12-21 14:22 ` Dr. Werner Fink
2000-12-16 1:18 ` James Simmons
2000-12-16 10:54 ` Miquel van Smoorenburg
2000-12-18 17:07 ` James Simmons
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=20001216124011.A14129@cistron.nl \
--to=miquels@cistron.nl \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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).