stif,
Don't remember precisely when, but I added this in rc.sysinit (It was needed by cups daemon)

Code:

ifconfig lo up

ping localhost and ping 127.0.0.1 work this way, could you test that or maybe I should make replacement in rc.sysinit with

Code:

ifconfig lo up 127.0.0.1

Edit: For starting dbus looks like /etc/init.d/messagebus needs some fixing, it reports missing /run/dbus/system_bus_socket.
And only reason I added exec dbus-launch $WINDOW_MANAGER in /root/.xinitrc was to get thumbnails to show in thunar (tumbler used it).
In spacefm thumbnails are shown without it, but something else might need dbus-daemon so I'll leave this line.Last edited by simargl on Tue 22 Jan 2013, 16:43; edited 3 times in total

I followed this guide http://chakra-linux.org/wiki/index.php/D-Bus and after adding
dbus group and user and changing PIDFILE=/var/run/dbus/pid to PIDFILE=/run/dbus/pid
in /etc/init.d/messagebus dbus seems to start regularly.
No need for launching dbus within /root/.xinitrc so that line is removed.

What do you think about this? Is it possible to setup wireless this way? Obviously this needs
fixing for static IP, but it's just beginning. Also, I'm not at all expert in all of those different network
configurations so your help is welcome (and needed).

I followed this guide http://chakra-linux.org/wiki/index.php/D-Bus and after adding
dbus group and user and changing PIDFILE=/var/run/dbus/pid to PIDFILE=/run/dbus/pid
in /etc/init.d/messagebus dbus seems to start regularly.
No need for launching dbus within /root/.xinitrc so that line is removed.

Scooby,
Try removing /run/dbus/pid that file should be there only if dbus-daemon is already running,
Did you replace PIDFILE in /etc/init.d/messagebus? After that try /etc/init.d/messagebus start
and /etc/init.d/messagebus stop, for me it's working.

mavrothal wrote:

Are you looking to replace Pwireless/Frisbee/SNS etc?

No, I will leave Pwireless included it seems to work OK. It will not change unless sometime someone make
GUI ( preferably in yad) for wireless connections that will store variables in rc.conf, and read them on system boot.
But, nothing is wrong with Pwireless - judging by user comments it's working fine .

A lot of stuff is wrong with Pwireless. It won't work with my wifi device, even if the module for it is loaded. Yes, I am using Slacko 5.4's non-pae kernel in ArchPup 12.12.2 and it should work, but it does not._________________What consenting adults do in their bedroom is none of your business so if you think there is something wrong with homosexuality and your bothered by it, then you're an idiot who needs to mind their own business.

A lot of stuff is wrong with Pwireless. It won't work with my wifi device, even if the module for it is loaded. Yes, I am using Slacko 5.4's non-pae kernel in ArchPup 12.12.2 and it should work, but it does not.

Unless you intent to fix it your self, statements like this do not help in any way.
What about providing /tmp/xerrors.log (were pwireless writes its successes/failures), your wifi card model and the kernel messages that show that everything is fine (or not) with it, etc, so either solve the problem or establish that Pwireless is indeed problematic. _________________Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too

Why so?_________________What consenting adults do in their bedroom is none of your business so if you think there is something wrong with homosexuality and your bothered by it, then you're an idiot who needs to mind their own business.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum