News for hackers. Stuff that matters.

markps

Assumption? So you were lying when you said you had a “concrete fact”?
Re:Starlink Direct to Cell on Sunday November 24, 2024 @08:28PM (#42232312)
Have you looked into AWS Ground Station? I don’t know if it’s economical, or has enough locations for 24/7 access, but it might be better than once an orbit.
Just so no one gets discouraged, there is no 10 year limit. You can get BasicMed as long as you’ve held a 3rd class medical after July 14, 2006.

https://www.faa.gov/licenses_certificates/airmen_certificati...

When I was about 15, my dad and I volunteered to help strip cable and waveguide off giant dishes in a decommissioned radio-free zone north of Boulder. The material was donated to a local amateur radio club and was mostly recycled as scrap metal.

I was given some wrenches, a harness, a few carabiners and some rope. I have to say, hanging off those bottom supports with nothing below me was one of the most exciting times of my life!

Re:Once upon a time, memory allocators made sense on Monday January 18, 2016 @04:24PM (#10927073)
You're correct. I do agree with the point, but I misinterpreted where he was going with that example.
Re:Once upon a time, memory allocators made sense on Monday January 18, 2016 @03:47PM (#10926800)
> If the fork() call succeeds, this means the OS has guaranteed that all the memory in the child process is available to be written over. i.e. it has had to allocate 'lots of memory' x 2 in total, even if only 'lots of memory' x 1 will actually be used.

That isn't the case anymore, at least on Linux and BSD. fork() uses a copy-on-write scheme so the OS only allocates/copies the parent memory space if the child attempts to write to it.