From owner-freebsd-arm@freebsd.org Tue Jun 14 16:08:01 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 4A451B6A143 for ; Tue, 14 Jun 2016 16:08:01 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2D0AA2785 for ; Tue, 14 Jun 2016 16:08:00 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 36bb05e1-324a-11e6-8929-8ded99d5e9d7 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.34.117.227 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Tue, 14 Jun 2016 16:08:20 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.14.9) with ESMTP id u5EG7wub001380; Tue, 14 Jun 2016 10:07:58 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1465920477.1188.142.camel@freebsd.org> Subject: Re: Shell or mv eats a period? From: Ian Lepore To: bob prohaska , freebsd-arm@freebsd.org Date: Tue, 14 Jun 2016 10:07:57 -0600 In-Reply-To: <20160614153805.GB50221@www.zefox.net> References: <20160614153805.GB50221@www.zefox.net> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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 16:08:01 -0000 On Tue, 2016-06-14 at 08:38 -0700, bob prohaska wrote: > 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_c > d.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_c > d.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.e > lf 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 A FAT filesystem enforces that there is only a single dot in a filename. Welcome to 1983. -- Ian