[arch-dev-public] initscripts in testing

Aaron Griffin aaronmgriffin at gmail.com
Thu Oct 18 12:01:14 EDT 2007


On 10/18/07, Dan McGee <dpmcgee at gmail.com> wrote:
> On 10/18/07, Aaron Griffin <aaronmgriffin 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.
> >
> > Agreed.
> >
> > In addition, could you make sure 'isatty' is part of this package? It
> > somehow got lost recently and I use it in some personal scripts.
>
> Um...I killed this. It was pointless and not even full-featured. Try
> the test -t option.

Well ok then, I kinda expected some mention of this in the logs, and
didn't see it, so assumed it was an oversight.

Could you 'cvs rm' the C file




More information about the arch-dev-public mailing list