I think the point was that either udev could be forked or an older version of it could be kept kicking around for servers, and that network-manager wouldn't be needed at all. Device and network client configuration can be done via conf files with minimal effort (especially in context of a managed deployment via Puppet or the like). I agree, by and large. I'd argue that we could even do without udev, if it didn't take more effort to live without than to live with it.

I've used the site longer and reserve the right to use Doctor Who references where I'm suspicious of technical details, especially as relate to timing vulnerabilities. This is allowed, as per The Hacker's Dictionary. Bonus points for finding the Doctor Who references included.

That was pretty much my interpretation as well. Which would be great for ad-hoc encrypted tunnels - the source and destination can have keys that are valid only until the tunnel's authentication expires (typically hourly) and where the encryption is based on the identity the other side is known by. Ad-hoc tunnels need to generate keys quickly and efficiently, but also don't need to be super-secure. In fact, they can't be.

If RIBE isn't useful in ad-hoc, then you'd end up having to ask when it would be useful.

Anything that depends on a third party, including PGP/GPG with keyservers, is vulnerable to some form of compromise, SSL/TLS certificates all have a third party signer and Kerberos depends on all kinds of behind-the-scenes work being secure. However, although they're imperfect, they're considered adequate for what they do. Well, except for SSL, perhaps.

RIBE presumably therefore also has a niche where it's good. Rapid key turnover is what's wanted for conversation-based protocols with timeouts. That makes RIBE sound promissing for IPSec ad-hoc and SSL, as it makes store and crunch by attackers less likely to work. But is that the right niche?

Do you want high-risk open-heart surgery, with a fifteen-per-cent risk of dying during the operation, or would you rather continue as you are, with a fifty-per-cent chance you will be dead in two years?

Open-heart surgery, please. You can actually feel your heartbeat, and thinking there's a problem means every irregularity, real or imagined, is going to give you a start. This gets especially fun when you're trying to sleep because that, after all, involves heartbeat slowing down.

NO!!! This is just plain bullshit. I do NOT object to a term for electrical power. I simply asserted a physical truth: in our isolated system, the electrical power to the heat source, called for by Spencer, has zero dependency on the chamber walls.

It is this nonsense dependency on the chamber walls that I have disputed, nothing else. That is a violation of the Stefan-Boltzmann law.

So just to be clear: I don't object to a term for "electrical power" and never have. My only objection is your insistence that the power input to the heat source is somehow related to radiation from the chamber walls. If these are treated as gray bodies: just no. That's a violation of Stefan-Boltzmann.

You are VERY good at trying to make it appear I have been saying things I actually haven't. But it isn't going to fly. It's just bullshit.

NO!!! Repeat, for about the 100th time now: no NET radiative power input from cooler objects. That is ALL I have claimed, and it's a direct result of the Stefan-Botlzmann radiation law. Why do you keep disputing textbook physics laws?

Stop lying. Because that's all you're doing now.

MAD prevented WWIII. I don't care whether the people who build them or the people who authorize their construction are corrupt, or worship a giant statue of a sexually aroused Beelzebub, the fact is that we are kept largely secure from would be Napoleons, Hitlers and Stalins by the mere fact that these weapons exist.

When it hurts to get out of bed and you can't go and do what you want when you want?

Isn't this true for most people most of the time?

Who said anything about open source? Even the old direct Unix server variants all ran Bourne shell or c shell and their descendants. For chrissakes, a CLI-based server OS running a scriptable shell is decades old, predating Windows and FOSS by decades. This idea that Server 2012 is doing anything unique boggles the mind of anyone with even a basic understanding of operating system development and administration for the last half century. Maybe the Microsoft-funded diploma mills churn out admins who actually believe that Server 2012 is some revolutionary step, but for those of us who have been in the industry for oh, over seven or eight years, seeing somebody claim "we tossed out *nix and put in Server 2012 'cause it wuns with just a CLI" is liking seeing some fuckwit claim "I just invented the toothbrush!"

If you threw out *nix servers because you like the modern Windows toolset, then great! No prob. I have a network that runs a Server 2012 AD domain and a couple of Hyper-V servers, so it's not like I'm allergic to Windows. But fuck man, reading the parent's post (I dunno, maybe it's your post, I can understand why you would go AC to write such an incredible retarded post), with the underlying notion that Server 2012 is doing something revolutionary, and yeah, I start seeing red. Server 2012 is merely Microsoft, after twenty fucking years, getting the fucking hint.

Can you be specific here? What on a basic net install of Debian or CentOS does not fit your criteria? Christ, the base install of Debian doesn't even come with Samba.

Windows sysadmins amaze. For fifteen years I listened to them rattle on about how the GUI in Windows NT and its descendants was absolutely necessary, that it opened up servers to people who couldn't or wouldn't learn how to work from a CLI. So a few server distros put the head on their installs, worked like mad dogs to build GUI and web-based management systems like Webmin, and now suddenly all those Windows sysadmin flunkies are declaring Server 2012 is the bestest ever because you can run in headless with a CLI.

Listen you fucking asshole. *nix has been running CLI longer than most people posting here have been alive. It had mature toolsets and script libraries when Windows was a 16-bit cooperative multitasking layer on top of fucking MS-fucking-DOS. Generations of system administrators have lived and fucking died while Windows was forcing a clunky GUI toolset that you couldn't fucking script properly, and that you ended up having to go to REGEDIT and a bazillion GPO entries to fine tune.

Oh no, but Windows is so fucking cutting edge because in the last seven or eight years has developed a fucking shell that you can properly fucking script (even if the scripting language in question is a verbose and unbelievably slow executing piece of shit that is in almost every way the exact opposite of the elegance of *nix).

Well congrat-u-fuck-ulations Mr. "We paid a bazillion dollars to Redmond in licensing fees so we could have a scriptable CLI-based OS in our data center". I bet you even think you did an amazing thing.

Fucking Windows admins. Arrogance, stupidity and a total lack of knowledge of their own fucking operating systems incredibly dubious history as a Server OS.

Meanwhile, in the time it takes you to type out the name of a Powershell scriptlet and its arguments to import a CSV and puke it out as a SQL script, I can do write the code in awk or Perl in a bash wrapper. But hey, I must be stupid and you must the be the super fucking genius.

If you want a real thin install, pick something like Gentoo and Slackware. You can build minimal installs from the kernel up. In ye olden days when I was working on pretty minimal hardware (low RAM, slow CPUs, small drives), I used to install minimum base on top of a very small kernel (only the hardware found on the machine, plus a few generic IDE drivers just in case I had to move the HD and fire it up on another computer). It's a pain in the rear, and with even low-end hardware having huge amounts of RAM and storage space, I don't bother.

The whole point of the net install version of Debian is that it installs a very base version of Linux; and then you build on top of it. If you really need some sort of unique kernel variant, most fine tuning can be done in /boot or /proc.

I'll be blunt, if you claim to be a sysadmin who works with Linux, and you don't know how to build an optimized small footprint server, then you're talking bullshit, and whoever has hired or contracted you should give you the boot really fast.

... I'm going to die at 112.

It will be in a gunfight over a 26 year old woman. I'll still be a quicker draw than her husband, but my gun will jam.

....Big Band.

Never mind. Wrong kind of Stardust.