I finished compiling sage 5.4 on ARM. I'll make a bdist available soon, and run "make ptestlong" afterwards (and report).
The compilation went mostly fine ; the only caveat is that in libm4rie, conversion.c took hours to build, and wouldn't build with MAKE="make -j 3" because it was too heavy for the box in that case.
I'd like to know if it works on more recent ARM-based hardware ; for example, if someone has an android tablet, it should be possible to install ubuntu in a chroot (I think there's an app for that, something like "Ubuntu noroot" or some such) and run the bdist from there.
I just started the tests, and as usual it starts by rebuilding the docs... I'll report when it will be finished.
I run sage on my tablet (asus transformer prime) precisely in that
way: over a ubuntu chroot. I have an old version installed though. I
have an ubuntu 10 chroot, where i compiled sage 4.8 (it was a pain:
over a week of comilation time).
Later i tested version 5.1 over a very minimal newer version of
ubuntu. It also runs fine.
Which version of ubuntu did you build it in?
On 16 nov, 12:53, Julien Puydt <julien.pu...@laposte.net> wrote:
> I'd like to know if it works on more recent ARM-based hardware ; for
> example, if someone has an android tablet, it should be possible to
> install ubuntu in a chroot (I think there's an app for that, something
> like "Ubuntu noroot" or some such) and run the bdist from there.
> I just started the tests, and as usual it starts by rebuilding the
> docs... I'll report when it will be finished.
> I run sage on my tablet (asus transformer prime) precisely in that
> way: over a ubuntu chroot. I have an old version installed though. I
> have an ubuntu 10 chroot, where i compiled sage 4.8 (it was a pain:
> over a week of comilation time).
What!? *A week*!?
If I don't err, this box has:
- 1Go of RAM (vs 512Mo)
- a quad-core nvidia tegra 3 (vs dual-core nvidia tegra 2)
Perhaps you didn't compile with export MAKE="make -j 3" ?
I was pondering buying one of those beasts (more powerful, more ram, good autonomy) to replace my poor netbook (toshiba AC100, whose hinges are starting to get bad -- mechanical problem), so I'm really interested in understanding what happens.
Well, the main problem was overheating. Compilation failed several
times, the device turned off by itself. I even think it got damaged,
since the power button stopped working properly (luckily asus was kind
enough to replace it)
On 16 nov, 17:07, Julien Puydt <julien.pu...@laposte.net> wrote:
> > I run sage on my tablet (asus transformer prime) precisely in that
> > way: over a ubuntu chroot. I have an old version installed though. I
> > have an ubuntu 10 chroot, where i compiled sage 4.8 (it was a pain:
> > over a week of comilation time).
> What!? *A week*!?
> If I don't err, this box has:
> - 1Go of RAM (vs 512Mo)
> - a quad-core nvidia tegra 3 (vs dual-core nvidia tegra 2)
> Perhaps you didn't compile with export MAKE="make -j 3" ?
> I was pondering buying one of those beasts (more powerful, more ram,
> good autonomy) to replace my poor netbook (toshiba AC100, whose hinges
> are starting to get bad -- mechanical problem), so I'm really interested
> in understanding what happens.
> Well, the main problem was overheating. Compilation failed several
> times, the device turned off by itself. I even think it got damaged,
> since the power button stopped working properly (luckily asus was kind
> enough to replace it)
Ouch. Bad, very bad, extremely bad!
I wouldn't have asked for a replacement but for a refound...
> Le 16/11/2012 16:53, mmarco a écrit :
>> I run sage on my tablet (asus transformer prime) precisely in that
>> way: over a ubuntu chroot. I have an old version installed though. I
>> have an ubuntu 10 chroot, where i compiled sage 4.8 (it was a pain:
>> over a week of comilation time).
> What!? *A week*!?
> If I don't err, this box has:
> - 1Go of RAM (vs 512Mo)
> - a quad-core nvidia tegra 3 (vs dual-core nvidia tegra 2)
> Perhaps you didn't compile with export MAKE="make -j 3" ?
> I was pondering buying one of those beasts (more powerful, more ram, > good autonomy) to replace my poor netbook (toshiba AC100, whose hinges > are starting to get bad -- mechanical problem), so I'm really interested > in understanding what happens.
IMHO Samsung's new ARM Chromebook is what you might want; unfortunately
the internal SSD is small, only 16GB (like on AC100), but 1.7GHz
dual-core Cortex A15. (and 12"(?) screen)
> IMHO Samsung's new ARM Chromebook is what you might want; unfortunately
> the internal SSD is small, only 16GB (like on AC100), but 1.7GHz
> dual-core Cortex A15. (and 12"(?) screen)
The internal storage is small, but since it's possible to stick a big SD in, that could fly (I need about 5Go for a system, 7Go for sage [did I mention it's too much?] and 20Go [mostly] static storage).
Now I'll only
(1) make sure it can run ubuntu instead of the crappy chrome OS it ships with
(2) wait until it's available in France (my AC100 isn't dead yet, so no hurry).
I can't help but notice that you didn't comment on the thread's main topic: the quite honest status of sage on ARM/ubuntu :-P
Oh, and btw, i think the real bottleneck with it was not the
processor, but the disk access. The processor is not bad (but again,
it can overheat), but the access to the internal sd disk is too slow.
Definitely, not a machine designed with this purpose in mind. And i
guess that pretty much the same could be said for almost every tablet
or smartphone: no cooling system, usually slow internal drives... they
are thought for another kind of usage.
But if your process is not very disk intensive, it does a decent job.
Foir instance, now that i have sage installed, it takes a long time to
startup, but after that, the speed is decent.
On 16 nov, 19:09, Julien Puydt <julien.pu...@laposte.net> wrote:
> > Well, the main problem was overheating. Compilation failed several
> > times, the device turned off by itself. I even think it got damaged,
> > since the power button stopped working properly (luckily asus was kind
> > enough to replace it)
> Ouch. Bad, very bad, extremely bad!
> I wouldn't have asked for a replacement but for a refound...
> Oh, and btw, i think the real bottleneck with it was not the
> processor, but the disk access. The processor is not bad (but again,
> it can overheat), but the access to the internal sd disk is too slow.
> Definitely, not a machine designed with this purpose in mind. And i
> guess that pretty much the same could be said for almost every tablet
> or smartphone: no cooling system, usually slow internal drives... they
> are thought for another kind of usage.
> But if your process is not very disk intensive, it does a decent job.
> Foir instance, now that i have sage installed, it takes a long time to
> startup, but after that, the speed is decent.
Same as my AC100 ; and I suspect it is likewise with the latest ARM chromebook.
Though I think more ram should help, since the poor AC100 has both a slow (and small) storage, and needs to swap to it a lot.
On 2012-11-17, Julien Puydt <julien.pu...@laposte.net> wrote:
> The internal storage is small, but since it's possible to stick a big SD > in, that could fly (I need about 5Go for a system, 7Go for sage [did I > mention it's too much?] and 20Go [mostly] static storage).
> Now I'll only
> (1) make sure it can run ubuntu instead of the crappy chrome OS it ships > with
> (2) wait until it's available in France (my AC100 isn't dead yet, so no > hurry).
it might take a while, as they are apparently being sold out very
quickly...
> I can't help but notice that you didn't comment on the thread's main > topic: the quite honest status of sage on ARM/ubuntu :-P
Since Sept. my nappy-changing duties take away a lot of time, so I didn't touch ARM since. :-)
I have tried your package in a chroot environment (actually in two, a
full ubuntu and a lubuntu), and it doesn't start in neither of them.
Stranegly, the problem seems to be different: in the lubuntu case, it
just shows the message with the version and quits. In the full ubuntu,
it complains with the message "can't import module sage", but for
example, sage -python works fine
> I have tried your package in a chroot environment (actually in two, a
> full ubuntu and a lubuntu), and it doesn't start in neither of them.
> Stranegly, the problem seems to be different: in the lubuntu case, it
> just shows the message with the version and quits. In the full ubuntu,
> it complains with the message "can't import module sage", but for
> example, sage -python works fine
On Friday, December 7, 2012 7:55:55 AM UTC-5, mmarco wrote:
> Nevermind, i found the problem: i had to use an armhf ubuntu.
> On 7 dic, 13:15, mmarco <mma...@unizar.es> wrote: > > I have tried your package in a chroot environment (actually in two, a > > full ubuntu and a lubuntu), and it doesn't start in neither of them.
> > Stranegly, the problem seems to be different: in the lubuntu case, it > > just shows the message with the version and quits. In the full ubuntu, > > it complains with the message "can't import module sage", but for > > example, sage -python works fine
The problem was that the ubuntu image that i was using was armel
architecture, but the sage distribution made by Julien was compiled in
an armhf environment (a slightly different architecture). So there
were not compatible.
The procedure to do so would be the following (on a linux box, maybe
you would need root privileges to mount the image):
1) create an empty file to build the image in. If you just wwant it to
use sage, 3GB should be fine. If you want to install a complete ubuntu
system, you will need more (i used 7GB):
dd -if=/dev/zero of=ubuntu.img -bs=1G count=3
2) format the file
mkfs.ext2 ubuntu.img
3)create a directory and mount the image there
mkdir mount
mount -o loop ubuntu.img mount
5) Unpack the sage install inside the directory
6) Unmount the directory
cd ..
umount mount
And that's it, the file ubuntu.img is ready to be used as a chroot
environment with a very minimal ubuntu system (not even graphical
interface, just the very basic system tools), where sage should work
just fine.
I do have a 7gb image with a lightweight desktop, vnc server, and some
applications installed (although for example qt apps don't render
well, and firefox and chromium don't work either, so i have replaced
them by some alternatives).
I can try to upload it somewhere, if people is interested.
On 7 dic, 23:46, jaebond <jacob.ae.b...@gmail.com> wrote:
> I had been working on this exact same issue a few months ago. Would you
> mind explaining what you did to fix your issue?
> On Friday, December 7, 2012 7:55:55 AM UTC-5, mmarco wrote:
> > Nevermind, i found the problem: i had to use an armhf ubuntu.
> > On 7 dic, 13:15, mmarco <mma...@unizar.es> wrote:
> > > I have tried your package in a chroot environment (actually in two, a
> > > full ubuntu and a lubuntu), and it doesn't start in neither of them.
> > > Stranegly, the problem seems to be different: in the lubuntu case, it
> > > just shows the message with the version and quits. In the full ubuntu,
> > > it complains with the message "can't import module sage", but for
> > > example, sage -python works fine
> I had been working on this exact same issue a few months ago. Would you
> mind explaining what you did to fix your issue?
To explain a bit more: there are several arm flavours, the armel and the armhf. The -el stands for "endian-little" (a pun), the -hf for "hard float". When I started the sage port to arm, I used the armel flavour (which was the only available then). I switched to armhf as soon as possible (as you can guess, using hard floats instead of software floats tends to be faster).
Thank you for that, that will help a lot. I would be interested in the 7gb file. How do you chroot into your images, do you use a script or an app? I have been using an app, but it doesn't seem to like images that weren't made by the app.
On Saturday, December 8, 2012 9:22:20 AM UTC-5, mmarco wrote:
> The problem was that the ubuntu image that i was using was armel > architecture, but the sage distribution made by Julien was compiled in > an armhf environment (a slightly different architecture). So there > were not compatible.
> The procedure to do so would be the following (on a linux box, maybe > you would need root privileges to mount the image):
> 1) create an empty file to build the image in. If you just wwant it to > use sage, 3GB should be fine. If you want to install a complete ubuntu > system, you will need more (i used 7GB): > dd -if=/dev/zero of=ubuntu.img -bs=1G count=3
> 2) format the file > mkfs.ext2 ubuntu.img
> 3)create a directory and mount the image there > mkdir mount > mount -o loop ubuntu.img mount
> 5) Unpack the sage install inside the directory > 6) Unmount the directory > cd .. > umount mount
> And that's it, the file ubuntu.img is ready to be used as a chroot > environment with a very minimal ubuntu system (not even graphical > interface, just the very basic system tools), where sage should work > just fine.
> I do have a 7gb image with a lightweight desktop, vnc server, and some > applications installed (although for example qt apps don't render > well, and firefox and chromium don't work either, so i have replaced > them by some alternatives).
> I can try to upload it somewhere, if people is interested.
> > I had been working on this exact same issue a few months ago. Would you > > mind explaining what you did to fix your issue?
> > On Friday, December 7, 2012 7:55:55 AM UTC-5, mmarco wrote:
> > > Nevermind, i found the problem: i had to use an armhf ubuntu.
> > > On 7 dic, 13:15, mmarco <mma...@unizar.es> wrote: > > > > I have tried your package in a chroot environment (actually in two, > a > > > > full ubuntu and a lubuntu), and it doesn't start in neither of them.
> > > > Stranegly, the problem seems to be different: in the lubuntu case, > it > > > > just shows the message with the version and quits. In the full > ubuntu, > > > > it complains with the message "can't import module sage", but for > > > > example, sage -python works fine
> Thank you for that, that will help a lot. I would be interested in the 7gb
> file. How do you chroot into your images, do you use a script or an app?
> I have been using an app, but it doesn't seem to like images that weren't
> made by the app.
> On Saturday, December 8, 2012 9:22:20 AM UTC-5, mmarco wrote:
> > The problem was that the ubuntu image that i was using was armel
> > architecture, but the sage distribution made by Julien was compiled in
> > an armhf environment (a slightly different architecture). So there
> > were not compatible.
> > The procedure to do so would be the following (on a linux box, maybe
> > you would need root privileges to mount the image):
> > 1) create an empty file to build the image in. If you just wwant it to
> > use sage, 3GB should be fine. If you want to install a complete ubuntu
> > system, you will need more (i used 7GB):
> > dd -if=/dev/zero of=ubuntu.img -bs=1G count=3
> > 2) format the file
> > mkfs.ext2 ubuntu.img
> > 3)create a directory and mount the image there
> > mkdir mount
> > mount -o loop ubuntu.img mount
> > 5) Unpack the sage install inside the directory
> > 6) Unmount the directory
> > cd ..
> > umount mount
> > And that's it, the file ubuntu.img is ready to be used as a chroot
> > environment with a very minimal ubuntu system (not even graphical
> > interface, just the very basic system tools), where sage should work
> > just fine.
> > I do have a 7gb image with a lightweight desktop, vnc server, and some
> > applications installed (although for example qt apps don't render
> > well, and firefox and chromium don't work either, so i have replaced
> > them by some alternatives).
> > I can try to upload it somewhere, if people is interested.
> > > I had been working on this exact same issue a few months ago. Would you
> > > mind explaining what you did to fix your issue?
> > > On Friday, December 7, 2012 7:55:55 AM UTC-5, mmarco wrote:
> > > > Nevermind, i found the problem: i had to use an armhf ubuntu.
> > > > On 7 dic, 13:15, mmarco <mma...@unizar.es> wrote:
> > > > > I have tried your package in a chroot environment (actually in two,
> > a
> > > > > full ubuntu and a lubuntu), and it doesn't start in neither of them.
> > > > > Stranegly, the problem seems to be different: in the lubuntu case,
> > it
> > > > > just shows the message with the version and quits. In the full
> > ubuntu,
> > > > > it complains with the message "can't import module sage", but for
> > > > > example, sage -python works fine
> On 8 dic, 23:01, jaebond <jacob.ae.b...@gmail.com> wrote:
> > Thank you for that, that will help a lot. I would be interested in the 7gb
> > file. How do you chroot into your images, do you use a script or an app?
> > I have been using an app, but it doesn't seem to like images that weren't
> > made by the app.
> > On Saturday, December 8, 2012 9:22:20 AM UTC-5, mmarco wrote:
> > > The problem was that the ubuntu image that i was using was armel
> > > architecture, but the sage distribution made by Julien was compiled in
> > > an armhf environment (a slightly different architecture). So there
> > > were not compatible.
> > > The procedure to do so would be the following (on a linux box, maybe
> > > you would need root privileges to mount the image):
> > > 1) create an empty file to build the image in. If you just wwant it to
> > > use sage, 3GB should be fine. If you want to install a complete ubuntu
> > > system, you will need more (i used 7GB):
> > > dd -if=/dev/zero of=ubuntu.img -bs=1G count=3
> > > 2) format the file
> > > mkfs.ext2 ubuntu.img
> > > 3)create a directory and mount the image there
> > > mkdir mount
> > > mount -o loop ubuntu.img mount
> > > 5) Unpack the sage install inside the directory
> > > 6) Unmount the directory
> > > cd ..
> > > umount mount
> > > And that's it, the file ubuntu.img is ready to be used as a chroot
> > > environment with a very minimal ubuntu system (not even graphical
> > > interface, just the very basic system tools), where sage should work
> > > just fine.
> > > I do have a 7gb image with a lightweight desktop, vnc server, and some
> > > applications installed (although for example qt apps don't render
> > > well, and firefox and chromium don't work either, so i have replaced
> > > them by some alternatives).
> > > I can try to upload it somewhere, if people is interested.
> > > > I had been working on this exact same issue a few months ago. Would you
> > > > mind explaining what you did to fix your issue?
> > > > On Friday, December 7, 2012 7:55:55 AM UTC-5, mmarco wrote:
> > > > > Nevermind, i found the problem: i had to use an armhf ubuntu.
> > > > > On 7 dic, 13:15, mmarco <mma...@unizar.es> wrote:
> > > > > > I have tried your package in a chroot environment (actually in two,
> > > a
> > > > > > full ubuntu and a lubuntu), and it doesn't start in neither of them.
> > > > > > Stranegly, the problem seems to be different: in the lubuntu case,
> > > it
> > > > > > just shows the message with the version and quits. In the full
> > > ubuntu,
> > > > > > it complains with the message "can't import module sage", but for
> > > > > > example, sage -python works fine
I'm experimenting with building Sage on the Raspberry Pi. It apparently has an ARM6 processor, so I'm running from scratch. I ran into problems building libm4rie as well (and also on building conversion.c); it would start running and then after about 20 minutes the device would freeze up and my ssh session (since I'm running headless!) would seize up. Nothing I can find in the log files; seems like just a straight out crash. I'm trying again from the beginning in case something went wrong earlier in the build process.
ATLAS took 807 minutes to compile on the first attempt. I seem to recall hearing that ATLAS has some kind of processor database at some point? I poked around looking for whether there's a good way to store the timings, etc, and chop down the ATLAS compile time but wasn't immediately able to turn any answers up. Anyone have a good idea of where to look?
On Thursday, December 13, 2012 2:35:52 PM UTC+3, mmarco wrote:
> jaebond, did you try the image i linked? did it work for you?
> On 9 dic, 10:56, mmarco <mma...@unizar.es> wrote: > > I have made a zip archive with both the image and the scripts that i > > use. you can download it from:
> > On 8 dic, 23:01, jaebond <jacob.ae.b...@gmail.com> wrote:
> > > Thank you for that, that will help a lot. I would be interested in > the 7gb > > > file. How do you chroot into your images, do you use a script or an > app? > > > I have been using an app, but it doesn't seem to like images that > weren't > > > made by the app.
> > > On Saturday, December 8, 2012 9:22:20 AM UTC-5, mmarco wrote:
> > > > The problem was that the ubuntu image that i was using was armel > > > > architecture, but the sage distribution made by Julien was compiled > in > > > > an armhf environment (a slightly different architecture). So there > > > > were not compatible.
> > > > The procedure to do so would be the following (on a linux box, maybe > > > > you would need root privileges to mount the image):
> > > > 1) create an empty file to build the image in. If you just wwant it > to > > > > use sage, 3GB should be fine. If you want to install a complete > ubuntu > > > > system, you will need more (i used 7GB): > > > > dd -if=/dev/zero of=ubuntu.img -bs=1G count=3
> > > > 2) format the file > > > > mkfs.ext2 ubuntu.img
> > > > 3)create a directory and mount the image there > > > > mkdir mount > > > > mount -o loop ubuntu.img mount
> > > > 4) put the ubuntu core tarball in the directory and unpack it > > > > cd mount > > > > wget
> > > > 5) Unpack the sage install inside the directory > > > > 6) Unmount the directory > > > > cd .. > > > > umount mount
> > > > And that's it, the file ubuntu.img is ready to be used as a chroot > > > > environment with a very minimal ubuntu system (not even graphical > > > > interface, just the very basic system tools), where sage should work > > > > just fine.
> > > > I do have a 7gb image with a lightweight desktop, vnc server, and > some > > > > applications installed (although for example qt apps don't render > > > > well, and firefox and chromium don't work either, so i have replaced > > > > them by some alternatives).
> > > > I can try to upload it somewhere, if people is interested.
> > > > > I had been working on this exact same issue a few months ago. > Would you > > > > > mind explaining what you did to fix your issue?
> > > > > On Friday, December 7, 2012 7:55:55 AM UTC-5, mmarco wrote:
> > > > > > Nevermind, i found the problem: i had to use an armhf ubuntu.
> > > > > > On 7 dic, 13:15, mmarco <mma...@unizar.es> wrote: > > > > > > > I have tried your package in a chroot environment (actually in > two, > > > > a > > > > > > > full ubuntu and a lubuntu), and it doesn't start in neither of > them.
> > > > > > > Stranegly, the problem seems to be different: in the lubuntu > case, > > > > it > > > > > > > just shows the message with the version and quits. In the full > > > > ubuntu, > > > > > > > it complains with the message "can't import module sage", but > for > > > > > > > example, sage -python works fine
> I'm experimenting with building Sage on the Raspberry Pi. It apparently
> has an ARM6 processor, so I'm running from scratch. I ran into problems
> building libm4rie as well (and also on building conversion.c); it would
> start running and then after about 20 minutes the device would freeze up
> and my ssh session (since I'm running headless!) would seize up. Nothing
> I can find in the log files; seems like just a straight out crash. I'm
> trying again from the beginning in case something went wrong earlier in
> the build process.
Yes, that one file is a problem.
> ATLAS took 807 minutes to compile on the first attempt. I seem to recall
> hearing that ATLAS has some kind of processor database at some point? I
> poked around looking for whether there's a good way to store the
> timings, etc, and chop down the ATLAS compile time but wasn't
> immediately able to turn any answers up. Anyone have a good idea of
> where to look?
apt-get install libatlas-dev (or something like this),
then export SAGE_ATLAS_LIB=/usr
that way atlas won't get compiled in sage.
Things got pretty crazy and I haven't had a chance to take a look yet, but I should be able to give it a try in the next day or two. Thank you again for your help.
On Thursday, December 13, 2012 6:35:52 AM UTC-5, mmarco wrote:
> jaebond, did you try the image i linked? did it work for you?
> On 9 dic, 10:56, mmarco <mma...@unizar.es> wrote: > > I have made a zip archive with both the image and the scripts that i > > use. you can download it from:
> > On 8 dic, 23:01, jaebond <jacob.ae.b...@gmail.com> wrote:
> > > Thank you for that, that will help a lot. I would be interested in > the 7gb > > > file. How do you chroot into your images, do you use a script or an > app? > > > I have been using an app, but it doesn't seem to like images that > weren't > > > made by the app.
> > > On Saturday, December 8, 2012 9:22:20 AM UTC-5, mmarco wrote:
> > > > The problem was that the ubuntu image that i was using was armel > > > > architecture, but the sage distribution made by Julien was compiled > in > > > > an armhf environment (a slightly different architecture). So there > > > > were not compatible.
> > > > The procedure to do so would be the following (on a linux box, maybe > > > > you would need root privileges to mount the image):
> > > > 1) create an empty file to build the image in. If you just wwant it > to > > > > use sage, 3GB should be fine. If you want to install a complete > ubuntu > > > > system, you will need more (i used 7GB): > > > > dd -if=/dev/zero of=ubuntu.img -bs=1G count=3
> > > > 2) format the file > > > > mkfs.ext2 ubuntu.img
> > > > 3)create a directory and mount the image there > > > > mkdir mount > > > > mount -o loop ubuntu.img mount
> > > > 4) put the ubuntu core tarball in the directory and unpack it > > > > cd mount > > > > wget
> > > > 5) Unpack the sage install inside the directory > > > > 6) Unmount the directory > > > > cd .. > > > > umount mount
> > > > And that's it, the file ubuntu.img is ready to be used as a chroot > > > > environment with a very minimal ubuntu system (not even graphical > > > > interface, just the very basic system tools), where sage should work > > > > just fine.
> > > > I do have a 7gb image with a lightweight desktop, vnc server, and > some > > > > applications installed (although for example qt apps don't render > > > > well, and firefox and chromium don't work either, so i have replaced > > > > them by some alternatives).
> > > > I can try to upload it somewhere, if people is interested.
> > > > > I had been working on this exact same issue a few months ago. > Would you > > > > > mind explaining what you did to fix your issue?
> > > > > On Friday, December 7, 2012 7:55:55 AM UTC-5, mmarco wrote:
> > > > > > Nevermind, i found the problem: i had to use an armhf ubuntu.
> > > > > > On 7 dic, 13:15, mmarco <mma...@unizar.es> wrote: > > > > > > > I have tried your package in a chroot environment (actually in > two, > > > > a > > > > > > > full ubuntu and a lubuntu), and it doesn't start in neither of > them.
> > > > > > > Stranegly, the problem seems to be different: in the lubuntu > case, > > > > it > > > > > > > just shows the message with the version and quits. In the full > > > > ubuntu, > > > > > > > it complains with the message "can't import module sage", but > for > > > > > > > example, sage -python works fine
I have seen that there is an android app that runs an ubuntu desktop
without the need of root access. From the web page, i see that it uses
something called fakechroot. I would like to investigate that
possibility. Maybe it could be the open door to some nice android app
that would install sage to be run in the terminal emulator.
Somebody knows anything about this fakechroot thing?
And on a different subject: what happened with the ARM machine that
William bought to serve as a buildbot?
fakechroot is a LD_PRELOAD hack that overrides glibc calls and e.g. redirects file open() calls. Though its not perfect, for example no pseudo-ttys (I think this already rules out Sage).
On Friday, December 21, 2012 6:19:48 PM UTC, mmarco wrote:
> I have seen that there is an android app that runs an ubuntu desktop > without the need of root access. From the web page, i see that it uses > something called fakechroot.
