-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eric MSP Veith escribió: > I agree with you, the net/ folder perfectly fits into system/, as Unix boxes > are network boxes anyway. :-) > > Once we've tied the system/ folder, we should change the names/pourposes of > the services in there as little as possible while only adjusting/tweaking the > contents of the files. I.e. people should trust that system/mountfs stays > there, is not renamed and it's pourpose stays the same, only the code gets > bugfixed and tuned. > > So we get: > > daemon/ only for daemons, > system/ services essential for system startup and scripts > responsible > for establishing, maintaining and closing network connections
Well, as i said before, network stuff is somewhat special, however we may move it into system/network/, but things like daemon/dhcpcd or daemon/pppoe will not be moved there. > services/ place for services that aren't essential for system bootup, > i.e. "the rest", > runlevel/ runlevels, > config/ initng specific configuration files (for configuring > daemons/services, as /etc/sysconfig or /etc/conf.d do) > > Eric > > ------ Original Message ------ > Sender: Jens Persson <[EMAIL PROTECTED]> > Recipient: [email protected] > Date: Thursday 08 February 2007 02:47 > Subject: Re: [Initng] We need to tie /etc/initng > >>> I agree too. That may also work as a warning bell for the devs that no >>> lazy coding is accepted in system. And maybe we can ditch net and only >>> have daemon, system and service. The net stuff could then be put in >>> system as most boxes needs a network connection to be useful and to be >>> updated. Just a thought. >>> >>> Felipe Balbi wrote: >>>> I agree with Ismael, >>>> >>>> This way it could be possible to kind of freeze the system folder once >>>> we know all the services we have to setup on boot time... >>>> >>>> On 2/5/07, Ismael Luceno <[EMAIL PROTECTED]> wrote: >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA1 >>>>> >>>>> Eric MSP Veith escribió: >>>>>> It could be slightly confusing when to put a script into service/ and >>>>>> when into system/ - some services might be essential for certain >>>>>> configurations, but for others not. >>>>>> >>>>>> Perhaps we shouldn't distinguish between service/ and system/ and keep >>>>>> only the service/ directory as it is a nice visible contrast to >>>>>> daemon/. >>>>> With essential I mean that the system can't boot without it, or it's >>>>> low-level (like hdparm). >>>>> >>>>> For example, things like issue.i, aumix.i, and anacron.i will go to >>>>> service/, while others like udev.i will go to system/. >>>>> >>>>>> Eric >>>>>> >>>>>> ------ Original Message ------ >>>>>> Sender: Ismael Luceno <[EMAIL PROTECTED]> >>>>>> Recipient: InitNG ML <[email protected]> >>>>>> Date: Monday 05 February 2007 18:25 >>>>>> Subject: [Initng] We need to tie /etc/initng >>>>>> >>>>>>>> We have services in daemon/ and other nasty things, so it's time to >>>>>>>> tie it. >>>>>>>> >>>>>>>> What I want: >>>>>>>> >>>>>>>> daemon/ : only for daemons >>>>>>>> service/ : all those services that aren't essential for the system >>>>>>>> system/ : system services/daemons >>>>>>>> runlevel/ : for runlevels >>>>>>>> config/ : for initng-specific config files, and may help to support >>>>>>>> unknown distros ;) >>>>> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFFypLn/mxY0+yOXJoRAsotAJ4h914HSPnHLIkBk9qVYtA/s9iQ0ACgzyfA 3Oa5A1eLwsBVp0abvHmKO/s= =rdLc -----END PGP SIGNATURE----- -- _______________________________________________ Initng mailing list [email protected] http://jw.dyndns.org/mailman/listinfo/initng
