Date: Fri, 20 Mar 2015 14:32:46 +0800 From: Julian Elischer <julian@freebsd.org> To: sson <sson@FreeBSD.org>, freebsd-hackers@freebsd.org Subject: Re: UFS endian conversion Message-ID: <550BBF0E.2050600@freebsd.org> In-Reply-To: <1426819192856-5998370.post@n5.nabble.com> References: <alpine.BSF.2.11.1503091410290.26083@laptop.wojtek.intra> <20150309190119.GC72806@spindle.one-eyed-alien.net> <1426819192856-5998370.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/20/15 10:39 AM, sson wrote: > Brooks Davis-2 wrote >> On Mon, Mar 09, 2015 at 02:11:02PM +0100, Wojciech Puchar wrote: >>> is it possible without backup/restore? >>> >>> any tool? >>> >>> or do i miss something in fsck_ffs manual? >> You would need to backup on the source endian and restore on the >> destination. Stacey Son (cc'd) has some patches to allow access to UFS >> file systems of non-native endian that need someone to help polishing >> them up. >> >> -- Brooks >> >> >> attachment0 (188 bytes) >> <http://freebsd.1045724.n5.nabble.com/attachment/5995345/0/attachment0> > (Sorry, I have been on vacation and then started having #mbp2011 > <https://mbp2011.org>; issues with my laptop so I am just catching up.) > > I just rebased my patches to something a little closer to -current. You can > find my preliminary changes here: > > https://github.com/staceyson/freebsd/commit/642ad5aec8e9d130cdd347699da9718b23ff749a > > This provides enough support for the somewhat trivial case (e.g. ro, no soft > updates, etc.). This, indeed, needs more polishing. > > -stacey. > \ rather cool. does it all compile away to naught if not wanted?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?550BBF0E.2050600>