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 would mainly like to see fewer packages. I do not use any command line mp3 players; nor do I need the plethora of news readers, chat programs. or mail programs. Don't get the idea that I am advocating eliminating these programs (as soon as something is completely deleted, I would have a great need for it & have to package it myself!), but to my mind, moving a bunch of packages to 'extra', or some new directory, would be a good idea.
Regards,
Bill
Along these lines I would love to see an option to install a bare minimum system. Now for this to really work the installation process needs a way to track all dependencies when installing packages on top of this base.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Speaking of RTFM, maybe I should recommend this program that I put together a year or so ago: http://distro.ibiblio.org/pub/linux/...6.1-i486-1.tgz
That's a nice little GUI program for searching man pages by category and includes a viewer -no joke!
The program is a hacked combination of two programs -gman and coolman, but I just couldn't resist naming it that way. No one has ever heard of the program and yet it gets recommended by name all the time...
Not bad, testing it ..... loving it xD
Congratz and thxz for sharing
I guess that any comment can lead to something helpfull, even the one from 'testing' he he
I agree with gargamel about auto-updating. It's clever from software side to suggest auto-updating when running it only as root, because he's the only one who can do it. What's wrong with letting software to auto-update itself?
I agree with gargamel about auto-updating. It's clever from software side to suggest auto-updating when running it only as root, because he's the only one who can do it. What's wrong with letting software to auto-update itself?
Along these lines I would love to see an option to install a bare minimum system.
It already does. Install the A series and nothing else, and in fact, you can probably even cull out a few of those. That's the bare minimum packages you need to have a working system. Of course, the system isn't going to be useful for many purposes, but it's a "bare minimum" working system.
Anything over and above that is entirely up to the admin. A fileserver will need different packages than a print server which will need different packages than a web server which will need different packages than a router which will need [...]
Quote:
Now for this to really work the installation process needs a way to track all dependencies when installing packages on top of this base.
I believe it was already mentioned in the topic, but your best bet for a slimed down system (without breaking anything) is to use tag files. Once you get the install down to where you like it on a working system, generate the tags for it based on the installed packages and then use those to install the next system.
Well, this is more of a cosmetic change. You know when you bootup and a penquin is on the left-hand corner of the screen, symbolizing the processor you have? Maybe instead of the penguin, it can be the head of Bob, or maybe the penguin with Bob's face on his stomach?
Well, this is more of a cosmetic change. You know when you bootup and a penquin is on the left-hand corner of the screen, symbolizing the processor you have? Maybe instead of the penguin, it can be the head of Bob, or maybe the penguin with Bob's face on his stomach?
Hey, thanks for the idea! I needed something to do! Will report back with results when done.
Changing the image in the frame-buffer during bootup would require patching the kernel -mostly a no-no in stock Slackware, even though the change would be a zero-risk thing. Still, the few times that Slackware has come with an altered or patched kernel, the changes were of a more serious nature. For instance, when the 2.4 kernel was still being used, the Slackware kernel always had a fundamental change in the code for the umsdos file system which would make sure that the underlying native FAT was read-only.
As some of my hardware is going to become outdated, I've started looking around for a new PC. And I found that almost everything is 64-bit, now. So, sooner or later, an "official" 64-bit Slackware would certainly be nice.
As some of my hardware is going to become outdated, I've started looking around for a new PC. And I found that almost everything is 64-bit, now. So, sooner or later, an "official" 64-bit Slackware would certainly be nice.
gargamel
I agree, although it looks like the Slamd64 port is pretty darned close.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.