Feb 2012
whatsnew.txt | Mar 2012 | Jan 2012

raspberrypi.org

2012/02/29 07:00 Category: foss | IT | english
Right now the IT team of raspberrypi.org is faced by the devastating penalties of using ancient and crapware technologies like Linux, Apache, and PHP. Then they resort to last minute panic and workarounds.

Forbidden                                                        
                                                                                                                        
  You don't have permission to access / on this server.                                                                



    Apache/1.3.37 Server at www.raspberrypi.org Port 80


My advize? nginx and FreeBSD.

UPDATE: their retailers didn’t fare too well either, and for the very same reason.

Premier Farnell -> Linux -> Apache/2.2.17 Unix mod_ssl/2.2.17 OpenSSL/1.0.0d DAV/2 PHP/5.3.5
RS Components -> Linux -> Apache

Note that RS’s first line of webservers is an NT4 with IIS. It’s the only one that works.

%TCPIP-E-MAPNOSYS

2012/02/27 10:14 Category: IT | english
OpenVMS NFS server configuration hint:

TCPIP> show map
            Dynamic Filesystem Map
Pathname Logical File System
 
/storage    DKB0:
/dka300     DKA300:


%TCPIP-E-MAPNOSYS, file system is not mapped



TCPIP> show map
            Dynamic Filesystem Map
Pathname Logical File System
 
/dkb0        DKB0:
/dka300      DKA300:


Works. Go figure. Or not.

sixxs is a piece of shit

2012/02/16 10:26 Category: foss | IT | english
I had a sixxs.net IPv6 tunnel. Turns out that I forgot to update this one service with my new e-mail address, and they have automatically disabled it. That shouldn’t be a problem, according to the relevant entry in the FAQ I should contact them. I did.

Gabucino> Greetings, Please reactivate my account (userid here). I forgot to update the e-mail address.
Jeroen Massar> Please see the FAQ on bouncing emails.
G> I did. The FAQ points to: ”SIXXS handles For updates to information in SixXS handles, provide SixXS with the details.” So here, I'm providing.
J> You are not providing anything. Please actually read the FAQ and provide the requested details.

Well I wonder what else do they need?

  • Always include clear descriptive information about your problem or inquiry.

It could hardly be any clearer.

  • Always provide your NIC handle and if applicable the Tunnel or Route IDs you wish to discuss.

I did.

  • Use the email address you have provided in your handle as that is what we use as a contact handle.

Clearly that is not possible.

  • Provide details of the setup, type of connections, where NATs are located.

Makes no sense for this type of problem.

  • Provide information of your OS type, version and release (ie. uname -a), noting also the distribution name.

Uh-huh.

  • Include full interface, routing and firewall tables.

Will not, because there are no problems there.

  • Include the list of firewall and anti-virus software you have installed / are running (note that under Windows some 'firewall' tools don't understand IPv6 at all and thus just throw it away, only uninstall helps for those cases).

Can’t figure why I’d need to do this.

  • Include a IPv4 and IPv6 traceroute to the PoP in question.

It does not work.

  • Check with Wireshark or tcpdumps of the interface over which the tunnel runs.

For the lulz let’s suppose I did.

  • Use -n (numeric) as an option and don't filter returning ICMP which could also come from routers between your endpoint and the PoP and also use -s 1500 so that one gets the full packet.

Wow totally cool advize bro!

  • The status of the PoP is listed on the PoP Status page, if it is marked down there we are aware of the issue and we will try to resolve it as soon as possible. Additionally other issues are listed in the Ticket Tracker.

Good to know!

  • We are not your personal helpdesk

Thanks you made that abundantly clear.

AVOID