T.O.P.L.E.S.S. Version 1.0.1 - now available !!!

[LazY Puppy]

T.O.P.L.E.S.S. introduction

Hi,

I'm now going to introduce T.O.P.L.E.S.S.,

a (T)opless (O)rganizing & (P)uppy (L)inux (E)xpanding (S)FS-P.L.U.S. (S)ervice

T.O.P.L.E.S.S. is much more than just a ToolBox. T.O.P.L.E.S.S. is a Multi-Language Puppy Linux Wrapper.

The T.O.P.L.E.S.S. Method allows you to run a WoofCE/JWM Puppy Linux without to use a save file and it will give to you: the benefits of personalisation plus the benefits of persistent settings plus also the benefits of pristine non-persistence - all together, when ever you'll boot a T.O.P.L.E.S.S. LazY Puppy 5!

A T.O.P.L.E.S.S. LazY Puppy 5 is getting personalised during the boot process by its config files and its extended functions are performed by the pile of available T.O.P.L.E.S.S. System SFS Modules (.sfs).

This means you could have one single frugal install of a Puppy Linux that can be personalised in many different ways - just by the use of the .cfg file/s. That's just an easy method and a pretty cool way to setup a personal Puppy Linux for everyone in your family. No save file and no remaster necessary at all!

It is pretty similar to SFS based LazY Puppy or L.A.S.S.I.E. and has been tested successfully in these Puppies: Slacko 5.9.3, Slacko 64 5.9.1, Slacko 64 6.3.0, Tahr 6.0.2 CE, Tahr 6.0.5 CE, Tahr 64 6.0.2 CE, Tahr 64 6.0.4 CE, Tahr 64 6.0.5 CE, Unicorn 6.0, Vivid beta2 - and it should work also on newer versions of those Puppies listed. But for newer Slackos it probably needs some small tweaks in the future.

All the work done in T.O.P.L.E.S.S. is mainly based on my work done on: LazY Puppy, L.A.S.S.I.E., SARA B., SFS P.L.U.S., RoxApp Builder, PaDS, A vote for a modular use of Puppy Linux and Editing the initrd.gz. All resulting Programs and Tools are combined into T.O.P.L.E.S.S. and them are either based on SFS Modules or available as RoxApp Directories - though some may come as scripts.

There are also multiple new Menu Pipes to external (at boot and/or parallel partition) files, scripts, RoxApps, Portables for Linux and Wine (run a Windows executable just by clicking its menu entry), partitions of boot drive and directories; also to SFS Modules at boot directory, Modules directory and already loaded SFS Modules (unload by clicking its menu entry).

A T.O.P.L.E.S.S. LazY Puppy is easy to build just by drag 'n' drop and completely controlled by two different Configuration Files. Just drag 'n' drop the initrd.gz file onto the T.O.P.L.E.S.S. RoxApp Directory and your Puppy will be immediately bootable as a pre-configured LazY Puppy 5 - at least after the initrd.gz was modified which could take a few minutes first time doing it on slow usb flash drives.

Read about the config files at next post.

Note: in all following posts I will use tahr 6.0.2 when giving examples for names etc. but descriptions will be equal to all puppies listed above.

Before trying to use T.O.P.L.E.S.S. read all posts linked below carefully and follow exactly its instructions

1. T.O.P.L.E.S.S. introduction & default wallpaper
2. The T.O.P.L.E.S.S. Configuration Files
3. Setup a T.O.P.L.E.S.S. LazY Puppy easily
4. The T.O.P.L.E.S.S. System SFS Modules
5. Save settings back to T.O.P.L.E.S.S. System SFS Modules
6. Special benefit of T.O.P.L.E.S.S. to users & developers
7. T.O.P.L.E.S.S. requirements and how to install
8, Last steps before booting a T.O.P.L.E.S.S. LazY Puppy 5
9. Special treatment of Precise and Super Lucid for T.O.P.L.E.S.S..
10. Package content and download of T.O.P.L.E.S.S.
11. First steps after booting a T.O.P.L.E.S.S. LazY Puppy 5
12. Booting into different Languages

Attached fix for T.O.P.L.E.S.S. 1.0.0 removed - not needed anymore.
Attached T.O.P.L.E.S.S. 1.0.0 default Wallpaper removed - has changed now.

Look down below from here for the new Wallpapers.

Note 1: installation on vfat partitions is not supported anymore!
Note 2: Precise and SuLu are not supported anymore!

New TOPLESS 1.0.1 starts here.
Information in posts below here are still active and up to date (almost all?)!
A few of them have been updated.

A LazY Puppy 5 based on Tahr 6.0.2 and T.O.P.L.E.S.S. 1.0.2 is here.

[LazY Puppy]

The T.O.P.L.E.S.S. Configuration Files

To have control over a T.O.P.L.E.S.S. LazY Puppy 5 there are two different configurations files. The 1st config file is made to set some options for Puppy already at boot up. The 2nd config file is made to define paths, sfs modules and similar things for a later use.

The 1st configuration file:
(this is the main config file for boot up)

Name-Specification:

$DISTRO_FILE_PREFIX_$DISTRO_VERSION.cfg
It can have additions (free to define) to the file name.
Example: $DISTRO_FILE_PREFIX_$DISTRO_VERSION-monday.cfg
So in this here case: tahr_6.0.2.cfg or even tahr_6.0.2-monday.cfg

Usage:

Boot Parameter setup for a use: pconfig

- pconfig=no (or No or NO or n or N) ---> don't load a config file
- pconfig=monday --> loads the $DISTRO_FILE_PREFIX_$DISTRO_VERSION-monday.cfg
- no pconfig submitted loads the default config, which is: tahr_6.0.2.cfg

Options to setup:

Window Manager, Themes (gtk, icon, wm, audio), Num Lock on/off, Interface, Timezone, Keyboard Layout, Global Font Size, Add a swap to (Z)RAM, Mount all HD and USB Flash Drives, List of Drives to mount, Welcome First Boot on/off, Personal Settings PopUp on/off, Desktop Icons on/off, Drive Icons on/off, Wallpaper, Startup Sound, Install Packages, Global Directory to load SFS Modules from, Load SFS Modules to a top layer, Auto-Load of SFS Modules at /etc/profile.local, Auto-Load of SFS Modules at /root/Startup, Auto-Start of Applications, Auto-Start of Applications from a list file, Menu Pipes on/off, Execute a Startup Script, Execute a external file in /etc/profile.local to set new Global Environment Variables.

The 2nd configuration file:
(this is the sub config file for a use after X started)

Name-Specification:

DISTRO_CONFIG_PREFIX='lped.cfg' (LazY Puppy External Directories)
DISTRO_CONFIG_FILE="$DISTRO_FILE_PREFIX.$DISTRO_VERSION.$DISTRO_CONFIG_PREFIX"

So this will be tahr.6.0.2.lped.cfg

Usage:

Boot Parameter setup for a use: lpconfigfile

- lpconfigfile=yes (or Yes or YES or y or Y) ---> load default config file
- lpconfigfile=monday.cfg --> loads the $DISTRO_FILE_PREFIX.$DISTRO_VERSION-monday.cfg
- no lpconfigfile submitted loads the default config, which is: tahr.6.0.2.lped.cfg

Options to setup:

Paths to external Files, Directories, Scripts, RoxApps, Linux Binaries, PortableApps and Installers for Wine - the Menu Pipes are referring to these paths.

If this sub config file is not to be found, there will be a search for file lped at boot partition and this will be used, if it was found at boot partition. At least, if you don't have a sub config file, the file lped should be available at boot partition (just like a fall-back-file) !!!

Note: after X is running both configuration files will be existing in /etc and its content is read out from /etc in T.O.P.L.E.S.S. programs and scripts.

Besides these two configuration files there are two more files that can setup a T.O.P.L.E.S.S. LazY Puppy either at boot up (from within /etc/profile.local) and/or after X is running. These files can be edited when ever needed and its content will be executed immediately at next boot. No need to do a remaster or to edit the initrd.gz.

Read about these two files at next post.

[LazY Puppy]

Setup a T.O.P.L.E.S.S. LazY Puppy easily

One can setup a T.O.P.L.E.S.S. LazY Puppy either at boot up and/or after X is running. For this to do there are two files created. The first one will contain code that will be executed from within /etc/profile.local. The second one will contain code that is executed from /root/Startup (ready made for the xdg exec of .desktop files in newer Puppies instead of using scripts from /root/Startup).

The 1st setup file:
(this is the main setup file for boot up)

Name-Specification:

$DISTRO_FILE_PREFIX_$DISTRO_VERSION-etc.profile.local
So in this here case: tahr_6.0.2-etc.profile.local

The name of this file also is free to define in $DISTRO_FILE_PREFIX_$DISTRO_VERSION.cfg etc. if there is a need for different files to execute from within /etc/profile.local by different main config files.

By default this will set two paths as Global Environment Variables and gives access to the RSH's Puppy Scripting Library - which is also part of T.O.P.L.E.S.S.. Just add anything you want to be executed at /etc/profile.local to the User Section of this file. Though be careful. You should somehow know what you're trying to achive...

The 2nd setup file:
(this is the sub setup file for /root/Startup)

Name-Specification:

It's name is free to define in $DISTRO_FILE_PREFIX_$DISTRO_VERSION.cfg etc.

So in this here case: tahr_6.0.2.cfg or even tahr_6.0.2-monday.cfg

By default this is set to: StartUp

As there is nothing built into a Puppy Linux that is used by the main config, sub config, main setup and sub setup files of T.O.P.L.E.S.S., there is a need to have some more sources available to get this all working together properly. All of these sources (binaries, data, programs and scripts) are built into SFS Modules - the T.O.P.L.E.S.S. System SFS Modules.

Read about the T.O.P.L.E.S.S. System SFS Modules at next post.

[LazY Puppy]

The T.O.P.L.E.S.S. System SFS Modules

To make all settings (done in main config, sub config, main setup and sub setup files) recognized by the T.O.P.L.E.S.S. LazY Puppy 5 it needs to have some programs, scripts and Rox App Directories available. So, when converting a clean and fresh Puppy Linux into a T.O.P.L.E.S.S. LazY Puppy 5 it will change the initrd.gz and add the T.O.P.L.E.S.S. System SFS Modules to the directory of initrd.gz.

It depends on a original initrd.gz!

System SFS Modules

binaries32.sfs, binaries64.sfs, defaultapps.sfs, designs.sfs, documents.sfs, icons.sfs, langpack.sfs, roxappstarters.sfs, sfsplus.sfs, sfsplusrunscripts.sfs, variomenu.sfs, windowmanager.sfs

After converting to the T.O.P.L.E.S.S. LazY Puppy 5 based on tahr 6.0.2 they remain as:

binaries32_tahr_6.0.2.sfs, defaultapps_tahr_6.0.2.sfs, designs_tahr_6.0.2.sfs, documents_tahr_6.0.2.sfs, icons_tahr_6.0.2.sfs, langpack_tahr_6.0.2.sfs, roxappstarters_tahr_6.0.2.sfs, sfsplus_tahr_6.0.2.sfs, sfsplusrunscripts_tahr_6.0.2.sfs, variomenu_tahr_6.0.2.sfs, windowmanager_tahr_6.0.2.sfs

For a 64bit example: tahr64 6.0.2 will have binaries64_tahr64_6.0.2.sfs then.

When existing in boot directory all of these T.O.P.L.E.S.S. System SFS Modules are loaded at boot up from within /etc/profile.local and they will load to a top layer to ensure each and every SFS Content will above the layer of main sfs.

So now there are the config and setup files to be able to boot a pretty well pre-configured T.O.P.L.E.S.S. LazY Puppy 5 using favorite wallpaper, icon set, SFS Modules loaded, applications installed plus many more as it's listed two posts up - pretty much like a remastered version of a Puppy. And we have 10 T.O.P.L.E.S.S. System SFS Modules including many functions never seen in any different Puppy than LazY Puppy.

Though T.O.P.L.E.S.S. is able to do some more. Just save lots of your settings back to T.O.P.L.E.S.S. System SFS Modules!

Read about this at next post.

[LazY Puppy]

Save settings back to T.O.P.L.E.S.S. System SFS Modules

These T.O.P.L.E.S.S. System SFS Modules:
defaultapps.sfs, designs.sfs, documents.sfs, roxappstarters.sfs, sfsplusrunscripts.sfs and variomenu.sfs

or depending on tahr 6.0.2 these ones:
defaultapps_tahr_6.0.2.sfs, designs_tahr_6.0.2.sfs, documents_tahr_6.0.2.sfs, roxappstarters_tahr_6.0.2.sfs, sfsplusrunscripts_tahr_6.0.2.sfs, variomenu_tahr_6.0.2.sfs

can be rebuilt by rebuild-scripts. They will store at a sub-directory at boot directory and update to boot directory automatically at next boot. So let's have a look at the variomenu.sfs or variomenu_tahr_6.0.2.sfs and the VarioMenu-Groups for example.

There are 9 VarioMenu-Groups connected to 9 desktops:

Administrator, Audio, Development, Favorites, Graphics, Internet, Multimedia, Office, Video

Let's assume on VarioMenu-Group Favorites (which is desktop 4 (count from 1)) some Icons have been placed to the desktop or just moved around. Before rebooting or shutting down just go to menu SFS P.L.U.S. and let it rebuild the variomenu.sfs regarding variomenu_tahr_6.0.2.sfs. At next boot VarioMenu-Group Favorites will appear with icons added/moved - just like having a personal storage file in use.

Though there isn't any, so that's why T.O.P.L.E.S.S.: no personal storage file on a top layer necessary.

Using Programs by menu entries just as they would have been installed - just by creating RunScripts from SFS Modules and rebuilding the sfsplusrunscripts.sfs regarding sfsplusrunscripts_tahr_6.0.2.sfs. Starting Windows executable immediately by a menu entry of a Menu Pipe and by defining a default wine sfs in tahr.6.0.2.lped.cfg. Define your favorite word processor (a RunScript created from a Office SFS Module like LibreOffice etc.pp.) as defaultwordprocessor and rebuild the defaultapps_tahr_6.0.2.sfs. Store documents in /root/my-documents, create and collect links to online manuals and useful things like repositories, add them to the Guides menu (/root/my-guides) and just rebuild documents_tahr_6.0.2.sfs.

So this is mainly the benefit to the User of a T.O.P.L.E.S.S. LazY Puppy 5 based on tahr 6.0.2 or any different Puppy listed at the opening post. But -of course- there is some more benefit for the even more interested Puppy Linux User or even (probably more private?) Puppy Developer.

In the middle of this post Look for: I'm calling this Save Settings... is some more detailed information on an example for how to use Seamonkey and keep settings persistent.

Read about developers benefit at next post.

[LazY Puppy]

Special benefit of T.O.P.L.E.S.S. to users & developers

T.O.P.L.E.S.S. will give to users & developers a number of around 27 new defined Global Environment Variables, easy to use to get Access to external Files, Directories, Scripts, RoxApps, SFS Modules and many more by scripts. In Addition to these Global Environment Variables there will be some Global Environment Functions (atm there are 66, I may reduce this to the basics when releasing T.O.P.L.E.S.S.) called the Puppy Scripting Library.

Global Environment Variables:
(for the use in scripts and applications)

$MYBOOTDIR - Boot Directory (e.g.: /mnt/sde1/LazY)
$MYBOOTPRT - Boot Partition (e.g.: /mnt/sde1)
$MYEXTERNALRUNSCRIPTS - Path to external RunScripts Directory
(e.g.: /mnt/sde2/RSHs-ScriptBox/run_scripts/SFS_PLUS_Scripts)
$MYEXTERNALSFSPLUSSCRIPTS - equal to the above
$MYFILES - Path to a Directory containing Files
(e.g.: /mnt/sde1/My-Files)
$MYIMAGEMAGICKSFS - Name of the ImageMagick SFS Module
(e.g.: LP2_ImageMagick-6.6.9-5.sfs)
$MYIMAGICKSFS - equal to the above
$MYJDKSFS - Name of the JDK SFS Module
(e.g.: LP2_jdk-1.7u25-i586.sfs)
$MYJRESFS - Name of the JRE SFS Module
(e.g.: LP2_jre-1.7u13-i586.sfs)
$MYLINUXAPPS - Path to external Portable Linux Directory
(e.g.: /mnt/sde1/PortableApplications/PortableLinux)
$MYLPED - Name of the current used LPED Sub Config File
(e.g.: /mnt/sde1/tahr602/ConfigData/tahr.6.0.2.lped.cfg)
$MYMODULES - Path to external Modules Directory
(e.g.: /mnt/sde1/Module)
$MYPAR1PRT - Parallel Partition 1 (e.g.: /mnt/sde2)
$MYPAR2PRT - Parallel Partition 2 (e.g.: /mnt/sde3)
$MYPIKONAPRG - Path and Name to external Pikona Program
(e.g.: /mnt/sde1/Pikona/pikona)
$MYROXAPPS - Path to the external RoxApp Directories
(e.g.: /mnt/sde2/RoxApps)
$MYRSHROXAPPS - Path to RSH's RoxApp Directories
(e.g.: /mnt/sde2/RoxApps/RSH)
$MYRSHSCRIPTBOX - Path to RSH's ScriptBox Directory
(e.g.: /mnt/sde2/RSHs-ScriptBox)
$MYSARARSD - Path to the SARA R.S.D. Directories
(e.g.: /mnt/sde2/RSHs-SARA-ScriptBox/SARA-RSD)
$MYSARASCRIPTBOX - Path to the SARA B. ScriptBox
(e.g.: /mnt/sde2/RSHs-SARA-ScriptBox)
$MYSCRIPTS - Path to external Scripts
(e.g.: /mnt/sde1/Scripts)
$MYSYMLINKSTARGET - Target Partition for some symbolic Links
(e.g.: /mnt/sda1)
$MYWINDOWMANAGERSFS - Name of the current Window Manager SFS
(e.g.: windowmanager_tahr_6.0.2.sfs)
$MYWINEAPPS - Path to PortableApps for Wine
(e.g.: /mnt/sde1/PortableApplications/PortableApps)
$MYWINEAPPSSTARTER - Path to PortableApps Starter for Wine
(e.g.: /mnt/sde1/PortableApplications/PortableApps.exe)
$MYWINEINSTALLS - Path to Installation Packages for Wine
(e.g.: /mnt/sde1/PortableApplications/WineInstalls)
$MYWINESFS - Name of the current used Wine SFS Module
(e.g.: LP2_WineCorelSuite.sfs)

Puppy Scripting Library:
(just an overview of current content, I will add detailed information when probably reduced to its basics)

psl_backupinitrd, psl_cleaninitrd, psl_cleantemp, psl_cleantmp, psl_combobox, psl_date, psl_deskrefresh, psl_dev, psl_development, psl_dirdir, psl_drivelist, psl_errmsg, psl_extonly, psl_fixmenus, psl_funcs, psl_getappcategory, psl_getappcomment, psl_getappexec, psl_getappgenname, psl_getappicon, psl_getappicon4gtk, psl_getappname, psl_getlp2prefix, psl_getvolume, psl_getwinpos, psl_getwinsize, psl_getwp, psl_icon2script, psl_imageviewer, psl_info, psl_jwmpiperefresh, psl_launcher, psl_legend, psl_lp2prefix, psl_mdselect, psl_mfselect, psl_mkmenu, psl_mylang, psl_mypup, psl_noext, psl_noextbn, psl_okmsg, psl_okmsg1, psl_okmsg2, psl_opendir, psl_qr, psl_quickreboot, psl_replace, psl_savewinsize, psl_screenframe, psl_screenh, psl_screenshot, psl_screenw, psl_setdesktop, psl_setvmgroup, psl_setvolume, psl_setwinpos, psl_setwinsize, psl_setwp, psl_sound, psl_spacereplace, psl_strlen, psl_time, psl_tree, psl_xdte, psl_yesno

Dependencies: gtkdialog4 (>=0.8.3), wmctrl, Xdialog, xdotool
(gtkdialog and Xdialog should be in Puppy, wmctrl and xdotool are in the (e.g.) binaries32_tahr_6.0.2.sfs)

Ok, so you may think running live (in PUPMODE=5) is probably best of all use of Puppy and T.O.P.L.E.S.S. seems to be some sort of addition that could make running live a lot easier and much smarter, then be prepared to install T.O.P.L.E.S.S. and to create lots of T.O.P.L.E.S.S.LazY Puppy 5 Operating Systems.

Read about requirements and how to install T.O.P.L.E.S.S. at next post.

[LazY Puppy]

T.O.P.L.E.S.S. requirements and how to install

First I want to make sure not to have any impact at your boot partition or any of your internal drives.

Don't do this at your boot partition!

I strictly recommend for the first use to hold a free usb flash drive or a free usb hd drive to be able to boot from this drive as T.O.P.L.E.S.S. will create files that are usually/probably already existing at boot partition!

Formatted (using gparted) to (boot partition marked green):
- ext2 (if it is a single partition)
- ext2/ext3 (recommended) (if there are at least two partitions)
make it bootable (set boot flag)
install grub4dos
delete the resultant menu.lst

If the usb flash drive or the usb hd drive is e.g. /mnt/sde we need to install to its first (boot) partition sde1 (do not install to sde2 or to sde3 etc.)!

So now we are ready to go...

1. run a 32bit Puppy that can mount xz compressed sfs files
- best would be that also can extract/rebuild initrd.gz files just by clicking on it
2. extract the T.O.P.L.E.S.S..tar.gz to a ext partition
3. create a unique directory for each Puppy to convert at above mentioned drive's boot partition
4. copy contents from original ISO into the related directory (except: boot.cat)
5. make also sure to mount the 2nd partition (if there is any)

Important 1: there has been content of a Super Lucid 004 copied? If so, open its directory and make a symbolic link puppy_sulu_004.sfs to the sulu_004.sfs. SuLu not supported anymore

Important 2: Puppy Precise 5.7.1 and/or Super Lucid 004 needs some special treatment, which is explained in a post further down. So just convert them as the last ones when its special treatment was already executed. Precise not supported anymore

Important 3: If you got e.g. tahr and tahr64 to convert or even slacko and slacko64 to convert, just convert the 32bit Puppy first.

If all directories are created and all contents are copied, just open each directory and drag 'n' drop its initrd.gz file onto the T.O.P.L.E.S.S. RoxApp Directory. There will be a message when the initrd.gz is converted. After exiting this message the T.O.P.L.E.S.S. System SFS Modules will be copied.

The first one to convert may take a while, as there will be copied some files first time and just once! Any else will be converted in just seconds.

Repeated this for all Puppies/directories? Good!

If all the Puppies are converted just drag 'n' drop the file menu.lst onto the T.O.P.L.E.S.S. RoxApp Directory. (Note: this is only needed if you want to be able to boot Windows etc. from within this menu.lst instead of booting a Puppy.)

If the used drive is a usb hd drive, open file menu.lst in a text editor and replace pmedia=usbflash by pmedia=atahd. Save it. Repeat this to all the menu-xxx_xxx.lst files in all directories holding a T.O.P.L.E.S.S. Puppy now. Save them also.

Reboot...

No, wait. There is a few last steps to go just like to define the default wine sfs etc.pp.

Read about last steps to do at next post.

[LazY Puppy]

These steps aren't really necessary anymore, but the last one is!

Last steps before booting a T.O.P.L.E.S.S. LazY Puppy 5

Let's assume you have converted tahr 6.0.2 to T.O.P.L.E.S.S. and its directory is named Tahr602CE on /mnt/sde1.

Open /mnt/sde1/Tahr602CE/ConfigData/tahr.6.0.2.lped.cfg in a text editor.

Replace mywinesfs="LP2_WineCorelSuite.sfs" by mywinesfs="EnterTheNameOfYourWineSFSHere.sfs"

You can do this also with contents of:

Code: Select all

myjavajresfs="LP2_jre-1.7u13-i586.sfs" #<-- is included in T.O.P.L.E.S.S. package
myjavajdksfs="LP2_jdk-1.7u25-i586.sfs"
myimagemagicksfs="LP2_ImageMagick-6.6.9-5.sfs"

Repeat this to all Puppies converted to T.O.P.L.E.S.S..

Yes, this one is the necessary step to do!

Now choose one of those lped.cfg files and place a copy of it at boot partition. Rename it just to lped (used as fall back file).

[LazY Puppy]

Content removed!

SuLu and Precise aren't supported anymore by T.O.P.L.E.S.S. 1.0.1

[LazY Puppy]

Package content and download of T.O.P.L.E.S.S.

After converting a Puppy Linux into a T.O.P.L.E.S.S. LazY Puppy 5 each one owns 2 different main config files. By the created menu.lst files at boot partition and in each boot directory of a T.O.P.L.E.S.S. LazY Puppy 5 you can boot each one immediately by three different ways.

1. booting as original Puppy Linux
- no T.O.P.L.E.S.S. System SFS Modules loaded
2. booting by the default main config file
- just loading the T.O.P.L.E.S.S. System SFS Modules
3. booting by the BlackHoleInTheSky config file
- loading also additional SFS Modules for a Graphics T.O.P.L.E.S.S. LazY Puppy 5

So there added some additional files added like RoxApps and SFS Modules.

Content of T.O.P.L.E.S.S. Package:

SFS Modules
- LP2_GimpPainter-2.8.7.sfs
- LP2_Gimp-PlugIns-2.8.sfs
- LP2_ImageMagick-6.6.9-5.sfs
- LP2_jre-1.7u13-i586.sfs
- LP2_JWildFire-2.23.sfs
- LP2_LightZone_4.0.0-0_i386.sfs
- LP2_Pically-1.0.3.sfs
- LP2_Pixelitor_1.1.1.sfs
- LP2_Pixelize-1.0.0-1.sfs

RoxApps
- Find-And-Run (1.10.8, a little modified)
- ImageJ-1.44
- Make-Diff-n-Patch-GUI
- P.S.Library
- JVEditor-0.0.3

Wallpapers
- BadLittleDoggie-wallpaper_00-a-invers.jpg
- BadLittleDoggie-wallpaper_00-a.jpg
- BlackHoleInTheSky.jpg
- VM-Group-Video.jpg

Anything else in the package is needed by T.O.P.L.E.S.S. it self.

Download T.O.P.L.E.S.S. Package:

You can download T.O.P.L.E.S.S. at smokey01.com/RSH/TOPLESS/

MD5-Sum: 3ad51a1e4280a139c64f6b89f4663a26

[LazY Puppy]

First steps after booting a T.O.P.L.E.S.S. LazY Puppy 5

After the graphical desktop is running, there will be some actions executed that will give Xdialog information about its action. The last action to be executed is to create the menu pipes. If creating the menu pipes has finished execute the following steps:

1. Update the default applications for your needs using LazY-DAC Defaults Changer (menu Workstation->Setup)
- if you want to use a application from sfs in a defaultxxx script create a Runscript for this application
- create the RunScript by right-clicking the sfs and choosing: Create a RunScript
- select the application from appearing GUI
- then drag and drop the RunScript from /root/.my-sfs-scripts/SubDirHere/ScriptHere to the related entry in LazY-DAC
- if all defaultxxx scripts are updated to your needs re-build the defaultapps_xxx.sfs (menu SFS P.L.U.S.)

2. Setup the VarioMenu Desktop-Groups
- switch through the VarioMenu Desktop-Groups by the icons in task bar
- add or remove what ever you want and switch the VM-Group afterwards
- each VM-Group owns some RoxApp icons that need to be updated also (if you keep them)
- update them by right-clicking it (you may need to update its AppInfo.xml file also afterwards)
- if all is setup to your likes, rebuild the variomenu_xxx.sfs (menu SFS P.L.U.S.)

3. If you have created RunScripts
- update the sfsplusrunscripts_xxx.sfs (menu SFS P.L.U.S.)

4. If you have kept some RoxApp icons
- update the roxappstarters_xxx.sfs (menu SFS P.L.U.S.)

Everything will update at next boot automatically!

[LazY Puppy]

Booting a T.O.P.L.E.S.S. LazY Puppy 5 into different Languages

Like L.A.S.S.I.E. you can boot a T.O.P.L.E.S.S. LazY Puppy 5 into different languages, as there is option to boot into

DA, DE, EN, ES, FI, FR, IT, NL, PT and TR

just by setting up MYINTERFACE in the main config file. You can additionally setup MYTIMEZONE and MYKBDLAYOUT in that file.

The langpack_xxx.sfs needs to be manually updated to use this option. Get the latest version of the language package for your needs and extract it to get access to its content. Just open the langpack_xxx.sfs to edit by right-clicking it and copy the needed languages from /usr/share/locale of the extracted language package into /usr/share/locale of the extracted langpack_xxx.sfs. When it is updated and rebuilt store it into sub-directory Update.

Note 1: do only add files to /usr/share/locale and do not overwrite /pinstall_hacks.sh
Note 2: there will be parts of the menu still appearing in EN as they still would need to be translated by langpack developers

[stemsee]

Hi RSH

I cannot find the downloads. I am sure I am not the only one waiting for the post. Is it up?

stemsee

[LazY Puppy]

Hi RSH

I cannot find the downloads. I am sure I am not the only one waiting for the post. Is it up?

stemsee

Sorry, I wasn't at home on Sunday, I've just entered my home a few minutes ago. Preparing the file to upload now.

[LazY Puppy]

T.O.P.L.E.S.S. is now ready to download

Download-Link is here

Please follow instructions made in these postings.

1. T.O.P.L.E.S.S. introduction & default wallpaper
2. The T.O.P.L.E.S.S. Configuration Files
3. Setup a T.O.P.L.E.S.S. LazY Puppy easily
4. The T.O.P.L.E.S.S. System SFS Modules
5. Save settings back to T.O.P.L.E.S.S. System SFS Modules
6. Special benefit of T.O.P.L.E.S.S. to users & developers
7. T.O.P.L.E.S.S. requirements and how to install
8, Last steps before booting a T.O.P.L.E.S.S. LazY Puppy 5
9. Special treatment of Precise and Super Lucid for T.O.P.L.E.S.S..
10. Package content and download of T.O.P.L.E.S.S.
11. First steps after booting a T.O.P.L.E.S.S. LazY Puppy 5
12. Booting into different Languages

Some of them have been updated and the last two are added tonight.

[LazY Puppy]

Hi.

I've received a PM containing some questions about T.O.P.L.E.S.S. and I'd decided to answer these questions here, as the answers may include information of interest for any else user/tester of T.O.P.L.E.S.S. - I've also found a small issue related to the BlackHoleInTheSky.cfg which is not renamed to e.g. tahr_6.0.2-BlackHoleInTheSky.cfg after creating a T.O.P.L.E.S.S. LazY Puppy 5 from e.g. tahr 6.0.2.

Question No.1 was about packages (ndiswrapper) needed to be installed (tahr 605 and tahr64 605) and about where wif-fi drivers should be placed to be selected by the connect software.

Answer No.1:
Each T.O.P.L.E.S.S. LazY Puppy 5 will have a sub-directory in its boot directory (where the main sfs is stored) called InstallMe. Just put .pet packages to install into this sub-directory InstallMe - they will install automatically. No need to confirm its installation. Each package will give a short Xdialog message when it's going to be installed.

Change MYPKGINSTALLDIROPT=0 to MYPKGINSTALLDIROPT=1 in main config file (e.g.: tahr_6.0.2.cfg or tahr_6.0.2-BlackHoleInTheSky.cfg)

When loading wi-fi drivers by connect software from a directory at boot partition works well, just keep it as is. No need to change anything on this. Though you could e.g. create a sfs (e.g.: wifi-drivers.sfs or wifi-drivers64) and load them automatically at boot up. Enter wifi-drivers.sfs or wifi-drivers64.sfs at MYBOOTSFSLOADLIST in main config file and change MYBOOTSFSLOADLISTOPT=0 to MYBOOTSFSLOADLISTOPT=1.

Question No.2 was about providing small examples of config and setup files.

Answer No2:
When e.g tahr 6.0.2 is converted to a T.O.P.L.E.S.S. LazY Puppy 5 it will have a sub-directory in its boot directory (where the main sfs is stored) called ConfigData. There are two/three presets.

Just rename BlackHoleInTheSky.cfg to e.g. tahr_6.0.2-BlackHoleInTheSky.cfg (do this also for already converted Puppies).
You can watch its contents also in sub-directory /data-bootdir/ConfigData of the T.O.P.L.E.S.S. RoxApp directory.

Question No.3 was about Grub4DOS being necessary

Answer No.3:
Yes, Grub4DOS needs to be installed. Unmount the drive where to install it (if mounted), execute Grub4DOS and select the drive where to install it. Activate option to search only on this (selected) drive. Click Ok. At next GUI click Ok also. Open the drive to see its content. Remove the file menu.lst though keep the file grldr!!!

T.O.P.L.E.S.S. will create file menu.lst especially for Grub4DOS at boot partition plus e.g. menu-tahr_6.0.2.lst at boot directory of e.g. tahr 6.0.2. So you will have basically 3 boot menu entries for each T.O.P.L.E.S.S. LazY Puppy 5 plus a file containing sub-boot-menus where you can add more boot menu entries for a later or special use.

Very special: if there are multiple T.O.P.L.E.S.S. LazY Puppy 5 Systems installed you can choose at shutdown or reboot which T.O.P.L.E.S.S. LazY Puppy 5 System should be booted next time.

Question No.4 was about where to place the devx sfs

Answer No.4:
The devx sfs goes into boot directory.
Also all SFS Modules that should load at boot up.

Any else SFS Module -especially when you have created RunScripts from it to execute its program/s by a menu entry- goes into directory Modules at boot partition.

---

At next post I will place a Link to fix the issue related to the BlackHoleInTheSky.cfg which is not renamed to e.g. tahr_6.0.2-BlackHoleInTheSky.cfg after creating a T.O.P.L.E.S.S. LazY Puppy 5 from e.g. tahr 6.0.2.

[LazY Puppy]

Here is a archive to fix the issue related to the BlackHoleInTheSky.cfg which is not renamed to e.g. tahr_6.0.2-BlackHoleInTheSky.cfg after creating a T.O.P.L.E.S.S. LazY Puppy 5 from e.g. tahr 6.0.2.

Download archive and extract it to where the T.O.P.L.E.S.S. RoxApp directory is stored.

Archive removed - not needed anymore!

[LazY Puppy]

Found another issue when install drive has two partitions, so here's a updated archive.

Download archive and extract it to where the T.O.P.L.E.S.S. RoxApp directory is stored.

[unicorn316386]

Just tried downloading and extracting this, then dragging my initrd.gz from Slim Slacko 6 onto the Topless icon (as it's pop-up message instructed)... and what happened next was crazy, it was like someone unlocked all the cages at the zoo and all the wild animals were running free, transforming the root of my partition from a simple set of folders into a chaotic party house, and the directory where I dragged the initrd.gz from (which was also a simple dir of 5 files) started popping out a ton of new strange things left and right too, so I rebooted into that distro to see if anything would be different, and a giant myriad of stuff started displaying during boot like I was in a colourful circus act, finally with a completely new BIZARRO WORLD like desktop appearing instead of my old one. Hahahahah. You gotta try it to believe it! This T.O.P.L.E.S.S. thing is some ***** **** man.

[LazY Puppy]

Just tried downloading and extracting this, then dragging my initrd.gz from Slim Slacko 6 onto the Topless icon (as it's pop-up message instructed)... and what happened next was crazy, it was like someone unlocked all the cages at the zoo and all the wild animals were running free, transforming the root of my partition from a simple set of folders into a chaotic party house, and the directory where I dragged the initrd.gz from (which was also a simple dir of 5 files) started popping out a ton of new strange things left and right too, so I rebooted into that distro to see if anything would be different, and a giant myriad of stuff started displaying during boot like I was in a colourful circus act, finally with a completely new BIZARRO WORLD like desktop appearing instead of my old one. Hahahahah. You gotta try it to believe it! This T.O.P.L.E.S.S. thing is some ***** **** man.

Sorry, but I don't come to the clue of what are you trying to tell me (by: This T.O.P.L.E.S.S. thing is some ***** **** man).

As I read and understand your post, it seems to have done anything like it is intended to do.

Though, if this has messed up anything or everything at you usual boot partition, then you may should have read first my postings done, where I have mentioned e.g.:

First I want to make sure not to have any impact at your boot partition or any of your internal drives.

Don't do this at your boot partition!

I strictly recommend for the first use to hold a free usb flash drive or a free usb hd drive to be able to boot from this drive as T.O.P.L.E.S.S. will create files that are usually/probably already existing at boot partition!

T.O.P.L.E.S.S. requirements and how to install

If I did understand this somehow the wrong way and you did -as recommended- install to a fresh usb flash drive or usb hd drive then everything should be fine and you're going now to may have some fun with that!

However, the only file that has really changed is the initrd.gz and that was backed up to initrd-orig.gz. So nothing is getting lost and everything that has been added can be removed easily.

So anyone else before trying to use this: read my postings done carefully!

By the way: I haven't tried this on slim Slacko, so if anyone is trying to use this on a Puppy not listed in the opening post, please especially follow exactly the instructions in my post:T.O.P.L.E.S.S. requirements and how to install

Before trying to use T.O.P.L.E.S.S. read all posts linked below carefully and follow exactly its instructions

1. T.O.P.L.E.S.S. introduction & default wallpaper
2. The T.O.P.L.E.S.S. Configuration Files
3. Setup a T.O.P.L.E.S.S. LazY Puppy easily
4. The T.O.P.L.E.S.S. System SFS Modules
5. Save settings back to T.O.P.L.E.S.S. System SFS Modules
6. Special benefit of T.O.P.L.E.S.S. to users & developers
7. T.O.P.L.E.S.S. requirements and how to install
8, Last steps before booting a T.O.P.L.E.S.S. LazY Puppy 5
9. Special treatment of Precise and Super Lucid for T.O.P.L.E.S.S..
10. Package content and download of T.O.P.L.E.S.S.
11. First steps after booting a T.O.P.L.E.S.S. LazY Puppy 5
12. Booting into different Languages