From: Karsten Merker <karsten@excalibur.cologne.de>
To: Marc Karasek <marc_karasek@ivivity.com>
Cc: Jun Sun <jsun@mvista.com>, linux-mips@oss.sgi.com
Subject: Re: busybox does not like 2.4.8, or the other way around?
Date: Wed, 26 Sep 2001 18:47:10 +0200 [thread overview]
Message-ID: <20010926184710.D348@excalibur.cologne.de> (raw)
In-Reply-To: <25369470B6F0D41194820002B328BDD2195AA2@ATLOPS>; from marc_karasek@ivivity.com on Wed, Sep 26, 2001 at 11:53:39AM -0400
On Wed, Sep 26, 2001 at 11:53:39AM -0400, Marc Karasek wrote:
[busybox does not react to a keypress]
> Yes, there was a bug in busybox that caused this. I helped track it down a
> few months ago and it should be fixed in the latest one. I have attached an
> email about the bug. What version(s) of busybox are you using?
busybox 0.60.1-2 (current version from Debian/Sid)
> > I'm using busybox as init/getty/shell.
> >
> > Everything works fine with 2.4.2.
> > With 2.4.3 console output is fine but not input.
Hm, this seems to be another problem - 2.4.3 and 2.4.5 work fine for me,
anything newer than 2.4.5 does not. I suppose we have a kernel problem
after 2.4.5 as kernels newer than 2.4.5 completely crash on a DECstation
sooner or later during bootup.
Greetings,
Karsten
--
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.
next prev parent reply other threads:[~2001-09-26 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 15:53 busybox does not like 2.4.8, or the other way around? Marc Karasek
2001-09-26 16:47 ` Karsten Merker [this message]
2001-09-26 17:26 ` Jun Sun
2001-09-26 21:56 ` Geoffrey Espin
2001-09-27 17:21 ` Jun Sun
-- strict thread matches above, loose matches on Subject: below --
2001-09-21 1:21 Jun Sun
2001-09-21 2:02 ` Bradley D. LaRonde
2001-09-21 2:02 ` Bradley D. LaRonde
2001-09-21 3:56 ` Ralf Baechle
2001-09-21 5:30 ` Karsten Merker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010926184710.D348@excalibur.cologne.de \
--to=karsten@excalibur.cologne.de \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=marc_karasek@ivivity.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox