On Mon, Aug 12, 2013 at 10:24 AM, Paul Robert Marino
<[log in to unmask]> wrote:
> On Wed, Jul 31, 2013 at 10:21 PM, zxq9 <[log in to unmask]> wrote:
>> On 07/31/2013 11:57 PM, Tom H wrote:
>>> On Tue, Jul 30, 2013 at 5:12 PM, zxq9<[log in to unmask]>  wrote:
>>>> On 07/30/2013 10:26 PM, Tom H wrote:
>>>
>>> I was only commenting on the more complex and unreadable spec files.
>>> Otherwise I'm happy about systemd and journald. In short, the kernel
>>> has evolved, the applications have evolved, why not the init system?
>>
>> Its not that the init system can't do with some modernization, its that the
>> new system has a severe case of featuritis that is spawning little eddies of
>> nonlocalized complexity all over the place. Modernizing a system and tossing
>> everything that's come before in the interest of a deliberately incompatible
>> rewrite are different things. Remember HAL?
>
> well thats mostly due to the fact that its new and far more complex.
> there was a mad rush for every one to rewrite there statup scripts and
> quite a few of them weren't done very well and others weren't fully
> thought out.
>
> what I find worse is they did a ground up rewrite and didn't touch the
> network configuration portion wasn't rewritten.
>
> The network scripts are limited and problematic if you want to do any
> thing advanced. for example its a long story why but on one device a
> bridge I have to add a static arp entry. iproute2 has been able to do
> this for as long as i can remember but there was no clean way to get
> it to work was to hack the network scripts in order to add the
> functionality.
>
> Really the scripts network scripts need to have hooks added so user
> defined scripts can be called at various points of the startup and
> shutdown of an interface. but more than that they mostly date back to
> the 2.0 Kernel and Linux's Network capabilities have change
> significantly since then but for the most part these scripts keep
> people stuck in the 90's.

(Couldn't you top-post like everyone else?)

There's been more than one hint on fedora-devel that the reason that
the "/etc/sysconfig/network-scripts/<scripts>" haven't been adapted to
systemd is that no one wants to do the (large amount of) work that
would be required when the eventual goal is to default to NM and only
use NM; and that that goal's ever closer. (As a Fedora user, I
sometimes wish that TUV weren't so involved with GNOME and NM and that
netctl were packaged for Fedora - and in the future for EL-7 - because
it's integrated into systemd; but NM's slowly getting there for
servers.)

EL-6.4's network scripts mostly use iproute (although I don't think
that you can use "PREFIX=24" instead of "NETMASK=255.255.255.0" as you
can on Fedora).

The following command returns nothing on F-19, but on EL-6.4:

[root@sci6:/etc/sysconfig/network-scripts]# grep ifconfig *
ifup-ippp:    /usr/bin/logger -p daemon.info -t ifup-ippp "ifconfig
$DEVICE $IPADDR pointopoint $GATEWAY $netmask up"
ifup-ippp:    ifconfig $DEVICE $IPADDR pointopoint $GATEWAY $netmask
up >/dev/null 2>&1
ifup-isdn:    /usr/bin/logger -p daemon.info -t ifup-ippp "ifconfig
$DEVICE $IPADDR pointopoint $GATEWAY $netmask up"
ifup-isdn:    ifconfig $DEVICE $IPADDR pointopoint $GATEWAY $netmask
up >/dev/null 2>&1
ifup-plip:ifconfig ${DEVICE} ${IPADDR} pointopoint ${REMIP}
ifup-plusb:    ifconfig ${DEVICE} ${IPADDR} pointopoint ${REMIP}
netmask ${NETMASK}
ifup-plusb:    ifconfig ${DEVICE} ${IPADDR} pointopoint ${REMIP}
netmask ${NETMASK}
[root@sci6:/etc/sysconfig/network-scripts]#