Hi there, I've fixed the problem and it comes down to one of two things. I installed the RPMs on a fresh RH7.2 install and didn't reboot the computer after installing the rpms. I think this is the most likely problem however one other thing I changed was that I had set the eth0 to use 192.168.0.1 and ltsp was trying to load from 192.168.0.254. I haven't got time to check out if the conflicting eth0 setting was the problem or if it was all down to rebooting after installing the rpms.
I know it should have clicked with me seeing as how the rpms included ones affecting the kernel, but I guess when I'm not in Windows land I don't automatically think of rebooting when installing software. This also started all of the services that weren't started that I startedby following through the trouble shhoting guide. Maybe it's worth putting a note at the end of the server setup to say that restarting the machine is nec? Anyway, problem solved thanks for you thoughts. cheers, noel On Wednesday, February 27, 2002 11:16 PM, Jason Bechtel [SMTP:[EMAIL PROTECTED]] wrote: > Jim- > > I got the i386.1 directory when I installed on SuSE 7.2 because it's not > supported. I installed the ltsp_core RPM and it bombed on the > install.sh. Unfortunately, it had already created the i386 dir, so when > I finally looked through the install_scripts directory and modified > stuff and ran install.sh, it backed the i386 dir to i386.1 and then put > in a broken i386 dir. At least, that's what I think happened... > > But I think that he was using a supported distro, anyway. I just > thought that my experience might lend some insight. > > Just a pipe dream, but maybe the behavior of the installer on > non-supported distros could be improved so that it doesn't do anything > half-*ssed or anything to cause the later scripts trouble. Maybe a > simple clean-up after detecting the unsupported environment... Of > course, this might defeat the whole point of having "supported > distributions"... Depends on your perspective. > > Jason > > > > Date: Tue, 26 Feb 2002 17:26:48 -0500 (EST) > > From: <[EMAIL PROTECTED]> > > > > I'm not sure what is going on, but i386.1 is supposed > > to be a backup directory. When the LTSP core package > > is installed, it will look to see if there is already > > an existing i386 directory. If there is, it will rename > > it to i386.1, then install a new i386 directory. > > > > if you have an empty i386 directory and you also have an > > i386.1 directory then the correct way to fix that > > is to remove the empty i386 directory and then rename > > i386.1 to i386. > > > > Changing dhcpd.conf to look in i386.1 is likely to cause > > problems later. > > > > Now, if only I had a few extra minutes to track down why > > you are getting the i386.1 directory in the first place. > > > _____________________________________________________________________ > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > For additional LTSP help, try #ltsp channel on irc.openprojects.net _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
