Am 10.02.2012 18:49, schrieb Jon Ciesla:
On Fri, Feb 10, 2012 at 11:42 AM, Jef Spaleta
<jspaleta(a)gmail.com> wrote:
> On Fri, Feb 10, 2012 at 8:36 AM, Dan Williams <dcbw(a)redhat.com> wrote:
>> In any case, badmouthing systemd for an upgrade bug where it actually
>> works fine *when you're really running F15* doesn't seem right. I
>> wouldn't have had this problem if it'd installed off the Live CD or done
>> a fresh install.
>
> Shrug, I don't make it a point to do yum based upgrades across release
> boundaries so that would explain why i didn't encounter it.
>
> Did anyone doing and testing the "not supported" upgrade dance to F15
> bother filing it at any point? Obviously people use it regardless of
> what the support policy is. I would imagine one of them would file it
> as a market for other people who aren't going to follow policy.
I've been yum upgrading since FC1. I didn't see that. I was also
running a mysql server.
BOAh mysqld has NOTHING to do with the yum upgrade
mysqld in F15 worked only on baby-systems where nothing
other relies on mysqld but not on machines having tons
of services rely in a init-process who fires them up
after mysqld id reday for connections
how often havce i to repeat this here?