/usr/bin/ls missing following stage 1 emerge system

Mark Hobley wrote:
> I am installing Gentoo from stage 1. I have compiled the base system using:
>
> emerge system
>
> I now try to examine the kernel sources symlink:
>
> ls -l /usr/src/linux
> bash: /usr/bin/ls: No such file or directory
>
> Should this file exist?, or will it be a built-in command following reboot?

The default ls is part of sys-apps/coreutils, could be that you missed to
emerge it, or your $PATH is messed up and the file in question can't be found
by the system (did you run: source /etc/profile).

If you are missing coreutils, then use busybox,

busybox ls -l /usr/src/linux

if you do get the same error, then it's your $PATH which ain't up to date.

using the full path will be a temporary solution, but I suggest you run the
source command.

--

//Aho

J.O. Aho <user.TakeThisOut@example.net> wrote:

> The default ls is part of sys-apps/coreutils, could be that you missed to
> emerge it, or your $PATH is messed up and the file in question can't be found
> by the system (did you run: source /etc/profile).

Ok, following compilation of the base, I exit from the chroot environment, and
re-enter:

exit
exit
chroot /mnt/gentoo /bin/bash
env-update
source /etc/profile
export PS1="(chroot) $PS1"

ls -l /usr/bin/linux

Ok. It is working fine now. The rebuilt version must be using either a built
in command, or a different pathname. (Examining the box reveals that /bin/ls
exists so maybe the pathname changed.)

Mark.

--
Mark Hobley
393 Quinton Road West
QUINTON
Birmingham
B32 1QE

Email: markhobley at hotpop dot donottypethisbit com

http://markhobley.yi.org/

Mark Hobley wrote:

> source /etc/profile

> Ok. It is working fine now. The rebuilt version must be using either a built
> in command, or a different pathname. (Examining the box reveals that /bin/ls
> exists so maybe the pathname changed.)

There are some builds that will require you to run the 'source /etc/profile'
to get the shell back working. If I don't remember it wrong, some upgrades of
glibc and gcc can cause your trouble.
As you are working from a stage1 install, I guess when you run 'emerge system'
there was one/some upgrades that caused the problem, with later versions of
portage you will see all the important notes from the builds you done after
the emerges has finished, don't forget to read those notes.

--

//Aho

markhobley DeleteThis @hotpop.deletethisbit.com (Mark Hobley) writes:

>J.O. Aho <user DeleteThis @example.net> wrote:

>> The default ls is part of sys-apps/coreutils, could be that you missed to
>> emerge it, or your $PATH is messed up and the file in question can't be found
>> by the system (did you run: source /etc/profile).

>Ok, following compilation of the base, I exit from the chroot environment, and
>re-enter:

>exit
>exit
>chroot /mnt/gentoo /bin/bash
>env-update
>source /etc/profile
>export PS1="(chroot) $PS1"

>ls -l /usr/bin/linux

>Ok. It is working fine now. The rebuilt version must be using either a built
>in command, or a different pathname. (Examining the box reveals that /bin/ls
>exists so maybe the pathname changed.)

No, /bin is used for files which are crucial and should be available even
if the system is in single user mode, where /usr may be on another
partition and not even mounted. ls is one of those commands, as is mount,
and a variety of others (ls /bin/)

Unruh wrote:
> No, /bin is used for files which are crucial and should be available even
> if the system is in single user mode, where /usr may be on another
> partition and not even mounted. ls is one of those commands, as is mount,
> and a variety of others (ls /bin/)

What's the Gentoo concept of /sbin and /usr/sbin? I learned they were for
statically linked files, but out of 140 in my /sbin only four are statically
linked. /usr/sbin is worse, one of 262 is statically linked.

--
One meter, to within 0.0125% accuracy (off by just under .005 inches):
Three feet
Three inches
Three eights of an inch

clifto <clifto.RemoveThis@gmail.com> writes:

>Unruh wrote:
>> No, /bin is used for files which are crucial and should be available even
>> if the system is in single user mode, where /usr may be on another
>> partition and not even mounted. ls is one of those commands, as is mount,
>> and a variety of others (ls /bin/)

>What's the Gentoo concept of /sbin and /usr/sbin? I learned they were for
>statically linked files, but out of 140 in my /sbin only four are statically
>linked. /usr/sbin is worse, one of 262 is statically linked.

That is what sbin used to mean under Unix. Now it means programs which only
root should run. /sbin is programs which should be available always, even
before /usr is mounted, and /usr/sbin is otherwise.
Ie, /sbin and /usr/sbin should only be in root's path.

clifto wrote:
> Unruh wrote:
>> No, /bin is used for files which are crucial and should be available even
>> if the system is in single user mode, where /usr may be on another
>> partition and not even mounted. ls is one of those commands, as is mount,
>> and a variety of others (ls /bin/)
>
> What's the Gentoo concept of /sbin and /usr/sbin? I learned they were for
> statically linked files

As far as I know /sbin is for architecture-dependent and system administrative
tools and is used that way in most distros.


>, but out of 140 in my /sbin only four are statically linked.

Those shared libs using binaries uses libs in /lib, which should be located on
/ as /sbin. You have always busybox to fall back on, if you would break your
system so badly that the shared lib using programs in /sbin wouldn't work.


> /usr/sbin is worse, one of 262 is statically linked.

Those files aren't as system important as those in /sbin, and therefore can be
dynamically linked.




--

//Aho