On 30/07/2019 18:50, Bruce Dubbs via blfs-dev wrote: > On 7/30/19 5:40 AM, Pierre Labastie via blfs-dev wrote: >> On 29/07/2019 21:15, Pierre Labastie via blfs-dev wrote: >>> On 29/07/2019 18:32, Bruce Dubbs via blfs-dev wrote: > > [snip] > >> nspr >> js60 >> polkit >> libepoxy >> xorg-server >> xkeyboard-config >> Xorg Legacy >> twm >> xclock >> xterm2 >> xorg-intel-driver >> libevdev >> mtdev >> libinput >> xorg-libinput-driver >> ----------->8------- >> I've not rebooted the computer during the build, so that neither elogind nor >> dbus was running (I rebooted only after building the X drivers, before >> running >> startx). Do they need to run at some point? > > I do think the system needs to be rebooted and both dbus and elogind > bootscripts (among others) started. Then log in and try startx. > > Also I'm not sure how jhalfs handles configuration. There are a couple of > places where pam needs to be configured and there may be a couple of other > packages. >
Normally, if the configuration instructions are in the "Configuring blah" paragraph, jhalfs should be able to run them. I'm bothered by this order, because, for systemd book, we first build shadow, then systemd, then dbus (in the LFS book), then linux-pam, shadow again, then systemd again, but not dbus again (at least for using xinit). It seems to me that the order with elogind is slightly different. There is also another thing, which bothers me: instructions for the xorg server are the same in both books (sysv/elogind and systemd). So, when we add --enable-install-setuid to xorg-server, we add it in both books. But I believed it was not needed in the systemd book... Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
