From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] usb/disk nvram and pxeload
Date: Sat, 26 Feb 2011 20:15:32 -0800 [thread overview]
Message-ID: <AANLkTinqh7nEKRk-HFCO6130Z-KijNNLpCbvNzGEcf1+@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimMN46BDskQRfLRNWVqnF1aTHgoUn3Ls+MKrBsH@mail.gmail.com>
That was the approach i was taking when ... ( i only need 512 bytes
after MBR, what could possibly go wrong?!) I destroyed some
memorabilia on that flash. Oh well; no big loss.
for some reason setting nvram='#u/usb/ep6.0/data" nvroff=513 (is it 0
or 1 origin?) nvrlen=512 didn't work. i guessed it might have been the
fact that usbd started usb/disk; i was getting device busy.
On Sat, Feb 26, 2011 at 6:41 PM, Gorka Guardiola <paurea@gmail.com> wrote:
> 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?
>>
>>
>
> On second thought, if you are only going to use it for nvram,
> you can cook something fast with bind slashn and aux/stub
> using the whole usb disk data file.
>
> --
> - curiosity sKilled the cat
>
>
next prev parent reply other threads:[~2011-02-27 4:15 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
2011-02-27 2:21 ` ron minnich
2011-02-27 2:41 ` Gorka Guardiola
2011-02-27 4:15 ` Skip Tavakkolian [this message]
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=AANLkTinqh7nEKRk-HFCO6130Z-KijNNLpCbvNzGEcf1+@mail.gmail.com \
--to=skip.tavakkolian@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).