::wait wait a second http://www.funtoo.org/Special:RecentChanges <--- can u make bigger changes, like adding content, and try avoid spamming this plz. i hate it when i screw up, and notice it immediately after a commit because of this. im just making sure you're aware that you're massively spamming logs. [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) 23:47, 22 September 2014 (UTC)

+

Essa é uma básica visão geral do processo de instalação do Funtoo:

−

I am sorry if I have caused you any inconvenience. However, I am adding all Templates on the wiki to a Category:Template. Because of this, I have to add [[Category:Template]] to each Template -- hence the spamming of the log. Is it okay with you if I finish up (I will then be done spamming, I promise.)?

Duncan, it is not really that helpful to add Templates to a Template category. They are all in their own namespace and it is easy to find them using this link: http://www.funtoo.org/index.php?title=Special%3AAllPages&from=&to=&namespace=10

I did not know about this namespaces tool. Should I remove all of the templates from that category that I created?

+

http://www.sysresccd.org/Download

−

Yeah, probably. In MediaWiki, generally any "Foo:" (with colon) prefix means it's in a separate namespace. This means it's easy to find all pages in a namespace using the All Pages link. Also note that you did this wrong. If you look at all the pages in [[:Category:Templates]], you'll notice that all the packages are in there. If you want to add a template to a category, but not the page that it's used on, then you need to put the category tag inside a <noinclude> </noinclude> section. That section will only apply to the template itself.

Moreover, this causes any page using a template to be in the template category as <code>[[Category:Template]]</code> is included in the source code of the page. By the way, I wonder if this is a good behavior. Indeed, you can't link to a category without including the page in this category. -- [[User:Pytony|Pytony]] ([[User talk:Pytony|talk]])

One of the interfaces should have an IP address (listed as <code>inet addr:</code>) from your LAN. You can then connect remotely, from another system on your LAN, to System Rescue CD, and perform steps from the comfort of an existing OS. On your remote system, type the following, replacing <code>1.2.3.4</code> with the IP address of System Rescue CD. Connecting from an existing Linux or MacOS system would look something like this:

+

+

<console>

+

(remote system) $ ##i##ssh root@1.2.3.4

+

Password: ##i##**********

+

</console>

+

+

{{Note|If you'd like to connect remotely from an existing Microsoft Windows system, you'll need to download an SSH client for Windows, such as [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY].}}

+

+

After you've logged in via SSH, you're now connected remotely to System Rescue CD and can perform the installation steps.

Revision as of 13:54, January 20, 2015

Note

This is a template that is used as part of the Installation instructions which covers: uma visão geral inicial do processo de instalação, tão em quanto instruções de download do LiveCD e de boot. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.

One of the interfaces should have an IP address (listed as inet addr:) from your LAN. You can then connect remotely, from another system on your LAN, to System Rescue CD, and perform steps from the comfort of an existing OS. On your remote system, type the following, replacing 1.2.3.4 with the IP address of System Rescue CD. Connecting from an existing Linux or MacOS system would look something like this:

(remote system) $ ssh root@1.2.3.4
Password: **********

Note

If you'd like to connect remotely from an existing Microsoft Windows system, you'll need to download an SSH client for Windows, such as PuTTY.

After you've logged in via SSH, you're now connected remotely to System Rescue CD and can perform the installation steps.