d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Typo nits in SUIDDIR comment (removed some parentheses, moved some

Browse Source 
commas, replaced "partition" with "filesystem", reformatted the
paragraph)
This commit is contained in:
Dag-Erling Smørgrav 1998-05-16 14:08:31 +00:00
parent bc6ee716d5
commit 276756a441
3 changed files with 39 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
sys/conf/NOTES
View File

@ -2,7 +2,7 @@
# LINT -- config file for checking all the sources, tries to pull in
# as much of the source tree as it can.
#
# $Id: LINT,v 1.428 1998/04/22 18:18:16 mjacob Exp $
# $Id: LINT,v 1.429 1998/04/29 17:09:41 andreas Exp $
#
# NB: You probably don't want to try running a kernel built from this
# file. Instead, you should start from GENERIC, and add options from
@ -510,17 +510,18 @@ options QUOTA #enable disk quotas
# The number is supposed to be in seconds.
options "CD9660_ROOTDELAY=20"
# If you are running a machine just as a fileserver for PC and MAC users.
# (using SAMBA or Netatalk), then you may consider setting this option
# and keeping all those user's directories on a partition that is mounted
# with the suiddir option. This gives new files the same ownership as
# the directory (similiar to group). It's a security hole if you let
# these users run programs so confine it to file-servers, (but it'll save you
# lots of headaches in that case). Root owned directories are excempt and X bits
# are cleared. the suid bit must be set on the directory as well. see chmod(1)
# PC owners can't see/set ownerships so they keep getting their toes
# trodden on. This saves you all the support calls as the filesystem
# it's used on will act as they expect. ("It's my dir so it must be my file").
# If you are running a machine just as a fileserver for PC and MAC
# users, using SAMBA or Netatalk, you may consider setting this option
# and keeping all those users' directories on a filesystem that is
# mounted with the suiddir option. This gives new files the same
# ownership as the directory (similiar to group). It's a security hole
# if you let these users run programs so, confine it to file-servers
# (but it'll save you lots of headaches in those cases). Root owned
# directories are exempt and X bits are cleared. The suid bit must be
# set on the directory as well; see chmod(1) PC owners can't see/set
# ownerships so they keep getting their toes trodden on. This saves
# you all the support calls as the filesystem it's used on will act as
# they expect: "It's my dir so it must be my file".
#
options SUIDDIR

25
sys/i386/conf/LINT
View File

@ -2,7 +2,7 @@
# LINT -- config file for checking all the sources, tries to pull in
# as much of the source tree as it can.
#
# $Id: LINT,v 1.428 1998/04/22 18:18:16 mjacob Exp $
# $Id: LINT,v 1.429 1998/04/29 17:09:41 andreas Exp $
#
# NB: You probably don't want to try running a kernel built from this
# file. Instead, you should start from GENERIC, and add options from
@ -510,17 +510,18 @@ options QUOTA #enable disk quotas
# The number is supposed to be in seconds.
options "CD9660_ROOTDELAY=20"
# If you are running a machine just as a fileserver for PC and MAC users.
# (using SAMBA or Netatalk), then you may consider setting this option
# and keeping all those user's directories on a partition that is mounted
# with the suiddir option. This gives new files the same ownership as
# the directory (similiar to group). It's a security hole if you let
# these users run programs so confine it to file-servers, (but it'll save you
# lots of headaches in that case). Root owned directories are excempt and X bits
# are cleared. the suid bit must be set on the directory as well. see chmod(1)
# PC owners can't see/set ownerships so they keep getting their toes
# trodden on. This saves you all the support calls as the filesystem
# it's used on will act as they expect. ("It's my dir so it must be my file").
# If you are running a machine just as a fileserver for PC and MAC
# users, using SAMBA or Netatalk, you may consider setting this option
# and keeping all those users' directories on a filesystem that is
# mounted with the suiddir option. This gives new files the same
# ownership as the directory (similiar to group). It's a security hole
# if you let these users run programs so, confine it to file-servers
# (but it'll save you lots of headaches in those cases). Root owned
# directories are exempt and X bits are cleared. The suid bit must be
# set on the directory as well; see chmod(1) PC owners can't see/set
# ownerships so they keep getting their toes trodden on. This saves
# you all the support calls as the filesystem it's used on will act as
# they expect: "It's my dir so it must be my file".
#
options SUIDDIR

25
sys/i386/conf/NOTES
View File

@ -2,7 +2,7 @@
# LINT -- config file for checking all the sources, tries to pull in
# as much of the source tree as it can.
#
# $Id: LINT,v 1.428 1998/04/22 18:18:16 mjacob Exp $
# $Id: LINT,v 1.429 1998/04/29 17:09:41 andreas Exp $
#
# NB: You probably don't want to try running a kernel built from this
# file. Instead, you should start from GENERIC, and add options from
@ -510,17 +510,18 @@ options QUOTA #enable disk quotas
# The number is supposed to be in seconds.
options "CD9660_ROOTDELAY=20"
# If you are running a machine just as a fileserver for PC and MAC users.
# (using SAMBA or Netatalk), then you may consider setting this option
# and keeping all those user's directories on a partition that is mounted
# with the suiddir option. This gives new files the same ownership as
# the directory (similiar to group). It's a security hole if you let
# these users run programs so confine it to file-servers, (but it'll save you
# lots of headaches in that case). Root owned directories are excempt and X bits
# are cleared. the suid bit must be set on the directory as well. see chmod(1)
# PC owners can't see/set ownerships so they keep getting their toes
# trodden on. This saves you all the support calls as the filesystem
# it's used on will act as they expect. ("It's my dir so it must be my file").
# If you are running a machine just as a fileserver for PC and MAC
# users, using SAMBA or Netatalk, you may consider setting this option
# and keeping all those users' directories on a filesystem that is
# mounted with the suiddir option. This gives new files the same
# ownership as the directory (similiar to group). It's a security hole
# if you let these users run programs so, confine it to file-servers
# (but it'll save you lots of headaches in those cases). Root owned
# directories are exempt and X bits are cleared. The suid bit must be
# set on the directory as well; see chmod(1) PC owners can't see/set
# ownerships so they keep getting their toes trodden on. This saves
# you all the support calls as the filesystem it's used on will act as
# they expect: "It's my dir so it must be my file".
#
options SUIDDIR