HDTenEightyP/NetNews huggingface dataset:
From: peter@ferranti.com (Peter da Silva)
Subject: Re: 386BSD announcement
Organization: Xenix Support, FICC
Date: Tue, 7 Apr 1992 18:13:01 GMT

In article <12333@auspex-gw.auspex.com> guy@Auspex.COM (Guy Harris) writes:
> "/usr/openwin" is a completely *separate* glitch, although it has its
> own "share" directory ("/usr/openwin/share").  I've no idea where
> "/usr/openwin/fonts" comes from;

I meant /usr/openwin/lib/fonts

> it doesn't appear to be in the Open
> Windows 2.0 nor the Open Windows 3.0 "/usr/openwin" directory.  They
> have "/usr/openwin/lib/fonts" instead (and they're not "Postscript
> fonts" in the sense of Adobe Type N fonts, as far as I know; it's a
> different font technology).

There are Postscript fonts in there. Run "ldf" with no arguments.
-- 
/F { dup /Courier findfont exch scalefont setfont } def /S { show } def /L { 8
mul 24 add 24 exch moveto } def 8 F 1 L (Peter da Silva, Ferranti Internat) S
(ional Controls Corporation) S currentpoint 0 L (Sugar Land, TX  77487-5012;) S
(  +1 713 274 5180) S 8 sub moveto 16 F ( Have you hugged your wolf today?) S
Newsgroups: comp.unix.bsd
From: tbillman@hns.com (Tom Billman)
Subject: Re: Recompiling the bootcode. Fix for my PC
Originator: tbillman@tbillman
Organization: Hughes Network Systems Inc.
Distribution: hns
Date: Mon, 13 Apr 1992 15:08:10 GMT


Alex,

I'm not sure that I fully understand which version of Unix you are
using, but I have a 386SX, AMI BIOS and tried to boot BSDI's 386
Unix last week. I ran into problems with the computer reebooting.  It
turned out that I needed to set my Memory Interleave to INTERLEAVED in
the CMOS to be able to run. I also disabled all of the memory Shadowing. 
Jeff Polk from BSDI was VERY helpful in solving this problem.

You may want to check out your CMOS configuration.  I think I was running
version 1.5.1 of the CMOS, but I'd have to check.  I have an WD IDE drive.

Tom
Newsgroups: comp.unix.bsd
From: vixie@pa.dec.com (Paul A Vixie)
Subject: Re: BSD names (was: BSD on floppies)
Organization: DEC Network Software Lab
	<1992Apr8.110359.10948@pegasus.com> <148@adagio.UUCP>
	<VIXIE.92Apr9152242@cognition.pa.dec.com>
	<DRG.92Apr10110449@bubba.ma30.bull.com>
Date: 10 Apr 92 15:14:59

We do not need to solve this problem for all of time.  We just have to get
through to next week without name collisions.  I know that Jolitz calls his
386BSD, which is certainly different from what BSDi calls theirs (BSD/386):
there is a "/" in one of them, and the "386" and "BSD" are swapped.  This is
not enough difference for a number of the folks here in comp.unix.bsd, so I
proposed "Jolitz 386BSD" and "BSDi BSD/386", which are awkward but have the
twin virtues of (1) not dropping any information that the authors had chosen,
and (2) adding only information which the authors cannot possibly disagree
with or be offended by.  Unless someone proposes a naming scheme less awkward
than mine which still has those two virtues, let's let this issue settle.
--
Paul Vixie, DEC Network Systems Lab	
Palo Alto, California, USA         	"Ready, Fire, Aim"
<vixie@pa.dec.com> decwrl!vixie
<paul@vix.com>     vixie!paul          alt.pink.bunny.boom.boom.boom moderator
Newsgroups: comp.unix.bsd
From: sean@u36.uucp (Sean Goggin)
Subject: Partition ID table - version 1.1
Summary: Summary of know partiton codes
Keywords: partition
Organization: U36 Research
Date: Wed, 8 Apr 1992 03:34:19 GMT

Here the updated table of partition IDs.

If you know any other valid partition ID, please mail me at sean@u36.kwnet.on.ca

Thank you  - Sean


Partition Type 		Number 	
no partition 		0x00
Dos 12bit FAT Table	0x01
Xenix Root		0x02
Xenix Usr filesystem	0x03
Dos 16bit FAT Table	0x04
Dos 3.3 Extended	0x05
Dos 4.0 large volume	0x06
OS/2 HPFS		0x07
QNX			0x07
Advanced Unix		0x07
AIX file system		0x08
AIX boot partition	0x09
OPUS			0x0A
OPUS			0x10
VENIX 80286		0x40
Novell ?		0x51
CPM ? 			0x52
Microport SysV/AT	0x52
386/IX			0x63
UNIX System V/386	0x63
Novell			0x64
PC/IX			0x75
Minix 1.1 - 1.4a	0x80
Minix 1.4b - 1.5.10 	0x81
Linix (Planned) 	0x82
Amoeba file system	0x93
Amoeba bad block table	0x94
CPM			0xDB
C.DOS			0xDB
CTOS			0xDB
DOS 3.3+ Secondary 	0xF2
Bad Track table 	0xFF

-- 
Sean.Goggin....sean@u36.kwnet.on.ca..............................U36.Research...
From: nc00@eurotherm.co.uk (Neil Corlett)
Newsgroups: comp.unix.bsd
Subject: 4.4 filesystems
Date: 14 Apr 92 16:33:17 GMT
Organization: Eurotherm Limited


I seem to remember some reference to a new superfast filesystem in
bsd4.4. Is this true? And if it is, what exactly is it?

It's just that I get curious :-)

Thanks,

Neil
--
ncorlett@eurotherm.co.uk
Eurotherm Limited on +44 903 268500
Newsgroups: comp.unix.bsd
From: rjp@sabre.bellcore.com (Ronald Plummer)
Subject: Re: What happens if you have both BSD/386 and 386BSD?
Reply-To: rjp@sabre.bellcore.com (Ronald Plummer)
Organization: Bellcore, Livingston, NJ
Date: Mon, 13 Apr 92 22:15:24 GMT


> The BSDI folks are probably all great people.  That doesn't mean they can
> ignore the conditions of the marketplace they've decided to do business in.

I don't think they have, else those other folks here in NJ would have this
marketplace lock, stock and barrel. As it goes, there are those of us who
see all these efforts as a breath of fresh air that can only make this 
industry better by allowing other points of view and technologies to pitch
their worth.
 

> After all, this isn't a court of law where we're supposed to cut them
> some `presumed innocent' slack.  This is the marketplace where the clock
> is ticking and some of us need to make decisions based on whatever
> information is available.

If the product is as good as they say (I for one think it is), then the
natural market forces will prevail. If they become too restrictive with
their licensing strategies, the niche that they're marketing to will
dry up, so I wouldn't worry too much about it. 

Remember when SUN was going to ram NeWS down everyone's throat ? 
Irregardless of it's technical worth, they alienated us by restricting 
access and putting it out of economic reach of the average user 
(remember the PC revolution). 

You no longer have to work with someone who can afford the Evil Empire's
exorbitant source license cost and YOU can participate in pushing the
art/science. YOU can now release yourself from the stranglehold of
third party vendors who won't support their brain damaged code that 
you've become dependent on.

I wouldn't flame any of these efforts about their moral intentions in
this strange world, because the more the merry, unless of course you
have stock locked up inside the Death Star.

				 
-- 
Ronald J. Plummer
Bell Communications Research
331 Newman Springs Rd.
NVC-1H219
Red Bank, NJ 07701
(908) 758-2187 (Voice)  (908) 758-4192 (FAX)

I predict that today will be remembered until tomorrow!

rjp@sabre.bellcore.com
From: snewton@oac4.hsc.uth.tmc.edu (Steven E. Newton)
Newsgroups: comp.unix.bsd
Subject: Re: swap_pager_finish: clean of page 349000 failed (386BSD)
Date: 6 Apr 1992 15:55:30 GMT
Organization: Office of Academic Computing, UTHSCH, Houston, TX

In article <1992Apr04.223405.14237@NeoSoft.com>, karl@NeoSoft.com (Karl Lehenbauer) writes:
|> I've started getting some swap_pager_finish errors.  Here's one:
|> 
|>   error 0 blkno 12160 sz 4096 swap_pager_finish: clean of page 349000 failed.
|> 
|> I haven't dug in yet.  Anyone see this and know what the problem is?

Seen it also.  Just one time, but I got an endless repetition of about 8 or 10
different page #s.  Had to 3-finger salute.

Don't know what causes it, and I haven't been able to reproduce it.

Steve
-- 
+      +      +      +      +      +      +    |snewton@oac.hsc.uth.tmc.edu
    "Adventure without risk is Disneyland"     |Nobody else speaks for me,
                             --Generation X    |and I speak for no one else.
                                               |     +     +     +     +     +
From: scott@pita.cns.ucla.edu (Scott Burris)
Newsgroups: comp.unix.bsd
Subject: Re: Adaptec SCSI boot disk for 386BSD
Distribution: na
Date: 7 Apr 92 16:08:21 PDT

bvickers@bonnie.ics.uci.edu (Brett J. Vickers) writes:

>Has anyone successfully rebuilt the 386BSD kernel using the Adaptec
>SCSI driver that was recently posted here by Pace Willisson?  If so,

Yes, I have it running with a Fujitsu M2263SA SCSI drive.  Works like
a charm.  But I don't have a purely SCSI system running yet, so I boot
off of a Rodime IDE drive.
--
----------
Scott Burris
UCLA Campus Network Services
cnetslb@oac.ucla.edu (213) 206-4860 - OR - scott@pita.cns.ucla.edu
Newsgroups: comp.unix.bsd
From: garlangr@en.ecn.purdue.edu (Mark T Garlanger)
Subject: Wanted: Hacked 386bsd bootdisk...
Organization: Purdue University Engineering Computer Network
Date: Fri, 17 Apr 92 17:58:34 GMT

Seeing how I got no response on whether or not a new version of 386bsd 
is near completion, I now have other request.

There has been some discussions about making this version work without
interferring with DOS.  Has any made a new boot disk that won't dump on
the hard-drive and can be installed in a partition?  If anyone has such
a disk I would love to get a copy of it...

					Thanks,	
					   Mark


-- 
/---------------------------\
|Mark Garlanger             |
|garlangr@en.ecn.purdue.edu |
\---------------------------/
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: The great BSD name-off...
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Fri, 10 Apr 1992 17:15:36 GMT

As some other bright, intelligent, forward thinking person already
suggested (bright, intelligent, forward thinking because that person
suggested a name I had already thought of  ;-) ), I think

   FREEB (Prounounced free-b, for Free BSD)

would work great!

-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: BSD names (was: BSD on floppies)
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Thu, 09 Apr 1992 13:13:42 GMT

Call it "Jolix" even though it's 99.9% 4.3BSD?  Nah.

BSDJ?  That'll make people even more confused, and it'd be kind of like
starting a new pizza company called "Dominoes", y'know?

I just call it "386BSD", or "The free Unix for the 386".
-- 
-- Email info@NeoSoft.com for info on getting Internet access.
     "Trust me.  I know what I'm doing." -- Sledge Hammer
From: jtkohl@cs.Berkeley.EDU (John T Kohl)
Newsgroups: comp.unix.bsd
Subject: 16-bit '386/486 assembler?
Date: 13 Apr 92 04:53:07 GMT
Article-I.D.: agate.sb43jINN1db
Organization: University of California, Berkeley
NNTP-Posting-Host: stinson.cs.berkeley.edu

Anybody know where I can find a 16-bit 386/486 assembler that'll run
under BSD/386 or 386BSD?  The latest gas I looked at groks neither 16-bit
mode nor some of the more pathological addressing modes of the 386/486.

Thanks,
--
John Kohl <jtkohl@cs.berkeley.edu>
UC Berkeley CS grad student
Member of the League for Programming Freedom--details: league@prep.ai.mit.edu
(The above opinions are MINE.  Don't put my words in somebody else's mouth!)
From: lucchina@hsi86.hsi.com (Paul Lucchina)
Newsgroups: comp.unix.bsd
Subject: Need help modifying 4.3 BSD cmap.h
Keywords: Modifying cmap.h to allow for > 64 Mb of memory.
Date: 13 Apr 92 00:18:23 GMT
Distribution: usa
Organization: 3M Health Information Systems, Wallingford, CT


I would like to increase the  memory on a VAX 8650 running 4.3 BSD from 
36 Mb to 100 Mb.  The physical memory is currently limited to 64 Mb via the
core-map definitions in (/sys/h/cmap.h).  I don't completely understand
the comments in cmap.h for expanding the memory.  I would appreciate
directions on modifying this structure and information on any other
patches needed to make this task a success.

Thanks in advance!

Paul

**************************************************************************
Paul J. Lucchina				E-MAIL - lucchina@hsi.com 
3M Health Information Systems			VOICE - (203) 949-0303
Wallingford, CT  06492 				FAX - (203)949-6331  
**************************************************************************
-- 
Paul J. Lucchina				E-MAIL - lucchina@hsi.com 
3M Health Information Systems			VOICE - (203) 949-0303
Wallingford, CT  06492 				FAX - (203)949-6331
From: eichin@athena.mit.edu (Mark W. Eichin)
Newsgroups: comp.unix.bsd
Subject: Re: Ditto: Status of next release??
Summary: CVS is great
Keywords: CVS 386BSD
Date: 15 Apr 92 23:22:14 GMT
Organization: MIT SIPB; Cygnus Support

At Cygnus Support, we use cvs to manage all of our source trees. For
example, we've got gcc and binutils trees in California, and a
Kerberos tree here in Cambridge.
	The things I find the most useful are
		- email notification of changes
		- automatic update/merge
		- tree tagging & date-based fetching 
		- the standard RCS features underneath (diffs and logs
		in particular) 
	I've also had a lot of success using cvs to take a snapshot,
bring it somewhere (perhaps off the net), work on it, bring it back,
and fold the changes in. 

>> of a remote access version which minimizes the amount of data sent 
	I'm really looking forward to that.

	I haven't built a cvs tree of the 386bsd sources myself yet,
mostly because (1) I'm waiting for the next release (2) the network
code (well, some combination of SLIP, the serial drivers, and the tty
code) are broken in such a way that while it's easy to ftp stuff in to
the PC, it's very hard to get stuff *out*. 

				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
				Cygnus Support <eichin@cygnus.com>
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: BSD names (was: BSD on floppies)
Reply-To: Rich@Lamprey.Gal.UTexas.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
	<24838.9204051603@thor.cf.ac.uk>
	<1992Apr5.173902.23415@zip.eecs.umich.edu>
Date: Tue, 7 Apr 1992 04:13:09 GMT

In article <1992Apr5.173902.23415@zip.eecs.umich.edu> dmuntz@dip.eecs.umich.edu (Daniel A Muntz) writes:
   BSDJ seems to be the natural choice as many people have independently
   suggested it.  I haven't seen anyone confuse BSDI and BSDJ, but several 
   people have "mixed up" 386BSD and BSD386. 

Jolnix is pleasing to the ear.  :-)   Rich
--
From: tutui@silk.imel.kyoto-u.ac.jp (Takashi &)
Newsgroups: comp.unix.bsd
Subject: Why don't we separate ng of 386BSD and BSDI?
Date: 13 Apr 92 13:05:00 GMT
Distribution: comp
Organization: Dept. of Medical Informatics, KYOTO Univ. Hospital, KYOTO, Japan.

Why not? 
I can't dintinguish which is mentioned about in this news
group in these days.

--
TAKASHI Tsutsui M.D.		tutui@silk.imel.kyoto-u.ac.jp
Dept. of Medical Informatics Hospital of KYOTO Univ.
SAKYO-ku KYOTO JAPAN	Zip 606		Phone +81-75-751-3647
  (automaticaly switched to the fax)	Fax   +81-75-751-3647
Newsgroups: comp.unix.bsd
From: libove@libove.det.dec.com (Jay Vassos-Libove)
Subject: Re: BSD names (was: BSD on floppies)
Organization: Digital Equipment Corporation, Detroit Ultrix Resource Center
	<1992Apr4.015115.5860@cirrus.com> <1992Apr4.215301.17060@uwm.edu>
	<24838.9204051603@thor.cf.ac.uk> <28422@hoptoad.uucp>
Date: Thu, 9 Apr 1992 15:27:52 GMT


	  I don't think BSDI and BSDJ are very good choices. If you think there's
	  a tendency to mix up 386BSD and BSD386 then what do you think will
	  happen when the names only differ by the last digit and they're
	  consecutive letters of the alphabet.

   But they're mnemonic at least.  There's nothing to tell 386BSD from
   386BSD unless you can keep them straight by other means.  Mine is BSDI
   and BSDJ (I for Inc. and J for Jolitz).  

   I like the fact that J is close to I: full source puts your 1 step
   ahead.

BSDI includes full source too, as well as support.
They're different products aimed at different audiences, that's all.
--

Jay Vassos-Libove                  libove@libove.det.dec.com
Digital Equipment Corporation      decwrl!libove.det.dec.com!libove
Open Systems Resource Center       Opinions? They're mine, mine, all mine!
Farmington Hills, Michigan         and D.E.C. Can't have 'em!
Newsgroups: comp.unix.bsd
From: cproto@marsh.cs.curtin.edu.au (Computer Protocol)
Subject: Re: BSD names (was: BSD on floppies)
Organization: Curtin University of Technology
Date: Thu, 9 Apr 1992 16:55:46 GMT

libove@libove.det.dec.com (Jay Vassos-Libove) writes:


>	  I don't think BSDI and BSDJ are very good choices. If you think there's
>	  a tendency to mix up 386BSD and BSD386 then what do you think will
>	  happen when the names only differ by the last digit and they're
>	  consecutive letters of the alphabet.

>   But they're mnemonic at least.  There's nothing to tell 386BSD from
>   386BSD unless you can keep them straight by other means.  Mine is BSDI
>   and BSDJ (I for Inc. and J for Jolitz).  

>   I like the fact that J is close to I: full source puts your 1 step
>   ahead.

>BSDI includes full source too, as well as support.
>They're different products aimed at different audiences, that's all.
>--

>Jay Vassos-Libove                  libove@libove.det.dec.com

When will you guys stop arguing about those stupid names. BSDI call
their product BSD/386, Bill calls his stuff 386BSD. You don't have
to be too bright to remember those two names. So please stop the
bullshit and fix bugs, write new device drivers or contribute
something else more useful.

-- Tibor Sashegyi

Newsgroups: comp.unix.bsd
From: ramzi@tigger.Colorado.EDU (Ramzi Al-Majid)
Subject: Which UNIX to buy for the PC
Keywords: n
Organization: University of Colorado, Boulder
Date: Sun, 12 Apr 1992 20:53:54 GMT




i need recommendation on which unix to buy for a 486-50 pc. 
which unix has more software support? which has best features implemented?

thanks

-- 
Computer Science Department	arpanet : ramzi@cs.colorado.edu
Univ. of Colorado - Boulder	bitnet  : ramzi@boulder.bitnet
Campus Box # 430		csnet   : ramzi@boulder.csnet
Boulder, Co 80309-430		uucp    : {ncar|nbires}!boulder!ramzi
From: s871780@minyos.xx.rmit.oz.au (Antony Suter)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD partial success & dos coexist.
Keywords: coexist success
Date: 6 Apr 92 05:46:50 GMT
Organization: RMIT Computer Centre, Melbourne Australia.

cheetah@sage.cc.purdue.edu (Bowen (Laughing Cheetah)) writes:

>in how many years?), everything looked fine.  However, the unix system 
>identified itself on bootup.  Careful inspection of cylinder 0 showed
>that 386BSD resides before MSDOS's startup code.  Careful removal of the
>386BSD code allowed MSDOS to boot.  From this experience, I'd assume that it

I had the same problem! Frustrating to try 386BSD, it didnt boot - ok,
put DOS back on - now 386BSD boots, but no kernal or fs!! Argh! I fixed
it by filling the first track on my harddrive with zeros, and re-DOSing it.

a. my problem with 386BSD is in the kernal not the bootblock.

b. DOS fdisk, if it sees a valid bootblock signature, assumes that it is a
DOS bootblock and doesnt write a DOS bb to hdisk.
-- 
Antony Suter			s871780@minyos.xx.rmit.oz.au
Melbourne, Australia
"Call me Jack, stranger things have happened!"
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Re: Recompiling the bootcode. Fix for my PC
Date: 13 Apr 92 21:01:55 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

Ok, I've got 386bsd to boot ok but I'm having problems installing the
binaries. I've mounted /dev/wd0a on root and /dev/wd0h on /usr. I'd
previously mounted /dev/wd0a on /mnt on the floppy and transferred the
dist.fs stuff across. Now, things get very weird when I start to
transfer the first floppy. Why are things getting put in bin/bin? After
a while I get file system full errors on root (which is 4Mb).

Surely, apart from a few things, it should be going in /usr/bin? I've
never come across a system with /bin/bin before. Also, probably due to a
mistake I made, there are several copies of these binaries all over my
filesystem. Some in /mnt, some in /bin, some more in /bin/bin etc. Often
these are multiple copies of the same file!

What is going on? What did I do wrong?

The one filesystem with lots of space i.e. /usr is empty!!

p.s. I noticed that df doesn't handle full filesystems properly. It
gives minus block available values. Can't look at it myself, as yet,
because I haven't even tried to get the source installed.
-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@thor.cf.UUCP or ...!uunet!mcsun!ukc!cf!thor!spedpr
+++
Xref: sparky comp.unix.bsd:768 comp.unix.internals:1100 comp.unix.questions:6109 comp.lang.c:7492
From: hans@sun.se (Hans J. Albertsson - Sun Sweden)
Newsgroups: comp.unix.bsd,comp.unix.internals,comp.unix.questions,comp.lang.c
Subject: Re: errno questions
Date: 11 Apr 92 14:18:14 GMT
Reply-To: hans@Sweden.Sun.COM
Organization: Sun Microsystems AB, Sweden

In article <etxaax.702829519@falcon2> etxaax@falcon2.ericsson.se (Anders Axelsson) writes:
>Does anyone know if errno can be 0 after a Unix error? sys_errlist[0] does
>have a value, a cryptic message "Error 0". In our version of errno.h (from
>SunOS 4.1), there is no #define for the value 0.

For any error that doesn't set the errno field, yes! And there are quite
a few such situations, though one might argue that they're not `UNIX errors',
e.g. library errors and such.
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: 386BSD - adaptec 1542 scsi driver help needed!
Keywords: 386BSD adaptec 1542 scsi driver
Date: 9 Apr 92 16:38:57 GMT
Organization: HCS GmbH, Hamburg, Europe


i'm trying to get the adaptec 1542 scsi driver to work with 0.0new - no 
success yet. after inserting a couple of printf's and consulting the
technical ref manual, the problem seems to be the second call to as_put_byte()
in asattach(). the first call succeeds, but the second times out - any ideas ?

how do i have to make a correct entry for a tape into devices.i386 ?

also i added the entries for the driver into conf.c struct's bdevsw & cdevsw,
as i recognized there is no asdump(), what shall i substitute for it ?

couple of questions, but i must have a working tape !!! (crossing fingers ..)

anybody out there ?

hellmuth
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
From: richard@pegasus.com (Richard Foulk)
Newsgroups: comp.unix.bsd
Subject: Re: BSD names (was: BSD on floppies)
Date: 8 Apr 92 11:03:59 GMT
Article-I.D.: pegasus.1992Apr8.110359.10948
Organization: Pegasus,  Honolulu

>
>BSDJ seems to be the natural choice as many people have independently
>suggested it.  I haven't seen anyone confuse BSDI and BSDJ, but several 
>people have "mixed up" 386BSD and BSD386. 
>

They both seem equally funky ... and confusion prone.

Besides, the I J sillyness makes it seem like BSD386 came before 386BSD ...


-- 
Richard Foulk		richard@pegasus.com
Newsgroups: comp.unix.bsd