Updated theme

1 files changed, 5 insertions, 5 deletions

diff --git a/public/wireless-sensor-networks.html b/public/wireless-sensor-networks.html
index 279ccc2..035ee32 100755
--- a/public/wireless-sensor-networks.html
+++ b/public/wireless-sensor-networks.html
@@ -33,11 +33,11 @@ exporting settings/profile in X-CTU application. Make sure you have enabled
 “Upgrade firmware” so you can be sure each radio has the same firmware.<li>And again: make plans! Plan everything! In months advanced! You will thank me
 later :)<li>Test, test, test. Wireless networks can be tricky.</ul><p>If you are serious, I suggest you buy this book, Building Wireless Sensor
 Networks. You will get a glimpse of how networks work in lumens terms. It is a
-good starting point for everybody who wants to build wireless networks.<p><strong>Additional resources:</strong><ul><li><a href=http://www.digi.com/aboutus/export/generalexportinfo>http://www.digi.com/aboutus/export/generalexportinfo</a><li><a href=http://doresearch.stanford.edu/research-scholarship/export-controls/export-controlled-or-embargoed-countries-entities-and-persons>http://doresearch.stanford.edu/research-scholarship/export-controls/export-controlled-or-embargoed-countries-entities-and-persons</a><li><a href=http://www.bis.doc.gov/licensing/exportingbasics.htm>http://www.bis.doc.gov/licensing/exportingbasics.htm</a></ul></div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSWhyNotDirectoryToFilesystem target=_blank rel=noopener>One reason that ZFS can't turn a directory into a filesystem</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>One of the wishes that I and other people frequently have for ZFS
-is the ability to take an existing directory (and everything
-underneath it) in a ZFS filesystem and turn it into a sub-filesystem
-of its own. One reason for wanting this is that a number of things
-are set and controlled on a per-filesyst…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen
+good starting point for everybody who wants to build wireless networks.<p><strong>Additional resources:</strong><ul><li><a href=http://www.digi.com/aboutus/export/generalexportinfo>http://www.digi.com/aboutus/export/generalexportinfo</a><li><a href=http://doresearch.stanford.edu/research-scholarship/export-controls/export-controlled-or-embargoed-countries-entities-and-persons>http://doresearch.stanford.edu/research-scholarship/export-controls/export-controlled-or-embargoed-countries-entities-and-persons</a><li><a href=http://www.bis.doc.gov/licensing/exportingbasics.htm>http://www.bis.doc.gov/licensing/exportingbasics.htm</a></ul></div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/linux/NFSv4ServerLockClients target=_blank rel=noopener>Finding which NFSv4 client owns a lock on a Linux NFS(v4) server</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>A while back I wrote an entry about finding which NFS client owns
+a lock on a Linux NFS server, which turned
+out to be specific to NFS v3 (which I really should have seen coming,
+since it involved NLM and lockd). Finding the NFS v4 client that
+owns a lock is, depending on your perspective, either simpl…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen
 and Bradley Kuhn, are interacting on the OSI's license-discuss
 list where the're doing
 bad computer history and insisting that a guy Larry Rosen