Just set your ulimit to a reasonable number of processes per user and you'll be fine.
Zoidberg
Freedom paper! 8.5"x11". There's also legal for when you're in trouble or spending a ton of money: 8.5"x14".
Phew. For a second there I thought the book would be about Bluetooth in Linux.
So what's the problem? They're blaming her for keeping up-to-date on topics she was teaching.
You can still read the contents of the directory because you have -r
on it. If you just run ls foo
you'll see your file on there, no problem.
However, without -x
you cannot read metadata in that directory. That's why all information about the file shows as question marks.
And the same enlightened kids who are so aware about discrimination and gender fluidity (which is good) are the ones discriminating against others because they don't have an iPhone.
How did you manage with video performance? I don't game and have had a lot of experience with both vbox and kvm. Kvm performance for video is excruciatingly slow. It got to a point I said "that does it" and went back to vbox.
I like tailscale and have been testing it for a few months. I'm also using headscale as the control plane.
Unfortunately the android client is somewhat unreliable. It works most of the time but once in a while, connections to your tailnet will fail for a bit and require retries. If you ping a machine in your tailnet during this problem, it will show packet loss and then start working after a few pings. This unfortunately makes it difficult to have a reliable split DNS setup.
I've done everything to try and understand what happens without success. It seems like state is lost somewhere and a few packets flowing will fix it. Running a constant ping from Android to my tailnet "fixes" the problem, but is not a great workaround.
Just something to keep in mind before you jump headfirst.
I have to say my faith in signal has been shattered since I got crosstalk on a signal conversation. I still can't imagine how that's possible but it was there, clear as day.
Back when Google started, the idea was to only show discrete text ads on search. Then they started showing image ads and created AdSense which basically shows Google ads on external pages. The real killer was when Google bought doubleclick. Until then Google didn't do ad tracking but with dclk (which has a tracking cookie) things went downhill fast. Ever wonder why Google ads domains are (or used to be) doubleclick.net? Because changing the domain would make Google lose all those yummy doubleclick tracking cookies.
There are many examples in software engineering. You have probably encountered many of them online and didn't even notice.
For example, a website that under load starts to serve cached content only. If more load is imposed it will stop serving ads and on yet more load it will render fewer articles per page, etc.
It's one of those things that when you're doing it right people will think you're not doing anything at all.
Starring: Jeffrey Combs as the Jefferies Tubes.