https://wiki.archlinux.org/api.php?action=feedcontributions&user=Badvok&feedformat=atomArchWiki - User contributions [en]2024-03-28T11:00:44ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=User_talk:Kynikos&diff=303775User talk:Kynikos2014-03-09T12:18:06Z<p>Badvok: </p>
<hr />
<div>Feel free to leave here your comments on my edits or anything else you want to talk about: I'll reply as soon as I can!<br />
<br />
==QuickVZ==<br />
I understand the reversion of my comment. Unfortunately the only proof I have is the email they sent out to all of their customers, myself included, and my subsequent conversation with them. Hopefully they'll update their official website soon. If not then I'll check on April 1st that they really have gone down and just remove them from the list then.<br />
==Xyne-related page edits after Powerpill, Bauerbill... discontinuation==<br />
See [[User_talk:Kynikos/Xyne-related pages|Xyne-related page edits after Powerpill, Bauerbill... discontinuation]].<br />
<br />
== Where should translations go? ==<br />
Hi! I'm wondering where the Archwiki team wants new translations to go? On the page [[ArchWiki Translation Team]] I get the feeling that translations should be placed under archlinux.org. At the same time there are national wikis as well, at different stages of development. In my case this is archlinux.se, which only contains a few articles, and is generally lacking links to the main Wiki from what I can see. What is the policy on where to put translations?<br />
:Hi and welcome! I'm glad to know that the Swedish website has come back to life :) Since MediaWiki is _not_ designed to handle internationalization (it requires resorting to workarounds like the suffix one we're using here) the ideal goal would be to move each language to its own separate wiki, for ease of maintenance. So, in your case, all Swedish articles should now be moved to wiki.archlinux.se and replaced with interwiki links on at least the English page, e.g. {{ic|<nowiki>[[sv:Huvudsida]]</nowiki>}}. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:23, 4 May 2012 (UTC)<br />
:Ah, I forgot to mention that if you want to add an interlanguage link to a protected English page, you can just ask on its talk page, and it will be added by one of us admins as soon as possible! -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:28, 4 May 2012 (UTC)<br />
<br />
On a secondary note - poorly developed regional wikis might work as a black hole for new users (turned off from arch due to lack of documentation) if they do not link to the main wiki for untranslated topics. Ideally they should cover the entire topic tree, and link to the anglish main wiki for untranslated articles. Granted, most potential new users that find a poor regional wiki probably continue searching and eventually find wiki.archlinux.org, but not necessarily all of them.<br />
:That's why we must exploit as much as we can the native tool that MediaWiki offers for keeping the various local wikis linked with each other: [http://meta.wikimedia.org/wiki/Help:Interwiki_linking#Interlanguage_links interlanguage links] (example above).<br />
:Until the Swedish wiki lacks important articles, at least its Main Page if not also other important articles should instruct Swedish users to search for missing content on the English wiki.<br />
:-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:23, 4 May 2012 (UTC)<br />
<br />
== Text shift in discussion answers ==<br />
I noticed that the discussion pages of the wiki, in order to indicate that the piece of text written actually answers a comment from a guy above, we are using colon to shift our answer. The problem appears on long discussions page (like the beginner guide, I'm coming from), when we answer to answers answering answers... <br />
<br />
I think it would be better to use a @name statement: this indicates we are answering directly to the guy whose name is written. And this avoid left space waste (especially on mobile phones, I couldn't even read the whole thread on mine yesterday, because of the so long shift).<br />
-- [[User:Wget|Wget]] ([[User talk:Wget|talk]]) 13:10, 5 August 2013 (UTC)<br />
<br />
:Well, about indentation we're just following Wikipedia's standards: [[Wikipedia:Help:Using_talk_pages#Indentation]], [[Wikipedia:Wikipedia:Indentation]].<br />
:About long discussions, outdenting can be used, [[Wikipedia:Wikipedia:Indentation#Outdenting]].<br />
:I admit that the @ method wouldn't be such a silly idea, it would work with short discussions, but it wouldn't allow branching out long discussions. On wide screens the "left space waste" is negligible, and on my phones (Android) the browser correctly manages to fit long discussions to the screen width, I don't understand why your phone can't do that ^^<br />
:-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 13:41, 6 August 2013 (UTC)<br />
<br />
== VirtualBox article rewrite ==<br />
<br />
Hi Kynikos!<br />
<br />
I'm currently rewriting the [[VirtualBox]] article and I've some question about the latter.<br />
<br />
In the ''Related'' section of that article, there is currently two different articles which are looking exactly the same regarding the subject they are dealing with:<br />
<br />
* [[Installing Arch Linux from VirtualBox]]: this one is really outdated and has been marked as is for ages. I think it could be removed. If you agree, could you request its deletion or do it by yourself (I think I haven't the required right to achieve that).<br />
<br />
* [[VirtualBox Arch Linux Guest On Physical Drive]]: this one is rather recent only ''initscripts' and ''grub legacy'' mode should be replaced by ''systemd'' and ''grub2''.<br />
<br />
Also I've found a page dedicated to [[systemd/Services|systemd services]] which are completely unrelated. I've found [[Systemd/Services#VirtualBox_virtual_machines|a service related to VirtualBox]], I think the later should be removed from that section and integrated to the main VirtualBox article (this is what I'll do).<br />
<br />
Also I wonder why even this [[systemd/Services]] section has ever been created. It has unrelated stuffs and each of them should be located to its related article. The problem is similar with [[Systemd#Running_DMs_under_systemd|sections of the systemd main article]].<br />
<br />
Regards. [[User:Wget|Wget]]<br />
<br />
:Hi Wget, thank you for your will to take on this task! After having a look at the current status of those articles, I agree that there are indeed many improvements that can be done:<br />
:*I confirm that [[Installing Arch Linux from VirtualBox]] and [[VirtualBox Arch Linux Guest On Physical Drive]] practically cover the same topic, however they do it for two different purposes: the former allows installing Arch Linux on a physical drive from VB, the latter allows booting an already existing "physical" system from VB; IMO the best thing to do in this case would be to merge the two articles while keeping intact and clear the distinction of the two scenarios (i.e., some rewording would be required on [[VirtualBox Arch Linux Guest On Physical Drive]]); maybe a new title could be created for the merged article, and the old ones should be redirected there, not deleted.<br />
:*About [[systemd/Services]] I think you're right, those units should be moved to the respective articles, if existing: if a list of services not provided upstream is required to keep track of the status of the respective packages, [[systemd/Services]] should be moved to the DeveloperWiki namespace and it should contain only a list of links to the articles where the services have been moved. It would be great if you could start a discussion on [[Talk:systemd/Services]] about this. Regarding the VB service you can safely move it to [[VirtualBox]].<br />
:*About [[Systemd#Running DMs under systemd]], both it and [[Systemd#Native configuration]] are already properly marked for merging/moving/deleting, they're just waiting for somebody to give them a bit of love ^^<br />
:-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 02:16, 30 September 2013 (UTC)<br />
:: Hi Kynikos,<br />
:: Thanks for your fast reply. I've just begun to make the adaptation, articles merge, we agreed on. But after spending some times to the article, I realized that the Wiki's style rules don't explicitly define how parts of commands that have to be adapted must be formated (or maybe I haven't found it yet ;-) ). An example is worth a thousand of words: <br />
:: {{bc|# dkms install vboxhost/'''<virtualbox-host-source version>''' -k '''<your custom kernel's version>'''/'''<your architecture>'''}}<br />
::In which format do I have to put <the strings that must be replaced/adapted>. I don't even know if we have to surround them with angle brackets < >.<br />
::[[User:Wget|Wget]] ([[User talk:Wget|talk]]) 22:00, 30 September 2013 (UTC)<br />
:::[[Help:Style/Formatting and Punctuation]] will give you all the answers you need, in particular [[Help:Style/Formatting and Punctuation#Pseudo-variables in file/command line contents]] deals with your example.<br />
:::Sorry if I can't give you feedback for your edits now, but I'm incredibly busy, I'll get there in the next days! Meanwhile if you have more questions don't hesitate to ask :)<br />
:::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 14:54, 1 October 2013 (UTC)<br />
Hi Kynikos,<br />
Just to bring to you some updates. I'm still on this rewrite. It is longer that expected as I need to recheck all assumptions written in the documentation (and I needed to wait for the 4.3 release). I'm gonna make some subpages, as proposed in the discussion page of VirtualBox Extras.<br />
Do you know if some warning templates are available to indicate that the page is currently being rewritten? -- [[User:wget|wget]] ([[User talk:wget|talk]]) 19:59, 6 November 2013 (UTC)<br />
<br />
:Hey wget, thanks for the update, I think just using [[Template:Stub]] with a proper description will serve the purpose. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 08:50, 7 November 2013 (UTC)<br />
<br />
Kynikos, The rewrite makes some progress, but I'm still spending a huge time at verification and tests. I put the content from VirtualBox Extras to the main VirtualBox article. Could you proceed to deletion of [[VirtualBox_Extras]]? Thanks! (The main VirtualBox article will be clearer when I will have finished the rewrite and a dedicated subpage might be unneeded) -- [[User:wget|wget]] ([[User talk:wget|talk]]) 20:47, 12 November 2013 (UTC)<br />
<br />
:Done, it's always preferable to redirect instead of deleting when possible :) I'm trying to follow your changes, I think you're doing a great job, keep up the good work!! -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 08:48, 13 November 2013 (UTC)<br />
<br />
Hi Kynikos, regarding the Virtualbox article rewrite, I wonder if you could remove this article [[Installing_Arch_Linux_from_VirtualBox]] since it does not contain any relevant content (it is only speaking about creating an Arch Linux VM stricto sensu, without adding much information. Install steps for Arch Linux guests are already covered in the main article. Can we remove that article and, if needed, redirect it to [[VirtualBox]]. Thanks. -- [[User:wget|wget]] ([[User talk:wget|talk]]) 22:35, 30 December 2013 (UTC)<br />
<br />
:What about my observation above about it and [[VirtualBox Arch Linux Guest On Physical Drive]]? (02:16, 30 September 2013 (UTC), first bullet point) I still think [[Installing_Arch_Linux_from_VirtualBox]] has a goal that's not covered in [[VirtualBox]]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 12:02, 31 December 2013 (UTC)<br />
<br />
== Integrating Google searches into ArchWiki ==<br />
<br />
Re-reading the discussion on my talk page ([[User_talk:Jstjohn#Unused_redirects]]) made me think that we should try improving the search functionality of the ArchWiki. Native MediaWiki search is really awful in my experience, and I'm guessing many others feel the same way.<br />
<br />
The easiest way to improve it would be to integrate Google search directly into ArchWiki. A brief search on Google led me to [https://www.mediawiki.org/wiki/Extension:GoogleCustomWikiSearch] and [http://www.mediawiki.org/wiki/Extension:Google], which are two ways to integrate Google search into MediaWiki. Even if those two aren't ideal solutions&mdash;I haven't looked at them in-depth&mdash;there are likely to be several other ways of integrating Google search into MediaWiki. So consider this a very nascent proposal for extending/improving search quality on ArchWiki without necessarily proposing a certain implementation.<br />
<br />
I don't think that we should completely replace native MediaWiki search (yet?); however, integrated Google search would be a very useful alternative search feature that everyone can use.<br />
<br />
-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 00:15, 5 December 2013 (UTC)<br />
<br />
:I don't have a particular preference for one search engine or the other, however extensions can only be installed by the Devs, who have access to the [https://projects.archlinux.org/vhosts/wiki.archlinux.org.git/ repo], so a bug report should be opened for these things. In particular [[User:Pierre]] is the one who takes care of the wiki, and '''*IIRC*''' he tends to be against installing new extensions. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 09:18, 5 December 2013 (UTC)<br />
<br />
== Crazy idea about interlanguage links ==<br />
<br />
If [https://www.mediawiki.org/wiki/Extension:ParserFunctions ParserFunctions] extension was installed on ArchWiki, it would be possible to implement an (almost) fully automatic solution to the problem of interlanguage links, similar to mediawiki.org: [https://www.mediawiki.org/wiki/Template:Languages], [https://www.mediawiki.org/wiki/Template:Languages/Lang]. I think it would be possible to adjust it to the layout currently used on ArchWiki, so no mass renaming would be required.<br />
<br />
Intended layout is that we would have single central template to be used on all pages, similar to [[Template:i18n]], that would include the {{ic|<nowiki>[[subtag:Page Name]]</nowiki>}} links for all languages. There would also be checking if the localized page exists (using the {{ic|#ifexist}} function from ParserFunctions) to avoid links to non-existent pages.<br />
<br />
Manual intervention would still be required in several cases:<br />
* the localized article is on external wiki - the link would have to be added manually<br />
* the localized article has different base name than the English page ([[Network configuration]] vs. [[Configuring Network (Italiano)]]) - best solution would be moving the localized pages to match the English page (this would be good anyway)<br />
* there are possible problems with redirects, I did not think of it yet<br />
<br />
Disadvantages:<br />
* slower rendering of pages, higher server load ({{ic|#ifexist}} is considered an "expensive parser function" [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#ifexist_limits])<br />
<br />
Anyway, what do you think of it? Is it a viable solution?<br />
<br />
-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:53, 8 December 2013 (UTC)<br />
<br />
:The short answer would be the same I've given to Jstjohn in [[#Integrating Google searches into ArchWiki]], however even if we could easily install extensions, maybe we should consider [[Help_talk:I18n#MediaWiki_translation_extension]] before this idea. I think you've never seen our [[Template:i18n]] on this wiki, which was practically the same except for the #ifexist check. It was in use before June 2012 and was deprecated by [https://wiki.archlinux.org/index.php?title=Help_talk:I18n&oldid=209375#.22Dummy.22_interlanguage_links_and_deprecation_of_Template:i18n]: that discussion is full of arguments against its reintegration :D -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 04:44, 9 December 2013 (UTC)<br />
<br />
::I like automatic solutions, I'm sure there are plenty of extensions that make this possible. The current solution is by no means automatic, even considering the Wiki Monkey bot plugin. We should at least have a solution to automatically check all pages on the wiki (or at least some specific namespace). The current solution relies on lists like [[Special:MostLinkedPages]], which tend to overlap, and also in my opinion the plugin does not cover all cases. I already have several ideas on how to improve the algorithm, it's just the matter of putting it "on paper" - I think I'll open an issue about this on github... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:54, 9 December 2013 (UTC)<br />
<br />
:::I have written a quite long post about redesigning the bot algorithm, but unfortunately it seems that I can't post it on github because markdown apparently supports only two levels of bullet lists :( -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:41, 10 December 2013 (UTC)<br />
<br />
::::No worries, we can easily discuss it here, after all we're doing it for this wiki's sake, it's nothing extraneous. Maybe you (or I) can create a bug report with a link to this discussion, just as a reminder for myself. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 14:35, 10 December 2013 (UTC)<br />
<br />
:::::Alright, I've started the discussion in [[Talk:Wiki_Monkey#Improvements_to_the_interlanguage_syncing_algorithm]] - feels like the right place for it... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 20:02, 10 December 2013 (UTC)<br />
<br />
== Anomaly in list of categories ==<br />
<br />
Hi,<br />
<br />
in [https://wiki.archlinux.org/index.php?title=Special:MostLinkedCategories&limit=500&offset=1500] there is an anomaly in the list, which prevents Wiki Monkey to update filter preview:<br />
<br />
1731. Invalid title with namespace "Category" and text ""<br />
<br />
I can't think of any reasonable explanation since {{ic|<nowiki>[[:Category:]]</nowiki>}} does not work.<br />
<br />
Another thing, is there a reason why deleted pages are in the list of most linked-to pages even though they are not linked or transcluded?<br />
<br />
-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 22:21, 24 December 2013 (UTC)<br />
<br />
:Weird, Wiki Monkey expects to find a link in those list items, so it was just crashing there. From the next release it won't blindly assume there's a link anymore :)<br />
:Maybe a category with an empty title was created with a version of MediaWiki that was still allowing it? It's unlikely that they put it there by default for a mechanism that kind of prevents its creation, because other wikis don't have it, e.g. [https://wiki.archlinux.de/index.php?title=Spezial:Meistbenutzte_Kategorien&limit=500&offset=0].<br />
:About the second question, I think you're talking about deleted Categories, not simple pages, as no pages with 0 backlinks appear in [[Special:MostLinkedPages]]. Assuming you're talking about [[Special:MostLinkedCategories]] then, most (if not all) of the red links that you see there are former "wanted" (not "deleted") categories, which are likely cached in a special database table for which deletion of entries has never been implemented perhaps for the danger of breaking something else? MostLinkedCategories would then query that table without filtering the results with 0 backlinks: I've got no idea why, there could even be no reason at all and it just happens to have been implemented like that, waiting for somebody to submit a patch ;)<br />
:-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 15:52, 25 December 2013 (UTC)<br />
<br />
::I was talking exclusively about categories. Thanks for pointing out that [[Special:MostLinkedPages]] (and also [[Special:MostLinkedTemplates]]) are OK - this is really weird, so I've submitted a [https://bugzilla.wikimedia.org/show_bug.cgi?id=58967 bug report].<br />
::I also found [https://gerrit.wikimedia.org/r/#/c/17668/ this commit], which is probably behind the error description produced in the list.<br />
::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 22:55, 25 December 2013 (UTC)<br />
<br />
:::Ah well, good job, I've contributed to the report. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 02:36, 26 December 2013 (UTC)<br />
<br />
==<s> Systemd / Transmission </s>==<br />
<br />
In this diff [[https://wiki.archlinux.org/index.php?title=Transmission&diff=299997&oldid=299990]] (/usr/lib/systemd/system/transmission.service in transmission-cli 2.82-1 seems to invoke "/usr/bin/transmission-daemon -f --log-error"), systemd does invoke "transmission-daemon" as usual, but the user has to use "transmission" when invoking systemd/systemctl.<br />
[[User:Idomeneo1|Idomeneo1]] ([[User talk:Idomeneo1|talk]]) 18:22, 23 February 2014 (UTC)<br />
<br />
:Thank you for clarifying, "transmission" is not "invoked" by systemd then, it's just the name of the service, as I've further remarked with [https://wiki.archlinux.org/index.php?title=Transmission&diff=301029&oldid=300011], I think the article is clear enough now about that, if somebody tries to start a "transmission-daemon" service they'll just get a simple error anyway, and they'll read the article again more accurately ;) -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 03:32, 24 February 2014 (UTC)<br />
<br />
::The problem with this is people are not going to know that this service is not called by what they would expect it to be called. In fact the only place where "transmission" occurs without a modifier is the config folder - for the GUI, not even for the daemon. Daemon names are generally marked in some way, as the normal ''transmission-daemon'' command is, and users are not going to come up with the idea on their own, that calling "transmission" on systemd/systemctl doesn't following any usual pattern.<br />
::"they'll read the article again more accurately" - Now the article doesn't say this at all, and an error message is not going to give them any idea what the problem is. <br />
::[[User:Idomeneo1|Idomeneo1]] ([[User talk:Idomeneo1|talk]]) 14:41, 24 February 2014 (UTC)<br />
<br />
:::I do not know how there is confusion over this. The article explicitly states that "transmission" is the name of the systemd unit file. See below (emphasis added by me):<br />
:::{{bc|As a ''{{ic|transmission}}'' user by starting the ''{{ic|transmission}}'' service [[systemd#Using units|using systemd]].}}<br />
:::-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 06:56, 25 February 2014 (UTC)<br />
<br />
::::The problem is that people who consult the wiki do need this spelled out, because if they think they're starting a ''transmission-daemon'', as systemctl itself does, it becomes counterintuitive to suddenly be "starting" ''transmission''. If the wiki administrators have been rehashing this stuff ad nauseam, the people who actually consult the wiki do come from other distros and need these things spelled out.<br />
::::[[User:Idomeneo1|Idomeneo1]] ([[User talk:Idomeneo1|talk]]) 14:54, 25 February 2014 (UTC)<br />
<br />
:::::Users that are confused about this need to read about systemd to understand what a service/unit file is and does. There is a significant difference between running a program and starting a systemd service. If the reader is familiar with systemd and what a service/unit file is, the transmission-daemon/transmission thing is not all that counter-intuitive.<br />
:::::I do not know what you mean by this:<br />
::::::{{bc|If the wiki administrators have been rehashing this stuff ad nauseam}}<br />
:::::-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 01:54, 26 February 2014 (UTC)<br />
<br />
:::::::There is a difference between the information that administrators are exposed to every day, and what most users come here with, who consult the Wiki.<br />
:::::::[[User:Idomeneo1|Idomeneo1]] ([[User talk:Idomeneo1|talk]]) 02:44, 26 February 2014 (UTC)<br />
<br />
::::::@Idomeneo1: I'd like to know if you've read of somebody being actually confused by that, or if you're just guessing. Because to me the name of the service is already "spelled out", unless we want to start trying to prevent users from misreading words everywhere in the wiki by adding a note whenever there are two "things" with similar names.<br />
::::::I also don't get how the fact of coming from another distro could make a person more likely to misread a word, as if only Arch users had the ability to correctly read names of systemd services.<br />
::::::Anyway, I didn't want to get so far for such a little detail, but at this stage your next viable option is to start a poll in [[Talk:Transmission]], otherwise we'll never settle this.<br />
::::::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 02:01, 26 February 2014 (UTC)<br />
:::::::It ''did'' confuse me, in fact. Moreover, at the time the Transmission article was such mess, I was consulting Google, which also threw ''transmission-da'' in the mix. Prior to that I had only used the GUI version, which requires minimal configuration. I don't think my experience was exceptional, but of course it would be a simple matter to dismiss someone who would be confused by an confusing article as a noob.<br />
:::::::Ntpd, wicd, dhcpcd, xdm, gdm all use "expected" names for systemctl. Netctl and dropbox discuss their differences in their articles.<br />
:::::::It ''is'' those little, easily-overlooked details that make things go or not go, that need to be pointed out.<br />
:::::::[[User:Idomeneo1|Idomeneo1]] ([[User talk:Idomeneo1|talk]]) 02:44, 26 February 2014 (UTC)<br />
<br />
::::::::Well, if that's so confusing for you I guess I can't hold you back anymore, just please don't re-add the previous note, which was more confusing than the issue it was trying to explain; be as clear and concise as possible. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 09:40, 27 February 2014 (UTC)<br />
<br />
:::::::::Ok, I see the note is back (without a Note template), together with all the systemctl examples which we had already found being against [[Help:Style#Daemon operations]], however I'm tired of fixing that, I'm closing this discussion. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 13:13, 28 February 2014 (UTC)<br />
<br />
::::::::::It sounded like the big purple template was what you objected too. Also the systemctl information in the article was wrong - it is not restricted to user "transmission" usage. The idea was to explain what the different commands actually do.<br />
::::::::::[[User:Idomeneo1|Idomeneo1]] ([[User talk:Idomeneo1|talk]]) 13:56, 28 February 2014 (UTC)<br />
<br />
:::::::::::I wasn't really objecting the "big purple template" itself, just what was inside, however after all if the note has to be there, it's better to keep it without the Note template.<br />
:::::::::::About the systemctl commands I'm tired to fix, I was referring to [[Help:Style#Daemon operations]], according to which I should remove them again.<br />
:::::::::::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 01:17, 1 March 2014 (UTC)<br />
::::::::::::But if they work differently, i.e. having to specify the user or not, this needs to be pointed out in some way. With daemons, command-line commands and systemctl calls can often be used interchangeably, and where they don't follow the same rules, this needs to be said - this was evidenced in the article itself, which had the systemctl usage wrong.<br />
::::::::::::[[User:Idomeneo1|Idomeneo1]] ([[User talk:Idomeneo1|talk]]) 01:33, 1 March 2014 (UTC)<br />
<br />
:::::::::::::I don't think we're talking about the same thing: what conflicts with [[Help:Style#Daemon operations]] (and I invite you to actually follow the link and read what's written there) is the systemctl example itself, ''not'' the mention of the service. However I've taken the time to fix the article once again, I hope it makes what I'm saying clearer for you. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 02:29, 1 March 2014 (UTC)</div>Badvokhttps://wiki.archlinux.org/index.php?title=Arch_Linux_on_a_VPS&diff=303502Arch Linux on a VPS2014-03-07T17:28:28Z<p>Badvok: /* Providers that offer Arch Linux */</p>
<hr />
<div>[[Category:Getting and installing Arch]]<br />
[[Category:Virtualization]]<br />
{{Related articles start}}<br />
{{Related|Comprehensive Server Guide}}<br />
{{Related articles end}}<br />
From [[Wikipedia:Virtual private server]]:<br />
<br />
:''Virtual private server (VPS) is a term used by Internet hosting services to refer to a virtual machine. The term is used for emphasizing that the virtual machine, although running in software on the same physical computer as other customers' virtual machines, is in many respects functionally equivalent to a separate physical computer, is dedicated to the individual customer's needs, has the privacy of a separate physical computer, and can be configured to run server software.''<br />
<br />
This article discusses the use of Arch Linux on Virtual Private Servers, and includes some fixes and installation instructions specific to VPSes.<br />
<br />
{{Warning|1=[https://bbs.archlinux.org/viewtopic.php?id=176171 It appears] that systemd does not support Linux 2.8.32 since systemd-205. Since many container-based virtualization environments rely on older kernels (the latest OpenVZ runs on a modified RHEL6-2.8.32 for example), it may be impossible to keep an Arch Linux install up to date. Most of the instructions regarding OpenVZ on this page were written for systemd-204 and earlier.}}<br />
<br />
==Providers that offer Arch Linux==<br />
<br />
{{Warning|We cannot vouch for the honesty or quality of any provider. Please conduct due diligence before ordering.}}<br />
{{Note|This list is for providers with a convenient Arch Linux image. Using Arch on other providers is probably possible, but would require loading custom ISOs or disk images or [[Installation guide|installing under chroot]].}}<br />
<br />
{| class="wikitable"<br />
! Provider !! Arch Release !! Virtualization !! Locations !! Notes<br />
|-<br />
| [http://123systems.net 123 Systems] || 2010.05.xx || OpenVZ || Dallas, US-TX || Arch available as a selection upon reinstall. Very old (2.6.18-308) kernel - See [[Virtual_Private_Server#OpenVZ:_kernel_too_old_for_glibc|OpenVZ troubleshooting]]. Limited information available before purchase. Cannot verify Arch Linux version without purchase.<br />
|-<br />
| [http://ausweb.com.au AUSWEB] || Latest Only (clarify?) || VMware ESXi || Sydney, AU || Latest ISO (clarify?) of Arch Available. Enterprise Service. <br />
|-<br />
| [https://www.affinity.net.nz affinity.net.nz] || 2013.08.01 || KVM || Auckland, New Zealand (NZ) || IRC channel is #affinity on ircs.kiwicon.org<br />
|-<br />
| [http://afterburst.com/ Afterburst] || 2012.12.01 || OpenVZ || Miami, US-FL; Nuremberg, DE || Formerly FanaticalVPS, kernel version depends on what node your VPS is on, the ones in Miami are fine (2.6.32-042stab072.10) but some of the ones in Germany require a [[Virtual_Private_Server#OpenVZ:_kernel_too_old_for_glibc|custom glibc]].<br />
|-<br />
| [http://www.buyvm.net/ BuyVM] || 2013.07.01 || KVM || LA, Buffalo NY || Must chose a different OS at sign up. Once accessible, choose to mount the latest Arch ISO and reboot to install manually. <br />
|-<br />
| [https://digitalocean.com DigitalOcean] || 2013.05.xx || KVM || New York, US-NY; San Francisco, US-CA; Amsterdam, AN || Uses a custom kernel. You can run your own kernel with a [https://github.com/helirexi/LEMP-VPS-DigitalOcean/blob/master/README.md kexec hack]. Every server uses SSDs by default.<br />
|-<br />
| [http://en.edis.at/ Edis] || [http://www.edis.at/en/support-and-service/faq/server-faq/which-distributions-are-available-with-edis-kvm-vps-plans/ 2013.03.01] || vServer, KVM, OpenVZ || [http://www.edis.at/en/server/kvm-vps/austria/ Multiple international locations]. || Also offer dedicated server options as well as an "off-shore" location at the Isle of Man (IM).<br />
|-<br />
| [https://www.directvps.nl/ DirectVPS] || 2014.01.xx || OpenVZ || Amsterdam, AN; Rotterdam, AN || Dutch language site. Version verifyable by clicking through https://www.directvps.nl/try-1.plp?p=31<br />
|-<br />
| [https://www.gandi.net/hosting/ Gandi] || 2013.10.27 || Xen || Paris, FR; Baltimore, MD, US; Bissen, LU || Very granular scaling of system resources (e.g. RAM, disk space); IPv6-only option available; you can supply your own install image, version based on keyring package version ||<br />
|-<br />
| [https://www.gigatux.com/virtual.php GigaTux] || [https://www.gigatux.com/distro/ 2013.06.01] || Xen || Chicago, US-IL; Frankfurt, DE; London, GB; San Jose, US-CA ||<br />
|-<br />
| [http://www.vr.org/ Host Virtual] || [http://www.vr.org/os/linux-vps/archlinux-vps 2011.08.19] || KVM || [http://www.vr.org/cloud-locations/ Multiple International Locations] || Appears to use KVM virtualization. Site lists "Xen based virtualization" and [http://www.vr.org/features/ features] lists ability to install from ISO.<br />
|-<br />
| [https://hostigation.com/ Hostigation] || [https://hostigation.com/wiki/index.php?title=KVM:Install 2010.05 i686] || OpenVZ, KVM || Charlotte, US-NC; Los Angeles, US-CA || You can [[Migrating Between Architectures Without Reinstalling|migrate to x86_64]].<br />
|-<br />
| [http://www.intovps.com IntoVPS] || 2012.09.xx || OpenVZ || Amsterdam, NA; Bucharest, RO; Dallas, US-TX; Fremont, US-CA; London, GB || Blog has not been updated since September, 2012 which included the Arch Linux update.<br />
|-<br />
| [https://leapswitch.com Leapswitch Networks] || [2013.10.xx] || OpenVZ/KVM || USA, India, Portugal, Spain, Ukraine, Germany || ArchLinux currently available in Control Panel for reinstall, not on order form. <br />
|-<br />
| [https://www.linode.com Linode.com] || [https://www.linode.com/faq.cfm 2013.06.xx] || OpenVZ|| [https://www.linode.com/speedtest/ Tokyo, JP; Multiple US; London, GB] || To run a custom kernel, install {{AUR|linux-linode}}. ({{pkg|linux}} will break on a 32-bit Linode.)<br />
|-<br />
| [http://lylix.net/home Lylix] || [https://customer.lylix.net/announcements/21/New-64-bit-Linux-Distributions-and-32-bit-Ubuntu-1304.html 2013.xx.xx] || Unlisted || Unlisted || Core2Duo and Woodcrest based processors. <br />
|-<br />
| [http://www.nodedeploy.com Node Deploy] || xxxx.xx.xx || OpenVZ, KVM || Germany (DE); Los Angeles, US-CA; Atlanta, US-GA; Phoenix, US-AZ || "At NodeDeploy we support virtually every linux distribution." Arch Linux is listed under their Operating Systems. No version information.<br />
|-<br />
| [http://netcup.de Netcup] || 2012.11.xx || KVM || Germany (DE)|| German language site. <br />
|-<br />
| [http://onepoundwebhosting.co.uk OnePoundWebHosting] || 2013.05.xx || Xen PV, Xen HVM || United Kingdom (UK) || They are a registrar too. Unable to verify server locations.<br />
|-<br />
| [https://www.proplay.biz/ proPlay.de] || 2012.12.xx || OpenVZ, KVM || Germany (DE) || German language site.<br />
|-<br />
| [https://www.quickvz.com QuickVZ] || 2013.10 || OpenVZ, Xen || Amsterdam, Netherlands (NL); Stockholm, Sweden (SE) || Provide hardened Arch Linux images along with Enterprise services (e,g. VPN, Virtual Private LAN Service (VPLS) and Virtual Routers. '''This company is closing down from April 1st, 2014'''<br />
|-<br />
| [http://www.rackspace.com/cloud/cloud_hosting_products/servers/ Rackspace Cloud] || 2013.6 || Xen || [https://www.rackspace.com/whyrackspace/network/datacenters/ Multiple international locations] || Billed per hour. Use their "next gen" VPSes (using the mycloud.rackspace.com panel); the Arch image on the first gen Rackspace VPSes is out of date.<br />
|-<br />
| [http://www.ramhost.us RamHost.us] || [http://www.ramhost.us/?page=news 2013.05.01] || OpenVZ, KVM || Los Angeles, US-CA; Great Britain (GB); Atlanta, US-GA; Germany (DE) || You can request a newer ISO on RamHost's IRC network.<br />
|-<br />
| [http://www.ramnode.com RamNode] || [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=48 2013.07.01] || [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=39 SSD and SSD Cached:] [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=52 OpenVZ, KVM] || [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=18 Seattle, WA USA, Atlanta, GA USA] || [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=66 You can request Host/CPU passthrough with KVM service.] [http://www.ramnode.com/about.php Customer service has been prompt and professional.] [https://twitter.com/search?q=ramnode%20code&src=typd Regular discount codes can be found (15-35% off).] [http://www.ramnode.com/index.php Modern hardware.] [https://clientarea.ramnode.com/cart.php?carttpl=svz Competitive pricing (before discounts).]<br />
|-<br />
| [http://www.tilaa.nl/ Tilaa] || 2013.06.01 || [https://www.tilaa.com/pages/vps/technology KVM] || Amsterdam, NL || English or Dutch language site.<br />
|-<br />
| [https://www.transip.eu/ TransIP] || [https://www.transip.eu/vps/vps-os/ 2013.05.01] || [https://www.transip.eu/vps/vps-technology/ KVM] || Amsterdam, NL || English language site. Registrar.<br />
|-<br />
| [http://www.xenvz.co.uk/ XenVZ] || 2009.12.07 || OpenVZ, Xen || United Kingdom (UK), United States (US) || [http://www.xenvz.co.uk/faq.php#use2 Hardware]<br />
|-<br />
| [http://www.virpus.com/ Virpus] || [http://virpus.com/tour/ 2013.05.xx] || OpenVZ, Xen || Kansas City, US-KS; Los Angeles, US-CA ||<br />
|-<br />
| [http://www.vmline.pl/ Vmline] || 2013.09.01 || KVM, OpenVZ || Kraków, PL || [http://www.s-net.pl/en/ S-Net] reseller. Full virtualization. Polish language site.<br />
|-<br />
| [https://vpsbg.eu/ VPSBG.eu] || 2013.10 || OpenVZ || [https://vpsbg.eu/en/index.php?page=vps-datacenter Sofia, Bulgaria] || Offshore VPS in Bulgaria - anonymous registrations and Bitcoin are accepted.<br />
|-<br />
| [https://vps6.net/ VPS6.NET] || 2013.01.xx || OpenVZ, Xen, HVM-ISO || [http://vps6.net/network/ Multiple US]; Frankfurt, DE; Bucharest, RO; Istanbul, TR || Registrar.<br />
|-<br />
|}<br />
<br />
==Installation==<br />
<br />
===KVM===<br />
{{Expansion|Are there instructions specific to VPSes?}}<br />
See [[QEMU#Preparing an (Arch) Linux guest]].<br />
<br />
===OpenVZ===<br />
<br />
====Updating a 2010.05 installation image====<br />
These instructions assume you have a 2010.05 image from your VPS provider and you would like to get it updated. The biggest work involves preparing {{ic|/lib}} for the symlink upgrade ({{pkg|glibc}} 2.16, and later {{pkg|filesystem}} 2013.01).<br />
<br />
{{Warning|If you are on a older kernel than 2.6.32, please refer [[Virtual_Private_Server#OpenVZ:_kernel_too_old_for_glibc|further down the page]] to get the ''glibc-vps'' repository working (just add the repository and you can follow these steps).}}<br />
<br />
To start, grab the latest BusyBox from http://busybox.net/downloads/binaries/latest/. This allows you to force glibc (losing {{ic|/lib}} temporarily) without losing your OS (BusyBox comes with its own GNU tools which are statically linked).<br />
# wget http://busybox.net/downloads/binaries/latest/busybox-i686<br />
# chmod +x busybox-i686<br />
<br />
First, you can get a list of packages that own files in {{ic|/lib}} with the following command:<br />
{{bc|<nowiki><br />
$ pacman -Qo /lib/* | cut -d' ' -f 5 | egrep -v 'glibc' | uniq | xargs<br />
</nowiki>}}<br />
<br />
For the current 2010.05 that comes from ibiru's page, these are the packages that were required to be removed for me:<br />
<br />
{{bc|pacman -S acl attr util-linux-ng bzip2 libcap e2fsprogs libgcrypt libgpg-error udev readline ncurses pam pcre popt procps readline shadow e2fsprogs sysfsutils udev util-linux-ng sysvinit coreutils}}<br />
<br />
You may have to remove {{ic|/lib/udev/devices/loop0}} (a simple {{ic|rm}} works).<br />
<br />
After the upgrade finishes, you must remove any extra empty directories in {{ic|/lib}} ({{ic|/lib/modules}} is the common offender):<br />
# rm -rf /lib/modules<br />
<br />
Install {{pkg|tzdata}} to fix some dependencies, and remove {{ic|/etc/profile.d/locale.sh}}:<br />
# pacman -S tzdata<br />
# rm /etc/profile.d/locale.sh<br />
<br />
Remove {{ic|/var/run}} (you should have nothing running that matters):<br />
# rm -rf /var/run<br />
<br />
Force glibc, which will pull in the latest filesystem package, but will BREAK everything (other than BusyBox):<br />
# pacman -S --force glibc}}<br />
<br />
Now, you will have a broken system, so symlink {{ic|/usr/lib}} to {{ic|/lib}} with BusyBox's ln program:<br />
# ./busybox-i686 ln -s /usr/lib /lib<br />
<br />
And you should have a fully functional system where you can now update pacman.<br />
# pacman -S pacman; pacman-key --init; pacman-key --populate archlinux; pacman-db-upgrade; pacman -Syy<br />
<br />
Now, update initscripts to get the {{pkg|iproute2}} package:<br />
# pacman -S initscripts<br />
<br />
Install the {{pkg|makedev}} package:<br />
{{bc|pacman -S makedev}}<br />
<br />
Add the following to your {{ic|/etc/rc.local}}:<br />
/usr/sbin/MAKEDEV tty<br />
/usr/sbin/MAKEDEV pty<br />
<br />
Comment the following lines in {{ic|/etc/inittab}}:<br />
#c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux<br />
#c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux<br />
#c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux<br />
#c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux<br />
#c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux<br />
#c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux<br />
<br />
Finally, you should be able to upgrade the whole system:<br />
# pacman -Syu<br />
<br />
You may run into some issues with krb5 and heimdal, as krb5 no longer provides+conflicts+replaces heimdal (https://projects.archlinux.org/svntogit/packages.git/commit/trunk/PKGBUILD?h=packages/krb5&id=f5e6d77fd14ced15ebf5b6a78a7c76e0db0625f7). The old openssh depends on heimdal (and the new openssh depends on krb5), so force install krb5, then upgrade openssh, then remove heimdal and reinstall krb5.<br />
# pacman -S --force krb5<br />
# pacman -S openssh openssl<br />
# pacman -R heimdal<br />
# pacman -S krb5<br />
<br />
Fix {{pkg|syslog-ng}}. Set the src to {{ic|unix-dgram("/dev/log")}} and add {{ic|--no-caps}} to both check and run args in {{ic|/etc/conf.d/syslog-ng}}.<br />
<br />
Make sure your {{ic|/etc/rc.conf}} is not messed up with broken network definitions, or else be sure serial access works on your VPS before you reboot.<br />
<br />
====Moving your VPS from network configuration in rc.conf to netcfg (tested with OpenVZ)====<br />
<br />
1) Install netcfg<br />
<br />
{{bc|pacman -S netcfg}}<br />
<br />
2) Create a netcfg configuration file {{ic|/etc/network.d/venet}}<br />
<br />
{{bc|1=CONNECTION='ethernet'<br />
DESCRIPTION='VPS venet connection'<br />
INTERFACE='venet0'<br />
IP='static'<br />
IPCFG=(<br />
#default<br />
'addr add 127.0.0.1/32 broadcast 0.0.0.0 dev venet0'<br />
#IPv4 address<br />
'addr add xxx.xxx.xxx.xxx/32 broadcast 0.0.0.0 dev venet0'<br />
#IPv4 route<br />
'route add default dev venet0'<br />
#IPv6 address<br />
'addr add xxxx:xx:xx::x/128 dev venet0'<br />
#IPv6 route<br />
'-6 route add default dev venet0'<br />
)<br />
DNS=('xxx.xxx.xxx.xxx' 'xxx.xxx.xxx.xxx')}}<br />
<br />
3) Edit your netcfg main conf file {{ic|/etc/conf.d/netcfg}}<br />
<br />
{{bc|1=NETWORKS=(venet)<br />
WIRED_INTERFACE="venet0"}}<br />
<br />
4) Try your new setup<br />
<br />
{{bc|rc.d stop network && ip addr flush venet0 && netcfg venet}}<br />
<br />
Your VPS should still be connected and have its IP addresses set correctly. (Check with {{ic|ip a}})<br />
<br />
DO NOT proceed to next step if this isn't the case.<br />
<br />
5) Make your new setup survive reboots<br />
<br />
In the {{ic|DAEMONS}} array in {{ic|/etc/rc.conf}}, replace {{ic|network}} with {{ic|net-profiles}}.<br />
<br />
Remove all networking information that is in {{ic|/etc/rc.conf}}.<br />
{{bc|reboot}}<br />
<br />
====Moving your VPS from initscripts to systemd====<br />
<br />
{{Warning|This has been known to work with OpenVZ on the 2.6.32 kernel, but systemd may not work on older kernels.}}<br />
<br />
This is very similar to a regular arch system, except you probably don't have access to your kernel line.<br />
<br />
1) Move from network in rc.conf to netcfg (see above).<br />
<br />
2) Install systemd<br />
<br />
{{bc|pacman -S systemd}}<br />
<br />
2 bonus for OpenVZ) Remove kernel core dump pattern since this is blocked by OpenVZ and causes errors<br />
<br />
Edit {{ic|/usr/lib/sysctl.d/coredump.conf}}, comment out the following line:<br />
{{bc|#kernel.core_pattern&#61;&#124;/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e}}<br />
<br />
3) Move all configuration from {{ic|/etc/rc.conf}} (except the {{ic|DAEMONS}} array) to its appropriate location.<br />
<br />
See [https://wiki.archlinux.org/index.php/Systemd#Native_configuration Native configuration] and [https://wiki.archlinux.org/index.php/Rc.conf rc.conf] for details.<br />
<br />
Now your {{ic|/etc/rc.conf}} should only contain the {{ic|DAEMONS}} array.<br />
<br />
4) Install systemd-sysvcompat<br />
<br />
{{bc|pacman -S systemd-sysvcompat}}<br />
<br />
It will ask to replace sysvinit, say yes.<br />
<br />
{{bc|reboot}}<br />
<br />
5) Move daemons from the {{ic|DAEMONS}} array in {{ic|/etc/rc.conf}} to {{ic|systemd}}<br />
<br />
See the [https://wiki.archlinux.org/index.php/Systemd#Moving_away_from_the_DAEMONS_array guide] and the [https://wiki.archlinux.org/index.php/Daemons_List daemons list].<br />
<br />
If your {{ic|DAEMONS}} array is now empty, skip next step.<br />
<br />
6) Moving rc.d daemons with no systemd support, example: {{ic|vzquota}}<br />
<br />
Create a custom systemd service file for vzquota: {{ic|/etc/systemd/system/newvzquota.service}}:<br />
{{bc|1=[Unit]<br />
Description=Setup vzquota on VPS<br />
ConditionFileIsExecutable=/etc/rc.d/vzquota<br />
<br />
[Service]<br />
Type=oneshot<br />
ExecStart=/etc/rc.d/vzquota start<br />
ExecStop=/etc/rc.d/vzquota stop<br />
TimeoutSec=0<br />
StandardInput=tty<br />
RemainAfterExit=yes<br />
<br />
[Install]<br />
WantedBy=multi-user.target}}<br />
<br />
{{Note|It is recommended to choose a .service file name that is different from the name of the daemon, because systemd might try to call the LEGACY scripts with the old name.}}<br />
<br />
Enable this service:<br />
{{bc|systemctl enable newvzquota.service}}<br />
<br />
Remove {{ic|vzquota}} from the {{ic|DAEMONS}} array in {{ic|/etc/rc.conf}}<br />
<br />
Repeat this step to remove all daemons from {{ic|/etc/rc.conf}}.<br />
<br />
7) Removing {{ic|/etc/rc.local}} and {{ic|/etc/rc.local.shutdown}}<br />
<br />
Write [https://wiki.archlinux.org/index.php/Systemd#Writing_custom_.service_files custom .service files] to replace functionality in {{ic|/etc/rc.local}} and {{ic|/etc/rc.local.shutdown}}. You can take a look at {{ic|/usr/lib/systemd/system/rc-local.service}} and {{ic|/usr/lib/systemd/system/rc-local-shutdown.service}} for inspiration.<br />
<br />
8) Removing {{ic|initscripts}}<br />
<br />
Your {{ic|/etc/rc.conf}} file must look like this:<br />
{{bc|1=DAEMONS=()}}<br />
and {{ic|/etc/rc.local}} and {{ic|/etc/rc.local.shutdown}} must now be empty.<br />
<br />
Uninstall {{ic|initscripts}}<br />
{{bc|pacman -R initscripts}}<br />
<br />
{{bc|reboot}}<br />
<br />
===Xen===<br />
{{Expansion|Are there instructions specific to VPSes?}}<br />
See [[Xen#Arch as Xen guest (PVHVM mode)]] and/or [[Xen#Arch as Xen guest (PV mode)]].<br />
<br />
===Converting OpenStack and Xen components to systemd===<br />
There are three components that need to be enabled in systemd when using a VPS based on OpenStack/Xen, such as Rackspace NextGen Cloud. The current version of {{Pkg|xe-guest-utilities}} contains two of these: xe-linux-distribution and xe-daemon.<br />
<br />
You will need to create a custom service file for the OpenStack nova-agent, as the current version 0.0.1.37 only comes with a sysvinit start-up script.<br />
<br />
{{hc|1=/etc/systemd/system/nova-agent.service|2=<br />
[Unit]<br />
Description=nova-agent service<br />
After=xe-daemon.service<br />
<br />
[Service]<br />
Environment=LD_LIBRARY_PATH=/usr/share/nova-agent/0.0.1.37/lib<br />
ExecStart=usr/bin/nova-agent -n -l info /usr/share/nova-agent/nova-agent.py<br />
<br />
[Install]<br />
WantedBy=multi-user.target}}<br />
Once these steps are done, you can continue with converting the server from sysvinit to systemd.<br />
<br />
Make sure to enable the following services:<br />
# systemctl enable xe-linux-distribution<br />
# systemctl enable xe-daemon<br />
# systemctl enable nova-agent<br />
<br />
==Troubleshooting==<br />
===OpenVZ: kernel too old for glibc===<br />
Are you on a virtual private server (VPS) with an old kernel & broke your system? Are you using OpenVZ?<br />
<br />
Check your kernel version with:<br />
<br />
{{bc|uname -r}}<br />
<br />
If your kernel is older than 2.6.32, you will need a custom version of glibc ([https://www.archlinux.org/news/minimum-kernel-requirement-2632/ because of dependencies in glibc]).<br />
<br />
Arch Template Used: https://dev.archlinux.org/~ibiru/openvz/2010.05/arch-2010.05-i686-minimal.tar.gz<br />
<br />
{{Note|For installs that have not been updated to glibc-2.16, it will save you lots of time and prevent major breakage to do:<br />
pacman -U https://dev.archlinux.org/~ibiru/openvz/glibc-vps/i686/glibc-2.16.0-101-i686.pkg.tar.xz<br />
or<br />
pacman -U https://dev.archlinux.org/~ibiru/openvz/glibc-vps/x86_64/glibc-2.16.0-101-x86_64.pkg.tar.xz<br />
Add a single {{ic|-d}} if needed. ''The instructions below assume that this has been done.''<br />
}}<br />
<br />
Following similar instructions from [[DeveloperWiki:usrlib]].<br />
<br />
Try doing the following to fix it:<br />
<br />
1) Edit {{ic|/etc/pacman.conf}} and add the following repository '''ABOVE''' {{ic|[core]}}:<br />
<br />
For 32-bit:<br />
{{bc|<nowiki>[glibc-vps]<br />
Server = https://dev.archlinux.org/~ibiru/openvz/glibc-vps/i686</nowiki>}}<br />
<br />
For 64-bit:<br />
{{bc|<nowiki>[glibc-vps]<br />
Server = https://dev.archlinux.org/~ibiru/openvz/glibc-vps/x86_64</nowiki>}}<br />
<br />
2) Then run {{ic|pacman -Syy}} followed by {{ic|pacman -Syu}}. You will be notified to upgrade pacman first.<br />
<br />
3) Upgrade the [[pacman]] database by running {{ic|pacman-db-upgrade}} as root.<br />
<br />
4) Edit {{ic|/etc/pacman.conf.pacnew}} (new pacman config file) and add the following repository '''ABOVE''' {{ic|[core]}}:<br />
{{bc|<nowiki>[glibc-vps]<br />
Server = https://dev.archlinux.org/~ibiru/openvz/glibc-vps/$arch</nowiki>}}<br />
<br />
5) Replace {{ic|/etc/pacman.conf}} with {{ic|/etc/pacman.conf.pacnew}} (run as root):<br />
# mv /etc/pacman.conf.pacnew /etc/pacman.conf<br />
<br />
6) Upgrade your whole system with new packages again {{ic|pacman -Syu}}<br />
<br />
If you get the following error or a similar error:<br />
{{bc|initscripts: /etc/profile.d/locale.sh exists in filesystem}}<br />
<br />
Simply delete that file (e.g., {{ic|rm -f /etc/profile.d/locale.sh}}), then run {{ic|pacman -Syu}} again.<br />
<br />
If you get the following error or a similar error:<br />
{{bc|filesystem: /etc/mtab exists in filesystem}}<br />
<br />
Run {{ic|pacman -S filesystem --force}}<br />
<br />
If you get the following error or a similar error:<br />
{{bc|libusb-compat: /usr/bin/libusb-config exists in filesystem}}<br />
<br />
Run {{ic|pacman -S libusb}} and then {{ic|pacman -S libusb-compat}}<br />
<br />
7) Before rebooting, you need to [[pacman|install]] the {{Pkg|makedev}} package from the [[Official repositories|official repositories]] by running {{ic|pacman -S makedev}}.<br />
<br />
8) Add MAKEDEV to {{ic|/etc/rc.local}}:<br />
/usr/sbin/MAKEDEV tty<br />
/usr/sbin/MAKEDEV pty<br />
<br />
9) Edit {{ic|/etc/inittab}}, comment out the following lines; otherwise, you will see errors in {{ic|/var/log/errors.log}}):<br />
#c1:2345:respawn:/sbin/agetty -8 -s 38400 tty1 linux<br />
#c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux<br />
#c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux<br />
#c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux<br />
#c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux<br />
#c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux<br />
<br />
10) To enable use of the {{ic|hostname}} command, [[pacman|install]] the package {{Pkg|inetutils}} from the [[Official repositories|official repositories]]. <br />
<br />
11) Remove disabling of the SysRq key and setup of core dump pattern because this is blocked by OpenVZ and causes errors.<br />
<br />
Because sysctl does not use {{ic|/etc/sysctl.conf}} any more[https://www.archlinux.org/news/deprecation-of-etcsysctlconf/], you must transfer all settings to {{ic|/etc/sysctl.d/99-sysctl.conf}} (or any other file in {{ic|/etc/sysctl.d/}}; however, do not transfer the following line:<br />
{{bc|1=kernel.sysrq = 0}}<br />
<br />
Edit {{ic|/usr/lib/sysctl.d/coredump.conf}} and comment out the following line:<br />
{{bc|1=#kernel.core_pattern=&#124;/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e}}<br />
<br />
12) Save and reboot.<br />
<br />
Enjoy & thank ioni if you happen to be in #archlinux<br />
<br />
===SSH fails: PTY allocation request failed on channel 0===<br />
<br />
Some VPSes have an outdated {{ic|/etc/rc.sysinit}}. You may be able to log in via serial console or with the following command:<br />
$ ssh root@broken.server '/bin/bash -i'<br />
<br />
Then run the following:<br />
# mv /etc/rc.sysinit.pacnew /etc/rc.sysinit<br />
# reboot<br />
<br />
Once it is working, you should be able to comment out the {{ic|udevd_modprobe}} line in {{ic|/etc/rc.sysinit}} to save a bit of RAM the next time you reboot.<br />
<br />
If the above does not work, take a look at [http://fsk141.com/fix-pty-allocation-request-failed-on-channel-0 this guide].</div>Badvok