[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Tue, 17 May 2011, Keith Abraham wrote:
On 17/05/11 14:48, Gordon Henderson wrote:On Tue, 17 May 2011, Keith Abraham wrote:On 16/05/11 16:41, Philip Hudson wrote:Just did a debian apt-get dist-upgrade, new kernel, so rebooted, stone me, blank resolv.conf WTF!I don't know if you are using a very recent kernel on a Debian system but if you are then any resolv.conf in /etc/ should no longer exist or at least point to /etc/run/resolv.conf/resolv.conf. I think this is all to do with the new /run directory where many things will live in the future including resolv.conf.-- Phil Hudson http://hudson-it.no-ip.biz @UWascalWabbit PGP/GnuPG ID: 0x887DCA63eh? What has the kernel got to do with it?I'm runnig various debians including squeeze, some with 2.6.36.x and all have /etc/resolv.conf. it's been that way for 20 years, why change it now?Is this a new thing... just debian, or all distros? seems to me they're fixing something that isn't broken...I was only using recent kernels eg 2.6.38 and above to indicate the upgrade state of your system. If you are using the latest kernel then, as I see it, you are more likely keeping your system up to date and be using the latest package versions.
No - I'm using the latest kernel to see if it works. My current favourite kernel is 2.6.35 as it's flagged as having long-term support...
$ uname -a Linux drongo 2.6.35.13 #1 SMP PREEMPT Thu Mar 25 17:21:44 GMT 2010 i686 unknown $ cat /etc/debian_version 3.0
RE: the transition to a /run directory the maintainer's article http://lwn.net/Articles/436012/
OK. Interesting. Probably for the better, given the issues that have risen to cause it. Can't say I'm totally in favour of it, but then I compile my own LAMP stack and don't use udev either. Call me old fashioned, but my systems are fast, lean and efficient compared to a stock install. (I'd use gentoo if I could be bothered)
So while /run is addressing some issues, it doesn't actually address resolv.conf, resolvconf, dhcp, network-manager, etc. though. These seem like a totally separate issue, and one that I don't see is currently broken - at least not for the majority of people.
For the few like myself, Phil, Simon, etc. who know better and know/want to manage out own resolv.conf, then we don't need no steenking resolvconf package, but then we need to know how to turn off the automatics that are changing this file against our wishes.
and other places.During the transition there will be problems Some versions of udev for example will introduce the /run directory too early in the transitional period and can cause the system to be un-bootable.eg. http://aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=1093&highlight=run
Good job I don't use udev then.
It's happening to linux in general. If your distro uses timed upgrades the /run concept will probably be contained in the next upgrade. But if you do upgrades yourself then beware as odd things may happen until the transition is over.
I don't auto-upgrade anything.. if it ain't broke, etc. I build servers for a purpose and they stay that way until I either recycle them fully, (having migrated data/apps to new hardware), or scrap them.
Gordon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq