Language Selection

English French German Italian Portuguese Spanish

Ubuntu 6.06 LTS Final Look

Filed under
Reviews
Ubuntu
-s

Ubuntu 6.06 LTS starting hitting the mirrors yesterday, May 31, and was officially announced in the wee hours of this morning, June 1. Considering the bad luck tuxmachines had with the release candidate's hard drive install, we felt it was only fair to give Ubuntu another chance. We downloaded the desktop version, checked the md5sum, burnt our cd and booted. This is what happened this time.

As described in our earlier report on the release candidate, the livecd boots up to a nice gnome desktop with a customized ubuntu wallpaper. No telltale ubuntu logo this time, but it's unmistakably ubuntu. As I perused the menus and check some version numbers I detected nothing new since our last report. The menus contain many popular applications for one's computer needs, sufficient enough to get one started.

        

Again we went through the hard drive install procedure. Actually we went through it twice, as the first time our test machine locked up pretty tight. This was a bit surprizing as we've had wonderful luck with our new test rig that our readers helped us purchased. Not to be deterred, and figuring it was our tester's fault as he was surfing the internet in firefox as the installer was running, we restarted the livecd and tried again. This time we went through the install, again as described in our earlier report. The user is asked a few elementary configuration questions, the most difficult might be the partitioning step if needed, and it installs in little time.

        

As expected (ie: learned) it installed grub with no confirmation and then asks if the user would like to continue using the livecd or reboot to their new system. I was anxious to test a few things, most importantly the boot process itself, so I clicked reboot.

Holding my breath as the beep from my system let me know it had posted, I waited to see if I could actually test Ubuntu. The bootloader paused momentarily and the boot process was off and running. Matching the livecd boot, it featured a goldish logo and progress bar with some verbose output towards the bottom of the screen. The boot of the livecd and the installed system take a bit longer than one might expect, but as long as no errors are encountered, I can live with that. None were and in time I was greeted by the gdm log in manager. I logged in and the now familiar gnome desktop, with accompanying startup sound, appeared. Whatever the previous problem, it didn't rear its head this time. We had achieve lift off.

Under the hood we find a kernel 2.6.15-23, Xorg 7.0, and gcc 4.0.3 is installable. Gnome is version 2.14.1.


One annoying feature of the default Ubuntu system is its mounting of all media it founds automagically. One of the things I did before the next reboot was delete all those extra entries from the /etc/fstab.

Another major annoyance I have with Ubuntu is its insistence upon changing my hardware clock to UTC. Despite my graphical adjustments and reconfigurations in the time and date applet, I've yet to stop this undesirable behavior. I'm gonna have to whip out the terminal on it next boot.

    

Beyond that, things went relatively well. The first thing that occurred after first boot was a notification that some updates were available and a suggestion to click on the "notification icon to show" them. I did as instructed and an update window appeared listing the available updates. Only an update to pcmcia was available and not needed on my desktop, but to test the feature I installed it anyway. That process concluded extremely quick without any negative issues. I could conclude 'well, that works.'

        

Next thing of interest was the software manager. Ubuntu features the wonderful apt-get front-end Synaptic. I can't recall when I've had trouble Synaptic, it always performs well under pressure. This time was no exception. Mark your selection(s), confirm dependencies if required, and click apply. Synaptic does the rest. It worked flawlessly as usual. 'Well, that works.'

        

My next wish was to get XGL going and take some really cool screenshots. I'd just posted a link to a great looking review/howto yesterday and I pointed my browser to it. I followed the author's instructions, but alas, it was not meant to be. Perhaps you'll have better luck. Some helpful tips I did still find useful there were the installation of the nvidia drivers and compiling tools. One can either apt-get or search in Synaptic for nvidia-kernel-common, nvidia-glx, and build-essential.

All in all, things went fairly well. Hardware detection was good and performance of the system was pretty good. The applications opened, functioned and closed without issue, but the system seemed a bit slow. It felt a little heavy. As I normally run KDE, I found that a bit surprizing. This condition improved after installing and starting X using the Nvidia 3d graphic drivers. The new installer is very much improved from the old Debian ascii text version found in the 5.0x series and much more "newbie" friendly. I don't like the lack of grub configuration and that needs to be addressed. Included apps might be a bit scarce, but there's plenty available through the package manager. In conclusion, Ubuntu 6.06 is a viable and worthy Linux desktop system.

Related Links:

I have come across the

I have come across the website occasionally and got very interested. Found many useful materials.Looked through the archive with pleasure. Thumbs up!

re: come across

Thank you so much for saying. I've been suffering a bit of "burn out" this fall/winter, but I hope to get back on the horse soon. We hope you continue to visit. Smile

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's leftovers

  • Clear Linux Has A Goal To Get 3x More Upstream Components In Their Distro
    For those concerned that running Clear Linux means less available packages/bundles than the likes of Debian, Arch Linux, and Fedora with their immense collection of packaged software, Clear has a goal this year of increasing their upstream components available on the distribution by three times. Intel Fellow Arjan van de Ven provided an update on their bundling state/changes for the distribution. In this update he shared that the Clear Linux team at Intel established a goal this year to have "three times more upstream components in the distro. That's a steep growth, and we want to do that with some basic direction and without reducing quality/etc. We have some folks figuring out what things are the most desired that we lack, so we can add those with most priority... but this is where again we more than welcome feedback."
  • The results from our past three Linux distro polls
    You might think this annual poll would be fairly similar from year to year, from what distros we list to how people answer, but the results are wildly different from year to year. (At the time of the creation of each poll, we pull the top 15 distributions according to DistroWatch over the past 12 months.) Last year, the total votes tallied in at 15,574! And the winner was PCLinuxOS with Ubuntu a close second. Another interesting point is that in 2018, there were 950 votes for "other" and 122 comments compared to this year with only 367 votes for "other" and 69 comments.
  • Fedora Strategy FAQ Part 3: What does this mean for Fedora releases?
    Fedora operating system releases are (largely) time-based activity where a new base operating system (kernel, libraries, compilers) is built and tested against our Editions for functionality. This provides a new source for solutions to be built on. The base operating systems may continue to be maintained on the current 13 month life cycle — or services that extend that period may be provided in the future. A solution is never obligated to build against all currently maintained bases.
  • How open data and tools can save lives during a disaster
    If you've lived through a major, natural disaster, you know that during the first few days you'll probably have to rely on a mental map, instead of using a smartphone as an extension of your brain. Where's the closest hospital with disaster care? What about shelters? Gas stations? And how many soft story buildings—with their propensity to collapse—will you have to zig-zag around to get there? Trying to answer these questions after moving back to earthquake-prone San Francisco is why I started the Resiliency Maps project. The idea is to store information about assets, resources, and hazards in a given geographical area in a map that you can download and print out. The project contributes to and is powered by OpenStreetMap (OSM), and the project's entire toolkit is open source, ensuring that the maps will be available to anyone who wants to use them.
  • Millions of websites threatened by highly critical code-execution bug in Drupal

    Drupal is the third most-widely used CMS behind WordPress and Joomla. With an estimated 3 percent to 4 percent of the world's billion-plus websites, that means Drupal runs tens of millions of sites. Critical flaws in any CMS are popular with hackers, because the vulnerabilities can be unleashed against large numbers of sites with a single, often-easy-to-write script.

  • Avoiding the coming IoT dystopia
    Bradley Kuhn works for the Software Freedom Conservancy (SFC) and part of what that organization does is to think about the problems that software freedom may encounter in the future. SFC worries about what will happen with the four freedoms as things change in the world. One of those changes is already upon us: the Internet of Things (IoT) has become quite popular, but it has many dangers, he said. Copyleft can help; his talk is meant to show how. It is still an open question in his mind whether the IoT is beneficial or not. But the "deep trouble" that we are in from IoT can be mitigated to some extent by copyleft licenses that are "regularly and fairly enforced". Copyleft is not the solution to all of the problems, all of the time—no idea, no matter how great, can be—but it can help with the dangers of IoT. That is what he hoped to convince attendees with his talk. A joke that he had seen at least three times at the conference (and certainly before that as well) is that the "S" in IoT stands for security. As everyone knows by now, the IoT is not about security. He pointed to some recent incidents, including IoT baby monitors that were compromised by attackers in order to verbally threaten the parents. This is "scary stuff", he said.

KDE: Slackware's Plasma5, KDE Community 'Riot' (Matrix), Kdenlive Call for Testers/Testing

  • [Slackware] Python3 update in -current results in rebuilt Plasma5 packages in ktown
    Pat decided to update the Python 3 to version 3.7.2. This update from 3.6 to 3.7 broke binary compatibility and a lot of packages needed to be rebuilt in -current. But you all saw the ChangeLog.txt entry of course. In my ‘ktown’ repository with Plasma5 packages, the same needed to happen. I have uploaded a set of recompiled packages already, so you can safely upgrade to the latest -current as long as you also upgrade to the latest ‘ktown’. Kudos to Pat for giving me advance warning so I could already start recompiling my own stuff before he uploaded his packages.
  • Alternatives to rioting
    The KDE Community has just announced the wider integration of Matrix instant messaging into its communications infrastructure. There are instructions on the KDE Community Wiki as well. So what’s the state of modern chat with KDE-FreeBSD? The web client works pretty well in Falkon, the default browser in a KDE Plasma session on FreeBSD. I don’t like leaving browsers open for long periods of time, so I looked at the available desktop clients. Porting Quaternion to FreeBSD was dead simple. No compile warnings, nothing, just an hour of doing some boilerplate-ish things, figuring out which Qt components are needed, and doing a bunch of test builds. So that client is now available from official FreeBSD ports. The GTK-based client Fractal was already ported, so there’s choices available for native-desktop applications over the browser or Electron experience.
  • Ready to test [Kdenlive]?
    If you followed Kdenlive’s activity these last years, you know that we dedicated all our energy into a major code refactoring. During this period, which is not the most exciting since our first goal was to simply restore all the stable version’s features, we were extremely lucky to see new people joining the core team, and investing a lot of time in the project. We are now considering to release the updated version in April, with KDE Applications 19.04. There are still a few rough edges and missing features (with many new ones added as well), but we think it now reached the point where it is possible to start working with it.

Preliminary Support Allows Linux KVM To Boot Xen HVM Guests

As one of the most interesting patch series sent over by an Oracle developer in quite a while at least on the virtualization front, a "request for comments" series was sent out on Wednesday that would enable the Linux Kernel-based Virtual Machine (KVM) to be able to boot Xen HVM guests. The 39 patches touching surprisingly just over three thousand lines of code allow for Linux's KVM to run unmodified Xen HVM images as well as development/testing of Xen guests and Xen para-virtualized drivers. This approach is different from other efforts in the past of tighter Xen+KVM integration. Read more

Servers: Kubernetes, SUSE Enterprise Storage and Microsoft/SAP

  • Kubernetes and the Cloud
    One of the questions I get asked quite often by people who are just starting or are simply not used to the “new” way things are done in IT is, “What is the cloud?” This, I think, is something you get many different answers to depending on who you ask. I like to think of it this way: The cloud is a grouping of resources (compute, storage, network) that are available to be used in a manner that makes them both highly available and scalable, either up or down, as needed. If I have an issue with a resource, I need to be able to replace that resource quickly — and this is where containers come in. They are lightweight, can be started quickly, and allow us to focus a container on a single job. Containers are also replaceable. If I have a DB container, for instance, there can’t be anything about it that makes it “special” so that when it is replaced, I do not lose operational capability.
  • iSCSI made easy with SUSE Enterprise Storage
    As your data needs continue to expand, it’s important to have a storage solution that’s both scalable and easy to manage. That’s particularly true when you’re managing common gateway resources like iSCSI that provide interfaces to storage pools built in Ceph. In this white paper, you’ll see how to use the SUSE Enterprise Storage openATTIC management console to create RADOS block devices (RBDs), pools and iSCSI interfaces for use with Linux, Windows and VMware systems.
  • Useful Resources for deploying SAP Workloads on SUSE in Azure [Ed: SUSE never truly quit being a slave of Microsoft. It's paid to remain a slave.]
    SAP applications are a crucial part of your customer’s digital transformation, but with SAP’s move to SAP S/4HANA, this can also present a challenge.