lavaeolus

Sorry, but as far as I know an update from versions prior to 10.0 was not recommended, since to many things have changed, so I would really recommend a fresh install

If you installed them from rpms, maybe you have parallel-urpmi enabled in some way ??? just a very wild guess

voted sohpomore, although I know a bit more, but I don't like those self-called gurus, that most of the time are just advanced beginners, the real guru doesn't call himself one, but just helps others solving their problems that's why I like this forum: no guru's just a helpfull, knowledgeable and friendly community

so much for the desktop, that's why I always wondered what the sense of desktop icons should be, but the problem I thougt of is: I don't know how deep nautilus is connected into gnome and its session management

If they are still at 1.0.7 on cooker there is no real difference on the inside, except that the rpms are labelled 1.0.7, whereas on stable they are still labelled as 1.0.6 but in reality contain 1.0.7, I think Mandriva didn't want to have countless new mozilla-firefox-1.0.x directories in /usr/lib after every security update, so they just put the security-relevant stuff into the update-rpms, but do not rename the base-version there could be one difference, if cooker is using a newer compiler, then there is a chance that the cooker firefox is compiled with this version, therefore sometimes it's not very wise to install cooker packages on your normal mandy, it may spit in your face afterwards (it works sometimes but not always, cooker is experimental after all)

you should have one source for updates, if you have not, then open (in the menu) system/configuration/software/Mandriva update, it's the package with the blue arrow, you should get a list with mirrors, choose one of them as your update source (it then loads a file named hdlist.cz or synthesis.hdlist.cz, which contains all package information on your comp), after that rpmdrake will show you all available updates for your system, choose them and then you should be up-to-date whenever you want to update later click this icon again and it will directly search for updates, since you have already a configured update-source for installing thunderbird (if it's not already installed): go to: install software, then search for mozilla-thunderbird

the export looks ok (at least from the nfs-side) you could put all the users that should have write access in the group users and make the local directory on the server writable for this group sorry, I don't have a nfs-server at hand at the moment of this writing, so I can't tell you the exact permissions, but the above way should do it the problem with nfs or samba is, you have your local file permissions and the file permissions of the network service, but if your local permissions prevent your user from writing to the directory, you can't write even if nfs or smb is configured to be writable the local permissions supersede the permissions of the network service (smb, nfs) example: local directory belongs to joe user and is writable for group users, exported through nfs with no_all_squash, rw now jane user who does not belong to group users connects, she can't write on it until she becomes a member of the group users yes, this sometimes is a pain in the a..

I think it would have been a good Idea to include x.org 6.8.2 and some older drivers and let you choose at the installation stage, if you want to be secure (6.8.2) or bleeding edge (6.9.1cvs), with the risk of bloodying your nose, so they could still be centrino-certified (that was the reason for the cvs-x.org, to support all the new intel-chipsets), but would not have all those probs I remember back in mandrake 8.1 you had the choice between xfree 3.3.6 and 4.x, which was nice if you had an older card not supported by the newer xfree-version

as others before my pointed out you seem to have a x86-64 bootiso, look for something that is labelled ...i586.iso, and yes a fresh install is recommended, if I remember correctly updates from systems before 10.0 wouldn't even work

the acpi warning tells that your acpi (power management) does not work correctly, guessing from your graphics card your computer is a somewhat older model, that maybe does not support acpi, but since it does not seem to be a notebook, you can disable acpi, just go to the bootloader configuration and uncheck the ACPI entry, you could configure your services not to start acpi and acpid at boottime, too, or if you really don't need powermanagement just uninstall the acpi and acpid rpms. the other warnings seem to suggest that your monitor indeed does not support those refresh rates, maybe you could try reconfiguring your graphics setup, choosing a generic LCD-monitor in the list that closest matches the data of yours (Flat Panel 1024x768 for example, they are at the end of the monitor list under generic), maybe this helps btw if your graphics card and your flat panel both have a DVI use it, if you haven't already

Something I remember, which might be a problem: nautilus is not only the file manager for gnome but it also manages the desktop, so I'm not really sure if my guess would work, but I remember in gnome 1.x you could substitute nautilus by gmc, but don't ask me how I managed it back then, this was before gnome got this registry-like thing (aka gconf), on the other hand I think there must be a way and it should be found in gconf for KDE I really wouldn't even know where to begin my search

Maybe you could set up a new network profile in MCC (the profiles-entry in the menu) and add a second entry in your bootloader that boots with this second profile, I have three or four network profiles on my comp, they all have different network settings (even different hardware, since I use a pcmcia-card in one of the profiles) and don't interfere with each other, you can easily change the profiles on your running system, either through mcc or by right-clicking on the network-icon

Normally it's not my thing to bash reviews, but there is a difference if the review is objective or just to propagate a predetermined opinion.

sorry, maybe my somewhat unlucky formulation was a bit misleading if there was a newer package on the servers it would have been updated, there is no difference between using MCC or CLI in this respect using urpmi on the command line is just a different way of doing things, but in the end the effect is the same the difference is that the command line is good for use in scripts or if you don't have a graphical interface (on a server this might be the case), but on a desktop machine you can just use MCC as well urpmi has indeed some nice additional features on the command line, you can tell it to retain the rpm-packages in /var/cache/urpmi/rpms (that's where they are initially stored after download) if you want to use them for another machine, normally they would be deleted after install

Maybe you could look at the hardware databases of the linux-distributors for mandriva it's here: http://wwwnew.mandriva.com/hardware/ The problem is that even if the manufacturer does support linux in some way, not every product is supported, 3Com has wifi-cards that are supported under linux, there is even a driver out there for them, but not all of their cards are supported, important is, which chipset the card uses, the manufacturer itself is not so relevant best thing is a card with a chipset that is supported directly in linux, without such things like ndiswrapper, while you might get some cards to work with it, it's not always granted, therefore the question is not so unimportant as it might seem

maybe you can change this in gconf-editor: in /desktop/gnome/applications/Component_viewer there is an entry for nautilus, maybe if you change this to rox ? I did not test it, so it's only a guess

while the official upgrades from mandriva are labelled 1.0.6 on the outside they contain all patches from 1.0.7, it can be seen if you open about Mozilla Firefox it shows that it indeed is a 1.0.7: Mine shows: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050921 Firefox/1.0.7 Mandriva/1.0.6-16.1.20060mdk (2006.0) only the rpm is still called 1.0.6 (yes this IS confusing)

I'm not sure from where you got firefox and thunderbird, but if you updated them through urpmi update from an official mandriva mirror, they are still located in the 1.0.6 directories, while they are labelled 1.0.6 on the outside, inside there are the 1.0.7 versions (yes it is a bit confusing) for openoffice: the OOo 2 in Mandriva contribs is a pre-version, but it works very well, so if you can live with that, stick with it, otherwise you can install the official OOo2 rpms (they work very well on my system) or if you are a club-member, there are official mandriva-OOo2 packages available for members if you install the official packages from OOo, it's best to uninstall OOo 1.1.5 at first and make sure to install the mandriva-menus rpm from the OOo 2 archive, too (it is located in the desktop integration folder), otherwise you have no menu-entries for OOo 2 the only problem with this rpm is it puts its icons into /usr/share/icons/hicolor, so they didn' show up in my menus at first until I copied them to /usr/share/icons

I'm not sure if it was already said here, but jumping through the forums I found that some of the problems mentioned here are already mentioned on the Errata pages, it seems that these pages are not apparent to many users (admitted they are somewhat well-hidden on mandrivas security page) so here are the links: security advisory page: http://wwwnew.mandriva.com/en/security/advisories Errata pages: http://qa.mandriva.com/twiki/bin/view/Main...Linux2006Errata sorry, at the moment only 2006 errata was available but the others are linked on the pages above I hope this might help some users running into problems

the problem is, if the partition or directory on the nfs-server does not have the correct file permissions for your user it wont let you write, make sure that you connect as a user who has rights to write in the directory

suid-perl is not installed correctly, the setuid bit is NOT set, after installation you have to do: chmod 4711 /usr/bin/sperl5.8.7 in a console as root TIP: always read the errate page for your mandriva version, many of the problems I encountered where already mentioned there: go to http://wwwnew.mandriva.com/en/security/advisories and click the link: Errata

I think the main advantage of mandrivas partitioning-tool is, that it shows not just numbers, which is somewath unintuitive on Fedora and Suse but one of the really underestimated parts of mandriva is msec (sure nothing for the beginner), but it makes securing your system much easier about the qualities of urpmi we need not talk again, it's the other shining piece of mandriva apart from that I think the three distros are mostly equal in ease of use

nice to hear seems that it didn't load the ndiswrapper module automatically, have never worked with ndiswrapper, so this never occured to me concerning udev and updates: you can update from the CLI too: I think it's urpmi update, but then there must be a newer version of the packaage in one of your update-sources

as far as I know they included it to become centrino-certified, because it includes modules for some new intel-graphics for the ati-xpert, sorry but the ati-driver won't do it, because its just for newer radeon-cards, even the first radeon mobility isn't supported by this driver, not very nice, ati has good hardware but their linux support is really bad

is the package dynamic installed ? as far as I know it handles things like mounting usb-connected digital-cameras and the like rpmdrake tells me the following about it: Create desktop entries for GNOME and KDE when a new peripheral is plugged in the system (mainly USB devices). on my system plugging in a konica-minolta digicam works without hassle on both 2005 LE and 2006, it is automatically mounted and I can access it like a harddrive