From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [absolute newbie] Problems with Riva TNT
Date: Mon, 1 Dec 2003 06:53:15 -0700 [thread overview]
Message-ID: <c4759d66bec090a7202337517fdb2b04@plan9.ucalgary.ca> (raw)
In-Reply-To: <18ae804a.0311270906.1354ef15@posting.google.com>
sadly the only way you can get a new kernel in requires either to use
'ed' (the standard editor when rio isn't running) or boot from the
disk and work a bit of magic to get a new kernel from
sources.cs.bell-labs...
this really should've been fixed in the default installation. the
change appears to be there (> 0x20 -> >= 0x20) but depending on which
kernel you're booting you may be using sources as far back as Dec
15th, 2002.
email me privately and I'll walk you through building a new kernel
without using rio..
i'll probably add it to the wiki too.
andrey
next prev parent reply other threads:[~2003-12-01 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 11:06 Richard Hunt
2003-12-01 13:53 ` mirtchov [this message]
2003-12-02 7:31 cej
2003-12-02 16:11 ` Russ Cox
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=c4759d66bec090a7202337517fdb2b04@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/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).