<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/">
  <channel>
    <title>Desktop</title>
    <link>https://www.linuxjournal.com/</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Without a GUI--How to Live Entirely in a Terminal</title>
  <link>https://www.linuxjournal.com/content/without-gui-how-live-entirely-terminal</link>
  <description>  &lt;div data-history-node-id="1340674" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/bryan-lunduke" lang="" about="https://www.linuxjournal.com/users/bryan-lunduke" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Bryan Lunduke&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;Sure, it may be hard, but it &lt;em&gt;is&lt;/em&gt; possible to give up graphical interfaces
entirely—even in 2019.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
About three years back, I attempted to live entirely on the command line for 30
days—no graphical interface, no X Server, just a big-old terminal and me,
for a month.
&lt;/p&gt;

&lt;p&gt;
I lasted all of ten days.
&lt;/p&gt;

&lt;p&gt;
Why did I attempt this? What on Earth would compel a man to give up all the
trappings and features of modern graphical desktops and, instead,
artificially restrict himself to using nothing but text-based, command-line
software, as if he were stuck in the early 1980s?
&lt;/p&gt;

&lt;p&gt;
Who knows. Clearly, I make questionable decisions.
&lt;/p&gt;

&lt;p&gt;
But you know, if I'm being honest, the experience was not entirely
unpleasant. Sure, I missed certain niceties from the graphical side of things,
but there were some distinct benefits to living in a shell. My computers, even
the low-powered ones, felt faster (command-line software tends to be a whole
lot lighter and leaner than those with a graphical user interface). Plus, I
was able to focus and get more work done without all the distractions of a
graphical desktop, which wasn't bad.
&lt;/p&gt;

&lt;p&gt;
What follows are the applications I found myself relying upon the most during
those fateful ten days, separated into categories. In some cases, these are
applications I currently use over (or in addition to) their graphical
equivalents.
&lt;/p&gt;

&lt;p&gt;
Quite honestly, it is entirely possible to live completely without a GUI (more
or less)—even today, in 2019. And, these applications make it
possible—challenging, but possible.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
Web Browsing&lt;/span&gt;

&lt;p&gt;
Plenty of command-line web browsers exist. The classic Lynx
typically comes to mind, as does ELinks. Both are capable of browsing
basic HTML websites just fine. In fact, the experience of doing so is rather
enjoyable. Sure, most websites don't load properly in the "everything is a
dynamically loading, JavaScript thingamadoodle" future we live in, but the
ones that do load, load &lt;em&gt;fast&lt;/em&gt;, and free of distractions, which makes reading
them downright enjoyable.
&lt;/p&gt;

&lt;p&gt;
But for me, personally, I recommend w3m.
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_650x650/public/u%5Buid%5D/w3m.png" width="564" height="563" alt="w3m" class="image-max_650x650" /&gt;&lt;p&gt;
&lt;em&gt;Figure 1. Browsing Wikipedia with Inline Images Using w3m&lt;/em&gt;
&lt;/p&gt;

&lt;p&gt;
w3m supports inline images (via installing the &lt;code&gt;w3m-img&lt;/code&gt;
package)—seriously, a web browser with image support, inside the terminal. The future is now.
&lt;/p&gt;

&lt;p&gt;
It also makes filling out web forms easy—well, maybe not easy, but at least
doable—by opening a configured text editor (such as nano or vim) for
entering form text. It feels a little weird the first time you do it, but
it's surprisingly intuitive.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/without-gui-how-live-entirely-terminal" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 28 Jun 2019 11:00:00 +0000</pubDate>
    <dc:creator>Bryan Lunduke</dc:creator>
    <guid isPermaLink="false">1340674 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Hello Again, Linux</title>
  <link>https://www.linuxjournal.com/content/hello-again-linux</link>
  <description>  &lt;div data-history-node-id="1340638" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/richard-mavis" lang="" about="https://www.linuxjournal.com/users/richard-mavis" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Richard Mavis&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;My first MacBook was the first computer I really loved, but I wasn't happy
about the idea of buying a new one.
I decided it's important to live your values and to
support groups that value the things you do.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
After ten years of faithful service, last year the time finally came to
retire my MacBook. Not many laptops last ten years—not many companies
produce a machine as durable and beautiful as Apple does—but, if one
was available, I was willing to invest in a machine that might last me
through the next ten years.
A lot has changed in ten years—for Apple, for Linux and for
myself—so
I started looking around.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;The Situation&lt;/span&gt;

&lt;p&gt;
Prior to 2006, I had used only Windows. Around that time, there was a lot
of anxiety about its upcoming successor to Windows XP, which at the time
was code-named Project Longhorn. My colleagues and I all were dreading
it. So, rather than go through all that trouble, I switched to Linux.
&lt;/p&gt;

&lt;p&gt;
However, my first experience with Linux was not great. Although 2006 was &lt;em&gt;The Year of
the Linux Desktop&lt;/em&gt; (I saw headlines on Digg proclaiming it almost every
day), I quickly learned, right after wiping my brand-new laptop's
hard drive to make way for Fedora, that maybe it wasn't quite &lt;em&gt;The Year
of the Linux Laptop&lt;/em&gt;. After a desperate and miserable weekend, I finally
got my wireless card working, but that initial trauma left me leery. So,
about a year later, when I decided to quit my job and try the digital
nomad freelance thing, I bought a MacBook. A day spent hunting down
driver files or recompiling my kernel was a day not making money. I
needed the assurance and convenience Apple was selling. And it proved
a great investment.
&lt;/p&gt;

&lt;p&gt;
During the next decade, I dabbled with Linux. Every year seemed to
be The Year of the Linux Desktop—the real one, at last—so
on my desktop at work (freelancing wasn't fun for long), I
installed Ubuntu, then Debian, then FreeBSD. An article in this
journal introduced me to tiling window managers in general and
&lt;a href="https://www.linuxjournal.com/content/going-fast-dwm"&gt;DWM&lt;/a&gt;
in
particular. The first time I felt something like disappointment with my
MacBook was after using DWM on Debian for the first time.
&lt;/p&gt;

&lt;p&gt;
Through the years, as my MacBook's hardware failures became increasingly
inconvenient, and as my personal preference in software shifted from big
beautiful graphical applications to small command-line programs, Linux
started to look much more appealing. And, Linux's hardware compatibility
had expanded—companies had even started selling laptops with Linux
already installed—so I felt reasonably sure I wouldn't need to waste
another weekend struggling with a broken wireless connection or risk
frying my monitor with a misconfigured Xorg.conf.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/hello-again-linux" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 31 May 2019 13:26:34 +0000</pubDate>
    <dc:creator>Richard Mavis</dc:creator>
    <guid isPermaLink="false">1340638 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>The State of Desktop Linux 2019</title>
  <link>https://www.linuxjournal.com/content/state-desktop-linux-2019</link>
  <description>  &lt;div data-history-node-id="1340362" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/bryan-lunduke" lang="" about="https://www.linuxjournal.com/users/bryan-lunduke" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Bryan Lunduke&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;A snapshot of the current state of Desktop Linux at the start of
2019—with comparison charts and a roundtable Q&amp;A with the leaders of three top
Linux distributions.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
I've never been able to stay in one place for long—at least in terms of which Linux distribution I call home.
In my time as a self-identified "Linux Person", I've bounced around between a
number of truly excellent ones. In my early days, I picked up boxed copies of
S.u.S.E. (back before they made the U uppercase and dropped the dots
entirely) and Red Hat Linux (before Fedora was a thing) from store shelves at
various software outlets.
&lt;/p&gt;

&lt;p&gt;
Side note: remember when we used to buy Operating Systems—and even most
software—in actual boxes, with actual physical media and actual printed
manuals? I still have big printed manuals for a few early Linux versions, which, back then, were necessary for getting just about everything working
(from X11 to networking and sound). Heck, sometimes simply getting
a successful boot required a few trips through those heavy manuals. Ah, those
were the days.
&lt;/p&gt;

&lt;p&gt;
Debian, Ubuntu, Fedora, openSUSE—I spent a good amount of time living in
the biggest distributions around (and many others). All of them were
fantastic. Truly stellar. Yet, each had their own quirks and peculiarities.
&lt;/p&gt;

&lt;p&gt;
As I bounced from distro to distro, I developed a strong attachment to just
about all of them, learning, as I went, to appreciate each for what it
was. Just the same, when asked which distribution I recommend to others,
my brain begins to melt down. Offering any single recommendation feels
simply inadequate.
&lt;/p&gt;

&lt;p&gt;
Choosing which one to call home, even if simply on a secondary PC, is a
deeply personal choice.
&lt;/p&gt;

&lt;p&gt;
Maybe you have an aging desktop computer with limited RAM and an older, but
still absolutely functional, CPU. You're going to need something light on
system resources that runs on 32-bit processors.
&lt;/p&gt;

&lt;p&gt;
Or, perhaps you work with a wide variety of hardware architectures and need a
single operating system that works well on all of them—and standardizing
on a single Linux distribution would make it easier for you to administer
and update all of them. But what options even are available?
&lt;/p&gt;

&lt;p&gt;
To help make this process a bit easier, I've put together a handy set of
charts and graphs to let you quickly glance and find the one that fits your
needs (Figures 1 and 2).
&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_1300x1300/public/u%5Buid%5D/LJ-Jan-2018-BigChart-1.png" width="1004" height="1300" alt="""" class="image-max_1300x1300" /&gt;&lt;p&gt;&lt;em&gt;Figure 1. Distribution Comparison Chart I&lt;/em&gt;&lt;/p&gt;

&lt;img src="https://www.linuxjournal.com/sites/default/files/styles/max_1300x1300/public/u%5Buid%5D/LJ-Jan-2018-BigChart-2.png" width="1004" height="1300" alt="""" class="image-max_1300x1300" /&gt;&lt;p&gt;&lt;em&gt;Figure 2. Distribution Comparison Chart II&lt;/em&gt;&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/state-desktop-linux-2019" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Mon, 31 Dec 2018 12:30:00 +0000</pubDate>
    <dc:creator>Bryan Lunduke</dc:creator>
    <guid isPermaLink="false">1340362 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Weekend Reading: Qubes</title>
  <link>https://www.linuxjournal.com/content/weekend-reading-qubes</link>
  <description>  &lt;div data-history-node-id="1339883" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/carlie-fairchild" lang="" about="https://www.linuxjournal.com/users/carlie-fairchild" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Carlie Fairchild&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;a href="https://www.qubes-os.org/"&gt;Qubes OS&lt;/a&gt; is a security-focused operating system that, as tech editor Kyle Rankin puts it, "is fundamentally different from any other Linux desktop I've used". Join us this weekend in reading Kyle's multi-part series on all things Qubes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.linuxjournal.com/content/secure-desktops-qubes-introduction"&gt;Secure Desktops with Qubes: Introduction&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In this first article, I provide an overview of what Qubes is, some of the approaches it takes that are completely different from what you might be used to on a Linux desktop and some of its particularly interesting security features. In future articles, I'll give more how-to guides on installing and configuring it and how to use some of its more-advanced features.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.linuxjournal.com/content/secure-desktops-qubes-installation"&gt;Secure Desktops with Qubes: Installation&lt;/a&gt;&lt;/p&gt;

&lt;p dir="ltr"&gt;This is the second in a multipart series on the Qubes operating system. In my first article, I gave an overall introduction to Qubes and how it differs from most other desktop Linux distributions, namely in the way it focuses on compartmentalizing applications within different VMs to limit what attackers have access to in the event they compromise a VM. This allows you to use one VM for regular Web browsing, another for banking and a different one for storing your GPG keys and password manager. In this article, I follow up with a basic guide on how to download and install Qubes, along with a general overview of the desktop and the various default VM types.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.linuxjournal.com/content/secure-desktops-qubes-compartmentalization"&gt;Secure Desktops with Qubes: Compartmentalization&lt;/a&gt;&lt;/p&gt;

&lt;p dir="ltr"&gt;This is the third article in my series about Qubes. In the first two articles, I gave an &lt;a href="http://www.linuxjournal.com/content/secure-desktops-qubes-introduction"&gt;overview&lt;/a&gt; about what Qubes is and described &lt;a href="http://www.linuxjournal.com/content/secure-desktops-qubes-installation"&gt;how to install&lt;/a&gt; it. One of the defining security features of Qubes is how it lets you compartmentalize your different desktop activities into separate VMs. The idea behind security by compartmentalization is that if one of your VMs is compromised, the damage is limited to just that VM.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.linuxjournal.com/content/secure-desktops-qubes-extra-protection"&gt;Secure Desktops with Qubes: Extra Protection&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/weekend-reading-qubes" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Sat, 17 Nov 2018 12:29:12 +0000</pubDate>
    <dc:creator>Carlie Fairchild</dc:creator>
    <guid isPermaLink="false">1339883 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>The Asus Eee: How Close Did the World Come to a Linux Desktop?</title>
  <link>https://www.linuxjournal.com/content/asus-eee-how-close-did-world-come-linux-desktop</link>
  <description>  &lt;div data-history-node-id="1340239" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/jeff-siegel" lang="" about="https://www.linuxjournal.com/users/jeff-siegel" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Jeff Siegel&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
&lt;em&gt;It was white, not much bigger than my hands held side by side, weighed
about as much as a bottle of wine, and it came in a shiny, faux-leather case. It
was the $199 Asus Eee 901, and I couldn't believe that a computer could be
that powerful, that light and that much fun.&lt;/em&gt;
&lt;/p&gt;

&lt;p&gt;
This is the story of the brief, shining history of the Asus Eee, the
first netbook—a small, cheap and mostly well-made laptop that dominated
the computer industry for two or three years about a decade go. It's not so
much that the Eee was ahead of its time, which wasn't that difficult in an
industry then dominated by pricey and bulky laptops that didn't always have
a hard drive and by desktop design hadn't evolved much past the first IBM
8086 box.
&lt;/p&gt;

&lt;p&gt;
Rather, the Eee was ahead of everyone's time. It ran a Linux
operating system with a tabbed interface and splashy icons, and the hardware
included wireless, Bluetooth, a webcam and an SSD hard drive—all in a
machine that weighed just 2.5 pounds. In this, it teased many of the concepts
that tech writer Mark Wilson says we take for granted in today's cloud,
smartphone and Chromebook universe.
&lt;/p&gt;

&lt;p&gt;
The Eee was so impressive that even Microsoft, whose death grip on the
PC world seemed as if it would never end, took notice. As everyone from Dell to
HP to Samsung to Toshiba to Sony to Acer to one-offs and "never-weres" raced
netbooks into production, Microsoft offered manufacturers a version of Windows
XP (and later a truncated Windows 7) to cram onto the machines. Because we
can't have the masses running a Linux OS, can we?
&lt;/p&gt;

&lt;p&gt;
"The Eee gave regular people something they couldn't have
before", says Dan Ackerman, a longtime section editor at CNET who wrote
some of the website's original Eee and netbook reviews. "Laptops had
always been ridiculously expensive. The Eee wasn't, and it gave regular
people a chance to buy a laptop that was smaller and more portable and that
they could be productive with. I always gave Asus credit—they understood
the role of form and function."
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
Netbook History&lt;/span&gt;

&lt;p&gt;
The computer world never had really seen anything like the first Eee,
which didn't even have a name when it was launched in 2007 (although it
later would be called both the 701 and the 4G). In fact, say those who reviewed the
701, it wasn't so much a product but a proof of concept—that Asus
could make something that small and that cheap that worked.
&lt;/p&gt;

&lt;p&gt;
There had been small laptops before, of course, like the Intel
Classmate PC and the OLPC X0-1, each part of the One Laptop per Child project.
But those were specialized machines designed to bring computing and the
internet to students throughout the world, and not necessarily consumer
products.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/asus-eee-how-close-did-world-come-linux-desktop" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 02 Nov 2018 13:30:00 +0000</pubDate>
    <dc:creator>Jeff Siegel</dc:creator>
    <guid isPermaLink="false">1340239 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>System76 Announces American-Made Desktop PC with Open-Source Parts</title>
  <link>https://www.linuxjournal.com/content/system76-announces-american-made-desktop-pc-open-source-parts</link>
  <description>  &lt;div data-history-node-id="1340238" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/bryan-lunduke" lang="" about="https://www.linuxjournal.com/users/bryan-lunduke" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Bryan Lunduke&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;Early in 2017—nearly two years ago—System76 invited me, and a handful of others, out to its Denver headquarters for a sneak peek at something new they'd been working on.&lt;/p&gt;

&lt;p&gt;We were ushered into a windowless, underground meeting room. Our phones and cameras confiscated. Seriously. Every word of that is true. We were sworn to total and complete secrecy. Assumedly under penalty of extreme death...though that part was, technically, never stated.&lt;/p&gt;

&lt;p&gt;Once the head honcho of System76, Carl Richell, was satisfied that the room was secure and free from bugs, the presentation began.&lt;/p&gt;

&lt;p&gt;System76 told us the company was building its own desktop computers. Ones that it designed themselves. From-scratch cases. With wood. And inlaid metal. What's more, these designs would be open. All built right there in Denver, Colorado.&lt;/p&gt;

&lt;p&gt;We were intrigued.&lt;/p&gt;

&lt;p&gt;Then they showed them to us, and we darn near lost our minds. They were gorgeous. We all wanted them.&lt;/p&gt;

&lt;p&gt;But they were not ready yet. This was early on in the design and engineering, and they were looking for feedback—to make sure System76 was on the right track.&lt;/p&gt;

&lt;p&gt;They were.&lt;/p&gt;

&lt;p&gt;Flash-forward to today (November 1, 2018), and these Linux-powered, made in America desktop machines are finally being unveiled to the world as the Thelio line (which they've been teasing for several weeks with a series of &lt;a href="https://thel.io/"&gt;&lt;u&gt;sci-fi themed stories&lt;/u&gt;&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;The Thelio comes in three sizes:&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;Thelio (aka "small") — max 32GB RAM, 24TB storage.&lt;/li&gt;
	&lt;li&gt;Thelio Major (aka "medium") — max 128GB RAM, 46TB storage.&lt;/li&gt;
	&lt;li&gt;Thelio Massive (aka "large") — max 768GB RAM, 86TB storage.&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;&lt;img alt="Image removed." class="image-max_650x650 filter-image-invalid" data-entity-type="file" data-entity-uuid="insert-max_650x650-bd90d59b-9116-4542-84f2-c81988784dd5" height="16" src="https://www.linuxjournal.com/core/misc/icons/e32700/error.svg" width="16" title="This image has been removed. For security reasons, only images from the local domain are allowed." /&gt;&lt;/p&gt;

&lt;p&gt;All three sport the same basic look: part black metal, part wood (with either maple or walnut options) with rounded side edges. The cases open with a single slide up of the outer housing, with easy swapping of components. Lots of nice little touches, like a spot for in-case storage of screws that can be used in securing drives.&lt;/p&gt;

&lt;p&gt;In an awesomely nerdy touch, the rear exhaust grill shows the alignment of planets in the solar system...at UNIX Epoch time. Also known as January 1, 1970. &lt;a href="https://en.wikipedia.org/wiki/Unix_time"&gt;&lt;u&gt;A Thursday&lt;/u&gt;&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;img alt="Image removed." class="image-max_650x650 filter-image-invalid" data-entity-type="file" data-entity-uuid="insert-max_650x650-8695d750-6fa1-4c11-860f-3916df6af995" height="16" src="https://www.linuxjournal.com/core/misc/icons/e32700/error.svg" width="16" title="This image has been removed. For security reasons, only images from the local domain are allowed." /&gt;&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/system76-announces-american-made-desktop-pc-open-source-parts" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 01 Nov 2018 15:01:36 +0000</pubDate>
    <dc:creator>Bryan Lunduke</dc:creator>
    <guid isPermaLink="false">1340238 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>FOSS Project Spotlight: Nitrux, a Linux Distribution with a Focus on AppImages and Atomic Upgrades</title>
  <link>https://www.linuxjournal.com/content/foss-project-spotlight-nitrux-linux-distribution-focus-appimages-and-atomic-upgrades</link>
  <description>  &lt;div data-history-node-id="1340084" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/nitrux-latinoamericana-sc" lang="" about="https://www.linuxjournal.com/users/nitrux-latinoamericana-sc" typeof="schema:Person" property="schema:name" datatype="" content="Nitrux Latinoamericana S.C." xml:lang=""&gt;Nitrux Latinoa…&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;
Nitrux is a Linux distribution with a focus on portable, application formats
like AppImages. Nitrux uses KDE Plasma 5 and KDE Applications, and it also uses
our in-house software suite Nomad Desktop.&lt;/em&gt;
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;
What Can You Use Nitrux For?&lt;/span&gt;

&lt;p&gt;
Well, just about anything! You can surf the internet, word-process, send
email, create spreadsheets,
listen to music, watch movies, chat, play games, code, do photo editing,
create content—whatever you want!
&lt;/p&gt;

&lt;p&gt;
Nitrux's main feature is the Nomad Desktop, which aims to extend Plasma to suit new users without
compromising its power and flexibility for experts. Nomad's features:
&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;
The System Tray replaces the traditional Plasma version.
&lt;/li&gt;

&lt;li&gt;
An expanded notification center allows users to manage
notifications in a friendlier manner.
&lt;/li&gt;

&lt;li&gt;
Easier access to managing networks: quick access to different
network settings without having to search for them.
&lt;/li&gt;

&lt;li&gt;
Improved media controls: a less confusing way to adjust the
application's volume and integrated media controls.
&lt;/li&gt;

&lt;li&gt;
Calendar and weather: displays the traditional Plasma calendar but
also adds the ability to see appointments and the ability to configure
location settings to display the weather.
&lt;/li&gt;

&lt;li&gt;
Custom Plasma 5 artwork: including Look and Feel, Plasma theme,
Kvantum theme, icon theme, cursor themes, SDDM themes, Konsole theme and
Aurorae window decoration.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Nitrux is a complete operating system that ships the essential apps and
services for daily use: office applications, PDF reader, image editor,
music and video players and so on. We also include non-KDE or Qt applications like
Chromium and LibreOffice that together create a friendly user experience.
&lt;/p&gt;

&lt;span class="h3-replacement"&gt;Available Out of the Box&lt;/span&gt;

&lt;p&gt;
Nitrux includes a selection of applications carefully chosen to perform the
best when using your computer:
&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;
Dolphin: file manager.
&lt;/li&gt;

&lt;li&gt;
Kate: advanced text editor.
&lt;/li&gt;

&lt;li&gt;
Ark: archiving tool.
&lt;/li&gt;

&lt;li&gt;
Konsole: terminal emulator.
&lt;/li&gt;

&lt;li&gt;
Chromium: web browser.
&lt;/li&gt;

&lt;li&gt;
Babe: music player.
&lt;/li&gt;

&lt;li&gt;
VLC: multimedia player.
&lt;/li&gt;

&lt;li&gt;
LibreOffice: open-source office suite.
&lt;/li&gt;

&lt;li&gt;
Showimage: image viewer.
&lt;/li&gt;&lt;/ul&gt;&lt;span class="h3-replacement"&gt;
Explore a Universe of Apps in Nitrux&lt;/span&gt;

&lt;p&gt;
The NX Software Center is a free application that provides Linux users with a
modern and easy way to manage the software installed on their open-source
operating systems. Its features allow you to search, install and manage
AppImages. AppImages are faster to install, easier to create and safer to
run. AppImages aim to work on any distribution or device, from IoT devices to
servers, desktops and mobile devices.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/foss-project-spotlight-nitrux-linux-distribution-focus-appimages-and-atomic-upgrades" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 21 Sep 2018 13:41:37 +0000</pubDate>
    <dc:creator>Nitrux Latinoamericana S.C.</dc:creator>
    <guid isPermaLink="false">1340084 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Edit PDFs with Xournal</title>
  <link>https://www.linuxjournal.com/content/edit-pdfs-xournal</link>
  <description>  &lt;div data-history-node-id="1340060" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;Forget all of those magical command-line PDF incantations and edit
your PDFs easily with Xournal.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
Somehow, despite all the issues with proprietary clients and the history of
security issues with Acrobat, PDFs have become the de facto standard for your
average print-ready document shared around the office. Sure, people might use
some kind of open document format or a cloud editor if they intend to edit a
document, but if the goal is to print the document or lock its
contents in place, most people these days will export it to a PDF.
&lt;/p&gt;

&lt;p&gt;
Reading PDFs is typically fine on Linux, because Linux has plenty of
applications that can open PDFs for viewing, and you easily can print PDFs
under Linux as well. Even Adobe supplied a proprietary (and somewhat outdated)
port of its Acrobat Reader for Linux. Some distributions also offer the
ability to create a special software printer that converts any print job sent
to it into a local PDF file.
&lt;/p&gt;

&lt;p&gt;
The problem comes when people want to turn read-only print-ready PDFs into
read-write documents you need to modify. As more people work in paperless
offices with strictly digital documents and fewer people own fax machines, you
are more likely to find official documents like contracts show up in your
INBOX in PDF format. These contracts likely were created with a proprietary PDF
editor tool, and they usually have blanks for you to fill in and often
signature lines so you can add a real signature. Unfortunately, for the longest
time, even if you were using Adobe's own Linux port of Acrobat Reader, you
couldn't reliably edit these PDFs, and you certainly couldn't easily add a real
signature.
&lt;/p&gt;

&lt;p&gt;
A lot of Linux applications claim the ability to edit PDFs from
graphical tools like GIMP, or the aforementioned Acrobat Reader or tools like
Inkscape. In the past, I've even gone so far as to use command-line tools
to convert a PDF into multiple pages of a different format, edit that
format, then use the command-line tools to convert it back to a PDF.
&lt;/p&gt;

&lt;p&gt;
Then I discovered Xournal. Xournal is a graphical tool that's designed for
note-taking and sketching either with a keyboard and mouse or even with a
tablet and stylus. This program is pretty common, and you should be able to
install it in any major Linux distribution, but otherwise, you can download the
software from its &lt;a href="http://xournal.sourceforge.net"&gt;Sourceforge
page&lt;/a&gt;.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/edit-pdfs-xournal" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 06 Sep 2018 12:00:00 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1340060 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Organizing a Market for Applications</title>
  <link>https://www.linuxjournal.com/content/organizing-market-applications</link>
  <description>  &lt;div data-history-node-id="1340095" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/sriram-ramkrishna" lang="" about="https://www.linuxjournal.com/users/sriram-ramkrishna" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Sriram Ramkrishna&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
The "Year of the Desktop" has been a perennial call to arms that's sunken into a
joke that's way past its expiration date. We frequently talk about
the "Year of the Desktop", but we don't really talk about how we would
achieve that goal. What does the "Year of the Desktop" even look like?
&lt;/p&gt;

&lt;p&gt;
What it comes down to is applications—rather, a market for applications.
There is no market for applications because of a number of cultural
artifacts that began when the Free Software was just getting up on wobbly legs.
&lt;/p&gt;

&lt;p&gt;
Today, what we have is a distribution-centric model. Software is
distributed by an OSV (operating system vendor), and users get their software
directly from there via whatever packaging mechanism that OSV supports.
This model evolved, because in the early-to-mid 1990s, those OSVs existed to
compile the kernel and userspace into a cohesive product. Packaging of
applications was the next step as a convenience factor to save users from
having to compile their own applications, which always was a hit-or-miss
endeavor as developers
had different development environment from the users. Ultimately, OSVs
enjoyed being gatekeepers as part of keeping developers honest and fixing
issues that were unique to their operating system. OSVs saw themselves as
agents representing users to provide high-quality software, and there was a
feeling
that developers were not to be trusted, as of course, nobody knows the state
of their operating system better than they would.
&lt;/p&gt;

&lt;p&gt;
However, this model represented a number of challenges to both
commercial and open-source developers. For commercial developers, the
problem became how to maximize their audience as the "Linux"
market consisted of a number of major OSVs and an uncountable number of
smaller niche distributions. Commercial application developers would have
to develop multiple versions of their own application targeted at
various major distributions for fear of missing out on a subset of users.
Over time, commercial application developers would settle on using Ubuntu
or a compressed tar file hosted on their website. Various distributions would
pick up these tar balls and re-package them for their users. If
you were an open-source developer, you had the side benefit of distributions
picking up your work automatically for you and packaging them if you
successfully enjoyed a large following. But they faced the same dilemma.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/organizing-market-applications" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 24 Aug 2018 13:08:08 +0000</pubDate>
    <dc:creator>Sriram Ramkrishna</dc:creator>
    <guid isPermaLink="false">1340095 at https://www.linuxjournal.com</guid>
    </item>
<item>
  <title>Why the Failure to Conquer the Desktop Was Great for GNU/Linux</title>
  <link>https://www.linuxjournal.com/content/why-failure-conquer-desktop-was-great-gnulinux</link>
  <description>  &lt;div data-history-node-id="1339910" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/glyn-moody" lang="" about="https://www.linuxjournal.com/users/glyn-moody" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Glyn Moody&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;AI: open source's next big win.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
Canonical recently launched Ubuntu 18.04 LTS. It's an
important release. In part, that's because Canonical will
support it for five years, making it one of the relatively rare &lt;a href="https://wiki.ubuntu.com/LTS"&gt;LTS&lt;/a&gt; products in Ubuntu's history.
Ubuntu 18.04 also marks a high-profile return to GNOME as the default
desktop, after a few years of controversial experimentation with Unity.
The result is regarded by many as the best desktop Ubuntu so far (that's my
view too, for what it's worth). And yet, the emphasis at launch lay elsewhere. Mark
Shuttleworth, CEO of Canonical and founder of Ubuntu, said:
&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;
Multi-cloud operations are the new normal. Boot-time and
performance-optimised images of Ubuntu 18.04 LTS on every major public
cloud make it the fastest and most efficient OS for cloud computing,
especially for storage and compute-intensive tasks like machine
learning.
&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;
The bulk of &lt;a href="https://insights.ubuntu.com/2018/04/26/ubuntu-18-04-lts-optimised-for-security-multi-cloud-containers-ai"&gt;the
official 18.04 LTS announcement&lt;/a&gt; is about Ubuntu's &lt;a href="https://www.linuxjournal.com/content/everything-you-need-know-about-cloud-and-cloud-computing-part-i"&gt;cloud
computing&lt;/a&gt; features. On the main web site, Ubuntu claims
to be "&lt;a href="https://www.ubuntu.com/cloud"&gt;The standard
OS for cloud computing&lt;/a&gt;", citing (slightly old) research
that shows "70% of public cloud workloads and 54% of OpenStack
clouds" use it. Since Canonical is a privately held company,
it doesn't publish a detailed breakdown of its operations, just &lt;a href="https://beta.companieshouse.gov.uk/company/06870835/filing-history"&gt;a
basic summary&lt;/a&gt;. That means it's hard to tell just how successful
the cloud computing strategy is proving. But, the fact that &lt;a href="https://www.youtube.com/watch?time_continue=235&amp;v=y4lF_fYxvIk"&gt;Shuttleworth
is now openly talking about an IPO&lt;/a&gt;—not something to be undertaken
lightly—suggests that there is enough good news to convince
investors to throw plenty of money at Canonical when the prospectus
spells out how the business is doing.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/why-failure-conquer-desktop-was-great-gnulinux" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Mon, 06 Aug 2018 11:30:00 +0000</pubDate>
    <dc:creator>Glyn Moody</dc:creator>
    <guid isPermaLink="false">1339910 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
