Re: Directory structure

[Nick Holland <nhollan@home.com>]

I was just getting ready to ask for an explaination of this.  Someone
else had commented that there was a "real reason" (which I figured --
I've seen lots of reason to respect the skills of the people who put
OpenBSD together!), but didn't say what it was.  Now I understand! 8)

Thanks for the clairification!
That link you gave looks VERY educational, too.  Gonna spend some time
on that, I can tell. 8)


In an unrelated issue, my appologies to the entire group for the
excessive my line lengths on past postings, didn't realize they were
going out that way (and thanks to the person who let me know). 
Hopefully, it is fixed now.

Nick.

"Adam Thompson, MCNE, MCSE" wrote:
> 
> Michael Richard wrote:
> > /var/named/ -> /etc/named       (this one seems to work fine)
> > /var/spool/ftp -> /home/ftp     (works fine too)
> > /var/www -> /etc/www            (for configuration files)
> >             /home/www           (for htdocs, icons and cgi-bin)
> >             /var/www            (for log files)
> 
> The whole point or /var is that if you have a shared-disk environment,
> EVERYTHING can be mounted read-only except /var.  "/var" is designated
> the area that contains machine-specific data that must be modified
> regularly.
> 
> "/etc" should be mountable read-only while in multi-user mode, so that
> the only way to change your system configuration is to boot single-user
> and remount /etc as read-write.
> 
> It's actually a security and manageability feature of sorts.
> 
> There is a discussion of this with historical background information in
> the FSSTND (which is Linux-centric) located at
> http://www.pathname.com/fhs/.
> 
> --
> Adam Thompson, MCNE, MCSE, CWT, A+
> Vice-President / Chief Technology Officer, Commerce Design Inc.
> <athompso@commerced.com>
> tel: (204) 942-1648, fax: (204) 989-8080, cell: (204) 782-6198