Date: Sat, 8 Apr 1995 23:20:03 -0700 From: uhclem%nemesis@fw.ast.com To: freebsd-bugs Subject: bin/309: Do-it-yourself FTP deletes /usr/tmp dir rather than contents Message-ID: <199504090620.XAA05885@freefall.cdrom.com> In-Reply-To: Your message of Sun, 9 Apr 95 01:05 CDT <m0rxq85-0004voC@nemesis.lonestar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>Number: 309 >Category: bin >Synopsis: Do-it-yourself FTP deletes /usr/tmp dir rather than contents >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Apr 8 23:20:02 1995 >Originator: Frank Durda IV >Organization: >Release: FreeBSD 2.0.0-SNAP950322 i386 >Environment: Occurs in SNAP-021095 Still occurs in SNAP-032295 >Description: [FDIV002] During installation, if you specify that you want to do your own FTP commands and have specified more than one distribution (bin, src, etc), FTP is invoked repeatedly to download each module separately. After processing each module, the installation procedure asks if you want to delete the files in /usr/tmp. If you answer this "yes", the installation procedure apparently does a "rm -rf /usr/tmp" (or the equivalent) and when the installation procedure moves on to load the next module, it can't because /usr/tmp is now deleted and the installation is unable to proceed. You get the message "No such file or directory for /usr/tmp, sorry! Please fix this and try" The rest of the message is cut off and the box and shading gets messed-up, probably because the message is too long. Of course, there is no way to fix this since you can't get a shell. If you do a ^Z, it causes the installation process to panic and reboot as does ^C. If there is a way to get to a shell to fix this the now-missing directory, it isn't obvious. This did not happen in 2.0, and I suspect it has to do with the new ability to select multiple modules and something is not re-creating the directory if you answer the above question "yes" or the method used to delete the files in /usr/tmp is too aggressive. In my case, the test system was tight on disk space and could not afford to have the packed distribution hanging around after it was extracted. I was able to get around this on a tight disk space system by answering "No", and once in FTP, !-out to a shell and remove the files in /usr/tmp manually, then resume FTP and download the next batch of files. But this is clumsy, and would not have been possible until after the "bin" distribution was loaded. See FDIV001 for related problems. >How-To-Repeat: Perform an installation and select do-it-yourself FTP downloads and request more than one distribution. After bin is downloaded and you are asked if you want to delete the files in /usr/tmp, answer "Yes". >Fix: Verify that /usr/tmp (or the directory that the user specifies) either does not get deleted or make sure it gets recreated with the same permissions after each module is downloaded and the directory contents removed. By the way, if the user specifies a different directory, the installation process should create it. This doesn't seem to happen if you select something other than /usr/tmp in the first place. Probably /usr/tmp is already there so there is no problem with using it the first time. *END* >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504090620.XAA05885>