aboutsummaryrefslogtreecommitdiff
path: root/public/running-golang-application-as-pid1.html
diff options
context:
space:
mode:
authorMitja Felicijan <mitja.felicijan@gmail.com>2023-10-31 10:17:43 +0100
committerMitja Felicijan <mitja.felicijan@gmail.com>2023-10-31 10:17:43 +0100
commitae24d9a8869c497537839f330384cbadb2cf687c (patch)
tree79184f1d1db6f0b8e2f7aad3a262b3a2bccdde58 /public/running-golang-application-as-pid1.html
parent409dfae3983b55ffa469a556683fab4ec70b1e99 (diff)
downloadmitjafelicijan.com-ae24d9a8869c497537839f330384cbadb2cf687c.tar.gz
Updated theme
Diffstat (limited to 'public/running-golang-application-as-pid1.html')
-rwxr-xr-xpublic/running-golang-application-as-pid1.html12
1 files changed, 6 insertions, 6 deletions
diff --git a/public/running-golang-application-as-pid1.html b/public/running-golang-application-as-pid1.html
index 12877be..3047555 100755
--- a/public/running-golang-application-as-pid1.html
+++ b/public/running-golang-application-as-pid1.html
@@ -13,7 +13,7 @@ idea, it makes a lot of sense.<blockquote><p>A unikernel is a specialized, singl
13by using library operating systems. (<a href=https://en.wikipedia.org/wiki/Unikernel>Wikipedia</a>)</blockquote><p>I really like the explanation from the article 13by using library operating systems. (<a href=https://en.wikipedia.org/wiki/Unikernel>Wikipedia</a>)</blockquote><p>I really like the explanation from the article
14<a href="https://queue.acm.org/detail.cfm?id=2566628">Unikernels: Rise of the Virtual Library Operating System</a>. 14<a href="https://queue.acm.org/detail.cfm?id=2566628">Unikernels: Rise of the Virtual Library Operating System</a>.
15Really worth a read.<p>If we compare a normal operating system to a unikernel side by side, they would 15Really worth a read.<p>If we compare a normal operating system to a unikernel side by side, they would
16look something like this.<figure><img src=/posts/pid1/unikernels.png alt="Virtual machines vs Containers vs Unikernels"></figure><p>From this image, we can see how the complexity significantly decreases with 16look something like this.<figure><img loading="lazy" src=/posts/pid1/unikernels.png alt="Virtual machines vs Containers vs Unikernels"></figure><p>From this image, we can see how the complexity significantly decreases with
17the use of Unikernels. This comes with a price, of course. Unikernels are hard 17the use of Unikernels. This comes with a price, of course. Unikernels are hard
18to get running and require a lot of work since you don't have an actual proper 18to get running and require a lot of work since you don't have an actual proper
19kernel running in the background providing network access and drivers etc.<p>So as a half step to make the stack simpler, I started looking into using 19kernel running in the background providing network access and drivers etc.<p>So as a half step to make the stack simpler, I started looking into using
@@ -184,11 +184,11 @@ and could be deployed to AWS as an EC2 instance and observing how it fares.
184But in that case, we would need to write some sort of supervisor that would 184But in that case, we would need to write some sort of supervisor that would
185run on a separate EC2 that would check if other EC2 instances are running 185run on a separate EC2 that would check if other EC2 instances are running
186properly. Remember that if your application fails, kernel panics and the 186properly. Remember that if your application fails, kernel panics and the
187whole machine is inoperable in this case.</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 187whole machine is inoperable in this case.</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
188is the ability to take an existing directory (and everything 188a lock on a Linux NFS server, which turned
189underneath it) in a ZFS filesystem and turn it into a sub-filesystem 189out to be specific to NFS v3 (which I really should have seen coming,
190of its own. One reason for wanting this is that a number of things 190since it involved NLM and lockd). Finding the NFS v4 client that
191are 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 191owns 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
192and Bradley Kuhn, are interacting on the OSI's license-discuss 192and Bradley Kuhn, are interacting on the OSI's license-discuss
193list where the're doing 193list where the're doing
194bad computer history and insisting that a guy Larry Rosen 194bad computer history and insisting that a guy Larry Rosen