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 was wondering why the installation instructions finish up with:
"Finish the base Slackware installation. Eventually, chroot into the newly installed environment and replace the HUGE kernel by the GENERIC kernel. That's what I usually do."
It doesn't really say why, is it a recommendation for running MLED or just something you do personally?
Since MLED is basically Slackware under the hood, this is the way folks are supposed to run Slackware.
Since MLED is basically Slackware under the hood, this is the way folks are supposed to run Slackware.
I'm not sure that's the case, the default kernel selected by the Slackware installer is huge.s, you just hit enter to boot it or hit F12 if you want something else.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
Quote:
Originally Posted by kikinovak
This is exactly my feeling. Let's see if I can persuade folks to make the move.
The Whisker Menu for Xfce, as mentioned by Woodsman (thanks, again), would be a nice addition to MATE. I never cared for the default KDE menu, a la XP, but find the Whisker Menu to be the perfect compromise between the "classic" menu and the "XP style" menus.
Last edited by cwizardone; 04-14-2014 at 04:13 PM.
I'm not sure that's the case, the default kernel selected by the Slackware installer is huge.s, you just hit enter to boot it or hit F12 if you want something else.
That's during installation and even if you hit F2 you won't be proposed a generic kernel because at time of installation it couldn't boot by lack of the proper drivers built in.
But even if you can continue using a huge kernel afterwards, using a generic one is recommended (but of course not mandatory), as for instance that can help select the proper drivers for your devices. The only caveat is that you need to make an initrd for it.
As MATE and Xfce appear to be very similar, I wonder how hard it would be to tweak Whisker Menu to work in MATE? Not that I have the first clue as to where to begin. :-)
Last edited by cwizardone; 04-14-2014 at 06:16 PM.
I'm not sure that's the case, the default kernel selected by the Slackware installer is huge.s, you just hit enter to boot it or hit F12 if you want something else.
The HUGE kernel is a one-size-fits-all kernel that can be used for the installation phase. Once Slackware is installed, you're supposed to switch to the GENERIC kernel. Check out the README.initrd file:
The Whisker Menu for Xfce, as mentioned by Woodsman (thanks, again), would be a nice addition to MATE. I never cared for the default KDE menu, a la XP, but find the Whisker Menu to be the perfect compromise between the "classic" menu and the "XP style" menus.
I like it too. I even gave mintmenu a spin, but unfortunately it's quite complicated to integrate, and quite resource-hungry.
Niki:
Here's a n00bish question... is MLED only for French-speaking users?
All the screenies I glanced at show the French language on menus and such.
Thanks!
Hi Habitual,
No, of course not. MLED officially supports french, english and german, though you can of course define any other language under the sun. The "official" languages mainly concern the menu entries. IMHO, a minor flaw on many Linux desktops are the rather non-intuitive menu entries, what with the quirky application names and all (Caja? Pluma? Engrampa? WTF?). This can be solved quite easily, and since I fluently speak three languages, I rewrote nearly all the desktop menu entries and replaced them by something more intuitive (Burning Application, Instant Messaging, Word Processor, ...) and added a little script which installs these files. Using this script is not mandatory, so you can still use MLED even if you're hungarian or korean. Simply edit /etc/profile.d/lang.sh and set your language to something like en_US.utf8.
Actually, it's a matter of choice. If you have no problem with huge kernel, then use it.
People use generic kernel so that they can decide which modules should be loaded and which should not.
For debugging purpose, it's easier to be done in generic, so that's why most article/people recommend to use generic kernel, even though you have to make an initrd for that before it can be used normally.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
@willysr,
Many thanks for your MATE packages. It was a lot of hard work and is greatly appreciated.
Quote:
Originally Posted by kikinovak
I like it too. I even gave mintmenu a spin, but unfortunately it's quite complicated to integrate, and quite resource-hungry.
You mean to incorporate the Whisker Menu into Xfce as the default application menu?
As to resources... you are the expert, but I just did an comparison of the standard application menu vs Whisker, using the task manager and GKrellm to check the memory usage. Just booting up to the Xfce desktop and giving it a few seconds to settle down, the Whisker menu appears to use 19 megs less memory than the standard application menu. OTOH, I might have been doing something wrong, it wouldn't be the first time.
Last edited by cwizardone; 04-15-2014 at 08:33 AM.
The HUGE kernel is a one-size-fits-all kernel that can be used for the installation phase. Once Slackware is installed, you're supposed to switch to the GENERIC kernel. Check out the README.initrd file:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.