Hi,
The FreeBSD Handbook needs improving and I have suggestions to improve it.
Yesterday I installed FreeBSD 14-RELEASE and it was a headache.
I wanted the GNOME desktop environment, so I navigated the FreeBSD Handbook
table of contents to section 8.2.2. GNOME and followed the instructions. Th
I have given it more thought. If each desktop environment section states a
windows system needs to be installed in order to use it, then the mention of a
windows system needing to be installed in order to use a desktop environment
under section 8.1 Synopsis can be removed because the user will r
Hi,
The FreeBSD Handbook has a systematic problem where it gives literal
instructions that don't work.
For example, section 8.2.2.1. Install GNOME meta package states to execute '#
pkg install gnome', but '# ' is not part of the command. And the copy button
next to the command includes the '#
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
Another idea that I think is better is to bring the sudo package into the base
system. This would then mean the FreeBSD Handbook wouldn't need to
systematically indicate or state the command requires superuser privileges.
So instead of the FreeBSD Handbook incorrectly stating to execute this...
Hi,
The FreeBSD Handbook inconsistently uses both the flow of wording and
terminology when giving instructions. When I say the flow of wording, I mean
syntax.
Section 20.12.2. Setting Quota Limits states "To verify that quotas are
enabled, run:".
Section 20.13.1. Disk Encryption with gbde st
After giving it more thought, I think using the terminology with the flow 'run
the command:' is good.
'Running a command', 'running a program' and 'running an app' are not always in
the same context. 'run the command' makes the context clearer in this regard.
