HDTenEightyP/NetNews huggingface dataset:
From: ac116@city.ac.uk (Tarkan)
Subject: [386BSD] Checksums,,How to check them????
Summary: how do you use the Manifest files to check checkums
Keywords: CHECKSUM CHECK
Organization: The City University
Distribution: comp
Date: 26 Jan 93 10:33:32 GMT


Can anyone tell me how i can check the checksums are correct
with the 386BSD distrubution i have ftp'd using the Manifest
files,,,I tried using dcksum < MANIFEST 
but that says cant find sum or something...
I'm using a Sparc running SunOS 4.1.3.

PS..Can anyone also tell me what Julians Stuff is and what it
does,,and is it useful,,and where can i get them from.????




-- 
************************************************
* if you haven't guessed yet...                *
*  Tarkan....             at: ac116@city.ac.uk *
********************************auto*signature**
Newsgroups: comp.unix.bsd
From: zh@nike.rz.uni-konstanz.de (Z. Horvat)
Subject: Inst prob: bad sector table corrupted
Reply-To: zh@nike.rz.uni-konstanz.de
Organization: RZ Universitaet Konstanz
Date: Thu, 28 Jan 1993 11:54:28 GMT

I have an Compaq 386 which i would like to see 386bsd running.
Booting from the (new, patches applied) floppy disk works,
but after install has completed the machine pops out the
following message during the boot off the hard drive :

wd0: error in bad sector file

shortly after (messages about probed devices appear) the machine reboots
with a message which disappears much to fast to be read.

Is the compaq the problem or the corrupted bad sector table ?

Any hints appreciated.


---

---------------------------------------------------
SYS337654 Could not locate coffee - Operator halted 
---------------------------------------------------

Z. Horvat
Rechenzentrum Universitaet Konstanz
++49-7531-88-2405

zh@nike.rz.uni-konstanz.de
rzhorv@nyx.uni-konstanz.de
From: captain@rot.qc.ca (Andrew Webster)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Problem with WD8013 card!
Summary: Problem with WD8013 and 386BSD
Keywords: 386BSD ethernet 8013 problem bug
Date: 22 Jan 93 04:24:15 GMT
Organization: Groupe de Recherche Operationnelle en Telecommunication (ROT) Inc.
X-Newsreader: TIN [version 1.1 PL6]

Hi...

This may be old hat, but here goes...

Just a little backgroud:
I'm tring to get 386BSD to talk to my ISC3.0 box but so far only slip works!

I just recently aquired 386BSD, and have been installing it.  The documentation
mentions that it supports western digital (SMC) network cards.  I have such
a beast, and 386BSD does indeed detect the card upon boot-up.  However
after configuring it with:
ifconfig we0 192.1.1.2 netmask 255.255.255.0 broadcast 192.1.1.255
and: route add default 192.1.1.1 
ping 192.1.1.1 does nothing (NADA) the activity lights on the card don't
even flash.  Going the other way (ISC3.0->386BSD ping makes the RX light
flash on the card but it seems to be ignoring the packets.)

I noticed however that when I set a new address with ifconfig a packet is
transmitted (lights flash and packet count goes up on ISC machine.)

I've tried with Tarry's new distribution tiny bsd and that didn't help either.
Any comments / sugestions?

-------------------------------------------------------------------------------
captain@broue.rot.qc.ca	| Andrew Webster	|  "The engines canna take it 
			|			|  anymore cap'n..."
IP: 192.77.49.131	| ROT inc.		 ------------------------------
			| Recherche Operationnelle en Telecommunication
			|
Voice: +1 514 737 0020	| Dataradio Inc.
Fax:   +1 514 737 7883	| Montreal, Quebec
-------------------------------------------------------------------------------
From: prang@du9ds4.fb9dv.uni-duisburg.de (Juergen Prang)
Newsgroups: comp.unix.bsd
Subject: HD with >1023 cyl. for DOS+386BSD without translation mode ?
Date: 28 Jan 1993 00:24:45 GMT
Organization: Universitaet Duisburg GH
NNTP-Posting-Host: du9ds4.fb9dv.uni-duisburg.de
X-Newsreader: TIN [version 1.1 PL8]

Hi,
I'm using a Conner CP3544 IDE HD (543.7MB, 12 heads, 1806 cyl, 49 sect.)
for both DOS (200MB, 1st partition) and 386BSD (2nd partition). Because
I didn't know anything better, I setup the drive type 47 with 1023 cyl.,
16 heads and 63 sectors (DOS maximum) with my AMI BIOS (dated 7/7/91),
thereby loosing some 10 MB and running the drive in translation mode
(some problems known with 386BSD). The drive was partitioned with DR-DOS's
fdisk.

The following questions arise:
Is it possible to setup the drive with its real parameters to circumvent
  translation mode and giving 386BSD the whole rest of the drive ?
Will BIOS/DOS (and soon OS/2) function properly with these parameters on
  its 200MB partition ?
Will I have to setup some parameters differently than given above ?
Are any other important things worth to be considered (possible potential
problems with DOS/OS2/386BSD etc.) ?

If these are FAQs, please point me to an archive for the answers.
--
   Juergen Prang           |     prang@du9ds4.fb9dv.uni-duisburg.de
   University of Duisburg  | 
   Electrical Engineering  |       (intentionally left blank)
   Dept. of Dataprocessing |          (no cookie available)
From: rommel@jonas.gold.sub.org (Kai Uwe Rommel)
Newsgroups: comp.unix.bsd
Subject: Re: please help with SCSI tape and 386BSD!
Date: 23 Jan 93 16:22:49 GMT
Organization: Private

In article <727481242rommel.root@jonas.gold.sub.org> rommel@jonas.gold.sub.org (Kai Uwe Rommel) writes:
>I have a SCSI tape drive (Tandberg 4120) and want to read 386BSD from
>it after installing the boot disk, which worked fine. I can prepare a
>tape with 386BSD under OS/2 but cannot read it under 386BSD. In fact,
>386BSD cannot read *anything* from the tape.
>
>I have already replaced the kernel with one from the net with the new
>SCSI drivers but it still can't read the tape (although it prints out
>less error messages than the shipped kernel). I have made the new
>devices names/minors and have no problems with the hard disk and
>cd-rom devices.
>
>However, when I try to access the tape (even with cat, not only with
>tar), it streams a bit and when using "tar tv" I see one line with the
>contents of the first record (correct, BTW) and then I only get the
>message "length error". What is wrong here and what can I do?
>
>Does anyone have a working kernel with SCSI drivers which work with
>the Tandberg streamer so that I could FTP the kernel (and diffs to be
>able to eventually recompile the kernel afterwards)?
..
>Please send mail with suggestions.

[no response so far]

Update: I have today tried a HP 35470A DAT drive and to my surprise it
works. It is a SCSI-2 device like the Tandberg streamer but unlike the
Tandberg it works fine. I suspect that they respond a bit differently
to SCSI commands. 

Does anyone know the fix for 386BSD to get the Tandberg working? BTW,
both the Tandberg and the HP DAT work fine under OS/2, so it's not a
fault in the hardware.

Kai Uwe Rommel

--
/* Kai Uwe Rommel                                      Muenchen, Germany *
 * rommel@jonas.gold.sub.org                       Phone +49 89 723 4101 *
 * rommel@informatik.tu-muenchen.de                  Fax +49 89 723 7889 */

DOS ... is still a real mode only non-reentrant interrupt
handler, and always will be.                -Russell Williams
Newsgroups: comp.unix.bsd
From: hlu@eecs.wsu.edu (H.J. Lu)
Subject: Re: [386BSD] gcc2 and -fPIC
Organization: School of EECS, Washington State University
Date: Wed, 27 Jan 93 04:46:27 GMT

In article <1993Jan27.002600.21136@jpl-devvax.jpl.nasa.gov>, kaleb@jpl-devvax.jpl.nasa.gov (Kaleb Keithley) writes:
|> In article <1993Jan26.210430.27806@serval.net.wsu.edu> hlu@eecs.wsu.edu (H.J. Lu) writes:
|> >In article <CGD.93Jan25211237@eden.CS.Berkeley.EDU>, cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes:
|> >|> anybody gotten code compiled w/gcc2's -fPIC to assemble properly
|> >|> (or "at all") under 386bsd?
|> >|> 
|> >That is because as on bsd doesn't support PIC yet. That leads to another
|> >question. I believe a.out format is not very good for PIC even with some
|> >patches. Personally, I prefer ELF. The problem is gnu binutils 2.x and
|> >gas do not fully support ELF. I was wondering if anyone has done something
|> >on ELF?
|> 
|> Huh?  a.out and PIC work pretty good on Sun.  I always understood the
|> difference between PIC and non-PIC was the use of relative addressing
|> versus "hard" addressing.  I'm sure the assembler is more than capable
|> of handling relative offsets if the compiler generates them correctly.
|> 

Not even SUN uses that a.out format anymore. ELF is the way to go.

|> Gcc doesn't grok PIC on any 386 machine, period, e.g. Sun 386i -- at

You haven't try -fPIC -O on libg++-2.3 yet.

|> least that's what I was told when I asked gnu.gcc.help.  There are patches 
|> out there to make gcc generate PIC on 386.  One author of such patches told 
|> me that Stallman didn't like them because they broke other things, or didn't 
|> fit the gcc conceptual design or some other blather...
|> 
|> Anyway, ask around on gnu.gcc.help -- the patches are out there!

Those patches are for psudo PIC for SVR3. I don't care SVR3. I want ELF.

|> 
|> BTW, you probably already know this, but I'll mention it for what it's
|> worth.  99&44/100% of all things compiled with PIC go into shared 
|> "libraries".  Getting things compiled/assembled with PIC is only half the 
|> battle.  Then you have to modify 'ld' to create the library with the PIC 
|> objects.  At least you'll want to handle the pure-text assertion.
|> 
|> -- 
|> 
|> Kaleb Keithley                               kaleb@jpl-devvax.jpl.nasa.gov


That is precisely why I want PIC. I'like to see PIC/ELF be used in 386bsd
and Linux.


H.J.
From: vax@ccwf.cc.utexas.edu (Vax)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Elm anyone?
Date: 26 Jan 1993 01:39:35 GMT
Organization: The University of Texas at Austin, Austin TX
NNTP-Posting-Host: sylvester.cc.utexas.edu
Summary: I ported elm.

Is anyone interested in me posting a compiled elm-2.3 somewhere handy?
(FTP, not really -posting-, anyway)

It didn't take alot of modification, but it took some.. and the configure
script is probably a pain for mail-neophytes like me.  I don't know where
to put it, or if it requires enough "work" to make it worth the space it
takes on a 386bsd site.  Opinions?
-- 
Protect our endangered bandwidth - reply by email.  NO BIG SIGS!
VaX#n8 vax@ccwf.cc.utexas.edu - finger for more info if you even care.
From: cjb@cs.uq.oz.au (Christopher J Biggs)
Newsgroups: comp.unix.bsd
Subject: [386bsd] anyone got that Hard-disk chaser circuit?
Date: 22 Jan 93 10:47:12 GMT
Organization: Computer Science Department, The University of Queensland,
	Brisbane, Australia


   Some time ago, someone posted a circuit idea and kernel patch for 386bsd
that utilized a parallel port to drive an LED chaser circuit as an upmarket
disk-activity monitor.  I carefully filed that article against the day I
would acquire a spare parallel port.

Needless to say, now that I have a free paralell port, I can't find the
article.  Does anyone have the circuit diagram and code that they could
mail to me or repost?
			Ta,
				Chris.

--
 Christopher J Biggs   cjb@cs.uq.oz.au   | "You can have peace.  Or you can  
 Department of Computer Science,         | have freedom.  Don't ever count on 
 The University of Queensland, Australia | having both at once."--Lazarus Long 
------------veni vidi nuclei deceiri - I came, I saw, I dumped core------------
Newsgroups: comp.unix.bsd
From: dwex@cbnewsj.cb.att.com (david.e.wexelblat)
Subject: Re: [386BSD] gcc2 and -fPIC
Organization: AT&T
Date: Wed, 27 Jan 1993 19:36:44 GMT

In article <1993Jan27.172321.14231@jpl-devvax.jpl.nasa.gov> kaleb@jpl-devvax.jpl.nasa.gov (Kaleb Keithley) writes:
> 
> >|> Gcc doesn't grok PIC on any 386 machine, period, e.g. Sun 386i -- at
> >
> >You haven't try -fPIC -O on libg++-2.3 yet.
> >
> >|> least that's what I was told when I asked gnu.gcc.help.  There are patches 
> >|> out there to make gcc generate PIC on 386.
> >
> >Those patches are for psudo PIC for SVR3. I don't care SVR3. I want ELF.
> 
> Actually the patches I'm referring to are for SunOS on Sun386i, which
> is actually COFF.  At the risk of repeating myself, gcc itself doesn't
> yet support PIC on any 386, irrespective of anything else.
> 

Hmm.  That's odd.  I've been building X11R5 shared libraries on Microport
SVR4 on an i486 box for about a year, using 'gcc -fPIC'.  Works very well,
thank you.  GCC DOES support PIC on a 386, if your OS supports it.

> 
> -- 
> 
> Kaleb Keithley                               kaleb@jpl-devvax.jpl.nasa.gov
> 

--
David Wexelblat <dwex@mtgzfs3.att.com>  (908) 957-5871
AT&T Bell Laboratories, 200 Laurel Ave - 3F-428, Middletown, NJ  07748

"The meaning of life?  That's simple.  Try to be happy, try not to hurt
 other people, and hope to fall in love."  -- Mallory Keaton
From: mel1@soc8.acpub.duke.edu (Douglas Melamed)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Just a quick question or two
Date: 28 Jan 93 18:26:02 GMT
Reply-To: mel1@soc8.acpub.duke.edu (Douglas Melamed)
Distribution: usa



I recently set up the distribution and noticed that there where
numerous patches to the src out there (ie patch-kit-2), many of these
patches seems to cause problems in the process of fixing others. So what I'd
really like to know is if someone is working on the next distribution (ie 
putting all the patches together cleanly and making sure they work).

Is 386BSD0.2 going to be released anytime soon, or do I have to go through the
trouble of patching and hacking the code. I'd really just like a working
operating system without having to go though the trouble of messing with the
source code. Is there another publicly available unix operating system that
is more stable? Please email me responses, I'd appreciate any information you
can give me.

-Doug
Newsgroups: comp.unix.bsd
From: ramzi@rintintin.Colorado.EDU (Ramzi Al-Majid)
Subject: BSD where ?
Organization: University of Colorado, Boulder
Date: Sat, 23 Jan 1993 01:58:51 GMT


where can one get the BSD system from and how ? how much does it cost ?
does it run on 486 PCs ?

thanks

-- 
Computer Science Department	arpanet : ramzi@cs.colorado.edu
Univ. of Colorado - Boulder	bitnet  : ramzi@boulder.bitnet
Campus Box # 430		csnet   : ramzi@boulder.csnet
Boulder, Co 80309-430		uucp    : {ncar|nbires}!boulder!ramzi
From: peter@micromuse.co.uk (Peter Galbavy)
Newsgroups: comp.unix.bsd
Subject: Re: Cannot nfs export cdrom directory...HELP!!
Date: 21 Jan 93 17:26:56 GMT
Reply-To: peter@micromuse.co.uk
Organization: MicroMuse Ltd, London

In article 17336@netcom.com, jagane@netcom.com (Jagane D Sundar) writes:
> 
> 
> 	I am unable to nfs access a cdrom drive mounted on a 386bsd system 
> 	using nfs. 
> 
> 	My commands,
> 
> 		mount -t isofs /dev/as4d /cdrom.
> 
> 		/etc/exports contains /cdrom.
> 
> 		I am able to mount the /cdrom drive on a different 
> 		machine using nfs.  However, the directory
> 		is empty and ls shows nothing.

Right, I haven't tried this, but it sounds like the same as with SunOS...

You have to "re-export" the /cdrom directory, after mounting it. On 386BSD I think
you do this my sending a HUP signal to the mountd proess. This causes mountd to
reread the /etc/exports file.

Please try it, but I haven't got a CDROM drive on the PC (yet).


---
Peter Galbavy
Tech Support, Micromuse Ltd
Phone: +44 71 352 7774		E-Mail: P.Galbavy@micromuse.co.uk
Newsgroups: comp.unix.bsd
From: tdbear@dvorak.amd.com (Thomas D. Barrett)
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
Subject: Re: Vesa Local Bus and Companies (please read)
Date: 27 Jan 93 19:13:30 GMT
Organization: Advanced Micro Devices, Inc.; Austin, Texas

In article <1993Jan27.050642.15880@wam.umd.edu> tictac@wam.umd.edu (Shake it to the Left) writes:
>Then WHY does [deleted] sell 486/DX50's claming to have
>3 VLB slots in them? 

Although they may have a true 50MHz CPU, they might operate the rest
of the system at 25MHz.  You will have to ask them what the clock rate
is on the vl-bus.

The rules are that only certified VL-Bus systems have a special VESA
VL-Bus compliance label.  The compliance testing requirements are just
being finalized and will soon be off to the mags and the various
compliance labs.  If a company is not on the committee, then they will
most likely have to be certified by an independent lab.  Those on the
committee *might* be permitted to self-certify.

Only 33MHz and less systems can have 3 physical slots.  Right off the
bat these are in violation UNLESS they are buffered (probably not).

I was amazed that some companies are offering so-called VL-Bus
compatible machines with well over 200pF of UNLOADED capacitance on
the Bus.  These companies generally just take a chip vendor's demo
platform and stamp out massive units.  Unfortunately, these demo
platforms typically do not conform to any intelligent design
parameters.  One that I looked at recently (the over 200pF one) had
the two banks of SRAM, the 8 SIMM modules, and the 3 local bus slots
all on the motherboard.  The SRAM and DRAM alone put the recommeded
bus capacitance at the limit.  Naturally, adding buffers to the DRAM
would have required an extra waitstate or faster DRAM.  But, if I had
such a system that would be a whole lots better than having parity
errors (assuming you have parity).

-- 
|Tom Barrett (TDBear), Sr. Engineer|tom.barrett@amd.com|v:512-462-6856 |
|AMD PCD MS-520 | 5900 E. Ben White|Austin, TX  78741  |f:512-462-5155 |
|"No is yes, And we're all free" ---Tracy Chapman, "Why?"              |
|My views are my own and may not be the same as the company of origin  |
From: vax@ccwf.cc.utexas.edu (Vax)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Do I need a swap partition?
Date: 21 Jan 1993 12:32:03 GMT
Organization: The University of Texas at Austin, Austin TX
Distribution: comp
NNTP-Posting-Host: sylvester.cc.utexas.edu
Keywords: bsd swap partition swapon disklabel low-level frustration

Do I need a dedicated swap partition for BSD use?  I have 8 MB RAM and
plenty of HD space.

How do I partition and initialize a partition so that 386BSD will recognize
it?  BSD appears to read the disklabel stuff which must refer to a parallel
dimension in which I have three overlapping partitions; or, it is wrong.
Why is my disklabel confused, and how do I fix it?

Also, if you mess up your disk label, like I did once, how do you fix it
without a low level format and a reinstall (like I did)?
I lost everything since I installed crypt and now I know I shouldn't have
touched it;when it booted, it couldn't find any kernel file.  fsck reported
an unallocated root inode, and then asked me if I wanted to clear hundreds
of files, one by tedious one.  So I formatted it.

-- 
Protect our endangered bandwidth - reply by email.  NO BIG SIGS!
VaX#n8 vax@ccwf.cc.utexas.edu - finger for more info if you even care.
From: vazquez@iqm.unicamp.br (Pedro A.M. Vazquez)
Newsgroups: comp.unix.bsd
Subject: [386BSD] panic: npxintr
Date: 21 Jan 1993 18:02:27 -0600
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu

Helo:
	Is there a patch to avoid "npxtint: panic" ? It's ocurring when
I run somewhat big fortran applications and redirect stdout to a file. If
I use some system commands (ls -lR, ps aux) it will eventualy crash the
system (I'm unable the whole message, the screen clears :)
	If I run the same application without redirecting stdout or from
a xterm I've no problems.
	I'm using the kernel from XFree package in a 386/IIT387 40MHz with
* M ram.

	Thanks in advance

	Pedro

PS: please reply direct to me as I don't have very good access to news, I'll
sumarize.

=============================================================================
Pedro A. M. Vazquez | Depto de Fisico Quimica | Instituto de Quimica
Universidade Estadual de Campinas | Fone : 39-7253 | Fax : 39-3805 | Brasil
=============================================================================
chemist: [Cambridge] n. Someone who wastes computer time on number-crunching 
when you'd far rather the machine were doing something more productive, such 
as working out anagrams of your name or printing Snoopy calendars or running 
life patterns. May or may not refer to someone who actually studies chemistry.
						Jargon File v2.9.6
=============================================================================
From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su>
Newsgroups: comp.unix.bsd
Subject: [386bsd] New patch00071 is slightly wrong
Date: Wed, 27 Jan 93 15:50:34 +0300
Distribution: world
Organization: Ha-oh-lahm Yetzirah
Reply-To: ache@astral.msk.su

I just look into new patch00071 of clock.c and found small bug,
it don't calculate leap year properly, produce error in 2000 year.

! 	if (sec < 1970)
! 		sec += 100;
! 	leap = !(sec % 4); sec = ytos(sec); /* year    */

Correct way to calculate leap year is:

#define isleap(y) (((y) % 4) == 0 && ((y) % 100) != 0 || ((y) % 400) == 0)

see for example /usr/include/tzfile.h
-- 
In-This-Life:  Andrew A. Chernov    |  "Hay mas dicha, mas contento
Internet:      ache@astral.msk.su   |  "Que adorar una hermosura
FIDOnet:       2:5020/23.34         |  "Brujuleada entre los lejos
Organization:  The RELCOM Corp.     |  "De lo imposible?!"  (Calderon)
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: [386BSD] gcc2 and -fPIC
Date: 25 Jan 93 21:12:37
Organization: Kernel Hackers 'r' Us
Distribution: world
NNTP-Posting-Host: eden.cs.berkeley.edu

anybody gotten code compiled w/gcc2's -fPIC to assemble properly
(or "at all") under 386bsd?

if so, could you tell me what i'm doing wrong?

gcc -c -fPIC -O foo.c
just won't do it for me... 8-)

later,

chris
--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

"Sometimes it is better to have twenty million instructions by
        Friday than twenty million instructions per second." -- Wes Clark
Xref: sparky comp.unix.bsd:11865 comp.sys.ibm.pc.hardware:37291
From: johng@informix.com (John Galloway)
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
Subject: Re: ATI Mach32 and Xfree86 or XS3?
Date: 27 Jan 93 05:20:56 GMT
Organization: Galloway Research

In article <1993Jan26.220906.26671@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes:
>>
>The ATI Mach32 is based upon ATI's mach32 chipset.
>for speed I suggest acquiring a 928 based card which is faster than the
>ATI MACH32 by as much as 34% overall graphics performace, even on the ISA :-)

Any info on cards that are using the 928 that are available?
>
>Going to a local bus card will not buy you significant performance improvement,
>at least with the S3 chipsets.

Why?  It was my understanding that the local bus was specifically intended
for things like video cards that are twiddling bytes back and forth with the
cpu, as opposed to massive memory transfers.
	-jrg

-- 
internet    jrg@galloway.sj.ca.us  John R. Galloway, Jr  795 Beaver Creek Way
internet    johng@informix.com     CEO...receptionist    San Jose, CA   95133
applelink   D3413                  Galloway Research     (408) 259-2490
Newsgroups: comp.unix.bsd