| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Wed, 2002-06-05 at 07:19, Robin Holt wrote: > > 1) rc.sysinit.d would be created. > 2) rc.sysinit script would be broken into many small scripts, each with > a definite purpose. > ie: the launching setting of networking options would end up being a > script named rc.sysinit.d/10network. > 3) rc.sysinit would then simply source each of those scripts in > numerical order. > What this would allow is when a third party is building an rpm for > RedHat, they would not need to have a %pre and %post which patches > rc.sysinit. I definitely agree. rc.sysinit is the last BSD-style remnant in a SysV structure. The idea behind SysV is to modularize, so that there's no need to edit critical files, but just create symlinks as needed. Breaking rc.sysinit into a directory is the logical next step towards a fully modularised startup mechanism. -- Florin Andrei "You can get excited about just any subject if you study it enough. It's the deep knowledge that makes a topic interesting." - Larry McVoy _______________________________________________ Redhat-devel-list mailing list Redhat-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-devel-list