DigitalOcean: You haven't used our services in a while... "no matter what roadblock lies in your way, we’re here to help."
Me: My roadblock is that you stopped offering #FreeBSD images.
DigitalOcean: You haven't used our services in a while... "no matter what roadblock lies in your way, we’re here to help."
Me: My roadblock is that you stopped offering #FreeBSD images.
DigitalOcean: You can bring your own image!
Me: BYO images require ext3/ext4, which are not native FreeBSD filesystems.
@vwbusguy @autolycus @Conan_Kudo #FreeBSD includes a BSD licensed ext2/3/4 implementation and there's no fundamental reason an ext3/4 rootfs is impossible.
@vwbusguy @neel @emaste @autolycus @Conan_Kudo You don't need to hack #FreeBSD, it has implemented Linux calls too, on BSD license. 😀 It is called Linuxator. So, ext drivers should work with FreeBSD, same as it is done with Wi-Fi and DRM drivers. All of them are "rip-offs" from Linux.
License also isn't a problem. Even FreeBSD kernel still has some code with GPL.
@vwbusguy @thindil @neel @autolycus @Conan_Kudo
see sys/gnu: in there is gcov and a bwn (Broadcom WiFi) phy
@emaste @thindil @neel @autolycus @Conan_Kudo FWIW, Those are in process of being rewritten to BSD licensed code: https://wiki.freebsd.org/GPLinBase
You can personally, legally probably make it happen, but there is an ideological difference beyond the legal difference. I look at this GPL inclusion like Fedora packaging proprietary Intel firmware. It's a exception rather than the rule for the sake of practicality, but not at all an ideological opening of floodgates.