--- Dag-Erling Smørgrav [EMAIL PROTECTED] wrote:
masta [EMAIL PROTECTED] writes:
I found that if I put /rescue in my PATH before
all the normal stuff,
things tend to work (like ls). For me I got
caught doing the:
make buildworld
make buildkernel KERNCONF=FOO
make installkernel
masta [EMAIL PROTECTED] writes:
I found that if I put /rescue in my PATH before all the normal stuff,
things tend to work (like ls). For me I got caught doing the:
make buildworld
make buildkernel KERNCONF=FOO
make installkernel
mergemaster
make installworld
BAM! installworld fails, and
Dag-Erling Smørgrav wrote:
[EMAIL PROTECTED] writes:
I'm building new kernels as I write this. My next question is:
One of the machines I'm building on is remote and was last rebuilt
just before the change. What would be be better sequence for making
the change after a fresh cvsup ?
On Thu, Nov 13, 2003 at 07:39:15AM -0800, [EMAIL PROTECTED] wrote:
Mensaje citado por [EMAIL PROTECTED]:
| Mensaje citado por Ceri Davies [EMAIL PROTECTED]:
|
| | On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote:
| | I installed an older current snap, Oct 26, on a brandnew
Mensaje citado por Jesper Skriver [EMAIL PROTECTED]:
| On Thu, Nov 13, 2003 at 07:39:15AM -0800, [EMAIL PROTECTED] wrote:
CUT
| I'm building new kernels as I write this. My next question is:
| One of the machines I'm building on is remote and was last rebuilt
| just before the change. What
[EMAIL PROTECTED] writes:
I'm building new kernels as I write this. My next question is:
One of the machines I'm building on is remote and was last rebuilt
just before the change. What would be be better sequence for making
the change after a fresh cvsup ?
RTFM.
make buildworld
make
