4.5.1 or 4.5.2 for win?

85 views
Skip to first unread message

Rolandb

unread,
Aug 7, 2010, 3:37:16 PM8/7/10
to sage-support
Hi,

I'm thrilled that a new VMware version is out. But looking at
METALINK, I found version 4.5.2 for win while other versions are
4.5.1? See www.sagemath.org/mirror/win/meta/sage-vmware-4.5.2.zip.

Roland

Alex Ghitza

unread,
Aug 7, 2010, 7:47:11 PM8/7/10
to Rolandb, sage-support

Hi,

Sage 4.5.2 was just released. I had some insider information and
obtained the final tar while it was still being tested on some
platforms, and built it into vmware. Thus the somewhat unusual
situation of sage-vmware-4.5.2 preceeding the official release by half a
day or so.

So it should be fine to use the sage-vmware-4.5.2 that's up now.


Best,
Alex


--
Alex Ghitza -- http://aghitza.org/
Lecturer in Mathematics -- The University of Melbourne -- Australia

Rolandb

unread,
Aug 8, 2010, 3:16:34 AM8/8/10
to sage-support


On 8 aug, 01:47, Alex Ghitza <aghi...@gmail.com> wrote:
> Hi,
>
> On Sat, 7 Aug 2010 12:37:16 -0700 (PDT), Rolandb <rola...@planet.nl> wrote:
> > I'm thrilled that a new VMware version is out. But looking at
> > METALINK, I found version 4.5.2 for win while other versions are
> > 4.5.1? Seewww.sagemath.org/mirror/win/meta/sage-vmware-4.5.2.zip.
>
> Sage 4.5.2 was just released.  I had some insider information and
> obtained the final tar while it was still being tested on some
> platforms, and built it into vmware.  Thus the somewhat unusual
> situation of sage-vmware-4.5.2 preceeding the official release by half a
> day or so.
>
> So it should be fine to use the sage-vmware-4.5.2 that's up now.
>
> Best,
> Alex

There is a (huge) difference between win version 4.5.1 and 4.5.2.
In version 4.5.1 an external network was setup, so I can use Sage via
Windows Firefox using the address 192.168.236.128.
The 4.5.2 version gives the warning that an external network was not
setup.
Is there an easy way to solve this? Thanks in advance!
Roland






>
> --
> Alex Ghitza --http://aghitza.org/

Alex Ghitza

unread,
Aug 8, 2010, 4:46:13 AM8/8/10
to Rolandb, sage-support

Hi,

On Sun, 8 Aug 2010 00:16:34 -0700 (PDT), Rolandb <rol...@planet.nl> wrote:
>
> There is a (huge) difference between win version 4.5.1 and 4.5.2.
> In version 4.5.1 an external network was setup, so I can use Sage via
> Windows Firefox using the address 192.168.236.128.
> The 4.5.2 version gives the warning that an external network was not
> setup.
> Is there an easy way to solve this? Thanks in advance!

The short answer is: I don't know.

Going from 4.5.1 to 4.5.2, I made no changes to either the Ubuntu
operating system that powers the virtual machine, nor to the settings of
the virtual machine itself. The only thing that changed was the folder
"sage", which now contains sage-4.5.2 instead of sage-4.5.1.

I also tested the image on my laptop (which runs Mac OS X, not Windows,
but that should not matter), and I can use the host's web browser to
access the virtual machine's Sage notebook without any problems.

So that's why I don't know what's going on at your end. The best I can
do at the moment is to suggest renaming the sage-vmware folder and
starting over from sage-vmware-4.5.2.zip (if you still have it).


Best,
Alex


--
Alex Ghitza -- http://aghitza.org/

jockothy

unread,
Aug 15, 2010, 6:50:13 AM8/15/10
to sage-support
Hi!

>
> There is a (huge) difference between win version 4.5.1 and 4.5.2.
> In version 4.5.1 an external network was setup, so I can use Sage via
> Windows Firefox using the address 192.168.236.128.
> The 4.5.2 version gives the warning that an external network was not
> setup.
> Is there an easy way to solve this? Thanks in advance!
> Roland
>

I had the same experience. With a bit of Googling I found a solution
that worked for me:

http://blog.timc3.com/2010/05/04/vmware-ubuntu-ip-address-change/

I ended up with the IP address 192.168.171.128 and a working Sage that
I could use via Firefox on the host machine as well as the VM.

Hope this helps.

Jim

Rolandb

unread,
Sep 8, 2010, 2:25:53 PM9/8/10
to sage-support


On 15 aug, 12:50, jockothy <jgmcc...@gmail.com> wrote:
> Hi!
>
>
>
> > There is a (huge) difference between win version 4.5.1 and 4.5.2.
> > In version 4.5.1 an externalnetworkwas setup, so I can use Sage via
> > Windows Firefox using the address 192.168.236.128.
> > The 4.5.2 version gives the warning that an externalnetworkwas not
> > setup.
> > Is there an easy way to solve this? Thanks in advance!
> > Roland
>
> I had the same experience.  With a bit of Googling I found a solution
> that worked for me:
>
> http://blog.timc3.com/2010/05/04/vmware-ubuntu-ip-address-change/
>
> I ended up with the IP address 192.168.171.128 and a working Sage that
> I could use via Firefox on the host machine as well as the VM.
>
> Hope this helps.
>
> Jim

Hi Jim, (and others)

Version 4.5.3 has the same problem. Could you elucidate somewhat more
on what you did exactly.
Where did you put the command sudo rm /etc/udev/rules.d/70-
persistent-net.rules ?
N.B.: I'm using VMware 3.1.1, and I have no knowledge of UNIX

Thanks in advance!

Roland

jockothy

unread,
Sep 9, 2010, 4:54:26 PM9/9/10
to sage-support


On Sep 8, 7:25 pm, Rolandb <rola...@planet.nl> wrote:

> Version 4.5.3 has the same problem. Could you elucidate somewhat more
> on what you did exactly.
> Where did you put the command sudo rm /etc/udev/rules.d/70-
> persistent-net.rules ?
> N.B.: I'm using VMware 3.1.1, and I have no knowledge of UNIX

Hi Roland

I'm also using VMPlayer 3.1.1, and I have some UNIX knowledge from
around
1994!

When the Sage VM has started up, there are three icons: Sage Notebook,
Sage,
Terminal. Double-click the Terminal icon to open a command window;
there
should be a prompt like sage@ubuntu:~$ and a flashing black cursor.
This is
where you type the command:

sudo rm /etc/udev/rules.d/70-persistent-net.rules

then press Enter. It will ask for the password for the sage user; the
password is sage, so type it and press Enter. Close the Terminal
window.

If you now open the Sage Notebook, it may work. I didn't think to try
it at
this stage. I shut down the VM and restarted it, and everything
worked
perfectly after that.

Good luck!

Jim

Rolandb

unread,
Sep 10, 2010, 12:32:35 AM9/10/10
to sage-support
Jim, tnx!

After typing the password sage, I got the message
rm: cannot remove `/etc/udev/rules.d/70-persistent-net.rules': No such
file or directory
You had the same?

Roland

HarryK

unread,
Sep 10, 2010, 11:56:36 AM9/10/10
to sage-support
Hi,

I had the same problem.
After starting sage-vmware.vmx I just clicked on
VMware Player -> Troubleshoot -> Reset
and this solved the problem.
I'm using sage 4.5.3 on VMware player 2.5.

Maybe worth a try.

Harald

Rolandb

unread,
Sep 10, 2010, 2:35:58 PM9/10/10
to sage-support
Hi,

THIS IS THE FINAL TRICK!

Tnx!

jockothy

unread,
Sep 11, 2010, 10:32:03 AM9/11/10
to sage-support
On Sep 10, 5:32 am, Rolandb <rola...@planet.nl> wrote:
> Jim, tnx!
>
> After typing the password sage, I got the message
> rm: cannot remove `/etc/udev/rules.d/70-persistent-net.rules': No such
> file or directory
> You had the same?
>

Hi again!

The "sudo rm ..." technique worked for me for both 4.5.2 and 4.5.3.
However, it sounds as if HarryK's suggestion has worked so your
problem is solved.

I've done some experiments and I've found yet another way to get
things working. When using VMware Player 3.1.1 (and WIndows XP SP3),
the Sage 4.5.2 and 4.5.3 VMs produced a message when first opened:

"This virtual machine may have been moved or copied.

In order to configure certain management and networking features,
VMware Player needs to know if you moved this virtual machine or if
you copied it.

If you don't know, answer 'I copied it'."

With Sage 4.5.2, I selected "I copied it", and had to do the "sudo rm /
etc..." thing. With Sage 4.5.3, I tried selecting "I moved it", and
the Sage Notebook opened correctly first time with external network
access correctly set up. I suppose this makes some sort of sense, as
the VM has been moved to my PC from somewhere else.

I thought it was worth posting this for future reference.

Happy Sageing!

Jim
Reply all
Reply to author
Forward
0 new messages