Package: base
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
If /nfsfolder/client1 is the nfsroot of a "client1" debian computer,
then /nfsfolder/client1/initrd.img exists, and it points to
/boot/initrd.img-3.2.0-4-486 instead of
/nfsfolder/client1/boot/initrd.img-3.2.0-4-486
This happens becouse a absolute symlink is used instead of a relative.
(example: ln -s initrd.img /boot/initrd.img-3.2.0-4-486
instead of
ln -s initrd.img boot/initrd.img-3.2.0-4-486 )
If you take a look at /vmlinuz it does not have this problem. A
relative symlink was used
This creates a problem in automating kernel updates of nfsroot debian
clients.
* What exactly did you do (or not do) that was effective (or
ineffective)?
rm initrd.img; ln -s initrd.img initrd.img-3.2.0-4-486
* What was the outcome of this action?
it works until the kernel updates and some script recreates it with "/"
* What outcome did you expect instead?
i would expect the script that creates that symlink (/initrd.img) to
drop the "/" and use relative path
*** End of the template - remove these lines ***
-- System Information:
Debian Release: 7.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i586)
Kernel: Linux 3.2.0-4-486
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
