Re: 6.28. Bash-3.2 and exec /bin/bash --login +h

2007-09-02 Thread Trent Shea
On Sunday 02 September 2007 10:42, Dan Nicholson wrote: > 2. is a little more sensible to me, but only because I know > of a very simple way to create the markers. I like that; a lot more flexible than my initial idea of copying the running script, doing a sed, and then running the new script. T

Re: 6.28. Bash-3.2 and exec /bin/bash --login +h

2007-09-02 Thread Dan Nicholson
On 9/2/07, Trent Shea <[EMAIL PROTECTED]> wrote: > On Sunday 02 September 2007 08:45, Dan Nicholson wrote: > > It depends what you do with your script and if you keep some kind of > > progress marker so that the newly invoked script knows where to pick > > up. > That's going to be the tricky part.

Re: 6.28. Bash-3.2 and exec /bin/bash --login +h

2007-09-02 Thread Trent Shea
On Sunday 02 September 2007 08:45, Dan Nicholson wrote: > It depends what you do with your script and if you keep some kind of > progress marker so that the newly invoked script knows where to pick > up. That's going to be the tricky part. The only ideas I've had so far are: 1. Somehow pause the

Re: compiling samba with pam, but it's not finding the libraries

2007-09-02 Thread Randy McMurchy
Alan wrote: > -bash-3.1$ locate libpam | tail > /usr/lib/libpam.la > /usr/lib/libpam.so > /usr/lib/libpamc.la > /usr/lib/libpamc.so > /usr/lib/libpam_misc.la > /usr/lib/libpam_misc.so Seems to me that libpam.so is just a symlink to the actual library, which doesn't show up in your locate commmand

Re: chroot error

2007-09-02 Thread Dan Nicholson
On 9/2/07, Boovarahan (Sridhar) <[EMAIL PROTECTED]> wrote: > > lfs live cd rc2032 - chapter 6.4 "entering the chroot environment - > command "chroot "$LFS" /tools/bin/env -i \ > HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \ > PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ > /tools/bin/bash --login +h"

Re: 6.28. Bash-3.2 and exec /bin/bash --login +h

2007-09-02 Thread Dan Nicholson
On 9/2/07, Trent Shea <[EMAIL PROTECTED]> wrote: > On Sunday 02 September 2007 08:00, Dan Nicholson wrote: > > That's fine. I use the temp bash all the time to do the final build. > That's good to hear; the only difference I noticed was that the second > bash was compiled to use the readline we ins

Re: chroot error

2007-09-02 Thread Trent Shea
On Sunday 02 September 2007 07:42, Boovarahan (Sridhar) wrote: > Plz help me to proceed further. Did you deviate from the book at all? Like, trying to use a link at /mnt/lfs/tools? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubs

Re: 6.28. Bash-3.2 and exec /bin/bash --login +h

2007-09-02 Thread Trent Shea
On Sunday 02 September 2007 08:00, Dan Nicholson wrote: > That's fine. I use the temp bash all the time to do the final build. That's good to hear; the only difference I noticed was that the second bash was compiled to use the readline we install in chapter 6, and I wasn't sure if anything depend

Re: 6.28. Bash-3.2 and exec /bin/bash --login +h

2007-09-02 Thread Dan Nicholson
On 9/1/07, Trent Shea <[EMAIL PROTECTED]> wrote: > Does anyone know of any problems that could creep in if I > skip "exec /bin/bash --login +h" and continuing to use the bash built > in chapter 5 until I'm done chapter 6? I ask because I have no idea how > to pass control of a running script to the

chroot error

2007-09-02 Thread Boovarahan (Sridhar)
Hi ! lfs live cd rc2032 - chapter 6.4 "entering the chroot environment - command "chroot "$LFS" /tools/bin/env -i \ HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \ PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \ /tools/bin/bash --login +h" gives the following msg: chroot: cannot run command `/tools/bin