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?
--
To UNSUBSCRIBE, email to
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.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 8 Dec 2005 16:42:51 -0500
Norbert Veber [EMAIL PROTECTED] 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
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
On Tue, Nov 29, 2005 at 01:57:32PM -0500, Norbert Veber wrote:
yaird error: modprobe psmouse requires install /sbin/modprobe mousedev
/sbin/modprobe --ignore-install psmouse (fatal)
Failed to create initrd image.
from my modprobe configuration:
alias /dev/psaux psmouse
install psmouse
Package: yaird
Version: 0.0.11-12
Severity: important
Setting up linux-image-2.6.14-2-k7 (2.6.14-4) ...
Using /usr/sbin/mkinitrd.yaird to build the ramdisk.
Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd
/usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs.
yaird error: modprobe
6 matches
Mail list logo
