#1544 closed defect (invalid)
Gnome utilities, errors in command explanations
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | BOOK | Version: | SVN |
| Severity: | minor | Keywords: | |
| Cc: | hugo@… |
Description
In the "Command Explanations" section, there is an invalid reference to "ScrollKeeper":
--localstatedir=/var/lib: This switch puts ScrollKeeper files in /var/lib/ scrollkeeper instead of $GNOME_PREFIX/var/scrollkeeper.
Also, there is an explanation for a pam-related switch, which is not present int he installation instructions:
--with-pam-prefix=/etc/pam.d: This switch puts PAM files in /etc/pam.d instead of /etc/gnome.
Change History (7)
comment:1 by , 19 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 19 years ago
For Gnome Utilities, PAM is optional. For GDM, PAM is also optional except that the "--with-pam-prefix=/etc/pam.d" switch is present in the installation instructions. I don't know what is the BLFS convention on optional packages and switches, but personnaly I think it is best done like in the GDM package, although it would be better to use a comment like "Use this switch if you have PAM installed in order to put PAM files in /etc/pam.d instead of /etc/gnome."
comment:3 by , 19 years ago
If you can figure out how to download, compile and make 'consolehelper' work in a BLFS environment, and you can show that there are PAM files written to /etc/pam.d, I'll gladly add that stuff to the book.
As is, there are no files written into /etc/pam.d, so there is no need to mention a switch.
comment:4 by , 17 years ago
consolehelper is provided my usermod, which in turn depends on libuser.
With consolehelper installed /etc/pam.d/gnome-system-log and /etc/pam.d/security/console.apps/gnome-system-log are created.
comment:6 by , 17 years ago
In the build I just did running gnome-system-log died with:
Failed to find selected program.
This was because /etc/security/console.apps/gnome-system-log had NONE/sbin/gnome-system-log as the program to be run. The reason for the NONE is the way $sbindir was expanded in configure. I wrote a patch changing the way it is expanded so it always expands to an absolute path.
The patch is at http://cross-lfs.org/~jciccone/gnome-utils-2.16.1-logviewdir_fix-1.patch .
Marking this bug as invalid.
1) The reference to ScrollKeeper is required. 2) the PAM related switch is simply documentation to let folks know stuff