| Summary: | [PATCH] Add KERNEL identifier to GENERIC | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Doug <Doug> | ||||||
| Component: | kern | Assignee: | Marcel Moolenaar <marcel> | ||||||
| Status: | Closed FIXED | ||||||||
| Severity: | Affects Only Me | ||||||||
| Priority: | Normal | ||||||||
| Version: | 3.4-STABLE | ||||||||
| Hardware: | Any | ||||||||
| OS: | Any | ||||||||
| Attachments: |
|
||||||||
|
Description
Doug
2000-03-25 06:40:01 UTC
Responsible Changed From-To: freebsd-bugs->sheldonh I'll take this one. If the patch on 17536 works as advertised, I'd prefer that solution, but we'll see. Hi Doug, Here's what I sent the originator of PR 17536 regarding additional work on the buildkernel and installkernel targets. I hope this explains why I haven't gone ahead with your patch. Ciao, Sheldon. Hi Doug, Have you had time to test whether "makeoptions KERNEL?=kernel.GENERIC" is allowed? Ciao, Sheldon. Responsible Changed From-To: sheldonh->freebsd-bugs Divest myself of another PR so that I can focus on my only goal for 5.0-RELEASE. Sorry about this, Doug. Responsible Changed From-To: freebsd-bugs->marcel My plate as well. State Changed From-To: open->closed We won't support installing multiple kernels with the installkernel target. With this path, the default case (ie KERNEL=GENERIC) would not install a kernel named 'kernel'. This is potentially harmful. The problem the patch tries to solve is more pilot error than anything else. Remember that installing a new kernel always leaves the old kernel under 'kernel.old'... |