HDTenEightyP/NetNews huggingface dataset:
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Lance query
Date: 2 Oct 92 16:37:34 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

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

What I want to know is: under what circumstances does the lance clear
this bit, supposedly indicating that the transmitter has been switched
off?

I can get this to happen consistently when running a X graphics package
as a client on one machine, displaying to a server on another, with
386bsd in between acting as a router. Strang thing is I get these reset
errors on the server side card but not on the client side card!

Why would one card behave like this and not the other since they're both
handling these X packets. In fact the client side card is connected to
the rest of the world so it's a LOT busier but it doesn't give me any
hassle. 

Anyway, if someone can explain why the lance does this I'll
track down the cause myself.

Although I wrote the isolink driver I took most of the lance code from
other lance based drivers so I don't know a lot about the lance's
behaviour.

Is anyone else getting errors with this driver? Does anyone else even
have an isolink card or am I the only one in an university that
only allows isolink cards to be used!
-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
  UUCP:     spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr
+++
Newsgroups: comp.unix.bsd
From: pk@cs.few.eur.nl (Paul Kranenburg)
Subject: Re: Marvellous Memory Munching Make
Keywords: where does it go? what does it do?
Reply-To: pk@cs.few.eur.nl
Organization: Erasmus University Rotterdam
Date: Tue, 29 Sep 1992 10:03:39 GMT

In <1992Sep28.165610.22836@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
[...]
>Which "new VM system" is this?  If you mean the one in 0.1, I submit the
>following from Chris Torek, which I hope he doesn't mind me quoting:

>]> The BSD make has at least one leak: it calls vfork, then malloc,
>]> then exec.  This malloc affects the parent as well.  It is fixable,
>]> but not very cleanly (well, you could change the vfork to fork, I
>]> suppose...).

>He also went on to say that BSD uses large amounts of memory and that the
>current memory management wasn't very efficient, and that a rewrite was on
>a project list (not his).

I mean the VM system as it appeared in the NET-2 release and which is also
in 386bsd. The code therein which sets up the address space for a newly born
process pays no attention as to whether it was invoked by the vfork() or
fork() system call. I guess vfork() is retained for compatibility reasons
only and it isn't even compatible anymore as far as sharing address spaces
is concerned.

Also, I do not think the memory leak in my copy of make is explained by your
description above. Are you sure we are talking about the same version of
the sources here?

-pk


Newsgroups: comp.unix.bsd
From: meikel@marie.physik.tu-berlin.de (Michael Feig)
Subject: [386BSD] compiling a list of working Xconfig entries
Organization: ZRZ/TU-Berlin
Date: Mon, 5 Oct 1992 12:56:15 GMT

Hi !

Obviously lots of people (I am one of them) have problems in creating 
proper Xconfig entries for their VGA-card/monitor combination.

I consider it to be a great deal of help for many people out in the net
if mode entries people have found out to be working with their hardware
are compiled into a list and made public - i.e. posting to comp.unix.bsd.

Assuming that such a compilation does not exist somewhere I volunteer to
collect working Xconfig entries, sort them together and post the whole list
to comp.unix.bsd.

So, *please* could anyone who has working Xconfig's send them to me via
e-mail together with a short description of the used VGA-card and monitor
especially the clock rate(s) of the VGA-card and the vertical/horizontal
monitor frequencies. 

Michael.
--
 Michael Feig                 INTERNET: meikel@marie.physik.tu-berlin.de
 Department of Physics                  meikel@cs.tu-berlin.de
 Technical University of Berlin
From: se26+@andrew.cmu.edu (Steven Joseph Esbrandt)
Newsgroups: comp.unix.bsd
Subject: ummm... HELP!
Date: 6 Oct 92 04:34:20 GMT
Organization: Freshman, MCS general, Carnegie Mellon, Pittsburgh, PA

Ok.  I'\m having MAJOR installation problems...

Here's the system that I'm trying to install bsd on:

486/50 EISA
16 MB ram
200 MB Maxtor IDE HD
Trident svga w/1meg
SMC Elite 16

these are the problems:
while GETing a file via ftp- "netin: bad address"
while using cpio to put the bindist where it's supposed to go 
    "cpio: <something>: bad address"
other similar errors... sometimes they result in a trap.. BLECH!
So... anyone got any ideas?
From: zonjic@plains.NoDak.edu (Radivoje Zonjic (CE))
Newsgroups: comp.unix.bsd
Subject: [386BSD] Problem with ethernet
Date: 28 Sep 92 22:23:56 GMT
Article-I.D.: plains.20763
Organization: North Dakota Higher Education Computing Network


I am sorry if these are frequently asked questions, but I
experienced them just today:

After starting 386BSD (both tiny and with bin01) and issuing
a command like    ifconfig ne0 inet 147.91.128.8
something really gets weird: communication over the Ethernet
does function properly, but I keep on getting messages on the
console like
	/386bsd: last message repeated 3 times

and inevitable:
	startart start startartstartstartartartstart

	etc. Any decent work on console is impossible.

Does anyone have experience in solving such problems? NE2000
had been properly reported at boot time, but the ifconfig
command makes problems...


Thanks,
Rade Zonjic
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD/Xfree com ports questions
Date: 28 Sep 1992 11:58:39 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <1992Sep27.143015.24664@cronkite.ocis.temple.edu>, lafollet@astro.ocis.temple.edu (Paul Lafollette) writes:
> 1) I have a Genius mouse on com1.  Does one of the
> standard protocols useable in Xconfig work for it?

Use Mousesystems (works for me, at least...)

> 2) One of the changes I made in Xconfig was to change
> "/dev/tty00" to "/dev/com1".  Was this reasonable?

Depends on where your mouse is connected. Mine is on /dev/com4...

> More important, how do I get the baud rate set right on
> com1?  Does it suffice to include the speed paramater in Xconfig?

Yes, that's sufficient. (1200, I think)

> 3) Related to number 2... i have an internal modem on com2.  I
> would like to configure it so that when i am home i can use
> it for dialout with tip or (God help me) slip.  On the
> otherhand when I am at work, I would like to be able to use
> this as a dial-in port.  Is this possible?  Is it possible
> to do it so I don't have to remember to make a change before
> I go running out the door late for class? :)

Hmm... dunno. But if you find a com driver that supports your mouse *and*
your modem at the same time, drop me a mail and tell me about it.

-Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd
From: andrew@citr.uq.oz.au (Andrew A Zander)
Subject: parallel printer
Organization: Prentice Centre, University of Queensland
Date: Mon, 28 Sep 1992 00:45:41 GMT

I would appreciate some help in getting my 386BSD system
to use the parallel port. There dosent seem to be any
reference to lpt1 in the GENERICISA kernel config file.
There is also no indication at boot time that the system
located a parallel port ( unlike com1, com2 and wd which
are all listed in the boot messages ).

Any help would be greatly appreciated.

Andrew Zander	e-mail andrew@citr.uq.oz.au
CiTR
University of Queensland
Australia.
--
------------------------------------------------------------------------
Andrew Zander                                  | email: 
Centre for Information Technology Research     | andrew@citr.uq.oz.au
University of Queensland  QLD  4072  AUSTRALIA | 
Newsgroups: comp.unix.bsd
From: rminnich@super.org (Ronald G Minnich)
Subject: compaq users: new boot disk and tar file of bin01
Organization: Supercomputing Research Center (Bowie, MD)
Date: Wed, 30 Sep 1992 17:17:09 GMT

Due to a request met.super.org now has the following: 
1) fixit disk bootable on compaqs
fixit.compaq.ftp

2) compressed tar file of one of my compaq's root and /usr/ partition. 
386bsd.0.1.usr-root.tar.Z

the fixit disk is minus some standard things, notably cpio, stty. 
there was not much room. the kernel is stripped too.

the idea is:
1) boot this diskette
2) ftp and zcat are on the diskette, as is ifconfig. 
3) disklabel and newfs your disk, both a and b (you need it for a minute)
4) mount the disk, both a and b partitions (remember you are still running
   from floppy)
5) ifconfig your iface. ftp the tar.z file down to the b partition of the disk. 
6) cd to the place where you have the a partition mounted, and 
   zcat the tar.z | tar xf -. Once that is done the a partition of the
   disk is now loaded with 386bsd. 
7) don't reboot until you fix the host, resolv.conf, and hostname files.

8) shutdown. you should be able to reboot from the hard disk.

NOte: sorry about this, i just realized the kernel on the fixit is 
      only for ne0. if you need something different, let me know ...
      i got sick of the damn printfs. 

ron 
-- 
BOYCOTT ATT&DESTINY  --- BOYCOTT ATT&DESTINY      | rminnich@super.org
BOYCOTT ATT&DESTINY  --- BOYCOTT ATT&DESTINY      | (301)-805-7451
BOYCOTT ATT&DESTINY  --- BOYCOTT ATT&DESTINY      |
From: changhwa@gringo.usc.edu (Changhwa Lin)
Newsgroups: comp.unix.bsd
Subject: NFS server with secure ports
Date: 30 Sep 1992 14:36:55 -0700
Organization: University of Southern California, Los Angeles, CA
Distribution: usa
NNTP-Posting-Host: gringo.usc.edu
Keywords: NFS

The 386BSD 0.1 does not include DES for NFS with secure port. So one can
not mount the file system from the secure port available with SunOS 4.1.X.

Is there anyone out there work on NFS with secure port mechanism for
386BSD 0.1? And if the package can be available for public without DES code?

-- 
===============================================================================
From: torvalds@klaava.Helsinki.FI (Linus Torvalds)
Newsgroups: comp.unix.bsd
Subject: Re: vm86 system call
Date: 29 Sep 92 10:33:34 GMT
Organization: University of Helsinki

In article <1992Sep28.054649.15131@lugb.latrobe.edu.au> lurch@ee.latrobe.edu.au (Geoffrey Liersch) writes:
>
>Has anyone got any comments on where to start the implementation of the 
>vm86 system call such as the system call number, parameters, header files to
>be changed or any other hints/documentation that I should be aware of as I
>am looking at implementing such a call?

A vm86 system call has the rather bad point of resulting in some
fundamental changes in how interrupts/exceptions are handled: the
supervisor stack looks different when the exception happened in vm86
mode.  I don't know how 386bsd handles this state information, but it
could be potentially ugly (ie needing a lot of small changes to some
fundamental routines.)

Assuming that isn't a problem, you might look at the way I did it (with
comments/suggestions from others) for linux: as far as I am concerned,
the linux VM86 code can be used freely for 386bsd if you can get it to
work (under similar conditions as the math emulator.  See the copyright
on that one).  Whatever you do, you need a good understanding of the
vm86 mode.  If you decide to use code from linux, just drop me a line,
and we can make it official (ie don't take the above as "do anything you
like with my code" - but I'm flexible about the copyleft). 

The linux vm86() code assumes all special cases are handled by the
user-level DOS emulator - the kernel does nothing at all when an
exception occurs, and only sends the process the correct signal which
will then be processed in "normal" 32-bit mode.  That means the vm86()
interface is only about 100 lines (might even be less) of C code (and a
couple of checks in "ret_from_sys_call" which is written in assembler). 

I'll be happy to answer (intelligent) questions about the linux
implementation in case somebody wants to do something similar for
386bsd.  It is entirely possible that the linux way of doing things
simply won't work under 386bsd: the vm86() system call does some
"interesting" simplifications by playing around with the supervisor
stack addresses etc. 

		Linus
Newsgroups: comp.unix.bsd
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: 386sx with bsd
Organization: tu-chemnitz
Date: Mon, 5 Oct 1992 18:19:35 GMT

Try disabling all shadow and EMS - it's of nil use within 386bsd since
the processor likes to use the whole memory itself (unlike under dos).

	J"org
--
J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
                                                              \     ~.~. 
	joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de         \   ~  | ~ 
	voice: +49-351-5965 137                                 \    ===
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: Clock.exe doesn't seem to work
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Fri, 2 Oct 1992 14:48:44 GMT

In article <wmbfmk.718016107@rw9.urc.tue.nl> wmbfmk@urc.tue.nl writes:
>If I use clock.exe to determine my videoclocks, 
>this is what I get:
>D
>  25.2   28.3   19.8  23.7  25.2  28.3  19.8  23.7
>
>I have however another program for the videocard, DMODE.EXE, 
>which gives the following results:
>
>  50.35  56.672  65.306  72.240 80.276  90.172  63.114  75.498
>
>My videocard is an ET4000, with 15-bit RAMDAC.
>I know my card can run 1024x768x256 at 70Hz, I can put it into
>that mode using DMODE. I find both listings of clocks a bit 
>suspicious however.
>
>(I have not yet been able to test this because of a harddisk crash)
>
>Has anyone any ideas?
>
>Thanks in advance,
>A
>
>Marc.
>wmbfmk@urc.tue.nl
>
Have you run clock.exe with the et4000 option?
If not I think that it defaults for the et3000..

Cheers,
Amancio


Newsgroups: comp.unix.bsd
From: berry@enuxha.eas.asu.edu (Joel R. Berry)
Subject: patch00038 in the patchkit.
Keywords: patch00038
Organization: Arizona State University
Date: Sun, 4 Oct 1992 08:04:39 GMT

I am not sure if this is has been discussed before, but I am having
a little trouble figuring out how to get patch #38 installed from
the patch kit.  This patch fixes the problem with the wd.c driver
not telling when it finds a bad block on the disk.  After installing
the patch it did find the bad blocks and they were already in my
bad144 block table.  Now when it  comes up into multi-user mode,
it will fail because fsck fails.  I must be using bad144 wrong.  Can
someone help me with how to have fsck use the bad144 bad block table?
Thanks for any help.
   Joel Berry
--

-----------------------------------------------------------
Joel Berry | berry@enuxha.eas.asu.edu
-----------------------------------------------------------
From: se26+@andrew.cmu.edu (Steven Joseph Esbrandt)
Newsgroups: comp.unix.bsd
Subject: Re: Ethernet Western Digital Troubles
Date: 3 Oct 92 17:42:58 GMT
Article-I.D.: andrew.4enYkWa00axfA0vl9Q
Organization: Freshman, MCS general, Carnegie Mellon, Pittsburgh, PA

>I'm have trouble getting tiny 386bsd to find the ethernet card.
>The card is set to: IRO 2 mem 0xd0000 Port 280 ram size 16k.
>
>Tiny 386bsd fails to see the card...
>
>I must be missing smething.

Is your card actually a WD or an SMC? I have an SMC (should be exactly
the same) set up the same way... BSD recognzed it, and I could even ftp
to wuarchive to get the bindist.  But I get an error whenever I try to
actually GET anything (netin: bad address)... Maybe our problems have
the same cause...
From: David.Fox@Saigon.COM
Newsgroups: comp.unix.bsd
Subject: tip sometimes causes wierd terminal behaviour until reboot
Date: 1 Oct 92 00:09:55 GMT
Organization: Station Zebra Corp, Sunnyvale CA Ph:408-739-1520

I've begun to notice something strange with respect to tip.  Depending on
what sites or BBSes I call, the terminal will get screwed up (/dev/console)
until I reboot the system.  Sometimes it might be a continual blinking, others
it will be vi not displaying messages - or the messages it does display in
blue blinking mode, instead of the normal bright yellow, or other times it'll
affect things like manual page displays or emacs.  

It seems to be something on the other end (depends on what strings the
BBS program sends) that causes the problem.

Apart from not calling :) isn't there a simple way to 'reset' dev/console so
it's back to normal, without rebooting?
From: pauls@css.itd.umich.edu (Paul Southworth)
Subject: Re: [386BSD] extract etc01 fails
Organization: University of Michigan ITD Consulting and Support Services
Date: Thu, 1 Oct 1992 20:40:54 GMT

In article <1992Oct1.132112.1@max.u.washington.edu> anything@max.u.washington.edu writes:
>extract etc01 works fine until it gets to the final installation line then
>it says "extract.etc01 /tmp/install.etc01 unable to find file" or something of
>the sort. what now? is etc01 installed or am I up a creek?
>

You're fine.  There are no install scripts for etc01 or src01 distributions.


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

  <Representing myself.  Everything I say is for educational use only.>
From: mbo@dde.dk (Morten Bonde)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Where do I find X386-source
Keywords: X386-source
Date: 6 Oct 92 12:44:01 GMT
Followup-To: comp.unix.bsd
Organization: Dansk Data Elektronik A/S

Is the sources for X386-1.2E (or XFree86 - I don't know the difference??)
available from a mailserver (like nic.funet.fi) ?
I don't have FTP-access to places outside my company :-(
-- 
Morten Bonde                 Voice:  Int. +45 42 84 50 11
Dansk Data Elektronik A/S    Fax:    Int. +45 42 84 52 20
Central Government           Email:  mbo@dde.dk
DK-2730 Herlev, Denmark      uucp:   ...!uunet!mcsun!sunic!dkuug!dde!mbo
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Newsgroups: comp.unix.bsd
Subject: Re: FAQ questions: X386.
Date: 28 Sep 92 14:52:39 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

In article <2AC68B02.12922@ics.uci.edu> bvickers@valentine.ics.uci.edu (Brett J. Vickers) writes:
>1. What are the minor and major device numbers for /dev/vga?
>2. Where can I find the patches for pccons and locore?
>3. Why is the installation information for X386 on 386BSD so
>   damn terrible?
>
>All these things should be in the FAQ, but there isn't one.  Help!
>
>--

The above release was meant as an Alpha release!

Please use the XFree86 release on agate.berkeley.edu:/pub/incoming/X386
Also, read the readme files.

Your local Xfree86 Developer,
Amancio Hasty

>Brett J. Vickers		 "Don't go around saying the world owes you
>bvickers@ics.uci.edu		 a living.  The world owes you nothing.
>				 It was here first."  - Mark Twain
Newsgroups: comp.unix.bsd
From: dawes@physics.su.OZ.AU (David Dawes)
Subject: Re: [386BSD] compiling a list of working Xconfig entries
Organization: School of Physics, University of Sydney, Australia
Date: Mon, 5 Oct 1992 14:55:20 GMT

In article <meikel.718289775@marie> meikel@marie.physik.tu-berlin.de (Michael Feig) writes:
>Hi !
>
>Obviously lots of people (I am one of them) have problems in creating 
>proper Xconfig entries for their VGA-card/monitor combination.
>
>I consider it to be a great deal of help for many people out in the net
>if mode entries people have found out to be working with their hardware
>are compiled into a list and made public - i.e. posting to comp.unix.bsd.
>
>Assuming that such a compilation does not exist somewhere I volunteer to
>collect working Xconfig entries, sort them together and post the whole list
>to comp.unix.bsd.

Such a compilation already exists.  The database is maintained by
David Wexelblat <dwex@mtgzfs3.att.com>, and can be found on
export.lcs.mit.edu in /contrib/modeDB.txt.Z.  It is also included in
the XFree86 distribution (/usr/X386/lib/X11/etc/modeDB.txt).  The file
is currently about 45K -- so is a bit large to post here.

Anyone with contributions to this database should send them to David.

>So, *please* could anyone who has working Xconfig's send them to me via
>e-mail together with a short description of the used VGA-card and monitor
>especially the clock rate(s) of the VGA-card and the vertical/horizontal
>monitor frequencies. 
>
>Michael.
>--
> Michael Feig                 INTERNET: meikel@marie.physik.tu-berlin.de
> Department of Physics                  meikel@cs.tu-berlin.de
> Technical University of Berlin         

David
--
------------------------------------------------------------------------------
 David Dawes (dawes@physics.su.oz.au)    DoD#210      | Phone: +61 2 692 2639
 School of Physics, University of Sydney, Australia   | Fax:   +61 2 660 2903
------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: chip@tct.com (Chip Salzenberg)
Subject: Re: [Re: Catch What They're Saying About Us...]
Date: Tue, 29 Sep 1992 16:44:54 GMT
Organization: TC Telemanagement, Clearwater, FL

According to vixie@PA.dec.com (Paul A Vixie):
>But that does not make it OK for you to respond-as-though-attacked whenever
>someone disagrees with you or calls some action of yours (or Bill's) into
>minor question.  Nothing -- NOTHING! -- can excuse the kind of mud-slinging
>that have characterized your copyrights, release notices, public flames,
>and "disinformation" (your word, which I am borrowing) to the press.

This point is, to me, the most important.

Paul Vixie is right on the mark.

Bill and Lyne, you're doing great work.  But please: Grow a skin!
-- 
Chip Salzenberg at Teltronics/TCT  <chip@tct.com>, <73717.366@compuserve.com>
    "My favorite phenomenon is when someone mails me or posts to this
     group, either calling me a newbie or telling me that my postings
     are not relevant to alt.non.sequitur."           -- Matt Welsh
Newsgroups: comp.unix.bsd
From: c162-dz@po.berkeley.edu (wade shen)
Subject: 3.5" boot disk?
Organization: University of California, at Berkeley
Date: Mon, 28 Sep 1992 21:00:02 GMT

I've been trying to install 386BSD on my little notebook
machine but have been unable to create the TinyBSD386 disk
on a 3.5" drive.  I've been using rawrite.exe and the dist.fs
files but have had no success.  How can I create this disk?

I've tried to format the diskette as a 1.2 meg diskette, but
dos 5.0 does not allow this.

thanks

Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.rt,comp.unix.large
From: br.pct@RLG.Stanford.EDU (Peter C. Tam)
Subject: strdup
Organization: Research Libraries Group, Inc.
Date: Thu, 1 Oct 1992 00:11:50 GMT

	In BSD 4.3 C lib, there is no strdup that is provided in System 5,
& I just happened to get a program that was supposed to be able to compile
in BSD also. Can anyone tell me where I can get the strdup routine for
BSD 4.3, especially, in ibm.pc.rt AOS.
	thanks.

+---------------------------------------------------------------------------+
| Peter C. Tam                         InterNet: br.pct@RLG.Stanford.EDU    |
| Fax: (415) 964-0943                  BitNet:   br.pct@RLG.BITNET          |
+---------------------------------------------------------------------------+
Newsgroups: comp.unix.bsd