Language Selection

English French German Italian Portuguese Spanish

Wolvix: Leader of the Pack

Filed under
Linux
Reviews
-s

A new distribution is in our midst and it clearly deserves some attention. Wolvix is a Linux distribution livecd based on Slax and is available as a 456M download. The site says, "It's a desktop oriented distribution made to fit the needs from regular to advanced desktop users." When the head developer wrote and asked me to take a look, I said, "sure." But I was not expecting quite what I found.

To quote the site, "With Wolvix you can: Surf the internet, read email, chat with friends over ICQ, MSN, Jabber, Yahoo, IRC, etc. Watch movies in various file formats including DVD. Listen to your favorite music. Create graphics and webpages. Hook up to Windows networks with Samba. Transfer files over FTP or BitTorrent. And the best of all. It's free.

Along with the applications you'll get some of the best free Linux games. (No 3D gfx card required) - All work and no play makes Jack a dull boy. =)"

Indeed I found Wolvix 1.0.2 to be this and much more. It is based on the 143MB Slax, so this means it is derived from Slackware. Using Linux Live boot scripts, all hardware is detected and appropriate modules loaded. The boot is a fast text boot and being based on Slax, it comes with several nice boot options. Some include: gui, which tells it to boot straight into X without stopping at a console for login, nohd, that tells it not to mount all your partitions automagically, and copy2ram. Copy2ram is a nice feature that loads the entire cd into ramdisk for faster operation. The options screen states that it requires 256 MB of ram to work, but this is the only option or feature found in Wolvix that did not work for me. At 512 MB ram, I still ran out of memory when trying that boot option. However, I found in the default mode as a livecd, the system functioned quite well and responsively. The desktops and the applications performed fast and was stable as well. The nohd option is worth the author's weight in gold. And the gui option is rather nice as well.

        

When either using the gui option or booting to the console for logging in, one has only a root account to use. I suppose in a livecd environment and as long as coupled with the nohd option, it's not entirely a bad thing. The only application that had a problem with it was Xchat that warned one shouldn't hook up to irc network as root.

One of the options at the log in screen is xconf. This is as it looks, a configuration for X. One can set up glx through this option if desired. Left alone, X uses vesa as default and I always find that a wonderfully sensible choice for developers. As such, there were no problems encountered when starting the x server and gui. Even in vesa mode, the 2D games functioned quite well. In fact I wasted almost a 1/2 hour playing Lbreakout.

        

Other log in options include: startx = which starts the default Xfce4 (4.2.2) window manager; flux, which starts the fluxbox (0.9.13) window manager; and ice, which starts the icewm (1.2.23pre1) window manager. All the light and fast desktop choices are unified by using the same wallpaper, very similar looks as well as a very consistant menu. The wallpaper is this tasteful background in a grayish hue embossed with a paw print. I'm guessing that is a wolf paw print. Coupled with that is tormso in xfce4 and what looks like a calender adesklet across the board. Fluxbox comes with a nice monitoring application setup as well in the form of the dockapps wmcpuload, wmmemmon, wmclockmon, wmix, and fbpager. The menu is almost identical across the board. All desktops feature a quicklaunch to a transparent aterm - another feature adding consistency as well as similar windec for each as possible. These few little added details give the whole system a more polished and planned feel. It adds to the user experience in such a manner as to promote comfort and ease of use.

        

Aside from the window manager choice, comes a whole plethora of software for productivity, entertainment, and internet. Not only does Wolvix come with some nice gui applications, it also includes a whole suite of useful commandline/console applications as well as menu items to start them. Some of these include mp3blaster, mc, centericq, and mutt. Neato!

    

Well, if console apps aren't your thing, have no fear. Wolvix comes with a whole stack of wonderful and useful graphical applications to complete your given task. It features abiword for word processing, gnumeric for spread sheets, and the firefox/thunderbird team. It has a real nice selection of games as well as several applications for image viewing and manipulation. One of them being blender, and of course another, the gimp.

        

        

Wolvix also includes applications to make your internet experience complete as well as mucho multimedia enjoyment. It comes with gaim, XChat, Audacity, Beep, mplayer and xine. ...really just way to much to list.

        

Speaking of mplayer, it comes all nicely equipped with all the libs and codecs to play just about any media file you throw at it.

        

Another wonderful feature of Wolvix is the inclusion of gslapt (slapt-get). This is a package manager for the slackware distribution in the same strain as synaptic. It comes with repository already set up to download and install from a slackware 10.1 mirror. Although I'm not sure of the uses of it in a livecd environment, perhaps this is an indication of a harddrive installer in the near future. I didn't see one as of yet, nor any mention of it on the Wolvix site.

        

Wolvix is in its third release, the original 1.0 only released August 31. Wolvix 1.0.2 was announced yesterday, September 20. The changelog can be viewed HERE, and many version numbers are reported there. Wolvix comes on a linux-2.6.12-2 kernel and with Xorg 6.8.2.

In summation, Wolvix is all that it claims and more. I found the entire experience quite enjoyable and easy. Despite its small size, it's complete with wonderful assortment of included applications and utilities. It's fast and stable! I didn't experience one lockup, freeze, or crash. The unified desktop experience gives it polished look and feel. I was highly impressed with this offering and can recommend it to anyone. In fact, I suggest you download and try it out for yourself today. It is definitely at least a 9 out of 10!

Screenshots here.

Distrowatch has added this distribution to is lineup as of this morning.


Thank you very much for the nice review.

I had some initial problems with the new release, as I found an issue
with Gaim and MSN. (SSL problem) The issue has been fixed and I've
uploaded the new ISO.
As I was uploading the fix my distro appeared on DistroWatch and I got
lots of hits on the website, which slowed down the process. I hope I
didn't upset too many people with the upload and change of ISOs.

Thanks again. =)

Edit:
There is a guest account too. The login/password is guest/guest, but it has a few problems: PySol and glHack does not work and there is an issue with the soundmixer causing SnackAmp to refuse starting.

re: review

Oh, there's no real need to thank me, but thank you for saying. Just as with the reviews that get me nasty emails and mean comments, I just tell it like it is. You've done a real nice job here. I plan to keep an eye on your announcements page. Smile

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

re: wonderful mini

Yeah, I'm working with one stick of 512mb 333ddr, corsair mmx.

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

Slack- based distros are always interesting.

Because of its simple, straightforward design, Slackware has been the basis of some really interesting and creative second and third generation dikstros, including Slax, Vector Linux, and Zenwalk. I really want to try Wolvix.

Comment viewing options

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

More in Tux Machines

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.

US Sanctions Against Chinese Android Phones, LWN Report on Eelo

  • A new bill would ban the US government from using Huawei and ZTE phones
    US lawmakers have long worried about the security risks posed the alleged ties between Chinese companies Huawei and ZTE and the country’s government. To that end, Texas Representative Mike Conaway introduced a bill last week called Defending U.S. Government Communications Act, which aims to ban US government agencies from using phones and equipment from the companies. Conaway’s bill would prohibit the US government from purchasing and using “telecommunications equipment and/or services,” from Huawei and ZTE. In a statement on his site, he says that technology coming from the country poses a threat to national security, and that use of this equipment “would be inviting Chinese surveillance into all aspects of our lives,” and cites US Intelligence and counterintelligence officials who say that Huawei has shared information with state leaders, and that the its business in the US is growing, representing a further security risk.
  • U.S. lawmakers urge AT&T to cut commercial ties with Huawei - sources
    U.S. lawmakers are urging AT&T Inc, the No. 2 wireless carrier, to cut commercial ties to Chinese phone maker Huawei Technologies Co Ltd and oppose plans by telecom operator China Mobile Ltd to enter the U.S. market because of national security concerns, two congressional aides said. The warning comes after the administration of U.S. President Donald Trump took a harder line on policies initiated by his predecessor Barack Obama on issues ranging from Beijing’s role in restraining North Korea to Chinese efforts to acquire U.S. strategic industries. Earlier this month, AT&T was forced to scrap a plan to offer its customers Huawei [HWT.UL] handsets after some members of Congress lobbied against the idea with federal regulators, sources told Reuters.
  • Eelo seeks to make a privacy-focused phone
    A focus on privacy is a key feature being touted by a number of different projects these days—from KDE to Tails to Nextcloud. One of the biggest privacy leaks for most people is their phone, so it is no surprise that there are projects looking to address that as well. A new entrant in that category is eelo, which is a non-profit project aimed at producing not only a phone, but also a suite of web services. All of that could potentially replace the Google or Apple mothership, which tend to collect as much personal data as possible.

today's howtos

Mozilla: Resource Hogs, Privacy Month, Firefox Census, These Weeks in Firefox

  • Firefox Quantum Eats RAM Like Chrome
    For a long time, Mozilla’s Firefox has been my web browser of choice. I have always preferred it to using Google’s Chrome, because of its simplicity and reasonable system resource (especially RAM) usage. On many Linux distributions such as Ubuntu, Linux Mint and many others, Firefox even comes installed by default. Recently, Mozilla released a new, powerful and faster version of Firefox called Quantum. And according to the developers, it’s new with a “powerful engine that’s built for rapid-fire performance, better, faster page loading that uses less computer memory.”
  • Mozilla Communities Speaker Series #PrivacyMonth
    As a part of the Privacy Month initiative, Mozilla volunteers are hosting a couple of speaker series webinars on Privacy, Security and related topics. The webinars will see renowned speakers talking to us about their work around privacy, how to take control of your digital self, some privacy-security tips and much more.
  • “Ewoks or Porgs?” and Other Important Questions
    You ever go to a party where you decide to ask people REAL questions about themselves, rather than just boring chit chat? Us, too! That’s why we’ve included questions that really hone in on the important stuff in our 2nd Annual Firefox Census.
  • These Weeks in Firefox: Issue 30