Re: [SLE] Nobody is home in Samba [Solved]

From: David Rankin (drankin_at_cox-internet.com)
Date: 05/07/04

  • Next message: dmc: "Re: [SLE] Upgrade 9.0 -> 9.1 went totally wrong" 
    To: "Jerome Lyles" <susemail@hawaii.rr.com>
Date: Fri, 7 May 2004 09:32:33 -0500

    What are modes 0660 and 0750? And from one of your later
    > emails (Samba Share - Access Denied) what does "chmod g+s /some directory
    do?
    > Thanks again,
    > Jerome

    The easiest way to think about it is that the four numbers of a mode
    represent -- directory -- owner -- group -- world -- permissions. The
    directory bit just signifies whether the filename is a file (0) or a
    directory (1). The owner, group and world permissions are each defined by
    the read, write and execute bits. (ie. dwrxwrxwrx) The mode numbers are just
    short hand for setting the binary attributes of the read-write-execute
    permissions you want. For the owner, group and world bits the numbers mean
    the following:

    # binary wrx permission
    1 001 (--x) execute only
    2 010 (-w-) write only
    3 011 (-wx) write and execute
    4 100 (r--) read only
    5 101 (r-x) read and execute
    6 110 (rw-) read and write
    7 111 (rwx) read, write and execute

    So chmod 0660 filename sets the file permission of filename to

    -rw-rw----

    That means owner has read/write and group has read/write and world has no
    access

    Similarly chmod 0750 filename sets the file permission of filename to

    -rwx-r-x---

    Which means owner has read/write/execute, group has read/execute and world
    has no access.

    If your not affecting the directory bit, you can omit the leading 0. So
    chmod 660 is the same as chmod 0660.

    Hope that helps...... Somebody add this to a man page somewhere........ 

    --
David C. Rankin, J.D., P.E.
RANKIN * BERTIN, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankin-bertin.com
--
----- Original Message ----- 
From: "Jerome Lyles" <susemail@hawaii.rr.com>
To: <suse-linux-e@suse.com>
Sent: Friday, May 07, 2004 3:35 AM
Subject: Re: [SLE] Nobody is home in Samba [Solved]
> On Thursday 06 May 2004 03:27 am, Louis Richards wrote:
> <SNIP>
> I did as you suggested and also I added myself as a user using smbpasswd
and
> it worked.  Thank you Louis!  I checked man chmod but couldn't find out
what
> the modes you suggested I use mean.  What are the create mask and
directory
> mask functions?  What are modes 0660 and 0750?  And from one of your later
> emails (Samba Share - Access Denied) what does "chmod g+s /some directory
do?
> Thanks again,
> Jerome
>
> >
> > You have changed this to make the home directory browsable. When a
> > client first browses a server, it is done as nobody. You have not logged
> > on to the server yet. The server has no way to tell who you are. You
> > also are allowing guest access. Try the following:
> >
> > [homes]
> >         comment = Home Directories
> >         valid users = %S
> >         writable = Yes
> >         create mask = 0660
> >         directory mask = 0770
> >         browseable = No
> >
> >
> > --
> >
> > Louis D. Richards
> > LDR Interactive Technologies
>
>
> -- 
> Check the headers for your unsubscription address
> For additional commands send e-mail to suse-linux-e-help@suse.com
> Also check the archives at http://lists.suse.com
> Please read the FAQs: suse-linux-e-faq@suse.com
>
>
>
-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: dmc: "Re: [SLE] Upgrade 9.0 -> 9.1 went totally wrong"

    Relevant Pages

    • Re: [SLE] Nobody is home in Samba [Solved]
      ... > So chmod 0660 filename sets the file permission of filename to ... > Similarly chmod 0750 filename sets the file permission of filename to ...
      (SuSE)
    • Re: Reg: mkfs in FC4
      ... I'm a novice in device driver programming. ... command..It gives error as permission denied..I changed the permission ... chmod 777 <filename> ...
      (comp.os.linux.development.system)
    • [patch 12/22] vfs: utimes cleanup
      ... * must be owner or have write permission. ... * Else, update from *times, must be owner or super user. ... * If filename is NULL and dfd refers to an open file, ... extern int do_setitimer(int which, struct itimerval *value, ...
      (Linux-Kernel)
    • Re: Is it possible to create a write-only directory in *nix?
      ... DavidFilmer wrote: ... only the owner of the directory can read. ... I thought, duh, chmod the directory to 722. ... the filename could be easily known). ...
      (comp.unix.shell)
    • [patch 13/24] vfs: utimes cleanup
      ... * must be owner or have write permission. ... * Else, update from *times, must be owner or super user. ... * @filename: path name or NULL ...
      (Linux-Kernel)