This forum thread is for anyone who wants to discuss the concepts, and implementation-of in Quirky.
Any other issues, such as video incompatibility, an application not working right, etc., is not a Quirky issue -- as Quirky is built from Racy packages, so post such feedback to the Wary/Racy forum thread:
http://murga-linux.com/puppy/viewtopic.php?t=84618_________________http://bkhome.org/news/

The point was made on my blog that, like Tinycore Linux, this "one file" technique requires a lot of RAM.

Yes and no. The comparison with Tinycore is not appropriate. It has been a very long time since I looked at Tinycore, so correct me if I am wrong, but I seem to recall that Tinycore has the entire filesystem in the "initramfs", full expanded, and runs it from there. No switch_root is involved.

Quirky does it totally differently. Quirky has the usual Puppy files, 'vmlinuz', 'initrd.gz', 'racy_5.4.91.sfs', it is just that the latter two are embedded inside the former.

Or, more correctly, initrd.gz, which is the cpio initramfs, is embedded inside vmlinuz, and racy_5.4.91.sfs is embedded inside initrd.gz.

Now, racy_5.4.91.sfs is our usual xz-compressed squashfs filesystem, so is very small, and it stays that way.

At bootup, a tmpfs is created and racy_5.4.91.sfs is placed in it, then moved into a aufs layered filesystem (which also has a save-file on subsequent boots), then a switch_root takes place and the initramfs is discarded.

In other words, only the original kernel is left (totally) in RAM.

puppy_5.4.91.sfs, which has all of the Puppy files, is in a tmpfs, which is also in RAM, but the operating system is able to use a swap file/partition.

Which means, that the Quirky approach does not need a "lot of RAM". Not necessarily, anyway. I mentioned in the Quirky release notes that there should be at least 512MB RAM, however Quirky would probably work in 256MB RAM if there is a swap file/partition -- but, I wouldn't recommend it, it would likely be slow._________________http://bkhome.org/news/

Yes, I have been thinking that for sometime. I left it at that name for now, to get the ball rolling.

As any Puppy can be built as a "one file" Puppy, I suggest that the name include the name of the Puppy.

As far as the "qky" extension, I suggest "pup". We did have .pup package files a long time ago, but that extension should now be available for a new use.

So, a one-file pup built from Racy could be 'racy.pup'.

But, should the version number be included?

In that case, it would be 'racy-5.4.91.pup'

We can reserve .pup to always mean these one-file puppies. Furthermore, we can get ROX-Filer to recognise .pup mime-type to have this new meaning, and offer to open up and edit the contents -- for those who would like to hack the contents.

We already do this for 'initrd.gz' files. Awhile back I added mime-type handling, so if you click on a 'initrd.gz' file, you get an offer to open it up, then you can edit the contents, then put it together again. Which is great for hacking your pup's bootup._________________http://bkhome.org/news/

Ray I fail to get what your refer to here
"So logically Q (folders) are positioned after P folders (dir)’s and
before R. If one just dumps one’s Q (qky) folder (dir) anywhere -
grub4dos gets the hump."

How can one decide on such things? The computer place it where it does?

Okay I download and see if it loads _________________I use Google Search on Puppy Forum
not an ideal solution though

Normally when one installs and runs grub4dos - it will search your drives and automatically produce a menu.lst.

However as BK explains - with kernel.qky - one needs to manually edit menu.lst - because grub4dos won’t automatically work with “kernel.qky” - therefore where (in menu.lst) one positions one’s manually edited entry is potentially important when using grub4dos.

The old Nouveau problem has definitely reared its ugly head again. Both booted to a distorted frozen desktop which seemed to be a frame-buffer echo of the vesamenu.c32 splash screen.
Using nouveau.modeset=0, I was however able to get vesa displays and then to switch to NV. Having done that however the show stopper was that the boot time extended to 180 seconds compared to 40 seconds with Precise 5.4.93 k3.8.0 on the same stick!
In order to eliminate syslinux as a possible cause, I also booted from CDs with the same result.

Precise 5.4.93 has been the best experience to date on my particular hardware and I have made some progress with the dual partition approach (fat/f2fs) which I have written up in this thread:
www.murga-linux.com/puppy/viewtopic.php?p=687182#687182_________________Regards ETP

So most likely it this code ? nouveau.modeset=0
So hope next Racy find ways to
fix this nouveau thing?
I tested racy and it booted fine with that code.

I test quirky now that one booted just fine into vesa too
if one use that code and then it suggest one test with
proper driver so please fix that |smile|_________________I use Google Search on Puppy Forum
not an ideal solution thoughLast edited by nooby on Thu 28 Feb 2013, 09:11; edited 2 times in total

Booted fine but unable to create a savefile - don't get asked for either the "Are You Ready" screen or savefile size on 1st reboot and even if location is set by Barry's instruction in his blog the size does not get set - see screenie

This is a "frugal" install on an NTFS drive inside subdirectory test-quirky

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum