Grub2config replaces Grub4Dos

[Governor]

Could you elucidate? This is exactly what I want to do. I want to create a bootable ISO of my current configuration and place it on my Ventoy thumb drive.
Thanks!

BTW: You can remaster where your current system and all of the work you have put in is saved in the new ISO file the remaster creates.

Its an option that should/will work.

[wizard]

@Governor

What Puppy are you using?

wizard

[Clarity]

Use @amethyst's NixOS facility.

@amethyst, have you submitted your package to WoofCE development ?

[Governor]

Code: Select all

▶—— Distro Specifications ——◀

Distro: fossapup64 9.5
Window Manager: JWM v2.4.0
Desktop Start: xwin jwm

Development:
 Bash: 5.0.17
 Geany: 1.35
 Gtkdialog: 0.8.4
 Perl: 5.30.0
 Python: 
 Yad: 0.42.1 (GTK+ 2.24.32)
 --
 busybox: 1.31.0
 dhcpcd: 6.6.2
 Glibc: 2.31
 OpenSSL: 1.1.1f  31 Mar 2020, built on: Mon Apr 20 11:53:50 2020 UTC
 wpa_supplicant: 2.9

▶—— /etc/DISTRO_SPECS ——◀

One or more words that identify this distribution:
 • DISTRO_NAME='fossapup64'

Version number of this distribution:
 • DISTRO_VERSION=9.5

The distro whose binary packages were used to build this distribution:
 • DISTRO_BINARY_COMPAT='ubuntu'

Prefix for some filenames: exs: bionicpup64save.2fs, bionicpup64-7.9.8.sfs
 • DISTRO_FILE_PREFIX='fossapup64'

The version of the distro whose binary packages were used to build this distro:
 • DISTRO_COMPAT_VERSION='focal'

Read by /usr/bin/xwin to bypass Xorg Wizard at first boot:
 • DISTRO_XORG_AUTO='yes'

 • DISTRO_KERNEL_PET='Huge_Kernel'

 • DISTRO_DB_SUBNAME='fossa64'

Multiarch distros, such as Ubuntu, will have this. ex: /usr/lib/i386-linux-gnu, so DISTRO_ARCHDIR=i386-linux-gnu
 • DISTRO_TARGETARCH='x86_64'

NO_MULTIARCH_SYMLINK=1
 • BUILD_FROM_WOOF='testing;2dee7595a;2020-06-19 20:43:24 +1000'

Puppy default filenames...
Note, the 'SFS' files below are what the 'init' script in initrd.gz searches for,
For the partition, path and actual files loaded, see PUPSFS and ZDRV in /etc/rc.d/PUPSTATE
 • DISTRO_PUPPYSFS='puppy_fossapup64_9.5.sfs'

 • DISTRO_ZDRVSFS='zdrv_fossapup64_9.5.sfs'

 • DISTRO_FDRVSFS='fdrv_fossapup64_9.5.sfs'

 • DISTRO_ADRVSFS='adrv_fossapup64_9.5.sfs'

 • DISTRO_YDRVSFS='ydrv_fossapup64_9.5.sfs'

 • DISTRO_PUPPYDATE='Sep 2020'

 • DISTRO_ARCHDIR='x86_64-linux-gnu'


[quote=wizard post_id=115957 time=1712170642 user_id=1282]
@Governor 

What Puppy are you using?

wizard
[/quote]

[wizard]

@Governor

OK, FossaPup64 9.5. As @Clarity suggested, you can use nicOS-Utility-Suite to remaster an ISO, but it takes some manipulating.

I recently posted "remasterme.sh" which also works with FossaPup95:
viewtopic.php?p=115865#p115865

You make a directory, then put the original ISO file and remasterme.sh into it. Run remasterme.sh and carefully follow the instructions. It will make a smaller ISO file than nicOS-Utility-Suite.

wizard

[rockedge]

For remastering we should also revisit the woofy package by @sc0ttman

A simple remaster tool for Puppy Linux.

With Woofy, you can customise and rebuild an ISO file, without having to boot it up.
Just choose your 'base' ISO - the ISO you want to remaster.

Puppy Linux Forum thread: http://www.murga-linux.com/puppy/viewtopic.php?t=57037

Thanks to stu90, iguleder, jemimah, 01micko, shinobar, others...

Go to GitHub repo for info, code and download -> https://github.com/sc0ttj/woofy

[tosim]

Re Woofy DL--Unable to DL from that link. Can you please provide workable link? Thank you.

[rockedge]

@tosim Does this help? Download in ZIP form.

https://github.com/sc0ttj/woofy/archive ... master.zip

Seems the link in the oldforum will need to be repaired!

[Governor]

Woofy looks promising. Unfortunately, it ended up failing when I tried it.

For remastering we should also revisit the woofy package by @sc0ttman

A simple remaster tool for Puppy Linux.

With Woofy, you can customise and rebuild an ISO file, without having to boot it up.
Just choose your 'base' ISO - the ISO you want to remaster.

Puppy Linux Forum thread: http://www.murga-linux.com/puppy/viewtopic.php?t=57037

Thanks to stu90, iguleder, jemimah, 01micko, shinobar, others...

Go to GitHub repo for info, code and download -> https://github.com/sc0ttj/woofy

[rockedge]

It is a definitely older package so not that surprised.

Maybe some tweaking to the code can bring it up to speed.....

[tosim]

rockedge-Thank you. Will check it out tomorrow, hopefully.

[shinobar]

Hi, all! Sorry for my long absent.
I realized you soleved the problems of the grub2config while my absent.
Thank you radky and all the community members.

[radky]

@shinobar

Your return to the forum is very much appreciated.

Any additional adjustments or corrections you may have for grub2config are certainly welcome.

[shinobar]

DOWNLOAD grub2config-2.0.8 (2024-08-27)
from http://shinobar.server-on.net/puppy/opt ... -2.0.8.pet

Update:
grub2config-2.0.8
graphical boot menu layout, ucode.cpio support, drive icon, launch gparted, proceed without 'boot' flag

[peebee]

Am I correct in thinking that Grub2config is only for 64bit systems??

[shinobar]

Am I correct in thinking that Grub2config is only for 64bit systems??

Grub2config supports both 32/64bit, XenialPup-7.5 and later.
See document.

[peebee]

Am I correct in thinking that Grub2config is only for 64bit systems??

Grub2config supports both 32/64bit, XenialPup-7.5 and later.
See document.

Thanks. So it can be placed in Woof-CE NoArch to make it more widely available?

https://github.com/puppylinux-woof-CE/w ... h-official
https://github.com/puppylinux-woof-CE/w ... ges-noarch

[shinobar]

So it can be placed in Woof-CE NoArch to make it more widely available?

I would be happy to do so.

Please consider this one as well.
Frugalinstaller: viewtopic.php?t=12533

[peebee]

Please consider this one as well.
Frugalinstaller: viewtopic.php?t=12533

We already have FrugalPup .......... possibility of overlap / confusion?

[rockedge]

Slowly working on adapting Grub2config-2.0.8 for operation on KLV distro variants. Started with the previous version which works but is also not fully integrated from Puppy Linux to KLV as far as generating proper boot stanza's for KLV because these are not recognized by the program yet.

There is an error appearing in runs of Grub2config-2.0.8 which seems to involve a missing function call:

Code: Select all

/usr/bin/grub2config: line 837: guess_fstype: command not found

around line 837:

Code: Select all

if  [ "$BOOTPART"  ]; then
	TOFS=$(guess_fstype /dev/$BOOTPART) || fatal "Failed to guess_fstype /dev/$BOOTPART"
fi

I can't seem to find any other reference, calls or actual code for guess_fstype

[rockedge]

The function guess_fstype is a busybox applet which is not patched in Void Linux's busybox version.

Once I pulled guess_fstype.falsе.gz
I removed the fake.gz and placed it in /usr/bin, Grub2config worked enough to install a boot loader.

Also I borrowed from NoblePup64 a busybox-1.36_1 which does have both fgconsole and guess_fstype and it works so far and grub2config works when this busybox is used. I do not know the downsides yet

KLV-Airedale version is BusyBox v1.31.0 it has no guess_fstype
KLV-Spectr version is BusyBox v1.35.0 it has no guess_fstype
Puppy Linux NoblePup64 version is BusyBox v1.36.1 it has guess_fstype

[Dry Falls]

guess_fstype:

Code: Select all

#!/bin/ash
#20220619 BarryK https://bkhome.org/news/202206/guessfstype-symlink-removed.html license: GPL version 3 or any later version

## a replacement for the old guess_fstype:
PART="$1"
[ ! "$PART" ] && exit
[ "${PART:0:5}" != "/dev/" ] && exit
FS="$(blkid $PART | tr ' ' '\n' | grep '^TYPE' | cut -f 2 -d '"')"
[ ! "$FS" ] && FS='unknown'
echo "$FS"

This has worked for me.
df

[shinobar]

Minor update.
You need not update if you are using v2.0.8 and have no problem.

DOWNLOAD grub2config-2.0.9 (2024-09-05)
from http://shinobar.server-on.net/puppy/opt ... -2.0.9.pet

#2924-09-05 v2.0.9: gtk2dialog, without guess_fstype

[don570]

I am reading Shinobar explanation
https://shinobar.net/linux/blog/?viewDetailed=00012

Grub2 or Grub4Dos?
Once the installation is complete with the Puppy installer , it will recommend Grub4Dos as the boot loader. Grub4Dos does not support UEFI , which is the standard for recent PCs. This is what the Puppy installer means when it says it does not support UEFI. If you use Grub2Config instead of the recommended Grub4Dos , there will be no problem even if your PC is UEFI.

How to use Grub2Config (if Puppy Linux is installed on the internal HDD)
The boot loader will be installed on the sda ​​drive of the internal HDD , and the partition will be sda1 of fat32. The installed OS will only be searched for on the internal HDD, and the USB memory used for booting will be excluded from the search range.

Where is Grub2Config?
For FossaPup64-9.5 and later Puppy, both Grub2Config for UFI/BIOS and Grub4Dos for BIOS only are available in Menu → Setup .
Grub2Config is not included in BionicPup(64/32)-8.0 and earlier. You will need to download an additional package.
Main body http://shinobar.server-on.net/puppy/opt ... -2.0.2.pet
Japanese translation http://shinobar.server-on.net/puppy/opt ... 0.1-ja.pet

Puppy's built-in Grub3Config-2.0.1 does not handle memory cards with device names such as mmcblk0p1 or nvme0n1p1. In that case, please download and install the above grub2config-2.0.2.pet for the main body only.
BookwormPup64-10.0.7 includes Grub2Config-2.0.2, so no update is necessary. Is

Grub4Dos really unusable?
PC booting will switch from BIOS to UEFI in 2012, so it will be around the time of Windows 8. UEFI supports the partition table GPT, which can handle storage over 2TB.

Most PCs shipped in the last 10 years since 2012 can choose between UEFI and BIOS. If you are in this transitional period and do not plan to use more than 2TB of storage, you can set it to BIOS (sometimes called CMS or Lefacy). Even in that case, Grub4Dos cannot handle the ext4 (64bit) format, so if you want to use it, you will need to format it for Linux in ext3.
So, Grub2Config is fine.

[don570]

Note to Shinobar

I noticed a couple of spelling errors in documents for Grub2config

Screenshot 2024-09-07 14.10.54.png (19.69 KiB) Viewed 708 times

[don570]

When I tried to use Grub2config in Fatdog64 linux I got the following terminal errors

Code: Select all

# grub2config
splash start Searching.
/usr/sbin/grub2config: line 678: gtkdialog-splash: command not found
/usr/sbin/grub2config: line 682: clean_desk_icons: command not found
/usr/sbin/grub2config: line 681: pup_event_frontend_d: command not found
/usr/sbin/grub2config: line 683: roxfiler: command not found
sda|500GB:_ATA_WDC_WD5000AZLX-6
sdb|2000GB:_ATA_HDS722020ALA330
sdc|63.3GB:_Mass_Storage_Device
3
splash end Searching.

[rockedge]

For comparison I ran grub2config-2.0.8_1 in a terminal on a KLV-Boxer which works well enough to install the boot loader and construct a boot menu. If Puppy Linux variants are in the search path it finds them and writes a working menu.lst.

The errors are from looking for Puppy Linux components and not finding them as expected.

For KLV's there is a script: wd_grubconfig that will generate the proper boot stanza's.

Screenshot(16).jpg (53.03 KiB) Viewed 687 times

I would like to somehow combine grub2config and wd_grubconfig. To add in grub2config identifying a KLV and suggesting boot stanza's tailored for Kennel Linux installations as well.

As it is though it is totally usable and easy to manually copy the wd_grubconfig generated boot stanza's over to the grub.cfg and or menu.lst

Even though the terminal shows errors grub2config worked on KLV-Boxer and installed a boot loader and a working menu.

Not the same luck though on a virt-manager libvirt machine. It can't see /dev/vda1, formatted ext3 and the boot flag set, for some reason.

[rockedge]

Seems the errors come from these lines:

Code: Select all

# v2.0.2: parted probing of drive partitions may result in overlapping
# of ROX desktop drive icons, so we should refresh/realign drive icons.
pidof ROX-Filer >/dev/null 2>&1 && ROX_DESKTOP=yes
if [ "$ROX_DESKTOP" ]; then
	gtkdialog-splash -close never -timeout 5 -margin 10 -placement bottom-left -fontsize large -bg goldenrod -text "$(gettext 'Refreshing drive icons')  " &
	killall frontend_startup 2>/dev/null
	killall pup_event_frontend_d 2>/dev/null
	pup_event_frontend_d &
	clean_desk_icons
	roxfiler -p "$HOME/Choices/ROX-Filer/PuppyPin"
fi

So modified to:

Code: Select all

# v2.0.2: parted probing of drive partitions may result in overlapping
# of ROX desktop drive icons, so we should refresh/realign drive icons.
#pidof ROX-Filer >/dev/null 2>&1 && ROX_DESKTOP=yes
#if [ "$ROX_DESKTOP" ]; then
#	gtkdialog-splash -close never -timeout 5 -margin 10 -placement bottom-left -fontsize large -bg goldenrod -text "$(gettext 'Refreshing drive icons')  " &
#	killall frontend_startup 2>/dev/null
#	killall pup_event_frontend_d 2>/dev/null
#	pup_event_frontend_d &
#	clean_desk_icons
#	roxfiler -p "$HOME/Choices/ROX-Filer/PuppyPin"
#fi

which seems to have fixed the terminal output. KLV-Boxer uses JWM and Rox pinboard

[sinc]

Hi All,

I have a computer with only Windows on it and want to set Puppy up as the main OS with only Windows as the backup. So, the install has the normal 3 windows partitions that Windows generates when it installs. I am trying to use Grub2config but cannot get puppy to start after using it. It appears to be searching sda1 however puppy is stored on sda3 (the main windows partition). Any ideas?

[d-pupp]

@sinc I had a similar error with dpup. It's fixed now in dpup but maybe not in bookworm.
Try adding >> pupsfs=your uuid goes here << to the boot stanza
The line should look something like below
kernel /vanilladpup/vmlinuz pupsfs=b226b3de-6248-4c96-9404-##### psubdir=/vanilladpup pmedia=ataflash
Edit I'm using gurb4dos grub2 maybe a bit different

The problem was init is searching in the wrong place for the files. pupsfs will tell it where to look.
In your case you need the uuid of sda3
There is also a psave=UUID for your save folder

It worked for me.