permission denied installing tar-1.14 at chapter 5.27

status1 · 10-29-2006, 02:38 PM

Hello,
I am working on building my first lfs with the lfs 6.0 book and cd.
I made it to chapter 6 earlier but I had a problem so I started from scratch.
I made it to chapter 6.9 when I realized that I must have skipped over the tar installation because it was not in the
/tools/bin
I thought it should have been simple just to login as lfs
user and instal tar but when I got to "make install"
I got an error /tools/bin/install : cannot create regular file '/tools/bin/tar': Permission denied
I know this installation worked before because I did not have any errors but now that I made it to chapter 6 and
I changed to user root I am thinking that even if I am user
lfs it's not allowing me to make any changes to /tools/bin
It's a bit strange because if I type ls -ld /mnt/lfs/tools
I get drwx-xr-x 16 lfs root 4096
But if I type ls -ld /mnt/lfs/tools/bin I get
drwx-xr-x 2 root root 4096

It looks like the /bin directory does not have the same
user as /tools.
Is there a way to make the /bin have the same privilages as the /tools ?

zhangmaike · 10-29-2006, 04:17 PM

Quote:

Is there a way to make the /bin have the same privilages as the /tools ?

See man chown.

Assuming you mean /tools/bin:

Code:

# chown lfs:root /tools/bin

Will make /tools/bin owned by the user lfs and group root.

status1 · 10-29-2006, 06:43 PM

Hello,
Thanks for the reply but it did not do what I thought it would
I changed the command to chown lfs:root /bin because that is what I have problem with.
I had to be su to be able to do it but even after saying that/bin has lfs
ownership after typing ls -l I still get drwx-xr-x 2 root root 4096
If I try chmod command on /bin I get
Chmod: changing permissions of '/bin' : Read only file system
How can it be read only if I just created it not long ago ?

zhangmaike · 10-29-2006, 07:35 PM

Could you post the output of:

Code:

mount

status1 · 10-30-2006, 06:04 PM

Hello,
Here is the output for mount
rootfs on / type rootfs (rw)
proc on /proc type proc (rw, nodiratime)
sysfs on /sys type sysfs (rw)
/dev/hdc on ./cdrom type iso9660 (ro)
none on /dev type ramfs (rw)
none on /dev/pts type devpts (rw)
none on /de/shm type tmpfs (rw)
/dev/loop0 on /usr /type squashfs (ro)
/dev/loop1 on /opt type squashfs (ro)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/fd0 on /mnt/floppy type ext2 (rw)
/dev/hda7 on /mnt/lfs type ext2 (rw)

zhangmaike · 10-31-2006, 03:38 PM

It doesn't look like /bin resides on a read-only file system.

If you want /bin to be owned by the user lfs and group root, chown is the command to use. I'm surprised that it's not working.

Just to make sure that you're doing what I think you're doing, could you post the output of the following commands as you run them, in order:

Code:

$ su
# chown lfs:root /bin
# exit
$ mount

status1 · 10-31-2006, 06:37 PM

Hello,
I assume I am running those commands from the lfs environment

su
root:/home/lfs #
chown lfs:root /bin
I had no output for this but I tried it with the -v and it said that ownership
of /bin was retained by lfs
exit gets me back to lfs environment

Correct me if I am wrong but I don't think the mount will show the /bin directory itself as being mounted
The output is the same as before
I tried the /bin directory but I still don't have permission to write while I am inside the lfs environment

status1 · 10-31-2006, 07:06 PM

Hello,
I am not sure if this is the right way to do it but I found a way.

I found out by looking at the passwd in /etc that lfs has the uid of 1002
and gid of 101
So then I went inside chroot and typed chown -R 1002:101 /tools then I checked the /bin and I saw that it finally changed to lfs.
Then I was able to install tar with no problems.
After that I went back into chroot to change back the chown command to the original that was in the book
I just hope everything is back the way it should be and not have some other
unforseen consequences later on