headers
Joshua Jackson | 1 Feb 2003 07:33

More patches - issue file fixes

Attached is a patch against the 1/31/2003 busybox CVS code for the following:

- Fixes syslogd to not die when a remote UDP host is unavailable
- Changes default hash to MD5 for passwd utility
- Ports TinyLogin's issue file handling to current busybox tree

The issue file was being dumped with the annoying LF but no CR stepping 
effect. This patch adds the issue file output routines from the original 
TinyLogin. This also adds several additional issue file tokens.

--
Joshua Jackson
http://www.coyotelinux.com
Attachment (bb-patch): text/x-diff, 7171 bytes
Permalink | Reply | 0 comments |
headers
Thomas Cameron | 1 Feb 2003 07:51

Re: Can't boot without graphic card

Oliver,
	If you use the previous suggestions, and either start a terminal/getty on a 
serial port, or if you tell your boot-loader that a specific serial port is 
your main console, then all will be well.  You simply attack another system 
via a serial "null modem" cable, open up your favorite serial terminal 
program, and you're good to go.

Sincerely,
Thomas Cameron
CEI Systems, Inc.

On Friday 31 January 2003 02:02 pm, Oliver Friedrich wrote:
> Ok, have found a solution...
> I have now included the serial port permanently (not as a module) and
> activated "console on serial port". Now the system doesn't reboot. This
> works for kernels 2.4.18 & 2.4.20 (others not tested).
>
> But where i can find now my keyboard input? I have a application, that
> normaly uses all input on /dev/tty1, but this doesn't work in the current
> setup (without vga card).
>
> Any Ideas?
>
> cu,
> Oliver
>
> > -----Original Message-----
> > From: Magnus Damm [mailto:damm <at> opensource.se]
> > Sent: Thursday, January 30, 2003 4:08 PM
> > To: Oliver Friedrich
(Continue reading)

Permalink | Reply | 1 comment |
headers
Oliver Friedrich | 1 Feb 2003 10:06
Picon
Favicon

RE: Can't boot without graphic card

Hi Thomas,
Thanks for your tip with the null modem cable, but this computer should be
"stand alone" ...

In fact it is a standard pc (P200MMX) in the case of an old cd player. I
have connected the keyboard controller out of an old keyboard to the
original buttons of the cd player (20 buttons are available).

The box now acts as a CD-Audio/MP3/(S)VCD/DVD-Player and a DVB-Receiver
and -Recorder. So it would be fine to control it via the buttons on its
front, too. LIRC is working fine.

It must be possible to use the input of an connected keyboard, even if there
is no locale console available. Is there a good (i mean: simple to
understand) programming howto available to get the keypresses from a
keyboard?
Perhaps it is possible for me to extend the application with something like
a "raw keyboard support". The 'init' of BusyBox makes it possible to start
the application with other parameters in the severall cases:
- with vga card and devfs support (consoles are named vc/[1..n])
- with vga card and no devfs support (consoles are named tty[1..n])
- without vga card (is this ttyS0 or ttyS1 as the console in the inittab?)

Thanks,
Oliver

> -----Original Message-----
> From: busybox-admin <at> busybox.net [mailto:busybox-admin <at> busybox.net]On
> Behalf Of Thomas Cameron
> Sent: Saturday, February 01, 2003 7:52 AM
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Bush | 2 Feb 2003 01:41
Favicon

Cannot chroot busybox

Compiled and built uClibc(i386) 0.9.17, and then built busybox 0.60.5
and when  i try to chroot it i get:

alpha busybox-0.60.5 # /usr/bin/chroot /home/mike/root/ /bin/sh
chroot: /bin/sh: No such file or directory

ldd gives me 
alpha busybox-0.60.5 # ldd ./busybox     
libc.so.0 => /usr/i386-linux-uclibc/lib/libc.so.0 (0x0x40006000)
ld-uClibc.so.0 => /usr/i386-linux-uclibc/lib/ld-uClibc.so.0
(0x0x40000000)

What am i doing wrong ?

Mike
Permalink | Reply | 3 comments |
headers
Tom Oehser | 2 Feb 2003 05:01
Favicon

There is no stdbool.h in gcc-2.7.2.3 ... um...


I'm trying to go to a newer busybox than I had been using on
tomsrtbt, which is compiled under libc5 with gcc-2.7.2.3.  I
pulled the newest CVS version, did 'make [menu]config', and,
well, got "expr.h:15: stdbool.h: No such file or directory".

I saw that some people had problems with conflicts, resolved
by updating ncurses, but that doesn't help me.  I need it to
check if there is a stdbool.h and use its own if that is not
present, or similar, so that it will work, with gcc-2.7.2.3.

-Thanks, -Tom
Permalink | Reply | 0 comments |
headers
Gene Cumm | 2 Feb 2003 05:24
Picon

Re: Cannot chroot busybox

Mike Bush wrote:
> Compiled and built uClibc(i386) 0.9.17, and then built busybox 0.60.5
> and when  i try to chroot it i get:
> 
> alpha busybox-0.60.5 # /usr/bin/chroot /home/mike/root/ /bin/sh
> chroot: /bin/sh: No such file or directory
> 
> ldd gives me 
> alpha busybox-0.60.5 # ldd ./busybox     
> libc.so.0 => /usr/i386-linux-uclibc/lib/libc.so.0 (0x0x40006000)
> ld-uClibc.so.0 => /usr/i386-linux-uclibc/lib/ld-uClibc.so.0
> (0x0x40000000)
> 
> What am i doing wrong ?

Are your libraries in that location also relative to the chroot, either 
copied in or hard linked (soft links to the real files won't work), ie 
does /home/mike/root/usr/i386-linux-uclibc/lib/libc.so.0 exist?  That's 
a common problem.

Next, does /home/mike/root/bin/sh exist and point to something like 
/bin/busybox or busybox (not /home/mike/root/bin/busybox)?
Permalink | Reply | 2 comments |
headers
John van Vlaaderen | 2 Feb 2003 05:58
Picon

Re: Cannot chroot busybox

Instead of chroot ( you do need all the libraries ) why not go the whole 
9 yards and kexec
to full reboot w/ a specified kernel running from an independent file 
system.   That way you are working directly on your final product.

BTW is there any repository of kernels or kernel config files that are 
commonly used by uClibc developers and integrators ??

On Saturday, February 1, 2003, at 11:24 PM, Gene Cumm wrote:

> Mike Bush wrote:
>> Compiled and built uClibc(i386) 0.9.17, and then built busybox 0.60.5
>> and when  i try to chroot it i get:
>> alpha busybox-0.60.5 # /usr/bin/chroot /home/mike/root/ /bin/sh
>> chroot: /bin/sh: No such file or directory
>> ldd gives me alpha busybox-0.60.5 # ldd ./busybox     libc.so.0 => 
>> /usr/i386-linux-uclibc/lib/libc.so.0 (0x0x40006000)
>> ld-uClibc.so.0 => /usr/i386-linux-uclibc/lib/ld-uClibc.so.0
>> (0x0x40000000)
>> What am i doing wrong ?
>
> Are your libraries in that location also relative to the chroot, either 
> copied in or hard linked (soft links to the real files won't work), ie 
> does /home/mike/root/usr/i386-linux-uclibc/lib/libc.so.0 exist?  That's 
> a common problem.
>
> Next, does /home/mike/root/bin/sh exist and point to something like 
> /bin/busybox or busybox (not /home/mike/root/bin/busybox)?
>
> _______________________________________________
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mike Bush | 2 Feb 2003 06:06
Favicon

Re: Cannot chroot busybox

John van Vlaaderen wrote:

> Instead of chroot ( you do need all the libraries ) why not go the 
> whole 9 yards and kexec
> to full reboot w/ a specified kernel running from an independent file 
> system.   That way you are working directly on your final product.
>
> BTW is there any repository of kernels or kernel config files that are 
> commonly used by uClibc developers and integrators ??
>

That is my goal. I am trying to create an install/boot cd with all my 
apps. ( using isolinux to boot ) but the kernel panics 'cannot find 
init',  so I am thinking that it cannot find the libs to run init.

Mike
Permalink | Reply | 0 comments |
headers
Gene Cumm | 2 Feb 2003 07:49
Picon

Re: Cannot chroot busybox

Mike Bush wrote:
> Creating a hard link solved the problem.
> 
> I had performed a make PREFIX=/home/mike/root install_target
> so uClibc was installed to /home/mike/root/lib, now why doens't BB find 
> the libs in their target install dir?

The lib paths are hardcoded into uClibc and subsequently all apps 
against uClibc.  See "SHARED_LIB_LOADER_PATH=" in .config or in `make 
menuconfig` etc.

> So let me get this straight, when I go to install this system on a fresh 
> computer, I have to have the development location dir on the target pc 
> or the libs will not be found? I don't want to put the development dir 
> on /lib on my delveopment machine, but on my target pc i wanted the libs 
> in /lib. Thats what I thought the install_target took care of.
> 
> Their is something im missing..

I think the above explains it.  Not sure a solution to solve it other 
than having say ./usr/i386-linux-uclibc/lib symlink to ./lib (relative 
to your chroot/project environment) or let the libs goto something like 
/uclibc and into ./uclibc.  Please read the README in your uClibc directory.

This is really a uClibc thing and not busybox for this issue.

<snip from other message>
 > That is my goal. I am trying to create an install/boot cd with all my
 > apps. ( using isolinux to boot ) but the kernel panics 'cannot find
 > init',  so I am thinking that it cannot find the libs to run init.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tom Oehser | 2 Feb 2003 23:02
Favicon

More problems with current cvs busybox on libc5 / gcc-2.7.2.3


So, I copied over the stdbool.h from a newer gcc, since it isn't
part of gcc-2.7.2.3, and got the newest ncurses, and now, I have
more problems, where it seems to insist on repeatedly re-running
config, and if I do a 'make dep', it fails with a: /bin/sh:
/usr/i386-linux-uclibc/bin/i386-uclibc-gcc: No such file or directory
no matter what I do, so far.  What am I missing?  The 0.60.5 works
fine still, but I had already gone to a .61-pre, I'll have to back
up to go back to 0.60.5,,,

-Tom
Permalink | Reply | 2 comments |

Gmane