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.
Did the Bluewhite64 Linux distro start at version 12.0?
Funny how they got there so quick.
Did you also notice how a Romanian copyrighted his stuff
in California?
Slamd64 still uses the Slackware name in it's Slackware files.
I also imagine the Bluewhite64 guy sends some of the profits
from his USB disk sales to Slackware.
That copyright issue was a glitch when I used sed to change the name. Sorry for this, not was with intention and is fixed here in the dev tree.
About the donation, yes, my first profit from on-disk sales (USB, DVD`s) is gone back to Slackware. In the future will go more as the sales are growing.
Here is the proof of the $100 donation to Slackware:
Code:
Order tracking num: uP2KZJIB.1211057560
E-Mail Address: on-disk{at}on-disk{dot}com
Telephone:
Shipping Info: Name: Attila Craciun
Company: bluewhite64.com
Address: xxxx
Baia Mare, Maramures 430182
Romania
Billing Info: Name: Karlie Robinson
Company: Webpath Technologies/On-Disk
Address: xxx
xxx
Payment Method: MasterCard
Credit Card Number: xxxxx
Shipping Method:
Item Info: qty price description
=== ===== ===============
100 1.00 slackdonation
Subtotal: $ 100.00
Tax: $ 0.00
Shipping and Handling: $ 0.00
Order Total: $ 100.00 If you have any questions about your order, please email us at
info[at]store[dot]slackware[dot]com, and please include your order tracking
number (uP2KZJIB.1211057560) in your email.
That copyright issue was a glitch when I used sed to change the name. Sorry for this, not was with intention and is fixed here in the dev tree.
I'm really not meaning to be critical, but how do you justify
substituting your name in place of the man's name who did all
the work, and calling it a copyright?
Maybe I'm splitting legal hairs, but I just don't get it. If
you really want your own distribution, who not make yours from
sources just like Pat has done. That seems to me much more ...
reputable, than using his work and changing the name.
Besides that, Pat wants a pure lib 64-bit Slackware. Why not
start working towards that end, rather than what you have now?
Quote:
Originally Posted by arny
About the donation, yes, my first profit from on-disk sales (USB, DVD`s) is gone back to Slackware. In the future will go more as the sales are growing.
Here is the proof of the $100 donation to Slackware:
I hope it's true and glad to see you giving back to Slack.
I'm really not meaning to be critical, but how do you justify
substituting your name in place of the man's name who did all
the work, and calling it a copyright?
I think this quote from Pat will clarify why I'm changing names. The copyright notices ARE not to be changed, only the Slackware name in the distro (like /etc/salckware-version to /etc/bluewhite64-version etc), as Pat suggested. Sorry again for that copyright issue!
Quote:
Besides that, Pat wants a pure lib 64-bit Slackware. Why not
start working towards that end, rather than what you have now?
Bluewhite64 is a pure 64-bit and, as I stated in the interview, it follows Slackware development line, just under different name.
Quote:
I hope it's true and glad to see you giving back to Slack.
"If you have any questions about your order, please email us at info[at]store[dot]slackware[dot]com, and please include your order tracking
number (uP2KZJIB.1211057560) in your email."
I'm the DARKSTAR Linux Project leader and a easys GNU/Linux developer, too...
But! I think, a derived distribution is not a "parasite distribution"... If this is not true, 90% of DistroWatch recorded distributions is simply... parasites.
In this thread is not about "White Side" and (parasite) "Dark Side" of Slackware... Marcus, me, yours? I'm old Slackware fans, first of all!
But! I not believe in the Slackware "right way" and in the (parasite) "wrong way" of the rest!
The easys (and DARKSTAR or Bluewhite64) graphical tools, including the installer and the managers has written over few years and spending time and money! Remember! The easys GNU/Linux is not a commercial solution. Can be used and downloaded for free. Is this a "wrong way" of our efforts?
Quote:
Originally Posted by Alien Bob
What you could consider for easys (it is something that I have wanted to build in the past) is revamping it into a custom Slackware installer distributed as an ISO, where the installer asks for a Slackware repository as part of the installation process (on a DVD, CD set, network server, NFS, you name it). That way everybody wins - Slackware will remain the distro that is going to be installed; your easys gains fame as a Slackware installer for those who need another language than english, and this Easys Slackware installer can take care of post-install configuration for the end user as well (including the installation of add-on packages that are not in Slackware itself - compare it to the several Gnome add-on installers like GnomeSlackBuild, Gware and Dropline Gnome).
Eric
I believe this: the easys GNU/Linux is not only a "custom Slackware installer"... This is a complete distribution derived from Slackware, because have own installer, configuration tools, artwork and packages selection. Is more advanced and different from another Slackware derivative (ie. Slax, etc) and beginner targeted.
Now, still exists three YaLI (graphicall installer) variants, for easys, DARKSTAR and Bluewhite64, writen in the top of ALICE managers API...
BTW. ALICE is a (Slackware) graphicall configuration environment and have seven managers, now. This ALICE managers can be used in genuine Slackware and any Slackware based distribution. Of course works in 64bits variants, too...
Well, is possible, of course, to create another variant of YaLI graphicall installer with this requirements, but the writing of graphicall managers is a very complex task, with spending of time and money, billions of carefully tests in virtual machine and in "real life" is required.
Where is the person interested in supporting the creation of a (unofficial) graphicall installer for genuine Slackware? If is any, please, contact me for supporting the writing of this YaLI variant.
Whitout any real interest, this is only suggests and wishes...
Second variant: of course, another C/C++ programmers can be payed, maybe as full-time job, to create this "graphicall installer solution".
Quote:
Originally Posted by Bruce Hill
Maybe I'm splitting legal hairs, but I just don't get it. If you really want your own distribution, who not make yours from sources just like Pat has done. That seems to me much more ... reputable, than using his work and changing the name.
Well, a good point! Is the time to reinvent the wheel! I like this!
Quote:
Originally Posted by Bruce Hill
Besides that, Pat wants a pure lib 64-bit Slackware. Why not
start working towards that end, rather than what you have now?
I hope it's true and glad to see you giving back to Slack.
Well... A "pure lib 64-bit Slackware" still exist as unofficial 64 bits Slackware port named "Bluewhite64". But is a "unofficial port"...
Oh no, I ignored this thread for a while, but it seems the parasite discussion has spread to this thread.
Look, there's no use in arguing about this. It is absolute nonsense and highly proprietary, anti-FLOSS thinking to call a derivative distro a parasite. NOW STOP IT !!!
Last time I checked the software that makes up Slackware is pretty much all FLOSS or at least redistributable without cost with source available. If someone wants to make a distro using this, there's not only nothing wrong with that, but it is highly encouraged as it is good FLOSS mentality and it helps fight the evil empire and it helps people out, etc.
I hope this will end the nonsense here (crosses fingers). That is all.
Last edited by H_TeXMeX_H; 05-19-2008 at 10:17 AM.
If I known right, you have directly contacts with the Slackware development team...
Well... At this time, the Slackware not contains a graphical configuration environment like SuSE, RedHat, Fedora, Ubuntu, etc...
Why not to be create a lobby for including our ALICE in the official Slackware tree, as (alternative) configuration tools?
Details about ALICE (Advanced Linux Installation and Configuration Environment):
ALICE is a graphical Slackware configuration suite, written by DARKSTAR Linux Project in C/C++, using Qt library, with the (strong) support from easys GNU/Linux and Bluewhite64 Linux. This include several modular managers:
1. X.org Manager - configuration on X.org server
2. Disk Manager - a partitioner wich known 13 filesystems management
3. Package Manager - graphical packages management in the GSlapt style but, of course, modular, using the slapt-get API and compatible with this.
4. Packages Wizard - packages installation wizard, using the "meta-package" files, for "one-click" install (well, the truth is: a "next-next" install).
5. Network Manager - network and PPPoE configuration
6. Time Manager - timezone configuration
7. Services Manager - configuration of the services starting
The software lobby requirements is: ALICE itself, the slapt-get (optionally GSLapt) and OpenSuSE's hwinfo.
In the future, if exists a true interest and support, of course, the DARKSTAR Linux Project can be write and maintain a graphical installer for the Slackware Linux, using the ALICE API (aka a YaLI variant).
Best Regards and I waiting your opinions,
Adrian.
Last edited by Darth Vader; 05-19-2008 at 12:47 PM.
I think ALICE might be pushing Slackware too far in the Ubuntu direction. I don't think those who choose Slackware want those kind of aids for configuration, etc.
That's why we have actually started developing easys GNU/Linux. The declared aim of easys is to make more people use Slackware. It offers a nice multilanguage capable graphical installer and a well preconfigured KDE Desktop with necessary apps for daily work.
As mentioned before: easys is not made for useres who are already glad with Slackware Linux (this is what is our goal . Also easys is not like Ubuntu is to Debian. The official upstream of easys is called Slackware Linux.
To make things a bit clearer we have updated the docs section, too:
Well, the Z80 systems and the M$ Basic over the 8bit system, works very good over the several years in the past...
I have a biiiiiiiiig problem! Why I have now a Athlon64x2 4000+ computer, over 64bit support?
This is, maybe, a big mistake! I live in Romania! Is poor country! But I can't buy now a (first-hand) 32bit processor from my city! Only 64bits procesors can buy from Craiova, Romania!
Where is the problem?
Your opinion? Is case to use, again, a Z80 (8bit) computer now, because works perfectly?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
"Dark Side" proposal to the true Slackware Jedi's
