Re: http daemon suggestion/proposal

["Brian C. White" <bcwhite@verisim.com>]

> I'm likely to change /usr/bin, since I often install new software.
> Therefore, all new software should be installed in /var/bin instead.
> 
> Installing a new cgi-bin is similar to installing a new program, and both
> require a writeable /usr.  If we want to support a completely non-writeable
> /usr, while still allowing installation of new software, then perhaps
> we should look into a mechanism to solve the general case.  (/opt, perhaps.
> In any case, we would need relocateable packages.)
> 
> /var is for data that is likely to change during normal operation.
> Installing new software is not normal operation.

This is the way I look at it...

/usr (except /usr/local and /usr/share) is for files installed by the system
maitenence tool (i.e. "dpkg" & friends).  Installing new cgi-bin programs
is something that may want to be done by the local sysadmin and thus should
go in /var or /usr/local or /usr/share just like local programs would.
(Note that the future of /usr/share is still being discussed, as I understand
it.)

I might want to install new cgi-bin programs on a system that has /usr
mounted from CD-Rom or a read-only NFS mount.

                                        Brian
                               ( bcwhite@verisim.com )

-------------------------------------------------------------------------------
    In theory, theory and practice are the same.  In practice, they're not.