Unable to create directories

satimis · 07-01-2005, 10:03 PM

Hi folks,

Following
6.2. Mounting Virtual Kernel File Systems
http://www.sg.linuxfromscratch.org/l...06/kernfs.html

[satimis@localhost ~]$ su - lfs
Password:
lfs:~$ echo $LFS
/mnt/lfs
lfs:~$ mkdir -p $LFS/{proc,sys}

Code:

mkdir: cannot create directory `/mnt/lfs/proc': Permission denied
mkdir: cannot create directory `/mnt/lfs/sys': Permission denied

I was not allowed to create directories. Whether I have to login as "su -" on FC3 host first as follows,

[satimis@localhost ~]$ su -
Password:
[root@localhost ~]# cd /mnt/lfs/

then to proceed

[root@localhost lfs]# mkdir -p $LFS/{proc,sys}

OR on which directory (/mnt/lfs/sources/) to run that command line. Please advise. TIA

B.R.
satimis

CroMagnon · 07-02-2005, 12:40 AM

what does
ls -lA $LFS
show?

satimis · 07-02-2005, 01:45 AM

Hi CroMagnon,

Tks for your advice.

Quote:

what does
ls -lA $LFS
show?

[satimis@localhost ~]$ su - lfs
Password:
lfs:~$ ls -lA $LFS

Code:

total 32
drwx------   2 root root 16384 Jun  2 03:41 lost+found
drwxrwxrwt  34 lfs  root  4096 Jul  1 12:54 sources
drwxr-xr-x  16 lfs  root  4096 Jul  1 12:57 tools

Before I read;
6. Installing Basic System Software
http://www.sg.linuxfromscratch.org/l...chapter06.html

Note:-
The remainder of this book is to be performed while
logged in as user root and no longer as user lfs.

I was a little bid confused there. Whether I must login as "su -"
(some folks term it as "Super Root" - the System
Admin of FC3 host".)

Then cd /mnt/lfs"
lfs:~$
to proceed.

If after login as "su -" on the FC3 host, then to "su
- lfs" on FC3 host, it won't ask for LFS root's
password and continues to login as;
lfs:~$

Would it confuse the FC3 host? TIA

B.R.
satimis

CroMagnon · 07-02-2005, 03:15 AM

Damn, I meant for that to be a lower case 'a', but it doesn't matter as you've found the solution - you should be running these commands as root. I'm not sure what you're asking at the end, but when you create files as root, they will be owned by the user "number 0" (usually called root). There shouldn't be any confusion between the systems, as that user will be "number 0" in both systems. Once you get to step 6.3 and start using the chroot command, things should become a bit more clear.

satimis · 07-02-2005, 03:42 AM

Hi CroMagnon,

Tks for your advice. I'm clear now.

Quote:

I'm not sure what you're asking at the end, .......

Because I had some confusion whether login as

"su -" (the Super Root - Admin)

of the FC3 host would damage the later (FC3 host) while building LFS if anything goes wrong

B.R.
satimis

CroMagnon · 07-02-2005, 03:54 AM

Ahh, I see now. No, as long as you make sure you are in the chroot environment before you run anything, your FC3 host shouldn't be affected in any way. If you log out or reboot, be sure to rerun the chroot command before you continue with LFS.

satimis · 07-02-2005, 04:05 AM

Hi CroMagnon,

Quote:

make sure you are in the chroot environment before you run anything,....

Whether you meant to run

[satimis@localhost ~]$ su - lfs

first. Tks.

B.R.
satimis

CroMagnon · 07-02-2005, 04:15 AM

Nope, you shouldn't need the lfs user any more (but don't delete it yet, in case I've forgotten something). The instructions for the chroot command are in 6.3, and once you reach that point, you should always make sure you re-run that command (as root, not lfs) before continuing with your LFS instructions.

In other words:
1) From this point on, ALWAYS log in as root, never as lfs (unless told otherwise)
2) When you get to section 6.3, bookmark it, and re-run the chroot command any time you've had to log in to continue your build, right up until you get your LFS system to boot.

satimis · 07-02-2005, 04:48 AM

Hi CroMagnon,

Quote:

From this point on, ALWAYS log in as root, never as lfs (unless told otherwise)

Tks, I'm clear now, always;

[satimis@localhost ~]$ su -
Password: (enter FC3 host's Root password)
[root@localhost ~]#

staying here (for the rest of this Section unless instructed)

Quote:

2) When you get to section 6.3, bookmark it, and re-run the chroot command any time you've had to log in to continue your build, right up until you get your LFS system to boot.

Noted with thanks.

6.3. Entering the Chroot Environment
http://www.sg.linuxfromscratch.org/l...06/chroot.html

B.R.
satimis