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 know slackware no goes in to no "stable released packages" ... but is possible 1.1.0 released sortly and think is better 1.1.0 than recompiled 1.0.29.
I suggest to ship in packages a/pkgtools and ap/slackpkg the 120 localized man pages gathered in the archives in http://slint.fr/localized_man_pages/
They are provided in following languages, thanks to the Slint translators:
Code:
Code Language Suggested console font
de German ter-1*
el Greek ter-7*
es Spanish (Latin America) ter-1*
fa Persian bicon-8x16-512*[1]
fr French ter-1*
id Indonesian ter-1*
it Italian ter-1*
nb Norwegian ter-1*
nl Dutch ter-1*
pt_BR Portuguese (Brazil) ter-1*
pt_PT Portuguese (Portugal) ter-1*
ru Russian ter-k*
sv Swedish ter-1*
tr Turkish ter-9*
uk Ukrainian ter-c*
Notes:
All these man pages are encoded in UTF-8, so GROFF_ENCODING should be set to UTF-8.
To display a man page in a given language, LANG should be set to a locale encoded in UTF-8 and beginning with the relevant code in the left column above.
For instance for Dutch following locales can be used:
Code:
~$ for i in $(locale -a|grep ^nl);do LANG=$i; echo -n "$i ";locale -k charmap;done|grep UTF-8|cut -d ' ' -f 1
nl_AW
nl_BE.utf8
nl_NL.utf8
Then to display "man installpkg" in Dutch, for instance:
Code:
GROFF_ENCODING=UTF-8 LANG=nl_AW man slackpkg
For a proper display in Persian, use mlterm available from http://slackbuilds.org. An acceptable display can be obtained with this command:
Code:
LANG=fa_IR GROFF_ENCODING=UTF-8 man <man page>|fribidi --nobreak --wrtl|most
It should go without saying that the font used should include all the needed glyphs. Under X or in an adapted framebuffer the font DejaVuSansMono, for instance, covers all these languages.
[1]Fonts not shipped in Slackware, provided by bicon available from http://slackbuilds.org
Last edited by Didier Spaier; 11-08-2015 at 11:17 AM.
Reason: s/can be get/can be obtained/
Recently I have migrated my system to a different disk. It's rather a flawless task.
But (from my point of view) it could be simpler if mkinitrd supported the following options:
1) possibility to specify an alternative configuration file,
2) chroot,
3) possibility to prepend another image.
1) I'm using mkinitrd.conf, because I prefer it over specifying all the arguments on the command line. The point is that I'm using partitions ID as opposed to /dev/sd* so it's easier/faster for me to keep them in config file. When you're migrating to a different disk, you have to change the IDs accordingly, so that's the point when it's important to be able to use alternative configuration file (that is I leave the original config file intact and only modify the config that resides in /etc on the disk that I'm migrating to.
2) This is more of a "visual" thingy. If the disk I'm migrating to is mounted on /mnt/tmp then when I create the initrd for the new disk, then when the new disk is booted, the initrd path will read something like: /mnt/tmp/boot/initrd.gz, where clearly this is not the truth.
3) It's not my case at the moment, but more and more people are gonna need the microcode to be updated early in the boot. For that reason it would be preferable to be able to prepend another image before the actual initrd image. This should be doable in the config file and also on command line.
For 3) to be painless experience, also the stock kernel configuration should have all the relevant CONFIG_MICROCODE_* set to =y.
The Perl script xscreensaver-text that comes with XScreenSaver 5.33 uses deprecated regular expression syntax, which causes Perl 5.22.0 to emit a deprecation warning, which appears on text-emitting screensavers.
You can see the warning at the beginning of the output when you run `xscreensaver-text --program fortune`.
The version of the script bundled with XScreenSaver 5.34 has the updated regular expression syntax.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
