Mandrake 10.1 Community Released

MohammedSameer writes "Mandrakesoft released MandrakeLinux 10.1 Community, As usual it's only available first to the club members The new release features Kernel 2.6.8.1, Xorg-X11 6.7, KDE 3.2.3 with 3.3 as an install option,"

Comments

Also, let's not forget to thank Texstar...

[Chuck Bucket]

One of the best resources in the Mandrake community has been an individual called Texstar who ran a Linux news site called www.pclinuxonline.com and also in his spare time created RPM packages for Mandrake systems. Texstar's packages became justly famous and were widely used. Thanks to his efforts, many reallly nice RPMs were made available to the MDK commmunity, and eventually went into 9 and 10 from what I've heard. This kind of 'community support' is what I'm most happy with.

Thanks Texstar!

CB@#$

2.6 kernel may blow away NTFS.

[jlseagull]

This problem is common with the 2.6 kernel and has been verified in Mandrake 10.0 Community, Red Hat FC1, Red Hat FC2, and others.

Read about it here.

Basically, if you touch the MBR with a 2.6 kernel bootloader, XP or Windows 2000 is gone, and can't be restored. So backup your MBR first by using

"dd if=(input device) of=/(output dir)/hda-img.mbr bs=512 count=1"

where if=(input device), should point to your first drive, eg. /dev/hda, and of=(output dir) should point to where you want to save the bootsector as a file. Restore the MBR by reversing the input and output.

Even if you do this to restore, your Windows partition may still be toast, depending on how much you messed with the partition table.

Re:2.6 kernel may blow away NTFS.

[hitmark]

oh man, not this old story again.

what happend was that the bios didnt agree with itself if it should use chf or lba mode to set the gemoetry of the disk. windows relys on the bios info when it creates the partitions. then along comes the linux kernel, pokes the disk directly, finds that the geometry info used to create the partitions is wrong and goes about cleaning up. then windows comes back and finds non of the info it expects and in good old windows fashion trows its virtual arms in the air and gives up. the files are all there, the partitions are all there, its just that the partition table isnt of the type windows expects and therefor windows fails.

its just like ripping a disk with win2k or later on and stick it into a diffrent computer. on boot you will most likely get a bluescreen with a error as windows rely on its old hardware list to boot drivers, and when said drivers fail there is no fallback. linux on the other hand build the list every time it boots and therefor will not have mutch of a problem with the move.

complaining that this is a linux error is like complaining that there is something wrong with firefox when you try to access a page designed with ms frontpage. most likley a visit to the w3c validator will show so many error that you will be surprised that it renders at all.

the problem is that windows have become so mutch a "standard" that when something goes wrong it have to be the odd boy out there is the problem, not the devil in drag down the road.

I'm about to renew.

[biendamon]

I'd say club membership is worth it, if you happen to prefer Mandrake as your primary distro. I appreciate the dedicated mirrors for club members quite a bit. Makes patch times much faster.

I also like the repositories for software that are available to club members. I have yet to find a piece of software out there that someone didn't turn into a Mandrake RPM, and the club mirrors seem to have it all. Sure, you can find them other places, too, but all in all it's nice to have everything in one place.

Comment removed

[account_deleted]

Comment removed based on user account deletion

The issues have been fixed in the kernel

[Sits]

Here is a cooker mailing list post refering to the bug being resolved.