On Fri, Nov 27, 2009 at 9:39 AM, stosss <sto...@gmail.com> wrote:
> On Fri, Nov 27, 2009 at 9:35 AM, Chris Staub <ch...@beaker67.com> wrote:
>> On 11/27/2009 09:32 AM, stosss wrote:
>>> On Fri, Nov 27, 2009 at 9:19 AM, Chris Staub<ch...@beaker67.com>  wrote:
>>> About the only things that are there is the Linux kernel, bash, grub
>>> and coreutils, beyond that there is nothing else. The /var /usr /sys
>>> directories are empty. there is no vi or vim cmd, no tar cmd, no make
>>> cmd, no man pages, no docs for anything. The very basic cmds for the
>>> cli are there but nothing else.
>>
>> By "empty" do you mean that /usr and /var have absolutely nothing, not
>> even other directories? There's nothing in /usr/bin? Also if /sys is
>> empty that means you forgot to mount it - nothing is supposed to be
>> installed there. Same with /proc...and what about /dev?
>> --
>> http://linuxfromscratch.org/mailman/listinfo/lfs-support
>> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
>> Unsubscribe: See the above information page
>>
> Yes I mean empty. no files no directories nothing.
>

here is a sample of the errors at boot up just before the login prompt.

cd: /var/lock: no such file or directory
/etc/rc.d/rcsysinit.d/S45cleanfs: line 86: cd: /var/run: no such file
or directory
/etc/rc.d/rcsysinit.d/S45cleanfs: line 89: cd: /var/utmp: no such file
or directory
chmod: cannot access '/var/run/utmp': no such file or directory
chgrp: cannot access '/var/run/utmp': no such file or directory
/etc/rc.d/rcsysinit.d/S80localnet: line 17: /etc/sysconfig/network: no
such file or directory

INIT: entering runlevel: 3
Starting system log daemon...
/etc/rc.d/init.d/functions: line 577: nice: command not found
Starting kernel log daemon...
/etc/rc.d/init.d/functions: line 577: nice: command not found
/etc/rc.d/rc3.d/S20network: line 19: /etc/sysconfig/network: no such
file or directory
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to