On Thu, 12 Sep 2002, Buchan Milne wrote: > Yesterday, I spent the day, and a large portion of the evening setting > up a server for a school, running 9.0rc2 (with updates from cooker) as: > 1)Domain controller and print server > 2)SNF > 3)Mail gateway > 4)Terminal server > (I know this isn't the best idea, but cash is limited - the whole > project including all new hardware is less than one of the new firewall > appliances, and we can only afford one machine until we can prove the > value of diskless clients). > I had some issues, which currently result in the clients not booting. I > will have one opportunity to fix this, probably on Saturday morning > (connectivity over a dialup also, so limited email/googling etc). > Unfortunately I didn't have time to investigate too much, but here we go: > The clients booted their kernel, I think managed the pivot ok, then > started up the init scripts, and just died there. One file listed as > missing was /etc/mtab, gprintf was not available, and then I got dumped > into a root shell saying I had to run fsck on some device, which > shouldn't have been mounted, and didn't exist in /dev on the machine. > /dev/ appeared to be very empty (about 40 files I think). If I remember > correctly, /dev/tty0 was missing (sorry, it was quite late by that stage). > If I want to try and fix these issues, what kind of things am I going to > need to do?
Run "msec 2" and all should be well. The terminal-server package exports the server's root file system with all_squash set, which means that root on the workstation is effectively an anonymous user on the server. Therefore, an anonymous user must be able to read all the files necessary in order to boot a workstation. This includes things like /etc/rc.d/init.d/functions. > One annoyance is that it seems impossible to have terminal-server and > snf configure dhcp, but terminal-server doesn't make allowance for a > dynamic range or WINS IPs (both of which I need for the +- 10 windows > desktops they currently have), if I were to add another interface to the > machine I don't see how I would be able to run two dhcpd's (yet, I could > hack a bit), and the SNF config also trashes everything the terminal > server setup. terminal-server provides an example DHCPD configuration file, which is made active only if you do not have a DHCPD configuration file at the time of installing terminal-server. The *only* thing that you need to add to a working DHCPD config file in order to turn it into a DHCPD config file that will work with terminal-server clients is the single line: include "/etc/dhcpd.conf.etherboot.include"; Absolutely everything else is automatic. Please note: I am talking about the terminal-server package as originally built by me; it is possible that the official Mandrake package works slightly differently. My package can be downloaded from www.fensystems.co.uk/RPMS.fensys/. > (The need for a configuration api which would make these two tools live > together is made evident by this setup). Not really; as I said, you need to add only one line to a working DHCPD config file in order to get it to serve terminal-server clients. [ However, while we're on the subject of configuration, you might want to take a look at the pre-alpha release of fenconfig, which is also available from www.fensystems.co.uk/RPMS.fensys. ] Michael Brown http://www.fensystems.co.uk -- Fen Systems: Linux made easy for schools
