HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.unix.bsd

/ hpycla:comp.unix.bsd / armhold@action.rutgers.edu (George Armhold) /  1:34 am  Aug 15, 1992 /

armhold> "Press any key to reboot from HD".  I do, and the machine
armhold> goes into an endless boot cycle.  When it tries to read the bootstrap
armhold> code from the HD it does a hard reset, memory check, etc, and then
armhold> loops again. 

This is exactly the same situation as mine!
The following is my configuration.

   HI-Tech USA ISA-486/33 w/ AMI BIOS and SiS Chipset
   8MB RAM
   Adaptech 1542B
   HP2213A 633MB SCSI Disk
   IBM DOS 5.0

I removed all cards (i.e. IDE/FDD,1P/2S/1G) except Video (Diamond
SpeedStar Plus) and 1542B from AT bus and re-installed 386BSD from the
FDD controlled by 1542B. But the situation was not changed.

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.

--
Yasuyuki Suzuki         yas@kobe.hp.com   +81-78-993-2846 (JAPAN)
Client Technology Lab., Kobe Systems Operation,   Hewlett-Packard
Newsgroups: comp.unix.bsd
Subject: Re: time for comp.unix.bsd.386
From: jiu1@husc9.harvard.edu (Haibin Jiu)
Date: 22 Aug 92 13:06:19 EDT
Organization: Harvard University Science Center

In article <34254@hoptoad.uucp> brendan@cygnus.com writes:
>
>Any reason not to start a discussion for creating comp.unix.bsd.386?
>(For the many people who are interested in geeric BSD issues, but
>could care less about device drivers in 386BSD, etc.)

Someone please do this!!!!!!  People like me who use true 4.xBSD
UNIX need this group to talk about issues that concern 4.xBSD in
general.  There has been just too much on 386BSD (which I abandoned
after deciding it was not as robust as my MS DOS 5 or DR DOS 6 --
please do not flame on this!) and not enough about the real BSD.

Bugs
Newsgroups: comp.unix.bsd
From: bill@twwells.com (T. William Wells)
Subject: Cpio and symbolic links (was Re: stock 0.1 swap not enough.)
Organization: None, Mt. Laurel, NJ
Keywords: cpio, bug, symbolic link
Date: Fri, 14 Aug 1992 23:39:18 GMT

This may be relevant to those who use cpio for backups: it appears
that cpio generates bogus output for symbolic links. I haven't
checked this out fully so someone else may want to try and confirm
this.

---
Bill                            { uunet | decwrl | telesci }!twwells!bill
bill@twwells.com
Newsgroups: comp.unix.bsd
From: cproto@marsh.cs.curtin.edu.au (Computer Protocol)
Subject: Re: (386BSD) Modems and com ports
Keywords: internal or external?
Organization: Curtin University of Technology
Date: Fri, 21 Aug 1992 14:35:48 GMT

hasty@netcom.com (Amancio Hasty Jr) writes:


>I think that if the com driver is strap to interrupt levels less than 
>disk level, then under heavy I/O activities the com drivers will drop
>characters. If the com drivers is split into two parts:
>(a) a routine at  high level interrupt level less than splhigh and at
> least as high  as diskio that just collects the characters and queues 
> the requests to be processed at a lower priority.

>(b) essential the same com driver that de-queues the request from its
>    higher level routine

>If such a scheme is not implemented, it is conceivable that the system
>may lock out spltty interrupts long enough for the uart to drop characters.

>The above outlinde strategy has been implemented in Unix systems for pcs
>with good results for instance the system being able to drive four
>com ports at 9600  without dropping a single character.

>Cheers,
>Amancio Hasty



I couldn't agree more. Here at Computer Protocol we have developed 68000
based boxes running at whimpish 10 MHz with 4 simple Zilog 8530 serial
controler chips providing 8 synchronous ports. It easily supports 8
full duplex X.25 links at 9600 b/s. Compare that to a 486 at 33MHz and
with only one 9600 b/s port. Unless you do something really silly, it
shouldn't be a problem. 386BSDs com driver sucks, it can't keep up.

I would write a new com driver from scratch using the strategy posted
by Amancio but I haven't got the time. It's definitely the right way
to go.

If nobody else voluntiers then I might risk a divorce and do it at home.

Regards - Tibor Sashegyi (cproto@abel.cs.curtin.edu.au)
From: andrew@zone4.ocunix.on.ca (Andrew Low)
Newsgroups: comp.unix.bsd
Distribution: world
Subject: Re: 2nd drive file ... (Actually wd ESDI problems)
Organization: Zone4
Date: Thu, 13 Aug 92 03:20:05 GMT

In article <193@asgard.mlb.dmt.csiro.au> 
mjj@mlb.dmt.csiro.au (Murray Jensen) writes:
>partition C *contains* partitions A, B, E, F, G, H *and* the bad144 area,
>none of which should overlap if they exist.

Well, I don't get it because you go to some trouble to explain that the
bad144 area is contained within the C partition - then..

>		  size	offset	cylinders
>	A:	 10360	 80640	 288- 324
>	B:	 30800	 91000   325- 434
>	C:	205240	 80640	 288-1020
>	D:	285880	     0	   0-1020
>	E:	 80080	   560	   2- 287
>	H:	163800	121800	 435-1019

80640 + 205240 = 285880 (which is the size of the D partition, no?)

Thus it seems to me that this disktab entry doesn't leave any space
for the bad144 sector markings.  My *guess* at the 5 cylinder number is
that 386BSD will try to re-map sectors from that 5 cylinders of free
sectors onto the bad sectors, this allows for 'perfect' media..

Maybe this is in the FAQ, if so please ignore this.  If not, can someone
add something to the FAQ about how the bad sector mapping is handled,
how your disktab entry should look when its done (with some attention
given to the fact that IDE drives should not use bad sector mapping and
how this is done)?

Thanks (especially to the creators of 386bsd!)
+/+\+/+\+/+chew carefully/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+\+/+
Roo [andrew@zone4.ocunix.on.ca] m a c h i n e l o v e h a t e f e a r v o i d .
               "dreams are all that separate us from the machines"
From: dana@me.chalmers.se (Dan Andersson)
Newsgroups: comp.unix.bsd
Subject: Re: X386BSD Don't start
Date: 20 Aug 92 21:19:02 GMT

I received the advice that compile and link the kernel with -DXSERVER.

The kernel from X-dist does not work ( for me ).

After making a new kernel... The xinit starts, i get two lines of text
and it just enters the binary nirvana.

The machine dont hang entirely. I can log in from my VAX with telnet
and kill the process, wherafter i have a core.X386 in $HOME... 

Any more hints?


Dan Andersson   ///  dana@theta.chalmers.se

Newsgroups: comp.unix.bsd,comp.unix.solaris,comp.org.usenix,comp.sys.super
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: Re: Endless boot cycle- suggestions?
Date: 20 Aug 92 04:09:25 GMT
Article-I.D.: maverick.17092lINNju6
	<Aug.18.17.41.42.1992.4915@action.rutgers.edu>
	<1072@galileo.rtn.ca.boeing.com>
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu
In-reply-to: dmp3592@galileo.rtn.ca.boeing.com's message of 19 Aug 92 16:28:05 GMT

In article <1072@galileo.rtn.ca.boeing.com> dmp3592@galileo.rtn.ca.boeing.com (Dean M. Phillips) writes:


>A disk drive which does geometry translation will hopelessly confuse
>386BSD.
>
>Background:
>
>MessDOS has a hard limit of 10 bits for a cylinder number.  This
>prevents MessDOS from accessing cylinders beyond 1023.  Most large hard
>disks have more than 1024 cylinders.
>
>So, to make these disks useable with MessDOS, the disk drive
>manufacturers invented geometry translation.  The way this works is the
>drive says that it has more heads than it really does, and less
>cylinders than it really does, so that the total number of sectors
>comes out the same but with less than 1024 cylinders.  When MessDOS
>asks for a particular track, sector, and cylinder, the drive silently
>translates this to the real location.  "Brain damage begets brain
>damage."
>
>386BSD gets the geometry and its partition info from the partition
>table and then TURNS OFF GEOMETRY TRANSLATION.  If geometry translation
>was on in the first place, 386BSD will get hopelessly lost, fail to
>find its disk label and panic.

This is not totally true.  I have a MAXTOR 7120/A IDE drive that has a
true geometry of 1516 cyl, 4 heads and 42 sec/track.  However, there
are a couple jumpers on it that you use to set the geometry that it
reports when asked, one of which is 935 cyl, 16 heads and 17
sec/track.  You can set the geometry to be anything in the BIOS so
long as the total number of sectors comes out <= the real number.

My problem in getting 386BSD up was that I was using the above
geometry in the BIOS, but the jumpers were set for a 1024 cyl, 16
head, 14 sec/track geometry.  This did not make any difference until I
tried using 386BSD.  The disklabel program on the fixit disk showed
the geometry as reported by the drive and not the BIOS settings.
Although I could get it to write a disklabel at the right place with
the right stuff in it, it could never find it at boot time.

I finally figured this out last night and shorted the jumpers to make
the drive say that it had 935 cyl, etc.  Now it all works fine, and it
is using geometry translation.  My drive does not have any way to shut
it off as far as I can tell.  It gives you a choice of 4 different
translations, settable by jumpers, but none of them are for the real
geometry.

I'm sure this isn't the same for all drives.  Some probably always
return the real geometry when asked.  The MAXTOR just has a different
idea of what REAL is.

++Brett;

BTW, I have spec sheets for the 7120/A.  If anyone would like info
like what the jumper settings are or anything like that, send me mail.
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: Endless boot cycle- suggestions?
Date: Wed, 19 Aug 92 11:04:26 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <Aug.18.17.41.42.1992.4915@action.rutgers.edu> armhold@action.rutgers.edu (George Armhold) writes:
>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...

    How about folk medicine?  I found that my graphics and I/O cards
    were interfering with my disk controller (1542B).  The solution was
    to stuff the graphics card in an 8-bit slot until the installation
    was complete...
    -Andrew Moore <alm@netcom.com>
Newsgroups: comp.unix.bsd
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: Restrictions on 'free' UNIX / 386BSD (Re: selling 386BSD)
Organization: Kithrup Enterprises, Ltd.
Date: Mon, 17 Aug 1992 07:39:54 GMT

In article <5146@airs.com> ian@airs.com (Ian Lance Taylor) writes:
>Apple seems to do fairly
>well with a freely redistributable operating system.

APPLE DOES NOT HAVE A FREELY REDISTRIBUTABLE OPERATING SYSTEM!

Any macintosh is licensed for the Apple OS, but that is *it*.  Any and all
clones that might, or might not, exist are not allowed to run the code.

That is an important point.

-- 
Sean Eric Fagan  | "You can't get lost in 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.
Newsgroups: comp.unix.bsd
From: jsaker@cwis.unomaha.edu (James R. Saker Jr.)
Subject: Re: 386BSD QIC-02 Driver with Wangtek 5150PK is sloooooow
Organization: University of Nebraska at Omaha
Date: Fri, 21 Aug 1992 01:38:50 GMT

dmuntz@dip.eecs.umich.edu (Daniel A Muntz) writes:

>The problem isn't the 512-byte blocks, per se, but that the controller doesn't
>receive data quickly enough to allow the drive to stream properly.  You can
>get some performance improvement by buffering data in the driver and polling
>the controller instead of waiting for interrupts and timeouts.  Perhaps
>someone could comment on why so many interrupts seem to get lost.  I've
>hacked wt.c to do buffering and polling to make the qic-02 drives usable, but
>this isn't really the "right" solution.  A couple of thoughts:

Would this explain why my tar -cvf /dev/rwt0 to my Wangtek QIC-150 drive
produces unusual "features", including:

	o wildcard tarring writes only one file from each sequence,
	  for example, tar -cvf /dev/rwt0 etc*   with files etc01 to etc09,
	  etc10 to etc19, etc20 to etc29  results in one file from etc0*,
	  one file from etc1*, etc. (i.e. etc04, etc18, etc21, etc33 being
	  the only ones written)

	o tarring large files (esp. large tar.Z files) results in an
	  end of tape not found error

	o accessing floppies during tar operation results in errors
	  in the floppy operation

Tar has no problem reading from the unit - even sizable files written
from another system to tape. And the files it does write to tape are
reliable and hold their integrity.

Any ideas/suggestions? While I'm on the podium, how about plans for
EISA support eventually?;-)

>  -Dan


.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
.  Jamie Saker					jsaker@cwis.unomaha.edu    .
.  Network Costing Analyst			Business/MIS Major	   .
.  Telenational Communications			Univ. Nebraska at Omaha	   .
.  (402) 392-7548							   .
.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
From: merlin@neuro.usc.edu (merlin)
Newsgroups: comp.unix.bsd
Subject: Re: FORTRAN for 386BSD?
Date: 13 Aug 92 08:05:27 GMT
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: neuro.usc.edu

>Is there a Fortran compiler available for 386BSD?  Where would I get it?
>Is it free?

YES --  Anonymous ftp from research.att.com:/netlib/f2c/*  -- YES.

This compiler (well, fortran to c translator and supporting libraries) is
EXCELLENT.  We have used it in our initial porting of several large image
processing systems to 386BSD-0.1.  It has also been the basis of previous
ports of the same packages to Apple's AUX version of UNIX.

I also think there is some poetic justice in using an AT&T Research Group
product to enhance our AT&T source code free 'Berkeley UNIX' installation.
Newsgroups: comp.unix.bsd
From: dmuntz@dip.eecs.umich.edu (Daniel A Muntz)
Subject: Re: 386BSD QIC-02 Driver with Wangtek 5150PK is sloooooow
Organization: University of Michigan EECS Dept., Ann Arbor
Date: Wed, 19 Aug 1992 05:17:45 GMT

In article <1992Aug17.191318.8853@hotb.sub.org> thomas@hotb.sub.org (Thomas Brettinger) writes:
>Hi.
>I got 386BSD running on a noname sx, 4 Meg Ram, a 100M Conner Disk, WD
>Elite and a Wangtek 5150PK QIC-02 Streamer.
>
>The system runs fine, but the tape driver is incredibly slow. I looked
>at the source and saw, that it's using 512 byte blocks... Oh well.

The problem isn't the 512-byte blocks, per se, but that the controller doesn't
receive data quickly enough to allow the drive to stream properly.  You can
get some performance improvement by buffering data in the driver and polling
the controller instead of waiting for interrupts and timeouts.  Perhaps
someone could comment on why so many interrupts seem to get lost.  I've
hacked wt.c to do buffering and polling to make the qic-02 drives usable, but
this isn't really the "right" solution.  A couple of thoughts:

  Track down why interrupts are being lost so the driver can by purely
  interrupt driven (I'm not sure this would help).  It seems that the
  drive streams properly when interrupts are received, but loses it when
  it frequently has to fall back on the timeout to make up for lost interrupts.

  Rewrite the driver and part of subr_vnops.c (I think) to allow the driver
  to pull data bufs down instead of waiting for requests to read/write.
  This along with polling should allow the drive to stream.

I'm sporadically working on these things and would appreciate any feedback.

  -Dan
From: martelli@cadlab.sublink.org (Alex Martelli)
Newsgroups: comp.unix.bsd
Subject: Unigram-X (was Re: UNIGRAM's article on the USL-BSDI suit)
Date: 11 Aug 92 15:01:06 GMT
Organization: CAD.LAB S.p.A., Bologna, Italia

jds@cs.umd.edu (James da Silva) writes:
	...
:By the way, does anyone have any information on who these UNIGRAM-X people
:are anyway?  Is this a real newspaper or newsletter?  Who owns them, and
:who is their intended audience?  It was so badly written that I would have

Yes, it's a real newsletter, and we have been subscribing to it for
years (it's pretty costly, as most newsletters are).  "Intended
audience" is presumably people trying to make business decisions
depending on the vagaries of the UNIX(R) and similar markets, more
specifically in Europe (Unigram-X is published in the UK).  So, a
software house trying to decide which platforms to target with which
products, which strategic directions to invest in, and so on, is a
part of what I presume this "intended audience" is; so would be
consultants or other professionals, other kind of firms buying and
selling in this market, and so on.

:thought it a joke in other circumstances.  "drug-happy hippy-freak Unix
:culture", indeed!  "naive tech-weenies", indeed!  Are the authors brave
:enough to show their faces here and admit to writing this piece of trash,
:or are they just going to continue lurking about?

The *average* level of Unigram-X articles is better than this, IMHO,
although, as most newsletter do, rather frequently some of their wild
rumor-based speculation turns out to have no basis in reality.  Still,
I believe that, over the years, our subscription to it has paid for
itself as an investment, so although I'm VERY tempted to cancel it
in pique over this idiotical piece, I think I'll keep my cool instead,
and keep the subscription, as being in the best interest of my firm.

-- 
Email: martelli@cadlab.sublink.org                   Phone: ++39 (51) 6130360
CAD.LAB s.p.a., v. Ronzani 7/29, Casalecchio, Italia   Fax: ++39 (51) 6130294 
Newsgroups: comp.unix.bsd
From: dwa@ossi.com (David W. Abbott)
Subject: Re: Problem with WD8003-Card in BSD386
Organization: Open Systems Solutions Inc.
Date: Wed, 12 Aug 1992 16:13:55 GMT

peter@panther.cosy.sbg.ac.at (Peter Burgstaller) writes:

>I can't set the jumpers on my ethernet-card to irq 2, the only settings
>my card accepts is irq 3 or irq 5.

>Is there anyway to solve this problem ??

>H E L P !!!

Is your COM2 port IRQ 2 ? Try disabling it and having another go.


--
David Abbott, Open Systems Solutions Inc.
6121 Hollis Street, Emeryville, CA 94608-2092
phone: (510) 652 6200 ext. 137   fax: (510) 652 5532
dwa@ossi.com     {...,ucbvax,uunet}!ossi!dwa
Newsgroups: comp.unix.bsd
From: scm@aiware.in-berlin.de (Harald Schmidt)
Subject: Search for BSD books
Summary: bsd
Keywords: books
Organization: AIware
Date: Thu, 13 Aug 1992 23:22:33 GMT

Hallihallo,

I would like to start working with 386BSD, but there are
no books like these from UNIX System V3.2, no programming mans,
no reference mans and no admin books.

Does anybody knowns where I can buy those books?

Thnaks in advance,

	Harald
-- 
User:		Harald Schmidt
E-Mail:		scm@aiware.in-berlin.de
Voice:		Berlin - 815 59 75
Data:		Berlin - 815 75 90 (nuucp/nuucp)
Newsgroups: comp.unix.bsd
From: peter@panther.cosy.sbg.ac.at (Peter Burgstaller)
Subject: Problem with WD8003-Card in BSD386
Organization: University of Salzburg
Date: Wed, 12 Aug 1992 15:09:41 GMT

I can't set the jumpers on my ethernet-card to irq 2, the only settings
my card accepts is irq 3 or irq 5.

Is there anyway to solve this problem ??

H E L P !!!

--
/------------------------------------------------------------------------- 
------\
| Peter Burgstaller		| Student of Computerscience		 
	|
| (peter@cosy.sbg.ac.at)	| in Salzburg, Austria (Europe)		 
	|
| (cd048@freenet-in-a.cwru.edu)	| "So Long, and Thanks for the Fish" (D.  
Adams)	|
\------------------------------------------------------------------------- 
------/
From: guido@gvr.win.tue.nl (Guido van Rooij)
Newsgroups: comp.unix.bsd
Subject: secure NFS
Date: 16 Aug 92 18:34:25 GMT
Organization: Guido's home 486 box

Someone mentioned that a certain James made some patches for the NFS stuff
in 386bsd so that it will only use priviledged ports when doing NFS.
Can someone please mail me those patches?

-Guido
-- 
Guido van Rooij            /        internet: guido@gvr.win.tue.nl
Bisschopsmolen 16          \        phone: ++31-40461433
5612 DS Eindhoven          /
The Netherlands            \
From: mengel@dcdmwm.fnal.gov (Marc W. Mengel)
Newsgroups: comp.unix.bsd
Subject: Re: : searching for Usenix conferences
Date: 14 Aug 92 21:07:21 GMT

Of course, you can join USENIX, and get printed copies of USENIX conference
proceedings for cheap...


-------
Marc Mengel
mengel@fnal.fnal.gov
From: dj@godot.co.uk (DJ Walker-Morgan)
Newsgroups: comp.unix.bsd
Subject: Re: USL's claims to "intellectual property"
Date: 14 Aug 92 07:50:44 GMT
Reply-To: dj@godot.co.uk
Organization: MicroMuse - The SPARC dudes

In article 18970@telematics.com, ted@telematics.com (Ted Goldblatt) writes:
>(ObDisclaimer: I'm no lawyer, and don't even play one :-))
>All of this does seem to argue against academia and others who are
>interested in free distribution of research and results from getting
>involved with "protected" code, since the "black box" approaches
>used in industry for reverse engineering are probably too expensive
>and provide too little benefit to be worth while.

Hmmm.... Though they could be useful for an academic site setting up a course
on reversed engineering and implementing clean room procedures. B)

>
>ted
>-- 
>Ted Goldblatt    ted@telematics.com     (305) 351-4367
>    Telematics Intl., Inc.   Ft. Lauderdale, FL

---

============================================================================
  dj@micromuse.co.uk    |"In a perfect world we'd all sing in tune
  Voice +44-71-352-7774 | but this is reality so give some room" 
  Fax   +44-71-351-7834 |                           (Sir) William Bragg
------------------------+---------------------------------------------------
 Non-standard Disclaimer : "I didn't do it, it wasn't me, I wasn't there"
From: athos@eyrie.img.com.au (David Burren)
Newsgroups: comp.unix.bsd
Subject: Re: WD Ethernet Card not found on warmboot
Date: 20 Aug 92 13:30:32 GMT
Organization: img Consultants, Melbourne, Australia

In <1992Aug19.165319.14767@doug.cae.wisc.edu> dinda@cae.wisc.edu (Dinda Peter) writes:

>I have 386BSD 0.1 installed on a Gateway 486/33, 170MB partion,
>16MB RAM, Diamond Speedstar card, Western Digital Ethercard PLUS
>Elite16 Combo (8003E compatible).  After some staring at a BSD
>admin handbook, ifconfig, routeing (no demon), named, and sendmail
>are up and running.  I can telnet, ftp, etc without any problems.

>However, this is only that case when the machine is power-cycled.  On
>warmboot initiated via reboot or shutdown -r (or a panic) the WD    
>Ethernet card is not recognized.  The card is correctly configured
>as IRQ2, I/O adx 0x280, Mem base 0xD000 with EASYSET.EXE.  Any thoughts?

I also have an Elite16 Combo (it's the 8013E with AUI, BNC, & UTP) and
see exactly the same symptoms.  No ideas yet, just another "me too!"...

This is in a system that's evolved from a 16 MHz 386SX through a 20 MHz
386DX to a 40 MHz 386DX.  Using a mono display, A1540, floppy, & serial.
The we device has never so far been detected on warm-boot.
___________________________________________________________________________
David Burren					athos@img.com.au
img Consultants					+61 3 634 3635
Newsgroups: comp.unix.bsd