Frankly, leaving your DNS with the registrars has been a non-starter for close to a decade now. They're notoriously slow at adding features to their DNS management, hilariously inept at making new "marketing directed" changes to the DNS page (in order to lock you in better), etc. The dedicated DNS companies are a better choice because they have to compete on value/features specifically related to DNS.
(We switched away to DNSMadeEasy years ago, but they don't yet do DNSSEC on "primary" domains. Which are domains where you manage the authoritative records via their web interface. If you want DNSSEC, you need to setup a public DNS server and then make DNSMadeEasy servers your secondaries.)
Try doing RSS in Thunderbird, which might be closer to what you want. From what I recall, you can choose to keep the RSS feeds in a single folder, or split them by feed, plus all the easy things like marking / emailing.
Anything multi-core from 2006 onward is probably fine. That means the Athlon64 X2s, the Core Duos, etc. I know I was purchasing 45W and 65W AMD CPUs around 2006-2007 which run cool and quiet.
The multi-core machines also age well because they have at least 2 physical cores to handle both processing and the UI. In fact, my primary laptop is still a T61p Core2 Duo @ 2.2GHz. It has a SSD and was upgraded to Win7 Pro and 8GB last summer. So we purchased that laptop in 2007 and I plan on using it for at least another year or two.
Sure, an Intel i5 or i7 would be nice, but it still handles everything I throw at it for systems administration, programming and other tasks.
No, a P4 is not perfectly usable. Not unless it was one of the rare breed that came with 2 cores or one of the rarer SMP setups with two chips.
There's a huge and noticeable difference in responsiveness between the old single-core P4s and the slightly newer (2006-onward) chips that are dual-core. Multi-core chips and multi-CPU setups age well, single-core chips never have.
In fact, multiple core systems age so well that we immediately jumped on them (AMD X2 64bit) back in 2006 when they started dropping below $200. Those 2006-2007 era machines are still very viable, although we're in the process of refreshing them with Win7, 4GB RAM (or 6-8GB) and Intel 330 SSD series drives. We expect to keep using those 2007 era machines up through 2015-2017 unless something breaks horribly on them.
Total cost for the refresh was $75 for the SSD, about $150 for the Win7 Pro upgrade license and $30 in RAM. Which gets us machines that can probably run another 3-6 years. Better then spending $500 or so on a new white box, and the SSDs were optional (but we got a good price on 120GB units).
Starting around 2014-2016, we'll likely replace them with 4-8 core machines at higher clock rates, more RAM, new SSDs, etc. and go another 10 years. Which might end up just being an operating system install and motherboard / CPU / RAM swap.
Political repression is worse than any other country in the world. People often spy on each other for the slightest signs of disloyalty, and the government not only punishes offenders, but also punishes three generations of their families in order to purge their tainted blood.
Basically, if you screw up, they take you, your family, your relatives, etc.
Most of their soldiers don't want to be in the military. There are a lot of desertions to go back home where they have a better chance of getting fed.
You must have missed the whole point of the "military first" (songun) concept in NK, where the military gets fed in preference to the citizens. Especially during the Arduous March of the late 90s.
Eh, the famine of the late 90s shot a lot of holes in the brainwashing. But the secret police in North Korea are still extremely effective so you can't expose to anyone that you are a non-believer (not unless you want you, your family, and extended relatives shipped off to someplace unpleasant).
Not cultural, but more one of cost per square meter. Land is expensive, therefore it becomes economic to build vertically instead of sprawl horizontally.
Java has that stuff too... at which point you throw AspectJ or some sort of code-injection at it and make all the template / boilerplate code go away.
Basically, if you have a function which needs to be logged, you can just name it a certain way so that the Aspect can match it, or you can annotate it with @SomeAnnotation. Either way, it eliminates a ton of boilerplate code (cross-cutting concerns).
And you're fucked when they change all the URLs a year from now. You know, just in case you decided to document in your code base where you got that calling syntax from, or a link to further reading on an esoteric call.
Things also go missing. You will find something this week, only to find it missing with the next update to the website.
This is their biggest sin by far in terms of documentation.
Used to be that their URLs were nice, short and made sense. Then they rewrote everything and broke all the URLs just so they could do some weird frame in a frame nonsense that went against most web UI standards.
The suits in charge of the documentation web at MS are clueless, each one wants to put their own stamp on things by rewriting everything during their tenure.
I gave up trying to bookmark anything at Microsoft.com a decade ago (also about the point I started moving away from Microsoft for all software where possible). Instead, if it's absolutely vital reference documentation, it gets printed to a PDF file and stored locally.
They're not the only sinners in that regard, way too many other companies around the web constantly shuffle their documentation URLs around, breaking all the old links.
Main advantages that XP brought over 2000 was better compatibility and game/media support. The big one for me was that XP supported WiFi out of the box with a standard UI. Prior to XP, you had to deal with every different manufacturer of WiFi cards having a different control UI / drivers / software. Which made support a nightmare unless you standardized on a single WiFi card.
I like Win7, it's definitely the successor to XP in pretty much everything, plus it does 64bit well for those 4+ GB systems. Or those of us who actively use 8-32GB of RAM and were feeling the pinch under XP.
I look at it the other way. If you're a start-up and short on cash, go CentOS or SciLinux. Then you always have the option to move seamlessly into the RHEL world once you can fund things. Or use RHEL on the public servers where support contracts matter and CentOS on the internal servers.
Might also be easier to find data center / hosting providers who will rent you a RHEL box then a Debian box.
Sounds a lot more like "Freenet". And you'll run into the many of the same issues with Freenet as you'll run into with this new proxied torrent system.
I don't see why we'd need 128-bit time if we're counting seconds, considering that 64-bit time gets us up to 20 times the current age of the universe
Moving to 128bits, you would definitely no longer count in seconds but probably in 1 millionth or 1 billionth of a second. Or even finer resolution then that (use the lower 64bits for sub-second resolution).
OpSys and small files (such as programming stuff) on the SSD, then a 2nd larger magnetic bulk drive for media. Or store the bulky stuff on a central NAS unit.
The most important thing is to make good backups of the SSD (Acronis, Ghost, other backup software). They can and will fail at the worst moments, so it's a good idea to be able to quickly restore from backup.
The problem with that is that modern SSDs, I think, when left offline for extended period of time can lose their contents. I've heard that number is around 3 months or so for modern units? Older units with larger feature size were more resilient.
Dr McNinja has good art, but isn't as good at telling a story. When reading through the panels, you're often left with the feeling that you're missing at least half the story. Note that it's improved slightly in the past few month.
The usual answer is "run 2 copies of SSHD". One that listens on the public address and only allows key-based authentication (and runs on a non-standard port) with a 2nd copy that runs on the internal network and allows password based authentication.
If you're tired of your log files filling up with errors from dictionary attacks, do the smart thing - get off of the default port. That alone will reduce the number of attacks against your SSH service by 2-3 orders of magnitude.
(Banning by IP address doesn't work. Most attackers now use botnets where each individual bot in the network only attacks your system a handful of times.)
Combine non-standard port with key-only authentication and you're mostly worry free. Unless someone can steal your SSH private keys, at least.
Slashdot Mirror
Frankly, leaving your DNS with the registrars has been a non-starter for close to a decade now. They're notoriously slow at adding features to their DNS management, hilariously inept at making new "marketing directed" changes to the DNS page (in order to lock you in better), etc. The dedicated DNS companies are a better choice because they have to compete on value/features specifically related to DNS.
(We switched away to DNSMadeEasy years ago, but they don't yet do DNSSEC on "primary" domains. Which are domains where you manage the authoritative records via their web interface. If you want DNSSEC, you need to setup a public DNS server and then make DNSMadeEasy servers your secondaries.)
Try doing RSS in Thunderbird, which might be closer to what you want. From what I recall, you can choose to keep the RSS feeds in a single folder, or split them by feed, plus all the easy things like marking / emailing.
Anything multi-core from 2006 onward is probably fine. That means the Athlon64 X2s, the Core Duos, etc. I know I was purchasing 45W and 65W AMD CPUs around 2006-2007 which run cool and quiet.
The multi-core machines also age well because they have at least 2 physical cores to handle both processing and the UI. In fact, my primary laptop is still a T61p Core2 Duo @ 2.2GHz. It has a SSD and was upgraded to Win7 Pro and 8GB last summer. So we purchased that laptop in 2007 and I plan on using it for at least another year or two.
Sure, an Intel i5 or i7 would be nice, but it still handles everything I throw at it for systems administration, programming and other tasks.
No, a P4 is not perfectly usable. Not unless it was one of the rare breed that came with 2 cores or one of the rarer SMP setups with two chips.
There's a huge and noticeable difference in responsiveness between the old single-core P4s and the slightly newer (2006-onward) chips that are dual-core. Multi-core chips and multi-CPU setups age well, single-core chips never have.
In fact, multiple core systems age so well that we immediately jumped on them (AMD X2 64bit) back in 2006 when they started dropping below $200. Those 2006-2007 era machines are still very viable, although we're in the process of refreshing them with Win7, 4GB RAM (or 6-8GB) and Intel 330 SSD series drives. We expect to keep using those 2007 era machines up through 2015-2017 unless something breaks horribly on them.
Total cost for the refresh was $75 for the SSD, about $150 for the Win7 Pro upgrade license and $30 in RAM. Which gets us machines that can probably run another 3-6 years. Better then spending $500 or so on a new white box, and the SSDs were optional (but we got a good price on 120GB units).
Starting around 2014-2016, we'll likely replace them with 4-8 core machines at higher clock rates, more RAM, new SSDs, etc. and go another 10 years. Which might end up just being an operating system install and motherboard / CPU / RAM swap.
Simply put, they're worried about the big US army that's been stationed there, just as they were during the Korean War.
I'm not sure how roughly 30,000 US troops counts as a "big" army.
At least, when compared with the roughly 640,000 active South Korean troop count. Or China's roughly 2.2 million active duty personnel.
Not insane, just mindful of the consequences.
Political repression is worse than any other country in the world. People often spy on each other for the slightest signs of disloyalty, and the government not only punishes offenders, but also punishes three generations of their families in order to purge their tainted blood.
Basically, if you screw up, they take you, your family, your relatives, etc.
And you have spent too much time drinking the propaganda (which exists on both sides, in copious quantities).
Most of their soldiers don't want to be in the military. There are a lot of desertions to go back home where they have a better chance of getting fed.
You must have missed the whole point of the "military first" (songun) concept in NK, where the military gets fed in preference to the citizens. Especially during the Arduous March of the late 90s.
Eh, the famine of the late 90s shot a lot of holes in the brainwashing. But the secret police in North Korea are still extremely effective so you can't expose to anyone that you are a non-believer (not unless you want you, your family, and extended relatives shipped off to someplace unpleasant).
they'd be trying to support a front line with starving soldiers and prisoners with pack-bikes by then, and that would not last for long.
So, sort of like how the northern viet supplied their front lines during Vietnam? And how did that turn out?
Not cultural, but more one of cost per square meter. Land is expensive, therefore it becomes economic to build vertically instead of sprawl horizontally.
Java has that stuff too... at which point you throw AspectJ or some sort of code-injection at it and make all the template / boilerplate code go away.
Basically, if you have a function which needs to be logged, you can just name it a certain way so that the Aspect can match it, or you can annotate it with @SomeAnnotation. Either way, it eliminates a ton of boilerplate code (cross-cutting concerns).
Not sure what the equivalent in C# or C++ is.
And you're fucked when they change all the URLs a year from now. You know, just in case you decided to document in your code base where you got that calling syntax from, or a link to further reading on an esoteric call.
Things also go missing. You will find something this week, only to find it missing with the next update to the website.
This is their biggest sin by far in terms of documentation.
Used to be that their URLs were nice, short and made sense. Then they rewrote everything and broke all the URLs just so they could do some weird frame in a frame nonsense that went against most web UI standards.
The suits in charge of the documentation web at MS are clueless, each one wants to put their own stamp on things by rewriting everything during their tenure.
I gave up trying to bookmark anything at Microsoft.com a decade ago (also about the point I started moving away from Microsoft for all software where possible). Instead, if it's absolutely vital reference documentation, it gets printed to a PDF file and stored locally.
They're not the only sinners in that regard, way too many other companies around the web constantly shuffle their documentation URLs around, breaking all the old links.
Main advantages that XP brought over 2000 was better compatibility and game/media support. The big one for me was that XP supported WiFi out of the box with a standard UI. Prior to XP, you had to deal with every different manufacturer of WiFi cards having a different control UI / drivers / software. Which made support a nightmare unless you standardized on a single WiFi card.
I like Win7, it's definitely the successor to XP in pretty much everything, plus it does 64bit well for those 4+ GB systems. Or those of us who actively use 8-32GB of RAM and were feeling the pinch under XP.
Newer versions of Postgres, Postfix, Dovecot... to name just a few (that I either go to a 3rd party repo or build from source).
I look at it the other way. If you're a start-up and short on cash, go CentOS or SciLinux. Then you always have the option to move seamlessly into the RHEL world once you can fund things. Or use RHEL on the public servers where support contracts matter and CentOS on the internal servers.
Might also be easier to find data center / hosting providers who will rent you a RHEL box then a Debian box.
Sounds a lot more like "Freenet". And you'll run into the many of the same issues with Freenet as you'll run into with this new proxied torrent system.
I don't see why we'd need 128-bit time if we're counting seconds, considering that 64-bit time gets us up to 20 times the current age of the universe
Moving to 128bits, you would definitely no longer count in seconds but probably in 1 millionth or 1 billionth of a second. Or even finer resolution then that (use the lower 64bits for sub-second resolution).
Depends on whether you got a flu shot or the fluemist. The nasal spray uses a weakened version of the virus.
OpSys and small files (such as programming stuff) on the SSD, then a 2nd larger magnetic bulk drive for media. Or store the bulky stuff on a central NAS unit.
The most important thing is to make good backups of the SSD (Acronis, Ghost, other backup software). They can and will fail at the worst moments, so it's a good idea to be able to quickly restore from backup.
The problem with that is that modern SSDs, I think, when left offline for extended period of time can lose their contents. I've heard that number is around 3 months or so for modern units? Older units with larger feature size were more resilient.
But I can't find my notes and may be wrong.
Dr McNinja has good art, but isn't as good at telling a story. When reading through the panels, you're often left with the feeling that you're missing at least half the story. Note that it's improved slightly in the past few month.
The usual answer is "run 2 copies of SSHD". One that listens on the public address and only allows key-based authentication (and runs on a non-standard port) with a 2nd copy that runs on the internal network and allows password based authentication.
If you're tired of your log files filling up with errors from dictionary attacks, do the smart thing - get off of the default port. That alone will reduce the number of attacks against your SSH service by 2-3 orders of magnitude.
(Banning by IP address doesn't work. Most attackers now use botnets where each individual bot in the network only attacks your system a handful of times.)
Combine non-standard port with key-only authentication and you're mostly worry free. Unless someone can steal your SSH private keys, at least.