RE: [Dextrose] Support for Firefox 3.5 is ending
-Original Message- From: dextrose-boun...@lists.sugarlabs.org [mailto:dextrose- boun...@lists.sugarlabs.org] On Behalf Of Bernie Innocenti Sent: Sunday, June 05, 2011 2:34 AM To: Sridhar Dhanapalan Cc: OLPC Devel; OLPC Australia list; Dextrose Subject: Re: [Dextrose] Support for Firefox 3.5 is ending On Sun, 2011-06-05 at 15:50 +1000, Sridhar Dhanapalan wrote: (sorry - sending again because I had the wrong address for the olpc devel list) Firefox 3.5 is being EOLed by Mozilla[0] and Google is dropping support for it[1]. In 10.1.3 this is default Web browser in GNOME and the backend of the Browse activity, so we should be thinking of what that means for us. The plan for Australia is to have a Fedora 14 build (based on DX12) ready by January. F14 comes with Firefox 3.6, which is the oldest version supported by Mozilla and Google. What would be even better is to have Firefox 4 available. By January, Firefox 3.6 will be quite old and close to EOL. Firefox 4 is a fair bit faster than 3.6, allowing us to squeeze extra performance out of our XOs. There is a yum repository for F14[2]. I use this on my F14 work machine (albeit in x86_64), and I've had no problem. Browse continues to work in Sugar. Are there any thoughts/plans about including Firefox 4 in the OLPC/DX OS? There was some discussion at EduJam. Browse is currently unmaintained, but Simon Schampijer and Gonzalo Odiard expressed interest in working on it. There was the question of missing support for the Python bindings of GtkMozEmbed, but the problem appears to be solved now. What is the solution? david In the longer term, there's also the option of switching to Surf, an alternative browser based on WebKit which promises to be faster and less memory hungry than Browse. This depends on Lucian Branescu (or someone else) resuming the work on it. Migrating to Surf wasn't feasible with Fedora 11 because too many of WebKitGtk's dependencies were missing. -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Dextrose mailing list dextr...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/dextrose ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Support for Firefox 3.5 is ending
On 5 June 2011 17:02, Bernie Innocenti ber...@sugarlabs.org wrote: Fedora 14 is still shipping xulrunner 1.9.2, which is roughly equivalent to the version used by Firefox 3.6. Backporting things from Fedora 15 is going to be a royal pain in the ass, since they have switched everything to Gnome 3. Does that mean that with FF4 installed, Browse is still working because it is (equivalently) using FF3.6 as the backend? Would that mean that if we were to upgrade to FF4, we would have a disparity in rendering between GNOME and Sugar? Thanks, Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: [Dextrose] Support for Firefox 3.5 is ending
-Original Message- From: Sridhar Dhanapalan [mailto:srid...@laptop.org.au] Sent: Sunday, June 05, 2011 3:42 AM To: Bernie Innocenti Cc: David Farning; OLPC Devel; OLPC Australia list; Dextrose Subject: Re: [Dextrose] Support for Firefox 3.5 is ending On 5 June 2011 17:02, Bernie Innocenti ber...@sugarlabs.org wrote: Fedora 14 is still shipping xulrunner 1.9.2, which is roughly equivalent to the version used by Firefox 3.6. Backporting things from Fedora 15 is going to be a royal pain in the ass, since they have switched everything to Gnome 3. Does that mean that with FF4 installed, Browse is still working because it is (equivalently) using FF3.6 as the backend? FF3.6 and xulrunner 1.9.2 are based on the same code base FF4 and xulrunner 2.0 are based on the same code base When you install FF4 on Fedora14 there will be two versions of xulrunner installed. Would that mean that if we were to upgrade to FF4, we would have a disparity in rendering between GNOME and Sugar? The issues becomes one of cost benefit. What is the cost of OLPC, AC, or individual deployments supporting a version of xulrunner which is not supported or QAed by fedora vs. the benefit of having ff4 in the os. My guess is that the cost will exceed the benefit. So AC will not back port, QA, or support ff4 on DX12 unless someone else takes the lead. But the beauty of a community project is that if anyone else thinks that benefit is greater than the cost they are welcome and encouraged to 'make it happen.' From AC's point of view. The biggest request is for stability and predictable over features and performance. david ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Support for Firefox 3.5 is ending
On 5 June 2011 12:07, David Farning dfarn...@activitycentral.com wrote: Would that mean that if we were to upgrade to FF4, we would have a disparity in rendering between GNOME and Sugar? The issues becomes one of cost benefit. What is the cost of OLPC, AC, or individual deployments supporting a version of xulrunner which is not supported or QAed by fedora vs. the benefit of having ff4 in the os. My guess is that the cost will exceed the benefit. So AC will not back port, QA, or support ff4 on DX12 unless someone else takes the lead. But the beauty of a community project is that if anyone else thinks that benefit is greater than the cost they are welcome and encouraged to 'make it happen.' From AC's point of view. The biggest request is for stability and predictable over features and performance. I've been doing more thinking about it, and I came to the same conclusion. We've got enough to chew on in our development, so let's stick with what the Fedora Project have already tested and released. We need that stable base to build on. Sridhar ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] Support for Firefox 3.5 is ending
On Sun, Jun 5, 2011 at 6:47 AM, Sridhar Dhanapalan srid...@laptop.org.au wrote: Firefox 3.5 is being EOLed by Mozilla[0] and Google is dropping support for it[1]. In 10.1.3 this is default Web browser in GNOME and the backend of the Browse activity, so we should be thinking of what that means for us. The plan for Australia is to have a Fedora 14 build (based on DX12) ready by January. F14 comes with Firefox 3.6, which is the oldest version supported by Mozilla and Google. What would be even better is to have Firefox 4 available. By January, Firefox 3.6 will be quite old and close to EOL. Firefox 4 is a fair bit faster than 3.6, allowing us to squeeze extra performance out of our XOs. There is a yum repository for F14[2]. My understanding (I can't find where I read it) is that Firefox 3.6 will stick around for a while to support older OS releases. Do you have information that's different? I use this on my F14 work machine (albeit in x86_64), and I've had no problem. Browse continues to work in Sugar. Yes. But in this case Browse is still using the old version of XULRunner, Browse doesn't work with Xulrunner 2. Are there any thoughts/plans about including Firefox 4 in the OLPC/DX OS? There are a lot of other impacts that would need to be addressed and its no a small amount of work. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] [Dextrose] Support for Firefox 3.5 is ending
On Sun, Jun 5, 2011 at 8:02 AM, Bernie Innocenti ber...@sugarlabs.org wrote: (hey, is the clock of your computer set correctly? your message appears to be one day old!) On Sat, 2011-06-04 at 20:37 -0400, David Farning wrote: There was some discussion at EduJam. Browse is currently unmaintained, but Simon Schampijer and Gonzalo Odiard expressed interest in working on it. There was the question of missing support for the Python bindings of GtkMozEmbed, but the problem appears to be solved now. What is the solution? Ubuntu Natty ships a new version of python-gtkmozembed, which is based on xulrunner 2.0. Fedora 15 also has xulrunner 2.0, with Python bindings. Fedora 14 is still shipping xulrunner 1.9.2, which is roughly equivalent to the version used by Firefox 3.6. Backporting things from Fedora 15 is going to be a royal pain in the ass, since they have switched everything to Gnome 3. Its not roughly equivalent it is the version being used by FF 3.6. In terms of Firefox 4 in Fedora 14 your correct that it will be a pain, but not really due to gnome 3. FF4 still uses gtk2. The problem is all the gnome deps that use xulrunner that would need porting as well. I personally believe that it would be less work to move Fedora 15! Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] [Dextrose] Support for Firefox 3.5 is ending
On Sun, Jun 5, 2011 at 9:07 AM, Bernie Innocenti ber...@sugarlabs.org wrote: On Sun, 2011-06-05 at 17:42 +1000, Sridhar Dhanapalan wrote: On 5 June 2011 17:02, Bernie Innocenti ber...@sugarlabs.org wrote: Fedora 14 is still shipping xulrunner 1.9.2, which is roughly equivalent to the version used by Firefox 3.6. Backporting things from Fedora 15 is going to be a royal pain in the ass, since they have switched everything to Gnome 3. Does that mean that with FF4 installed, Browse is still working because it is (equivalently) using FF3.6 as the backend? Would that mean that if we were to upgrade to FF4, we would have a disparity in rendering between GNOME and Sugar? Yes. Since version 3.5 (iirc), Firefox comes with its own forked version of xulrunner. The system-wide copy of xulrunner is distinct from the one bundled with the Firefox package. Same for nspr (the Netscape portable runtime) and nss (the netscape SSL implementation). And if you happen to use Thunderbird, you've even got a third copy of all these libraries in your system. No, xulrunner wasn't forked and the firefox package in Fedora uses the system xulrunner. In the case of the repo with FF4 there's a xulrunner2 package and all the libraries and names of the package when built have been changed. To use it you have to change the way the xulrunner app links to which version/name of the underlying xulrunner. Following the best traditions of Windows applications, Firefox and Thunderbird will store passwords, proxy settings and file associations in two different locations. No idea about windows nor thunderbird but firefox 3.x and 4 will both use the same profile (I was switching between the two for a while when FF4 had issues even restoring the sessions) and use system proxies. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] [Dextrose] Support for Firefox 3.5 is ending
On Sun, Jun 5, 2011 at 7:33 AM, Bernie Innocenti ber...@sugarlabs.org wrote: On Sun, 2011-06-05 at 15:50 +1000, Sridhar Dhanapalan wrote: (sorry - sending again because I had the wrong address for the olpc devel list) Firefox 3.5 is being EOLed by Mozilla[0] and Google is dropping support for it[1]. In 10.1.3 this is default Web browser in GNOME and the backend of the Browse activity, so we should be thinking of what that means for us. The plan for Australia is to have a Fedora 14 build (based on DX12) ready by January. F14 comes with Firefox 3.6, which is the oldest version supported by Mozilla and Google. What would be even better is to have Firefox 4 available. By January, Firefox 3.6 will be quite old and close to EOL. Firefox 4 is a fair bit faster than 3.6, allowing us to squeeze extra performance out of our XOs. There is a yum repository for F14[2]. I use this on my F14 work machine (albeit in x86_64), and I've had no problem. Browse continues to work in Sugar. Are there any thoughts/plans about including Firefox 4 in the OLPC/DX OS? There was some discussion at EduJam. Browse is currently unmaintained, but Simon Schampijer and Gonzalo Odiard expressed interest in working on it. There was the question of missing support for the Python bindings of GtkMozEmbed, but the problem appears to be solved now. From looking at the Browse problem for Fedora 15 / SoaS 5 it seems that hulahop needs to be ported to the latest xulrunner 2/xulrunner-python and we should be mostly good to go. I have no idea how much work this would be though. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [OLPC-AU] [Dextrose] Support for Firefox 3.5 is ending
Does that mean that with FF4 installed, Browse is still working because it is (equivalently) using FF3.6 as the backend? Would that mean that if we were to upgrade to FF4, we would have a disparity in rendering between GNOME and Sugar? A note from a sometimes_bleeding_edge user: Ever since FF4 beta was available, I've been running it on all my XOs. It has its own subset of xulrunner functions - so does not conflict with whatever xulrunner package version has been installed in the XO. Browse has not been affected by my upleveling of FF. mikus p.s. Activities such as Karma appear to have packaged-in an entire copy of the then-current xulrunner function. pps. With FF 5 beta now available - that's what I am currently running in all my F11/F14 XOs. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Support for Firefox 3.5 is ending
On Sun, 2011-06-05 at 15:50 +1000, Sridhar Dhanapalan wrote: (sorry - sending again because I had the wrong address for the olpc devel list) Firefox 3.5 is being EOLed by Mozilla[0] and Google is dropping support for it[1]. In 10.1.3 this is default Web browser in GNOME and the backend of the Browse activity, so we should be thinking of what that means for us. The plan for Australia is to have a Fedora 14 build (based on DX12) ready by January. F14 comes with Firefox 3.6, which is the oldest version supported by Mozilla and Google. What would be even better is to have Firefox 4 available. By January, Firefox 3.6 will be quite old and close to EOL. Firefox 4 is a fair bit faster than 3.6, allowing us to squeeze extra performance out of our XOs. There is a yum repository for F14[2]. I use this on my F14 work machine (albeit in x86_64), and I've had no problem. Browse continues to work in Sugar. Are there any thoughts/plans about including Firefox 4 in the OLPC/DX OS? There was some discussion at EduJam. Browse is currently unmaintained, but Simon Schampijer and Gonzalo Odiard expressed interest in working on it. There was the question of missing support for the Python bindings of GtkMozEmbed, but the problem appears to be solved now. In the longer term, there's also the option of switching to Surf, an alternative browser based on WebKit which promises to be faster and less memory hungry than Browse. This depends on Lucian Branescu (or someone else) resuming the work on it. Migrating to Surf wasn't feasible with Fedora 11 because too many of WebKitGtk's dependencies were missing. -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: [Dextrose] Support for Firefox 3.5 is ending
(hey, is the clock of your computer set correctly? your message appears to be one day old!) On Sat, 2011-06-04 at 20:37 -0400, David Farning wrote: There was some discussion at EduJam. Browse is currently unmaintained, but Simon Schampijer and Gonzalo Odiard expressed interest in working on it. There was the question of missing support for the Python bindings of GtkMozEmbed, but the problem appears to be solved now. What is the solution? Ubuntu Natty ships a new version of python-gtkmozembed, which is based on xulrunner 2.0. Fedora 15 also has xulrunner 2.0, with Python bindings. Fedora 14 is still shipping xulrunner 1.9.2, which is roughly equivalent to the version used by Firefox 3.6. Backporting things from Fedora 15 is going to be a royal pain in the ass, since they have switched everything to Gnome 3. -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Dextrose] Support for Firefox 3.5 is ending
On Sun, 2011-06-05 at 17:42 +1000, Sridhar Dhanapalan wrote: On 5 June 2011 17:02, Bernie Innocenti ber...@sugarlabs.org wrote: Fedora 14 is still shipping xulrunner 1.9.2, which is roughly equivalent to the version used by Firefox 3.6. Backporting things from Fedora 15 is going to be a royal pain in the ass, since they have switched everything to Gnome 3. Does that mean that with FF4 installed, Browse is still working because it is (equivalently) using FF3.6 as the backend? Would that mean that if we were to upgrade to FF4, we would have a disparity in rendering between GNOME and Sugar? Yes. Since version 3.5 (iirc), Firefox comes with its own forked version of xulrunner. The system-wide copy of xulrunner is distinct from the one bundled with the Firefox package. Same for nspr (the Netscape portable runtime) and nss (the netscape SSL implementation). And if you happen to use Thunderbird, you've even got a third copy of all these libraries in your system. Following the best traditions of Windows applications, Firefox and Thunderbird will store passwords, proxy settings and file associations in two different locations. Seeing this, the Chromium developers promptly reacted by bundling a dozen of large system libraries into their codebase, including ffmpeg, libicu, openssl and sqlite. Some of these have been diligently forked to ensure that packagers wouldn't accidentally try to use the system copies! -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
document on SLAK13.37 OLPC was done
I just put it at: http://e-university.eu.org/OLPC/YOUR_USB_SLAK_OLPC_HOWTO.txt By this method, any Slackware users can made USB OLPC on their own choice. Regards, supat On Thu, 2 Jun 2011, su...@supat.eu.org wrote: I just put it at: http://e-university.eu.org/OLPC/minimalUSB_OLPC_SLAK.howto.txt This will used with file: http://e-university.eu.org/OLPC/minimalUSB_OLPC_SLAK.tar.bz2 check sum was in: http://e-university.eu.org/OLPC/md5sum.txt If I have time I will write 2 more HOWTOs. Regards, supat On Wed, 1 Jun 2011, James Cameron wrote: On Wed, Jun 01, 2011 at 09:06:54AM +0700, su...@supat.eu.org wrote: I just try to add my info at: http://wiki.laptop.org/go/Developers_manual#Quickstart I am not familiar with how to write it. I have to spend time on it. Firstly, in fast I will add how to on my own web. If you think it was good I will import to http://wiki.laptop.org/ Ok. Your work on Slackware, it is not very relevant to topic of Developers_manual. Instead, use page http://wiki.laptop.org/go/Slackware ... just edited by me. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Regarding my OLPC XS Wishlist
Hi, I hope we can keep Abhisek in the loop as he has detailed information on the XS version deployed in Nepal. The procedure there is to build XS and release it as an img. The image is loaded to a usb drive (mkusbinstall.sh). This key is used to install all of the deployed school servers. I have attached the instructions for installing NEXS from the olenepal redmine (slightly edited). I am very internet-challenged (at this campground I arrived on Thursday and used the internet for about two hours and then it died - now on Sunday evening it is working intermittently!), so I think some of my previous comments have not been received. So please be patient if you have read this before: I think the separation of the server into two components XS and XC is very valuable. The XC build should provide a working schoolserver which can be accessed via the LAN from an XO using ssh. With the XS-Au fix for the 'race' condition in kickstart, it should be possible to do this install 'headless' on a server which supports booting from the usb drive when present (and bootable). XC provides the content for the /library partition. However, with Daniel Drake's usbmount scripts XC could be used to install any optional packages such as Dan's Guardian, Moodle (forgive me, Martin), Fedora Commons, Fez, mediawiki, and so on. The netsetup.sh script should be used to configure the WAN network and should not be needed when the school server is not connected to an external network (the LAN network is configured the same in every school as 172.18.0.1). The LAN should be configured for the baseboard (RJ45) port and the WAN for a secondary port (e.g. usb-ethernet). Essentially this is the procedure used in Nepal with considerable success over the past two years (success measured by the schoolserver very rarely being a problem requiring service (UPS failures seem far more frequent). Tony P.S. http://wiki.laptop.org/go/OLE_Nepal:Procedure_to_build_NEXS_from_OLPC_XS gives a description of the build procedure used for XS-0.4. It provides details on the installation of the extra packages as of that time. Abhishek Singh can provide more recent details. On 06/03/2011 04:21 PM, Sridhar Dhanapalan wrote: On 4 June 2011 00:00, Aleksey Limalsr...@activitycentral.org wrote: On Fri, Jun 03, 2011 at 09:40:48AM -0400, Martin Langhoff wrote: On Fri, Jun 3, 2011 at 7:49 AM, Sridhar Dhanapalan srid...@laptop.org.au wrote: On 3 June 2011 21:31, Aleksey Limalsr...@activitycentral.org wrote: btw, did someone try to use cloning paradigm for setting up new school servers instead of using regular install way? Just clonning the system will lest avoid many issues by design. Do you mean creating an image of a server installation and applying it to other machines? We've done that with the XS-AU (using clonezilla), and I'm pretty sure it works with an OLPC XS. Note that without a script that cleans up config state, you're bound to have some fun problems with the resulting systems. Do you mean particular script, which one? You'll need to clean up: /etc/udev/rules.d/70-persistent-net.rules (delete the lines that refer to all the eth devices) /etc/sysconfig/network-scripts/ifcfg-eth* (remove the HWADDR line) ssh keys (/etc/ssh/ssh_host_*) postgresql server.crt Info: http://dev.laptop.org.au/issues/422 Sridhar NEXS installation¶ From USB¶ 1. Take a USB disk, create a single partition with type 0x83 (Linux) (e.g. using fdisk) and format it as VFAT (e.g. using mkfs.vfat) * This conflict of partition type vs filesystem is intentional; the Anaconda installer seems a bit sensitive to other configurations and may get confused at the bootloader install stage if you don't use this configuration 2. Download the NEXS .iso corresponding to the NEXS version that you want to install to your hard disk 3. Download http://hg.olenepal.org/NEXS-image-builder/raw-file/tip/mkusbinstall to your hard disk 4. Run: # sudo bash ./mkusbinstall /path/to/nexs.iso /dev/sdb1 * where /dev/sdb1 is the partition of your USB disk 5. Plug the USB disk into the Wind computer 6. Turn on and press F11 until menu appears 7. Choose USB device from the boot device menu 8. Choose the default Install with kickstart option from the boot menu 9. After a few seconds, you will see an error that says that the kickstart file cannot be found. Wait 5 seconds, then press enter twice to retry. * This is an Anaconda bug where it tries to access the USB disk before it is ready 10. You may see another error message saying that the installation media cannot be found. If so, try selecting /dev/sdc1 as the installation device (the default is sdb1) * This is because on some Wind systems, the onboard SD card reader takes the sdb position Once installation completes, the system will reboot. Remove the USB disk at this time, and continue with the
Re: [Server-devel] Regarding my OLPC XS Wishlist
On 06/05/2011 09:42 PM, Tony Anderson wrote: Hi, I hope we can keep Abhisek in the loop as he has detailed information on the XS version deployed in Nepal. The procedure there is to build XS and release it as an img. The image is loaded to a usb drive (mkusbinstall.sh). This key is used to install all of the deployed school servers. I have attached the instructions for installing NEXS from the olenepal redmine (slightly edited). I am very internet-challenged (at this campground I arrived on Thursday and used the internet for about two hours and then it died - now on Sunday evening it is working intermittently!), so I think some of my previous comments have not been received. So please be patient if you have read this before: I think the separation of the server into two components XS and XC is very valuable. The XC build should provide a working schoolserver which can be accessed via the LAN from an XO using ssh. With the XS-Au fix for the 'race' condition in kickstart, it should be possible to do this install 'headless' on a server which supports booting from the usb drive when present (and bootable). XC provides the content for the /library partition. However, with Daniel Drake's usbmount scripts XC could be used to install any optional packages such as Dan's Guardian, Moodle (forgive me, Martin), Fedora Commons, Fez, mediawiki, and so on. The netsetup.sh script should be used to configure the WAN network and should not be needed when the school server is not connected to an external network (the LAN network is configured the same in every school as 172.18.0.1). The LAN should be configured for the baseboard (RJ45) port and the WAN for a secondary port (e.g. usb-ethernet). Essentially this is the procedure used in Nepal with considerable success over the past two years (success measured by the schoolserver very rarely being a problem requiring service (UPS failures seem far more frequent). Tony P.S. http://wiki.laptop.org/go/OLE_Nepal:Procedure_to_build_NEXS_from_OLPC_XS gives a description of the build procedure used for XS-0.4. It provides details on the installation of the extra packages as of that time. Abhishek Singh can provide more recent details. On 06/03/2011 04:21 PM, Sridhar Dhanapalan wrote: On 4 June 2011 00:00, Aleksey Limalsr...@activitycentral.org wrote: On Fri, Jun 03, 2011 at 09:40:48AM -0400, Martin Langhoff wrote: On Fri, Jun 3, 2011 at 7:49 AM, Sridhar Dhanapalan srid...@laptop.org.au wrote: On 3 June 2011 21:31, Aleksey Limalsr...@activitycentral.org wrote: btw, did someone try to use cloning paradigm for setting up new school servers instead of using regular install way? Just clonning the system will lest avoid many issues by design. Do you mean creating an image of a server installation and applying it to other machines? We've done that with the XS-AU (using clonezilla), and I'm pretty sure it works with an OLPC XS. Note that without a script that cleans up config state, you're bound to have some fun problems with the resulting systems. Do you mean particular script, which one? You'll need to clean up: /etc/udev/rules.d/70-persistent-net.rules (delete the lines that refer to all the eth devices) /etc/sysconfig/network-scripts/ifcfg-eth* (remove the HWADDR line) ssh keys (/etc/ssh/ssh_host_*) postgresql server.crt Info: http://dev.laptop.org.au/issues/422 Sridhar Hi Tony, and all, Greetings from Nepal. I would like to correct a few things in Tony's descriptions and elaborate upon what he discussed. NEXS (the Nepalese version built upon OLPC XS) has separated the content part from the base server. We call the content part NEXC (C for content). This separation has helped us a lot in managing content bundles and content updates. The NEXC generally contains: 1. Content of the digital library (see http://www.pustakalaya.org), which is spanned across: * Database dumps for Fedora Commons and Fez * Fedora Commons datastream files * Fez's customized interface (that is being used at pustakalaya.org) 2. Wiki for schools 3. English Wiktionary 4. Nepali Dictionary 5. External Content: All the other static content (e.g. video files, maps etc) are packaged as external content 6. Learn English Kids from British Council (recently added) We have a 3-month NEXC release schedule. At every release, we'll bundle the most recent content and put it on a USB HDD, test it internally on our test school server, and then finally release it. After every release, the deployment team will go to the schools with the USB HDDs and plug it to the school server at the site schools. Daniel Drake's usbmount script takes care of installing/updating the content from the USB HDDs - you just nee to listen to the starting and the ending beep during which all the content update is done. We have tried updating it over Internet, but the
