HDTenEightyP/NetNews huggingface dataset:
From: slix@svcs1.UUCP (Bill Miller)
Newsgroups: comp.unix.bsd
Subject: terminal lockups with 0.1
Keywords: sgtty, terminal problems
Date: 5 Sep 92 04:46:21 GMT
Organization: Silicon Valley Computer Society, Sunnyvale, CA

Hi,
 
I'm a recent (4 days) user of 386bsd, and I pulled off some unix
source code (ephem) that I was working with under DO$, and am
having troubles with it.  It compiled fine, but as soon as it
hits the first "press any key to continue" it locks up completely,
and the only thing I can type is ctrl-Z to suspend it, and that
locks up the shell and I have to reboot.

I'm wondering if this is related to the problems 386bsd has about
tty lockups when it first boots up.  The app uses sgtty.h.  I tried
using termio.h but it's not there.  Frankly, I know next to nothing about
i/o under Unix systems.  The other thing, is this at all related to FIONREAD?
From: andre@abs.sed.sun.ac.za (ANDRE SKARZYNSKI)
Newsgroups: comp.unix.bsd
Subject: how do I put 386bsd on drive 2 (I second that!)
Date: 11 Sep 92 15:07:58 GMT
Organization: Electronic Engineering, University of Stellenbosch, South Africa

In article <92252.033510MHS108@psuvm.psu.edu> MHS108@psuvm.psu.edu (Mark Solsman) writes:

>Hello -

>I have a question that I cant seem to find an answer to in the docs-

>I have two esdi drives, I would like to make the first drive msdos, and
>the second drive 386bsd.  Can I do this, and how?  I am not sure, because
>386bsd install only seems to look at drive one, and doesn't notice the big
>vacient sign on the partition table for drive two...

>any/all help would be greatly appreciated!

>-----
>Mark Solsman

>The Pennsylvania State University  -  University Park, Pennsylvania
>                "My opinions are not that of my own"

Yes, how. I also want to keep drive one for my present OS (Linux! ;-))

Andre
abs@sunvax.sun.ac.za
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: How to make mwrite work?
Organization: Nanyang Technological University - Singapore
X-Newsreader: Tin 1.1 PL4
Distribution: usa
Date: Tue, 8 Sep 1992 12:24:57 GMT

David.Fox@Saigon.COM writes:
: How does one use mwrite correctly:
: 
: I have a file "astro.zoo" in my root directory under 386bsd, and
: I want to write this to a floppy (B:) in msdos format.  I've tried
: all sorts of variations on a theme, the theme being "mwrite unixfiles
: msdosdirectory" as per the usage().
: 
: I've tried - amongst others:
: 
: mwrite astro.zoo b:
: mwrite astro.zoo b:\
: mwrite astro.zoo B:\
: 
: etc.
: 
: Everything responds with "open(): no such file or directory.  astro.zoo
I had the same problem. I solved it by using my old 0.0 versions.
I have deleted my 0.1 mtools so not sure why that happens.

That error message happens even when I'm just as ordinary user so I just
change the access rights of /dev/fd0a to 666 i.e. rw_rw_rw_ even with the
0.0 mtools.

CAn someone verify whether it is caused by the access rights of fd0a?

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet

Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Minimum system requirements for 386bsd ?
Organization: Weber State University  (Ogden, UT)
Date: Tue, 15 Sep 92 19:34:02 GMT

In article <2552.2ab5def0@vger.nsu.edu> r_moore@vger.nsu.edu writes:
>In article <2551.2ab5de20@vger.nsu.edu>, r_moore@vger.nsu.edu writes:
>> I need to know what the minimum requirements are to run 386bsd are. More
>> specifically will it run on this configuration:
>> 386sx @16mhz
>> 1 meg RAM
>> 40 meg HD
>> if it will not run on this system what additions will I need to make ?
>>         Thanks, Richard
>> 
> While I'm at it is there a bsd FAQ for information such as my above question ?
>if so is there a site where I can FTP it from ?
>          Thanks again, Richard
>

It *will* run on that configuration; however, you will need a high density
floppy drive to load it before it can run, and you will need to rawrite
the files from a DOS machine with a high density drive to get them onto
disks.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
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
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: abeech@kraken.itc.gu.edu.au (Adrian Beech)
Subject: LPT problems in 386BSD - HELP!
Organization: ITC, Griffith University, Brisbane, Australia
Date: 11 Sep 92 11:40:32 GMT

Greetings!

I've installed the lpt patch as suggested by many readers of this group.  I
now cat print using the `cat <file> >/dev/lpt' command with no problems.
However when I use the lpr command all I get is the banner page and then the
system falls over.  Has anyone else had the same trouble?


-- 
Adrian V. Beech                              E-MAIL: A.Beech@ext.gu.edu.au
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd -- The New Newsgroup
Date: 10 Sep 1992 19:03:33 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu
Keywords: newsgroup 386bsd news group

In article <1992Sep09.203731.3433@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes:
>...
>In any event, I would suggest waiting about a month or so before any such
>discussions; by that time, the judge in the USL v BSDI and State of
>California suit should have returned, and made a decision on BSDI's motion
>for dismissal...

386BSD is not involved in this dispute, and work is continuing as usual.
Neither Bill nor I believe that this dispute should have any affect on the
formation of a 386BSD newsgroup nor should it preclude research in the area.
(However, a comp.os.386bsd newsgroup would make certain "AT&T wanna-bes 
with BSD" most unhappy, as it's pretty hard to get people to pony-up dollars
when 386BSD is available and it's users active and supportive.)

Lynne Jolitz.
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: FORMs with bsd spooler
Organization: Weber State University  (Ogden, UT)
Date: Sat, 5 Sep 92 01:17:09 GMT

In article <1882juINN688@cs.widener.edu> gjh@netman.Berkeley.EDU (Gary J. Habermann) writes:
>Does anyone know  how to handle special forms with a BSD spooler.  I have several forms
>and want to be able to control which one prints?

Two possibilities:

1.	Get Palladium from Project Athena.  8-).  It might even work...

2.	Cheat.  You do this by providing multiple filters for the same printer.
	How do you do this?  Use a remote printcap definition that refers to
	*the local host*.  I currently use this for 300DPI/400DPI selection
	for a SparcPrinter.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                                       terry@icarus.weber.edu
 "I have an 8 user poetic license" - me
-------------------------------------------------------------------------------
From: richard@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.bsd
Subject: Networking
Date: 8 Sep 92 13:13:22 GMT
Organization: AIAI, University of Edinburgh, Scotland

I'm considering getting an ethernet card for use with 386BSD.  I see
various cheap no-name cards advertised which claim to be compatible
with NE1000/2000 or WD8003E.  Are these likely to work?

Alternatively, does anyone have IP running between 386BSD machines
using the parallel port?

Thanks,
-- Richard
-- 
Richard Tobin,
AI Applications Institute,                                R.Tobin@ed.ac.uk
Edinburgh University.
From: blile@thesis1.med.uth.tmc.edu (BUD W. LILE)
Newsgroups: comp.unix.bsd
Subject: Xfree (X386) and 386BSD
Date: 6 Sep 1992 17:47:46 GMT
Organization: University of Texas Medical School at Houston
Originator: blile@thesis1.med.uth.tmc.edu


I have installed X386 on my 386BSD system and have two questions?

1.  The README makes reference to a locore.s patch, any one know of
    where to find it.  I have looked on agate.berkeley.edu and have
    been unable to find it.
 
    I did apply the com port patches.
 
2.  When trying to run x i get a message that says "cannot open /dev/vga"
    any one know what device this is?  Is there a special driver that
    needs to be built into the kernel, and of so, weres the sources?
 
If any one can answer please post to the news group or try my network
address.

Thanks
BUD W. LILE
blile@thesis1.med.uth.tmc.edu
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386BSD] Ethernet problem
Organization: Weber State University  (Ogden, UT)
Date: Fri, 11 Sep 92 21:14:27 GMT

In article <18qp76INN53o@usenet.INS.CWRU.Edu> esw@po.CWRU.Edu (Eric S. Wallace) writes:
>
>After much frustration, I came to the same conclusion, Joerg. So, does
>anyone know of a newbootable which will support a Cabletron or AT&T
>Ethernet card? If not, please write one! :)

The StarLAN dist.fs that I uploaded to agate.berkeley.edu has the 8M
stability patches, fixed (HP/ATT box) memory identification code, and
the if_ie (PC-10 NAU/EN100 AT&T ethernet[starlan card] driver).  It's
been up there for quite some time.

	I will be posting the memory identification fixes real soon now
...I'm down to only about a half a billion things to do.  Probably this
weekend some time.  Sorry to the people I told I'd upload the NFS patches
and then didn't.  They'll be this weekend as well.


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
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
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: pauls@icecreambar.css.itd.umich.edu (Paul Southworth)
Subject: Re: 386bsd -- The New Newsgroup <Summary>
Reply-To: pauls@umich.edu
Organization: University of Michigan
Date: Sat, 12 Sep 1992 20:54:51 GMT

Well having heard some opinions about the new newsgroup project, I think I  
can distill the lines being put forth as:

Position 1: No change, stay in comp.unix.bsd

Position 2: Create a single newsgroup, comp.os.386bsd or freebsd

Position 3: Create three newsgroups (that was my position) with
            comp.os.386bsd.misc
            comp.os.386bsd.install
            comp.os.386bsd.development

Position 4: Create seven newsgroups (L. Jolitz's position) with
            comp.os.386bsd
            comp.os.386bsd.kernel
            comp.os.386bsd.windows
            comp.os.386bsd.sharedlib
            comp.os.386bsd.net
            comp.os.386bsd.bugs
            comp.os.386bsd.ann or announce

Did I fail to represent anyone who has posted in this thread so far?

I would like to get a feel for what sort of support each of these  
positions has.  Please either follow up or email me.
Newsgroups: comp.unix.bsd
From: 31005_1650@uwovax.uwo.ca (Mark Bramwell 1-519-661-3714)
Subject: using mwm and others with Xfree86 and 386bsd
Organization: University of Western Ont, London
Date: Thu, 10 Sep 1992 18:31:55 GMT

Has anyone been using any other window manager other than twm?

I have been using the Motif window manager and I like it better than twm.

I have heard of gwm, olvwm plus a few others, but have not tried them
with Xfree86.

PS:  The way I use mwm with 386bsd is this.....

edit /usr/X386/lib/xinit/xinitrc

comment out the line that states twm &
use xhost to allow other access  xhost +   ( I think or was it xhost - )

rsm userid otherhost /usr/bin/X11/mwm -display myip:0 &


This actually tells otherhost to run its window manager pointing back to my 
box.  It actually works great!

I have also tried HPvue window manager this way, and it works ok also.


-- 


..........................................................................
.  Mark Bramwell,    VE3PZR                                              .
.                                                                        .
.  The University of Western Ontario           Bitnet:  MBRAMWEL@UWO.CA  .
.  School of Business Administration           Packet:  VE3PZR @ VE3GYQ  .
.  London, Ontario, N6A 3K7                    Phone:   (519)  661-3714  .
..........................................................................

Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386BSD] cc1 fatal error & more!
Organization: Weber State University  (Ogden, UT)
Date: Sat, 12 Sep 92 17:29:13 GMT

In article <veit.716290747@du9ds3> veit@du9ds3.uni-duisburg.de writes:
>In <1992Sep11.012623.14965@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>
>>>>
>>>>Hi, I tried to compile a program and got the cc1 fata error like:
>>>>cc -I.. -I../..  -O -c fogdeck.c
>>>>cc: Program cc1 got fatal signal 6.
>>>>*** Error code 1
>>>>
>[...]
>>	Make has a terrific leak.  I compiled up a different version (sorry,
>>proprietary).  You may want to try gnumake.
>
>Terry, can you comment on the "terrific leak"? I am interested because I
>just build a large application (named X386 from the patched mit-tapes)
>with gcc 1.39 and bsdmake without ever having seen something like a signal 6.

	It's not the signal 6 (IOT).  It's a memory leak.  I found that
compiling the kernel with a makefile was much, much slower than compiling
it by hand, and that for large packages (>300 files in one target), it
would eventually run out of memory and slow to a crawl.  Apparently, the
process image was just growing and growing and growing.

	I compiled the SVR4 make (which is why it's proprietary) and the
problem "went away".  This actually required only minor changes.

	I have found that I get an IOT from the compiler if it runs out of
memory.  With make sucking up all the memory, there wasn't enough left to
compile.  Eventually, I always got an IOT, no matter how small the files
were.

	I tested this by building a make file that compiled the same file
to numbered file names 10,000 times (it wasn't a complicated file).

	Admittedly, the memory leak could be in fork or exec, but this is
kind of doubtful, since the SVR4 make fixed the problem.  Hence my statement
"Make has a terrific leak".


					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
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
-------------------------------------------------------------------------------
joel
Newsgroups: comp.unix.bsd
Subject: 386BSD with Bustek 542b scsi adapter
From: joel@hadar.wisdom.weizmann.ac.il (Isaacson Joel)
Date: Sun, 6 Sep 1992 21:22:31 GMT
Organization: Weizmann Institute of Science, Computation Center

   I have have tried installing 386BSD on a 386dx 40MH computer with a
Bustek 542b scsi adapter. The Tiny diskette boot fine and install
works to completion but the resulting scsi disk doesn't boot.
It just seizes up very early in the boot proceedure. The scsi disk can
be mounted under Tiny 386BSD system and it seems just fine.
   Has anyone have any luck with using this disk controller under 386BSD.

						Joel Isaacson
						joel@wisdom.weizmann.ac.il

Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: Re: /dev/lp and LARGEW configurations
Date: Fri, 11 Sep 92 02:29:57 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <5717@blue.cis.pitt.edu.UUCP> dri@gl.pitt.edu (Paul) writes:
>I have a quick question about the lp.c patch in the unofficial/terry
>directory on agate.berkeley.edu for 386bsd-0.1.
>
>I have applied the patch to the various files and double checked the
>changes, and when I build a new kernel with the GENERICISA configuration
>I get a reboot after trying to print something to /dev/lp (I did mknod).
>
>More exactly the printer starts to spit out a ROOT banner page and then
>the system softreboots.

    I am using Eric Haug's lpt driver, but if you haven't already done
    so, you might try recompiling lpd (/usr/src/usr.sbin/lpr/lpd/lpd.c).  
    Before I did this reboots would occur when printing control characters.  
    -Andrew Moore <alm@netcom.com>
From: tom@afthree.as.arizona.edu (Thomas J. Trebisky)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd -- The New Newsgroup
Keywords: newsgroup 386bsd news group
Date: 11 Sep 92 18:35:46 GMT
Organization: University of Arizona, Tucson, AZ

wjolitz@soda.berkeley.edu (Lynne Jolitz) writes:
>As per Bill's suggestion, here's a breakdown of some of the suggested 
>topics and groups:
>
>	comp.os.386bsd		(general questions and trivia)
>	comp.os.386bsd.kernel	(discussion on kernel content/structure)
>	comp.os.386bsd.windows	(ditto, on windowing systems like X)
>	comp.os.386bsd.sharedlib (shared library and programming environment)
>	comp.os.386bsd.net	(networking topics)
>	comp.os.386bsd.bugs	(new bugs)
>	comp.os.386bsd.ann	(announcements, fixes, additions)
>

Looks good, in particular I am glad to see the .kernel group split out
so I can avoid a lot of the (needful but uninteresting to me) stuff
of the "My system won't boot, what do I do now?" sort.

Maybe some discussion about kernel internals can be stirred up, and
not get lost in the volume of other traffic.
--
	Tom Trebisky	ttrebisky@as.arizona.edu
...."There's no sense in being precise when you don't even
.... know what you're talking about." 
                       - John von Neumann  
Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Subject: Which dir structure?  2 X386, each with its own!?
Organization: University of Western Ontario
Date: Thu, 10 Sep 1992 21:33:42 GMT

I have downloaded both copies in X386.  One uses what I call the standard 
directory names.  /usr/lib/X11   /usr/bin/X11


The latest uses everything under  /usr/X386


which one is going to be kept?  I want to setup things now.  I have both 
copies working ok, each in its own directory structure.

mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Western Business School  --  London, Ontario
Newsgroups: comp.unix.bsd
From: petri@ibr.cs.tu-bs.de (Stefan Petri)
Subject: Re: A major BSD socket bug?
Summary: it is not a bug
Reply-To: petri@ibr.cs.tu-bs.de (Stefan Petri)
Organization: TU Braunschweig, Informatik, Bueltenweg, Germany
Date: Wed, 9 Sep 1992 16:12:24 GMT


In article <1992Sep9.053147.411@lmpsbbs.comm.mot.com> rittle@supra (Loren James Rittle) writes:
[..]
>/* It appears that whenever recvfrom() doesn't block and yet doesn't
>   return a packet (due to being in non-blocking mode), it hoses the
>   socket in some way.  Any later call to recvfrom() that returns a
>   valid packet fails to write the sender's network address in the
>   sockaddr stucture that was passed to recvfrom().
[sample program deleted]

>  It seems to me that the correct output (for my machine) should be:
>  676331921 hello1   # 676331921 is 145.1.80.40 - my machine's IP address BTW.

Printing the address in hex would surely have helped you :

ra 11> cc    -target sun4 -o t t.c 
ra 12 > ./t
7f000001 hello1

It's the address of the loopback interface, since that is where the packet is
routed through :-)

Stefan
Newsgroups: comp.unix.bsd
From: sef@kithrup.COM (Sean Eric Fagan)
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Organization: Kithrup Enterprises, Ltd.
Date: Thu, 10 Sep 1992 05:58:34 GMT

In article <1992Sep10.015548.4228@pegasus.com> richard@pegasus.com (Richard Foulk) writes:
>Termcap/terminfo is a standard that's available on, pretty much, all
>Unixes.  So why leave it out of the POSIX standard?

Termcap and terminfo are two different things.  Or aren't you aware of that?
Which one should be standardised on?

Choose termcap, and you choose an outdated, limited, and obsolete
technology.

Choose terminfo, and you leave out all of the non-SysV sites out there, such
as BSD systems.  And you are still choosing a limited and obsolete
technology.

Create an alternative, and you run the risk of creating something that is
unworkable, overly complicated, difficult to implement, or just out and out
broken.  Ask Henry Spencer or Dan Bernstein about that.

-- 
Sean Eric Fagan  | "You can't get lost in one room, no matter how
sef@kithrup.COM  |  little effort you make to learn your way around."
-----------------+    -- William E Davidsen (william@crd.GE.COM)
Any opinions expressed are my own, and generally unpopular with others.
From: schneck@Physik.TU-Muenchen.DE (Bernhard Schneck)
Newsgroups: comp.unix.bsd
Subject: Re: more about 386BSD SLIP
Date: 8 Sep 92 12:55:42 GMT
Organization: Leibniz-Rechenzentrum, Muenchen (Germany)

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

>In article <Sep.7.14.41.53.1992.602@athos.rutgers.edu> hedrick@athos.rutgers.edu (Charles Hedrick) writes:
>>Aside from the well-known silo overflow problem, I think there's
>>another problem in the serial driver.  I just had output hang in SLIP.

There may be a buglet in obcopy (or something like that) in the kernel
code, which will kill TCP ACK packets (among others).  There was a fix
in the PPP code for 386BSD which also repairs SLIP.

\Bernhard.
--
Bernhard Schneck              | Email: Bernhard.Schneck@Physik.TU-Muenchen.DE
GeNUA Gesellschaft fuer Netz- | TU Muenchen Physik | There is no problem so big
und UNIX-Administration mbH   | 8046 Garching      | that it cannot be run away
8000 Muenchen 83, Germany     | Germany            | from.   Illusions, R. Bach
From: wk0x@ANDREW.CMU.EDU (William Stephen Kish)
Newsgroups: comp.unix.bsd
Subject: XFree86 on Tseng 4K local bus?
Date: 4 Sep 92 17:14:38 GMT
Article-I.D.: andrew.8ee0byS00axa419UpC
Organization: Carnegie Mellon, Pittsburgh, PA


Has anyone managed to get XFree86 (X386) working on a localbus based
Tseng 4000?  Respond by email...

Thanks,
William Kish
kish+@cmu.edu
Newsgroups: comp.unix.bsd