/explore
|
You are here 
|
meka.rs | ||
| | | | |
www.henryleach.com
|
|
| | | | | I wanted to create some jails that run under their own IP address on my home network for various services. I prefer to have the central DHCP server hand out of the IP addresses, so that if I want to change anything it can all be managed in one place, but it does mean getting the jails and related networking to use DHCP, which turned out to be a little more involved that I thought. | |
| | | | |
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. | |
| | | | |
etherealwake.com
|
|
| | | | | When using FreeBSD, the most common method for virtualization and process isolation are jails. Introduced with FreeBSD 4.0 in March of 2000, they predate the closest Linux equivalent, cgroups (and, by extension, Docker), by nearly a decade. A core part of any virtualization technology is its interaction with the networking infrastructure. In this regard, I've found much of the available documentation lacking, often deferring to third party tools which are no longer maintained. As such, I've had to scrape... | |
| | | | |
fnordig.de
|
|
| | | Personal website of Jan-Erik Rediger | ||
