[Ltsp-discuss] confusing error in lts.conf

2011-04-07 Thread David Burgess
I added some MAC entries to my lts.conf yesterday and rearranged the ordering of sections slightly. Today I noticed that my clients weren't setting their hostname according to the HOSTNAME variable, which is something that was working until yesterday. So I did some investigating: ~# cat

Re: [Ltsp-discuss] confusing error in lts.conf

2011-04-07 Thread David Burgess
On Thu, Apr 7, 2011 at 9:14 AM, David Burgess apt@gmail.com wrote: I added some MAC entries to my lts.conf yesterday and rearranged the ordering of sections slightly. Today I noticed that my clients weren't setting their hostname according to the HOSTNAME variable, which is something that

Re: [Ltsp-discuss] confusing error in lts.conf

2011-04-07 Thread Pierre Yann Baco
The [dunvegan] section is empty as the only line in it is commented out. It could be a parser problem, finding a section name right after another one with no content in between? Le 07/04/2011 17:21, David Burgess a écrit : On Thu, Apr 7, 2011 at 9:14 AM, David Burgessapt@gmail.com wrote:

Re: [Ltsp-discuss] confusing error in lts.conf

2011-04-07 Thread Gideon Romm
David, You have 2 empty sections there. Sections cannot be empty - you need at least one uncommented param=value line. -Gadi On Thu, Apr 7, 2011 at 11:14 AM, David Burgess apt@gmail.com wrote: I added some MAC entries to my lts.conf yesterday and rearranged the ordering of sections

Re: [Ltsp-discuss] ltsp@debian: Upgrade of chroot to squeeze gives nfsmount: need a path error

2011-04-07 Thread Vagrant Cascadian
On Wed, Apr 06, 2011 at 09:39:44AM +0100, Rainer Stumbaum wrote: I found the regression: udhcpc is called in init-premount to get the DHCP configuration. The udhcpd used in the busybox does not ask the DHCP server for the rootpath option. Adjusting the udhcpc call in