Date: Tue, 13 Nov 2007 10:53:14 +0900 From: "Adrian Chadd" <adrian@freebsd.org> To: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> Cc: freebsd-stable@freebsd.org, Clint Olsen <clint.olsen@gmail.com> Subject: Re: Source upgrade from 5.5 to 6.X not safe? Message-ID: <d763ac660711121753u358d4705vc558a8a46d741af7@mail.gmail.com> In-Reply-To: <4736BB24.8010905@gmx.de> References: <20071102095628.GA796@0lsen.net> <472AF94B.1020600@gmx.de> <20071104200325.T91647@fledge.watson.org> <20071104211009.GC20861@0lsen.net> <4736BB24.8010905@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/11/2007, [LoN]Kamikaze <LoN_Kamikaze@gmx.de> wrote: > > If a binary/library that is currently used gets removed/replaced, it will be > copied to memory. The process will not even recognize this. Only restarting > the process will remove the old version from memory and cause the new one to > be used. I thought every OS did it like that, so I'm surprised that there are > systems causing problems in this case. Wha, when did that happen? I was always under the impression that binaries/libraries were demand paged in and referenced as a VM object via VFS; you could unlink/rename the file and the currently open reference would still be valid. (Admittedly I looked at this last in 4.x VFS.) Doing a rename-replace-unlink shouldn't clobber existing binaries that are using the library. Doing an -overwrite- of the existing file will cause exciting results. man install. :) Adrian -- Adrian Chadd - adrian@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d763ac660711121753u358d4705vc558a8a46d741af7>