[nycbug-talk] Last night's meeting

Isaac Levy isaac at diversaform.com
Thu Dec 3 15:43:12 EST 2009


> ----- Original Message ----
>> From: George Rosamond <george at ceetonetechnology.com>
>> To: talk <talk at lists.nycbug.org>
>> Sent: Thu, December 3, 2009 11:19:15 AM
>> Subject: [nycbug-talk] Last night's meeting
>>
>> Wondering other's thoughts on last nights meeting. . .
>>
>> I thought it was a great meeting overall. .. brought in more  
>> speakers,
>> some for the first time, encouraged more people to be involved.
>>
>> We often have side discussions about topics that don't justify a full
>> meeting.  It might be an SSH hack, a creative use of pipes, and so it
>> reflects the day-to-day activities of people. . . so it's worth
>> integrating into our meetings without the rigidity of this or that
>> specific topic.
>>
>> Personally, though, I was thinking we should try for a "pipes and
>> scripts" meetings as opposed to "ports and packages."
>>
>> Maybe a bit clearer by saying the solutions/hints/hacks should be
>> interoperable for all bsds (and even Linux and Solaris, etc). .. .
>> basically a focus on creatively employing the core unix commands. ..
>> from "at to zcat."  Say, unix is a toolbox, what do you do with the  
>> tools?
>>
>> Say. . . running a command then ending with "&& mail -s 'script done'
>> root" or  uniquely piping things to logger, like ike's jls example  
>> (jls
>> being a FreeBSD ls for the current jails for the host).  little  
>> things
>> that make life easier because ppl are employing the core unix tools
>> creatively.
>>
>> Nevertheless, we could look at repeating last night in some form or  
>> another.
>>
>> Other thoughts?
>>
>> g

On Dec 3, 2009, at 11:45 AM, Mark Saad wrote:

> George
>  My wife Sheila had a good idea,  some of the short topics from last  
> night or another similar meeting
> could be an entire meeting. Why not vote someone to come back and  
> expand on their topic for a future meeting.
>
> --
> Mark Saad
> mark.saad at ymail.com

I vote for a full meeting on logger(1) "advanced" usage, so I can  
correct what was missing last night, (using it without pipes!)

e.g.:
   # logger hi ike

instead of:
   # echo 'hi ike' | logger

Rocket-
.ike





More information about the talk mailing list