to specify
and MPPT controller, but I'm not sure they can afford it. PWM (pulse width
modulation) is better than no controller.
Thanks for inviting me, Adam. Don't hesitate to send questions on renewable
energy projects -- not sure if I can help, but I'd give it a try.
Regards,
Kim Quirk
On Sun
I've been thinking about this problem for the last year -- when it first
became obvious (to me) that:
1 - we were definitely NOT going to be able to lock down APIs for at least a
year or two
2 - we have no control over the activity developers and the maintainability
of any given activity (unless
date and time stamps, etc.?
Kim
On Mon, Jul 14, 2008 at 10:35 AM, Tomeu Vizoso [EMAIL PROTECTED]
wrote:
On Mon, Jul 14, 2008 at 4:24 PM, Eben Eliason [EMAIL PROTECTED]
wrote:
2008/7/14 Kim Quirk [EMAIL PROTECTED]:
3 - Encourage schools to completely reflash (cleaninstall) their laptops
For a 'change log' that is useful for both development and testing groups, I
would like to ask that people please use the comments during check-in to add
the trac item being fixed (when available) and a short description that
would help others to know what to test or what feature has been added.
We've had a couple of discussions about Release Notes and Feature lists.
Here is my proposal:
Feature lists -- I created a 'XO_Base_Features' page (which should keep the
running list of features the XO supports as of the latest stable release). I
added the as of release 8.1.1 to the top of this
With almost 400,000 deployed in the world, we need to have some good
discussions on the backward compatibilty and upgradability of Activities.
Some of the bugs Charlie is writing up from the QA first look at joyride may
be answered by upgrading an activity to a newer one.
So here are the
I think you should just start a page...
Thanks,
Kim
On Tue, Jul 8, 2008 at 11:06 AM, Greg Smith [EMAIL PROTECTED] wrote:
Hi All,
Who is writing the release notes for 8.2.0?
I am seeing a lot of good info on improvements pass by in e-mail or in
Trac exchanges (e.g.
This is a good point and I hope Michael will be able to address it. If
there are any questions about how to get translations into pootle or
into a build, please post them so we can get them resolved quickly.
In order to help focus which translations are high priority for this
release, I have
For testing, Scott, we are growing a set of each new keyboard/language
laptop that comes out of manufacturing.
The 'ultimate' test for fonts, translations, keyboard integration is to load
a build on these laptops. I have two of each new SKU and I have tried to
label one as 'WP' (write protected
My thoughts in-line...
Kim
On Tue, Jul 1, 2008 at 6:16 PM, C. Scott Ananian [EMAIL PROTECTED] wrote:
On Tue, Jul 1, 2008 at 5:13 PM, Greg Smith [EMAIL PROTECTED]
wrote:
- Kim will check with Peru and Greg will check with Uruguay teams to
ensure that they do not plan to upgrade to 8.2.0.
On Tue, Jul 1, 2008 at 5:39 PM, Greg Smith [EMAIL PROTECTED] wrote:
Hi All,
Thanks for all the comments on the Development Process.
http://wiki.laptop.org/go/Release_Process_Home
A few gentle suggestions on managing the input.
A - My intention is that this page
Scott,
I think we all agree that communications can improve and constructive ideas
on how to do that are always welcome.
I'm not sure how you decided that we had consensus on following Mozilla's
design principles. I don't remember being part of that discussion. I'm not
sure how we define
We separated out the activities so that we could push the testing and
localization of activities out to the country. How many activities can they
test? As many as they have people and time for.
It is in the deployment guide (and starting to get good discussion from
sales/deployment people) that
Thanks Noah!
Kim
On Fri, Jun 27, 2008 at 3:41 PM, Noah Kantrowitz [EMAIL PROTECTED]
wrote:
I have enabled ticket cloning support on dev.laptop.org. Just use the
new Clone button on the ticket form. Enjoy.
--Noah
___
Devel mailing list
John,
Beyond SN and U#, I have found that I need these tags for correct
keyboard/localization:
KV
LO
KL
KA only affects the keyboard in OFW (and default if missing is good)
P# was important in older hardware.
And if you change any of these tags, you need to re-image the software to
actually use
Saxena [EMAIL PROTECTED] wrote:
On Jun 25 2008, at 00:04, Kim Quirk was caught saying:
Thanks Deepak.
I'd love to see the SD card corruption fixed, but we are just about
finished
with testing and are now in the release process for 8.1.1... so i
recommend
that we schedule this fix
Thanks Deepak.
I'd love to see the SD card corruption fixed, but we are just about finished
with testing and are now in the release process for 8.1.1... so i recommend
that we schedule this fix for the 8.1.2 release (if we do this release) and
make sure it gets into 8.2.0, which might be the next
support to one release back -- which has an impact on how many major
releases we should do each year.
Kim
On Sat, Jun 21, 2008 at 7:37 PM, Deepak Saxena [EMAIL PROTECTED] wrote:
On Jun 21 2008, at 20:10, Kim Quirk was caught saying:
Sounds great! We've discussed a similar thing here, but I
New milestone created.
Kim
On Sun, Jun 22, 2008 at 2:27 PM, Michael Stone [EMAIL PROTECTED] wrote:
On Sun, Jun 22, 2008 at 03:38:25AM +0200, Marco Pesenti Gritti wrote:
On Sun, Jun 22, 2008 at 3:34 AM, Eben Eliason [EMAIL PROTECTED] wrote:
Make sense. Wonder why Michael has been using the rel-
22, 2008 at 3:51 PM, Kim Quirk [EMAIL PROTECTED] wrote:
New milestone created.
Kim
On Sun, Jun 22, 2008 at 2:27 PM, Michael Stone [EMAIL PROTECTED] wrote:
On Sun, Jun 22, 2008 at 03:38:25AM +0200, Marco Pesenti Gritti wrote:
On Sun, Jun 22, 2008 at 3:34 AM, Eben Eliason [EMAIL PROTECTED] wrote
Sounds great! We've discussed a similar thing here, but I don't
believe there has been any time for that.
For g1g1 people there could possibly be 2 options - 1. Upgrade from
656 to 8.1.1, with the automatic second step of adding activities; or
2. Cleanstall to the 8.1.1 build that already
Michael,
If we can all agree on tagging and on using exactly the same tags
(which is very difficult); then we still have to deal with the
milestone issue as the entire roadmap and all the past expectations
have been that the milestone DO mean something.
It is difficult to give up on milestones
Greg,
I am adding the 'testing' mailing list. We can use this 'real life'
information for generating Use Cases and test cases but we will
probably need to simplify it. There are too many things going on in
this particular case. We have some use cases for school scenarios in
some of these links:
Looks good to me. Thanks for writing it up.
Kim
On Thu, Jun 12, 2008 at 1:12 PM, Chris Ball [EMAIL PROTECTED] wrote:
Hi,
At the IRC software meeting yesterday we discussed creating some new
build streams in preparation for our August 8.2 release. These
streams were proposed:
*
be used for countries to provide feedback on requested features and
serious bugs. Continue to use '[EMAIL PROTECTED]' ticketing system to report
bugs and get general help. Please respond if there is interest in this
mailing list.
Thanks,
Kim Quirk
VP Software and Support
-- Forwarded
We have been having similar problems in the office (tons of RF, if that
matters), where one laptop can successfully connect to a WPA client and
another one can't; or the same laptop might not be able to on a second or
third attempt.
If it worked once, it is likely that you can get it to work
Nice summary Pol!
Kim
On Wed, Jun 11, 2008 at 2:22 PM, Polychronis Ypodimatopoulos [EMAIL PROTECTED]
wrote:
This is a summary (a la Michael) of the cerebro/telepathy thread.
Pol brought up the issue of how the collaboration stack is currently
implemented, that there should be a dead-simple
We are discussing this and the best use of resources to get to 8.2.0 and
beyond. There will be many more discussions. I would like to figure out how
to make progress on cerebro.
Kim
On Tue, Jun 10, 2008 at 9:34 PM, Robert McQueen
[EMAIL PROTECTED] wrote:
Ricardo Carrano wrote:
We need
This worked pretty well for me. I booted the LiveCD off my Macbook Pro and
it started up the 703build of sugar (the previous LiveCD). Nice and fast!
The only problem was the aspect ratio of my screen doesn't meet that of
Sugar so some things are cut off the bottom making it difficult or
impossible
Some thoughts from a QA perspective:
I consider the 100 laptops that I budgeted, ordered and help install in
Peabody to be the QA collaboration testbed, which is expected to be used
to recreate problems from the field and test out next release solutions.
Since we had to dismantle Peabody, most of
The two issues that I am concerned about regarding the write protect
flag with regards to G1G1:
1 - I thought requiring signed images was part of our bitfrost
security. Doesn't it provide some protection from malicious images?
Assuming we get to the point where upgrading is an easy click from the
and warranties. I believe these issues (and
perhaps more) will be different for almost every country.
Kim
On Sat, May 31, 2008 at 11:18 AM, Edward Cherlin [EMAIL PROTECTED] wrote:
On Fri, May 30, 2008 at 7:09 AM, Kim Quirk [EMAIL PROTECTED] wrote:
Adam and Support gang,
A second G1G1 program
John,
We experienced quite a large number of 'software broken' laptops when
we first starting shipping both in Uruguay and in the G1G1 program. I
thought one of the things Ivan did in Uruguay was to help them reflash
their laptops when they couldn't boot due to journal corruption or
other software
Developer program laptops are shipped out as US/International
keyboards, English language, AK flag set, which means they do NOT need
activation. They are permanently activated in the manufacturing data.
The only thing they need to be a developer unit is a developer key.
One more reason to add to
Including the testing ml as well.
Items that are scheduled for testing (and might have issues for the
2pm edt meeting):
1 - Build 706, candidate 8.1.1, with fixes as described by Michael (I
still see almost all the same problems with kreyol as were written up
in #6973; and there are still some
Scott,
I agree with the need for at least the four branches that you have
described below. I would think the Support team would be most familiar
with the Stable branch; the QA/Test team would do most of their work
(especially system level testing) from the Testing branch; and the
Development
Since I can't read Martin's answers in Spanish, I thought I would
answer a few in English. If these two sets of answers don't agree, can
someone point it out so we can get them right.
See inline below.
Kim
2008/5/15 Yama Ploskonka [EMAIL PROTECTED]:
Hi y'all, I am double posting for I do not
[EMAIL PROTECTED] wrote:
Hi,
On Tue, May 13, 2008 at 1:41 AM, Kim Quirk [EMAIL PROTECTED] wrote:
A high level view of this process:
1) Prioritize feature and bug fix requests from deployments, developers,
support, our sales/marketing group
2) Triage bugs to determine which bugs are critical
I'm just getting some feedback from Quanta on problems with Mongolian
laptops as they are producing a couple thousand this week and will be
shipping them out.
I will try to recreate these issues and we can see if they fit the same
areas of change and if there is another fix that could be a
This looks great, Sayamindu! Thanks for getting to this so quickly.
Michael,
Once the next step is figured out -- packaging, do we start a 704 build
(based on 703) with just these fixes? Or do I test them out in a joyride
first?
Please tell me when there is a build I can test these fixes on.
Greg,
The work that Pol is doing on mesh is all in development now... nothing that
has been released in a signed build. So I would NOT recommend that many
people try to upgrade to this. Plus I believe the work he is doing requires
api changes, so other activities probably won't work
Development and Testing community,
We have started planning for the next SW releases. The goal is a bug fix
release in a few weeks (8.1.1), and then the major August release (8.2.0).
[NOTE: the release numbers are based on my last reading of the numbering
convention... not sure if it is final.]
, closing out 95% of the 90 that
were open from previous weeks.
- continues working the replacement, reshipment and refund requests.
Kim Quirk:
- worked with various deployment teams to address their longer term feature
requests
- provided activation server management to allow deployments to get
This looks great, Poly. Can you please put this test plan and results into a
wiki page, preferably linked somewhere off the main 'Testing' page.
Thanks!
Kim
On Fri, May 9, 2008 at 3:29 AM, Polychronis Ypodimatopoulos [EMAIL PROTECTED]
wrote:
Dear devel,
Here are the latest results from
*shipping* refers to what leaves the factory in China.
We do not *ship* anything without activities installed.
If you already have a build and you upgrade, you shouldn't lose your
activities (that would be a bug if you did).
If you do a 'cleaninstall' based on the old methods of cleaninstall,
character
The \ character before the shift character should be moved up and should
be part of the character that is currently *?
(I have in front of me a Turkish keyboard at the moment).
Thanks,
Alp
On Wed, May 7, 2008 at 6:01 AM, Kim Quirk [EMAIL PROTECTED] wrote:
Hi Alp,
I was given your
Sounds great, Martin! 'super happy dev house' -- is that a new zealand
specialty?
Kim
On Sun, May 4, 2008 at 12:58 AM, Martin Langhoff [EMAIL PROTECTED]
wrote:
We just had a Super Happy Dev House thing here in Wellington,
organized by the superlative Shiny Brenda. I'll post a link to pics
Sounds great, Martin! 'super happy dev house' -- is that a new zealand
specialty?
Kim
On Sun, May 4, 2008 at 12:58 AM, Martin Langhoff [EMAIL PROTECTED]
wrote:
We just had a Super Happy Dev House thing here in Wellington,
organized by the superlative Shiny Brenda. I'll post a link to pics
Hi Bernie,
Yes SKU 23 will come from Quanta with the 'ak' flag set (no activation lease
needed). To 'roll' your own builds, you will need developer keys.
I can make you the technical contact on the activation server to get the
developer keys, or you can designate someone else.
You can get the
I'm not seeing the use case that I *think* is the primary one:
1) Backup and restore from a disaster recovery perspective.
and the secondary that goes with that is:
2) Ability to restore to a new laptop (as in the child lost the laptop or it
died and they need to restore their work to a new
OLPC's focus is on development, funding and delivery of laptops to the least
developed countries. The expectations for features, testing, support,
logistics, delivery, IT and RF infrastructure (to name a few things) are
widely different between schools in Rwanda and those in NYC (for example).
We
Walter,
Can you provide the state of the keyboards that have no note in the table:
http://wiki.laptop.org/go/Mfg-data
I have been assuming that this is the table that is most up to date. If
there is no note in saying 'not yet approved', does that mean they have been
through the entire approval
as it is our connection to the outside world and to our
local or school library. So that will have be part of any good test plan.
You get the idea...
Kim
On Mon, Apr 21, 2008 at 5:11 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote:
2008/4/20 Kim Quirk [EMAIL PROTECTED]:
Bernie,
I'd like to make two points
We are all grateful to have had Walter's leadership and inspiration to get
us to this point. It should be inspiring to see OLPC branching out,
expanding and increasing support for children in many different ways.
OLPC has increased funding and resources in 2008 toward a continued
commitment to
as far as I know. I had been in close
contact with several groups in Turkey about 12 months ago and at the
time, they were advocating the F layout. It would certainly be easy
enough to do a Q layout.
-walter
On Mon, Apr 21, 2008 at 7:29 PM, Kim Quirk [EMAIL PROTECTED] wrote:
Walter,
Can you
What happens when you want to upgrade to the next OLPC build? Do you have to
do it all again?
Kim
On Mon, Apr 21, 2008 at 10:25 PM, Martin Langhoff [EMAIL PROTECTED]
wrote:
On Mon, Apr 21, 2008 at 3:37 PM, Bryan Berry [EMAIL PROTECTED]
wrote:
Currently, I use an extremeley inelegant method
Bernie,
I'd like to make two points regarding your notes:
1 - OLPC cannot be responsible for activities. So it is really much better
that the activities are now separate from the base code to help get this
point across to the country. As a 'sales' type person, you need to convey
that activities
and I spent many
hours working to broaden and deepen communication channels throughout
the project. I also helped prepare a collection of activation leases for
Mexico and I began trying to comprehend what packages could be updated
in a near-term bug-fix release if the need arose to make one.
Kim Quirk
Bernie,
It is really, really important that we don't encourage countries to have
their own images if they are not developers participating in active
development of our code base.
We've had some good discussions around this recently as it has become very
difficult to support Uruguay. This is why
In my experience running QA teams and releases for commercial projects,
small fast releases require (or imply) quite a bit of focused process and
really good automation on the testing side.
Also, after other discussions on this list, it seems like there are two
other items that drive 'major
I thought there might be a wireless driver piece that needed to be
addressed. I gave the PEAP trac item to Michail for comment.
Thanks,
Kim
On Thu, Apr 17, 2008 at 1:51 PM, Marten Vijn [EMAIL PROTECTED] wrote:
On Thu, 2008-04-17 at 09:27 -0400, Kim Quirk wrote:
Martin, Wad,
We have
Walter found a problem with Chat when using an open AP between two laptops.
The Chat invitation shows after the first one shares it, but when the second
laptop clicks on it, that opens a new chat -- it doesn't open the shared
one. THey can't chat.
It worked in simple mesh and school server mesh.
, 2008 at 10:02 AM, Bryan Berry [EMAIL PROTECTED] wrote:
Hey guys,
Today I tested out almost of all of the activities on
wiki.laptop.org/go/Activities on build 702.
I remember reading an e-mail from Kim Quirk asking folks to test
installing the activities on build 702. I am posting my
Ricardo,
Use this link to create your customization USB stick:
http://wiki.laptop.org/go/Customization_key#Preparing_the_key:
Chris,
I have pulled together a set of bundles that include the latest version of
each of the activities that shipped with G1G1. I would like people to use
this set of
Sounds great!!
Thanks,
Kim
On Sun, Mar 23, 2008 at 10:00 PM, Chris Ball [EMAIL PROTECTED] wrote:
Hi Kim,
Chris, I have pulled together a set of bundles that include the
latest version of each of the activities that shipped with G1G1. I
would like people to use this set of
Michael,
It seems like recording the compatibility matrix between builds and
activities alone is a 2-3 person job in the very near future. Today it is
probably a full time QA person -- and we are short about 3 QA people right
now.
It would be great to get some feedback as to how this can be
Great! Thanks for the update, Chris.
Kim
On Sun, Mar 2, 2008 at 7:05 PM, Chris Ball [EMAIL PROTECTED] wrote:
Hi,
Daf and I got the school server jabberd/shared roster working today.
We connected/registered 32 laptops to it with mesh TTL set to 1 for
broadcast, and they were all able to see
All developers in the 1CC area should plan to spend time in the board room
helping with setup, discussion of bugs, builds, and testing for our scaling,
mesh testing. Please don't run any XO laptops outside of the board room
today (and perhaps this whole week).
Thanks!
Kim
changes related to 4470.
Ricardo, can you confirm this?
If we decide on the build by tonight, I can have all the XOs updated and
ready by tomorrow.
On Sat, Feb 23, 2008 at 5:08 PM, Kim Quirk [EMAIL PROTECTED] wrote:
Agreed that Read sharing is the highest priority application.
My concern
Right. But the suspend and resume problems we've seen with the mesh and
sharing can be recreated on a relatively small number of laptops (10). So
we will either fix the problems, or turn off suspend in order to test for
scaling issues above 50. We have 50 MPs for next weeks testing.
So we should
Agreed that Read sharing is the highest priority application.
My concern is if there are a lot of other things in joyride, then it will
take us a long time to get a release out based on joyride.
If we pull the fix for Read back into update.1, (and other things that we
find next week), then we
It does feel like we should turn off suspend for some of our testing.
I've experienced similar problems.
Chris, do you recommend removing ohm? Or is there something else we should try?
Kim
On 2/19/08, Ricardo Carrano [EMAIL PROTECTED] wrote:
I believe the most important issue here is that,
Thanks Ricardo!
Kim
On Feb 11, 2008 10:59 AM, Ricardo Carrano [EMAIL PROTECTED]
wrote:
Kim,
I wrote http://wiki.laptop.org/go/Libertas_Debug and linked from
Test_Config_Notes.
On Feb 9, 2008 2:17 AM, Kim Quirk [EMAIL PROTECTED] wrote:
Ricardo,
Can you add this 'enable wireless debug
I'm worried about these two Regression bugs. Things that worked in 656, last
good shipping build:
- Problem copying a photo to a write doc -
6405http://dev.laptop.org/ticket/6405(mstone is working on it)
- Problem when sharing a document; try to add a photo and write
crashes - 6407
Gary,
Did you upgrade to 691 via olpc-update?
If so, can you remove your /home/olpc/.sugar/default/nm/network.cfg file and
reboot? I had to do this to get my WPA connection to work. I haven't been
able to test WEP with this build, but I wouldn't be surprised if it is
similar.
Ricardo,
Can you
Calling all Testers!
This release candidate is available and ready for serious testing, build
691. Before Chih-yu left the office she pulled together some wiki pages with
test cases and a place to record some results.
Please take a look - help refine and create test cases - or help test and
Ricardo,
Can you add this 'enable wireless debug' info to the Test Config Notes:
http://wiki.laptop.org/go/Test_Config_Notes
Thanks!
Kim
On Feb 8, 2008 7:35 PM, Ricardo Carrano [EMAIL PROTECTED] wrote:
Ricardo,
Can you tell us what method of update (cleaninstall or network upgrade)
you
Mako and Bert,
I added a note to the Roadmap for Update.1, to discuss these items for
inclusion in the final release of Update.1. If it doesn't take place before
the Wed SW meeting, it should happen then. 2pm EST, irc.
Dennis,
I think it would be best if you could help drive this process for the
Earlier this week I sent out a message for people who want to help in
testing for THursday afternoons. I need to change that to Friday afternoons,
4pm EST
Over the next few weeks we are looking at the release candidates for
Update.1.
A reminder of the agenda/wiki page:
Jim,
I think this is way too much stuff for Update.1. We are in code freeze. We
have items 1 and 2 scheduled to go into RC2; I would suggest that we ONLY
pick up Spanish, where we really fell short in the current build; I don't
agree with holding up this build for either 4 or 5, as this feels like
Thanks for your info, Martin. Are you on Trac? Can you write up a bug for
follow up?
(Or if someone knows of a trac item that Martin can use to add his notes;
that would be great).
Thanks,
Kim
2008/1/28 Martin Dengler [EMAIL PROTECTED]:
I hate to trac something so vague, but please let me know
Hi Gary,
Thanks for these notes!
On the WPA/WEP issues with this build, there is a trac bug already open,
#6123 (WEP) or #6191 (WPA). Can you add your info to one of those?
The other two issues might need new trac items.
- kim
On Jan 27, 2008 9:24 AM, Gary Oberbrunner [EMAIL PROTECTED] wrote:
I can't log into my simple WEP at home with this build...and I have had many
builds where this has worked just fine, so I'm confident it is the build.
Does anyone know why this is so broken in 690? Will we be able to get a fix?
Trac item: 6123
Kim
On Jan 26, 2008 10:29 AM, Bert Freudenberg
Hi Teresa,
It seems to me that it would be really good if you could somehow mark the
activities which currently don't load or run on a particular build so others
will not both trying to load them until they are fixed...
It will be important to note what build didn't work, as well as what build
Jan 7, 2008
This week we expect to finish testing on Ship2.2, with a few fixes as
described in the USR (unscheduled software release),
http://wiki.laptop.org/go/OLPC_SW-ECO_2.
Update1, based on joyride, is the other focus for bug fixes and testing.
Please use the Test Group Release Notes for a
Marco,
If this is the same issue that I just encountered in Joyride, then the login
is now 'olpc' instead of 'root'. No password. Sudo should work (i believe).
Kim
On Dec 24, 2007 5:21 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote:
Hello,
how do we login as root in the latest Update.1
Thanks for doing this work, Marco!
I want to add an Update1 blocker, 5671, which is how to get a developer key.
In the previous versions there was a link from the laptop to get a developer
key (from the 'about your XO' in the browser)... I can't find that link in
the most recent joyrides.
Also,
: contact the 'Give Many' program:
[EMAIL PROTECTED], 800-379-7017
- How can I apply to the Developers program?
http://wiki.laptop.org/go/Developers_Program
Things that the Netherlands community could do would include making
emulation/virtualization.
-kim
On Dec 17, 2007 12:37 PM, Kim
Now that we have G1G1 recipients we would like to discuss ways to help
people get started and how to help answer all the questions that have begun
to hit via [EMAIL PROTECTED], multiple IRC channels, forums,
community-support, etc.
Here are some ideas for agenda:
* Groupings of people: by media
Michail,
We have two other critical bug fixes that require us to do a build
today and get it out asap.
I had put the new firmware on that list to get into the new build, but
we really have to understand if this bug is real. If you and Ricardo
can look at this today (build is scheduled for 5pm),
Elijah,
Thanks for this information. It would be great if you can start a bug with
all this info and then we can follow the suggested steps and results.
Ricardo - can you add suggested tests for Elijah since this is an area you
have spent a lot of your time recently :-)
Thanks,
Kim
On Dec 10,
One extra piece of info: Once you get a developers key, you should 'disable
security' from the OK prompt.
Then you can upgrade to any image.
Here is a link to the wiki page with the process:
http://wiki.laptop.org/go/Guide_to_Secure_Install
Kim
On 04 Dec 2007 10:36:21 -0500, Alexander M.
My suggestion is that people should test the joyride builds.
At this point many bugs in ship2 have already been fixed in joyride. Be
sure to include the build number and steps for reproduction in a bug report
-- that helps alot!
Thanks,
Kim
On Dec 1, 2007 5:41 PM, ffm [EMAIL PROTECTED] wrote:
Please try Update1, build 641. The latest wireless firmware and kernel
changes for the 4470 fix are in this build.
Thanks,
Kim
On Nov 25, 2007 7:44 PM, Javier Cardona [EMAIL PROTECTED] wrote:
Hi Hal,
On 11/25/07, Hal Murray [EMAIL PROTECTED] wrote:
After a while (1 to several hours), the
it go away... I've seen this for a while now,
all the way back to joyride 20x
Shall I file a bug for that too?
Regards,
- Pascal.
On 12 nov 2007, at 20:51, Kim Quirk wrote:
Did anyone write up a trac bug?
Also, Please add quick notes for really broken things here:
http
Notes/major bugs on the 262 build can be found here:
http://wiki.laptop.org/go/Test_Group_Release_Notes
I don't believe we've been able to get through basic smoke with joyride or
update.1 builds... until we do, it is probably good to use this page for
bugs that have to addressed asap (blockers)
John,
It sounds like you recommend that Quanta put 624 on the laptops at the end
of mfg test.
Is that true?
If so, I would support that decision as well; and we don't need to go
through the release testing for 625.
Regards,
Kim
On 11/4/07, John Watlington [EMAIL PROTECTED] wrote:
There
This weekend I found that opening too many activities too quickly (I opened
about 5 activities before waiting for them to each open); caused my machine
to hang miserably. After about 20 minutes of absolutely no response, I held
down the power button. There was no virtual terminal or dev teminal,
, on
B4. In this circumstance, how should we proceed? Should we proceed
to push the changes to branch? Or is it a bad idea and it should be
deferred?
Thanks!
-- Yoshiki
At Mon, 22 Oct 2007 10:43:46 -0400,
Kim Quirk wrote:
Schedules:
This is the last week of changes to the FRS
Thanks for putting these all together, Yani.
Dafydd and Simon - can we discuss these and the new mesh protocol at the
12:30pm edt meeting today? I think some of these issues are supposed to be
addressed with the more robust protocol.
Thanks,
Kim
On 10/23/07, Giannis Galanis [EMAIL PROTECTED]
1 - 100 of 123 matches
Mail list logo
