Deadlines

Reindl Harald h.reindl at thelounge.net
Fri Feb 21 18:48:01 UTC 2014



Am 21.02.2014 19:36, schrieb Simo Sorce:
> On Fri, 2014-02-21 at 19:16 +0100, Reindl Harald wrote:
>>
>> Am 21.02.2014 19:09, schrieb Adam Williamson:
>>> On Fri, 2014-02-21 at 19:06 +0100, Reindl Harald wrote:
>>>> do we have a systemd-209 somewhere
>>>
>>> http://koji.fedoraproject.org/koji/buildinfo?buildID=499417 - build
>>> failed on ARM. But if you haven't even built it locally and tried it
>>> yet...
>>
>> that's not the point
>>
>> * currently nobody knows details but many have qualified guesses
>> * systemd replaced much complexer things than network.service
>> * on 99 out of 100 servers you don't want more than network.service
>> * on 99 out of 100 servers you don't want the NM dependency-chain
>> * you have all the systemd code already in the system
>> * you can expect systemd controls systemd-networkd.service better than
>>   the old fashinoed LSB network.service i expect it to work relieable
>> * we are talking about *future*
>>
>> so you won't get people like me in a direction to accept NM at all
>> well, we had to suck systemd in F15 and survived
>> so *now* that we survived we want to have it finished
>> have systemd finished means no LSB/SysV-Init service on the system
>> the payback have NM instead network.service is not accepted
> 
> Let me correct you here, *you* do not accept it

not only i, but skip that details because it leads to a flamewar

> but At *this* moment you do not even know if it will really work or not,
> because it can't even be compiled for Fedora
> so let's table for more discussion in a 3 months or so, ok ?

agreed

>> guess what happens the next few years
> 
> I do not have crystal balls

in that context i do - NM will not be accepted for people
satisfied with a simple "ifcfg-eth0" the past, currently
and in the future

>> people running Fedora on static network interfaces and hate
>> NetworkManager as much someone can hate software will use it
>> anyways - the same people would even write there own ifup
>> systemd-units if "network.service" would get dropped without
>> a replacement which is not NM
> 
> This is the same argument people had against systemd.
> People will hate it and won't know how to work w/o sysv.

the difference is that from F15 on it was *impossible* to stay
at SysvInit, otherwise i would have started use it with F16/F17
but given that that time back Fedora had outdated kernels not
supporting the onobrad-NIC of sandy-bridge machines at all and
the display froze all day long you needed to upgrade a fresh
installed F14 to F15 wihtout any choice

> Sorry I do not care for fear mongering, thank you

there is no fear

we need a lightweight replacement for network.service
maybe not now but in the to so far future and before someone claims
"network.service is no nolger maintained hust use NM"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/server/attachments/20140221/5875ed9c/attachment.sig>


More information about the server mailing list