Live data from Hacker News

New Year's Resolutions for SysAdmins

usenix.org

41–46 of 46 posts

Re: New Year's Resolutions for SysAdmins

#41
post #5
post #3

Excuse my ignorance, but what's wrong with nslookup and ifconfig?

short answer: `/bin/ip` replaces `ifconfig` -- it's newer and more powerful more info: http://www.tty1.net/blog/2010/ifconfig-ip-comparison_en.html

OT but ip is a really unfortunate name that will be hard to google for.

Re: New Year's Resolutions for SysAdmins

#42
post #20
post #2

I'd also recommend any sysadmin to start looking into an automation framework like Chef, Puppet, Ansible, or any other of the myriad options.

I just started digging into chef with the intention of using with AWS opsworks and... holy complexity. There just doesn't seem to be any obvious entry point, as far as I can tell. I've spent two entire days searching and there doesn't seem to be anything in between "hello wordpress" and "read this 300+ page user manual". Can anyone recommend a hands on guide for setting up a multi-node stack with opsworks that isn't…

Chef smells over engineered from the get go. Try salt stack, or ansible. I've settled with Salt, but I believe they are both equally good solutions. Puppet is also OK, even if we moved away from it (towards Salt) because of poor performance (on a deployment of about 100 physical servers plus the VMs running on top of them).

Re: New Year's Resolutions for SysAdmins

#43
post #7
post #2

I'd also recommend any sysadmin to start looking into an automation framework like Chef, Puppet, Ansible, or any other of the myriad options.

Absolutely. Automate relentlessly. As a bonus, the recipes/playbooks you develop serve as documentation for how things are configured.

Better yet, version controlled changes to recipes are an excellent logbook for sysadmin teams.

Re: New Year's Resolutions for SysAdmins

#44
post #29
post #22

Earlier quoted context omitted.

They've been replaced with ipadm/dladm: http://omnios.omniti.com/wiki.php/GeneralAdministration And dnsip/dnsipq/dnsmx/dnsname/dnstxt: http://cr.yp.to/djbdns/tools.html

What? Your reply seems purposefully disingenuous and misleading. The ipadm and dladm commands seem to be specific to Solaris and derivatives. And I can not believe that you are seriously proposing that the new standard commands for doing DNS is to use DJB’s tools. What the original post most likely referred to is to use ip instead of ifconfig , and to use dig instead of nslookup .

I use dig, but in the name of correctedness, dig is as much a BIND tool as the others are djbdns tools.

Re: New Year's Resolutions for SysAdmins

#45
post #29

Earlier quoted context omitted.

What? Your reply seems purposefully disingenuous and misleading. The ipadm and dladm commands seem to be specific to Solaris and derivatives. And I can not believe that you are seriously proposing that the new standard commands for doing DNS is to use DJB’s tools. What the original post most likely referred to is to use ip instead of ifconfig , and to use dig instead of nslookup .

I use dig, but in the name of correctedness, dig is as much a BIND tool as the others are djbdns tools.

nslookup is also a BIND tool, so its logical successor is indeed dig.

Re: New Year's Resolutions for SysAdmins

#46
post #29
post #22

Earlier quoted context omitted.

They've been replaced with ipadm/dladm: http://omnios.omniti.com/wiki.php/GeneralAdministration And dnsip/dnsipq/dnsmx/dnsname/dnstxt: http://cr.yp.to/djbdns/tools.html

What? Your reply seems purposefully disingenuous and misleading. The ipadm and dladm commands seem to be specific to Solaris and derivatives. And I can not believe that you are seriously proposing that the new standard commands for doing DNS is to use DJB’s tools. What the original post most likely referred to is to use ip instead of ifconfig , and to use dig instead of nslookup .

Calm down a bit. Of course my post was in jest (well intentioned I might add) - I was pointing out the TMTOWTDI nature of this entire debate. The goal here wasn't to instruct or mislead.

The Linux way isn't always the way the rest of Unix is going. In fact, most of our current OS's are a hodgepodge of different great things developed by different teams - for example, rsync from the Samba devs, sudo from OpenBSD, git from Linux, etc.

This is one of the great things about Unix is that it's a big sandbox to play in. The entire "lets replace init" movement from the last 10 years is pretty fascinating in it's own right. Spend some time looking at how the other crowds out there are doing things - you might find something interesting and helpful.

Post reply on HN