On Tue, 15 Jul 2008, Kel Modderman wrote:
> On Tuesday 15 July 2008 00:07:13 Henrique de Moraes Holschuh wrote:
> > Usually, alternative initscript systems supply their own update-rc.d and
> > invoke-rc.d. That can be a bit more robust, although it IS a lot of code
> > duplication.
> >
> > What exactly do you intend to do with these changes to sysv-rc's
> > update-rc.d?
>
> This particular patch allows to test update-rc.d in a test suite, for example.
>
> You can create /tmp/etc/init.d/, /tmp/etc/rc{S,{0..6}}.d/, put some
> scripts in /tmp/etc/init.d/ and then manipulate runlevel links in
> /tmp/etc/rc{S,{0..6}}.d/ by supplying /tmp as argument to -d command line
> option.
If it is just for testing update-rc.d, I'd rather it be done using a chroot.
That way you test the REAL effect of the command (you don't run the entire
thing on the chroot, just the update-rc.d command itself). That would also
test that we have all dependencies and other such *critical* details as a
side-effect, since we need them in the croot for update-rc.d to work ;-)
> Maybe "alternative filesystems" was poor wording for patch description.
Yeah, and the lack of a [PATCH 0/4] introdutory email telling us what is the
objective of the patches...
Note that I am just commenting on the patches, I am not *objecting* to them.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
_______________________________________________
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
