RE: Improvements for the future FreeBSD Handbook

2024-01-01 Thread Kolusion K
But is the current FreeBSD Handbook even the fourth edition?! It doesn't actually state what edition it is. Perhaps its the Five Edition and both the Fourth Edition and Third Edition sections are incorrectly claiming to be the current version??   And this another example of why the FreeBSD

Improvements for the future FreeBSD Handbook

2024-01-01 Thread Kolusion K
Hi I have been reading the current FreeBSD Handbook. Much of it is straight the point which I appreciate, but I have found a substantial amount of irrelevant information in it. For example, the document includes sections Third Edition, Second Edition (2004), and First Edition (2001). These

RE: Clearly explain images

2024-01-01 Thread Kolusion K
After reading over my last e-mail, I think the button [Download now] can just be [Download].

Clearly explain images

2024-01-01 Thread Kolusion K
Hi When I was obtaining FreeBSD I didn't know if I had to download the CD image or the DVD image. I tried to find an explanation but it doesn't exist. I had to take a 'lucky shot' and download the one I thought was the one for my needs. Luckily it was the right one, but if it hadn't been then

Non-existent system requirements

2024-01-01 Thread Kolusion K
Hi, The FreeBSD Handbook has a problem where section 2.2. Minimum Hardware Requirements states the hardware architectures and devices supported by a FreeBSD release are listed on the FreeBSD Release Information page. There is three problems with this: 1. The release information page doesn't

Re: Inconsistent use of both flow of wording and terminology

2023-12-31 Thread Kolusion K
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.

Inconsistent use of both flow of wording and terminology

2023-12-31 Thread Kolusion K
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

Re: Systematic broken instructions

2023-12-31 Thread Kolusion K
pm > From: "Kolusion K" > To: freebsd-doc@freebsd.org > Subject: Systematic broken instructions > > 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

Systematic broken instructions

2023-12-31 Thread Kolusion K
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

RE: Suggestions to improve the FreeBSD handbook

2023-12-31 Thread Kolusion K
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

Suggestions to improve the FreeBSD Handbook

2023-12-31 Thread Kolusion K
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.