[7.4] [BUG] Launching an image gives write permission to it

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[7.4] [BUG] Launching an image gives write permission to it

Martin McClure
In VW7.4, it looks like just launching VW with an image that you own
gives you write permission to the image file, even if you didn't have
that previously.

This is on Linux, I haven't tried other platforms.

I keep a "clean" image around that has various extra development tools
around. To keep it clean, I set the permissions of the image and changes
files so I cannot write them:

   mmcclure@lehr ~ $ cd /lehr1/users/mmcclure/apps/vw74/martin/
   mmcclure@lehr /lehr1/users/mmcclure/apps/vw74/martin $ ls -l Tools.*
   -r--r--r-- 1 mmcclure users   425110 May 17 16:00 Tools.cha
   -r--r--r-- 1 mmcclure users 16845684 Jun 12 10:43 Tools.im


Now I launch VW:

   export VISUALWORKS=/lehr1/users/mmcclure/apps/vw74
   $VISUALWORKS/bin/linux86/vwlinux86gui Tools.im &

It launches normally, but the image file is no longer write-protected!

   mmcclure@lehr /lehr1/users/mmcclure/apps/vw74/martin $ ls -l Tools.*
   -r--r--r-- 1 mmcclure users   425110 May 17 16:00 Tools.cha
   -rw-r--r-- 1 mmcclure users 16845684 Jun 12 10:43 Tools.im

This seems like a bug. I do NOT want to be able to save this image. I DO
want to be able to "save as" this image under a different name.

-Martin

Reply | Threaded
Open this post in threaded view
|

Re: [7.4] [BUG] Launching an image gives write permission to it

Alan Knight-2
Thanks. This does reproduce, and I've created AR 50949 for it, although I don't know why it falls to me to be creating VM ARs. Perhaps if certain VM engineers got around to reading their mail... :-)

At 01:56 PM 12/06/2006, Martin McClure wrote:

>In VW7.4, it looks like just launching VW with an image that you own gives you write permission to the image file, even if you didn't have that previously.
>
>This is on Linux, I haven't tried other platforms.
>
>I keep a "clean" image around that has various extra development tools around. To keep it clean, I set the permissions of the image and changes files so I cannot write them:
>
>  mmcclure@lehr ~ $ cd /lehr1/users/mmcclure/apps/vw74/martin/
>  mmcclure@lehr /lehr1/users/mmcclure/apps/vw74/martin $ ls -l Tools.*
>  -r--r--r-- 1 mmcclure users   425110 May 17 16:00 Tools.cha
>  -r--r--r-- 1 mmcclure users 16845684 Jun 12 10:43 Tools.im
>
>
>Now I launch VW:
>
>  export VISUALWORKS=/lehr1/users/mmcclure/apps/vw74
>  $VISUALWORKS/bin/linux86/vwlinux86gui Tools.im &
>
>It launches normally, but the image file is no longer write-protected!
>
>  mmcclure@lehr /lehr1/users/mmcclure/apps/vw74/martin $ ls -l Tools.*
>  -r--r--r-- 1 mmcclure users   425110 May 17 16:00 Tools.cha
>  -rw-r--r-- 1 mmcclure users 16845684 Jun 12 10:43 Tools.im
>
>This seems like a bug. I do NOT want to be able to save this image. I DO want to be able to "save as" this image under a different name.
>
>-Martin

--
Alan Knight [|], Cincom Smalltalk Development
[hidden email]
[hidden email]
http://www.cincom.com/smalltalk

"The Static Typing Philosophy: Make it fast. Make it right. Make it run." - Niall Ross