HDTenEightyP/NetNews huggingface dataset:
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Occasional system hangs
Organization: Weber State University  (Ogden, UT)
Date: Sat, 12 Dec 92 07:30:53 GMT

In article <jason.724071780@sorokin> jason@sorokin.anu.edu.au (Jason Andrade) writes:
>Well, im going to have fun when [more likely IF] i get X happening. Not.
>Oh, system uptime record so far is way behind your 12 hours and its a nominally
>'quiet' machine....
>
>>Time for more RAM I guess!
>
>Would be nice, but I'd prefer a patch to the kernel myself. :-)

This is the correct soloution.  Basically, remove evrything in the kernel
you don't have installed in your machine.

RAM isn't a problem; I have run a sufficiently stripped kernel on a 640K
(no extended or expanded memory!) 386 Box with an NE2K card for periods
in excess of 4 days with moderate usage (20 Meg swap on a 30 Meg drive
and /usr remote mounted).  Moderate usage is 3 users curious about it and
beating on the compiler.  Obviously, no X  8-).

I think there are a number of questionable drivers; I also thing that the
stability is vastly improved after installing all patches (and the patches
to them and the mbuf/kern_* code posted here after the patchkit release).

The vast majority of the patches Nate is putting into the new patchkit are
stability patches and should improve things for heavy memory users.


					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: dosburn@cwis.unomaha.edu (Don Osburn)
Subject: Help, Unable to install on Tandon Hardware
Summary: Unable to install 386bsd on Tandon
Keywords: Hardware, Tandon, Architecture, install, boot
Organization: University of Nebraska at Omaha
Date: Thu, 17 Dec 1992 03:20:00 GMT

I have been attempting to boot my Tandon 386sx using the dist.fs image
and it will not work.  I did a binary download of the image from three
different places, and used rawrite.exe to write it to a 3.5" floppy
each time, but to no avail.  When I boot the system, it starts ok (I
guess), queries the A:\ drive, then just hangs leaving the A: drive
spinning infinitely.  I get a black screen with a flashing cursor, 
but nothing else.

I called the Tandon company long distance, and after waiting a LONG
time, I finally got to speak to a rather rude person that gave me the
following answers to my inquiries:

The Tandon 386 Option has a "standard 16 bit AT bus architecture," and
a "standard IBM compatible BIOS."  Here is the catch, when I asked about
the chipset on the board, I was told that it is a "Tandon  proprietary
chipset, made by Tandon."  I have 4 MB of memory installed, and a 105MB
IDE hardrive.

I would really like to work on porting the 386BSD to this machine, but
I am going to need some serious help.  I have relegated myself to
perusing the articles in DDJ to find some answers.  In one of the early
articles (sorry, I forgot the date), there is mention of some tools that
were created to "check out" a systems configuration, hardware, etc., to
determine any idiosyncracies that would need to be resolved with a
system in order to port the bsd to the machine.  Does anyone know 
anything about this?  Where can I get these tools, and how do I use
them?  The Tandon company does not seem to be very willing to give me
much information about the internal hardware of this machine!

I guess I should ask if anyone else has managed to port the bsd to
a Tandon machine.  Am I just being a total klutz, or is there something
different about this hardware?  I would be willing to spring for the
phone calls to Tandon if someone can tell me more specific questions 
that I should ask to resolve the problem.  I admit that I am rather
new to this, (I am a graduate student that has spent too much time
in the theory, and not enough in the applications), but I am willing 
to put in the effort if someone can point me in a direction. :-)

If anyone has any information that can help, PLEASE contact me soon.
Thanks in advance.  Take care.
Don

Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386bsd] drivers for DEC ethernet DEPCA,DE201,DE101
Organization: Weber State University  (Ogden, UT)
Distribution: comp.unix.bsd
Date: Sun, 20 Dec 92 02:14:02 GMT

In article <1992Dec19.170938.25446@nwnexus.WA.COM> levinson@halcyon.com (Don Levinson) writes:
>a while back I got the sources to  a DE200 driver from this newsgroup.
>I was wondering if the individual who wrote this driver (sorry I forgot
>your name) has updated this driver since then.

Contact:	Francis J. Hitchens
		hitchens@okfest.unt.dec.com

Accompanying information:
> please find included
> 
> -rw-r--r--    1 hitchens     1444 Sep 16 09:03 DEC325
> -rw-r--r--    1 hitchens    18863 Sep 16 09:02 if_se.c
> -rw-r--r--    1 hitchens     2458 Sep 16 09:02 if_sereg.h
> 
> in the following uuencoded compressed tar file.
> 
> You need to add the line
> 
> i386/isa/if_se.c        optional se device-driver
> 
> to the file /usr/src/sys.386bsd/i386/conf/files.i386
> 
> before you do your config.
> 
> The kernel prints out some garbage about the ethernet address, I will remove
> this later when I put the recommended initialisation code in for the
> ethernet address.
> 
> I may also use the NI_CSR to find out how much memory the card is configured
> to use, as well as using the network memory fully. At the moment only half is
> used in the 48k configuration.
> 
> Please let me know if you find any bugs, or if it doesn't work for your
> particular card.

Driver was beta as of last reference.


					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
-------------------------------------------------------------------------------
From: wjin@cs.uh.edu (W. Woody Jin)
Newsgroups: comp.unix.bsd
Subject: Re: Dumb Question: Why 512 byte block?
Date: 19 Dec 1992 20:04:32 GMT
Organization: University of Houston
NNTP-Posting-Host: rodin.cs.uh.edu

In article <1992Dec18.235623.27538@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>
>You can't split blocks between files.  

Yes, you can.
For example, you may have 4K size block with 512 byte fragment size.

>A block is, by definition, the
>smallest possible allocation unit.  Thin about the case where you have
>a 1 byte file and a 1 block - 1 byte file; what would you do when
>adding one or two characters to the first (1 Byte)?  TReallocate?  Shift
>and reallocate for the last byte of the second file?
>
>But... you're right that it doesn't work the way I've shown... thought
>for sure I'd get bombarded on this one:
>
>Consider the most ridiculous possible situation:  I have a 1G disk with
>a 1G blocking factor (impossible without rewriting the buffering code).
>
>How many files can I have on the disk? (Ignore the blocks allocated to inodes
>and directoryies 8-P).
>
>The answer is "1"... even if it only has 1 byte in it.

In this case, if you have 512 byte fragment size, you use only one
fragment which is 512 byte.  And you must have 1G of buffer memory.

BTW, could anyone clarify whether 386BSD uses the Fast Unix File System
which is described in "A Fast File System For Unix" by McKusick, Joy, Leffler,
and Fabry (1984 ACM Tran. on Computer System) ?

-- 
____   ____  ____ ____________________________________ (___) _________________
|  |   |  |  |  |  W. Woody Jin (wjin@cs.uh.edu)       (o o)      Moo.... 
|  |   |  |__|  |  PhD Student. Research Asst.  o=======\ /  I'm  a Cow Lover.
|  |   |        |  Dept. of Computer Science   / |     ||O   My wife  was born
\  |---|  |--|  |  University of Houston      `  ||'---||    in Cow year. Mooo
 \____/|__|  |__| _______________________________^^    ^^_____________________


Newsgroups: comp.unix.bsd
From: gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart)
Subject: Re: [386BSD] Disklabel help and large drives (1.7 gig)
Organization: Technische Universitaet Muenchen, Germany
Date: Fri, 18 Dec 1992 13:53:35 GMT

In article <1992Dec10.171917.20431@decuac.dec.com> darryl@sai.com writes:
>
>I know this is a FAQ which I have read, but I can't seem to partition
>my disk to anything but the default.  What am I doing wrong?   Do
>I need a disktab entrie to match my disk, before disklabel will work?
>Does the partition relate to fdisk format?
>
>
>Also does 386BSD have any problem supporting drives larger than 1 gig?
I'm currently using a 2 GB Disk in my 386BSD box and all of the 2 GB for
386BSD, so it works :). 
As far as I know ref.tfs.com has also a larger disk than 1 gig.

Ralf


Newsgroups: comp.unix.bsd
From: danson@lgc.com (Doug Anson)
Subject: Microsoft busmouse on 386BSD?
Organization: LandMark Graphics Corporation LGC
Date: Fri, 18 Dec 1992 16:25:24 GMT

HI:

I have downloaded from agate the mousedriver.tar.Z from /incoming. I installed
it in my 0.1 pl58+ kernel. I actually have a Microsoft Busmouse and not a 
logitech busmouse (which I believe the driver is made for). Well, the driver
doesnt work with the MS mouse. 

I would like to port this puppy for the Microsoft busmouse.  Does anyone 
know where I can get information for the busmouse card? (or for that matter
what differences I can expect between a Logitech busmouse and a Microsoft
busmouse)?

Any help would be apprecated. I will be glad to place the driver (when done)
in a good home (ftp site) if interested.

Doug
-- 
-------------------------------------------
Doug Anson					
Internet: danson@lgc.com			
Phone:	  713.560.1274
FAX:	  713.560.1277
SNAIL:    Landmark Graphics Corporation LGC	
	  15150 Memorial Drive
	  Houston, TX 77079			
-------------------------------------------
Newsgroups: comp.unix.bsd
From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
Subject: I18N and BSD future directions
Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages
Organization: Naval Research Laboratory, DC
Distribution: na 
Date: Sat, 19 Dec 1992 04:06:57 GMT

  Not to interrupt cross-cultural flaming or anything, but it is worth
mentioning that the Plan 9 folks at AT&T have come up with a scheme
for handling ISO-10646 in a way that reportedly works relatively well
with a UNIX-like file system.  Such capabilities would be a useful
addition to 4 BSD and would go a long way towards addressing I18N
issues.

  The other piece that is off the shelf and important is the "locale"
work in ANSI C and in the IEEE POSIX standards.

Ran
atkinson@itd.nrl.navy.mil
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Re: boot string; boot & root floppy set (was Re: Occasional system hangs)
Date: 15 Dec 92 20:46:28 GMT
Organization: Amdahl Corporation

In article <scott.724374170@pita.cns.ucla.edu>, scott@pita.cns.ucla.edu
(Scott Burris) writes:
> karl@NeoSoft.com (Karl Lehenbauer) writes:
> 
> >Another useful thing would be to have a "boot and root" floppy set,
> where
> >booting would pull the kernel off of one floppy but then pause for
> you to
> >insert a second floppy with the "real" root filesystem on it.  It
> would 
> >free up about 400K on the floppy for more useful programs, if it
> wouldn't 
> >be too hard to do.
> 
> Julian's boot blocks can already prompt you to insert a new floppy
> after 
> loading the kernel.  There are a couple of changes I needed to make
> to
> get this to work -- something to do with the boot code not properly
> recognizing you are booting from floppy.  I can post diffs if there's
> interest.

I would like to see them.  Of course, you might want to send them to Julian
also.

-- 
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
From: gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart)
Subject: Re: [386BSD] Comm software?
Organization: Technische Universitaet Muenchen, Germany
Date: Sun, 20 Dec 1992 13:23:46 GMT
Distribution: comp

In article <PETRI.WESSMAN.92Dec18104935@lk-hp-8.hut.fi> Petri.Wessman@hut.fi writes:
>Has anyone ported a comm program to 386BSD? Except tip, that is :-) I
>compiled pcomm-2.0 (or was it 2.1?) yesterday, but it doesn't manage
>to actually send anything to the com port, and panics the kernel (!)
>when I interrupt a dial attempt -- I'm using the new multiport com
>driver with a plain vanilla 2-port I/O card. I also tried a program
>called 'xc', but it's crawling with SysV-isms and would require a bit
>of hacking to compile. Don't tell me everyone's still using tip!

A 386BSD version of pcomm can be found on ftp.informatik.tu-muenchen.de
in /pub/BSD/386BSD/0.1-ports/misc.
It definitly works, cause I'm currently logged in via pcomm while writing
this article :).

Ralf
Newsgroups: comp.unix.bsd,alt.suit.att-bsdi
From: pcg@aber.ac.uk (Piercarlo Grandi)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Disklabel for MAXTOR LXT340S
Date: 18 Dec 92 22:37:54 GMT
	<1992Dec15.165013.18162@prism.poly.edu>
Reply-To: pcg@aber.ac.uk (Piercarlo Grandi)
Organization: Prifysgol Cymru, Aberystwyth

On 15 Dec 92 16:50:13 GMT, kapela@prism.poly.edu (Theodore S. Kapela) said:

(Martin BIRGMEIER) writes:

Martin> Hello netters,
Martin> MAXTOR LXT340S 6.20
Martin> cylinders: 324 <=========================== (!)

kapela> (Julian Elischer) writes:

Julian> It used the BIOS's idea of the geometry which is different.
Julian> (The adaptec sets it up to LOOK LIKE 32sec, 64heads, 324CYL) in
Julian> fact since the disk MAY have Zone recording we may BOTH be
Julian> wrong!

kapela> YES!  The drive *DOES* use Zone-Bit Recording (I have the IDE
kapela> version [ an LXT-340A ] that I am temporarily using for 386bsd.

Confirmed.


Actually recent SCSI/IDE disk drives are not disk drives at all. They
are fairly powerful minicomputers (the LCT340 has got a 68000 with 256KB
of RAM, quite a bit of ROM, and the operating system that runs on it
keeps overlays in the last cylinders of the disk itself) dedicated to
driving a disk drive.

The LXT340 is just a disk server, only it uses the SCSI protcol over a
SCSI bus rather than say NFS over an Ethernet bus.

The OS that runs on the minicomputer does a lot of nifty tricks, just
like a file server would do; caching, read ahead, error recovery and so
on. In practice it is impossible to treat it as a disk drive.

Therefore the best bet is to give a bogus geometry, of which the default
Adaptec supplied one is one of the most convenient, being N cylinders of
1MB each, which makes partitioning easier, and abandon all hopes of
doing lowe level optimizations as those done in the BSD filesystem code,
that try to minimize things like rotational latency, which are actually
handled by the LXT340 OS.

A couple of years ago we had a discussion on this; somebody recently
posted in this newsgroup a patch along the line sof that discussion that
just makes the BSD filesystem code try to keep block sequentially
contiguous if the parameters indicate it is a SCSI disk, with no fancier
layout policy (which are of dubious value anyhow).
--
Piercarlo Grandi, Dept of CS, PC/UW@Aberystwyth <pcg@aber.ac.uk>
  E l'italiano cantava, cantava. E le sue disperate invocazioni giunsero
  alle orecchie del suo divino protettore, il dio della barzelletta
Newsgroups: comp.unix.bsd
From: tjon@plains.NoDak.edu (Christopher C. Tjon)
Subject: Re: [386bsd] need motif 
Date: Wed, 16 Dec 1992 23:41:08 GMT
Organization: North Dakota Higher Education Computing Network
Keywords: motif 386bsd


BTW, If there is enough interest I could begin to maintain an archive here
on plains.nodak.edu.  I am sure that this package will need some porting
to 386bsd.  I was planning to do it over the holidays.  Feed back is 
welcome

-- 
Chris
		tjon@plains.nodak.edu	 Christopher C. Tjon
		uunet!plains!tjon (UUCP) Box 5224
		tjon@plains (Bitnet)	 Fargo, ND 58105-5224
This message brought to you by the letters X and S and the number 3.
Newsgroups: comp.unix.bsd
From: serini@ghost.dsi.unimi.it (Piero Serini)
Subject: swap
Organization: Computer Science Dep. - Milan University
Date: Sun, 20 Dec 1992 18:30:33 GMT

Hi all.

How can I know if my swap area is enabled ? I suspect my
box is not swapping at all. I have 16 megs of RAM, so I
never noticed it before i started using X and, say, xv.

I have a 486/50, 16 megs RAM, 425 SCSI drive.

Thanks and merry Xmas.
Piero

------------------------------------------ Piero Serini -----------------
Piero Serini	                  E-mail: serini@ghost.dsi.unimi.it   
Computer Science Dept.            or: piero@strider.st.dsi.unimi.it
Univ. Statale - Milano - ITALY      ** mail me your .signature **
-------------------------------------------------------------------------

Newsgroups: comp.unix.bsd
From: tjon@plains.NoDak.edu (Christopher C. Tjon)
Subject: Re: [386bsd] need motif 
Date: Wed, 16 Dec 1992 23:38:18 GMT
Organization: North Dakota Higher Education Computing Network
Keywords: motif 386bsd

I ftp'd what is claimed to be the first public domain version of Motif 
from somewhere in austrailia.  I dont have it online right now but I will
post the location of it as soon as I get some time as I am right in the middle
of finals.  I hope to find time by friday.  The name of the file was xmfm????
something.  I cannot remember exactly.  It is somewhere in .oz.

-- 
Chris
		tjon@plains.nodak.edu	 Christopher C. Tjon
		uunet!plains!tjon (UUCP) Box 5224
		tjon@plains (Bitnet)	 Fargo, ND 58105-5224
This message brought to you by the letters X and S and the number 3.
Newsgroups: comp.unix.bsd
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 23:35:37 GMT

In article <Bz5z4n.FoC@undergrad.math.waterloo.edu> wgsteven@cayley.uwaterloo.ca (Warren Stevens) writes:
>With regards to all this information on CD, can someone tell me when
>the CD is expected to be produced, who i can get info from, and all
>that other stuff?

[I've already mentioned this on comp.os.linux, so I've removed that
group from the Newsgroups line.]

	The Yggdrasil Linux/GNU/X Operating System distribution on
CDROM has been shipping since Tuesday.  You can get more information
by anonymous FTP from netcom.com:~ftp/pub/yggdrasil or by contacting me.

-- 
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).
From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su>
Newsgroups: comp.unix.bsd
Subject: [386bsd] Patch tty.c to fix TIOCSTI simulate 8-bit chars
Date: Mon, 14 Dec 92 22:35:47 +0300
Distribution: world
Organization: Ha-oh-lahm Yetzirah
Reply-To: ache@astral.msk.su

TIOCSTI produce nulls instead of 8-bit chars, here simple fix:

*** tty.c.was	Thu Dec  3 06:25:38 1992
--- tty.c	Mon Dec 14 22:23:52 1992
***************
*** 434,440 ****
  			return (EPERM);
  		if (p->p_ucred->cr_uid && !isctty(p, tp))
  			return (EACCES);
! 		(*linesw[tp->t_line].l_rint)(*(char *)data, tp);
  		break;
  
  	case TIOCGETA: {
--- 434,440 ----
  			return (EPERM);
  		if (p->p_ucred->cr_uid && !isctty(p, tp))
  			return (EACCES);
! 		(*linesw[tp->t_line].l_rint)(*(unsigned char *)data, tp);
  		break;
  
  	case TIOCGETA: {
-- 
In-This-Life:  Andrew A. Chernov    |  "Hay mas dicha, mas contento
Internet:      ache@astral.msk.su   |  "Que adorar una hermosura
Organization:  The RELCOM Corp.,    |  "Brujuleada entre los lejos
               Moscow, Russia       |  "De lo imposible?!"  (Calderon)

Newsgroups: comp.unix.bsd
From: g89s9112@hippo.ru.ac.za (Dirk Sturzebecher)
Subject: [386bsd] patch kit problems (bad patch kit ?)
Organization: Rhodes University, Grahamstown, South Africa
Distribution: global
Date: Wed, 16 Dec 1992 14:06:40 GMT

Hi all,
I have the original src and bin distribution. I put the patchkit into
/usr/src/patches and did run the mkpatchdirs. Then when I run the
patches command. It goes all OK until it starts installing the patches.
patch001 install fails ! Do I have a defect kit, or have I left out some
crutial step ?

Cheers, Dirk

-- 
-----------------------------------------------------------------------
Dirk Sturzebecher				g89s9112@alpha.ru.ac.za
Rhodes University Grahamstown			South Africa
Newsgroups: comp.unix.bsd
From: rivers@ponds.uucp (Thomas David Rivers)
Subject: Wangtek 5099/5150ES questions.
Summary: How to read 5099 on a 5150ES, what are 5099 settings?
Keywords: WANGTEK, 5099, 5150ES, SCSI tape, tape, QIC-120, QIC-60
Date: Tue, 15 Dec 1992 01:25:56 GMT


 While we're talking tape drives here, I have two questions to pose
 to the net-at-large.

  1) I have replaced my Wangtek 5099-EN 24 (QIC-60 with it's own controller)
 with a Wangtek 5150ES, hung off of my SCSI controller.  Although
 it seems to have no problems reading/writting new tapes (and it
 streams *very* well) it doesn't seem to be able to read tapes written
 with the 5099.  It reads *some* of the tape, never very much...
 Is there some special magic to getting this to work?


  2) I had to permute the settings on the 5099 controller making guesses
 until I hit on 0x300 as the address.  You guessed it, I bought this
 second hand a *long* time ago, and go *no* documentation with it.
 I would appreciate if someone could send me the switch settings, etc...
 as I would like to have this tape drive in another box (to read the
 old tapes), but the 0x300 address conflicts with my NE2000 card.  
 The controller looks like:

   +------------------------------------------------------------------+
   |     ASSY  30006-002               EV-835  REV. C                 |
   |                                                                  |
   |                                                                  |
   |                                                          ==----------
   |                                                          ==----------
   |                                                          ==-----------
   |                   1 2 3 4 5 6 7 8 9 10                   ==---Ribbon---
   |              On  +--------------------+                  ==----Cable---
   |                  |S S S S S S S S S S |                  ==-------------
   |              Off +--------------------+                  ==-------------
   |                                                          ==-------------
   |                                   IRQ O41 DRQ DACK               |
   |                                  2345 67  123 123                |
   +--------------------------------+                    +------------+
                                    ||||||||||||||||||||||
                                    +--------------------+

 Where the large block in the center (labelled "On"/"Off") is a set of
 10 switches.  The numbers items labeled IRQ (obviously Interrupte Requst #),
 041, DRQ and DACK are jumpers.  That is, each of the digits represents a
 single jumper, in a contiguous row - it's just hard to draw that... 

  The board is made by Wangtek and is labelled "ASSY 30006-002 - REV. C".

 If anyone has any info about the switch settings, I'd really appreciate
 it.

    - Thanks -
   - Dave Rivers -

Newsgroups: comp.unix.bsd