home.social

#linuxulator — Public Fediverse posts

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

fetched live
  1. Denial of permission should not be followed by apparent confirmation that the impossible was achieved.

    blah@maximal:~ % service linux disable
    sed: /etc/rc.conf: Permission denied
    linux disabled in /etc/rc.conf
    blah@maximal:~ % service linux status
    /etc/rc.d/linux: unknown directive 'status'.
    Usage: /etc/rc.d/linux [fast|force|one|quiet](start|stop|restart|rcvar|enable|disable|delete|enabled|describe|extracommands)
    blah@maximal:~ % su -
    Password:
    root@maximal:~ # sysrc linux_enable
    linux_enable: YES
    root@maximal:~ # freebsd-version -kru ; uname -mvKU
    16.0-CURRENT
    16.0-CURRENT
    16.0-CURRENT
    FreeBSD 16.0-CURRENT main-n288034-d6f97c6bbca6 GENERIC-NODEBUG amd64 1600019 1600019
    root@maximal:~ #

    #FreeBSD #Linuxulator #service #bug

  2. Denial of permission should not be followed by apparent confirmation that the impossible was achieved.

    blah@maximal:~ % service linux disable
    sed: /etc/rc.conf: Permission denied
    linux disabled in /etc/rc.conf
    blah@maximal:~ % service linux status
    /etc/rc.d/linux: unknown directive 'status'.
    Usage: /etc/rc.d/linux [fast|force|one|quiet](start|stop|restart|rcvar|enable|disable|delete|enabled|describe|extracommands)
    blah@maximal:~ % su -
    Password:
    root@maximal:~ # sysrc linux_enable
    linux_enable: YES
    root@maximal:~ # freebsd-version -kru ; uname -mvKU
    16.0-CURRENT
    16.0-CURRENT
    16.0-CURRENT
    FreeBSD 16.0-CURRENT main-n288034-d6f97c6bbca6 GENERIC-NODEBUG amd64 1600019 1600019
    root@maximal:~ #

    #FreeBSD #Linuxulator #service #bug

  3. Denial of permission should not be followed by apparent confirmation that the impossible was achieved.

    blah@maximal:~ % service linux disable
    sed: /etc/rc.conf: Permission denied
    linux disabled in /etc/rc.conf
    blah@maximal:~ % service linux status
    /etc/rc.d/linux: unknown directive 'status'.
    Usage: /etc/rc.d/linux [fast|force|one|quiet](start|stop|restart|rcvar|enable|disable|delete|enabled|describe|extracommands)
    blah@maximal:~ % su -
    Password:
    root@maximal:~ # sysrc linux_enable
    linux_enable: YES
    root@maximal:~ # freebsd-version -kru ; uname -mvKU
    16.0-CURRENT
    16.0-CURRENT
    16.0-CURRENT
    FreeBSD 16.0-CURRENT main-n288034-d6f97c6bbca6 GENERIC-NODEBUG amd64 1600019 1600019
    root@maximal:~ #

    #FreeBSD #Linuxulator #service #bug

  4. Denial of permission should not be followed by apparent confirmation that the impossible was achieved.

    blah@maximal:~ % service linux disable
    sed: /etc/rc.conf: Permission denied
    linux disabled in /etc/rc.conf
    blah@maximal:~ % service linux status
    /etc/rc.d/linux: unknown directive 'status'.
    Usage: /etc/rc.d/linux [fast|force|one|quiet](start|stop|restart|rcvar|enable|disable|delete|enabled|describe|extracommands)
    blah@maximal:~ % su -
    Password:
    root@maximal:~ # sysrc linux_enable
    linux_enable: YES
    root@maximal:~ # freebsd-version -kru ; uname -mvKU
    16.0-CURRENT
    16.0-CURRENT
    16.0-CURRENT
    FreeBSD 16.0-CURRENT main-n288034-d6f97c6bbca6 GENERIC-NODEBUG amd64 1600019 1600019
    root@maximal:~ #

    #FreeBSD #Linuxulator #service #bug

  5. Denial of permission should not be followed by apparent confirmation that the impossible was achieved.

    blah@maximal:~ % service linux disable
    sed: /etc/rc.conf: Permission denied
    linux disabled in /etc/rc.conf
    blah@maximal:~ % service linux status
    /etc/rc.d/linux: unknown directive 'status'.
    Usage: /etc/rc.d/linux [fast|force|one|quiet](start|stop|restart|rcvar|enable|disable|delete|enabled|describe|extracommands)
    blah@maximal:~ % su -
    Password:
    root@maximal:~ # sysrc linux_enable
    linux_enable: YES
    root@maximal:~ # freebsd-version -kru ; uname -mvKU
    16.0-CURRENT
    16.0-CURRENT
    16.0-CURRENT
    FreeBSD 16.0-CURRENT main-n288034-d6f97c6bbca6 GENERIC-NODEBUG amd64 1600019 1600019
    root@maximal:~ #

    #FreeBSD #Linuxulator #service #bug

  6. Is it normal for FreeBSD sleep (suspend) or wake (resume) to fail with virtual hardware that should support sleep?

    hdac0: Unexpected unsolicited response from address 0: 00000000

    The second screenshot here shows me preparing to run:

    zzz

    First run: a glimpse of ttyv0, and then Plasma reappeared at ttyv8. I can't recall whether it reappeared in response to keyboard input.

    Second run: a screen full of the hdac0 lines at ttyv0

    16.0-CURRENT, AMD64.

    #FreeBSD #Linuxulator #audio #S3 #sleep #suspend #wake #resume #bug

  7. Is it normal for FreeBSD sleep (suspend) or wake (resume) to fail with virtual hardware that should support sleep?

    hdac0: Unexpected unsolicited response from address 0: 00000000

    The second screenshot here shows me preparing to run:

    zzz

    First run: a glimpse of ttyv0, and then Plasma reappeared at ttyv8. I can't recall whether it reappeared in response to keyboard input.

    Second run: a screen full of the hdac0 lines at ttyv0

    16.0-CURRENT, AMD64.

    #FreeBSD #Linuxulator #audio #S3 #sleep #suspend #wake #resume #bug

  8. Is it normal for FreeBSD sleep (suspend) or wake (resume) to fail with virtual hardware that should support sleep?

    hdac0: Unexpected unsolicited response from address 0: 00000000

    The second screenshot here shows me preparing to run:

    zzz

    First run: a glimpse of ttyv0, and then Plasma reappeared at ttyv8. I can't recall whether it reappeared in response to keyboard input.

    Second run: a screen full of the hdac0 lines at ttyv0

    16.0-CURRENT, AMD64.

    #FreeBSD #Linuxulator #audio #S3 #sleep #suspend #wake #resume #bug

  9. Is it normal for FreeBSD sleep (suspend) or wake (resume) to fail with virtual hardware that should support sleep?

    hdac0: Unexpected unsolicited response from address 0: 00000000

    The second screenshot here shows me preparing to run:

    zzz

    First run: a glimpse of ttyv0, and then Plasma reappeared at ttyv8. I can't recall whether it reappeared in response to keyboard input.

    Second run: a screen full of the hdac0 lines at ttyv0

    16.0-CURRENT, AMD64.

    #FreeBSD #Linuxulator #audio #S3 #sleep #suspend #wake #resume #bug

  10. Is it normal for FreeBSD sleep (suspend) or wake (resume) to fail with virtual hardware that should support sleep?

    hdac0: Unexpected unsolicited response from address 0: 00000000

    The second screenshot here shows me preparing to run:

    zzz

    First run: a glimpse of ttyv0, and then Plasma reappeared at ttyv8. I can't recall whether it reappeared in response to keyboard input.

    Second run: a screen full of the hdac0 lines at ttyv0

    16.0-CURRENT, AMD64.

    #FreeBSD #Linuxulator #audio #S3 #sleep #suspend #wake #resume #bug

  11. 🐧😈 BSDun: Modulul experimental de kernel care îți permite să rulezi aplicații de FreeBSD nativ pe Linux 🚀💻

    Lumea sistemelor de operare open-source este plină de experimente fascinante, dar cel mai recent proiect prezentat de Linuxiac pare desprins din universul magiei negre a programării. Un dezvoltator independent a creat un modul de kernel experimental pentru Linux numit BSDun, care are un scop incredibil: să permită rularea fișierelor binare (aplicațiilor compiled) din FreeBSD direct pe sisteme Linux, fără a folosi mașini virtuale, emulatoare sau containere.

    Acest proiect funcționează într-un mod invers față de celebrul strat de compatibilitate Linuxulator din FreeBSD (care permite rularea aplicațiilor de Linux pe BSD) și deschide o discuție tehnică extrem de interesantă.

    Iată detaliile principale despre cum funcționează acest experiment și care sunt limitările sale actuale:

    ⚙️ Cum funcționează sub capotă?
    În mod normal, deși atât Linux cât și FreeBSD folosesc același format de fișier executabil (ELF), ele au moduri complet diferite de a comunica cu hardware-ul. Diferența critică stă în apelurile de sistem (syscalls): modul în care o aplicație cere kernelului să scrie un fișier, să deschidă o conexiune la internet sau să aloce memorie.

    BSDun rezolvă această problemă printr-o abordare la nivel de nucleu:

    Proiectul vine ca un modul de kernel (.ko) care se încarcă direct în nucleul Linux.

    Modulul include un loader (încărcător) ELF modificat și un tabel de translare. În momentul în care detectează că încerci să pornești o aplicație marcată pentru FreeBSD, el interceptează apelurile de sistem specifice BSD și le traduce „în zbor” în apelurile de sistem echivalente din Linux.

    Datorită acestei abordări, aplicațiile rulează la viteză nativă (bare-metal), având o pierdere de performanță practic insesizabilă în comparație cu emularea tradițională.

    ⚠️ Stadiul experimental și limitările majore
    Deși din punct de vedere conceptual este o realizare tehnologică impresionantă, dezvoltatorul avertizează că BSDun este în prezent un prototip aflat în fază Alpha timpurie și nu ar trebui sub nicio formă folosit în medii de producție.

    Suport limitat pentru Syscalls: FreeBSD are sute de apeluri de sistem unice. Momentan, BSDun implementează doar o mică parte dintre cele de bază (gestionarea proceselor simple, input/output elementar). Aplicațiile complexe sau serverele masive vor da erori imediat.

    Problema librăriilor dinamice: Pentru ca executabilele care nu sunt compilate static să funcționeze, utilizatorul trebuie să aducă manual librăriile de sistem (.so) din FreeBSD și să configureze calea către ele în Linux, proces care momentan se face manual și este destul de anevoios.

    Stabilitate: Fiind un cod care rulează în kernel-space, o singură eroare nerezolvată în modulul BSDun va duce instantaneu la prăbușirea întregului sistem Linux (Kernel Panic).

    🔮 De ce contează acest experiment?
    Pentru utilizatorul obișnuit, utilitatea practică imediată este redusă, având în vedere că marea majoritate a aplicațiilor open-source sunt deja disponibile pe ambele platforme. Totuși, importanța proiectului este uriașă pentru:

    Păstrarea ecosistemului: Permite rularea unor aplicații closed-source sau a unor utilitare vechi comerciale care au fost compilate exclusiv pentru FreeBSD și ale căror coduri sursă s-au pierdut.

    Cercetare și Sysadmini: Oferă inginerilor de sistem o modalitate rapidă de a testa sau depana scripturi și instrumente specifice BSD direct de pe mașina lor principală de dezvoltare cu Linux.

    BSDun demonstrează încă o dată flexibilitatea incredibilă a arhitecturii kernelului Linux, care, cu modulele potrivite, poate fi învățat să „vorbească” limbajul altor sisteme de operare direct la nivelul rădăcinii.

    #BSDun #LinuxKernel #FreeBSD #Syscalls #Linuxulator #OpenSource #KernelDevelopment #TechNews

  12. #linuxulator...another prove of "The fact that you can do it, doesn't mean that you must do it"

  13. #linuxulator...another prove of "The fact that you can do it, doesn't mean that you must do it"

  14. #linuxulator...another prove of "The fact that you can do it, doesn't mean that you must do it"

  15. @david_chisnall thanks … I was keen to try Linuxulator as directed in the FreeBSD Handbook. The end result seemed quite bonkers, it seems that there's a gap in official documentation.

    <reddit.com/r/freebsd/comments/> – there's a request for someone to make a bug report.

    #FreeBSD #Linuxulator #documentation

  16. @david_chisnall thanks … I was keen to try Linuxulator as directed in the FreeBSD Handbook. The end result seemed quite bonkers, it seems that there's a gap in official documentation.

    <reddit.com/r/freebsd/comments/> – there's a request for someone to make a bug report.

    #FreeBSD #Linuxulator #documentation

  17. @david_chisnall thanks … I was keen to try Linuxulator as directed in the FreeBSD Handbook. The end result seemed quite bonkers, it seems that there's a gap in official documentation.

    <reddit.com/r/freebsd/comments/> – there's a request for someone to make a bug report.

    #FreeBSD #Linuxulator #documentation

  18. @david_chisnall thanks … I was keen to try Linuxulator as directed in the FreeBSD Handbook. The end result seemed quite bonkers, it seems that there's a gap in official documentation.

    <reddit.com/r/freebsd/comments/> – there's a request for someone to make a bug report.

    #FreeBSD #Linuxulator #documentation

  19. @david_chisnall thanks … I was keen to try Linuxulator as directed in the FreeBSD Handbook. The end result seemed quite bonkers, it seems that there's a gap in official documentation.

    <reddit.com/r/freebsd/comments/> – there's a request for someone to make a bug report.

    #FreeBSD #Linuxulator #documentation

  20. How to add things such as wget and apt to Ubuntu 26.04 LTS in Linuxulator on FreeBSD?

    reddit.com/r/Ubuntu/comments/1

    What's the easiest way to install apt, in the absence of wget?

    Alternatively: what's the easiest way to install wget, in the absence of apt?

    #FreeBSD #apt #Linux #Linuxulator #Ubuntu

  21. How to add things such as wget and apt to Ubuntu 26.04 LTS in Linuxulator on FreeBSD?

    reddit.com/r/Ubuntu/comments/1

    What's the easiest way to install apt, in the absence of wget?

    Alternatively: what's the easiest way to install wget, in the absence of apt?

    #FreeBSD #apt #Linux #Linuxulator #Ubuntu

  22. How to add things such as wget and apt to Ubuntu 26.04 LTS in Linuxulator on FreeBSD?

    reddit.com/r/Ubuntu/comments/1

    What's the easiest way to install apt, in the absence of wget?

    Alternatively: what's the easiest way to install wget, in the absence of apt?

    #FreeBSD #apt #Linux #Linuxulator #Ubuntu

  23. How to add things such as wget and apt to Ubuntu 26.04 LTS in Linuxulator on FreeBSD?

    reddit.com/r/Ubuntu/comments/1

    What's the easiest way to install apt, in the absence of wget?

    Alternatively: what's the easiest way to install wget, in the absence of apt?

    #FreeBSD #apt #Linux #Linuxulator #Ubuntu

  24. How to add things such as wget and apt to Ubuntu 26.04 LTS in Linuxulator on FreeBSD?

    reddit.com/r/Ubuntu/comments/1

    What's the easiest way to install apt, in the absence of wget?

    Alternatively: what's the easiest way to install wget, in the absence of apt?

    #FreeBSD #apt #Linux #Linuxulator #Ubuntu

  25. Running Podman on FreeBSD? It’s a totally different beast than Linux. :freebsd:

    I just published a follow-up to my previous Podman deep dive, going into the FreeBSD operational model for OCI containers. No systemd, no Quadlets, and no rootless mode, but you get native ZFS storage drivers, rc.d service integration, and the Linuxulator.

    We also cover the big question: why Podman complements Jails instead of replacing them.

    Read it here: blog.hofstede.it/podman-on-fre

    #FreeBSD #Podman #Linuxulator #ZFS #Homelab

  26. Running Podman on FreeBSD? It’s a totally different beast than Linux. :freebsd:

    I just published a follow-up to my previous Podman deep dive, going into the FreeBSD operational model for OCI containers. No systemd, no Quadlets, and no rootless mode, but you get native ZFS storage drivers, rc.d service integration, and the Linuxulator.

    We also cover the big question: why Podman complements Jails instead of replacing them.

    Read it here: blog.hofstede.it/podman-on-fre

    #FreeBSD #Podman #Linuxulator #ZFS #Homelab

  27. Running Podman on FreeBSD? It’s a totally different beast than Linux. :freebsd:

    I just published a follow-up to my previous Podman deep dive, going into the FreeBSD operational model for OCI containers. No systemd, no Quadlets, and no rootless mode, but you get native ZFS storage drivers, rc.d service integration, and the Linuxulator.

    We also cover the big question: why Podman complements Jails instead of replacing them.

    Read it here: blog.hofstede.it/podman-on-fre

    #FreeBSD #Podman #Linuxulator #ZFS #Homelab

  28. Running Podman on FreeBSD? It’s a totally different beast than Linux. :freebsd:

    I just published a follow-up to my previous Podman deep dive, going into the FreeBSD operational model for OCI containers. No systemd, no Quadlets, and no rootless mode, but you get native ZFS storage drivers, rc.d service integration, and the Linuxulator.

    We also cover the big question: why Podman complements Jails instead of replacing them.

    Read it here: blog.hofstede.it/podman-on-fre

    #FreeBSD #Podman #Linuxulator #ZFS #Homelab

  29. Running Podman on FreeBSD? It’s a totally different beast than Linux. :freebsd:

    I just published a follow-up to my previous Podman deep dive, going into the FreeBSD operational model for OCI containers. No systemd, no Quadlets, and no rootless mode, but you get native ZFS storage drivers, rc.d service integration, and the Linuxulator.

    We also cover the big question: why Podman complements Jails instead of replacing them.

    Read it here: blog.hofstede.it/podman-on-fre

    #FreeBSD #Podman #Linuxulator #ZFS #Homelab

  30. Getting `KLD Linux.ko: depends on kernel - not available or version mismatch` on a machine that runs the #Linuxulator on #FreeBSD after upgrading a pkgbasified 14 to 15. Same for related file system modules. Is there anything I can do right now, or should I revert and wait for the modules to be re-compiled for 15? When would those versions hit -RELEASE?

  31. Getting `KLD Linux.ko: depends on kernel - not available or version mismatch` on a machine that runs the #Linuxulator on #FreeBSD after upgrading a pkgbasified 14 to 15. Same for related file system modules. Is there anything I can do right now, or should I revert and wait for the modules to be re-compiled for 15? When would those versions hit -RELEASE?

  32. Getting `KLD Linux.ko: depends on kernel - not available or version mismatch` on a machine that runs the on after upgrading a pkgbasified 14 to 15. Same for related file system modules. Is there anything I can do right now, or should I revert and wait for the modules to be re-compiled for 15? When would those versions hit -RELEASE?

  33. Getting `KLD Linux.ko: depends on kernel - not available or version mismatch` on a machine that runs the #Linuxulator on #FreeBSD after upgrading a pkgbasified 14 to 15. Same for related file system modules. Is there anything I can do right now, or should I revert and wait for the modules to be re-compiled for 15? When would those versions hit -RELEASE?

  34. Getting `KLD Linux.ko: depends on kernel - not available or version mismatch` on a machine that runs the #Linuxulator on #FreeBSD after upgrading a pkgbasified 14 to 15. Same for related file system modules. Is there anything I can do right now, or should I revert and wait for the modules to be re-compiled for 15? When would those versions hit -RELEASE?

  35. 🎩✨ Oh look, someone discovered the #Linuxulator on #FreeBSD and thinks it's magical because VS Code kinda works. 🎉🚀 It’s like finding out that water is wet—astoundingly groundbreaking! 🧙‍♂️🔍
    hayzam.com/blog/02-linuxulator #VSCode #discovery #techmagic #groundbreaking #HackerNews #ngated

  36. 🎩✨ Oh look, someone discovered the #Linuxulator on #FreeBSD and thinks it's magical because VS Code kinda works. 🎉🚀 It’s like finding out that water is wet—astoundingly groundbreaking! 🧙‍♂️🔍
    hayzam.com/blog/02-linuxulator #VSCode #discovery #techmagic #groundbreaking #HackerNews #ngated

  37. 🎩✨ Oh look, someone discovered the #Linuxulator on #FreeBSD and thinks it's magical because VS Code kinda works. 🎉🚀 It’s like finding out that water is wet—astoundingly groundbreaking! 🧙‍♂️🔍
    hayzam.com/blog/02-linuxulator #VSCode #discovery #techmagic #groundbreaking #HackerNews #ngated

  38. 🎩✨ Oh look, someone discovered the #Linuxulator on #FreeBSD and thinks it's magical because VS Code kinda works. 🎉🚀 It’s like finding out that water is wet—astoundingly groundbreaking! 🧙‍♂️🔍
    hayzam.com/blog/02-linuxulator #VSCode #discovery #techmagic #groundbreaking #HackerNews #ngated