Difference between revisions of "Talk:Mkinitcpio"

From ArchWiki
Jump to: navigation, search
(systemd hook ?)
m (WARNING: No modules were added to the image. This is probably not what you want.: remove closed discussion)
 
(33 intermediate revisions by 13 users not shown)
Line 1: Line 1:
 
{{DISPLAYTITLE:Talk:mkinitcpio}}
 
{{DISPLAYTITLE:Talk:mkinitcpio}}
== keymap v. consolefont ==
+
== Talking about other hooks and a more generic view of the early userspace ==
Using the consolefont hook seems to work as advertised in /lib/initcpio/hooks/consolefont and {{ic|mkinitcpio -H  consolefont}} i.e. I get my font in the early stages of the boot process, while using keymap only sets the font a bit later and mangles Polish accented characters if I'm using {{ic|1=DAEMON_LOCALE="yes"}}. I think we need to add consolefont to the HOOKS list and fix keymap hook description. -- [[User:Karol|Karol]] 11:10, 21 January 2012 (EST)
+
I am the current maintainer of the the {{AUR|dropbear_initrd_encrypt}}, and, I've also developed some other mkinitcpio hooks, such as: {{AUR|mkinitcpio-ppp}} and {{AUR|mkinitcpio-ddns}}. I will write some wiki pages describing them, but I would also like to talk more about the early userspace. So, my question is, should I make an early userspace page, should I write a page just for the hooks? Should I write it and make it related to the mkinitcpio page? Thanks in advance.
  
== systemd hook ? ==
+
[[User:Grazzolini|Grazzolini]] ([[User talk:Grazzolini|talk]]) 01:03, 11 February 2015 (UTC)
Can someone point me to the "systemd" hook added by this revision?: https://wiki.archlinux.org/index.php?title=Mkinitcpio&oldid=267771
 
It's not listed by mkinitcpio -L and I don't see it in testing (0.15) too. What is meant by it? Thanks --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 18:50, 25 July 2013 (UTC) Ah, found this thread: https://bbs.archlinux.org/viewtopic.php?id=167153&p=2]this[/url]
 
So I guess the wiki is just flying ahead of [core].
 
  
:True! However mkinitcpio-p works, and it does not error free. why? [[User:Veleno77|Veleno]] ([[User talk:Veleno77|talk]]) 19:45, 25 July 2013 (UTC)
+
:It depends a lot on how much content you're actually going to write. I suggest starting by expanding on the early userspace in [[Arch boot process]]; then, if what you write gets too long, we can always consider splitting the page. About custom/additional hooks you might create a section below [[Mkinitcpio#Common hooks]], following the same principle: if the content gets too long/detailed to stay in the page, we can split it later. In any case, it's very important that you try your best to avoid duplicating existing information in other articles, and instead either add links to them, or move that information to your new content, if it fits best there, and add links to the new location from the articles where the info was removed. [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 4:32, 12 February 2015 (UTC)
{{hc|mkinitcpio -p linux|
 
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
 
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
 
==> Starting build: 3.10.2-1-ARCH
 
  -> Running build hook: [base]
 
  -> Running build hook: [systemd]
 
  -> Running build hook: [autodetect]
 
  -> Running build hook: [fsck]
 
  -> Running build hook: [modconf]
 
  -> Running build hook: [block]
 
  -> Running build hook: [keyboard]
 
  -> Running build hook: [keymap]
 
  -> Running build hook: [filesystems]
 
  -> Running build hook: [shutdown]
 
==> Generating module dependencies
 
==> Creating gzip initcpio image: /boot/initramfs-linux.img
 
==> Image generation successful
 
}}
 
  
::Why would you expect this to fail? The systemd hook is included with... systemd. [[User:Falconindy|Falconindy]] ([[User talk:Falconindy|talk]]) 14:32, 26 July 2013 (UTC)
+
::Thank you for your information [[User:Kynikos|Kynikos]]. I'll be contributing these changes very soon. [[User:Grazzolini|Grazzolini]] ([[User talk:Grazzolini|talk]]) 12:54, 12 February 2015 (UTC)
  
:::mmm... because {{ic|mkinitcpio -L}} don't show systemd hook, then it is assumed there is no.[[User:Veleno77|Veleno]] ([[User talk:Veleno77|talk]]) 15:01, 26 July 2013 (UTC)
+
== Mark /usr with a passno of {{ic|2}}, not {{ic|0}} ==
::::And it may fail because [core] does not have it yet in systemd (204). Only testing (206) has it as of today. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 17:03, 26 July 2013 (UTC)
 
  
:::::I have the systemd version 204-3. My example is refer to this package.[[User:Veleno77|Veleno]] ([[User talk:Veleno77|talk]]) 18:31, 26 July 2013 (UTC)
+
[[mkinitcpio#/usr as a separate partition]] firmly suggests to mark {{ic|/usr}} with a {{ic|passno}} of {{ic|0}} in {{ic|/etc/fstab}}. The way I understand {{ic|man fstab}}, {{ic|2}} is the correct number for the task. Am I wrong? [[User:Regid|Regid]] ([[User talk:Regid|talk]]) 19:09, 6 April 2017 (UTC)
:::::Now this confuses me, are we not talking about "/usr/lib/initcpio/install/systemd" which is not in the filelist of 204-3 but in 206? 
+
: It also suggests adding the {{ic|fsck}} hook to your config. Seeing as the regular fsck binaries reside on the {{ic|/usr}} partition, this is needed to actually make it possible to fsck it at startup. The entry in {{ic|/etc/fstab}} should thus be {{ic|0}}. [[User:Koneu|Koneu]] ([[User talk:Koneu|talk]]) 07:27, 7 April 2017 (UTC)
{{hc|$ pacman -Qil systemd #grep initcpio/install/ |
+
::I see your point about the binaries residing on /usr. Still, with a passno of {{ic|0}} you set no automatic fsck at all, don't you? Would you set passno for / to {{ic|0}} when usr is an integral part of /?
systemd /usr/lib/initcpio/install/
+
::Indeed the fsck hook copies fsck binaries to the initramfs, and possibly ignores passno for / and /usr at runtime. As an aside, its help text should mention usr, not just /.  
systemd /usr/lib/initcpio/install/timestamp
+
::[[User:Regid|Regid]] ([[User talk:Regid|talk]]) 10:12, 7 April 2017 (UTC)
systemd /usr/lib/initcpio/install/udev}}
 
:::::I am at a loss. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 00:41, 27 July 2013 (UTC)
 
::::::If mkinitcpio doesn't complain about the systemd hook not existing, then it exists. Rather than blindly stabbing at pacman's DB, why don't you go see what exists in /usr/lib/initcpio/install/systemd ? Hooks which don't exist '''will''' error out. [[User:Falconindy|Falconindy]] ([[User talk:Falconindy|talk]]) 14:31, 27 July 2013 (UTC)
 
:::::::While I did not write it earlier, I indeed looked there too - it does not exist and, of course, fails. That was why I created this discussion in the first place.  
 
:::::::Besides, why blind stabbing? I followed up your earlier comment that it is included with systemd - and saw it is, yes, in 206. Question rather is how else is it shipped before 206-1 so that Veleno77 appears to have it, but not the machine here with 204-3? i686 to 64 diff? No. Other ideas? --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 15:32, 27 July 2013 (UTC)
 

Latest revision as of 15:32, 11 April 2017

Talking about other hooks and a more generic view of the early userspace

I am the current maintainer of the the dropbear_initrd_encryptAUR, and, I've also developed some other mkinitcpio hooks, such as: mkinitcpio-pppAUR and mkinitcpio-ddnsAUR. I will write some wiki pages describing them, but I would also like to talk more about the early userspace. So, my question is, should I make an early userspace page, should I write a page just for the hooks? Should I write it and make it related to the mkinitcpio page? Thanks in advance.

Grazzolini (talk) 01:03, 11 February 2015 (UTC)

It depends a lot on how much content you're actually going to write. I suggest starting by expanding on the early userspace in Arch boot process; then, if what you write gets too long, we can always consider splitting the page. About custom/additional hooks you might create a section below Mkinitcpio#Common hooks, following the same principle: if the content gets too long/detailed to stay in the page, we can split it later. In any case, it's very important that you try your best to avoid duplicating existing information in other articles, and instead either add links to them, or move that information to your new content, if it fits best there, and add links to the new location from the articles where the info was removed. — Kynikos (talk) 4:32, 12 February 2015 (UTC)
Thank you for your information Kynikos. I'll be contributing these changes very soon. Grazzolini (talk) 12:54, 12 February 2015 (UTC)

Mark /usr with a passno of 2, not 0

mkinitcpio#/usr as a separate partition firmly suggests to mark /usr with a passno of 0 in /etc/fstab. The way I understand man fstab, 2 is the correct number for the task. Am I wrong? Regid (talk) 19:09, 6 April 2017 (UTC)

It also suggests adding the fsck hook to your config. Seeing as the regular fsck binaries reside on the /usr partition, this is needed to actually make it possible to fsck it at startup. The entry in /etc/fstab should thus be 0. Koneu (talk) 07:27, 7 April 2017 (UTC)
I see your point about the binaries residing on /usr. Still, with a passno of 0 you set no automatic fsck at all, don't you? Would you set passno for / to 0 when usr is an integral part of /?
Indeed the fsck hook copies fsck binaries to the initramfs, and possibly ignores passno for / and /usr at runtime. As an aside, its help text should mention usr, not just /.
Regid (talk) 10:12, 7 April 2017 (UTC)