On 04.06.2014 08:25, Dave Young wrote: > On 05/29/14 at 02:20pm, Dave Young wrote: >> On 05/27/14 at 02:25pm, Baoquan He wrote: >>> On 05/22/14 at 03:33pm, Dave Young wrote: >>>> On 05/05/14 at 03:12pm, Baoquan He wrote: >>> >>>> Hi, Baoquan >>>> >>>> The route-$netif is supposed in 1st kernel filesystem. Can we passing the >>>> detail ip/netmask/gw for specific nic in kernel cmdline instead of copy >>>> the route file in initramfs? In that way we can avoid this dracut fix. >>>> >>>> I'm not sure if it works for the complicate route setup though. >>> >>> I am not sure, it had better handle the route during setup net. I want >>> to hear what Harald will say. He is more familiar with this. >> >> Ok, the route table item must be a line like "192.168.100.1 via 127.0.0.1 dev lo metric 203" >> >> If passing them via cmdline we need quote it with some special character and append >> it to the ip= cmdline param >> >> The other way is copy the route file to /etc/ in initramfs like you are doing. >> But we did need the functions to handle the static route. >> >> So leave to Harald about the interface. > > Harald, what do you prefer to passing static route item to initramfs? > Do you have beeter idea in mind? > > Thanks > Dave > Actually, I would like to parse systemd-networkd like config files. As we will integrate systemd-networkd as a replacement for our shell script mess in the future, I think it might make more sense not to introduce another format, which will be obsoleted. http://www.freedesktop.org/software/systemd/man/systemd.network.html What do you think? -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
