I submitted an application for the Fedora Summer of Open Hardware program. Haven't heard of that? Well, the Fedora folks had accumulated quite a bit of hardeware that they wanted to pass along to their community members. The hardware consisted of Aurdino, Raspberry Pi, and OLPC XO-1.75 units. Since I already have a Raspberry Pi that I bought myself... and I'm part of an OLPC Lending Library project that already has X0-1.0 and XO-1.5 units... I thought I'd go for an XO-1.75. I just got word today that I was approved and should get the laptop in a few weeks.
How does the XO-1.75 differ from previous models? Well the main difference is that it uses an ARM-based CPU rather than an Intel compatible. As a result the XO-1.75 supposedly has an improved battery life. All of the OLPC models so far use the same case so even though they may be vastly different inside, they all look the same on the outside. Another area where some of the models vary is in the keyboards they have. For example, the "HS" model stands for "high school" and it has a hard plastic keyboard like a traditional netbook rather than the rubber keyboard the non-HS models have. With the XO-1.75 it appears that the keyboard has changed again. While it is still a rubbery keyboard, it is mostly covered by a white, hard plastic cover that has holes that they keys stick out through. See the picture above. The laptop on the left is an XO-1.75 whereas the one on the right is a previous model with an HS keyboard.
If you didn't notice, today is Fedora 16 release day. Yeah! I've been using Fedora 16 for a while now preping my MontanaLinux remix. I made a 41 minute screencast that does two things: 1) Showcases the desktop environments available in Fedora as melded together in the MontanaLinux LiveDVD remix, and 2) Shows using KVM and virt-manager some.
Please pardon my voice and occasionally sniffing... an allergy is bugging me.
I setup a local mirror of the Fedora 16 development repo and got to work on the MontanaLinux LiveDVD remix. I ran into a few minor problems but the 32-bit build seems to be working great now.
Now that grub2 is used by default and grub is also in the repos, you actually have to add grup2 to your package list in the kickstart file or it isn't there when you try to do an install. Check.
When using the sample KDE kickstarts to add to, make sure and remove a few of the really big packages you don't want or your iso may grow over 2 GB at which point a few of the later build pieces may get cranky. After removing a lot of koffice translations, octave, and a few other things... my iso went from 2.1 GB to a more desirable 1.8 GB. Check.
Packages that I noticed that disappeared in Fedora 16 that I needed to remove from the package list: agave and xfprint. Check.
Since grub2 is used the process of rebranding grub has changed and I haven't figured that out yet. In fact, I still need to learn how to customize grub2 since it is no where near as obvious as the grub.conf used to be for grub1.
New stuff in Fedora 16 I still need to figure out
Anyone got grub2 all figured out yet? From what I understand there are a number of config files, and then a few for settings... and then some process to build from those the config file. Editing the config file directly is a no-no.
systemd is now in full force and legacy tools like chkconfig and ntsysv still work but to a lesser degree. The legacy tools only show a subset of services rather than all of them and I haven't figured out yet how to get a complete list of enabled services from systemd.
chkconfig httpd on" has become "
systemctl enable httpd.service". I'm just not sure what the systemd equivalent for "
chkconfig --list" is yet.
I still have to work on the 64-bit version but now that I have a functional 32-bit kickstart, that should be a piece of cake. I should have everything done before or by the official Fedora 16 release date which currently is set for 2011-11-08.
After looking around for a good introduction video to GNOME 3 I found this one. It is the best one I've found so far. Unfortunately it seems to only be available in flash format. Since Fedora 15 was one of the first distros to ship GNOME 3, it also covers Fedora some. Enjoy.
When I can, I try to participate in The Linux Link Tech Show when it is streaming LIVE... but even when I can't I often listen to the archived recordings. When I find something interesting I'll sometimes shoot Dann Washko an email with my thoughts. This morning I found myself writing a long email to him on a subject they covered on their June 15 episode (#407). I thought I'd post it here too.
It just so happens that several of TLLTS regulars had attended the Southeast Linuxfest the weekend prior and one of the conversations that Dann encountered there was about Canonical and Ubuntu. Dann spoke about the questions and opinions he heard raised and asked for everyone else's opinions but he didn't get a whole lot of feedback so I thought I'd provide him with some.
I'll admit yet again... I'm a big Red Hat and Fedora fan and I am biased... and I sometimes even serve as an apologist for them. While I think everything I say below is "fair and balanced"... I'm sure there are plenty of folks who disagree with me... and maybe one or two who agree... I do encourage feedback and comments from all sides. Read on at your own peril. :)
I've been keeping up with the virtualization related developments in the upcoming Fedora 15... but even if I weren't... Fedora offers a fedora-virt-preview repository that makes it easy to ckeck out the new stuff on Fedora 14.
Adding SPICE support to virt-manager is one of the upcoming features in Fedora 15 and as of 2011-03-28 it appears to be 100% done. I decided to use the fedora-virt-preview repository to check it out on my Fedora 14 workstation.
If you aren't familiar with virt-manager, it is the default GUI-based management application for virtual machines on Fedora and Red Hat Enterprise Linux... as well as a few other distros. virt-manager uses libvirt so it can support a number of virtual machine types but it is primarily used for KVM and Xen. I use it with KVM and KVM is the only virtualization product that offers SPICE support currently.
Then I deleted the existing VNC-based Graphics device and added a SPICE server. There are a number of different SPICE related options... what port to run it on... whether only the local machine can access it or if it is accessible remotely... use a password or not. There is a setting for SSL port but I'm not sure if that is actually operational... as I have not figured out the SSL stuff yet.
In virt-manager's preferences they have added a toggle for the default graphic device, either VNC or SPICE. Of course you can always delete one and add the other if the default isn't what you wanted.
I've been keeping up with Fedora 15 development. I installed a nightly build on my wife's dual-boot computer. I setup a Fedora 15 KVM virtual machine in preparation for my remix compose... which isn't quite there yet.
Anyway, I've noticed a few changes that came with some updates yesterday that I wanted to share:
- Fedora 15 appears to have incorporated all of the upstream GNOME 3 changes. The experience is exactly like that from the GNOME 3 live beta based on OpenSUSE
- They added a way in the GNOME 3 Shell System Settings to switch back to the GNOME 2 style desktop
- The GNOME 2 style desktop has been polished up some
- Fedora has added some additional artwork for non-GNOME desktops
The GNOME 2 style fallback desktop in GNOME 3 isn't exactly like the previous GNOME 2.32 desktop but it is fairly close. There are some elements from GNOME Shell present... such as the window styling and decorations (although you DO get the minimize and maximize buttons back). You can place application buttons on the top panel but none are there by default. There isn't a right-click desktop menu and the System Settings are from GNOME 3. Although the fallback desktop mode is a bit different than the older GNOME 2.32 desktop, the changes they have made should go a long way to make GNOME 2 diehards a little happier.
I've been using the GNOME 3 Shell more and I really like the changes they've made since the Fedora 15 Alpha release. These changes include larger icons in the Applications list and auto-managed virtual desktops. Some people call this a "dumbing down" of the interface but I prefer to call it streamlining. If you have a lot of previous GNOME 2.x experience you might perceive it to be counter-intuitive... but give it a little while. The streamlining really makes the new environment easy to learn and use. It is elegant, and as one blogger put it... "it looks expensive".
The GNOME developers have frozen the development for this development cycle and only bugfixes will be accepted. GNOME 3 Shell is finished and I like it. As a long-time KDE user, I'm not sure I'm ready to switch to GNOME 3 exclusively but really have enjoyed testing it out. I still expect there to be quite a bit of backlash against GNOME 3 Shell when it becomes the default desktop in Fedora 15 and probably also in the next major releases of other GNOME-based distros... but I think a lot of people are going to like it too. When you get a chance, give it a try.
I've been making a personal Fedora remix for a while now... since Fedora 10. While that might sound hard, thanks to Fedora's livecd-tools package and their livecd-creator script, it is really quite easy. I even made a screencast about it. I recently started making a remix of Scientific Linux 6.0 and wanted to share.
As you may recall, I prefer Fedora on my personal desktops but on servers I prefer Red Hat Enterprise Linux or a RHEL clone. There are actually a few clones to pick from and I've been using CentOS for a number of years. One thing I like about CentOS is that one of its goals is to stay as true to RHEL as possible by attempting to be 100% binary compatible with it, bugs and all. Unfortunately the CentOS developers have gotten somewhat backlogged with the onslaught of RHEL releases over the last few months (6.0, 5.6, and 4.9) and have taken a lot of criticism for release delays as well as falling behind on security updates in the process.
Trying out Clone #2
CentOS is definitely the most widely used RHEL clone with an estimated 6 million users who are eagerly awaiting the releases of CentOS 6.0 and 5.6. I can't really fault the CentOS developers for the delays because they are a completely volunteer organization and do development in their spare time.
Another popular RHEL clone is Scientific Linux (SL) which is put together by a small number (two or three?) of developers who are paid to work on it by Fermi National Accelerator Laboratory and the European Organization for Nuclear Research (CERN). SL's main goal is to produce an enterprise grade Linux distribution to meet the needs of scientists and people working with scientific data. SL strays a bit from the stock RHEL package set by adding some additional science related software including some changes to a few core packages to accommodate additional filesystems (reiserfs and AFS). SL is also known for its additional "tweak" packages that are designed to easily change some of the application default configurations.
The primary reason I had previously avoided SL was because I really did not want to deal with their changes and additions to RHEL. Now I'm giving it a try. What has changed? SL has a fairly public development process. For example, they came out with several alpha and beta releases of SL 6.0 before releasing the final version on March 3. They have adopted several of the Fedora developer tools and have given many public presentations about their development process.
While reading about SL I discovered that with their 6.0 release they have switched to Fedora's livecd-creator for producing their Live media. They have also released the kickstart files they used to build their live media and have quite a bit of documentation including a Create your own SL6 LiveCD page. While CentOS does offer live media, they don't use livecd-creator... and their live media does NOT offer an install option. I certainly hope that changes for CentOS 6.0.
Another thing I learned was that as a result of feedback from their userbase, the SL developers have decided to drop their "tweak" packages with 6.0... at least initially... although they may offer them as an option later for those that want them.
But wait... another long post from me... this time from an email I wrote today to the Fusion Linux mailing list... regarding how Flash 64-bit was broken in Fedora 14 and the arguments around who should fix it and why:
----- Original Message -----
> I am sorry to disagree, Linus does state that it is an hack, but he
> also suggests that it could/should be used, please see comment
> https://bugzilla.redhat.com/show_bug.cgi?id=638477#c38 :
> " The nicest alternative might be to just install that mymemcpy.so
> into the google chrome directory, and add the LD_PRELOAD to the wrapper shell
> script that google chrome already uses for the xdg binaries and the ffmpeg
> And obviously something similar should work for firefox. I just
> happen to use chrome, so I gave the directions (approximate as they were) for the
> thing I tried.
> No guarantees. It was a really quick hack. "
Oh don't worry about disagreeing with me. That is often good and I don't take it personally. :)
Yeah... but did you read comment from Linus later on?
- - - - -
Linus Torvalds 2011-02-21 18:19:22 EST Comment 199
Don't use my workaround: it was a stupid hack to test the bug, and show that "always copy upwards" works better than the crap that is in glibc now.
A much better workaround is likely to just implement memcpy() as memmove() (you can replace the inline asm by that in my preload example if you want to). Once memcpy() isn't small and trivial any more, that's just the right thing to do.
The fact that the glibc people don't do that, and that this hasn't been elevated despite clearly being a big usability problem (normal users SHOULD NOT HAVE TO google bugzillas and play with LD_PRELOAD to have a working system), is just sad.
Quite frankly, there is no reason for the current memcpy() mess. There is no _technical_ reason for it, and there is certainly no usability reason for it. Why the Fedora people don't just fix it, I don't understand. It's a shame and a
The fact that Adobe does something that isn't technically right is no excuse for having a sub-par crap memcpy() implementation.
And how does one raise the priority for a bug in bugzilla, or get it re-assigned to somebody who cares?
- - - - -
Please note that I disagree with Linus on everything but the first half of the first paragraph. :) So did the glibc developers and the Fedora developers. While users want it to work, it isn't Fedora's job to fix Adobe's broken program. Just because the problem didn't show up until after the glibc change doesn't mean the problem wasn't there. It was just luck that it worked to begin with. The glibc change just happened to expose the problem, not create it. Adobe needs to fix their program. Why can't they? They update Flash all the time so getting an update out to users really isn't a problem. They said they have a fix for the issue but it could be months before it gets deployed? Why?
Linus still ignores the direct evidence that the glibc change wasn't supposed to be faster except on lower end CPUs... and his testing is invalid. He blathers on and on... intimidating others. That is his way. That is actually his sense of humor... and he is obviously right much more often than when he is wrong... but this is one of the few times he is wrong. :)
Working around Adobe's problem can be done... but why should we do it? Oh, so it makes our distro look better... and users are happier. Yeah, but look at the crazy mess of a workaround it is. Is every distro supposed to engineer their own fix? How much work is that by how many people? I realize that many have not and may not run into this issue because they use older versions of glibc... but you get my point.
I think it is better to say... "we are aware of this bug and we are waiting for Adobe to fix it" and put the blame where it needs to go... rather than everyone working around Adobe's problem and then having to undo everything after they fix it.
What will be next? How many other closed source, commercial vendors will need to be accommodated in the future? This would set a very bad precedent... and that's why (in my opinion) Fedora didn't go for it... even with Linus breathing down their necks.
Fedora doesn't even ship with Flash (nor Google Chrome). They ship with alternative players and those are not affected. Lots of programs break when libraries change... and if they are in distro then they get fixed. If they are closed, commercial products... and they are slow to change... that just re-enforces our belief that FOSS is a better development model... because it is.
Ok, Fusion Linux DOES ship with Flash... and maybe you guys want to fix it. I haven't really contributed to Fusion Linux other than typing some emails here and there... so my opinion doesn't really matter. Do what you think is best... but I did want to provide some additional background and clarification.
I've been living with the warbly sound on some Flash videos for some time now... and I guess I've gotten used to it. Like I said previously, it just strengthens my desire to consume and promote the use of more non-flash content... like webm and ogv.
I don't want baby users who are pampered away from issues... I'd prefer to grow a community of contributors who can see problems (rather than having them hidden from them)... who work to solve problems rather than work around them. I guess that's part of the reason I'm a Fedora user. :)
> I am sorry that it did not fix for you, but as you can check from the
> bug report it fixed for many others. IMHO and until there is proper
> fix we should try to provide a positive user experience to as mush
> users as we can.
That report has been around for a long time and there have been a ton of updates since then. I don't know if that has a bearing on it not working for me or not. This fix I tried was the patch not the Linus fix. That fix was too much work for me.
> I don't think that the technical argumentation on who is right or
> wrong about the proper fix has any relevance for the end user, also
> I do not have have the technical expertise to debate with you, Linus
> or the glibc maintainers about the change.
> My suggestion was just about delivering a better experience to the
> users, getting broken sound on some flash contents is bad, if we
> could avoid it it would be great.
See my above comments.
I do appreciate you taking the time voice your opinions... because it shows you care... and I definitely want to encourage that! Please do not take anything I've written as a personal attack. I don't claim to be any more right than you... but it is obvious I disagree. Perhaps you'll be comforted in the knowledge that Linus agrees with you... I know I would be. :)
One other thing Linus was wrong on and that was on moving cgroup scheduling policy into the kernel... rather than keeping it in userspace... like the systemd developer explained was the better way. I don't recall what the final outcome of that was.
TYL, Scott Dowdle
Here's a LONG response I wrote to one of the comments to the previously mentioned blog posting (The GNOME war) that I wanted to share here as well.
Novell has already been sold. There is an investigation holding up the original transfer date but it is very likely to go through. There will be changes in Novell. If the company taking it over didn't think they could turn it around, they would not have bought it. Turning it around might end up being breaking up all of the pieces and selling some of them, keeping some of them, and killing some of them. Who knows what will happen? We'll just have to wait.
I'm not sure why you seem to be so unhappy with Red Hat with your "while Red Hat is imposing their rules" comment. What rules are they imposing? Is Red Hat in decline? I have no idea. I can tell you that their quarterly reports have been quite positive since they went public... which is pretty rare for any technology company much less a Linux company.
I see some people complaining about their stock prices and valuation... but what tech company on the stock market isn't overvalued? To me the stock market is fundamentally broken but that is a completely different topic so I'll leave it at that.
Oh wait, let me bring up one example. Apple. A while back I read some report where a leading PC magazine had one of their guys dig deeply into Microsoft's yearly earnings reports. The gist of the article was that the author believed he had discovered that Microsoft had moved around various things in their financial reporting to hide the fact that they had lost 1% of the desktop marketshare. Ok, let's think about that for a second. Who did they lose it to? Let's just say all of the 1% went to Apple. Last I checked, and I haven't checked in a while, Apple was very high up on the stock market. They are seen as the darlings of the tech industry... making the cool products... having the best usability... advertising on US TV (I don't know about the rest of the world) with a budget of tens of millions of US dollars. Sure they sold a ton of iPhones but the Android army has come into being and has hit them hard. The iPad has done quite well (15 million sold(?) with the iPad 2 coming out today)... and no one else in the market seems to have an inroad to significant marketshare in the "tablet" arena (which I don't even believe is a legitimate genre although Miguel de Icaza definitely disagrees with me buying his third iPad today). How are they doing with the desktop OS marketshare? They are supposedly selling lots of laptops... but in one of their best years in recent history... they have managed to pull 1% of the marketshare away from Microsoft? 1%? That's all? Yet they are a darling of the stock market... and the envy of the GNOME and Canonical developers.
Of course if you listen to others, the desktop is dead and there is no reason to care about it anymore... and FOSS developers should start working on cloud apps before it is too late... and some say it is already too late.
Wow, I'm getting off on some tangents. In any event, you can see that the tech industry is a tangled web of twisty little passages... all different. :) (Who knows where geeky reference comes from?)
Also, I'm not sure where people keep coming up with this figure that Ubuntu has "60% of the Linux desktop marketshare". I have no idea if it does or not... but determining that is near to, if not completely, impossible. For the sake of argument, let's say it's true. Have they been able to turn a profit yet? If not, why not? How much of the marketshare will they have to gain BEFORE they can turn a profit? Stupid question. Having marketshare for something that is free doesn't make you successful. In fact, it can be a dead albatrose hanging around a company's neck. That is the situation Red Hat found itself in before it decided to go the enterprise Linux route.
Some say it is because Mr. Shuttleworth, who you obviously see as another legendary hero like many see Steve Jobs, has made it impossible for Canonical to make a profit because he has tried to focus the company in too many directions... meaning that no particular direction gets enough focus to be successful. Others might say that doing that is like throwing many things at the wall and seeing which ones stick. He keeps throwing things, and so far nothing has really stuck... nothing that will make the company profitable. I'm not saying that Canonical won't figure it out. I certainly hope they do... because the Linux market needs more FINANCIAL successes... not less.
If Red Hat and Novell falter (which I don't think is going to happen)... while it might shift some customers over to other companies... it will make Linux seem like a less stable technology platform to pay for and invest in. Red Hat has shown that it can be done by having positive financial statements quarter after quarter... all while releasing everything they do as FOSS... and you want them to be taken down? You do know how much they contribute to the Linux kernel, gcc, GNOME, x.org, etc... right?
I do know that if Novell fails or Red Hat falters... any people they have to shed will most likely be snapped up by other companies. Linux can survive the loss of Linus and Linux can survive the loss of one or more of its major distros... but we'd like to do more than survive.
If you ignore everything else I write, please realize that there is plenty of room for more than one or two successful Linux companies. We all do better, when we all do better. :)
Just because you see Arch and Ubuntu and not much else used in your neck of the woods doesn't mean that is how it is everywhere else. Red Hat and Novell are doing well in the "enterprise" space and CentOS is doing quite well too. Debian also.
I think your supposition that if someone uses distro X in high school and/or college they will refuse to work for a company that doesn't use distro X... is silly. Or maybe you were saying that the company they work for will be forced (somehow) to switch to distro X because that's what their new employee(s) use. Riiiiiiiiight. That might be true for major OSes... but not from one flavor of Linux to another. Distros are 95% the same software and switching between them is not so difficult.
Thanks for the discussion, Scott Dowdle