HDTenEightyP/NetNews huggingface dataset:
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: install 0.1 problems
Date: 23 Jul 92 14:06:42 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <1992Jul22.165732.7669@thyme.jpl.nasa.gov> kaleb@thyme.jpl.nasa.gov (Kaleb Keithley) writes:

>Onto my NEXT QUESTION:  I appear to have a corrupt file in the
>bin01 files -- the extract hangs.  My lowly SPARCstation doesn't have 
>cksum, just sum and /usr/5bin/sum, neither of which produce checksum 
>values remotely similar to those in the MANIFEST file.

>Can anyone point me to source for the cksum program, or even a binary
>that I could run prior to trying to extract?  I've searched the 
>INSTALL.NOTES and all the directories on TinyBSD, and all the directories
>on my favorite ftp archive -- did I miss it somehow?

>Thanks in advance.

I've an unpacked version, modified to compile without cdefs.h, working
at least on SunOs 4.1 in
ftp.uni-duisburg.de (134.91.4.132) in /pub/unix/386bsd.01/unofficial/cksum/*

Holger

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: OS Boot Select 1.32 - yet another boot menu program
Date: 31 Jul 92 18:47:45 GMT
Organization: Amdahl Corporation, Sunnyvale CA

> In article <1992Jul30.165820.2328@tfs.com>, julian@tfs.com (Julian
> Elischer) writes:

> |> It looks like uuencode, but uudecode won't touch it.

Worked fine for me.
-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
Newsgroups: comp.unix.bsd
From: boot@donald.osf.org (Bruce Bauman)
Subject: problems with 0.1
Reply-To: boot@osf.org
Organization: Open Software Foundation
Distribution: comp
Date: 29 Jul 92 14:36:25

I've been having some problems with 0.1, specifically kernel hangs. I
can't get far enough to build a kernel with KDB configured in, so I am
stuck. I'm assuming the "distributed" 0.1 kernel doesn't have kdb in,
because <ctl>-<alt>-<esc> has no effect. Is there a kernel somewhere
that I can use for debugging.

BTW, my kernel hangs seem to be timing related - if I slow my 486
machine down from 33 MHZ to 18 MHZ, the problems sometimes go away.

I'm also having problems with kmem_map too small, but I can remove
memory to solve that problem :-).

-- Bruce
--
Bruce Bauman	email: boot@osf.org		phone: 617-621-7205
Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142
From: sxjcb@orca.alaska.edu (Jay C. Beavers)
Newsgroups: comp.unix.bsd
Subject: libcompat.a missing?
Date: 31 Jul 92 02:22:28 GMT
Followup-To: comp.unix.bsd
Organization: University of Alaska Computer Network

Ok, I've just installed the etc and src distributions and I've been trying
to compile the games that come with etc, however, on a number of games I've
run into an error that libcompat.a is missing.  I checked /usr/lib and it
isn't there nor is the source located in /usr/src/lib.  What am I missing?

______________________________________________________________________________
                                        |    jay@seaspray.uacn.alaska.edu
Jay C. Beavers                          |    sxjcb@orca.alaska.edu
University of Alaska Computer Network   |    sxjcb@alaska.bitnet
________________________________________|_____________________________________
From: ben@rex.chb.uokhsc.edu (Benjamin Z. Goldsteen)
Newsgroups: comp.unix.bsd
Subject: Should I get the AT&T source?
Date: 27 Jul 92 23:07:08 GMT
Organization: Engineering Computer Network, University of Oklahoma, Norman, OK, USA


    The place where I work can get the AT&T souce for like $200 (.edu).
However, I don't want to be limited by this.  Will I be prevented
from writing in an OS in the future (theoretically?)  What if I don't
sign a non-diclosure agreement, but "somehow" gain access to the sources?
What are the implications of this?

Thanks
Newsgroups: comp.unix.bsd
From: erc@unislc.uucp (Ed Carp)
Subject: Re: AT&T sues BSDI
X-Newsreader: Tin 1.1 PL4
Organization: Unisys Corporation SLC
Date: Tue, 21 Jul 1992 23:59:46 GMT

sef@kithrup.COM (Sean Eric Fagan) writes:

: One of the complaints was about the 1-800-ITS-UNIX (I didn't know ITS was
: unix compatible... hmm), which is no longer a valid phone number, seeming,
: to me at least, that that part of the complaint is either resolved or no
: longer relevant.

Huh?  You mean that Pande Inc. (which has the number 1-800-SOS-UNIX), as well
as anyone else that has UNIX in their phone number, has to change it?
That's utter nonsense...
-- 
Ed Carp, N7EKG		erc@apple.com	<-- preferred email address!
"In wildness is the preservation of the world."  - Henry David Thoreau
** Member, Linux port team - uucp division ** :)   801/269-8125
Newsgroups: comp.unix.bsd
From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz)
Subject: Re: 386bsd-0.1
Keywords: 386bsd
Organization: University of Michigan EECS Dept., Ann Arbor
Date: Mon, 27 Jul 1992 16:53:21 GMT

In article <cproto.712235554@marsh> cproto@marsh.cs.curtin.edu.au (Computer Protocol) writes:
>Hi there,
>
>after running 386bsd-0.0 since march, 0.1 has not much to offer. Here
>is a list of problems, the first is really a showstopper:
>
>2 - if fsck fails at the second partition, init continues rather then 
>reboot

You only need to reboot if fsck fails on the root partition.

>
>3 - the com driver looses characters (0.0 hasn't)

Get the new com.c (I believe it is at agate, but check past postings).

>
>5 - pccons.c driver delays entered characters until the next char is
>typed (sometimes) (0.0 hasn't)

I haven't seen this and I've been using 0.1 quite a bit.

>
>6 - cp is stupid in single user mode ???? (0.0 wasn't)

0.0 was also (along with mv and possibly rm)

  -Dan
From: tmh@keks.first.gmd.de (Thomas Hoberg)
Newsgroups: comp.unix.bsd
Subject: SCSI tape drive not accessible
Date: 23 Jul 92 02:19:36 GMT
Distribution: comp
Organization: GMD-FIRST, Berlin

I managed to get the "Tiny BSD" floppy accross the modem and got
386BSD installed on my system (486/33, 16MB, ET4000/8514, AHA1542, 1GB
Wren VII + 88MB Syquest SCSI drives, Tandberg TDC3800 QIC 525 SCSI
Streamer). The SCSI disks are at targets 0+1, the tape drive is at
target 4. On boot up, only the first disk is recognized. Trying to
read off /dev/ras1a seems to attach the Syquest drive. Any attempt to
read /dev/ras4a results in an error. cat </dev/ras4a returns "bad file
descriptor", cpio -itvc </dev/ras4a returns "error 9". All other
targets return "sense errors" with lots of status data (mostly zeros).
Does 386 support only certain tape drives? The drive works fine with
ISC UNIX, DOS (various programs) and OS/2 (modified GTAR).

BTW: I use a small partition booter wholly contained within the master
boot block. Works like a charm! I can select any OS to boot at
startup. In theory I could even boot off a second disk drive (the OS's
secondary bootstrap has to support that, though (e.g. DOS doesn't). If
there is interest, I could post it together with a (DOS based)
installation program.

I like what I have seen so far. If only I could get the tape drive to
work, so  I can install the rest of the system...

Cheers for the 386BSD team!
---
Thomas M. Hoberg   | Internet: tmh@first.gmd.de
1000 Berlin 41     |           tmh@cs.tu-berlin.de
Wielandstr. 4      |
Germany            | BITNET:   tmh@tub.bitnet 
+49-30-851-50-21   |
From: tinguely@plains.NoDak.edu (Mark Tinguely)
Newsgroups: comp.unix.bsd
Subject: Re: Questions/problems with 386BSD 0.1
Date: 29 Jul 92 22:19:54 GMT
Article-I.D.: plains.19427
Organization: North Dakota State University

In article <1992Jul29.042244.29277@umbc3.umbc.edu> cs481a07@umbc5.umbc.edu (cs481a07) writes:

>problem 3: I noticed that anyone could run shutdown. the permissions were
>
>-rwsr-x--- owner root group operator. I changed the permissions to
>-r-x------ and anyone can still run it. (you get the shutdown: NOT super-user)

 This is a big security hole. In 0.0, a VOP_ACCESS was used, but root always
 succeeds (and tries to execute anything). But the check for a single execute
 bit it wrong too. I put the VOP_ACCESS back but also checked to make sure
 at least one execute bit is on before root can execute the file. I also
 checked if the filesystem was mount for execution:

*** kern_execve.c	Wed Jul 29 14:48:13 1992
--- kern_execve.c.orig	Wed Jul  8 19:07:57 1992
***************
*** 120,129 ****
  		goto exec_fail;
  
  	/* is it executable, and a regular file? */
!         if ((ndp->ni_vp->v_mount->mnt_flag & MNT_NOEXEC) ||
! 	   (VOP_ACCESS(ndp->ni_vp, VEXEC, p->p_ucred, p)) ||
! 	   ((attr.va_mode & 0111) == 0) ||
! 	   (attr.va_type != VREG)) {
  		rv = EACCES;
  		goto exec_fail;
  	}
--- 120,126 ----
  		goto exec_fail;
  
  	/* is it executable, and a regular file? */
! 	if ((attr.va_mode & VEXEC) == 0 || attr.va_type != VREG) {
  		rv = EACCES;
  		goto exec_fail;
  	}
Newsgroups: comp.unix.bsd,comp.os.linux
From: boyd@cs.unca.edu (Mark Boyd)
Subject: Re: Query: Drivers for AHA >1522< ?
Organization: University of North Carolina at Asheville
X-Newsreader: Tin 1.1 PL3
Date: Tue, 21 Jul 1992 15:12:40 GMT

I also have a 1522, which I purchased used a year or so ago.  At that
time I asked Roy Neese ( I think I have his name right ) of Adaptec
about the differences between the 1520 and the 1540 series.  Roy is
active in comp.periphs.scsi and is an excellent source of info on
Adaptech controllers. He said that the major difference is that the
1540 series has its own, on board microprocessor.

Now that is a big difference, from a programmers point of view,
because it means that the 1520 drivers have to interact with the SCSI
interface chip(s) directly, while the 1540 drivers interact with the,
much higher level, interface provided by the microprocessor and its
firmware. As a result, it is much harder to write drivers for the
1520 series.

I think some programming information is available from Adaptech's
technical Support BBS ((408) 945-7727 8 data bits, no parity, one stop
bit ), but I'm not sure that it is enough to write a driver. I think
Roy did mention a technical manual ($$) which does have all the
necessary information. I decided not to pursue this, but I hope Chip
will 8^). It would be nice to have source for 1522 driver.

	Mark
From: lyndon@ampr.ab.ca (Lyndon Nerenberg)
Newsgroups: comp.unix.bsd
Subject: Re: Is AT&T listening?...
Summary: Yes, and they're still a bunch of twits.
Date: 24 Jul 92 17:40:08 GMT
Organization: Boycott AT&T!

mgrjtb@nextwork.rose-hulman.edu writes:

> I have seen people from apple.com very active in the Linux newsgroup, which  
> would seem like treason to me, and ADM and Intel people in the comp.sys.intel 
> group, but we haven't heard from AT&T here.

> AT&T, are you listening?

Yes, they're listening. cjc@ulysses.att.com was kind enough to point
out that one of my previous postings about the copying of /bin/true
source code was incorrect. It is in fact, as he stated in e-mail, the
BSD version of /bin/true that contains 'echo 0'. The System V version
of /bin/true instead contains five lines of copyright notice, one line
of version control information, and a colon. 

What really impresses me about System V's version of /bin/true is that
it only took them four revision of the code to get a single character
shell script right. Now THAT's the sort of intellectual property I would
hire a building full of lawyers to defend!

AT&T: just say NO.
From: geoff@East.Sun.COM
Newsgroups: comp.unix.bsd
Subject: USL/AT&T vs. BSDI - what about The Book?
Date: 27 Jul 92 17:47:49 GMT
Organization: SunSelect
NNTP-Posting-Host: tyger.east.sun.com

In an earlier posting, someone noted that USL/AT&T had suggested that
BSDI *must* have made improper use of USL sources because they were
able to develop the BSDI kernel so quickly. Since most of the relevant
kernel mechanisms are described in great detail in "The Design and
Implementation of the 4.3BSD UNIX Operating System" (Leffler et al,
Addison-Wesley, 1989/1990), this complaint would seem preposterous...
unless, perhaps, USL/AT&T believe that the book describes "UNPUBLISHED
PROPRIETARY SOURCE CODE OF AT&T". So, have they complained about the
book? Any of the authors care to comment?

Geoff
--
Geoff Arnold, PC-NFS architect | In the years after WW2 it was said that Oxford
  (geoff.arnold@East.Sun.COM)  | philosophers had found a cure for atheism.
         SunSelect,            | Young people coming up as atheists soon found
  a Sun Microsystems Business  | that they no longer knew what to disbelieve...
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 24 Jul 92 07:21:12 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <1992Jul21.131433.16450@ntuix.ntu.ac.sg>,
eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:
> In article <1992Jul21.104627.3353@mel.dit.csiro.au
smart@wanda.mel.dit.CSIRO.AU (Robert Smart) writes:
>
>> This is insanity. Surely this will be thrown out of court.
> Who is going to defend NET/2?

The person/organization AT&T might sue in the future over NET/2.

BSDI is not responsible for NET/2 so you cannot sue them to have it
purged.  As I see it, the NET/2 distribution is not in question here.
What can happen is a precedent that goes against using the NET/2
sources in a working O/S. (or, of course, AT&T could try to sue
UCB.  But I doubt it, since it is going to be hard to explain why
they waited all these years).

Just my opinion.  I am not a lawyer.

Personally, I think AT&T is just trying to put BSDI out of bussiness.
They must know that BSDI is not capable of funding major legal battles
at this stage in its development.  Makes no difference if their case
will stand up in court - only that it not be thrown out on an early
decision.

I like the idea of sending letters of complaint to AT&T explaining
why you have requested changing your long-distance carrier.  Seems like
fair play in light of AT&T's tactics.

-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
From: anthony@csd4.csd.uwm.edu (Anthony J Stieber)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T sues BSDI
Date: 28 Jul 92 22:45:57 GMT
Article-I.D.: uwm.1992Jul28.224557.2546
Followup-To: alt.folklore.computers
Organization: Computing Services Division, University of Wisconsin - Milwaukee

In article <BZS.92Jul25162833@ussr.std.com> bzs@ussr.std.com (Barry Shein) writes:

>if their conception of this is pimply teen-agers looking roughly like
>Matthew Broderick in War Games running to their friends' houses with a
>black jacketed 5 1/4" floppy.)

But Matthew Broderick used 8" floppies in WarGames :-).

Is this where we can make jokes about doing things with hard disks
in embedded systems?
--
<-:(= Anthony Stieber	anthony@csd4.csd.uwm.edu   uwm!uwmcsd4!anthony
Newsgroups: comp.unix.bsd
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Re: 386BSD on ALR??
Organization: Iowa State University, Ames IA
Date: Fri, 31 Jul 1992 00:33:26 GMT

In <veit.712418327@du9ds3> veit@du9ds3.uni-duisburg.de (Holger Veit) writes:

>In <1992Jul29.122935.4015@nynexst.com> rjc@nynexst.com (Robert Casazza) writes:

>>ALR BusinessVEISA 386/33, 8Mb, 200M IDE Conner, Paradise SVGA,
>             ^^^^^

>Does the above really read EISA? If so:

>	N O  S U P P O R T  F O R  E I S A  A N D  M I C R O C H A N N E L

>	A R C H I T E C T U R E S  Y E T !!!

>Give it up.

386BSD does not yet work with EISA-specific CARDS.  It works perfectly
in my EISA box with ISA cards.

	G E T   A   C L U E!!!

EISA is not MicroChannel.  It is backwards compatible with ISA.

-- 
------------------------------------------------------------------------------
  Michael L. VanLoon                           Project Vincent Systems Staff
  michaelv@iastate.edu           Computer Engineering, Iowa State University
------------------------------------------------------------------------------
From: jbh@aii.com
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd-0.1: primary bootstrap (wdbootblk.c) problem & fix.
Keywords: 386bsd boot bootstrap wdbootblk.c
Date: 28 Jul 92 11:48:31 GMT
Organization: Automation Intelligence

In article <1992Jul27.192502.15727@gateway.novell.com> terry@npd.Novell.COM (Terry Lambert) writes:
>In article <greg.712261295@hibp1.ecse.rpi.edu> greg@ecse.rpi.edu (Greg) writes:
>>Terry, please reread my message. THIS IS NOT THE SAME BUG!!!!!!
>>This problem is in wdbootblk.c. The code contained in wd.c has not
>>even been loaded off the disk at the point when this hang occurs! 
>>To understand what is going on, study wdbootblk.c.
>
>	I think I goofed in recommending the wd.c fix for this problem;
>however, the status register being polled after the delay is wd_status,
>and I still believe that a canonical fix would be looking at wd_altsts
>instead.

  You have totally missed it ! wd_altsts is BOGUS period. Read your
IBM Tech ref. manual, the register is READ ONLY and only 4 bits wide. It
ain't good for anything when bieng read !!!!! Read the Western Digital
Manual, a read of this register is good only to provide a VENDOR ID number,
on a REAL W.D. chip it ALWAYS returns a FIXED value regardless of the
status of the controller. The 'patch' simply used wd_status to obtain the
REAL status of the controller ! This is the proper way!!!!!
>
>	Greg's delay loop will have the same effect -- that is, making sure
>the controller has finished it's reset prior to using it.
>

The DELAY loop method is still dancing through raindrops and is NOT safe
for ALL combinations of CPU-speed and MFM/RLL controllers.

======================================================================
Jim Huber   jbh@aii.com or ...!tarpit!jbh Voice (407) 661-7017
Automation Intelligence,Inc.
850 Trafalgar Court
Suite 200
Maitland, FL 32751
======================================================================
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Tue, 28 Jul 1992 14:23:41 GMT

In article <1992Jul27.164334.9376@nebulus.ca>, dennis@nebulus.ca (Dennis S. Breckenridge) writes:
| Randy, the way you donate to the cause is to buy a BSDi source license.

I am not certain that helps the ``cause'' of assuring the freedom of
the net2 code, but....

If you read USL's interrogatories, you might be interrested to note that,
unless the case is dismissed, BSDI will probably have to provide your name
and address to USL if you buy the BSDI code...

P.S., I'm not sure that the ``cause'' of assuring the freedom of the net2
code would not be better served by FTPing it from someplace or getting
a tape from Vix, or doing something that does not require your signing
*any* licence agreement.  Sending a ``donation'' to Jolitz would not hurt 
either.

P.P.S.  After reading the suit and interrogatories, I, for one, am convinced
that USL's ultimate goal is the suppression of *all* free BSD code, and that
BSDI is just a convienent ``point of attachment'' for them to begin this
task...  From this point of view, helping BSDI does not hurt, but it may
not help...

-- 
---
 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: peter@taronga.com (Peter da Silva)
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Organization: Taronga Park BBS
Date: Sun, 26 Jul 1992 18:18:46 GMT

In article <2cHS02Pi1bvx01@JUTS.ccc.amdahl.com> gab10@griffincd.amdahl.com (Gary A Browning) writes:
>What can happen is a precedent that goes against using the NET/2
>sources in a working O/S. (or, of course, AT&T could try to sue
>UCB.  But I doubt it, since it is going to be hard to explain why
>they waited all these years).

Since the source has been available for FTP for at least 3 years, and a smaller
subset available for even longer, how can they possibly prosecute? Trade
secrets, like trademarks, *have* to be defended to be retained. 
-- 
Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.unix.bsd
Subject: email read by corp higher-ups 
Distribution: world
Date: Mon, 27 Jul 92 13:26:33 GMT
Organization: Crynwr Software

In article <BRAD.92Jul26095134@caicos.Cayman.COM> brad@Cayman.COM writes:

      Sean.Levy@cs.cmu.edu writes:

      > Is there an email address inside AT&T to which complaints (as opposed to
      > termcaps :-) can be sent re their suit?

      A basic rule of business computer usage: the higher up in management a
      person is, the less likely they are to soil their fingers on a keyboard.

   I disagree.  Scott McNealy reads his email.  I know this for a fact.
   Most CEO's of small companies (like Cayman) read their email.

   I think you'd be suprised if you tried "telnet xxx.com 25; VRFY <ceo-name>".

That doesn't tell you if the CEO reads his/her mail, or if an
assistant reads it for him/her.

-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
Crynwr Software            Crynwr Software sells packet driver support.
11 Grant St.               315-268-1925 Voice   [ if mail bounces, forward it ]
Potsdam, NY 13676          315-268-9201 FAX     [ to uuadmin@uu.psi.com.      ]
Organization: Penn State University
Date: Thu, 23 Jul 1992 09:40:21 EDT
From: <NXS10@psuvm.psu.edu>
Newsgroups: comp.unix.bsd
Subject: Is it only for clone BSD?

I am not aware with the hardware requirement for 386BSD.Is it only for clone BS
D pc(as linux is)? I have a machine model 70/386,ps/2. Monitor type 8515,S/N
23-kp615.does it support microchannel architecture,or only At-bus machine?I'm c
urious to know wheather it will run on my machine or not.Thanks in advance.
Neena.
From: mike@pacsoft.com (Mike Stefanik)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Date: 23 Jul 92 17:05:18 GMT
Organization: Pacific Software Group, Riverside, CA
X-Newsreader: Tin 1.1 PL4

tal@Warren.MENTORG.COM (Tom Limoncelli) writes:
: USL has been publishing press releases saying that Windows NT is the
: real enemy, and they don't care who's Unix you buy, just as long as you
: buy something that looks like Unix... because they'd rather see people
: switch to Unix than Windows NT.

Of course.  Since USL has it's fingers in (nearly) all of the pies, they
really don't care who you buy the end product from ... they *are* getting
a piece of the action with every sale.
-- 
Mike Stefanik  mike@pacsoft.com  ...!uunet!pacsoft!mike  (+1 714 681 2623)
Pacific Software Group, Riverside, CA
Newsgroups: comp.unix.bsd
From: randy@chinet.chi.il.us (Randy Suess)
Subject: adding another swap partition
Date: Tue, 21 Jul 1992 12:05:40 GMT
Organization: Chinet - Public Access UNIX

	With 16 meg of memory, I am a little leary of having only
	a 5 meg swap partition.  I  installed 0.1 on another drive,
	then added it as the second drive, so it has another 5 meg
	swap partition defined.  However I can't get swapon(8) to
	add the wd1b partition.  Mumbles something about "device
	not configured".  I tried using disklabel to mark that
	partition as swap instead of unused (why does install mark
	wd0b as unused instead of swap?) but it didn't help.
	Anyone have any luck with a second swap partition?
-- 
	I am created Shiva the Destroyer; Death, the shatterer of worlds!
	Who is this dog meat who stands before me now?
	That's the biz, sweetheart.
Randy Suess					 randy@chinet.chi.il.us