jboy

EDIT: My original answer was not right. See devries' answer below and also this one.

I'm wondering if you perhaps have ntldr (the windows loader) and boot.ini on hd1? If so, check the contents of boot.ini - does it points to rdisk(2) as the location of the Windows folder? Since WinXP doesn't boot off hd2, maybe ntldr and boot.ini are not on it but on hd1 instead?

Seems very strange! Have you taken a look at the settings in KDE Configuration -> LookNFeel -> Panels? Maybe there's something in there that needs reconfiguring? There's a Defaults button so you can reset to defaults. If you login as a different user, does the same problem occur? There's also a ~/.kde/share/config/kickerrc configfile. Maybe somethere in there? Or maybe it's just getting close to Halloween and the ghosts are playing tricks on you for sport? :D

I don't think so. Many people typically install downloaded rpms using urpmi. That way you have the benefit that if any dependencies are needed that aren't in the rpm and aren't installed yet on your system, urpmi may find them in it's repositories and install them. The --allow-force flag option should still prompt you if a dependency is not found, so you still have the option whether to proceed or not. So I don't think there's anything problem. You're not having any problem with the Open Office install, are you?

I've never tried it but there is a thread on it here: https://mandrivausers.org/index.php?showtopic=23913 Read the whole thread, especially: https://mandrivausers.org/index.php?showtop...91entry176591 Also check out: http://ylraw.free.fr/files/mkusb/ Be sure to read the procedure at http://ylraw.free.fr/files/mkusb/mkusb.txt Sorry I can't guide you any further than to point out these links.

Any clues from the messages in /var/log/messages?

Here's a message that might apply from the 2006 Release Notes page at http://qa.mandriva.com/twiki/bin/view/Main...006ReleaseNotes Plextor burner For security reasons the program to burn CD or DVD (cdrecord) is not run with administrator privileges (suid root). However it appears that for some Plextor burners, the cdrecord binary has to be suid root in order to be able to burn. If you cannot burn with your Plextor burner (and potentially other brands), try to give suid root privileges to the cdrecord binary: chmod 4755 /usr/bin/cdrecord

Check the Devices and/or Media folders on your Desktop. If the USB flash drive was detected and automounted, it should show in these folders with a Removable icon. If not check the output of the dmesg command for errors (also browse /var/log/messages) and also try starting up the machine with the USB device plugged in (to try to identify if the problem occurs only with dynamic detection of the device).. Various USB problems with 2006 have been reported. My USB flash device is detected and automounted ok in 2006.

I was able to run it ok, configure the channels, and apply updates as root with the command: smart --gui Shadowchasers images were helpful as I wasn't sure how to configure the channels. IMO, the interface is a little clunky, not too intuitive, and with not enough online help. But it does look like it could be a useful tool and I'll probably keep using it until I'm as familiar with it as with urpmi and rpmdrake

Check your favorite public mirror. There's a good chance the 2006 Official tree may now be available there. But not the ISOs yet.

It appears that this PLF mirror for 2006 free and non-free is available (I haven't checked the others): ftp://plf.time4t.net/pub/plf/mandriva/free/2006/i586/ ftp://plf.time4t.net/pub/plf/mandriva/non-free/2006/i586/

Yeah, I'm another one of those for whom Windows work pays the bills, but all my machines dual boot with various Linux distros (Mandriva being my favorite).

You can use the same separate /home partition, but just make sure that you use a different user name(s) than what you have for your current distribution. I've done this many times with no problem. As long as the user names are different, a separate directory for them will be created, leaving the directories for your current distribution's users alone.

The Limited Edition 2005 name just means something to the effect that it's an interim release between the previous Official release of 10.1 and the the next major Official release of Mandriva Linux 2006, which has just now become available to Mandriva Club members (available to the public via download from mirrors later this month or next month). LE2005, though not carrying the Official tag, is a full-featured very robust version in all respects.

See Keeping Your Cooker Installation Up-To-Date

Several good tips are in this thread: https://mandrivausers.org/index.php?showtopic=26976 Especially note ianw1974's post on Realtek cards.

According to this, the ISOs will be available to Club members and contributors tomorrow (Thursday 06-Oct-05): http://qa.mandriva.com/twiki/bin/view/Main/MandrivaLinux2006 Adam Williamson confirmed this today in a post here: http://club.mandriva.com/xwiki/bin/view/Ch...DiscoveryLX2006 As far as which mirrors, I dunno since I'm not a Club member, but the Club website will undoubtedly have that info once they're available. Note that the public release date is 26-Oct-05.

Apparently Cooker is not frozen right now, because an urpmi update I tried today installed some 2006.1 updates. So apparently this supersedes 2006.05. /etc/release shows: Mandriva Linux release 2006.1 (Cooker) for i586 Does anyone know if these will be part of the official 2006 Release or is this now the start of a new development cycle in Cooker?

Here's a couple ideas, but not a complete answer to your questions. This is a bash shell script that will trim files in /var/log to the last 50 lines. File should be owned by root with read, write, execute permissions by root only. #trim /var/log if [ `whoami` = "root" ]; then echo "Trimming /var/log..." find /var/log -type f -exec sh -c '[[ "${1##*.}" == "gz" ]] && rm $1 || (tail -50 $1 > ${1}.tmp && cat ${1}.tmp > $1 && rm ${1}.tmp)' '{}' '{}' \; echo "Finished with trimming" else echo "You must be root to trim logs." fi In firefox: Edit -> Preferences -> Privary Clear History Clear Download Manager History Clear Cache

I've used an AMD in just about every box I've ever built for myself - from a K6-2 to the Sempron. Haven't tried an AMD-64 yet, though. I always felt that price/performance favored this choice. And just as it subjectively feels good to me to support the underdog Linux vs. Microsoft, the same goes for AMD vs. Intel.

Here's one! http://baghira.sourceforge.net/OS_Clone-en.shtml

I had an LE2005 install on a test machine that I thought I'd try upgrading to what's currently in 2006 Cooker via an urpmi upgrade. Worked very nicely. I followed the procedures in this following thread, especially the posts by arctic, adamw, and ianw1974: https://mandrivausers.org/index.php?showtopic=25807 This was a fairly standard client machine with KDE, Gnome, and OpenOffice. About 600 packages were updated, not including the kernel upgrade. This probably wasn't necessary, but the first thing I did was update urpmi itself with: urpmi urpmi Then I resumed the upgrade with: urpmi --auto-select -v Only real urpmi problem was a conflict between kdebase-common and kdelibs-common, so that neither package would install. The conflict was due to: /usr/share/icons/crystalsvg/16x16/devices/nfs_mount.png (also 32x32, 48x48, and 64x64) To resolve this, I did: urpmi --allow-force kdelibs-common After the urpmi updates, I did the kernel update to the kernel-2.6.12-12mdk package. Then I executed the 'updatedb' and 'locate rpmnew' commands and resolved the differences, as described in the above thread. Had about a dozen rpmnew files to reconcile with the original config files; e.g., the shorewall rules, policy, interfaces, and zones files, and various other config files. Then I fixed up /etc/lilo.conf and executed 'lilo -v' to update the MBR with the new boot loader info. I also removed the old kernel with urpme. This wasn't really necessary but I went ahead and did it anyway since the LE2005 kernel is not supposed to work with a 2006 install. Periodically during the downloads, urpmi would hang so I just did a Ctrl-C and restarted the 'urpmi --auto-select -v' command and it just picked up from where it left off. No problems with using my existing /home from LE2005, so my configuration settings transferred with no problems so far. Caveats: I don't use this machine for audio or cd-writing or printing so that part of the upgrade is untested. All networking functionality works fine, including ssh into and out of the box. Several weeks ago, I did a new install of 2006 and this upgraded install seems to work as smoothly as the fresh install although it's on a less powerful machine so I can't be quantitative about things like boot-up time.

I'm assuming that Cooker currently is reasonably close to what the upcoming 2006 release will be. Is this right? At what point will it start diverging from 2006 and how would we know when that is?

It's available here (and perhaps other mirrors as well): ftp://mirrors.usc.edu/pub/linux/distribut...-12mdk.i586.rpm

This might help: https://mandrivausers.org/index.php?showtop...ndpost&p=205854