From mboxrd@z Thu Jan 1 00:00:00 1970 From: md@Linux.IT (Marco d'Itri) Date: Fri, 18 Aug 2006 17:02:49 +0000 Subject: Re: [PATCH] optical_gen Message-Id: <20060818170249.GA23268@wonderland.linux.it> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Aug 18, Kay Sievers wrote: > Marco, how does Debian handle the other issues when it never triggers > failed events again? Like /usr or other part of the filesystem, or > whatever service not available at that time of the bootup? Scripts fork and wait in the background until they can continue. I still do not like the idea of restarting all failed events without knowing why they failed. > The generic 'retrigger' to create the rules later, when /etc is writable > sounds much easier than having a special boot script logic for that > special case. Looks simple enough to me: :-) # copy the rules generated before / was mounted read-write for file in /dev/.udev/tmp-rules--*; do dest=${file##*tmp-rules--} [ "$dest" = '*' ] && break cat $file >> /etc/udev/rules.d/$dest rm -f $file done > In an initramfs boot, which is the standard distro setup today, /etc is > writable at that point anyway, and we don't have that problem, right? Does a typical initramfs have e.g. sed? -- ciao, Marco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel