ianalis

Actually, I have already upgraded my system. Rpm's installed after the entries were duplicated do not produce duplicated entries. Any other ideas? How is the menu constructed? That is, what files and/or directories are being looked at to create the menu?

Hi! Where can I get the md5 sum of the burned installers, not the iso? Also, can I just do md5sum /mnt/cdrom to get a cd's md5 sum? I remember that rh9 and fedora has the capability of checking its installers for errors. I wonder if mandriva will add that

Hi! The menu entries for all the users in my system were duplicated i.e. each entry occurs twice, after installing an rpm that I already forgot its name. In menudrake, the entries only show once but in kmenuedit, the duplicate entries show up. I tried deleting the duplicate entries in kmenuedit but the following error comes up: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x320044d any ideas?

uummhhh... they are the same OS: Linux (Gnu/Linux for the purists.) You are referring to a distro, not an OS

a bit off topic... I hope you have a very good reason to install IE6. I think it's a huge step backward when people are switching to firefox. Yes, it's immune to some of the vulnerabilities because it runs in linux. But... ...maybe you just want to use it for testing your webpages :)

make sure you have a static build of wx_gtk2_xrc-2.6 installed

Hi!I'm trying to rebuild kde from srpms but I've encountered some problems. I first rebuilt arts and I was able to succesfully rebuild and install it. Then, I successfully rebuilt kdelibs. However, I can't the install the built rpms (kdelibs-common, libkdecore4) because kdebase-progs and libkdebase4 conflicts with them. I tried rebuilding kdebase but it needs kdelibs-devel. How do I solve this apparent circular dependency? [moved from Software by spinynorman]

The disk is not broken. In fact, I'm able to write to it sometimes. It also works perfectly for mdk 10.0, fc3, win xp, win 2k and win 98. In fact, I am forced sometimes to reboot to winxp just to write to it. Any other ideas? How do automounting and autounmounting work?

what does it do? iphitus <{POST_SNAPBACK}> It means that only files residing on the source's partition will be copied. For example, if a subdirectory is actually a mount or a link to another partition, then it will not be copied.

Hi! I've been tinkering with my distro lately and now my flash drive is not writable anymore. First of all, I'm not asking anyone to fix it for me because it's my fault anyway. I just hope some of you can point me in the right direction. Now, the flash drive is automatically mounted and unmounted. Files can also be read and copied from it. The only problem is that I can't write to it, most of times, even as root. The fstab entry for that drive is: /dev/sdb1 /mnt/removable auto umask=0,kudzu,codepage=850,nosuid,nodev,iocharset=iso8859-1,sync,users 0 0 I was wondering if it's a permission issue but I guess umask=0 is already sufficient. I'm thinking about replacing auto with vfat but I don't know how to do it aside from editing fstab directly. I'm not even sure if that will work. I'm planning to study how the automounting and unmounting works but I don't know where to start. What do you think? Any help would be very much appreciated :)

Hi! Does anybody have a clue why this problem occurs? I'm experiencing this quite frequently for some time now. I know it's wrong but I've mixed 10.1 and cooker rpm's. I've tried updating kdebase, kdelibs and several other rpm's but it still comes up. What do you think are the other rpm's I need to update or is there other fixes? I'm on dial-up so updating to the latest cooker release is very inconvenient for me.

I think I made a mistake. That should be splash=silent. Anyway, I guess you got the idea and solved your problem :)

remove display=silent from the append line of the image you are using

How did you run mkinitrd? I tried running it with mkinitrd preload sd_mod preload scsi_mod with=ata_piix /boot/initrd-2.6.8.1-12mdksmp-sata.img 2.6.8.1-12mdksmp but it says it cannot open initial console after detecting the sata drive. EDIT: I've solved it! I'm actually moving my / to a new sata drive. Apparently, cp -ax / /newroot will not copy the contents of /dev. What I did was to cp -a /dev/* /newroot/dev after that. It works fine now except the bootsplash is not displayed. Probably, bootsplash needs to be added to the initrd. I'll stfw first

Hi! Thanks for giving me the idea. Apparently, the module was not loaded. I just loaded the module, ata_piix, and it worked. I added it to modules.preload so that it will be loaded everytime I boot. I thought it is automatically loaded since it was detected. I was wrong :(

Hi! I have a new sata drive (seagate 80gb 7200.7) and it was detected by the bios. The driver, ata_piix for intel ich5, was detected and loaded but the drive is not detected. Since it's new, there are no partitions there. I'm using mandrake 10.1. I've read that it's compatible that's why I bought it. Any ideas? I've tried to stfw and this forum but the results were about installing a distro on it. Btw, I have kernel 2.6.8.1-12smp if that's important

in windows me, the usb key still blinks slowly even if the device was stopped. i guess it's really okay to unplug it while unmounting. probably, the blinking is due to the pc probing the attached usb devices

thanks! I've read the manpage before I posted but I've skipped parameters that begin with "no" I've read the manpage for urpmi.cfg and there was no option to change the cache ditectory. Anyway, I'll just move the rpm's myself

How can I make urpmi download the dependencies only or at least stop urpmi from deleting the downloaded rpm's after installing? How can I set the directory where the rpm's will be put?

i tried issuing umount /mnt/removable and the directory was unmounted. however, the device still blinks slowly and /mnt/removable was automatically removed when i unplugged it. i think i will just rely on the automatic unmounting. of course i will not remove it while it's blinking rapidly, indicating that data is being transferred. i don't issue a synch before unplugging it since the automatically added fstab line contains the synch option. so far, i have experienced no problems with it. i'll just post again if it becomes broken... hopefully, i will never have to :unsure:

i have read from several sources that usb devices need not be unmounted. i tried doing that and, indeed, the device was unmounted (and mounted) automatically. however, the device (usb key) was still blinking, but not as rapid as during a data transfer, when i detached it from the pc. in windoze, the device stops blinking when i choose the "safely remove hardware." so, is it really okay to remove it without unmounting? btw, what is the system used for the automatic (un)mount in mdk 10.1? is it supermount?

apparently, this was a bug and was already fixed (but i haven't tried updating yet): http://bugs.kde.org/show_bug.cgi?id=92501 the above workaround worked for me