to use the slashdot effect as a means of intimidation and blackmail is a Bad Thing.
its the stuff of Union Thugs.
Man, I gotta disagree most strongly here. Having some 75,000 angry geeks hammering on your email, web and voicemail servers is merely the online equivalent of a bunch of angry, vocal picketers on the public pavement outside your head office. Those servers have been opened to the public to give information and take feedback.
Ah yes. Vi, the lowest common denominator of all Unices.
Were it not for my knowledge of vi, I would not have been able to talk (over the phone) a newbie through editing/etc/fstab on a system that could not determine the terminal type of it's own console.
I don't know for certain, but I suspect that emacs is fine for people who spend most of their computing time editing/compiling/debugging.
That's OK, but I don't. I spend most of my system time looking at logfiles and process displays, searching text files, checking disk space, and editing config files. Hence, my requirements for a working environment are better matched by a shell than by an editor.
Don't get me wrong, I *like* modal editors (anyone familiar with isredit on VM/MVS/OS-390?), it's just that I don't think "keystrokes to leave the editor" is a good argument for the virtues of one editor over the other.
I took a course at Sun Education's Melbourne offices a couple of years ago. I thought I noticed that the receptionist at the front desk was not using MS products, so I asked what office suite she was using.
Her answer? Applix.
So I very much doubt that Sun are as dependent on MS stuff as has been suggested. MS Office is certainly not a company-wide standard.
...was basically by being in the right place at the right time. Or to be more accurate, putting myself in the right place and waiting for the right time to happen.
The crowd I work for (a facilities management company) had a few itty-bitty Unix boxes that required very little system administration. The sysadmins were primarily a network admin and a mainframe systems programmer respectively. They usually had no need for a dedicated system admin, and when they did, they hired a contractor for six months.
At this time I was a mainframe operator, and had no formal qualifications. But I had console access and arranged root access to a few of the Unix boxes.
This was when I voiced my interest in Unix administration as my career direction, and started playing with their systems. Tidying up scripts, automating backups via cron, etc. All this time I was messing around with Linux at home, learning as much as I could and noting the differences and similarities between Linux/SunOS/BSD/HP-UX.
The company then sent me on a 5 day intro to sysadmin course, which by this stage only, about 30% of was really new to me. About six months later, the company acquired a new contract that required two HP-UX system administrators. The right time had happened.
That was a little under twelve months ago, and I haven't been disappointed.
That's just my story, a little bit of preparation and a lot of luck.
Slashdot Mirror
Man, I gotta disagree most strongly here. Having some 75,000 angry geeks hammering on your email, web and voicemail servers is merely the online equivalent of a bunch of angry, vocal picketers on the public pavement outside your head office. Those servers have been opened to the public to give information and take feedback.
Well they got their feedback. In spades!
I think he probably does do his development on a separate machine, but some of these niggles only show up on his live system.
He also may not be able to afford to set up a complete test environment complete with equivalent bandwidth and 75k users providing load testing.
I'm getting my money's worth, what's your beef?
Ah yes. Vi, the lowest common denominator of all Unices.
/etc/fstab on a system that could not determine the terminal type of it's own console.
Were it not for my knowledge of vi, I would not have been able to talk (over the phone) a newbie through editing
"Alright, now type 'jjwwwcwc0t0d4' etc."
I don't know for certain, but I suspect that emacs is fine for people who spend most of their computing time editing/compiling/debugging.
:)
That's OK, but I don't. I spend most of my system time looking at logfiles and process displays, searching text files, checking disk space, and editing config files. Hence, my requirements for a working environment are better matched by a shell than by an editor.
Horses for courses folx
Hi-ho silver!
On the other hand let's look at vi(*)
:)
Lessee
[esc]:wq![enter]
I count six
Don't get me wrong, I *like* modal editors (anyone familiar with isredit on VM/MVS/OS-390?), it's just that I don't think "keystrokes to leave the editor" is a good argument for the virtues of one editor over the other.
I took a course at Sun Education's Melbourne offices a couple of years ago. I thought I noticed that the receptionist at the front desk was not using MS products, so I asked what office suite she was using.
Her answer? Applix.
So I very much doubt that Sun are as dependent on MS stuff as has been suggested. MS Office is certainly not a company-wide standard.
It ain't gonna be Y2K issues that cause a run on this bank :)
Yes, but I can't very well spell it with an SX.
You'd feel more like an American in the UK.
They speak the same language, but the accent's sometimes a little hard to understand.
You don't know your way around but you can ask for directions and for the most part, get an intelligible answer.
The customs are somewhat similar, but often distinctly different.
...was basically by being in the right place at the right time. Or to be more accurate, putting myself in the right place and waiting for the right time to happen.
The crowd I work for (a facilities management company) had a few itty-bitty Unix boxes that required very little system administration. The sysadmins were primarily a network admin and a mainframe systems programmer respectively. They usually had no need for a dedicated system admin, and when they did, they hired a contractor for six months.
At this time I was a mainframe operator, and had no formal qualifications. But I had console access and arranged root access to a few of the Unix boxes.
This was when I voiced my interest in Unix administration as my career direction, and started playing with their systems. Tidying up scripts, automating backups via cron, etc. All this time I was messing around with Linux at home, learning as much as I could and noting the differences and similarities between Linux/SunOS/BSD/HP-UX.
The company then sent me on a 5 day intro to sysadmin course, which by this stage only, about 30% of was really new to me. About six months later, the company acquired a new contract that required two HP-UX system administrators. The right time had happened.
That was a little under twelve months ago, and I haven't been disappointed.
That's just my story, a little bit of preparation and a lot of luck.
I had to laugh at Chris Carter's apparent promotion.
"E's not the Messiah! E's a very naughty boy!"