summaryrefslogtreecommitdiff
path: root/content/bsd
diff options
context:
space:
mode:
authormms <michal@sapka.me>2024-05-03 21:38:58 +0200
committermms <michal@sapka.me>2024-05-03 21:38:58 +0200
commit126f1384861265a5548e5c4540a786ee4f6002d3 (patch)
tree6368d4deb65baf5a74e39b1928579273d76e5ccf /content/bsd
parent108c556fee08e99c575b5c4ddd55af1129ca55aa (diff)
fix: typo
Diffstat (limited to 'content/bsd')
-rw-r--r--content/bsd/why-bsd.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/bsd/why-bsd.md b/content/bsd/why-bsd.md
index 7e9d4e6..faa5a9f 100644
--- a/content/bsd/why-bsd.md
+++ b/content/bsd/why-bsd.md
@@ -169,12 +169,12 @@ Well, OpenBSD, FreeBSD, NetBSD, and DragonFly BSD are separate operating systems
They are developed separately and have separate teams.
And even though the code very often migrates between them, they are not the same.
-Just an example: PF, the great pocket filter was developed as part of OpenBSD.
+Just an example: PF, the great packet filter was developed as part of OpenBSD.
It was then ported to FreeBSD.
It worked great, but with time, it diverged from the OpenBSD's one quite significantly, and all those changes had to be ported again, just recently.
Since OpenBSD and FreeBSD grew out of Unix, they are binary compatible, but their kernels differ significantly.
FreeBSD and OpenBSD have different goals, and therefore are diverging more and more.
-Pocket Firewall needs to be fast, so it needs to interact closely with the kernel.
+Packet Firewall needs to be fast, so it needs to interact closely with the kernel.
This means that all attempts to align PF on these systems requires significant effort.
Another example: ZFS.