From: Diego Calleja <diegocg@gmail.com>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crazy Idea: Replacing /dev using sysfs over time
Date: Tue, 27 Sep 2005 01:55:03 +0200 [thread overview]
Message-ID: <20050927015503.702ca60e.diegocg@gmail.com> (raw)
In-Reply-To: <200509261928.20701.shawn.starr@rogers.com>
El Mon, 26 Sep 2005 19:28:18 -0400,
Shawn Starr <shawn.starr@rogers.com> escribió:
> /sys/class/block/
> `-- sda
> |-- sda1
> | - major
> | - minor
> | - raw
With this you're adding again all the device naming linux has got ridden of
by removing devfs (it rememebers me to solaris' devfs: They have a
sysfs-like filesystem, except that things in /dev are a symbolic link to a
device file in /devices)
> Do we really need /dev other than for historical/legacy purposes?
If your intention is just to boot kernels and not run userspace on them,
then sure, it's a good idea to get rid of /dev.
next prev parent reply other threads:[~2005-09-26 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 23:28 Crazy Idea: Replacing /dev using sysfs over time Shawn Starr
2005-09-26 23:55 ` Diego Calleja [this message]
2005-09-27 0:02 ` Shawn Starr
2005-09-27 10:25 ` Greg KH
2005-09-27 12:52 ` linux-os (Dick Johnson)
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=20050927015503.702ca60e.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.