On Mon, Jun 11, 2012 at 2:23 AM, 7v5w7go9ub0o <
7v5w7g...@gmail.com> wrote:
> On 06/10/12 17:45, Radoslaw Szkodzinski wrote:
>
>>
>> Part of the reason why I'm working on Sabayon. Far better platform to
>> support. (When I'm not battling other Qubes-related issues etc.) I'm
>> still working on the right "qubeize" script for it, as the install
>> wasn't trivial.
>>
>> Perhaps I'll just post the image once it's done.
>
> err....... image....... is this a Qubes installation .iso built around
> Sabayon!?!?
Not yet and I'd have to handle Anaconda to make one, as well as
prepare a dom0 image. (which should actually be easier than domU)
First, I want to finish the script to construct the builder script -
it's still missing a few parts.
Afterwards, I'll replace the dom0.
> If you are building a Qubes-Sabayon based installation .iso, in parallel
> with the development of the Qubes-Fedora iso., ISTM it would be *very*
> interesting to Joanna and Marek (not to mention others on this list)
> after they get some time to breath.
I'm still handling a few minor remaining issues.
For starters, I'm using Pulseaudio in system mode to avoid any
unnecessary session management, as I was unable to get it to work
without consolekit.
I had to patch the vchan module preload hack to not attempt setuid,
but I was unable to get rid of the preload entirely yet. Perhaps this
will require a patch vs u2mfn module.
Consolekit itself is also (strongly?) deprecated and no longer
available due to Fedora decision for systemd to handle everything,
including making coffee and walking pets.
As there's no systemd in Sabayon, the init scripts had to be
rewritten... and they contain a few minor hacks.
I'm still tangling with the desktop file propagation and have to "fix"
the service list handling by adding pulseaudio and correct
meminfo-writer toggle.
And of course finish the builder script, which proved to be harder
than I wanted it to - I need to run a full install using entropy/equo
alone.
There are also other things I want to fix to smooth out the usage,
involving browser horizontal transfers between VMs.
(e.g. enter an unknown shop in an untrusted VM or DVM, then move the
state to the banking VM to complete the transaction once you're sure
it's legit after a proper confirmation)
Currently Qubes is wide open to operator errors (such as phishing
attacks) and I'm looking into ways to rectify that.
--
Radosław Szkodziński