Quirky April 7.0 - 7.0.3, 7.0.4, 7.0.4.1
@BarryK, sorry for posting under the retired thread.
I have been running Fatdog64 for awhile now, but, decided to give April64 a try.
The Compaq CQ58, which I use, is a UEFI machine. I do not have Window$ l on it. The suggested method of using April64 can not be used.
I have managed to get April64 7.0.3 to boot and operate with UEFI. However, April64 thinks it is running from a CDROM rather than the hard drive partition.
Here is the Grub2 menu entry that works:
I have less than 4 Gigabytes of RAM, so I can not create a save file with the "Save" Button. The "Save" script also does not give an option to save to a hard drive.
I have to tried to use the older script, 4install-quirky-to-partition and april64-7.0.3.usfs.xz to install April64 to a hard disk partition. The installation was successful, but, will not boot. I get a kernel panic.
Here is the Grub2 menu entry that I have tried. I tried several different ways to get it right with no luck.
Any thoughts or suggestions witll be appreciated. Thank you in advance for any help.
I have been running Fatdog64 for awhile now, but, decided to give April64 a try.
The Compaq CQ58, which I use, is a UEFI machine. I do not have Window$ l on it. The suggested method of using April64 can not be used.
I have managed to get April64 7.0.3 to boot and operate with UEFI. However, April64 thinks it is running from a CDROM rather than the hard drive partition.
Here is the Grub2 menu entry that works:
Code: Select all
menuentry "Quirky 7.0.3 Test on sda3" {
search --no-floppy --fs-uuid --set 07fdd8a9-efed-4de1-8b7c-#####
# above line searches for UUID and sets root to device with UUID
# savefile=direct:device:sda3:/fd64save.ext4 normal save file for fd64
# savefile=direct:device:sda3:/fd64save normal save directory only with 620
#
linux /vmlinuz
initrd /initrd.d # first sucess
}
I have to tried to use the older script, 4install-quirky-to-partition and april64-7.0.3.usfs.xz to install April64 to a hard disk partition. The installation was successful, but, will not boot. I get a kernel panic.
Here is the Grub2 menu entry that I have tried. I tried several different ways to get it right with no luck.
Code: Select all
menuentry "Quirky 7.0.3 Test on sda3" {
search --no-floppy --fs-uuid --set 07fdd8a9-efed-4de1-8b7c-d5a8f3530328
# above line searches for UUID and sets root to device with UUID
# savefile=direct:device:sda3:/fd64save.ext4 normal save file for fd64
# savefile=direct:device:sda3:/fd64save normal save directory only with 620
#
linux /boot/vmlinuz root=PARTUUID=52F6159C-4ADE-4F08-BAE7-245CE89C7C2E-03 rootwait rw
# root=UUID=07fdd8a9-efed-4de1-8b7c-d5a8f3530328 rootwait rw
# initrd /initrd.q #from first success, but not needed
}
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
Flags idea
Forum posting problem
Last edited by ETP on Fri 24 Apr 2015, 18:32, edited 1 time in total.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
Flags idea
Forum posting problem
Last edited by ETP on Fri 24 Apr 2015, 18:31, edited 1 time in total.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
Flags idea
RE: Flags idea.
The flag plus logo strikes me as a good idea but IMHO should be
applied to the "Installer/build script" rather than within the produced pup.
For example, select say the interactive "Italian installer" and the relevant code(s)
could be transfered to the build Pup, regardless of the target, which would then boot up
in Italian.
The current idea puts the cart before the horse as the interactive build script is only in English.
The flag plus logo strikes me as a good idea but IMHO should be
applied to the "Installer/build script" rather than within the produced pup.
For example, select say the interactive "Italian installer" and the relevant code(s)
could be transfered to the build Pup, regardless of the target, which would then boot up
in Italian.
The current idea puts the cart before the horse as the interactive build script is only in English.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I have no experience with grub2. Here is an example for a frugal install, for grub4dos:JustGreg wrote:@BarryK, sorry for posting under the retired thread.
I have been running Fatdog64 for awhile now, but, decided to give April64 a try.
The Compaq CQ58, which I use, is a UEFI machine. I do not have Window$ l on it. The suggested method of using April64 can not be used.
I have managed to get April64 7.0.3 to boot and operate with UEFI. However, April64 thinks it is running from a CDROM rather than the hard drive partition.
Here is the Grub2 menu entry that works:I have less than 4 Gigabytes of RAM, so I can not create a save file with the "Save" Button. The "Save" script also does not give an option to save to a hard drive.Code: Select all
menuentry "Quirky 7.0.3 Test on sda3" { search --no-floppy --fs-uuid --set 07fdd8a9-efed-4de1-8b7c-##### # above line searches for UUID and sets root to device with UUID # savefile=direct:device:sda3:/fd64save.ext4 normal save file for fd64 # savefile=direct:device:sda3:/fd64save normal save directory only with 620 # linux /vmlinuz initrd /initrd.d # first sucess }
I have to tried to use the older script, 4install-quirky-to-partition and april64-7.0.3.usfs.xz to install April64 to a hard disk partition. The installation was successful, but, will not boot. I get a kernel panic.
Here is the Grub2 menu entry that I have tried. I tried several different ways to get it right with no luck.Any thoughts or suggestions witll be appreciated. Thank you in advance for any help.Code: Select all
menuentry "Quirky 7.0.3 Test on sda3" { search --no-floppy --fs-uuid --set 07fdd8a9-efed-4de1-8b7c-d5a8f3530328 # above line searches for UUID and sets root to device with UUID # savefile=direct:device:sda3:/fd64save.ext4 normal save file for fd64 # savefile=direct:device:sda3:/fd64save normal save directory only with 620 # linux /boot/vmlinuz root=PARTUUID=52F6159C-4ADE-4F08-BAE7-245CE89C7C2E-03 rootwait rw # root=UUID=07fdd8a9-efed-4de1-8b7c-d5a8f3530328 rootwait rw # initrd /initrd.q #from first success, but not needed }
Code: Select all
title Quirky April64 7.0 (sda7/april64-7.0)
uuid f547d8df-78f1-44db-a84a-600d9e9185cb
kernel /april64-7.0/vmlinuz rootwait rw
initrd /april64-7.0/initrd.q
When you use the Quirky Installer, it hardcodes the install path into initrd.q. That is, the folder name and partition.
So, you must leave it there.
So, you must use the Quirky Installer to do installations.
Quirky is different from Puppy, frugal installs are very limited and only run in RAM. Both live-CD and frugal need a lot of RAM, at least 1.2GB, happier with at least 2GB.
[url]https://bkhome.org/news/[/url]
Hi Barry,
I am studying/reworking the sysinit.
Some initial questions :
- why not use busybox for all programs like ln, mkdir etc ?
- usbfs is not existing in linux kernel , why still use it ?
- busybox mount is buggy right ? I had problems with read only, it should be rw by default, is there any bug report for that ?
- code can be cleaned up...it's not easy I know.
Cheers
I am studying/reworking the sysinit.
Some initial questions :
- why not use busybox for all programs like ln, mkdir etc ?
- usbfs is not existing in linux kernel , why still use it ?
- busybox mount is buggy right ? I had problems with read only, it should be rw by default, is there any bug report for that ?
- code can be cleaned up...it's not easy I know.
Cheers
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
The actual script is /usr/local/install_quirky/install-quirky-to-frugalBarryK wrote:I have no experience with grub2. Here is an example for a frugal install, for grub4dos:JustGreg wrote:@BarryK, sorry for posting under the retired thread.
I have been running Fatdog64 for awhile now, but, decided to give April64 a try.
The Compaq CQ58, which I use, is a UEFI machine. I do not have Window$ l on it. The suggested method of using April64 can not be used.
I have managed to get April64 7.0.3 to boot and operate with UEFI. However, April64 thinks it is running from a CDROM rather than the hard drive partition.
Here is the Grub2 menu entry that works:I have less than 4 Gigabytes of RAM, so I can not create a save file with the "Save" Button. The "Save" script also does not give an option to save to a hard drive.Code: Select all
menuentry "Quirky 7.0.3 Test on sda3" { search --no-floppy --fs-uuid --set 07fdd8a9-efed-4de1-8b7c-##### # above line searches for UUID and sets root to device with UUID # savefile=direct:device:sda3:/fd64save.ext4 normal save file for fd64 # savefile=direct:device:sda3:/fd64save normal save directory only with 620 # linux /vmlinuz initrd /initrd.d # first sucess }
I have to tried to use the older script, 4install-quirky-to-partition and april64-7.0.3.usfs.xz to install April64 to a hard disk partition. The installation was successful, but, will not boot. I get a kernel panic.
Here is the Grub2 menu entry that I have tried. I tried several different ways to get it right with no luck.Any thoughts or suggestions witll be appreciated. Thank you in advance for any help.Code: Select all
menuentry "Quirky 7.0.3 Test on sda3" { search --no-floppy --fs-uuid --set 07fdd8a9-efed-4de1-8b7c-d5a8f3530328 # above line searches for UUID and sets root to device with UUID # savefile=direct:device:sda3:/fd64save.ext4 normal save file for fd64 # savefile=direct:device:sda3:/fd64save normal save directory only with 620 # linux /boot/vmlinuz root=PARTUUID=52F6159C-4ADE-4F08-BAE7-245CE89C7C2E-03 rootwait rw # root=UUID=07fdd8a9-efed-4de1-8b7c-d5a8f3530328 rootwait rw # initrd /initrd.q #from first success, but not needed }
'inird.q' is the correct name.Code: Select all
title Quirky April64 7.0 (sda7/april64-7.0) uuid f547d8df-78f1-44db-a84a-600d9e9185cb kernel /april64-7.0/vmlinuz rootwait rw initrd /april64-7.0/initrd.q
When you use the Quirky Installer, it hardcodes the install path into initrd.q. That is, the folder name and partition.
So, you must leave it there.
So, you must use the Quirky Installer to do installations.
Quirky is different from Puppy, frugal installs are very limited and only run in RAM. Both live-CD and frugal need a lot of RAM, at least 1.2GB, happier with at least 2GB.
initrd.q can be opened up just by clicking on it, so in theory it is possible to manually make any required changes for a manual frugal install.
[url]https://bkhome.org/news/[/url]
JustGreg wrote: Here is the Grub2 menu entry that works:Here is the Grub2 menu entry that I have tried. I tried several different ways to get it right with no luck.Code: Select all
menuentry "Quirky 7.0.3 Test on sda3" { search --no-floppy --fs-uuid --set 07fdd8a9-efed-4de1-8b7c-##### # above line searches for UUID and sets root to device with UUID # savefile=direct:device:sda3:/fd64save.ext4 normal save file for fd64 # savefile=direct:device:sda3:/fd64save normal save directory only with 620 # linux /vmlinuz initrd /initrd.d # first sucess }
Code: Select all
menuentry "Quirky 7.0.3 Test on sda3" { search --no-floppy --fs-uuid --set 07fdd8a9-efed-4de1-8b7c-d5a8f3530328 # above line searches for UUID and sets root to device with UUID # savefile=direct:device:sda3:/fd64save.ext4 normal save file for fd64 # savefile=direct:device:sda3:/fd64save normal save directory only with 620 # linux /boot/vmlinuz root=PARTUUID=52F6159C-4ADE-4F08-BAE7-245CE89C7C2E-03 rootwait rw # root=UUID=07fdd8a9-efed-4de1-8b7c-d5a8f3530328 rootwait rw # initrd /initrd.q #from first success, but not needed }
Looks like you tried a *manual* frugal install first with just vmlinuz and large initrd.q as this will act like a live CD with no save.
For a *real* frugal install, use the install script which creates a small initrd.q and a large q.sfs which is what is saved for persistence.
As for your full install, make sure your PARTUUID is correct. Did you get it from blkid command? Note that the blkid command in Quirky is from busybox and may not give proper PARTUUID in all cases. You can use the blkid from fatdog or another linux which is a separate command, or specify root manually for your /dev/sda3 or wherever it's installed instead of using PARTUUID.
I would like to report a problem I am having with installquirky.amd64.
I am working on a Dell Inspiron 3520, a 64-bit windows 8 laptop with 4 GB of RAM and Secure Boot turned off in the UEFI setup. Running april64-7.0.3, I used installquirky.amd64 to install tahr-6.0.5.usfs.xz to a usb thumb drive, and the process proceeded smoothly with no errors reported.
Trying to boot the newly installed USB stick, tapping F12 on boot, I chose the “UEFI SanDisk Cruzer 1.27
I am working on a Dell Inspiron 3520, a 64-bit windows 8 laptop with 4 GB of RAM and Secure Boot turned off in the UEFI setup. Running april64-7.0.3, I used installquirky.amd64 to install tahr-6.0.5.usfs.xz to a usb thumb drive, and the process proceeded smoothly with no errors reported.
Trying to boot the newly installed USB stick, tapping F12 on boot, I chose the “UEFI SanDisk Cruzer 1.27
- in sysinit, as far as I can see, all functions can be replaced by their busybox equivalent.BarryK wrote:Many busybox applets lack needed options/functionality.
busybox mount works fine for me.
- busybox mount should be RW by default when I read the man page, and it's not.
- (As side note : did you try to use busybox ash everywhere instead of bash ?)
BarryK wrote: initrd.q can be opened up just by clicking on it, so in theory it is possible to manually make any required changes for a manual frugal install.
Very nice! I never even thought to click on it, but wondered why it had the Quirky icon, should have known it was something special.
Easy one click editing/saving of initrd.q and confirmed that I can move a frugal install to different directory and partition post install just by editing BOOT_SPECS file.
Also tried on my Win8 UEFI tablet, which previously refused to boot frugal mode off the flash drive.(kernel panic) Tried the BOOT_SPECS fix but didn't work. Then modified init to add a 3 sec delay before the mount of tmpmntpt, and it worked!
Don't know if other systems may need some delay for flash drive booting, or if any revision to init is needed, but it worked in my case.
- xanad
- Posts: 400
- Joined: Fri 28 Feb 2014, 14:56
- Location: 2 locations: MonteRosa Alp and Milano
- Contact:
i18n Quirky 7.0.3 italian langpack
Hi Barry,
I read your message and sorry for the inconvenience, this is an italian langpack without executables:
i18n Quirky 7.0.3 italian langpack
https://drive.google.com/file/d/0Bz9e78 ... sp=sharing
-----
A curiosity, where can I find a list of the 64bit executables, used by Quirky 7.0.3?
I read your message and sorry for the inconvenience, this is an italian langpack without executables:
i18n Quirky 7.0.3 italian langpack
https://drive.google.com/file/d/0Bz9e78 ... sp=sharing
-----
A curiosity, where can I find a list of the 64bit executables, used by Quirky 7.0.3?
[url]http://www.xanad.tk[/url] Html5 Parallax
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: i18n Quirky 7.0.3 italian langpack
Thanks.xanad wrote:Hi Barry,
I read your message and sorry for the inconvenience, this is an italian langpack without executables:
i18n Quirky 7.0.3 italian langpack
https://drive.google.com/file/d/0Bz9e78 ... sp=sharing
-----
A curiosity, where can I find a list of the 64bit executables, used by Quirky 7.0.3?
Well, I am hoping to get them all internationalised, so it won't be necessary for any to be substituted.
I need to do a check before I release 7.0.4, that all are converted.
Note, it it easy to check in Quirky 7.0.3+ what binary executables are internationalized. Look in /usr/share/doc/nls -- I have tried to put all required .pot files in here, does not need the 'devx' pet loaded.
This is what is there now:
freememapplet_tray
gfnrename
gmeasures
jwm
network_tray
notecase
powerapplet_tray
proxy-setup
pupradio
retrovol
ROX-Filer
vobcopy
welcome1stboot
xarchive
EDIT: the collection of .pot files will be more complete in 7.0.4
EDIT AGAIN: Um, no. They are all the .pot files that got installed in T2. I really need to modify T2 so that every package build also installs its .pot file. That is a lot of work to implement, have to postpone that.
Last edited by BarryK on Sun 26 Apr 2015, 09:15, edited 3 times in total.
[url]https://bkhome.org/news/[/url]
- xanad
- Posts: 400
- Joined: Fri 28 Feb 2014, 14:56
- Location: 2 locations: MonteRosa Alp and Milano
- Contact:
Re: i18n Quirky 7.0.3 italian langpack
okBarryK wrote: Well, I am hoping to get them all internationalised, so it won't be necessary for any to be substituted.
I need to do a check before I release 7.0.4, that all are converted.
Note: http://murga-linux.com/puppy/viewtopic.php?t=83633
this is also a my langpack,started by vicmz only for Precise 571
[url]http://www.xanad.tk[/url] Html5 Parallax