Re: [Ltsp-discuss] KIWI-LTSP: some clarifications
So ?? Is it SAFE for me to use OpenSuse 11 + KIWI-LTSP at my Office ?? I've plan to install new LTSP Server using OpenSuse 11 + KIWI-LTSP. Instead of KIWI-LTSP .. what should I use wiht OpenSuse 11 if I would like to implement LTSP ? can I use LTSP-4.2 ? Need your suggestion. Best Regards, Donny Christiaan. On Thu, Aug 21, 2008 at 5:40 PM, CyberOrg [EMAIL PROTECTED] wrote: On Thu, Aug 21, 2008 at 3:47 PM, Oliver Grawert [EMAIL PROTECTED] wrote: hi, On Do, 2008-08-21 at 11:19 +0530, CyberOrg wrote: So how are we making contribution to the LTSP? - We are introducing users of one of the top two distributions to this great way of computing: LTSP. We are trying to make use of LTSP popular. who then get lost during suport in teh #ltsp channel since nobody there knows much about kiwi really, it is not that hard to make kiwi a backend like all other distros do with their build tools (anaconda for redhat, debootstrap and a set of metapackages for ubuntu and debian, stage1 and emerge for gentoo) you have the necessary plugins for kiwi in place in the upstream code, using teh plugin system to seed kiwi variables with the common system we all use (and can help with in support) would be a first step ... its great that you use kiwi but i'm 100% sure you can as well use it as a backend like all of us do and work with the common plugins so people are not lost and have to be sent to #kiwi if the are asking for support. Yes, to keep it common we have a SUSE plugin already in place, it is fully functional as it is. Hopefully someone who is familiar with how KIWI works would always be around, that is not going to come in way of helping users as LTSP still is the same. I always respond to any queries posted on mailing lists, I am also always idling in #ltsp, refer to IRC logs if someone has pinged me and respond if they are online. contributes to. i know that japerry showed interest to help getting the suse side in shape to function in a proper upstream way so lets sit down together and develop a plan how to do it so we dont have one distro that doesnt fit the scheme and users can get proper support ... its really not that hard to just change the order of the scripts to wrap around kiwi and use all the distro independent variables and options instead of kiwi wrapping around the scripts. Japerry, gbolte have always been very keen to help, and even made it to the LTSP hackfest. They too are openSUSE community members and not developers. the BTS hackfest in november should be a very good opportunity to do it, how about sending one person there and getting suse in shape ? i'm hapy to help with that if needed and i know the other distro devs would too for teh ske of having something thats similar over all distros ... I had requested Guy Lunardi to send someone for the hackfest, which did not materialise, so also requested Zonker to send someone over, but it was too late. It is upto the powers that be at Novell/SUSE to make it possible, again Zonker would be the best person to get it done. Please be assured that we are not on the opposing sides, we just want LTSP5 working very well and are deploying tools that are most familiar and efficient for us without having to code. Wrapping everything we do with kiwi in LTSP plugin has been done, it would take a proper developer to do more. Cheers -J - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] KIWI-LTSP: some clarifications
On Fri, Aug 22, 2008 at 2:04 PM, Donny Christiaan [EMAIL PROTECTED] wrote: So ?? Is it SAFE for me to use OpenSuse 11 + KIWI-LTSP at my Office ?? I've plan to install new LTSP Server using OpenSuse 11 + KIWI-LTSP. Yes, it is quite safe to use :) It has all the same features available in LTSP implementation on Ubuntu. Follow the instructions here: http://en.opensuse.org/LTSP There is now a GUI also available to make things easier: http://en.opensuse.org/Easy-LTSP Instead of KIWI-LTSP .. what should I use wiht OpenSuse 11 if I would like to implement LTSP ? can I use LTSP-4.2 ? LTSP 4.2 is not recommended as it is now quite old and unmaintained. Cheers -J - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] KIWI-LTSP: some clarifications
hi, On Do, 2008-08-21 at 11:19 +0530, CyberOrg wrote: So how are we making contribution to the LTSP? - We are introducing users of one of the top two distributions to this great way of computing: LTSP. We are trying to make use of LTSP popular. who then get lost during suport in teh #ltsp channel since nobody there knows much about kiwi really, it is not that hard to make kiwi a backend like all other distros do with their build tools (anaconda for redhat, debootstrap and a set of metapackages for ubuntu and debian, stage1 and emerge for gentoo) you have the necessary plugins for kiwi in place in the upstream code, using teh plugin system to seed kiwi variables with the common system we all use (and can help with in support) would be a first step ... its great that you use kiwi but i'm 100% sure you can as well use it as a backend like all of us do and work with the common plugins so people are not lost and have to be sent to #kiwi if the are asking for support. please dont point out again that kiwi is a fine standalone tool ... all of us use such tools more or less, but thats not the point, the point is that we all want to use the same code and want to collaborate and thus decided to put our image and chroot building tools in teh backend, that way it is possible to have distro independent ltsp tools *everybody* contributes to. i know that japerry showed interest to help getting the suse side in shape to function in a proper upstream way so lets sit down together and develop a plan how to do it so we dont have one distro that doesnt fit the scheme and users can get proper support ... its really not that hard to just change the order of the scripts to wrap around kiwi and use all the distro independent variables and options instead of kiwi wrapping around the scripts. the BTS hackfest in november should be a very good opportunity to do it, how about sending one person there and getting suse in shape ? i'm hapy to help with that if needed and i know the other distro devs would too for teh ske of having something thats similar over all distros ... ciao oli signature.asc Description: This is a digitally signed message part - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/_ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
Re: [Ltsp-discuss] KIWI-LTSP: some clarifications
On Thu, Aug 21, 2008 at 3:47 PM, Oliver Grawert [EMAIL PROTECTED] wrote: hi, On Do, 2008-08-21 at 11:19 +0530, CyberOrg wrote: So how are we making contribution to the LTSP? - We are introducing users of one of the top two distributions to this great way of computing: LTSP. We are trying to make use of LTSP popular. who then get lost during suport in teh #ltsp channel since nobody there knows much about kiwi really, it is not that hard to make kiwi a backend like all other distros do with their build tools (anaconda for redhat, debootstrap and a set of metapackages for ubuntu and debian, stage1 and emerge for gentoo) you have the necessary plugins for kiwi in place in the upstream code, using teh plugin system to seed kiwi variables with the common system we all use (and can help with in support) would be a first step ... its great that you use kiwi but i'm 100% sure you can as well use it as a backend like all of us do and work with the common plugins so people are not lost and have to be sent to #kiwi if the are asking for support. Yes, to keep it common we have a SUSE plugin already in place, it is fully functional as it is. Hopefully someone who is familiar with how KIWI works would always be around, that is not going to come in way of helping users as LTSP still is the same. I always respond to any queries posted on mailing lists, I am also always idling in #ltsp, refer to IRC logs if someone has pinged me and respond if they are online. contributes to. i know that japerry showed interest to help getting the suse side in shape to function in a proper upstream way so lets sit down together and develop a plan how to do it so we dont have one distro that doesnt fit the scheme and users can get proper support ... its really not that hard to just change the order of the scripts to wrap around kiwi and use all the distro independent variables and options instead of kiwi wrapping around the scripts. Japerry, gbolte have always been very keen to help, and even made it to the LTSP hackfest. They too are openSUSE community members and not developers. the BTS hackfest in november should be a very good opportunity to do it, how about sending one person there and getting suse in shape ? i'm hapy to help with that if needed and i know the other distro devs would too for teh ske of having something thats similar over all distros ... I had requested Guy Lunardi to send someone for the hackfest, which did not materialise, so also requested Zonker to send someone over, but it was too late. It is upto the powers that be at Novell/SUSE to make it possible, again Zonker would be the best person to get it done. Please be assured that we are not on the opposing sides, we just want LTSP5 working very well and are deploying tools that are most familiar and efficient for us without having to code. Wrapping everything we do with kiwi in LTSP plugin has been done, it would take a proper developer to do more. Cheers -J - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ _ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
[Ltsp-discuss] KIWI-LTSP: some clarifications
Hello Community Recently there has been some concerns about the role of KIWI in LTSP5 implementation in openSUSE. I think it would be best if we discuss this openly with the community and furnish the clarifications to address misunderstandings about our work. Let me start by explaining who is working on KIWI-LTSP. I have been working on getting LTSP5 on openSUSE using KIWI imaging technology, I am not employed by Novell or hold any official position with openSUSE, so whatever work that is done is done in my own time as a contribution to the community of the distribution I use. Important point to note is that *I cannot code*. Other team members include Magnus Boman, who is a Novell employee, he is helping me purely in his personal time (whatever little he can spare in his busy schedule). KIWI is a separate project lead by Marcus Schaefer, it is hosted here: http://kiwi.berlios.de/, it is the main tool that we use. KIWI is distribution independent, extremely sophisticated toolkit that is used to build system images of any kind, currently it supports Xen, VMX, Live CD, Live USB, Network Booting. It also supports various types of thin client technologies such as embedded TC used in Novell's enterprise products. It is also an engine that drives: http://studio.suse.com - a protal where everyone can create their own OS with few mouse clicks. Due to KIWI's capabilities it is natural for us to take full advantage of all the features it provides, some features that will never be available in LTSP's plugin system without someone coding it again. KIWI is the reason LTSP5 implementation on openSUSE has a lot of additional features such as providing LTSP prebuilt images through rpm, Live USB client that can be used with LTSP server running any Distribution, Live CD client and many more. Apart from the KIWI as a tool we use to create and configure image, all the core components of LTSP such as : LDM, LTSPFS/D, initscript, lts.conf, configure_x.sh, localapp support etc are *exactly as upstream without any patch specific to openSUSE*. The LTSP's plugin system has been presented as ready-to-use distribution independent way of building and configuring LTSP images, we appreciate the effort that has gone into it so have worked closely with upstream developers Ogra and VagrantC to implement fully functional openSUSE plugin. The shortcomings of the plugin system's common code or rather my own is, I cannot code, and cannot modify it to get it working on openSUSE, anyone suggesting that all the other distributions are able to work with it except us would be very misguided. A paid developer from Redhat has been working extremely hard to get it to work on Fedora since almost a year, it is still not at the feature parity of the implementation we had on openSUSE last year. Gentoo team is struggling to get it working since last many months too. Debian too did not have many features including NBD+squashfs+aufs until recently, so only distributions that had all the features of LTSP implementation using plugin system is Ubuntu. Imagine that all this effort will have to be repeated again to get LTSP implemented on new distro. I agree that if all the distributions used the plugin system it will benefit everyone, I do not have skills to work on it, hopefully one day some SUSE developer will take this up. Until then, to me as a non-developer KIWI is a perfect tool that allows me to do everything that is required from ltsp's plugin system and lot more with very little effort. So how are we making contribution to the LTSP? - We are introducing users of one of the top two distributions to this great way of computing: LTSP. We are trying to make use of LTSP popular. - We worked on Easy-LTSP - A truely distribution independent tool to easily configure lts.conf during this Google Summer of Code, surely it fills in a gap that has been there for a long time. - We provide easy to install rpm packages for LTSP via openSUSE Build Service, as a demonstration and a goodwill gesture we offered to build it for all distributions supported by oBS, a platform that could be immensely useful for upstream to provide builds of development snapshots while their official packages can go in the distribution's repo/media. - Easy to follow documentation(although not as good as edubuntu's) here: http://en.opensuse.org/LTSP - Some users of KIWI-LTSP already hang out in #ltsp and help with questions, not just on openSUSE but for other distributions too - There has been some suggestions(about LDM from lejo)/patches(gbolte's team for ltspfs) from kiwi-ltsp users too. My apologies for not being able to contribute upstream, hopefully it will be remedied in future by more active participation from SUSE devs. I am sure this helped clear some things up, if not, this is the place to discuss ask away any questions you may have :) Kind regards -J - This SF.Net email is sponsored by the
