Lines Matching full:you
20 first, to ensure you have two working OS images.
33 that you really mean it. Select "Boot from Internal Storage" at the
34 bootloader screen. You will see this screen every time the machine
35 boots now, telling you that the boot is unverified.
45 You will at some point wreck your device and need a recovery stick.
49 You can actually do this on any machine (and any OS) with Chrome
54 root filesystem and /usr/local customizations you have made**. So
55 plan on a strategy that can tolerate data loss on the device you're
68 user. Finally (in developer mode) a simple "sudo su -" will get you a
77 Now you need to turn of signature verification in the bootloader
90 Next you disable the validation step:
96 **THIS COMMAND WILL FAIL**, give you an error that you are changing
101 After rebooting, you will notice that your chromebook boots with the
120 Once you are booted with a writable partition, you can turn on the
128 passwords, so unless you want to type a ssh key in by hand, you
129 probably want to set a password for the first login (before you run
137 ``.ssh/authorized_keys`` as you do for any Linux system.
151 package list, there are X11-enabled ones available too if you prefer
155 the only writable filesystem without noexec, you must place the binary
172 Now you are typing commands into the Ubuntu environment. Enable
189 the chroot is restarted. You can put them in /etc/rc.local for
211 hostname "dev" here to represent the development machine on which you
216 Note: you probably have an existing Linux tree somewhere already. If
217 you do it's much faster to add this as a remote there and just fetch
220 Now you need a .config file. The Chromebook kernel ships with the
221 "configs" module built which exposes this in the running kernel. You
230 You will need to set some custom configuration variables differently
231 from ChromeOS defaults (you can edit .config directly, or use
243 Now build your kernel just as you would any other:
250 The modules you can copy directly to the (now writable) rootfs on the
253 required, and you may find you need to regularly prune modules from
273 Find the current kernel partition on the device. You can get this by
292 Now you can pack a new kernel image using the vboot tooling. Most of
308 You can verify this image if you like with "vbutil_kernel --verify".
317 Now reboot, and if all goes well you will find yourself running in
339 Finally, with your new kernel booted, you are ready to run Zephyr