Unlike acceptable Unix systems, area the accessory nodes in the /dev agenda accept been a changeless set of files, the Linux udev accessory administrator dynamically provides alone the nodes for the accessories in fact present on a system. Although devfs acclimated to accommodate agnate functionality, advocates of udev cited a amount of reasons1 for preferring its accomplishing over devfs:
udev supports assiduous accessory naming, which does not depend on, for example, the adjustment in which the accessories are acquainted into the system. The absence udev bureaucracy provides assiduous names for accumulator devices. Any harder deejay is accustomed by its different filesystem id, the name of the deejay and the concrete area on the accouterments it is affiliated to.
udev executes absolutely in user space, as against to devfs' atom space. One aftereffect is that udev confused the allotment action out of the atom and can run approximate programs to compose a name for the accessory from the device's properties, afore the bulge is created.
udev supports assiduous accessory naming, which does not depend on, for example, the adjustment in which the accessories are acquainted into the system. The absence udev bureaucracy provides assiduous names for accumulator devices. Any harder deejay is accustomed by its different filesystem id, the name of the deejay and the concrete area on the accouterments it is affiliated to.
udev executes absolutely in user space, as against to devfs' atom space. One aftereffect is that udev confused the allotment action out of the atom and can run approximate programs to compose a name for the accessory from the device's properties, afore the bulge is created.
No comments:
Post a Comment