Package: initscripts Version: 2.88dsf-22.1 Severity: grave Justification: fucks up systems during upgrade
Hi, from previous “RAMTMP isn't so bad” IRC sessions, it appears it's supposed to be on for new installations, and not turned on during upgrades. Except it is. Reproducibility: - install a squeeze VM - sed -i s/squeeze/testing/ /etc/apt/sources.list - apt-get update && apt-get install initscripts → RAMTMP=yes is set. For your convenience, before/after /etc/default/rcS are attached. Please stop this craziness. Mraw, KiBi.
# # /etc/default/rcS # # Default settings for the scripts in /etc/rcS.d/ # # For information about these variables see the rcS(5) manual page. # # This file belongs to the "initscripts" package. TMPTIME=0 SULOGIN=no DELAYLOGIN=no UTC=yes VERBOSE=no FSCKFIX=no RAMRUN=no RAMLOCK=no
# # /etc/default/rcS # # Default settings for the scripts in /etc/rcS.d/ # # For information about these variables see the rcS(5) manual page. # # This file belongs to the "initscripts" package. # delete files in /tmp during boot older than x days. # '0' means always, -1 or 'infinite' disables the feature TMPTIME=0 # spawn sulogin during boot, continue normal boot if not used in 30 seconds SULOGIN=no # do not allow users to log in until the boot has completed DELAYLOGIN=no # assume that the BIOS clock is set to UTC time (recommended) UTC=yes # be more verbose during the boot process VERBOSE=no # automatically repair filesystems with inconsistencies during boot FSCKFIX=no # mount /run/lock as a tmpfs (separately from /run) RAMLOCK=yes # mount /run/shm as a tmpfs (separately from /run) RAMSHM=yes # mount /tmp as a tmpfs RAMTMP=yes
