> From: Bert Freudenberg
> 
> What I meant is that teh image looks in the image directory too, not just the VM 
> dir.
Makes sense, thanks for the clarification.


> But now that you mention it I remember seeing problems with resolving symlinks. 
> Not in this VM but an older one, but under Linux, yes.
If I wanted to look into that and contribute the changes, where and how would I start?

Have fun,
Markus

> 
> - Bert -
> 
> On 17.09.2009, at 22:09, Markus Lampert wrote:
> 
> > To clarify, my setup looks like this:
> > 
> > /home/mlampert/.squeak/          ... images and changes
> >   vms       ... all VMs I have installed
> >     Squeak-3.10-6/...
> >     Squeak-3.11.3.2135-linux_i386/...
> >   vm-3.10-6 -> 
> vms/Squeak-3.10-6/i686-pc-linux-gnu/usr/local/lib/squeak/3.10-6/
> >   vm-3.11.3 -> vms/Squeak-3.11.3.2135-linux_i386/bin
> >   vm -> vm-3.11.3    .... (or -> vm-3.10.6)
> > 
> > Additionally I added a symlink 'vms/Squeak-3.10-6/SqueakV39.sources -> 
> /usr/lib/squeak/SqueakV39.sources'. So far vm pointed to vm-3.10-6 and the image 
> found the sources file.
> > 
> > When I added the 3.11.3 vm I added the symlink 
> 'vms/Squeak-3.11.3.2135-linux_i386/lib/SqueakV39.source -> 
> /usr/lib/squeak/SqueakV39.sources'. After pointing vm to vm-3.11.3 I encountered 
> the problems described below. (well, of course I forgot to create the sources 
> symlink initially ...).
> > 
> > Only after creating the symlink '/home/mlampert/.squeak/SqueakV39.sources -> 
> /usr/lib/squeak/SqueakV39.sources' is the trunk image/vm-3.11.3 combination 
> happy.
> > 
> > Have fun,
> > Markus
> > 
> > 
> > 
> > ----- Original Message ----
> > From: Markus Lampert 
> > To: The general-purpose Squeak developers list 
> 
> > Sent: Thursday, September 17, 2009 12:47:13 PM
> > Subject: Re: [squeak-dev] 3.11.3.2135 for Unix
> > 
> >>> If you start the VM with an image and it can't find the SqueakV39.sources it 
> will pop up a confirmation box saying the sources file does not exist in the 'VM 
> directory'. Creating a symlink to the sources file in the VM directory does not 
> quite resolve the problem. A menu is brought up on startup saying that 
> SqueakV39.sources does not exist giving several options of choosing another name 
> and so on. It seems the VM expects SqueakV39.sources to be in the same directory 
> as the image file, not the VM itself (doesn't make a big difference but the 
> dialog box is misleading).
> >> 
> >> 
> >> This has nothing to do with the VM, the image is looking for the sources.
> > 
> > Interesting, using the same image (trunk about 1 week old) with the 3.10-6 vm 
> it expects the sources in the vm directory. May the difference in behaviour be 
> related to resolving symbolic links?
> > 
> > Have fun,
> > Markus
> > 
> > 
> > 
> > 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com