Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Jan 1998 01:59:30 -0800 (PST)
From:      Simon Shapiro <shimon@simon-shapiro.org>
To:        "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc:        asami@cs.berkeley.edu, aryder@bestweb.net, current@FreeBSD.ORG, kong@kkk.ml.org, Alex Nash <nash@mcs.net>
Subject:   Re: Making world today
Message-ID:  <XFMail.980111015930.shimon@simon-shapiro.org>
In-Reply-To: <11733.884504253@time.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 11-Jan-98 Jordan K. Hubbard wrote:
>> Seems that way.  Maybe we should start thinking about how to eliminate
>> these slips.  We are gaining a reputation lately.
> 
> It is the nature of -current to break occasionally and I would be no
> means wish to get so anal about this that the whole intention of
> -current was lost, namely to be a place to work out new stuff and,
> yes, occasionally break things in the process.  That is why -current
> has always been a strictly no-warranty proposition with warning
> stickers stuck all over it.  The complains we've been getting lately
> stem, I think, more from the fact that a lot of the wrong people are
> now running -current rather than any major instability there.  Hell, I
> remember when running -current was a good way to lose *filesystems*
> and things have definitely come a hell of a long way from there. ;-)
> 
>                                       Jordan

As you no doubtedly noticed, I did say that FreeBSD is one of the best.
We all understand rather well the experimental nature of -current.

As there is absolutely no warranty on ANY version of FreeBSD, it is quite
clear that -current is less waranted than no warranty.

None of these should act as a license for careless checkin (which happens
by all admissions, from time to time).  Neither should it impede the quest
for a better, more reliable environment and methodology.

As far as being ``far and long way from loosing filesystems'', I've got
news for you :-)  Not that far:

a.  My /usr/ports/distfiles is belived, by FSCK to have corrupt superblocks
    where the forst copy does not match the second copy.  This is a)
    nonsense - they actually match, and b) a result of a -current crash.

b.  I took this long to reply and still am up at this time, despite needing
    to wake up at 0600, because of a -current crash that neatly and cleanly
    removed ALL the files from /, kernels and all, and corrupted two
    filesystems beyond repair.

These facts are NOT a bitch/complaint/moan.  I am fully aware of the
consequences of using in-progress code.  Just a light-hearted tease :-))


----------


Sincerely Yours, 

Simon Shapiro
Shimon@Simon-Shapiro.ORG                      Voice:   503.799.2313



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980111015930.shimon>