https://wiki.alpinelinux.org/w/api.php?action=feedcontributions&feedformat=atom&user=Konki 2026-05-06T15:04:22Z User contributions MediaWiki 1.40.0 https://wiki.alpinelinux.org/w/index.php?title=Talk:Dualbooting&diff=25366 2023-10-08T17:00:05Z

<p>Konki: </p> <hr /> <div>1.<br /> <br /> alp:/# updqate-grub2<br /> /bin/ash: updqate-grub2: not found<br /> <br /> And package absent<br /> <br /> 2.<br /> <br /> alp:/# grub-mkconfig -o /boot/grub/grub.cfg<br /> Generating grub configuration file ...<br /> Found linux image: /boot/vmlinuz-lts<br /> Found initrd image: /boot/initramfs-lts<br /> Warning: os-prober will be executed to detect other bootable partitions.<br /> Its output will be used to detect bootable binaries on them and create new boot entries.<br /> error: syntax error.<br /> error: Incorrect command.<br /> error: syntax error.<br /> Syntax error at line 126<br /> Syntax errors are detected in generated GRUB config file.<br /> Ensure that there are no errors in /etc/default/grub<br /> and /etc/grub.d/* files or please file a bug report with<br /> /boot/grub/grub.cfg.new file attached.<br /> <br /> — Preceding unsigned comment added by Vul (talk • contribs) 04:43, 7 November 2022‎<br /> <br /> The command in your 1st section is most certainly misspelled at a minimum.<br /> zcrayfish (talk) 03:01, 14 August 2023 (UTC)<br /> <br /> 3. Installing Alpine on an HDD partition with dualbooting windows 10/11<br /> <br /> I'm not a computer scientist, but this should be added to the &quot;Installing Alpine on an HDD partition&quot; section to avoid putting off those who wish to upgrade. <br /> <br /> to be done after basic setup-alpine<br /> if we assume that the partition is the following:<br /> /dev/nvme0n1p5 for the root<br /> /dev/nvme0n1p2 /mnt/boot/efi for the efi partition created by windows 10/11<br /> /dev/sda4 for /home<br /> <br /> in the following example:<br /> <br /> apk update <br /> apk upgrade <br /> apk add dosfstools for vfat support <br /> apk add util-linux for lsblk <br /> apk add e2fsprogs for mkfs <br /> apk add efibootmgr<br /> <br /> lslbk <br /> or <br /> fdisk -l<br /> <br /> <br /> Format partition / <br /> mkfs.ext4 /dev/nvme0n1p5 <br /> Format /home partition <br /> mkfs.ext4 /dev/sda4<br /> <br /> Mount the Root partition <br /> mount -t ext4 /dev/nvme0n1p5 /mnt<br /> <br /> Mount the EFI partition created by windows <br /> mkdir -p /mnt/boot/efi <br /> mount -t vfat /dev/nvme0n1p2 /mnt/boot/efi<br /> <br /> and create the necessary directories in EFI <br /> cd /mnt/boot/efi/EFI <br /> mkdir -p boot # attention must be lowercase not Boot #<br /> mkdir -p alpine<br /> <br /> Mount /home partition <br /> mkdir -p /mnt/home <br /> mount -t ext4 /dev/sda4 /mnt/home<br /> <br /> Install in /mnt partition <br /> setup-disk -m sys /mnt<br /> <br /> reboot</div>

Konki https://wiki.alpinelinux.org/w/index.php?title=Talk:Dualbooting&diff=25365 2023-10-08T16:59:00Z

<p>Konki: </p> <hr /> <div>1.<br /> <br /> alp:/# updqate-grub2<br /> /bin/ash: updqate-grub2: not found<br /> <br /> And package absent<br /> <br /> 2.<br /> <br /> alp:/# grub-mkconfig -o /boot/grub/grub.cfg<br /> Generating grub configuration file ...<br /> Found linux image: /boot/vmlinuz-lts<br /> Found initrd image: /boot/initramfs-lts<br /> Warning: os-prober will be executed to detect other bootable partitions.<br /> Its output will be used to detect bootable binaries on them and create new boot entries.<br /> error: syntax error.<br /> error: Incorrect command.<br /> error: syntax error.<br /> Syntax error at line 126<br /> Syntax errors are detected in generated GRUB config file.<br /> Ensure that there are no errors in /etc/default/grub<br /> and /etc/grub.d/* files or please file a bug report with<br /> /boot/grub/grub.cfg.new file attached.<br /> <br /> — Preceding unsigned comment added by Vul (talk • contribs) 04:43, 7 November 2022‎<br /> <br /> The command in your 1st section is most certainly misspelled at a minimum.<br /> zcrayfish (talk) 03:01, 14 August 2023 (UTC)<br /> <br /> 3.<br /> <br /> I'm not a computer scientist, but this should be added to the &quot;Installing Alpine on an HDD partition&quot; section to avoid putting off those who wish to upgrade. <br /> <br /> to be done after basic setup-alpine<br /> if we assume that the partition is the following:<br /> /dev/nvme0n1p5 for the root<br /> /dev/nvme0n1p2 /mnt/boot/efi for the efi partition created by windows 10/11<br /> /dev/sda4 for /home<br /> <br /> in the following example:<br /> <br /> apk update <br /> apk upgrade <br /> apk add dosfstools for vfat support <br /> apk add util-linux for lsblk <br /> apk add e2fsprogs for mkfs <br /> apk add efibootmgr<br /> <br /> lslbk <br /> or <br /> fdisk -l<br /> <br /> <br /> Format partition / <br /> mkfs.ext4 /dev/nvme0n1p5 <br /> Format /home partition <br /> mkfs.ext4 /dev/sda4<br /> <br /> Mount the Root partition <br /> mount -t ext4 /dev/nvme0n1p5 /mnt<br /> <br /> Mount the EFI partition created by windows <br /> mkdir -p /mnt/boot/efi <br /> mount -t vfat /dev/nvme0n1p2 /mnt/boot/efi<br /> <br /> and create the necessary directories in EFI <br /> cd /mnt/boot/efi/EFI <br /> mkdir -p boot # attention must be lowercase not Boot #<br /> mkdir -p alpine<br /> <br /> Mount /home partition <br /> mkdir -p /mnt/home <br /> mount -t ext4 /dev/sda4 /mnt/home<br /> <br /> Install in /mnt partition <br /> setup-disk -m sys /mnt<br /> <br /> reboot</div>

Konki https://wiki.alpinelinux.org/w/index.php?title=Talk:Dualbooting&diff=25364 2023-10-08T16:56:30Z

<p>Konki: Installing Alpine on an HDD partition with dual boot (MS windows 10/11)</p> <hr /> <div>I'm not a computer scientist, but this should be added to the &quot;Installing Alpine on an HDD partition&quot; section to avoid putting off those who wish to upgrade. <br /> <br /> to be done after basic setup-alpine<br /> if we assume that the partition is the following:<br /> /dev/nvme0n1p5 for the root<br /> /dev/nvme0n1p2 /mnt/boot/efi for the efi partition created by windows 10/11<br /> /dev/sda4 for /home<br /> <br /> in the following example:<br /> <br /> apk update <br /> apk upgrade <br /> apk add dosfstools for vfat support <br /> apk add util-linux for lsblk <br /> apk add e2fsprogs for mkfs <br /> apk add efibootmgr<br /> <br /> lslbk <br /> or <br /> fdisk -l<br /> <br /> <br /> Format partition / <br /> mkfs.ext4 /dev/nvme0n1p5 <br /> Format /home partition <br /> mkfs.ext4 /dev/sda4<br /> <br /> Mount the Root partition <br /> mount -t ext4 /dev/nvme0n1p5 /mnt<br /> <br /> Mount the EFI partition created by windows <br /> mkdir -p /mnt/boot/efi <br /> mount -t vfat /dev/nvme0n1p2 /mnt/boot/efi<br /> <br /> and create the necessary directories in EFI <br /> cd /mnt/boot/efi/EFI <br /> mkdir -p boot # attention must be lowercase not Boot #<br /> mkdir -p alpine<br /> <br /> Mount /home partition <br /> mkdir -p /mnt/home <br /> mount -t ext4 /dev/sda4 /mnt/home<br /> <br /> Install in /mnt partition <br /> setup-disk -m sys /mnt<br /> <br /> reboot</div>

Konki https://wiki.alpinelinux.org/w/index.php?title=Talk:Dualbooting&diff=25363 2023-10-08T16:54:03Z

<p>Konki: </p> <hr /> <div>I'm not a computer scientist, but this should be added to the &quot;Installing Alpine on an HDD partition&quot; section to avoid putting off those who wish to upgrade. <br /> <br /> to be done after basic setup-alpine<br /> if we assume that the partition is the following:<br /> /dev/nvme0n1p5 for the root<br /> /dev/nvme0n1p2 /mnt/boot/efi for the efi partition created by windows 10/11<br /> /dev/sda4 for /home<br /> <br /> in the following example:<br /> <br /> &lt;nowiki&gt;apk update <br /> apk upgrade <br /> apk add dosfstools for vfat support <br /> apk add util-linux for lsblk <br /> apk add e2fsprogs for mkfs <br /> apk add efibootmgr&lt;/nowiki&gt;<br /> <br /> lslbk <br /> or <br /> fdisk -l<br /> <br /> <br /> Format partition / <br /> mkfs.ext4 /dev/nvme0n1p5 <br /> Format /home partition <br /> mkfs.ext4 /dev/sda4<br /> <br /> Mount the Root partition <br /> mount -t ext4 /dev/nvme0n1p5 /mnt<br /> <br /> Mount the EFI partition created by windows <br /> mkdir -p /mnt/boot/efi <br /> mount -t vfat /dev/nvme0n1p2 /mnt/boot/efi<br /> <br /> and create the necessary directories in EFI <br /> cd /mnt/boot/efi/EFI <br /> mkdir -p boot # attention must be lowercase not Boot #<br /> mkdir -p alpine<br /> <br /> Mount /home partition <br /> mkdir -p /mnt/home <br /> mount -t ext4 /dev/sda4 /mnt/home<br /> <br /> Install in /mnt partition <br /> setup-disk -m sys /mnt<br /> <br /> reboot</div>

Konki https://wiki.alpinelinux.org/w/index.php?title=Talk:Dualbooting&diff=25362 2023-10-08T16:52:06Z

<p>Konki: Installing Alpine on an HDD partition with dual boot (MS windows 10/11)</p> <hr /> <div>I'm not a computer scientist, but this should be added to the &quot;Installing Alpine on an HDD partition&quot; section to avoid putting off those who wish to upgrade. <br /> <br /> to be done after basic setup-alpine<br /> if we assume that the partition is the following:<br /> /dev/nvme0n1p5 for the root<br /> /dev/nvme0n1p2 /mnt/boot/efi for the efi partition created by windows 10/11<br /> /dev/sda4 for /home<br /> <br /> in the following example:<br /> <br /> apk update <br /> apk upgrade <br /> apk add dosfstools for vfat support <br /> apk add util-linux for lsblk <br /> apk add e2fsprogs for mkfs <br /> apk add efibootmgr<br /> <br /> lslbk <br /> or <br /> fdisk -l<br /> <br /> <br /> Format partition / <br /> mkfs.ext4 /dev/nvme0n1p5 <br /> Format /home partition <br /> mkfs.ext4 /dev/sda4<br /> <br /> Mount the Root partition <br /> mount -t ext4 /dev/nvme0n1p5 /mnt<br /> <br /> Mount the EFI partition created by windows <br /> mkdir -p /mnt/boot/efi <br /> mount -t vfat /dev/nvme0n1p2 /mnt/boot/efi<br /> <br /> and create the necessary directories in EFI <br /> cd /mnt/boot/efi/EFI <br /> mkdir -p boot # attention must be lowercase not Boot #<br /> mkdir -p alpine<br /> <br /> Mount /home partition <br /> mkdir -p /mnt/home <br /> mount -t ext4 /dev/sda4 /mnt/home<br /> <br /> Install in /mnt partition <br /> setup-disk -m sys /mnt<br /> <br /> reboot</div>

Konki https://wiki.alpinelinux.org/w/index.php?title=Talk:Configure_a_Wireguard_interface_(wg)&diff=21960 2022-06-11T10:47:22Z

<p>Konki: /* Bringing up an interface using ifupdown-ng */</p> <hr /> <div>== Bringing up an interface using wg-tools ==<br /> <br /> ''Then load the module''<br /> <br /> modprobe wireguard<br /> <br /> ''Add it to &lt;code&gt;/etc/modules&lt;/code&gt; to automatically load it on boot.''<br /> <br /> This does not seem to be necessary (any more)?<br /> <br /> [[User:Anianz|Anianz]] ([[User talk:Anianz|talk]])<br /> <br /> == Bringing up an interface using ifupdown-ng ==<br /> <br /> The netifrc package is perfect for mounting the wg0 interface at boot in the specific case of using the plain wg command ( https://wiki.gentoo.org/wiki/Wireguard#netifrc ), but only available for the edge branch.<br /> <br /> What is the right approach for loading the configuration file and mount the wg0 network interface, at startup in the stable branch?<br /> <br /> Konki</div>

Konki https://wiki.alpinelinux.org/w/index.php?title=Talk:Configure_a_Wireguard_interface_(wg)&diff=21959 2022-06-11T10:41:46Z

<p>Konki: /* Bringing up an interface using ifupdown-ng */</p> <hr /> <div>== Bringing up an interface using wg-tools ==<br /> <br /> ''Then load the module''<br /> <br /> modprobe wireguard<br /> <br /> ''Add it to &lt;code&gt;/etc/modules&lt;/code&gt; to automatically load it on boot.''<br /> <br /> This does not seem to be necessary (any more)?<br /> <br /> [[User:Anianz|Anianz]] ([[User talk:Anianz|talk]])<br /> <br /> == Bringing up an interface using ifupdown-ng ==<br /> <br /> The netifrc package is perfect for mounting the wg0 interface at boot in the specific case of using the plain wg command ( https://wiki.gentoo.org/wiki/Wireguard#netifrc ), but only available for the edge branch.<br /> <br /> What is the right approach for loading the configuration and mount the wg0 network interface, at startup in the stable branch?<br /> <br /> Konki</div>

Konki https://wiki.alpinelinux.org/w/index.php?title=Talk:Configure_a_Wireguard_interface_(wg)&diff=21958 2022-06-11T10:40:44Z

<p>Konki: /* Bringing up an interface using ifupdown-ng */</p> <hr /> <div>== Bringing up an interface using wg-tools ==<br /> <br /> ''Then load the module''<br /> <br /> modprobe wireguard<br /> <br /> ''Add it to &lt;code&gt;/etc/modules&lt;/code&gt; to automatically load it on boot.''<br /> <br /> This does not seem to be necessary (any more)?<br /> <br /> [[User:Anianz|Anianz]] ([[User talk:Anianz|talk]])<br /> <br /> == Bringing up an interface using ifupdown-ng ==<br /> <br /> The netifrc package is perfect for mounting the wg0 interface at boot in the specific case of using the plain wg command ( https://wiki.gentoo.org/wiki/Wireguard#netifrc ), but only available for the edge branch.<br /> <br /> What is the right approach for loading the configuration and mount the wg0 network interface, at startup in the stable branch?<br /> <br /> [[User:Konki|Konki]] ([[User talk:Konki|talk]])</div>

Konki https://wiki.alpinelinux.org/w/index.php?title=Talk:Configure_a_Wireguard_interface_(wg)&diff=21957 2022-06-11T10:39:31Z

<p>Konki: /* Bringing up an interface using ifupdown-ng */ new section</p> <hr /> <div>== Bringing up an interface using wg-tools ==<br /> <br /> ''Then load the module''<br /> <br /> modprobe wireguard<br /> <br /> ''Add it to &lt;code&gt;/etc/modules&lt;/code&gt; to automatically load it on boot.''<br /> <br /> This does not seem to be necessary (any more)?<br /> <br /> [[User:Anianz|Anianz]] ([[User talk:Anianz|talk]])<br /> <br /> == Bringing up an interface using ifupdown-ng ==<br /> <br /> The netifrc package is perfect for mounting the wg0 interface at boot in the specific case of using the plain wg command ( https://wiki.gentoo.org/wiki/Wireguard#netifrc ), but only available for the edge branch.<br /> <br /> What is the right approach for loading the configuration and mount the wg0 network interface, at startup in the stable branch?</div>

Konki