Another re-write of the "init" script - using OverlayFs?

Under development: PCMCIA, wireless, etc.
Post Reply
Message
Author
gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#121 Post by gyro »

Don't bother trying to boot this using isoBooter, it won't work.
The 'init' script ignores the BOOT_SPECS file. The whole booting from an iso stuff in 'init', needs to be reworked.
gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#122 Post by gyro »

I just tried using this iso with the "UEFI Installer" in Tahrpup 6.0.6, and it failed on 2 accounts.
1. It didn't copy the BOOT_SPECS file from the iso.
2. It didn't provide a "pupsfs" (or "pdrv") boot parameter.
After manually fixing these 2 ommissions, it all worked fine.

This deficency in the installer is not surprising, since in the past neither of these were requirements.

So, this still ends up being a manual frugal install.

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#123 Post by gyro »

I've uploaded an iso delta file of the current version 0.2++, against "artfulpup-17.11+12.iso".

With some help from peebee, I've written a script that creates a patched iso that actually boots.
And now I've produced a delta from "artfulpup-17.11+12.iso" to "artful-overlay-17.11+12.iso".

This is not a release of a new version, rather a test of producing an iso and a delta.
I uploaded it mainly because it represents an iso that actually boots, and the delta is so small (1.8MiB).

Fixing the "init" and utilities to work correctly with actually booting an iso, is what I've been working on since the release of version 0.2.

For what it's worth, here it is.
Download from http://www.fishprogs.software/puppy/ini ... .iso.delta.

Note: My script uses an overlayfs stack to "merge" my mods with the parent iso.
I created a "mods" directory containing the patched files.
Mounted the parent iso on a "release" directory, and copied it's "isolinux.bin" to "mods".
Then mounted an overlay stack on the directory "stack", with "mods" as the read/write directory, and "release" as the lower read-only directory.
I then did a "mkisofs" using the "stack" directory.

gyro

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#124 Post by ally »


gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#125 Post by gyro »

@ally,
Thanks.
gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Release of overlay_init-0.3

#126 Post by gyro »

Release of overlay_init-0.3

Download from http://www.fishprogs.software/puppy/ini ... it-0.3.tar.

There's also a delta for artfulpup-17.11+12.iso http://www.fishprogs.software/puppy/ini ... .iso.delta.
And an untested http://www.fishprogs.software/puppy/ini ... .iso.delta.
I'm open to suggestions for other deltas.

I'm uploading deltas simply because they are so small compared to a full iso.
And I assume that you already have the ".iso" of the Puppy you would like to test.

This release is mainly about support for booting an ".iso", using a multi-session DVD or isoBooter.

Changes:

1. I've reverted pupmode=37 back to pupmode=21.

2. Introduced a pupmode=93. This is what you get when you choose "Archive" as a save mechanism when booting a multi-session DVD.
It's a lot like pupmode=77, only different.
Like pupmode=21, on shutdown, it makes a tar archive of the rw layer in tmpfs.
On reboot it extracts the latest tar image into the empty rw layer in tmpfs.

3. To facilitate item 2, there is a new utility called "dvd-append-files" to write a list of files to a multi-session DVD.
For any other media it will do nothing.
It accepts multiple files, since sometimes "rc.shutdown" has to write a new copy of BOOT_SPECS as well as the tar archive.
It automatically adds a 4 digit number to the provided file names to ensure that the files written to the DVD are unique,
and that the latest will sort as the last filename.
There is also a "dvd-check" utility wich will indicate any problems with the media in a specified device.

4. Both pupmode=21 and pupmode=93 create ".tar.gz" files, to save space, without sacrificing too much time.

5. BOOT_SPECS is now called "${DISTRO_FILE_PREFIX}BOOT_SPECS" e.g. "slackoBOOT_SPECS".
Based on the curtrrent parctice of "${DISTRO_FILE_PREFIX}save" e.g. "slackosave".
This is to provide some uniqueness when it gets written to the root of a device.

6. "init" now supports a default BOOT_SPECS in the "initrd.gz".
This is to enable Puppy non-standard sfs files to be included in first boot, e.g. "overlay_mods.sfs".
This is created by the "overlay-setup" script, and my script to update an iso.

7. "init" now supports the "psavemark=" boot parameter,

8. "init" now runs 'date "+%F %R %z"' after any clock set.
The output of this command ends up in "/initrd/tmp/bootinit.log".

9. "init" will now boot with only 1 sfs file.
For later convenience, this "init" creates a read-only overlay stack of all the sfs files, mounted at "/initrd/pup_sfs".
Unfortunately overlayfs does not support the creation of such a stack with only 1 layer.
This can occur if several of the sfs files get renamed and hence fail to mount, so you are left with only a puppy...sfs.
"init" now handles this situation, and continues the boot, (although booting a modern Puppy without a zdrv is often not pretty).

To try this version, use the same procedure as for overlay_init-0.1,
see http://www.murga-linux.com/puppy/viewto ... 6&start=96.
Please note step 0, things to check before you start.

Note:
I obviously need to make available a utility to generate an overlay iso from a standard iso.
The one I currently use is not very transportable, and depends on "overlayfs" being active, and uses the utilities contained in "overlay_mods.sfs".
So, currently you need a running overlay Puppy to produce an overlay iso.

gyro
Last edited by gyro on Sun 04 Feb 2018, 08:12, edited 3 times in total.

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#127 Post by gyro »

Now that I have released overlay_init-0.3 deltas.
Would you please delete this file as it represents no particular version of overlay_init.
gyro

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: Release of overlay_init-0.3

#128 Post by peebee »

gyro wrote:Release of overlay_init-0.3

And an untested http://www.fishprogs.software/puppy/ini ... .iso.delta.

gyro
Looks good here.....
Attachments
Screenshot.png
(58.03 KiB) Downloaded 362 times
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#129 Post by gyro »

@peebee,
Great, thanks for testing.
gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

mk-overlay-iso script

#130 Post by gyro »

A "mk-overlay-iso" script is attached as "mk-overlay-iso-0.1.gz".

To use:
Download into an empty directory and rename to "mk-overlay-iso".
Download "overlay_init-0.3.tar" into the same directory.
In a console window in this directory, run "mk-overlay-iso /path/to/puppy.iso".
It should produce a "puppy-overlay0.3.iso" file in the same directory.

Unfortunately this version uses "overlayfs" and some utilities in "overlay_mods.sfs", (contained in "overlay_init-0.3.tar").
It will refuse to do anything if these are not available.
If you don't have a running overlay_init-0.3 Puppy, you should be able to use "mk-overlay-iso" if your kernel supports "overlayfs", by issuing a "modprobe overlay" command, and loading "overlay_mods.sfs" with "sfs_load".

I tested this script against "slacko-700-RC3_k4.4.70-PAE_2017-12-10.iso", the resultant iso booted fine under isoBooter.
So I uploaded a delta http://www.fishprogs.software/puppy/ini ... .iso.delta.

gyro
Attachments
mk-overlay-iso-0.1.gz
Fake .gz, simply rename to "mk-overlay-iso"
(2.43 KiB) Downloaded 171 times

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Using an overlay iso with Puppy installers - warning

#131 Post by gyro »

If you generate an overlay iso and try to use it with one of the Puppy install programs to do a frugal install, the result install will probably not boot.
1. The installer probably failed to copy the overlay_mods.sfs to the install directory.
2. The installer did not specify a "psfspart=" boot parameter, (or a "pdev1=", or "pupsfs=" or "pdrv=").
This "init" needs to be told which partition the Puppy is installed on.
This is done by using one of the above boot parameters.
And of course, if the insatll is to a sub-directory, this needs to be specified with a "psfsdir=" boot parameter, (or "psubdir=").

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

isoBooter recommendation

#132 Post by gyro »

If booting an overlay iso using isoBooter, I recommend:

1. Use a 2 partition device.
Partition 1 as vfat for isoBooter.
Partition 2 as Linux partition, for savefolder, e.g. ext4

2. Answer '2' to the "Choose a partition" question.

3. Answer 'n' to the "splash screen" question.
This means grub4dos boots using the Puppy files inside the iso, rather than booting the iso itself.
This provides you with a "kernel" line in "menu.lst", to which you can add boot parameters.

4. Edit the "menu.lst" file and replace "pfix=fsck" with a "TZ=" parameter appropriate to your timezone.
For Queensland, Australia, I add "TZ=AEST-10".

Note: "overlay_mods.sfs" contains a "showTZ" utility which displays a TZ parameter that should be appropriate to your timezone.

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

Release of overlay_init-0.4

#133 Post by gyro »

Release of overlay_init-0.4

Download from http://www.fishprogs.software/puppy/ini ... it-0.4.tar.

There's also a delta for artfulpup-17.11+13.iso http://www.fishprogs.software/puppy/ini ... .iso.delta.
And one for slacko-700-RC3_k4.4.70-PAE_2017-12-10.iso http://www.fishprogs.software/puppy/ini ... .iso.delta.

I'm uploading deltas simply because they are so small compared to a full iso.
And I assume that you already have the ".iso" of the Puppy you would like to test.

This release is just a bug fix release. Only some utilities in "overlay_mods.sfs" have changed.
So if you have a working overlay_init-0.3, you only need to replace "overlay_mods.sfs".

Changes:

1. "saveconfig" -> "Folder" contains a "Default" button which was frequently not shown when it could have been.
The "Default" button is now shown more appropriately.

2. Replaced "overlay-setup" with "overlay-setup-frugal".
It will now update a normal frugal install if it has either,
both "initrd.overlay.gz" and "overlay_mods.sfs" added to it,
or, an "overlay_init-" ".tar" file added to it.
It also does a more complete cleanup of un-needed files.

3. It includes a new "overlay-make-iso" utility.
Open a console in a directory containing only an "overlay_init-0.4.tar" file,
and issue a command like "overlay-make-iso /path/to/puppy-7.iso".
This will produce a new "puppy-overlay0.4-7.iso".

Note on multisession DVD:
I was able to "upgrade" my overlay_init0.3 DVD, with the following:
I used "dvd-append-files" to append the new "overlay_mods.sfs" to the DVD.
This resulted in a file called "overlay_mods-1001.sfs" being written to the DVD.
I then booted the DVD and used "System-SFS manager" to modify the "ABOVE" sfs list,
by removing the "overlay_mods.sfs" entry, and adding "overlay_mods-1001.sfs", (and moving it to the top of the list).
On reboot, it loaded "overlay_mods-1001.sfs", and so became a working overlay_init0.4 DVD.

gyro

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#134 Post by 01micko »

Generated from delta the slacko version, booted fine without any messages without a timezone arg.

Setup timezone, touchpad, wireless, my shares (client side) had a quick browse then, for lack of a working installation tool [ I really should merge f2fs installer and UEFI usb installer and make them overlay compliant and offer ext2,3,4 filesystems ], rebooted and saved the archive back to DVD. Rebooted fine, connected to network and shares working. Everything else saved fine. Posting from said now.

Cheers!
Puppy Linux Blog - contact me for access

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#135 Post by gyro »

@01micko,
Thanks for testing.

That's one of the thiings I like about the "Archive" save mechanism,
when you realise you don't have everything setup for a "Folder" based install,
you can just choose "Archive" and not lose any of the mods you have made.

gyro

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#136 Post by 01micko »

gyro wrote:@01micko,
Thanks for testing.

That's one of the thiings I like about the "Archive" save mechanism,
when you realise you don't have everything setup for a "Folder" based install,
you can just choose "Archive" and not lose any of the mods you have made.

gyro
Yes, very handy.. but we need an easy installer, perhaps to USB for testing anyway.

I have obliged. Seems to work ok, posting from a saved install to ext4 (no journal - to reduce writes).

1. Download the attached file [ 4th revision now available ]
2. run

Code: Select all

gunzip install2usb.gz; chmod 755 install2usb
3. plug in a USB stick that you can totally overwrite; in other words, make sure you have got any valuable data off of it
4. run it from your fav terminal emulator. I use urxvt

Code: Select all

./install2usb
5. if your pup supports f2fs or UEFI then that should be detected
6. choose what filesystem and boot type you want (choices are ext2, ext4-no journal,f2fs and legacy bios, UEFI or both respectively)
7. a summary is displayed; if anything is wrong please cancel out of this prog!
8. sit back and watch for errors
9. if succesful, make sure you can boot from USB and try to boot it, run it and save the session.

NOTE: booting is done from a FAT partition but only Linux partitions are allowed for the saving process at this stage. A 33MB FAT partition is created (labeled 'BOOT' - holds vmlinuz, initrd.gz) and a Linux partition of ext2 or 4 or f2fs (if supported) by choice - holds all the sfs files.

10. NO WARRANTY. BE CAREFUL.

BUGFIXES + FEATURE ADDITIONS
(v2)
* fix typo with f2fs variable
* fix f2fs formatting
* make sure iso gets unmounted
* check USB isn't mounted and abort if so (accidentally wiped my running install FAT partition :oops: )

(v3)
* added @gyro's patch (unpublished)

(v4)
* add ability to specify the label for the boot and system partitions (vfat and linux types respectively)
* bugfix: copy appropriate BOOT_SPECS to initrd,gz
* feature: add P_TZ and P_TZONE vars to TIME_ZONE file (based on running systems timezone) >> initrd.gz
* feature: add ability to use ext2, ext3 and ext4 (existing was ext4[no journal] and f2fs) as well as FAT32 as SYSTEM (ie 'save') partition - please see caveat in 'KNOWN ISSUES')
* fix some mount/umount issues
* code clean up

KNOWN ISSUES
* the image doesn't copy for the boot menu if Grub2-efi doesn't exist. Will be fixed when I make this a pet package
* sometimes the CD doesn't mount for copying files, I think it maybe is a hardware issue on this laptop (intermittent)
* CAVEAT from v4: There seems to be corruption, albeit fairly minor if you believe the start of the error message... ('This is mostly harmless')

Code: Select all

 fsck.fat /dev/sdb1
fsck.fat 3.0.28 (2015-05-16)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  3:53/6d, 4:59/6b, 5:53/66, 6:4c/73, 7:49/2e, 8:4e/66, 9:55/61, 10:58/74
  , 90:fa/0e, 91:fc/1f, 92:31/be, 93:c9/77, 94:8e/7c, 95:d1/ac, 96:bc/22
  , 97:76/c0, 98:7b/74, 99:52/0b, 100:06/56, 101:57/b4, 102:1e/0e, 103:56/bb
  , 104:8e/07, 105:c1/00, 106:b1/cd, 107:26/10, 108:bf/5e, 109:78/eb
  , 110:7b/f0, 111:f3/32, 112:a5/e4, 113:8e/cd, 114:d9/16, 115:bb/cd
  , 116:78/19, 117:00/eb, 118:0f/fe, 119:b4/54, 120:37/68, 121:0f/69
  , 122:a0/73, 123:56/20, 124:20/69, 125:d2/73, 126:78/20, 127:1b/6e
  , 128:31/6f, 129:c0/74, 130:b1/20, 131:06/61, 132:89/20, 133:3f/62
  , 134:89/6f, 135:47/6f, 136:02/74, 137:f3/61, 138:64/62, 139:a5/6c
  , 140:8a/65, 141:0e/20, 142:18/64, 143:7c/69, 144:88/73, 145:4d/6b
  , 146:f8/2e, 147:50/20, 148:50/20, 150:50/6c, 151:cd/65, 152:13/61
  , 153:eb/73, 154:62/65, 155:8b/20, 156:55/69, 157:aa/6e, 158:8b/73
  , 159:75/65, 160:a8/72, 161:c1/74, 162:ee/20, 163:04/61, 164:01/20
  , 165:f2/62, 166:83/6f, 167:fa/6f, 168:4f/74, 169:76/61, 170:31/62
  , 171:81/6c, 172:fa/65, 173:b2/20, 174:07/66, 175:73/6c, 176:2b/6f
  , 177:f6/70, 178:45/70, 179:b4/79, 180:7f/20, 181:75/61, 182:25/6e
  , 183:38/64, 184:4d/0d, 185:b8/0a, 186:74/70, 187:20/72, 188:66/65
  , 189:3d/73, 190:21/73, 191:47/20, 192:50/61, 193:54/6e, 194:75/79
  , 195:10/20, 196:80/6b, 197:7d/65, 198:b8/79, 199:ed/20, 200:75/74
  , 201:0a/6f, 202:66/20, 203:ff/74, 204:75/72, 205:ec/79, 206:66/20
  , 207:ff/61, 208:75/67, 209:e8/61, 210:eb/69, 211:0f/6e, 212:51/20
  , 213:51/2e, 214:66/2e, 215:ff/2e, 216:75/20, 217:bc/0d, 218:eb/0a
  , 219:07/00, 220:51/00, 221:51/00, 222:66/00, 223:ff/00, 224:36/00
  , 225:1c/00, 226:7c/00, 227:b4/00, 228:08/00, 229:e8/00, 230:e9/00
  , 232:72/00, 233:13/00, 234:20/00, 235:e4/00, 236:75/00, 237:0f/00
  , 238:c1/00, 239:ea/00, 240:08/00, 241:42/00, 242:89/00, 243:16/00
  , 244:1a/00, 245:7c/00, 246:83/00, 247:e1/00, 248:3f/00, 249:89/00
  , 250:0e/00, 251:18/00, 252:7c/00, 253:fb/00, 254:bb/00, 255:aa/00
  , 256:55/00, 257:b4/00, 258:41/00, 259:e8/00, 260:cb/00, 262:72/00
  , 263:10/00, 264:81/00, 265:fb/00, 266:55/00, 267:aa/00, 268:75/00
  , 269:0a/00, 270:f6/00, 271:c1/00, 272:01/00, 273:74/00, 274:05/00
  , 275:c6/00, 276:06/00, 277:46/00, 278:7d/00, 280:66/00, 281:b8/00
  , 282:85/00, 283:55/00, 286:66/00, 287:ba/00, 292:bb/00, 294:80/00
  , 295:e8/00, 296:0e/00, 298:66/00, 299:81/00, 300:3e/00, 301:1c/00
  , 302:80/00, 303:a1/00, 304:f3/00, 305:42/00, 306:6f/00, 307:75/00
  , 308:74/00, 309:e9/00, 310:f8/00, 311:02/00, 312:66/00, 313:03/00
  , 314:06/00, 315:60/00, 316:7b/00, 317:66/00, 318:13/00, 319:16/00
  , 320:64/00, 321:7b/00, 322:b9/00, 323:10/00, 325:eb/00, 326:2b/00
  , 327:66/00, 328:52/00, 329:66/00, 330:50/00, 331:06/00, 332:53/00
  , 333:6a/00, 334:01/00, 335:6a/00, 336:10/00, 337:89/00, 338:e6/00
  , 339:66/00, 340:60/00, 341:b4/00, 342:42/00, 343:e8/00, 344:77/00
  , 346:66/00, 347:61/00, 348:8d/00, 349:64/00, 350:10/00, 351:72/00
  , 352:01/00, 353:c3/00, 354:66/00, 355:60/00, 356:31/00, 357:c0/00
  , 358:e8/00, 359:68/00, 361:66/00, 362:61/00, 363:e2/00, 364:da/00
  , 365:c6/00, 366:06/00, 367:46/00, 368:7d/00, 369:2b/00, 370:66/00
  , 371:60/00, 372:66/00, 373:0f/00, 374:b7/00, 375:36/00, 376:18/00
  , 377:7c/00, 378:66/00, 379:0f/00, 380:b7/00, 381:3e/00, 382:1a/00
  , 383:7c/00, 384:66/00, 385:f7/00, 386:f6/00, 387:31/00, 388:c9/00
  , 389:87/00, 390:ca/00, 391:66/00, 392:f7/00, 393:f7/00, 394:66/00
  , 395:3d/00, 396:ff/00, 397:03/00, 400:77/00, 401:17/00, 402:c0/00
  , 403:e4/00, 404:06/00, 405:41/00, 406:08/00, 407:e1/00, 408:88/00
  , 409:c5/00, 410:88/00, 411:d6/00, 412:b8/00, 413:01/00, 414:02/00
  , 415:e8/00, 416:2f/00, 418:66/00, 419:61/00, 420:72/00, 421:01/00
  , 422:c3/00, 423:e2/00, 424:c9/00, 425:31/00, 426:f6/00, 427:8e/00
  , 428:d6/00, 429:bc/00, 430:68/00, 431:7b/00, 432:8e/00, 433:de/00
  , 434:66/00, 435:8f/00, 436:06/00, 437:78/00, 439:be/00, 440:da/00
  , 441:7d/00, 442:ac/00, 443:20/00, 444:c0/00, 445:74/00, 446:09/00
  , 447:b4/00, 448:0e/00, 449:bb/00, 450:07/00, 452:cd/00, 453:10/00
  , 454:eb/00, 455:f2/00, 456:31/00, 457:c0/00, 458:cd/00, 459:16/00
  , 460:cd/00, 461:19/00, 462:f4/00, 463:eb/00, 464:fd/00, 465:8a/00
  , 466:16/00, 467:74/00, 468:7b/00, 469:06/00, 470:cd/00, 471:13/00
  , 472:07/00, 473:c3/00, 474:42/00, 475:6f/00, 476:6f/00, 477:74/00
  , 478:20/00, 479:65/00, 480:72/00, 481:72/00, 482:6f/00, 483:72/00
  , 484:0d/00, 485:0a/00, 504:fe/00, 505:02/00, 506:b2/00, 507:3e/00
  , 508:18/00, 509:37/00
  1) Copy original to backup
  2) Copy backup to original
  3) No action
  ?
	# option 1 works well, which indicates the backup is somehow corrupted.
So there is a work around in v4 that takes care of this issue until a real solution is found, which will be the topic of another thread in the near future. It should be noted that this issue is old in that exists in my old uefi and f2fs flash drive installer programs that both used the gparted GUI. While the 4th revision should be 'safe' there will be no next version until this issue is solved. Bear in mind this is experimental so use AT YOUR OWN RISK.
* this script is somewhat dependent on @gyro's vision of overlay in Puppy Linux. That may or may not change in the future.
Attachments
install2usb.gz
revision 4
(7.88 KiB) Downloaded 232 times
Last edited by 01micko on Tue 06 Mar 2018, 12:01, edited 3 times in total.
Puppy Linux Blog - contact me for access

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#137 Post by 01micko »

I tried the second revision of install2usb on my slacko64 overlay install (upgraded from 0.2 to 0.4 without issue it seems) because that way I can test the UEFI feature. The installation went without error.

I booted it in my wife's macbook-air and got the grub2 screen and proceeded to boot. Booted, connected to wifi and a few other tweaks were made and saving to the second partition worked fine, except for an 'overlay failed to mount at /' error on shutdown. It might be this kernel (4.9.73 64 bit). I don't know but it doesn't seem to affect anything. I rebooted fine.

Subsequent shutdowns and reboots do not show the overlay error.

Cheers!
Puppy Linux Blog - contact me for access

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#138 Post by gyro »

01micko wrote:I booted it in my wife's macbook-air and got the grub2 screen and proceeded to boot. Booted, connected to wifi and a few other tweaks were made and saving to the second partition worked fine, except for an 'overlay failed to mount at /' error on shutdown. It might be this kernel (4.9.73 64 bit). I don't know but it doesn't seem to affect anything. I rebooted fine.
That would be an attempt to remount the main overlay as "ro".
If there's no complaints from "fsck" on the subsequent boot, then no problem.
In the "normal" rc.shutdown, these kinds of remounts are redirectd to /dev/null, so it's display could be seen as being residule "debug".

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#139 Post by gyro »

01micko wrote:Yes, very handy.. but we need an easy installer, perhaps to USB for testing anyway.

I have obliged. Seems to work ok, posting from a saved install to ext4 (no journal - to reduce writes).
Thanks, I'll try it.

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

01micko's install2usb

#140 Post by gyro »

@01micko,
I've tested a slightly patched version of "install2usb" and it works great in both UEFI, and LEGACY.
Please consider the attached patch file as a suggestion.

The patch file, "install2usb.diff", does 3 things:
1. Overides DISTRO_FILE_PREFIX with data from the name of the target puppy...sfs, so the boot config files reflect the target Puppy, not the host Puppy.
2. Removes the "psave=" parameter from all boot configs.
This is not needed, since the save partition is the same as the sfs partition. And it resuilts in the bootspecs file being stored in the root of partition 2, instead of in the directory with the sfs files.
3. For backwards compatibility, specifies the save partition with "pupsfs=" and the sfs directory with "psubdir=".

Note: If this script were to be aimed at only "overlay_init" then it would be preferable to use "psfspart=" and "psfsdir=" instead of "pupsfs=" and "psubdir=".

Additional features I would like it to have:
1. An option to have a normal ext4 partition, i.e. with journal.
Given the price of USB sticks, I think the "cost" of the journal is good value as insurance against data corruption.
2. An option to specify a label for the Linux partition.
The label on the vfat partition could also be optional and able to be specified.

gyro
Attachments
install2usb.diff.gz
gunzip to produce "install2usb.diff"
(810 Bytes) Downloaded 236 times

Post Reply