User: Password:
|
|
Subscribe / Log in / New account

Slackware 13.37: Linux for the fun of it

Slackware 13.37: Linux for the fun of it

Posted Mar 24, 2011 23:32 UTC (Thu) by fsateler (subscriber, #65497)
Parent article: Slackware 13.37: Linux for the fun of it

I once attended a class where they told us a story about a certain ballet-shoemaker who had invented a shoe that had the property of not destroying and deforming your feet when doing the tip-toe thing. When introducing the shoe, he thought he would make a lot of money out of this. Alas, all the serious ballet dancers refused to use the new shoe, saying that to get the true beauty of ballet the dancer had to endure the pain of the shoes, or something like that. So the shoemaker had to go to ballet schools so teenage ballet dancers, who had not yet gotten used to hurting feet, adopted them.

I can't help but feel a similarity here.


(Log in to post comments)

Slackware 13.37: Linux for the fun of it

Posted Mar 25, 2011 2:25 UTC (Fri) by dmag (guest, #17775) [Link]

The biggest benefit of Slackware is that you can upgrade things at will. There are no surprises if you have to go upstream and do the "download/configure/make" dance.

In Ubuntu/RedHat, everything works if you stick to the package system. But if they are too slow (or you need different compile-time options) it's not always easy to "do it yourself". Grabbing a fresh copy from upstream will often break in subtle ways because of changes made by the distributor. (In fact, that's what makes moving between these distros a pain.) They do everything from moving around config files to adding custom patches to changing the name of services! (ssh vs sshd, apache vs httpd).

Slackware 13.37: Linux for the fun of it

Posted Mar 25, 2011 20:19 UTC (Fri) by vonbrand (guest, #4458) [Link]

I'm sorry, but when I used Slackware (way back) and installed stuff from sources, I had to reinstall with some regularity because of self-inflicted breakage. Same when I moved to Red Hat, until I learned to get the SRPM (source), create my own with any updated/hacked upstream, check the patches/modifications from Red Had still work, build and install my own package. It integrates with the system cleanly, if/when Red Hat does come out with an updated package it will cleanly replace mine if I'm a bit careful, any dependencies are handled for me. Any real package management system must at least allow yo to do the same. Remembering what hacked stuff is on the system is feasible as long as it is a dozen (at most) packages, over that is sheer madness.

Been there, done it.


Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds