Re: syslog messages NOT! - the last word?

["Jose M. Sanchez" <opjose ex-pressnet com>]

Yeah I missed that one. Other than /home, /opt and /usr most of the other
directories MUST be present at boot time or else the system will not
initialize itself properly due to scripts, etc...

-JMS

-----Original Message-----
From: Kevin Colby <kevinc grainsystems com>
To: redhat-install-list redhat com <redhat-install-list redhat com>
Date: Friday, October 30, 1998 11:09 AM
Subject: Re: syslog messages NOT! - the last word?


>Hrm.
>I don't like that linking business very much,
>but I have to admit I wouldn't set /boot aside
>from root.  Thanks for the heads-up anyway.
>
> - Kevin Colby
>   kevinc grainsystems com
>
>
>Greg W. Fiske wrote:
>>
>> I  believe I have figured it out.  Here is a summary:
>>
>> etc/rc.d/rc.sysinit makes three symlinks (lines 121-123) on every
>> reboot.
>>
>>         ln -sf /lib/modules/$mver /lib/modules/preferred
>>         ln -sf /boot/System.map-$mver /boot/System.map
>>         ln -sf /boot/module-info-$mver /boot/module-info
>>
>> On my installation, System.map and module-info symlinks aren't being
>> created, but /lib/modules/preferred is.  Now, at this point, only / and
>> /proc are mounted (see around line 100).  Now, I have a seperate
>> partition for /boot and since it isn't mounted when the /boot symlinks
>> are created they get wiped out when /boot is mounted later.
>>
>> So, I submitted that to developer.redhat.com/bugs (whose bug lists have
>> been down for quite a while).
>>
>> I fixed this by manually making the symlinks myself.
>>
>> But, I'm still having trouble with signal 11 for pppd. Sigh.
>>