Return to BSD News archive
Xref: sserve comp.unix.bsd:13799 comp.bugs.2bsd:474 comp.bugs.4bsd:2023 comp.unix.internals:7122 comp.unix.misc:12120 Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!panix!ddsw1!news.cic.net!locust.cic.net!pauls From: pauls@locust.cic.net (Paul Southworth) Newsgroups: comp.unix.bsd,comp.bugs.2bsd,comp.bugs.4bsd,alt.suit.att-bsdi,comp.unix.internals,comp.unix.misc Subject: Re: The 4.4BSD-Lite distribution announcement Date: 27 Apr 1994 23:14:14 GMT Organization: CICNet, Inc. Lines: 23 Message-ID: <2pmrk6$bar@spruce.cic.net> References: <2p4ieg$89j@agate.berkeley.edu> <2p9esl$lam@agate.berkeley.edu> <1994Apr27.074929.1863@newsroom.bsc.no> <VIXIE.94Apr27133921@office.home.vix.com> NNTP-Posting-Host: locust.cic.net In article <VIXIE.94Apr27133921@office.home.vix.com>, Paul A Vixie <vixie@vix.com> wrote: |>I've heard nothing from UCB indicating that they intended to publish diffs |>for 4.4->4.4lite. Since such diffs would consist mainly of removing files |>or large chunks of files, and since such removal could be reversed using |>"patch -R", someone with 4.4-lite could generate a fairly complete 4.4ish |>system without actually possessing the relevant USL/Novell licenses. Fair enough. Anyone know what would happen if you just extracted the "lite" release on top of a pre-existing encumbered source tree? Seems like if the structure coincided that would be the easiest way to update it without publishing "criminal" diffs or complicating Berkeley's job of distributing the sources. Maybe that's a stupid idea; I haven't seen what the "lite" distribution actually looks like yet. -- Paul Southworth CICNet Systems Support pauls@cic.net