Language Selection

English French German Italian Portuguese Spanish

Linux Mint Debian review

Filed under
Linux

Linux Mint Debian is the latest addition to Mint’s suite of Linux desktops. Mint has long promoted itself as a distribution based on Ubuntu and Debian, a claim that I have long discounted as misleading. This release, while still experimental, is one, as the name implies, that is truly based on Debian.

The package manager is pointed at Debian’s testing, instead of to Ubuntu’s repository, and the installer is different too. Since almost every other aspect of this release is the same as the main edition’s, this short review is focused almost entirely on the features of the new installation program.

Installation: The boot options. This edition is, of course, a live DVD edition.

Rest Here




not a full review, hope there will be more...

The author of LinuxBSDos is at this point primarily critiquing the installation process of the newly offered LinuxMint Debian beta release.
Questions like; why not borrow the whole Debian install process? installation being allowed without swap being setup? Why not have a Linux Security package category? are good questions which already have an answer in the workings of the final release.
I hope readers (Mint'ers esp.) take this into account as there are some pertinent questions, but which may seem harsh for some.

Review: Linux Mint "Debian"

dasublogbyprashanth.blogspot: The first thing I see is a standard Linux Mint boot menu — no surprises here. Though I picked the default option, there was no boot splash to speak of — there was only a running console commentary of the boot process. That said, the boot process was rather fast, and I was soon greeted by a standard Linux Mint desktop; there is visually no difference between Linux Mint "Debian" and Linux Mint 9 "Isadora" GNOME. The MintMenu is the same, as are the panel, desktop layout, icons, and window decorations.

As I played around with the desktop, I wondered if the developers rebranded Mozilla Firefox as Iceweasel as per Debian (and Crunchbang 10) standards. Surprisingly, Mozilla Firefox is present with the original branding; less surprising is the presence of most proprietary codecs. OpenOffice.org is also present, though a couple of the icons in the program (notably the "Open file" icon) look a little more ugly and drab for some reason (as far as I can tell, other than that, it's the same icon set). More importantly, some of the application menus open to the side of the button instead of below (e.g. "File", "Insert", etc.), meaning the menus cover up the other menu buttons; this is not an especially good design.

Rest Here

Linux Mint 9 (Debian)

desktoplinuxreviews.com: Each time Ubuntu is updated, we get also get another version of Linux Mint. I usually end up reviewing most of the Linux Mint derivatives of Ubuntu. This time around though, we’ve gotten a delightful surprise from the Linux Mint developers. A Debian version of Linux Mint! Yes, there is now a rolling release Linux Mint distro!

When I found out about it, I couldn’t resist doing a review. Frankly, I was not aware that the Linux Mint developers had even undertaken this project, but I’m very glad that they did. It’s the icing on an already very sweet Linux Mint cake, to say the least.

rest here

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

diff -u: What's New in Kernel Development

Alexander Holler wanted to make it much harder for anyone to recover deleted data. He didn't necessarily want to outwit the limitless resources of our governmental overlords, but he wanted to make data recovery harder for the average hostile attacker. The problem as he saw it was that filesystems often would not actually bother to delete data, so much as they would just decouple the data from the file and make that part of the disk available for use by other files. But the data would still be there, at least for a while, for anyone to recouple into a file again. Alexander posted some patches to implement a new system call that first would overwrite all the data associated with a given file before making that disk space available for use by other files. Since the filesystem knew which blocks on the disk were associated with which files, he reasoned, zeroing out all relevant data would be a trivial operation. Read more

8 Linux Security Improvements In 8 Years

At a time when faith in open source code has been rocked by an outbreak of attacks based on the Shellshock and Heartbleed vulnerabilities, it's time to revisit what we know about Linux security. Linux is so widely used in enterprise IT, and deep inside Internet apps and operations, that any surprises related to Linux security would have painful ramifications. In 2007, Andrew Morton, a no-nonsense colleague of Linus Torvalds known as the "colonel of the kernel," called for developers to spend time removing defects and vulnerabilities. "I would like to see people spend more time fixing bugs and less time on new features. That's my personal opinion," he said in an interview at the time. Read more

Linux from Square One

Despite the fact I have a different view of which distros are best for kids — Qimo (pronounced “kim-o,” as in the last part of eskimo, not “chemo”) tops the list, as it should, but the French distro Doudou (add your own joke here) is unfortunately left out — the link there is informative. So for those who are just getting their proverbial feet wet in Linux, this is a godsend. Read more

Explaining Security Lingo

This post is aimed to clarify certain terms often used in the security community. Let’s start with the easiest one: vulnerability. A vulnerability is a flaw in a selected system that allows an attacker to compromise the security of that particular system. The consequence of such a compromise can impact the confidentiality, integrity, or availability of the attacked system (these three aspects are also the base metrics of the CVSS v2 scoring system that are used to rate vulnerabilities). ISO/IEC 27000, IETF RFC 2828, NIST, and others have very specific definitions of the term vulnerability, each differing slightly. A vulnerability’s attack vector is the actual method of using the discovered flaw to cause harm to the affected software; it can be thought of as the entry point to the system or application. A vulnerability without an attack vector is normally not assigned a CVE number. Read more