Jump to content

tparys

Members
  • Posts

    198
  • Joined

  • Last visited

Reputation Activity

  1. Like
    tparys got a reaction from Werner in armbian-config RFC ideas   
    So, started playing around a bit. Mostly just mocking up ideas.
     
    https://github.com/tparys/armbian-reconfig
     
    The script currently is recursively driven by a directory system. When it hits a script, it simply executes it. Should be pretty easy to extend. Just drop a script in place and it should use it.
     
    I mulled over how to "name" the various scripts and directories, and eventually settled on using gettext, which also provides internationalization support as well. Basically takes the relative menu location like "/system/firmware" and "translates" into the appropriate language. In the case that only partial translations exist, it falls back to English, which i figured wasn't a horrible default.
     
    And for testing, I added some translations of the top level menu to Spanish. I did use Google Translate, as my bash-fu is strong and my Spanish is quite rusty.
  2. Like
    tparys got a reaction from Igor in armbian-config RFC ideas   
    So, started playing around a bit. Mostly just mocking up ideas.
     
    https://github.com/tparys/armbian-reconfig
     
    The script currently is recursively driven by a directory system. When it hits a script, it simply executes it. Should be pretty easy to extend. Just drop a script in place and it should use it.
     
    I mulled over how to "name" the various scripts and directories, and eventually settled on using gettext, which also provides internationalization support as well. Basically takes the relative menu location like "/system/firmware" and "translates" into the appropriate language. In the case that only partial translations exist, it falls back to English, which i figured wasn't a horrible default.
     
    And for testing, I added some translations of the top level menu to Spanish. I did use Google Translate, as my bash-fu is strong and my Spanish is quite rusty.
  3. Like
    tparys got a reaction from guidol in What diffirend armhf and arm64 for .deb packets?   
    Some additional information for the curious ... https://www.debian.org/ports/arm/
    The ARM EABI (armel) port targets a range of older 32-bit ARM devices, particularly those used in NAS hardware and a variety of *plug computers. The newer ARM hard-float (armhf) port supports newer, more powerful 32-bit devices using version 7 of the ARM architecture specification. The 64-bit ARM (arm64) port supports the latest 64-bit ARM-powered devices.
  4. Like
    tparys got a reaction from gounthar in Creating an Armbian Docker image for armhf (Orange Pi Zero)   
    Armbian is little more than a stock Debian/Ubuntu installation with the aim of providing recent kernel, bootloaders, and some quality of life userspace customizations.
     
    None of those seem needed for a docker image. Maybe start with the upstream image of whichever version you're using for your Orange Pi?
     
    If you do need certain things from Armbian, you can always copy the apt configuration from /etc/apt/sources.list or sources.list.d into your Dockerfile and go from there.
     
     
  5. Like
    tparys got a reaction from lanefu in armbian-config RFC ideas   
    I suppose my question was less where you would run it, and rather what exactly you would want to test.
     
    Unit tests are great for functional libraries with known inputs/outputs, but are somewhat trickier with user interfaces.
     
    Testing the individual scripts should be more possible if you're looking for actual run products (eg - changes to /etc/apt/sources, or edits to config files).
  6. Like
    tparys got a reaction from TRS-80 in armbian-config RFC ideas   
    As a fun little hack, here's a little example wrapper for the dialog program. Mark it executable, toss it in /usr/local/bin, and fire up armbian-config.
     
    Obviously delete it afterwards. don't leave it there. That's probably a bad idea.
     
    But might work as a brief tech demo of what an X11 driven armbian-config might look like ...
     

    dialog
  7. Like
    tparys got a reaction from Igor in armbian-config RFC ideas   
    As a fun little hack, here's a little example wrapper for the dialog program. Mark it executable, toss it in /usr/local/bin, and fire up armbian-config.
     
    Obviously delete it afterwards. don't leave it there. That's probably a bad idea.
     
    But might work as a brief tech demo of what an X11 driven armbian-config might look like ...
     

    dialog
  8. Like
    tparys got a reaction from lanefu in armbian-config RFC ideas   
    So, there are GUI based dialog frontends. Where you would do something like this in dialog:
     
    $ dialog --menu "Choose an option" 0 0 0 a argle b bargle  
    Or whiptail ...
     
    $ whiptail --menu "Choose an option" 0 0 0 a argle b bargle  
    You could use a different frontend like zenity to do something similar. Obviously the arguments would change:
     
    $ zenity --title "Choose an option" --column tag --column Description --list a argle b bargle  
    If you could distill it down to minimum information required to populate either list, you could have a bash wrapper that just calls the specified frontend, or just defaults to the GUI version if the $DISPLAY variable is set.
  9. Like
    tparys got a reaction from lanefu in armbian-config RFC ideas   
    As a fun little hack, here's a little example wrapper for the dialog program. Mark it executable, toss it in /usr/local/bin, and fire up armbian-config.
     
    Obviously delete it afterwards. don't leave it there. That's probably a bad idea.
     
    But might work as a brief tech demo of what an X11 driven armbian-config might look like ...
     

    dialog
  10. Like
    tparys got a reaction from Werner in armbian-config: Add apt mirror selection   
    https://github.com/armbian/config/pull/135
     
    In case anyone wants to try and break it.
     
  11. Like
    tparys got a reaction from Werner in Armbian as read-only   
    I know this topic's already marked solved, however wanted to add something interesting that I found in my travels.
     
    If for some reason a software software controlled read-only switch isn't sufficient, it is actually possible to make a MicroSD card read-only.
     
    https://github.com/BertoldVdb/sdtool
     
    I'll still echo that overlayroot is generally the way to go. But in some applications that may not be sufficient.
     
    And the permlock function does work as advertised.
  12. Like
    tparys got a reaction from lanefu in Armbian as read-only   
    I know this topic's already marked solved, however wanted to add something interesting that I found in my travels.
     
    If for some reason a software software controlled read-only switch isn't sufficient, it is actually possible to make a MicroSD card read-only.
     
    https://github.com/BertoldVdb/sdtool
     
    I'll still echo that overlayroot is generally the way to go. But in some applications that may not be sufficient.
     
    And the permlock function does work as advertised.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines