On Sun Nov 29, 2020 at 1:14 PM CET, Lone_Wolf wrote:
> It wasn't clear to me (and still is not) what initramfs environment your
> questions were about.
>
>
> Do you want answers based on systemd manpages OR on a systemd initramfs
> as setup by mkinitcpio on archlinux ?
As I conjecture below, I
On 28-11-2020 19:24, Riccardo Paolo Bestetti wrote:
I'm informed on what the supported boot processed for Arch are, and I
very well known which one I'm running, as I configured it. :)
I'm grateful for your help, but you didn't really answer any of my
questions, which are about some specifics
"Riccardo Paolo Bestetti" wrote:
> I2'm trying to fully make sense of the boot process with systemd.
>
> I've read various pages from the manual, including bootup(7). There are
> two points I don't fully understand.
>
> * Filesystem mounts during initrd
> The man page, under the initrd
On Sat Nov 28, 2020 at 1:58 PM CET, Lone_Wolf wrote:
> Archlinux has its own boot process, described at [1]
>
> Check the initramfs section and you'll see a reference to mkinitcpio [2]
> .
>
> On the mkinitcpio page look at the Common Hooks section.
>
> Basically there are 2 systems that archlinux
On 28-11-2020 10:22, Riccardo Paolo Bestetti wrote:
I2'm trying to fully make sense of the boot process with systemd.
I've read various pages from the manual, including bootup(7). There are
two points I don't fully understand.
* Filesystem mounts during initrd
The man page, under the initrd
On Mon, 14 Nov 2016 23:25:45 +0100
Tung Anh Vu via arch-general wrote:
> I managed to make the boot menu screen not appear by holding the minus key
> down to 0 second timeout in the boot menu itself.
> Thanks everyone, especially David Thurstenson.
>
> PS: I still
I managed to make the boot menu screen not appear by holding the minus key
down to 0 second timeout in the boot menu itself.
Thanks everyone, especially David Thurstenson.
PS: I still have no idea, why does systemd-boot ignore the timeout setting
from loader.conf, but obeys the rest.
On Mon, Nov
timeout 0 <-- in loader.conf 1st line
default arch <-- in loader.conf 2nd line
On 11/14/2016 12:58 PM, David Thurstenson via arch-general wrote:
On Mon, Nov 14, 2016 at 12:55 PM, Tung Anh Vu via arch-general
wrote:
Exactly. I'm successfully booting, so the
I just tried and it didn't help. Just in case, is the location
/boot/loader/loader.conf correct?
Also, do I need to explicitly reload the conf file using some bootctl
command?
On Mon, Nov 14, 2016 at 7:58 PM, David Thurstenson via arch-general <
arch-general@archlinux.org> wrote:
> Try setting
On Mon, Nov 14, 2016 at 12:55 PM, Tung Anh Vu via arch-general
wrote:
> Exactly. I'm successfully booting, so the /boot/loader/entries/arch.conf is
> present and appears to be correct.
> My problem is, that I'm trying to make the boot menu to *not* appear, but
>
Exactly. I'm successfully booting, so the /boot/loader/entries/arch.conf is
present and appears to be correct.
My problem is, that I'm trying to make the boot menu to *not* appear, but
without any success.
On Mon, Nov 14, 2016 at 7:47 PM, David Thurstenson via arch-general <
On Mon, Nov 14, 2016 at 12:39 PM, Zachary Kline wrote:
> Hello,
>
> I think the boot menu will still appear, because the default boot entry just
> indicates which OS will be booted after the timeout. It doesn’t stop the menu
> from appearing, or you couldn’t pick another
Hello,
I think the boot menu will still appear, because the default boot entry just
indicates which OS will be booted after the timeout. It doesn’t stop the menu
from appearing, or you couldn’t pick another OS easily.
Best,
Zack.
> On Nov 14, 2016, at 10:02 AM, Tung Anh Vu via arch-general
>
https://wiki.archlinux.org/index.php/systemd-boot#Adding_boot_entries
Probably missing /boot/loader/entries/arch.conf
-Original Message-
From: arch-general [mailto:arch-general-boun...@archlinux.org] On Behalf Of
Tung Anh Vu via arch-general
Sent: Monday, November 14, 2016 12:03 PM
To:
On Tue, Aug 28, 2012 at 9:41 AM, Arno Gaboury arnaud.gabo...@gmail.com wrote:
Dear list,
I am testing systemd.
I have the following errors at boot:
1-failed to start packet filtering framework
iptables is installed on my system
2-boot hangs on at: reached target graphical interface
i do
On Tue, Aug 28, 2012 at 2:41 PM, Arno Gaboury arnaud.gabo...@gmail.com wrote:
Dear list,
I am testing systemd.
I have the following errors at boot:
1-failed to start packet filtering framework
iptables is installed on my system
There probably was an error restoring the iptables rules.
16 matches
Mail list logo