Getting closer... or ...editing the initrd.gz (Closed)

Message

stemsee · #21 Post by **stemsee** » Wed 26 Nov 2014, 10:55

I think you are from 'beyond' RSH

This is game changing stuff ... very exciting! I will wait for it!

LazY Puppy · #22 Post by **LazY Puppy** » Thu 27 Nov 2014, 01:05

stemsee wrote:I think you are from 'beyond' RSH

Oh...

So I need to refine my statement:

Ok, I have made some Progress, I have gone here!

stemsee wrote:This is game changing stuff ... very exciting! I will wait for it!

Yes!

This is changing everything - especially for my own developments!

However, I have made again some progress. Added Option to load Window Manager SFS and SFS files listed to load at boot up to a top layer.

Now going to try to include the new L.A.S.S.I.E.'s pinterface option into the config file. After doing this -successfully or even not- I will build a GUI to setup the config file from within a GtkDialog GUI.

Hopefully I can upload a ready for use initrd.gz for precise 5.7.1 on Friday afternoon or Friday at night.

Don't refuse to learn...

Edit:

Attached Image shows a clean, fresh and un-remastered precise 5.7.1 booted straight into Enlightenment e17 Window Manager loaded to top layer, wine-1.5.28-i486-2-s14-patched.pet and Wine-MimeType.pet installed automatically and PortableApps Starter immediately working! Gimp Painter 2.8.7 and its PlugIns SFS loaded from /root/Startup to normal layer.

LazY Puppy · #23 Post by **LazY Puppy** » Thu 27 Nov 2014, 05:32

Success!

Added option pinterface to the config file!

Now going to sleep and later building the config GUI.

stemsee · #24 Post by **stemsee** » Thu 27 Nov 2014, 08:17

Totally awesome dude! Congratulations!

I know that you don't generally use savefiles, but many of us do. So if a savefile is used what happens? Does the config also allow for uninstalling/unloading a pet/sfs? Just thinking about it, not trying to dampen down the euphoria, by making inane requests as is usual when someone reaches a milestone here!!!

stemsee

LazY Puppy · #25 Post by **LazY Puppy** » Fri 28 Nov 2014, 00:21

stemsee wrote:Totally awesome dude! Congratulations!

I know that you don't generally use savefiles, but many of us do. So if a savefile is used what happens? Does the config also allow for uninstalling/unloading a pet/sfs? Just thinking about it, not trying to dampen down the euphoria, by making inane requests as is usual when someone reaches a milestone here!!!

stemsee

Never mind!

None of the Forum Members/Puppy users really will be able to dampen down my euphoria and/or fun in Puppy Linux. Usually it is sufficient if I do know for myself that my work is just good!

Ok, personal storage files aka savefiles:

- unloading .sfs will work as usual since sfs_load is used, except
- .sfs loaded to top layer will not unload during the running session

- un-installing .pet files will not work since petget isn't used for that (petget is uncomfortable for automated installs since you need to confirm installation of each package)

Using a save file combined with the new config file options should work generally - or at least should not crash the boot process.

E.g.: as long as the new wallpaper set for a use is inside the Puppy it will be used. But you cant' access /mnt/sdc1 (e.g. boot partition) when using a save file since it will be /mnt/home then and wallpapers from within the boot partition/directory currently won't be found then - needs refining some code.

New startup sound is equal to this.

Loading .sfs to top layer is equal to this also.

However, I can't see any advantage for this when using a save file since there is very much more to set up as covered by the config file by now.

In my opinion the use of a save file should be deprecated. Go have a look at the Lucid 528 thread (the original by playdayz). You'll find hundred of pages where dozens of people worked for months just to get 'sound not working when using a save file' problem solved. This huge amount of effort better had be going into development of a external config file. At least they did solve the issue, but that didn't solve any of the frequently arising save file issues in general. These issues are still arising -more or less- in each new puppy developed and published forcing a new user to run straight into such issues over and over again.

Instead of listening and watching (external config file was suggested already earlier multiple times by several users and was already used in Arch Pup (iirc)) they invent the save to folder option forcing a user to run straight into new save file related issues.

Give to the user a external config file plus a config script for the config file plus added some functions to create symbolic links to HDD for the use of e.g. saving browsers content etc.pp.

Of course, you can do a mess that way as well but just need to remove the symbolic link (or not to create it at boot up) and your OS will boot and run. You cant do this with save file in use. All you can do is to boot in RAM (PUPMODE=5) and trying to copy some files out of the save file, to put them into a new one after creating a new save file.

However, want to have this working in complete for the use of a save file?

Just join into the one man RSH development team and add/change related code for it.

stemsee · #26 Post by **stemsee** » Fri 28 Nov 2014, 01:49

Code: Select all

durr=`mount | grep dev_ro2 | cut -f1 -d ' ' | cut -f3 -d '/'`
dorr=`mount | grep dev_save | cut -f1 -d ' ' | cut -f3 -d '/'`

Code: Select all

	if [[ $durr = $drive ]]; then
	drive="Home"
	elif [[ $dorr = $drive ]]; then
	drive="home"
	fi

Code: Select all

#normal pups
	. /etc/DISTRO_SPECS
	. /etc/rc.d/PUPSTATE
	if [[ $durr = "`echo $PUPSFS | cut -c 1-4,11-40 | cut -f1,2 -d '/' | cut -f1 -d '/'`" ]]; then
	echo $PUPSFS | cut -c 1-4,11-40 | cut -f1,2 -d '/' | sed -e 's|'$durr'|Home|' > /tmp/sfs
	elif [[ $dorr = "`echo $PUPSFS | cut -c 1-4,11-40 | cut -f1,2 -d '/' | cut -f1 -d '/'`" ]];  then
	echo $PUPSFS | cut -c 1-4,11-40 | cut -f1,2 -d '/'  | sed -e 's|'$dorr'|home|' > /tmp/sfs
	else
	echo $PUPSFS | cut -c 1-4,11-40 | cut -f1,2 -d '/' > /tmp/sfs
	fi
	sed -i 's|^|boot=|' /tmp/sfs
	. /tmp/sfs

[/code]

LazY Puppy · #27 Post by **LazY Puppy** » Fri 28 Nov 2014, 03:32

Knocked out!

This is a good example and could be used as a proof/evidence that I'm not a programmer!

It won't work this way. Offering such kind of code to me without any advice what to do with it, will knock me out - completely!

Here is how it could work:

After finishing the config GUI (currently already working on it) I will publish a ready to use initrd.gz for precise 5.7.1.
Use this one to add your code and/or to change mine and to testing it using a precise 5.7.1.
Send your edited files to me by PM (LazY Puppy, NOT RSH !!!)
Don't forget to mark your code (code sections) with # stemsee either at beginning and end of code section or per line, so I can find it easily to put it into my file/s (since I'm obviously continuing to work on it).

If we would get close to a point, where you could use it all to be built into the initrd.gz of the your created OS, send it (the initrd.gz) to me (PM, LazY Puppy, NOT RSH !!!) and I will put it in for you.

What do you think?

stemsee · #28 Post by **stemsee** » Fri 28 Nov 2014, 06:54

It is proof that I am NOT a programmer. It is a reliable mech to deal with 'home' and I add 'Home' for /initrd/dev_save and /initrd/dev_ro2 respectively, in case they use the same partitiion, or different partitions or no partitions at all.

It is the way I translate /initrd/mnt/dev_save to 'home'
and /initrd/mnt/dev_ro2 to 'Home' . So in /mnt/ there exists 'Home' and 'home' ...

Just sharing a loose idea ...

I will follow your idea.

LazY Puppy · #29 Post by **LazY Puppy** » Sat 29 Nov 2014, 00:12

Ok.

I have uploaded the initrd.gz for precise 5.7.1 plus the new config file (you'll need to edit this for your purposes).

Therefor I've changed the first post where you can find the link. It's all packaged into a .tar.gz file.

Note: it doesn't contain the PConfig GUI Script since this is currently still in DE only and I need to pause this for some days due to real life issues.

Just play with it and check what you can do for the use with a save file until I return to this.

Have fun.

stemsee · #30 Post by **stemsee** » Sat 29 Nov 2014, 12:36

I can read DE no problem!

stemsee · #31 Post by **stemsee** » Sat 29 Nov 2014, 21:43

Looking to the future maybe you should consider continuing the work using trusty tahr! Precise 5.7.1 is OLD.

LazY Puppy · #32 Post by **LazY Puppy** » Mon 01 Dec 2014, 03:33

stemsee wrote:Looking to the future maybe you should consider continuing the work using trusty tahr! Precise 5.7.1 is OLD.

At least I need to use tahr temporarily to "fix" the code for the use of a new wallpaper.

Currently I'll stay using precise, since I've set up a usb flash drive for this development. This usb flash drive is pretty much filled up and doesn't have enough space on it to install also a tahr.

Sometimes I need to push the reset button (bug in edited init script) and I don't want to use my USB HD for such actions where tahr is already installed.

stemsee · #33 Post by **stemsee** » Mon 01 Dec 2014, 06:25

How big is your usb flash drive? I have a sandisk cruzer extreme 192mb/s usb 3.0 drive unopened, here I'd be happy to send to you (as a contribution to your present work), just pm me your address.

LazY Puppy · #34 Post by **LazY Puppy** » Mon 01 Dec 2014, 09:34

stemsee wrote:How big is your usb flash drive? I have a sandisk cruzer extreme 192mb/s usb 3.0 drive unopened, here I'd be happy to send to you (as a contribution to your present work), just pm me your address.

It's just a 2GB USB flash drive containing Precise 571 and LazY Puppy (to be able to boot a different OS, if edited init script of precise fails) and minimum necessary files and SFS Modules to be able to work and test this work as comfortable as possible - related to the USB flash drive size.

Thanks for the offer, but my machine can use USB 3.0 only if it would be especially also USB 2.0 compatible. I did once bought accidentally a USB 3.0 HD which did not work on my machine - all USB 2.0 interfaces. I'm owning now a USB 3.0 HD which was especially marked as USB 2.0 compatibel and this is working well. I have made a switch on this HD to use ext2 formatted boot partition instead of fat32 which I used to use normally.

However, it's also really not needed to contribute my present or any other work that way, since I'm already paid in a royally way by owning four (six) of the smartest Operating Systems of the Planet!

LazY Puppy · #35 Post by **LazY Puppy** » Tue 02 Dec 2014, 22:47

Hi.

While trying to build this into my LazY Puppy I've found some (very small) issues when setting a new wallpaper to use. Though the wallpaper functions had already a need to be refined for Tahr Puppy, so I refined it and built some initrd.gz files packaged in a .tar.gz file.

Therefor I now have uploaded this .tar.gz file which contains the initrd.gz files for:

- Precise 5.7.1
- Slacko 5.9.3
- Tahr 6.0 CE

plus a config file for each one of these Puppies.

The config file includes my current settings used while developing and doing some testings with it. You'll need to make some changes to apply your preferred settings for doing some testings on this work.

First post updated.

stemsee · #36 Post by **stemsee** » Tue 02 Dec 2014, 23:16

Exactly - I wanted to say provide example configs! Do you think this should work on DPup Wheezy?

LazY Puppy · #37 Post by **LazY Puppy** » Tue 02 Dec 2014, 23:48

stemsee wrote:Exactly - I wanted to say provide example configs! Do you think this should work on DPup Wheezy?

I'm quiet sure it will work in almost any Puppy that is using the Rox Desktop and PuppyPin.

Just copy and paste all of the '# RSH' marked code lines and sections to the appropriated section of the Puppy's init script. Maybe the wallpaper functions and enabling/disabling welcome first boot needs to be refined. But most of all should work!

Ok, here is what we got right now:

Currently there are these Options available:

# Sleep Time - wait until script zzz_z_auto_execute will be executed
MYSLEEPTIME=2

# Window Manager - set a new window manager, load from SFS, load to a top layer
MYWINDOWMANAGER=jwm
MYWMSFSLOADOPT=1
MYWMSFSTOPLAYEROPT=1
MYWINDOWMANAGERSFS=LP3_WM-Flux-Ice-0.1.sfs

# Num Lock - disable/enable numlock of the numerical block
MYNUMLOCKOPT=1

# Interface - boot directly into new interface: da, de, es, fi, fr, it, nl, pt & tr
MYINTERFACE=de

# Timezone - currently unused
MYTIMEZONE=

# Keyboard Layout - set keyboard layout also needed when using $MYINTERFACE
MYKBDLAYOUT=de
RESTARTAFTERX=1

# Mount all HD and USB Flash Drives - mount all or only listed drives automatically
MOUNTALLMYDRIVES=1
MOUNTMYDRIVES=""

# Welcome First Boot - enable/disable welcome first boot GUI
MYWELCOMEFIRSTBOOT=0

# Personal Settings PopUp - enable/disable the Personal Settings PopUp
MYPERSONALSETTINGSPOPUP=0

# Desktop Icons - enable/disable the Desktop Icons
MYDESKTOPICONS=1

# Drive Icons - enable/disable the Drive Icons (only if $MYDESKTOPICONS is used)
MYDRIVEICONS=1

# Wallpapers - set a new wallpaper for a use
MYWALLPAPERDIRECTORY=Dateien/Wallpaper/RSH
MYWALLPAPER=Michaela.png

# Startup Sound - set a new startup sound (no longer barking)
MYSTARTUPSOUND=studio1337-bootsound.wav

# Install Packages - install .pet packages automatically from directory
MYPKGINSTALLDIROPT=1
MYPKGINSTALLDIR=InstallMe

# Global Directory to load SFS Files from - currently only for my private LazY Puppy
MYGLOBALSFSDIR=

# Auto-Load of SFS Modules at /etc/profile.local - load SFS Modules listed at boot up, load to top layer also
MYBOOTSFSLOADLISTOPT=0
MYBOOTSFSTOPLAYEROPT=0
MYBOOTSFSLOADLIST=""

# Auto-Load of SFS Modules at /root/Startup - load SFS Modules listed after X appears on the screen (only to normal layer)
MYSFSLOADLISTOPT=1
MYSFSLOADLIST=""

# Auto-Start of Applications - execute listed applications automatically and from list in simple text file
MYAUTOSTARTAPPS=""
MYAUTOSTARTAPPSLISTFILE=precise_5.7.1-autostart.lst

# Startup Script - execute a user's startup script
RUNMYSTARTUPSCRIPT=0
RUNMYSTARTUPSCRIPTBOOTCONTENT=0
MYSTARTUPSCRIPT=StartUp

LazY Puppy · #38 Post by **LazY Puppy** » Wed 03 Dec 2014, 03:51

Hi.

I've just setup a new initrd.gz file for testings.

It is for Super Lucid 4.

First Post updated.

Image:

Super Lucid 4 booted into DE (it offers a boot dialog, though), different Wallpaper, all Drives mounted, L.A.S.S.I.E.'s Window Managers SFS plus LP2_Gimp273.sfs automatically loaded.

LazY Puppy · #39 Post by **LazY Puppy** » Thu 04 Dec 2014, 02:32

Hi.

I successfully have built this into my several Puppy Linux Operating Systems.

Remastered Versions:

- LazY Puppy - (based on Lucid 528-4)
- Osiris Studio - (based on Lucid 528-4)
- LazY THD - (based on Three Headed Dog)
- LazY Precise - (based on Precise 5.6)
- L.A.S.S.I.E. - (based on Precise 5.7.1)

All done just by copy/paste the additional code into the init script in less than five minutes.
Edit: of course, added the additional files to the initrd.gz as well. (additional files listed at first post)

Original Versions:

- Precise 5.7.1
- Slacko 5.9.3
- SuLu 4
- Tahr 6.0 CE

By now this is running AND working in nine (9) Puppy Linux Operating Systems, so I'm sure this will work in almost any Puppy Linux.

My current goals are reached now, so I'm open to further suggestions and/or related code etc.pp. I will finish the Config GUI much later and I'm now back to standard development.

greengeek · #40 Post by **greengeek** » Thu 04 Dec 2014, 07:00

- possible Locations for $MYWALLPAPER:
- - /usr/share/backgrounds, Boot Partition, Boot Directory, Sub Directory of Boot Partition or Boot Directory

In my 'self personalising' puppy I ask the user to put their desired wallpaper into a new directory called /usr/share/backgrounds/personal.

I also ask them to include a new bootsplash called splash.xpm into the same directory. Would this work for your system?

EDIT :I probably wasn't very clear - I get the user to boot the puppy, set up their new wallpaper in the 'personal folder', (and other changes), then run the personaliser script which grabs the personal changes and builds the new pup.

Maybe you could ask the user to set the desired changes up in their current pup, the 'grab' those changes. At least for wallpaper.

Do you think you will build a script that automatically makes the required changes to the initrd? And to also help the user to set up the new config file at the same time?

What you are doing here is amazing. I think of it as a similar concept to Woof 5 - a 'standard' way to make a 'personal' pup. i'm just so excited by this development.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Getting closer... or ...editing the initrd.gz (Closed)