Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:How many times .... (Score 2) 33

by Bigbutt (#49465927) Attached to: Book Review: Networking For System Administrators

Yea, a1 is the one that's probably the most annoying. I get regular (daily) data from this server. I have monitoring agents in place to notify me if the system goes off line or even has a bad afternoon.

"Has this ever worked?"

Are you fucking kidding me? Here are the tcpdumps from the system showing the packet loss. Here's the output of ifconfig showing the interface as down. Here's ethtools showing no link. Here are the configuration files from yesterday showing it was on line yesterday. Here is the monthly consolidation file showing it's been configured for years. The shit I gave you when I opened the ticket in the first place!

"Did something change in the data center?"

Nothing we've done. It's a remote site and we don't manage the data center. Maybe it's a cable that went bad, someone tripped over, a switch configuration change due to a reboot, a firewall change?

Data Center Manager: "In my experience, cables don't go bad. Are you sure the system was working yesterday? I tend to believe the Networking folks over you sysadmins."

Ultimately it turns out the cable went bad. Replaced the cable and all was well again.

But damn, "was it working yesterday" really is a pisser.


Comment: Re: And it's not even an election year (Score 1) 407

Actually we helped with the description, in part because a few years back when we were looking, he'd failed to put 'Unix' in the description. It seems to be a bog standard description. We are looking for someone with enterprise level experience so HP-UX, Solaris, or AIX are big plusses.

We do get candidates but they all seem to be junior/power user types who haven't managed systems at an enterprise level. They don't know how things work under the hood and don't appear to be interested in learning.

With 35 years of experience in computers and 20 years experience as a Unix admin, I'm making a bit over 100k. In checking the job descriptions available in Denver, I think I could get another 20k if I decided to commute for an hour but since I'm 5 minutes from my house now, I think it's just about worth the reduction in stress to stick around :)


Comment: Re:And it's not even an election year (Score 1) 407

Which tech? I'm in Operations and I can't think of any "foreign" worker in the entire department (600 or so people) other than the CIO who's Indian _and_ female (I might have missed someone but I can't really come up with any).

We do have about a third of the department which are women and half the managers are women.


Comment: Re: And it's not even an election year (Score 1) 407

From a sysadmin perspective, we spent 18 months trying to find a competent sysadmin. When I spoke to HR, mid level sysadmins in the Denver area thought they were worth $250,000 a year.

If you're going to price yourself out of the market then don't be surprised when you're replaced by an H1B.


Comment: Hard to say (Score 1) 220

by Bigbutt (#49399651) Attached to: How would you rate your programming skills?

I've professionally programmed in the past and continue to explore and learn even though I'm not a programmer now (unix admin). I do a lot of scripting for my environment though and one of the other admins recently quipped after I said something like "I do a lot of scripting", that I actually "program scripts". In other words, I use my programming skills to create maintainable and robust scripts vs 10 lines to achieve a task. It tends to be interesting when we ask applicants if they can script and to describe a fun script they wrote. It seems that not many unix admins enjoy writing scripts (or at least our applicants).

Could I get a job as a Programmer now? Probably although age and relevant experience might be a problem. Certainly I wouldn't be immediately making the same income I'm currently making.


Comment: Re: Suck it Millenials (Score 1) 407

by Bigbutt (#49353365) Attached to: Millennial Tech Workers Losing Ground In US

Tail Boomer here and same situation. I was a Military Policeman in the late 70's and a security guard in the early 80's. I'd been writing programs since 1980 supporting my Dungeons & Dragons and board gaming hobby (first Timex program was a D&D Game Monitor and first Color Computer program was a Vehicle Generation program for Car Wars :) ). I moved into BBS's, writing programs for the BBS software (PCBoard) and programs for my security guard post and brief stint writing code as a car salesman. Then into full time programming. Installed LANs, was on Usenet when Linux started, played with Slackware from the beginning.


Comment: Re:Suck it Millenials (Score 1) 407

by Bigbutt (#49353313) Attached to: Millennial Tech Workers Losing Ground In US

Worse, the first time I typed in 'Super StarTrek' from the Red Computer Games book on an IBM PC (I had the Yellow one as well), I had failed to format a 5 1/4" floppy. After getting the game working successfully, I couldn't save it. I'd been typing in programs on a Color Computer before that and a Timex/Sinclair before that and all my program saving was on cassette (reset the tape counter and record the location on the tape for each program).


Comment: Drivers! (Score 1) 307

I've had the most problems with Video cards, the expensive ones. Specifically the drivers.

The AMD cards I first bought in 2008 generated driver related blue screens on boot. DiamondMM tested them and found no problems. I upgraded drivers including the set that forced me to go into single user mode and roll them back. Nothing seemed to take care of it.

The nVidia replacements I bought in 2012 don't blue screen however the driver resets (Windows has restarted the video driver) pretty often. Doesn't seem to cause a problem other than the aggravation of waiting while it recovers. The solution apparently is to underclock the GPU.

I don't seem to have any problems with the cards when I run them under Red Hat Linux however I suspect I don't use them quite the same way as on the Windows system.


You do not have mail.