From: vadik likholetov <vadim.likholetov@unikie.com>
To: Alyssa Ross <alyssa.ross@unikie.com>
Cc: devel@spectrum-os.org
Subject: Re: Firefox appVM patches and appVM refactoring
Date: Wed, 07 Dec 2022 09:41:56 +0200 [thread overview]
Message-ID: <W1GIMR.26XVN4YFI0CQ1@unikie.com> (raw)
In-Reply-To: <20221206202545.lb53nydhf7c2rd7i@x220>
[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]
On ti, joulu 6 2022 at 20.25.45 +00:00:00, Alyssa Ross
<alyssa.ross@unikie.com> wrote:
> On Tue, Dec 06, 2022 at 10:12:49PM +0200, Vadim Likholetov wrote:
>> I’ll try to explain — running as user is not just dropping the
>> priviledges, it is about preparing the environment - making home
>> directory, fixing permissions, allocating pty-s in case of
>> interactive sessions, setting environment variables.
>> Many system daemons like dbus, pipewire , etc has their
>> system-level and user-level parts and we should manage this
>> separately — and it is our nearest future if we want some complex
>> user environments to run on Spectrum, and possibly the packages for
>> this daemons will extend this environment transparent to the user.
>>
>> So it’s s another form of encapsulation like we discussed about
>> making a separate layer for wayland.
>
> Ah, thanks for the explanation. I understand now!
>
> You're quite right about running user daemons like PipeWire.
> I think to manage those, we'd want to run a user-level s6(-rc)
> instance,
> so that the services are supervised, and can therefore be restarted if
> they crash, and dependencies can be taken care of, and logs can be
> managed however that should work.
>
> Let's try adding PipeWire, D-Bus etc. daemons straight to the img/app
> image? It's intended to be the default image for running
> applications,
> so anything that an application is likely to expect to be running
> should
> be provided by that image by default. And then later on, when it
> comes
> up, we can figure out how to support adding extra services, or whether
> we should support removing default services from the image, etc. How
> does that sound?
Sounds good if we add both user and system parts of dbus or pipewire
subsystem -- the system part when the system starts and the user
part when the user "logs in".
Adding it only to system part doesn't make sense IMO.
I can try to prototype it on the basis of s6 features if we agree
about architecure :)
--
vadik likholetov
[-- Attachment #2: Type: text/html, Size: 2270 bytes --]
next prev parent reply other threads:[~2022-12-07 7:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 22:42 Vadim Likholetov
2022-12-06 11:42 ` Alyssa Ross
2022-12-06 13:56 ` Vadim Likholetov
2022-12-06 15:18 ` Alyssa Ross
2022-12-06 15:20 ` Alyssa Ross
2022-12-06 15:57 ` Vadim Likholetov
2022-12-06 17:10 ` Alyssa Ross
2022-12-06 20:12 ` Vadim Likholetov
2022-12-06 20:25 ` Alyssa Ross
2022-12-07 7:41 ` vadik likholetov [this message]
2022-12-06 20:19 ` Vadim Likholetov
2022-12-06 20:31 ` Developer-friendliness Alyssa Ross
2022-12-07 7:46 ` Developer-friendliness vadik likholetov
2022-12-06 20:59 ` Developer-friendliness Michael Raskin
2022-12-06 21:14 ` Developer-friendliness Alyssa Ross
2022-12-06 22:05 ` Developer-friendliness Michael Raskin
2022-12-07 8:04 ` Firefox appVM patches and appVM refactoring Ville Ilvonen
2022-12-07 11:09 ` vadik likholetov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=W1GIMR.26XVN4YFI0CQ1@unikie.com \
--to=vadim.likholetov@unikie.com \
--cc=alyssa.ross@unikie.com \
--cc=devel@spectrum-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).