From george at ceetonetechnology.com Sat Jan 2 14:18:50 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Sat, 2 Jan 2016 14:18:50 -0500 Subject: [talk] NYC*BUG Wednesday, Jan 6 Message-ID: <5688229A.1070900@ceetonetechnology.com> Welcome to 2016. This January 6th's meeting will be an installfest, with a portion of Kirk McKusick's "Introduction to the FreeBSD Open Source Operating System LiveLessons" in the background. February 3rd will be Ike on shell-fu, focused on the powerful portability of the UNIX shell. Other upcoming meetings include debuggers and the BSD init/rc system. Wednesday, January 6 - BSD Installfest, various regulars 18:45, Stone Creek Bar & Lounge: 140 E 27th St between Lexington and 3rd Avenues. Abstract A chance to dip your toes in the *BSD waters! Want to try out some embedded Hardware? Novices, and Expert-Novices are all welcome! This is a good opportunity to bring in a laptop (maybe with a spare disk), or other hardware to hack on. There will be some embedded ARM hardware on hand, (Beaglebone and RaspberryPI), for curious folks who haven't touched these platforms. Do you have a spare laptop lying around? Do you have a Beaglebone or RaspberryPi rotting in your desk drawer? Lets get it lit with a *BSD! Various levels of experienced *BSD users will be on hand to help get a system up and running, and generally hack around on hardware. Materials to bring: Some kind of computer Some kind of spare disk or even USB memory stick media (optional) If you can, bring install media to share! (Nothing fancy, just grab useful bits from your desk drawer.) Materials which will be on site: ethernet networking gear (a small switch) Power Strips, and Extension Cords, etc A USB CD/DVD r/w drive, blank media A spare Beaglebone and RaspberryPI will be on site Additionally, we will be streaming McKusick's "Introduction to the FreeBSD Open Source Operating System LiveLessons" videos, complements of Pearson. This month, the meeting will be run by the usual cast of NYC*BUG attendees. Regular NYC*BUG attendees range in experiences from Sys/Ops folks, to committers and software developers from the BSD Projects. There will definately be folks on hand with experience using Beaglebone/RaspberryPI, Soekris, PCEngines ALIX/APU, and it almost goes without saying, regular X86 architectures in server and laptop form. NYC*BUG doesn't have record of many official installfests since 2004, this should be fun! From jesse at emptysquare.net Sat Jan 2 21:43:32 2016 From: jesse at emptysquare.net (A. Jesse Jiryu Davis) Date: Sat, 2 Jan 2016 21:43:32 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? Message-ID: Hi NYC*BUG folk. I'm a MongoDB coder and CPython contributor in NYC. I hope you can help me answer a Darwin / Mac OS X question. There's rampant speculation regarding whether Mac OS X's implementation of getaddrinfo is thread-safe. Uncertainty is so widespread that even the Python standard library locks around calls to getaddrinfo to avoid a possible bug: https://hg.python.org/cpython/file/d2b8354e87f5/Modules/socketmodule.c#l185 There was a FreeBSD bug "getaddrinfo not thread-safe" resolved back in 2006, but I don't know if Darwin and / or Mac OS X got the same bugfix, or a different bugfix, or no bugfix. I have a deeper ignorance, too, about the relationship between the FreeBSD, Darwin, and Mac OS X implementations of libc functions like getaddrinfo. I don't know where to look for OS X's implementation of getaddrinfo either (I can't find it on opensource.apple.com). Is there a Darwin or OS X expert on the list who could help me investigate? Links: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=60478 http://www.manpagez.com/man/3/getaddrinfo/osx-10.4.9.php http://www.manpagez.com/man/3/getaddrinfo/osx-10.5.php -------------- next part -------------- An HTML attachment was scrubbed... URL: From jkeen at verizon.net Sat Jan 2 21:59:10 2016 From: jkeen at verizon.net (James E Keenan) Date: Sat, 02 Jan 2016 21:59:10 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: References: Message-ID: <56888E7E.4050508@verizon.net> On 01/02/2016 09:43 PM, A. Jesse Jiryu Davis wrote: > Hi NYC*BUG folk. I'm a MongoDB coder and CPython contributor in NYC. I hope > you can help me answer a Darwin / Mac OS X question. > > There's rampant speculation regarding whether Mac OS X's implementation of > getaddrinfo is thread-safe. Uncertainty is so widespread that even the > Python standard library locks around calls to getaddrinfo to avoid a > possible bug: > > https://hg.python.org/cpython/file/d2b8354e87f5/Modules/socketmodule.c#l185 > > There was a FreeBSD bug "getaddrinfo not thread-safe" resolved back in > 2006, but I don't know if Darwin and / or Mac OS X got the same bugfix, or > a different bugfix, or no bugfix. I have a deeper ignorance, too, about the > relationship between the FreeBSD, Darwin, and Mac OS X implementations of > libc functions like getaddrinfo. I don't know where to look for OS X's > implementation of getaddrinfo either (I can't find it on > opensource.apple.com). > > Is there a Darwin or OS X expert on the list who could help me investigate? > > Links: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=60478 > http://www.manpagez.com/man/3/getaddrinfo/osx-10.4.9.php > http://www.manpagez.com/man/3/getaddrinfo/osx-10.5.php > > I don't know if these address the thread-safety question, but they seem like starting points: https://duckduckgo.com/?q=getaddrinfo+Darwin&t=canonical https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man3/getaddrinfo.3.html jimk From slynch2112 at me.com Sun Jan 3 00:10:55 2016 From: slynch2112 at me.com (Siobhan Lynch) Date: Sun, 03 Jan 2016 00:10:55 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: References: Message-ID: <542A5254-C440-4D77-8E35-07C1104975CB@me.com> > On Jan 2, 2016, at 9:43 PM, A. Jesse Jiryu Davis wrote: > > Hi NYC*BUG folk. I'm a MongoDB coder and CPython contributor in NYC. I hope you can help me answer a Darwin / Mac OS X question. > > There's rampant speculation regarding whether Mac OS X's implementation of getaddrinfo is thread-safe. Uncertainty is so widespread that even the Python standard library locks around calls to getaddrinfo to avoid a possible bug: > > https://hg.python.org/cpython/file/d2b8354e87f5/Modules/socketmodule.c#l185 > > There was a FreeBSD bug "getaddrinfo not thread-safe" resolved back in 2006, but I don't know if Darwin and / or Mac OS X got the same bugfix, or a different bugfix, or no bugfix. I have a deeper ignorance, too, about the relationship between the FreeBSD, Darwin, and Mac OS X implementations of libc functions like getaddrinfo. I don't know where to look for OS X's implementation of getaddrinfo either (I can't find it on opensource.apple.com ). > > Is there a Darwin or OS X expert on the list who could help me investigate? Use the Source? The Darwin source and revision history should be available (just not for the Mac OS X specific stuff) - has anyone actually gone in to see? That seems like the way to do it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at ceetonetechnology.com Sun Jan 3 00:47:39 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Sun, 3 Jan 2016 00:47:39 -0500 Subject: [talk] BSDNow featuring... Message-ID: <5688B5FB.50200@ceetonetechnology.com> For those who didn't hear yet, Ike is on BSDNow: http://www.bsdnow.tv/episodes/2015_12_30-the_bsd_black_box NYC*BUG's role in creating primary data remains as critical as ever :) g From slynch2112 at me.com Sun Jan 3 00:14:01 2016 From: slynch2112 at me.com (Siobhan Lynch) Date: Sun, 03 Jan 2016 00:14:01 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: References: Message-ID: OK? try and look at the revision histories of these three files: #include #include #include -Trish -------------- next part -------------- An HTML attachment was scrubbed... URL: From slynch2112 at me.com Sun Jan 3 00:12:04 2016 From: slynch2112 at me.com (Siobhan Lynch) Date: Sun, 03 Jan 2016 00:12:04 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: References: Message-ID: <953F8000-5ACA-4479-94B0-82E082CF77D6@me.com> OK I didn?t see that you could;t find it?. let me see, I was;t going to do this, but I?ll delve in?. > > There was a FreeBSD bug "getaddrinfo not thread-safe" resolved back in 2006, but I don't know if Darwin and / or Mac OS X got the same bugfix, or a different bugfix, or no bugfix. I have a deeper ignorance, too, about the relationship between the FreeBSD, Darwin, and Mac OS X implementations of libc functions like getaddrinfo. I don't know where to look for OS X's implementation of getaddrinfo either (I can't find it on opensource.apple.com ). > > Is there a Darwin or OS X expert on the list who could help me investigate? > > Links: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=60478 > http://www.manpagez.com/man/3/getaddrinfo/osx-10.4.9.php > http://www.manpagez.com/man/3/getaddrinfo/osx-10.5.php > > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From christos at zoulas.com Sun Jan 3 10:51:33 2016 From: christos at zoulas.com (Christos Zoulas) Date: Sun, 3 Jan 2016 10:51:33 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: <953F8000-5ACA-4479-94B0-82E082CF77D6@me.com> from Siobhan Lynch (Jan 3, 12:12am) Message-ID: <20160103155133.F348317FDAD@rebar.astron.com> On Jan 3, 12:12am, slynch2112 at me.com (Siobhan Lynch) wrote: -- Subject: Re: [talk] Is getaddrinfo thread-safe on OS X? | OK I didn=E2=80=99t see that you could;t find it=E2=80=A6. let me see, I wa= | s;t going to do this, but I=E2=80=99ll delve in=E2=80=A6.=20 You can use the NetBSD: http://nxr.netbsd.org/xref/src/tests/lib/libpthread/h_resolv.c test with a hosts file like the d_mach in the same directory. This does not test port resolution concurrency though. christos From jesse at emptysquare.net Sun Jan 3 10:57:13 2016 From: jesse at emptysquare.net (A. Jesse Jiryu Davis) Date: Sun, 3 Jan 2016 10:57:13 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: References: Message-ID: Thanks for the pointers, with your help I'm making progress. I think I found the source for Apple's getaddrinfo. In Apple's Libinfo version 222.4.12, the man page says getaddrinfo isn't thread-safe: http://www.opensource.apple.com/source/Libinfo/Libinfo-222.4.12/lookup.subproj/getaddrinfo.3 And here's its source: http://www.opensource.apple.com/source/Libinfo/Libinfo-222.4.12/lookup.subproj/getaddrinfo.c Glancing at the source na?vely, I might see the data race: getaddrinfo calls gai_lookupd, which reads and writes the global static variable "gai_proc". I can't see what will go wrong as a result of the race, but it sure LOOKS bad. =) In the next release, version 278, the thread-safety warning is gone from the man page: http://www.opensource.apple.com/source/Libinfo/Libinfo-278/lookup.subproj/getaddrinfo.3 And getaddrinfo is largely rewritten: http://www.opensource.apple.com/source/Libinfo/Libinfo-278/lookup.subproj/getaddrinfo.c It calls a new function, "ds_getaddrinfo". But ds_getaddrinfo still accesses the global static variable "gai_proc"; I wonder why this is considered thread-safe now? On Sun, Jan 3, 2016 at 12:14 AM, Siobhan Lynch wrote: > OK? try and look at the revision histories of these three files: > > *#include* ** > *#include* ** > *#include* ** > > > *-Trish* > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From _ at thomaslevine.com Mon Jan 4 02:05:58 2016 From: _ at thomaslevine.com (Thomas Levine) Date: Mon, 4 Jan 2016 07:05:58 +0000 Subject: [talk] NYC*BUG Wednesday, Jan 6 In-Reply-To: <5688229A.1070900@ceetonetechnology.com> References: <5688229A.1070900@ceetonetechnology.com> Message-ID: <20160104070558.GA14463@tlevine.home> I'll bring screwdrivers and spare laptop hard drives, in case anyone wants to install a new operating system on a laptop and still keep the stuff that is presently on there. On 02 Jan 14:18, George Rosamond wrote: > Welcome to 2016. > > This January 6th's meeting will be an installfest, with a portion of > Kirk McKusick's "Introduction to the FreeBSD Open Source Operating > System LiveLessons" in the background. > > February 3rd will be Ike on shell-fu, focused on the powerful > portability of the UNIX shell. > > Other upcoming meetings include debuggers and the BSD init/rc system. > > Wednesday, January 6 - BSD Installfest, various regulars > 18:45, Stone Creek Bar & Lounge: 140 E 27th St between Lexington and 3rd > Avenues. > > Abstract > > A chance to dip your toes in the *BSD waters! > > Want to try out some embedded Hardware? > > Novices, and Expert-Novices are all welcome! > > This is a good opportunity to bring in a laptop (maybe with a spare > disk), or other hardware to hack on. There will be some embedded ARM > hardware on hand, (Beaglebone and RaspberryPI), for curious folks who > haven't touched these platforms. > > Do you have a spare laptop lying around? Do you have a Beaglebone or > RaspberryPi rotting in your desk drawer? Lets get it lit with a *BSD! > > Various levels of experienced *BSD users will be on hand to help get a > system up and running, and generally hack around on hardware. > > Materials to bring: > > Some kind of computer > Some kind of spare disk or even USB memory stick media (optional) > > If you can, bring install media to share! (Nothing fancy, just grab > useful bits from your desk drawer.) > > Materials which will be on site: > > ethernet networking gear (a small switch) > Power Strips, and Extension Cords, etc > A USB CD/DVD r/w drive, blank media > A spare Beaglebone and RaspberryPI will be on site > > Additionally, we will be streaming McKusick's "Introduction to the > FreeBSD Open Source Operating System LiveLessons" videos, complements of > Pearson. > > This month, the meeting will be run by the usual cast of NYC*BUG attendees. > > Regular NYC*BUG attendees range in experiences from Sys/Ops folks, to > committers and software developers from the BSD Projects. > > There will definately be folks on hand with experience using > Beaglebone/RaspberryPI, Soekris, PCEngines ALIX/APU, and it almost goes > without saying, regular X86 architectures in server and laptop form. > > NYC*BUG doesn't have record of many official installfests since 2004, > this should be fun! > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk From steve.b at osfda.org Mon Jan 4 09:00:56 2016 From: steve.b at osfda.org (Steve) Date: Mon, 4 Jan 2016 09:00:56 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: References: Message-ID: <568A7B18.6050805@osfda.org> Sometimes they do things like that for backlevel compatibility; so single threaded apps that rely on that global don't immediately break. The question is: does ds_getaddrinfo _rely_ on that variable? I doubt it; but it's _possible_ you found an oversight! On 1/3/2016 10:57 AM, A. Jesse Jiryu Davis wrote: > Thanks for the pointers, with your help I'm making progress. I think I > found the source for Apple's getaddrinfo. > > In Apple's Libinfo version 222.4.12, the man page says getaddrinfo > isn't thread-safe: > > http://www.opensource.apple.com/source/Libinfo/Libinfo-222.4.12/lookup.subproj/getaddrinfo.3 > > And here's its source: > > http://www.opensource.apple.com/source/Libinfo/Libinfo-222.4.12/lookup.subproj/getaddrinfo.c > > Glancing at the source na?vely, I might see the data race: getaddrinfo > calls gai_lookupd, which reads and writes the global static variable > "gai_proc". I can't see what will go wrong as a result of the race, > but it sure LOOKS bad. =) > > In the next release, version 278, the thread-safety warning is gone > from the man page: > > http://www.opensource.apple.com/source/Libinfo/Libinfo-278/lookup.subproj/getaddrinfo.3 > > And getaddrinfo is largely rewritten: > > http://www.opensource.apple.com/source/Libinfo/Libinfo-278/lookup.subproj/getaddrinfo.c > > It calls a new function, "ds_getaddrinfo". But ds_getaddrinfo still > accesses the global static variable "gai_proc"; I wonder why this is > considered thread-safe now? > > On Sun, Jan 3, 2016 at 12:14 AM, Siobhan Lynch > wrote: > > OK? try and look at the revision histories of these three files: > > *#include* ** > *#include* ** > *#include* ** > > > *-Trish* > > > > > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at ceetonetechnology.com Mon Jan 4 10:05:49 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Mon, 4 Jan 2016 10:05:49 -0500 Subject: [talk] NYC*BUG Wednesday, Jan 6 In-Reply-To: <20160104070558.GA14463@tlevine.home> References: <5688229A.1070900@ceetonetechnology.com> <20160104070558.GA14463@tlevine.home> Message-ID: <568A8A4D.60709@ceetonetechnology.com> Thomas Levine: > I'll bring screwdrivers and spare laptop hard drives, in case anyone > wants to install a new operating system on a laptop and still keep the > stuff that is presently on there. > Great. I can do a quick demonstration of installing OpenBSD on a Soekris 4801, so we can party like it's 1999. https://github.com/gman999/doc/blob/master/openbsd/soekris-4801-openbsd.md And again, I strongly recommend pinging anyone interested in dipping their toes into BSD land. g From pete at nomadlogic.org Mon Jan 4 13:44:25 2016 From: pete at nomadlogic.org (Pete Wright) Date: Mon, 4 Jan 2016 10:44:25 -0800 Subject: [talk] BSDNow featuring... In-Reply-To: <5688B5FB.50200@ceetonetechnology.com> References: <5688B5FB.50200@ceetonetechnology.com> Message-ID: <568ABD89.5030903@nomadlogic.org> On 01/02/16 21:47, George Rosamond wrote: > For those who didn't hear yet, Ike is on BSDNow: > > http://www.bsdnow.tv/episodes/2015_12_30-the_bsd_black_box > > NYC*BUG's role in creating primary data remains as critical as ever :) nice one - congrats .ike! -p -- Pete Wright pete at nomadlogic.org twitter => @nomadlogicLA From mark.saad at ymail.com Mon Jan 4 16:23:03 2016 From: mark.saad at ymail.com (Mark Saad) Date: Mon, 4 Jan 2016 21:23:03 +0000 (UTC) Subject: [talk] FreeBSD 10.2-stable "random device not loaded" In-Reply-To: <20151219211222.GA84778@jimby.name> References: <20151219211222.GA84778@jimby.name> Message-ID: <72012210.7027610.1451942583629.JavaMail.yahoo@mail.yahoo.com> ----- Original Message ----- > From: Jim B. > To: George Rosamond > Cc: talk at lists.nycbug.org > Sent: Saturday, December 19, 2015 4:12 PM > Subject: Re: [talk] FreeBSD 10.2-stable "random device not loaded" > > * George Rosamond [2015-12-18 23:16]: >> John Baldwin: >> > On Wednesday, December 16, 2015 11:41:52 PM George Rosamond wrote: >> >> Pete Wright: >> >>> >> >>> >> >>> On 12/16/15 16:10, Pete Wright wrote: >> >>>> >> >>>> >> >>>> On 12/16/15 15:42, John Baldwin wrote: >> >>>>> On Friday, December 11, 2015 06:10:52 PM George > Rosamond wrote: >> >>>>>> Just updated a box to #r292122 with GENERIC, found > this wildly >> >>>>>> confidence-building note in the dmesg: >> >>>>>> >> >>>>>> random device not loaded; using insecure entropy >> >>>>>> >> >>>>>> Two lines later in the dmesg it does say: >> >>>>>> >> >>>>>> random: initialized >> >>>>>> >> >>>>>> I don't see anything online recently about > this... except for one >> >>>>>> unanswered post on freebsd-questions@ in late > October. >> >>>>>> >> >>>>>> Thought I'd post here before I dug further... >> >>>>> >> >>>>> Humm, any luck on more info? I haven't seen that > on HEAD, and GENERIC >> >>>>> on stable/10 includes device random so that seems odd. >> >>>>> >> >>>> >> >>>> >> >>>> i am *not* seeing this on one of my KVM instances here > running HEAD r292065: >> >>>> >> >>>> pwright at bsd-current:/usr/src % dmesg|grep -i random >> >>>> random: unblocking device. >> >>>> random: entropy device external interface >> >>>> random: registering fast source Intel Secure Key RNG >> >>>> random: fast provider: "Intel Secure Key RNG" >> >>>> >> >>>> >> >>>> this is a sandy bridge (E3xxx) Intel CPU on the hypervisor > fwiw. >> >>> >> >>> strike that - freebsd detects this as a E312xx but the > hypervisor is a >> >>> E5-2697 v2 which is also a sandy bridge, but a different rev > than the E3xxxx >> >> >> >> Thanks Pete and John. >> >> >> >> Again, here's the relevant part of the dmesg: >> >> >> >> random device not loaded; using insecure entropy >> >> ioapic0 irqs 0-23 on motherboard >> >> random: initialized >> >> >> >> Someone hit me offlist on this, and apparently it's Supermicro >> >> motherboard-related. Yes, vague, but I need to do more searching > after >> >> that. >> > >> > Hmm, that seems like a bit of an order of operations thing where > something is >> > asking for random bits before device random is initialized. I'm > not sure what >> > would be asking for it that early though. >> > >> >> Yes, definitely. What could be requesting entropy before Yarrow >> initializes? >> >> I have to look a bit more into it when I get a chance. >> > > Try booting verbose. The demsg will have all the verbose info. > > My 2 (Arkansas hick version) > > Jim B. > > > All I was looking at this issue again, and I was able to recreate it. On 10-STABLE amd64 r292855. See dmesg here http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2871 I am going to start digging , the warning is in sys/dev/random/harvest.c 102 /* If the entropy device is not loaded, make a token effort to 103 * provide _some_ kind of randomness. This should only be used 104 * inside other RNG's, like arc4random(9). 105 */ 106 static int 107 read_random_phony(void *buf, int count) 108 { 109 u_long randval; 110 int size, i; 111 112 if (!warned) { 113 log(LOG_WARNING, "random device not loaded; using insecure entropy\n"); 114 warned = 1; 115 } 116 117 /* srandom() is called in kern/init_main.c:proc0_post() */ 118 119 /* Fill buf[] with random(9) output */ 120 for (i = 0; i < count; i+= (int)sizeof(u_long)) { 121 randval = random(); 122 size = MIN(count - i, sizeof(u_long)); 123 memcpy(&((char *)buf)[i], &randval, (size_t)size); 124 } 125 126 return (count); -- Mark Saad mark.saad at ymail.com > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk > From jschauma at netmeister.org Tue Jan 5 17:42:30 2016 From: jschauma at netmeister.org (Jan Schaumann) Date: Tue, 5 Jan 2016 17:42:30 -0500 Subject: [talk] uptime Message-ID: <20160105224230.GG6641@netmeister.org> Hey, This seems like the sort of thing this group might appreciate: https://twitter.com/jschauma/status/684501926180958208 $ uptime 2:26PM up 3429 days, 11:59, 1 user, load averages: 0.33, 0.27, 0.29 $ uname -rs FreeBSD 4.11 $ Now to go and take this fucker behind the barn and shoot it... -Jan From slynch2112 at me.com Tue Jan 5 17:44:52 2016 From: slynch2112 at me.com (Siobhan Lynch) Date: Tue, 05 Jan 2016 17:44:52 -0500 Subject: [talk] uptime In-Reply-To: <20160105224230.GG6641@netmeister.org> References: <20160105224230.GG6641@netmeister.org> Message-ID: Wow, that might actually date from around the period I was doing heavier work with this stuff - LOL And bullets won?t help, but I am pretty sure that we can crack in? and destroy it from within. -Trish ? > On Jan 5, 2016, at 5:42 PM, Jan Schaumann wrote: > > Hey, > > This seems like the sort of thing this group might appreciate: > > https://twitter.com/jschauma/status/684501926180958208 > > $ uptime > 2:26PM up 3429 days, 11:59, 1 user, load averages: 0.33, 0.27, 0.29 > $ uname -rs > FreeBSD 4.11 > $ > > Now to go and take this fucker behind the barn and shoot it... > > -Jan > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at ceetonetechnology.com Tue Jan 5 17:47:12 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Tue, 5 Jan 2016 17:47:12 -0500 Subject: [talk] uptime In-Reply-To: <20160105224230.GG6641@netmeister.org> References: <20160105224230.GG6641@netmeister.org> Message-ID: <568C47F0.8020305@ceetonetechnology.com> Jan Schaumann: > Hey, > > This seems like the sort of thing this group might appreciate: > > https://twitter.com/jschauma/status/684501926180958208 > > $ uptime > 2:26PM up 3429 days, 11:59, 1 user, load averages: 0.33, 0.27, 0.29 > $ uname -rs > FreeBSD 4.11 > $ > > Now to go and take this fucker behind the barn and shoot it... that dmesg *needs* to be uploaded to dmesgd.nycbug.org g From jschauma at netmeister.org Tue Jan 5 17:56:13 2016 From: jschauma at netmeister.org (Jan Schaumann) Date: Tue, 5 Jan 2016 17:56:13 -0500 Subject: [talk] uptime In-Reply-To: <568C47F0.8020305@ceetonetechnology.com> References: <20160105224230.GG6641@netmeister.org> <568C47F0.8020305@ceetonetechnology.com> Message-ID: <20160105225613.GH6641@netmeister.org> George Rosamond wrote: > that dmesg *needs* to be uploaded to dmesgd.nycbug.org http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2874 -Jan From george at ceetonetechnology.com Tue Jan 5 18:43:20 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Tue, 5 Jan 2016 18:43:20 -0500 Subject: [talk] uptime In-Reply-To: <20160105225613.GH6641@netmeister.org> References: <20160105224230.GG6641@netmeister.org> <568C47F0.8020305@ceetonetechnology.com> <20160105225613.GH6641@netmeister.org> Message-ID: <568C5518.2060704@ceetonetechnology.com> Jan Schaumann: > George Rosamond wrote: > >> that dmesg *needs* to be uploaded to dmesgd.nycbug.org > > http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2874 Thanks Jan. And none of the RAID disks died? wow. ciss0: 3 physical devices ciss0: 1 logical drive g From george at ceetonetechnology.com Wed Jan 6 08:35:18 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Wed, 6 Jan 2016 08:35:18 -0500 Subject: [talk] NYC*BUG Installfest Tonight Message-ID: <568D1816.5080404@ceetonetechnology.com> This January 6th's meeting will be an installfest, with a portion of Kirk McKusick's "Introduction to the FreeBSD Open Source Operating System LiveLessons" in the background. February 3rd will be Ike on shell-fu, focused on the powerful portability of the UNIX shell. Other upcoming meetings include debuggers and the BSD init/rc system. Wednesday, January 6 - BSD Installfest, various regulars 18:45, Stone Creek Bar & Lounge: 140 E 27th St between Lexington and 3rd Avenues. Abstract A chance to dip your toes in the *BSD waters! Want to try out some embedded Hardware? Novices, and Expert-Novices are all welcome! This is a good opportunity to bring in a laptop (maybe with a spare disk), or other hardware to hack on. There will be some embedded ARM hardware on hand, (Beaglebone and RaspberryPI), for curious folks who haven't touched these platforms. Do you have a spare laptop lying around? Do you have a Beaglebone or RaspberryPi rotting in your desk drawer? Lets get it lit with a *BSD! Various levels of experienced *BSD users will be on hand to help get a system up and running, and generally hack around on hardware. Materials to bring: Some kind of computer Some kind of spare disk or even USB memory stick media (optional) If you can, bring install media to share! (Nothing fancy, just grab useful bits from your desk drawer.) Materials which will be on site: ethernet networking gear (a small switch) Power Strips, and Extension Cords, etc A USB CD/DVD r/w drive, blank media A spare Beaglebone and RaspberryPI will be on site Additionally, we will be streaming McKusick's "Introduction to the FreeBSD Open Source Operating System LiveLessons" videos, complements of Pearson. This month, the meeting will be run by the usual cast of NYC*BUG attendees. Regular NYC*BUG attendees range in experiences from Sys/Ops folks, to committers and software developers from the BSD Projects. There will definately be folks on hand with experience using Beaglebone/RaspberryPI, Soekris, PCEngines ALIX/APU, and it almost goes without saying, regular X86 architectures in server and laptop form. NYC*BUG doesn't have record of many official installfests since 2004, this should be fun! From george at ceetonetechnology.com Wed Jan 6 11:25:53 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Wed, 6 Jan 2016 11:25:53 -0500 Subject: [talk] Fwd: Re: [new] aws cli tools Message-ID: <568D4011.40306@ceetonetechnology.com> OpenBSD AWS port looks like it's on its way. -------- Forwarded Message -------- Subject: Re: [new] aws cli tools Date: Wed, 6 Jan 2016 16:23:17 +0100 From: Reyk Floeter To: Antoine Jacoutot CC: ports at openbsd.org On Wed, Jan 06, 2016 at 02:18:09PM +0100, Antoine Jacoutot wrote: > Hi. > > This tarball contains the AWS cli tools to manage your cloud resources. > It comes with several new dependencies. > > I'd like to get it in soon and maybe polish a few things after import. > And then I will bring the EC2 tools and the aws shell in. > > Please test, comment, ok... > > $ aws --version > aws-cli/1.9.16 Python/2.7.11 OpenBSD/5.9 botocore/1.3.16 > Nice! $ aws ec2 get-console-output --instance-id i-c7cf777b i-c7cf777b +2176664+267272+0+647168 [72+576648+383917]=0xa6eb00 entry point at 0x1001000 [7205c766, 34000004, 24448b12, 60a304] [ using 961280 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2016 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.9-beta (GENERIC.MP-xen) #50: Wed Jan 6 15:03:16 CET 2016 reyk at esdenera.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP-xen real mem = 1056964608 (1008MB) avail mem = 1020788736 (973MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xeb01f (11 entries) bios0: vendor Xen version "4.2.amazon" date 12/07/2015 bios0: Xen HVM domU acpi0 at bios0: rev 2 acpi0: sleep states S3 S4 S5 acpi0: tables DSDT FACP APIC HPET WAET SSDT SSDT acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 11, 48 pins ioapic0: misconfigured as apic 0, remapped to apid 1 cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz, 2400.39 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz acpihpet0 at acpi0: 62500000 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1(@1 halt!) pvbus0 at mainbus0: Xen 4.2 xen0 at pvbus0 xen0: hypercall page at va 0xffffffff81002000 pa 0x1002000 xen0: version 4.2.amazon xen0: features 705 xen0: shared info page at va 0xffff8000000ef000 pa 0x3f6fe000 xen0: registered callback IDT vector 112 xen0: grant table frames allocated 32/32 xen0: xenstore event channel 3 xen0: xenstore ring at va 0xffff800014ad8000 pa 0xfeffc000 xen0: xenstore interrupt established for port 3 "vfb" at xen0: device/vfb/0 not configured "vbd" at xen0: device/vbd/768 not configured xen0: xenstore request 2 "device/vif/0/type" error ENOENT xnf0 at xen0: event channel 5, address 06:c0:fd:39:93:7f "console" at xen0: device/console/0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 1024MB, 2097152 sectors wd0(pciide0:0:0): using PIO mode 0, DMA mode 2 pciide0: channel 1 disabled (no drives) piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x01: SMBus disabled vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) xspd0 at pci0 dev 3 function 0 "XenSource Platform Device" rev 0x01 isa0 at pcib0 isadma0 at isa0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: density unknown fd1 at fdc0 drive 1: density unknown com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 vmm at mainbus0 not configured nvram: invalid checksum vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on wd0a (eeacdbd148573cfa.a) swap on wd0b dump on wd0b clock: unknown CMOS layout Automatic boot in progress: starting file system checks. /dev/wd0a (eeacdbd148573cfa.a): file system is clean; not checking setting tty flags pf enabled starting network DHCPDISCOVER on xnf0 - interval 3 DHCPOFFER from 172.31.16.1 (06:bc:14:46:67:74) DHCPREQUEST on xnf0 to 255.255.255.255 DHCPACK from 172.31.16.1 (06:bc:14:46:67:74) bound to 172.31.17.41 -- renewal in 1800 seconds. openssl: generating isakmpd/iked RSA keys... done. ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 starting early daemons: syslogd pflogd ntpd. starting RPC daemons:. savecore: no core dump checking quotas: done. clearing /tmp kern.securelevel: 0 -> 1 creating runtime link editor directory cache. preserving editor files. starting network daemons: sshd smtpd sndiod. Path to firmware: http://firmware.openbsd.org/firmware/snapshots/ No devices found which need firmware files to be downloaded. starting local daemons: cron. Wed Jan 6 15:31:42 CET 2016 OpenBSD/amd64 (openbsd.my.domain) (tty00) login: From robin.polak at gmail.com Wed Jan 6 11:35:46 2016 From: robin.polak at gmail.com (Robin Polak) Date: Wed, 6 Jan 2016 08:35:46 -0800 Subject: [talk] Fwd: Re: [new] aws cli tools In-Reply-To: <568D4011.40306@ceetonetechnology.com> References: <568D4011.40306@ceetonetechnology.com> Message-ID: <0A83B1C3-A220-4D5D-B427-2B5E48504FFE@gmail.com> That's awesome. Great to hear BSD getting more traction on AWS. I will have to check that out. Do you have the AMI ID? Sent from my iPhone > On Jan 6, 2016, at 8:25 AM, George Rosamond wrote: > > OpenBSD AWS port looks like it's on its way. > > > -------- Forwarded Message -------- > Subject: Re: [new] aws cli tools > Date: Wed, 6 Jan 2016 16:23:17 +0100 > From: Reyk Floeter > To: Antoine Jacoutot > CC: ports at openbsd.org > >> On Wed, Jan 06, 2016 at 02:18:09PM +0100, Antoine Jacoutot wrote: >> Hi. >> >> This tarball contains the AWS cli tools to manage your cloud resources. >> It comes with several new dependencies. >> >> I'd like to get it in soon and maybe polish a few things after import. >> And then I will bring the EC2 tools and the aws shell in. >> >> Please test, comment, ok... >> >> $ aws --version >> aws-cli/1.9.16 Python/2.7.11 OpenBSD/5.9 botocore/1.3.16 > > Nice! > > $ aws ec2 get-console-output --instance-id i-c7cf777b > i-c7cf777b +2176664+267272+0+647168 [72+576648+383917]=0xa6eb00 > entry point at 0x1001000 [7205c766, 34000004, 24448b12, 60a304] > [ using 961280 bytes of bsd ELF symbol table ] > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > Copyright (c) 1995-2016 OpenBSD. All rights reserved. > http://www.OpenBSD.org > > OpenBSD 5.9-beta (GENERIC.MP-xen) #50: Wed Jan 6 15:03:16 CET 2016 > reyk at esdenera.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP-xen > real mem = 1056964608 (1008MB) > avail mem = 1020788736 (973MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xeb01f (11 entries) > bios0: vendor Xen version "4.2.amazon" date 12/07/2015 > bios0: Xen HVM domU > acpi0 at bios0: rev 2 > acpi0: sleep states S3 S4 S5 > acpi0: tables DSDT FACP APIC HPET WAET SSDT SSDT > acpi0: wakeup devices > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat > ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 11, 48 pins > ioapic0: misconfigured as apic 0, remapped to apid 1 > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz, 2400.39 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,LONG,LAHF,ABM,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 100MHz > acpihpet0 at acpi0: 62500000 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpicpu0 at acpi0: C1(@1 halt!) > pvbus0 at mainbus0: Xen 4.2 > xen0 at pvbus0 > xen0: hypercall page at va 0xffffffff81002000 pa 0x1002000 > xen0: version 4.2.amazon > xen0: features 705 > xen0: shared info page at va 0xffff8000000ef000 pa 0x3f6fe000 > xen0: registered callback IDT vector 112 > xen0: grant table frames allocated 32/32 > xen0: xenstore event channel 3 > xen0: xenstore ring at va 0xffff800014ad8000 pa 0xfeffc000 > xen0: xenstore interrupt established for port 3 > "vfb" at xen0: device/vfb/0 not configured > "vbd" at xen0: device/vbd/768 not configured > xen0: xenstore request 2 "device/vif/0/type" error ENOENT > xnf0 at xen0: event channel 5, address 06:c0:fd:39:93:7f > "console" at xen0: device/console/0 not configured > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 > pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 > pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, > channel 0 wired to compatibility, channel 1 wired to compatibility > wd0 at pciide0 channel 0 drive 0: > wd0: 16-sector PIO, LBA48, 1024MB, 2097152 sectors > wd0(pciide0:0:0): using PIO mode 0, DMA mode 2 > pciide0: channel 1 disabled (no drives) > piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x01: SMBus > disabled > vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > wsdisplay0: screen 1-5 added (80x25, vt100 emulation) > xspd0 at pci0 dev 3 function 0 "XenSource Platform Device" rev 0x01 > isa0 at pcib0 > isadma0 at isa0 > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 > fd0 at fdc0 drive 0: density unknown > fd1 at fdc0 drive 1: density unknown > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > com0: console > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > pckbd0 at pckbc0 (kbd slot) > wskbd0 at pckbd0: console keyboard, using wsdisplay0 > pms0 at pckbc0 (aux slot) > wsmouse0 at pms0 mux 0 > pcppi0 at isa0 port 0x61 > spkr0 at pcppi0 > vmm at mainbus0 not configured > nvram: invalid checksum > vscsi0 at root > scsibus1 at vscsi0: 256 targets > softraid0 at root > scsibus2 at softraid0: 256 targets > root on wd0a (eeacdbd148573cfa.a) swap on wd0b dump on wd0b > clock: unknown CMOS layout > Automatic boot in progress: starting file system checks. > /dev/wd0a (eeacdbd148573cfa.a): file system is clean; not checking > setting tty flags > pf enabled > starting network > DHCPDISCOVER on xnf0 - interval 3 > DHCPOFFER from 172.31.16.1 (06:bc:14:46:67:74) > DHCPREQUEST on xnf0 to 255.255.255.255 > DHCPACK from 172.31.16.1 (06:bc:14:46:67:74) > bound to 172.31.17.41 -- renewal in 1800 seconds. > openssl: generating isakmpd/iked RSA keys... done. > ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 > starting early daemons: syslogd pflogd ntpd. > starting RPC daemons:. > savecore: no core dump > checking quotas: done. > clearing /tmp > kern.securelevel: 0 -> 1 > creating runtime link editor directory cache. > preserving editor files. > starting network daemons: sshd smtpd sndiod. > Path to firmware: http://firmware.openbsd.org/firmware/snapshots/ > No devices found which need firmware files to be downloaded. > starting local daemons: cron. > Wed Jan 6 15:31:42 CET 2016 > > OpenBSD/amd64 (openbsd.my.domain) (tty00) > > login: > > > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk From george at ceetonetechnology.com Thu Jan 7 15:01:13 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Thu, 7 Jan 2016 15:01:13 -0500 Subject: [talk] last night's installfest Message-ID: <568EC409.60301@ceetonetechnology.com> Installfests can be dry and turn into a bunch of people staring at the walls. Last night wasn't one of those nights. And I think it was clear we need to do them more. There was some confusion with the room, and we had to be out by 8 PM, but for the time we were there, it was a success. Poor Ike dragged a big container of cables and hardware from work... We had a good mix of the new and old, along with an array of hardware. Most of the BSDs were tinkered with, and hardware from BeagleBones and Raspberry Pis to Thinkpad Carbons and the venerable Soekris, etc., were install targets. For the next one, it would be good if more people hit talk@ and said what they wanted to get out of it... which BSD, which architecture, which hardware. g From mmatalka at gmail.com Thu Jan 7 15:06:03 2016 From: mmatalka at gmail.com (Malcolm Matalka) Date: Thu, 7 Jan 2016 21:06:03 +0100 Subject: [talk] last night's installfest In-Reply-To: <568EC409.60301@ceetonetechnology.com> References: <568EC409.60301@ceetonetechnology.com> Message-ID: How well is the Carbon supported on BSD? And which BSDs? Den 7 jan 2016 21:01 skrev "George Rosamond" : > Installfests can be dry and turn into a bunch of people staring at the > walls. > > Last night wasn't one of those nights. And I think it was clear we need > to do them more. > > There was some confusion with the room, and we had to be out by 8 PM, > but for the time we were there, it was a success. Poor Ike dragged a > big container of cables and hardware from work... > > We had a good mix of the new and old, along with an array of hardware. > Most of the BSDs were tinkered with, and hardware from BeagleBones and > Raspberry Pis to Thinkpad Carbons and the venerable Soekris, etc., were > install targets. > > For the next one, it would be good if more people hit talk@ and said > what they wanted to get out of it... which BSD, which architecture, > which hardware. > > g > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arielsanchezmora at gmail.com Thu Jan 7 15:07:19 2016 From: arielsanchezmora at gmail.com (=?UTF-8?Q?Ariel_S=C3=A1nchez?=) Date: Thu, 7 Jan 2016 15:07:19 -0500 Subject: [talk] last night's installfest In-Reply-To: <568EC409.60301@ceetonetechnology.com> References: <568EC409.60301@ceetonetechnology.com> Message-ID: On Jan 7, 2016 3:01 PM, "George Rosamond" wrote: > > Installfests can be dry and turn into a bunch of people staring at the > walls. > > Last night wasn't one of those nights. And I think it was clear we need > to do them more. > > There was some confusion with the room, and we had to be out by 8 PM, > but for the time we were there, it was a success. Poor Ike dragged a > big container of cables and hardware from work... > > We had a good mix of the new and old, along with an array of hardware. > Most of the BSDs were tinkered with, and hardware from BeagleBones and > Raspberry Pis to Thinkpad Carbons and the venerable Soekris, etc., were > install targets. > > For the next one, it would be good if more people hit talk@ and said > what they wanted to get out of it... which BSD, which architecture, > which hardware. > > g > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk Thanks so much for the Installfest. I for one had a great time installing my first real (not vm) openbsd on a cheap acer es1-111m-p2yu. It even picked up the lan and wireless from the get go. Now starts the learning process to turn it into the everyday laptop i want :) Ariel -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at ceetonetechnology.com Thu Jan 7 15:20:58 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Thu, 7 Jan 2016 15:20:58 -0500 Subject: [talk] last night's installfest In-Reply-To: References: <568EC409.60301@ceetonetechnology.com> Message-ID: <568EC8AA.1020609@ceetonetechnology.com> Ariel S?nchez: > On Jan 7, 2016 3:01 PM, "George Rosamond" > wrote: >> >> Installfests can be dry and turn into a bunch of people staring at the >> walls. >> >> Last night wasn't one of those nights. And I think it was clear we need >> to do them more. >> >> There was some confusion with the room, and we had to be out by 8 PM, >> but for the time we were there, it was a success. Poor Ike dragged a >> big container of cables and hardware from work... >> >> We had a good mix of the new and old, along with an array of hardware. >> Most of the BSDs were tinkered with, and hardware from BeagleBones and >> Raspberry Pis to Thinkpad Carbons and the venerable Soekris, etc., were >> install targets. >> >> For the next one, it would be good if more people hit talk@ and said >> what they wanted to get out of it... which BSD, which architecture, >> which hardware. >> >> g >> >> _______________________________________________ >> talk mailing list >> talk at lists.nycbug.org >> http://lists.nycbug.org/mailman/listinfo/talk > > Thanks so much for the Installfest. I for one had a great time installing > my first real (not vm) openbsd on a cheap acer es1-111m-p2yu. It even > picked up the lan and wireless from the get go. Now starts the learning > process to turn it into the everyday laptop i want :) > Great. And as a reminder, dmesgd.nycbug.org is a great place to upload your dmesgs, besides submitting to the OpenBSD project as detailed in the welcome email. g From scottro at nyc.rr.com Thu Jan 7 15:21:08 2016 From: scottro at nyc.rr.com (Scott Robbins) Date: Thu, 7 Jan 2016 15:21:08 -0500 Subject: [talk] last night's installfest In-Reply-To: References: <568EC409.60301@ceetonetechnology.com> Message-ID: <20160107202108.GA17976@scott1.scottro.net> On Thu, Jan 07, 2016 at 09:06:03PM +0100, Malcolm Matalka wrote: > How well is the Carbon supported on BSD? And which BSDs? What sort of video card? I know that the Haswell 4000 Intel card, which is used on a lot of newer laptops, isn't well supported in FreeBSD. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 From george at ceetonetechnology.com Fri Jan 8 09:19:10 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Fri, 8 Jan 2016 09:19:10 -0500 Subject: [talk] NYC*BUG Upcoming Message-ID: <568FC55E.6050304@ceetonetechnology.com> A lot of upcoming meetings are in the works, along with BSD events beyond NYC. *Conferences* March 10-13 AsiaBSDCon https://2016.asiabsdcon.org/ June 10-11 BSDCan https://www.bsdcan.org/2016/ (CFP closes January 19th) July 22-24 is HOPE (2600 Magazine), a great opportunity for BSD speakers particularly on topics related to security and privacy (http://xi.hope.net/). The CFP opens January 11. September, EuroBSDCon in Belgrade, Serbia (https://2016.eurobsdcon.org/) *NYC*BUG Meetings* All meetings are at Stone Creek at 140 E 27th Street (just east of Lexington Ave) in Manhattan February 3rd Ike Levy on Shell-Fu March 2nd Raul Cuza on BSD Init/RC system We're sorting out the dates, but other topics include: * Debuggers/LLVM (https://en.wikipedia.org/wiki/LLVM) * Urchin (https://github.com/tlevine/urchin) * LiteBSD/RetroBSD (https://github.com/sergev/LiteBSD/wiki, http://retrobsd.org/wiki/doku.php) * HardenedBSD (https://hardenedbsd.org/) Please email talk@ or admin@ if you have a potential meeting topic to discuss, including any recommendations. From george at ceetonetechnology.com Mon Jan 11 18:54:53 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Mon, 11 Jan 2016 18:54:53 -0500 Subject: [talk] ISC shifting license to MPL 2.0 In-Reply-To: <567AA65C.9070600@ceetonetechnology.com> References: <567AA65C.9070600@ceetonetechnology.com> Message-ID: <569440CD.6010700@ceetonetechnology.com> George Rosamond: > ISC is moving Kea (the replacement for ISC DHCP) to the MPL 2.0 from the > ISC license. > > "There is no longer a good reason for ISC to have its own license, > separate from everything else, even though we had and were using our > license years before most of these other licenses existed." > > https://www.isc.org/blogs/kea-license-2-0/ > On the ports at openbsd list, I see they stopped hosting Lynx. g From bcallah at devio.us Mon Jan 11 18:57:16 2016 From: bcallah at devio.us (Brian Callahan) Date: Mon, 11 Jan 2016 18:57:16 -0500 Subject: [talk] ISC shifting license to MPL 2.0 In-Reply-To: <569440CD.6010700@ceetonetechnology.com> References: <567AA65C.9070600@ceetonetechnology.com> <569440CD.6010700@ceetonetechnology.com> Message-ID: <5694415C.6020500@devio.us> On 1/11/2016 6:54 PM, George Rosamond wrote: > George Rosamond: >> ISC is moving Kea (the replacement for ISC DHCP) to the MPL 2.0 from the >> ISC license. >> >> "There is no longer a good reason for ISC to have its own license, >> separate from everything else, even though we had and were using our >> license years before most of these other licenses existed." >> >> https://www.isc.org/blogs/kea-license-2-0/ >> > On the ports at openbsd list, I see they stopped hosting Lynx. > > g > I don't see how those two things are related. lynx is GPLv2 licensed. Always has been. ~Brian From george at ceetonetechnology.com Mon Jan 11 19:00:02 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Mon, 11 Jan 2016 19:00:02 -0500 Subject: [talk] ISC shifting license to MPL 2.0 In-Reply-To: <5694415C.6020500@devio.us> References: <567AA65C.9070600@ceetonetechnology.com> <569440CD.6010700@ceetonetechnology.com> <5694415C.6020500@devio.us> Message-ID: <56944202.7040703@ceetonetechnology.com> Brian Callahan: > > > On 1/11/2016 6:54 PM, George Rosamond wrote: >> George Rosamond: >>> ISC is moving Kea (the replacement for ISC DHCP) to the MPL 2.0 from the >>> ISC license. >>> >>> "There is no longer a good reason for ISC to have its own license, >>> separate from everything else, even though we had and were using our >>> license years before most of these other licenses existed." >>> >>> https://www.isc.org/blogs/kea-license-2-0/ >>> >> On the ports at openbsd list, I see they stopped hosting Lynx. >> >> g >> > > I don't see how those two things are related. lynx is GPLv2 licensed. > Always has been. Related insofar as they are both connected to ISC. g From jesse at emptysquare.net Tue Jan 12 21:05:28 2016 From: jesse at emptysquare.net (A. Jesse Jiryu Davis) Date: Tue, 12 Jan 2016 21:05:28 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: <568A7B18.6050805@osfda.org> References: <568A7B18.6050805@osfda.org> Message-ID: With your help I've convinced myself that modern Mac OS X's getaddrinfo is indeed thread-safe on version 10.10. I wrote up my findings in a CPython bug report: http://bugs.python.org/issue25924 Now I just need to get my hands on a machine running Mac OS X 10.4 and confirm that getaddrinfo is NOT thread-safe there.... On Mon, Jan 4, 2016 at 9:00 AM, Steve wrote: > Sometimes they do things like that for backlevel compatibility; so single > threaded apps that rely on that global don't immediately break. > The question is: does ds_getaddrinfo _rely_ on that variable? > > I doubt it; but it's _possible_ you found an oversight! > > > > On 1/3/2016 10:57 AM, A. Jesse Jiryu Davis wrote: > > Thanks for the pointers, with your help I'm making progress. I think I > found the source for Apple's getaddrinfo. > > In Apple's Libinfo version 222.4.12, the man page says getaddrinfo isn't > thread-safe: > > > http://www.opensource.apple.com/source/Libinfo/Libinfo-222.4.12/lookup.subproj/getaddrinfo.3 > > And here's its source: > > > http://www.opensource.apple.com/source/Libinfo/Libinfo-222.4.12/lookup.subproj/getaddrinfo.c > > Glancing at the source na?vely, I might see the data race: getaddrinfo > calls gai_lookupd, which reads and writes the global static variable > "gai_proc". I can't see what will go wrong as a result of the race, but it > sure LOOKS bad. =) > > In the next release, version 278, the thread-safety warning is gone from > the man page: > > > http://www.opensource.apple.com/source/Libinfo/Libinfo-278/lookup.subproj/getaddrinfo.3 > > And getaddrinfo is largely rewritten: > > > http://www.opensource.apple.com/source/Libinfo/Libinfo-278/lookup.subproj/getaddrinfo.c > > It calls a new function, "ds_getaddrinfo". But ds_getaddrinfo still > accesses the global static variable "gai_proc"; I wonder why this is > considered thread-safe now? > > On Sun, Jan 3, 2016 at 12:14 AM, Siobhan Lynch wrote: > >> OK? try and look at the revision histories of these three files: >> >> *#include* ** >> *#include* ** >> *#include* ** >> >> >> *-Trish* >> >> >> > > > _______________________________________________ > talk mailing listtalk at lists.nycbug.orghttp://lists.nycbug.org/mailman/listinfo/talk > > > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jkeen at verizon.net Tue Jan 12 21:36:22 2016 From: jkeen at verizon.net (James E Keenan) Date: Tue, 12 Jan 2016 21:36:22 -0500 Subject: [talk] Is getaddrinfo thread-safe on OS X? In-Reply-To: References: <568A7B18.6050805@osfda.org> Message-ID: <5695B826.8090808@verizon.net> On 01/12/2016 09:05 PM, A. Jesse Jiryu Davis wrote: > With your help I've convinced myself that modern Mac OS X's getaddrinfo is > indeed thread-safe on version 10.10. I wrote up my findings in a CPython > bug report: > > http://bugs.python.org/issue25924 > > Now I just need to get my hands on a machine running Mac OS X 10.4 and > confirm that getaddrinfo is NOT thread-safe there.... > Would an iBook G4 running Mac OS X 10.4.11, Darwin/PPC, suffice? If so, contact me. Thank you very much. Jim Keenan From george at ceetonetechnology.com Thu Jan 14 09:04:41 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Thu, 14 Jan 2016 09:04:41 -0500 Subject: [talk] NYC*BUG Announcements Message-ID: <5697AAF9.3080506@ceetonetechnology.com> A number of things to note: * We are now hosting a mailing list for CharmBUG, a *BSD user group in Baltimore, Maryland http://lists.nycbug.org/mailman/listinfo/charmbug * AsiaBSDCon (.org) is March 10-13 in Tokyo, Japan. * BSDCan (.org) is June 10-11 in Ottawa, Canada, and the call for submissions closes in five days on January 19th. * Is your company looking for summer interns? Don't hesitate to post to the NYC*BUG jobs list at http://lists.nycbug.org/mailman/listinfo/jobs * HOPE (Hackers on Planet Earth) is scheduled for July 22-24 in Manhattan. The call for participation is open, and it's a great opportunity for *BSD users and developers to speak to a broader audience (http://xi.hope.net/speakers) with presentations or workshops. * Upcoming meetings include: February 3, Ike Levy on "Shell Fu" March 2, Raul Cuza on "BSD Init/RC" Other planned meetings include "Debugging with LLVM", "Urchin," "Lite and RetroBSD" and another installfest, most likely in August. From george at ceetonetechnology.com Thu Jan 14 09:49:00 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Thu, 14 Jan 2016 09:49:00 -0500 Subject: [talk] SSH vulnerability Message-ID: <5697B55C.8000206@ceetonetechnology.com> echo "UseRoaming no" >>/etc/ssh/ssh_config https://marc.info/?l=openbsd-misc&m=145278077920530&w=2 Affects all OSs, it sounds like. g From chsnyder at gmail.com Thu Jan 14 10:30:07 2016 From: chsnyder at gmail.com (Chris Snyder) Date: Thu, 14 Jan 2016 10:30:07 -0500 Subject: [talk] SSH vulnerability In-Reply-To: <5697B55C.8000206@ceetonetechnology.com> References: <5697B55C.8000206@ceetonetechnology.com> Message-ID: On Thu, Jan 14, 2016 at 9:49 AM, George Rosamond < george at ceetonetechnology.com> wrote: > echo "UseRoaming no" >>/etc/ssh/ssh_config > > https://marc.info/?l=openbsd-misc&m=145278077920530&w=2 > > Affects all OSs, it sounds like. > > g > > > Client bug, not server. OK. -------------- next part -------------- An HTML attachment was scrubbed... URL: From george at ceetonetechnology.com Thu Jan 14 10:30:59 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Thu, 14 Jan 2016 10:30:59 -0500 Subject: [talk] SSH vulnerability In-Reply-To: References: <5697B55C.8000206@ceetonetechnology.com> Message-ID: <5697BF33.7030309@ceetonetechnology.com> Chris Snyder: > On Thu, Jan 14, 2016 at 9:49 AM, George Rosamond < > george at ceetonetechnology.com> wrote: > >> echo "UseRoaming no" >>/etc/ssh/ssh_config >> >> https://marc.info/?l=openbsd-misc&m=145278077920530&w=2 >> >> Affects all OSs, it sounds like. >> >> g >> >> >> > Client bug, not server. OK. > yes... ssh_config, not sshd_config. http://undeadly.org/cgi?action=article&sid=20160114142733 https://lists.mindrot.org/pipermail/openssh-unix-dev/2016-January/034680.html g From george at ceetonetechnology.com Thu Jan 14 11:28:52 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Thu, 14 Jan 2016 11:28:52 -0500 Subject: [talk] SSH vulnerability In-Reply-To: References: <5697B55C.8000206@ceetonetechnology.com> <5697BF33.7030309@ceetonetechnology.com> Message-ID: <5697CCC4.10405@ceetonetechnology.com> Isaac (.ike) Levy: > >> On Jan 14, 2016, at 10:30 AM, George Rosamond >> wrote: >> >> yes... ssh_config, not sshd_config. > > What an interesting vuln. Seems to blur the line between client and > server to exploit this one. > > Big question now that it's been addressed: will this be the third > "remote hole in the default install"? It's on the client end, and the exploit is a MITM AFAIK, so probably not considered a remote hole. g From george at ceetonetechnology.com Thu Jan 14 12:48:10 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Thu, 14 Jan 2016 12:48:10 -0500 Subject: [talk] box running almost 19 years... Message-ID: <5697DF5A.9090104@ceetonetechnology.com> With FreeBSD 2.2.1. http://www.theregister.co.uk/2016/01/14/server_retired_after_18_years_and_ten_months_beat_that_readers/ Obviously the OS is secondary to hardware, but still... g From nick at hackermonkey.com Fri Jan 15 20:34:14 2016 From: nick at hackermonkey.com (Nick Danger) Date: Fri, 15 Jan 2016 20:34:14 -0500 Subject: [talk] box running almost 19 years... In-Reply-To: <5697DF5A.9090104@ceetonetechnology.com> References: <5697DF5A.9090104@ceetonetechnology.com> Message-ID: <56999E16.5060409@hackermonkey.com> The article doesn't mention if that was uninterrupted uptime! Still an impressive feat. -Nick On 01/14/2016 12:48 PM, George Rosamond wrote: > With FreeBSD 2.2.1. > > http://www.theregister.co.uk/2016/01/14/server_retired_after_18_years_and_ten_months_beat_that_readers/ > > Obviously the OS is secondary to hardware, but still... > > g > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk From raulcuza at gmail.com Fri Jan 22 09:58:49 2016 From: raulcuza at gmail.com (Raul Cuza) Date: Fri, 22 Jan 2016 09:58:49 -0500 Subject: [talk] IPv6 DoS Vulnerability (CVE-2016-1879) Message-ID: SCTP ICMPv6 error processing vulnerability (CVE-2016-1879) A detailed write up can be found at http://blog.ptsecurity.com/2016/01/severe-vulnerabilities-detected-in.html?m=1 (video demo is a nice touch) tl;dr The default configuration of FreeBSD (v9.3, 10.1, and 10.2) is vulnerable to maliciously crafted ICMPv6 message. From spork at bway.net Fri Jan 22 13:31:41 2016 From: spork at bway.net (Charles Sprickman) Date: Fri, 22 Jan 2016 13:31:41 -0500 Subject: [talk] IPv6 DoS Vulnerability (CVE-2016-1879) In-Reply-To: References: Message-ID: On Jan 22, 2016, at 9:58 AM, Raul Cuza wrote: > > SCTP ICMPv6 error processing vulnerability (CVE-2016-1879) > A detailed write up can be found at > http://blog.ptsecurity.com/2016/01/severe-vulnerabilities-detected-in.html?m=1 > (video demo is a nice touch) The telecom section of their site is pretty fascinating: http://blog.ptsecurity.com/search/label/telecom The phrase ?root via SMS? scares me. > tl;dr The default configuration of FreeBSD (v9.3, 10.1, and 10.2) is > vulnerable to maliciously crafted ICMPv6 message. > > _______________________________________________ > talk mailing list > talk at lists.nycbug.org > http://lists.nycbug.org/mailman/listinfo/talk From george at ceetonetechnology.com Mon Jan 25 09:37:13 2016 From: george at ceetonetechnology.com (George Rosamond) Date: Mon, 25 Jan 2016 09:37:13 -0500 Subject: [talk] NYC*BUG Upcoming Message-ID: <56A63319.90300@ceetonetechnology.com> We said we had an exciting list of upcoming meetings--and we weren't lying. Tentatively this is the lineup, although we are still working on getting some of the details up. All meetings will (likely) be in the backroom of Stone Creek. * February 3 "shell-fu" Isaac (.ike) Levy * March 2 "Discussion of the Past and Future of PID 1 on BSD" Raul Cuza Raul's meeting is something of a reply to reaffirmation of the BSD init/rc systems, in the face of systemd * April 6 "Debugging with llvm" John Wolfe * May 4 "Urchin: Putting an End to Sloppy Shell Code" Thomas Levine * June 15 "Adventures in HardenedBSD" Shawn Webb Shawn will be coming up from Maryland for this meeting. Note the date which was set as to not conflict with BSDCan * July 6 "Meet the Smallest BSDs: RetroBSD and LiteBSD" Brian Callahan * August 3 A *BSD Installfest This installfest will happen after HOPE, and is a great meeting to publicize at HOPE. We should have fliers for this event at HOPE * Sept 7 "Teaching FreeBSD" George Neville-Neil Also note these other upcoming events: * Tokyo, Japan: AsiaBSCon, March 10-13 * Ottawa, Canada: BSDCan, June 10-11 with tutorials and the dev summit beforehand * New York, NY: HOPE (Hackers on Planet Earth), July 22-24 a great opportunity for more popular BSD-related presentations ************************ Feb 3: Isaac Levy on "shell-fu" 18:45, Stone Creek Bar & Lounge: 140 E 27th St Abstract shell-fu in 3 short talks To say everything starts with the shell, is quite an understatement. Portable shell programming does not have to be painful, exposing the raw power of UNIX with shell can even be fun. This talk is relevant for expert and novice alike, aimed at anyone who uses UNIX systems. Not the 'shell tricks' variety of talk, but a language discussion focused on portability, and showing off how simple and profoundly powerful portable shell can be. We will cover: the 3 finger claw technique using atomic filesystem operations general shell-fu, input and variable handling There is always something amazing to learn about sh(1). Speaker Bio Isaac (.ike) Levy is a crusty UNIX Hacker. A long-time community contributor to the *BSD's, ike is obsessed with high-availability and redundant networked servers systems, mostly because he likes to sleep at night. Standing on the shoulders of giants, his background includes partnering to run a Virtual Server ISP before anyone called it a cloud, as well as having a long history building internet-facing infrastructure with UNIX systems. .ike has been a part of NYC*BUG since it was first launched in January 2004. He was a long-time member of the Lower East Side Mac Unix User Group, and is still in denial that this group no longer exists. He has spoken frequently on a number of UNIX and internet security topics at various venues, particularly on the topic of FreeBSD's jail(8). From mcevoy.pat at gmail.com Thu Jan 28 14:32:00 2016 From: mcevoy.pat at gmail.com (Pat McEvoy) Date: Thu, 28 Jan 2016 14:32:00 -0500 Subject: [talk] Building a data center? Need a clean room floor? Message-ID: http://hudsonvalley.craigslist.org/zip/5421628816.html Little north of NYC, but the price is right once you get insurance. Patrick