From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] pxe booting net4801
Date: Wed, 22 Sep 2010 01:57:56 -0400 [thread overview]
Message-ID: <64d1f9e3f2581835c1fb570d027ca877@brasstown.quanstro.net> (raw)
In-Reply-To: <20100922055538.GB18297@chiron.galaxy>
> No, because the plan9.ini manpage seems to indicate that the default
> is b9600 l8 pn s1 (which is also how I used it with Linux and
> OpenBSD). Is the kernel expecting 19200 baud being used by default?
no, the plan 9 default is 9600 baud.
- erik
next prev parent reply other threads:[~2010-09-22 5:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 21:41 frank
2010-09-22 3:29 ` erik quanstrom
2010-09-22 5:55 ` frank
2010-09-22 5:57 ` erik quanstrom [this message]
2010-09-22 20:01 ` frank
2010-09-22 21:09 ` erik quanstrom
2010-09-22 21:23 ` David du Colombier
2010-09-23 1:11 ` erik quanstrom
2010-09-23 6:31 ` David du Colombier
2010-09-23 13:11 ` erik quanstrom
2010-09-23 8:19 ` David du Colombier
2010-09-23 12:59 ` erik quanstrom
2010-09-23 13:51 ` David du Colombier
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=64d1f9e3f2581835c1fb570d027ca877@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).