Bryan Lunduke has a conversation with the leaders of Debian, Fedora and elementary OS: https://www.linuxjournal.com/content/state-desktop-linux-2019
Jordi Mallach details in a post I found via Google Plus why GNOME should remain the default desktop environment in Debian Jessie despite the usual switch to Xfce prompted by a desire to keep the ISO image at CD size.
There’s more. And it’s not just image size: Most use Debian’s netinstall image, which is always much smaller than a traditional data CD, and I think many if not most have access to a DVD drive or bypass optical media entirely for USB flash drives, so size doesn’t matter as much as it might.
The dust-up over GNOME 3’s controversial desktop is nothing new. Many will never like it. Cue irony: Windows 8, UI-wise, is as crazy as GNOME 3. They make the current Mac OS X desktop look positively old-school. That’s probably drawing more to OS X than it is the other direction (to GNOME and Windows 8).
Continue reading “Jordi Mallach: Why GNOME should be the default desktop environment in Debian Jessie — and why I agree”
Debian Developer Jon Dowland writes about switching from Linux to the Macintosh with OS X:
It appears I have switched for good. I’ve been meaning to write about this for some time, but I couldn’t quite get the words right. I doubted I could express my frustrations in a constructive, helpful way, even if I think that my experiences are useful and my discoveries valuable, perhaps I would put them across in a way that seemed inciteful rather than insightful. I wasn’t sure anyone cared. Certainly the GNOME community doesn’t seem interested in feedback.
It turns out that one person that doesn’t care is me: I didn’t realise just how broken the F/OSS desktop is. The straw that broke the camel’s back was the file manager replacing type-ahead find with a search but (to seemlessly switch metaphor) it turns out I’d been cut a thousand times already. I’m not just on the other side of the fence, I’m several fields away.
What can I say? With the Macintosh seemingly left for dead by Apple while the iPhone and iPad shovel in the revenue, Mac laptops have quietly become the platform of choice for developers everywhere.
Meanwhile, fragmentation in the Linux desktop space and what appears to be not just a lack of attention to detail but a willful rejection of it haven’t helped.
That said, I’m firmly in the “buy cheap, run Linux” camp, and I figure that the Microsoft-driven laptop price war to combat the Google Chromebook will provide a whole new class of sub-$250 machines on which to run the Linux distribution of your choice.
Since I don’t have $1,500+ for a laptop that won’t accept OS updates in a few years and generally don’t need to run the Adobe Creative Suite, I don’t have the opportunity/burden of trying to figure out how much free (as in freedom) software I could shoehorn into a Macintosh OS X environment.
But I can see how developers who aren’t Linux distro developers want to go for what’s “easy,” if not at all cheap.
While Ubuntu has in the past tried to court developers, the current direction in which they’re taking Unity is more about mobile compatibility than desktop productivity. And I don’t see any advantages for the average developer with GNOME Shell. Maybe GNOME Classic in an environment with a whole lot more configurability out of the box would work. I know that a more polished Xfce with a lot of the rough edges smoothed out could be popular.
But it’s the fragmentation …
I’d love for Fedora Workstation with its (I think) target audience of developers to fill this gap. But without a long-term support release, that won’t happen. Maybe a CentOS “developer desktop” spin could do better.
The elephant. In the room. It’s the same thing it always was: Preloads.
It’s going to require a major hardware vendor to commit to developer-centric laptops in a variety of price ranges with dedicated, in-house developers making sure the hardware is 100-percent supported in Linux and on the Linux distribution shipping with that hardware. I’m not saying it will never happen. I hope it does.
Until then, Apple is going to eat everybody’s lunch, including Microsoft’s. And desktop Linux’s, too.
I’m not saying that choice on the Linux desktop is bad. What I am saying is that a stable, functional, not-scary desktop with some heavy development attention and (dare I say it) substantial corporate support could turn the tide and bring not just developers but others (back) to Linux.
You can knock me over with a feather right this very moment: Mark Shuttleworth announced in his blog that Ubuntu will follow Debian in adopting systemd as its init system, even though Ubuntu itself coded the alternative Upstart:
Upstart has served Ubuntu extremely well – it gave us a great competitive advantage at a time when things became very dynamic in the kernel, it’s been very stable (it is after all the init used in both Ubuntu and RHEL 6 😉 and has set a high standard for Canonical-lead software quality of which I am proud.
Nevertheless, the decision is for systemd, and given that Ubuntu is quite centrally a member of the Debian family, that’s a decision we support. I will ask members of the Ubuntu community to help to implement this decision efficiently, bringing systemd into both Debian and Ubuntu safely and expeditiously.
I thought Ubuntu would fight to the end, but the SABDFL appears happy to offload init-system development to Lennart Poettering and company. A wise move, I think. Canonical’s resources are spread thinly enough that anything not directly related to getting their phone OS to market should be seen as ripe for offloading to other parts of the community.
I’m nowhere near qualified to opine on which init system is better, systemd, Upstart or even the old SysVinit, but it was clear in the debate coursing through the Debian mailing lists over the past month that the licensing of Upstart, which required contributors to sign a Canonical CLA (contributor licensing agreement) that allowed the company to make the code proprietary in the future, was a huge, huge nonstarter for many free software advocates.
So Upstart will ship in the Ubuntu 14.04 LTS release, and all derivatives like Kubuntu and Xubuntu, which are due in April. These long-term-support releases will be around for five years, so Upstart isn’t exactly dead yet, though it’s quite the lame duck.
These things happen in predictable patterns. Due to hardware issues I land in Fedora, and after six months it’s time for something else.
Not that Fedora 18 and now 19 haven’t been great, because they have.
But I’m wary of my AMD APU-based HP laptop’s trouble with suspend/resume and 3D acceleration. I had both working for a very short time during the AMD Catalyst 13.6 beta’s brief run.
But before that I had neither, and now I have decent 3D with AMD Catalyst but seemingly no hope of working suspend/resume with this AMD A4-4300M APU and its AMD Radeon HD 7420G graphics.
And I’m getting tired of new kernels coming into Fedora, some with Catalyst support, some without. And it’s past time that this AMD GPU (I think it’s the Trinity family) get better support from the kernel and the free and proprietary drivers.
What I’m saying is that if the hardware support I need is not going to come soon, I’d like something more stable while I’m waiting.
So I started auditioning new Linux distributions yesterday.
And when Debian 7.1 and 7.2 Live DVDs both allowed me to successfully suspend/resume my HP Pavilion g6-2210us laptop, I was firmly pulled back into the Debian camp. To my “home” distro.
Continue reading “After six or so months with Fedora, I’m looking for something new”
The “welcome” talk for DebConf 12 in Managua, Nicaragua.
Kilt-wearing Debian Developer (and former Debian Project Leader) Steve McIntyre talks about the state of EFI in Debian in this DebConf 2012 video.
I have done an EFI installation of Debian Wheezy, and while the installation was ultimately not successful, the EFI part went smoothly.
Given that pretty much all new PCs will ship not only with EFI but with Secure Boot, it’s vitally important that Linux handle EFI — and handle it well.
I’m not sure what the state of Secure Boot is in Debian at this point. I know that Secure Boot did not make it into Wheezy, though there’s some kind of solution where you enter your own key (a solution I know nothing about).
Let me just say that UEFI is both the present and the future, and any operating system that wants to stay relevant in the coming years needs to support it.
After more than two years of development, Debian Wheezy has been released.
I swapped an old hard drive into the HP Pavilion g6-2210us and gave a few Linux distros a spin today.
Why a separate drive? I’m not at all confident about a successful Linux-Windows 8 dual boot. For those keeping score, this laptop features an AMD A4-4300M APU processor with AMD Radeon HD 7420G graphics. The wireless NIC is by Atheros, and the wired NIC is a Realtek. (I’ll report later on specific NIC chips for wired and wireless Ethernet.)
First up was Debian Wheezy. I had to turn off Secure Boot because Debian doesn’t support it. That was no problem. You can toggle Secure Boot on this HP Pavilion g6, and you can also toggle UEFI and “legacy” BIOS mode. So really I’m only limited by what “works” with the hardware itself. Given my angst lately over video (no GNOME 3 due to shaky 3D acceleration support for this newish AMD chip), that’s cold comfort.
Debian seemed to install perfectly. Except that, early in the install, it wanted me to supply nonfree firmware for the wired networking port (a Realtek NIC) on removable media. I actually got the nonfree .deb package (all Wheezy firmware is here, unpacked it and put the required files on a USB flash drive (formatted as FAT), plugged it in and continued with the install. That didn’t work. Debian didn’t “see” the firmware.
Give what happened later (the laptop stalled during boot), this was strange because the system continued installing from the netboot image — using that very NIC to download all of the required files.
I knew I would have trouble with the 3D acceleration in GNOME 3 (and I later confirmed that the proprietary 3D driver for ATI/AMD does not work on this video card), but I was doing a test install and could always bring in Xfce later.
That wouldn’t matter.
I did the entire installation. But as I hinted above, Debian Wheezy wouldn’t reboot into the new system. It hung during configuration of the wired Ethernet port. I guess I can try again with install media that includes the nonfree firmware.
Later: I did look at the installation guide for Wheezy, where I saw that you need to leave the firmware in .deb package form. I also found install images with the firmware included.
Next up was Xubuntu.
The install went fine with Secure Boot turned on. But on reboot, I had to turn off Secure Boot to get the system up and running. It could have had something to do with the fully encrypted LVM option that I chose during the install. I’ll have to do an install without encrypted LVM to see if it makes a difference in Xubuntu’s ability to run with Secure Boot enabled.
Everything looked good once I was in the system. I installed a boatload of updates. I brought in Skype with the service’s own .deb package. I managed to get audio working in Skype. But upon reboot it was not to be. The audio left Skype, as did the configuration options I had to choose from to make it work in the first place. it might come back on the next boot. Who knows?
Unfortunately I need Skype to work at the moment. I never had such trouble in Debian Wheezy on my now-dead Lenovo G555. Until it died, that is.
Otherwise I was happy with audio. That was a major concern of mine. However, I was able to boost audio levels with the Pulse Audio Volume Control, and audio was every bit as good as it is in Windows 8.
Alas, the day’s experimenting had to come to an end. I swapped back in the Windows 8 hard drive, re-enabled Secure Boot and had a working Win 8 system once again. Yep, it’s as exciting as you thought it was.