Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment Re:Did you even read the notice? (Score 1) 385

The change DOES also apply to the usual stuff like HP Proliant DL380 etc.

Yup, we got the same mail today. We have a bunch of ageing Proliants, and are currently engaged in a procurement round for a new generation of servers (we buy them by the ton, almost). Guess which company just ruled themselves out of the process?

Comment *facial* (Score 1) 336

Sounds like the kind of domain name which would trigger these nanny-state filters some countries are so fond of nowadays. But let's be clear on this - is in no way involved with bukkake porn involving minors and there is no record known to myself of any of their senior management being on any form of sex offender registry.

Comment Re:hmm (Score 1) 154

Similar here, at my previous job... except irony of ironies, while even the manager and sales droids were very happy with their Macs, the Photoshoppers were Windows only.

Meanhile at my current job, where the developer workstations are pretty much all Linux, I am looked down upon because my laptop of choice comes pre-installed with a certified UNIX OS.

(Posting from my home desktop Linux right now BTW, in case anyone wants to accuse me of being a hipster).

Comment Re:Speed is not everything (Score 1) 268

Last time I was in Japan, I had a good connection, but the ISP decided to drop every ssh connection above a given traffic. My tunnels kept being broken until I set a speed limit on my side.

Was that a DSL connection with an ISP-supplied router, or maybe a cable TV ISP? With optical fiber I've never had any problems, SSH sessions stay open for days (and this is without a fixed IP address), and p2p "just works". This is in Tokyo, BTW.

Comment Blog post from one of the core team members (Score 2) 100

Do please check out this informative post from Magnus Hagander, one of the PostgreSQL core team members, which clarifies most of the points raised here:

About security updates and repository "lockdown"

I have received a lot of questions since the announcement that we are temporarily shutting down the anonymous git mirror and commit messages. And we're also seeing quite a lot of media coverage.

Let me start by clarifying exactly what we're doing:

  • We are shutting down the mirror from our upstream git to our anonymous mirror
  • This also, indirectly, shuts down the mirror to github
  • We're temporarily placing a hold on all commit messages

There has been some speculation in that we are going to shut down all list traffic for a few days - that is completely wrong. All other channels in the project will operate just as usual. This of course also includes all developers working on separate git repositories (such as a personal fork on github).

We are also not shutting down the repositories themselves. They will remain open, with the same content as today (including patches applied between now and Monday), they will just be frozen in time for a few days.


What this country needs is a good five cent ANYTHING!