HDTenEightyP/NetNews huggingface dataset:
From: spider@hercules.kgn.ibm.com (Gregory Scallan)
Subject: Re: Building X11R5
Date: Wed, 06 Jan 93 15:35:38 GMT
Reply-To: spider@hercules.kgn.ibm.com (Gregory Scallan)
Organization: IBM Kingston NY


X11R5 has been available on AIX since 12/18/92.  You will need to obtain the
tape with 3.2.3 extended plus the R5 images.  Instructions are sent with 3.2.3e
on how to install it.

____________________________________________________________
Gregory J. Scallan                       |  IBMnet:     GSCALLAN@KGNVMY
Graphics Systems Technical Center, AWSD  |  Internet:   spider@vnet.ibm.com
(914)385-5054  (T/L 695)                 |  Sneakernet: 203-2-2-2, Kingston
From: larsowe@csd.uu.se (Lars-Owe Ivarsson)
Newsgroups: comp.unix.aix
Subject: Prestoserve
Date: 11 Jan 1993 14:20:37 GMT
Organization: Computing Science Department
Distribution: world
NNTP-Posting-Host: groucho.csd.uu.se
Keywords: I/O, disk

Hello!
      Rumor has it that Legato is working on a Prestoserver for the RS/6000.
I thougt a Prestoserver, as used by Sun and Dec, was a kind of disk-cache.  
As many operating systems--e.g. AIX and IRIX, unlike SunOS and Ultrix--use memory-mapped files, I assumed that the operating system would take care of that (given enough memory at least), making a prestoserver unnecessary on IBM and SGI systems, or at least not cost justified.  Obviously I was wrong on that, so if anybody would please explain the Prestoserve concept for me, especially in combination with the RS/6000, I would be very grateful.  

   /lars-owe  

--
 _________________________________________________________________________
/\                                                                        \
\_\ snailmail: Lars-Owe Ivarsson     | email: lars-owe.ivarsson@udac.uu.se \
  |   UDAC            Haacksby       | phone: work:   018 18 78 41         |
  |   Box 174         S-744 92  HEBY |       home:     0224 930 55         |
  |   751 04  UPPSALA Sweden         |        int:  +46 224 930 55         |
  |   Sweden                         |        fax:    018 51 66 00         |
  | _______________________________________________________________________|_
  \ \    (approximately 1300 kilometers northeast of Brussels)               \
   \/________________________________________________________________________/
From: dpb@air54.air54 (David P. Boerschlein)
Newsgroups: comp.unix.osf.misc
Subject: Motif interface to dbx
Date: 6 Jan 93 08:16:28
Organization: NASA Langley Research Center
NNTP-Posting-Host: air54.larc.nasa.gov


Does anyone know of a Motif interface to the dbx source-level debugger which
will run on SUN OS on a SPARCStation?   I am looking for something like
dbxtool but it has to run under Motif.

--
                                 __________________________
                                |                          |
      ___                       | David Boerschlein        |
      |  \  _     .  _|         | dpb@air16.larc.nasa.gov  |
    (_|__/_(_|_\/_|_(_|         | MS 130    (804) 864-6228 |
                                | NASA LaRC                |
                                | Hampton, VA 23681        |
                                |__________________________|
Newsgroups: comp.unix.osf.misc
From: nhyim@uxmail.ust.hk (Yim Ngok Hon)
Subject: Re: Motif interface to dbx
Organization: Hong Kong University of Science and Technology
Date: Thu, 7 Jan 1993 05:50:18 GMT

You can try xxgdb which is available on the net.

Hon
Newsgroups: comp.unix.osf.osf1
From: henry@geo.ucalgary.ca (Henry Bland)
Subject: amd automounter for Alpha AXP
Date: Thu, 7 Jan 1993 05:38:47 GMT
Organization: Geology & Geophysics, University of Calgary, Canada

Has anyone managed to get "amd" (a replacement for "automount") to
work on DEC Alphas running OSF1 ?

Thanks,
-Henry Bland
Geology & Geophysics Dept
University of Calgary, Canada
Newsgroups: comp.unix.osf.osf1
From: rosenth@vision.ethz.ch (Lukas Rosenthaler)
Subject: TeX /LaTeX on DEC Alpha OSF/1
Summary: TeX / LaTeX on DEC Alpha OSF/1
Keywords: TeX LaTeX on DEC Alpha OSF/1
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Fri, 8 Jan 1993 10:48:37 GMT


Has anyone ported TeX / LaTeX to DEC Alpha OSF/1 ???

Lukas Rosenthaler
rosenth@vision.ethz.ch
From: M.L.Nelson@LaRC.NASA.GOV (Michael L Nelson)
Newsgroups: comp.unix.osf.osf1
Subject: OSF/1 - C validation suites
Date: 7 Jan 1993 19:19:18 GMT
Organization: NASA Langley Research Center, Hampton, VA  USA
Distribution: world
NNTP-Posting-Host: sunkj.larc.nasa.gov
Keywords: OSF/1 C validation testing

Hello all,

Here at Langley Research Center, we are expecting the delivery
of a 66 node Paragon in February.  We were wondering if anyone
had any experience with OSF/1 validation.  Specifically, we
would like to know of some validation suites to run on the
operating system and the C compiler (Fortran too, if available).

All suggestions are appreciated.

I will post a summary if there is sufficient interest.

Michael Nelson


Newsgroups: comp.unix.osf.osf1
From: de5@ORNL.GOV (Dave Sill)
Subject: XXX on Alpha OSF/1?
Organization: Oak Ridge National Lab, Oak Ridge, TN
Date: Fri, 8 Jan 1993 13:49:05 GMT

The alpha-osf-managers mailing list discusses the availability of Alpha OSF/1
ports (like amd and TeX).

To subscribe, send a message to majordomo@sws10.ctd.ornl.gov containing
something like:

	subscribe alpha-osf-managers

or

	subscribe alpha-osf-managers local-exploder@mysite.domain

or

	info alpha-osf-managers         (for info on the list)

or
	help                            (for info on majordomo)

-- 
Dave Sill (de5@ornl.gov)                 Computers should work the way beginners
Martin Marietta Energy Systems           expect them to, and one day they will.
Workstation Support                                                -- Ted Nelson
From: M.L.Nelson@LaRC.NASA.GOV (Michael L Nelson)
Newsgroups: comp.unix.osf.osf1
Subject: Re: OSF/1 - C validation suites
Date: 8 Jan 1993 16:43:30 GMT
Organization: NASA Langley Research Center, Hampton, VA  USA
Distribution: world
NNTP-Posting-Host: sunkj.larc.nasa.gov
Keywords: OSF/1 C validation testing

My Mailer was broken over for about 16 hours.  If you tried
to mail me and it bounced, please mail me again.

Thanks.

Michael Nelson
From: clauberg@RRZK (Axel Clauberg)
Newsgroups: comp.unix.osf.osf1
Subject: Re: amd automounter for Alpha AXP
Date: 8 Jan 93 11:18:46
Organization: Regional Computing Center, University of Cologne, Germany
NNTP-Posting-Host: noc.rrz.uni-koeln.de
In-reply-to: henry@geo.ucalgary.ca's message of Thu, 7 Jan 1993 05:38:47 GMT

In article <HENRY.93Jan7003847@tuba.geo.ucalgary.ca> henry@geo.ucalgary.ca (Henry Bland) writes:
>   Has anyone managed to get "amd" (a replacement for "automount") to
>   work on DEC Alphas running OSF1 ?
Yes, I did. Here is a copy of the patches I've sent out to the amd-workers
list on Dec, 28:
From: clauberg (Axel Clauberg)
Date: Mon, 28 Dec 1992 12:54:52 +0100
To: amd-workers@acl.lanl.gov
Subject: amd patches for DEC Alpha OSF/1

Hi,
here are the basic patches to make amd work (at least for me...) on the 
DEC Alpha under DEC OSF/1 (we currently run T1.2-2  (Rev. 5)).
Besides the mount trap, the most important definition is the _SOCKADDR_LEN,
else <sys/socket.h> will give you (unwanted) 4.3 compatibility, this will
break amd's nfs auto mount calls (and wire.c compilation).
I haven't worked on the OSF/1 rfs@rhost syntax problems Mike Kiernan reported
on Nov, 23, as these don't hit us.
The patches are against the 240892 version.

*** /vol/src/share/local/amd240892/Makefile.top	Sun May 31 18:37:20 1992
--- Makefile.top	Mon Dec 28 12:16:25 1992
***************
*** 59,65 ****
  
  OS_SUPPORTED = \
  	acis43 aix3 aux bsd44 concentrix dgux fpx4 hcx \
! 	hlh42 hpux irix3 irix4 next pyrOSx riscix sos3 sos4 \
  	stellix u2_2 u3_0 u4_0 u4_2 umax43 utek utx32 xinu43
  CHECK_OS = \
  	case " ${OS_SUPPORTED} " in *" $${OS} "*) ;; \
--- 59,65 ----
  
  OS_SUPPORTED = \
  	acis43 aix3 aux bsd44 concentrix dgux fpx4 hcx \
! 	hlh42 hpux irix3 irix4 next osf1 pyrOSx riscix sos3 sos4 \
  	stellix u2_2 u3_0 u4_0 u4_2 umax43 utek utx32 xinu43
  CHECK_OS = \
  	case " ${OS_SUPPORTED} " in *" $${OS} "*) ;; \
*** /vol/src/share/local/amd240892/config/os-type	Sun May 31 18:45:41 1992
--- config/os-type	Mon Dec 28 12:07:36 1992
***************
*** 60,65 ****
--- 60,66 ----
  *"Ultrix Worksystem V2."*)	OS=u3_0;;
  *"ULTRIX V4.2"*)		OS=u4_2;;
  *"ULTRIX V4."*)			OS=u4_0;;
+ *"OSF/1"*)			OS=osf1;;
  *"HLH OTS Version 1."*)		OS=hlh42;;
  *"RISC iX release 1."*)		OS=riscix;;
  *"FPX 4."*)			OS=fpx4;;
*** /vol/src/share/local/amd240892/config/os-osf1.h	Sun Feb  9 16:10:15 1992
--- config/os-osf1.h	Mon Dec 28 12:35:20 1992
***************
*** 153,157 ****
--- 153,164 ----
  /*
   * 4.4 has RE support built in
   */
+ #ifndef __alpha
  #undef RE_HDR
  #define RE_HDR <regexp.h>
+ #else
+ #define _SOCKADDR_LEN
+ #define  _BSD 44
+ #define MOUNT_TRAP(type, mnt, flags, mnt_data) \
+         mount(type, mnt->mnt_dir, flags, mnt_data)
+ #endif

Best regards, Axel




--
Axel Clauberg,    Regional Computing Center, University of Cologne
                  Robert-Koch Str. 10, D- 5000 Koeln 41, Germany
                  Phone:    +49 (221) 478-5589
                  FAX:      +49 (221) 478-5590
                  Internet: clauberg@rrz.Uni-Koeln.DE
		  X.400: s=clauberg; ou=rrz; p=uni-koeln; a=dbp; c=de
Newsgroups: comp.unix.osf.osf1
From: speleg@acri.fr (Sharon Peleg)
Subject: Re: OSF/1 - C validation suites
Keywords: OSF/1, MACH, tetsing
Reply-To: speleg@acri.fr
Organization: ACRI
Date: Fri, 8 Jan 1993 08:46:39 GMT

We also plan to test OSF/1 on a new machine and looking for all possible technics
to accomplish this huge task.
So far I came across only 2 known test-suites: the VSX and the VSE.
VSX3/4 are X/Open's XPG3/4 standard testing suites and VSE, coming from OSF, is
a test suite that checks only those parts of the AES that are not in XPG.
These are licensed software and need to be purchased.
Together, they suppose to cover only the AES definition of OSF, not the rest of the 
OSF/1 functionality, like the P-Threads for example.

It seems that a more serious and interesting problem
should be to test the MACH itself. Once OSF/1 is based on MACH 3.0, testing OSF/1
should be split into testing MACH 3.0 and then testing OSF/1 server.
I'm also interested in such a summery. So I add my questions:

1. Is there any public/comercial tools/suites to test MACH?
2. Are there any documents describing MACH testing?
2. Did anybody do code-covergae on MACH? How?

Thanks in advance, Sharon.
------------------------------+--------------------------
      Sharon  Peleg           | Email : speleg@acri.fr
         A.C.R.I              | Voice : +33-72358460
   1, Bd Vivier-Merle         | Fax   : +33-72358410
69443 LYON Cedex 03,  FRANCE  |


Newsgroups: comp.unix,comp.unix.wizzards,comp.unix.os.kernal,misc.jobs.contract
From: KCconsul@world.std.com (Karen Coffman)
Subject: Contract job, agency.
Keywords: UNIX TOOLS GURU.
Organization: The World Public Access UNIX, Brookline, MA
Distribution: ne
Date: Tue, 5 Jan 1993 21:01:11 GMT

Dear UNIX contractor:

I have a contract opening which I am looking to fill.  If you
have the required skills for this or know of someone who does, 
would you please contact me as soon as possible.  A brief 
description is listed below:

     UNIX TOOLS GURU required for a one month contract
     for a highly respected and successful client on
     Rte. 128.  The contractor will develop a tool box
     which will convert custom configuration files from
     one system to another (the host is on a UNIX/SUN 
     workstation.  The rate per hour is open.


Karen N. Coffman
----------------------------------------------------------------
KC Consultants
fax:    (617)235-3327
email:  kcconsul@world.std.com 

Newsgroups: comp.unix.bsd
From: rich@Rice.edu (& Murphey)
Subject: Re: [386bsd] Mtools documentation
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Mon, 11 Jan 1993 06:38:34 GMT

>>>>> In article <C0pwxL.7Ls@watdragon.uwaterloo.ca>, yqian@yoho.uwaterloo.ca (Yuemin Qian~{G.T>Cq~}) writes:

Yuemin> Looking at /usr/local/bin in 386bsd, there are a bounch of tools
Yuemin> such as 'mread', 'mwrite', 'mdir', 'mdel' as those commands in MS-DOS.
Yuemin> I tried some of these commands, they seemed not work for me except the
Yuemin> ones 'mread' and 'utree'.

Some people have reported that simply recompiling the sources in
/usr/src/othersrc/public/mtools-2.0.5/mtools-2.0.5 fixes problems with
mdir, etc.  This is part of the 'etc' distribution.

Yuemin> The directory /usr/local/man is empty. So there are no man pages for
Yuemin> these commands.

Yuemin> Can someone tell me how to use these commands or where to find the
Yuemin> man pages for these commands?

They are in /usr/src/othersrc/public/mtools-2.0.5/man/cat1.  Rich

Yuemin> Thanks in advance.

Yuemin> -Yuemin
From: greg@coombs.anu.edu.au (Greg Price)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Anyone running ephem under 386BSD?
Date: 10 Jan 93 20:44:20 GMT
Organization: Australian National University
NNTP-Posting-Host: 150.203.76.2
Keywords: ephem 386bsd

Hi there, has anyone compiled up and tried to run any version of the
ephem program (astro stuff)? I have tried a couple of versions, but
it fails miserably with math types errors which I am just starting
to chase. If anyone has tried, or suceeded, drop me some mail.

Thanks,
Greg
(greg@coombs.anu.edu.au)
From: hasty@netcom.com (Amancio Hasty Jr)
Newsgroups: comp.unix.bsd
Subject: Re: kern_execve.c (patch)
Keywords: patch kern_execve.c #!
Date: 12 Jan 93 03:36:03 GMT
Organization: Netcom Online Communications Services (408-241-9760 login: guest)


could you make your version of kern_execve.c available somewhere like over
at ref or your favorite ftp site :-)

Tnks,
-- 
This message brought to you by the letters X and S and the number 3
Amancio Hasty           |  
Home: (415) 495-3046    |  ftp-site depository of all my work:
e-mail hasty@netcom.com	|  sunvis.rtpnc.epa.gov:/pub/386bsd/incoming
Newsgroups: comp.unix.bsd
From: christia@latenite.ssc.gov (Mike Christiansen)
Subject: Re: 386BSD.EXE - Let DOS handle booting?
Organization: SSC Laboratory, Dallas, TX
Date: Tue, 12 Jan 1993 23:56:29 GMT


> This is what Plan 9 does. I was at first repelled and disgusted, but on
> reflection it sounds like a really nice idea. It would resolve the Compaq
> boot problem, it would resolve the problem of video boards that require
> magic DOS configuration programs, it would resolve the "how do I boot
> 386BSD on a second controller" problem, and so on.

> Plus, it'd make it easier to hack around with the boot sequence. You could
> build a new boot program without worrying about making your system non-
> bootable. You could give it arguments
> 
> 	bootbsd boot-options where init-options
> 
> 	bootbsd as1a:386bsd.old
> 	bootbsd -large wd0a
> 	bootbsd -debug fd0a
> 


A DOS bootstrap application would be great, but beyond my capabilites
right now. I just posted a question about how to get BSD to boot when
installed on a SCSI controller, but still maintain my DOS partion on
a MFM disk (I need to keep both disk controllers in the system). I
still haven't determined how to get BSD to boot from the aha scsi
controller with out removing or otherwise disabling the MFM
controller.

I understand if some of you are replused by the though of having to go
through DOS to load BSD. If you dont need DOS on your system, then
remove it and forget about it. (I wish I could!) But for some of us
Windows and other DOS applications are needed for us to do our jobs,
etc. and cant live without it. 
--
----------------------

Mike Christiansen
Superconducting Super Collider Laboratory
Controls Group
2550 Beckleymeade Ave.
MS.4002
Dallas, TX. 75237

214-708-3415
christia@latenite.ssc.gov
Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: [386bsd] f2c with record/structure sup
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Mon, 11 Jan 93 23:04:14 GMT

In article 1545@fcom.cc.utah.edu, terry@cs.weber.edu (A Wizard of Earth C) writes:
>In article <1993Jan10.211632.3269@ll.mit.edu> pope@ll.mit.edu (Frank Pope) writes:
>>Hi
>>
>>Does anyone out there know of a f2c translator which has been ported to
>>386bsd that has support for fortran records and structures.  I believe
>>these are features found in FORTRAN 90 [not sure].  I want to
>>convert some software written using MS Fortran 5.1 to c and run it 
>>under 386bsd.  Thanks in advance.
>
>I don't know of many compilers, let alone translators, which support '90.
>
>Historically, the ANSI-90 FORTRAN was rejected by most major vendors,
>either due to a lack of backward compatability or conflicts with vendor
>extensions (depending on the vendor); it was rejected by Harris, DEC,
>HP, and IBM... dunno if Sun was involved at all.

IBM defected from the Luddite faction as early as May 1989.  I believe that
HP were long-time supporters of Fortran 90 as were Sun.  Incidentally,
Fortran 90 *is* backwards compatible with FORTRAN 77 but does not include
some vendors extensions.  User defined types have a syntax that differs
from the VMS Fortran style adopted my Microsoft.

	Chris Flatters
	cflatter@nrao.edu
Newsgroups: comp.unix.bsd
From: zh@nike.rz.uni-konstanz.de (Z. Horvat)
Subject: Re: [386BSD] Anybody try to use OS/2 Boot Mana
Reply-To: zh@nike.rz.uni-konstanz.de
Organization: "RZ Universitaet Konstanz"
Date: Tue, 12 Jan 1993 19:02:29 GMT

In article 1iup0gINN8hd@darkstar.UCSC.EDU, david@maxwell.ucsc.edu (David Darknell) writes:
>I have been trying to get the OS/2 boot manager to select 386BSD,
>but BSD reboots the computer, re-invoking boot manager.  Any way 
>around this, or is boot manager not compatible with 386BSD?
>
>David
>

Use OS/2's FDISK to make the 386BSD partiotion the default partition. 
Define a timeout at your own taste.
This should automatically load 386BSD after a reboot.
(No, i dont't have a system with both 386BSD and OS/2 installed, but this is the
way how it should work)

---

---------------------------------------------------
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


Newsgroups: comp.unix.bsd
From: ljg@space.physics.uiowa.edu (Larry Granroth)
Subject: [386BSD] more than 16MB?
Organization: The University of Iowa, Department of Physics and Astronomy
X-Newsreader: TIN [version 1.1 PL8]
Date: Tue, 5 Jan 1993 21:48:34 GMT

I Didn't find this in the FAQ:

Is anyone out there running 386bsd on an ISA-bus machine with more than
16MB ram?  Does 386bsd support this?  Does it (does it need to?) support
DMA above 16MB?

Thanks for any info.  I'll summarize if appropriate/useful.

larry-granroth@uiowa.edu
From: veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: codrv problems..
Date: 7 Jan 93 17:40:12 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.fb9dv.uni-duisburg.de
NNTP-Posting-Host: du9ds3.fb9dv.uni-duisburg.de
Keywords: 386BSD, codrv

In <1993Jan6.184438.5175@lgc.com> danson@lgc.com (Doug Anson) writes:

>HI:

>I tried installing the latest codrv package (keycap-0.1.1.tar.Z). I ran into
>several problems with /sys/i386/i386/conf.c. I _REMOVED_ the pc0 interface
>definition from my config file and installed the co0 interface as told by the
>instructions. As a result, I got an unresolved error in /sys/i386/i386/conf.c
>(pcmmap to be specific) when compiling the kernel. 

Ah, you at least didn't read all the instructions. The "missing" comap,
for instance, is one of the documentation bugs found after everyone already 
had a working version ;-). There is a file BUGLIST.151292 which should be in 
the same directory where you found keycap-0.1.1 which lists bugs and corrections
for this version. Some of the corrections may be already corrected in
the distribution you have. Also, the documentation does not explicitly
state that there are some diffs which should also be applied (see below).

>Well, I decided to ifdef the pccons stuff (i.e. if NPC > 0 ...) as is done with
>other drivers in conf.c. I managed to get the kernel recompiled successfully.
>However, In addition, I made the /dev/vga and /dev/kbd as instructed with the
>correct major device numbers coresponding to conf.c. However, my kernel now
>reboots continuously on a syscall panic.

There is a sample file conf.c which gives a hint how your configuration
should look like. In particular take a look at the "co" device, which 
is in slot 15. The major numbers given in the documentation (15/0 and 15/128)
assume that your conf.c has the co device in the same slot.

>I have the 386BSD 0.1 kernel with 1-58 patches applied + pcfs.

In this case, you do not need the tty.h.diff.
But kbd.h.diff, cons.diff, and tty_pty.h.dif are still necessary.

>Any help would be appreciated.
>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			
>-------------------------------------------

Contact me for further questions (and some special offer!) at my
email address veit@du9ds3.fb9dv.uni-duisburg.de.

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.fb9dv.uni-duisburg.de
|__|  /  University of Duisburg  |
|  | /   Dept. of Electr. Eng.   |          "Understand me correctly:
|  |/    Inst. f. Dataprocessing |     I'm NOT the WIZARD OF OS" (Holger)
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: Where can I pick up the FAQ from?
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Date: Tue, 12 Jan 1993 01:44:39 GMT

You might find the FAQ and BUGLIST (really an FAQ) on agate:
anon ftp agate.berkeley.edu; ~/pub/386BSD/386bsd-0.1/unofficial/{*FAQ,*BUGLIST}
Newsgroups: comp.unix.bsd
From: msw@world.std.com (Mark S Warren)
Subject: Re: [386BSD] scsi tape problem
Organization: The World @ Software Tool & Die
Date: Tue, 12 Jan 1993 15:08:06 GMT

dgd@kcbbs.gen.nz (David Dix) writes:

>My scsi tape drive used to work ok with the original 386bsd scsi driver.
>However after installing Julian's new scsi driver the tape is found ok:

[...config info deleted...]

>The disk and CD-Rom work ok but when I try to write anything to a tape with
>'tar cvf /dev/rst0 .' these errors are reported:

> st0: medium error block no. 40 (decimal)
[...and so on...]

I had exactly the same symptoms.  I have a 1542B with an LXT-200 disk,
Wangtek 5150ES tape, and LMS-214 CDROM.  Unfortunately, the problem is *NOT*
reproduceable.  Right now, the driver is workiung fine, and I've changed
nothing since the write errors were reported.

Anyone have any clues on this?

-- 

 == Mark S. Warren    msw@world.std.com     (508) 772-6045 ==
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] fp exception after 387 installation - help !
Keywords: 386BSD floating point 387
Date: 4 Jan 93 09:12:50 GMT
Organization: HCS GmbH, Hamburg, Europe

In <1610@hcshh.hcs.de> hm@hcshh.hcs.de (Hellmuth Michaelis) writes:

[about installing an 387 and getting floating point exceptions after that]

Thanks to everyone who replied to that article !

But the problem stays ! There is (and was) a "double" declaration of getpcpu()
in ps.c - it solved the problem of the ps-coredump on the virgin 0.1, ps ran
fine after installing the patchkit until i installed the 387 ....

anyone else who had such a problem ?
are all other 387's running fine after it's installation ?

ps: made new libm.c, libutil.c, libc.c, kvm_mkdb, dev_mkdb etc. etc ...
-- 
hellmuth michaelis    HCS Hanseatischer Computerservice GmbH   hamburg, europe
hm@hcshh.hcs.de              tel: +49/40/55903-170         fax: +49/40/5591486
Newsgroups: comp.unix.bsd