On Wed, May 20, at 11:05 Bruce Dubbs wrote: > Trent Shea wrote: > > Hello, > > > > > > I'm just bringing this to the proper list: > > > > Beginning of thread: > > http://linuxfromscratch.org/pipermail/alfs-discuss/2009-May/009729.html > > > > Proposed adjustment: > > http://linuxfromscratch.org/pipermail/alfs-discuss/2009-May/009733.html > > > > > > I'd like to propose that we follow Matt's suggestion as it leaves the > > instructions intact for educational purposes, and it leaves the system in a > > state that the book's instructions and tools expect. > > > > Any other suggestions or discussion are welcome. If there are no objections > > I'll create a ticket and submit a patch in a day or two. > > > OK, I fixed the book. > Author: bdubbs > Date: 2009-05-20 09:55:19 -0600 (Wed, 20 May 2009) > New Revision: 7825 > > -<screen role="root"><userinput>ln -svf dash /bin/sh</userinput></screen> > + <note><para>If you create the symbolic link from <command>dash</command> > + to <command>sh</command>, you will need to reset the link to > + <command>bash</command> to build LFS. </para></note>
I'm not totally sure, but chapter-05 was build-able with dash as /bin/sh last time I've tried, so if there is another confirmation the above statement is not correct. > +<screen role="nodump"><userinput>ln -svf dash /bin/sh</userinput></screen> Also, though I don't have strong objection adding "nodump", but wouldn't be more logical to fix the root of the cause, by adding the $SHELL variable to Jhalfs, as Trent suggested? So it can possible catch other problematic situations that might occur for Jhalfs users? > -- Bruce Regards, Agathoklis. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
