Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
cp /etc/resolv.conf /mnt/gentoo/etc/resolve.conf is NOT right. /etc/resolve.conf minus the e is correct
Also:
cp -a /mnt/cdrom/packages /mnt/gentoo/urs/portage/packages
Should be /usr
As for the rest:
That's an OLD portage snapshot, that shouldn't matter though...
You may have to source /etc/profile first? Can you post up the exact message you are getting, an illegal action is far from something to go off of
Sorry. I messed up. You type those after chroot is done. I only mentioned them because MasterC did. Did you try to redo the steps MasterC pointed out? I also just noticed that you left the .tar.bz2 out of the stage tarball file name. What happened when you untarred the stage tarball? Did you actually untar it?
it just prints that out over and over and over...so i figure that since i already formatted the reiser partition in the unsuccessful installs before i probably could just skip it...but then i got to
mount /dev/hdc2 /mnt/gentoo
and it does the same things so whats up!? also will having the right resolv.conf fix the chrooting?
Ok. The first time I did a Gentoo installation (also 1.4 stage 3 GRP), I had to restart three or four times. It's actually very simple if you read the instructions carefully and make sure that you do everything correctly, but it can be really tricky. It's not necessarily the resolv.conf that messes up the change of the root directory (though it may well be). You have to do everything exactly right for it all to work.
I remember doing everything (and I mean everything) over when restarting the installation. I'm not sure if it's necessary or not, but I'm sure that it will work if you redo it all. If you got past the making of filesystems once, you can do it again. Are you going straight into filesystems, or are you fdisk-ing over? When I started over, I would delete all the partitions from the unsuccessful installation, re-create them and format them, just like the first time. So, try it again, following the instructions down to the letter, and see what happens.
That's strange. I'm no Gentoo Linux guru, so I'm not sure what to tell you based on your error message. As I understand it, you're able to mke2fs -j on your boot partition and mkswap on hdc4 (based on your previous list of commands), but you can't mkreiserfs on hdc2? I would try creating a different filesystem (ext3) on hdc2, just to see what happens. I really don't know what else to suggest. Maybe you could post your partition table here.
Yeah i tried that too...and it still doesn't work...the only thing i can think of would be a bad harddrive...but then it seems like teh other hdc partitions wouldn't work then...im really lost here
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.