Re: What level Sugar Activities on F11 ?
2009/8/17 Mikus Grinbergs mi...@bga.com: Is XO-1.5 software expected to run Activities marked for 0.86 ? If we are shipping Sugar 0.84, the answer is no (due to API incompatibility). The current build tools pulls in the latest stable activities from ASLO somewhat blindly (as per my understanding) I am interpreting this answer to say: ASLO needs to declare a Sugar version to be stable, in time for it to be picked up by the XO-1.5 build tools. Whatever stable Sugar version gets picked by XO-1.5, the Activities to be used with XO-1.5 need to be compatible with the picked Sugar version. The current stable Sugar version being picked up by the XO-1.5 tools is 0.84. So it comes down to the ASLO release date (published 0.86 target is September), vs. the XO-1.5 release (to production) date (published target is later in 2009). Test time against 0.84 is accumulating -- but test time against 0.86 appears doubtful. Unless something to the contrary gets announced, I'll continue by __IGNORING__ Activity versions not marked for 0.82 - 0.84. This is basically correct, with the exception that stability is not declared on ASLO. ASLO is naive about stable vs unstable platforms. Instead, when a Sugar Client pings ASLO for update information, it sends a string identifing which version of Sugar is running on the client. ASLO then responds by sending a link to the most appropriate update for a the given version of Sugar which the client is running. david mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
touchpad redux
the XO-1 touchpad has recently come under scrutiny once again. most long-time readers of this list (and most users of the XO-1) are aware that the touchpad doesn't always behave as a proper touchpad should. as a result of more reports from the field, and with better data than we've had before [1], we've been taking a fresh look at what goes wrong when the touchpad acts up, and have taken a fresh stab at trying to work around some of the problems. (for various reasons a different touchpad was slipped into production earlier this year, and initial field reports are much more favorable. but that still leaves something on the order of a million laptops out there, built with the older device. and to answer the first question everyone asks: no, it's not a drop-in replacement. most of the lower half of the laptop needs to be replaced to accomodate the newer touchpad.) so, i've put together a wiki page detailing what we think goes wrong, and what we've done so far to try and reduce the impact of those failures. most of what i've done is really just refinements on what was already there (standing on the shoulders of giants, and all that), but we're hoping that those small changes may help a lot: http://wiki.laptop.org/go/Touchpad_driver_changes the new driver has been commited to the olpc-2.6.30 branch, so the next build(s) of F11-on-XO1, or SoaS-on-XO1, should pick up the new driver. if you've had trouble with the touchpad in the past, and can try one of those releases when it's available, please let me know what you think now. (if you've resorted to using a mouse, you might go back to the touchpad for a while before upgrading to the new driver, just to remind yourself how poorly, or well, it behaved.) one unconfirmed theory we've heard from folks in the field is that the touchpad behavior gets worse over the course of several hours of continuous use. if anyone can comment on that, or would like to design (and execute :-) an appropriate test, please shout! i'm now in the process of backporting the changes to the testing branch which was the basis for the kernel released for 802. we don't have plan yet for creating a new release -- i'm sure the first step will be a kernel rpm, or other installable package of some sort. paul [1] getting better data from the field was made much easier with the help of a script put together by James Cameron. See the final section (Large Jump Logging Technique) of http://wiki.laptop.org/go/Three_known_touchpad_issues =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: touchpad redux
i forgot to add my second footnote! i wrote: as a result of more reports from the field, and with better data than we've had before [1], we've been taking a fresh look at what ... [1] getting better data from the field was made much easier with the help of a script put together by James Cameron. See the final section (Large Jump Logging Technique) of http://wiki.laptop.org/go/Three_known_touchpad_issues the data was gathered by students and teachers and the team in rwanda many thanks!! paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] idmgr broken in latest 0.6
Hi Martin,
Latest idmgr in the XS is broken. No laptops can register because the
database is still in the v2 format.
/home/idmgr/create_registration only creates a v2 database, and marks
the fs accordingly:
echo 2 /home/idmgr/storage_format_version
The spec file would then ordinarily cause the upgrade_2_to_3 to be
run, but it doesn't because commit 5ef89de945 makes the spec file
update that file to '3'
I think you should remove the line of code that updates
/home/idmgr/storage_format_version from the spec file (since
create_registration does that), and update create_registration to make
a v3 db.
Also, xs-restore needs the attached patch. Can you throw that in at
the same time?
Thanks,
Daniel
--- create_user.orig 2009-07-29 15:55:26.0 +0545
+++ create_user 2009-07-29 15:54:19.0 +0545
@@ -37,16 +37,26 @@
exit 1
}
+PASSWD_ONLY=0
+# this option allows the homedir setup (including dealings with ssh key)
+# to be skipped. useful when restoring from backups.
+if [ '$1' == '--passwd-only' ]; then
+ PASSWD_ONLY=1
+fi
+
read username
read full_name
-read uuid #unused!
-read pubkey
+if [ '$PASSWD_ONLY' == '0' ]; then
+ read uuid #unused!
+ read pubkey
+fi
# check for sane values
export LC_ALL=C
echo $username | grep -s -E '^[A-Z]{3}[A-F0-9]{8}$' /dev/null || die bad username
-echo $pubkey | grep -s -E '^[A-Za-z0-9+/=]+$' /dev/null || die bad public key
-
+if [ '$PASSWD_ONLY' == '0' ]; then
+ echo $pubkey | grep -s -E '^[A-Za-z0-9+/=]+$' /dev/null || die bad public key
+fi
homedir=/library/users/$username
XO_USERS_GROUP=xousers
@@ -68,6 +78,8 @@
NEW_USER=1
fi
+[ '$PASSWD_ONLY' == '1' ] exit 0
+
#from here, if a new user was created, a failure will leave the user
#there but unconfigured. So rather than simply dying, we try to clean
#up first.
@@ -90,4 +102,4 @@
chmod 600 .ssh/authorized_keys || clean_up_and_die Unable to chmod authorized_keys
chown -R $username .ssh || clean_up_and_die Unable to chown .ssh
-#clean_up_and_die goodbye
\ No hay ningún carácter de nueva línea al final del fichero
+#clean_up_and_die goodbye
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] idmgr broken in latest 0.6
2009/8/18 Daniel Drake d...@laptop.org: The spec file would then ordinarily cause the upgrade_2_to_3 to be run, but it doesn't because commit 5ef89de945 makes the spec file update that file to '3' Also upgrade_users_2_to_3 doesn't work if idmgr was running. The wasrunning check is broken - /var/lock/subsys/idmgr is never created. Daniel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Help Nicaragua
2009/8/18 Kevin Mauricio Benavides Castro webmaster.ac@gmail.com: Hola a todos los de la lista de correo soy kevin programador proyecto fedora 11 la cual tengo problemas a la hora del NANBLASTER la cual me pide una llave de activavion las cuales ya las tenemos pero no se realiza el nanblaster en las otras maquina necesitamos ayuda. todos los pasos que aparecen en la wiki. Hola Kevin! Un par de preguntas, al azar, de problemas frequentes: - Tienen todas las maquinas el firmware q2e41? - Si usas una imagen firmada de OLPC como fuente, el NANDBlaster funciona? O no hace diferencia? Si estas ideas no ayudan a resolver el problema, nos vas a tener que contar exactamente los pasos que siguen (en la maquina fuente, y en las maquinas receptoras, y _exactamente_ el error que ven. abrazos, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] idmgr broken in latest 0.6
On Tue, Aug 18, 2009 at 9:02 AM, Daniel Draked...@laptop.org wrote: Latest idmgr in the XS is broken. No laptops can register because the database is still in the v2 format. you are right. My fix to the installation issue idmgr had is buggy. Working on it - Also, xs-restore needs the attached patch. Can you throw that in at the same time? shall do, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
