Talk:Update paths: Difference between revisions
(→Conflicting information: respond) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 27: | Line 27: | ||
I think that rather than requiring the actual build number to be entered (ie 711, 8.2-759, etc) it would be better to have text names, such as 'stable','beta', or 'RC'. That way, users could run the update routine without needing to research what the current build number was. You could even automate the updates so that the system checks at boot for available updates and it always gets the latest stable version. Then, the RSYNC process wouldn't be such a monumental task at the major updates. |
I think that rather than requiring the actual build number to be entered (ie 711, 8.2-759, etc) it would be better to have text names, such as 'stable','beta', or 'RC'. That way, users could run the update routine without needing to research what the current build number was. You could even automate the updates so that the system checks at boot for available updates and it always gets the latest stable version. Then, the RSYNC process wouldn't be such a monumental task at the major updates. |
||
: Good points. I think olpc-update with certain arguments already gets latest build, and I read somewhere about XOs checking once a day for latest software. In builds after about August, olpc-update's first rsync attempt (the "pristine" one) is more likely to succeed so the process goes much faster. -- [[User:Skierpage|Skierpage]] 00:09, 28 September 2008 (UTC) |
: Good points. I think olpc-update with certain arguments already gets latest build, and I read somewhere about XOs checking once a day for latest software. In builds after about August, olpc-update's first rsync attempt (the "pristine" one) is more likely to succeed so the process goes much faster. -- [[User:Skierpage|Skierpage]] 00:09, 28 September 2008 (UTC) |
||
== update problems == |
|||
I am trying to update from version 656 to 711. I think I have followed all the instructions, but when I type the commands in the Terminal Activity, I get the following error message: |
|||
"bash: sudo: command not found" |
|||
Do you have any suggestions on my next steps? |
|||
Thanks. |
|||
OK, I kept poking around and answered my own questions. I needed to type "su -l" to get to the Super User state. Then I was allowed to type "olpc-update 711". |
|||
Perhaps the "su -l" should be documented on the Update paths page. |
|||
Latest revision as of 03:51, 28 September 2008
It's unfortunate that external applications are being wiped out with each OS update. I know that some folks consider this to be a feature, not a bug, but I can't really test new builds on the laptop if upgrading wipes out my whole carefully configured environment (external applications that aren't .xo bundles).
Online updates not requiring AC power?
You note that AC power is not required for online updates. Is this true in all cases? How about updates that might also flash the Firmware. Or is there no such online update variety?Alc 12:47, 12 February 2008 (EST)
I just did an online update of 656 and althought the battery and AC worked fine before, upon restart it told me this: got firmware version CL1 Q2D07 Q2D checking integrity... updating firmware battery not present powering off in 10 sec
i've removed and reinstalled the battery twice, making sure it's clean.
no go. why would the battery die right after an update if it was plugged in that whole time?
hmmm. anyone got ideas?
Conflicting information
The information on this page appears to indicate that activities only need to be installed separately when updating offline. However, the information at http://wiki.laptop.org/go/Release_Notes/8.1.0 suggests that activities now must always be installed separately (which was my experience when upgrading a while back).
- Yes, your first update to "Update.1" 8.1.0 or higher will lose the pre-installed Ship.1 activities unless you update using a special build that bundles them. Thereafter, the activities you install stick around through olpc-update. And in the awesome 8.2.0 release, the Software update in the Sugar control panel will download the latest versions of activities for you. -- Skierpage 00:12, 28 September 2008 (UTC)
OLPC-UPDATE command suggestion
I think that rather than requiring the actual build number to be entered (ie 711, 8.2-759, etc) it would be better to have text names, such as 'stable','beta', or 'RC'. That way, users could run the update routine without needing to research what the current build number was. You could even automate the updates so that the system checks at boot for available updates and it always gets the latest stable version. Then, the RSYNC process wouldn't be such a monumental task at the major updates.
- Good points. I think olpc-update with certain arguments already gets latest build, and I read somewhere about XOs checking once a day for latest software. In builds after about August, olpc-update's first rsync attempt (the "pristine" one) is more likely to succeed so the process goes much faster. -- Skierpage 00:09, 28 September 2008 (UTC)
update problems
I am trying to update from version 656 to 711. I think I have followed all the instructions, but when I type the commands in the Terminal Activity, I get the following error message: "bash: sudo: command not found"
Do you have any suggestions on my next steps?
Thanks.
OK, I kept poking around and answered my own questions. I needed to type "su -l" to get to the Super User state. Then I was allowed to type "olpc-update 711".
Perhaps the "su -l" should be documented on the Update paths page.