linux-kernel - Re: [GIT PULL] Squashfs pull request for 2.6.29

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]

Date:	Sat, 10 Jan 2009 10:30:23 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Jörn Engel <joern@...fs.org>,
	Ingo Molnar <mingo@...e.hu>, David Brown <lkml@...idb.org>,
	Phil Oester <kernel@...uxace.com>,
	Kay Sievers <kay.sievers@...y.org>,
	Phillip Lougher <phillip@...gher.demon.co.uk>,
	Christoph Hellwig <hch@...radead.org>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [GIT PULL] Squashfs pull request for 2.6.29

On Sat, 10 Jan 2009, Andrew Morton wrote:
> 
> More importantly, the filesystem driver has to be able to read older
> filesystem instances.  This is a userspace-visible binary interface!
> A really complex one.

Well, the good news is that read-only filesystems are _sooo_ much simpler 
than any real filesystem that quite frankly, on a "complexity" scale it's 
still way way down there.

Also, if it's not used for backup (and I don't think anybody would), 
there's actually less reason to be back-wards compatible. I know I changed 
cramfs a few times incompatibly, simply becaus "you might as well just 
re-run the user tools to generate the image". It was for a similar need, 
and the image really always goes along with the kernel.

I think squashfs usage would be similar - you'd not have squashfs as a 
standalone media, it would be a "installation medium" thing.

			Linus
--
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/