home.social

#read-only — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #read-only, aggregated by home.social.

fetched live
  1. 🤖🚨 Oh no, the almighty #Wikipedia is in *read-only mode* because a bunch of #admins forgot their passwords! Now we can all take a break from editing and pretend to be surprised that #security might be an afterthought. 😱🔒
    wikimediastatus.net #ReadOnly #Breach #ForgotPasswords #EditingBreak #HackerNews #ngated

  2. 🤖🚨 Oh no, the almighty #Wikipedia is in *read-only mode* because a bunch of #admins forgot their passwords! Now we can all take a break from editing and pretend to be surprised that #security might be an afterthought. 😱🔒
    wikimediastatus.net #ReadOnly #Breach #ForgotPasswords #EditingBreak #HackerNews #ngated

  3. 🤖🚨 Oh no, the almighty #Wikipedia is in *read-only mode* because a bunch of #admins forgot their passwords! Now we can all take a break from editing and pretend to be surprised that #security might be an afterthought. 😱🔒
    wikimediastatus.net #ReadOnly #Breach #ForgotPasswords #EditingBreak #HackerNews #ngated

  4. 🤖🚨 Oh no, the almighty #Wikipedia is in *read-only mode* because a bunch of #admins forgot their passwords! Now we can all take a break from editing and pretend to be surprised that #security might be an afterthought. 😱🔒
    wikimediastatus.net #ReadOnly #Breach #ForgotPasswords #EditingBreak #HackerNews #ngated

  5. 🤖🚨 Oh no, the almighty #Wikipedia is in *read-only mode* because a bunch of #admins forgot their passwords! Now we can all take a break from editing and pretend to be surprised that #security might be an afterthought. 😱🔒
    wikimediastatus.net #ReadOnly #Breach #ForgotPasswords #EditingBreak #HackerNews #ngated

  6. Ok... this is weird. One of my #Raspis decided to not start some services after a reboot. Turns out the / file system was read only. Somehow, /etc/fstab got a "o" at the end of the line for the root file system.

    Remounted rw, removed this "o" from fstab, rebooted and everything is back to normal.

    e2fsck showed no errors so... ??? Maybe modifying files via an SSH client on a tiny smartphone screen is not the best idea.

    #raspi #fstab #readonly #filesystem

  7. Ok... this is weird. One of my #Raspis decided to not start some services after a reboot. Turns out the / file system was read only. Somehow, /etc/fstab got a "o" at the end of the line for the root file system.

    Remounted rw, removed this "o" from fstab, rebooted and everything is back to normal.

    e2fsck showed no errors so... ??? Maybe modifying files via an SSH client on a tiny smartphone screen is not the best idea.

    #raspi #fstab #readonly #filesystem

  8. Ok... this is weird. One of my #Raspis decided to not start some services after a reboot. Turns out the / file system was read only. Somehow, /etc/fstab got a "o" at the end of the line for the root file system.

    Remounted rw, removed this "o" from fstab, rebooted and everything is back to normal.

    e2fsck showed no errors so... ??? Maybe modifying files via an SSH client on a tiny smartphone screen is not the best idea.

    #raspi #fstab #readonly #filesystem

  9. Ok... this is weird. One of my #Raspis decided to not start some services after a reboot. Turns out the / file system was read only. Somehow, /etc/fstab got a "o" at the end of the line for the root file system.

    Remounted rw, removed this "o" from fstab, rebooted and everything is back to normal.

    e2fsck showed no errors so... ??? Maybe modifying files via an SSH client on a tiny smartphone screen is not the best idea.

    #raspi #fstab #readonly #filesystem

  10. Ok... this is weird. One of my decided to not start some services after a reboot. Turns out the / file system was read only. Somehow, /etc/fstab got a "o" at the end of the line for the root file system.

    Remounted rw, removed this "o" from fstab, rebooted and everything is back to normal.

    e2fsck showed no errors so... ??? Maybe modifying files via an SSH client on a tiny smartphone screen is not the best idea.

  11. One of the most fundamental yet little-known features of FreeBSD is its ability to be used in read-only mode very easily. By installing the system on a UFS file system, you just need to modify the fstab file, change "rw" to "ro," and reboot. On the next boot, the system will automatically create mount points in RAM for the main directories (/tmp, log, etc.), and it will run perfectly.

    This was the main reason why, many years ago, I chose FreeBSD for almost all my embedded systems. Even today, on my Raspberry Pies, I keep the SD cards in read-only mode and use external storage in read-write mode. This ensures that, in case of an unexpected poweroff, the system will come back up, and there will be no wear on the memory card.

    #FreeBSD #EmbeddedSystems #RaspberryPi #ReadOnly #SysAdmin #Tech #OpenSource

  12. One of the most fundamental yet little-known features of FreeBSD is its ability to be used in read-only mode very easily. By installing the system on a UFS file system, you just need to modify the fstab file, change "rw" to "ro," and reboot. On the next boot, the system will automatically create mount points in RAM for the main directories (/tmp, log, etc.), and it will run perfectly.

    This was the main reason why, many years ago, I chose FreeBSD for almost all my embedded systems. Even today, on my Raspberry Pies, I keep the SD cards in read-only mode and use external storage in read-write mode. This ensures that, in case of an unexpected poweroff, the system will come back up, and there will be no wear on the memory card.

    #FreeBSD #EmbeddedSystems #RaspberryPi #ReadOnly #SysAdmin #Tech #OpenSource

  13. One of the most fundamental yet little-known features of FreeBSD is its ability to be used in read-only mode very easily. By installing the system on a UFS file system, you just need to modify the fstab file, change "rw" to "ro," and reboot. On the next boot, the system will automatically create mount points in RAM for the main directories (/tmp, log, etc.), and it will run perfectly.

    This was the main reason why, many years ago, I chose FreeBSD for almost all my embedded systems. Even today, on my Raspberry Pies, I keep the SD cards in read-only mode and use external storage in read-write mode. This ensures that, in case of an unexpected poweroff, the system will come back up, and there will be no wear on the memory card.

    #FreeBSD #EmbeddedSystems #RaspberryPi #ReadOnly #SysAdmin #Tech #OpenSource

  14. One of the most fundamental yet little-known features of FreeBSD is its ability to be used in read-only mode very easily. By installing the system on a UFS file system, you just need to modify the fstab file, change "rw" to "ro," and reboot. On the next boot, the system will automatically create mount points in RAM for the main directories (/tmp, log, etc.), and it will run perfectly.

    This was the main reason why, many years ago, I chose FreeBSD for almost all my embedded systems. Even today, on my Raspberry Pies, I keep the SD cards in read-only mode and use external storage in read-write mode. This ensures that, in case of an unexpected poweroff, the system will come back up, and there will be no wear on the memory card.

    #FreeBSD #EmbeddedSystems #RaspberryPi #ReadOnly #SysAdmin #Tech #OpenSource

  15. One of the most fundamental yet little-known features of FreeBSD is its ability to be used in read-only mode very easily. By installing the system on a UFS file system, you just need to modify the fstab file, change "rw" to "ro," and reboot. On the next boot, the system will automatically create mount points in RAM for the main directories (/tmp, log, etc.), and it will run perfectly.

    This was the main reason why, many years ago, I chose FreeBSD for almost all my embedded systems. Even today, on my Raspberry Pies, I keep the SD cards in read-only mode and use external storage in read-write mode. This ensures that, in case of an unexpected poweroff, the system will come back up, and there will be no wear on the memory card.

    #FreeBSD #EmbeddedSystems #RaspberryPi #ReadOnly #SysAdmin #Tech #OpenSource

  16. @kuf so much important climate science needs #semantifying - making it so you can ask questions of the content as to being #readonly - here is a recent example US Plan for Energy Decarbonisation - guess what - just one big PDF Blob - #nomorepdfblobs heh? mastodon.social/@Snoro/1112517

  17. @kuf so much important climate science needs #semantifying - making it so you can ask questions of the content as to being #readonly - here is a recent example US Plan for Energy Decarbonisation - guess what - just one big PDF Blob - #nomorepdfblobs heh? mastodon.social/@Snoro/1112517

  18. @kuf so much important climate science needs #semantifying - making it so you can ask questions of the content as to being #readonly - here is a recent example US Plan for Energy Decarbonisation - guess what - just one big PDF Blob - #nomorepdfblobs heh? mastodon.social/@Snoro/1112517

  19. @kuf so much important climate science needs #semantifying - making it so you can ask questions of the content as to being #readonly - here is a recent example US Plan for Energy Decarbonisation - guess what - just one big PDF Blob - #nomorepdfblobs heh? mastodon.social/@Snoro/1112517

  20. @kuf so much important climate science needs #semantifying - making it so you can ask questions of the content as to being #readonly - here is a recent example US Plan for Energy Decarbonisation - guess what - just one big PDF Blob - #nomorepdfblobs heh? mastodon.social/@Snoro/1112517

  21. Now I at least receive this warning in the Azure portal, which must mean it's impossible to actually know whether a query is hitting the read-only replica or not.

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming #DBA

  22. Now I at least receive this warning in the Azure portal, which must mean it's impossible to actually know whether a query is hitting the read-only replica or not.

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming #DBA

  23. Now I at least receive this warning in the Azure portal, which must mean it's impossible to actually know whether a query is hitting the read-only replica or not.

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming #DBA

  24. Now I at least receive this warning in the Azure portal, which must mean it's impossible to actually know whether a query is hitting the read-only replica or not.

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming #DBA

  25. Now I at least receive this warning in the Azure portal, which must mean it's impossible to actually know whether a query is hitting the read-only replica or not.

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming #DBA

  26. Do I know anyone with Azure SQL Database experience who can answer me why queries against read-only geo replicas incur massive CPU usage on the main replica and almost none on the read-only replica that is being queried?

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming

  27. Do I know anyone with Azure SQL Database experience who can answer me why queries against read-only geo replicas incur massive CPU usage on the main replica and almost none on the read-only replica that is being queried?

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming

  28. Do I know anyone with Azure SQL Database experience who can answer me why queries against read-only geo replicas incur massive CPU usage on the main replica and almost none on the read-only replica that is being queried?

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming

  29. Do I know anyone with Azure SQL Database experience who can answer me why queries against read-only geo replicas incur massive CPU usage on the main replica and almost none on the read-only replica that is being queried?

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming

  30. Do I know anyone with Azure SQL Database experience who can answer me why queries against read-only geo replicas incur massive CPU usage on the main replica and almost none on the read-only replica that is being queried?

    #Microsoft #Azure #SQL #Database #Geo #Replica #ReadOnly #Development #Programming

  31. As my #weekendCodeProjects often are web-based, I have to debug #JavaScript code that was written by an amateur (me) on a regular basis.

    My N=1 sample indicates that Javascript’s variable-scoping is responsible for ~80% of issues with the code. The rest is weird type-scoping bugs and the author (again, me) trying/failing to be clever.

    #NaN #readOnly #watMan

  32. As my #weekendCodeProjects often are web-based, I have to debug #JavaScript code that was written by an amateur (me) on a regular basis.

    My N=1 sample indicates that Javascript’s variable-scoping is responsible for ~80% of issues with the code. The rest is weird type-scoping bugs and the author (again, me) trying/failing to be clever.

    #NaN #readOnly #watMan

  33. As my #weekendCodeProjects often are web-based, I have to debug #JavaScript code that was written by an amateur (me) on a regular basis.

    My N=1 sample indicates that Javascript’s variable-scoping is responsible for ~80% of issues with the code. The rest is weird type-scoping bugs and the author (again, me) trying/failing to be clever.

    #NaN #readOnly #watMan

  34. As my #weekendCodeProjects often are web-based, I have to debug #JavaScript code that was written by an amateur (me) on a regular basis.

    My N=1 sample indicates that Javascript’s variable-scoping is responsible for ~80% of issues with the code. The rest is weird type-scoping bugs and the author (again, me) trying/failing to be clever.

    #NaN #readOnly #watMan

  35. As my #weekendCodeProjects often are web-based, I have to debug #JavaScript code that was written by an amateur (me) on a regular basis.

    My N=1 sample indicates that Javascript’s variable-scoping is responsible for ~80% of issues with the code. The rest is weird type-scoping bugs and the author (again, me) trying/failing to be clever.

    #NaN #readOnly #watMan

  36. #TweetBot kann aktuell wieder lesend auf Twitter zugreifen, aber tweets zu schreiben scheitert bei mir an einer Fehlermeldung #ReadOnly ?