On Mon, Jun 01, 2015 at 07:06:06PM -, Thomas Hood wrote:
> Was there in Trusty or later an option to run Ubuntu with sysvinit instead
> of Upstart,
No. sysvinit is not supported on any version of Ubuntu since karmic.
> or do the rc symlinks have side effects even when Upstart is used?
Also
Continuing with my investigation of how a default symlink field got
created for resolvconf on my machine... (What I am calling a 'default
symlink field' is the set of symlinks /etc/rc[1-5].d/S??resolvconf ->
../init.d/resolvconf as would be created by "update-rc.d resolvconf
defaults" with update-r
You know, I didn't even look closely at those warnings. Duh. Now that I
read them I see that I am being warned that I have runlevel symlinks in
1 2 3 4 5. Those aren't supposed to be there! (I run Ubuntu 15.04
upgraded from 14.04 originally.) What the aytch-e-double-hockey-stick?
Consider the hist
Hey THomas,
Thomas Hood [2015-06-01 8:35 -]:
> Is there something we should do to silence those insserv warnings?
> insserv: warning: current start runlevel(s) (2 3 4 5) of script `resolvconf'
> overrides LSB defaults (S).
> insserv: warning: current stop runlevel(s) (0 1 6) of script `resol
Yep, I see that debian/triggers is present in 1.77ubuntu1, and when I
install the package I see the report of the trigger being processed.
Thx! P.S. Is there something we should do to silence those insserv
warnings?
$ sudo dpkg -i resolvconf_1.77ubuntu1_all.deb
(Reading database ... 282465 files
The indirection via /etc/resolvconf/run dates from the era before /run/.
I introduced resolvconf in 2003 as part of a larger effort to make it
possible to run Debian with a read-only root filesystem[1] but the
project to introduce the /run/ tmpfs into Debian base failed due to lack
of consensus abo
Thanks Thomas for the review! I cleaned up the three issues you
mentioned.
Out of interest, do you plan to keep /etc/resolvconf/run in Debian? To
me this has always appeared to be a transitional thing in Debian, as
going through that indirection is a bit confusing and also cluttering of
/etc.
+
I'd like to comment on the remaining differences between Debian
resolvconf and Ubuntu resolvconf.
Besides the extensive source-textual differences arising from Debian's
use of /etc/resolvconf/run versus Ubuntu's direct use of
/run/resolvconf, I see only three substantial differences.
1. The omiss
@Martin: Ubuntu resolvconf 1.76.1ubuntu2 includes the trigger-sending
and trigger-processing section at the end of the postinst but fails to
include the debian/triggers file from Debian. Without this file the
resolvconf package doesn't register an interest in the trigger
resolvconf-enable-updates.
@Martin: My previous comment raced with your release of 1.76.1ubuntu2.
Looks good.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1453185
Title:
resolvconf: updates are
@Thomas: I found it best to simply drop that part of our delta, which
both fixes this bug again and makes maintenance easier.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bug
In the Debian postinst there is a case clause at the end whose purpose
is to enable updates. In Debian this is done by means of a trigger.
resolvconf 1.77
[...]
case "$1" in
reconfigure)
resolvconf --enable-updates
;;
configure)
This bug was fixed in the package resolvconf - 1.76.1ubuntu2
---
resolvconf (1.76.1ubuntu2) wily; urgency=medium
* debian/postinst: Put back calling resolvconf during configuration, to
immediately apply it after package installation. This drops the Ubuntu
delta introduced in
FTR, this is unrelated to pid1. The issue is that older versions called
dh_installinit which added the invoke-rc.d call to postinst. Current
version calls "dh_installinit --no-start", so the update wouldn't happen
right after package installation under any init system.
** Changed in: resolvconf (U
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1453185
Title:
resolvconf: updates are not enabled right after installation
Status in resolv
15 matches
Mail list logo
