Explore >> Select a destination
|
You are here 
|
www.jamesbadger.ca | ||
| | | | |
smallhacks.wordpress.com
|
|
| | | | | After upgrading to Mac M1 I decided to run FreeBSD virtually. As VirtualBox is not supported on this host (and likely will never be) QEMU was the only possible choice. I found great gist post on how to do this with patched QEMU 6. The good news is that now QEMU 7 is released and... | |
| | | | |
thinkingeek.com
|
|
| | | | | In my day job sometimes I need to edit documents using tools that are only available on Windows. As such, I have a virtual machine with Windows 10 running on VirtualBox. Recently I upgraded to Debian 13 and I took the opportunity to migrate to a libvirt-based solution. I explain here the steps that I followed. | |
| | | | |
darrengoossens.wordpress.com
|
|
| | | | | We've got a Windows 10 notebook and an old game that won't run on this version of Windows. I have install disks for Windows98, but we do not have administrator access so we cannot install VirtualBox. QEMU can do this, kind of. Went to https://qemu.weilnetz.de/w64/. Downloaded installer. Ran it. But it wants admin password... OK,... | |
| | | | |
www.daemonology.net
|
|
| | | [AI summary] The article details the author's experience of setting up a FreeBSD desktop environment, highlighting the challenges faced and the eventual success. The author spent significant time configuring hardware, installing packages, and troubleshooting issues such as touchpad responsiveness, driver compatibility, and power management. While the process was complex and time-consuming, the author concludes that FreeBSD is capable of being a viable desktop operating system, especially with the support of the FreeBSD Foundation and community efforts to document laptop compatibility. The article also reflects on the broader implications of using FreeBSD for desktop use, emphasizing the need for more developers to adopt and test laptops for this purpose. | ||
