/initrd.img symlink created with absolute target pathname
Bug #1020004 reported by
Juha Aatrokoski
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
The /initrd.img symlink is created with absolute target path in Precise. This makes accessing the latest initrd difficult if the rootfs in question is not *our* rootfs (e.g. nfsroot server). In Lucid the target path was relative, and so is the kernel path in Precise:
/initrd.img -> /boot/initrd.
/vmlinuz -> boot/vmlinuz-
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: precise |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1020004
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.