CentOS 6 grabs i386/lts.conf for x86_64 clients

Bug #1198937 reported by Berend De Schouwer
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LTSP5
Expired
Undecided
Unassigned

Bug Description

LTSP on CentOS 6 grabs /ltsp/i386/lts.conf via TFTP, despite everything else being x86_64, eg. /ltsp/x86_64/vmlinuz.ltsp and /opt/ltsp/x86_64

It should grab i386 for i386, and x86_64 for x86_64

Revision history for this message
Joshua Trimm (enslaver-l) wrote :

We are working on a unified solution for a central location and daemon for the configuration to be stored and grabbed. There really is no need at the moment that I can see for a different conf file for each architecture. I'm sure there are real world instances where such are needed but they can still be combined into one file with subsections.

Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

The lts.conf location is usually determined from the bootfile location of DHCP.
I don't know about CentOS, but for example in Debian, ipconfig in initramfs does a DHCP request, sends a "Linux ipconfig" identifier in the request, and dhcpd is supposed to answer with /ltsp/amd64/lts.conf or something similar.

Is your dhcpd configured to send the correct bootfile at the initramfs request?

Changed in ltsp:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for LTSP because there has been no activity for 60 days.]

Changed in ltsp:
status: Incomplete → Expired
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.