Fixed in LTSP 5.3. NBD exports are now declared in /etc/nbd-
server/conf.d used of inetd.conf.
** Changed in: ltsp
Status: Triaged = Fix Released
** Changed in: ltsp
Assignee: (unassigned) = Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member
Fixed in LTSP 5.3. NBD exports are now declared in /etc/nbd-
server/conf.d used of inetd.conf.
** Changed in: ltsp (Ubuntu)
Status: Triaged = Fix Released
** Changed in: ltsp (Ubuntu)
Assignee: (unassigned) = Alkis Georgopoulos (alkisg)
--
You received this bug notification because
** Changed in: ltsp (Ubuntu)
Status: New = Triaged
** Also affects: ltsp
Importance: Undecided
Status: New
** Changed in: ltsp
Status: New = Triaged
** Changed in: ltsp
Importance: Undecided = High
--
You received this bug notification because you are a member of
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...
--
You received this bug notification because you are a member of
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.
--
Lucid Alternate Alpha3 AMD64, wrong
On Sat, 2010-02-27 at 11:56 +, 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
