-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 08/06/2013 12:09 AM, Robin H. Johnson wrote:
> I'm replying the start of this thread, rather than picking a
> single person to respond to. I DO want more brainstorming on ideas
> for the naming of the package, and I think people need to cast a
> wider net for naming ideas.
> 
> I'm most certainly not planning to get rid of the package
> whatsoever, many of my systems have complex configurations that are
> made MUCH easier with oldnet than any other network configuration
> system I have found.
> 
> Goals of gentoo-oldnet: - Make oldnet functionality available to
> users of other init systems [1][2] - If a package upstream is
> forcing you towards systemd, you shouldn't have to lose other very
> useful packages. - Seperate out development cycle from core OpenRC 
> - oldnet accounts for more than 30% of OpenRC bugs, and a large 
> fraction of the codebase.
> 
> History of the oldnet name: - It's only called oldnet because when
> Roy introduced 'newnet', what we consider to be 'oldnet' didn't
> actually have a separate name.
> 
> Various proposed names (in no specific order): - openrc-oldnet
> (implies OpenRC, and has 'old'). - openrc-gentoo-net (implies
> OpenRC) - gentoo-networking (does this mean newnet is here too?) -
> gen-net  (ditto) - netrc (conflicts) - opennetrc (implies OpenRC) -
> 'net run control' (hard to search) - 'net run configuration' (hard
> to search) - multi-net (conflicts) - netctl (conflicts) - netcfg
> (conflicts) - netconf (conflicts) - enet (conflicts) -
> posixsh-netconf (conflicts netconf) - nettool (conflicts) -
> netcfgtool (conflicts) - posixnet (conflicts) - shnettool
> 
> Naming goals: - Should describe what it does - Does NOT have a name
> conflict as verified by Google. - Does NOT imply OpenRC. - Implying
> Gentoo is fine, as it's where the package comes from. - Should drop
> 'old'
> 
> I think we should focus on the first goal the most: "oldnet is a
> network configuring tool in pure POSIX shell" So we probably want
> the substring 'net' somewhere in there. Beyond that, all
> suggestions are welcome.
> 
> [1] There was a failed GSOC project that I mentioned several years
> ago, that was to support ALL openrc style init.d scripts on
> Upstart, so oldnet would have worked implicitly. Unfortunately the
> student didn't actually do ANY work.
> 
> [2] The configuration itself ends up broken into two parts: -
> directives that control the startup dependency tree. - directives
> that control the actual configuration. The former will need to be
> interoperable or exported to other init systems in some way
> (hopefully dynamically), the latter can stay the same.
> 


Adding some proposals:
- - altnetrc (as it is an alternative)
- - galtnet (gentoo + alternative + network)
- - altgnet (same, permuted)
- - anetcfg (alternative + network + configuration)
- - netposh (network + posix + shell)
- - psnetconf (posix shell network configuration)
- - maybe this one is inspirational, too:
https://en.wikipedia.org/wiki/Gannet

Kind regards,

Manuel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQJ8BAEBCgBmBQJSACk5XxSAAAAAAC4AKGlzc3Vlci0uLi5Abm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4MDA1RERERkM0ODM2QkE4MEY3NzY0N0M1
OEZCQTM2QzhEOUQ2MzVDAAoJEFj7o2yNnWNcW3MP/iu+n+SPJ50tfrfWyrONXj8v
m5mABJtK8DkX/KVdOpr1YWKv3DJVB4Nx6iGSh4PW/jdkVeRmIOJLwipMX3aqpCGi
T0dxQrmTwYyJ1+F6oF9UJiFAtTQ1jhNDlBcc/AqajPwWuMOKHGiHeyrROqnUakiA
/BeZ02a28TMy+stwMaiKT/4DvoIQX/chi5CLdiPOk1uKxnhC7yfSZvh+WFcYh7SW
iW3LQrPO+fiHLrKxr7GlFQ86RTg2A0ySjrpbBYhsYSePkDuRZkAQ8hB1wzDayvek
p6zLgHh7qaFREndnSnWhK2Pk7IZ/FqF+MFodW0j6Wv3BTxf0CDoDiWvkIrrrAXfe
w2YfzBgQfOtPmARQegWQn2PhsM+F9jPCvA0r2GrSm92i6F9pQ7sHGjniL1Wj4nwA
H7YYkAK6Vh23NM49evTragrIWAPtNFKAtyrMVHhGcMYy9gXWKQW1HgxW6N4Mxmv7
OO3SkzS5FNU7rrwbL9thGoRwLifTj9jzLIi3Kb2xcyC2Cxl99JxYq1tgwXYYDkEM
Kywqug/sAe5RXk2dfqrVspkOZzppsZYo5ffa7ddPZJGqSdKIqgOqn0TuDh/v1sWZ
sUol5N0hr56KjG6a3oiHdjxbqj9CiWNGO5n6/AhUbEIccyg5Ug2TTamfMDYqnXPj
DCIE9KqaYxIQA30CyTen
=4zrW
-----END PGP SIGNATURE-----

Reply via email to