Pretty sure the 'less filling/tastes great" thing was Miller Lite
Whichever it was, it wasn't a "this is bad/this is good" type argument. And it was both informative and educational. To this day, we all remember that whatever beer this was, it tasted great and was less filling, even if it was neither.
Don't forget to manually update all the patches that should be part of a service pack before connecting to the network. Especially the ones that patch the Windows Update service that fix errors where Windows Update can be tricked into downloading and installing anything from anywhere.
Sorry, but psexec-ing into SMB is not the same.
While I'm talking about sysinternals tools, maybe a 64 bit version of psinfo? Psinfo -s still only shows the 32 bit programs installed on a system, ignoring the 64 bit versions.
"How does systemd remind you of windows? Have you actually *used* either in a system administration capacity?'
YES, yes I have. Windows with it's registry and svchost reminds me ALOT of systemd.
Worse still, Microsoft has the manpower to pull this off.
What is a Linux with systemd in comparison but a village fool who sees an aeroplane an tries to construct one for himself from old bicycle parts and scrap wood?
I wouldn't call the registry and svchost an airplane. Perhaps a television set? Not quite a suicide booth.
You don't get taxed based on your net worth; it's "income tax" for a reason. How much taxable income does he receive a year (not counting this tax break)?
the President can stop it from becoming a law in the first place by vetoing the bill. Laws do not exist until the President agrees to the bill. He had equal footing in passing laws as the Congress, in that regard.
And congress can override the executive veto with two-thirds majority of both house and senate.
Am I the only one who thinks that Congress is to blame here (for passing sloppy legislation), not the IRS or The Government?
Allowing an action, mandating an action, and performing an action are all separate things. Congress didn't mandate this action (for which the IRS could be viewed as ethically blameless as long as they sought ways to mitigate damage). According to the summary, the action was allowed, so while not legally culpable, the IRS can be blamed for poor ethics by choosing to exercise power in this fashion. Congress is to blame for one thing (allowing this activity), and IRS the other (choosing to engage in this activity).
Cutting greenhouse gasses by 40% will also cut jobs by 40%.
This is fallacious reasoning. You could replace some of the current energy production with human power: pushing a flywheel for room, board, and $1.50/hour. Unemployment would drop to nil! Of course productivity would reduce because overall energy production would be much less, but jobs are how the government measures economic success right now.
but the kernal and start-up are still black magic to me.
SysV init is really quite simple. Just a few minutes playing around with it on a system and you'll get the hang of it. First off, there are several run-levels. Let's focus on just one run-level for now since most people only ever edit one (they'll use run-level 0: shutdown, and run-level 6: reboot, unknowingly). Within each runlevel directory (let's choose/etc/rc5.d/) are symlinks that point to the scripts in/etc/init.d/, and these symlinks are named with S for start or K for kill, followed by a number for the order they should be executed in, followed by the script name (for readability's sake; it doesn't need anything beyond the S/K##). When starting or ending a run-level (booting/shutting-down), init goes through the simlinks in order and runs the init scripts they point to with either "start" or "stop" as parameters. The scripts handle the peculiarities of the various daemons, and act as an easily configurable startup mechanism that allows the sysadmin to fine-tune things. For example, if a server's system clock fails, ntpd will refuse to update because the clock-skew is too great ("2014!? But it's currently 2002 according to the system clock."). So, a sysadmin can write a little hack for ntpdate at the beginning of the "start" function in ntpd's init script. Mind you, this is a poor example, but easier to explain than any I could come up with quickly.
Maybe an init system can be simple. I don't understand why even shell scripts are needed. Seems like they should be the exception, not the rule.
Editing init scripts is the exception, but because it happens enough times, the scripts should exist as a rule. Scripts allow for high-configurability while keeping some level of separation. The things ntpd does on startup could be parameters, and even the above ntpdate functionality (which is considered bad form in the ntp world: trusting the network time too greatly) could be compiled into the ntp daemon. But who wants to include every hack every sysadmin comes up with for their own environments in the main codebase for ntpd? And who amongst all the sysadmins wants to recompile ntpd for every change and essentially maintain their own fork? Not to mention the differences between distributions for configuration file locations, log files, etc. It's much easier to use scripts as that happy medium where sysadmins can edit without need for constant recompiles.
Why not one big super-script then...
Seems like configuration should be a single file that lists the programs to start from top to bottom
...this violates the separation principle. And would be slightly annoying too. It's easier to handle the individual scripts for their respective daemons than it is to isolate the section that is needed, and as pointed out before, a mere list of executable paths isn't enough, even with parameters; not configurable enough. Let's say you make a change on server 1's init script for ntpd. Now you want to copy that configuration to all 10,000 servers you have. Easy-peasy for a specialized init-script (assuming they're all the same distro and version): just copy the file to every machine and restart ntpd. But with a monolithic script, if you copy it to every machine, you'll be copying entries for daemons that the other servers might not have, or worse: removing entries for vital daemons on the target servers. Keeping them separate is best. Just as keeping them highly configurable is best.
They could just take all of their DC Animated Universe stories and convert them to live action. The writers for the DCAU seem to know how to grab a comic book audience. The DC live action movie writers don't want to make a fun comic book movie. They want to make a work of art based on a comic book series.
My gradnfather fought in a real war. From what he told me, it was nothing like this.
Some great uncles of mine were on the beach at Normandy. One of them got a blueprint copied directly from his entire left leg. He survived, but only because a quick thinking medic was able to replace it with a pin-up from the landing craft. He still gets compliments on that leg.
"Unlikely contagious" is an acceptable risk for a lesser disease, one that doesn't usually kill its host. But she and the CDC should have recognized that even a slight risk of spreading this thing is unacceptable. She should have quarantined herself.
Even worse: she's a nurse. She felt there was a chance she might have Ebola, so much that she called the CDC. She didn't err on caution. Forget the CDC's (non)answer. She knew what she was doing was risky. Even if no one gets infected, she had better talk to a lawyer about all the "mental anguish" lawsuits she'll soon be subjected to.
Slashdot Mirror
as informative as an old Bud Light commercial
Pretty sure the 'less filling/tastes great" thing was Miller Lite
Whichever it was, it wasn't a "this is bad/this is good" type argument. And it was both informative and educational. To this day, we all remember that whatever beer this was, it tasted great and was less filling, even if it was neither.
Don't forget to manually update all the patches that should be part of a service pack before connecting to the network. Especially the ones that patch the Windows Update service that fix errors where Windows Update can be tricked into downloading and installing anything from anywhere.
iexplore.exe
FTFY
Sorry, but psexec-ing into SMB is not the same.
While I'm talking about sysinternals tools, maybe a 64 bit version of psinfo? Psinfo -s still only shows the 32 bit programs installed on a system, ignoring the 64 bit versions.
"How does systemd remind you of windows? Have you actually *used* either in a system administration capacity?'
YES, yes I have. Windows with it's registry and svchost reminds me ALOT of systemd.
Worse still, Microsoft has the manpower to pull this off.
What is a Linux with systemd in comparison but a village fool who sees an aeroplane an tries to construct one for himself from old bicycle parts and scrap wood?
I wouldn't call the registry and svchost an airplane. Perhaps a television set? Not quite a suicide booth.
You don't get taxed based on your net worth; it's "income tax" for a reason. How much taxable income does he receive a year (not counting this tax break)?
the President can stop it from becoming a law in the first place by vetoing the bill. Laws do not exist until the President agrees to the bill. He had equal footing in passing laws as the Congress, in that regard.
And congress can override the executive veto with two-thirds majority of both house and senate.
Manspider, Manspider,
Can do any human like jerb
Surfs the web, posts trolling lies
Uses chopsticks to catch flies
Look Out!
Here comes the Manspider!
Am I the only one who thinks that Congress is to blame here (for passing sloppy legislation), not the IRS or The Government?
Allowing an action, mandating an action, and performing an action are all separate things. Congress didn't mandate this action (for which the IRS could be viewed as ethically blameless as long as they sought ways to mitigate damage). According to the summary, the action was allowed, so while not legally culpable, the IRS can be blamed for poor ethics by choosing to exercise power in this fashion. Congress is to blame for one thing (allowing this activity), and IRS the other (choosing to engage in this activity).
Or your brain tumors, as it were.
Cutting greenhouse gasses by 40% will also cut jobs by 40%.
This is fallacious reasoning. You could replace some of the current energy production with human power: pushing a flywheel for room, board, and $1.50/hour. Unemployment would drop to nil! Of course productivity would reduce because overall energy production would be much less, but jobs are how the government measures economic success right now.
Green is now red for purposes of traffic law. Red remains red. Yellow is still Procede With Caution. Release the hounds.
Ego.
>IBM still obtains boku bucks
The word you're looking for is "beaucoup." You seem super-high.
Might have been trying to say "goku". That would make GP super-saiyan.
I'm a web programmer who loves Linux,
Welcome.
but the kernal and start-up are still black magic to me.
SysV init is really quite simple. Just a few minutes playing around with it on a system and you'll get the hang of it. First off, there are several run-levels. Let's focus on just one run-level for now since most people only ever edit one (they'll use run-level 0: shutdown, and run-level 6: reboot, unknowingly). Within each runlevel directory (let's choose /etc/rc5.d/) are symlinks that point to the scripts in /etc/init.d/, and these symlinks are named with S for start or K for kill, followed by a number for the order they should be executed in, followed by the script name (for readability's sake; it doesn't need anything beyond the S/K##). When starting or ending a run-level (booting/shutting-down), init goes through the simlinks in order and runs the init scripts they point to with either "start" or "stop" as parameters. The scripts handle the peculiarities of the various daemons, and act as an easily configurable startup mechanism that allows the sysadmin to fine-tune things. For example, if a server's system clock fails, ntpd will refuse to update because the clock-skew is too great ("2014!? But it's currently 2002 according to the system clock."). So, a sysadmin can write a little hack for ntpdate at the beginning of the "start" function in ntpd's init script. Mind you, this is a poor example, but easier to explain than any I could come up with quickly.
Maybe an init system can be simple. I don't understand why even shell scripts are needed. Seems like they should be the exception, not the rule.
Editing init scripts is the exception, but because it happens enough times, the scripts should exist as a rule. Scripts allow for high-configurability while keeping some level of separation. The things ntpd does on startup could be parameters, and even the above ntpdate functionality (which is considered bad form in the ntp world: trusting the network time too greatly) could be compiled into the ntp daemon. But who wants to include every hack every sysadmin comes up with for their own environments in the main codebase for ntpd? And who amongst all the sysadmins wants to recompile ntpd for every change and essentially maintain their own fork? Not to mention the differences between distributions for configuration file locations, log files, etc. It's much easier to use scripts as that happy medium where sysadmins can edit without need for constant recompiles.
Why not one big super-script then...
Seems like configuration should be a single file that lists the programs to start from top to bottom
...this violates the separation principle. And would be slightly annoying too. It's easier to handle the individual scripts for their respective daemons than it is to isolate the section that is needed, and as pointed out before, a mere list of executable paths isn't enough, even with parameters; not configurable enough. Let's say you make a change on server 1's init script for ntpd. Now you want to copy that configuration to all 10,000 servers you have. Easy-peasy for a specialized init-script (assuming they're all the same distro and version): just copy the file to every machine and restart ntpd. But with a monolithic script, if you copy it to every machine, you'll be copying entries for daemons that the other servers might not have, or worse: removing entries for vital daemons on the target servers. Keeping them separate is best. Just as keeping them highly configurable is best.
We know how to induce fusion via a multitude of methods. The thing is, none of them are net positive in energy production. None. Of. Them.
H-bombs are fairly net positive. Slightly uncontrolled, but it's a start.
"Flight is a scientific impossibility." - Dr. Cornelius, Archaeologist.
That has been Marvel's secret since they first started. Marvel has always been about the human side of the masks.
Yes. DCAU, along with Jeffrey Combs, took the Question and made him into a star.
And created Harley Quinn from whole cloth.
Who knew Shaquille Oneal could act? The only thing I don't get was he also played Steel.
The internet isn't some zone that is free from libel and slander laws just because "it's on a computer."
They could just take all of their DC Animated Universe stories and convert them to live action. The writers for the DCAU seem to know how to grab a comic book audience. The DC live action movie writers don't want to make a fun comic book movie. They want to make a work of art based on a comic book series.
My gradnfather fought in a real war. From what he told me, it was nothing like this.
Some great uncles of mine were on the beach at Normandy. One of them got a blueprint copied directly from his entire left leg. He survived, but only because a quick thinking medic was able to replace it with a pin-up from the landing craft. He still gets compliments on that leg.
"Unlikely contagious" is an acceptable risk for a lesser disease, one that doesn't usually kill its host. But she and the CDC should have recognized that even a slight risk of spreading this thing is unacceptable. She should have quarantined herself.
Even worse: she's a nurse. She felt there was a chance she might have Ebola, so much that she called the CDC. She didn't err on caution. Forget the CDC's (non)answer. She knew what she was doing was risky. Even if no one gets infected, she had better talk to a lawyer about all the "mental anguish" lawsuits she'll soon be subjected to.