Sure it's possible, but then you make a single mistake during booting and your Linux install is wiped out. And the prompt you see during booting is worded to encourage you to disable developer mode and revert to ChromeOS.
>Boot into recovery mode with Esc-Refresh-Power, hold Ctrl-D at the right moment, confirm that you want to wipe the stateful partition, and away you go. Yes, switching to Developer Mode requires deleting all non-OS data on the Chromebook.
Why would you need to wipe the main partition in order to be able to dual boot? Also, I hear that this scary screen comes up every time you boot for 30 seconds unless you press Ctrl-D everytime.
Since NayuOS is still based on Chromium OS you should only need dev mode enabled to run it. It'll boot the same way that Chromium OS does. Legacy boot is only necessary for a traditional Linux distro that isn't using the Chrome OS format for kernel images.
For the record, the write protect is just a screw on Chrome OS devices and doesn't need to be desoldered.
That's only possible if you pay no attention to the hardware you buy. The last time I had to do any post-install config with a linux distro was when I installed kubuntu 5.10 and since Debian 4 onward I never experienced any problem.
Then of course companies like Google are immune to this sort of issue as they even design and sell linux hardware.
Booting by default into an inferior environment and not having the chance to change that default sounds like a massive issue to me.
Maybe not massive from the developers' point of view (they can probably revert it just from tweaking a flag somewhere in the code), but definitely massive for the user which will see a completely different desktop environment.
That effectively is breaking the boot process. Of course, you may be able to tinker with it in order to make things work again, but you have to do that.
> (Boot to DOS) This feature is not available more, but in Linux, the possibility to boot in a console mode still exists.
That's not really how it works - there's no "console mode" in Linux. On Linux the Desktop environment is built on top of underlying OS interface - that's precisely why you can run it completely headless, or why you can completely switch desktop environments in a few seconds.
> so there's no longer any point in having a distinction between "install" and "run/boot".
When Linux boots, the in memory state changes quite a bit. Even the actual code gets modified during boot. The whole process takes well under a second. Linux does support an “execute in place”, but it’s barely a win, and I don’t think it works on x86.
A more interesting idea is to put your OS installation on a DAX (direct access) filesystem.
> 1. It uses systemd-boot as the boot loader. I like not having a grub menu, just turn on my computer and I'm basically on the login screen. It's seamless.
For those on other distros wondering about this behavior and whether they can get it: systemd-boot does support menus, and GRUB also supports bypassing the menu. Systemd-boot is quite good though. It's simpler to configure and less feature-complete than GRUB, and a great first choice for EFI setups.
reply