HDTenEightyP/NetNews huggingface dataset:
From: wade@nb.rockwell.com (Wade Guthrie)
Subject: Re: 386BSD + LINIX + GNU + X11R5 on CDROM - let us know what you want!
Organization: Rockwell International
Date: Wed, 16 Dec 1992 19:02:23 GMT


In article <1992Dec12.055725.23540@netcom.com>, adam@netcom.com (Adam J. Richter) writes:
> In article <whatever> I wrote:
> >The Linux cd-rom drivers may support [the Rockridge extensions]
> >already, but if you don't already
> >HAVE Linux up and running on your system, the point is moot.  I would not
> >like to see the Rockridge extensions, 'cause then I wouldn't be able to 
> >load Linux from the CD on a system that currently has only DOS.

> 	My Linux/GNU/X CD is a counter-example to your claim.  The CD
> uses the Rockridge extensions, but you can install it on a system that
> "has only DOS" or that has no software at all.  This is because the
> distribution includes a boot floppy that boots linux and then mounts
> the CD.

That is one approach that would be fine.

> 	Even on a distribution that did not include a boot floppy,
> the inclusion of Rock Ridge extension information would not make
> it any harder to install.  After all, you can still read a Rockridge
> disk with a system that only understands iso9660, although the filenames
> will appear in iso9660 level 1 (DOS style) or iso9660 level 2 (similar
> to VMS) formats.

I tried to read a SUN CD-ROM (which uses the rockridge extensions) and had
some problems.  The CD-ROM had one file (README -- which I could read
fine) and several directories (all with names longer than 8 characters).  I
could not change into any of the directories, although everything else seemed
fine.  Now, I admit that I may be missing something here.  If I am, and the
people putting the disk together want to do things that way, may I humbly
request that the README on the disk explain the stuff that I should have 
known?

> Installing Linux from a CD that contains only source
> code is essentially the same problem.

Yeah, this is why I would like a binary of the os.


Wade
wade@nb.rockwell.com
Newsgroups: comp.unix.bsd,comp.os.linux
From: msw@world.std.com (Mark S Warren)
Subject: Hauppaugh 486DX25 and Purek SVGA compatibility???
Organization: The World @ Software Tool & Die
Date: Fri, 18 Dec 1992 04:16:08 GMT

I have an opportunity to buy a system with a Hauppaugh 486-DX25 and a
Purek (Trident chipset) SVGA board, and lots of other standard stuff.

I can't find either of these mentioned in the hardware buyer's FAQ.

Can anyone tell me of their experience with these running 386BSD, Linux,
and XFree86?

Email responses to me and I'll summarize.  Thanks in advance,


-- 

 == Mark S. Warren    msw@world.std.com     (508) 772-6045 ==
Newsgroups: comp.unix.bsd
From: hpeyerl@novatel.cuc.ab.ca (Herb Peyerl)
Subject: Re: 386BSD: Problem in wd.c (?) - affects swap, non-atatched drive(s)
Organization: "NovAtel Communications Ltd. Calgary, Alberta, Canada"
X-Newsreader: TIN [version 1.1 PL8]
Date: Mon, 14 Dec 1992 15:55:04 GMT

Joseph Thomas (jpt@uh.msc.edu) wrote:
: 	Okay - here's a problems I haven't seen talked about and it's
: not in the FAQ. Before I go chase it down and come up with some (possibly
: unique to my system) fix, has anyone else run across this ??? Thanks.

This really SHOULD be in the FAQ since it affects ANYONE using MFM/RLL
drives and having installed the patches from the patchkit.

[Diatribe of problem deleted.]

: Anyone have any ideas??? Thought it was worth asking before I really
: dig into this (not that I've had time before now - but things look good
: for the next week or two).

I went through the exact same thing a few weeks ago and came up with the
same symptoms... When I posted the same sort of message to the net that
you did, someone sent me a message telling me exactly what I'm telling
you now.  

If you use the Norway wd driver, you won't have this problem, you will
also have proper bad144 support and proper multi-drive support.  You
Can get the Norway wd driver from agate.berkeley.edu in (I think) the
unsupported directories.  It might be under "barsoom" (which is where
it originated).  Anyways, the file I got was called "drivepatch.tar" and
contains:

rwxr-xr-x 268/20      0 Jul 31 04:27 1992 ./
rw-r--r-- 268/20   3162 Jul 31 04:22 1992 fd.c.patch
rw-r--r-- 268/20    396 Jul 31 04:22 1992 isa_device.h.patch
rw-r--r-- 268/20   5098 Jul 31 04:21 1992 mkioconf.c.patch
rw-r--r-- 268/20   3510 Jul 31 04:22 1992 wd.c.patch
rw-r--r-- 268/20    991 Jul 31 04:23 1992 CONFIG.SAMPLE

I sent Terry a message when I discovered this asking him to possibly
remove the appropriate patches from his next release of the patchkit
and replace them with these patches but I didn't receive a response
which could indicate that he's either very busy (likely) or didn't
receive my message. (or third possibility: thinks I'm a weenie and
chose to ignore me. :-> )

Anyways, this is definitely one for the FAQ.. (Terry; are you listening?)

--
"I was early to finish | hpeyerl@novatel.cuc.ab.ca <Reply-To>   | I brew |
I was late to start, I | peyerlh@sun.cuug.ab.ca                 | there- | 
might be an adult, but | #define JANITOR "Network Administrator"| fore I | 
I'm a minor at heart." |    JANITOR, NovAtel Communications Ltd.|   AM.  |
-- 
"I was early to finish | hpeyerl@novatel.cuc.ab.ca <Reply-To>   | I brew |
I was late to start, I | peyerlh@sun.cuug.ab.ca                 | there- | 
might be an adult, but | #define JANITOR "Network Administrator"| fore I | 
I'm a minor at heart." |    JANITOR, NovAtel Communications Ltd.|   AM.  |
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Bug Report and Patchkit status
Keywords: time,school,need a life!
Organization: Weber State University  (Ogden, UT)
Distribution: usa
Date: Mon, 14 Dec 92 18:56:15 GMT

In article <1992Dec12.183953.6573@rwwa.COM> witr@rwwa.com writes:
>In article <1992Dec11.224735.23342@fcom.cc.utah.edu>,
> terry@cs.weber.edu (A Wizard of Earth C) writes:
>
>| I am also wary of the USL reaction to large scale distribution of 386BSD
>| (or for that matter, Linux) prior to the suit being resolved one way or
>| the other.
>
>This could cut both ways.  It *might* have a benificial (sort of a ``lancing
>of the boil'') result.

The problem with lancing boils is that one gets staphlococci on ones scalpal.

This is not to say boils should not be lanced; only that it is bad to be a
scapal around boil-lancing.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: mhiroshi@tansei.cc.u-tokyo.ac.jp (H. Murakami)
Newsgroups: comp.unix.bsd
Subject: [386bsd] problem "ifconfig: ioctl (SIOCGIFFLAGS): no such interface"
Date: 20 Dec 92 06:31:35 GMT
Organization: Hokkaido Univ. However I am subject to tansei for JUNET.


I have a problem at the boot time of 386bsd0.1 with Terry's patches.

When I boot the system, the boot message appeares like:

================================
......
adding swap: swapon: adding /dev/as0e as swap device
starting network
ifconfig: ioctl (SIOCGIFFLAGS): no such interface
ifconfig: ioctl (SIOCGIFFLAGS): no such interface
ifconfig: ioctl (SIOCGIFFLAGS): no such interface
ifconfig: ioctl (SIOCGIFFLAGS): no such interface
ifconfig: ioctl (SIOCGIFFLAGS): no such interface
ifconfig: ioctl (SIOCGIFFLAGS): no such interface
add host ps486: gateway localhost
starting system logger, time daemon.
checking for core dump...
Dec 19 18:25:40 ps486 timed[35]: No network usable
preserving editor files
standard daemons: update crond.
starting network daemons: routed printer sendmail inetd.
starting local daemons:.
Sat Dec 19 18:25:52 PST 1992

   386BSD (ps486) (console)

Login: 
================================


The message
	"ifconfig: ioctl (SIOCGIFFLAGS): no such interface"
is the what I would like to know how to fix for.

I think there is no such ioctl functionality "SIOCGIFFLAGS" defined
in the 386BSD0.1.

Does anyone have the fix to stop this noisy messages on the console?

	Hiroshi Murakami
	mhiroshi@tansei.cc.u-tokyo.ac.jp
Newsgroups: comp.unix.bsd
From: osynw@gemini.oscs.montana.edu (Nate Williams)
Subject: Re: Occasional system hangs
Keywords: n
Organization: Montana State University
Date: Fri, 11 Dec 1992 21:04:30 GMT

In article <1gaclpINN84v@hrd769.brooks.af.mil> news@hrd769.brooks.af.mil (InterNet News) writes:
>-Time for more RAM I guess!
>>
>
>  I don't think more RAM will help.  I have 32M of RAM and and 32M swap 
>partition.  It still hangs.  nroff is the usual culprit for me.

The fix for this is to fix G++, re-compile it, and then recompile groff
with the fixed GCC.  The patch for g++ will be in the next patchkit.
[If I ever get it finished :-(]

Nate

-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home. 
work: (406) 994-5991         |  Keeper of the Unofficial 386BSD Bug Report
home: (406) 586-0579         |  Please send bugs and/or fixes you find.
From: mike@zogwarg.etl.army.mil (Mike McDonnell)
Newsgroups: comp.unix.bsd
Subject: [386bsd] need motif
Summary: I want to buy motif for 386bsd; where?
Keywords: motif 386bsd
Date: 15 Dec 92 15:26:56 GMT
Organization: Engineer Topographic Labs, Ft. Belvoir, VA

I need to buy motif to rehost some code under 386bsd.  Someone please
tell me about a distributor here in the US.  Prices too if possible.
From: conklin@kaleida.com (J.T. Conklin)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Need help mounting CD-ROMs.
Date: 17 Dec 92 12:13:30
Organization: Kaleida Labs, Inc.
Reply-To: conklin@kaleida.com
NNTP-Posting-Host: talisman.kaleida.com

Whenever I try to mount a CD-ROM:

	mount -r -t isofs /dev/cd0a /mnt

I get:
	cd0: illegal request
	cd0: illegal request

I can read the directories of the disks fine, but whenever I try to
read any file that is not in the toplevel directory, the open fails
with errno = EINVAL (Invalid Argument).

I'm using a patchlevel 58 kernel with the new SCSI drivers, a Adaptec
1742a controller, and a Texel 3024 CD ROM drive.

I can read the disks fine in MSDOS.

	--jtc


--
J.T. Conklin    Kaleida Laboratories, Inc.
                Mountain View, California
Newsgroups: comp.unix.bsd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: BSD on HP3500s?
Date: 21 Dec 92 01:49:31 GMT
Organization: Kernel Hackers 'r' Us
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: reink@hpuamsa.neth.hp.com's message of Sun, 20 Dec 1992 13:46:51 GMT

In article <21250002@hpuamsa.neth.hp.com> reink@hpuamsa.neth.hp.com (Reinier Kleipool) writes:
>  I suppose you mean with HP3500 an Apollo domain 3500 workstation.
>I dont't think this will be a trivial task, as the 3500 works with an
>68030. So you should do a complete port of the os to that processor.
>I don't know if anybody is doing that. Porting the os starts with a
>port of a C compiler to the 'new' archtecture. Mabe you can use the
>existing Domain C compiler to port the gnu C compiler. But this is
>only the start of an os port.....

Actually, i was working on a port of 4.4 to the DN3500/DN4500,
but for lack of time, never got too far...

I actually found that it wasn't too hard to set up a reasonable development
environment under Domain/OS (10.1 at that time, i think...),
w/ the stuff off of the tape which Keith Bostic gave me...
(which doesn't exist any more, but you couldn't have anyway... 8-)

the gnu c compiler, as disted in net/2 (and probably 386bsd) 
has full 680x0 support -- for the hp300.  just modify a few things,
and set it up to give you one or two unique symbols,
and you win.

>  You should also write new device drivers for ithe domain peripheral
>controllers. This is not a simple task. Unless you intend to become 
>the Willaim Jolitz of the 68000 community!

arguable... 8-)  the ethernet board in the DN[34]500 machines are
the 3COM 3c501 or 3c503, i think, so that shouldn't be too hard;
just occasional byte swapping on 16 bit I/O.

the disk controllers are standard PC controllers...  one type is OMTI i
think, and the other type is the WD7000...

the video boards are a helluvalot nicer than PC video boards; they're
actually flat framebuffers!!! (of course, they've no character mode,
so that's a bit of a problem...  also the color displays are planar not
chunky...)

you could support token ring, but that may or may not be worthwhile
depending on the hardware you have at your disposal...

the way i started off was trying to merge the locore, etc. of the hp300 port
with the devices of the early work on the i386...

There's also been a Mach port to the DN3000, which was somewhat useful,
for info about booting, etc.

i'd be glad to answer questions... 8-)

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
Newsgroups: comp.unix.bsd
From: risner@ms.uky.edu (James Risner)
Subject: Re: [386bsd] what tape drives can be used?
Keywords: 386bsd tape scsi
Organization: University Of Kentucky, Dept. of Math Sciences
Date: Thu, 17 Dec 1992 02:25:52 GMT
Distribution: usa

sitongia@hao.ucar.edu (HAO Computer System Managment Group) writes:

>What brand of tape drives are people using on their 386bsd systems?  I've seen
>the threads about not being able to use CMS tape drives.  What about SCSI tape
>drives?  What brands of tape drives can be used?

>Thanks for your time.

>---
>--Leonard E. Sitongia           HAO System Manager                 
>sitongia@ncar.ucar.edu          voice: (303)497-1509   fax: (303)497-1589
>High Altitude Observatory       P.O. Box 3000 Boulder CO  80307

WangDAT 3200 works perfectly with the new scsi drivers.
sd.c

Risner
From: witke@cs.tu-berlin.de (Marius Witke)
Subject: Re: [386BSD]: installing on a 2nd HD
Organization: Technical University of Berlin, Germany
Date: Sat, 12 Dec 1992 15:44:59 GMT


There were some contradictory postings about this topic in the last
days, so I should tell my experiences.

First, I do boot from 2nd drive, using the first drive for DOS and
the second one for 386bsd.  I don't use SCSI drives, so I can only
speak about AT-bus drives.

Second, this is how I arranged my drive to do so:
   0. I had 386bsd installed on my first drive, so it was much easier
      to work on the second (my kernel supports two drives).
   1. I used the 'pboot' bootselector -available from agate- to 
      be able to choose a partition from second drive. 
   2. I got the SCSI bootset by Julian Elischer, that enables you to
      choose the drive, partition and kernel to boot from.
      I changed the sources to make the second drive the default.
   3. I disklabeled my 2nd drive with these patched bootset, and
      created new filesystems.
   4. I mounted the drive and moved the bsd system from the first to the
      second drive (don't forget to adapt /etc/fstab ...).
   5. After sync, unmount and reboot everything worked !

In the meantime I removed 386bsd from the first drive and had 
no problems with it.

Ok, I hope this could help someone...
ciao,
	Marius.
   
-------------------------------------------------------------------------------
Marius Witke				|  The human mind ordinarily operates
					|  at only ten percent of its capacity
witke@cs.tu-berlin.de			|  --- the rest is overhead for the
Technical University of Berlin, Germany |  operating system.
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: kspousta@qualcom.qualcomm.com (Kevin Spousta)
Subject: Re: Help needed to remove 386bsd off of a 386
Keywords: Won't work with just a high level foramt
Organization: Qualcomm, Inc., San Diego, CA
Date: Tue, 15 Dec 1992 01:36:44 GMT

pauls@css.itd.umich.edu (Paul Southworth) writes:


>In article <3506@carroll1.cc.edu> sander@carroll1.cc.edu (Scott Anderson) writes:
>>I recently decided to move 386bsd to a better machine and as part of the
>>deal, I have to put MS-DOS back on the machine.  I've tried the docs
>>exactly and then complete formats of the hard drive etc, all to no avail,
>>I keep getting an error message saying the it is upset that it can't find
>>386bsd at boot time and that continues in an infinite loop.  I thought
>>maybe I'd try a low level format, but my manual says "Low level formats
>>should only be done by qualified personell."  :)

>If you have an IDE drive then a low-level is a last resort to resurrect
>a trashed drive.  I wouldn't advise it unless you know what you're doing.
>If you do not have an IDE drive, then you can probably low level it with
>relative impunity.

>However, if you haven't tried to do "FDISK /MBR" to nuke the boot record,
>I suggest you try that first.  (That is, do FDISK /MBR in DOS, not 386BSD
>and it will write you a new boot record for DOS.)

I tried the fdisk /mbr bit when I attempted to remove BSD and I still kept
getting the "Can't find 386BSD" error.  I finally made a DOS boot Disk and put
Norton's Disk Editor on it and manually edited the boot sector. I filled up sector 0 with null values and then FDISK'ed.  Worked like a charm..
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Occasional system hangs
Organization: Weber State University  (Ogden, UT)
Date: Mon, 14 Dec 92 17:58:11 GMT

In article <1992Dec11.142822.6314@crash> fpm@crash.cts.com (Frank Maclachlan) writes:
>>  I don't think more RAM will help.  I have 32M of RAM and and 32M swap
>>partition.  It still hangs.  nroff is the usual culprit for me.
>
>I had the same problem. My system system would lock up completely from
>time to time.  Nroff seemed to be particularly troublesome.  I resolved
>it by removing my ULSI 80387 fpu.  You can see if this is the problem
>by modifying npxprobe() in '/sys/i386/isa/npx.c' to not find the fpu
>and return 0.  This causes the fpu to be ignored.

Is there a reliable way to identify this particular chip?  With the number
of problems reported, it would seem worthwhile to identify FPU type, and
emulate only those instructions not supported.  This would allow the poor
people stuck with the chip to derive some benefit from it, as well as
not requiring major surgery to get a machine with one booted and a kernel
set up to ignore the FPU before another surgical procedure to reinsert it.

Another useful approach (that would require full acceptance of Julians
boot blocks -- as in replacing the wdboot code as well) would be to
allow "arguments" on boot to the kernel, like "NOFPU" and "10BITIO" for
people with bad FPU's or single sigma 386's.  Of course this would also
require the ability to put these flags in a file somewhere so the
kernel could have them "on" by default.



					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: mhiroshi@tansei.cc.u-tokyo.ac.jp (H. Murakami)
Newsgroups: comp.unix.bsd
Subject: Has anyone run the REDUCE 3.4 or newer on 386BSD?
Date: 20 Dec 92 06:35:45 GMT
Organization: Hokkaido Univ. However I am subject to tansei for JUNET.

To: comp.unix.bsd
Subject: Has anyone run the REDUCE 3.4 or newer on 386BSD ?

I request the information of the availability of the REDUCE systems
on 386BSD with all the source codes.

Information  like:
	1) Where the system with the license can be purchased from?
	2) How much are they?

Thank you.
	Hiroshi Murakami
	mhiroshi@tansei.cc.u-tokyo.ac.jp

PS.
	How about  MIT MACSYMA?
Newsgroups: comp.unix.bsd,alt.suit.att-bsdi
From: dmuntz@gip.eecs.umich.edu (Dan Muntz)
Subject: Re: AT&T/USL CD-ROM Review Process
Organization: University of Michigan EECS Dept., Ann Arbor
Date: Mon, 14 Dec 1992 20:03:37 GMT

In article <1992Dec14.165913.6896@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>it has reaped from University level research.  The question remains as to
>whether they are willing to trade fututre benefits for control of the
>market; the answer may suprise us.
>

I'm not sure that they are losing anything.  With full knowledge of what 
USL/AT&T has done, universities and reasearchers are still clamoring 
for Plan 9.  If I attend a university with a Plan 9 source license does this
mean I'll have to *live in New Jersey* if I want to do OS reasearch?!

I would have liked to have seen universities refusing to use Plan 9 and joining
in the lawsuit against USL.  What we get instead are places like CMU
dropping their BNR2SS project (net2/386bsd? replacement of AT&T code
necessary to run Mach).  I'll bet AT&T is running scared now.

  -Dan
   dmuntz@eecs.umich.edu

Newsgroups: comp.unix.bsd
From: zxmsd01@studserv.zdv.uni-tuebingen.de (Gunther Schadow)
Subject: Re: [386BSD] lisp/akcl/clx ported to 386bsd?
Organization: Comp. Center (ZDV) U of Tuebingen, FRG
Date: Sun, 13 Dec 1992 16:18:21 GMT

In <li7jbbINNiqb@latexo.cs.utexas.edu> brazile@cs.utexas.edu (P. Jason Brazile) writes:

>I happen to know that Dr. Shelter is working on akcl on our (math department)
>Dell 450 running 386BSD. He has gotten it compiled but last I heard, he was 
>tracking down a floating point bug that occurred in loading which caused the 
>machine to crash.

Well this is great! I have patches too and I think that I already
fixed that bug. I will contact Dr. Shelter. You'll see our akcl will be
there soon!

-Gunther
--
-------------------------------------------------------------------------------
Gunther Schadow,	          e-mail: Gunther@studserv.ZDV.Uni-Tuebingen.DE
Sudetenstrasse 25,	          Phone:  (49) 7071/37527
7400 Tuebingen, Germany.__________Stop__________Horn Please!__________O.K. TATA
Newsgroups: comp.unix.bsd
From: hackney@moxie.hou.tx.us (Greg Hackney)
Subject: 386BSD wd.c timeout problem during autoconfig
Organization: None
Date: Wed, 16 Dec 1992 00:25:42 GMT


We found a timeout problem in the wd.c code that occurs when the
system trys to autoconfigure the disk drives at boot time.

In wdcommand() there is a declaration:  int timeout = 1000000;

This is a loop counter that runs while the disk controller
registers are being probed. For a Conner 510MB IDE drive on a Compaq
SystemPro 486/33, that value is not large enough for the controller
to respond in time. (It's only short by a count of about 3,000 on
this system).

As a result, booting the dist.fs floppy indicates you have no hard
disk drives.

The fix was to increase the value of timeout. We used 1,500,000.
--
Greg Hackney   hackney@compaq.com
Mike Busby     mcb@compaq.com

Newsgroups: comp.unix.bsd