Re: PINN - An enhanced version of NOOBS.
Posted: Sat Jan 28, 2017 10:51 pm
@I621148 please check your inbox for a couple of PMs.
A small, affordable computer with free resources to help people learn, make things, and have fun
How involved would it be to reverse the options to backup an OS image to web/usb/sd card?PINN is designed to make it easy to select and install operating systems for the Raspberry Pi without having to worry about manually imaging your SD card.
You might like to take a look as "OS spaces" as supplied by WD:321 wrote: Ideally I'd like to have an automated way to spin up and down different OS 's and backup to SD/USB/Web an OS for post mortem. I dont know if this is too much feature creep for PINN and/or if something else exists which would let me do what I'm looking to do, but I see from this link https://github.com/procount/pinn/blob/m ... os-version
that it basically involves duplicating an OS before making changes to it, which is one way, but doesnt really allow for quick easy post mortem analysis, as I'd have to still shutdown and extract the SD card.
NOOBS and PINN both have instructions on how to create a custom OS for installation. (I see you found them already)321 wrote:How involved would it be to reverse the options to backup an OS image to web/usb/sd card?
PINN is a minimal OS in its own right that is used to install other OSes and act as a boot selector in the case of a multi-boot scenario. Once another OS is chosen, the Pi is rebooted directly into that OS, so PINN is not active in the background. To activate PINN you must reboot the Pi again. Think of it more like U-Boot rather than a hypervisor. So if you can automate a reboot then this may be a possible enhancement (by adding automation controls via ssh, for example) But I'd need some more details on what you would like to automate.321 wrote:In terms of automation....
As I said above, it could be a possible future enhancement. You can already install multiple OSes on the same SD card (or possibly multiple instances of the same OS with a bit of tweaking) and use PINN to select which one you want to use at any time if one goes corrupt, for example. But if you want to copy an OS off of the SD card to somewhere else for "quick easy post mortem analysis", then it may still take a while no matter how you copy it due to the typical size of an image. Maybe you could do it in-situ by mounting the inactive OS?321 wrote:Ideally I'd like to have an automated way to spin up and down different OS 's and backup to SD/USB/Web an OS for post mortem.
When you say mount it in-situ, do you mean using the running OS to copy the inactive OS/partitions back assuming two or more OS's exist on an sd card or usb mem stick? That is an option if they are all the same OS's, but more work if using non linux OS's like RiscOS and others ported to the pi.But if you want to copy an OS off of the SD card to somewhere else for "quick easy post mortem analysis", then it may still take a while no matter how you copy it due to the typical size of an image. Maybe you could do it in-situ by mounting the inactive OS?
I'll check that out, although the project spaces from a quick read seem to be really geared for a single pi, and I'm looking for a multi pi setup which I can use with my clusterhat.com automatically.mikerr wrote:You might like to take a look as "OS spaces" as supplied by WD:
http://wdlabs.wd.com/products/wd-pidriv ... n-edition/
http://www.gadgetoid.com/2017/02/16/wdl ... node-zero/
Unzip it and copy it to the SD card which should previously have been formatted as FAT32 with the SDformatter tool with the FORMAT SIZE ADJUSTMENT ON Option.
I am referring to the pinn-lite.zip file mentioned just above the 1st screenshot.Download and extract the files from the PINN zip file.
at the top, there is nothing to suggest what PINN-lite is, and thats what people need to download if they dont want to compile it using github.The latest version of PINN-lite can be downloaded from sourceforge.
The button does change colour which is supposed to indicate it is toggled (pressed-in). In a future version, this button's functionality is changing and this will be addressed.321 wrote: Having got net access and the list of OS's, when clicking the Advanced button, the existing buttons dissappear, from a user perspective especially the caution one's, they might not find it intuitive to click the Advanced button again to restore the original buttons, so maybe the text on the Advanced button could change to something like Back to make it more obvious.
Yes, always an issue. This will also affect NOOBS, so suggestions for replacement text are always welcome.321 wrote: One point about the error msg seen in edit1, whilst its displaying in part, system generated errors, from a novice user perspective these msg's are too technical, so if they could be translated into something more useful for users, that would be more useful.
NOOBS issue.321 wrote: One thing I have noticed having installed raspbian via pinn, the ext4 Settings partition shows in the Eject button (far right of the taskbar on raspbian desktop) as Ncards(SETTINGS),
Hopefully my recent update to README_SUM.md has addressed this? If so, I will copy the QuickStart info across.321 wrote: Edit3
https://github.com/procount/pinn/blob/m ... ME_PINN.md
Where it saysat the top, there is nothing to suggest what PINN-lite is, and thats what people need to download if they dont want to compile it using github.The latest version of PINN-lite can be downloaded from sourceforge.
Point taken, but as this is a derivative of NOOBS, PINN-LITE is more closely aligned to NOOBS-LITE.321 wrote: https://github.com/procount/pinn/blob/master/README.md
Is similar to the above point, in that theres nothing to suggest what PINN-lite is, so some people might interpret PINN-lite as being like raspbian-lite, in thats its a headless os, when in fact PINN-lite is not really a headless OS.
All the command line options for recovery.cmdline are in https://github.com/procount/pinn/blob/m ... ME_PINN.md But maybe a section grouping them altogether would be good. Please see the 'silentinstall' option for an automated install which removes the confirmation dialogs. I intend to improve on the 'silentinstall' option to remove some of the existing limitations and make it more flexible.321 wrote: Where would be the best place to find a brief or concise list or table of the different command settings that can be used to configure PINN? The reason I ask about this, is right now, the raspbian OS has downloaded and the msg box saying something to that effect with an OK button is on screen. For an automated installation, it would be useful to have the msg box with the OK button not appear but for PINN to automatically reboot and load the OS.
Do you mean enabling VNC/SSH etc for Raspbian?321 wrote: A nice to have feature if it doesnt exist at the moment, which you might have already done with https://github.com/procount/pinn/blob/m ... xt.example is to have the options to set the options that enable/disable things like VNC & SSH.
I dont know if its possible to get PINN to also copy across a script file which can be run on first boot to save me having to copy across my scripts and run then. Some of my scripts involve downloading code and then compiling as they are not in the main repositories whilst other scripts are just downloading packages before making config changes.
PINN already supports VNC and SSH if you enable them. You can use these tools to remotely tweak your setup or administer it. NOOBSCONFIG/PiKitchen can be used to alter the config.txt of an OS when it is being installed.321 wrote: Feature request. A way to remotely edit the config.txt file of the OS in question.
When tweaking the config.txt files, if a settings change causes raspbian to not boot up, whilst you can recover using the edit button, having a way to remotely edit this file would be useful.
Will do, I guess I cant put off using github any longer.procount wrote:It might be better to consider putting future suggestions there, and leaving this thread for questions.