Mail Archives: djgpp/2002/05/23/15:00:05
In article <aci50u$5ep$1 AT antares DOT lu DOT erisoft DOT se>, Martin Stromberg wrote:
> Bart Oldeman (enbeo AT pg5 DOT enm DOT bris DOT ac DOT uk) wrote:
>: However, DOSEMU uses a certain mapping between DOS and Unix file
>: attributes/permissions:
>
>: DOS attribute UNIX
>: read-only <->not writable (1)
>: archive <->not executable (2)
>: hidden <- filename starts with a dot and is not '..' (3)
>
>: Don't ask me why this is so, I don't know.
>
> samba is doing similar things. I think it's because if you want to
> have DOZE specific attributes you have to have somewhere to put them.
>
> May I suggest that you only use one of the x bits to record the a bit.
We already do so (S_IEXEC == 00100 == user x bit).
>: Maybe rule (2) should be ignored for directories.
>
> That's a possible solution. But you might consider looking up the
> samba way.
Samba has "map archive = yes" mapping the user x bit to the archive
attribute (without a "NOT", so it's reversed wrt DOSEMU)
it can also do similar tricks for system and hidden files
(group and world x bits).
Samba does not appear to do any such mapping for directories and
always forces the "archive", "system" and "hidden" attributes
off for directories, unless (for hidden) their name starts
with a . in Unix.
Indeed it might be a good idea to make DOSEMU archive mappings
compatible with Samba, including the ability to configure in
dosemu.conf.
Sorry for becoming a little off-topic here.
Bart
- Raw text -