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.
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.
> The /etc/sysconfig/rc.site is sourced so we need to change rc.site with
> something like:
>
> RUNSUBS="${RUNSUBS} dbus"
>
> and add to mountvirtfs:
>
> for D in ${RUNSUBS}; do mkdir -p $D; done
>
> For other subdirectories of /var/run we would only need to add
>
> RUNSUBS="${RUNSUBS} subdir"
>
> to the end of rc.site.
>
> A second option would be to just hard code any needed directories like
> we do with {var,lock,shm}. A directory entry is negligible if it is not
> used.
>
> A third option would be to add it to the dbus bootscript, but that is
> not required if the user is just adding dbus-launch to the appropriate
> line in the ~/.xinitrc file.
>
> Comments?
>
> -- Bruce
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.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
