ltsp-update-kernels dies if you already have a PPC chroot tree installed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ltsp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
If you run ltsp-update-kernels on a server that already has a PPC chroot installed (Like from the ltsp-5 tarballs from ltsp.org), the ltsp-udpate-kernels script fails, because it tries to create a symlink for the yaboot file. Well, it turns out you don't even need the symlinks. Chuck Liebow and I proved that you can boot PPC thin clients just fine without the yaboot symlinks.
If ltsp-update-kernels was running as a port of ltsp-build-client, the failure causes ltsp-build-client to also fail.
Here's the output:
Setting up linux-image-386 (2.6.20.13.10) ...
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386.sv
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/
ln: creating symbolic link `/var/lib/
error: LTSP client installation ended abnormally
| Jim McQuillan (jam-mcquil) wrote | #1 |
| Oliver Grawert (ogra) wrote | #2 |
| Changed in ltsp: | |
| status: | Unconfirmed → Fix Released |
I've included a patch to remove the lines that try to create the yaboot symlinks.
The only thing this patch does is remove 11 lines of code. There's no new code being added.