severity 380338 minor
thanks
Hi,
While I can appreciate the pain caused by moving a binary from
/sbin to /usr/sbin, changing kernel-package is not critical to the
solution of the problems we have.
No matter what we do, /etc/kernel-img.conf would need to be
changed for the machines where it is currently set to the old path.
I do not envisage update-grub changing location again, so the edit
could just as well be to go from /sbin/update-grub to
/usr/sbin/update-grub, no changes needed, and that would probably
work well for update-grub in the foreseeable future.
Now, as to whether kernel-package should check the postinst
hook or not for existence etc, I would like to point out that we are
running user input as root, so the default stance should be to do as
many sanity checks as we can.
I am also not happy about just trusting the PATH env variable
(though, I suppose, if root's PATH has been compromised we have worse
things to worry about, but then I would not like to add yet another
point of carnage when root's path is cracked).
Having said that, I guess I could check in in a restricted
path list like /bin:/sbin:/usr/bin:/usr/sbin if the postinst hook
does not contain a full path.
I am not going to edit the conffile on disk in the postinst,
which is complex enough already, and add to code that has to check
for the version of grub and test paths and edit a configuration file
and not lose user input and support and maintain that code for
backwards compatibility for ages just to correct snafu's in other
packages, sorry.
manoj
--
The ripest fruit falls first. William Shakespeare, "Richard II"
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
