🚀 go-pugleaf

In article <1993Jan9.023523.861@leland.Stanford.EDU>, dhinds@leland.Stanford.EDU (David Hinds) writes:
|> [[ omitted: use of "versions" to list config files. ]]
}> But this still leaves out a few system files
|> that I've changed but which are not known to inst as configuration
|> files.  These will still get clobbered when I upgrade IRIX, and I
|> will have to keep track of them on my own.

1. Let me play back what I understand you to be saying.

    If you have intentionally modified a normal inst'ed file, a
    file not known as a config file to inst, then you would like
    to tell inst, to treat this file as if it were a config
    file:

	* naming upgrade versions with a .N suffix,

	* listing that file in the output of "versions changed",

	* giving you a chance to merge in your localisms, and
	
	* letting you list all config files, for cloning systems.

2. /usr/lib/inst/userlist.exc

    |> I noticed that /usr/lib/inst/userlist.exc is also not a
    |> configuration file.  It might be nice if it were...

    Userlist.exc is like any other config file that inst never
    installed in the first place.  So by the present understanding of
    inst (which this thread might change), it's not a config file.

-- 

				I won't rest till it's the best ...
				Software Production Engineer
				Paul Jackson (pj@sgi.com), x1373