HDTenEightyP/NetNews huggingface dataset:
From: david@mlb.geomechanics.csiro.au (David Le Blanc)
Newsgroups: comp.unix.bsd
Subject: Re: Compiling 386bsd-0.1 on < 40Meg ( I've done it)
Date: 31 Aug 92 00:12:39 GMT
Organization: CSIRO DIT (Melb.)

terry@cs.weber.edu (A Wizard of Earth C) writes:

>In article <colin.715158768@marsh> colin@marsh.cs.curtin.edu.au (Colin Manning) writes:
>>	Now that I've compiled the kernel, how do I make a bootable floppy?

>	I need to put this in the FAQ.  The procedure is as follows:

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

Your procedure is perfectly good for creating a copy of the dist.fs with
a new kernel. 

As for the more generic question of :How do I make a bootable floppy :-


Put the floppy in (say /dev/fd0a) drive a.
type 'newfs /dev/fd0a floppy'

mount /dev/fd0a /mnt
copy /.../386bsd /mnt/386bsd

(copy on any other utils you will/may need such as init)

umount /mnt

The trick here is simply that typing 'newfs /dev/fd0a floppy' puts a
file system on the floppy, and AUTOMATICALLY places boot code on the
floppy disk. As long as /386bsd exists on the floppy, it will boot!


>---
>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
>-------------------------------------------------------------------------------
--
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.
From: michael@resonex.com (Michael Bryan)
Newsgroups: comp.unix.bsd
Subject: Re: time for comp.unix.bsd.386
Date: 27 Aug 92 09:16:07 GMT
Organization: Resonex Inc., Sunnyvale CA

In article <1992Aug27.122244.23194@prism.poly.edu> kapela@prism.poly.edu (Theodore S. Kapela) writes:
>Read the INSTALL.NOTES with the 386bsd 0.1 distribution.  It reads:
>
>	On the INTERNET/USENET, we are hoping to establish our
>	own  newsgroup called "comp.os.386bsd". This newsgroup would
>	reside  alongside  the  "comp.os.mach"  and  "comp.os.linux"

Well, this is what the Jolitz' want.  But do they have ultimate say in
what newsgroup gets created?  No --- the general net population does.
It's fine for them to suggest and support a particular name, but they
can't create it just because they are responsible for the code.  If
the net majority opinion is such that comp.os.386bsd is the desired
name, then so be it.  However, using their Release Notes as *the*
reason for a name is not good enough, IMHO.

Personally, I rather like Peter's recent suggestion of comp.os.posix.*
as a place for 386bsd and other POSIX-based systems.  It provides a
general heirarchy to encompass all UN*X-ish systems, yet doesn't use
the name UN*X itself, which appears to be the Jolitz' main concern
with comp.unix.bsd.  Future UN*X-like O/S additions will easily fit
under this tree, whether or not they have AT&T/USL code in them.

So let's see.  We now have various suggestions:

        comp.os.posix.386bsd
        comp.os.unix.386bsd     [I really don't think this one will fly]
        comp.os.386bsd
        comp.unix.bsd.386bsd

Any others? ;-)

-- 
Michael Bryan        michael@resonex.com                     |     ,_,
Milk and Cheese in '92!!!                                    |    /oo \
"What the world needs now are some true words of wisdom,     |    <>__|
like 'La-la-la-la-la-la-la-la-la-la'."  -- Cracker           |    |  U|
Newsgroups: comp.unix.bsd
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Subject: Re: adaptec scsi error,sendmail error
Date: 31 Aug 92 08:30:40 GMT
Reply-To: veit@du9ds3.uni-duisburg.de
Organization: Uni-Duisburg FB9 Datenverarbeitung

In <Btnu1D.Fz@ibg1.ibg.sub.org> ado@ibg1.ibg.sub.org (Christoph Adomeit) writes:

>Hi Freaks,

>2 )
>I don't have any sendmail experience. My sendmail always complains that
>there is no "frozen config file sendmail.fc". I only have a "sendmail.cf".
>Any idea about how to generate a "sendmail.fc" ?

/usr/sbin/sendmail -bz

>Thanks
>Bye
>	Christoph
>-- 
>Origin: It's not a bug, it's a feature !

Holger

-- 
|  |   / 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"
Xref: sparky comp.unix.bsd:4967 comp.sources.wanted:4174 comp.unix.sysv386:13902
From: jrh@mustang.dell.com (Randy Howard)
Newsgroups: comp.unix.bsd,comp.sources.wanted,comp.unix.sysv386
Subject: Re: lockd sources
Date: 1 Sep 92 21:49:12 GMT
Organization: Dell Computer Co

damon@netcom.com (Damon Skaggs) writes:


>I have having terrible problems slowness problems in lockd.  Is there
>any PD implementation of lockd available to see if I can figure out 
>what is going on?  BTW, does BSDI have lockd?

This is a well-known problem with the USL lockd.  It is very slow, and 
in a lot of cases, broken.  I think all SVR4 vendors will have this 
problem unless someone has managed to fix it.

-- 
Randy Howard            _o	    @'s: jrh@dell.com
Dell Computer Corp.     \<,	    !'s: ...!uunet!dellunix!jrh
______________________()/ ()______________________________________________
Superusers should wreak havoc only by accident.
-- Maurice J. Bach "The Design of the UNIX Operating System"
Newsgroups: comp.unix.bsd
From: stripes@pix.com (Josh Osborne)
Subject: Re: [386BSD]
Organization: Project GLUE, Merriversity of Uniland, College Purgatory
Date: Sat, 29 Aug 1992 15:52:14 GMT

In article <p5tullo@sgi.sgi.com> rpw3@rigden.wpd.sgi.com (Rob Warnock) writes:
[...]
>Although an excellent work, KA9Q's "NOS" is not needed in 386bsd, which
>already has full Berkeley networking built in. See the man pages for
>rlogin, rsh, rcp, ftp, telnet, socket, etc.

But I don't think 386BSD _currently_ has support for PPP, or AX.25 (and
there may be a few other things 386BSD doesn't have), also NOS seems to
lose way fewer charactors at high speeds.  Hopefully we can fix all that,
but for the moment "NOS is not needed" isn't quite true...
-- 
           stripes@pix.com              "Security for Unix is like
      Josh_Osborne@Real_World,The          Multitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
We all agree on the necessity of compromise.  We just can't agree on
when it's necessary to compromise.       - Larry Wall
From: eje@irenaeus.mlo.dec.com (Eric James Ewanco)
Newsgroups: comp.unix.bsd
Subject: Re: su behavior
Date: 31 Aug 92 21:21:40 GMT
Reply-To: ewanco@kalvin.enet.dec.com
Organization: Digital Equipment Corporation


In article <KHERA.92Aug31132624@thneed.cs.duke.edu>, khera@cs.duke.edu (Vivek Khera) writes:
From: khera@cs.duke.edu (Vivek Khera)
Subject: Re: su behavior
Organization: Duke University CS Dept., Durham, NC

> now if you claim that just by being in group wheel, one has root
> priveleges, then i suggest you find a good book on unix security and
> read it.

I am not claiming this.  I am saying that this is in fact what is happening.

Actually the reason, I discovered, that this is happening is that I gave it
gid zero in /etc/password.  This is what I thought was meant by putting it in
the wheel group.  Now I know I need to make its gid something else and simply
list the user under wheel in /etc/groups.

Eric
--
/=============================================================================\
| Eric Ewanco - Software Engineer     For the rash and outrageous opinions ex-|
| Digital Equipment Corp, Maynard MA  pressed herein I alone am responsible;  |
| ewanco@kalvin.enet.dec.com          they do not belong to DIGITAL(TM).      |
\==============================- 2 Th 2:15 -==================================/
From: fontenot@ravl.rice.edu (Dwayne Jacques Fontenot)
Newsgroups: comp.unix.bsd
Subject: Re: new boot roms
Date: 3 Sep 1992 23:46:00 GMT
Organization: Rice University

better yet, why doesn't somebody figure out how to make it work with those
flash BIOS machines (Dell, etc.). That would be totally cool!

In article <183c4vINNfit@maverick.ksu.ksu.edu> brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:
>Okay, here's a thought.  Why doesn't someone write up some new boot
>room code that would make a PC act a lot like a Sun when you turn it
>on.  Get rid of all the gunky MS-DOS support.  Put in a nice little
>monitor to examine memory and various registers and i/o ports and
>allow easy booting from any device and any partition on that device.
>
>This would effectively disable the machines ability to run MS-DOS, but
>that wouldn't be a great loss anyway.  It might be possible to dump
>the ROM code before replacing the ROM's, and store it on the last
>couple, or first couple, tracks of a hard disk.  Then the new boot
>code could, upon detecting an MS-DOS boot, load the old ROM code,
>twiddle a few bits and bytes and jump to the old code and let it
>finish loading MS-DOS and provide the BIOS support that it needs.
>
>This is far, far beyond any skills I have, but it seems like it might
>be worthwhile and would solve a lot of the problems and workarounds
>that people are having and using now.  Maybe someone should get on
>AMI's or Phoenix's back and get them to add some support for other
>OS's than MS-DOS in their boot code.
>
>++Brett;
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: Small X for 386 bsd??
Date: Fri, 04 Sep 92 02:28:49 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 

In article <N2XIFZ6@taronga.com> peter@taronga.com (Peter da Silva) writes:
>In article <80hnj7a.hasty@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes:
>>If you or anyone can come up with a better windowing system than X 
>>which enjoys such wide support not only on 386bsd but across many
>>operating systems and that is FREE, Please let me know.
>
>MGR
>
>Anyone doing a port? I don't have 386BSD here, but a good windowing system
>that didn't make a 486/50 seem less responsive then an Amiga 500 would
>be a convincing argument... :->

I have an 486/33 is very responsive with X. Also, the performance
problems in a PC are related to non-accelarated svga chip-sets and
their 64k banking systems. For instance, the S3  is about 10 times
faster than your regular vga. 

Is MGR a networked windowing system ? And does it have a graphics API?


Amancio Hasty
>-- 
>                                                                `-_-'
>                         Have you hugged your wolf today?        'U`
>
>Peter da Silva, Taronga Park BBS, Houston, TX  +1 713 568 0480/1032


Xref: sparky comp.unix.bsd:4604 gnu.misc.discuss:2754
From: ian@airs.com (Ian Lance Taylor)
Newsgroups: comp.unix.bsd,gnu.misc.discuss
Subject: Re: selling 386BSD (was Re: 386BSD on CD-ROM?)
Date: 23 Aug 92 21:16:56 GMT
Followup-To: comp.unix.bsd

Cross posted from comp.unix.bsd to gnu.misc.discuss.

peter@taronga.com (Peter da Silva) writes:

>In article <1992Aug23.060308.6392@nuchat.sccsi.com> kevin@nuchat.sccsi.com (Kevin Brown) writes:
>>Say that a copyright, regardless of who owns it, states that what is being
>>copyrighted (a) is freely redistributable (i.e., anyone can give it to
>>anyone else), (b) can be put to whatever legal use someone wants to put
>>it to [...] (c) any modified version *must* be distributed with source as
>>part of the distribution, but other than being included with the
>>normal distribution, can be distributed with any copyright provisions.

>I'm not sure how this differs from the Copyleft. Could you provide an
>example?

Note that I didn't write the original article.

It differs because if, say, the C compiler hcc were covered by this
license, some computer company, say HAL, could modify it and sell HAL
hcc under restrictive terms.  Anybody would still be able to get the
original hcc but the only way to get the HAL modifications would be to
purchase them directly from HAL.  HAL hcc would be required to be
distributed with source.

The GPL, of course, would require that purchasers of HAL hcc be
permitted to redistribute it to others.

The terms are described above are essentially public domain, except
that anybody who sells a program covered by these terms is required to
provide source.  However, they need to be made more complex to provide
the protection I think the original poster is after, because as
described above they imply that person A could sell the code to person
B, with source, but permit person B to resell the code without source.

Anyhow, the real issue of the GPL is library code, and it's not
immediately clear to me what the implications of the above terms are
for that.  I have not yet heard what I consider to be a reasonable
objection to the GPL for application programs.

On a separate note, it seems to me that several posters to
comp.unix.bsd recently have been misrepresenting the GPL.  It's not
that hard to understand, and it's widely available.  I encourage
everyone to try to read and understand it before criticizing it.
-- 
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: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Compiling 386bsd-0.1 on < 40Meg ( I've done it)
Organization: Curtin University of Technology
Date: Sun, 30 Aug 1992 07:12:48 GMT

Hi,
	This is probably no interest to those with 200+ Meg hard drives, but
I've compiled 386bsd on a 40 meg hard drive.  I have two 40 Meg drive, the 
binaries live on one, and the sources live on the other.  After extracting the 
sources and looking around I deleted all the sources except those in the
/usr/src/sys.386bsd directory.  I then followed the instructions in 
/usr/src/sys.386bsd/ROADMAP (after applying the patch supplied by Chris D. to 
/usr/src/sys.386bsd/i386/conf/Makefile.i386 which is in the unofficial
directory at agate.)

	There is a heap of free space left over at the end, so not all the
sources have to be deleated, so my next move is to put them all back on 
again :-(

	Now that I've compiled the kernel, how do I make a bootable floppy?
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
From: tgt@neon.ecn.purdue.edu (Conan the Librarian)
Newsgroups: comp.unix.bsd
Subject: X for 386 bsd
Date: 1 Sep 92 18:12:04 GMT
Article-I.D.: noose.1992Sep1.181204.5986
Organization: Purdue University Engineering Computer Network

Could someone please give me an update on using X386 with alternate
video configuration (specifically, with an ATI Graphics Ultra "8514a" card).
I am extremely eager to try X386 out!  How soon before this is possible?

Thanks.

-tom
--
Tom Tobin				UUCP:     pur-ee!tgt	
Dept. of ChE				INTERNET: tgt@ecn.purdue.edu
Purdue University			Ma Bell:  home (317) 463-0189
W. Lafayette, IN 47907				  office "   494-4052
From: pejn@cc.uow.edu.au (Paul Nulsen)
Newsgroups: comp.unix.bsd
Subject: [386bsd] Installing X386
Summary: What is /dev/vga?
Keywords: 386bsd, X386, installation
Date: 30 Aug 92 02:50:58 GMT
Organization: University Of Wollongong


This is obviously a stupid question, but I can't seem to find the answer. I
have tried to install the X386 binaries (X386 version 1.2E 1.0.1) from
agate.berkeley.edu. When I run startx I get an error message to the effect
that the server can't open /dev/vga. This is presumably the device that the
server uses to access the video hardware, but I can't find any info on what
the device numbers need to be. Being foolhardy, I reckoned this had to be
some form of access to the console, so I tried mknod /dev/vga c 0 0. The
result was an instantaneous crash of the whole system. I have not been able
to find any reference to /dev/vga in any of the information I have
collected. Can someone please enlighten me - before I do some serious damage
to my system?

Thanks
Paul Nulsen
From: rstevens@noao.edu (W. Richard Stevens)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd on notebooks?
Summary: works fine, but beware of network connectivity
Date: 26 Aug 92 13:01:33 GMT
Distribution: comp.unix.bsd
Organization: National Optical Astronomy Observatories, Tucson, AZ, USA

I have its relative (BSD/386) on a Dell 325N and it works fine.

But, beware of network connectivity with a notebook.  That's the
real problem.  SLIP works so-so, mainly due to silo overflows,
and it's usually pretty hard to just swap in a 16550 in a notebook
given their tight packaging.  I doubt it would be very nice for
NFS anyways.  I had intended to use a Xircom pocket Ethernet adapter
(I was prepared to write the driver myself), but it turns out Xircom
won't give you any information at all about programming their device.
(And of course, all their supplied drivers are for DOS.)  Seems like
a docking station is about the only way to really hook one up for real
connectivity.

	Rich Stevens  (rstevens@noao.edu)
From: gt@prosun.first.gmd.de (Gerd Truschinski)
Newsgroups: comp.unix.bsd
Subject: Re: HELP: Can't install 386bsd-0.1 into own partition!
Keywords: 386BSD
Date: 27 Aug 92 20:19:50 GMT
Organization: GMD Berlin (FIRST)

In article <ache.714917290@cpuv1>, ache@astral.msk.su (Andrew A. Chernov, Black Mage) writes:
|> In <ache.714840717@cpuv1> I writes:
|> 
|> >Problem description:
|> >Can't install 386BSD into 0xa5 partition, but installation on whole
|> >disk is sucessfull.
|> >This bug is independent of partition size and order.
|> 
|> >'install' diagnostics:
|> >"High level... disk storage:"
|> >Disk parameters and partition size are correct.
|> >After "super-block backups ..." and its numbers 'install' says:
|> >newfs: ioctl (WDINFO): No such process
|> >newfs: /dev/rwd0a: can't rewrite disk label
|> 
|> I found some solution of this problem, but not a _real_ solution:
|> 
|> You must allow 'install' to _create_ BSD partition, don't create this
|> partion by hand or by "diskmanager" or by something else.
|> 'install' can't work only when BSD partition already exist, but can
|> create it himself!

Hey, are there anywhere the sources of 'install', did I miss an artikel?:-)
I have had the same and other problems and I'm ending with one big 
BSD partition without DOS.


|> 
|> Very strange...
|>
Thats what I'm saying, but thank you for system as it is working now. 
|> -- 
|> In-This-Life:  Andrew A. Chernov    |  "Hay mas dicha, mas contento
|> Internet:      ache@astral.msk.su   |  "Que adorar una hermosura
|> Organization:  The RELCOM Corp.,    |  "Brujuleada entre los lejos
|> 	       Moscow, Russia       |  "De lo imposible?!"  (Calderon)


/gT/
Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Re: Extracted {bin,src,etc}dist and X386?
Organization: Curtin University of Technology
Date: Thu, 27 Aug 1992 04:48:54 GMT

terry@cs.weber.edu (A Wizard of Earth C) writes:

>In article <colin.714802377@marsh> colin@marsh.cs.curtin.edu.au (Colin Manning) writes:
>>Hi,
>>	Is there anywhere that individual files from the {bin,src,etc}dist's
>>can be got from (anon ftp?)?

>agate.berkeley.edu.  Root directory is a directory under:

>	pub/386BSD/386bsd-0.1/

O.K.  kirk.bu.oz.au (My "local" site) only has the director tree, and not the
files.  Thanks.

>X386 is not a standard distribution piece yet, but is under the ports
>directory:

>	pub/386BSD/ports-0.1/ (may be a little off on the actual name)

>as a lump.  There is apparently a patched kernel in with it, as well as the
>kernel patches to patch your own.


>					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
>-------------------------------------------------------------------------------
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
From: cl45@cunixf.cc.columbia.edu (Ching-Tse Liu)
Newsgroups: comp.unix.bsd
Subject: HELP: installing SRC01 for 386bsd
Date: 31 Aug 92 17:32:28 GMT
Reply-To: cl45@cunixf.cc.columbia.edu (Ching-Tse Liu)
Organization: Columbia University


	After successful installation of the bin distribution, I had trouble installing the 
src dist. Then I followed the suggestion of some people by increasing the number of
openfiles thru " limit openfiles 128 ." In the middle of the extraction ( of the src01 ),
an error message came up

	panic: kmem_malloc: kmem_map too small

I have a 486/50 with 16 meg using Adaptec 1452B with Seagate ST1200N 1GB hard drive.
I allocated the last 500 meg to 386bsd. If it makes any difference, I use the dist.fs from
/unofficial/newbootables/cgd that supposedly fixed some bugs.

Any help will be greatly appreciated. Thanks !



       		                     	***********************
--cliu@merlin.appmath.columbia.edu	*   CLifton T. Liu    *
--cl45@cunixf.cc.columbia.edu		***********************
From: aw2t+@andrew.cmu.edu (Alex R.N. Wetmore)
Newsgroups: comp.unix.bsd
Subject: thick port on 3c503
Date: 2 Sep 92 07:03:32 GMT
Article-I.D.: andrew.YedBT4e00WAtEAD39w
Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA

Does anyone have a kernel that is patched to use the thick port on the
3com 3c503?  Our local net isn't thin...

alex
Newsgroups: comp.unix.bsd
From: gclarkii@NeoSoft.com (Gary Clark II)
Subject: Kernel sources only
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Thu, 27 Aug 1992 01:35:55 GMT
Followup-To: comp.unix.bsd
Summary: Getting kernel sources only...
Keywords: kernel sources BSD


Hello,

Some people have been asking about how to get just the kernel sources
instead of the whole thing.  Here are the steps I took to get them.

1. FTP to agate.berkeley.edu (or anysite that has a tar capable ftp)
2. cd to /pub/386BSD/386bsd-0.1/filesystem/usr/src
3. type 'get sys.386bsd.tar.Z' and the system should open a path for
   /bin/tar and will also compress it.  You can also type
   'get sys.386bsd.tar' and you get just a tar file.
4. Take this file to your 386bsd system and un-tar in the /usr/src dir.
5. You now have the kernel sources to hack and break.

Maybe someone who has a ftp site open could go do this and let the net know
instead of overloading poor agate with tar transfers.

Hope it helps.

Gary Clark II **N5VMF**
gclarkii@tghost.gbdata.com
gclarkii@neosoft.com

Newsgroups: comp.unix.bsd
From: grefen@wilbur.uni-mainz.de (Stefan Grefen)
Subject: Re: Restrictions on free UNIX / 386BSD (Re: selling 386BSD)
Organization: Johannes Gutenberg Universitaet Mainz
Date: Wed, 26 Aug 1992 07:40:58 GMT

In article <9208251653.26@rmkhome.UUCP>, rmk@rmkhome.UUCP (Rick Kelly) writes:
|> In article <1992Aug25.062100.15187@nntp.hut.fi> jkp@cs.HUT.FI (Jyrki Kuoppala) writes:
[ save bandwitdh ]
|> >
|> >Hmm - I think I've heard that Commodore(-Amiga) uses gcc to compile
|> >their **ix OS and Lotus (yep, of the 1-2-3 and lawsuit fame) uses gcc
|> >to compile their products.  And then there's DG which ships gcc as the
|> >native compiler.
|> 
|> 
|> It would be a strange to build SVR4 with gcc.  Commodore probably started
|> out with a Motorola development system running SVR4, and a big pile of
|> sources.  They would have then hacked and cross-compiled a development
|> environment that would run on the Amiga 2500 and 3000.
Atari has done it. Their SYSVR4 comes with only gcc (and g++).
They were not very happy with the AT&T Sources, they told me :-)
|> -- 
|> 
|> Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP

-- 
Stefan Grefen   ---   Johannes Gutenberg University Mainz   ---    Germany
Email: grefen@goofy.zdv.uni-mainz.de       ---        Phone:  06131/392415

Newsgroups: comp.unix.bsd