mount -t proc proc /mnt/gentoo/proc and the new 1.4 CD

[jlowell]

OK, I'm using the new LiveCD to do a stage 1 install on yet another of my network's boxes. I unpack the tarball with no problem and move on to entering the installation. I run mount -t proc proc /mnt/gentoo/proc and get output mount point /mnt/gentoo/proc does not exist. Huh?

The instructions clearly call for this command. Might it be superfluous because I extracted the stage 1 tarball from the CD and not the web? I'm guessing. Never had this trouble with 1.4_rc4.

jlowell

[Cicero]

Sounds like you didn't unpack the tarball correctly. cd into /mnt/gentoo, ls, and then see if there's a proc directory. Also, I think the command should be mount -t proc /proc /mnt/gentoo/proc if you're in a directory other than /.

[jlowell]

Hi Cicero,

Well ls -la /mnt/gentoo gives no output proc. The command I used to unpack the tarball was tar -xvjpf /mnt/cdrom/stages/stage1-x86-20030726.tar.bz2 and it most verbosely unpacked. I'm quite sure the right command to use to enter the installation is mount -t proc proc /mnt/gentoo/proc, that's clear from the user docs. It looks to me that the directory /mnt/gentoo/proc was never created but we are not asked to create it.

jlowell

[azote]

did you run the extract command from the /mnt/gentoo directory?
_________________
contact me -> azote@mail.i2p

What do you want to emerge today?

if you think that a person is normal, it is because you do not know them well

[jlowell]

Hi azote,

Here's the series of commands I entered , in order, once I'd gotten my file systems created:

1. ls /mnt/cdrom/stages (This so as to get a look at the tarball's name)
2. cd /mnt/gentoo
3.tar -xvjpf /mnt/cdrom/stages/stage1-x86-20030726.tar.bz2 (It unpacked)
4. mount -t proc proc /mnt/gentoo/proc

I'm told there's no /mnt/gento/proc and that's true, there isn't. I can't explain this. For some reason that directory wasn't created. Bad data on the CD? I don't know, I'm speculating.

jlowell

[jlowell]

Thank you Cicero and azote for your messages. Since there's always a decent chance that some kind of mistake could have been made at this end without my realizing it - old grampa has been known to forget things more and more lately - I've decided to delete and recreate my partitions and try another time. If I run into this business again, though, I'll report it as a bug. Weird.

jlowell

[jlowell]

Well, this time I can get past the chroot. I'm doing an emerge sync at the moment!

While I can't account for what happened last night with absolute certainty, it's beginning to look to me like a another "senior moment"

Apologies for any inconvenience.

jlowell

[r0nster]

it's mount -o bind /proc /mnt/gentoo/proc
Forgive me if the typing of this post may look funny, I'm posting via links from the console (bootstrapping 1.4!!)

[Cicero]

r0nster, I think you're right. In fact, I think that's what it used to be in the install docs. I don't know why it was changed to its current form. For me, any of the above work, so I don't think it matters.

[Sven Vermeulen]

No need to bindmount partitions, "mount -t proc proc /mnt/gentoo/proc" should work.