On 06/03/17 18:53, bob prohaska wrote:
> Theo  wrote:
>> https://github.com/mkatiyar/fuse-ufs2
>>
>> Note that UFS is not a standardised format, so there are differences between
>> different UNIX systems' implementations.
>>
> Now I appreciate the depths of the difficulty.........
>
> Thanks to all who replied! I did  build a new kernel using
> menuconfig. Didn't try the "dangerous" write option. Since the ufs
> partion had crashed it was dirty, I couldn't read or fsck it so it
> had to go on a freebsd box anyway.

strange.  'dirty' shouldn't prevent reading it.  normally that's caused
by not doing a complete shutdown, and doesn't actually affect file
system integrity.  Well, it *could* and apparently the file system
driver is being "paranoid".

menuconfig is painful so kudos to going through the process.  I usually
manually edit the files and use 'oldconfig' for kernel mods.  but it's
been a while since I needed to do that [used to do a lot with
customizing Linux on wifi access points back in the day].

and a kernel build on a Pi would be equally painful...

[hopefully you have a really good cross-compile environment set up]

--- SoupGate-Win32 v1.05