MESSAGE
| DATE | 2015-12-16 |
| FROM | Paul Robert Marino
|
| SUBJECT | Re: [Hangout-NYLXS] Best comment in a bug report ever
|
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.
It goes back to something I said a long time ago. When evaluation if a
consultant and or company is a good choice to provide you with support
for any Free Speech or Open Source software the first question you
should always ask is have they at least attempted to contributed to
the code or documentation to the project they are claiming to provide
support for. if the answer is no then chances are they are waisting
your time and you should move on to the next candidate.
On Wed, Dec 16, 2015 at 12:22 PM, Rick Moen wrote:
> Quoting Paul Robert Marino (prmarino1-at-gmail.com):
>
>> This is meme-worthy.
>
> It is. And, because an SVLUG Vice-President picked Ubuntu Server as the
> group's Web site platform a decade ago, and immediately handed it off to
> me to do all the actual work, I've been finding out on the installment
> plan that the Canonical, Ltd. kiddies just don't grasp server
> administration and shouldn't be allowed near it.
>
> 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
> stdout.
>
> It would be super-fun to discover the hard way on SVLUG's Linode
> virthost that the /etc/init.d/networking script's stop and restart
> functions have been deliberately caused to do nothing. 'Damn,
> networking didn't restart. I guess I'll have to drive over to the
> server.... Oh, wait.'
>
> Canonical's answer appears to be 'Oh, just reboot to solve problems.
> That's what we always do.'
>
> Comment #33:
>
> This is ridiculous to see this is still an issue. I ran an update on a
> couple farms (that were staged in a lab). Now my networking scripts that
> I had *FIXED* are now overwritten... I now have 300+ servers that don't
> do anything with an init networking script. If this script is an issue,
> then please leave it out. The community will create their own patches.
> But more importantly, if this script was disabled purposefully (note the
> fix below) why was it overwritten by changes that don't do anything?
>
> Can someone please post a link to where this decision was made? It's one
> thing if you want to disable this for desktops. It's an entire other
> issue for disabling for headless servers.
>
> And why is there an init script that does nothing anyway? This makes no
> sense. An init script that sill exists I assume are "for legacy
> purposes" that is purposely broken? This is years in reverse to proclaim
> the OLD way for bouncing the network is now the "documented way." This
> breaks the motto of Ubuntu : Linux for Humans.
>
> Better change that to 'Linux for humans who play with computers but
> never do anything requiring reliability.'
>
> _______________________________________________
> hangout mailing list
> hangout-at-nylxs.com
> http://www.nylxs.com/
_______________________________________________
hangout mailing list
hangout-at-nylxs.com
http://www.nylxs.com/
|
|
