From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 15068 invoked from network); 1 Jun 2021 02:37:22 -0000
Received: from 1ess.inri.net (216.126.196.35)
  by inbox.vuxu.org with ESMTPUTF8; 1 Jun 2021 02:37:22 -0000
Received: from mx.sdf.org ([205.166.94.24]) by 1ess; Mon May 31 10:03:46 -0400 2021
Received: from sdf.org (IDENT:adr@sdf.org [205.166.94.16])
	by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 14VE09pb022689
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO)
	for <9front@9front.org>; Mon, 31 May 2021 14:00:09 GMT
Received: (from adr@localhost)
	by sdf.org (8.15.2/8.12.8/Submit) id 14VE09Uo029871
	for 9front@9front.org; Mon, 31 May 2021 14:00:09 GMT
Date: Mon, 31 May 2021 14:00:09 +0000
From: adr@SDF.ORG
To: 9front@9front.org
Message-ID: <YLTr6eGBCaNoKVb8@SDF.ORG>
Mail-Followup-To: 9front@9front.org
References: <YLQSFuXDd5Gpp5Xb@SDF.ORG>
 <0B1A14D5F8310F876623612B8491433C@felloff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0B1A14D5F8310F876623612B8491433C@felloff.net>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: module-scale metadata 
Subject: Re: [9front] I can't make sdloop(3) work
Reply-To: 9front@9front.org
Precedence: bulk

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.