Ltsp-build-client updates kernel a tftboot for all images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LTSP5 |
Won't Fix
|
Low
|
Unassigned |
Bug Description
ltsp-build-client --dist precise --arch amd64 --purge-chroot --copy-sourceslist --apt-keys /etc/apt/
Which should create a image fat-amd64
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/fat-i386
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/amd64
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/fat-amd64
Regenerating kernel...
Skipping yaboot configuration. install yaboot package if you need it.
Skipping etherboot images. Install the mkelfimage package if you need them.
Skipping netabootwrap images. Install the aboot package if you need them.
Skipping sparc piggyback images. Install the sparc-utils package if you need them.
Done.
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/fat-i386
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/amd64
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/i386
Updating /var/lib/tftpboot directories for chroot: /opt/ltsp/fat-amd64
Parallel mksquashfs: Using 4 processors
Creating 4.0 filesystem on /opt/ltsp/
But for some reason it updates all ?
Changed in ltsp: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in ltsp: | |
assignee: | nobody → Vagrant Cascadian (vagrantc) |
It does only make the right image though but recreates the kernel and tftboot directories for all images?