D
Don Y
Guest
On 1/13/2022 11:00 AM, bob prohaska wrote:
Don\'t worry about \"useful amounts\"! My network cables are \"labeled\"
A, B, C, D, E... up through several *punctuation* symbols (ran out
of letters). There\'s a little \"card\" I keep next to each switch
that explains:
Identifier Length Hostname
All you really care about is: \"Is this the card that I want?\"
As to how to identify when installed... <shrug>
But, may help with the identify when installed issue (at least
if the device is powered up AND a console is easily accessible).
I have a database that tracks the contents of my media so I can
look for a particular file and sort out where it resides. You
might be able to do the same by
ls -alR > filelistN.txt
and
grep <filesought> filelist*.txt
But, I still have to physically hunt for \"medium #381\". (so, discipline
comes into play, eventually)
Don Y <blockedofcourse@foo.invalid> wrote:
On 1/12/2022 7:27 PM, bob prohaska wrote:
Don Y <blockedofcourse@foo.invalid> wrote:
I ended up settling on 64G microSD cards. They are physically
tiny and everyone can use them in a phone, tablet, etc. once
they\'ve taken the delivered data off. So, they don\'t become
discards like the thumb drives would!
Have you come up with a decent way to label them, which doesn\'t
get in the way of actually using them in a reader or other device?
If so please post your method. My best efforts have all failed.
My first guess would likely be a Sharpie? Depending on how much
you want to write on them. I assume you\'ve tried this? Does the
ink not adhere? Or, is *re*labeling them the problem?
Speaking only of microSD, my handwriting isn\'t good enough to put
useful amounts of legible text on them and it can\'t be read when
they\'re in use, such as in Raspberry Pi systems that are running.
Don\'t worry about \"useful amounts\"! My network cables are \"labeled\"
A, B, C, D, E... up through several *punctuation* symbols (ran out
of letters). There\'s a little \"card\" I keep next to each switch
that explains:
Identifier Length Hostname
All you really care about is: \"Is this the card that I want?\"
As to how to identify when installed... <shrug>
Thin \"Scotch\" tape tags sort of work, but off the roll they\'re
too wide to fit the socket, tend to come off and frequently have
exposed adhesive when folded onto itself imperfectly. That last
problem leads to cases where labels attach themselves to moving
objects, causing them to diffuse away from where they\'re put down,
leading to vast confusion.
Putting a readme file on the disk certainly identifies it, but
doesn\'t help with the initial \"which one do I want\" problem.
But, may help with the identify when installed issue (at least
if the device is powered up AND a console is easily accessible).
I have a database that tracks the contents of my media so I can
look for a particular file and sort out where it resides. You
might be able to do the same by
ls -alR > filelistN.txt
and
grep <filesought> filelist*.txt
But, I still have to physically hunt for \"medium #381\". (so, discipline
comes into play, eventually)
I guess the only answer is greater discipline in handling the cards.....
Thanks for writing,
bob prohaska