Thanks Mary,
I tried typing "Linux init=/bin/sh" at the LILO prompt and it booted
without all the bells & whistles, but when I tried 'vi' or 'apt-get' I was told they were
unknown commands. I had thought I might try changing '/etc/apt/sources.list' to
testing and deleting and reinstalling samba, or just doing another 'dist-upgrade'.
I could do a 'find' and 'rm' the samba files but that might be a bit unpredictable.
But if 'vi' was not available, what do I use to edit and save files ?
I think I'll sleep on it. After getting 2.6.5 working, I don't wish to blow it.
Cheers,
Adam.
On Mon, May 24, 2004, Adam Felix Bogacki wrote:
"rsync daemon not enabled in /etc/default/rsync Starting Samba daemons: nmbd smbd"
... until reboot..
I have heard something about about rsync being buggy in unstable (if that's relevant).
That looks more like a Samba bug than an rsync bug. All the "rsync daemon not enabled in /etc/default/rsync" message means is "I'm not starting the rsync daemon because you've told me not to in the file /etc/default/rsync".
Google assumes you can first boot in and then do things as root.
If you type "Linux init=/bin/sh" at the LILO prompt, does this let you boot and log in as root? That should skip the loading of the daemons (and of a lot of other things).
If you're not getting a LILO prompt on bootup (just a LILO 22.x message and then straight into booting), then I believe you should press "Tab" a few times when the LILO message appears.
Alternatively, boot from a rescue disk. Almost every Linux install CD doubles as a rescue disk.
-Mary
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
