On Thu, Dec 08, 2005 at 10:51:56PM +0100, Erik van Konijnenburg wrote: > On Thu, Dec 08, 2005 at 04:42:51PM -0500, Norbert Veber wrote: > > On Sat, Dec 03, 2005 at 07:46:34PM +0100, Erik van Konijnenburg wrote: > > > The reason is that install lines in the modprobe configuration are > > > complete > > > shell scripts: they can invoke every executable, access every file. > > > > Oh I see. How does the old mkinitrd handle this? > > Ignore the install lines and hope for the best. > > quoting mkinitrd: sed -n 's%^insmod \([^ ]\+\).*%\1%p'
Oh. Thats probably reasonable as long as its documented, or better yet a warning could be printed. Failing with an error is a bit overkill I think. Thanks, Norbert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
