public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: kemas <k_henry@ramayana.co.id>
To: Tarquin Adams <Tarquin.Adams@rhsh.co.uk>
Cc: linux-msdos@vger.kernel.org
Subject: Re: cifs 1.50 and dosemu 1.4 great combination
Date: Wed, 21 Nov 2007 11:04:18 +0700	[thread overview]
Message-ID: <4743AE42.20700@ramayana.co.id> (raw)
In-Reply-To: <70AFCDD624131E4F8E093DF91AA2CBA225B2D5@SERVER.STOKE01.local>

Tarquin Adams wrote:
> Claudia, thank you for your response.
>
> I think I have now identified the cause of my problem.  When a user creates a file in dosemu, the permissions are set as 'read and write' for that user but 'read only' for their group and all other users.  Hence when my software tries to access a .pre file to append data to, it finds it is 'read only' for any user other than the first one to have run the software.
>
> How can I force all files created in dosemu to be 'read and write' for all users?
>
> Regards,
> Tarquin Adams
>
>   
Hi Tarquin,

if you want to force every file newly created by them to have access 
mode read write for user and group, you have to change the default umask.
I use CentOS, so I've change in /etc/bashrc
    if [ $UID -gt 99 ] && [ "`id -gn`" = "`id -un`" ]; then
        umask 002
    else
        umask 022  --> this one change to 002
    fi






  reply	other threads:[~2007-11-21  4:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 10:26 Re: cifs 1.50 and dosemu 1.4 great combination Tarquin Adams
2007-11-21  4:04 ` kemas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-14 14:39 Tarquin Adams
2007-11-14 16:03 ` Claudia Neumann
2007-10-11 14:30 kemas
     [not found] ` <470E52D1.5040406@pobox.com>
     [not found]   ` <1192159242.2490.10.camel@localhost>
2007-10-12  5:31     ` Alain M.
2007-10-12  6:19       ` Bart Oldeman
2007-10-12 11:58       ` Claudia Neumann
2007-10-15  3:23       ` kemas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4743AE42.20700@ramayana.co.id \
    --to=k_henry@ramayana.co.id \
    --cc=Tarquin.Adams@rhsh.co.uk \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox