You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-21Lines changed: 17 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,17 @@
1
1
# chromeos-build
2
-
A tool to build Chrome OS easily
2
+
Scripts to build Chrome OS easily
3
3
4
-
## Prerequisites
4
+
## How to run Chromium OS on KVM
5
+
6
+
Retrieve one of KVM images. I recommend [chromiumos_qemu_image-R60-9592.63-amd64-generic.32GB.qcow2.xz](https://github.com/jam7/chromeos-build/releases/download/R60/chromiumos_qemu_image-R60-9592.63-amd64-generic.32GB.qcow2.xz), 410MB.
7
+
8
+
Then, create VM using the image. [Here](https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/running-chromeos-image-under-virtual-machines) has command line for KVM. If you use GUI manager, plase make sure to use **cirrius** VGA and **SATA** or **IDE** storage device.
9
+
10
+
You cannot log in from GUI until you register your own google API keys, but it is possible to ssh to Chromium OS with chronos:chronos account.
11
+
12
+
## How to compile Chromium OS by yourself
13
+
14
+
### Prerequisites
5
15
Prerequisites are described [here](https://www.chromium.org/chromium-os/developer-guide).
6
16
7
17
I'll list them for the ease. **Bold** means new or different prerequisities from above. I noticed them through my experience.
@@ -14,16 +24,6 @@ I'll list them for the ease. **Bold** means new or different prerequisities fro
14
24
- configure git
15
25
- tweak sudoers for **400** minutes (My machine takes more than 180 min for compilation)
16
26
17
-
## How to run Chromium OS on KVM
18
-
19
-
Retrieve one of KVM images. I recommend [chromiumos_image-R60-9592.63-amd64-generic.bin.xz](https://github.com/jam7/chromeos-build/releases/download/R60/chromiumos_image-R60-9592.63-amd64-generic.bin.xz).
20
-
21
-
Then, create VM using the image. It is required to use **cirrius** VGA and **SATA** or **IDE** storage.
22
-
23
-
You cannot log in from GUI until you register your own google API keys, but it is possible to ssh to Chromium OS with chronos:chronos account.
24
-
25
-
## How to compile Chromium OS by yourself
26
-
27
27
### Setup
28
28
Type following command to prepare depo_tools and sources.
29
29
@@ -59,11 +59,7 @@ Convert qemu raw image to qcow2 image if your qemu-manager requires it.
59
59
$ qemu-img convert -f raw -O qcow2 chromiumos_qemu_image-R55-8872.76-amd64-generic.img chromiumos_qemu_image-R55-8872.76-amd64-generic.qcow2
60
60
```
61
61
62
-
## How to run Chromium OS on KVM
63
-
64
-
Create VM using GUI manager. It is required to use **cirrius** VGA. At this time, you cannot log in from GUI since google API keys are not installed yet.
65
-
66
-
## How to set chronos password
62
+
## How to change chronos password
67
63
68
64
Push `CTRL`+`ALT`+`F2`. Type `chronos` as a user. You may need to enter `chronos` as password also.
69
65
@@ -78,11 +74,11 @@ Retype new UNIX password:
78
74
passwd: password updated successfully
79
75
```
80
76
81
-
After updating UNIX password, you can ssh to Chromium OS.
77
+
It is required to update UNIX password to log-in through ssh.
82
78
83
79
## How to set google API keys
84
80
85
-
You need to retrieve your own API keys from https://www.chromium.org/developers/how-tos/api-keys. Then, you can update Chromium OS like below.
81
+
You need to retrieve your own API keys from https://www.chromium.org/developers/how-tos/api-keys. Then, you can set those API keys into Chromium OS like below.
0 commit comments