From: Hans Reiser <reiser@namesys.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: [reiserfs-list] [PATCH/URL] Endian Safe ReiserFS
Date: Thu, 26 Apr 2001 12:56:36 -0700 [thread overview]
Message-ID: <3AE87D74.5D75BB8@namesys.com> (raw)
In-Reply-To: <3AE85F24.1010208@suse.com>
Jeff Mahoney wrote:
> I've just completed my port of ReiserFS to be endian safe. The patch
> has been tested successfully on x86 (UP/SMP), ppc (UP/SMP), and
> UltraSparc (UP). I've received reports that it also works successfully
> on mips (UP).
>
> The patch preserves the little-endian disk format, so a disk can be
> moved across architectures. The on-disk format has not been altered, so
> the code can be patched in without disruption to users with existing
> reiserfs filesystems (like myself :)). There are no VFS changes.
>
> Due to the patches affecting all of ReiserFS, the patch is quite
> large (180K), and so in the interests of preserving bandwidth for
> everyone, I've decided to post a URL to the patch instead.
>
> The patch can be found at:
> http://penguinppc.org/~jeffm/releases/endian-safe-reiserfs-for-2.4.4-pre7.final.bz2
>
> More information, including the endian safe utiltities, can be found
> at http://penguinppc.org/~jeffm.
>
> -Jeff
You might consider sending the patch to the maintainer of ReiserFS.
Hans
prev parent reply other threads:[~2001-04-26 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 17:47 [PATCH/URL] Endian Safe ReiserFS Jeff Mahoney
2001-04-26 19:56 ` Hans Reiser [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AE87D74.5D75BB8@namesys.com \
--to=reiser@namesys.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.