Code: Select all
# syslinux -i -d /boot/syslinux /dev/sdd4
sh: mcopy: command not found
syslinux: failed to create ldlinux.sys
Code: Select all
# syslinux -i -d /boot/syslinux /dev/sdd4
sh: mcopy: command not found
syslinux: failed to create ldlinux.sys
I used this write-quirky-to-partition.sh that I downloaded a fewtronkel wrote: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.
Thanks for the hint Billtoo. I commented out the section that you indicated, but I'm still getting the same error message as before:I commented out this section of the script and the script ran without
error then:
Anything else I can try with the script?. I've already tried replacing f2fs with ext4 but still no joy.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!
I ran the script from sda1 which is ext4, sda2 is also ext4.tronkel wrote:
Anything else I can try with the script?. I've already tried replacing f2fs with ext4 but still no joy.
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'.CHLee wrote:syslinux 5.10 in Quirky 6.0 missing mcopyCode: Select all
# syslinux -i -d /boot/syslinux /dev/sdd4 sh: mcopy: command not found syslinux: failed to create ldlinux.sys
Read my blog, there is a script to install to a HD partition.rameshiyer wrote: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.
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.rameshiyer wrote: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.
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.nooby wrote: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.
Interesting that you had to comment-out that section!Billtoo wrote:I used this write-quirky-to-partition.sh that I downloaded a fewtronkel wrote: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.
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,Monsie wrote: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