🚀 go-pugleaf

In article <874lkxibcu.fsf@bogus.nodomain.nowhere>,
Mike Spencer  <mds@bogus.nodomain.nowhere> wrote:
>
>Ahem A Rivet's Shot <ste...@eircom.net> writes:
>
>> On 28 Mar 2018 03:17:00 GMT
>> t...@loft.tnolan.com (Ted Nolan <tednolan>) wrote:
>> 
>>> and also 386BSD stalled for a while as the author had in mind more
>>> of a teaching tool than a supported, stable system and things didn't
>>> take off for FreeBSD & NetBSD until it was forked.
>> 
>> 	Yes, I discovered the BSDs shortly after the fork (1993) after
>> trying Linux (bought on floppies) and finding it OK but not good enough for
>> what I wanted. It was confusing 386BSD, BSD386, NetBSD, FreeBSD were all
>> talked about with some people managing to mix up the first two (one was
>> commercial for the 386) - I wound up asking on USENET and getting a good
>> answer (even if it did claim that Linux was a toy).
>
>I got my first intro to Unix in '89, realized immediately that this
>was where I wanted to go.  But there appeard to be a mare's nest of
>legal and technical penc around the whole BSD shebang.  I had remote
>access to Unix so I kept putting it off.  Didn't want to have to
>figure out all the gnarly details of the conflict.
>
>In '99 my Unix access threatened to go away so I bought a used Intel
>486 machine and moved to Linux.  Haven't looked back since. (Well,
>except that my very first shot was Caldera Linux from a CD in a Great
>Fat Book.  That lasted only long enough to figure out how to get and
>install Slackware.)
>

I have always run FreeBSD at home, but professionally, it always seems to
be Linux on the job (after it stopped being Sun).  It didn't have to be
that way (and FreeBSD ran some major sites at one time I think) but that's
the way it's fallen out.
-- 
------
columbiaclosings.com
What's not in Columbia anymore..