Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!agate!dog.ee.lbl.gov!horse.ee.lbl.gov!torek From: torek@horse.ee.lbl.gov (Chris Torek) Newsgroups: comp.unix.bsd Subject: Re: BSD on SPARC Message-ID: <24519@dog.ee.lbl.gov> Date: 10 Jul 92 23:12:26 GMT Article-I.D.: dog.24519 References: <24288@dog.ee.lbl.gov> Organization: Lawrence Berkeley Laboratory, Berkeley Lines: 25 NNTP-Posting-Host: 128.3.112.15 On 1 July 1992, in article <24288@dog.ee.lbl.gov>, I wrote: >SPARC support will be included on the 4.4BSD-alpha tape. There will >probably be no SPARC binaries, however. None of the SPARC-specific >code is proprietary, so the system will be exactly as AT&T-encumbered >as 4.4BSD-alpha. This is not quite right: the ptrace code is based on the BSD hp300 ptrace code, which *is* AT&T-encumbered. (Presumably this will get fixed when we go to /proc.) >Bootstrapping [the BSD system from source] is a bit tricky ... This was a major understatement (what is the antonym of `hyperbole' again? :-) ). If CSRG do not ship SPARC binaries---and `no SPARC binaries' will probably be the case---bootstrapping will be quite a task. The fact that most SunOS binaries do work, provided that the SunOS shared library files are first copied to the disk, should help. Depending on time factors, the installation document (which is currently in progress) may, or may not, have an outline of an approach to bootstrapping. -- In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 510 486 5427) Berkeley, CA Domain: torek@ee.lbl.gov