HDTenEightyP/NetNews huggingface dataset:
From: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats
Date: Tue, 18 Aug 1992 22:53:26 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)

In article <1992Aug17.225116.20533@panix.com> tls@panix.com (Thor Lancelot Simon) writes:
>In article <9208162341.30@rmkhome.UUCP> rmk@rmkhome.UUCP (Rick Kelly) writes:
>>In article <YSDIBS4@taronga.com> peter@taronga.com (Peter da Silva) writes:
>>>In article <PHR.92Aug15214245@soda.berkeley.edu> phr@soda.berkeley.edu (Paul Rubin) writes:
>>>>    If 386BSD was copylefted, it would be Linux. It's the absence of copyleft
>>>>    that leads to the possibility of more than a bunch of random hackers
>>>>    benefiting from it.
>>>
>>>>Please clarify this.  How is anyone else prevented from benefitting
>>>>from it?   Say, for example, the same people who now benefit from GCC?
>>>
>>>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.
>>
>>
>>And from reading comp.unix.solaris, I get the idea that a number of development
>>shops will buy compilers for Solaris 2.0 because of the GNU Copyleft.
>
>I'm sorry, that's just stupid.  Is this another reincarnation of the anti-FSF
>propaganda line about "if you compile your code with GCC, it's covered by
>copyleft!!!!"?  That suggestion is patently false.  The degree to which a number
>of commercial software houses are frightened of the FSF is neatly displayed by
>the persistence of this absurd rumor.


When an organization introduces a new and novel way of controlling the uses
of a product into a society that is infatuated with litigation, it should
expect fear.

Software houses such as Lotus and Wordperfect want complete assurance that
their product is secure under the law when it goes out the door.  There is
no court record to show what happens when the buyer of a commercial software
product demands source from the author because it was compiled using GCC,
and should fall under the GNU Copyleft.  

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
Xref: sparky comp.unix.bsd:4534 comp.bugs.4bsd:208
From: davidg@agora.rain.com (David Greenman)
Newsgroups: comp.unix.bsd,comp.bugs.4bsd
Subject: Re: 386BSD kernel bugs w/fixes
Date: 21 Aug 92 04:18:21 GMT
Article-I.D.: agora.1992Aug21.041821.13236
Organization: Open Communications Forum

ws@tools.de (Wolfgang Solfrank) writes:
> While I didn't check the other fixes, at least point 4 is incorrect.

Oops, you're right.  Thank you for pointing this out.  I mis-read the manual
page for get/setrlimit and thought that the discussion about hard/soft limits
only applied to RSS. This doesn't change the fact that 6MB is not enough VM
for a large number of applications.  In light of this, I would recommend
changing the DFLDSIZ and DFLSSIZ parameters in /sys/i386/include/vmparam.h
 - even 8MB is *much* better than 6.

---
David Greenman
davidg%implode@percy.rain.com
Organization: Penn State University
Date: Mon, 17 Aug 1992 08:50:04 EDT
From: <NXS10@psuvm.psu.edu>
Newsgroups: comp.unix.bsd
Subject: resize swap space?

I installed 386bsd on my pc.Now I want to run xwindows on that.How to change sw
ap space now when I have the complete system loaded?I have tiny boot flopy,fixi
t floppy &bin01.**.
thanks.Neena
Newsgroups: comp.unix.bsd
From: bri@pegasus.mit.edu (Brian D. Carlstrom)
Subject: Re: 680x0 version of 386BSD?? [Was: Re: Mac version of 386BSD??]
Organization: mit
Date: Wed, 19 Aug 1992 15:53:59 GMT

In article <1992Aug19.093937.14857@olymp.informatik.uni-bonn.de> volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt ) writes:
>In article <1992Aug18.174205.23671@news.iastate.edu> niko@iastate.edu (Nikolaus E Schuessler) writes:
>>Since most of the source is written in C, I believe that most of the time
>>is going to be spent writing drivers for disks, displays, etc...

i just had an interesting thought. wouldn't ib be a bit easier to port 
to the 68k apollos, since they use an ISA bus, which is supported by
386bsd? i realize that the video cards they use are not standard, but
you could at least get it up and going by using a pc card and monitor.

also i know others are trying to get info on making the apollo cards
and monitors usable in pc isa buses, so some others could get specs on
that.

btw, apollo does use a normal 3com ethernet card. is there support for
3com cards in 386bsd? if there was, that would be done too...

hmm...

-bri


Newsgroups: comp.unix.bsd
From: tls@panix.com (Thor Lancelot Simon)
Subject: Re: Restrictions on free UNIX / 386BSD (Re: selling 386BSD)
Date: Tue, 18 Aug 1992 06:56:41 GMT
Organization: PANIX Public Access Unix & Internet, NYC

In article <9208171721.29@rmkhome.UUCP> rmk@rmkhome.UUCP (Rick Kelly) writes:
>In article <PHR.92Aug17112028@soda.berkeley.edu> phr@soda.berkeley.edu (Paul Rubin) writes:
>>    >... 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.
>>
>>    And from reading comp.unix.solaris, I get the idea that a number
>>    of development shops will buy compilers for Solaris 2.0 because of
>>    the GNU Copyleft.
>>
>>The copyleft does not prevent development shops from using GCC.
>>If they think it does, they haven't been paying attention, or they are
>>letting their decisions be controlled by paranoid knee-jerk reactions
>>instead of by intelligence.  I'm sure this makes Sun happy; there's
>>one born every minute, as the saying goes.  I don't see this as a
>>reason to let Sun and others make proprietary GCC's.  I can't see
>>any benefit of a non-copyleft GCC that could outweigh sacrificing
>>the hundreds of improvements, ports, etc. that people have been
>>allowed to contribute because the marketroids they work for weren't 
>>permitted to grab the improvements for themselves.
>
>But some lawyers believe that the use of GCC to develop proprietary
>applications that are shipped "binary only" may be hazardous to a
>companies legal health.  The GPL has not been tested deeply in court.

And I suppose you don't know about the special license, *not* the ordinary GPL,
under which the GNU libraries and similar portions of GCC are distributed.  Nice
try.

-- 
Thor Lancelot Simon	 tls@panix.COM
  "Oh, you have wounded me!  I have very few prejudices, actually.  The
biggest problem is that I am intolerant of fools.  That is why I have
such a low tolerance level for Libertarians."  -- Jim McMaster
From: tgt@neon.ecn.purdue.edu (Conan the Librarian)
Newsgroups: comp.unix.bsd
Subject: apparent csh bug, 386bsd
Keywords: free(), core.csh
Date: 15 Aug 92 20:12:27 GMT
Organization: Purdue University Engineering Computer Network

I'm getting the following strange behavior when running csh as joe user
("tgt").  I have not seen any of this while running a Bourne shell:

Login as tgt, and simply start moving around within subdirectories with "cd".
Eventually I get an error message of the type

	free(20008) above top of memory.memtop = 2a000 membot = 23504
or
	free(24de8) bad block.memtop = 29800 membot = 23504

On rare occasions I get a csh core dump and the system logs me out (with or
without the above error message).

Now here is where it gets really strange.  Alias "cd" to incorporate the
current working directory ($cwd) into the prompt.  Then cd around again,
in a directory structure like follows:

LEVEL		0	1	2	...

	/usr
		/tgt
			/bin
				/dud
			/src
			/stu
				/stupid
			/stupid

Everytime I cd into a level 1 directory WITH 3 LETTERS IN THE NAME, (either
from a directory above or below it) I get either A) an error message from
free() of the two types above or B) two bogus characters, one a superscript-2
and the other a smiley face appended to the end of the directory printed out
in the prompt.  If this latter happens, then I am hosed.  vi fails with core
dumps, "rm", "mv", or "cd" cause csh itself to core dump, logging me off.
This is very reproducible, as crazy as it may sound!

An example (short) login session:

	/usr/tgt >  cd bin/dud
	/usr/tgt/bin/dud >  cd
	/usr/tgt >  cd stupid
	/usr/tgt/stupid >  cd ..
	/usr/tgt >  cd bin
	/usr/tgt/bin^2^0 >  cd ..			LOGOUT!!!

1) I have not (perhaps YET) noticed this when operating as root.

2) It is not a function of the particular file system (I've had this behavior
when /usr is a mounted SCSI file system and when part of the root IDE file
system).

3) Recompiling csh hasn't helped.

Any ideas???

-tom
--
Tom Tobin				UUCP:     pur-ee!tgt	
Dept. of ChE				INTERNET: tgt@ecn.purdue.edu
Purdue University			Ma Bell:  home (317) 463-0189
W. Lafayette, IN 47907				  office "   494-4052 
Newsgroups: comp.unix.bsd
From: jdb@bitcave.in-berlin.de (Joern D. Busch)
Subject: Re: wd1 bad144 woes & workaround (& another idea)
Organization: BitCave BBS, Berlin, FRG
Date: Thu, 13 Aug 1992 00:14:03 GMT

bs@Germany.EU.net (Bernard Steiner) writes:

>swapon: wd1b: device not configured and mount complained in a very similar
>fashion.

I'm not really sure about the necessity of this, but does your config
file include something like:
config	"386bsd"	root on wd0 swap on wd0 and wd1

About bad144 in general, a few days ago I asked here about it, at that
point missing the dd trick.  The very first mail I received mentioned
that trick, so after low-level formatting the drive, letting the con-
troller mark the bad sectors, installing an appropriate disklabel and
initialising bad144 wd0 0, I dd-searched all bad sectors and marked
them with bad144 -a, and in fact all the right hd/cyl combinations
(not 100% sure about the sects) got marked (as reported by bad144 wd0),
but -- it still wrote to these sectors.

By then I received a few more mails, mostly telling me that bad144 is
broken and I should use the controller's alternate sector option.  I'm
doing that now, and it works just fine.

But -- another person (sorry, forgot the name, but thanks!) phoned me
and told me he got bad144 working by _not_ letting the controller mark
the bad tracks.  This way the dd trick doesn't work, but you can just
mark all sectors of a known to be bad hd/cyl combination as bad.  You
loose quite some disk space, especially if you not have a MFM (17sec)
drive, but if you're controller doesn't do alternate sectors I guess
it's the only way to go.

So it might be interesting but enerving to try the following: low-level
format, controller-mark bad sectors, dd-find bad sectors, bad144-mark
them while writing them down, low-level format again, _not_ let the
controller mark the bad sectors, bad144 the previously noted sectors.

After a precious weekend of reinstalling I'm a bit tired of this, so if
anybody tries this please let me and/or this newsgroup know.

cheers,
	Joern.
-- 
     Joern D. Busch, Postfach 210401, 1000 Berlin 21, FRG, (+49 30) 3931111
jdb@bitcave.in-berlin.de ..!mcsun!unido!fub!einoed!bitcave!jdb ..which reality? 
Newsgroups: comp.unix.bsd
From: bill@unixland.natick.ma.us (Bill Heiser)
Subject: Re: com woes
Organization: Unixland Public Access Unix  (508) 655-3848
Date: Fri, 14 Aug 1992 22:34:33 GMT

spedpr@thor.cf.ac.uk (Paul Richards) writes:
>This change seems to be causing more confusion than anything else. Those
>die hard unix people feel uncomfortable with it and those with less
>experience are getting confused by conflicting messages relating to
>different com numbers. I think we should change back to zero based com

There shouldn't be any confusion.  FORGET about DOS!  This isn't DOS!
People who use DOS (including myself) have to know what DOS calls com
ports, and people who use UNIX (including myself) have to know what they
are called in UNIX.  The fact that both operating systems happen to run
on the same hardware is irrelevant!

-- 
bill@unixland.natick.ma.us                      ESIX Mailing List Moderator
Public Access UNIX/USENET/E-MAIL!  UUCP Accounts Available!  (508) 655-3848
5 lines  -  Located in Natick, MA   USA    Supporting V.32/PEP/V.42bis, etc.
From: ken@sugra.uucp (Kenneth Ng)
Newsgroups: comp.unix.bsd
Subject: Re: USL's Pieper profiled in UNIXWorld (selections)
Date: 14 Aug 92 00:00:20 GMT
Organization: Private Computer, Totowa NJ

In article <Aug09.201214.62367@yuma.ACNS.ColoState.EDU:, barnesdo@CS.ColoState.EDU (douglas barnes) writes:
: As someone unfortunate enough to have to use actual vanilla AT&T Unix
: for the 386, as well as their abominable hardware, I can testify that
: they not only dish out some of the worst products in the universe from
: a technical basis, but also from the perspective of "documentation,
: and service, and support, and training..." 

AT&T UNIX for the 386 does not seem that bad at all, but then I am used to
the sludge that is AT&T UNIX Rel 2 on an AT&T 3B15.  We had a problem
reading a cpio file from a tape.  We called AT&T.  They said they knew of
the bug.  Great, is there a patch available?  No.  Will it be in the next
release of the OS?  No.  Is there a workaround?  No.  Do you plan to fix
this problem?  No, we don't consider it to be a problem if you can only
read tapes written by other 3B15s.

SunOS isn't much better unfortunately.  I had a problem (again) with cpio.
Yes we know of the problem.  Great when will a patch be available?  You
don't understand, we prioritize our bug fixes.  ?  Ok, which release of
the OS will this problem be fixed in?  You do not understand, we prioritize
our bug fixes.  (Now I'm suspicious)  How long has this bug been known?
I can't tell you that, its propriety information.  At what point does this
bug occur, I can program around it.  I can't tell you that, its propriety
information.  Well, after talking to several other people, I finally find
out that this bug has been known for several years, and no bug patch is
ever planned.  

-- 
Kenneth Ng
Please reply to kdn5669@hertz.njit.edu for now.
Apple and AT&T lawsuits: Just say NO!
Newsgroups: comp.unix.bsd
From: lucchina@hsi.com (Paul Lucchina)
Subject: Stray interrupts
Organization: 3M Health Information Systems, Wallingford CT
Distribution: usa
Date: Fri, 21 Aug 1992 21:48:36 GMT

A few new  tape devices were added to our 8650 running 4.3 BSD. On occasion
the system logs some stray interrupt messages.  Is there a way to 
identify what is causing these interrupts short of removing the boards. 

The following is the message that is logged:

vmunix: nexus stray intr ipl15

Thanks
pjl

/*******************************************************************/
/* Paul J. Lucchina                     E-MAIL - lucchina@hsi.com  */
/* 3M Health Information Systems        VOICE - (203) 949-0303     */
/* Wallingford, CT  06492               FAX - (203)949-6331        */
/*******************************************************************/
-- 
/*******************************************************************/
/* Paul J. Lucchina                     E-MAIL - lucchina@hsi.com  */
/* 3M Health Information Systems        VOICE - (203) 949-0303     */
/* Wallingford, CT  06492               FAX - (203)949-6331        */
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: Re: re_comp/exec() ?
Date: 20 Aug 92 07:32:52 GMT
Organization: HCS GmbH, Hamburg, Europe

In <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?

have a look in comp.sources.unix, volume7, Archive-name: regex, just
needed them for index ...

hellmuth
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
From: armhold@action.rutgers.edu (George Armhold)
Newsgroups: comp.unix.bsd
Subject: Re: Endless boot cycle- suggestions?
Date: 18 Aug 92 21:41:43 GMT
Organization: DIMACS @ Rutgers University

yas@hpycla.kobe.hp.com (Yasuyuki Suzuki) writes:

>Then, I tried to install to IDE disk (Conner CP30104H) and the 386BSD
>was successfully booted from the hard drive.

>So, I think our problems are related to disk controlers or hard disks.

Actually I have the Adaptec ACB-2322B card controlling an ESDI drive.
The ESDI was pulled from a Sun "shoebox" disk/tape drive.
Unfortunatly I have no alternate drive controller to test it out on.
:-(

To anyone else who is keeping score- I also tried the patched kernels
in the unofficial/newbootables directory to no avail.  I'm still
awaiting suggestions...

-George
-- 
		 Internet: armhold@dimacs.rutgers.edu
	       UUCP: {backbone}!rutgers!dimacs!armhold
		    BITNET: armhold@PISCES.BITNET
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: Motif on X386???
Date: Wed, 19 Aug 92 00:25:25 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <1992Aug18.174802.9845@BitBlocks.com> bvs@BitBlocks.com (Bakul Shah) writes:
>terry@cs.weber.edu (A Wizard of Earth C) writes:
>
>>I also saw problems with menus not coming active unless you let go of the
>>button popping up the menu, then quickly pressed it again (not in the menu
>>area) to get the menu selection bar to follow the mouse.
>
>Make sure you are using the latest com.c driver (with select()
>bug fixed).  But even then there is some problem with the mouse
>code in X386 as the very first button press is not seen until
>after you either release the button or move the mouse a bit.
>
>If you wish to track this problem down, check out file
>$X11R5/mit/server/ddx/x386/x386Io.c.  Routine x386MseEvents()
>seems to be the culprit.
>
Rich (rich@rice.edu) already fix this problem in the next upcoming release of X386 1.2E 1.0.2 for 386bsd 0.1, please ask him for the fix. The problem in a nutshell is that X386Io.c is not setting the cflag. the fix was also previously posted by me.

Additionally, there are problems with the X server not grabbing the keyboard,
this problem has been also resolved.

So just ask Rich when he is going to release X again. Hopefully, it will be
soon. I just hate to see the same problems being reported over and over again
even though there has been previous postings relating to the problem with
suggested fixes.

>-- Bakul Shah <bvs@bitblocks.com>

Amancio Hasty




Newsgroups: comp.unix.bsd
From: niko@iastate.edu (Nikolaus E Schuessler)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Organization: Iowa State University, Ames, IA
Date: Fri, 14 Aug 1992 14:21:33 GMT

> [...]
>I really like 386BSD -- and I've put a lot of time into understanding it.
>I've read most of the kernel, filesystem, network, startup, and memory
>management source codes.  I reread the Leffler 'devil book' several times.
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What book is this? What is it about? how much?

>I'm eagerly awaiting the arrival of the announced Jolitz internals book --

Neat... when is this supposed to come out?



-- 
Niko Schuessler               
Project Vincent Systems Manager              email: niko@iastate.edu
Iowa State University Computation Center     voice: (515) 294-1672
Ames IA 50010                                snail: 272 Durham
From: dxper@dtek.chalmers.se (Per Anders Olausson)
Newsgroups: comp.unix.bsd
Subject: Re: Mac version of 386BSD??
Date: 18 Aug 92 22:39:58 GMT
Organization: Chalmers University of Technology, Gothenburg Sweden

scs@iti.org (Steve Simmons) writes:

  [since there are a lot of confusion and lack of 4.4BSD info I thought I add
   something to the confusion...]

>niko@iastate.edu (Nikolaus E Schuessler) writes:

>>Q:
>>   1) Where would I get 4.4BSD? (site, directory)

>I believe that only the alpha release is out and only to selected
>sites.

  Not true. As far as I know you can order it now, although I am not 100% sure
of exactly when you would find it in the mailbox, however it appears to be out.

  (or else I am one of those selected sites since I got an offer to buy it B-))

>>   3) Do I need some sorta license ?

>Depends on who you ask.  UCB says no, USL says yes.

  They are currently only shipping 4.4BSD-encumbered which means you have to 
have a AT&T source licence...

  Lite will follow later according to the paper ... 

>>   4) Is there enough interest?

>Not from me.  Now, if you were going to put it on a Sun . . .

  These are the supported boxes:

	HP9000/300 68000-based workstations
	Intel 386/486-based machines (ISA/AT or EISA(?!!) bus only)
	Sony News MIPS-based workstations
	Omron Luna 68000-based workstations
	DECstation 3100 and 5000 MIPS-based workstations
	Sparcstation I & II SPARC-based workstations                   (<------)

  As you can see there are at least two m680x0 machines supported...as well
as support for the SPARC...

  If you want more info, I would suggest contacting Pauline Schwartz at
pauline@cs.berkeley.edu or phone (510) 642-7780...

  [why haven't CSRG posted this info here? Beats me...]

  (reservations for any late night reading/typing errors...)

pao
--
-------------------------------Andrew Olausson--------------------------------
--------------------------Unemployed Unix Specialist--------------------------
------------------------------pao@cd.chalmers.se------------------------------
-------------------------------pa-ola@proxxi.se-------------------------------
Newsgroups: comp.unix.bsd