public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	linux-hotplug-devel@lists.sourceforge.net
Subject: Re: udev - please help me to understand
Date: Sat, 3 Jan 2004 02:00:10 +0100	[thread overview]
Message-ID: <20040103010010.GA14823@werewolf.able.es> (raw)
In-Reply-To: <20040102202316.GD4992@kroah.com> (from greg@kroah.com on Fri, Jan 02, 2004 at 21:23:16 +0100)


On 01.02, Greg KH wrote:
> On Fri, Jan 02, 2004 at 09:48:36PM +1000, Steve Youngs wrote:
> > Hi Greg!
> > 
> > I've been looking at this "udev" thingy and I can't for the life of me
> > see why I'd need it.  There doesn't appear to be _any_ advantages of
> > using udev in my present situation.
> 
> Ok, great.  Then don't use it, I'm not forcing you to for 2.6 :)
> 
> > No, I don't use devfs.
> > 
> > I have zero hot-pluggable devices (that might change somewhere in the
> > distant future, but for now I don't have any).  And never in my wildest
> > dreams could I ever imagine running out of device numbers.
> > 
> > Reading through the documentation that I've found about udev, your
> > main points seem to be about:
> > 
> >         - udev vs devfs
> >         - running out of device major/minor numbers
> >         - not having to worry about major/minor numbers
> > 
> > For me, the first point is moot because I don't use devfs.  The second
> > point is just plain ridiculous, there is just _no_ way that it could
> > happen (remember that I'm talking about my own situation).  
> 
> If you never have any hotpluggable devices, nor any need to move disks
> around in your system, then you don't need udev.
> 

Don't think so. My first use for udev is a cluster (when bproc works on
2.6 ;)). Or in general diskless booting.

You build your initrd for remote boot. You have two options:
- copy a full /dev from a working host (tons of files that make the rd big
  just to fit all the inodes).
- spend a lot of time guessing what is and what is not needed on each node
  (you can have ata drives, scsi ones, different network cards, different
  graphics cards...)

I just want to boot with and empty /dev and let udev populate it, even with
same device names for different hadrware. And nodes will never hotplug anything.

IE, I want a working and race free devfs, and this is udev.

-- 
J.A. Magallon <jamagallon()able!es>     \                 Software is like sex:
werewolf!able!es                         \           It's better when it's free
Mandrake Linux release 10.0 (Cooker) for i586
Linux 2.6.1-rc1-jam1 (gcc 3.3.2 (Mandrake Linux 10.0 3.3.2-3mdk))

  reply	other threads:[~2004-01-03  1:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 11:48 udev - please help me to understand Steve Youngs
2004-01-02 13:00 ` Michael Buesch
2004-01-03  3:52   ` Steve Youngs
     [not found] ` <20040102123636.GA29909@mark.mielke.cc>
2004-01-02 20:21   ` Greg KH
2004-01-02 20:39     ` T'aZ
2004-01-03  3:56     ` Steve Youngs
2004-01-02 20:23 ` Greg KH
2004-01-03  1:00   ` J.A. Magallon [this message]
2004-01-03 12:54     ` Witukind
2004-01-03 21:56       ` Greg KH
2004-01-04 16:02         ` Kevin P. Fleming
2004-01-03  3:28   ` Steve Youngs

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=20040103010010.GA14823@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=greg@kroah.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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