HDTenEightyP/NetNews huggingface dataset:
From: danson@lgc.com (Doug Anson)
Subject: Re: Motif on X386???
Organization: LandMark Graphics Corporation LGC
Date: Mon, 17 Aug 1992 14:08:57 GMT

In article <1992Aug16.210959.17266@fcom.cc.utah.edu>, terry@cs.weber.edu (A Wizard of Earth C) writes:
|> In article <16kt8jINN9so@agate.berkeley.edu> randyc@ocf.berkeley.edu (Randy Yen-Pang Chou) writes:
|> >Anybody got motif working on X386 with 386bsd?  How's the performance?
|> >How much memory do I need to compile it(not including the docs) ?
|> 
|> You have to have at least the 1.2 Motif sources, and, if you mean "how much
|> disk" instead of "how much memory", the answer depends on whether you want
|> .... stuff deleted ....

Motif 1.2 Really? --- 1.1 is running on my 386BSD quite nicely.  I had no
problems compiling it based on X386 1.2E 1.0.2.  Furthermore I compiled it in
about 30 Meg space (including install).

Cheers,
Doug
--
-------------------------------------------
Doug Anson					
Internet: danson@lgc.com			
Phone:	  713-579-4739
SNAIL:    Landmark Graphics Corporation LGC	
	  333 Cypress Run			
	  Houston, TX 77094			
-------------------------------------------
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: 680x0 version of 386BSD?? [Was: Re: Mac version of 386BSD??]
Date: 21 Aug 92 00:10:01 GMT
Article-I.D.: fcom.1992Aug21.001001.3788
Organization: Weber State University  (Ogden, UT)

In article <1992Aug20.173817.21681@organpipe.uug.arizona.edu> tom@afthree.as.arizona.edu (Thomas J. Trebisky) writes:
>You can even run unix
>without an MMU on a vanilla 68000, but I won't go into the horrid schemes
>involved in doing that.

They're not horrid!  They're your friends!  8-).

Actually, you have to go to pure swapping.  Then the only things you care about
are segmentation faults (which you treat as if they were segmentation faults)
and stack grows (which you handle with a doctored u struct an "stack probes".

The best examples I have seen for this are the 68000 Xenix for Tandy 6000's,
and the SVR2 for the Amiga 1000 ith a Xebec hard drive (sorry; Xebec only,
and yes, the Amiga is on Weber's SVR4 source license list).

Virtual memory is pretty mush out of it, as is nearly any form of address
remapping.


					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: jaap@alice.att.com (jaap)
Newsgroups: comp.unix.bsd
Subject: Re: Search for BSD books
Keywords: books
Date: 18 Aug 92 19:45:34 GMT
Article-I.D.: alice.23478
Reply-To: jaap@alice.UUCP ()
Organization: AT&T, Bell Labs

In article <scs.713925427@wotan.iti.org> scs@iti.org (Steve Simmons) writes:
 > scm@aiware.in-berlin.de (Harald Schmidt) writes:
 > 
 > For internals, you need "The Design and Implementation of the 4.3BSD
 > UNIX Operating System" by Leffler, McKusic, Karels and Quarterman.
 > Addison-Wesley, 1989, ISBN 0-201-06196-1.  *The* book on the internals
 > of BSD 4.3.  May be slightly out-of-date with the 4.4isms that have
 > crept into Jolix and BSDI, but still far and away your first choice.
 > 
 > >Does anybody knowns where I can buy those books?
 > 
 > In Germany?  You've got me.... but undoubtably there are US bookstores
 > which ship overseas.

Note that Leffler etc. is also translated into German.


	jaap
Xref: sparky comp.unix.bsd:4482 misc.legal.computing:1986
From: leonard@qiclab.scn.rain.com (Leonard Erickson)
Newsgroups: comp.unix.bsd,misc.legal.computing
Subject: Re: Poisoned textbooks and net articles?
Date: 20 Aug 92 08:58:17 GMT
Article-I.D.: qiclab.1992Aug20.085817.5749
Reply-To: 70465.203@compuserve.com
Organization: SCN Research/Qic Laboratories of Tigard, Oregon.

jeff@aiai.ed.ac.uk (Jeff Dalton) writes:

>Well, just when _are_ we allowed to use information we read in books
>or on the net?  And what's the point of reading these things if the
>answer is "never"?  How much does copyright restrict us?  (Is there
>any point in reading books, for instance?)

>I'm not trying to disagree with you here -- I'd like to know the
>answers to these questions, and I'm starting to worry about what
>the answers might turn out to be.

>A lot of people buy books in order to learn more about how to
>write programs.  These books are copyrighted.  Do we have to
>artificially skew our code so that we don't use exactly the
>same technique we read about or what?

You are confusing copyright and patent. You can use *all* the info
you want from a copyrighted work. If you *copy* sections of
it with only minor changes, you are violating copyright. Using
the *techniques* is not covered. 

You *might* run into trouble if it could be shown that your stuff
was a "derivative work". I'm not really sure what the law says
there.

-- 
Leonard Erickson		      leonard@qiclab.scn.rain.com
CIS: [70465,203]			 70465.203@compuserve.com
FIDO:   1:105/51	 Leonard.Erickson@f51.n105.z1.fidonet.org
(The CIS & Fido addresses are preferred)
From: ian@airs.com (Ian Lance Taylor)
Newsgroups: comp.unix.bsd
Subject: Re: UUCP woes with 386BSD
Date: 15 Aug 92 16:46:06 GMT

bill@unixland.natick.ma.us (Bill Heiser) writes:

>I noticed that it is TAYLOR UUCP.  Maybe that means someone could 
>re-compile it to use HDB style config files instead of those funny
>Taylor types?  :-)

You should be able to recompile it that way by simply editing policy.h
and typing make.  I haven't looked at it on 386BSD, but I assume it is
shipped already configured (that is, conf.h and Makefile have been
created).  If not, you will also have to type configure.

The patches I have received for 386BSD have been relatively trivial,
and will be incorporated in the next version.
-- 
Ian Lance Taylor                ian@airs.com                uunet!airs!ian
First person to identify this quote wins a free e-mail message:
``I would prefer my life to contain more hours of pain, if that means
  that none of this pain is still to come.''
Newsgroups: comp.unix.bsd
From: MCROSBY@bsa3.kent.edu (Malcolm Crosby)
Subject: Re: How could I add 2nd Hardisk in 386BSD 0.1 ?
Organization: Kent State University, School of Business Admin.
Date: Sat, 15 Aug 1992 18:55:39 GMT

In article <13AUG92.19224777@twncu865.ncu.edu.tw> center4@twncu865.ncu.edu.tw writes:

>Dear Sir:
>        Now I want to install the 2nd Hardisk Conner 30104 (120MB)
>in my 386BSD 0.1 System, what's the step:
>        Could you give me the detail procedure and disktab file.
>
>        Thanks very much!!

I would also like to know how this is done. I have a 2nd 330MB ESDI drive 
that I'd like to add.

>Sheng, I-shing
>center4@twncu865.ncu.edu.tw


----
Malcolm Crosby

Internet:   blabc183@ksuvxa.kent.edu
E-Mail:     emcamiga!malcolm@redpoll.neoucom.edu (E-Mail Please)
Newsgroups: comp.unix.bsd
From: niko@iastate.edu (Nikolaus E Schuessler)
Subject: Re: Installing GNU Emacs 18.58 under 386BSD
Organization: Iowa State University, Ames, IA
Date: Mon, 17 Aug 1992 21:55:48 GMT

In article <pugwr*s00@channelz.GUN.de> swildner@channelz.GUN.de (Sascha Wildner) writes:
>Hi!
>Is there anybody who can tell me how to install GNU Emacs 18.58 under
>386BSD?
>

Yes, it is easy.. 
 

1) ftp to agate.berkely.edu find the emacs config stuff 
   (found in the 386bsd area).  
2) ftp to wuarchive.wustl.edu and get emacs-18.58.tar.Z 
   out of the gnu directory.  

3) follow the directions found in the README(?) file retrieved on
   step 1.  

   You may have to edit one .c file to #include<termios.h> because it
   looks for 'termio.h' which didn't seem to exist.


-- 
Niko Schuessler               
Project Vincent Systems Manager              email: niko@iastate.edu
Iowa State University Computation Center     voice: (515) 294-1672
Ames IA 50010                                snail: 272 Durham
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD filesystem types. Can I mount a SunOS 4.1.2 disk?
Date: 16 Aug 92 11:34:51 GMT
Organization: Auspex Systems, Santa Clara

>>Hi.  Is the 386BSD filesystem a 4.2 filesystem?  Ie, could I mount
>>a Sun formatted, ... disk?  (Formatted under 4.1.1 or later of SunOS).

As noted by Casper Dik, the "Ie" doesn't belong there.  They may both be
4.2 file systems, but unless the Sun disk came from a Sun386i, the byte
orders differ (and the 386i didn't get a 4.1.1 port).

>Note that Sun have made some changes to the file system format which
>may mean that your Sun disk is not a 4.2 filesystem.

Well, actually, it ceased being a "4.2" file system in 4.1; it's a
4.3-tahoe file system there....  (It picked up most 4.3-isms in 4.0,
although directory truncation didn't show up until 4.1.)  However,
386BSD is presumably also a 4.3-tahoe or later file system.

>In particular,
>they introduced something they call "clustering" in 4.1.1.

That didn't involve any file system format changes; it's just changes to
the code, so that with "rotdelay" of 0, the UFS code can do sequential
reads and writes in "maxcontig"-sized chunks, rather than in file system
blocks.

4.1.1 file systems with "rotdelay" of 0 and "maxcontig of 7 (7 8K
blocks, or 56KB chunks) should be readable by BSD-file-system code even
if it doesn't support clustering - modulo other file system changes, and
byte-order issues, and the like.

Now, one "other file system change" is that the "fs_headswitch" and
"fs_trkseek" fields in the 4.3-tahoe and later superblock are, in SunOS,
an 8-byte file system ID.  The file system id is "currently unused and
unmaintained"; I don't know whether 386BSD uses the "fs_headswitch" or
"fs_trkseek" fields, so this may not be a problem.  (Then again, without
code changes, the byte order is a bigger problem, as noted....)
Newsgroups: comp.unix.bsd
From: terry@ithaca.Eng.Sandy.Novell.COM (Terry Lambert)
Subject: Re: X386 still doesn't work for me
Keywords: X386, startup trouble, keyboard junk
Organization: Novell NPD -- Sandy, UT
Date: Tue, 18 Aug 1992 17:41:27 GMT

In article <1992Aug18.141621.24833@olymp.informatik.uni-bonn.de> juengst@boss1.physik.uni-bonn.de (Henry G. Juengst) writes:
>... --- ...    ;-)
>
>Hello,
>
>  I'm still trying to get X386 working, but it only starts if I boot MSDOS
>before and reboot without a hardware reset. Otherwise it produces a core
>dump (you can have it if it could help). If it starts (e.g. via xdm) the
>keyboard input is a "little bit" confused. I do not the character I pressed.
>
>I tried to open and close /dev/vga and /dev/console, stty raw </dev/console,
>removed /dev/console from /etc/ttys. Nothing helps.
>
>Please, can anybody tell me where I can find a patched X server, BSD kernel
>or what ever I need ? I'm afraid, but I can't recompile the server or kernel
>because the hard disk is to small. I've got a friend who has the same
>problem and he would be happy too, if you can help.

You *must* patch the kernel.  This is not an option.  Patches are in the
X distribution.  This will continue to be the case until such time as the
patches are incorportated into the standard kernel and it is rereleased.

Anyone with an already patched kernel without too much garbage in it (mine
has 3 extra file systems, only 2 of which currently work, patches to the
boot code, patches to the page table code, the starlan driver, and a hacked
hi/lo density floppy driver) care to ftp it up to agate.berkeley.edu for
this guy and his friend?

					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu

---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.
From: briggs@cstest.cs.vt.edu (Allen Briggs)
Newsgroups: comp.unix.bsd
Subject: Re: xterm: Permission Denied
Date: 19 Aug 92 13:28:16 GMT
Organization: Virginia Tech Computer Science Dept, Blacksburg, VA

In article <1992Aug18.214058.14232@hparc0.aus.hp.com> harry@hparc0.aus.hp.com (Harry Page) writes:
>I am having a little trouble running xterms under X386. Every time I try to
>start an xterm I get a message saying Permission Denied and the xterm dies.

Xterm should be installed setuid.  The owner should probably be root or
whomever owns the tty(/pty/ttyp/whatever)s that it will be allocating.
In any case, my xterm (not on X386) is owned by root and has permissions
4555.

-allen
-- 
Allen Briggs             | The spirit was freedom and justice
briggs@csugrad.cs.vt.edu | Its keepers seemed generous and kind
Computer Science         | Its leaders were supposed to serve the country
Virginia Tech            | Now they don't pay it no mind...--Steppenwolf
Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: WD (SMC) elite-16T enet board.
Organization: TRW Financial Systems
Distribution: comp
Date: Thu, 20 Aug 1992 04:49:05 GMT

Well, so Now I can compile kernels and start porting my scsi
stuff, but one thing remeains to be done..

I cannot get my wd elite16T to be recognised by the kernel

As far as I can see from comments other people have made
in this newsgroup, this is a supported board.

The settings of the board match those in the config file
so, I would have expected that it would have found it,
however NO message is printed out regarding that
device during the boot.

I only re-joined this group recently after a couple of
weeks away from it (for work reasons). Has there
been any information regarding this board that
I have missed out on?

I have it configured to Int=3, mem=D0000, port=280
(one of the defaults for the board.)
We run it with this configuration under MACH
and this board was last seen working.
I have no com ports to clash with it, so this configuration SHOULD work.

If no-one has any ideas then I suppose I'll be able to
figure it out but each delay keeps me away from the 
scsi stuff which is the aim of the exercise.


+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v
From: armhold@action.rutgers.edu (George Armhold)
Newsgroups: comp.unix.bsd
Subject: Endless boot cycle- suggestions?
Date: 14 Aug 92 16:34:42 GMT
Organization: DIMACS @ Rutgers University

I'm having problems getting 386BSD 0.1 to boot from my HD.  Here's my
configuration: 

	ZEOS 386 SX
	2 MB Ram
	American Megatrends BIOS
	300MB ESDI,Adaptec controller
	Western Digital Elite16T Enet card
	DOS 5.0

I've got a 32 MB DOS primary partition, and an extended partition, 75
MB of which are for another DOS drive, and the rest to BSD.  I did
this partitioning via fdisk under DOS.

When booting off of the install floppy, it right away recognized the
partition I had allocated for BSD (magic?) and I followed the
procedure for formatting and installation.

It claimed to have formatted 214 MB pretty damn quick- about 3
minutes.  I'm suspicious.  It then mounts the disk and does the
install.  "Press any key to reboot from HD".  I do, and the machine
goes into an endless boot cycle.  When it tries to read the bootstrap
code from the HD it does a hard reset, memory check, etc, and then
loops again. 

I checked the partition code for the BSD partition, and sure enough
it's set to A5.  I read the "known problems" article, but didn't find
a solution.  If anyone could offer some help or suggestions I'd be
most appreciative.  I'm not intimately familiar with this hardware, so
please forgive me if I've left out some important detail.

Thanks,
-George
-- 
		 Internet: armhold@dimacs.rutgers.edu
	       UUCP: {backbone}!rutgers!dimacs!armhold
		    BITNET: armhold@PISCES.BITNET
From: hm@hcshh.hcs.de (Hellmuth Michaelis)
Newsgroups: comp.unix.bsd
Subject: 386BSD - vt100 vga driver posted to alt.sources
Keywords: 386bsd vga driver vt100
Date: 18 Aug 92 10:03:55 GMT
Organization: HCS GmbH, Hamburg, Europe

hi,

i just posted a pccons driver for vga-boards to alt.sources. this one is
strictly for vga owners, no other boards are supported yet, sorry!

it's possible, that it may not everybodies taste, for me it is a great
enhancement of my 386bsd environment. if you don't like it, cat * >/dev/null!

being a (character-) terminal user, my objective was to 1. provide vt100
functionality and 2. to get function key labels, which i got used to since
my first meeting with an hp3000 series II and 3. "cheap" virtual screens.

i'd like to thank holger veit for his keyboard code, without it something
i did would not be possible. he reported some bugs to me, some i could fix,
one (a trap while pressing keys) is not reproducable by me, so ...

the additional code posted contains mostly all my development environment,
it is posted in the hope to speed up further development and bugfixing.

this code is far from being perfect, but i think, it's a startpoint.

this whole stuff ran now several weeks without noticable instabilities
on a 486/16Mb/scsi machine, so i think it is time now to let it go.

thanks to lynne, bill and all the contributors to 386bsd !

ps: if someone has code to detect, what type of card is installed (mda,
    cga,ega,vga) and this code avoids the use of the programming language
    "int10", i would like to hear from him !

hellmuth
-- 
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
From: faldor@seq.uncwil.edu (Sherman Brown)
Subject: ncheck not implemented? /fstat errors
Keywords: fstat, ncheck
Organization: Univ. of North Carolina @ Wilmington
Date: Sat, 22 Aug 1992 07:07:17 GMT

I have noticed that ncheck isn't in the /sbin, /bin, or /usr/bin
directories and I was wondering if it had been implemented at all
or if an equivalent was available...
Also the executable fstat for file-specs. doesn't seem to work
when I put it in verbose mode it tells me that everything I try
to run it on is of an "unknown file type 2" so it's bugging me...

Any info. would be appreciated,
Faldor

.___________________________________________________________________.
|               University of North Carolina at Wilmington          |
|                          Faldor Inglorion                         |
|                        faldor@seq.uncwil.edu                      |
|-------------------------------------------------------------------|
|  Alien Invasion Division : Integration/Substitution Group. (ISG)  |
.___________________________________________________________________.
From: dinda@cae.wisc.edu (Dinda Peter)
Newsgroups: comp.unix.bsd
Subject: Re: WD Ethernet Card not found on warmboot
Date: 21 Aug 92 22:18:28 GMT
Organization: U of Wisconsin-Madison College of Engineering

In article <714317431.111@eyrie.img.com.au> athos@eyrie.img.com.au (David Burren) writes:
>I also have an Elite16 Combo (it's the 8013E with AUI, BNC, & UTP) and
>see exactly the same symptoms.  No ideas yet, just another "me too!"...
>
>This is in a system that's evolved from a 16 MHz 386SX through a 20 MHz
>386DX to a 40 MHz 386DX.  Using a mono display, A1540, floppy, & serial.
>The we device has never so far been detected on warm-boot.

Every solution I've gotten so far is to "recompile the kernel."  I
really wonder why Unix *still* doesn't have installable device drivers.
The Novell Netware Requester for OS/2 is updated by just copying over
the new device drivers - there's even a PM program that'll do it for
you.  DOS has had installable device drivers (device=) since 2.0.  Is
there a fundamental reason why Unix hasn't/will not support this?
Newsgroups: comp.unix.bsd
From: bill@unixland.natick.ma.us (Bill Heiser)
Subject: Re: UUCP woes with 386BSD
Organization: Unixland Public Access Unix  (508) 655-3848
Date: Fri, 14 Aug 1992 22:37:19 GMT

mink@coyote.datalog.com (Clint Ruoho) writes:

>I've been unsuccessful in getting UUCP to work under 386bsd.  Has anybody 
>else out there had any success in this?  Could somebody send me some sample 
>scripts that are better than the default ones?

I noticed that it is TAYLOR UUCP.  Maybe that means someone could 
re-compile it to use HDB style config files instead of those funny
Taylor types?  :-)

-- 
bill@unixland.natick.ma.us                      ESIX Mailing List Moderator
Public Access UNIX/USENET/E-MAIL!  UUCP Accounts Available!  (508) 655-3848
5 lines  -  Located in Natick, MA   USA    Supporting V.32/PEP/V.42bis, etc.
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
From: pynq@midway.uchicago.edu (George Jetson)
Newsgroups: comp.unix.bsd
Subject: Report small bug (?) in GO32
Date: 17 Aug 92 21:42:57 GMT

I did something like:

	go32 foo bar bletch > outfile

and it exited quickly back to the the DOS prompt (it should have run for
awhile).  Turned out that I had forgotten to set GCCTMP, and it could
not open the swap file.  However, the msg to that effect ended up in
OUTFILE.  I suggest that GO32 error msgs go to stderr, not stdout.

Actually, a case can be made that they should just be blasted
to the terminal (something like to "CON" [In Unixese, /dev/tty]),
since at this point, your program has not even run (it might want
to have exclusive control over the contents of the stderr stream)
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: WD Ethernet Card not found on warmboot
Organization: Weber State University  (Ogden, UT)
Date: Sat, 22 Aug 92 05:37:03 GMT

In article <1992Aug21.171828.14323@doug.cae.wisc.edu> dinda@cae.wisc.edu (Dinda Peter) writes:
>Every solution I've gotten so far is to "recompile the kernel."  I
>really wonder why Unix *still* doesn't have installable device drivers.

It has installable device drivers!  What you do is:

1)	Install the driver
2)	Recompile the kernel  8-) 8-).

Seriously, that's what loadable kernel modules and streams are all about...
Actually, streams modules are more like "configurable" device drivers.
Loadable kernel modules can be system calls, devices, pseudo devices, file
systems, or streams modules.

>The Novell Netware Requester for OS/2 is updated by just copying over
>the new device drivers - there's even a PM program that'll do it for
>you.  DOS has had installable device drivers (device=) since 2.0.  Is
>there a fundamental reason why Unix hasn't/will not support this?

These aren't "loadable drivers"... these are "boot time configurable drivers"
...the closest DOS comes to loadable drivers is GSS CGI, AutoCAD, and printer
configurations.  Printer configurations are like printcap entries, and the
others are rather application centric (ie: like UNIX shared libraries or
runtime link-loading).

Best thing you can do is wait for the necessary modifications to gcc to
do symbol relocation and resoloution against a known a.out module, and
incorporation of a link-loader into the kernel.  This will allow loadable
kernel modules.

Until then:

1)	Relink the kernel with all possible permutations of configuration
2)	"boot time configure" it like DOS by linking the correct one to
	/386bsd.


					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
-------------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
Subject: Re: Restrictions on free UNIX / 386BSD (Re: selling 386BSD)