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.
Hehe, I couldn't help but think of that damn MS Word paper-clip when I read that.
Perhaps we could have a cute looking animated spanner that pops up and goes...
"It looks like you're trying to install a kernel..."
Originally Posted by AGer
Afterthought. For boot I would like mkinitrd, kernel, and slackpkg packages to be a bit smarter so that when slackpkg upgrades the kernel it could prompt "it looks like you are using generic kernel with initrd created with "mkinitrd ...". Should I recreate initrd and run LILO now?"
Hand holding? Not with my Slackware. I think that is one of the reasons loads of people use Slackware; 'KISS'!
Personally, I would like some handholding with this (and already said so in #402). I tend to leave my big updates to late at night when I can be confident of a reliable internet connection. By the time I have completed the download, updated my configuration scripts, changed boot run level so that I can recompile graphics driver and modem driver to suit the new kernel, it has become easy to make a slip in updating mkinitrd or forget to run lilo. I have had lots of practice at recovering from an unbootable partition after a kernel upgrade! I definitely do not want a paperclip aspiring to be intelligent, but a simple text prompt based on the contents of lilo.conf would seem possible. (I do not use GRUB obviously!)
Yesterday I hit a minor problem that would best be solved by the distribution itself. The command "git add -p", which allows you to pick specific file differences to be included in the next commit, requires the Error CPAN module. There could be an official package for it because it's a bit of a pain in the ass to install it and maintain it if you are not used to Perl and CPAN (I'm not).
Can you see if this is still an issue in -current now? I think the recent changes to subversion should fix this, but I'm not certain. (yes, I've had this thread noted in my TODO for a while now) :-)
Thank you very much. I think it's solved. I'm not very confident about it because I installed the module several months ago and I don't remember what I touched, but I had it installed in $HOME/perl and had a PERL5LIB environment variable pointing there. So I removed $HOME/perl, $HOME/.cpan and unset the environment variable, and it still seems to be working in a minimal test I have performed.