On July 30, 2019 3:54:34 PM CDT, Pierre Labastie via blfs-dev 
<[email protected]> wrote:
>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.
>

IIUC above, this is because we do not have elogind in LFS, so our first build 
of dbus does not link to libsystemd (unlike in LFS-systemd). The lack of dbus 
support is inconsequential in that configuration because we are going to 
rebuild systemd later in BLFS.

>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...
>
That would be my doing as I had believed that they would be the same (and still 
believe they should be, but my attempts to find the reason for the differences 
have failed me thus far), so the two variants got merged down. In fact, I think 
I am the only one who has demonstrated that a rootless Xorg is even possible 
with elogind in our group. Five consecutive builds, all slightly different, but 
logical (apparently only to me), build orders. I'd gotten frustrated trying to 
track it down, I was simply spinning my wheels, so I put it on the back burner 
(knowing that a viable workaround exists). I'll be testing noveau on an 
existing build next week to possibly eliminate hardware/drivers. I want to also 
say that I've built entirely in chroot already, but I'm not 100% certain on 
that.

HTH

--DJ



-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to