9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Gorka Guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] usb/disk nvram and pxeload
Date: Sun, 27 Feb 2011 03:07:29 +0100	[thread overview]
Message-ID: <AANLkTimON4z5HZQbowcd6p5_UBG+uuqUGbeyW0NM=7rq@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=pq9ASxa5y53f2HUQ+6amvMmCCqAAwN-gzyns+@mail.gmail.com>

On Sun, Feb 27, 2011 at 1:38 AM, Skip Tavakkolian
<skip.tavakkolian@gmail.com> wrote:
> if i pxeload a cpu and want to be able to use an nvram partition on a
> usb disk (i.e. nvram=/dev/sdXX/nvram - once it is partitioned &
> formated). it seems i also must change boot/boot.c to add the 'partfs
> && fdisk -p && prep -p' after usbd has started. is this correct?
>
>

There are two alternatives.
Be wary, I am writing this by looking at the manual and from
what I remember from the code, but they should be *almost* right.

One is run
usb/usbd
mount /srv/usb /n/usb
#now you have /n/usb/sdU0.0 for example there
#here there are two alternatives, you can use partfs or fs, depending
#on your needs.

#with partfs *simpler but slower*
disk/partfs /n/usb/sdU0.0
cd /dev/sdXX
disk/fdisk -p data > ctl
disk/prep -p plan9 > ctl

#alternatively to partfs
#with fs
{
    echo disk sdXX 512 /n/usb/sdU0.0/data
   disk/fdisk -p /n/usb/sdU0.0/data
   disk/prep -p /n/sdXX/plan9

} > /dev/fs/ctl


G.

--
- curiosity sKilled the cat



  reply	other threads:[~2011-02-27  2:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-27  0:38 Skip Tavakkolian
2011-02-27  2:07 ` Gorka Guardiola [this message]
2011-02-27  2:21 ` ron minnich
2011-02-27  2:41 ` Gorka Guardiola
2011-02-27  4:15   ` Skip Tavakkolian
2011-02-27  8:51     ` Gorka Guardiola
2011-02-27 16:49       ` Skip Tavakkolian

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='AANLkTimON4z5HZQbowcd6p5_UBG+uuqUGbeyW0NM=7rq@mail.gmail.com' \
    --to=paurea@gmail.com \
    --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).