(old)Puppy Linux Discussion Forum

Hello,
My question doesn't concern directly Grub4DosConfig but Grub4Dos users who perhaps experienced this problem and know how to solve it: the "halt" command doesn't work at all. I can reboot without any problem but not shutdown my computer using this "halt" command from my USB flash drive menu.lst entry...

Thank you for you attention.

Cordialement.

Updated:
grub4dos-0.4.4.v1.9.3.pet (2018-08-03)
http://shinobar.server-on.net/puppy/opt/

#2018-08-03 v1.9.3: fix chain loading grub2, always install wee as for mbr, fix for full installed (mavrothal)

Thanks shinobar!
First update in a long time, that is nice.

merci. Grub4Dos is so easy to use ! nice.

Thanks shinobar!

+1
Thanks shinobar!!!!

There is already:

http://distro.ibiblio.org/puppylinux/pe ... v1.9.3.pet dated 11-jun-2018

which is what is included in woof-ce builds....

Some sort of rationalisation is required....

Tnx peebee.

#2018-09-18 v1.9.4: merge woof, fix chain loading grub2, always install wee as for mbr, fix for full installed (mavrothal)
grub4dos-0.4.4.v1.9.4.pet (2018-09-18)
http://shinobar.server-on.net/puppy/opt/

Here is an issue that needs to be known by all and maybe get fixed in Grub4dos Config.

Grub4DOS Error 13, wee 13> due to 64-bit Ext4
http://murga-linux.com/puppy/viewtopic.php?t=111376
This topic has some info on how to work around the problem.

If nothing else, put a warning in Grub4dos config about the issue with Linux ext4 64bit format.

I have modified grub4dosconfig to detect frugal installations of EasyOS. There was also a problem with a frugal installation of Racy Puppy not getting detected:

http://bkhome.org/news/201812/grub4dos- ... asyos.html

I looked into that "64bit ext4" problem, did not come up with a solution. However, Gparted creates 32bit ext4 filesystems, thus avoiding the problem.

Someone more familiar with the grub4dosconfig script code could improve on my hacks. The main thing with EasyOS is that the files are 'vmlinuz', 'easy.sfs' and 'initrd', no versioning in the sfs filename.

Also, I noticed that Puppy frugal installations are only searched for one- or two-deep, whereas EasyOS has no limit. For example, sda1/frugal/amd64/easy/0.9.9 is quite valid.

...Easy doesn't search for the installation at bootup, as the install path is inside 'initrd', see explanation here:

http://bkhome.org/news/201811/automatic ... stall.html

...which means, to determine the release version, you would have to open up 'initrd', however, it is usual to have the version info in the install path, for example sda1/easy/0.9.9
Or, mount easy.sfs and read the etc/DISTRO_SPECS file.

Another thing, Easy does not recognise any of those "pfix=..." parameters. They are not needed. There is a "qfix=..." which can accept "nox", "fsck", "bak" or "new", or a combination comma-delimited.

nox: do not start X
fsck: filesystem check of the working-partition.
bak: rollback to last snapshot.
new: bootup as a pristine first-boot.

...the last one is a radical rollback.

Note also, 'initrd' is a cpio archive, not compressed.
There are some notes how to open up a cpio archive here:

http://bkhome.org/easy/easy-frugal-installation.html

...note, that webpage refers to 'initrd.q', but have renamed that to just 'initrd' in the upcoming release (which will be 0.9.10).

EasyOS 0.9.10 has been released, with Grub4Dos in it:

http://bkhome.org/news/201812/easyos-ve ... eased.html

And there is a new tutorial that explains how to use Grub4Dos:

https://easyos.org/install/easy-frugal- ... ation.html

hi shinobar,

grub4dosconfig line 1910 has a missing space after 'kernel' causing 'find grub2' to fail. should be cheers

666philb wrote:grub4dosconfig line 1910 has a missing space after 'kernel'

Corrected ibiblio noarch version but with SAME NAME so woof-ce builds will need to force a download by deleting the old version....

Tnx 666philb and peebee.
Maybe fixed in v1.9.4.

#2018-09-18 v1.9.4: merge woof, fix chain loading grub2, always install wee as for mbr, fix for full installed (mavrothal)
grub4dos-0.4.4.v1.9.4.pet (2018-09-18)
http://shinobar.server-on.net/puppy/opt/

Hi
is a Grub4Dos TOTALY remover available?
What is to care on if your wish to erase each little trace (what other system parts, BIOS etc, will perhaps found) of it from system?
Kind regards

shinobar wrote:Known issue with 64-bit Ext4 filesystem
Ext4 partitions created by recent Linux make trouble with Grub4Dos.
You can avoid this issue converting the filesystem to 32-bit ext4.

Since grub4dos is default in most puppies, very few users will ever read this warning.
Now that more puppies are 64 bit, 64-ext4 fs may be more common.
Would be nice if g4d config detects this setup, warn the user and either suggest and do the change or bailout and suggest grub2 or a manual fix.

shinobar (in part) wrote:Recent:
grub4dos-0.4.4.v1.9.4.pet (2018-09-18)
http://shinobar.server-on.net/puppy/opt/

Please pardon me. I had moved Puppy directories from /mnt/home/ to mnt/home/Puppys/

grub4dosconfig does not find the Puppys in mnt/home/Puppys/

How can I edit so that it will work?

Thank you.

Sheldon

ls -l /mnt/home/Puppys/
total 24
drwxr-xr-x 3 root root 4096 Dec 21 08:57 bionic
drwxr-xr-x 4 root root 4096 Oct 17 23:29 Buster80
drwxr-xr-x 5 root root 4096 Aug 29 09:26 dingo
drwxr-xr-x 3 root root 4096 Dec 15 08:26 Ermine
drwxr-xr-x 4 root root 4096 Dec 21 05:26 PrecLight
drwxr-xr-x 3 root root 4096 Jul 18 11:07 Stretch75

Hi shinobar,

"I had moved Puppy directories from /mnt/home/ to mnt/home/Puppys/"

grub4dos only searches 2 levels deep: (1) the top of the drives/partitions, and (2) within the folders at the top of the drives/partitions.

Your puppies are now three levels deep; /mnt/home = /mnt/dev_save = /initrd/mnt/dev_save being the top of the drive/partition; ... /Puppys being the folder at the second level and the respective puppy folders --e.g. /mnt/home/Puppys/tahrpup-- being at the 3rd level.

I don't know of any boot command which would enable grub4dos to search deeper; and quick 'google' didn't reveal any. It may require compiling grub4dos to provide that capability. But I could be wrong.

mikeslr)(in part) wrote: I don't know of any boot command which would enable grub4dos to search deeper; and quick 'google' didn't reveal any. It may require compiling grub4dos to provide that capability.

Thanks a lot. I was just hoping that shinobar or someone could think of a change in the script 'grub4dosconfig' to perhaps specify look in a desired directory and its sub-directories.