From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx is really excellent, link it on the bell-labs pages?
Date: Thu, 1 Oct 2009 01:32:37 +0100 [thread overview]
Message-ID: <20091001013237.5682c17c.eekee57@fastmail.fm> (raw)
In-Reply-To: <4AC38D5C.1060900@maht0x0r.net>
On Wed, 30 Sep 2009 17:54:52 +0100
matt <maht-9fans@maht0x0r.net> wrote:
>
> > I've had "/bin/rc: not found" twice from Qemu with clean shutdowns
>
> I've also *just* had the disk go bad during the install to a qcow2 disk,
> at 90%+ too :(
>
> (or at least I think it went bad, I had lots of /n/newfs not found based
> errors)
>
> I started over with a raw disk instead
>
Owwwww! You know one thing.. I've had trouble getting qemu to build
in the past and ended up using qemu 0.9.1 long after 1.0 was out, and
it's rock solid. I've had no trouble from qemu at all. I think I'll
stick with 0.9.1 now! Oh btw the man pages for 0.9.1 seemed to imply
that qcow2 was really only to be used where the host OS doesn't
support holes. (Holes are long runs of 0, and can be stored as a
simple length.) Maybe it's not tested very well any more.
As to drawterm, I've held xorg-server back too. It's at 1.4.2, and
I'm having no trouble with drawterm. I really hate the careless
changes in recent xorg-server versions, several old-but-good functions
don't work right any more.
--
Ethan Grammatikidis
Those who are slower at parsing information must
necessarily be faster at problem-solving.
next prev parent reply other threads:[~2009-10-01 0:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 8:23 Sam Watkins
2009-09-30 14:45 ` David Leimbach
2009-09-30 15:30 ` Ethan Grammatikidis
2009-09-30 16:16 ` matt
2009-09-30 16:54 ` matt
2009-10-01 0:32 ` Ethan Grammatikidis [this message]
2009-09-30 16:55 ` ron minnich
2009-09-30 17:55 ` 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=20091001013237.5682c17c.eekee57@fastmail.fm \
--to=eekee57@fastmail.fm \
--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).