At Gentoo/Linux to localize my system i have to config keymaps and consolefont services (/etc/conf.d/consolefont and /etc/conf.d/keymaps) and select locale with "eselect locale set x". At FreeBSD there are options in /etc/rc.conf. Gentoo/FreeBSD's /etc/rc.conf is openrc's one, not FreeBSD, and there is no keymaps and consolefont services. But I was able to localize system for russian with following commands: eselect locale set 229 . /etc/profile vidcontrol -f koi8-r kbdcontrol -l ru.koi8-r.win First I set locale to ru_RU.KOI8-R (number 229, st this only once), update env, set font to koi8-r and keymap to en/ru.koi8-r with ctrl+shift for switch. I'd like to have at openrc/freebsd services keymaps (wrapper for kbdcontrol) and consolefont (wrapper for vidcontrol) Reproducible: Always
isnt /etc/init.d/syscons what you need ?
it seems it is, Josh, could you please revert: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoo-freebsd.xml?r1=1.38&r2=1.39 we get that kind of bug because the wiki does not contain all the information that even the old guide had. It used to be described there. Thanks.
(In reply to comment #2) > it seems it is, Josh, could you please revert: > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoo- > freebsd.xml?r1=1.38&r2=1.39 > we get that kind of bug because the wiki does not contain all the > information that even the old guide had. It used to be described there. > Thanks. It might be better to put a note at the top saying that the Wiki has more up to date information, but the guide still holds some relevance, rather than outright reverting it. A major complaint that I have received from users and other Gentoo developers is that they cannot find updated installation information.
So there is nothing for us to do here then? If that's the case, I want to close this as invalid.
(In reply to comment #4) > So there is nothing for us to do here then? If that's the case, I want > to close this as invalid. reassign to doc team imho, there's something wrong and the bug reporter is not to blame as i couldn't find mention of syscons anywhere now.
Re-assigning to the documentation team since there isn't anything for us to do in OpenRC.
why not just put this info into the wiki page, so that it has all the needed content, and we don't have to rewrite the outdated doc?
(In reply to comment #7) > why not just put this info into the wiki page, so that it has all the needed > content, and we don't have to rewrite the outdated doc? probably for the same reason you dont put the handbook on the wiki; the doc is not _that_ outdated, I'm (was?) still using it for new installs as it is short and concise and reminds me all the steps.
(In reply to comment #8) > (In reply to comment #7) > > why not just put this info into the wiki page, so that it has all the needed > > content, and we don't have to rewrite the outdated doc? > > probably for the same reason you dont put the handbook on the wiki; the doc > is not _that_ outdated, I'm (was?) still using it for new installs as it is > short and concise and reminds me all the steps. the init.d info isn't in the doc, either, so i don't know what exactly the doc has that the wiki page doesn't. (aside from better organization.) i'll include a note at the top of the doc for now, but it's bad practice to do so instead of a redirect. one of the guides should have everything...users shouldn't need to read two incomplete/outdated guides just to get their install info.
(In reply to comment #9) > > probably for the same reason you dont put the handbook on the wiki; the doc > > is not _that_ outdated, I'm (was?) still using it for new installs as it is > > short and concise and reminds me all the steps. > > the init.d info isn't in the doc, either, so i don't know what exactly the > doc has that the wiki page doesn't. (aside from better organization.) > > i'll include a note at the top of the doc for now, but it's bad practice to > do so instead of a redirect. one of the guides should have > everything...users shouldn't need to read two incomplete/outdated guides > just to get their install info. i added a note at the top of the gentoo doc, for now. but we still need a proper solution: one of the guides needs to be fully up-to-date and self-contained.
(In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > why not just put this info into the wiki page, so that it has all the needed > > > content, and we don't have to rewrite the outdated doc? > > > > probably for the same reason you dont put the handbook on the wiki; the doc > > is not _that_ outdated, I'm (was?) still using it for new installs as it is > > short and concise and reminds me all the steps. > > the init.d info isn't in the doc, either, so i don't know what exactly the > doc has that the wiki page doesn't. (aside from better organization.) > copy/pasted from webcgi: 709 <p> 710 In case you need to use another keyboard layout for your language, you have to 711 set the correct value in <path>/etc/conf.d/syscons</path>. The following example 712 uses the Spanish layout, so you'll have to adjust it to your need if you want to 713 use another one. 714 </p> this is what I was referring to. when you look at the conf.d file, you see some comments and examples. we wont describe the details in a quick install guide. > i'll include a note at the top of the doc for now, but it's bad practice to > do so instead of a redirect. one of the guides should have > everything...users shouldn't need to read two incomplete/outdated guides > just to get their install info. i dont think the wiki will replace the quick install guide, imho they serve different purposes; its nice to have a section about major upgrades, how to run jails, how to use zfs, troubleshooting, etc., but these do not belong at all to a quick install guide.
