HDTenEightyP/NetNews huggingface dataset:
From: osynw@gemini.oscs.montana.edu (Nate Williams)
Subject: Re: Occasional system hangs
Keywords: nn
Organization: Montana State University
Date: Mon, 14 Dec 1992 16:14:24 GMT

In article <a0x9021N2ehg01@JUTS.ccc.amdahl.com> gab10@griffincd.amdahl.com (Gary A Browning) writes:
>In article <1992Dec11.210430.17335@coe.montana.edu>,
>osynw@gemini.oscs.montana.edu (Nate Williams) writes:
>> In article <1gaclpINN84v@hrd769.brooks.af.mil>
>> news@hrd769.brooks.af.mil (InterNet News) writes:
>> >-Time for more RAM I guess!
>> >>
>> >
>> >  I don't think more RAM will help.  I have 32M of RAM and and 32M
>> swap 
>> >partition.  It still hangs.  nroff is the usual culprit for me.
>> 
>> The fix for this is to fix G++, re-compile it, and then recompile
>> groff
>> with the fixed GCC.  The patch for g++ will be in the next patchkit.
>> [If I ever get it finished :-(]
>
>This might be a problem but are you sure it is not simply masking another?
>A bum compile of a user level program should never cause the system to hang.
>
Sorry I didn't make myself clear.  Yes, the REAL reason the system is hanging
is because the kernel has a leak.  However, groff has a leak in it which 
magnifies the kernel leak, and fixing groff at least allows the system
to last longer. 

Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home. 
work: (406) 994-5991         |  Keeper of the Unofficial 386BSD Bug Report
home: (406) 586-0579         |  Please send bugs and/or fixes you find.
From: jwp20406@uxa.cso.uiuc.edu (Jeffrey Palmer)
Subject: An interesting problem (and solution?)
Organization: University of Illinois at Urbana
Date: Sat, 19 Dec 1992 07:24:50 GMT


Hey all,

	I love 386bsd, but lately I have been having some very strange 
problems...  I was just windering if anyone else out there might have
an idea as to why in the world my system would be doing this...

	The problem first started when I attempted to install a 
second Western Digital 2200a 200 Meg drive in my 486-50 Gateway 2000
(which I've had no problems with, in relation to 386bsd).  I found
out quickly  that I needed patches, so patch away I did...  I tried
the barsoom patches, but they didn't work.  It seemed that they would
see only the initial drive on my controller, and instead of a second 
drive, all I saw was another image of the first.  Well, needless to say,
that didn't do me any good.  I installed the other 2nd hard-drive
patches from the unofficial directory at agate, and they worked like a charm.

	However, although I could now label and newfs my drive, whenever
I tried to mount or access the drive at startup, the label seemed to 
have a habit of either disappearing or causing the mmachine to hang
while loading.  Well,  since I just finished finals I decided to
dig around in 'ufs_disksubr.c'  I wanted to find out where exactly
my machine was crashing.  Now I know this sounds like a bogus way
to go about this, but I don't know too much about kernel debugging, 
so I put in some printf statements inbetween some lines that I thought
looked interesting.  Well, after a while I realized that this 
new kernel was able to read the label and mount and everything, no
problem.  I took out those printf statements just to be sure, and lo and
behold, the machine crashed when I attempted to do a 'disklabel -r wd1'

	I am guessing that there is a timing problem here, but like I said,
I am no Unix guru, just an intermmediate trying to get this system up.
So, I just wanted to let you know about this problem, and to ask
if anyone else has had this problem, and if there is a better way
to solve this problem that a bunch of printfs...

	Thanks!

		Jeff
		palmer@cs.uiuc.edu

-- 
Jeffrey Palmer                palmer@cs.uiuc.edu
------------------------------------------------
for life's not a paragraph
And death i think is no parenthesis
From: randy@chinet.chi.il.us (Randy Suess)
Newsgroups: comp.unix.bsd
Subject: Re: swapping on a second drive.
Date: 19 Dec 92 15:45:04 GMT
Organization: Chinet - Public Access UNIX

In article <1992Dec18.171556.3158@data-io.com> bachesta@pugsley.Data-IO.COM (Jim Bachesta) writes:
>This problem probably has been addressed on the net before, but I'm having
>a problem getting my swap space to work on my second drive. 

	Did you modify ioconf.c in the compile directory and duplicate
	the &wddriver line 34, incrementing the unit to 1 before
	compiling the kernel?  This is what is needed to get a second
	drive working at all.

-- 
	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
Newsgroups: comp.unix.bsd
From: swong@watserv1.uwaterloo.ca (Stanley Wong)
Subject: Install problems.
Organization: University of Waterloo
Date: Thu, 17 Dec 1992 08:07:12 GMT


I am having some problems with my installation of 386BSD.

First, I installed the binary distribution, but when it got to the end it
hung.  This occurred after the "Final installation" message.  It did not
ask me for a system name.  So I rebooted the machine and the system
banner came up and the info with all my equipment then this:

Automatic reboot in progress...
/dev/rwd0a: 2129 files, 26395 used, 295476 free (284 frags, 36899 blocks, 0.1% f
ragmentation)
starting network
starting system logger.
checking for core dump...
can't find device 0/1
Dec 17 03:05:59 savecore: can't find device 0/1
chmod: /dev/tty[pqrs]*: No such file or directory.
preserving editor files
clearing /tmp
standard daemon: update crond.
starting network daemons: routedBus error - core dumped
 printer sendmail inetd
Starting local daemons
Thu Dec 17 03:06:09 PST 1992

     386BSD (amnesiac) (console)

login:

Is my file system corrupt?  If so, can I fix it without reinstalling?  (I
lost all the bin01 files, they were in /tmp).  Also, what is the
device 0/1 not found?

Also had a problem with tip:

tip com2
/dev/com2:  permission denied
link down

Thanks for any help with these problems.

stan
swong@watserv1.uwaterloo.ca
Newsgroups: comp.unix.bsd
From: torvalds@klaava.Helsinki.FI (Linus Torvalds)
Subject: Re: 386BSD vs Linux: major differences?
Organization: University of Helsinki
Date: Sun, 20 Dec 1992 11:50:36 GMT

In article <davis.724817863@csrg2> davis@csrg2.ee.iastate.edu (Jim Davis) writes:
>						But I have wondered
>why there are two efforts to provide a free UNIX...is it just coincidence
>that two groups developed a distribution at about the same time?  or did
>they have different goals?  or is this a BSD vs. System-V thing?

It's just coincidence: I knew about 386bsd through DDJ, but it obviously
wasn't ready when I would have wanted it, so I just started on my own. 
If 386bsd had been ready one year earlier, I'd probably not have started
on linux at all, but used bsd instead - although I'm very happy with how
it all turned out. 

As to bsd vs sysv - no, nothing like that.  Linux isn't exactly sysv,
but has a lot of features from both camps, and looks a bit more like
sysv simply because POSIX generally leans in that direction. 

			Linus
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (& Murphey)
Subject: Re: More on pccons/XFree86 problems (keyboard hangs)
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Mon, 14 Dec 1992 15:56:33 GMT

>>>>> In article <1992Dec14.115444.12691@news.tu-graz.ac.at>, chmr@fstgds01.tu-graz.ac.at (Christoph Robitschko) writes:
Christoph> In article <1992Dec13.172900.451@ponds.uucp> rivers@ponds.uucp (Thomas David Rivers) writes:
>  Try it out yourself, inside of an X window, do a :
>
>     kill -1 `cat /var/run/syslog.pid`
>
>  and your keyboard will lock up.
>
>
>I will probably try and examine the stock pccons.c to determine where
>the problem can be corrected... but if someone has an idea/fix, feel
>free to beat me to it...
>
Christoph> The problem is that the pccons driver is used in two ways: first in 
Christoph> the standard way through pcopen() etc., and second as a console device
Christoph> through cnopen(). 
Christoph> The cn???() calls simply call the corresponding pc???() routines, which 
Christoph> is OK for open(), read() and write(), but not for close(), because
Christoph> the close routine is only to be called when the LAST reference to 
Christoph> the device was closed. But when the last reference to the console device
Christoph> is closed (as happens when you kill or SIGHUP the syslogd), cnclose()
Christoph> calls pcclose(), no matter if there are any references to the pccons
Christoph> device (such as the keyboard input for your shell or X server).
Christoph> pcclose() then thinks there is no more reference to it and disables
Christoph> keyboard input.

Christoph> One possible solution would be to modify pcclose() to only do the real
Christoph> close operation if there are really no more files open on it (A sort of
Christoph> reference count or reference bits for each device type is needed).

Another solution might be to ignore the close while the X server is
running:

diff -cb pccons.c~ pccons.c
*** pccons.c~	Mon Dec 14 09:07:08 1992
--- pccons.c	Mon Dec 14 09:07:52 1992
***************
*** 241,246 ****
--- 241,250 ----
  	int flag, mode;
  	struct proc *p;
  {
+ #ifdef XSERVER
+ 	if (pc_xmode)
+ 		return (0);
+ #endif /* XSERVER */
  	(*linesw[pccons.t_line].l_close)(&pccons, flag);
  	ttyclose(&pccons);
  	return(0);


Christoph> I don't know if any of the replacement pccons (or codrv) drivers fix this.

codrv does fix this and should be supported in the next XFree86
release.  Rich
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD install program - where is it?
Date: 18 Dec 92 06:07:58 GMT
Distribution: usa
Organization: Amdahl Corporation

In article <1992Dec17.172923.19040@rwwa.COM>, witr@rwwa.COM (Robert
Withrow) writes:
> In article <1992Dec17.134832.9812@moxie.hou.tx.us>,
>  hackney@moxie.hou.tx.us (Greg Hackney) writes:
> 
> | I wonder why? It sure would be nice to have to make a customized
> | installation process!
> 
> According to Lynne, it was not something that she would be proud to
> release, and she wanted to wait until she had developed something
> better.

I can understand this.  I have pieces of software that I wrote like that.

Is she working on improvements now?  If not, maybe we had better find
someone to write a new one up.

-- 
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,comp.os.linux
From: adam@netcom.com (Adam J. Richter)
Subject: Re: 386BSD + LINIX + GNU + X11R5 on CDROM - let us know what you want!
Organization: Yggdrasil Computing, Incorporated
Date: Sat, 12 Dec 1992 05:57:25 GMT

In article <1992Dec11.225241.1941@nb.rockwell.com> wade@nb.rockwell.com (Wade Guthrie) writes:
>The Linux cd-rom drivers may support [the Rockridge extensions]
>already, but if you don't already
>HAVE Linux up and running on your system, the point is moot.  I would not
>like to see the Rockridge extensions, 'cause then I wouldn't be able to 
>load Linux from the CD on a system that currently has only DOS.
>
>Wade Guthrie
>wade@nb.rockwell.com

	My Linux/GNU/X CD is a counter-example to your claim.  The CD
uses the Rockridge extensions, but you can install it on a system that
"has only DOS" or that has no software at all.  This is because the
distribution includes a boot floppy that boots linux and then mounts
the CD.

	Even on a distribution that did not include a boot floppy,
the inclusion of Rock Ridge extension information would not make
it any harder to install.  After all, you can still read a Rockridge
disk with a system that only understands iso9660, although the filenames
will appear in iso9660 level 1 (DOS style) or iso9660 level 2 (similar
to VMS) formats.

	Do you understand that the CD that Jordan is talking about
doing is a pure source code CD?  An unpacked linux source tree wouldn't
be that useful in installing Linux on your system.  If all of the
Linux binaries in the world disappeared tomorrow, I imagine that there
would be a lot of work involved in rebuilding a complete working Linux
system again.  Installing Linux from a CD that contains only source
code is essentially the same problem.

	I do, however, see two uses for the ability to look at a Rockridge
disk with binaries, like mine, under an iso9660 reader that doesn't
support the Rockridge extensions (in particular, DOS).  On a subsequent
version of my Linux/GNU/X CD, I'll probably include rawrite.exe so that
it will be possible to recreate the boot floppy, and I'll probably also
include some kind of runlinux.exe program so that it will be possible
to boot directly to linux from DOS.  Those are about the only real uses
that I see for the underlying non-Rockridge iso9660 file system on my CD.
As for Jordan's CD, I don't see any reason why he shouldn't include
the Rockridge extensions, unless it breaks some buggy iso9660 CDROM
reader or something.

-- 
Adam J. Richter				Yggdrasil Computing, Incorporated
409 Evelyn Avenue, Apt. 312		PO Box 8418
Albany CA 94706				Berkeley CA 94707-8418
(510) 528-3209				(510) 526-7531, fax: (510) 528-8508
adam@netcom.com				yggdrasil@netcom.com
Another member of the League for Programming Freedom (league@prep.ai.mit.edu).
Newsgroups: comp.unix.bsd
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Subject: Re: [386bsd] pcnfsd?
Date: Mon, 14 Dec 1992 21:08:31 GMT
Organization: SAS Institute Inc.


  I had no problems porting pcnfsd to 386bsd - gcc complained about
 a missing argument (the mode to open() if memory servers) but 
 other than that negligible change it worked straight away.

  Of course, to allow 386bsd to accept non-root mounts (which
 pc-nfs uses) you need to add the "-n" option to mountd (see /etc/rc,
 as well as the mountd man page.)

  After doing that, I had no problem using FTP Software's NFS product
 mounting 386bsd file systems.

       - Dave Rivers -
-- 
UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express
Xref: sparky comp.unix.bsd:10185 alt.suit.att-bsdi:661
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.bsd,alt.suit.att-bsdi
Subject: Re: AT&T/USL CD-ROM Review Process
Date: 14 Dec 92 16:21:11 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <1992Dec13.183240.23944@blaze.cs.jhu.edu>, bogstad@gauss.cs.jhu.edu (Bill Bogstad) writes:

| 	I'ld like to know why people think that USL won't sue the Jolitzes
| if they win against BSDI.  Is there something magically wrong that BSDI did
| that the Jolitzes didn't.  (Okay, BSDI charges money.)  Still, I'ld like
| 386BSD and the other freeware Unix clones to succeed to the extent that I
| can purchase support for them.  I'm quite happy to hack on my own system for
| fun, but when I go to work it would be nice to be able to use the same
| system.  Until I can safely trade some of my employers money for less
| hacking on the company time clock, I won't be able to do this.  I can
| understand that this might not be the primary goal of either Jolitz (386BSD)
| or Linus (Linux); but I would hope that neither one of them would mind their
| software being used for something besides hacking.  I predict that if it
| appears even remotely that 386BSD or Linux are starting to encroach on the
| commercial Unix market; USL will take any and all legal steps possible to
| stop their further distribution.

  Note that AT&T signed off on Coherent, even though the authors had
obviously seen AT&T code. If AT&T has reason to believe that there is
AT&T code in NET2, or paraphrased routines, or program structures, they
have the right and obligation to sue. Linux was clearly written from
scratch, as opposed to having been written based on AT&T code ant then
"cleansed." I don't think there's much comparison.

  For those who aren't up on legal positions, if the officers of a
company don't protect the assets of the company (like code and trade
secrets) the stockholders have the right to sue the officers to recover
lost profits. As in sue them personally. Without making any judgement on
the merits of the case, I can't imagine the owner of the code NOT
protecting it.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
From: sam_s@NeXT.com (Sam Streeper)
Newsgroups: comp.unix.bsd
Subject: Re: Want info on German Boot Manager thingy please
Date: 15 Dec 92 02:13:44 GMT
Reply-To: sam_s@NeXT.com

ricky@lindblat.cc.monash.edu.au (Mr RS Mcconachy) writes:
> A few months back (not long after the release of 0.1 386BSD in fact)
> a German getleman posted a note to this group about his boot manager
> program.  

The program you seek is "os-bs.asm", a turbo assembler program that creates an  
MS-DOS com file that writes a menuing boot record.  I ftp'd it from a site
in Germany (a very slow site, I might add...) but I didn't save the site name.
The author is Thomas Wolfram.

-sam
ps I should probably add that I am unable to mail this...

--
Opinions expressed herein are not those of my employer.  They're not even
mine.  They're probably wrong besides.  How did they get in here, anyway?
From: ptd2@po.CWRU.Edu (Palmer T. Davis)
Newsgroups: comp.unix.bsd
Subject: Re: Gateway 2000 problems?
Date: 12 Dec 1992 00:51:22 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: ptd2@po.CWRU.Edu (Palmer T. Davis)
NNTP-Posting-Host: thor.ins.cwru.edu


In a previous article, ted@usasoc.soc.mil (Ted Nolan) says:
>
>We happened to have a Gateway 2000 486DX-33 sitting in our lab, so I took
>the dist-fs floppy from the bootables directory and tried it out: no
>dice.  I also tried the new dist-fs from the unofficial/terry/new-bootables
>area on agate, but that didn't work either.  I think the floppy is OK, because
>I have tried it on another system here and it booted fine.

We have a Gateway 486DX2-50 that I just brought 386bsd up on last night.
The problem may be that you didn't turn off the memory caching; if it is
enabled, the kernel panics.  For what it's worth, the distribution I used
was taken from gatekeeper.dec.com.

>Does this mean I have to stop considering Gateway. . . ?

You don't have to, but you should; Gateway's designs are relatively rude
and annoying, and the only reason that I'm using ours is that it was
assigned to me.  Think of Gateway as the SCO of hardware vendors.  1/2 :-)
-- 
Palmer T. Davis      ___
<ptd2@po.cwru.edu>   \X/   cthread.  cthread_fork().  Fork, thread, fork!
From: trotter@enuxha.eas.asu.edu (Russell Trotter)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Small Question About 'su' and 'tip'
Date: 21 Dec 92 05:25:42 GMT
Organization: Arizona State University, Tempe, AZ

Hello All,
	I just d/l 386bsd for the first time and installed it
on my PC, applied all 58 (well, all except patch #47) of the
patches in Lambert's Patchkit (which kicks butt BTW :) ), rebuilt
the kernel and affected utils.  I also took the time to read
the 386bsd FAQ (on agate).  The FAQ said that to fix the 'tip'
'all ports busy' message one just has to recompile tip.  I tried this,
but I couldn't get it to work. Next question, when I log in as
a normal user (not root) then su (to become root), my machine just hangs
with no promt or anything and I am forced to reboot.  Any suggestions
as to these miniscule newbie inquiries would be most appreciated.
Thanks! 

Please reply via email to:     asu@panther.mot.com

Russ 
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Linux boots on Tandon but 386BSD doesn't 
Keywords: Hardware, Tandon, Architecture, install, boot
Organization: Weber State University  (Ogden, UT)
Date: Fri, 18 Dec 92 23:33:37 GMT

In article <1992Dec18.163714.24667@usasoc.soc.mil> ted@usasoc.soc.mil (Ted Nolan) writes:
>In article <1992Dec17.214418.552@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>>
>>If this is the "it just sits there looking dumb" problem, there's a NOP in
>>the wd boot code that dorks a register.  Use one of the Compaq disk
>>images.  These are available from the machine "rachel", the address of
>>which is in the FAQ.
>>
>
>Hello,
>
>Are you sure the address for rachel is in the FAQ?  If it's the FAQ from 
>agate in unofficial, I can't find it.  (And I'd really like to..)


The full address of the rachel archive is rachel.ibmpcug.co.uk.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: kaleb@jpl-devvax.jpl.nasa.gov (Kaleb Keithley)
Subject: Re: Dumb Question: Why 512 byte block?
Organization: Jet Propulsion Laboratory (NASA)
Date: Fri, 18 Dec 1992 18:31:44 GMT

>>Why is everything in 1/2 k block instead the BSD standard of 1024 byte blocks?
>>Yes, I know there is a '-k' switch, but it seems to me it should be
>>the otherway around.

The one answer I haven't seen yet, and the one that makes the most sense
to me, is that the Sector size on most disks, even today, is 512 bytes.

-- 

Kaleb Keithley                               kaleb@jpl-devvax.jpl.nasa.gov

From: reink@hpuamsa.neth.hp.com (Reinier Kleipool)
Date: Sat, 19 Dec 1992 15:53:22 GMT
Subject: Re: [386bsd] IDE disktab/driver...
Organization: HP-Sales Office-The Netherlands
Newsgroups: comp.unix.bsd

Hello, Youhave some stange problems, but the information you give
is not enough to help you...

>I just brought down 386bsd, and started to load it on my machine:
> 386SX/33, 2 Meg ram, mono, and a Western Digital Caviar 280 IDE drive.

>Here's the thing: I only get like 75 megs, and apparently that is
>because of the bizarrre way the kernal deals with IDE drives, by
>treating them as ESDI? 

Why you are getting only 75 megs is not clear to me. I have installed
386bsd on 120, 170 and 240MB IDE drives, and that works fine. Did you
use the install program? Did you commanded to use the whole drive for unix?
  As for the ESDI thing. 386BSD does not treat a drive as ESDI or IDE or
whatever. This just signifies that the HD controller is a 'standard' ISA
controller. The 'software side' of the contraller (registers etc..) are
the same for ST506, IDE and ESDI, so you can use the same driver for all
those controller types. (only the SCSI driver uses a different controller,
and therefore needs an other driver)

  This doesn't help you directly, but is is the best i can do with the
info you gave me. 

Reinier Kleipool
reink@hpuamsa.hp.hp.nl

Newsgroups: comp.unix.bsd