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.
actually I had already included kmod, as I missed it for something, although unfortunately I don't remember exactly what right now. I will check how big is a container with these packages added.
actually I had already included kmod, as I missed it for something, although unfortunately I don't remember exactly what right now. I will check how big is a container with these packages added.
Tue Jun 20 05:08:21 UTC 2017
...
ap/lxc-2.0.8-x86_64-1.txz: Upgraded.
Since lxc 2.x.x, starting containers was simplified, the screen -dmS construction isn't needed anymore.
man lxc-start
Quote:
-d, --daemon
Run the container as a daemon. As the container has no more tty, if an error occurs nothing will be displayed, the log file can
be used to check the error. (This is the default mode)
Suggested patch to simplify the startup-script:
Code:
diff -ru ../lxc.orig/rc.lxc ./rc.lxc
--- ../lxc.orig/rc.lxc 2016-04-26 00:00:00.000000000 +0200
+++ ./rc.lxc 2017-02-21 16:43:44.000000000 +0100
@@ -17,11 +17,7 @@
if [ "$(lxc-info -n $CONTAIN -c lxc.start.auto)" = "lxc.start.auto = 1" ]; then
if [ "$(/usr/bin/lxc-info -s -n $CONTAIN | grep STOPPED$)" ]; then
echo "Starting LXC container ${CONTAIN}."
- if [ -x /usr/bin/screen ]; then
- /usr/bin/screen -dmS init-${CONTAIN} /usr/bin/lxc-start -n $CONTAIN
- else
- /usr/bin/lxc-start -n $CONTAIN -d
- fi
+ /usr/bin/lxc-start -n $CONTAIN
/usr/bin/lxc-wait -n $CONTAIN -s RUNNING
if [ $? -gt 0 ]; then
return 2
The x264 developers are playing hardball and the latest x264 from git will not compile with the version of nasm shipped with Slackware -current. Minimum version required by x264 is now nasm-2.13:
Code:
Found no assembler
Minimum version is nasm-2.13
If you really want to compile without asm, configure with --disable-asm.
Edit: It is a bit of a tussle to add to Slackware because of this insanity with building docs. Under -current these perl modules are required:
IO::String
Font::TTF::Font
Sort::Versions
as well as installation of Clear-Sans font pack. An option to disable docs would be better I suspect but it all works now and x264 is happy again...
And the docs that it fails building (bloated PDFs) are ones that we never even packaged! The only docs we've packaged are the info files, and they've apparently dropped support for creating those as well. Anyway, it's easy enough to quit having the SlackBuild try to make all the docs and have it only make the .txt file instead, so we'll do that. I imagine this one should be a bugfix for 14.2 also so that people don't run into problems trying to build the latest with the SBo script.
IF we arrive to rebuilding/upgrading the LAMP stack, I would like to suggest (again) the addition of XMLRPC support to PHP.
This is used by PHP to make RPC API calls to other sites, and heavily used by complex monsters like Moodle, a widely used e-Learning Platform, but also very useful for (and used by) CMS engines like Drupal or Joomla!
We have the following associated build options for this XMLRPC support:
Code:
--with-xmlrpc
This will build the XMLRPC as built-in support, introducing a very small increase in PHP binaries size.
OR
Code:
--with-xmlrpc=shared
This will build the XMLRPC support as a shared library, optionally loaded at run-time.
Last edited by Darth Vader; 06-25-2017 at 01:59 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
