On Sat, Apr 12, 2008 at 1:49 PM, J. Greenlees <[EMAIL PROTECTED]> wrote: > > Dan Nicholson wrote: > > On Fri, Apr 11, 2008 at 11:49 PM, J. Greenlees > > <[EMAIL PROTECTED]> wrote: > > > >> Dan Nicholson wrote: > >> > >> > bash - Not needed for actual building, but glibc's ldd and tzselect > >> > need either bash or ksh to work. The values will be substituted at > >> > configure time. I don't know what happens without them, and it's > >> > probably not that important in Ch. 5 if those utilities aren't there. > >> > However, we create the LFS user with /bin/bash as the login shell, and > >> > this can't be substituted as is because we set up the environment > >> > through the bash initialization files. > >> > > >> > >> Yet another minor issue with PCLinuxOS as a build environment, the > >> environment set up following the book is not a login shell. > >> [ only mentioning it as a f.w.i.w. ] > >> > > > > Sure it is. You switch to the lfs user with `su - lfs'. That creates a > > login shell using the shell listed in the passwd database. If > > PCLinuxOS' su doesn't follow that trend, I don't know if there's a lot > > we can do about that. > > > > -- > > Dan > > > And even the LFS Livecd will toss a "Not a login shell, try exit > instead" when given a logout. > I rarely get more than an hour or two to actually work on a build in one > session, so I always wind up having to end a session, or I wouldn't have > noticed.
That's only a side effect of what we actually do with the login shell in ~lfs/.bash_profile. Since we take the login shell and exec a regular bash with a very clean environment, then, yes, you are no longer in a login shell. However, you have reached that state only as a result of starting in a login shell for the lfs user. http://www.linuxfromscratch.org/lfs/view/development/chapter04/settingenvironment.html -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
