it is likely rearranged by systemd, therefore only non-systemd glibc distributions are affected.
systemd doesn't imply installed and running systemd-resolved though. I believe it's usually not enabled by default.
HN user
it is likely rearranged by systemd, therefore only non-systemd glibc distributions are affected.
systemd doesn't imply installed and running systemd-resolved though. I believe it's usually not enabled by default.
Matrix has so-called spaces, which group rooms together. Chaos Computer Club used this for 37C3, it was quite neat.
Actually, this guy lives in Luhansk, active war zone in eastern Ukraine.
They apparently has left Ukraine since the full-scale war broke out, and travelling around the world: Thailand, India, Kazakhstan, etc.
Pseudo-anglicism?
Is it really about light vs. heavy though? I thought it was mostly about multiplexing notifications through a single app (usually through a single connection as well), so only one app has to consume resources constantly, and others might be activated as needed.
I mean, isn't the appeal of a relational DBMS that it is a black box to the user and it's the query planner's job to yield an efficient search for a given goal?
I wish
Just for the record, in Russia, we write all identifiers in English and practically all comments in (sometimes broken) English as well. Russian comments seem heavily discouraged, but hey, it's possible there're places where there're not.
Is this the solution for the infamous "foobar: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by foobar)" problem?
There's also "computed gotos". It's not the same as function pointers, though.
https://eli.thegreenplace.net/2012/07/12/computed-goto-for-e... - article about them being used in CPython
That's an interesting scenario for sure, but "defeats the purpose" is a stretch.
I understand it as a part of "crappy CGI" aesthetic.
I wish it could optionally ignore the info boxes and navbars. They kinda feel like cheating.
Not really. From the website:
Contrary to similar solutions, this application does not intercept SSL connections, minimising privacy risks and allowing for usage on unrooted Android devices. Only the meta data about network communications is logged, and displayed to the users.
It sounds like using systemd is a terrible idea for memory-constrained devices, so you really don’t want to see it in the embedded world.
On the other hand, proper event-driven init system (instead of horrible shell scripts with all sorts of fragile "sleep"s and other hacks) sounds sexy for an embedded system. I sometimes get annoyed how home routers, NAS, etc. are slow to boot up
Though the embedded systems I refer to have much more than 16 MB of RAM, more like 128 and up.
Maybe page cache (the thing tmpfs relies on) doesn't do full copy when reallocation, but rather, roughly speaking, appends extra pages to some sort of linked list? It would explain why it's faster.
You could put epoll fd in non-blocking mode, wrap it with os.NewFile, use SyscallConn() to get syscall.RawConn object, and then use its Read method. Its Read method is special: you can return "not ready", and it will use the Go runtime poller to wait until it's readable, in this particular case effectively putting epoll in a epoll.
In epoll case, using RawConn.Read would look like this:
err := rawConn.Read(func(fd uintptr) bool {
nevents, err = syscall.EpollWait(int(fd), events[:], 0)
if nevents == 0 {
return false // try again
}
return true
})
Note that using RawConn.Read here is only necessary because epoll needs epoll_wait(2) instead of typical read(2). For ordinary file descriptors, like pipes, etc., setting them to non-blocking mode, wrapping them with os.NewFile, and using its ordinary Read/Write methods is sufficient.It really depends. In our case, Gmail rejects our IPv6, but accepts IPv4. The IPs are from university network and they don't have any history other than being used by us. SPF, DKIM and PTR records are in place.
Our system has detected that this message is likely suspicious due to the very low reputation of sending domain. To best protect our users from spam, the message has been blocked. Please visit https://support.google.com/mail/answer/188131 for more information.
This message is extra confusing because mail from said "sending domain" is accepted by IPv4.
Lots of CTF organizers are security researchers. This particular CTF is organized by people from Chaitin Tech, which is a cybersecurity company. They emphasize that their challenges are based on real vulnerabilities (found in their research, I presume).
The QEMU task was likely inspired by a real vulnerability as well: https://mail.gnu.org/archive/html/qemu-devel/2020-09/msg0090... (discovered by CTF organizers, I think)
Isn't it in the vanilla game, though?
Wow, didn't expect to find a reference to RD-Sounds on HN.
Sometimes tautology helps understands acronyms faster, without having to reconstruct context.
In this particular example, I think the error is as specific as it gets, though.
Matrix as well. https://matrix.org/blog/2020/05/06/cross-signing-and-end-to-...
OpenID is a single sign-on protocol built on top of Oauth.
Note that there's older OpenID (without "Connect"), which, to my knowledge, is more or less dead nowadays, and OpenID Connect, which is indeed built on top of OAuth. Both are indeed SSO, though.
Recording the kernel profile with perf would be more useful, I think. strace would probably only show long "unlink" syscall.
AFAIK most of these are DKMS, so compilation (although automated and supported by distro) is still necessary.
Are you sure systemd overwrites it? I believe it maintains its own /run/systemd/resolve/{resolv,stub-resolv}.conf file, and it's up to you whether you want to symlink /etc/resolv.conf to one of these or not.
Isn't direct current component ignored by default just because Ethernet devices are galvanically isolated? I thought even if you applied some DC voltage to Ethernet without proper PoE negotation, nothing would happen at all.
I've seen many sites that generate feed URLs with secret token appended as a query parameter. This token only gives an access to the feed, so this as safe as it gets, and requires no special support on reader app part.