the linux-image .postrm script is (through some mechanism) invoking
/sbin/update-grub.
/sbin/update-grub gives a warning now:
You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead!
except that warning is sent on stdout.
stdout in the .postrm script is hooked up
On Sun, 3 Dec 2006, Frans Pop wrote:
On Sunday 03 December 2006 22:34, dean gaudet wrote:
the linux-image .postrm script is (through some mechanism) invoking
/sbin/update-grub.
/sbin/update-grub gives a warning now:
You shouldn't call /sbin/update-grub. Please call /usr/sbin/update
Package: initramfs-tools
Version: 0.85a
the run_scripts() function should respect the same naming conventions as
run-parts(8) ... in particular if my editor creates foo~, foo.bak,
.foo.swp files run_scripts() will try to run them. ditto for foo,v.
run_scripts() should also not attempt to
mdrun does not respect the device minor numbers at all... this can totally
mess up the ordering of md devices and screw with static mounts (note that
while mounting by label/uuid is preferable it isn't always available --
for example XFS external log partitions cannot be specified by label or
Package: initramfs-tools
Version: 0.59b
hi... if you're going to use mdrun /dev and launch all arrays during the
initrd then you should also include mdadm.conf -- because otherwise you
may end up starting arrays on the wrong minors... or even worse, if
someone is using partitioned md then
Package: initrd-tools
Version: 0.1.84
currently for a root on md raid mkinitrd does something like this:
mdadm -A /dev/md3 -R -u 2b3a5b77:c7b4ab81:a2b8322a:db5c4e88 /dev/sdb4 /dev/sda4
however this has the problem that it will require the root raid devices to
always reside at /dev/sda4 and
Package: linux-image-2.6.12-1-686-smp
Version: 2.6.12-7
usb audio worked in -6... but as of -7 i'm getting this in dmesg when the
module is inserted:
snd_usb_audio: Unknown symbol __compound_literal.170
snd_usb_audio: Unknown symbol __compound_literal.89
snd_usb_audio: Unknown symbol
7 matches
Mail list logo
