Problem in running "ln -s $LFS/tools /"

Stephen Liu satimis at yahoo.com
Tue Jun 28 04:20:10 PDT 2005


Hi Steve,

Tks for your advice.

- snip -

> When you "su" you load a new environment, and your
> $LFS variable is
> lost, so the chown is attempting to access /sources,
> instead of
> /mnt/lfs/sources.
> 
> do a "export LFS=/mnt/lfs" and run the chown again.

Continued proceeding as follows;

# export LFS=/mnt/lfs
# chown lfs $LFS/tools
# chown lfs $LFS/sources
both went through without complaint

# su - lfs
-bash-3.00$ 


-bash-3.00$ cat > ~/.bash_profile << "EOF"
> exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ '
/bin/bash
> EOF
-bash-3.00$ cat > ~/.bashrc << "EOF"
> set +h
> umash 022
> lFS=/mnt/lfs
> LC_ALL=POSIX
> PATH=/tools/bin:/bin:/usr/bin
> export LFS LC_ALL PATH
> EOF
-bash-3.00$ source ~/.bash_profile
bash: umash: command not found
lfs:~$  

Up to here I have no idea whether I have committed any
mistake because no indication of success.

What is "bash: umash: command not found"?  Is it a
WARNING?

B.R.
Stephen



More information about the lfs-support mailing list