Where do I change the permissions that are set when I create a new file?
I mean, I'd like to be able to change the default permissions that my
system atributes to new files.


bruno@merlin:~$ > newfile
bruno@merlin:~$ ls -l newfile
-rw-r--r-- 1 bruno bruno 0 2007-06-17 18:06 newfile


I'd like new files to be created as writable to the group, as in

-rw-rw-r-- 1 bruno bruno 0 2007-06-17 18:06 newfile


thanks!


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Jun 17, 2007 at 18:11:02 -0300, Bruno Buys wrote:
>Where do I change the permissions that are set when I create a new file? I
>mean, I'd like to be able to change the default permissions that my system
>atributes to new files.
>
>bruno@merlin:~$ > newfile
>bruno@merlin:~$ ls -l newfile
>-rw-r--r-- 1 bruno bruno 0 2007-06-17 18:06 newfile
>
>I'd like new files to be created as writable to the group, as in
>
>-rw-rw-r-- 1 bruno bruno 0 2007-06-17 18:06 newfile

Look into umask.

/M

--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus@therning.org Jabber: magnus.therning@gmail.com
http://therning.org/magnus

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBGdauxiMWTaatN+6QRAsVzAJ0U1ejuOjhWwBItXf30rj f5tkyMTwCeKlaI
pcRT+La2bAqSGKFChfp3z1U=
=N8Cj
-----END PGP SIGNATURE-----

Bruno Buys wrote:
> Where do I change the permissions that are set when I create a new file?
> ...
> I'd like new files to be created as writable to the group, as in
> -rw-rw-r-- 1 bruno bruno 0 2007-06-17 18:06 newfile

It sounds like you are trying to set up a "User Private Group" type of
configuration. Is that correct? That is a typical and good
configuration to use in a group of users.

In that case you will want to modify /etc/profile and change the umask
setting there from 'umask 022' to 'umask 02'. That file is sourced by
login shells.

sudo editor /etc/profile

Note that the default install configuration for the root user is to
have /root/.bashrc set 'umask 022' and to have /root/.profile source
the /root/.bashrc file but these are often customized. Even when
using UPG for non-root users it is desirable to keep root's umask to
be 022. After making the above change to /etc/profile you should log
in as root and verify that root's umask is still 022. This is just in
case root's environment has been customized and the umask setting
removed.

Bob


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Bruno Buys wrote:
> Where do I change the permissions that are set when I create a new
> file? I mean, I'd like to be able to change the default permissions
> that my system atributes to new files.
>
>
> bruno@merlin:~$ > newfile
> bruno@merlin:~$ ls -l newfile
> -rw-r--r-- 1 bruno bruno 0 2007-06-17 18:06 newfile
>
>
> I'd like new files to be created as writable to the group, as in
>
> -rw-rw-r-- 1 bruno bruno 0 2007-06-17 18:06 newfile
>
>
> thanks!
>
Umask did the trick. Kde seems to be following /etc/profile, so i edited
it. Konsole and yakuake needed a 'umask 02' added to ~/.bashrc (there
was none) to behave well. Neither one was reading ~/.bash_profile, by
the way. It remembers me when I was trying to add ~/bin to my path.
There was

if [ -d ~/bin ] ; then
PATH=~/bin:"${PATH}"
fi

but not worked.
Anyway, the issue is solved. Thanks all!




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Bruno Buys wrote:

> Konsole and yakuake needed a 'umask 02' added to ~/.bashrc (there
> was none) to behave well. Neither once was reading ~/.bash_profile, by
> the way.

That is because ~/.bash_profile is read on login shells only (unless you
source it from ~/.bashrc

--

Felipe Sateler


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Felipe Sateler wrote:
> Bruno Buys wrote:
> > Konsole and yakuake needed a 'umask 02' added to ~/.bashrc (there
> > was none) to behave well. Neither once was reading ~/.bash_profile, by
> > the way.
>
> That is because ~/.bash_profile is read on login shells only (unless you
> source it from ~/.bashrc

This is a very old issue that still has not been resolved, despite it
having been closed during the migration from XFree86 to X.org. Please
read through Bug#250765 for history.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=250765

Summary:

cat >$HOME/.xsession <<EOF
#!/bin/bash --login
exec x-session-manager
EOF
chmod a+x $HOME/.xsession

Bob


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

>From konsole use these:
chmod
chown

Chmod changes permissions. Type "$ man chmod" to know how to change them.
Chown changes owner. Type "$ man chown" to know how to change them.

E.g.
# mkdir /home/temp
# ls -l /home/temp
# chmod 777 /home/temp
# ls -l /home/temp
# chown bruno /home/temp
# ls -l /home/temp


Kind regards,

--
Oscar Blanco García
Ingeniero Electrónico - Universidad Nacional de Colombia
Teléfono: Casa: +57 1 687 0019
Celular: +57 3133890451
Carrera 123B # 131-66 Bloque 55 Apartamento 402
Bogotá, Colombia