On Tue, Jan 15, 2002 at 11:47:04AM -0500, David Sowsy wrote: > > Another, maybe nicer solution would be a 'lock' on the systemfiles, > > so that no application can put or change anything in /boot/beos, and > > if an application tries, the OS pops up a password dialog to let that > > application (and it's child processes) to override the protection, > > until the application quits. > > That sounds pretty annoying. Other OSes do things this way. This would only be needed when installing software, since that is the only time systemfiles in /boot/beos are being written. Logs and configuration for applications go elsewhere on the filesystem. Mark-Jan