Am 15.01.2013 09:04, schrieb Bob Proulx: > Maroš Žilka wrote: >> I was reading The Linux System Administrator's Guide >> [http://www.tldp.org/LDP/sag/html/index.html] and there is stated that >> device files are creatied by /dev/MAKEDEV but in my debian stable >> instalation /dev/MAKEDEV is just symbolic link to /bin/true and i also >> find out that there is package makedev which provides that but it is >> not installed, so my question is what is default mechanism for debian >> to fill /dev/ and more specifically how are /dev/loop* files created. > > That documentation is the classic legacy way. It has since been > completely obsoleted. The new way is with "udev". The goal is to > create an event driven strategy to handle hotplugged devices such as > pcmcia and usb and any other hot plugged device. Currently with udev > /dev is a tmpfs ram file system and udev creates devices there as > needed. Being a ram file system it is created fresh with every > reboot. > > $ df -lhT /dev > Filesystem Type Size Used Avail Use% Mounted on > udev tmpfs 1.8G 244K 1.8G 1% /dev > > The kernel will notice that a device appears. It will notify udev. > udev will create a new device for it as it appears. The device is > removed. The kernel will notice it is gone and notify udev. udev > will remove the device. It is dynamic. Actually, this information is outdated too. Nowadays, the devices in /dev are created by the kernel itself using a tmpfs callsed devtmpfs [1]. Udev only creates symlinks or applies permissions. Cheers, Michael [1] http://lwn.net/Articles/330985/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature