Still can't find whats wrong with this:
I restart the server, network comes up, but the only interface is lo
(loopback). Eth0 is down, and systemctl status network.service says
the process died. restart with systemctl brings the eth0 up and
network is ok and running.
Any ideas?
2013/2/19 Martín
2013/2/18 Reindl Harald :
>
>
> Am 18.02.2013 23:23, schrieb Martín Marqués:
>> I just finished reinstalling (fresh install from my old F16) my fedora
>> server which ended up with a bad disk.
>>
>> The problem I'm seeing is related to, AFAICS, NetworkManager collision
>> with Network. In this serv
Another thing that's happening is that after booting eth0 doesn't come
up (only lo is up abter reboot) automatically. But it does if I do a
"systemctl restart network.service".
2013/2/18 Martín Marqués :
> Not sure, but because of the timeout, after which everythings starts
> working again.
>
> I
Not sure, but because of the timeout, after which everythings starts
working again.
I also have these messages when ever I use yum:
# yum install httpd.x86_64
Complementos cargados:langpacks, presto, refresh-packagekit
Unable to send message to PackageKit
Any idea. yum works great after that mes
Am 18.02.2013 23:23, schrieb Martín Marqués:
> I just finished reinstalling (fresh install from my old F16) my fedora
> server which ended up with a bad disk.
>
> The problem I'm seeing is related to, AFAICS, NetworkManager collision
> with Network. In this server I don't want NM as I have a sta
I just finished reinstalling (fresh install from my old F16) my fedora
server which ended up with a bad disk.
The problem I'm seeing is related to, AFAICS, NetworkManager collision
with Network. In this server I don't want NM as I have a static IP
which should come up on interface eth0 (found that
