Last I knew, there was still an issue of symbolic links not being supported
by Virtualbox on windows.  Is that not a problem any more?

--Ned.

On Tue, Oct 18, 2016 at 12:33 PM, <benali.a...@gmail.com> wrote:

> HI Yarko / Felipe ,
>
> i m trying to install devstack on my windows laptop ( 16GB RAM ) .
> what are the prerequisites to this installation ? any SW needed ?
>
> Regards ,
> Amine
>
>
> On Friday, January 31, 2014 at 7:59:41 PM UTC+1, Felipe Montoya wrote:
>>
>> Hi Yarko,
>>
>> yes, this is what I used to do, but it was not working for me with the
>> devstack-empanada. So my workaround it to get to the point, where it works
>> again.
>>
>> --Felipe
>>
>> On Friday, January 31, 2014 1:45:47 PM UTC-5, Yarko Tymciurak wrote:
>>>
>>> Had you seen this?   (sorry for the re-send; forgot "reply-all" before):
>>>
>>> https://github.com/edx/edx-platform/wiki/Simplified-install-
>>> with-vagrant#wiki-dealing-with-line-endings-and-symlinks-under-windows
>>>
>>>
>>> On Fri, Jan 31, 2014 at 12:40 PM, Felipe Montoya <luisfm...@gmail.com>
>>> wrote:
>>>
>>>> Quick update:
>>>>
>>>> The reason why the files were working without the symlinks being
>>>> processed was that they got deleted in the copy. So please un-delete them
>>>> using git, and deal with the symlinks as the wiki explains. (The first
>>>> command is not needed: git rm --cached -r . && git reset --hard)
>>>>
>>>> --Felipe
>>>>
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "General Open edX discussion" group.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/edx-code/dfcf1970-72d2-4e82-ab53-19bf01b2fecc%40googlegroups.com
> <https://groups.google.com/d/msgid/edx-code/dfcf1970-72d2-4e82-ab53-19bf01b2fecc%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"General Open edX discussion" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/edx-code/CAGtJPNMiQRp%3DN_7TkiUsRqQybVx93MQDS6A3UB_EyfYw0CVjQQ%40mail.gmail.com.

Reply via email to