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.
It adds support for the 'discard' option in /etc/crypttab, as well as fixing a(n apparent) bug with the 'none' password option on non-swap volumes.
Is there anything I can do to have this patch included in the next release? The patch is currently for 14.1, but I could sync -current down and re-generate the patch if needed.
Well it is true that the version currently in slack is ancient (2011?). However, there is a 0.9.x branch that seems to be stable according to the website and the current version is 0.9.12.2 dating from last August. I have never used it so I cannot comment further as to whether it would actually work though. It may be too late for 14.2 depending how much of a hassle it is to compile the new version.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
Quote:
Originally Posted by volkerdi
rworkman has been testing 1.2.x and contributing code upstream for it, but without a good reason it's a bit late in the game for that one.
Understandable.
Here are the "key" features:
Quote:
The NetworkManager team just released NetworkManager 1.2, and it is the biggest update in over a year. With almost 3500 commits since the previous major release (1.0), this release delivers many new key features:
Less dependencies
Improved Wi-Fi and IPv6 privacy
Wider support for software devices
Improved command line tool
Better documentation
Support for multiple concurrent VPN sessions
Based on this post, would it be prudent to either symlink /usr/local/share/pkgconfig/ with /usr/local/lib{64}/pkgconfig/ (like it's done in /usr/) or add /usr/local/share/pkgconfig to PKG_CONFIG_PATH? Based on that post, compiz-bcop will, without setting --prefix, install its pc file to /usr/local/share/pkgconfig/ and will not be viewable by pkg-config without altering the PKG_CONFIG_PATH variable.
There are probably other programs that do this as well, but since most of my software is installed into /usr which has those two locations symlinked, it's not easy for me to find.
Since we already have the /etc/profile.d/pkgconfig.sh file and the symlink happens on /usr, I don't see any issues that one (or both) of these "fixes" might cause. Strike that, if users already have files in /usr/local/share/pkgconfig/, they'd be hidden when the symlink is done. If we were to do one, it'd probably be wise to just modify the variable to add the new location.
Well it is true that the version currently in slack is ancient (2011?). However, there is a 0.9.x branch that seems to be stable according to the website and the current version is 0.9.12.2 dating from last August. I have never used it so I cannot comment further as to whether it would actually work though. It may be too late for 14.2 depending how much of a hassle it is to compile the new version.
Actually that 0.9 branch of compiz has never been stable or useful IMO for anything outside of unity. The 0.8 branch of compiz has been given new life in the form of the compiz-reloaded project. It's basically a merger or the mate-compiz project and Scott Moreau's work of the 0.8 branch. I have been using it for a while and it works great. A lot of the old bugs and memory leaks have been fixed, plus there is now mate support which is nice. Here is their git page.
Just built and installed version 1.2.0, using the script from the slackware64-current/source/networkmanager/ directory and so far, so good.
Let me know what happens when you stop NM and try to use the system networking scripts (e.g. for a wired connection). Hint: have a look at /etc/resolv.conf :-)
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
Quote:
Originally Posted by rworkman
Let me know what happens when you stop NM and try to use the system networking scripts (e.g. for a wired connection). Hint: have a look at /etc/resolv.conf :-)
Sorry, don't follow, i.e., using system networking scripts?
Sorry, don't follow, i.e., using system networking scripts?
/etc/rc.d/rc.inet* mostly.
But then, doesn't "chmod 444 /etc/resolv.conf" suffice?
Caveat emptor: here, just a laptop used as a desktop behind an optic fiber box (link to the Internet) also used as NAT router. Nothing complicated, nothing fancy. But still I use NM to be able to move to another room.
Last edited by Didier Spaier; 04-21-2016 at 09:53 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
Quote:
Originally Posted by Didier Spaier
/etc/rc.d/rc.inet* mostly.
But then, doesn't "chmod 444 /etc/resolv.conf" suffice?
Caveat emptor: here, just a laptop used as a desktop behind an optic fiber box (link to the Internet) also used as NAT router. Nothing complicated, nothing fancy. But still I use NM to be able to move to another room.
I'm embarrassed to admit this, but I don't know what you two are talking about, other than it is network and networkmanager related.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.