Re: kFreeBSD future
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 1/10/2014 6:35 AM, Steven Chamberlain wrote:
> On 30/09/14 20:03, brunomaximom@openmailbox.org wrote:
> The remaining concern would be having enough people involved. I'm
> certainly not the only active developer; Christoph has been testing and
> doing all the uploads since DebConf, this month Petr fixed a glibc issue
> for us, Axel updated the manpages package, Sylvestre Ledru helped port
> clang-3.4 to build our kernels, Jeff Epler's patch for partman finally
> made it into d-i, several people have sent installation reports, and
> today I saw someone new contribute a patch for a package that was FTBFS
> on kfreebsd. I haven't heard from Robert in some time, so I had to
> learn how to do the 10.1 userland packaging myself, but that's done now,
> and if he comes back he can of course help us a lot with whatever needs
> to be done during freeze.
So, is there currently ANY concern that kFreeBSD won't continue for
Jessie and/or beyond Jessie? Are there enough people involved now to
remove the risk for new users coming on board to use kFreeBSD, such as
those needing an exit strategy from systemd on the main Debian release?
Also, if people move systems to kFreeBSD and kFreeBSD stops being
properly maintained and supported, is there a good migration path to
FreeBSD or would it be a case of learning the whole FreeBSD system
/ways/ over the Debian /ways/ ? How about ZFS, would the data on ZFS
volumes be easily migrated, without rebuilding ZFS setups from scratch
if the need arose?
What is the status of virtualization? I would like to replace xen which
I am currently using with squeeze-lts -- is xen going to work with
kFreeBSD? Is bhyve going to be a realistic option to use on kFreeBSD?
I am also interested in using FDE (full disk encryption), including /
file system and use of dropbear ssh for mount time entry of LUKS pass
phrases as I do with some current wheezy servers. Is there well
documented ways to get systems up with these requirements?
Thank you
A.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
iF4EAREIAAYFAlQ8FEQACgkQqBZry7fv4vviVQD/fCE1LaEKqCbH3HocudKf2agV
xNfE6K0wL9pcadPgaIkA/0+DePAc7oIf9PDxQTsmekL95weatUAiWufZq+9nSqW0
=Prlq
-----END PGP SIGNATURE-----
Reply to: