All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: udev for dummies
Date: Thu, 11 Dec 2003 23:16:04 +0100	[thread overview]
Message-ID: <20031211221604.GA2939@werewolf.able.es> (raw)

Hi all...

I am starting to use 2.6, and I really would like to use udev.
But I can't find a doc about how to move from taditional heavily
populated /dev to new method.

Any pointer ?

I have installed udev and hotplug utils, and have hotplug enabled in
kernel.
As I undestand it, I should do now something like
- run udev for the first time, so it populates /udev
- check that basic dev files are there
- move /dev to /dev.old, and ln -s /udev /dev (or real-move it and
  change udev.conf to write directly on /dev)

Or just create and empty /dev, and let hotplug call hotplug scripts
on boot which in turn call udev. Is this correct ? Will hotplug call
udev for the built-in drivers ?
Could it also work without hotplugging, ie, can I use udev to just
create a minimal /dev for my system ?

After installing udev, I run /sbin/udev and nothing appears on
/udev.

What am I missing / misunderstanding ?

TIA

-- 
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.0-test11-jam1 (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-4mdk))

             reply	other threads:[~2003-12-11 22:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 22:16 J.A. Magallon [this message]
2003-12-11 22:59 ` udev for dummies David T Hollis
2003-12-12  2:49   ` Chris Friesen
2003-12-12 21:32     ` Greg KH
2003-12-12  4:43   ` Bob
2003-12-12 21:31 ` Greg KH
2003-12-14 18:36   ` Martin Schlemmer

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=20031211221604.GA2939@werewolf.able.es \
    --to=jamagallon@able.es \
    --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 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.