What features/changes would you like to see in future Slackware?
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Coming back to the original question, I think that we'll see a switch to UTF-8 encoding as the default locale setting some day soon.
I think it has been a very good decision not to switch, so far, as it was good to wait for developers enabling their programs for Unicode support, first. However, the time to make the move is close, IMHO, for reasons of interoperability. Almost any other major distro is UTF-8 based, now. When I copy files from Slackware with some German special characters in their names, these characters aren't displayed correctly on the target system.
Ah, hmm. Yes, I'd like to see some more modern boot manager as the default. Although LILO has never let me down.
Nowadays, with large harddrives in desktop systems, multiboot scenarios are becoming the standard. Boot managers like GRUB offer more flexibility and are more friendly when you have a typo in your config file: Just type the correct syntax and boot, then correct the typo in the config file.
With LILO you need to have another system to boot with, correct the error and then reboot. It works, but it's just a little less comfortable.
This is low-priority wish, though, but it's good to see that GRUB made into /extra, meanwhile. 8-)
Just to answer the sd* or hd* names for hard disk devices, it's just that recent 2.6 kernels have actually two drivers for PATA and SATA devices, the old one, using /dev/hd* for PATA devices and /dev/sd* for SATA devices, and the one based on libata, which uses /dev/sd* for all ata devices and /dev/sr* for optical recorders and readers (CD, DVD). The kernel is moving to use the new libata-based driver so there won't be much choice going this way in the future. I've been using this libata-based drivers for quite some time now and it works well. Changing was essentially a matter of booting once on a CD to change lilo/grub and the /etc/fstab and then now further problems.
As for what I would like in the new Slackware, I think what could be really improved is wifi support. There are many drivers not yet in the kernel (madwifi, rt2XXX) that could be provided and indeed the way Slack currently handle the network changes is not quite dynamic and could be improved.
For the rest, most basic libraries and tools are already there : I usually compile by myself only about 20 projects to get my usual system running. I understand Pat is a bit blocked in including media projects that could yield to legal issues in the States (libdvdcss, ffmpeg, xvid, transcode) but that's easy to compile them by myself. Apart from that, adding Codeine and/or Kaffeine to KDE would be nice (they're way better than xine-ui). I'm really quite interested in KDE4 but I don't expect it in the next Slackware, as I bet KDE4.0 will be a bit too buggy to be chosen. An available QT4 would be nice though.
But on the whole, Slack is really perfect for me as it is.
I've responded to this thread before. After reading more response(s) and thinking about what has been said. I would like the New SlackwareŽ release to be more SlackwareŽ like than be M$ Windows like. I don't need another Ubuntu or RH, FC or whatever, just SlackwareŽ.
PV & team have done a great job too date. I can modify my system as I wish. I use utilities & applications within or add to my system when I need anything. That is the glory of SlackwareŽ!
Sure there are some minor problems that could be addressed in a future release (I'm sure PV is well aware of the current issues).
We can wish for and suggest a whole bunch of ideas for a release but it boils down to what PV will include in the final. If you follow '-current' then a good picture of the new SlackwareŽ distribution will develop.