Quirky 1.2 feedback

[rcrsn51]

It sounds like the Universal Installer is relying on the disktype command to determine the filesystem on the flash drive. If it gets it wrong, extlinux won't install properly.

FWIW, the blkid command does identify the flash drive correctly in qret. Also, manually installing extlinux onto the flash drive does work.

[npierce]

Looking at the patched source for disktype-9 given in Barry's August 24 blog, disktype-9-patched_pardus_bk.tar.gz, and the new source for disktype-10, disktype-10_cvs20091020.tar.bz2, shows that both versions determine the filesystem type by looking for ext4 features that are not supported by ext3. The code is very different, but the bits tested appear to be the same with one exception: the new code tests the field called "min_extra_isize", but the old code does not.

Apparently, that field is actually used by both ext3 and ext4, so is not a good indication of the filesystem type. In fact, I have a bunch of ext3 partitions; when I run tune2fs -l on any of them I see:

Code: Select all

Required extra isize:     28
Desired extra isize:      28

As it turns out, there is already a patch for this:

http://svn.exactcode.de/t2/trunk/packag ... tfix.patch

[edoc]

Just downloaded and installed Frugal Quirky 1.2 and Wary 030.

Quirky loaded OK except that it, like Lucid 5.01, will not handle xorg on this laptop - so I am forced into Vesa and that annoying flicker

This is a Panasonic Toughbook CF-29 with the Intel 82852/855GM integrated graphics.

[npierce]

The fact that the Universal Installer is identifying your filesystems correctly with Quirky 1.2 but not Quirky-Retro 1.2 would seem to indicate that there may be more going on here than just the need of the patch for disktype.

Perhaps it is also depends upon which version of mkfs.ext3 and/or which kernel was used to create the ext3? Just a guess.

[Gabo]

Hello,

I am using 1.1 Quirky and it is working excellent.
How can i upgrade to 1.2 simply?

Thanks,

Gabó

[edoc]

Hello,

I am using 1.1 Quirky and it is working excellent.
How can i upgrade to 1.2 simply?

Thanks,

Gabó

If your install is Frugal - just copy the three system files from the 1.2 ISO and replace the 1.1 ones.

[nooby]

Sounds interesting way to test new versions of Quirky or Lupu.

Have you tested this?

[edoc]

Sounds interesting way to test new versions of Quirky or Lupu.
Have you tested this?

I installed Wary and Quirky by merely opening the downloaded ISO and copying the three files to "wary" and "qrky" folders, then I modified GRUB menu.lst to make them available at boot.

The only quirk in wary was that one has to specify "hda" instead of "sda" in menu.lst

I see no reason why one may not repeat that process with a new version of either - of course separate folders for the old and new would allow shitching back and forth via reboot - one just needs to add the new menu.lst entry for the new version.

I currently have 4.31, LHP, Quirky, and Wary on this laptop (and WinXP-Pro, but I don't use that).

[nooby]

I misunderstood you.
I thought you meant one could really upgrade using the old pupsavefile but using the upgraded wmlinuz and initrd and quirky120 instead of the Quirky 100 that I already have.

I tested and that totally failed. I renamed the old pupsave file and that did not work either. It too the old one despite being renamed. It ignored the new one when I moved the old one out of reach several layers down.

[edoc]

Are you saying that it is booting Quirky 1.0 and not 1.2?

Did you fix menu.lst to call 1.2 instead of 1.0?

[`f00]

For liveCD multisession..
0) eject the current q110 disc
1) make a new disc for q120 with burniso2cd (q110 still running in RAM)
2) reboot with the q120 disc in and save session - almost all your current personal data from q110 will be saved as the 1st two savedirs on the new disc (follow the prompts)
3) When you get to q120's desktop, use Rox to check /tmp/versioncleanup dir for any personal files or modifications that were displaced in the upgrade process (judgement call here as to whether to use some of these to overwrite Official files)

For frugal installs such as usb (optional if you'd like a q110 fallback etc)..
0) boot with pfix=ram
1) backup and/or copy/rename your savefile (example qrkysave-110.2fs to qrkysave-120.2fs)
2) rename q110's initrd.gz and vmlinuz (example initrd-110.gz and vmlinuz-110), then copy the initrd.gz and vmlinuz from (click to open) q120's iso (or a bootdisc made with burniso2cd if you use one) .. also the main sfs
3) If you select qrkysave-120.2fs at boot, it should go through much the same upgrade process as on the liveCD multisession method
note - if you copy savefiles 'whole', it may help to keep the size small-ish (depending on your setup)

hth and welcome to the plmf, Gabó

@nooby - sometimes I alter a few files to reflect expected DISTRO_SPECS and such in the modified savefile (not truly recommended as it can bypass the upgrade process but useful for some mods).

[nooby]

Thanks guys, I have to look at it later and do more tests. Much appreciated.

[DaveS]

Adobe announced Flash 10.1 today which fixes critical security issue. Highly rec upgrading.

[nooby]

How does one find out if one already have it or not?

[DaveS]

How does one find out if one already have it or not?

Open Seamonkey, then from the menus, select help, about plugins.

[nooby]

Jay, Shockwave Flash 10.1 r53 but I also have 10.0 r42 which most likely is the old one that can be exploited. Do I dare to delete that one then? Hm I give it a try.

One can only disable not delete them So I did disable it. Now I only need to find a good site to test it on.

Edit typical of me that I failed to install it correctly. I need to find your thread where you explain how to set it up correctly.

One has to untar the gz file and place the .so file where?

Wow was not easy for somebody as dense as me but finally I have it going on both SM and FF3.6.3 and the old one deleted from the files.

I tested it here.

Thanks Dave. I am a slow learner and a fast laps of what I just learned. Embarrassing but it may help others that find the thread.
http://www.chemgapedia.de/vsengine/info ... flash.html

I don't think I can test it on Hulu because they sensor Sweden due to copyright things. But http://edition.cnn.com/video/ does work. and youtube and it says me have the 10.1 r53

[DaveS]

One has to untar the gz file and place the .so file where?

/usr/lib/mozilla/plugins. Delete the old one and replace it with the new. Works fine in Quirky.

[Firewave]

I am trying to setup a development installation, but my frugal installs (1.2 and 1.2) on a full install of 1.1 never ask to save the session, so I cannot setup the devx.

Regarding my "lock" issues. I don't even get the configuration screen. No idea what's going on.

Regarding my scanner issues. It turns out, that imageCLASS is the US version of i-SENSYS products and mine is listed. It's also working with the latest sane-backends. I was just connecting the wrong USB cable (there were two identical ones coming from behind the cupboard and I overlooked the other one). Unfortunately the default scans are darker and seem to have some gamma/color issues compared to the default scans I did on Windows, which match the original.

[Bamoset]

I am trying to remaster my Quirky 1.2 live disk using the "Remaster Puppy Live CD" script from Quirky 1.2. The remastered disk does not connect properly to the internet at bootup. The blinky shows activity, but I can't connect to servers on the internet until after I use the Connect Wizard. With both Lupu 501 and 4.3.1, the internet connection is successfully established upon boot. I suspect there have been changes to the file name(s) configuring and activating Eth0 in Quirky 1.2, making it so some of these files are not copied to etc/tmp when the remaster script is run and Customization is selected. So far I haven't figured out what these files are. Can anyone help? Thanks,

Bamoset

[Bamoset]

Deleted double post.