From: Conor Williams <conor.williams@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] mounting a 9660 file system - writeable
Date: Sun, 9 Jul 2023 00:43:56 +0100 [thread overview]
Message-ID: <CAL6pNZ9EwEvB0sg=Xrm-8idVfzXBYozj2A7N1tU3UuNmOPaz7g@mail.gmail.com> (raw)
In-Reply-To: <16924.1688834476@lunacy.ugrad.cs.cmu.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1285 bytes --]
thanks Dave... will look into the overlay file system + kernel hack soun..
got the 9front booting off one 9660 drive now (50GB) and am
mounting my second 20GB drive into /tmp/D (its a 9fat partition)
and i have rebooted and the created D files are still there
one strange thing that bogged me down for most of today (and stopped
me emailing you earlier), was that I edited the .iso, lets call it
cwCON.iso
and catted that to /dev/sdC0/data and no matter what I did it would not
boot,
the fs was there, but no booting...
what I am after doing is reverting to the current 9front iso just 20 mins
ago and it worked perfectly, so somehow they created 3 partitions
in /dev/sdC0/data (a 486MB, a 1MB ESP (1 cylinder)
and another large file system) (using cat???) so... my next post is
going to wonder how they did that and how i can add some handy
scripts to my own version of their iso... (is /386/pbslba somethingp...)
ps: is a 20GB file system safe? r why should i use fossil??
Kind Regards... & happy summer Dave... /c@midnight+43mi
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T49170188f63f430d-M68edd167cc7be7f1057e6f27
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #1.2: Type: text/html, Size: 2023 bytes --]
[-- Attachment #2: plan9_9front_boot_hackp.png --]
[-- Type: image/png, Size: 22433 bytes --]
prev parent reply other threads:[~2023-07-08 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 8:05 Conor Williams
2023-07-08 16:41 ` Dave Eckhardt
2023-07-08 23:43 ` Conor Williams [this message]
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='CAL6pNZ9EwEvB0sg=Xrm-8idVfzXBYozj2A7N1tU3UuNmOPaz7g@mail.gmail.com' \
--to=conor.williams@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).