From owner-freebsd-questions Tue Oct 19 10:53:33 1999 Delivered-To: freebsd-questions@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.13]) by hub.freebsd.org (Postfix) with ESMTP id C2FF617818 for ; Tue, 19 Oct 1999 10:53:26 -0700 (PDT) (envelope-from wayne@staff.msen.com) Received: from manor.msen.com (LOCALHOST [127.0.0.1]) by manor.msen.com (8.8.8/8.8.8) with ESMTP id NAA01919 for ; Tue, 19 Oct 1999 13:53:25 -0400 (EDT) (envelope-from wayne@manor.msen.com) Message-Id: <199910191753.NAA01919@manor.msen.com> To: freebsd-questions@FreeBSD.ORG Subject: Is it impossible to upgrade FreeBSD systems? From: "Michael R. Wayne" Date: Tue, 19 Oct 1999 13:53:25 -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Environment: Machines sitting miles away in colo space. No floppy, CDROM, keyboard, monitor, or console. Just Ethernet and a hard drive. Goal: Binary upgrade from 3.2 to 3.3 RELEASE, from remote site. Problem: All docs state that old versions of sysinstall should not be used but new version of sysinstall is not found on CDROM #1. Attempted solution: NFS mount the CDROM on the target machine, cd to /cdrom/bin and sh install.sh # sh install.sh You are about to extract the base distribution into / - are you SURE you want to do this over your installed system (y/n)? y tar: Could not unlink bin/rcp : Operation not permitted tar: Could not create file bin/rcp : Operation not permitted tar: Could not unlink sbin/init : Operation not permitted tar: Could not create file sbin/init : Text file busy tar: Could not unlink usr/bin/man : Operation not permitted tar: Could not create file usr/bin/man : Operation not permitted tar: Could not unlink usr/lib/libc.so.3 : Operation not permitted tar: Could not create file usr/lib/libc.so.3 : Operation not permitted tar: Could not unlink usr/lib/libc_r.so.3 : Operation not permitted tar: Could not create file usr/lib/libc_r.so.3 : Operation not permitted tar: Could not unlink usr/libexec/mail.local : Operation not permitted tar: Could not create file usr/libexec/mail.local : Operation not permitted tar: Could not unlink usr/libexec/ld-elf.so.1 : Operation not permitted tar: Could not create file usr/libexec/ld-elf.so.1 : Operation not permitted tar: Could not create directory usr/share/examples/etc/defaults : File exists tar: Could not unlink usr/share/examples/etc/defaults/rc.conf : Not a directory tar: Could not create file usr/share/examples/etc/defaults/rc.conf : Not a directory Once this process completes, users can no longer log into the machine (they are prompted for a password but always get "Login incorrect") I figured out that I can do a bunch of chflags noschg commands permitting this to mostly complete. Shouldn't the install script be doing this? Was it really intentional that /usr/bin/man become a file and /usr/share/examples/etc/defaults change from a file to a directory? I can't believe people actually travel to remote locations to shove floppies into servers to upgrade them. So, how DO people upgrade machines? /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message