HDTenEightyP/NetNews huggingface dataset:
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: FP exceptions
Date: 2 Sep 92 16:52:40 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

Can someone give me some info on floating point exceptions. A program I
have, which works fine on other unix boxes and even worked on 386bsd
0.0, has now decided to give fp-exceptions under 0.1. If I can get
enough help I'll track the problem down but at the moment I don't even
know what the possible causes of exceptions are?

I couldn't use install because of an fp-exception so there may be some
difference with my board. If so, I'm going to have to find a fix.
Since this didn't happen with 0.0 does anyone know what has been changed
as this would be a good place to start.
-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr
+++
From: cappucci@crs.cl.msu.edu (Chris Cappuccio)
Newsgroups: comp.unix.bsd
Subject: Silo Overflow
Date: 1 Sep 92 17:49:01 GMT
Organization: Michigan State University


 Some guy wrote to comp.unix.bsd:
> And also why do I get "com1 silo overflow" when
> I am using com2?
 
Actually a silo is a tall hollow tower used to store grain. In a silo overflow
the machinery that fills the silo with grain has failed to notice that the
tower is full allowing grain to overflow. This is only dangerous when the
access doors are closed and locked which causes a backup into the filling
machine.
 
A silo is also a store which sells home electronics at a discount. The problem
with a silo overflow in this case is when there are too many silos in
operation in a single area causing a lose of discount offerings because the
competition has been eliminated by the excess silos.
Newsgroups: comp.unix.bsd
From: arnej@Lise.Unit.NO (Arne Henrik Juul)
Subject: [386bsd] FIX: Truncating when appending over NFS 
Followup-To: comp.unix.bsd
Reply-To: arnej@lise.unit.no
Organization: Norwegian Institute of Technology
Date: Fri, 28 Aug 92 02:42:29 GMT

Thanks to Ian Donaldson, I found - and fixed - the bug
which causes files to be truncated when opened for append via
NFS in certain configurations.

He said (some articles ago):
 > 
 > I fixed this exact bug in an ancient NFS port a few days ago (on a
 > SVR3.2 machine actually).  The problem was that the NFS server wasn't
 > interpreting the sattr information provided in the "NFS create" call
 > properly.
 > 
 > One field of sattr is the file size.  When you do creat() of the above
 > form, SunOS sends the file size attribute as -1 over the wire which
 > should mean to the server "don't change the file size".  The server is
 > probably ignoring this field and truncating the file unconditionally
 > (at least thats what the server I worked on did).
 > 
 > The fix was trivial... just recognize the size attribute and if -1,
 > leave the file size alone, otherwise truncate to the specified value.
 > 
 > Ian D

And this was exactly what was wrong. The file was always truncated if
it existed. The reason why it only happens when used from certain
NFS clients, is that some clients does not do a NFS create request at
all if the file already exists.

So everybody who are just waiting to run their 386bsd machines as file
servers, this is your patch :-)

*** nfs_serv.c.orig	Fri Aug 28 04:34:35 1992
--- nfs_serv.c	Fri Aug 28 04:40:29 1992
***************
*** 550,556 ****
  
  /*
   * nfs create service
!  * now does a truncate to 0 length via. setattr if it already exists
   */
  nfsrv_create(mrep, md, dpos, cred, xid, mrq, repstat, p)
  	struct mbuf *mrep, *md, **mrq;
--- 550,557 ----
  
  /*
   * nfs create service
!  * if it already exists, just set length
!  * do NOT truncate unconditionally !
   */
  nfsrv_create(mrep, md, dpos, cred, xid, mrq, repstat, p)
  	struct mbuf *mrep, *md, **mrq;
***************
*** 588,595 ****
  	VATTR_NULL(vap);
  	nfsm_disect(tl, u_long *, NFSX_SATTR);
  	/*
! 	 * Iff doesn't exist, create it
! 	 * otherwise just truncate to 0 length
  	 *   should I set the mode too ??
  	 */
  	if (nd.ni_vp == NULL) {
--- 589,596 ----
  	VATTR_NULL(vap);
  	nfsm_disect(tl, u_long *, NFSX_SATTR);
  	/*
! 	 * If it doesn't exist, create it
! 	 * otherwise just set length from attributes
  	 *   should I set the mode too ??
  	 */
  	if (nd.ni_vp == NULL) {
***************
*** 654,660 ****
  		else
  			vput(nd.ni_dvp);
  		VOP_ABORTOP(&nd);
! 		vap->va_size = 0;
  		if (error = VOP_SETATTR(vp, vap, cred, p)) {
  			vput(vp);
  			nfsm_reply(0);
--- 655,661 ----
  		else
  			vput(nd.ni_dvp);
  		VOP_ABORTOP(&nd);
! 		vap->va_size = fxdr_unsigned(long, *(tl+3));
  		if (error = VOP_SETATTR(vp, vap, cred, p)) {
  			vput(vp);
  			nfsm_reply(0);

--
Arne H. Juul  --  arnej@lise.unit.no  --  University of Trondheim, Norway










Newsgroups: comp.unix.bsd
From: kilroy@mik.uky.edu (Paul S. Kilroy)
Subject: I need a patched dist.fs disk
Keywords: bsd
Organization: University Of Kentucky, Dept. of Math Sciences
Date: Thu, 3 Sep 1992 13:28:57 GMT

-> I'm posting this again because the subject got messed up last time..

Hi  all,
 	
	Does anyone know where I can download(ftp) a fully-mostly
    patched dist.fs file I only have 80mb and cannot keep recompiling
    the kernel, mostly I am looking for the fixed bugs in: man -k, com
    ports and ps.

thanks

--
                       -Paul   (kilroy@mik.uky.edu)
Newsgroups: comp.unix.bsd
From: Benjamin Z. Goldsteen <ben@rex.uokhsc.edu>
Subject: Did AT&T win?
Originator: usenet@essex.ecn.uoknor.edu
Date: Fri, 4 Sep 1992 16:35:03 GMT
Reply-To: Benjamin Z. Goldsteen <benjamin-goldsteen@uokhsc.edu>
Organization: University of Oklahoma HSC, R&E Computing


   Acording to the release notes, BSD4.4 will be in two versions --
Encumbered and Lite.  The Encumbered version requires a AT&T license.
Does this mean that AT&T won?

I am really pissed.  I want BSD4.4, but I don't want an AT&T license.

I reading this right?

Thanks

Does this mean that AT&T won?

I am really pissed.  I want BSD4.4, but I don't want an AT&T license.

I reading this right?

Thanks
From: raz@socs.uts.edu.au (The Inimitable Raz)
Newsgroups: comp.unix.bsd
Subject: Problems with telnetd
Date: 30 Aug 92 00:19:28 GMT
Organization: Computing Sciences, Uni of Technology, Sydney.

Greetings all.

I am having problems with using NCSA Telnet for DOS to access
386bsd. Basically when telnet in all works OK. When I enter Tip,
things work OK (ignoring Silo overflow messages which I uunderstand
are a seperate problem altogether). When I leave Tip, the session appears
to lock up by virtue of innumerable LFs being sent to the session. 

Nate Williams (many thanks!) has suggested that I recompile telnetd
with KLUDGELINEMODE, however I don't have sufficient space to extract the
src or etc distributions at this point in time. Would some kind 
individual care to recompile it for me and make it available for ftp
(or E-Mail it)> Has someone done so already?


--
Bye for now.
         - Raz           

raz@socs.uts.edu.au   (Roland Turner)   (OH) 61 2 580 2888
From: paoletti@cps.msu.edu (David R. Paoletti)
Newsgroups: comp.unix.bsd
Subject: backup w/ compression for UN*X?
Date: 3 Sep 92 01:54:37 GMT
Organization: Dept. of Computer Science, Michigan State University
Originator: paoletti@pacific.cps.msu.edu

Does anyone know of any software for UN*X, 386BSD or otherwise,
that does on-the-fly compression?  Thinking of looking into
writing my own, or getting some 386BSD people together to help,
as soon as I get my new machine built with enough HD space to
re-compile 386BSD...  This would be really nice for people with
floppies, or even people who want to save on tapes.

I realize that this isn't the standard UN*X way to do backups,
but a compressing dump program would be really useful to students.

Dave Paoletti :)
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: WD Ethernet Card not found on warmboot
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Wed, 26 Aug 1992 17:43:27 GMT

In article <1992Aug25.165542.5689@gateway.novell.com>,
  terry@thisbe.npd.Novell.COM (Terry Lambert) writes:

| In article <veit.714724604@du9ds3>, veit@du9ds3.uni-duisburg.de (Holger Veit) writes:
| |> Which system calls do you want to make "loadable"? It is an interesting idea
| |> to add features but it makes the software that rely on it unportable.
|
| Given a uniform underlying interface, everything else would have no problem
| running.

What Terry is saying, I think, (Interpreting Terry is always risky ;-) )
is that ``loadability'' and ``portability'' are orthogonal issues:
and example of this is (I know, I know) VMS, where gobs of the kernel
are loadable images, and can be dynamically loaded (and
possibly---shudder---unloaded or reloaded) during the life of the
system.  I know; I wrote part of a loadable system image.

As long as the *interface* to the services are standard (i.e. portable)
loadable OS features can be portable also.

-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM







-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
From: sb@next.neuro.emory.edu (Stephen O. Berger)
Newsgroups: comp.unix.bsd
Subject: Re: X386 and Diamond Stealth: not solution
Date: 3 Sep 92 14:54:27 GMT
Reply-To: sb@next.neuro.emory.edu

> 
> I had just made up my mind to buy a Diamond Stealth when I heared about  
all
> this trouble. Well, I am looking for cards from other vendors now.
> So maybe you should give them a list of people who are _not_ going to  
buy a
> card from them, unless they change their policy.
> If you are doing so feel free to put my name on it.
> -- 
> Andreas Klingler
> asklingl@informatik.uni-erlangen.de
>        I'd love to help you out... Which way did you come in?


  I was just about to buy a Diamond Stealth also, but not now that
I've heard about diamond's uncooperative attitudes.  With the rate
that technology changes these days, you'd think that companies
couldn't afford these kinds of policies.



  Steve Berger (sb@onripx.neuro.emory.edu)
From: sp_pm@space.alcbel.be (Paul Moore)
Newsgroups: comp.unix.bsd
Subject: Problems building olvwm on SunOS 4.1.2
Date: 1 Sep 92 15:28:31 GMT
X-Received: by usenet.pa.dec.com; id AA14903; Tue, 1 Sep 92 10:51:20 -0700
X-Received: by inet-gw-1.pa.dec.com; id AA02164; Tue, 1 Sep 92 10:50:42 -0700
X-Received: from ub4b.buug.be by mcsun.EU.net with SMTPid AA28051 (5.65b/CWI-2.174); Tue, 1 Sep 1992 19:50:27 +0200
X-Received: from alcbel.UUCP by ub4b.buug.be (5.65c/ub4b_02)id AA03582; Tue, 1 Sep 1992 19:50:24 +0200
X-Received: from se.alcbel.be by alcbel.be (4.1/SMI-4.1)id AA23949; Tue, 1 Sep 92 17:25:45 +0200
X-Received: by se.alcbel.be (5.57/SE_03)id AA23211; Tue, 1 Sep 92 17:29:11 +0200
X-Received: from btmpj9.space by space.alcbel.be (4.1/SMI-4.0)id AA06148; Tue, 1 Sep 92 17:28:31 +0200
X-To: comp.unix.bsd.usenet

Hello,

I believe that there is a separate newsgroup for SunOS, but I no longer have
direct access to News, and I can't recall what it's called.

Anyway, I've been trying to build olvwm 3.2 using olvwm3.tar.Z and the two 
patch files, located on export.lcs.mit.edu:/contrib. I've encounted two 
problems:

1. I can't compile ol_button.c, due to the unknown symbol OLGX_MORE_ARROW.
   Since this symbol appears not to be used anywhere else, I simply commented
   out the two lines making use of this symbol. 

2. During, the linker cannot find the library Xext in the directory
   /usr/openwin/lib. Is this a missing library on our system configuration?
   
Can anyone help me, please?

Thanks, Paul
Newsgroups: comp.unix.bsd
From: sitongia@hao.ucar.edu (Leonard Sitongia)
Subject: Re: [386bsd] does the ethernet device have a /dev entry?
Reply-To: sitongia@hao.ucar.edu (Leonard Sitongia)
Organization: High Altitude Observatory/NCAR, Boulder CO
Distribution: usa
Date: Thu, 3 Sep 1992 02:29:20 GMT

In article <1992Sep3.014444.28578@ncar.ucar.edu>, sitongia@hao.ucar.edu (Leonard Sitongia) writes:
> I'm all confused about why my system wont recognize the 3C503 ethernet
> 
> So, is the problem the IRQ number?
> 

No.

Well, after stuggling for some time, I thought it was time to post.  Well,
I should have know I should have struggled more.  I didn't think the I/O
Base and memory base jumpers were relevant under Unix, but of course they
are!  When I saw the correspondence in the config file line for ec0, I
rejumpered the board, and now it works!

Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: How to rebuild x386 under 386bsd?
Date:  3 Sep 92 10:11:49 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung
Keywords: 386BSD x386

In <8414@sirius.ucs.adelaide.edu.au> cagney@cs.adelaide.edu.au (Andrew Cagney - aka Noid) writes:

>I'm trying to rebuild the x386 server and am having problems with the
>system include files being missing (eg termio.h, there is a termios.h).
>I can't find the missing include files in the basic 386BSD distribution.

>Are there any problems in re-building the x386 server under 386BSD or
>have I simply missed something obvious?

>Any help would be appreciated

>					Andrew Cagney
>					cagney@cs.adelaide.edu.au

Maybe you don't have the 386bsd.cf config file that comes with a patch kit 
applicable to X386 1.2E for 386bsd usage. In this case imake includes the
config for i386 which is most likely a sysV configuration. There is a 
file of about 76K size named 386BSD.X386-1.2E.diff (on agate?, at least 
here 134.91.4.132 (ftp.uni-duisburg.de) /pub/unix/386bsd-0.1/unofficial/ports/X386
where I found the 386bsd.cf file (among other essential things).
It may be overriden by a more recent patch to X386-1.2E.

The only small bug I found with compiling from the mit sources (after 
application of all the patches) were two SPACE characters at the end of
lines in an Imakefile in a PEX subdirectory, which cause the make break
in this location. You'll find out very soon.

Hope that helps

Holger

-- 
|  |   / Dr. 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"
Newsgroups: comp.unix.bsd
From: arnej@Lise.Unit.NO (Arne Henrik Juul)
Subject: Re: lockd on 386BSD
Reply-To: arnej@lise.unit.no
Organization: Norwegian Institute of Technology
Date: Mon, 24 Aug 92 03:35:40 GMT

In article <1992Aug23.205117.5204@fcom.cc.utah.edu>,
 terry@cs.weber.edu (A Wizard of Earth C) writes:
 > In article <BtFxC8.3r0@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
 > >
 > >	Well, still no luck in being able to ">>" (append) properly
 > >	to a BSD partition NFS mounted to my Dell system.  Tried all
 > >	sorts of different mount options, tried different shells, etc.
 > >	Append works ok on a Novell 3.11 mounted NFS partition, and another
 > >	SYSVR4 (AT&T) system.  Now, I have noticed that 386BSD is not
 > >	running any sort of lock daemon, i.e. lockd.  Not even any mention
 > >	of it in any of the man pages having to do with NFS.
 > >	Is this normal?
 > 
 > 1)	lockd is an addon.  It's normal to not have it.  You may want to
 > 	add it on, though.

But you probably don't want to write it, I don't :-)
NFS and file locking are - well - somewhat anathema.


 > 2)	The append failure is not a result of NFS.  It's a result of a rather
 > 	loose interpretation of the "a" and "a+" modes in POSIX 1003.1.  You
 > 	would be better off fixing the shell, or you're bound to repeat the
 > 	performance later with some other box.

I do not understand this comment - would you care to explain further?
I have read the Standards (1003.1 and ANSI C), and they seem pretty
clear to me.

Anyway, I will assert that it IS an NFS problem. The following
program:


#include <sys/file.h>
main() 
{
  int fd;
  
  fd=open("afile", O_CREAT|O_WRONLY|O_APPEND);
  write(fd, "testing\n", 8);
  close(fd);
}


Will truncate the file "afile" when you mount FROM an NFS server on a
386bsd system ON some operating systems (at least SunOS seems to have
this problem, and probably lots more).

This is a bug *somewhere* in NFS, and the big question is: SunOS or
386bsd?  Personally I'd bet that SunOS was the problem here, but
that's only my gut feeling that Sun are unable to implement their own
protocols according to spec.

The problem does NOT occur when I use the file system via NFS from a
system running Ultrix, or from a m88k system running System Vr3.2.

We also have nearby a box running DEC OSF v1.0, which I *think* has the
same problem, but I am unable to test this just now.

I hope that someone will be able to trace this one down, but if not,
I'll have a go at it sometime next week.

Regards,

Arne H. Juul  --  arnej@lise.unit.no  --  University of Trondheim, Norway
From: ghe@ruhets.rutgers.edu (Guangliang He)
Newsgroups: comp.unix.bsd
Subject: Hardware Configuration to run 386BSD
Date: 1 Sep 92 02:40:04 GMT
Organization: Rutgers Univ., New Brunswick, N.J.


I am interested to know what is needed to run a 386BSD system
comfortablly. A 33 MHz 486 system? How much of RAM? 8 Meg enough? 16?
Harddisk? How much to hold all bsd (including source and manual)? What
if including latest version of X-window systems. Of course, I would
like to have some space left to do programming.

Please email the advise. I will summerise if there is enough interest.

Thanks a lot.

Guangliang He
ghe@physics.rutgers.edu
Newsgroups: comp.unix.bsd,comp.bugs.4bsd
From: elh@netcom.com (Ed Hudson)
Subject: Re: 386BSD kernel bugs w/fixes
Date: Mon, 24 Aug 92 00:41:06 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

	i installed the patches from Mr. Greenman (except #4) and saw this
	performance speed-up when running 'make depend' for the kernel
	rebuild (virgin compile/xxx directory):

	without patch:	60.9u 58.1s 4:45.87 41.6% 0+0k 0+0io 0pf+0w     (make depend)
	with    patch:	61.7u 53.8s 2:17.82 83.8% 0+0k 0+0io 0pf+0w
				    ^^^^^^^ ^^^^^

	for both trys, the machine was otherwise idle.
	this is more than a 2x improvement in wall-clock time.
	thanks Mr Greenman!

	hdware:	486-25, 16meg, Maxtor 8380, adaptec 1542


	-ed hudson
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: custom disk partitioning (as0)
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sun, 30 Aug 92 19:15:30 GMT


I still have not solved the problem (due to lack of answers from the net :)
that I cannot boot my 1GB M2266S-512 disk with AH1542A.

Terry Lambert (Terry, are you listening?) hinted that he wanted to work on asboot
to look at the partitions of the as disk.

It seems to me that presently only the standard installation (5MB swap)
is possible. I have partitioned my disk with 32MB swap, 64 MB root, rest /usr
but when I then boot the disk, it hangs.

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

Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Re: Compiling 386bsd-0.1 on < 40Meg ( I've done it)
Organization: Curtin University of Technology
Date: Mon, 31 Aug 1992 00:28:53 GMT

terry@cs.weber.edu (A Wizard of Earth C) writes:

>In article <colin.715158768@marsh> colin@marsh.cs.curtin.edu.au (Colin Manning) writes:
>>	Now that I've compiled the kernel, how do I make a bootable floppy?

>	I need to put this in the FAQ.  The procedure is as follows:
[Procedure deleted]

O.K. thats the way I've done it, but instead of striping the kernel I deleated
some of the less important files.

BUT,  I boot from a 3.5in disk, and wanted to be able to use the full 1.44 Meg.
I should have mentioned this in my original post, but I didn't - sorry.
Someone mentioned cat-ing fdboot and bootfd to the device, but I can't remember
if it was the raw or block device, or what partition.  Before anyone jumps on
me about not reading the previous posts our server has lost everything prior to
about two weeks ago.

Colin



>					Terry Lambert
>					terry_lambert@gateway.novell.com
>					terry@icarus.weber.edu
>---
>Any opinions in this posting are my own and not those of my present
>or previous employers.
>-- 
>-------------------------------------------------------------------------------
>                                                       terry@icarus.weber.edu
> "I have an 8 user poetic license" - me
>-------------------------------------------------------------------------------
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: ado@ibg1.ibg.sub.org (Christoph Adomeit)
Subject: Setting dial-in line to 8N1 ?
Organization: ibg
Date: Mon, 31 Aug 1992 21:28:12 GMT

Hi everybody,
i have not much experience with (386)bsd yet.
How can I set my dial-in line to 19200 8 bit, no parity, 1 stop bit ?
It seems to work at 7E1 by default.
I suppose this requires an entry in gettytab, but what is the syntax ?
Thanks
	Christoph

BTW: Why do I always get a "com1 silo overflow" ? com1 is not even
connected, I use com2 for communication.
-- 
Origin: It's not a bug, it's a feature !
From: randyc@soda.berkeley.edu (Yen-Pang Randy Chou)
Newsgroups: comp.unix.bsd
Subject: How to disable "^S"(suspend) while using tip?
Date: 27 Aug 1992 09:16:54 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
Distribution: world
NNTP-Posting-Host: soda.berkeley.edu

Hi there,

Does anyone know how disble "^S" (suspend) while using tip?  Also, everytime 
I dial in to school and use emacs, I need to press "^p" twice before the 
cursor moves up.  Is that because I'm using tcsh at home?  Is there anyway
I can disable it too?

---Randy
From: slix@svcs1.UUCP (Bill Miller)
Newsgroups: comp.unix.bsd
Subject: whatis broken?
Keywords: whatis
Date: 4 Sep 92 03:28:32 GMT
Organization: Silicon Valley Computer Society, Sunnyvale, CA

Recently, it seems that the whatis command is broken in 386bsd.  I do
remember it working (I think) but every time I run it I get a "segmentation 
fault - core dumped, and a core.whatis file appears in my cwd.  If it's
really not broken, perhaps the binary got munged at some point since I 
did the install.  If so, can someone mail me the whatis source, and I'll
compile it (to davidfox@west.darkside.com).
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Newsgroups: comp.unix.bsd
Subject: Re: Installation adventures and other magic, (a cry for help!!!)
Date: 4 Sep 92 09:07:09 GMT
Organization: Nanyang Technological University - Singapore
X-Newsreader: Tin 1.1 PL4

eddy@aludra.usc.edu (George Edmond Eddy) writes:
: bad sector flag entry.  

Ya, this is the mistake. I did it myself.
: 
: 	*I think this may have been a mistake*????
: 
: rebooted and IT WORKED!!! gee what clever guy, i thought i was.
: 
: 
: So now i set out to extract bin01, had to use /usr/tmp because
extract only works with /tmp
: i just extracted by hand.  zcat | unompress | cpio -pdalmu.

this is completely wrong;
should be 
cat bin* | uncompress | (cd /; cpio -idialmu )
: 
: it completed with no complaints, however when i rebooted, i 

before you reboot, run 
sh install.bin ( or something),
if it failed, 
cd /dev
sh MAKEDEV


--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
Newsgroups: comp.unix.bsd