HDTenEightyP/NetNews huggingface dataset:
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: which X386 in agate is better?
Date: Fri, 11 Sep 92 17:30:31 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <EICHIN.92Sep11043000@tsx-11.mit.edu> eichin@athena.mit.edu (Mark W. Eichin) writes:
>> Is there any archive site which has 'stripped' X11 binaries ?
>> Downloading 12M bytes of X386 server only (even though it is compressed)
>> does not make sense to me since I'll never debug X386 server.
>	Since I run at the end of a SLIP line (38,400 wire, but still
>not ethernet) and I've mostly filled a 200M disk, I wanted a smaller
>release for a lot of reasons... there are two things I've done that
>you might find helpful (that I'd also like to see in any future X
>binary release):
>	1) strip all binaries. If I care, I'll build with symbols. If
>*you* care, write a version of "pirts" and keep the symbols yourself.
>[pirts is a reverse strip, I've seen a few people write them under BSD
>-- it takes the symbols and puts them in a different file. Then, when
>debugging something, you should be able to tell gdb "symbol-file
>foo.syms" and have it look there instead of in the exec-file...]
>	2) compress all the fonts. The X11R5 has inline code to
>uncompress them on the fly... all you have to do with the current
>release is remember to delete fonts.dir and run mkfontdir again in
>each of the font directories (75dpi, 100dpi, misc.) I haven't noticed
>any performance difference.
>	My current installation only uses 40M (compressing the fonts
>saves 6M by itself; stripping X386 saves over 10M...) and has *all* of
>the user-level functionality of the original release...
>				_Mark_ <eichin@athena.mit.edu>
>				MIT Student Information Processing Board
>				Cygnus Support <eichin@cygnus.com>
>ps. Above numbers using the agate:ports... version of Xfree86, not the
>one in pub/incoming.

The version in agate:/pub/incoming was built without "-g",
for instance, the size of the server is about 900,000 bytes and 
that is uncompressed!

Hope this helps,
Amancio Hasty





Xref: sparky comp.unix.bsd:5749 comp.os.mach:1289 misc.int-property:987 alt.suit.att-bsdi:306 alt.folklore.urban:23509
From: dpassage@eden.CS.Berkeley.EDU (David Paschich)
Newsgroups: comp.unix.bsd,comp.os.mach,misc.int-property,alt.suit.att-bsdi,alt.folklore.urban
Subject: Re: AT&T "DeathStar" Trademark (was: Are you sure UNIX is a trade mark?)
Followup-To: alt.folklore.urban
Date: 15 Sep 92 12:24:19
Organization: Organization?  Who cares?  You just gotta say "Go Bears!"
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: tjc50@juts.ccc.amdahl.com's message of 15 Sep 92 16:22:45 GMT

In article <4093@novavax.UUCP>, 
	burtond@novavax.UUCP (Donald B. Burton) writes:
   > actually, i have heard of this
   > purely as a rumor--the death-star <well thats what i call it> symbol
   > you know, the orb made with line-art so often seen with at&t logos
   > was once untm-ed and un <c>-ed.  then some joe-schmoo noticed and
   > copyrighted it before the execs at at&t realized.  at&t had to
   > pay him $$$ to buy it back/pay royalt etc. 

In article <05h702Px22VG01@JUTS.ccc.amdahl.com>, 
	tjc50@juts.ccc.amdahl.com (Terry Carroll) writes:

   I very much doubt this.

[explanation of copyright/trademark law deleted]

In fact, I heard this same story around 6 years ago about the old
pre-breakup Bell System logo of a bell in a circle.

Followups to alt.folklore.urban.

David Paschich
Newsgroups: comp.unix.bsd
From: meissner@triton.unm.edu (John Meissner)
Subject: X386 Installation Woes
Date: Mon, 14 Sep 92 00:27:58 GMT
Organization: University of New Mexico, Albuquerque

After obtaining the X386 release from agate.berkeley.edu (/pub/incoming/X386),
I find that I am unable to make it do anything after performing the steps
outlined for installation. I have made the appropriate links, installed the
kernel which was provided with the distribution, mknod /dev/vga, and
everything else I can think of.

When I start X, 'startx', the screen clears, I get some strange graphic stuff
on the screen in graphics mode, and then the server restores to text mode
with the error message 'XIO fatal IO error 32 (Broken Pipe)'. After running
xdm and examining the file 'xdm-errors', I see that X is detecting my video
board as an ET4000 with 16 clocks (the first few are correct), and then
it follows with an error message to the effect 'fatal server error, cannot
load default font 'fixed''.

Does anyone have any suggestions on what I can try to get this thing up and
running? Thank you for your time and effort.
Newsgroups: comp.unix.bsd
From: nerd@percival.rain.com (Michael Galassi)
Subject: Re: bsd386 slip xfer rate disappointing.
Organization: Percy's mach, Portland, OR
Date: Fri, 11 Sep 1992 21:14:18 GMT

solsman@ra.nrl.navy.mil (Mark Solsman) writes:


>Is everyone getting the same response?  slip from 386/25 running bsd to
>a 486/50 running slip8250 & tn3270 yeilds about .8k/second???

>funny, I am using slattach /dev/com2 38400, that should be damn faster than
>800 bytes/second...

You bet...

>also, as far as the silo overflows , I seem to only get them when I 
>have a packet collision.  dont type anything until after xfers, and turn
>off the damn hashing, and you dont get any overflows...  this maybe a side-
>effect.

Colisions indicated by netstat -i are not collisions, by definition you
can't have collisions on slip links.  The collision counter is incremented
(counter intuitevly) when the output routine (slstart I think) drops a
packet instead of putting it into the com port's ring buffer.  They say
this is to improve interactive responsivenes and that tcp will take care
of it but...  I've got a hacked if_sl.c which I'll mail to those who know
enough to look over the changes and decide if they are indeed good.  End
result of these changes here is that my machine routes between two 38.4K
slip, one 19.2K slip, and one ether with very few errors (this is a 386/25
w/ 2meg ram & 1 floppy).

-michael
-- 
Michael Galassi -- nerd@percival.rain.com
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: SCSI Tape and X11R5 questions
Date: Wed, 16 Sep 92 02:27:54 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <47606@shamash.cdc.com> pbd@runyon.cim.cdc.com (Paul Dokas) writes:
>I have two rather basic 8-) questions about 386BSD 0.1:
>
>  1) I want to build X11 preferably R5 for my 386.  I've increased
>     the swap to 24MB, applied as many patches as I could find and
>     now I'm stuck.  I know that I have to get XFree86 (probably from
>     agate), but do I also need the MIT X11R5 distribution?  My
	You need to get mit-1, mit-2 and maybe mit-3 if you are
	good at building X you may get by without mit-3.
	Also, you will need patch levels 1 to 16.
	Finally, the instructions and patches on how to build
	X11R5 are in the README in agate.berkeley.edu:/pub/incoming/X386

	There is also under the same directory in agate a patch
	kit for the kernel. 
	
>     question is basically:  what source do I need to ftp to build
>     X11R5 on my 386-40 (TVGA 512K, God I hope that there's a driver
>     for this card!)
	could you please look in the card and send me the svga 
	chip name/model. A good chipset that works with Xfree86 is et4000
	you can get clones for about $125 now days. Also, the
	next upcoming release of Xfree86 has support for Trident
	which are dirt cheap around $85.

>
>Thanks for the help!
>
>Paul Dokas
>pbd@runyon.cim.cdc.com
>
>BTW many thanks to Terry Lambert for the patchkit!  I applied all 19
>    patches to my system and rebuilt it in less than 30 minutes.
>    When are the rest of the ~30 patches coming out?
>-- 


Amancio Hasty
From: karn@servo.qualcomm.com (Phil Karn)
Newsgroups: comp.unix.bsd
Subject: Re: Fixed: Runs at 8MHz, Crashes at 33MHz, 386bsd
Date: 13 Sep 92 21:11:26 GMT
Organization: Qualcomm, Inc., San Diego, CA


I think I've found and fixed the problem I was having at high
CPU clock speeds. I found and applied Frank Maclachlan's DMA fixes
posted about a month ago on this group, and the system hasn't crashed
since. I've exercised it by rebuilding the kernel a half dozen times;
before the fix it usually crashed several times before finishing it
even once.

Phil
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: 386BSD PATCHKIT UPDATE (Alpha 2)
Date: 15 Sep 92 03:35:26 GMT
Organization: Weber State University  (Ogden, UT)


	I have fixed all reported problems (so far) in the patchkit.  The
new version is alpha2 (0.1.1 for patches, 0.1 for mkpatch)

	For those of you currently using the patchkit, you need the new
version.  Explataion follows:

------------------------------------------------------------------------------
README.1ST
Terry Lambert
terry@icarus.weber.edu


	This is the updated patch kit for patch 00001-00019.  If you have
not downloaded the previous version, ignore this file and simply follow
the instructions in the file "patchkit-0.1.README".

	If you have downloaded the previous version of the patchkit, you
may have noticed problems with patches 00010, 00014 and 00016.  You may
also have notices that failure to install was not correctly caught (A
problem with the "patches" program itself).

	If you have used the previous patch kit, the following procedure
will allow you to update to the most recent version:

1.	cd /patch/bin
2.	run patches
3.	deinstall patches 00010, 00014 and 00016
4.	cd ../ready
5.	rm -rf patch00010 patch00014 patch00016
6.	cd /tmp
7.	get the new tar file "patchkit-0.1.tar"
8.	tar xvf patchkit-0.1.tar
9.	cd patch/inbound
10.	mv patch00010.tar.Z patch00014.tar.Z patch00016.tar.Z /patch/inbound
11.	cd ../bin
12.	mv patches /patch/bin
13.	cd ../..
14.	rm -rf patch
15.	cd /patch/bin
16.	run patches
17.	install patches 00010, 00014 and 00016

You are now at the most recent alpha2-release.


EOF -- This file has not been truncated.
------------------------------------------------------------------------------

Any other problem, please report them to me.


					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.
-- 
-------------------------------------------------------------------------------
                                        "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: cyber@ecst.csuchico.edu (Erik Berls)
Subject: 386BSD hangs
Organization: California State University, Chico
Date: Fri, 11 Sep 1992 05:32:21 GMT

I posted earlier about 386BSD crashing after 9-10 'ls -al's.
I had listed my hardware and some symptoms and someone suggested
that I pull out unneeded hardware to see if i could find a conflict.
well, here is what I got:
Hardware:
Adaptec 1542B
Orchid Prodesigner II
386-33, 8megs, has a "Chips" IC on the motherboard, I think the manual
had something about "Star" on the top of the cover (brandname?)
AMI Bios, not sure of the date offhand... (if you think it might make
a difference let me know..)

the other configuration i tried was removing the Orchid card and using
just the monochrome card.

well, it looked like the car didnt matter...

boot info:
pc0<mono> at 0x60 inq 1 on isa
fd0 drive 0: 1.2M 1: 1.44M at 0x3f0 inq 6 drq 2 on isa
as0 at 0x330 inq 11 drq 5 on isa

with the orchid it had 'color' instead of 'mono'

other than that i changed around the bios scratch ram area...

with it grabbing 1k of memory:
it booted, i was able to do 'ls -al' about 9-10 times then:
1) the system would hang
2) it would say Bus Error as Message and Hang
3) would Hang and have a bogus entry in the ls:
?--------- 0 0        0  Jan 1 1970 c???FEST

with the other bios ram area:
after 9-10 times of 'ls -al':
1) would display Memory Fault each consecutive time of trying ls -al
2) hang with wierd entry (see above)
3) wouldnt let me do a pwd:
"cannot exec /bin/pwd" (paraphrased)
4) Bus Error and Hung

thanks,
-=erik.
From: eric@hpsanaeo.nsr.hp.com (Eric Stephenson)
Newsgroups: comp.unix.bsd
Subject: X386.modeDB for NEC 4FG w/ Diamond Speedstar Plus?
Date: 8 Sep 1992 20:01:01 GMT
Organization: Hewlett Packard, San Diego
Distribution: world
NNTP-Posting-Host: hpsanaeo.nsr.hp.com

I'm looking for X386.modeDB for NEC 4FG monitor. 
I'm using Diamond Speedstar Plus controller.
NEC specs for 4FG seem to be consistent with X386.modeDB for 4D and 5D,
 should I just use these settings?
I'll post a working X386.modeDB when mine works. 

anyone have a 386BSD system "on the net" for browsing? 

--eric stephenson
Newsgroups: comp.unix.bsd
From: lma@dayton.Stanford.EDU (Larry Augustin)
Subject: 4.3bsd vs NET2: upgrading a VAX?
Organization: DSO, Stanford University
Date: 11 Sep 92 04:55:06 GMT

Sorry to interrupt all the discussion of 386bsd. :-)

Could someone please to me explain the difference between the
following:

	4.3bsd
	4.3bsd-tahoe
	4.3bsd-reno
	NET2

My particular interest is in upgrading a (don't laugh) VAX 11/785
running 4.3bsd to something with some more modern features, in
particular NFS.

What's the path of least resistance?

Thanks,

Larry

Larry M. Augustin			ERL 414, M/C 4055
lma@dayton.stanford.edu			Computer Systems Lab
+1 415.723.9285 (voice)			Stanford University
+1 415.725.7398 (fax)			Stanford, CA 94305

Newsgroups: comp.unix.bsd
From: hand@spc9.jpl.nasa.gov (Kolin Hand)
Subject: X386 with ATI VGA Wonder?
Organization: Jet Propulsion Laboratory, Pasadena, CA
Date: Mon, 14 Sep 1992 19:36:05 GMT

Greeting (Part 2).

I have an ATI VGA Wonder card in my system, conected to an NEC Mult-Synch 3D.
Can X386 1.0.2a (I think that's the version at agate in /pub/incoming/X386)
work with this configuration or would I be wasting my time trying  to get this
to work without major hacking?

Thanks.

Kolin

+===========================================================================+
+  "Guilt Trip:  The nuclear weapon of relationships."  -- K. Hand          +
+---------------------------------------------------------------------------+
+  Kolin E. Hand                              hand@spc7.jpl.nasa.gov        +
Newsgroups: comp.unix.bsd
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: 386bsd -- The New Newsgroup
Organization: Kithrup Enterprises, Ltd.
Date: Wed, 09 Sep 1992 20:37:31 GMT
Keywords: newsgroup 386bsd news group

In article <1992Sep9.180831.3944@nntp.hut.fi> jkp@cs.HUT.FI (Jyrki Kuoppala) writes:
>>I would strongly suggest forming comp.unix.freebsd.  The name more
>>correctly indicates the purpose, and as appropriate variants emerge
>>it can develop subgroups rationally.
>comp.os.free.386bsd?

Horrible name.

In any event, I would suggest waiting about a month or so before any such
discussions; by that time, the judge in the USL v BSDI and State of
California suit should have returned, and made a decision on BSDI's motion
for dismissal.  At that point, whether or not a potentially short-lived
group should exist can be discussed more fully.

-- 
Sean Eric Fagan  | "You can't get lost in one room, no matter how
sef@kithrup.COM  |  little effort you make to learn your way around."
-----------------+    -- William E Davidsen (william@crd.GE.COM)
Any opinions expressed are my own, and generally unpopular with others.
From: jbone@splat.dell.com (Jeff Bone)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd -- The New Newsgroup
Keywords: newsgroup 386bsd news group
Date: 8 Sep 92 20:29:05 GMT
Organization: Dell Computer Co

john@socrates.umd.edu (John VanAntwerp) writes:
>>
>>	comp.os.386bsd.ann	(announcements, fixes, additions)


One nit...  why not comp.os.386bsd.announce?  No sense in needless
truncation...  remember creat() ?  ;)


jb





--
-- Jeff Bone ------------------------------------------------------------
      "Imagination is more important than knowledge."  - A. Einstein
------------------------------------------------------- jbone@dell.com --
                                                                       --
Newsgroups: comp.unix.bsd
From: dmuntz@quip.eecs.umich.edu (Daniel A Muntz)
Subject: Re: Problem with OPTi?
Keywords: OPTi
Organization: University of Michigan EECS Dept., Ann Arbor
Date: Mon, 7 Sep 1992 16:03:12 GMT

In article <terry.715846751@uivlsi.csl.uiuc.edu> terry@uivlsi.csl.uiuc.edu (Terry Lee) writes:
>	Has anyone been able to get 0.1 to run on any 486 machine based on
>an OPTi chipset?  If so, are you using the 486SXWB or 486WB motherboard?
>I think I am experiencing bug BOOT009 in Nate Williams's bug list version 0.2,
>where all of the boot floppies lock up the system after displaying the initial
>copyright message (before listing any devices found).  I have an OPTi 486SXWB
>motherboard (486DX-33, 06/06/91 AMI BIOS).  Please, I really need help with
>this!  Also, if no one has found a fix, new buyers should be warned away from
>this motherboard (or chipset)!  Thanks.

The OPTI chipset/AMI BIOS combination is working for others.  I'm running 0.1
(and ran 0.0) on an OPTI-495WB with AMI BIOS without problems (486DX50 ISA).
This combination is also known to work under Mach and Linux.  You might try 
changing some of the parameters in the AMI setup.  The default worked for me.

  -Dan

Newsgroups: comp.unix.bsd
From: karn@servo.qualcomm.com (Phil Karn)
Subject: Re: [386BSD]
Organization: Qualcomm, Inc
Date: Sun, 13 Sep 1992 06:19:16 GMT

In article <1992Aug29.163711.25695@NeoSoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes:
>Unless you want to do ham packet radio stuff, the Berkeley TCP/IP and SLIP
>implementations that come with 386BSD are superior to KA9Q, which was
>designed for non-multitasking DOS operation and, thus, incurs some serious
>penalties when running under Unix.

Ahem.

Although I agree that my stuff isn't designed to run efficiently under
UNIX, I beg to differ about the "quality" of the implementation. I've
long had all the same stuff in my TCP/IP and SLIP that Berkeley has:
VJ header compression, VJ srtt/mdev rto calculation, clamped
retransmission backoffs, slow start, fast recovery, Nagle tinygram
avoidance, etc. It's fast enough to never be the bottleneck on a FTP
(as opposed to the wire or the disk.)  And it has avoided many of the
problems that still nag the descendants of some previous Berkeley
TCPs, like closing all TCP connections to a given host whenever you
receive ANY ICMP message that references that host...

Phil
From: paul@frcs.Alt.ZA (Paul Nash)
Newsgroups: comp.unix.bsd
Subject: NN, Elm, Smail, RC ported to 386bsd (was: 386BSD: news stuff)
Date: 13 Sep 92 17:34:30 GMT
Article-I.D.: frcs.1992Sep13.173430.12374
Organization: Free Range Computer Systems CC

Thus spake umrose05@ccu.umanitoba.ca (Dave Rose):

> run? Also, what about nn6.14?

I built this (as an NNTP client) straight out the box, as far as I can
remember.  However, the machine that I did it on is at work, so I can't
check for hacks.  I also have elm2.4 and smail3.1 running under 386bsd.
These took a bit of hacking (terribly inelegant, but they work), mostly
to get the configuration scripts to run under BSD's "sh".  Oh, I also
have RC (the PD version of the plan-9-from-bell-labs shell) going -- 
this needed no changes at all.  If anyone wants binaries or patches,
let me know.  

I am prepared to mail off a few binaries, and/or post patches if there
is demand for them.  Alternatively, any FTP sites I should ship these
to?

	paul
 
 ---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---
 Paul Nash                                         paul@frcs.Alt.ZA
 Box 12475, Onderstepoort, 0110 South Africa         +27-12-5611879

      "You don't want to get locked into open systems" -- IBM
Newsgroups: comp.unix.bsd
From: colin@cs.curtin.edu.au (Colin Manning)
Subject: Re: IDE and bad sectors.
Organization: Curtin University of Technology
Date: Mon, 14 Sep 1992 01:04:34 GMT

eddy@aludra.usc.edu (George Edmond Eddy) writes:

>How does one deal with bad sectors on an IDE hardrive?  

>After I had done the disklabel and newfs on a conners 3204, the 
>disklabel showed a bad sector map (paraphrase) in the flags field
>and went into the endless reboot cycle.  i used disklabel -e to
>clear the flags field, and everything proceeded fine, (this,
>however is wrong!).  It was suggested that i run bad144, however
>i read the INSTALL.NOTES and know not to do this!  

>Now i suffer from magically corrupting cp, rm and mv commands.
>I will rebuild the commands mv 'em into bin, everything is fine
>for a while, then WHAM! they start core dumping, (in the call to
>rindex).  i'll do a diff on the versions in the build directory
>vs. those in /bin, and diff claims there are differences????

>So will some kind soul illuminate me as to how to handle bad sectors
>on an IDE drive?  or should that flag be showing up at all???

I had the same problem.  I got no resopnce, so I went about it *MY* way.  It
may not be the best, but it works.

I had three bad sectors.

1)  File the hard disk with files of 10Meg, marking the files that cover bad
sectors.

2)  Delete one of the files that has bad sectors.

3)  file the hard disk with files 1/10 the size of the previous file.

4)  repeat steps 2 and 3 until you have sufficently small files.

NOTE:  I did this from a directory called HARDERRORS, and named the files by
the sector number that was bad in it, and removed rw permissions
from all three files AND the directory.  I know this doesn't stop root 
accidently removing them, but who logs in as root all the time anyway?

I think I got each of my bad sector files down to 512 bytes.  It took some
time to do (4 hours I think), but saved frustration later.

If someone has a better idea PLEASE let me know.

>thank you!
Hope it helps.

>- rusty


>eddy@usc.edu
>rusty@kirra.ema.rockwell.com

Colin.


--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd