As I remember, Patrick made the move to 7.0 to parodize the move to 7.0 that other major distros had done. There was no significance to it. So I guess, 8.0 should be 6.0
I also heard that another reason was also to give those who put absolute faith in version numbers a little push towards Slackware. Still alot of people out there who think that a version 7 distro is far more advanced than Slackware 4.0
Re:The Neverending wave of criticism of slackware.
on
Slackware 8.0 Released
·
· Score: 1
Definitely...
What's the point in having advocating open-source systems when you don't even want to look at source code in the first place!
Red Hat may have originated from Slackware, but it definitely doesn't feel like it! I'm thinking that Slackers who want an RPM slackware still want that stability and closeness to unix that we don't get from Red Hat. I don't even know how to navigate around Red Hat's/etc:)
Yes, I used rpm2tgz just last night, and everything works like a charm - and I made everything into a tgz package after that.:)
Sooooo, what's the deal with RPM? Is there a significant advantage to using it that I am missing out on? I'm happy with tarballs, and I've never come across RPMs on Irix or Solaris, so I haven't had a need for them until I tried getting Helix Code.:(
Is a RPM version of Slackware even feasible?
I just don't understand this modern OS thing - I've used Slackware since the beginning, and I've also played with Red Hat 'Hedwig' and 'Guiness', did a rough install of Mandrake, but I keep finding reasons to go back to Slackware. I'm running a very new P4 with a lot of new hardware, and Slackware picked it up just fine... and the new Gnome packages are tasty;)
Anyway, age old question, but how difficult would it be to create an RPM-based version of slackware? I'd like to give it a go, but admittedly, I know little about the internals of RPM and why RPM *allegedly* doesn't lend itself well to systems based on tarballs. Any ideas or references to get me started?
Slashdot Mirror
As I remember, Patrick made the move to 7.0 to parodize the move to 7.0 that other major distros had done. There was no significance to it. So I guess, 8.0 should be 6.0
I also heard that another reason was also to give those who put absolute faith in version numbers a little push towards Slackware. Still alot of people out there who think that a version 7 distro is far more advanced than Slackware 4.0
Definitely...
What's the point in having advocating open-source systems when you don't even want to look at source code in the first place!
Red Hat may have originated from Slackware, but it definitely doesn't feel like it! I'm thinking that Slackers who want an RPM slackware still want that stability and closeness to unix that we don't get from Red Hat. I don't even know how to navigate around Red Hat's /etc :)
Yes, I used rpm2tgz just last night, and everything works like a charm - and I made everything into a tgz package after that. :)
Sooooo, what's the deal with RPM? Is there a significant advantage to using it that I am missing out on? I'm happy with tarballs, and I've never come across RPMs on Irix or Solaris, so I haven't had a need for them until I tried getting Helix Code. :(
Is a RPM version of Slackware even feasible?
I just don't understand this modern OS thing - I've used Slackware since the beginning, and I've also played with Red Hat 'Hedwig' and 'Guiness', did a rough install of Mandrake, but I keep finding reasons to go back to Slackware. I'm running a very new P4 with a lot of new hardware, and Slackware picked it up just fine... and the new Gnome packages are tasty ;)
Anyway, age old question, but how difficult would it be to create an RPM-based version of slackware? I'd like to give it a go, but admittedly, I know little about the internals of RPM and why RPM *allegedly* doesn't lend itself well to systems based on tarballs. Any ideas or references to get me started?