[Buildroot] link to busybox

[Buildroot] link to busybox

[Tiju Jacob]

Hi all,

I am using buildroot for an arm board. 

Is it common to have all my executables as links to busybox?

eg.
-rwsr-xr-x 216 tiju users 589352 May  6 10:30 freeramdisk -> ../bin/busybox
-rwsr-xr-x 216 tiju users 589352 May  6 10:30 fsck -> ../bin/busybox
-rwsr-xr-x 216 tiju users 589352 May  6 10:30 getty -> ../bin/busybox
-rwsr-xr-x 216 tiju users 589352 May  6 10:30 halt -> ../bin/busybox
-rwsr-xr-x 216 tiju users 589352 May  6 10:30 hdparm -> ../bin/busybox
-rwsr-xr-x 216 tiju users 589352 May  6 10:30 hwclock -> ../bin/busybox

The issue I am facing is that I am not able to get the shell prompt. It keeps on respawning the getty when I try to login.

Thanks in advance.
Tiju


      Meet people who discuss and share your passions. Go to http://in.promos.yahoo.com/groups/bestofyahoo/

[Buildroot] link to busybox

[Thiago A. Corrêa]

>
>  I am using buildroot for an arm board.
>
>  Is it common to have all my executables as links to busybox?

Yes, that's how busybox works, it's a single binary file for all the
tools, so it shares code and reduces total size.

>  The issue I am facing is that I am not able to get the shell prompt. It keeps on respawning the getty when I try to login.
>

I don't use arms, but AVR32 instead. I had a similar issue a while
back and it was something to do with bash, once I removed bash from
the build, everything worked ok. You might want to try that.

Kind Regards,
   Thiago A. Correa

[Buildroot] link to busybox

[Christian SCHWARZ]

The respawn problem typically is not related to a specific shell, but 
either to a misconfiguration of the /etc files (especially rc.S) or, 
more probable, missing /dev/tty??
You might want to check those messages.
In my case, I had to add several special devices by hand, not added by 
buildroot (and I also replaced all the files in /etc with a single rc.S 
one, which resolved several other problems). The platform is an ARMv6 board.

cheers,
Christian

Thiago A. Corr?a wrote:
>>  I am using buildroot for an arm board.
>>
>>  Is it common to have all my executables as links to busybox?
> 
> Yes, that's how busybox works, it's a single binary file for all the
> tools, so it shares code and reduces total size.
> 
>>  The issue I am facing is that I am not able to get the shell prompt. It keeps on respawning the getty when I try to login.
>>
> 
> I don't use arms, but AVR32 instead. I had a similar issue a while
> back and it was something to do with bash, once I removed bash from
> the build, everything worked ok. You might want to try that.
> 
> Kind Regards,
>    Thiago A. Correa
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
> 

[Buildroot] link to busybox

[Tiju Jacob]

Hi Christian,

> The respawn problem typically is not related to a specific shell, but 
> either to a misconfiguration of the /etc files (especially rc.S) or, 
> more probable, missing /dev/tty??
> You might want to check those messages.

What kind of tty? My serial device ttySAC0 is present in /dev.

> In my case, I had to add several special devices by hand, not added by 
> buildroot

What type of devices? I may also be missing these devices.

>(and I also replaced all the files in /etc with a single rc.S one, 
>which resolved several other problems). The 
>platform is an ARMv6 board.
 
I am very new to this. Could you please tell me how to modify these files to my requirement or atleast the links from where I will get more information regarding this?

Thanks in advance.
Tiju



      From Chandigarh to Chennai - find friends all over India. Go to http://in.promos.yahoo.com/groups/citygroups/

[Buildroot] link to busybox

[Christian SCHWARZ]

Hi Tiju,

I believe root filesystems are not an exact science, thus I can only 
provide you with some generic stuff, which mostly works.
For me, a simple device layout like the following (using busybox or 
buildroot) works on several different embedded platforms:

mknod initrd b 1 250
mknod console c 5 1
mknod mem c 1 1
mknod null c 1 3
mknod ram1 b 1 1
mknod ttyAM0 c 204 16
mknod ram0 b 1 0
ln -s ram1 ram
ln -s ram0 ramdisk

In your case you'd probably replace ttyAM0 with ttySAC0..

> I am very new to this. Could you please tell me how to modify these files to my requirement or atleast the links from where I will get more information regarding this?
Even though this is the buildroot mailing list, I would recommend to 
first try a rootfs with only busybox, thus without buildroot. You can 
easily use the buildroot-generated cross-compiling toolchain with busybox..
  make CROSS_COMPILE=<xtoolchain-prefix> all install

The rc.S file is not required by busybox, it makes some smart assumptions.

hope this helps,
Christian