comp.lang.ada
 help / color / mirror / Atom feed
From: Craig Carey <research@ijs.co.nz>
Subject: Re: OpenBSD 3.5 & GNAT
Date: Sat, 05 Jun 2004 11:51:07 +1200
Date: 2004-06-05T11:51:07+12:00	[thread overview]
Message-ID: <jh12c05ju04iipbn1rm8cg9i5is13fft1e@4ax.com> (raw)
In-Reply-To: slrncc0ki5.f6g.adi@ppc201.mipool.uni-jena.de

On 4 Jun 2004 10:43:17 GMT, Adrian Knoth <adi@thur.de> wrote:

>Craig Carey <research@ijs.co.nz> wrote:
>
>> I find my FreeBSD 5 system is auto-erasing. 
>
>Is what? It deletes itself?

Actually, all no data is lost since again FreeBSD got a corrupted BSD
disklabel. I suppose it could have been this FreeBSD 5.1 problem that
I informed the OpenBSD bugs list about.

>Date: Fri, 21 Nov 2003 14:24:35 +1300
>To: bugs@openbsd.org
>From: Craig Carey <research@ijs.co.nz>
>Subject: Re: fsck damages FreeBSD 5 disklabels ? 
>
>At 2003-08-13 23:39 -0600 Wednesday, Theo de Raadt wrote:
...
>>Hundreds of Unix operating systems ship with an fsck that will
>> not check that field.

However justifiying OpenBSD when trashing FreeBSD was mismatching
with the facts. In fact FreeBSD 5.1 was deleting its own filesystem.

...
>It turned out that OpenBSD was innocent. [...]
>The faulty binaries appeared in about 5 June 2003. Still they are
>not updated:
>  ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/5.1-RELEASE/
...
>(2) The FreeBSD 5.1 "bsdlabel" program can't read the disklabels
> correctly.
...
>Installing an v5.1 emergency repair system is a way to cause
>(seeming) destruction of the other FreeBSD UFS2 system.
>
>Buildworld removes the problem
  [if it completes]







  reply	other threads:[~2004-06-04 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 10:52 OpenBSD 3.5 & GNAT Roman V. Isaev
2004-06-03 11:20 ` Jeff C,
2004-06-03 23:12   ` Roman V. Isaev
2004-06-04  6:15     ` Craig Carey
2004-06-04 10:43       ` Adrian Knoth
2004-06-04 23:51         ` Craig Carey [this message]
2004-06-05 22:42     ` Roman V. Isaev
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox