Summary: | put sshd in default runlevel | ||
---|---|---|---|
Product: | [OLD] Docs on www.gentoo.org | Reporter: | Bart Van Loon <bart> |
Component: | Installation Handbook | Assignee: | Docs Team <docs-team> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bart Van Loon
2006-11-01 07:43:52 UTC
(In reply to comment #0) We already tell you to add a user to the wheel group. And we already talk about starting up sshd -- we expect that if you're going to be doing something advanced like a remote install, that you keep track of what programs you'll need to emerge. Unfortunately, we can't include warnings for every possible bit of software a user might include, because if we wrote things like "oh, if you emerged *foo*, don't forget to configure it like so..." the handbook would be another hundred pages long. yeah, well... ok then. :-) it's not all that important, I was just so frustrated by my mistake that I didn't want others to overcome the same. anyway, thanks for the answer. It's beyond the scope of the regular handbook. I'd expect users doing such an install to be more familiar with Gentoo and they would be more likely to use the quick install guide. http://www.gentoo.org/doc/en/gentoo-x86-quickinstall.xml |