Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
On Mon, Jun 8, 2009 at 13:03, James Zakijames.z...@gmail.com wrote: With regards to the speed issue. I tried SoaS on a USB2.0 (but not high-speed) memory-stick, performance was hideous on a macbook. Using a USB2.0 high-speed memory-stick, performance is great on an eeepc, which has 1G Ram. I know its not small, but its all I have to compare with for now. So from what I have experienced the USB port would be the first target. I'll hopefully get a chance to test on low-RAM school computers tomorrow. We should see why disk I/O is affecting so much performance. Instead of making the disk faster we should make Sugar stop doing stupid things (if that's indeed the case). Anybody with performance profiling of linux system can give some hints about which tools we can use to see why disk I/O seems to be the bottleneck? Thanks, Tomeu James. 2009/6/8 Jonas Smedegaard d...@jones.dk -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Sun, Jun 07, 2009 at 07:00:28PM -0400, Luke Faraone wrote: On Sun, Jun 7, 2009 at 18:43, Jonas Smedegaard d...@jones.dk wrote: It sound like another great, low impact (I am trying to think of a term like 'carbon foot print' to properly reflect the impact) way of bringing LTSP into the class room. polite or gentle perhaps? or non-invasive? Emphasizing what is avoided: invading - potentially taking over, accidentally or on purpose, the computers Granted, you would *need* to check with your local systems administrator before implementing LTSP. (as opposed to a lower-risk USB-local-booting solution) At my school, for example, netbooting a workstation starts the recloning process of loading a new Windows XP image; setting up LTSP without asking would cause major problems with their work. non-invasive to the _computers_ but invasive to the network infrastructure. So yes, a better term would be good, to not risk sysadmins feeling cheated when learning the hard way that this so-called non-invasive system includes a DHCP daemon, breaking their WiFi hotspots, printers and what not. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkosXD0ACgkQn7DbMsAkQLgTYwCeNg687lF4eEXrGw9SqB62AGih 5WQAniL/ZEmBKsZ8zVMCRmPlNnScHmE5 =lu5m -END PGP SIGNATURE- ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
With regards to the speed issue. I tried SoaS on a USB2.0 (but not high-speed) memory-stick, performance was hideous on a macbook. Using a USB2.0 high-speed memory-stick, performance is great on an eeepc, which has 1G Ram. I know its not small, but its all I have to compare with for now. So from what I have experienced the USB port would be the first target. I'll hopefully get a chance to test on low-RAM school computers tomorrow. James. 2009/6/8 Jonas Smedegaard d...@jones.dk -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Sun, Jun 07, 2009 at 07:00:28PM -0400, Luke Faraone wrote: On Sun, Jun 7, 2009 at 18:43, Jonas Smedegaard d...@jones.dk wrote: It sound like another great, low impact (I am trying to think of a term like 'carbon foot print' to properly reflect the impact) way of bringing LTSP into the class room. polite or gentle perhaps? or non-invasive? Emphasizing what is avoided: invading - potentially taking over, accidentally or on purpose, the computers Granted, you would *need* to check with your local systems administrator before implementing LTSP. (as opposed to a lower-risk USB-local-booting solution) At my school, for example, netbooting a workstation starts the recloning process of loading a new Windows XP image; setting up LTSP without asking would cause major problems with their work. non-invasive to the _computers_ but invasive to the network infrastructure. So yes, a better term would be good, to not risk sysadmins feeling cheated when learning the hard way that this so-called non-invasive system includes a DHCP daemon, breaking their WiFi hotspots, printers and what not. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkosXD0ACgkQn7DbMsAkQLgTYwCeNg687lF4eEXrGw9SqB62AGih 5WQAniL/ZEmBKsZ8zVMCRmPlNnScHmE5 =lu5m -END PGP SIGNATURE- ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
On Sun, Jun 7, 2009 at 9:49 AM, Sean DALY sdaly...@gmail.com wrote: Hmmm I'm not sure a BIOS will be wiling to boot from a USB port on a card. However, combined with a CD boot helper might do the trick. I have to use the CD at this point anyway. My goal is to have it boot more quickly and respond more quickly once its booted. Reconditioning older PCs (even just adding RAM or a USB card) is a bit of a thankless job :-( But one that makes many high school and young at heart computer geeks pretty happy on a Saturday, especially if you add pizza and donuts. If a school IT person has to do it, its never financially feasible, but I could see a lot of volunteers actually enjoying the work, and getting a lot of satisfaction about getting faster computers into kids hands and keeping computers out of the land fill. I'm wondering if there's a way for SoaS to automatically report what it has booted on. Computer labs are prime candidates for SoaS and are often populated with a single PC model; it would be great if we could offer good upgrade advice x30. Ah actually Sebastian already wrote that! I forgot to do it when I was in the computer lab. I will remember next time. It would be cool to turn that into an Activity so its super easy. My work trying to get a Work Study student for GPA looks like its going to generate a bunch of volunteers without the correct paperwork to get paid as Work Study students. Let me echo Caryl's question. Do we have a page with tasks for new volunteers? Sean On Sun, Jun 7, 2009 at 3:34 PM, Caroline Meekscarol...@solutiongrove.com wrote: This week, thanks for installing the Broadcom drivers separately, we got Sugar on a Stick up and running on the GPA computers. http://wiki.sugarlabs.org/go/Gardner_Pilot_Academy#Current_computers_at_GPA They are older computer and they run faster then an XO but still not that snappy. A big part of SoaS is using existing computers and donated computers. I wonder what it would take to upgrade older computers, and make them snappier. I don't know if we will get permission to open up these particular computers, (which are owned by Boston Public Schools) but there are certainly tons of older computers like them around. I think there are two things that might make them perform better. 1. Add a USB 2.0 port. They are almost certainly USB 1 right now. I see that if the box has the right slots for it, USB 2.0 cards are less then $10. http://www.newegg.com/Product/Product.aspx?Item=N82E16815123010 2. Add more RAM. Earlier this year I worked with a group that specialized in repairing and recyclying computers. They had lots of RAM they had scavanged. It would be very cool if someone had some old computers and could try Sugar, then do motifications like add a USB 2.0 port and RAM and document the results. Caryl, this is another potential project for someone who wants to help. -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
On Sun, Jun 7, 2009 at 10:07 AM, Caroline Meeks carol...@solutiongrove.comwrote: Let me echo Caryl's question. Do we have a page with tasks for new volunteers? http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO has been restored and is ready to be updated, perhaps restructured to cover this need. --Fred ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
When it come to older pcs, it really makes sense to try and use LTSP. We have created a kiwi-ltsp usb stick for openSUSE, which gives a portable ltsp server wherever u plug it in. In most cases it would make sense for this to be the most powerful computer. It is as easy as installing the sugar and sugar activities meta packages on this usb image and the users on the ltsp network then have access to Sugar from any computer in the network, and they are bound to load faster than from a usb image. The advantage is u need one usb stick per network, as opposed to one for each terminal... that saves costs, and time. Also, u dont need any of the old hardware, such as cdrom drives, hard drives, etc. Networking and internet is also no issue as if it works on the server, it has to work on each of the terminals too... kind Regards, David (nubae) Van Assche On Sun, Jun 7, 2009 at 5:27 PM, Frederick Grose fgr...@gmail.com wrote: On Sun, Jun 7, 2009 at 10:07 AM, Caroline Meeks carol...@solutiongrove.com wrote: Let me echo Caryl's question. Do we have a page with tasks for new volunteers? http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO has been restored and is ready to be updated, perhaps restructured to cover this need. --Fred ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
On Sun, Jun 7, 2009 at 12:24 PM, David Van Asschedvanass...@gmail.com wrote: When it come to older pcs, it really makes sense to try and use LTSP. We have created a kiwi-ltsp usb stick for openSUSE, which gives a portable ltsp server wherever u plug it in. In most cases it would make sense for this to be the most powerful computer. It is as easy as installing the sugar and sugar activities meta packages on this usb image and the users on the ltsp network then have access to Sugar from any computer in the network, and they are bound to load faster than from a usb image. The advantage is u need one usb stick per network, as opposed to one for each terminal... that saves costs, and time. Also, u dont need any of the old hardware, such as cdrom drives, hard drives, etc. Networking and internet is also no issue as if it works on the server, it has to work on each of the terminals too... SoaS is also working on a slightly different issue. I didn't understand it until Caroline explained it for about the 100th time yesterday:) In addition to all the technical hurdles. Sugar on a Stick is tackling the _bureaucratic_ issue of installing and running Sugar (or any software) on systems which one doesn't have admin access. In many schools it can be difficult to get the authority to install software or modify the configuration on their computers. SoaS circumvents that problem by replacing 'install a new OS' with 'insert the stick and turn it on.' The piece that I was _misunderstanding_ was that all of the technically hurdles that SoaS introduces are worth the ability to circumvent the bureaucratic hurdles. FWIW, at least in developed nations Once you get the bureaucratic permission to 'install' Sugar, a client-server configuration is most palatable to the existing generation of elementary school sysadmins. david kind Regards, David (nubae) Van Assche On Sun, Jun 7, 2009 at 5:27 PM, Frederick Grose fgr...@gmail.com wrote: On Sun, Jun 7, 2009 at 10:07 AM, Caroline Meeks carol...@solutiongrove.com wrote: Let me echo Caryl's question. Do we have a page with tasks for new volunteers? http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO has been restored and is ready to be updated, perhaps restructured to cover this need. --Fred ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
That's a good point, and I understand the thinking behind it, as if you are not 'changing' anything in an existing setup, people are less afraid that things might go terribly wrong. That's the reason we have ltsp on a usb stick... because you can stick in a server, and test it without installing anything. Think of it as SoaS server with beaurocratic advantages included (taking care of networking, providing Sugar images, setting up user accounts, providng collaboration if necessary. It is by no means the XS server, nor should it try to be that, its just the desktop environment part with ejabberd, if needed.. of course, it only works in wired environments. kind Regards, David (nubae) Van Assche On Sun, Jun 7, 2009 at 8:19 PM, David Farning dfarn...@sugarlabs.orgwrote: On Sun, Jun 7, 2009 at 12:24 PM, David Van Asschedvanass...@gmail.com wrote: When it come to older pcs, it really makes sense to try and use LTSP. We have created a kiwi-ltsp usb stick for openSUSE, which gives a portable ltsp server wherever u plug it in. In most cases it would make sense for this to be the most powerful computer. It is as easy as installing the sugar and sugar activities meta packages on this usb image and the users on the ltsp network then have access to Sugar from any computer in the network, and they are bound to load faster than from a usb image. The advantage is u need one usb stick per network, as opposed to one for each terminal... that saves costs, and time. Also, u dont need any of the old hardware, such as cdrom drives, hard drives, etc. Networking and internet is also no issue as if it works on the server, it has to work on each of the terminals too... SoaS is also working on a slightly different issue. I didn't understand it until Caroline explained it for about the 100th time yesterday:) In addition to all the technical hurdles. Sugar on a Stick is tackling the _bureaucratic_ issue of installing and running Sugar (or any software) on systems which one doesn't have admin access. In many schools it can be difficult to get the authority to install software or modify the configuration on their computers. SoaS circumvents that problem by replacing 'install a new OS' with 'insert the stick and turn it on.' The piece that I was _misunderstanding_ was that all of the technically hurdles that SoaS introduces are worth the ability to circumvent the bureaucratic hurdles. FWIW, at least in developed nations Once you get the bureaucratic permission to 'install' Sugar, a client-server configuration is most palatable to the existing generation of elementary school sysadmins. david kind Regards, David (nubae) Van Assche On Sun, Jun 7, 2009 at 5:27 PM, Frederick Grose fgr...@gmail.com wrote: On Sun, Jun 7, 2009 at 10:07 AM, Caroline Meeks carol...@solutiongrove.com wrote: Let me echo Caryl's question. Do we have a page with tasks for new volunteers? http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO has been restored and is ready to be updated, perhaps restructured to cover this need. --Fred ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
Thanks David great explanation. and David, I totally agree that LTSP is the right technical solution for this computer lab. Next year, perhaps we will have the level of trust and political clout to implement it. There is yet another reason I want to know if we can speed up these computers and ones like it. Part of the Sugar on a Stick vision is the kids having a computer at home. So next year, when we replace the computer lab with LTSP, we will probably send the existing boxes home with kids who don't have computers. If for less then $10 and a hour of volunteer time we can send a kid home with a snappy system vs a pokey one, I think that is totally worth it and that we will not have trouble finding the volunteers to do the work. On Sun, Jun 7, 2009 at 2:19 PM, David Farning dfarn...@sugarlabs.orgwrote: On Sun, Jun 7, 2009 at 12:24 PM, David Van Asschedvanass...@gmail.com wrote: When it come to older pcs, it really makes sense to try and use LTSP. We have created a kiwi-ltsp usb stick for openSUSE, which gives a portable ltsp server wherever u plug it in. In most cases it would make sense for this to be the most powerful computer. It is as easy as installing the sugar and sugar activities meta packages on this usb image and the users on the ltsp network then have access to Sugar from any computer in the network, and they are bound to load faster than from a usb image. The advantage is u need one usb stick per network, as opposed to one for each terminal... that saves costs, and time. Also, u dont need any of the old hardware, such as cdrom drives, hard drives, etc. Networking and internet is also no issue as if it works on the server, it has to work on each of the terminals too... SoaS is also working on a slightly different issue. I didn't understand it until Caroline explained it for about the 100th time yesterday:) In addition to all the technical hurdles. Sugar on a Stick is tackling the _bureaucratic_ issue of installing and running Sugar (or any software) on systems which one doesn't have admin access. In many schools it can be difficult to get the authority to install software or modify the configuration on their computers. SoaS circumvents that problem by replacing 'install a new OS' with 'insert the stick and turn it on.' The piece that I was _misunderstanding_ was that all of the technically hurdles that SoaS introduces are worth the ability to circumvent the bureaucratic hurdles. FWIW, at least in developed nations Once you get the bureaucratic permission to 'install' Sugar, a client-server configuration is most palatable to the existing generation of elementary school sysadmins. david kind Regards, David (nubae) Van Assche On Sun, Jun 7, 2009 at 5:27 PM, Frederick Grose fgr...@gmail.com wrote: On Sun, Jun 7, 2009 at 10:07 AM, Caroline Meeks carol...@solutiongrove.com wrote: Let me echo Caryl's question. Do we have a page with tasks for new volunteers? http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO has been restored and is ready to be updated, perhaps restructured to cover this need. --Fred ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
On Sun, Jun 7, 2009 at 7:24 PM, David Van Asschedvanass...@gmail.com wrote: When it come to older pcs, it really makes sense to try and use LTSP. We LTSP is an excellent path. Note that a happy LTSP adventure is conditional on a good network infra and a decent TS machine. Wireless won't do. Sound and video used to be almost impossible to setup, or plainly unusable -- I hope that it has improved with the help of pulseaudio and other bits and pieces. 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 ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
On Sun, Jun 7, 2009 at 2:38 PM, David Van Asschedvanass...@gmail.com wrote: That's a good point, and I understand the thinking behind it, as if you are not 'changing' anything in an existing setup, people are less afraid that things might go terribly wrong. That's the reason we have ltsp on a usb stick... because you can stick in a server, and test it without installing anything. Think of it as SoaS server with beaurocratic advantages included (taking care of networking, providing Sugar images, setting up user accounts, providng collaboration if necessary. It is by no means the XS server, nor should it try to be that, its just the desktop environment part with ejabberd, if needed.. of course, it only works in wired environments. Very cool. I had not heard of LTSP on a usb stick before. It sound like another great, low impact (I am trying to think of a term like 'carbon foot print' to properly reflect the impact) way of bringing LTSP into the class room. david kind Regards, David (nubae) Van Assche On Sun, Jun 7, 2009 at 8:19 PM, David Farning dfarn...@sugarlabs.org wrote: On Sun, Jun 7, 2009 at 12:24 PM, David Van Asschedvanass...@gmail.com wrote: When it come to older pcs, it really makes sense to try and use LTSP. We have created a kiwi-ltsp usb stick for openSUSE, which gives a portable ltsp server wherever u plug it in. In most cases it would make sense for this to be the most powerful computer. It is as easy as installing the sugar and sugar activities meta packages on this usb image and the users on the ltsp network then have access to Sugar from any computer in the network, and they are bound to load faster than from a usb image. The advantage is u need one usb stick per network, as opposed to one for each terminal... that saves costs, and time. Also, u dont need any of the old hardware, such as cdrom drives, hard drives, etc. Networking and internet is also no issue as if it works on the server, it has to work on each of the terminals too... SoaS is also working on a slightly different issue. I didn't understand it until Caroline explained it for about the 100th time yesterday:) In addition to all the technical hurdles. Sugar on a Stick is tackling the _bureaucratic_ issue of installing and running Sugar (or any software) on systems which one doesn't have admin access. In many schools it can be difficult to get the authority to install software or modify the configuration on their computers. SoaS circumvents that problem by replacing 'install a new OS' with 'insert the stick and turn it on.' The piece that I was _misunderstanding_ was that all of the technically hurdles that SoaS introduces are worth the ability to circumvent the bureaucratic hurdles. FWIW, at least in developed nations Once you get the bureaucratic permission to 'install' Sugar, a client-server configuration is most palatable to the existing generation of elementary school sysadmins. david kind Regards, David (nubae) Van Assche On Sun, Jun 7, 2009 at 5:27 PM, Frederick Grose fgr...@gmail.com wrote: On Sun, Jun 7, 2009 at 10:07 AM, Caroline Meeks carol...@solutiongrove.com wrote: Let me echo Caryl's question. Do we have a page with tasks for new volunteers? http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/TODO has been restored and is ready to be updated, perhaps restructured to cover this need. --Fred ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 On Sun, Jun 07, 2009 at 04:40:31PM -0500, David Farning wrote: On Sun, Jun 7, 2009 at 2:38 PM, David Van Asschedvanass...@gmail.com wrote: That's a good point, and I understand the thinking behind it, as if you are not 'changing' anything in an existing setup, people are less afraid that things might go terribly wrong. That's the reason we have ltsp on a usb stick... because you can stick in a server, and test it without installing anything. Think of it as SoaS server with beaurocratic advantages included (taking care of networking, providing Sugar images, setting up user accounts, providng collaboration if necessary. It is by no means the XS server, nor should it try to be that, its just the desktop environment part with ejabberd, if needed.. of course, it only works in wired environments. Very cool. I had not heard of LTSP on a usb stick before. Great indeed. It sound like another great, low impact (I am trying to think of a term like 'carbon foot print' to properly reflect the impact) way of bringing LTSP into the class room. polite or gentle perhaps? or non-invasive? Emphasizing what is avoided: invading - potentially taking over, accidentally or on purpose, the computers Or did I misunderstand the kind of term you had in mind? Kind regards, - jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREDAAYFAkosQp0ACgkQn7DbMsAkQLhCXQCgnD7wIbtV99DEe6cHJOkcHqQj djEAnjWsys5SJGSoD9zo1XefN9GpGwP+ =yKke -END PGP SIGNATURE- ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] Getting data about the upgrading older machines and SoaS responsiveness.
On Sun, Jun 7, 2009 at 18:43, Jonas Smedegaard d...@jones.dk wrote: It sound like another great, low impact (I am trying to think of a term like 'carbon foot print' to properly reflect the impact) way of bringing LTSP into the class room. polite or gentle perhaps? or non-invasive? Emphasizing what is avoided: invading - potentially taking over, accidentally or on purpose, the computers Granted, you would *need* to check with your local systems administrator before implementing LTSP. (as opposed to a lower-risk USB-local-booting solution) At my school, for example, netbooting a workstation starts the recloning process of loading a new Windows XP image; setting up LTSP without asking would cause major problems with their work. -- Luke Faraone http://luke.faraone.cc ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
