Evgeny wrote:

> Hello guys
>
> I have EMC2 verson 3.3
>
>   
3.3?
> System based on puppy linux and works well.
>
>   
Nice to see emc2 still works on Puppy Linux (as, of course, it should).
> I have one small problem and do not have ideas how I can solve it 
>
> In emc script I changed variables 
> EMC2_CONFIG_PATH="~/emc2/configs:/usr/local/etc/emc2/configs:/usr/share/doc/emc2/examples/sample-configs"
> EMC2_NCFILES_DIR=/usr/share/emc/ncfiles
> to
> EMC2_CONFIG_PATH=/mnt/home/ems/emc-config
> EMC2_NCFILES_DIR=/mnt/home/ems/ncfiles
>
> when I start system , it takes config from directory /mnt/home/ems/emc-config
> but when I try to open file, in onen file dialog, I have default directory = 
> /initrd/mnt/dev_save/emc/emc-config/stepper
>   
was this meant to say /initrd/mnt/dev_save/ems/emc-config/stepper ?
> what really is /mnt/home/ems/emc-config + configuretion directory.
>
>   
I'm not sure what you intended to say here.
> Any ideas what is a problem ?
>
> Best Regards
> Evgeny
Evgeny:

Maybe I'm not understanding your question but I believe your system is 
working correctly. If I recall correctly, in Puppy Linux, /mnt/home is a 
symbolic link to /initrd/mnt/dev_save. Hence as far as EMC2 is 
concerned, your variables are actually

EMC2_CONFIG_PATH=/initrd/mnt/dev_save/ems/emc-config
EMC2_NCFILES_DIR=/initrd/mnt/dev_save/ems/ncfiles


You don't notice this when EMC2 starts up because it doesn't present you with a 
menu then.

Just my two cents worth.

Regards,
Kent



------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to