From owner-freebsd-stable Fri Mar 29 11:40:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sumter.awod.com (sumter.awod.com [208.140.99.1]) by hub.freebsd.org (Postfix) with ESMTP id 7E3B937B416 for ; Fri, 29 Mar 2002 11:40:52 -0800 (PST) Received: from teddy.fas.com (pcp01010372pcs.mplsnt01.sc.comcast.net [68.58.176.67]) by sumter.awod.com (8.8.7/8.12.2) with ESMTP id OAA85348 for ; Fri, 29 Mar 2002 14:40:51 -0500 (EST) (envelope-from stanb@awod.com) X-Authentication-Warning: sumter.awod.com: User sandib [pcp01010372pcs.mplsnt01.sc.comcast.net] popped 71 seconds ago Received: from stan by teddy.fas.com with local (Exim 3.34 #1 (Debian)) id 16r2G6-0005VZ-00 for ; Fri, 29 Mar 2002 14:41:58 -0500 Date: Fri, 29 Mar 2002 14:41:58 -0500 From: stan To: FreeBSD Stable Mailing List Subject: Help making second disk bootable Message-ID: <20020329194158.GA20822@teddy.fas.com> Mail-Followup-To: FreeBSD Stable Mailing List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.17 X-Uptime: 14:27:34 up 6 days, 19:12, 2 users, load average: 0.08, 0.12, 0.29 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I Broke so much stuff with last weekends atempt at upgrading the base system and ports, that after fighting with it all week, all I really want is my machine back to the state it was in on last Friday :-( here is what I have: 1. A good set of Amanda backups. 2. A machine with several disk, everythign including /usr/local is on ad0, and ad1 is an identical disk. Here is my plan. 1. Use sysinstall to partion ads1 (done. I could not get it to partion just like ad1, but all the "auto" created partions are at least big enough, and I'm really wanting to wind up back on ads0, anyway). 2. Restore all 3 partions on ads1 (/, /var, usr). (runing as I type this). 3. Make ads1 bootable (How do I do this?). 4. Reboot, coming up on ads1. 5. Mount the 3 paritions of ads1, and do a rm -rf on them ( will I get burned by symlinks here?). 6. Uisng tar copy all 3 paritions of ads1 to the respective paritions of ads0. (Any risks of permissions, sticky bit loss here?) (tar cvpf - | tar xpf -). 7. Reboot using adsi (happy ending?). Can anyone see any problems with this strategy? Is there a safer one? Thanks for any sugestiosn, I'm prety frustrated at the moent, this was one sweet machien with several months of tweaking on it, and I dpended on it for daily use! -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message