From e465722b908aa870bdc293b9a417d3c15294aa6d Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 25 Dec 2024 20:36:29 +0100 Subject: New upstream version 1.50.1 --- docs/libnm/html/ref-overview.html | 67 --------------------------------------- 1 file changed, 67 deletions(-) delete mode 100644 docs/libnm/html/ref-overview.html (limited to 'docs/libnm/html/ref-overview.html') diff --git a/docs/libnm/html/ref-overview.html b/docs/libnm/html/ref-overview.html deleted file mode 100644 index 4ff7b666..00000000 --- a/docs/libnm/html/ref-overview.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - -Overview: libnm Reference Manual - - - - - - - - - - - - - - - - -
-

-Overview

- -
-

-Introduction to libnm

-

- libnm is a client library for NetworkManager, the standard Linux network - management service. NetworkManager supports a wide variety of network - configuration scenarios, hardware devices and protocol families. Most of - the functionality is exposed on a - D-Bus API, - allowing other tools to use the functionality provided by NetworkManager. -

-

- libnm provides C language bindings for functionality provided by - NetworkManager, optionally useful from other language runtimes as well. -

-

- libnm maps fairly closely to the actual D-Bus API that NetworkManager - provides, wrapping the remote D-Bus objects as native GObjects, - mapping D-Bus signals and properties to GObject signals and properties, - and providing helpful accessor and utility functions. However, unlike - the old libnm-util/libnm-glib API, the mapping to the D-Bus API is not - exact, and various inconveniences and historical anomalies of the D-Bus - API are papered over. -

-

- The following is a rough overview of the libnm object structure and - how to use the various parts of it: -

-
- -
-

-

-
-
- - - \ No newline at end of file -- cgit 1.3.0-6-gf8a5