Garance A Drosihn [EMAIL PROTECTED] writes:
Uh. /usr/src/UPDATING explicitly says:
20031112:
[...] You should build and boot a new kernel BEFORE doing a
`make world' as the new kernel will know about binaries using
the old statfs structure, but an old kernel will not know
Antoine Jacoutot [EMAIL PROTECTED] writes:
Here is what I did:
$ cvsup blablabla...
$ make buildkernel KERNCONF=MYKERNEL make install kernel KERNCONF=MYKERNEL
There's not much point in 'make buildkernel' if you haven't done 'make
buildworld' first.
DES
--
Dag-Erling Smørgrav - [EMAIL
At 10:37 AM +0100 11/17/03, Dag-Erling Smørgrav wrote:
Antoine Jacoutot [EMAIL PROTECTED] writes:
Here is what I did:
$ cvsup blablabla...
$ make buildkernel KERNCONF=MYKERNEL
make install kernel KERNCONF=MYKERNEL
There's not much point in 'make buildkernel' if you haven't
done 'make
On Mon, 17 Nov 2003, Garance A Drosihn wrote:
At 10:37 AM +0100 11/17/03, Dag-Erling Smørgrav wrote:
Antoine Jacoutot [EMAIL PROTECTED] writes:
Here is what I did:
$ cvsup blablabla...
$ make buildkernel KERNCONF=MYKERNEL
make install kernel KERNCONF=MYKERNEL
There's
At 6:23 PM -0500 11/17/03, Robert Watson wrote:
On Mon, 17 Nov 2003, Garance A Drosihn wrote:
Uh. /usr/src/UPDATING explicitly says:
20031112:
[...] You should build and boot a new kernel BEFORE
doing a `make world' as the new kernel will know about
binaries using the old
On Tuesday 18 November 2003 00:17, Garance A Drosihn wrote:
Users need to specify a single target of 'installkernel',
with no blanks between the two words. Antoine, was that
just a typo, or did you really do 'make install kernel'?
I was a typo :)
--
Antoine Jacoutot
[EMAIL PROTECTED]
I just ran into this very same thing today on a brand new installation. Upon
reboot I can't even get to a shell. Was rather hoping someone had some more
information about this.
Running the installation on an IBM xSeries 305 with a P4. Going to try the
installation fresh with a cvsup back to
Selon Michael Collette [EMAIL PROTECTED]:
I just ran into this very same thing today on a brand new installation. Upon
reboot I can't even get to a shell. Was rather hoping someone had some more
information about this.
Running the installation on an IBM xSeries 305 with a P4. Going
I got trapped in the mess too but finally repaired it with a livecd. Let's
hope the path for 5.2 RELEASE will be smoother for the less adventurous of us.
I just ran into this very same thing today on a brand new installation. Upon
reboot I can't even get to a shell. Was rather hoping someone
Selon long [EMAIL PROTECTED]:
reboot
make world
single user mode, make installworld
reboot
and it's up and running... no more sig12 or anything like that...
Yes, but no !
I don't have any sig12 error...
I have: /libexec/ld-elf.so.1: Shared object libedit.so.4 not found
And I can't even
Selon Dylan Wylie [EMAIL PROTECTED]:
The idea is that you need to build a new kernel with the new sources before
you install
world.
You built your kernel before building the sources, so your kernel is based on
old source.
Quoting from another message:
make buildworld
make buildkernel
Lör 2003-11-15 klockan 16.30 skrev Antoine Jacoutot:
Selon Dylan Wylie [EMAIL PROTECTED]:
The idea is that you need to build a new kernel with the new sources
before you install
world.
You built your kernel before building the sources, so your kernel is based
on old source.
Selon Aron Håkanson [EMAIL PROTECTED]:
If you are looking for a fast and temporary solution, just to finish the
installworld process, you can export the following value to the
LD_LIBRARY_PATH variable: $LD_LIBRARY_PATH:/lib:/usr/lib
Hey :)
Thanks a lot... I'll try that.
Antoine
13 matches
Mail list logo
