linux-kernel - Re: Versioning file system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0706151601320.27993@blackbox.fnordora.org>
Date:	Fri, 15 Jun 2007 16:06:34 -0700 (PDT)
From:	alan <alan@...eserver.org>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Jack Stone <jack@...keye.stone.uk.eu.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	akpm@...ux-foundation.org, viro@...iv.linux.org.uk
Subject: Re: Versioning file system

On Fri, 15 Jun 2007, H. Peter Anvin wrote:

> alan wrote:
>>
>> ZFS is the cool new thing in that space.  Too bad the license makes it
>> hard to incorporate it into the kernel.  (I am one of those people that
>> believe that Linux should support EVERY file system, no matter how old
>> or obscure.)
>>
>
> I have details on the Luxor UFD-DOS filesystem, if you'd care to
> implement it.

Do you have example discs that can be mounted to test it?  If you do, I 
will consider doing it.

I have a couple of older DOS filesystems that got dropped out years ago 
that I actually need to mount disks that i may rewrite for 2.6.x.

Now all i need is the time.

And speaking of obscure information...

I have a bunch of PCMCIA spec documents from the PCMCIA standards 
association from the late 90s.  Would anyone involved in maintaining the 
PCMCIA code be interested in it?  (Especially if they are in Portland.) 
It has been a while since I have even needed to look at it and I hate for 
it to go to waste if it can be of any use.  (Bit late now, I know...)

-- 
"ANSI C says access to the padding fields of a struct is undefined.
ANSI C also says that struct assignment is a memcpy. Therefore struct
assignment in ANSI C is a violation of ANSI C..."
                                   - Alan Cox
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/