A SAVE-session to directory option added for PUPs [REOPENED]

A home for all kinds of Puppy related projects
Message
Author
User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#301 Post by mikeb »

https://www.dropbox.com/s/5ropea4n9xxkk ... e_V5.1.iso

An older but more familiar one... I started chomping more after that.

Notes...
sub folders disabled for simplicity but easy to restore..save search all over the same for the same reasons...so add to root of partition

need ram=/dev/ram0 if installing manually... pre cpio embedded initrd.

hash 79a422fb444a0debcfccea58b8d16ce0

mike

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

#302 Post by gyro »

It was mikeb's suggestion to use "mount -o bind" to map the actual save directory into "pup_rw", that gave me the impetuous to have a go at the "init" script. Until then I was avoiding the horrible alternative of changing all references to "pup_rw".
My understanding is that this is the same methodology mikeb has used previously, hence his experience has some relevance to the current implementation of "save directory".

Still, go for it, test it as hard as you can, and if it doesn't pass the test, then let's forget it.
I ask only one thing of testers; please be careful to test the difference between the patched version of a puppy and the actual behavior of the normal version of the same puppy.
Already during this project there have been some instances of the patched puppy not performing as expected, but further testing revealed that the normal version of the same puppy performed exactly the same way as the patched puppy. The discovered "bug" was part of the normal puppy, and unrelated to the "save directory" patches.

gyro

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#303 Post by mavrothal »

Thanks.
Is that a puppy2 init?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#304 Post by mikeb »

Its uses the modified puppy 2 init/initrd but made for lucid with its kernel needs eg usb hid changes.

mike

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#305 Post by bigpup »

shinobar,

Is your save to a directory code ready for real use testing or are you still just tweaking the CLI and GUI?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Scedule

#306 Post by shinobar »

bigpup wrote:shinobar,

Is your save to a directory code ready for real use testing or are you still just tweaking the CLI and GUI?
Still tweekling mainly the GUI for the save-to-partition. Hopefully update on this friday.
And what about save-to-floppy?

Please continue your test on the current iso:
http://shino.pos.to/party/bridge.cgi?pu ... ve-dir.iso
I feel we need more test on many scripts aside the shutdown. For example, the puppyinstaller need to modify the messages regarding save-to-partition and save-to-directory.
Last edited by shinobar on Thu 05 Jun 2014, 10:42, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

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

FYI

#307 Post by gyro »

jamesbond wrote:Save folder is implemented in Fatdog, since 620beta1 (over a year ago )
Reviewing this thread, I found this statement on page 1.
Apologies to jamesbond for taking so long to check this out. Today I installed Fatdog 361 and had a look inside.
Well, it seems that Fatdog's "init" uses "mount -o bind" to map the actual save directory to the desired mount point, (same as we do).
Just a bit more experience for the methodology.
gyro

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#308 Post by bigpup »

what about savi-to-floppy?
Where I live you can not buy floppies.
Have not been able to for years.
I have one 12 year old computer that has a floppy drive, but I have no floppy disc to use in it.

Would a floppy even have room for a useful save?

1.44MB, if I remember, was the biggest I ever used.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

gcmartin

#309 Post by gcmartin »

bigpup wrote:
what about savi-to-floppy?
Where I live you can not ...
I think @Shinobar is just having some fun with us. He knows that. Testing the waters, as I see it.

I probably have a "ton" of floppies of which I have not touched in maybe a decade. Cannot give them away....even to local museums. Also have some other media that is also, now, useless to...namely, couple of proprietary medias no-one uses anymore. Cannot give those away either.

BTW @Shinobar
Seems you and 01Micko are working together on that 32bit Slacko ISO you posted. It looks good and runs very smoothly. Thanks to both of you!

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

pupsaveconfig GUI update

#310 Post by shinobar »

EDIT: most recent gyro has uploaded:
http://www.fishprogs.info/puppy/slacko/ ... ko_5.7.sfs
See the post by gyro:
http://www.murga-linux.com/puppy/viewto ... 663#781663

shutdownconfig CUI/pupsaveconfig GUI update:
1. save-to-partition support with the GUI.
2. ROX-filer icon for pupsave directory.
http://shino.pos.to/party/bridge.cgi?pu ... ko_5.7.sfs

USAGE:
1. Get http://shino.pos.to/party/bridge.cgi?pu ... ve-dir.iso (2014-05-30)
2. Replace ydrv_slacko_5.7.sfs by the one above, 2014-0605 (notice the time stamp).
3. See on the test commands at http://www.murga-linux.com/puppy/viewto ... 445#781445

TODO:
Updating documents /usr/share/doc/help/C/pupsaveconfig.txt, puppyinstaller, resizepfile.sh, and etc.
Fix of the petget, bootmanager, and etc.
The rc.shutdown to be support not saving back with RAMSAVEINTERVAL=0 and '-0'.
Last edited by shinobar on Sat 07 Jun 2014, 11:57, edited 10 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

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

#311 Post by 01micko »

Save to floppy is basically useless. All it can do is save some basic system settings from /etc. None of $HOME (/root) is saved. Since floppies have been out of "vogue" for at least 10 years then I think "save to floppy" should be deprecated and in fact unsupported. Zip disks (iomega) are dubious too, however they can be still of some use to someone. The only thing floppies are good for now are booting in cases where old, old BIOS do not support CD boot. We are talking, in most cases, pre 2000; pentium I, early pentium II, old AMD K5 (which all I have tried boot CD anyway), cyrix and possibly early Via. And remember, this is BIOS dependent (not processor or chipset) and there are possibly PIII's that only boot from floppy, though I am yet to encounter one. Only one I have is a 486DX, @ 66 MHz. That thing won't run anything past puppy 2.1.6-fat-free-dillo (by BigBass - Hi Joe).

In fact, many mobo's still have a floppy controller but said mobo's are often configured with no floppy drive. This can hinder searching as a floppy drive (in the save file creation code) is probed. If a controller is present but no floppy drive is present it can take up to 90 seconds before the kernel returns a response, delaying save by that amount of time. A definite turn off to newcomers. I raised this issue on the woof-CE forum but nothing is done as yet. We'll get to it. Sure, it could be disabled at kernel level but then it totally excludes any user that may want to use a floppy drive for any purpose.
Puppy Linux Blog - contact me for access

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

CUI and GUI

#312 Post by shinobar »

The CUI shutdownconfig and the GUI pupsaveconfig has different code.
The pupsaveconfig has many settings in one window interface whereas the shtdownconfig has step by step dialog.

Removing the file /usr/sbin/pupsaveconfig, you get step by step dialog even on graphical X environment. The puplet builder has a choice whether one window interface or step by step under the graphical X environment.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

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

#313 Post by 01micko »

@GCMartin. Thank shinobar. It's his collation of effort in this case. I haven't had time to provide any input. I'll test soon.
Puppy Linux Blog - contact me for access

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

#314 Post by peebee »

Using shinobar's ydrv dated today....

If I disable a systray item with:

Menu - System - Boot Manager - Manage startup apps

when I reboot the item is back in the systray and root/.config/autostart contains both the original systray .desktop and the renamed version - the renamed version comes from the pupsave folder....

see screenie
Attachments
Screenshot_2014-06-05_220223.png
(25.77 KiB) Downloaded 250 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

#315 Post by gyro »

@peebee
Looks like a missing ".wh.firewallstaterun.desktop" file.
But I don't think that it's shinobar's ydrv that's doing it.

On my "save directory" patched slacko 5.7, I replaced my minimalist ydrv with shinobar's ydrv. Used "Manage startup apps" to disable and enable startup apps, and all worked correctly. When I disabled an app, on reboot it wasn't there. In another puppy I looked in slacko's slackosave/root/.config/autostart and all the appropriate ".wh." files were present.

So, I have no idea what is deleting the appropriate ".wh." file on your system.

gyro

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#316 Post by bigpup »

gcmartin,

What to do with all those floppies.
http://www.noordinaryhomestead.com/10-w ... ppy-disks/
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

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

#317 Post by peebee »

gyro wrote:So, I have no idea what is deleting the appropriate ".wh." file on your system. gyro
It was a pristine manual frugal install of shinobar's iso but with the ydrv updated with the latest version...nothing else installed.

There were some other oddities to do with sfs files - on 1st reboot you get asked if you want the ydrv loaded - even though it already is.

Then sfs-on-the-fly could not "see" an sfs in the frugal install folder (actually a symlink to an sfs) and would not load it. It did load OK if clicked directly rather than using sfs-load-on-the-fly. This (putting a symlink for an sfs into the frugal folder) works fine for "standard" Slacko.

Cheers
peebee
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#318 Post by mavrothal »

peebee wrote: There were some other oddities to do with sfs files - on 1st reboot you get asked if you want the ydrv loaded - even though it already is.
As I mentioned earlier it needs this change
Also another couple of apps can not handle a/ydrv and need this
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

Re: slacko-5.7-01-pupsave-dir.iso

#319 Post by bigpup »

shinobar wrote: This does not intend to make a derivative. Just for precise test of the new concept of the pupsave to a directory and the new user interface to make the pupsave.
If you already have slacko-5.7 in your HDD, boot off the CD with RAM mode, or it does not work as expected.

You can do actual test, and can still use 'shutdownmock' for dummy test.
Examples:
# shutdownmock ram
# shutdownmock cd
# shutdownmock sda2
# shutdownmock acpi ram
# shutdownmock --cli cd
etc.

It is not remastered. It has ydrv_slacko_5.7.sfs in it for ease to see the differences from the original. some made by gyro and some by shinobar.
The initrd.gz is patched by gyro, and i shinobar add another patch because it did not read the Puppy SFS on USB media:
#140427 shinobar: search on usb if PUPSFS is on cd
#140508 gyro: save-directory
The boot loader of the CD is replaced by Grub4Dos instead of the original isolinux for ease to boot with RAM mode.
I think from these statements this is not a full working version of Slacko. Just one that will let you test the new shutdownconfig and save options.

I would only use it to do those tests.

shinobar correct me if that is not true.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

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

#320 Post by gyro »

Well, at least ydrv support is getting a good testing.

@mavrothal, sometime ago I rejected your proposal that a remastered puppy was required. Unfortunately I naively assumed that ydrv was fully supported. Looks like we may need to ditch the ydrv and produce at least a patched puppy_slacko_5.7.sfs.

gyro

Post Reply