Language Selection

English French German Italian Portuguese Spanish

Ultima Linux: Ultimate Disappointment

Filed under
Reviews

I'm not sure this can be classified as much a review as a rant. This is why I'll file this as a blog instead of a news/review. I love slackware, I've stated that numerous times. In fact one of my first reviews here at Tuxmachines was on slackware. So why is it that more times than not when someone goes to try and "improve" upon slackware, it just makes a mess. Oh they have their communities that'll come down on me for stating the truth and even accuse me of hurting linux and open source advocacy. They go as far to declare me an incompetent and my hardware garbage. So, when I state that I found ultimalinux the ultimate disappointment, it's with saddness in my heart and a bit of trepidation. But I have to tell the truth.

Sure perhaps it's my hardware. Perhaps it was my kernel appends. But my hardware does rather well on most distributions and I always try many many configurations before I shrug my shoulders and say "oh well!"

It all started on September 4, 2005 when DistroWatch announced a new version of Ultimalinux ready for download. It took 2 days to get two 600 mb cds in, I kid you not. First the torrent tracker was shooting errors, then the ftp refused connections. Finally on the 5th the torrent started working, but it trickled in at anywhere from 0 to 30 kb/sec. It was quite frustrating. I told a friend, 'I guess they really don't want anyone to try their distro.'

However it finally finished on the evening of the 6th and I forgot the frustrations of obtaining the isos. I was open-minded upon boot of the 1st install cd and saw the familiar slackware installer and became rather optimistic when I saw all the extra great packages included and being installed. I was disappointed to see a 2.4.31 kernel as well as the packages being built for i486. Still I had hope.

It booted fine and I had no problems installing nvidia drivers. I'd seen during the install configuration where one has a choice of kde or kde+e (among others such as window maker and fluxbox). kde+e is KDE using the Enlightenment window manager. I thought for something different I'd default to that. It starts and appears to be doing fine until one starts opening and closing applications.

Konqueror was the first application to crash when I was trying to read the Ultima Linux website. I was looking to see if there was some package management system available. I was trying to see if there was a ssl package available as gaim couldn't connect to msn without it. Ho hum. I didn't find anything out about package management other than they say they have an update utility for security fixes called ulupdate.

Trying a couple different stock wallpapers (the usual KDE fare), just previewing mind you, the whole computer locks up.

Next boot I delete all of .kde and .enlightenment files and try with just a straight kde (3.4.2). While trying to get screenshots of OpenOffice.org 1.14, it froze up as soon as I clicked file > new > text document. A crash report window had time to open before the whole desktop just locks down. I was able to ctrl+alt+F2 and kill openoffice and get back to kde, but the window manager had crashed. The desktop was crippled and I restarted.

        

gxine locked up as well. First I was trying to see if it'd play a movie .bin and it just locked everything up, so the next reboot I try an .avi and it shot an error stating it couldn't allocate memory.

Throughout all these reboots I tried various boot options. The first time was a blank append line and other boots I tried things like apm=off, acpi=off, noapic, acpi=ht, and even mem=nopentium. I even tried using vesa graphics. It was no use. That distro was just not going to run.

So, I'll forego all the description, changelog, goals and philosophy. I'll leave it up to you to test.

OSDIR has a whole shi^H^Hcart load of screenshots, but it turns out they were provided by the developer. Is this an indication I know of which I speak?

I'd like to hear from my readers, but only in a positive sense. If you have ultimalinux running stably on your system, please contribute. But if anyone insults me, my intelligence, my grandmother, my machine, or my site, I'll just delete them and turn off committing.

UPDATE: Please see my updated review on a new version HERE.

Comment viewing options

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

Ultima does work for me

I just posted a mostly positive review of Ultima at OSDir's Distroreviews and I am very suprised our experiences were so different because Ultima has been rock-solid for me, just as I would expect Slackware system to be. In fact, just now I've run through the problems you mention: Konqueror did not crash on Ultima's home page, nor did it ever crash before. Open Office opened text documents with no trouble, and gxine played .avi movie with no suprises (I had no .bin files to test). I stuck to the defaults all the way through. On my desktop I run plain KDE or some other WM, but not KDE+e. I use nv drivers and no funny boot options other than append ide-scsi... and everything is fine here. I assure you I have no special reasons to promote Ultima and I am not lying either.

I also have to say that even if you're feeling frustrated, it is really unfair of you to slam a distro for the speed of their torrent - of all things, something out of their control! How fast the download is for you depends entirely on how many people are downloading and seeding, as I'm sure you know perfectly well. Ultima is clearly a small one-person, not-for-profit project and has to make do with whatever means of distribution it can afford, especially since its download and use are completely free. In any case, even in this regard our experiences differ because I used bittorrent and got both disks in under 6 hours, which I consider totally acceptable.

More in Tux Machines

PlayOnLinux For Easier Use Of Wine

PlayOnLinux is a free program that helps to install, run, and manage Windows software on Linux. It can also manage virtual C: drives (known as Wine prefixes), and download and install certain Windows libraries for getting some software to run on Wine properly. Creating different drives using different Wine versions is also possible. It is very handy because what runs well in one version may not run as well (if at all) on a newer version. There is PlayOnMac for macOS and PlayOnBSD for FreeBSD. Read
more

Linux Kernel: KPTI, SEV, CBS

  • Experimental KPTI Support For x86 32-bit Linux
    For the Kernel Page Table Isolation (KPTI) support currently within the Linux kernel for addressing the Meltdown CPU vulnerability it's currently limited to 64-bit on the x86 side, but for the unfortunate souls still running x86 32-bit operating systems, SUSE is working on such support.
  • AMD Secure Encrypted Virtualization Is Ready To Roll With Linux 4.16
    With the Linux 4.16 kernel cycle that is expected to begin immediately following the Linux 4.15 kernel debut on Sunday, AMD's Secure Encrypted Virtualization (SEV) technology supported by their new EPYC processors will be mainline. Going back to the end of 2016 have been Linux patches for Secure Encrypted Virtualization while with Linux 4.16 it will finally be part of the mainline kernel and supported with KVM (Kernel-based Virtual Machine) virtualization.
  • Deadline scheduler part 2 — details and usage
    Linux’s deadline scheduler is a global early deadline first scheduler for sporadic tasks with constrained deadlines. These terms were defined in the first part of this series. In this installment, the details of the Linux deadline scheduler and how it can be used will be examined. The deadline scheduler prioritizes the tasks according to the task’s job deadline: the earliest absolute deadline first. For a system with M processors, the M earliest deadline jobs will be selected to run on the M processors. The Linux deadline scheduler also implements the constant bandwidth server (CBS) algorithm, which is a resource-reservation protocol. CBS is used to guarantee that each task will receive its full run time during every period. At every activation of a task, the CBS replenishes the task’s run time. As the job runs, it consumes that time; if the task runs out, it will be throttled and descheduled. In this case, the task will be able to run only after the next replenishment at the beginning of the next period. Therefore, CBS is used to both guarantee each task’s CPU time based on its timing requirements and to prevent a misbehaving task from running for more than its run time and causing problems to other jobs.

Graphics: Mesa and AMDGPU

  • Mesa 17.3.3 Released With RADV & ANV Vulkan Driver Fixes
    Mesa 17.3.3 is now available as the latest point release for the Mesa 17.3 stable series. This bi-weekly point release to Mesa presents several RADV Vega/GFX9 fixes, various Intel ANV Vulkan driver fixes, a DRI3 fix, and random fixes to the OpenGL drivers like RadeonSI, Etnaviv, and even Swrast.
  • R600g "Soft" FP64 Shows Signs Of Life, Enabling Older GPUs To Have OpenGL 4 In 2018
    Most pre-GCN AMD graphics cards are still limited to OpenGL 3.3 support at this time due to not supporting FP64. Only the HD 5800/6900 series on R600g currently have real double-precision floating-point support working right now so at present they are on OpenGL 4.3 rather than 3.3, but those other generations may be catching up soon thanks to the "soft" FP64 code.
  • AMDGPU DC Gets More Raven Ridge Improvements, Audio Fixes
    Harry Wentland of AMD has sent out the latest batch of patches for the AMDGPU DC display code stack. Fortunately it lightens up the DRM driver by about six thousand lines thanks to removing some unused code. Besides gutting out a chunk of unused code, the DC code has a few audio fixes (no word yet on supporting newer audio formats with DC), fixes on driver unload, a "bunch" of continued Raven Ridge display updates, and various other code clean-ups.
  • AMDGPU Firmware Blobs Updated For Video Encode/Decode
    There are updated AMDGPU microcode/firmware files now available for recent Radeon GPUs. The updated firmware files now available via the main linux-firmware.git repository are centered around the video blocks: UVD video decoding, VCE video encode, and the new VCN video encode/decode block with Raven Ridge.

Games: DRAG, Geneshift, Balloonatics and More