From: "Sander van Dijk" <a.h.vandijk@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Booting problem after fresh install from 20080203 iso.
Date: Tue, 12 Feb 2008 14:26:01 +0100 [thread overview]
Message-ID: <ba0d3bc70802120526n43cc4e53x7598c7619c6a0459@mail.gmail.com> (raw)
In-Reply-To: <eae39cae24f7abbdd19cd5440e3f78cd@quanstro.net>
On Feb 12, 2008 1:50 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> > 1. I zeroed the target harddisk before installation like this: "dd -if
> > /dev/zero -of /dev/sdC1/data".
> > 2. I also accidentally did this first when I really meant to zero the
> > disk: "dd -if /dev/zero -f /dev/sdC1/raw".
>
> you did the right thing. the raw file is for issuing raw commands to
> the drive. (not raw like you're thinking. they're raw scsi commands
> which might be translated (loosely) into ata.) see scuzz(8).
I believe my writing turns out a bit unclear. What I meant to say was
that I actually did a "dd -if /dev/zero -f /dev/sdC1/raw" before I
figured out that it should have been "dd -if /dev/zero -of
/dev/sdC1/data" instead. Hence I was wondering if writing those zeroes
to the raw file could be the source of my problem (in case those
zeroes translate to a command I really shouldn't have given), because
this is one of the things I did right before the problem appeared.
Anyway, thanks for the reference, I'll take a look at scuzz(8).
Greetings, Sander.
next prev parent reply other threads:[~2008-02-12 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 20:19 [9fans] " Sander van Dijk
2008-02-05 23:24 ` [9fans] " Sander van Dijk
2008-02-12 8:20 ` Sander van Dijk
2008-02-12 9:19 ` lucio
2008-02-12 20:14 ` Sander van Dijk
2008-02-13 4:29 ` lucio
2008-02-13 13:41 ` erik quanstrom
2008-02-18 18:51 ` Sander van Dijk
2008-02-12 12:50 ` erik quanstrom
2008-02-12 13:26 ` Sander van Dijk [this message]
2008-02-12 13:36 ` erik quanstrom
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=ba0d3bc70802120526n43cc4e53x7598c7619c6a0459@mail.gmail.com \
--to=a.h.vandijk@gmail.com \
--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).