Hi, On Sonntag, 5. Mai 2013, Petter Reinholdtsen wrote: > > ain't this because we had/have some i386 settings hardcoded? A few > > years ago this made sense, but today I do see how amd64 only setups > > are useful and desirable. > Yes, on amd64 we install an i386 LTSP chroot, based on the old truth > that all LTSP clients had less than 4 GiB RAM and some of them had > 32-bit CPUs, making it the most sensible choice to make sure as many > clients as possible would work out of the box. > > I have no idea if this is still true, or if all clients these days > have 64-bit CPUs or some of them have more than 4 GiB RAM. If so, > amd64 would be a more sensible choice for the LTSP chroot. I've been thinking about this several times and came to the conclusion that I believe it's best to - continue to default to install an i386 chroot on amd64 installs _if possible_, else install an amd64. - document how to create such a chroot more expclicitly with these constraints. Comments? > Changing it is easy, though. Would have to edit > share/ltsp/plugins/ltsp-build-client/Debian-custom/000-arch-detection > in debian-edu-config. ack. > > I guess I shall setup jenkins tests for these. for now I've just put it in the TODO there :/ cheers, Holger
Attachment:
signature.asc
Description: This is a digitally signed message part.