From owner-freebsd-chat Tue Mar 30 14: 0:27 1999 Delivered-To: freebsd-chat@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id B532B1502E for ; Tue, 30 Mar 1999 14:00:25 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (qmail 27639 invoked from network); 30 Mar 1999 22:00:03 -0000 Received: from dyson.iquest.net (198.70.144.127) by iquest3.iquest.net with SMTP; 30 Mar 1999 22:00:03 -0000 Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.9.1) id RAA16694; Tue, 30 Mar 1999 17:00:02 -0500 (EST) From: "John S. Dyson" Message-Id: <199903302200.RAA16694@dyson.iquest.net> Subject: Re: Linux vs. FreeBSD: The Storage Wars In-Reply-To: <199903301823.LAA14513@usr06.primenet.com> from Terry Lambert at "Mar 30, 99 06:23:05 pm" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 30 Mar 1999 17:00:02 -0500 (EST) Cc: dyson@iquest.net, hamellr@dsinw.com, unknown@riverstyx.net, freebsd-newbies@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > Linux-Alpha doesn't have the 2 gig problem, and the 2.2 series does have > > > > patches available to go past the 2 gig limit. > > > > > > Which is why I personally don't like Linux. It seems that you're > > > always loading patches to fix little problems. :) Granted FreeBSD has > > > patches too. But when was the last time you needed a patch? :) Anyways, > > > isn't the Linux patch still limited to 8 gigs or so? > > > > IMO, it is *silly* that Linux doesn't support large files correctly. If > > it doesn't support large files on an X86, then it doesn't support large > > files. There was alot of pressure from the user and developer base when > > FreeBSD didn't properly support large files, and I am surprised that > > either the Linux base hasn't pressured for proper support for large files, > > or the Linux developers can't figure out how to do it. (I sure hope that > > it isn't arrogance on their part that it isn't "needed.") > > Well, as long as we are beating dead horses here... > > IMO, it is *silly* that FreeBSD coopted the fields in FFS that were > reserved for dealing with the Y2038 "bug", which technically didn't > exist in BSD 4.4 until these fields were coopted. > > But then, who am I to look 39 years into the future, instead of only > 6 months ahead, like everyone else. > Since the *fix* wasn't implemented, then the fix wasn't broken. Nothing additional was broken, and a better fix will eventually be created (e.g. changed inode structure for ACL support?) If you think that the ODS needs to be fixed, then fix it!!! :-). If it ends up being a solution rather than a hack, then it might just be adopted. If the "fix" ends up requiring lots of support from others, then the chance of the "idea" being adopted is lessened. But, please don't proclaim an idea as an implementation, and don't proclaim a piece of hackery as a "solution." I understand your frustration, but because YOUR projects don't get the highest priority doesn't mean that you are being ignored. It seems odd to me that some people think that others should support their works. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message