Re: [Pkg-sysvinit-devel] So, what should we do about /etc/rc.boot/ (BTS #546401)?
On Fri, 18 Sep 2009, Petter Reinholdtsen wrote: 1) Leave it as it is, update the release notes for Squeeze do document the change. 2) Revert the change temporarely, and decide on a deadline when the feature is going away for good. 3) Revert the change, and rewrite the rc.boot(5) manual page to no longer state that the feature is obsolete. I'd vote for (3), but one has to also say when it will run on a dependency-based system. Can we make it run last? -- 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
[Pkg-sysvinit-devel] So, what should we do about /etc/rc.boot/ (BTS #546401)?
So, I guess everyone saw the /etc/rc.boot/ discussion in #546401? What should we do? The options as I see it is 1) Leave it as it is, update the release notes for Squeeze do document the change. 2) Revert the change temporarely, and decide on a deadline when the feature is going away for good. 3) Revert the change, and rewrite the rc.boot(5) manual page to no longer state that the feature is obsolete. I do not really have a preference myself. I am just quite sure that this option is out of the question: 4) Revert the change, claim the feature is obsolete in the manual page but make no plan to actually remove the feature. Why was /etc/rc.boot/ flagged as obsolete in the first place? Happy hacking, -- Petter Reinholdtsen ___ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
