LinuxQuestions.org - Permission

- Linux - General (http://www.linuxquestions.org/questions/linux-general-1/)

- - Permission - Folder vs. File (http://www.linuxquestions.org/questions/linux-general-1/permission-folder-vs-file-405427/)

Permission - Folder vs. File

Hello,

I was wondering if it is possible to create folders with default permissions of 0755. And, file permissions with 0744. Is this possible?

I know that I can use UMASK 007. However, this will create ALL files/folders with the permission of 0770.

Thanks for your help!

P.S.
I am not using Samba. Just SSH.

Quote:

I know that I can use UMASK 007. However, this will create ALL files/folders with the permission of 0770

The above is incorrect. The umask setting is applied as a MASK to default permissions, not as an OVERRIDE of these permissions.
Example:

Code:

$ umask 022

$ >testfile

$ mkdir testdir

$ ls -l | grep test

drwxr-xr-x  2 haertig haertig   1024 2006-01-19 12:22 testdir

-rw-r--r--  1 haertig haertig      0 2006-01-19 12:22 testfile

$

By default, files are not created as executable, and that's why the file permission above came out as 644 rather than 755.

Also umask is a genefral mask, whereas dmask and fmask are masks for directories and files respectively.

Thanks for your help!

Quote:

Originally Posted by linmix

Also umask is a genefral mask, whereas dmask and fmask are masks for directories and files respectively.

Gack! I've been writing programs on Unix systems since about, well, when time(2) used to return zero! And I've never heard of fmask or dmask. You never quit learning...

Quote:

Originally Posted by haertig

Gack! I've been writing programs on Unix systems since about, well, when time(2) used to return zero! And I've never heard of fmask or dmask. You never quit learning...

Neither has any of the Linux installations I can lay
my hands on at the moment, or Solaris? Where do
you find dmask/fmask? :)

Cheers,
Tink

I read up on mount (man page) and found info on dmask and fmask for inclusion in fstab. Maybe it's a builtin command? Haven't looked if it exists as seperate binary and am not at my linux box right now.

Quote:

Originally Posted by linmix

I see... well, those are mount options for FAT file-sytems,
have *nothing* to do with linux file-system creation masks.

Cheers,
Tink

Sorry. I guess that's the risk of answering a post when you have no access to a linux box. I expected that since it works for mount options there would be a binary as well, but it appears I was wrong: umask is a bash builtin command, dmask and fmask only apply to mount options.

Anyway, to get back to the topic at hand, I guess default file and directory permissions are set in a config file somewhere, so if you locate that the question would be answred, right? Does anyone know?

The common place (for the system default umask) is
/etc/profile - may (of course) vary with distribution,
and no, it's a script, not a config-file.

Cheers,
Tink

Code:

]$ cat /etc/profile

# /etc/profile



# System wide environment and startup programs, for login setup

# Functions and aliases go in /etc/bashrc



pathmunge () {

        if ! echo $PATH | /bin/egrep -q "(^|:)$1($|:)" ; then

           if [ "$2" = "after" ] ; then

              PATH=$PATH:$1

           else

              PATH=$1:$PATH

           fi

        fi

}



# Path manipulation

if [ $EUID = 0 ]; then

        pathmunge /sbin

        pathmunge /usr/sbin

        pathmunge /usr/local/sbin

fi



pathmunge /usr/X11R6/bin after





# No core files by default

ulimit -S -c 0 > /dev/null 2>&1



USER="`id -un`"

LOGNAME=$USER

MAIL="/var/spool/mail/$USER"



HOSTNAME=`/bin/hostname`

HISTSIZE=1000



if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ]; then

    INPUTRC=/etc/inputrc

fi



export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC



for i in /etc/profile.d/*.sh ; do

    if [ -r "$i" ]; then

        . $i

    fi

done



unset i

unset pathmunge

Where's the bit about standard file and directory permission settings?
Probably different in Fedora then..

As I said - it can vary;

Mine is here:

Code:

# /etc/profile: This file contains system-wide defaults used by

# all Bourne (and related) shells.



# Set the values for some environment variables:

export MINICOM="-c on"

export MANPATH=/usr/local/man:/usr/man:/usr/X11R6/man

export HOSTNAME="`cat /etc/HOSTNAME`"

export LESSOPEN="|lesspipe.sh %s"

export LESS="-M"



# If the user doesn't have a .inputrc, use the one in /etc.

if [ ! -r "$HOME/.inputrc" ]; then

  export INPUTRC=/etc/inputrc

fi



# Set the default system $PATH:

PATH="/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games"



# For root users, ensure that /usr/local/sbin, /usr/sbin, and /sbin are in

# the $PATH.  Some means of connection don't add these by default (sshd comes

# to mind).

if [ "`id -u`" = "0" ]; then

  echo $PATH | grep /usr/local/sbin 1> /dev/null 2> /dev/null

  if [ ! $? = 0 ]; then

    PATH=/usr/local/sbin:/usr/sbin:/sbin:$PATH

  fi

fi



# I had problems using 'eval tset' instead of 'TERM=', but you might want to 

# try it anyway. I think with the right /etc/termcap it would work great.

# eval `tset -sQ "$TERM"`

if [ "$TERM" = "" -o "$TERM" = "unknown" ]; then

 TERM=linux

fi



# Set ksh93 visual editing mode:

if [ "$SHELL" = "/bin/ksh" ]; then

  VISUAL=emacs

#  VISUAL=gmacs

#  VISUAL=vi

fi



# Set a default shell prompt:

#PS1='`hostname`:`pwd`# '

if [ "$SHELL" = "/bin/pdksh" ]; then

 PS1='! $ '

elif [ "$SHELL" = "/bin/ksh" ]; then

 PS1='! ${PWD/#$HOME/~}$ '

elif [ "$SHELL" = "/bin/zsh" ]; then

 PS1='%n@%m:%~%# '

elif [ "$SHELL" = "/bin/ash" ]; then

 PS1='$ '

else

 PS1='\u@\h:\w\$ '

fi

PS2='> '

export PATH DISPLAY LESS TERM PS1 PS2



# Default umask.  A umask of 022 prevents new files from being created group

# and world writable.

umask 022



# Set up the LS_COLORS and LS_OPTIONS environment variables for color ls:

if [ "$SHELL" = "/bin/zsh" ]; then

 eval `dircolors -z`

elif [ "$SHELL" = "/bin/ash" ]; then

 eval `dircolors -s`

else

 eval `dircolors -b`

fi



# Notify user of incoming mail.  This can be overridden in the user's

# local startup file (~/.bash.login or whatever, depending on the shell)

if [ -x /usr/bin/biff ]; then

 biff y

fi



# Append any additional sh scripts found in /etc/profile.d/:

for file in /etc/profile.d/*.sh ; do

  if [ -x $file ]; then

    . $file

  fi

done



# For non-root users, add the current directory to the search path:

if [ ! "`id -u`" = "0" ]; then

 PATH="$PATH:."

 ulimit -u 512

fi

Cheers,
Tink

This is one of the few things that occasionally makes want to scream. I know each distro developer blieves he/she has a very good reason for doing things diferently, but the disparity in config files and scripts between distros - not in content, but in location - can be quite annoying at times.

I suppose I could just include those lines in my /etc/profiles script, but I doubt whether it'll do any good as either my distro won't look into that script for the permissions, or it will override it with the settings indicated somewhere else. Where? Who knows! Annoying!! Mainly becasue it makes learning 'linux' so much harder.

Well, FCs coders may have stuck it somewhere in /etc/profile.d
for instance...
Just do a
grep -r umask /etc/*
to find where ...

Cheers,
Tink

Strange as it may sound I'd never used grep in this way! I either use it to serch for a file by name (as a complement to slocate) or to look inside 1 file, but I do remember reading this...

Anyway, grep -r umask /etc/* gives a ling list of hits, but no profiles. The most promising entry (as far as I can tell) is /etc/bshrc (what's rc an abbreviarion of anyway?)

Code:

if [ $UID -gt 99 ] && [ "`id -gn`" = "`id -un`" ]; then

        umask 002

else

        umask 022

fi

although it doesn't look a bit like the entry in your /etc/profiles