FreeBSD Cert

Ralf Mardorf ralf.mardorf at
Sun May 31 03:11:44 UTC 2020

On Sat, 30 May 2020 22:16:42 -0400, Aryeh Friedman wrote:
>On Sat, May 30, 2020 at 9:42 PM Ralf Mardorf wrote:
>> I don't know if the hanbook mentions the following, too. Often it's
>> wiser to get in touch with upstream, to ask them to fix an issue,
>> than to fix an issue by a FreeBSD port (or any other operating
>> system's repository).  
>Depends on how active the upstream is and how critical the fix is.

Full acknowledge

>How does maintaining a wiki in and upon itself help any community?

Man(ual) pages are sometimes incomplete and even if they are complete
they seldom provide hints, to e.g. understand pitfalls.

Keep in mind something simple such as globbing. Information about
stdout, stderr... Good software without a manual at all. Pitfalls such
as immutable files, that a user even with root privileges can't remove,
due to set attributes.
Pitfalls such as
  sudo echo "1234" > test
returns "Permission denied".
Beginners usually need a hint, that sudo applies to echo, not to the
redirection, so a Wiki might inform about tee:
  echo "1234" | sudo tee test

>Just a general comment on the "no top posting" "rule" that FreeBSD has
>no one else has such a rule and many mail clients do top posting by
>default and make interleaving non-trivial (such OP's it appears).
>Additionally there is enough top posting being done on today's
>Internet that everyone should be familiar with it and know how to read
>it in context.    So we might want to recommend interleaving but it
>should not be some rule set in stone that will get any newbie flamed
>for not using it, talk about one way to turn people off to FreeBSD

In addition to ignoring bottom posting subscribers might want to send
HTML text only, break lines of posted terminal output, recursively
quote signatures or way more fun, keep the complete digest text. How
many rules could be ignored before communication becomes impossible?

Confusing the subject with the mail's body, breaking threads?

Actually it's possible to move the cursor and to delete content when
using any mail client. A lot users don't write a new mail, they push a
reply button, replace the subject and the body, so their "new" thread
actually is a reply to another thread. Moving the cursor and deleting
works when doing this, but not for bottom or interleaved posting?

Btw. even replying to digest emails does not need to break
threading and the subject:

Sometimes I'm using iPad Mail, a disgusting mailer, but it's still
possible to move the cursor and edit a reply.

Almost all mailing lists have got similar etiquettes for good reasons,
not just the FreeBSD and Linux mailing lists, also mailing lists of
upstream providing software for FreeBSD and/or Linux and even philosophers
or scientists mailing lists tend to follow those rules.

More information about the freebsd-questions mailing list