I have just tried my first SuSE installation of 7.0 Professional, which went pretty smoothly except for one or two small problems which I wondered if anyone else had encountered. Everything looked fine until the end of the installation and configuration, and the system proceeded to complete it final boot. 1. 5 minutes timeout on starting HTTPD When it got to the point of start httpd (Apache), however, the boot froze for about five minutes before continuing, and when I checked httpd was not running. I spent a few hours hunting around, and eventually found the problem to be some hard coded FQDNs (linux.local) in /etc/httpd/midgard/midgard.conf It seems that anyone installing Linux with a host name and domain name other than the installation default should have had the same problem. If not, what did I do that was unusual or wrong? I couldn't see any mention of 'midgard' in the support database... (and to be honest I am not sure what it is for). 2. Power Status BAD The installation leaves runlevel 3 trying to start the UPS daemons via the /etc/rc.d/argo script. I have no UPS connected to ttyS0, so I can't imagine why this is being tried... I assume I just remove argo from the start and stop entries for runlevel 3 using the SysV init editor. 3. No power off. At the end of a shutdown, the screen displays the message: Failed services in runlevel 0: networker This seems to be an error in the file /etc/rc.d/networker where the argument to killproc is missing the /usr/sbin prefix which was used in the startup. 4. Several of the symbolic links in /etc/rc3.d (and rc2.d) are to non-exitant files. In particular K10pcp -> ../pcm (should be ../pcp) K96Frontbase -> Frontbase (should be ../Frontbase) K97FBWb -> FBWeb (should be ../FBWeb) Appart from these things, it was a pretty clean install. I checked the Suse web site, but couldn't see any errata for the release mentioning these problems, and I don't see how I would be the only one to encounter them??? DigbyT -- Digby R. S. Tarvin digbyt@acm.org http://www.cthulhu.dircon.co.uk