https://wiki.archlinux.org/api.php?action=feedcontributions&user=Deadrabbit&feedformat=atomArchWiki - User contributions [en]2024-03-28T18:38:44ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&diff=447924Talk:Installation guide2016-08-25T17:52:43Z<p>Deadrabbit: /* Hostname */ correction suggested</p>
<hr />
<div>== Read this first before adding new suggestions ==<br />
<br />
* The point of this page is to be a ''concise'' checklist of things to be done. Detailed instructions belong in wiki articles or upstream documentation which describe the respective topics.<br />
* Should you have more complex changes for this guide in mind, create a copy on your user page, and link it here for review.<br />
* systemd tools such as ''hostnamectl'', ''timedatectl'' and ''localectl'' [https://github.com/systemd/systemd/issues/798#issuecomment-126568596 do not work] in the installation chroot environment, so please do not propose to use them in the guide unless you can prove that they have been made to work also in that case. See [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=388727#General_problems], [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=404695#Replace_commands_with_their_systemd_equivalents], [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=418662#Utilizing_systemd_tools] and [https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&oldid=434985#change_configuration_system_from_old_way_to_new_way.28using_systemd_commands.29] for some past discussions about this issue.<br />
* {{ic|localectl list-keymaps}} does not work due to bug {{Bug|46725}}. For the chosen replacement command, see [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=435044#localectl].<br />
<br />
-- [[ArchWiki:Administrators|The ArchWiki Administrators]] 12:16, 25 July 2016 (UTC)<br />
__TOC__<br />
<br />
== "See ''foo''" vs "See the ''foo'' article" ==<br />
<br />
:Moved from [[Talk:Beginners' guide]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 20:29, 12 July 2016 (UTC)<br />
<br />
This revision [https://wiki.archlinux.org/index.php?title=Beginners%27_guide&diff=400266&oldid=400243] added a new mention of "See the ''foo'' article", rather than the more common "See ''foo''". I'd argue former is the better form, and when the guide is viewed from a .txt (if the BG/IG merge completes), the longer wording makes sense as well. Are there opinions against using the longer form throughout the BG? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:13, 18 September 2015 (UTC)<br />
<br />
:I'm neutral, so that doesn't count as an opinion against ^^ That said, the long form can only be used with links to entire articles, but more difficultly with links to specific sections such as "See also [[Pacman#pacman crashes the official installation media]]", since in those cases a more natural-sounding long form should be something like "See also the 'pacman crashes the official installation media' section of the [[Pacman]] article", I think, which is clearly ugly to see and use, so consistency is a bit hard to reach. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 16:13, 18 September 2015 (UTC)<br />
<br />
::I guess the proper solution would be to incorporate links in the article text where possible. "See X" gets repetitive fast, anyway. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:44, 29 September 2015 (UTC)<br />
<br />
== pacman-key --populate ==<br />
<br />
:Moved from [[Talk:Beginners' guide]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 20:38, 12 July 2016 (UTC)<br />
<br />
Reference: https://wiki.archlinux.org/index.php?title=Beginners%27_guide&diff=next&oldid=411670<br />
I tried to install Archlinux on my new computer and got stuck. Only using the {{ic|pacman-key --populate archlinux}} helped me. I think I am not the only one having this problem. But why did you undo it? {{Unsigned|20:38, 12 December 2015|Sandstorm}}<br />
:This command is already run for the new system (by installation of archlinux-keyring), so running it by hand shouldn't be required for most users. Of course, things can go wrong (how old was the ISO you used to install the system?), but that belongs in Troubleshooting sections of the respective articles, which are linked at the beginning of the guide. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:52, 12 December 2015 (UTC)<br />
::I had downloaded the ISO just yesterday, minutes before the install. Only that command installed the keys. Probably I should open a bug if you can confirm the issue?<br />
:::Did you have to run pacman-key after, or before pacstrap? And do you recall what the error messages said exactly? (See also {{Bug|31286}}) -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 20:15, 12 December 2015 (UTC)<br />
::::I had to run after pacstrap. As far as I remember, pacstrap stopped after trying to download the keys. The error message was something like shown in this forum post: https://bbs.archlinux.org/viewtopic.php?id=165367<br />
:::::Well then, as you suggested, I'd open a bug report. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 20:34, 12 December 2015 (UTC)<br />
::::::Done. Could you check if the description is good. I could not find an appropriate category, so I though Packages:Core might be the closest one. https://bugs.archlinux.org/task/47351 --[[User:Sandstorm|Sandstorm]] ([[User talk:Sandstorm|talk]]) 20:48, 12 December 2015 (UTC)<br />
:::::::Thanks, the description looks OK. If the category e.a is not right, [[Special:Contributions/Scimmia|User:Scimmia]] should fix it. :P -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:59, 13 December 2015 (UTC)<br />
<br />
::::::::Hmm, looks like it was closed with "Works for me" ... not very enlightening. All I can suggest is to further improve on [[Pacman/Package signing]] and related articles, and recheck if they're accessible enough from the Beginners' guide. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 21:59, 12 February 2016 (UTC)<br />
<br />
== timesyncd: add manual date ==<br />
<br />
:Moved from [[Talk:Beginners' guide]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 20:44, 12 July 2016 (UTC)<br />
<br />
While the right time isn't as important in the live system as in the installed one, it may still be unexpected to users [https://wiki.archlinux.org/index.php?title=Beginners%27_guide&diff=432465&oldid=431268]. We could instead instruct to specify a date explicitly to timedatectl. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:25, 6 July 2016 (UTC)<br />
<br />
:Is the issue setting the time manually or just setting the time zone? The change you linked to just had setting the time zone. -- [[User:Rdeckard|Rdeckard]] ([[User_talk:Rdeckard|talk]]) 01:29, 9 July 2016 (UTC)<br />
<br />
::Well, with setting it manually you'd kill two birds with one stone. The time would be what users expect, but without adding an extra step of little consequence. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:35, 12 July 2016 (UTC)<br />
<br />
== <s>BG merge</s> ==<br />
<br />
Progress on [[Talk:Beginners'_guide#The_Great_Merge]] is below. Note that content is not copied literally from the BG, but kept in the style and spirit of the IG. This keeps a clear overview of the various steps; if more detailed instructions are required, these belong in dedicated articles. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 23:32, 9 July 2016 (UTC)<br />
<br />
:The merge is done. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:30, 23 August 2016 (UTC)<br />
<br />
::Well, I thought this was too big of a change not to take this chance to thank you and all those who contributed to discussing and implementing this task during the past ''years''!! — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:05, 24 August 2016 (UTC)<br />
<br />
=== <s>Sections</s> ===<br />
<br />
:: Introduction [✔]<br />
# Preparation<br />
## UEFI mode [✔]<br />
## Set the keyboard layout [✔]<br />
## Connect to the internet [✔]<br />
## Update the system clock [✔]<br />
# Prepare the storage devices<br />
## Identify the devices [✔]<br />
## Partition the devices [✔]<br />
## Format the partitions [✔]<br />
## Mount the partitions [✔]<br />
# Installation<br />
## Select the mirrors [✔]<br />
## Install the base packages [✔]<br />
# Configuration<br />
## fstab [✔]<br />
## Change root [✔]<br />
## Locale [✔]<br />
## Time [✔]<br />
## Initramfs [✔]<br />
## Boot loader [✔]<br />
## Network configuration [✔]<br />
### Hostname [✔]<br />
### Wired [✔]<br />
### Wireless [✔]<br />
## Root password [✔]<br />
# Unmount the partitions and reboot [✔]<br />
# Post-installation [✔]<br />
<br />
== Switch to systemd-networkd ==<br />
<br />
Next ISOs may use systemd-networkd instead of dhcpcd, see [https://lists.archlinux.org/pipermail/arch-releng/2016-July/003739.html] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:26, 19 July 2016 (UTC)<br />
<br />
== Dual-boot with windows ==<br />
<br />
In the [[Beginners' guide]], this is mentioned in [[Beginners'_guide#Format_the_partitions]], but perhaps this should be linked earlier, e.g. in [[Installation guide#Pre-installation]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 12:08, 25 July 2016 (UTC)<br />
<br />
:What about [[Installation_guide#Partition_the_disks]]? — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 09:51, 26 July 2016 (UTC)<br />
<br />
== The Great Merge ==<br />
<br />
:''[Moved from [[Talk:Beginners' guide]]. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:11, 24 August 2016 (UTC)]''<br />
<br />
[[#Plan]] reaches closure, and the [[Beginners' guide]] is now comparable in size to the [[Installation guide]]. "Cleanup day" [https://bbs.archlinux.org/viewtopic.php?id=214373] would be a good time to start the merge of both guides, and replace the Beginners' guide, together with translations on this domain, to redirections to the [[Installation guide]]. <br />
<br />
It would be preferable if before then, a TU or dev also brings this up on arch-dev-public for input from the developers, also regarding [[#Page protection]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:25, 5 July 2016 (UTC)<br />
<br />
:I agree with extending the redirection to the translations, with the exception of 4 which are actively maintained or have been retranslated recently, so I've flagged them to see if their maintainers want to deal with the merge on their own: [[Beginners' guide (العربية)]], [[Beginners' guide (Español)]], [[Beginners' guide (Русский)]] and [[Beginners' guide (简体中文)]]. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:58, 6 July 2016 (UTC)<br />
<br />
:: I will take care of [[Beginners' guide (简体中文)]]. --[[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 06:21, 7 July 2016 (UTC)<br />
<br />
::: Note that typically content is rewritten in the [[Installation guide]], rather than taken literally from the [[Beginners' guide]] (see [[Talk:Installation_guide#BG_merge]]), so my suggestion is to focus translation efforts on the Installation guide, rather than the Beginners' guide. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:44, 12 July 2016 (UTC)<br />
<br />
::: I've redirected all translations apart from the above. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:50, 12 July 2016 (UTC)<br />
<br />
::::There are still some pages left: [https://wiki.archlinux.org/index.php?title=Special%3APrefixIndex&prefix=Beginners%27+Guide&namespace=0&hideredirects=1] -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:13, 14 July 2016 (UTC)<br />
<br />
:::::I've just handled those, but there's more to do at [https://wiki.archlinux.org/index.php?title=Special%3APrefixIndex&prefix=begin&namespace=10]. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:38, 14 July 2016 (UTC)<br />
<br />
::::::What's the point of redirecting templates to regular pages? [https://wiki.archlinux.org/index.php?title=Template:Beginners%27_Guide_navigation_(Dansk)&curid=10983&diff=441462&oldid=387477] [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:59, 15 July 2016 (UTC)<br />
<br />
:::::::We were discussing that in [[ArchWiki_talk:Administrators#How_to_archive_templates]], we had a half-baked solution, maybe we should just put it to the vote. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 14:28, 16 July 2016 (UTC)<br />
<br />
::::::::Oops, 154 days and still no reply from me, sorry about that... Thanks for your patience and strong nerves for the future, because unfortunately it's far from being the worst case of my this-year-maybe discussions :P<br />
::::::::In this case, I'd say that the templates can be simply deleted: it's fairly trivial transclusion of one &lt;div> and a couple of links, without any MediaWiki hacks, which can be recreated any time if needed. There is also pretty low probability that beginners' guides will be allowed in the near (less than 10 years) future in general, let alone split across multiple pages requiring navigational template. And if it's needed sometime in the next century, they will most likely have something better than MediaWiki's obscure template syntax.<br />
::::::::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 15:13, 16 July 2016 (UTC)<br />
<br />
:::::::::These redirected templates are a very marginal problem IMO, I don't mind if they stay as redirects or are deleted, but only because the fact that [[ArchWiki_talk:Administrators#How_to_archive_templates]] is still open justifies deciding case by case for the moment. Note that as redirects they don't pollute [[Special:UnusedTemplates]]. I wouldn't like to promote deletion as the official default template archiving method though, but I agree with delaying the resolution of that discussion, there are other priorities right now. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 13:57, 18 July 2016 (UTC)<br />
<br />
::::::::::So I've taken the chance and deleted the BG navigation templates. Let's wait for [[ArchWiki_talk:Administrators#How_to_archive_templates]] with the general decision, hopefully this year... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:06, 25 July 2016 (UTC)<br />
<br />
=== Main page link ===<br />
<br />
Before redirecting we have to decide at least how to rebalance the links in the [[Main page]]: what about also removing the [[Arch Linux press coverage]] link from the left colum? That article is pretty much unmaintained anyway, we can give it more backlinks from somewhere else. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:04, 6 July 2016 (UTC)<br />
<br />
:+1 from me -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:30, 6 July 2016 (UTC)<br />
<br />
Let's not forget that we must also patch [https://git.archlinux.org/archweb.git/tree/templates/public/index.html#n116 the main home page]. — [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:14, 13 July 2016 (UTC)<br />
<br />
=== Translations ===<br />
<br />
The translations of the [[Main page]] should be updated along with the English page. Also the [https://wiki.archlinux.org/index.php/Special:WhatLinksHere/Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87) backlinks] of the BG translations should be cleaned as much as possible, as that might be somewhat [https://wiki.archlinux.org/index.php?title=Beginners%27_guide_(%E6%AD%A3%E9%AB%94%E4%B8%AD%E6%96%87)&diff=443707&oldid=443682 confusing] for future translators. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:45, 30 July 2016 (UTC)<br />
<br />
:Oh jolly... can we automate this with a bot somehow? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:12, 30 July 2016 (UTC)<br />
<br />
::I haven't been doing any natural language processing yet, but if you feel like teaching my bot Chinese, please help yourself :)<br />
::Just kidding, I could probably make some semi-automatic assistant to at least quickly find and mark the links and open vimdiff for manual editing.<br />
::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:23, 30 July 2016 (UTC)<br />
<br />
== Clarifications ==<br />
<br />
=== General ===<br />
<br />
From [https://www.reddit.com/r/archlinux/comments/4z7z0i/the_beginners_guide_has_been_removed_from_the_wiki/d6ui70e /u/youguess]:<br />
<br />
* Verify the boot mode tells you to check efivars but doesn't give the expected output (if none, no UEFI)<br />
* Connect to the internet, maybe direct link to wireless?<br />
* Mount the partion was easier to follow in the beginners guide, what I kind of miss is the explicit command example of first creating and then mounting a subdir of root (yes I know that it should be clear how to do that, but it wasn't for me at first before I read about what chrooting does)<br />
* Initramfs, maybe add some examples like "eg encrypting/btrfs hook" so that beginners know what it is for?<br />
<br />
-- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:38, 24 August 2016 (UTC)<br />
<br />
I would also say the biggest pain points are the partitioning, filesystem and mount sections --[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
=== Connect to the Internet ===<br />
<br />
"For other network configuration, ..." is badly worded<br />
<br />
There is no mention of wireless networks<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
Why are both [[Systemd-networkd]] and [[netctl]] wiki pages and man pages both mentioned like this?: "If a different [[network configuration]] tool is needed, [[systemd-networkd]] and [[netctl]] are available. See systemd.network(5) and netctl.profile(5) for examples." The man pages should be mentioned in those respective wiki pages. The section should rewritten as: "If a different [[network configuration]] tool is needed, see either [[systemd-networkd]] or [[netctl]] for details." [[User:H0x0d|H0x0d]] ([[User talk:H0x0d|talk]]) 14:27, 25 August 2016 (UTC)<br />
<br />
=== Partition the disks ===<br />
<br />
A section on how to identify the devices is completely missing<br />
<br />
The old page provided a very succinct introduction to partitioning, clear examples as well as appropriate warnings that data loss will incur if used incorrectly<br />
<br />
The new page provides none of that, rather linking to many separate pages not as extra information or for less common use cases as is common in the Beginners' guide but rather as the only way to accomplish the task, it never actually answers the question "What do I need to do?"<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
=== Format the partitions ===<br />
<br />
Similar story again, the new guide fails to answer the question "What do I need to do?", it abstracts away to the page on filesystem article that bombards a new user with 16 different filesystems instead of the common case the beginners guide provided: it mentioned explicitly it's recommended to use ext4<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
=== Mount the partitions ===<br />
<br />
Instead of providing two short examples the user is asked to read the manpage for mount, for a beginner this is pretty unnecessary. They're then told to create directories but not told how<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
: Regarding "mount" I think we should link to [[Mount]] from the installation guide and then we can link to the manpage from there. -- [[User:Rdeckard|Rdeckard]] ([[User_talk:Rdeckard|talk]]) 12:31, 25 August 2016 (UTC)<br />
<br />
::Ok, though we should make some edits to the [[mount]] article. It's structured oddly, e.g the first section is a convoluted zgrep line.<br />
::For the examples, the main reason I've left them out is because the Beginners' guide used a horrid "/dev/sdxy, where x is ... and y ..." scheme. Though if you're following along, it should be pretty clear what a command like {{ic|mount ''/dev/sda1'' /mnt}} means. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:32, 25 August 2016 (UTC)<br />
<br />
=== <s>Fstab</s> ===<br />
<br />
Minor but I would think it's generally preferable to use -U as in the Beginners' guide since new users probably won't alter the command themselves<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
:Via [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=447912&oldid=447904] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:17, 25 August 2016 (UTC)<br />
<br />
=== <s>Time Zone</s> ===<br />
<br />
"other operating systems should be configured accordingly." - Why/How?<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
:If you follow the link to [[time standard]], you'll see why and how. That's about as much as the installation guide can contain on this topic. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:50, 25 August 2016 (UTC)<br />
<br />
::I wonder if using a wording like "See [[time standard]] for details" is more clear after all. cf. [[#.22See_foo.22_vs_.22See_the_foo_article.22]] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:02, 25 August 2016 (UTC)<br />
<br />
::: Yes I agree. It's similar to the hostname section I commented on below. The whole article needs to make it clear that clicking on certain links will show the user on how to accomplish a task, vs simply giving more insight on something. [[User:H0x0d|H0x0d]] ([[User talk:H0x0d|talk]]) 14:09, 25 August 2016 (UTC)<br />
<br />
::::This is completely fine and natural, the proposed alternative ("If the time standard is set to UTC, other operating systems should be configured accordingly. See [[time standard]] for details.") is overly repetitive. Unlike other media, on ArchWiki there are links incorporated into the text not to be ignored, but followed, if not already known to the reader. We're giving the reader a hint, it's up to them how they handle it. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:39, 25 August 2016 (UTC)<br />
<br />
::::: Overly repetitive is better than being unclear, when it comes to a guide like this. If you don't want to repeat the phrases "see details", then it should be at least written like this: "If the time standard is set to UTC, other operating systems should be [[time standard|configured accordingly]]." [[User:H0x0d|H0x0d]] ([[User talk:H0x0d|talk]]) 14:47, 25 August 2016 (UTC)<br />
<br />
::::::Alright, [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=447902&oldid=447900 changed]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 15:05, 25 August 2016 (UTC)<br />
<br />
=== Locale ===<br />
<br />
If a user doesn't know what they are yet, they may not know which are needed<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
=== Hostname ===<br />
<br />
Again needing to read manpages instead of a short example<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
:There is a link to [[hostname]], we won't duplicate its content here. Closing. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:46, 25 August 2016 (UTC)<br />
<br />
::Well, a single code line {{ic|# echo myhostname > /etc/hostname}} wouldn't hurt, as [[hostname]] first mentions ''hostnamectl'', only to then mention it doesn't work in the installation environment and that you should [[edit]] {{ic|/etc/hostname}}. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:06, 25 August 2016 (UTC)<br />
<br />
:::That's a good point. I'll leave it up to you to add it to the [[Installation guide]] or [[Network configuration]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:48, 25 August 2016 (UTC)<br />
:::The line {{ic|#echo myhostname > /etc/hosts}} needs to be corrected to /etc/hostname. --[[User:Deadrabbit|Deadrabbit]] ([[User talk:Deadrabbit|talk]]) 17:52, 25 August 2016 (UTC)<br />
<br />
::::Via [https://wiki.archlinux.org/index.php?title=Network_configuration&type=revision&diff=447899&oldid=447877] and [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=447900&oldid=447890] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:04, 25 August 2016 (UTC)<br />
<br />
[[Network configuration]] covers setting the hostname in better detail than the Hostname section, perhaps it can be just covered there instead of in the install guide also.<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
:The [[Installation_guide#Hostname]] section already contains little more than the link to [[hostname]] (redirects to [[Network configuration#Set the hostname]]), so I'd say it's pretty much "covered there". Do you suggest to remove the section completely? -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:45, 25 August 2016 (UTC)<br />
<br />
:: However that link isn't worded in a way that makes it obvious that following that link would show one how to set the hostname. It should said like this: "Create an entry for your hostname in /etc/hostname and /etc/hosts. See [[Network configuration#Set the hostname]] for example on how to set the hostname." There's no need to mention the hostname or hostnamectl man pages in the Installation Guide as they are already covered in the [[Network configuration#Set the hostname]] section. [[User:H0x0d|H0x0d]] ([[User talk:H0x0d|talk]]) 13:55, 25 August 2016 (UTC)<br />
<br />
::: This should be covered by the edits above -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:14, 25 August 2016 (UTC)<br />
<br />
=== Initramfs ===<br />
<br />
It's not mentioned that most users don't need to worry about this section<br />
<br />
--[[User:Alexendoo|Alexendoo]] ([[User talk:Alexendoo|talk]]) 12:28, 24 August 2016 (UTC)<br />
<br />
=== Elinks ===<br />
<br />
[[w:Virtual console]] usage is probably too basic/essential to keep as a Tip on the [[elinks]] page. It should be mentioned in the introduction or [[Installation guide#Pre-installation]] instead. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:10, 24 August 2016 (UTC)<br />
<br />
=== Small suggestion ===<br />
<br />
I think in [[Installation guide#Partition the disks|Partition the disks]] section should be also mentioned ''cfdisk'' as its much easier for beginners and in [[Installation guide#Install the base packages|Install the base packages]] section should be also mentioned ''base-devel'' package group. --[[User:Conder|Conder]] ([[User talk:Conder|talk]]) 15:44, 30 July 2016 (UTC)<br />
<br />
:Whether cfdisk is easier for beginners depends on the person using it; for instance, someone on IRC was installing Arch for the first time and found the menu-based approach of gdisk more straightforward than the "GUI" of cgdisk. That said, we might as well link to the man page.<br />
:For base-devel, see [[#Let.27s_mention_filesystem_tools_in_pacstrap_step]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:17, 30 July 2016 (UTC)<br />
<br />
::We might as well link to the [[fdisk]] page instead, which covers all 6 tools; cf. [https://wiki.archlinux.org/index.php?title=Help_talk:Style&diff=443278&oldid=443277]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 17:44, 30 July 2016 (UTC)<br />
<br />
:::Okay, though the article mentions "This article covers fdisk and its related sfdisk and cfdisk utilities, as well as the analogous gdisk, sgdisk and cgdisk utilities" but misses the promised cfdisk/cgdisk sections. I guess there's not that much to explain anyway, cf. {{man|8|cfdisk}} "Note that cfdisk provides basic partitioning functionality with a user-friendly interface. If you need advanced features, use fdisk(8) instead."<br />
:::Updated links with [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=443798&oldid=443361] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:05, 30 July 2016 (UTC)<br />
<br />
::::This said, one benefit of using man templates is that the format remains useful for {{ic|install.txt}}, contrary to wiki links which are converted to plain text. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 20:07, 9 August 2016 (UTC)<br />
<br />
=== A note for Xen users ===<br />
<br />
For Xen PV VMs, the hwclock --systohc --utc command does not need to be run. Please update the article. [[User:RudyValencia|RudyValencia]] ([[User talk:RudyValencia|talk]]) 12:07, 1 August 2016 (UTC)<br />
<br />
:This guide isn't meant to account for every special use case a user might have. Add something to the [[Time]] article if you think this is relevant. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:09, 1 August 2016 (UTC)<br />
<br />
::On second thought, I assume this applies to other [[virtual machine]]s as well? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:35, 1 August 2016 (UTC)<br />
<br />
::: To be honest, running {{ic|hwclock --systohc --utc}} is hardly required if you plan to run a desktop enviroment, since most DEs can automatically set up your clock. But I agree that this should better be stated in the [[Time]] article [[User:Jujstme|Jujstme]] ([[User talk:Jujstme|talk]]) 14:38, 24 August 2016 (UTC)<br />
<br />
:::: It's something that could fit [[General recommendations]], yeah. That said, I'd say people should at least know on the UTC/localtime difference. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:47, 24 August 2016 (UTC)<br />
<br />
=== <s>LVM and partitioning clarification</s> ===<br />
<br />
I guess that it's worth mentioning that now (as on 23th of August, 2016) lvm2 package automatically installs and it needs to be removed/skipped if not utilized since it would make grub-mkconfig operate incorrectly and lead to unbootable OS.<br />
Also, beginners' guide had a small example how to do partitioning using parted, now there's none, not in this guide nor in beginners' one.<br />
<br />
{{unsigned|04:38, 23 August 2016|ThePanda}}<br />
<br />
:The {{Pkg|lvm2}} package has been part of the {{Grp|base}} group [https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/lvm2&id=50d7227a240f7ab65ca5660fc26a121706fffbff since at least 2008] so the problem is hardly at its side. The description of using parted is on the [[parted]] page, which is linked from both guides. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:13, 23 August 2016 (UTC)<br />
<br />
=== <s>"Other partitions may be needed" - needs expanding</s> ===<br />
<br />
I suggest adding a short list of the situations where one might need to add a special partition to the disk. Knowing the pitfalls can save a lot of time. <br />
<br />
For example, I recently installed Arch on a BTRFS RAID 1 array. I had planned to use Syslinux (my normal choice) but didn't find out until after installing that Syslinux doesn't support BTRFS multi-device. So I tried switching to GRUB, but of course I hadn't put a 1MB partition at the beginning of the drive. I had to wipe everything and start over. So just a short paragraph or (better still) a table here would be helpful - it could show the system configurations that different bootloaders support, and the various partitioning schemes that they require. <br />
<br />
At the very least, it would be helpful to see "Check to make sure your system configuration is supported by your intended bootloader, and find out whether it will require additional partitions before you partition your disk."<br />
<br />
[[User:Afontenot|afontenot]] ([[User talk:Afontenot|talk]]) 02:49, 24 August 2016 (UTC)<br />
<br />
:It seems this issue is hidden away as a Troubleshooting item in [[Syslinux#Btrfs_multi-device]]. First, it should be made more prominent in [[Btrfs#Multi-device_file_system]] and possibly [[RAID]].<br />
:For the table, we could expand on the existing one in [[:Category:Boot loaders]]. Establishing a relation between file systems and boot loaders as you propose sounds good though. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 06:05, 24 August 2016 (UTC)<br />
<br />
::It would have been enough to read the first sentence of the [[syslinux]] page. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:39, 24 August 2016 (UTC)<br />
<br />
:::Good point; I've fixed the link to not only point to the ext4 section of the syslinux wiki: [https://wiki.archlinux.org/index.php?title=Syslinux&curid=10347&diff=447636&oldid=446213]. I also think it doesn't hurt repeating, see: [https://wiki.archlinux.org/index.php?title=Category:Boot_loaders&curid=14299&diff=447639&oldid=440617], [https://wiki.archlinux.org/index.php?title=Btrfs&curid=10448&diff=447637&oldid=446122] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 10:18, 24 August 2016 (UTC)<br />
<br />
:::Glad to see it's been added to the [[syslinux]] page - it wasn't when I did the install a month and a half ago. [[User:Afontenot|afontenot]] ([[User talk:Afontenot|talk]]) 07:07, 25 August 2016 (UTC)<br />
<br />
::::Yeah, I think [https://wiki.archlinux.org/index.php?title=Category:Boot_loaders&curid=14299&diff=447639&oldid=440617] solves the problem, closing. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:22, 25 August 2016 (UTC)<br />
<br />
=== "Boot loader" - clarification ===<br />
<br />
I suggest to briefly expand the Boot Loader section. Since GRUB is probably the easiest boot loader to configure for a beginner, just a simple sentence that clarifies that could be enough. [[User:Jujstme|Jujstme]] ([[User talk:Jujstme|talk]]) 15:16, 24 August 2016 (UTC)<br />
<br />
:What in particular do you have in mind? Once upon a time, the Beginners' guide had a GRUB section for both BIOS/MBR and UEFI/GPT, but then it was mentioned that GRUB is not the recommended method for UEFI/GPT [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=416614#Replace_systemd-boot_with_GRUB_.28UEFI.29], and that you should use systemd-boot instead. These sort of discussions on what's recommended and what not is why the guide ended up with linking to [[:Category:Boot loaders]] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:11, 25 August 2016 (UTC)<br />
<br />
=== "Connect to the Internet" is not properly explained ===<br />
It says: "check the connection using a tool such as ping(8)." But ping's man page is huge with lots of options of the ping command detailed. But nowhere does it have a simple example such as "ping google.com" which is exactly what someone trying to check the internet connection would need. The above line should be replaced with how it was in the Beginner's Guide: "Verify a connection was established, for example with ping archlinux.org".<br />
<br />
Basic wired and wireless connection scenarios should be on the installation page itself like it was in the Beginner's Guide.<br />
<br />
"When using either service, stop dhcpcd@interface.service:" What is an interface? It's not explained here. Should be explained like it was in the Beginner's Guide:<br />
"Interfaces can be listed using ip link, or iw dev for wireless devices. They are prefixed with en (ethernet), wl (WLAN), or ww (WWAN)." And the command should also come with a concrete example like the Beginner's Guide was: "# systemctl stop dhcpcd@enp0s25.service".<br />
[[User:H0x0d|H0x0d]] ([[User talk:H0x0d|talk]]) 19:58, 24 August 2016 (UTC)<br />
<br />
: Perhaps with {{ic|ping}} we could link to [[Network configuration#Check the_connection]]. -- [[User:Rdeckard|Rdeckard]] ([[User_talk:Rdeckard|talk]]) 12:31, 25 August 2016 (UTC)<br />
<br />
:: Good suggestion, [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=447850&oldid=447679 done]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:28, 25 August 2016 (UTC)<br />
<br />
::: Is it useful to add a code line with {{ic|# ping archlinux.org}} (interrupted by {{ic|Ctrl-c}}) ? I'm unsure since there's a good bit of context to using ping, such as pinging with DNS or the IP address. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:26, 25 August 2016 (UTC)<br />
<br />
:::: I'd leave it this way, after all the installation guide is not a debugging guide, it can't cover everything that could possibly go wrong. Let's focus on the wireless part. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:32, 25 August 2016 (UTC)<br />
<br />
: The "interface" text was changed with [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=441809&oldid=441764]. However, it doesn't hurt to give a quick explanation on what an interface is, possibly with a reminder they can be tab-completed. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 13:26, 25 August 2016 (UTC)<br />
<br />
:: Clarified in [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=447853&oldid=447850]. Users will have to read [[systemd-networkd]] or [[netctl]] anyway if they need something better than dhcpcd, so we can skip the details here. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:37, 25 August 2016 (UTC)<br />
<br />
::: But neither [[systemd-networkd]] nor [[netctl]] pages proper explain what an interface is, or how one can list them using ip link or iw dev commands. [[User:H0x0d|H0x0d]] ([[User talk:H0x0d|talk]]) 13:43, 25 August 2016 (UTC)<br />
<br />
::::[[Systemd-networkd#Configuration_examples]] suggests to use {{ic|networkctl list}}, [[Netctl#Profile_configuration]] (as well as the installation guide) links to [[Network configuration]] for full explanation. Feel free to improve those pages. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:02, 25 August 2016 (UTC)<br />
<br />
::::: Those are buried deep into those articles (as they should be), and in case of Netctl buried inside multiple links. What an interface is and how to obtain them should be more directly explained. Perhaps by linking directly to [[Network_configuration#Get_current_device_names]] from the Installation Guide. [[User:H0x0d|H0x0d]] ([[User talk:H0x0d|talk]]) 14:15, 25 August 2016 (UTC)</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=Firefox/Ubiquity_commands&diff=77184Firefox/Ubiquity commands2009-10-04T20:15:59Z<p>Deadrabbit: </p>
<hr />
<div>= Introduction =<br />
<br />
Due to my recent discovery of [http://labs.mozilla.com/2008/08/introducing-ubiquity/ Ubiquity] and MrGreen's suggestion on the [http://bbs.archlinux.org/viewtopic.php?pid=450773 forum], here's a place for collecting Ubiquity commands that people find of interest.<br />
<br />
= Arch Specific =<br />
'''Requires Ubiquity 0.5+'''<br />
<br />
== AUR Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["aur-packages"],<br />
icon: "http://wiki.archlinux.org/favicon.ico",<br />
description: "Search the AUR for Packages.",<br />
help: "Enter a string to search the AUR",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the Arch Bugtracker for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
var before_url = "http://aur.archlinux.org/packages.php?O=0&L=0&C=0&K=";<br />
var after_url = "&SeB=nd&SB=n&SO=a&PP=25&do_Search=Go";<br />
Utils.openUrlInBrowser(before_url + args.object.text + after_url);<br />
}<br />
}); <br />
<br />
== BBS Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["bbs-arch", "arch bbs"],<br />
icon: "http://wiki.archlinux.org/favicon.ico",<br />
description: "Search all of archlinux forums",<br />
help: "Enter a string to search the archlinux forums",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the Arch forums for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
var before_url = "http://bbs.archlinux.org/search.php?action=search&keywords=";<br />
var after_url = "&author=&forum=-1&search_in=all&sort_by=0&sort_dir=DESC&show_as=topics&search=Submit"<br />
Utils.openUrlInBrowser(before_url + args.object.text + after_url);<br />
}<br />
});<br />
<br />
== Bugtracker Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["arch-bugs"],<br />
icon: "http://wiki.archlinux.org/favicon.ico",<br />
description: "Search the Arch Bugtracker.",<br />
help: "Enter a string to search the Arch Bugtracker.",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the Arch Bugtracker for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
var before_url = "http://bugs.archlinux.org/index.php?string=";<br />
Utils.openUrlInBrowser(before_url + args.object.text);<br />
}<br />
});<br />
<br />
== Wiki Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["awiki", "arch wiki"],<br />
icon: "http://wiki.archlinux.org/favicon.ico",<br />
description: "Search all of archlinux wiki",<br />
help: "Enter a search query",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the wiki for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
Utils.openUrlInBrowser("http://wiki.archlinux.org/index.php/Special:Search?search=" + args.object.text);<br />
}<br />
});<br />
<br />
= Web Lookup =<br />
<br />
== Man Page Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["man", "man page" ],<br />
description: "Search man pages",<br />
help: "Enter a string to search the man pages",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the man pages for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
var before_url = "http://www.linuxmanpages.com/man1/";<br />
var after_url = ".1.php"<br />
Utils.openUrlInBrowser(before_url + args.object.text + after_url);<br />
}<br />
}); <br />
<br />
== Whois Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["whois"],<br />
description: "whois domain lookup",<br />
help: "Enter a domain to query.",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Whois search for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
var before_url = "http://reports.internic.net/cgi/whois?whois_nic=";<br />
var after_url = "&type=domain";<br />
Utils.openUrlInBrowser(before_url + args.object.text + after_url);<br />
}<br />
}); <br />
<br />
== Websters Dictionary ==<br />
'''Not updated for Ubiquity 0.5+ yet'''<br />
<br />
CmdUtils.CreateCommand({<br />
name: "webster-dictionary",<br />
author: {name: "Timothy Sorbera", email: "tim.sorbera@gmail.com"},<br />
license: "MPL",<br />
description: "Searches Webster's Dictionary for your words.",<br />
takes: {search: noun_arb_text},<br />
preview: function(pblock, searchText) {<br />
var html = "Searches Webster's Dictionary for ";<br />
if (searchText.text) {<br />
html += searchText.text;<br />
} else {<br />
html += "your words.";<br />
}<br />
pblock.innerHTML = html;<br />
},<br />
icon: "http://www.merriam-webster.com/favicon.ico",<br />
execute: function(directObject) {<br />
var searchUrl = "http://www.merriam-webster.com/dictionary/" + directObject.text;<br />
Utils.openUrlInBrowser(searchUrl);<br />
}<br />
});<br />
<br />
== Websters Thesaurus ==<br />
'''Not updated for Ubiquity 0.5+ yet'''<br />
<br />
CmdUtils.CreateCommand({<br />
name: "webster-thesaurus",<br />
author: {name: "Timothy Sorbera", email: "tim.sorbera@gmail.com"},<br />
license: "MPL",<br />
description: "Searches Webster's Thesaurus for your words.",<br />
takes: {search: noun_arb_text},<br />
preview: function(pblock, searchText) {<br />
var html = "Searches Webster's Thesaurus for ";<br />
if (searchText.text) {<br />
html += searchText.text;<br />
} else {<br />
html += "your words.";<br />
}<br />
pblock.innerHTML = html;<br />
},<br />
icon: "http://www.merriam-webster.com/favicon.ico",<br />
execute: function(directObject) {<br />
var searchUrl = "http://www.merriam-webster.com/thesaurus/" + directObject.text;<br />
Utils.openUrlInBrowser(searchUrl);<br />
}<br />
});<br />
<br />
= External links =<br />
*[https://ubiquity.mozilla.com/xpi/ubiquity-latest.xpi Ubiquity extension]<br />
*[https://wiki.mozilla.org/Labs/Ubiquity/Commands_In_The_Wild Ubiquity commands on the Mozilla wiki]<br />
*[http://sysadmin.wikia.com/wiki/Ubiquity The Ubiquity article on The Sysadmin Wiki, featuring Ubiquity commands]</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=Firefox/Ubiquity_commands&diff=77183Firefox/Ubiquity commands2009-10-04T20:07:17Z<p>Deadrabbit: Updated arch specific commands for v. 0.5+</p>
<hr />
<div>= Introduction =<br />
<br />
Due to my recent discovery of [http://labs.mozilla.com/2008/08/introducing-ubiquity/ Ubiquity] and MrGreen's suggestion on the [http://bbs.archlinux.org/viewtopic.php?pid=450773 forum], here's a place for collecting Ubiquity commands that people find of interest.<br />
<br />
= Arch Specific =<br />
'''Requires Ubiquity 0.5+'''<br />
<br />
== AUR Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["aur-packages"],<br />
icon: "http://wiki.archlinux.org/favicon.ico",<br />
description: "Search the AUR for Packages.",<br />
help: "Enter a string to search the AUR",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the Arch Bugtracker for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
var before_url = "http://aur.archlinux.org/packages.php?O=0&L=0&C=0&K=";<br />
var after_url = "&SeB=nd&SB=n&SO=a&PP=25&do_Search=Go";<br />
Utils.openUrlInBrowser(before_url + args.object.text + after_url);<br />
}<br />
}); <br />
<br />
== BBS Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["bbs-arch", "arch bbs"],<br />
icon: "http://wiki.archlinux.org/favicon.ico",<br />
description: "Search all of archlinux forums",<br />
help: "Enter a string to search the archlinux forums",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the Arch forums for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
var before_url = "http://bbs.archlinux.org/search.php?action=search&keywords=";<br />
var after_url = "&author=&forum=-1&search_in=all&sort_by=0&sort_dir=DESC&show_as=topics&search=Submit"<br />
Utils.openUrlInBrowser(before_url + args.object.text + after_url);<br />
}<br />
});<br />
<br />
== Bugtracker Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["arch-bugs"],<br />
icon: "http://wiki.archlinux.org/favicon.ico",<br />
description: "Search the Arch Bugtracker.",<br />
help: "Enter a string to search the Arch Bugtracker.",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the Arch Bugtracker for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
var before_url = "http://bugs.archlinux.org/index.php?string=";<br />
Utils.openUrlInBrowser(before_url + args.object.text);<br />
}<br />
});<br />
<br />
== Wiki Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
names: ["awiki", "arch wiki"],<br />
icon: "http://wiki.archlinux.org/favicon.ico",<br />
description: "Search all of archlinux wiki",<br />
help: "Enter a search query",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
arguments: [{role: 'object', nountype: noun_arb_text}],<br />
preview: function preview(pblock, args) {<br />
pblock.innerHTML = "Search the wiki for <b>" + args.object.html + "</b>.";<br />
},<br />
execute: function execute(args) {<br />
Utils.openUrlInBrowser("http://wiki.archlinux.org/index.php/Special:Search?search=" + args.object.text);<br />
}<br />
});<br />
<br />
= Web Lookup =<br />
'''Not updated for Ubiquity 0.5+ yet'''<br />
<br />
== Man Page Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
name: "man",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
description: "Search man pages",<br />
help: "Enter a string to search the man pages",<br />
takes: {"Search string": noun_arb_text},<br />
preview: "Search the man pages",<br />
execute: function( search_string ) {<br />
var prefix_url = "http://www.linuxmanpages.com/man1/";<br />
var after_crap_url = ".1.php"<br />
var search_url = prefix_url + search_string.text + after_crap_url;<br />
Utils.openUrlInBrowser(search_url);<br />
}<br />
})<br />
<br />
== Websters Dictionary ==<br />
<br />
CmdUtils.CreateCommand({<br />
name: "webster-dictionary",<br />
author: {name: "Timothy Sorbera", email: "tim.sorbera@gmail.com"},<br />
license: "MPL",<br />
description: "Searches Webster's Dictionary for your words.",<br />
takes: {search: noun_arb_text},<br />
preview: function(pblock, searchText) {<br />
var html = "Searches Webster's Dictionary for ";<br />
if (searchText.text) {<br />
html += searchText.text;<br />
} else {<br />
html += "your words.";<br />
}<br />
pblock.innerHTML = html;<br />
},<br />
icon: "http://www.merriam-webster.com/favicon.ico",<br />
execute: function(directObject) {<br />
var searchUrl = "http://www.merriam-webster.com/dictionary/" + directObject.text;<br />
Utils.openUrlInBrowser(searchUrl);<br />
}<br />
});<br />
<br />
== Websters Thesaurus ==<br />
<br />
CmdUtils.CreateCommand({<br />
name: "webster-thesaurus",<br />
author: {name: "Timothy Sorbera", email: "tim.sorbera@gmail.com"},<br />
license: "MPL",<br />
description: "Searches Webster's Thesaurus for your words.",<br />
takes: {search: noun_arb_text},<br />
preview: function(pblock, searchText) {<br />
var html = "Searches Webster's Thesaurus for ";<br />
if (searchText.text) {<br />
html += searchText.text;<br />
} else {<br />
html += "your words.";<br />
}<br />
pblock.innerHTML = html;<br />
},<br />
icon: "http://www.merriam-webster.com/favicon.ico",<br />
execute: function(directObject) {<br />
var searchUrl = "http://www.merriam-webster.com/thesaurus/" + directObject.text;<br />
Utils.openUrlInBrowser(searchUrl);<br />
}<br />
});<br />
<br />
== Whois Search ==<br />
<br />
CmdUtils.CreateCommand({<br />
name: "whois",<br />
contributors: ["Mr Green", "deadrabbit"],<br />
license: "MPL",<br />
description: "whois domain lookup",<br />
help: "Enter a domain to query.",<br />
takes: {"Search string": noun_arb_text},<br />
preview: "Enter a domain to query.",<br />
execute: function( search_string ) {<br />
var prefix_url = "http://reports.internic.net/cgi/whois?whois_nic=";<br />
var after_crap_url = "&type=domain"<br />
var search_url = prefix_url + search_string.text + after_crap_url;<br />
Utils.openUrlInBrowser(search_url);<br />
}<br />
})<br />
<br />
= External links =<br />
*[https://ubiquity.mozilla.com/xpi/ubiquity-latest.xpi Ubiquity extension]<br />
*[https://wiki.mozilla.org/Labs/Ubiquity/Commands_In_The_Wild Ubiquity commands on the Mozilla wiki]<br />
*[http://sysadmin.wikia.com/wiki/Ubiquity The Ubiquity article on The Sysadmin Wiki, featuring Ubiquity commands]</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=Dell_Mini_10v&diff=74833Dell Mini 10v2009-08-29T12:46:16Z<p>Deadrabbit: </p>
<hr />
<div>== Summary ==<br />
The Dell Mini 10v is a netbook from Dell. The display and wired NIC workes out of the box but the rest needs some work.<br />
<br />
== Hardware ==<br />
Audio: Realtek ALC272 (snd_hda_intel)<br />
<br />
Video: Integrated Intel 945GSE UMA Graphics Media Accelerator <br />
<br />
Wired NIC: Realtek RTL8101E/RTL8102E<br />
<br />
Wireless NIC: Broadcom Corporation BCM4312 802.11b/g<br />
<br />
Bluetooth: <br />
<br />
Webcam: <br />
<br />
== Installing ==<br />
Because the netbook has no CD-ROM drive you need to boot from a USB. See the guide [[Install_from_USB_stick]].<br />
<br />
== Xorg ==<br />
Setting up Xorg is easy on the Mini 10v. Just follow the guide for [[Xorg | Xorg]] and hal will do the rest. Becareful not to start the display manager without adding hal to the /etc/inittab and installing the touchpad driver! <br />
<br />
Kernel Mode Setting (KMS) works well on the 10v, allowing the native resolution to work at init level 3, and flickerless switching between the terminal and X sessions. See "Early Start" section in [[Intel_Graphics]] for more details.<br />
<br />
=== Touchpad ===<br />
The Mini 10v needs the synaptics driver to get the touchpad working. Read the [[synaptics]] guide to get help. The integrated buttons are difficult to use (anyone have a good xorg.conf to post here?).<br />
<br />
==Wireless==<br />
Works, except for connecting to hidden ESSIDs. See this guide: [[Broadcom_BCM4312]]<br />
<br />
== Sound ==<br />
"Just works" with OSS, or ALSA<br />
<br />
== Power ==<br />
pm-suspend from the pm-utils package works<br />
<br />
== Extras ==<br />
=== Webcam ===<br />
UVC 1.00 compatible - should work out of the box, with the latest kernel (remember to add user to video group)<br />
<br />
=== Bluetooth ===</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=Dell_Mini_10v&diff=73422Dell Mini 10v2009-08-06T18:49:11Z<p>Deadrabbit: /* Xorg */ note on KMS</p>
<hr />
<div>== Summary ==<br />
The Dell Mini 10v is a netbook from Dell. The display and wired NIC workes out of the box but the rest needs some work.<br />
<br />
== Hardware ==<br />
Audio: Realtek ALC272 (snd_hda_intel)<br />
<br />
Video: Integrated Intel 945GSE UMA Graphics Media Accelerator <br />
<br />
Wired NIC: Realtek RTL8101E/RTL8102E<br />
<br />
Wireless NIC: Broadcom Corporation BCM4312 802.11b/g<br />
<br />
Bluetooth: <br />
<br />
Webcam: <br />
<br />
== Installing ==<br />
Because the netbook has no CD-ROM drive you need to boot from a USB. See the guide [[Install_from_USB_stick]].<br />
<br />
== Xorg ==<br />
Setting up Xorg is easy on the Mini 10v. Just follow the guide for [[Xorg | Xorg]] and hal will do the rest. Becareful not to start the display manager without adding hal to the /etc/inittab and installing the touchpad driver! <br />
<br />
Kernel Mode Setting (KMS) works well on the 10v, allowing the native resolution to work at init level 3, and flickerless switching between the terminal and X sessions. See "Early Start" section in [[Intel_Graphics]] for more details.<br />
<br />
=== Touchpad ===<br />
The Mini 10v needs the synaptics driver to get the touchpad working. Read the [[synaptics]] guide to get help.<br />
<br />
==Wireless==<br />
Works, except for connecting to hidden ESSIDs. See this guide: [[Broadcom_BCM4312]]<br />
<br />
== Sound ==<br />
<br />
== Power ==<br />
<br />
== Extras ==<br />
=== Webcam ===<br />
UVC 1.00 compatible - should work out of the box, with the latest kernel (remember to add user to video group)<br />
<br />
=== Bluetooth ===</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=Dell_Mini_10v&diff=73418Dell Mini 10v2009-08-06T17:51:07Z<p>Deadrabbit: </p>
<hr />
<div>== Summary ==<br />
The Dell Mini 10v is a netbook from Dell. The display and wired NIC workes out of the box but the rest needs some work.<br />
<br />
== Hardware ==<br />
Audio: Realtek ALC272 (snd_hda_intel)<br />
<br />
Video: Integrated Intel 945GSE UMA Graphics Media Accelerator <br />
<br />
Wired NIC: Realtek RTL8101E/RTL8102E<br />
<br />
Wireless NIC: Broadcom Corporation BCM4312 802.11b/g<br />
<br />
Bluetooth: <br />
<br />
Webcam: <br />
<br />
== Installing ==<br />
Because the netbook has no CD-ROM drive you need to boot from a USB. See the guide [[Install_from_USB_stick]].<br />
<br />
== Xorg ==<br />
Setting up Xorg is easy on the Mini 10v. Just follow the guide for [[Xorg | Xorg]] and hal will do the rest. Becareful not to start the display manager without adding hal to the /etc/inittab and installing the touchpad driver! <br />
<br />
=== Touchpad ===<br />
The Mini 10v needs the synaptics driver to get the touchpad working. Read the [[synaptics]] guide to get help.<br />
<br />
==Wireless==<br />
Works, except for connecting to hidden ESSIDs. See this guide: [[Broadcom_BCM4312]]<br />
<br />
== Sound ==<br />
<br />
== Power ==<br />
<br />
== Extras ==<br />
=== Webcam ===<br />
UVC 1.00 compatible - should work out of the box, with the latest kernel (remember to add user to video group)<br />
<br />
=== Bluetooth ===</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=Dell_Mini_10v&diff=73383Dell Mini 10v2009-08-05T21:55:36Z<p>Deadrabbit: Added notes for webcam, wireless</p>
<hr />
<div>== Summary ==<br />
The Dell Mini 10v is a netbook from Dell. The display and wired NIC workes out of the box but the rest needs some work.<br />
<br />
== Hardware ==<br />
Audio: Realtek ALC272 (snd_hda_intel)<br />
<br />
Video: Integrated Intel 945GSE UMA Graphics Media Accelerator <br />
<br />
Wired NIC: Realtek RTL8101E/RTL8102E<br />
<br />
Wireless NIC: Broadcom Corporation BCM4312 802.11b/g<br />
<br />
Bluetooth: <br />
<br />
Webcam: <br />
<br />
== Installing ==<br />
Because the netbook has no CD-ROM drive you need to boot from a USB. See the guide [Install_from_USB_stick].<br />
<br />
== Xorg ==<br />
Setting up Xorg is easy on the Mini 10v. Just follow the guide for [[Xorg | Xorg]] and hal will do the rest. Becareful not to start the display manager without adding hal to the /etc/inittab and installing the touchpad driver! <br />
<br />
=== Touchpad ===<br />
The Mini 10v needs the synaptics driver to get the touchpad working. Read the [[synaptics]] guide to get help.<br />
<br />
==Wireless==<br />
Works, except for connecting to hidden ESSIDs. See this guide: [[Broadcom_BCM4312]]<br />
<br />
== Sound ==<br />
<br />
== Power ==<br />
<br />
== Extras ==<br />
=== Webcam ===<br />
UVC 1.00 compatible - should work out of the box, with the latest kernel (remember to add user to video group)<br />
<br />
=== Bluetooth ===</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=GNU_Screen&diff=54157GNU Screen2008-11-26T03:08:39Z<p>Deadrabbit: note about detaching from screen, and section on nested screen sessions</p>
<hr />
<div>[[Category:Utilities (English)]]<br />
[[Category:HOWTOs (English)]]<br />
GNU Screen is a wrapper that allows separation between the text program and the shell from which it was launched. This allows the user to, for example, start a text program in a terminal in X, kill X, and continue to interact with the program. Here are a couple of tips and tricks you may be interested in.<br />
<br />
== Basics == <br />
Commands are entered pressing Control A and then the key binding. The escape key can be changed with the ''escape'' option in ~/.screenrc. IE:<br />
<pre><br />
escape ``<br />
</pre><br />
sets the escape key to `<br />
<br />
=== Common Commands ===<br />
C-a 0<br />
:opens window 0<br />
C-a A<br />
:Rename the current window<br />
C-a c<br />
:Create a new window (with shell)<br />
C-a S<br />
:Split current region into two regions<br />
C-a <TAB> <br />
:Focus on next region<br />
C-a <ESC> <br />
:Enter Copy Mode (use enter to select a range of text)<br />
C-a ]<br />
:Paste text<br />
C-a Q<br />
:Close all regions but the current one<br />
C-a d<br />
:Detach from the current screen session, and leave it running. Use screen -r to resume<br />
<br />
== Start at window 1 ==<br />
By default, the first screen window is 0. If you'd rather never have a window 0 and start instead with 1, put something like the following in your ~/.screenrc:<br />
<pre><br />
bind c screen 1<br />
bind 0 select 10 <br />
screen 1<br />
select 1<br />
</pre><br />
<br />
== Nested Screen Sessions ==<br />
It's possible to get stuck in a nested screen session. A common scenario: you start an ssh session from within a screen session. Within the ssh session, you start screen. By default, the outer screen session that was launched first responds to C-a commands. To send a command to the inner screen session, use C-a a, followed by your command. For example:<br />
<br />
C-a a d<br />
:Detaches the inner screen session.<br />
C-a a K<br />
:Kills the inner screen session.<br />
<br />
== Fix for residual editor text ==<br />
When you open a text editor like nano in screen and then close it, the text may stay visible in your terminal. To fix this, put the following in your ~/.screenrc:<br />
<pre><br />
altscreen on<br />
</pre><br />
<br />
== Use 256 colors ==<br />
By default, screen uses an 8-color terminal emulator. Use the following line to enable more colors, which is useful if you are using a more-capable terminal emulator:<br />
<pre><br />
term screen-256color<br />
</pre><br />
<br />
== Use 256 Colors with Rxvt-Unicode (urxvt) ==<br />
If you are using rxvt-unicode-256color from the AUR you may need to add this line in your ~/.screenrc to enable 256 colors while in screen.<br />
<pre><br />
terminfo rxvt-unicode 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'<br />
</pre><br />
<br />
== Informative statusbar ==<br />
The default statusbar may be a little lacking. You may find this one more helpful:<br />
<pre><br />
hardstatus off<br />
hardstatus alwayslastline<br />
hardstatus string '%{= kG}[ %{G}%H %{g}][%= %{= kw}%?%-Lw%?%{r}(%{W}%n*%f%t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}][%{B} %m-%d %{W}%c %{g}]'<br />
</pre><br />
<br />
== Turn welcome message off == <br />
Cause it's annoying. Add to ~/.screenrc:<br />
<pre><br />
startup_message off<br />
</pre><br />
<br />
==Add a GRUB entry to boot into Screen==<br />
If you mostly use X but occasionally want to run a Screen-as-window-manager session, here's one way to do it by adding a GRUB entry for Screen on a virtual console (text terminal). <br />
<br />
GRUB allows you to designate what runlevel you want so we'll use runlevel 4 for this purpose. Clone an appropriate GRUB entry and add a '4' to the kernel boot parameters list, like so:<br />
<br />
<pre><br />
# (0) Arch Linux<br />
title Arch Linux Screen<br />
root (hd0,2)<br />
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/a29113d7-2204-49e9-be69-d94699eba466 ro acpi_no_auto_ssdt irqpoll 4<br />
initrd /boot/kernel26.img<br />
</pre><br />
<br />
Add some entries to /etc/inittab to indicate what should happen on runlevel 4, substituting your user name for <user>:<br />
<pre><br />
# gnu screen on rl4<br />
scr2:4:respawn:/sbin/mingetty --autologin <user> vc/1 linux<br />
</pre><br />
The line uses mingetty to [[automatically login some user to a virtual console on startup]]. You will need to install the [http://aur.archlinux.org/packages.php?ID=13793 mingetty package] (AUR). The inittab line segments are separated by colons. The first part (scr*) is simply an id. The second part is the runlevel: This should only happen on runlevel 4 (which isn't used in any default setup - 3 is by default for a tty login and 5 is for X). 'Respawn' causes init to repeat the command (i.e. autologin) if the user logs out. <br />
We'll need to see that nothing else happens on virtual console 1 when we use runlevel 4, so remove '4' from the the first of the agetty lines:<br />
<br />
<pre>c1:235:respawn:/sbin/agetty -8 38400 vc/1 linux</pre><br />
<br />
Once logged in we want to ensure that screen is started. Add the follwoing to the end of your .bashrc:<br />
<pre><br />
rl=$(runlevel | grep -o [0-9])<br />
case $rl in<br />
4) TERM=screen; exec /usr/bin/screen;;<br />
esac<br />
</pre><br />
This checks for the current runlevel and will launch a screen session immediately after the autologin if the runlevel is 4.<br />
<br />
This can also be adapted to run screen on a virtual console next to X, simply checking for the current tty instead of the current runlevel. This check to see if we're on virtual console 3:<br />
<pre><br />
vico="$(tty | grep -oE ....$)"<br />
case "$vico" in<br />
vc/3) TERM=screen; exec /usr/bin/screen;;<br />
esac<br />
</pre><br />
Set inittab/mingetty to automaically log in to vc/3 on runlevel 5 and you're set.<br />
<br />
== See Also ==<br />
* [http://www.macosxhints.com/article.php?story=20021114055617124 MacOSX Hints - Automatically using Screen in your shell]<br />
* [http://gentoo-wiki.com/TIP_Using_screen#Tab-bar GentooWiki - Using tabs with Screen]<br />
* [http://bbs.archlinux.org/viewtopic.php?id=50647 Arch-Forum Thread regarding 256 color screen + urxvt]</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=GNU_Screen&diff=54156GNU Screen2008-11-26T02:58:34Z<p>Deadrabbit: /* Common Commands */</p>
<hr />
<div>[[Category:Utilities (English)]]<br />
[[Category:HOWTOs (English)]]<br />
GNU Screen is a wrapper that allows separation between the text program and the shell from which it was launched. This allows the user to, for example, start a text program in a terminal in X, kill X, and continue to interact with the program. Here are a couple of tips and tricks you may be interested in.<br />
<br />
== Basics == <br />
Commands are entered pressing Control A and then the key binding. The escape key can be changed with the ''escape'' option in ~/.screenrc. IE:<br />
<pre><br />
escape ``<br />
</pre><br />
sets the escape key to `<br />
<br />
=== Common Commands ===<br />
C-a 0<br />
:opens window 0<br />
C-a A<br />
:Rename the current window<br />
C-a c<br />
:Create a new window (with shell)<br />
C-a S<br />
:Split current region into two regions<br />
C-a <TAB> <br />
:Focus on next region<br />
C-a <ESC> <br />
:Enter Copy Mode (use enter to select a range of text)<br />
C-a ]<br />
:Paste text<br />
C-a Q<br />
:Close all regions but the current one<br />
C-a d<br />
:Detach from the current screen session, and leave it running. Use screen -r to resume<br />
<br />
== Start at window 1 ==<br />
By default, the first screen window is 0. If you'd rather never have a window 0 and start instead with 1, put something like the following in your ~/.screenrc:<br />
<pre><br />
bind c screen 1<br />
bind 0 select 10 <br />
screen 1<br />
select 1<br />
</pre><br />
<br />
== Fix for residual editor text ==<br />
When you open a text editor like nano in screen and then close it, the text may stay visible in your terminal. To fix this, put the following in your ~/.screenrc:<br />
<pre><br />
altscreen on<br />
</pre><br />
<br />
== Use 256 colors ==<br />
By default, screen uses an 8-color terminal emulator. Use the following line to enable more colors, which is useful if you are using a more-capable terminal emulator:<br />
<pre><br />
term screen-256color<br />
</pre><br />
<br />
== Use 256 Colors with Rxvt-Unicode (urxvt) ==<br />
If you are using rxvt-unicode-256color from the AUR you may need to add this line in your ~/.screenrc to enable 256 colors while in screen.<br />
<pre><br />
terminfo rxvt-unicode 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'<br />
</pre><br />
<br />
== Informative statusbar ==<br />
The default statusbar may be a little lacking. You may find this one more helpful:<br />
<pre><br />
hardstatus off<br />
hardstatus alwayslastline<br />
hardstatus string '%{= kG}[ %{G}%H %{g}][%= %{= kw}%?%-Lw%?%{r}(%{W}%n*%f%t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}][%{B} %m-%d %{W}%c %{g}]'<br />
</pre><br />
<br />
== Turn welcome message off == <br />
Cause it's annoying. Add to ~/.screenrc:<br />
<pre><br />
startup_message off<br />
</pre><br />
<br />
==Add a GRUB entry to boot into Screen==<br />
If you mostly use X but occasionally want to run a Screen-as-window-manager session, here's one way to do it by adding a GRUB entry for Screen on a virtual console (text terminal). <br />
<br />
GRUB allows you to designate what runlevel you want so we'll use runlevel 4 for this purpose. Clone an appropriate GRUB entry and add a '4' to the kernel boot parameters list, like so:<br />
<br />
<pre><br />
# (0) Arch Linux<br />
title Arch Linux Screen<br />
root (hd0,2)<br />
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/a29113d7-2204-49e9-be69-d94699eba466 ro acpi_no_auto_ssdt irqpoll 4<br />
initrd /boot/kernel26.img<br />
</pre><br />
<br />
Add some entries to /etc/inittab to indicate what should happen on runlevel 4, substituting your user name for <user>:<br />
<pre><br />
# gnu screen on rl4<br />
scr2:4:respawn:/sbin/mingetty --autologin <user> vc/1 linux<br />
</pre><br />
The line uses mingetty to [[automatically login some user to a virtual console on startup]]. You will need to install the [http://aur.archlinux.org/packages.php?ID=13793 mingetty package] (AUR). The inittab line segments are separated by colons. The first part (scr*) is simply an id. The second part is the runlevel: This should only happen on runlevel 4 (which isn't used in any default setup - 3 is by default for a tty login and 5 is for X). 'Respawn' causes init to repeat the command (i.e. autologin) if the user logs out. <br />
We'll need to see that nothing else happens on virtual console 1 when we use runlevel 4, so remove '4' from the the first of the agetty lines:<br />
<br />
<pre>c1:235:respawn:/sbin/agetty -8 38400 vc/1 linux</pre><br />
<br />
Once logged in we want to ensure that screen is started. Add the follwoing to the end of your .bashrc:<br />
<pre><br />
rl=$(runlevel | grep -o [0-9])<br />
case $rl in<br />
4) TERM=screen; exec /usr/bin/screen;;<br />
esac<br />
</pre><br />
This checks for the current runlevel and will launch a screen session immediately after the autologin if the runlevel is 4.<br />
<br />
This can also be adapted to run screen on a virtual console next to X, simply checking for the current tty instead of the current runlevel. This check to see if we're on virtual console 3:<br />
<pre><br />
vico="$(tty | grep -oE ....$)"<br />
case "$vico" in<br />
vc/3) TERM=screen; exec /usr/bin/screen;;<br />
esac<br />
</pre><br />
Set inittab/mingetty to automaically log in to vc/3 on runlevel 5 and you're set.<br />
<br />
== See Also ==<br />
* [http://www.macosxhints.com/article.php?story=20021114055617124 MacOSX Hints - Automatically using Screen in your shell]<br />
* [http://gentoo-wiki.com/TIP_Using_screen#Tab-bar GentooWiki - Using tabs with Screen]<br />
* [http://bbs.archlinux.org/viewtopic.php?id=50647 Arch-Forum Thread regarding 256 color screen + urxvt]</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=Festival&diff=52538Festival2008-11-03T02:55:09Z<p>Deadrabbit: I changed this from the Ubuntu style copy&paste-mysterious-commands to Arch style intelligent conf file editing :)</p>
<hr />
<div>{{stub}}<br />
=Introduction=<br />
[http://www.cstr.ed.ac.uk/projects/festival/ Festival] is a general multi-lingual speech synthesis system developed at CSTR ([http://www.cstr.ed.ac.uk/ Centre for Speech Technology Research]).<br />
<br />
=Step 1: Installation=<br />
Festival is in the extra repository so:<br />
# pacman -S festival<br />
<br />
You will also need to install one or more voices because by default there is no voice to speak with.<br />
<br />
=Step 2: Add voices=<br />
==American English==<br />
American English male voice `kal' 16kHz version:<br />
# pacman -S festival-kallpc16k<br />
==British English==<br />
British English male voice `rab' 16kHz version:<br />
# pacman -S festival-rablpc16k<br />
==Other voices==<br />
Other voices are available for Festival, some of them can be found in [[AUR]].<br />
<br />
=Step 3: Testing and debugging=<br />
To test festival lets make it speak an example text:<br />
$ echo "This is an example. Seems like I'm working fine."|festival --tts<br />
If your hear all the example text below: congratulations, you just installed a TTS system.<br />
<br />
If you don't hear anything or just the beginning of the example sentence continue below.<br />
<br />
==Debugging==<br />
If festival returns the following error message:<br />
Linux: can't open /dev/dsp<br />
<br />
Switch to ALSA output by adding these lines to the end of your .festivalrc file, or to /usr/share/festival/festival.scm ([http://ubuntuforums.org/showpost.php?p=4058268&postcount=16 source]):<br />
(Parameter.set 'Audio_Method 'Audio_Command)<br />
(Parameter.set 'Audio_Command "aplay -q -c 1 -t raw -f s16 -r $SR $FILE")</div>Deadrabbithttps://wiki.archlinux.org/index.php?title=Arch_compared_to_other_distributions&diff=39432Arch compared to other distributions2008-04-01T01:10:15Z<p>Deadrabbit: /* Arch vs Sorcerer/Lunar-linux/Sourcemage */</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:General (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|Deutsch|Arch im Vergleich mit anderen Distributionen}}<br />
{{i18n_entry|English|Arch Compared To Other Distros}}<br />
{{i18n_entry|Español|Arch Comparada con Otras Distribuciones}}<br />
{{i18n_entry|Français|Arch Comparée Aux Autres Distros}}<br />
{{i18n_entry|Italiano|Arch e le altre distribuzioni}}<br />
{{i18n_entry|Nederlands|Arch in vergelijking met andere distributies}}<br />
{{i18n_entry|Português do Brasil|Arch_x_Outras(Português_do_Brasil)}}<br />
{{i18n_entry|Slovensky|Arch vs Ostatné distribúcie}}<br />
{{i18n_entry|Polski|Porownanie Archa z innymi dystrybucjami}}<br />
{{i18n_entry|Česky|Arch_vs_ostatní_linuxové_distribuce (Česky)}}<br />
{{i18n_entry|简体中文|Arch 与其他发行版的比较}}<br />
{{i18n_entry|Русский|Arch и другие}}<br />
{{i18n_entry|ไทย|ข้อแตกต่างระหว่าง Arch กับ Distro อื่นๆ}}<br />
{{i18n_links_end}}<br />
<br />
This page summarizes some of the similarities and differences between Arch and other GNU/Linux distributions/<code>UNIX</code>-like operating systems. Please note that the best way to compare Arch to other distributions is to install it and try it yourself. Arch has a wonderful user community that is always willing to help new users. The summaries below are meant only to give you enough information to decide if Arch is really for you.<br />
<br />
==Arch vs Gentoo==<br />
Because the Arch installation is binary, it is much less time-consuming than the source-based Gentoo installation. Both Gentoo and Arch allow binary and source-based packaging; however, the Gentoo base system is source-based while Arch's is binary. Both are rolling-release systems. Arch PKGBUILDs are widely perceived as easier and more expedient to create than Gentoo ebuilds. Gentoo offers support for x86, ppc, sparc, alpha, amd64, mips, hppa, and itanium, whereas Arch offers i686 and x86-64 only (although an i586 user-based spin-off project is underway). There is no documented proof that Gentoo is any faster than Arch or vice-versa. The Arch design approach is more focused on simplicity and minimalism, whereas Gentoo focuses more on the ability to globally control each aspect of source compilation. Both distros allow for a very high level of customization, therefore, Gentoo users will generally feel quite comfortable with most aspects of Arch.<br />
<br />
==Arch vs Crux==<br />
Arch Linux was inspired by Crux. Judd once summarized the differences:<br />
:&quot;I used Crux before starting Arch. Arch started out as Crux, pretty much. Then I wrote pacman and makepkg to replace my bash pseudo packaging scripts (I built Arch as an LFS system to begin). So the two are completely separate distros, but technically, they're almost the same. We have dependency support (officially) for example, although Crux has a community that provides other features. CLC's prt-get will do rudimentary dependency logic. Crux gets to ignore lots of problems we have too, since it's a very minimalistic package set, basically what Per uses and nothing else.&quot;<br />
<br />
See [http://bbs.archlinux.org/viewtopic.php?pid=133721#p133721 this forum post] for a user's impressions of both distributions.<br />
<br />
==Arch vs Sorcerer/Lunar-linux/Sourcemage==<br />
Sorcerer/Lunar-linux/Sourcemage (SLS) are all source-based distros, much like Gentoo is, but are originally related to one another. SLS distros use a rather simple set of script files to create package descriptions, and use a global configuration file to configure the compilation process, much like Arch's ABS system. The SLS tools do full dependency checking (including handling optional features) and package tracking (and uninstalling/upgrading). There are no binary packages for any of the SLS family, although they all can roll back earlier installed packages easily.<br />
<br />
The install involves installing a base system (much like Arch's: i686-optimized, CLI and ncurses menus, only core tools), then recompiling the base system (optionally) afterwards. There is obviously no &quot;standard&quot; WM/DE/DM, and they do not install an X server during the base installation. But they do provide you with an easy way of installing one of several X server alternatives (X.Org 6.8 or 7, XFree86).<br />
<br />
SLS has a very complicated history. The best write-up about it can be found here: http://wiki.sourcemage.org/SourceMage/History<br />
<br />
Lunar Linux: http://lunar-linux.org/ <br><br />
SourceMage: http://www.sourcemage.org/ <br><br />
Sorcerer: http://sorcerer.berlios.de/<br />
<br />
==Arch vs Rock==<br />
''From Introduction http://www.rocklinux.org/wiki/About''<br />
<br />
ROCK Linux is a flexible Linux Distribution Build Kit, i.e. it is a toolchain/framework for making your own Linux distributions. See also our Mission Statement.<br />
If you don't want to build your own distribution but simply are interested in a good general-purpose distribution, you might want to have a look at Crystal ROCK. http://www.rocklinux.org/wiki/Crystal_ROCK<br />
<br />
A distro based on being a build tool. VS Arch; again same issues as source based with time to compile, etc. Seems to work on many processors like SPARC, ARM, etc.<br />
<br />
==Arch vs Slackware==<br />
Slackware and Arch are quite similar in that both are simple distributions focused on elegance and minimalism. Both use BSD-style init scripts. Arch supplies a package management system in pacman which, unlike Slackware's standard tools, offers automatic dependency resolution and allows for easy system upgrades. Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them. Arch is a rolling-release system. Slackware is seen as more conservative in its release cycle, preferring proven stable packages. Arch is more 'bleeding edge' in this respect. Arch is i686 and x86_64 whereas Slackware can run on i486 systems. Both have a ports-like system available in addition to their regular package managers- the (unofficial) Slackbuild system is very similar to the Arch Build System (ABS), the latter being slightly more automated. Arch is a very good system for Slack users who want package management with automatic dependency resolution and/or more current packages.<br />
<br />
==Arch vs Debian GNU/Linux==<br />
Debian is a much larger project and community and features stable, testing, and unstable branches, offering over 18,000 binary packages. Arch does not 'split' their packages into -dev and -common as Debian does, therefore, Arch repositories will seem much smaller. Arch is more lenient when it comes to 'non-free' packages as defined by GNU. Debian's design approach focuses more on stability and stringent testing. Arch is focused more on the philosophy of simplicity and offering bleeding edge software. Arch packages are more current than Debian Stable and Testing, being about equal with Debian unstable. Both have excellent package management systems. Arch is a rolling release, whereas Debian Stable is released with "frozen" packages. Debian is available for many architectures, including alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, and sparc, whereas Arch is i686 and x86_64 only. Arch provides more expedient support for building your own packages and also offers a ports-like system. The Arch installation is designed as a minimal base, transparently exposed during system configuration, whereas Debian's method offers a more automatically configured approach.<br />
<br />
==Arch vs Graphical Distros==<br />
The graphical distros have a lot of similarities, and Arch is very different from any of them. Arch is text-based and command-line oriented. Arch may be a better choice if you want to learn about GNU/Linux by building up from a very minimal base. Graphical distros tend to ship with GUI installers (like Fedora's Anaconda) and GUI system-configuration tools (like SuSE's YaST). Specific differences between distros are described below.<br />
<br />
==Arch vs Ubuntu==<br />
Ubuntu is an immensely popular Debian-based distro commercially sponsored by Canonical Ltd., while Arch is an indepedently developed system built from scratch. Arch has a simpler foundation than Ubuntu. If you like to compile your own kernels, try out bleeding-edge CVS-only projects, or build a program from source every once in a while, Arch is better suited. If you want to get up and running quickly and not fiddle around with the guts of the system, Ubuntu is better suited. Arch is presented as a much more minimalist design from the installation onward, relying on the user to customize it to their own specific needs. In general, developers and tinkerers will probably like Arch better than Ubuntu, though many Arch users claim to have started on Ubuntu and eventually migrated to Arch.<br />
<br />
==Arch vs Zenwalk==<br />
Zenwalk is derived from Slackware and is convenient and modern. A major difference is that Zenwalk installs the packages the developers have chosen for you. That saves time if you like their choices but, at the same time, is a disadvantage in case you want to use something else.<br />
<br />
==Arch vs Fedora==<br />
Fedora is a spin-off from the Red Hat distribution and has continually been one of the most popular distributions to date. As such, there is a massive community and lots of pre-built packages and support available. Fedora is RPM-based. Arch uses pacman to manage tar.gz packages. Fedora famously doesn't attempt to support the MP3 media format due to perceived patent issues. Arch is more lenient in its disposition toward MP3 and other media. Fedora uses a graphical install. Arch uses an ncurses-based install. Fedora is very GUI-driven. Arch is a much simpler system than Fedora, relying on the user for manual configuration. Fedora has a scheduled release cycle. Arch is a rolling-release system. The Arch design approach is geared more toward lightweight elegance and minimalism rather than automation/autoconfiguration. Fedora does innovate and recently earned kudos for integration of SELinux and GCJ compiled packages to remove the need for Sun's JRE.<br />
<br />
==Arch vs Mandriva==<br />
Mandriva Linux (formerly Mandrakelinux) was created in 1998 with the goal of making GNU/Linux easy to use for everyone. It is RPM-based and uses the urpmi package manager. Again, Arch takes a simpler approach, relying on more manual configuration and is aimed a bit more toward intermediate to advanced users.<br />
<br />
==Arch vs SUSE==<br />
SUSE is centered around its well-regarded YaST configuration tool, which is a one-stop shop for most users' configuration needs. Arch doesn't offer such a facility as it goes against [[TheArchWay]]. SUSE, therefore, is widely regarded as more appropriate for less-experienced users, or those who want a more GUI-driven environment, autoconfiguration and expected functionality out of the box.<br />
<br />
==Arch vs PCLinuxOS==<br />
PCLinuxOS is an extremely popular Mandriva-based distro providing a complete DE (KDE), designed for user-friendliness. Arch is designed as a simple base system to be customized from the ground up and is aimed more toward advanced users. PCLOS uses the apt package manager as a wrapper for RPM packages. Arch uses its own independently developed pacman package manager with .tar.gz packages. PCLOS is very GUI-driven and provides GUI hardware configuration tools and the Synaptic package management front end. Arch is command line oriented and designed for more simple approaches to system configuration, management and maintenance. PCLOS recommends 256MB RAM as part of its minimum system requirements. Being more lightweight, Arch can run on systems with much less system memory, requiring only 64MB of RAM for a base i686 install, and will run flawlessly on more modern systems.<br />
<br />
==Arch vs Frugalware==<br />
Arch is text-based and command-line oriented. Frugalware provides better multilingual support. Frugalware has adopted Arch's pacman as its package manager, though their packages are not really very compatible. Frugalware doesn't support the JFS file-system by default. Frugalware is no longer based on Slackware but is rather a distro of its own, and is promoted as an i686 distro. Arch is a fundamentally different system, being installed as a minimal base environment and expanded with pacman according to the user's choices and needs. Frugalware is installed from a DVD, with default software choices and desktop environment chosen for the user already. Frugalware has a scheduled release cycle. Again, Arch is more focused on simplicity, minimalism and bleeding edge packages within a rolling release model.<br />
<br />
==Arch vs FreeBSD==<br />
Arch is perhaps more similar to the *BSD's, from a design overview, than to other GNU/Linux distros. The BSDs derive from Berkeley <code>UNIX</code>. [http://www.freebsd.org/about.html FreeBSD] therefore is not a GNU/Linux distro, but rather, a <code>UNIX</code>-like OS. Both Arch and FreeBSD offer software which can be obtained using binaries or compiled using 'ports' systems. Both share a very similar init system. FreeBSD boasts that it is more of a system designed as a whole, compared to GNU/Linux distros, with each app 'ported' over to FreeBSD and made sure to work in the process. Arch is focused more toward releasing bleeding edge software in this regard. Both use /etc/rc.conf as a main configuration file. The FreeBSD license is more of a free-as-in-beer license than some GNU/Linux users prefer. Arch is released under the GPL. In FreeBSD, like Arch, decisions are delegated to you, the power user. This may be the most interesting competitor to Arch since it goes head-to-head in package modernity and has a somewhat sizable, smart, active, no-nonsense community. Both systems share many similarities and FreeBSD users will generally feel quite comfortable with most aspects of Arch.<br />
<br />
==Arch vs NetBSD==<br />
NetBSD is a free, secure, and highly portable <code>UNIX</code>-like open-source operating system available for many platforms, from 64-bit Opteron machines and desktop systems to handheld and embedded devices. Its clean design and advanced features make it excellent in both production and research environments, and it is user-supported with complete source. Many applications are easily available through pkgsrc, the NetBSD Packages Collection. Arch may not operate on the vast number of devices NetBSD operates on, but for an i686 system it may offer more apps. Also, the default installation method in pkgsrc is to pull and compile sources whereas Arch offers binary packages.<br />
<br />
==Arch vs OpenBSD==<br />
The OpenBSD project produces a free, multi-platform 4.4BSD-based <code>UNIX</code>-like operating system. Efforts focus on portability, standardization, code correctness, proactive security, and integrated cryptography. In contrast, Arch focuses on simplicity, elegance, minimalism and bleeding edge software. OpenBSD supports binary emulation of most programs from SVR4 (Solaris), FreeBSD, GNU/Linux, BSD/OS, SunOS and HP-UX. OpenBSD is perhaps the #1 security OS. <br />
In common with Arch, OpenBSD offers a small, elegant, base install and uses a ports system and packaging systems to allow for easy installation and management of programs which are not part of the base operating system. In contrast to a GNU/Linux system like Arch, but in common with most other BSD-based operating systems, the OpenBSD kernel and userland programs, such as the shell and common tools like cat and ps, are developed together in a single source repository.<br />
<br />
==Arch vs Gobolinux==<br />
Gobolinux has a unique package system in that it has none. The file system is reorganized so that apps all sit in a /Programs directory, and it works using some symlink magic. Get rid of Program X by rm -rf /Programs/X http://www.gobolinux.org/index.php?page=at_a_glance<br />
It does not seem to focus on i686 binaries and does allow source-based package installs.<br />
<br />
==Arch vs Minix 3==<br />
Arch is a complete distro with a modern community and hardware support. Minix 3 is a slim, usable advanced-research OS with some interesting features, e.g. the use of a [http://en.wikipedia.org/wiki/Microkernel microkernel]. http://www.minix3.org/</div>Deadrabbit