wildcat_paris

I added extra info message to patching function, this should help a bit
[ o.k. ] Started patching process for [ u-boot u-boot-next 2015.10 ] [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-next ]

@wildcat_paris,
Did you make and install board-specific package (linux-trusty-root-next-lamobo-r1_5.00_armhf.deb or something similar)?
I ran 
./compile.sh BRANCH=next BOARD='lamobo-r1' KERNEL_ONLY=yes PROGRESS_DISPLAY=plain RELEASE=trusty  [ o.k. ] Building deb package. [ linux-trusty-root-next-lamobo-r1_5.00_armhf.deb ] #dpkg-deb -c linux-trusty-root-next-lamobo-r1_5.00_armhf.deb | grep '/usr/local/bin' drwxr-xr-x root/root 0 2015-12-14 16:06 ./usr/local/bin/ -rwxr-xr-x root/staff 15531 2014-06-03 13:17 ./usr/local/bin/temper -rwxr-xr-x root/root 25528 2015-12-14 16:06 ./usr/local/bin/meminfo -rwxr-xr-x root/root 27244 2015-12-14 16:06 ./usr/local/bin/nand-part -rwxr-xr-x root/root 46614 2015-12-14 16:06 ./usr/local/bin/sunxi-fexc -rwxr-xr-x root/root 34868 2015-04-02 19:37 ./usr/local/bin/swconfig -rwxr-xr-x root/root 16943 2015-12-14 16:06 ./usr/local/bin/brcm_patchram_plus Files are present in board support package, but as far as I see this package is not installed to image, maybe Igor didn't finish this part yet.

it's possible since there were so many changes. I'll look into this part and fix.

more testing...
 
 

Yes, thanks. I already have this on my todo list for unmounting loop devices after debootstrap process.

I already did something like that, prepare_host function duplicates directory structure from lib/patch to userpatches

Then it must be packaging error, not compiling. I didn't touch it (yet) and so didn't test it. Maybe will check later.

http://linux-sunxi.org/Sunxi_devices_as_NAS#Benchmarking_.2F_Identifying_bottlenecks
 
"Always test from bottom to top" means: Use iperf to identify whether it's network related.

I think it's more right to declare relationship between kernel packages so they cannot be installed at the same time.
If I understand this right, it should be something like this in the kernel package control file:
Provides: linux-image Conflicts: linux-image Replaces: linux-image Right now it doesn't have "Conflicts" and "Replaces" fields.
➜ ~ % apt-cache show linux-image-next-sunxi Package: linux-image-next-sunxi Status: install ok installed Priority: optional Section: kernel Installed-Size: 14180 Maintainer: Igor Pecovnik <****l.com> Architecture: armhf Source: linux-4.3.0-sunxi Version: 4.6 Provides: linux-image, linux-image-2.6, linux-modules-4.3.0-sunxi Suggests: linux-firmware-image-next-sunxi Description: Linux kernel, version 4.3.0-sunxi This package contains the Linux kernel, modules and corresponding other files, version: 4.3.0-sunxi. Description-md5: 117a3231b09bf7ccdf0ae5d4ec6b8c5f Homepage: http://www.kernel.org/ Edit:
This is only the beginning  I mean, beginning of improvement, not of introducing tons of bugs, I hope 

This lamobo fix was "lost in the crash" together with others small fixes yet to be rediscovered
 
 
Agreed. I used to merge others snippets via Github pull request. My git handling knowledge need some upgrading I see it's simple but I will do a tests before. ASAP
 
I fixed download / patching part ... will update when I fix this .config part and made few test runs.
 
EDIT: I added another remote to my branch and made some merging w/o problems but I got quite some conflicts which needs slow manual resolving. 

@Skygod: I don't know how different M1+ is from M2, of which Hosteiner mentioned it works fine. If there is a difference, it would be cool to see it it works on the M1+ as well!
 
@Holsteiner: The Docker version in this image is probably by far not latest, but will probably work fine, which is good to see!
 
Performance of Docker? Like charm :-) See this is docker daemon without any containers:
$ ps -p 1277 -o %cpu,%mem,cmd %CPU %MEM CMD  1.1  2.8 /usr/bin/docker daemon -H fd:// --storage-driver=overlay -D Let's start 20 webservers (https://hub.docker.com/r/hypriot/rpi-busybox-httpd/), i.e. starting 20 containers, and check again:
%CPU %MEM CMD  6.5  3.4 /usr/bin/docker daemon -H fd:// --storage-driver=overlay -D Note, that this is just the Docker daemon as "container manager" instance!
 
For each container, Docker starts 4 processes. Please do not ask me why. Let's rather have a look at CPU and RAM:
With 20 webservers running, CPU usage in total and average is about 4%. Before starting these 20 containers, it was a bit more than 2% in average.
RAM usage is 162 MB. Before starting the 20 containers, it was 46 MB.
 
So in general, only the Docker daemon is put on top. For containers, Docker's footprint is about the same as if you run apps natively. For this test, I used HypriotOS (http://blog.hypriot.com/) on a Raspberry Pi 2 B.
You also can define how much CPU and RAM a container is allowed to have at max, and also in relation to other containers. Docker offers many options to make sure you are in control about available resources.
 
And, BTW, with some tweaking, it's possible to start 2500 containers on a single Raspberry Pi with Docker :-) -> https://blog.docker.com/2015/10/raspberry-pi-dockercon-challenge-winner/
 
@September: I can see that several containers are running, which shows that Docker works well, awesome! Thanks for your feedback! Yeah, we are not sure yet how much work it is, but we at least try to get together...

Hello,
 
Interested in replacing virtualbox as a VM host, "docker" tool seems to be able to run on Debian/Ubuntu/other linux distro/MacOS/Windows (as they claim)
 
 
 
My test:
 
1/
Installing docker on my amd64 4-cores Ubuntu 14.04 (too much tweaking to run "armbian" properly)
see doc here also I have been using "Create a Docker group" and don't forget to run "Hello World" test
 
2/
To create a new container with Ubuntu 14.04 (if you have added docker group to your non-privileged user, if not use "sudo")
 
$ docker run --privileged -i -t ubuntu:14.04 /bin/bash
 
"privileged" is needed for /dev/loop operations, if not the container cannot see the loop device, btw it is less "secure" but not "really" applicable here, I am on my test system.
 
on the host system, the files are stored in "/var/lib/docker", you can move this folder on another HDD/SSD, then you need to (in my example) "cd /var/lib; ln -s /home4/docker docker"
 
3/
once you have the root shell of the VM
 
# mkdir /root/armbian
# cd /root/armbian
 
then feel free to follow the Armbian tool instructions
 
Once all is compiled & package, you can transfer the files with "sftp", "ftp", etc. Or if you want a challenge, grab the files in /var/lib/docker (good luck!)
 
4/
later to come back to the container, list the containers, get the "Container ID" then start the container
$ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e12d3a2b9263 ubuntu:14.04 "/bin/bash" About an hour ago Up About an hour grave_ardinghelli d1efa716ad64 hello-world "/hello" 8 hours ago Exited (0) 8 hours ago elegant_meitner $ docker start -i e12d3a2b9263 (to be tested more carefully)
 
edit:
you need the "under work" script attached as the ubuntu:14.04 is *not* really a ubuntu server packaged style!
 
edit2:
[ o.k. ] Fixing release custom applications. [ jessie ] [ o.k. ] Install board specific applications. [ lamobo-r1 ] [ o.k. ] Fingerprinting. [ Armbian 4.6 Lamobo-r1 Debian jessie next Linux 4.2.6 ] [ o.k. ] Creating boot scripts [ lamobo-r1 ] [ o.k. ] Possible after install. [ o.k. ] Writing boot loader [ /dev/loop1 ] [ o.k. ] Shrink image last partition to [ minimum ] [ o.k. ] Create and sign [ Armbian_4.6_Lamobo-r1_Debian_jessie_4.2.6.zip ] [ o.k. ] Runtime [ 81 min ] et voilà !
 
more testing needed

I know.  More and better comments are needed. I made few test runs and it looks good ... busy with life until evening.

My logic with oldconfig/olddefconfig is:
if KERNEL_CONFIGURE is true, then process is designed to be interactive and it will ask about new options before bringing menu configuration dialog;
otherwise process is not interactive, and it won't ask users about some new kernel options if they don't want to mess with kernel configuration at all, safe defaults will be assumed for new options.
 
If you don't like this, you can change it to always be oldconfig, it's not 100% needed.
 
Make *config right now doesn't use dialog as far as I see.
 
I'll try to implement this next.

I am done until evening. 

Some ideas: 
- I need to see new kernel features, so make olddefconfig / oldconfig must be an option and always out of dialog
- this dialog on/off option would be cool also a blank, no console output, only log
- when mostly done we can alter/adjust script names 

Implemented something similar: https://github.com/zador-blood-stained/lib/commit/8e1551e9faef962d4abca603fe6d8f88d377075b, Igor can merge this if he likes it.
Options are not documented in compile.sh for now and are not dependent on each other. Affect only kernel & u-boot compilation for now.
USE_DIALOG is enabled by default,
USE_DIALOG_LOGGING is disabled by default; writes to output/debug/compilation.log if enabled (also deletes this file before new compilation).

Cool ! 
 
I gave up on this "advanced" git handling, now changing kernel and u-boot sources. Each tags will have own subdir, all with shallow clone of course.
 
u-boot-odroid/unttaged
u-boot-odroid/2015.10
u-boot-odroid/2015.04
 
... kernel likewise. According to this, I'll fix the compilation part so ... 

Fixed dtb compilation (removed extra space in 0013-lamobo_r1_dts.patch at the beginning of the line).
Mainline kernel compilation is working.
[ o.k. ] Kernel building done [ @host ] [ o.k. ] File name [ linux-image-next-sunxi_5.00_armhf.deb ] [ o.k. ] Runtime [ 4 min ] BTW, you can add my repo as another remote and merge commits or even branches from it, this way it will be easier for me to merge your changes back into my working copy (and it may be faster and easier for you).
 
Edit: some config names are broken after configuration update:
[ o.k. ] Compiling kernel [ @host ] cp: cannot stat ‘/home/zador/armbian/lib/config/linux-sun7i-default.config’: No such file or directory

Hm. I tested it briefly on cubietruck sun7i kernel, it got all patches from /lib and it skipped fbtft patch when I created empty file userpatches/kernel/sun7i-default/fbtft_for_older.patch
I'm waiting for your solution to passing correct LINUXFAMILY to patching function to do proper tests.
What exactly did you test?
 
Edit: Just checked. Works like intended for me
➜ ~ % cd armbian/userpatches/kernel/sun7i-default ➜ sun7i-default % _ cp ~/armbian/lib/patch/kernel/small_lcd_drivers.patch test-patch.patch ➜ sun7i-default % ~ ➜ ~ % armbian ➜ armbian % ./compile.sh BOARD=cubietruck KERNEL_ONLY=yes BRANCH=default .... .... [ o.k. ] ... test-patch.patch sun7i-default 3.4.104 [ succeeded ]

A bug
 
This is also an exception. When added to configuration it should work properly, like for .configs
https://github.com/igorpecovnik/lib/blob/master/configuration.sh#L269-L270
 
https://github.com/zador-blood-stained/lib/blob/master/patching.sh#L147
This part can be dumped. I made patches, fbtft sources are not changing anymore. It has been merged into mainline for some time.
 
Tnx.
 
I'll try later to merge this together
 
EDIT:
adv.patches doesn't collect my custom patches even they are in proper dir.

https://github.com/zador-blood-stained/lib   Changelog:   Edit: made some fixes
 
Testing patching process: for mainline stable kernel "$LINUXFAMILY-$BRANCH" parses to "sun7i-next" or "sun4i-next" instead of "sunxi-next". Is this a bug or a feature? 
 
Edit 2: pushed advanced_patching changes. Mainline patches are still broken due to wrong $LINUXFAMILY

I had a productive morning. I manage to rework:
- conf
- fetch from github (i am a bit confused if it can be solve this "fully optimized" way)
 
Things are (probably) not working properly yet since I had no time for any serious debug.

A break would be the best / most productive. I'll see how I'll feel in the morning
 
If you wants to jump in - I'll work on the configuration.sh + few things in main.sh for a while.
 
... better sources handling is a open part or even only the code cleaning, where is needed, cpu speed fixes ... $GOVERNOR will be now in config.

That's unfortunate 
So do you mean that you'll start rewriting all again tomorrow or you will take a break for few days?

┌───────────────────────┤ Choose a board ├────────────────────────┐ │ │ │ Supported: │ │ │ │ cubieboard4 A80 octa core 2Gb SoC Wifi │ │ aw-som-a20 A20 dual core SoM │ │ cubieboard A10 single core 1Gb SoC │ │ cubieboard2 A20 dual core 1Gb SoC │ │ cubietruck A20 dual core 2Gb SoC Wifi │ │ lime-a10 A10 single core 512Mb SoC │ │ lime A20 dual core 512Mb SoC │ │ lime2 A20 dual core 1Gb SoC │ │ micro A20 dual core 1Gb SoC │ │ pcduino3nano A20 dual core 1Gb SoC │ │ bananapim2 A31 quad core 1Gb SoC Wifi │ │ bananapi A20 dual core 1Gb SoC │ │ bananapipro A20 dual core 1Gb SoC Wifi │ │ lamobo-r1 A20 dual core 1Gb SoC Switch │ │ orangepi A20 dual core 1Gb SoC Wifi USB hub │ │ orangepimini A20 dual core 1Gb SoC Wifi │ │ orangepiplus H3 quad core 1Gb SoC Wifi USB hub │ │ cubox-i Freescale iMx dual/quad core Wifi │ │ udoo Freescale iMx dual/quad core Wifi │ │ udoo-neo Freescale iMx singe core Wifi │ │ guitar S500 Lemaker Guitar Action quad core │ │ odroid Exynos5422 XU3/XU4 octa core │ │ │ │ │ │ │ │ │ │ │ │ <Ok> <Cancel> │ │ │ └─────────────────────────────────────────────────────────────────┘ This far I got:
 
- added few new boards
- proper git sources switching
- completely reorganized configuration
- legacy / next / dev versions
- 80% of code cleaned.
 
Starting tomorrow from here:
https://github.com/igorpecovnik/lib