HDTenEightyP/NetNews huggingface dataset:
From: tlukka@vipunen.hut.fi (Tuomas Lukka)
Subject: Re: getdtablesize
Organization: Helsinki University of Technology, Finland
Date:  1 Oct 92 11:22:21 GMT

In <1992Sep30.164745.13200@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:

>In article <1992Sep29.142535.21001@nntp.hut.fi> alo@kampi.hut.fi (Antti Louko) writes:
>>In article <Bv7Dz7.C2o@BitBlocks.com> bvs@BitBlocks.com (Bakul Shah) writes:
>>>tlukka@vipunen.hut.fi (Tuomas Lukka) writes:
>>>>for(i=getdtablesize(); --i>2; close(i));
>>>>and getdtablesize returned something like 2000000000 and this
>>>>naturally would take a while to run... 
>>
>Obviously, the value you are seeing for getdtablesize() is wrong... are
>you sure it is either undeclared or declared as an external int?  I get
>64 ...of course, my kernel is patched to all get out, but I don't believe
>any of them effected the open files tables.

>I tried declaring the function extern short, int, and double, but always
>got 64.

I AM sure, and the real weirdness of the problem is, that 
WHEN I'M RUNNING THE THING UNDER CSH, IT WORKS!! I.E. getdtablesize
returns a reasonable value, and everything works out.

	TJL
-- 
 /--\  TJL -- Tuomas J. Lukka  tlukka@vipunen.hut.fi IIIIIIIII -------    Just
/-\ o\        Puistokaari 1E18  _________--------------------+    I  J     go
\o \-/        00200 Helsinki    --------I GONE FISHING AGAIN ->   I        to
 \__/  SIGh.. Finland T. +358-0-6923924 /---------------------    L___    sleep..
Newsgroups: comp.unix.bsd
From: bad@flatlin.ka.sub.org (Christoph Badura)
Subject: Re: 386BSD and IDE drives
Organization: Guru Systems/Funware Department
Date: Sat, 3 Oct 1992 03:20:24 GMT

In <id.O7NT.0O3@ferranti.com> peter@ferranti.com (peter da silva) writes:

>In article <Bv32LD.K9t@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>> 	Something is very wrong here.  My experience is that IDE drives
>> 	are great for UNIX and IDEAL for 386bsd.  Main reason is that, like
>> 	SCSI, they hide bad sectors from the OS.

>This is the one problem with SCSI, and presumably IDE. Why? What happens
>when you have a marginal disk? When you're running MFM or ESDI, you start
>getting more and more disk errors, and you have time to back up and reformat.
>When you're running SCSI, you suddenly (without warning) get a LOT of errors
>when the bad sector table fills up. By then it's too late to do anything
>about it.

Fortunatly, one can disable the automatic remapping of bad sectors on
most SCSI drives. And even better, SCSI-2 provides a standard way to
do so.
-- 
				Christoph Badura  ---  bad@flatlin.ka.sub.org

AIX is a better... is a better...  is a better... OpenSystem.
					IBM Rep at GUUG Symposium '92
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: [386BSD] troff: out of memory
Keywords: 386bsd troff memory
Date: 3 Oct 92 12:15:20 GMT
Organization: HCS GmbH, Hamburg, Europe

recently i got the error message "troff: out of memory" while formatting
two large manuals (cnews-guide and nn) using groff with the postscipt output
option.

has anyone already a solution for that ?

btw, how can a program on a vm-os run out of memory ??? mysterious ....

hellmuth
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
From: julian@tfs.com (Julian Elischer)
Subject: Re: Booting 386BSD from second hard drive
Organization: TRW Financial Systems
Date: Fri, 2 Oct 1992 22:10:34 GMT

In article <1992Oct2.035826.863@spang.Camosun.BC.CA> dbarker@spang.Camosun.BC.CA (Deryk Barker) writes:
>
>OK - here's the scenario. I want to run OS/2 and DOS on my new system,
>which will have a 170MB hard drive. When finances allow I want to buy
>a second hard drive and would like to install 386BSD on that. OS/2's
>boot manager will allow you to boot from a partition on drive #2, so
>the question is, will 386BSD do that? If not what is the minimum sized
>partition which I would need to leave on drive #1 for 386BSD to boot
>from?
>
>Deryk Barker, Computer Science Dept., Camosun College, Victoria B.C.
>
With the new boot blocks the minimum sized partition needed
to boot from the second hard disk is 14 sectors

Of course there is not reason that it needs to be 
a real partition.

All unix filesystesm leave at least that much room
free before the superblock, so what I do is to set up a 
boot partition on the second disk,
then patch the figures in teh master boot block of the 
first disk to point to the beginning of some unix partition
where I can conveniently dump a copy of then new bootblocks
which have been modified to default to drive 2.

I use os-bs to set the default partition on the first disk
to be the fake partition and off I go.
basically you can make the fake partition any set of 14
contiguous blocks that you know will not be overwritten.
(you could put them in a file on DOS if you could be sure that
it was not going to be deleted, and that it was contiguous).

julian
+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v



Newsgroups: comp.unix.bsd
From: pauls@css.itd.umich.edu (Paul Southworth)
Subject: Re: 386BSD and IDE drives
Organization: University of Michigan ITD Consulting and Support Services
Date: Tue, 29 Sep 1992 14:01:17 GMT

In article <id.O7NT.0O3@ferranti.com> peter@ferranti.com (peter da silva) writes:
>In article <Bv32LD.K9t@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:
>>       Second, for a 1 or 2 drive system, IDE
>> 	is a non-negligable amount less cost than SCSI.
>
>Not unless you really compromise on the quality of the drives, or unless
>you've got some sort of special deal. Street prices vary by $20-$50 for
>the same drive in SCSI and IDE versions.

Uh, wait a minute.  The mechanisms are about the same.  But have you ever
compared price of controllers?  Mine was $10.  How much is an Adaptec 1542?

Paul Southworth                    |     ftp redspread.css.itd.umich.edu
Consulting and Support Services    |        Anonymous Political Archives
Information Technology Division    |                     100% 386BSD 0.1
University of Michigan, Ann Arbor  |  Coming soon: mirror of ftp.eff.org

  <Representing myself.  Everything I say is for educational use only.>
From: peter@ferranti.com (peter da silva)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD - what a pain to install!
Date: 3 Oct 92 17:44:59 GMT
Organization: Xenix Support, FICC

I've completely lost the thread of this discussion, and I'm certainly not
about to argue that 286 segments are in any way desirable, but...

In article <1992Oct2.155958.29182@fcom.cc.utah.edu> terry@icarus.weber.edu writes:
> "Large model" (which differes from "Medium model" by frequent segment register
> reloads) has always seemed like a kludge to me, mostly because of the 286
> being set up for 64K segments in the first place.

The kludge is the 64K segments. Large model is a reasonable response. Intel
even uses it (we're using Intel Fortran, PL/M, and C compilers, which is why
we're still using Intel Xenix because Intel in their infinite wisdom decided
that MS-DOS was a better software development platform than UNIX and dumped
the UNIX compiler products (though they still use them internally: do as I
say, not as I do, I suppose)) for all their languages.

In any case, you can always buy a used TRS-80 model 16 and run Xenix on a
68000.
-- 
Peter da Silva                                          `-_-'
Ferranti Intl. Ctls. Corp.                               'U` 
Sugar Land, TX  77487-5012
+1 713 274 5180                           Heb jij vandaag je wolf al geaaid ?
Organization: Stanford Linear Accelerator Center
Date: Monday, 28 Sep 1992 12:23:40 PST
From: <CALT@SLACVM.SLAC.STANFORD.EDU>
Newsgroups: comp.unix.bsd
Subject: Xconfig file

Hi -- I got X386 split files (58 files) unpacked on my 386.
Then I did a "# mknod /dev/vga c 12 0". After typing
# xinit
X386 Version 1.2E 1.0.1 / X Window System
(protocol version 11, revision 0, vendor release 5000)
then system hangs.

Could someone advise me what to do next?
Any patches needed?
How to get a correct Xconfig file?
(I have an NEC MultiSync 3D, ATI1024 card, and
Logitech mouse.)

Any information would be greatly appreciated!

Ching Shih
shih@cithex.bitnet
shih@cithex.caltech.edu
Newsgroups: comp.unix.bsd
From: kzin@terminus.gatech.edu (John Rudd)
Subject: Re: BSD/386 and 50Mhz 486
Keywords: maximum users, drivers
Organization: Georgia Tech College of Computing
Date: Wed, 30 Sep 1992 11:17:12 GMT

kzin@terminus.gatech.edu (John Rudd) writes:

>I'm looking in to running 2 486/50's running BSD/386 by
>BSDI.  I need to know what multi-port boards it has drivers
>for (since most of them only come with drivers for sysv), or
>that I can get drivers for, and how many users people think it'll
>support.

>each will be EISA machines, networked to a third box that provides
>a 56k line to the internet.  Each will have a 1.2 GB scsi drive (one
>for users, one for news).  Both will play NFS server for the other.
>I'm wanting to hang 24 users off of each machine.  That sound overtly
>unreasonable? (no one will be doing anything off of the console..
>except maybe regular terminal like things..definitely no heavy x work
>or anything.  Also, most of the things I expect people to do are vi,
>news, mail, and network chat/mud programs.  Probably some people will
>be compiling stuff, but I don't expect it to be widespread)

>(alternate configurations are welcome too, but try to keep the price
>range of this setup in mind (under $30k for the two 486's and their
>multiport boards))


I'm sorry..I forgot to mention an important aspect of they two
486 boxes.. They'll probably have 64MB each, and their boot drive
wont be the 1.2 GB drive, but a 200 MB drive (both SCSI).

Consensus makes an intelligent (coprocessor driven) multi-port board
that comes with "drivers for Xenix and Unix".  A company called
Stallion makes a simular board, that says the same thing ("comes with
drivers for Xenix and Unix).  The Stallion board has a 80186 coprocessor.
(I'm assuming from other things that I have read, that they meant SysV,
anyone that can confirm or refute that, I'd really appreciate hearing so)

John Rudd  --  kzin@cc.gatech.edu         ex- kzin@ucscb.ucsc.edu
All opinions expressed here are my own, and no one elses.
--If Happy Fun Ball begins to smoke, leave the area immediately,
  seek shelter, and cover your head.  Do NOT Taunt Happy Fun Ball.
Newsgroups: comp.unix.bsd
From: u84167@aix01.rz.fht-mannheim.de ( )
Subject: problem,ith compiling kernel
Date: Mon, 05 Oct 92 11:33:26 GMT
Organization: Fachhochschule fuer Technik Mannheim
X-Newsreader: Tin 1.1 PL4

hello out there,

I've a problem: 

I've three serial ports in my computer, which i would like to use under bsd.

A frind told my that i should compile the kernel, after changing the 
GENERICISA .....

I changed .... and made config GE....
                        cd /sys/compile/....
                        make depend
                        make

he (the computer) did his compiling work and then he said:
loding 386bsd
init_main.o undefined symbole _version reference from text segment
*error code 1

stop.
....

could anybody help me :-) ??????

Arno....

(sorry my english is really so bad..... :( )

i-net: fh07@rummelplatz.uni-mannheim.de
From: wmbfmk@rw9.urc.tue.nl (Marc van Kempen)
Newsgroups: comp.unix.bsd
Subject: Re: Lance query
Date: 4 Oct 92 09:26:24 GMT
Reply-To: wmbfmk@urc.tue.nl

spedpr@thor.cf.ac.uk (Paul Richards) writes:

>I've been getting a number of is1:reset errors from the isolink driver
>and the cause is due to the lance stopping its transmitter.
>Specifically, in the interrupt routine the transmitter-on (TXON) bit of
>the lance is checked and if it isn't set then a reset occurs.

>What I want to know is: under what circumstances does the lance clear
>this bit, supposedly indicating that the transmitter has been switched
>off?
I am currently working on a driver for the Lance and this is what
the documentation says about TXON:

TRANSMITTER ON indicates that the transmitter is enabled. TXON is set
if DTX=0 in the mode register in the initialization block and the INIT
bit has been set. TXON is cleared when IDON is set and DTX=1 in the MODE
register, or an error, such MERR, UFLO or BUFF, has occurred during
transmission.
TXON is READ ONLY; writing this bit has no effect. TXON is cleared by
RESET or by setting the STOP bit.

MERR : 	Memory error is set when the LANCE is the bus master and has 
	not received READY within 25.6 microsec. after asserting the
	address on the DAL lines.
	If this is the cause then it seems to me that you have a serious 
	hardware problem. I guess however that it would show up on 
	other cards as well.
UFLO :	Underflow error indicates that the transmitter has truncated 
	a message due to data late from memory. UFLO indicates that
	the silo has been emptied before the end of the packet was
	reached.
	Something wrong with the bus being too slow???
BUFF :	Buffer error is set by the LANCE during transmission when the 
	LANCE does not find the ENP flag in the current buffer and does
	not own the next buffer. (ENP = End Of Packet, bit 8 in the
	Transmit Messages Descriptor 1, (TMD1)) (counting is from 0). 
	I guess this would be a simple programming error.

I hope this is of any help and that you didn't already have this
information.

Marc.
(wmbfmk@urc.tue.nl)
Newsgroups: comp.unix.bsd
From: mark@alias.com (Mark Andrews)
Subject: Whatis gremlin?
Organization: Alias Research Inc., Toronto ON Canada
Distribution: na
Date: Fri, 2 Oct 1992 18:37:00 GMT

I have been trying to format some of the 4.3bsd IPC tutorials. This seems
to require a utility called gremlin to draw figures. Anyone know what it
is and where I can get it?

Thanks,

Mark
Newsgroups: comp.unix.bsd
From: pauls@css.itd.umich.edu (Paul Southworth)
Subject: Re: Catch What They're Saying About Us...
Organization: University of Michigan ITD Consulting and Support Services
Date: Tue, 29 Sep 1992 15:05:39 GMT

In article <1992Sep29.132808.29177@prism.poly.edu> kapela@prism.poly.edu (Theodore S. Kapela) writes:
>In article <1992Sep25.021813.2369@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>>BSDi is actually benefited, to some degree, by 386BSD.  BSD/386 is stabler,
>>better supported, and commercial (and proprietary; one need not follow from
>
>Better supported?  A few techies compared to thousands of readers of this
>newsgroup?  And what happens if BSDI goes out of business?

Couldn't agree more.  The support I get out of this newsgroup is better,
faster and cheaper than any support I've received from any commercial
firm.

Not to mention friendlier.

>Nowhere in the distribution is any mention made that 386BSD is a production
>system.  In fact, the notes emphasize that the release is targeted for
>research/education, not the commercial sector.

Nonetheless, I have basically been using the system only as an end-user,
and I would characterize my impression as *far* from dissatisfied.
I have no desire (or reason) to change.

Paul Southworth                    |     ftp redspread.css.itd.umich.edu
Consulting and Support Services    |        Anonymous Political Archives
Information Technology Division    |                     100% 386BSD 0.1
University of Michigan, Ann Arbor  |  Coming soon: mirror of ftp.eff.org

  <Representing myself.  Everything I say is for educational use only.>
Newsgroups: comp.unix.bsd
From: rt@MAGEC.COM (49)
Newsgroups: comp.unix.bsd
Subject: Re: Catch What They're Saying About Us...
Date: 1 Oct 92 14:41:34 GMT
Organization: MAGNAVOX Electronics Systems Co., Fort Wayne

In article <1992Sep29.132808.29177@prism.poly.edu>, kapela@prism.poly.edu
	(Theodore S. Kapela) writes:
> In article <1992Sep25.021813.2369@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
> >BSDi is actually benefited, to some degree, by 386BSD.  BSD/386 is stabler,
> >better supported, and commercial (and proprietary; one need not follow from
> 
> Better supported?  A few techies compared to thousands of readers of this
> newsgroup?  And what happens if BSDI goes out of business?
> 
I could not disagree more.  While there may be fewer 'techies' supporting
BSD/386 the signal to noise ratio is much higher.  

As to BSDi going out of business, the most likely cause of that
happening is a loss to the death star (tm).  In that case, IMHO, we are
all 'out of business'.

-- 
Al Marshall
rt@magec.com					Standard Disclaimer...
netwrk!rt
Newsgroups: comp.unix.bsd
From: anything@max.u.washington.edu
Subject: [386BSD] extract etc01 fails
Organization: 
Date: Thu, 1 Oct 1992 20:21:12 GMT

extract etc01 works fine until it gets to the final installation line then
it says "extract.etc01 /tmp/install.etc01 unable to find file" or something of
the sort. what now? is etc01 installed or am I up a creek?

Xref: sparky comp.unix.bsd:6404 comp.os.linux:11729
From: ajt@doc.ic.ac.uk (Tony Travis)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Problems reading partition table in 386bsd
Date: 26 Sep 92 22:29:10 GMT
Reply-To: ajt@rri.sari.ac.uk
Organization: Dept. of Computing, Imperial College, University of London, UK.
NNTP-Posting-Host: swan.doc.ic.ac.uk
X-Newsreader: TIN [version 1.1 PL6]

I've just re-installed 386bsd onto a 100Mb Quantum IDE drive on my
Elonex PC-320X (20MHz 386SX with 4Mb RAM) from the distribution
floppies and I noticed that, occasionally, 386bsd fails to read the
partition table correctly and reports that the 'b' partition overlaps
the 'a' partition so refuses to use it as a swap area.

I've checked using "disklabel wd0" and the 'b' partition appears to
start at cylinder 0 in the kernel's copy, when the error is reported.
But re-reading the label with '-r' shows that the label is intact on
the disk.

I suspect that this may have been the cause of the poor response I
observed from shell commands in the foreground whilst compiling the
GENERICISA kernel in the background.  With only 4Mb of memory and no
swap space it is likely that my foreground processes blocked.

As far as I am aware, this problem only occurs at boot-time and
repeatedly re-reading the label with "disklabel -r wd0" worked
correctly every time.

The remarks I made about the relative performance of Linux and 386bsd
on comp.os.linux were honest, but inaccurate.  Bill Jolitz was right
not to believe me and I apologise for misleading everyone.

	Tony.
--
Dr. A.J.Travis,                       |  Tony Travis
Rowett Research Institute,            |  JANET: <ajt@uk.ac.sari.rri>
Greenburn Road, Bucksburn,            |  other: <ajt@rri.sari.ac.uk>
Aberdeen, AB2 9SB. UK.                |  phone: 0224-712751
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd]Wanted:PC Diagnostic reporting bad BLOCKS (not track/head)
Date: 6 Oct 92 17:12:54 GMT
Article-I.D.: fcom.1992Oct6.171254.20906
Organization: Weber State University  (Ogden, UT)

In article <1aqootINNo3l@roche.csl.sri.com> caveh@spartacus.csl.sri.com (Caveh Jalali) writes:
>note that you will have to verify that your driver *correctly* supports
>sector remapping.  the original 386BSD driver does not.  i've beaten mine
>into submission so that it works for me.  i think there are patches
>which claim to fix sector remapping as well.  my version of wd.c is
>has significant changes, so i don't think i can send diffs at this point.

The bad sector forwading code is included in the patch kit.  It appears to
work for me (which is *why* it was included in the patch kit).

>another enhancement i made was to introduce the convention that sector
>#255 is a wildcard sector, such that the entire track is marked as remapped.
>this is somewhat consistent with the SCSI convention, but more importantly
>cuts down the size of your bad144 table by a factor of 17!  this is significant
>since the table needs to be scanned (linearly right now!) for every disk
>transfer (generally 8K).

We actually should do what ACER did here and go to a bit vector.  This should
speed it up by a factor of 8.  Obviously we would alo want write-through
caching on the bad sector list so the traversal can be made in memory --
are you sure that the table isn't in core anyway?  The normal LRU should
act to keep it there if it's small enough.  If it isn't small enough, the
bad performace will act as incentive to get a better disk.

>one question i have about the current wd.c driver is whether it handles the
>case correctly, where a disk transfer starts on a "normal" sector, but
>either has a bad sector in the middle of the transfer or at the end.
>is the driver smart enough to split the transfer into the required 2 or 3
>sub-transfers???  could someone familiar with the current driver let me
>know, please?

By default, not it isn't; with the proper patches applied (also in the patch
kit), yes, this works.


					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.solaris,comp.periphs.scsi,comp.sys.sun.hardware
From: bdj@lepton.med.ge.com (Brian D. Johnston)
Subject: Re: HP DAT drive under SunOS 4.1.2
Organization: GE Medical Systems, Waukesha, WI, USA
Date: 27 Sep 92 10:02:31

>>>>> On 25 Sep 92 08:06:26 GMT, chas@visionware.co.uk (Charles Hirst) said:
Charles> Originator: chas@poohbear


Charles> I am trying to connect a shoe-box containing a

Charles> HP HP35470A DAT drive on SCSI ID 4

Charles> and a

Charles> Wangtek QIC-150 on SCSI ID 5

Charles> to a Sparc Station 2 running SunOS 4.1.2

Charles> I can talk to the Wantek quite happily, but whenever I talk to any of the
Charles> device nodes that refer to the DAT drive I get an I/O error.

Charles> Going through the st and mtio man pages I can see that the Sun does not have 
Charles> explicit support for DAT drives, but I was hoping I might get away with
Charles> being a "generic scsi" unit.

Charles> On booting, the Sun correctly sees both the drives, and on first open of the
Charles> DAT drive the following is displayed on the console

Charles> #tar cvfb /dev/rst0 2 /etc
Charles> st0:	Generic Drive, Vendor = <HP          >
Charles> 3.81mm helical scan cartridge
Charles> Variable record length I/O
Charles>  esp0: Target 4 now synchronous at 4.0 mb/s max transfer rate

Charles> tar  /dev/rst0: I/O Error
Charles> #

Charles> If I use the mt command to request the drive status all I get is

Charles> #mt -f /dev/rst0 status
Charles> esp0: Target 4 now synchronous at 4.0 mb/s max transfer rate
Charles> /dev/rst0 no tape loaded or drive offline
Charles> #

Charles> I have looked around the system, and am begining to wander if I need to modify
Charles> /usr/kvm/sys/scsi/targets and add an entry for this unit.  However if I do, what
Charles> type of drive is it, as the Sun only seems to understand EXEBYTE.

Charles> Thanks in advance for any help

Charles> Charles Hirst


Charles,

I have been using the HP DAT drives on Sun's for several months. They
always fail with the first attempt at accessing the DAT.  Do your tar
command then repeat the command and it should work.  I also almost
always get  the message:
esp0: Target 4 now synchronous at 4.0 mb/s max transfer rate

whenever I access the DAT.


--
		     Brian D. Johnston, PET Team
   GE Medical Systems, W641, P.O. Box 414, Milwaukee, WI 53201-0414
	     (414) 548-5189 : EMAIL -  johnstonb@med.ge.com
Xref: sparky comp.unix.solaris:229 comp.periphs.scsi:4743 comp.sys.sun.hardware:4653