The "standard" configuration is conservative, with 'ticks' enabled, and uniprocessor. It also has ext4 support builtin (not a module). It is compiled in Jaunty-Puppy.
There are only two patches, to change the default loglevel from 7 to 3, and Unionfs 2.5.1.
3rd party modules
I compiled some 3rd-party modules:
ntfs-3g-2009.4.4 (not a module, uses fuse.ko)
I tried, couldn't get these modem drivers to compile:
ess, agrsm, Intel 537EP, ltmodem, hsfmodem
...hopefully some of these will be updated soon. I have been in contact with the ESS maintainer in the past, he at least is likely to respond to a plea.
I have created a kernel source SFS file, but it is in Squashfs 4.0 format. Also a patched source .tar.gz tarball. Also module sources. Uploaded to here:
I have taken a new approach for true-SCSI drives. Instead of compiling special kernels with SCSI support builtin -- three of them I think I did before -- this time I am staying with the "standard" kernel. Instead, Woof has a live-CD build option to place SCSI modules in the 'initrd.gz' file.
When I upload the 'upup-463-SCSI.iso' (alpha5, expected in a day or two), anyone with SCSI hardware is invited to test it. It will only work for PCI-based computers, in which the SCSI drive is connected via a PCI card or motherboard PCI interface.
Comments:Posted on 20 Apr 2009, 12:06 by happypuppy
Any plans for a Puppy with a real-time multimedia kernel as the ones used in Ubuntu Studio and Musix?
Posted on 20 Apr 2009, 14:44 by happypuppy
or a Puppy with a semi-RT kernel
...or at least a kernel configured for semi-realtime operation,like Windows XP.
Just enable these kernel config options for that:
CONFIG_HZ=1000 (and uncomment 250Hz)
CONFIG_PREEMPT (and uncomment PREEMPT_VOLUNTARY)
A true real-time kernel requires an *RT patch*:
and enabling these options:
Also one should comment out / disable all debugging options.
Posted on 20 Apr 2009, 14:47 by MU
I can see in your config:
# CONFIG_PCI_MSI is not set
Vesions 9.1 of the Ati catalyst driver required:
Or it refused to compile in 220.127.116.11.
So for 18.104.22.168 we activated this option.
I don't know, if this still is required for the newer drivers 9.4 or newer Kernels.
Posted on 20 Apr 2009, 14:52 by MU
you currently use:
Posted on 20 Apr 2009, 15:48 by Béèm
I am happy with this decision as it means that probably my 2 sata HDD's in my Medion MD8818 will be supported.
It is actualy in upup-015, but not any more in jaunty.
Maybe consider smp support also. More and more new PC's/laptops have dual processors.
Posted on 20 Apr 2009, 16:08 by happypuppy
Drivers and PCI_MSI
CONFIG_PCI_MSI is not set
I think nVidia drivers (and other non-driver stuff) require this option as well.
Posted on 20 Apr 2009, 17:23 by Leon
you currently use:
Yes, that would make a real progress.
wow's solution finally allowed file operations with files that have non-US locale characters in filenames.
Posted on 20 Apr 2009, 23:31 by Guy2
Why aren't you using AUFS?
It now supports 2.6.29 too.
Posted on 21 Apr 2009, 13:42 by happypuppy
How about a Zenwalk-based Woof?
Zenwalk is Slackware based,but much better,lighter and with a superior package repository.
Slackware is becoming more bloated with each release (loads of unneeded dependencies) :(
The Zenwalk guys are doing a much better job - they even have precompiled realtime kernels for download:
Posted on 21 Apr 2009, 23:37 by helander
The last part in the kernel_patches.txt (about firmware install) was a bit cryptic (for me at least). I would appreciate some elaboration on the steps that should be performed.
Posted on 22 Apr 2009, 2:03 by BarryK
You can ignore that last bit, it was for the case where the kernel is configured with external firmware "blobs". However I have configured with the blobs builtin to the kernel binary.
Posted on 22 Apr 2009, 3:35 by helander
Thanks for the firmware info.
I am planning to build a kernel with the RT patches applied. I have built a 2.6.29 kernel with RT and uinionfs that works fine, but for another distro (TinyCore) but for various reasons I would like to use Puppy instead. I have not yet integrated any kernel into Puppy/Woof yet, so I would like to get access to some up-to-date instructions on how to build the initrd etc. Is that somehow "automated" within Woof?
Posted on 22 Apr 2009, 9:47 by BarryK
Yes, Woof does it all.
Posted on 22 Apr 2009, 24:34 by helander
Kernel Pet package
I studied the woof build files and found out that the kernel should be packaged as a pet package prior to the woof build. What is the preferred way to build the kernel pet package; look at the structure of an existing kernel pet package and create a package having the same structure but with my own kernel image (and I guess the corresponding modules as well) or do you have some script available that I can adjust to my "needs" that will build a proper kernel pet package?
Posted on 23 Apr 2009, 7:37 by BarryK
Re: kernel PET pkg
Yes, you will have to create a directory that mimics the same layout as the other kernel PET packages. Let's say it's 'linux_kernel-22.214.171.124-myversion' -- also give it the same base name "linux_kernel". Then convert to PET:
# dir2tgz linux_kernel-126.96.36.199-myversion
# tgz2pet linux_kernel-188.8.131.52-myversion.tar.gz
Posted on 30 Apr 2009, 22:07 by coolpup
184.108.40.206 stable kernel update
The 220.127.116.11 stable kernel update is out; it contains about 100 patches. "There are a lot of fixes in this release touching all over the tree. At least a few have possible security impact (e.g. af_rose, agp, capability fs_mask, splice/ocfs2). As usual, you're encouraged to upgrade."