[EMAIL PROTECTED] wrote: >> No, I think modprobe directives are more appropriate for this task. >> You need a script anyway to change the sysfs permissions, create the >> /var/run/ directory, etc. So it can as well wait for the sysfs files to >> appear. Let me know if you have more doubts. >Ok, it took me a while to figure out that the daemon could not be >started early in the boot process because at the time udev modprobes >the drivers, the filesystem is still read-only (including /var), so it >can't write its PID file. It is possible to work around it by using >/lib/init/rw as the location of the PID file, do you think this is an >acceptable solution? You need /var/log/ anyway for the log file, so I suggest that you make the script wait until /var has been mounted rw.
-- ciao, Marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
