Indeed.
I've always thought of UnixCLI as a quirky RISCiXFS. It can read the root filesystem (if the correct offset is given/configured, otherwise it complains about it not being a super block). It can 'cat' files. It can try to 'run' files (typically it fails due to other dependencies but it gives it a good go).
Now it turns out it can probably pass the pertinent root and swap locations over to vmunix.
From the look of things, it would seem to be moaning because it's been told root and swap are on the same partition, rather than because it's successfully dealing with one and then discovering they can't both be there.
Presumably, now we can pass the offset for the root partition, I can try passing a single location until it stops complaining about not being able to find it. At which point, it will either find the swap partition on its own or I can then start passing it both locations until it stops complaining about about lack of swap.
I suspect I've still not got something quite right, as it's complaing when root is on "sc0(0,root offset)" and swap is on "sc0(0,swap offset)", as being on the same filesystem. This is in contrast to RISCiXFS, which is quite happy with "sd0(0,root partition number)" and sd0(0,swap partition number)" being on different filesystems.
Thanks to bluescsi, I've created a second copy of the drive so I can use sc0 as root and sc1 as swap. At this point it stops complaining about both being on the same filesystem and goes back to whingeing about not being able to find root. I can 'ls' either drive (with suitable offset) and boot vmunix from either.
ps I'm reading the partition offsets from 'prptable' in scsidm, so they should be right...
I've always thought of UnixCLI as a quirky RISCiXFS. It can read the root filesystem (if the correct offset is given/configured, otherwise it complains about it not being a super block). It can 'cat' files. It can try to 'run' files (typically it fails due to other dependencies but it gives it a good go).
Now it turns out it can probably pass the pertinent root and swap locations over to vmunix.
From the look of things, it would seem to be moaning because it's been told root and swap are on the same partition, rather than because it's successfully dealing with one and then discovering they can't both be there.
Presumably, now we can pass the offset for the root partition, I can try passing a single location until it stops complaining about not being able to find it. At which point, it will either find the swap partition on its own or I can then start passing it both locations until it stops complaining about about lack of swap.
I suspect I've still not got something quite right, as it's complaing when root is on "sc0(0,root offset)" and swap is on "sc0(0,swap offset)", as being on the same filesystem. This is in contrast to RISCiXFS, which is quite happy with "sd0(0,root partition number)" and sd0(0,swap partition number)" being on different filesystems.
Thanks to bluescsi, I've created a second copy of the drive so I can use sc0 as root and sc1 as swap. At this point it stops complaining about both being on the same filesystem and goes back to whingeing about not being able to find root. I can 'ls' either drive (with suitable offset) and boot vmunix from either.
ps I'm reading the partition offsets from 'prptable' in scsidm, so they should be right...
Statistics: Posted by Boydie — Tue Feb 04, 2025 9:11 pm