I've got a 250GB Ext3 formatted external Harddrive that I use for storing most of my files, including most of stuff I get off of bittorrent. Problem is that when I try to import files from this harddrive Ktorrent returns this error:

Code: Select all

You can only select local files

I may be wrong, but isn't an external harddrive connected directly to a computer supposed to count as local storage? Is this a problem on my end or has it just not been incorporated into Ktorrent yet?

Jeffery Mewtamer wrote:I've got a 250GB Ext3 formatted external Harddrive that I use for storing most of my files, including most of stuff I get off of bittorrent. Problem is that when I try to import files from this harddrive Ktorrent returns this error:

Code: Select all

You can only select local files

I may be wrong, but isn't an external harddrive connected directly to a computer supposed to count as local storage? Is this a problem on my end or has it just not been incorporated into Ktorrent yet?

What version are you running ? I see no reason why this should be any different with a local filesystem, once it is mounted, it is mounted and it should work.

Ktorrent 1.2 installed from Dapper Drake repositories. Drive properly mounted with read access to all users on all files.

To me it sounds like the ioslave problem. Have you mounted and access it via /mn/whatever or through the system:/ or media:/ ioslave? For some reason, they don't register as local.

Unmounted from media
Created mount point under mnt
mounted under mnt
problem solved

Thank you Knut.

Personally I think the whole media:/ ioslave ting is a big design flaw, and it creates more problems and inconsistencies than it solves. But that's only my humble opinion:-)

I had the same error with k3b some time ago, it supposedly fixed with a workaround now(I haven't tried). George, if you think it's worth the bother and are interested, I think the workaround for k3b was introduced in 0.12.6 or 0.12.9 or thereabout.

Knut wrote:Personally I think the whole media:/ ioslave ting is a big design flaw, and it creates more problems and inconsistencies than it solves. But that's only my humble opinion:-)

I had the same error with k3b some time ago, it supposedly fixed with a workaround now(I haven't tried). George, if you think it's worth the bother and are interested, I think the workaround for k3b was introduced in 0.12.6 or 0.12.9 or thereabout.

It depends I'm not gonna rewrite all filehandling code just to make KT work with the media ioslave. If the workaround is a way to get the real path of the file instead of the media:/ path, I can put it in.