From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Install: root file system
Date: Sat, 2 Jan 2016 16:26:39 -0800 [thread overview]
Message-ID: <be9e8c90c529b93fd0159e9675a06ed6@mule> (raw)
In-Reply-To: <20160102115515.GA498@polynum.com>
i'm not sure what the root cause of your problem is, due to not enough data,
but it does remind me of a limitation that has been bugging me.
to boot from usb cleanly, i added a bit to the boot process that creates a loopback
sd device /dev/sdu0 that points to the usb disk device. i've been booting my auth
server this way for some time.
it seems to me that i really screwed this up. what i really want is a sd device
that always points to the boot drive, the one bios refers to as 0x80.
givem this, one can then put something like "bootargs=local!#S/sdB0/fs"
in plan9.ini. this will allow the 9atom usb install image to run off any bootable
media (for which we have drivers).
so, i'm preparing a patch that will present the boot device as /dev/sdB0 regardless
of what underlying disk driver or protocol is being used. here's the output from
my test machine. it's been booted over the network, but even so bios has assigned
a 0x80 drive, and it's been found and configured:
>> sdB loop #S/sdF0/data
sdE ahci ahci port 0xfffffe00fb538000 pci 0.17.4: 64a ncq alp led clo pmb slum pslum ems apts alhd xonly smb elmt iss 3 ncs 31 np 4 ghc 80000002 isr 0 pi f 0-3 ver 10300
sdF ahci ahci port 0xfffffe00fb532000 pci 0.31.2: 64a ncq alp led clo pmb slum pslum ems apts alhd xonly smb elmt iss 3 ncs 31 np 6 ghc 80000002 isr 0 pi 3f 0-5 ver 10300
sdN nvme port 0xfffffe00fb410000 pci 2.0.0 v1.0 rst 0 ctg 1 ams 0 stride 1 to 20000 fatal 0
sdO nvme port 0xfffffe00fb300000 pci 4.0.0 v1.1 rst 0 ctg 1 ams 0 stride 1 to 30000 fatal 0
- erik
next prev parent reply other threads:[~2016-01-03 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 11:55 tlaronde
2016-01-03 0:26 ` erik quanstrom [this message]
2016-01-03 10:06 ` tlaronde
2016-01-11 20:06 ` Iruatã Souza
2016-01-11 21:47 ` tlaronde
2016-01-11 22:08 ` 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=be9e8c90c529b93fd0159e9675a06ed6@mule \
--to=quanstro@quanstro.net \
--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).