Again, it seems to me if you have someone with the ability to kill sshd on your server, killing sshd on your server, your problems lie elsewhere then " Man I really wish I had some automated way of restarting that when my retardard brother billo kills it using sudo".
I've been a sysadmin for many years and can safely say that _never_ once in all my jobs on all of my systems has a processed *just died* and was capable of being restarted while dismissing the reasons it died in the first place.
In fact, many times restarting the job without human intervention would have led to some pretty serious consequences.
In all, if you have a process dying - shouldn't you be looking at why it's dying and not how to restart it?
Hard codes port numbers. Uses non-descript variables. Forces interpretations one way without allowing changing. Hard codes directory structures. Has to write a monitoring program to monitor his daemons and restart on failures instead of just spending more time making sure his daemons are solid to begin with. Here's a note: If you need a different tool to restart your process when it fails, perhaps you should consider looking into why the process failed in the first place?
Because you can get a support contract which effectively transfers blame from the low guy on the totem pole to the company providing the support.
Somewhere in the mix, the CEO looks to the CTO/CIO to get problems fixed. When the problems don't get fixed, the CTO looks to the management who look to the workers who look to the support contract.
If you're a worker bee in such a company, or even management, it behooves you add this job security cushion into the mix.
I'd normally call such people who need to resort to calling support "incompetent" due to the fact that most larger companies I work for simply default to calling support, but there are times where such calls are necessary because you just can't know everything.
I'm a bigtime gnome user too, but I've broken down for two things:
#1. Amarok #2. Kopete
I used to use konsole as well, but then gnome-terminal stopped sucking ass. Installing the libs is totally worth it if you're tired of the pidgen shitfest or annoyed by lack of standard options in the current gnome media player.
I don't think you're emphasizing enough just how much bandwidth a newsgroup infrastructure consumes. Once you're doing binaries, and dabbling in 99% retention for any amount of days, you have yourself tremendous bandwidth and server requirements (IO/Spindles, mainly) that could quickly turn an ISPs profit into the red if they decided to keep doing it and not charge for some tiers of service.
The basic stuff like the text, completion and retention is hard enough without binaries. This is why most places (Comcast, et. al.) outsource their newsgroups to giganews - the barrier to entry is substantial.
While I'm sure you enjoy being able to prepare and cook your favorite Peking Duck variation while opening OpenOffice, Koffice will provide competition and hopefully some innovation on the code side which is next to impossible to get into openoffice using your standard submit patches procedures. It can be the coolest and tightest integration/innovation in the entire niche and Sun won't accept it unless you kiss their ass. This, and they accept shitty, buggy internal patches from half assed coders from their own staff (but I repeat myself) all the time. You would welcome this change if you had any idea that OO was just a semi-shiny turd.
You know if you took a few seconds to research something you're writing - or even speaking - about, it may help others think you're not such a dumbass. You might even up your intelligence. Alas, this is slashdot. The barrier of entry for intelligence here is so low, you don't even need to remember your username to post.
(That's a link, you can click it and it will take you to another place on the internet). As you can see, QT4 is ported to Windows, and other non-x11 OSs. In an amazing twist of coincidences, Koffice is written in QT4.
In larger companies IT is where computers n00bs go to die. It is likely an entirely different department from, say, Sysadmins or DBAs or networking, whose sole purpose is to:
A. Unpack and install desktops when they arrive. B. Help Betsy with her resolution in the acct. dept. C. Call IBM when _anything_ on your laptop fails, get a ticket number and handle the outbound/inbound shipping of your laptop. D. Reformat your machine when there are any issues.
On another perspective, the one of behavior, predictable patterns are weaker than randomized one, because the external world is subjected to chaotic changes and because you will never catch by surprise a competitor who's studying you. So a degree of randomness is likely an evolutionary advantage.
It can also be selected against evolution-wise. If you had predictable patterns, a predator of comparable evolution-al tendencies would evolve to exploit such behaviors.
"These technical issues are now completed at a core level in our engine, and now that we have the systems working, looking ahead to 2008, we expect the PS3 versions of our titles to ship day and date with our other versions," [CEO David Zucker] said.
I'm going to refrain from answering authoritatively, as all I do is read the malling list to learn. I would think, though, based on what I've seen, that the work hasn't been done in terms of pluggability. The work has been done it patches for applying different schedulers, but I suspect making it modular is a substantially different beast.
Most african countries have populations that can't stop killing each other! It's a bit of an undertaking to get them to stop killing species of lesser distinction, if you will.
You're right, AFAICT, but you've missed the emphasis on "more" code. From what I've read, the scheduler's tentacles touch just about every portion of vital linux code and making something "pluggable" on the order of this would require an enormous amount of effort - effort that would be pointless for all but very small minorities that can apply a patch easily.
Indeed, it's also been showing (RTFML) that scheduler improvements are mostly trivial and generally don't warrant such an effort.
Finally, one must consider that the enormous amount of bugs being introduced by touching so many different areas and applying different algorithms in different cases.
Maybe this is something for consideration with the 3.x branch (Of which Linus has no intention of making), but it seems like a reasonable decision so far given the data.
Outside of rare exceptions, GMT should be used on servers, so this shouldn't affect many people. It'd be quite absurd for any application to rely on the time the server gives out as the applications time. An application should be server agnostic and able to handle an environment where servers could be geographically distributed. By application, I mean a DB, website, etc.
You're fooling yourself if you think that FDIC insured is going to be worth more than two squirts of piss when the day comes that ING fails. If a depression or stagflation take it down, that $100,000 likely won't buy you a loaf of bread based on current circumstances.
I'm not trying to chicken little here, I'm just trying to say that "If something could take ING (and similiar banks) down, that something is going to have widespread effects on many, many, more things".
Slashdot Mirror
Actually, it seems to me that you can thank the Turks for that one.
Again, it seems to me if you have someone with the ability to kill sshd on your server, killing sshd on your server, your problems lie elsewhere then "
Man I really wish I had some automated way of restarting that when my retardard brother billo kills it using sudo".
I've been a sysadmin for many years and can safely say that _never_ once in all my jobs on all of my systems has a processed *just died* and was capable of being restarted while dismissing the reasons it died in the first place.
In fact, many times restarting the job without human intervention would have led to some pretty serious consequences.
In all, if you have a process dying - shouldn't you be looking at why it's dying and not how to restart it?
Good solid code outside of the fact that he:
Hard codes port numbers.
Uses non-descript variables.
Forces interpretations one way without allowing changing.
Hard codes directory structures.
Has to write a monitoring program to monitor his daemons and restart on failures instead of just spending more time making sure his daemons are solid to begin with. Here's a note: If you need a different tool to restart your process when it fails, perhaps you should consider looking into why the process failed in the first place?
Because you can get a support contract which effectively transfers blame from the low guy on the totem pole to the company providing the support.
Somewhere in the mix, the CEO looks to the CTO/CIO to get problems fixed. When the problems don't get fixed, the CTO looks to the management who look to the workers who look to the support contract.
If you're a worker bee in such a company, or even management, it behooves you add this job security cushion into the mix.
I'd normally call such people who need to resort to calling support "incompetent" due to the fact that most larger companies I work for simply default to calling support, but there are times where such calls are necessary because you just can't know everything.
I was thinking more like 640Kp. Because it seems like 640k%s is enough for everyone.
I would have to say I agree with him on the kiosks, who has anything better than this?
The camera is easily worth that. I'd keep it in a case and give it to your grandchildren, it may make them bloody rich.
There are games on the ps3?
I'm a bigtime gnome user too, but I've broken down for two things:
#1. Amarok
#2. Kopete
I used to use konsole as well, but then gnome-terminal stopped sucking ass. Installing the libs is totally worth it if you're tired of the pidgen shitfest or annoyed by lack of standard options in the current gnome media player.
I don't think you're emphasizing enough just how much bandwidth a newsgroup infrastructure consumes. Once you're doing binaries, and dabbling in 99% retention for any amount of days, you have yourself tremendous bandwidth and server requirements (IO/Spindles, mainly) that could quickly turn an ISPs profit into the red if they decided to keep doing it and not charge for some tiers of service.
The basic stuff like the text, completion and retention is hard enough without binaries. This is why most places (Comcast, et. al.) outsource their newsgroups to giganews - the barrier to entry is substantial.
0.3 GB (2%) of 13 GB
(Alright, alright, I paid for storage for picasaweb)
While I'm sure you enjoy being able to prepare and cook your favorite Peking Duck variation while opening OpenOffice, Koffice will provide competition and hopefully some innovation on the code side which is next to impossible to get into openoffice using your standard submit patches procedures. It can be the coolest and tightest integration/innovation in the entire niche and Sun won't accept it unless you kiss their ass. This, and they accept shitty, buggy internal patches from half assed coders from their own staff (but I repeat myself) all the time. You would welcome this change if you had any idea that OO was just a semi-shiny turd.
You know if you took a few seconds to research something you're writing - or even speaking - about, it may help others think you're not such a dumbass. You might even up your intelligence. Alas, this is slashdot. The barrier of entry for intelligence here is so low, you don't even need to remember your username to post.
Here, check this out:
http://en.wikipedia.org/wiki/Qt_(toolkit)
(That's a link, you can click it and it will take you to another place on the internet). As you can see, QT4 is ported to Windows, and other non-x11 OSs. In an amazing twist of coincidences, Koffice is written in QT4.
Fortunately, that's a good attribute for koffice to have over OO. Most operating systems can boot faster than OO can open.
In larger companies IT is where computers n00bs go to die. It is likely an entirely different department from, say, Sysadmins or DBAs or networking, whose sole purpose is to:
A. Unpack and install desktops when they arrive.
B. Help Betsy with her resolution in the acct. dept.
C. Call IBM when _anything_ on your laptop fails, get a ticket number and handle the outbound/inbound shipping of your laptop.
D. Reformat your machine when there are any issues.
On another perspective, the one of behavior, predictable patterns are weaker than randomized one, because the external world is subjected to chaotic changes and because you will never catch by surprise a competitor who's studying you. So a degree of randomness is likely an evolutionary advantage.
It can also be selected against evolution-wise. If you had predictable patterns, a predator of comparable evolution-al tendencies would evolve to exploit such behaviors.
It's still coming out before the 360 version...
Wrong.
http://www.next-gen.biz/index.php?option=com_content&task=view&id=7359&Itemid=2
"These technical issues are now completed at a core level in our engine, and now that we have the systems working, looking ahead to 2008, we expect the PS3 versions of our titles to ship day and date with our other versions," [CEO David Zucker] said.
I'm going to refrain from answering authoritatively, as all I do is read the malling list to learn. I would think, though, based on what I've seen, that the work hasn't been done in terms of pluggability. The work has been done it patches for applying different schedulers, but I suspect making it modular is a substantially different beast.
Most african countries have populations that can't stop killing each other! It's a bit of an undertaking to get them to stop killing species of lesser distinction, if you will.
Man, this darwinism stuff sure kicks in slowly.
You're right, AFAICT, but you've missed the emphasis on "more" code. From what I've read, the scheduler's tentacles touch just about every portion of vital linux code and making something "pluggable" on the order of this would require an enormous amount of effort - effort that would be pointless for all but very small minorities that can apply a patch easily.
Indeed, it's also been showing (RTFML) that scheduler improvements are mostly trivial and generally don't warrant such an effort.
Finally, one must consider that the enormous amount of bugs being introduced by touching so many different areas and applying different algorithms in different cases.
Maybe this is something for consideration with the 3.x branch (Of which Linus has no intention of making), but it seems like a reasonable decision so far given the data.
Your logs aren't in GMT? How can you handle comparing many syslog servers' logs from different geographical locations when it comes time to audit?
Outside of rare exceptions, GMT should be used on servers, so this shouldn't affect many people. It'd be quite absurd for any application to rely on the time the server gives out as the applications time. An application should be server agnostic and able to handle an environment where servers could be geographically distributed. By application, I mean a DB, website, etc.
You're fooling yourself if you think that FDIC insured is going to be worth more than two squirts of piss when the day comes that ING fails. If a depression or stagflation take it down, that $100,000 likely won't buy you a loaf of bread based on current circumstances.
I'm not trying to chicken little here, I'm just trying to say that "If something could take ING (and similiar banks) down, that something is going to have widespread effects on many, many, more things".
Wish I had mod points. And kittens would have been replaced with mother-in-laws.