zen root (was Re: Flash wiki entries)
On Fri, Jan 2, 2009 at 11:41 AM, Samuel Klein wrote: >>> Anyway, why does this wiki page tell you to enter >>> sudo su - > > Some future zen compilation of sudo may support infinite nesting of > levels of protectedness, so that you have to really REALLY mean it to > say sudo sudo sudo 'make me a sandwich' I had Zen Buddhist priest training, and I have publicly taken a vow never to write anything entitled Zen and the Art of Computer Programming. Stan Kelly-Bootle thought that vow worth recording in The Computer Contradictionary. So don't start any Zen threads here unless you know enough to mean it. ^_^ > SJ -- Silent Thunder (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) is my name And Children are my nation. The Cosmos is my dwelling place, The Truth my destination. http://wiki.sugarlabs.org/go/User:Mokurai ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora Desktop on XO
Hi Chris, No probs on the reply. > Hi Peter, thanks for the reply, > > > Is this on 8.2.0 or joyride? It looks like 8.2 due to the > > gnome-python version being olpc3. > > It's running a joyride F10 build, but looks like you're right about > olpc3. Here's the /etc/yum.repos.d/olpc-development.repo shipped in > Joyride: > > [olpc_development] > name=OLPC development repository, based on koji tag dist-olpc3-devel. > baseurl=http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ > enabled=1 > gpgcheck=0 > exclude=kernel > > [olpc-joyride] > name=OLPC 'Joyride' repository > baseurl=http://xs-dev.laptop.org/~cscott/repos/joyride/ > enabled=1 > gpgcheck=0 > > > I suspect some of the errors are due to the custom packages, or > > possibly due to a repo not being available. You can get some weird > > errors if there's two package provides split across repos > > (something like a base gnome-python provided by the olpc3 repo > > where as the gnome-python-blah which was stripped out of the olpc3 > > build is then provided by the Fedora 9 repo. Overall it looks like > > an issue with cyrus-sasl. What does a "yum list cyrus-sasl*" show? > > Excluding Packages from Fedora 10 - i386 > Finished > Excluding Packages from OLPC development repository, based on koji tag > dist-olpc3-devel. > Finished > Excluding Packages from Fedora 10 - i386 - Updates > Finished > Installed Packages > cyrus-sasl-lib.i386 2.1.22-19.fc10 installed > Available Packages > cyrus-sasl.i386 2.1.22-15.fc9 olpc_development > cyrus-sasl-debuginfo.i3862.1.22-15.fc9 olpc_development > cyrus-sasl-devel.i3862.1.22-15.fc9 olpc_development > cyrus-sasl-gssapi.i386 2.1.22-15.fc9 olpc_development > cyrus-sasl-krb4.i386 2.1.22-15.fc9 olpc_development > cyrus-sasl-ldap.i386 2.1.22-15.fc9 olpc_development > cyrus-sasl-md5.i386 2.1.22-15.fc9 olpc_development > cyrus-sasl-ntlm.i386 2.1.22-15.fc9 olpc_development > cyrus-sasl-plain.i3862.1.22-15.fc9 olpc_development > cyrus-sasl-sql.i386 2.1.22-15.fc9 olpc_development I would remove the old fc9 build from the olpc_development repo (or even have one for 8.2.0 and one for 9.1.0 so they don't get mixed up). Surely it should be pulling cyrus-sasl from the Fedora repos anyway? Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora Desktop on XO
Hi Peter, thanks for the reply, > Is this on 8.2.0 or joyride? It looks like 8.2 due to the > gnome-python version being olpc3. It's running a joyride F10 build, but looks like you're right about olpc3. Here's the /etc/yum.repos.d/olpc-development.repo shipped in Joyride: [olpc_development] name=OLPC development repository, based on koji tag dist-olpc3-devel. baseurl=http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ enabled=1 gpgcheck=0 exclude=kernel [olpc-joyride] name=OLPC 'Joyride' repository baseurl=http://xs-dev.laptop.org/~cscott/repos/joyride/ enabled=1 gpgcheck=0 > I suspect some of the errors are due to the custom packages, or > possibly due to a repo not being available. You can get some weird > errors if there's two package provides split across repos > (something like a base gnome-python provided by the olpc3 repo > where as the gnome-python-blah which was stripped out of the olpc3 > build is then provided by the Fedora 9 repo. Overall it looks like > an issue with cyrus-sasl. What does a "yum list cyrus-sasl*" show? Excluding Packages from Fedora 10 - i386 Finished Excluding Packages from OLPC development repository, based on koji tag dist-olpc3-devel. Finished Excluding Packages from Fedora 10 - i386 - Updates Finished Installed Packages cyrus-sasl-lib.i386 2.1.22-19.fc10 installed Available Packages cyrus-sasl.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-debuginfo.i3862.1.22-15.fc9 olpc_development cyrus-sasl-devel.i3862.1.22-15.fc9 olpc_development cyrus-sasl-gssapi.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-krb4.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-ldap.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-md5.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-ntlm.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-plain.i3862.1.22-15.fc9 olpc_development cyrus-sasl-sql.i386 2.1.22-15.fc9 olpc_development Thanks! - Chris. -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora Desktop on XO
> Hi Greg, > > Sorry for delayed response, I've had little internet connectivity so > have only had limited mail access and mostly through a windows box :( > >> I'm still looking for help resolving the dependencies Chris found when he >> tried to install Gnome. >> >> The issue and thread are documented in the specifications section here: >> http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO >> >> What do we do next when we get a list of "dependency errors"? > > Is this on 8.2.0 or joyride? It looks like 8.2 due to the gnome-python > version being olpc3. I suspect some of the errors are due to the > custom packages, or possibly due to a repo not being available. You > can get some weird errors if there's two package provides split across > repos (something like a base gnome-python provided by the olpc3 repo > where as the gnome-python-blah which was stripped out of the olpc3 > build is then provided by the Fedora 9 repo. Overall it looks like an > issue with cyrus-sasl. What does a "yum list cyrus-sasl*" show? The other thing to check for is that there isn't multiple versions installed (rpm -qa | grep cyrus), I've seen this sometimes with things like glibc and openssl where there's both an i386 and i686 version. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problems with Adobe Flash player on the XO.
> On Fri, Jan 02, 2009 at 10:56:59PM +0800, Carlos Nazareno wrote: >>Ditto. I've tried Sugarizing newer versions of Opera myself, but we're >>out of luck because of the Rainbow Security implemented in newer XO OS >>builds don't allow writing of files by Activities to certain >>directories that Opera installs to. The Opera dudes will have to >>create a special OLPC Opera Activity for us like with 9.12 since Opera >>is not open sourced and we won't be able to do the proper >>modifications for Rainbow Security compatibility ourselves. I do a fair amount of "customization" on every build I install. Therefore the fact that current Opera versions for example want to install something in /etc is no obstacle for me - I just "lump" that requirement with the other "system modifications" I apply (e.g., putting something in /etc to support 'rsync' between XOs)). [I also install the Adobe Flash-10 player onto all the Browsers my XO has.] In any case, I have for a long time been running Opera (currently 9.60) on (F9-based) 8.2 and on (F10-based) Joyride. I launch Opera from its icon in Home view. I do not need to disable Rainbow in order to run Opera. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora Desktop on XO
Hi Greg, Sorry for delayed response, I've had little internet connectivity so have only had limited mail access and mostly through a windows box :( > I'm still looking for help resolving the dependencies Chris found when he > tried to install Gnome. > > The issue and thread are documented in the specifications section here: > http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO > > What do we do next when we get a list of "dependency errors"? Is this on 8.2.0 or joyride? It looks like 8.2 due to the gnome-python version being olpc3. I suspect some of the errors are due to the custom packages, or possibly due to a repo not being available. You can get some weird errors if there's two package provides split across repos (something like a base gnome-python provided by the olpc3 repo where as the gnome-python-blah which was stripped out of the olpc3 build is then provided by the Fedora 9 repo. Overall it looks like an issue with cyrus-sasl. What does a "yum list cyrus-sasl*" show? Regards, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Flash & Opera on the XO + Firefox
>Since Opera's newer releases still won't see the XO's webcam, I won't be >installing Opera updates until >someone (OLPC people or Adobe) gets the driver situation fixed. I don't think >either organization has much >motivation to fix it, though. Yeah, a shame IMO. The IT world has gone full-circle and if you think about it, users are now actually shifting back to thin clients kinda like dumb terminals back before everyone had a personal computer. A lot of services/applications are shifting to the web and and a lot of traditional desktop apps can now be run from browsers (thin clients) especially now because of leaps in dynamic interactivity because of AJAX and Flash -> Rich Internet Applications (RIAs). Microsoft's windows and office productivity software is now under a big threat because of this and that's why they jumped onto the cloud computing bandwagon ;P Anyway, as such, I'm hoping to contribute more to OLPC as volunteer by attacking the problems we're trying to solve from a cross-platform web-based approach rather than being tied down to hardware/software configurations (which evolve so rapidly that stable locked-down versions are moving targets that are practically impossible to hit because of new stuff breaking old stuff all the time), and the camera is a particularly useful and interesting extension. Since Flash is now the de-facto "installed everywhere" interface for tightly-integrated interactive multimedia (vector graphics, sound, video, etc -> it completely ate Java's originally envisioned browser niche!), I was hoping we could do more work in browser-contained sandbox environments (Webcam -> Flash). Anyway, I think Adobe isn't that unreachable regarding Flash + XO cam. I mean with Adobe's strong support and coordination Flash-wise (Flash Lite) of less-well known devices (that hold similar geek appeal as the XO) like the Chumby (http://www.chumby.com/) and iRiver Clix (http://www.iriver.com/), I think we've got a decent shot at getting a Flash 10 webcam fix for the lean mean green machine ;) > However, Opera didn't play nicely with the icons at the top of the > frame. There were two circles on the frame when I ran Opera, one of which > would not go away when I closed Opera. Oh, I guess I didn't encounter this because after my 2 failed attempts at trying to modify newer versions of Opera to run sugarized, I did complete wipes and clean reinstalls of the XO with me. Is your current Opera installation an "upgrade" with the latest 9.63 desktop version installed over the 9.12 OLPC edition? If so that could be causing it... the un-updated section on upgrading Opera at its wiki page is now wrong: you will no longer be able to launch Opera with the Sugar icon on newer XO Builds (8.2.0/767) because of Rainbow Security. > I couldn't get that icon to go away > without rebooting (it didn't respond with a menu when I dwelled the mouse > pointer on it). I experienced this too when I installed Opera 9.12 OLPC Sugar Activity edition. Didn't happen to me anymore when I fresh-wiped and installed the vanilla Opera standard Fedora desktop rpm version. Off-topic, I'm also experiencing a lot of circle icons that refuse to die until reboot with C Scott's Sugarized Activity version (0.6) of Firefox 3.01. Am going to try out latest Firefox non-Sugarized on the XO and see how it goes. > Since I don't plan to use Opera until Flash plays in it on the > XO, I'll just ignore that icon bug. Oh, Flash plays pretty well enough with Opera, better than with Browse IMHO ;) It's the webcam that's wonky, and I just recently discovered, the flash and stuff now refuses to click buttons properly in the Flash privacy configuration screen (I hadn't played much with my alloted XO since the Flash 10 beta/XO OS 767 beta days because of work and the privacy configuration screen was working pretty okay during Flash 10 beta). > Opera is nice, but I have to use a > microscope to read some of the text menus because it's not set up for the > high-resolution on the XO's small screen. Oh, sorry about that! *insert developer "It's not a bug, it's a feature!" joke* ;) Seriously tho, "tiny resolution" is more a feature for me: because everything's being rendered at native resolution with Opera (everything is so tiny because the XO's real resolution is a mind-blowing 1200x900), everything is so much faster compared to the Browse Activity and Sugarized Firefox 3.01 where pages are zoomed in to make them more readable. (I could be wrong about Firefox -- is it displaying just larger fonts, Scott, or is everything zoomed in?) Scaling up/zooming in graphical stuff taxes the processor so much more because it's actually resampling and upscaling content and has to work even harder because it's now rasterizing more pixels. *** Anyway, you can change the default Opera zoom to remedy the microscopicity problem: (We really should update the Opera wiki ;P) "Setting the default zoom/scaling of new windows http://www.opera.com/support/kb/vie
Re: Problems with Adobe Flash player on the XO.
> Could you be more specific about what writes are failing? > Hi Michael! Basically the problem is this one from the Opera Wiki page: "There is at present an incompatibility between the Opera activity and the OLPC Rainbow security system on some builds. If when you launch the Opera activity, the screen goes blank and stays blank, you have likely encountered that incompatibility." > In the past, we've been able to achieve both isolation and a working > activity (e.g. Scratch) with some easy filesystem tricks... > > Also, have you filed a bug? I've tried searching dev.laptop.org for > "opera rainbow" but I didn't find any likely tickets... My memory's kinda fuzzy, but I think I went straight to the guys at Sugar Labs then asked over there (web form?)... basically the answer I got was that we really can't do much about it because the standard linux desktop version of the latest Opera rpms installs its files to /etc/ and other system directories, and the new Rainbow Security system requires that Activities only install and run from /home/ (olpc/ ?) or something like that, and the only way to fix it was to modify Opera to install/run only from Rainbow-permitted directories and that's not possible outside of Opera's organization because Opera is closed-source. -Naz -- Carlos Nazareno http://www.object404.com -- interactive media specialist zen graffiti studios http://www.zengraffiti.com -- Philippine Flash ActionScripters http://www.phlashers.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please help test our pre-release build of 8.2.1
On 02.01.2009, at 17:09, Brian Pepple wrote: > Hi All, > > A pre-release build of 8.2.1 is now available for testing. It has > passed > an initial smoke test and now needs broader testing. > > The build download and problem reporting instructions are here: > http://wiki.laptop.org/go/Friends_in_testing#Current_status > > The very early draft release notes are here: > http://wiki.laptop.org/go/Release_Notes/8.2.1 > > Please send a note to the list if you try this build even if you don't > find anything interesting. We want to measure our test capacity. You should mention that you want people to test the latest "staging" build, not the latest "8.2.1" build (which is exactly the same as 8.2.0 at this point): http://dev.laptop.org/~bert/8.2.1-staging.html This is a significant change from previous release procedures (e.g., I was not even aware that "staging" builds were meant for testing). - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problems with Adobe Flash player on the XO.
On Fri, Jan 02, 2009 at 10:56:59PM +0800, Carlos Nazareno wrote: >Ditto. I've tried Sugarizing newer versions of Opera myself, but we're >out of luck because of the Rainbow Security implemented in newer XO OS >builds don't allow writing of files by Activities to certain >directories that Opera installs to. The Opera dudes will have to >create a special OLPC Opera Activity for us like with 9.12 since Opera >is not open sourced and we won't be able to do the proper >modifications for Rainbow Security compatibility ourselves. Could you be more specific about what writes are failing? In the past, we've been able to achieve both isolation and a working activity (e.g. Scratch) with some easy filesystem tricks... Also, have you filed a bug? I've tried searching dev.laptop.org for "opera rainbow" but I didn't find any likely tickets... Thanks, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Flash wiki entries
>> Just in time for New Year's resolutions: edit the wiki page first. :-) On Thu, Jan 1, 2009 at 1:52 AM, Carlos Nazareno wrote: > Hey Skier! Your wish is my command :) > > Just did a massive update to the Adobe Flash page, hope to update the > main Flash Player and Gnash pages as well soon, pending spare time off > work. Thank you. > Anyway, for the benefit of the folks who prefer to use Gnash to Adobe > Flash, it would be really great if we could outline that sound howto > on the Gnash wiki entry :) +1 -- and specifically on how to file new bugs or videos/sites that are not working (should they be olpc-trac bugs? gnash-dev emails? gnash bugs?) >> Anyway, why does this wiki page tell you to enter >> sudo su - Some future zen compilation of sudo may support infinite nesting of levels of protectedness, so that you have to really REALLY mean it to say sudo sudo sudo 'make me a sandwich' SJ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Please help test our pre-release build of 8.2.1
Hi All, A pre-release build of 8.2.1 is now available for testing. It has passed an initial smoke test and now needs broader testing. The build download and problem reporting instructions are here: http://wiki.laptop.org/go/Friends_in_testing#Current_status The very early draft release notes are here: http://wiki.laptop.org/go/Release_Notes/8.2.1 Please send a note to the list if you try this build even if you don't find anything interesting. We want to measure our test capacity. Thanks, /B -- Brian Pepple https://fedoraproject.org/wiki/User:Bpepple gpg --keyserver pgp.mit.edu --recv-keys 810CC15E BD5E 6F9E 8688 E668 8F5B CBDE 326A E936 810C C15E signature.asc Description: This is a digitally signed message part ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: UDP broadcast from an XO
On Fri, 2 Jan 2009, shivaprasad javali wrote: > Hi, > Is there any way I can ask the OLPC to broadcast the UDP packets. I am > broadcasting the UDP packets by writing to the UDP port and setting the > destination address to 255.255.255.255 . I am using ports 61556 and 61557 > for communication. So if the antenna of the OLPC ( and hence its wireless > connectivity) is functional wont it broadcast the UDP packets it receives > for broadcast? the normal address to use for broadcasts is nto 255.255.255.255, but the broadcast address of the particular network you are on. for example: if you are on 192.168.1.0 with a netmask of 255.255.255.0 the broadcast address would be 192.168.1.255 David Lang > Thanks > jbsp72 > > On Fri, Jan 2, 2009 at 1:30 PM, wrote: > >> On Fri, 2 Jan 2009, qu...@laptop.org wrote: >> >> Visibility in Neighbourhood View is determined by access from the XO to >>> the Jabber server. The Jabber server does not relay these UDP packets >>> for you. Therefore visibility is not an indicator of ability to operate >>> over UDP. >>> >>> A wireless router will relay the UDP packets. The relay is being done >>> by the router itself, and so any XO not associated with the router may >>> not receive the UDP packets unless the packets are forwarded by the >>> router to whatever router the other XO is associated with. >>> >>> Can you show me one of these UDP packets? >>> >> >> remember that broadcast packets don't generally go through routers (they go >> through bridges, but not routers) >> >> so if the two XO's are on different subnets, broadcasts won't be seen by >> the other one. >> >> David Lang >> > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Problems with Adobe Flash player on the XO.
Hi Stan! > I'm having problems: Adobe FlashPlayer doesn't detect the XO's built-in > webcam so it can't transmit video out to the Internet on Flash-enabled > web sites, I've documented this problem as well at http://wiki.laptop.org/go/Adobe_Flash -> The XO's webcam is not interfacing properly with Adobe Flash 9 & 10. Adobe's done a lot of work towards getting cameras in various Linux distros working with webcam enabled-Flash apps, and they finally got V4L2 running last year, but apparently the XO is using some kind of not-as-common chipset/software combo (in 8.2.0 I think the OS is using a weird mishmash of old & new software/drivers because of problems with the cam in the webcam activity on newer drivers?). I got in touch with some Adobe guys last year before Flash Player 10 final launched about Flash's webcam interfacing problems on the XO, filed the bug report, followed their instructions and submitted the hardware info gathered from the data-gathering tool at Penguin.swf's (Adobe's official Linux Flash dude) blog: http://blogs.adobe.com/penguin.swf/2008/07/paparazzi_v2_1.html Anyway, I haven't heard a word from the Adobe folks yet as I guess that was a very busy time for them with Flash 10 final release going out the door at the time, the report probly got lost in all the hubbub. Anyway, I'll try following up with them as I'd like to play with writing some Flash webcam toys that would work on the XO myself. >I can't get Flash to activate the > XO's camera... ...This was while running on the XO's Browse activity. The camera works with the Browse Activity, just not properly (the camera turns on and it displays red & green static that reacts to objects waved in front of the camera) > I thought > that maybe Opera for the XO would do better. No luck. Yup, Same as with the Browse Activity. XO's weird camera chipset/software combo interface still hasn't been fixed with the linux Adobe Flash 10 plugin. > Opera as installed from the wiki.laptop.org/opera instructions does not even > play > the Flash on the Adobe web site nor any other Flash embedded in a web page. > All that Opera shows is a > gray rectangle where the Flash should be, no text saying to click to > play the Flash. As documented in the Adobe Flash wiki: http://wiki.laptop.org/go/Adobe_Flash and Adobe Flash The official Opera Activity is based on Opera 9.12 and it isn't compatible with Flash 10. The newest Adobe Flash plugin compatible with it is an older version of Flash Player 9. Newer non-Sugarized Linux desktop versions of Opera like 9.63 latest work fine and dandy with latest Flash Player 10 final. Again, you're going to have to use the Terminal (type "opera" at the prompt) to launch Opera. > I submitted a comment to the Opera programmer who maintains the Opera > blog about the OLPC version, but that blog has had very little activity > in the past year so I'm not hopeful of any results from the Opera > people. Ditto. I've tried Sugarizing newer versions of Opera myself, but we're out of luck because of the Rainbow Security implemented in newer XO OS builds don't allow writing of files by Activities to certain directories that Opera installs to. The Opera dudes will have to create a special OLPC Opera Activity for us like with 9.12 since Opera is not open sourced and we won't be able to do the proper modifications for Rainbow Security compatibility ourselves. > Has anyone here tried to run a recent release of Opera on the > XO, not the very old version that was customized for the XO according to > our wiki? Runs fine and dandy, you just have to launch it via terminal :) -> Launch Terminal Activity, type "opera" at the prompt (assuming of course that you'd already installed Opera). That instance of terminal will then be inaccessible until you exit Opera. Once you exit Opera, you regain control of the terminal prompt. (Yeah Skier, the Opera wiki entries are next on my hit list for editing: they're due for massive updates :P) > Even without the 2-way video streaming, www.vyew.com is a nice > application for collaboration over the Internet. Try it. Thanks for the link Stan! I was looking to build a Flash app just like that, only less ambitious (crud, someone beat me to the punch! ;P) Cheers! -Naz -- Carlos Nazareno http://www.object404.com -- interactive media specialist zen graffiti studios http://www.zengraffiti.com -- Philippine Flash ActionScripters http://www.phlashers.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: UDP broadcast from an XO
Hi, Is there any way I can ask the OLPC to broadcast the UDP packets. I am broadcasting the UDP packets by writing to the UDP port and setting the destination address to 255.255.255.255 . I am using ports 61556 and 61557 for communication. So if the antenna of the OLPC ( and hence its wireless connectivity) is functional wont it broadcast the UDP packets it receives for broadcast? Thanks jbsp72 On Fri, Jan 2, 2009 at 1:30 PM, wrote: > On Fri, 2 Jan 2009, qu...@laptop.org wrote: > > Visibility in Neighbourhood View is determined by access from the XO to >> the Jabber server. The Jabber server does not relay these UDP packets >> for you. Therefore visibility is not an indicator of ability to operate >> over UDP. >> >> A wireless router will relay the UDP packets. The relay is being done >> by the router itself, and so any XO not associated with the router may >> not receive the UDP packets unless the packets are forwarded by the >> router to whatever router the other XO is associated with. >> >> Can you show me one of these UDP packets? >> > > remember that broadcast packets don't generally go through routers (they go > through bridges, but not routers) > > so if the two XO's are on different subnets, broadcasts won't be seen by > the other one. > > David Lang > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
How do I clear an OFW flag?
Trying to test the fix for #8976 , I am stumped at what I thought would be a trivial step - clearing the AK flag. My laptop has ak and dk flags set, and I have both leases handy in case something goes wrong. The NAND has a good signed image. The only hint I was able to find was in a script in http://wiki.laptop.org/go/OLPC_Ethiopia/XO_reflash_process - but I'm not sure how to safely/sanely remove the flag without bricking this nice XO. So far the plan seems to be... unfreeze ??? profit! any hints? 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
