Jump to content

Igor

Administrators
  • Posts

    13602
  • Joined

  • Last visited

Posts posted by Igor

  1. I just made an update from 5.05 and all went fine.

     

    Mount SD card on some Linux machine and tell me the content of /boot folder. Next: change those boot parameters, 

     

    console=ttymxc0 loglevel=7

     

    attach serial console and try to boot:

  2. Hi - Any information or links on how to install directly to emmc flash - Many thanks

    Armbian, not possible, only via SD card boot first method.

     

    @mdel

     

    I don't see any problems. Network works as expected ... desktop version uses Network Manager, where this could be possible.

     

    Shutdown looks like it manifest to reboot? It works properly on some boards but I guess not on all ... need to be investigated.

  3. With buildroot you will get worse results for sure, forget about. Their tool is generic while we are specialised for those ARM boards, especially we know a lot about Allwinner chips. Additionally you have to expect much more troubles to make things together since the tool is complex.
     

    Our desktop is already as light as possible and you won't achieve any vivid (if any) speed improvements if you change window manager. XFCE is among the light ones. Furthermore our desktop build has build-in all possible acceleration methods: 3D and video playing but I guess they don't help your type of usage.

     

    If you installed system on eMMC you are already on the edge - you can only try some good SSD drive for system - via USB. If you are running our of memory, get an Opi +2e ... it has faster eMMC and 2GB of memory.

  4. ill you be doing easy-reproducible builds? 

     

    Builds can be reproducible but they might not be exactly since we are attached to external source projects and we are fixing things daily.

     

    Does the build process only fetch verified sources from other projects? (even xen still uses http wget lol)

     

    Sources are more or less trusted (mainline kernel and uboot, legacy sources maintained by vendors, some community, some mixed, ...). They are git cloned with https, so nothing gets in between.

     

    Do you have a reasonable level of build process security and dev computer security? (ie, a qubes type security model for all your devs)

     

    Each developer has it's own environment and our common end result is public on Github. Code is review upon commits so I would say yes. Official build is (so far) always done by me on a dedicated hardware, accessible locally and output is securely transferred to download server which will get ssl when admin of the server gets up and finds time.

     

    Armbian project is still a small one no matter of importance. Our core team resources and budget are tiny, on a hobby level, so even some things are possible, we might not be able to afford them. But we take security seriously and possible problems will be fixed ASAP ... just this ASAP will take longer :)

     

    Sometimes is hard to see even most obvious things so I only thank you for bringing ideas up. I certainly don't want that our work becomes involved in something like this :o:)

  5. For download images it's trivial indeed and will be done asap. The rest we need to check manuals (wordpress, nginx, ispconfig, IPboard) and it's a task, with unknown time of execution at this point.

     

    BTW. My public pgp key is stored on a public keyserver. In any case, our primary objective is a build tool so if you are afraid on security -> build your own image from sources (with our tool or manually) Even this way, you need to trust that sources are good and fully checked ...

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines