HDTenEightyP/NetNews huggingface dataset:
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: HELP!  VM problems while recompiling X11R5
Date: 30 Sep 92 18:37:51 GMT
Organization: ICEM Systems, Inc.

I'm having even more problems while trying to compile X11R5.  :-(

I built all of X11R5 (including PEX, InputExt and TYPE1 fonts)
just over a week ago.  I was eventually able to compile everything
with no errors.  But then I tried to go in and bring it up to X386
1.0.2...   The X11R5 patches 14-16 went in fine.  But the X386 1.0.2
patch failed so miserably that I had to start from scratch.

So I uncompressed the raw MIT distribution (mit-[1234].??) and patched
it with patches 1-13, X386 1.0.1 and the 386BSD patches (this is
exactly what I did the first time).  All looked good, so I did a
"make World >& world.log &" and a "tail -f world.log" and went home.

This morning I found that the make had failed miserably in
./extensions/lib/PEX.  It seems that everytime it tried to compile a *.c
file that included ../include/cpx.h it would run out of virtual memory.

Now normally this wouldn't be suprising for a 386-40 with 8MB of memory
except for two things:  1) I've got 43MB of swap, 2) this didn't happen the
first time that I built X11R5 with PEX.

I've tried reducing the size of my kernel by reducing MAXUSERS, ptys and
unneeded devices (sd2, sd3, st?, cd?, etc).  I've also removed nfs daemons
from the startup procedure (they aren't running now).  But I still get
stuck with "virtual memory exhausted".

Does anyone have any ideas?  I've tried everything that I could think of.

Also, does anyone have a working vmstat or pstat?  I desperately want to
be able to watch my VM to trace this problem.

BTW, I've tried to use ps -aux to trace VM usage, and it seems that cc1
is the culprit.  It's VSIZ goes up to over 6500 before it fails.

-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/* we are realizing infinite possibilities in exchange for our soul */
From: shanny@snake20.cs.wisc.edu (Nicholas Shanny)
Newsgroups: comp.unix.bsd
Subject: Emacs diffs - where are they?
Date: 29 Sep 92 17:06:52 GMT
Article-I.D.: daffy.1992Sep29.170652.24994
Organization: U of Wisconsin CS Dept


Subject says it all. I would like to get emacs-18.58 up and running under 0.1. A while back
I saw patches for emacs to work under 386BSD. Where can I get these patches?

Thanks

nick Shanny
shanny@cs.wisc.edu
Newsgroups: comp.unix.bsd
From: kmo@sae.com (Mike Ovington)
Subject: Re: Patents: What they are. What they aren't. Other factors.
Organization: Template Software
Date: Fri, 2 Oct 1992 19:16:11 GMT

In article <1992Oct1.230931.7833@netcom.com>, mcgregor@netcom.com (Scott Mcgregor) writes:
|> In article <1992Oct1.134749.5671@cae.prds.cdx.mot.com> dan@cae.prds.cdx.mot.com (Dan Breslau) writes:
|> 
|> >Regardless of that problem, it's ridiculous to claim that the end 
|> >result of LZW is a rearrangement of the polarity of electrons.  The
|> >end result is the transformation of information, regardless of the
|> >medium.  This is the essence of what algorithms are.
|> 
|> I've never disagreed that the end result of LZW is a rearrangement of
|> information, not polarities of electrons.  What I have said is that
|> one could construct a physical process patent that described the
|> transformation of polarities of electrons without appealing to mental
|> states, or even without assigning the polarities significance of being
|> information.  It just focusses on the physical world changes. In such
|> a patent, the fact that you are modifying the polarities is essential,
|> because that is EXACTLY what you are claiming is the benefit.

Focussing on physical world changes misses the crux of what a software
patent is trying to protect. It isn't trying to protect the physical changes,
it is trying to protect the thought process/algorithm that went into
creating those physical changes.

Say I create a new sorting algorithm which, for large volumes of data, is
10 times faster than any existing method. A patent on that software would
prevent other people from using my algorithm without permission.
They can still sort their data with other algorithms, which means they can
have the same input and same output, i.e. the same physical world changes.
I would not be able to tell if they are infringing by looking at physical
changes in their disks, RAM or anything else. I could only tell if they
are infringing by examining the non-physical algorithm that they used to
sort the data. Even if the speed of the algorithm used by the alleged
infringers were the same as mine, I can't be sure that they didn't just
invent an equally good sort routine.

It is the mental process, not the physical process that seems to be protected,
at that strikes me as out of the patent realm.
-- 
________________________________________________________________________________
    Michael S. Ovington                         Template Software 
       uunet!sae!mikeo                   13100 Worldgate Drive, Suite 340       
        mikeo@sae.com                         Herndon, VA 22070-4382
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: BEWARE:  stupid placement of swap space...
Keywords: (or:  Don't be stupid like me :-)
Date: 25 Sep 92 14:24:58 GMT
Organization: ICEM Systems, Inc.

Just a word of caution to anyone who installs swap space on extra
disk drives.  I learned this the hard way and don't want anyone
to be as stupid as I am ;-)

I borrowed a 1.0GB SCSI drive so that I could build X11R5 and have some
extra swap space.  But when I disklabeled the drive, I put partition
b (swap) in cylinders 0-19 and gave the rest to partition a.  I am also
running with Julian's SCSI subsystem (it's amazing!).  After about
2-3 hours of compiling X11R5, my machine would start giving "sd1: timeout"
errors and nothing but a reboot would bring back my filesystem.  Also,
after rebooting, my swap space would NOT come back.  swapon -a complained
about /dev/sd1b not being configured.

I originally thought that I might be having SCSI cable length problems.
But the solution turned out to be:

    1) repartitioning the 1.0GB drive so that partition a (ufs) came
       first.  The swap space is now at the end of the drive.
    2) adding "swap on sd1" to my kernel's configuration file and
       rebuilding the kernel.

Everything is now fine.  By the way, the reason for not putting swap
first was given to me by a gentleman from Germany (sorry I've forgotten
your name :-(  It turns out that the first few sectors of a SCSI drive
are used for partition information.  A filesystem will not use the first
few sectors of it's partition (knowing about the reserved blocks).  But
a swap space will eventually overwrite the partition information,  thus
causing strange things to happen.

BTW, I've now got X11R5 built with PEX and the Type1 stuff.  If anyone is
in need of something (object, executable or source) from this, just drop
me an email and I'll do what I can for you.  Please understand that I'm
doing this from work and that company business MUST come first.  I will
try to respond as fast as I can to any reasonable request, please be
patient.  Also, don't even think of asking for me to email the entire
source or executables.  If there is enough demand for this, then I will
try to place it in an anon-ftp server.
-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/* we are realizing infinite possibilities in exchange for our soul */
Newsgroups: comp.unix.bsd
From: bad@flatlin.ka.sub.org (Christoph Badura)
Subject: Re: 386BSD and IDE drives
Organization: Guru Systems/Funware Department
Date: Sat, 3 Oct 1992 03:23:30 GMT

In <BvCCD0.5J0@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes:

>In article <id.O7NT.0O3@ferranti.com> peter@ferranti.com (peter da silva) writes:
>>>       Never a need to run bad144 or worry about bad sectors.
>>Oh, you should worry. Trust me.
>	With IDE/SCSI?  Please elaborate.

Because catastrophic disk failures announce themself some weeks before
by suddenly developing bad sectors. Thisway you get an early warning.
-- 
				Christoph Badura  ---  bad@flatlin.ka.sub.org

AIX is a better... is a better...  is a better... OpenSystem.
					IBM Rep at GUUG Symposium '92
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject:  fdprobe() does not see fdc0 
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Wed, 30 Sep 92 11:06:20 GMT


Some time ago I posted that fd0 was not seen anymore and I blamed it
on some problem I might have had with various patches not properly installed.

Now I found out that fd0 is only recognized by the autoconfig code when
the floppy drive contains a floppy and the door is closed. I admit, I did
not check it with door closed and no floppy inserted , should I ? :)

Anyway, now I always put a non-bootable floppy into the drive when booting.
Strange, though, isn't it?

--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.

Newsgroups: comp.unix.bsd
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: 386BSD's non-standard C library
Organization: tu-chemnitz
Date: Tue, 6 Oct 1992 18:26:08 GMT

alex@am.sublink.org (Alex Martelli) writes:

>...

>I once benchmarked the is*() and to*() functions from ctype.h as macros
>using table-lookup instead and got huge speedups... that was in some PC
>C compiler long ago, but I believe a simple lookup will still be
>superior to a comparison, if and addition, and you need only pay a
>few hundred bytes (256 each for toupper(), tolower(), and is*() since
>the latter can make do with 1 byte/char by using the bits as flags for
>lowercase, uppercase, digit, etc, for example isalnum() will do the
>lookup and & the flag byte with (ISLOWER|ISUPPER|ISDIGIT)).
>-- 
Ooops, you are not right, i guess. The macros _and_ the functions all
do a table lookup (btw: the tables are smaller, only 2 * (256 + 1) bytes;
i.e. for each char + for EOF one byte for the is*()-flags, and one byte
for to{upper,lower}() ). But the problem is still another: if i had
a given string ``FOO'', it'd be obvious: tolower()ing it must result in
``foo'' - but i can write down this immediate without any function or
macro calls:-) If i don't know which characters my string consists of,
but my intent is to have all possible uppercase characters in lower case,
i'd _always_ habe to test for isupper(). So why shouldn't do that the
tolower() function/macro?
ANNOUNCEMENT: my enhanced ctype(3) package is complete now. That would
be especially of interest for European people. It is based on configur-
able character classes as done in SVR3. I'm only awaiting the test re-
port of an alpha tester before releasing it.

	Enjoy, 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                                 \    ===
From: adrian@ibmpcug.co.uk (Adrian Hall)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] Properly patched init.c wanted
Date: 28 Sep 92 12:23:47 GMT
Organization: The IBM PC User Group, UK.

In article <1992Sep27.220337.29789@dsuvax.dsu.edu> ghelmer@dsuvax.dsu.edu (Guy Helmer) writes:
>I have tried to run 386bsd 0.1 with /sbin/init compiled from the
>sbin/init/init.c at patchlevel 4 from Terry's patch kit, but it fails
>strangely -- a little while (10 to 20 seconds) after 386bsd begins
>running /etc/rc, the machine reboots (usually while running fsck).  If
>someone has an operating, patched init, could you please send it to
>me?  Thanks in advance.

All sources are available (patches to Alpha-3 patchkit!) on 
rachel.ibmpcug.co.uk for anonymous ftp.

Adrian
-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
From: bvs@BitBlocks.com (Bakul Shah)
Newsgroups: comp.unix.bsd
Subject: Re: getdtablesize
Date: 26 Sep 92 20:52:18 GMT
Organization: Bit Blocks, Inc.

tlukka@vipunen.hut.fi (Tuomas Lukka) writes:

>I've had a couple of programs (most notably login and screen)
>crash under zsh.
>With gdb, I found that the reason was that they did something like
>for(i=getdtablesize(); --i>2; close(i));
>and getdtablesize returned something like 2000000000 and this
>naturally would take a while to run... 

Another culprit is popen(). It attempts to allocate an array to hold
getdtablesize() number of descriptors and fails under zsh.

In 386bsd there is no fixed limit on how many open file
descriptors a process may have so getdtablesize returns the
current resource limit on open file descriptors; which is
2,147,483,647 or thereabouts by default in zsh.  A quick fix may
be to lower this limit using `limit descriptors N'.

Now I don't think what zsh is doing is wrong.  The problem is in
the use of getdtablesize() in popen() and the code above.  What is
needed is a system call that returns the highest *open* file
descriptor number.

Bakul Shah <bvs@bitblocks.com>
Newsgroups: comp.unix.bsd
From: wutcd@chemnitz.guug.de (Joerg Wunsch)
Subject: Re: What kind of code does GCC produce?
Organization: tu-chemnitz
Date: Mon, 5 Oct 1992 18:15:34 GMT

STDN%MARIST@VM.MARIST.EDU (Dan Newcombe) writes:

>Hi,  When I compile a program using cc (gcc) what kind of output
>does it produce?  Is it straight 80x86 assembly code, or is it
>some sort of psuedo-code that the system will interpret?
> thanks,
>  -Dan
Try compiling

	gcc -O -S foo.c

and have a look at ``foo.s'' to see the code which is normally fed
into the assembler (as).

	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: Granville.Moore@purplet.demon.co.uk (Granville Moore)
Subject: multiport serial with 389
Organization: FidoNet node 2:252/305.0 - The Purple Tentacle, Reading
Date: Thu, 1 Oct 1992 18:14:00 +0000

You said:
KW>   Who uses multiport serial adapters under 386bsd?
KW>   Did this require spcific drivers/kerner modification andif , which?

Please post a summary of replies, as I would like to use some CB811 adaptors
which I have lurking in my system...

Regards,

Granville


  PQ-Under-Trial 2.15  We don't need no steenking DOS...
Newsgroups: comp.unix.bsd,comp.unix.pc-clone.32bit,comp.unix.pc-clone.16bit
From: greg@unlv.edu (Greg Wohletz)
Subject: Aplus computer Co.
Originator: greg@duke.cs.unlv.edu
Organization: The Cave
Distribution: usa
Date: Thu, 1 Oct 92 03:26:25 GMT

Does anyone have anything good or bad to say about these folks?  I'm
considering buying some hardware from them with the intent to run 386bsd
and/or mach 3.0 on it.

						--Greg
From: rcskb@minyos.xx.rmit.oz.au (Kendall Bennett)
Newsgroups: comp.unix.bsd
Subject: Re: How to format UNIX floppies under 386BSD
Date: 26 Sep 92 06:31:10 GMT
Organization: RMIT Computer Centre
NNTP-Posting-Host: minyos.xx.rmit.oz.au

bs@Germany.EU.net (Bernard Steiner) writes:

>However, do yourself a favour and cut down on cylinder groups and tune the
>bytes-per-inode to your needs.

Does someone want to explain how to do this? Do you need to change the
disktab entry (if so, what about posting one :-), or is it some cryptic
set of command line options to newfs?

BTW, if I finally get mtools working on 386BSD, it has an mformat command
to format an MSDOS floppy right? So you could write a shell script that
would use mformat to low-level format the floppy, then newfs to put a
file system on it. Or is mformat only a high level format program (like
the MSDOS 5.0 format without /U?)...

Thanks,

+------------------------------------------+-------------------------------+
| Kendall Bennett                          | Internet:                     |
| RMIT Advanced Computer Graphics Centre   | kjb@citri.edu.au              |
| CITRI Building, 723 Swanston Street      | rcskb@minyos.xx.rmit.oz.au    |
| Carlton Victoria 3053 AUSTRALIA.         |                               | 
+------------------------------------------+-------------------------------+
| CoSysop (Bossman), PC Connection Australia:               +61 3 688 0909 |
+--------------------------------------------------------------------------+
Newsgroups: comp.unix.bsd
From: bmyers@rucs2.sunlab.cs.runet.edu (B.Myers)
Subject: Re: 386BSD's non-standard C library
Organization: Radford University
Date: Tue, 6 Oct 92 21:35:42 GMT


In refrence to this subject header, The curses routines
included are rather ancient. I can't compile any of
my programs that I have written using curses because
it doesn't support all of the comand set. Nor does it
have all of the #defines in it. Ither I'm loking in
the wrong place or i'm using specialized commands that
are not supported on all machines. I'm currently trying
to port pcomm and am running into difficulty on all
of the #defines that a "standard" curses library should
contain. Such as KEY_LEFT, and the various functions
dealing with attributes such as the function WATTRON();
Anyone know where I can obtain the sources to curses so
I may recompile it with as many compatabilities as I can
shove into it?

hats of to all who have helped develope 386bsd into what
is it today, and what it will become tomorrow... The
best damn PD UnIx available. :)
--
Brandon Myers
bmyers@rucs2.sunlab.cs.runet.edu
From: jimj@miller.cs.uwm.edu (James Jegers)
Newsgroups: comp.unix.bsd
Subject: Re: HELP: wiped out my DOS partition
Date: 5 Oct 1992 15:58:19 GMT
Organization: University of Wisconsin - Milwaukee
Distribution: world
NNTP-Posting-Host: 129.89.9.13

In article <1992Oct5.150129.27179@unibi.uni-bielefeld.de>, torsten@techfak.uni-bielefeld.de (Torsten Kasch) writes:
|> 
|> I've got some problems installing 386BSD "by hand". Until last weekend
|> I had a fine working system (Thanks to all who made this possible!) of DOS
|> and BSD until I decided to do some "real partitioning"...
|> 
|> a 100MB Conner CP3104. I had BSD working in a 450MB partition (along with 
|> 50MB DOS) on the first HD. Now I want to divide the BSD partition as  follows:
|> 	a: 40MB       /
|> 	b: 20MB       swap
|> 	d: 70MB       /usr
|> 	e: remaining  /volumes


  ha ha ha ha ha ha..  You did the same thing I did!!!

   The "d" partition cann't be used as a partition ..  the 'd'
partition is the whole drive..  So even though you set it aside as 70meg
for unix. It actually was the first 70meg of your HD.  Which is probably
where you dos is..

So change the d to an e, and move the rest of the drive numbers down.
Make a d partition that is the whole drive. and then 
reformat your dos partition and stick dos back on it.

Hope you made a backup of DOS :-)

|-- 
     ______________________________________________________________
    /\               University of Wisconsin -- Milwaukee          \
    \_| Computing Services Division     Computer Science Department |
      |   jimj@csd4.csd.uwm.edu           jimj@miller.cs.uwm.edu    |
      |   jimj@convex.csd.uwm.edu                                   |
      |   __________________________________________________________|___
       \_/_____________________________________________________________/
Newsgroups: comp.unix.bsd
From: snodgras@cs.unca.edu (Ryan Snodgrass)
Subject: Re: 386BSD - what a pain to install!
Organization: University of North Carolina at Asheville
Date: Sun, 27 Sep 1992 02:09:09 GMT

Ok, I have a question I need to have answered.  I tried installing 386BSD the
other day with no success.  Here is what I want to do:

Install BSD on a hard disk partition (would have been F) in DOS, so that it
looks like:

Primary Partition 20meg
Extended Partition 320meg

Then the extended partition has three logical partitions, each about 106meg,
the first two are to be formated for DOS, and the last logical partition is
for BSD.  Is this possible?

Also is it possible to have both DOS and BSD on the system?  Thanks.  Oh and
one other quick question.  I know it is 386BSD, but is it possible to put it
on a 286?

Thanks,
Ryan Snodgrass
snodgrass@uncavx.unca.eud
snodgrass@unca.bitnet

Newsgroups: comp.unix.bsd
From: dorsey@lila.com (Bill Dorsey)
Subject: Re: Elite16 ethernet problems (solved)
Date: Tue, 29 Sep 1992 06:31:41 GMT

Yesterday I wrote about some problems I experienced with my SMC Elite16
ethernet card on my 386-system.  This card is probably identical to the
WD8013 card.  Hacking the driver, it appeared that accesses to odd-memory
in the cards buffer failed.

Examining my system configuration carefully, it appears that my Weitek
super-vga card uses memory from A000:0000 through D000:FFFF.  386bsd expects
the buffer to be at D000.  I reconfigured the 386bsd buffer address to be
E000 and ran the software configuration utility on the card to change its
address to E000, too.  I then booted 386bsd, and was greeted by a functional
ethernet card!  I still can't figure out why it worked under DOS with NCSA
telnet at D000, but not under 386bsd.

Anyway, perhaps this note will save someone else some trouble.

Oh, and if anyone's curious, I ftp'd a large file from a Sun Sparcstation
and consistently got a transfer rate of 300KB/sec.  After installing the
16-bit ethernet driver patches by Barry Lustig, this went up to 370KB/sec.
Ftp put performance wasn't quite as good, at 270KB/sec with the 16-bit driver.

- Bill Dorsey
Newsgroups: comp.unix.bsd