Terry Lambert wrote:
Wesley Morgan wrote:
It's also unfortunate that this protection does not seem to extend to
libaries. I've had some in-use X libraries get overwritten with some very
colorful results.
So send patches.
I did a year ago :-) See PR 37554. (Not the original patch, the
s
On Thu, 2003-09-04 at 19:20, Tim Kientzle wrote:
> Depends on how you're installing the binary. It has always been
> safe to do either of the following:
>* Rename the current executable and then install the new one.
>* Unlink the current executable and then install the new one.
> Many too
Wesley Morgan wrote:
> On Thu, 4 Sep 2003, Scott M. Likens wrote:
> > On Thu, 2003-09-04 at 07:44, Paul Richards wrote:
> > > Overwriting a file that's currently executing results in a "Text file
> > > busy" error.
> >
> > this "feature" has always existed in FreeBSD for as long as I remember.
>
>
Paul Richards wrote:
> Overwriting a file that's currently executing results in a "Text file
> busy" error.
>
> When did this start happening?
>
> This was something that was fixed way back on FreeBSD but it seems to be
> a problem again.
You are opening an existing file for write. You need to
On Thu, Sep 04, 2003 at 09:36:31AM -0700 I heard the voice of
Mikko Ty?l?j?rvi, and lo! it spake thus:
>
> If you are into foot shooting, you can always overwrite a shared lib,
> such as libc.so, and watch (almost) all your programs crash and burn :-)
*raise hand*
Yup. Got the t-shirt.
Nothing
On Thu, 4 Sep 2003, Scott M. Likens wrote:
> On Thu, 2003-09-04 at 07:44, Paul Richards wrote:
> > Overwriting a file that's currently executing results in a "Text file
> > busy" error.
> >
> > When did this start happening?
> >
> > This was something that was fixed way back on FreeBSD but it seem
:
:Tim
:
:P.S. I wonder if demand-paging of executables is still a win for
:program startup on modern systems with dynamically-linked executables?
:Large reads are a lot more efficient, and it seems that dynamic
:linking might cause more startup thrashing. Hmmm...
Yes, they are a big win 95%
Paul Richards wrote:
Overwriting a file that's currently executing results in a "Text file
busy" error.
I guess there are folks around who don't know this:
When you execute a program, the program is not simply copied
into memory. Instead, the kernel keeps the file open and pages the
executable in
On Thu, Sep 04, 2003 at 02:44:13PM +, Paul Richards wrote:
> Overwriting a file that's currently executing results in a "Text file
> busy" error.
>
> When did this start happening?
>
> This was something that was fixed way back on FreeBSD but it seems to be
> a problem again.
>
cp -f
Cheer
On Thu, 4 Sep 2003, Scott M. Likens wrote:
> On Thu, 2003-09-04 at 07:44, Paul Richards wrote:
> > Overwriting a file that's currently executing results in a "Text file
> > busy" error.
> >
> > When did this start happening?
> >
> > This was something that was fixed way back on FreeBSD but it seem
On 04-Sep-2003 John Polstra wrote:
> On 04-Sep-2003 William K. Josephson wrote:
>> On Thu, Sep 04, 2003 at 08:02:50AM -0700, Scott M. Likens wrote:
>>> Every single 'flavor' of Unix/Unices has always had this feature. I've
>>
>> No, just recent ones. One use to be able to page in from the wrong
On 04-Sep-2003 William K. Josephson wrote:
> On Thu, Sep 04, 2003 at 08:02:50AM -0700, Scott M. Likens wrote:
>> Every single 'flavor' of Unix/Unices has always had this feature. I've
>
> No, just recent ones. One use to be able to page in from the wrong
> binary with rather entertaining results
On Thu, Sep 04, 2003 at 08:02:50AM -0700, Scott M. Likens wrote:
> That's like trying to reinstall X while running in X.
> You're just asking for problems.
This has worked for me many times in the past :)
Of course it's on a (essentially) single user desktop, and I do a restart
after portupgrade
On Thu, 2003-09-04 at 07:44, Paul Richards wrote:
> Overwriting a file that's currently executing results in a "Text file
> busy" error.
>
> When did this start happening?
>
> This was something that was fixed way back on FreeBSD but it seems to be
> a problem again.
>
> Paul.
this "feature" ha
On (2003/09/04 14:44), Paul Richards wrote:
> Overwriting a file that's currently executing results in a "Text file
> busy" error.
>
> When did this start happening?
>
> This was something that was fixed way back on FreeBSD but it seems to be
> a problem again.
Really? I've never seen it "fixe
15 matches
Mail list logo