r8518 - in trunk/BOOK: . chapter01 prologue

Sukucorp Sukucorp sukucorp at gmail.com
Sat Apr 12 17:25:44 MDT 2008


On Sat, Apr 12, 2008 at 5:28 PM, Bruce Dubbs <bruce.dubbs at gmail.com> wrote:
>
>  I'm not sure why.  The changes I added only say to change some (three) symbolic
>  links or add them if they don't already exist.   These changes to links can't
>  really hurt and it establishes a better base configuration from which to build
>  LFS.
>
>  The unsaid implication here is that if a user doesn't know how to change a
>  symbolic link, then they are not yet ready for LFS.
>
>  Resetting the links by a user is just as trivial as making them.  The only real
>  change I can see being made on the vast majority of systems that need any change
>  at all is to change /bin/sh to point to bash.
>

This is not about whether a user is competent enough to change
symlinks, it is about whether the user needs to update the symlinks on
the host. With the change you changed the minimum host system
requirements to something more the absolute minimum. The change
implies that if /bin/sh is a link to /bin/dash or if /usr/bin/awk is a
symlink to /usr/bin/mawk then LFS cannot be bootstrapped which is
simply not true.

-- 
Tushar Teredesai
 mailto:tushar at linuxfromscratch.org
 http://www.linuxfromscratch.org/~tushar/


More information about the lfs-dev mailing list