Re: Bug#390038: this is caused by the use of /sbin/update-grub
dean gaudet <dean@arctic.org> 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 split is all about, so maybe the
> pipe is there for a good reason and there should be an update-grub wrapper
> specific to how this postrm script wants to work.
I'll change the wrapper to send it to stderr.
>> New installs write the lines in kernel-img.conf without any path (i.e.
>> just the command).
>
> that sounds at odds then with the path ordering in the postrm and the
> /sbin/update-grub wrapper. installer probably should put
> /usr/sbin/update-grub in there... (or the /sbin wrapper should go away...
> but istr there's a bug regarding why it was reinstated.)
If we remove the wrappers we break the upgrade path from Sarge it I
won't do that. Let's fix it in another way.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
Reply to: