Erico Mendonca

Looking again at the issues on the original project, it appears that this reader has many, many problems with different proposed solutions: https://github.com/nfc-tools/libnfc/issues/646 https://github.com/nfc-tools/libnfc/issues/691 https://github.com/nfc-tools/libnfc/pull/678 I'll look into getting it...

> And here is an example of building the NFC script with a patch: > > [main...fix-clone-reader](https://github.com/wizzomafizzo/mrext/compare/main...fix-clone-reader) Interesting, I got it to work with this version, but it's acting a...

I was in process of compiling libnfc with debug, when I remembered to check the udev messages. Whenever there was an error on nfc.sh, I got quite a few unbind/remove...

And plugging the reader to a computer, I can see that 200mA is its standby current after initializing the reader, going up to 400mA when reading a card. So, there...

Thanks. I'll link your script on the README.

I made a script to evaluate what fields can be used based on these samples. My experience with enterprise distros would suggest using CPE, which is guaranteed to be unique....

Further analyzing, we have 25 unique NAME tags: ``` erico@suselab-erico:~/Projetos/distrobox> egrep "NAME" summary.txt | sort | uniq --> NAME=[AlmaLinux] --> NAME=[Alpine Linux] --> NAME=[Amazon Linux] --> NAME=[Amazon Linux AMI] -->...

So, it would boil down to something like this: ``` #!/bin/bash DISTRO_NAME=$(egrep "^NAME=.*" ${1}| cut -d\= -f2-) if [[ ${DISTRO_NAME} =~ "Ubuntu" ]] || [[ ${DISTRO_NAME} =~ "Debian" ]]; then...

And of course, if there are exceptions, like suppose there 4 versions of CentOS and one of them doesn't support DNF... test the other fields, preferrably PRETTY_NAME and then VERSION,...

> Thanks for thinking about this! > > Only problem I see is supporting unknown distros > > For example, `wolfi` vs `alpine`, both use `apk` but different /etc/os-release >...