That would obviously depend on where you live. The easiest way to get trained is to actually install Linux on a spare PC/hard disk and use it. (The spare disk is simply so that Windows issues don't make you fight to keep Linux booting).
Expect a two or three year learning curve (depending on how much you want to learn, you can reduce it considerably by learning less or learning faster). The first bump in the curve is when you meet the command line. Any basic Unix textbook will show you the basic initial commands. Don't worry about the systematic learning part, you will learn a lot more by making mistakes.
Once you are comfortable with the command line (this should take you a week or two), learn a text editor. I like vim, others may recommend emacs or something else. Emacs is a reasonably good programmer editor, vi is better for sysadmin tasks. Learning the basics of the editor may take a few days, expect to spend a few months before you get really comfortable with it (this is a question of habit forming, not technically difficult stuff). Your best friends at this time will be the man(1) command and a good search engine.
Your second bump will be learning to manage systems instead of hosts. This is a fairly large conceptual jump from common MS Windows system administration, and you may not get it at one go. The basic theme is that you are managing an ecosystems of hosts, and not each host individually.
Learn some basic scripting. Shell and Perl are recommended, but Ruby and Python are good choices as well.
At this point, you are ready to begin playing with servers. Start with something simple, like Squid. Once you are comfortable with squid, DHCP, then DNS, then Apache. All these require you to read a lot, but there are no real complexities in basic setups. Once you are done with this, build a nice web-filtering proxy which will redirect users to a friendly URL in case of blockage (your school directors will like this). Then setup a LDAP server, mail server, and a Samba server. At this point, you know most of your backend stuff, and can being rolling it into production.
Not all slums are opoverty ridden. Dharavi (the biggest slum in the world) is also the biggest source of leather products in India. That's a USD 1 billion industry right there. And it is densely poulated, so you need about 8 ATMs at most.
*Shrug*. You will need to get your software stack certified. As an end user. Doctors don't build humans cell by cell, or even organ by organ.
Now, if there was a human assembly plant, with different organs coming from different places, people adding and removing organs on their own, upgrading organs willy nilly, would the plant operators be liable for bugs introduced by using unsupported third party extensions?
Doctors are mechanics. In computer terminology, helpdesk.
common identity. It was done by some European powers, take India for example.
The "Indian" common identity predates the European and Islamic invasions. It has never been a common political identity, but it does exist. There is more of an Indian socio-cultural identity than a political identity, far more so than in the EU.
I've never seen or heard of anything like a blanket ten fold increase in productivity come from the introduction of a new system or even new technology
Cue reference to No Silver Bullet.
On the other hand, the author spends much more time dealign with computer and network problems; not only is his time more expensive than the secretarial time on a unit basis, he also needs the support of highly paid technical staff.
A lot of the problems in this case are because of the bad choice of technology. Thin clients would be useful for a lot of tasks, for which we are using browser based solutions today. Using some basic skills in filing information (think of naming files sensibly, version control on documents...) would help as well.
While the people in India work to solve that little problem of illiteracy, why ignore the needs of the 400 million people who can actually use the Internet to do things, and possibly generate enough local demand for technology that jobs get exported back to the US?
The problem isn't merely of pressing buttons on a keyboard, the problem is with interacting with a computer in the first place. And it isn't merely domains in a browser, what do you do about other things relying on DNS, including VoIP?
With ~ 350 million English speakers, and a literacy rate of 65%, that's 400 million people who can't use the current form of the DNS. About as big a population as the US.
Just because it isn't useful to you doesn't mean it isn't useful to anyone else.
When faced with a workforce shortage, in no other field has the answer been to import skilled labor from other countries. The answer has always been to increase pay until the appropriate number of skilled candidates are attracted.
The answer has been to outsource the manufacturing to China, or Mexico, or any other third world country instead. Why import labour when the cost of shipping is so low? The answer isn't taxes or tariffs. Just increase the cost of oil so that shipping becomes unviable. Of course, that also drives up the cost of oil for personal transportation, so you do have to take a hit.
Heh. You need to realise that this is exactly what happens when the cost of reproduction is near zero, It won't kill innovation, it will kill innovation for profit.
Economics will be turned on its head if actual cloning ob material objects in the real world becaomes as easy as it is in software.
Or to quote Ian M. Banks: "Money implies poverty".
Though if Java was GPLed, the certain Redmond based company would have to release those modifications under the GPL as well. They could easily avoid that issue by dropping those into a class of their own.
Is vakya mein teesra shabda kaunsa hain? Ya vyakyat tisra shabda kuthla aahe?
(This is a perfectly valid response, and illustrates exactly why the long questions don't work. If the parent can answer those questions, so much the better, if not, parent poster should understand why his solutions are b0rked).
The original intent of the Realtime Blackhole List was to nullroute all traffic from the ISP until the issue was fixed. That is why it was called Realtime:P.
But because business interests decided that outright blocking was bad, we ended up with the spam mess today. Filters are the wrong solution. You have to stop the spew at the source, and if that means that Comcast customers get nullrouted globally, it means just that.
The problem is that this would have worked much better with a smaller Internet, but getting any form of consensus today is next to impossible.
The salaries in Mumbai are a third that in Bangalore, but land prices are slightly more than insane. Manhattan is cheaper than Mumbai's business district at the moment.
Hmmm, I just ensure that the hardware I buy is supported by Linux. This tends to mean that I am a few months behind the early adoption curve, but hey, it really doesn't matter. I also don't buy bottom of the market stuff, but somewhere slightly above it.
You don't have to give away your source on Linux, and you can choose any of the GUI toolkits available. Skype is QT based, Mozilla/Firefox need GTK/GTK+. And there is always xlib.
May I suggest that the right way for this to happen would be for the government to own the basic infrastructure (the physical layer), while access to that infrastructure is competitive?
Slashdot Mirror
That would obviously depend on where you live. The easiest way to get trained is to actually install Linux on a spare PC/hard disk and use it. (The spare disk is simply so that Windows issues don't make you fight to keep Linux booting).
Expect a two or three year learning curve (depending on how much you want to learn, you can reduce it considerably by learning less or learning faster). The first bump in the curve is when you meet the command line. Any basic Unix textbook will show you the basic initial commands. Don't worry about the systematic learning part, you will learn a lot more by making mistakes.
Once you are comfortable with the command line (this should take you a week or two), learn a text editor. I like vim, others may recommend emacs or something else. Emacs is a reasonably good programmer editor, vi is better for sysadmin tasks. Learning the basics of the editor may take a few days, expect to spend a few months before you get really comfortable with it (this is a question of habit forming, not technically difficult stuff). Your best friends at this time will be the man(1) command and a good search engine.
Your second bump will be learning to manage systems instead of hosts. This is a fairly large conceptual jump from common MS Windows system administration, and you may not get it at one go. The basic theme is that you are managing an ecosystems of hosts, and not each host individually.
Learn some basic scripting. Shell and Perl are recommended, but Ruby and Python are good choices as well.
At this point, you are ready to begin playing with servers. Start with something simple, like Squid. Once you are comfortable with squid, DHCP, then DNS, then Apache. All these require you to read a lot, but there are no real complexities in basic setups. Once you are done with this, build a nice web-filtering proxy which will redirect users to a friendly URL in case of blockage (your school directors will like this). Then setup a LDAP server, mail server, and a Samba server. At this point, you know most of your backend stuff, and can being rolling it into production.
Not all slums are opoverty ridden. Dharavi (the biggest slum in the world) is also the biggest source of leather products in India. That's a USD 1 billion industry right there. And it is densely poulated, so you need about 8 ATMs at most.
*Shrug*. You will need to get your software stack certified. As an end user. Doctors don't build humans cell by cell, or even organ by organ.
Now, if there was a human assembly plant, with different organs coming from different places, people adding and removing organs on their own, upgrading organs willy nilly, would the plant operators be liable for bugs introduced by using unsupported third party extensions?
Doctors are mechanics. In computer terminology, helpdesk.
common identity. It was done by some European powers, take India for example.
The "Indian" common identity predates the European and Islamic invasions. It has never been a common political identity, but it does exist. There is more of an Indian socio-cultural identity than a political identity, far more so than in the EU.
I've never seen or heard of anything like a blanket ten fold increase in productivity come from the introduction of a new system or even new technology
Cue reference to No Silver Bullet.
On the other hand, the author spends much more time dealign with computer and network problems; not only is his time more expensive than the secretarial time on a unit basis, he also needs the support of highly paid technical staff.
A lot of the problems in this case are because of the bad choice of technology. Thin clients would be useful for a lot of tasks, for which we are using browser based solutions today. Using some basic skills in filing information (think of naming files sensibly, version control on documents...) would help as well.
While the people in India work to solve that little problem of illiteracy, why ignore the needs of the 400 million people who can actually use the Internet to do things, and possibly generate enough local demand for technology that jobs get exported back to the US?
The problem isn't merely of pressing buttons on a keyboard, the problem is with interacting with a computer in the first place. And it isn't merely domains in a browser, what do you do about other things relying on DNS, including VoIP?
http://en.wikipedia.org/wiki/List_of_Indian_langua ges_by_total_speakers
With ~ 350 million English speakers, and a literacy rate of 65%, that's 400 million people who can't use the current form of the DNS. About as big a population as the US.
Just because it isn't useful to you doesn't mean it isn't useful to anyone else.
Ah, creatures from the Dungeon dimensions. Oook!
No big deal. Just ask Adam Selene to help you.
When faced with a workforce shortage, in no other field has the answer been to import skilled labor from other countries. The answer has always been to increase pay until the appropriate number of skilled candidates are attracted.
The answer has been to outsource the manufacturing to China, or Mexico, or any other third world country instead. Why import labour when the cost of shipping is so low? The answer isn't taxes or tariffs. Just increase the cost of oil so that shipping becomes unviable. Of course, that also drives up the cost of oil for personal transportation, so you do have to take a hit.
Until we can engineer bullet resistant skin. Or a forcefield. Or one side gets tired of being bitten and gets a nuclear sized flyswatter.
ETLA
Blocking 25 is fine. Blocking 587 is moronic. Using 465 is kinda stupid, but blocking it is wrong too.
587/tcp is for message submission. 25/tcp is MTA to MTA. Your MUA has no business talking on port 25.
You just need to replace his phone with one that has a proximity switch. Just ask the BOFH for help.
Heh. You need to realise that this is exactly what happens when the cost of reproduction is near zero, It won't kill innovation, it will kill innovation for profit.
Economics will be turned on its head if actual cloning ob material objects in the real world becaomes as easy as it is in software.
Or to quote Ian M. Banks: "Money implies poverty".
Though if Java was GPLed, the certain Redmond based company would have to release those modifications under the GPL as well. They could easily avoid that issue by dropping those into a class of their own.
India in Punjab, China in Tibet ...
Is vakya mein teesra shabda kaunsa hain? Ya vyakyat tisra shabda kuthla aahe?
(This is a perfectly valid response, and illustrates exactly why the long questions don't work. If the parent can answer those questions, so much the better, if not, parent poster should understand why his solutions are b0rked).
The original intent of the Realtime Blackhole List was to nullroute all traffic from the ISP until the issue was fixed. That is why it was called Realtime :P.
But because business interests decided that outright blocking was bad, we ended up with the spam mess today. Filters are the wrong solution. You have to stop the spew at the source, and if that means that Comcast customers get nullrouted globally, it means just that.
The problem is that this would have worked much better with a smaller Internet, but getting any form of consensus today is next to impossible.
The salaries in Mumbai are a third that in Bangalore, but land prices are slightly more than insane. Manhattan is cheaper than Mumbai's business district at the moment.
GMail in classic HTML mode?
I note that they had broken support for opening messages in new tabs.
Hmmm, I just ensure that the hardware I buy is supported by Linux. This tends to mean that I am a few months behind the early adoption curve, but hey, it really doesn't matter. I also don't buy bottom of the market stuff, but somewhere slightly above it.
You don't have to give away your source on Linux, and you can choose any of the GUI toolkits available. Skype is QT based, Mozilla/Firefox need GTK/GTK+. And there is always xlib.
May I suggest that the right way for this to happen would be for the government to own the basic infrastructure (the physical layer), while access to that infrastructure is competitive?
He was there in an encrypted form.