Posted by WilliamC on Fri Nov 13 11:55:34 1998
In Reply to: Alive posted by Myles on November 11, 1998 at 17:06:07:
| Distribution: | paneris@i-way.co.uk |
|---|
wishlist:Perl
Presumably it has 5.004, we should probably install 5.005
just to keep up.Postgresql
It comes with the old version,
we should probably install the new version.Apache
It comes with it, do we care which version?
You can set this up with linuxconf, or its
peasy to zap its config files.INN (news server)
It comes with it, do we care which version?
I have never tried to set this up and it is
reputedly a little opaque.sendmail (mail server)
It comes with it, we don't care which version,
since if we did we would be using smail or qmail
anyway :). This is very easy to configure using
linuxconf, with one proviso which doesn't matter if
it's only being used from remotely (details on
request).procmail (incoming mail processor)
This is simple but poorly documented unless things have
changed. Maybe there is something better on the RedHat
CD. Otherwise it's possible to make sendmail do fancy
things directly by defining new pseudo-mail-delivery
commands.ftp server is presumably up already
Paneris, which should work trivially since it is currently
running on BSD.samba server (?)
It comes with it.
CVS server
It comes with it.
I truly cannot think of anything else we could possibly
want for the moment. Probably working out how all those
things are used will keep Chippy happy for a few days!NB don't forget I know quite a lot about running a simple
Linux setup, so can answer questions if they arise.
One tip:When you install new non-RPM packages from source,
in other words compiling them from the plain sources,
they generally by default put themselves spread over
/usr/local/bin, /usr/local/lib, etc.The best policy, however, is to keep source packages
and source trees in a definite place, and installed
binaries/libs in a definite place so that you know
what is there, can delete them and maintain several
versions, and so on.So I put source packages in /usr/local/packages/dist
(e.g. /usr/local/packages/dist/perl5.005_3/...)
and tell them to install themselves in /usr/local/packages/inst,
(e.g. /usr/local/packages/inst/perl5.005_3/...).
You then have to go to /usr/local/bin and /usr/local/lib,
etc., and make symbolic links to all the files in
/usr/local/packages/inst/perl5.005_3/bin
and .../lib and so on,
but you can do that semiautomatically with simple
shell commands,
and I find it saves a lot of bother. For instance
to uninstall perl5.005, knowing that you won't
mess anything else up, it is sufficient torm -rf /usr/local/packages/inst/perl5.005_3