From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,21541ce5f449bd0 X-Google-Attributes: gid103376,public Path: g2news1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsfeeds.ihug.co.nz!ihug.co.nz!news.xtra.co.nz!53ab2750!not-for-mail From: Craig Carey Newsgroups: comp.lang.ada Subject: Re: OpenBSD 3.5 & GNAT Message-ID: References: X-Newsreader: Forte Free Agent 2.0/32.652 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 05 Jun 2004 11:51:07 +1200 NNTP-Posting-Host: 219.88.31.54 X-Complaints-To: newsadmin@xtra.co.nz X-Trace: news.xtra.co.nz 1086393068 219.88.31.54 (Sat, 05 Jun 2004 11:51:08 NZST) NNTP-Posting-Date: Sat, 05 Jun 2004 11:51:08 NZST Organization: Xtra Xref: g2news1.google.com comp.lang.ada:1113 Date: 2004-06-05T11:51:07+12:00 List-Id: On 4 Jun 2004 10:43:17 GMT, Adrian Knoth wrote: >Craig Carey 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 >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]