HDTenEightyP/NetNews huggingface dataset:
From: tim@serss0.fiu.edu (Timothy Walker)
Newsgroups: comp.unix.bsd
Subject: Troubles installing 386BSD
Date: 31 Jul 92 17:28:40 GMT
Followup-To: comp.unix.bsd
Organization: Florida International University, Miami

This is a desperate plea for help. I have a Zenith 386/SX-16 with 6
of RAM, an 80MB hd that because of ZBIOS is only 76MB. I have successfully
installed 386BSD on a Z386/20, and booted the Tiny disk in another machine
with the exact same configuration. I have already deleted my DOS partition,
and I would like to use the whole drive for BSD, in order to create a patched
kernel for the machine that is already working. I don't remember the exact 
drive that I have installed, but it is an IDE 80M (Possibly Maxtor). Any help
would be greatly appreciated

BTW...It works pretty well on the Z386, but that damn com port bug is a problem.

--Timothy R. Walker
--Florida International University
--North Miami Computer Services
--tim@serss0.fiu.edu	- Internet
--tim@servax.bitnet
From: guest@pegasus.com (Guest)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD 0.1 release
Date: 19 Jul 92 14:10:27 GMT
Article-I.D.: pegasus.1992Jul19.141027.3845
Organization: Pegasus,  Honolulu

>>It's also on gatekeeper.dec.com, and probably other mirrors (but not
>>yet ftp.uu.net).
>
>ftp.uu.net will probably never be a real mirror site;
>they refuse to carry the binaries, as well as the sources,
>and therefore (In the release notes) the Jolitzes encourage *NOT*
>getting it from uunet...

There have been indications that UUNET has an interest in BSDI.  If
this is true, then it's not surprising that they are somewhat
obstructionist towards the spread of 386BSD.

Their claims about not carrying binaries are, of course, ludicrous
and false.
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject:  NFS (mount hangs)
Keywords: NFS mount  
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sat, 25 Jul 92 15:22:07 GMT


Does the initial kernel (what you have when install has been run, the hard disk is booted and the bin01 files are installed) have NFS built in?

If no, discard the rest of my question. 

In case it has NFS then why does it hang when I want to

    mount host:/u /mnt            ?

 

--Chris
-----------------------------------------------------------------
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

Newsgroups: comp.unix.bsd
From: wutcd@hrz.tu-chemnitz.de (Joerg Wunsch)
Subject: Re: sendmail.cf help for a sendmail novice
Keywords: sendmail,uucp,aarg
Organization: tu-chemnitz
Date: Fri, 31 Jul 1992 11:24:14 GMT


Hi all,
i tried to mail to James Saker, but:

------------------------------ Start of body part 1

This report relates to your message: Subject: Re: sendmail.cf help,
  Message-ID: <9207310748.AA06968%bonnie>,
  To: jsaker@cwis.unomaha.edu (James R. Saker Jr.)
        of Fri, 31 Jul 1992 11:43:39 +0000

Your message was not delivered to   jsaker@cwis.unomaha.edu
        for the following reason:
        Unknown Address
        Nameserver error for cwis.unomaha.edu: Non existant
        host/domain (NXDOMAIN) 

------------------------------ Start of forwarded message 1

Hi Jamie;-)
i'll try to help you. But, i don't have a mail connexion on 386BSD
for now, only on a bigger box. Nor have i a release 0.1 currently,
but i guess sendmail.cf is same as in 0.0

Say, your internet relay is mailman.omahug.org (in internet address),
its uucp node name relative to your machine be mailman.uucp, and your
own machine name is funny.uucp (uucp nodenames are limited to 7 alpha-
numeric chars due to some ancient U**Xes with 14-char file names).

Include the following lines near the top:
# my uucp hostname
DUfunny
# my uucp aliases
CUfunny

# local uucp connections
CVmailman.uucp

# local domain name
DDuucp

# internet/UUCP/csnet/bitnet relays
DAmailman.uucp
DRmailman.uucp
DCmailman.uucp
DBmailman.uucp

...and delete all the CN entries, leaving only one blank CN line,
since you don't have a NIC-registered host (i assume).

Care for mailman.omahug.org, it must resolve your addresses (in From:
and Reply-to: lines) to one of the forms

	jamie%funny@mailman.omahug.org, or
	funny!jamie@mailman.omahug.org

unless funny.uucp is registered in the global uucp maps anyway. This 
fact is my problem, too, so my return addresses are invalid:-(

	Hope you can succeed, enjoy
	J"org


ps: Please DO NOT reply to the return path, some mailer clobbers it.
    Only reply to that address:

+------------------------------------------------------------------+
|  joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de                  |
|------------------------------------------------------------------|
|  J"org Wunsch                    |  If anything can go wrong...  |
|  Textil Computer Design GmbH     |                   - it WILL.  |
|  R"ahnitzgasse 18                |                               |
|  D-O-8060 Dresden (F.R.Germany)  |                (Murphy's law) |
+------------------------------------------------------------------+


------------------------------ End of forwarded message 1

--
J"org Wunsch		         joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de
Textil Computer Design GmbH
R"ahnitzgasse 18, D-O-8060 Dresden
                              If anything can go wrong, it will. (Murphy's Law)
From: sb380@cs.city.ac.uk (Andy Holt)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD
Date: 23 Jul 92 09:04:42 GMT
Organization: City University

In <3674@vidiot.UUCP> brown@vidiot.UUCP (Vidiot) writes:

>                It is virtually impossible to not have had access to a Unix
>system in one's career of computer science.  If that is allowed to stand,
>AT&T will win every time.  Yuch.
But that could wreck any AT&T claim to "trade secret" status - I suspect
_far_ too many people have seen the code for such a claim to stand. 

Andy

Andy Holt // City University Computer Unit
Newsgroups: comp.unix.bsd
From: zxmsd01@mailserv.zdv.uni-tuebingen.de (Gunther Schadow)
Subject: 386BSD: TeX01 distribution
Keywords: TeX 386BSD i386
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Tue, 21 Jul 1992 15:56:02 GMT

Hi all TeXnicians (and those who want to become),

sorry if you missed TeX.386bsd.tar.Z at agate. It came across the
releasing of 0.1 and got lost.

>> Please stop getting on Chris' (cgd@agate) nerves with questions about TeX <<

I plan to release a full TeX distribution for 386bsd, which include
all files, necessary to run TeX (and not just to compile). Because
386bsd turned out to be user-friendly TeX for 386bsd will become so,
in order to save time for the non-TeXpert to compile, install and run
TeX successfuly.
  So far I got TeX compile and run successfuly, I had to install it
manually, and I got up most of the necessary files to the correct
place. I will fit the changes to web2c smoothly into the code, in
order not to lose tex3.14 compatibility. After this is done (in
approx. 2 or 3 days :-), I will release a distribution named TeX01.??
into the unofficial/ directory. This will be a base to start on
improving it.
  TeX01 will not yet be a complete release because we still lack of
appropriate dvi-driver. Since 386bsd is a low cost (though high
performance) operating system, we whant to keep care about low cost
devices to be supported too. Particularly we should provide dvi-driver
which support printers, other than HP*jet and IMAGEN, which of course
will be supported too.
  We need an easy graphics console support very soon, because
usability of both GhostScript and TeX suffers essentialy from not
being able to preview the output produced by either program. Since X386
for 386bsd will be very big and not easyly installed on screen
graphics devices other than tseng ET400 and paradise VGA, there is
some essential (and not trivial) part of work to be done.
  Anyone who is interested in helping to bring up TeX01 is greatly
appreciated. Feel free to mail me, especially if you already achieved
some progress in TeX for 386bsd.

regards
-Gunther

... now going to work ...
--
-------------------------------------------------------------------------------
Gunther Schadow,	          e-mail: Gunther@mailserv.ZDV.Uni-Tuebingen.DE
Sudetenstrasse 25,	          Phone:  (49) 7071/37527
7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA
From: rpw3@rigden.wpd.sgi.com (Rob Warnock)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd 0.1: non-reciprical ftp performance.
Date: 21 Jul 92 11:50:03 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

greg@ecse.rpi.edu (Greg) writes:
+---------------
|    In a previous post,  I complained of sluggish ftp performance (6-7 kb/sec).
| I discovered later that I can ftp files to a sun sparcstation ipc and get 
| 120-130 kb/sec. Ftping files from the same machine still yeilds only
| 6-7 kb/sec. This is quite repeatable.
+---------------

Such asymmetrical performances often indicate a TCP protocol mismatch. I'm
not sure what window sizes 386bsd is offering to the Sun, but I'm guessing
that the "Net-2" delayed-ACK code may be hanging you up. Try FTP from a
machine running a more recent TCP, and see if the problem goes away.

(We at SGI saw similar problems when we our new TCP increased its default
offered window. Suddenly some older TCPs started misbehaving.)


-Rob

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com
Silicon Graphics, Inc.		(415)390-1673
2011 N. Shoreline Blvd.
Mountain View, CA  94043
Newsgroups: comp.unix.bsd
From: wollman@sadye (Garrett Wollman)
Subject: Re: 386BSD - 8250 com ports
Organization: University of Vermont, EMBA Computer Facility
Date: Fri, 24 Jul 1992 00:45:16 GMT

In article <1992Jul23.125510.4250@ulrik.uio.no> toreh@bootes.sds.no (Tore Haraldsen) writes:
>The com driver (i386/isa/com.c) supplied with 386BSD seems to have
>support only for the "modern" chips, 16540 & 16550. The result is, it
>locks up my com ports of the "old" kind, 8250. Anyone got a "better"
>driver for the com ports?

Hmmm... I've got an 8250, and it works just fine.  (The machine's
built-in 16450 died, so we plugged in a card... and I *still* insist
on running SLIP over it.)

-GAWollman

-- 
   Garrett A. Wollman  = wollman@emba.uvm.edu = UVM is welcome to my opinions
                       =    uvm-gen!wollman   =
   That's what being alive is all about.  No deity, no higher goal
   exists, than to bring joy to another person.    - Elf Sternberg
Newsgroups: comp.unix.bsd
From: pim@cti-software.nl (Pim Zandbergen)
Subject: Re: Pax (was Re: Sorry, everyone, but I'm cpio clueless...)
Organization: CTI Software BV, The Hague, The Netherlands
Date: Tue, 21 Jul 92 23:21:22 GMT

karl@NeoSoft.com (Karl Lehenbauer) writes:

>It was funded by Usenix, and can be found about anywhere on the net.
>It's also /usr/5bin/pax on your Sun, /usr/bin/pax under SCO.

It's also /usr/lbin/pax in ISC Unix, and /usr/bin/pax in AIX 3.2
for the IBM RS/6000.
-- 
Pim Zandbergen                      domain : pim@cti-software.nl
CTI Software BV                     uucp   : uunet!mcsun!sun4nl!ctisbv!pim
Laan Copes van Cattenburch 70       phone  : +31 70 3542302
2585 GD The Hague, The Netherlands  fax    : +31 70 3512837
From: pfaffman@pilot.njin.net (Jay Pfaffman)
Newsgroups: comp.unix.bsd
Subject: Questions: tip, src install problems, kermit, rz, crypt library
Date: 30 Jul 92 23:30:56 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

I managed to get tip to work, but what term type do I tell the Sun I'm
using?  What are those "last message received XXX times" errors about?

Anybody got kermit 5a (?) going?  Is the vt10[02] emulation good?
Is there a better term program?  MS-Kermit is very nice, but I hope to
be leaving that behind.

rz gets *lots* of checksum errors with my 9600 modem.  The modem is
doing error correction, so that I don't think *that's* the problem.
Is BSD too slow to keep up?  Will a 16550 (?) UART help?

extract complained that it couldn't find src01.install.  Why not?
Should I worry?  Why isn't extract a script so that I can fix it when
it breaks?

I understand why a real crypt wasn't included, but Linux has one.
Shouldn't it be easy to plug it in?  What will have to be recompiled
besides login, su, & passwd? (crypt, I guess:-)

Oops, one more.  I've got a DCA ethernet card; I don't know anything
else about it.  It's not recognized on boot-up.  Is there any chance
that I can do something easy or am I likely SOL?
-- 
Jay Pfaffman, Computer Coordinator        pfaffman@pilot.njin.net
Dwight-Englewood School, 315 E. Palisade Ave.                      
Englewood, NJ  07631-0489                 201-569-9500
Newsgroups: comp.unix.bsd
From: dc@stars.gsfc.nasa.gov (Dave Cottingham)
Subject: What kind of tape is OK w/ 386BSD?
News-Software: VAX/VMS VNEWS 1.4-b1  
Reply-To: dc@cobi.gsfc.nasa.gov
Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics
Date: Tue, 28 Jul 1992 22:20:00 GMT

Time has come for me to buy a tape drive, and I want it to be something
386BSD can deal with, and something I can afford.  INSTALL.NOTES gives
two options: QIC-02 or SCSI.  I can't find a SCSI tape drive at a
reasonable price (where reasonable would be within a factor of two of
those Colorado Mountain System guys, 120 Meg for $250), so I guess that
leaves QIC-02.  There was a note on this group recently telling somebody
that his tape didn't work because he had the wrong kind of QIC-02, but
after looking through the installation docs and the new FAQ list I can't
find any mention of which QIC-02 devices are ok, or indeed any hint that
some are not.  Can someone point me toward a list of 386BSD compatible
tape devices, so I'll know that what I'm buying will work?

Thanks,
Dave Cottingham
dc@cobi.gsfc.nasa.gov
Newsgroups: comp.unix.bsd
From: vixie@pa.dec.com (Paul A Vixie)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: DEC Network Software Lab
Date: 21 Jul 92 19:00:35

>> [If AT&T is that worried about everyone having a license, why haven't they
>> gotten uunet/dec/etc. to pull the Net-2 sources out of the public archives?]

i'm sure that if they win their court case, they will try very hard to do that.
--
Paul Vixie, DEC Network Systems Lab	
Palo Alto, California, USA         	"Don't be a rebel, or a conformist;
<vixie@pa.dec.com> decwrl!vixie		they're the same thing, anyway.  Find
<paul@vix.com>     vixie!paul		your own path, and stay on it."  -me
Newsgroups: comp.unix.bsd
From: osynw@warp.mhd.montana.edu (Nate Williams)
Newsgroups: comp.unix.bsd
Subject: Re: Beginner's problems with 386BSD
Date: 26 Jul 92 17:43:58 GMT
Article-I.D.: coe.1992Jul26.174358.29102
Organization: /usr/local/lib/MYORG

In article <712169547snx@rama.demon.co.uk> steve@rama.demon.co.uk (Steve Entwistle) writes:
>
>
>1) How do I talk to my printer ? A /dev/lp device was not created when
>   I installed the binary distribution. Is it just a simple matter of
>   doing a mknod ? If so, what are the relevant major and minor devices
>   numbers ?
>
The line-printer device driver does not work as supplied.  There is a 
BETA version of the lpt driver on agate in unofficial/lpt-haug.patch (?).
I have gotten it to work sporadically on my machine, but I haven't found
out why it wouldn't work sometimes.  When it works, it works great, but
sometime's when I boot-up it recognizes it but it waits for some
acknowledgement from the printer which never comes.

>2) Should Mtools work straight out of the box ? If for example I issue
>   mdir a:  it produces the message init: open: No such file or directory.
>   Most of the other mtools commands produce similar messages.
>
cd /dev;sh MKDEV fd0 fd1;mk_devdb

This creates the specific special files that mtools needs to run.  I ran
into this and finally figured it out.

>4) How do I configure the system for UK local time ? I tried symlinking
>   /etc/localtime to /usr/share/zoneinfo/GB-Eire, but this puts the clock
>   about 8 hours ahead.
>

I wish someone could tell me how to get my clock correct too.  I have tried
various combinations of things, including re-linking the kernel with
the correct offset in the config file, re-compiling the tzinfo stuff.  I too
would like to know how to get the correct time.



Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home.  Anyone  interested
work: (406) 994-5991         |  in a used Sys. Admin., which alot of 
home: (406) 586-0579         |  good hacks left?
Organization: Carnegie Mellon, Pittsburgh, PA
Newsgroups: comp.unix.bsd
Date: Fri, 24 Jul 1992 12:20:31 -0400 
From: Sean.Levy@cs.cmu.edu
Subject: AT&T vs BSDI: email address?

Is there an email address inside AT&T to which complaints (as opposed to
termcaps :-) can be sent re their suit? Do any AT&T folks read
comp.sys.att (like the feedback you see in comp.sys.dec?)? I don't
normally read that group, and a quick perusal just now showed only one
post on this subject and no responses... any other suggestions for
e-channels to let them know how very displeased everyone is?

		-- Sean
--
Sean Levy, n-dim Group, EDRC, CMU, 5000 Forbes Ave, PGH, PA 15213
Email: snl+@cmu.edu, Phone: +1 412 268 5221, Fax: +1 412 268 5229
Newsgroups: comp.unix.bsd,misc.jobs.misc
From: orion@nuchat.nuchat.sccsi.com (Roland Dunkerley)
Subject: Re: AT&T sues BSDI
Organization: Eristic Rite In Software, Houston, Tx.
	<1992Jul25.222121.20426@socrates.umd.edu> <s6j1Hp4!q8@atlantis.psu.edu>
Date: Tue, 28 Jul 1992 08:37:53 GMT

>>>>> On 27 Jul 92 23:41:15 GMT, hvozda@wilbur.psu.edu (Eric Hvozda) said:

	|> In article <1992Jul25.222121.20426@socrates.umd.edu>
	|> ice@socrates.umd.edu (Fredrik Nyman) writes:
>Comments?

	|> Indeed!

	|> It is a shame companies can be so petty over such things
	|> when all poeple want to do is make a living...
I thought there was a precedent that no agreement you make with a
company can prohibit you from earning a living in your chosen
profession.  Hopefully someone will correct me if I have the details
wrong, but the particular case I am thinking of has to do with Greg
Wilcox (I think that's his name, it's been a while), the founder of
Alpha-Micro.  Anyway, he left DEC with tapes of an early version of
RSTS under his arm, founded Alpha-Micro selling systems based on the
LSI-11 processor with a re-arranged instruction set running AMOS, an
exact clone of RSTS.  The binary images were different due to the
re-arranged instruction set.  The court ruled that not only could DEC
not prohibit him from writing OS software since that was his primary
profession, but that if he had written RSTS once, he could therefore
write it again.  Of course, this was before look and feel, these days,
DEC could claim that he had infringed on the look and feel of their
software and probably win on those grounds.  Too bad Atari managed to
create the concept of look and feel, we'd certainly be better off
without it.  Of course, I can do without a Mac or Mac-related job just
fine...  Don't think I'll be buying anything from Lotus either.
--
"I still dream of Orgonon..."     ---    KaTe Bush, Cloudbusting
Fnord.                        Roland Pleasant Dunkerley III, KSC
South Coast Computing Services, Inc - Houston Public Access UNIX
orion@nuchat.sccsi.com               {uhnix1,uunet}!nuchat!orion
-- 
"I still dream of Orgonon..."     ---    KaTe Bush, Cloudbusting
Fnord.                        Roland Pleasant Dunkerley III, KSC
South Coast Computing Services, Inc - Houston Public Access UNIX
orion@nuchat.sccsi.com               {uhnix1,uunet}!nuchat!orion
From: james@raid.dell.com (James Van Artsdalen)
Newsgroups: comp.unix.bsd
Subject: 386BSD 0.1: pccons.c bug
Date: 26 Jul 92 06:17:59 GMT
Reply-To: james@raid.dell.com (James Van Artsdalen)
Organization: Dell Computer Corporation

I think there is a bug in the function kbd_cmd in pccons.c.

kbd_cmd waits for the 8042 input buffer to empty, and then writes a
byte destined for the keyboard.

kbd_cmd then waits for the 8042 input buffer to become empty again,
and then reads the output buffer.  This part is wrong: kbd_cmd should
wait for the output buffer to become full, rather than wait for the
input buffer to become empty.

I haven't tested this change.  I found the bug by inspection.

*** pccons.c.~1~	Sun Jul 26 01:12:26 1992
--- pccons.c	Sun Jul 26 01:13:36 1992
***************
*** 155,161 ****
  	
  	while (inb(KBSTATP)&KBS_IBF);
  	if (val) outb(KBOUTP, val);
! 	while (inb(KBSTATP)&KBS_IBF);
  	return (inb(KBDATAP));
  }
  
--- 155,161 ----
  	
  	while (inb(KBSTATP)&KBS_IBF);
  	if (val) outb(KBOUTP, val);
! 	while (inb(KBSTATP)&KBS_DIB);
  	return (inb(KBDATAP));
  }
  
-- 
-- 
James R. Van Artsdalen          james@bigtex.cactus.org   "Live Free or Die"
Dell Computer Co    9505 Arboretum Blvd Austin TX 78759         512-338-8789
Newsgroups: comp.unix.bsd
From: osynw@warp.mhd.montana.edu (Nate Williams)
Subject: Re: Beginner's problems with 386BSD
Organization: /usr/local/lib/MYORG
Date: Mon, 27 Jul 1992 18:09:42 GMT

In article <jnpotts.712255910@vincent1.iastate.edu> jnpotts@iastate.edu (James N. Potts) writes:
>I had a problem at first getting the correct time, but I finally got it to
>work.  I set my system clock to GMT, and linked /etc/localtime to the correct
>timezone (in my case, /usr/share/zoneinfo/US/Central).  Of course, now my DOS
>programs are a few hours off, but at least I get the correct time when I log
>onto my 386BSD system.
>
>James
>


It appears that I'm going to have to change my Real Time Clock to get
the correct time on my machine.  Some have sent me mail telling me to
re-make the kernel.  That didn't seem to make any difference.  
	Other have mentioned symlinking /etc/localtime to 
/usr/share/zoneinfo/US/Mountain, and that has me one hour too fast.  What
I *THINK* is happening is both the 386BSD code and my BIOS are both
correcting for Daylight Saving's time.  For the time being, I think I
am going to have to change my clock, but if I could figure out the format
of the zoneinfo data files, I think I could fix it so that it left the 
daylight savings time to my BIOS.  If nobody else figures it out, I will
probably look at it later, but it's not a big deal right now.  There are
more interesting bugs to fix. :-)

Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home.  Anyone  interested
work: (406) 994-5991         |  in a used Sys. Admin., which alot of 
home: (406) 586-0579         |  good hacks left?
From: storner@diku.dk (Henrik St|rner)
Newsgroups: comp.unix.bsd
Subject: Re: Setting up bootable DOS pertition by hand
Keywords: DOS
Date: 30 Jul 92 13:02:13 GMT
Organization: Department of Computer Science, U of Copenhagen

One line of attack that has worked for me is the following:

1) Clear all partitions off the harddisk.

2) Using FDISK from MS-DOS, create a "Primary DOS" partition that will
   be Your *only* DOS partition.

3) Create - using MS-DOS FDISK again - a "Secondary DOS" partition that
   will be used for BSD.

4) Using Norton's DISKEDIT or something similar, alter the byte indicating
   the partition type from 06 (Secondary/Extended DOS) to A5 (386BSD).
   (for the real hackers, edit absolute sector 0, changing the byte at
   offset 450/466/482/498 for partition 1/2/3/4).

5) The 386BSD 'install' program now recognizes the second partition as
   the 386BSD partition, and installs 386BSD there.

6) Use a DOS-based boot-partition switcher to replace the Master Boot
   record so You can select which partition to boot from as part of the
   booting proces. Several of these are avaiable at ftp archives such as
   wuarchive.wustl.edu / oak.oakland.edu / wsmr-simtel20-army.mil . If
   You cannot find one, I can e-mail or post one.
--
Henrik Storner (storner@diku.dk / storner@olivetti.dk)
Dept. of Computer Science
Univ. of Copenhagen, Denmark
Newsgroups: comp.unix.bsd