Archive for October, 2016

Just found out from somewhere than syncfusion is offering free license for lifetime which includes all the products. No Strings attached.


Here’s the link. Please tell everyone there’s nothing better than getting everything for free with future support and everything legit too!

Well, Most of the times I see hundreds of projects in a single repo. Now, if I don’t want to download a GB of code and then eventually use just 20mb of it. How is it fare?

So I wanted to create a downloader for it. Turns out I’m a little too late. There are already a couple of options which work flawlessly.

Go ahead and give it a try!

 


Git doesn’t support this, but Github does via SVN. If you checkout your code with subversion, Github will essentially convert the repo from git to subversion on the backend, then serve up the requested directory.

Here’s how you can use this feature to download a specific folder. I’ll use the popular javascript librarylodash as an example.

  1. Get the repo URL. First, copy the URL of the Github repo to your clipboard. github repo URL example
  2. Modify the URL for subversion. I want to download the folder at /docs from the masterbranch, so I will append trunk/docs. Full URL is now https://github.com/lodash/lodash/trunk/docs. See my note below for a more in-depth explanation of why we must use this URL format.
  3. Download the folder. Go to the command line and grab the folder with SVN. svn checkout https://github.com/lodash/lodash/trunk/docs

You might not see any activity immediately because Github takes up to 30 seconds to convert larger repositories, so be patient.

Full URL format explanation:

  • If you’re interested in master branch, use trunk instead. So the full path is trunk/foldername
  • If you’re interested in foo branch, use branch/branchname instead. The full path looks like branch/branchname/foldername
  • Protip: You can use svn ls to see available tags and branches before downloading if you wish

That’s all! Github supports more subversion features as well, including support for committing and pushing changes.

 

 

Instead of letting Berryboot download operating system image files straight from the Internet, it is also possible to have a local repository in your own network.

Steps required:

1) Obtain image files

Download the Operating System image files you wish to offer on your local repository from the Internet to your local computer.

2) Put the downloaded files on a Windows file sharing (CIFS) network share

3) In the Berryboot “Add OS” Windows, press the “Network settings” button, go to the tab “repository” and enter the IP-address of your server, and the name of the share, in the format:

If no username and password is provided, Berryboot will try to login to the network share as “guest”
The settings are saved in berryboot.ini on the FAT partition of the SD card.

Berryboot screenshot

For people short on SD cards: Berryboot is a simple boot selection screen for ARM computers like the Raspberry Pi, that allows you to put multiple Linux distributions on a single SD card.
In addition it allows you to put the operating system files on an external USB hard drive instead of on the SD card itself.

Download link Berryboot for the original Raspberry Pi and Pi Zero: berryboot-20160209-pi0-pi1.zip
sha1sum: f8cfc1b4f57e0b6886569091ca7e277d33ffee0f

Download link Berryboot for the quad-core Raspberry Pi 2 and Pi 3: berryboot-20160930-pi2-pi3.zip
sha1sum: 7f44898dcca58cd4c1562273a44121c90e3543ab

To install: extract the contents of the .zip file to a normal (FAT formatted) SD card, and put it in your Raspberry Pi. This can be simply done under Windows without any special image writer software.
Once you start your Pi it will start an installer that reformats the SD card and downloads the operating systems files from the Internet.

Changelog

→ Moved to: Berryboot Changelog

Walkthrough

If your Pi is connected to the Internet BerryBoot will try to detect your location based on your IP-address, and set the right timezone automatically. Verify that it is correct and press “ok”

Select where you want to store the operating system files, and press “format”
You can choose to install the operating system files:

Be aware that if you choose an external drive, the files of the operating system will be stored there, but you still need to keep the SD card in the Pi to boot from.

WARNING: all existing files on the disk will be erased.

Select which operating system you want to install. You can add more later.

It will download the files from the Internet automatically.

In the Berryboot menu editor you can install more operating systems, rename them, delete them, etc. Press “exit” to exit the editor and start using the operating system you installed.

HDMI CEC support

When attached to a HDMI TV, you can also use the arrows on your TV remote to select an operating system to boot, instead of using your keyboard or mouse.

Available options in menu editor

  • “Add OS” (or CTRL+A on keyboard, red button on TV remote)
    Single click to download additional operating systems from the Internet.
    Hold down your mouse button over the “Add OS” button and select “copy OS from USB stick”, to install an operating system saved on USB stick.
  • “Edit” (or ENTER on keyboard)
    Change the name of the selected operating system.
    You used to be able to change the memory split setting here as well, but for new installations (that have CMA enabled) this is no longer used.
  • “Clone”
    Creates a copy of the selected operating system.
    It is possible to create either a copy that includes the file system changes you made, or create a copy of the original operating system image as downloaded from the Internet.
  • “Backup”
    Creates a backup of a single operating system or all of them to a USB stick, or SD card (requires USB SD card reader).
    Backups of individual images can be restored by holding down the “add OS” button and selecting “copy OS from USB stick”
  • “Delete” (or DEL on keyboard)
    Deletes the files of the selected operating system.
  • “Make default”
    Makes the selected operating system the default. On boot, this operating system will be started automatically unless another is selected within a number of seconds.
  • “Exit” (or ESC on keyboard)
    Exits the menu editor.

Advanced options

Click on the ”»” button to the right of the screen to see all options.

  • “Advanced configuration”
    Editor for configuration files such as cmdline.txt and config.txt

When using a Raspberry Pi you can specify kernel parameters and Berryboot parameters in cmdline.txt (use uEnv.txt if you have another device).
Special Berryboot parameters:

bootmenutimeout=<number of seconds> - number of seconds before default operating system is started. nobootmenutimeout - do not start the default operating system automatically.

In config.txt advanced overscan, HDMI and overclocking settings can be specified. See the RPIconfig page on eLinux.org for details.
Note that overclocking is known to cause SD card filesystem corruption, so only use that when you are using an USB stick or drive as storage and know what you are doing.

  • “Console”
    Activates a console on tty2
    Press CTRL+ALT+F2 to access, username “root”, no password.
  • “Set password”
    Password protects access to the menu editor, so that unauthorized users cannot delete or edit the operating systems.
  • “Repair filesystem”
    Performs a file system check and repair. Attempts to repair file system corruption. Can perform a lot of writes to the SD card, so you might want to make a backup of important files first.

Acestream Engine, (as of 28/04/2016) unofficial version 3.1.5, for the Raspberry Pi 2 and 3.

Unofficial because it is closed source and the Acestream developers do not provide binaries for Linux ARM (only for more popular platforms), so no official support for the Raspberry Pi.
And as some may know, the Acestream Engine/module for the Raspberry Pi from the Plexus Kodi addon, stopped working recently, so this is the updated engine to fix it.

### Installation ###

For this to work, you need the Plexus Addon already installed in Kodi. The Plexus Kodi addon was discontinued by the developer but it still works. You can find it easily on the web.

Then open a virtual terminal, for example via SSH, and run the following commands (you can copy/paste to terminal):

cd ~/.kodi/userdata/addon_data/program.plexus
sudo rm -r acestream
wget https://dl.bintray.com/pipplware/dists/unstable/armv7/misc/acestream_rpi_3.1.5.tar.gz
tar xfv acestream_rpi_3.1.5.tar.gz

Done. Then you can play acestreams again.

PS: If you are running an OS as root, like OpenELEC, you may need to remove the “sudo” on the second line.

### Notes ###

Another way that may work is to download the tarball, and via network, extract it to the correct directory. This was not tested!

It is also possible to use this acestream engine without the need to install the Plexus addon, like standalone mode, but it may depend on your OS. There are already some tutorials on how to do this, so do some web searches if you want it.