Is the wiki missing documentation for a popular software package or coverage of an important topic? Or, is existing content in need of correction, updating, or expansion? Write your requests below and share your ideas...
Here, list requests for topics that you think should be covered on ArchWiki. If not obvious, explain why ArchWiki coverage is justified (rather than existing Wikipedia articles or other documentation). Furthermore, please consider researching and creating the initial article yourself (see Help:Editing for content creation help).
Left-Handed Adjustments for Desktop Environments
I was thinking it would be helpful for lefties if there were a list of configuration options for each desktop environment that facilitate left-handed use of mice and touchpads. I'm not sure if this is related enough to Arch to include in this wiki, but I haven't had a lot of luck finding information for my own DE (KDE) let alone for others. I will start writing down information, and if no one else thinks there should be a separate page for this, I'll just add the information I find to each individual DE's page. —ajrl 2013-08-11T15:09−06:00
iPXE is a powerful network boot program with many features. Currently, there is no iPXE specific page to describe iPXE in details. There are some pages mentioning iPXE in the wiki, mostly related to network booting, without any further instruction on how to get iPXE to work. So I think it's worth to add a page with detailed iPXE explanation in the wiki. Alive4ever (talk) 10:08, 21 July 2016 (UTC)
- I have recently added
[community], which apart from the defaults also features the binaries required to allow iPXE booting towards the Arch Linux specific endpoint. It would be great to have a page for this and I will try to work on iPXE as soon as time permits. Davezerave (talk) 09:54, 17 June 2021 (UTC) to
- Linux namespaces
- lspci and lsusb
- pacstrap and genfstab
- terminfo (termcap)
- LPD, LPR
- JSON, XML, CSV, JS, CSS
- YAML, TOML
Unfortunately, Mirrors#Troubleshooting is a bit lacking and can definitely benefit from more information such as how to detect a bad mirror. A mirror becoming faulty is not extremely uncommon so this topic should definitely be covered, including who to tell about the bad mirror so it can e.g be removed from the mirrorlist.
This topic is impacting enough people that it is worth putting it into here.
- The bad mirror case i covered now. Should another section, about a mirror returning 404, be added or information in is Pacman#Packages_cannot_be_retrieved_on_installation enough? --Mpan (talk) 08:19, 6 August 2021 (UTC)
- Thanks for contributing! The content you added looks good. Some information helping how to determine that a mirror is faulty is still missing. The section you mentioned is unfortunately not containing enough information on that and would be specific to the Mirrors article anyways. If any developer or other person knowing mirror internals sees this, please share your knowledge in debugging mirrors.
- -- NetSysFire (talk) 17:19, 6 August 2021 (UTC)
Since this is soon to be a desktop environment based off KDE, Cutefish arch documentation needs to be written as the user can refer to the ArchWiki and fix problems with Cutefish on Arch.
- The page Cutefish has been created :) Closing. --Erus Iluvatar (talk) 11:09, 29 September 2022 (UTC)
qBittorrent page similar to Transmission's
I think that a page on qBittorrent on how to set-up qBittorrent for cli-use, would be helpful. Transmission has a guide on how to set-up the service and how it uses /var/lib/transmission as a user folder. I set this up for qBittorrent on my own machine yesterday my modifying files such as /usr/lib/sysusers.d/transmission.conf to fit qBittorrent. I would be up to creating the first draft.
Here, list requests for correction or other modification of existing articles. Only systemic modifications that affect multiple articles should be included here. If a specific page needs modification, use that page's discussion or talk page instead and one of the article status templates.
As a rolling release, Arch is constantly receiving updates and improvements. Because of this the Arch wiki must be updated quickly to reflect these changes.
Change drive naming/accessing to UUID?
Trying to install drives with/out Luks, LVM on internal, external drives is quite complicated currently. Following the ralated articles suggest different ways of reaching the goal. Many different drive name conventions are suggested, eg.:
Some of them don't work with portable external drives. This overcomplicates setting up encrypted drives in different situations. My suggestion is, to change all drive related articles to one specific solution of addressing drives universal. Currently I think of UUDI drive naming as a way to go. This would ease the process of drive naming in all kinds of situations:
- The reader is guided through system setup along one red line
- Troubleshootiing "no drie found" is strait forward
- Many sections become clearer to read even when not reading the whole article
- Articles are easier to write and maintain
- Beginners have an easier read and geta better idea of how to access drives
- Accessing internal/external encrypted drives is easy
' LMV or other virtual file systems are easier to describe and setup
Ok, I know it is a big suggestion. I wanted to bring it up here, bacause I have the impression that following one primary path would help a lot - everyone involved. It doesn't need to be done in one day. While I think to have one suggested guideline would be a good start. Then with thain mind, we all have it easier to change those sections while Writing/editing Wiki entries.
- Hi, To your own examples above: using an UUID for a /dev/mapper/* device declaration is generally unnecessary (the uniqueness of the device is determined when it is mapped). I think you overestimate the amount of users who actually require setting up the examples where it really matters (e.g. external drives). What I don't understand is why you consider using UUIDs being easier to read/describe. For starters the terribly long UUIDs will break formatting in many cases, e.g. making code blocks in-text not possible. An UUID itself gives no contextual hint, something that a device name does. If you look at the three examples in Persistent block device naming#Boot managers, you really find the UUID one the easiest?
- I think you are certainly right in that we may lack crosslinks to Persistent_block_device_naming in some articles where it may be important to use an UUID. Maybe we also need an example section to illustrate singular important points in Persistent block device naming and maybe there are individual articles/sections where content should indeed use a form of persistent naming straight away.
- Suggestion: How about using Talk:Persistent block device naming to assemble a list of particular article sections with content where persistent naming should be made more prominent? That way we could also figure if and which examples may be useful to be added. --Indigo (talk) 17:47, 30 March 2015 (UTC)
- Hi, I started this topic because "by design" Linux has so many ways to assign drives and the Wiki uses them kind of "randomly". Finding the best drive naming method for the Wiki is my intention. Giving the reader a hand, by enabling him/her to understand one way of accessing drives and collect all the others somewhere.
- I'm suggesting UUIDs, because they can be used for local and mobile situations. They are easy to use. The UUID format is universal and is independent of the location (local/mobile) or the context (LVM, Raid, Luks, ...) in which they are used.
- The reason why I'm bring this up is, that it seems, the wiki has currently no standardized form of drive path declaration. If we can find one practical method, it will be easier to write, edit and maintain articles. Everyone involved will know then, which method is the recommended.
- Therefore, I wanted to start an open conversation, to find ideas to improve the situation. I guess, UUIDs are also a good choice, because they are easy to substitute with pseudo code, eg.:
- "mount /dev/disks/by-uuid/e9ea05ce-0ccb-87a1-c71e-90fab8be1944 /mnt"
- could then be written as:
- "/dev/disks/by-uuid/[UUID] /mnt"
- instead of having the choice of:
- "mount /dev/sda3 or
- /dev/mapper/vgroup--lvm-root or
- /dev/md/0 or
- /dev/md0 or
- ... /mnt"
- The reader immediately knows:
- "I just need to alter [UUID]"
- There is no need to know of all possible alternative methods making use of the Wiki example. Because the user already learned (Beginners Guide) how to determine UUIDs those examples are well adoptable.
- Reduced uncertainties like the reader had before:
- Can I use that example's local path in my case, too?
- What's my case anyway? And how is it different for the one provided?
- Is my drive IDE, SATA or ... what?
- Where and how is the correct format of my drive/partitions's path?
- I need an example to boot my USB drive everywhere. That provided example doesn't work for me. Where is the article I need to know?
- I skimmed through many articles, no success so far. There must be one, but where?
- I have an Luks, Raid, LVM (or mixed) situation here. The current article just uses /dev/sdi3. What to do?
- Which article do I need to read first? I can't use the current example. How about alternatives?
- The reader's issue is, that "/dev/sdb3" drive paths aren't that descriptive without the knowledge of how and when they are used as written. They are nice for that particular situation, but may immediately loose their meaning in other use cases?!
- If we could pick out one drive naming method the Wiki uses, then we are able to eliminate many of the upper soliloquies and ...
- We get a good article structure for the writer, reader and maintainer.
- The provided method will work in either situation (local/mobile/..).
- All alternative methods can be listed in one conversion article/table.
- The reader can quickly move on reading the article:
- Great, I already know how to determine UUIDs. I just change it..
- As you mentioned, crosslinks then point to one subpage, where the conversion to other alternative methods is explained.
- Don't get me wrong, I don't want to imply something is wrong with the current way the Wiki does it. This just a natural process how something grows. A bit of standardization may help here.
- I'm for UUIDs so far, because are easily exchangeable and can be written as [UUID] in the Wiki.
- OMG, I wrote a huge wall of text. Sorry for that. It's not easy and very time consuming writing down what I wanted to say. as a non-native speaker. I hope, it's now easier to understand what my intention was. I'm kind of uncertain that I found the right words. --T.ask (talk) 13:24, 31 March 2015 (UTC)
- Thank you for elaborating on the background of why you propose it. No need to apologize at all for taking the time to give input how to improve our wiki! I just want to add two thoughts on it:
- (1) One reason descriptive device declarations (/dev/sda/...) are easy to grasp is that everyone is used to them. It starts when you open any partitioning tool - you start it for a device from the /dev tree. Try to find the term "UUID" in the manpage of cfdisk/cgdisk/parted (fdisk has it, the others not a mention). With this I don't want to say your intention to introduce the user early to use persistent naming is wrong, just that using descriptive naming is common and, thereby, accessible to the reader.
- (2) I like your idea of using a "/dev/disks/by-uuid/[
YOURUUID] /mnt" format (we call other instances of such 'pseudo-variables'). Still, if you used it in an article context, e.g. an encrypted LVM, you would still have to more verbosely describe which dev/blockdevice/vg/lv UUID is meant to be mounted on /mnt. I still can't really picture for myself how writing and reading it is easier in general.
- As I wrote above, I agree we might need to pinpoint the advantages of persistent naming more, but we do some already (e.g. right from the start: Beginners' guide#Generate an fstab). In short I believe we are better off with the way we have it (no rule on it, as long as the contribution fits the article contributed to all editors may choose what's best in context). That's it from me. Looking forward to read feedback & other opinions. --Indigo (talk) 20:46, 31 March 2015 (UTC)
- IMO man page examples are sometimes a bit behind "new standards". That's natural and this shouldn't prevent us from moving a bit more forward. With Arch we have UUIDs - lets use them :)
- In case the user doesn't know UUIDs, we will guide him/her to a short conversion-table/article on how to switch to UUIDs. Actually it's much easier to grasp than often thought:
- Just enter lsblk -f and it's obvious which UUID points to which drive in any context (raid, luks, lvm, ...). As this Get UUID example shows, just copy the corresponding UUID and use it with all UUID Wiki examples. IMHO it's quite easy.
- I see where you are coming from, while I'm confident the reader will learn fast how UUIDs work. A new user will not even know which other options have been there before. Moreover, as the reader is already familiar with UUIDs he/she won't experience future problems with moving drives around. The experienced user just reads the conversion-table/article.
- You see, I'm quite confident that the user will grasp UUIDs easily. Also, this will prevent him/her from experiencing future problems. We just need the courage to do the first step. It's not something we need to do in one day. We have all the time to slowly move into one direction.
- That's why I would also appreciate other opinions on this topic here.
- T.ask (talk) 12:45, 1 April 2015 (UTC)
- Hi, T.ask, thank you for discussing this, however I'm not sure if this is all only theoretical or you have a precise idea of how to put it into practice, because after reading all the discussion I haven't understood very well how this idea would change our articles. At this stage you must choose one of our important articles, e.g. LVM, and explain us how the article would change in details, so we can discuss on something more tangible. — Kynikos (talk) 14:37, 2 April 2015 (UTC)
- Hi, Kynikos. Yes, it's always better to have a good practical example if things seem to be complicated. I'm quite busy right now. When I find the time, I will start changing the Wiki (slowly) as I mentioned before. LVM is a nice example, while I would like to start with those sections which are easier to adapt and more commonly used. Especially if I need to add a new subsection (How do you work with UUIDs) beforehand. --T.ask (talk) 10:44, 21 April 2015 (UTC)
Drop of i686 support
Following  I've done these edits for the moment:
There are so many other articles that need updating, and also the edits above will need to be amended after November 2017. I think it's better to decide here whether we remove all the i686 content immediately, or we keep it until the final deprecation and do the cleanup then.
- Hi, I think for some of content it will depend on further decisions of the devs along the timeline, e.g. will there be changes to
arch=options. We should wait a little to see how the migration plan looks like. IMHO it is useful to start updating once a topic is clear, i.e. before the deadline. Another moving target is whether a community effort to keep i686 somewhat establishes itself; any such would have an impact on what to change how.
- In general I believe the related content changes will be so wide ranging that we should open a Archwiki:Requests/Drop of i686 support (or a top-level link like Archwiki:Drop of i686 support - easier to crosslink) to link to from here. Better to keep overview.
- --Indigo (talk) 09:32, 27 January 2017 (UTC)
- schroot redirects to Install bundled 32-bit system in 64-bit system. I think we should continue to have a page showing an example of setting up an schroot. It's sometimes useful to run Fedora, Ubuntu, etc in schroot. I suppose the article should be altered (and re-titled) to use something other than 32-bit Arch as the example. Bobpaul (talk) 17:46, 17 July 2017 (UTC)
- In the end, with no official repository of i686 dependencies to build against, there is no longer any method of building natively 32bit packages in Archlinux (the only way to do so would be to create a build chroot using Archlinux32's repository). There's probably very little use for this anyway and as such, I've archived the relevant pages. quequotion (talk) 14:53, 5 June 2019 (UTC)
For some x86_64 capable hardware there are 32-bit UEFI restrictions. Example section: Unified Extensible Firmware Interface#UEFI Firmware bitness.
It needs to be checked whether
i386.efi bootloader files will continue to be built after i686 is dropped (FS#52772). Depending on result, it may be useful to rebase Category:Boot loaders content to x86_64 early on?
- Turns out my prior research was bad, 32-bit efi files are not packaged anyhow. Hence, users requiring those need to generate them, see FS#52772 for details. Still it is useful to weave this info in when references to i686 are eliminated in Category:Boot loaders articles. --Indigo (talk) 09:24, 2 February 2017 (UTC)
- I've done a little cleanup about this right now but there is probably some left. --Erus Iluvatar (talk) 19:12, 30 January 2022 (UTC)
In preparation to making all (php) webapps use a dedicated user, I extended information on PostfixAdmin and realized, that the information on php-fpm is scattered all over the articles of nginx and apache (and probably all over some other web server pages as well). I think the citation/ linking in all of the web server pages and the php web application pages would greatly improve, if this information was moved to a dedicated page, or to a sub-page for PHP, as it is quite PHP specific (unlike e.g. uwsgi). Davezerave (talk) 00:55, 26 May 2019 (UTC)
Templates & pages that need to be modified
I am modifying the template to deprecate Template:META Box Red, Template:META Box Blue and Template:META Box Green, but I cannot modify the Arabic template (probably because Arabic is arranged from right to left). These templates need to be modified:
Template:Warning (العربية) Template:Note (العربية) Template:TranslationStatus (العربية) Template:Tip (العربية)
- I've done Warning, Note and Tip, but yeah the rest gets trickier... -- Kynikos (talk) 11:40, 13 June 2020 (UTC)
- If Red, Blue and Green are deprecated, probably Template:META Box Yellow should follow, or be renamed to something more meaningful. -- Kynikos (talk) 04:22, 14 June 2020 (UTC)
- I think I've fixed Template:TranslationStatus (العربية), fixed the last content pages using Template:META Box Red, the last content page for Template:META Box Blue is Talk:Pacman so I've left it alone, fixed the last content pages using Template:META Box Green and Template:META Box Yellow looks good too ! --Erus Iluvatar (talk) 19:50, 30 January 2022 (UTC)
- I'm looking at the oldest pages flagged for archiving, which are these four META Boxes.
- Template:META Box Yellow is only used in Template:Committed identity, but there is no replacement class in MediaWiki:Common.css.
- Template:META Box Red is still used in MediaWiki:Spamprotectiontext which is protected but also begs the same question as before.
- Template:META Box Green is only used in two user pages : should anything be done to those before archiving ?
- Template:META Box Blue is also only used in two user pages, so the same question applies.
- --Erus Iluvatar (talk) 19:22, 2 March 2022 (UTC)
Here, list requests for repetitive, systemic modifications to a series of existing articles to be performed by a wiki bot.
It'd be nice if a bot went around changing links to packages that have a wiki entry to links to the wiki entry (e.g. change git), possibly also for aur packages (e.g. AUR to dropbox). Jabranham (talk) 19:42, 31 July 2018 (UTC)to
- It's not that simple because package links like in git#Installation, List of applications and probably many other places should not be replaced. -- Lahwaacz (talk) 19:35, 11 August 2018 (UTC)
Some languages are hosted on external wikis, and I want the bot to automatically add / update language links for languages hosted on external wikis so that users do not need to add them manually. -- Blackteahamburger (talk) 15:27, 20 May 2020 (UTC)
- External wikis can use different titles than "English title (Language)" and since the bot does not speak human languages, it can't figure out which links should be added on which pages. -- Lahwaacz (talk) 08:34, 21 May 2020 (UTC)
Can the hints for Template:Broken package link marked on the localization page use the localized version? This allows users who do not understand English to understand the status of the software package. -- Blackteahamburger (talk) 11:34, 26 May 2020 (UTC)
- If you manually translate the hint, the bot will overwrite it to English later. Translations would have to be added to wiki-scripts, I'm not sure how to best do it. -- Lahwaacz (talk) 11:38, 26 May 2020 (UTC)
Arch's git URLs
Sooner or later git.archlinux.org will cease to exist. It's not clear when (or if) there will be redirects and after a project has moved to gitlab.archlinux.org, the repo in git.archlinux.org might not get updated anymore. Lets prepare to update the links in the wiki pages.
- Projects on GitHub will move to gitlab.archlinux.org too. -- nl6720 (talk) 14:04, 14 June 2021 (UTC)
We already flag external links, broken packages in the repositories and AUR: could we do the same for interwiki links? I've seen a few of those manually fixed recently, in particular on translations. --Erus Iluvatar (talk) 19:41, 2 March 2022 (UTC)