Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 15 Dec 2017, 21:50
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Utilities
sfs_load-2.4 on-the-fly
Post new topic   Reply to topic View previous topic :: View next topic
Page 25 of 25 [371 Posts]   Goto page: Previous 1, 2, 3, ..., 23, 24, 25
Author Message
learnhow2code

Joined: 12 Jun 2016
Posts: 1015

PostPosted: Tue 21 Jun 2016, 20:08    Post subject:  

LazY Puppy wrote:
Doesn't you puppy have a Rox right-click option to make PET package ?


i got it, thanks everybody.
Back to top
View user's profile Send private message 
shinobar


Joined: 28 May 2009
Posts: 2664
Location: Japan

PostPosted: Wed 22 Feb 2017, 10:28    Post subject: sfs_load-3.0.1  

sfs_loat v3.0 in the slacko-6.9.6.4 does append the extra sfs to EXTRASFSLIST, but does not to LASTUNIONRECORD in /etc/rc.d/BOOTCONFIG.

Made sfs_load-3.0.1.pet applied above change:
EDIT: sfs_load-3.0 and 3.0.1 fails to load sfs's in the sub folder(psubdir) at boot. Fixed at v3.0.2.
EDIT: Rewrite around '/mnt/home' link, v3.0.3.
http://shinobar.server-on.net/puppy/opt/pup5/sfs_load-3.0.3.pet

Note that sfs_load-3.x is only for recent puppies like slacko-6+ and tahrpup.
Not compatible with older puppies.

See
http://www.murga-linux.com/puppy/viewtopic.php?p=944481#944481

_________________
Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html

Last edited by shinobar on Sun 26 Feb 2017, 07:19; edited 2 times in total
Back to top
View user's profile Send private message Visit poster's website 
gyro

Joined: 28 Oct 2008
Posts: 1409
Location: Brisbane, Australia

PostPosted: Wed 22 Feb 2017, 15:13    Post subject:  

@shinobar,
Please see my comment here, http://www.murga-linux.com/puppy/viewtopic.php?t=108017&start=445
gyro
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1409
Location: Brisbane, Australia

PostPosted: Tue 28 Feb 2017, 10:29    Post subject:  

As suggested by mavrothal, I'm continuing the discussion here.

Theh following is by boot entry:
Code:
title Puppy tahr 6.0.6 12 (sda3/tahr)
  uuid d304ea0b-d87a-415f-93e7-44275ade4a77
  kernel /puppy/tahr/vmlinuz libata.noacpi=1 psubdir=/puppy/tahr pupsfs=Linux pmedia=atahd psave=Work:/pupsaves/ pfix=fsckp,trim,nocopy
  initrd /puppy/tahr/initrd.gz
"Linux" is the label of an ext4 partition on my SSD (sda).
"Work" is the label of an ext4 partition on my HD (sdb).
The devx is in the "Linux" partition as /puppy/tahr/devx_tahr_6.0.6.sfs, beside /puppy/tahr/puppy_tahr_6.0.6.sfs and /puppy/tahr/zdrv_tahr_6.0.6.sfs.
The current sfs_load does not support the devx in this situation because the "Linux" partition is not "/mnt/home", that's the "Work" partition.

The new "init" script handles this scenario correctly.
"sfs_load" will load the devx, with a warning, but it's not loaded on reboot, it can't find the devx when called from "rc.sysinit".

Now that there is no "Boot Manager" or "init" code handling, touching or even looking at, extra=sfs's; it's time to think outside the box about how sfs_load stores it's data. Why not in "/root/.packages/loaded_sfs/" as symbolic links to the sfs files?

gyro
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2926

PostPosted: Tue 28 Feb 2017, 14:49    Post subject:  

gyro wrote:
Now that there is no "Boot Manager" or "init" code handling, touching or even looking at, extra=sfs's; it's time to think outside the box about how sfs_load stores it's data. Why not in "/root/.packages/loaded_sfs/" as symbolic links to the sfs files?


Symlinks will be broken if the partition they target resides on is not mounted. The only certainly mounted partition is /mnt/home (if $PUPMODE != 5).
Saving "partition,filesystem,/path/to/sfs " in BOOTCONFIG for each SFS may not be out of the box but has a known implementation and should work if the aim is to be able to have the target SFS anywhere in the running system.
As usually however there are many possible "solutions" to the "problem" and at the end of the day is up to the person that will do the coding.

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
OscarTalks


Joined: 05 Feb 2012
Posts: 1643
Location: London, England

PostPosted: Tue 28 Feb 2017, 17:21    Post subject:  

I am curious as to why the boot manager option for .sfs loading has been removed?
_________________
Oscar in England

Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1409
Location: Brisbane, Australia

PostPosted: Wed 01 Mar 2017, 21:39    Post subject:  

OscarTalks wrote:
I am curious as to why the boot manager option for .sfs loading has been removed?
Because "Boot Manager" has never done any loading of .sfs files. It aways was just a GUI for the extra-sfs facilitiy of the "init" script.
Now there is no extra-sfs facility in "init", so no GUI in "Boot Manager".

Why? Having 2 is just a waste of time and effort.

gyro

Last edited by gyro on Thu 02 Mar 2017, 00:24; edited 1 time in total
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1409
Location: Brisbane, Australia

PostPosted: Wed 01 Mar 2017, 21:47    Post subject:  

@mavrothal,

BOOTCONFIG, is the communication mechanism between the "init" script and the extra-sfs GUI in "Boot Manager".

While there was an extra-sfs facility in "init", and a corresponding GUI in "Boot Manager", "sfs_load" had no choice but to piggy-back on this mechanism.
Now, it is just an anachronism.

Edit:
My apologies, BOOTCONFIG is still a communication mechanism between "init" and "rc.sysinit" for the puppy system sfs's.
But, it's an "init" file, and having "extra-sfs" stuff in it is no longer needed. It's puppose is simpler and more obvious, if it contains only puppy system sfs information.

gyro
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1409
Location: Brisbane, Australia

PostPosted: Wed 01 Mar 2017, 22:21    Post subject:  

To bring the conversation back to my original issue, here is the "PUPSTATE" file of my setup:
Code:
PUPMODE=12
PDEV1='sda4'
DEV1FS='ext4'
PUPSFS='sda4,ext4,/puppy/tahr/puppy_tahr_6.0.6.sfs'
PUPSAVE='sdb2,ext4,/pupsaves/tahrsave'
PMEDIA='atahd'
#ATADRIVES is all internal ide/pata/sata drives, excluding optical, excluding usb...
ATADRIVES='sda sdb '
#ATAOPTICALDRIVES is list of non-usb optical drives...
ATAOPTICALDRIVES='sr0 '
#these directories are unionfs/aufs layers in /initrd...
SAVE_LAYER='/pup_rw'
PUP_LAYER='/pup_ro2'
#The partition that has the tahrsave file is mounted here...
PUP_HOME='/mnt/dev_save'
#(in /initrd) ...note, /mnt/home is a link to it.
#this file has extra kernel drivers and firmware...
ZDRV='sda4,ext4,/puppy/tahr/zdrv_tahr_6.0.6.sfs'
FDRV=''
ADRV=''
YDRV='sda4,ext4,/puppy/tahr/ydrv_tahr_6.0.6.sfs'
#Partition no. override on boot drive to which session is (or will be) saved...
PSAVEMARK=''
PSAVEPART='sdb2'
PSAVEDIR='/pupsaves/'
PSUBDIR='/puppy/tahr'
For optimum use of my SSD versus my HD, my "devx_tahr_6.0.6.sfs" is in the same directory as my "puppy_tahr_6.0.6.sfs".
The current sfs_load can't properly cope with this.
(Oh, the old "Boot Manager" extra-sfs code would have coped even less than sfs_load does.)

gyro
Back to top
View user's profile Send private message 
gyro

Joined: 28 Oct 2008
Posts: 1409
Location: Brisbane, Australia

PostPosted: Thu 02 Mar 2017, 00:22    Post subject:  

A couple of lessons about loading sfs's, from the woof-ce 'rationalise' project, that should not be overlooked:

1. Always use read-only loop devices.
My observations from always running "pfix=fsckp" show:
e2fsck does not indicate issues with the previous umount when read-only loop devices are used for sfs's.
e2fsck often reports issues with the previous umount when read-write loop devices are used for sfs's.

2. Add sfs's to aufs as "rr" layers.
According to the aufs documentation:
"ro" means that the actual directory could be "rw" and so aufs needs to be open to the possibility that it's contents might get changed by acesses outside aufs. e.g. pup_ro1 in pupmode=13.
"rr" means that the actual directory is also "ro" and so aufs can depend on it's contents remaining unchanged.
I have no emperical evidence to show that it makes a signicicant difference, but "rr" is supposed to be more efficient, and there seems to be no problem with specifying it.

gyro
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 2926

PostPosted: Thu 02 Mar 2017, 07:21    Post subject:  

gyro wrote:
But, it's an "init" file, and having "extra-sfs" stuff in it is no longer needed. It's puppose is simpler and more obvious, if it contains only puppy system sfs information.

Not that is important but if BOOTCONFIG is to have only puppy system sfs information we can just delete it. This info is in DISTRO_SPECS.
Again, many ways to do the same thing. The important part in the "everywhere" scenario is to include partition, fs and full path info.
Regarding where, my tendency is to keep as many files as possible so I do not need to worry for whatever other script may be digging info out of the target file, but is up to the person that may add this functionality to sfs_load to decide.

_________________
== Here is how to solve your Linux problems fast ==
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 25 of 25 [371 Posts]   Goto page: Previous 1, 2, 3, ..., 23, 24, 25
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Utilities
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0697s ][ Queries: 14 (0.0226s) ][ GZIP on ]