Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.os.386bsd.misc Subject: Re: To Merge or Not to Merge *BSD. What does it really mean? Date: 17 Jan 1995 16:40:18 GMT Organization: University of California, Berkeley Lines: 11 Message-ID: <3fgrti$pvt@agate.berkeley.edu> References: <3f1h83$hgl@newshost.lanl.gov> <3f253c$es0@agate.berkeley.edu> <3f9hst$q8n@idiom.com> <3fgqpb$6b2@newshost.lanl.gov> NNTP-Posting-Host: violet.berkeley.edu In article <3fgqpb$6b2@newshost.lanl.gov>, Charlie Sorsby <crs@beta.lanl.gov> wrote: >But wouldn't the scheduling have been done by Usenix, as opposed to >the *BSD* folks? If so, it was rather silly on the part of Usenix. It was, but I don't think they even realized the significance of the scheduling. I've moved the FreeBSD BOF to AFTER the NetBSD bof, so that those who wish to hear about both systems can. Jordan