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 really hope Pat does something with Network manager. It will not do a simple dhcpcd . Before everyone jumps on this and says I do not understand it.
Network manager has three things to do
1 bring the device up
2 make a hand shake
3 use crypto or not.
Other wise it prety much useless.
If it works for you on a fresh install I am on mars then.
Me and Bob sucking down some some cosmic babes.
I comment in some threads
1 - service not stopped if use more than 1 time , only aparently works the first time , later cant manage wireless devices
2 - dhcpcd for some users no work , need change to dhcp , and dhcp=internal , i think no work for no one.
3 - if want system autoconnect to your wifi at start time, need to check ..."all can connect to this network" ...or no connect on start up
all seems to be related to some permission problem, the question is
wow thanks for the wonderful reply. I just want it to work on a simple wired line.
I can just use default dhcpcd /etc/rc.inet1 but you know what caused this weird thing while I was a work.
I have a shop by my home out back hre on campus. Att came in to add the Uverse phone to my modem.
The guy was so nice as he set my modem back to factory reset.
heck who cares about the 2 severs and a virtual world simulator that we develop on.
His little laptop said reset. Which took me about ten hours of getting with people that used that UUID.
after that it screwed up. Had to just use /etc/rc.d/rc.inet.1 just wonder why after this last
networkmanager update that it no longer does what it is designed to do.
I am telling you it is a conspiracy and I need a cosmic babe.
Dhcpcd has really been fickle with NetworkManager. Nothing new really. The issue for me really was prevalent and noticeable when I tried out the SBo OpenRC script and init helper set. Dhcpcd just would not work period.
As UsuarioNuevo said, try dhcp=internal or dhcp=dhclient in the configuration file. Dhclient from the dhcp package tends to be more sane in how it operates. If you use dhcpcd, just use it by itself from netconfig.
Note: /usr/man/man6/maze.6.gz will replace the same file included in xgames-0.3. I suggest either rename maze from xscreensaver to xmaze and the manpage to xmaze.6.gz or do something similar for xgames.
The no-expiration-patch for xscreensaver needs to be updated because it does not apply to the new sources. Updated patch :
Code:
diff -U3 -d -r -N xscreensaver-5.35/driver/prefs.c xscreensaver-5.35.fixed/driver/prefs.c
--- xscreensaver-5.35/driver/prefs.c 2016-05-24 05:08:27.000000000 +0200
+++ xscreensaver-5.35.fixed/driver/prefs.c 2016-05-29 10:29:07.578127838 +0200
@@ -1734,6 +1734,14 @@
shipping the last version with the old license and then never
upgrading it again -- which would be the worst possible outcome for
everyone involved, most especially the users.
+
+ NOTE: This feature is disabled by Slackware... we do not ship multi-year
+ old versions, nor do we think it is a good idea to include nag screens
+ that activate when an expiration date is reached. In this case, the
+ nag screen was activated after only one year, which practically insures
+ that this will be seen before the next stable Slackware release.
+ If there's a problem that needs fixing, we'll issue a fix.
+ No nag screens please. Thanks for possibly reconsidering this!
*/
time_t now = time ((time_t *) 0); /* */
@@ -1766,5 +1774,7 @@
months = ((((tm->tm_year + 1900) * 12) + tm->tm_mon) - /* h */
(y * 12 + m)); /* p */
/* . */
- return (months >= 17); /* */
+ /* Disable date checking for Slackware: */
+ /* return (months >= 17); */
+ return ( 0 );
}
Last edited by DarkVision; 05-29-2016 at 03:52 AM.
Reason: Added patch file...
I don't remember having issues using NetworkManager, so my guess is that it's hardware related stuff.
I have flawless operation using Ethernet, WiFi and mobile broadband.
$ cat /etc/NetworkManager/NetworkManager.conf
# /etc/NetworkManager/NetworkManager.conf
#
# See additional config files (such as for DHCP settings) in ./conf.d
$ cat /etc/NetworkManager/conf.d/00-dhcp-client.conf
[main]
# Choose a DHCP client below. Upstream recommends dhclient, but results may vary.
# dhcpcd is the DHCP client usually used by Slackware:
dhcp=dhcpcd
# dhclient is the ISC reference DHCP client, part of the dhcp package:
#dhcp=dhclient
# This is a simple DHCP client that is built into NetworkManager:
#dhcp=internal
$ cat /etc/NetworkManager/conf.d/00-rc-manager.conf
[main]
rc-manager=file
I don't have a need to restart NM daemon, so I really don't know how it behaves after restarting.
Quote:
3 - if want system autoconnect to your wifi at start time, need to check ..."all can connect to this network" ...or no connect on start up
Isn't it sufficient to set the "Automatically connect to this network when it is available" ?
Note: The sources are available as .tar.xz only but the Slackbuild script is using different search patterns for the source version (tar.?z*) and the tar archive (tar.xz). This minor issue is similar to the python-setuptools patch. Suggested patch:
OK, just a minor, really minor and more cosmetic fix:
Some packages seem to set the package version using a search pattern like '.tar.?z*' which includes tar.xz, .tar.bz2 and .tar.gz. On the other hand the SlackBuilds are using a hardcoded .tar.xz command to untar the sources. Examples are here and here.
A small and quick dirty fix (not recommended) would be to use the following sed-command:
I'm sure the above command can be fixed to add a variable using the search pattern and fix the two locations of the archive format using that variable. This is just a first try:
Dhcpcd has really been fickle with NetworkManager. Nothing new really. The issue for me really was prevalent and noticeable when I tried out the SBo OpenRC script and init helper set. Dhcpcd just would not work period.
Thanks ReaperX7 I will fiddle with it. Jiggle the handle LOL. I am sure it isn't writing to the /etc/NetworkManager/NetworkManager.conf
I also think it has to do with kwallet on user level as root it should not have been a problem. I Think.
Yeah, I'm not sure why it seems to work with Slackware's bsd-init scripts, but with OpenRC it doesn't work until you switch it to dhclient. It's still problematic, and each time I fiddle with the package, I check the NetworkManager.conf and reset the dhcp backend to dhclient.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.