[[Template core/front/global/updateWarning is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]
The old forums are being retired in favour of a more modern (free) community platform.
These forums will remain accessible as a read only archive for the time being.
I'd really like to have a decent DC++ client on Linux... Porting ApexDC++ to Linux sounds like an ambitious task -- at least there is a working linuxdc++ now as a starting point...
Actually, I might be able to help a bit -- but time is rare... My knowledge of DC++ internals is also very limited...
EDIT: Maybe those FILE_SHARE Blah and junk relate to this somehow? MO_IRUSR|MO_IWUSR|MO_IRGRP|MO_IROTH
GENERIC_READ and GENERIC_WRITE are equivalent to O_RDONLY, O_WRONLY, O_RDRW access modes.
that FILE_SHARE_* junk is used to specify whether the file may be read/written/deleted by other handles. AFAIK sharing is enabled by default on Linux systems.
MO_IRUSR|MO_IWUSR|MO_IRGRP|MO_IROTH <-- these are for specifying permissions when creating files
Linux Project Development
in Client Discussion
Posted
I'd really like to have a decent DC++ client on Linux... Porting ApexDC++ to Linux sounds like an ambitious task -- at least there is a working linuxdc++ now as a starting point...
Actually, I might be able to help a bit -- but time is rare... My knowledge of DC++ internals is also very limited...
GENERIC_READ and GENERIC_WRITE are equivalent to O_RDONLY, O_WRONLY, O_RDRW access modes.
that FILE_SHARE_* junk is used to specify whether the file may be read/written/deleted by other handles. AFAIK sharing is enabled by default on Linux systems.
MO_IRUSR|MO_IWUSR|MO_IRGRP|MO_IROTH <-- these are for specifying permissions when creating files
(correct me if I'm wrong)
hope this helps...