Re: [linuxdc-dev]Busybox behaviour

[Adrian M. <ad...@mc...>]

On Monday 31 Dec 2001 4:13 pm, M. R. Brown wrote:
> * Adrian McMenamin <ad...@mc...> on Mon, Dec 31, 2001:

> Do you have glibc installed in your NFS root environment?  Is busybox
> statically-linked?

Busybox is statically linked - I couldn't get init to work with it 
dynamically linked.

I had copied over libc, but then found that there was a dependency on libm. 
When I copied over all the library files - as per instructions on linuxsh.org 
I got a different error:

"./mpg123: error while loading shared libraries: libm.so.6: cannot open 
shared object file: No such file or directory"

I thought this was a PATH error, but even with PATH pointing to /lib I still 
have this problem? Is it something to do with the symlinks? The library is 
there...

>
> > I am using ASH as the shell.
> >
> > Finally - another question:
> >
> > On m17n using devfs I could do things like cat somefile > /dev/dsp
> >
> > But bb (again using devfs) insists on me writing cat somefile >
> > /dev/sound/dsp
> >
> > Why?
>
> The first is because the m17n distro created/maintained legacy device nodes
> (/dev/dsp).  You would have to manually create /dev/dsp and others if you
> *didn't* want to use devfs with busybox.
>

Thanks for this.

> M. R.