From owner-freebsd-hackers Wed Oct 15 01:25:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA28761 for hackers-outgoing; Wed, 15 Oct 1997 01:25:11 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from nessie.ethz.ch (dapor@nessie.ethz.ch [129.132.71.52]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id BAA28756 for ; Wed, 15 Oct 1997 01:25:07 -0700 (PDT) (envelope-from dapor@nessie.inf.ethz.ch) Received: (from dapor@localhost) by nessie.ethz.ch (8.6.10/8.6.12) id KAA29036 for hackers@freebsd.org; Wed, 15 Oct 1997 10:23:44 +0200 From: Carlo Dapor Message-Id: <199710150823.KAA29036@nessie.ethz.ch> Subject: 86open and implication on FreeBSD To: hackers@freebsd.org Date: Wed, 15 Oct 1997 10:23:44 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear Hackers I read the 86open 'vision'. To me it sounds nice, having to generate simply one binary for many x86 plat- forms. I have two questions: one thing is that this UBF (universal binary format) would require all the platforms to ELFish ? If this is correct, what is the status on FreeBSD ? I know FreeBSD is able to run both a.out and (Linux)-ELF bianries. The guy in charge of ELFizing FreeBSD is John D. Polstra, correct ? However, FreeBSD is still a.out, for several good reasons. The second thing that comes to my mind is, how are the differences addressed as far as devices are concerned ? I mean, what if I were to write a nice archiving utility, it would fully conform to UBF (a term I made up, btw), but I would still have to know, which partition I'd archive (/dev/sd0s1a or /dev/sda1 - not so sure here about Linux' corresponding name). Will there be some kind of flavours ? Or even better, a mechanism that maps device names, so that You wouldn't have to bother anymore ? Hope somebody can shed a light. Thanks a lot, guys ! Ciao, derweil, -- Carlo -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3ia Comment: requires PGP version 2.6 or later mQENAzQOnboAAAEIALnpSTc5y2g21CIX5V9bMqxsixXpQZDyR3hGosGsPC8S0WXP xfJiXAw/Zq3sPZhmiGZWq8/QP/d69tm4ert6rGB5Vuue96beKei4iemBF1ZpTU9G 3/tLsL63GHTLDAf+jqNcp1xM5ORF+qkFqP1ForzED06ba7HPQomzD0uhPbczHr9p vLAsczg1Wm9op06m7VTgK/hEvOJZPdxu0i2mFC2KVmRJr/KLcjs4CyEt6S8cJk8F Q3vDOOvwa+j/AHkvejBYokNYbfA+5D6bbYmNl5GxsKmY/qxamEaPWy7lZ87v8J0E CwnfzxiFPlguHCAux3u388EWqGWyAqOeROtKqL0ABRG0JkNhcmxvIERhcG9yIDxk YXBvckBuZXNzaWUuaW5mLmV0aHouY2g+iQEVAwUQNA6dugKjnkTrSqi9AQH3kAf/ T7dFJl6YQbUKSwTxNX/rERk2W010j2fH1bkbgOOfEfvQ6LiIRJYmJQCgeehP8kEU V66vSPboGsjl+8wU5CdlmoPsf7xw94Dh+uI48/CKLFAu+Rq2lonQOuzSvEDGg1P0 pU4UyCdj5i+y89jS+wBNA/yG6wsEGWMVltWqB2UKSg1n3YbA8JqaO2x9JLtIzfoB J/jhl5Jl4kX8OJzX1XVlJTxYdu9PTwaTZP68EG6NNfEyCn5Fp6iSDtUrLms1pI5i 3U282bIhBgVXr19hVS2olqTUHGdgcRqFjcnrARIBKoB9stuKj1+ORqlDiLwJfvg5 6JNSM4HFutk/iftKBqYXhQ== =XYxp -----END PGP PUBLIC KEY BLOCK-----