HELP! ls damaged

scott thomason scott at industrial-linux.org
Wed Jan 10 17:13:02 PST 2001


Yes, but I would bet it didn't work 100% and you didn't notice it in the reams of output. Or a library changed. Or ???
---scott

On Thu, 11 Jan 2001 02:10:30 +0100, Matthias Minich said:

> OK, did that. now it works again. but shouldn't it be compiled dynamically
>  from within the chrooted environment?
>  
>  thanks, matthias
>  
>  > > Matthias Minich wrote:
>  > > i think i have some serious problem. when hitting ls (in
>  > chrooted env.) i
>  > > get the following output
>  > >
>  > > root:/# ls
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > ls: : No such file or directory
>  > > root:/#
>  >
>  > Gerard Beekmans wrote:
>  >
>  > compile a static ls, put it on LFS, boot into LFS and see what
>  > that one does.
>  >
>  
>  
>  -- 
>  Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
>  and put unsubscribe in the subject header of the message
>  
>  


-- 
Unsubscribe: send email to lfs-discuss-request at linuxfromscratch.org
and put unsubscribe in the subject header of the message




More information about the lfs-dev mailing list