diff options
author | mms <michal@sapka.me> | 2024-05-03 21:38:58 +0200 |
---|---|---|
committer | mms <michal@sapka.me> | 2024-05-03 21:38:58 +0200 |
commit | 126f1384861265a5548e5c4540a786ee4f6002d3 (patch) | |
tree | 6368d4deb65baf5a74e39b1928579273d76e5ccf /content-org/bsd.org | |
parent | 108c556fee08e99c575b5c4ddd55af1129ca55aa (diff) |
fix: typo
Diffstat (limited to 'content-org/bsd.org')
-rw-r--r-- | content-org/bsd.org | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/content-org/bsd.org b/content-org/bsd.org index d1d7506..5f614b9 100644 --- a/content-org/bsd.org +++ b/content-org/bsd.org @@ -201,12 +201,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. |