Man pages on XO
Hi all, I'm working on turning the XO-1.75 build 12.1.0 into a school server. I want to make loading man pages an option. I used yum downloadonly to fetch the man-pages.rpm. Used rpm -qipl man-pages to verify that they load to /usr/share/man/*. Then when I installed them using rpm -ivh man-pages, they appeared to be installing. But /usr/share/man/* is still empty. It's as if there was a yum macro that relocated /usr/share/man to /dev/null, but I can't find the setting. Any ideas of where to look? George ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO battery/performance [Devel Digest, Vol 76, Issue 21]
On 07/21/2012 12:53 PM, Yioryos Asprobounitis wrote: I'm sorry but I did not run any bg-acr! commands except the one you suggested. The only command that I run outside your suggestions is bg-acr@ .bg-acr with no batman.fth/batman-start first, which certainly can not account for the erratic behavior. Commands _like_ 'bg-acr!' that includes all of the bg-* commands and many others. They _require_ batman-start to function. If it hasn't been called then they do it for you. Thus if you have run those command and not run batman-stop then the charging system will behave erratically. bg-acr! changes values that take the EC close to a full cycle to recovery from so even after a full reset the reporting can be incorrect. I keep saying that the battery EC might have a problem There is no battery EC. The battery only has a sensor chip. The EC on the XO talks to that chip and reads voltage, current, temperature, ACR and a few other values. and you just dismiss all the indications (like a full battery reporting as empty) I'm sorry if my last mail came across the wrong way I was in a bit of a hurry before my flight. Its just that I keep telling you that nothing you have presented so far indicates there is a communication problem between the EC and battery. I'll be the very first to tell you when I see something I think is funky. Just like with the rollover bug. I'm not dismissing what you say. I'm just trying to tell you that you aren't doing anything useful debugging wise when you try to figure out whats going on based on the charging LED or what sugar tells you. The use of _any_ of the debugging commands I gave you will screw up the normal battery reporting. If you want to known whats happening when you boot Linux then please do a full power cycle and run olpc-pwr-log. Those log files are much, much, more useful than what the LED/Sugar is doing. The LED/sugar can lie to you but the log files do not. Normally, I boot the laptop without the battery installed, run olpc-pwr-log and then insert the battery. olpc-pwr-log will wait for a battery to show up. including even the fact that EC reports the battery is asleep while the discharge data show that is not. Its not possible for the battery to go to sleep. I don't understand what you are referring to. Oh well, I do not think that one battery in a couple of millions worths all this trouble. Actually I believe it is worth the trouble because there is never just a single problem that doesn't happen to another machine. If you have this failure then there are probably many more. Its just never been reported. I'm happy to keep working on this if you don't mind the time. -- Richard A. Smith rich...@laptop.org One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO battery/performance [Devel Digest, Vol 76, Issue 21]
--- On Sun, 7/22/12, Richard A. Smith rich...@laptop.org wrote: Actually I believe it is worth the trouble because there is never just a single problem that doesn't happen to another machine. If you have this failure then there are probably many more. Its just never been reported. I'm happy to keep working on this if you don't mind the time. I'm afraid that I can not be of much help. Let me repeat the problems as I see them, (pretty much as originally stated) - The battery loses too much charge (~12% in 24h) when in an XO but not when out. - The battery has a bit decrease capacity (2.75Ah was the max I ever recorded last month) - The battery miss-communicates its state to the kernel/OS (BTW usually I confirm erratic Sugar readings by looking directly at /sys/class/power_supply/olpc-battery/) After a month of e-mails we hopefully agree in 2 out of the 3 symptoms and have no causes/solutions yet. As I said before, the problem needs an engineer if it is to be investigated any further, and I'm not. You are welcome to the battery. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO battery/performance [Devel Digest, Vol 76, Issue 21]
On 07/22/2012 04:29 PM, Yioryos Asprobounitis wrote: As I said before, the problem needs an engineer if it is to be investigated any further, and I'm not. You are welcome to the battery. Ok. Well then please send me the battery. Richard Smith One Laptop per Child 222 3rd St. STE 0234 Cambridge, MA 02142 +1 617-714-4589 Thanks for all your help so far. -- Richard A. Smith rich...@laptop.org One Laptop per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Man pages on XO
Edit /etc/rpm/macros.imgcreate and remove the %_excludedocs line, then install the RPMs again, and also include the man package so you can read them. The man-pages package are a collection from the Linux Documentation Project, and are not the manual pages included with each package. If you are using olpc-os-builder to make a fresh build ... which would give you a much smaller build since it wouldn't include GNOME and Sugar and applications ... search for and remove the --excludedocs option in osbuilder.py -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
forth scripting
Hi All: Is there a build-in function in OFW that I can use to detect a non-empty directory before I re-invent the wheel? Any quick way to display all the defined words in use in OFW? Jerry ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
