|Re: [Hangout-NYLXS] Best comment in a bug report ever
> Comment #27 on the bug:
> Server admins have been restarting networking with init scripts for
> many years, and for me personally it was rather disturbing to find this
> no longer works -- as well as to read some of the comments here.
> Networking that cannot be reliably restarted in the same manner it's
> brought up at boot time is a major problem.
> Also, the only error reporting is to a _logfile_, with nothing to
:( That blows.
'/etc/init.d/networking restart' still works fine on Debian Sid/Unstable
(i.e. the lastest Debian), even when running systemd. I've had a look at
the changelog.gz and NEWS.Debian.gz files for ifupdown -- all looks fine.
This sickness in ifupdown in Ubuntu seems to be something specific to Ubuntu
as far as I can tell ... i.e. the Ubuntu maintainers went out of their way
to make this change.
I can't think of what the purpose might be for this disabling use of
'/etc/init.d/networking restart' in Ubuntu. I don't see justification for
it in the bug report.
Paul Robert Marino:
> Well what do you expect from a Linux support vendor who according to
> the Linux foundation is always conspicuously missing from the yearly
> report listing of companies paying people to contributing code to the
> Linux kernel.
> Canonical has contributed a whopping 0% consistently every year.
That's somewhat expected; the top contributors (~15%) to the Linux Kernel
every year are "None" (no specified affiliation) -- that's where it's
expected that the contributions from most distributions are in. Specifying
an affiliation for a particular distribution can be difficult because
developers often seem to work on multiple distros and/or would perhaps
rather be known for their contributions individually.
hangout mailing list