Mandrake Linux 10.1 Release Notes
From Mandriva Community Wiki
Mandrakelinux 10.1 Community has been released, Mandrakelinux 10.1 Official is scheduled for September, 2004
Note that these notes are here to assist the end user in setting up the new OS by warning them of major changes from prior versions in the features and functionality of the system and not a place to report bugs or errata. There are seperate places for that.
This page was developed because many people complained that major changes were not explained properly, so users either didn't know how to use the new feature, or didn't understand the rationale behind it, so they got mad (and closed-minded) about it. Please fully explain the rational behind the change as well how to configure the machine with the change (or the difference between the old way and the new way). It would be helpful also to point out where more info can be found. more info = better.
The general hierarchy of the repository has been changed. Everything related to installation is now in /install, included live install files (install/stage2/live), images (install/images), isolinux (install/isolinux) and ramdisks (install/stage2). Packages are still separated in media, located in /media. A top level /media/media_info directory contains general medadata, and each medium has a subdirectory media_info with related packages metadata.
You now have the possibility to add extra media (CD or network) during the installation. This means that you can download only the disc 1 or the new mini disc 1 and add a network source to complete your packages list.
- Boot with the Mandrakelinux-10.1rc1-mini.i586.iso or the Mandrakelinux-10.1rc1-CD1.i586.iso
- Select HTTP or FTP extra medium.
- Wait for basesystem to install.
- Follow the steps to configure your network.
- Enter your mirror URL (check http://www.mandrakelinux.com/en/cookerdevel.php3 to find mirrors). Use the complete URL path, and preferably use the frozen 10.1 subtree instead of the cooker one, e.g. ftp://ftp.free.fr/pub/Distributions_Linux/Mandrakelinux/devel/10.1/i586/media/main/
- Add a new medium or proceed with the packages installation.
Problems with devices after upgrades?
The most common problem reported during the 10.1 beta release was problems accessing some devices. In most cases this was due to users not having udev enabled, or having both udev and devfs enabled. To ensure you are not set up for failure, ensure that you boot the correct kernel, with devfs disabled (your append line for your kernel should not include "devfs=mount", it should either have "devfs=nomount" or no devfs entry) and ensure you have the udev package installed (urpmi udev) with it set to start at boot (check 'chkconfig --list udev').
On computers with firewire, firewire networking will now be bound to the first availlable ethX, after all other interfaces have been set up (eg: if you've two network card, your firewire will be eth2).
laptop_mode is used to lower battery usage via the suspend-scripts package. Configure it with /etc/sysconfig/laptop.
PCMCIA network cards
Network cards must be set to ONBOOT=yes now. So you need to change it if you upgrade using drakconnect or any other ways.
- most PalmOS PDA working device should now be automatically detected and linked to /dev/pilot (see Bug #3381), but some can't be autodetected (like Tungsten T, T2). In this case (ie if pilot-link -l failed after starting hotsync on the Palm), add "VISOR_SWAP=true" to /etc/sysconfig/usb to force correct device usage.
- Bluetooth keyboards and mouse should be working out of the box, very early in the boot process (once USB is initialized). To have bluetooth support for Lilo/Grub, you need a recent enough BIOS with "USB Legacy mode" enabled. Unfortunately, authentification need to be disabled by default for keyboard/mouse, which might cause other bluetooth devices to not be able to communicate with your computer. To enable authentication, remove '#' at line '#auth enabled" in /etc/bluetooth/hcid.conf and run "/sbin/service bluetooth restart". Beware this might break bluetooth mouse/keyboards.
- DKMS support is included in the system by default. This allow to install kernel modules separated from the main kernel. See http://linux.dell.com/projects.shtml for more info.
A new tool, dmraid (Device-Mapper Raid tool) was included in the distribution.
It discovers, activates and displays properties of software RAID sets (ie. ATARAID) and contained DOS partitions using the device-mapper runtime of the 2.6 kernel.
The following ATARAID types are supported on Linux 2.6:
- Highpoint HPT37X
- Highpoint HPT45X
- Intel Software RAID
- LSI Logic MegaRAID (basic support)
- Promise FastTrack
- Silicon Image Medley
SONY Combo CD-RW/DVD CRX320E
- Firmware NYK1 does not inform cdrecord correctly about which driver to use. Update the drive to the NYK5 firmware.
ICH5-based motherboard (like in the Shuttle SB75G2) with a SATA hard drive and an IDE PATA CD(-RW) drive (ATAPI)
- With this configuration, one can get a freeze at boot when detecting the drives. Reboot and enter the BIOS settings (pressing DELETE). Go to Integrated Peripherals -> On Chip IDE Device -> On Chip Serial ATA Setting. Set the SATA Mode to "Enhanced mode" but not "Auto" (see Serial ATA (SATA) Linux status report #ICH5).
- GNOME 2.6
The simplified menu system has been enhanced to avoid the "All Applications" entry.
Amhraic and Vietnamese are now configured to use an input method.
A new universal input method framework has been added: SCIM. SCIM is now the default input method for Amhraic, Chinese and Korean. Japanese uses SCIM+UIM.
Vietnamese uses x-unikey by default but SCIM provide IM support for it too.
Localedrake now enable one to change its default input method. It will also install the needed packages if you are configuring the whole system (ie if you run it as root). One can also altered the preselected input method at install time by clicking on "Country / Region" in summary.
The following input method are availlable:
- ami (Korean)
- fcitx (Chinese Simplified)
- im-ja (Japanese)
- kinput2 (Japanese)
- miniChinput (Chinese Simplified)
- nabi (Korean)
- UIM (Japanese)
- SCIM (nearly universal), SKIM (Qt frontend of SCIM, through contrib)
- xcin (Chinese Traditional)
- x-unikey (Vietnamese)
hostname changes and X sessions
hostname changes triggered by network scripts will no longer break X sessions. This is implemented in the s2u package.
Default routes are handled by device now to allow easy plugging/unplugging of network cards. To have priority between your devices, use the METRIC variable in your ifcfg-* files. These values are preconfigured by drakconnect wizard (priority is Gigabit > Ethernet > ADLS > ISDN > Modem). They can be altered through "Manage Interfaces" in "Network & Internet" section in Mandrake Control Ccenter.
The METRIC is an integer. The lower the greater priority.
The internet service has been removed in favor of the normal network service. The installer or drakconnect will take care of the transition.
There is a new net applet that displays the network status in the notification area of the panel.
Speedtouch USB ADSL
If you got problems to connect the internet with revision4 modems, download http://download.ethomson.com/download/KQD6_R204.zip and copy KQD6P2.eni to /usr/share/speedtouch/mgmt.o. If drakconnect fails to bring the connection up, try this command :
modem_run -v 2 -k -f /usr/share/speedtouch/mgmt.o && ifup ppp0
udev is now the default device manager
- if urpmi has been used to upgrade from Mandrakelinux 10.0, make sure the udev package is installed, and change the "devfs=mount" option in your kernel command line to "devfs=nomount" (check /etc/lilo.conf or /boot/grub/menu.lst); this option will be automatically removed for kernels installed in 10.1 Official Bug #11892
- the udev service must be started at boot, or else some devices may be missing (use "chkconfig --list udev" to check if it is enabled, "chkconfig --add udev" to enable it) Bug #11852
- previous Mandrakelinux releases used some devfs rules to create links in /dev (/dev/mouse, /dev/dvd, /dev/modem), these rules should have been migrated to udev rules by the udev package from 10.1 Official Bug #10860
- Bug #10821 udev doesn't remember NVIDIA driver devices => put in /etc/modprobe.preload
xorg is now the default X server and the configuration file has been moved from /etc/X11/XF86Config-4 to /etc/X11/XF86Config
- With printerdrake a machine can be configured as daemon-less CUPS client now. All printing requests are directly redirected to a specified server. This avoids running a local spooler daemon and saves resources, but if the server is down printing is not possible.
- When setting up a print queue via the add-printer wizard the print queue name is only asked for after choosing the printer model, then the default name is derived from the model name and not "Printer1", "Printer2", ... any more.
- One can enable and disable print queues by appropriate commands in the menu appearing when clicking the "Edit" button or double-clicking a print-queue entry in the main window of printerdrake. In the main window also the state whether enabled or disabled is shown.
- Special needs by applications (OpenOffice.org, GIMP) are not handled by printerdrake any more, the applications are appropriately patched to print out-of-the-box.
- If the printing infrastructure is installed by starting CUPS once with a normal CUPS configuration (not daemon-less) additional USB printers are automatically configured by simply plugging them in and turning them on.
- If a print queue is disabled, for example because a user tried to print on this printer but the printer was turned off, and the printer (USB) is connected and turned on again, the queue gets automatically enabled, so that the printer is immediately ready to print.
- Many new drivers and driver versions: Gimp-Print 4.2.7, HPIJS 1.6.1, drivers for Minolta PagePro 12xx/13xx, magicolor 2300W, Canon LBP-460/660, ...)
- drakroam - Assist with wireless networking
- drakbt - Wizard for setting up Bittorrent
Openssh has PAM disabled by default
In OpenSSH 3.8 and later, PAM is disabled by default. While there are triggers in the new OpenSSH packages that check whether you need PAM support (based on the settings in /etc/pam.d/system-auth, checks being done for ldap and winbind at least), and enable it if necessary, if you are doing a new install and configure authentication via winbind or ldap, or change authentication types later with drakauth, you will need to manually enable PAM (change the "#UsePAM no" to "UsePAM yes" in /etc/ssh/sshd_config and restart the sshd service).
- gcc 3.4