From: Conor Williams <email@example.com>
To: 9fans <firstname.lastname@example.org>
Subject: Re: [9fans] Re: iso expanded, mount list (dd) device
Date: Fri, 7 Jul 2023 23:52:15 +0100 [thread overview]
Message-ID: <CAL6pNZ-pQNUgXGvUQcGW8uD=G-6uS+Z-WSWJOkDaaOi5nHM_qw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3150 bytes --]
thanks Steve for de.help...
all good in the hood bros.of.9fans /c
ps: almost midnight, time for zeeeees....
---------------------o ------------ o -------------
On Fri, Jul 7, 2023 at 7:41 PM Conor Williams <email@example.com>
> im going to try
> (once mounted...)
> copy of /tmp/THEISO -> /tmp/b4 (/dev/sdC0/9fat) possibly using:
> tar -cf - / | ( cd /tmp/b4; tar -xf - )
> #that used work on minix...
> run the ns command of what ns returns (loads of binds etc...)
> -- maybe some udder commands...
> try and boot off the VM C drive (whilst turning off the iso boot)
> disaster 1 rec: boot off iso and possible bind /tmp/b4 -> /
> (or maybe selective dirs...)
> disaster 2 scenario: boot off iso, keep created ram fs and bind into
> /tmp/b4. eg bind -[abc] /tmp/bin /bin
> (after mounting C drive manually with
> *mount /srv/dos /tmp/b4 **/dev/sdC0/9*fat
> *any advice greatefully accepted... /c /bd*
> On Fri, Jul 7, 2023 at 7:28 PM Steve Simon <firstname.lastname@example.org> wrote:
>> 9660srv - it mounts an iso as 9p file server in /srv/9660, so you need to
>> do a mount(1) to actually see the contents.
>> On 7 Jul 2023, at 7:20 pm, Conor Williams <email@example.com>
>> ok... thank you Steve, well in...
>> that particular train of thought leads me to another question...
>> has you r a'yone an iso.expander for plan9... (ps: i do have anudder way)
>> ps: am still on the lookout for a dd arg...
>> laterz... /c /d 773
>> pps: overall: looking at a 10/15 minute vm plan9 static os creation...
>> with 99.99% automation
>> On Fri, Jul 7, 2023 at 6:58 PM Conor Williams <firstname.lastname@example.org>
>>> hello 9fannors...
>>> i wish to find the device? which the p9 iso file is mounted from...
>>> (a vm boot (i dont think that matters though...)
>>> e.g c drive is /dev/sdC0
>>> /c /ba 7723
>>> ps: i wish to do a quick back of the (, possibly ramfs, ) temporary /
>>> system kind of like a backup of the c drive
>>> % dd /dev/XXYXX /dev/sdC0/9fat
>>> pps: would anyone know what might happen if the /dev/XXYXX partition is
>>> smaller that the C drive... (the /dev/sdC0/9fat is formatted and large
>>> ready to go) -- i do realise i can find this out if I know the device...
>>> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
>> <https://9fans.topicbox.com/groups/9fans> + participants
>> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
>> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 5177 bytes --]
prev parent reply other threads:[~2023-07-07 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 17:58 [9fans] " Conor Williams
2023-07-07 18:02 ` Steve Simon
2023-07-07 18:19 ` [9fans] " Conor Williams
2023-07-07 18:27 ` Steve Simon
2023-07-07 18:41 ` Conor Williams
2023-07-07 22:52 ` Conor Williams [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).