Re: [Sugar-devel] On Sugar 0.84 - status of the Chat/collab leader issue...
On Tue, Nov 3, 2009 at 9:54 PM, David Van Assche dvanass...@gmail.com wrote: moving to mission control 5 and letting go of the admittedly antiquated sugar presence now In planning future work in rpesence and collab stuff, I have a small, humble suggestion. Figuring out if a presence service / collab infra works and scales properly on both wired and wireless networks is hard. Very hard. We've been gotten it wrong several times by looking at the theory (instead of hard-nosed testing). Right now we have something that -- while less than ideal -- at least works for a number of scenarios. If you play with a major component replacement - test it for scalability stability over wifi before doing a lot of integration work - do the integr work on a branch - test that the integrated thing works stable and scalable Of course that's ideal world stuff. However, the heart of the matter is: approach mission control tentatively... and at least _some_ significant testing needs to happen before it's merged... We've gotten this wrong a few times -- I am not keen on repeating the adventures... :-/ 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] On Sugar 0.84 - status of the Chat/collab leader issue...
Well, at least on Gnome, Mission Control not only works well, but its far more stable and does what its supposed to. Its been very heavily tested by Nokia (Maemo), Collabra, Google, openmoko and other heavy hitters. I don't really agree that we have something that works with sugar presence. In the majority of cases, where we've had testing sessions, though admittedly, with badly callibrated xmpp servers, I would go so far as to say that it was attrocious in terms of performance and stability. Once connected, collaboration worked great, but the stuff that happens before that, which is what sugar presence is supposed to be taking care of does not work well at all. If you take a look at telepathy-inspector and the advancements in telepathy itself, of which mission control 5 is one of the major overhauls, its massive improvement over the passed. And one of the main issues was that sugar presence used its own bindings, blind sighting a lot of what telepathy is doing, which is why currently it simply doesn't work. Without a xmpp server, you'll have a field day getting any kind of collaboration to work, and even with a really carefully setup ejabbberd server full of optimisations, I at least, have not been able to get the presence part to reliably do the same thing every time. Some times people show up, sometimes they dont sometimes 10 minutes later, sometimes with totally weird settings and names Its quite clear to me that what may have worked ok in 0.82, now does not. And to me that makes total sense, if u look at the timeline, the code, the blueprints, and most importantly, the actualised telepathy dbus bindings (The presence part has changed completely and looks nothing like it did when 0.82 and earlier were coded.) But dont take my word for it, take a look here and you'll see what I mean: http://people.collabora.co.uk/~danni/telepathy-book/chapter.accounts.html kind regards, David Van Assche On Wed, Nov 4, 2009 at 10:38 AM, Martin Langhoff martin.langh...@gmail.com wrote: On Tue, Nov 3, 2009 at 9:54 PM, David Van Assche dvanass...@gmail.com wrote: moving to mission control 5 and letting go of the admittedly antiquated sugar presence now In planning future work in rpesence and collab stuff, I have a small, humble suggestion. Figuring out if a presence service / collab infra works and scales properly on both wired and wireless networks is hard. Very hard. We've been gotten it wrong several times by looking at the theory (instead of hard-nosed testing). Right now we have something that -- while less than ideal -- at least works for a number of scenarios. If you play with a major component replacement - test it for scalability stability over wifi before doing a lot of integration work - do the integr work on a branch - test that the integrated thing works stable and scalable Of course that's ideal world stuff. However, the heart of the matter is: approach mission control tentatively... and at least _some_ significant testing needs to happen before it's merged... We've gotten this wrong a few times -- I am not keen on repeating the adventures... :-/ 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 -- Stephen Leacock - I detest life-insurance agents: they always argue that I shall some day die, which is not so. - http://www.brainyquote.com/quotes/authors/s/stephen_leacock.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] On Sugar 0.84 - status of the Chat/collab leader issue...
Don't get me wrong though, I agree thoroughly that we should really test it and make sure it plays as advertised But I think its gonna be easier to do that than test/scale/stabalise what we currently have. David On Wed, Nov 4, 2009 at 11:06 AM, David Van Assche dvanass...@gmail.com wrote: Well, at least on Gnome, Mission Control not only works well, but its far more stable and does what its supposed to. Its been very heavily tested by Nokia (Maemo), Collabra, Google, openmoko and other heavy hitters. I don't really agree that we have something that works with sugar presence. In the majority of cases, where we've had testing sessions, though admittedly, with badly callibrated xmpp servers, I would go so far as to say that it was attrocious in terms of performance and stability. Once connected, collaboration worked great, but the stuff that happens before that, which is what sugar presence is supposed to be taking care of does not work well at all. If you take a look at telepathy-inspector and the advancements in telepathy itself, of which mission control 5 is one of the major overhauls, its massive improvement over the passed. And one of the main issues was that sugar presence used its own bindings, blind sighting a lot of what telepathy is doing, which is why currently it simply doesn't work. Without a xmpp server, you'll have a field day getting any kind of collaboration to work, and even with a really carefully setup ejabbberd server full of optimisations, I at least, have not been able to get the presence part to reliably do the same thing every time. Some times people show up, sometimes they dont sometimes 10 minutes later, sometimes with totally weird settings and names Its quite clear to me that what may have worked ok in 0.82, now does not. And to me that makes total sense, if u look at the timeline, the code, the blueprints, and most importantly, the actualised telepathy dbus bindings (The presence part has changed completely and looks nothing like it did when 0.82 and earlier were coded.) But dont take my word for it, take a look here and you'll see what I mean: http://people.collabora.co.uk/~danni/telepathy-book/chapter.accounts.html kind regards, David Van Assche On Wed, Nov 4, 2009 at 10:38 AM, Martin Langhoff martin.langh...@gmail.com wrote: On Tue, Nov 3, 2009 at 9:54 PM, David Van Assche dvanass...@gmail.com wrote: moving to mission control 5 and letting go of the admittedly antiquated sugar presence now In planning future work in rpesence and collab stuff, I have a small, humble suggestion. Figuring out if a presence service / collab infra works and scales properly on both wired and wireless networks is hard. Very hard. We've been gotten it wrong several times by looking at the theory (instead of hard-nosed testing). Right now we have something that -- while less than ideal -- at least works for a number of scenarios. If you play with a major component replacement - test it for scalability stability over wifi before doing a lot of integration work - do the integr work on a branch - test that the integrated thing works stable and scalable Of course that's ideal world stuff. However, the heart of the matter is: approach mission control tentatively... and at least _some_ significant testing needs to happen before it's merged... We've gotten this wrong a few times -- I am not keen on repeating the adventures... :-/ 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 -- Stephen Leacock - I detest life-insurance agents: they always argue that I shall some day die, which is not so. - http://www.brainyquote.com/quotes/authors/s/stephen_leacock.html -- Marie von Ebner-Eschenbach - Even a stopped clock is right twice a day. - http://www.brainyquote.com/quotes/authors/m/marie_von_ebnereschenbac.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
versioned partitioned upgrading: safety boot configuration
Hi Michael, I'm working on updating olpc-update and the initramfs to be able to work with a partitioned layout where /boot is separate from the rest of the system. Thanks for the good documentation at http://wiki.laptop.org/go/Early_boot This means I will probably be troubling you with a few questions :) First one, I'm implementing the Create a safety boot configuration bit. I guess the purpose of this is to ensure that the current running OS is marked as current, and to free up the other OS image (so that it can be deleted soon after to make space for the incoming update). So onto the bit I have to add: (If partitioned: Make /boot/alt point to ../$a.) I don't understand this part. Surely the instructions for /boot would be equivalent to what was done above, i.e. on the boot partition: 1. make sure that /boot points at boot-versions/$a 2. remove /boot/alt Or have I just answered my own question through writing this mail? Step 1 is deemed unnecessary (we can assume that it's already pointing to the right place), and your instructions are simply making the alternate boot configuration point to exactly the same one that is booted (hence there is no longer an alternative) Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
versioned partitioned upgrading: clean up / config creation
Hi Michael, Last question for now: http://wiki.laptop.org/go/Early_boot#Clean_Up This part of the page seems to suggest that you only create a /versions/configs entry for systems where an unpartitioned layout is being used, and no config would be created for a partitioned layout. Am I reading that right? I'm having a bit of trouble getting my head around the whole system and perhaps I'm missing something obvious .. Perhaps you designed it so that boot configs in /versions/configs are not necessary when we are booting from a partitioned system, because the current and alt image hashes can be deduced from the symlinks on the boot partition at /boot and /boot/alt ? Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OOM conditions
On Fri, Oct 30, 2009 at 11:22:13PM +0100, Tomeu Vizoso wrote: On Fri, Oct 30, 2009 at 16:58, Richard A. Smith rich...@laptop.org wrote: Working the table at the Boston book festival I was reminded how painful the OOM stuff is on a gen 1. The demo machines were in this state a lot as each visitor would open up a new program. Basically you have to just turn the unit off and restart as trying to recover is futile. What if activities had a higher oom_score? Would that protect enough the processes that once killed require a system restart (X, shell, etc)? See patch vs sugar-toolkit HEAD below[1] (I can backport to 0.82 if wanted). Maybe even have the background activities have a higher oom_score than the one in the foreground? Interesting. Another approach I'd love feedback on would be to set the allowed number of simultaneous running activities to be 2 (1 + Journal) and writing a simple control panel extension that would allow tweaking that, this oom_adj, and other related gconf values. Regards, Tomeu Martin 1. patch against http://cgit.sugarlabs.org/sugar-toolkit/mainline/tree/src/sugar/activity/main.py : diff --git a/src/sugar/activity/main.py b/src/sugar/activity/main.py index 93f34e6..c868e11 100644 --- a/src/sugar/activity/main.py +++ b/src/sugar/activity/main.py @@ -31,7 +31,40 @@ from sugar.bundle.activitybundle import ActivityBundle from sugar import logger +def __oom_adj_self(omm_adj_value=None): + Change this process' OOM likelihood to oom_adj_value. + +By default, use the value of gconf path +/desktop/sugar/performance/oom_adj_default; if none exists, make +this process most likely to be killed (oom_adj_value=15). + +Linux-specific. See http://linux-mm.org/OOM_Killer for details. + +oom_adj_fullpath = /proc/self/oom_adj +if os.path.exists(oom_adj_fullpath): +try: + +# get values/defaults from gconf +import gconf +gconf_dir = /desktop/sugar/performance +gconf_key = oom_adj_default +client = gconf.client_get_default() +if not client.dir_exists(gconf_dir): +client.add_dir(gconf_dir, gconf.CLIENT_PRELOAD_NONE) +if oom_adj_value is None: +oom_adj_value = client.get_int(gconf_dir + / + gconf_key) +if oom_adj_value is None: +oom_adj_value = 15 +client.set_int(gconf_dir + / + gconf_key, + oom_adj_value) + +file(oom_adj_fullpath).write(oom_adj_value) + +except: +pass + def create_activity_instance(constructor, handle): +__oom_adj_self() activity = constructor(handle) activity.show() pgpNZISREnFmt.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Terminal.xo patch: do not die if the cwd is gone
On Tue, Nov 03, 2009 at 12:08:20PM -0500, paul fox wrote: On Tue, Nov 3, 2009 at 11:04 AM, Martin Langhoff martin.langh...@gmail.com wrote: Attached is a trivial patch that handles gracefully the situation where cwd does not exist anymore or is no longer accessible to the olpc user. frankly, i think the whole state-saving notion in Terminal (and other terminal emulators i've seen) is flawed, and a bad idea I agree. I don't see the point of Terminal's journal entries, either. (i understand the desire for restoring scrollback -- that's useful history). Perhaps. I don't find its place on the confusion/benefit curve interesting, though. paul Martin pgpraAmQibT5v.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] xs-activation and OS update info
Hi Daniel,
Working on unrelated code, I found that the iniparse module, which we
ship on our F9 and F11 OSs, knows the ordering of the sections.
from iniparse import INIConfig
import os
c = INIConfig(open(os.path.expanduser('~')+'/.sugar/default/config'))
list(c) # gives you the sections in order
cheers,
m
On Fri, Oct 30, 2009 at 2:33 AM, Daniel Drake d...@laptop.org wrote:
2009/10/30 Martin Langhoff martin.langh...@gmail.com:
It is about avoiding maintaining a bespoke lib. If you say it is a
variant on a python standard lib, do you think we can subclass it? Or
is there a reason not to?
Yeah it can probably be subclassed.
It is needed up until Python 3.0, unless you know of a python ordered
I saw a commend mentioning that something wouldn't be needed w 2.6. On
F11 we have 2.6... but maybe I misunderstood.
Ah yes, I forgot the specifics. odict is needed until Python 3.0, but
Python 2.6 adds the dict_type constructor parameter for ConfigParser
so MyConfigParser is not needed with python 2.6.
Daniel
--
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-de...@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
Re: [Sugar-devel] Terminal.xo patch: do not die if the cwd is gone
On 4 Nov 2009, at 14:56, Martin Dengler wrote: On Tue, Nov 03, 2009 at 12:08:20PM -0500, paul fox wrote: On Tue, Nov 3, 2009 at 11:04 AM, Martin Langhoff martin.langh...@gmail.com wrote: Attached is a trivial patch that handles gracefully the situation where cwd does not exist anymore or is no longer accessible to the olpc user. frankly, i think the whole state-saving notion in Terminal (and other terminal emulators i've seen) is flawed, and a bad idea I agree. I don't see the point of Terminal's journal entries, either. With tabs, the last page of text, and dir location being saved, I find it extremely useful for development. I only have a couple of Terminal Journal entries, one my default (usually just in one of the activities directories I'm currently working/testing on), and another with a bunch of tabs in various deep sugar directory paths useful for poking about and tweaking Sugar innards. Saves a heap of cd'ing about and trying to remember where some darn Sugar resource buried. (i understand the desire for restoring scrollback -- that's useful history). Perhaps. I don't find its place on the confusion/benefit curve interesting, though. I would find some scrollback handy, but buffer history state saving would be a killer feature for me at least ;-) Regards, -Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] xs-activation and OS update info
2009/11/4 Martin Langhoff martin.langh...@gmail.com: Hi Daniel, Working on unrelated code, I found that the iniparse module, which we ship on our F9 and F11 OSs, knows the ordering of the sections. Cool, indeed, their site makes it pretty clear that preserving order is a feature. Daniel ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
crond disabled?
chkconfig --list shows crond completely disabled. Accident or by design? If it's by design, any hints on alternative means of running cron-ish jobs? 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Changes in the handling of sleep in idlesuspend (rtcwake?) for F11 based builds?
Hi Chris, long time ago you warned me that towards our 9.1 release the handling of sleep would change, and that I would need to setup a wakeup alarm. Is this happening on any of our builds? If so, we need a quick audit of shell scripts using sleep More details at http://dev.laptop.org/ticket/8177 -- perhaps we were waiting on something in kernel land that may now be there...? cheers, 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: crond disabled?
Agreed, on both F11 for XO-1 (os8) and F11 for XO-1.5 (os33). However / etc/cron.d has olpc specific files present. I see olpc things in /etc/cron.d/, but I don't see any way to get to it. /etc/crontab is empty (on my os8 on a XO-1) So is /var/spool/cron/ F9 for XO-1 (802) uses crond for ds-backup, olpc-pwr-prof, and olpc-update. Do we really want to be running something like update which (I assume) takes significant resources without consulting with the user? I'd be grumpy if things slowed down mysteriously, or worse if my real work got killed because some cron job triggered OOM. My home systems do most of their cron work in the early morning when I'm asleep. (I leave them running 7x24.) Sometimes, I'm still up when some of the heavy work starts running and the performance hit is annoying. How do people with laptops handle cron jobs? I'd expect them to be turned off at the equivalent of early morning. How/when do you do backups? updates? -- These are my opinions, not necessarily my employer's. I hate spam. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: crond disabled?
2009/11/4 Hal Murray hmur...@megapathdsl.net: Do we really want to be running something like update which (I assume) takes significant resources without consulting with the user? Yes! Remember, these are not designed as normal laptops. They are for young children and for use in schools. The only time to do updates is when the child is at school, connected to the school server, and if updates are not fully automatic then they simply will not happen. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: crond disabled?
Keep in mind that some of cron's duties are done by anacron (or were when I had a hand in the distro), which is laptop-friendly. Anacron only handles daily/weekly/monthly tasks, though; you do need cron running if you want tasks with sub-day scheduling. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: crond disabled?
c. scott ananian wrote: Keep in mind that some of cron's duties are done by anacron (or were when I had a hand in the distro), which is laptop-friendly. Anacron only handles daily/weekly/monthly tasks, though; you do need cron running if you want tasks with sub-day scheduling. as dsd pointed out to me on IRC, anacron is driven by cron -- at least these days it seems to be. so without cron, anacron probably won't work either. (i was under the impression they were separate, but perhaps that's ancient history, or i was just wrong.) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: crond disabled?
On Wed, Nov 4, 2009 at 5:01 PM, Paul Fox p...@laptop.org wrote: c. scott ananian wrote: Keep in mind that some of cron's duties are done by anacron (or were when I had a hand in the distro), which is laptop-friendly. Anacron only handles daily/weekly/monthly tasks, though; you do need cron running if you want tasks with sub-day scheduling. as dsd pointed out to me on IRC, anacron is driven by cron -- at least these days it seems to be. so without cron, anacron probably won't work either. (i was under the impression they were separate, but perhaps that's ancient history, or i was just wrong.) That's *mostly* right. Anacron is idempotent, it just needs to be triggered at least once a day so it can check to see if there's stuff to do. It's invoked from initscripts/upstart at power up, and is often invoked on resume-from-suspend as well. But if you actually leave the machine on and unsuspended for 1 day, you need to trigger it from cron as well to make sure it gets a chance to do its thing. It never hurts to invoke anacron, you just need to ensure a certain minimum frequency of invocation -- and cron is usually used to do this. But you don't always immediately notice if cron is missing, because anacron will still do its thing on startup, etc. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: crond disabled?
Do we really want to be running something like update which (I assume) takes significant resources without consulting with the user? Yes! Remember, these are not designed as normal laptops. They are for young children and for use in schools. The only time to do updates is when the child is at school, connected to the school server, and if updates are not fully automatic then they simply will not happen. In an endeavor *completely* removed from OLPC (or the XO), I've had a long-standing philosophy difference - I'm a hands on guy - and they don't want to facilitate that. Now with regard to automatic updates, the same philosophy difference is showing up with the XO: Wiki page http://wiki.laptop.org/go/Update_streams describes how by specifying 'none' as the update-stream value, updates are supposed to be never update me (automatically). Yet, despite me always having 'none' in /security/update-stream -- in 2007/2008 if I entered 'top' I all too frequently saw 'olpc-update-query' using system resources (uselessly, because it was unable to get through my proxy back to any server). [I do updating with manual commands.] Please -- do run your automatic updates to your heart's content. But if a non-child XO user like me has specified 'none' -- DON'T run automatic updates. Thanks, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: crond disabled? [#9605]
Being tracked. http://dev.laptop.org/ticket/9605 -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: crond disabled?
On Wed, Nov 4, 2009 at 4:40 PM, Mikus Grinbergs mi...@bga.com wrote: Do we really want to be running something like update which (I assume) takes significant resources without consulting with the user? Yes! Remember, these are not designed as normal laptops. They are for young children and for use in schools. The only time to do updates is when the child is at school, connected to the school server, and if updates are not fully automatic then they simply will not happen. In an endeavor *completely* removed from OLPC (or the XO), I've had a long-standing philosophy difference - I'm a hands on guy - and they don't want to facilitate that. Now with regard to automatic updates, the same philosophy difference is showing up with the XO: Wiki page http://wiki.laptop.org/go/Update_streams describes how by specifying 'none' as the update-stream value, updates are supposed to be never update me (automatically). Yet, despite me always having 'none' in /security/update-stream -- in 2007/2008 if I entered 'top' I all too frequently saw 'olpc-update-query' using system resources (uselessly, because it was unable to get through my proxy back to any server). [I do updating with manual commands.] Please -- do run your automatic updates to your heart's content. But if a non-child XO user like me has specified 'none' -- DON'T run automatic updates. Mikus: olpc-update-query should be launching, seeing your 'none' stream, and immediately exiting. It's just a software maintenance issue that it launches at all; cron doesn't allow conditionals in crontab. I don't have the source handy, but I suspect I implemented 'none' server side just to avoid cluttering up the client code with special cases, but I'm sure a patch would be accepted to do early exit on 'none' if you'd like to write one. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] XS 0.6 on XO
Really nice to have an XS on the XO for testing and showing people what they can do with an XS. The easy setup which doesn't even need an access point is really cool. There are 3 points about XS 0.6 on XO I want to bring up: 1. How to shutdown the XS. I couldn't find the information what is the easiest way to do it. I see to easy options: - Switching off power means the XS shuts down (I have attached an acmon script a workmate wrote some time ago for a webserver on an XO which does that using crontab) - ctrl+alt+delete (on the XO delete is fn+erase) does a reboot at the moment, but I think it could be easily changed to a more useful shutdown. 2. How to change the timezone is missing in the documentation, but probably necessary in most places. 3. Non XO computers can not connect to the school-mesh-0 of the XS on XO. I wanted to do some testing and had just one XO (which was running the XS). To be able to connect from a normal laptop I had to do the following changes on the XS (the specific IP is important since various services are bound to this IP): ifdown lanbond0 iwconfig wmesh0 essid schoolserver iwconfig wmesh0 mode ad-hoc iwconfig wmesh0 channel 6 ifconfig wmesh0 172.18.0.1 Is there an easier way? Cheers, Philipp #!/bin/bash #** # Script: acmon # Author: matt # Purpose: checks if ac power gone from xo and schedules shutdown. # If the ac power is restored and there is a shutdown in progress # then the shutdown will be cancelled # Should be run from /etc/crontab as follows : # 00,10,20,30,40,50 * * * * root /usr/local/bin/acmon # NOTE the cron interval needs to less than the SHTDWNTIME # so that the server picks up if the power is back down # Versions: # 0.1 04/04/08Initial Matt # 0.2 05/04/08added -h switch to shudown Matt #** # Length of time before shutdown SHTDWNTIME=15 # if there is no ac power if [ $(cat /sys/class/power_supply/olpc-ac/online) = 0 ]; then # if there no shutdown in progress then schedule on in 15 mins pgrep shutdown /dev/null 21 if [ $? -ne 0 ]; then shutdown -h $SHTDWNTIME power failed /dev/null 21 logger -p info acmon: Shutting down in $SHTDWNTIME minutes due to ac pwr failure else logger -p info acmon: No ac power and shutdown already in progress fi else # if there is ac power and a shutdown in progress cancel it... pgrep shutdown /dev/null 21 if [ $? -eq 0 ]; then shutdown -c /dev/null 21 logger -p info acmon: Cancelling shutdown due to ac pwr restore fi fi ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
New F11 for XO-1.5 build 36
http://wiki.laptop.org/go/F11_for_1.5 http://dev.laptop.org/~cjb/f11-1.5/os36 Compressed image size: 412.28mb (-0.30mb since build 35) Description of changes in this build: * Wireless works again, fixed in #9606. * #9601: avoid a resume crash by changing agetty args. * #9605: re-enable crond Package changes since build 35: -kernel-2.6.30_xo1.5-20091104.0546.1.olpc.cf6b007.i586 +kernel-2.6.30_xo1.5-20091104.1716.1.olpc.019dbcf.i586 -kernel-firmware-2.6.30_xo1.5-20091104.0546.1.olpc.cf6b007.i586 +kernel-firmware-2.6.30_xo1.5-20091104.1716.1.olpc.019dbcf.i586 +libertas-sd8686-firmware-9.70.7.p0-1.fc11.noarch -libertas-usb8388-firmware-5.110.22.p23-2.fc11.noarch -xorg-x11-drv-openchrome-0.2.903-16.fc11.i586 +xorg-x11-drv-openchrome-0.2.904-1.fc11.1.i586 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
versioned partitioned upgrading: safety boot configuration
Hi Dan, I'm working on updating olpc-update and the initramfs to be able to work with a partitioned layout where /boot is separate from the rest of the system. Thanks for the good documentation at http://wiki.laptop.org/go/Early_boot You're welcome; apologies that it isn't better. :) First one, I'm implementing the Create a safety boot configuration bit. I guess the purpose of this is to ensure that the current running OS is marked as current, and to free up the other OS image (so that it can be deleted soon after to make space for the incoming update). Correct. So onto the bit I have to add: (If partitioned: Make /boot/alt point to ../$a.) I don't understand this part. Surely the instructions for /boot would be equivalent to what was done above, i.e. on the boot partition: 1. make sure that /boot points at boot-versions/$a 2. remove /boot/alt First, understand that Scott+Mitch wrote the logic for updates with partitions. I am only a secondary source for this scenario. The primary source is the pre-formatted version of the upgrade procedure, which may be found here: http://wiki.laptop.org/index.php?title=Early_bootoldid=77286#Upgrade_procedure Second, unfortunately, the instructions as written are *not* equivalent: Mitch and Scott decided to simplify the partitioned design by insisting that a) boot:/boot be a symlink pointing to 'boot-versions/XXX' b) boot:/boot/alt be a symlink pointing to '../YYY'. Or have I just answered my own question through writing this mail? Step 1 is deemed unnecessary (we can assume that it's already pointing to the right place), and your instructions are simply making the alternate boot configuration point to exactly the same one that is booted (hence there is no longer an alternative) I concur with this answer to your question. Regards, Michael P.S. - Tit for tat: how is the correct root partition identified and communicated from ??? - OFW - initramfs - ??? - updater - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
versioned partitioned upgrading: clean up / config creation
Last question for now: http://wiki.laptop.org/go/Early_boot#Clean_Up This part of the page seems to suggest that you only create a /versions/configs entry for systems where an unpartitioned layout is being used, and no config would be created for a partitioned layout. Am I reading that right? I'm having a bit of trouble getting my head around the whole system and perhaps I'm missing something obvious .. Perhaps you designed it so that boot configs in /versions/configs are not necessary when we are booting from a partitioned system, because the current and alt image hashes can be deduced from the symlinks on the boot partition at /boot and /boot/alt ? Thanks, Daniel The configs mechanism is only used for unpartitioned systems. The linkage from boot data to tree-ids is, as you say, recorded in the boot:/boot and boot:/boot/alt symlinks. I don't think the current writeup says where the contents manifests should be stored on partitioned systems. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
