2009/9/6 Timo Jyrinki timo.jyri...@gmail.com:
http://wiki.debian.org/DebianOnFreeRunner#CurrentStatusofInstallation
For those of you (like me) who don't read help texts, I added the
pretty useful information about needing to install perl on the host
system before running the install script :)
Hi,
Am Sonntag, den 13.09.2009, 21:42 -0400 schrieb Stefan Monnier:
Or more precisely, for $DISPLAY on fso-controlled device at runtime,
not installation time. I think that mess will be larger than that of having
two icons, menu items or whatever the launcher makes of it, for the user to
On Sun, Sep 13, 2009 at 10:52:53PM +0400, Nikita V. Youshchenko wrote:
That will result in two icons in launchers.
why nor let the user decide on installation or check in postinst for
arm and copy the matching one?
Not for arm but for fso-controlled device.
Or more
On Mon, Sep 14, 2009 at 10:24:04AM +0400, Nikita V. Youshchenko wrote:
On Sun, Sep 13, 2009 at 10:52:53PM +0400, Nikita V. Youshchenko wrote:
That will result in two icons in launchers.
why nor let the user decide on installation or check in postinst for
arm and copy the
AFAIK, there is such a protocol already (which is hopefully used by all
tools like VLC, Xine, mplayer, totem, at least when in fullscreen
mode). So mokomaze should use it. And the FSO side should also
support it.
x screensaver extension. you can request x to suspend blanking until
u
Not for arm but for fso-controlled device.
Or more precisely, for $DISPLAY on fso-controlled device at
runtime, not installation time.
Cant think out a use case when same device will run a window manager
(or whatever component that uses .desktop files) sometimes with fso
On Monday 14 September 2009, Nikita V. Youshchenko wrote:
Not for arm but for fso-controlled device.
Or more precisely, for $DISPLAY on fso-controlled device at
runtime, not installation time.
Cant think out a use case when same device will run a window manager
(or
On Monday 14 September 2009 04:07:43 Carsten Haitzler wrote:
On Sun, 13 Sep 2009 21:42:49 -0400 Stefan Monnier
monn...@iro.umontreal.ca
said:
Or more precisely, for $DISPLAY on fso-controlled device at
runtime, not installation time. I think that mess will be larger than
that of
On Mon, 14 Sep 2009 09:38:49 -0400 Stefan Monnier monn...@iro.umontreal.ca
said:
AFAIK, there is such a protocol already (which is hopefully used by all
tools like VLC, Xine, mplayer, totem, at least when in fullscreen
mode). So mokomaze should use it. And the FSO side should also
On Tue, 15 Sep 2009 00:11:54 +0200 Michael 'Mickey' Lauer
mic...@vanille-media.de said:
On Monday 14 September 2009 04:07:43 Carsten Haitzler wrote:
On Sun, 13 Sep 2009 21:42:49 -0400 Stefan Monnier
monn...@iro.umontreal.ca
said:
Or more precisely, for $DISPLAY on fso-controlled
On Sun, Sep 06, 2009 at 11:23:58PM +0400, Nikita V. Youshchenko wrote:
For example, it's nice that mokomaze is in debian, but if you install it
and run it, you will get your screen blanked after a minute. To avoid
that, one needs to start mokomaze under fsoraw wrapper. Making this happen
On Sun, Sep 06, 2009 at 11:23:58PM +0400, Nikita V. Youshchenko wrote:
For example, it's nice that mokomaze is in debian, but if you install
it and run it, you will get your screen blanked after a minute. To
avoid that, one needs to start mokomaze under fsoraw wrapper. Making
this happen
On Sun, Sep 13, 2009 at 08:09:33PM +0400, Nikita V. Youshchenko wrote:
On Sun, Sep 06, 2009 at 11:23:58PM +0400, Nikita V. Youshchenko wrote:
For example, it's nice that mokomaze is in debian, but if you install
it and run it, you will get your screen blanked after a minute. To
avoid
For example, it's nice that mokomaze is in debian, but if you
install it and run it, you will get your screen blanked after a
minute. To avoid that, one needs to start mokomaze under fsoraw
wrapper. Making this happen automatically while staying within
debian policy could be a
That will result in two icons in launchers.
why nor let the user decide on installation or check in postinst for arm
and copy the matching one?
___
Openmoko community mailing list
community@lists.openmoko.org
That will result in two icons in launchers.
why nor let the user decide on installation or check in postinst for arm
and copy the matching one?
Not for arm but for fso-controlled device.
And depending on a result of such a check, different .desktop files should
be installed under
On Sun, Sep 13, 2009 at 10:52:53PM +0400, Nikita V. Youshchenko wrote:
That will result in two icons in launchers.
why nor let the user decide on installation or check in postinst for arm
and copy the matching one?
Not for arm but for fso-controlled device.
Or more precisely, for
Or more precisely, for $DISPLAY on fso-controlled device at runtime,
not installation time. I think that mess will be larger than that of having
two icons, menu items or whatever the launcher makes of it, for the user to
choose between.
The solution is to use a scheme where the blanking
On Sun, 13 Sep 2009 21:42:49 -0400 Stefan Monnier monn...@iro.umontreal.ca
said:
Or more precisely, for $DISPLAY on fso-controlled device at runtime,
not installation time. I think that mess will be larger than that of having
two icons, menu items or whatever the launcher makes of it,
2009/9/6 Nikita V. Youshchenko yo...@debian.org:
Doing debian install with (c)debootstrap, as current install.sh does and as
debian installer does, although being a standard way, is somewhat
questionable on slow devices such as freerunner. This is plainly slow,
compared to reflashing or
2009/8/29 Timo Jyrinki timo.jyri...@gmail.com:
Unfortunately it was found out installing Debian via the install.sh
script is broken until dpkg 1.15.4 lands in unstable.
1.15.4 ARM build has now landed in the Debian archive (at least
ftp.debian.org, mirrors soon follow, check
I'm quite glad with the new E17 and Zhone packages in the main Debian
archive. The only package you really need from the (still enabled by
default) pkg-fso archive is the kernel, so this is very good progress.
The kernel is of course a hard thing and involves work from all
Openmoko kernel
2009/8/29 Nikita V. Youshchenko yo...@debian.org:
GPRS worked fine.
Could you please post an explanation on how to test/use gprs on debian?
Maybe see http://wiki.openmoko.org/wiki/GPRS_FSO#Using_scripts ? I
added now a link to that page also from DebianOnFreeRunner.
I'm myself actually using
2009/8/28 Radek Polak pson...@seznam.cz:
Risto H. Kurppa wrote:
Tried to install debian today:
...
E: Internal error: install
Unfortunately it was found out installing Debian via the install.sh
script is broken until dpkg 1.15.4 lands in unstable. So, keep eye on
GPRS worked fine.
Could you please post an explanation on how to test/use gprs on debian?
signature.asc
Description: This is a digitally signed message part.
___
Openmoko community mailing list
community@lists.openmoko.org
2009/8/27 Lee Grime lee.gr...@gmail.com:
Re-camping. I can only tell it is doing this because I left it near my PC
and the speakers were picking it up! Happens about every 5-10mins.
I did not have this problem with SHR, it is stable for GSM. SMS has a few
quirks, but nothing major. I know
O Xoves, 27 de Agosto de 2009, Lee Grime escribiu:
Re-camping. I can only tell it is doing this because I left it near my PC
and the speakers were picking it up! Happens about every 5-10mins.
I did not have this problem with SHR, it is stable for GSM. SMS has a few
quirks, but nothing
Tried to install debian today:
INST_MIRROR=http://ftp.fi.debian.org/debian HOST=ribian TASKS=ALL
SINGLE_PART=true QI=true ./install.sh all
problem #1: fdisk fails.
(copied from irc..)
10:08 rhkfin Syncing disks.
10:08 rhkfin Partitioning failed, could not execute with fdisk:
10:08 rhkfin n
Risto H. Kurppa wrote:
Tried to install debian today:
...
E: Internal error: install
I really dont like these long install scripts. When it works it's good
but if not, it's really hard to find where is problem.
I think Debian should be offered as ready-for-flash image. I am creating
debian
On Fri, Aug 28, 2009 at 12:19 PM, Radek Polakpson...@seznam.cz wrote:
I really dont like these long install scripts. When it works it's good
but if not, it's really hard to find where is problem.
But isn't that the thing with everything?
I think Debian should be offered as ready-for-flash
Nice, well done! I like that the moko page of Debian is a graphical
showcase (add your OpenOffice screenshot there!) and the install
instructions are separated (to debian wiki).
I don't really remember calling for wiki cleaning, maybe mentioned the
messy wiki somewhere but yes, the wiki needs a
On Thu, Aug 27, 2009 at 3:20 PM, Timo Jyrinkitimo.jyri...@gmail.com wrote:
Hi,
With the gust of fresh air everywhere, I took the liberty of joining
the mess that was combined http://wiki.openmoko.org/wiki/Debian +
http://wiki.debian.org/DebianOnFreeRunner , so that in the end the
Openmoko
2009/8/27 Risto H. Kurppa ri...@kurppa.fi:
showcase (add your OpenOffice screenshot there!)
Done :)
2009/8/27 Edder ed...@tkwsping.nl:
I had been looking at installing debian a couple of days ago and it
seems that this is a definite improvement! The only suggestion I have
is to add some more
I installed debian a couple of days ago.
1st try with a new 8GB sandisk uSDHC card, which failed with IO errors. I
assume this is because of the SD card speed.
Tried with a sandisk 4GB uSDHC, using install.sh, with VFAT boot partition.
Install worked fine.
Some problems encountered :-
34 matches
Mail list logo
