>>>>> "itojun" == itojun  <itojun@iijlab.net> writes:
    itojun> 	dependency list in /etc/init.d/foo looks good to me at a first glance,
    itojun> 	but when i've done reading it i'm a bit worried about problem tracking
    itojun> 	issues and support issues.
    itojun> 	it will become harder to track problems in rc script as rc script
    itojun> 	will be tailor-made to the installation site.  if random user says
    itojun> 	that she has some problem with start up script, we basically have
    itojun> 	to get her script, read it through, to track the problem.

    itojun> 	since there's little manpower to handle PRs, I would vote to stick
    itojun> 	with simple-and-static rc and rc.conf...

  I suggest that we distribute an /etc/rc generated by mkrc by default.
  That solves the typical user problem. If our /etc/rc.d/* is empty, then
users can install packages, etc. easily without disturbing /etc/rc too much.

]      Out and about in Ottawa.    hmmm... beer.                |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [