[Bulk] Ubuntu-devel-discuss Digest, Vol 88, Issue 10
ma1l1ists at yahoo.co.uk
Mon Mar 10 15:10:16 UTC 2014
previously on this list ubuntu-devel-discuss-request at lists.ubuntu.com
> > So we have a program performing mission critical actions that is not
> > documented, or if it is, then the documentation is in the bottom file
> > drawer of the cabinet on the left in the third subbasement of the
> > Vogon Galactic office on Alpha Centauri.
> this is an internal helper script, nothing an enduser should touch (else
> it would live in /usr/bin or /bin) and thus it is not required to have a
> manual page (i'm sure its API is documented in the source somewhere for
> programmers wanting to use it from within network manager).
I don't have NM installed on any of my Linux or BSD machines so I can't
really investigate from an admins point of view in looking at the file
I'm not sure that's really a justification for code running
as root to be undocumented especially the dbus man pages which aren't
anywhere near as forthcoming as they should be about the location of
these files (first line or it's own section). I am glad however that
they are in one place and easily switched off, once found.
This may stem from RedHats rediculous idea (from their website) that a
programmer is 'guaranteed' that a system dbus will always be available,
and this just encourages dbus to be used where it is not appropriate or
snprintf has a man page and I don't see why 'required' has any bearing
on any decision?
> to manage network manager connections from the commandline you use the
> nmcli tool, which ships with a nicely written manpage ;)
or simply edit /etc/network/interfaces and happen to have network
manager installed (by default) and wonder what potential effects that
service might have.
'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
In Other Words - Don't design like polkit or systemd
More information about the Ubuntu-devel-discuss