Re: non-Sugar but core software?
Holger Levsen wrote: > for Debian I've started http://wiki.debian.org/DebianEdu/OLPC/ToDo yesterday, > to document what is working and whats not and what work needs to be done. > > In general, a document describing how the XO-1-fedora installation differs > from a plain fedora would be very much appreciated, also by the OpenWRT > developers. A quick (although low-level) way to find out, is going through the Fedora pkgdb to find the complete list of packages we've forked in the OLPC-2 collection: https://admin.fedoraproject.org/pkgdb/collections/ For each one of these, you can checkout the cvs source: cvs -d :pserver:[EMAIL PROTECTED]/cvs/pkgs co Then you can diff between the version in F-7 and the one in OLPC-2. Many changes are not OLPC specific and will hopefully be merged back with our upstreams as soon as the relevant maintainers find the time to clean them up. I've been doing some of this work for my packages, but I'm afraid there's a lot more to be done, especially in Xorg. Feel free to beat me! This list does not include a small number of packages that need to be moved to koji and have not made it yet for various reasons. You can find all these by grepping for "olpc-joyride" in our build logs: http://xs-dev.laptop.org/cscott/olpc/streams/joyride/latest/devel_jffs2/build.log Finally, while I have no time to do much of this work myself, I'm glad to help integrate our customizations into Debian, OpenWRT, or any other distro willing to support the XO. -- \___/ |___| Bernardo Innocenti - http://www.codewiz.org/ \___\ One Laptop Per Child - http://www.laptop.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: non-Sugar but core software?
Hi, for Debian I've started http://wiki.debian.org/DebianEdu/OLPC/ToDo yesterday, to document what is working and whats not and what work needs to be done. In general, a document describing how the XO-1-fedora installation differs from a plain fedora would be very much appreciated, also by the OpenWRT developers. regards, Holger pgp1BitIwTmpF.pgp Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: non-Sugar but core software?
Hi, evince-olpc is deprecated. The new package that should be used with Read is sugar-evince. Reinier C. Scott Ananian wrote: > *In general* packages have 'olpc' in their titles because they are not > appropriate for non-XO machines. There are exceptions: olpc-contents > and olpc-evince (or is it called evince-sugar?) come to mind. > --scott > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: non-Sugar but core software?
*In general* packages have 'olpc' in their titles because they are not appropriate for non-XO machines. There are exceptions: olpc-contents and olpc-evince (or is it called evince-sugar?) come to mind. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: non-Sugar but core software?
Michael Stone wrote: > Jani, > > Adapting Rainbow (the activity isolation component) to work on regular > linux systems is an interesting challenge that I'd love to discuss with > you. Unless Rainbow is necessary for parts of the Sugar emulation to work correctly - minus security - it is not a priority for packaging until the rest of Sugar is done. I have not looked at Rainbow at all, so at this moment I am afraid I cannot intelligently reply to your comments. Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: non-Sugar but core software?
Jani, Adapting Rainbow (the activity isolation component) to work on regular linux systems is an interesting challenge that I'd love to discuss with you. At present, there are three or so issues that would need to be overcome: First, magic numbers. The rainbow codebase hardcodes some magic numbers and strings that would need to be broken out and made configurable. Second, dbus configuration. Most standard dbus configurations create session buses which accept connections from exactly one uid. This is totally incompatible with the security model that we're implementing. Fortunately, the session bus config file makes this option somewhat configurable. Unfortunately, being a single-user system, it was most expedient to simply disable the check entirely than to work out a more reasonable setting. Therefore, if we wish to support multi-user systems, some work will need to be done to make the session bus play nicely with Rainbow. Some more work might need to be done to allow per-human-operator state in rainbow itself. Finally, there's some work that should probably be done to finish a rainbow nss module since it probably conflicts will all sorts of distro guidelines to write software that wantonly writes to /etc/passwd and /etc/group every time you use it to launch an activity. All this being said, Rainbow can definitely be adapted to the standard linux desktop environment and I am very excited about performing that adaptation (time permitting) because I know that I've often wanted something like Rainbow around when I'm trying out software from sources that I don't fully trust. Thoughts? Michael On Sat, Jan 12, 2008 at 04:24:45PM +0200, Jani Monoses wrote: > Hello, > > which software besides Sugar and the activities are XO independent and > would make sense to be packaged and run in emulators or normal PCs? > I see there are various projects with olpc in their name - olpc-utils, > olpc-content, then there's the security infrastructure. > I'd appreciate any suggestions as to what to package after the Sugar > pieces are done. > > thank you > Jani > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
non-Sugar but core software?
Hello, which software besides Sugar and the activities are XO independent and would make sense to be packaged and run in emulators or normal PCs? I see there are various projects with olpc in their name - olpc-utils, olpc-content, then there's the security infrastructure. I'd appreciate any suggestions as to what to package after the Sugar pieces are done. thank you Jani ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
