Ken Moffat wrote:
> On Thu, Dec 15, 2011 at 07:10:04PM -0600, Bruce Dubbs wrote:
>> More on D_BUS. The install creates /var/run/dbus, but that will go away
>> with a reboot. We need to figure out a way to create it upon boot.
>
> Is that a theoretical problem, or is it actually broken on your
> system ? The dbus init.d script has mkdir -p /run/dbus with the
> pidfile and socket defined to be in /var/run/dbus/ so therefore
> beneath/run/dbus at runtime.
>
> It appears to work on my box.
The problem is that the dbus boot script is not required. A user can
just add it to ~/xinitrc:
dbus-launch --exit-with-session startfluxbox
I need to do more testing on this.
> But, in view of your continuing investigation of the dbus
> dependencies, I won't spend any more time on dbus.
>> The first LFS boot script, mountvirtfs, does:
>>
>> mkdir -p /run
>> mount -n /run || failed=1
>> mkdir -p /run/{var,lock,shm}
>>
>
> As well as Wayne's earlier problem with perms on /run/shm (totem, I
> think) my own attempt to try pulse also failed because it was not
> 1777.
Yes, I think that needs to be done. Right now it's 0755. It's a change
needed in LFS.
> Ah, I see, you build dbus but not the bootscripts. AFAIK, the
> bootscript has been required for a long time. I see no obvious
> reason to add dbus-launch to .xinitrc.
I've updated the dbus boot script, but not committed it yet.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
