Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Using Robby's bandwidth is not stealing. He posts links on the
net and offers his stuff for free. If he doesn't want someone
leeching it, he is free to block their IP, netblock, or whatever
it takes.
Indeed. For clarity's sake, I wasn't implying that anyone was stealing - just that they might perhaps be impolite in their actions.
Quote:
There are many ways that easys is taking from Slackware without
paying for the efforts. They could start with asking Pat V. and
the Slackware core team if they agree to easys using what they
have worked very hard on (Slackware) and putting the easys name
on it.
The same thing applies to Slamd64 IMO. They don't even bother
to change the name from Slackware to Slamd64 in files they get
from Slackware. Lazy ...
What does "Behalten Sie es einfach, dumm" translate to in English?
In the context, I assumed it was the German translation of K.I.S.S.
Quote:
But basically taking someone else's
hard, and continuing work, and just rebranding it is stealing ... plain and simple.
I don't want to quibble (well, maybe, just a little....) but--if I am not mistaken--the typical Open-Source license allows you take some code, and make no changes except the name.
This said, I do agree that there are lots of parasites out there--defined in this context as people who take but don't add value. More generally, some feel that the world is being taken over by parasites. Unfortunately, most of them are doing nothing illegal.
Looks to me like stealing ... course, I'm just an old country boy.
To my knowledge, Slamd64 doesn't do that, and I'd be sorely disappointed if they did.
Of course, the only reason I know about Bluewhite doing it is that comment though, so...
I don't want to quibble (well, maybe, just a little....) but--if I am not mistaken--the typical Open-Source license allows you take some code, and make no changes except the name.
This said, I do agree that there are lots of parasites out there--defined in this context as people who take but don't add value. More generally, some feel that the world is being taken over by parasites. Unfortunately, most of them are doing nothing illegal.
Indeed, hence my usage of the term "impolite" rather than "illegal."
This file documents the instructions for upgrading to Slamd64 12.0, the
packages added, removed, renamed, and/or split during the development cycle
from Slamd64 11.0 through Slamd64 12.0, and some potential "gotchas" that
users can avoid by arming themselves with a little knowledge. This file is
a very slightly modified version of the same file in Slackware.
Same file from Slackware-12.0:
Quote:
This file documents the instructions for upgrading to Slackware 12.0, the
packages added, removed, renamed, and/or split during the development cycle
from Slackware 11.0 through Slackware 12.0, and some potential "gotchas" that
users can avoid by arming themselves with a little knowledge.
Heavy emphasis on very slightly modified.
So perhaps Alien Bob is right ... they're just parasites.
Well, when the content is the same, the content is the same. I mean, in that particular case, how could it be redone effectively? I'd be more concerned if the file had *not* mentioned that it was basically copied from Slackware. Using and properly crediting it is fine IMHO, at least in that particular case.
Well, when the content is the same, the content is the same. I mean, in that particular case, how could it be redone effectively? I'd be more concerned if the file had *not* mentioned that it was basically copied from Slackware. Using and properly crediting it is fine IMHO, at least in that particular case.
Agreed. I don't have a problem with Slamd64 because it is only intended to be a port of Slackware for 64bit. I'm not aware of any 'features' it adds, and it does credit Slackware.
Stuff like easys, on the other hand, I'd prefer that instead their features simply be an 'addon' to Slackware (like the third party GNOME projects), or that they provide a diff of their sources right on the download page. I suppose they don't do this because they don't want to confuse their potential users. Since part of the feature-set of easys is a unique installer, perhaps it would be too difficult to package it as an addon. No matter, it feels cheap to me, and I hope it does bring most people to the original.
Stuff like easys, on the other hand, I'd prefer that instead their features simply be an 'addon' to Slackware (like the third party GNOME projects), or that they provide a diff of their sources right on the download page. I suppose they don't do this because they don't want to confuse their potential users. Since part of the feature-set of easys is a unique installer, perhaps it would be too difficult to package it as an addon. No matter, it feels cheap to me, and I hope it does bring most people to the original.
People who wonder why I stressed that these parasi^H^H^H^H^H^Hfork-off distros should make their full sources available to the public, should read this page to get some clarity about what violations of the GPL they are guilty of: http://gpl-violations.org/faq/sourcecode-faq.html
People who wonder why I stressed that these parasi^H^H^H^H^H^Hfork-off distros should make their full sources available to the public, should read this page to get some clarity about what violations of the GPL they are guilty of: http://gpl-violations.org/faq/sourcecode-faq.html
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.