g uClibc? I only
> found one for the older Bering distro.
>
> Ricardo
> - Original Message -
> From: "Martin Hejl" <[EMAIL PROTECTED]>
> To: "Ricardo Kleemann" <[EMAIL PROTECTED]>
> Cc:
> Sent: Tuesday, February 28, 2006 10:14 AM
>
sday, February 28, 2006 10:14 AM
Subject: Re: [leaf-user] Re: Bering uClibc on a serial console
> Hi Ricardo,
>
> > It's great to know that lrp is simply a tgz. I never knew that! That
> > certainly helps.
> just make sure you're root while unpacking, editing and re
Hi Ricardo,
> It's great to know that lrp is simply a tgz. I never knew that! That
> certainly helps.
just make sure you're root while unpacking, editing and re-packing the
package - otherwise, the ownerships of the files will get screwed up
(which could create problems).
Martin
--
ehler" <[EMAIL PROTECTED]>;
Sent: Tuesday, February 28, 2006 7:13 AM
Subject: Re: [leaf-user] Re: Bering uClibc on a serial console
> Hello Ricardo,
>
> You can use the following "trick" if you have a linux PC:
> rename etc.lrp to etc.tar.gz
> unpack etc.tar.gz to a te
eemann" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>;
> Sent: Tuesday, February 28, 2006 6:41 AM
> Subject: Re: [leaf-user] Re: Bering uClibc on a serial console
>
>
>
>> Hello Ricardo,
>>
>>
>> Every Bering-uClibc kernel have serial support co
>;
Sent: Tuesday, February 28, 2006 6:41 AM
Subject: Re: [leaf-user] Re: Bering uClibc on a serial console
> Hello Ricardo,
>
> Every Bering-uClibc kernel have serial support compiled in, but you have
> to make sure you enable a getty on /dev/ttyS0 in /etc/inittab.
>
> In other
Hello Ricardo,
Every Bering-uClibc kernel have serial support compiled in, but you have
to make sure you enable a getty on /dev/ttyS0 in /etc/inittab.
In other words uncomment:
T0:23:respawn:/sbin/getty -L ttyS0 19200 vt100
You can comment the following lines:
#1:2345:respawn:/sbin/getty 38400 t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ricardo Kleemann wrote:
> Hi,
>
> I'm trying to install Bering uClibc on a net4501. It boots up but the
> problem I'm having is that it is not opening up a serial console connection.
> It attempts to open up /dev/tty1 and /dev/tty2, which fail (as e