Steve Scrimpshire

According to this, it looks like this device is supported by SANE (for scanning). You need to install a front-end package along with libsane. I would suggest Xsane and/or Gimp for scanning. As for printing in color, you really shouldn't have a problem with it. It should print in color by default, but I would check the configuration (or buttons) of the printer itself.

The content is great. Very thorough. I would make a small suggestion. I would move the "Warnings" section to the top of the article, right after the title and sub-title, to encourage it being read before attempting anything.

You're welcome. A lot of the credit goes to aru. I just basically took his commands and turned them into a bash script.

You've tried replacing the second one? How about both? kwin --replace && sh -c "cd ~/.Games/TitanAttacks && javaws titanattacks.jnlp" && compiz --replace &

I've updated this script to not throw an error if your installation is not missing any files. I've attached the update script to this post. repair.zip

shouldn't this be: Modify your LD_LIBRARY_PATH environment variable to contain the full path to the lib/<ARCH> directory. For example, on 32-bit Linux: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/myhome/j3d/lib/i386 ?

I'm not in Linux right now, but if I remember correctly, on Mandriva you would add that path to the /etc/ld.so.config file and then run ldconfig

Or maybe: find . -name " - *.mp3" -exec sh -c 'mv ${0} "${0//\ \-\ / }"' {} \;

Possibly...it could be your use of double quotes instead of single quotes, using the = instead of -eq, etc. Sorry, I forgot to look yesterday. Not sure you need the "" around the "$(wmctrl...". I think the case problem and the = sign did the trick...you might, though. What we really should do is grep -i gnumeric which makes the grep case-insensitive, in case they change it. Then I think you're good. Let me know if you do need the "" around "$(wmctrl..." and let me know if you need double instead of single quotes and all that. I guess my bash is rusty.

When I get home today, I will check the syntax. It may be that you left off a space or I just missed a little something.

I'm not at my linux box at the moment, but you might try something similar to this: wmctrl -s2 gnumeric filename1 & while [ $(wmctrl -l | grep gnumeric) -eq '' ] do sleep done wmctrl -s3 kpdf filename2 &

Sorry about that. I lost a closing }. Add } on the very last line...you'll see I edited my post above to fix it.

Ack. It's not the same command any more. You can copy this text to a file: #!/usr/bin/perl -w # rename - Larry's filename fixer $op = shift or die "Usage: rename expr [files]\n"; chomp(@ARGV = <STDIN>) unless @ARGV; for (@ARGV) { $was = $_; eval $op; die $@ if $@; rename($was,$_) unless $was eq $_; } And name it rename.pl, put it in your /usr/bin directory and chmod +x /usr/bin/rename.pl Then you can do: rename.pl 's/[0-9]+-//g' *

There aren't a lot of examples, but I found one: http://tips.webdesign10.com/how-to-bulk-re...in-the-terminal Remove all underscores: rename -v 's/_/ /g' *.JPG Remove the numbers (and the dash): 01-test_rename_a 02-test_rename_b 03-test_rename_c rename -v 's/[0-9]+-//g' * If you want to remove the test_ part, too: rename -v 's/[0-9]+-test_//g' * I've been studying regexes for years and I still have a very limited understanding of them: http://www.cs.tut.fi/~jkorpela/perl/regexp.html

mandri, That's pretty close to being exactly correct. The * is telling it to do this for all files in the directory. The "%%20" is the string to replace and " " is what to replace it with. " " is not exactly nothing, though. It's a space. The command is renaming all files that contain %%20, by using what they're named already, but replacing %%20 with a space. like%%20this becomes like this and%%20like%%20this becomes and like this

Yeah, I voted perfectly fine, but IIRC, I did try to visit there once before and it was way too dark for me to hang around.

Here's something you might find useful: http://mr337.thecoderblogs.com/archives/7

Pardon my ignorance, but what does this mean?

To answer your other question: Yes, the new kernel will just be a couple of files and as long as you don't overwrite your old kernel (just name your new one something different) and still have all of them as choices in your menu.lst or lilo.conf you will be able to boot an old kernel if it goes splat.

Glad we could help.

I voted Mix of Mandriva and non-Mandriva systems even though, at the moment, the only Linux I have installed is Mandriva on my desktop and I dual-boot Windows XP (work and school) and Mandriva. I go back and forth between Ubuntu, Knoppix, Kanotix and Mandriva, but you probably have an 80% chance of catching me with just Mandriva and XP installed.

I would like to see tyme in a dress. No, for real...I know there's an HCL, but it would be nice if we had a user-contributable list of specific hardware and whether or not it works with Linux and what they had to do to get it to work with whatever distro.

scarecrow: I can accept that explanation...sorta. But, I had burned on the exact same media before (I still had some left in the pack after 2 or 3 years...I didn't burn very much).

Who was angry? :P

I like the concept, but you will probably run into the same problems tyme did. He didn't have regular enough contributors, which you must have at the beginning to attract more people to contribute, which keeps the fuel burning to attract more contributors until it is self-supporting. I attempted to contribute as much as I could to tyme's Geeklog, but I had some personal issues that needed my attention and he/we only had two or three other contributors that also were not that easily available (I miss LZ :sad: ).