[Pkg-sysvinit-devel] Bug#585540: initscripts: improve /etc/default/tmpfs documentation and rcS manpage documentation

Christoph Anton Mitterer calestyo at scientia.net
Fri Jun 11 14:37:26 UTC 2010


Package: initscripts
Version: 2.88dsf-7
Severity: wishlist

Hi Petter and others.

Recently I wrote on Debian about how to improve waerleveling with SSDs and now found out
that there's already infrastructure there by RAMRUN/RAMLOCK in rcS :-)

I'd have some questions and ideas for improvements:
1) TMPFS_SIZE serves only as a default for RUN_SIZE and LOCK_SIZE in case those are not
   set, right? Thus it's possible to set their size and leaf all other tmpfs as is.
   I'd suggest then to better reflect this in the rcS(5) manpage by:
   - do not mentioning TMPFS_SIZE there at all, but just in /etc/default/tmpfs
   - change the order in the text, first RUN_SIZE respectively LOCK_SIZE and then
     TMPFS_SIZE plus adding in brackets or so, that TMPFS_SIZE is just their default if
     unset.

2) /etc/default/tmpfs only contains documentation about SHM_SIZE but not about the
   others (TMPFS_SIZE, RUN_SIZE, LOCK_SIZE, perhaps others I don't know).
   Could you add such documentation similar to what we already have with SHM_SIZE?
   If you want me I could try to set up a text for this.

4) OT: Is it safe to use the two (RAMRUN/RAMLOCK)? I mean as you say "Packages expecting
   this are buggy and need to be fixed."... do you know of any packages breaking this?

5) btw: while /etc/default/tmpfs is listed (dpkg -L) as being part of initscripts,
   /etc/default/rcS is not (although it's content says it belongs to it). Is there any
   good reason for this?


Thanks + best wishes,
Chris.





More information about the Pkg-sysvinit-devel mailing list