| Title: | The setld and ULTRIX layered product installation/integration conference |
| Moderator: | SQM::DUFAULT |
| Created: | Thu Feb 08 1990 |
| Last Modified: | Wed Apr 23 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 359 |
| Total number of notes: | 1357 |
I'm just starting out with setld. I do have a lot of U*IX shell experience. Can someone pls tell me EXACTLY what the "keyword" RESERVED, as used in the Master Inv' file means, any tricks or things to be weary of, when using it, etc It seems to be far to quickly brushed over in all the setld doc I've seen, including the WWW pages. Thx Craig.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 356.1 | My unofficial "i'm just another user" take on it | TLE::TALCOTT | Wed Feb 12 1997 11:47 | 7 | |
Reserved directories are owned by the operating system rather than us layered-product weenies. Thus a typical mi file could start with 0 ./usr RESERVED 0 ./usr/opt RESERVED *** your files start here *** Trace | |||||
| 356.2 | That what I thought too, but... | OZROCK::THOMAN | The House Of Script | Thu Feb 13 1997 19:34 | 23 |
Re .1, >Reserved directories are owned by the operating system rather than us >layered-product weenies. Thus a typical mi file could start with I was just a little concerned it may of meant more than that after a case we saw. A fellow kit writter here put "RESERVED" on the dir /usr/examples in his .mi, since that dir will exist on the system before his kit is installed. When he went to test the install he got verify errors, and entries in the file "fverify" alerting him to that dir at fault. After changing it from RESERVED to the name of his kit's subset in the .mi, & rekitting, the installation completed succesfully. The OS was D/Unix 3.2c I believe. Thx Craig. | |||||