[arch-dev-public] initscripts in testing

[Aaron Griffin]

On 10/18/07, Dan McGee <dpmcgee at gmail.com> wrote:
> On 10/18/07, Simo Leone <simo at archlinux.org> wrote:
> > On Thu, Oct 18, 2007 at 11:05:32AM +0200, Jan de Groot wrote:
> > >
> > > 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.
> > >
> > I agree. I think we've always had lo enabled by default, and I see
> > little reason to change that right now. It'll just cause a lot of
> > headaches for like 90% of people by adding a little nuance that they're
> > unlikely to know about.
> >
> > -S
> >
> > _______________________________________________
> > arch-dev-public mailing list
> > arch-dev-public at archlinux.org
> > http://archlinux.org/mailman/listinfo/arch-dev-public
> >
> >
> >
>
> Two thoughts here, mostly for Tobias:
> * Version is 2007.08-4, shouldn't this be version 2007.10/11?
> * When you made the lo change, did you ensure it is backward
> compatable? Having lo in your network array shouldn't cause an error
> now, because every current user will have it.

Third thought. We should treat the initscripts as a real code project.
That is, place them beside the rest of the code and create real
tarballs.