[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dependencies on makedev

Hash: SHA1

Adam Heath <doogie@debian.org> writes:

> On Thu, 29 Dec 2005, Marco d'Itri wrote:
>> On Dec 29, Adam Heath <doogie@debian.org> wrote:
> How does persistance of the permission model work?  Can I do chown/chmod on
> the dynamic files in /dev, and have them remain the next time?  Even if a
> device node changes it's name?  Or do I have to edit some alternative
> database?

You edit or add to the udev rules.  These are usually used to set
policy for whole categories of devices, but you can of course fine
tune it, or replace all the standard rules with your own.  The default
gives you all the standard names, as with a static /dev.  (I
personally switched it to the devfs-style rules.)

> I've been running 2.6 for a while now.  Lots of our servers do(all
> our xen machines).  We've had no use for any dynamic device
> anything; in fact, I'd much prefer to not have anything dynamic on a
> server; stable names is all I want

The names are stable, but the devices are created dynamically.  The
only exceptions are hotplug events which may not always occur/complete
in the same order.  This will not be an issue for a server where you
are not e.g. constantly plugging and unplugging lots of USB storage

I've been running udev on all my systems for some time now without any
problems at all.  The fact that the available devices nodes actually
matches your hardware is quite useful.

Even if you never use udev yourself (though I would recommend at least
trying it), Marco's proposal does make sense: even if you never use
it, we do need to allow for the eventual removal of makedev on systems
using udev--when all the device nodes are already created, it's no
longer useful; this will not preclude it being installed by hand on
systems with a static /dev.


- -- 
Roger Leigh
                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                Debian GNU/Linux        http://www.debian.org/
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>


Reply to: