I'm having the same problem with a 013-pre something machine. First noticed it after I built a vserver kernel. I fix it using a livecd, chroot to my root and SymlinkProgram BootScripts. Everything does look fine. One thing I noticed, "shutdown -r now" doesn't restart but "reboot" does. I've always restarted remotely so I don't see any error messages.
I've updated to the 013 release BootScripts. I thought I fubar'ed something and was about to reinstall. Guess I'll try to track it down instead. Are you using the actual 013 or a prerelease? On 3/4/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: > This happened once before, but tonight it happened again: > > When I shutdown my system, I get these error messages: > > /System/Settings/BootScripts/Halt: line 2: Shutdown: No such file or > directory. > The boot theme shows (CheckList) and then all getty's are killed and I > can't log in, but the system is still running and processes are active. > ctrl-alt-del does nothing. Since most processes are still up, I can log > in with ssh. But doing "poweroff" there doesn't help. I tried to > manually kill all processes, unmount partitions and halt but that only > killed the ssh connection, leaving me with an isolated system in need of > physical power off. =( > > And then, the even worse thing, after this the machine does not boot > correctly! The boot theme shows, but I get: > > /System/Settings/BootScripts/Console: line 3: BootUp: No such file or > directory. > /proc/meminfo: No such file or directory > > Trying ctrl-alt-del says: > /dev/initctl: No such file or directory > > I booted with my LiveCD a couple of times, looking around to find the > problem. All files seemed to be there, > /P/BootScripts/Settings/BootScripts/BootUp was not missing, etc... > > At last I found out that after chrooting to my root fs from the LiveCD, > and doing SymlinkProgram on BootScripts, Udev and Sysvinit (all things I > could think of that would affect the boot in this way), it worked! > > Even though I saw some strange errors from udev flickering by the > screen, but this could also be because I changed to "Slack" theme to see > the errors better... Too bad those udev error messages doesn't stick to > /var/log/boot.log or any other log... > > So, there's surely a bug somewhere. I'm trying to remember if I did > something, and the only thing I can think of is that I've used > DisableProgram on XMMS and GTK+ 1.2.10. Perhaps there's a bug here that > destroys the wrong symlinks? > > It would be nice with a script that checks for missing symlinks for all > installed programs. > -- > /Jonatan -=( http://kymatica.com )=- > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel@lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel > -- Carlo J. Calica _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
