![](/uploads/1/2/7/1/127187895/687991144.jpg)
![Dev21 installer ps2 Dev21 installer ps2](http://www.dev21.fr/wp-content/uploads/2016/06/climatisation_reversible_1.jpg)
Cari file DEV21.ELF yang tadi dicopy di flash disk Pilih DEV21.ELF dan tekan lingkaran, maka BOOT.ELF akan diinstal ke HDD, ikuti instruksinya seperti gambar dibawah ini Jika Hardisk Pada Playstation anda terdeteksi maka tampilanya seperti gambar dibawah Tekan kali untuk instal BOOT.ELF ke HDD.
VersionDownloadsLast updated322797/9/20173257/9/20172897/9/20172707/3/20172857/3/20172817/3/2017282829273292/4/201738512/6/201634512/6/201632129127131228029328230031611/3/201631911/2/201628511/1/201628711/1/201628911/1/201630011/1/201629611/1/201629411/1/201629711/1/201629911/1/2016298316321303308312Info.last updated 11/1/2016.(369.75 KB).Statistics.13,440 total downloads.299 downloadsof current version.11 downloadsper day (avg)Owners.AuthorsEmitter.Runtime CopyrightMisakai Ltd.
Contents.Overview For developers of Chromium OS there are many helpful packages included as part of developer and test images that are not included as part of Chrome OS. Bootstrapping and getting these back into the system can be very difficult without re-imaging the entire device. Ideally, you'd be able to get these packages back but still auto-update the rest of the system. Dev-install solves this use case. In essence it restores /usr/local back to that of a developer image.The requirements are:. In developer mode.The installation of software is done through Gentoo's emerge. In order to get emerge configured, follow the following steps:.
Boot the machine and go to a shell (login and go to crosh (ctrl+alt+t) or change to virtual terminal 2 (CTRL+ALT+F2)). Change to root and initialize the login environment variables. # devinstall -reinstallAnother source of problems is devinstall trying to connect to an incorrect BINHOST.
![Dev21 Installer Dev21 Installer](/uploads/1/2/7/1/127187895/924447977.jpg)
The symptom for this is devinstall exiting after trying to extract the first download package (the package file downloaded with curl in /usr/local/portage/packages/. Will contain a html error message). The binhost is generated by the release buildbots, so it is possible that a developer builds a new image with a release number that it's the same as a failed builbot. For example, in /etc/lsb-release the version number reads 0.15.912 but the builbot with that version number failed. The are two possible fixes:.
repo sync to another build number. Use another binhost with the -binhostversion option or -binhost. Based on the board and the release number in /etc/lsb-release find the appropriate BINHOST, unless -binhost or -binhostversion command line arguments are used. Bootstrap emerge by downloading the packages listed in /etc/portage/bootstrap.packages from the BINHOST.
Configure emerge (write make.conf to /usr/local/etc/portage and symlink /etc/portage/make.profile) to install new software to /usr/local.bootstrap.packages is generated during the build image process. It is a text file that contains a list of packages with version numbers that portage needs (portage included) and that are not already in the base image. All the packages in the base image (except the virtual ones) are listed /etc/portage/make.profile/package.provided so emerge will no try to install them and assume they are installed while resolving dependencies.
![](/uploads/1/2/7/1/127187895/687991144.jpg)