Linking a category
Regarding , you can use a colon to link categories:
It's a problem I met, for which I couldn't find a solution with googling, so I had to retreat to asking at IRC. In short, it's that the default Archlinux config shipped somewhere in /etc/ overwrites variables for runtime, i.e. one can't even overwrite them manually. I thought it would be useful to many others. Probably, it may cause problems not only with "oh-my-zsh", but I decided to put info in that paragraph because I'm not sure if there is a better place.
And sorry for html formatting, markup is pretty unusual, and the formatting page is surprisingly unhelpful. I.e. how to write a link I figured out only because I thought, perhaps wikipedia.org using the same markup formatting; which turned out to be right. Hi-Angel (talk) 10:23, 6 October 2016 (UTC)
- User's files are sourced after their system-wide counterparts (i.e.
~/.zshrcis sourced after
/etc/zsh/zshrc), so things set in
~/.zshrcshould normally not be undone by
/etc/zsh/zshrc. But I guess it's possible for
/etc/zsh/zshrcto define a function that changes
$PROMPTunder certain conditions. I probably shouldn't have called the content questionable.
- About formatting, start with Help:Editing then Help:Style, Help:Style/Formatting and punctuation and Help:Style/White space. There is also Help:Cheatsheet. -- nl6720 talk 10:48, 6 October 2016 (UTC)
GRUB UEFI install
nl6720 rEFInd is able to:
- auto-detect the kernels if the file system drivers are there
- launch the last one booted - for this to work it needs to list all unfolded
so the following minimal configuration works:
# cp /usr/share/refind/refind_x64.efi /esp/EFI/Boot/bootx64.efi # cp -r /usr/share/refind/drivers_x64/ /esp/EFI/Boot/ # echo 'extra_kernel_version_strings linux,linux-lts,linux-git;' > /esp/EFI/Boot/refind.conf # echo 'fold_linux_kernels false' >> /esp/EFI/Boot/refind.conf
rod smith was so kind to add the "extra_kernel_version_strings" option end of 2017 so rEFInd could handle the kernel naming conventions in arch. and with it, rEFInds problem of finding the correct fallback image was fixed, and the necessity to provide a configuration. there is no editing of a file necessary, no additional boot parameters, no tinkering with nvram, etc. currently i find really hard to detect out of the description that this works. i am inclined to break up the text slightly different - not focussing on "manual" and "scripted", and "configuration" but more in "install into EFI default location", "install in rEFInd location", "secure boot". currently the section "scripted" contains secure boot, shim, editing files. what you think? --Soloturn (talk) 03:40, 14 March 2018 (UTC)
- The first sentence of the section mentions the
refind-installscript so it should be obvious that the whole section is about using the script. Just in case I've now renamed the section to avoid any confusion. Secure boot is under the "Scripted installation" section because
refind-installprovides a way to automate installation on Secure Boot enabled systems. I'll repeat, the whole section is about
refind-installand its provided options.
extra_kernel_version_stringswas added to support multiple kernels without version numbers in their filenames, unless I've missed something rEFInd still doesn't support automatically detecting and matching fallback initramfs images with their respective kernels.
- I've removed your "minimal configuration" because it mixed installation (i.e. getting rEFInd binary to the ESP) and configuration (editing
refind.conf), those sections are split for a good reason. Before drastically changing an article, you must first discuss it in the article talk page (Talk:REFInd in this case), please read ArchWiki:Contributing#Announce article rewrites in a talk page. Also I would not accept adding
echo 'extra_kernel_version_strings linux,linux-lts,linux-git;' > /esp/EFI/Boot/refind.confto rEFInd, the
/usr/share/refind/refind.conf-samplefile has a lot of comments explaining its content, it's more useful to copy the sample and edit it. -- nl6720 (talk) 07:20, 14 March 2018 (UTC)
ok, will try. i had enough difficulties with boot loader installation. so much that i took the time to address it with the software itself, and the wiki page. i even asked rod if he would be able to adjust refind a little to make it configuration-less. but he thought using the 2 lines are appropriately minimal - and no editing of a config file would be necessary. while coding arch kernel names into rEFInd would be a bad idea. --Soloturn (talk) 06:18, 19 March 2018 (UTC)
- Closing. Any further discussion will be in Talk:REFInd#add a paragraph with simple installation. -- nl6720 (talk) 08:47, 19 March 2018 (UTC)
Thank you for the improvements to my solution to the firewall. Could I just ask, why is it you chose to explicitly list most the packet types opposed to allowing them all? Is there a security concern when the ones you omitted?
- I compared Wikipedia:Internet Control Message Protocol#Control messages and Wikipedia:Internet Control Message Protocol for IPv6#Types with the ICMP types with names in nftables proto.c. I skipped those listed as deprecated and the one I didn't think should be needed. AFAIK only the redirects can potentially have security issues, so I skipped those too. I doubt it's really that much safer to specify only those ICMP types so it could just be considered a personal preference to allow only those that could be needed. -- nl6720 (talk) 15:19, 2 July 2018 (UTC)
Closing of several discussions in one edit
- Sorry! Somehow I overlooked that rule in Help:Discussion#Closing a discussion. -- nl6720 (talk) 11:55, 20 September 2018 (UTC)
>that is obvious since the examples provide full HOOK lines and "udev" is not listed in the example with the "systemd" hook
It is not obvious. The obvious ones are the ones that are highlighted.
How about highlighting udev too so it becomes obvious?