HDTenEightyP/NetNews huggingface dataset:
From: rodeen@buddha.ncc.umn.edu (Rick Odeen)
Subject: Re: swap problems - Not Again!
Summary: Frustrating isn't it...
Organization: Nutrition Coordinating Center, University of Minnesota
Date: Fri, 14 Aug 1992 14:54:55 GMT

In article <NEAL.92Aug13080724@neal.ctd.comsat.com> neal@neal.ctd.comsat.com (Neal Becker) writes:
>I have a recent 386/4Mb with Wd1007V and 150Mb Micropolis EDSI drives.
>When 0.1 installed, I get "clean of page xxx failed" warnings.  A LOT.
>By the hundreds.

What you are experiencing is hitting a bad sector in your swap space.
This happened to me and the only way I've been able to get around it
for now was to move my swap space somewhere that didn't have bad sectors.
If you've been following the discussion on bad sectors on EDSI drives
there was method of discovering where you have bad sectors by doing
a dd if=/dev/wd0c of=/dev/null bs=512 conv=syn,noerror.  Grab a copy
of the unofficial FAQ (I think it's on agate), there is a good set of
instructions on how to install 386BSD manually, reinstall your system
with your swap space in a clean section of disk, leaving a gap between
probably your root partition and your swap partition (this is where the
bad sector is).  I was fortunate in that the bad sector on my drive
was close enough to the start of swap that I was able to relabel my
disk shrinking swap a little and leaving a gap where the bad sector was.

Another apprach people are having success with, if your controller
supports it, is to enable alternate sector mapping and do a new low
level format of your drive, this should make the drive to appear
defect free to 386BSD.

This whole bad sector issue seems to be a problem for a lot of people,
lets try to coordinate the effort and get this working.  Keep those
posts coming with any and all ideas and efforts!

-Rick Odeen

-- 
"MINIX costs $169, but the license allows  | Rick Odeen 
making two backup copies, so the effective | rodeen@buddha.ncc.umn.edu 
price can be under $60."                   | rutgers!umn-cs!buddha!rodeen
         - ast@cs.vu.nl (Andy Tanenbaum)   |
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: X386 mouse problems
Date: 18 Aug 1992 12:08:31 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

Folks,
I'm having problems with mouse support for X386 (386bsd). The
mose is configured as "MouseSystems". However, no input from the mouse
is accepted *unless* a shift, control or alt key is pressed while the mouse
actions occur.

Hmm. Coming to think of it, I may un-patch my com driver and try again..
Any hints ?

-Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd
From: fredw@mks.com (Fred Walter)
Subject: Re: building cnews 02may92 (not)
Organization: Mortice Kern Systems Inc., Waterloo, Ontario, CANADA
Date: Thu, 13 Aug 1992 15:53:15 GMT

jdb@bitcave.in-berlin.de (Joern D. Busch) writes:
>Trying to build Cnews 02may92 ...
>
>I give up for now.  Anybody?

I built it a while back. I don't remember all the stuff I had to do to
get it to build; I'm planning on putting it up (binaries and all) on agate
once I have time to figure out one last thing - why news that I post isn't
making it off the system. Maybe this week-end I'll have time to look
at it. If you send me email at home (fred@walter.uucp) I can email you
my build.def file and a list of comments on what I had to do to get it to
build.

	fred
-- 
Disclaimer: everything I write is my *personal* opinion and does not represent
or reflect the opinion of the company which employs me.
From: merlin@neuro.usc.edu (merlin)
Newsgroups: comp.unix.bsd
Subject: Re: ESDI disk performance under 386BSD
Date: 14 Aug 1992 12:09:06 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: neuro.usc.edu

In article <1992Aug14.170148.22228@dsuvax.dsu.edu> ghelmer@dsuvax.dsu.edu (Guy Helmer) writes:
# Having been running 386bsd 0.1 on a 25Mhz 386 w/ WD1007V-SE2
# controller connected to a Wren VI (330Mb) disk and 16Mb of memory,
# I've noticed that the system seems seriously disk-bound.  Any work on
# the disk drive seems to take forever - mkdir takes a few seconds to
# execute; extracting a tar file brings the system to a crawl.

Something else must be wrong -- I've got a 386-33, WD1007V-SE2,
Maxtor 8760E (676MB) which is fast as greased lightening -- may
be some other problem -- do you have enough memory -- maybe the
system is thrashing in small memory.
From: copernicus@digund.uucp (Copernicus) 
Newsgroups: comp.unix.bsd
Subject: Allways IN-2000 SCSI Cont
Date: 22 Aug 92 10:51:00 GMT
Distribution: world
Organization: Digital Underground - PRIVATE
Reply-To: copernicus@digund.uucp (Copernicus) 

Can someone please tell me whether or not 386BSD supports the ALLWAYS
IN-2000 controller?  Before I download everything Id like to know if
its gonna work!

Chris Nalley
---
 . SLMR 2.1 . For A Hobby -- This SURE Is Getting EXPENSIVE!
                      
Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Organization: Taronga Park BBS
Date: Mon, 17 Aug 1992 10:54:59 GMT

In article <PHR.92Aug16224207@soda.berkeley.edu> phr@soda.berkeley.edu (Paul Rubin) writes:
>    OK, I missed one aspect of this in my previous article. There is a large
>    category of people who now benefit from GCC who would not be able to
>    benefit from a GPL-covered 386BSD. Next, Sun (In Solaris 2), and I believe
>    MIPS ship GCC with their products, in some cases as the primary compilers.
>    This sort of distribution is not practical for an operating system.

>Why is it practical for compilers and not OS's?

Because the compiler distribution is subsidised by the OS distribution. If
the OS itself has no protection against unsupported copying, what is there
to subsidise it?

>In the old days, OS's came with source code, and users and system
>maintainers benefited greatly from this.

In the old days, OSes were subsidised by hardware sales and rental. In fact,
OSes were only provided to support hardware sales. That's not true any more:
even for proprietary systems, operating systems are products in their own
right. And for clonable machines (Sparc, MIPS, x86) the O/S has to be a
profit center in its own right.

Also, as BSDI has demonstrated, "coming with source code" and "free" are in
no way synonymous.
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.unix.bsd
Subject: Re: 4.4 BSD beta? Available? Postponed?
Date: 13 Aug 92 04:14:38 GMT
Distribution: na
Organization: St. Peter's College, US

In article <183033@pyramid.pyramid.com>, mfrost@sword.eng.pyramid.com (Mark Frost) writes:
> I had expected to hear something by now.  Has anyone else heard anything about
> this tape?  Has the AT&T lawsuit affected the release?  Is this just another
> slipped release date?  Am I dreaming?

  I received the forms last week. There is a brief overview of the 4.4 release,
the checklist, site info form, and 2 copies of the license agreement. This is
for the early release. You can order just this for $2000, or you can prepay an
additional $400 to receive the final version when it comes out.

  They only have the encumbered version now - the letter said an announcement
of the "lite" version would follow later.

  I called up to inquire if the USL complaint would affect this, and was told
that for AT&T/USL-licensed sites there would be no delays. I didn't inquire
about the "lite" version as we have an AT&T license.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
Newsgroups: comp.unix.bsd,comp.bugs.4bsd
From: randy@chinet.chi.il.us (Randy Suess)
Newsgroups: comp.unix.bsd
Subject: lockd on 386BSD
Date: 23 Aug 92 14:24:07 GMT
Organization: Chinet - Public Access UNIX


	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?

	(BTW, the ">>" problem is that it overwrites the file, instead of
	appending to it.  Plays havoc with rkive when using the BSD system
	for archiving)

-- 
	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
From: morphy@cco.caltech.edu (Jones Maxime Murphy)
Newsgroups: comp.unix.bsd
Subject: EISA machines & notebook question
Date: 18 Aug 92 20:47:59 GMT
Organization: California Institute of Technology, Pasadena

I have a Gateway 486/50 with an UltraStor Ultra 32 Bit SCSI host adaptor. 386bsd
does not recognize my hard drive(a 1.5 Gig Imprimis). What's going on, anybody?

2nd question:Then I tried booting on my PC Brand 486SLC notebook, which has
a Cyrix clone chip. It starts up fine, but then after loading the files onto
the hard disk, I can't boot from the hd. It says no bootable partition, altough
I can see the bootable partition with other software.
Jones
-- 
Jones M Murphy Jr                                        (212) 602-4375
NatWest Investment Bancorp, National Westminster Bank PLC
100 Wall Street, New York, NY10005                   FAX (212) 269-0113
From: elh@netcom.com (Ed Hudson)
Newsgroups: comp.unix.bsd
Subject: Re: apparent csh bug, 386bsd (WITH FIX)
Keywords: free(), core.csh
Date: 17 Aug 92 17:28:39 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)


hi.

	/* many, many thanks to the jolitz's, gnu, cgd...
	 * this stuff is really sex on wheels!
	 */

	i ran into the same csh bug that bri@pegasus.mit.edu and
	tgt@neon.ecn.purdue.edu have reported (but for me, it was
	with 5 character directory names).  what follows is a work-around,
	not a real fix - but solves all of the problems that i've had.
	i haven't posted this to the net before, because i wanted to post
	a real fix for the real problem.

	i believe that the 'csh' bug is a memory allocation problem
	of some kind.

	my 'fix' is to just allocated 4 additional bytes on each call to
	malloc.  having done this, i have seen no other problems with
	the csh.

*** /usr/src/bin/csh/alloc.c	Mon Aug 10 21:14:15 1992
--- /usr/src/bin/csh/Orig/alloc.c	Mon Aug 10 21:08:09 1992
***************
*** 156,163 ****
      register int bucket = 0;
      register unsigned shiftr;
  
- nbytes= nbytes + 4;
- 
      /*
       * Convert amount of memory requested into closest block size stored in
       * hash buckets which satisfies request.  Account for space used per block
--- 156,161 ----


	in any event, here's my data on the bug problem:


	i've encountered a problem that i believe is a memory allocation bug
	in csh.

	i have a prompt setting alias in my .cshrc for "cd", that looks like:

		alias cd 'cd \,* > /dev/null; set noglob; set xdirs = `dirs`; set prompt = "$user@$hostname $xdirs[1]:q \, % "; unset noglob xdirs'

	the bug manifests itself when i type:

		cd
		cd bin01

	the csh says "Segmentation fault", and on a repeated attempt, dies.

	it seems to occur whenever the target directory is 5 characters in name length.
	i think that it is blowing up when the statement "set xdirs = `dirs`" is executed.
	if i modify /usr/src/bin/csh/alloc.c so that the number of bytes requested is automatically
	increased by 4 (on entry to malloc), then the problem goes away.

	i'm not sufficiently expert with gdb or the structure of csh to debug this
	properly.

	my hardware is:	DTK 486-25, AD1542b, WD8013, 16meg, maxtor 8380.
From: duplain@rtf.bt.co.uk (Andy Duplain)
Newsgroups: comp.unix.bsd
Subject: Re: re_comp/exec() ?
Date: 20 Aug 92 08:22:55 GMT
Organization: BT Customer Systems, Brighton, UK

In article <1992Aug19.170703.6627@news.uit.no> thostr@stud.cs.uit.no (Thomas Strandenaes) writes:
>I can't find the re_comp/re_exec system-calls. I need these to
>compile some of the source in /usr/othersrc. Can anyone give
>a helping hand here?

	Try regcomp(), regexec() and regsub() courtesy Harry Spencer of
	the University of Toronto.
	

-- 
Andy Duplain, BT Customer Systems, Brighton, UK.            duplain@rtf.bt.co.uk
#define	DISCLAIMER      My views and opinions are my own, and not my company's
Newsgroups: comp.unix.bsd
From: peter@taronga.com (Peter da Silva)
Subject: Re: Poisoned textbooks and net articles?
Organization: Taronga Park BBS
Date: Thu, 13 Aug 1992 02:12:12 GMT

In article <7172@skye.ed.ac.uk> jeff@aiai.ed.ac.uk (Jeff Dalton) writes:
>(2) Suppose I find out about an algorithm by reading a textbook.
>How much does my implementation have to differ from the one in
>the book?  Should I stay away from textbooks that give code and
>look for ones that give only informal or mathematical descriptions?

Well, at least one program was removed from the net after someone at
AT&T claimed the author had stolen the troff hyphenation code. The
author claims he implemented it from scratch based on a technical paper
he read.

So even if you're in the right it doesn't mean they won't sue you.
-- 
                                                                `-_-'
                         Have you hugged your wolf today?        'U`

Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032
Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: Why the big copyright statements?
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Wed, 19 Aug 1992 14:16:18 GMT

In article <1992Aug18.202317.28426@cci632.cci.com>,
 tvf@cci632.cci.com (Tom Frauenhofer) writes:
| Technically, the symbol <c inside circle> is not a legal replacement for the
| word ``Copyright''  (Yes, I check with a lawyer friend on this one a couple
| of years ago).

Im afraid you got that reversed.  The symbol <c inside circle> is, by treaty,
recognized internationally, including the US (for those countries that
are signatories).  The word ``Copyright'' or the abbreviation ``Copr.''
is *not* recognized internationally.

-- 
---
 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: dj@ctron.com (DJ Delorie)
Newsgroups: comp.unix.bsd
Subject: Polling for ctrl-C
Date: 18 Aug 92 13:16:10 GMT

>But the fact is I do not need asynchronous interrupts: for various
>reasons, the program I'm porting cannot be interrupted at any time, so
>the signal handler just sets a global flag, and the main program
>periodically polls this flag.

You could just shut off ctrl-c handling completely, and look for the
^C character when you scan the keyboard (kbhit() and getch()).  1.08
will have setcbrk(), but 1.07 has int 0x21 AH=0x33 already.

DJ
From: merlin@neuro.usc.edu (merlin)
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Date: 14 Aug 1992 18:44:16 -0700
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: neuro.usc.edu

In article <...> jrbd@craycos.com (James Davies) writes:

>Excuse my ignorance, but doesn't 386BSD use gcc?  Sounds like it's already
>contaminated beyond all hope of redemption...

You are of course not ignorant -- nor is anyone else I have met on the net --
gcc is an isolatable special case component clearly identified as a special
case in the distribution -- it is not a simple driver -- nor is it a major
patch -- moreover no fee is required of anyone redistributing gcc -- nor does
the gnu organization require specific permission for redistribution.  There
exist portions of the gnu license to which I object -- but since I am at all
concerned about doing my own compiler development the restrictions have very
little impact on me.  This is very different from vague intellectual property
claims (where no one knows the terms for free redistribution) or the specific
restriction (every penny of any payments to jolitz [without even a reduction 
to cover media, machine time, or personnel time expended in the duplication]).

Moreover, gcc could be stripped out without affecting many end user sites --
they just have to acquire compatible adaptors and put them at good addresses.
Including gcc in the present distribution doesn't make much difference -- but
a whole slew of cgd type copyrights and restrictions would be unmanagable.

For the record, I received a note from Bill Jolitz indicating (1) cgd should
not be singled out for criticism [I agree -- his was only a convenient case]
and (2) my point was right on the mark -- this is why Jolitz continued the
minimal requirements of the UC Regents distribution.  The net may not be at
all ready for this concept -- 'freely redistributable software' -- but there
are forward looking people like Jolitz who perceive the folly of inhibitory
and/or confusing ad hoc collections of miscellanous copyright claims.

Merlin

The Magician
King Arthur's Court
Camelot


Newsgroups: comp.unix.bsd,comp.protocols.nfs
From: eichin@athena.mit.edu (Mark W. Eichin)
Subject: Re: 386BSD: 16550's vs. NFS
Organization: Massachusetts Institute of Technology
	<oc27njc@rhyolite.wpd.sgi.com>
	<schneck.713651159@Physik.TU-Muenchen.DE>
Date: Wed, 12 Aug 1992 23:34:15 GMT

I've gotten a number of useful comments from people on the net; thanks
for reading my note. I'm currently looking at FAS (Final Async
Solution) to see if I can port that to BSD rather than continuing to
hack the mainline driver (after all, FAS is designed to support
multi-port boards.) The interrupts are still not showing up, I'm about
ready to take a logic probe to the board and test it... I've even set
breakpoints in Vcom3 and they don't fire, so I'm pretty sure they're
not getting to the CPU.
	Several people have suggested reducing the block sizes; from
bad experiences with UDP fragmenting on Ethernets, I already knocked
the block size down to 1024 (both rsize and wsize.) I tried it at 128
once but got XDR errors from SunOS on the server.
	Another suggestion:
>>And radically bloat the attribute cache expirations.
	386BSD mount doesn't have an option to control that (the only
place I've ever seen fine control of the attribute cache is in SunOS.)
A quick glance at the source shows NFS_ATTRTIMEO at 5 seconds in
nfs/nfs.h, I'll try compiling that higher (but I doubt that it is much
of a problem at 38,400bps.)
>> ... and use ppp or nfs over TCP or turn on UDP checksums ... you might 
>> loose big with NFS otherwise, even with MNP4/V.42!
	Actually, I'm using a direct wire and *still* losing. I don't
know if I mentioned this before but NFS over TCP (to another 386BSD
machine) works fine, it is the UDP version that fails.
	I haven't heard from *anyone* who is actually *using* 386BSD
NFS over SLIP, so I may be the only having this problem just now :-)
				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
				Cygnus Support <eichin@cygnus.com>
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: 386bsd mount points
Date: 21 Aug 1992 09:47:44 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

Experiment (repeat-by) : Create a directory mode 000 owner root. Mount
filesystem on top of that. Give mounted directory permissions 755. Log in
as ordinary user. Go into that directory. Type 'pwd' or 'ls -la'.
Watch the programs complain about '..'.
Tell me why this happens.

Thanks,
	Bernard

-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd
From: jpk@Ingres.COM (Jon Krueger)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Reply-To: jpk@Ingres.COM (Jon Krueger)
Organization: Ask Computer Systems Inc., Ingres Division, Alameda CA 94501
Date: 19 Aug 92 02:22:46 GMT

Peter da Silva writes:
> as BSDI has demonstrated, "coming with source code" and "free" are in
> no way synonymous.

This was well understood thirty years before BSDI.

But it took USL to show  how "coming with source code" and
"free" could be antonymous.

-- Jon
--
Jon Krueger  jpk@ingres.com  
Newsgroups: comp.unix.bsd
From: michaelv@iastate.edu (Michael L. VanLoon)
Subject: Re: Major Problems with 386bsd0.1 please read
Organization: Iowa State University, Ames IA
Date: Thu, 13 Aug 1992 21:23:43 GMT

In <1992Aug10.090201.601@cl.cam.ac.uk> qs101@cl.cam.ac.uk (Quentin Stafford-Fraser) writes:
>In article <9208100044.AA09303@cs.utexas.edu>, STDN%MARIST@VM.MARIST.EDU
>(Dan Newcombe) writes:

>|> 4) cc:  I compiled the following C program using cc -o test test.c

>I have done this more than once, and I kick myself every time :-)
>Test is a builtin command in almost every shell. It has different return
>codes, but no output.
>You can run your program using ./test, or some such.

You can always find out which command is getting executed by typing:
	which <command>

Trying 'which test' on this Ultrix system under tcsh tells me:
	/bin/test

-- 
------------------------------------------------------------------------------
  Michael L. VanLoon                           Project Vincent Systems Staff
  michaelv@iastate.edu              Iowa State University Computation Center
------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: bri@pegasus.mit.edu (Brian D. Carlstrom)
Subject: Re: Motif on X386???
Organization: mit
Date: Mon, 17 Aug 1992 22:39:09 GMT

In article <1992Aug17.140857.3882@lgc.com> danson@lgc.com (Doug Anson) writes:
>|> In article <16kt8jINN9so@agate.berkeley.edu> randyc@ocf.berkeley.edu (Randy Yen-Pang Chou) writes:
>|> >Anybody got motif working on X386 with 386bsd?  How's the performance?
>|> >How much memory do I need to compile it(not including the docs) ?
>|> 
>|> You have to have at least the 1.2 Motif sources, and, if you mean "how much
>|> disk" instead of "how much memory", the answer depends on whether you want
>|> .... stuff deleted ....
>Motif 1.2 Really? --- 1.1 is running on my 386BSD quite nicely.  I had no
>problems compiling it based on X386 1.2E 1.0.2.  Furthermore I compiled it in
>about 30 Meg space (including install).

What is the deal with site licenses and motif. i know mit has a bin/lib/src 
license to cover everyone on campus. does this mean you can give it to me?
it would save a lot of gried. i reall dont have the space for src.

what's the legal bit on this...

-bri
Newsgroups: comp.unix.bsd