Permission for folder created during rtems_fsmount

ali nasir supremenasir at yahoo.com
Tue Jan 17 09:24:22 UTC 2012


Hi,

The flash directory is created automatically by the rtems_fsmount. This is done when we call the rtems_fsmount to mount the RFS on the flash device. 

Is there a way to change the default mask from 022 to something which we desire?

Regards,
Ali


------------------------------
On Tue, Jan 17, 2012 2:46 PM IST Sebastian Huber wrote:

>The default umask is 022.  This corresponds perfectly to the permissions below 
>"/mnt" and "ram".  Please have a look at
>
>http://pubs.opengroup.org/onlinepubs/009695399/functions/umask.html
>
>How do you create the "flash" directory?
>
>On 01/17/2012 10:02 AM, ali nasir wrote:
>>
>> Hi,
>> Below is the permissions of the '/mnt' and 'ram' for RTEMS4.10
>> # ls -l
>> total 0
>> drwxr-xr-x  1 root  root  2992 Jan  1  1988 dev
>> drwxr-xr-x  1 root  root  1088 Jan 17 12:09 etc
>> drwxr-xr-x  1 root  root   544 Jan 17 12:09 mnt
>> #
>>
>> # cd mnt
>> [/mnt] # ls -l
>> total 1
>> drwx--x--x  0 root  root  512 Nov 22 14:01 flash
>> drwxr-xr-x  1 root  root  272 Jan 17 12:09 ram
>> [/mnt] #
>>
>> Is it that because the /mnt does not have 'w' set for group and other, the 'ram' also does not have 'w' for group and others? How do i give 'w' rights to all (apart from using chmod after mounting the ram)? I  now see that flash does not even have 'r' for the group and others.
>>
>> Regards,
>> Ali
>>
>> ------------------------------
>> On Tue, Jan 17, 2012 1:51 PM IST Sebastian Huber wrote:
>>
>> On 01/17/2012 09:01 AM, ali nasir wrote:
>>>
>>> Hi,
>>>
>>> We observed a change in the permissions of folders created during rtems_fsmount between the RTEMS4.9 and RTEMS4.10.
>>> When we mount the ramdisk on the 4.9 on path /mnt/ram, this directory has rwx permissions for all. But with the 4.10 the rwx permissions are only granted to the root. We use the RFS on the ramdisk.
>>>
>>> We see that a build function is introduced in the 4.10 and it plays with the permissions before calling the mknod function. Is the above behavior the desired behavior or it is a problem? What do we do so that the rwx permissions are given to everyone? We know that calling chmod just after mounting will solve this. But is there another way out?
>>
>> Which permissions do the "/mnt" and "ram" have?  Please have a look at
>>
>> http://pubs.opengroup.org/onlinepubs/009695399/functions/umask.html
>>
>> --
>> Sebastian Huber, embedded brains GmbH
>>
>> Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
>> Phone   : +49 89 18 90 80 79-6
>> Fax     : +49 89 18 90 80 79-9
>> E-Mail  : sebastian.huber at embedded-brains.de
>> PGP     : Public key available on request.
>>
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-users
>>
>
>
>-- 
>Sebastian Huber, embedded brains GmbH
>
>Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
>Phone   : +49 89 18 90 80 79-6
>Fax     : +49 89 18 90 80 79-9
>E-Mail  : sebastian.huber at embedded-brains.de
>PGP     : Public key available on request.
>
>Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.





More information about the users mailing list