Language Selection

English French German Italian Portuguese Spanish

Setting Up the Ideal Linux Desktop

Filed under
Linux

After years of authorized and -- I admit -- the occasional unauthorized but non-tampering snooping, I'm overdue to offer reciprocity. I'm not naive enough to throw open my machine for everyone to examine online, but, over the years, I have developed several pages of hard-earned notes that I follow and revise whenever I buy and set up a new computer.

Since I'm currently mulling buying another computer in the spring, I'm sharing them now. I figure that many other people share my insatiable curiosity, and, like me, can find a benefit or two by seeing how someone else approaches the task of preparing a computer to run with their favorite free operating system.

Selecting hardware and general setup

If I were doing nothing more than writing and web work, I wouldn't buy a new computer. Instead, I'd get a refurbished two or three year old computer from Free Geek Vancouver, saving me cash and making me environmentally responsible while giving me all the computing power I need.

However, I occasionally do graphics work or review software that strains system resources, so I try to have at least one reasonably up to date computer. I always buy a customized workstation from a small specialty store (every major urban center should have a couple) after researching GNU/Linux hardware compatibility. Then, when it's assembled, I take a live CD -- preferably from my distribution of choice -- and test the assembled computer at the store before I take it home. These days, hardware compatibility is less and less of an issue, but, by making this effort, I sidestep any problems that might lessen the joy of a new machine.

Annoyingly, I don't have the same option for a customized machine if I buy a laptop.

More Here




More in Tux Machines

more of today's howtos

Leftovers: OSS and Sharing

Microsoft Begs, Bugs, and Bug Doors

  • Don't install our buggy Windows 10 Creators Update, begs Microsoft
    Microsoft has urged non-tech-savvy people – or anyone who just wants a stable computer – to not download and install this year's biggest revision to Windows by hand. And that's because it may well bork your machine. It's been two weeks since Microsoft made its Creators Update available, and we were previously warned it will be a trickle-out rather than a massive rollout. Now, Redmond has urged users to stop manually fetching and installing the code, and instead wait for it to be automatically offered to your computer when it's ready.
  • Microsoft Word flaw took so long to fix that hackers used it to send fraud software to millions of computers
    A flaw in Microsoft Word took the tech giant so long to fix that hackers were able to use it to send fraud software to millions of computers, it has been revealed. The security flaw, officially known as CVE-2017-0199, could allow a hacker to seize control of a personal computer with little trace, and was fixed on April 11 in Microsoft's regular monthly security update - nine months after it was discovered.

FOSS Licensing (and Lack Thereof)

  • Portugal to harmonise usability of govt portals
    All of the code, information and tools are made available for reuse.
  • JRC: ‘Releasing code without a licence hinders reuse’
    Projects that publish source code without a licence weaken the reusability of their code, warns Stefano Gentile, a copyright and trademark specialist working for the European Commission’s Joint Research Centre (JRC). Currently just 20 % of all projects published on GitHub, one of the most popular source code sharing platforms, have selected a licence for their work - down from about 60% in 2008, Gentile said, quoting numbers published in 2015 by GitHub.
  • React to React
    The Additional Grant of Patent Rights is a patent license grant that includes certain termination criteria. These termination criteria are not entirely unprecedented when you look at the history of patent license provisions in OSI-approved licenses, but they are certainly broader than the termination criteria [or the equivalent] in several familiar modern licenses (the Apache License 2.0, EPL, MPL 2.0, and GPLv3).
  • BetConstruct declares the source code for its front-end as open source
    The project is distributed under MIT license.