Difference between revisions of "Talk:Mkinitcpio"

From ArchWiki
Jump to: navigation, search
(page title: rm closed discussion)
m (WARNING: No modules were added to the image. This is probably not what you want.: remove closed discussion)
 
(60 intermediate revisions by 17 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.
  
== udev hook ==
+
[[User:Grazzolini|Grazzolini]] ([[User talk:Grazzolini|talk]]) 01:03, 11 February 2015 (UTC)
I feel like there should be an indicator somewhere that removing the udev hook will render UUID references useless. For people like me, except I've had that problem before and knew how to recover quickly. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 07:12, 24 July 2012 (UTC)
+
 
* Hrmm? UUID= and LABEL= references are designed to still "just work". Look at resolve_device() in /usr/lib/initcpio/init_functions. blkid is used to try and immediately resolve the UUID to a block device. If and only if udev is involved, the UUID is translated to a /dev/disk path which can be waited on by poll_device (since the symlink may eventually show up). What you '''don't''' get without udev is automatic module insertion, which may cause '''all''' block device references to be useless ;) [[User:Falconindy|Falconindy]] ([[User talk:Falconindy|talk]]) 21:59, 26 July 2012 (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)
:: I may need some time to wrap my head around this, will have to re-read 'early userspace' articles. I remember having this issue in Mandriva between upgrades, but probably unrelated. Ultimate goal is shooting for <12 second boot times on SATA or USB drive. Custom kernel with all required modules built-in. [[User:T1nk3r3r|T1nk3r3r]] ([[User talk:T1nk3r3r|talk]]) 18:33, 27 July 2012 (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)
 +
 
 +
== Mark /usr with a passno of {{ic|2}}, not {{ic|0}} ==
 +
 
 +
[[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)
 +
: 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)
 +
::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 /?
 +
::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 /.  
 +
::[[User:Regid|Regid]] ([[User talk:Regid|talk]]) 10:12, 7 April 2017 (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)