I'm running Raspbian (Wheezy) on a headless Raspberry Pi 2 at home to manage a number of services for my own amusement (*listed below) and to play around in general (** below).

It's pretty much only got an Ethernet cable, power cable and an external USB enclosure plugged into it. (and of course the SD card)

I'm not using it to learn about computers or programming. I mostly SSH into it over the internet and hope to never have a Monitor/keyboard/mouse plugged in ever again.

Most of the upgrades I've heard about in Jessie are UI upgrades. Is there any point to me upgrading to Jessie?

*currently running on my Pi2:

  • DuckDNS (DDNS) updater so that I don't have to remember my IP, or look it up on my ISP's site each time they change it.
  • Simple page on apache that links to a few IP cameras I have around my house (Port 80).
  • Transmission (BitTorrent client)

** previously run and future plans

3 Answers 3


It's important to clarify something about Raspbian for people who aren't otherwise aware: Raspbian is Debian, a GNU/Linux distribution that's been around for ~20 years and is currently on its 8th major release, nicknamed "Jessie". This is why the first Raspbian release is numbered 7 and not 1. The software packages, excluding the firmware, tweaked kernel and 0.01% which are peculiar to the Pi (e.g., raspicam software) are all compiled directly from Debian sources, hence have exactly the same version numbers and so on. Raspbian also has some trivial configuration differences and uses LXDE as the default desktop environment, but if you wanted to turn a fresh Raspbian install into a more exact duplicate of Debian 8 it could be done easily in half an hour.

I mention this because it's central to the issue of updating software and such. The reason there's a new Raspbian (jessie became the default this summer) is because there's a new Debian. Here's a table listing Debian releases chronologically, which includes a couple of columns who's values for the previous release, "Wheezy", are:

  • Full support until February 2016. Support means packagers are actively dedicated to keeping packages updated. Keep in mind that those packages are mostly not maintained by the people who wrote the software, and when the people who wrote the software release a new version, it is not automagically part of Raspbian. That depends on the Debian packagers.
  • Long term support until May 2018. Here's a Debian wiki page about what "long term support" means, which is ambiguous beyond the point that the "Debian security team" are no longer involved.

That's probably the number one factor in a decision to change over. If everything you have works the way you want, you may not care about ever upgrading anything ever again.1 If you do, there is a further subtle issue that has to do with the native C library, glibc. This is the heart, and most essential aspect of, the OS userland (i.e., everything but the kernel). Updating it is one of the riskiest tasks since everything links to it, and this a significant aspect of a major version upgrade (e.g., 7 to 8); the stable glibc for wheezy is 2.13 and jessie is 2.19.2 Both of these are actually at least a year or so older than the corresponding Debian release because of Debian policy and practice.

The glibc version is important because it sets a potential ceiling on updating other software on wheezy, regardless of the good intentions of the long term support maintainers. You may or may not have run into the issue already.

Most of the upgrades I've heard about in Jessie are UI upgrades. Is there any point to me upgrading to Jessie?

I would very strongly disagree that the most significant aspect of the upgrade is something cosmetic, which is what it sounds like you are referring to. The most significant aspect is that Debian abandoned SysVinit as the init system and replaced it with systemd. To ease this transition, they did implement some backward compatibility with their old system. Init is critical and used by a lot of ubiquitous software (namely, everything that starts automatically at boot, and anything else that may count as a "system service").

The difference between systemd and SysVinit is another question (and more appropriate to U&L). The major significance for Raspberry Pi users is that it will obsolete a lot of already aging online blog tutorials (and Q&As here) about how to install X and create a boot service for Y.

If you are learning about, or at some future point become interested in, the init system, do not be misled by this outdated material. Do not start learning SysVinit and tools such as update-rc.d. Learn systemd. It is a much better piece of software. Years ago, there was a lot of griping among Fedora users (including me) when it first appeared there, which mostly boiled down to old dogs having to learn new tricks. No doubt there is a lot of similar griping now with Debian users. Regardless, this means SysVinit could be completely gone from the linux world in 5 years, so if you spend a lot of time learning about it now, that knowledge will be useless unless you commit to maintaining an increasingly eccentric, cobbled together system.

1. I'll skip over the obvious issue of security patches other than to point out that once a significant security hole becomes public and is fixed, a slew of devious people who otherwise wouldn't know about it now do. This doesn't matter if you have the relevant upgrades, but something that slew of devious people can count on is that a lot of people won't.

2. Actually, prior to jessie Debian used eglibc, a close cousin of glibc using the same version numbers that essentially merged back into glibc for 2.19.

  • Ok, nicely put, thanks for the info! Before I asked this quesiton, the only notes i'd seen were here.
    – Jim
    Nov 23, 2015 at 8:01

In my opinion, there is no need to upgrade to jessie, since your systems works as it is any you won't get any benefits from using jessie instead of wheezy.

Nevertheless you should make sure to stay up to date with the wheezy system in terms of security updates. Security updates are supported for wheezy until May 2018 Feb 2016 by the official security team. For long term support, there is a separate group working on support until May 2018.

EDIT: Thanks @goldilocks for correction.

  • Oh of course, I often run the updates and upgrades. And on that note, would of course want to have the latest and greatest raspbian. But just not feeling it with Jessie. I see people begging for Jessie-lite, but others saying that "raspberry pi is a learning computer" etc etc etc "and that a -lite version could be an afterthought, IF that..."
    – Jim
    Nov 20, 2015 at 11:46
  • Ah, it looks as if there are indeed some (minor) updates in packages that I use from wheezy to jessie: - Apache 2.2.22 2.4.10 - BIND DNS Server 9.8 9.9 - lighttpd 1.4.31 1.4.35 - OpenSSH 6.0p1 6.7p1 - Perl 5.14 5.20 - PHP 5.4 5.6 - Samba 3.6 4.1 look like a few candidates. Also I'd upvote your answer, but not enough rep :-(
    – Jim
    Nov 20, 2015 at 11:51
  • Do you need these new versions? What are you missing in your current versions?
    – user236012
    Nov 20, 2015 at 11:54
  • 1
    Seems to me your link about security updates contradicts your comment that "security updates are supported for wheezy until May 2018". They may or may not be supported in some form (that depends on who volunteers to do what), but they will NOT be supported by the official staff after February 2016, and if this is really an important issue to you don't count on it after that.
    – goldilocks
    Nov 20, 2015 at 13:12
  • 2
    TBH I wouldn't be that worried about them either unless you are running a public facing server (transmission sort of is, I think, and something you should stay abreast of security wise regardless of anything else). However, unambiguously reassuring people about something that isn't exactly true deserves a remark.
    – goldilocks
    Nov 20, 2015 at 16:21

I upgraded to Jessie simply because the python versions in Wheezy are REALLY out of date. After struggling to compile python myself, and even after doing it successfully, it interfered with the system python, whereas I really just wanted to replace it. So for me, that was the reason. I'd say unless you have a solid reason, there is no point. It gave me audio problems, so I am currently trying to work those out.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.