Event JSON
{
"id": "23a6149f045cdcb461546ca0f56a6f24a8a337899a9c4eab5b70eb02d5b37bdb",
"pubkey": "b4130b784939ff68f97723dd4552b9d84960d9caee6638e2e19c99e7055c8125",
"created_at": 1770218697,
"kind": 1,
"tags": [
[
"t",
"sysadmin"
],
[
"t",
"zfs"
],
[
"t",
"openzfsmastery"
],
[
"t",
"debian"
],
[
"emoji",
"flan_disappointed",
"https://cdn.hosted.spacebear.ee/sb-53d788bcd8441bb97cfb7a64f2552521/custom_emojis/images/000/000/128/original/0228cfb93df72667.png"
],
[
"proxy",
"https://io.mwl.io/@mwl/116013052552819852",
"web"
],
[
"proxy",
"https://io.mwl.io/users/mwl/statuses/116013052552819852",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://io.mwl.io/users/mwl/statuses/116013052552819852",
"pink.momostr"
],
[
"-"
]
],
"content": "It appears Linux root-on-ZFS is a mess. No standard way to do it. Kernel updates require recompiling ZFS. Boot environments are a cornucopia of constantly evolving hacks.\n\nIf you're actually using #ZFS on root, on #Debian, what's your preferred hack to make that happen? #sysadmin \n\nI suspect #openzfsmastery might need to assume root on extFS and data on ZFS, leaving root-on-ZFS for the advanced user or a terminal chapter. :flan_disappointed:",
"sig": "c9b982778ec9959cbebd45d78480c49199a73187e9f2d178f3cc48467d81364a8cf1a0fdfbd6808eaf754374bdb6148b9441d51d49b1f7792866ca1dc3c3a568"
}