public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: miquels@cistron-office.nl (Miquel van Smoorenburg)
To: linux-kernel@vger.kernel.org
Subject: Re: serial console and kernel 2.4
Date: Mon, 30 Jul 2001 20:59:51 +0000 (UTC)	[thread overview]
Message-ID: <9k4hs7$m7u$1@ncc1701.cistron.net> (raw)
In-Reply-To: <20010730165453.A19255@pc8.lineo.fr> <20010730223632.B82B.GAUTIER@email.enst.fr>

In article <20010730223632.B82B.GAUTIER@email.enst.fr>,
Fabrice Gautier  <gautier@email.enst.fr> wrote:
>> Is there something that I'm missing ? (something new with the kernel 2.4
>> that is required for a serial console that was not required with the 2.2 ?)
>
>It's probably a bug in your init.
>I had the same, my init is busybox init, but maybe the sysv init has/had
>the same problem.

It has, was fixed in 2.80 which I put on
ftp.cistron.nl/pub/people/miquels/software/ a few days ago.

It's probably wise to wait for your vendor to ship a new sysvinit
package, or for all I know some vendors might have patched 2.78 already.

Mike.
-- 
"dselect has a user interface which scares small children"
	-- Theodore Tso, on debian-devel


  reply	other threads:[~2001-07-30 21:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 14:54 serial console and kernel 2.4 christophe barbé
2001-07-30 15:18 ` baettig
2001-07-30 15:33   ` christophe barbé
2001-07-30 15:19 ` Steve Hill
2001-07-30 20:43 ` Fabrice Gautier
2001-07-30 20:59   ` Miquel van Smoorenburg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-30 15:20 James Bottomley
2001-07-30 15:37 ` christophe barbé
2001-07-30 15:53   ` Stuart MacDonald
2001-07-30 16:21     ` christophe barbé
2001-07-30 16:55       ` Chris Wedgwood
2001-07-30 20:36         ` Thomas Duffy
2001-07-30 21:41           ` Chris Wedgwood
2001-07-30 22:24             ` Miquel van Smoorenburg
2001-07-31  7:51               ` christophe barbé
2002-01-16 14:29 Eric Lamarque

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='9k4hs7$m7u$1@ncc1701.cistron.net' \
    --to=miquels@cistron-office.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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