sh: chroot: command not found

nehsa · 2004-11-30 14:45:50

I assume this is bad. I tried to installed bluefish with pacman -S bluefish and it seemed to install ok. When I tried to run it it said:

bluefish: error while loading shared libraries: libgnomevfs-2.so.0: cannot open shared object file: No such file or directory

So, following the advise of some people in the irc channel I did

pacman -Sy gnome-vfs

That when I saw the error in the title the first time. I finally tried to install the entire gnome group and it said that message:

sh: chroot: command not found

About every 5 or 6 packages. How do I fix that? And is that why bluefish isn't working?

Thanks!

skeeterbug · 2004-11-30 15:17:13

I don't know a lot about how pacman works but chroot is owned by coreutils and should be in /usr/sbin/chroot. If it's there then maybe your path has gotten messed up; if it's not there maybe try reinstalling coreutils? Once chroot gets straightened out try reinstalling gnome-vfs and bluefish. Hope this helps a bit, I'll be watching this thread to see what more knowledgeable people have to say.

[gsinglet@boise ~]$ pacman -Qo `which chroot`
/usr/sbin/chroot is owned by coreutils 5.2.1-4

nbcjr · 2005-06-07 02:46:32

i'm also getting this. fresh install.

nbcjr · 2005-06-17 16:59:08

my solution was to reinstall. everything is a-ok now.

koyi · 2005-08-15 07:15:28

Hi, I am totally new to Arch Linux and in fact I have just installed it and am still configuring it to my likings.

I encountered this same problem during the "Install Packages" and "Install kernel" stage in the installation. I used the base installation disc and did a FTP installation.

Why this happened, I think, is that there was no chroot in the base installtion disc. However, it did exist in /mnt/usr/sbin/.

Now my question is that, does this pose any dangers to my newly installed system? Will that be the same if I have used the full installation disc?

If chroot is important in installing packages, why is it not there in the base installtion disc?

Sorry for asking so many questions in my first post. But I hope someone will help clear my doubts.

Thanks.

paranoos · 2005-08-15 09:18:05

chroot must be on the disc, because it's used for installing grub or lilo to your hard drive.

hmmmmmmm i have a feeling anybody would have a hard time trying to explain this problem. :?

well, i've been using arch for well over a year, so i wouldn't think this is something common.

koyi · 2005-08-15 11:17:21

Thanks for the reply.

However, despite having those error messages, the system runs well as far as I know.

I would appreciate it if somebody else can give me an explanation, though.

cactus · 2005-08-15 14:33:11

/me scratches head
I know during my modification of the base iso (updating packages and so forth), I ran into a problem with a later version of pacman, and chroot...but that would not effect the base iso as it exists now..just modifications of it.

It is possible that the busybox instance didn't get setup properly during the boot of the cd..maybe a read error, or a flipped bit in memory somewhere. Other than something outlandishly weird like that, I have no idea..

koyi · 2005-08-15 15:02:40

Alright, I tried to install again with the full installation disc. And this time I looked properly into the problem.

After doing "install packages", I came to this "Installation Complete" screen with lots of names listed under "Targets:". When I scrolled down the page, there is something like a log of the installation, and I still see this somewhere:

sh: /usr/sbin/chroot: not found

and I tried to ls for /usr/sbin/chroot, it is not found. Then, I do "which chroot" and it happened that chroot is located under /usr/bin/chroot!!!

Is this a bug or is it something I have done wrong?

Anyway, I will try to re-install after linking /usr/sbin/chroot to /usr/bin/chroot and see if this error goes away. Will post a update here later.

koyi · 2005-08-15 15:28:01

Bingo!!! After linking /usr/sbin/chroot to /usr/bin/chroot BEFORE the package installation, the problem is gone!!! Although I don't know whether this is the proper solution or not. At least it works for now.

cactus · 2005-08-15 23:34:28

I had to recompile pacman to fix the chroot path issue on my base iso update, but I figured it was only a problem with later version of pacman. The chroot path is hardcoded into the pacman source (a security feature). The problem is that on the install cd (using busybox), /usr/sbin is reserved for add-on packages. I changed the pacman source and recompiled, so that the install cd remake that I made worked properly.

/me shrugs

Arch Linux

#1 2004-11-30 14:45:50

sh: chroot: command not found

#2 2004-11-30 15:17:13

Re: sh: chroot: command not found

#3 2005-06-07 02:46:32

Re: sh: chroot: command not found

#4 2005-06-17 16:59:08

Re: sh: chroot: command not found

#5 2005-08-15 07:15:28

Re: sh: chroot: command not found

#6 2005-08-15 09:18:05

Re: sh: chroot: command not found

#7 2005-08-15 11:17:21

Re: sh: chroot: command not found

#8 2005-08-15 14:33:11

Re: sh: chroot: command not found

#9 2005-08-15 15:02:40

Re: sh: chroot: command not found

#10 2005-08-15 15:28:01

Re: sh: chroot: command not found

#11 2005-08-15 23:34:28

Re: sh: chroot: command not found

Board footer