Not wanting to discover different views on what UFS is, for the data exchange between #DragonFlyBSD and #FreeBSD I just allocated a piece of disc and wrote it directly to it🤣
tar cvf /dev/da5s4 some-dir
tar xvf /dev/ada5p4 -C dest
Not wanting to discover different views on what UFS is, for the data exchange between #DragonFlyBSD and #FreeBSD I just allocated a piece of disc and wrote it directly to it🤣
tar cvf /dev/da5s4 some-dir
tar xvf /dev/ada5p4 -C dest
#BSDCan 2025 conference videos are posted to Youtube.
If you wanted to learn more about #FreeBSD, #OpenBSD, #NETBSD, #HardenedBSD or #DragonflyBSD this is collection of videos is a good place to browse and sample some of the features as they are explained.
https://youtube.com/playlist?list=PLeF8ZihVdpFe4u2cwVY8GgxjoFICIYyfY&feature=shared
@dch
let's see. I have no desire to reboot from #DragonFlyBSD now - I've been struggling with Free all day and now I'm going to watch a film:).
But I can give you hardware information if that's what you mean. If you need the result of #FreeBSD specific commands, then post which ones and I'll do it tomorrow.😉
FWIW, I heard #netbsd and #openbsd both works great on the T480. I would expect #freebsd and #dragonflyBSD would too.
Also let us know the choice and how it went :)
📦 Source code sandboxing
ï½¢ Sandboxing is when a developer limits available system resources to a program from within its own source code. A classic example is calling chroot(2) to change the root file-system to an empty directory so that the program cannot scribble into the root file-system ï½£
M.2 USB SSD wakes up using #ZFS and #FreeBSD. I'll leave that question for later (although I have SATA mechanical drives and it would be annoying to see wake-up failures).
I need the Linux command line to create #apicula bases. Qemu works here, which is welcome. But 10 times slower than under #DragonFlyBSD - accel=nvmm accelerator is used there. I wonder what kind of accelerators there are under #FreeBSD?🤔
No, the BSD variants inside are quite different, it's not one kernel with different userspace and a couple of patches:) And the driver set is also different - #NetBSD doesn't want to use the #OrangePi Zero network card, #FreeBSD has no problems with it.
#DragonFlyBSD doesn't know how to use ZFS, so it's not clear which sw component won't wake up the hard drive.
First lessons from experiments with #ZFS - I connected an external 750G HDD with usb interface to play. Creating pool and so on... everything was great until I got distracted and HDD's motor stopped.
Under #DragonFlyBSD it was enough to give ls a mounted directory and the motor would spin up, but that was not the case with #FreeBSD - the hdd didn't wake up.
tomorrow I'll check with UFS, maybe it's FS.
#DragonFlyBSD Updates Its Graphics Drivers With New GPU Support But Still Years Behind • Phoronix
ï½¢ Yesterday's push to the DragonFlyBSD Git tree syncs the DRM driver code against what's found in Linux 4.20.17. Yes, the 4.20 series that debuted at the end of 2018 compared to Linux 6.16 being the very latest upstream. It's also far behind FreeBSD currently using around Linux 6.7 kernel graphics driver code ï½£
https://www.phoronix.com/news/DragonFlyBSD-DRM-Linux-4.20.17
You're welcome. I cottoned on when there was a very brief flicker of a character at one point, and went looking.
#TianoCore doing that self-recursion for backspace and #NetBSD calling OutputString twice makes enough of a window that the character not being erased yet, can synchronize with the display refresh on rare occasion.
So I expect that some sort of putchar_twiddle() that calls OutputString then SetCursorPosition would likely also cut down twiddling overhead.