gcmd-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gcmd-dev] relative unix-like device root


From: Micha
Subject: [gcmd-dev] relative unix-like device root
Date: Sat, 16 Dec 2006 12:35:08 +0100
User-agent: Alpenglühn 7.2

I changed the subject since this is no more a python issue.

What i think it does is, writing a file 'foo.md5sum' to the other (inactive) 
cwd,
but if that's a 'rooted' device, it writes to path // and that's just the unix 
filesystem 
root /, where user have no write access. It's a plain bug anyway.

I already noted that in the device manager, putting '-fin > /dev/null && cd' 
instead 
of a real device name, the device buttons (icon) allow to switch to any 
directory 
even if it's no device, skipping the mount attempt and any error message.
This is recently not possible in any other way, with gcmd onboard resources.

However, even this 'cd', when done from the device module, leads to gcmd 
setting 
up absolute 'device' root. (No '..' entry available).

md5sum plugin works in ~ (location list 'Home' ) which is the only location 
where gcmd preserves the '..' entry in the file list, indicating it's not 
treated 
as different device root, although /home is a sperate device on this box. 

The only only-losely-related attempt of a fix i can find is

2006-03-08  Assaf Gordon  <address@hidden>

        * src/gnome-cmd-con-device.c:
        * src/gnome-cmd-data.c:
        * src/gnome-cmd-options-dialog.c:
        Fixed the VFS auto volume mounting.


... Looks like old bugs are new bugs ;)



 m°





reply via email to

[Prev in Thread] Current Thread [Next in Thread]