aboutsummaryrefslogtreecommitdiff
path: root/README.newnet
diff options
context:
space:
mode:
authorWilliam Hubbs <w.d.hubbs@gmail.com>2012-07-08 15:02:11 -0500
committerWilliam Hubbs <w.d.hubbs@gmail.com>2012-07-08 19:51:36 -0500
commit3e2018f5e9c5cfd4ba8066747fc02dac1ce22f59 (patch)
tree97e9c85c1f2a6a069976bd0062de540d2593b79c /README.newnet
parentdceeef9fe568bd633ed72ca995a1846a9dc20689 (diff)
Revert "Deprecate the network and staticroute scripts"
This reverts commit 5994e55937cbbb71b1c22ad829b77a1bcd8c3793. There are situations where these scripts can be useful, so I am bringing them back. Also, I want to start discussions about simplifying the OpenRC network stack.
Diffstat (limited to 'README.newnet')
-rw-r--r--README.newnet40
1 files changed, 40 insertions, 0 deletions
diff --git a/README.newnet b/README.newnet
new file mode 100644
index 00000000..2e157e2b
--- /dev/null
+++ b/README.newnet
@@ -0,0 +1,40 @@
+The following applies only to the newnet stack, which is not presently
+maintained in OpenRC. The oldnet stack is maintained instead.
+- Robin H. Johnson <robbat2@gentoo.org>, 2011/02/21
+
+OpenRC Network Ideals
+---------------------
+
+The new style networking for OpenRC is very simplistic - provide a basic means
+of configuring static interface address and routes whilst allowing the
+possibility to run any command at any point.
+
+In a nutshell, init.d/network is a wrapper around ifconfig(8) and
+init.d/staticroute is wrapper around route(8).
+
+In the Perfect World (TM) ifconfig should be able to configure everything
+about the interface easily * . The BSD family almost get this right and Linux
+epically fails.
+
+* Only static configuration, including link setup.
+For dynamic, static, IPv4LL, arping and per ssid IPv4 setup dhcpcd-5.x
+provides your needs.
+
+It fails because there are many tools to do the same job and often have
+vastly different syntax where they could be similar. In other words, there
+is no coherence.
+
+OpenRC-0.4.x and older (inc Gentoo baselayout-1) had a collection of scripts
+for each tool and allowed a script per interface. Over the years, this design
+has proven very hard to maintain as each user has their own idea of how
+things should work. Also, there were (and still are) race conditions.
+
+So where do we go from here?
+Well, it's possible to use the new network scripts using the tools
+currently available. It's just harder as you have to know them and their
+documentation can be lacking at times.
+The correct end goal is a BSD style ifconfig tool.
+I've started work on it, but the project has stalled somewhat.
+It's display only right now and the source is not yet publicly available.
+If you have the skills and share the vision then contact me privately and
+we'll take it from there.