On Mon 12 Oct 2015 at 18:55:40 -0700, Seeker wrote:
> Have not tried setting an interface for DHCP with static DNS using a
> 'dns-nameservers' line in case you want to
> use Google DNS server, OpenDNS, or some other public DNS server when you are
The example in the resolvconf manual is for a stat
Seeker writes:
> On 10/12/2015 12:31 AM, Glenn English wrote:
>>
>> On my laptop, there's a static nameserver address used by
>> eth0. wlan0 uses that too, when it can. But, IIRC, it's smart enough
>> to go looking around if the local network is gone.
>>
>>
> If you set up your network interface
On 10/12/2015 12:31 AM, Glenn English wrote:
On Oct 11, 2015, at 10:45 PM, David Wright wrote:
I thought the OP was about a laptop.
It was. I put Jessie on my laptop to see what it was like. It's running Wheezy
now. And all my troubles with Jessie are gone.
How do you set a static addres
On Oct 11, 2015, at 10:45 PM, David Wright wrote:
> I thought the OP was about a laptop.
It was. I put Jessie on my laptop to see what it was like. It's running Wheezy
now. And all my troubles with Jessie are gone.
> How do you set a static address
> for nameservers?
On Wheezy, and everythin
Quoting Glenn English (g...@slsware.net):
>
> On Oct 11, 2015, at 1:58 PM, Mart van de Wege wrote:
>
> > No, for servers we don't install NetworkManager and resolvconf, and we
> > do static configuration.
>
> I didn't install NM, the installer did. I didn't know there was such a thing.
>
> I d
On Sun 11 Oct 2015 at 13:22:37 -0600, Glenn English wrote:
> On Oct 11, 2015, at 12:37 PM, Brian wrote:
>
> > "Oops" conveys nothing. Which is probably why you didn't expand on it
> > when replying to David Wright.
>
> That's exactly what I was trying to say. A next to meaningless error
> messa
On Sunday 11 October 2015 21:20:40 Glenn English wrote:
> Yup. I should have removed NM as soon as I saw that label in resolv.conf.
> I tried to. But if I'd been successful, I think I would have broken a lot
> of stuff in Jessie.
Didn't you say that this was a server? Surely it must be possible
Glenn English writes:
> On Oct 11, 2015, at 1:58 PM, Mart van de Wege wrote:
>
>> No, for servers we don't install NetworkManager and resolvconf, and we
>> do static configuration.
>
> I didn't install NM, the installer did. I didn't know there was such a thing.
>
> I did know enough, though, to
On Sun, 11 Oct 2015 14:02:20 -0600
Charlie Kravetz wrote:
> On Sun, 11 Oct 2015 13:22:37 -0600
> Glenn English wrote:
>
> >
> >On Oct 11, 2015, at 12:37 PM, Brian wrote:
> >
> >> Your expectations are too high.
> >
> >Don't agree. This is software is intended to run server(s) on the
> >Intern
On Oct 11, 2015, at 2:02 PM, Charlie Kravetz
wrote:
> I am still learning.
Good for you; most of us are :-)
> I can't help asking why you would not be using
> something like dnsmasq instead of /etc/hosts on a server? Isn't it more
> reliable?
Probably. /etc/hosts is just what the admin claim
On Sun, 11 Oct 2015 13:22:37 -0600
Glenn English wrote:
>
>On Oct 11, 2015, at 12:37 PM, Brian wrote:
>
>> Your expectations are too high.
>
>Don't agree. This is software is intended to run server(s) on the Internet
>(for me) and other important networks (for enterprise admins). For those
>a
On Oct 11, 2015, at 2:12 PM, Mart van de Wege wrote:
> it uses whatever is
> configured in nsswitch.conf; that means /etc/hosts first on a default
> install.
/etc/hosts didn't work. Putting the domain name in resolv.conf did. Maybe it
shouldn't have, but that's what happened.
In the past, I'v
On Oct 11, 2015, at 1:58 PM, Mart van de Wege wrote:
> No, for servers we don't install NetworkManager and resolvconf, and we
> do static configuration.
I didn't install NM, the installer did. I didn't know there was such a thing.
I did know enough, though, to toss resolvconf and hand write re
Glenn English writes:
> 'hostname -f' isn't rocket science -- it's just a small lookup. I
> suspect it goes to ifconfig for the IP then in hosts for the FQDN that
> matches the IP, or, apparently, resolv.conf and hostname.
You shouldn't suspect, it's in the Fine Manual. It calls into the C
libra
Glenn English writes:
>
> This is what we're supposed to use for servers on the Internet?
No, for servers we don't install NetworkManager and resolvconf, and we
do static configuration.
Really, you should know better if you're going do whine.
Mart
--
"We will need a longer wall when the revo
On Oct 11, 2015, at 12:37 PM, Brian wrote:
> Your expectations are too high.
Don't agree. This is software is intended to run server(s) on the Internet (for
me) and other important networks (for enterprise admins). For those
applications, it needs to work for at least the trivial software.
On Sun 11 Oct 2015 at 01:25:15 -0600, Glenn English wrote:
>
> On Oct 10, 2015, at 11:28 PM, David Wright wrote:
>
> > If it's unacceptable, why don't you just stick with sysv.
>
> I just expect Debian stable to work correctly, like, as best I can
> remember, it always has.
Your expectations
On Sunday 11 October 2015 05:37:30 to...@tuxteam.de wrote:
> On Sat, Oct 10, 2015 at 08:51:18PM -0600, Glenn English wrote:
>
> [...]
>
> > The problem with that is that there's a line at the top of the
> > resolv.conf: "Generated by NetworkManager." [...]
>
> A reason why I avoid NetworkManager s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Oct 11, 2015 at 11:37:30AM +0200, to...@tuxteam.de wrote:
[...]
> (sudo chattr -i ) and wait until the perpetrator
Sorry. That would be "chattr +i"
regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Oct 10, 2015 at 08:51:18PM -0600, Glenn English wrote:
[...]
> The problem with that is that there's a line at the top of the
> resolv.conf: "Generated by NetworkManager." [...]
A reason why I avoid NetworkManager since long (this has lead m
On Oct 10, 2015, at 11:28 PM, David Wright wrote:
> If it's unacceptable, why don't you just stick with sysv.
I just expect Debian stable to work correctly, like, as best I can remember, it
always has.
I wouldn't mind a new init system -- I've been through several in the past, and
System V
Quoting Glenn English (g...@slsware.net):
> I put Jessie on a laptop. 'hostname -f' said it couldn't do it (don't
> remember the error message, but it was, essentially, "Oops").
Couldn't do what?
> The instructions on the 'Net for fixing the missing domain name in Jessie
> were the same as they
I put Jessie on a laptop. 'hostname -f' said it couldn't do it (don't remember
the error message, but it was, essentially, "Oops").
The instructions on the 'Net for fixing the missing domain name in Jessie were
the same as they've always been: put the fully qualified domain name (fqdn)
with the
23 matches
Mail list logo
