Follow Slashdot stories on Twitter


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).


+ - LOPSA Mentorship Program Launched->

Submitted by Merc248
Merc248 (1026032) writes "LOPSA has launched a mentorship program for system administrators, and is now soliciting for both mentors and proteges! It costs absolutely nothing to join the program, though if you're wanting to be a mentor, you must be a LOPSA member (but not if you're wanting to be a protege.) It's a great way to advance one's career in system administration."
Link to Original Source

Comment: Re:Switch to *NIX (Score 1) 385

by Merc248 (#31970924) Attached to: Confessions of a SysAdmin

Right. But what of politics and whatnot, preventing people from changing the infrastructure?

Also, when I say someone could fuck up the infrastructure, I mean the people who are architecting the infrastructure in the first place, not any environmental issues like any malicious attempts at penetrating the network, or whatever.

Also, I must stress how important it is to use some semblance of configuration management; it's almost necessary when you're managing at least 100 servers.

Comment: What's your goal? (Score 1) 261

by Merc248 (#31916728) Attached to: Good, Portable "Virtual" Linux Distro?

Are you simply easing them into what a modern Linux desktop distro looks like, or do you want to teach them some stuff about the command line?

If it's the latter, why not just construct a Xen box and roll out a bunch of VM's that students can use remotely? Either that, or if you can subsidize the monthly costs somehow with a lab fee or whatever, you could always roll out a ton of EC2 instances or Linode slices for them to play on.

Of course, you'd have to worry about security, and it's not exactly the least complex solution, but you'd also force them to work in a command line.

Comment: Re:how to not cheat (Score 1) 694

by Merc248 (#31903266) Attached to: Why Computer Science Students Cheat

God, you've no idea how annoyed I am of hearing people who end up jumping into a field they don't like.

Typical conversation between me and various people in college (or who've just graduated from college):

me: "What'd you major in?"
person: "X"
me: "Awesome! What sort of stuff interests you about X anyway?"
person: "Oh, I'm just doing X because I can make a ton of money with it."
me: "Oh... okay."


Comment: Re:We did something else which was a lot more usef (Score 1) 349

by Merc248 (#31903152) Attached to: Virtualizing Workstations For Common Hardware?

One thing I should add: it can be a little tedious to figure out what command line switches are required for whatever program you're wanting to install, especially since the whole system can install everything, including .msi's and regular .exe InstallShield packages. This tedium pays off in a big way, however: if you set it up like how the original developers set it up, where you can pick between two or three models in the bootstrap stage, then it's extremely easy for an operator to queue up 50 machines at once for installation within 10 minutes.

For example, it took me a good week or two of scripting out all of the installation stuff so that it prompts the operator for only two pieces of information: 1.) computer use type (student lab computer, laptop, etc.), and 2.) owner's username. This only takes about a minute to fill out, and streamlines the hell out of the process. Compare this to a naive Acronis image that hasn't been sysprepped, which requires about 15 minutes per computer to rename the computer, make sure that the owner has admin rights, etc. If the computer has been sysprepped, this should be reduced down to about 2 minutes, though if you're in a heterogeneous computing environment, you'll have problems down the road where you're forced to update a ton of images for however many permutations you've bothered to save to an image.

Comment: Re:how to not cheat (Score 1) 694

by Merc248 (#31902096) Attached to: Why Computer Science Students Cheat

I wish I could've done this earlier; I really really enjoyed CS, but the program I was in at a private university was more about software engineering than CS theory. I still enjoyed coding, however.

When I went to the local public university (University of Washington), my GPA wasn't up to snuff. I LOVED computer science, but this interest was not enough to actually get me into the department.

C'est la vie.

Thankfully, I also liked the other majors I ended up graduating with, which were math and philosophy. But I think I would've loved being in the CS dept. a lot more than either of those two combined...

Comment: Re:We did something else which was a lot more usef (Score 1) 349

by Merc248 (#31898490) Attached to: Virtualizing Workstations For Common Hardware?

Yep. Before I left, we were in the talks of replacing it with WDS, since we were in the process of migrating everything to Windows 7. The general area where unattended fails is when it comes to partitioning the disk.

Someone else suggested to use OPSI; I haven't had a chance to test it out before I left, so I don't know how well it works with deploying Windows 7 nor with any sort of server OS.

Comment: We did something else which was a lot more useful (Score 5, Interesting) 349

by Merc248 (#31892156) Attached to: Virtualizing Workstations For Common Hardware?

I used unattended on a FreeBSD box at one of my old jobs, since we had like five or so different models of computers. It works sort of like RIS, except it's easier to extend the system since it's all written in Perl and it's all open source. We dumped the contents of an XP disc on the server, then slipstreamed driver packs into the disc directory structure; this catches almost everything but the most obscure hardware out there. Unattended allowed us to run post-install scripts, so we threw in a bunch of other software packages that would install after the OS was done installing, like Office 2007, Adobe suite, etc.

This was substantially better than a disk image; we took care of all of the drivers in one fell swoop, so the only thing we used as a differentiator between computers was how the person used the computer (if it's a student lab computer, we loaded a bunch of stuff like Geometer's Sketchpad, InDesign, etc. If it was a faculty's laptop, we'd load software to operate stuff in the classroom.) We save space on the server, and we save time when it comes to putting together another "image" for a different use case.

But as others said above, I wouldn't virtualize the workstation, even if it eases up on the IT dept. a little bit; just be smart about what deployment method you use. I wouldn't recommend using unattended if you had only about three different models; it's likely substantially easier to just use CloneZilla.

Oh, and use a centralized software deployment system such as WPKG. Your disk images will go stale after a while, in which case you'll have to make sure that you can manage the packages installed on clients somehow.

Saliva causes cancer, but only if swallowed in small amounts over a long period of time. -- George Carlin