Search the Community
Showing results for tags 'chroot'.
Found 4 results
-
Hello everyone, I've been using Funtoo on my main desktop PC for quite some time. Now I'm expanding the family building a small (and "weak") NAS and I'd like to have the OS on a USB key, easy to move and clone. I created a chroot environment on the desktop and installed Funtoo inside it; it all went well, except that when I tried to compile a new kernel ( gentoo-sources-4.15.4 ) the modules_install phase fails: more specifically, depmod.sh fails. As consequence, apparently, the kernel fails to boot. I tried different methods: manual compilation, genkernel and genkernel-next, all with the same result. It worth mentioning that the two CPU are different, but both x86_64 and I modified the *FLAGS accordingly. The two errors are: ./scripts/depmod.sh: line 46: 6113 Illegal instruction "$DEPMOD" -b "$tmp_dir" $KERNELRELEASE 2> /dev/null *./scripts/depmod.sh: line 58: 6118 Illegal instruction "$DEPMOD" "$@" "$KERNELRELEASE" $SYMBOL_PREFIX I'm not too knowledgeable and couldn't find a hint from those. Thanks
-
Hello all, I am rusty enough with Unix/Linux to call myself a Newbie, I know enough to get myself in trouble. So I need to chroot into my funtoo installation so I can run: rc-update del xdm default However when looking at the commands for chroot on the install instructions and I try to run: mount /mnt/funtoo/ I get no such directory. So I am thinking it is because I am booted to "rescue" and then I try to run: mount /dev/sdb3/ /mnt/funtoo/ and I also got no such directory. I ran: mount /dev/sdb3/ / and it seemed to work but when I changed to / and looked around at some of the files and directories I found that I was looking at directories and files on the "rescue" Linux. I looked back in the instructions and they say: mkdir /mnt/funtoo mount /dev/sdb3 /mnt/funtoo However I do not want to create a new directory I want to mount what is already there, so I did not do that. As you can see I somewhat understand the commands and what I am doing but not really (my linux install is on sdb). I could use some help - even if it is "Hey you need to read this" - I will learn and want to learn. What got me here: Installing xfce4 after testing xwindows - the instructions say to edit /etc/conf.d/xdm and make these entries: DISPLAYMANAGER="<LightDM>" # rc-update add xdm default # rc-update add dbus default # rc Finished up with the other instructions - created power group and added root to it etc. rebooted and did not get my xfce session as expected so not knowing what I was doing, and I seem to remember from somewhere years ago that # in a config file = a comment, I ran the rc-update commands at the command prompt and rebooted now I am presented with a login screen and can get no where and cannot get a command prompt.
-
Hi there! I'm new to funtoo - to linux too to be honest... :-) I tried an installation according to the section "install" at the website. Everything worked until i came to the headline "chroot into Funtoo"; actualy in this part it's NOT mentioned how to chroot in the new system EXACTLY. I tried several approachses like "chroot /dev/sdc" because there would be my root directory, according to the previous steps.. But it doesn't work a bit. I searched the net but found nothing that helped me. Any suggestions? Thanks for your help angus71
- 5 replies
-
- 1
-
-
- installation
- error
- (and 1 more)
-
Is ubuntu 14.04 LTS a good live cd for a funtoo install?
maldoror posted a question in Installation Help
I tried installing funtoo from ubuntu and when it came time to chroot ubuntu would not recognize this command: env -i HOME=/root TERM=$TERM chroot . bash -l When I ran the previous command it echoed: env: chroot: No such file or directory And if I ran only the chroot portion of it it said something about illegal instruction and a core dumped. I thought maybe the problem was my stage tarball: intel64-sandybridge subarch, my processor is a Intel? Pentium® CPU G630 @ 2.70GHz ? 2 I think that was the right one. I'm completely lost as to what the problem is. I will try the install again with systemrescuecd, I'm worried it will be a waste of time if there is something wrong with the stage tarball.
