Puppy Linux Discussion Forum

Hello Puppers,

I did a frugal install of Fossapup64 9.6 on a 16bit SanDisk flash drive several months ago.
I've forgotten which install program I used.
The machine is a HP Slim Desktop 260-a010 with a hard drive.

The partition labels shown via Gparted are NOT label names that I inserted.

Does this install look correct?

Note: my personal files are kept on the hard drive.

Thank you in advance for your response.

Sky

@Sky Aisling Odd for sure. You had named the LABEL's and yet they are differently indicated by GParted.

Can you use another program to look at the partitions? Can you remove any save file/folder and re-format the USB drive with GParted then run Grub4Dos and manually frugally install Fossapup64?

@rockedge
Yes, in the boot partition sdb1, I labeled it 'Puppy'. I think I left the partition sdb2 label blank.
I'm wondering about the IBA (Intel Boot Agent). Perhaps I'll experiment with turning off the IBA.
https://www.intel.com/content/www/us/en ... ducts.html
edit: I didn't mark IBA in the boot flags. I marked only 'boot'. The IBA was added apparently by the install program?

Thank you rockedge. I'll nose around your suggestions.

Sky

@rockedge
I found this reference in SAVESPEC that matches the numbers in sdb1 and sdb2 partition labels as shown by Gparted.
Perhaps this is a clue?
Sky

@Sky Aisling I see....looking again at the SAVESPEC file parameters ->

SAVESPEC support is now part of woof-ce.
This topic also contains information on the MakeSAVESPEC utility.
MakeSAVESPEC is now at version 6, announced here viewtopic.php?p=50415#p50415.

---------------------------Original post----------------------------
This is the next phase of my testing stuff in the woof-ce 'init-experiment' branch.

I've uploaded spec-UPupGG+D-20.10+0.tar.xz and spec-eslacko64-6.9.9.11.tar.xz to https://www.mediafire.com/folder/ufo1lerdg73j0/savespec

Each of these tar archive files contains an 'initrd.gz' and a 'ydrv...sfs' file for the corresponding Puppy.
These are meant to be replacements for the release file(s).

You can install them with a command like:

Code: Select all

tar xf spec-....tar.xz -U -C /path/to/install/directory

where "spec-....tar.xz" is the appropriate downloaded tar archive file.
But this will clobber any existing files, so don't do that to a production Puppy.

These files contain the latest updates to the woof-ce 'init-experiment' branch.
They provide support for a SAVESPEC file, a bit like a SAVEMARK file on steriods.

In a normal frugal install, 'shutdownconfig' will write a SAVESPEC file to the install directory on first shutdown, if you select either a different partition or a different sub-directory, to the default.
You can also create a SAVESPEC file with a text editor, and place it in the install directory before first boot. This will simplify the dialogs shown by 'shutdownconfig'.

If you are booting a CD/DVD, 'shutdownconfig' can't write a SAVESPEC file to your install directory,
but it is possible to create a SAVESPEC file and write it to an "open" CD/DVD, (one suitable for multisession, pupmode=77).

If you are using 'isoboot', you can generate a SAVESPEC that defines the location for all your save-folders,
and place it in the same directory as the iso files.

A typical SAVESPEC file, defines a partition and a sub-directory e.g.:

Code: Select all

SS_ID='Work'
SS_DIR='/tsaves'

The entire Topic is here -> viewtopic.php?t=1371

A GUI to edit the SAVESPEC file -> viewtopic.php?p=10222#p10222

Some problem encountered -> viewtopic.php?p=89901#p89901

@rockedge

Well, I've wandered through the comments on SAVESPEC you sent.
I note that I put only one frugal Puppy on any Puppy stick I make, no multiple Puppies on a stick, so far anyway.
So, back to the original question: Does this install look ok?
(The OS is running normally so far except for the usual Firefox cache issue which I'm about to fix, but that's another subject.)
If I edit the labels to words that I choose then will my Puppy be struck by lightening?
(It's nice to quickly check a flash drive with Gparted and see which Puppy is on the stick by reading the boot partition label.)
If I leave the labels showing the inserted location by SAVESPEC then "If it ain't broke don't fix it" might apply here?

Sky

If I leave the labels showing the inserted location by SAVESPEC then "If it ain't broke don't fix it" might apply here?

Yes. Exactly, no harm no foul. The system is working to expectations? If so leave it be. It was about understanding why it was doing what it's doing