What features/changes would you like to see in future Slackware?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I found nothing wrong with udev, yet it's not included in the install ramdisk. That is the problem. The old network.sh in Slakcware install initrd.img is for linux-2.4. For more recent Slackware versions, using udev instead is a better choice. I did post to explain how to use udev during installation here twice, and also mailed Pat. to explain it.
The above link (to another thread) I posted is only an example to explain the benefit of using udev (headless installation on a machine without knowing the model of its network interface card). I'm sorry if it confused you.
You didn't confuse me. I just wanted to have a better explanation about your issues with udev as you provided none. Thanks!
Click here to see the post LQ members have rated as the most helpful post in this thread.
I'd like to see Twinkle, or another SIP phone. But it's not hard to install from the sources.
I like Slackware, it's got almost everything I want and the package management doesn't try to discourage me from installing anything "unofficial". What could be better than that?
Regarding packages, I think things should be left the way they are. I think Slackware does a great job trying to cater to the desires/needs of most people. If people want this package and don't want that package, perhaps it would be better to switch to Ubuntu with the package manager and some 18000 available packages.
If you do not have the package you want, and you do not like to install from source, it is probably available at one of the sites like slackey or slack build or linuxpackages.
Having said that, perhaps it would be a good idea to add src2pkg and a network manager such as knetwork.
Another issue which I had not read about; though I have to admit that I had not read all 400 posts; is window dressing. When you meet someone for the first time, interview for a job, or test drive a car, first impression is critical. Slackware is known for stability and simplicity, but who are the users, the audience so to speak. My question is who do you want to have the product? Is Slackware looking to add new users? Or content with the current audience. If new users, the next generation, is important, then window dressing needs improvement.
In other words, the idea of changing the logo was a good start. But, slackwars was a terrible choice.
From my experience, I started with debian which locked up on a regular basis. "If this is what linux is all about, for get it," I thought to myself! By shear chance, I saw a post that 12.0 was out!. Giving it a try, I went to the slack web site and discovered that I had stopped by once before. But the site is so bland, the first time I quickly clicked on.
Furthermore, not knowing alot about computers, I tried the slack install and found it a little confusing. I had no idea what type of keyboard I had. What is a kernel? I had no idea what was a swap disk or how to set it up. Once installed, it was by chance that I previously fiddled with backtrack 2 figured out how to start x by startx etc..... It is kind of like buying your first car and not knowing that you need to change the oil.
Perhaps it would be good to accommodate to new users to gain additional interest. Modernize the looks of the website. Helpful instructions would be great for first time users. When I first installed slack 12, I had no clue of the slackbook. Updating the slackbook, setup slack bible etc.... would be good. I don't think setting up a wiki would be necessary because LQ is sort of a wiki on how to do things.
I would be glad help in updating the slackbook. The only draw back is that I am NO expert in linux or slack. But I would be glad to do what I can.
Another issue which I had not read about; though I have to admit that I had not read all 400 posts; is window dressing. When you meet someone for the first time, interview for a job, or test drive a car, first impression is critical. Slackware is known for stability and simplicity, but who are the users, the audience so to speak. My question is who do you want to have the product? Is Slackware looking to add new users? Or content with the current audience. If new users, the next generation, is important, then window dressing needs improvement.
.....
Perhaps it would be good to accommodate to new users to gain additional interest. Modernize the looks of the website. Helpful instructions would be great for first time users. When I first installed slack 12, I had no clue of the slackbook. Updating the slackbook, setup slack bible etc.... would be good. I don't think setting up a wiki would be necessary because LQ is sort of a wiki on how to do things.
I would be glad help in updating the slackbook. The only draw back is that I am NO expert in linux or slack. But I would be glad to do what I can.
I agree. I am not sure if/how Slackware wants users, but the official website puzzles me too. I find the look and feel very appropriate since it is what the rest of Slackware is like - simpe and efficient, but what do I get from the very first page (http://www.slackware.org/)?
1. 12.2 is released - good.
2. Slackware Team lost interest in KDE 4 - wrong (if not, why KDE4 in -current /testing makes news and KDE 4 in -current does not?)
3. Next Slackware is due Summer 2009 - reasonable.
4. Slackware does not care about documentation - wrong. However, a visit to the new slackbook results in http://www.slackbook.org/Changelog.txt which ends 2005-05-16.
5. No Slackware ports are alive - not sure, but possibly correct. IMHO nobody needs them since there are Slackware based distributons, but why this is still on the front page?
As for catering for new users, my experience suggests that people almost never stay with their first or second distro, with the possible exception of Ubuntu. So, catering to returning customers may be a better idea.
Now back to the subj. I guess it will be appropriate in Slackware.
Imagine it is necessary to install a Linux server that will be managed remotely at a Windows Dummy's office. Why not allow for remotely controlled installation?
Variant 1. Mr. Dummy inserts Slackware 12.3 DVD and a USB disk with the key and the new server IP. The DVD boots and starts SSH so that all the installation and maintenance can be done remotely from this moment on.
Variant 2. USB stick with readily available key, IP, boot parameters, and package list boots and installs Slackware from the DVD unattended, resulting in a server ready for remote managment.
In both cases all that is necessary on-site is to insert devices and take them away when the DVD is ejected.
I would like to see LXDE for Slackware come in one of the CD's, like XFCE4 does.
Alien Bob has an LXDE package- ( http://www.slackware.com/~alien/slackbuilds/lxde/ )
But it is only available for 12.1.
The only thing I'd like to see is the "master script" for building packages for entire distribution (i.e. for making installation DVD). After all, if Slackware includes source for every package (which is very, very, very good decision), why not include script for building your own installation DVD? For example, recompiling everything with additional compiler flags could be interesting...
Besides "master script", everything else either is already here or easy enough to get.
ErV, there is no "master script". Slackware releases are not completely re-compiled -just have a look at the file-creation dates on the packages and you'll see what I mean. Things only get recompiled when it is necessary.
ErV, there is no "master script". Slackware releases are not completely re-compiled -just have a look at the file-creation dates on the packages and you'll see what I mean. Things only get recompiled when it is necessary.
If there is no "master script" it is (IMO) not good, because manual recompiling is inefficient when there is large number of packages, especially when each package is created using slackbuild.
It is certainly possible to make such script for at least 95% of packages using scons or "gnu make" coupled with few bits of bash or python programming. I think if it is possible to make such script, it should be created, because repetative tasks should be automated.
I'm sure any such script would be welcomed by those who want to re-compile everything -and we'd all appreciate it when you have gotten it working... LOL
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.