@thisisthebreath@DaemonFools I can't seem to find it, so perhaps its an extension in some versions of find. in that case you can just incorporate a call to "realpath" into that, or use "xargs", or just make it a proper executable shell script
Theres many better and more legible ways to do it, but with that obligatory comment out of the way, I'm quite sure there's an argument to find that gives you the full path instead of relative
@one@Bemf yeah I saw this last night and it disgusted me but I didn't say anything. dude saying "just go we can't do nothing for her" just reeked of "I'm calm, collected, and in control making the hard judgement calls but actually I just want to make sure we save ME" energy. I was expecting from the "dead body" description of the video last night somebody burnt to a crisp, but that lady looked fine. she may have collapsed from smoke inhalation 10 seconds ago. sadly we'll never know
@Kaiserhase@pjbrunet just remembered, furthermore Tusky hardcode blocks entire instances in their source code due to what they feel is wrongthink. so while it may work with NAS today, it might not tomorrow
@CSBHOTSQUAD 🪕 He stopped loving her today... She took the mask off from her face. And soon her shots'll be out of daaaaate... He stopped loving her todayyy 🎶
@CSB I'm reminded of a recent issue, from another team that does the front end parts of our system, where windows does something odd only when you have more than EIGHT monitors. I'm not sure why one would need that many, but anyway he did. finally they said "the software can't be used with more than 8 monitors" lol
@CSB absolutely. writing portable software, even scripts, is quite tricky. even a different version of the same shell could make your script suddenly not work. its unfortunately why everything needs to be tested almost everywhere, unless you can make strict requirements on the end user's environment
@CSB it seems you aren't getting my point of windows being the exception, so go try running your original broken script on every modern operating system besides windows. note that it behaves the same - that is, broken. now compare that to windows, where it works. that's why windows is the exception, not the other way around
@CSB but on every other system they'll behave the same, even if that's not what you intended for to happen. so in that sense, windows is the exceptional case
@CSB I'd say that the other way around, since windows is generally the exception here, but yes. :) basically all modern *nix filesystems are case sensitive, windows/dos as I recall is case preserving but not case *sensitive*.