(FYI, we at Sun in Menlo Park, CA are going to be offline until next Monday because all of our mail/home directory machines are down for some power upgrades over our holiday. Apologies in advance for delayed responses.)
Brad Mitchell wrote: > Hi there, > > I hope this is indeed posted in the right area. > > In the past my company has produced an application which runs as an > appliance on Solaris 8 & 9. By running as an appliance I mean, > switch it on, switch it off. No FS problems as the system is > essentially running in read only. The only means by which data is > persisted is by using some of the spare slices to store data. In our > case, we had some which contained config files and others which > contained log files. These files would get stored on a "PRIMARY" and > a "BACKUP" slice so even if the system was turned off during a write > operation, the application would still be able to recover. > > Part of the project/application guidelines was to be able to deploy > in a rugged environment using as little "moving-parts" hardware as > possible. At the start we used and still use the cPCI architecture > and flash memory. In the past it has been Sandisk Flash cards and > more recently, due to flash cards no longer working, PQi flask 2.5" > ide drives. > > Going from Solaris 2.6 -> Solaris 8 -> Solaris 9 didn't seem to be an > issue in changing the rCS file and mounting root as RO and remounting > several parts of the OS copied into /tmp (Memory) - var, etc, opt etc > over existing disk copies. > > The problem I am having now is that Solaris 10 has changed > significantly and SMF is here and causing me issues. The issues come > down to /etc. More importantly (I'm guessing) is /etc/svc/*. > > I've had to change the time at which I copy the various file system > sub-directories to /tmp to be in the fs-root method. This has worked > for every sub-directory except for etc. Mounting /etc at this stage > completely halts the system startup. > > Allowing the boot process to continue with /etc as RO only causes > bucket-loads of errors for various services. > > Is there any way to change the dependence on /etc, i.e. change > repository/where to point at for SMF related files or is there a > point in the start up sequence where /etc could be safely replicated > across to RW in memory so as the system can start up? You'll want to start by looking at this bug: http://bugs.opensolaris.org/view_bug.do?bug_id=6608098 You may need that fix to continue sensibly. When you say you're mounting /etc, though... you're mounting something over /etc? Perhaps you're losing the /etc/svc/volatile tmpfs mount done before that? liane
