Archives
Archives
| From: | Michael Orlitzky <michael@××××××××.com> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default | ||
| Date: | Thu, 24 Jan 2013 19:21:59 | ||
| Message-Id: | 510189CE.3020700@orlitzky.com | ||
| In Reply to: | Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default by Ian Stakenvicius |
||
| 1 | On 01/24/13 13:58, Ian Stakenvicius wrote: |
| 2 | > |
| 3 | > |
| 4 | > How about, you know what you're doing and are going to build a new |
| 5 | > kernel as soon as the emerge finishes (since the emerge is also |
| 6 | > bringing in a new gentoo-sources)?? |
| 7 | > |
| 8 | |
| 9 | If you're going to upgrade both anyway, you should be upgrading the |
| 10 | kernel first. That way if you lose power or the system crashes, the box |
| 11 | can reboot. |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default | "vivo75@×××××.com" <vivo75@×××××.com> |
| Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default | Rich Freeman <rich0@g.o> |