My report on Quirky 6.0

[CHLee]

syslinux 5.10 in Quirky 6.0 missing mcopy

Code: Select all

# syslinux -i -d /boot/syslinux /dev/sdd4
sh: mcopy: command not found
syslinux: failed to create ldlinux.sys

[tronkel]

Hi Barry,

Still no joy with the amended script. I've tried both Puppy Precise 5.6 as well as Debian Wheezy. Both of these have Busybox installed. The target partition is ext4.

The error output is the same as before and the amended script issues no warnings while using Puppy as the install distro.

There is a warning when using Debian Wheezy as the install distro. Even although the image file and the install script exist in the same folder, the install script nevertheless can't see the image file.

The script does manage to copy over the boot folder containing the vimlinuz file - but nothing else. The rest of the files do not get copied. So, the script is failing just at that point. Can't see where the error is.

[Billtoo]

I needed to compile several other libs + install qt-482, then the
latest VLC compiled successfully.
I'm liking Quirky 6.0 a lot

[rameshiyer]

How to install quirky 6.00 in my hard disk either full or frugal. I am already having several other puppies running in Hard Disk. How to install this quirky.img file in any other partition already available in the hard disk (ext4). Please give the some simple method to install in hard disk.

[Ray MK]

BarryK is working on a method to do exactly that - easy install an image to an existing partition.
It may be known as Quirky-6.1.
Early Xmas maybe ?

[rameshiyer]

I have also tried to install quirky 6.00 by running write-quirky-to-partition.sh. However, it says Quirky image is not available. ( not able to detect Quirky6.00 image file) Even though it was in same folder where sh file is available. I have limited knowledge in linux and also not having any programming skill.

[Billtoo]

I moved my SDHC install to my eeePC 701SD netbook.

Summary
Computer
Processor Intel(R) Celeron(R) M processor 900MHz
Memory 505MB (34MB used)
Machine Type Physical machine
Operating System Quirky - 6.0
User Name root (root)
Date/Time Tue 17 Dec 2013 11:00:28 AM EST
Display
Resolution 640x480 pixels
OpenGL Renderer Unknown
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA Intel
Input Devices
AT Translated Set 2 keyboard
Logitech USB Optical Mouse
SynPS/2 Synaptics TouchPad
Asus EeePC extra buttons
Lid Switch
Sleep Button
Power Button
Power Button
Video Bus
PC Speaker
HDA Digital PCBeep
HDA Intel Headphone
HDA Intel Mic

Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)

I didn't try connecting an external monitor yet.

EDIT:
I connected a 17" external monitor, it's working well.

[eowens2]

I have been able to use BK's scripts and quirky6-6.0.img.xz to install to a f2fs partition using the full space of the USB 16 GB thumb drive.

I began by using ./write-quirky-image-to-drive, writing quirky onto a 16 GB USB thumb drive, leaving about 7 GB of unused space. Rather than adding a third partition (to the FAT16 and f2fs), I deleted the f2fs partition with the root file system. The FAT partition with the bootloader etc I left intact on the drive.

Then I created (with the Gparted version 0.16.2 included in quirky6) a new f2fs partition of 14.88 GB that mostly filled the thumb drive, leaving a little space at the end for the secondary GUID partition table. (This was done with a second functioning copy of Quirky6).

I then used ./write-quirky-to-partition to put the root file system back on to the f2fs partition. BK made some recommended changes for /etc/rc.d/rc.sysinit: I did not make the change at line 152 "DEV1FS='f2fs'", since the partition is still in a f2fs format, but did the change at about line 80 regarding busybox mount.

The system will still not boot yet, because the file SYSLINUX.CFG has the incorrect partition UUID value, and doesn't know where to find the root file system (it is trying to use the UUID value of the original f2fs partition).

To get the new UUID value, do "./gdisk /dev/sdx" where "x" is the thumb drive in question (in my case ./ gdisk /dev/sdc) which will give some preliminary info, and await furthur commands. Enter "i" for detailed information, and enter "2" for the f2fs partition.

Two GUID values will be reported, but the one we need is the one labled "Partition unique GUID". Copy this value and go to the partition 1 (FAT16 partition) and open SYSLINUX.CFG, go to the line "append root=PARTUUID=" and replace the value there with the one copied from gdisk interrogation of the new f2fs partition. Save SYSLINUX.CFG and the system should be bootable. Mine was!

I repeated the above procedure on a 32 GB USB stick (=> a 29.8 f2fs partition) which worked equally well.

[don570]

gimp-quirky-2.6.12 compiled and available

Compiled with old gegl 0.1

If the included python is installed then it will open ORA files
(native format of mypaint)

Unfortunately I couldn't get the g'mic plugins to work

All pets inside gimp-quirky-2.6.12.tar.gz (just install the main pet package
if that is all you need)

http://www.datafilehost.com/d/afdc41a7 31mb

_______________________________________________

I was able to back up a full install using Barry Kauler's Pudd

______________________________________________

[nooby]

Please be patient with an old grumpy Noob.

I am a frugal fanatic so no way I destroy the only ntfs
partition I have with all the other puppies and other
Linux frugal installs that is on that single partition. sda1 the sda2 is for
windows Vista on the Desktop. I need those for upgrading my smartphones
but I never use it other than for that purpose maybe once a year. .

So please make a version that one can manually install
as a standard frugal install that Puppy has worked for many years.

We need mirrors. Dowloads usally take a few minutes
but this one some33 minutes.

[Billtoo]

Hi Barry,

Still no joy with the amended script. I've tried both Puppy Precise 5.6 as well as Debian Wheezy. Both of these have Busybox installed. The target partition is ext4.

The error output is the same as before and the amended script issues no warnings while using Puppy as the install distro.

There is a warning when using Debian Wheezy as the install distro. Even although the image file and the install script exist in the same folder, the install script nevertheless can't see the image file.

The script does manage to copy over the boot folder containing the vimlinuz file - but nothing else. The rest of the files do not get copied. So, the script is failing just at that point. Can't see where the error is.

I used this write-quirky-to-partition.sh that I downloaded a few
minutes ago (dec 18th) from ibiblio.
I commented out this section of the script and the script ran without
error then:

#TESTDIR="`pwd`/write-quirky-to-partition"
# if [ ! -f "$TESTDIR" ];then
# echo
# echo "ERROR!"
# echo "You should have downloaded the Quirky6 compressed image, named
# something like 'quirky6*-img.xz' and it must be in the same folder
# as the script you are now executing. You must have opened a terminal
# in that folder and then executed this script.
# So, the current directory:"
# pwd
# echo "...is wrong. Aborting."
# exit
# fi

The screenshot shows the result, still getting the Seamonkey popup though until Barry's fix is applied.

[Monsie]

Hi all,

I have Quirky installed on a 16 gb flash drive. The install script appears to have formatted the flash drive as f2fs, but it's showing up as two partitions: sdb1 (fat) and sdb2(f2fs). I am not sure if this is the intended outcome or not. Should I have re-formatted the flash drive as ext 2 or ext 3, and then installed Quirky?

I've only begun to look at Quirky, so have not done much testing yet. However, I do want to report that I managed to install Quirky on my Windows laptop. This was out of necessity, because it is my only computer that is capable of booting from a usb drive. Sadly, (perhaps) my linux distros currently run on much older systems. What I did is run debian squeeze in a virtual machine with VMware Player... It all went quite smoothly, except that I found that I had to add the file extension to the shell script when setting permission and then running it, but I guess that is standard in debian.

Cheers,
Monsie

[tronkel]

Billtoo wrote:

I commented out this section of the script and the script ran without
error then:

Thanks for the hint Billtoo. I commented out the section that you indicated, but I'm still getting the same error message as before:

Writing Quirky6 files to sda10...
vmlinuz...
all of Quirky files, please wait...
mount: unknown filesystem type 'f2fs'
cp: cannot stat `mntpt/*': No such file or directory
sed: can't read /mnt/sda10/sbin/init: No such file or directory
sed: can't read /mnt/sda10/etc/rc.d/rc.sysinit: No such file or directory
umount: can't umount mntpt: Invalid argument

That's it, done!

Anything else I can try with the script?. I've already tried replacing f2fs with ext4 but still no joy.

[Billtoo]

Anything else I can try with the script?. I've already tried replacing f2fs with ext4 but still no joy.

I ran the script from sda1 which is ext4, sda2 is also ext4.
I just noticed a new empty folder in hold directory.
I was just sharing what worked for me, other than that I have no more
ideas.
I ran the script from precise 5.7.1 which is a frugal install on sda1.
My hard drive just has the 2 ext4 partitions + a swap partition.
Yours is much more complex so that's beyond me

[BarryK]

syslinux 5.10 in Quirky 6.0 missing mcopy

Code: Select all

# syslinux -i -d /boot/syslinux /dev/sdd4
sh: mcopy: command not found
syslinux: failed to create ldlinux.sys

Yeah, that will be fixed in next release. The "make install" installs the mtools-dependent 'sylinux', but there is a 'syslinux-nomtools' in the source package. Have to manually get that out, rename as 'syslinux'.

Actually, I have rolled back to version 4.05.

5.10 won't load the initial .lss splash image.

I will upload a 4.05 PET soon.

[BarryK]

How to install quirky 6.00 in my hard disk either full or frugal. I am already having several other puppies running in Hard Disk. How to install this quirky.img file in any other partition already available in the hard disk (ext4). Please give the some simple method to install in hard disk.

Read my blog, there is a script to install to a HD partition.
Also read my blog, frugal install is not supported.

[BarryK]

I have also tried to install quirky 6.00 by running write-quirky-to-partition.sh. However, it says Quirky image is not available. ( not able to detect Quirky6.00 image file) Even though it was in same folder where sh file is available. I have limited knowledge in linux and also not having any programming skill.

Are you doing this in a Linux partition? It must not be a ntfs or vfat (Windows/DOS) filesystem. Also must have over 8GB free.

I am working on another script, will try and put more automatic checking into it.

[BarryK]

Please be patient with an old grumpy Noob.

I am a frugal fanatic so no way I destroy the only ntfs
partition I have with all the other puppies and other
Linux frugal installs that is on that single partition. sda1 the sda2 is for
windows Vista on the Desktop. I need those for upgrading my smartphones
but I never use it other than for that purpose maybe once a year. .

So please make a version that one can manually install
as a standard frugal install that Puppy has worked for many years.

We need mirrors. Dowloads usally take a few minutes
but this one some33 minutes.

No, Quirky6 never will do a frugal install. it is not designed that way. it does not work with a layered filesystem, nor does it have a save-file, as in frugal. It is a full Linux installation. Needs an entire HD partition, or you can install to a pluggable external media.

[BarryK]

Hi Barry,

Still no joy with the amended script. I've tried both Puppy Precise 5.6 as well as Debian Wheezy. Both of these have Busybox installed. The target partition is ext4.

The error output is the same as before and the amended script issues no warnings while using Puppy as the install distro.

There is a warning when using Debian Wheezy as the install distro. Even although the image file and the install script exist in the same folder, the install script nevertheless can't see the image file.

The script does manage to copy over the boot folder containing the vimlinuz file - but nothing else. The rest of the files do not get copied. So, the script is failing just at that point. Can't see where the error is.

I used this write-quirky-to-partition.sh that I downloaded a few
minutes ago (dec 18th) from ibiblio.
I commented out this section of the script and the script ran without
error then:

#TESTDIR="`pwd`/write-quirky-to-partition"
# if [ ! -f "$TESTDIR" ];then
# echo
# echo "ERROR!"
# echo "You should have downloaded the Quirky6 compressed image, named
# something like 'quirky6*-img.xz' and it must be in the same folder
# as the script you are now executing. You must have opened a terminal
# in that folder and then executed this script.
# So, the current directory:"
# pwd
# echo "...is wrong. Aborting."
# exit
# fi

The screenshot shows the result, still getting the Seamonkey popup though until Barry's fix is applied.

Interesting that you had to comment-out that section!

Hopefully the new script I am working on will be better in other distros.

[BarryK]

Hi all,

I have Quirky installed on a 16 gb flash drive. The install script appears to have formatted the flash drive as f2fs, but it's showing up as two partitions: sdb1 (fat) and sdb2(f2fs). I am not sure if this is the intended outcome or not. Should I have re-formatted the flash drive as ext 2 or ext 3, and then installed Quirky?

I've only begun to look at Quirky, so have not done much testing yet. However, I do want to report that I managed to install Quirky on my Windows laptop. This was out of necessity, because it is my only computer that is capable of booting from a usb drive. Sadly, (perhaps) my linux distros currently run on much older systems. What I did is run debian squeeze in a virtual machine with VMware Player... It all went quite smoothly, except that I found that I had to add the file extension to the shell script when setting permission and then running it, but I guess that is standard in debian.

Cheers,
Monsie

Monsie,
Yes, two partitions is correct. There is no x86 boot manager that can boot to a f2fs partition, that is why the small vfat partition is required.