Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
A starting point: https://wiki.archlinux.org/index.php/Syslinux -- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
Ralf: I just did a quick search on the googly and it seems like syslinux is for "MS/DOS" or "BIOS" and/or possibly "FAT32" systems?? It didn't seem to mention Macs, although it did show something on "UEFI" . . . but then one item was saying, "It won't boot ext2 systems"??? So it seems like syslinux is also "going back" in the history of linux in the time before apple was considered "adequate" . . . . But, I think sometime in the next year or so I will be trying to find a PC laptop, or a "built for linux" laptop . . . and that would likely have the "BIOS" and "MBR" items that might be friendlier to syslinux Seems like what I might have seen in OpenSUSE was some "syslinux" package or app, which might not be the same as the "syslinux bootloader" that is BIOS friendly and only boots "MS/DOS" and/or Fat32 formatted systems??? I know that in Mac the EFI boot partition is formatted as FAT32 . . . so question is . . . is that meeting the requirements for booting via syslinux, or nope it don't do Macintoshes . . . ??? On Wed, Jul 29, 2020 at 3:40 PM Ralf Mardorf wrote: > PPS: > > For my Xenial install I'm using links, I have to manually update, so > that I don't need to fix my syslinux.cfg: > > [rocketmouse@archlinux ~]$ /usr/bin/ls -hl /.boot/ubuntu_moonstudio/boot/ > total 114M > -rw--- 1 root root 3.8M Jul 1 09:30 System.map-4.4.0-186-lowlatency > -rw-r--r-- 1 root root 3.2M Nov 15 2019 > System.map-5.3.0-11.2-liquorix-amd64 > -rw-r--r-- 1 root root 187K Jul 1 09:30 config-4.4.0-186-lowlatency > -rw-r--r-- 1 root root 213K Nov 15 2019 config-5.3.0-11.2-liquorix-amd64 > drwxr-xr-x 2 root root 4.0K May 7 06:09 grub > -rw-r--r-- 1 root root 37M Jul 21 04:50 initrd.img-4.4.0-186-lowlatency > -rw-r--r-- 1 root root 54M Jun 13 18:23 > initrd.img-5.3.0-11.2-liquorix-amd64 > lrwxrwxrwx 1 root root 36 Nov 26 2019 initrd.img-liquorix -> > initrd.img-5.3.0-11.2-liquorix-amd64 > lrwxrwxrwx 1 root root 31 Jul 21 04:58 initrd.img-lowlatency -> > initrd.img-4.4.0-186-lowlatency > -rw-r--r-- 1 root root 179K Jan 28 2016 memtest86+.bin > -rw-r--r-- 1 root root 181K Jan 28 2016 memtest86+.elf > -rw-r--r-- 1 root root 181K Jan 28 2016 memtest86+_multiboot.bin > -rw-r--r-- 1 root root0 Aug 6 2018 s3.archlinux > -rw--- 1 root root 7.0M Jul 6 11:18 vmlinuz-4.4.0-186-lowlatency > -rw-r--r-- 1 root root 9.0M Nov 15 2019 vmlinuz-5.3.0-11.2-liquorix-amd64 > lrwxrwxrwx 1 root root 33 Nov 26 2019 vmlinuz-liquorix -> > vmlinuz-5.3.0-11.2-liquorix-amd64 > lrwxrwxrwx 1 root root 28 Jul 21 04:58 vmlinuz-lowlatency -> > vmlinuz-4.4.0-186-lowlatency > > -- > /usr/bin/ls since 'ls' is an alias on my install: > [rocketmouse@archlinux ~]$ alias ls > alias ls='lsd' > -- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
On Wed, Jul 29, 2020 at 3:51 PM Ralf Mardorf wrote: > On Wed, 29 Jul 2020 15:34:54 -0700, Fritz Hudnut wrote: > >got a good laugh out of the "Hal 9000" line . . . classic geek humor > >there > > Using a computer without a sense of dark humour is really dangerous! > Indeed it is . . . and the reference to Hal 9000 is "the stuff of the dark web" . . . i.e., extra dark stuff . . . . : - -- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
On Wed, 29 Jul 2020 15:34:54 -0700, Fritz Hudnut wrote: >got a good laugh out of the "Hal 9000" line . . . classic geek humor >there Using a computer without a sense of dark humour is really dangerous! -- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
PPS: For my Xenial install I'm using links, I have to manually update, so that I don't need to fix my syslinux.cfg: [rocketmouse@archlinux ~]$ /usr/bin/ls -hl /.boot/ubuntu_moonstudio/boot/ total 114M -rw--- 1 root root 3.8M Jul 1 09:30 System.map-4.4.0-186-lowlatency -rw-r--r-- 1 root root 3.2M Nov 15 2019 System.map-5.3.0-11.2-liquorix-amd64 -rw-r--r-- 1 root root 187K Jul 1 09:30 config-4.4.0-186-lowlatency -rw-r--r-- 1 root root 213K Nov 15 2019 config-5.3.0-11.2-liquorix-amd64 drwxr-xr-x 2 root root 4.0K May 7 06:09 grub -rw-r--r-- 1 root root 37M Jul 21 04:50 initrd.img-4.4.0-186-lowlatency -rw-r--r-- 1 root root 54M Jun 13 18:23 initrd.img-5.3.0-11.2-liquorix-amd64 lrwxrwxrwx 1 root root 36 Nov 26 2019 initrd.img-liquorix -> initrd.img-5.3.0-11.2-liquorix-amd64 lrwxrwxrwx 1 root root 31 Jul 21 04:58 initrd.img-lowlatency -> initrd.img-4.4.0-186-lowlatency -rw-r--r-- 1 root root 179K Jan 28 2016 memtest86+.bin -rw-r--r-- 1 root root 181K Jan 28 2016 memtest86+.elf -rw-r--r-- 1 root root 181K Jan 28 2016 memtest86+_multiboot.bin -rw-r--r-- 1 root root0 Aug 6 2018 s3.archlinux -rw--- 1 root root 7.0M Jul 6 11:18 vmlinuz-4.4.0-186-lowlatency -rw-r--r-- 1 root root 9.0M Nov 15 2019 vmlinuz-5.3.0-11.2-liquorix-amd64 lrwxrwxrwx 1 root root 33 Nov 26 2019 vmlinuz-liquorix -> vmlinuz-5.3.0-11.2-liquorix-amd64 lrwxrwxrwx 1 root root 28 Jul 21 04:58 vmlinuz-lowlatency -> vmlinuz-4.4.0-186-lowlatency -- /usr/bin/ls since 'ls' is an alias on my install: [rocketmouse@archlinux ~]$ alias ls alias ls='lsd' -- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
Ralf: Thanks for sharing that data . . . it looks like "French" right now to this redneck hippie 'merican . . . so I'll have to study it for awhile . . . . But, got a good laugh out of the "Hal 9000" line . . . classic geek humor there . . . . Somewhere recently I used the "Dave . . . stop . . . stop . . . Dave . . . please stop . . . stop." line, but it didn't seem to be "recognized" for the high value humor that it should have provided . . . . : - 0 F On Wed, Jul 29, 2020 at 3:25 PM Ralf Mardorf wrote: > PS: > > I've got experiences with chainloading FreeBSD and Windows when using > grub legacy and grub2, but not with syslinux. > > My syslinux multi-boot PC is a Linux only multi-boot _and_ I never > used, neither with grub, nor with syslinux, anything secure boot/(U)EFI > related. > > That's my current syslinux.cfg: > > [rocketmouse@archlinux ~]$ cat /boot/syslinux/syslinux.cfg > # Syslinux > # http://syslinux.zytor.com/wiki/index.php/Doc/menu > # > # Mitigations linux >= 5.1.13 > # > https://linuxreviews.org/HOWTO_make_Linux_run_blazing_fast_(again)_on_Intel_CPUs > # mitigations=off > # > # Misc > # grep . /sys/devices/system/cpu/vulnerabilities/* | cut -d/ -f7 > # audit=off > > PROMPT 0 > TIMEOUT 600 > UI menu.c32 > MENU HIDDEN > MENU CLEAR > MENU COLOR screen 0;30;40 > MENU COLOR border 0;30;40 > MENU COLOR title 1;37;44 > MENU COLOR unsel 0;37;40 > MENU COLOR hotkey 1;37;40 > MENU COLOR hotsel 7;37;40 > MENU COLOR sel 7;37;40 > MENU COLOR disabled1;37;40 > MENU COLOR scrollbar 0;30;40 > MENU COLOR tabmsg 0;30;40 > MENU COLOR cmdmark 0;31;40 > MENU COLOR cmdline 0;37;40 > MENU COLOR timeout_msg 0;37;40 > MENU COLOR timeout 1;37;40 > > # Used hotkeys: ^8 ^A ^C ^e ^f ^g ^H ^i (^l) ^M ^n ^o ^P ^Q ^R ^S ^t ^V > (^X) ^y > KBDMAP de.ktl > DEFAULT Securityink > > MENU TITLE HAL 9000-s3 > LABEL Toolbox > MENU LABEL Toolbox > MENU DISABLE > MENU SEPARATOR > > > LABEL Hardware > MENU LABEL ^Hardware Detection > COM32 hdt.c32 > > LABEL Memtest > MENU LABEL Memtest^86+ > LINUX /.boot/ubuntu_moonstudio/boot/memtest86+.bin > > LABEL Reset > MENU LABEL R^eset > COM32 reboot.c32 > > > MENU SEPARATOR > MENU SEPARATOR > LABEL Arch Menu > MENU LABEL Arch Linux > MENU DISABLE > MENU SEPARATOR > > > LABEL Threadirqs > MENU LABEL Arch Linux ^threadirqs > LINUX ../vmlinuz-linux > APPEND root=LABEL=s3.archlinux ro threadirqs > INITRD ../intel-ucode.img,../initramfs-linux.img > > LABEL Threadirqs_no_mitigations > MENU LABEL Arch Linux threadirqs ^no mitigations > LINUX ../vmlinuz-linux > APPEND root=LABEL=s3.archlinux ro threadirqs mitigations=off audit=off > INITRD ../intel-ucode.img,../initramfs-linux.img > > LABEL Securityink > MENU LABEL Arch Linux Rt ^Securityink > LINUX ../vmlinuz-linux-rt-securityink > APPEND root=LABEL=s3.archlinux ro > INITRD ../intel-ucode.img,../initramfs-linux-rt-securityink.img > > LABEL Securityink_no_mitigations > MENU LABEL Arch Linux Rt Securityink no m^itigations > LINUX ../vmlinuz-linux-rt-securityink > APPEND root=LABEL=s3.archlinux ro noibrs noibpb nopti nospectre_v2 > nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off > mitigations=off > INITRD ../intel-ucode.img,../initramfs-linux-rt-securityink.img > > LABEL Pussytoes > MENU LABEL Arch Linux Rt ^Pussytoes > LINUX ../vmlinuz-linux-rt-pussytoes > APPEND root=LABEL=s3.archlinux ro > INITRD ../intel-ucode.img,../initramfs-linux-rt-pussytoes.img > > LABEL Pussytoes_no_mitigations > MENU LABEL Arch Linux Rt Puss^ytoesno mitigations > LINUX ../vmlinuz-linux-rt-pussytoes > #APPEND root=LABEL=s3.archlinux ro mitigations=off > APPEND root=LABEL=s3.archlinux ro noibrs noibpb nopti nospectre_v2 > nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off > mitigations=off > INITRD ../intel-ucode.img,../initramfs-linux-rt-pussytoes.img > > LABEL Cornflower > MENU LABEL Arch Linux Rt ^Cornflower > LINUX ../vmlinuz-linux-rt-cornflower > APPEND root=LABEL=s3.archlinux ro > INITRD ../intel-ucode.img,../initramfs-linux-rt-cornflower.img > > LABEL Cornflower_no_mitigations > MENU LABEL Arch Linux Rt Corn^flower no mitigations > LINUX ../vmlinuz-linux-rt-cornflower > #APPEND root=LABEL=s3.archlinux ro mitigations=off audit=off > APPEND root=LABEL=s3.archlinux ro mitigations=off > INITRD ../intel-ucode.img,../initramfs-linux-rt-cornflower.img > > LABEL Rt > MENU LABEL Arch Linux ^Rt > LINUX ../vmlinuz-linux-rt > APPEND root=LABEL=s3.archlinux ro > INITRD ../intel-ucode.img,../initramfs-linux-rt.img > > LABEL Rt_no_mitigations > MENU LABEL Arch Linux Rt n^o mitigations > LINUX ../vmlinuz-linux-rt > APPEND root=LABEL=s3.archlinux ro mitigations=off > INITRD ../intel-ucode.img,../initramfs-linux-rt.img > > LABEL
Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
PS: I've got experiences with chainloading FreeBSD and Windows when using grub legacy and grub2, but not with syslinux. My syslinux multi-boot PC is a Linux only multi-boot _and_ I never used, neither with grub, nor with syslinux, anything secure boot/(U)EFI related. That's my current syslinux.cfg: [rocketmouse@archlinux ~]$ cat /boot/syslinux/syslinux.cfg # Syslinux # http://syslinux.zytor.com/wiki/index.php/Doc/menu # # Mitigations linux >= 5.1.13 # https://linuxreviews.org/HOWTO_make_Linux_run_blazing_fast_(again)_on_Intel_CPUs # mitigations=off # # Misc # grep . /sys/devices/system/cpu/vulnerabilities/* | cut -d/ -f7 # audit=off PROMPT 0 TIMEOUT 600 UI menu.c32 MENU HIDDEN MENU CLEAR MENU COLOR screen 0;30;40 MENU COLOR border 0;30;40 MENU COLOR title 1;37;44 MENU COLOR unsel 0;37;40 MENU COLOR hotkey 1;37;40 MENU COLOR hotsel 7;37;40 MENU COLOR sel 7;37;40 MENU COLOR disabled1;37;40 MENU COLOR scrollbar 0;30;40 MENU COLOR tabmsg 0;30;40 MENU COLOR cmdmark 0;31;40 MENU COLOR cmdline 0;37;40 MENU COLOR timeout_msg 0;37;40 MENU COLOR timeout 1;37;40 # Used hotkeys: ^8 ^A ^C ^e ^f ^g ^H ^i (^l) ^M ^n ^o ^P ^Q ^R ^S ^t ^V (^X) ^y KBDMAP de.ktl DEFAULT Securityink MENU TITLE HAL 9000-s3 LABEL Toolbox MENU LABEL Toolbox MENU DISABLE MENU SEPARATOR LABEL Hardware MENU LABEL ^Hardware Detection COM32 hdt.c32 LABEL Memtest MENU LABEL Memtest^86+ LINUX /.boot/ubuntu_moonstudio/boot/memtest86+.bin LABEL Reset MENU LABEL R^eset COM32 reboot.c32 MENU SEPARATOR MENU SEPARATOR LABEL Arch Menu MENU LABEL Arch Linux MENU DISABLE MENU SEPARATOR LABEL Threadirqs MENU LABEL Arch Linux ^threadirqs LINUX ../vmlinuz-linux APPEND root=LABEL=s3.archlinux ro threadirqs INITRD ../intel-ucode.img,../initramfs-linux.img LABEL Threadirqs_no_mitigations MENU LABEL Arch Linux threadirqs ^no mitigations LINUX ../vmlinuz-linux APPEND root=LABEL=s3.archlinux ro threadirqs mitigations=off audit=off INITRD ../intel-ucode.img,../initramfs-linux.img LABEL Securityink MENU LABEL Arch Linux Rt ^Securityink LINUX ../vmlinuz-linux-rt-securityink APPEND root=LABEL=s3.archlinux ro INITRD ../intel-ucode.img,../initramfs-linux-rt-securityink.img LABEL Securityink_no_mitigations MENU LABEL Arch Linux Rt Securityink no m^itigations LINUX ../vmlinuz-linux-rt-securityink APPEND root=LABEL=s3.archlinux ro noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off INITRD ../intel-ucode.img,../initramfs-linux-rt-securityink.img LABEL Pussytoes MENU LABEL Arch Linux Rt ^Pussytoes LINUX ../vmlinuz-linux-rt-pussytoes APPEND root=LABEL=s3.archlinux ro INITRD ../intel-ucode.img,../initramfs-linux-rt-pussytoes.img LABEL Pussytoes_no_mitigations MENU LABEL Arch Linux Rt Puss^ytoesno mitigations LINUX ../vmlinuz-linux-rt-pussytoes #APPEND root=LABEL=s3.archlinux ro mitigations=off APPEND root=LABEL=s3.archlinux ro noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off INITRD ../intel-ucode.img,../initramfs-linux-rt-pussytoes.img LABEL Cornflower MENU LABEL Arch Linux Rt ^Cornflower LINUX ../vmlinuz-linux-rt-cornflower APPEND root=LABEL=s3.archlinux ro INITRD ../intel-ucode.img,../initramfs-linux-rt-cornflower.img LABEL Cornflower_no_mitigations MENU LABEL Arch Linux Rt Corn^flower no mitigations LINUX ../vmlinuz-linux-rt-cornflower #APPEND root=LABEL=s3.archlinux ro mitigations=off audit=off APPEND root=LABEL=s3.archlinux ro mitigations=off INITRD ../intel-ucode.img,../initramfs-linux-rt-cornflower.img LABEL Rt MENU LABEL Arch Linux ^Rt LINUX ../vmlinuz-linux-rt APPEND root=LABEL=s3.archlinux ro INITRD ../intel-ucode.img,../initramfs-linux-rt.img LABEL Rt_no_mitigations MENU LABEL Arch Linux Rt n^o mitigations LINUX ../vmlinuz-linux-rt APPEND root=LABEL=s3.archlinux ro mitigations=off INITRD ../intel-ucode.img,../initramfs-linux-rt.img LABEL Arch MENU LABEL ^Arch Linux LINUX ../vmlinuz-linux APPEND root=LABEL=s3.archlinux ro INITRD ../intel-ucode.img,../initramfs-linux.img MENU SEPARATOR MENU SEPARATOR LABEL Other Menu MENU LABEL Other Linux MENU DISABLE MENU SEPARATOR LABEL Moonstudio_liquorix MENU LABEL Ubuntu X Moon Studio ^liquorix threadirqs LINUX /.boot/ubuntu_moonstudio/boot/vmlinuz-liquorix APPEND root=LABEL=moonstudio ro threadirqs INITRD /.boot/ubuntu_moonstudio/boot/initrd.img-liquorix LABEL Moonstudio_liquorix_no_mitigations MENU LABEL Ubuntu ^X Moon Studio liquorix threadirqs no mitigations LINUX /.boot/ubuntu_moonstudio/boot/vmlinuz-liquorix APPEND root=LABEL=moonstudio ro threadirqs mitigations=off audit=off INITRD
Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
On Wed, Jul 29, 2020 at 3:03 PM Ralf Mardorf wrote: > Hi Fritz, > > it comes with a learning curve ;). > > On Wed, 29 Jul 2020 14:20:18 -0700, Fritz Hudnut wrote: > >Any pointers on why you choose syslinux over grub2?? > > For me the pros of syslinux are > > - I do not need to disable insane automation, as I had to do (depending > on the distro providing it) for grub2 > - I do not need to tidy up a default config, to get rid of clutter > > For me the con of syslinux is > > - I'm either forced to use chainloading or as I do, to use one > partition for the kernels of all installs and (not necessarily) to > bind mount [1] > > In my case 2 pros vs one con. > > Actually there are a lot of more pros and cons for both, syslinux as > well as grub2, depending on the users needs. For me just the mentioned > matter. > > On 'apt' based distros, such as the Ubuntu flavour Lubuntu, you can > 'dpkg-divert' [2] 'grub-mkconfig' and 'update-grub' to get rid of the > insane automation and usage of configs, to generate cluttered configs. > Instead manually edit a clean grub.cfg and don't worry about any > automation that could mess up anything. > > FWIW I'm using syslinux of my Arch Linux install, not from my Ubuntu > Xenial install. > > Regards, > Ralf > > [1] > [weremouse@moonstudio src]$ grep bind /etc/fstab > /mnt/archlinux/.boot/ubuntu_moonstudio/boot /boot none bind > 0 0 > > [2] > http://manpages.ubuntu.com/manpages/xenial/man1/dpkg-divert.1.html > > > @Ralf: Thanks for the fast reply . . . indeed, there usually is "a learning curve" . . . I was thinking after I posted that it might be "a nightmare" to try to get my Mac Pro with 4 drives with multiple installs spread across each of them, all switched over from Grub2 . . . without creating a "mess" beyond the mess that I have now. It seems like grub2 must "memorize" all of the systems that have ever been installed or booted by Grub2 . . . because in SG2 disk the list of all of the various "cfg's" . . . what "vmlinuz" and all of the other overlaps that might boot something up . . . are all listed there and it's a "very long list." Maybe 6 months back I had a Sid linux distro installed and it turned out to be "unfriendly" to the other distros and removed data across partitions and possibly drives AND it messed up grub2 . . . and I had a thread on the opensuse forum that was huugggeee with guys trying to help me figure out how to get grub2 all tidy again . . . and in spite of what was pretty high level help . . . nothing seemed to get grub2 "freshened" to just show the current installs . . . it remina as you say, "cluttered." It might be easier to fiddle with my olde laptop that only has two OSX installs and one Manjaro . . . Manjaro is stacked on Arch, right?? That install is my first or second Arch based install . . . might be "easier" to get over to syslinux in that computer and if it blows up . . . not too difficult to do a fresh install??? Or, is this something that is easier to do with a fresh install and then instead of flagging the EFI boot partition with "grub2" . . . there's a drop down choice for "syslinux"?? I was trying to figure out if Xenial is 16.04??? Ancient history man, didn't they just "drop support" for it a couple weeks back??? Check out Groovy . . . the water is "fine" in the 20.10 game. : - -- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
Re: [lubuntu-users] Apart from this I'm using syslinux instead of grub2.
Hi Fritz, it comes with a learning curve ;). On Wed, 29 Jul 2020 14:20:18 -0700, Fritz Hudnut wrote: >Any pointers on why you choose syslinux over grub2?? For me the pros of syslinux are - I do not need to disable insane automation, as I had to do (depending on the distro providing it) for grub2 - I do not need to tidy up a default config, to get rid of clutter For me the con of syslinux is - I'm either forced to use chainloading or as I do, to use one partition for the kernels of all installs and (not necessarily) to bind mount [1] In my case 2 pros vs one con. Actually there are a lot of more pros and cons for both, syslinux as well as grub2, depending on the users needs. For me just the mentioned matter. On 'apt' based distros, such as the Ubuntu flavour Lubuntu, you can 'dpkg-divert' [2] 'grub-mkconfig' and 'update-grub' to get rid of the insane automation and usage of configs, to generate cluttered configs. Instead manually edit a clean grub.cfg and don't worry about any automation that could mess up anything. FWIW I'm using syslinux of my Arch Linux install, not from my Ubuntu Xenial install. Regards, Ralf [1] [weremouse@moonstudio src]$ grep bind /etc/fstab /mnt/archlinux/.boot/ubuntu_moonstudio/boot /boot none bind 0 0 [2] http://manpages.ubuntu.com/manpages/xenial/man1/dpkg-divert.1.html -- Lubuntu-users mailing list Lubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/lubuntu-users
