Network availability systemd dependency failure at boot

[Sam Varshavchik]

Ed Greshko writes:

> >
> > Hilarity ensues.
>
> Any plans to bugzilla your issue?  It should be fun to follow.

Well, I thought about this. For about 30 seconds.

I'm going to say something controversial now. It'll likely send some flames  
my way; and my ethics will get questioned. Maybe, I suppose, someday I'll  
care about that, but not today.

This is the very last thing that I'd like to do. Rather, I want systemd to  
fail. To go down, hard, rather than get some help in band-aiding its fall- 
out.

I'd like to see Red Hat start getting tickets from angry, paying customers,  
who, after upgrading to RHEL 7, end up half their servers come up deaf and  
mute. And a different subset of servers having a problem with every boot  
cycle.

I'm tired of dealing, first with the PrivateTmp fiasco, and now this, and  
who knows what's next. Hopefully, at least someone might understand why  
someone else will NOT want to help fixing this mess, but, if not, that's ok  
too.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140705/bd7c78a1/attachment.sig>