| DistroWatch Weekly
|DistroWatch Weekly, Issue 149, 1 May 2006
Welcome to this year's 18th issue of DistroWatch Weekly. This issue focuses on Linspire, or more precisely Freespire, a new distribution built with the same user-friendly aspects as its commercial partner, but without the price tag; besides revisiting the Freespire press release, we also bring you an interview with Kevin Carmony, the company's CEO. The news section then informs about all the recent BSD releases, brings news from the Slackware current changelog, and provides updates on the development of Kubuntu. Robert Storey is back with his "tips and tricks" column, advising on how to use GRUB with the XFS file system. Finally, it's our pleasure to announce that the April 2006 donation of US$260 goes to the Doxygen project. Happy reading!
Listen to the Podcast edition of this week's DistroWatch Weekly in ogg (8.84MB) or mp3 (11.7MB) format (courtesy of Shawn Milo).
Join us at irc.freenode.net #distrowatch
Miscellaneous news: Freespire announcement, BSD releases, Slackware kernel hints, Kubuntu updates
After several quiet months, Linspire stole the media spotlight last week with an announcement about Freespire, a new and free (as in beer) edition of Linspire built by a volunteer developer community. Additionally, the company also confirmed that the new distribution will optionally include support for many proprietary file formats and closed-source applications. Although this has resulted in some harsh criticism by Free Software advocates, the company insists that this is a legitimate way of increasing levels of Linux adoption among the less technical computer users. The first beta release of Freespire is scheduled for around August 2006.
While on the subject of Freespire, some DistroWatch readers might remember that a distribution of the same name was added to this site's database in August last year. This was a personal project by Andrew Betts, a Linspire user, who rebuilt the commercial distribution using free components only and released it as "proof of concept". It was subsequently renamed to Squiggle OS and later abandoned. The new Freespire is a different project, fully sponsored by Linspire; however, it is interesting to note that Betts now serves on the Freespire leadership board. As always, we will keep an eye on this interesting development and will add Freespire to the DistroWatch database as soon as the first development build is released for testing.
* * * * *
It seems that many BSD projects find this time of the year highly productive and a number of new releases have been made available in the last few days. A brand new version of OpenBSD is out today, while the first stable release of PC-BSD, an interesting, user-friendly BSD variant based on FreeBSD 6.x was released on Saturday. In the meanwhile, two FreeBSD-based live CDs have also been hard at work in recent weeks - the FreeSBIE project has released several development builds of their live CD for both i386 and AMD64 architectures, while the developers of Frenzy, an excellent FreeBSD-based live CD with a collection of networking, rescue and penetration testing tools, have finally released the first beta of Frenzy 1.0 (see the Upcoming Releases section for more details about this interesting live CD developed in Ukraine).
The first beta of the FreeBSD-based Frenzy live CD was made available on Sunday
(full image size: 881kB, resolution: 1280x1024 pixels)
* * * * *
A large number of updates, comments and hints in Slackware's "current" changelog during the past week has turned the file into an interesting read. Besides package upgrades to Thunderbird, ALSA, Mozilla, udev and others, Patrick Volkerding has hinted that the upcoming Slackware Linux 11.0 will finally default to kernel 2.6: "I think 2.6.16.x, being the first kernel series in the 2.6 series that has been promised some long-lived support, will be the 2.6 kernel you'll see in the next Slackware release. If/when 2.6.17 (or 18, etc.) come out, don't expect to see me chasing after it immediately. I'm looking for a kernel that can be counted on for stability -- not the bleeding edge. Of course, once 2.6.16.x is considered tested enough to leave /testing (and it does seem close), perhaps a newer kernel might take its place here just for fun." For more information please see the latest entries in the Slackware "current" changelog.
* * * * *
Following a recent protest by some of the of Kubuntu development team members, Mark Shuttleworth has published an open invitation to KDE and Kubuntu teams to join him at LinuxTag exhibition in Wiesbaden later this week: "This is an invitation for the Kubuntu and KDE community to join us at LinuxTag on 6 May in Wiesbaden near Frankfurt to chart the future course of Kubuntu. We will hold a series of meetings and presentations on the structure of Kubuntu and Ubuntu, the goals of the project, and an open discussion on how Kubuntu can come to represent the very best example of KDE in action." Sounds like a good idea to ensure that Kubuntu 6.06 gets the same attention as its older brother. For more details pleas see the full message as published on the ubuntu-announce mailing list.
|Interviews: Kevin Carmony, CEO of Linspire
Interview with Kevin Carmony, CEO of Linspire
DW: Kevin, thank you very much for your time. The Freespire announcement came as a surprise to many in the Linux community. Can you tell us what prompted the launch of a free edition of Linspire and why do you think this is the right time to announce it?
KC: I just hit my one-year anniversary as CEO for Linspire, but I have been with the company since the beginning, employee number one, and we're just hitting our 5th year. Wow! It's hard to believe I've been doing this for that long! We've had a fun and interesting history, starting back in the "Lindows" days, but we've had a lot of success and accomplished much. Today over 350 OEMs sell computers pre-installed with Linspire Linux and retailers such as Wal-Mart, Fry's, Micro Center, Target, and Sears are selling these computers.
We've learned a lot during the last five years, and two of the most important lessons were: 1) the open source and Linux community needs Linspire, and 2) Linspire needs the open source and Linux community. We've known the latter for a long time, and we started the Freespire project internally about two years ago. However, I think the timing is now right for us to do what we're trying to do with Freespire. Had we tried this a few years ago, I think a larger part of the open source community would have not understood why we were offering proprietary software as an option in the core distribution. Today, the vast majority not only understand this need, they welcome it. When I announced this at Desktop Linux Summit to hundreds of people, I didn't hear a single "Boo!" or "Hissss!" from anyone, but I saw a lot of heads nodding in agreement and heard a lot of applause.
DW: I guess you had discussed the idea with Michael Robertson (the founder of Lindows and Linspire). What was his reaction? Does he still take an active interest in Linspire or has he moved on to other projects?
KC: This has been a project of mine since before becoming CEO. Michael is certainly aware of what we're doing, and is very supportive. I meet with Michael each week and update him on what's going on, and of course, he always has ideas to share, but for the most part, Michael is very hands off when it comes to Linspire. This is for two reasons: 1) He completely trusts the team here at Linspire, as he knows we have some incredibly bright people here, and 2) he's just way too busy with all the other things he's working on. Michael is a visionary. He sees things years before they have economic viability. If he just did one thing, he'd go crazy, because his head is going a million miles per hour, and usually 5 years ahead of adoption curves. So, it suits Michael to have many different companies, each in a different stage of adoption.
Today he is involved with Linspire, SIPphone, AJAX13, MP3tunes, CompareSoft, and a couple of others. Because Linspire is the largest and oldest of all these companies, it requires less of his time and attention. Michael loves inventing and creating, but lets others deal with the execution and implementation over the years these things take to find adoption. He doesn't have the patience to watch paint dry, he'd rather leave that to others so he can keep painting. He's like Johnny Appleseed, running around planting the seeds for his vision, which hopefully years later sprout and bear fruit.
DW: How would you describe the relationship between Freespire and Linspire? Would you say it's similar to the relationship between Fedora and Red Hat Enterprise Linux (RHEL) in that Fedora is a freely available distribution that serves as a base for RHEL, or do you see it differently?
I actually just made a post about this on the Freespire forums here
. It's a rather lengthy answer, but others can take a look if they want the "long version." The short version is, yes, Freespire is not unlike Fedora in that it's free and designed to be a community project to help make Linspire better. Freespire is more for developers and Linux devotees, where as Linspire is more for consumers, but they will certainly share a great deal of code and make each other better. However, Freespire is very different from every other community Linux because of the option for legally licensed codecs, drivers and software, and the option of using CNR (Click And Run).
DW: One potential problem with Freespire is that the project could find it difficult to attract skilled developers. Firstly, software developers tend to code for more advanced computer users rather than the Linspire target market. Secondly, Linspire itself does not have the best reputation -- rightly or wrongly -- in the "geek" community. Any comments on this? What kinds of incentives, if any, do you intend to offer in order to attract skilled coders to work on Freespire?
KC: Just like Linspire didn't go after the traditional Linux users, Freespire isn't going after the traditional Linux developers. Linspire tries to draw away Windows users, and Freespire is trying to draw away Windows developers. For every Linux developer today, there are a hundred, if not a thousand, for Windows. I have a lot of friends who are Windows developers. When I ask them why they don't program for desktop Linux, they just look at me funny and say, "Why would I? No one runs Linux on the desktop, and there is no marketplace for my work even if I did." Freespire aims to change that. The Linux community sometimes gets so excited about what they're working on, they just assume everyone thinks it's great. That may be true for servers, where you have technical IT people using it, but it's far from true on the desktop.
It's simple math and market share. For every person running Linux on their desktop, there are 95 people running Windows. We had over 1,000 developers sign up for the Freespire developers list in the first 24 hours of our announcement at DLS. So no, I don't think it will be hard to find skilled developers, I'm going to be drawing from a pool of programmers that is 100 times greater than what Fedora and SUSE are pulling from. I've already had meetings with Windows developers who are very excited about CNR and the CNR Warehouse model, and now want to start coding for Linux. Of course, all developers are welcome, and I'm sure we'll get plenty from the current Linux community who just believe in the Freespire vision. They want to see desktop Linux succeed too, and many believe our approach is just what is needed.
DW: The Freespire FAQs talk about "frequent, on-going updates and release cycles". How frequently will new Freespire versions come out? How long do you expect a beta cycle to last? Will Freespire have a fixed release cycle?
KC: This will be similar to Linspire. Development work will always be going on, and new and interesting things will always be happening via the CNR Warehouse (using CNR or apt), but we will not have fixed released cycles because: 1) fixed cycles often force you to compromise on stability and quality, and 2) desktop users don't want to have to upgrade their system too often. Linspire has always believed in longer release cycles, but keeping everything current and fresh via CNR and/or apt-get. I like to think of an OS like a house. Who wants to bother with moving every year? It's a lot of work and hassle. Sure, it's fun and sometimes necessary as your family grows, etc., to move into a new home, but usually you just want to enjoy your house, buy some new furniture now and then, have friends over, have some parties, etc.
An OS should be used and enjoyed, NOT become a burden. CNR lets the OS stay current and interesting, without it needing to be completely changed every few months. The community will help decide some of this, but I think a stable build once a year is about as aggressive as it should get, with lots of activity going on in the CNR Warehouse. Of course, in the early days as we roll the first few releases out, they'll come more often than yearly, but in time, it's good to have things settle down some.
DW: Talking about "on-going updates" sounds great in theory, but we know from other project's experiences that it doesn't work well in practice - new updates sometimes introduce new bugs or worse, they can even break a system. Does Linspire have a panacea for this issue?
KC: Linspire has done it this way for years. We have a system down that works incredibly well. You see, the CNR Warehouse system can provide not only for different warehouses (pools) between releases, but multiple warehouses within a release. We have a few different CNR Warehouses for our developers, a couple for our QA testers, one for our employees here, one for our Insiders, and then one for the rest of the world. For example, let's say there is a new version of Firefox and you're running Freespire 1.0. In short order, we can put the new Firefox in the developers' pool for them to work on. It them moves to our QA testers, then we share it with our Insiders (Linspire has about 15,000 Insiders who help with testing), and then if all goes well, we roll it to the rest of the world. Freespire won't have Insiders like Linspire does, because anyone in the community can choose to point to the testing pools or the stable pools. The key is that by the time it hits the mainstream pool, it has been tested by thousands. Again, we've been doing this for years with Linspire, and we've never completely blown anyone's system up yet with some major bug.
DW: Do (will) Freespire have a freely accessible package repository where interested parties can monitor the development process?
DW: What version control system and bug reporting facility will Freespire deploy?
KC: That is being decided. There are two phases to the Freespire project launch: Phase 1, the Community Organization Phase and then Phase 2, the Technology Organization Phase. We are currently in the Community Organization Phase and will be until August. In this phase, it's not really about the technology, it's about the 1) the vision and mission for the project, 2) the organization, structure and leadership, 3) the community education and building, and 4) building community tools, such as the wiki, website, FAQ, mailing lists, etc.
The Technology phase starts in August. This was done very intentionally. I didn't want to open up the Freespire project and have a bunch of developers think this was just about code. It's not. I want the community, users and developers alike, to understand what the Vision for Freespire is. It makes no sense for a developer to get involved and contribute code, if they don't buy into the vision for this project. They will just become frustrated. It would be like being a world-class chef, volunteering at a new restaurant that just opened, only to later find out it serves Italian food, when you're a Thai chef!
I want the community to understand WHAT the house is going to look like before they start sawing and hammering. I know this could be a less interesting time for coders, but you can't build a good house on a shaky foundation. I want Freespire to endure and last, so I want a strong foundation of leadership, organization, community tools, all which takes some time, and THEN we can talk about the code in the OS.
DW: Your Freespire press release talks about the CNR (Click-N-Run) client to become an open source application. Under what license will it be released?
KC: This hasn't yet been decided. We know the code will be released and open, but will it be GPL, LGPL, or something else, we just haven't had time to decide that. For me personally, I really don't care. eBay isn't eBay because they have some top secret, proprietary way of doing things. It's an auction site. Anyone can look at what they do and copy it. Same can be said for Amazon. eBay and Amazon are successful because they simply do it better than the rest. I have never cared about the CNR being kept closed, but I do care that we always have the best Warehousing service anywhere for our intended audience.
DW: You mentioned in the latest Linspire Letter that you had converted to Linux shortly after becoming the CEO of Linspire. I assume you normally use Linspire, but have you tried a recent release of another distribution? If so, what do you think of Fedora 5, Ubuntu 6.06, SUSE 10.1? Have you tried any of the more user-friendly distributions, such as SimplyMEPIS or PCLinuxOS?
I have tried them all. I have installed pretty much every Linux distro and I install every new release from any that look interesting. Every time I do this, I get some good ideas of how others are doing things, and I also see how they are now doing things like we have been doing them. I'm a very competitive person, not because I want to make money (I've done that already in other businesses), but because I take great pride in anything I do. I don't want to have the "best" desktop Linux, because that is a subjective term. Best at what? Best for whom? The one area I do want to always be the best in, however, is ease of use for desktop Linux. We say Linspire is the world's easiest to use desktop Linux, and I truly believe it is. For example, if you visit the file types page
, every link you see there works, right out of the box, with Linspire and will with Freespire. With Ubuntu, you get to do this
. Fedora has its strengths, SUSE has its pluses, Ubuntu has things it's great at, but when it comes to ease of use for the desktop, that's our focus. Even with Freespire, which is geared for developers, it will still be the easiest to use, it just doesn't need to be as easy to use as Linspire, which is for consumers.
DW: Micorosoft's Steve Ballmer was recently quoted as saying that he did not allow his children to listen to music on an iPod or search on Google. Are members of your family allowed to use a competing product? Or have they all converted to Linspire?
KC: I love my iPod (and this is why Linspire has contributed a lot of good code to make iPods work with Linux), and I even have an X-box. (I have no problem with Microsoft competing with Sony in the game area, I think competition is good, besides, they lose money every time someone buys one. =) My oldest son sometimes uses Ubuntu and SUSE, because he's a developer, but I'm confident he'll move to Freespire soon. =) Most of his development is done under Windows. If there were more people using desktop Linux, and a obvious marketplace for his programming, he'd do more Linux work, as would many Windows developers.
DW: Can you tell us something about yourself? What jobs did you do before joining Linspire? Do you ever have time to relax or go away for a weekend? Do you have any hobbies?
I have been involved in a lot of different businesses, mostly software, but also the clothing industry, the music business (that's actually how I met Michael), and I am still involved in a chain of children's photography stores throughout the U.S. I have been blessed with financial success, which is good, because you don't make much money with Desktop Linux yet. =) Linspire is a passion and labor of love these days. If I wanted to make money, I'd be doing something else. If anyone wants, they can visit my web page
and learn way more than they would care to.
DW: Anything else you wish to say to the DistroWatch readers?
Sorry we didn't do Freespire sooner. We wanted to make sure we had a viable business model that could sustain our company before inflicting yet another community project on the world. We now know we have that sustainable model. We're not going anywhere. We will be around for a good long time. We have invested over US$35 million into open source software, with all of it having gone back to the community
. Because Linspire didn't go after the traditional Linux user, we have often been misunderstood. We've also made our share of mistakes, but what new company doesn't? We've gotten wiser and better with age. Not everyone will agree with the approach we're taking by offering proprietary software as an option in the Freespire core, but we believe it will get more people to look at open source.
Think of hybrid cars. They take half of the good (clean, non-oil burning electricity) and combine it with some bad (oil), but it has been received in a big way by car buyers, which brings them one stop closer to being open minded about other alternative fuels. Well, Freespire is the "hybrid" of open source Linux operating systems. If it can become cool and popular, not just for the tech crowd, but for the masses, it will bring millions one step closer to an open source world. I think that's pretty great.
Thanks for having me, and I look forward to seeing Freespire shoot up the charts there at DistroWatch come August. ;-)
DW: Kevin, thank you and good luck!
|Released Last Week
MCNLive is a Mandriva-based live CD developed by MandrivaClub in the Netherlands. A new version, name "Leuven", has been released: "I am glad to announce a new version of MCNLive, code name Leuven. Some highlights: 2.6.14 kernel with updated Unionfs and SquashFS. Desktop environment: KDE 3.5.2. Office suite: KOffice 1.5, Open Document Format, Firefox 126.96.36.199, music, video and image applications with all common codecs, Internet and networking applications for all your needs. All this on less than 350 MB." Visit the project's home page to read the full release announcement.
MCNLive "Leuven" - a nicely designed live CD based on Mandriva Linux
(full image size: 1,007kB, resolution: 1280x1024 pixels)
Wolvix 1.0.4 Media Edition
The Media edition of Wolvix 1.0.4 has been released: "The final release of Wolvix Media Edition 1.0.4 is ready. There are not many changes since RC1, mostly application updates and I've added a few games. This release marks the end of the 1.0.4 series and I want to thank everyone who has given me feedback, suggestions and bug reports. Updated: gmusicbrowser, XChat, Firefox, Thunderbird, AbiWord, GIMP, Comix. Added: Thunar (file manager), MP3Creator (console CD ripper), networkconfig (configuration tool from Zenwalk), Kye (puzzle game), Freeciv (strategy game), Bygfoot (football manager game)." Read the full release announcement for full details.
Foresight Linux 0.9.4 MR5
The fifth maintenance release of Foresight Linux 0.9.4 is now available: "This is the fifth in a series of maintenance releases for Foresight Linux 0.9.4. These maintenance releases help you stay current and also ensure that new downloads include the latest stuff. To update to MR5, 'sudo conary updateall', it’s that simple. There are new ISOs (both DVD and CD) and virtual machine images as well. Updates: Conary 1.0.13, Firefox 188.8.131.52, Beagle 0.2.5, Galago 0.5.0, AbiWord 2.4.4, Linux kernel 184.108.40.206. Added: Alacarte 0.9 (menu editor), GIMP 2.3.8, Inkscape 0.42, XaraLX 0.4r828. Tweaks: VTE patched to support 256 colors." Read the full release announcement for more details.
Litrix Linux 6.4
The Litrix project, which develops a Linux live CD based on Gentoo Linux, has released Litrix Linux 6.4. This is a start of a new series based on Gentoo 2006 and developed during the past seven months. The new release includes support for MMX and 3DNow!, offering a major performance boost to multimedia applications. This is further enhanced by the addition of new KDE-based multimedia applications, such as amaroK with its excellent archive organising abilities and intuitive playlist features, and Kaffeine, which offers playback of both audio and video files. For more information please see the full release announcement (in Portuguese).
Litrix Linux is a Brazilian live CD based on Gentoo Linux
(full image size: 1,347kB, resolution: 1280x1024 pixels)
The first stable version of PC-BSD, a user-friendly operating system based on FreeBSD, has been released: "PC-BSD software is pleased to announce the immediate availability of PC-BSD 1.0 for x86 based processors. This first 'non-beta' release of PC-BSD ushers in a new era of stability and simplicity for desktop operating systems based on UNIX. Powered by the latest FreeBSD 6.0 and integrated with KDE 3.5.2, PC-BSD provides a solid server base, while being user-friendly enough to run as a primary desktop system. Due to the nature of the UNIX operating system, PC-BSD provides a high degree of protection from the every growing threat of malware, spyware and viruses that plague other popular operating systems today." See the complete press release and changelog for more information.
GParted LiveCD 0.2.4-3
Patrick Verner has announced the release of a new minor update to GParted LiveCD. From the changelog: "Updated to Linux kernel 220.127.116.11; updated to busybox 1.1.2, udev 091, gtkmm 2.8.5, glib 2.10.2, glibmm 2.10.1, pango 1.12.2, mdadm 1.12.0; added Xvesa 4.5.0, added xres2, depth2, and X server scripts to /bin for Xvesa; added better X config scripts in /etc/rc.d; added gvidm 0.8 to the Fluxbox menu; removed /etc/dialogrc to fall back to default colors; cleaned up boot dialog scripts to be more consistent; eject should now eject the proper CD-ROM drive."
We are pleased to announce the official release of OpenBSD 3.9. This is our 19th release on CD-ROM (and 18th via FTP). We remain proud of OpenBSD's record of eight years with only a single remote hole in the default install. As in our previous releases, 3.9 provides significant improvements, including new features, in nearly all areas of the system. Improved hardware support, including: some G5-based Apple Macintosh machines, including W^X support (currently restricted to 32-bit mode); many more audio drivers in the macppc port; support for many system sensors (temperature, voltage, fan speed)...." Read the full release announcement and visit the OpenBSD 3.9 page to learn more.
* * * * *
Development and unannounced releases
|Upcoming Releases and Announcements
Sergei Mozhaisky has announced a release schedule (in Russian) for the upcoming Frenzy 1.0, a FreeBSD-based live CD with a collection of security and networking tools. Beta testing is expected to start on 1 May and, if everything goes according to the plan, the final release should be available exactly a month later. Please visit the project's home page for more information.
* * * * *
Summary of expected upcoming releases
|Tips and Tricks: Using GRUB with XFS
Using GRUB with XFS (by Robert Storey)
Perhaps some of you will recall the following little excerpt from last week's DWW:
"Do you also hesitate every time you need to choose a journalled file system while installing a Linux distribution? If so, you might find it interesting to read the File system comparison on Debian 'etch', as published by Debian-Administration.org. In it, Hans Ivers provides a number of benchmarks to evaluate the performance on ext3, JFS, ReiserFS and XFS file systems. And the winner? Perhaps surprisingly, it's the less well-known and relatively rarely used XFS."
After reading this and following the link to the main story, I became convinced that XFS was the best thing since sliced pickles. As it turned out, the very next day I needed to install Ubuntu Breezy on a friend's machine, and it was a no-brainer to go with XFS.
I've installed Breezy quite a few times already, and I know that by default it chooses GRUB as its boot manager. So I was really surprised when I found that LILO, rather than GRUB, wound up on my friend's hard disk. Was I hallucinating? Had I been kidnapped by aliens, and they were now controlling my brain with radio waves? Perhaps, but even after I put on my tinfoil hat, LILO was still there.
So be it. Even if it is a hallucination, LILO isn't that bad. I could live with it, and my friend (who wouldn't know GRUB from an earthworm) was oblivious.
However, my tinfoil hat really took a beating the next day when I decided to install the all-new Ubuntu Dapper Beta on my laptop. The installation process was identical to Breezy, and there were no surprises... until the very end when this message popped up:
"No boot loader has been installed, either because you chose not to or because your specific architecture doesn't support a boot loader yet. You will need to boot manually with the /vmlinuz kernel on partition /dev/hda5 and root=/dev/hda5 passed as a kernel argument."
The thing is, I absolutely swear that I did not choose to not install the boot loader. I was never even asked that question during the installation. Even worse, since no boot loader was installed, I could not boot into Dapper even though it was installed.
I decided it was my duty as a beta-tester to file a bug report. This I duly did, and in short order received a response from one of the Ubuntu developers:
"Well, you won't be able to easily get the installer to install GRUB, because your /boot is on an XFS file system; we've had a very large number of reliability problems getting grub installed on XFS (see other bug reports), so it's disabled. The interesting question is why the installer didn't automatically fall back to LILO, as it's supposed to."
Aha! So that explains why Breezy installed LILO after I chose to use XFS as the file system. And as for the problem with Dapper, that was indeed a bug and I trust that the good folks on the Ubuntu development team will squash it before the final release hits the servers.
So let it be stated for the record: if you want to use XFS, you should install GRUB to a separate /boot partition formatted with a different file system (ext3 will work fine). How large should a /boot partition be? Surprisingly, bigger than I expected. I checked how much space is being used in my /boot directory and have discovered it's hefty 18MB. Your mileage may vary. On my Dapper installation there are two kernels and two bloated initrd files (probably because I updated the kernel once and didn't delete the old files). Anyway, I would guess that 30MB would be a safe size for a /boot partition. If you keep installing kernels, be sure you clean out the cruft, otherwise your /boot partition will fill to the bursting point. As it is, too many sedentary geeks are plagued with bulging waistlines - last thing we need are bulging /boot partitions as well.
April 2006 donation: Doxygen receives US$260|
We are pleased to announce that, based on readers' requests, the DistroWatch April 2006 donation of US$260.00 goes to Doxygen. What is Doxygen? "Doxygen is a documentation system for C++, C, Java, Objective-C, Python, IDL (Corba and Microsoft flavours) and to some extent PHP, C#, and D." Written by Dimitri van Heesch, Doxygen is widely used by many open source software developers for generating documentation for their software.
As always, our monthly donations programme is a joint initiative between DistroWatch, which allocates 10% of its advertising revenue, and two online shops selling low-cost CDs and DVDs with Linux, BSD and other open source software - LinuxISO.co.uk and LinuxCD.org, each of which contributed US$50 towards this month's donation. Both stores have an excellent selection and latest releases at very reasonable prices. Next time you need to order your favourite Linux or BSD CDs, get them from LinuxCD.org or, if you are in the United Kingdom, from LinuxISO.co.uk.
This is the PayPal receipt for the donations to Doxygen:
This email confirms that you have paid dimitri at stack.nl $260.00 USD using PayPal.
Transaction ID: 9UD16010FE2883734
Total: $260.00 USD
Item/Product Name: Doxygen
Message: This is a donation by DistroWatch.com as part of our programme to support open source software projects. Keep up the good work!
Here is the list of projects that received a DistroWatch donation since the launch of the programme:
Since the launch of the DistroWatch Donations Programme in March 2004, we have donated a total of US$7,800 to various open source software projects.
* * * * *
DistroWatch database summary
That's all for today. The next issue of DistroWatch Weekly will be published on Monday, 8 May 2006. See you then :-)
If you've enjoyed this week's issue of DistroWatch Weekly, please consider sending us a tip.
(Tips this week: 0, value: US$0.00)
|Linux Foundation Training
|• Issue 793 (2018-12-10): openSUSE Tumbleweed, finding non-free packages, Debian migrates to usrmerge, Hyperbola gets FSF approval|
|• Issue 792 (2018-1203): GhostBSD 18.10, when to use swap space, DragonFly BSD's wireless support, Fedora planning to pause development schedule|
|• Issue 791 (2018-11-26): Haiku R1 Beta1, default passwords on live media, Slax and Kodachi update their media, dual booting DragonFly BSD on EFI|
|• Issue 790 (2018-11-19): NetBSD 8.0, Bash tips and short-cuts, Fedora's networking benchmarked with FreeBSD, Ubuntu 18.04 to get ten years of support|
|• Issue 789 (2018-11-12): Fedora 29 Workstation and Silverblue, Haiku recovering from server outage, Fedora turns 15, Debian publishes updated media|
|• Issue 788 (2018-11-05): Clu Linux Live 6.0, examining RAM consumpion, finding support for older CPUs, more Steam support for running Windows games on Linux, update from Solus team|
|• Issue 787 (2018-10-29): Lubuntu 18.10, limiting application access to specific users, Haiku hardware compatibility list, IBM purchasing Red Hat|
|• Issue 786 (2018-10-22): elementary OS 5.0, why init keeps running, DragonFly BSD enables virtual machine memory resizing, KDE neon plans to drop older base|
|• Issue 785 (2018-10-15): Reborn OS 2018.09, Nitrux 1.0.15, swapping hard drives between computers, feren OS tries KDE spin, power savings coming to Linux|
|• Issue 784 (2018-10-08): Hamara 2.1, improving manual pages, UBports gets VoIP app, Fedora testing power saving feature|
|• Issue 783 (2018-10-01): Quirky 8.6, setting up dual booting with Ubuntu and FreeBSD, Lubuntu switching to LXQt, Mint works on performance improvements|
|• Issue 782 (2018-09-24): Bodhi Linux 5.0.0, Elive 3.0.0, Solus publishes ISO refresh, UBports invites feedback, Linux Torvalds plans temporary vacation|
|• Issue 781 (2018-09-17): Linux Mint 3 "Debian Edition", file systems for SSDs, MX makes installing Flatpaks easier, Arch team answers questions, Mageia reaches EOL|
|• Issue 780 (2018-09-10): Netrunner 2018.08 Rolling, Fedora improves language support, how to customize Kali Linux, finding the right video drivers|
|• Issue 779 (2018-09-03): Redcore 1806, keeping ISO downloads safe from tampering, Lubuntu makes Calamares more flexible, Ubuntu improves GNOME performance|
|• Issue 778 (2018-08-27): GuixSD 0.15.0, ReactOS 0.4.9, Steam supports Windows games on Linux, Haiku plans for beta, merging disk partitions|
|• Issue 777 (2018-08-20): YunoHost 18.104.22.168, limiting process resource usage, converting file systems on Fedora, Debian turns 25, Lubuntu migrating to Wayland|
|• Issue 776 (2018-08-13): NomadBSD 1.1, Maximum storage limits on Linux, openSUSE extends life for 42.3, updates to the Librem 5 phone interface|
|• Issue 775 (2018-08-06): Secure-K OS 18.5, Linux is about choice, Korora tests community spin, elementary OS hires developer, ReactOS boots on Btrfs|
|• Issue 774 (2018-07-30): Ubuntu MATE & Ubuntu Budgie 18.04, upgrading software from source, Lubuntu shifts focus, NetBSD changes support policy|
|• Issue 773 (2018-07-23): Peppermint OS 9, types of security used by different projects, Mint reacts to bugs in core packages, Slackware turns 25|
|• Issue 772 (2018-07-16): Hyperbola GNU/Linux-libre 0.2.4, UBports running desktop applications, OpenBSD auto-joins wi-fi networks, boot environments and zedenv|
|• Issue 771 (2018-07-09): Linux Lite 4.0, checking CPUs for bugs, configuring GRUB, Mint upgrade instructions, SUSE acquired by EQT|
|• Issue 770 (2018-07-02): Linux Mint 19, Solus polishes desktop experience, MintBox Mini 2, changes to Fedora's installer|
|• Issue 769 (2018-06-25): BunsenLabs Helium, counting Ubuntu users, UBports upgrading to 16.04, Fedora CoreOS, FreeBSD turns 25|
|• Issue 768 (2018-06-18): Devuan 2.0.0, using pkgsrc to manage software, the NOVA filesystem, OpenBSD handles successful cron output|
|• Issue 767 (2018-06-11): Android-x86 7.1-r1, transferring files over OpenSSH with pipes, LFS with Debian package management, Haiku ports LibreOffice|
|• Issue 766 (2018-06-04): openSUSE 15, overview of file system links, Manjaro updates Pamac, ReactOS builds itself, Bodhi closes forums|
|• Issue 765 (2018-05-28): Pop!_OS 18.04, gathering system information, Haiku unifying ARM builds, Solus resumes control of Budgie|
|• Issue 764 (2018-05-21): DragonFly BSD 5.2.0, Tails works on persistent packages, Ubuntu plans new features, finding services affected by an update|
|• Issue 763 (2018-05-14): Fedora 28, Debian compatibility coming to Chrome OS, malware found in some Snaps, Debian's many flavours|
|• Issue 762 (2018-05-07): TrueOS 18.03, live upgrading Raspbian, Mint plans future releases, HardenedBSD to switch back to OpenSSL|
|• Issue 761 (2018-04-30): Ubuntu 18.04, accessing ZFS snapshots, UBports to run on Librem 5 phones, Slackware makes PulseAudio optional|
|• Issue 760 (2018-04-23): Chakra 2017.10, using systemd to hide files, Netrunner's ARM edition, Debian 10 roadmap, Microsoft develops Linux-based OS|
|• Issue 759 (2018-04-16): Neptune 5.0, building containers with Red Hat, antiX introduces Sid edition, fixing filenames on the command line|
|• Issue 758 (2018-04-09): Sortix 1.0, openSUSE's Transactional Updates, Fedora phasing out Python 2, locating portable packages|
|• Issue 757 (2018-04-02): Gatter Linux 0.8, the UNIX and Linux System Administration Handbook, Red Hat turns 25, super long term support kernels|
|• Issue 756 (2018-03-26): NuTyX 10.0, Neptune supplies Debian users with Plasma 5.12, SolydXK on a Raspberry Pi, SysV init development|
|• Issue 755 (2018-03-19): Learning with ArchMerge and Linux Academy, Librem 5 runs Plasma Mobile, Cinnamon gets performance boost|
|• Issue 754 (2018-03-12): Reviewing Sabayon and Antergos, the growing Linux kernel, BSDs getting CPU bug fixes, Manjaro builds for ARM devices|
|• Issue 753 (2018-03-05): Enso OS 0.2, KDE Plasma 5.12 features, MX Linux prepares new features, interview with MidnightBSD's founder|
|• Issue 752 (2018-02-26): OviOS 2.31, performing off-line upgrades, elementary OS's new installer, UBports gets test devices, Redcore team improves security|
|• Issue 751 (2018-02-19): DietPi 6.1, testing KDE's Plasma Mobile, Nitrux packages AppImage in default install, Solus experiments with Wayland|
|• Issue 750 (2018-02-12): Solus 3, getting Deb packages upstream to Debian, NetBSD security update, elementary OS explores AppCentre changes|
|• Issue 749 (2018-02-05): Freespire 3 and Linspire 7.0, misunderstandings about Wayland, Xorg and Mir, Korora slows release schedule, Red Hat purchases CoreOS|
|• Issue 748 (2018-01-29): siduction 2018.1.0, SolydXK 32-bit editions, building an Ubuntu robot, desktop-friendly Debian options|
|• Issue 747 (2018-01-22): Ubuntu MATE 17.10, recovering open files, creating a new distribution, KDE focusing on Wayland features|
|• Issue 746 (2018-01-15): deepin 15.5, openSUSE's YaST improvements, new Ubuntu 17.10 media, details on Spectre and Meltdown bugs|
|• Issue 745 (2018-01-08): GhostBSD 11.1, Linspire and Freespire return, wide-spread CPU bugs patched, adding AppImage launchers to the application menu|
|• Issue 744 (2018-01-01): MX Linux 17, Ubuntu pulls media over BIOS bug, PureOS gets endorsed by the FSF, openSUSE plays with kernel boot splash screens|
|• Issue 743 (2017-12-18): Daphile 17.09, tools for rescuing files, Fedora Modular Server delayed, Sparky adds ARM support, Slax to better support wireless networking|
|• Issue 742 (2017-12-11): heads 0.3.1, improvements coming to Tails, Void tutorials, Ubuntu phasing out Python 2, manipulating images from the command line|
|• Full list of all issues|
|Random Distribution |
Linux Media Lab Distribution
Linux Media Lab Distribution was a Japanese Linux distribution based on Red Hat.
|Tips, Tricks, Myths and Q&As |
|Questions and answers: Transferring email to Linux|
|Questions and answers: Office licenses|
|Questions and answers: Keeping up with the vulnerabilities|
|Tips and tricks: Play nicely, drop secure shell sessions cleanly, check init's name|
|Tips and tricks: Basename, for loop, dirname, aliases, bash history, xsel clipboard|
|Questions and answers: Setting up home server, experiment with rolling releases|
|Tips and tricks: OpenSSH, pipes and file transfers|
|Tips and tricks: Play nicely, drop secure shell sessions cleanly, check init's name|
|Tips and tricks: Package compression compared|
|Tips and tricks: Transitioning from PC-BSD to TrueOS|
|More Tips & Tricks and Questions & Answers|