On Tue, 31 May 2005 22:41:38 -0500, Walter Goulet wrote:

> I've recenly installed OpenBSD 3.7 on my Zaurus C3000. While perusing 
> the afterboot manpage to figure out how to configure my system, I 
> noticed that the manpage indicated that the /etc/rc.conf.local file was 
> referred to before the manpage stated that the user had to create this file.

This is a good idea.
IMHO there could be more like that; but now people will jump at me;
because they rather stay off mainstream ... ?

I'd personally even have /etc/rc.conf.local in /etc/ at install, with a
small comment on top and an upgrade script just ignoring it when it exists
in the earlier version. If I was in beauty, I made something similar for
rc.local; because I always have to scroll down (had, that is) fearing to
touch something, so I also start by copying the files to files.orig. I
prefer those rc.* compared to SysV !

Another, minor, item: Not doing this each day, I always need to look up
the syntax: YES compared to "". And the new ntpd - setup at install - does
ntpd_flags= 
Some 'standard' would be fine for non-professionals like myself.

One day after retirement, I'd even write an 'afterboot' script; asking
about ssh protocol version and RootLogin; as well as the three aliases,
etc. 
I also have to look up the fstab entry for ALTROOT regularly; adduser.conf;
 and so on and so forth.
I am sure that would make it easier for everyone newbie including myself
to get started.

2 Sen,

Uwe

Reply via email to