Question regarding exclusive system modifications and persistence

[Magi Ancient]

Not sure if this has been asked before. I wildly gleened the forum entries for related keywords, but did not locate anything as a near match (although i do miss things from time to time).

I am wondering how i can save a file created internally (e.g.: via edit command) back to the disk. I see that there is persistence until I rebuild. So the "new file" exists in the disk image itself, but not exists in the programs directory. 

I am aware of the looptmp method (under gnu/linux), but i had something different in mind that i think many MikeOS devs and users would find very useful and enjoyable.

I would love to be able to modifiy the system within itself, without relying on external applications or host system (for example, only using ASM, Mike Basic, and Forth, etc).

Thanks ahead and stay well :D

PS: Don't forget to belly laugh!

[Michael Saunders]

Hi again Magi,

Are you using build-linux.sh to build MikeOS? That should only create
a new disk_images/mikeos.flp if the file doesn't exist, but otherwise
only add the bootloader, kernel and programs to it. So IIRC there
should be persistence (but I'm not near a Linux box at the moment to
test).

Or do you mean something else?

Cheers,
Mike

> --
> You received this message because you are subscribed to the Google Groups "MikeOS" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to mikeos+un...@googlegroups.com.
> To view this discussion, visit https://groups.google.com/d/msgid/mikeos/d708d795-fc48-46e4-8ddc-a9b42d894eb7n%40googlegroups.com.

[Magi Ancient]

Hi again Mike && thx for speedy reply!

Yes, that's correct. Currently, I am running the system via Qemu under 64-bit Pop-OS (Ubuntu) 22.04.

Ideally, I want to run on actual hardware, but i gotta find some more parts for my pentium3 pc that's been sitting on a patio for 14 years first.

On the issue of the rebuild process, I noticed that disk_images/mikeos.flp does, indeed, persist changes made internally during operation. 

But I also noted that rebuild wiped everything, leaving it pristine, like a live boot system.. all new changes lost (i've been telling myself to back things up for 20 years...)

I had modified the build script to copy any new files over to the disk during rebuild, since I'm creating and editing the programs from within the system.

This seemed to have fixed the problem i was having. On a real floppy, of course, the persistence would be there :)

I wanted to prevent the need for rebuild, but... now that you mention this, i guess i could just.. not rebuild lol

Problem solved.

In the case that it may be helpful someday, here's my one liner mod for build-linux.sh (it's placed directly after tmp-loop is mounted) (hence removed, since i won't be rebuilding after each change)

    cp tmp-loop/*.bin tmp-loop/*.bas tmp-loop/*.pcx tmp-loop/*.txt tmp-loop/*.4th tmp-loop/*.512 programs
    cp programs/*.bin programs/*.bas programs/*.pcx programs/*.txt programs/*.4th programs/*.512 tmp-loop

recursively recursive parroty parody

It needs to be cleaned up but it gets things done ATM

Thanks again and stay well