From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] Free Carrots #5: MNT Reform
Date: Sun, 17 Jul 2022 18:56:24 -0700 [thread overview]
Message-ID: <7FC1BA039C3F9AB7D2BB9CCB8157C145@thinktankworkspaces.com> (raw)
In-Reply-To: <561A9BBC-A479-4410-9F77-EE989B12C191@biobuf.link>
Yes I made sure to unzip the archive which is obvious. I also made sure
to rename the image to 9fron.iso
I can cat the image to the sd drive and it boots up with 1.2G fs with
30G of unclaimed space or empty partition. Not sure how to reclaim that
extra space.
so inst/start was the plan to try to reclain that space but
after it does mountfs I run into the following
Preparing menu...% mount /srv/9660.dist /n/dist /n/distmedia///9front.iso
mount: mount /n/dist: unknown format
% mount /srv/dos /n/distmedia /dev/sdU7b1211/dos
% mount /srv/9660.dist /n/dist /n/distmedia///9front.iso
mount: mount /n/dist: unknown format
This is an uncompressed image.
I also just tried to build the iso from scratch but ran into other issues.
mk /tmp/9fron.arm64.iso
mk: don't know how to make '/tmp/9fron.arm64.iso' in directory /sys/lib/dist
Next is to skip mountfs and go to copydist. I think I will need to make some modifcations
to /rc/bin/inst/copydist to get it working. But then I got a bit lost with
disk/mkfs -z 16372 -U -s /n/dist /n/newfs /sys/lib/sysconfig/proto/allproto
I guess bind the system root to /n/dist then try to run it or do something different
not sure of the proto. I read it might be better to run
disk/mkfs -a -s dist proto > arch but I think I got an error on that
Quoth james palmer <james@biobuf.link>:
> On 17 July 2022 04:23:01 BST, william@thinktankworkspaces.com wrote:
> >I gave up and cat 9front-c5cf9b3e26033272c5f57b9a860c335e63786045.reform.img.gz > /dev/sdU7b121/data
>
> that is a gzip archive,
> surely you want to unzip it first? try:
>
> gunzip <9front-c5cf9b3e26033272c5f57b9a860c335e63786045.reform.img.gz >/dev/sdU7b121/data
>
> - james
>
next prev parent reply other threads:[~2022-07-18 1:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 1:40 sl
2022-07-16 23:12 ` william
2022-07-16 23:47 ` sl
2022-07-17 3:23 ` william
2022-07-17 20:31 ` james palmer
2022-07-18 1:56 ` william [this message]
2022-07-18 2:25 ` Stanley Lieber
2022-07-18 3:53 ` william
2022-07-18 4:59 ` ori
2022-07-18 5:12 ` william
2022-07-18 5:20 ` william
2022-07-18 5:49 ` william
2022-07-18 8:46 ` cinap_lenrek
2022-07-18 10:31 ` romi
2022-07-18 14:29 ` cinap_lenrek
2022-07-18 15:10 ` Alexander Shendi
2022-07-18 15:18 ` Sigrid Solveig Haflínudóttir
2022-07-18 15:42 ` Stanley Lieber
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=7FC1BA039C3F9AB7D2BB9CCB8157C145@thinktankworkspaces.com \
--to=william@thinktankworkspaces.com \
--cc=9front@9front.org \
/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).