mirror of
https://github.com/Zeckmathederg/glfs.git
synced 2025-02-07 09:37:17 +08:00
adf287b1be
xorg-server itself does not need libelogind/libsystemd to invoke the logind D-Bus API. elogind/systemd-logind works for Xorg server when you login: once you've logged in on a TTY, pam_systemd or pam_elogind invokes systemd-logind or elogind to modify the ACL of the device node of GPU for you: $ getfacl /dev/dri/card1 getfacl: Removing leading '/' from absolute path names # file: dev/dri/card1 # owner: root # group: video user::rw- user:xry111:rw- group::rw- mask::rw- other::--- Note that the "user:xry111:rw-" line allows the user logged in (in this example, xry111, my user account) to operate on the GPU. If systemd-logind or elogind is not installed, there will be no such a line and you need to setuid bit for Xorg executable, which is not recommended. FWIW logind is smart enough not to add the ACL entry if you've logged in via SSH. You may need to logout and login again to use startx if you've installed pam_{elogind,systemd} and Xorg server & xinit in a continous login session, but this is already mentioned on xorg-config.xml. You may ask why Xorg server links to libsystemd or libelogind. It uses sd_notify and sd_listen_fds API so the Xorg server can function as a socket-activated systemd service. This is useless in SysV: elogind is a logind, not a service manager. In Systemd the libsystemd.so installed in LFS should be enough, and we've never provided instructions to run Xorg server in BLFS as a systemd service. Reported-by: Rainer Fiebig <jrf@mailbox.org> |
||
---|---|---|
appendices | ||
archive | ||
book | ||
general | ||
gnome | ||
images | ||
introduction | ||
kde | ||
lxde | ||
multimedia | ||
networking | ||
postlfs | ||
pst | ||
server | ||
stylesheets | ||
template | ||
x | ||
xfce | ||
xincludes | ||
xsoft | ||
.gitattributes | ||
.gitignore | ||
changelog.xml | ||
expand_date | ||
general.ent | ||
git-version.sh | ||
gnome.ent | ||
index.xml | ||
INSTALL | ||
Makefile | ||
obfuscate.sh | ||
packages.ent | ||
README | ||
tidy.conf |
How do I convert these XML files to HTML? You need to have some software installed that deal with these conversions. Please read the INSTALL file to determine what programs you need to install and where to get instructions to install that software. After that, you can build the html with a simple 'make' command. The default target builds the html in $(HOME)/public_html/blfs-book. For all targets, setting the parameter REV=systemd is needed to build the systemd version of the book. Other Makefile targets are: nochunks, validate, and blfs-patch-list. nochunks: builds BLFS in one huge file. validate: does an extensive check for xml errors in the book. blfs-patch-list: generates a list of all blfs controlled patches in the book.