Closed asdf1nit closed 5 years ago
Interesting. Would help #211 . I have no real way to test this though.
What I can suggest is a script that exports the OS in to a tar.xz
file.
You could run on an image something along the line of (you will need CustomPiOS installed and common.sh
from it in path.
mkdir /tmp/mount
source /path/to/CustomPiOS/src/common.sh
mount_image /path/to/extracted/fullpageos.img 2 /tmp/mount
cd /tmp/mount
tar cfJ /tmp/fullpageos_piserver.tar.xzt
You might need to unmount /dev
and /proc
first I just wrote this and never ran it.
Alternatively I would gladly accept a CustomPiOS module that would do this. Would also be useful for RealtimePi.
I haven't looked into CustomPiOS as I've just run across your repo but, I think that I'm going to give this a shot. I have no where close to the 150 pi that issue #211 has but deploying 20 is enough for me to not want to mess with frequent, even twice yearly updates to my pi's.
Thanks for the starting point. I'll play around on a vm, got a few Pi's I can test with so I'll see it I can get it right. Once I've got something worked out if it benefits your project I'll submit a pull.
Cool, would appreciate if you update so others can learn.
See https://github.com/guysoft/CustomPiOS/commit/4537a1eb332d8a562e9e5174a340ee172582b94a
If you export the filesystem to a tar.gz it should work.
Something along the lines of
export fullpageos /
Might be an option (not tested)
Not quite understanding the use of "export fullpageos /". I'm fairly new to managing linux systems. I'm a sysadmin mostly windows and mac but my google fu is failing me at the moment for the process to accomplish this.
I've added common.sh to my path but it's not acting correctly, to my knowledge. If I call it with parameters it just returns to the cmdline with no output.
As for the script you mention and posted earlier having an image that's bootable with my tweaks is the problem I'm having. I have the current running build that I'd like to use but how would I image that while it's running?
Maybe I'm going about this the wrong way. Could you point me in the direction of some documentation so I can learn this?
You need to source common.sh. Not add it to your path. On Jun 26, 2018 03:52, "asdf1nit" notifications@github.com wrote:
Not quite understanding the use of "export fullpageos /". I'm fairly new to managing linux systems. I'm a sysadmin mostly windows and mac but my google fu is failing me at the moment for the process to accomplish this.
I've added common.sh to my path but it's not acting correctly, to my knowledge. If I call it with parameters it just returns to the cmdline with no output.
As for the script you mention and posted earlier having an image that's bootable with my tweaks is the problem I'm having. I have the current running build that I'd like to use but how would I image that while it's running?
Maybe I'm going about this the wrong way. Could you point me in the direction of some documentation so I can learn this?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/guysoft/FullPageOS/issues/229#issuecomment-400141521, or mute the thread https://github.com/notifications/unsubscribe-auth/AAT4JjiN683lE_CAjARjQ9SmKIx-oubXks5uAYXQgaJpZM4T12E4 .
Anything new on this? Trying for days to make it PiServer "compatible" Thanks
@TakuyaSan420 OP said its beyond their scope, I have no time for this. I gave an explanation how this might be done, if you feel like trying.
I never went down this path but I did find a solution. I started using cockpit https://cockpit-project.org/ which brings all of my pi's into one management interface, with a little setup overhead.
It can sync your users and login info as well as run updates relatively easy.
In stretch you have to add the debian backports repository but in buster it is now in the testing repo which doesn't need any additional configuration to work. I haven't been able to add the program to a module successfully as it has some dependencies that don't work in a chroot.
Looking into piServer for deployment and management of your OS and thought maybe you would consider either