--- 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 i
> Date: Sat, 15 Nov 2003 09:51:40 +1000 (EST)
> From: Andy Farkas <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> Richard Coleman wrote:
>
0. mergemaster -p
> > 1. make buildworld
> > 2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE
> > 3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE
2 and
"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
Richard Coleman wrote:
Andy Farkas wrote:
Richard Coleman wrote:
1. make buildworld
2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE
3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE
4. shutdown -r now
5. boot into single user mode
6. fsck -p
7. mount -u /
8. mount -a -t ufs
9. swapon -a
9.
Andy Farkas wrote:
Richard Coleman wrote:
1. make buildworld
2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE
3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE
4. shutdown -r now
5. boot into single user mode
6. fsck -p
7. mount -u /
8. mount -a -t ufs
9. swapon -a
9.5 adjkerntz -i
Yep, forg
Richard Coleman wrote:
> 1. make buildworld
> 2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE
> 3. make installkernel KERNCONF=NAME_OF_KERNEL_FILE
> 4. shutdown -r now
> 5. boot into single user mode
> 6. fsck -p
> 7. mount -u /
> 8. mount -a -t ufs
> 9. swapon -a
9.5 adjkerntz -i
> 10. make
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
+---[ Edmund L. Wong ]--
|
| I am able to get myself to a single-user prompt as
| root, but not much else. Does anyone have any
| suggestions as to how I can salvage this? Or will I
| have to reinstall anew?
Boot from a live/fixit CD/floppy, and mount your drives and rebu
Thanks Richard. So unfortunately, I was an idiot and
ran installworld without rebuilding and installing a
new kernel (the one I have was built on Nov. 1). Now
everything coredumps, including rm, ls, etc. I cannot
make installworld, installkernel, buildworld or
buildkernel.
I am able to get myse
Sure. I can do that. Some structures in statfs changed size. So you
need to rebuild and install your kernel before you update the world.
The instructions in the handbook should work just fine.
1. make buildworld
2. make buildkernel KERNCONF=NAME_OF_KERNEL_FILE
3. make installkernel KERNCONF=N
Could someone bring me up to speed on this thread? I
just joined current and I also updated this morning
and have all kinds of issues.
THanks,
Ed
--- Richard Coleman <[EMAIL PROTECTED]>
wrote:
> Someone just needs to bring the build(7) man page up
> to date with the
> handbook.
>
> Also, I no
Someone just needs to bring the build(7) man page up to date with the
handbook.
Also, I noticed that build(7) still lists the "installmost" build
target. I believe that was removed.
I would file a PR except that my man pages always suck.
Richard Coleman
[EMAIL PROTECTED]
Brent Jones wrote:
I
In message: <[EMAIL PROTECTED]>
Brent Jones <[EMAIL PROTECTED]> writes:
: If this is true, perhaps the "build" man page should be updated.
: Here's what the man page has to say on the topic:
:
: The ``approved'' method of updating your system from the latest
: sources
:
If this is true, perhaps the "build" man page should be updated.
Here's what the man page has to say on the topic:
The ``approved'' method of updating your system from the latest
sources
is:
make buildworld
make buildkernel KERNCONF=FOO
make installke
In message: <[EMAIL PROTECTED]>
Uwe Laverenz <[EMAIL PROTECTED]> writes:
: [EMAIL PROTECTED] schrieb:
:
: > Uwe, do you have any remote machines? I'm wondering what the correct
: > sequence would be to update and reboot them.
:
: I would suggest to do it this way:
:
: 1. make buildw
[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 bui
Mensaje citado por Uwe Laverenz <[EMAIL PROTECTED]>:
| [EMAIL PROTECTED] schrieb:
|
| > Uwe, do you have any remote machines? I'm wondering what the correct
| > sequence would be to update and reboot them.
|
| I would suggest to do it this way:
|
| 1. make buildworld
| 2. make kernel KERNCONF=
U
Mensaje citado por Jesper Skriver <[EMAIL PROTECTED]>:
| On Thu, Nov 13, 2003 at 07:39:15AM -0800, [EMAIL PROTECTED] wrote:
| > 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. Wha
[EMAIL PROTECTED] schrieb:
Uwe, do you have any remote machines? I'm wondering what the correct
sequence would be to update and reboot them.
I would suggest to do it this way:
1. make buildworld
2. make kernel KERNCONF=
3. *reboot* (with new kernel and old userland)
4. make installworld
5. merge
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
Mensaje citado por Uwe Laverenz <[EMAIL PROTECTED]>:
| [EMAIL PROTECTED] schrieb:
|
| > Thanks, I missed that. :( Sorry for the noise.
|
| You're not the only one who missed that. We killed 2 machines yesterday
| evening (~11pm CET) this way. I think I did read UPDATING and I can't
| remember a
[EMAIL PROTECTED] schrieb:
Thanks, I missed that. :( Sorry for the noise.
You're not the only one who missed that. We killed 2 machines yesterday
evening (~11pm CET) this way. I think I did read UPDATING and I can't
remember any warning entries?! It's there now, of course so we were just
run
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 dell power edge
| | > with a single Xeon 2.4 GHz cpu and 1G in memory.
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 dell power edge
| > with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great.
| > I installed everythi
On Thu, Nov 13, 2003 at 06:48:35AM -0800, [EMAIL PROTECTED] wrote:
> I installed an older current snap, Oct 26, on a brandnew dell power edge
> with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great.
> I installed everything except the kitchen sink. Then I decided it was
> time to
I installed an older current snap, Oct 26, on a brandnew dell power edge
with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great.
I installed everything except the kitchen sink. Then I decided it was
time to update, I've got serveral other machines weathering the storms.
Bad idea.
26 matches
Mail list logo
