Hi Helge, At 2023-01-23T18:47:42+0100, Helge Kreutzmann wrote: > On Mon, Jan 23, 2023 at 12:54:23AM -0600, G. Branden Robinson wrote: > > At 2023-01-22T22:22:02+0100, Alejandro Colomar wrote: > > > On 1/22/23 20:31, Helge Kreutzmann wrote: > > > > Without further ado, the following was found: > > > > > > > > Issue 1: runlevel 2 → run-level 2 > > > > > I believe the fix would be to use runlevel everywhere. run-level is > > > not correct under any point of view, if I'm correct. > > > I therefore recommend "run level". > > I'm fine with either version. Currently, it is mixing both, so it > should "just" be unifrom (at least throught linux man pages). Agreed. Fortunately, it appears that boot(7) is the only page in the Linux man-pages project that needs revision; no other document uses the term in the forms I checked for. $ git grep 'run level' || echo no matches no matches $ git grep 'runlevel' || echo no matches man7/boot.7:.BR runlevel (8). man7/boot.7:runlevel 2. man7/boot.7:.BR runlevel (8), $ git grep 'run.level' || echo no matches man7/boot.7:program is instructed to enter a particular \fIrun-level\fR, giving man7/boot.7:for some usage; each run-level is associated with a set of services man7/boot.7:(for example, run-level \fBS\fR is \fIsingle-user\fR mode, man7/boot.7:and run-level \fB2\fR entails running most network services). man7/boot.7:run-level via man7/boot.7:and query the current run-level via man7/boot.7:To make specific scripts start/stop at specific run-levels and in a man7/boot.7:To define the starting or stopping order within the same run-level, man7/boot.7:To manage these links is to manage the boot order and run-levels; The cross reference to the systemd "runlevel" man page of course should be kept as-is. Regards, Branden
Attachment:
signature.asc
Description: PGP signature
