[Pkg-sysvinit-devel] Bug#459425: [PATCH]: improve README.Debian
kel at otaku42.de
Sun Jan 6 13:40:06 UTC 2008
Please apply patch to remove obsolete cruft from README.Debian and
describe tmpfs features of initscripts package and new sendsigs pid omission
Also fix some grammar in new /sys blurb.
--- debian/initscripts/doc/README.Debian (revision 1198)
+++ debian/initscripts/doc/README.Debian (working copy)
@@ -1,39 +1,47 @@
-Around kernel version 2.3.3x, a memory based filesystem was
-introduced to support POSIX shared memory, called 'shmfs'.
-Later this filesystem was extended for general usage and a
-"tmpfs" could be mounted. The CONFIG_TMPFS kernel compile option
-must be set to 'y', as it is for Debian kernels.
+Tmpfs can be used as virtual memory filesystem. glibc 2.2 and above
+expects a tmpfs to be mounted at /dev/shm for POSIX shared memory,
+this is done automatically by /etc/init.d/mountdevsubfs.sh early in
+the boot process. You can limit tmpfs max size by setting the
+SHM_SIZE variable to a desired size in the /etc/default/tmpfs file
+to prevent tmpfs from using up all system memory.
-Early in the 2.4 kernel series, shmfs was renamed to tmpfs, but
-could be mounted using either 'shmfs' or 'tmpfs'. Starting with
-kernel version 2.5.44, the 'shmfs' alias was dropped.
+A tmpfs can also be mounted over /var/run/ and /var/lock/. This can
+be achieved by setting the RAMRUN and RAMLOCK variables to "yes" in
+the /etc/default/rcS file. A size limit for the tmpfs filesystem
+mounted over /var/run/ and /var/lock/ can be set via the RUN_SIZE
+and LOCK_SIZE variables in the /etc/default/tmpfs file.
-Confusingly, in kernels 2.3.x - 2.5.43 where both "shmfs" and
-"tmpfs" are present, disabling CONFIG_TMPFS actually removes
-support for shmfs, but tmpfs is still listed in /proc/filesystems
-to support SYSV and POSIX shared memory, and it should still be
-mounted under /dev/shm.
+If TMPFS_SIZE is set in /etc/default/tmpfs, it will be used as the
+default value for SHM_SIZE, RUN_SIZE and LOCK_SIZE. Otherwise, kernel
+defaults are used.
-Recommendation: always enable CONFIG_TMPFS and always mount
-using the tmpfs type. Forget about shmfs.
-Tmpfs can be used as memory filesystem, so you can limit tmpfs
-max size using /etc/default/tmpfs to prevent tmpfs from using
-up all system memory.
+sendsigs process omission interface
+Since initscripts package version 2.86.ds1-48, /etc/init.d/sendsigs
+is able to omit processes from being killed by killall5(8). Process
+id's listed in /var/run/sendsigs.omit, /lib/init/rw/sendsigs.omit or
+any file in the /lib/init/rw/sendsigs.omit.d/ directory will be
+omitted by sendsigs.
+The recommended practise for adding a process id for omission is to
+create a file in /lib/init/rw/sendsigs.omit.d/<package name>
+containing the process id that is to be omitted by sendsigs.
/sys in /etc/fstab
-If the mounting point /sys/ have an entry in /etc/fstab (which is not
-required, it will be mounted in any case), the entry have to look like
+If the mount point /sys/ has an entry in /etc/fstab (which is not
+required, it will be mounted in any case), the entry must be:
sysfs /sys sysfs rw,nosuid,nodev,noexec 0 0
-The reason is that the entry in fstab need to match the entry
+The reason is that the entry in fstab needs to match the entry
generated by the mountkernfs.sh and mtab.sh scripts. If it does not,
the system will complain with this message during boot:
More information about the Pkg-sysvinit-devel