mirror of the now-defunct rocklinux.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

74 lines
2.9 KiB

  1. # --- ROCK-COPYRIGHT-NOTE-BEGIN ---
  2. #
  3. # This copyright note is auto-generated by ./scripts/Create-CopyPatch.
  4. # Please add additional copyright information _after_ the line containing
  5. # the ROCK-COPYRIGHT-NOTE-END tag. Otherwise it might get removed by
  6. # the ./scripts/Create-CopyPatch script. Do not edit this copyright text!
  7. #
  8. # ROCK Linux: rock-src/package/base/linux/linux26/81-reiser-suiddir.patch
  9. # ROCK Linux is Copyright (C) 1998 - 2005 Clifford Wolf
  10. #
  11. # This patch file is dual-licensed. It is available under the license the
  12. # patched project is licensed under, as long as it is an OpenSource license
  13. # as defined at http://www.opensource.org/ (e.g. BSD, X11) or under the terms
  14. # of the GNU General Public License as published by the Free Software
  15. # Foundation; either version 2 of the License, or (at your option) any later
  16. # version.
  17. #
  18. # --- ROCK-COPYRIGHT-NOTE-END ---
  19. --- ./fs/reiserfs/namei.c.orig 2003-01-13 10:03:00.000000000 +0100
  20. +++ ./fs/reiserfs/namei.c 2003-01-13 10:03:57.000000000 +0100
  21. @@ -555,6 +555,13 @@
  22. } else {
  23. inode->i_gid = current->fsgid;
  24. }
  25. +#ifdef CONFIG_REISERFS_FS_SUIDDIR
  26. + if (dir->i_mode & S_ISUID) {
  27. + inode->i_mode |= (inode->i_mode & 0700) >> 3;
  28. + if (S_ISDIR(inode->i_mode))
  29. + inode->i_mode |= S_ISUID;
  30. + }
  31. +#endif
  32. DQUOT_INIT(inode);
  33. return 0 ;
  34. }
  35. --- ./fs/Kconfig.orig 2003-01-13 10:00:39.000000000 +0100
  36. +++ ./fs/Kconfig 2003-01-13 10:04:55.000000000 +0100
  37. @@ -252,6 +252,35 @@
  38. Almost everyone but ReiserFS developers and people fine-tuning
  39. reiserfs or tracing problems should say N.
  40. +config REISERFS_FS_SUIDDIR
  41. + bool "Reiserfs SUID on Directory Extension"
  42. + depends on REISERFS_FS
  43. + help
  44. + As you might know, the SGID flag has a special function on
  45. + directories: files within that directories will be owned by
  46. + the same group that also owns the directory - which is useful
  47. + for creating directories which are shared between the members
  48. + of a group.
  49. +
  50. + But that only makes sense if the umask is set to give full
  51. + permissions to the group (e.g. 007 or 002). Noone would do that
  52. + if there is a system-wide 'users' group - so some distributions
  53. + add an extra group for every user which lets the /etc/group
  54. + file grow very fast and makes the admins life harder ...
  55. +
  56. + Activating this feture adds a function to the SUID flag on
  57. + directories, which usually has no function at all:
  58. +
  59. + If the SUID flag is set for a diectory, all new files in that
  60. + directory will get the same rights in the group-field as they
  61. + have in their user-field. So, if one sets both - SUID and SGID
  62. + - on a directory, it will also work with a umask like 022 or
  63. + 077 and there is no more need for an extra group for every user.
  64. +
  65. + Also, the SUID flag will be set to all subdirectories of a
  66. + SUID directory (as it is already now with the SGID flag on
  67. + directories).
  68. +
  69. config JFS_FS
  70. tristate "JFS filesystem support"
  71. help