1 |
On Saturday, August 08, 2015 2:57:29 AM Felix Miata wrote: |
2 |
> I don't get why any distro leaves this out, why anyone wouldn't like to |
3 |
> automatically notice while booting any announcement that something failed, |
4 |
> especially someone who has just gotten a new installation up for the first |
5 |
> times. Why isn't --noclear set by default? |
6 |
|
7 |
Because it's your choice (and your job) to set it or not. Gentoo is not a |
8 |
distro per se, it' more of a set of tools to help you build your own system. |
9 |
In most cases it provides whatever upstream ships with only patches and fixes |
10 |
as needed. There's also a logging setting on rc.conf that logs the boot |
11 |
process. |
12 |
|
13 |
The rest of your problems where due to failure to follow the handbook. |
14 |
|
15 |
> |
16 |
> Once I set this and rebooted I saw several things that needed fixing that I |
17 |
> didn't have a clue about: |
18 |
> |
19 |
> 1-error loading /etc/.../hostname (I had copied it from openSUSE |
20 |
installation |
21 |
> instead of following installation instruction, and without reading or saving |
22 |
> the existing one) |
23 |
> |
24 |
> 2-depending on hostname working, syslog-ng fails to start |
25 |
> |
26 |
> 3-missing mount points |
27 |
> |
28 |
> As a consequence of my ineptitude (and prior to reading |
29 |
> http://www.gentoo-wiki.info/FQDN) I did emerge -s hostname, found a package |
30 |
> by that name, and chose to emerge it. 30 minutes later, it and 3 dep |
31 |
packages |
32 |
> were still compiling, lots lots longer than a kernel compile. :-( |
33 |
> |
34 |
|
35 |
-- |
36 |
Fernando Rodriguez |