stuck on chroot
Bill Maltby LFS Related
lfsbill at wlmlx1.wlmcs.com
Sat Mar 9 07:37:20 PST 2002
Minor, but yes. Printenv is an external binary. Export, set, readonly,
etc. are bash builtins. So, less overhead, flexibility, etc. But the
_significant_ difference is from the man page and execution results,
I can't tell which are exported. Exportation _is_ important in that
_by_default_, non-exported variables are _not_ passed to
So, if you have a construct like
LFS will _not_ be seen (or rather will be seen a LFS='', the
equivalent, sort of, of "unset LFS").
The most common way to assure that _all_ commands and subshells
see the needed vraiable's values is to export them. IIRC, the
book explicitly shows this being exported.
In my example, it would be
cd /mnt/hdc2;export LFS=`pwd`
- - O R - -
cd /mnt/hdc2;LFS=`pwd`;export LFS
There are also a couple of other clues to this behaviour in the book.
IIRC, something like
This does a "temporary" or "localized" export, assigning the value
and then passing the variable as part of the environment, which is
different than passing argumanets.
Well, I hope it's something as simple as this.
billm at wlmcs.com
On Sat, 9 Mar 2002, Paul Bailey wrote:
> On Fri, Mar 08, 2002 at 06:10:40AM -0500, Bill Maltby LFS Related wrote:
> > Let's take number 4 first. If you type export, do you see something
> > like "LFS=/mnt/hdc2" as example? If not, and if your originally
> > typed something like "chroot $LFS ...", that is probably your problem.
> > ...
> Just for my education: is there a difference between "export" and
> "printenv"? They seem to report the same data, although in a somewhat
> different format.
> paul.bailey at wanadoo.fr
> Unsubscribe: send email to listar at linuxfromscratch.org
> and put 'unsubscribe lfs-support' in the subject header of the message
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-support' in the subject header of the message
More information about the lfs-support