Yes, unfortunately resolvconf 1.63 depends on a newer version of
initscripts:
$sudo dpkg -i resolvconf_1.63ubuntu11_all.deb
dpkg: regarding resolvconf_1.63ubuntu11_all.deb containing resolvconf,
pre-dependency problem:
resolvconf pre-depends on initscripts (= 2.88dsf-13.10)
initscripts is
Is there any chance of a backport for 10.04?
I am working on a headless machine that should automatically connect to a
server on the first available network interface. Resolvconf seems like the
right tool for the job but as mentioned here it is broken for anything but
12.04.
--
You received
Have you tried upgrading the resolvconf package to the Precise or
Quantal version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be thought-out more
my /etc/resolv.conf file got blown away
[...]
But guess what, no more clean reboots. Each reboot requires an ifdown/ifup
ritual.
As Steve mentioned, the resolvconf package was not an official part of
Ubuntu prior to 12.04. In earlier releases it was available from the
Universe repository
I had an up-to-date Ubuntu 11.10 workstation. I recently received an
update that required a 'restart' (aka reboot - new kernel). I put off
the reboot while working away - for a week or so. So, as has happened
each time I've had to 'restart' (aka reboot for a new kernel), I once
again watched in
On Tue, Feb 21, 2012 at 09:26:17PM -, Steffen H. wrote:
I had an up-to-date Ubuntu 11.10 workstation.
I recently received an update that required a 'restart' (aka reboot - new
kernel). I put off the reboot while working away - for a week or so. So,
as has happened each time I've had to
This bug was fixed in the package resolvconf - 1.63ubuntu1
---
resolvconf (1.63ubuntu1) precise; urgency=low
[ Thomas Hood ]
* Debian fixed bugs (LP: #797339, #871058, #471975, #378844, #894417)
* Differences from Debian:
- /sbin/resolvconf:
+ Exit if /etc/resolv.conf
resolvconf v1.63ppa7 from the jdthood's PPA also fixes the boot up
problem on my oneiric machine (using a local caching DNS server as well
as multiple upstream DNSes for VPN connections) . Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Well, if there was a dns-search option in a stanza that was activated
then the corresponding search option should have appeared in
resolv.conf. If that didn't happen then we need to figure out why it
did not.
Please let me know if, after fixing /etc/network/interfaces, resolv.conf
still isn't
That was the thing - it had dns-search but not dns-nameservers. The
dns-search line showed up fine. I don't think that's resolvconf's
fault.
After fixing /etc/network/interfaces, I rebooted the machine twice - the
first time, I zero'ed the resolv.conf file (not deleting the symlink of
course)
Thanks very much for testing the beta resolvconf package. I am pleased
to hear that it behaves better than the previous Ubuntu resolvconf
package. We'll do our best to release 1.63ubuntu1 very soon.
Around the time you were writing your message I uploaded a new version,
1.63ppa6. Relative to
I will test the new version today and post the results tonight. Look
for another post from me in about 10 hours.
Thanks,
Marty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
One of my systems (an Oneiric server) did not correctly regenerate
resolv.conf on boot - but it had a partial interfaces file (dns-search
was defined but not dns-nameservers. Don't ask me how that happened.)
I'm not exactly sure what to make of that, as I have several other boxes
(Oneiric and
I have installed the new packages on several oneiric and precise boxes
that used to have problems with resolvconf 1.48 from Ubuntu; the
1.63ppa5 packages seem to resolve those issues. The servers are multi-
interface machines, one workstation uses static addressing but never
seemed to be able to
** Changed in: resolvconf (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be thought-out more
A new Ubuntu resolvconf package has been prepared by the Debian
maintainers which we hope will fix this bug.
I ask you to test this new package before we upload it to the Ubuntu
repos.
Please install the resolvconf package from ppa:jdthood/resolvconf
Hello Mathieu,
Sander is now working with the Debian maintainers of resolvconf to fix
the problems in the Ubuntu version of the resolvconf package. Your
participation would also be most welcome!
Sander mentioned some improvements to resolvconf itself that can be
beneficial to Debian as well
Sander,
Could you please copy the exact changes you're referring to back in
this bug (since bug 448095 is marked as a duplicate of this one here)?
It would also make it a little easier to track down and sponsor. Any
type of patch will do, if you have just an upstart script that's fine,
and if you
upstart configuration is already done.
Also packaging and patches are available
See Bug #448095
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be
That would be much appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be thought-out more thoroghly
To manage notifications about this bug go
More generally (and this is addressed to anyone who has submitted
information to this report and to all those marked as duplicates of this
one) I would appreciate it if one or more of you would step forward and
offer to help me maintain the resolvconf package in Ubuntu on an ongoing
basis. I
I'm willing to do that.
I have done the upstart specifics of resolvconf over at bug #448095, and
have made some improvements to resolvconf itself that can be beneficial
to debian as well (basically factoring out hardcoded paths in
/etc/resolvconf/*.d scripts and delegating those to the
Ran into this when updating to 11.10, I suspect that an incomplete
transition from /var/run to /run lead to it.
Anyway, purging the package was the cleanest fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am the author and maintainer of resolvconf in Debian. Unfortunately I
don't know enough about upstart to maintain resolvconf for Ubuntu.
In its current condition in Ubuntu (universe) the resolvconf package
does not work properly.
If no one is willing to maintain resolvconf in Ubuntu then it
It turns out that writing Upstart configuration is pretty simple, so
I'll take a crack at making some Ubuntu patches in the next few weeks.
Someone remind me if I forget.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To disable automatic generation of /etc/resolv.conf, purge the
resolvconf package. Then you should have a static /etc/resolv.conf you
can edit by hand. Unless you use NetworkManager in which case
NetworkManager will overwrite /etc/resolv.conf.
--
You received this bug notification because you
The workaround in dupe bug #448095 might still work..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be thought-out more thoroghly
To manage
#448095 has over 80 comments -- I've read through it carefully several
times and I don't see that there's a clear, works-on-Lucid work around.
But that's ok -- jdthood's suggest above in comment 15 sounds like the
straightforward work around I was seeking. (Since I don't need the
dynamic feature
You could also try the PPA mentioned in comment 39 (has lucid packages),
then read comment 83.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be
...just removing (apt-get purge resolvconf) the package fixes the
problem for me.
I don't need the /etc/resolv.conf file being dynamically modified.
Simply purge the package, remove the # this file is auto generated...
comment in /etc/resolv.conf and my problem is solved.
--
You received this
...I'd be perfectly satisfied with a work-around. As it is, I've waded
through all the comments on this bug and all the dupes and there's just
a mess of try-this-try-that, etc. I suspect, I might be able to remove
the dns- options from my interfaces file, and then somehow disable/break
the auto
Is there really no solution to this, in an LTS distro? Seriously?
Keep in mind that resolvconf is from universe.
But still, if resolvconf is going to be offered for Ubuntu then critical
bugs in the Ubuntu patch need to be fixed.
--
You received this bug notification because you are a member
I have some 10.04 LTS systems which are afflicted by this, and some
which aren't.
Is there really no solution to this, in an LTS distro? Seriously?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: resolvconf (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/366967
Title:
ifupdown-udev integration should be thought-out more thoroghly
To
This looks like an issue with resolvconf not being integrated with the
Ubuntu event-driven boot, not with ifupdown not integrating properly
with udev. Indeed, ifupdown now hooks into upstart instead of into
udev, but I don't imagine this has fixed your problem.
** Package changed: ifupdown
Don't know why the requirements are conflicting.
I am sure no one would object that resolvconf runtime initialization should
happen before first ifup run. Just that simple.
As to iptables rules loading, I usually put iptables-restore command into
'iface lo' config section.
Earlier, Debian had a
For the original problem, why not remove eth0 from auto in
/etc/network/interfaces, and call ifup eth0 from rc.local?
It appears to me that there are conflicting requirements when interfaces should
be configured. I like to have the
iptable rules in place before bringing up the outer interface.
This bug is specific to Ubuntu 9.04.
For Ubuntu 9.10, see LP:448095 (in the file '/etc/init/network-interface.conf'
comment out the line 'exec ifup --allow auto $INTERFACE')
--
ifupdown-udev integration should be thought-out more thoroghly
https://bugs.launchpad.net/bugs/366967
You received
My symptoms are the same on ubuntu 9.10 karmic. I use a static ip
address, but I decided to migrate from specifying my dns servers in
/etc/resolv.conf to adding a dns-nameservers line in
/etc/network/interfaces. After a full boot /etc/resolv.conf is blank
with only the comment lines.
# Dynamic
** Changed in: ifupdown (Ubuntu)
Assignee: Scott James Remnant (scott) = (unassigned)
--
ifupdown-udev integration should be thought-out more thoroghly
https://bugs.launchpad.net/bugs/366967
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've looked at how Debian handles that - and it also launches ifup/down
for new interfaces but with --allow hotplug. Sane approach. Please fix
Ubuntu's behavior?
--
ifupdown-udev integration should be thought-out more thoroghly
https://bugs.launchpad.net/bugs/366967
You received this bug
Fact that ifup runs so early from this udev rule breaks asynchronous
mounting of network shares (nfs/cifs). If you add a CIFS share to
/etc/fstab, set it to auto, it might not get mounted at boot anyway. It
should get mounted as a result of /etc/network/if-up.d/mountnfs script
run, during ifup,
On Wed, 2009-05-06 at 05:48 +, Wladimir Mutel wrote:
Everything I have configured in my /etc/network/interfaces worked for some
reason up to and including Ubuntu 8.10.
I had a look into ifupdown-udev integration in Ubuntu 8.10 and so far did not
notice any serious difference with 9.04,
Writable filesystem in my cases is required only by at/batch, as we have
determined. But who knows what configurations could other people have.
Certainly, if the interface config has 'up' options with any commands,
this should be an indication that it is not to be brought up from udev.
Or may be
Ubuntu has called ifup from a udev rule for pretty much every release,
I'm not sure what changed between Ubuntu 8.10 and 9.04 that has caused
your problem.
From the simplest perspective, yes, you have a very complex setup and
it's likely not possible to run certain things before the filesystem is
Everything I have configured in my /etc/network/interfaces worked for some
reason up to and including Ubuntu 8.10.
I had a look into ifupdown-udev integration in Ubuntu 8.10 and so far did not
notice any serious difference with 9.04, but anyway, with 9.04, actions
configured in 'interfaces'
46 matches
Mail list logo
