Michael Brown wrote: > On Thu, 12 Sep 2002, Buchan Milne wrote: [...]
>>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. This isn't documented anywhere (or at least nowhere obvious someone under pressure would look, ie rpm -qd terminal-server etc), Stew, would it be possible to add this to the help content for drakTermServ? [...] >>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. > OK, so this is more of an annoyance with SNF constantly overwriting config files ... I guess I will have to hack the template ... > 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. And the line gets removed from the file by SNF. And if you run drakTermServ, it overwrites the one SNF made (but at least only when you click the button). > > [ 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. ] > OK, I took a brief read through it, and will have some comments on it once I have looked at it a bit more ... it's something I have thought about a bit, and http://unixconfig.sourceforge.net spent a long time debating, but ultimately hasn't come up with anything. At least I agree with you on many aspects (such as the fact that comments need to be preserved). Buchan -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
