How to boot a "Live USB" with added SFS file? (Solved)

A home for all kinds of Puppy related projects
Post Reply
Message
Author
DrDeaf
Posts: 69
Joined: Sat 30 Dec 2006, 14:10

How to boot a "Live USB" with added SFS file? (Solved)

#1 Post by DrDeaf »

Hello all! First post, new to Fatdog64 (no extensive experience elsewhere either), so here goes...

Just bought a 64 bit notebook (no optical drive) but booting 601 from a Live CD perfectly with no issues. Don't want to carry a USB optical drive, so I have found Grub4Dos works for me to load the ISO CD config from a USB. So far so good, and this is the path I want. I will have a USB resource that I can carry and hopefully use with any 64 bit machine I encounter, as if it was a "Live CD".

I want to maintain a primary boot that is not configured beyond the distro ISO.

Next step is to figure out how to create a pause in the boot sequence where I can load the audio-all-in-one-amd64-10.sfs if the machine I am using merits that. So far, my reading nor my hacking at is has been successful.

Is this possible to do? All suggestions appreciated!
TIA!

DrDeaf
Posts: 69
Joined: Sat 30 Dec 2006, 14:10

Re: (Solved) "Live USB" boot and SFS

#2 Post by DrDeaf »

As stated often in the threads, other puppy foreign tools did not work. Fatdog64 is very different. However, my primary concern was as quoted:
DrDeaf wrote: I want to maintain a primary boot that is not configured beyond the distro ISO.
And, I was able to accomplish that after a bit of hacking. :D

I appreciate the opportunity to post!

User avatar
RSH
Posts: 2397
Joined: Mon 05 Sep 2011, 14:21
Location: Germany

#3 Post by RSH »

Hi.

I've just seen this thread right now at first time.

What you want to do is something I've done in LazY Puppy. I have disabled all options to create the zdrv.sfs on doing a remaster.

Then I've edited the file init in initrd.gz and added boot options to be able to load each and every sfs i want to load at bootup.

Example:

Boot option lpextsfs=lpaudiostudio boots LazY Puppy using LP2_AudioStudio.sfs at bootup. It can also load a sfs at bootup just by giving the sfs's name ---> like: lpextsfs=MyApps.sfs.

The sfs then is loaded at mount point /initrd/pup_z, just like the zdrv.sfs would be (if it would exist).

Code: Select all

#now supporting a boot menu...
# get Option of LazY Puppy 2 Extension SFS's ----------------------------------
# 2012-04-04 RSH
if [ "$lpextsfs" ];then
 for ONELPEXTSFS in `echo -n "$lpextsfs" | tr ',' ' '`
 do
  case $ONELPEXTSFS in
	lpcpext) ZDRVSFS="$LP2_CP_SFS" ;;
	lprshext) ZDRVSFS="$LP2_RSH_SFS" ;;
	lpaudiostudio) ZDRVSFS="$LP2_AUDIO_SFS" ;;
	lpvideostudio) ZDRVSFS="$LP2_VIDEO_SFS" ;;
	lpofficesuite) ZDRVSFS="$LP2_OFFICE_SFS" ;;
	lpkdeofficesuite) ZDRVSFS="$LP2_KDEOFFICE_SFS" ;;
	lpopenofficesuite) ZDRVSFS="$LP2_OPENOFFICE_SFS" ;;
	lplibreofficesuite) ZDRVSFS="$LP2_LIBREOFFICE_SFS" ;;
	lpgraphicssuite) ZDRVSFS="$LP2_GRAPHICS_SFS" ;;
	lpnetworksuite) ZDRVSFS="$LP2_NETWORK_SFS" ;;
	lpwebsuite) ZDRVSFS="$LP2_INTERNET_SFS" ;;
	lpinternetsuite) ZDRVSFS="$LP2_INTERNET_SFS" ;;
	lpmediaplayersuite) ZDRVSFS="$LP2_PLAYER_SFS" ;;
	lplazarusfpcsuite) ZDRVSFS="$LP2_LAZARUS_SFS" ;;
	lptoolboxsuite) ZDRVSFS="$LP2_TOOLS_SFS" ;;
	lputilitysuite) ZDRVSFS="$LP2_UTILITY_SFS" ;;
	lpwinesuite) ZDRVSFS="$LP2_WINE_SFS" ;;
	lpsciencesuite) ZDRVSFS="$LP2_SCIENCE_SFS" ;;
	lptechsuite) ZDRVSFS="$LP2_TECH_SFS" ;;
	lpphytechsuite) ZDRVSFS="$LP2_PHYTECH_SFS" ;;
	lpdevxsuite) ZDRVSFS="$LP2_DEVX_SFS" ;;
	lpdevxgambassuite) ZDRVSFS="$LP2_DEVXGAMBAS_SFS" ;;
	lpkernel) ZDRVSFS="$LP2_KERNEL_SFS" ;;
	nolpextsfs) ZDRVSFS="NoLP2ExtensionSFS" ;;
	lpuser1ext) ZDRVSFS="$LP2_USER1_SFS" ;;
	lpuser2ext) ZDRVSFS="$LP2_USER2_SFS" ;;
	lpuser3ext) ZDRVSFS="$LP2_USER3_SFS" ;;
	lpuser4ext) ZDRVSFS="$LP2_USER4_SFS" ;;
	lpuser5ext) ZDRVSFS="$LP2_USER5_SFS" ;;
	*) if [ "$ONELPEXTSFS" != "" ]; then
		ZDRVSFS="$ONELPEXTSFS"
		else
		ZDRVSFS="NoLP2ExtensionSFS"
	   fi ;;
  esac
 done
fi
# End RSH ---------------------------------------------------------------------
#continuing original file
The Names are defined in DISTRO_SPECS

Code: Select all

#------------------------------------------------------------------------------
# LazY Puppy 2.1 SFS Files boot options
#------------------------------------------------------------------------------
LP2_AUDIO_SFS='LP2_AudioStudio.sfs'
LP2_VIDEO_SFS='LP2_VideoStudio.sfs'
LP2_OFFICE_SFS='LP2_OfficeSuite.sfs'
LP2_GRAPHICS_SFS='LP2_GraphicsSuite.sfs'
LP2_NETWORK_SFS='LP2_Network.sfs'
LP2_INTERNET_SFS='LP2_Internet.sfs'
LP2_WEB_SFS='LP2_Internet.sfs'
LP2_PLAYER_SFS='LP2_MediaPlayer.sfs'
LP2_KDEOFFICE_SFS='LP2_KDEOfficeSuite.sfs'
LP2_OPENOFFICE_SFS='LP2_OpenOfficeSuite.sfs'
LP2_LIBREOFFICE_SFS='LP2_LibreOfficeSuite.sfs'
LP2_LAZARUS_SFS='LP2_LazarusFPCSuite.sfs'
LP2_TOOLS_SFS='LP2_Toolbox.sfs'
LP2_UTILITY_SFS='LP2_Utility.sfs'
LP2_WINE_SFS='LP2_Wine.sfs'
LP2_SCIENCE_SFS='LP2_Science.sfs'
LP2_TECH_SFS='LP2_Tech.sfs'
LP2_PHYTECH_SFS='LP2_PhyTech.sfs'
LP2_DEVX_SFS='LP2_DevX.sfs'
LP2_DEVXGAMBAS_SFS='LP2_DevX_Gambas.sfs'
LP2_KERNEL_SFS='LP2_Kernel26332.sfs'
LP2_USER1_SFS='LP2_UserExtension1.sfs'
LP2_USER2_SFS='LP2_UserExtension2.sfs'
LP2_USER3_SFS='LP2_UserExtension3.sfs'
LP2_USER4_SFS='LP2_UserExtension4.sfs'
LP2_USER5_SFS='LP2_UserExtension5.sfs'
LP2_CP_SFS='LP2_CPsExtension.sfs'
LP2_RSH_SFS='LP2_RSHsExtension.sfs'
#------------------------------------------------------------------------------
# End of modified DISTRO_SPECS for LazY Puppy 2.x
#------------------------------------------------------------------------------
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]

DrDeaf
Posts: 69
Joined: Sat 30 Dec 2006, 14:10

#4 Post by DrDeaf »

Thanks RSH,
RSH wrote:
Then I've edited the file init in initrd.gz and added boot options to be able to load each and every sfs i want to load at bootup.

-------------------
[/code]
Yes, what you describe here is what I was looking for. What you have done is much larger in scope than what I was thinking.

Which brings to mind a question: Is there available somewhere a tutorial or discussion thread on editing the initrd.gz?

In the month I have had this new hardware Fatdog64 came with a new release of 610. I just added that to my 601 so I have both available at boot.

Can you point me to some good tutorial info on initrd.gz functions and mods?
Thanks again!

User avatar
RSH
Posts: 2397
Joined: Mon 05 Sep 2011, 14:21
Location: Germany

#5 Post by RSH »

Hi.

My signature leads to a post containing links to all my programs. There you'll find the Edit-initrd.gz application. A tool to open and edit the initrd.gz ---> it needs the devx loaded to work!

Here is the right-click application: http://murga-linux.com/puppy/viewtopic. ... 126#652126

It's been downloaded and used a lot and the previous (GUI) version has been downloaded 414 times ---> no complaints so far. :D

GUI application is at the end of this post: http://murga-linux.com/puppy/viewtopic. ... 255#575255

To edit the initrd.gz the way I did, search for the line

Code: Select all

#now supporting a boot menu...
in file init. In LazY Puppy's init it is at line 264.

This is the place where I've insert the first code at above post.

I hope such comment is in your init script. If not, send me your script and I'll search for the fitting location to modify.

---

This is how the full DISTRO_SPECS is looking:

Code: Select all

#------------------------------------------------------------------------------
# This is a modified DISTRO_SPECS for LazY Puppy 2.x
# 2012-04-05 RSH
# 2012-07-24 expanded: LP2_NETWORK_SFS, LP2_CP_SFS, LP2_RSH_SFS
#------------------------------------------------------------------------------
#One or more words that identify this distribution:
DISTRO_NAME='LazY Puppy'
#A three-digit numeric value, version number of this distribution:
DISTRO_VERSION='203'
#A two-digit numeric value, minor-version number of this distribution:
DISTRO_MINOR_VERSION=00
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='ubuntu'
#Prefix for some filenames: exs: lupusave.2fs, lupu-528.sfs
DISTRO_FILE_PREFIX='RSHsLP2'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='lucid'
#the kernel pet package used:
DISTRO_KERNEL_PET='linux_kernel-2.6.33.2-tickless_smp_patched-L3.pet'
#16-byte alpha-numeric ID-string appended to vmlinuz, lupu_528.sfs, zl528332.sfs and devx.sfs:
DISTRO_IDSTRING='R203121205134913'
#Puppy default filenames...
# Note, the SFS files below are what the init script in initrd.gz searches for,
# partition, path and actual files loaded, is in PUPSFS and ZDRV in /etc/rc.d/PUPSTATE
# Main SFS for LazY Puppy 2.x
DISTRO_PUPPYSFS='RSHsLP2_203.sfs'
# Extension SFS for LazY Puppy 2.x
DISTRO_ZDRVSFS='RSHsLP2_Extension.sfs'
#------------------------------------------------------------------------------
# LazY Puppy 2.1 SFS Files boot options
#------------------------------------------------------------------------------
LP2_AUDIO_SFS='LP2_AudioStudio.sfs'
LP2_VIDEO_SFS='LP2_VideoStudio.sfs'
LP2_OFFICE_SFS='LP2_OfficeSuite.sfs'
LP2_GRAPHICS_SFS='LP2_GraphicsSuite.sfs'
LP2_NETWORK_SFS='LP2_Network.sfs'
LP2_INTERNET_SFS='LP2_Internet.sfs'
LP2_WEB_SFS='LP2_Internet.sfs'
LP2_PLAYER_SFS='LP2_MediaPlayer.sfs'
LP2_KDEOFFICE_SFS='LP2_KDEOfficeSuite.sfs'
LP2_OPENOFFICE_SFS='LP2_OpenOfficeSuite.sfs'
LP2_LIBREOFFICE_SFS='LP2_LibreOfficeSuite.sfs'
LP2_LAZARUS_SFS='LP2_LazarusFPCSuite.sfs'
LP2_TOOLS_SFS='LP2_Toolbox.sfs'
LP2_UTILITY_SFS='LP2_Utility.sfs'
LP2_WINE_SFS='LP2_Wine.sfs'
LP2_SCIENCE_SFS='LP2_Science.sfs'
LP2_TECH_SFS='LP2_Tech.sfs'
LP2_PHYTECH_SFS='LP2_PhyTech.sfs'
LP2_DEVX_SFS='LP2_DevX.sfs'
LP2_DEVXGAMBAS_SFS='LP2_DevX_Gambas.sfs'
LP2_KERNEL_SFS='LP2_Kernel26332.sfs'
LP2_USER1_SFS='LP2_UserExtension1.sfs'
LP2_USER2_SFS='LP2_UserExtension2.sfs'
LP2_USER3_SFS='LP2_UserExtension3.sfs'
LP2_USER4_SFS='LP2_UserExtension4.sfs'
LP2_USER5_SFS='LP2_UserExtension5.sfs'
LP2_CP_SFS='LP2_CPsExtension.sfs'
LP2_RSH_SFS='LP2_RSHsExtension.sfs'
#------------------------------------------------------------------------------
# End of modified DISTRO_SPECS for LazY Puppy 2.x
#------------------------------------------------------------------------------
Do not edit the DISTRO_IDSTRING in DISTRO_SPECS ---> it's generated automatically at remaster.

If you get option to edit /tmp/etc at remaster process do copy the /etc/DISTRO_SPECS to /tmp/etc/

Here is the original Lucid 528-4 DISTRO_SPECS file:

Code: Select all

#One or more words that identify this distribution:
DISTRO_NAME='Lucid '
#A three-digit numeric value, version number of this distribution:
DISTRO_VERSION=528
#A two-digit numeric value, minor-version number of this distribution:
DISTRO_MINOR_VERSION=00
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='ubuntu'
#Prefix for some filenames: exs: lupusave.2fs, lupu-528.sfs
DISTRO_FILE_PREFIX='lupu'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='lucid'
#the kernel pet package used:
DISTRO_KERNEL_PET='linux_kernel-2.6.33.2-tickless_smp_patched-L3.pet'
#16-byte alpha-numeric ID-string appended to vmlinuz, lupu_528.sfs, zl528332.sfs and devx.sfs:
DISTRO_IDSTRING='l528121019101928'
#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='lupu_528.sfs'
DISTRO_ZDRVSFS='zl528332.sfs'
I think, it's obviously what I've had changed. At editing the files DISTRO_SPECS is opened twice in geany (or leafpad). One is from the initrd.gz, the other is from the running system. Make sure both are saved with equal content.

Inside the remaster script (usually remasterpup2 in Puppy) search for this code (main thing is MKZDRV):

Code: Select all

eval m_16_1=\"$m_16_1\"
Xdialog --wrap --left  --title "$m_01" --default-no --yesno "$m_16_1" 0 0
[ $? -eq 0 ] && MKZDRV="yes" || MKZDRV=""
and disable it (comment it out or remove) and add:

Code: Select all

MKZDRV=""
Also disable or remove the following code:

Code: Select all

if [ "$MKZDRV" = "yes" ]; then
	rm -f $WKGMNTPT/$rebuilddir/$ZDRVSFS 
	mksquashfs /lib $WKGMNTPT/$rebuilddir/$ZDRVSFS -keep-as-directory -e /lib/[^m]* $ANOTHER_REMOVE
	ANOTHER_REMOVE="/lib/modules"
fi
If you get option to edit /tmp/etc at remaster process do copy the /etc/DISTRO_SPECS to /tmp/etc/ ! ! !

I hope I didn't forget anything. Long time ago since I've made a manually remaster - because of the comfortable LazY Remaster Suite. :D

Otherwise come back here. :lol:
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]

User avatar
RSH
Posts: 2397
Joined: Mon 05 Sep 2011, 14:21
Location: Germany

#6 Post by RSH »

Hello DrDeaf.

I have forgot to mention something in my last PM about building a ISO with a graphical boot menu.

I have build (just for fun and testing) earlier this year a LazY Puppy Multiboot DVD that contains all sfs files plus a LazY Puppy Win Installer which contains also all sfs files and installs LazY Puppy frugal with all sfs files in windows.

It was done using the MultiPup CD/DVD Creator by puppyluvr. The thread is here: http://murga-linux.com/puppy/viewtopic. ... 180#483148

First screenshot shows dvd main menu (only LazY Puppy 2.0.1-rc1 n.y.p.)
Second screenshot shows dvd sub menu (boot as LazY Puppy Audio Studio, RAM only)
Third screenshot shows boot sequence of loading LazY Puppy Audio Studio SFS

All running in LazY Puppy from DVD using LazY Puppy Tools (VirtualBox) SFS...

Image

Image

Image

I think this is really interesting because you can put also several puppies onto such CD/DVD.

---

As I mentioned in my PM, I will now work out and test the short form to the above posted codes and be back later here for this.

RSH
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]

User avatar
RSH
Posts: 2397
Joined: Mon 05 Sep 2011, 14:21
Location: Germany

#7 Post by RSH »

Hi.

I have downloaded the FatDog64-Firefox ISO.

Wow.

This has been really a surprise to me. I never have seen that before.

Image

No SFS file and a initrd (not initrd.gz) sized 198 MB. It seems not to be a SFS (tried to rename and then to open) and it seems not be a .GZ file (tried to rename ant to open with the Edit-inird.gz tool). Nothing works.

That's really different. What file type is this intrd?

---

Unfortunately, it looks to me that nothing of the above can be used in FatDog.

I'm sorry.
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]

Post Reply