Bug#406685: [Pkg-sysvinit-devel] Bug#406685: initscripts: RAMRUN, RAMLOCK vars/opts are undocumented

2007-01-18 Thread Paolo
[sorry for late reply] On Mon, Jan 15, 2007 at 12:41:51AM -0200, Henrique de Moraes Holschuh wrote: > > > > problem is, that fixes need to survive upgrades. > > It survives upgrades just fine, or at least it is supposed to by design. hope so - we'll see on next round. > Now, how the heck you ha

Bug#406685: [Pkg-sysvinit-devel] Bug#406685: initscripts: RAMRUN, RAMLOCK vars/opts are undocumented

2007-01-14 Thread Henrique de Moraes Holschuh
On Sun, 14 Jan 2007, Paolo wrote: > On Sun, Jan 14, 2007 at 12:13:34PM -0200, Henrique de Moraes Holschuh wrote: > > > their init.d/ scripts. Case in point was clamav-daemon, which didn't start > > > on boot, expecting /var/run/clamav/ to be already there. Same for virus-DB > > > updater freshclam.

Bug#406685: [Pkg-sysvinit-devel] Bug#406685: initscripts: RAMRUN, RAMLOCK vars/opts are undocumented

2007-01-14 Thread Paolo
On Sun, Jan 14, 2007 at 12:13:34PM -0200, Henrique de Moraes Holschuh wrote: > > their init.d/ scripts. Case in point was clamav-daemon, which didn't start > > on boot, expecting /var/run/clamav/ to be already there. Same for virus-DB > > updater freshclam. > > They are buggy. They need to be fix

Bug#406685: [Pkg-sysvinit-devel] Bug#406685: initscripts: RAMRUN, RAMLOCK vars/opts are undocumented

2007-01-14 Thread Henrique de Moraes Holschuh
On Sat, 13 Jan 2007, Paolo wrote: > config, is a secondary point, main one is that RAMRUN - ie /var/run on > tmpfs - and perhaps others, doesn't look like an acceptable option in Etch > current, as too many pkgs don't expect volatile dirs under /var/run hence > fail on (re)boot. > Respective mai