Difference between revisions of "OS: Android - Mirror Source"

From OnnoWiki
Jump to navigation Jump to search
(New page: Using a local mirror When using several clients, especially in situations where bandwidth is scarce, it is better to create a local mirror of the entire server content, and to sync clien...)
 
Line 5: Line 5:
 
These instructions assume that the mirror is created in /usr/local/aosp/mirror. The first step is to create and sync the mirror itself, which uses close to 13GB of network bandwidth and a similar amount of disk space. Notice the --mirror flag, which can only be specified when creating a new client:
 
These instructions assume that the mirror is created in /usr/local/aosp/mirror. The first step is to create and sync the mirror itself, which uses close to 13GB of network bandwidth and a similar amount of disk space. Notice the --mirror flag, which can only be specified when creating a new client:
  
  $ mkdir -p /usr/local/aosp/mirror
+
Lakukan sebagai user biasa
  $ cd /usr/local/aosp/mirror
+
 
  $ repo init -u https://android.googlesource.com/mirror/manifest --mirror
+
  sudo mkdir -p /usr/local/aosp/mirror
  $ repo sync
+
  sudo mount --bind /media/onno/onnolibrary/repository/android-source/mirror/ /usr/local/aosp/mirror/
 +
sudo chmod -Rf 777 /usr/local/aosp
 +
sudo chown -Rf nobody.nogroup /usr/local/aosp
 +
cd /usr/local/aosp/mirror
 +
  repo init -u https://android.googlesource.com/mirror/manifest --mirror
 +
  repo sync
  
 
Once the mirror is synced, new clients can be created from it. Note that it's important to specify an absolute path:
 
Once the mirror is synced, new clients can be created from it. Note that it's important to specify an absolute path:
  
  $ mkdir -p /usr/local/aosp/master
+
Lakukan sebagai userbiasa
  $ cd /usr/local/aosp/master
+
 
  $ repo init -u /usr/local/aosp/mirror/platform/manifest.git
+
  mkdir -p /usr/local/aosp/master
  $ repo sync
+
  cd /usr/local/aosp/master
 +
  repo init -u /usr/local/aosp/mirror/platform/manifest.git
 +
  repo sync
  
 
Finally, to sync a client against the server, the mirror needs to be synced against the server, then the client against the mirror:
 
Finally, to sync a client against the server, the mirror needs to be synced against the server, then the client against the mirror:

Revision as of 10:26, 10 August 2013

Using a local mirror

When using several clients, especially in situations where bandwidth is scarce, it is better to create a local mirror of the entire server content, and to sync clients from that mirror (which requires no network access). The download for a full mirror is smaller than the download of two clients, while containing more information.

These instructions assume that the mirror is created in /usr/local/aosp/mirror. The first step is to create and sync the mirror itself, which uses close to 13GB of network bandwidth and a similar amount of disk space. Notice the --mirror flag, which can only be specified when creating a new client:

Lakukan sebagai user biasa

sudo mkdir -p /usr/local/aosp/mirror
sudo mount --bind /media/onno/onnolibrary/repository/android-source/mirror/ /usr/local/aosp/mirror/
sudo chmod -Rf 777 /usr/local/aosp
sudo chown -Rf nobody.nogroup /usr/local/aosp
cd /usr/local/aosp/mirror
repo init -u https://android.googlesource.com/mirror/manifest --mirror
repo sync

Once the mirror is synced, new clients can be created from it. Note that it's important to specify an absolute path:

Lakukan sebagai userbiasa

mkdir -p /usr/local/aosp/master
cd /usr/local/aosp/master
repo init -u /usr/local/aosp/mirror/platform/manifest.git
repo sync

Finally, to sync a client against the server, the mirror needs to be synced against the server, then the client against the mirror:

$ cd /usr/local/aosp/mirror
$ repo sync
$ cd /usr/local/aosp/master
$ repo sync

It's possible to store the mirror on a LAN server and to access it over NFS, SSH or Git. It's also possible to store it on a removable drive and to pass that drive around between users or between machines.


Referensi