Aggelos aggman at
Wed Oct 3 00:09:25 PDT 2001

I suggest including a let say "critical updates log", where all critical or
most important updates should be listed, with respect to the previous lfs
for example in lfs-3.0 with respect to lfs-3.0-pre4. And next to each
critical update, some brief directions/instrucions as to what actions should
be taken regarding the update, always with respect to the previous version

----- Original Message -----
From: "Gerard Beekmans" <gerard at>
To: "lfs-support" <lfs-support at>
Sent: Tuesday, October 02, 2001 5:19 PM
Subject: Re: troubleshooting-upgrading

> On Tue, Oct 02, 2001 at 12:55:55PM +0300, Aggelos wrote:
> > Mounting other file systems... modprobe: modprobe: Can't locate module
> >
> > Setting clock... modprobe: modprobe: Can't locate module
> nls_cp437 is some locale setting that you probably enabled in your kernel.
> If you don't need/use it, go to kernel config, disable it.
> char-major-10-135 refers to the RTC device through /dev/rtc - perhaps you
> enabled rtc support in the kernel as a module, but didn't load the module
> before running the setclock script. Or /dev/rtc doesn't exist
> > And another question: How should someone find his way in a newer edition
of the lfs-book, in order to see what changes have been introduced,
> > and probably try to bring his lfs in a more or less updated state ? I
have read the changelog part of the lfs-book, but I don't find its format to
be so clear for someone not experienced in linux.
> Well the changelog is the only and best place to go to find out what was
> changed since the last version. It quickly explains in which chapter and
> section something was updated. You can then judge whether you want to
> reinstall the package, or re-create the bootscripts, or whatever. If in
> doubt just reinstall any package mentioned in the changelog and you'd be
> well on your way keeping it up to date.
> If you don't find the format clear then suggest a better format.
> --
> Gerard Beekmans
> -*- If Linux doesn't have the solution, you have the wrong problem -*-
> --
> Unsubscribe: send email to listar at
> and put 'unsubscribe lfs-support' in the subject header of the message

Unsubscribe: send email to listar at
and put 'unsubscribe lfs-support' in the subject header of the message

More information about the lfs-support mailing list