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 use grub as a boot manager and agree that it would be easier to be given the choice of grub or lilo when installing. Only a few months ago I would have been agreeing with fancylad that other packages should be included in extra, however now that I am more comfortable with slackware I realize the method in the madness. It is the chassing all over the internet for information and packages that is the fun and the learning process.
The oracle knows best - Leave it as it is!!!!!
Click here to see the post LQ members have rated as the most helpful post in this thread.
I think you are missing my point sombragris. When I'm installing Slackware there is no other OS on my system so I need to write something to my MBR.
Oh well. Point taken. I did not realize that. I stand corrected ...
Quote:
Originally Posted by fancylad
And even if you are writing to the first sector of your root partition you will still have to write to that sector each time you change something in lilo.conf. Again this is not such a big deal, but in my mind it is better to not have to have a program keep reinstalling itself just because you have made a change to it's config file.
I understand that too. I don't see the problem, however.
Alien BOB's politics reply here might be of interest to you.
FWIW there is one *kit i like, webkit and its the only one id welcome in Slackware
Woh, I didn't know alienbob had a blog, thanks for the link. Ok so I'm not the only one in the world who has/takes issue with these *kits.
I thought maybe I was ranting like an old fuddy-duddy.
I ran across this *kit issue's with gnome, and was a pita to get it working, which I did finally get, but so much changes per gnome release that you need to rework everything.
Now I see KDE dev's claiming they want to reduce redundancy and use these tool kit's.
Have they *any* idea what bringing the *kit's will do, oh my, oh my. And I see that XFCE power manager is doing the same thing too!
All I can say is, if we need these *kit to provide security, I'd like these dev's to show us where/who/how gnu/linux boxen are getting PWNED by hackers that we need these tools. I know alot of the people here follow the news in the linux world, but I can't seem to recall *ever* hearing of someone hacked, box getting rooted that would've been thwarted by these measures.
For $DIETY's sake, I don't need $KIT to:
1.) surf the web
2.) check email
3.) play a cd
4.) edit photo's
5.) change a wallpaper/theme
6.) turn on a pc and turn it off
7.) use a thumb drive
8.) type a letter
9.) run a simple home finance app
The above 1 thru 9 is majority of desktop pc use. I don't understand this logic.
GNU/linux get's whacked for having user's needing to edit text files in console if/when a thing here or there may/might-if-ever go awry, now they have to edit XML file's too! oh great.
Last edited by Old_Fogie; 02-02-2010 at 02:30 PM.
Reason: dumb forums lost all my carriage returns,
I use grub as a boot manager and agree that it would be easier to be given the choice of grub or lilo when installing. Only a few months ago I would have been agreeing with fancylad that other packages should be included in extra, however now that I am more comfortable with slackware I realize the method in the madness. It is the chassing all over the internet for information and packages that is the fun and the learning process.
The oracle knows best - Leave it as it is!!!!!
Lilo has two fundamental advantages over GRUB. First, it can be uninstalled guaranteed. Second, if something tough happens, it may still be able to boot the OSes that survived the event. I guess this is why there was no Slackware branding on boot for so long.
Thus, as far as GRUB is in extra, there is no real problem. I agree that it would be nice to add GRUB as an option in the installer, but I doubt there are no more important things to do before that.
I guess Slackware should introduce some dependency tracking before considerable amount of packages may be added. As it is now, a package from slackbuilds assumes that full Slackware is installed. For example, the Eclipse slackbuild assumes Java is present. So, the normal way to run Slackware is to install all of it. Without dependency tracking more packages will mean more mandatory updates.
I also think that keeping software fresh is more important than providing it as binary. Having more software is more important than keeping it fresh. Thus, more binary packages are the least priority.
Speaking of new packages, I would like Slackware to allow things that can take care for themselves to do so and free resources for the development team. Why not just unpack that which can be unpacked to /opt?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,086
Rep:
Quote:
Originally Posted by Old_Fogie
Woh, I didn't know alienbob had a blog, thanks for the link. Ok so I'm not the only one in the world who has/takes issue with these *kits.
I thought maybe I was ranting like an old fuddy-duddy.
I ran across this *kit issue's with gnome, and was a pita to get it working, which I did finally get, but so much changes per gnome release that you need to rework everything.
Now I see KDE dev's claiming they want to reduce redundancy and use these tool kit's.
Have they *any* idea what bringing the *kit's will do, oh my, oh my. And I see that XFCE power manager is doing the same thing too!
All I can say is, if we need these *kit to provide security, I'd like these dev's to show us where/who/how gnu/linux boxen are getting PWNED by hackers that we need these tools. I know alot of the people here follow the news in the linux world, but I can't seem to recall *ever* hearing of someone hacked, box getting rooted that would've been thwarted by these measures.
For $DIETY's sake, I don't need $KIT to:
1.) surf the web
2.) check email
3.) play a cd
4.) edit photo's
5.) change a wallpaper/theme
6.) turn on a pc and turn it off
7.) use a thumb drive
8.) type a letter
9.) run a simple home finance app
The above 1 thru 9 is majority of desktop pc use. I don't understand this logic.
GNU/linux get's whacked for having user's needing to edit text files in console if/when a thing here or there may/might-if-ever go awry, now they have to edit XML file's too! oh great.
A) my keybindings burned into my memory for my new mini i3 window manager;
B) Familiar with SciiTE editor, to replace my dependency on KWrite.
C) Find a Konqueror replacement I am happy with (I must admit, Konq is great when it isn't acting up).
Speaking of new packages, I would like Slackware to allow things that can take care for themselves to do so and free resources for the development team. Why not just unpack that which can be unpacked to /opt?
I would remove XFCE. It is very buggy, panels are always disappearing, you have to change manually your keyboard layout every session and some other minor problems. Let's not waste DVD space with it, in my opinion.
I would remove XFCE. It is very buggy, panels are always disappearing, you have to change manually your keyboard layout every session and some other minor problems. Let's not waste DVD space with it, in my opinion.
I use 'XFCE' and don't have the issues that you mention. Possibly a problem with your configuration or hardware? What are the minor problems not mentioned?
I would remove XFCE. It is very buggy, panels are always disappearing, you have to change manually your keyboard layout every session and some other minor problems. Let's not waste DVD space with it, in my opinion.
I'm sorry to hear you're having issues with XFce. XFce is perfectly stable for me. I'm not experiencing any of the issues that you are describing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.