Lucid Alternate Alpha3 AMD64, wrong line in inetd.conf for i386 chroot after installation

Bug #528951 reported by Asmo Koskinen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LTSP5
Fix Released
High
Alkis Georgopoulos
ltsp (Ubuntu)
Fix Released
Undecided
Alkis Georgopoulos

Bug Description

Lucid Alternate Alpha3 AMD64 is OK to install, but after installation there is wrong line in inetd.conf file for i386 chroot.

I removed /opt/ltsp/amd64 after installation and build new one - /opt/ltsp/i386.

Thin client did not boot because of wrong image.

cat /var/log/daemon.log | grep amd64

Feb 27 12:38:43 cluster1 nbd_server[1424]: connect from 192.168.1.200, assigned file is /opt/ltsp/images/amd64.img
Feb 27 12:38:43 cluster1 nbd_server[1424]: Could not open exported file /opt/ltsp/images/amd64.img: No such file or directory

When I changed manually one line in inetd.conf, thin client booted just fine.

cat /etc/inetd.conf

#:OTHER: Other services

9571 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/ldminfod
9572 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdswapd
2000 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/i386.img

Best Regads Asmo Koskinen.

Revision history for this message
Asmo Koskinen (asmok) wrote :

You know, for someone who is new to LTSP this is really mess. For a heavy server you need AMD64, but also i386 chroot.

Why we do not have i386 chroot as a default option when performing installation from Alternate AMD64 CD?

Best Regards Asmo Koskinen.

Revision history for this message
Stéphane Graber (stgraber) wrote : Re: [Bug 528951] Re: Lucid Alternate Alpha3 AMD64, wrong line in inetd.conf for i386 chroot after installation

On Sat, 2010-02-27 at 11:56 +0000, Asmo Koskinen wrote:
> You know, for someone who is new to LTSP this is really mess. For a heavy server you need AMD64, but also i386 chroot.
>
> Why we do not have i386 chroot as a default option when performing
> installation from Alternate AMD64 CD?
>
> Best Regards Asmo Koskinen.
>

That's because these CDs must be self-contained (as in, not require
access to the internet) and so it's impossible to get the i386 packages
from there.

It's a known issue for which we can't do much (at least for Lucid), the
long term plan was to offer an option to create a i386 chroot using
internet (but that'd be opt-in, not the default).

--
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com

Revision history for this message
beetlebolt (beetlebolt) wrote :

After rebuilding my i386 image this happened to me too. Asmo's post fixed it for me. Any suggestions how to improve my image re-build script so I don't have to edit the /etc/inetd.conf file also? This was a real gotcha for me...

Changed in ltsp (Ubuntu):
status: New → Triaged
Changed in ltsp:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

Fixed in LTSP 5.3. NBD exports are now declared in /etc/nbd-server/conf.d used of inetd.conf.

Changed in ltsp:
assignee: nobody → Alkis Georgopoulos (alkisg)
status: Triaged → Fix Released
Changed in ltsp (Ubuntu):
assignee: nobody → Alkis Georgopoulos (alkisg)
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.