From owner-freebsd-binup Tue Oct 22 11: 8: 4 2002 Delivered-To: freebsd-binup@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5C7937B401 for ; Tue, 22 Oct 2002 11:08:03 -0700 (PDT) Received: from centaur.acm.jhu.edu (centaur.acm.jhu.edu [128.220.223.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id C432243E75 for ; Tue, 22 Oct 2002 11:07:59 -0700 (PDT) (envelope-from jflemer@acm.jhu.edu) Received: by centaur.acm.jhu.edu (Postfix, from userid 556) id 7624013E9B; Tue, 22 Oct 2002 14:07:27 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by centaur.acm.jhu.edu (Postfix) with ESMTP id 758B437BF3 for ; Tue, 22 Oct 2002 14:07:27 -0400 (EDT) Date: Tue, 22 Oct 2002 14:07:27 -0400 (EDT) From: "James E. Flemer" Reply-To: "James E. Flemer" To: Subject: updating shared libs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-binup@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wow, there is traffic here once again. Anyway, I was wondering if anyone has ideas about how one would go about replacing shared libs (assuming they are in use by running procs). Will doing so cause any problems? I assume that renaming a file won't cause problems because the inode is preserved, so the VM will still know where the backing store is. But what about upgrading something like libjpeg that may be in use by lots of programs. How should a binup type program deal with this? It would be nice if whatever binup process could provide patch, rollback, commit type operations to test patches w/o committing them on a running system. This would need a safe way of messing w/ shared libs w/o breaking stuff though. -James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-binup" in the body of the message