* Chuck Swiger [2005-05-11 14:33 -0400]
> Otherwise, you only have one default umask. I'm not sure there is a sane way
> of changing it depending on which directory you are currently in, but you
> might try setting up an alias ("cd77", "cd22"?) which combines setting the
> umask and cd'ing.
On Wed, May 11, 2005 at 03:44:04PM -0400, Chuck Swiger wrote:
> Sure, modulo the permissions on .cshrc itself. If you don't want them to,
> give that file 600 perms. The Unix octal permissions bits work just fine
> for almost all reasonable cases, but no default is ever going to suit all
> pos
Lewis Thompson wrote:
Okay, I'm going to jump in now and ask something I have always wanted to
know the answer to but always seem to forget.
Can /home be configured so all files are created with permissions of
0600 (or 0700 for directories)? I use a umask of 77 but that's annoying
when playing wit
Lewis Thompson wrote:
On Wed, May 11, 2005 at 03:15:40PM -0400, Chuck Swiger wrote:
If you "mkdir private && chmod 700 private", any files created under
private will be safely[1] hidden away from anyone else but you, regardless
of their permissions or what your umask is.
Ah, okay. A slightly bad
On Wed, May 11, 2005 at 03:15:40PM -0400, Chuck Swiger wrote:
> If you "mkdir private && chmod 700 private", any files created under
> private will be safely[1] hidden away from anyone else but you, regardless
> of their permissions or what your umask is.
Ah, okay. A slightly bad example. How
Lewis Thompson wrote:
On Wed, May 11, 2005 at 02:33:30PM -0400, Chuck Swiger wrote:
setgid on directories won't help, but maybe the behavior of the sticky bit
is what you are looking for? Is how stuff in /tmp handled OK
permission-wise for your expectations?
No, I was thinking more along the lin
On Wed, May 11, 2005 at 02:33:30PM -0400, Chuck Swiger wrote:
> setgid on directories won't help, but maybe the behavior of the sticky bit
> is what you are looking for? Is how stuff in /tmp handled OK
> permission-wise for your expectations?
No, I was thinking more along the lines of inheritin
Lewis Thompson wrote:
On Wed, May 11, 2005 at 01:37:27PM -0400, Chuck Swiger wrote:
If all of the users have their default group be staff or some such, anyone
can change any file which is group-writable. If each user has their
default group be a unique group (with UID==GID), then users can safel
On Wed, May 11, 2005 at 01:37:27PM -0400, Chuck Swiger wrote:
> If all of the users have their default group be staff or some such, anyone
> can change any file which is group-writable. If each user has their
> default group be a unique group (with UID==GID), then users can safely use
> a 002 u
David Bear wrote:
I've noticed that with some Linux distributions the default behavior
of creating user accounts created the group with the same name as the
user, and made that group the primary group of the user. There are
other linux distributions that the throw all users into a default
group nam
In the last episode (May 11), David Bear said:
> Apoligies in advance but searches based on keyword were too
> voluminous.
>
> I've noticed that with some Linux distributions the default behavior
> of creating user accounts created the group with the same name as the
> user, and made that group th
Apoligies in advance but searches based on keyword were too
voluminous.
I've noticed that with some Linux distributions the default behavior
of creating user accounts created the group with the same name as the
user, and made that group the primary group of the user. There are
other linux distribu
12 matches
Mail list logo
