🚀 go-pugleaf

Gordon Mulcaster <gordonm@geocities.com> writes:

>In article <56qq6m$bh6@vanbc.wimsey.com>, John Henders writes:
>
>> If you are running Redhat or Debian, there are packages that drop right
>> in. If you're running Slackware, there may be a package, but who knows
>> if it will work. ;)

I've always built INN myself.  That way everything goes where *I* want
them.

There are a few things that I just can't conceive of installing from a
package - INN's one of 'em.  But that's just the news admin in me - an
INN newbie should probably install from a package on the assumption
that it's hopefully already reasonably configured.

Oh, I built INN for my home box and set up a small feed.  No problems
once it was configured.

>I've got a slackware release, I'm running 1.2.13, I know 2 is out, but
>since the books I have cover 1.2.x I figured I'd stay here for now while I
>figure stuff out. The above statment makes me wonder if the slackware
>distribution is looked down upon by those "in the know"? I'm using
>slackware becuase it's on the CD I have, should I avoid it when it comes
>time to getting a new version?

Anecdote: I went to install Red Hat on a new office machine but
couldn't reach redhat or any mirrors.  So with a shrug I went and
installed Slackware instead.

In other words, I didn't care either way which one I installed.  I
typically build a dozen or so packages that I have need of, and find
that everything else is in both distributions.

Others can argue about package managers and other distinguishing
features of the distributions - my main concern is about what binaries
are available and where they are installed.  Either distribution
satisfies those needs.

--
Toomas Losin                                    Services Development
tlo@istar.ca                                    iSTAR internet inc.