HDTenEightyP/NetNews huggingface dataset:
From: thomasg@cip-s02.informatik.rwth-aachen.de (Thomas Gellekum)
Subject: Re: [386BSD] cc1 fatal error
Organization: Rechnerbetrieb Informatik  /  RWTH Aachen
Date: 14 Sep 92 06:21:17 GMT

veit@du9ds3.uni-duisburg.de (Holger Veit) writes:

>In <thomasg.716194555@cip-s02> thomasg@cip-s02.informatik.rwth-aachen.de (Thomas Gellekum) writes:

[some stuff deleted]

>Just one question? Did you set 'limit memorysize' to 'unlimited' in csh before
>the above compile?

no, as far as i know, limit is a builtin of csh and i use rc as a login shell.
but correct me, if i'm wrong.

>Holger
>-- 
>|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
>|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
>|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
>|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"

thomas
-- 
thomas gellekum, kapellenstr. 26, d-5100 aachen, w-germany
dq060ge@dacth11.bitnet	     |      thomasg@pool.informatik.rwth-aachen.de
"why stop now, just when i'm hating it?" - marvin 
Newsgroups: comp.unix.bsd
From: dawes@physics.su.OZ.AU (David Dawes)
Subject: Re: Help with X386 and xmd!!!!
Organization: School of Physics, University of Sydney, Australia
Date: Tue, 8 Sep 1992 07:01:47 GMT

In article <1992Sep7.232511.6638@noose.ecn.purdue.edu> tgt@neon.ecn.purdue.edu (Conan the Librarian) writes:
>In article <1992Sep6.115915.3934@desire.wright.edu> cse0935@desire.wright.edu writes:
>>I'm in some dire need of help with X386.  Any help would be much appreciated.
>>Here is my xdm-errors file.....
>>
>>X386 Version 1.2E 1.0.1  / X Window System
>>(protocol Version 11, revision 0, vendor release 5000)
>>error (pid 90): IO Error in XOpenDisplay
>>error (pid 88): Display :0 cannot be opened
>>X386 Version 1.2E 1.0.1  / X Window System
>>(protocol Version 11, revision 0, vendor release 5000)
>>error (pid 93): IO Error in XOpenDisplay
>>error (pid 88): Display :0 cannot be opened
>>X386 Version 1.2E 1.0.1  / X Window System
>>(protocol Version 11, revision 0, vendor release 5000)
>>error (pid 95): IO Error in XOpenDisplay
>>error (pid 88): Display :0 cannot be opened
>>X386 Version 1.2E 1.0.1  / X Window System
>>(protocol Version 11, revision 0, vendor release 5000)
>>error (pid 98): IO Error in XOpenDisplay
>>error (pid 88): Display :0 cannot be opened
>>error (pid 88): Display :0 is being disabled
>>
>   (stuff deleted)
>
>DITTO!!  I am also getting the above messages in the xdm-errors
>file.  I am trying to startup in 640x480 mode (I have an ATI Graphics
>Ultra card) so I have commented out the Chipset, Vendor, etc.
>lines of the Xconfig file.  "Modes" is left defined as 640x480.
>
>As soon as xinit starts (at the end of the startx script) my
>screen blanks, I get the Version info, and then nothing!  I
>can get characters to echo on the screen, but I get no
>usable response and am unable to recover without rebooting.

The current version doesn't support the ATI chipset.  The next release
will have support for the ATI SVGA chipset (but not 8514/A).  I

Contrary to what someone else posted, the current X386 will not drive
a generic VGA card in 640x480 (or any other resolution).

The next release (XFree86 1.1) will also have support for the Trident
8900C chipset, and will include a monochrome server that should run on
most generic VGA cards.  Support for 386BSD is also greatly improved.
This version is in beta-test at the moment, and will probably be released
at the end of the month.

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: stark@cs.sunysb.edu (Gene Stark)
Subject: Re: Program dies with FP Exception
Organization: SUNY at Stony Brook Computer Science Dept.
	<1992Sep13.083846.6134@fcom.cc.utah.edu>
	<1992Sep14.151555.12300@cs.few.eur.nl> <BuMMFx.Isq@Novell.COM>
Date: Wed, 16 Sep 1992 00:34:59 GMT

I had asked about why my program was dying with an FP exception.
I tried debugging again with a clearer head, and I found the problem source:
a typedef with an unintended type in the source code.  However, the
error should not have caused the exception--instead the program should
have performed a double to int conversion and continued happily.  This may
indicate a problem in the GNU C routine __fixdfsi.  If I get a chance
I'll try to track this down.  What seems to happen is that the conversion
from double to integer clobbers some locations it shouldn't be clobbering.
The offending source code looked like this:

------
typedef struct AST_float {
  int value;			/* I intended 'double' here */
} AST_float;

main()
{
  AST_float *bar();
  bar(3.0);
}

AST_float *AST_make_float(v)
double v;
{
  AST_float *f;

  f = (AST_float *) allocate(sizeof(AST_float)) ;
  f->value = v;			/* Here is where the type mismatch is */
  return(f);
}
From: scott@solids.phy.bnl.gov (david scott coburn)
Newsgroups: comp.unix.bsd
Subject: *** How to format BDS man pages ???? ***
Date: 11 Sep 92 20:29:30 GMT
Distribution: usa
Organization: Brookhaven National Laboratory   Upton, NY, USA


I have been trying (unsuccessfully) to format some BSD man pages
gotten from the archives on ftp.uu.net.  The files in question
are for the lpr/lpd stuff.  nroff -man does not seem to do the job.

Anyone have any ideas?

(This is one of my biggest gripes about nroff.  nroff files should
indicate somewhere within themselves which macro package they use.
But, anyway...)

Any help would be welcome.

Scott

scott coburn                                brookhaven national laboratory
scott@solids.phy.bnl.gov [130.199.128.73]                   upton, ny, usa
 .....q.. ...q.... ......q. q....... .......q .q...... ....q... ..q......
Newsgroups: comp.unix.bsd
From: bad@flatlin.ka.sub.org (Christoph Badura)
Subject: Re: [386BSD] tinyBSD Does not recognize QIC-02 Drive
Organization: Guru Systems/Funware Department
Date: Sat, 12 Sep 1992 20:07:55 GMT

In <92255.215952MHS108@psuvm.psu.edu> Mark Solsman <MHS108@psuvm.psu.edu> writes:

>TinyBSD does not recognize my Archive VP402 QIC-02 controller and
>Wangtek 5150EQ Drive.  I played around with the jumper settings, and none
>of the following made any differnce..

The VP402 and the Wangtek QIC-02 controller are not compatible. The
difference is minor though.

-- 
				Christoph Badura  ---  bad@flatlin.ka.sub.org

ISO? Nicht immer, aber immer M-vfter.
From: dmp3592@galileo.rtn.ca.boeing.com (Dean M. Phillips)
Newsgroups: comp.unix.bsd
Subject: Re: backup w/ compression for UN*X?
Date: 4 Sep 92 18:25:51 GMT
Organization: Boeing Commercial Airplane Group, Seattle

In article <1992Sep3.015437.15379@msuinfo.cl.msu.edu> paoletti@cps.msu.edu (David R. Paoletti) writes:
>Does anyone know of any software for UN*X, 386BSD or otherwise,
>that does on-the-fly compression?

I have used zip followed by zipsplit to do this.  This gives me one
complete, independent zip file per floppy.  The compression ratio of
zip tends to be better than compress.  It can also be told not to
recompress files which are already compressed.  The zip and unzip
programs were posted to comp.sources.misc and are also available via
ftp from agate.berkeley.edu and elsewhere.

The disadvantage of this approach is that you need enough free disk
space to build both the big zip file and the split zip files.  I have
handled this by backing up files in <gasp> related groups which has the
added benefit of making it easier to find things in the backups.

Has anyone hacked zipsplit to handle a sequence of raw floppies?
-- 
----------------------------------------------------------------------
#include <standard_disclaimer.h>
Dean M. Phillips                                        (206) 393-9333
Boeing Commercial Airplane Group            dmp3592@galileo.boeing.com
From: richard@pegasus.com (Richard Foulk)
Newsgroups: comp.unix.bsd
Subject: Re: AT&T Long Distance Boycott (was: BNR2SS, Mach, and The Lawsuit)
Date: 8 Sep 92 13:48:24 GMT
Organization: Pegasus,  Honolulu

>>That makes perfect sense, since they're hackerware. All they do is file
>>translation, and the only OS services they need are reading and writing
>>files.
>
>*sigh*
>
>Fine.
>
>trn (without networking) compiles without anything other than what is given
>in POSIX (if you throw in a termcap library, which can easily be provided
>with it and considered "part of the application").  And, last time I
>checked, trn was an application, even more so than a compiler and whatnot
>are.
>

A good example of the problem that half a standard (POSIX) creates!  Take
a look at just about any of the larger products that have crossed over
from the DOS world.  They all use their own incompatible version of a
termcap-like library.

A sad situation.


-- 
Richard Foulk		richard@pegasus.com
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: which X386 in agate is better?
Date: Wed, 09 Sep 92 18:39:54 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Keywords: X386

In article <1992Sep9.031159.13322@cucs5.cs.cuhk.hk> ko053@cucs11.cs.cuhk.hk (Patrick Ko) writes:
>I've the 386bsd up and running with 150M partition 
>with 20M DOS partition healthy.  TCPIP under ethernet
>card NE2000 with another DOS machine doing NCSA ftp
>things, fine. 
>
>Now I am going to get a copy of X386 and I found
>there are 2 directories that contain it. One is
>in /pub/incoming/X386 and the other is in /pub/386BSD/ports-0.1.
>
>Is there anybody who kindly tell me what are the
>differences between them? Which one should I get?
>
>Thanks for all you guys.
>

The /pub/incoming/X386 in agate is the latest relese of X386 (which
has been renamed to Xfree86). We are waiting for kernel patches and
this is the reason we have not release X386. As for the current
X386 in /pub/incoming from an X11R5 point of view is rock solid.
Feel free to read the release notes - it states all the bug fixes
done so far to the kernel and to X386. There has been many installations
using the /pub/incoming/X386 and have reported no problems to me.

The reason why I am posting this is that the net independent of me
has discover the release in /pub/incoming/X386.

And, don't ask me what kernel patches are forth-coming because I
don't know.


Hope this helps,
Amancio Hasty
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] cc1 fatal error & more!
Date: 11 Sep 92 15:15:05 GMT
Organization: Weber State University  (Ogden, UT)

In article <BuEAx4.JIq@mentor.cc.purdue.edu> rahnds@mentor.cc.purdue.edu (Dale Rahn) writes:
>is it possible that the -O option of gcc uses too much memory 
>(i have 8M real, 16M swap but have X386 running)
>or could there be a problem with gcc.

It depends on which X you are running.  Is your server binary the 11 Meg or
the 1 Meg flavor?

Seriously, since you have the test bed all set up ;-), try not running X
and redoing the compile.  I suspect that 24 Meg is too teeny to run the big
version of X and compile at the same time (considering the 11 Meg is the
size of the image without stack or locally allocated memory).


					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
-------------------------------------------------------------------------------
From: rahnds@mentor.cc.purdue.edu (Dale Rahn)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] cc1 fatal error & more!
Date: 11 Sep 92 03:55:51 GMT
Organization: Purdue University

In article <1992Sep11.012623.14965@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
>In article <6703@vtserf.cc.vt.edu> linkt@GroupW.cns.vt.edu (Tim Link) writes:
>>In article <0efk57e00WB60gg0pN@andrew.cmu.edu> tj2n+@andrew.cmu.edu (Tao Jiang) 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.
>
>I used to get around the problem by doing:
>
>	make -n > foo
>	vi foo
>	sh foo

I have been having this problem getting MetaFont to compile.
While using Terry's solution I found that the program would not
compile using the command line from the shell but did compile
when i left off the -O option, it compiled correctly

gcc -g -O -I.. -c mf1.c
gcc: Program cc1 got fatal signal 6.
*** Error code 1

but

gcc -g -I.. -c mf1.c
returns with no errors and creates mf1.o
which will compile and link with no errors.
is it possible that the -O option of gcc uses too much memory 
(i have 8M real, 16M swap but have X386 running)
or could there be a problem with gcc.

The problem was fixed with a patch to the code which reduced various
arrays in the program. but this was not useful to me (it did not allow
all of the characters for some fonts.

Dale Rahn
rahnds@mentor.cc.purdue.edu
Newsgroups: comp.unix.bsd
From: casper@fwi.uva.nl (Casper H.S. Dik)
Subject: Re: Shared Libs for X11?, was Re: 386bsd -- The New Newsgroup
Organization: FWI, University of Amsterdam
Date: Tue, 15 Sep 1992 15:01:39 GMT

veit@du9ds3.uni-duisburg.de (Holger Veit) writes:

>This is what I originally intended; I'm just sitting in front of a Sparc,
>and curiously watch what it is doing...:-). There are two possible problems:
>1. What will Sun say about using (or reverse-engineering) their solution
>   (in the light of AT&T vs. BSDI/UCB...)?

There is no reverse engeneering involved in AT&T vs BSDI/UCB. For one,
BSD had access to AT&T source code. I haven't heard Sun complaining
about anyone using/reimplementing the things they created.

>2. It is rumoured that the whole Sun DL stuff depends on or contains 
>   self-modifying code, which caused/s problems with SunOS look-alikes 
>   like Solbourne OS/MP (was fixed by some strange patch in OS/MP). I don't
>   know whether this is needed (I suppose, not), but it make me think that
>   this can be not a clean solution.

All dynamic linkiung will probably have some sort of ``self modifying code''
problem. The dynamic linker will have to patch the code somewhat.

If there was a problem on Solbournes that didn't exist on Suns than
that can be easily explained.  The SPARC based machines shipped by Sun
all had a unified I&D cache (The SS10 changes that, however).
Solbournes ships machines with a split I&D cache. This gives some
problems if you code. The solution is simple, flush the cache after
you're done with linking.

There are a number of problems with the shared library implementation in
SunOS 4.x. Although the construction of shared libraries seems easy enough,
breaking the rules isn't easily detected and costs a fortune in VM.

Casper
-- 
						|	Casper H.S. Dik
						|	casper@fwi.uva.nl
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386BSD] Install Query
Organization: Weber State University  (Ogden, UT)
Date: Sat, 5 Sep 92 23:43:33 GMT

In article <Bu1u5v.F7C@ibmpcug.co.uk> adrian@ibmpcug.co.uk (Adrian Hall) writes:
>What amount of swap space is configured into the kernel/disk by
>the install script?

5 Mb.  This is in the install notes.


					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
From: jlu@cs.umr.edu (Eric Jui-Lin Lu)
Subject: Questions:  X server, the patched kernel, and ....
Date: Thu, 10 Sep 1992 00:46:44 GMT
Organization: University of Missouri - Rolla
Originator: jlu@mcs213i.cs.umr.edu


Greetings *,

I fetched the X server and the patched kernel for X from
pub/incoming/X386.  I found that ps works correctly with the patched
kernel.  However, I have some questions:

1.  What kind of patches were put into this kernel?
2.  The X server is roughly 1MB while the X server I got from
    pub/386BSD/0.1-ports/X386 is roughly 11 MB.  In other words,
    the debugging info is around 10MB.  Am I correct?
3.  Is there a way to split the files so that it'll fit into
    either 1.2M or 1.44M floppies?
4.  Except that the X server from pub/incoming/X386 is more stable,
    do I have to get the rest bin, inc, lib, etc. files?  Can I
    use the files from /pub/386BSD/0.1-ports/X386?

Thanks in advance!  You can either post the answer here or email
me at jlu@cs.umr.edu.


   --Eric
-- 
***************************************---       Grad. student          ---*
* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
***************************************---   Univ. of Missouri-Rolla    ---*
From: gab10@griffincd.amdahl.com (Gary A Browning)
Newsgroups: comp.unix.bsd
Subject: Shared Libs for X11?, was Re: 386bsd -- The New Newsgroup
Keywords: shared libraries X X11
Date: 11 Sep 92 03:20:36 GMT
Organization: Amdahl Corporation, Sunnyvale CA

In article <veit.716107923@du9ds3>, veit@du9ds3.uni-duisburg.de (Holger
Veit) writes:

[ stuff about naming new newgroup deleted ]

> >For example, shared libraries are quite easy to "hack in" (just look at
> >Linux), and for some systems that is probably the best approach -- just
> >get it in there and going. However, there are several considerations that
> >must be dealt with before putting in such a feature. Expedient approaches
> >can result in a long-time legacy that is difficult to support and even
> >impedes new progress in related areas.
> 
> Currently I'm still "hacking" at pccons (will be called "co"nsole
> driver next),
> but my next goal is quite clear: I want to have the disk space back
> that is
> currently used by statically linked X apps (=> shared libs). We should
> talk 
> about that in another *thread*. 

Ok, this is another thread. ;-)

I just finished installing X and noticed that most binaries are several times
larger than expected due to the lack of shared libraries.  I caught an article
posted here a few days back that quickly described the SysVr3 approach of using
fixed addresses for the libraries and the Sun/SysVr4 approach of using position
independent code.

I tend to dislike the SysVr3 method since I got the impression that the source
code had to be written differently (though I am not sure why).  I also noted
that the GCC-2.2.2 compiler I just got compiled can produce PIC code which
would be one of the major hurdles for the SysVr4 method.

Any knowledgable person want to talk a little more about the pros and cons of
these two (or any other) approach?

Anyone kept up with the Linux discussions of shared library implementations?
Can you summarize?

What ever happened to the Jolix's special interest groups?  Wasn't one of them
addressing the shared library problem?

-- 
Gary Browning        | Exhilaration is that feeling you get just after a
		     | great idea hits you, and just before you realize
                     | what is wrong with it.
From: asah@cory.Berkeley.EDU (SAH Adam)
Newsgroups: comp.unix.bsd
Subject: Looking for BSDI info...
Date: 13 Sep 92 11:08:11
Organization: Organization is a necessary evil.
Distribution: world
NNTP-Posting-Host: boa.cs.berkeley.edu


I'm looking for references to BSDI's UNIX.  What I'm looking for:

1. Pros/cons/reviews from people who USE IT.  Specifically, 
	a. how is the multi-tasking performance under load (ie. trying to 
		use it interactively while a compile is happening in the 
		background).  
	b. how are real X-apps on a 486/33 running it from a SCSI disk 
		(ie. Wordperfect, spread-sheets, etc.).
	c. how reasonable is the X server on a non-local bus machine vs.
		a local bus machine at high res (>= 1Kx800x8 bits)?
		Can you run twm in opaque mov mode and it be 'smooth'?

2. An updated list of supported hardware.

3. How I can contact BSDI directly.

Please respond by email to 'asah@cory.Berkeley.EDU' or to this account.
  I will post a summary.

Thanks in advance.

Thanks again,
-A.Sah'92

Newsgroups: comp.unix.bsd
From: goran@astro.uu.se (Goran Hammarback)
Subject: Re: How to lowlevel-format floppies ?
Keywords: floppies,formatting
Organization: UDAC, Uppsala, Sweden
Date: Wed, 9 Sep 1992 08:29:16 GMT

In article <hahn.715972931@ios>, hahn@ipk.fhg.de (Uwe Hahn) writes:
|> Is there anybody, who can tell me how to lowlevel-format floppies under 
|> 386BSD ? The mtools only offer to highlevel-format floppies and I know of 
|> fdformat or format on SunOS or SysV-PC-Unixes. 
|> 
|> Is there such a tool under 386BSD (Jolix) ?

No, there isn't one in the ordinary distribution, and unless someone
has fixed this (I think you need to add lowlevel-format capability to
the fd driver) you have to boot DOS to format floppies.
-- 

Goran

------------------------------+---------------------------------
Goran Hammarback              |     goran@astro.uu.se
Astronomiska Observatoriet    |
Uppsala Universitet           |
S-751 20 SWEDEN               |
------------------------------+---------------------------------
From: richard@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.bsd
Subject: Re: Some more on NMI problems (some meager advancement)
Date: 8 Sep 92 12:49:16 GMT
Organization: AIAI, University of Edinburgh, Scotland

In article <1992Sep7.014351.946@ponds.uucp> rivers@ponds.uucp (Thomas David Rivers) writes:
>Well, I thought I would relay my current status with the NMI
>investigation.

I had a problem with spurious NMIs that was solved by removing the
halt instruction from the idle loop.  It's been suggested that the
reason for this is that memory is not being refreshed while the
processor is halted.

-- Richard
-- 
Richard Tobin,
AI Applications Institute,                                R.Tobin@ed.ac.uk
Edinburgh University.
Newsgroups: comp.unix.bsd
From: david@mlb.geomechanics.csiro.au (David Le Blanc)
Subject: Re: 386BSD hangs
Organization: CSIRO DIT (Melb.)
Date:  5 Sep 92 04:54:14 GMT

hell@desert.in-berlin.de (Steffen Hellwig) writes:

>Hallo world.
>I've some problems running 386BSD on my 386 40MHZ with an ADAPTEC 1542A
>I've installed 386BSD sucsessfully on a Fujutsu M2624FA SCSI Disk and every 
>thinks works fine.
>But sometimes, most often during heavy disk-io, the machine hangs without
>any comments.

>Anyone else noticed that strange thing?

I have had that happening. It usually happens when I do two large things
such as run GCC twice while under Xwindows.. The swapping will halt, and
the machine will go quiet. And stay that way.

Also, I have had problems where while swapping the IDE drive (which has
the swap partition, I have /usr files on a 'D:' SCSI drive (adaptec 1542b))
will pause, with the activity light on solid for maybe five seconds, then
resume. Any ideas?

>Bye.
>-- 
>hell@desert.in-berlin.de (Steffen Hellwig)
--
David Le Blanc                         :
Email: david@mlb.geomechanics.csiro.au : `Sort of a cross between a Jaguar
CSIRO Division of Geomechanics,	       :  and a freight train.' the Alien
P.O. Box 54 Mt Waverley 3149	       : in Alien^3.