closure regarding udev

Nick Fotopoulos weasel at beyondnormal.org
Sun May 23 06:25:45 PDT 2004


On Sun, 2004-05-23 at 15:32 +0600, Alexander E. Patrakov wrote:
> Jeremy Utley wrote:
> > createfiles can create any individual file needed at the time of boot.  
> > Right now, I use it to create the nvidia devices, because they don't 
> > export their info to sysfs yet, and vmware devices if I'm using it.
> 
> So it is a _temporary_workaround_ for drivers that don't export the 
> information via sysfs yet.
> 
> > In response to your previous question, for my zip drive, I always 
> > modprobe the device by hand - I rarely use it, so I don't build it into 
> > the kernel.  I assume that when I load the module, and it detects the 
> > drive, it would send a hotplug event to udev for the device to be 
> > created, but I haven't tested that as of yet.
> 
> You are absolutely correct here. You modprobe the module, the kernel 
> sends the hotplug event, and udev creates the device. But it is rather 
> unfair to make our users to probe modules manualy.
> 
> -- 
> Alexander E. Patrakov
> To get my address: echo '0!42!+/6 at 5-3.535.25' | tr [!-:] [a-z] | tr n .
> -- 

Who is making them use anything manually.  Whether or not the person
uses udev, devfs, or staticly created devices, has no effect on how they
go about loading their modules if the choose to use them.  If anything
is unfairly forcing users to do things manually, it makedevices.sh...

Nick




More information about the lfs-dev mailing list