Installing dual boot ubuntu + windows 10

[Ralf Mardorf]

On Tue, 13 Sep 2016 18:43:39 +0200, Ralf Mardorf wrote:
>On Tue, 13 Sep 2016 14:32:48 +0200, Liam Proven wrote:
>>If you don't trust Ubuntu's elderly GRUB, just boot into Fedora and
>>use its GRUB updater. That should add Ubuntu to your existing boot
>>menu. However, every time you update Ubuntu's kernel, you must boot
>>into Fedora and re-update GRUB.  
>
>If you edit grub.cfg manually, as I did, you even don't need to chroot,
>however, by a chroot the OP could update grub.cfg by the auto-thingy
>without the need to reboot. Wit the latest LTS the OP even could use
>the easier systemd-nspawn to uptade.
>
>My trick is, that I even don't manually edit my grub.cfg each time I
>update. Currently the grub.cfg anyway is part of my Ubuntu install.
>What I do is to change links.
>
>[rocketmouse at archlinux ~]$ ls -hAl /mnt/moonstudio/boot/ | grep lrw
>lrwxrwxrwx 1 root root   30 Aug 29 21:09 initrd.img-lowlatency ->
>initrd.img-4.4.0-36-lowlatency lrwxrwxrwx 1 root root   27 Aug 29
>21:09 vmlinuz-lowlatency -> vmlinuz-4.4.0-36-lowlatency
>
>As long as links are only required for one kernel, a user could even
>use the default links, which are not in /boot, but directly in /. I
>dislike those links, so I remove them and add the links to /boot.

PS: Or is that auto-update-crap to stupid to work in a chroot or
systemd-nspawn environment ;D, confused by uname or something like this?
However, using links definitively does solve this issue.

[root at archlinux moonstudio]# uname -rm
4.7.2-1-ARCH x86_64
[root at archlinux moonstudio]# systemd-nspawn -q
[root at moonstudio ~]# uname -rm
4.7.2-1-ARCH x86_64
[root at moonstudio ~]# cat /etc/issue
Ubuntu 16.04.1 LTS \n \l

[root at moonstudio ~]# logout
[root at archlinux moonstudio]# cat /etc/issue
Arch Linux \r (\l)