[Bug 2033158] New: Grub documentation out of date in System
Administration Guide
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2033158
Bug ID: 2033158
Summary: Grub documentation out of date in System
Administration Guide
Product: Fedora Documentation
Version: devel
Status: NEW
Component: system-administrator's-guide
Assignee: pbokoc(a)redhat.com
Reporter: fedora(a)chrisirwin.ca
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Grub2 documentation is out of date in System Administrators Guide.
It explains how grub was configured in previous releases, but doesn't explain
the current configuration and tools sufficiently/
* systemd Boot Loader Specification (/boot/loader/entries)
* grubby description is inaccurate (it says it edits grub.cfg, while it looks
like it now edits /boot/loader/entries/*conf files)
* location of grub config (/boot/grub2/grub.cfg, even on EFI systems now)
* menuentries in grub.cfg (not used now)
* Gives instruction to `grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg`
several times, but that is not the proper location now
* Above command is given for "Editing a Menu Entry" to change kernel command
args, but it doesn't do that any more. grubby must be used for that task.
Version-Release number of selected component (if applicable):
Fedora 35 Documentation:
https://docs.fedoraproject.org/en-US/fedora/f35/system-administrators-gui...
Rawhide documentation appears the same.
How reproducible:
It's documentation, so every time.
Steps to Reproduce:
1. Look at Fedora documentation to see where kernel menuentries are defined
2. Documentation says /boot/efi/EFI/fedora/grub.cfg
3. That is not correct.
Actual results:
1. /boot/efi/EFI/fedora/grub.cfg is only a stub to load /boot/grub2/grub.cfg,
even on EFI systems (documentation says this file is BIOS only)
2. No kernel menu entries are defined there, either
3. Kernel menu entries defined in /boot/loader/entries/*conf files, and
probed by grub via unknown mechanism
Expected results:
Expected documentation to match and explain grub configuration on a current
Fedora system.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2033158
1 week, 5 days
[Bug 1993662] New: In F34 /usr/bin/X process is a wrapper of
/usr/libexec/Xorg
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1993662
Bug ID: 1993662
Summary: In F34 /usr/bin/X process is a wrapper of
/usr/libexec/Xorg
Product: Fedora Documentation
Version: devel
Status: NEW
Component: system-administrator's-guide
Assignee: pbokoc(a)redhat.com
Reporter: sinosuse(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
https://docs.fedoraproject.org/en-US/fedora/f34/system-administrators-gui...
command "ps aux|grep /usr/bin/X"
In f34, /usr/bin/X is linked to /usr/bin/Xorg, which is wrapper of
/usr/libexec/Xorg.
[suse@suse ~]$ ls -altr /usr/bin/X
lrwxrwxrwx 1 root root 4 Apr 14 18:58 /usr/bin/X -> Xorg
[suse@suse ~]$ ls -altr /usr/bin/Xorg
-rwxr-xr-x 1 root root 277 Apr 14 18:55 /usr/bin/Xorg
[suse@suse ~]$ cat /usr/bin/Xorg
#!/usr/bin/sh
#
# Execute Xorg.wrap if it exists otherwise execute Xorg directly.
# This allows distros to put the suid wrapper in a separate package.
basedir=/usr/libexec
if [ -x "$basedir"/Xorg.wrap ]; then
exec "$basedir"/Xorg.wrap "$@"
else
exec "$basedir"/Xorg "$@"
fi
Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.20.11-1.fc34.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
suggest to use command "ps aux|grep Xorg"
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
1 week, 5 days
[Bug 1831542] New: Documentation of PEERNTP variable
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1831542
Bug ID: 1831542
Summary: Documentation of PEERNTP variable
Product: Fedora Documentation
Version: devel
Status: NEW
Component: system-administrator's-guide
Assignee: pbokoc(a)redhat.com
Reporter: mlichvar(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The PEERNTP variable, which can be set to "no" in /etc/sysconfig/network in
order to disable use of NTP servers provided by the DHCP server, is described
in the "Configuring NTP Using ntpd" section, but not in the "Configuring NTP
Using the chrony Suite".
Both ntp and chrony follow this setting. The documentation should make it clear
that NTP servers provided by DHCP are enabled by default.
--
You are receiving this mail because:
You are the QA Contact for the bug.
1 week, 5 days
[Bug 1662306] New: TigerVNC Configuration Page out of date
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1662306
Bug ID: 1662306
Summary: TigerVNC Configuration Page out of date
Product: Fedora Documentation
Version: devel
Hardware: x86_64
OS: Linux
Status: NEW
Component: system-administrator's-guide
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: colin.henry(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Documentation does not reflect current file configuration
Version-Release number of selected component (if applicable):
Fedora 29
How reproducible:
Try and follow the instructions on the configuration page, it tells you to
change settings that aren't there. For instance, users are told to edit the
and change:
ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024"
PIDFile=/home/USER/.vnc/%H%i.pid
Whereas the actual file contains:
ExecStart=/usr/bin/vncserver -autokill %i
PIDFile=/home/<USER>/.vnc/%H%i.pid
Steps to Reproduce:
1. Go to the documentation page:
https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-gui...
2. Install tigervnc-server
3. Look at the configuration file /lib/systemd/system/vncserver@.service
Actual results:
The files differ significantly, also following the instructions in the
configuration file fails to start vnc successfully, but I'll file a bug for
that separately.
Expected results:
Configuration documentation should match the files on the host
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
1 week, 5 days