public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Laura Eaves" <leaves1@carolina.rr.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: about permissions
Date: Wed, 1 Jun 2005 01:41:24 -0400	[thread overview]
Message-ID: <069901c5666c$8c939330$6401a8c0@Charmin> (raw)
In-Reply-To: <20050601033016.5980.47625@rif.myfreedombox.com>

A directory should havae execute permission for everybody as that grants the 
ability to cd into that directory.
Also, you made the directory writable to everyone, which isn't a good idea.
In general, 755 or 711 is a good setting for a home directory.
I think the lack of execute permission is what tripped you up.  Baasically 
nothing will work if no one can cd or traverse through that directory.
HTH
--le


----- Original Message ----- 
From: "tony seth" <lp800@myfreedombox.com>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, May 31, 2005 11:30 PM
Subject: about permissions


Hi all:  I have made a bit of a mess of my system, and need a bit of
help to fix it.  I tried recreating a user, and although that went
fine, when I tried to run a program in X, the X server shut down due to
permissions not being correct.  I tried correcting this by chmod 666 on
the home directory, but now can't log in with my home directory. Can
anyone tell me what the correct permissions on the /home directory
should be, and also those on a directory of a user within that
directory?  Thanks much!
Cjeerep!

-- 
Email services by FreedomBox.  Surf the Net at the sound of your voice.
www.freedombox.info

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup 



      parent reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 tony seth
 ` Luke Yelavich
 ` Laura Eaves [this message]

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='069901c5666c$8c939330$6401a8c0@Charmin' \
    --to=leaves1@carolina.rr.com \
    --cc=speakup@braille.uwo.ca \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).