Steve Scrimpshire

Maybe you have to be root? How about trying fglrxconfig and choose yes to external agp

It's already here. pktcdvd. It's still considered experimental and it makes my 680 MB CDRW only 535 MB when I format it and prepare it for packet writing, but we're getting there.

In Mandrake, through urpmi, fetchmail and fetchmailconf are two different pkgs btw.

I really doubt you forgot to install something. I get the template error, too, but khelpcenter goes on to run fine. I can't testify to the menu item, because i do not use KDE, but man runs completely fine for me from konqueror. I use kde-3.3 though. Can you run konqueror from a console and then run man in it and see if there is an error aside from your ordinary kde/qt errors that one gets every time one launches a QT app? You may also want to try the repair script that's pinned in Tips and Tricks. I happen to know the guy who cobbled it together and he's a great guy.

I'm gonna take a stab at this. I think what you need is fetchmail to fetch mail to your local spool (/var/spool/mail/<<username>>). As far as I know, mutt doesn't fetch, don't know about pine. Mutt can read mail from your local spool, though.

If you're comfortable with the commandline, I say stick with it. To see a list of the files in the package through commandline, as root do rpm -ql nameof.rpm You typically only need the basename, like this: rpm -ivh ncftp-3.1.8-1mdk.i586.rpm installs it rpm -ql ncftp lists the files it installs

Superkaramba will run just fine outside of KDE. You need kde installed though, because it uses the qt libs from KDE. gdesklets is the gtk equivalent and requires most, if not all, of gnome to be installed, but it can run outside of gnome once installed. I'm having no luck with gdesklets running on my 10.1 box lately though. P.S. It's also on the contrib mirrors, so if you use the EasyUrpmi link above and add a contrib source, you can just urpmi superkaramba . No really good themes without following the link from mikeee, though.

Oh, and something else I just noticed: It is more correct to say either test=$(cat backslash.txt) or test=$(<backslash.txt) rather than both together: test=$(cat <backslash.txt)

They are slightly different: http://www.tldp.org/LDP/abs/html/commandsub.html aru or theYinYeti can translate it better than I.

KDE has the ability to 'Run a program as the desktop background', but I've never really checked into it thoroughly, since I don't use KDE. Maybe that'll wake some KDE users up to help you.

To be clear, the 'cat' way could be done line by line, as well: #!/bin/bash test="$(cat <backslash.txt)" for line in $test do <<do something with $line here making sure it has "doublequotes" around it>> done

I'm not 100% sure of what you are doing or how you are managing it, but if you cat the file in, the \ remain intact: backslash.txt: \test \\test \\40 \\\3 \13 backslash.sh: #!/bin/bash test="$(cat <backslash.txt)" echo "$test" output: \test \\test \\40 \\\3 \13 I am but a lowly bash apprentice...aru or theYinYeti will come along and fix everything.

Should just need php-xml. It's on your disks.

I have no idea why it would work the second time and not the first. But it is a Beta distro you're working with :P. My only thought is that maybe you ran the installer as regular user the first time. :shrug: Edit: To clarify. Are you saying that 2.6.11.* does not need a patch with the latest nvidia driver? It works out of the box?

What if I have more than one screen session running?: I can do screen -D -R 19255 to attach to the second session...to attach to the first: screen -D -R 5439 You may find it useful to give your screen sessions meaningful names if you want to have more than one running at a time: screen -S first screen -S second would've created in my first example: I could then do either screen -D -R 5439 or screen -D -R first to attach to the first one. Next we will discuss the -X switch. More fun.

:D Don't give away all my secrets :D

I think you really should grab disk 3 also. disk3: 029f660c78e29427f775a54284fb7085

http://www.pc-tools.net/win32/md5sums/ Download an md5sum tool for windows and run it against your ISOs. Disk 1 should be: 7833f17c3fbe95581c48cf3848792d21 Disk 2 should be: 5850545e8fa3f63323a90b1403ec5064

On your download edition there should be 3 disks. Did you check the md5sums on the disks? It sounds like not everything got set up right.

Well, apparently, the cgi chat server is down. If your internet connection works in linux, it would be great if we could get you hooked up with a console-based irc client like irssi and we could chat in irc while you are actually in linux. If you're up for trying that (and internet works in linux) I can give you a link to download irssi and instructions on how to get into the channel.

Try this: cd /mnt/win_c/windows/Profiles/Angela/desktop urpmi kernel-source-2.6<<hit the tab button to finish filling in the name and then hit enter>> It sounds like your urpmi sources are not pointing to your one CD or the CD is missing some files. Did you download that file to your desktop in windows or something? Anyway, the above should work. The 'grep cdrom /etc/fstab' was so that you could see what the mountpoint is for your cdrom, but since, apparently you have the file you need downloaded to your windows desktop it is not that important at the moment. P.S. If you want, you can click the chat link up there (upper right) and I can help you one on one in IRC. I'm "Ohms" in there.

Ah. In KDE, right-click the clock. Choose Date/time format. Click the date/time tab (I think). In the dropdown menu for Short Date, add WEEKDAY in front of it and click Apply, then OK. Then log out and back in.

The kernel-source RPM is on Disk 1. Try just doing urpmi kernel-source-2.6 The other error you get about "Error parsing config file" is because there is something wrong with the /etc/X11/xorg.conf file. Probably there is a syntax error in it from hand-editing it. It should give you a hint as to what is wrong in the error, including maybe a line number.

I have no idea how it keeps running doing it that way, but your regular user can run it using screen.

Install screen on the workstation. Then ssh into workstation start screen start your batch job hit Ctrl-a d logout of ssh Your job will contnue to run. More about screen here: http://mandrakeusers.org/index.php?showtopic=23247