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'd prefer some sort of Slackware Bible (like Ubuntu Bible) or smth.
Yes, that would be terrific. However, I think it is a bit challenging. I guess the first thing to do is to add an easy to find text explaining what the groups created by the installer are for. I see many bugs in Slackware reviews caused by not including a regular user to some group. Possibly that should even be in the mail the installer sends to root.
Click here to see the post LQ members have rated as the most helpful post in this thread.
That's here, and it's clearly linked from the Support page.
Sure the website doesn't boast eyecandy, but then again I highly doubt anyone will first try Slackware because they are looking for something pretty.
I guess you spotted a web site problem. The site does not explain why anyone should try Slackware. An official list of design goals will help to get rid of some confusion. Example: "bla-bla no dependency tracking in packages bla" - "Please refer to the design goal #X".
I see many bugs in Slackware reviews caused by not including a regular user to some group. Possibly that should even be in the mail the installer sends to root.
That issue is dealt with in the 12.1 ncurses installer. You are prompted to add your regular user to plugdev, cdrom, audio, video, and floppy during the set-up of a user account. All you need to do is hit the up arrow button. This is not a Slackware problem, but, a failure to read during the installation procedure.
I guess you spotted a web site problem. The site does not explain why anyone should try Slackware. An official list of design goals will help to get rid of some confusion. Example: "bla-bla no dependency tracking in packages bla" - "Please refer to the design goal #X".
Agreed. Too many people look at Slackware and say something is wrong with it because they don't agree with or understand the design goals. It's like complaining a bicycle has no motor. A tool used out of its specifications will almost always be found to be undesirable.
Can pat replace Kwifi manager with wirelessassistant ?
Kwifi manager is a part of the kdenetwork package, so it is very unlikely it will get removed.
wirelessassistant could be added, but I don't know if it is considered stable enough yet. I know some of wireless tools out there are not considered stable enough for Slackware.
A script to generate initrd.gz as part of the installation might be nice. After all the installer should 'know' what it needs to generate the file. I know it is not that difficult to read the Readme file and run the command but I often seem to type it wrong and it is one of those niggly little things that would make the installation more user friendly.
Last edited by arubin; 12-18-2008 at 01:29 PM.
Reason: spelling error
I need more Cow Bell More !!!!. Thats what I need in slackware 12.2. The fact that there is know dependency program is the best thing that ever could be. and only people that understand how them rpm pacakges and deb pakages are made would agree also. just down load a deviant rpm or deb package and you have the time of your life. you may get 1000 extra libraries that will only hurt stuff you do use. trust me I spend many hours going over bad packages and I wish people would learn to type ./configure.
I need more ubuntu disks to set my coffee cup on little higher please.
Ding Ding
/me wonders if Eric's mkinitrd_command_generator.sh script will be reborn ...
Quote:
Originally Posted by brianL
I didn't know it had died.
No, I jut uploaded an updated version - PiterPUNK improved the storage hardware detection (for some computers including my T41 laptop the command would list an absurd collection of required modules).
My test-installer has this script embedded and liloconfig will use it. But it still has a lot of wrinkles that need to be ironed out...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.