On Wednesday 10 of March 2010 04:12:19 Dan Williams wrote: > As you've discovered, there are user-specific settings (which are > only available when that user is logged in) and system-wide settings > (which are available to all users *and* before any user has logged > in). The problem you're hitting is when there aren't any settings > at all, like right after an install. > > So NetworkManager creates an internal "Auto XXXX" connection that at > least allows your system to get online if there are any > DHCP-configured ethernet devices on the system. This is a > "system-wide" connection and should be available at boot and before > login. > Are they created by NM service or nm-connection-editor/nm-applet? Should they be present even if other, explicitly defined connections exist? > The problem with that is that often writing to privileged locations > requires some permissions, so NetworkManager will ensure that the > caller is authenticated via PolicyKit before they can change a > connection to be "system-wide". That's configurable too, so as a > distro maintainer you could turn that authentication off via the > file in the policy/ directory in the source. > Is it also run-time settable?
Attachment:
signature.asc
Description: This is a digitally signed message part.