Hi,

We all have our opinions on 'forked distros'. I tend to agree with Erics' well stated definition.

A lot of people do plagiarize, while others take the work and acknowledge the original author but still build on someone's original work.

Sure, you use a Slackware based livecd to enrich yourself. Therefore in your mindset it is OK to use a derived distro. I'm sure PV finds his derivation being used for others gain as a minor problem, but revenue has not always been his way. His support base is strong and loyal.

Slax, is a good livecd and their credit is valid. I think they do use the work of PV but credit his work. Still not really justifiable! Other forked distros, I cannot not really acknowledge.

In this case, 'imatation is the ultimate flattery' should be thrown out the window into the trash!

If you're suggesting that other distros shouldn't be based on Slackware, then that would wipe out most Linux distros, as they're all based on something. Debian, Gentoo, Redhat etc. So we'd be left with just a handful of distros. As long as use of someones work is acknowledged then it should be OK. Isn't that how the GPL is supposed to work?

Home > Library > Science > Hacker Slang

Slackware was not a fork of SLS, Slax is not a fork of Slackware, Ubuntu is not a fork of Debian, so on.

But nor "vulture" is the right word. Slax has not a rapacious, predatory, or profiteering nature.

'Enrich'? in what way? making money? no, I don't sell any Linux distro. I make money with services - consultancy, server administration and programming. I always ask my customers to buy their Linux distros directly from the 'sources' - some do that, others don't.

'Enrich' in the sense of raising my knowledge? yes, I always try to do that.

BTW, I'm not a SLAX developer or anything else. That was an example of a LiveCD distro - the one I know.

Isn't GPL about freedom? "Freedom to run the program, for any purpose; freedom to study how the program works, and adapt it to your needs; freedom to redistribute copies so you can help your neighbor; freedom to improve the program, and release your improvements to the public, so that the whole community benefits". Apparently, you're not very comfortable with some of these freedoms when they are put in practice.

I think GPL isn't about freedom in the truest sense. It contaminates everything it touches with GPL too.
I prefer the BSD-license which truly lets you do whatever you like with the code.

where does one download the new RC version? i'd like to help test it if i can. looked on the slack site and i can't find it. i kind of figured it's part of current but i can't seem to find out how to get slackware-current.

You can download it from here: http://www.slackware.no

To get the RC1 you need to download the -current branch. You can download easily using Alien Bob's script mirror-slackware-current from here.

The RC1 (release candidate 1) is the same slackware-current as always. It's just stamped with a new status, to indicate that the release of Slackware 12.0 is imminent.
So, if you download slackware-current today, you will in fact get Slackware 12.0-RC1.

Eric

Hi,

Not to get into semantics about this but you are using the Linux to enrich yourself. The act or performance in services using the material is enriching. Nothing wrong with advising someone to purchase but still the services are rendered by you with the presentation of any materials at hand or used.

Not to get into GNU/GPL issues here since that is an on going open debate. Our original discussion was about forked/vulture distros. Sure some distros would not be here without the original but that is still a development in progress. I feel that if you want something then taking it is not the right way to go. Earn it! Put time an effort into development without plagiarize. Stamp, credit or license properly.

I'm very comfortable when the practice is done properly. Maybe a definition of GPL is in order.
Too many people loosely fly the GPL/GNU without full understanding of the reasoning of Stallmans intent. A lot of gain has been had off the back of free software development society because of the license not being implement fully or properly. That's my beef!

Another reason for GPLv3, which will be released in July/07. A lot of holes are being plug. Authors/developers will have more control of their code, not necessarily restrictions. Rid the world of the RHs' and Novells within the GPL world.

As for distribution, look at the 'The copyleft'.

You should also look at the Free Software Foundation site.

HTH!

As soon as this version comes out, I am going to replace my 11.0 installation with it on my notebook, hoping some issues will be fixed. From scouring the web and forums, it seems HP notebook users have slightly better luck with ACPI with kernels beyond 2.6.18. A good 9 or so months has passed now since the purchase of my HP notebook, and two months later after I bought it Slack11.0 was released, but at that time my notebook was perhaps too new and hardware wise 11.0 couldn't quite cope with it. I am also looking out for further bios updates for my notebook, hoping ACPI will be improved. *sigh*

Question...if I were to install the RC1 version of Slackware 12, would it be easy to upgrade to the final release? Like installing from the current tree? Just curious. Can't wait for Slackware 12!

Yeah - no telling how much may change between now and then, but it should be relatively minor. Upgrading to the final should be akin to doing a normal security update after final. Most of the hard stuff (Xorg and other package splitting, core kernel/glibc/gcc stuff, and so on) should be done and it's just catching last minute bugs and updates. It's not to say all hell might not break loose, but it's not likely.

If you continue to follow the -Current tree (after upgrading to RC1), you don't need to upgrade to the final release, as it's already the same version as the final

Cool...thanks!!