How do I cut a core?
Cutting a core removes all the user-specific and site-specific information in the core, and reduces it to a barebones core that has all the default objects and the root user.
All released cores are made with this process. It is also helpful for integrating changes from a non standard core into mainline development.
- grab a copy of the core's .db file, put it in a separate directory, along with a copy of moo and restart.sh
- run restart.sh with the core running on a different port.
- login as root.
- use /passwd to set the root password to something known. (and NOT your private corporation's root lily passwd.)
- be very sure you're on the right core.
- No, really.
- run $SETUP CORE-CONFIGURE
- You may see several BOOM:! diagnostic messages that can be ignored. technical note
- $shutdown the core.
- You now have a core with a .new extension on it. this is your "cut" core.
Technical Notes:
Those BOOM diagnostic messages are ignorable. At this stage they can even be removed. I added them because I was having trouble tossing objects linearly when the object system is really hierarchical. This has been fixed, inasmuch as is possible, but there are still places where this linear v hierarchical recycling problem still occurs. BOOM just means "we did it and trapped the error."
to top