You can run it multiple times as well, and even over multiple files (though I find it easier to do one file at a time

and use the `git rebase -i` to fold the related commits together).

**Q:** How do I join the FreeBSD GitHub organization?

[.filename]#src/.mailmap#, [.filename]#doc/.mailmap#, and [.filename]#ports/.mailmap# - Add an entry for commits you created prior to becoming a FreeBSD committer.

+

Mapping to your FreeBSD address allows us to track external committers who may be ready for a commit bit more easily.

. Generate a Kerberos Password

+

See crossref:committers-guide[kerberos-ldap, Kerberos and LDAP web Password for FreeBSD Cluster] to generate or set a Kerberos account for use with other FreeBSD services like the link:https://bugs.freebsd.org/bugzilla/[bug-tracking database] (you get a bug-tracking account as part of that step).

Gandi offers an E-rate discount to all FreeBSD developers.

To streamline the process of getting the discount first set up a Gandi account, fill in the billing information and select the currency.

[[benefits-rsync]]

=== `rsync.net`

[[releng-stable]]

== Release from {branchStable}

[[releng-stable-slush]]

=== FreeBSD `stable` Branch Code Slush

When all the files of the status report are ready, it is time to publish it.

First [.filename]#doc/website/content/en/status/_index.adoc# is edited: the next due date is updated and a link to the new report is added.

Then the news entry for the main website page is added to [.filename]#doc/website/data/en/news/news.toml#.

These functions are called from the `g_down` kernel thread and there can be no sleeping in this context, (see definition of sleeping elsewhere) which limits what can be done quite a bit, but forces the handling to be fast.

[[geom-threads]]

=== GEOM Threads

Sleeping is well and very convenient but can very effectively destroy performance of the geom transformation.

Extremely performance-sensitive classes probably should do all the work in `.start`() function call, taking great care to handle out-of-memory and similar errors.

This is also very convenient but can be slow.

In most cases, handling of `.done`() requests can be left to the `g_up` thread.

# gjournal label -s 2G /dev/ada1p1

....

[source,shell]

....

When `fsck_ffs(8)` is later invoked during boot, it reads this state from the superblock and skips the file system check.

For Soft Updates with journaling, recovery is initiated by `fsck_ffs(8)` itself.

If journal replay reports that the file system is consistent, `fsck_ffs(8)` terminates early without performing a full check.

If journal replay cannot complete successfully, a traditional file system check is performed.

=== Mirroring Packages

Due to very high requirements of bandwidth, storage and administration the FreeBSD Project has decided not to allow public mirrors of packages.

Alternatively specific packages and their dependencies can be fetched by running something like the following:

[source,shell]

The preferred order is the copyright notice first, followed by the SPDX-License-Identifier, but either order is acceptable.

When both SPDX-License-Identifier and the full text of the license are present, the full text takes priority and the SPDX-License-Identifier is informational only.

The FreeBSD project does not allow using the "advertising clause" in new code.

Due to the large number of contributors to the FreeBSD project, complying with this clause for many commercial vendors has become difficult.

You cannot duplicate IRQ 3 because the output drivers of each UART are wired in a "totem pole" fashion, so if one of the UARTs drives IRQ 3, the output signal will not be what you would expect.

Depending on the implementation of the extension board or your motherboard, the IRQ 3 line will continuously stay up, or always stay low.

The solution was proposed by Joerg Wunsch mailto:j@ida.interface-business.de[j@ida.interface-business.de]: To solder up a wired-or consisting of two diodes (Germanium or Schottky-types strongly preferred) and a 1 kOhm resistor.

Here is the schematic, starting from the 4 by 3 jumper field above:

The scope of this article will be limited to solid state disk devices made from flash memory.

Flash memory is a solid state memory (no moving parts) that is non-volatile (the memory maintains data even after all power sources have been disconnected).

One very important aspect of flash memory, the ramifications of which will be discussed later in this article, is that each sector has a limited rewrite capacity.

You can only write, erase, and write again to a sector of flash memory a certain number of times before the sector becomes permanently unusable.

Although many flash memory products automatically map bad blocks, and although some even distribute write operations evenly throughout the unit, the fact remains that there exists a limit to the amount of writing that can be done to the device.

For example, a very old Kodak Duaflex IV camera in my possession has three such holes for f-numbers 8, 11, and 16.

A more recently made camera may offer f-numbers of 2.8, 4, 5.6, 8, 11, 16, 22, and 32 (as well as others).

[[x86-f-stop]]

==== The F-Stop

To solve the conflict, we use the `std` op code early on.

We cancel it with `cld` later on: It is quite important we do not `call` anything that may depend on the default setting of the _direction flag_ while `std` is active.

It is a classical example of the adage that programming requires a lot of thought and only a little coding.

Once we have thought through every tiny detail, the code almost writes itself.

....

For detailed usage and features, refer to man:accerciser[1].

and the https://help.gnome.org/users/accerciser/stable/index.html.en[Accerciser User Guide].

== Mouse

[[mouse-apparance]]

Some desktop environments allow you to change the size, color, and other graphical properties of the mouse cursor.

====

Alternatively, you can achieve the same result via the `xfconf-query` command.

[source,shell]

....

[[find-mouse-cursor]]

=== Find Cursor

[[kde-find-mouse-cursor]]

==== KDE Plasma

[[biblio-cheriton]] Cheriton, 1988 The V Distributed System D. R.Cheriton 314-333 Comm ACM, 31, 3 March 1988

[[biblio-gingell]] Gingell et al, 1987 Virtual Memory Architecture in SunOS R.Gingell J.Moran W.Shannon 81-94 USENIX Association Conference Proceedings USENIX Association June 1987

[[biblio-macklem]] Macklem, 1994 The 4.4BSD NFS Implementation R.Macklem 6:1-14 4.4BSD System Manager's Manual O'Reilly & Associates, Inc. Sebastopol CA 1994

[[biblio-mckusick-1]] McKusick et al, 1994 Berkeley Software Architecture Manual, 4.4BSD Edition M. K.McKusick M. J.Karels S. J.Leffler W. N.Joy R. S.Faber 5:1-42 4.4BSD Programmer's Supplementary Documents O'Reilly & Associates, Inc. Sebastopol CA 1994

If we would like to support jumbogram properly, the field must be expanded to hold 4G + IPv6 header + link-layer header.

Therefore, it must be expanded to at least int64_t (u_int32_t is NOT enough).

* TCP code needs a careful update in bunch of places, of course.

==== Loop Prevention in Header Processing

Now following two items are required to be supported by standard drivers:

. mbuf clustering requirement. In this stable release, we changed MINCLSIZE into MHLEN+1 for all the operating systems in order to make all the drivers behave as we expect.

If any of the drivers do not support the requirements, then the drivers cannot be used for IPv6 and/or IPsec communication.

If you find any problem with your card using IPv6/IPsec, then, please report it to the {freebsd-bugs}.

* Put each file system on its own disk. This minimizes jitter from head-seek optimizations.

* Minimize output to serial or VGA consoles. Running output into files gives less jitter. (Serial consoles easily become a bottleneck.) Do not touch keyboard while the test is running, even kbd:[space] or kbd:[back-space] shows up in the numbers.

* Make sure the test is long enough, but not too long. If the test is too short, timestamping is a problem. If it is too long temperature changes and drift will affect the frequency of the quartz crystals in the computer. Rule of thumb: more than a minute, less than an hour.

* Run the test at least 3 times but it is better to run more than 20 times both for "before" and "after" code. Try to interleave if possible (i.e.: do not run 20 times before then 20 times after), this makes it possible to spot environmental effects. Do not interleave 1:1, but 3:3, this makes it possible to spot interaction effects.

+

A good pattern is: `bababa{bbbaaa}*`.

Some graphics cards may have excessive power consumption.

FreeBSD allows certain configurations to improve power consumption.

[.programlisting]

....

[[kde-environment]]

=== Plasma

This desktop provides a suite of applications with a consistent look and feel, a standardized menu and toolbars, keybindings, color-schemes, internationalization, and a centralized, dialog-driven desktop configuration.

More information on Plasma can be found at the link:https://kde.org/plasma-desktop[Plasma homepage].

Next, in the main console window, install a package, such as man:zip[1] which has no dependencies.

Once that completes, renter the monitor and create another snapshot (`snap1_pkg+zip`).

[[qemu-after-monitor-snapshots]]

.QEMU Using Monitor Commands for Snapshots

====

It has been reported that ZFS users may experience issues with some Wayland clients because they need access to `posix_fallocate()` in the runtime directory.

While the author could not reproduce this issue on their ZFS system, a recommended workaround is not to use ZFS for the runtime directory and instead use `tmpfs` for the [.filename]#/var/run# directory.

The XDG_RUNTIME_DIR environment variable could be configured to use [.filename]#/var/run/user/$UID# and avoid potential pitfalls with ZFS.

Consider that scenario when reviewing the configuration examples in the following sections.

====

WINE can be installed via the pkg tool, or by compiling the port(s).

[[wine-prerequistes]]

Before installing WINE itself, it is useful to have the following pre-requisites installed.

....

This creates a versioning scheme that increases over time, and that is still before version `0`.

[source,shell]

....

[.procedure]

. If this is a new file, does it have a [.filename]#.sh# extension? If so, that must be changed to just [.filename]#file.in# since [.filename]#rc.d# files may not end with that extension.

. Do the name of the file (minus [.filename]#.in#), the `PROVIDE` line, and `$` _name_ all match? The file name matching `PROVIDE` makes debugging easier, especially for man:rcorder[8] issues. Matching the file name and `$`_name_ makes it easier to figure out which variables are relevant in [.filename]#rc.conf[.local]#. It is also a policy for all new scripts, including those in the base system.

. Does the script start a persistent service? If so, it must have `KEYWORD: shutdown`.

. Make sure there is no `KEYWORD: FreeBSD` present. This has not been necessary nor desirable for years. It is also an indication that the new script was copy/pasted from an old script, so extra caution must be given to the review.

. If the script uses an interpreted language like `perl`, `python`, or `ruby`, make certain that `command_interpreter` is set appropriately, for example, for Perl, by adding `PERL=${PERL}` to `SUB_LIST` and using `%%PERL%%`. Otherwise,

Possible arguments: (none)

[[uses-tar]]

== `tar`