jboy

That was a rare fluke, John! :D I was just thrilled that there was a question that I knew an answer to that hadn't been answered yet! I didn't know about the MCC -> Help -> About way, so I'm glad he got the GUI way of doing it as well as a CLI way.

Open a terminal and enter the command: cat /etc/version For example, mine gives the following: cat /etc/version 2006.0.1 2.0.20060 Metal Platinum

I have a Samsung TS-H552-U, cost $39 six months or so ago. It's an EIDE Internal drive, double layer DVD-RW. Works great with K3B. Never had a bad burn. I really like it. Link: http://samsung.com/Products/OpticalDiskDri...RW_TS_H552U.htm Newer models are now available since I bought mine: http://samsung.com/Products/OpticalDiskDri...ables/index.htm I highly recommend that you get a DVD Writer and not just a Reader. The prices are so low these days for DVD Writers, it'd be a shame not to get one.

Have you considered using Multiple Desktops in KDE? kcontrol -> LookNFeel -> Multiple Desktops Then, in LookNFeel -> Taskbar, make sure the Show Windows from All Desktops checkbox is unchecked. Now you have several virtual desktops (whatever number you chose) and the taskbar will show only the apps opened in that Desktop. Switching to a different Desktop is only a click away. See the KDE Help Center for more info. If you use Gnome, maybe there's something similar, I dunno as I don't use it.

Oooh, that squeeze-repeats option is nice! Great catch, neddie. Much more elegant. Will definitely have to remember that option for future reference.

I just discovered that if you select all the text in Kate, then issue the Ctrl-J, all the separate lines will be joined into one line. So after doing the Replace to convert linefeed chars to commas, highlight all the text, and then press Ctrl-J. Now all you have to do is replace the ", " with "," and you're done.

If you want to do it solely within kate, there is a way of doing it that I just found out about. Open the text file in Kate Ctrl-R (Edit -> Replace) Text to Find: $ Check the "Regular Expression" box Replacement text: , Click Replace button This will replace all linefeed chars with a comma, but will leave the originally separate lines unjoined. Then you can use the Tools -> Join command (Ctrl-J) to manually join the lines by pressing Ctrl-J repetitively until all lines are joined. [UPDATE: See EDIT paragraph below]. This, however, will leave a space after each comma so then you have to globally replace ", " with just a comma. EDIT: I just discovered that if you select all the text in Kate, then issue the Ctrl-J, all the separate lines will be joined into one line.

Here's a command line way to do it. cat aTextfile | tr "\n" "," | sed 's/,,/,/g' | sed 's/,$//' >aNewTextfile It first translates all linefeed chars to a comma (which creates one long single line), then converts any instances of two commas in a row to a single comma, and then strips the trailing comma off the last phrase in the line, then writes the output to a new file. Taking your original data, the result is this: something,something else,whatever This can probably be done more elegantly, but this will work (given your spec that there are no more than 2 linefeeds in a row).

Somewhere I seem to recall reading that the tar parameter syntax has been tightened up for the version packaged with Mandriva 2006. The tar documentation is quite clear that the tar archive name parameter comes before the files that the tar is to be created from.

This thread is an eye-opener and makes me think that I've been lucky. I've always built my own boxes, always had 2 HDs and 2 optical drives, always put in extra fans, and ran einstein@home and seti@home (which raised the CPU temperature 5 degrees F, so that's drawing more power), and never had a glitch. However, I never have had a real high end video card either. When I bought the cases, I paid attention to the PSU rating but never really had a clear idea of how much wattage I actually needed. I just always assumed I'd be ok with 350 - 400 watts. I sure will pay more attention to this in the future. I guess the mechanism here is that with the gui running, a spike in power requirements overloads the psu, cpu instructions get garbled, and gui crashes, but the kernel itself and network and other services somehow (by pure random luck?) do not crash. So power requirements then drop but with the kernel itself still functional, the ssh into the box works ok to shut the machine down. Is that what's going on? So for this machine in question that Ix gave us, can anyone think of a way to more directly test the PSU theory other than by process of elimination (memtests, other diagnostics, taxing the gui with power-hungry CPU and disk intensive tasks, swapping out the psu for a higher rated one, etc)?

Some quick thoughts: First: Per excellent IX advice from a past message: "Preparation is the Key." Make a list of the various steps and options you are going to take to try to identify the problem and solve it. Plan your problem-solving action steps. Second: Keep a detailed log of each trouble-shooting thing you try. Your notes may prove handy later on. Action Steps: 1. Read Tom Berger's FAQ: What do I do when my system stops responding?. Also, the article on the Magic SysRq Key. 2. Check logs -> /var/log/messages, Xorg.0.log, etc. Any hints? 3. Run memory checks. 4. Have all upgrades/bug fixes/security fixes etc. been applied? 5. Test hypothesis that the problem is X-related, demonstrate that problem does not occur when operating solely in command line mode. Boot to runlevel 3, operate machine for a day or so in this mode. Make sure you use network - use links or lynx for Internet, ssh into and out, rsync, etc. If no freeze problems, then the working hypothesis that it's X-related is looking good. 6. If machine froze in CLI-only mode, open box and check all data and power connections. Reseat boards, etc. 7. Is it an X-problem or a DM problems. Try some different DMs to see if problem is specific to DM you were using. 8. If machine stable in CLI-only mode and problem does not seem related to DM, try a different video driver. Try VESA as last resort. 9. If different video driver works without freeze re-occuring, either go with that or try playing around with the X config options on the (presumed) ATI driver the owner was using originally.

Two suggestions: 1. Before the upgrade, if you had the Mandriva ATI video driver installed, then boot into Failsafe mode from your lilo or grub menu. This takes you to command line mode as root. Execute the command XFdrake and reconfigure your video driver. Be sure to try the Test feature. Also be sure to select the feature to boot into graphics mode at startup. Then reboot (shutdown -r now). 2. If you had the proprietary ATI driver (downloaded from the ATI website) installed before the upgrade, you will have to try to re-install it. If that doesn't work, you may have to try using the Mandriva ATI driver.

Just now, I was able to access http://devries.mandrivausers.org That link not worked for the last several hours until just a minute ago. So perhaps the update just got propagated to my ISP's DNS servers. Anyway, thanks devries, it's a terrific job.

Hmm, didn't have that problem. I was able to install a new extension (fasterfox), update an existing extension, and delete an old extension I no longer wanted. The cleanest thing is probably to do start with a new profile, but I thought I'd try the lazy way out first. Anyway, I'm very happy to have the new version installed. I like it a lot better.

First of all, I wish to thank everyone for the really excellent suggestions that gave me the info and confidence to do this. I went ahead and installed firefox 1.5 on LE2005, leaving the original 1.0.x Mandriva version in place. I'll try it on 2006 later. So far, everything works fine. Here's what I did: 1. Made a backup of ~/.mozilla (using command: tar cvzf ~/.mozilla) 2. Downloaded the .tar.gz from the Mozilla site and put it in /usr/lib 3. Unpacked the file (tar xvzf firefox-1.5.tar.gz). This created the /usr/lib/firefox directory and contents. 4. I left the original /usr/lib/mozilla-firefox-1.0.2 directory in place. Copied the plugins from the old version to the plugins subdir of the new version. Also copied the nphelix.xpt component from the old components subdir over to the new components subdir (this nphelix.xpt is realplayer-related, since I installed realplayer some time ago). 5. I decided to go ahead and use the original .mozilla home dir and did not create a new profile. 6. In Mandriva, firefox is launched via the /usr/bin/mozilla-firefox script. Made a backup copy of that as mozilla-firefox-OLD. Then created a new mozilla-firefox script, as follows: #!/bin/sh cd /usr/lib/firefox ./firefox 6. Clicked the firefox icon in the panel and everything worked great! So the only thing I changed regarding the old 1.0.x version was the /usr/bin/mozilla-firefox script that invoked it. Instead I pointed this script to execute the new version instead. If for some reason, I have to go back to the original firefox version, all I have to do is restore the backups of the .mozilla home dir and mozilla-firefox script. If everything continues to work fine for a week or so, then I'll update my 2006 installs using the same method. EDIT: I went ahead and did this on 2006 as well and it worked fine.

Thanks, daniewicz. That's a great tip about setting up a new profile with profilemanager. I remember hearing about profilemanager (probably from one of your posts) but it didn't register with me about using that to create a new profile for a new separate installation of a second version of Firefox. Also, I need to correct what I said about downloading and installing the rpm - I really meant the .tar.gz file from the Mozilla site. I would plan to install using that, not an rpm. Your post gives me some confidence that this is feasible, given the ability to create that separate profile.

I'd like to install Firefox 1.5 on 2006 but I'm uncertain what the best way to do that would be. I don't want to remove the default Mandriva 1.0.x version, because as has been pointed out in this thread, that will affect many package dependencies. Several people have reported that they installed Firefox 1.5 on 2006, but how did you do it, specifically? Do you just download the rpm (EDIT: I meant the .tar.gz) from Mozilla and install, while keeping the original Mandriva 1.0.x version? There is only one .mozilla directory in /home, so that would need to be shared between the two versions, right? Does this cause any problems? Has anyone actually removed the default Firefox 1.0.x and then installed 1.5? Did this cause you any problems with other stuff being uninstalled along with it? Any suggestions from those who have actually done this and are familiar with the consequences, or from those who have a clear understanding of how this should be done, are appreciated. Or should adding 1.5 be avoided altogether because of the consequences? If this can be done, please give some clear details on how to do it.

This won't do exactly what you want, but it still may provide some useful info. Using the find command, there is a way to determine which files were last accessed more than x days ago. Since the find command can also apply another command to the results, we can use urpmf to then find what package the file was installed from. For example, if I want to see what files in /usr have not been accessed for at least the past 180 days, I could run the following command which will display the package plus the file name. find /usr -atime +180 -exec urpmf {} \; Example of what the above might output: printer-filters:/usr/share/doc/printer-filters-10.2/AppleStyleWriter/README.troubleshooting printer-filters:/usr/share/doc/printer-filters-10.2/AppleStyleWriter/Makefile.atalk Note: If you use the noatime option in fstab, then the system does not update access time and the above won't work.

I bet your existing urpmi plf sources are for LE2005, not 2006. The xine-plugins-1.1.1-0.1.102plf.i586 package is for LE2005. The correct one for 2006 is xine-plugins-1.1.1-0.1.20060plf.i586.rpm (this uses libiso9660.so.4). Reconfigure urpmi to use 2006-specific repositories for plf-free and plf-nonfree. Use the Easy-Urpmi link at the top of the page to find a plf repository for 2006. Remove your old plf sources first, before adding the new sources. For example: urpmi.removemedia plf-free urpmi.removemedia plf-nonfree Here is an example for one plf source for 2006: urpmi.addmedia plf-free ftp://ftp.free.fr/pub/Distributions_Linux/plf/mandrake/free/2006.0 with ../hdlist.cz urpmi.addmedia plf-nonfree ftp://ftp.free.fr/pub/Distributions_Linux/plf/mandrake/non-free/2006.0 with ../hdlist.cz

Review of 2006.1-0.3 at tuxmachines.org (detailed review) Another review of 2006.1-0.3 at geektimelinux.com (very perfunctory)

This should help: How Lilo Can Boot A Second Distribution

I second arctic's good advice about going for the install rather than an upgrade of something that is now several versions old. There are several posts here about the serious problems people have had trying to upgrade 10.0 or 10.1 to the new 2006 version. For a new install, you might find the following links useful: aRTee's 2006 install: http://www.mandrake.tips.4.free.fr/installmdv2006.html Install slideshow: http://www.tuxpedia.com/chap2.html Howto setup Mandriva 2006 as a server: http://www.howtoforge.com/perfect_setup_mandriva_2006

man-1.5m2-3mdk.i586.rpm (includes the man, apropos, and whatis binaries for 2006) man-pages-2.07-1mdk.noarch.rpm (contains the actual 2006 man pages)

I did a quick search on IBM's Linux site and found it here: Boot Linux Faster

DistroWatch announcement: http://distrowatch.com/?newsid=03143 Mandriva Distribution Changelog: http://qa.mandriva.com/twiki/bin/view/Main/DistroChangelog Mandriva schedule from this (2006.1-0.3) to the eventual 2007 release: http://qa.mandriva.com/twiki/bin/view/Main/MandrivaLinux2007