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.
Those fonts are high quality than existing CJK fonts in slackware-current, it would be great if Slackware could have them as official packages for CJK users.
Those are essentially noto-cjk, which is already part of alienBOB's Plasma 5 packages. noto-cjk will very likely make it into -current at one point together with Plasma 5, but until then it's probably best to get it from alienBOB's ktown repo.
Those are essentially noto-cjk, which is already part of alienBOB's Plasma 5 packages. noto-cjk will very likely make it into -current at one point together with Plasma 5, but until then it's probably best to get it from alienBOB's ktown repo.
I look forward to see Noto-CJK fonts make their way in Slackware.
By the way and following post #2270 I confirm that mlterm works in a framebuffer, although I see some issues that I hope can be sorted out. This seems to bring proper display of complex scripts (including bidi for e.g. a mix of Arabic or Persian and English) and CJK. I have tested this displaying Japanese and Persian man pages for slackpkg and pkgtools, using for CJK NotoSansCJK.ttc.zip dowloaded from https://www.google.com/get/noto/ (didn't know Eric had packaged it. They also have serif now).
Additionally since last release mlterm searchs alternative glyphs in other fonts automatically on framebuffer and wayland if it is built with freetype and fontconfig (yes, it is ready for wayland too). In other words thanks to fontconfig additional fonts bringing the glyphs missing in currently in use font(s) are automatically searched for and loaded, as under X.
So my hope is that mlterm on a framebuffer can be a good alternative to dead or otherwise limited projects as fbterm, kmscon and bogl/bterm (the latter used in Debian text installer). I will post a request for testing in some time in a separate thread.
Last edited by Didier Spaier; 05-11-2017 at 11:08 AM.
I tested Didier's NVME install patches which were merged into -current and they work well.
However, it would be great to have nvme-cli included as a package in -current, and the nvme binary included in the installer initrd.
That way one can properly (re-)format an nvme (if required) prior to installing.
So, AMD just released the open-source opencl stack. It's possible now to use opencl in Blender and such without the closed amdgpu-pro. It would be great to have it as standard in Slackware.
So, AMD just released the open-source opencl stack. It's possible now to use opencl in Blender and such without the closed amdgpu-pro. It would be great to have it as standard in Slackware.
Sorry, this is nowhere close to be ready. We can take a look once the llvm/clang changes are merged and released.
I finally made the test... recompiled the kernel with CONFIG_CIFS_SMB2, mounted the share with "-o vers=2.0" - it simply worked. So while kerberos is a requirement for some use cases it doesn't seem to be a hard requirement for SMB2/3.
Environment: Slackware64-14.2 + SMB share on a WD NAS box.
Qt 5 was officially released on 19 December 2012. Is it stable enough for Slackware yet?
Quote:
Originally Posted by mralk3
It will probably be upgraded if/when KDE4 is replaced with plasma 5.
Agreed.
It is likely that we'll see the move from KDE4 to Plasma 5 this cycle since KDE4 development has pretty much ceased except for security fixes. All major development has moved to Plasma 5. Alien Bob already has packages for Plasma 5 for -current in his ktown repo, so as soon as Pat is ready to throw the switch, it should be relatively easy to move to it.
-current's alpine and imapd seem compiled without IPv6 support.
To support IPv6 properly, "IP=6" is needed when building alpine.
Please consider.
Code:
--- alpine.SlackBuild.orig 2017-03-21 17:54:00.000000000 +0900
+++ alpine.SlackBuild 2017-05-17 14:56:22.260335179 +0900
@@ -96,7 +96,7 @@
# Build and install:
# Since we build non-compliant to RFC3501 we have to answer 'y' half-way:
-echo y | make EXTRACFLAGS="-fPIC" SSLTYPE=unix || exit 1
+echo y | make EXTRACFLAGS="-fPIC" SSLTYPE=unix IP=6 || exit 1
make install SSLTYPE=unix DESTDIR=$PKG || exit 1
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
