HN user

t90fan

60 karma
Posts0
Comments27
View on HN
No posts found.

associated with open source software for digital object repository systems and that Red Hat could use the name when it was clearly associated with open source computer operating systems.'

If it's as worded, I'm surprised Fedora Directory Server didn't end up being a problem for RedHat, as its not an OS, and you could call it a digital object repository system, I guess.

Or maybe thats why they re-branded it as 389 Directory Server?

we had a 20 TB ballpark (so I would guess many tens or even hundreds of billions of rows for sure) postgres database at a place I worked in ~2015, hosted on-prem, I don't recall it causing them too much hassle, main thing I remember was the server had an very large amount of RAM (512GB which was loads and loads back then), and lots (for the time) of cores, something like 16, but was otherwise a fairly standard ~£50k ballpark piece of HP kit.

I can't remember exactly what the use case was but we used at my old work (Start up providing a Web CDN/WAF type service, think the kind of stuff CloudFlare does nowadays) in ~2013 for some sort of batch processing analytics/billing type job, using MRJob and AWS Elastic Map Reduce over a seriously large data set.

The performance of PyPy over CPython saved us loads and loads time and thus $$$s, from what I can recall.

Running regular incremental repairs is the norm, as nodes will from time to time have trouble talking to each other due to real world network reasons, or will go down, for things like OS patching. We had a (daily) cron job for it. I come from the software side not the DBA side of things but my main advice from running Cassandra at scale in production (it was part of an Apigee stack) is don't basically! It was very not realisable, would consume huge volumes of memory (especially during repairs), bandwidth (doing a repair is very chatty as it has to sync lots of data) and disk space (tombstoning meant deleted records take up space until compaction runs), and was generally not much fun to manage, and it was difficult to hire people who knew much about it to do so. I would not build a solution myself using it going forward. We also had to periodically (weekly) do "full" repairs to work around Cassandra bugs, silent data corruption etc...

Aside from the whole, well... lack of HTTPS support in any browser you could possibly use on that OS. Also in Win95. And Win98. But regardless...

Use a proxy running on your LAN.

The proxy connects to the site over modern HTTPS (i.e. TLS 1.2 or whatever) and you connect to the proxy over plain HTTP, or whatever old version of HTTPS your client supports (NT4 sp6 with IE6 supports TLS1.0 or SSL3, as the latest, dunno about win 98), if you make sure to trust its cert.

Containers are 2 (20ft) or 4 (40ft) tonnes (roughly) unloaded.

And they can (if I remember right) contain 20 tonnes or so, of cargo.

Our current chinooks can handle 10 tonnes, and the old models could carry 4, if I recall.

And probably less in desert heat.

So helicopters will not be moving any containers

Well, on account there isnt really a working AD or SMB implementation, little printing support, and most NICs arent supported (also: no wireless at all), then I would say there is little attack surface :)

Do you have a 3rd party bootloader installed? OR non-apple hardware?

You get that error if you are not using the official apple firmware/UEFI bootloader - I saw it a few releases ago when trying to do an install on a machine with an opensource bootloader

You will also get it on hackintoshes (OSX on x86 PCs)