From: dave <dave@dpomeroy.com>
To: "Theo. Sean Schulze" <tschulze@teamfinders.org>
Cc: linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: security
Date: Tue, 17 Feb 2004 13:22:45 -0800 [thread overview]
Message-ID: <40328625.4080403@dpomeroy.com> (raw)
In-Reply-To: <20040217191000.GA30689@teamfinders.org>
Theo. Sean Schulze wrote:
>On Tue, Feb 17, 2004 at 09:55:34AM -0800, dave hunted and pecked out:
>
>
>>I've been runing Mandrake for a couple of years and I'm still having
>>problems with groups.
>>This is the procedure for making a group and sharing a subdirectory that
>>I use. Can someone tell me where I'm screwing up? Thanks in advance
>>
>>Make a folder: mkdir /home/everyone
>>make group: groupadd everyone
>>add users gpasswd -a dave everyone
>>add users gpasswd -a laura everyone
>>change the group for the folder chgrp -R everyone /home/everyone
>>add write for group everyone chmod g+r /home/everyone
>>
>>
>
>Could just be a typo, but r adds read privileges. g+w would add write
>privileges.
>
>
>
>>When I'm done with this I still can not make a folder in /home/everyone
>>logged on as dave.
>>
>>
>
>If that wasn't a typo, then it would explain why you can't write a new
>directory in the /home/everyone folder.
>
>
>
>>again thanks for your help
>>
>>--
>>Dave Pomeroy K7DNP South Eastern Washington
>>
>>
>>
>Cheers,
>Sean
>
>
Sean,
That was a typo. I've made some progress with Rays help. It appears
msec is causing the problem. It keeps running and revoking the write on
the /home/everyone subdirectory for the group. I'll work on msec.
Thanks for the help
--
Dave Pomeroy K7DNP South Eastern Washington
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-02-17 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 17:55 security dave
2004-02-17 19:00 ` security Ray Olszewski
2004-02-17 19:10 ` security Theo. Sean Schulze
2004-02-17 21:22 ` dave [this message]
2004-02-18 2:10 ` security Ray Olszewski
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 16:28 Security Oliver Ob
2002-07-09 17:48 ` Security Jennifer Olson
2002-07-09 18:05 ` Security Wladimir Foo
2002-07-09 18:25 ` Security pa3gcu
2002-07-11 7:01 ` Security Kilaru Sambaiah
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=40328625.4080403@dpomeroy.com \
--to=dave@dpomeroy.com \
--cc=linux-newbie@vger.kernel.org \
--cc=tschulze@teamfinders.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.