Language Selection

English French German Italian Portuguese Spanish

Linux Mint Debian Edition 201204 - Gnome and Xfce

Filed under
Linux

A few weeks ago, when Linux Mint Debian Edition Update Pack 4 was released, Clement Lefebvre said that a new set of ISO images including the latest update would be available "in the coming days/weeks". Today he made good on that, with the release of LMDE 201204, with both Gnome and Xfce versions. This removes the final hurdle to my whole-heartedly recommending LMDE to anyone interested in Linux. There are a lot of good Linux distributions available, no doubt, but in my opinion this is one of the best because Clement and the rest of the development team think about their users first, all the time.

The Release Announcement is a bit sparse, because in truth this is not really a major new release for LMDE, that happened when Update Pack 4 was released, so for more details check the Release Announcement for that. These new ISO images are NOT just a respin of Update Pack 4, however, there have been some changes and some important bug fixes. One of the most significant changes is in the Gnome desktops. The original LMDE Gnome included the standard Gnome 3 shell, so if you wanted MATE or Cinnamon, you had to install them via the Synaptic Package Manager. This release includes both of them in the Gnome distribution (and does not include the Gnome 3 shell, unless my eyes and brain are deceiving me).

Rest here




More in Tux Machines

Leftovers: Ubuntu

Kernel Space/Linux

  • Why Is Microsoft Showing So Much Interest In Linux? [Ed: Someone needs to explain to Mathew Lodge what EEE is and how it works. Is the Linux Foundation (including Rorvalds as well) still permitted to criticise Microsoft or is it frowned upon internally?]
  • Linux on the Mac — state of the union
    The MacBook Pro introduction in October caused unusually negative reactions among professional users due to the realization that Apple no longer caters equally to casual and professional customers as it had in the past [YouTube video]. Instead, the company appears to be following an iOS-focused, margin-driven strategy that essentially relegates professionals to a fringe group. This has well-known developers such as Salvatore Sanfilippo (of the Redis project) consider a move back to Linux. Perhaps that's a good moment to look at the current state of Mac hardware support in the kernel. While Macs are x86 systems, they possess various custom chips and undocumented quirks that the community needs to painstakingly reverse-engineer.
  • How well does the Linux kernel support Mac hardware?
    There is an interesting subset of Linux users that prefer to run it on a Mac. Yes, a Mac. That might seem odd given how Apple is known for its closed ecosystems and high cost hardware, but the Linux on Mac folks really do exist out there. But how well does the Linux kernel support Mac hardware? LWN.net has a “state of the union” article for Linux on the Mac that could be quite helpful if you are thinking about installing Linux on your Mac.
  • New Kernel Vulnerability Allows Local Root For Unprivileged Processes
    There is yet another new Linux kernel vulnerability being disclosed today that allows for unprivileged processes to gain kernel code execution abilities. This new vulnerability is CVE-2016-8655 but it doesn't seem to be getting too much attention yet. CVE-2016-8655 comes down to a race condition within the af_packet.c code for gaining local root access. The researcher that found it was able to write an exploit to gain root shell on an Ubuntu 16.04 LTS system and defeats SMEP/SMAP protection too.
  • Avoiding CVE-2016-8655 with systemd
    Just a quick note: on recent versions of systemd it is relatively easy to block the vulnerability described in CVE-2016-8655 for individual services. Since systemd release v211 there's an option RestrictAddressFamilies= for service unit files which takes away the right to create sockets of specific address families for processes of the service. In your unit file, add RestrictAddressFamilies=~AF_PACKET to the [Service] section to make AF_PACKET unavailable to it (i.e. a blacklist), which is sufficient to close the attack path. Safer of course is a whitelist of address families whch you can define by dropping the ~ character from the assignment. Here's a trivial example:
  • The Best Features Of The Linux 4.9 Kernel

today's howtos

Red Hat Financial News