VoidPup32 and VoidPup64 Discussion

[N97]

I do not have a file/directory named ucode.cpio in my Voidpup64 22.02.-20241009 (kernel 6.6.53)

[peebee]

I do not have a file/directory named ucode.cpio in my Voidpup64 22.02.-20241009 (kernel 6.6.53)

viewtopic.php?p=9658#p9658

[peebee]

Voidpup64-22.02 has some bugs and omissions that need fixing...

1.) the grub cfg file needs 'insmod fat32'

N97

Thinking about this more - I am wondering why you are the first user to discover this "omission" given that people must have been booting woof-ce pups with grub successfully???

How did you discover this was needed? how were you booting VoidPup64?

[N97]

I might be wrong about fat32 inclusion... i was booting using boot flash --> Grub/GPT UEFI. The os did not run at all. Thats when I noticed that grub.cfg and the boot folder were not transferred to target usb drive from the iso. the insmod fat32 was insurance that the transfer was successful... to no avail apparantly. I left it in my build JIC.

FWIW the computer is x86_64.

[N97]

Given the rolling release, it would be helpful if the 'packages-void-current' file is made available as a separate download. This helps end-users with an older version update to the 'correct' available app version. Its not necessary to D/L the iso and burn/boot it to get this info. Right now... it is.

Thanx
N97

[peebee]

Given the rolling release, it would be helpful if the 'packages-void-current' file is made available as a separate download. This helps end-users with an older version update to the 'correct' available app version. Its not necessary to D/L the iso and burn/boot it to get this info. Right now... it is.

Thanx
N97

Not sure this is a good idea - much better to update all system components to be consistent..... and this would make PPM inconsistent with VPM....

If you do want to do it - download the iso and open it - then open the puppy.sfs and copy from /var/packages - but then why not update all the .sfs??

[N97]

Going back to the bootflash --> GPT/GRUB install bug...
I also tried the Frugal Pup installer e3stickpup. It makes a boot partition, then an ext drive. But wait, there's more...
THEY'RE LOCKED !!! Puppy Jail.

So, theres two BAD options, Broken, or Jail.

NONE suits me. So I did it the old-fashioned way, and now i have a boot partition, an os partition, and a storage partition.
They work great, with usual caveat that its wise to keep a copy of the storage partition on another drive JIC chip fail.
Also periodically update the save file in any/all copies.

To top it off, thrown for a loop when the fiberoptic system went down locally... high wind culprit. A call to ISP revealed snafu. whew... thought i failed.

[N97]

As far as the vpm current file... because not broken, no update. But if an app fails, update the app/dependencies. If theres a security snafu, update the app/dependencies. Further infestation warrants new os version.
It reminds me of diabetics, when the toe gets gangrene, we cut off the foot, not the whole leg.