Frans Pop [EMAIL PROTECTED] writes:
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-grub
dean gaudet [EMAIL PROTECTED] writes:
that doesn't seem appropriate... update-grub isn't the only tool which is
invoked -- arbitrary user hooks are invoked, plus dozens of other
executables. isn't it wrong to pass them the IPC pipe on stdin? i
honestly don't know what the parent/child
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 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-grub
instead!
except that warning is sent
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
5 matches
Mail list logo