Download raw body.
[www] faq/current.html - fix order
On 2026/01/13 10:13, Raf Czlonka wrote:
> Hello,
>
> Historically, the entries in faq/current.html[0] were sorted in
> reverse chronological order.
Not true, new entries are normally added to the end. The dates are not
always in order because they usually refer to the date when the relevant
change was made, not when they were added to current.html
> Also, I fixed the anchors by dropping ":" from the URL, i.e.:
>
> "://foo" -> "//foo"
>
> I'm guessing that dlg@ wanted the links to work regardless of whether
> the page is viewed via either HTTP or HTTPS - now it works fine.
I'll commit that bit
> While there, move the HTML comment from the bottom of the page to
> just before the first entry, where it is more useful.
>
> [0] https://www.openbsd.org/faq/current.html
>
> Regards,
>
> Raf
>
> Index: faq/current.html
> ===================================================================
> RCS file: /cvs/www/faq/current.html,v
> diff -u -p -r1.1146 current.html
> --- faq/current.html 12 Jan 2026 04:40:40 -0000 1.1146
> +++ faq/current.html 13 Jan 2026 10:12:42 -0000
> @@ -56,6 +56,44 @@ use a snapshot to recover.
> <p>
> Most of these changes will have to be performed as root.
>
> +<!--
> + Two blank lines before new sections.
> + New sentences start on new lines.
> + Try to make lines shorter than 80 characters.
> +-->
> +
> +
> +<h3 id="r20260112">2026/01/12 - LACP mode removed from trunk(4)</h3>
> +
> +IEEE 802.3ad/802.1AX Link Aggregation Control Protocol support has
> +been removed from <a href="//man.openbsd.org/trunk.4">trunk(4)</a>.
> +trunk(4) LACP configuration can be moved to
> +<a href="//man.openbsd.org/aggr.4">aggr(4)</a>,
> +the dedicated IEEE 802.1AX Link Aggregation network interface driver.
> +
> +<p>
> +aggr(4) is compatible with trunk(4) with two exceptions:
> +
> +<ol>
> +<li>
> +aggr(4) uses a random MAC by default, trunk(4) uses the MAC of the
> +first-added child port.
> +
> +<li>
> +aggr(4) needs to be configured up explicitly.
> +</ol>
> +
> +<p>
> +An example of migrating configuration for trunk0 to aggr0:
> +
> +<pre class="cmdbox">
> +# <b>cd /etc</b>
> +# <b>ifconfig trunk0 | awk '/lladdr/ { print "lladdr $2" } > hostname.aggr0</b>
> +# <b>cat hostname.trunk0 >> hostname.aggr0</b>
> +# <b>echo up >> hostname.aggr0</b>
> +# <b>rm hostname.trunk0</b>
> +</pre>
> +
> <h3 id="r20251122">2025/11/22 - [packages] PostgreSQL major update</h3>
>
> <p>
> @@ -184,44 +222,6 @@ Rebuild the system as usual.
> </pre>
>
> </ol>
> -
> -
> -<h3 id="r20260112">2026/01/12 - LACP mode removed from trunk(4)</h3>
> -
> -IEEE 802.3ad/802.1AX Link Aggregation Control Protocol support has
> -been removed from <a href="://man.openbsd.org/trunk.4">trunk(4)</a>.
> -trunk(4) LACP configuration can be moved to
> -<a href="://man.openbsd.org/aggr.4">aggr(4)</a>,
> -the dedicated IEEE 802.1AX Link Aggregation network interface driver.
> -
> -<p>
> -aggr(4) is compatible with trunk(4) with two exceptions:
> -
> -<ol>
> -<li>
> -aggr(4) uses a random MAC by default, trunk(4) uses the MAC of the
> -first-added child port.
> -
> -<li>
> -aggr(4) needs to be configured up explicitly.
> -</ol>
> -
> -<p>
> -An example of migrating configuration for trunk0 to aggr0:
> -
> -<pre class="cmdbox">
> -# <b>cd /etc</b>
> -# <b>ifconfig trunk0 | awk '/lladdr/ { print "lladdr $2" } > hostname.aggr0</b>
> -# <b>cat hostname.trunk0 >> hostname.aggr0</b>
> -# <b>echo up >> hostname.aggr0</b>
> -# <b>rm hostname.trunk0</b>
> -</pre>
> -
> -<!--
> - Two blank lines before new sections.
> - New sentences start on new lines.
> - Try to make lines shorter than 80 characters.
> --->
>
> <hr id="end">
> <small>$OpenBSD: current.html,v 1.1146 2026/01/12 04:40:40 dlg Exp $</small>
>
[www] faq/current.html - fix order