Thanks, but the main question is how come the behaviour is still the same whether you pass the flag or not? I would get it if it just failed without "-S" but it works as intended. I am wondering if this is cause I might not be using the GNU version of env, so this is less relevant? Edit: looks to be the version thing indeed, this doesn't work for someone on Ubuntu
At some point coreutils added -S in order to support the behavior of BSD and MacOS. I would guess that whatever implementation you're using then added -S as a noop in order to (at long last) permit the portable usage of multi-argument shebang lines. Until both of those things happened there was no portable way to pass multiple arguments in a shebang. You used to have to do really stupid things (ex https://unix.stackexchange.com/a/399698).
Actually, you might be onto something! If I test with explicit quoting in terminal, BSD and GNU produce the same behavior:(`env 'bash -c "echo hello"'` fails while `env -S 'bash -c "echo hello"'`) works. I wasn't aware of this:
"To test env -S on the command line, use single quotes for the -S string to emulate a single parameter. Single quotes are not needed when using env -S in a shebang line on the first line of a script (the operating system already treats it as one argument)"(from your second link).
This is different for shebang on Mac though:
GNU env works with or without '-S':
#!/opt/homebrew/bin/genv -S bash -v
echo "hello world!"
BSD env works with or without '-S' too:
#!/usr/bin/env -S bash -v
echo "hello world!"
To conclude, looks like adding `-S` is the safest option for comparability sake :).
Modern commercial aviation is extremely safe because of investigators and regulators banning this "well the pilot just fucked up" explanation and instead looking at systemic factors.
As pointed out in the article, if the pilot was so incompetent, why didn't they receive further training, or if truly untrainable, fired? The airline and regulator have the responsibility for doing so, and ending the investigation at "pilot error" guarantees that another incompetent pilot will crash another plane.
I stopped using atop when I found it installs several hooks which automatically run code as root and deposit files around the filesystem, including a "power management" hook.
Do you have any references that describe this behavior? That sounds like exactly the kind of thing that could conceal a backdoor of the sort this seems to be warning about.
> Why aren't you using this logic to argue that they should use Delphi or TurboPascal because Anders Hejlsberg created those?
as you know full well, Delphi and Turbo Pascal don't have strong library ecosystems, don't have good support for non-Windows platforms, and don't have a large developer base to hire from, among other reasons. if Hejlsberg was asked why Delphi or Turbo Pascal weren't used, he might give one or more of those reasons. the question is why he didn't use C#, for which those reasons don't apply.
the contention of your respondents and downvoters is that regardless of your intention, the extra information actually communicated is "i'm an asshole".
More accurately in the context of the comment, its "Im gonna be an asshole to you because I think you don't have the life experience I do", which is at least, some kind of signal.
Yeah, it seems like it could be implemented as a postprocessor of strace --decode-fds. Knowing what each syscall does isn't really the hard part of strace, it's knowing which ones are important, which ones are part of libc itself and can usually be ignored (e.g. collecting /etc/localtime) and which are explicitly requested by the application, piecing together multi-threaded/multi-process logic, etc. strace has a lot of functions to help with that which this doesn't support, like syscall filtering, struct decoding, and stack tracing.
>Knowing what each syscall does isn't really the hard part of strace, it's knowing which ones are important, which ones are part of libc itself and can usually be ignored
An excellent point!
More broadly, since many/most Linux/Unix/etc, programs use one or more libraries (which in turn could use one or more other libraries, etc., etc.), then one very important key for designers of any type of strace program, present or future, is:
Can the traced system calls be set granularly, such that the individual libraries making syscalls (as opposed to the main program!) be identified individually, and possibly filtered in/out from the results accordingly?
Agreed, I'm a bit underwhelmed by intentrace when compared to the richness of strace. For sure, strace could maybe benefit from some UX like colorised output and a TUI that lets you filter syscalls while it is running.
I googled "quebec educational attainment" and found https://statistique.quebec.ca/en/communique/university-gradu..., which says that "Québec has the highest proportion of people aged 25 to 64 with any postsecondary certificate, diploma or degree (71.2%).". According to https://www.statista.com/statistics/467078/median-annual-fam..., Quebec's median annual family income in 2021 was 96,910, almost the same as the median 98,390. The top "provinces" are Northwest Territories and Yukon, whose ways of doing things, for better or worse, cannot be easily copied to other provinces.
They're the same thing. The problem is not the container, it's the H.265 encoded video which Firefox doesn't accept. It's not a good idea to throw raw cell phone video onto a website, first because it probably won't play everywhere, and second because there's embedded high-precision location data.
it would be most convenient to have no 2FA. hell, skip the password too, then nobody will forget theirs. security is tradeoffs, but NIST says "if you take security seriously, you should not use SMS 2FA".
> Not for extended international use; you must reside in the U.S. and primary usage must occur on our network. Device must register on our network before international use. Service may be terminated or restricted for excessive roaming. Coverage not available in some areas; we are not responsible for our partners’ networks.
> AT&T ROAM NORTH AMERICA FEATURE: Allows plan data, talk & text usage with no roaming charges in and to Mexico/Canada. Data: Allows domestic plan data usage in Mexico/Canada.
Eskimo (Singapore telco) has both North America and Global eSIMs.
