From: adr@SDF.ORG
To: 9front@9front.org
Subject: Re: [9front] I can't make sdloop(3) work
Date: Mon, 31 May 2021 14:00:09 +0000 [thread overview]
Message-ID: <YLTr6eGBCaNoKVb8@SDF.ORG> (raw)
In-Reply-To: <0B1A14D5F8310F876623612B8491433C@felloff.net>
On Mon, May 31, 2021 at 01:18:01PM +0200, cinap_lenrek@felloff.net wrote:
> > Thanks!, it is working now, but partitions aren't shown:
> > Am I missing something?
>
> adding the partitions is done by userspace. the kernel doesnt parse
> partition tables:
>
> diskparts /dev/sdl0
>
> --
> cinap
I see, I had the impression by sdloop(3) that the behavior will be the same
as when you attach a disk device. Knowing This command solved the issue of changing
the sd card, although I suppose this device should be treated as removable device.
Now, diskparts on a sdloop device doesn't configure the plan9 partitions:
; echo config switch on spec l type loop//n/data/plan9/9front-8392.16c5ead832f2.pi3.img!1024 >/dev/sdctl
; diskparts /dev/sdl0
; ls /dev/sdl0
/dev/sdl0/ctl
/dev/sdl0/data
/dev/sdl0/dos
/dev/sdl0/raw
Reading diskparts(8) I noticed partfs(8):
; disk/partfs /n/data/plan9/9front-8392.16c5ead832f2.pi3.img
; ls /dev/sdXX
/dev/sdXX/ctl
/dev/sdXX/data
In this case diskparts does what is expected:
; diskparts /dev/sdXX
; ls /dev/sdXX
/dev/sdXX/ctl
/dev/sdXX/data
/dev/sdXX/dos
/dev/sdXX/fs
/dev/sdXX/nvram
/dev/sdXX/plan9
Was sdloop written for something different I was supposing?
Now that I know of partfs, what is the common use of sdloop?
Last time I used Plan9 (9front) was almost a decade ago, sorry
for the mess.
Regards,
adr.
next prev parent reply other threads:[~2021-06-01 2:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-29 20:34 adr
2021-05-30 5:17 ` [9front] " Anthony Martin
2021-05-30 9:53 ` [9front] " Alex Musolino
2021-05-30 22:30 ` adr
2021-05-31 11:18 ` cinap_lenrek
2021-05-31 14:00 ` adr [this message]
2021-06-01 13:06 ` cinap_lenrek
2021-06-02 15:58 ` adr
2021-06-03 7:40 ` hiro
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=YLTr6eGBCaNoKVb8@SDF.ORG \
--to=adr@sdf.org \
--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).