Am 21.02.2013 17:30, schrieb Tim:
> On Wed, 2013-02-20 at 22:38 +0100, Reindl Harald wrote:
>> and nobody needs NM for workstations with static IP's
>
> Yes, and no. Yes, you don't need it. But it can still be useful.
>
> Apart from the most obvious - static addresses being configured by your
On Wed, 2013-02-20 at 22:38 +0100, Reindl Harald wrote:
> and nobody needs NM for workstations with static IP's
Yes, and no. Yes, you don't need it. But it can still be useful.
Apart from the most obvious - static addresses being configured by your
central DHCP server, rather than each machine
On 02/20/2013 05:10 PM, Ed Greshko wrote:
FWIW, a superficial search only
foundhttps://bugzilla.redhat.com/show_bug.cgi?id=785618 reported by you where
you mention the problem you are seeing with resolv.conf but indicate that it
isn't part of the issue you are reporting.
Thanx for finding t
On 02/20/2013 05:07 PM, Martín Marqués wrote:
Don't touch resolv.conf. Set all the network configuration (including
DNS) on you ifcfg-eth0 file.
Actually, on my new mobo, it's eth1 for some reason, but as long as
network handles it correctly (and it does) there's no need to mess with
it. Tha
On 02/21/13 08:39, Joe Zeff wrote:
> On 02/20/2013 04:30 PM, Ed Greshko wrote:
>> If you filed a bugzilla, and it was closed as "WONTFIX" then it should still
>> be broken. If you are talking about a problem with F14 and now we are on
>> F18 then it would be a good idea if you bring this up as a
2013/2/20 Joe Zeff :
> On 02/20/2013 04:05 PM, Ed Greshko wrote:
>>
>> If you have "Manual" or "Automatic (DHCP) addresses only" with DNS servers
>> defined in the NM configuration and your resolv.conf file is getting written
>> with 0.0.0.0 then you've hit a bug. One would hope you've filed a bug
On 02/20/2013 04:30 PM, Ed Greshko wrote:
If you filed a bugzilla, and it was closed as "WONTFIX" then it should still be
broken. If you are talking about a problem with F14 and now we are on F18 then it would
be a good idea if you bring this up as a problem you could verify, or at least try t
On 02/21/13 08:20, Joe Zeff wrote:
> On 02/20/2013 04:05 PM, Ed Greshko wrote:
>> If you have "Manual" or "Automatic (DHCP) addresses only" with DNS servers
>> defined in the NM configuration and your resolv.conf file is getting written
>> with 0.0.0.0 then you've hit a bug. One would hope you'v
On 02/21/13 08:11, Martín Marqués wrote:
> 2013/2/20 Ed Greshko :
>> On 02/21/13 05:50, Joe Zeff wrote:
>>> On 02/20/2013 01:38 PM, Reindl Harald wrote:
and nobody needs NM for workstations with static IP's
>>> Agreed. I had to turn it off on my desktop because it insisted on
>>> overwriting
On 02/20/2013 04:05 PM, Ed Greshko wrote:
If you have "Manual" or "Automatic (DHCP) addresses only" with DNS servers
defined in the NM configuration and your resolv.conf file is getting written with 0.0.0.0 then
you've hit a bug. One would hope you've filed a bugzilla.
I've got the interface
2013/2/20 Ed Greshko :
> On 02/21/13 05:50, Joe Zeff wrote:
>> On 02/20/2013 01:38 PM, Reindl Harald wrote:
>>> and nobody needs NM for workstations with static IP's
>>
>> Agreed. I had to turn it off on my desktop because it insisted on
>> overwriting my DNS numbers with 0.0.0.0 every time I boo
On 02/21/13 05:50, Joe Zeff wrote:
> On 02/20/2013 01:38 PM, Reindl Harald wrote:
>> and nobody needs NM for workstations with static IP's
>
> Agreed. I had to turn it off on my desktop because it insisted on
> overwriting my DNS numbers with 0.0.0.0 every time I booted. I still use it
> on my
On 02/20/2013 01:38 PM, Reindl Harald wrote:
and nobody needs NM for workstations with static IP's
Agreed. I had to turn it off on my desktop because it insisted on
overwriting my DNS numbers with 0.0.0.0 every time I booted. I still
use it on my laptop because the old network service doesn
Am 20.02.2013 22:10, schrieb Juan Orti Alcaine:
> network.service is the old SysV scripts, it is disabled by default.
> NetworkManager.service is the default in Fedora
and nobody needs NM for workstations with static IP's
i maintain 20 production servers, a couple of test-setups
and a ahndful o
Am 20.02.2013 21:52, schrieb Martín Marqués:
>> well it is a sysv-script, but chkconfig/systemctl are working in both
>> directions as wrapper
>
> U
there is only systemd in Fedora which SyV compatibility layer
> # systemctl enable network.service
> network.service is not a native serv
2013/2/20 Martín Marqués
> 2013/2/20 Reindl Harald :
>
> > well it is a sysv-script, but chkconfig/systemctl are working in both
> > directions as wrapper
>
> U
>
> # systemctl enable network.service
> network.service is not a native service, redirecting to /sbin/chkconfig.
> Executing /s
2013/2/20 Reindl Harald :
>
>>
>> # chkconfig --list
>>
>> ebtables0:desactivado 1:desactivado 2:desactivado
>> 3:desactivado 4:desactivado 5:desactivado 6:desactivado
>> netconsole 0:desactivado 1:desactivado 2:desactivado
>> 3:desactivado 4:desactivado 5:desactivado
Am 20.02.2013 21:06, schrieb Martín Marqués:
> What system brings up networking on Fedora 18? SysV or Systemd?
there is no SysV since Fedora 15
> I have a newly installed server and I haven't been able to make the
> eth0 network card come up on boot (manually running systemctl restart
> network
18 matches
Mail list logo
