From owner-freebsd-questions Mon Mar 27 10: 4:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id E5CC237B52B for ; Mon, 27 Mar 2000 10:03:58 -0800 (PST) (envelope-from bartequi@neomedia.it) Received: from bartequi.ottodomain.org (ppp3-pa5.neomedia.it [195.103.207.115]) by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id UAA14509; Mon, 27 Mar 2000 20:03:38 +0200 (CEST) From: Salvo Bartolotta Date: Mon, 27 Mar 2000 19:05:31 GMT Message-ID: <20000327.19053100@bartequi.ottodomain.org> Subject: Re: -STABLE upgrade question (disk devices) To: pmoyer@hyperon.com, freebsd-questions@FreeBSD.ORG In-Reply-To: <200003271640.IAA03872@gull.prod.itd.earthlink.net> References: <200003271640.IAA03872@gull.prod.itd.earthlink.net> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 3/27/00, 5:40:37 PM, "Philip R. Moyer" wrote=20 regarding -STABLE upgrade question (disk devices): > I'm upgrading from 3.4 to 4.0 (-STABLE) and I have a couple > of questions regarding the disk devices. The procedure for > doing an upgrade to 4.0 (from /usr/src/UPDATING) is: > 1. cd /usr/src > 2. make buildworld > 3. cd /usr/src/sbin/mknod > 4. make install > 5. cd /usr/src/sys/modules > 6. make install > 7. cd /usr/src > 8. make buildkernel KERNEL=3D > 9. make installkernel KERNEL=3D > 10. chflags noschg /kernel > 11. mv /kernel /kernel.3_4 > 12. mv / /kernel > 13. chflags schg /kernel > 14. cp /usr/src/etc/MAKEDEV /dev/MAKEDEV > 15. for N in list of disks > MAKEDEV N > for M in list of slices > MAKEDEV NsMa > 16. reboot single > 17. cd /usr/src > 18. make -DNOINFO installworld > 19. make installworld > 20. reboot multi > My questions are in step 15. > I've done an ls in /dev and made a list of all the disk-related > devices. Is that what I should use (it's appended)? Should I > remake the devices for the raw disks, too (e.g., rwd0)? > Cheers, > Phil > Here's the list of disk devices on my system: > da0 > da0s1 > da0s2 > da0s3 > da0s4 > da1 > da1s1 > da1s2 > da1s3 > da1s4 > da2 > da2s1 > da2s2 > da2s3 > da2s4 > da3 > da3s1 > da3s2 > da3s3 > da3s4 > od0 > od0s1 > od0s2 > od0s3 > od0s4 > rda0 > rda0s1 > rda0s2 > rda0s3 > rda0s4 > rda1 > rda1s1 > rda1s2 > rda1s3 > rda1s4 > rda2 > rda2s1 > rda2s2 > rda2s3 > rda2s4 > rda3 > rda3s1 > rda3s2 > rda3s3 > rda3s4 > rod0 > rod0s1 > rod0s2 > rod0s3 > rod0s4 > rvn0 > rvn0s1 > rvn0s2 > rvn0s3 > rvn0s4 > rwd0 > rwd0s1 > rwd0s1a > rwd0s1b > rwd0s1c > rwd0s1d > rwd0s1e > rwd0s1f > rwd0s1g > rwd0s1h > rwd0s2 > rwd0s3 > rwd0s4 > rwd0s5 > rwd1 > rwd1s1 > rwd1s2 > rwd1s3 > rwd1s4 > rwd2 > rwd2s1 > rwd2s2 > rwd2s3 > rwd2s4 > rwd3 > rwd3s1 > rwd3s2 > rwd3s3 > rwd3s4 > rwfd0 > rwfd0s1 > rwfd0s2 > rwfd0s3 > rwfd0s4 > vn0 > vn0s1 > vn0s2 > vn0s3 > vn0s4 > wd0 > wd0s1 > wd0s1a > wd0s1b > wd0s1c > wd0s1d > wd0s1e > wd0s1f > wd0s1g > wd0s1h > wd0s2 > wd0s3 > wd0s4 > wd0s5 > wd1 > wd1s1 > wd1s2 > wd1s3 > wd1s4 > wd2 > wd2s1 > wd2s2 > wd2s3 > wd2s4 > wd3 > wd3s1 > wd3s2 > wd3s3 > wd3s4 > wfd0 > wfd0s1 > wfd0s2 > wfd0s3 > wfd0s4 Dear Philip Moyer, If I fully understand the whole matter, you have to remake your *disk*=20 and *slice* entries at this stage (stage 15) because you need to=20 access them in the subsequent reboot (s.u.m.). So, strictly speaking,=20 you should remake only those disks and slices which are necessary for=20 the uprading procedure (e.g. because they will contain the upgraded=20 pieces of your system :-) Personally, I followed Nik's make world tutorial as usual (steps >20):=20 ie I ran mergemaster and then I remade *all* the devices ("/dev/sh=20 MAKEDEV all"). =20 If you do so, you will automatically (re)make a good number of them=20 (ie a "standard set", so to speak.) But you *MUST* make slice entries=20 (e.g. ad0s1a) and all those entries outside the "standard set". You might want to check what is remade (e.g. as indicated in the=20 hanbook), and, mutatis mutandis (ie check the new names for the device=20 nodes), make what is missing. AFAIK, in 4.0-something (current,=20 release, or "stable"), the concept of block devices has disappeared=20 although, in the early stages, "compatibility" devices nodes will=20 still be present (e.g. wd*). Also, you might want to *write down* what you do as well as recording=20 your session (script command): if something goes wrong, somebody will=20 be able to help you. BTW, after upgrading to 4-(then)CURRENT, I remade the world once again=20 to make sure that *all* the components were ok: the logs (and the=20 script command) are your friends :-)=20 Good luck, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message