On Tue, Aug 18, 2009 at 10:16:47PM +0200, Serafeim Zanikolas wrote: > I like this proposal, thanks for ignoring my request to not write about > alternatives ;) > > I'll take some time to think about it and read up on triggers/etc. I might bug > you in private about this as I think we're getting off-topic here. No worries. The other things that this will be useful for are full IPv6 support (currently needs two separate entries, so every update-inetd user needs to call it twice, but no packages I've seen do this--it's IPv4 only), and also transparent migration between inetd implementations (e.g. inetd←→xinetd and other future programs. upstart?). Currently these are both completely unsupported. The initial work that needs doing is defining a suitable file format. A simple key=value or Key: Value scheme would probably be sufficient if there's only one service per file. Alternatively, the xinetd format is /currently/ the superset, but that's perhaps not flexible enough for the future since we're then tied into being compatible with that single implementation. The next bit would be writing the update-inetd replacement (which could just be part of the existing update-inetd, used when called with no arguments, and/or run on every invocation). If called with arguments, it will work as usual; the old code would be removed after the transition is done so it just does nothing, or emits a warning. Until the transition is complete, and this would most likely be over a stable release, it would also need to update the fragments from inetd.conf since during this period that would remain the definitive configuration. Once complete this would be stopped. Once that's in place, packages can then start providing the fragments in /etc/inetd.d. At this point, there won't be any use of the generated file(s), but we can verify it's all working correctly. Once done, the inetds can start using the new generated configs, and then it's done. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
Attachment:
signature.asc
Description: Digital signature