Date: Fri, 24 Sep 2004 15:53:24 -0000 From: Darren Pilgrim <dmp@pantherdragon.org> To: dwbear75@gmail.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Why is there no JFS? Message-ID: <3E4ADDDE.5040208@pantherdragon.org> In-Reply-To: <005801c2d2eb$aa5fae60$1200a8c0@gsicomp.on.ca> References: <3E4A5B77.5080103@ant.uni-bremen.de> <3E4A863E.2030801@potentialtech.com> <3E4A8EF5.1070308@ant.uni-bremen.de> <3E4A9712.8030609@potentialtech.com> <3E4AA331.5040701@ant.uni-bremen.de> <3E4AA734.5040102@potentialtech.com> <045401c2d2db$f9d45c30$0a0aa8c0@dweebsoft.com> <20030212225631.GA10375@HAL9000.homeunix.com> <005801c2d2eb$aa5fae60$1200a8c0@gsicomp.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Emmerton wrote: >>Thus spake Daxbert <daxbert_news@dweebsoft.com>: >> >>>The inspiration for this email was from a thread in >>>-questions: "Re: fsck takes very long after crash/reset" >>> >>>Is anybody currently working on or does there exist >>>a JFS for FreeBSD? > > > Various people (including myself and Hiten Pandya) have done work to port > the GPL'd JFS implementation, but there's one ugly problem -- the GPL. > > We can make JFS into a kernel module (avoiding the static-link policy of the > GPL), but then it can only (legally) be used on non-root filesystems, as the > code to read the root filesystem must be statically linked into the kernel. > This in itself makes JFS support somewhat pointless. Not really. A properly laid-out filesystem hierarchy will result in no writes to / (except for installworld/kernel). That removes the problem that journalling addresses, and is probably why softupdates is disabled by default for /. For large, active filesystems, journalling would be a big improvement when you had to run a foreground fsck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E4ADDDE.5040208>