On Fri, 2011-04-01 at 05:20 +0200, Ralf Corsepius wrote:
> On 03/31/2011 07:28 PM, Dan Williams wrote:
> > On Sun, 2011-03-27 at 17:57 +0200, Ralf Corsepius wrote:
> >> On 03/27/2011 05:27 PM, Chuck Anderson wrote:
> >>> On Sun, Mar 27, 2011 at 03:58:06PM +0200, Ralf Ertzinger wrote:
> Hi.
> >
Ralf Corsepius wrote:
> In other words, my question is:
> How to configure NM in a private, dhcp-less, static network, with only
> static IPs, such that
> "hostname" returns "" and
> "hostname -f" returns "."
I take it you have compelling reasons to avoid "hostname --short"?
Björn Persson
sign
On Fri, Apr 01, 2011 at 05:20:03AM +0200, Ralf Corsepius wrote:
> On 03/31/2011 07:28 PM, Dan Williams wrote:
>
> > domainname is only used for NIS,
> Hmm, this doesn't match with my understanding. Doma
On 03/31/2011 07:28 PM, Dan Williams wrote:
> On Sun, 2011-03-27 at 17:57 +0200, Ralf Corsepius wrote:
>> On 03/27/2011 05:27 PM, Chuck Anderson wrote:
>>> On Sun, Mar 27, 2011 at 03:58:06PM +0200, Ralf Ertzinger wrote:
Hi.
On Sun, 27 Mar 2011 15:48:14 +0200, Kevin Kofler wrote
>
On Sun, 2011-03-27 at 17:57 +0200, Ralf Corsepius wrote:
> On 03/27/2011 05:27 PM, Chuck Anderson wrote:
> > On Sun, Mar 27, 2011 at 03:58:06PM +0200, Ralf Ertzinger wrote:
> >> Hi.
> >>
> >> On Sun, 27 Mar 2011 15:48:14 +0200, Kevin Kofler wrote
> >>> NM supports static IPs these days. So I think
On Tue, 29.03.11 14:23, Ian Pilcher (arequip...@gmail.com) wrote:
> On 03/29/2011 12:14 PM, Lennart Poettering wrote:
> > http://0pointer.de/blog/projects/three-levels-of-off
>
> Any ideas why this is happening?
>
> [pilcher@ian ~]$ systemctl is-enabled bluetooth.service && echo ENABLED
> [pilch
On 03/29/2011 12:14 PM, Lennart Poettering wrote:
> http://0pointer.de/blog/projects/three-levels-of-off
Any ideas why this is happening?
[pilcher@ian ~]$ systemctl is-enabled bluetooth.service && echo ENABLED
[pilcher@ian ~]$ systemctl status bluetooth.service
bluetooth.service - Bluetooth Manag
On Tue, 29.03.11 10:12, Adam Williamson (awill...@redhat.com) wrote:
>
> On Tue, 2011-03-29 at 02:35 -0400, Jon Masters wrote:
>
> > For clarification, I usually do have NM_CONTROLLED set for every
> > interface, except on laptops. In this case, I just wanted to instead
> > turn off NetworkManag
On Tue, 2011-03-29 at 02:35 -0400, Jon Masters wrote:
> For clarification, I usually do have NM_CONTROLLED set for every
> interface, except on laptops. In this case, I just wanted to instead
> turn off NetworkManager and configure the interface manually. I see no
> reason why it shouldn't be poss
On Mon, 2011-03-28 at 14:47 -0400, Jeff Garzik wrote:
> > end, I gave up and used a system without NM or any of the other stuff,
>
> That's the right answer: simply turn off NetworkManager and turn on the
> "network" service, to prevent these new breakages from occurring. I do
> that for all
On 03/29/2011 07:35 AM, Jeff Raber wrote:
> On 03/27/2011 10:57 AM, Ralf Corsepius wrote:
>> And how to tweak /etc/sysconfig/network-scripts/ifcfg-* (and/or
>> /etc/sysconfig/network) for static IPs such that NM sets
>> hostname/domainname correctly?
>>
>> I have never got this working correctly.
>
On 03/27/2011 10:57 AM, Ralf Corsepius wrote:
> And how to tweak /etc/sysconfig/network-scripts/ifcfg-* (and/or
> /etc/sysconfig/network) for static IPs such that NM sets
> hostname/domainname correctly?
>
> I have never got this working correctly.
>
> In all cases, I've tried either "hostname
On Sat, 2011-03-26 at 17:59 -0400, Jon Masters wrote:
> On Sat, 2011-03-26 at 11:03 -0400, Neil Horman wrote:
>
> > IIRC you can set:
> > NM_CONTROLLED="no"
> > in /etc/sysconfig/network-scripts/ifcfg-ethX
> > Supposedly that will take ethX off the reservation and allow you to use the
> > ifup
>
Jon Masters (jonat...@jonmasters.org) said:
> Right. This is exactly what I do on non-laptops. But I find NM useful
> for WiFi sometimes so I keep it installed...but now it seems it's
> becoming very difficult to just temporarily configure an interface that
> won't be touched when I plug/unplug a
On 03/26/2011 05:59 PM, Jon Masters wrote:
> On Sat, 2011-03-26 at 11:03 -0400, Neil Horman wrote:
>
>> IIRC you can set:
>> NM_CONTROLLED="no"
>> in /etc/sysconfig/network-scripts/ifcfg-ethX
>> Supposedly that will take ethX off the reservation and allow you to use the
>> ifup
>> script and ifcon
On Sat, Mar 26, 2011 at 5:59 PM, Jon Masters wrote:
> On Sat, 2011-03-26 at 11:03 -0400, Neil Horman wrote:
>
>> IIRC you can set:
>> NM_CONTROLLED="no"
>> in /etc/sysconfig/network-scripts/ifcfg-ethX
>> Supposedly that will take ethX off the reservation and allow you to use the
>> ifup
>> script
On 03/27/2011 05:27 PM, Chuck Anderson wrote:
> On Sun, Mar 27, 2011 at 03:58:06PM +0200, Ralf Ertzinger wrote:
>> Hi.
>>
>> On Sun, 27 Mar 2011 15:48:14 +0200, Kevin Kofler wrote
>>> NM supports static IPs these days. So I think that rather than
>>> hacking around NM, you should just fix the IP in
On Sun, Mar 27, 2011 at 03:58:06PM +0200, Ralf Ertzinger wrote:
> Hi.
>
> On Sun, 27 Mar 2011 15:48:14 +0200, Kevin Kofler wrote
> > NM supports static IPs these days. So I think that rather than
> > hacking around NM, you should just fix the IP inside NM's
> > configuration and have NM work FOR y
Hi.
On Sun, 27 Mar 2011 15:48:14 +0200, Kevin Kofler wrote
> NM supports static IPs these days. So I think that rather than
> hacking around NM, you should just fix the IP inside NM's
> configuration and have NM work FOR you rather than AGAINST you.
I'm sorry, but by the time I have clicked throu
NM supports static IPs these days. So I think that rather than hacking
around NM, you should just fix the IP inside NM's configuration and have NM
work FOR you rather than AGAINST you.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mail
On Sat, 2011-03-26 at 11:03 -0400, Neil Horman wrote:
> IIRC you can set:
> NM_CONTROLLED="no"
> in /etc/sysconfig/network-scripts/ifcfg-ethX
> Supposedly that will take ethX off the reservation and allow you to use the
> ifup
> script and ifconfig utility as you traditionally would.
I remain un
On Sat, Mar 26, 2011 at 07:24:24AM -0400, Jon Masters wrote:
> On Sat, 2011-03-26 at 12:10 +0100, Michel Alexandre Salim wrote:
> > On 03/26/2011 12:05 PM, Jon Masters wrote:
> > > Then it became necessary to:
> > >
> > > /etc/init.d/NetworkManager stop
> > >
> > > Then it became necessary to:
> >
On Sat, 2011-03-26 at 07:05 -0400, Jon Masters wrote:
> So, back in the good old days, one could just type this:
> Just to try to get the interface left alone.
Isn't "the way" just to put NM_CONTROLLED=no in the relevant interface
config file? Even if you're not statically configuring an actu
On Sat, 2011-03-26 at 12:23 +0100, Reindl Harald wrote:
> Nobody stops you to disable Network-Manager, DHCP, AVAHI and the other
> noob-crap
> and write your /etc/sysconfig/network-scripts/ifcfg-eth0 manually as i do
> everytime directly after the first boot and i guess the next 20 years
> this w
Am 26.03.2011 12:24, schrieb Jon Masters:
> On Sat, 2011-03-26 at 12:10 +0100, Michel Alexandre Salim wrote:
>> On 03/26/2011 12:05 PM, Jon Masters wrote:
>>> Then it became necessary to:
>>>
>>> /etc/init.d/NetworkManager stop
>>>
>>> Then it became necessary to:
>>>
>>> systemctl disable Network
Am 26.03.2011 12:05, schrieb Jon Masters:
> Hello,
>
> So, back in the good old days, one could just type this:
>
> ifconfig eth0 some_temp_ip up
>
> Then it became necessary to:
>
> /etc/init.d/NetworkManager stop
>
> Then it became necessary to:
>
> systemctl disable NetworkManager.service
On Sat, 2011-03-26 at 12:10 +0100, Michel Alexandre Salim wrote:
> On 03/26/2011 12:05 PM, Jon Masters wrote:
> > Then it became necessary to:
> >
> > /etc/init.d/NetworkManager stop
> >
> > Then it became necessary to:
> >
> > systemctl disable NetworkManager.service
>
> The last two are equivale
Jon,
have you seen nmcli? If you can't do what you want to with it, maybe a
feature request is in order.
I get the impression that NM will generally do the right thing for
most people most of the time, and when we are hacking on firmware,
running a tftp server and the like we might want to use nm
On 03/26/2011 12:05 PM, Jon Masters wrote:
> Then it became necessary to:
>
> /etc/init.d/NetworkManager stop
>
> Then it became necessary to:
>
> systemctl disable NetworkManager.service
The last two are equivalent to "service NetworkManager stop", which
still works even with systemd.
--
Mich
29 matches
Mail list logo
