Talk:Chroot

Recommends adding support reference
Recommends adding support reference on IRC, Discord, etc.. for user to ask question and get answers and to encourage them to not be afraid to ask "stupid questions", based on experience on discord ppl are scared to ask which usually results in bad decision. If user is encouraged to ask stupid questions he/she will which makes is for the user to better understand how gentoo works and how to use it properly. Kreyren (talk) 11:42, 28 August 2018 (UTC)

Discussion here:

--- Kreyren (talk) 11:45, 28 August 2018 (UTC)

Adding support thread to  might be efficient enough to display all available resources to get support. (Template:InfoBox_stack)

--Maffblaster (talk) 22:49, 28 August 2018 (UTC)

We clearly list areas for support on the main website and on the Main Page of the wiki. Seems clear enough to me. The wiki isn't a place to receive support, it's a place to read documentation, make improvements to existing docs, etc. Please see Gentoo Wiki:Contributor's guide for more details on the design goals for the wiki.

I should mention, Discord is not a place for our users to receive any kind of 'official' support for Gentoo. If you're willing to help users who choose closed-source medium of communication then so be it, however it's not a great idea to start advertising closed source software among the primary venues for support. We have the official Forms, the mailing lists, and IRC (which is open source) as our primary areas of support.

--Kreyren (talk) 03:57, 29 August 2018 (UTC)

Noted, but you need to understand that the installation of Gentoo Linux is very flustrating and seemingly impossible for new users and they are often unable to find resources for support even when they are provided on wiki (based on experience on discord and my personal experience). I believe that mensioning support resources at least on handbook pages would greately increase the effectivness of gentoo wiki. Please note that based on my research most of potential new users try to install gentoo, fail multiple times and leave on another distro with anger (i would probably left on debian if i waren't perfectionist.. Spend up to 2 months just with the installation..). About Discord it's partially open-source and mostly used by new users which is the main and only reason for me to use it for gentoo linux. There are almost 200 users and half of them come to gentoo as new users in about one month. I strongly believe that if it was supported officialy it would have positive impact on the community itself. Ideally if Discord, Zulip, Slack and IRC were linked together using bots so that one message could be synced between all those platforms seamlessly resulting in providing the best support possible on all those platforms. I understand that most of the Gentoo devs hate it, but this hate should be overcome for the greater good of community. You're on Discord now too just read some messages if this didn't convince you..


 * This discussion is clearly finished. --Davidbryant (talk) 18:14, 9 August 2020 (UTC)

Recommends adding 2x spacing between each section
Recommends adding 2x between each section. Based on my experience it makes it easier to read the content and understand it. Kreyren (talk) 11:39, 28 August 2018 (UTC)

Discussion here:

We try to avoid adding direct HTML formatting into our wiki text pages. is an HTML element that can be emulated by using two new line white spaces in wiki markup. Please read up on this specific question here Gentoo_Wiki:Guidelines. Also please read up on all the links you noted yesterday when you received translations privileges. You've been not following the wiki formatting Guidelines. I appreciate your enthusiasm, but please be cautious of these guidelines before making edits so that you don't generate unnecessary formatting clean up work... -- Maffblaster (talk) 22:32, 28 August 2018 (UTC)

should be the most effective solution or you might want to edit source code of wiki to make this kind of spacing? --Kreyren (talk) 03:41, 29 August 2018 (UTC)
 * I wasn't able to emulate it using two new lines since it won't recognize them.. Also editors might remove those lines on edit which might be counter-productive.. The usage of

My point here is that the Guidelines state "There should be an empty line above and below section headings and around any paragraph-breaking (not inline) templates. This improves readability by editors (wiki syntax) and simplifies the translation effort used by the community." It also states the use of is to be avoided. The same effect can be obtained with empty/new lines (see the double empty I added between our posts above to prove the point)...

That said, I would disagree with your premise: I do not agree that double empty lines between sections are easier to read. I much like the single empty line approach and would stress the point that single spaces between paragraphs is how HTML was designed to be formatted (wiki markup converts these sections into  tags. This is the way upstream Wikipedia does formatting. Anyone else want to weigh in? ? ? ?

If you want standard paragraphs to be different in appearance you can probably figure out a solution to this problem. Perhaps a browser plugin will reformat the web to your liking?

I'll also point out that this would be the only article with which I am aware that would use double empty line spacing between sections. I believe double empty lines would interfere with translation efforts due to the way our translation plugin works. It uses empty lines to mark/divide new sections for translations. If you really wanted to make this a site-wide change this discussion should be moved to the Gentoo_Wiki_talk:Guidelines, as they govern side-wide changes...

You seem to be eager to contribute, but you're suggesting to change a lot of paradigms that have been already been discussed, decided, and documented. I encourage you to actually through through the Guidelines and other documents that were provided above. These should give you an idea of why things are the way they are here on the wiki. I'm not trying to push you away, but I also cannot continue to spend much time asking you read our docs before trying to change things. Hopefully this makes sense. Asking more questions before suggesting such changes would be beneficial.

Lastly, the general formatting of discussions across the wiki is to indent the replies to the original discussion. Although free-form is technically possible, keeping a consistency for discussions is preferred and suggested as other wiki contributors are already used to this format. I have revised this discussion to match typical discussion format. =) --Maffblaster (talk) 17:23, 30 August 2018 (UTC)


 * 640kbr ought to be enough for anybody. --Cronolio (talk) 06:14, 31 August 2018 (UTC)

Maffblaster, my time is also limited. Can't we discuss this on Discord/IRC rather then writing long messages in discussion? I believe that it would be much more effective to find the most effective solution this way. About Gentoo docs i read them before contributing to a gentoo wiki and my actions are based on gathered informations from those documents.

Based on my research i understand that having two spacing under each section improve overall readability and is much easier for an end-user to read and understand, but i respect your decision. --Kreyren (talk) 13:35, 3 September 2018 (UTC)

Adding a image for a article
I made this simple image for this article, i hope that it make it easier for ppl to grasp what chroot means. Requesting approval, not sure how to add it by myself.. Kreyren (talk) 11:36, 28 August 2018 (UTC)

Discussion here:

I suggest using the Gentoo purple in the image instead of the red text and putting the image in the InfoBox stack. Export SVG if you're able. Close discussion when you've done the work. --Maffblaster (talk) 22:35, 28 August 2018 (UTC)


 * I tried to locate the artwork, but it has been removed from the wiki. Nothing much left to talk about imo. --Davidbryant (talk) 18:17, 9 August 2020 (UTC)

Problem at translation time
The breaking of the initialisation scripts at the end creates a problem at the time of translating. The system refuses to register the last part complaining about the odd number of parentheses. This obliges to group everything in the first part and to place a dash in the other ones.

Unnecessary separation of msgid into each group should be revoked for the /etc/init.d/mychroot file description box. please remove comments from to --Darkcircle(talk)


 * Looks like now all is working --Cronolio (talk) 19:46, 1 June 2017 (UTC)

link incorrect http://distfiles.gentoo.org/releases/amd64/current-iso/
in section Unpacking system files and the Portage tree (new installations) link http://distfiles.gentoo.org/releases/amd64/current-iso/ ->404

--Jms (talk) 22:44, 24 October 2016 (UTC)


 * Done --Cronolio (talk) 19:46, 1 June 2017 (UTC)

Please clarify about mounting
I do not understand why I need this - only for access my host files from the chroot jail?

And also mount is only for root user, so looks like this Wiki template should be changed. Vitaly-zdanevich (talk) 00:32, 28 February 2021 (UTC)

mount: /proc: must be superuser to use mount.
Got this error when tried emerge inside choot. Also `Unable to mark /proc slave: 32`

Vitaly-zdanevich (talk) 02:57, 28 February 2021 (UTC)