Re: Mounting old BSD filesystem

2025-03-05 Thread Stephen Borrill
On Tue, 4 Mar 2025, Michael van Elst wrote: net...@precedence.co.uk (Stephen Borrill) writes: Looking good! Also mmm, a kernel that's 800k in size :-) Are these changes commitable? I didn't change any code, just modified the superblock a little bit. In particular, it now says it is 8k in s

Re: Mounting old BSD filesystem

2025-03-04 Thread Michael van Elst
net...@precedence.co.uk (Stephen Borrill) writes: >Looking good! Also mmm, a kernel that's 800k in size :-) >Are these changes commitable? I didn't change any code, just modified the superblock a little bit. In particular, it now says it is 8k in size and some bits that were undefined (all 1's)

Re: Mounting old BSD filesystem

2025-03-04 Thread Stephen Borrill
On Mon, 3 Mar 2025, Michael van Elst wrote: mlel...@serpens.de (Michael van Elst) writes: mlel...@serpens.de (Michael van Elst) writes: the direct struct doesn't use the d_namlen field, it's always zero. Correction, it apparently uses a 16bit d_namlen field and d_type is missing. This is

Re: Mounting old BSD filesystem

2025-03-03 Thread Michael van Elst
mlel...@serpens.de (Michael van Elst) writes: >mlel...@serpens.de (Michael van Elst) writes: >>the direct struct doesn't use the d_namlen field, it's always zero. >Correction, it apparently uses a 16bit d_namlen field and d_type is missing. >This is the OLDDIRFMT. Eh voila: % ls -l /mnt total

Re: Mounting old BSD filesystem

2025-03-03 Thread Michael van Elst
mlel...@serpens.de (Michael van Elst) writes: >the direct struct doesn't use the d_namlen field, it's always zero. Correction, it apparently uses a 16bit d_namlen field and d_type is missing. This is the OLDDIRFMT.

Re: Mounting old BSD filesystem

2025-03-03 Thread Michael van Elst
mlel...@serpens.de (Michael van Elst) writes: >So far: >it's a 2048 byte superblock (we insist on having 8192 bytes). >the old_flags field isn't known and we try to intrpret it. >the sblockloc field isn't known and validation fails. >the maxsymlinklen field isn't known and the 'value' triggers a

Re: Mounting old BSD filesystem

2025-03-03 Thread Michael van Elst
net...@precedence.co.uk (Stephen Borrill) writes: >Interestingly, Linux reads it just fine (copied from another forum): >a680v1: Unix Fast File system [v1] (little-endian), last mounted on /, >last written at Thu Nov 21 13:09:49 2002, clean flag 0, number of blocks >40960, number of data blocks

Re: Mounting old BSD filesystem

2025-03-03 Thread Stephen Borrill
On Fri, 28 Feb 2025, Michael van Elst wrote: net...@precedence.co.uk (Stephen Borrill) writes: dumpfs recognises it as a FFSv1 filesystem (mildly surprised as wasn't sure of partitioning, if any). file system: /dev/vnd0a format FFSv1 endian little-endian magic 11954 timeThu

Re: Mounting old BSD filesystem

2025-02-28 Thread Michael van Elst
net...@precedence.co.uk (Stephen Borrill) writes: >dumpfs recognises it as a FFSv1 filesystem (mildly surprised as wasn't >sure of partitioning, if any). >file system: /dev/vnd0a >format FFSv1 >endian little-endian >magic 11954 timeThu Nov 21 13:09:49 2002 The superblock looks

Mounting old BSD filesystem

2025-02-28 Thread Stephen Borrill
I have an Acorn A680 [1] which runs RISCiX which is a BSD 4.3 variant from 1989. The hardware itself is currently not well (magic smoke problems), but the SCSI disk is fine. I have taken an image of it (using NetBSD/acorn32!). dumpfs recognises it as a FFSv1 filesystem (mildly surprised as was