vault backup: 2025-03-20 11:07:48

17 files changed, 10 insertions, 110 deletions

diff --git a/0 Inbox/Ed Sheeran tickets verkopen.md b/0 Inbox/Ed Sheeran tickets verkopen.md
new file mode 100644
index 0000000..d97b251
--- /dev/null
+++ b/0 Inbox/Ed Sheeran tickets verkopen.md
@@ -0,0 +1,9 @@
+---
+references:
+  - https://help.ticketmaster.fr/hc/en-us/articles/4407518083089-Ed-Sheeran-how-to-prepare-for-the-sale
+---
+#### **I can’t go any more and need to sell on my ticket. What do I do?**
+
+The official ticket resale will be released up to 14 days before the show, in which case we will update this information accordingly. The reselling of any Ed Sheeran ticket is strictly forbidden other than through the official face value resale platform of your original point of purchase platform or the offical app.
+
+Any Ed Sheeran ticket offered for resale elsewhere, either on or offline (including Viagogo or any other unauthorised source including all secondary ticket retail websites), will result in the entire original booking being cancelled. The original purchaser and their party will be refused admission and any other purchases they hold will also be cancelled.
\ No newline at end of file
diff --git a/0 Inbox/Image updater issue.md b/0 Inbox/Image updater issue.md
deleted file mode 100644
index 85af9ad..0000000
--- a/0 Inbox/Image updater issue.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-tags:
-  - reflectie
-  - openstack
-  - code-review
----
-There was an issue with the image updater, setting the tags on creating the image - rather than after waiting until it's completed.
-I didn't realise this would be an issue while reviewing the changes of Mohammed.
-
-Hoe kan ik mezelf trainen in het beter worden om zulke issues meteen te zien als ik er zelf niet mee bezig ben?
\ No newline at end of file
diff --git a/0 Inbox/Make filesystems.md b/0 Inbox/Make filesystems.md
deleted file mode 100644
index ffdffc0..0000000
--- a/0 Inbox/Make filesystems.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-tags:
-  - linux
-  - "#filesystem"
----
-mkfs.fat
-mkfs.ext4
-..etc 
\ No newline at end of file
diff --git a/0 Inbox/Odd taxi.md b/0 Inbox/Odd taxi.md
new file mode 100644
index 0000000..4532c71
--- /dev/null
+++ b/0 Inbox/Odd taxi.md
@@ -0,0 +1 @@
+aanrader van Bert om te kijken.
\ No newline at end of file
diff --git a/0 Inbox/Performance review maart 2025.md b/0 Inbox/Performance review maart 2025.md
new file mode 100644
index 0000000..e69de29
--- /dev/null
+++ b/0 Inbox/Performance review maart 2025.md
diff --git a/0 Inbox/Reminders.md b/0 Inbox/Reminders.md
deleted file mode 100644
index d64141f..0000000
--- a/0 Inbox/Reminders.md
+++ /dev/null
@@ -1,8 +0,0 @@
-Puffen om en om
-Nu 2 tablet
-Morgen elke dag 1
-
-15 feb 11u zaterdag <- maria jurk inkorten
-
-Manchetknopen
-3 voor de bruiloft AVBA bezoeken pak op maat maken -> ff bellen afspraak, dinsdag of vrijdag -> vrijdagochtend voorkeur 
\ No newline at end of file
diff --git a/0 Inbox/Snapshot restore procedure.md b/0 Inbox/Snapshot restore procedure.md
deleted file mode 100644
index 6a63949..0000000
--- a/0 Inbox/Snapshot restore procedure.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-tags:
-  - goba
-  - snapshot
----
-stop server if active
-
-clone snapshot -> out comes a filesystem -> `{fs-name}-clone`
-- `sudo zfs clone <snapshot> <fs-name(-clone)>`
-promote said filesystem
-- `sudo zfs promote <fs-name(-clone)>`
-rename original fs
-- `sudo zfs rename <fs-name> <fs-name-datetime>`
-rename cloned snapshot to original fs
-- `sudo zfs rename <fs-name(-clone)> <fs-name>`
-
-start server if it was active
diff --git a/0 Inbox/System feedback.md b/0 Inbox/System feedback.md
deleted file mode 100644
index 92958db..0000000
--- a/0 Inbox/System feedback.md
+++ /dev/null
@@ -1,3 +0,0 @@
-I read an article somewhere about control plane feedback: any action we take should give (direct) feedback.
-
-This idea can be extended to a control panel implementation, e.g an openstack control panel. Where any action you do provides you with instant feedback. Think of creating a server; but it fails somewhere down the line due to an IP being allocated already. We want to know that so we can try again with another IP.
\ No newline at end of file
diff --git a/0 Inbox/Taskflow.md b/0 Inbox/Taskflow.md
deleted file mode 100644
index 07e7c22..0000000
--- a/0 Inbox/Taskflow.md
+++ /dev/null
@@ -1,5 +0,0 @@
-storage layer        \
-notifications           < - > task i/o
-persistence layer /
-
-Recommended way to provide flow inputs: store parameter.
\ No newline at end of file
diff --git a/0 Inbox/Thursday,  16 Jan 2025.md b/0 Inbox/Thursday,  16 Jan 2025.md
deleted file mode 100644
index ce2c65a..0000000
--- a/0 Inbox/Thursday,  16 Jan 2025.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-tags:
-  - daily
-  - "#unfinished-tasks"
----
-# Tasks
-- [ ] Organize previous daily note
-- [ ] Configure VPN's with NetworkManager rather than systemd
-- [ ] Maria TAF overlijdensverzekering uitzoeken
-
-# Work
-- [x] Try to get a POC of taskflow resumption working
-- [ ] Implement it on the testpod
-- [x] Check snapshots production
\ No newline at end of file
diff --git a/0 Inbox/Virtual block device per QEMU.md b/0 Inbox/Virtual block device per QEMU.md
deleted file mode 100644
index 6e612d6..0000000
--- a/0 Inbox/Virtual block device per QEMU.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-tags:
-  - linux
-  - filesystem
-references:
-  - https://wiki.qemu.org/Documentation/9p_root_fs
----
-**Transparency and Shared File Access**: The classical way to deploy a virtualized OS (a.k.a. "guest") on a physical machine (a.k.a. "host") is to create a virtual block device (i.e. one huge file on host's filesystem) and leave it to the guest OS to format and maintain a filesystem ontop of that virtualized block device. As that filesystem would be managed by the guest OS, shared file access by host and guest simultaniously is usually cumbersome and problematic, if not even dangerous. A 9p passthrough-filesystem instead allows convenient file access by both host and guest simultaniously as the filesystem is just a regular subdirectory somewhere inside host's own filesystem.
\ No newline at end of file
diff --git a/0 Inbox/Write from a new-guy perspective.md b/0 Inbox/Write from a new-guy perspective.md
deleted file mode 100644
index 13c046b..0000000
--- a/0 Inbox/Write from a new-guy perspective.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-tags:
-  - note-taking
-  - 2nd-brain
----
-When documenting or noting something - I think it's always a good idea to take a new-guy perspective to it. Which means to really try and dissect and understand exactly what's being written.
\ No newline at end of file
diff --git a/0 Inbox/Writeback cache.md b/0 Inbox/Writeback cache.md
deleted file mode 100644
index 83495c4..0000000
--- a/0 Inbox/Writeback cache.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-tags:
-  - linux
-  - qemu
-  - filesystem
-references:
-  - https://avidandrew.com/understanding-disk-cache-writeback-ext4.html
-  - https://docs.kernel.org/admin-guide/sysctl/vm.html#dirty-expire-centisecs
----
-normal: write() -> cache (multiple layers) -> disk
-
-# Physical server write cache
-![[physical_write_cache.png]] 
-
-Page cache -> RAM
-
-Journal -> ensures data is fully written before the transaction is considered complete.
-`commit` mount option -> flushes cache to disk every x seconds (configurable)
-`barrier` mount option -> enables the ordering of groups of writes, controller ensures writes before barrier are written before writes after barrier.
-
-`commit` + dirty_expire_centisecs [2] ~ automatic persisting of data.
-
-If we call `sync`, `fsync` or `fdatasync` ourselves our data is forced on-disk right away by the kernel, no need to wait for commit + dirty_expirty_centisecs.
-
-# VM Write cache
- Guest has its own page cache
- ![[vm_write_cache.png]]
- 
\ No newline at end of file
diff --git a/0 Inbox/gitlab workflows.md b/0 Inbox/gitlab workflows.md
deleted file mode 100644
index e309f6e..0000000
--- a/0 Inbox/gitlab workflows.md
+++ /dev/null
@@ -1,2 +0,0 @@
-GitHub’s merge queue and GitLab’s merge train workflows
-https://techdoc.one.com/guides/gitlab/marge-bot/
\ No newline at end of file
diff --git a/0 Inbox/physical_write_cache.png b/0 Inbox/physical_write_cache.png
deleted file mode 100644
index 819c834..0000000
--- a/0 Inbox/physical_write_cache.png
+++ /dev/null
diff --git a/0 Inbox/ssh.md b/0 Inbox/ssh.md
deleted file mode 100644
index 25258cc..0000000
--- a/0 Inbox/ssh.md
+++ /dev/null
@@ -1 +0,0 @@
-automatisch throttle bij hoge throttling <- tcp doet dat ook
\ No newline at end of file
diff --git a/0 Inbox/vm_write_cache.png b/0 Inbox/vm_write_cache.png
deleted file mode 100644
index 1c63843..0000000
--- a/0 Inbox/vm_write_cache.png
+++ /dev/null