home.social

#forky — Public Fediverse posts

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

  1. 🔐 Debian 14 verrouille sa sécurité : vous allez pouvoir compter sur "Forky" !

    goodtech.info/debian-14-forky-

    > Fini les "boîtes noires" logicielles. Debian bloque désormais tout paquet binaire qui ne peut pas être reconstruit à l'identique. L'intégrité avant tout.

    #debian #forky #reproducibility #software #securite

  2. 🔐 Debian 14 verrouille sa sécurité : vous allez pouvoir compter sur "Forky" !

    goodtech.info/debian-14-forky-

    > Fini les "boîtes noires" logicielles. Debian bloque désormais tout paquet binaire qui ne peut pas être reconstruit à l'identique. L'intégrité avant tout.

    #debian #forky #reproducibility #software #securite

  3. Debian now requires reproducible builds for the Debian 14 “Forky” cycle, blocking non-reproducible packages from entering or remaining in testing. 🐧
    The policy lets developers independently verify binaries against published source code, with 98.29% of architecture-independent packages already reproducing successfully. 🔐

    🔗 itsfoss.com/news/debian-makes-

    #TechNews #Debian #Linux #OpenSource #Security #FOSS #Privacy #Cybersecurity #Developers #Programming #Software #Technology #Debian14 #Forky #Policy

  4. Debian now requires reproducible builds for the Debian 14 “Forky” cycle, blocking non-reproducible packages from entering or remaining in testing. 🐧
    The policy lets developers independently verify binaries against published source code, with 98.29% of architecture-independent packages already reproducing successfully. 🔐

    🔗 itsfoss.com/news/debian-makes-

    #TechNews #Debian #Linux #OpenSource #Security #FOSS #Privacy #Cybersecurity #Developers #Programming #Software #Technology #Debian14 #Forky #Policy

  5. Debian now requires reproducible builds for the Debian 14 “Forky” cycle, blocking non-reproducible packages from entering or remaining in testing. 🐧
    The policy lets developers independently verify binaries against published source code, with 98.29% of architecture-independent packages already reproducing successfully. 🔐

    🔗 itsfoss.com/news/debian-makes-

    #TechNews #Debian #Linux #OpenSource #Security #FOSS #Privacy #Cybersecurity #Developers #Programming #Software #Technology #Debian14 #Forky #Policy

  6. Debian now requires reproducible builds for the Debian 14 “Forky” cycle, blocking non-reproducible packages from entering or remaining in testing. 🐧
    The policy lets developers independently verify binaries against published source code, with 98.29% of architecture-independent packages already reproducing successfully. 🔐

    🔗 itsfoss.com/news/debian-makes-

    #TechNews #Debian #Linux #OpenSource #Security #FOSS #Privacy #Cybersecurity #Developers #Programming #Software #Technology #Debian14 #Forky #Policy

  7. Debian now requires reproducible builds for the Debian 14 “Forky” cycle, blocking non-reproducible packages from entering or remaining in testing. 🐧
    The policy lets developers independently verify binaries against published source code, with 98.29% of architecture-independent packages already reproducing successfully. 🔐

    🔗 itsfoss.com/news/debian-makes-

    #TechNews #Debian #Linux #OpenSource #Security #FOSS #Privacy #Cybersecurity #Developers #Programming #Software #Technology #Debian14 #Forky #Policy

  8. It got late and I didn’t follow this up. The installation worked. Everything worked. It ended up on Debian #Forky / Sid, I believe because there’s no official release of #Debian for #PPC, so it tracks the latest unstable. Nothing to compile, it all just worked.

    It's the first device in the house to run kernel 6.19, and it's 26 years old!

  9. It got late and I didn’t follow this up. The installation worked. Everything worked. It ended up on Debian #Forky / Sid, I believe because there’s no official release of #Debian for #PPC, so it tracks the latest unstable. Nothing to compile, it all just worked.

    It's the first device in the house to run kernel 6.19, and it's 26 years old!

  10. It got late and I didn’t follow this up. The installation worked. Everything worked. It ended up on Debian #Forky / Sid, I believe because there’s no official release of #Debian for #PPC, so it tracks the latest unstable. Nothing to compile, it all just worked.

    It's the first device in the house to run kernel 6.19, and it's 26 years old!

  11. It got late and I didn’t follow this up. The installation worked. Everything worked. It ended up on Debian #Forky / Sid, I believe because there’s no official release of #Debian for #PPC, so it tracks the latest unstable. Nothing to compile, it all just worked.

    It's the first device in the house to run kernel 6.19, and it's 26 years old!

  12. It got late and I didn’t follow this up. The installation worked. Everything worked. It ended up on Debian #Forky / Sid, I believe because there’s no official release of #Debian for #PPC, so it tracks the latest unstable. Nothing to compile, it all just worked.

    It's the first device in the house to run kernel 6.19, and it's 26 years old!

  13. Ich war vorhin mal an meinem Debian Testing Rechner, um nach Updates zu schauen.. habe mir mal den Spaß erlaubt, Protracker zu installieren.. das war damals 1990 mein erstes Tracker Programm auf meinem damaligen Amiga 500 Computer gewesen, mit dem ich Songs komponiert hatte..später ab 1991 dann mit Oktalyzer..❤️
    #debian #testing #linux #forky #protracker #amiga

  14. Ich war vorhin mal an meinem Debian Testing Rechner, um nach Updates zu schauen.. habe mir mal den Spaß erlaubt, Protracker zu installieren.. das war damals 1990 mein erstes Tracker Programm auf meinem damaligen Amiga 500 Computer gewesen, mit dem ich Songs komponiert hatte..später ab 1991 dann mit Oktalyzer..❤️
    #debian #testing #linux #forky #protracker #amiga

  15. Ich war vorhin mal an meinem Debian Testing Rechner, um nach Updates zu schauen.. habe mir mal den Spaß erlaubt, Protracker zu installieren.. das war damals 1990 mein erstes Tracker Programm auf meinem damaligen Amiga 500 Computer gewesen, mit dem ich Songs komponiert hatte..später ab 1991 dann mit Oktalyzer..❤️
    #debian #testing #linux #forky #protracker #amiga

  16. Ich war vorhin mal an meinem Debian Testing Rechner, um nach Updates zu schauen.. habe mir mal den Spaß erlaubt, Protracker zu installieren.. das war damals 1990 mein erstes Tracker Programm auf meinem damaligen Amiga 500 Computer gewesen, mit dem ich Songs komponiert hatte..später ab 1991 dann mit Oktalyzer..❤️
    #debian #testing #linux #forky #protracker #amiga

  17. Ich war vorhin mal an meinem Debian Testing Rechner, um nach Updates zu schauen.. habe mir mal den Spaß erlaubt, Protracker zu installieren.. das war damals 1990 mein erstes Tracker Programm auf meinem damaligen Amiga 500 Computer gewesen, mit dem ich Songs komponiert hatte..später ab 1991 dann mit Oktalyzer..❤️
    #debian #testing #linux #forky #protracker #amiga

  18. Hier paar Screenies von meinem aktuellen Debian Testing Desktop.. on the way to Forky..
    #linux #debian #testing #forky #kdeplasma

  19. LoongArch 64-bit (#loong64) is a computer processor architecture developed by Loongson Technology Corporation, a Chinese semiconductor company.

    "loong64 has become an official architecture in Debian and will therefore be part of the upcoming Debian 14 ("forky") release"

    lists.debian.org/debian-devel-

    #Debian #Linux #Forky

  20. LoongArch 64-bit (#loong64) is a computer processor architecture developed by Loongson Technology Corporation, a Chinese semiconductor company.

    "loong64 has become an official architecture in Debian and will therefore be part of the upcoming Debian 14 ("forky") release"

    lists.debian.org/debian-devel-

    #Debian #Linux #Forky

  21. LoongArch 64-bit (#loong64) is a computer processor architecture developed by Loongson Technology Corporation, a Chinese semiconductor company.

    "loong64 has become an official architecture in Debian and will therefore be part of the upcoming Debian 14 ("forky") release"

    lists.debian.org/debian-devel-

    #Debian #Linux #Forky

  22. LoongArch 64-bit (#loong64) is a computer processor architecture developed by Loongson Technology Corporation, a Chinese semiconductor company.

    "loong64 has become an official architecture in Debian and will therefore be part of the upcoming Debian 14 ("forky") release"

    lists.debian.org/debian-devel-

    #Debian #Linux #Forky

  23. LoongArch 64-bit (#loong64) is a computer processor architecture developed by Loongson Technology Corporation, a Chinese semiconductor company.

    "loong64 has become an official architecture in Debian and will therefore be part of the upcoming Debian 14 ("forky") release"

    lists.debian.org/debian-devel-

    #Debian #Linux #Forky

  24. @rl_dane @msdropbear42 @MsDropbear42

    Hey R.L. Dane,

    as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.

    Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.

    Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.

    Okay, back to your situation...

    Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.

    It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.

    Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p

    #tallship #FOSS #Remote_Management

  25. @rl_dane @msdropbear42 @MsDropbear42

    Hey R.L. Dane,

    as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.

    Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.

    Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.

    Okay, back to your situation...

    Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.

    It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.

    Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p

    #tallship #FOSS #Remote_Management

  26. @rl_dane @msdropbear42 @MsDropbear42

    Hey R.L. Dane,

    as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.

    Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.

    Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.

    Okay, back to your situation...

    Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.

    It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.

    Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p

    #tallship #FOSS #Remote_Management

  27. Heads up if you're running #Debian #Forky (a.k.a. Debian Testing) and you have a lot of RAM. The new user-space OOM manager systemd-oomd doesn't treat kernel cache memory as available when calculating memory usage. That means it decides you're running out of RAM when you actually aren't and kills processes when it shouldn't.
    Ref: bugs.debian.org/cgi-bin/bugrep
    You might want to uninstall it until this is fixed, or mask systemd-oomd.{service,socket} and reboot to disable it.
    #DebianForky #Linux #systemd

  28. Heads up if you're running #Debian #Forky (a.k.a. Debian Testing) and you have a lot of RAM. The new user-space OOM manager systemd-oomd doesn't treat kernel cache memory as available when calculating memory usage. That means it decides you're running out of RAM when you actually aren't and kills processes when it shouldn't.
    Ref: bugs.debian.org/cgi-bin/bugrep
    You might want to uninstall it until this is fixed, or mask systemd-oomd.{service,socket} and reboot to disable it.
    #DebianForky #Linux #systemd

  29. Heads up if you're running #Debian #Forky (a.k.a. Debian Testing) and you have a lot of RAM. The new user-space OOM manager systemd-oomd doesn't treat kernel cache memory as available when calculating memory usage. That means it decides you're running out of RAM when you actually aren't and kills processes when it shouldn't.
    Ref: bugs.debian.org/cgi-bin/bugrep
    You might want to uninstall it until this is fixed, or mask systemd-oomd.{service,socket} and reboot to disable it.
    #DebianForky #Linux #systemd

  30. Heads up if you're running #Debian #Forky (a.k.a. Debian Testing) and you have a lot of RAM. The new user-space OOM manager systemd-oomd doesn't treat kernel cache memory as available when calculating memory usage. That means it decides you're running out of RAM when you actually aren't and kills processes when it shouldn't.
    Ref: bugs.debian.org/cgi-bin/bugrep
    You might want to uninstall it until this is fixed, or mask systemd-oomd.{service,socket} and reboot to disable it.
    #DebianForky #Linux #systemd

  31. Heads up if you're running #Debian #Forky (a.k.a. Debian Testing) and you have a lot of RAM. The new user-space OOM manager systemd-oomd doesn't treat kernel cache memory as available when calculating memory usage. That means it decides you're running out of RAM when you actually aren't and kills processes when it shouldn't.
    Ref: bugs.debian.org/cgi-bin/bugrep
    You might want to uninstall it until this is fixed, or mask systemd-oomd.{service,socket} and reboot to disable it.
    #DebianForky #Linux #systemd