From owner-freebsd-arm@freebsd.org Tue Jun 14 15:53:21 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0EF0DAF2CAD for ; Tue, 14 Jun 2016 15:53:21 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D0C552D46 for ; Tue, 14 Jun 2016 15:53:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id u5EFc61f066002 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 14 Jun 2016 08:38:07 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id u5EFc652066001; Tue, 14 Jun 2016 08:38:06 -0700 (PDT) (envelope-from fbsd) Date: Tue, 14 Jun 2016 08:38:05 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Shell or mv eats a period? Message-ID: <20160614153805.GB50221@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2016 15:53:21 -0000 During a recent update of freebsd-arm on an rpi2 I happened to type root@ns1:/boot/msdos # ls bootcode.bin fixup_cd.dat readme start_cd.elf ubldr config.txt fixup_x.dat rpi2.dtb start_x.elf fixup.dat licence.bro start.elf u-boot.bin To prepare for upgrading from r494499, I then typed root@ns1:/boot/msdos # mv rpi2.dtb rpi2.dtb.old root@ns1:/boot/msdos # ls bootcode.bin fixup_cd.dat readme start_cd.elf ubldr config.txt fixup_x.dat rpi2dtb.old start_x.elf fixup.dat licence.bro start.elf u-boot.bin Note that the renamed file has lost the first dot. Next, the new file was copied into position: root@ns1:/boot/msdos # cp /boot/dtb/rpi2.dtb /boot/msdos root@ns1:/boot/msdos # ls bootcode.bin fixup_cd.dat readme start.elf u-boot.bin config.txt fixup_x.dat rpi2.dtb start_cd.elf ubldr fixup.dat licence.bro rpi2dtb.old start_x.elf root@ns1:/boot/msdos # It's happened twice so far, so it's unlikely to be a wetware error 8-) Can anybody tell me what happened? thanks for reading, bob prohaska