Difference between revisions of "User talk:Nl6720"

From ArchWiki
Jump to: navigation, search
(Firewall Limiting: re)
(acronym in title: rewrite a bit)
(3 intermediate revisions by the same user not shown)
Line 59: Line 59:
  
 
: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 [https://git.netfilter.org/nftables/tree/src/proto.c 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. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 15:19, 2 July 2018 (UTC)
 
: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 [https://git.netfilter.org/nftables/tree/src/proto.c 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. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 15:19, 2 July 2018 (UTC)
 +
 +
== acronym in title ==
 +
 +
Regarding [[Special:Diff/529121/next]] edit summary:
 +
 +
{{bc|If something is "only" known by its acronym, is it really an acronym any more?}}
 +
 +
Yes, see for example [[GIMP]], [[GNOME]], [[LXDE]].
 +
 +
[https://www.merriam-webster.com/dictionary/known Known] by definition is "generally recognized". You refer to something to be recognized later. Therefore you use generally recognized or in other words known form for reference.
 +
 +
Whole point of changing "primarily" to "only" is to reflect current practice. Because otherwise it will be a lie, because by sheer number [[ALSA]] and [[UEFI]] are primarily referred that way, but not "only".
 +
 +
Basically you either reach compromise on your loose wording or you agree that you are deliberately making exceptions to the rule that in turn does not reflect the current practice.
 +
 +
Here is less opinionated wording which relies on upstream instead of 3rd opinion:
 +
 +
{{bc|Unless the subject of the article is only referred to as an acronym by its author, prefer using the full name in the title of the article.}}
 +
 +
I'll change it to that in few hours unless you have any good reason why we should have wording that is not very different to what was before and does not in any way clear it up.
 +
 +
-- [[User:Svito|Svito]] ([[User talk:Svito|talk]]) 13:20, 8 July 2018 (UTC)

Revision as of 13:20, 8 July 2018

Linking a category

Regarding [1], you can use a colon to link categories:

Merge-arrows-2.pngThis article or section is a candidate for merging with Category:Boot loaders.Merge-arrows-2.png

Notes: foo bar (Discuss in User talk:Nl6720#)

See: mw:Help:Categories#Linking_to_a_category -- Alad (talk) 12:50, 25 August 2016 (UTC)

Thanks! -- nl6720talk 12:57, 25 August 2016 (UTC)

Email address

Hey Nl6720,

You've disabled email from other users, but I'd like to send you a private message. If interested, would you mind contacting me on alad <at> archlinux <dot> info (address in ArchWiki:Administrators)?

Cheers -- Alad (talk) 11:50, 2 October 2016 (UTC)

I re-enabled email from other users. -- nl6720talk 13:54, 2 October 2016 (UTC)

Clarification for: The content seems questionable too, but I know nothing about these frameworks

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. ~/.zshrc is sourced after /etc/zsh/zshrc), so things set in ~/.zshrc should normally not be undone by /etc/zsh/zshrc. But I guess it's possible for /etc/zsh/zshrc to define a function that changes $PROMPT under 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. -- nl6720talk 10:48, 6 October 2016 (UTC)

GRUB UEFI install

We were amending the page at the same time, can you review my latest change to see if it is consistent with your definition of esp? -- Kewl (talk) 13:04, 5 March 2018 (UTC)

Looks good to me. -- nl6720 (talk) 14:35, 5 March 2018 (UTC)

rEFInd

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-install script 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-install provides a way to automate installation on Secure Boot enabled systems. I'll repeat, the whole section is about refind-install and its provided options.
extra_kernel_version_strings was 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.conf to rEFInd, the /usr/share/refind/refind.conf-sample file 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)

Firewall Limiting

Hi Nl6720,

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?

Sainty (talk) 17:42, 1 July 2018 (UTC)

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)

acronym in title

Regarding Special:Diff/529121/next edit summary:

If something is "only" known by its acronym, is it really an acronym any more?

Yes, see for example GIMP, GNOME, LXDE.

Known by definition is "generally recognized". You refer to something to be recognized later. Therefore you use generally recognized or in other words known form for reference.

Whole point of changing "primarily" to "only" is to reflect current practice. Because otherwise it will be a lie, because by sheer number ALSA and UEFI are primarily referred that way, but not "only".

Basically you either reach compromise on your loose wording or you agree that you are deliberately making exceptions to the rule that in turn does not reflect the current practice.

Here is less opinionated wording which relies on upstream instead of 3rd opinion:

Unless the subject of the article is only referred to as an acronym by its author, prefer using the full name in the title of the article.

I'll change it to that in few hours unless you have any good reason why we should have wording that is not very different to what was before and does not in any way clear it up.

-- Svito (talk) 13:20, 8 July 2018 (UTC)