Craig, > I have been trying to implement a R/O root file system with SLES10 SP2 The paper was based on SLES 10 "vanilla", and the changes are specific to that version, I believe. Especially, on page 36 of the paper, the modifySystem() function in the mkror.sh script has the lines: patch $TGT/etc/init.d/boot.rootfsck < $rorDiffs if [ "$?" != 0 ]; then exit 49; fi
So if the boot.rootfsck script changed between SLES10 and SLES 10 SP2, then I would expect that the patch command would fail. By chance does mkror.sh exit with a return code of 49? You write: > You can see later on where boot.rootfsck, modified for the Read-Only root, gets executed, but at that point it is too late... That would seem to imply that mkror.sh has run and has succeeded. Then you write: > I start getting file system errors, because the minidisk containing the root file system is defined as R/O to the Linux guest. Well now I'm confused. We want a read-only root file system correct? I'm also a bit confused as to why you cite SLES 9. I know the steps in the paper are repeatable for a SLES 10 vanilla system. Have you tried the steps on that flavor of the distro? Maybe starting with SLES 10, which is the basis of the paper is a good place to start. This is part of the problem with writing a technical paper using a specific version of an OS as a basis - the specifics get stale quite quickly. Maybe if Rick T. is listening - has boot.rootfsck changed between SLES 10 and SLES 10 SP2? "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
