home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!utcsri!utcs.toronto.edu!cks
- Newsgroups: comp.sys.dec
- From: cks@hawkwind.utcs.toronto.edu (Chris Siebenmann)
- Subject: Re: Upgrading to 65+ users
- Message-ID: <1992Aug26.105302.5261@jarvis.csri.toronto.edu>
- Organization: Ziebmef home away from home
- References: <10958@platypus.uofs.uofs.edu> <1992Aug20.035716.11424@nntpd2.cxo.dec.com>
- Date: 26 Aug 92 14:53:02 GMT
- Lines: 20
-
- alan@nabeth.enet.dec.com (Alan Rollow - Alan's Home for Wayward Tumbleweeds.) writes:
- | With LMF I believe some part of LMF looks for the file [/upgrade]
- | and fakes up a LMF database entry based on the upgrade file.
-
- I found out the hard way (well, it wasn't very hard, just some
- headscratching) that LMF only does this if it's building a database
- from scratch; running 'lmf reset' afterwards does no good. So if you
- install a /upgrade on a already running 4.0+ system, make sure to save
- your keys somehow[*], rm /usr/adm/lmf/ldb, and only then run lmf reset
- and reload your keys.
-
- [*: I'd tell you how to do this, except I don't know; we have no PAKs
- loaded except the one we get from /upgrade, so it's never been
- a problem.]
- --
- When we get calls from faculty and staff regarding problematic
- software, we always ask if they have a backup. We got this
- *classic* response today "Well, I thought I had a backup, but
- she refused to type it in again..." - Lou Anschuetz
- cks@hawkwind.utcs.toronto.edu ...!{utgpu,utzoo,watmath}!utgpu!cks
-