On Wed, Sep 19, 2007 at 10:44:56AM +0100, Ian Campbell wrote: > A couple of reasonable workarounds occur to me: > * Don't run mkboot if the user is not root;
This would break any scenario wherein the user is expecting mkboot to run as non-root. > * Only to run mkboot if $4 (install path) is empty (==install to > /boot); This would break any setups where mkboot is expected to work with a different directory. Note that the directory is passed to mkboot. > * Use the full path to mkboot; This would break any setups where a custom mkboot is being used from /usr/local/sbin. I suppose that checking for uid 0 is the best option. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
