linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wiktor Wodecki <wodecki@gmx.de>
To: Balram Adlakha <b_adlakha@softhome.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 devfs question
Date: Sat, 26 Jul 2003 22:35:35 +0200	[thread overview]
Message-ID: <20030726203535.GD789@gmx.de> (raw)
In-Reply-To: <20030726104506.GA663@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]

On Sun, Jul 27, 2003 at 01:49:19AM +0530, Balram Adlakha wrote:
> On Sat, Jul 26, 2003 at 08:37:50PM +0200, Wiktor Wodecki wrote:
> > On Sat, Jul 26, 2003 at 11:22:14PM +0530, Balram Adlakha wrote:
> > > The old naming scheme is (quite) depricated. Firstly, devfs shows only those devices which are probed (have a driver), secondly the devices are sorted in an easy to understand directory heirarchy to reduce clutter.
> > > Theres a devfs daemon called devfsd which is actually (almost) a part of a working devfs system. Using devfsd, you can autoload modules even while using devfs, and it also creates symlinks to older device name if that is specified in the /etc/devfsd.conf file.
> > > It is your choice if you want to use devfs or not, linux is all about choice. If you don't like the new naming scheme, you can edit a few lines in the devfs source and change the scheme. Or you can have devfs mounted in another place (like /dev2) and create a script which creates symlinks from /dev2 to /dev with your own preferred names, and you can edit /etc/rc.d/rc.sysinit to run the script on bootup.
> > > Or you can continue using the old device inodes...Some people still prefer them.
> > 
> > I understand that and I greatly appreciate the new naming scheme.
> > However it would have been nice if I could have bootet just up and look
> > at it without changing my core system files (I regard /etc/fstab as
> > core). Nevermind, I might give it another shot on a testing system.
> > 
> You won't need to update /etc/fstab if you use devfsd and its configured to create old device names in /dev...

ah! This should be placed somewhere in a FAQ or so. As I've read through
the docs this isn't mentioned anywhere. This of course solves all my
concerns about devfs. Will try it again soon.
Thanks for enlightment :-)

-- 
Regards,

Wiktor Wodecki

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-07-26 20:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 18:53 Balram Adlakha
2003-07-26 10:45 ` Wiktor Wodecki
     [not found]   ` <20030726175214.GA2535@localhost.localdomain>
     [not found]     ` <20030726183750.GB789@gmx.de>
     [not found]       ` <20030726201919.GA5166@localhost.localdomain>
2003-07-26 20:35         ` Wiktor Wodecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-28  7:13 "Andrey Borzenkov" 
2003-07-28  7:22 ` Andrew Morton
2003-07-26 19:51 Andrey Borzenkov
2003-07-26 20:50 ` Andrew Morton
2003-07-26 22:30   ` Andrey Borzenkov
2003-07-27  8:58     ` Daniele Venzano
2003-07-25 11:08 Wiktor Wodecki
2003-07-25 11:18 ` Wiktor Wodecki
2003-07-26 11:12 ` Daniele Venzano
2003-07-26 18:25   ` Andrew Morton
2003-07-27 11:17     ` Alan Cox

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=20030726203535.GD789@gmx.de \
    --to=wodecki@gmx.de \
    --cc=b_adlakha@softhome.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.0-test1 devfs question' \
    /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

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).