SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
U mean just one person that develop the whole Slackware, not like Debian that is hacker by > 600. It's that is guy is really expert. But how about the stablelity & securety. Can this person handle this all alone. Because I have just read a one website that said Slackware 8.0 have about 10 security holes compare to others distro.
Slack 8.0 was released in July 2001, well over a year ago. How many security holes have they found in packages since then? Keep in mind that the security issues are related to the packages that are used to build the distro with. Each package can always be upgraded individually, and Pat does a great job at keeping up with the security issues.
Recently, the reason for the delay on 8.1 and the second release 8.1.01 was a security issue within a particular package. If I recall correctly, the security announcement was made just days after the first 8.1 was released. Pat stopped the process and remastered the set because of just one program that had a known security issue. I seriously doubt if any other distro could of accomplished the same task after announcing the official release.
Originally posted by garyura
Because I have just read a one website that said Slackware 8.0 have about 10 security holes compare to others distro.
Perhaps this comment was meant as a compliment, as in, _only_ 10 security holes.
There have been some more security patches (8) since Slackware 8.1.01 was released, and it's very easy to get the patched packages and apply them. Check out an up-to-date mirror, (July 30, at least) e.g.