[arch-dev-public] initscripts in testing

[Jan de Groot]

> -----Oorspronkelijk bericht-----
> Van: arch-dev-public-bounces at archlinux.org [mailto:arch-dev-public-
> bounces at archlinux.org] Namens Tobias Powalowski
> Verzonden: donderdag 18 oktober 2007 10:11
> Aan: Public mailing list for ArchLinux development
> Onderwerp: [arch-dev-public] initscripts in testing
> 
> Hi
> i put new initscripts for both arches to testing.
> they should fix those bugs:
> http://bugs.archlinux.org/task/5740
> http://bugs.archlinux.org/task/6237
> http://bugs.archlinux.org/task/7165
> http://bugs.archlinux.org/task/7554
> http://bugs.archlinux.org/task/7641
> 
> 
> there are some feature requests which i didn't implemented yet comments
> from
> your side please:
> http://bugs.archlinux.org/task/7369
> http://bugs.archlinux.org/task/7714
> http://bugs.archlinux.org/task/7267
> 
> 
> probably not implement / closing requests:
> http://bugs.archlinux.org/task/5324
> 
> 
> finally next step bump to next release name:
> we need a new release name :)
> suggestions please,
> i think the last name suggestion was "Hardcore".

About the "lo" fix: there's a comment in rc.conf about disabling lo now. Did
you think about users who don't add "network" to DAEMONS?

IMHO rc.sysinit should always enable the lo interface, unless it is
specifically disabled (look for interfaces=(!lo) or !network in DAEMONS).
Yes, this is inconsistent with the way we work in arch, but it will lower
the amount of bugreports we get for this, while still giving people control
over their lo interface if they want to disable it on purpose.