From: "Dag-Erling Smørgrav" <des_at_des.no> > I didn't realize you were building and installing on different > systems. Try adding 'INSTALLFLAGS=-p' to /etc/make.conf on the > client (or running 'make installkernel INSTALLFLAGS=-p') No, the idea is: There's this box in a corner which build on a "regular"basis: 4-STABLE for some production servers (haven't tried upgrading those) 5-RELEASE for my fileserver and firewall 5-CURRENT for not critical boxes 5.1 as an intermediate when I following some migrations since my COMPAQ ML370 does not always like CURRENT I export /usr/obj, /usr/src{4,4,51,52} to the same mounts on the system I want to upgrade. And normally I can just follow the regular process, where I get to single mode via multi-user mode, so all IP stuff is loaded and started. I only seriously ran into the discussed catch when I installed a fresh system (for some NFS performance tests) with an old 5.0-DP1 release and wanted to upgrade that to 5.1 or 5.2. I tried your suggestion(-p), but it still gives 'signal 12' But perhaps my system is too botched right now. Doing it the 'hard' way works: cd /usr/obj/usr/src51/src/sys/sys/GENERIC make install --WjWReceived on Thu Feb 12 2004 - 05:44:16 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:42 UTC