Archiv der Kategorie: Linux

All about Linux.

You stay where you started… Most of us do…

In response to Back with Mac again – And Here to Stay by Simon Royal.


Such an odd word. Upbringing. But in a strange way it fits. When you analyze it, you would eventually find that it all boils down to exactly this: Your own „IT youth“ so to say. What were the systems, computers and operating software, that you were brought up with? With what (brand of) hardware and software did you start your computer use, and continue to use them up until this very day?

In my case it was PCs with some version of DOS at first: a 386SX with 25 MHz and DR DOS 5.0. And Windows 3.0. I remember this because it was my first computer. So I am a Windows guy, right?

In school we also used DOS and NetWare from Novell for the school network. Later the school had some version of Windows, but at this time I had already graduated and left my school for good.

IT – Information Technology – was since not my area of expertise in my professional life other than the common use of computers at the office. Those were PCs, the software was and is Microsoft dominated. In fact, we only had Windows from the start. NT 4.0, which I liked, then XP and later Windows 7.

The servers ran Linux though. Not all of them, I guess, but most of the network backbone was Linux-based. As an office guy that just uses the software provided I didn’t get to see this infrastructure though, so no fiddling with Linux at the work side of my life.

In private life I got in contact with other operating systems early on. In my youth I used to play on my friends and neighbors Commodore C64 and Amiga 500. On my own PCs I briefly tried Windows NT 4.0 and 2000, but my main system was Windows 95, later 98 and 98 Second Edition. I gave up on DR DOS with Windows 95, even though I preferred DR DOS over MS-DOS. I never tried IBM’s version of MS-DOS though, PC DOS, but I had a brief look at PTS-DOS, which was rocking fast and the full system fit on only one 1.44 MB floppy disk! Amazing! Windows 95 then ended all this broad variety of Disk Operating System options to choose from…

In the late 1990ies I started to look into Linux for the first time. I also tried OS/2 Warp 3.x, but it was complicated (especially the hardware support). I think my first Linux was around early 1997 and the Linux Distribution was S.u.S.E. Linux 4.2. The installation procedure was so complicated, there were so many new and unknown packages to choose for installation, and the Unix shell, bash or any other – I honestly don’t remember, was so confusing that I soon lost interest. It was too much for me, information overflow so-to-say, being used to the easy way that Windows 9x supplied in comparison.

I finally took off with Linux in the early 2000s, after a short-lived period of using Mandrake Linux – a very easy-to-use and user-friendly Linux of its time. But Mandrake Linux became Mandriva Linux, new releases were being delayed, and I found myself looking for alternatives. I tried Fedora (RedHat) as well as SuSE (OpenSuSE, Novell) and finally came to Gentoo Linux. Although I remember also considering Arch and Debian…

Gentoo Linux

For me, the reason to dig into Gentoo Linux was that I really wanted to understand how things were made to work in Linux. I wanted to get acquainted to Linux, if you will.

Gentoo Linux really made me love Linux. I was finally understanding how things worked a lot better and I was in the position to decide and control the whole of my operating system. Almost every aspect of it, except for the source code itself. But that would have been accessible too. Even more, with Gentoo Linux I had to configure everything myself, because there is no real preconfiguration like other distributions offer. Everything is controlled, decided and configured by the user (or admin).

The installation of a Gentoo Linux based system, up to getting a working desktop, still takes a few days. I just recently set up my new system, an AMD Ryzen 7 1800X, 2017. It was about a week until I had a desktop running. Not at all like Windows or macOS, right?

Mac OS X

I never used classic Mac OS or Macintosh System Software. I touched the first Mac in the year 2005 or so, and Mac OS X 10.3 aka Panther was still current then, Tiger was soon to be released. I was impressed by the quality of the hardware: It was a Power Mac G4 MDD, original, Dual-1 GHz model.

I also installed Gentoo Linux on that machine and was very impressed how well the Power Mac was supported. Everything worked. Fact is, I went from a Pentium III 800 MHz to a G4 MPC 7450 dual processor system, just copied the /home directory, and was back in business. Hardware-wise this was a migration from a little endian x86 platform to a big endian PowerPC platform, and Linux let me do it! Amazing!

And then Apple did the same in the opposite direction: 2005 was the year Steve Jobs announced that Apple was going to replace PowerPC processors with Intel x86 processors… And, yes, Mac OS X, based on Rhapsody, based on OPENSTEP/NeXTStep let them do it quite easily too!

Anyway, my first Apple operating system was Panther and I found it quite intuitive to use, but I came from Linux and Windows and DOS, so maybe it wasn’t very hard for me to understand how Mac OS X worked. Also, Panther was a very solid and stable operating system. The only thing I had to get used to was the Finder. At first I really preferred the command line, I even installed the Midnight Commander on Mac OS X to use it in Terminal. After a while though I started to like the Finder, even more than the Windows Explorer. I still don’t like the Explorer, but find working with the Finder okay… and still prefer the Midnight Commander on a terminal on Linux.

So, I upgraded to Tiger and found little difference. Yes, Spotlight. Okay. I never used this and also not the Dashboard. Too fancy for me. I used and still do use a lot though! In a way, I guess you can say, that I love Unix, and the Unix shell. Especially bash is very nice to use, with command history and so forth.

I did not like Mac OS X Leopard 10.5 so much. It was heavy, slow and blown on a Power Mac. Tiger and Panther rocked, but Leopard was just all about the graphics polish, not about the performance. Also, Apple killed the Classic Environment with Leopard, so I wasn’t happy about that either, since I was just beginning to experiment on using older applications and games.

I now ask myself, what my relationship with Mac OS X really is? What I came up is my very personal perspective, and this is what I can say:

I really liked Tiger. I think with 10.4 Apple created their masterpiece. It was very polished, solid, had a wide support for older and newer Apple systems (it ran on 1999 Macs as well as on 2006+ Intel-Macs, and it had Classic on PowerPCs) and in my opinion it is what Apple wanted to accomplish with Mac OS X when they started it in 1998. This was it! How can such a perfect system get better?

And here lies the tragedy. I had come from Linux and appreciated the possibilities of a true Unix system. Apple, on the contrary, decided to go more for the iPad-way of doing things: hide the Unix base, make the OS all shiny but more and more uninteresting for people who like the command line. At least that was my impression. I could be wrong. But nowadays, in High Sierra and Mojave, it’s all about the App Store, isn’t it? Device drivers (kexts in Mac OS X) have to be signed, and installing a simple open source application lets macOS ask „Are you sure? It could be malware, since I (Apple) didn’t approve it!“ My very, very personal response to that: That’s just sh*t!

As far as privacy goes, I also have my second thoughts. It’s not that I distrust Apple, but at the same time also „Why should I trust Apple?“ in the first place? It makes no sense. I take my responsibility serious, and by doing so the only option I have is to use an open source operating system. Like Linux. Or FreeBSD, OpenBSD, NetBSD.

Darwin, the open source core of macOS, isn’t freely available by the way. You cannot get it installed on a Mac, because it lacks all the fancy device drivers that are needed to run it on a Mac. Apple used to be different, but now they don’t even provide an installer for Darwin. Darwin, as a free and open distribution, was on the decline since Mac OS X and Apple became a success, so Apple wasn’t really interested anymore.

I now own a couple of older Power Macs, a G3, G4s and G5s, and I also bought myself two Mac mini’s. Intel-based. Yes, I know. They are the 2011 models and they are the last ones that are unofficially able to run Snow Leopard 10.6.8. I use them with Snow Leopard and run all my old PowerPC software on them through Rosetta. I refuse to get anything newer because… Why would I? I wouldn’t be able to use my old software, which I still use, and my old devices, like my 2006 iPod nano.

Still, the Mac mini opened up the opportunity to look into macOS up to High Sierra. And what can I say? Well, I don’t like what I see.
I get it that it is important to support high resolution displays. And quite frankly, this support came way too late. I remember that I had trouble reading stuff even on Mac OS X Tiger when I used a larger monitor, like full HD 1920×1080. Instead, they tweaked the look of the Dock. All new and pseudo-3D it came with Leopard – and now look: With macOS the Dock finally looks 2D like in Tiger again!
And why must it integrate in social networks so much? I don’t appreciate that at all. I’m not lightly giving away my identity, so I don’t enter anything into those fields. As much as macOS is concerned, I don’t even have a Facebook and Twitter account. And all the rest. I don’t even have an e-mail address!

In other words: I only truly trust myself, so as a result I can only trust the Linux I configured, which is Gentoo Linux in my case.


I can understand that people like macOS and like to work with it. Like I can understand how people like to work with Windows. But that’s not for me.

In essence, it all boils down to trust. Who do I really trust? And if you trust a billion dollar company, that’s fine with me. But be aware that their main business is to make money, not to protect you. Because that’s your job, your own responsibility. Even if it is convenient for you to out-source this responsibility, to Apple if you run macOS, or to Microsoft if you run Windows 10.

But to get back to my initial statement: The full title really should have been: You stay where you started… At least most of us do… Sadly.

The big companies also know that. And they promote it by supplying schools, collages and universities with almost free student licenses. Sometimes such licenses are even completely gratis. But in reality they aren’t, because they influence your upbringing, your IT youth. You start with this system, and guess which system you will prefer later in life?

Don’t get me wrong. Apple has made it quite clear that they do a lot to protect the privacy of their users (equals customers). But for me that’s not enough.

As for working with macOS, for me personally, I just now found that the most fancy version for me to use actually is – get seated, otherwise you might fall due to either shock or laughter – is: Jaguar! Yes. Mac OS X 10.2. I just started to appreciate its retro-look and the small little details, almost flaws, in its design. It is not yet the finished, stable and perfect GUI that Tiger has, but it has some kind of (to me) appealing charm so that I keep using it, despite the availability of Tiger and Leopard on Power Macs.

On the Mac mini, sadly, I have to use Snow Leopard, but this is still way better for my taste than the new macOS (High Sierra and Mojave at the time of this article).

That said, on my main computer, a PC, I use Gentoo Linux, and it will stay that way. On some of my Macs I run Debian GNU/Linux, just because it is way easier and quicker to get installed. It doesn’t have to compile the source code for days and weeks… 😉 But it’s getting harder and harder, because support was already dropped and it is now an „unsupported“ platform, which means that it can be installed, but no guarantees. And that’s what you get: Some things simply don’t work out-of-the-box, and some software recently stopped working. Thus I’m considering Gentoo Linux on the old Power Macs as well, maybe with a binary repository so I only need to compile the packages once and can install them on all the Power Macs I own.

Your opinion?

So, what do you think of my hypothesis? Is it true? Do you also see it that way too? Or was this complete rubbish to you?

I’d be happy to read your comments.


Dear Computer Makers: be visionary, unleash the power of Linux

I’ve just read this article by Jim Mendenhall. Yes, a Linux pre-installation would be a good thing. But I just cannot agree with his choice of Linux distribution: Ubuntu.

Linux for the masses

Ubuntu is said to be the Linux for beginners. But it really is awful. A lot of Linux newbies don’t like Linux because of Ubuntu. Show them Gnome 2 or KDE 4 and they may stay, show them Unity and the run away!

Ubuntu has to go its own way. Mir instead of Wayland, Unity instead of Gnome or KDE. Upstart instead of systemd. Yes, upstart was there first, I know; and they will eventually make the switch to systemd, which probably was greatly inspired by upstart. In this regard: thank you Ubuntu! But Mir and Unity really wasn’t necessary on the desktop!

Linux is all about choice!

There is no Linux but all of them! Linux users like to choose which distribution they want to use. They like to choose which desktop to use.

They like to choose on the hardware side as well: it’s not always low-end they want. Sometimes they’d like to get a high-end computer, but there is none specifically for Linux!

If you know that, pre-installation suddenly doesn’t make that much sense anymore. The only thing a vendor can do is to actively help letting the user make choices of his own and to eagerly help with Linux support. This means: a clean and working BIOS or UEFI implementation, which is commited clearly to supporting Linux from the firmware side, and not the other way around. (And there is nothing wrong with supporting Windows as well!)

The hardware and the firmware of a Linux computer

So what does this mean? It means that the firmware (like the BIOS or UEFI) has to be suitable for Linux so that Linux must not use workarounds, so called “quirks” which in their quantity bloat the kernel already. A firmware designed for Linux – that’s real Linux support.

Another support could be to provide firmware blobs for embedded devices inside a special firmware area for the Linux kernel to grab and use. This situation is less a long-term target than it is here-and-now necessity.
The Linux kernel would have to be patched so that support for such a – please: standardised! – “firmware blob interface” would be present, but then this could be used for all Linux firmware implementations from various computer vendors.

The long-term goal is to use hardware that does not require blobs at all. This is the hardest part, as it requires vendors to stand up for open devices. If, for example, a WiFi chip is used, then the computer vendor has to get the WiFi chip vendor to help develop an open source Linux driver that does not require a firmware blob at all. Open specifications would be one way to do this, but most chip vendors say they cannot release this information due to intellectual property and due to their industrial secrets they want to keep. It’s a dilemma.
Even more so, the CPU itself has firmware blob issues, like the Librem Laptop project found out the hard way.

So there are two ways to go:

  1. either try to go fully open source,
  2. or make the best of it and help as much as you can.

Trying to be fully open source

As of 2014, I see lots of small hacking & development devices fully open sourced, and only one laptop-to-be:

  1. the Novena is a low-end laptop-to-be
  2. lots of Rasperry-Pi-like open source hardware
  3. the AMD Gizmo is also intended for developers

Making the best of the firmware blob situation

Most Linux-pre-loaded laptops are basically “designed for Windows” machines that come with Ubuntu:

  1. Dell, HP, ASUS, to name just a few vendors selling lower-end linux laptops and netbooks
  2. the Librem 15 is an exception, as it tries to be higher-end, but it is still a laptop-to-be…

The only problem with how it is now is that support ends with the pre-installed linux. Maybe a driver support site lets you download some linux drivers, but often they will not work well on other distros. And these vendors don’t let the Linux community provide help. And: where are the high-end Linux computers?!?

A new über-firmware approach?

I have an idea. It actually isn’t new, but it transforms the idea of choice towards operating systems.

First, you all know, or have at least heard of, that Microsoft was sued in Europe and finally forced to provide a choice of which internet browser to use on Windows – and this freedom of choice had to be presented highly visible to the user: the Browser Choice.

So, how would you like to get an “operating system choice”? The idea is as follows:

  1. Use an open firmware, like coreboot (wiki)
  2. Include a module (payload) that is some kind of Mini OS
    • read-only
    • Internet access
    • choice of operating system
    • partition management (like gparted)
    • include a special service partition (noexec!), where
      • you can download drivers and manuals to
      • and save configuartion backup on
  3. This Mini OS could let you chooce which OS you would like to use, including commercial operating systems – yes, even Microsoft Windows.

Even more, this firmware should be able to provide a safe pre-initialization environment that prevents malware from being loaded from hard disk drives or other sources, to provide a safe environment for firmware updates.

  1. TWO firmware chips:
    1. read-only firmware ROM chip on a socket: a factory-default hence safe firmware and Mini OS
    2. a flashable – updateable – firmware flash chip with updated firmware blobs (microcode, AGESA update, blobs for various chips), an updated coreboot firmware and an updated Mini OS
  2. the flashable i.e. second firmware chip should be jumper-securable to read-only setting as well. This should cover for malware infection prevention.
  3. each and every embedded chip must be read-only as well, making it only possible to modify by the firmware provided updated
    1. this too provides durable malware protection, as no malware is then able to hide deep in the system – if such a system gets infected, all that is needed it to reset the firmware completely using the factory-default image from the first read-only firmware ROM chip
    2. since both firmware chips riside on a socket, they can even be updated in terms of storage capacity and, for the ROM chip, in firmware version


I know this idea is kind of idialistic. But hey, all innovations started with some kind of far-fetched vision, right?

In my opinion, an open source computer can only start by using an open source firmware of some kind.

And a Linux computer can only be about choice. Because Linux is about choice. That said, only the program that runs before the actual Linux distribution can provide such a choice to the user. That would be the firmware then: an über-firmware, that asks the user which distribution – which operating system – (s)he wants to install and use. And it should provide means to assist with this installation, like by conveniently providing the required drivers and firmware blobs.


Even more far-fetched: such an über-firmware could also act as a hypervisor for multi-boot installations. Just imagine: in the firmware you decide which resources an operating system gets, the firmware provides the virtualized environment for the OS and then allows you to boot that operating system. As a hypervisor it would theoretically also be possible to stop that OS, save its state, switch to an other OS, or even let the OS continue to run in the background and finish its job while the user works with one the other OSes.

A Linux vision

As long as Linux computers try to copy pre-installations as we see them from Microsoft Windows they lack a unique Linux vision. There is no Linux way nor a real open source way perceptible.

Linux users deserve better. They deserve better computers than low-end models with pre-installed Ubuntu.

Linux vendors ought to do better. They should work with the open source community, build on already existing software technologies (like coreboot) and envision how to enhance the Linux experience for every user: even if the user installs and uses only one distro. It is worth the effort, since other Linux users will discover the potential, they will help to develop and enhance the implementations, they will help build a community around it. They will spent hours providing drivers/firmware for their favorite distro, help other users in forums, write wiki pages, translate documentations, contribute code – they will even build KVM and Docker images if you let them!

Dear computer makers! Be visionary! And trust in the community – work with them!

Unleash the power of Linux: the freedom of choice!

5 KDE-Funktionen, die ich auf einem Desktop vermissen würde

5 Dinge, die ich auf meinem Desktopbetriebssystem nicht mehr missen möchte – und die ich auf dem K Desktop Environment (KDE) sofort gerne genutzt habe!

1. Markierter Text Kopieren&Einfügen mit Mittelklick

Durch das Markieren von Text wird eine Art zweite Zwischenablage befüllt, deren Inhalt sich mit dem Mittelklick auf das Mausrad (Maustaste 3) einfügen lässt. Benutzt man zuvor bei einer Markierung die normale Kopieren&Einfügen-Funktion mit Strg+C, dann hat man anschließend zwei Einfüge-Vorgänge „frei“, ohne auf das vorige Fenster zurück zu müssen.

Ich liebe das. Außerdem ist für einfaches Copy&Paste kein Ctrl+C mehr nötig, weil ein Markieren + Mittelklick reicht. Viel schneller, viel einfacher.

Leider führt das auch oft dazu, dass ich unter Windows einen zweiten Versuch brauche, weil der Mittelklick in ein leeres Textfeld nicht den zuvor markierten Text einfügt, sondern entweder keine Funktion, oder aber eine andere Funktion auslöst. Ärgerlich.

2. Klipper

Klipper erweitert die Zwischenablage ins unendliche. Damit kann man zuvor zuvor zuvor zuvor markierten Text nochmals einfügen. Klipper funktioniert sowohl mit Strg+C als auch mit einfachem Markieren von Text (der oben schon erwähnten Funktion).

Sicherheitswarnung: alles, was mit der Maus markiert wird, landet auch in Klipper. Wenn du wissen willst, was ich so mache auf meinem Computer, sieh mal in der Zwischenablage nach…
Lösung des Problems: ab und an mal die Zwischenablage löschen. Das kann man auch automatisch mit jedem Neustart machen lassen („Inhalt der Zwischenablage beim Verlassen speichern“ deaktivieren).

3. Eingabefukus folgt Mauszeiger

Fast am meisten vermisse ich unter Windows und OS X, dass meine Eingabe nicht dort landet, wo sich der Mauszeiger gerade befindet. Der Grund: oft stelle ich ein anderes Fenster über jenes, auf dem die Eingabe erfolgen soll. So kann ich beispielsweise ein Bildfenster (z.B. Paint unter Windows) öffnen, und auf dem dahinter liegenden Textfenster (z.B. Notepad unter Windows) einen Text eintippen, den ich eben von jenem Bild abschreiben will. Liegt der Mauszeiger nun über dem Textfenster, so landen die Tastatureingaben auch auf jenem Fenster, während das Bildfenster jedoch im Vordergrund bleibt (und daher nicht vom Textfenster überdeckt wird).

Ebenso verhällt es sich mit dem Mausrad:

4. Mausradfokus folgt Mauszeiger

Wenn ich das Mausrad zum Scrollen verwende, dann doch wohl dort, wo sich der Mauszeiger gerade befindet. Unter Windows geht mir das dermaßen auf den Geist, dass man jedesmal zuerst Klicken muss, bis das Mausrad etwas bewegt. Vorallem im Explorer, wo man einmal auf der Verzeichnisbaumseite, dann aber auf der Detailansicht der Verzeichnisinhaltsseite scrollen möchte, nervt das sehr und hält auf.

5. Kürzel für Suchanfragen im Browser

Im Konqueror kann man zumindest seit KDE 3 einstellen, dass ein „gg:“ gefolgt von einem Suchbegriff eine Google-Suche auslöst. Diverse Suchdienste lassen sich hinzufügen.

Als Beispiel: „gb:“ habe ich mir als Gentoo Bugs eingerichtet. Suche ich nun einen bestimmten Fehlerbericht im Gentoo-Bugtracker, so reicht ein „gb:segfault konqueror“ und schon erscheint die entsprechende Seite.

Unter Windows finde ich mich manchmal bei dem Versuch wieder, beispielsweise „gg:Urlaubstipps Spanien“ eingeben zu wollen, was natürlich nicht zur Google-Suche nach Spanien-Urlaubstipps führt, sondern zu der Fehlermeldung, das „Protokoll gg:“ wäre „nicht bekannt.“


Diese 5 Funktionen sind unter KDE auf Linux Standard, müssen aber teilweise manuell konfiguriert werden. Das war bei KDE 2 bereits so, mit Klipper ist das seit KDE 3 so und auf KDE 4 funktionieren diese Funktionen natürlich ebenfalls. Nur unter KDE 1 waren die meisten dieser Funktionen noch nicht implementiert.

KDE gibt es auch für Windows. Das nennt sich KDE Windows Initiative und lässt sich mit dem Installer sehr einfach auch unter Windows installieren. Ob jedoch all diese Funktionionen auch unter Windows implementiert sind, weiß ich nicht, denn einige davon scheinen mir eher X11-spezifisch zu sein.

Es war auch einmal angedacht, KDE auf OS X zu portieren. Stattdessen gibt es derzeit nur die Möglichkeit, einzelne KDE-Anwendung nativ unter OS X zu nutzen.

6. Dock

Das Einzige, das offensichtlich aus der Mac-Welt stammt, ist das Dock.  Dabei handelt es sich um eine Kombination aus Programmstarter und Taskleiste/Fensterleiste. Das heißt, Programme, die noch nicht gestartet sind, können einfach über das Symbol gestartet werden (Programmstarter). Wenn diese jedoch bereits laufen und ein oder mehrere Fenster offen sind, so übernimmt dasselbe Symbol die Funktion eines Eintrags in einer Taskleiste bzw. Fensterleiste.

Seit KDE 4 gibt es Versuche, ein Dock, wie es von Mac OS X her bekannt ist, funktionell auch unter KDE zu implementieren. Mit KDE 4.8 wurde die „Symbol-Fensterleiste“ hinzugefügt und muss manuell aktiviert werden (als Plasma-Widget auf der Kontrollleiste). Auf Englisch heißt dieses Widget übrigens “Icon-Only Task Manager” und hieß vorher Icon Tasks.

Die Symbol-Fensterleiste funktioniert ganz gut, wenn auch nicht perfekt. Jedenfalls ist sie das einzige, was noch optimiert gehört – ansonsten ist KDE unter Linux wirklich das für meinen Geschmack beste Desktopsystem auf dem Planeten! Und wenn ich Desktop sage, dann meine ich auch Desktop: ich arbeite mit Tastatur und Maus vor einem Monitor. Auf Laptops mit Touchpad (die meist ohne mittlerer Maustaste daherkommen) bzw. ohne Maus sind einige der Funktionen nicht so gut nutzbar.

Und von Touchscreens rede ich erst gar nicht…

Bauvorschlag für eine Steam-Box

Was eine SteamBox ist, weiß hoffentlich jeder. Auf meiner Wohnzimmer-SteamBox soll Windows und/oder Linux laufen. Der Bauvorschlag basiert auf dem c’t-Artikel „Dampfmaschine“ aus c’t Heft 7/2013. Mehr dazu auf der Projektseite c’t Steam Box: Spielkonsole selbst bauen.


Damit sollte alles laufen. Zusammenbauen und loslegen.


Das Gehäuse ist das alternative Gehäuse aus dem c’t-Bauvorschlag. Es gefällt mir einfach besser als die erste Wahl des originalen Vorschlags. Nachteil: das Netzteil ist nicht debei.

Das Netzteil im c’t-Bauvorschlag ist ein be quiet! Pure Power L7, aktuell ist anscheinend das Pure Power L8.

Das Mainboard aus dem Bauvorschlag gibt es nicht mehr – zumindest nicht in Österreich. Darum ebenfalls eines von MSI, aber mit A88X-Chipsatz statt mit A75-Chipsatz. Kann hoffentlich nur besser werden. (Fingers crossed!)

Die CPU wurde von der c’t als Steam-CPU empfohlen.


Ich habe ein Windows 7 Home Premium, das ich damit verwenden werde. Der einzige Grund dafür ist, dass ich auf Steam ein paar Spiele habe, die leider noch nicht unter Linux laufen. Allerdings werde ich eine Dual-Boot-Installation mit Debian testing einrichten.

Der Plan ist, Steam im Big-Picture-Modus automatisch mit dem Betriebssystem zu starten.


Dieser Bauvorschlag ist derzeit noch ein Projekt. Die Finanzmittel stehen noch nicht zur Verfügung 😦