FOG EMMC compatability
-
Unfortunately, at this time, 1.2.0 uses a specific kernel. I talked to @Tom-Elliot about it and he said that 1.2.0 probably won’t work properly with a newer init.
Your option at this point is to try out the bleeding edge and see if the latest SVN version serves your needs for now.
-
@Jamie-Read SVN versions are very stable, lot of us use it
@cspence said:Unfortunately, at this time, 1.2.0 uses a specific kernel. I talked to @Tom-Elliot about it and he said that 1.2.0 probably won’t work properly with a newer init.
Your option at this point is to try out the bleeding edge and see if the latest SVN version serves your needs for now.
-
The most preferred method of upgrading to FOG Trunk is using subversion.
Here’s the article on how to do that: https://wiki.fogproject.org/wiki/index.php/SVN
-
i am getting the following error when trying to download ,svn: E175013 unable to connect to repository at URL ‘https://svn.code.sf.net/p/freeghost/code/trunk’
svn: E175013: Access to ‘p/freeghost/code/trunk’ forbidden
thanks -
@Jamie-Read Is your network blocking it?
-
most probably but i have configured the server to use a a proxy which has full access to everything
-
Is your FOG GUI setup to use the proxy?
-
i am attempting to setup a new svn fog server so currently there is no fog installed , do i need to install 1.2.0 first then run the svn? , we do have another fog server in place but i don’t want to do anything to that incase it stopped working
thanks -
You can install from svn directly, no need to install 1.2.0 first.
-
Also, i mis-understood orginally, SVN would need to be configured to allow for passing through your proxy.
http://stackoverflow.com/questions/1491180/how-to-configure-a-http-proxy-for-svn
-
okay so i have install subversion but there is no ~/.subversion file in the directory which it says you need to amment
-
@Jamie-Read No sure but look at the folder /etc/subversion/ .
Edit : the “server” file.
-
thanks for that , i have ammended that file with the proxy details but still getting error 403
