Will Dyson on 29 Oct 2006 20:06:53 -0000 |
On 10/9/06, Art Alexion <art.alexion@verizon.net> wrote: On Sunday 08 October 2006 13:06, sean finney wrote: > hey art, > > > The only boot problem I still detect is that init stalls on HAL > > initialization. It complains that it can't create a file because the > > directory already exists. I was able to continue booting by pressing > > ctrl+c and ctrl+d a few times. Any suggestions here? I will need to > > reboot to find out the precise file overwriting problem and whether > > ctrl+c or d was what did the trick. > > you could always try reinstalling that too ("dpkg -S filename" will tell > you what package "owns" a file, btw). otherwise, you'll need to post > more information (logs, error messages, etc) if you want more help.
Two errors I can see.
I don't have a dapper system handy at the moment to compare with, but as Sean said, this is a pretty odd error. Especially since the string var.run does not occur anywhere in your config files. I'd like to see the output of 'mount' and 'uname -a' on your system. The errors could be from a script running from the initramfs. That would not show up on a search through /etc. If that was the case, it would indicate an out-of-date kernel, or just a need to update your initramfs. If you run sudo dpkg-reconfigure linux-image-$(uname -r) Do the errors go away? -- Will Dyson ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|