coldkernel status update

262 views
Skip to first unread message

Colin Childs

unread,
Apr 8, 2017, 10:17:45 PM4/8/17
to qubes...@googlegroups.com
Hi everyone,

It has been some time since we posted on this list, so here is a brief
update:

1. We have recently pushed 0.9a-4.9.20

2. An issue with switching from 4.8.x to 4.9.x was identified and fixed
upstream (https://github.com/coldhakca/coldkernel/issues/55)

3. The blog post for Fedora support is currently being written

4. Final tests for Whonix support are underway

5. 0.9b will be released soon, with support for Fedora and 0.9c will
follow soon after with full Whonix support (and a blog post, again.)

6. Once 0.9c is out, we will direct our efforts towards providing
binaries for Qubes users (and potentially our other supported platforms)

7. After all above steps are complete, we will evaluate what the next
steps should be. This may include attempting to provide a kernel for Dom0.

If anyone has questions / comments, please feel free to contact me directly.

Thanks!

--
Colin Childs
Coldhak
https://coldhak.ca
Twitter: @coldhakca

Reg Tiangha

unread,
Apr 8, 2017, 10:49:47 PM4/8/17
to qubes...@googlegroups.com
Thanks for all the hard work! WillyPillow just pointed out to me today
on the qubes-devel mail list that installing busybox and updating
initramfs in Whonix is all you need to do to get it to boot with
coldkernel, and I just discovered myself a few minutes ago that for
whonixcheck to work, you need to add 'user' to group 9001 (and for
tor-browser to work properly, you need to disable memory protection
using paxctl just like you do for regular Firefox). I haven't gotten
much further than that in my testing, though. In the meantime while we
all wait for 0.9c, any other tips are appreciated!


Patrick Schleizer

unread,
Apr 9, 2017, 11:35:54 AM4/9/17
to qubes...@googlegroups.com
Reg Tiangha:
> On 04/08/2017 08:17 PM, Colin Childs wrote:
> Thanks for all the hard work! WillyPillow just pointed out to me today
> on the qubes-devel mail list that installing busybox and updating
> initramfs in Whonix is all you need to do to get it to boot with
> coldkernel,

Source:
https://groups.google.com/forum/#!topic/qubes-devel/lbeVnhxNIP8

Patrick Schleizer

unread,
Apr 9, 2017, 11:49:30 AM4/9/17
to qubes...@googlegroups.com, Whonix-devel
Reg Tiangha:
> Thanks for all the hard work! WillyPillow just pointed out to me today
> on the qubes-devel mail list that installing busybox and updating
> initramfs in Whonix is all you need to do to get it to boot with
> coldkernel,

busybox will be installed on Whonix 14 by default.

https://github.com/Whonix/anon-meta-packages/commit/92c70963ed34953a81f8e53273453926b738ea18

On the other hand, what about adding busybox as a dependency to the
coldkernel Debian package?

Cheers,
Patrick

Reg Tiangha

unread,
Apr 9, 2017, 11:42:09 PM4/9/17
to qubes...@googlegroups.com
It should probably also be added as a dependancy to
qubes-kernel-vm-support as well since the script that needs it comes
from that package.

I know that the package is currently in current-testing at the moment,
but is it too late to modify it to add busybox as a dependency? That
way, if/when it gets pushed out to stable, anyone wanting to use it on a
Whonix template won't have to do anything extra to get coldkernel or
other local kernels to work on it.


Reply all
Reply to author
Forward
0 new messages