<?xml version="1.0" encoding="ISO-8859-1"?>
	<rss version="2.0">
	<channel>
	<title>Barry Kauler</title>
	<description>Barry Kauler Puppy Linux UniPup Developer Daily Blog</description>
	<link>http://bkhome.org/blog/</link><item>
		<link>http://bkhome.org/blog/?viewDetailed=01392</link>
		<title>Woof uploaded, February 8, 2010</title>
		<category>Woof</category>
		<description>There have been three commits since the previous upload of Woof:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Quirky: experiment use mostly busybox 1.16.0 applets not good, mostly reverted&lt;br /&gt;dir2pet, petspec scripts improved&lt;br /&gt;Puppy 4.3.2-experiment1 built with this release of Woof&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Grab this one if you are interested in building your own Puppy in the 4.x series.&lt;br /&gt;&lt;br /&gt;Woof home page:&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01391</link>
		<title>Experimental unofficial Puppy 4.3.2</title>
		<category>Puppy</category>
		<description>Here it is again, with the fix for ROX-Filer:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.3.2-experimental1/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.3.2-experimental1/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The ISO has all the modem drivers in it, which is why it is a bit big (112MB). SCSI drivers are missing.&lt;br /&gt;&lt;br /&gt;There is a forum thread for feedback:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=52280 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=52280&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m only really interested in bug reports of a certain type: if something worked in 4.3.1 but not in this 4.3.2 build. It would be nice to know about the reverse also: something that did not work in 4.3.1 and does in 4.3.2.&lt;br /&gt;&lt;br /&gt;I must reiterate that I did not create this with the intention that it will be the next official 4.3.2 release. I&#39;m mostly just wanting to know that Woof builds a sane Puppy 4.x.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01390</link>
		<title>Improved modem scripts</title>
		<category>Puppy</category>
		<description>Rerwin (Richard) has posted packages for improved modem detection and management:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?p=388235#388235 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?p=388235#388235&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;He has commented:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Barry and technosaurus might wait a while before integrating them, to allow users to &quot;shake it out&quot;&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;So, everyone running Puppy 4.3.1 or later variant, is invited to test these packages!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01389</link>
		<title>ROX-Filer: fix for focus bug</title>
		<category>Woof</category>
		<description>I described this problem here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01387 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01387&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I would like to thank &#39;perthie&#39; who responded, informing me of a fix posted to the Dpup forum thread.&lt;br /&gt;&lt;br /&gt;I found it:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=50728&amp;start=15 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=50728&amp;start=15&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...thanks to &#39;rcrsn51&#39; for the fix.&lt;br /&gt;&lt;br /&gt;I have tested in pup 432 and the fix works. I have implemented this fix in Woof, adding this code to /etc/profile:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;#100208 rox-filer needs this for GTK &gt;= 2.18, fixes focus problem...&lt;br /&gt;if [ `grep &#39;^gtk+-2&#39; /root/.packages/woof-installed-packages | head -n 1 | cut -f 2 -d &#39;.&#39;` -ge 18 ];then&lt;br /&gt; export GDK_NATIVE_WINDOWS=true&lt;br /&gt;fi&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01388</link>
		<title>Gecko: Adobe Flash player crashes</title>
		<category>Puppy</category>
		<description>With my &quot;432&quot; pup, which has Adobe Flashplayer 10.x, it crashes when I try to play a video at youtube.com. In /tmp/xerr.log I see &quot;illegal instruction&quot;.&lt;br /&gt;&lt;br /&gt;So I tried Flashplayer9, same thing.&lt;br /&gt;&lt;br /&gt;So I tried pskin&#39;s 431 pup, same thing.&lt;br /&gt;&lt;br /&gt;Then I tried WattOS, and that works. WattOS has the Adobe player.&lt;br /&gt;&lt;br /&gt;Just on the off-chance, I got the player out of WattOS and tried it in pup 431, still crashes.&lt;br /&gt;&lt;br /&gt;So, it&#39;s something else. I suspect the MTRR registers. The kernel used in WattOS has MTRR disabled. I suppose that I could try that, recompile the kernel for Puppy with MTRR disabled.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01387</link>
		<title>Experimental Puppy 4.3.2</title>
		<category>Puppy</category>
		<description>I have built this using Woof, so it has the latest infrastructure, that is, all the underlying scripts. I also updated or added these packages:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;915resolution, bones, cpu-scaling-ondemand, flashplayer10, grub4dos (instead of grub), lamesmbxplorer (instead of pnethood), ntfs-backup, pburn, pcd, pfind, pmusic (instead of aqualung), precord, pupradio, seamonkey_addone_flashblock, seamonkey_addon_user_agent_switcher, sfs-converter, util-macros, woo-ff, floppy-format&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I am using it right now, and it is working fine. There is just one thing, a bug with ROX-Filer that plagued me awhile back with Quirky. When I built Quirky with GTK 2.18.3, ROX-Filer exhibited a problem in which file icons would stay shadowed/selected. For example, if I right-click on a file then choose to open it in the text editor, the file icon remains shadowed, even after the text editor is closed. It is effectively still &quot;selected&quot; and this has an adverse effect if you don&#39;t click in the window to de-select it, as if you for example click on some other file, the previous one is actually chosen -- awful!&lt;br /&gt;&lt;br /&gt;In Quirky, I rolled back to GTK 2.16.6 and that fixed it. However, to my great surprise, I now have the problem in 4.3.2. I was thinking &quot;oh no!!!!&quot;, but then I discovered that Woof built Puppy 432 with my latest GTK 2.18.3 packages. So, bear in mind that the ISO I have uploaded has the &quot;wrong&quot; version of GTK, which may also adversely affect some applications.&lt;br /&gt;&lt;br /&gt;I&#39;ll do another build tomorrow. &lt;br /&gt;&lt;br /&gt;Am I planning to release an official Puppy 4.3.2? No, I built this because the &#39;rdc&#39; Xorg driver does not work in Xorg 7.5, which is what Quirky uses. I have installed 432 into the Gecko Edubook, but it turns out that the &#39;rdc&#39; driver is too buggy so I&#39;m only using the &#39;vesa&#39; driver -- so I might as well have stayed with Quirky.&lt;br /&gt;&lt;br /&gt;...so that&#39;s how 432 came into being. As I have come this far, I&#39;ll fix the ROX-Filer problem, and might even recompile the kernel to add the elantech touchpad support that Jemimah wanted.&lt;br /&gt;&lt;br /&gt;Anyway, if you feel like you want to play with it, get Puppy &quot;unofficial&quot; 4.3.2 with &quot;wrong&quot; GTK version here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/experimental-432/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/experimental-432/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;BUT&lt;/b&gt;, I must emphasise that some apps may be adversely affected by this later GTK. So please do not report that Abiword worked in 431 but has become strange in 432. If in doubt, wait and I&#39;ll upload 432 with the correct GTK in a day or two.&lt;br /&gt;&lt;br /&gt;Note, after I have built 432 with correct version of GTK, I&#39;ll upload Woof that has been used to build this pup.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01386</link>
		<title>2.6.30.5 kernel recompiled</title>
		<category>Puppy</category>
		<description>Forum member pskin has already done this, but I have also been through the exercise as I wanted to make some other minor configuration changes.&lt;br /&gt;&lt;br /&gt;I patched the kernel source to support audio on the Gecko Edubook, and made these configuration changes (relative to the kernel used in 4.3.1):&lt;br /&gt;&lt;br /&gt;Kernel compression mode (gzip) -- changed from lzmo&lt;br /&gt;(15) Kernel log buffer size -- up from 14&lt;br /&gt;apm bios support: [*] ignore user suspend&lt;br /&gt;&lt;br /&gt;...after compiling the kernel, I remembered that Jemimah wanted support for the Elantech touchpad -- doh! -- well, maybe I&#39;ll compile it again soon.&lt;br /&gt;&lt;br /&gt;The changes are very small, and all existing modules created for Puppy 4.3.1 should still work.&lt;br /&gt;&lt;br /&gt;I have uploaded the patched source and the .config file:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/sources/kernel-2.6.30.5-pup432/ target=_blank&gt;http://bkhome.org/sources/kernel-2.6.30.5-pup432/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01385</link>
		<title>&#39;tr&#39; mystery</title>
		<category>Woof</category>
		<description>One of the scripts in Woof has suddenly gone crazy. I found the cause: the &#39;tr&#39; utility has suddenly developed an abnormality. The script uses &#39;tr&#39; to convert all lower-case letters to upper, like this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# echo &#39;abc&#39; | tr [a-z] [A-Z]&lt;br /&gt;ABC&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...well, the output used to be &#39;ABC&#39;, but now it has become &#39;abc&#39;. In other words, tr is just passing the characters through unchanged:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# echo &#39;abc&#39; | tr [a-z] [A-Z]&lt;br /&gt;abc&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I tried with the latest 1.16.0 &#39;busybox&#39; executable, same problem.&lt;br /&gt;&lt;br /&gt;I rebooted with &quot;pfix=ram&quot; and &#39;tr&#39; works. I ran my Woof script and &#39;tr&#39; becomes broken. I have used this &#39;2createpackages&#39; script many times without this problem. I am so puzzled.&lt;br /&gt;&lt;br /&gt;Ah, if I open a new terminal, &#39;tr&#39; works again. More specifically, if I open another terminal in the same Woof directory as my script, &#39;tr&#39; is broken. Open a terminal anywhere else, &#39;tr&#39; works.&lt;br /&gt;&lt;br /&gt;However, if I do it this way, tr comes good again:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# echo &#39;abc&#39; | tr &#39;[a-z]&#39; &#39;[A-Z]&#39;&lt;br /&gt;ABC&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I put the single-quotes into my script, and it is now working. Yeah, but why?????&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01384</link>
		<title>Gecko: DMP X-Linux</title>
		<category>Puppy</category>
		<description>I have installed X-Linux, which is provided by DMP, the manufacturers of the Xcore86 CPU and the Gecko Edubook.&lt;br /&gt;&lt;br /&gt;It&#39;s a simple console-only distribution (no X).&lt;br /&gt;&lt;br /&gt;I installed it into sda2 of the SD card and made an entry in menu.lst. It booted okay.&lt;br /&gt;&lt;br /&gt;I especially wanted to know if it would power-off the Gecko. Well, guess what, it doesn&#39;t!!!!! I typed &quot;poweroff&quot; at the prompt, it did the normal shutting down things, got down to &quot;System halted&quot; and that was it, no power-off.&lt;br /&gt;&lt;br /&gt;But, I don&#39;t know how the software request to power-off actually works. Perhaps the fault is not on the actual circuit board but in the design of the power supply -- just guessing.&lt;br /&gt;&lt;br /&gt;If DMP themselves can&#39;t do it, what can I say? I&#39;m not going to rush into writing what I&#39;m thinking. I&#39;ll keep investigating, and will post my conclusions on the Edubook in a couple of days.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01383</link>
		<title>Gecko: success booting FreeDOS</title>
		<category>Puppy</category>
		<description>Yay, I finally got there!&lt;br /&gt;&lt;br /&gt;Thanks for all the feedback guys.&lt;br /&gt;&lt;br /&gt;What I ended up doing was using GRUB4DOS. I intended to put in either GRUB or GRUB4DOS anyway, to offer dual booting between the DOS shell and Puppy/Quirky.&lt;br /&gt;&lt;br /&gt;Using GRUB4DOS, it was so easy. I booted Quirky 006 and used shinobar&#39;s package (which is already in Quirky) to install to the SD card, sda1, which is the little 256MB fat32 partition.&lt;br /&gt;&lt;br /&gt;I then edited &#39;menu.lst&#39;:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;title Boot FreeDOS 1.0 in sda1&lt;br /&gt;  root (hd0,0)&lt;br /&gt;  chainloader /kernel.sys&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I then placed &#39;kernel.sys&#39; and &#39;command.com&#39; from the FreeDOS live-CD into sda1.&lt;br /&gt;&lt;br /&gt;Rebooted, it works!&lt;br /&gt;&lt;br /&gt;I then placed the &#39;spiflash.exe&#39; utility and the &#39;edu.rom&#39; image file into sda1 and ran:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;c:\&gt; spiflash u edu.rom&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...it returned messages indicating success.&lt;br /&gt;&lt;br /&gt;Note, what I&#39;m working toward is to make an image of the entire SD drive, so anyone will be able to install by inserting the SD card in another computer, use &#39;dd&#39; to copy the image file, then put the SD card back into the Gecko.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01382</link>
		<title>Gecko Flash BIOS saga</title>
		<category>Puppy</category>
		<description>&lt;b&gt;Take 1: DOSBox&lt;/b&gt;&lt;br /&gt;I had the idea of booting Quirky from external USB stick, install DOSBox MSDOS emulator, then run the &#39;spiflash.exe&#39; utility. I realised it is a long shot, as the emulator is just that, an emulated environment.&lt;br /&gt;&lt;br /&gt;The experiment itself was pretty straightforward. I booted Quirky, with SDL, SDL_net and dosbox PET packages on the stick, then installed them. The &#39;spiflash.exe&#39; and &#39;edu.com&#39; are available on /mnt/sda1...&lt;br /&gt;&lt;br /&gt;# dosbox&lt;br /&gt;Z:\&gt; mount c /mnt/sda1&lt;br /&gt;Z:\&gt; c:&lt;br /&gt;Z:\&gt; spiflash u edu.rom&lt;br /&gt;Unknown CPU type&lt;br /&gt;&lt;br /&gt;...that is, spiflash executed, put up some preliminary text, then that message about CPU type.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Take 2: MSDOS format&lt;/b&gt;&lt;br /&gt;I have reformatted the Gecko internal SD card with sda1 as fat (256MB), sda2 as ext3 (6GB+) and a bit left over in case I want to create a swap partition. I did this with Gparted.&lt;br /&gt;&lt;br /&gt;The XP recovery console has &#39;format&#39; utility, but it does not accept the &#39;/s&#39; (install system shell). So, I&#39;m going to take out the SD card, plug it into another computer that runs Windows, then see if I can run &#39;format d: /s&#39; (or whatever).&lt;br /&gt;&lt;br /&gt;Then I will put the SD card back into the Gecko and should be able to boot to a MSDOS prompt.&lt;br /&gt;&lt;br /&gt;...well, that&#39;s the theory anyway!&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Take 3: Bootable MSDOS CD&lt;/b&gt;&lt;br /&gt;Daftdog and bigpup posted some links to boot CDs, I might try them first. Whatever method I come up with, it needs to be easily reproducible by others, so &quot;Take 2&quot; really should be last.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01381</link>
		<title>Gecko complaints</title>
		<category>Puppy</category>
		<description>I&#39;m typing this message from one of the Geckos right now. This one has WattOS installed, which is based on Ubuntu.&lt;br /&gt;&lt;br /&gt;Everywhere I&#39;m looking, I&#39;m finding rough edges, things where I think &quot;they could have done that better&quot;.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;WattOS&lt;/b&gt;&lt;br /&gt;Booting WattOS, some &quot;fail&quot; messages come up, which not what users should be seeing. &lt;br /&gt;&lt;br /&gt;After bootup, the touchpad is far too sensitive, and somehow my mouse pointer became translucent with a white translucent rectangle next to it -- I have no idea how that happened, and I only got rid of it by rebooting. I&#39;m now using a USB mouse.&lt;br /&gt;&lt;br /&gt;WattOS is quite nice, based on Ubuntu 9.04. The main problem though is the sluggishness compared with Puppy.&lt;br /&gt;&lt;br /&gt;Xorg is using the &#39;rdc&#39; driver, that&#39;s good.&lt;br /&gt;&lt;br /&gt;When I started Firefox, Shiretoko came up with some kind of error message. can&#39;t recall what. Second time, it started without complaint.&lt;br /&gt;&lt;br /&gt;I&#39;m finding that I very easily get repeat characters on this keyboard. Hmmm, can&#39;t make it happen now.&lt;br /&gt;&lt;br /&gt;I need to check that it powers-off. Will do that now.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01380</link>
		<title>The Gecko&#39;s have arrived</title>
		<category>Puppy</category>
		<description>If you haven&#39;t been following discussion about the Gecko Edubook on my blog, here are recent blog posts:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=00771 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=00771&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01341 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01341&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01346 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01346&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01353 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01353&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I picked them up this afternoon, and haven&#39;t had time to do much yet. I have fired up one of them, it has Puppy 431 pre-installed. Hmmm, quite a lot wrong though. It looks like they just grabbed the standard 431, knowing that I would be messing around with it and getting everything to work.&lt;br /&gt;&lt;br /&gt;Okay, starting from the beginning:&lt;br /&gt;&lt;br /&gt;When I opened the packaging, I saw that the metal back-plate was not properly attached -- which someone else also reported. The power cord does not have an Australian plug, but I have an international adapter -- that&#39;s something they will need to consider when shipping these things all over the world.&lt;br /&gt;&lt;br /&gt;I plugged in the power cord, pressed the power button, and Puppy booted. Snappy performance. But, I quickly noticed these things:&lt;br /&gt;&lt;br /&gt;1. Does not power off.&lt;br /&gt;2. &quot;save&quot; button on desktop even though PUPMODE=2 (full &quot;hard drive&quot; install).&lt;br /&gt;3. X is Xvesa.&lt;br /&gt;4. Pupscan: when click to show PCI interfaces, information is broken (that is a problem in 431, it works in Quirky 006).&lt;br /&gt;5. No battery status applet.&lt;br /&gt;6. No audio.&lt;br /&gt;7. No wifi.&lt;br /&gt;&lt;br /&gt;I booted Quirky 006 from a USB stick, and noticed a &quot;general protection fault&quot; related to APM -- which would explain why the battery status applet doesn&#39;t work. Also, the kernel reports &quot;no acpi support in BIOS found, acpi daemon is unable to proceed&quot;.&lt;br /&gt;&lt;br /&gt;Running Quirky, Xorg is using the &#39;vesa&#39; driver.&lt;br /&gt;&lt;br /&gt;My Gecko seems to have a different USB wifi unit than what &#39;pskin&#39; got. It identifies itself as &quot;Realtek RTL8188S wlan adapter&quot;, vendor: 0bda, product: 8171. A CD was provided that has a driver for it.&lt;br /&gt;&lt;br /&gt;So, I have the kernel patch for sound that pskin posted, source for wifi driver, that leaves video...&lt;br /&gt;&lt;br /&gt;Hmmm, will have to investigate the apm/acpi problem too.&lt;br /&gt;&lt;br /&gt;A nice little fun project!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01379</link>
		<title>Wireless mystery with 2.6.31 kernel</title>
		<category>Quirky</category>
		<description>My Acer 3681WXMi laptop has inbuilt wireless that uses the ath5k kernel module. It used to work, however with Quirky and the 2.6.31.5 kernel it doesn&#39;t.&lt;br /&gt;&lt;br /&gt;In the Network Wizard, when I choose to scan for neworks, an error message comes up that &#39;ifconfig wlan0 up&#39; failed, with this error:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;ifconfig: SIOCSIFFLAGS: Unknown error 132&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I googled around, and there are many wireless problems with recent kernels. My particular problem seems to have something to do with the &#39;rfkill.ko&#39; kernel module, which is now a dependency of the wireless kernel modules.&lt;br /&gt;&lt;br /&gt;There is a utility called &#39;rfkill&#39; that queries the state of a wireless interface. I ran it:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# rfkill list&lt;br /&gt;0: phy0: Wireless LAN&lt;br /&gt;	Soft blocked: no&lt;br /&gt;	Hard blocked: no&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;However, after I had done the scan with the Network Wizard, it returns this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# rfkill list&lt;br /&gt;0: phy0: Wireless LAN&lt;br /&gt;	Soft blocked: no&lt;br /&gt;	Hard blocked: yes&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;&quot;Hard blocked&quot; means that there is a hardware switch on my laptop that has turned off the wireless interface. That is just plain incorrect.&lt;br /&gt;&lt;br /&gt;I found a &quot;fix&quot; posted in a forum thread discussing the same problem with the &#39;ath9k&#39; driver. I applied it to my ath5k:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# rmmod ath5k&lt;br /&gt;# rfkill block wifi&lt;br /&gt;# rfkill unblock wifi&lt;br /&gt;# modprobe ath5k&lt;br /&gt;# ifconfig wlan0 up&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Somehow, the above clears the problem. But then, running Network Wizard and the problem comes back. So, I had a little play with /usr/sbin/wag-profiles.sh (part of Network Wizard) and modified the cleanUpInterface function:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;cleanUpInterface(){&lt;br /&gt;	# put interface down&lt;br /&gt;	#ifconfig &quot;$1&quot; down&lt;br /&gt;	killDhcpcd &quot;$1&quot;&lt;br /&gt;	# kill wpa_supplicant&lt;br /&gt;	killWpaSupplicant &quot;$1&quot;&lt;br /&gt;	# clean up some wireless stuff (taken from wifi-radar)&lt;br /&gt;	if [ &quot;$IS_WIRELESS&quot; = &quot;yes&quot; ] ; then&lt;br /&gt;	  iwconfig &quot;$1&quot; essid off&lt;br /&gt;	  iwconfig &quot;$1&quot; key off&lt;br /&gt;	  iwconfig &quot;$1&quot; mode managed # auto doesn&#39;t exist anymore??&lt;br /&gt;	  iwconfig &quot;$1&quot; channel auto&lt;br /&gt;	fi&lt;br /&gt;	# put interface down&lt;br /&gt;	ifconfig &quot;$1&quot; down&lt;br /&gt;	# reset ip address (set a false one)&lt;br /&gt;	ifconfig &quot;$1&quot; 0.0.0.0&lt;br /&gt;	# stop dhcpcd &lt;br /&gt;	#killall dhcpcd 2&gt;/dev/null&lt;br /&gt;	# flush routing table&lt;br /&gt;	#ip route flush dev &quot;$1&quot;&lt;br /&gt;	# bring interface up again&lt;br /&gt;	#ifconfig &quot;$1&quot; up&lt;br /&gt;	&lt;br /&gt;	#100202&lt;br /&gt;	ERROR=&quot;`ifconfig &quot;$1&quot; up 2&gt;&amp;1`&quot;&lt;br /&gt;	if [ &quot;$ERROR&quot; ];then&lt;br /&gt;	 case $1 in&lt;br /&gt;	  wlan*)&lt;br /&gt;	   if [ &quot;`echo &quot;$ERROR&quot; | grep &#39;ifconfig: SIOCSIFFLAGS: Unknown error 132&#39;`&quot; != &quot;&quot; ];then&lt;br /&gt;	    rmmod $INTMODULE&lt;br /&gt;	    rfkill block wifi&lt;br /&gt;	    rfkill unblock wifi&lt;br /&gt;	    modprobe $INTMODULE&lt;br /&gt;	    ERROR=&quot;`ifconfig &quot;$1&quot; up 2&gt;&amp;1`&quot;&lt;br /&gt;	   fi&lt;br /&gt;	  ;;&lt;br /&gt;	 esac&lt;br /&gt;	fi&lt;br /&gt;	if [ &quot;$ERROR&quot; ];then&lt;br /&gt;	  giveErrorDialog &quot;${L_MESSAGE_Failed_To_Raise_p1}${1}${L_MESSAGE_Failed_To_Raise_p2} ifconfig $1 up&lt;br /&gt;$L_MESSAGE_Failed_To_Raise_p3&lt;br /&gt;$ERROR&lt;br /&gt;&quot;&lt;br /&gt;	  return 1&lt;br /&gt;	fi&lt;br /&gt;&lt;br /&gt;	return $?&lt;br /&gt;} # end cleanUpInterface&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;Hmmm, now there is no error message, but it reports no networks found (there is one, about 1 foot away from my laptop!). &lt;br /&gt;&lt;br /&gt;I&#39;m far from an expert on networking, and I have left development of these wizards to others. I have messed around a bit, but that&#39;s enough.&lt;br /&gt;&lt;br /&gt;Now plugging in my USB wireless, which does work with the Wizard.&lt;br /&gt;&lt;br /&gt;The Arch Linux guys have been discussing this problem, ath5k/ath9k and 2.6.31.x:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bbs.archlinux.org/viewtopic.php?id=81930 target=_blank&gt;http://bbs.archlinux.org/viewtopic.php?id=81930&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...seem to be quite a mess.&lt;br /&gt;&lt;br /&gt;Hmmm, I wonder if the 2.6.33 kernel has improved this situation? I wonder if I can/should disable &#39;rfkill&#39; in the kernel pre-compile configuration?&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Rfkill utility links&lt;/b&gt;&lt;br /&gt;&lt;a href=http://linuxwireless.org/en/users/Documentation/rfkill target=_blank&gt;http://linuxwireless.org/en/users/Documentation/rfkill&lt;/a&gt;&lt;br /&gt;&lt;a href=http://wireless.kernel.org/download/rfkill/ target=_blank&gt;http://wireless.kernel.org/download/rfkill/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01378</link>
		<title>Termite infestation</title>
		<category>General</category>
		<description>This morning I was busy stripping off the inside lining of a wall of my house. Termites!&lt;br /&gt;&lt;br /&gt;&lt;img src=http://www.timber.org.au/ewebeditpro4/upload/Z_termites_cwc.jpg /&gt;&lt;br /&gt;&lt;br /&gt;The little buggers have been there for quite a while. Would you believe it, they eat plasterboard! The wall looked ok, but my finger went straight through. I don&#39;t think they eat the plaster itself, rather the fibre in the plasterboard.&lt;br /&gt;&lt;br /&gt;My house is wood frame, weatherboard outer cladding, plasterboard and wood panels on the inside. The wood is mostly Jarrah, but there is some pine. The pine is later renovations, not in the original house construction.&lt;br /&gt;&lt;br /&gt;Termites (white ants) don&#39;t like Jarrah, but they do eat it, slowly. They will look around for something better, and in my case it is the pine and the plasterboard. Interesting, there are some MDF moldings that they ate all around but did not chew at all.&lt;br /&gt;&lt;br /&gt;I have not called a pest exterminator, as I don&#39;t want to use chemicals. I don&#39;t like the whole philosophy of poisoning them. White ants perform an essential function in nature, especially where I live -- there are no worms in this arid soil, but a lot of white ants.&lt;br /&gt;&lt;br /&gt;After stripping the wall, I found where they are coming up, and they sure are clever. My house is on stumps, with metal plates separating house and stump. They built an earth &quot;bridge&quot; right around the protruding metal plate. The stump is on the edge of the house, but they built their earth &quot;bridge&quot; on the inside, and I only saw it after getting right down and looking underneath.&lt;br /&gt;&lt;br /&gt;Now, my understanding of white ants is that they need access to their nest in the ground. They also need access to underground water. So, if I replace the stump, that breaks their path to home, but my question is, what do those left behind in my house do?&lt;br /&gt;&lt;br /&gt;In mean, will they survive? I have stripped the wall, but they have made it up to the roof (not too far fortunately) and there are going to be quite a few that I won&#39;t be able to physically remove. &lt;br /&gt;&lt;br /&gt;I have remembered an old bush method, to paint the timber with sump oil, the older and dirtier the better. However this site says sump oil doesn&#39;t work, but sump oil mixed with creosote does:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.woodworkforums.com/f85/drywood-termites-treated-ply-10105/ target=_blank&gt;http://www.woodworkforums.com/f85/drywood-termites-treated-ply-10105/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...they mention &quot;flying white ants&quot; -- I&#39;ve had those coming into the house, but no apparent infestation from them -- perhaps they are not the same thing as those in Queensland.&lt;br /&gt;&lt;br /&gt;In a day or two I&#39;ll tackle rebuilding the stump. There are metal stumps available, that I have seen in Bunnings -- the base gets set in concrete I think.&lt;br /&gt;&lt;br /&gt;This page is a good read:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.greenpest.com.au/newsletter_february2009.html target=_blank&gt;http://www.greenpest.com.au/newsletter_february2009.html&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01377</link>
		<title>dir2pet, petspec scripts improved</title>
		<category>Woof</category>
		<description>I have improved these two scripts, to help developers with creating the most appropriate entries in each of the package database fields.&lt;br /&gt;&lt;br /&gt;These two scripts are in Woof, to be uploaded soon, but as they are of value to anyone using Puppy 4.3.1 or later, I have posted them on the forum:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=52033 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=52033&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01376</link>
		<title>JWM 464 with i18n patch</title>
		<category>Puppy</category>
		<description>I have been adopting shinobar&#39;s scripts that he developed for Japanese Puppy, with a view to making Woof (the &quot;Puppy builder&quot;) more international-friendly.&lt;br /&gt;&lt;br /&gt;Recently, shinobar has patched JWM, the window manager used in most puppies, for i18n support of the menu. Forum post:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=51847 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=51847&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have compiled this in Quirky:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/jwm2-464-patched_i18n-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/jwm2-464-patched_i18n-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Builders of other puppies could either compile it themselves, or use my PET package.&lt;br /&gt;&lt;br /&gt;Note, Quirky has a recent fribidi package and I had to hack the JWM source:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;jwm 464-patched-i18n (patched by shinobar)&lt;br /&gt;&lt;br /&gt;edit src/jwm.h:&lt;br /&gt;/*BK #     include &lt;fribidi/fribidi_char_sets_utf8.h&gt; replace with...*/&lt;br /&gt;#     include &lt;fribidi/fribidi-char-sets-list.h&gt;&lt;br /&gt;#     include &lt;fribidi/fribidi-char-sets.h&gt;&lt;br /&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --disable-confirm --enable-fribidi&lt;br /&gt;# make&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01375</link>
		<title>Woof uploaded, Jan. 31, 2010</title>
		<category>Woof</category>
		<description>Lots of little fixes to scripts: pmount, drive_all, rc.sysinit, init, xdelta_gui. As reported in recent blog posts.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01374</link>
		<title>Xdelta GUI fixed for FAT f.s.</title>
		<category>Woof</category>
		<description>It has been reported that the Xdelta GUI has a problem working with files on a FAT filesystem, as the &#39;:&#39; character is not supported.&lt;br /&gt;&lt;br /&gt;I have modified the script /usr/sbin/xdelta_gui to accept .delta files in either format:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;oldfile:newfile.delta&lt;br /&gt;oldfile___newfile.delta&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;And the default is that a .delta is generated in the format:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;oldfile___newfile.delta&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;That is, three underscores is the delimiter.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01373</link>
		<title>Pburn 3.1.8</title>
		<category>Quirky</category>
		<description>I have upgraded to zigbert&#39;s latest Pburn optical drive burner application.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01372</link>
		<title>Mplayer recompiled with ALSA enabled</title>
		<category>Quirky</category>
		<description>Due to a problem I was having with ALSA in Gnome-mplayer, I compiled &#39;mplayer&#39; to support oss only.&lt;br /&gt;&lt;br /&gt;However, I have modified the Gnome-mplayer package to default to using oss, and there doesn&#39;t seem any reason why the mplayer executable cannot be compiled to support both oss and alsa.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01371</link>
		<title>Pmount, drive_all scripts change</title>
		<category>Woof</category>
		<description>Shinobar modified these scripts, including internationalization, and these are in Woof, and in Quirky 006.&lt;br /&gt;&lt;br /&gt;However, there was one of his modifications that I did not apply, to mount iso9660 filesystems with &#39;iocharset=utf8&#39;.&lt;br /&gt;&lt;br /&gt;Shinobar has informed me that it is necessary to correctly mount CD/DVDs that have been created in Windows.&lt;br /&gt;&lt;br /&gt;Ok, I have implemented that change in the scripts. It will be in the next upload of Woof.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01370</link>
		<title>Fix detect multiple optical drives</title>
		<category>Woof</category>
		<description>I was testing Quirky 006 on one of my PCs that has two optical drives, a CD and a DVD drive. Gnome-mplayer defaults to playing a DVD at /dev/dvd, however I found that /dev/dvd was missing.&lt;br /&gt;&lt;br /&gt;/dev/dvd should get set at bootup, by the /etc/rc.d/rc.sysinit script, to point to the actual optical drive. I found that this automatic setting was failing sometimes when there are two (or more) optical drives.&lt;br /&gt;&lt;br /&gt;This is an ancient bug. I have fixed it in rc.sysinit, so it will be in the next upload of Woof.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01369</link>
		<title>pkeys boot param fix</title>
		<category>Woof</category>
		<description>Quirky 006 testers have reported that the &#39;pkeys&#39; boot parameter causes an error message at bootup.&lt;br /&gt;&lt;br /&gt;I found that the device node /dev/tty0 was missing from the initramfs, which caused &#39;loadkmap&#39; and &#39;loadfont&#39; utilities to fail. I also found that tty1 to tty4 were all the same minor device number, so I fixed that too.&lt;br /&gt;&lt;br /&gt;This was a Woof bug.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01368</link>
		<title>Busybox experiment</title>
		<category>Quirky</category>
		<description>I compiled version 1.16.0 and enabled almost everything. The &#39;busybox&#39; executable is now 628KB, compared with 427KB in recent puppies.&lt;br /&gt;&lt;br /&gt;Over the years I have incrementally replaced Busybox applets with the &quot;full&quot; versions, whenever I found the former to be inadequate.&lt;br /&gt;&lt;br /&gt;For Quirky 007 I have decided to experiment with rewinding back to using more of the Busybox applets. For the record, these are the packages that I have changed:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Cut down&lt;/b&gt;&lt;br /&gt;coreutils_cut, bc_cut&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Removed&lt;/b&gt;&lt;br /&gt;bzip2, cpio, diffutils, ed, eject, findutils, grep, gzip, hdparm, less, mktemp, net-tools, psmisc, sed, tar, time, unzip&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Left alone&lt;/b&gt;&lt;br /&gt;dosfstools, dpkg-deb, ifplugd, ifplugd_old, lzma, module-init-tools, ncurses, pciutils, procps, util-linux, wget.&lt;br /&gt;&lt;br /&gt;The packages that I have &quot;left alone&quot;, that is, left in Quirky, are those that I know or am pretty certain Busybox cannot adequately replace. Note though, I have left the Busybox applets enabled and they can be executed by &#39;busybox &lt;applet&gt;&#39; for comparison purposes.&lt;br /&gt;&lt;br /&gt;I created &#39;coreutils_cut&#39; PET package which is very cut down, with only three utilities (install, paste, pr).&lt;br /&gt;&lt;br /&gt;I know that we are going to find problems with this and will have to bring back some full utilities, but I&#39;m hoping that it won&#39;t be many.&lt;br /&gt;&lt;br /&gt;Then there&#39;s Bash... I know that there are some scripts written specifically for Bash.&lt;br /&gt;The &#39;bash&#39; executable is 498KB. Should I be a devil and take that out too? Create a script /bin/bash that just runs /bin/ash?&lt;br /&gt;&lt;br /&gt;...so tempting. But I know that doing all of this, especially the Bash thing, is going to cause trouble with compiling some packages. But then, this is Quirky...&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01367</link>
		<title>Leeman again</title>
		<category>General</category>
		<description>Right now it&#39;s 7am and I can already feel the heat. So, I&#39;m taking the day off, going to Leeman -- see my recent post about this nice seaside village:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01315 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01315&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;But, first, reading the latest posts on the forum. This post about Busybox from technosaurus has made me excited:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=51874 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=51874&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;It&#39;s great that I still get excited about things Puppy-related &lt;img src=smilies/happy.gif /&gt; &lt;br /&gt;&lt;br /&gt;Hah hah, but I have already decided to go to Leeman, so checking out the latest Busybox will have to wait. Tonight...&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01366</link>
		<title>Woof uploaded, January 28, 2010</title>
		<category>Woof</category>
		<description>These are the commit notes, since the last upload of Woof:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;ppm fixes, shinobar localized scripts remasterpup2 (bugfix), pmount, drive_all&lt;br /&gt;xwin: make sure xorg kbd layout same as console&lt;br /&gt;this version of Woof used to build Quirky 006&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;To learn more about Woof:&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01365</link>
		<title>Quirky 0.0.6 uploaded</title>
		<category>Quirky</category>
		<description>Brief announcement here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-006/quirky-006-readme.htm target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-006/quirky-006-readme.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Grab the ISO and &#39;zdrv&quot; from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-006/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-006/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...there are also xdelta files for upgrading from 005.&lt;br /&gt;&lt;br /&gt;Read my recent blog posts to find out what I have done since 005. As to what is planned for 007, well, I hope to get stuck into the problems with networking. There are some issues with Xorg on certain hardware and I hope to give that some attention also.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01364</link>
		<title>ext4 fixed</title>
		<category>Quirky</category>
		<description>Gparted did not work with ext4 in Quirky 005. Fixed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01363</link>
		<title>My XO-1 is getting redeployed</title>
		<category>Puppy</category>
		<description>I am not using my OLPC XO-1 and have no plans to do so, so I decided the best thing to do is pass it on to someone who can make good use of it.&lt;br /&gt;&lt;br /&gt;First, I asked the guy who gave it to me, forum member mdd (Mike), and he replied that he doesn&#39;t want it back and I&#39;m welcome to pass it on.&lt;br /&gt;&lt;br /&gt;Forum member sculver, who is a support volunteer for OLPC, gave me contact details of a guy who is a OLPC support volunteer in Australia (NSW), first name James.&lt;br /&gt;&lt;br /&gt;I contacted James and he replied that yes he can make use of it, either for testing or redeployment. The latter may involve it being sent to Haiti.&lt;br /&gt;&lt;br /&gt;So, I&#39;ll post it off today or tomorrow.&lt;br /&gt;&lt;br /&gt;Note to anyone interested in Puppy Linux running on the XO-1, see the forum: OLPC developer Mitch has succeeded, and sculver, ttuuxxx and others are assisting with solving further issues.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01362</link>
		<title>Pmusic 0.9.9.2</title>
		<category>Quirky</category>
		<description>I have upgraded to zigbert&#39;s latest. This will be in Quirky 006.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01361</link>
		<title>lameSMBxplorer 0.1.7b</title>
		<category>Quirky</category>
		<description>I have upgraded to Patriot&#39;s latest. This will be in Quirky 006.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01360</link>
		<title>Grub4dos 0.4.4v1.5.2</title>
		<category>Quirky</category>
		<description>I have upgraded to shinobar&#39;s latest version. This will be in Quirky 006.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01359</link>
		<title>Xorg and console keyboad layouts</title>
		<category>Woof</category>
		<description>I fixed a bug that has been in Puppy for a very long time, maybe always.&lt;br /&gt;&lt;br /&gt;When the Xorg Wizard is run, it looks at the console keyboard layout as specified in /etc/keymap and puts an appropriate value into this line in /etc/X11/xorg.conf:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;	Option      &quot;XkbLayout&quot; &quot;us&quot; #xkeymap0&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;That&#39;s fine, however if the Keyboard Wizard is used to change to a different layout, /etc/keymap gets changed and the console layout is updated, however the layout in xorg.conf is not changed.&lt;br /&gt;&lt;br /&gt;I have modified /usr/bin/xwin, which is the script that is used to start X, to check for a mismatch between console and Xorg keyboard layout and if found then fix it.&lt;br /&gt;&lt;br /&gt;Note, the same situation can occur if the &quot;pkeys&quot; kernel boot parameter is used to change the current setting in /etc/keymap. That is fixed also.&lt;br /&gt;&lt;br /&gt;This fix is in Woof, that I will upload soon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01358</link>
		<title>pmount, drive_all scripts</title>
		<category>Woof</category>
		<description>Shinobar posted upgrades for these scripts to the Quirky 005 feedback thread. They are /usr/sbin/pmount and /usr/local/bin/drive_all.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;pmount&lt;/b&gt;&lt;br /&gt;There was a report on the 005 feedback thread about the CD tray closing too quickly, that this should have fixed. Also it adds locale support.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;drive_all&lt;/b&gt;&lt;br /&gt;This is the original of the script that runs when a desktop drive icon is clicked on. Shinobar has made some improvements plus locale support. I had recently modified this script, so had to merge my recent changes with shinobar&#39;s script.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01357</link>
		<title>005 feedback, planning for 006</title>
		<category>Quirky</category>
		<description>Thanks guys for testing Quirky 005 and reporting back. I&#39;m working through the 005 forum feedback thread, fixing things. Of course some of these issues are generic to Woof and so apply to all future puppies built with Woof, not just Quirky-specific.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;PPM&lt;/b&gt;&lt;br /&gt;A couple of bug-fixes. One was changing the choice of repos. Another was &#39;sysfiles&#39; listed as a dependency of the &#39;mesa&#39; package.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Crypto modules&lt;/b&gt;&lt;br /&gt;As Quirky 005 is built with a cutdown selection of modules, this needs to be tweaked. Further work to be done here, but for now have added all the &quot;crypto&quot; modules, as some needed one may have been missing.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;remasterpup2&lt;/b&gt;&lt;br /&gt;Shinobar has updated this script, now at version &#39;100120&#39;. There was feedback of a missing value in one of the windows, that this should fix.&lt;br /&gt;I also put the &#39;ja&#39; locale file into Woof.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Planning for 006&lt;/b&gt;&lt;br /&gt;Apart from continuing to work through the 005 feedback, and upgrading some packages, the multimedia is getting another workover. I plan to build 006 with these changes:&lt;br /&gt;&lt;br /&gt;Added:&lt;br /&gt;&lt;i&gt;mplayer_dvd&lt;br /&gt;dbus&lt;br /&gt;dbus-glib&lt;br /&gt;gnome-mplayer&lt;br /&gt;gecko-mediaplayer&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Removed:&lt;br /&gt;&lt;i&gt;mplayerplug-in&lt;br /&gt;mplayer&lt;br /&gt;ogle&lt;br /&gt;ogle_gui&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Note, I created &#39;mplayer&#39; and &#39;mplayer_dvd&#39; packages. They are both Mplayer, but the latter has DVD playing support.&lt;br /&gt;&lt;br /&gt;Gecko-mediaplayer is a browser plugin and works with gnome-mplayer. They need Dbus to communicate.&lt;br /&gt;&lt;br /&gt;Note however, if we decide that gecko-mediaplayer doesn&#39;t quite cut it, we can go back to the mplayerplug-in browser plugin, which uses mplayer directly. ...if we did that, then gnome-mplayer does not really need dbus and in theory we could hack it to remove its dbus dependency.&lt;br /&gt;&lt;br /&gt;One good thing about mplayerplug-in, gnome-mplayer and gecko-mediaplayer is that they are all developed by the same guy, Kevin, who is very responsive to bug reports.&lt;br /&gt;&lt;br /&gt;I can tell you one good thing about gnome-mplayer -- the menu navigation in my DVDs now works. However, the mouse pointer becomes invisible, which makes selection a bit awkward.&lt;br /&gt;Also, there is a problem with switching between full-screen -- can switch to, but when switch back the playing stops and something goes wrong with sound -- have to click the sound icon to bring it back. These are issues that we can report to Kevin!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01356</link>
		<title>Woof uploaded, Jan. 26, 2010</title>
		<category>Woof</category>
		<description>This has the Manage System Services added to the BootManager (see previous blog post).&lt;br /&gt;&lt;br /&gt;Today is Australia Day!&lt;br /&gt;&lt;br /&gt;I went into town, a small group gathered for a couple of speeches, raising of the flag and we sang &quot;Advance Australia Fair&quot;. The whole thing took about 15 minutes!&lt;br /&gt;&lt;br /&gt;Australia Day originally commemorated the landing at Botany Bay (Sydney) by Captain Cook. Many Aboriginals think of it as &quot;invasion day&quot;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01355</link>
		<title>Manage System Services</title>
		<category>Woof</category>
		<description>The BootManager now manages the running of &quot;system services&quot; at bootup.&lt;br /&gt;&lt;br /&gt;The main window of BootManager now looks like this:&lt;br /&gt;&lt;img src=http://puppylinux.com/technical/bootmanager.png /&gt;&lt;br /&gt;&lt;br /&gt;The Manage System Services window:&lt;br /&gt;&lt;img src=http://puppylinux.com/technical/bootmanager-systemservices.png /&gt;&lt;br /&gt;&lt;br /&gt;The &#39;HELP&#39; button brings up this:&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;System services&lt;br /&gt;---------------&lt;br /&gt;&lt;br /&gt;&quot;daemon&quot;&lt;br /&gt;...this word is used below. It means an application that when executed, runs&lt;br /&gt;continually in the background.&lt;br /&gt;&lt;br /&gt;The scripts in /etc/init.d are executed at bootup and shutdown to start and stop&lt;br /&gt;services.&lt;br /&gt;&lt;br /&gt;At bootup, the /etc/rc.d/rc.services script will run all executable scripts&lt;br /&gt;found in /etc/init.d, with the commandline parameter &#39;start&#39;.&lt;br /&gt;At shutdown, the /etc/rc.d/rc.shutdown script will run all executable scripts&lt;br /&gt;found in /etc/init.d, with the commandline parameter &#39;stop&#39;.&lt;br /&gt;&lt;br /&gt;Puppies built from the Woof build system after January 26, 2010, have System&lt;br /&gt;Service Management provided in the BootManager (see Sysytem menu).&lt;br /&gt;This Services Manager controls which of these scripts will run by setting or&lt;br /&gt;clearing their &#39;executable&#39; flag -- a script flagged as executable will run,&lt;br /&gt;otherwise not.&lt;br /&gt;&lt;br /&gt;System Services Management&lt;br /&gt;--------------------------&lt;br /&gt;&lt;br /&gt;Most users do not normally need to disable any of the system services, however&lt;br /&gt;sometimes there might be a need. &lt;br /&gt;&lt;br /&gt;Each service uses CPU and memory resources, so with a slow CPU there may be&lt;br /&gt;some noticeable gain in not running services that are not needed.&lt;br /&gt;&lt;br /&gt;On rare occasions a service may cause trouble, so needs to be disabled.&lt;br /&gt;&lt;br /&gt;Here are some notes on particular services:&lt;br /&gt;&lt;br /&gt;cups&lt;br /&gt;----&lt;br /&gt;This runs the CUPS daemon &#39;dbusd&#39;, required for printing. Leave this enabled unless&lt;br /&gt;you don&#39;t need to print.&lt;br /&gt;&lt;br /&gt;messagebus&lt;br /&gt;----------&lt;br /&gt;Runs the daemon &#39;dbusd&#39;.&lt;br /&gt;DBUS is a method for applications to communicate with one another. Only certain&lt;br /&gt;applications use this, and most puppies are built with apps that don&#39;t.&lt;br /&gt;If &#39;messagebus&#39; script is present, it probably means some application is installed&lt;br /&gt;that needs DBUS. An example is &#39;gecko-mediaplayer&#39; (browser plugin) that uses DBUS&lt;br /&gt;to communicate with &#39;gnome-mplayer&#39; (multimedia player). So, unless you know&lt;br /&gt;that no apps require this, leave it enabled.&lt;br /&gt;&lt;br /&gt;rc.acpi&lt;br /&gt;-------&lt;br /&gt;Runs the daemon &#39;acpid&#39;.&lt;br /&gt;This is a daemon that provides certain ACPI management functions. Puppy will&lt;br /&gt;still work without it.&lt;br /&gt;&lt;br /&gt;rc.firewall&lt;br /&gt;-----------&lt;br /&gt;In most puppies this scipt is actually located at /etc/rc.d. If you have Internet&lt;br /&gt;access then this is essential to provide protection. It doesn&#39;t actually launch&lt;br /&gt;any daemon, only loads kernel modules, so runtime resource usage is low. &lt;br /&gt;The only time that you might want to disable it is when testing the Internet&lt;br /&gt;connection.&lt;br /&gt;&lt;br /&gt;slmodem&lt;br /&gt;-------&lt;br /&gt;Runs the daemon &#39;slmodemd&#39;.&lt;br /&gt;This provides support for some analog dialup modems. There are reports that&lt;br /&gt;this can conflict with sound on some PCs, so if you don&#39;t use an analog modem&lt;br /&gt;for Internet access, or a different modem driver, consider disabling this.&lt;br /&gt;&lt;br /&gt;sys_logger&lt;br /&gt;----------&lt;br /&gt;This runs the daemons &#39;syslogd&#39; and &#39;klogd&#39;, which log kernel and application&lt;br /&gt;events (espcially error messages) to various log files, mostly to &lt;br /&gt;/var/log/messages. This can be disabled and Puppy will still work.&lt;br /&gt;&lt;br /&gt;udev&lt;br /&gt;----&lt;br /&gt;Runs the daemons &#39;udevd&#39; and &#39;pup_event_frontend_d&#39;.&lt;br /&gt;This is a mechanism that receives information about hardware events from the kernel,&lt;br /&gt;such as a USB pen drive being plugged in or removed. If you don&#39;t want automatic&lt;br /&gt;detection of hardware changes while Puppy is running, Puppy will still work&lt;br /&gt;and you will save quite a lot of CPU usage and resources -- worth considering&lt;br /&gt;this one on a very slow CPU.&lt;br /&gt;This one is different from those listed above, as &#39;udevd&#39; is essential during&lt;br /&gt;bootup. However, it can be killed after bootup -- it involves the daemon &#39;udevd&#39;&lt;br /&gt;and the daemon &#39;pup_event_frontend_d&#39; and if disabled these two are killed when&lt;br /&gt;X is started. The technical description is that when X starts, /root/.xinitrc&lt;br /&gt;runs, which launches /sbin/pup_event_frontend_d -- look in that latter script&lt;br /&gt;and you will see that it reads /etc/eventmanager which has a variable &#39;BACKENDON&#39;&lt;br /&gt;that can be set to kill udevd and pup_event_frontend_d.&lt;br /&gt;There is a GUI manager for this, the EventManager (see System menu), and changing&lt;br /&gt;the &#39;udev&#39; checkbox will cause the EventManager to run.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Technical notes&lt;br /&gt;---------------&lt;br /&gt;&lt;br /&gt;At startup, the system services are executed by /etc/rc.d/rc.services, which&lt;br /&gt;in turn is called from /etc/rc.d/rc.sysinit.&lt;br /&gt;&lt;br /&gt;At shutdown, the system servcies are executed (with the &#39;stop&#39; parameter) by&lt;br /&gt;/etc/rc.d/rc.shutdown.&lt;br /&gt;&lt;br /&gt;Puppy does not have runlevels (basically because Busybox doesn&#39;t, at least that&lt;br /&gt;was the original reason). Normal Linux distros would have a list of services to&lt;br /&gt;start for each runlevel, but apart from not having runlevels Puppy also only&lt;br /&gt;runs a very minimum essential set of services, that most users would not want&lt;br /&gt;to tamper with.&lt;br /&gt;&lt;br /&gt;Note that /etc/rc.d/init.d is a symlink to /etc/init.d&lt;br /&gt;&lt;br /&gt;Note, the scripts in /etc/init.d can have any name, but must have their executable&lt;br /&gt;flag set. Any file that does not have the &#39;x&#39; flag set will be ignored.&lt;br /&gt;&lt;br /&gt;Event Management, which is mostly concerned with hardware-related detection and&lt;br /&gt;configuration while X is running, is described in more detail on this web page:&lt;br /&gt;&lt;br /&gt;http://puppylinux.com/technical/event-management.htm&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;Barry Kauler&lt;br /&gt;Jan. 2010&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;The script is /usr/sbin/bootmanager. I also modified /etc/rc.d/rc.sysinit -- syslogd and klogd are no longer started in that script, instead in /etc/init.d/00sys_logger.&lt;br /&gt;&lt;br /&gt;Management of &quot;udev&quot; is more involved. The &#39;udevd&#39; daemon must run at startup, but can be killed later. If the &#39;udev&#39; checkbox is changed, the Puppy EventManager is launched, which provides the GUI for enablng and disabling udev.&lt;br /&gt;&lt;br /&gt;The Manage System Services window can be brought up directly from the commandline by this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# bootmanager sysdaemons&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;This is implemented in Woof, that I will upload soon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01354</link>
		<title>US Money Order problem</title>
		<category>Puppy</category>
		<description>Today I received a donation of US 20 Dollars, in the form of a US Postal Money Order.&lt;br /&gt;&lt;br /&gt;Unfortunately, I cannot cash this. The postmistress at Perenjori made a telephone enquiry to find out if there is some way to cash it, but there isn&#39;t. &lt;br /&gt;&lt;br /&gt;Hmmm, the fact that it has &quot;negotiable only in the U.S. and possessions&quot; printed on it is a hint!&lt;br /&gt;&lt;br /&gt;The person who sent this has only identified themselves as:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Puppy Linux User&lt;br /&gt;Hawthorne&lt;br /&gt;California, USA&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...if you are that person, please contact me so that I can return the money order. Or, if you think that you know who that person is, please pass on this message.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01353</link>
		<title>Gecko review</title>
		<category>Puppy</category>
		<description>I have posted to my blog recently about the Gecko Edubook:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=00771 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=00771&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01341 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01341&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01346 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01346&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Now, forum member judland (David) has posted a review:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.ipernity.com/blog/virtualsky/223038 target=_blank&gt;http://www.ipernity.com/blog/virtualsky/223038&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Here are some performance criticisms from the review:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;About the only thing the Edubook falls short on is in its multi-media / video playback capabilities. Although YouTube videos an MP4s do play, they are very choppy and out of sync with the audio track.&lt;br /&gt;&lt;br /&gt;However, there is one saving grace; Puppy Linux come installed with a YouTube video downloader and format converter. If you download the YouTube video you wish to watch and convert it to a lower resolution MPEG, the video plays just fine. Same with MP4s you may have ripped from you DVDs.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;and...&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Now for the biggest beef I have against the Edubook... the mouse-pad. In my opinion, this mouse-pad is far too sensitive to the touch. I don&#39;t even need to be touching the mouse-pad for the mouse pointer to start jumping all over the screen. If I leave a finger resting on one of the mouse buttons, the pad picks it up. If, while typing, my palm comes too close to the surface of the mouse-pad, it registers as a mouse-click. Very annoying.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I wonder if things can be tweaked so that videos can be made to play smoothly when streamed from youtube.com?&lt;br /&gt;&lt;br /&gt;It is most likely possible to fix that mouse pad sensitivity problem.&lt;br /&gt;&lt;br /&gt;...I look forward to working on these issues when I get my Gecko! And of course I&#39;ll post my own mini-review.&lt;br /&gt;&lt;br /&gt;There is a comment about a signature needed for credit card payment, yes I had to do that too. It&#39;s a bank in Thailand that requires that. I think the alternative is a Western Union transfer.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01352</link>
		<title>Mplayerplug-in fixed</title>
		<category>Puppy</category>
		<description>As reported recently, The Mplayer browser plugin used in Quirky 005 crashes with some .ram files. After discussion with the developer Kevin, we determined that it is due to the .ram file being a single line of text without a trailing carriage-return character. But kevin pointed out that his code does test for that condition.&lt;br /&gt;&lt;br /&gt;Rather than hand it over to Kevin to fix, I decided to tackle it. I found the appropriate file, and where it was crashing. I fixed it.&lt;br /&gt;&lt;br /&gt;I have posted the fix to the Mplayerplug-in maillist, also have uploaded the patched source here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/m/mplayerplug-in-20100117-patched.tar.gz target=_blank&gt;http://bkhome.org/sources/alphabetical/m/mplayerplug-in-20100117-patched.tar.gz&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01351</link>
		<title>Universal source code highlighter</title>
		<category>Puppy</category>
		<description>Forum member droope sent me a pm about this forum thread posted by Dingo:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=51674 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=51674&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The product is called Highlight and I found the home   page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.andre-simon.de/ target=_blank&gt;http://www.andre-simon.de/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Highlight supports these languages:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.andre-simon.de/doku/highlight/en/highlight_langs.html target=_blank&gt;http://www.andre-simon.de/doku/highlight/en/highlight_langs.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...Vala, but not Genie.&lt;br /&gt;&lt;br /&gt;Droope was prompted to send me the pm as I had once requested such an export feature be added to Nicoedit (color highlighting exported to HTML) -- but that never happened.&lt;br /&gt;&lt;br /&gt;I really want Genie, so still waiting. I see in the news page for Highlight that two languages have been added recently, so the author would probably be responsive to a request for Genie.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01350</link>
		<title>Flashblock for SeaMonkey</title>
		<category>Quirky</category>
		<description>I have been playing with Quirky 005, thinking how to enhance the multimedia control. Recently when I used dialup I was reminded how slow some pages load, so I have installed Flashblock as one more thing to control page content.&lt;br /&gt;&lt;br /&gt;I have made it into a PET package and intend that it will be in the next build of Quirky.&lt;br /&gt;&lt;br /&gt;SeaMonkey in Quirky 005 already has these addons:&lt;br /&gt;&lt;br /&gt;adblock&lt;br /&gt;user-agent-switcher&lt;br /&gt;zombie-keys&lt;br /&gt;&lt;br /&gt;Adblock is off by default, as probably most people will find it annoying, however I have left Flashblock on by default. Flashblock can be disabled on a per-page, per-site or totally basis.&lt;br /&gt;&lt;br /&gt;Flashblock home:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://flashblock.mozdev.org/ target=_blank&gt;http://flashblock.mozdev.org/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01349</link>
		<title>Woof uploaded, January 20, 2010</title>
		<category>Woof</category>
		<description>This is the Woof version that has been used to build Quirky 005.&lt;br /&gt;&lt;br /&gt;I have also updated the Quirky PET packages at ibiblio.org.&lt;br /&gt;&lt;br /&gt;Further information on Woof:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01348</link>
		<title>Quirky 0.0.5 uploaded</title>
		<category>Quirky</category>
		<description>Brief intro to &quot;multimedia special&quot;:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-005/quirky-005-readme.htm target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-005/quirky-005-readme.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Download from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-005/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-005/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The ISO is 92.4MB.&lt;br /&gt;&lt;br /&gt;I have put in pizzasgood&#39;s latest Retrovol tray volume control and sound mixer.&lt;br /&gt;&lt;br /&gt;Note that the boot prompt has reverted to &quot;puppy&quot; prefix instead of &quot;quirky&quot;, for example &quot;puppy pfix=ram&quot;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01347</link>
		<title>Cpu-scaling-ondemand</title>
		<category>Quirky</category>
		<description>Forum member trio has updated to version 1.3-2:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=45143 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=45143&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Quirky 005 will have this.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01346</link>
		<title>Gecko orders</title>
		<category>General</category>
		<description>I have just placed an order for two Gecko Edubooks. The manager Michael Barnes has offered one for free, but I am buying a second unit also.&lt;br /&gt;&lt;br /&gt;I won&#39;t be keeping the second, I&#39;ll be donating it to a charity organization in India. A member of an NGO in India, someone I know, will be visiting Perth soon, and I&#39;ll give the laptop to her. Hopefully it will arrive in time.&lt;br /&gt;&lt;br /&gt;So, it&#39;s kind of like the OLPC scheme where you buy one, and one goes to a third world country &lt;img src=smilies/happy.gif /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01345</link>
		<title>Quirky &quot;multimedia special&quot; coming</title>
		<category>Quirky</category>
		<description>I have built a Quirky that &quot;plays everything&quot;, which will be uploaded as 005, real soon.&lt;br /&gt;&lt;br /&gt;I explored radical options in Quirky 003, using Swfdec as the Flash browser plugin, &#39;ffplay&#39; as the media player, mozplugger to launch appropriate players for embedded browser audio or video, and Ogle to play DVD movies.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Ffmpeg&lt;/b&gt;&lt;br /&gt;Yesterday I started again, from scratch. I got ffmpeg out of version-control, dated 2010-01-16. I compiled dependencies opencore-amr 0.1.2 and x264 20091230.&lt;br /&gt;&lt;br /&gt;I then went the usual route, compiled xine-lib and gxine, but it was disappointing, some test files did not play properly.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Mplayer&lt;/b&gt;&lt;br /&gt;So, I got mplayer out of version-control, dated 2010-01-17, and went through a very tortured process of getting it to compile, with the external ffmpeg dependency. I patched the source, and I will upload &#39;mplayer-2010-01-17-patched.tar.gz&#39; to my source repo soon -- it also has a special script to do the final link step that builds the &#39;mplayer&#39; executable. I have also left the source pre-configured so you just type &#39;make&#39; to compile.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Mplayerplug-in&lt;/b&gt;&lt;br /&gt;I compiled mplayerplug-in 20100117 to handle browser embedded content.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Adobe Flash Player&lt;/b&gt;&lt;br /&gt;To top it all off, I put in the official Adobe Flash browser plugin, version 9.0.124.0 (more stable than the 9.0.48.0 used in Puppy 431).&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Ogle&lt;/b&gt;&lt;br /&gt;I built mplayer without DVD playing capability, as I have never been able to get that working right (mplayer can still play VCDs). I have left in Ogle specifically to fill that gap.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Conclusion&lt;/b&gt;&lt;br /&gt;The end result is quite remarkable. This combo plays everything I have thrown at it, and plays everything properly. I&#39;ve got a Lindows RealMedia video that played with garbled sound, now plays nicely. The &#39;sunrise.wmv&#39; that I had trouble with gaps in the sound, now no gaps.&lt;br /&gt;&lt;br /&gt;Beautiful! the iso is 91MB.&lt;br /&gt;&lt;br /&gt;Note, one little hiccup is that with some files, mplayer displays an error window that a certain codec is missing, yet the video plays ok. What is happening is that mplayer is thinking a certain codec is required, however ffmpeg has the video and audio capability to play it. I would like to figure out how to suppress that error message window.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01344</link>
		<title>Little fix for CD remaster script</title>
		<category>Woof</category>
		<description>Forum member npierce sent me a pm about a problem with the CD remaster script. There is a problem with the &#39;globicons&#39; file, if the use has made any changes to the desktop icons. This file is stored in two places, and the one that has preference does not get saved by the remaster script. Fixed. I also added saving of the rox &#39;Options&#39; file.&lt;br /&gt;&lt;br /&gt;The script is /usr/sbin/remasterpup2.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01343</link>
		<title>Audio/video test site</title>
		<category>Puppy</category>
		<description>Forum member coolpup often pm&#39;s me with useful information, such as notification of a new package version or a useful link. Like this one:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html target=_blank&gt;http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;That&#39;s very good. I&#39;m just about to get back onto developing the multimedia in Quirky and of course want to do lots of testing.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01342</link>
		<title>One-file Quirky for OLPC XO-1</title>
		<category>Quirky</category>
		<description>Well, an attempt anyway. Here it is:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/test/vmlinuz-16JAN2010-GEODE-OLPC.t01 target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/test/vmlinuz-16JAN2010-GEODE-OLPC.t01&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This is a &#39;vmlinuz&#39; Linux kernel with everything embedded in it. It is 81.74MB.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01341</link>
		<title>Xcore86 CPU in Gecko Edubook</title>
		<category>Puppy</category>
		<description>I have been tracking down technical details on the Xcore86 CPU used the the Gecko Edubook laptops. The website for the Xcore86:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.xcore86.com/ target=_blank&gt;http://www.xcore86.com/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;However that site is severely lacking in technical detail. However, I discovered from this wikipedia page that the Xcore86 is a rebadged Vortex86:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://en.wikipedia.org/wiki/Vortex86 target=_blank&gt;http://en.wikipedia.org/wiki/Vortex86&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The Gecko uses a Vortex86MX chip, and there is a PDF technical specifications file:&lt;br /&gt;&lt;br /&gt;&lt;a href=ftp://download@ftp.dmp.com.tw/vortex86dx/Vortex86DX_V0.9A_Brief.pdf target=_blank&gt;ftp://download@ftp.dmp.com.tw/vortex86dx/Vortex86DX_V0.9A_Brief.pdf&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...well, that is for the &quot;DX&quot; model, which apparently has the same CPU core. Um, need to do better than that, ok, the pmx-1000 is the consumer-grade version of the Vortex86MX and here is a technical specification file:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.vortex86mx.com/wp-content/uploads/2009/03/PMX-1000_V10_Brief.pdf target=_blank&gt;http://www.vortex86mx.com/wp-content/uploads/2009/03/PMX-1000_V10_Brief.pdf&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...no, that one is &lt;i&gt;very&lt;/i&gt; brief, hardly any information.&lt;br /&gt;&lt;br /&gt;Anyway, what I can glean from the &quot;DX&quot; specs, the CPU core is a equivalent to a 486SX CPU, plus FPU (maths processor) and GPU (graphics processor) plus lots of other things are on the chip.&lt;br /&gt;&lt;br /&gt;The chip is actually manufactured by DMP Electronics in Taiwan:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://dmp.com.tw/ target=_blank&gt;http://dmp.com.tw/&lt;/a&gt;&lt;br /&gt;&lt;a href=http://www.vortex86mx.com/ target=_blank&gt;http://www.vortex86mx.com/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The 486 CPU does not have the MMX instructions, nor the MTRR registers. The kernels that we compile for Puppy are for the &quot;i486&quot;, which basically means &quot;486sx + FPU&quot;. One thing that is enabled in the kernel config is support for MTRRs, but I have done some research on this and apparently it doesn&#39;t matter, the kernel will still work on a CPU that does not have the MTRR registers.&lt;br /&gt;&lt;br /&gt;There is a question mark over Xorg and whether it needs the MTRRs. I&#39;ll have to check, perhaps that is also configurable prior to compiling the Xorg servers.&lt;br /&gt;&lt;br /&gt;There may be some multimedia apps used in Puppy that are configured to expect the MMX instructions, or even some more advanced architectures such as SSE and SSE2. It will be necessary to check when configuring those apps prior to compiling that if these features are enabled, the app can still work if they aren&#39;t there.&lt;br /&gt;&lt;br /&gt;Anyway, overall conclusion is that the CPU used in the Gecko Edubook is Puppy-compatible, but we will need to be mindful that it lacks MTRR, MMX, SSE, SSE2 when configuring some applications prior to compiling.&lt;br /&gt;&lt;br /&gt;Now to confuse the issue... quoting from this site:&lt;br /&gt;&lt;a href=http://hkampar.moh.gov.my/modules/news/article.php?storyid=31 target=_blank&gt;http://hkampar.moh.gov.my/modules/news/article.php?storyid=31&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;i&gt;The Xcore86 (also known as the PMX 1000) is x586 based System on Chip (SoC) that offers a less than average thermal envelope of the Atom. The Xcore86 uses a x586 core, MMX compatible extensions, Video Core and r6040 Lan on Chip from RDC, HD sound core from Realtek and electronic integration from DMP.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...huh, &quot;MMX compatible extensions&quot;? Why isn&#39;t that in any of the official docs?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01340</link>
		<title>Creating one-file Quirky for XO-1</title>
		<category>Quirky</category>
		<description>I looked through the kernel .config file that mavrothal posted on the forum. I didn&#39;t follow it exactly, so there is some element of gamble here, but anyway I have now created a one-file Quirky with kernel configured for the Geode LX CPU and (hopefully) the OLPC XO-1.&lt;br /&gt;&lt;br /&gt;I&#39;m building it now and will announce when it is uploaded.&lt;br /&gt;&lt;br /&gt;For the XO-1.5, I would need to get a kernel .config file (ideally for the 2.6.31.x kernel) to see what differences there are. probably there are some hardware differences, apart from the CPU.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01339</link>
		<title>Another &#39;vmlinuz&#39; for OLPC test</title>
		<category>Quirky</category>
		<description>I recompiled the one-file Quirky, this time I configured the kernel for the Geode GX1 CPU. &lt;br /&gt;&lt;br /&gt;Download here:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/test/vmlinuz-15JAN2010.t00 target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/test/vmlinuz-15JAN2010.t00&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Note, I also turned off MTRR register support in the kernel, as I don&#39;t know if the Geode GX1 has those registers. I think that Xorg needs those registers.&lt;br /&gt;Anyway, see if this boots, and I can do another compile with MTRR enabled.&lt;br /&gt;&lt;br /&gt;I had a quick look at Geode specs, I see that the GX1 doesn&#39;t even have the MMX instructions, but the GX2 does. If I recall rightly, even the i486 has MMX instructions.&lt;br /&gt;I think that some applications compiled for a i486 are not going to work with a Geode GX1.&lt;br /&gt;&lt;br /&gt;I don&#39;t know whether the first XO&#39;s have a GX1 or GX2, hopefully not the former.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01338</link>
		<title>Notes on booting Quirky on OLPC</title>
		<category>Quirky</category>
		<description>Continuation from previous blog post, about the single-file Quirky:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01337 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01337&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;My OLPC laptop doesn&#39;t work. It has been sitting in its original box, with original packing, since 2008, unused. This is my blog report back then when I tested it:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.puppylinux.com/news/news400a5-400a7.htm target=_blank&gt;http://www.puppylinux.com/news/news400a5-400a7.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The battery would be discharged after such a long time. I have the power adaptor connected, I get the orange battery light. If I press the power button, the green power-on lights up, but the screen remains black. I thought maybe I needed to wait awhile for the battery to charge, but after one hour, still no-go.&lt;br /&gt;&lt;br /&gt;Anyway, I have been reading-up on booting. A good reference:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://wiki.laptop.org/go/Olpc.fth target=_blank&gt;http://wiki.laptop.org/go/Olpc.fth&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...I don&#39;t know how much of that applies to my early-model XO.&lt;br /&gt;&lt;br /&gt;Anyway, it seems pretty straightforward. If you have a normal bootable USB Flash drive, with one partition, say 1GB drive, fat16 filesystem. Perhaps play safe and use a small Flash drive of 1GB and fat16.&lt;br /&gt;&lt;br /&gt;On the Flash drive, place my Quirky file, &#39;quir004.t00&#39;, rename it to &#39;vmlinuz&#39; -- no particular reason, just playing safe, use a &quot;normal&quot; name for the kernel.&lt;br /&gt;&lt;br /&gt;Create a file /boot/olpc.fth on the Flash drive, with this in it:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;unfreeze&lt;br /&gt;boot u:\vmlinuz root=sda1 pmedia=usbflash&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...docs indicate the &quot;root=sda1&quot; is required, it would be interesting to see if it worked without that parameter.&lt;br /&gt;&lt;br /&gt;If booting from a SD card:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;unfreeze&lt;br /&gt;boot sd:\vmlinuz root=mmcblk0p1&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;The above is theoretical, as I can&#39;t test it myself!&lt;br /&gt;&lt;br /&gt;Clock battery&lt;br /&gt;Read this about the clock battery in the OLPC. Maybe mine is dead.&lt;br /&gt;&lt;a href=http://en.forum.laptop.org/viewtopic.php?f=1324&amp;t=164934 target=_blank&gt;http://en.forum.laptop.org/viewtopic.php?f=1324&amp;t=164934&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01337</link>
		<title>Test single-file Quirky</title>
		<category>Quirky</category>
		<description>As I have previously announced, also on the Quirky home page, Woof can build a distro which is just one file, the Linux kernel, with absolutely everything inside it to boot to the desktop. No access to any drives required -- if you can get the kernel to start booting, that&#39;s it, you should get a desktop.&lt;br /&gt;&lt;br /&gt;The single-file Quirky has some issues that I still need to sort out, but Raffy and others involved in getting Puppy to boot on the OLPC have asked about trying this. So here it is.&lt;br /&gt;&lt;br /&gt;Readme file:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/test/quirky004-readme.htm target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/test/quirky004-readme.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Download live-CD: &lt;b&gt;URL CORRECTION:&lt;/b&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/test/quirky-004-t00.iso target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/test/quirky-004-t00.iso&lt;/a&gt;&lt;br /&gt;...you can easily mount this and extract the kernel file.&lt;br /&gt;&lt;br /&gt;Md5sum:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/test/md5sums.txt target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/test/md5sums.txt&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Quirky home page:&lt;br /&gt;&lt;a href=http://bkhome.org/quirky/ target=_blank&gt;http://bkhome.org/quirky/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The ISO is 92MB, a bit big as I have included all the modules. &lt;br /&gt;&lt;br /&gt;Note that any Puppy built with Woof can be built this way, it is not just a Quirky thing. It does require an appropriate .config file for the kernel source, and currently only the 2.6.31.5 kernel PET package has that (it&#39;s on the ibiblio.org Quirky repository).&lt;br /&gt;&lt;br /&gt;&lt;b&gt;URGENT:&lt;/b&gt;&lt;br /&gt;I uploaded the wrong iso. Sorry, it was late, I was tired and my attention lapsed. Uploading the correct iso now. Will post when it&#39;s done.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;CORRECTION:&lt;/b&gt;&lt;br /&gt;The correct iso has now been uploaded, see above. Note, the ftp connection broke halfway through uploading, and I had to resume, so check the md5sum.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01336</link>
		<title>Woof uploaded, January 13, 2010 (again)</title>
		<category>Woof</category>
		<description>&lt;b&gt;Full hd install fixed!&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;Testers of Quirky 003 and earlier have reported that a full hard drive installation is broken. In fact, building any puppy, Dpup, Upup, or whatever, the full hd install is broken.&lt;br /&gt;&lt;br /&gt;The reason for this is recent optimizations that I made in Woof, in which files in the initrd are not duplicated in the main f.s.:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01294 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01294&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01218 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01218&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...full hd install would have been partly broken right back in late November 2009.&lt;br /&gt;&lt;br /&gt;So, as there are lots of people who like doing a full hd install, I have immediately uploaded the fix. For information about Woof and how to download, see here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Note, the script that I fixed is /usr/sbin/puppyinstaller.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01335</link>
		<title>Nouveau merging in 2.6.33 kernel</title>
		<category>Puppy</category>
		<description>I tested the nouveau Xorg driver on my PC with Nvidia 6600 GT card, but no-go. I reported recently on how I compiled it:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01332 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01332&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The good news is that the nouveau kernel driver will be merging in the 2.6.33 kernel, which hopefully should greatly improve the nouveau Xorg driver. The news about this is here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://lwn.net/Articles/366648/ target=_blank&gt;http://lwn.net/Articles/366648/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...I wouldn&#39;t hold my breath though, I don&#39;t think the Xorg nouveau driver is likely to suddenly become really great.&lt;br /&gt;&lt;br /&gt;Some useful links for developers:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://nouveau.freedesktop.org/wiki/InstallNouveau target=_blank&gt;http://nouveau.freedesktop.org/wiki/InstallNouveau&lt;/a&gt;&lt;br /&gt;&lt;a href=http://nouveau.freedesktop.org/wiki/InstallDRM target=_blank&gt;http://nouveau.freedesktop.org/wiki/InstallDRM&lt;/a&gt;&lt;br /&gt;&lt;a href=http://people.freedesktop.org/~pq/nouveau-drm/ target=_blank&gt;http://people.freedesktop.org/~pq/nouveau-drm/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01334</link>
		<title>Woof uploaded, January 13, 2010</title>
		<category>Woof</category>
		<description>Commits file comments:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;ppm fix install t2 .tar.bz2 pkgs, fix xorgwizard when choose generic vesa, quirky: xorg-server, xf86-video-nv upgrades&lt;br /&gt;xorgwizard: alternate driver selection, libdrm,nv,nouveau: xorg drivers in quirky&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Details in recent blog posts.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01333</link>
		<title>Xorg Wizard enhanced</title>
		<category>Woof</category>
		<description>I have made a significant improvement to the Xorg Wizard, script /usr/sbin/xorgwizard.&lt;br /&gt;&lt;br /&gt;Often there are alternative drivers to choose from, for example:&lt;br /&gt;&lt;br /&gt;intel i810 vesa&lt;br /&gt;nv nouveau vesa&lt;br /&gt;ati radeon vesa&lt;br /&gt;&lt;br /&gt;I have setup a mechanism for easy switching between these alternatives. Directory /usr/lib/xorg/modules/drivers-alternate is where unused drivers are kept. I have put the old i810 driver (from Xorg 7.2) and the nouveau driver in there. &lt;br /&gt;&lt;br /&gt;For Intel video hardware, you can test the intel and/or vesa drivers, but there is now an option to swap-in the i810 and swap-out the intel driver, then re-probe.&lt;br /&gt;&lt;br /&gt;Ditto for nv and nouveau. They can be swapped, so that when Xorg probes it only sees one of them.&lt;br /&gt;&lt;br /&gt;It was very easy on my laptop, with Intel hardware, to test each of the vesa, intel and i810 drivers. I have not yet built a Quirky CD and tried it on my daughter&#39;s old PC (which has an Nvidia 6600 GT card).&lt;br /&gt;&lt;br /&gt;I&#39;ll upload Woof soon with this improvement.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01332</link>
		<title>Compiling Xorg Nouveau driver</title>
		<category>Quirky</category>
		<description>This has turned up some interesting stuff. I got xf86-video-nouveau from git, dated 2010-01-12.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;util-macros&lt;/b&gt;&lt;br /&gt;I had trouble configuring, then found that this package is required. I have installed version 1.4.1. I&#39;ll make sure that this is in the Quirky &#39;devx&#39;.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;aclocal&lt;/b&gt;&lt;br /&gt;When I ran &#39;autogen.sh&#39;, to generate the &#39;configure&#39; script, there was an error:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;./configure: line 10956: syntax error near unexpected token `RANDR,&#39;&lt;br /&gt;./configure: line 10956: `XORG_DRIVER_CHECK_EXT(RANDR, randrproto)&#39;&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I found the reason here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://nouveau.freedesktop.org/wiki/FAQ#head-6f41727cc579ed3d7f42d67328466e2acbda9fc4 target=_blank&gt;http://nouveau.freedesktop.org/wiki/FAQ#head-6f41727cc579ed3d7f42d67328466e2acbda9fc4&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I created a file /usr/share/aclocal/dirlist, with this in it:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;/usr/X11R7/share/aclocal&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have put this fix into the &#39;rootfs-skeleton&#39; in Woof.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;libdrm_nouveau&lt;/b&gt;&lt;br /&gt;autogen.sh still gave an error:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;checking for LIBDRM_NOUVEAU... configure: error: Package requirements (libdrm_nouveau) were not met:&lt;br /&gt;No package &#39;libdrm_nouveau&#39; found&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...this is supposed to be part of package &#39;libdrm&#39;, that I do have installed. Hmmm. Ok, I am compiling libdrm, version 2.4.17 (the latest, 20 dec 2009):&lt;br /&gt;&lt;br /&gt;&lt;b&gt;UPDATE 13Jan2010: need CFLAGS to make it compile libdrm_intel:&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# &lt;b&gt;CFLAGS=&quot;-march=i486&quot;&lt;/b&gt; ./configure --prefix=/usr/X11R7 --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --enable-nouveau-experimental-api --enable-radeon-experimental-api --with-kernel-source=/usr/src/linux-2.6.31.5 &lt;b&gt;--enable-intel&lt;/b&gt; &lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;xf86-video-nouveau 2010-01-12&lt;/b&gt;&lt;br /&gt;We should be good to go now:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# ./autogen.sh&lt;br /&gt;# ./configure --prefix=/usr/X11R7 --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu&lt;br /&gt;# make&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;oh crap...&lt;br /&gt;&lt;i&gt;nv_accel_common.c: In function &#39;NVAccelInit2D_NV50&#39;:&lt;br /&gt;nv_accel_common.c:470: error: &#39;NV50_2D_CLIP_ENABLE&#39; undeclared&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...I looked in an older version of xf86-video-nouveau and the actual numeric value is used, which I have substituted. It looks like the developers have some extra header file that I don&#39;t have.&lt;br /&gt;&lt;br /&gt;But then it stops again, more undefined symbols. These symbols are undefined anywhere, can&#39;t find them by googling either:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;nv10_exa.c: In function &#39;setup_combiners&#39;:&lt;br /&gt;nv10_exa.c:493: error: &#39;NV10TCL_RC_IN_RGB_A_INPUT_TEXTURE0&#39; undeclared (first use in this function)&lt;br /&gt;nv10_exa.c:493: error: (Each undeclared identifier is reported only once&lt;br /&gt;nv10_exa.c:493: error: for each function it appears in.)&lt;br /&gt;nv10_exa.c:495: error: &#39;NV10TCL_RC_IN_RGB_A_MAPPING_UNSIGNED_INVERT&#39; undeclared (first use in this function)&lt;br /&gt;nv10_exa.c:498: error: &#39;NV10TCL_RC_IN_RGB_B_INPUT_TEXTURE1&#39; undeclared (first use in this function)&lt;br /&gt;nv10_exa.c:500: error: &#39;NV10TCL_RC_IN_RGB_B_MAPPING_UNSIGNED_INVERT&#39; undeclared (first use in this function)&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;The file &#39;nv10_exa.c&#39; has had a lot of work done on it recently. So, it&#39;s another case of the developers having the definitions of those symbols, but not me.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Finally...&lt;/b&gt;&lt;br /&gt;Oh, man, it took me awhile. I tried several different versions of xf86-video-nouveau. I got some courtesy of the Arch guys:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://mirror.leaseweb.com/archlinux/other/xf86-video-nouveau/ target=_blank&gt;http://mirror.leaseweb.com/archlinux/other/xf86-video-nouveau/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I tried most of them, got different errors. Finally, I tried &#39;xf86-video-nouveau-20091221.tar.bz2&#39; and finally, it compiled. Yippee. It has to be the right versions of everything, and I finally got it. My guess is that libdrm is being developed in-step, so you must have the right version of libdrm.&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01331</link>
		<title>Xorg server, nv, updated</title>
		<category>Quirky</category>
		<description>I decided to update the &#39;xorg-server&#39; and &#39;xf86-video-nv&#39; packages in Quirky. As Quirky is cut-down, I thought that I would probably need the &#39;mesa&#39; package, so I ran the Puppy Package Manager and installed it from the T2 binary repository.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Puppy Package Manager fixed for .tar.bz2 packages&lt;/b&gt;&lt;br /&gt;PPM also stated that &#39;mesa&#39; needed two dependencies, &#39;dri2proto&#39; and &#39;sysfiles&#39;. I installed the former only. &#39;sysfiles&#39; is core structural files that are already in Puppy, so to avoid this issue in the future, I added &quot;sysfiles&quot; to the &#39;PKG_NAME_IGNORE&#39; variable in file /root/.packages/PKGS_MANAGEMENT (this is done in Woof, so will be in all puppy builds).&lt;br /&gt;&lt;br /&gt;But then I discovered that PPM has a bug, does not actually install any files. I edited /usr/local/petget/installpkg.sh and fixed so that .tar.bz2 packages do get installed. &lt;br /&gt;&lt;br /&gt;I ended up installing these T2 binary pkgs:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;mesa&lt;br /&gt;dri2proto&lt;br /&gt;glproto&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have the &#39;devx&#39; and the 2.6.31.5 kernel source SFS files loaded, although I don&#39;t know if the latter is needed.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;xorg-xserver 1.7.3&lt;/b&gt;&lt;br /&gt;Quirky is supposed to be as cutdown as is reasonable... so I have taken out the XvMC (Xv Motion Control) support, as my understanding is that not all Xorg drivers support it. DRI2 is probably in the same boat, but I have left that in. It is a bit of a concern taking out too much, as then the commercial Nvidia drivers might not compile -- although one of my reasons for upgrading is to see if the latest &#39;nv&#39; driver will do the job, so the commercial Nvidia drivers won&#39;t be needed. Anyway, giving this a go...&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# ./configure --prefix=/usr/X11R7 --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --disable-dmx --disable-xvfb --disable-xephyr  --disable-config-hal --disable-xnest --enable-kdrive --enable-xsdl --disable-xvmc&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...very interesting, I enabled the &#39;Xsdl&#39; kdrive server. What is this? There is no documentation in the package. Ah, the Xorg 7.5 release notes have this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Xsdl server&lt;br /&gt;    The experimental Xsdl server has never been finished or maintained, and will be removed in future X server releases.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...so much for that! There is not much left in the &#39;kdrive&#39; category. For 7.5, everything has been removed, except for the Xsdl and Xfbdev servers.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;xf86-video-nv 2.1.16&lt;/b&gt;&lt;br /&gt;The version compiled in T2 and hence in Quirky up until 003 is 2.1.15. So, we shall see if this one makes any difference...&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# ./configure --prefix=/usr/X11R7 --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --with-xserver-source=../xorg-server-1.7.3&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;These upgrades will be in Quirky 004. The bugfixes for Woof will be uploaded soon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01330</link>
		<title>SDL compile howto</title>
		<category>Quirky</category>
		<description>Just for the record, this is how I compiled SDL and the extras for Quirky. I compiled SDL recently as it is needed for the &#39;ffplay&#39; utility in ffmpeg. Then a couple of days ago I compiled the extras:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;SDL 1.2.14&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --disable-esd --disable-pulseaudio --disable-arts --disable-mintaudio --disable-video-cocoa --disable-video-directfb --disable-video-opengl --enable-nasm --disable-video-photon --disable-video-carbon --disable-video-ps2gs --disable-video-ps3 --disable-video-ggi --disable-video-vgl&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;sdl_mixer 1.2.11&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --disable-music-mod --disable-music-midi --enable-music-mp3-mad-gpl&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;SDL_image 1.2.10&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;SDL_ttf 2.0.9&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu &lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;Note that the default of SDL_mixer is to require the &#39;smpeg&#39; package to provide mp3 audio support. However, the &#39;--enable-music-mp3-mad-gpl&#39; option makes it use &#39;libmad&#39; instead.&lt;br /&gt;&lt;br /&gt;Even so, when I was compiling SDL games, I came across some that require the &#39;smpeg&#39; package.&lt;br /&gt;&lt;br /&gt;Just a little note on the side:&lt;br /&gt;this could be completely wrong, I just got the vibes that things have moved on since SDL was at it&#39;s heyday. A bit like Tcl/Tk. Libraries like &#39;cairo&#39; in GTK have made GTK coding of games more than competitive? I dunno, this is a very superficial assessment, as I say, just some vibes I got while browsing. You are welcome to shoot me down on this one.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01329</link>
		<title>Xorg Wizard &#39;vesa&#39; bugfix</title>
		<category>Woof</category>
		<description>I found a couple of bugs in the Xorg Wizard. After the user has chosen to test the video, a dialog window asks if want to change to the generic vesa driver -- but the button display &lt;yes&gt; &lt;no&gt; only instead of the appropriate labels. Furthermore, if the vesa generic driver is chosen, a following window after the next test states that the previous driver is still chosen. I fixed both bugs.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Nvidia GeForce 6600 GT&lt;/b&gt;&lt;br /&gt;Sometime ago, my daughter gave me her old computer. Today is the first time I have plugged it in. No hard drive. What interests me about this PC is that it has an Nvidia card, a GeForce 6600 GT model.&lt;br /&gt;&lt;br /&gt;Ok, I get video for both the &#39;nv&#39; and &#39;vesa&#39; drivers, however the ps/2 mouse is crazy -- pointer jumps one side of the screen to the other, or just moves horizontally along the bottom, or disappears entirely. Totally unusable. &lt;br /&gt;&lt;br /&gt;Well, I&#39;ll google around, see if others have this problem.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01328</link>
		<title>More SDL games</title>
		<category>Quirky</category>
		<description>A few more:&lt;br /&gt;&lt;br /&gt;Sizes of PETS:&lt;br /&gt;Burgerspace: 130KB, Cosmosmash: 70KB, Lmarbles: 764KB, Wakkabox: 76KB.&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/burgerspace-1.8.3-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/burgerspace-1.8.3-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/cosmosmash-1.4.3-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/cosmosmash-1.4.3-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/lmarbles-1.0.8-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/lmarbles-1.0.8-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/wakkabox-1.1.0-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/wakkabox-1.1.0-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;That&#39;s enough, I&#39;ve run out of steam!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01327</link>
		<title>SDL games</title>
		<category>Quirky</category>
		<description>Now that Quirky 003 has the SDL library, the door is opened for lots of SDL games. Ok, Quirky 003 has the SDL package, but these extra dependencies are required. fortunately they are small:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Dependencies&lt;/b&gt;&lt;br /&gt;SDL_mixer, SDL_image, SDL_ttf, flatzebra -- the latter is a game engine used by some of the games. Get these dependencies from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_mixer-1.2.11-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_mixer-1.2.11-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_image-1.2.10-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_image-1.2.10-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_ttf-2.0.9-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_ttf-2.0.9-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/flatzebra-0.1.3-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/flatzebra-0.1.3-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And if you want to compile your own SDL games, you&#39;ll need the DEV packages:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_mixer_DEV-1.2.11-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_mixer_DEV-1.2.11-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_image_DEV-1.2.10-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_image_DEV-1.2.10-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_ttf_DEV-2.0.9-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_ttf_DEV-2.0.9-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/flatzebra_DEV-0.1.3-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/flatzebra_DEV-0.1.3-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If you have Quirky 003 then you will already have these:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL-1.2.14-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL-1.2.14-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_DEV-1.2.14-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/SDL_DEV-1.2.14-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Games&lt;/b&gt;&lt;br /&gt;Here are some games:&lt;br /&gt;&lt;br /&gt;Sizes of PETs:&lt;br /&gt;Abe: 2.8MB, Icebreaker: 35KB, Maze-rays: 15KB, Toppler: 1.5MB, AfternoonStalker: 92KB, Btrachians: 102KB.&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/abe-1.1-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/abe-1.1-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/icebreaker-1.2.1-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/icebreaker-1.2.1-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/maze-rays-1.1-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/maze-rays-1.1-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/toppler-1.1.3-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/toppler-1.1.3-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/afternoonstalker-1.1.2-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/afternoonstalker-1.1.2-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/batrachians-0.1.2-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/batrachians-0.1.2-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m compiling more, will upload soon!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01326</link>
		<title>Stardust 004</title>
		<category>Puppy</category>
		<description>So, what&#39;s happening on the Puppy 4.x front? There are a few puplets being developed. I noticed in the forum today two that are especially active: Jemimah&#39;s Puppeee (for eeePC netbooks) and zigbert&#39;s Stardust.&lt;br /&gt;&lt;br /&gt;Stardust has now reached version 004. Read more:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=51126 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=51126&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01325</link>
		<title>Retrovol 0.1, Xtmix 0.4</title>
		<category>Puppy</category>
		<description>&lt;b&gt;Retrovol&lt;/b&gt;&lt;br /&gt;Pizzasgood has written a very nice volume control for the tray, with a popup mixer. Pizzasgood has achived a fully-featured mixer, as some other GUI mixers are somewhat lacking -- forcing us to use the ncurses text-mode AlsaMixer.&lt;br /&gt;&lt;br /&gt;Forum thread:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=50744 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=50744&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Pizzasgood, I would like to make a request. Could you add a commandline option to bring up the mixer immediately -- and it would have to run with some other name than &quot;retrovol&quot; so that it doesn&#39;t get swallowed by the JWM tray. That would be really neat, then I can have a menu entry for the mixer.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;EDIT:&lt;/b&gt; no sorry, Retrovol is not a window that gets swallowed, as in the example of Xtmix, so running the mixer as a different name doesn&#39;t apply.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Xtmix&lt;/b&gt;&lt;br /&gt;Note that Quirky 003 has Xtmix, an oldy-but-goody. In /root/.jwmrc-tray there is this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;&lt;Swallow name=&quot;xtmix-launcher&quot;&gt;&lt;br /&gt; xtmix -launch&lt;br /&gt;&lt;/Swallow&gt;&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...this causes a round volume control knob to display, that gets swallowed in the JWM tray (it&#39;s running name is &quot;xtmix-launcher&quot;. Right-click brings up a mixer. There is also a menu entry, which launches &#39;xtmix&#39; which brings up the mixer directly. &lt;br /&gt;The Xtmix mixer is a bit light-on as far as slider controls goes, and that&#39;s the main disadvantage. What is really good is the tray applet uses few resources. &lt;br /&gt;&lt;br /&gt;The Xtmix PET:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/xtmix-0.4-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/xtmix-0.4-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And the source:&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/x/xtmix04.tar.gz target=_blank&gt;http://bkhome.org/sources/alphabetical/x/xtmix04.tar.gz&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01324</link>
		<title>GtkLP print files, manage queue</title>
		<category>Quirky</category>
		<description>I have compiled GtkLP 1.2.7 for Quirky:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/gtklp-1.2.7-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/gtklp-1.2.7-q1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I looked at a GtkLP package created by ttuuxxx:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?p=371589&amp;sid=a2bf25bc0fc4b7faa2a5dfaf0acff7f4 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?p=371589&amp;sid=a2bf25bc0fc4b7faa2a5dfaf0acff7f4&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;ttuuxxx has modified /etc/gtk-2.0/gtkrc, setting this:&lt;br /&gt;&lt;br /&gt;gtk-print-backends = &quot;lpr,file&quot;&lt;br /&gt;&lt;br /&gt;...whereas the default is &quot;file,cups&quot;.&lt;br /&gt;&lt;br /&gt;Ttuuxxx also has a script /usr/bin/lpr.&lt;br /&gt;&lt;br /&gt;Ttuuxxx&#39;s package is for Puppy 431 I think, however in Quirky I don&#39;t know of any printing problem that requires such a solution. So, my package doesn&#39;t change &#39;gtk-print-backends&#39; and has the default lpr script that comes with the cups package.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Printing note&lt;/b&gt;&lt;br /&gt;Quirky uses CUPS 1.3.11. Interesting, it doesn&#39;t ever ask for username/password -- I somehow seem to have fixed that.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Compiling note&lt;/b&gt;&lt;br /&gt;Quirky has Xorg in /usr/X11R7, but I have got it setup so never have trouble anymore with configuring and compiling packages. They are all able to find the libs. This contrasts with trouble I had sometime in Puppy4.&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01323</link>
		<title>g2calc won&#39;t compile</title>
		<category>Puppy</category>
		<description>I have tried to compile g2calc version 0.13 created by disciple:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# cd src&lt;br /&gt;# make&lt;br /&gt;yacc -d --report=solved --report=itemset expcalc_par.y&lt;br /&gt;conflicts: 44 reduce/reduce&lt;br /&gt;flex expcalc_tok.l&lt;br /&gt;gcc -c -o y.tab.o y.tab.c&lt;br /&gt;In file included from expcalc_par.y:129:&lt;br /&gt;expcalc_tok.l: In function &#39;yylex&#39;:&lt;br /&gt;expcalc_tok.l:53: error: &#39;tE&#39; undeclared (first use in this function)&lt;br /&gt;expcalc_tok.l:53: error: (Each undeclared identifier is reported only once&lt;br /&gt;expcalc_tok.l:53: error: for each function it appears in.)&lt;br /&gt;make: *** [y.tab.o] Error 1&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Hmmm, I downloaded g2calc original source, it compiles, but it doesn&#39;t work -- I click buttons, nothing displays. Oh well.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01322</link>
		<title>lameSMBxplorer 0.1.1a</title>
		<category>Quirky</category>
		<description>Patriot has developed a new Samba shares browser, that looks like it can replace HairyWill&#39;s Pnethood. Forum thread:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=50901 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=50901&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have made it into a PET package and placed at my Quirky repository:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/lamesmbxplorer-0.1.1a.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/lamesmbxplorer-0.1.1a.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Of course, Patriot already had a PET package, but I updated it with the &#39;pet.specs&#39; file and a list of dependencies. Which are:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;+gtkdialog3,+nbtscan,+samba_client&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;One difference from Pnethood is that lameSMBxplorer does not use &#39;mount.cifs&#39; from the &#39;mountcifs&#39; package -- or does it?&lt;br /&gt;&lt;br /&gt;&lt;b&gt;pet.specs&lt;/b&gt;&lt;br /&gt;A note about the database entry in &#39;pet.specs&#39;, this is it for lamesmbxplorer:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;lamesmbxplorer-0.1.1a|lamesmbxplorer|0.1.1a||Network|76K|pet_packages-quirky|lamesmbxplorer-0.1.1a.pet|+gtkdialog3,+nbtscan,+samba_client|connect to samba shares|||official|&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...I&#39;m planning to make a small change, allow the subdirectory field to be empty. I have put &quot;pet_packages-quirky&quot; in it, but that of course is only relevant when it is at my repo.&lt;br /&gt;I will now allow the field to be blank:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;lamesmbxplorer-0.1.1a|lamesmbxplorer|0.1.1a||Network|76K||lamesmbxplorer-0.1.1a.pet|+gtkdialog3,+nbtscan,+samba_client|connect to samba shares|||official|&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...and the meaning of the empty field is that the package is located in the default location on whatever repo it is held.&lt;br /&gt;&lt;br /&gt;I intend to update the package manager to recognise an empty path field to have that meaning.&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01321</link>
		<title>PupScan fixed</title>
		<category>Woof</category>
		<description>The PupScan application (see System menu) was displaying incorrect information about the PCI devices.&lt;br /&gt;&lt;br /&gt;The problem is that it uses the &#39;scanpci&#39; utility, which I have in Woof, but it is no longer part of Xorg. It used to be, up to Xorg 7.3, that the libpciaccess library had a database of PCI information, however from 7.4 onwards the libpciaccess does not have its own database, instead reads from /usr/share/pci.ids (which is part of pciutils package).&lt;br /&gt;&lt;br /&gt;So Woof builds now have the full &#39;pci.ids&#39; file, but &#39;scanpci&#39; is still included. However, it no longer works properly.&lt;br /&gt;&lt;br /&gt;So, I have modified /usr/sbin/pupscan so that it detects existence of /usr/share/pci.ids and if exists then uses the lspci utility to obtain the PCI information.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01320</link>
		<title>Woof uploaded, January 7, 2010</title>
		<category>Woof</category>
		<description>These are the comments in the &#39;commits&#39; file since the last upload:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;ntfs-3g in initrd (and quirky pkg) updated from 2009.4.4 to 2009.11.14&lt;br /&gt;fix shutdown if ntfs partition mounted, 60-sec timeout in shutdown dlg&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;JorgenS reported in the Quirky 003 feedback thread that the on-going problem remains, if a NTFS partition is mounted, Quirky will not shutdown, X just restarts. I have isolated the problem, and fixed /etc/rc.d/rc.shutdown.&lt;br /&gt;Note, this problem did not occur if the NTFS partition has the &#39;pupsave&#39;.&lt;br /&gt;&lt;br /&gt;There was another issue where unattended shutdown may be required, and where there is no &#39;pupsave&#39; file. The rc.shutdown script brings up a dialog asking if you want to create a &#39;pupsave&#39;, but if unattended then it will never shutdown. I have put in a 60 second timeout in the dialog, after which it will shutdown without creating a &#39;pupsave&#39;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01319</link>
		<title>Hacking Pwireless2</title>
		<category>Quirky</category>
		<description>There are some issues with putting Jemimah&#39;s Pwireless2 beta2.7 into Quirky.&lt;br /&gt;&lt;br /&gt;Jemimah has included binary executables from &#39;gtrayicon&#39;, &#39;dhcpcd&#39; and &#39;wpa_supplicant&#39; packages inside Pwireless2. That is not acceptable for me, so I am in the process of providing those packages as separate PETs.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;dhcpcd&lt;/b&gt;&lt;br /&gt;I recently compiled version 5.1.3. There are problems with using this with Pwireless2. I configured like this:&lt;br /&gt;&lt;br /&gt;./configure --libexecdir=/lib/dhcpcd --dbdir=/var/lib/dhcpcd --sysconfdir=/etc&lt;br /&gt;&lt;br /&gt;as this is the posix recommended layout, as stated in the dhcpcd docs. However, jemimah has left the db-directory as /var/db, the execdir as /usr/libexec and the binary executables are in /usr/local/sbin whereas I have them in /usr/sbin -- and Jemimah&#39;s scripts have hardcoded paths for the excutables (which she probably did to avoid using old executables (?)).&lt;br /&gt;&lt;br /&gt;I have created a dhcpcd PET package with symlinks, which fixes most of the problems. However, /var/db is used by something else and I cannot make that into a symlink. Umm, it seems only /root/Startup/Pwireless2 explicitly addresses /var/db, so I request that another line be inserted in the script:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;rm -f /var/db/dhcpcd*&lt;br /&gt;rm -f /var/lib/dhcpcd/dhcpcd*&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Oh, I have just looked in Jemimah&#39;s /etc/dhcpcd.conf, it has this line:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;denyinterfaces lo,ppp0,wmaster0&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...hmmm, I need to put this on hold until after further discussion with Jemimah and others. Um, wouldn&#39;t it be better, if dhcpcd.conf is modified in a manner that may adversely affect other uses (like ppp0 dialup), that the dhcpcd executable be called with &quot;--config &lt;alternate config file&gt;&quot;? The dhcpcd commandline also allows &quot;--denyinterfaces &lt;comma-delimited list&gt;&quot;.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;wpa_supplicant&lt;/b&gt;&lt;br /&gt;Jemimah has configured this differently from the one already in Puppy or Quirky. She has sent me the configure details but I have not yet got onto that. For the record, this is the .config file that she has sent me:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;# Example wpa_supplicant build time configuration&lt;br /&gt;#&lt;br /&gt;# This file lists the configuration options that are used when building the&lt;br /&gt;# hostapd binary. All lines starting with # are ignored. Configuration option&lt;br /&gt;# lines must be commented out complete, if they are not to be included, i.e.,&lt;br /&gt;# just setting VARIABLE=n is not disabling that variable.&lt;br /&gt;#&lt;br /&gt;# This file is included in Makefile, so variables like CFLAGS and LIBS can also&lt;br /&gt;# be modified from here. In most cases, these lines should use += in order not&lt;br /&gt;# to override previous values of the variables.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# Uncomment following two lines and fix the paths if you have installed OpenSSL&lt;br /&gt;# or GnuTLS in non-default location&lt;br /&gt;#CFLAGS += -I/usr/local/openssl/include&lt;br /&gt;#LIBS += -L/usr/local/openssl/lib&lt;br /&gt;&lt;br /&gt;# Some Red Hat versions seem to include kerberos header files from OpenSSL, but&lt;br /&gt;# the kerberos files are not in the default include path. Following line can be&lt;br /&gt;# used to fix build issues on such systems (krb5.h not found).&lt;br /&gt;#CFLAGS += -I/usr/include/kerberos&lt;br /&gt;&lt;br /&gt;# Example configuration for various cross-compilation platforms&lt;br /&gt;&lt;br /&gt;#### sveasoft (e.g., for Linksys WRT54G) ######################################&lt;br /&gt;#CC=mipsel-uclibc-gcc&lt;br /&gt;#CC=/opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc&lt;br /&gt;#CFLAGS += -Os&lt;br /&gt;#CPPFLAGS += -I../src/include -I../../src/router/openssl/include&lt;br /&gt;#LIBS += -L/opt/brcm/hndtools-mipsel-uclibc-0.9.19/lib -lssl&lt;br /&gt;###############################################################################&lt;br /&gt;&lt;br /&gt;#### openwrt (e.g., for Linksys WRT54G) #######################################&lt;br /&gt;#CC=mipsel-uclibc-gcc&lt;br /&gt;#CC=/opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc&lt;br /&gt;#CFLAGS += -Os&lt;br /&gt;#CPPFLAGS=-I../src/include -I../openssl-0.9.7d/include \&lt;br /&gt;#	-I../WRT54GS/release/src/include&lt;br /&gt;#LIBS = -lssl&lt;br /&gt;###############################################################################&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;# Driver interface for Host AP driver&lt;br /&gt;CONFIG_DRIVER_HOSTAP=y&lt;br /&gt;&lt;br /&gt;# Driver interface for Agere driver&lt;br /&gt;#CONFIG_DRIVER_HERMES=y&lt;br /&gt;# Change include directories to match with the local setup&lt;br /&gt;#CFLAGS += -I../../hcf -I../../include -I../../include/hcf&lt;br /&gt;#CFLAGS += -I../../include/wireless&lt;br /&gt;&lt;br /&gt;# Driver interface for madwifi driver&lt;br /&gt;#CONFIG_DRIVER_MADWIFI=y&lt;br /&gt;# Set include directory to the madwifi source tree&lt;br /&gt;CFLAGS += -I../../madwifi&lt;br /&gt;&lt;br /&gt;# Driver interface for Prism54 driver&lt;br /&gt;# (Note: Prism54 is not yet supported, i.e., this will not work as-is and is&lt;br /&gt;# for developers only)&lt;br /&gt;#CONFIG_DRIVER_PRISM54=y&lt;br /&gt;&lt;br /&gt;# Driver interface for ndiswrapper&lt;br /&gt;#CONFIG_DRIVER_NDISWRAPPER=y&lt;br /&gt;&lt;br /&gt;# Driver interface for Atmel driver&lt;br /&gt;CONFIG_DRIVER_ATMEL=y&lt;br /&gt;&lt;br /&gt;# Driver interface for old Broadcom driver&lt;br /&gt;# Please note that the newer Broadcom driver (&quot;hybrid Linux driver&quot;) supports&lt;br /&gt;# Linux wireless extensions and does not need (or even work) with the old&lt;br /&gt;# driver wrapper. Use CONFIG_DRIVER_WEXT=y with that driver.&lt;br /&gt;#CONFIG_DRIVER_BROADCOM=y&lt;br /&gt;# Example path for wlioctl.h; change to match your configuration&lt;br /&gt;#CFLAGS += -I/opt/WRT54GS/release/src/include&lt;br /&gt;&lt;br /&gt;# Driver interface for Intel ipw2100/2200 driver&lt;br /&gt;CONFIG_DRIVER_IPW=y&lt;br /&gt;&lt;br /&gt;# Driver interface for Ralink driver&lt;br /&gt;CONFIG_DRIVER_RALINK=y&lt;br /&gt;&lt;br /&gt;# Driver interface for generic Linux wireless extensions&lt;br /&gt;CONFIG_DRIVER_WEXT=y&lt;br /&gt;&lt;br /&gt;# Driver interface for Linux drivers using the nl80211 kernel interface&lt;br /&gt;#CONFIG_DRIVER_NL80211=y&lt;br /&gt;&lt;br /&gt;# Driver interface for FreeBSD net80211 layer (e.g., Atheros driver)&lt;br /&gt;#CONFIG_DRIVER_BSD=y&lt;br /&gt;#CFLAGS += -I/usr/local/include&lt;br /&gt;#LIBS += -L/usr/local/lib&lt;br /&gt;&lt;br /&gt;# Driver interface for Windows NDIS&lt;br /&gt;#CONFIG_DRIVER_NDIS=y&lt;br /&gt;#CFLAGS += -I/usr/include/w32api/ddk&lt;br /&gt;#LIBS += -L/usr/local/lib&lt;br /&gt;# For native build using mingw&lt;br /&gt;#CONFIG_NATIVE_WINDOWS=y&lt;br /&gt;# Additional directories for cross-compilation on Linux host for mingw target&lt;br /&gt;#CFLAGS += -I/opt/mingw/mingw32/include/ddk&lt;br /&gt;#LIBS += -L/opt/mingw/mingw32/lib&lt;br /&gt;#CC=mingw32-gcc&lt;br /&gt;# By default, driver_ndis uses WinPcap for low-level operations. This can be&lt;br /&gt;# replaced with the following option which replaces WinPcap calls with NDISUIO.&lt;br /&gt;# However, this requires that WZC is disabled (net stop wzcsvc) before starting&lt;br /&gt;# wpa_supplicant.&lt;br /&gt; CONFIG_USE_NDISUIO=y&lt;br /&gt;&lt;br /&gt;# Driver interface for development testing&lt;br /&gt;#CONFIG_DRIVER_TEST=y&lt;br /&gt;&lt;br /&gt;# Driver interface for wired Ethernet drivers&lt;br /&gt;CONFIG_DRIVER_WIRED=y&lt;br /&gt;&lt;br /&gt;# Driver interface for the Broadcom RoboSwitch family&lt;br /&gt;CONFIG_DRIVER_ROBOSWITCH=y&lt;br /&gt;&lt;br /&gt;# Enable IEEE 802.1X Supplicant (automatically included if any EAP method is&lt;br /&gt;# included)&lt;br /&gt;CONFIG_IEEE8021X_EAPOL=y&lt;br /&gt;&lt;br /&gt;# EAP-MD5&lt;br /&gt;CONFIG_EAP_MD5=y&lt;br /&gt;&lt;br /&gt;# EAP-MSCHAPv2&lt;br /&gt;CONFIG_EAP_MSCHAPV2=y&lt;br /&gt;&lt;br /&gt;# EAP-TLS&lt;br /&gt;CONFIG_EAP_TLS=y&lt;br /&gt;&lt;br /&gt;# EAL-PEAP&lt;br /&gt;CONFIG_EAP_PEAP=y&lt;br /&gt;&lt;br /&gt;# EAP-TTLS&lt;br /&gt;CONFIG_EAP_TTLS=y&lt;br /&gt;&lt;br /&gt;# EAP-FAST&lt;br /&gt;# Note: Default OpenSSL package does not include support for all the&lt;br /&gt;# functionality needed for EAP-FAST. If EAP-FAST is enabled with OpenSSL,&lt;br /&gt;# the OpenSSL library must be patched (openssl-0.9.8d-tls-extensions.patch)&lt;br /&gt;# to add the needed functions.&lt;br /&gt;#CONFIG_EAP_FAST=y&lt;br /&gt;&lt;br /&gt;# EAP-GTC&lt;br /&gt;CONFIG_EAP_GTC=y&lt;br /&gt;&lt;br /&gt;# EAP-OTP&lt;br /&gt;CONFIG_EAP_OTP=y&lt;br /&gt;&lt;br /&gt;# EAP-SIM (enable CONFIG_PCSC, if EAP-SIM is used)&lt;br /&gt;#CONFIG_EAP_SIM=y&lt;br /&gt;&lt;br /&gt;# EAP-PSK (experimental; this is _not_ needed for WPA-PSK)&lt;br /&gt;#CONFIG_EAP_PSK=y&lt;br /&gt;&lt;br /&gt;# EAP-PAX&lt;br /&gt;#CONFIG_EAP_PAX=y&lt;br /&gt;&lt;br /&gt;# LEAP&lt;br /&gt;CONFIG_EAP_LEAP=y&lt;br /&gt;&lt;br /&gt;# EAP-AKA (enable CONFIG_PCSC, if EAP-AKA is used)&lt;br /&gt;#CONFIG_EAP_AKA=y&lt;br /&gt;&lt;br /&gt;# EAP-AKA&#39; (enable CONFIG_PCSC, if EAP-AKA&#39; is used).&lt;br /&gt;# This requires CONFIG_EAP_AKA to be enabled, too.&lt;br /&gt;#CONFIG_EAP_AKA_PRIME=y&lt;br /&gt;&lt;br /&gt;# Enable USIM simulator (Milenage) for EAP-AKA&lt;br /&gt;#CONFIG_USIM_SIMULATOR=y&lt;br /&gt;&lt;br /&gt;# EAP-SAKE&lt;br /&gt;#CONFIG_EAP_SAKE=y&lt;br /&gt;&lt;br /&gt;# EAP-GPSK&lt;br /&gt;#CONFIG_EAP_GPSK=y&lt;br /&gt;# Include support for optional SHA256 cipher suite in EAP-GPSK&lt;br /&gt;#CONFIG_EAP_GPSK_SHA256=y&lt;br /&gt;&lt;br /&gt;# EAP-TNC and related Trusted Network Connect support (experimental)&lt;br /&gt;#CONFIG_EAP_TNC=y&lt;br /&gt;&lt;br /&gt;# Wi-Fi Protected Setup (WPS)&lt;br /&gt;#CONFIG_WPS=y&lt;br /&gt;&lt;br /&gt;# EAP-IKEv2&lt;br /&gt;#CONFIG_EAP_IKEV2=y&lt;br /&gt;&lt;br /&gt;# PKCS#12 (PFX) support (used to read private key and certificate file from&lt;br /&gt;# a file that usually has extension .p12 or .pfx)&lt;br /&gt;CONFIG_PKCS12=y&lt;br /&gt;&lt;br /&gt;# Smartcard support (i.e., private key on a smartcard), e.g., with openssl&lt;br /&gt;# engine.&lt;br /&gt;CONFIG_SMARTCARD=y&lt;br /&gt;&lt;br /&gt;# PC/SC interface for smartcards (USIM, GSM SIM)&lt;br /&gt;# Enable this if EAP-SIM or EAP-AKA is included&lt;br /&gt;#CONFIG_PCSC=y&lt;br /&gt;&lt;br /&gt;# Development testing&lt;br /&gt;#CONFIG_EAPOL_TEST=y&lt;br /&gt;&lt;br /&gt;# Select control interface backend for external programs, e.g, wpa_cli:&lt;br /&gt;# unix = UNIX domain sockets (default for Linux/*BSD)&lt;br /&gt;# udp = UDP sockets using localhost (127.0.0.1)&lt;br /&gt;# named_pipe = Windows Named Pipe (default for Windows)&lt;br /&gt;# y = use default (backwards compatibility)&lt;br /&gt;# If this option is commented out, control interface is not included in the&lt;br /&gt;# build.&lt;br /&gt;CONFIG_CTRL_IFACE=y&lt;br /&gt;&lt;br /&gt;# Include support for GNU Readline and History Libraries in wpa_cli.&lt;br /&gt;# When building a wpa_cli binary for distribution, please note that these&lt;br /&gt;# libraries are licensed under GPL and as such, BSD license may not apply for&lt;br /&gt;# the resulting binary.&lt;br /&gt;CONFIG_READLINE=y&lt;br /&gt;&lt;br /&gt;# Remove debugging code that is printing out debug message to stdout.&lt;br /&gt;# This can be used to reduce the size of the wpa_supplicant considerably&lt;br /&gt;# if debugging code is not needed. The size reduction can be around 35%&lt;br /&gt;# (e.g., 90 kB).&lt;br /&gt;#CONFIG_NO_STDOUT_DEBUG=y&lt;br /&gt;&lt;br /&gt;# Remove WPA support, e.g., for wired-only IEEE 802.1X supplicant, to save&lt;br /&gt;# 35-50 kB in code size.&lt;br /&gt;#CONFIG_NO_WPA=y&lt;br /&gt;&lt;br /&gt;# Remove WPA2 support. This allows WPA to be used, but removes WPA2 code to&lt;br /&gt;# save about 1 kB in code size when building only WPA-Personal (no EAP support)&lt;br /&gt;# or 6 kB if building for WPA-Enterprise.&lt;br /&gt;#CONFIG_NO_WPA2=y&lt;br /&gt;&lt;br /&gt;# Remove IEEE 802.11i/WPA-Personal ASCII passphrase support&lt;br /&gt;# This option can be used to reduce code size by removing support for&lt;br /&gt;# converting ASCII passphrases into PSK. If this functionality is removed, the&lt;br /&gt;# PSK can only be configured as the 64-octet hexstring (e.g., from&lt;br /&gt;# wpa_passphrase). This saves about 0.5 kB in code size.&lt;br /&gt;#CONFIG_NO_WPA_PASSPHRASE=y&lt;br /&gt;&lt;br /&gt;# Remove AES extra functions. This can be used to reduce code size by about&lt;br /&gt;# 1.5 kB by removing extra AES modes that are not needed for commonly used&lt;br /&gt;# client configurations (they are needed for some EAP types).&lt;br /&gt;#CONFIG_NO_AES_EXTRAS=y&lt;br /&gt;&lt;br /&gt;# Disable scan result processing (ap_mode=1) to save code size by about 1 kB.&lt;br /&gt;# This can be used if ap_scan=1 mode is never enabled.&lt;br /&gt;#CONFIG_NO_SCAN_PROCESSING=y&lt;br /&gt;&lt;br /&gt;# Select configuration backend:&lt;br /&gt;# file = text file (e.g., wpa_supplicant.conf; note: the configuration file&lt;br /&gt;#	path is given on command line, not here; this option is just used to&lt;br /&gt;#	select the backend that allows configuration files to be used)&lt;br /&gt;# winreg = Windows registry (see win_example.reg for an example)&lt;br /&gt;CONFIG_BACKEND=file&lt;br /&gt;&lt;br /&gt;# Remove configuration write functionality (i.e., to allow the configuration&lt;br /&gt;# file to be updated based on runtime configuration changes). The runtime&lt;br /&gt;# configuration can still be changed, the changes are just not going to be&lt;br /&gt;# persistent over restarts. This option can be used to reduce code size by&lt;br /&gt;# about 3.5 kB.&lt;br /&gt;#CONFIG_NO_CONFIG_WRITE=y&lt;br /&gt;&lt;br /&gt;# Remove support for configuration blobs to reduce code size by about 1.5 kB.&lt;br /&gt;#CONFIG_NO_CONFIG_BLOBS=y&lt;br /&gt;&lt;br /&gt;# Select program entry point implementation:&lt;br /&gt;# main = UNIX/POSIX like main() function (default)&lt;br /&gt;# main_winsvc = Windows service (read parameters from registry)&lt;br /&gt;# main_none = Very basic example (development use only)&lt;br /&gt;#CONFIG_MAIN=main&lt;br /&gt;&lt;br /&gt;# Select wrapper for operatins system and C library specific functions&lt;br /&gt;# unix = UNIX/POSIX like systems (default)&lt;br /&gt;# win32 = Windows systems&lt;br /&gt;# none = Empty template&lt;br /&gt;#CONFIG_OS=unix&lt;br /&gt;&lt;br /&gt;# Select event loop implementation&lt;br /&gt;# eloop = select() loop (default)&lt;br /&gt;# eloop_win = Windows events and WaitForMultipleObject() loop&lt;br /&gt;# eloop_none = Empty template&lt;br /&gt;#CONFIG_ELOOP=eloop&lt;br /&gt;&lt;br /&gt;# Select layer 2 packet implementation&lt;br /&gt;# linux = Linux packet socket (default)&lt;br /&gt;# pcap = libpcap/libdnet/WinPcap&lt;br /&gt;# freebsd = FreeBSD libpcap&lt;br /&gt;# winpcap = WinPcap with receive thread&lt;br /&gt;# ndis = Windows NDISUIO (note: requires CONFIG_USE_NDISUIO=y)&lt;br /&gt;# none = Empty template&lt;br /&gt;#CONFIG_L2_PACKET=linux&lt;br /&gt;&lt;br /&gt;# PeerKey handshake for Station to Station Link (IEEE 802.11e DLS)&lt;br /&gt;CONFIG_PEERKEY=y&lt;br /&gt;&lt;br /&gt;# IEEE 802.11w (management frame protection)&lt;br /&gt;# This version is an experimental implementation based on IEEE 802.11w/D1.0&lt;br /&gt;# draft and is subject to change since the standard has not yet been finalized.&lt;br /&gt;# Driver support is also needed for IEEE 802.11w.&lt;br /&gt;#CONFIG_IEEE80211W=y&lt;br /&gt;&lt;br /&gt;# Select TLS implementation&lt;br /&gt;# openssl = OpenSSL (default)&lt;br /&gt;# gnutls = GnuTLS (needed for TLS/IA, see also CONFIG_GNUTLS_EXTRA)&lt;br /&gt;# internal = Internal TLSv1 implementation (experimental)&lt;br /&gt;# none = Empty template&lt;br /&gt;#CONFIG_TLS=openssl&lt;br /&gt;&lt;br /&gt;# Whether to enable TLS/IA support, which is required for EAP-TTLSv1.&lt;br /&gt;# You need CONFIG_TLS=gnutls for this to have any effect. Please note that&lt;br /&gt;# even though the core GnuTLS library is released under LGPL, this extra&lt;br /&gt;# library uses GPL and as such, the terms of GPL apply to the combination&lt;br /&gt;# of wpa_supplicant and GnuTLS if this option is enabled. BSD license may not&lt;br /&gt;# apply for distribution of the resulting binary.&lt;br /&gt;#CONFIG_GNUTLS_EXTRA=y&lt;br /&gt;&lt;br /&gt;# If CONFIG_TLS=internal is used, additional library and include paths are&lt;br /&gt;# needed for LibTomMath. Alternatively, an integrated, minimal version of&lt;br /&gt;# LibTomMath can be used. See beginning of libtommath.c for details on benefits&lt;br /&gt;# and drawbacks of this option.&lt;br /&gt;#CONFIG_INTERNAL_LIBTOMMATH=y&lt;br /&gt;#ifndef CONFIG_INTERNAL_LIBTOMMATH&lt;br /&gt;#LTM_PATH=/usr/src/libtommath-0.39&lt;br /&gt;#CFLAGS += -I$(LTM_PATH)&lt;br /&gt;#LIBS += -L$(LTM_PATH)&lt;br /&gt;#LIBS_p += -L$(LTM_PATH)&lt;br /&gt;#endif&lt;br /&gt;# At the cost of about 4 kB of additional binary size, the internal LibTomMath&lt;br /&gt;# can be configured to include faster routines for exptmod, sqr, and div to&lt;br /&gt;# speed up DH and RSA calculation considerably&lt;br /&gt;CONFIG_INTERNAL_LIBTOMMATH_FAST=y&lt;br /&gt;&lt;br /&gt;# Include NDIS event processing through WMI into wpa_supplicant/wpasvc.&lt;br /&gt;# This is only for Windows builds and requires WMI-related header files and&lt;br /&gt;# WbemUuid.Lib from Platform SDK even when building with MinGW.&lt;br /&gt;#CONFIG_NDIS_EVENTS_INTEGRATED=y&lt;br /&gt;#PLATFORMSDKLIB=&quot;/opt/Program Files/Microsoft Platform SDK/Lib&quot;&lt;br /&gt;&lt;br /&gt;# Add support for DBus control interface&lt;br /&gt;#CONFIG_CTRL_IFACE_DBUS=y&lt;br /&gt;&lt;br /&gt;# Add support for loading EAP methods dynamically as shared libraries.&lt;br /&gt;# When this option is enabled, each EAP method can be either included&lt;br /&gt;# statically (CONFIG_EAP_&lt;method&gt;=y) or dynamically (CONFIG_EAP_&lt;method&gt;=dyn).&lt;br /&gt;# Dynamic EAP methods are build as shared objects (eap_*.so) and they need to&lt;br /&gt;# be loaded in the beginning of the wpa_supplicant configuration file&lt;br /&gt;# (see load_dynamic_eap parameter in the example file) before being used in&lt;br /&gt;# the network blocks.&lt;br /&gt;#&lt;br /&gt;# Note that some shared parts of EAP methods are included in the main program&lt;br /&gt;# and in order to be able to use dynamic EAP methods using these parts, the&lt;br /&gt;# main program must have been build with the EAP method enabled (=y or =dyn).&lt;br /&gt;# This means that EAP-TLS/PEAP/TTLS/FAST cannot be added as dynamic libraries&lt;br /&gt;# unless at least one of them was included in the main build to force inclusion&lt;br /&gt;# of the shared code. Similarly, at least one of EAP-SIM/AKA must be included&lt;br /&gt;# in the main build to be able to load these methods dynamically.&lt;br /&gt;#&lt;br /&gt;# Please also note that using dynamic libraries will increase the total binary&lt;br /&gt;# size. Thus, it may not be the best option for targets that have limited&lt;br /&gt;# amount of memory/flash.&lt;br /&gt;#CONFIG_DYNAMIC_EAP_METHODS=y&lt;br /&gt;&lt;br /&gt;# Include client MLME (management frame processing).&lt;br /&gt;# This can be used to move MLME processing of Linux mac80211 stack into user&lt;br /&gt;# space. Please note that this is currently only available with&lt;br /&gt;# driver_nl80211.c and only with a modified version of Linux kernel and&lt;br /&gt;# wpa_supplicant.&lt;br /&gt;#CONFIG_CLIENT_MLME=y&lt;br /&gt;&lt;br /&gt;# IEEE Std 802.11r-2008 (Fast BSS Transition)&lt;br /&gt;#CONFIG_IEEE80211R=y&lt;br /&gt;&lt;br /&gt;# Add support for writing debug log to a file (/tmp/wpa_supplicant-log-#.txt)&lt;br /&gt;CONFIG_DEBUG_FILE=y&lt;br /&gt;&lt;br /&gt;# Enable privilege separation (see README &#39;Privilege separation&#39; for details)&lt;br /&gt;#CONFIG_PRIVSEP=y&lt;br /&gt;&lt;br /&gt;# Enable mitigation against certain attacks against TKIP by delaying Michael&lt;br /&gt;# MIC error reports by a random amount of time between 0 and 60 seconds&lt;br /&gt;#CONFIG_DELAYED_MIC_ERROR_REPORT=y&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01318</link>
		<title>More PETs for Quirky</title>
		<category>Quirky</category>
		<description>Ttuuxxx has been compiling PETs for Quirky:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=50364 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=50364&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;You can also find my PETs here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...these are used to build the live-CD, but not all of them are chosen. For example, Quirky 003 does not have Geany and you can grab it from here.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01317</link>
		<title>Mozplugger in Quirky 003</title>
		<category>Quirky</category>
		<description>Quirky 003 has a radically different architecture for handling multimedia. There&#39;s no xine/gxine, gstreamer or mplayer.&lt;br /&gt;&lt;br /&gt;There is ffmpeg and the mozplugger browser plugin is supposed to launch &#39;ffplay&#39; to play embedded video (and maybe audio) in web pages.&lt;br /&gt;&lt;br /&gt;I created a test html file, using the suggestion from technosaurus, posted here:&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01310 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01310&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Yeah, ffplay plays the video, as a separate window. I want it to be swallowed into the web page, so I edited /etc/mozpluggerrc:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;video/mpeg:mpeg,mpg,mpe:MPEG animation&lt;br /&gt;video/x-mpeg:mpeg,mpg,mpe:MPEG animation&lt;br /&gt;video/x-mpeg2:mpv2,mp2ve:MPEG2 animation&lt;br /&gt;video/mp4:mp4:MPEG4 animation&lt;br /&gt;video/msvideo:avi:AVI animation&lt;br /&gt;video/x-msvideo:avi:AVI animation&lt;br /&gt;video/fli:fli,flc:FLI animation&lt;br /&gt;video/x-fli:fli,flc:FLI animation&lt;br /&gt;application/x-mplayer2:*:Windows Media video&lt;br /&gt;video/x-ms-asf:asf,asx:Windows Media video&lt;br /&gt;video/x-ms-wm:wm:Windows Media video&lt;br /&gt;video/x-ms-wmv:wmv:Windows Media video&lt;br /&gt;video/x-ms-wvx:wvx:Windows Media video&lt;br /&gt;video/x-ms-asf-plugin:*:Window Media video&lt;br /&gt;video/ogg:ogg:OGG stream with video&lt;br /&gt;video/x-ogg:ogm,ogv:OGG stream with video&lt;br /&gt;	stream swallow(ffplay) : ffplay &quot;$file&quot;&lt;br /&gt;&lt;br /&gt;audio/mp3:mp3:MPEG audio&lt;br /&gt;audio/x-mp3:mp3:MPEG audio&lt;br /&gt;audio/mpeg2:mp2:MPEG audio&lt;br /&gt;audio/x-mpeg2:mp2:MPEG audio&lt;br /&gt;audio/mpeg3:mp3:MPEG audio&lt;br /&gt;audio/x-mpeg3:mp3:MPEG audio&lt;br /&gt;audio/mpeg:mpa,abs,mpega:MPEG audio&lt;br /&gt;audio/x-mpeg:mpa,abs,mpega:MPEG audio&lt;br /&gt;audio/x-ogg:ogg:OGG audio&lt;br /&gt;application/x-ogg:ogg:OGG audio&lt;br /&gt;application/ogg:ogg:OGG audio&lt;br /&gt;audio/x-flac:flac:FLAC audio&lt;br /&gt;application/x-flac:flac:FLAC audio&lt;br /&gt;audio/basic:au,snd:Basic audio file&lt;br /&gt;audio/x-basic:au,snd:Basic audio file&lt;br /&gt;audio/wav:wav:Microsoft wave file&lt;br /&gt;audio/x-wav:wav:Microsoft wave file&lt;br /&gt;audio/x-pn-wav:wav:Microsoft wave file&lt;br /&gt;audio/x-pn-windows-acm:wav:Microsoft wave file&lt;br /&gt;audio/x-ms-wax:wax:Windows Media Audio&lt;br /&gt;audio/x-ms-wma:wma:Windows Media Audio&lt;br /&gt;	stream : ffplay &quot;$file&quot;&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;I then deleted /root/.mozilla/pluginreg.dat, which is recommended whenever /etc/mozpluggerrc is changed, then started SeaMonkey, opened the test html file, and YAY, embedded video!&lt;br /&gt;&lt;br /&gt;Note that the &quot;stream&quot; parameter means that ffplay can take a URL directly. Without &quot;stream&quot;, the video would be downloaded entirely first, then ffplay would be launched.&lt;br /&gt;&lt;br /&gt;Not sure what to do about those audio files. Maybe most of those should be played with aplay?&lt;br /&gt;&lt;br /&gt;Anyway, I want to play some more with this. Anyone know of URLs where I can test this further?...&lt;br /&gt;That is, a variety of embedded formats. Or, anyone really interested and wants to setup /etc/mozpluggerrc for all situations? -- go for it!&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01316</link>
		<title>Ntfs-3g 2009.11.14</title>
		<category>Woof</category>
		<description>I have updated the Ntfs-3g driver in the initrd in Woof. Previously it was version 2009.4.4.&lt;br /&gt;&lt;br /&gt;The situation with puppies built with Woof, is you have a ntfs-3g package but that is separate from the ntfs-3g driver that I have put into the initrd. The latter is compiled statically.&lt;br /&gt;&lt;br /&gt;This means that the live-CD has duplication, but I recently made a change in Woof so that when the live-CD is built, executables that are duplicated in the initrd and the main f.s. are deleted in the main f.s., and at bootup they get copied to the main f.s. I posted about this:&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01294 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01294&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have also created a PET package with this statically-compiled ntfs-3g:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/ntfs-3g-2009.11.14-static.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/ntfs-3g-2009.11.14-static.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Static compile howto&lt;/b&gt;&lt;br /&gt;I compiled it with uClibc. A ready-made uClibc ext2 f.s. in a file can be downloaded from the uClibc site. You have to mount it, then chroot into it. Then compile:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# ./configure --prefix=/ --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --target=i486-pc-linux-gnu --disable-mtab --enable-really-static&lt;br /&gt;# make&lt;br /&gt;&lt;br /&gt;secaudit.c:262:24: attr/xattr.h: No such file or directory&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...I don&#39;t think I had that problem with &#39;xattr.h&#39; before. I knew there is a usr/include/sys/xattr.h, so changed secaudit.c to use that, and it compiled. Hmmm.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01315</link>
		<title>Leeman</title>
		<category>General</category>
		<description>Ah, Leeman is your quintessential sleepy seaside village. This is where I parked, that&#39;s my car in the middle:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://puppylinux.com/bkauler/leeman.jpg /&gt;&lt;br /&gt;&lt;br /&gt;I was quite surprised, even though this must be still in the height of the holiday season, there was hardly anyone around.&lt;br /&gt;&lt;br /&gt;There was a lovely cool breeze off the ocean, shady parking, change rooms with shower, and I even found a nice shaded spot on the beach. Heaven!&lt;br /&gt;&lt;br /&gt;Leeman is big enough to have all the facilities, such as general store, fuel, hotel, telecentre, library ...oh yeah, even a tiny hardware store.&lt;br /&gt;&lt;br /&gt;Driving around the town, I noticed quite a lot of for-sale signs. I imagine that&#39;s due to the nature of the place (seasonal holiday destination).&lt;br /&gt;&lt;br /&gt;There was a housing boom in Perth in 2008, that went flat in 2009. Country prices followed, now they are too high I think, that&#39;s why so many for-sale signs:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://reiwa.com.au/real+estate/leeman/ target=_blank&gt;http://reiwa.com.au/real+estate/leeman/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Fool that I was, I made it a day-trip only. I got back to Perenjori before the Post Office closed, and the post-mistress told me that the temperature hit 47 degrees C. It sure felt like it. I watched the weather on TV and they gave Dalwallinu as 45 degrees. Tomorrow is a &quot;cool change&quot;, only 38.&lt;br /&gt;&lt;br /&gt;Next time I go to Leeman, I&#39;m going to stay overnight. Look at this nice caravan park:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.leemancaravanpark.com.au/ target=_blank&gt;http://www.leemancaravanpark.com.au/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I could have pitched my tent there for just 10 dollars:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.leemancaravanpark.com.au/accommodation.html target=_blank&gt;http://www.leemancaravanpark.com.au/accommodation.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01314</link>
		<title>Woof uploaded, January 5, 2010</title>
		<category>Woof</category>
		<description>This is the Woof version used to build Quirky 0.0.3.&lt;br /&gt;&lt;br /&gt;More info on Woof:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01313</link>
		<title>Seaside adventure</title>
		<category>General</category>
		<description>Man, it&#39;s 5am here and already so hot. I don&#39;t use air-conditioning in my house, just a fan. But when the air gets too hot, blowing hot air onto oneself just doesn&#39;t quite do it. &lt;br /&gt;&lt;br /&gt;As the summer advances, the underground water supply pipe gradually warms, so I can&#39;t even have a cold shower, only a warm shower.&lt;br /&gt;&lt;br /&gt;I do have one of those hole-in-the-wall reverse-cycle air-conditioners, but rarely use it. For one thing, it battles to cool even part of my weatherboard house. Then there&#39;s the 15-amp plug -- I don&#39;t have a 15-amp rated outlet.&lt;br /&gt;&lt;br /&gt;I usually find it is better to just make use of nature. In the evening open all the windows and let the cool breeze blow through. Close the windows in the morning and use the fan when it gets a bit too hot.&lt;br /&gt;&lt;br /&gt;The Indian Ocean is about 1.5 hours drive due West of my place, so that&#39;s where I&#39;m heading. There&#39;s a little caravan and camping site on the coast directly West of here, named Leeman. I haven&#39;t been there for ages, can&#39;t recall what it looks like. Strangely enough, I have never before taken the direct route to the ocean from my home, always used to go to the beach at Perth.&lt;br /&gt;&lt;br /&gt;I&#39;m taking my tent, might stay overnight there. Or maybe not. Will just see what happens!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01312</link>
		<title>Quirky 0.0.3 uploaded</title>
		<category>Quirky</category>
		<description>The latest experimental Quirky is available at ibiblio.org:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-003/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-003/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...it has just uploaded and not yet on any mirrors.&lt;br /&gt;&lt;br /&gt;And there is a readme file:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-003/003-readme.htm target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-003/003-readme.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;As you gather from the version number 0.0.3, this is not intended to be anything like a polished release version, or even an alpha or beta.&lt;br /&gt;&lt;br /&gt;Have fun, play with the new ideas.&lt;br /&gt;&lt;br /&gt;Known bug: the Ogle DVD player Stop Button in the GUI doesn&#39;t work. Gposil is working on the Ogle code for Dpup and may have resolved some issues. I just used the original code with patches from Debian.&lt;br /&gt;&lt;br /&gt;For newcomers who are wondering what this &quot;Quirky&quot; thing is all about:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/quirky/ target=_blank&gt;http://bkhome.org/quirky/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01311</link>
		<title>Swfdec: development slowed</title>
		<category>Puppy</category>
		<description>I have joined the Swfdec mail list and posted about my experiences, with a request that the latest Swfdec could return to linking direct with external ffmpeg (and not with gstreamer-ffmpeg). Also sound selection used to allow &#39;alsa&#39; selection, currrently doesn&#39;t (and sound doesn&#39;t work).&lt;br /&gt;&lt;br /&gt;The main developer Benjamin responded, and basically he is focussed on developing it for his particular needs. He has Gstreamer and a particular sound setup, etc. He explained that he is not interested in maintaining anything else, and besides, development has slowed, almost stopped. Well, his words:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;The reason why Swfdec does not support more than one sound system,&lt;br /&gt;HTTP backend or multimedia system is very simple: The main&lt;br /&gt;developer(s) (read: me) only uses one of each and wants to use his&lt;br /&gt;time to improve the Flash player instead of supporting multiple&lt;br /&gt;backends of a non-working player. So every backend that wasn&#39;t updated&lt;br /&gt;whenever necessary was thrown out. It&#39;s not hard to add back, it&#39;s&lt;br /&gt;just that the Swfdec devs don&#39;t want to keep it working.&lt;br /&gt;&lt;br /&gt;That said, active Swfdec development has pretty much stopped, so&lt;br /&gt;you&#39;ll likely not see any new features in the near future anyway.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;So, to move forward with this in our puppies, one of the Puppy developers competent in C coding would have to take it on-board.&lt;br /&gt;&lt;br /&gt;When I release Quirky 003, you can try it out. There are two main issues:&lt;br /&gt;&lt;br /&gt;1.&lt;br /&gt;I&#39;m using Swfdec-mozilla 0.6.0 as this is required for Swfdec 0.6.8-patched. Plays videos ok, but the control buttons are weird, like if you choose to replay. Probably the latest Swfdec-mozilla has improved the user interface.&lt;br /&gt;&lt;br /&gt;2.&lt;br /&gt;I had to compile Swfdec 0.6.8-patched with an older Ffmpeg (2009-02-13) as the latest ffmpeg out of svn caused SeaMonkey to crash whenever tried to view a Flash video.&lt;br /&gt;&lt;br /&gt;Note, if you google around, these two problems, no sound and browser crashing, are common, even with latest Swfdec and Swfdec-mozilla. There are also reports of excessive CPU usage in later versions.&lt;br /&gt;&lt;br /&gt;I came across one person&#39;s report that the 0.6.8 version of Swfdec is the best.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01310</link>
		<title>Mozplugger</title>
		<category>Puppy</category>
		<description>Gposil and I are building puppies without xine/gxine or mplayer, or gstreamer, just ffmpeg. This has been discussed in recent posts.&lt;br /&gt;&lt;br /&gt;Without Gxine, there won&#39;t be any browser plugin, so  technosaurus asked this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;One other ?? Without the gxine plugin, how is normal embedded video handled? swfdec?&lt;br /&gt;&lt;br /&gt;like this (add to body of html template)&lt;br /&gt;&lt;EMBED type=&#39;application/x-mplayer2&#39; src=&quot;http://www.puppylinux.com/test/media-test-video/lionhugsandkisseswoman.wmv&quot; autostart=&quot;true&quot; designtimesp=&#39;5311&#39; loop=&quot;true&quot;&gt;&lt;/EMBED&gt; &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I think that Mozplugger might be a good solution:&lt;br /&gt;&lt;a href=http://mozplugger.mozdev.org/ target=_blank&gt;http://mozplugger.mozdev.org/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;It compiles easily, is very small. The tricky part will be to modify /etc/mozpluggerrc as appropriate for Quirky or Dpup.&lt;br /&gt;&lt;br /&gt;For embedded video is seems that it can be made to swallow ffplay into the browser window. This should be interesting, I&#39;ll have a bit of a play tonight.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01309</link>
		<title>Pmusic: default audio player</title>
		<category>Puppy</category>
		<description>In my latest Quirky, to become 003, Pmusic is the default audio player. So, I have placed the script &#39;pinstall.sh&#39; into the Pmusic PET package:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;#!/bin/sh&lt;br /&gt;&lt;br /&gt;if [ &quot;`pwd`&quot; != &quot;/&quot; ];then&lt;br /&gt;&lt;br /&gt; echo &quot;Configuring Pmusic...&quot;&lt;br /&gt; &lt;br /&gt; if [ ! -e ./usr/bin/aqualung ];then&lt;br /&gt;  echo &#39;#!/bin/sh&#39; &gt; ./usr/local/bin/defaultaudioplayer&lt;br /&gt;  echo &#39;exec pmusic &quot;$@&quot;&#39; &gt;&gt; ./usr/local/bin/defaultaudioplayer&lt;br /&gt;  chmod 755 ./usr/local/bin/defaultaudioplayer&lt;br /&gt; fi&lt;br /&gt;&lt;br /&gt;fi&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;I have created &#39;pmusic-0.9.9-1.pet&#39; and uploaded to the ibiblio.org PET repository.&lt;br /&gt;&lt;br /&gt;Zigbert, if you read this, is it ok for you to put this script in future Pmusic PETs? Otherwise, I&#39;ll manually insert it each time I upgrade Pmusic.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01308</link>
		<title>Woof uploaded, January 3, 2010</title>
		<category>Woof</category>
		<description>I have just uploaded the latest Woof.&lt;br /&gt;&lt;br /&gt;One thing that I have done is remove Shinobar&#39;s &#39;pupsaveconfig&#39;. After using it for awhile, I feel that there are too many questions and steps at shutdown. Also, as I run my puppies from live-CD and do a lot of rebooting, I got very annoyed having to reinsert the CD and press ENTER key each time.&lt;br /&gt;&lt;br /&gt;I can conceive of a simpler way of implementing an X GUI for the pupsave, so will revisit this later.&lt;br /&gt;&lt;br /&gt;Interesting, this was my first need to use &#39;bones diff&#39; to compare the commits where Shinobar&#39;s changes were introduced, and I was easily able to restore the previous files.</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01307</link>
		<title>Ffmpeg recompiled for 003</title>
		<category>Quirky</category>
		<description>Here is a record of what I have compiled, that will (probably) be in Quirky 003:&lt;br /&gt;&lt;br /&gt;i had a problem, after compiling ffmpeg 20091229 and swfdec-mozilla, seamonkey crashes when try play any flash videos (using Swfdec 0.6.8-patched and Swfdec-mozilla) 0.6.0 -- see recent posts).&lt;br /&gt;&lt;br /&gt;so, staying with the ffmpeg from t2 (as used in Quirky 001 and 002)...&lt;br /&gt;i want to recompile it with &#39;ffplay&#39; which requires SDL...&lt;br /&gt;&lt;br /&gt;&lt;b&gt;SDL 1.2.14&lt;/b&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --disable-esd --disable-pulseaudio --disable-arts --disable-mintaudio --disable-video-cocoa --disable-video-directfb --disable-video-opengl --enable-nasm --disable-video-photon --disable-video-carbon --disable-video-ps2gs --disable-video-ps3 --disable-video-ggi --disable-video-vgl&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;&lt;b&gt;amrnb 7.0.0.2&lt;/b&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --with-downloader=wget&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;&lt;b&gt;amrwb 7.0.0.3&lt;/b&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --with-downloader=wget&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;&lt;b&gt;speex 1.2rc1&lt;/b&gt;&lt;br /&gt;# ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --build=i486-t2-linux-gnu &lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;&lt;b&gt;yasm 0.8.0&lt;/b&gt;&lt;br /&gt;x264 needs this to compile. ffmpeg can also use it.&lt;br /&gt;# ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc --build=i486-t2-linux-gnu --disable-python --disable-debug&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;&lt;b&gt;x264 20091230&lt;/b&gt;&lt;br /&gt;tricky, installs to /usr/local, have edited &#39;configure&#39;, changed prefix=&#39;/usr&#39;&lt;br /&gt;note, configure needs &#39;join&#39; command, from coreutils pkg, not in quirky.&lt;br /&gt;hmmm, it ignores the --host=i486 instruction, compiles for i686...&lt;br /&gt;# ./configure --enable-shared --host=i486-t2-linux-gnu --enable-pthread&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;...note, the executables got linked statically with the libx264 library, so have removed them from the PET package, just kept the shared lib as that is what ffmpeg needs.&lt;br /&gt;...note, new2dir failed to grab the symlink /usr/lib/libx264.so&lt;br /&gt;...crap, tried to use in ffmpeg, but configure ran a test and reported &#39;undefined reference to `x264_encoder_open&#39;&#39;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;x264 20090113&lt;/b&gt;&lt;br /&gt;compiled as above. this time it is not compiling for i686!&lt;br /&gt;now for the 64,000 dollar question, is ffmpeg happy? ... yes&lt;br /&gt;&lt;br /&gt;&lt;b&gt;ffmpeg 2009-02-01&lt;/b&gt;&lt;br /&gt;removed  --enable-libvorbis, cos libvorbisenc is 1MB. nah, back in...&lt;br /&gt;# ./configure --prefix=/usr --cpu=i486 --arch=i486 --enable-libmp3lame --enable-libfaac --enable-libfaad --enable-pthreads --enable-small  --enable-postproc --enable-swscale --enable-gpl --enable-shared --enable-nonfree --enable-x11grab --enable-bzlib --enable-libamr-nb --enable-libamr-wb --enable-libspeex --enable-zlib --disable-debug --enable-libvorbis --enable-libx264&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;...works! swfdec flash player works in seamonkey. ffplay works.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Notes&lt;/b&gt;&lt;br /&gt;The latest ffmpeg from svn almost plays RealMedia videos -- I got video, and although it does have the &#39;sipr&#39; audio codec it doesn&#39;t work. On the other-hand, the ffmpeg version above cannot play my RM files at all.&lt;br /&gt;&lt;br /&gt;I really need to look into getting the latest Swfdec working (0.6.8 is an old version) and I intend to communicate with the author about this.&lt;br /&gt;&lt;br /&gt;Then I&#39;ll be able to upgrade to the latest ffmpeg.&lt;br /&gt;&lt;br /&gt;My recent posts on Swfdec:&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01298 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01298&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01299 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01299&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01306</link>
		<title>Multimedia unhappiness</title>
		<category>Quirky</category>
		<description>It took me all morning, I compiled all of these:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;SDL 1.2.14&lt;br /&gt;opencore-amr 0.1.2&lt;br /&gt;speex 1.2rc1&lt;br /&gt;xvidcore 1.2.2&lt;br /&gt;yasm 0.8.0&lt;br /&gt;x264 20091230&lt;br /&gt;ffmpeg 20091229&lt;br /&gt;liboil 0.3.16&lt;br /&gt;libsoup 2.28.2&lt;br /&gt;swfdec 0.6.8-patched&lt;br /&gt;swfdec-mozilla 0.6.0&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...as well as some other stuff, such as Ogle.&lt;br /&gt;&lt;br /&gt;ffplay works nice.&lt;br /&gt;But, whenever I try to view a Flash video, SeaMonkey crashes! Oh dear.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01305</link>
		<title>Ogle DVD player</title>
		<category>Puppy</category>
		<description>We have been discussing a major rethink about multimedia packages in our puppies:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01304 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01304&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I downloaded Ogle and Ogle_gui (GTK2 application) from the project home, but I found both to be buggy. But yes, they do work, and very light-weight.&lt;br /&gt;&lt;br /&gt;But I have just now found that the Debian guys have been patching both ogle and ogle_gui, right up until 2008:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://mirror.aarnet.edu.au/debian/pool/main/o/ogle/ target=_blank&gt;http://mirror.aarnet.edu.au/debian/pool/main/o/ogle/&lt;/a&gt;&lt;br /&gt;&lt;a href=http://mirror.aarnet.edu.au/debian/pool/main/o/ogle-gui/ target=_blank&gt;http://mirror.aarnet.edu.au/debian/pool/main/o/ogle-gui/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;So, it&#39;s looking like Dpup and Quirky are undergoing major changes in the multimedia arena!&lt;br /&gt;&lt;br /&gt;Tonight I&#39;m going to go through and recompile ffmpeg, without x264 only xvid -- as tempestuous suggested. I&#39;ll dump xine and gxine. Ogle_gui for playing DVDs, ffplay for video files. The Adobe Flash player is also gone, replaced with Swfdec. This will all be in Quirky 003, which I hope to upload in a couple of days.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Dpup&lt;/b&gt;&lt;br /&gt;If you want to see ffplay in action as a media player, gposil has just released Dpup 484beta1:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.dpup.org/downloads.html target=_blank&gt;http://www.dpup.org/downloads.html&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01304</link>
		<title>Fundamental questions about multimedia packages</title>
		<category>Puppy</category>
		<description>There is discussion about .3g2 video files playing video but no sound:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=50409 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=50409&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;In Quirky I have just been through the exercise of recompiling ffmpeg (from svn, December 29), with libopencore-amr, x264 and xvid support, as well as all the usual packages in Puppy/Quirky.&lt;br /&gt;&lt;br /&gt;But, I was very disappointed when I played the .3g2 files in Gxine and still no sound.&lt;br /&gt;&lt;br /&gt;Then I tried &#39;ffplay&#39;, a console video player, and hey, I get sound!&lt;br /&gt;&lt;br /&gt;Gposil has been through the same exercise for Dpup, and has also commented how good ffplay is. Incidentally, note that ffplay needs libSDL, so there is a bonus for games if we decide to put ffplay into our puppies.&lt;br /&gt;&lt;br /&gt;Anyway, all of this is making me rethink the fundamentals. I&#39;ve got Swfdec-mozilla compiled against ffmpeg and doing a pretty good job as a Flash player plugin. Well, here are the questions:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;1. x264, xvid&lt;/b&gt;&lt;br /&gt;I am not really clear on why we need these dependencies in ffmpeg. In my general rambling around on the Internet, ffmpeg seems to handle everything, well most files, without these dependencies. What files/streams are going to need these dependencies? In other words, is it really important to have ffmpeg compiled with these dependencies?&lt;br /&gt;&lt;br /&gt;&lt;b&gt;2. Why do we need xine?&lt;/b&gt;&lt;br /&gt;If ffplay can do such a good job at playing videos, and something else such as Pmusic can play audio files, and pCD play audio CDs (I don&#39;t know about DVD videos though), why do we need xine and gxine?&lt;br /&gt;&lt;br /&gt;Regarding question 2, couldn&#39;t we develop our own wrapper for ffplay? Ffplay can even toggle full-screen:&lt;br /&gt;&lt;a href=http://linux.die.net/man/1/ffplay target=_blank&gt;http://linux.die.net/man/1/ffplay&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01303</link>
		<title>Cabernet Shiraz</title>
		<category>General</category>
		<description>&quot;Mr C&quot; (who wishes to remain anonymous) sent me a bottle of Scotts Creek Cabernet Shiraz for Christmas -- but it arrived today, December 31. AU50 dollars cash as well.&lt;br /&gt;&lt;br /&gt;That&#39;s great, I&#39;ll have a glass (or two) this evening. There are a couple of nice musical programs on ABC tonight, so I&#39;ll settle down in front of the TV, glass in hand.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01302</link>
		<title>Woof uploaded, December 31, 2009</title>
		<category>Woof</category>
		<description>This has various improvements, including shinobar&#39;s X GUI &#39;pupsave&#39; script.&lt;br /&gt;&lt;br /&gt;Further information on Woof:&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01301</link>
		<title>&#39;pupsave&#39; X GUI</title>
		<category>Woof</category>
		<description>Shinobar has posted to the forum Quirky 002 feedback thread:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;quirky-002 does shudown by power button if acpid is fixed.&lt;br /&gt;but still has a problem if it is boot up without pupsave(quirkysave).&lt;br /&gt;&lt;br /&gt;boot up without pupsave (asume acpid is fixed), and pressed power button, what happens?&lt;br /&gt;after 30 seconds going to shutdown, then the dialog asking where to save the session appears and waits reply forever.&lt;br /&gt;&lt;br /&gt;one solution is add &#39;--timeout&#39; option with the dialog.&lt;br /&gt;another way is use pupsaveconfig, a GUI tool to setup where to save the session.&lt;br /&gt;&lt;br /&gt;i prepared the pupsaveconfig of the puppy 4.3.1JP ready for quirqy-002.&lt;br /&gt;find pupsaveconfig-1.8.pet available from here: &lt;a href=http://shino.pos.to/linux/puppy/ target=_blank&gt;http://shino.pos.to/linux/puppy/&lt;/a&gt;&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;pupsaveconfig-1.8.pet has /etc/rc.d/rc.shutdown in it, with enhancements to recognise if the pupsave has already been chosen by the X GUI. I have mofified rc.shutdown since 002, with a fix to recognise memory cards that have /dev/mmcblk* device nodes. I have merged my lasted fix with shinobar&#39;s script and placed it at /etc/rc.d in Woof.&lt;br /&gt;&lt;br /&gt;The scripts in pupsaveconfig-1.8.pet are pretty integral to the &#39;rootfs-skeleton&#39; in Woof, so I thought it best to put them directly into the skeleton f.s. in Woof rather than having them as a separate package. The &#39;ja&#39; locale is also in Woof.&lt;br /&gt;&lt;br /&gt;Ok, that is done, shinobar&#39;s &#39;pupsaveconfig&#39; is now builtin to Woof. I&#39;ll upload the latest Woof soon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01300</link>
		<title>acpid fix</title>
		<category>Quirky</category>
		<description>On the forum Quirky 002 feedback thread, shinobar reported:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Quirky-002 does not shutdown by power button because acpi_poweroff attempts to call /usr/X11/bin/wmpoweroff but is not there.&lt;br /&gt;Rewright &#39;/usr/X11/bin/wmpoweroff&#39; to &#39;wmpoweroff&#39; at the bottom of the script /etc/acpi/actions/acpi_power_off.&lt;br /&gt;&lt;br /&gt;Or, install acpid-1.0.8-7.pet available from here: &lt;a href=http://shino.pos.to/linux/puppy/ target=_blank&gt;http://shino.pos.to/linux/puppy/&lt;/a&gt;.&lt;br /&gt;The duration of the closing dialog is adjustable by changing the number &#39;TIMELIMIT=30&#39; at the top of /etc/acpi/actions/acpi_power_off.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I will upload this PET to the Quirky repository at ibiblio.org soon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01299</link>
		<title>Swfdec-mozilla Flash plugin</title>
		<category>Quirky</category>
		<description>I have uploaded liboil 0.3.16, libsoup 2.28.2, libgpg-error 1.7, libgcrypt 1.4.5, gnutls 2.8.5, swfdec 0.6.8 (patched) and swfdec-mozilla 0.6.0 sources:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/ target=_blank&gt;http://bkhome.org/sources/alphabetical/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;To compile the Swfdec player with least dependencies, build as follows:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;liboil 0.3.16&lt;/b&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;&lt;b&gt;libsoup-2.28.2&lt;/b&gt;&lt;br /&gt;disable ssl, compile static lib only...&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --enable-debug=no --disable-shared --enable-static  --without-gnome --disable-ssl&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;&lt;b&gt;swfdec 0.6.8-patched&lt;/b&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --with-audio=alsa --disable-gstreamer --enable-ffmpeg --disable-static --enable-mad&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;&lt;b&gt;swfdec-mozilla 0.6.0&lt;/b&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-t2-linux-gnu --with-plugin-dir=/usr/lib/mozilla/plugins --disable-static&lt;br /&gt;# make&lt;br /&gt;# new2dir make install&lt;br /&gt;&lt;br /&gt;Libsoup is compiled statically into Swfdec as it is somewhat crippled without the SSL support. I could have compiled liboil statically, in fact I could even have compiled Swfdec statically into Swfdec-mozilla for the absolute smallest size.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Gstreamer option&lt;/b&gt;&lt;br /&gt;There is also the option of abandoning Xine and going over totally to Gstreamer. The main problem with that is Gstreamer does not want to compile with external ffmpeg (well, perhaps that could be hacked, but the Gstreamer developers very strongly recommend to use their internal ffmpeg). Puppy has some apps that rely on the external ffmpeg.&lt;br /&gt;It would be interesting to get Gstreamer to compile with external ffmpeg and see how well it works. Swfdec can be compiled against Gstreamer instead of ffmpeg.&lt;br /&gt;&lt;br /&gt;Oh yes, I should report on that. I did compile Swfdec against Gstreamer, and some videos at youtube.com just were a black window -- no video or sound.&lt;br /&gt;On the otherhand, for Swfdec 0.6.8 with ffmpeg, so far I&#39;ve tested about a dozen videos at youtube.com and they all work.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01298</link>
		<title>Swfdec Flash player</title>
		<category>Quirky</category>
		<description>I compiled Swfdec version 0.8.4 and Swfdec-mozilla 0.8.2. The latter is a Flash plugin for Mozilla-based browsers.&lt;br /&gt;&lt;br /&gt;It plays most of the videos at youtube, except for one small problem -- no sound. Running SeaMonkey from a terminal, I get this error message:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;SWFDEC: ERROR: swfdec_audio_decoder.c(232): swfdec_audio_decoder_errorv: error decoding audio: no suitable decoder for audio codec 10&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have done a quick google and this error is reported many times. Have not yet seen a solution, will investigate some more.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01297</link>
		<title>Memtest in Linux</title>
		<category>Puppy</category>
		<description>panzerpuppy wrote:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;How about including Memtest (accessible from the boot menu) in the next build of Quirky?&lt;br /&gt;I really miss this useful app. Great for memory diagnostics and checking the bandwidth/performance of the memory and CPU caches.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;The 2.6.26 and later kernel has memtest builtin, that can be invoked at the boot prompt. See my earlier report:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01142 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01142&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The 2.6.30.5 kernel used in Puppy 4.3.1 is configured with memtest enabled (as is the 2.6.31.5 kernel in Quirky), but I was unable to get anything in &#39;dmesg&#39; despite what Dougal investigated should be happening.&lt;br /&gt;&lt;br /&gt;Obviously I was doing something wrong when I tried to activate it. Maybe there was something in &#39;dmesg&#39; and I overlooked it?&lt;br /&gt;&lt;br /&gt;I wish that I could get this issue resolved. Every now and again someone posts that they would like memtest to be in Puppy, I respond that it is already in the kernel, and there the matter stops, noone resolves it. Would someone take this onboard and solve this mystery? There is probably a very simple solution.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01296</link>
		<title>User Agent Switcher for SeaMonkey</title>
		<category>Puppy</category>
		<description>sage and infectiia have complained that SeaMonkey does not work on the NatWest Bank website.&lt;br /&gt;&lt;br /&gt;I have posted a query about this here:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?p=375342#375342 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?p=375342#375342&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If the &#39;User Agent Switcher&#39; SM addon fixes it, I&#39;ll make it into a PET package and build the next Quirky with it.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;UPDATE:&lt;/b&gt;&lt;br /&gt;I looked at www.nwolb.com (NatWest online banking) and it told me I had the wrong browser. I then installed User Agent Swicher, restarted SM, chose &quot;Internet Explorer 7&quot; (see Tools menu), then tried that site -- this time success. Couldn&#39;t login of course.&lt;br /&gt;&lt;br /&gt;Comment: What a crappy bank, blocking SM. If I had an account there, I would vote with my money, go elsewhere and let them know why.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01295</link>
		<title>Pnethood bugfix</title>
		<category>Quirky</category>
		<description>I was looking through the Quirky 002 feedback thread and thanks to shinobar who posted a fix for Pnethood:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=50319&amp;start=30 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=50319&amp;start=30&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have updated the package, so the next build of Quirky will have the fix.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01294</link>
		<title>Woof uploaded, December 26, 2009</title>
		<category>Woof</category>
		<description>I found myself with a couple of idle hours yesterday, so opened up my laptop and did a little bit of work on Woof.&lt;br /&gt;&lt;br /&gt;There was something I was meaning to do for a very long time, and finally have done it.&lt;br /&gt;&lt;br /&gt;In the Puppy ISO there is some duplication of binary excutables in the &#39;initrd.gz&#39; and &#39;pup-nnn.sfs&#39; main filesystem file. This adds to the size of the ISO.&lt;br /&gt;&lt;br /&gt;What I have done is the &#39;3builddistro&#39; script in Woof deletes the duplicate files in the main f.s., except for &#39;busybox&#39; and &#39;cp&#39; -- the busybox in the main f.s. is different and cp is needed later by the build script. These are the executables that are deleted in the main f.s.:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;guess_fstype modprobe lsmod fusermount e2fsck disktype e3 elspci resize2fs fsck modinfo rev find waitmax hotplug2stdout_notimeout losetup ntfs-3g&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;At bootup, the &#39;init&#39; script copies all of the above from the initramfs to the main f.s., at their correct locations. 3builddistro creates bin/TARGETEXES in the initramfs that lists the executables as well as their correct path in the main f.s., and the init script reads this file.&lt;br /&gt;&lt;br /&gt;Anyway, the end result is surprising, the ISO file is 0.5MB smaller -- all those little apps do add up. This is good, it applies to all puppies/puplets/quirklets built with Woof.&lt;br /&gt;&lt;br /&gt;I have just uploaded this latest Woof. &lt;br /&gt;&lt;br /&gt;Don&#39;t think I&#39;ll be doing anything on Woof/Puppy/Quirky today, got other things to do!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01293</link>
		<title>Woof uploaded, December 24</title>
		<category>Woof</category>
		<description>It is early morning on December 24 here and I am just having a last look on the Internet before heading off for my Xmas break.&lt;br /&gt;&lt;br /&gt;Good thing too, I found this report by playdayz:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=49411 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=49411&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I don&#39;t know about the Python package problem with Upup (or as some people prefer, uPup!), but I have fixed the entries in file &#39;Packages-puppy-woof-official&#39;.&lt;br /&gt;&lt;br /&gt;I have uploaded Woof just now, with the fix. Playdayz, thanks for that.&lt;br /&gt;&lt;br /&gt;Ah, I saw on the news, some of you guys in the US and Europe are snowed under. Today we are having a mild 30 degrees C, tomorrow 36. I&#39;m taking my bathers.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01292</link>
		<title>Woof uploaded December 23, 2009 (again)</title>
		<category>Woof</category>
		<description>As explained in recent blog posts, there is a problem in some cases with hotplugging of memory cards, with the deskop drive icons not appearing (or disappearing).&lt;br /&gt;&lt;br /&gt;See recent posts:&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01291 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01291&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01289 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01289&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I had a solution, that used &#39;dd&#39; to read from removable USB drives every two seconds, however I wasn&#39;t happy with it. I don&#39;t like the idea of a plugged-in card being read every two seconds.&lt;br /&gt;&lt;br /&gt;So, I have worked on /sbin/pup_event_frontend_d and now have it so &#39;dd&#39; only runs when a card is not plugged in. It works nicely, except that removal of a card is now not properly detected, meaning that an icon may remain on the desktop after a card is unplugged -- however I modified /usr/local/bin/drive_all to detect an invalid icon if it is clicked on and it is then removed.&lt;br /&gt;&lt;br /&gt;This is a workable compromise, with low overheads, and most inportantly I think doesn&#39;t keep reading from a card every 2 seconds to see if it is still there.&lt;br /&gt;&lt;br /&gt;Actually, the problem is at the kernel and kernel driver level, and it might go away as the kernel keeps improving. For example, external drive sde, and I plug in a card, /sys/block/sde/sde1 directory appears -- but when I unplug the card that directory remains indefinitely -- until an attempt is made to read from that drive (as with &#39;dd&#39;).&lt;br /&gt;&lt;br /&gt;Anyway, I have uploaded Woof with this latest solution.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01291</link>
		<title>PCMCIA/MMC/SD support at bootup, hotplug drives</title>
		<category>Woof</category>
		<description>&lt;b&gt;Improved PCMCIA/MMC/SD recognition in initramfs&lt;/b&gt;&lt;br /&gt;This was discussed here:&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01289 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01289&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I think that I have got it so that the &#39;init&#39; script will recognise a much wider range of memory cards, so they can be used to hold a &#39;pupsave&#39; file or even booted from (if the BIOS supports it -- unfortunately my Acer Aspire laptop can&#39;t boot from the inbuilt multi-function card slot -- which would have been so nice -- I reckon that&#39;s something to look for if you are shopping for a new laptop).&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Desktop drive icons hotplug support&lt;/b&gt;&lt;br /&gt;The above link has discussion with pakt about a limitation, where a memory card may be plugged or unplugged but there is no desktop drive icon, yet Pmount does recognise it.&lt;br /&gt;&lt;br /&gt;I&#39;ve got an external USB multi-function card reader that has this problem. When plugged in, /sys/block shows that it has sdc, sdd, sde and sdf (in my case), regardless whether any card is plugged in or not.&lt;br /&gt;&lt;br /&gt;Even if I plugin a card, /proc/partitions does not update.&lt;br /&gt;&lt;br /&gt;The only way to detect that a card is inserted is to actually probe it. The &#39;probedisk2&#39; and &#39;probepart&#39; scripts, that are called by Pmount, do this -- they use &#39;dd&#39; to try and read from the card -- this causes /proc/partitions to update.&lt;br /&gt;&lt;br /&gt;I have put this probing into /sbin/pup_event_frontend_d, but in an extremely restrained way, as the scan occurs every 2 seconds and we don&#39;t want an overhead that will noticeably impact on performance -- that is, we don&#39;t want the user to notice any degradation.&lt;br /&gt;&lt;br /&gt;It is working for me. I can plug and unplug an SD card in my multi-function adaptor and the desktop drive icon appears and disappears accordingly.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Woof uploaded, December 23 2009&lt;/b&gt;&lt;br /&gt;I have just uploaded Woof with the above fixes. &lt;br /&gt;&lt;br /&gt;Those unfamiliar with Woof can read more here:&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m going to be taking it easy for the next 5 - 6 days. Have a nice Christmas holiday everyone! For those who don&#39;t have a holiday at this time of year, best wishes also and take it easy too!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01290</link>
		<title>More PETs for Quirky</title>
		<category>Quirky</category>
		<description>Ttuuxxx has already started compiling PET packages for Quirky:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=50364 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=50364&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Of course, older Puppy 2, 3, 4 PETs will also likely work. &lt;br /&gt;&lt;br /&gt;Note, the packages used to build Quirky were recently compiled in T2 so all the libraries are very recent versions.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01289</link>
		<title>SD card support at bootup</title>
		<category>Puppy</category>
		<description>A problem with Puppy is that an internal MMC or SD card is not recognised at bootup. It is recognised after bootup. This means that you can&#39;t use it to boot from or to hold a &#39;pupsave&#39; file.&lt;br /&gt;&lt;br /&gt;By &quot;internal&quot; I mean laptops that have a card reader built-in. A card reader that connects via USB or IDE  interfaces is different.&lt;br /&gt;&lt;br /&gt;I have fixed this on my laptop, which has a Texas Instruments multi-function card reader interface. I presume this is what most laptops would have?&lt;br /&gt;&lt;br /&gt;If you do have a laptop with internal card reader, could you confirm something for me. Run this:&lt;br /&gt;&lt;br /&gt;&gt; elspci -l&lt;br /&gt;&lt;br /&gt;...and see if you get a line with &quot;018000&quot; in it. If so, we&#39;re in business.&lt;br /&gt;&lt;br /&gt;If not, run:&lt;br /&gt;&lt;br /&gt;&gt; lspci&lt;br /&gt;or&lt;br /&gt;&gt; scanpci&lt;br /&gt;&lt;br /&gt;and see if you can identify which line from elspci corresponds to your card reader interface.&lt;br /&gt;&lt;br /&gt;Oh yeah, the kernel modules. On my laptop, these are loaded:&lt;br /&gt;&lt;br /&gt;tifm_sd&lt;br /&gt;mmc_block&lt;br /&gt;mmc_core&lt;br /&gt;tifm_7xx1&lt;br /&gt;tifm_core&lt;br /&gt;&lt;br /&gt;Run &#39;lsmod&#39; to find out what is loaded in your laptop. I&#39;m interested in knowing if your hardware needs some other modules.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01288</link>
		<title>Quirky 0.0.2 uploaded</title>
		<category>Quirky</category>
		<description>I made a very brief announcement here:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-002/002-readme.htm target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-002/002-readme.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The desktop features &quot;Tillman the skateboarding bulldog&quot;.&lt;br /&gt;&lt;br /&gt;Download:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-002/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-002/&lt;/a&gt;&lt;br /&gt;&lt;a href=http://ftp.nluug.nl/ftp/pub/os/Linux/distr/quirky/quirky-002/ target=_blank&gt;http://ftp.nluug.nl/ftp/pub/os/Linux/distr/quirky/quirky-002/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Build 002 is for sanity testing my work on reducing size, so testers welcome. I would like to know if any apps are not working. Look around the menu, there are new things there.&lt;br /&gt;&lt;br /&gt;002 is my Christmas present. Have a nice time everybody. Between now and Christmas I&#39;ll be working on a few things -- like, a few people want booting from SD card (with a laptop inbuilt SD card slot), so I might take a look at that. Then a break for a few days, family get togethers, etc.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01287</link>
		<title>Woof, December 21, 2009</title>
		<category>Woof</category>
		<description>I have just uploaded the latest &lt;b&gt;Woof&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;To download it, you need to install &lt;b&gt;Bones&lt;/b&gt; version 0.1 (which is already in Quirky 002). Read about Bones, also has download link:&lt;br /&gt;&lt;a href=http://bkhome.org/bones/ target=_blank&gt;http://bkhome.org/bones/&lt;/a&gt;&lt;br /&gt;...also explains how to download Woof.&lt;br /&gt;&lt;br /&gt;If you need to catch up on what Woof is all about:&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I will be announcing Quirky 002 soon, built from Woof. This build is pretty much a straight Tpup, but at 88MB a pretty compact starting point for anyone wanting to develop their own Tpup.&lt;br /&gt;Like for example, you could build it with the 2.6.30.5 kernel and all the extra drivers that are bundled with it (like lots of analog modem drivers).&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01286</link>
		<title>Modules loading preferences fix</title>
		<category>Woof</category>
		<description>Rerwin (Richard) has posted this message to the Puppy 431 bugs thread:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Reports of unreliable handling of module preferences, as given in the BootManager Preference option, probably resulted from a bug in the pup_event_backend_modprobe script, which is responsible for the loading of appropriate hardware driver modules. The attached package, pup_event_backend_modprobe_fix_to_p43x-1.pet, resolves that bug and extends the capabilities of the Preference function to (1) provide predictable control over module preferences and (2) support some special cases of module selection and substitution.&lt;br /&gt;&lt;br /&gt;The current implementation of preferences not only can fail to make a substitution, but may load a module other than the one specified, if more than one alternative is appropriate. Specifying the name of a module as a substitute merely results in substitution with whatever module is available for the device; if there are multiple candidates available, the one loaded may not be the one named as the preference.&lt;br /&gt;&lt;br /&gt;This new version of the script extends the preference function by (1) allowing multiple preferences for the same module (separated by a &quot;|&quot; and ordered first-choice-first if needed), the selection being governed by the particular modules that identify themselves as supporting a particular device, and (2) allowing dynamic activation of a set of preferences needed when certain conditions occur. The special preferences reside in /etc/rc.d/MODULESCONFIG as assignment statements setting variables named PREF...; they are not accessible through the BootManager.&lt;br /&gt;&lt;br /&gt;One use of these extensions is for hybrid USB storage-modem devices (e.g., wireless modems), which require two drivers but only one of them normally gets loaded. All such devices may initially require module usb-storage, then need one of several possible modem drivers. If the normally-loaded driver is usb-storage instead of the others, an internally activated preference is used if usb-storage is already loaded (which it normally is), but the modem driver must be the one(s) intended for the modem (known at load time).&lt;br /&gt;&lt;br /&gt;Another use is for supporting ALSA modems that might instead actually be Conexant modems. The Conexant (Linuxant) driver issues an error message if the modem is not a Conexant. In this case, preferences can be activated to force use of the alternate (ALSA) driver after a reboot of Puppy. The new features could support other special module-loading situations as they become known.&lt;br /&gt;&lt;br /&gt;This package/dotpet has been tested with all three kernel versions of Puppy 4.3.1. It should be installed by anyone experiencing a problem with preferred modules not loading (e.g., atl1e instead of atl1c). Do not use this package on Puppies 4.1.x or 4.2.x; instead, use the similar, but bugfix-only package created for those Puppies and available in the Bugs/Fixes threads for 4.1.2 and 4.2.1. Use of the HSF/ALSA reselection requires installation of the new modem &quot;fix pack&quot; package (to be uploaded soon in this thread). This fix can be applied to any Puppy 4.3 installation and is a candidate for inclusion in 4.4CE.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have applied rerwin&#39;s fixes to Woof. The affected files are /sbin/pup_event_backend_modprobe, /etc/rc.d/MODULESCONFIG and /etc/rc.d/rc.sysinit.&lt;br /&gt;&lt;br /&gt;I will probably upload the latest Woof later today.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01285</link>
		<title>Gxine rollback</title>
		<category>Quirky</category>
		<description>I had fun and games with Gxine last night. I found that Gxine 0.5.904 (compiled in T2) crashes with my new cutdown SeaMonkey 1.1.18. Ah, SM 2.0 was compiled in T2 and Gxine uses its libmozjs, so I recompiled Gxine 0.5.904 against the SM 1.1.18 libmozjs ....oh, it still crashes.&lt;br /&gt;&lt;br /&gt;So, I compiled Gxine 0.5.9 against my SM 1.1.18, and that works.&lt;br /&gt;&lt;br /&gt;Interesting, Gxine 0.5.904 was stable when compiled against SM 2.0.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01284</link>
		<title>Quirky 002 soon</title>
		<category>Quirky</category>
		<description>I have updated Pburn to 3.1.7, Precord to 2.0.6 and NicoEdit to 2.5.1.&lt;br /&gt;&lt;br /&gt;Or rather, I made a PET package for the latest NicoEdit, but I have decided to build Quirky 002 with only Geany.&lt;br /&gt;&lt;br /&gt;I have made a little short-list for Quirky 002, which I think I can get through tonight and tomorrow morning, so maybe will upload 002 tomorrow afternoon.&lt;br /&gt;&lt;br /&gt;It&#39;s going to be a &quot;straight Tpup&quot;, normal desktop with JWM and tray on the bottom, usual icons on the desktop. I do intend to play some more with a cleaner desktop, however the purpose of 002 is to test that my efforts to reduce the size still results in a sane system.&lt;br /&gt;&lt;br /&gt;So, try all the apps, printing, scanning, whatever, let me know if anything is broken. Note, I have not yet put in Jemimah&#39;s Pwireless2 -- probably will do that for 003.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01283</link>
		<title>Bones 0.1</title>
		<category>Bones</category>
		<description>Bones is getting a bit more meat on it, and I have now released version 0.1.&lt;br /&gt;&lt;br /&gt;This is a PET package, available from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/bones-0.1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/bones-0.1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Thanks to ecube (Olov) who has contributed a helper-script, bones_diff.pl, Bones is now at the early stage of being able to examine differences between saves.&lt;br /&gt;&lt;br /&gt;There is now a main GUI window, invoked by typing &#39;bones&#39; at the prompt, so Bones is heading towards being highly GUI-fied. I have updated the web page with information:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/bones/ target=_blank&gt;http://bkhome.org/bones/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Does anyone know an easy way to extract just one file out of a .tar.gz, without actually expanding the whole thing? I think Midnight Commander can do it, but I need something standalone for that one purpose only.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01282</link>
		<title>pupRadio and pupTelly</title>
		<category>Puppy</category>
		<description>It seems like just about every day I visit the forum and there is some new exciting project started!&lt;br /&gt;&lt;br /&gt;pupRadio and pupTelly is an example, created by 01micko:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=50016 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=50016&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Puppy 431 has Pstreamvid created by trio:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=45023&amp;search_id=1526069224 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=45023&amp;search_id=1526069224&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;One thing I was wondering, trio modified his script to work specifically with Gxine 0.5.9, but my Quirky has Gxine 0.5.904.&lt;br /&gt;&lt;br /&gt;What about pupRadio/pupTelly, is it happy with either version of Gxine? Of course, your script can read the version of Gxine by&lt;br /&gt;&lt;br /&gt;gxine --help | grep &#39;^gxine &#39; | cut -f 2 -d &#39; &#39;&lt;br /&gt;&lt;br /&gt;...and then behave accordingly.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01281</link>
		<title>Proposed NicoEdit 2.5.1</title>
		<category>Puppy</category>
		<description>I posted a request to this forum thread:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?p=373513#373513 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?p=373513#373513&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;My forum post:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Nicolas, the developer of NicoEdit, is busy with other things right now, so not currently keen to work on NicoEdit.&lt;br /&gt;&lt;br /&gt;Version 2.5 fixed a problem, the PPLOG script did not open. It does not fix the shebang line &#39;#!/bin/ash&#39; detection that I had requested. Also, 2.5 does not have the menu option to manually choose color highlighting -- which 2.4 does have.&lt;br /&gt;&lt;br /&gt;So, is anyone interested in examining 2.4 and 2.5 source and put the menu entry for syntax highlighting back in? -- because NicoEdit does not always autodetect the type of file.&lt;br /&gt;&lt;br /&gt;Also, figure out how to add &#39;#!/bin/ash&#39; to the other shebang lines &#39;#!/bin/sh&#39;, &#39;#!/bin/bash&#39;.&lt;br /&gt;&lt;br /&gt;Then we will have say version 2.5.1.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Anyone interested in having a play with Genie coding?&lt;br /&gt;&lt;br /&gt;NicoEdit source:&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/n/ target=_blank&gt;http://bkhome.org/sources/alphabetical/n/&lt;/a&gt;&lt;br /&gt;User: pup¶py Pass: lin¶ux&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01280</link>
		<title>Precord 2.0.4</title>
		<category>Puppy</category>
		<description>I introduced Precord recently:&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01261 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01261&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Forum:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=49907 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=49907&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Version 2.0.4 is very nice, and will be in Quirky 002. I have a problem with sound being too quiet on my laptop, and I appreciated being able to adjust levels on the mixer and see immediately what sound-level I got -- I found &quot;mic boost&quot; settings that got my recording level high enough.&lt;br /&gt;&lt;br /&gt;A really nice little app!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01279</link>
		<title>pCD 1.1, gtkdialog3 rolled forward</title>
		<category>Quirky</category>
		<description>I have placed zigbert&#39;s pCD version 1.1 audio CD player into Quirky.&lt;br /&gt;&lt;br /&gt;I had previously announced gtkdialog3 patched by Patriot:&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01264 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01264&lt;/a&gt;&lt;br /&gt;But ipinfo was broken so I rolled back:&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01267 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01267&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;However, I have communicated with Patriot, and the ipinfo script is the one that is wrong. Extract from pm from Patriot:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;I&#39;ve taken a look at ipinfo1 and yes, ipinfo1 uses the very method (the bug) that zigbert wishes to be fixed to exit the program ...&lt;br /&gt;&lt;br /&gt;The documented method to exit is &lt;action&gt;exit:exit&lt;/action&gt; ... The closewindow:x method was supposed to close an opened child window (and now working correctly in the patched gtkdialog3) ... My suggested remedy for the ipinfo1 :&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;         &lt;button ok&gt;&lt;br /&gt;            &lt;action&gt;exit:exit&lt;/action&gt;&lt;br /&gt;         &lt;/button&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Or, simply omit the &lt;action&gt; line, as by default gtkdialog will exit if no action is defined.&lt;/i&gt; &lt;br /&gt;&lt;br /&gt;So, I have fixed ipinfo and rolled gtkdialog3 forward again.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01278</link>
		<title>HomeBank 4.1</title>
		<category>Quirky</category>
		<description>There is a new version with lots of bugfixes:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://homebank.free.fr/ target=_blank&gt;http://homebank.free.fr/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have compiled it for Quirky.&lt;br /&gt;&lt;br /&gt;I did not compile-in libofx support, as the &#39;libofx&#39; package needs &#39;opensp&#39; which would not compile.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01277</link>
		<title>Floppy Formatter 1.7</title>
		<category>Quirky</category>
		<description>Forum member 8-bit has incorporated support for both internal and USB floppy drives into his Floppy Formatter package. This is now version 1.7:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?p=367386#367386 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?p=367386#367386&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have added this to Quirky.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01276</link>
		<title>Internet Connection Wizard and ipinfo</title>
		<category>Woof</category>
		<description>I have incorporated the &#39;ipinfo&#39; script into the Internet Connection Wizard, callable by a button.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01275</link>
		<title>gHasher</title>
		<category>Quirky</category>
		<description>A small application to calculate md5 (and other) hashes of files. Discovered by ttuuxxx. I have compiled this for Quirky, and the PET is only 13KB.&lt;br /&gt;&lt;br /&gt;gHasher home:&lt;br /&gt;&lt;a href=http://asgaard.homelinux.org/code/ghasher/ target=_blank&gt;http://asgaard.homelinux.org/code/ghasher/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01274</link>
		<title>Free SoftMaker Office 2008</title>
		<category>General</category>
		<description>For Windows only though. If you are interested, get it from here, but note that the offer expires on December 31:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://loadandhelp.com/home-en.html target=_blank&gt;http://loadandhelp.com/home-en.html&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01273</link>
		<title>Ayttm 0.6.1</title>
		<category>Quirky</category>
		<description>I have compiled Ayttm version 0.6.1 for Quirky. This has support for Yahoo webcam (using the jasper package).&lt;br /&gt;&lt;br /&gt;Project changelog:&lt;br /&gt;&lt;a href=http://ayttm.git.sourceforge.net/git/gitweb.cgi?p=ayttm/ayttm;a=blob;f=ChangeLog;h=9e090ace2c35a722d2dc4a301215e79cef359e38;hb=HEAD target=_blank&gt;http://ayttm.git.sourceforge.net/git/gitweb.cgi?p=ayttm/ayttm;a=blob;f=ChangeLog;h=9e090ace2c35a722d2dc4a301215e79cef359e38;hb=HEAD&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Hmmm, The PETs for Ayttm and Jasper are about 0.9MB, so if I went for Meebo I could save that much off the ISO. But, I am not inclined to move Quirky toward online applications, not yet anyway.&lt;br /&gt;&lt;br /&gt;Regarding release of Quirky 002, I&#39;ll aim to get it out before Christmas, so consider it as my Christmas pressie to ya all.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01272</link>
		<title>Quirky 002 coming soon</title>
		<category>Quirky</category>
		<description>In a few days probably, and I&#39;ll upload Woof as well.&lt;br /&gt;&lt;br /&gt;I have just built the precursor to 002, and the ISO file is &lt;b&gt;87.6MB&lt;/b&gt;. Running it now.&lt;br /&gt;&lt;br /&gt;This has my new tiny SeaMonkey. Noticeably faster startup.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01271</link>
		<title>Compiling SM 1.1.18</title>
		<category>Quirky</category>
		<description>The SM 2.0 PET package is 11.33MB, that of SM 1.1.18 is 10.28MB. As one of the aims of Quirky is to become smaller, I am planning to roll SM back.&lt;br /&gt;&lt;br /&gt;Right now I&#39;m recompiling SeaMonkey 1.1.18, trying some different configure options to see if I can get it even smaller.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01270</link>
		<title>NicoEdit 2.5</title>
		<category>Puppy</category>
		<description>Nicolas has made a couple of small improvements and released version 2.5. &lt;br /&gt;&lt;br /&gt;One of those is to recognise the &quot;shebang line&quot; (first line in a script) of &quot;#!/bin/ash&quot;&lt;br /&gt;&lt;br /&gt;Another was 2.4 refuses to open the PPLOG Perl script. I haven&#39;t tested yet, but that should be fixed now.&lt;br /&gt;&lt;br /&gt;2.5 source:&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/n/nicoedit-2.5.tar.gz target=_blank&gt;http://bkhome.org/sources/alphabetical/n/nicoedit-2.5.tar.gz&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;PET package compiled in Quirky:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/nicoedit-2.5-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/nicoedit-2.5-q1.pet&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01269</link>
		<title>Searchmonkey is back</title>
		<category>Puppy</category>
		<description>Searchmonkey is the best file and file-content finder, but in Puppy4 it crashes, which is why it wasn&#39;t chosen.&lt;br /&gt;&lt;br /&gt;In Quirky however, it works, but then I discovered that the project has been revitalised, and there is a new version, 0.8.1.&lt;br /&gt;&lt;br /&gt;Searchmonkey home:&lt;br /&gt;&lt;a href=http://searchmonkey.embeddediq.com/index.php target=_blank&gt;http://searchmonkey.embeddediq.com/index.php&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;My PET, compiled in Quirky:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/searchmonkey-0.8.1-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/searchmonkey-0.8.1-q1.pet&lt;/a&gt;&lt;br /&gt;...PET size is 92KB.&lt;br /&gt;&lt;br /&gt;I have chosen Searchmonkey as the sole file finder app in Quirky.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01268</link>
		<title>USB Floppy Formatter</title>
		<category>Puppy</category>
		<description>Forum member 8-bit has developed this:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=48053 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=48053&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have repackaged it slightly and uploaded to here:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/usb_floppy_format-1.5-p4.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/usb_floppy_format-1.5-p4.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Note that the package has &#39;ufiformat&#39; in it which is a binary executable (compiled in Puppy4).&lt;br /&gt;&lt;br /&gt;Ufiformat home page:&lt;br /&gt;&lt;a href=http://www.geocities.jp/tedi_world/format_usbfdd_e.html target=_blank&gt;http://www.geocities.jp/tedi_world/format_usbfdd_e.html&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01267</link>
		<title>IPInfo network information</title>
		<category>Woof</category>
		<description>Vovchik has created a nice little GUI application that displays information about the network:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=47262 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=47262&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Some of the information was not displaying properly in the tabs, so I hacked the script a bit to fix it. I also added a &quot;Please wait&quot; message at startup.&lt;br /&gt;&lt;br /&gt;I have placed IPInfo into Woof, at /usr/sbin/ipinfo and created a .desktop file so there is a menu entry.&lt;br /&gt;&lt;br /&gt;Then I noticed that the &#39;Cancel&#39; button did not work. This is due to Patriot&#39;s patched gtkdialog, so I have rolled back to &#39;gtkdialog-0.7.20-1.pet&#39;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01266</link>
		<title>NTFS-backup</title>
		<category>Puppy</category>
		<description>Kirk created a tiny little app that is handy for Windows people. Extract of kirk&#39;s message to me:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;It&#39;s a GUI for ntfsclone, it&#39;s written with xdialog. I&#39;ve used it many times with Windows 2000, XP, and Vista. Ntfsclone is included in Puppy and it&#39;s very fast. My kids hose up their laptops with Vista a lot, with ntfsclone it takes about 15min to restore the c: partition.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have uploaded the PET package here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/ntfs-backup-1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/ntfs-backup-1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...the PET is 2.1KB!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01265</link>
		<title>Pfind 4.16, Pburn 3.1.6</title>
		<category>Quirky</category>
		<description>I have updated zigbert&#39;s apps in Quirky. The PETS will be uploaded soon to:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01264</link>
		<title>gtkdialog 0.7.20-patriot-e-1</title>
		<category>Puppy</category>
		<description>Zigbert recently posted the latest gtkdialog sources that had been patched by Patriot. I think that Patriot had also included patches from Ubuntu. &lt;br /&gt;&lt;br /&gt;I have uploaded this source to here:&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/g/gtkdialog3-0.7.20-patriot-e-1.tar.gz target=_blank&gt;http://bkhome.org/sources/alphabetical/g/gtkdialog3-0.7.20-patriot-e-1.tar.gz&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have compiled it in Quirky/Tpup and uploaded the PET to here:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/gtkdialog3-0.7.20-patriot-e-1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/gtkdialog3-0.7.20-patriot-e-1.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The forum thread where this came from:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?p=357567 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?p=357567&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01263</link>
		<title>dhcpcd 5.1.3</title>
		<category>Quirky</category>
		<description>I have upgraded the package in Quirky. Configuration:&lt;br /&gt;&lt;br /&gt;# ./configure --libexecdir=/lib/dhcpcd --dbdir=/var/lib/dhcpcd --sysconfdir=/etc&lt;br /&gt;&lt;br /&gt;...note, set to /var/lib instead of /var/db.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01262</link>
		<title>gtrayicon_network</title>
		<category>Puppy</category>
		<description>Jemimah uses a patched Gtrayicon v1.1 in Pwireless2. I decided to package the former as a separate package and named it &#39;gtrayicon_network&#39; -- a dumb name, but I&#39;ve done it now.&lt;br /&gt;&lt;br /&gt;The Gtrayicon home page:&lt;br /&gt;&lt;a href=http://gtrayicon.sourceforge.net/ target=_blank&gt;http://gtrayicon.sourceforge.net/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I applied patches by Jemimah and technosaurus from here:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=48816 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=48816&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I uploaded the patched source here:&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/g/gtrayicon_network-1.1.tar.gz target=_blank&gt;http://bkhome.org/sources/alphabetical/g/gtrayicon_network-1.1.tar.gz&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I uploaded the PET package here:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/gtrayicon_network-1.1-q1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/gtrayicon_network-1.1-q1.pet&lt;/a&gt;&lt;br /&gt;...size of PET is 22KB.&lt;br /&gt;&lt;br /&gt;What I aiming for is to pull all of the binary executables out o Jemimah&#39;s Pwireless2 package.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01261</link>
		<title>Precord, Woo-ff, mhWavedit, Pmusic, Asunder</title>
		<category>Quirky</category>
		<description>As I put acpid into Quirky, I wanted to take something out, as one objective for Quirky is to be always moving down in size.&lt;br /&gt;&lt;br /&gt;Hmmm, the acpid PET package is only 12KB. Anyway, I did have in mind something to take out, so have done this...&lt;br /&gt;&lt;br /&gt;I removed Sweep (254KB PET) and replaced it with mhWavedit (172KB PET).&lt;br /&gt;&lt;br /&gt;Then I put in Precord 1.0.2, a sound recorder created by mcewanw:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=49907 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=49907&lt;/a&gt;&lt;br /&gt;...the PET is only 3.4KB.&lt;br /&gt;&lt;br /&gt;I took out Pawdioconverter (has missing Sox dependency, and 12KB PET) and I added Woo-ff 0.1.1, an audio file converter, created by technosaurus:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=45680 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=45680&lt;/a&gt;&lt;br /&gt;...the PET is only 2.6KB!&lt;br /&gt;&lt;br /&gt;The I added zigbert&#39;s Pmusic 0.9.9:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=31206 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=31206&lt;/a&gt;&lt;br /&gt;...the PET is 33KB.&lt;br /&gt;&lt;br /&gt;I replaced Ripoff CD ripper (50KB) with Asunder (45KB).&lt;br /&gt;&lt;br /&gt;...overall I&#39;m down by 15KB!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01260</link>
		<title>Remaster-CD script updated</title>
		<category>Woof</category>
		<description>Shinobar suggested this for 4.4:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=46941&amp;start=180 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=46941&amp;start=180&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;So, I have put this &#39;remasterpup2&#39; script into Woof.&lt;br /&gt;&lt;br /&gt;I know that I have been dragging my feet with regard to adding locale support to my scripts, but shinobar has done so much work on this script, so it is now in Woof -- shinobar has also made improvements, like choice to get the Puppy files from CD or elsewhere.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01259</link>
		<title>acpid</title>
		<category>Quirky</category>
		<description>This looks pretty desirable for laptops. Forum member Patriot has done all the work, see forum:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=38173 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=38173&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Shinobar has been tweaking it for the Japanese Puppy and has PETs available here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://shino.pos.to/linux/puppy/ target=_blank&gt;http://shino.pos.to/linux/puppy/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have decided to put it into Quirky, so I have uploaded the latest from the Japanese Puppy to my Quirky PET repo:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/acpid-1.0.8-6-p4.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/acpid-1.0.8-6-p4.pet&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01258</link>
		<title>915resolution supports GM45</title>
		<category>Puppy</category>
		<description>Continuing from my blog post:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01251 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01251&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Tempestuous has come to the rescue and added support for Intel GM45 video hardware. Forum thread, with latest source and a PET:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=32462 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=32462&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01257</link>
		<title>Puppy Stardust</title>
		<category>Puppy</category>
		<description>Those who love a slim-trim-and-elegant Puppy will like what zigbert has done. Zigbert has taken a standard Puppy 431 and tweaked it:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=49971 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=49971&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The iso is 98MB.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01256</link>
		<title>Woof uploaded</title>
		<category>Woof</category>
		<description>I have uploaded Woof, which has the &#39;CHANGED_ONLY&#39; option for &#39;2createpackages&#39; and GRUB4DOS support in the Universal Installer.&lt;br /&gt;&lt;br /&gt;Note: I have also fixed ext4 support in the Quirky build. Strangely, the e2fsprogs package compiled in T2 does not support ext4, so I change over to our PET package.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01255</link>
		<title>2createpackages improved</title>
		<category>Woof</category>
		<description>There was a comment on the forum that it is a limitation of &#39;2createpackages&#39; in Woof that it can either build one package or build all of them -- the latter takes a long time.&lt;br /&gt;&lt;br /&gt;If you have changed a few packages, say new version and/or added new packages, but can&#39;t recall which ones exactly, I have added a new feature to &#39;2createpackages&#39; that takes care of this.&lt;br /&gt;&lt;br /&gt;In the GUI there is now a &#39;CHANGED_ONLY&#39; selection, or it can be done from the commandline:&lt;br /&gt;&lt;br /&gt;&gt; ./2createpackages CHANGED_ONLY&lt;br /&gt;&lt;br /&gt;This looks to see what packages have been changed/added since last time 2createpackages was run, and only rebuilds those.&lt;br /&gt;&lt;br /&gt;I am just about to test it. If it works, I&#39;ll probably upload the latest Woof in the morning (which also has the GRUB4DOS-compatible Universal Installer).&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01254</link>
		<title>Universal Installer improved</title>
		<category>Woof</category>
		<description>I reported earlier today about shinobar&#39;s GRUB4DOS package:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01252 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01252&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have made this the default in Quirky, removed GRUB.&lt;br /&gt;&lt;br /&gt;I have modified the Universal Installer, /usr/sbin/puppyinstaller, in Woof. It now supports both GRUB and GRUB4DOS, and I made a couple of simplifications as well.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01253</link>
		<title>Bones bugfix</title>
		<category>Bones</category>
		<description>Thanks to playdayz report in the previous blog post, &lt;a href=http://bkhome.org/blog/?viewDetailed=01249 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01249&lt;/a&gt;, I have fixed a bug. Get &#39;bones-11dec2009.gz&#39; from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/test/bones/ target=_blank&gt;http://puppylinux.com/test/bones/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Playdayz, install this latest &#39;bones&#39; script, then run &#39;bones download&#39; again -- this time there should not be any error message.&lt;br /&gt;&lt;br /&gt;For extra peace-of-mind, you can check afterward, run &#39;bones check&#39;, which checks that the database is correct.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01252</link>
		<title>GRUB4DOS</title>
		<category>Puppy</category>
		<description>Forum member shinobar recently posted to the forum about the GRUB4DOS package used in the Japanese edition of Puppy:&lt;br /&gt;&lt;br /&gt;Japanese Puppy: &lt;a href=http://openlab.jp/puppylinux/index.html.en target=_blank&gt;http://openlab.jp/puppylinux/index.html.en&lt;/a&gt;&lt;br /&gt;GRUB4DOS PET package: &lt;a href=http://shino.pos.to/linux/puppy/ target=_blank&gt;http://shino.pos.to/linux/puppy/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I think that I read awhile back that the GRUB in pup 431 has a problem with number of inodes for ext4. Forum member CatDude has researched this and come up with a replacement, which also has a graphical boot interface:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=49873 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=49873&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Both of these are very interesting. I decided to test shinobar&#39;s GRUB4DOS 0.4.4v1.4.1. It has a nice simple GUI and all seemed to go well, but when I booted all I got was this message:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;GRUB Loading stage1.5&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...then it hung.&lt;br /&gt;&lt;br /&gt;The GRUB4DOS GUI offered to install to the MBR of sda, and I accepted the default. But, my PC has mixed SATA and IDE drives, and that is the problem. What Linux sees as sda (SATA), GRUB4DOS looks at the other one first (the IDE drive) -- and I previously had GRUB on the MBR of the IDE drive.&lt;br /&gt;&lt;br /&gt;The solution was to choose sdb MBR to install GRUB4DOS.&lt;br /&gt;&lt;br /&gt;I think that a solution to this problem would be for the GRUB4DOS installer to detect mixed IDE and SATA drives and default to install on the IDE drive. However, I don&#39;t know how to auto-detect that anymore -- on older kernels it was easy, as IDE drives had &#39;hd&#39; naming, SATA drives were &#39;sd&#39;.&lt;br /&gt;&lt;br /&gt;I intend to modify the Puppy Universal Installer to work with shinobar&#39;s GRUB4DOS installer, so I could put in a warning.&lt;br /&gt;&lt;br /&gt;I unplugged the IDE drive, then when I installed GRUB4DOS to sda, it booted ok. The problem is just that search-order, IDE found first.&lt;br /&gt;&lt;br /&gt;One other point to note: I read somewhere that although GRUB4DOS will recognise ext4 partitions, it should not be installed to an ext4 partition. Which I take to mean, if installed to MBR of say sda, with &#39;menu.lst&#39; and &#39;grldr&#39; in sda1, then sda1 must not be ext4.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01251</link>
		<title>915resolution patched</title>
		<category>Puppy</category>
		<description>&#39;915resolution&#39; patches the video BIOS of Intel video hardware to accept non-standard widescreen resolutions (not defined in the VESA standard).&lt;br /&gt;&lt;br /&gt;A Quirky tester reported a problem with 915resolution on their video hardware, so I looked around to see if there are any recent patches.&lt;br /&gt;&lt;br /&gt;Forum member tempestuous did all the work for us for Puppy 4.1.1:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=32462 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=32462&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I am not aware of any Puppy developers patching it since then.&lt;br /&gt;&lt;br /&gt;The Arch Linux guys have patched it fairly recently:&lt;br /&gt;&lt;a href=http://aur.archlinux.org/packages.php?ID=15486 target=_blank&gt;http://aur.archlinux.org/packages.php?ID=15486&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The only extra one that Arch has added is 500GMA. One of the chips that tempestuous identified as 945GM, Arch has identified as 945GME, so I changed that. The only other small thing is that a chip that tempestuous named as GM965, Arch named as 965GM.&lt;br /&gt;&lt;br /&gt;So, I have patched the source so that it now supports all of these:&lt;br /&gt;&lt;br /&gt;&quot;500GMA&quot;, &quot;830&quot;, &quot;845G&quot;, &quot;855GM&quot;, &quot;865G&quot;, &quot;915G&quot;, &quot;915GM&quot;, &quot;945G&quot;, &quot;945GM&quot;, &quot;945GME&quot;, &quot;946GZ&quot;,   &quot;G965&quot;, &quot;Q965&quot;, &quot;GM965&quot;, &quot;G33&quot;&lt;br /&gt;&lt;br /&gt;The source is at:&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/9/915resolution-0.5.3-patched20091210.tar.gz target=_blank&gt;http://bkhome.org/sources/alphabetical/9/915resolution-0.5.3-patched20091210.tar.gz&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have uploaded a PET package to here:&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/915resolution-0.5.3-patched20091210.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/pet_packages-quirky/915resolution-0.5.3-patched20091210.pet&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01250</link>
		<title>Woof uploaded</title>
		<category>Woof</category>
		<description>I posted recently about improvements to placement of desktop drive icons on the desktop, and improved &#39;bones&#39; script.&lt;br /&gt;&lt;br /&gt;This is all in Woof and I have just uploaded it to the Bones online repository.&lt;br /&gt;&lt;br /&gt;But, you do need the latest &#39;bones&#39; script to download Woof, &#39;bones-10dec2009.gz&#39;, see previous post.&lt;br /&gt;&lt;br /&gt;Intro and how to use Bones, see my blog posts:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewCat=Bones target=_blank&gt;http://bkhome.org/blog/?viewCat=Bones&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01249</link>
		<title>Bones updated</title>
		<category>Bones</category>
		<description>I have improved the &#39;bones&#39; script, and you now have to use this one. Get &#39;bones-10dec2009.gz&#39; from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/test/bones/ target=_blank&gt;http://puppylinux.com/test/bones/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...gunzip it, set it executable, place at /usr/sbin.&lt;br /&gt;&lt;br /&gt;The .delta files have a different naming, with both previous and latest dates in them.&lt;br /&gt;&lt;br /&gt;There is improved database checking, and &#39;bones check&#39; will perform a database integrity check.&lt;br /&gt;&lt;br /&gt;If you have already downloaded Woof, running &#39;bones download&#39; with the new script will automatically update to the new .delta files (I think).&lt;br /&gt;&lt;br /&gt;I tested a brand new download, works fine.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01248</link>
		<title>Full control of desktop drive icon placement</title>
		<category>Woof</category>
		<description>In Puppy 4.3.x, the desktop drive icons are restricted to running along the bottom of the screen, just above the tray.&lt;br /&gt;&lt;br /&gt;I have now made placement totally configurable. It is controlled by these variables in /etc/eventmanager:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;#091208 adjust drive icons placement, read by /sbin/pup_event_frontend_d&lt;br /&gt;#TODO: GUI in /usr/sbin/eventmanager&lt;br /&gt;#gap between icons and edge of screen (&gt;0 if need to leave space for a tray)...&lt;br /&gt;ICON_PLACE_EDGE_GAP=64&lt;br /&gt;#indent from edge before icons start...&lt;br /&gt;ICON_PLACE_START_GAP=32&lt;br /&gt;#spacing between successive icons (64 matches other desktop icons)...&lt;br /&gt;ICON_PLACE_SPACING=64 #56&lt;br /&gt;#left, right, bottom, or top of screen...&lt;br /&gt;ICON_PLACE_ORIENTATION=&#39;bottom&#39;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;The script /sbin/pup_event_frontend_d reads these and draws the icons. Hopefully theywill avoid other icons.&lt;br /&gt;&lt;br /&gt;Another improvement is that if there are too many partitions to fit on one line (or column), it wraps to another line (or column).&lt;br /&gt;&lt;br /&gt;This is done in Woof, but I won&#39;t upload it just yet. I want to improve something in Bones first, so I&#39;ll upload in a day or two.&lt;br /&gt;&lt;br /&gt;Anyone can put code into the &#39;pinstall.sh&#39; script of a package to modify these variables. I have done so my &#39;rox-panel-quirky&#39; package, to draw the drive icons right at the bottom of the screen. I also modified the default spacing from 64 to 56, as I think they look nicer slightly closer together.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01247</link>
		<title>Flwm, wmx window managers</title>
		<category>Quirky</category>
		<description>Jemimah is using Flwm, so I took a look at it. First I compiled FLTK, version 1.1.10rc3:&lt;br /&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --disable-gl --enable-xdbe --enable-xft --enable-threads --enable-xinerama --enable-largefile&lt;br /&gt;&lt;br /&gt;Then Flwm (which needs FLTK):&lt;br /&gt;I edited config.h:&lt;br /&gt;&lt;br /&gt;#define CLICK_TO_TYPE 1&lt;br /&gt;#define TITLE_FONT &quot;DejaVu Sans&quot;&lt;br /&gt;#define MENU_FONT &quot;DejaVu Sans&quot;&lt;br /&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --host=i486-t2-linux-gnu&lt;br /&gt;&lt;br /&gt;...there were some compile errors, had to do a couple of hacks to get it to compile. Fltk was linked statically and I got a &#39;flwm&#39; executable at 202KB.&lt;br /&gt;&lt;br /&gt;I also got Flwm out of CVS, noticed the code is quite old, like 2000. It appears to be based on an old version of wmx. I thought it would support Xft (as wmx does) which is why I specified &#39;DejaVu Sans&#39; font, but it only displays a bitmap font.&lt;br /&gt;&lt;br /&gt;wmx version 7 is more recent code and does support Xft. It does not use FLTK. The executable is 140KB. I&#39;m running it now, but it lacks the extra title-bar buttons that the Flwm developer put in, which makes it awkward to use -- like, how to maximise a window? -- you need to know a key-combination, can&#39;t do it with the mouse.&lt;br /&gt;&lt;br /&gt;One interesting feature of both of these is they have the title bar on the side of the window, which might be good for small widescreen netbooks.&lt;br /&gt;&lt;br /&gt;Flwm: &lt;a href=http://flwm.sourceforge.net/ target=_blank&gt;http://flwm.sourceforge.net/&lt;/a&gt;&lt;br /&gt;wmx: &lt;a href=http://xwinman.org/wm2.php target=_blank&gt;http://xwinman.org/wm2.php&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01246</link>
		<title>Fluppy puplet</title>
		<category>Puppy</category>
		<description>Jemimah is doing great work, optimising Puppy for small widescreens:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=47192 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=47192&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&quot;Fluppy&quot; is a proposed puplet that will incorporate these ideas.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01245</link>
		<title>Password protected sources</title>
		<category>Woof</category>
		<description>I have added password protection to access:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/sources/ target=_blank&gt;http://bkhome.org/sources/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;My laptop was chugging away all night uploading most of the source packages that I used for the T2 build.&lt;br /&gt;&lt;br /&gt;The problem is though, when it becomes widely known that I have a very nice repository of source packages, and especially when people decide to download everything, I am going to run into problems with my host. My account with Hostgator has &quot;unlimited downloads&quot; however it isn&#39;t really, as it is one of those cheap shared accounts (&quot;Baby Croc&quot;).&lt;br /&gt;&lt;br /&gt;This &quot;download everything&quot; problem is going to occur with Woof Tpup builds, as I am uploading most of the packages that I used to build my latest Tpup. It is better that when people use T2, just let it try and get the required packages from the T2 repositories or the author&#39;s sites. My site can be a last resort.&lt;br /&gt;&lt;br /&gt;My username and password is the same that Eric is using, &quot;pup¶py&quot; and &quot;lin¶ux&quot;. -- probably not necessary, but they are displayed here slightly obfuscated.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01244</link>
		<title>Playing with Echinus and Oroborus</title>
		<category>Quirky</category>
		<description>These are tiny window managers. Unfortunately they both have something wrong with them.&lt;br /&gt;&lt;br /&gt;I&#39;m running Oroborus right now, version 2.0.18. Looks nice. The only problem that I have encountered so far is that when I click an icon in the ROX Panel, nothing appears on the desktop -- I have to then click in the desktop for the application to appear. Weird.&lt;br /&gt;&lt;br /&gt;Home: &lt;a href=http://www.oroborus.org/ target=_blank&gt;http://www.oroborus.org/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;An aesthetic thing: these days window managers should support xft, even minimalistic ones.&lt;br /&gt;&lt;br /&gt;Echinus has been discussed recently on the forum:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=47476 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=47476&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I compiled version 0.3.9. It is delightfully tiny and simple. Unfortunately, when I right-click on a file in a ROX-Filer window the menu appears underneath the window! (only in floating mode, it&#39;s ok in tiled mode). Also, there doesn&#39;t seem to be any way to drag-resize a window.&lt;br /&gt;&lt;br /&gt;So for me the only windows managers that I have been satisfied with are still JWM and Openbox.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01243</link>
		<title>Woof page updated</title>
		<category>Woof</category>
		<description>I have updated the Woof introduction page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This includes explanation of how to get Woof out of the Bones online repository.&lt;br /&gt;&lt;br /&gt;Note, I have just now updated Woof online, so it&#39;s my very latest, that I used to build Quirky 001 -- plus I fixed a couple of bugs in the &#39;devx&#39; (a couple of missing symlinks).&lt;br /&gt;&lt;br /&gt;A warning about &#39;bones download&#39;...&lt;br /&gt;The first time that you run &#39;bones download&#39; that&#39;s fine, you will then have Woof. After that, if you see an announcement on my blog that I have uploaded a new version of Woof, you can run &#39;bones download&#39; again to sync with the latest code. Note however, if you have modified any of the files, they will get over-written.&lt;br /&gt;&lt;br /&gt;You would need to backup any customised files first. This is an area that I plan to improve.&lt;br /&gt;&lt;br /&gt;Note that if you have user customisations that you think I might want to incorporate into Woof, if you run &#39;woof save&#39; it will create a delta file in directory &#39;woof-bones&#39; that you can email to me.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01242</link>
		<title>Quirky version 0.0.1</title>
		<category>Quirky</category>
		<description>The live-CD ISO file is 90.36MB and available from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-001/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-001/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;There is also a README file:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-001/001-readme.htm target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/quirky/quirky-001/001-readme.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...which explains that this release only has a &quot;quirkiness factor&quot; of one.&lt;br /&gt;&lt;br /&gt;I have only just uploaded it, it hasn&#39;t got through to the mirrors yet.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01241</link>
		<title>A clean screen for netbooks</title>
		<category>Quirky</category>
		<description>I am working on a different desktop for Quirky, that is more usable for small widescreen netbooks.&lt;br /&gt;&lt;br /&gt;A tray along the bottom or top (or even worse, both) is not the best for a small wide-screen, as there tends to be more &quot;free space&quot; not required by windows at the sides.&lt;br /&gt;&lt;br /&gt;Then of course we have icons on the desktop, and windows have to be dragged aside to get at them.&lt;br /&gt;&lt;br /&gt;I was inspired by Jemimah to take another look at using the ROX panel instead of the JWM tray. Right now I&#39;m playing with a panel on the right side, the drive icons moved down slightly so they are right at the bottom of the screen, and all the other desktop icons removed.&lt;br /&gt;...I&#39;ll probably upload the first Quirky ISO with this.&lt;br /&gt;&lt;br /&gt;For the record, the packages required are:&lt;br /&gt;&lt;br /&gt;libwnck-2.26.2-p4.pet&lt;br /&gt;rox-clib-2.1.10-q1.pet&lt;br /&gt;rox-clib_DEV-2.1.10-q1.pet&lt;br /&gt;rox-menu-0.5.0.pet&lt;br /&gt;rox-monitor-applets-1-p4.pet&lt;br /&gt;roxpanel-pager-1.2-p4.pet&lt;br /&gt;rox-panel-quirky-1.pet&lt;br /&gt;roxpanel-systray-0.3.2-p4.pet&lt;br /&gt;roxpanel-taskbar-0.4-p4.pet&lt;br /&gt;&lt;br /&gt;These will be available on my ibiblio Quirky site.&lt;br /&gt;&lt;br /&gt;&#39;rox-panel-quirky-1.pet&#39; has configuration stuff to set things up properly for Quirky.&lt;br /&gt;&lt;br /&gt;Most of the other packages are just Jemimah&#39;s packages re-badged.&lt;br /&gt;&lt;br /&gt;I don&#39;t know if I&#39;ll stay with this though, due to the size overhead. Next, I might experiment with a JWM tray on the right side. We&#39;ll see...&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01240</link>
		<title>Why you should NOT visit Australia</title>
		<category>General</category>
		<description>Heh heh, see the forum:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?p=369573#369573 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?p=369573#369573&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01239</link>
		<title>Quirky page expanded</title>
		<category>Quirky</category>
		<description>Here it is:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/quirky/ target=_blank&gt;http://bkhome.org/quirky/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;There is still no actual ISO to download, but I&#39;m getting there. I keep finding stuff to either fix or improve.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01238</link>
		<title>Inkscapelite</title>
		<category>Quirky</category>
		<description>This is also known as &quot;InkLite&quot; in the menu. Inkscapelite is a fork of Inkscape 0.36pre0, the last version to be written in C. After that, they rewrote it in C++ and also used GTKmm -- and my oh my did it ever jump up in size, especially if you linked the GTKmm libs statically.&lt;br /&gt;&lt;br /&gt;Technosaurus and ttuuxxx were discussing Inkscapelite recently on the forum, in regard to its dependence on &#39;libgnomeprint&#39; and &#39;libgnomeprintui&#39;. &lt;br /&gt;&lt;br /&gt;I have also taken those two libraries out of Quirky, so I wanted to recompile Inkscapelite either statically with those libs, or without -- Inkscapelite has a configure option &#39;--without-gnome-print&#39; which I chose -- the application can still print, but it is very basic.&lt;br /&gt;&lt;br /&gt;The problem is, the only source package I can find is &#39;inkscapelite-0.36.2.tar.gz&#39; but Puppy currently has version 0.36.3. Maybe I have it archived somewhere, but anyway I used the 0.36.2 source and compiled that -- one file needed a small hack to get it to compile, so perhaps that is what was done before when I created 0.36.3. So I decided that I might as well name this as version 0.36.3 and I have uploaded it here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/sources/alphabetical/i/ target=_blank&gt;http://bkhome.org/sources/alphabetical/i/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If anyone has that original 0.36.3 source, I would like to see it, find out if I did anything else.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01237</link>
		<title>T2 web page</title>
		<category>Woof</category>
		<description>I have updated my web page on T2:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/t2/ target=_blank&gt;http://bkhome.org/t2/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://bkhome.org/t2/t2logo115x96.png /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01236</link>
		<title>gcc 4.3.4 recompiled</title>
		<category>Quirky</category>
		<description>An old problem has come back. Previously when I compiled in T2, such as the base packages for Puppy 4.0, there was a problem with the gcc compiler. When using it in an alpha of Puppy 4.0, some packages would not compile, with error &quot;__sync_fetch_and_add_4 undefined&quot;. I reported this, and the solution, in my news archive (do a search for &quot;gcc bug fixed&quot;):&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.puppylinux.com/news/news400a3-400a5.htm target=_blank&gt;http://www.puppylinux.com/news/news400a3-400a5.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;With the recent T2 compile I made some changes that I thought would have fixed this problem, but not so. It has to do with the cross-compile environment that T2 runs in. So, here we go again...&lt;br /&gt;&lt;br /&gt;These are patches I got out of T2, and the configure parameters are based on information in var/adm/logs/5-gcc.log in the T2 build:&lt;br /&gt;&lt;br /&gt;# patch -p1 &lt; ../fixincl.patch&lt;br /&gt;# patch -p1 &lt; ../fixincl2.patch&lt;br /&gt;# patch -p1 &lt; ../libstdcpp-with-tag-cc.patch&lt;br /&gt;# patch -p1 &lt; ../no-install-libiberty.patch&lt;br /&gt;# patch -p1 &lt; ../stdc++-include_next.patch&lt;br /&gt;&lt;br /&gt;# mkdir objdir&lt;br /&gt;# cd objdir&lt;br /&gt;# ../configure --prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libdir=/usr/lib --datadir=/usr/share --includedir=/usr/include --infodir=/usr/info --mandir=/usr/man --sysconfdir=/etc --localstatedir=/var --disable-debug --without-libpam --without-pam --disable-libpam --disable-pam --build=i486-t2-linux-gnu --enable-__cxa_atexit --disable-checking --disable-bootstrap --disable-libstdcxx-pch --disable-multilib --with-gnu-as --with-gnu-ld --enable-threads=posix --disable-libgcj --enable-languages=c,c++,fortran --enable-shared&lt;br /&gt;&lt;br /&gt;...it&#39;s compiling right now. Gonna take awhile, it&#39;s a big package. &lt;br /&gt;&lt;br /&gt;Note, this time I have enabled the Fortran compiler, which is missing from the Puppy 4.x series.&lt;br /&gt;&lt;br /&gt;This is delaying the upload of the first pre-alpha of Quirky for a couple more days. I found bugs with Abiword 2.8.1, so I wanted to try compiling Abiword from SVN, and I also recompiled the Enchant package or rather tried to -- I hit that &quot;__sync_fetch_and_add_4&quot; bug.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01235</link>
		<title>2.6.31.5 kernel</title>
		<category>Quirky</category>
		<description>I am using the 2.6.31.5 kernel for Quirky.&lt;br /&gt;&lt;br /&gt;The patched source tarball and SFS are here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/sources/kernel-2.6.31.5/ target=_blank&gt;http://bkhome.org/sources/kernel-2.6.31.5/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01234</link>
		<title>Logos from afgs</title>
		<category>Woof</category>
		<description>Forum member afgs has been doing great things with the logos:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=48880 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=48880&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Here is a Quirky logo:&lt;br /&gt;&lt;img src=http://bkhome.org/quirky/quirky-grey96x96.png /&gt;&lt;br /&gt;&lt;br /&gt;And this is what it looks like in a web page:&lt;br /&gt;&lt;a href=http://bkhome.org/quirky/ target=_blank&gt;http://bkhome.org/quirky/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Here is a Woof logo:&lt;br /&gt;&lt;img src=http://bkhome.org/woof/woof-grey96x96.png /&gt;&lt;br /&gt;&lt;br /&gt;And this is what it looks like in a web page:&lt;br /&gt;&lt;a href=http://bkhome.org/woof/ target=_blank&gt;http://bkhome.org/woof/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01233</link>
		<title>SM2 rendering problem</title>
		<category>General</category>
		<description>I have just booked a return flight to Melbourne to visit my daughter next year. Tiger Airways are offering advance booking low fares ($100 each way).&lt;br /&gt;&lt;br /&gt;Before booking, I tried to look at the prices on offer from Jetstar:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.jetstar.com/au/en/index.aspx target=_blank&gt;http://www.jetstar.com/au/en/index.aspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...however, rendering is awful. So bad I was unable to fill in the flight search form.&lt;br /&gt;&lt;br /&gt;I&#39;m using SeaMonkey 2.0 every day now, and when I first started using it I was pleased that now I am using the same rendering engine as Firefox 3.5. But now I&#39;m not so pleased.&lt;br /&gt;&lt;br /&gt;Anyone reading this who is running SM 1.1.18, does that site render ok for you? Firefox? Opera?&lt;br /&gt;&lt;br /&gt;I&#39;m increasingly thinking I might go back to SM 1.1.18.&lt;br /&gt;&lt;br /&gt;Another thing that is broken in SM2 is drag-and-drop of URLs. I used to be able to drag a file from the web browser window to any open ROX-Filer window, and wget would start and download it -- very convenient -- wget is much better than the SM Downloader. However with SM2, wget reports that the URL is broken.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01232</link>
		<title>Testing Bones</title>
		<category>Bones</category>
		<description>Seems to be ok for basic usage. I have uploaded the Woof project as a Bones repository. So, to get hold of the latest Woof, do this:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;1.&lt;/b&gt; Obtain latest &#39;bones&#39; script&lt;br /&gt;From Here: &lt;a href=http://puppylinux.com/test/bones/ target=_blank&gt;http://puppylinux.com/test/bones/&lt;/a&gt;&lt;br /&gt;...gunzip it, set it executable and place at /usr/sbin.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;2.&lt;/b&gt; Bones setup&lt;br /&gt;In a Linux partition, do this:&lt;br /&gt; &gt; mkdir woof-tree&lt;br /&gt; &gt; cd woof-tree&lt;br /&gt; &gt; bones setup&lt;br /&gt;...enter a local username&lt;br /&gt;...enter url for woof project: http://bkhome.org/bones/woof/&lt;br /&gt;&lt;br /&gt;&lt;b&gt;3.&lt;/b&gt; Download Woof&lt;br /&gt; &gt; bones download&lt;br /&gt;&lt;br /&gt;After step 3 you are ready to use Woof.&lt;br /&gt;&lt;br /&gt;Further information: &lt;a href=http://bkhome.org/bones/ target=_blank&gt;http://bkhome.org/bones/&lt;/a&gt;&lt;br /&gt;Please report any bugs!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01231</link>
		<title>More Bones</title>
		<category>Bones</category>
		<description>I&#39;m back! I was in Perth for the weekend + Monday.&lt;br /&gt;&lt;br /&gt;I did a little bit of work on Bones, fleshed out the script a lot. I focused on getting the round-trip to work, that is, from the administrator (me) saving, uploading, then the user downloading, using, maybe contributing to Woof development.&lt;br /&gt;&lt;br /&gt;Well, I did what I could without having an actual Internet connection. My daughter on the otherhand, had an iPhone plugged into her laptop and had Internet access.&lt;br /&gt;&lt;br /&gt;Anyway, I wrote-up progress so far:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/bones/ target=_blank&gt;http://bkhome.org/bones/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01230</link>
		<title>Bones version control</title>
		<category>Bones</category>
		<description>A personal, tiny, and very simple version control system that does what I want for managing the Woof project:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/bones/ target=_blank&gt;http://bkhome.org/bones/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://bkhome.org/bones/bones416x304.png /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01229</link>
		<title>Offline for a few days</title>
		<category>Woof</category>
		<description>An announcement to let everyone know why I won&#39;t be posting here for awhile.&lt;br /&gt;&lt;br /&gt;My daughter is flying over from Melbourne to Perth for the weekend, so I&#39;ll be in Perth staying with one of my sisters -- she doesn&#39;t have an Internet connection.&lt;br /&gt;&lt;br /&gt;However, I will be continuing to work on the Tpup build, and plan to upload an alpha when I get back home. It works fine right now, I&#39;m very pleased and using it as my regular daily distro. But, I should do more testing and refining.&lt;br /&gt;&lt;br /&gt;There&#39;s a difference between Tpup and Quirky, in case you&#39;re confused! Tpup is just your usual Puppy-derivative or puplet built with Woof, similar to Dpup and Upup but instead built from T2 packages.&lt;br /&gt;&lt;br /&gt;Quirky just twists it a bit, adds the quirks. In Woof, it&#39;s an extra script, &#39;4quirkybuild&#39;. The only quirky thing that I have done so far is put everything into the &#39;vmlinuz&#39; kernel so that the entire distro is just one file.&lt;br /&gt;&lt;br /&gt;So I&#39;ll describe the build as &quot;Tpup&quot; if it is a normal puplet, and as &quot;Quirky&quot; if it has the quirks. Early next week I might just upload Tpup, or I suppose I could upload both.&lt;br /&gt;&lt;br /&gt;There&#39;s another quirky idea I&#39;m keen to work on, soon as I get the time. The days aren&#39;t long enough for me!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01228</link>
		<title>Printing now works</title>
		<category>Woof</category>
		<description>Testing my Tpup, I recently reported trouble with printing. As reported, I rolled back to CUPS 1.3.11 which fixed recognition of my USB printer, however I got a &quot;foomatic-rip failed&quot; message when I tried to print.&lt;br /&gt;&lt;br /&gt;It turned out to be a missing Perl script that foomatic-rip requires, &#39;Hash.pl&#39;. This script is part of the Perl package, however Puppy uses a cutdown Perl, very cutdown. I modified the Perl template in Woof to include this script.&lt;br /&gt;&lt;br /&gt;Then I discovered a problem in /usr/sbin/cups_shell. As I&#39;m using SM2 I don&#39;t have MU&#39;s lovely PuppyBrowser and have to use SM as the internal help viewer, also for the CUPS web interface.&lt;br /&gt;cups_shell starts SM with a help page, then tries to open the CUPS web interface. The latter fails as SM needs a couple of seconds to start the help page, more time on older PCs. I fixed this.&lt;br /&gt;&lt;br /&gt;Hey, my latest Tpup is just 90MB!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01227</link>
		<title>SeaMonkey 2.0 quibbles</title>
		<category>Puppy</category>
		<description>For day-to-day usability I&#39;m not so happy with SM 2.0 compared with 1.1.18. Three quibbles:&lt;br /&gt;&lt;br /&gt;1. Keeps asking if want to remember password, even when I reply &quot;never for this site&quot;.&lt;br /&gt;2. Sometimes at startup, SM apologises that previous session did not close down properly and do I want to restart with previous session or a new session. However, I did close SM down properly previously.&lt;br /&gt;3. SM remembers form and search entries. Trouble is, when I login to gmail, I type my username and SM displays it in a drop-down list which covers the password field. The drop-down won&#39;t go away unless I click elsewhere. Annoying. I changed Preferences to not remember form and search history.&lt;br /&gt;&lt;br /&gt;So, I don&#39;t think SM 2.0 is quite ready for prime-time.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01226</link>
		<title>Dpup beta5 coming</title>
		<category>Puppy</category>
		<description>Gposil and team have been busy developing the next-generation Puppy, that we have been terming &quot;Puppy5&quot;. Gposil has announced that beta5 should be uploaded tonight. Follow development here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47592 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47592&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Here is the Dpup home site:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.dpup.org/ target=_blank&gt;http://www.dpup.org/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I was just thinking yesterday, we have the &quot;pet_packages-5&quot; directory sitting virtually empty at ibiblio.org. So, that could be a home for Dpup PET packages. I won&#39;t manage uploading to it though -- Gposil or someone can have ftp access to it.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01225</link>
		<title>Another Woof logo</title>
		<category>Woof</category>
		<description>My daughter has designed a Woof logo:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://puppylinux.com/woof/woof-logo-yellow761x761.png /&gt;&lt;br /&gt;&lt;br /&gt;...I messed it up a bit though. Making it&#39;s proportions square, some shading is chopped off the bottom. if anyone wants to tweak it, go for it.&lt;br /&gt;&lt;br /&gt;I also put it into my web page to see what it looks like:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/woof/ target=_blank&gt;http://puppylinux.com/woof/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...quite nice!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01224</link>
		<title>Xorg Wizard bugfix</title>
		<category>Woof</category>
		<description>I&#39;m knocking off the bugs with this T2-based-pup.&lt;br /&gt;&lt;br /&gt;I&#39;m running Xorg with the &#39;vesa&#39; driver, and Xorg Wizard does not display the vertical and horizontal frequencies when testing a video mode. Fixed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01223</link>
		<title>T2 binary packages</title>
		<category>Woof</category>
		<description>The third run of T2 was completed yesterday, and I am pleased with the outcome. So, I have once again uploaded all the binary packages that were compiled in T2 to here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/binaries/t2/ target=_blank&gt;http://bkhome.org/binaries/t2/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;These are the raw packages that can used by Woof to build a &quot;tpup&quot;. I plan to use these as the basis for Quirky Linux.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01222</link>
		<title>Eliminate Type1 and most bitmap fonts?</title>
		<category>Woof</category>
		<description>I think that ttuuxxx and kirk have both been down this track. That is, replace most of the Type1 and bitmap fonts with TTF fonts. Objectives: better looking and save space.&lt;br /&gt;&lt;br /&gt;I have just done a bit of a search on the forum and can&#39;t find this documented. Guys, have you posted anything about this anywhere?&lt;br /&gt;I have a vague memory that ttuuxx sent me something awhile back.&lt;br /&gt;&lt;br /&gt;The T2 build has Xorg 7.5, which is working fine. Now, 7.5 is much more TTF-capable, so opportunity is definitely there to remove the older fonts.&lt;br /&gt;&lt;br /&gt;The only reservation I have is Ghostscript, that may have some need for Type1 fonts to render some .ps and .eps files.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01221</link>
		<title>MediaPlayerConnectivity</title>
		<category>Woof</category>
		<description>This looks good. URL:&lt;br /&gt;&lt;br /&gt;&lt;a href=https://addons.mozilla.org/en-US/firefox/addon/446 target=_blank&gt;https://addons.mozilla.org/en-US/firefox/addon/446&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;It doesn&#39;t work in SeaMonkey 2.0, so I have sent an email to the author asking if it can be adapted to SM2.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01220</link>
		<title>Testing T2 build</title>
		<category>Woof</category>
		<description>I did a recompile in T2. This is the third one recently. It took about 30 hours.&lt;br /&gt;&lt;br /&gt;I&#39;m aiming for small size, so am making quite a few radical decisions. The live-CD is 92MB, although I am aiming much lower than that.&lt;br /&gt;&lt;br /&gt;Working nicely. Some issues of course. The compiling environment works -- I compiled Gxine.&lt;br /&gt;&lt;br /&gt;And I&#39;m online running it right now, using SeaMonkey 2.0.&lt;br /&gt;&lt;br /&gt;Next thing to do is test printing....&lt;br /&gt;&lt;br /&gt;I mentioned before, I&#39;m doing this mainly for my Quirky Linux, which has one objective to be very small. Though, it&#39;s fine for any puplet. When I fix a few more bugs, I&#39;ll upload another Woof tarball and also the T2 .tar.bz2 binary packages (the Woof build system can download these to build a live-CD distro).&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01219</link>
		<title>Keyboard layout</title>
		<category>Woof</category>
		<description>Continuing from the previous post, I have revised how keyboard layout is handled.&lt;br /&gt;&lt;br /&gt;The modified scripts are &#39;init&#39;, &#39;rc.country&#39; and &#39;input-wizard&#39;.&lt;br /&gt;&lt;br /&gt;The relevant data files are no longer in /usr/share/kbd, instead are in /lib/keymaps and /lib/consolefonts. Both of these are in the initrd, and the &#39;pkeys&#39; boot parameter can now specify any layout and it will be loaded by the &#39;init&#39; script.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01218</link>
		<title>&#39;pkeys&#39; boot parameter</title>
		<category>Woof</category>
		<description>In Puppy 4.3.1, the &#39;pkeys&#39; boot parameter can be used to change the codepage and iocharset when mounting a vfat filesystem.&lt;br /&gt;&lt;br /&gt;The pkeys boot parameter is also read in /etc/rc.d/rc.country after switching to the main Puppy filesystem, and if set then the appropriate keyboard layout is loaded (and on first boot the dialog asking for keyboard layout will not appear).&lt;br /&gt;&lt;br /&gt;A limitation though, pkeys is currently restricted to:&lt;br /&gt;&lt;i&gt;be br cf de dk es fi fr gr hu it jp no pl ru se uk us&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;These are the keymaps located at /lib/keymaps.&lt;br /&gt;&lt;br /&gt;There are a number of improvements that can be made, but for now I have implemented one:&lt;br /&gt;&lt;br /&gt;The keymap is loaded after the switch-root to the main Puppy filesystem. The problem is, if you have to respond to any questions in the initrd, such as to choose a &#39;pupsave&#39; file from multiple choices, the keyboard is at the default layout (us).&lt;br /&gt;&lt;br /&gt;Woof now places /lib/keymaps into the initrd, and if there is a &#39;pkeys&#39; boot parameter, for example &#39;pkeys=uk&#39;, then that layout will get loaded by the init script (that&#39;s one reason why I recompiled busybox, to get the &#39;loadkmap&#39; applet).&lt;br /&gt;The init script copies /lib/keymaps to the main filesystem before the switch-root.&lt;br /&gt;&lt;br /&gt;Future improvements... I&#39;m thinking about it. Forum member ecube did some work excellent on this back in April 2009:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=40658 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=40658&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Ecube also sent me a pm with modified Keyboard Wizard and rc.country. Ecube, thanks for that -- I sure have taken awhile to get around to looking into it!&lt;br /&gt;&lt;br /&gt;The Tiny Core Linux people converted the kbd-1.14.1 package to kmap format that Busybox&#39;s &#39;loadkmap&#39; applet can load. The kmap files that I currently have in /lib/keymaps are very old, go right back to the very first release of Puppy in June 2003.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01217</link>
		<title>Woof tarballs</title>
		<category>Woof</category>
		<description>As I have put Fossil on hold, and quite likely won&#39;t reinstate it, for now I am uploading tarballs of Woof to here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/binaries/woof/ target=_blank&gt;http://bkhome.org/binaries/woof/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Regarding a suitable version control system, I&#39;m thinking that I will work with the Dim developers, as I think that is a much more Unix/Linux friendly system. See my earlier blog report:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01191 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01191&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...Dim currently does not support symlinks, empty directories or special files either, but the developers are intending to support those, and I might get involved.&lt;br /&gt;&lt;br /&gt;Developing Dim though, is a longer term thing, so I&#39;ll stay with uploading Woof tarballs for awhile.&lt;br /&gt;They are only 8MB so it&#39;s easy enough to do frequent uploads.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01216</link>
		<title>Fossil on hold</title>
		<category>Woof</category>
		<description>C**p, problems with Fossil.&lt;br /&gt;&lt;br /&gt;When I first created the fossil repository for Woof, it did store symlinks. However it has now converted them all into files. &lt;br /&gt;&lt;br /&gt;Woof has so many symlinks. &lt;br /&gt;&lt;br /&gt;So, Fossil is on hold. </description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01215</link>
		<title>Busybox recompiled for initramfs</title>
		<category>Woof</category>
		<description>The initramfs (&quot;initial ramdisk&quot;) has busybox version 1.4.2, statically compiled with uClibc. That was last done on 12 Nov. 2008. I have now recompiled it, kept the same version, and added more applets, plus enhanced the features of some. Fascinating, the busybox executable has grown from 253KB to 272KB, only 19KB, even though I have turned on help-text for each applet (the help text is internally compressed).&lt;br /&gt;&lt;br /&gt;I have reasons for wanting these extra applets, as will come clear in time. Here is the Fossil commit:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof.cgi/vinfo/8fbef54932b0355f6d3bb62fe6a98ecf4a56e875 target=_blank&gt;http://bkhome.org/fossil/woof.cgi/vinfo/8fbef54932b0355f6d3bb62fe6a98ecf4a56e875&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I turned on support for &#39;--help&#39;, so am able to provide the following information:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;NEW APPLETS&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;&lt;b&gt;dc&lt;/b&gt;&lt;br /&gt;Usage: dc expression ...&lt;br /&gt;&lt;br /&gt;This is a Tiny RPN calculator that understands the&lt;br /&gt;following operations: +, add, -, sub, *, mul, /, div, %, mod, **, exp, and, or, not, eor.&lt;br /&gt;For example: &#39;dc 2 2 add&#39; -&gt; 4, and &#39;dc 8 8 \* 2 2 + /&#39; -&gt; 16.&lt;br /&gt;&lt;br /&gt;Options:&lt;br /&gt;p - Prints the value on the top of the stack, without altering the stack&lt;br /&gt;f - Prints the entire contents of the stack without altering anything&lt;br /&gt;o - Pops the value off the top of the stack and uses it to set the output radix&lt;br /&gt;    Only 10 and 16 are supported&lt;br /&gt;    &lt;br /&gt;&lt;b&gt;halt&lt;/b&gt;&lt;br /&gt;Usage: halt [-d&lt;delay&gt;] [-n&lt;nosync&gt;] [-f&lt;force&gt;]&lt;br /&gt;&lt;br /&gt;Halt the system&lt;br /&gt;&lt;br /&gt;Options:&lt;br /&gt;        -d      Delay interval for halting&lt;br /&gt;        -n      No call to sync()&lt;br /&gt;        -f      Force halt (don&#39;t go through init)&lt;br /&gt;&lt;br /&gt;&lt;b&gt;loadfont&lt;/b&gt;&lt;br /&gt;Usage: loadfont &lt; font&lt;br /&gt;&lt;br /&gt;Load a console font from standard input&lt;br /&gt;&lt;br /&gt;&lt;b&gt;loadkmap&lt;/b&gt;&lt;br /&gt;Usage: loadkmap &lt; keymap&lt;br /&gt;&lt;br /&gt;Load a binary keyboard translation table from standard input&lt;br /&gt;&lt;br /&gt;&lt;b&gt;more&lt;/b&gt;&lt;br /&gt;Usage: more [FILE ...]&lt;br /&gt;&lt;br /&gt;View FILE or standard input one screenful at a time&lt;br /&gt;&lt;br /&gt;&lt;b&gt;pipe_progress&lt;/b&gt;&lt;br /&gt;No help available&lt;br /&gt;&lt;br /&gt;&lt;b&gt;poweroff&lt;/b&gt;&lt;br /&gt;Usage: poweroff [-d&lt;delay&gt;] [-n&lt;nosync&gt;] [-f&lt;force&gt;]&lt;br /&gt;&lt;br /&gt;Halt and shut off power&lt;br /&gt;&lt;br /&gt;Options:&lt;br /&gt;        -d      Delay interval for halting&lt;br /&gt;        -n      No call to sync()&lt;br /&gt;        -f      Force power off (don&#39;t go through init)&lt;br /&gt;&lt;br /&gt;&lt;b&gt;reboot&lt;/b&gt;&lt;br /&gt;Usage: reboot [-d&lt;delay&gt;] [-n&lt;nosync&gt;] [-f&lt;force&gt;]&lt;br /&gt;&lt;br /&gt;Reboot the system&lt;br /&gt;&lt;br /&gt;Options:&lt;br /&gt;        -d      Delay interval for rebooting&lt;br /&gt;        -n      No call to sync()&lt;br /&gt;        -f      Force reboot (don&#39;t go through init)&lt;br /&gt;&lt;br /&gt;&lt;b&gt;setkeycodes&lt;/b&gt;&lt;br /&gt;Usage: setkeycodes SCANCODE KEYCODE ...&lt;br /&gt;&lt;br /&gt;Set entries into the kernel&#39;s scancode-to-keycode map,&lt;br /&gt;allowing unusual keyboards to generate usable keycodes.&lt;br /&gt;&lt;br /&gt;SCANCODE may be either xx or e0xx (hexadecimal),&lt;br /&gt;and KEYCODE is given in decimal&lt;br /&gt;&lt;br /&gt;&lt;b&gt;setlogcons&lt;/b&gt;&lt;br /&gt;Usage: setlogcons N&lt;br /&gt;&lt;br /&gt;Redirect the kernel output to console N (0 for current)&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;ENHANCED APPLETS&lt;/b&gt;&lt;br /&gt;The following applets existed before, but I have enhanced their features...&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;&lt;b&gt;pidof&lt;/b&gt;&lt;br /&gt;Usage: pidof process-name [OPTION] [process-name ...]&lt;br /&gt;&lt;br /&gt;List the PIDs of all processes with names that match the&lt;br /&gt;names on the command line&lt;br /&gt;Options:&lt;br /&gt;        -s      Display only a single PID&lt;br /&gt;        -o      Omit given pid&lt;br /&gt;                Use %PPID to omit the parent pid of pidof itself&lt;br /&gt;&lt;br /&gt;&lt;b&gt;readlink&lt;/b&gt;&lt;br /&gt;Usage: readlink [-f] FILE&lt;br /&gt;&lt;br /&gt;Display the value of a symbolic link&lt;br /&gt;&lt;br /&gt;Options:&lt;br /&gt;        -f      Canonicalize by following all symlinks&lt;br /&gt;&lt;br /&gt;&lt;b&gt;tr&lt;/b&gt;&lt;br /&gt;Usage: tr [-cds] STRING1 [STRING2]&lt;br /&gt;&lt;br /&gt;Translate, squeeze, and/or delete characters from&lt;br /&gt;standard input, writing to standard output&lt;br /&gt;&lt;br /&gt;Options:&lt;br /&gt;        -c      Take complement of STRING1&lt;br /&gt;        -d      Delete input characters coded STRING1&lt;br /&gt;        -s      Squeeze multiple output characters of STRING2 into one character&lt;br /&gt;&lt;br /&gt;...it is not documented here, but enhanced functionality is to convert between upper-case and lower-case.&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01214</link>
		<title>Smaller Xorg</title>
		<category>Woof</category>
		<description>I have been working on making Xorg smaller in Woof builds.&lt;br /&gt;&lt;br /&gt;I have removed the &quot;openGL&quot; (and DRI drivers) component by default in Woof builds, as with Xorg 7.4 and 7.5 that has become enormous. The template was cutting it down a lot any way, now I have taken it right out. It can be added back in as a separate package later on.&lt;br /&gt;&lt;br /&gt;I am mostly aiming the T2 build for Quirky, where I want very small size. I am experimenting with cutting Xorg down to the &#39;vesa&#39; driver only (not the kdrive Xvesa, the vesa driver that is part of Xorg).&lt;br /&gt;&lt;br /&gt;The uncompressed size of /usr/X11R7 is as follows, for my T2 build:&lt;br /&gt;&lt;br /&gt;Before: 15.3MB&lt;br /&gt;GL removed: 12.58MB&lt;br /&gt;Vesa driver only: 8.02MB&lt;br /&gt;&lt;br /&gt;Fossil commits:&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof.cgi/vinfo/04c53c08ba048692414d78b749d6c215f7a1db5d target=_blank&gt;http://bkhome.org/fossil/woof.cgi/vinfo/04c53c08ba048692414d78b749d6c215f7a1db5d&lt;/a&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof.cgi/vinfo/be5207f38d91e576c2fa226564ff5f16a6aff2e9 target=_blank&gt;http://bkhome.org/fossil/woof.cgi/vinfo/be5207f38d91e576c2fa226564ff5f16a6aff2e9&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01213</link>
		<title>Xorg Wizard multiple monitors</title>
		<category>Woof</category>
		<description>Pizzasgood posted a patch to the &#39;xorgwizard&#39; script in the pup 4.3.1 forum feedback thread.&lt;br /&gt;&lt;br /&gt;I have applied this to Woof:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof.cgi/vinfo/fec6837bd2bfca364084f05e8329576459f7ed46 target=_blank&gt;http://bkhome.org/fossil/woof.cgi/vinfo/fec6837bd2bfca364084f05e8329576459f7ed46&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01212</link>
		<title>PDQ print system</title>
		<category>Puppy</category>
		<description>Experiencing problems with CUPS again, I remember wistfully the days when Puppy had the PDQ print system. I posted a comment to the previous post, but thought this deserves it&#39;s own post.&lt;br /&gt;&lt;br /&gt;PDQ homepage:&lt;br /&gt;&lt;a href=http://pdq.sourceforge.net/ target=_blank&gt;http://pdq.sourceforge.net/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Early versions of Puppy had PDQ, which is very nice, really tiny. It fell by the wayside for various reasons:&lt;br /&gt;&lt;br /&gt;No longer being developed.&lt;br /&gt;GTK 1.2 GUI application only.&lt;br /&gt;Some apps expect CUPS to be there.&lt;br /&gt;Very basic printer configuration.&lt;br /&gt;&lt;br /&gt;We could save an incredible amount of space with PDQ, plus it is very simple, and &quot;just works&quot;. But, it would need someone who is able to commit to developing it. It is written in C. For a start, the GUI application would have to be rewritten for GTK2.&lt;br /&gt;&lt;br /&gt;Mandrake Linux used to use PDQ as the default printing system. Um, I can&#39;t recall what version was the last to do that... 8.x comes to mind. The thing is, those guys had developed PDQ to a high art, did very nice things with it. But, like all the other distros they dropped it and went for CUPS&lt;br /&gt;&lt;br /&gt;So, if anyone wanted to take on PDQ as a project, getting an old Mandrake distro would be useful.&lt;br /&gt;I don&#39;t recall the last version of Puppy that used PDQ -- it would be in my online blog archive. &lt;br /&gt;&lt;br /&gt;I had developed a setup GUI that asked various questions about your printer, like how many color nozzles in an inkjet cartridge, so it didn&#39;t need a big database of printer types, but that would probably need to be developed further -- which is where the Mandrake stuff would be useful.&lt;br /&gt;&lt;br /&gt;I wouldn&#39;t mind messing around with it again. Anyone interested in helping out with porting it to GTK2?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01211</link>
		<title>CUPS 1.4.1 does not work</title>
		<category>Woof</category>
		<description>My T2 build has CUPS 1.4.1, but it does not recognise my USB printer.&lt;br /&gt;&lt;br /&gt;I started earlier today to trace reasons why Woof builds are bigger than earlier puppies. I&#39;m looking at the T2 build for now. The Ghostscript package for example is massive compared to the one in pup 4.3.1.&lt;br /&gt;&lt;br /&gt;This lead me to testing printing, when I discovered CUPS won&#39;t recognise my printer. It doesn&#39;t recognise its existence. A quick search revealed this is a known problem:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bugs.archlinux.org/task/15998 target=_blank&gt;http://bugs.archlinux.org/task/15998&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The kernel &#39;usblp&#39; module is no longer used, so I blcklisted it. But that did not help. The above link advises further changes, so I need to investigate further.&lt;br /&gt;&lt;br /&gt;Sigh, CUPS is such a pain.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01210</link>
		<title>Bug trackers!</title>
		<category>Woof</category>
		<description>I have activated the bug tracker for Woof, and posted a test-ticket:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof.cgi/rptview?rn=1 target=_blank&gt;http://bkhome.org/fossil/woof.cgi/rptview?rn=1&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;To view my ticket, to create a new ticket (bug report) and to append comments to existing tickets, you have to be logged in as &#39;anonymous&#39;.&lt;br /&gt;&lt;br /&gt;The requirement to login is partly a security measure and partly to prevent spambots from placing extra drain on the server.&lt;br /&gt;&lt;br /&gt;To avoid confusion, I think it best if only users of Woof report bugs to my ticketing system. That is, guys using Woof to build a distro, for example ttuuxx, gposil and kirk.&lt;br /&gt;&lt;br /&gt;For all Puppy Linux bugs, technosaurus has setup this bug tracker:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://code.google.com/p/puppy-development/issues/list target=_blank&gt;http://code.google.com/p/puppy-development/issues/list&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;However, regardless of what version of Puppy you are using, if you know there is a problem in a particular script that is in Woof, and you have looked at the Fossil version control system for Woof:&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof.cgi target=_blank&gt;http://bkhome.org/fossil/woof.cgi&lt;/a&gt;&lt;br /&gt;and seen that the latest script has the same problem as the script that you are using, then certainly report the bug to my Woof bug tracker.&lt;br /&gt;&lt;br /&gt;...or even fix it and send me a patch!&lt;br /&gt;&lt;br /&gt;POST EDITED NOV 19&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01209</link>
		<title>Weird shutdown problem</title>
		<category>Woof</category>
		<description>I was testing a T2 build, and when I tried to do a shutdown, it asked if I wanted to save the session, I declined, then X restarted!&lt;br /&gt;&lt;br /&gt;Hmmm. There was something different from normal. Usually I unmount all partitions before closing down, but this time I had left one mounted.&lt;br /&gt;&lt;br /&gt;The /etc/rc.d/rc.shutdown script attempts to kill any processes running on that partition (then later unmount it). take the example of /dev/sdc3 mounted, this is executed:&lt;br /&gt;&lt;br /&gt;fuser -k -m /dev/sdc3&lt;br /&gt;&lt;br /&gt;However, there are no processes running on /dev/sdc3, as &#39;fuser -m /dev/sdc3&#39; confirms.&lt;br /&gt;However that line causes a weird event to occur -- X immediately restarts!&lt;br /&gt;&lt;br /&gt;I have put a workaround into rc.shutdown:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof.cgi/timeline target=_blank&gt;http://bkhome.org/fossil/woof.cgi/timeline&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;However, I really do need to investigate this some more.&lt;br /&gt;&lt;br /&gt;Note, you will need to login as &#39;anonymous&#39; to see the actual changes made to rc.shutdown.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01208</link>
		<title>Fossil: Limitation workarounds</title>
		<category>Woof</category>
		<description>I have identified four limitations of Fossil that causes problems with hosting the Woof project. As far as I know, these limitations also exist in GIT and SVN. I have added to my &lt;i&gt;Fossil Quick Guide&lt;/i&gt; page explaining these limitations (scroll down near bottom):&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/fossil-guide.htm target=_blank&gt;http://bkhome.org/fossil/fossil-guide.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I developed a wrapper script named &#39;fossil&#39; to workaround these limitations (and I renamed the binary executable to &#39;fossil.bin&#39;). This script (and fossil.bin) is in a PET package, linked-to in the Fossil Quick Guide.&lt;br /&gt;&lt;br /&gt;Direct link to PET package:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/fossil-20091111.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/fossil-20091111.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Note: I am currently doing some testing that these Fossil workarounds do actually work.&lt;br /&gt;Then I&#39;ll get back to fixing some bugs in the T2 build (Tpup).&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01207</link>
		<title>Fossil: Woof repository not ready</title>
		<category>Woof</category>
		<description>Just in case you go to my new Fossil version control repository and see all files are uploaded:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof.cgi/timeline target=_blank&gt;http://bkhome.org/fossil/woof.cgi/timeline&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Don&#39;t be tempted to do a checkout yet, as described here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/fossil-guide.htm target=_blank&gt;http://bkhome.org/fossil/fossil-guide.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...because it won&#39;t work. That is, the Woof build scripts will fail.&lt;br /&gt;&lt;br /&gt;Fossil cannot store empty directories, files with &#39;[&#39; or &#39;]&#39; in them, and device nodes. Therefore I have had to employ workarounds to get them in.&lt;br /&gt;&lt;br /&gt;The build scripts will have to be aware of these workarounds, and I have not yet done that. Hopefully will do that tonight or tomorrow.&lt;br /&gt;&lt;br /&gt;As far the the T2 build, there are still some bugs that need to be fixed, plus I will have to upload the latest set of raw binary compiled packages.&lt;br /&gt;&lt;br /&gt;I&#39;ll announce when it is ready.&lt;br /&gt;&lt;br /&gt;Note, once it&#39;s up, I&#39;ll be syncing with it every time I make a local change, so you will be getting my very latest Woof.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01206</link>
		<title>Fossil: database integrity</title>
		<category>Woof</category>
		<description>I have a very temperamental Internet connection -- dish on the roof pointing at a satellite. Apart from the over-one-second round trip, the connection drops out randomly then comes good again seconds or minutes later -- clouds? atmospheric affects?&lt;br /&gt;&lt;br /&gt;Anyway, one of these dropouts occurred while I was syncing my local Fossil repository with the online one, which caused the operation to hang. It then raised the whole question about possible corruption of a repository.&lt;br /&gt;&lt;br /&gt;I raised this question in the Fossil mail list:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg00833.html target=_blank&gt;http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg00833.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Dr Hipp also referred me to this page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.fossil-scm.org/fossil/doc/tip/www/selfcheck.wiki target=_blank&gt;http://www.fossil-scm.org/fossil/doc/tip/www/selfcheck.wiki&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The precautions taken against any kind of corruption are very impressive.&lt;br /&gt;&lt;br /&gt;Note, I have updated this page, added a Fossil Quick Guide, but it needs more work:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/ target=_blank&gt;http://bkhome.org/fossil/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01205</link>
		<title>Woof: SeaMonkey 2.0</title>
		<category>Woof</category>
		<description>I am currently refining Woof to build a distro from packages compiled in T2.&lt;br /&gt;&lt;br /&gt;The T2 build is pretty up-to-date with the latest packages, including SeaMonkey 2.0. &lt;br /&gt;&lt;br /&gt;Woof has a directory &#39;packages-templates&#39; which contains &quot;templates&quot; that define how a raw binary package is to be cutdown and modified to be Puppy-compatible. I have updated directory &#39;packages-templates/seamonkey&#39; to handle SeaMonkey 2.x.&lt;br /&gt;&lt;br /&gt;Actually, it isn&#39;t easy. It has to handle a directory layout that has been butchered by Debian/Ubuntu as well as normal layouts. The raw binary package compiled in t2 is of course &quot;normal&quot;.&lt;br /&gt;&lt;br /&gt;Apart from cutting it down a bit, there are little things to tweak. For example the &#39;prefs.js&#39; file has to be modified so that the first time SM is run the Puppy home page comes up and not the SM home page.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01204</link>
		<title>Barking dog wanted</title>
		<category>Woof</category>
		<description>Has anyone seen a picture of a barking dog online, that I could use for the Woof logo?&lt;br /&gt;&lt;br /&gt;I&#39;m currently using this, as a temporary placeholder:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://bkhome.org/woof-big.gif /&gt;&lt;br /&gt;&lt;br /&gt;I got that off the Internet somewhere and it may have license restrictions, like for personal use only.&lt;br /&gt;&lt;br /&gt;Ideally I would like a circular logo, to match other logos on my website (and the Puppy logo).&lt;br /&gt;&lt;br /&gt;I&#39;m still experimenting with the Fossil version control system. The more I learn, the more I like it. My experimental setup has moved slightly:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/ target=_blank&gt;http://bkhome.org/fossil/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...I&#39;m going to start experimenting with putting some files into it, and generally play around. If my confidence reaches a certain level, then I&#39;ll &quot;go for it&quot; (Fossil as the official Woof version control, wiki and bug tracking system).&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01203</link>
		<title>Zombies on TV</title>
		<category>General</category>
		<description>Until a few days ago, I could only receive one TV channel, our ABC (Australian Broadcasting Commission) Government channel. &lt;br /&gt;&lt;br /&gt;Now, with satellite TV, all sorts of stuff. I am only getting free-to-air channels. Well, kind of -- most of them are scrambled and require an Optus smartcard to view, a one-off purchase ($85).&lt;br /&gt;&lt;br /&gt;I now get two commercial channels. I must say, after not watching any commercial TV for 10 years, my impression is these are mostly junk.&lt;br /&gt;Many of the programs are lowest-common-denominator (sex, violence, money).&lt;br /&gt;&lt;br /&gt;I now get SBS, which is a Government ethnic channel, sometimes has interesting stuff. On Monday night I watched &quot;Dead Set&quot;, first of a 5-part series:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://en.wikipedia.org/wiki/Dead_Set_(TV_series) target=_blank&gt;http://en.wikipedia.org/wiki/Dead_Set_(TV_series)&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;After that, I turned to another channel, and lo-and-behold, yet another zombie program, &quot;Undead&quot;:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.undeadthemovie.com/ target=_blank&gt;http://www.undeadthemovie.com/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I missed the beginnings of both of these, so don&#39;t know exactly how these zombies got going. It seems, in the Undead movie it is a rain of meteorites that infect the people. Zombies attack others, if bitten you become a zombie also.&lt;br /&gt;&lt;br /&gt;Oh dear, hasn&#39;t this been &quot;done to death&quot; already?&lt;br /&gt;I&#39;m not into horror movies. Though, this undead thing is kind of amusing because it is so dumb.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01202</link>
		<title>Pwireless2</title>
		<category>Puppy</category>
		<description>This is extremely interesting! Forum member jemimah has rewritten our Pwireless program (developed by plinej (Jason)):&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=48816 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=48816&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Quoting:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;As some of you may know, wpa_supplicant is a network management daemon that runs in the background on your computer and connects you to wireless networks. It supports open networks, WEP networks, and WPA networks.&lt;br /&gt;&lt;br /&gt;Puppy supports wpa_supplicant with the Network Wizard, but not in roaming mode. Roaming mode is a godsend for people with laptops who may need to reconfigure their wireless network several times a day. In roaming mode, you set up each network one time, and wpa_supplicant will automatically connect to it whenever you&#39;re in range. If multiple networks are in range, you can set priorities to tell wpa_supplicant which one you prefer.&lt;br /&gt;&lt;br /&gt;Until now, the only way to configure wpa_supplicant roaming mode was by editing the configuration files by hand, or use wpa_gui (http://www.murga-linux.com/puppy/viewtopic.php?t=47838). Wpa_gui has a somewhat confusing interface and requires large Qt libraries, so I thought it was time someone wrote a lightweight GUI frontend that was specifically designed for and integrated into Puppy.&lt;br /&gt;&lt;br /&gt;Pwireless2 looks much the same as the original Pwireless but the guts are totally replaced. Pwireless2 uses wpa_cli to communicate with wpa_supplicant. Wpa_supplicant handles profile storage, and all network configuration tasks. I&#39;ve also included an upgraded version of Dhcpcd which handles allocating Ip addresses and notifying you when the status of your network changes.&lt;br /&gt;&lt;br /&gt;Finally, I&#39;ve modified a program called gtrayicon to provide you with a very basic networking tray applet. Clicking on the applet will tell wpa_supplicant to start or stop (clicking it if you haven&#39;t configured any networks won&#39;t do much of anything). Right click and choose Configure to launch the Pwireless2 configuration gui. &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Jemimah, this is a great initiative.&lt;br /&gt;Guys, test it!&lt;br /&gt;&lt;br /&gt;A note on the original Pwireless. Plinej created it, and HairyWill and urban-soul did some further work. I think the most recent version is 0.8.4:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=23121 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=23121&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01201</link>
		<title>Fossil progress</title>
		<category>Woof</category>
		<description>I have made progress, of sorts. I logged into my Fossil Woof online repository and changed permission to &#39;clone&#39; from &#39;anonymous&#39; user to &#39;nobody&#39;.&lt;br /&gt;&lt;br /&gt;I then did this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;&gt; fossil clone http://bkhome.org/fossil/woof/woof.cgi woof.fossil&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...it has downloaded the correct &#39;woof.fossil&#39;, which has my modifications (title, logo).&lt;br /&gt;&lt;br /&gt;Hmmm, the Quick Start guide said nothing about having to do that.&lt;br /&gt;&lt;br /&gt;Note, it is essential to have &#39;woof.cgi&#39; on the URL in the above clone operation.&lt;br /&gt;&lt;br /&gt;I&#39;ll follow through the other things I did in the last post, see if it all works this time...&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01200</link>
		<title>Fossil version control</title>
		<category>Woof</category>
		<description>I was recently evaluating &lt;i&gt;Dim&lt;/i&gt; version control, see my blog report:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01191 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01191&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Dim is a Bash/Ash shell script, and a PHP script for the web site. Very small, but at this stage there is a lot on the to-do list.&lt;br /&gt;&lt;br /&gt;Then technosaurus informed me about &lt;i&gt;Fossil&lt;/i&gt;, a &quot;small and simple&quot; version control system. So, I have now started to evaluate Fossil.&lt;br /&gt;&lt;br /&gt;Fossil homepage: &lt;a href=http://www.fossil-scm.org/ target=_blank&gt;http://www.fossil-scm.org/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...read that, and it sure does seem impressive! &lt;br /&gt;&lt;br /&gt;Fossil has a single binary executable, named &#39;fossil&#39;. I compiled it and it is 652KB. That&#39;s the whole thing, all you need to install Fossil, and the executable even has the Sqlite database compiled statically into the executable -- which is good for uploading to a website that might not have shared Sqlite library (or wrong version). &lt;br /&gt;However, technosaurus has figured out how to compile Fossil against shared Sqlite library if you want.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Install on website&lt;/b&gt;&lt;br /&gt;Having had just about zero experience with installing and setting up a version control system (only a limited play with Dim), I was scratching my head. But forged ahead, and it turned out to be a simple procedure, very simple. It will be useful to others I reckon, for me to document it here...&lt;br /&gt;&lt;br /&gt;My first problem was where to upload the &#39;fossil&#39; executable, as I only have a shared hosting website (with hostgator.com). I can&#39;t just bung it into the system /bin directory! Well, I took a punt, and created a &#39;bin&#39; directory: /home/&lt;username&gt;/bin.&lt;br /&gt;/home/&lt;username&gt; is where I am when I do an ftp or ssh login.&lt;br /&gt;I then uploaded &#39;fossil&#39; to the &#39;bin&#39; directory. I set permission of &#39;bin&#39; to 755 and &#39;fossil&#39; to 755.&lt;br /&gt;&lt;br /&gt;I then created directories &lt;path to bkhome.org root&gt;/fossil/woof, set permissions at 755.&lt;br /&gt;Inside &#39;woof&#39; I created a script &#39;woof.cgi&#39; (755) with this in it:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;#!/home/&lt;username&gt;/bin/fossil&lt;br /&gt;repository: &lt;path to bkhome.org root&gt;/fossil/woof/woof.fossil&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;...of course, if you want to do this yourself, you will have to substitute the appropriate text into &quot;&lt; ... &gt;&quot;.&lt;br /&gt;&lt;br /&gt;I also created a &#39;.htaccess&#39; file (644) in fossil/woof directory with this in it:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;AddHandler cgi-script .cgi&lt;br /&gt;Options ExecCGI FollowSymLinks&lt;br /&gt;RewriteEngine On&lt;br /&gt;RewriteBase /fossil/woof/&lt;br /&gt;RewriteRule ^$ woof.cgi&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;...I wanted to completely hide the &#39;woof.cgi&#39; script from the URL that users would see, but I couldn&#39;t figure out how to do that. Instead, the above just allows a URL &quot;http://bkhome.org/fossil/woof/&quot; which will run the &#39;woof.cgi&#39; script -- but then the user still sees the full URL with &quot;woof.cgi&quot; in it. If anyone is an expert on Apache mod_rewrite, advice welcome!&lt;br /&gt;&lt;br /&gt;Almost there. I needed an empty &quot;repository&quot; to get going. I created it like this (locally, on my own computer):&lt;br /&gt;&lt;br /&gt;&lt;i&gt;&gt; fossil new woof.fossil&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I then uploaded &#39;woof.fossil&#39; to fossil/woof by sftp and set permissions to 744.&lt;br /&gt;&lt;br /&gt;Finally, I pointed my web browser here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/fossil/woof/ target=_blank&gt;http://bkhome.org/fossil/woof/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...hey man, it works! A very pleasant experience, I must say. I just followed my nose, doing logical things to set it up, not many steps required, and it works as advertised.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Install on local computer&lt;/b&gt;&lt;br /&gt;Just copy the &#39;fossil&#39; executable to the execute-path, such as /usr/bin.&lt;br /&gt;&lt;br /&gt;As far as usage goes, well, I&#39;m just getting started. As I commented above, I have zero experience. Yeah, I have had occasion to checkout from various CVS/SVN/GIT hosted projects, and always followed whatever instructions they provided. Beyond that, I know nothing.&lt;br /&gt;&lt;br /&gt;I haven&#39;t yet put any files into my &#39;woof.fossil&#39; repository. It is important to note that the entire project resides in that one file. It has its own internal Sqlite database, and all files, all revisions, will be inside &#39;woof.fossil&#39;. So, the file may grow quite large!&lt;br /&gt;&lt;br /&gt;An obvious first thing to do is, how to download my online &#39;woof.fossil&#39; repository to my local computer?&lt;br /&gt;&lt;br /&gt;A good place to look for basic usage instructions is the Fossil Quick Start Guide:&lt;br /&gt;&lt;a href=http://www.fossil-scm.org/index.html/doc/tip/www/quickstart.wiki target=_blank&gt;http://www.fossil-scm.org/index.html/doc/tip/www/quickstart.wiki&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Alright, this seems to be what is needed:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;&gt; fossil clone http://bkhome.org/fossil/woof/ woof.fossil&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...amazing, it works! Be sure to write down the username and password it reports. &lt;br /&gt;&lt;br /&gt;I notice though, it did not download the configuration I had done to the online woof.fossil -- title and logo -- the downloaded woof.fossil is empty, no default title and logo -- so, is something wrong?&lt;br /&gt;&lt;br /&gt;To use the web interface for looking inside the repository, run:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;&gt; fossil ui woof.fossil&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...at the time of writing I have not yet configured &#39;woof.fossil&#39; to auto-launch the web browser, so manually start your web browser and look at:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://127.0.0.1:8080/ target=_blank&gt;http://127.0.0.1:8080/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;When finished, CTRL-C in the terminal window to kill the fossil web server.&lt;br /&gt;&lt;br /&gt;The logical next thing to do is checkout a project-tree. That is, extract the latest version of the project from the repository:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;&gt; mkdir woof-tree&lt;br /&gt;&gt; cd woof-tree&lt;br /&gt;&gt; fossil open ../woof.fossil&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Now I want to create a file in my project, and add it to the repository:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;&gt; echo &quot;test file number one&quot; &gt; NewFile1&lt;br /&gt;&gt; fossil add NewFile1&lt;br /&gt;&gt; fossil commit -m &quot;first test commit NewFile1&quot; --nosign&lt;br /&gt;&gt; fossil close&lt;br /&gt;&gt; cd ..&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Problems&lt;br /&gt;&lt;br /&gt;1. &lt;br /&gt;The downloaded repository does not have stuff in it that I had put into the online &#39;woof.fossil&#39;.&lt;br /&gt;&lt;br /&gt;2.&lt;br /&gt;&quot;Autosync&quot; is by default turned on, and when I ran the above commit, it reported that it was also uploading to my online repository. However, when I point my browser at the online Woof repository, there is nothing, zilch.&lt;br /&gt;&lt;br /&gt;3.&lt;br /&gt;Unfortunately, it gets worse. When I attempted to reopen my local &#39;woof.fossil&#39;:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;&gt; cd woof-tree&lt;br /&gt;&gt; fossil open ../woof.fossil&lt;/i&gt;&lt;br /&gt;&lt;some stuff&gt;&lt;br /&gt;Segmentation fault&lt;br /&gt;&lt;br /&gt;...but it was then open.&lt;br /&gt;&lt;br /&gt;So, the current situation for me is that it does not &quot;just work&quot;. Probably I&#39;m doing something wrong, as there are obviously other happy Fossil users. Anyway, I&#39;ll keep experimenting.&lt;br /&gt;&lt;br /&gt;I looked at my website error log, and see this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;File does not exist: &lt;path to bkhome.org root&gt;/fossil/woof/xfer&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I did try various ways of uploading. For example, these two:&lt;br /&gt;&lt;i&gt;&gt; fossil push http://bkhome.org/fossil/woof/woof.cgi --repository woof.fossil&lt;/i&gt;&lt;br /&gt;&gt; fossil push &lt;i&gt;http://bkhome.org/fossil/woof/woof.cgi/xfer --repository woof.fossil&lt;/i&gt;&lt;br /&gt;...in both cases got a &quot;bad command&quot;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01199</link>
		<title>Woof GUI improved</title>
		<category>Woof</category>
		<description>&lt;b&gt;Previous templates&lt;/b&gt;&lt;br /&gt;I have added a pull-down list of templates in the first tab of the Woof GUI:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://puppylinux.com/woof/woof_gui_specifications.png /&gt;&lt;br /&gt;&lt;br /&gt;The &quot;Previous templates&quot; pull-down list currently has these entries:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Puppy 4.3.1&lt;br /&gt;Ubuntu Karmic Koala&lt;br /&gt;T2 8.0rc&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;These are recent successful builds. Choosing one of these will configure the above entries in the GUI window so that Woof should build a live-CD without problems.&lt;br /&gt;&lt;br /&gt;So for example, you choose &quot;Ubuntu Karmic Koala&quot;, then all the above entries get preset to build a Upup from Karmic deb packages. But then you can modify the individual boxes, such as change the version number.&lt;br /&gt;&lt;br /&gt;I have implemented this as I realised this first tab was a bit confusing.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Default tab&lt;/b&gt;&lt;br /&gt;Thanks to Zigbert who reported how to set default tab in a gtkdialog tabbed interface:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=38608 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=38608&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...I have implemented this in Woof.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01198</link>
		<title>puppylinux.org hacked into</title>
		<category>Puppy</category>
		<description>For your information. I don&#39;t know if it can compromise your own system by visiting it, best to stay away.&lt;br /&gt;&lt;br /&gt;I have received a few emails about it, but note that I don&#39;t have anything to do with maintaining puppylinux.org.&lt;br /&gt;&lt;br /&gt;There&#39;s a forum thread discussing this:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=48695 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=48695&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01197</link>
		<title>Preliminary testing Xorg 7.5</title>
		<category>Woof</category>
		<description>My T2 build has Xorg 7.5, at least a pre-release of 7.5.&lt;br /&gt;&lt;br /&gt;I used Woof to build a distro, booted off a Flash drive, got a black screen, dead keyboard.&lt;br /&gt;&lt;br /&gt;I tracked it down to this line in the Xorg Wizard:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Xorg -configure&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;By bypasing that, I was able to get Xorg to start.&lt;br /&gt;&lt;br /&gt;By running:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Xorg -configure &gt; /mnt/sda6/x.log 2&gt;&amp;1&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I was able to get a log, and I found this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;(EE) LoadModule: Module i810 does not have a i810ModuleData data object.&lt;br /&gt;(EE) Failed to load module &quot;i810&quot; (invalid module, 0)&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;then it complained that vmware_drv.so has an undefined symbol, then it hung.&lt;br /&gt;&lt;br /&gt;Anyway, one thing at a time. I could only find two partially useful links about that particular i810 problem:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.mail-archive.com/universe-bugs@lists.ubuntu.com/msg128432.html target=_blank&gt;http://www.mail-archive.com/universe-bugs@lists.ubuntu.com/msg128432.html&lt;/a&gt;&lt;br /&gt;&lt;a href=https://bugzilla.redhat.com/show_bug.cgi?format=multiple&amp;id=439045 target=_blank&gt;https://bugzilla.redhat.com/show_bug.cgi?format=multiple&amp;id=439045&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...the first link &quot;solves&quot; the problem by hardwiring use of the &#39;intel&#39; driver into Xorg.conf.&lt;br /&gt;&lt;br /&gt;...the second solution is very frustrating, as the fellow says he solved the problem, but does not say how.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;UPDATE&lt;/b&gt;&lt;br /&gt;Here&#39;s another i810 link:&lt;br /&gt;&lt;a href=http://www.linuxquestions.org/questions/slackware-14/what-happened-to-xorg-in-slackware-13.0-intel-chipset-762618/ target=_blank&gt;http://www.linuxquestions.org/questions/slackware-14/what-happened-to-xorg-in-slackware-13.0-intel-chipset-762618/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...interesting, Slackware 13.0 has an alternate (older) intel driver that people can use if the &quot;proper&quot; one doesn&#39;t work.&lt;br /&gt;&lt;br /&gt;Anyway, I have to go back and check what kernel modules were loaded. It looks like the i810_drv.so driver needs kernel DRM module i810.ko (and drm.ko). Yeah, this is new stuff -- previously only the agpgart.ko and intel_agp.ko modules were needed. I&#39;ll check and report back.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01196</link>
		<title>Puppy 4.4 links</title>
		<category>Puppy</category>
		<description>As it was asked about recently, here are the forum links that I know of, where Puppy 4.4 (CE) is being planned/developed:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Puppy 4.4 CE - Phase 1: pet tests&lt;/b&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46941 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46941&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;What shall I work on first for the next CE release?&lt;/b&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47065 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47065&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Puppy 4.4CE&lt;/b&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46497 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46497&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01195</link>
		<title>T2 8.0rc binary packages</title>
		<category>Woof</category>
		<description>I have uploaded the packages that I compiled in the T2 build system, to here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/binaries/t2/ target=_blank&gt;http://bkhome.org/binaries/t2/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;508 packages, occupying about 445MB.&lt;br /&gt;&lt;br /&gt;The next release of Woof will be able to build a distro from these.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01194</link>
		<title>Satellite TV: NITV</title>
		<category>General</category>
		<description>I reported recently that I was thinking of installing satellite television:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/blog/?viewDetailed=01118 target=_blank&gt;http://bkhome.org/blog/?viewDetailed=01118&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Given that I can only get one terrestrial TV channel, our ABC (Australian Broadcasting Corp., Government non-commercial), and that very weak, I reckoned it was time to go for free-to-air satellite TV.&lt;br /&gt;&lt;br /&gt;I know in some parts of the world, satellite TV is the normal thing. For me it&#39;s a big deal. Most Aussies are well-served by the terrestrial channels.&lt;br /&gt;&lt;br /&gt;So, on my last trip to Perth I bought the parts. There&#39;s this neat little hand-held &quot;satellite finder&quot;, just a needle gauge and beeps -- the gauge shows signal strength and the pitch of the beeps goes up, and the beeps go faster, as the signal increases. It was a cinch to get the dish pointed at the Optus C1 satellite. It only cost AU$15:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://www.sciteq.com.au/store/images/products/450001.jpg /&gt;&lt;br /&gt;&lt;a href=http://www.sciteq.com.au/store/product_info.php?products_id=149&amp;SciTeqsid=139c3f4d60243d27b11e5b70686703ba target=_blank&gt;http://www.sciteq.com.au/store/product_info.php?products_id=149&amp;SciTeqsid=139c3f4d60243d27b11e5b70686703ba&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;After getting it all setup, I then had to go onto the Internet to activate the Optus smartcard -- oh, &quot;two business days&quot;. Today is Saturday. Oh well.&lt;br /&gt;&lt;br /&gt;The Optus C1 satellite only has two un-encrypted channels, Optus Sydney which only has a test pattern and a continuous tone, and NITV. You can also see NITV online:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://nitv.org.au/ target=_blank&gt;http://nitv.org.au/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...I have been sitting here watching it. Hmmm, after the initial novelty perhaps even the most keen indigenous person would be changing to some other channel that provides entertainment. ...I don&#39;t mean that comment to come across as disrespectful.&lt;br /&gt;&lt;br /&gt;This is the receiver I bought:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://www.sciteq.com.au/store/images/products/101033.jpg /&gt;&lt;br /&gt;&lt;a href=http://www.sciteq.com.au/store/product_info.php?products_id=388&amp;SciTeqsid=139c3f4d60243d27b11e5b70686703ba target=_blank&gt;http://www.sciteq.com.au/store/product_info.php?products_id=388&amp;SciTeqsid=139c3f4d60243d27b11e5b70686703ba&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Not knowing anything about these things, I just bought what the guy behind the counter recommended. One nice feature, a USB socket that will take a drive, so can save to it.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01193</link>
		<title>Quirky page</title>
		<category>Quirky</category>
		<description>People are going to be asking, what is Quirky? I know Lobster has created a wiki page, but I thought that I should put something on my own Quirky page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://bkhome.org/quirky/ target=_blank&gt;http://bkhome.org/quirky/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01192</link>
		<title>Sqlite 3.6.20</title>
		<category>Quirky</category>
		<description>A note for developers...&lt;br /&gt;&lt;br /&gt;My T2 compile that I&#39;m doing for Quirky (that&#39;s &lt;i&gt;still&lt;/i&gt; chugging along) has Sqlite 3.6.20. However, compile failed as it complained that it needed &#39;tclsh&#39;, even though I had specified &#39;--disable-tcl&#39;.&lt;br /&gt;&lt;br /&gt;I rolled back to Sqlite 3.6.12, that was in a T2 compile I did in April 2009. That does compile without Tcl.&lt;br /&gt;&lt;br /&gt;I joined the Sqlite mail-list and asked about this. I was advised to use the &#39;sqlite-amalgamation-3.6.20.tar.gz&#39; source. Sure enough, that compiles without Tcl.&lt;br /&gt;&lt;br /&gt;Get it from here:&lt;br /&gt;&lt;a href=http://www.sqlite.org/download.html target=_blank&gt;http://www.sqlite.org/download.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The &quot;amalgamation&quot; is explained here:&lt;br /&gt;&lt;a href=http://www.sqlite.org/amalgamation.html target=_blank&gt;http://www.sqlite.org/amalgamation.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have compiled SeaMonkey 2.0 in T2. Note that it can use the system Sqlite, but it must be version &gt;= 3.6.16. Earlier SeaMonkeys have an internal Sqlite, so this saves space.&lt;br /&gt;&lt;br /&gt;N</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01191</link>
		<title>Dim version control</title>
		<category>Woof</category>
		<description>I think that I have finally found a version control system that is to my liking:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.oligem.com/dim/ target=_blank&gt;http://www.oligem.com/dim/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;With all due respect to CVS, SVN, GIT and the rest, I find them too complicated and big.&lt;br /&gt;&lt;br /&gt;Dim is a single shell script, and even works with Dash/Ash. &lt;br /&gt;&lt;br /&gt;I&#39;m thinking that I&#39;ll have Dim in the &#39;devx&#39; SFS file, so it becomes a standard feature in Woof builds.&lt;br /&gt;&lt;br /&gt;I reckon, finally, I might put Woof onto version control on my website, and let others have direct input.&lt;br /&gt;...if anyone sees a problem with doing that using Dim, let me know.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01190</link>
		<title>T2 compile in progress</title>
		<category>Quirky</category>
		<description>I decided to do a T2 compile from source, as a basis for Quirky Linux. Mainly because I want it to be small.&lt;br /&gt;&lt;br /&gt;My PC that I have dedicated to T2 builds is chugging away...&lt;br /&gt;&lt;br /&gt;The main T2 developer, Rene, recently announced version 8.0rc, so they are finally moving toward another release. I grabbed the build tarball from subversion a few days ago.&lt;br /&gt;&lt;br /&gt;The SVN package in Puppy&#39;s devx is not up to it, even though it was compiled in T2. It lacks support for connection to https://, which is due to a missing dependency. That&#39;s T2&#39;s fault, not including that dependency -- which is quite odd.&lt;br /&gt;I used my Upup to grab T2 from SVN.&lt;br /&gt;&lt;br /&gt;However, the SVN download still didn&#39;t work, something was missing. I solved the problem by merging my SVN download into &#39;t2-8.0rc.tar.gz&#39; (the official 8.0rc tarball).&lt;br /&gt;&lt;br /&gt;It&#39;s not for the faint-hearted. Lots of compile errors, but I&#39;m getting there.&lt;br /&gt;&lt;br /&gt;T2 home: &lt;a href=http://t2-project.org/ target=_blank&gt;http://t2-project.org/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01189</link>
		<title>Decisions, decisions...</title>
		<category>General</category>
		<description>I can&#39;t make up my mind whether &quot;barryk.org&quot; or &quot;bkhome.org&quot; is better.&lt;br /&gt;&lt;br /&gt;The latter might convey a slightly more professional impression maybe?&lt;br /&gt;&lt;br /&gt;I have registered both of them for two years, but should settle on just one for preferred use.&lt;br /&gt;&lt;br /&gt;Raffy, I know there are other possibilities. Strangely enough, I actually want a domain name for which all other variants are already registered. That is, I have .org, and all the other TLDs are already registered (bkhome.com, etc). My reasoning is, it is good to know what my neighbours are before I &quot;buy in&quot;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01188</link>
		<title>Notes for 4.4 developers</title>
		<category>Puppy</category>
		<description>Just a couple of quick notes, while I think of it.&lt;br /&gt;&lt;br /&gt;OpenSSH package in 4.3.1 is too old (4.7p1). It doesn&#39;t support SSH v2. My host Hostgator.com recently upgraded their SSH, and I had to compile the latest OpenSSH (5.3p1).&lt;br /&gt;&lt;br /&gt;Pburn. I&#39;m using version 3.1.2, in Puppy 4.3.1. I burnt an audio file to CD. At completion I exited via the &quot;File&quot; menu, that is, the proper way. However there was still a process left running. I had to kill it to be able to unmount the partition. This problem is repeatable.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01187</link>
		<title>Test post, barryk.org</title>
		<category>General</category>
		<description>This blog has a new URL, barryk.org/blog. First test post.&lt;br /&gt;&lt;br /&gt;Actually, I copied the blog, and the old one at puppylinux.com/blog is still running. Next step is to figure out how to do some URL-rewriting to redirect to the new blog.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01186</link>
		<title>Quirky idea #1 works</title>
		<category>Quirky</category>
		<description>I had already done a small test, now I have written a script in Woof, &#39;4quirkybuild&#39;, to do a full build of Quirky.&lt;br /&gt;&lt;br /&gt;I think that I discussed this idea with Raffy a long time ago. Well, it was briefly mentioned.&lt;br /&gt;&lt;br /&gt;Puppy has at least three files, vmlinuz, initrd.gz and pup-xxx.sfs. &lt;br /&gt;&lt;br /&gt;The initramfs, or to use it&#39;s old name &quot;initial ramdisk&quot;, is initrd.gz. After the kernel vmlinuz has loaded, it then loads this initramfs, which is a mini Linux working environment. It does the searching of the drives to find the Puppy files, and after having found pup-xxx.sfs (and maybe the &#39;pupsave&#39;, &#39;zdrv&#39;, and extra sfs files) then sets up the layered filesystem and peforms a &#39;switch_root&#39; into this layered filesystem.&lt;br /&gt;&lt;br /&gt;Puppy can be built with the pup-xxx.sfs inside the initrd.gz, which is good because then Puppy doesn&#39;t have to look anywhere to find it. It does slow bootup though, as it all has to be loaded into RAM.&lt;br /&gt;It is also simpler to setup booting, especially over a network, as there are only two files.&lt;br /&gt;&lt;br /&gt;Now, the quirky idea takes this one step further. It is possible to compile the kernel vmlinuz with the initrd inside it. So, if we build the pup-xxx.sfs inside initrd, then we compile the kernel with the initrd inside the kernel... we end up with just one file!&lt;br /&gt;&lt;br /&gt;Furthermore, the 2.6.30 kernel inroduced lzma compression. This reduces the size of the kernel, but we can keep plain gzip compression for the pup-xxx.sfs file (which runs faster). Though, I don&#39;t think that applying lzma compression to a sfs file reduces it much.&lt;br /&gt;&lt;br /&gt;Anyway, I did a test build, based on 4.3.1 pet packages, and created &#39;quirky000&#39;. This is a Linux kernel, with, as I explained above, the initrd and the pup-xxx.sfs inside it.&lt;br /&gt;I put it on a USB Flash drive, and modified the &#39;syslinux.cfg&#39; file to just this:&lt;br /&gt;&lt;br /&gt;default quirky000 pmedia=usbflash&lt;br /&gt;&lt;br /&gt;...the pmedia parameter isn&#39;t really needed.&lt;br /&gt;&lt;br /&gt;Yep, it works! booting is a bit slow, as everything loads into RAM. But, this is the direction that I am aiming Quirky -- a distro that runs in RAM only.&lt;br /&gt;&lt;br /&gt;Hey, this is fun!&lt;br /&gt;&lt;br /&gt;This idea #1 is going to be very useful for those who want to do network booting, I reckon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01185</link>
		<title>Quirky is coming</title>
		<category>Quirky</category>
		<description>I have had some ideas in the back of my mind for sometime, but didn&#39;t know if they would work. These ideas are, well, &quot;quirky&quot;, hence when I create a distro based on them, then I&#39;ll name it &quot;Quirky&quot;.&lt;br /&gt;&lt;br /&gt;I conducted tests on two of these, and they work. Three of the ideas tackle these areas:&lt;br /&gt;&lt;br /&gt;1. Simpler installation and booting.&lt;br /&gt;2. More security when running.&lt;br /&gt;3. Clean shutdown.&lt;br /&gt;&lt;br /&gt;I needed to make configuration changes to the kernel, so took the opportunity to grab the latest, 2.6.31.5.&lt;br /&gt;&lt;br /&gt;This evening I&#39;ll be figuring out how to build Quirky using Woof. I&#39;ll probably have to write an extra script, &#39;quirky_build&#39; or something.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01184</link>
		<title>Why do I bother?</title>
		<category>Retirement</category>
		<description>I sometimes wonder why I bother. In my position, I deal with criticism on a daily basis. Some of it comes direct to me in emails and pm&#39;s.&lt;br /&gt;Then there is negativity by some who lurk on the #puppylinux IRC channel. &lt;br /&gt;Then there are those who post to the forum with superficial, mis-informed, nit-picking, and just plain wrong comments, like in this thread:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=48160 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=48160&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I really don&#39;t need the aggravation. The latest contribution on the forum has prompted me to think some more about my retirement. &lt;br /&gt;&lt;br /&gt;My original plan was to retire from Puppy development early in 2010. I want to keep working on Woof and do some Genie coding, and that will likely continue into 2010, 2011. &lt;br /&gt;&lt;br /&gt;The multi-user improvement -- yes that is a definite contender for incorporation into Woof. That&#39;s a short-term goal, I might do that soon.&lt;br /&gt;&lt;br /&gt;Puppy 4.4 and 5.0 are now being developed by the community. That&#39;s good. I&#39;ll probably give the access to the ibiblio.org site to one or two community members soon.&lt;br /&gt;&lt;br /&gt;I won&#39;t be bringing out another official Puppy release, so I am now retired in that regard. &lt;br /&gt;&lt;br /&gt;What I might do is release a new distro sometime, which is something that I have mentioned before. It will be 100% personal, no irc, no forum, just my thing. In fact, I&#39;m already working on it.&lt;br /&gt;It is not intended to be a general purpose distro.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01183</link>
		<title>Multiuser Puppy</title>
		<category>Woof</category>
		<description>This needs to get lots of attention I think, as pizzasgood has put in considerable effort to solve the problem of running Puppy with multiple users:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=47409 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=47409&lt;/a&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=47410 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=47410&lt;/a&gt;&lt;br /&gt;&lt;a href=http://www.browserloadofcoolness.com/ target=_blank&gt;http://www.browserloadofcoolness.com/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;What I commend in particular, is the effort that pizzasgood put in to document everything.&lt;br /&gt;&lt;br /&gt;It&#39;s good stuff, and I&#39;m looking into incorporating this into my Woof build system.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01182</link>
		<title>Genie bugs reported</title>
		<category>Woof</category>
		<description>I&#39;m working through my Genie web pages, updating them, and of course testing all the examples.&lt;br /&gt;&lt;br /&gt;I am using vala from git, October 24, 2009.&lt;br /&gt;&lt;br /&gt;Two of the examples (so far) do not compile and I have reported to the bugzilla:&lt;br /&gt;&lt;br /&gt;&lt;a href=https://bugzilla.gnome.org/show_bug.cgi?id=599635 target=_blank&gt;https://bugzilla.gnome.org/show_bug.cgi?id=599635&lt;/a&gt;&lt;br /&gt;&lt;a href=https://bugzilla.gnome.org/show_bug.cgi?id=599636 target=_blank&gt;https://bugzilla.gnome.org/show_bug.cgi?id=599636&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01181</link>
		<title>Main Genie page updated</title>
		<category>Woof</category>
		<description>Now that I am embarking on furthering my knowledge of Genie, I have made a start by updating my main Genie page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/genie/ target=_blank&gt;http://puppylinux.com/genie/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01180</link>
		<title>Problem with GTK 2.18.3</title>
		<category>Woof</category>
		<description>I have got a problem in Karmic Puppy. If I right-click on a file, choose something from the menu, the file-thumbnail becomes highlighted and stays highlighted. I have to click elsewhere in the Rox window to deselect it.&lt;br /&gt;&lt;br /&gt;This is a feature of GTK 2.18.3, the version used in Karmic Koala. I confirmed this by compiling GTK 2.18.3 in Puppy 4.3.1, which I&#39;m running right now.&lt;br /&gt;&lt;br /&gt;This is very unexpected behaviour, and extremely annoying. I thought it best to post this, as others will encounter it, and you need to know that it is a GTK problem. The thing is, is this behaviour configurable? How?&lt;br /&gt;&lt;br /&gt;By the way, I compiled glib 2.22.2, pango 1.26.0 and gtk+ 2.18.3 in Puppy 4.3.1, and I&#39;ll make them into PET packages and upload them to ibiblio. I&#39;ll also make database entries for them in Woof.&lt;br /&gt;&lt;br /&gt;So, 4.4 developers can use these packages if they want, or they may already have compiled these latest packages.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01179</link>
		<title>Karmic Puppy live-CD</title>
		<category>Woof</category>
		<description>Get it from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/test/karmic-puppy-20091024/ target=_blank&gt;http://puppylinux.com/test/karmic-puppy-20091024/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The Woof tarball and the &quot;Karmic Puppy&quot; live-CD ISO file are just snapshots of work-in-progress.&lt;br /&gt;&lt;br /&gt;The Woof tarball is currently configured to build from Ubuntu Karmic Koala packages, and I used 9.10RC packages. The Intel graphics on my laptop now seems to be behaving itself, no flicker!&lt;br /&gt;&lt;br /&gt;I think that it should be pretty straight forward to get Woof to build a Dpup as well, and ttuuxxx and gposil may have use for this latest Woof in their Dpup project. Anyone is welcome to use Woof and Karmic Puppy and further develop them.&lt;br /&gt;&lt;br /&gt;Their Dpup project:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47592 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47592&lt;/a&gt;&lt;br /&gt;&lt;a href=http://www.dpup.org/index.html target=_blank&gt;http://www.dpup.org/index.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;But for me, well, I&#39;m taking a break, going to work on learning more about Genie and update the online docs. My main Genie page was last updated in December 2008 -- well overdue for further attention!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01178</link>
		<title>ROX-Filer 2.9.0</title>
		<category>Woof</category>
		<description>I have compiled the latest version in Puppy 4.3. I want to use it in Karmic Puppy, compiling it in 4.3 ensures that the same package will work in any build from 4.3 upward.&lt;br /&gt;&lt;br /&gt;I did compile this awhile ago, but had problems with the mime types -- the thumbnails did not display properly. Ttuuxxx solved that, and I looked at ttuuxxx&#39;s Rox package -- yes there are name changes in some mime files. I now have it working properly. Thanks ttuuxxx.&lt;br /&gt;&lt;br /&gt;Shared-mime-info package is now upgraded to the latest, 0.70. The &#39;dev&#39; component now goes into the &#39;devx&#39; SFS file.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01177</link>
		<title>Woof: Making 0setup faster</title>
		<category>Woof</category>
		<description>I reported recently on the super-fast code that Wosh has created:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/blog/?viewDetailed=01167 target=_blank&gt;http://puppylinux.com/blog/?viewDetailed=01167&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Wosh sent me version 0.0.1 of PPKG today, and it is nice but not yet quite what I need for building Karmic Puppy.&lt;br /&gt;&lt;br /&gt;To fill the immediate need, I thought that I would take another look at the Debian/Ubuntu-to-Puppy database conversion code in the &#39;0setup&#39; script.&lt;br /&gt;&lt;br /&gt;Testing the Ubuntu &quot;main&quot; repository db, the script took about 11 minutes. I applied some lateral thinking, and have now got it down to about 2 minutes. &lt;br /&gt;&lt;br /&gt;Here is the new code:&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;v1PATTERN=&quot;s%\\-[0-9.]*${DISTRO_BINARY_COMPAT}[0-9.]*$%%&quot;&lt;br /&gt;v2PATTERN=&quot;s%\\+[0-9.]*${DISTRO_BINARY_COMPAT}[0-9.]*$%%&quot;&lt;br /&gt;   while read DB_ONELINE&lt;br /&gt;   do&lt;br /&gt;    eval $DB_ONELINE&lt;br /&gt;    case $DB_ONELINE in&lt;br /&gt;     Description*)&lt;br /&gt;      DB_fullfilename=&quot;`echo -n &quot;$Filename&quot; | rev | cut -f 1 -d &#39;/&#39; | rev`&quot;&lt;br /&gt;      DB_path=&quot;`echo -n &quot;$Filename&quot; | rev | cut -f 2-9 -d &#39;/&#39; | rev`&quot;&lt;br /&gt;      DB_version=&quot;`echo -n &quot;$Version&quot; | sed -e &#39;s%^[0-9]:%%&#39; -e &quot;$v1PATTERN&quot; -e &quot;$v2PATTERN&quot;`&quot;&lt;br /&gt;      DB_pkgrelease=&quot;`echo -n &quot;$Version&quot; | sed -e &#39;s%^[0-9]:%%&#39; -e &quot;s%${DB_version}%%&quot; -e &#39;s%^\\-%%&#39; -e &#39;s%^\\+%%&#39;`&quot;&lt;br /&gt;      DB_pkgname=&quot;${Package}_${DB_version}&quot;&lt;br /&gt;      DB_category=&quot;`${FIND_CAT} $Package &quot;$Description&quot;`&quot;&lt;br /&gt;      DB_dependencies=&quot;`echo -n &quot;$Depends&quot; | sed -e &#39;s%, %\n%g&#39; | cut -f 1 -d &#39; &#39; | tr &#39;\n&#39; &#39; &#39; | sed -e &#39;s% $%%&#39; -e &#39;s% %,+%g&#39; -e &#39;s%,$%%&#39;`&quot;&lt;br /&gt;      [ &quot;$DB_dependencies&quot; != &quot;&quot; ] &amp;&amp; DB_dependencies=&#39;+&#39;&quot;$DB_dependencies&quot;&lt;br /&gt;      echo &quot;$DB_pkgname|$Package|$DB_version|$DB_pkgrelease|$DB_category|${InstalledSize}K|$DB_path|$DB_fullfilename|$DB_dependencies|$Description|&quot; &gt;&gt; $ONE_PKGLISTS_COMPAT&lt;br /&gt;      echo -n &quot;$Package &quot;&lt;br /&gt;     ;;&lt;br /&gt;    esac&lt;br /&gt;   done&lt;&lt;_END1&lt;br /&gt;$(grep -E &#39;^Package:|^Installed\-Size:|^Architecture:|^Version:|^Depends:|^Filename:|^Description:&#39; ${ONE_PKGLISTS_COMPAT}pre | tr &#39;[\t&quot;|]&#39; &#39; &#39; | tr -s &#39; &#39; | sed -e &#39;s%^Installed\-Size%InstalledSize%&#39; -e &#39;s%: %=&quot;%&#39; -e &#39;s% $%%&#39; -e &#39;s%$%&quot;%&#39;)&lt;br /&gt;_END1&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;Of course the big one is the &quot;universe&quot; repo. The database file to be processed is 24MB, a lot to churn through. Universe now takes 9 minutes, so all-up the conversion time will be about 12 minutes, apart from the time to download the Debian/Ubuntu db files.&lt;br /&gt;The Debian repo is a bit smaller so conversion will be quicker.&lt;br /&gt;&lt;br /&gt;This faster script is just a temporary fix, as I expect to move onto PPKG soon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01176</link>
		<title>Aghanistan: why are we there?</title>
		<category>General</category>
		<description>The Afghanistan election fraud is in the news right now, but I watched a TV documentary a couple of nights ago, and the situation is very depressing...&lt;br /&gt;&lt;br /&gt;&quot;Four Corners&quot; is a long-running and very reputable documentary program here in Australia. The last one was on what has happened to all the aid going into Afghanistan:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.abc.net.au/4corners/content/2009/s2714822.htm target=_blank&gt;http://www.abc.net.au/4corners/content/2009/s2714822.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;18 billion dollars. The reporter wanted to follow the money trails, find out where it went.&lt;br /&gt;&lt;br /&gt;The UN claims that 268 schools have been built, and the reporter asked for some addresses. But, he had trouble getting even one address, and when they finally gave him one, he went there and found a billboard with a picture of a grand building -- the billboard had been put up two years ago. What was actually built? -- there were some tents and the students were studying in those. &lt;br /&gt;&lt;br /&gt;And that was a lucky school. he found another &quot;school&quot;, they didn&#39;t even have a tent, they just sat outside, until it snowed too much.&lt;br /&gt;&lt;br /&gt;Then there was the hospital. The money donated was, if I recall, about 2.5 million, of which foreign NGOs took most for admin (etc.) and under 1 million finally got to the local construction company. The final building is shoddy, falling down, yet the foreign quality control engineers gave it the thumbs up.&lt;br /&gt;&lt;br /&gt;So, there is virtually no reconstruction, and whenever the reporter spoke to local people there was heaps of bitterness.&lt;br /&gt;&lt;br /&gt;Ah, but there is one area where there&#39;s lots of activity -- mansions for the rulers. No delays there. Also no explanations how they can afford million dollar mansions.&lt;br /&gt;&lt;br /&gt;In summary, everyone is on the take, both Afghanistan and foreign companies. The UN, well, I don&#39;t know what to say about them.&lt;br /&gt;&lt;br /&gt;The overall picture is that the hearts and minds of the people have not been won. Just the opposite. If that&#39;s the case, then the foreign troops are staying there with some other agenda.&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01175</link>
		<title>Howto compile apps</title>
		<category>Woof</category>
		<description>It is happening slowly, but I have updated another web page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/development/compileapps.htm target=_blank&gt;http://puppylinux.com/development/compileapps.htm&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01174</link>
		<title>Another ibiblio mirror</title>
		<category>Woof</category>
		<description>Tony sent me this message:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Hi Barry,&lt;br /&gt;&lt;br /&gt;just to inform you I maintain a puppy mirror here since couple of years at ...&lt;br /&gt;&lt;br /&gt;Goodie Domain Service - www.gdsw.at (frontend)&lt;br /&gt;Vienna University of Technology, Austria, Central EU&lt;br /&gt;located @&lt;br /&gt; &lt;a href=ftp://gd.tuwien.ac.at/linux/puppylinux/ target=_blank&gt;ftp://gd.tuwien.ac.at/linux/puppylinux/&lt;/a&gt;&lt;br /&gt; &lt;a href=http://gd.tuwien.ac.at/linux/puppylinux/ target=_blank&gt;http://gd.tuwien.ac.at/linux/puppylinux/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;mirrored from ibiblio&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I&#39;ll add this to the download page.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01173</link>
		<title>Karmic Puppy: first build</title>
		<category>Woof</category>
		<description>I&#39;m running &quot;Karmic Puppy&quot; right now. This is Puppy built from Ubuntu Karmic Koala packages.&lt;br /&gt;&lt;br /&gt;Working nicely!&lt;br /&gt;&lt;br /&gt;One thing though, most annoying, have got that periodic screen flicker. This happens with Intel video hardware and arrived with Xorg 7.4.&lt;br /&gt;I did manage to get rid of it in a Jaunty build, by using a later Intel Xorg driver, but later when I tested an early version of Karmic, the flicker was back. Now, with the final release of karmic due out on the 29th of this month, the flicker is still there.&lt;br /&gt;&lt;br /&gt;Anyway, apart from that, this pup is running fine.  A bit fatter than your usual pup of course, with all those dependencies -- this build is 113MB with the SCSI and big-analog-modem drivers removed.&lt;br /&gt;&lt;br /&gt;There are a few things that I want to improve, which I&#39;ll work on for a few more days.&lt;br /&gt;&lt;br /&gt;I might look into compiling a Intel Xorg driver out of subversion.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01172</link>
		<title>Woof plans</title>
		<category>Woof</category>
		<description>Just to let everyone know what I&#39;m doing, or rather, plan to do.&lt;br /&gt;&lt;br /&gt;For sometime I have only used Woof to build a &quot;Ppup&quot; (Puppy from Puppy packages), that is, working toward 4.3.1.&lt;br /&gt;&lt;br /&gt;So, the other compatible-distros have not been recently tested, and with the GUI not at all.&lt;br /&gt;&lt;br /&gt;I have now started working on building from Karmic Koala (the upcoming Ubuntu 9.10) packages. Immediately I have found some problems with the GUI. Also I have made some improvements to the GUI to clarify how to use it.&lt;br /&gt;&lt;br /&gt;When I get a successful &quot;Karmic Puppy&quot; built, I&#39;ll upload another snapshot of the Woof tarball.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01171</link>
		<title>Puppy 4.3.1 released</title>
		<category>Woof</category>
		<description>Took a long time to upload to ibiblio.org, but finally got there! Download from ibiblio only for now, as not yet filtered through to the mirrors:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;When the mirrors catch up, you can get to them via the main Puppy download page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/download/ target=_blank&gt;http://puppylinux.com/download/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;There are lots of ISOs to choose from:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1/readme-files.htm target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1/readme-files.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...the main guy, that will suit most people, is &#39;pup-431.iso&#39;, size 104.9MB.&lt;br /&gt;&lt;br /&gt;The main announcement and release notes page is here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/download/release-4.3.htm target=_blank&gt;http://puppylinux.com/download/release-4.3.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...scroll down that page and you will see the list of differences between 4.3 and 4.3.1.&lt;br /&gt;&lt;br /&gt;I have started a forum thread for bug reports and feedback on 4.3.1:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47563 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47563&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...I will monitor it, but my attention will now be moving to development of Woof. Forum member technosaurus is carrying on with developing the Puppy 4.x series, that is, 4.4, and you can find various threads about it on the forum.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01170</link>
		<title>Preparing for 431-final</title>
		<category>Woof</category>
		<description>I decided to go back to my Partview. I like what Ecube has done, but I personally want to be able to see the free space in all partitions, mounted or not. Ecube&#39;s script could be extended to do that. My script is rather slow, as it generates gif images for each partition.&lt;br /&gt;I have applied clarf&#39;s bugfix so that my partview works properly in older kernels without libata drivers.&lt;br /&gt;&lt;br /&gt;Forum member MinHundHettePerro reported the problem of icon-stacking when there are too many drive icons to fit horizontally on the screen. This will have to be tackled in a future Puppy. The appropriate script is /sbin/pup_event_frontend_d, function free_coord().&lt;br /&gt;&lt;br /&gt;Zigbert has upgraded Pburn to 3.1.2-1, incorporating a fix from rerwin.&lt;br /&gt;&lt;br /&gt;Zigbert has upgraded Pfind to 4.15-1, incorporating a fix from rerwin.&lt;br /&gt;&lt;br /&gt;One thing that is disappointing is that there have been a lot of bug reports using the Network Wizard, but we currently don&#39;t have anyone maintaining it. This will need to be tackled for 4.4.&lt;br /&gt;&lt;br /&gt;If I recall rightly, there have been two main problems: having to scan twice for a wireless network, and settings not (properly) remembered between boots.&lt;br /&gt;&lt;br /&gt;To a lesser extent problems have been reported with Pnethood, and again it is not currently maintained.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01169</link>
		<title>Puppy 4.3.1-RC2</title>
		<category>Woof</category>
		<description>Earlier today I was unable to login to ibiblio.org, so I uploaded the files to here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/test/puppy-4.3.1-rc2/ target=_blank&gt;http://puppylinux.com/test/puppy-4.3.1-rc2/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Ah, uploads at 3 times the speed of ibiblio (30KB/sec compared with 10KB/sec)!&lt;br /&gt;&lt;br /&gt;Just a minimum upload, only one ISO, 2.6.30.5 kernel, no Intel 536/537 modules, 104MB.&lt;br /&gt;&lt;br /&gt;I have also uploaded Woof, so anyone who is interested can try the new GUI.&lt;br /&gt;&lt;br /&gt;Right now it is 6pm Wednesday October 14 here in Western Australia. I&#39;ll be busy with other stuff all day tomorrow, so about 24 hours from now I&#39;ll take a look at any feedback.&lt;br /&gt;&lt;br /&gt;Note, I put in Ecube&#39;s Partview, although it does have a bug, doesn&#39;t run if no partitions are mounted. It only displays free space in mounted partitions, whereas my Partview in 4.3.1-RC1 displays free space in all partitions. Actually, it would be possible to extend Ecube&#39;s Partview to also display free space in unmounted partitions. My script is still there, renamed to &#39;partview_all&#39;.&lt;br /&gt;&lt;br /&gt;My previous blog post summarises the bugfixes:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/blog/?viewDetailed=01168 target=_blank&gt;http://puppylinux.com/blog/?viewDetailed=01168&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Forum thread for feedback:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47795 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47795&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01168</link>
		<title>4.3.1 RC1, RC2 bugfixes</title>
		<category>Woof</category>
		<description>Here is a summary of the bugfixes so far, since the release of 4.3:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;4.3.1-RC1&lt;/b&gt;&lt;br /&gt;&lt;i&gt;New modem drivers and improved modem detection and dialup, from rerwin.&lt;br /&gt;Fixes for CD Remaster script.&lt;br /&gt;Asunder CD ripper replaces Ripoff (which crashed).&lt;br /&gt;Cdparanoia upgraded to latest (previous crashed).&lt;br /&gt;You2pup, fix for spaces in paths.&lt;br /&gt;Ayttm multi-protocol chat client, upgraded to 0.6.0-9.&lt;br /&gt;DidiWiki personal wiki upgraded to 0.8.&lt;br /&gt;JWM window manager upgraded to revision 457.&lt;br /&gt;NicoEdit, our secondary text editor, upgraded to 2.4.&lt;br /&gt;Pburn upgraded to 3.1.1.&lt;br /&gt;&#39;resolv.conf&#39; circular symlinks maybe fixed?&lt;br /&gt;JWM Configure tool bug fix (&#39;.jwmrc-tray&#39; got corrupted).&lt;br /&gt;&#39;man&#39; and Help page fixed when search on linux.die.net.&lt;br /&gt;Frequency scaling fix for &quot;small&quot; iso (modules were missing).&lt;br /&gt;Shutdown problem when upgrade &#39;pupsave&#39; (shutdown scripts in wrong place).&lt;br /&gt;Partview, a new tool to view free space in drives.&lt;br /&gt;Sylpheed PET package upgraded to 2.7.1 (previous crashes).&lt;br /&gt;Mouse Wizard fixed (showed USB when a PS/2 was connected).&lt;br /&gt;Lots of bugfixes for the Puppy Package Manager (PPM).&lt;br /&gt;Some corrections in the locale-choosing dialog.&lt;br /&gt;Boot from ext4 and save &#39;pupsave&#39; to ext4 partition fixed.&lt;br /&gt;The famous &quot;insert key&quot; crash in Mozilla browsers fixed.&lt;br /&gt;Fixed modules loading for kernels prior to 2.6.24.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;4.3.1-RC2,-final&lt;/b&gt;&lt;br /&gt;&lt;i&gt;Some SVG images were not displaying in GTK applications. Fixed.&lt;br /&gt;Typo in You2pup script.&lt;br /&gt;CD/DVD Drive Wizard was broken. Rewritten.&lt;br /&gt;Fix for JWM Config keyboard script.&lt;br /&gt;Grammar checker default in Abiword is now off, as it is so slow.&lt;br /&gt;Fix for overlapping drive icons on desktop at certain screen resolutions.&lt;br /&gt;Partview simplified, faster.&lt;br /&gt;Burniso2cd could sometimes fail to perform the verify-step properly. Fixed.&lt;br /&gt;Pburn bugfixes.&lt;br /&gt;snd-ali5451.ko module added to Smartlink modem driver system.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m uploading 4.3.1-RC2 now, will announce it soon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01167</link>
		<title>Debian to Puppy database converter</title>
		<category>Woof</category>
		<description>Brilliant! Look at what Wosh has done:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=47763 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=47763&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I don&#39;t know about the need for a contest though, I reckon that 10,553 times faster than my script is pretty good &lt;img src=smilies/happy.gif /&gt;&lt;br /&gt;&lt;br /&gt;I want to get back onto testing Woof with other distros, probably Lenny and Karmic in the next few days, well immediately after I get 4.3.1-final released.&lt;br /&gt;&lt;br /&gt;So your converter is so so welcome. That script &#39;0setup&#39; is not just used in Woof, the 3builddistro script copies 0setup to /usr/local/petget in the built Puppy. It is used by the Puppy Package Manager to update the package database.&lt;br /&gt;&lt;br /&gt;So, when a user goes into the &#39;Configure PPM&#39; section and clicks on the button to update the package databases, they don&#39;t want to be waiting around for one hour! That&#39;s the main reason your program is so important.&lt;br /&gt;&lt;br /&gt;I&#39;ll get onto playing with it real soon.&lt;br /&gt;&lt;br /&gt;Note, I think that I filtered out []() from the description fields as those characters may have interfered with grep or sed when reading and processing the database. But, would have to check that, probably there is a workaround for that. Or, I may have just filtered them out because I thought potentially they could cause trouble.&lt;br /&gt;&lt;br /&gt;One other small detail, &quot;menu categories&quot; are really just &quot;categories&quot;. A package can belong in a certain category, say &quot;System&quot; but not have a menu entry. The categories are mostly for the Puppy Package Manager to group the packages.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01166</link>
		<title>SVG solution</title>
		<category>Woof</category>
		<description>Thanks to forum member ljfr, I was able to implement a solution to the problem of some SVG icons not displaying (see previous blog post).&lt;br /&gt;&lt;br /&gt;ljfr found that upgrading the shared_mime_info package to the latest fixed the problem.&lt;br /&gt;&lt;br /&gt;In Puppy, the shared_mime_info files are cutdown and inside the rox_filer package. It is also a rather old version of shared_mime_info.&lt;br /&gt;&lt;br /&gt;shared_mime_info is overdue to be upgraded, and will have to be done when we upgrade rox_filer.&lt;br /&gt;&lt;br /&gt;But for now, with 431-final imminent, I do not want to &quot;rock the boat&quot;. I found out that just one file needs to be upgraded, /usr/share/mime/magic, so as a temporary measure, just for 431 really, I have created a new package &#39;zz400_mime_hack-431.pet&#39; with just that one file in it. &lt;br /&gt;&lt;br /&gt;Note, the reason it starts with &quot;z&quot; is so that Woof will copy it into the live-CD last, overwriting the existing &#39;magic&#39; file.&lt;br /&gt;&lt;br /&gt;I have done some tests, and nothing else seems to be broken. The Rox mime-handling uses the &#39;magic&#39; file, as does the &#39;file&#39; utility, and they seem happy with the new file.&lt;br /&gt;&lt;br /&gt;But, I think that I will have to bring out an RC2, just to be sure. Of course, once again, I hope that I can just promote it to the final after a couple of days.&lt;br /&gt;&lt;br /&gt;I will probably upload 431-RC2 tomorrow.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01165</link>
		<title>SVG mystery</title>
		<category>Woof</category>
		<description>4.3x testers have reported that some SVG images do not display in ROX or Viewnior.&lt;br /&gt;&lt;br /&gt;Those in /usr/local/lib/X11/themes/FlatOrange do.&lt;br /&gt;&lt;br /&gt;Newer ones, such as created in Inkscape, do not.&lt;br /&gt;&lt;br /&gt;I wondered if perhaps &#39;librsvg&#39;, which is the package that provides SVG support for GTK, needed to be compiled with its optional dependency &#39;libcroco&#39; (provides support for SVG images that have CSS formating).&lt;br /&gt;&lt;br /&gt;So, I compiled libcroco 0.6.2 and recompiled librsvg 2.22.3. Nup, same problem.&lt;br /&gt;&lt;br /&gt;So, I grabbed the latest librsvg, 2.26.0, but still no good.&lt;br /&gt;&lt;br /&gt;Then I tried this (&#39;rsvg-view&#39; is a utility in the librsvg pkg):&lt;br /&gt;&lt;br /&gt;# rsvg-view &lt;svg file&gt;&lt;br /&gt;&lt;br /&gt;...hey, it displays!&lt;br /&gt;&lt;br /&gt;So, librsvg itself is okay, GTK is somehow the problem.&lt;br /&gt;If I try to open one of the newer SVG files in Viewnior, it reports an &quot;unrecognised file format&quot;. C**p.&lt;br /&gt;&lt;br /&gt;So, I wondered, just what is different between the SVG files that do display, and those that don&#39;t?&lt;br /&gt;&lt;br /&gt;I have one that doesn&#39;t, &#39;brasero.svg&#39;, the first few lines of the file:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&gt;&lt;br /&gt;&lt;!-- Created with Inkscape (http://www.inkscape.org/) --&gt;&lt;br /&gt;&lt;svg&lt;br /&gt;   xmlns:svg=&quot;http://www.w3.org/2000/svg&quot;&lt;br /&gt;   xmlns=&quot;http://www.w3.org/2000/svg&quot;&lt;br /&gt;   xmlns:xlink=&quot;http://www.w3.org/1999/xlink&quot;&lt;br /&gt;   version=&quot;1.0&quot;&lt;br /&gt;   width=&quot;48&quot;&lt;br /&gt;   height=&quot;48&quot;&gt;&lt;br /&gt;  &lt;defs&lt;br /&gt;     id=&quot;defs3&quot;&gt;&lt;br /&gt;    &lt;linearGradient&lt;br /&gt;       id=&quot;linearGradient5349&quot;&gt;&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;/usr/local/lib/X11/themes/FlatOrange/camera.svg works, here are the first few lines:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&gt;&lt;br /&gt;&lt;!DOCTYPE svg PUBLIC &quot;-//W3C//DTD SVG 20010904//EN&quot;&lt;br /&gt;&quot;http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd&quot;&gt;&lt;br /&gt;&lt;!-- Created with Inkscape (&quot;http://www.inkscape.org/&quot;) --&gt;&lt;br /&gt;&lt;svg&lt;br /&gt;   version=&quot;1.0&quot;&lt;br /&gt;   x=&quot;0.0000000&quot;&lt;br /&gt;   y=&quot;0.0000000&quot;&lt;br /&gt;   width=&quot;162.50000&quot;&lt;br /&gt;   height=&quot;162.50000&quot;&lt;br /&gt;   id=&quot;svg183&quot;&lt;br /&gt;   sodipodi:version=&quot;0.32&quot;&lt;br /&gt;   inkscape:version=&quot;0.36&quot;&lt;br /&gt;   sodipodi:docname=&quot;/usr/local/lib/X11/themes/Outline-svg/camera.svg&quot;&lt;br /&gt;   sodipodi:docbase=&quot;/usr/local/lib/X11/themes/Outline-svg&quot;&lt;br /&gt;   xmlns=&quot;http://www.w3.org/2000/svg&quot;&lt;br /&gt;   xmlns:inkscape=&quot;http://www.inkscape.org/namespaces/inkscape&quot;&lt;br /&gt;   xmlns:sodipodi=&quot;http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd&quot;&lt;br /&gt;   xmlns:xlink=&quot;http://www.w3.org/1999/xlink&quot;&gt;&lt;br /&gt;  &lt;sodipodi:namedview&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;So guess what? I copied that &quot;DOCTYPE&quot; declaration from camera.svg, pasted it into brasero.svg -- now brasero.svg displays!&lt;br /&gt;&lt;br /&gt;My memory of the SVG standard is that it needs that DOCTYPE declaration. So how come all the recent SVG images I have downloaded, created by Inkscape, don&#39;t have it? I just checked something, compiled GTK 2.16.6, still the same problem.&lt;br /&gt;&lt;br /&gt;So, I am stuck with a mystery. I have a workaround, but really when we download SVG images we want them to display as-is, not have to edit them. Anyone got a solution? As things stand, I will have to go to 431-final with this not properly resolved.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01164</link>
		<title>Hard-Puppy page updated</title>
		<category>Woof</category>
		<description>I have updated this page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/hard-puppy.htm target=_blank&gt;http://puppylinux.com/hard-puppy.htm&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01163</link>
		<title>Web pages updated</title>
		<category>Woof</category>
		<description>There is a lot more to do, but I have made a start updating web pages at puppylinux.com.&lt;br /&gt;&lt;br /&gt;A page that is highly recommended that all Puppy newcomers should read is the overview of package management:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/development/package-management.htm target=_blank&gt;http://puppylinux.com/development/package-management.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have also updated, at least partially, pages on Woof and the PPM:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/woof/ target=_blank&gt;http://puppylinux.com/woof/&lt;/a&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/woof/ppm.htm target=_blank&gt;http://puppylinux.com/woof/ppm.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This page is now a redirect to the main Woof page:&lt;br /&gt;&lt;a href=http://puppylinux.com/development/puppy-unleashed.htm target=_blank&gt;http://puppylinux.com/development/puppy-unleashed.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Documentation on the old Unleashed and PETget have been replaced with Woof and the PPM.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01162</link>
		<title>Service Pack for 4.3</title>
		<category>Woof</category>
		<description>Get it from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1-RELEASE-CANDIDATE/service_pack-430-to-431.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1-RELEASE-CANDIDATE/service_pack-430-to-431.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This is not as &quot;complete&quot; as a proper upgrade to Puppy 4.3.1, but is handy in certain circumstances, such as you have a full install of 4.3 to hard drive -- in that case, just download and install the PET and you have upgraded.&lt;br /&gt;&lt;br /&gt;At least I hope so, I haven&#39;t tested it.&lt;br /&gt;&lt;br /&gt;Probably the Service Pack is adequate if you are running 4.3 from CD, USB or frugal install and you just want a quick upgrade to 4.3.1.&lt;br /&gt;&lt;br /&gt;One thing that is missing is the latest &#39;initrd.gz&#39;, needed for booting from ext4 partitions. But you don&#39;t need that for a full hd installation. But you will have to get it for your USB/frugal installation -- but then you might as well grab the new pup-431.sfs too.&lt;br /&gt;&lt;br /&gt;But of course the Service Pack is small, just 4.4MB, whereas pup-431.sfs is about 103MB&lt;br /&gt;&lt;br /&gt;Note that I did not put the 537* modem drivers into the service pack.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01161</link>
		<title>Puppy 4.3.1-release-candidate</title>
		<category>Woof</category>
		<description>Available from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1-RELEASE-CANDIDATE/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1-RELEASE-CANDIDATE/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Puppy 4.3.1 is a bug-fix release of 4.3. Here are the highlights of things fixed, upgraded and improved. These items are in my blog (read the archive for October &lt;a href=http://puppylinux.com/blog/?do=archive target=_blank&gt;http://puppylinux.com/blog/?do=archive&lt;/a&gt;):&lt;br /&gt;&lt;br /&gt;&lt;i&gt;New modem drivers and improved modem detection and dialup, from rerwin.&lt;br /&gt;Fixes for CD Remaster script.&lt;br /&gt;Asunder CD ripper replaces Ripoff (which crashed).&lt;br /&gt;Cdparanoia upgraded to latest (previous crashed).&lt;br /&gt;You2pup, fix for spaces in paths.&lt;br /&gt;Ayttm multi-protocol chat client, upgraded to 0.6.0-9.&lt;br /&gt;DidiWiki personal wiki upgraded to 0.8.&lt;br /&gt;JWM window manager upgraded to revision 457.&lt;br /&gt;NicoEdit, our secondary text editor, upgraded to 2.4.&lt;br /&gt;Pburn upgraded to 3.1.1.&lt;br /&gt;&#39;resolv.conf&#39; circular symlinks maybe fixed?&lt;br /&gt;JWM Configure tool bug fix (&#39;.jwmrc-tray&#39; got corrupted).&lt;br /&gt;&#39;man&#39; and Help page fixed when search on linux.die.net.&lt;br /&gt;Frequency scaling fix for &quot;small&quot; iso (modules were missing).&lt;br /&gt;Shutdown problem when upgrade &#39;pupsave&#39; (shutdown scripts in wrong place).&lt;br /&gt;Partview, a new tool to view free space in drives.&lt;br /&gt;Sylpheed PET package upgraded to 2.7.1 (previous crashes).&lt;br /&gt;Mouse Wizard fixed (showed USB when a PS/2 was connected).&lt;br /&gt;Lots of bugfixes for the Puppy Package Manager (PPM).&lt;br /&gt;Some corrections in the locale-choosing dialog.&lt;br /&gt;Boot from ext4 and save &#39;pupsave&#39; to ext4 partition fixed.&lt;br /&gt;The famous &quot;insert key&quot; crash in Mozilla browsers fixed.&lt;br /&gt;Fixed modules loading for kernels prior to 2.6.24.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Test like crazy! I hope to upload the final in a few days. It may even be the case that the release-candidate is fine and can simply be promoted to final.&lt;br /&gt;&lt;br /&gt;I will upload a Service Pack for Puppy 4.3, for those who have that version installed and would just like to install the fixes without doing a full version upgrade.&lt;br /&gt;&lt;br /&gt;I am doing a little bit more work on the Woof GUI and it will be in Woof when 4.3.1-final is released. The GUI is not complete and will have many more features, but should be basically usable. So far only tested building Puppy 4.3.1.&lt;br /&gt;&lt;br /&gt;I created &quot;delta&quot; files, so if you have previously downloaded &#39;pup-430.iso&#39; and &#39;devx_430.sfs&#39; then there are small .delta files that can be used to upgrade -- see &quot;Xdelta file difference manager&quot; in &quot;Utility&quot; menu.&lt;br /&gt;The delta file for the ISO is a bit big (38MB), due I think, to a different organisation -- I built 431 without a &#39;zdrv&#39; SFS file.&lt;br /&gt;&lt;br /&gt;Forum thread to report bugs:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47671 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47671&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;The &#39;PUP_430.SFS&#39; problem&lt;/b&gt;&lt;br /&gt;Many people who used Isobuster in Windows had this problem. It is solved by upgrading to the latest version of Isobuster (which is able to read Rock Ridge extensions in the ISO file).&lt;br /&gt;&lt;br /&gt;Also, to make it easier for people who want to open up the ISO, I have uploaded the individual files to &#39;inside-iso&#39; folder on ibiblio.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Intel 536/537 analog modems&lt;/b&gt;&lt;br /&gt;I left these out of &#39;pup-431.iso&#39; due to their huge size. Instead, I did a special build, pup-431-INTEL_MODEMS.iso&#39; in folder &#39;special-puppies&#39;.&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01160</link>
		<title>431 release candidate soon</title>
		<category>Woof</category>
		<description>I&#39;m uploading it now. I was putting it together about 1am, but so tired I was making mistakes... I think I built the iso ok, started the upload then went to bed. Now it&#39;s 6am, still uploading.&lt;br /&gt;&lt;br /&gt;I&#39;ll let you know when it&#39;s done. Still another 4 - 5 hours.&lt;br /&gt;&lt;br /&gt;I&#39;ll also prepare the Service Pack for 430 today.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01159</link>
		<title>Final stuff before 4.3.1</title>
		<category>Woof</category>
		<description>A quick note:&lt;br /&gt;&lt;br /&gt;I found the bug that caused the Remaster CD script to crash if there are two optical drives.&lt;br /&gt;&lt;br /&gt;I have applied rerwin&#39;s latest ltmodem stuff, pupscan change, pmodemdiag PET pkg into puppy4 repo.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01158</link>
		<title>4.x plans</title>
		<category>Woof</category>
		<description>I plan to upload 4.3.1-release-candidate in a couple of days.&lt;br /&gt;&lt;br /&gt;There are still some issues in 4.3 that are not resolved, so don&#39;t expect miracles, but also there are a lot of bugs fixed.&lt;br /&gt;&lt;br /&gt;The idea of the release-candidate is to check that none of my &quot;fixes&quot; broke something else. If there&#39;s nothing dumb in it, or something is found that I can readily fix, then the final should hopefully follow a few days later.&lt;br /&gt;&lt;br /&gt;Then I&#39;m going back to Woof and working on the GUI plus various usability enhancements.&lt;br /&gt;&lt;br /&gt;Technosaurus will be full steam ahead on 4.4... which leads me to technosaurus&#39; initiative, to put Puppy development onto google:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47627 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47627&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...check it out, give feedback to technosaurus.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01157</link>
		<title>Asunder 1.9</title>
		<category>Woof</category>
		<description>There have been reports that Ripoff, the CD song ripper in 4.3 and earlier puppies, dies half-way through if you try to rip an entire CD.&lt;br /&gt;&lt;br /&gt;Looking at the Ripoff project page, I see that it has not been updated for a long time. &lt;br /&gt;&lt;br /&gt;On the otherhand, Asunder is very active, so I compiled the latest, version 1.9, and tested it. Yep, lovely, I ripped off an entire CD to MP3 files.&lt;br /&gt;&lt;br /&gt;So, 4.3.1 will have Asunder, not Ripoff.&lt;br /&gt;&lt;br /&gt;Asunder home:&lt;br /&gt;&lt;a href=http://littlesvr.ca/asunder/ target=_blank&gt;http://littlesvr.ca/asunder/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01156</link>
		<title>cdparanoia III 10.2</title>
		<category>Woof</category>
		<description>It has been reported that cdparanoia crashes in pup 4.3.&lt;br /&gt;&lt;br /&gt;That is a rather old package, III-alpha9.8, which dates back to 2007. I have compiled the latest, III-10.2.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01155</link>
		<title>Aqualung improvement</title>
		<category>Woof</category>
		<description>Here is something else that I have found in ttuuxxx&#39;s &quot;431.1 Firefox Puppy&quot; thread....&lt;br /&gt;&lt;br /&gt;Forum member Gedrean posted this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Only problem I had was, and not sure if this is with yours or with puppy 430 in general, that Aqualung would never actually open with a file I clicked on, I had to afterwards drag it in there.&lt;br /&gt;Also the Aqualung script, when I read it, seemed horribly inefficient. Kill the other processes, then relaunch, with the argument? Not too elegant either.&lt;br /&gt;&lt;br /&gt;So I had about 5 hours of editing, finding that behaviors would change from minute to minute (probably my corrupted computer somehow), and agonizing over the Aqualung command line options and their strange intricacies (sometimes they will behave as advertised, ONLY if other arguments exist) but here&#39;s what I&#39;ve done:&lt;br /&gt;&lt;br /&gt;I&#39;ve managed to make the default behavior for Aqualung to Enqueue (add to playlist without clearing rest of it), caused it to only ever open ONE process and not need to kill others, and set it up so that there&#39;s a right-click for directories to enqueue the whole directory and contents in as well! (Great for my huge music directory!)&lt;br /&gt;&lt;br /&gt;I&#39;ve got three files I&#39;ll paste in code, they&#39;re very short, and I&#39;ll detail what I did (something I wish others would do, as bash scripts are incredibly hard to read!)&lt;br /&gt;&lt;br /&gt;First, aqualung launcher script, located in /usr/bin :&lt;br /&gt;Code:&lt;br /&gt;#!/bin/sh&lt;br /&gt;exec aqualung2 --session=0 -E /dev/null &quot;$@&quot;&lt;br /&gt;&lt;br /&gt;--session=0 tells it to do remote cue functions (according to the aqualung usage text) with session #0, which is either the first one already opened (and in this case the only) or the one which is opening now if no other session exists.&lt;br /&gt;If you&#39;ll note, especially ingenious, it attempts to Enqueue /dev/null, which will fail out with an error that it is unable to open that file ... this is required so that the -session=0 will actually do anything other than opening a new session.&lt;br /&gt;-E tells it to enqueue, and then it adds the remainder of any files. I spent a good amount of time making it add files with unicode/utf-8 chars, and spaces, and goofy characters, and it all works!&lt;br /&gt;&lt;br /&gt;Next, defaultaudioplayer script, located /usr/local/bin, and as an added bonus this is the same code for the Add to Audiolung Queue script located in ~/.config/rox.sourceforge.net/OpenWith/.inode_directory :&lt;br /&gt;Code:&lt;br /&gt;#!/bin/sh&lt;br /&gt;exec aqualung &quot;$@&quot;&lt;br /&gt;&lt;br /&gt;Of course, aqualung2 is the name of the aqualung app itself, sitting in /usr/bin.&lt;br /&gt;&lt;br /&gt;Thought I might share these and see what people (you, others?) think, and maybe contribute a bit more than requests to the whole puppy thing.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have done some basic testing, and this looks like a very nice improvement, a big step toward making Aqualung usable. It prevents multiple instances of Aqualung starting everytime a sound file is clicked on.&lt;br /&gt;&lt;br /&gt;I have implemented Gedrean&#39;s excellent fix, except named the startup script &#39;aqualung_wrapper&#39; and left the executable as &#39;aqualung&#39;.&lt;br /&gt;&lt;br /&gt;Note:&lt;br /&gt;One thing in Aualung that seems so unintuitive to me: if you have a playlist, click on one file in the list to highlight it, then click the &#39;Play&#39; button, wouldn&#39;t it be nice if just that file played? (and not the whole lot)&lt;br /&gt;&lt;br /&gt;&lt;b&gt;UPDATE:&lt;/b&gt;&lt;br /&gt;I found a a later post from Gedrean, a different script to fix a problem when defaultaudioplayer is called from streamtuner.&lt;br /&gt;However, I have found showstopper problems with both scripts. The second one, files no longer played (aqualung did not even start) when I clicked on a sound file in Rox.&lt;br /&gt;&lt;br /&gt;So, I have rolled back to the previous aqualung package, not using Gedrean&#39;s fix.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01154</link>
		<title>You2pup fix</title>
		<category>Woof</category>
		<description>dio444 fixed a bug in trio&#39;s You2pup:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;There is a bug that causes the script to fail, and hence the entire You2Pup system to fail if a local filename with spaces in it is chosen. The fix is easy, simply add &quot;&quot; to a few arguments.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I found this fix in ttuuxxx&#39;s &quot;431.1&quot; forum thread (430 with fixes and various changes including Firefox).&lt;br /&gt;&lt;br /&gt;Hmmm, good thing I decided to scan through that thread.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01153</link>
		<title>Ayttm 0.6.0-8</title>
		<category>Woof</category>
		<description>Technosaurus has compiled the latest from revision control. Thanks also to Michalis:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=42959 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=42959&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have upgraded to technosaurus&#39; package.&lt;br /&gt;&lt;br /&gt;Note to technosaurus: You need to include the *.la files in /usr/lib/ayttm. Ayttm needs them to recognise the plugins. At least, it used to.&lt;br /&gt;And of course, if you were making an official package to replace mine, you would have to include the &#39;pinstall.sh&#39; script.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01152</link>
		<title>DidiWiki 0.8</title>
		<category>Woof</category>
		<description>It&#39;s great, forum member &#39;amigo&#39; has done a lot of work on DidiWiki, our personal Wiki. This was a dead project. Forum thread:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47185 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47185&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I have upgraded to the latest, version 0.8.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01151</link>
		<title>JWM revision 457</title>
		<category>Woof</category>
		<description>Pstef posted to this blog yesterday:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Joe has updated JWM on its SourceForge site about two weeks ago. Those updates include Patriot&#39;s contribution too.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m keeping changes to a minimum right now, as 431 is imminent, but this is too much of a temptation. So, I have sneaked this package upgrade in too.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01150</link>
		<title>NicoEdit 2.4</title>
		<category>Woof</category>
		<description>I have upgrades Nicolas&#39;s NicoEdit text editor:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=46629&amp;start=15 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=46629&amp;start=15&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01149</link>
		<title>Pburn 3.1.1</title>
		<category>Woof</category>
		<description>I have upgraded zigbert&#39;s Pburn to the latest.&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=23881 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=23881&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01148</link>
		<title>resolv.conf circular symlinks</title>
		<category>Woof</category>
		<description>Forum memeber disciple posted this to the forum recently:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;This is a problem that seems to have been around for at least four years, although I think normally the people who report it are connecting with adsl modems rather than through an ethernet card to a router with DHCP.&lt;br /&gt;&lt;br /&gt;The last time I saw it reported was for 4.3 beta 1 or release candidate 1 or something, and I didn&#39;t see any report that it was fixed. My experience is with 4.1.1:&lt;br /&gt;I installed Puppy on a friend&#39;s USB drive, and we played around with it on a computer at work. He then took it home and had to rerun the network wizard, and then brought it back to work and reran the network wizard, and then took it home and couldn&#39;t connect to the internet even after running the network wizard. The reason is that /etc/resolv.conf had somehow been replaced by a link to /etc/ppp/resolv.conf, which itself is a link to /etc/resolv.conf. On both computers we are connecting via ethernet to a router with DHCP. My friend is completely new to Linux so wasn&#39;t messing around with configuration files or anything, so somehow the gui wizard scripts or something must be at fault.&lt;br /&gt;&lt;br /&gt;What I want to know is:&lt;br /&gt;1. Does anyone have any idea why this problem would occur occasionally, or what is causing it?&lt;br /&gt;2. Does anyone know if it has by any chance been fixed in 4.3?&lt;br /&gt;3. Does anyone know a reason why the network setup wizard shouldn&#39;t delete the two resolv.conf files / links (or rename them with a .bak or something) to make sure they can be created properly? &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;In the Roaring Penguin pppoe package, I modified /usr/sbin/pppoe-setup back in July 2008:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;    #v4.00 BK if enter &#39;server&#39;, somehow /etc/resolv.conf gets changed to a&lt;br /&gt;    #symlink to /etc/ppp/resolv.conf (which is a symlink to /etc/resolv.conf)&lt;br /&gt;    #so it&#39;s a circle. This script does not do that, something else does if it&lt;br /&gt;    #sees /etc/resolv.conf is empty. A workaround is to put something into it,&lt;br /&gt;    #what I have done is put in a free name server:&lt;br /&gt;    if [ &quot;$DNS1&quot; = &quot;server&quot; ];then&lt;br /&gt;     [ &quot;`grep &#39;^nameserver&#39; /etc/resolv.conf`&quot; = &quot;&quot; ] &amp;&amp; echo &#39;nameserver 208.67.222.222&#39; &gt;&gt; /etc/resolv.conf&lt;br /&gt;    fi&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;I never did find out what actually causes the circular symlink problem.&lt;br /&gt;&lt;br /&gt;However, my comment does indicate a possible solution, or at least a workaround. It all hinges on my comment &quot;something else does if it sees /etc/resolv.conf is empty&quot;. If that is correct, then perhaps all I need to do is have a comment in resolv.conf, like this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# nameservers go in here&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m very nervous messing around with such a vital file at this stage, when 4.3.1 is imminent, but this possible fix is worth a try. Well, there will be a 4.3.1-RC, so give the network setup a good test, make sure that a pre-existing comment in resolv.conf doesn&#39;t break anything. I can&#39;t see why, but you never know.&lt;br /&gt;&lt;br /&gt;Um, but maybe whatever causes that bug needs to see an actual &quot;nameserver&quot; entry in the file? We shall see.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01147</link>
		<title>Jwmconfig fix</title>
		<category>Woof</category>
		<description>A little while ago happypuppy reported a bug in the JWM Configure tool:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.puppylinux.com/blog/?viewDetailed=01059 target=_blank&gt;http://www.puppylinux.com/blog/?viewDetailed=01059&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...which I passed off as not a bug, not really. Well, it isn&#39;t a bug in the strict sense, if you don&#39;t manually edit /root/.jwmrc-tray, only use the GUI tools.&lt;br /&gt;&lt;br /&gt;Not very satisfactory though, and fortunately Patriot has taken a look at it and fixed it:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;The attached file contains theme-switcher fixes for the zero-byte length jwmrc-tray issue. I have previously looked at the codes and as you have noted, the blinky and xload -bg update routines may render a zero-byte length jwmrc-tray after the sed ...&lt;br /&gt;&lt;br /&gt;I&#39;ve attempted to improve it a little bit with a more robust code. It should fix the zero-byte length jwmrc-tray issue. Please take a peek and see if any of the new codes can be used ... &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Well, the attached code was in a p.m. to me, but I have put it into 4.3.1 which is coming RSN (Real Soon Now). The file is /usr/local/jwmconfig2/theme_switcher.&lt;br /&gt;&lt;br /&gt;The PET package is now &#39;jwmconfig2-20091009.pet&#39;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01146</link>
		<title>430: &#39;man&#39; fixed</title>
		<category>Woof</category>
		<description>Thanks to technosaurus for this clever fix:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;I bashed together a fix for the broken man pages that restores 99% functionality&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;#! /bin/bash&lt;br /&gt;defaulthtmlviewer &quot;http://www.google.com/search?&amp;q=man+&quot;$1&quot;+site:linux.die.net&amp;btnI=Search&quot;&lt;br /&gt;&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have put this into /usr/bin/man, specifically this at line 62:&lt;br /&gt;&lt;br /&gt;exec defaulthtmlviewer &quot;http://www.google.com/search?&amp;q=man+\&quot;${1}\&quot;+site:linux.die.net&amp;btnI=Search&quot;&lt;br /&gt;&lt;br /&gt;So, you can do something like:&lt;br /&gt;&lt;br /&gt;# man e2image&lt;br /&gt;&lt;br /&gt;...and yippee, it works!&lt;br /&gt;&lt;br /&gt;We also need the same fix for /usr/share/doc/index.html, the main Help page. It has a Javascript function:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;function search_site()&lt;br /&gt;{&lt;br /&gt;var url = &quot;http://linux.die.net/man/1/&quot;&lt;br /&gt;// Append the text box input to the search url for the selected site&lt;br /&gt;url = url + document.search_form.u_search.value;&lt;br /&gt;// Change the the browser location to the new url&lt;br /&gt;window.location.href = url;&lt;br /&gt;}&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;...anyone know Javascript, can figure out how to put technosaurus&#39;s fix into that function?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01145</link>
		<title>430: GIT &quot;broken&quot;</title>
		<category>Woof</category>
		<description>ARAN reported:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;The Package Git is broken especially &quot;git pull&quot; dont work !&lt;br /&gt;&lt;br /&gt;I was just at the git irc chanell and asked what could be the problem and this was here the answer.&lt;br /&gt;&lt;br /&gt;Quote:&lt;br /&gt;hello to all. can somebody tell me how to resolve this ugly problem here ?/usr/libexec/git-core/git-pull: line 204: exec: git-merge: not found&lt;br /&gt;git: &#39;pull&#39; is not a git-command. See &#39;git --help&#39;.&lt;br /&gt;&lt;br /&gt;Did you mean this?&lt;br /&gt;pull&lt;br /&gt;&lt;br /&gt;this here are all files in git-core folder. could it be that something is missed ?&lt;br /&gt;http://pastebin.com/m23ca0d9e&lt;br /&gt;&lt;br /&gt;Quote:&lt;br /&gt;&lt;br /&gt;Well, that error message really looks like some busted git installation.&lt;br /&gt;&lt;br /&gt;Aw... Seems like they stripped out all direct executables for builtin commands, but didn&#39;t note that some scripts need the direct executables for those... &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Yes, some files are missing out of that &#39;git-core&#39; directory. I created a new PET pkg with all the files in &#39;git-core&#39;, but the PET is 49MB (yes I did strip), compared with 5.5MB before. I do not want to blow out the &#39;devx&#39; by another 43.5MB!!!&lt;br /&gt;&lt;br /&gt;I don&#39;t remember how I created my 5.5MB cut-down git pkg. Anyway, I have just put in &#39;git-merge&#39;, as that was the missing one in ARAN&#39;s post.&lt;br /&gt;&lt;br /&gt;Comment: that sure is one bloated project!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01144</link>
		<title>430: frequency scaling</title>
		<category>Woof</category>
		<description>Aragon reported:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;as pointed out by aran: frequency scaling is not working in 4.30.&lt;br /&gt;&lt;br /&gt;this is a problem for pup-430-small.iso. small seems to miss more modules than i thought. having a scaling-app but no modules is a bug i think.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Ok, I have fixed that in the &quot;small&quot; build.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01143</link>
		<title>430: Aqualung?</title>
		<category>Woof</category>
		<description>Guys, what&#39;s the verdict on Aqualung in 4.3?&lt;br /&gt;&lt;br /&gt;Personally, I don&#39;t like it. There was some feedback I think that it crashes.&lt;br /&gt;&lt;br /&gt;Should I change to Pmusic?&lt;br /&gt;Or, go back to how it was in pup 4.1x? (click on a sound file either launched a commandline player or Gxine).&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01142</link>
		<title>Memtest in 2.6.30.5</title>
		<category>Woof</category>
		<description>In the 4.3 feedback thread one of the guys laments the absence of memtest.&lt;br /&gt;&lt;br /&gt;I took it out as the kernel from 2.6.26 has a simplified memtest builtin:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://kernelnewbies.org/Linux_2_6_26 target=_blank&gt;http://kernelnewbies.org/Linux_2_6_26&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If I boot with &quot;puppy memtest loglevel=7&quot;, nothing is reported.&lt;br /&gt;&lt;br /&gt;Looking at kernel git logs:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=272b9cad6e7a2f61b13cfcd7dde0010e02e9376e target=_blank&gt;http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=272b9cad6e7a2f61b13cfcd7dde0010e02e9376e&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;x86: early memtest to find bad ram&lt;br /&gt;&lt;br /&gt;do simple memtest after init_memory_mapping&lt;br /&gt;&lt;br /&gt;use find_e820_area_size to find all ram range that is not reserved.&lt;br /&gt;&lt;br /&gt;and do some simple bits test to find some bad ram.&lt;br /&gt;&lt;br /&gt;if find some bad ram, use reserve_early to exclude that range.&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;...which seems to indicate that bad ram is automatically reserved.&lt;br /&gt;&lt;br /&gt;Looking in the kernel source documentation, kernel-parameters.txt:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;memtest=	[KNL,X86] Enable memtest&lt;br /&gt;			Format: &lt;integer&gt;&lt;br /&gt;			default : 0 &lt;disable&gt;&lt;br /&gt;			Specifies the number of memtest passes to be&lt;br /&gt;			performed. Each pass selects another test&lt;br /&gt;			pattern from a given set of patterns. Memtest&lt;br /&gt;			fills the memory with this pattern, validates&lt;br /&gt;			memory contents and reserves bad memory&lt;br /&gt;			regions that are detected.&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;...oh, just putting &quot;memtest&quot; as the boot parameter actually does nothing!!!?&lt;br /&gt;&lt;br /&gt;So, I tried &quot;puppy memtest=2 loglevel=7&quot;.&lt;br /&gt;&lt;br /&gt;Still nothing. Run &#39;dmesg&#39; after bootup, nothing in there. Look in /proc and /sys, can&#39;t find anything in there.&lt;br /&gt;&lt;br /&gt;So, a memtest feature that reserves any bad ram it finds, but doesn&#39;t actually report any of its findings ...unless it only reports if bad ram found? ...I think that borders on useless -- well, no, not &quot;useless&quot;, but less than satisfactory.&lt;br /&gt;&lt;br /&gt;Note, the 2.6.30.5 kernel is configured with:&lt;br /&gt;&lt;i&gt;CONFIG_MEMTEST=y&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;So, for pup 4.4 we do need to consider putting memtest86+ in.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01141</link>
		<title>430: Shutdown problem when upgrade pupsave</title>
		<category>Woof</category>
		<description>This problem is reported in a couple of places, including here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47169 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47169&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m not clear on why this problem is occurring, anyway I have put this code into /etc/rc.d/rc.update:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;  if [ $NEWPVERSION -gt 424 -a $OLDPVERSION -lt 424 ];then #424=4.3beta3&lt;br /&gt;   if [ -d /usr/X11R7/bin ];then&lt;br /&gt;    ln -snf /usr/bin/restartwm /usr/X11R7/bin/restartwm&lt;br /&gt;    ln -snf /usr/bin/wmexit /usr/X11R7/bin/wmexit&lt;br /&gt;    ln -snf /usr/bin/wmpoweroff /usr/X11R7/bin/wmpoweroff&lt;br /&gt;    ln -snf /usr/bin/wmreboot /usr/X11R7/bin/wmreboot&lt;br /&gt;   fi&lt;br /&gt;  fi&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01140</link>
		<title>The &#39;-&#39; versus &#39;_&#39; problem</title>
		<category>Woof</category>
		<description>I responded to alecz here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/blog/?viewDetailed=01129 target=_blank&gt;http://puppylinux.com/blog/?viewDetailed=01129&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...with a suggestion.&lt;br /&gt;&lt;br /&gt;I have an idea. You have installed the files to a hd, you mount the hd from a running Puppy and the files look correct. But when you try and boot from the hd, Puppy cannot find &#39;pup-430.sfs&#39;. &lt;br /&gt;&lt;br /&gt;If that is your situation, try mounting the hd (while running Puppy) from the commandline using &#39;-t msdos&#39;. This is suggestion I replied to alecz:&lt;br /&gt;&lt;br /&gt;Suggestion: mount the hd like this (if partition is sdb1):&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# mount -t msdos /dev/sdb1 /mnt/sdb1&lt;br /&gt;# ls /mnt/sdb1&lt;br /&gt;# umount /mnt/sdb1&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...if the names are wrong, let me know. You can correct them before unmounting.&lt;br /&gt;&lt;br /&gt;Do try the above, not just the GUI tools in Puppy, as Puppy mounts a fat f.s with &#39;-t vfat&#39;, and that might be hiding your problem. &lt;br /&gt;&lt;br /&gt;Oh, and to provide me with more complete information, run this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# disktype /dev/sdb1&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...you can drag the mouse to highlight the text in the xterm window, then use middle-mouse-button to paste it anywhere.</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01139</link>
		<title>Partview returns</title>
		<category>Woof</category>
		<description>I have been working through the 4.3-bugs forum thread, and a couple of guys have expressed sadness that the old &#39;Partview&#39; application is not there.&lt;br /&gt;&lt;br /&gt;Well, it was in Puppy 3.x, but gone in 4.0x and 4.1x as the required tcl/tk libraries were not there. However those libraries returned in 4.2x and so did Partview.&lt;br /&gt;&lt;br /&gt;Once again in 4.3 Partview (and tcl/tk) is gone.&lt;br /&gt;&lt;br /&gt;Actually all this time I was hoping that someone might write an equivalent using GTK, however noone did. So, today I decided to do it.&lt;br /&gt;&lt;br /&gt;I knocked together a very simple Partview, that has both more and less features than the old one. This new one can have features added later if desired.&lt;br /&gt;&lt;br /&gt;What it does not do is update, it is just a static display. An extra thing that it does do is show free space on all partitions, whether they are mounted or not. Snapshot:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://puppylinux.com/apps/partview.png /&gt;&lt;br /&gt;&lt;br /&gt;...notice that it even shows free space in an optical disc, which is very handy if it is not closed, open for further burning, as in the case of multisession CD/DVD.&lt;br /&gt;&lt;br /&gt;It is launched from the JWM tray, and as it is (currently) static, it has to be re-executed whenever you want to see the latest free spaces -- which is really ok, usually we don&#39;t want yet another app that has a polling loop taking up CPU time.&lt;br /&gt;&lt;br /&gt;However, maybe could put a &quot;refresh&quot; button, or even auto-polling if desired. They are possibilities for the future.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01138</link>
		<title>Pwidgets in PPM</title>
		<category>Woof</category>
		<description>Pwidgets was missing from the PPM. There is a report  that it works fine in 4.3, so I have added it to the PPM, in the &#39;puppy4&#39; repo.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01137</link>
		<title>537 upgrade</title>
		<category>Woof</category>
		<description>Rerwin has posted upgraded &#39;-3&#39; Intel 537 modem udev rules and firmware:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46594&amp;start=60 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46594&amp;start=60&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The new PET package is:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;intel-537EP_secure-2.60.80.0-3.pet&lt;/i&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01136</link>
		<title>Extra network modules for 2.6.30.5</title>
		<category>Woof</category>
		<description>Tempestuous has compiled extra drivers for the 2.6.30.5 kernel (as used in Puppy 4.3):&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47267 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47267&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;As I am restricting 431 to essential bugfixes only, I am reluctant to put them in.&lt;br /&gt;&lt;br /&gt;Perhaps many of them can go into 4.4?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01135</link>
		<title>PupDial upgrade</title>
		<category>Woof</category>
		<description>Rerwin posted this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;If a pupdial user checks the Stupid Mode box or unchecks the Auto Reconnect box for Account 1, those changes are not retained across dialup connections or for a subsequent pupdial session. This problem was introduced during 3G-wireless implementation and is easily fixed.&lt;br /&gt;&lt;br /&gt;An ongoing concern regarding the wireless modem support has been that at least one ISP requires addition of a dialer command to permit connection. This forces the user to edit a file within the dialup structure, which should not be required of new users. In particular, VirginBroadband aborts a connection if the &quot;chap&quot; form of authentication is attempted. Forum member 01micko finds that adding &quot;-chap&quot; to the /etc/ppp/options file prevents the attempt and allows connection to that ISP.&lt;br /&gt;&lt;br /&gt;I have added a simple, generic fix that adds the content of a file named for the ISP (matching the APN) to the wvdial files as it is copied to /etc/ppp/peers for each connection. The particular file resides in /etc/wvdial_options. Users who discover a need for a special dialer command can add an appropriate file to that directory. This implementation associates the use of the command to each account.&lt;br /&gt;&lt;br /&gt;Thanks to 01micko&#39;s reporting of both issues, I attach a fixed pupdial and the new file for VirginBroadband, as well as difference files. Thanks, too, to gyro for raising the checkbox issue. I did not change the Reconnect default, but will wait to hear objections first and can update the attachment (to -2).&lt;br /&gt;&lt;br /&gt;UPDATE 9/24/09: I have replaced the fix dotpet with better ones. Both dotpets have a more thorough implementation of the bug fix. Because the lines handled by that code are mainly entered by the user, the code ensures that the lines are entered only in the account sections of wvdial.conf and ignores such lines entered elsewhere in wvdial.conf.&lt;br /&gt;&lt;br /&gt;The APN-specific option remains, except that the VirginBroadband entry is not to be included in puppy, instead being supplied by the user (who would know when the option may no longer be required). But the dotpet does create the file when the dotpet is installed.&lt;br /&gt;&lt;br /&gt;To address purple_ghost&#39;s concern about Auto Reconnect being abused to keep a connection during long idle periods, I added support for a possible user-entered line: &quot;Idle Seconds&quot;, which times out after a specified period of inactivity. I also added that item to the wvdial.conf help information accessible from pupdial. This allows protection from inadvertent wastage of connect time and cost, but also disables auto-reconnect. Setting this would prevent a customer from accumulating excessive connect times. However, the Auto Reconnect setting is not unchecked when reconnect is disabled. I am reluctant to change the default setting of Auto Reconnect, as I feel that is Barry&#39;s decision to make. But now turning it off (or having it disabled) yields the benefit of protection from runaway connect charges. (I originally hoped that &quot;Idle Seconds&quot; would leave auto-reconnect active, but that is not the case.)&lt;br /&gt;&lt;br /&gt;The (-1) bugfix-only dotpet is provided in case Barry declines to accept anything beyond the serious bug fix for 4.3.1, although I hope he will consider taking the modest refinements, too. &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;He posted this PET package:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;pupdial_update_to_P430-final-2-refinements.pet &lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...as well as an upgrade for the &#39;pupdial&#39; script, a documentation file also had to be changed in the &#39;wvdial&#39; PET package.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01134</link>
		<title>Sound and HSF-modem conflict</title>
		<category>Woof</category>
		<description>Rerwin posted this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;lwill and others report issues with sound cards and the HSF modem drivers. At least part of their problems involve the loading of HSF modem drivers instead of the sound-card modem driver. This is due to particular modems being supported by two or more drivers (in modules.alias). To resolve this, I have added to the PCI_OVERRIDES definition in /etc/rc.d/MODULESCONFIG entries forcing use of the sound-card modem drivers instead of the HSF counterparts.&lt;br /&gt;&lt;br /&gt;In researching this issue, I discovered similar conflicts between some HCF and HSF drivers, so I forced one of them, based on their descriptions in the PCI_IDs listing. This confusion may be due to original misidentification of the HCF/HSF modems.&lt;br /&gt;&lt;br /&gt;While updating MODULESCONFIG, I discovered that the a-f characters in the &quot;hso&quot; entries were erroneously capitalized.&lt;br /&gt;&lt;br /&gt;The updated file is attached as a dotpet for anyone to try, along with difference files for it.&lt;br /&gt;Richard&lt;br /&gt;&lt;br /&gt;UPDATE 10/2/09: After reading that the modems that belong to both an HSF and ALSA driver probably need both, I have removed the overrides for them. iwill reports that the override did not prevent the HSF driver from running and that the modem did not work, although the sound card did. But the other changes are valid, for now.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;And an upgrade for /etc/rc.d/MODULESCONFIG:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;MODULESCONFIG_update_to_P430-2.pet&lt;/i&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01133</link>
		<title>537 driver in 2.6.25.16 kernel</title>
		<category>Woof</category>
		<description>Rerwin posted this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;The kernel 2.6.25.16 version of Puppy 4.3 does not detect these modems, because the modem-rules file and firmware tarball are the incorrect versions. I obtained the appropriate versions from puppy 4.1.5. The attached dotpet applies ONLY to the k2.6.25.16 puppy installations. The two files should be added to the bugfix release 4.3.1-k2.6.25.16.&lt;/i&gt; &lt;br /&gt;&lt;br /&gt;And he posted this package:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;modem_fix_to_P430-k2.6.25.16-1.pet&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have applied this fix to the 2.6.25.16 kernel.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01132</link>
		<title>Intel 537 modem drivers fixed</title>
		<category>Woof</category>
		<description>Rerwin has fixed a major bug in the 537* drivers that caused a bit of a panic when I uploaded 4.3-final -- had to remove those modules and re-upload the 4.3 iso.&lt;br /&gt;&lt;br /&gt;He posted these packages to the forum:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;intel-537EP_secure-2.60.80.0-2.pet&lt;br /&gt;intel-537EP_secure-2.60.80.0-k2.6.30.5-intel537-2.pet&lt;br /&gt;intel-537EP_secure-2.60.80.0-k2.6.30.5-intel537EA-2.pet&lt;br /&gt;intel-537EP_secure-2.60.80.0-k2.6.30.5-intel537EP-2.pet&lt;br /&gt;intel-537EP_secure-2.60.80.0-k2.6.30.5-intel537SP-2.pet&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Which have the fixed drivers and updated firmware.&lt;br /&gt;&lt;br /&gt;Note to rerwin: I don&#39;t yet have the latest source for the 537 drivers. Could you post it so I can upload it to puppylinux.com/sources?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01131</link>
		<title>Remaster CD bug fixes</title>
		<category>Woof</category>
		<description>There was a report in the 4.3 bugs thread on the forum, of the CD remaster script crashing. I couldn&#39;t reproduce that, but I did find 3 other bugs.&lt;br /&gt;&lt;br /&gt;1. Boot logo and help missing.&lt;br /&gt;2. mksquashfs error that may have caused iso to be bigger.&lt;br /&gt;3. Hiccup in manipulating the database files in /root/.packages that may have compromised operation of the PPM.&lt;br /&gt;&lt;br /&gt;There was a request that the remaster script needs a choice where to get the Puppy files from. Currently they must be on a CD. Need to also be able to choose a mounted directory.&lt;br /&gt;However, at this stage I am being very careful, essential bugfixes only for 431.&lt;br /&gt;&lt;br /&gt;One of the bugs in 430-final was caused by an earlier beta-release bugfix. So, I need to be extremely careful.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01130</link>
		<title>Sylpheed 2.7.1</title>
		<category>Woof</category>
		<description>Prehistoric reported that Sylpheed (PET package from ibiblio, v2.4.7) crashes under certain circumstances.&lt;br /&gt;&lt;br /&gt;I have compiled the latest, version 2.7.1.&lt;br /&gt;&lt;br /&gt;This is not in the standard live-CD but will be a PET package at ibiblio.&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01129</link>
		<title>WARNING TO WINDOWS USERS</title>
		<category>Woof</category>
		<description>In the 4.3 bugs thread in the forum, there are a few reports of the files on the Puppy 4.3 live-CD being incorrectly named. Especially &quot;PUP_430.SFS&quot;.&lt;br /&gt;&lt;br /&gt;What needs to be understood is that this is not a new &quot;bug&quot;, all prior puppies have it.&lt;br /&gt;&lt;br /&gt;The reason that you are seeing the wrong filenames is because you are using MS Windows. That is, running Windows, you plug in the Puppy CD and view the files in Windows Explorer.&lt;br /&gt;&lt;br /&gt;I presume that you are doing this to copy the files for doing a frugal hard-drive install or USB Flash drive install.&lt;br /&gt;&lt;br /&gt;The Puppy live-CD ISO file (CD image) is created without Joliet extensions -- this is needed for MS Windows to read the filenames on a CD/DVD correctly. This is what causes the problem.&lt;br /&gt;&lt;br /&gt;The reason that Joliet extensions is left off is because I had experience that it breaks saving of sessions for the multisession-CD/DVD (saving sessions back to the CD/DVD, no hard-drive or other storage media required on the PC).&lt;br /&gt;&lt;br /&gt;So, the question must be raised, why are you running Windows to copy the files off the Puppy CD? You need to wean yourself off this dependence on Windows. Boot the live-CD, then you have a running Puppy!&lt;br /&gt;&lt;br /&gt;Alternatively, maybe you only have the downloaded &#39;pup-430.iso&#39; live-CD image, you have not burnt it to CD, and you are running MS Windows, and you use a Windows application (Isobuster?) to view the contents of the ISO file and copy out the files.&lt;br /&gt;Really, you &quot;should&quot; be running Puppy or some other Linux, but if you really must be running Windows to perform this operation, then copy the files and then rename them...&lt;br /&gt;&lt;br /&gt;This is how Windows sees the files:&lt;br /&gt;&lt;i&gt;BOOT.CAT BOOT.MSG HELP.MSG INITRD.GZ ISOLINUX.BIN ISOLINUX.CFG LOGO.16 PUP_430.SFS VMLINUZ ZP430305.SFS&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;For frugal install, copy the required file to the destination then rename them to:&lt;br /&gt;&lt;i&gt;initrd.gz pup-430.sfs vmlinuz zp430305.sfs&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...most important, rename PUP_430.SFS to pup-430.sfs!&lt;br /&gt;&lt;br /&gt;Note, viewing inside an ISO file when running Puppy is a piece of cake. Just click on it!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01128</link>
		<title>430: Mouse Wizard fixed</title>
		<category>Woof</category>
		<description>The Mouse Wizard showed &quot;USB mouse&quot; selected when the hardware was actually a PS/2 mouse.&lt;br /&gt;&lt;br /&gt;Puppy no longer distinguishes between the two. That is, it is now taken care of by the kernel driver.&lt;br /&gt;&lt;br /&gt;So, I have merged the radiobutton in the Wizard, now  just two radiobuttons &quot;Serial mouse&quot; and &quot;USB or PS/2 mouse (also touchpad)&quot;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01127</link>
		<title>430: PPM configure fixed</title>
		<category>Woof</category>
		<description>This is a continuation of the previous two posts, fixing the Puppy Package Manager.&lt;br /&gt;&lt;br /&gt;In the &#39;Configure&#39; section of the PPM, clicking on &#39;Update databases&#39; downloads them from ibiblio.&lt;br /&gt;&lt;br /&gt;However, the list of repositories in the Configure window grows longer. Fixed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01126</link>
		<title>430: Ensure dependencies installed</title>
		<category>Woof</category>
		<description>This is a follow-on from the previous post, debugging the Puppy Package Manager.&lt;br /&gt;&lt;br /&gt;If I choose to install Sylpheed, the first window identifies &#39;bogofilter&#39; as a dependency. There are two buttons &quot;Examine dependencies&quot; and &quot;Install sylpheed-2.4.7&quot;.&lt;br /&gt;&lt;br /&gt;What is not clear is that if the latter is clicked, it only installs Sylpheed, not any deps.&lt;br /&gt;&lt;br /&gt;I have added clarification that &quot;Examine dependencies&quot; must be clicked to install Sylpheed as well as the dependencies.&lt;br /&gt;&lt;br /&gt;Note, even if Sylpheed only is installed, the final post-install window will identify what packages are missing.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01125</link>
		<title>430: Package check dependencies broken</title>
		<category>Woof</category>
		<description>The &#39;Setup&#39; menu, item &#39;Check dependencies installed pkg&#39;, was broken.&lt;br /&gt;&lt;br /&gt;I am testing with the Sylpheed package, it has the dependency &#39;bogofilter&#39;. I installed without the dependency and found this problem.&lt;br /&gt;&lt;br /&gt;The problem also occurs in the main PPM. If I choose Sylpheed, a window identifies the dependency &#39;bogofilter&#39; is required.  I then go ahead and install Sylpheed only, but the final window states that there are no missing dependencies. This is also fixed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01124</link>
		<title>Verified Open Office SFS works</title>
		<category>Woof</category>
		<description>Ramachandran reported:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;I have downloaded the open office sfs file put it mnt/home. However, the same is not working. On clicking the SFS file it shows mounting. But nothing happens. I have tried system-boot manager.However, it showing no sfs in mnt/home ! What to do&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;There are a couple of other similar reports in the forum 431-bugs thread.&lt;br /&gt;&lt;br /&gt;I have just been through the whole exercise. A pristine 430 running from CD, downloaded Open Office 3.1.1 SFS from ibiblio, to /mnt/home.&lt;br /&gt;I chose it in the BootManager, rebooted, it works fine.&lt;br /&gt;&lt;br /&gt;It works.&lt;br /&gt;Please check the md5sum.&lt;br /&gt;Please download a SFS version 4 if running the 2.6.30.5 kernel, or SFS version 3 for older kernels.&lt;br /&gt;&lt;br /&gt;It is difficult to go wrong. If you have checked the md5sum, then the file is ok. When you run the BootManager it pops up a window telling you if any SFS files at /mnt/home are the wrong version.&lt;br /&gt;&lt;br /&gt;So, it works.&lt;br /&gt;&lt;br /&gt;Er, you do have a &quot;pupsave&quot; file and a partition mounted at /mnt/home?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01123</link>
		<title>430: Menu not update when package installed</title>
		<category>Woof</category>
		<description>Prehistoric reported:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;I just found a clue about the missing menu entries on pet packages installed in 4.3 with the latest PPM. When I installed gimp 2.4.0rc3.pet downloaded directly from ibiblio there was no menu entry. When I clicked on a local file of the same pet there was no report it was already installed, and the menu entry appeared as expected. In the previous case, where there was no menu entry for Sylpheed, I had also downloaded from ibiblio using the PPM interface. Downloading and installing by clicking on a local pet file did solve the missing menu entry problem.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Yes. The script /usr/local/petget/petget is what runs when you click on a downloaded package. When you run the Puppy Package Manager and choose a package from a repo (and a local directory can be chosen instead of a URL), then /usr/local/petget/installpreview.sh runs, not &#39;petget&#39;.&lt;br /&gt;&lt;br /&gt;Both of these have code to call the script that updates the menu, however there was a bug in &#39;installpreview.sh&#39; that prevented the menu update. Fixed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01122</link>
		<title>Release schedule for 431</title>
		<category>Woof</category>
		<description>Technosaurus is working on 4.4, however it would be nice if 431 was available, then 4.4 development could take off with that as the base.&lt;br /&gt;&lt;br /&gt;So, it is probably a good idea if I announced a release date for 431, or at least something to aim for.&lt;br /&gt;&lt;br /&gt;It really depends on how many bugs I want to fix. 431 is supposed to be a bugfix release of 430, so should not have any other changes.&lt;br /&gt;&lt;br /&gt;I was thinking of setting the release date for the 1st of November, for the reason that my satellite Internet account resets it&#39;s quota at the start of each calendar month.&lt;br /&gt;&lt;br /&gt;I&#39;m going to be testing Woof soon, and this is going to chew through my October allowance (4GB).&lt;br /&gt;&lt;br /&gt;As the so-far and anticipated bugfixes for 431 are pretty straightforward, probably only one or two pre-releases will suffice.&lt;br /&gt;&lt;br /&gt;I&#39;ll aim to get one of those out mid-October.&lt;br /&gt;&lt;br /&gt;Does that schedule seem ok? Too slow?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01121</link>
		<title>Spanish locale fix</title>
		<category>Woof</category>
		<description>Forum member myselfo reported this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;In the new locale selection screen during the bootup when no previous session is saved, there is something strange:&lt;br /&gt;&lt;br /&gt;an-ES Spain&lt;br /&gt;&lt;br /&gt;But that&#39;s not correct, the code for Spain should be es-ES... but when I try to select es-ES it appears as &quot;Mexican, Spain&quot;. Actually the language is listed as Mexican for every Spanish-language country, which is kind of funny, but wrong Smile&lt;br /&gt;It should be &quot;Spanish, Spain&quot;, &quot;Spanish, Mexico&quot;, &quot;Spanish, Chile&quot;, and so on.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I fixed the script /usr/sbin/chooselocale.&lt;br /&gt;&lt;br /&gt;But, what is the &quot;an&quot; part of &quot;an_ES&quot;?&lt;br /&gt;&lt;br /&gt;...ah, found it. The &quot;an&quot; is &quot;Aragonese&quot;, which is a minor language in Spain.&lt;br /&gt;&lt;br /&gt;I fixed a couple of others too, such as &quot;el_&quot; is &quot;Greek&quot; not &quot;Cypriotic&quot;. &quot;mk_&quot; is not &quot;Fyrom&quot;, it&#39;s &quot;Macedonian&quot; (?).&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01120</link>
		<title>HOWTO satellite videos</title>
		<category>General</category>
		<description>Coolpup sent me a link to this great site, has videos that explain all aspects of installing satellite TV:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.ehow.com/videos-on_10573_satellite-tv-installation.html target=_blank&gt;http://www.ehow.com/videos-on_10573_satellite-tv-installation.html&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01119</link>
		<title>Computer cartoons</title>
		<category>General</category>
		<description>&lt;img src=http://www.processdevelopers.com/images/PM_Build_Swing.gif /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://dilbert.com/dyn/str_strip/000000000/00000000/0000000/000000/20000/1000/100/21168/21168.strip.gif /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://www.jeffiscool.com/pictures/Foxtrot/foxtrot_bluescreenofdeath.JPG /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://dilbert.com/dyn/str_strip/000000000/00000000/0000000/000000/00000/0000/100/170/170.strip.gif /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://www.ok-cancel.com/strips/okcancel20031010.gif /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://www.bugbash.net/strips/bug-bash20050521.gif /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://geekhero.iovene.com/comics/2008-08-20-Microsoft-Word.png /&gt;&lt;br /&gt;&lt;img src=http://geekhero.iovene.com/comics/2008-08-22-Editor-wars.png /&gt;&lt;br /&gt;&lt;br /&gt;These come from here....&lt;br /&gt;&lt;a href=http://stackoverflow.com/questions/84556/whats-your-favorite-programmer-cartoon target=_blank&gt;http://stackoverflow.com/questions/84556/whats-your-favorite-programmer-cartoon&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m wasting lots of time, better get back onto Puppy bug-finding.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01118</link>
		<title>Satellite TV</title>
		<category>General</category>
		<description>I&#39;m planning to install a satellite TV system, as currently I have a terrestrial TV antenna on a high mast that can only receive one channel, ABC1, and that with (sometimes) considerable snow.&lt;br /&gt;&lt;br /&gt;Here in Australia, Optus has two satellites with free channels, C1 (has ABC1 and some commercial channels) and D1 (has ABC2) -- there is more, such as SBS and some foreign channels. They are on the ku-band.&lt;br /&gt;&lt;br /&gt;The cheapest supplier I can find in Western Australia is these guys (AU$295):&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.sciteq.com.au/store/product_info.php?cPath=26_27&amp;products_id=163 target=_blank&gt;http://www.sciteq.com.au/store/product_info.php?cPath=26_27&amp;products_id=163&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;To receive from both satellites, I need two dishes (90cm dishes cost $55 each) and a cable-coupler thingy called a &quot;DiSeqc/tone burst switch&quot;.&lt;br /&gt;&lt;br /&gt;Although these channels are &quot;free&quot;, I do have to purchase a smartcard, included in the above package, but AU$85 separately (actually, I priced all the items in the above package, and it adds up to less than the package price!).&lt;br /&gt;&lt;br /&gt;I think that I understand basically what all the parts are for -- anyway, they provide an installation guide.&lt;br /&gt;&lt;br /&gt;I&#39;ll also buy a few extras, like roof bracket mounts, cable, compass ($10), signal-finder ($15).&lt;br /&gt;&lt;br /&gt;My little house with 3 dishes on top is going to look very hi-tech!&lt;br /&gt;&lt;br /&gt;Anyone reading this who has done an installation? Any tricky things to watch out for? -- yeah, well I suppose, getting the dish pointed right at the satellite is the hardest part!&lt;br /&gt;&lt;br /&gt;Optus D1:&lt;br /&gt;&lt;img src=http://www.optus.com.au/dafiles/OCA/AboutOptus/NetworkCoverage/SharedStaticFiles/Images/img_D1series.gif /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01117</link>
		<title>4.3 Japanese edition beta1</title>
		<category>Woof</category>
		<description>Snapshot:&lt;br /&gt;&lt;img src=http://yon8844.googlepages.com/43JPb1.png /&gt;&lt;br /&gt;&lt;br /&gt;Announcement:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46704&amp;start=15 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46704&amp;start=15&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01116</link>
		<title>Tsunamis and earthquakes</title>
		<category>General</category>
		<description>There have been recent posts to this blog and the forum about the typhoon in the Philippines.&lt;br /&gt;&lt;br /&gt;Recently, like in the last few days, there have been earthquakes and a tsunami around Australia, with major damage and lost of life. The vast Australian tectonic plate is on the move. A plate in the Pacific is pushing underneath the Aussie plate, and at the other end the Aussie plate is going underneath a Eurasian continental plate. At least, that is my uneducated overview after watching the news last night.&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.kval.com/news/local/62983817.html target=_blank&gt;http://www.kval.com/news/local/62983817.html&lt;/a&gt;&lt;br /&gt;&lt;a href=http://www.watoday.com.au/world/second-major-earthquake-hits-sumatra-as-death-toll-soars-20091001-gd48.html target=_blank&gt;http://www.watoday.com.au/world/second-major-earthquake-hits-sumatra-as-death-toll-soars-20091001-gd48.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Interesting Google map:&lt;br /&gt;&lt;a href=http://www.google.com/maps/ms?ie=UTF8&amp;hl=en&amp;msa=0&amp;msid=117631292961056724014.000474d161177b2aa613d&amp;t=h&amp;ll=-20.159572,144.140625&amp;spn=45.3039,101.601562&amp;source=embed target=_blank&gt;http://www.google.com/maps/ms?ie=UTF8&amp;hl=en&amp;msa=0&amp;msid=117631292961056724014.000474d161177b2aa613d&amp;t=h&amp;ll=-20.159572,144.140625&amp;spn=45.3039,101.601562&amp;source=embed&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01115</link>
		<title>The China Study</title>
		<category>General</category>
		<description>This post is definitely in the &quot;General&quot; category, not &quot;Woof&quot;!&lt;br /&gt;&lt;br /&gt;There is a thread running in the forum about the Swine Flu vaccine, would you take it, to which I posted a response. Then while on my morning walk my mind went off into a whole lot of memories about my own and others medical experiences. Somehow I got onto thinking about diet -- well of course our wellbeing is strongly related to diet.&lt;br /&gt;&lt;br /&gt;I&#39;m a vegetarian, have been since ...um, over 33 years. I&#39;m what is known as a ovo-lacto-vegetarian, meaning I take diary products and eggs. A couple of years ago I was most surprised when my daughter became a vegan -- I had previously considered them to be the lunatic fringe.&lt;br /&gt;&lt;br /&gt;The thing is, a lot of what we take to be as &quot;fact&quot;, turns out later to be bogus. The same holds for medical professionals -- after a lifetime of experience, my opinion of them has been steadily dropping. I think that generally they are good at &quot;physical&quot; things, like cutting out a tumour or stitching up a cut. But beyond that, many of them, especially GPs, are quite ignorant.&lt;br /&gt;&lt;br /&gt;For the first year that my daughter became a vegan, she went to a doctor for regular checkups. She also had her blood checked. On one visit to get her blood test results, her blood was excellent, her general health good, but the doctor persisted in being very critical of her being a vegan. My daughter retorted &quot;In your 5 year degree you study nutrition for just 5 weeks, and you think that qualifies you to lecture to me as though you know it all!&quot; Yeah, well, the doctor wasn&#39;t happy. That&#39;s my daughter, she has turned out to be a very strong character.&lt;br /&gt;&lt;br /&gt;As is typical of the &quot;newly converted&quot;, she often prompts me to adopt veganism. Like a couple of weeks ago, I mentioned that I still eat eggs, and she responds &quot;you know what they do to the hens after they stop laying, don&#39;t you!&quot;. Sigh, yes, I can imagine.&lt;br /&gt;&lt;br /&gt;Anyway, there&#39;s a book that she got me to read, &quot;The China Study&quot;. It&#39;s about as anti-quack as you can get, very heavy reading, but I did read it right through. I still didn&#39;t become a vegan, but I found it fascinating for various reasons -- one of which is how our knowledge about medicine and diet, what we consider as &quot;fact&quot;, is highly manipulated by vested interests.&lt;br /&gt;&lt;br /&gt;The principle author was a very high-profile researcher who was in charge or co-charge of many major studies, and served on many government panels. His stories of behind-the-scenes twisting and hiding of the truth are fascinating.&lt;br /&gt;&lt;br /&gt;Personally, I don&#39;t think that you &quot;must&quot; become vegetarian or vegan. The essential thing that the book concludes is the importance of a natural &quot;whole food&quot; diet that is high in plant content, low in animal content. &lt;br /&gt;&lt;br /&gt;I think that it is one of those &quot;must read&quot; books.&lt;br /&gt;&lt;br /&gt;&lt;a href=http://en.wikipedia.org/wiki/The_China_Study target=_blank&gt;http://en.wikipedia.org/wiki/The_China_Study&lt;/a&gt;&lt;br /&gt;&lt;a href=http://www.thechinastudy.com/ target=_blank&gt;http://www.thechinastudy.com/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://www.thechinastudy.com/images/index_cover_TP.gif /&gt;&lt;br /&gt;&lt;br /&gt;Finally, for the sake of balance, there&#39;s this very critical review of &quot;The China Study&quot;:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.cholesterol-and-health.com/China-Study.html target=_blank&gt;http://www.cholesterol-and-health.com/China-Study.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...which also has a link to a response from Dr Campbell.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01114</link>
		<title>Boot and save ext4 partition fixed</title>
		<category>Woof</category>
		<description>Thanks to help from forum members piratesmack and tulindo, this is now fixed. Forum thread where they posted:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46902 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46902&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Thanks very much guys. I&#39;m very pleased when you guys get stuck in and find the solution to a problem. It sure does make things easier for me. &lt;br /&gt;&lt;br /&gt;Note to tulindo: there are two places in rc.shutdown where &quot;ext4&quot; has to be inserted.&lt;br /&gt;&lt;br /&gt;These fixes will of course be in the upcoming 431.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01113</link>
		<title>Guide for Woof</title>
		<category>Woof</category>
		<description>Forum member Iguleder has written a guide to using Woof:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47331 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47331&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I&#39;m writing a GUI for Woof, but the commandline scripts will still be there, and many users will probably continue to use them. So, the guide in its current form will remain relevant.&lt;br /&gt;&lt;br /&gt;Note, the GUI is well advanced. I intend to release Woof with GUI at the same time as 431.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01112</link>
		<title>430: Insert key crash fix</title>
		<category>Woof</category>
		<description>Thanks to pizzasgood for this, I never would have figured it out.&lt;br /&gt;&lt;br /&gt;Under certain conditions, not always, pressing the &lt;insert&gt; key while a Mozilla-based browser is running, causes it to crash. The test I did was to start PPLOG, which uses MU&#39;s web browser, start a new post and then press the &lt;insert&gt; key while the cursor is in the text-entry box -- result, crash.&lt;br /&gt;&lt;br /&gt;Pizzasgood narrowed the problem down to one library, libgdk-x11-2.0.so*, and found that the gtk+ package had to be configured with &#39;--enable-debug&#39;.&lt;br /&gt;&lt;br /&gt;I looked at what ttuuxxx did for his bug-fixed &quot;431.1&quot; build. He compiled a later version of the gtk+ package, 2.16.x and reported that it spits out error messages, although it does work.&lt;br /&gt;&lt;br /&gt;I firstly followed ttuuxxx&#39;s lead, compiled gtk+ 2.16.6 and glib 2.19.10. I compiled these with &#39;--enable-debug=no&#39;, and found still had the crash bug.&lt;br /&gt;&lt;br /&gt;Then I went back to the same gtk+ version as in 430, 2.14.7. I recompiled it with this configuration:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-pc-linux-gnu --with-xinput=yes --enable-debug=minimum&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Great, PPLOG did not crash!&lt;br /&gt;&lt;br /&gt;I have upgraded the gtk+ 2.14.7 PET package with the new library files:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;libgailutil.so.18.0.1&lt;br /&gt;libgdk_pixbuf-2.0.so.0.1400.7&lt;br /&gt;libgdk_pixbuf_xlib-2.0.so.0.1400.7&lt;br /&gt;libgdk-x11-2.0.so.0.1400.7&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I did not upgrade libgtk-x11-2.0.so.0.1400.7 as the new one is 4.5MB compared with 3.5MB before.&lt;br /&gt;&lt;br /&gt;The new PET packages are named:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;gtk+-2.14.7-1-p4.pet&lt;br /&gt;gtk+_DEV-2.14.7-1-p4.pet&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;...I&#39;ll upload them soon.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01111</link>
		<title>I&#39;m back home</title>
		<category>Woof</category>
		<description>My Royal Show job runs until Saturday, but I have experienced back problems so left. Fortunately they had someone on standby who could take my place.&lt;br /&gt;&lt;br /&gt;When I got up one morning and could hardly stand up, and couldn&#39;t bend over to put on my boots ...I knew that I had a problem!&lt;br /&gt;&lt;br /&gt;Lots to catch up on....&lt;br /&gt;&lt;br /&gt;Technosaurus has volunteered to coordinate 4.4. Wiki page, plus other guys willing to help:&lt;br /&gt;&lt;a href=http://puppylinux.org/wikka/Puppy44Team target=_blank&gt;http://puppylinux.org/wikka/Puppy44Team&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Technosaurus has been asking for suggestions for 4.4CE:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=47065 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=47065&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Technosaurus has started &quot;phase 1&quot; of testing for 4.4CE:&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46941 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46941&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Technosaurus, thanks for stepping forward to tackle this. You&#39;ll get a buzz out of it. And the experience of being the focus of lots of people clamouring for what they want in the next Puppy!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01110</link>
		<title>OpenOffice, Anjuta SFSs on ibiblio.org</title>
		<category>Woof</category>
		<description>I have uploaded Open Office 3.1.1 and Wosh&#39;s Anjuta 2.4.2 to here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/sfs4_modules-4/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/sfs4_modules-4/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The Open Office SFS has Java, and if I&#39;ve done it right the web browser Java-plugin should also be functional.&lt;br /&gt;&lt;br /&gt;I posted about Wosh&#39;s Anjuta SFS here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/blog/?viewDetailed=01109 target=_blank&gt;http://puppylinux.com/blog/?viewDetailed=01109&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Note that the &#39;devx&#39; SFS file is also required if you want to use Anjuta:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/devx_430.sfs target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/devx_430.sfs&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;These links are all to &quot;sfs4&quot; (Squashfs version 4.0) files, for use with the 2.6.30.5 kernel.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01109</link>
		<title>Anjuta IDE for 4.3</title>
		<category>Woof</category>
		<description>Great news, forum member Wosh has created an SFS for the Anjuta C/C++ IDE, specifically for Puppy 4.3. Announcement and download here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=28629&amp;start=60 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=28629&amp;start=60&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I haven&#39;t used Anjuta myself, but it sure does look good. Anjuta home:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://projects.gnome.org/anjuta/index.shtml target=_blank&gt;http://projects.gnome.org/anjuta/index.shtml&lt;/a&gt;&lt;br /&gt;&lt;a href=http://projects.gnome.org/anjuta/features.shtml target=_blank&gt;http://projects.gnome.org/anjuta/features.shtml&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Note, sometime ago there was talk about offering Vala support in Anjuta, but I don&#39;t know the current status on that.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01108</link>
		<title>PUP_430.SFS &quot;bug&quot;</title>
		<category>Woof</category>
		<description>Forum member Rickrandom reported:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;In Windows (oh the shame, I guess Puppy will look inside an ISO without burning to a CD, but I don&#39;t know how) pup-430-small.iso contains PUP_430.SFS&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Yes, shameful &lt;img src=smilies/happy.gif /&gt;&lt;br /&gt;&lt;br /&gt;The iso was created without Joliet extensions. It has been done this way for many previous versions of Puppy also. Joliet extensions causes trouble -- straining my memory but I think it caused the multisession saving to fail.&lt;br /&gt;&lt;br /&gt;You should be using Puppy. Puppy does everything.&lt;br /&gt;&lt;br /&gt;Why are you stating can&#39;t look inside an ISO? Of course you can: just click on it.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01107</link>
		<title>Developing a GUI for Woof</title>
		<category>Woof</category>
		<description>I have started writing a GUI frontend for Woof.&lt;br /&gt;&lt;br /&gt;This will take Woof to a new level of ease-of-use. One thing it should do is make it easier to add or remove packages and repositories.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01106</link>
		<title>Back home 4th Oct</title>
		<category>Woof</category>
		<description>Just to let everyone know.&lt;br /&gt;&lt;br /&gt;I can&#39;t interact much on the Internet, as away from home. Working hard on other stuff, just doing a tiny bit of Puppy stuff.&lt;br /&gt;&lt;br /&gt;I&#39;ll be home on the 4th October, will catch up with everything then, eager to get stuck into Puppy development again.&lt;br /&gt;&lt;br /&gt;Have several CD orders, will post them tomorrow.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01105</link>
		<title>Open Office, soon</title>
		<category>Woof</category>
		<description>Regarding the requests for Open Office SFS, I haven&#39;t had Internet access as away from home.&lt;br /&gt;&lt;br /&gt;I&#39;ll see if I can do it tomorrow.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01104</link>
		<title>Uevent, SFS fixes</title>
		<category>Woof</category>
		<description>I am not able to get much Internet access. Right now I&#39;m visiting one of my sisters to use her internet.&lt;br /&gt;&lt;br /&gt;I have done a little bit of work on Puppy...&lt;br /&gt;&lt;br /&gt;I already reported a problem with hardware detection with the 2.6.21.7 kernel. This is due to the way the kernel handles uevents in kernels prior to 2.6.24.&lt;br /&gt;The result is that some modules may not load, though I expect it to be ok for most people.&lt;br /&gt;Anyway, I fixed it, a simple modification to /etc/rc.d/rc.sysinit.&lt;br /&gt;&lt;br /&gt;Another problem is that the desktop icons can get messed up when SFS files are added or removed.&lt;br /&gt;This is also fixed, needed a change in /etc/rc.d/rc.update.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01103</link>
		<title>Puppy CD</title>
		<category>Woof</category>
		<description>I have created an new CD for Puppy 4.3, the one I sell for $9.&lt;br /&gt;&lt;br /&gt;It has the same as &#39;pup-430.iso&#39;, that is, all the drivers and kernel 2.6.30.5.&lt;br /&gt;It also has Woof, and the PET packages required to build Puppy using Woof.&lt;br /&gt;&lt;br /&gt;Also I managed to squeeze in the &#39;devx&#39;, the kernel source, and Open Office 3.1.1 SFS files.&lt;br /&gt;&lt;br /&gt;Total size is 695MB.&lt;br /&gt;&lt;br /&gt;There are a few orders to process, I&#39;ll post them on Monday.&lt;br /&gt;&lt;br /&gt;Oh yeah, I created an SFS 4.0 of Open Office 3.1.1, with JRE.&lt;br /&gt;I looked at ttuuxxx&#39;s OO PET package, but the JRE didn&#39;t work, so I downloaded JRE and got it to work.&lt;br /&gt;&lt;br /&gt;I will upload the Open Office SFS in a day or two.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01102</link>
		<title>pup-430-small.iso</title>
		<category>Woof</category>
		<description>There seem to be some satisfied customers using the &quot;small&quot; live-CD. If 96MB can be considered small. The full build is 105MB.&lt;br /&gt;&lt;br /&gt;The small build is supposed to hve enough drivers to satisfy &quot;95%&quot; of users. If there is some really important driver missing, that is in the full build, let me know.&lt;br /&gt;&lt;br /&gt;I don&#39;t want the small build to creep up in size though, adding less-commonly-required modules, I would rather identify more that can be taken out.&lt;br /&gt;&lt;br /&gt;So the reverse applies, if you can see a module or group of modules that you reckon 95% of users will not need, let me know.&lt;br /&gt;&lt;br /&gt;I would like to see if I can drive that 96MB even lower.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01101</link>
		<title>&#39;split-pup&#39; re-uploaded</title>
		<category>Woof</category>
		<description>I have re-uploaded the split files:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/split-pup/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/split-pup/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Ha ha, toward the end, my Internet speed got &quot;shaped&quot; to dialup speed. I have used up my monthly quota -- 2GB peak, 2GB off-peak.&lt;br /&gt;&lt;br /&gt;Interesting Skymesh&#39;s idea of dialup speed -- the upload to ibiblio was a steady 4.6KB/sec.&lt;br /&gt;&lt;br /&gt;I get my next allotment at the start of the next calendar month. No problem, I&#39;ll be working in Perth for the rest of the month. This time I&#39;m staying with a relative who doesn&#39;t even have a computer!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01100</link>
		<title>ttuuxxx&#39;s Puppy &quot;431&quot;</title>
		<category>Woof</category>
		<description>Ttuuxxx has been remarkably fast!&lt;br /&gt;&lt;br /&gt;He has already created an upgrade for 4.3:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46727 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46727&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;He has built it with Firefox instead of SeaMonkey.&lt;br /&gt;&lt;br /&gt;Note that removing SeaMonkey has a flow-on effect, rendering some apps unusable, such as PuppyBrowser.&lt;br /&gt;Ttuuxx has posted a patch that is supposed to fix that.&lt;br /&gt;&lt;br /&gt;I haven&#39;t tried it. It&#39;s 2.30am here, I&#39;m going back to bed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01099</link>
		<title>Kernel PET re-uploaded</title>
		<category>Woof</category>
		<description>For you guys who are playing with Woof, I have re-uploaded the 2.6.30.5 PET package:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-woof/linux_kernel-2.6.30.5-tickless_smp-5-p4.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-woof/linux_kernel-2.6.30.5-tickless_smp-5-p4.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I left the package name the same, so that Woof itself does not have to be changed. Just download this latest and replace the previous one.&lt;br /&gt;&lt;br /&gt;The only difference is the Intel 537 modules are removed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01098</link>
		<title>pup-430.iso re-uploaded</title>
		<category>Woof</category>
		<description>Here I am, out of bed at 1.15am again.&lt;br /&gt;&lt;br /&gt;&#39;pup-430.iso&#39; has finished uploading.&lt;br /&gt;&lt;br /&gt;I decided a new strategy is needed for uploading, so I named the file pup-430.isoTEMP then uploaded it, then named it back.&lt;br /&gt;&lt;br /&gt;Yeah Sage, the iso is now 105.1MB. That&#39;s how big the 537 modules were -- added 5MB onto the iso!&lt;br /&gt;&lt;br /&gt;I&#39;m currently re-uploading the split files, and haven&#39;t yet checked the md5sum of &#39;pup-430.iso&#39;. It should be:&lt;br /&gt;&lt;br /&gt;e18650d38c4185a4b70778026c305e98&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01097</link>
		<title>depmod has gone mad</title>
		<category>Woof</category>
		<description>Puppy 4.3 is using the Busybox &#39;depmod&#39; applet because the full depmod uses too many resources.&lt;br /&gt;&lt;br /&gt;However, the ALSA Sound Wizard needs the full depmod to work. Note, the full version is named &#39;depmod-FULL&#39;.&lt;br /&gt;&lt;br /&gt;But, depmod-FULL has gone crazy. It worked right up until a day or to ago. I modified the script /usr/sbin/alsaconf to run the full depmod, tested it, all was fine.&lt;br /&gt;&lt;br /&gt;I have no idea why it has gone crazy. What it does is create /lib/modules/2.6.30.5/modules.pcimap.temp that just keeps growing bigger and bigger until there is no memory left.&lt;br /&gt;&lt;br /&gt;Hmmm, looks like we will need a service pack to fix this one.&lt;br /&gt;&lt;br /&gt;Anyone want to have a go at compiling the latest module-init-tools package, see if they have fixed this problem?&lt;br /&gt;&lt;br /&gt;Though, what the cause is, has me stumped. I wonder if one of the 3rd-party modules is causing the problem?&lt;br /&gt;&lt;br /&gt;EDIT:&lt;br /&gt;I had tested the ALSA Wizard very soon before releasing the final, so I thought hard, what changed before then and the final? ...ah, one thing, I put rerwin&#39;s 537 modem modules in. That&#39;s it, take them out and depmod-FULL works.&lt;br /&gt;&lt;br /&gt;You will find them at /lib/modules/2.6.30.5/intelmodem&lt;br /&gt;&lt;br /&gt;This bug does not affect pup-430-small.iso, only the full size pup-430.iso.&lt;br /&gt;I&#39;m going to rebuild and re-upload it, without the 537 modules.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01096</link>
		<title>Puppy Linux version 4.3 released</title>
		<category>Woof</category>
		<description>Please note that the files have not yet fully propagated from ibiblio.org to the mirrors. For example, I just now checked &#39;nluug.nl&#39; and it has an incomplete &#39;pup-430.iso&#39; file. So, for now only download from ibiblio:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Announcement and release notes:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/download/release-4.3.htm target=_blank&gt;http://puppylinux.com/download/release-4.3.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;There are a selection of live-CD ISO files and support files to choose from. Please read this page before going to the download page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/readme-files.htm target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/readme-files.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Main download page, has links to ibiblio.org and download mirrors:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/download/index.html target=_blank&gt;http://puppylinux.com/download/index.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;A thread has been created on the Puppy Linux forum for bug reports and suggestions:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46594 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46594&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01095</link>
		<title>4.3: not there yet</title>
		<category>Woof</category>
		<description>Still uploading. Right now it&#39;s 1.30am, I have just got up and recommenced uploading.&lt;br /&gt;&lt;br /&gt;My satellite connection died at 9.30pm so I went to bed.&lt;br /&gt;&lt;br /&gt;That&#39;s the downside of satellite Internet, very unreliable. At least, that has been my experience.&lt;br /&gt;&lt;br /&gt;It was the same story with my previous satellite provider. With the previous provider, the sync with the satellite would drop out frequently.&lt;br /&gt;With my current provider there appears to still be a connction with the satellite, judging from the lights on the satellite-modem, but nothing happens.&lt;br /&gt;&lt;br /&gt;When &quot;nothing happens&quot;, and I&#39;m using gFTP to do a transfer, gFTP just sits there indefinitely, never times out, nothing, just waits. I find it best to just power off and try again later.&lt;br /&gt;&lt;br /&gt;Anyway, here we are at 1.36am and it&#39;s working.&lt;br /&gt;&lt;br /&gt;I got a warning from my provider that my quota is just about used up -- then I get shaped to dialup speed. But, I think there&#39;s a bit more available on the off-peak quota, which is what I&#39;m using now.&lt;br /&gt;&lt;br /&gt;Enough rambling.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01094</link>
		<title>Uevent bug in old kernel</title>
		<category>Woof</category>
		<description>Ah, I have found a bug running 4.3 with the old 2.6.21.7 kernel. I won&#39;t let it hold up the release of 4.3 though.&lt;br /&gt;&lt;br /&gt;In /tmp/bootsysinit.log there are several lines like this:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;grep: /sys/bus/usb/devices/usb5/uevent: Permission denied&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;This is due to how I read the modaliases in /etc/rc.d/rc.sysinit. The 2.6.30.5 kernel allows &#39;uevent&#39; files to be read and the MODALIAS variable extracted from them. I don&#39;t know what kernel version that came in, but 2.6.21.7 doesn&#39;t support it. &lt;br /&gt;&lt;br /&gt;With the 2.6.21.7 kernel there are actual &#39;modalias&#39; file in /sys that have to be read.&lt;br /&gt;&lt;br /&gt;rc.sysinit loads modules in two stages, and it is the second stage that is now failing. This means that some modules might not load. There are not too many cases that are caught by this secondary loading step, maybe some PCMCIA interfaces and some less-usual USB interfaces.&lt;br /&gt;&lt;br /&gt;So it&#39;s not a critical thing, and I can easily provide a patched rc.sysinit soon to fix it. It needs a kernel-version test, with code to do it the &quot;old way&quot;.&lt;br /&gt;&lt;br /&gt;Probably those who want to run 4.3 with this old kernel will discover more things, and we can easily provide a &quot;service pack&quot; prior to 4.3.1.&lt;br /&gt;&lt;br /&gt;But, I must emphasize that the bug will only affect a limited range of hardware. I rebooted my PC, with a savefile, it came up, everything still working, all modules loaded.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01093</link>
		<title>4.3 with 2.6.21.7 kernel</title>
		<category>Woof</category>
		<description>Amazing! I&#39;m posting right from Puppy 4.3 built with the old 2.6.21.7 kernel.&lt;br /&gt;&lt;br /&gt;This kernel is about two years old. It was used back in Puppy 3.x and also retro 4.1x and 4.2x builds.&lt;br /&gt;&lt;br /&gt;The thing is, I just built the Puppy live-CD with exactly the same packages as the main 4.3 build with 2.6.30.5 kernel. Some packages are supposed to be kernel-version sensitive. The kernel ALSA drivers are much older than the alsa-lib and alsa-utils packages.&lt;br /&gt;&lt;br /&gt;But, everything works. I&#39;m online using it right now, via wireless with Ndiswrapper.&lt;br /&gt;&lt;br /&gt;I even had a bit of a pleasant surprise with the acx_pci driver. This PC has a Netgear WG311 wireless card, but I never was able to get the acx_pci driver to work with it. Now, it connects, DHCP works, but there is still a problem, /var/log/messages reports frame sizes to big.&lt;br /&gt;&lt;br /&gt;There&#39;s probably an upgraded driver that would fix that, but I used Ndiswrapper and that works fine.&lt;br /&gt;&lt;br /&gt;I also tested dialup on my other PC with Pctel 789 modem, that works too.&lt;br /&gt;&lt;br /&gt;Media players work, everything works...&lt;br /&gt;&lt;br /&gt;Oh, some news, 4.3 is going to be available with 2.6.30.5, 2.6.25.16 and 2.6.21.7 kernels.&lt;br /&gt;They are uploading now, but you will have to wait several more hours due to ibiblio.org low transfer speed.&lt;br /&gt;&lt;br /&gt;I&#39;ll announce when everything&#39;s ready.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01092</link>
		<title>Network Wizard upgrade</title>
		<category>Woof</category>
		<description>Tempestuous provided updated and new firmware for the 2.6.30.5 kernel, then discovered that the Network Wizard also needs to be upgraded.&lt;br /&gt;&lt;br /&gt;4.3beta3 has Dougal&#39;s Network Wizard dated 4th April 2009. I have inserted the following line into /usr/sbin/wag-profiles.sh, at line 322:&lt;br /&gt;&lt;br /&gt;	 ar9170usb|at76c50x-usb|libertas_cs|libertas_sdio|libertas_tf_usb|mwl8k|usb8xxx) CARD_WPA_DRV=&quot;wext&quot; ;; #v430&lt;br /&gt;&lt;br /&gt;I have named the upgraded Wizard as &#39;net_setup-20090916.pet&#39;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01091</link>
		<title>MSDOS expert required</title>
		<category>Woof</category>
		<description>It&#39;s too long ago, I can&#39;t remember...&lt;br /&gt;&lt;br /&gt;When 4.3 is released, I will be uploading it in pieces, to make it easy for those on dialup.&lt;br /&gt;&lt;br /&gt;So, pup-430.iso will be split into xaa, xab, xac, xad, xae, etc.&lt;br /&gt;&lt;br /&gt;After downloading, if running Linux it is easy to put them together:&lt;br /&gt;&lt;br /&gt;# cat x* &gt; pup-430.iso&lt;br /&gt;&lt;br /&gt;However, does anyone know the equivalent to that in a Windows DOS-box?&lt;br /&gt;&lt;br /&gt;Um, I presume that you can still open a DOS-box in Windows? Perhaps the average Windows user would need instructions how to do that, open it wherever they have downloaded the files?&lt;br /&gt;&lt;br /&gt;I&#39;ll provide the pieces on ibiblio, and a readme that tells how to assemble them.&lt;br /&gt;&lt;br /&gt;Of course, in the future they will be able to use our Xdelta file difference manager.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01090</link>
		<title>Dialup works!</title>
		<category>Woof</category>
		<description>I&#39;m doing a series of basic sanity checks on 4.3.&lt;br /&gt;&lt;br /&gt;I went through the exercise of a frugal install, then tested dialup -- yes, working!&lt;br /&gt;&lt;br /&gt;The modem in this PC has a PcTel 789 chipset, so it&#39;s a software modem. Piece of cake to run PupDial and connect.&lt;br /&gt;&lt;br /&gt;I have signed up for a full year with Netbay Internet, the people who provide my dialup.&lt;br /&gt;Although I have satellite broadband, my dialup account is a backup and also I need it for testing purposes.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01089</link>
		<title>Universal Installer bugfix</title>
		<category>Woof</category>
		<description>I did a full hd install of 4.3 and encountered a bug. The desktop came up with mostly the Rox default icons, not the current theme icons.&lt;br /&gt;&lt;br /&gt;The particular circumstance that caused this was I previously had 430 installed on the partition but chose to wipe when testing the latest pup. The installer runs /etc/rc.d/rc.update in the newly installed partition, and it is supposed to perform some actions based on it being a version upgrade -- however the installer had already recorded that version 430 was in the partition so did not know that upgrade actions were required.&lt;br /&gt;&lt;br /&gt;Well, anyway, the end result was that rc.update did not run the code that installs the icon theme into /usr/local/lib/X11/pixmaps.&lt;br /&gt;&lt;br /&gt;Fixed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01088</link>
		<title>4.3 frozen</title>
		<category>Woof</category>
		<description>Consider 4.3 to now be &quot;frozen&quot;. I&#39;m going to do a build then test as thoroughly as possible for a day or two.&lt;br /&gt;&lt;br /&gt;There are a few things that I would have liked to put in, but will consider them for 4.3.1. For example:&lt;br /&gt;&lt;br /&gt;USB floppy formating (8-bit)&lt;br /&gt;Woo-FF video file converter (trio)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01087</link>
		<title>Updated firmware for 2.6.30.5</title>
		<category>Woof</category>
		<description>Thanks to tempestuous for finding the latest firmware for wireless drivers in the 2.6.30.5 kernel.&lt;br /&gt;&lt;br /&gt;I have upgraded the 2.6.30.5 package with these.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01086</link>
		<title>NicoEdit 2.3</title>
		<category>Woof</category>
		<description>Nicolas has done it again.&lt;br /&gt;&lt;br /&gt;This remarkable little text editor now remembers the previous scroll position in a file and the cursor position. So, in the History menu you can flip back through files and they all come up in the same place at which you last had them open.&lt;br /&gt;&lt;br /&gt;This is great, makes NicoEdit just as good as, perhaps even better, than an editor with tabs.&lt;br /&gt;Better perhaps, as you can have a large number of files in the history menu, whereas the tabbed interface gets cumbersome when you have too many to fit in the width of the window.&lt;br /&gt;&lt;br /&gt;Anyway, as I am now at the 12th hour for 4.3, I have left Geany in also. We do need to use NicoEdit for awhile, build up confidence in it, maybe fix any outstanding bugs, and maybe consider NicoEdit as the sole GUI text editor for 4.3.1.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01085</link>
		<title>GTK Polished Blue theme tweaked</title>
		<category>Woof</category>
		<description>The guys were discussing on the forum that it is difficult to determine which tab is active in SeaMonkey, as the active tab is lighter grey, the reverse of what is expected in some other themes.&lt;br /&gt;&lt;br /&gt;I responded that we could look into tweaking the theme for pup 4.3.1, but afterward I thought why not do it now.&lt;br /&gt;&lt;br /&gt;So I have. I have made the active tab a light 3D blue, to match the other blue highlighting in the GTK theme and in JWM.&lt;br /&gt;It looks nice and it is now crystal clear which tab is selected.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01084</link>
		<title>Ayttm 0.6.0</title>
		<category>Woof</category>
		<description>I have been using snapshots from CVS for awhile, the most recent was 0.5.0-146. There were some small changes made since then and the new official release is now version 0.6.0. So, I have upgraded.&lt;br /&gt;&lt;br /&gt;A note while I think of it... technosaurus has brought out a PET package of 0.6.0 but I think it is rather large. I don&#39;t know why, mine is 806KB, with all the modules. I mention this as it is something for technosaurus to look into why that is so... maybe an extra pkg bundled with it?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01083</link>
		<title>puppyPDF fixed</title>
		<category>Woof</category>
		<description>See the &#39;Document&#39; menu. This was created in 2007 by forum member thoughtjourney, and hasn&#39;t been changed since.&lt;br /&gt;&lt;br /&gt;Until now, that is. Forum member nikin has fixed a couple of bugs:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;I tryed to use puppypdf today and it had 2 showstopping bugs.&lt;br /&gt;First: the dialogs where communicating on stderr, so they catched the GTK errors. messing up fselect boxe&#39;s filenames.&lt;br /&gt;&lt;br /&gt;Modified them to use --stdout and 2&gt;/dev/null&lt;br /&gt;&lt;br /&gt;The other one was a misuse of abiword.&lt;br /&gt;not working:&lt;br /&gt;&lt;br /&gt;Code:&lt;br /&gt;abiword --print=temp input&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;i updated it to work with abiword 2.6&lt;br /&gt;&lt;br /&gt;like:&lt;br /&gt;Code:&lt;br /&gt;&lt;br /&gt;abiword --to=ps --to-name=temp input&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;this version now converted my html file to pdf&lt;br /&gt;Any suggestions are welcome.&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01082</link>
		<title>&#39;zdrv&#39; bugfix</title>
		<category>Woof</category>
		<description>4.3beta3 has a &#39;zdrv&#39; of extra modem drivers.&lt;br /&gt;&lt;br /&gt;When this is placed at /mnt/home, it loads automatically and &#39;depmod&#39; runs so that the modules will be recognised. Ditto when the zdrv is removed.&lt;br /&gt;&lt;br /&gt;At least it is supposed to. I found that &#39;depmod&#39; did not run. Fixed, I think, still need to do a build to verify.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01081</link>
		<title>mhWaveEdit 1.4.16</title>
		<category>Woof</category>
		<description>4.3beta3 testers are invited to test the latest mhWaveEdit:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/mhwaveedit-1.4.16-1-p4.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/mhwaveedit-1.4.16-1-p4.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;And Zmixer, see my previous post.&lt;br /&gt;&lt;br /&gt;In particular, are you able to record with mhWaveEdit? Lobster likes to record stuff, so it&#39;s a pity that recording does not seem seem to work on his hardware with ALSA 1.0.20 -- I hope that is not the common experience!&lt;br /&gt;&lt;br /&gt;The 4.3beta3 forum feedback thread has some reports of audio problems, so we will probably need to upgrade the ALSA drivers for Puppy 4.4.&lt;br /&gt;Probably stay with the same kernel version perhaps, Rerwin (and myself to a much lesser extent) has been through a long process of getting 3rd party drivers to compile with it.&lt;br /&gt;Moving up to the latest in the 2.6.30.x series would be a reasonable thing to do. But then, you have to consider that there may be other 3rd party drivers compiled for 2.6.30.5, maybe by tempestuous, so there would be a big investment in staying with 2.6.30.5.&lt;br /&gt;...but, this is a decision that the 4.4 coordinator would have to make.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01080</link>
		<title>Zmixer</title>
		<category>Woof</category>
		<description>It is approaching the 12th hour and I should not be adding any more packages, but I think that I will add zmixer.&lt;br /&gt;&lt;br /&gt;AlsaMixer is a console ncurses application that is not to eveyone&#39;s liking, whereas Zmixer is a GTK2 app. I will have both in 4.3.&lt;br /&gt;&lt;br /&gt;4.3beta3 testers, those with working sound, are invited to test Zmixer:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/zmixer-0.2.1.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/zmixer-0.2.1.pet&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01079</link>
		<title>Sweep vs mhWaveEdit</title>
		<category>Woof</category>
		<description>Charlie6 asked the question, how to record in mhWaveEdit.&lt;br /&gt;&lt;br /&gt;I have taken a quick look, it doesn&#39;t seem very intuitive or flexible.&lt;br /&gt;&lt;br /&gt;Maybe I should change to mhWaveEdit?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01078</link>
		<title>Nathan Wallpaper Setter fix</title>
		<category>Woof</category>
		<description>The &#39;View&#39; button was broken. Thanks to 01micko who found the cause of the bug.&lt;br /&gt;&lt;br /&gt;I changed it to &#39;defaultimageviewer&#39;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01077</link>
		<title>pupX fixed</title>
		<category>Woof</category>
		<description>Thanks to DaveS who advised that the &#39;-dpms&#39; parameter is required, I have fixed pupX. The bug reported was that disabling the screensaver did not work.&lt;br /&gt;&lt;br /&gt;This fix is also required in /usr/bin/gxineshell, a wrapper script for Gxine, that turns of screensaving while a video is playing.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01076</link>
		<title>PupDial, ESS modem driver</title>
		<category>Woof</category>
		<description>Rerwin posted an upgrade for PupDial and a driver for ESS modem chipsets, which just missed out on getting into 4.3beta3.&lt;br /&gt;&lt;br /&gt;I have now put them in.&lt;br /&gt;&lt;br /&gt;The inclusion of ESS makes pup 4.3 with 2.6.30.5 kernel the most complete selection of analog modem drivers that we have ever had.&lt;br /&gt;&lt;br /&gt;The only slight inconvenience is that they are in a separate &#39;zdrv&#39; (due to their size), that the user will have to download and place at /mnt/home.&lt;br /&gt;On the plus side though, a &#39;zdrv&#39; is loaded automatically and does not have to be selected in the BootManager.&lt;br /&gt;&lt;br /&gt;I have documented the extra modem drivers &#39;zdrv&#39; in the 4.3 announcement page, with a list of what modem chipsets are likely to need it.&lt;br /&gt;&lt;br /&gt;There are some software-modem drivers that have remained builtin to the live-CD iso file, such as Lucent and Smartlink.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01075</link>
		<title>NicoEdit 2.1</title>
		<category>Woof</category>
		<description>I announced NicoEdit 2.0 here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/blog/?viewDetailed=01049 target=_blank&gt;http://puppylinux.com/blog/?viewDetailed=01049&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;But I later went back to Geany, plus NicoEdit 1.6 as the secondary &quot;Leafpad replacement&quot;, as 2.0 has some bugs.&lt;br /&gt;&lt;br /&gt;Nicolas has fixed the bugs in 2.0, and once again I am making NicoEdit the flagship text editor for 4.3.&lt;br /&gt;&lt;br /&gt;I have done some limited testing, it looks good. As I already mentioned, it is tiny -- the PET package is 40KB. Even with gtksourceview, the combined size is one third of Geany.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01074</link>
		<title>USB Flash boot fail if &quot;pkeys=de&quot;</title>
		<category>Woof</category>
		<description>It has been reported that booting from a USB Flash drive with &quot;pkeys=de&quot; the boot failed. Without the pkeys parameter it works.&lt;br /&gt;&lt;br /&gt;I found the problem. This is the fixed code in the &#39;init&#39; script:&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;  vfat) #w476&lt;br /&gt;   ####TODO#### need to get rid of the old 2-letter keyboard layout, so PKEYS boot&lt;br /&gt;   # param works for the main kbd layouts.&lt;br /&gt;   #would like to introduce codepage and iocharset, maybe as kernel params...&lt;br /&gt;   #ex: codepage=850 iocharset=iso8859-2 ...no, already have &#39;pkeys&#39;&lt;br /&gt;   OUT_PARAM=&#39;shortname=mixed,quiet&#39;&lt;br /&gt;   [ &quot;$MNT_O&quot; ] &amp;&amp; OUT_PARAM=&quot;${OUT_PARAM},${MNT_O}&quot;&lt;br /&gt;   if [ &quot;$PKEYS&quot; ];then&lt;br /&gt;    case $PKEYS in&lt;br /&gt;     de|be|br|dk|es|fi|fr|it|no|se|pt)&lt;br /&gt;      modprobe nls_cp850 #v426&lt;br /&gt;      OUT_PARAM=&quot;$OUT_PARAM&quot;&#39;,codepage=850&#39;&lt;br /&gt;     ;;&lt;br /&gt;	 slovene|croat|hu101|hu|cz-lat2|pl|ro_win)&lt;br /&gt;	  modprobe nls_cp852 #v426&lt;br /&gt;	  modprobe nls_iso8859-2 #v426&lt;br /&gt;	  OUT_PARAM=&quot;$OUT_PARAM&quot;&#39;,codepage=852,iocharset=iso8859-2&#39;&lt;br /&gt;	 ;;&lt;br /&gt;    esac&lt;br /&gt;   fi&lt;br /&gt;   mount -t $MNT_T -o $OUT_PARAM $MNT_DEV $MNT_DIR&lt;br /&gt;  ;;&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;...you can see where I have inserted explicit modprobe commands. Those modules should have loaded automatically, I don&#39;t know why they don&#39;t.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01073</link>
		<title>425: testing USB Flash booting</title>
		<category>Woof</category>
		<description>One or two people reported difficulty booting from USB Flash, for 4.3beta1/2.&lt;br /&gt;&lt;br /&gt;I used the Universal Installer, installed to 1GB Kingston DataTraveler drive with vfat partition. Works. Then installed to a 2GB DataTraveler with ext2 partition. Works also.&lt;br /&gt;&lt;br /&gt;I ran the BootFlash program and chose the default &#39;USB-HDD&#39; install option. Installed to the 1GB DataTraveler. The BootFlash utility reformats the drive with a vfat partition. Works.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01072</link>
		<title>Puppy 4.3beta3</title>
		<category>Woof</category>
		<description>Close enough -- at the time of posting this, the woof tarball and the delta files are still uploading.&lt;br /&gt;&lt;br /&gt;Puppy 4.3beta3 (425) now available, get it from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.3beta3/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.3beta3/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Of course you will also be able to download from the ibiblio mirrors. MU is also hosting 4.3beta3:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppyisos.org/isos/Puppylinux-official/4.3beta3/ target=_blank&gt;http://puppyisos.org/isos/Puppylinux-official/4.3beta3/&lt;/a&gt; (User: puppy Passwd: linux)&lt;br /&gt;&lt;br /&gt;I have updated the announcement and release notes page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/download/release-4.3.htm target=_blank&gt;http://puppylinux.com/download/release-4.3.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The default theme:&lt;br /&gt;&lt;br /&gt;GTK: Polished Blue (?)&lt;br /&gt;Icons: Blue Moon (ttuuxxx)&lt;br /&gt;JWM: Gradient-blueish (me)&lt;br /&gt;Background: Summer Clouds (author unknown)&lt;br /&gt;&lt;br /&gt;Note, the GTK Polished Blue theme is GPL and was hosted on freshmeat.net, but it has been removed and does not seem to be available online anymore. But, we do have it as a PET package.&lt;br /&gt;&lt;br /&gt;If anyone would like to tweak the themes, go for it. It seems reasonably ok as the theme for the final, what do you think? I don&#39;t think it&#39;s brilliant, just pleasant, though the mix of different blues may seem a bit odd.&lt;br /&gt;I was thinking though, that we could do something to the Summer Clouds background -- what about integrating the Puppy logo into the cloud? No, not Superpup, although that is tempting! -- but we decided to be more serious for the final.&lt;br /&gt;Anyone want to have a go at that? Here is the Summer Clouds image:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.3beta3/summer_clouds.jpg /&gt;&lt;br /&gt;&lt;br /&gt;It&#39;s 141KB as it was saved at quality-factor 95, but in Puppy I saved it at 85, which reduced its size to 63KB and it still looks the same.&lt;br /&gt;&lt;br /&gt;Forum thread for feedback on 4.3beta3:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46502 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46502&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01071</link>
		<title>4.3final by Saturday 19th Sept.</title>
		<category>Woof</category>
		<description>I intend to have 4.3 final out by the end of the week.&lt;br /&gt;&lt;br /&gt;After that, I am having a break for a couple of weeks, not really a break but doing something completely different.&lt;br /&gt;I confess, I&#39;m getting a bit burnt-out, need a change.&lt;br /&gt;&lt;br /&gt;So guys, when beta3 becomes available, test it and I&#39;ll put in a good effort at fixing anything that needs fixing before the final.&lt;br /&gt;&lt;br /&gt;The emphasis is now on fixing important bugs only. No upgrades unless absolutely essential.&lt;br /&gt;There will of course be small bugs that can be held over for a later version.&lt;br /&gt;&lt;br /&gt;Um yes, after 4.3 is released, we have to discuss who will coordinate 4.4. I would prefer to get back onto Woof core development and some other things. I was wondering, perhaps our old &quot;community edition&quot; model should be looked at again.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01070</link>
		<title>4.3beta3 is uploading</title>
		<category>Woof</category>
		<description>It&#39;s uploading to ibiblio.org right now, but they throttle transfers, so it is steady at 10.5KB/sec -- estimated completion time is 10 hours from now!&lt;br /&gt;&lt;br /&gt;I&#39;ll announce it when done.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01069</link>
		<title>NicoEdit 2.0 bugs</title>
		<category>Woof</category>
		<description>I earlier announced that I had replaced Geany by NicoEdit 2.0, however I have to reverse that.&lt;br /&gt;&lt;br /&gt;I found two showstopper bugs in NicoEdit 2.0:&lt;br /&gt;&lt;br /&gt;1. No syntax highlighting for Genie code.&lt;br /&gt;2. No synax highlighting at all if a file is opened from the commandline.&lt;br /&gt;&lt;br /&gt;That second one I discovered when right-clicked on a file in Rox and chose &quot;Open in text editor&quot;.&lt;br /&gt;&lt;br /&gt;I am sure that Nicolas will fix them, but as 4.3beta3 is immenent I have rolled back to Geany and NicoEdit 1.6 -- the latter is a simpler version of NicoEdit that is our Leafpad-replacement.&lt;br /&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01068</link>
		<title>ExpenseTracker removed</title>
		<category>Woof</category>
		<description>I have taken out ExpenseTracker from 4.3, as it needs work.&lt;br /&gt;&lt;br /&gt;I took a look at it as it was reported that it crashes for any locale other than en_US.&lt;br /&gt;&lt;br /&gt;I noticed that it displays currency as &quot;Rs.&quot; (Rupees). I fixed that, but then I noticed that an amount I entered as &quot;555.46&quot; got rolled up and displayed as &quot;555.5&quot; -- yuck, although it does store the correct value in the database.&lt;br /&gt;&lt;br /&gt;That could be fixed too, but I don&#39;t have the time right now.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01067</link>
		<title>Aqualung crashes</title>
		<category>Woof</category>
		<description>It was reported that if the &quot;Enable statusbar&quot; checkbox is unticked in the Music Store, in the Setup, then Aqualung crashes. Yes, I have confirmed that.&lt;br /&gt;&lt;br /&gt;If someone feels like testing their latest unreleased snapshot, please do. If the bug is still there, if you feel like reporting it, please do!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01066</link>
		<title>Universal Installer: SCSI</title>
		<category>Woof</category>
		<description>I have enabled the menu choice to install to SCSI hard drive in the Puppy Universal Installer.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01065</link>
		<title>ALSA Wizard fixed</title>
		<category>Woof</category>
		<description>It was reported that the ALSA sound Wizard does not work in 4.3beta2.&lt;br /&gt;&lt;br /&gt;Yes, this is because of the move from the full &#39;depmod&#39; to the Busybox &#39;depmod&#39; applet.&lt;br /&gt;&lt;br /&gt;I have modified /usr/sbin/alsaconf so that it runs the full depmod (/sbin/depmod-FULL), with a warning displayed that it may hang on low-RAM systems.&lt;br /&gt;&lt;br /&gt;The low-RAM problem is relieved once a swap file/partition is created, so is likely only to be a problem on the first boot, on a 64MB (or less) system.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01064</link>
		<title>iwlwifi firmware</title>
		<category>Woof</category>
		<description>Forum member lluamco reported that later firmware is needed for the iwlwifi wireless driver for the 2.6.30.5 kernel.&lt;br /&gt;&lt;br /&gt;It is /usr/lib/firmware/iwlwifi-4965-2.ucode&lt;br /&gt;&lt;br /&gt;I have put this into the firmware tarball, also left in the older firmware.&lt;br /&gt;&lt;br /&gt;I have modified /etc/modules/firmware.dep.2.6.30.5, added &quot;iwlagn.ko&quot; onto this line:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;iwlwifi:iwl3945.ko,iwl4965.ko,iwlagn.ko&lt;/i&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01063</link>
		<title>PupScan fixed</title>
		<category>Woof</category>
		<description>Puppy 4.3beta is using Busybox &#39;depmod&#39;, for reasons discussed recently in this blog. However, it compromises the operation of PupScan (see System menu). Rerwin has fixed that. Extract of his forum post:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;Now that the modules.*map files are no longer maintained in /lib/modules/&lt;kernel&gt;/, pupscan no longer displays the modules associated with hardware devices. I have updated it to obtain its information from the modules.alias file and added use of the dialup-modem rules file (for devices not listed in modules.alias).&lt;br /&gt;&lt;br /&gt;I also changed it to choose that last-found module instead of the first, to match how pup_event_backend_modprobe makes its choice.&lt;br /&gt;&lt;br /&gt;At some point, I hope to refine it so that it accounts for &quot;pci overrides&quot; and &quot;preferred modules&quot; specified in the BootManager. But this is already a little more comprehensive than when it was last working.&lt;br /&gt;&lt;br /&gt;UPDATE 9/10/09: Turns out using the modaliases is trickier than I anticipated. I have made further refinements to pupscan (as -2), but more can be done. I may continue refinement, but please (Barry) take whatever version is here at the deadline for the next beta. Thanks,&lt;br /&gt;Richard&lt;/i&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01062</link>
		<title>Pstreamvid channels</title>
		<category>Woof</category>
		<description>In 4.3beta2, The BBC channel has audio but no video, Fox11 has neither, and NASA has audio but no video.&lt;br /&gt;&lt;br /&gt;Probably fixable by installing Mplayer or more codecs for Gxine (or an updated xine-lib), however, I want people&#39;s first experience when using 4.3 for all the video channels to work.&lt;br /&gt;&lt;br /&gt;Therefore I have removed BBC, Fox11 and NASA, and added SFGTV2 and SCCtv.&lt;br /&gt;&lt;br /&gt;A great place to find out what&#39;s out there:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://watch.squidtv.net/ target=_blank&gt;http://watch.squidtv.net/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01061</link>
		<title>Ayttm 0.5.0-146</title>
		<category>Woof</category>
		<description>I have upgraded to the latest from CVS.&lt;br /&gt;&lt;br /&gt;ChangeLog:&lt;br /&gt;&lt;a href=http://ayttm.cvs.sourceforge.net/viewvc/ayttm/ayttm/ChangeLog?view=log target=_blank&gt;http://ayttm.cvs.sourceforge.net/viewvc/ayttm/ayttm/ChangeLog?view=log&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01060</link>
		<title>SeaMonkey 1.1.18</title>
		<category>Woof</category>
		<description>I have upgraded to the latest version.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01059</link>
		<title>JWM theme changing works</title>
		<category>Woof</category>
		<description>There was a report that running JWM Config to change theme caused /root/.jwmrc-tray to get deleted, without any backup.&lt;br /&gt;&lt;br /&gt;I&#39;m sorry, but it works fine for me. And there is a backup created.&lt;br /&gt;&lt;br /&gt;If you do experience a problem, then you need to document the exact steps, and make sure it is reproducable.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01058</link>
		<title>Gtkdialog question</title>
		<category>Woof</category>
		<description>In the PPM there is a Find box with a Go button beside it. There is a request that pressing ENTER in the Find box should initiate the search.&lt;br /&gt;&lt;br /&gt;However, if I put &lt;action&gt; tags within the &lt;enter&gt;, they run everytime a character is typed:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;   &lt;text&gt;&lt;label&gt;Find:&lt;/label&gt;&lt;/text&gt;&lt;br /&gt;   &lt;entry&gt;&lt;br /&gt;    &lt;variable&gt;ENTRY1&lt;/variable&gt;&lt;br /&gt;    &lt;action&gt;/usr/local/petget/findnames.sh&lt;/action&gt;&lt;br /&gt;    &lt;action&gt;refresh:TREE1&lt;/action&gt;&lt;br /&gt;   &lt;/entry&gt;&lt;br /&gt;   &lt;button&gt;&lt;br /&gt;    &lt;label&gt;Go&lt;/label&gt;&lt;br /&gt;    &lt;action&gt;/usr/local/petget/findnames.sh&lt;/action&gt;&lt;br /&gt;    &lt;action&gt;refresh:TREE1&lt;/action&gt;&lt;br /&gt;   &lt;/button&gt;&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;Does anyone know how to set it so that the actions only run when the ENTER key is pressed?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01057</link>
		<title>e2fsprogs 1.41.9</title>
		<category>Woof</category>
		<description>I have upgraded this as it has important bugfixes.&lt;br /&gt;&lt;br /&gt;As well as the shared-library package in the main filesystem, I also compiled it statically in uClibc, as the initrd needs &#39;e2fsck&#39;, &#39;fsck&#39;, and &#39;resize2fs&#39;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01056</link>
		<title>Intel 537 modem drivers</title>
		<category>Woof</category>
		<description>Rerwin has compiled these for the 2.6.30.5 kernel, and created new firmware tarball and udev rules.&lt;br /&gt;&lt;br /&gt;I have updated, will be in 4.3beta3.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01055</link>
		<title>Default image viewer</title>
		<category>Woof</category>
		<description>I have changed the default image viewer to Viewnior, instead of MU&#39;s Pictureviewer.&lt;br /&gt;&lt;br /&gt;Pictureviewer is still in Puppy, as MU&#39;s PuppyBrowser needs it, due to it&#39;s drag-and-drop capability.&lt;br /&gt;&lt;br /&gt;But now, click on any image in Rox, and it will launch in Viewnior.&lt;br /&gt;&lt;br /&gt;Note, I have stayed with Viewnior v0.6. The latest version is 0.7 which introduces image cropping, however I&#39;m really not so sure that I want the image viewer to have editing capabilities.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01054</link>
		<title>EmbeddedBookmarks bugfix</title>
		<category>Woof</category>
		<description>MU created EmbeddedBookmarks, but when I made it into a PET package I left out a file, so that when the icon to launch EmbeddedBookmarks from within PuppyBrowser is clicked, it fails to launch. Fixed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01053</link>
		<title>Gtkhash</title>
		<category>Woof</category>
		<description>Ttuuxxx has created a lovely little PET package for generating md5 and sha1 hashes (these are signatures that we use to verify integrity of a file).&lt;br /&gt;&lt;br /&gt;Ttuuxx has also integrated it into ROX-Filer so that for .pet, .tar.bz2, .iso, .tar.gz and .sfs files there is an entry in the right-click menu to launch Gtkhash.&lt;br /&gt;&lt;br /&gt;This will be in 4.3beta3.&lt;br /&gt;&lt;br /&gt;Ttuuxxx&#39;s forum post:&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=32700 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=32700&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Gtkhash home:&lt;br /&gt;&lt;a href=http://gtkhash.sourceforge.net/ target=_blank&gt;http://gtkhash.sourceforge.net/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01052</link>
		<title>Hiawatha 6.17.1</title>
		<category>Woof</category>
		<description>I had previously discussed doing so, have now done it, upgraded the Hiawatha web server to version 6.17.1.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01051</link>
		<title>Hewlett Packard drivers</title>
		<category>Woof</category>
		<description>Thanks to MU (Mark) who created these packages. I will be placing them in the official Puppy4 repo at ibiblio.org, as it is reported to work in 4.3beta2.&lt;br /&gt;&lt;br /&gt;These provide more complete support for HP printers and scanners than the SANE and Gutenprint drivers builtin to Puppy.&lt;br /&gt;&lt;br /&gt;The packages will be named &#39;hpliplite-3.9.8-mu-p4.pet&#39; and &#39;libnetsnmp-15-mu-p4&#39; -- the latter is a required dependency.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01050</link>
		<title>Pfind, Pfilesearch, Pburn</title>
		<category>Woof</category>
		<description>Zigbert&#39;s apps upgraded:&lt;br /&gt;Pfind 4.15&lt;br /&gt;Pfilesearch 1.20&lt;br /&gt;Pburn 3.0.4&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01049</link>
		<title>NicoEdit 2.0</title>
		<category>Woof</category>
		<description>I have upgraded NicoEdit to version 2.0. Nicolas posted it here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.murga-linux.com/puppy/viewtopic.php?t=39560&amp;start=390 target=_blank&gt;http://www.murga-linux.com/puppy/viewtopic.php?t=39560&amp;start=390&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This is brilliant. Nicolas, you are to be congratulated on creating such a lovely little text editor. It is good enough I reckon to satisfy most Puppians, so I have removed Geany (Geany could be in the devx perhaps).&lt;br /&gt;&lt;br /&gt;One thing NicoEdit does not support is tabs, but there is a &#39;History&#39; menu will allows quick flipping between documents -- actually, as I often have a lot of documents open, too many for the tabbed system to comfortably handle, the way NicoEdit does it is good.&lt;br /&gt;&lt;br /&gt;Nicolas wisely rolled development back a bit, removing the theming support, and just focusing on a simple functional text editor for 2.0final.&lt;br /&gt;&lt;br /&gt;The PET is only 47KB, although it does need gtksourceview (208KB PET) -- but gtksourceview is already needed in Puppy by Notecase.&lt;br /&gt;The Geany PET package is 748KB, so we shave about 500KB off the live-CD.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01048</link>
		<title>GRUB fixed</title>
		<category>Woof</category>
		<description>Thanks to the guys reporting back in the 4.3beta2 forum thread, the problem with GRUB is fixed.&lt;br /&gt;&lt;br /&gt;The GRUB in 4.3beta2 is patched to recognise ext4, however something is wrong with it as many people were unable to boot.&lt;br /&gt;&lt;br /&gt;So I grabbed GRUB 0.97 from Ubuntu, release &quot;29ubuntu53&quot;, which, if my memory serves me correctly, has a patch for ext4. I made this into a PET package and posted it to the forum. Feedback is that it works!&lt;br /&gt;&lt;br /&gt;So, 4.3beta3 will have &#39;grub-29ubuntu53.pet&#39;.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01047</link>
		<title>4.3 release schedule</title>
		<category>Woof</category>
		<description>I have got the Perth Royal Show gig coming up again this year. Those of you who have monitored my blog for over a year will know of this. I have worked there as a &quot;Pavilion Steward&quot; for the last couple of years, in a pavilion that has displays of the various regions of Western Australia. Here is a snapshot of my Midwest region from last year:&lt;br /&gt;&lt;br /&gt;&lt;img src=http://puppylinux.com/bkauler/ras-midwest-fri.jpg /&gt;&lt;br /&gt;&lt;br /&gt;What I would like to do is get 4.3final out before that, and I&#39;m aiming for the 18th September. The Royal Show starts sometime after that, but I want some leeway to handle feedback immediately after 4.3final is released -- as I won&#39;t have much Internet access while in Perth this time. I&#39;ll be in Perth about 2 weeks -- I work at the show from about 1 week before it starts, helping construction and general setup in the pavilion, then the actual Show runs for about 1 week.&lt;br /&gt;&lt;br /&gt;So, I plan to upload 4.3beta3 about 5-6 days from now.&lt;br /&gt;&lt;br /&gt;The alternative is that I delay 4.3final until about mid-October, but would prefer not to do that.&lt;br /&gt;&lt;br /&gt;Perth Royal Agricultural Show home page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.perthroyalshow.com.au/ target=_blank&gt;http://www.perthroyalshow.com.au/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01046</link>
		<title>My old Cyrix CPU</title>
		<category>Woof</category>
		<description>I&#39;ve got an old workhouse PC, mostly retired now but I fire it up every now and again to test Puppy.&lt;br /&gt;&lt;br /&gt;Cyrix 6x86 200MHz CPU, 128MB RAM, el-cheapo 14-inch monitor. The BIOS is dated Feb. 1998.&lt;br /&gt;&lt;br /&gt;Have just tested 4.3beta2. This is my bottom-of-the-rung machine -- if the pup runs on this, I&#39;m happy. Yep, 4.3beta2 is fine, although I found a bug, the serial mouse setting was not remembered after creating a pupsave -- I thought that old bug was fixed, I&#39;ll take another look at it.&lt;br /&gt;&lt;br /&gt;Anyway, tempestuous raised the question, will the 2.6.30.5 kernel be the final kernel for 4.3? I&#39;m very happy with it, there are no showstopper bugs reported on the forum... so, yes, that&#39;s it.&lt;br /&gt;&lt;br /&gt;The 2.6.30.5 source is here:&lt;br /&gt;&lt;a href=http://puppylinux.com/sources/kernel-2.6.30.5/ target=_blank&gt;http://puppylinux.com/sources/kernel-2.6.30.5/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01045</link>
		<title>The &quot;zdrv&quot;</title>
		<category>Woof</category>
		<description>I posted this to the forum, reproducing here:&lt;br /&gt;&lt;br /&gt;Quote from rerwin:&lt;br /&gt;&lt;i&gt;I am about to build a set of Intel537 drivers -- there are actually 4 of them, for the various flavors. Each is about 4 MB, so I fear for what that would do to puppy&#39;s waistline. Because I favor a puppy that can load its program squashfile into the ramfs in PCs with only 256 MB of RAM, I suspect we are facing migrating the heaviest of the modem drivers to a zdrv (or equivalent) auxiliary squashfile. Perhaps all modem drivers in their own subdirectories would be candidates for migration, except for modems built into laptops or motherboards. That would recognize that not all users need all of the modem drivers in their ramfs.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Yes, 4.3 is going to end up too fat!&lt;br /&gt;I&#39;m going to add another choice in the Woof &#39;3builddistro&#39; script to extract just the large modem drivers and their firmware tarballs into a separate &#39;zdrv&#39;.&lt;br /&gt;&lt;br /&gt;This zdrv will not be in the live-cd iso, it will be available separately for download.&lt;br /&gt;&lt;br /&gt;The zdrv has to be named in a very precise manner. This is how it is done:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;PREFIX1CHAR=&quot;`echo -n &quot;$DISTRO_FILE_PREFIX&quot; | cut -c 1`&quot;&lt;br /&gt;KERNEL3CHARS=&quot;`echo -n &quot;$KERNELVER&quot; | tr -d &#39;.&#39; | tr -d &#39;\-&#39; | tr -d &#39;[a-z]&#39; | rev | cut -c 1,2,3 | rev`&quot;&lt;br /&gt;&lt;br /&gt;z${PREFIX1CHAR}${DISTRO_VERSION}${KERNEL3CHARS}.sfs&lt;br /&gt;&lt;/i&gt;&lt;br /&gt;In 4.3beta2 (as I intend for the final) DISTRO_FILE_PREFIX=&quot;pup&quot;&lt;br /&gt;For the 2.6.30.5 kernel, KERNEL3CHARS=&quot;305&quot;&lt;br /&gt;&lt;br /&gt;So, for 4.3final, the zdrv must be named:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;zp430305.sfs&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Anyone can provide a zdrv with this name, with their own drivers or whatever, or even start with my official one and add more stuff to it.&lt;br /&gt;&lt;br /&gt;It isn&#39;t controlled by the BootManager, if present at /mnt/home it gets automatically loaded. Puppy will automatically run &#39;depmod&#39; first time it is loaded, and again if it is removed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01044</link>
		<title>FLAC, MP4 player</title>
		<category>Woof</category>
		<description>As requested, I have added mime-type handling for .flac audio files.&lt;br /&gt;The handler for ROX-Filer is /root/Choices/MIME-types/audio_x-flac and will launch the audio file with &#39;defaultaudioplayer&#39; (currently Aqualung).&lt;br /&gt;&lt;br /&gt;Coolpup has been urging me to add mime-type handling for .mp4 video files.&lt;br /&gt;Puppy already has /root/Choices/MIME-types/audio_mp4 (.m4a files) which will launch &#39;defaultaudioplayer&#39;.&lt;br /&gt;The MIME mechanism already recognises a .mp4 video file as video/mp4, so I have created /root/Choices/MIME-types/video_mp4 which will launch &#39;defaultmediaplayer&#39; (currently Gxine).&lt;br /&gt;&lt;br /&gt;Note that /usr/share/mime/globs already has:&lt;br /&gt;&lt;br /&gt;audio/x-flac:*.flac&lt;br /&gt;audio/mp4:*.m4a&lt;br /&gt;video/mp4:*.m4v&lt;br /&gt;video/mp4:*.mp4&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01043</link>
		<title>Upgrade Flash player?</title>
		<category>Woof</category>
		<description>Coolpup is urging me to upgrade to the latest Flash player. Coolpup has created this information page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.org/wikka/AdobeFlashPlayer target=_blank&gt;http://puppylinux.org/wikka/AdobeFlashPlayer&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Pup 4.3beta2 still has Flash player version 9.0.48.0, which is getting rather old.&lt;br /&gt;I have stayed with it because it works for me, and is small.&lt;br /&gt;&lt;br /&gt;So, do we really have to move up?&lt;br /&gt;&lt;br /&gt;Are you guys finding Flash-based sites that don&#39;t work with the older player?&lt;br /&gt;&lt;br /&gt;Of course, the latest player is supposed to have fixed some security holes.&lt;br /&gt;&lt;br /&gt;This is the main reason I am so reluctant to upgrade:&lt;br /&gt;flashplayer-9.0.48.0.pet 2545KB&lt;br /&gt;flashplayer-10.0.32.18.pet 3951KB&lt;br /&gt;...these are the compressed sizes, so the upgrade would cause the live-CD size to jump up about 1.4MB.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01042</link>
		<title>424: JWM fix, 536 modem driver</title>
		<category>Woof</category>
		<description>JWM version 456 PET package had an invalid &lt;corner&gt; tag in &#39;.jwmrc&#39;. Removed.&lt;br /&gt;&lt;br /&gt;Rerwin has patched the Intel 536 analog modem (dialup) to compile on the 2.6.30.5 kernel.&lt;br /&gt;I have added the source to &lt;a href=http://puppylinux.com/sources/kernel-2.6.30.5/3rd-party/modem target=_blank&gt;http://puppylinux.com/sources/kernel-2.6.30.5/3rd-party/modem&lt;/a&gt;, also added the kernel module to Puppy, for the upcoming 4.3beta3.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01041</link>
		<title>Testing latest Hiawatha</title>
		<category>Woof</category>
		<description>I have compiled the latest Hiawatha web server, version 6.17.1. &lt;br /&gt;&lt;br /&gt;Tested PPLOG, our personal blog, seems ok.&lt;br /&gt;&lt;br /&gt;Very basic testing with QUISP, seems ok.&lt;br /&gt;&lt;br /&gt;However, 4.3beta1 testers reported that they were able to get a server error. Lobster, you were one of those people.&lt;br /&gt;I was wondering, do you recall the steps to reproduce that error?&lt;br /&gt;If I can follow those same steps, then I will find out if the new Hiawatha has the same problem.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01040</link>
		<title>Advanced Xorg for 4.3beta2</title>
		<category>Woof</category>
		<description>MU has created an Xorg package with upgraded Intel and ATI drivers. This is reported to work in 4.3beta1 and beta2:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46266 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46266&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01039</link>
		<title>Puppy 4.3beta2</title>
		<category>Woof</category>
		<description>Now available, download from here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.3beta2/ target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/test/puppy-4.3beta2/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Theme&lt;/b&gt;&lt;br /&gt;Still not finalised, though the choice in 4.3beta2 looks ok to my eyes. Very business-like. Using icons by steve_s and background by zigbert.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Kernel&lt;/b&gt;&lt;br /&gt;I have built two live-CD iso files only, both with the 2.6.30.5 kernel. One of them has the SCSI drivers.&lt;br /&gt;I am seriously thinking of offering 4.3final with only this kernel -- other people can create builds with older kernels if they wish, and offer them for others to download.&lt;br /&gt;4.3beta2 with 2.6.30.5 has heaps of analog (dialup) modem drivers provided by rerwin (including all the Conexant drivers), which is why it is a bit fat (101MB).&lt;br /&gt;&lt;br /&gt;Note, it will please a certain person, this kernel also has the Ham Radio modules.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Image viewer&lt;/b&gt;&lt;br /&gt;Surprise -- Fotoxx is gone, replaced by Viewnior. Let me know what you think. Do you think that Viewnior should be the default image viewer instead of PictureViewer?&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Text editor&lt;/b&gt;&lt;br /&gt;Back with Geany. We still have syntax highlighting for Genie code via the NicoEdit 0.16 basic text editor included in the 4.3beta2 build.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Printing&lt;/b&gt;&lt;br /&gt;Would someone like to volunteer to create a hpijs printer package? The reason I ask this is there has been feedback that existing hpijs pet packages do not work in 4.3beta1. Some of you guys who are much more into messing round with printing could do a better job of preparing a hpijs pet package than me.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Release notes&lt;/b&gt;&lt;br /&gt;The release notes/announcement page is still there, but I haven&#39;t updated it since 4.3beta1:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/download/release-4.3.htm target=_blank&gt;http://puppylinux.com/download/release-4.3.htm&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Known bugs in beta2&lt;/b&gt;&lt;br /&gt;1. Nathan Wallpaper Setter broken. The XML for gtkdialog is broken by the absence of fotoxx. The fixed package is &#39;wallpaper-0.5.4.pet&#39;, available from the forum 4.3beta2 feedback thread.&lt;br /&gt;3. Even as I was uploading beta2, zigbert brought out another Pburn (3.0.4) -- grab the latest from here: &lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=23881 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=23881&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Forum feedback&lt;/b&gt;&lt;br /&gt;For all bug reports, and good news too:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=46273 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=46273&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Planning for 4.3beta3&lt;/b&gt;&lt;br /&gt;I intend that this will be the last beta before the final. Some things that need to be done by beta3:&lt;br /&gt;&lt;br /&gt;1. Fix upgrading a &#39;pupsave&#39; from 4.2x.&lt;br /&gt;2. Rerwin&#39;s 536/537 modem drivers.&lt;br /&gt;...more...&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01038</link>
		<title>GenieCC Genie code generator</title>
		<category>Woof</category>
		<description>I&#39;m posting this here, as the main forum is down.&lt;br /&gt;&lt;br /&gt;Nicholas has created a &quot;code generator&quot; for Genie. What it does is translate a simplified pseudo-code into Genie code.&lt;br /&gt;&lt;br /&gt;If the forum was working, you could download it. Maybe it will come-good soon.&lt;br /&gt;&lt;br /&gt;Anyway, to compile it in 4.3beta1 or beta2 requires a couple of modifications:&lt;br /&gt;&lt;br /&gt;Build it:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# ./waf configure&lt;br /&gt;# ./waf build&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;The configure step reports that Vala compiler 0.7.5 or later is required. Puppy only has 0.7.4. However I edited &#39;wscript&#39; so that it would accept 0.7.4, and it compiles.&lt;br /&gt;&lt;br /&gt;However at the second step it was unable to find the gee header files. They are at /usr/include/gee-1.0/gee. So, I created a link:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;# ln -s gee-1.0/gee /usr/include/gee&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;The idea is interesting. If this pseudo-code is simple yet capable, and well documented, then it would make it easy to get into creating Genie apps.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01037</link>
		<title>Murga forum problems</title>
		<category>Woof</category>
		<description>John has contacted me about the main Puppy forum. It is having trouble. John is putting in considerable effort to try and fix it -- if not, may move to a new host in a couple of weeks.&lt;br /&gt;&lt;br /&gt;John is one of those guys who supports Puppy behind the scenes. It is no small feat to look after such a big and busy forum. John also hosts it at his own expense.&lt;br /&gt;&lt;br /&gt;We do of course have the linuxquestions.com alternative forum for Puppy. I think Lobster create one also?&lt;br /&gt;&lt;br /&gt;Forum member tclhost (Thom) has just contacted me. He has setup another backup forum:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.us/smf/ target=_blank&gt;http://puppylinux.us/smf/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...I emailed and asked if some more categories could be created in it.&lt;br /&gt;&lt;br /&gt;Our backup LinuxQuestions forum is here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.linuxquestions.org/questions/puppy-71/ target=_blank&gt;http://www.linuxquestions.org/questions/puppy-71/&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01036</link>
		<title>4.3beta2 in 10 hours</title>
		<category>Woof</category>
		<description>I had it ready several hours ago, but was uploading the latest PET packages to ibiblio.org.&lt;br /&gt;&lt;br /&gt;Now I have started to upload the 4.3beta2 files, but you&#39;ll have to wait.... and wait. Ibiblio can be painfully slow sometimes -- currently uploading at 10KB/sec and estimated completion is 10 hours from now... &lt;br /&gt;&lt;br /&gt;I&#39;m posting this message at 7.35am GMT+8 (Western Australia). So, barring any upload failure, completion will be by 5.35pm.&lt;br /&gt;&lt;br /&gt;Use a international time converter, such as this one, to figure out your local time:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.timeanddate.com/worldclock/converter.html target=_blank&gt;http://www.timeanddate.com/worldclock/converter.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...for example, in Los Angeles the completion time will be &quot;Sunday, September 6, 2009 at 2:35:00 AM&quot;&lt;br /&gt;&lt;br /&gt;Of course, I&#39;ll announce it on this blog.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01035</link>
		<title>ALSA upgrade, scanner, printer tests</title>
		<category>Woof</category>
		<description>&lt;b&gt;Audio&lt;/b&gt;&lt;br /&gt;As has been reported, alsa-lib and alsa-util in 4.3beta1 are rather old (v1.0.16). I have upgraded them to v1.0.20, matching the version in the 2.6.30.5 kernel.&lt;br /&gt;&lt;br /&gt;Immediately there is a good outcome. One problem has been that, with certain audio hardware anyway, small audio files get truncated. For example, /usr/share/audio/2barks.au and 2barks.wav come out as a single bark. No more, on my laptop at least, I now get two distinct barks.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Scan&lt;/b&gt;&lt;br /&gt;Recently when I was driving home from Perth, I stopped at my favourite little opportunity shop -- I have mentioned this place before, picked up a couple of PCs there before. It&#39;s in a small country town, run by the local church.&lt;br /&gt;&lt;br /&gt;Anyway, they had a USB scanner, Hewlett Packard ScanJet 4200C, for $4. That&#39;s a bit of a gap in my test suite, so I bought it.&lt;br /&gt;&lt;br /&gt;This evening I am doing some testing of the soon-to-be-released 4.3beta2 and tested this scanner. I ran Xsane, and scanned a page, no problem whatsoever. Very nice.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Print&lt;/b&gt;&lt;br /&gt;Have also done a basic sanity test for printing, to my parallel-port Epson Stylus C41SX, that was also acquired from the opportunity shop awhile back.&lt;br /&gt;&lt;br /&gt;As I recall, there was feedback that printing was not working from certain applications, and over a LAN. I will have to hold-over the latter as I don&#39;t have a LAN setup.&lt;br /&gt;&lt;br /&gt;First stop, trying ePDFView. There&#39;s a demo PDF file at /usr/share/examples/ps-pdf/Acrobat.pdf. Yep, prints.&lt;br /&gt;&lt;br /&gt;Now for Abiword. This is version 2.6.3 with 2.6.8 plugins, as discussed in my earlier post. I opened /usr/share/examples/text/testdoc.doc. Success again.&lt;br /&gt;&lt;br /&gt;And SeaMonkey. Opening /usr/share/doc/home.htm. That prints also.&lt;br /&gt;&lt;br /&gt;After I have released 4.3beta2, would someone like to volunteer to create a hpijs printer package? The reason I ask this is there has been feedback that existing hpijs pet packages do not work in 4.3beta1. Some of you guys who are much more into messing round with printing could do a better job of preparing a hpijs pet package than me.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01034</link>
		<title>423: Abiword 2.6.3</title>
		<category>Woof</category>
		<description>I have been experimenting with Abiword 2.6.3 and the 2.6.8 plugins. Seems to be working fine.&lt;br /&gt;&lt;br /&gt;One interesting discovery, that would explain why the Presentation plugin did not work in earlier testing with Abiword 2.7.x -- it requires the Loadbinding plugin.&lt;br /&gt;&lt;br /&gt;I compiled Link-grammar 4.6.1, as I would like the grammar plugin to be working.&lt;br /&gt;&lt;br /&gt;Here is how I compiled everything:&lt;br /&gt;&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;abiword 2.6.3&lt;br /&gt;error, chooses internal goffice, so edit &#39;configure&#39;, change &quot;libgoffice-0.4&quot; to &quot;libgoffice-0.6&quot;:&lt;br /&gt;&lt;br /&gt;GOFFICE_VERSION_REQUIRED=&#39;0.4.0&#39;&lt;br /&gt;goffice_modules=&quot;libgoffice-0.6 &gt;= $GOFFICE_VERSION_REQUIRED&quot;&lt;br /&gt;&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-printing --enable-threads --disable-gucharmap --disable-scripting --without-ImageMagick&lt;br /&gt;&lt;br /&gt;link-grammar 4.6.1&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-pc-linux-gnu&lt;br /&gt;&lt;br /&gt;abiword-plugins 2.6.8&lt;br /&gt;# ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-pc-linux-gnu --disable-all --enable-abigrammar --enable-freetranslation --enable-gdict --enable-presentation --enable-bmp --enable-jpeg --enable-librsvg --enable-mswrite --enable-OpenDocument --enable-OpenWriter --enable-pdf --enable-xhtml --with-abiword=../abiword-2.6.3 --without-boost --enable-loadbindings&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;Note, I didn&#39;t compile the OpenXML plugin as it needs the &#39;boost&#39; package. Note, technosaurus has compiled Abiword 2.7.10 with OpenXML, and found that it only needs one small library out of boost. I suppose we could add the OpenXML plugin to my package afterwards.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01033</link>
		<title>Fatdog2 32bit beta2</title>
		<category>Woof</category>
		<description>This was released quietly on 8th August, I only noticed it a few days ago. Kirk has used T2 to compile from source, and the Woof build system, to create Fatdog2, in two flavours, 32-bit and 64-bit.&lt;br /&gt;&lt;br /&gt;This is extremely interesting work, and likely to be one of the Puppy-5 releases.&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=45335 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=45335&lt;/a&gt;&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01032</link>
		<title>KolibriOS: a tiny operating system</title>
		<category>General</category>
		<description>Wow, this has stirred up some memories! See the feature story in this week&#39;s Distrowatch News:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distrowatch.com/weekly.php?issue=20090831 target=_blank&gt;http://distrowatch.com/weekly.php?issue=20090831&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src=http://www.kolibrios.org/images/screenshots/0.6.5.0/big/opengl_tetris_minesweeper.png /&gt;&lt;br /&gt;&lt;br /&gt;Here is the KolibriOS home:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://wiki.kolibrios.org/ target=_blank&gt;http://wiki.kolibrios.org/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;KolibriOS is written in x86 32-bit assembly language and is a fork of MenuetOS. Back in 2002 I was involved with MenuetOS, and still have a web page:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://goosee.com/menuetos/index.html target=_blank&gt;http://goosee.com/menuetos/index.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;What about the original MenuetOS project? Yes, it is still going:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://www.menuetos.net/ target=_blank&gt;http://www.menuetos.net/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Fascinating! It&#39;s a great little OS, of course has extreme hardware compatibility limitations, and is reinventing the wheel, but it&#39;s design is so satisfying from the point of view of the tiny size and extreme speed and efficiency.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01031</link>
		<title>e3 fixed</title>
		<category>Woof</category>
		<description>I was puzzled, when I released a new 4.3 alpha or beta, e3 was broken. Note, &#39;vi&#39; runs e3 in its vi-compatible mode.&lt;br /&gt;&lt;br /&gt;I have found out why. I introduced file stripping into the &#39;3builddistro&#39; script in Woof, and it also strips e3 -- result, e3 reduces from 13KB to 208 bytes and won&#39;t run.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01030</link>
		<title>aufs2 utilities</title>
		<category>Woof</category>
		<description>I downloaded the Aufs2 utilities from GIT today, and created pet package &#39;aufs2-util-20090904.pet&#39;.&lt;br /&gt;&lt;br /&gt;These utilities will be in 4.3beta2. This includes /usr/share/doc/aufs.htm.&lt;br /&gt;&lt;br /&gt;Puppy has been using Unionfs for sometime, previously when we used Aufs it was the 1.x series.&lt;br /&gt;&lt;br /&gt;We will probably need to study Aufs2 to get the maximum benefit from it, but that can probably be a target for pup 4.4:&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Clean shutdown&lt;/b&gt;&lt;br /&gt;For example, it looks like there is potential for a clean shutdown, something that is an ongoing issue for Puppy.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Write directly to flash&lt;/b&gt;&lt;br /&gt;The /usr/local/petget/installpkg.sh script is able to write directly to the save-layer when running Puppy on a Flash drive, in the case of Unionfs.&lt;br /&gt;We never had this working properly with Aufs.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Unipup&lt;/b&gt;&lt;br /&gt;My Unipup concept, that I was working on sometime ago, runs Puppy totally in the initramfs and does not perform a switch_root. It seems that Aufs2 may be able to support building a layered filesystem within the initramfs -- this capability was a configure option when I compiled the kernel module, which I enabled.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;EDIT, 6 SEPT 2009:&lt;/b&gt;&lt;br /&gt;&lt;b&gt;Dynamic load&lt;/b&gt;&lt;br /&gt;Some of the guys have been working on adding and removing SFS files without rebooting. They had this working with aufs1. &lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01029</link>
		<title>PPM &#39;ALL&#39; category</title>
		<category>Woof</category>
		<description>By popular demand, I have reinstated the &#39;ALL&#39; category in the Puppy Package Manager main GUI window.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01028</link>
		<title>3G wireless, agrsm modem</title>
		<category>Woof</category>
		<description>Rerwin has done a lot of work helping people with getting their 3G wireless devices working. He posted an upgrade to the 4.3beta1 forum thread. These files are upgraded:&lt;br /&gt;&lt;br /&gt;/sbin/pup_event_backend_modprobe&lt;br /&gt;/usr/bin/modemprobe, modemprobe_erase, modemtest, pupdial, usb_modeswitch.sh&lt;br /&gt;&lt;br /&gt;Rerwin has also compiled the agrsm modem driver for the 2.6.30.5 kernel. He has patched the source to get it to compile, which I have uploaded here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/sources/kernel-2.6.30.5/3rd-party/modem/agrsm-20090502-patched.tar.gz target=_blank&gt;http://puppylinux.com/sources/kernel-2.6.30.5/3rd-party/modem/agrsm-20090502-patched.tar.gz&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;There is a new firmware tarball:&lt;br /&gt;/lib/modules/all-firmware/agrsm.tar.gz&lt;br /&gt;&lt;br /&gt;Kernel modules:&lt;br /&gt;/lib/modules/2.6.30.5/extra/agrmodem.ko, agrserial.ko&lt;br /&gt;&lt;br /&gt;Udev rules have been upgraded:&lt;br /&gt;/etc/udev/rules.d/60-udev-modem.rules&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01027</link>
		<title>SFS Converter 1.3.2</title>
		<category>Woof</category>
		<description>Trio has written a little GUI application that will convert a SFS file from version 3 to version 4 and vice versa. This is to be found in the Utility menu.&lt;br /&gt;&lt;br /&gt;I made a few small mods and bumped the version number slightly. The PET package is now &#39;sfs-converter-1.3.2.pet&#39;.&lt;br /&gt;&lt;br /&gt;When you click on a SFS file in Rox, it will be mounted (via /usr/sbin/filemnt), however if the wrong version for the current kernel an error message will come up. I have not put in automatic launching of the converter program, instead just added to the error message that a SFS-version-converter is to be found in the Utility menu.&lt;br /&gt;&lt;br /&gt;The BootManager (/usr/sbin/bootmanager) puts up an information box listing any SFS files found at /mnt/home that are the wrong version. I have also added an information message that a SFS-version-converter is to be found in the Utility menu.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01026</link>
		<title>Sysprof 1.0.12</title>
		<category>Woof</category>
		<description>Sysprof is a &quot;system profiler&quot;, very useful for analysing resource usage of an application. I have upgraded from 1.0.10.&lt;br /&gt;&lt;br /&gt;Sysprof consists of a kernel module and a GTK GUI excutable. The application will be in the &#39;devx&#39; SFS file.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01025</link>
		<title>423: Packages upgraded</title>
		<category>Woof</category>
		<description>Trio&#39;s JWM Theme Maker to 1.4&lt;br /&gt;Zigbert&#39;s Pburn CD/DVD burner to 3.0.3&lt;br /&gt;Zigbert&#39;s Pfind file finder to 4.14&lt;br /&gt;Tasmod&#39;s Psync time server synchronizer to 1.0&lt;br /&gt;Trio&#39;s You2pup youtube downloader to 1.3-1&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01024</link>
		<title>4.3beta2 schedule, updated</title>
		<category>Woof</category>
		<description>Some major bugs have been fixed, and things are looking pretty good.&lt;br /&gt;&lt;br /&gt;Just to let you know, I&#39;m currently thinking of uploading 4.3beta2 in a couple of days. Let&#39;s say, Saturday or Sunday.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01023</link>
		<title>423: GRUB fixed</title>
		<category>Woof</category>
		<description>4.3beta1 testers have reported that a frugal installation of Puppy failed. There was a problem with installing GRUB.&lt;br /&gt;&lt;br /&gt;If you already had GRUB installed and all that you needed to do was modify the /boot/grub/menu.lst file, then you would not have encountered this bug.&lt;br /&gt;&lt;br /&gt;On the otherhand, if you ran /usr/sbin/grubconfig, either from the Universal Installer or the System menu, to install GRUB, then you would have hit the bug.&lt;br /&gt;&lt;br /&gt;There was a typo at line 1003.&lt;br /&gt;&lt;br /&gt;I fixed it, but then I discovered an awful bug that was in the original script -- it wasn&#39;t written by me, I&#39;m just hacking on it!&lt;br /&gt;The partition to which GRUB is to be installed gets mounted on /tmp/boot, however when grubconfig failed it also left the partition mounted. After fixing the script (line 1003) and rerunning the script, one of the first things it does is wipe everything in /tmp/boot -- meaning, it wiped my partition!&lt;br /&gt;&lt;br /&gt;There are a couple of places in the script where this can happen. I have put in some safety checking, so this potential disaster is now fixed.&lt;br /&gt;&lt;br /&gt;Fortunately I didn&#39;t lose a vital partition!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01022</link>
		<title>423: libshadowfb.so</title>
		<category>Woof</category>
		<description>Forum member playdayz made this request:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;would it be possible to include libshadowfb.so with the basic Puppy? It is included in xorg_xorg_full (for 4.2.1); it is necessary for the two virtualizers vmware and virtualbox to use their own video drivers. If it is present in /usr/X11R7/lib/xorg/modules then vmware works out of the box with its own vmware_drv (which is included in the basic Puppy). If it is not present then X will not start from xorgwizard because xorgwizard chooses the vmware_drv which will not start without libshadowfb.so. thanks&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Done.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01021</link>
		<title>2.6.30.5 packages</title>
		<category>Woof</category>
		<description>I have uploaded the 2.6.30.5 patched source and 3rd-party modules here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/sources/kernel-2.6.30.5/ target=_blank&gt;http://puppylinux.com/sources/kernel-2.6.30.5/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The PET package that is used in Woof to build a puppy is here:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-woof/linux_kernel-2.6.30.5-tickless_smp-p4.pet target=_blank&gt;http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-woof/linux_kernel-2.6.30.5-tickless_smp-p4.pet&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;There are some more 3rd-party modules that could be compiled. I was unable to compile these:&lt;br /&gt;&lt;br /&gt;acx wireless driver&lt;br /&gt;linux-wlan-ng wireless, USB module only&lt;br /&gt;536/537 modem&lt;br /&gt;ess modem&lt;br /&gt;&lt;br /&gt;Rerwin said that he would investigate compiling the Intel 536/537 drivers.&lt;br /&gt;Regarding linux-wlan-ng, the hostap drivers already in the kernel supercede that, but I think the USB module in linux-wlan-ng is still required?&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01020</link>
		<title>Conexant modem drivers</title>
		<category>Woof</category>
		<description>Rerwin (Richard) has done a lot of work in getting the Conexant drivers to compile and making them auto-configure in Puppy. You can find his posts in the forum 4.3beta1 feedback thread.&lt;br /&gt;&lt;br /&gt;I have compiled the Conexant &#39;dgc&#39;, &#39;hcf&#39; and &#39;hsf&#39; drivers for the 2.6.30.5 kernel, and updated rerwin&#39;s firmware tarballs accordingly.&lt;br /&gt;&lt;br /&gt;I&#39;m uploading files right now.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01019</link>
		<title>2.6.30.5 kernel!</title>
		<category>Woof</category>
		<description>I decided to test the 2.6.30.5 kernel, see if the multisession problem using cdrkit or cdrtools is fixed. Yes it is!&lt;br /&gt;&lt;br /&gt;I have tested a CD-R and a DVD-R, multisession works fine.&lt;br /&gt;&lt;br /&gt;As I have reached 4.3beta1, I don&#39;t want to make any fundamental changes. But, this is extremely tempting...&lt;br /&gt;&lt;br /&gt;I patched the 2.6.30.5 kernel with aufs2 (cvs 20090831) and it no longer supports unionfs compatibility-mode. Meaning, the whiteout files have different names. This affects a lot of scripts, such as snapmergepuppy, savesession-dvd, init, rc.update. I&#39;m reluctant to make fundamental underlying changes at this stage, but I&#39;ll check it out, might not be potentially troublesome.&lt;br /&gt;&lt;br /&gt;I&#39;ll examine the situation for the whiteout files this afternoon. Also I&#39;ll compile some more 3rd party drivers.&lt;br /&gt;&lt;br /&gt;Note, I only did three patches to the kernel. The loglevel patch, aufs2, and an ALSA patch provided by rerwin.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01018</link>
		<title>b43 firmware problem solved</title>
		<category>Woof</category>
		<description>I think so anyway. I would like to thank trio for patiently answering a series of questions. I would have loved to have had the actual hardware to test, but I reckon that I have got to a solution.&lt;br /&gt;&lt;br /&gt;I will need to study the evolution of the uevent/udev mechanism to fully understand this. I have been relying upon the existence of &#39;modalias&#39; files in /sys for replaying kernel uevents. In /etc/rc.d/rc.sysinit there is code that locates the modalias files, then looks for a &#39;uevent&#39; file at the same location then sends a &quot;replay&quot; message to it.&lt;br /&gt;&lt;br /&gt;The problem is that it doesn&#39;t always work. I don&#39;t know if the problem is due to an evolution in the mechanism in recent kernels, or not. I&#39;m currently running 2.6.29.6, I would need to check this on older kernels.&lt;br /&gt;&lt;br /&gt;For USB interfaces, see this:&lt;br /&gt;&lt;div class=code&gt;&lt;pre&gt;# cat /sys/bus/usb/devices/*/uevent | grep &#39;MODALIAS&#39;&lt;br /&gt;MODALIAS=usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;MODALIAS=usb:v1058p1010d0105dc00dsc00dp00ic08isc06ip50&lt;br /&gt;MODALIAS=usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;MODALIAS=usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;MODALIAS=usb:v046DpC03Dd2000dc00dsc00dp00ic03isc01ip02&lt;br /&gt;MODALIAS=usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;MODALIAS=usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;# &lt;br /&gt;# cat /sys/bus/usb/devices/*/modalias                &lt;br /&gt;usb:v1D6Bp0002d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;usb:v1058p1010d0105dc00dsc00dp00ic08isc06ip50&lt;br /&gt;usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;usb:v046DpC03Dd2000dc00dsc00dp00ic03isc01ip02&lt;br /&gt;usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;That is,the MODALIAS information is to be found in both the &#39;modalias&#39; file and the &#39;uevent&#39; file.&lt;br /&gt;&lt;br /&gt;The problem arises with some newer interfaces, there is no &#39;modalias&#39; file, only a &#39;uevent&#39; file, and the MODALIAS variable is only to be found in the &#39;uevent&#39; file.&lt;br /&gt;&lt;br /&gt;This is the situation that trio has reported:&lt;br /&gt;&lt;br /&gt;&lt;i&gt;There is no modalias anywhere. But found two uevent(s)&lt;br /&gt;&lt;br /&gt;/sys/bus/ssb/devices/ssb0:1/uevent and /sys/bus/ssb/devices/ssb0:0/uevent&lt;br /&gt;&lt;br /&gt;Inside the uevent file:&lt;br /&gt;MODALIAS=ssb:v4243id0812rev0A&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;I have modified /etc/rc.d/rc.sysinit accordingly. It should now successfully replay the uevent for the network hardware that requires the b43 module, and the firmware should get installed.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01017</link>
		<title>Video test collection</title>
		<category>Woof</category>
		<description>I have uploaded some of the video files that I use for testing media players in Puppy:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/test/media-test-video/ target=_blank&gt;http://puppylinux.com/test/media-test-video/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If you have compiled a new release of ffmpeg, xine-lib, Gxine, Mplayer, or whatever, and want to assess it&#39;s suitability for use in Puppy, this collection is useful. All of the above files play with both audio and video in Puppy 4.1.2 and 4.3beta, which has a fairly old version of ffmpeg and xine-lib.&lt;br /&gt;&lt;br /&gt;My testing with more recent releases of ffmpeg has given patchy results. One thing to watch out for is choppy audio playback (to the extent that it is unintelligible) -- especially with the Lindows RealMedia file. Some media players may also have missing audio or video with certain files -- even if you have all the required codecs.&lt;br /&gt;&lt;br /&gt;Video DVDs should also be tested. In particular, the media player needs to be able to display and navigate the initial menu that most DVDs have -- Mplayer is an example that fails dismally here, all versions.&lt;br /&gt;&lt;br /&gt;This file has links to further audio/video test files:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://puppylinux.com/test/media-test-video/sites.txt target=_blank&gt;http://puppylinux.com/test/media-test-video/sites.txt&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;P.S.&lt;br /&gt;IT_Pro.wmv is very amusing!&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01016</link>
		<title>&quot;fontconfig development files missing&quot;</title>
		<category>Woof</category>
		<description>Coolpup recently informed me that the development files for fontconfig were missing in 4.3 pre-beta. I replied that they are present.&lt;br /&gt;&lt;br /&gt;Right now I&#39;m compiling WINE, and when I ran the configure script it complained that fontconfig and libGL development files are missing. This reminded me of the earlier report from coolpup. I double-checked, they are present.&lt;br /&gt;&lt;br /&gt;The problem is that the configure scripts of some applications are extremely dumb. Even though the &#39;/usr/lib/pkgconfig/fontconfig.pc&#39; informs that the development files are to be found under /usr/X11R7, the configure script won&#39;t look there.&lt;br /&gt;However, if you run these export operations before running configure, that should fix it:&lt;br /&gt;&lt;br /&gt;# export CPPFLAGS=&#39;-I/usr/X11R7/include&#39;&lt;br /&gt;# export LDFLAGS=&#39;-L/usr/X11R7/lib&#39;&lt;br /&gt;&lt;br /&gt;There aren&#39;t many distros that use /usr/X11R7. The Puppy 4.x series does because the original packages were compiled in T2 and that&#39;s how T2 does it. Ditto for kirk&#39;s Tpup.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01015</link>
		<title>Puppy with WINE builtin</title>
		<category>Woof</category>
		<description>A couple of days ago I gave a Puppy 4.21 CD to a local farmer. Yesterday he came back, quite excited. He said that he booted the CD on his PC and his son&#39;s PC and everything worked, and he got onto the Internet straightaway no hassles.&lt;br /&gt;&lt;br /&gt;The reason that he came back to see me, is he wants to run Windows applications in Puppy. That&#39;s not something I&#39;m into, but I suggested the easiest route for him might be to download a Puppy derivative with WINE builtin.&lt;br /&gt;&lt;br /&gt;The only one I know of is tazoc&#39;s Lighthouse pup:&lt;br /&gt;&lt;br /&gt;&lt;a href=http://murga-linux.com/puppy/viewtopic.php?t=38898 target=_blank&gt;http://murga-linux.com/puppy/viewtopic.php?t=38898&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;...which looks real nice from the description and snapshots.&lt;br /&gt;&lt;br /&gt;Does anyone know of any other puplets with WINE builtin, or alternatively a pre-prepared WINE pet that will just install and run without requiring any setup?&lt;br /&gt;&lt;br /&gt;Anyway, I&#39;ll send an email to the farmer, let him know about Lighthouse pup.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01014</link>
		<title>Planning for 4.3beta2</title>
		<category>Woof</category>
		<description>Thinking ahead, for the benefit of those who are eagerly awaiting the next release, I can probably upload 4.3beta2 early next week, say Monday or Tuesday.&lt;br /&gt;&lt;br /&gt;The Unionfs problem is still unresolved. Looking back in my blog, July 2008, I reported a problem with Unionfs version 2.3.3 which forced me to go over to Aufs:&lt;br /&gt;&lt;a href=http://www.puppylinux.com/blog/?viewDetailed=00207 target=_blank&gt;http://www.puppylinux.com/blog/?viewDetailed=00207&lt;/a&gt;&lt;br /&gt;The developers were working in version 2.4, a major change, but for a few months they totally ignored bug reports for the 2.3 series. I was most unhappy about that.&lt;br /&gt;Regarding the latest problem, I submitted a bug report on Aug 22, so hopefully it will get attention soon:&lt;br /&gt;&lt;a href=https://bugzilla.fsl.cs.sunysb.edu/show_bug.cgi?id=634 target=_blank&gt;https://bugzilla.fsl.cs.sunysb.edu/show_bug.cgi?id=634&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I think by this coming Sunday I will have to recompile the 2.6.29.6 kernel, I am very much hoping for the last time, and if Unionfs is not fixed by then I&#39;ll leave it out. Regardless, I&#39;ll put in the Aufs patch.&lt;br /&gt;&lt;br /&gt;Regarding the &#39;devx&#39; file, the gtkdialog examples were missing in 4.3beta1, fixed. Also, the next release will have the &#39;git&#39; package.&lt;br /&gt;</description>
		</item><item>
		<link>http://bkhome.org/blog/?viewDetailed=01013</link>
		<title>GParted: desktop icons refreshed</title>
		<category>Woof</category>
		<description>The daemon /sbin/pup_event_frontend_d has a fe