From: Thomas Haller <thaller@redhat.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org, rennes@openmailbox.org,
"Ludovic Courtès" <ludo@gnu.org>,
networkmanager-list@gnome.org
Subject: Re: NetworkManager doesn't "Connect automatically"
Date: Mon, 19 Dec 2016 12:45:11 +0100 [thread overview]
Message-ID: <1482147911.2540.8.camel@redhat.com> (raw)
In-Reply-To: <87r356hojb.fsf@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2487 bytes --]
On Sat, 2016-12-17 at 01:51 -0800, Chris Marusich wrote:
> Thomas Haller <thaller@redhat.com> writes:
>
> > On Wed, 2016-12-14 at 01:38 -0800, Chris Marusich wrote:
> > > Hi Thomas,
> > >
> > > Thank you for the quick response!
> > >
> > > Thomas Haller <thaller@redhat.com> writes:
> > >
> > > > Did you build NetworkManager yourself? Is session-tracking
> > > > properly
> > > > enabled to use systemd-logind or consolekit.
> > >
> > > Yes, I'm building it from source [1]. It looks like we might
> > > need to
> > > adjust the way we build it to enable session-tracking, like
> > > you've
> > > suggested. Am I correct in understanding that I should only need
> > > to
> > > pass the option "--with-systemd-logind=yes" to the configure
> > > script
> > > to
> > > enable session tracking via systemd-logind? Is anything else
> > > required?
> >
> > Hi,
> >
> > No, that should be enough.
> >
> > Possibly it was already enabled before, detected automatically?
> >
> > Thomas
>
> OK. Thank you for confirming my understanding.
>
> In GuixSD, we actually use elogind [1] instead of systemd for session
> tracking. This requires us to patch the NetworkManager source to use
> elogind instead of systemd libraries. For example, we do this sort
> of
> patching successfully when packaging polkit [2].
>
> I tried the same thing with NetworkManager [3], but it didn't quite
> work
> out. There are a lot of references to systemd in NetworkManager, and
> I
> think I'm just not familiar enough with NetworkManager, systemd, or
> elogind to know for sure what needs to be patched to trick
> NetworkManager into using elogind instead of systemd for session
> management. For now, we've committed the package definition as-is,
> but
> until somebody figures out exactly how to patch it to work with
> elogind,
> users must use the previously mentioned work-around (make the
> connection
> available to all users) if they want to enable automatic connection.
Hi,
There are very little dependencies of NetworkManager to systemd. Note
that the src/systemd directory contains a self-contained copy of
systemd sources. That is, you don't need an systemd dependency for
those.
Regarding session management, you'd only have to patch
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/nm-session-monitor.c?id=fa15543179aa8ca8e082267121e7df4a131bf642
That seems doable.
Thomas
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 171 bytes --]
_______________________________________________
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
next prev parent reply other threads:[~2016-12-19 11:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 6:51 NetworkManager doesn't "Connect automatically" Chris Marusich
2016-12-13 14:37 ` Thomas Haller
2016-12-13 15:26 ` rennes
2016-12-13 22:38 ` Ludovic Courtès
2016-12-14 9:13 ` Chris Marusich
2016-12-14 9:20 ` Andy Wingo
2016-12-14 10:06 ` Chris Marusich
2016-12-15 7:16 ` Chris Marusich
2016-12-15 10:24 ` Chris Marusich
2016-12-15 10:41 ` Andy Wingo
2016-12-15 15:53 ` Ludovic Courtès
2016-12-17 9:33 ` Chris Marusich
2016-12-14 9:38 ` Chris Marusich
2016-12-14 21:08 ` Thomas Haller
2016-12-17 9:51 ` Chris Marusich
2016-12-19 11:45 ` Thomas Haller [this message]
2016-12-23 10:09 ` Chris Marusich
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=1482147911.2540.8.camel@redhat.com \
--to=thaller@redhat.com \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=networkmanager-list@gnome.org \
--cc=rennes@openmailbox.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.