On Fri, Jun 20, 2014 at 5:41 AM, Corus <[email protected]> wrote: > I just joined the list so I'm sorry if this is not the proper way to > propose or ask for a feature to be added to systemd. I spoke in > #systemd on Freenode a few days ago and I was pointed in this > direction for submitting feature requests. > > I read this post: http://0pointer.de/blog/projects/stateless.html > > It sounds like systemd is working toward a boot situation where /etc > is disregarded in the hopes of using default/safe values (maybe > safeboot?). > > Basically I'd like to be able to pass minimal network settings to > networkd from the kernel cmdline on an incidental basis (I don't want > to supersede /etc, I just want to use this for convenience where > possible): > > I'd like to have something like this: > sysd.net=eth0:192.168.1.48/24- >>.256;eth1:172.16.0.3/16->0.1
I agree, we do want this. If you want to work on it, I suggest first adding support for reading the kernel's ip= option. Cheers, Tom > I've already discussed this idea on IRC with others and it was > negatively received -- everyone who spoke with me resisted the kernel > cmdline becoming "the new /etc". I want to reiterate that this is not > what I am after. I want basics passed to networkd, I don't want to > use the kernel cmdline for everything. > > Networking is pretty crucial to getting a remote box up and > reachable/ssh'able. Usually I find myself having to vnc in for a > console -- it can be inconvenient to maintain that gateway (imo). > > There are distros oriented for being minimally configured and almost > reentrant. I'm thinking of TAILS or TinyCore or the slew of > penetrating testing distros available out there. It would be *VERY* > useful to me to boot an ISO remotely with the networking settings > passed from the kernel cmdline, then ssh in and finish the > configuration. > > I'd like to be able to do static IP assignment. I want to have the > ability to use DHCP or enable responding to IPv6 router > advertisements. (It'd also be useful to enable security extensions so > the MAC address isn't leaked in the IPv6 assignment). It may also be > useful to configure wireless interfaces by passing the encryption > method and password -- though having the password visible on the > kernel cmdline would not be idea. -- AGAIN, I am thinking of > incidental/expendable setups -- not long-term management performed > this way. > > I hope I've been clear, I've met a lot of resistance with this idea > but I don't think it's terrible. I would simply like more discussion > on its viability. > _______________________________________________ > systemd-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
