On Thu, May 13, 2010 at 23:51, Jeremy Chadwick <free...@jdc.parodius.com> wrote: > 1) We use csup now, not cvsup. csup comes with the base system, so > there's no need to install cvsup. > > 2) I'm not sure why you're downloading ports.tar.gz and extracting it. > This means that /var/db/sup/ports-all won't match what's in > /usr/ports. You should just use csup to populate /usr/ports. > You can do this by doing: > > csup -h <cvsup-server> -L 2 /usr/share/examples/cvsup/ports-supfile > > You can also populate /usr/src (and thus /var/db/sup/src-all) by > doing: > > csup -h <cvsup-server> -L 2 /usr/share/example/cvsup/stable-supfile > > There are also /etc/make.conf variables you can set to make this > process easier once you've populated /usr/ports and /usr/src; you > can do something like "cd /usr/ports ; make update".
Thank you, that is something I didn't see changing. I will try that out from now on. > Well, if what you're doing is an "in-place" 7.x upgrade to 8.x, I don't > know how to do this or if it works. Others can help. No, I did a fresh 8.0-RELEASE install and then tried updating it to -STABLE. > Otherwise, the steps you're describing for building a system are not > what's in src/Makefile (not src/UPDATING). These are the steps: > > # 1. `cd /usr/src' (or to the directory containing your source tree). > # 2. `make buildworld' > # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > # [steps 3. & 4. can be combined by using the "kernel" target] > # 5. `reboot' (in single user mode: boot -s from the loader prompt). > # 6. `mergemaster -p' > # 7. `make installworld' > # 8. `make delete-old' > # 9. `mergemaster' (you may wish to use -U or -ai). > # 10. `reboot' > # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Yeah, that is very close to what I did: # cd /usr/src # make buildworld # make kernel KERNCONF=LIGHTNING # reboot That was for the first install, that got completely borked after rebooting and me trying to change the contents of /etc/fstab. On this current install, I did this: # cd /usr/src # make buildworld # make kernel KERNCONF=LIGHTNING # mergemaster -p # make installworld # make delete-old # mergemaster -i # make delete-old-libs # reboot The reason for me to try all that before rebooting, like I said on the first e-mail, was that I thought the drive numbers changing could be related to the -STABLE kernel running on top of -RELEASE userland. All those steps ran just fine, though. But when I reboot, I still see the kernel assigning ad10 to my first drive (it's ad8 with the -RELEASE kernel) and ad16 for the second (ad14 with -RELEASE). I have no idea what is causing this change in numbering. Thanks, Fred _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"