unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Blake Miller <blak3mill3r@gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: New tool to reduce emacs start-up time on Linux
Date: Mon, 13 Jul 2020 21:17:33 +0000	[thread overview]
Message-ID: <CAM79Mw9UQX3rppS0rwFStxOGE3auJ89ZcTmdcWh4b_jKFD1sSA@mail.gmail.com> (raw)
In-Reply-To: <24332.51925.447735.990302@retriever.mtv.corp.google.com>

[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]

Sure. I should improve this in the readme.

What runs as root are these three things only:

1. A little service that is part of my project, written in babashka, called
els-cloner
2. The criu binary
3. the criu-ns python script

That's all. CRIU currently cannot be run as non-root. The other two things
wrap CRIU and so also need to run as root... except I think I could make
the els-cloner service run as an els-cloner user and give it permission
only to invoke criu & criu-ns as root, and I should do that.

On Mon, Jul 13, 2020 at 8:58 PM T.V Raman <raman@google.com> wrote:

> I see, I dont understand all the terminology here, which explains my
> confusion. As long as neither the emacs daemon or client run as Root,
> then that would take away my concern. Could you also elaborate on what
> it is that runs as Root?
> Blake Miller writes:
>  > I'd never run emacs as root either. CRIU has to run as root, but the
>  > processes it creates when restoring a snapshot are regular non-root
>  > processes, just like the one that was checkpointed.
>  >
>  > On Mon, Jul 13, 2020 at 4:22 PM T.V Raman <raman@google.com> wrote:
>  >
>  > > Stefan Monnier <monnier@iro.umontreal.ca> writes:
>  > >
>  > > the biggest drawback I  saw at a quick-read was the need to run as
> root,
>  > >  I'd never run emacs as root.>> As the name suggests, it can provide
> you
>  > > with the fastest emacs startup
>  > > >> time in the west, by using CRIU checkpoint/restore to "clone"
> emacsen.
>  > > >
>  > > > Hmmm... an "unexec" that's not Emacs-specific, interesting,
>  > > >
>  > > >
>  > > >         Stefan
>  > > >
>  > > >
>  > >
>  > > --
>  > >
>
> --
> Id: kg:/m/0285kf1
>
> --
> Id: kg:/m/0285kf1
>

[-- Attachment #2: Type: text/html, Size: 2510 bytes --]

  reply	other threads:[~2020-07-13 21:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  1:50 New tool to reduce emacs start-up time on Linux Blake Miller
2020-07-13  4:21 ` Rafi Khan
2020-07-13  5:38 ` Stefan Monnier
2020-07-13  8:28   ` Blake Miller
2020-07-13 16:21   ` T.V Raman
2020-07-13 20:01     ` Blake Miller
2020-07-13 20:57       ` T.V Raman
2020-07-13 21:17         ` Blake Miller [this message]
2020-07-13 22:07           ` T.V Raman
2020-07-14  2:36       ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM79Mw9UQX3rppS0rwFStxOGE3auJ89ZcTmdcWh4b_jKFD1sSA@mail.gmail.com \
    --to=blak3mill3r@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=raman@google.com \
    /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://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).