farva

For an example of more malicious interference, see https://en.wikipedia.org/wiki/Captain_Midnight_broadcast_sig...

Block up-converter (BUC) at uplink site (in this case, likely part of a VSAT terminal or Satellite Internet "antenna") takes L-Band (950-1525mhz) input via cable, converts it to C-band uplink (5850-6425mhz) frequency, and transmits to satellite. Satellite then rebroadcasts verbatim at C-band downlink frequency (3400-4200mhz). Except that one of the inputs didn't have a cable or filter attached so it picked up a GSM signal at 936-960mhz. This caused interference on the satellite.

TLDR: Unterminated input port at satellite uplink site acted as antenna, picking up nearby cell tower by accident. Fix: put a terminator on the port.

I agree that we shouldn't be too quick to label every potentially unfair situation as discrimination. But part of the original intent (Ajit Pai notwithstanding) of the USF was to bring quality service to rural and low income areas, so AT&T should be careful to fulfill their obligation and, ideally, the government should hold them to it.

That would be all well and good if they didn't collude with the local authorities against competition and collect "universal service" funds from the government in exchange for, at most, the barest minimum effort. Either be a benevolent monopoly (no such thing IMHO) or compete in a free market.

Ford pardoned Nixon without him being convicted. Amnesty is a pardon given to a group of people, rather than an individual.

All this effort put into making low latency networks and what are they used for? Uselessly siphoning money and destabilizing markets.

I've repaired dozens of laptops and the one thing the broken power connectors had in common was being soldered directly to the motherboard instead of using a separate assembly.

The standard barrel connector protects against short-circuiting with a simple plastic ring. The magsafe connector requires a fucking microcontroller.

Pulseaudio did not work on DragonflyBSD. At all. Hence the removal. A feature that doesn't work isn't really a feature, is it?

Wouldn't that be a CNC lathe?

Surely *BSD accounts for more than 0.0001% of UNIX-like servers.

Fast food is more of a luxury...if you want the best value on food then go to the grocery store.

The OpenFirmware system used on old Macintosh and Sun machines used an extended FORTH for the bootstrapping and hardware management. FreeBSD's bootloader has a similar system as well.

Rob Landley (former Busybox developer) begs to differ.

See http://landley.net/notes-2011.html#13-11-2011 http://landley.net/notes-2011.html#15-08-2011 http://landley.net/notes-2009.html#15-12-2009

Haven't they suffered enough?

AT&T and Sun did a good job of rendering Unix irrelevant during the "Unix Wars". Microsoft hedged their bets with Xenix until it became clear that wasn't the way forward.

It's possible (at least with the HN7000 ku-band system) to put a Hughesnet dish on a tripod and point it yourself (with the proper tools and knowledge). You'd need to get it from a dealer that allows self-installs (Hughesnet won't sell you equipment without a professional installation), such as Montana Satellite.

This document, especially section 1.6: Incorrect Uses seems to inadvertently make a good case against the inflexible (and short-lived) "worm" logo. Or maybe that's just me.

If you're relying on DNS for security, you're doing it wrong.

No doubt the usual Cisco strategy will be followed: embrace, neglect, extinguish.

Have a look at abduco as well. It's a (IMHO) more user-friendly (and supposedly cleaner) dtach replacement, from the author of dvtm.

It's available on the Internet Archive: https://web.archive.org/web/20120913081458/http://www.africa...

Looks like it was moved to the National Parks Service website: http://www.nps.gov/afbg/index.htm

You would think they'd have engineered at least some basic wear leveling in. I guess it didn't occur to them at design time that it might survive as long as it has.

I used to use tmux, now I use dvtm and dtach with the following alias:

  alias vtmux="dtach -A /tmp/dvtm -z -e ^s -r winch dvtm -m ^a"

Peruvians will suffer, but the elephants will be alright and that's all that matters.

There's been a lot of discussion about the minimal set of primitives to build an interpreter in the Forth community (for instance https://groups.google.com/d/msg/comp.lang.forth/KHw28PKZXUk/.... ) Particularly interesting is eForth, a Forth made to be easily ported while still having acceptable performance, and Minimal ANS Forth, a heavily-commented ANS compliant Forth written in Forth (both of these use significantly more than the minimum for practical reasons.) The answer, for both Lisp and Forth, is somewhere between 8 and 11. In "real world" usage, the set of primitives largely depends on the hardware you're targeting and how well you need it to perform.

Surprised SICP isn't mentioned.

Shaka, when the walls fell.