Re: upgraded to CURRENT = system is dead
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 about the new system calls that support the new statfs structure. We generally recommend doing a buildworld first, but it has to be done in a different order for this upgrade. These instructions should be changed. Doing 'buildworld' before 'buildkernel' works just fine this time as always, and instructing users to do the opposite will only confuse them. There's nothing in the kernel build that calls statfs64. However, if I am correctly reading the section quoted from Antione's message, the problem might be that he did: 'make install kernel ...' instead of: 'make installkernel ...' I assumed that this was a typo in the email, but even if it wasn't, it shouldn't make any difference; since he didn't build a new world, 'make install' will just reinstall the world he already had, and 'make kernel' will build and install a new kernel. It'll just take a while longer than it should. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 buildworld' first. 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 about the new system calls that support the new statfs structure. We generally recommend doing a buildworld first, but it has to be done in a different order for this upgrade. However, if I am correctly reading the section quoted from Antione's message, the problem might be that he did: 'make install kernel ...' instead of: 'make installkernel ...' 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'? -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 not much point in 'make buildkernel' if you haven't done 'make buildworld' first. 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 about the new system calls that support the new statfs structure. We generally recommend doing a buildworld first, but it has to be done in a different order for this upgrade. Mmm. Indeed. I've just committed what I hope is a clarification to UPDATING to suggest buildworld buildkernel installkernel before installworld. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 statfs structure, but ... We generally recommend doing a buildworld first, but it has to be done in a different order for this upgrade. Mmm. Indeed. I've just committed what I hope is a clarification to UPDATING to suggest buildworld buildkernel installkernel before installworld. Oops. Sounds like I picked up the wrong idea of what was needed for this. Sorry if I created more confusion for anyone! I should note that what I actually did was I first did a normal upgrade to -current as of 11/11, and after that was all done I did a second upgrade to the up-to-date current. There was one problem in that src/sys/boot/i386/boot2/boot2.c needed to be fixed to build the 11/11 snapshot, but other than that it worked out fine for me. My second upgrade would only cover a few days, so that's why I probably got away with doing things in the wrong order for that second upgrade... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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] http://www.lphp.org PGP/GnuPG key: http://www.lphp.org/ressources/ajacoutot.asc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 Nov 1st to see how it goes. Thank the Unix gods this wasn't a production machine. Antoine Jacoutot wrote: 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 make installkernel reboot make installworld -- yes... but I get this during the installworld: /libexec/ld-elf.so.1: Shared object libedit.so.4 not found Stop in /usr/src :( I just tried it again from scratch but got the same error... ! If anyone has an idea... -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 to try the installation fresh with a cvsup back to Nov 1st to see how it goes. Thank the Unix gods this wasn't a production machine. Someone told me a solution for this: 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 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 Nov 1st to see how it goes. Thank the Unix gods this wasn't a production machine. Antoine Jacoutot wrote: 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 make installkernel reboot make installworld -- yes... but I get this during the installworld: /libexec/ld-elf.so.1: Shared object libedit.so.4 not found Stop in /usr/src :( I just tried it again from scratch but got the same error... ! If anyone has an idea... -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 mount anything :( I followed everything that was in UPDATING... So my box is really dead... right ? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 make installkernel reboot make installworld -- yes... but I get this during the installworld: /libexec/ld-elf.so.1: Shared object libedit.so.4 not found Stop in /usr/src :( I just tried it again from scratch but got the same error... ! If anyone has an idea... Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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. Quoting from another message: make buildworld make buildkernel make installkernel reboot make installworld -- yes... but I get this during the installworld: /libexec/ld-elf.so.1: Shared object libedit.so.4 not found Stop in /usr/src :( I just tried it again from scratch but got the same error... ! If anyone has an idea... Antoine 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 Aron ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
upgraded to CURRENT = system is dead
Hi :) I just upgraded with cvsup to CURRENT. I read UPDATING to make sure I would have no problem, but maybe I misunerstood something. Here is what I did: $ cvsup blablabla... $ make buildkernel KERNCONF=MYKERNEL make install kernel KERNCONF=MYKERNEL $ reboot (in single user mode) $ make buildworld $ make installworld .. -- error during the installworld: /libexec/ld-elf.so.1: Shared object libedit.so.4 not found Now, any command I try to launch gives me this exact same error and my system is then totally useless... :( Anything I could do ? Please please, tell me my box isn't dead... By the way, I compiled CURRENT with dynamic root. Thanks in advance. -- Antoine Jacoutot [EMAIL PROTECTED] http://www.lphp.org PGP/GnuPG key: http://www.lphp.org/ressources/ajacoutot.asc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
