Language Selection

English French German Italian Portuguese Spanish

Kicking the tires of Mandriva 2007.1 beta 2

Filed under
MDV
Reviews
-s

The folks at Mandriva are hard at work preparing the next incarnation of MandrivaLinux systems for home, office, and server applications. Mandriva Linux 2007.1 Beta 2 was announced yesterday and I wanted to take a look. I didn't spend a lot of time in it due to a personal showstopper, but what I saw really nice looking. So, as brief as it may be, I'd thought I'd share my experiences with my visitors.

I downloaded the 3 gig i586 dvd as linked to by distrowatch.com and had it in about 18 hours or so. Although I didn't spot any new features or changes in the installer, it installed almost 5 gigs of software rather quickly and without issue onto my HP laptop.

Hardware detection was fairly good, a startup sound greeted me at login, but it didn't detect my graphics just right. I was offered several choices for the generic flatpanel it detected during install, but none were my desired 1200x800. I chose 1024x768 until I could edit the xorg.conf file manually. After install, I was able to tweak my resolution to 1152x768. I probably could have messed with it some more, but in my world I call that a "close enough." The touchpad worked accurately and smoothly, and an additional usb mouse was also correctly setup. Wireless is another matter and what ended my foray.

But the good stuff first. Man oh man, Mandriva is looking goood. The default fonts were pretty nice looking, but I'd probably tweak on them some. The new wallpaper is yummy. I love it. It's, of course, blue, but this time we have some nice flower silhouettes in a lighter shade of blue gracing the bottom right hand corner and some outlines in the upper left. These aren't sissy flowers now, these are nice tasteful wildflowers I guessing. Anyway, it doesn't look "girlie." It's just pretty.

        


The KDE panel has been simplified and redecorated as well. Others in the community speculate that Mandriva has borrowed elements from Linspire, but regardless, it's looking real nice as well. The start button looks very kbfx-ish and launcher icons are limited to Firefox and Kmail at this point. The systray is home to klipper, net monitoring, and kOrganizer. Despite some new menu implementation, they aren't changed in appearance or structure. I don't care for the mandriva menus much and always change mine back to KDE/Gnome menus in the Mandrake Control Center. The boot splash, login screen, and kde start splash match the new wallpaper perfectly and make for a complete package.

The Gnome desktop is equally appealing. The same great wallpaper decorates the background and the Ia Ora theme is still looking good in shades of blue. The panels have a nice 3d effect in an almost metallic appearance with just a hint of powder blue coloring. Add them up and you get what feels like a really polished desktop.

        


I didn't test a whole lot of the applications, but you might know mandriva. They include just about everything but the kitchen sink and inevitably there will be crashes here and there. In fact, the clock applet crashes in gnome at every startup unless you disable it. But this is a beta 2, so no sense in spending a lot of time running down what started, what didn't, and what crashed anyway. Especially since I couldn't get my wireless connection to work.

That's the bad news. My windows drivers dependent wireless chip couldn't be made to work with this release. The adventure started when trying to configure it during install and I just got the 'couldn't do it' error. (I'm paraphrasing of course.) Later in Mandriva I tried through the Mandriva Control Center and I got the error that "can't install wireless-tools." They did however include wpa_supplicant. Nevertheless, this wasn't the end of road for me.

What was the showstopper for me was the error received during manual setup at the commandline. I could install the windows drivers just fine, but when modprobing ndiswrapper I got the "bad magic" error. It complained that the drivers were 64-bit and the kernel was 32-bit. And it's true. I downloaded the 32-bit system. But also, for what little it may be worth here, I saw this same error with SimplyMepis more than once and using the 64-bit system didn't cure it. Also, I'd like to state that other 32-bit systems do just fine with it, such as openSUSE and PCLOS. So, for now, I'm not going to test the 64-bit version of mandriva. The weekend is over and time to get ready for the workweek, but next beta or perhaps the first release candidate will work for me. I'll let you know. In the meantime, if you have a natively supported wireless chip, you can download the wireless-tools and libiw28 rpms from a mirror and probably enjoy.

Likewise the 3D desktop will have to wait as well. I've not had much luck with Mandriva in that department, but I'll test this feature again next release.

In conclusion, Mandriva 2007 is looking really good. I really like the updated presentation Mandriva gives. I hope the wireless setback is temporary. I want for them to make a comeback so very much. Let's cross our fingers for this upcoming release. As my mama used to say about me, if Mandriva does as well as it looks it will be just fine.

re: Mandriva too French ?

atang1 wrote:

Tuxmachines had pushed most distros to use Linus official releases to comply with Linux projects to have backward compatibility.

You'd think I'd remember saying something like that. Thinking

re: Well, you complained

I did?

I don't think that was me. I don't even use a straight linus kernel on my everyday gentoo anymore, not since 2.4. I use gentoo's hardened sources for the server and their regular sources for the desktop.

re: in your ealier reviews

hmm. maybe I did.

It's awful to get old and senile. I don't recommend it.

Thanks for the clarification

I hadn't considered Mandriva's kernel modifications as a factor in the bug fixing they have to do. I've not really looked into Ocilent1's kernels (Ocilent1 does the kernels for PCLOS) too closely, but I would guess they don't stray too far from the official kernel releases.

I think a number of other factors have contributed to Mandriva's demise.

  1. I think their cutting staffing levels too close to the bone, trying to do too many different flavors of distro releases over the years has brought the quality and reliability down.
  2. Sometimes I get the feeling that they're just not paying close attention to the Linux OS market (that stubborn independence?). Competing with 'buntu who is currently giving all their stuff away is problematic.
  3. A slick, helpful, easy to navigate web site is a must these days for a successful distro. Mandriva's web presence is, and has always been a cluttered and confusing mess.
  4. An easy-to-use, consistent, and reliable update process is essential. Mandriva has changed its repository directory structure so many times over the years, you have to become a Private Detective just to find package updates. And when you do, often the dependencies are not properly configured.
  5. They lost some community support with their abrupt termination of Mandrake/Mandriva founder, Gael Duval. Good community relations and support are still essential for an effective for profit Linux distro, even when most of the revenue is from corporate contracts.

PCLinuxOS

Isn't it ironic that a small and independent fork of Mandrake -- that which you sport in your Web site -- has gone above Mandriva, at least according to DW?

Re: Mandriva

Nice writeup Susan. I too would hate to see Mandriva go under. Or, even worse, make a pact with the devil for a quick infusion of cash like Novel/SUSE.

Not real sure what atang specifically means by 'too French'. Of course, for Mandriva, a real partnership with Dell would be ideal. But, of course, Mandriva still has yet to prove themselves with 2007.1. And, sadly, it looks like Dell isn't ready to offer installed Linux with the sale of their machines (Dell may eventually change its mind as realization sinks in about what a slow pig of an operating system MS Windows Vista really is).

PCLOS still depends on Mandriva, and although the skill set and dedication of the devs at PCLOS is sufficient to create a good distribution based on Debian or some other major branch of the distro tree, I would hate to see that happen.

PCLOS has taken the best part of Mandriva and specialized, customized, and polished it to near perfection as a 32-bit desktop Linux distro. And they've done this with just a few people and an extraordinary amount of sheer hard work.

Of course, Mepis has done the same with Debian. And 'buntu, in a more comprehensive way, has also done this with Debian.

I downloaded and installed PCLOS 2007 Test Release 3 yesterday, and watched it shine. What a great desktop distro!

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