> On Wed, Mar 14, 2001 at 03:57:48PM +0200, Ben-Nes Michael wrote:
> > Slackware considered to be hard because you need to compile everything
> > but if you do it right its the best ( so I heard )
> > Debian is just another way to manage the Linux with deb and not RPM but
> > considered to be superior ( the whole system )
>
> I'm not familiar with Slackware (never used it), but as I heard, the
> packaging system is quite primitive, and there aren't configuration
> tools similar to RedHat's, so you end up learning to compile stuff
> yourself, edit configuration files and learning sysadmining hardcode :)
>
> Debian's main strength is APT, which allows you to install and upgrade
> applications, libraries etc. right off the net (from one of the many
> Debian mirrors) by issuing one simple command. APT will take care of
> fetching and installing all of the dependencies and the package itself,
> just like the Aduva Manager does on RedHat :)
> (Of course, you can install packages from a local CD-ROM as well.)
> With servers, you could use it to upgrade various daemons to the
> latest versions regularilly to maintain security. As for today, Debian
> doesn't come with as much config tools as RedHat, so it's not for total
> newbies.
>
> For example, instead of RedHat's RPM-hell, I can simply issue:
> apt-get install mysql libapache-mod-perl php4-mysql libapache-mod-ssl
> (this will also install php4 and apache, since php4-mysql and
> libapache-mod-perl depend on them)
>
Debian is *not* just another way to manage Linux with deb and not RPM.
It took another route:
1) About 500 Debian maintainers.
2) Debian policy, which is one of reasons for the supposedly technical
superiority.
3) It is produced by an organization, as opposed to a commercial company.
4) One of its goals is to let you upgrade the system in place and with as less
interruption to production as possible.
5) A huge number of packages.
6) Work in progress for more architectures then any other distro?
7) I believe it is more much popular then Slackware. Furthermore, there is the
debian-il mailing list + some members in the local Linux community that are
committed to Debian.
As for the knowledge you would gain from building the system yourself, there
is the problem that it might take a long time. If you insists you can also try
to build the Debian packages from source. This might be similar to building
the binaries from src + you might get more insight by looking at the choices
that the official Debian maintainer had done. Some of these choices would give
you more insight from the system wide perspective, something which is more
difficult to get when looking at each package by itself.
In short, among {Debian, Slackware} I choose Debian.
Yet all the above is written without real Slackware experience. Can a
Slackware user tell us what he consider to be Slackware advantages?
> --
> Best regards,
> Ilya Konstantinov
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
>
--
Shaul Karl <[EMAIL PROTECTED]>
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
