I'm pretty sure you've made dumber mistakes in your life, and you seem to be stupid enough to not realize having a full tank of gas isn't always possible for everybody at every time.
But hey, you're showing a great ability there to quickly jump to conclusions without consideration at all. Or were you just looking for an opportunity to say something publicly appealing (to the/. crowd in this case) for the sake of doing so? Talk about requirements for political offices.
Same in Germany, they used to give you a can for a small deposit, didn't get them back and stopped doing it altogether now. One time I ran out of gas, I ended up leaving my entire wallet there to make them believe me that I will actually return the can. Another time they didn't even accept that, so I ended up buying a 2,5L bottle of water, emptied it outside and filled it up with gas. And then they had the nerves to tell me I can't actually do that (fortunately after it was too late). Geez.
Then again, it almost always boils down to filter caps on the PSU. Sure it would be cool to have documentation, but for this common sort of repair I'm okay with flying blind.
It doesn't compile, you cannot use on floating point types. But it's okay. If you fixed that, it wouldn't link, because wtf is println. Fine, though, if you fixed that, it would only break conventions because all caps are usually reserved for macros (and, for some reason, FILE).
So overall, the output is likely a ton of diagnostics.
EDIT(*): I realize now it was a joke. Never mind.
(*) Finally! Thank you so much,/.! This must be some sort of record for the longest-wanted feature on a website that was eventually actually implemented. What I don't get is why it's so subtle and in such an odd position. How about just making it another button next to those that are already there? Is this some sort of UX joke?
why self-signed certificates are equivalent to not using TLS at all on a corporate
So how can your non-admin coworker snoop on your traffic if there's a self-signed cert being used? Are you sure you understand the word "equivalent"?
If you want to know how a computer actually works, you need to understand Von Neumann architecture
Because computers can only use a von Neumann architecture, sure.
There are no "basics about computers"
Of course there are, see below
MESI and related cache coherency protocols [enumeration of arbitrary implementation details]
No, you don't need to understand the last detail of hardware optimization in order to learn how a computer works. Unfortunately for you, while typing that wall of text that's obviously designed to trick a naive reader into believing you knew what you're talking about, you forgot the most basic things that *are* actually required in order to understand how computers work, like boolean algebra, implementations of logic gates and how to arrange those to create things like memory and a CPU. But nice effort anyway.
I did study system administration for Microsoft systems
And it's showing.
enough to get a bit more than halfway to an MCSE
Halfway there before you MustCall Someone Experienced. Keep it up!
As for how operating systems work, what part would you like to know? [Another enumeration of arbitrary shit lacking actual OS basics except memory management and scheduling].
Oh well. Nice effort again. Have you ever considered working in marketing?
I could easily discuss most of the stuff you mentioned with you, and I'm not at all convinced that you're actually an expert in everything you enumerated. If you knew what you're talking about, you would have mentioned way different things.
Maybe you should learn a few things and catch up to me.
I have the feeling that in the area where I'm behind you, I don't want to catch up. I rather learn technical things.
Do you even have a clue how the machine and the software in front of you work
Yes, down to the transistor respective instruction level. I do not have a detailed understanding of the physics that makes transistors work, and I don't know the first thing about microcode.
is Linux just a giant black box that somebody else understands
It's actually turning into pretty much this. I've switched to BSDs 6-7 years ago, because they are as whiteboxish and well-designed as I could find.
which you've ever actually looked too deeply into?
I have a couple dozen patches against NetBSD kernel, userland and pkgsrc, some of them submitted and accepted upstream.
I'll give you that your comment probably would've shut me up if I actually were as clueless as you think I am, so, kudos for your deception skills. Have fun typing the next wall of text to convince me of your expertise. As said before, you seem to be quite the special expert.
You obviously fail to understand what an analogy is. Hint: I wasn't talking about debugging fucking motorcycles.
I do understand, now, why you prefer running a blackbox toy like windows, as well as why you failed to use free software. If this is your profession, it wouldn't hurt to try and pick up a few basics about how computers, networks and operating systems work.
And frankly,
I've managed SSH keys.
I'm not even sure what to reply, but I got a hearty laugh out of this. You're quite the special expert. Keep clicking or tapping your blackbox.
set up a corporate network with active directory domains using an all-Microsoft environment, complete with patch management, group policy, and the like.
There's your problem.
Then replicate that in linux.
Yep, it's hard to replicate such a complete POS infrastructure. Your mind is locked into the Windows world. This is like saying "Have you ever driven a car, with a steering wheel, seatbelts and all -- now try to replicate *that* on a motorcycle.
If you need evidence that unix is fit to run massive scale networks, maybe look at relatively unknown, obscure projects like, say, the Internet.
hard to debug
Harder to debug than AD? Do you even know what debugging means?
So fulfilling, you imagine being stalked on slashdot and start wading through my comments (I suppose the irony is lost on you here) to count how many are replies to yours.
You being happy I have absolutely no issues believing -- that's actually pretty common (see that other guy here with that "Happiness in intelligent people is the rarest thing I know" quote in his sig.). One might think it'd be depressing to be stupid, but (as seems to be the case with you too) stupid people tend to not realize they're stupid -- mainly due to being stupid. So there's nothing unsurmountable in the way on their way to happiness.
Yes, it's easier for you to believe I'm trying to troll you, but I really am not. I genuinely think you're genuinely stupid. Sorry.
Recording the password in plaintext in log files itself is a huge security lapse
If only they were using systemd, avoiding the whole plaintext log files problem.
Your point being?
s/theoretical/hypothetical/
Not to be pedantic, but I don't think pedantic means what you think it means. Hint: I mostly asked questions.
I'm pretty sure you've made dumber mistakes in your life, and you seem to be stupid enough to not realize having a full tank of gas isn't always possible for everybody at every time.
But hey, you're showing a great ability there to quickly jump to conclusions without consideration at all. Or were you just looking for an opportunity to say something publicly appealing (to the /. crowd in this case) for the sake of doing so? Talk about requirements for political offices.
Same in Germany, they used to give you a can for a small deposit, didn't get them back and stopped doing it altogether now. One time I ran out of gas, I ended up leaving my entire wallet there to make them believe me that I will actually return the can. Another time they didn't even accept that, so I ended up buying a 2,5L bottle of water, emptied it outside and filled it up with gas. And then they had the nerves to tell me I can't actually do that (fortunately after it was too late). Geez.
Now why I'm telling you this, I have no idea.
Then again, it almost always boils down to filter caps on the PSU. Sure it would be cool to have documentation, but for this common sort of repair I'm okay with flying blind.
Did I answer them for you?
Can't say that I understand most of what you said, but yes, you did. Thanks.
Magnetism increased in gauss
What does "increased in gauss" mean?
until poles began to form
Are there no poles when only so little magnetism is present?
; with north and south pokes come lines of force, and from these, eddy currents form.
Eddy currents in what? Doesn't a current require some sort of conductor?
These eddy currents are energy.
Ok
This caused the poles to begin to rotate.
The poles create the currents and then those currents cause the poles to rotate? How/why?
Since a stationary magnetic field is not moving (by definition) there was no mass or energy, ergo no universe yet.
Hm
But a rotating magnetic field is moving, so it can create a universe.
Why?
a tangent curve is simply a sine wave as viewed from outside the system.
Could you explain this?
The asymptote(s) appear to be a Big Bang because of this.
We (humans) are simply viewing the universe as a virtual system from outside it.
Can you elaborate on this?
This does away with not only pi
Why?
but also "dark matter/energy".
Why?
I ask you to think about it
Did that, raised the above questions.
Manipulating the next kernel requires root, while manipulating the current kernel requires ring 0.
but then an attacker has all the time in the world to manipulate that next kernel
Blah.
You keep assuming that the author of the unit file has to be the administrator of the server that is to be owned.
Hint: You're mistaken.
It doesn't compile, you cannot use on floating point types.
But it's okay. If you fixed that, it wouldn't link, because wtf is println.
Fine, though, if you fixed that, it would only break conventions because all caps are usually reserved for macros (and, for some reason, FILE).
So overall, the output is likely a ton of diagnostics.
EDIT(*): I realize now it was a joke. Never mind.
(*) Finally! Thank you so much, /.! This must be some sort of record for the longest-wanted feature on a website that was eventually actually implemented. What I don't get is why it's so subtle and in such an odd position. How about just making it another button next to those that are already there? Is this some sort of UX joke?
This sums it up pretty nicely.
Show me the pages in the Unix Haters Handbook
1994
that cover
- bind
Early 1980s
- ntp
1985-1988
- syslog
1980s
- sudo
1980s
they don't exist because the book predates all of those.
Yeah right.
TCP/IP routing
Okay, you said you're not a network engineer.
why self-signed certificates are equivalent to not using TLS at all on a corporate
So how can your non-admin coworker snoop on your traffic if there's a self-signed cert being used?
Are you sure you understand the word "equivalent"?
If you want to know how a computer actually works, you need to understand Von Neumann architecture
Because computers can only use a von Neumann architecture, sure.
There are no "basics about computers"
Of course there are, see below
MESI and related cache coherency protocols [enumeration of arbitrary implementation details]
No, you don't need to understand the last detail of hardware optimization in order to learn how a computer works. Unfortunately for you, while typing that wall of text that's obviously designed to trick a naive reader into believing you knew what you're talking about, you forgot the most basic things that *are* actually required in order to understand how computers work, like boolean algebra, implementations of logic gates and how to arrange those to create things like memory and a CPU. But nice effort anyway.
I did study system administration for Microsoft systems
And it's showing.
enough to get a bit more than halfway to an MCSE
Halfway there before you Must Call Someone Experienced. Keep it up!
As for how operating systems work, what part would you like to know? [Another enumeration of arbitrary shit lacking actual OS basics except memory management and scheduling].
Oh well. Nice effort again. Have you ever considered working in marketing?
I could easily discuss most of the stuff you mentioned with you, and I'm not at all convinced that you're actually an expert in everything you enumerated. If you knew what you're talking about, you would have mentioned way different things.
Maybe you should learn a few things and catch up to me.
I have the feeling that in the area where I'm behind you, I don't want to catch up. I rather learn technical things.
Do you even have a clue how the machine and the software in front of you work
Yes, down to the transistor respective instruction level. I do not have a detailed understanding of the physics that makes transistors work, and I don't know the first thing about microcode.
is Linux just a giant black box that somebody else understands
It's actually turning into pretty much this. I've switched to BSDs 6-7 years ago, because they are as whiteboxish and well-designed as I could find.
which you've ever actually looked too deeply into?
I have a couple dozen patches against NetBSD kernel, userland and pkgsrc, some of them submitted and accepted upstream.
I'll give you that your comment probably would've shut me up if I actually were as clueless as you think I am, so, kudos for your deception skills. Have fun typing the next wall of text to convince me of your expertise. As said before, you seem to be quite the special expert.
You obviously fail to understand what an analogy is. Hint: I wasn't talking about debugging fucking motorcycles.
I do understand, now, why you prefer running a blackbox toy like windows, as well as why you failed to use free software. If this is your profession, it wouldn't hurt to try and pick up a few basics about how computers, networks and operating systems work.
And frankly,
I've managed SSH keys.
I'm not even sure what to reply, but I got a hearty laugh out of this. You're quite the special expert. Keep clicking or tapping your blackbox.
set up a corporate network with active directory domains using an all-Microsoft environment, complete with patch management, group policy, and the like.
There's your problem.
Then replicate that in linux.
Yep, it's hard to replicate such a complete POS infrastructure. Your mind is locked into the Windows world. This is like saying "Have you ever driven a car, with a steering wheel, seatbelts and all -- now try to replicate *that* on a motorcycle.
If you need evidence that unix is fit to run massive scale networks, maybe look at relatively unknown, obscure projects like, say, the Internet.
hard to debug
Harder to debug than AD? Do you even know what debugging means?
Yep, and finally their names will be predictable(*)
(*) Predictable for software(**), not for humans.
(**) Provided the software knows all sorts of details, like, where exactly on what bus the NIC is attached, and so on(***).
(***) i.e. essentially unpredictable(****) for software and for humans.
(****) But we refer to it as "predictable(TM)" anyway.
Unless you have special hardware installed.
Exotic stuff like keyboards, mice and network interfaces, temperature sensors etc? I too am waiting for these to become commonplace.
This particular rocket previously flew in January
Where the fuck is the ambiguity in that?
I think [...]
See, there's the problem.
This particular rocket previously flew in January
It's a little ambiguously phrased
Yeah, reading is hard. That's from TFS, BTW.
I turned 14 in y2k, and I hated this shit with a passion.
So fulfilling, you imagine being stalked on slashdot and start wading through my comments (I suppose the irony is lost on you here) to count how many are replies to yours.
You being happy I have absolutely no issues believing -- that's actually pretty common (see that other guy here with that "Happiness in intelligent people is the rarest thing I know" quote in his sig.). One might think it'd be depressing to be stupid, but (as seems to be the case with you too) stupid people tend to not realize they're stupid -- mainly due to being stupid. So there's nothing unsurmountable in the way on their way to happiness.
Yes, it's easier for you to believe I'm trying to troll you, but I really am not. I genuinely think you're genuinely stupid. Sorry.