HDTenEightyP/NetNews huggingface dataset:
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] cc1 fatal error
Date: 12 Sep 92 10:15:13 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

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

>Tao Jiang <tj2n+@andrew.cmu.edu> 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

>>I could not figure out what's wrong with it.

>>Any help will be greatly appreciated!

>>TJ

>try to compile without -O. i had the same problem on metafont (mf1.c)
>and there it worked without the optimizer.

>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 

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

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"
Newsgroups: comp.unix.bsd
From: pk@cs.few.eur.nl (Paul Kranenburg)
Subject: Re: 386bsd: elvis won't compile
Reply-To: pk@cs.few.eur.nl
Organization: Erasmus University Rotterdam
Date: Fri, 11 Sep 1992 11:07:50 GMT

In <BuA04M.J6H@ibmpcug.co.uk> adrian@ibmpcug.co.uk (Adrian Hall) writes:

>In article <1992Sep8.185716.23623@hippo.ru.ac.za> ccml@hippo.ru.ac.za (Mike Lawrie) writes:
>>In /usr/src/usr.bin/elvis, I type "make" and end up with the message
>>
>>	make: obj: No such file or directory
>>
>>There is a link /usr/src/usr.bin/elvis/obj->/usr/obj/contrib/elvis-1.5,
>>but there is not even a directory /usr/obj/contrib.
>>

>Ummmm

>	mkdir -p /usr/obj/contrib/elvis-1.5

>Seriously though (sorry if I assumedyou didnt know the usage of the
>mkdir command!), there are a lot of directories under /usr/othersrc
>which ask for obj dirs and do not have one. The appropriate mkdir -p
>clears it up, so it is no great problem.

There is a related problem with make if you try to overrule the object
directory by setting the environment var MAKEOBJDIR. If I set it to "."
(doing "setenv MAKEOBJDIR ." or just "setenv MAKEOBJDIR"), make will
erroneously set its variable ${.CURDIR} to "..", causing a number of
Makefiles to get confused. A look at the code (right at the beginning
of main()) reveales that any value of MAKEOBJDIR that does not evaluate
to a subdirectory of the current directory (in which make was started)
will cause this error to show up.

A quick fix would be to change the line (#358, main.c)
	if (S_ISDIR(sb.st_mode))
to
	if (S_ISDIR(sb.st_mode) && !strcmp(path, _PATH_OBJDIR))

-pk
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD & COMPAQ 486/33
Date: 8 Sep 1992 17:45:21 GMT
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu

In article <1992Sep8.023138.25145@super.org> rminnich@super.org (Ronald G Minnich) writes:
>In article <1992Sep7.112452.5403@csd.uch.gr> kanagn@ikaros.cc.uch.gr (Kostas Anagnostakis) writes:
>>I tried to boot 386BSD on a COMPAQ 486/33 / 4 MB RAM but it didn't work.
>>It didn't even get to the "386BSD etc" notice. Has anybody out there gone
>>into the same problem ? 
>
>as things currently stand compaq's won't boot it at all. any compaq. ...

It's quite frustrating. We have an old Compaq greyface (386/20) (courtesy
of Compaq) and it works just fine, but it was a "lab special" and hence 
may not be fully representative of all of Compaq's product line.  Now if 
Compaq would just send us an updated model, or better yet one of the new 
notebooks, we would finally be able to figure out what's going wrong...

Lynne.
From: allard@isi.edu (Dennis Allard)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd -- The New Newsgroup
Date: 11 Sep 92 00:29:44 GMT
Reply-To: allard@isi.edu (Dennis Allard)
Distribution: world
Organization: USC Information Sciences Institute
Keywords: newsgroup 386bsd news group

wjolitz@soda.berkeley.edu (really Lynne Jolitz) writes:
> The subgroups kernel, windows, sharedlib (for shared libraries, Holger) and
> net (for networking) are actually research/development topics, and have 
> been of intense interest to those who wish to participate in developing 
> these areas further.

The attempt I am seeing here to a priori categorize content is doomed
to fail.  The reason threads exist is because dynamically created
discussions come and go and have a natural lifetime (and death).  The
cross indexing problem across the proposed subgroups will be tedious.
Maybe the 'keyword' field is where these categories should be
mentionned.  Note how 'well' that has worked in the past :).  The
current volume of traffic does not justify splitting things only based
on volume, and it is a pipe dream to assume that the proposed
subgroups are either complete or consistent.

Note, USENET is not the place for project management.  Private email
and mailing lists are.  General discussions of 386bsd shared
libraries, gigabyte networking, and the other open ended set of 386bsd
related topics which will arise belong in as few newsgroups as
possible.  In the case of gigabyte networks, that place need not have
anything to do with 386bsd, by the way, except in so far as it deals
with 386bsd implementation issues.

> It depends. If you find a bug but not the solution, you post to "bugs".
> If you find the fix, you post to "ann".

Too complicated.  People interested in bugs are also interested in
fixes.  "bug xyz" and "Re: bug xyz" appearing close to each other in
a threaded newsreader is preferable.

Occam's razor indeed should be carefully applied here.

sincerely,
Dennis G. Allard
allard@isi.edu
Newsgroups: comp.unix.bsd
From: u009@csx.cciw.ca (G. Stewart Beal)
Subject: [386bsd] Trap 19 suggestions wanted
Organization: Canada Centre for Inland Waters
Date: Tue, 8 Sep 1992 15:46:20 GMT
Keywords: 386bsd panic trap 19 motherboard memory problems AMI bios OPTI CONTAQ

Has anyone sucessfully started up a system which gave an initial Trap 19?
The only message I could find recently was from Lynne(?) indicating a
memory fault might be the culprit due to poor initialization of the
extended memory or a conflict with the expanded emm.
I have tried testing and ignoring, shadowing and not all the memory on
a couple of different 386-40 boards, one with an OPTI chipset, the other
with one by CONTAQ. Both boards had AMI bioses(sp) and both gave trap 19
errors all the time. Any suggestions? I can't find any info in the FAQ.
Regards, Stu Beal,. VE3MWM, U009@cs.cciw.ca
Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Subject: Re: Problem with 386BSD and Network
Organization: University of Western Ontario
Date: Sat, 5 Sep 1992 22:20:01 GMT

nyse@nicedel.north.de (Hermann Behrens) writes:

> 
> ne0 ethernet address 00:00:4d:21:65:97 at 0x300 irq9 on isa
> 
> ?? I installed ther card on all available IRQ's(2,3,4,5,12) but it
> will always be detected on IRQ 9. Then I type the following:
> 
> >ifconfig ne0 192.1.1.2		# I type in
> <neinitstartartstartart		# 386BSD answers
> >route add default 192.1.1.10 (The IP-Number for my 2nd computer).
> 

I have a wd elite 16 on irq 2, and the machine comes back as irq 9 also.
But mine works ok.

ifconfig ne0 192.1.1.2 255.255.255.0       (net mask is required?)
route add default 192.1.1.10

If you want name serving, create   /etc/resolv.conf
and put the lines:

nameserver 192.1.1.10
domain myhouse.de

If your machine was called  machine.myhouse.de   then   ftp myhouse would work
if the name server was running.

I was able to ftp everywhere within 2 minuntes of loading the 10 bindist
disks, by typing the above 2 commands (my numbers were different of course)

mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Western Business School  --  London, Ontario
From: adrian@ibmpcug.co.uk (Adrian Hall)
Newsgroups: comp.unix.bsd
Subject: Disk Distribution and FTp Archive
Date: 9 Sep 92 10:35:55 GMT
Organization: The IBM PC User Group, UK.

The IBM PC User Group (in Harrow, London), is now distributing
the latest 386BSD distribution on disk (3.5 and 5.25" formats).
The cost (ouch!) for the full distribution is charged at 1 UKP
per disk. (I should point out that this is a quarter of our normal
shareware distribution cost!). To order a copy, send (snail) mail
to :-

	Shareware Distribution
	The IBM PC User Group
	PO Box 360
	Harrow
	London
	(England)

	stating which format you require, and enclosing a cheque
	for 50 pounds drawn on a UK bank. For UK people, you will
	have to add VAT to this.

In addition, the new 386BSD machine that the PC User Group is running
is now acting as an ftp archive. I have put the unpacked /usr/src up
for grabs. I am *NOT* holding the distribution on-line (sorry - the
machine is only a 386SX!), but the files held are kept up to date with
the latest patches, so you will find the sources with working versions
of all patches already built into them.

Adrian

-- 
--------------------------------------------------------------------------
Adrian Hall					Connect Systems Manager
adrian@ibmpcug.co.uk				The IBM PC User Group
Tel: +44 81 863 1191				Harrow, London, UK
Newsgroups: comp.unix.bsd
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Subject: who does not show all users 
Keywords: com.c.cgd patch who 
Reply-To: kuku@acds.physik.rwth-aachen.de
Organization: I.Physikalisches Institut RWTH-Aachen
Date: Sun, 13 Sep 92 17:24:25 GMT


After having (successfully ) applied the com.c (CGD) patch I'm now able to log
into my 386BSD system from home via dial-in.

When I do a 'who' from such a dial-in session I don't see myself in the
list of users.

Is this a known problem or is my system messed up?

--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
 
Stop.
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: cross compiling on a Sparc for 386bsd
Date: 7 Sep 1992 21:27:51 -0500
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu

Okay, I've got a gcc 2.2.2 cross compiler set up on my SS-1 that
generates good 386 code.  I've got gas set up to assemble that code
and create an object file.  However, I can't link the object file.
All of the GNU binutils give me "malformed input (not a rel file or
archive)".  I'm assuming the little endian, bit endian difference is
what's getting me.  My question is this, is it possible to get ld
and assorted friends to work with 386 code on a SS-1?  Or, do I have
to just copy the .o files over to my 386 box and link them there?

++Brett;

Newsgroups: comp.unix.bsd
From: mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Subject: Re: X386 Installation Woes
Organization: University of Western Ontario
Date: Tue, 15 Sep 1992 01:18:19 GMT

randy@chinet.chi.il.us (Randy Suess) writes:

> In article <g7xnmdp@lynx.unm.edu> meissner@triton.unm.edu (John Meissner) wri
> >After obtaining the X386 release from agate.berkeley.edu (/pub/incoming/X386
> >I find that I am unable to make it do anything after performing the steps
> >it follows with an error message to the effect 'fatal server error, cannot
> >load default font 'fixed''.
> 
I had a simular problem with fonts missing.  I grabbed them from the 
older X386 on agate.
> 	Look at your Xconfig file for where the fonts are set.
> 	Bet they have the Speedo, or outline stuff defined but
> 	the supplied font.tar does not contain them.
> 	Just remove the definition from Xconfig.
> 
> -- 
> 	I am created Shiva the Destroyer; Death, the shatterer of worlds!
> 	Who is this dog meat who stands before me now?
> 	That's the biz, sweetheart.
> Randy Suess					 randy@chinet.chi.il.us


mark@student.business.uwo.ca (Mark Bramwell CS Staff)
Western Business School  --  London, Ontario
Newsgroups: comp.unix.bsd
From: ccml@hippo.ru.ac.za (Mike Lawrie)
Subject: Re: 8Mb stability patches DESPERATELY needed!
Organization: Rhodes University, Grahamstown, South Africa
Date: Sat, 12 Sep 1992 19:28:40 GMT

In <18ip3rINNg2m@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:

>In article <1992Sep8.062725.9038@marlin.jcu.edu.au> cejjb@marlin.jcu.edu.au (Jeffrey J Bird) writes:
>>I am in very desparate need of the patches that stop 386BSD 0.1
>>freezing when there is more than 8Mb of memory in the machine.

>This is a buffer cache problem, dealing with fragmentation of an internal
>resource. The fix for this, the "panic kmem" problem, and the resulting
>instability are to insert the following line before line 171 ("if(nbuf==0)..")
>of machdep.c:

>	bufpages = min (NKMEMCLUSTERS/2, bugpages); 	/* XXX */

>The real solution to this and other problems is related to 0.2 new work.

Even with /bugpages/bufpages as in a kernel patch from somewhere, my 8Mb
386 still hangs when it is very busy (eg executing make in
/usr/othersrc/share).

Anyone else with a fix or a pointer in the right direction?

Mike
-- 
Mike Lawrie                                    <ccml@hippo.ru.ac.za>
Director, Computing Services                   ph +27 461 22023 x 279
Rhodes University, Drostdy Rd                  fx +27 461 25049
Grahamstown 6140, South Africa
Newsgroups: comp.unix.bsd
From: bcrawfor@sol.UVic.CA (Bryan Crawford)
Subject: booting 386bsd from the install floppy
Organization: University of Victoria
Distribution: all
Date:  8 Sep 92 17:51:52 GMT

I'm having problems installing 386bsd: it won't
boot from floppy on my pc; I tested the boot
disk I made on a friend's machine, and it workjed
fine, so the rawrite worked OK. My machine is:
	386/25 with no cache
	AMI BIOS (dated 04/09/90) and with a 'K8'suffix
		on the serial number (a revision, I think)
	10 Mb RAM
	IDE drive and one floppy (3.5")

Nothing happens at all: no banner after the BIOS info
box.

Do I have the well known AMI BIOS that really sucks that
everyone in the comp.os.* groups always complains about??

Any suggestions??

Please reply by posting or by email, at your convenience.

thanks,

Pat Dowler
dowler@otter.phys.uvic.ca
.

C
C
A

-- 

bcrawfor@Sol.UVic.CA  -- member of the society for simple .signatures (SSS)
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] cc1 fatal error & more!
Date: 12 Sep 92 09:39:07 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

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.

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"
From: brad@cuba.cayman (Brad Parker)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD hangs
Date: 11 Sep 92 14:44:23 GMT
	<1992Sep8.190240.23921@hippo.ru.ac.za>
Organization: You must be kidding...
In-reply-to: ccml@hippo.ru.ac.za's message of 8 Sep 92 19:02:40 GMT

In article <1992Sep8.190240.23921@hippo.ru.ac.za> ccml@hippo.ru.ac.za (Mike Lawrie) writes:

   >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.

   Similar experience here. Do two large "makes" of libraries and binaries
   from separate telnet sessions, and the system reboots every now and
   again. Bit of a curse, as it does not recognise the WD enet card at
   reboot unless I press the hardware reset button.

I did some *very* simple testing and found that the system initially slows
way down and the stops if you run out of swap space.  (I really wanted
pstat -s at the point ;-)  Anyway, I looked around but was unable to
find any swap space stats gathering, so I gave up.

Does anyone know of or have any fixes for running out of swap space
gracefully?

-brad
--
A metaphor is like a simile.

Brad Parker	Cayman Systems, Inc., Cambridge, Ma.	brad@cayman.com
From: eichin@athena.mit.edu (Mark W. Eichin)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd & timezone
Date: 11 Sep 92 09:16:16 GMT
Distribution: usa
Organization: Massachusetts Institute of Technology

>> My solution was just to set the CMOS information to reflect standard
	Has anyone made changes to get 386BSD to update the CMOS time
from the kernel time? xntp3 builds and works out of the box, but if
the CMOS time drifts far enough, at the next reboot xntpd will declare
that "something is wrong" and won't try to fix it.
				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
From: adam@micromuse.co.uk (Adam Kerrison)
Newsgroups: comp.unix.bsd
Subject: Mounting DOS filesystems in 386BSD
Date: 9 Sep 92 11:36:55 GMT
Reply-To: adam@micromuse.co.uk
Organization: MicroMuse Ltd, London, Uk

Can you mount DOS filesystems/partitions in 386BSD (like you can in SunOS
using mount -t pcfs) ?? If so how ??

If not (which is what I expect) - is it likely to be included in a future
release ?? Is anybody working on it ?? If they are do you need a hand ??

I will have a look at this if noone else is doing it as I may find it useful.
Since BSD runs on Intel boxes (which usually run DOS) it would seem sensible 
to let you transfer data between the two systems.

As an after thought, I know that VPIX runs DOS apps but does it use the DOS
partitions or are the programs stored on the BSD partitions ??

Any information on these subjects would be useful ....
Thanks

Adam

---
===========================================================================
Adam Kerrison                  | Phone : +44 71 352 7774
Technical Support              | Fax   : +44 71 351 7834
MicroMuse Ltd                  | E-mail: adam@micromuse.co.uk
London SW10 0RN                | 
===========================================================================
"When you kill a man, you're a murderer. Kill many, and you're a conqueror.
Kill them all, you're a god !" - Think about it
===========================================================================
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: Tue, 08 Sep 1992 19:18:20 GMT

In article <1992Sep8.164622.21761@gateway.novell.com> terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert) writes:
>	What about the termcap file itself?  

Hate to tell you this, but I have seen applications that came with their own
termcap (or termcap equivalent) file.  Yes, the whole thing.

Next complaint?

>	VMS doesn't support the concept of SUID/SGID necessary from most
>things, like score files in games.  Instead, you have to install the image
>with priveledges (ie: I can't make an SUID "terry" program; only an SUID
>SYSTEM with some priveledges).

Gosh.  Then I guess the fact that such things were in the last VMS I checked
was my imagination, huh?  Yes, amazing as it seems, the POSIX work done to
VMS is real, and it works, and it does make it look a lot more like a UNIX
system.

>	The total lack of a CBREAK mode disallows single character I/O,
>unless you are willing to call SYS$QIO() directly.  Raw mode requires a
>QIO with IO$_SENSEMODE/IO$_SETMODE.

Here's another concept you and Peter seem to be missing:  wrapper libraries.
The VMS POSIX stuff has termios, which allows single character I/O the same
was as on a SysV system (well, kinda).

>	o	Open a file created with a text editor (this will insure
>		it is a variable length record file with implied carriage
>		return carriage control).
[deleted]

Works fine.  Oh?  Don't you use the correct port of emacs?

>	MMDF (Multi-Memorandum Distribution Facility) ... OK, it stinks, but
>it's what you asked for.

trn works with mmdf.  I haven't stuck the code in trn yet, because there
isn't a need.  Note that MMDF won't work on a lot of systems because it is
highly UNIX dependent, and if you claim a POSIX-dependent application isn't
going to work on a non-UNIX system, then I don't see how you can think that
something like MMDF will.  (Networking?  IPC?  fork() and exec()?  setuid()?
seteuid()?  Huh?  What are those?)

-- 
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.
Newsgroups: comp.unix.bsd
From: hbj@engr.uark.edu (Bernard Johnson)
Subject: Re: Colorado Memory Systems tape drive
Keywords: CMJ, Jumbo, DJ-20
Organization: University of Arkansas
Date: Tue, 8 Sep 1992 04:41:42 GMT

ken@sugra.uucp (Kenneth Ng) writes:

>Got the number or an address of some kind I can give to information?  Calling
>411 and saying "I'm looking for the number for Quarter Inch Standards, somewhere
>in the United States, although it might be elsewhere."

Quarter-Inch Cartridge Drive Standards, Inc.
311 East Carrillo Street
Santa Barbara, California  93101
Telephone:  (805) 963-3853
Fax:        (805) 962-1541

Bernard Johnson
hbj@engr.uark.edu
Newsgroups: comp.unix.bsd
From: terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert)
Subject: Re: 386BSD #!/bin/csh
Organization: Novell NPD -- Sandy, UT
Distribution: comp
Date: Thu, 10 Sep 1992 15:54:31 GMT

In article <61Ld025621cR01@JUTS.ccc.amdahl.com> gab10@griffincd.amdahl.com (Gary A Browning) writes:
>In article <1992Sep9.171327.20998@gateway.novell.com>,
>terry@thisbe.Eng.Sandy.Novell.COM (Terry Lambert) writes:
>> In article <TRI.92Sep9011202@supergirl.hut.fi> Timo.Rinne@hut.fi
>> writes:
>> >386bsd 0.1 doesn't seem to respect #! in beginning
>> >of the shell scripts, Anyone knows why? Fixes?
>> 
>> Instead of:
>> 
>> 	#!/bin/sh
>> 	#
>> 	...
>> 
>> use:
>> 
>> 	:
>> 	#
>> 	...
>> 
>> This will result in invocation of /bin/sh.  Sorry; no workaround known
>> to make it execute csh instead.
>
>I thought there was a patch for this in the X386 (XFree86) 1.0.2a distribution.

	There is; but it requires recompilation of the kernel (the patch is
to kern_execve.c).  Recompiling the kernel is unacceptable to most people.
What I gave was a workaround, and there is no similar workaround for the
csh.

	The patch also causes security problems (ie: SUID shell scripts
and anyone able to shut the machine down) unless other patches are applied
at the same time (and these *don't* come with the X stuff).


					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.
Newsgroups: comp.unix.bsd