HDTenEightyP/NetNews huggingface dataset:
From: bdale@col.hp.com (Bdale Garbee)
Subject: Re: Recompiling the bootcode. Fix for my PC
Date: Sun, 12 Apr 1992 04:14:55 GMT
Organization: HP Colorado Springs Division

u8acb@ohm.york.ac.uk (Alex Barclay) writes:
> I can get the thing to boot off the floppy by... Wait for it...

Fascinating!  I tried your sequence of operations on the 16Mhz 386SX system 
I've been trying to boot 386BSD on, and it worked exactly as you document!.  My
system config is:

	- no-name 386SX 16Mhz motherboard with Intel 387SX16, 4MB RAM, AMI Bios
	- WD1006 with Maxtor XT-2190 and a 1.44M floppy drive
	- no-name hercules-clone video card and Northgate keyboard

This system had exactly one time booted 386bsd correctly from floppy, but on
every other attempt hung after the 'color' token as has been so often 
described.  As you noted, it still hangs that way when attempting to boot off
the hard disk.  I wonder what happens when a disk isn't found that is tickling
the kernel/hardware?  Maybe a double-initialization, or something?

I don't currently have any easy way to build a new kernel, so this still 
doesn't leave me with a useful 386BSD system...  

Bizarre, but thoroughly amusing!  :-)

Bdale
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: "real" /sbin/init available somewhere ?
Keywords: 386BSD init
Date: 13 Apr 92 18:10:20 GMT
Organization: HCS GmbH, Hamburg, Europe

before i start hacking my own, is there a "real" init (/sbin/init) source
available somewhere ?

hellmuth
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
From: jot@zevs.ifi.unit.no (Jo Torsmyr)
Newsgroups: comp.unix.bsd
Subject: Re: Real version 0.1?
Date: 6 Apr 92 14:32:28 GMT
Organization: Dep. of Comp. Sci., Univ. of Trondheim

In article <1992Apr2.184639.24517@zip.eecs.umich.edu>, dmuntz@dip.eecs.umich.edu (Daniel A Muntz) writes:
|> In article <1992Apr02.173044.22752@unx.sas.com> sastdr@torpid.unx.sas.com (Thomas David Rivers) writes:
|> >
|> > Just curious; is there any expected date of the "real" 0.1 release,
|> 
|> We really need another release.  There are now multiple patches for the same
|> bugs/missing_features and patches which break earlier patches.

Agree -- I have a bunch of patches, and several of them do (almost)
the same things, and they interfere with each other (especially
patches to /sys/kern/kern_execve). Hopefully the next release will
have solved this.


|> 
|>   -Dan

-jo

-- 
Jo Torsmyr
Department of Computer Science
College of Arts and Sciences
University of Trondheim, Norway		FAX: +47 7 59 17 33
Email: jot@ifi.unit.no			Voice: +47 7 58 88 79
From: richard@pegasus.com (Richard Foulk)
Newsgroups: comp.unix.bsd
Subject: Re: What happens if you have both BSD/386 and 386BSD?
Date: 13 Apr 92 16:04:09 GMT
Article-I.D.: pegasus.1992Apr13.160409.21059
Organization: Pegasus,  Honolulu

>wait, wait...
>
>>> And why wouldn't you expect to see BSDI litter in, and taint, more and
>>> more BSD files as they add new `features', large and small?
>>>
>>> They have yet to make any public statements to give us any other impression.
>
>so have you stopped beating your wife?
>
>c'mon, folks.  BSDI hasn't give you any reason to suspect that they are
>going to do the thing you suggest, so why should they have to make some
>public statement denying it?
>

It seems natural that they will tend to modify more and more files over
time.  Will they make an effort to contain the impact?  Do they have
a policy in this regard?

Since industry precedent set by AT&T and others for source code licensing
and control is very restrictive the safe assumption is that BSDI will be
restrictive also.  A policy statement from BSDI could mitigate such
negative assumptions.  (Their license agreement is encouraging, but not
sufficient.)

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.

It is obvious that BSDI follows and maintains a presence in comp.unix.bsd.
Important fundamental questions about licensing have repeatedly been asked
here, yet BSDI has chosen not to respond to them.  I would say that this
is `reason to suspect'.

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.

It is up to BSDI to decide if they are going to make it easy for their
customers to take advantage of both BSD/386 and 386BSD without undue
fear of attack by lawyer.  So far, it appears that they would rather
ignore the issue.  That is, of course, their prerogative.


(Am I supposed to go kick the dog now Paul?)

-- 
Richard Foulk		richard@pegasus.com
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: 386BSD Bibliography
Reply-To: Rich@Lamprey.Gal.UTexas.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Wed, 15 Apr 1992 07:09:14 GMT

Here's a list of the articles on 386BSD by William Frederick
Jolitz and Lynne Greer Jolitz in Dr. Dobb's Journal.  Any
suggestions on what books or articles are essential to
understanding 386BSD would be welcome!  Leffler, the IBM AT
technical reference, and 80386 data sheets are mentioned in
the first article.  Any others?  Rich

  Jan. 91 Porting Unix to the 386: A Practical Approach:
Designing the software specification.
  Sep. 91, Porting Unix to the 386: The Basic Kernel:
Multiprogramming and Multitasking, Part One.
  Oct. 91, Porting Unix to the 386: The Basic Kernel:
Multiprogramming and Multitasking, Part Two.
  Nov. 91, Porting Unix to the 386: The Basic Kernel: Device
Autoconfiguration.
  Feb. 92 Porting Unix to the 386: Device Drivers: Drivers
for the basic kernel.
  Mar. 92 Porting Unix to the 386: Device Drivers: Entering,
exiting, and masking processor interrupts.
  Apr. 92 Porting Unix to the 386: Device Drivers: Getting
into and out of interrupt routines.

Other books and references:

  Leffler, McKusick, Karels, and Quareterman. "The Design and
Implementation of the 4.3BSD UNIX Operating System." Addison-Wesley,
1989.
  Crawford and Gelsinger. "Programming the 80386." Sybex, 1987.
  IBM. "Technical Reference Guide Personal Computer AT." 19??.
--
Newsgroups: comp.unix.bsd
From: trandu@woods.ulowell.edu
Subject: headers for fd.c & absence of coprocessor
Organization: University of Lowell
Date: Thu, 16 Apr 1992 01:05:21 GMT


I have the version current version on agate.berkeley.edu; can't
seem to find isa_device.h, fdreg.h, ... Any ideas?
Anybody ever tried to install the binaries on a machine with no copressor?
Thanks 
Huy
hvo@uml.ulowell.edu
Umass at Lowell
From: eichin@athena.mit.edu (Mark W. Eichin)
Newsgroups: comp.unix.bsd
Subject: 386bsd kernel debugging?
Date: 11 Apr 92 18:51:09 GMT
Article-I.D.: athena.1992Apr11.185109.13929
Organization: MIT SIPB; Cygnus Support

Does anyone have any more advanced kernel debugging tools for 386BSD
than printf/syslog? They're useful enough, but I noticed a bunch of
KDB #ifdefs and wondered if anyone had gotten anywhere with them.
				_Mark_ <eichin@athena.mit.edu>
From: scott@pita.cns.ucla.edu (Scott Burris)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD - adaptec 1542 scsi driver help needed!
Keywords: 386BSD adaptec 1542 scsi driver
Date: 9 Apr 92 20:35:17 GMT

I do have that scsi driver running in my 386BSD kernel, so I'll try to
answer the following questions.  I've received a number of requests for
a kernel with the scsi driver in it, but I've become confused as to exactly
which patches I've applied where, so I'm going to take every patch home this
weekend and try to sort out this mess.

hm@hcshh.hcs.de (Hellmuth Michaelis) writes:

>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 ?

This sounds related to the problem with the DELAY() macro I reported in an
earlier post.  DELAY() uses a variable called cpuspeed which is never
explicitly initialized, and therefore gets set to zero.
In init_main.c, try putting: 

	cpuspeed = some small number (depends on the speed of your machine)

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

Never looked at this as I'm not lucky enough to have a SCSI tape drive :-(

>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 ?

I used enodev, I think.

--
----------
Scott Burris
UCLA Campus Network Services
cnetslb@oac.ucla.edu (213) 206-4860 - OR - scott@pita.cns.ucla.edu
From: patg@imp.com (Patrick Guelat)
Newsgroups: comp.unix.bsd
Subject: Re: ps/sps
Date: 13 Apr 92 08:56:00 GMT
Organization: ImproWare, Fuellinsdorf, Switzerland

In article <1992Apr10.203548.1425@cs.few.eur.nl>, pk@cs.few.eur.nl (Paul Kranenburg) writes:
|> 
|> >And that's correct, I have no such file. So -- how do one create
|> >this file?
|> 
|> Run `/usr/sbin/dev_mkdb'.

There is a problem with the device-database. When I run dev_mkdb remote
logins and telnets won't work anymore (i.e. incoming , telnetd , rlogind)

You don't even get a login prompt, the connection just hangs..

 -Patrick
Newsgroups: comp.unix.bsd
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Subject: Re: What happens if you have both BSD/386 and 386BSD?
Organization: Silicon Graphics, Inc.  Mountain View, CA
Date: Mon, 13 Apr 1992 11:13:25 GMT

richard@pegasus.com (Richard Foulk) writes:
+---------------
| What I got from reading the thread you mention is that Mike Karels made
| it a condition of his employ with BSDI that he be allowed to finish
| bstreams and give it to Berkeley.
+---------------

First BSDI, then BSDJ, and now... BSDK!

(I couldn't resist.)


-Rob

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com
Silicon Graphics, Inc.		(415)335-1673
2011 N. Shoreline Blvd.
Mountain View, CA  94039-7311

Newsgroups: comp.unix.bsd
From: mak@tgivan.wimsey.bc.ca (Bob Makowski)
Subject: Re: BSD names (was: BSD on floppies)
Summary: $ sign
Organization: not hardly
Distribution: na
Date: Fri, 10 Apr 1992 02:12:26 GMT

In article <1992Apr4.015115.5860@cirrus.com> dhesi@cirrus.com (Rahul Dhesi) writes:
>I too find these names very confusing.  I think we should use
>the following terminlogy:
>
>     BSDI/386 or 386BSDI:   BSD from BSDI
>     BSDJ/386 or 386BSDJ:   BSD for the 386 as released by Bill Jolitz
>


I've been following this thread, since I asked the question a while ago.
One suggestion I recvd was:

On  Fri, 27 Mar 1992 10:28:19 -0600,  Rich Scott <scott@rtc.atk.com> said:
Subject:  Re: 4.3 vs. 4.4 feature set comparisons?
+--------------- 
| In article <1992Mar26.224217.3171@tgivan.wimsey.bc.ca> you write:
| |vs. BSD386 or BSD/386? That silly little slash is not enough ;-)
| 
| 	How about BSD386 and BSD3$6?
| 
+--------------- End of Excerpt  Rich Scott <scott@rtc.atk.com>

Maybe a spin would be:

	BSD$386

= Mak

Newsgroups: comp.unix.bsd
From: knie2586@csd4.csd.uwm.edu (Robert Joseph Knier)
Subject: swapping problems
Organization: Computing Services Division, University of Wisconsin - Milwaukee
Distribution: comp.unix.bsd
Date: Fri, 10 Apr 1992 17:43:23 GMT

    I've posted here before reguarding lockups while compiling the 386BSD
kernel.  Best that I can determine is that during I/O intensive operations,
the swapper can lock up.  Would anyone know of techniques to get around
this so I can compile the kernel (once I do this, I'll look into the bug)?
Currently, I have a 386 20Mhz Northgate systems (no cache) w/a RLL drive.
I can't uprade beyond the 4Mb that I have as the main board is full (old
system), so I am looking for a temporary solution.


						Thanks in Advance

						Bob Knier
						(knie2586@csd4.csd.uwm.edu)
From: michael@resonex.com (Michael Bryan)
Newsgroups: comp.unix.bsd
Subject: Re: To make 386bsd coexist with DOS partitions??
Date: 7 Apr 92 08:40:33 GMT
Article-I.D.: resonex.1992Apr7.084033.14142
Organization: Resonex Inc., Sunnyvale CA

In article <1992Apr7.053441.344@msus1.msus.edu> l00017@eeyore.stcloud.msus.edu (Networking Research) writes:
>	I like the way that Mach 2.6 deals with this on the 386.  You have
>only one Mach partition in the DOS partition table, but within that partition
>you have a standard BSD style disklabel with it's own partition table.

This would be my preference.  This would allow, for instance, the creation
of a small DOS partition, and a large BSD partition (say 95% of a disk?),
so that you could boot either one by using an fdisk-like utility to change
which partition was active (bootable).  This large BSD psuedo-disk could
then be split into standard BSD partitions.

Of course, for now I'm content to make my first drive a BSD drive, with
a second smaller drive for DOS, and boot DOS from a floppy when I want it.
That is, assuming 0.1 comes out and has a fix for the hang on the "pc0"
line.

-- 
Michael Bryan	        michael@resonex.com
This offer law where prohibited by void.
From: grog@adagio.UUCP (Greg Lehey)
Newsgroups: comp.unix.bsd
Subject: Re: BSD names (was: BSD on floppies)
Date: 9 Apr 92 08:24:35 GMT
Organization: LEMIS, Schellnhausen 2, W-6324 Feldatal, Germany

In article <1992Apr8.110359.10948@pegasus.com> richard@pegasus.com (Richard Foulk) writes:

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

Yes, but it did. I'm not taking sides in this rift, but the fact is
that Jolitz worked for BSDI before going his own way and bringing out
386BSD. Even his articles in Dr. Dobbs and UNIX Magazin call it
BSD386, not 386BSD.
-------------------------------------------------------------------------------
Greg Lehey		         | Public access UNIX available - try BSDI 
 LEMIS         			 | out on our machine! Mail and news 
W-6324 Schellnhausen 2           | connections available
Germany				 | Fax: +49-6637-1489
Tel: +49-6637-1488               | Mail: grog%lemis@Germany.Eu.net
Claimer: The opinions expressed *are* the opinions of LEMIS
Newsgroups: comp.unix.bsd
From: peter@ferranti.com (Peter da Silva)
Subject: Re: The great BSD name-off...
Organization: Xenix Support, FICC
Distribution: usa
Date: Mon, 13 Apr 1992 14:28:41 GMT

"Free S D" or "Freenix".
-- 
/F{findfont exch scalefont setfont}def /S{moveto show}def /T{/Times-Roman F}def
8 T(Ferranti International Controls Corporation)24 28 S(+1 713 274 5180)24 12 S
(Sugar Land, TX  77487-5012)24 20 S 12 /Courier F(`-_-')320 32 S( 'U` )320 16 S
12 T(Peter da Silva)24 36 S 16 T(Have you hugged your wolf today?)358 24 S
Newsgroups: comp.unix.bsd
From: cpetterb@javelin.sim.es.com (Cary Petterborg)
Subject: Re: BSD names (was: BSD on floppies)
Organization: Evans & Sutherland Computer Corp.
	<1992Apr4.015115.5860@cirrus.com> <1992Apr4.215301.17060@uwm.edu>
	<24838.9204051603@thor.cf.ac.uk> <28422@hoptoad.uucp>
	<LIBOVE.92Apr9102752@libove.det.dec.com> <cproto.702838546@marsh>
Date: Thu, 9 Apr 1992 20:57:28 GMT

In article <cproto.702838546@marsh> cproto@marsh.cs.curtin.edu.au (Computer Protocol) writes:

>   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.

Who pee'd in your coffee??

There is a good reason for people referring properly to the two versions,
the main one being that people can keep from getting confused about
which one a person is talking about in a posting.  If the person wrongly
refers to a version, confusion ensues.

Having been the instigator of the discussion, I have a bit of myself
wrapped up in the discussion.  I found it confusing, when going through
the posting since 386BSD came out, when people would not use the proper
names in their posting.  Sometimes it would take a little while to
sort out the discussion properly.  There were even some articles which
would contain references to both versions improperly.

This discussion has at least made people more aware of the names of
the two versions, if nothing else.  For that alone it has been worth
the "bandwidth".

And, we all know that the BS will never stop with something as simple as
this.  It's the "net", you know!

Cary
--
_______________
Cary Petterborg					   (801)582-5847 x6627
Evans & Sutherland Computer Corp.  Simulation Division   SLC, UT 84108
UUCP: ...!uunet!sim.es.com!cpetterb  *NET: cpetterb@javelin.sim.es.com
_______________
Not everything that counts can be counted.  Not everything that can be
counted counts.   - Charles Garfield
Newsgroups: comp.unix.bsd
From: dhirvela@icaen.uiowa.edu (Dave Hirvela)
Newsgroups: comp.unix.bsd
Subject: Gateway 486 EISA
Date: 7 Apr 92 19:51:12 GMT
ath: icaen.uiowa.edu!dhirvela

Anyone had any experiences running on the Gateway
486 EISA setup's with a 340 MB Adaptec controller ?
 
From the looks of it on paper, it wouldn't work
due to the eisa bus, but it there a work around ?
 
And also how about the same setup for linux ?
 
If not, is anyone working on making it so ?
 
At todays's prices, the Gateway system is an
excellent route towards a good box for unix.

Thanks...
 
Dave

:wq

-- 
Any opinions expressed are obviously wrong.  * dhirvela@icaen.iowa.edu
Save Ferris !  Use only optical media !      * dhirvela@umaxc.weeg.uiowa.edu
Try Telemate-PC and save feeping creatures ! * Booster Gold in mail on:
"I don't think that word means what you      * grind.isca.uiowa.edu login:
 think it does." _The Princess Bride_        * iscabbs - Try it today !!!
From: mmitchel@digi.lonestar.org (Mitch Mitchell)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1 boot block mods.
Summary: delay loop needed in wdbootblk.c to boot Toshiba 5100 w/200MB disk
Keywords: 386BSD wdbootblk.c
Date: 13 Apr 92 16:47:33 GMT
Organization: DSC Communications Corporation

I had to make some changes to wdbootblk.c to get it to boot from a new
Quantum Peripherals 200MB hard disk on my Toshiba 5100.  Specifically,
the loop at "readblk:" needed a delay between accesses to the disk status
register.  I've no idea why -- the 200MB disk is faster than the standard
40MB that came with the 5100 (and which booted fine). 

Note: I have the 0.1 distribution disk but 0.0new sources so the diffs
      to wdbootblk.c may be out of date


*** wdbootblk.c.std	Mon Apr 13 11:19:03 1992
--- wdbootblk.c	Mon Apr 13 11:21:11 1992
***************
*** 146,151 ****
--- 146,155 ----
  
  	/* check to make sure controller is not busy and we have data ready */
  readblk:
+ 	movl	$0x0000000f,%ecx
+ dwait:	NOP
+ 	loop dwait
+ 
  	movl	$ IO_WD1+wd_status,%edx
  	inb	%dx,%al
  	NOP
-- 
* {letni | egsner | mic | supernet}!harlie!mitch     Mitch Mitchell      *
* {uunet | texsun | sulaco}!digi!mmitchel      Voice Mail (214) 519-3257 *
* mmitchel@digi.lonestar.org                     FidoNet: 1:124/4115.224 *
Newsgroups: comp.unix.bsd
From: jbev@iscden.jbsys.com (Jim Bevier - J B Systems)
Subject: Updates suggestion
Organization: J B Systems on HiPeak, Morrison, Co.
Date: Tue, 7 Apr 1992 04:10:34 GMT


I think it about time for the next update.  I am not a directly
connected ftp user so TB+ is what I have to do.  I hope the
next set of updates will be in addition to the current "disk"
set.  Such as update.01 and newboot.01.  This would mean that
we would only have to get a new boot floppy image and a new
update floppy.  I think this would be best.  Else I would have
to download ~18mb of stuff again.  Please give us small users
a break.  

Thanks,

Jim Bevier
jbev@jbsys.com
-- 
+=+     From the mountains of Colorado:   jbev@jbsys.com      +=+
+=+           when it's not snowing, the sun is shining       +=+
+=+     Jim Bevier    -   J B Systems   (303)-697-1038        +=+
+=+         10136 Horizon View, Morrison, CO 80465            +=+
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.unix.bsd
Subject: Re: 4.4 filesystems
Date: 15 Apr 92 22:15:46 GMT
Organization: Lawrence Livermore National Laboratory

| From: nc00@eurotherm.co.uk (Neil Corlett)
| 
| 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?

  You're probably thinking about the "Log File System" put together by
Margo Seltzer and Keith Bostic last summer.  (Or, in Keith's words:
``What I did on my summer vacation ...'')

  The log file system is optimized for large amounts of writing (as
compared with the "Fast File System" which is optimized for reading).  I
don't believe that the LFS sacrifices much (if any) performance on
reading, but at this point I don't want to say anything more since I
can't find my documentation.

Casey
Newsgroups: comp.unix.bsd
From: chip@tct.com (Chip Salzenberg)
Subject: Re: To make 386bsd coexist with DOS partitions??
Date: Wed, 08 Apr 1992 18:59:06 GMT
Organization: TC Telemanagement, Clearwater, FL

According to l00017@eeyore.stcloud.msus.edu (Networking Research):
> I like the way that Mach 2.6 deals with this on the 386.  You have
>only one Mach partition in the DOS partition table, but within that
>partition you have a standard BSD style disklabel...

SCO's scheme is similar, and I like it.
-- 
Chip Salzenberg at Teltronics/TCT  <chip@tct.com>, <73717.366@compuserve.com>
      "Informix 4GL is not a 4G, and it's barely an L."  -- John Tombs
From: s871780@minyos.xx.rmit.oz.au (Antony Suter)
Newsgroups: comp.unix.bsd
Subject: Re: Recompiling the bootcode. Fix for my PC
Date: 13 Apr 92 15:46:24 GMT
Organization: RMIT Computer Centre, Melbourne Australia.

u8acb@ohm.york.ac.uk (Alex Barclay) writes:

>I can get the thing to boot off the floppy by... Wait for it...

>1) Telling the BIOS that the HD isn't present so it doesn't try to boot from it

I believe that Advanced AMI bioses have a CMOS config option specifying
which drives and the order in which to boot. You can set it to 'A: C:' or
'C:' etc. Look at yours, its probably 'C:' ! If you dont know how to get to
your CMOS setup... 1) Be careful changing it! 2) Press the 'DEL' key just
after the memory count before the rest of the boot is completed. (cold boot).
Enter advanced CMOS setup. 3) Be careful changing it! 4) Be very careful
changing it!


-- 
Antony Suter			s871780@minyos.xx.rmit.oz.au
Melbourne, Australia		antony@werple.pub.uu.oz.au
"Call me Jack, stranger things have happened!"
Newsgroups: comp.unix.bsd
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: The great BSD name-off...
Organization: NeoSoft Communications Services -- (713) 684-5900
Distribution: usa
Date: Mon, 13 Apr 1992 16:09:03 GMT

In article <id.57VO.87G@ferranti.com> peter@ferranti.com (Peter da Silva) writes:
>"Free S D" or "Freenix".

Pnix or Penix, because I like the thought of a really obscene-sounding Unix...
-- 
-- Email info@NeoSoft.com for info on getting Internet access.
     "Trust me.  I know what I'm doing." -- Sledge Hammer
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: 386BSD - correct destination for bin & src floppies ?
Keywords: 386BSD destination directories
Date: 7 Apr 92 07:27:43 GMT
Organization: HCS GmbH, Hamburg, Europe

hi,

after installing the binary and source floppy disks, it seems to me, that
all this stuff gets installed at some very strange places (/bin/usr/bin etc).

as i'm new to bsd-ish unix, can somebody give me a hint where to put all this
into the right places ?

hellmuth
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
Newsgroups: comp.unix.bsd