Which format is the correct format to use for mkinitcpio.conf?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

I am confused about which is the proper formatting to use within mkinitcpio.conf ... I have noticed sometimes double quotes are used and other times parentheses to close off the users desired hooks, modules, etc. settings.

Example:

HOOKS="base udev autodetect block filesystems"

HOOKS=(base udev autodetect block filesystems)

So which format is the right one to use?

asked Mar 9 at 10:39

Anonymous User

416

add a comment |

Example:

HOOKS="base udev autodetect block filesystems"

HOOKS=(base udev autodetect block filesystems)

So which format is the right one to use?

asked Mar 9 at 10:39

Anonymous User

416

add a comment |

Example:

HOOKS="base udev autodetect block filesystems"

HOOKS=(base udev autodetect block filesystems)

So which format is the right one to use?

asked Mar 9 at 10:39

Anonymous User

416

Example:

HOOKS="base udev autodetect block filesystems"

HOOKS=(base udev autodetect block filesystems)

So which format is the right one to use?

linux arch-linux kernel linux-kernel mkinitcpio

asked Mar 9 at 10:39

Anonymous User

416

asked Mar 9 at 10:39

Anonymous User

416

asked Mar 9 at 10:39

Anonymous User

416

asked Mar 9 at 10:39

Anonymous User

416

asked Mar 9 at 10:39

Anonymous User

416

add a comment |

1 Answer
1

active

oldest

votes

This is the old style:

HOOKS="base udev autodetect block filesystems"

And this is the current new style:

HOOKS=(base udev autodetect block filesystems)

see also arrayize config vars in mkinitcpio.conf

This change was done in 2017, so you should see the old style only in older installs.

Both styles work so don't worry too much about it.

edited Mar 9 at 10:58

answered Mar 9 at 10:52

frostschutz

27.6k15790

add a comment |

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505299%2fwhich-format-is-the-correct-format-to-use-for-mkinitcpio-conf%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

This is the old style:

HOOKS="base udev autodetect block filesystems"

And this is the current new style:

HOOKS=(base udev autodetect block filesystems)

see also arrayize config vars in mkinitcpio.conf

This change was done in 2017, so you should see the old style only in older installs.

Both styles work so don't worry too much about it.

edited Mar 9 at 10:58

answered Mar 9 at 10:52

frostschutz

27.6k15790

add a comment |

This is the old style:

HOOKS="base udev autodetect block filesystems"

And this is the current new style:

HOOKS=(base udev autodetect block filesystems)

see also arrayize config vars in mkinitcpio.conf

This change was done in 2017, so you should see the old style only in older installs.

Both styles work so don't worry too much about it.

edited Mar 9 at 10:58

answered Mar 9 at 10:52

frostschutz

27.6k15790

add a comment |

This is the old style:

HOOKS="base udev autodetect block filesystems"

And this is the current new style:

HOOKS=(base udev autodetect block filesystems)

see also arrayize config vars in mkinitcpio.conf

This change was done in 2017, so you should see the old style only in older installs.

Both styles work so don't worry too much about it.

edited Mar 9 at 10:58

answered Mar 9 at 10:52

frostschutz

27.6k15790

This is the old style:

HOOKS="base udev autodetect block filesystems"

And this is the current new style:

HOOKS=(base udev autodetect block filesystems)

see also arrayize config vars in mkinitcpio.conf

This change was done in 2017, so you should see the old style only in older installs.

Both styles work so don't worry too much about it.

edited Mar 9 at 10:58

answered Mar 9 at 10:52

frostschutz

27.6k15790

edited Mar 9 at 10:58

answered Mar 9 at 10:52

frostschutz

27.6k15790

answered Mar 9 at 10:52

frostschutz

27.6k15790

answered Mar 9 at 10:52

frostschutz

27.6k15790

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu