Ubuntu 16.10 Reaches End of Life (softpedia.com)

prisoninmate shares a report from Softpedia: Today, July 20, 2017, is the last day when the Ubuntu 16.10 (Yakkety Yak) was supported by Canonical as the operating system now reached end of life, and it will no longer receive security and software updates. Dubbed by Canonical and Ubuntu founder Mark Shuttleworth as the Yakkety Yak, Ubuntu 16.10 was launched on October 13, 2016, and it was a short-lived release that only received nine (9) months of support through kernel updates, bug fixes, and security patches for various components. Starting today, you should no longer use Ubuntu 16.10 (Yakkety Yak) on your personal computer, even if it's up-to-date. Why? Because, in time, it will become vulnerable to all sort of attacks as Canonical won't provide security and kernel updates for this release. Therefore, all users are urged to upgrade to Ubuntu 17.04 (Zesty Zapus) immediately using the instructions here.

Comments

non-remarkable non-LTS

[KiloByte]

Not sure why we would care -- it's just an old already-replaced short lived release. The release Ubuntu users should care about is 14.04 (supported until 2019-04) as it's the last one with a sane init.

Re:non-remarkable non-LTS

[Anonymous Coward]

how the fuck is it not the default behaviour of journalctl to linewrap so you can actually see all the errors?

Why the fuck do you expect anything shat out by Lennart Poettering to be user friendly?

Re: non-remarkable non-LTS

[Anonymous Coward]

Considering that the default behaviour for the past forty years, for all Unix systems, has been to print out lines unaltered, wrapping them when necessary, why the hell do users have to adjust to new behaviour? This is altering the system's behaviour, contrary to end user expectations, for no good reason that I am able to discern.

Two minutes of googling? Multiply that by however many thousands of sysadmins are out there and having to deal with this bullshit. Multiply that by however many times a sysadmin gets tripped up before baking it into a system image as a default, plus the number of times they get caught with a new release.

Arguing "you can change the behaviour back, quit whining" simply doesn't cut it in the context of systems that are managed by the thousands.

Re:non-remarkable non-LTS

[thegarbz]

Journalctrl is not a grep of a dumb text file. It's job is to do whatever it was designed to do by the author.

Fortunately the author made it quite configurable. Just export SYSTEMD_PAGER=less, and journalctl will look 100% identical to your previous ways of working. Or just ignore journalctl and set it to output to syslog and it will actually be 100% identical to your previous way of working (with the addition of boot messages in the syslog).

Complaining about something more configurable that offers a complete compatibility with your own way of working looks childish.

Re:non-remarkable non-LTS

[butzwonker]

Maybe they should use sane defaults?

Re:non-remarkable non-LTS

[Hognoxious]

Implying your retarded* well established defaults are the best way.

It implies nothing of the sort. However breaking expectations is rarely a good idea.

Is brake on the left & gas on the right intrinsically better than the other way round? No idea. But it's what people expect, and if you're going to change it then your awesome solution doesn't just need to be better - it needs to be vastly better.

See also: qwerty.

Nine Whole Months

[Anonymous Coward]

But sixteen years is not enough for Windows XP?

Bring on the excuses...

Re:Rolling Release

[somenickname]

Meanwhile the people who use their computers to get work done use the LTS releases, Debian stable, CentOS, etc.

Re:Rolling Release

[thegarbz]

Because the ever moving target of rolling releases which could change at any moment are so much better than running the command "do-release-upgrade" every 6 or so months?