Re: [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF

["Devon H. O'Dell" <devon.odell@gmail.com>]

2007/4/12, Uriel <uriel99@gmail.com>:
> >           # uncomment the following for booting other systems
> >           #ip/dhcpd
> >           #ip/tftpd
>
> Shouldn't optional stuff like this go in cpurc.local anyway?

Sure, but having it here gives a good idea for the kinds of things
that you would want to put into your cpurc.local.

> >         + #if(! netstat -n | grep -v 17008 | grep -s il.*Listen)
> >         + #     aux/listen -q il
> [...]
> >         + # cpu specific startup
> >         + #if(test -e /cfg/$sysname/cpustart)
> >         + #     . /cfg/$sysname/cpustart
> >         +
> >         + #echo `{date} $sysname >>/sys/log/boot
>
> Why is all this commented out?

There's no /cfg in the default distribution, for one. IL isn't really
used per default and isn't very inter-operable. Not sure why the
bootlog change would be; it seems like a good thing to have in there
by default. In either case it's giving good ideas for things you may
want / need in your cpurc.local.

One thing I'm not sure of still is, if there is a cpurc.local, it may
want to implement some things dependent on e.g. what if you are
starting some client script that requires the network to already have
been initialized. This seems to be what you would end up putting in
your /cfg/$sysname/cpustart,

> This changes seem to intend to allow local installations to override
> the default cpurc setup without having to edit it (and therefore get
> out of sync with sources and need to merge future changes by hand and
> so on), so I see little reason to leave 'alternative' sections
> commented out when the local and $sysname specific scripts can take
> care of that.

We need to have something automatically create /cfg for peoples
fossils when they upgrade then. You can't just mkdir /cfg.

> And thanks dho for writing the summaries! Just one small complaint,
> could you fix the first line of the comments (specially because it is
> used by convention as subject for the emails)?

I could. How is your script splitting them up though? I was assuming
that it used those lines to split each change.

> Best wishes
>
> uriel

If we really wanted to take care of these issues, it'd be worth
considering the creation of an rc system, but I'm not sure how much
fire that would cause in the community.

-dho