9front - general discussion about 9front
 help / color / mirror / Atom feed
From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] Free Carrots #5: MNT Reform
Date: Sat, 16 Jul 2022 20:23:01 -0700	[thread overview]
Message-ID: <1C13A329696D037D7BAF5A9DCAD04CA2@thinktankworkspaces.com> (raw)
In-Reply-To: <988AFD7485652830953194458D8BD495@gaff.inri.net>

So what you are saying is inst/start should work but the fat32 device that holds the image could be
corrupted?

I booted using mnt.reform image below and ran 

disk/fdisk -b /dev/sdU7b1211/data
disk/format -b pbs -d -r 2 /dev/sdU7b1211/dos

after that it automatically mounted in /shr/sdU7b1211

9front-c5cf9b3e26033272c5f57b9a860c335e63786045.reform.img.gz

after that the goal was to read from that device and write to sdU7b121 the larger drive

I gave up and cat 9front-c5cf9b3e26033272c5f57b9a860c335e63786045.reform.img.gz > /dev/sdU7b121/data

size never changes and fat32 should not be a problem if I can 'cat' the image to another drive

My partitions are always the same with the same size regardless of the size of the drive


Task to do [prepdisk]: 

--------------------------------------
The following Plan 9 disk partitions were found.

/dev/sdM0/plan9
  empty                 0 2          (2 sectors, 1.00 KB)
  nvram                 2 3          (1 sectors, 512 B )
  fs                    3 3657023    (3657020 sectors, 1.74 GB)
  empty           3657023 3657024    (1 sectors, 512 B )

/dev/sdU7b121/plan9
  empty                 0 2          (2 sectors, 1.00 KB)
  nvram                 2 3          (1 sectors, 512 B )
  fs                    3 3657023    (3657020 sectors, 1.74 GB)
  empty           3657023 3657024    (1 sectors, 512 B )

Plan 9 partition to subdivide (/dev/sdM0/plan9, /dev/sdU7b121/plan9)[no default]: 


Quoth sl@stanleylieber.com:
> > unknown format.
> 
> untested, but i think alien formats can confuse the install scripts.
> try dd </dev/zero >/target/device/data before running the installer.
> just be careful you write to the correct device!
> 
> sl
> 


  reply	other threads:[~2022-07-17  3:24 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 [this message]
2022-07-17 20:31       ` james palmer
2022-07-18  1:56         ` william
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=1C13A329696D037D7BAF5A9DCAD04CA2@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).