This article is from a FAQ concerning SCO operating systems. While some of the information may be applicable to any OS, or any Unix or Linux OS, it may be specific to SCO Xenix, Open There is lots of Linux, Mac OS X and general Unix info elsewhere on this site: Search this site is the best way to find anything.
to re-mount /stand read-write. After you have finished, use
to return it to its default state.
It would probably be a good idea to follow a procedure similar to this:
btmnt -w cd /stand cp unix unix.good cd btmnt -d
Unless, of course, "unix" is not known to be a good kernel. As you can have as many copies as will fit, and boot from any of them simply by typing their name at the "Boot:" prompt, it's not a bad idea to have at least one "unix.safe" or "unix.emergency".
Of course you can't fit very many if the /stand filesystem was created at its default size of 15MB. As disks got larger, I'd give /stand a 30MB or larger size just to allow room for other kernels.
This "btmnt" command was used primarily by the SCO kernel linking scripts to update the /stand (SCO's boot fs partition) with a new kernel. Why not just use mount commands? I don't know - maybe because was needed in enough places that they wanted easy syntax.
Got something to add? Send me email.
Anyone even peripherally involved with computers agrees that object-oriented programming (OOP) is the wave of the future. Maybe one in 50 of them has actually tried to use OOP – which has a lot to do with its popularity (Steve Steinberg)