SUMMARY Update: setld "not installed"
> Dr. Blinn sent some additional information which I thought was very
> useful:
>
> "Here's the deal -- if a subset is in fact installed, then there
> is a lock file (.lk) that corresponds to the other files that are
> the database data for the subset. If there is no .lk file, then
> you can remove ALL of the other files (.inv, .scp, .ctrl) for the
> subset. But they will come back (whether you want them or not)
> as soon as the "setld" utility again sees the original media that
> has the installable kit on it -- because "setld" ALWAYS copies the
> software management database files from the original kit into the
> /usr/.smdb. directory, and it will OVERWRITE whatever is in the
> directory with the files from the kit (it looks in the kit area
> for an "instctrl" directory, and finds the subsets in the kit via
> the file names in that directory). So removing the files may not
> do what you want long term -- because they may come back. But, if
> you do NOT install the subset, then the files are pure overhead,
> and if you don't want them on your system, you can remove them. ...
> [L]ike many things that are hidden files or in hidden directories, you
> have to know what they are used for and where they come from or you may
> accidentally break something if you just remove them (some people go
> off looking for the .proto.. or .new.. or .merge.. files and remove
> them, and that CAN break a subsequent update)."
>
> Many thanks to Dr. Blinn for the clarification.
>
> Bill
>
>
>
> -----Original Message-----
> From: Skulley, William [SMTP:William.Skulley_at_rfets.gov]
> Sent: Thursday, November 08, 2001 6:56 AM
> To: 'tru64-unix-managers_at_ornl.gov'
> Subject: SUMMARY: setld "not installed"
>
> Several people suggested setld -i | grep -iv 'not installed' or similar as
> a
> better way of handling the excess information. Also, some folks said that
> this would work fine (and it did appear to work on a test system without
> issue), however Debra LaGattuta from Compaq sent the following:
>
> "*Do not* remove any files from the /usr/.smdb. directory.
> This directory is the software management database on your system.
> Modifying or deleting files in this directory can cause potential
> problems for future updates, patches, and dependency issues for
> future software loads. It is recommended that you do not manually
> modify the contents of this directory. If you do, and you have
> subsequent software management problems, there may be no recourse
> for Compaq support personnel because this database cannot be recreated."
>
> Given that I can just filter out the information I don't need it seems
> safest to just do so and not mess with the /usr/.smdb. directory.
>
> Thanks to:
> Lucien Hercaud
> Dr. Thomas Blinn
> Dan Harrington
> Alan at cpqcorp
> Olle Eriksson
> Debra LaGattuta
>
> Bill
>
>
> > -----Original Message-----
> > From: Skulley, William [SMTP:William.Skulley_at_rfets.gov]
> > Sent: Monday, November 05, 2001 10:39 AM
> > To: Tru64 Mailing List (E-mail)
> > Subject: setld "not installed"
> >
> > When I run setld -i on my Tru64 5.1 systems some packages come back as
> > "not
> > installed". These are (apparently) packages I don't need as I am
> running
> > ok
> > without them. As near as I can tell, I can get rid of the listing all
> > together by removing the <package name>.ctrl, .inv. and .scp files from
> > /usr/.smdb. (the only files these particular packages have). Is there
> any
> > reason I should not do this and/or is there a better way? Is there any
> > reason I (or the system) would want to know that a particular package is
> > not
> > installed? As near as I can tell its just needless clutter but I might
> be
> > missing something(s).
> >
> > Thanks
> > Bill Skulley
Received on Thu Nov 08 2001 - 15:12:38 NZDT
This archive was generated by hypermail 2.4.0
: Wed Nov 08 2023 - 11:53:42 NZDT