You can (and should) always check which files will be affected by using ‘ls’ as in my example, before using rm on the same pattern.
rm * will remove files NOT starting with ‘.’ — p...@ehealth.id.au “Two men went up into the temple to pray, one a Pharisee and the other a tax collector.” > On 14 Mar 2021, at 1:02 pm, w...@theprescotts.com wrote: > > Be careful with 'rm' and the asterisk. > rm ._* will remove files with names that start with anything followed by '_' > rm ._ * will remove everything in the directory. > > Will > > On 2021 Mar 13, at 03-13 19:04:16, Peter West <p...@pbw.id.au> wrote: > > If these files are on linux try > > $ ls ._* > > That should show you those files. If there are none you want to keep then > > $ rm ._* > will remove them. > > > > — > p...@ehealth.id.au > “Two men went up into the temple to pray, one a Pharisee and the other a tax > collector.” > >> On 14 Mar 2021, at 8:38 am, Jim DeLaHunt <list+gnuc...@jdlh.com> wrote: >> >> >> On 2021-03-13 13:52, Jim DeLaHunt wrote: >>> …It's probably more correct to think of your non-Mac system as creating >>> these files. Did you publish your Linux file system to the Mac using >>> NetATalk or Samba, and then use the Mac Finder to copy the files from the >>> Mac file system to that published file system? If so, then NetATalk or >>> Samba told the Mac it supported storing metadata, when the underlying Linux >>> file system did not have a way of storing metadata. Thus perhaps NetATalk >>> or Samba created these "._*" files as a workaround for storing the file >>> metadata.… >> >> >> On 2021-03-13 13:59, Stephen C. Camidge wrote: >>> No Jim. I copied my files on my Mac to an external FAT32 (I think it is >>> called) drive and opened it in Linux. >> >> >> In that case, Mac system software is probably what handled reading and >> writing with the FAT32 disk. So, it is probably correct to say that the Mac >> software created these "._*" files. But the situation is the same: the FAT32 >> file system doesn't support storing metadata, so the thing bridging the >> differences between the Mac world and the FAT32 world probably created these >> files, to store metadata that was attached to the files on the Mac. >> >> —Jim DeLaHun >> >> _______________________________________________ >> gnucash-user mailing list >> gnucash-user@gnucash.org >> To update your subscription preferences or to unsubscribe: >> https://lists.gnucash.org/mailman/listinfo/gnucash-user >> If you are using Nabble or Gmane, please see >> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. >> ----- >> Please remember to CC this list on all your replies. >> You can do this by using Reply-To-List or Reply-All. > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
