From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Jesse Dyson <jesse@winston-salem.com>,
Klaus Naumann <spock@mgnet.de>,
linux-mips@oss.sgi.com
Subject: Re: Indigo2 Kernel Boots!!!
Date: Fri, 1 Dec 2000 00:59:42 +0100 [thread overview]
Message-ID: <20001201005942.A6172@bacchus.dhis.org> (raw)
In-Reply-To: <00f601c05ae8$19014500$0deca8c0@Ulysses>; from kevink@mips.com on Thu, Nov 30, 2000 at 05:10:32PM +0100
On Thu, Nov 30, 2000 at 05:10:32PM +0100, Kevin D. Kissell wrote:
> When the init process fires up, it opens /dev/console as the
> console output device. A default SGI workstation installation
> file system will have /dev/console bound to the major/minor device
> node of the graphics display console. If you want to run with a serial
> console, you must therefore change this to bind /dev/console
> to the serial port. You can do this by doing an explicit mknod,
> or by linking to the appropriate serial port device node,
> which is usually /dev/ttyS0.
Which both are wrong. /dev/console should be a char device major 5, minor 1.
There is no need to change this ever except for very old kernels. With 2.2
or 2.4 whenever people change /dev/console's major/minor it's usually painting
over some bug.
Ralf
next prev parent reply other threads:[~2000-12-01 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 6:48 Indigo2 Kernel Boots!!! Jesse Dyson
2000-11-30 7:53 ` Klaus Naumann
2000-11-30 14:41 ` Jesse Dyson
2000-11-30 15:56 ` Keith M Wesolowski
2000-11-30 16:10 ` Kevin D. Kissell
2000-11-30 16:10 ` Kevin D. Kissell
2000-11-30 23:59 ` Ralf Baechle [this message]
2000-12-01 7:22 ` Kevin D. Kissell
2000-12-01 7:22 ` Kevin D. Kissell
2000-12-01 15:33 ` Harald Koerfgen
2000-12-01 17:53 ` Ralf Baechle
2000-12-01 18:15 ` console knowledge Gordon McNutt
2000-12-02 1:53 ` Ralf Baechle
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=20001201005942.A6172@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=jesse@winston-salem.com \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=spock@mgnet.de \
/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