pmpatrick

You shouldn't unless you just enjoy tinkering; it's not worth your time if you rarely use the feature. But fish is something I think many people would find useful if they knew about it. It's just not real accessible but it's a very nice feature on any home network where you need to transfer files between two kde boxes. It sure beats setting up NFS or samba shares. Once you learn how to use fish, it's no big deal. However, there is just so much in kde/konqueror, it's very hard to get a handle on all of it and see what may be useful and what you don't like or have no use for. That's the main problem with konqueror if you can call that a problem - there's so much functionality built into it, that it's hard to discover what might be a very useful feature for you.

Usually, you have to edit /etc/ssh/ssh_config not sshd_config. Post ssh_config. By the way, my sshd_config has Port 22 commented as well and works fine.

A couple of things for mdv 2006: 1. Do all the updates as there were a lot of bug fixes early on with this release; 2. Uninstall the application known as "kat". It is installed and turned on by default in mdv2006 and known to be very bugy. To do that the most direct way, open a konsole and run: $ su <enter root password> # urpme kat

./f-prot / -silent -report=/home/****/virusscan The "./" in front of f-prot indicates to me that f-prot is not in PATH. To run that command you would have to cd to the directory where f-prot resides and then run that command, i.e.: cd <full path to f-prot directory> && ./f-prot / -silent -report=/home/****/virusscan

I agree. All of the above, especially fish, are terrific features. Fish allows for very efficient, secure file transfers without having to set up a formal samba or NFS network. But this is really a kde feature as you can use fish with any kde app and kde services must be running on all boxes on the local network for it to work network wide. However, konqueror integrates all these features very nicely. If you never or rarely need or use these services, then konqueror is probably overkill; it's just not worth the time investment in learning and configuring konqueror for something rarely used.

Post which mandriva version you installed. You need all three install cds when doing the installation. You can do a very basic installation with just cd-1 but you will get the type of problems you are experiencing if you do.

According to this: http://www.mandriva.com/security/productlifetime Mandriva stopped supporting 10.2(LE2005) on July 13, 2006. I'd say it's time for an upgrade. I'm using 10.2 myself for my main OS and haven't seen a security update for months although I've picked up several for mdv2006 which I have installed on a "test" partition. I almost have mdv2006 stable now but it was a real pain to get it that way. It was terrible on my desktop hardware but worked great on my daughter's acer centrino laptop. I'm sure I'll be installing 2007 on another test partition as soon as it comes out; I always do.

Post your output for: $ ls -l /mnt

I guess I misinterpreted this: which seems to imply that GTK which is licensed under the LGPL is somehow truer to open source ideals than QT which is licensed under the GPL. However, since 1999, RSM has called for libraries to be licensed under the GPL instead of the LGPL: http://www.gnu.org/licenses/why-not-lgpl.html You also failed to point out that you can with GTK without paying any fee, leaving the implication that you could only develop proprietary apps with QT, not GTK. I don't mean to nitpick, but there is a long history here of flamewars with kde supporters claiming that gnome supporters misrepresent the nature of kde licensing and gnomers claiming to be more open source friendly than kde/QT. As it currently stands, that is simply not the case. QT is currently licensed under the preferred GPL and encourages the production of GPL software by requiring a fee only from those wishing to use QT on non-GPL projects. Given the contentious history on this subject, greater care and precision is needed in describing the licensing differences between QT and GTK. As with any controversial subject, wikipedia is not the best place to go for info.

tyme, I think you are wrong. Gtk is licensed under the LGPL. With that license you are free to use the library for both non-GPL and GPL applications without paying any fee. QT is licensed under the GPL, same as the linux kernel. If you use QT, the app must also be licensed under th GPL. However, if you want to make a proprietary app with QT, the owner is willing to give you a commercial QT license for a fee. Open source developers with commercial aspirations for their software prefer Gtk and the LGPL for obvious reasons - it allows them to fork off a commercial version without having to pay any fee. The main technical difference is QT is C++ based and Gtk is C based. A lot of open source developers are more comfortable in C than C++.

They look pretty unimpressive to me but at least they are off of that blue background thing they've been stuck on since mdk 8.2. That penguin with the long beak is getting pretty old too. I know the first thing that everyone does with mandriva is change the wallpaper but more effort should go into ceating something special for the default wallpaper. I think it really makes a difference on how the distro is perceived, especially by newbies. If the default theme looks amateurish, then the distro appears amateurish.

Re ramfree's question on why mounted: The method I gave is for wiping only the free space on the partition, leaving the data on the partition intact. It just fills up the empty space on the partition with random junk, deletes it, fills it up with zeroes and deletes it. Whether this is effective with a journalled filesystem, I can't say. You could adopt the same method to wipe the entire partition: # dd if=/dev/urandom of=/dev/hda1 # dd if=/dev/zero of=/dev/hda1 or the entire drive: # dd if=/dev/urandom of=/dev/hda # dd if=/dev/zero of=/dev/hda In either of these cases, the partition/drive would not be mounted. If you just want to cleanup the free space on the partition, however, I think you would have to mount the partition to create and write a file on the partition which will occupy all the free space and then delete it.

Check out this hysterical bit of satire: http://www.bbspot.com/News/2006/08/paris-h...bell-linux.html

Try this for your dvd fstab entry: /dev/hdc /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0

I can think of ways to do it from the command line. Depending on how thorough you want to be, and assumming the mount point of the partition you want to have the free space cleaned on is /mnt/hda1, you could run as root with the partitiion mounted: # dd if=/dev/urandom of=/mnt/hda1/cleanup # sync # rm -f /mnt/hda1/cleanup # sync # dd if=/dev/zero of=/mnt/hda1/cleanup # sync # rm -f /mnt/hda1/cleanup #sync What this should do is fill up all the free space on the partition with random data, delete it, fill up that space with zeroes and delete it again. This will clean things up pretty securely, but the main caveat is with journalling filesystems like reiserfs or ext3, there may still be recoverable info about what was on the drive prior to deletion.

It's not sdbl using the letter "l", it's sdb1 using the number "1". You were suppose to run as root: # mount -t vfat /dev/sdb1 /mnt/portable

It's the winrar program. Winrar automatically associates all iso files with itself as winrar is capable of mounting and reading an iso file. You can change this default behaviour in winrar or just ignore it and burn the iso file as an image. It is not a winrar archive.

The latest nvidia driver, 1.0-8774, is now available for download and it's supposed to be compatible with xorg 7.1 for all those that like running on the bleeding edge. You can download here: http://www.nvidia.com/object/unix.html

I believe 9.1 was the last version that had a kernel image and initrd that were small enough to allow making a boot floppy without going through a lot of hassles. That's probably why you are getting the error message. You can do a regular install and then easily make a boot cd by running as root: # /sbin/mkrescue --iso That will automatically generate an iso named rescue.iso which you can burn to make a boot cd. See man mkrescue for more details. Also, as noted above, a fresh install will work better. There were a lot of changes from 9.2 to 10.1(devfs to udev; kernel 2.4 to 2.6, etc).

Ubuntu always gets a lot of press. They are very well funded and have an excellent PR department. Most distros don't have that kind of financial backing or PR expertise. I just don't see ubuntu doing anything all that interesting technically that isn't being done in many other distros as well or better. It's a nice distro if you like gnome but nothing special. What surprised me is how far mandriva has fallen in these types of polls. They used to be always on top but now they are lucky to be fourth place also rans. It's kind of sad really. From a business standpoint, the enterprise server market is all that seems to count as that's the only area where businesses seem to be able to make money with linux. Mandriva was never able to break into that market despite years of dominance in these user polls. Perhaps ubuntu will fare better; they certainly seem better managed and much better at marketing. I guess time will tell. I can guarantee you one thing - if ubuntu doesn't eventually make money in the enterprise server market, it too will eventually fade just like mandriva. I don't think Shuttleworth will dump money into this project forever if there proves to be no prospect of making a profit in the enterprise server market.

In the command I gave you there should be no space between the "&" and the ">", i.e., $ amarok &> error.txt That will ouput and redirect to your errror.txt file both the standard error, 2, and the standard output, 1. Redirecting only the standard error to the file like you did should be fine, however. The error messages may indicate that amarok is trying to scan a directory/partition that no longer exists or is no longer mounted like an mp3 player but that shouldn't bring down your entire system. You can try running amarok with a fresh set of configuration info. Most of that stuff is contained in a hidden directory in your home directory, .kde/share/apps/amarok and the file, .kde/share/config/amarokrc. Go into konqueror and in "View" tick the "Show Hidden Files" menu entry then you will be able to see the .kde directory. Just rename .kde/share/apps/amarok to amarok.old and .kde/share/config/amarokrc to amarokrc.old. The next time you start amarok, it will automatically generate new configuration files and run like the first time you opened the app.

Try launching it from a console and see if you can catch some error messages before it goes down: $ amarok &>error.txt should launch amarok and output and save any error messages to a text file in your home directory called "error.txt". Hopefully it will have time to do this before it goes down and you will have something to go on in error.txt for understanding what is happenning.

DesktopLinux.com is conducting its annual desktop linux survey here: http://www.desktoplinux.com/cgi-bin/survey...d=0821200617613 Anyone intersted should feel free to go and vote for their favorite distro, browser, DE, ect.

The easiest way to copy a dvd and have it be bootable is to place the DVD in your drive, open k3b and go into Tools>DVD>Copy DVD. In the popup window that comes up, note where the image file will be stored and tick the "Only create image" box. That will make an iso of your DVD. From that iso image file, you should be able to burn as many cds as you want and they should be bootable. The way you are trying won't work. For a cd or dvd to be bootable certain information must appear at very specific block locations on the disk. You can't just copy the data over as that block location will not be preserved. The iso image that k3b creates should be a block by block exact replica of the original dvd and when you burn it, you should get an identical block by block copy of the original dvd which should be bootable.

Also, when using ndiswrapper, WEP 128bit won't work for certain cards whereas WEP 64bit seems to work well for most. Finally, I think that card has a native linux driver available; if so you wouldn't need to use ndiswrapper. Something to investigate if you can't get it going. I suspect disabling WEP will get it working and WEP 64bit will probably work as well.