ltsp-build-image --chroot option not associated nbd image name
Bug #1592780 reported by
Ivan
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LTSP5 |
Expired
|
Undecided
|
Unassigned |
Bug Description
XUBUNTU 16.04
ltsp-server 5.5.7-1
Build two images (fat and thin)
1) fat without option --chroot
chroot /opt/ltsp/i386; img /opt/ltsp/
2) thin with option --chroot i386thin
chroot /opt/ltsp/i386thin; img /opt/ltsp/
for both client nbdroot in initramfs = /opt/ltsp/
To post a comment you must log in.
Ubuntu 18.04 LXDE 4.15.0-33-generic standalone 5.5.10-1build1
ltsp-server-
I have two trees: amd64-libre
/opt/ltsp/amd64
/opt/ltsp/
Images: images/ amd64.img images/ amd64-libre. img
/opt/ltsp/
/opt/ltsp/
NBD configs (each config points to correct image): server/ conf.d/ ltsp_amd64. conf server/ conf.d/ ltsp_amd64- libre.conf
/etc/nbd-
/etc/nbd-
Have to lines in dnsmasq.conf for 2 types of cliens: tag:ltsp, /ltsp/amd64/ pxelinux. 0,,172. 22.11.21 tag:ltsp2, /ltsp/amd64- libre/pxelinux. 0,,172. 22.11.21
dhcp-boot=
dhcp-boot=
at boot time I see different filenames: pxelinux. 0 libre/pxelinux. 0
Filename: /ltsp/amd64/
Filename: /ltsp/amd64-
but all clients boot to one image: amd64.img