chown....no such file or dir.

Dr.Swing · 10-07-2002, 03:44 PM

I have just successfully chroot'ed into my new LFS environment, but when I run the next command (chown -R 0:0 /static) I get an error......no such file or directory. I can't seem to access any bash commands except cd. Where to next ?

Tanks
Doc

lfslinux · 10-07-2002, 04:11 PM

Make sure $LFS/static/bin/chown is statically linked.

Dr.Swing · 10-07-2002, 05:10 PM

It looks like I'm already in the $LFS directory, which is now my / , and I can cd into static/bin, but I can't even do an ls to see what's there. I ran the "export LFS =/mnt/lfs" (I assume that's how you do the static linking) but still getting the error. I know very little about Linux but I hope that building this LFS will set me on my way.

Anyway I'll try again tomorrow evening, I'm heading for the cot now......I'll leave the system running.

Tanks
Doc

lfslinux · 10-07-2002, 05:19 PM

exit chroot, run this:

ldd $LFS/static/bin/ls

is it dynamically or statically linked?

Dr.Swing · 10-08-2002, 02:52 PM

When I exited chroot I got the following
logout
bash:exit: bad non-numeric arg 'chroot'
Then typing "ldd.....etc, i got the following result
librt.so.1 => /lib/librt.so.1 (0X40....)
libc.so.6 => /lib/libc.so.6 (0X40....)
libpthread.so.0 => /libpth... etc
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0X400...)

Don't know what it all means????

Tanks
Doc

lfslinux · 10-08-2002, 04:34 PM

all that from ldd means the program is not statically linked. It means that you did something wrong in chapter 5 and you need to redo the chapter. Read the book very careful and make sure you make no mistakes typing the comands. Sometimes typing a - wrong can cause the problems.

Dr.Swing · 10-08-2002, 04:42 PM

Ooops, back we go then.

Tanks Gerard
Doc