Re: Shock and Awe
- From: russotto@xxxxxxxxxxxxxxxxxxx (Matthew T. Russotto)
- Date: Sun, 25 Mar 2007 21:45:50 -0500
In article <PXlNh.4786$vI1.410@trnddc02>,
Wes Groleau <groleau+nntp@xxxxxxxxxxxxx> wrote:
Matthew T. Russotto wrote:
In article <LbmMh.18106$O_5.15491@trnddc03>,
Wes Groleau <groleau+nntp@xxxxxxxxxxxxx> wrote:
Matthew T. Russotto wrote:
It is. But modifying a file the way prebinding does is not the sameChanging bytes IN an open file is absurd!
as deleting one and putting a new one in its place.
Without some method of keeping changes coherent, it is. But it can be
quite useful if such methods exist.
In a multiuser database system, there is a reason for it, and extensive
code to keep it from causing problems. When you are merely recompiling
or tweaking an executable, make a new version and delete the old when
it is free.
Even Windows is smart enough to resist that.
Only Windows, so far as I know.
Windows is not the only system that has file locking.
Windows is the only system that prevents multiple processes from
opening a file without them demanding an explicit lock.
Now, if you want real fun, try changing a running application by
modifying the file on disk, then forcing the app to be paged out.
In the versions of Solaris that I worked with in the 1990s, you
don't really modify a file on disk. You write a new version and
tell the OS to delete the old one. Which it does when there are
no file descriptors using it. Until then, the processes owning
those file IDs continue to use the old version for paging or whatever.
You could do that, but you'd have to do so explicitly. There's nothing
in Solaris (or the old SunOS) to keep you from opening a file and
modifying it in place, while other processes are using it.
--
There's no such thing as a free lunch, but certain accounting practices can
result in a fully-depreciated one.
.
- Follow-Ups:
- Re: Shock and Awe
- From: Wes Groleau
- Re: Shock and Awe
- References:
- Re: Shock and Awe
- From: Wes Groleau
- Re: Shock and Awe
- From: Matthew T. Russotto
- Re: Shock and Awe
- From: Wes Groleau
- Re: Shock and Awe
- Prev by Date: Re: Website Hosting Using Airport Base Station
- Next by Date: Re: Finally some solid competition for Photoshop.
- Previous by thread: Re: Shock and Awe
- Next by thread: Re: Shock and Awe
- Index(es):
Relevant Pages
|
Loading