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...
- 1 General requests
- 2 Creation requests
- 3 Modification requests
- 3.1 Should we remove or archive obsolete articles?
- 3.2 Renamed software
- 3.3 index.php in url address
- 3.4 Change drive naming/accessing to UUID?
- 3.5 FAQ
- 3.6 Pacman hooks
- 3.7 Broken section links
- 3.8 Subpages in the main namespace
- 3.9 Drop of i686 support
- 4 Bot requests
- Inaccurate content
- Pages flagged with Template:Accuracy.
- Outdated content
- Pages flagged with Template:Out of date.
- Obsolete pages
- Pages flagged with Template:Archive.
- Irrelevant or unhelpful content
- Pages flagged with Template:Remove.
- Incomplete content
- Pages flagged with Template:Expansion.
- Content with language or style issues
- Pages flagged with Template:Style.
- Non-standard laptop pages
- Pages flagged with Template:Laptop style.
- Duplicate effort or overlapping scope
- Pages flagged with Template:Merge.
- Misleading names
- Pages flagged with Template:Move.
- Poor translations
- Pages flagged with Template:Bad translation.
- Incomplete translations
- Pages flagged with Template:Translateme. See also ArchWiki Translation Team.
- Incomplete content
- Pages flagged with Template:Stub (deprecated).
- Deprecated titles
- Pages flagged with Template:Redirect.
- Dead or broken links
- Pages flagged with Template:Dead link. Should be repaired or replaced.
- Templates with an undefined parameter
- Pages automatically flagged with Template:META Error
- Unexplained presence of an article status template
- Pages automatically flagged with Template:META Unexplained Status Template.
- Application listed without links to packages
- Pages automatically flagged with Template:META Missing package.
- Misspelled or deprecated templates
- Need to fix template or change to new template.
- Noindexed pages
- Automatic tracking category.
- Duplicate arguments in template calls
- Automatic tracking category.
ArchWiki contains many broken links to packages not found either in official repositories or AUR, which is the result of packages being merged, split or removed from the repositories. All pages in the main namespace are regularly checked by a bot, which checks all instances of AUR, Grp and Pkg templates, tries to automatically update them and marks them with Template:Broken package link when it is not possible to update them automatically.
To fix a broken package link, do not simply remove the reference to the packages from the wiki, do some research first:
- Search the package database (
pacman -Ss) and AUR, it is possible that the package was merged/renamed.
- If looking for a specific file, for example a binary that was part of the package, pkgfile might do the trick.
- If unsure, mark the page or section with an appropriate status template rather than completely removing the reference to the package.
To help with manual updates, each "broken package link" template provides a hint:
- "invalid number of template parameters" – All AUR, Grp and Pkg templates take exactly one parameter, but the wikitext specified more (or none). In most cases the excesive parameters should be moved to the surrounding text, or removed if already there.
- "replaced with [other package]" – The package was renamed or merged into another, which specifies the old package name in the replaces array. In most cases the old package should be simply replaced with the new one and surrounding text updated accordingly.
- "archived in aur-mirror" – Marks old AUR3 packages, which were not submitted to AUR4, or were deleted since then. You may consider resubmitting them to the AUR if interested in maintaining them.
- "package not found" – Default hint when none of the above applies.
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).
HOWTO: SAMBA PDC + LDAP
How to configure SAMBA PDC + LDAP in Arch Linux? (Moved from another page. Hokstein 19:57, 16 September 2007 (EDT))
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
Currently there is no page on ArchWiki properly describing various input methods generally. There is only Internationalization#Input_methods_in_Xorg, but it has several problems:
- missing descriptions
- X compose key does not fit in
- GTK has a default "simple" input method featuring the
Ctrl+Shift+ushortcut for entering a unicode character (this was added recently into a wrong article: ) - again, no description
- no description of XIM - outdated, but sometimes used as fallback?
So this is quite enough material to start a new great article ;)
- Update to note: While Internationalization#Input_methods_in_Xorg itself still remains a stub, we had editors contributing language specific instructions which were set as subpages of the article:
- Internationalization/Japanese and Internationalization/Korean
- --Indigo (talk) 21:57, 11 January 2015 (UTC)
An article, or even stub that links to resources, explaining what DRI is, why it's important, differences between DRI 1, 2, 3, how DRI1 is no longer supported as of xorg-server 1.13, simple xorg.conf code explaining the DRI section, enabling the composite and render extensions there, these and more. Just my thoughts.
ldns is a core package with no wiki documentation. It is also relatively new in the world of DNS tools and is not well covered on the Internet. Documentation of basic features and what it is not (eg a replacement for bind) would provide a valueable resource. MichaelRpdx (talk) 20:07, 17 February 2014 (UTC)
- The description of the official homepage mentions that several example programs are included with the library, the official docs is probably best for programmers. -- Lahwaacz (talk) 21:37, 17 February 2014 (UTC) package is "Fast DNS library supporting recent RFCs". The
Surprisingly, there is no wiki page describing the installation and configuration of Perl, unlike Python, Ruby etc. Could include the installation of CPAN modules and a list of good tutorials for beginners, too. So far there is only guides for packaging Perl and its modules (Perl Policy and Perl package guidelines respectively) -- bluestreak0 01:32, 17 April 2014 (UTC)
I was thinking that a new page for the console would be a good idea. The Wikipedia:Linux console article gives a short general overview, but obviously doesn't concern the configuration. Since it's an independent system, configured separately from any graphical environment, it would bring together several related sections across multiple articles in one place. It's a fairly complex system and difficult to cover in any depth in small sections across other articles (such as Fonts). I've put together a basic example, User:Teppic74/Linux_console. -- Teppic74 (talk) 17:11, 3 July 2014 (UTC)
- Sounds interesting, but I don't know how deep you want to go in the description, it may be too much for a single page as, according to your outline, the resulting article would cover all Fonts#Console fonts, Keyboard configuration in console, part of Extra keyboard keys, Map scancodes to keycodes and Extra keyboard keys in console. The keyboard configuration is split mainly because the configuration for Xorg is connected to it, I don't know how this would be done if the low-level description is moved. On the other hand, some of these articles could use some reorganization, so it may still be possible... -- Lahwaacz (talk) 13:17, 4 July 2014 (UTC)
- I feel this is part of the problem, that the details concerning the console are tacked on to other articles rather than being naturally associated with them. As things stand, I think the documentation is lacking. I don't think a huge amount of information is needed, it would just be helpful to be in one place, as the console is mostly isolated from the rest of the system. The other articles could link to the console article for further details. Another possibility is separate articles exclusively for the console display and keyboard, but they're obviously part of the same topic. -- Teppic74 (talk) 18:48, 4 July 2014 (UTC)
I think creating a page and mentioning ways to improve sublime-text integration with Gnome would be a good idea. The trick is if you run sublime with --class=<filename of sublime text .desktop file, e.g. sublime_text_3>, it would help Gnome and XFCE to group sublime instances with its respective desktop file. This is mentioned in the comments of the aur package but I think it's better that this would be in the wiki.--183.amir (talk) 12:41, 19 December 2014 (UTC)
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)
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 #General requests 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.
Should we remove or archive obsolete articles?
[Moved to ArchWiki talk:Administrators#Should we remove or archive obsolete articles?; keeping the section subtree here to prevent backlink breakage until the whole discussion is closed. — Kynikos (talk) 08:05, 12 April 2016 (UTC)]
List of suggested solutions
Restoring revisions and redirection
Separation of archive content
How to archive templates
index.php in url address
Admins of Arch Wiki, do you noticed, that in every page address begins with https://wiki.archlinux.org/index.php?title=? Why? It is uncomfortable. Why could not you do just article name after https://wiki.archlinux.org/? — Agent0 (talk|contribs) 22:48, 6 March 2015 (UTC)
- Administrators can't configure the entry-point urls, that's something that should be done in LocalSettings.php, which however is currently unpatchable because of FS#35545.
- Nonetheless I agree with you, urls could be prettified by removing "index.php/", I think wiki.archlinux.fr has the best configuration in this respect. Documentation is in mw:Manual:Short URL/LocalSettings.php. Backward compatibility wouldn't be a problem since urls can be easily rewritten by the http server.
- — Kynikos (talk) 01:49, 7 March 2015 (UTC)
- I have noticed, that article's path became https://wiki.archlinux.org/index.php/Page_title. Better, but still with ugly index.php. I agree with you, french arch linux wiki did varian which I wanted: just clearly https://wiki.example.com/Page_title. But according to  it is not recommended in some cases. As I understand, it just do not allow you (Pierre) to use some titles as articles, for example https://wiki.example.com/favicon.ico, but really, what reason to have such articles =D. And another problem may be that it may require root access to hosting server. Does wiki.archlinux.org is running on virtual server or it is hosted on a normal server? — Agent0 (talk|contribs) 09:59, 17 August 2015 (UTC)
- This could now be done, seeing as FS#35545 has been implemented. — Ekkelett (talk) 06:53, 6 March 2017 (UTC)
- Good point. Instead of totally shortening it, we should follow  in my view. The french version appears to be ending in what's referred to as unsupported configuration in  and you don't want to make things like processing robots.txt complex, because it will likely reveal bugs in proxies we don't want to care about. --Indigo (talk) 10:57, 6 March 2017 (UTC)
- For the records at least also KDE UserBase uses root titles, but I agree that it's better to keep a prefix. Wikipedia and Gentoo use "wiki/", while archlinux.de uses "title/". In our case I'd avoid "wiki/" since we already have it in the third-level domain; I like "title/", but also "w/" or "t/" are interesting options. — Kynikos (talk) 08:44, 7 March 2017 (UTC)
- I may have been too quick dismissing root titles, just saw the unsupported statement and because of that thought it's more to it than the favicon.ico example used above. We could ask devops about opinion in due course. Regarding a prefix: A singular "w/" or "t/" is not self-speaking as "title/", I like that too. --Indigo (talk) 15:31, 10 March 2017 (UTC)
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)
The FAQ could use an entry like "After upgrading my kernel, I can't mount USB devices", preferably linking FS#16702. See  for a case where users are not aware of this. -- Alad (talk) 22:55, 18 September 2015 (UTC)
- +1, but I'd place it into General troubleshooting. -- Lahwaacz (talk) 07:52, 19 September 2015 (UTC)
The link-checker.py script already detects hundreds of links with broken section fragment. Before automatic solution is implemented, what would you say to automatically marking these with Template:Broken section link, similarly to how broken package links are marked with Template:Broken package link? -- Lahwaacz (talk) 14:14, 22 July 2016 (UTC)
- +1. That would be helpful indeed. Maybe leave out the hint in the template to keep it short. Indigo (talk) 17:45, 22 July 2016 (UTC)
- Perfect, thanks. It can already be seen in recent changes how helpful it is having them marked.
- For anyone wanting to help with keeping our content properly linked: Special:WhatLinksHere/Template:Broken section link lists the identified broken links. Indigo (talk) 11:11, 7 August 2016 (UTC)
- Interesting to see how many broken section links there are, and how long they went unnoticed... thanks for the upgrade! -- Alad (talk) 13:04, 7 August 2016 (UTC)
Subpages in the main namespace
Subpages in the main namespace are finally enabled , so e.g. GRUB/Tips and tricks is now a true subpage of GRUB. Among other benefits, there is now an automatic link on each subpage leading to every existing parent page, so manual phrases like "See GRUB for the main article." on top of subpages are now useless and should be removed. -- Lahwaacz (talk) 19:17, 23 July 2016 (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)
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)
Here, list requests for repetitive, systemic modifications to a series of existing articles to be performed by a wiki bot.