Date: Mon, 28 Jun 2004 14:51:02 -0400 From: Robert Huff <roberthuff@rcn.com> To: questions@freebsd.org Subject: Re: Updating source code manually Message-ID: <16608.26774.233788.432969@jerusalem.litteratus.org> In-Reply-To: <20040628172641.GB2963@shark.localdomain> References: <BAY15-F11fWM5nWGsRw00004a38@hotmail.com> <20040628134639.GA5699@shark.localdomain> <16608.13888.194802.955936@jerusalem.litteratus.org> <20040628172641.GB2963@shark.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
Sergey Zaharchenko writes: > When a file is open by a process, even if you unlink it and replace it > with another one, the original file will stay on disk until the last > file handle referencing it is closed. Yes. > I assume that holds true for libraries too. I don't ... but I must also allow as I'm talking at the border between understanding, informed speculation, and outright guesswork. > So, EXISTING processes aren't screwed. But, when a NEW > process is created, it references the NEW shared library, and if their > ABI's don't match --- BOOM!:) That was just a correction. > > I was under the impression that the OP already had KDE (and thus all > `father' ports) installed and up-to-date, and only wanted to patch a > file. I don't remember whether he said "up to date"; if so, then my worries are moot. I run a few KDE apps, but very little of the larger environment, Every time I have upgraded even one of those apps it has provoked a long, tortuous (and not always sucessful) session of upgrading other ports. > Please read more carefully. I mentioned '-w'. Mea culpa. Sorry. Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16608.26774.233788.432969>