> A couple times I have wondered if it would make sense to > chmod the .../data files once services are running... > or maybe they should start off non-writable and startups > should embody a pattern like this? > > chmod 664 /dev/sdC0/fossil > fossil -f /dev/sdC0/fossil > chmod 444 /dev/sdC0/fossil
On non-terminals, the problem goes away because only hostowner has read/write access to them. Making the disks read-only by default would just frustrate people who actually have legitimate use for the disks! All the programs that access disks (think dossrv, 9660srv, fdisk, prep, etc.) would then try to chmod +w, making the permissions somewhat useless if you're running as hostowner. Of course, one could put a chmod -w /dev/sd*/data in termrc if one is worried about making mistakes. Russ
