All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Conway S. Smith" <beolach@comcast.net>
To: "Peter H." <heisspf@skyinet.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Fixing /etc/resolv.conf
Date: Thu, 21 Jul 2005 01:38:50 -0600	[thread overview]
Message-ID: <42DF510A.7040803@comcast.net> (raw)
In-Reply-To: <200507210552.j6L5qNoH000634@meridian.ph>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter H. wrote:
> Hi,
> 
> In slackware the file /etc/resolv.conf is updated on every reboot.
> 
> How can I stop that? I tried chattr +i and chmod -w w/o success.
> 
> The reason is that the nameserver address which is put into the file on every 
> reboot is not the the one I am supposed to use according to the advise from my 
> broadband ISP.
> 
> Thanks & regards


Most likely /etc/resolv.conf is being overwritten by the DHCP client
every time you reboot.  In Slackware, edit /etc/rc.d/rc.inet1 so that
when it runs dhcpcd it uses the option -R, which will prevent dhcpcd
from replacing the existing /etc/resolv.conf.

Good luck,
Conway S. Smith
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFC31EIGL3AU+cCPDERAj7yAJ9kbxVaLo9PSJlMlg7ra5m3CQVZZACg7afv
2cFV+FhRQLMUHX+GTLI0+4c=
=wx/F
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2005-07-21  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21  5:52 Fixing /etc/resolv.conf Peter H.
2005-07-21  7:38 ` Conway S. Smith [this message]
2005-07-22  1:05   ` Peter
2005-07-22 14:25     ` Richard Adams
2005-07-23  6:21       ` Peter
2005-07-24  1:55       ` Peter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42DF510A.7040803@comcast.net \
    --to=beolach@comcast.net \
    --cc=heisspf@skyinet.net \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.