From rch at umail.ucsb.edu Thu Mar 1 00:35:53 2007 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Thu Mar 1 00:36:07 2007 Subject: [Tdg] julian dates Message-ID: <45E69069.7080206@umail.ucsb.edu> Check it out.. Julian Dates: http://aa.usno.navy.mil/data/docs/JulianDate.html This is one of the "better" Julian Dates calculator online. It works for BCE years, leap years, and far into the future. Algorithm based on Numerical Recipes in C (ch 1.1, p.11-14). It is also the US Naval Observatory site so you'd think it'd be good. If you enter March 1st, 2100 you get JD: 2488128.5 If you enter Feb 29th, 2100 you also get JD: 2488128.5 If you do the reverse from 2488128.5 you get: Feb 29th, 2100 If you do the reverse from 2488129.5 you get: Mar 2nd, 2100 In other words, on these years (1600, 1700, 1900, 2100, etc.) there >is< no March 1st. This is problematic because it implies that it is not possible to represent March 1st dates on century years after 1600. Who needs these date anyway.. Feel free to test your favorite Julian Date calculator with this. I can't find another JD algorithm that doesn't fail the test. -R From wesley.hoke at gmail.com Thu Mar 1 00:41:42 2007 From: wesley.hoke at gmail.com (Wesley Smith) Date: Thu Mar 1 00:41:55 2007 Subject: [Tdg] julian dates In-Reply-To: <45E69069.7080206@umail.ucsb.edu> References: <45E69069.7080206@umail.ucsb.edu> Message-ID: <1079b050703010041x7697aaefv647c4ad5178cb926@mail.gmail.com> Are you suggesting that MintEvent's timestamp be a Julian date so that Mint-based apps wouldn't work on March 1st some years? wes On 3/1/07, Rama Hoetzlein wrote: > Check it out.. > > Julian Dates: http://aa.usno.navy.mil/data/docs/JulianDate.html > > This is one of the "better" Julian Dates calculator online. It works for > BCE years, leap years, and far into the future. Algorithm based on > Numerical Recipes in C (ch 1.1, p.11-14). It is also the US Naval > Observatory site so you'd think it'd be good. > > If you enter March 1st, 2100 you get JD: 2488128.5 > If you enter Feb 29th, 2100 you also get JD: 2488128.5 > If you do the reverse from 2488128.5 you get: Feb 29th, 2100 > If you do the reverse from 2488129.5 you get: Mar 2nd, 2100 > > In other words, on these years (1600, 1700, 1900, 2100, etc.) there >is< > no March 1st. > This is problematic because it implies that it is not possible to > represent March 1st dates on century years after 1600. > > Who needs these date anyway.. > > Feel free to test your favorite Julian Date calculator with this. > I can't find another JD algorithm that doesn't fail the test. > > -R > > > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > From rch at umail.ucsb.edu Thu Mar 1 00:44:37 2007 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Thu Mar 1 00:44:52 2007 Subject: [Tdg] julian dates In-Reply-To: <1079b050703010041x7697aaefv647c4ad5178cb926@mail.gmail.com> References: <45E69069.7080206@umail.ucsb.edu> <1079b050703010041x7697aaefv647c4ad5178cb926@mail.gmail.com> Message-ID: <45E69275.3010307@umail.ucsb.edu> Yep.. but not until 2100, when mint = skynet. R Wesley Smith wrote: > Are you suggesting that MintEvent's timestamp be a Julian date so that > Mint-based apps wouldn't work on March 1st some years? > > wes > > On 3/1/07, Rama Hoetzlein wrote: > >> Check it out.. >> >> Julian Dates: http://aa.usno.navy.mil/data/docs/JulianDate.html >> >> This is one of the "better" Julian Dates calculator online. It works for >> BCE years, leap years, and far into the future. Algorithm based on >> Numerical Recipes in C (ch 1.1, p.11-14). It is also the US Naval >> Observatory site so you'd think it'd be good. >> >> If you enter March 1st, 2100 you get JD: 2488128.5 >> If you enter Feb 29th, 2100 you also get JD: 2488128.5 >> If you do the reverse from 2488128.5 you get: Feb 29th, 2100 >> If you do the reverse from 2488129.5 you get: Mar 2nd, 2100 >> >> In other words, on these years (1600, 1700, 1900, 2100, etc.) there >is< >> no March 1st. >> This is problematic because it implies that it is not possible to >> represent March 1st dates on century years after 1600. >> >> Who needs these date anyway.. >> >> Feel free to test your favorite Julian Date calculator with this. >> I can't find another JD algorithm that doesn't fail the test. >> >> -R >> >> >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From rch at umail.ucsb.edu Thu Mar 1 00:55:35 2007 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Thu Mar 1 00:55:51 2007 Subject: [Tdg] julian dates Message-ID: <45E69507.40805@umail.ucsb.edu> Ah.. i figured it out.. Their inverse calculation is incorrect. The calculation of Julian dates is still correct. Apparently century years are not leap years, so there is no Feb 29th on 1600, 1700, 1800, 1900, 2100. (but there is a Feb 29th, 2000). When you enter Feb 29th, 2100 it shows Feb 29th - but there is no Feb 29th, 2100. It should be Mar 1st, 2100. When you enter Mar 1st, 2100 are reverse it, it becomes Feb 29th - It should be Mar 1st, 2100. What they are supposed to do is show Mar 1st for both of these, or given an error if you enter Feb 29th, 2100. The representation of Julian Date is correct, but the reverse calculation (to get m/d/y) is incorrect. It looks like many other online JD calculators do this too (most others are based on this one) R From wesley.hoke at gmail.com Thu Mar 1 09:59:48 2007 From: wesley.hoke at gmail.com (Wesley Smith) Date: Thu Mar 1 10:00:10 2007 Subject: [Tdg] Macromania Message-ID: <1079b050703010959r3e5bd1f9s199958adc47b15c4@mail.gmail.com> Hi mint lovers, I was just reminded of som experiences I had with OpenCV and macros that were laced throughout the code. It really sucks to debug this shit, especially in something like gdb. I would like to keep macro creep out of the mint core as much as possible where it obscures code. wes From alex at neisis.net Thu Mar 1 10:02:02 2007 From: alex at neisis.net (Alex Norman) Date: Thu Mar 1 10:02:11 2007 Subject: [Tdg] Macromania In-Reply-To: <1079b050703010959r3e5bd1f9s199958adc47b15c4@mail.gmail.com> References: <1079b050703010959r3e5bd1f9s199958adc47b15c4@mail.gmail.com> Message-ID: <20070301180202.GA22044@silverninja.net> Yes, lets use scripts to generate stubs! -Alex On 0, Wesley Smith wrote: > Hi mint lovers, > I was just reminded of som experiences I had with OpenCV and macros > that were laced throughout the code. It really sucks to debug this > shit, especially in something like gdb. I would like to keep macro > creep out of the mint core as much as possible where it obscures code. > > wes > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wesley.hoke at gmail.com Thu Mar 1 10:06:33 2007 From: wesley.hoke at gmail.com (Wesley Smith) Date: Thu Mar 1 10:08:25 2007 Subject: [Tdg] Macromania In-Reply-To: <20070301180202.GA22044@silverninja.net> References: <1079b050703010959r3e5bd1f9s199958adc47b15c4@mail.gmail.com> <20070301180202.GA22044@silverninja.net> Message-ID: <1079b050703011006x7dcb1b3m7e931afc44dc0aea@mail.gmail.com> Not! On 3/1/07, Alex Norman wrote: > Yes, lets use scripts to generate stubs! > > -Alex > > On 0, Wesley Smith wrote: > > Hi mint lovers, > > I was just reminded of som experiences I had with OpenCV and macros > > that were laced throughout the code. It really sucks to debug this > > shit, especially in something like gdb. I would like to keep macro > > creep out of the mint core as much as possible where it obscures code. > > > > wes > > _______________________________________________ > > Tdg mailing list > > Tdg@mat.ucsb.edu > > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > From wesley.hoke at gmail.com Thu Mar 1 12:23:57 2007 From: wesley.hoke at gmail.com (Wesley Smith) Date: Thu Mar 1 12:24:06 2007 Subject: [Tdg] Macromania In-Reply-To: <1079b050703011006x7dcb1b3m7e931afc44dc0aea@mail.gmail.com> References: <1079b050703010959r3e5bd1f9s199958adc47b15c4@mail.gmail.com> <20070301180202.GA22044@silverninja.net> <1079b050703011006x7dcb1b3m7e931afc44dc0aea@mail.gmail.com> Message-ID: <1079b050703011223l46eaedd7sb6236ba26e3c27c4@mail.gmail.com> Well maybe! I didn't read your other email! wes On 3/1/07, Wesley Smith wrote: > Not! > > On 3/1/07, Alex Norman wrote: > > Yes, lets use scripts to generate stubs! > > > > -Alex > > > > On 0, Wesley Smith wrote: > > > Hi mint lovers, > > > I was just reminded of som experiences I had with OpenCV and macros > > > that were laced throughout the code. It really sucks to debug this > > > shit, especially in something like gdb. I would like to keep macro > > > creep out of the mint core as much as possible where it obscures code. > > > > > > wes > > > _______________________________________________ > > > Tdg mailing list > > > Tdg@mat.ucsb.edu > > > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > > Tdg mailing list > > Tdg@mat.ucsb.edu > > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > From alex at neisis.net Thu Mar 1 12:29:27 2007 From: alex at neisis.net (Alex Norman) Date: Thu Mar 1 12:29:35 2007 Subject: [Tdg] Macromania In-Reply-To: <1079b050703011223l46eaedd7sb6236ba26e3c27c4@mail.gmail.com> References: <1079b050703010959r3e5bd1f9s199958adc47b15c4@mail.gmail.com> <20070301180202.GA22044@silverninja.net> <1079b050703011006x7dcb1b3m7e931afc44dc0aea@mail.gmail.com> <1079b050703011223l46eaedd7sb6236ba26e3c27c4@mail.gmail.com> Message-ID: <20070301202927.GK22044@silverninja.net> Yeah, the scripts wouldn't be required, but if you want to use them they'd copy in all the stuff for you that the MACROS would have done, except it would all be right there and you just fill in the gaps instead of having some macro that hides the stuff. I'll make an "event" and "eventgroup" generator script soon. -Alex On 0, Wesley Smith wrote: > Well maybe! I didn't read your other email! > > wes > > On 3/1/07, Wesley Smith wrote: > >Not! > > > >On 3/1/07, Alex Norman wrote: > >> Yes, lets use scripts to generate stubs! > >> > >> -Alex > >> > >> On 0, Wesley Smith wrote: > >> > Hi mint lovers, > >> > I was just reminded of som experiences I had with OpenCV and macros > >> > that were laced throughout the code. It really sucks to debug this > >> > shit, especially in something like gdb. I would like to keep macro > >> > creep out of the mint core as much as possible where it obscures code. > >> > > >> > wes > >> > _______________________________________________ > >> > Tdg mailing list > >> > Tdg@mat.ucsb.edu > >> > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> _______________________________________________ > >> Tdg mailing list > >> Tdg@mat.ucsb.edu > >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Thu Mar 1 13:10:48 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Thu Mar 1 13:10:56 2007 Subject: [Tdg] julian dates In-Reply-To: <45E69275.3010307@umail.ucsb.edu> References: <45E69069.7080206@umail.ucsb.edu> <1079b050703010041x7697aaefv647c4ad5178cb926@mail.gmail.com> <45E69275.3010307@umail.ucsb.edu> Message-ID: du du ... du ... du du ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... du du ... du ... du du ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... du du ... du ... du du ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... du du ... du ... du du ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... On Mar 1, 2007, at 12:44 AM, Rama Hoetzlein wrote: > Yep.. but not until 2100, when mint = skynet. > > R > > Wesley Smith wrote: > >> Are you suggesting that MintEvent's timestamp be a Julian date so >> that >> Mint-based apps wouldn't work on March 1st some years? >> >> wes >> >> On 3/1/07, Rama Hoetzlein wrote: >> >>> Check it out.. >>> >>> Julian Dates: http://aa.usno.navy.mil/data/docs/JulianDate.html >>> >>> This is one of the "better" Julian Dates calculator online. It >>> works for >>> BCE years, leap years, and far into the future. Algorithm based on >>> Numerical Recipes in C (ch 1.1, p.11-14). It is also the US Naval >>> Observatory site so you'd think it'd be good. >>> >>> If you enter March 1st, 2100 you get JD: 2488128.5 >>> If you enter Feb 29th, 2100 you also get JD: 2488128.5 >>> If you do the reverse from 2488128.5 you get: Feb 29th, 2100 >>> If you do the reverse from 2488129.5 you get: Mar 2nd, 2100 >>> >>> In other words, on these years (1600, 1700, 1900, 2100, etc.) >>> there >is< >>> no March 1st. >>> This is problematic because it implies that it is not possible to >>> represent March 1st dates on century years after 1600. >>> >>> Who needs these date anyway.. >>> >>> Feel free to test your favorite Julian Date calculator with this. >>> I can't find another JD algorithm that doesn't fail the test. >>> >>> -R >>> >>> >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Thu Mar 1 13:12:03 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Thu Mar 1 13:12:12 2007 Subject: [Tdg] julian dates In-Reply-To: <45E69275.3010307@umail.ucsb.edu> References: <45E69069.7080206@umail.ucsb.edu> <1079b050703010041x7697aaefv647c4ad5178cb926@mail.gmail.com> <45E69275.3010307@umail.ucsb.edu> Message-ID: <41884208-0180-4C09-97C1-35B01D7D3B2C@mat.ucsb.edu> But what happens to the julian date if you travel back in time? you have to go naked, you can't even take your julian date wristwatch with you, i promise. even the governor will tell you that. On Mar 1, 2007, at 12:44 AM, Rama Hoetzlein wrote: > Yep.. but not until 2100, when mint = skynet. > > R > > Wesley Smith wrote: > >> Are you suggesting that MintEvent's timestamp be a Julian date so >> that >> Mint-based apps wouldn't work on March 1st some years? >> >> wes >> >> On 3/1/07, Rama Hoetzlein wrote: >> >>> Check it out.. >>> >>> Julian Dates: http://aa.usno.navy.mil/data/docs/JulianDate.html >>> >>> This is one of the "better" Julian Dates calculator online. It >>> works for >>> BCE years, leap years, and far into the future. Algorithm based on >>> Numerical Recipes in C (ch 1.1, p.11-14). It is also the US Naval >>> Observatory site so you'd think it'd be good. >>> >>> If you enter March 1st, 2100 you get JD: 2488128.5 >>> If you enter Feb 29th, 2100 you also get JD: 2488128.5 >>> If you do the reverse from 2488128.5 you get: Feb 29th, 2100 >>> If you do the reverse from 2488129.5 you get: Mar 2nd, 2100 >>> >>> In other words, on these years (1600, 1700, 1900, 2100, etc.) >>> there >is< >>> no March 1st. >>> This is problematic because it implies that it is not possible to >>> represent March 1st dates on century years after 1600. >>> >>> Who needs these date anyway.. >>> >>> Feel free to test your favorite Julian Date calculator with this. >>> I can't find another JD algorithm that doesn't fail the test. >>> >>> -R >>> >>> >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Thu Mar 1 13:13:38 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Thu Mar 1 13:13:46 2007 Subject: [Tdg] Macromania In-Reply-To: <20070301202927.GK22044@silverninja.net> References: <1079b050703010959r3e5bd1f9s199958adc47b15c4@mail.gmail.com> <20070301180202.GA22044@silverninja.net> <1079b050703011006x7dcb1b3m7e931afc44dc0aea@mail.gmail.com> <1079b050703011223l46eaedd7sb6236ba26e3c27c4@mail.gmail.com> <20070301202927.GK22044@silverninja.net> Message-ID: <0CF8A1D8-E98E-4CD1-A3EC-8E179262ED77@mat.ucsb.edu> In fact I'm seriously thinking about writing my C++ stuff in Lua or Ruby from now on, and generating the .h / .cpp files from there. I mean, why not? Way easier. I hate the lame refactoring bs that C++ demands. On Mar 1, 2007, at 12:29 PM, Alex Norman wrote: > Yeah, the scripts wouldn't be required, but if you want to use them > they'd copy > in all the stuff for you that the MACROS would have done, except it > would all > be right there and you just fill in the gaps instead of having some > macro that > hides the stuff. I'll make an "event" and "eventgroup" generator > script soon. > > -Alex > > On 0, Wesley Smith wrote: >> Well maybe! I didn't read your other email! >> >> wes >> >> On 3/1/07, Wesley Smith wrote: >>> Not! >>> >>> On 3/1/07, Alex Norman wrote: >>>> Yes, lets use scripts to generate stubs! >>>> >>>> -Alex >>>> >>>> On 0, Wesley Smith wrote: >>>>> Hi mint lovers, >>>>> I was just reminded of som experiences I had with OpenCV and >>>>> macros >>>>> that were laced throughout the code. It really sucks to debug >>>>> this >>>>> shit, especially in something like gdb. I would like to keep >>>>> macro >>>>> creep out of the mint core as much as possible where it >>>>> obscures code. >>>>> >>>>> wes >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From rch at umail.ucsb.edu Thu Mar 1 17:29:03 2007 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Thu Mar 1 17:29:12 2007 Subject: [Tdg] Core commit Message-ID: <45E77DDF.40204@umail.ucsb.edu> Ok.. It builds. I did a first core commit to the subversion repo. Heres what's there: - New event code - Minimal application and scheduler - Placeholders for event queue, memory pool, timer - Core_easy built as separate lib - Log files - Test system lib (graphics) - Test app (test_app) - VisualStudio solution + projects I put everything in \core\branches\mint for now. The repository is at: rails.mat.ucsb.edu rails/mat/groups/tdg/svn I'm sure this won't build in gcc.. but its probably not far. Rama From rch at umail.ucsb.edu Thu Mar 1 20:35:09 2007 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Thu Mar 1 20:35:21 2007 Subject: [Tdg] Code commit Message-ID: <45E7A97D.2000204@umail.ucsb.edu> Ok.. It builds & runs.. The code base has been committed to subversion repo. Heres what's there: - New event stuff - Minimal application & scheduler - Placeholders for event queue, mem pool, etc. - Core_easy as a separate library - Example system library (graphics) - Example app (test_app) - Visual Studio solutions + projects - lots of other stuff we discussed. The stuff is in the repository under: \core\branch\mint The libs build a run in VS. I doubt it will build in gcc.. but probably not far off. Rama From wakefield at mat.ucsb.edu Fri Mar 2 00:26:56 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 00:27:06 2007 Subject: [Tdg] Code commit In-Reply-To: <45E7A97D.2000204@umail.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> Message-ID: <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> If I can figure out my SVN client, I'll try and build an Xcode project and add it. On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > Ok.. It builds & runs.. The code base has been committed to > subversion repo. > > Heres what's there: > - New event stuff > - Minimal application & scheduler > - Placeholders for event queue, mem pool, etc. > - Core_easy as a separate library > - Example system library (graphics) > - Example app (test_app) > - Visual Studio solutions + projects > - lots of other stuff we discussed. > > The stuff is in the repository under: > \core\branch\mint > > The libs build a run in VS. I doubt it will build in gcc.. but > probably not far off. > > Rama > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Fri Mar 2 00:49:13 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 00:49:31 2007 Subject: [Tdg] Core commit In-Reply-To: <45E77DDF.40204@umail.ucsb.edu> References: <45E77DDF.40204@umail.ucsb.edu> Message-ID: Is there a public URL for the subversion repository? I'm trying to set it up on svnx. I can't ssh to rails, my pwd doesn't work (it does work for FTP though... weird). On Mar 1, 2007, at 5:29 PM, Rama Hoetzlein wrote: > Ok.. It builds. I did a first core commit to the subversion repo. > > Heres what's there: > - New event code > - Minimal application and scheduler > - Placeholders for event queue, memory pool, timer > - Core_easy built as separate lib > - Log files > - Test system lib (graphics) > - Test app (test_app) > - VisualStudio solution + projects > > I put everything in \core\branches\mint for now. > > The repository is at: > rails.mat.ucsb.edu > rails/mat/groups/tdg/svn > > I'm sure this won't build in gcc.. but its probably not far. > > Rama > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From lists at grahamwakefield.net Fri Mar 2 00:53:30 2007 From: lists at grahamwakefield.net (Graham Wakefield) Date: Fri Mar 2 00:53:39 2007 Subject: [Tdg] event dispatch Message-ID: Found this online, thought it was a nice summary of some of the issues we have been discussing: Many different event dispatching strategies have been invented. Here is a small selection: One-Big-Switch: All control-flow relevant processing is done from a single main loop in a single function. Context is kept in local variables. That's the way some network servers have been implemented. I guess most event dispatchers started this way and have moved on to the callback model later. Maybe ok for your pet project. But please use a strategy that provides a better abstraction for anything bigger. Callbacks: A callback function is invoked whenever an event triggers. The intra-call context has to be kept in state variables that have to be passed around. This strategy is commonly used for GUIs and quite a few network servers. Good for simple tasks. Breaking the control flow up into many small snippets and passing the context quickly becomes annoying for anything more complicated. State machines: A triggered event is interpreted as a state machine transition. Depending on the current state and the transition some processing is done and then a new current state is set. The intra- state context has to be kept in the state machine or in other variables that have to be passed around. Most useful for processing complicated and layered protocols. Designing and debugging a state machine is not for the faint-hearted. Continuations: This mechanism depends on implementation language support for closures that can be returned as first class objects and/ or proper tail calls (Lua has both). A triggered event invokes the continuation that has been passed to the dispatcher from a previous invocation. The closures keep the context between continuations. Rather uncommon and there are some pitfalls (like loops). Please report if you have survived. Coroutine dispatcher: A specific coroutine is resumed whenever an event triggers. This coroutine yields back to the dispatcher when it needs to wait for an event. The context is kept in the stack of the coroutine. Allows you to keep the linear flow of control. Depends on good support for coroutines and the ability to yield from anywhere in the call stack. Lua qualifies (with the exception of pcall). Most other languages don't and this is the only reason why it's uncommon. It's extremly convenient and marries the advantages of the event based model and the native thread model. Can you tell I like it? :-) http://lua-users.org/files/wiki_insecure/users/MikePall/event.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zydeco.mat.ucsb.edu/pipermail/tdg/attachments/20070302/a4f1a01b/attachment.html From jcastellanos at umail.ucsb.edu Fri Mar 2 08:09:31 2007 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Fri Mar 2 08:09:45 2007 Subject: [Tdg] Code commit In-Reply-To: <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> Message-ID: <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> > If I can figure out my SVN client, I'll try and build an Xcode > project and add it. I've got it go work with SvnX. Using svn+ssh. For that to work you HAVE to configure password-less authentication (keygen...). j On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: If I can figure out my SVN client, I'll try and build an Xcode project and add it. On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > Ok.. It builds & runs.. The code base has been committed to > subversion repo. > > Heres what's there: > - New event stuff > - Minimal application & scheduler > - Placeholders for event queue, mem pool, etc. > - Core_easy as a separate library > - Example system library (graphics) > - Example app (test_app) > - Visual Studio solutions + projects > - lots of other stuff we discussed. > > The stuff is in the repository under: > \core\branch\mint > > The libs build a run in VS. I doubt it will build in gcc.. but > probably not far off. > > Rama > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg _______________________________________________ Tdg mailing list Tdg@mat.ucsb.edu http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From jcastellanos at umail.ucsb.edu Fri Mar 2 08:34:58 2007 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Fri Mar 2 08:35:14 2007 Subject: [Tdg] Code commit In-Reply-To: <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> Message-ID: Couple of questions: 1) I noticed a "mint.sln" file in the "mint" directory. Shouldn't it be inside the "make/visualstudio" folder? (I assume is a solution, right?) 2) What's the difference between the "output" and the "bin" directories? 3) I noticed a "test_app" directory inside source. Would it make sense to have a "Tests" folder (outside Source) where we have test apps and maybe unit tests, etc... ? > I'll try and build an Xcode project and add it. I'll also try to build it in XCode, but as a framework (as opposed to an app). j On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: If I can figure out my SVN client, I'll try and build an Xcode project and add it. On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > Ok.. It builds & runs.. The code base has been committed to > subversion repo. > > Heres what's there: > - New event stuff > - Minimal application & scheduler > - Placeholders for event queue, mem pool, etc. > - Core_easy as a separate library > - Example system library (graphics) > - Example app (test_app) > - Visual Studio solutions + projects > - lots of other stuff we discussed. > > The stuff is in the repository under: > \core\branch\mint > > The libs build a run in VS. I doubt it will build in gcc.. but > probably not far off. > > Rama > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg _______________________________________________ Tdg mailing list Tdg@mat.ucsb.edu http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From rch at umail.ucsb.edu Fri Mar 2 09:54:44 2007 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Fri Mar 2 09:55:01 2007 Subject: [Tdg] Code commit In-Reply-To: References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> Message-ID: <45E864E4.8020103@umail.ucsb.edu> > 1) I noticed a "mint.sln" file in the "mint" directory. Shouldn't it > be inside the "make/visualstudio" folder? (I assume is a solution, > right?) Possibly. I need to make sure VisualStudio doesn't complain. > 2) What's the difference between the "output" and the "bin" directories? Output is for obj, link and debug files (temporary). Bin is for .exe and .lib > 3) I noticed a "test_app" directory inside source. Would it make > sense to have a "Tests" folder (outside Source) where we have test > apps and maybe unit tests, etc... ? Graham suggested this too. Sounds good. (if you commit remember all folder names will be lower case with underscores between words) -rama From wakefield at mat.ucsb.edu Fri Mar 2 10:35:47 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 10:35:57 2007 Subject: [Tdg] Code commit In-Reply-To: <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> Message-ID: <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> For a svn newbie, could you step me through how you did this? Muchas Gracias! On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >> If I can figure out my SVN client, I'll try and build an Xcode >> project and add it. > > I've got it go work with SvnX. Using svn+ssh. For that to work you > HAVE to configure password-less authentication (keygen...). > > j > > On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: > > If I can figure out my SVN client, I'll try and build an Xcode > project and add it. > > On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > >> Ok.. It builds & runs.. The code base has been committed to >> subversion repo. >> >> Heres what's there: >> - New event stuff >> - Minimal application & scheduler >> - Placeholders for event queue, mem pool, etc. >> - Core_easy as a separate library >> - Example system library (graphics) >> - Example app (test_app) >> - Visual Studio solutions + projects >> - lots of other stuff we discussed. >> >> The stuff is in the repository under: >> \core\branch\mint >> >> The libs build a run in VS. I doubt it will build in gcc.. but >> probably not far off. >> >> Rama >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From jcastellanos at umail.ucsb.edu Fri Mar 2 11:49:10 2007 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Fri Mar 2 11:49:25 2007 Subject: [Tdg] Code commit In-Reply-To: <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> Message-ID: <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> Grahhhhhaaaaaammmm, Aqui va: 1) Configure ssh to authenticate using dsa keys... ? Create a folder named ".ssh" in your home directory (if it doesn't exist already) ? cd to the .ssh directory and type: "ssh-keygen -t dsa" ? it will ask for a paraphrase. Leave it blank (just press enter through the three prompts) ? Copy the public key "id_dsa_[ub" to the .ssh directory in your home directory of the remote machine (rails in this case) and rename the file in the remote machine to "authorized_keys". You can do these two steps using: "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/authorized_keys" * Note - Leaving the passphrase blank is not the most secure thing, but that's the way it has to be for xcode and svnx to work. As an alternative, you can use a key manager. I haven't use any, but you could skip all the above and the manager would do all that dynamically every time you connect. I think "SSHKeychain" does that nicely in OSX. Never tried it though. Now you should be able to ssh to your account in rails without entering any password. 2) Configure SvnX ? Open the "Repositories" window and create one. Fill the Path field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/tdg/svn/ ? Double click the repository, and check it out. This should add it to the "Working Copies" window. Now just use the working copy to commit, update, etc... if I forgot something, please fill in... j On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: For a svn newbie, could you step me through how you did this? Muchas Gracias! On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >> If I can figure out my SVN client, I'll try and build an Xcode >> project and add it. > > I've got it go work with SvnX. Using svn+ssh. For that to work you > HAVE to configure password-less authentication (keygen...). > > j > > On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: > > If I can figure out my SVN client, I'll try and build an Xcode > project and add it. > > On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > >> Ok.. It builds & runs.. The code base has been committed to >> subversion repo. >> >> Heres what's there: >> - New event stuff >> - Minimal application & scheduler >> - Placeholders for event queue, mem pool, etc. >> - Core_easy as a separate library >> - Example system library (graphics) >> - Example app (test_app) >> - Visual Studio solutions + projects >> - lots of other stuff we discussed. >> >> The stuff is in the repository under: >> \core\branch\mint >> >> The libs build a run in VS. I doubt it will build in gcc.. but >> probably not far off. >> >> Rama >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg _______________________________________________ Tdg mailing list Tdg@mat.ucsb.edu http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Fri Mar 2 16:04:20 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 16:04:45 2007 Subject: [Tdg] Code commit In-Reply-To: <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> Message-ID: <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> Hey Jorge - I'm stuck: g:~ grahamwakefield$ cd .ssh g:~/.ssh grahamwakefield$ ls id_rsa id_rsa.pub known_hosts g:~/.ssh grahamwakefield$ ssh-keygen -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/Users/grahamwakefield/.ssh/ id_dsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /Users/grahamwakefield/.ssh/ id_dsa. Your public key has been saved in /Users/grahamwakefield/.ssh/ id_dsa.pub. The key fingerprint is: 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 grahamwakefield@g.local g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys /Users/grahamwakefield/.ssh/authorized_keys: Not a directory ? On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: > Grahhhhhaaaaaammmm, > > Aqui va: > > 1) Configure ssh to authenticate using dsa keys... > > ? Create a folder named ".ssh" in your home directory (if it > doesn't exist already) > ? cd to the .ssh directory and type: "ssh-keygen -t dsa" > ? it will ask for a paraphrase. Leave it blank (just press enter > through the three prompts) > ? Copy the public key "id_dsa_[ub" to the .ssh directory in your > home directory of the remote machine (rails in this case) and > rename the file in the remote machine to "authorized_keys". You can > do these two steps using: > "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/authorized_keys" > > * Note - Leaving the passphrase blank is not the most secure thing, > but that's the way it has to be for xcode and svnx to work. As an > alternative, you can use a key manager. I haven't use any, but you > could skip all the above and the manager would do all that > dynamically every time you connect. I think "SSHKeychain" does that > nicely in OSX. Never tried it though. > > Now you should be able to ssh to your account in rails without > entering any password. > > 2) Configure SvnX > > ? Open the "Repositories" window and create one. Fill the Path > field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ > tdg/svn/ > ? Double click the repository, and check it out. This should add > it to the "Working Copies" window. Now just use the working copy to > commit, update, etc... > > if I forgot something, please fill in... > > j > > > > > > On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: > > For a svn newbie, could you step me through how you did this? > Muchas Gracias! > > On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: > >>> If I can figure out my SVN client, I'll try and build an Xcode >>> project and add it. >> >> I've got it go work with SvnX. Using svn+ssh. For that to work you >> HAVE to configure password-less authentication (keygen...). >> >> j >> >> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >> >> If I can figure out my SVN client, I'll try and build an Xcode >> project and add it. >> >> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >> >>> Ok.. It builds & runs.. The code base has been committed to >>> subversion repo. >>> >>> Heres what's there: >>> - New event stuff >>> - Minimal application & scheduler >>> - Placeholders for event queue, mem pool, etc. >>> - Core_easy as a separate library >>> - Example system library (graphics) >>> - Example app (test_app) >>> - Visual Studio solutions + projects >>> - lots of other stuff we discussed. >>> >>> The stuff is in the repository under: >>> \core\branch\mint >>> >>> The libs build a run in VS. I doubt it will build in gcc.. but >>> probably not far off. >>> >>> Rama >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From jcastellanos at umail.ucsb.edu Fri Mar 2 16:19:56 2007 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Fri Mar 2 16:20:11 2007 Subject: [Tdg] Code commit In-Reply-To: <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> Message-ID: You might have to create the .ssh directory in the home directory of the remote machine. After this, you should be able to ssh without a password. On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: Hey Jorge - I'm stuck: g:~ grahamwakefield$ cd .ssh g:~/.ssh grahamwakefield$ ls id_rsa id_rsa.pub known_hosts g:~/.ssh grahamwakefield$ ssh-keygen -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/Users/grahamwakefield/.ssh/ id_dsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /Users/grahamwakefield/.ssh/ id_dsa. Your public key has been saved in /Users/grahamwakefield/.ssh/ id_dsa.pub. The key fingerprint is: 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 grahamwakefield@g.local g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys /Users/grahamwakefield/.ssh/authorized_keys: Not a directory ? On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: > Grahhhhhaaaaaammmm, > > Aqui va: > > 1) Configure ssh to authenticate using dsa keys... > > ? Create a folder named ".ssh" in your home directory (if it > doesn't exist already) > ? cd to the .ssh directory and type: "ssh-keygen -t dsa" > ? it will ask for a paraphrase. Leave it blank (just press enter > through the three prompts) > ? Copy the public key "id_dsa_[ub" to the .ssh directory in your > home directory of the remote machine (rails in this case) and > rename the file in the remote machine to "authorized_keys". You can > do these two steps using: > "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/authorized_keys" > > * Note - Leaving the passphrase blank is not the most secure thing, > but that's the way it has to be for xcode and svnx to work. As an > alternative, you can use a key manager. I haven't use any, but you > could skip all the above and the manager would do all that > dynamically every time you connect. I think "SSHKeychain" does that > nicely in OSX. Never tried it though. > > Now you should be able to ssh to your account in rails without > entering any password. > > 2) Configure SvnX > > ? Open the "Repositories" window and create one. Fill the Path > field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ > tdg/svn/ > ? Double click the repository, and check it out. This should add > it to the "Working Copies" window. Now just use the working copy to > commit, update, etc... > > if I forgot something, please fill in... > > j > > > > > > On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: > > For a svn newbie, could you step me through how you did this? > Muchas Gracias! > > On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: > >>> If I can figure out my SVN client, I'll try and build an Xcode >>> project and add it. >> >> I've got it go work with SvnX. Using svn+ssh. For that to work you >> HAVE to configure password-less authentication (keygen...). >> >> j >> >> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >> >> If I can figure out my SVN client, I'll try and build an Xcode >> project and add it. >> >> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >> >>> Ok.. It builds & runs.. The code base has been committed to >>> subversion repo. >>> >>> Heres what's there: >>> - New event stuff >>> - Minimal application & scheduler >>> - Placeholders for event queue, mem pool, etc. >>> - Core_easy as a separate library >>> - Example system library (graphics) >>> - Example app (test_app) >>> - Visual Studio solutions + projects >>> - lots of other stuff we discussed. >>> >>> The stuff is in the repository under: >>> \core\branch\mint >>> >>> The libs build a run in VS. I doubt it will build in gcc.. but >>> probably not far off. >>> >>> Rama >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg _______________________________________________ Tdg mailing list Tdg@mat.ucsb.edu http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From alex at neisis.net Fri Mar 2 16:33:37 2007 From: alex at neisis.net (Alex Norman) Date: Fri Mar 2 16:33:47 2007 Subject: [Tdg] Code commit In-Reply-To: References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> Message-ID: <20070303003337.GV22044@silverninja.net> I think you have to put some file in ~/.ssh/authorized_keys on maize... I don't really know much about ssh keys though.. -Alex On 0, Jorge Castellanos wrote: > You might have to create the .ssh directory in the home directory of > the remote machine. > After this, you should be able to ssh without a password. > > > > > On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: > > Hey Jorge - > > I'm stuck: > > g:~ grahamwakefield$ cd .ssh > g:~/.ssh grahamwakefield$ ls > id_rsa id_rsa.pub known_hosts > g:~/.ssh grahamwakefield$ ssh-keygen -t dsa > Generating public/private dsa key pair. > Enter file in which to save the key (/Users/grahamwakefield/.ssh/ > id_dsa): > Enter passphrase (empty for no passphrase): > Enter same passphrase again: > Your identification has been saved in /Users/grahamwakefield/.ssh/ > id_dsa. > Your public key has been saved in /Users/grahamwakefield/.ssh/ > id_dsa.pub. > The key fingerprint is: > 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 grahamwakefield@g.local > g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub > wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys > /Users/grahamwakefield/.ssh/authorized_keys: Not a directory > > ? > > On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: > > >Grahhhhhaaaaaammmm, > > > >Aqui va: > > > >1) Configure ssh to authenticate using dsa keys... > > > > ? Create a folder named ".ssh" in your home directory (if it > >doesn't exist already) > > ? cd to the .ssh directory and type: "ssh-keygen -t dsa" > > ? it will ask for a paraphrase. Leave it blank (just press enter > >through the three prompts) > > ? Copy the public key "id_dsa_[ub" to the .ssh directory in your > >home directory of the remote machine (rails in this case) and > >rename the file in the remote machine to "authorized_keys". You can > >do these two steps using: > > "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/authorized_keys" > > > >* Note - Leaving the passphrase blank is not the most secure thing, > >but that's the way it has to be for xcode and svnx to work. As an > >alternative, you can use a key manager. I haven't use any, but you > >could skip all the above and the manager would do all that > >dynamically every time you connect. I think "SSHKeychain" does that > >nicely in OSX. Never tried it though. > > > >Now you should be able to ssh to your account in rails without > >entering any password. > > > >2) Configure SvnX > > > > ? Open the "Repositories" window and create one. Fill the Path > >field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ > >tdg/svn/ > > ? Double click the repository, and check it out. This should add > >it to the "Working Copies" window. Now just use the working copy to > >commit, update, etc... > > > >if I forgot something, please fill in... > > > >j > > > > > > > > > > > >On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: > > > >For a svn newbie, could you step me through how you did this? > >Muchas Gracias! > > > >On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: > > > >>>If I can figure out my SVN client, I'll try and build an Xcode > >>>project and add it. > >> > >>I've got it go work with SvnX. Using svn+ssh. For that to work you > >>HAVE to configure password-less authentication (keygen...). > >> > >>j > >> > >>On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: > >> > >>If I can figure out my SVN client, I'll try and build an Xcode > >>project and add it. > >> > >>On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > >> > >>>Ok.. It builds & runs.. The code base has been committed to > >>>subversion repo. > >>> > >>>Heres what's there: > >>>- New event stuff > >>>- Minimal application & scheduler > >>>- Placeholders for event queue, mem pool, etc. > >>>- Core_easy as a separate library > >>>- Example system library (graphics) > >>>- Example app (test_app) > >>>- Visual Studio solutions + projects > >>>- lots of other stuff we discussed. > >>> > >>>The stuff is in the repository under: > >>> \core\branch\mint > >>> > >>>The libs build a run in VS. I doubt it will build in gcc.. but > >>>probably not far off. > >>> > >>>Rama > >>> > >>>_______________________________________________ > >>>Tdg mailing list > >>>Tdg@mat.ucsb.edu > >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > >>_______________________________________________ > >>Tdg mailing list > >>Tdg@mat.ucsb.edu > >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > >>_______________________________________________ > >>Tdg mailing list > >>Tdg@mat.ucsb.edu > >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > >_______________________________________________ > >Tdg mailing list > >Tdg@mat.ucsb.edu > >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > >_______________________________________________ > >Tdg mailing list > >Tdg@mat.ucsb.edu > >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From jcastellanos at umail.ucsb.edu Fri Mar 2 16:39:28 2007 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Fri Mar 2 16:39:43 2007 Subject: [Tdg] Code commit In-Reply-To: <20070303003337.GV22044@silverninja.net> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> Message-ID: <475258BD-CE3B-45D2-8A00-FBEBB0BFDCB2@umail.ucsb.edu> > I think you have to put some file in ~/.ssh/authorized_keys on > maize... "authorized_keys" is not a directory. Is the new name for the file being copied. You are basically copying and renaming id_rsa.pub hope it works j On Mar 2, 2007, at 7:33 PM, Alex Norman wrote: I think you have to put some file in ~/.ssh/authorized_keys on maize... I don't really know much about ssh keys though.. -Alex On 0, Jorge Castellanos wrote: > You might have to create the .ssh directory in the home directory of > the remote machine. > After this, you should be able to ssh without a password. > > > > > On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: > > Hey Jorge - > > I'm stuck: > > g:~ grahamwakefield$ cd .ssh > g:~/.ssh grahamwakefield$ ls > id_rsa id_rsa.pub known_hosts > g:~/.ssh grahamwakefield$ ssh-keygen -t dsa > Generating public/private dsa key pair. > Enter file in which to save the key (/Users/grahamwakefield/.ssh/ > id_dsa): > Enter passphrase (empty for no passphrase): > Enter same passphrase again: > Your identification has been saved in /Users/grahamwakefield/.ssh/ > id_dsa. > Your public key has been saved in /Users/grahamwakefield/.ssh/ > id_dsa.pub. > The key fingerprint is: > 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 > grahamwakefield@g.local > g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub > wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys > /Users/grahamwakefield/.ssh/authorized_keys: Not a directory > > ? > > On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: > >> Grahhhhhaaaaaammmm, >> >> Aqui va: >> >> 1) Configure ssh to authenticate using dsa keys... >> >> ? Create a folder named ".ssh" in your home directory (if it >> doesn't exist already) >> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" >> ? it will ask for a paraphrase. Leave it blank (just press enter >> through the three prompts) >> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your >> home directory of the remote machine (rails in this case) and >> rename the file in the remote machine to "authorized_keys". You can >> do these two steps using: >> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ >> authorized_keys" >> >> * Note - Leaving the passphrase blank is not the most secure thing, >> but that's the way it has to be for xcode and svnx to work. As an >> alternative, you can use a key manager. I haven't use any, but you >> could skip all the above and the manager would do all that >> dynamically every time you connect. I think "SSHKeychain" does that >> nicely in OSX. Never tried it though. >> >> Now you should be able to ssh to your account in rails without >> entering any password. >> >> 2) Configure SvnX >> >> ? Open the "Repositories" window and create one. Fill the Path >> field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ >> tdg/svn/ >> ? Double click the repository, and check it out. This should add >> it to the "Working Copies" window. Now just use the working copy to >> commit, update, etc... >> >> if I forgot something, please fill in... >> >> j >> >> >> >> >> >> On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: >> >> For a svn newbie, could you step me through how you did this? >> Muchas Gracias! >> >> On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >> >>>> If I can figure out my SVN client, I'll try and build an Xcode >>>> project and add it. >>> >>> I've got it go work with SvnX. Using svn+ssh. For that to work you >>> HAVE to configure password-less authentication (keygen...). >>> >>> j >>> >>> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >>> >>> If I can figure out my SVN client, I'll try and build an Xcode >>> project and add it. >>> >>> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >>> >>>> Ok.. It builds & runs.. The code base has been committed to >>>> subversion repo. >>>> >>>> Heres what's there: >>>> - New event stuff >>>> - Minimal application & scheduler >>>> - Placeholders for event queue, mem pool, etc. >>>> - Core_easy as a separate library >>>> - Example system library (graphics) >>>> - Example app (test_app) >>>> - Visual Studio solutions + projects >>>> - lots of other stuff we discussed. >>>> >>>> The stuff is in the repository under: >>>> \core\branch\mint >>>> >>>> The libs build a run in VS. I doubt it will build in gcc.. but >>>> probably not far off. >>>> >>>> Rama >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg _______________________________________________ Tdg mailing list Tdg@mat.ucsb.edu http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Fri Mar 2 16:47:33 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 16:47:45 2007 Subject: [Tdg] Code commit In-Reply-To: References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> Message-ID: actually, it looks like it is complaining about authorized_keys is a file, not a directory, in my home dir on my own machine i removed the file and replaced it with a directory but then scp didn't work is it supposed to be a file or a directory? does scp need some kind of flag to make this work? Sorry, I'm not experienced in console/ unix stuff Here's the terminal session: g:~ grahamwakefield$ cd .ssh g:~/.ssh grahamwakefield$ ls id_rsa id_rsa.pub known_hosts g:~/.ssh grahamwakefield$ ssh-keygen -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/Users/grahamwakefield/.ssh/ id_dsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /Users/grahamwakefield/.ssh/ id_dsa. Your public key has been saved in /Users/grahamwakefield/.ssh/ id_dsa.pub. The key fingerprint is: 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 grahamwakefield@g.local g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys /Users/grahamwakefield/.ssh/authorized_keys: Not a directory g:~/.ssh grahamwakefield$ ls authorized_keys id_dsa.pub id_rsa.pub id_dsa id_rsa known_hosts g:~/.ssh grahamwakefield$ cd authorized_keys -bash: cd: authorized_keys: Not a directory g:~/.ssh grahamwakefield$ rm authorized_keys g:~/.ssh grahamwakefield$ ls id_dsa id_dsa.pub id_rsa id_rsa.pub known_hosts g:~/.ssh grahamwakefield$ mkdir authorized_keys g:~/.ssh grahamwakefield$ ls authorized_keys id_dsa.pub id_rsa.pub id_dsa id_rsa known_hosts g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub wakefield@mat.ucsb.edu: ~/.ssh/authorized_keys The authenticity of host 'mat.ucsb.edu (128.111.92.3)' can't be established. RSA key fingerprint is 51:41:15:67:75:99:e3:96:68:44:f3:91:5a:bd:53:ff. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'mat.ucsb.edu' (RSA) to the list of known hosts. wakefield@mat.ucsb.edu's password: scp: .: not a regular file On Mar 2, 2007, at 4:19 PM, Jorge Castellanos wrote: > You might have to create the .ssh directory in the home directory > of the remote machine. > After this, you should be able to ssh without a password. > > > > > On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: > > Hey Jorge - > > I'm stuck: > > g:~ grahamwakefield$ cd .ssh > g:~/.ssh grahamwakefield$ ls > id_rsa id_rsa.pub known_hosts > g:~/.ssh grahamwakefield$ ssh-keygen -t dsa > Generating public/private dsa key pair. > Enter file in which to save the key (/Users/grahamwakefield/.ssh/ > id_dsa): > Enter passphrase (empty for no passphrase): > Enter same passphrase again: > Your identification has been saved in /Users/grahamwakefield/.ssh/ > id_dsa. > Your public key has been saved in /Users/grahamwakefield/.ssh/ > id_dsa.pub. > The key fingerprint is: > 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 > grahamwakefield@g.local > g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub > wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys > /Users/grahamwakefield/.ssh/authorized_keys: Not a directory > > ? > > On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: > >> Grahhhhhaaaaaammmm, >> >> Aqui va: >> >> 1) Configure ssh to authenticate using dsa keys... >> >> ? Create a folder named ".ssh" in your home directory (if it >> doesn't exist already) >> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" >> ? it will ask for a paraphrase. Leave it blank (just press enter >> through the three prompts) >> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your >> home directory of the remote machine (rails in this case) and >> rename the file in the remote machine to "authorized_keys". You >> can do these two steps using: >> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ >> authorized_keys" >> >> * Note - Leaving the passphrase blank is not the most secure >> thing, but that's the way it has to be for xcode and svnx to work. >> As an alternative, you can use a key manager. I haven't use any, >> but you could skip all the above and the manager would do all that >> dynamically every time you connect. I think "SSHKeychain" does >> that nicely in OSX. Never tried it though. >> >> Now you should be able to ssh to your account in rails without >> entering any password. >> >> 2) Configure SvnX >> >> ? Open the "Repositories" window and create one. Fill the Path >> field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ >> tdg/svn/ >> ? Double click the repository, and check it out. This should add >> it to the "Working Copies" window. Now just use the working copy >> to commit, update, etc... >> >> if I forgot something, please fill in... >> >> j >> >> >> >> >> >> On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: >> >> For a svn newbie, could you step me through how you did this? >> Muchas Gracias! >> >> On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >> >>>> If I can figure out my SVN client, I'll try and build an Xcode >>>> project and add it. >>> >>> I've got it go work with SvnX. Using svn+ssh. For that to work >>> you HAVE to configure password-less authentication (keygen...). >>> >>> j >>> >>> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >>> >>> If I can figure out my SVN client, I'll try and build an Xcode >>> project and add it. >>> >>> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >>> >>>> Ok.. It builds & runs.. The code base has been committed to >>>> subversion repo. >>>> >>>> Heres what's there: >>>> - New event stuff >>>> - Minimal application & scheduler >>>> - Placeholders for event queue, mem pool, etc. >>>> - Core_easy as a separate library >>>> - Example system library (graphics) >>>> - Example app (test_app) >>>> - Visual Studio solutions + projects >>>> - lots of other stuff we discussed. >>>> >>>> The stuff is in the repository under: >>>> \core\branch\mint >>>> >>>> The libs build a run in VS. I doubt it will build in gcc.. but >>>> probably not far off. >>>> >>>> Rama >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From alex at neisis.net Fri Mar 2 16:49:36 2007 From: alex at neisis.net (Alex Norman) Date: Fri Mar 2 16:49:44 2007 Subject: [Tdg] Code commit In-Reply-To: References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> Message-ID: <20070303004936.GW22044@silverninja.net> use scp -r to send directories [recursively]. -ale On 0, Graham Wakefield wrote: > actually, it looks like it is complaining about authorized_keys is a > file, not a directory, in my home dir on my own machine > > i removed the file and replaced it with a directory > > but then scp didn't work > > is it supposed to be a file or a directory? does scp need some kind > of flag to make this work? Sorry, I'm not experienced in console/ > unix stuff > > Here's the terminal session: > > g:~ grahamwakefield$ cd .ssh > g:~/.ssh grahamwakefield$ ls > id_rsa id_rsa.pub known_hosts > g:~/.ssh grahamwakefield$ ssh-keygen -t dsa > Generating public/private dsa key pair. > Enter file in which to save the key (/Users/grahamwakefield/.ssh/ > id_dsa): > Enter passphrase (empty for no passphrase): > Enter same passphrase again: > Your identification has been saved in /Users/grahamwakefield/.ssh/ > id_dsa. > Your public key has been saved in /Users/grahamwakefield/.ssh/ > id_dsa.pub. > The key fingerprint is: > 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 grahamwakefield@g.local > g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub > wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys > /Users/grahamwakefield/.ssh/authorized_keys: Not a directory > g:~/.ssh grahamwakefield$ ls > authorized_keys id_dsa.pub id_rsa.pub > id_dsa id_rsa known_hosts > g:~/.ssh grahamwakefield$ cd authorized_keys > -bash: cd: authorized_keys: Not a directory > g:~/.ssh grahamwakefield$ rm authorized_keys > g:~/.ssh grahamwakefield$ ls > id_dsa id_dsa.pub id_rsa id_rsa.pub > known_hosts > g:~/.ssh grahamwakefield$ mkdir authorized_keys > g:~/.ssh grahamwakefield$ ls > authorized_keys id_dsa.pub id_rsa.pub > id_dsa id_rsa known_hosts > g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub > wakefield@mat.ucsb.edu: ~/.ssh/authorized_keys > The authenticity of host 'mat.ucsb.edu (128.111.92.3)' can't be > established. > RSA key fingerprint is 51:41:15:67:75:99:e3:96:68:44:f3:91:5a:bd:53:ff. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'mat.ucsb.edu' (RSA) to the list of known > hosts. > wakefield@mat.ucsb.edu's password: > scp: .: not a regular file > > > On Mar 2, 2007, at 4:19 PM, Jorge Castellanos wrote: > > >You might have to create the .ssh directory in the home directory > >of the remote machine. > >After this, you should be able to ssh without a password. > > > > > > > > > >On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: > > > >Hey Jorge - > > > >I'm stuck: > > > >g:~ grahamwakefield$ cd .ssh > >g:~/.ssh grahamwakefield$ ls > >id_rsa id_rsa.pub known_hosts > >g:~/.ssh grahamwakefield$ ssh-keygen -t dsa > >Generating public/private dsa key pair. > >Enter file in which to save the key (/Users/grahamwakefield/.ssh/ > >id_dsa): > >Enter passphrase (empty for no passphrase): > >Enter same passphrase again: > >Your identification has been saved in /Users/grahamwakefield/.ssh/ > >id_dsa. > >Your public key has been saved in /Users/grahamwakefield/.ssh/ > >id_dsa.pub. > >The key fingerprint is: > >27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 > >grahamwakefield@g.local > >g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub > >wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys > >/Users/grahamwakefield/.ssh/authorized_keys: Not a directory > > > >? > > > >On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: > > > >>Grahhhhhaaaaaammmm, > >> > >>Aqui va: > >> > >>1) Configure ssh to authenticate using dsa keys... > >> > >> ? Create a folder named ".ssh" in your home directory (if it > >>doesn't exist already) > >> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" > >> ? it will ask for a paraphrase. Leave it blank (just press enter > >>through the three prompts) > >> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your > >>home directory of the remote machine (rails in this case) and > >>rename the file in the remote machine to "authorized_keys". You > >>can do these two steps using: > >> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ > >>authorized_keys" > >> > >>* Note - Leaving the passphrase blank is not the most secure > >>thing, but that's the way it has to be for xcode and svnx to work. > >>As an alternative, you can use a key manager. I haven't use any, > >>but you could skip all the above and the manager would do all that > >>dynamically every time you connect. I think "SSHKeychain" does > >>that nicely in OSX. Never tried it though. > >> > >>Now you should be able to ssh to your account in rails without > >>entering any password. > >> > >>2) Configure SvnX > >> > >> ? Open the "Repositories" window and create one. Fill the Path > >>field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ > >>tdg/svn/ > >> ? Double click the repository, and check it out. This should add > >>it to the "Working Copies" window. Now just use the working copy > >>to commit, update, etc... > >> > >>if I forgot something, please fill in... > >> > >>j > >> > >> > >> > >> > >> > >>On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: > >> > >>For a svn newbie, could you step me through how you did this? > >>Muchas Gracias! > >> > >>On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: > >> > >>>>If I can figure out my SVN client, I'll try and build an Xcode > >>>>project and add it. > >>> > >>>I've got it go work with SvnX. Using svn+ssh. For that to work > >>>you HAVE to configure password-less authentication (keygen...). > >>> > >>>j > >>> > >>>On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: > >>> > >>>If I can figure out my SVN client, I'll try and build an Xcode > >>>project and add it. > >>> > >>>On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > >>> > >>>>Ok.. It builds & runs.. The code base has been committed to > >>>>subversion repo. > >>>> > >>>>Heres what's there: > >>>>- New event stuff > >>>>- Minimal application & scheduler > >>>>- Placeholders for event queue, mem pool, etc. > >>>>- Core_easy as a separate library > >>>>- Example system library (graphics) > >>>>- Example app (test_app) > >>>>- Visual Studio solutions + projects > >>>>- lots of other stuff we discussed. > >>>> > >>>>The stuff is in the repository under: > >>>> \core\branch\mint > >>>> > >>>>The libs build a run in VS. I doubt it will build in gcc.. but > >>>>probably not far off. > >>>> > >>>>Rama > >>>> > >>>>_______________________________________________ > >>>>Tdg mailing list > >>>>Tdg@mat.ucsb.edu > >>>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>> > >>>_______________________________________________ > >>>Tdg mailing list > >>>Tdg@mat.ucsb.edu > >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>> > >>>_______________________________________________ > >>>Tdg mailing list > >>>Tdg@mat.ucsb.edu > >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > >>_______________________________________________ > >>Tdg mailing list > >>Tdg@mat.ucsb.edu > >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > >>_______________________________________________ > >>Tdg mailing list > >>Tdg@mat.ucsb.edu > >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > >_______________________________________________ > >Tdg mailing list > >Tdg@mat.ucsb.edu > >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > >_______________________________________________ > >Tdg mailing list > >Tdg@mat.ucsb.edu > >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Fri Mar 2 16:50:12 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 16:50:21 2007 Subject: [Tdg] Code commit In-Reply-To: <20070303003337.GV22044@silverninja.net> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> Message-ID: Are we using maize or rails? On Mar 2, 2007, at 4:33 PM, Alex Norman wrote: > I think you have to put some file in ~/.ssh/authorized_keys on > maize... > I don't really know much about ssh keys though.. > -Alex > > On 0, Jorge Castellanos wrote: >> You might have to create the .ssh directory in the home directory of >> the remote machine. >> After this, you should be able to ssh without a password. >> >> >> >> >> On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: >> >> Hey Jorge - >> >> I'm stuck: >> >> g:~ grahamwakefield$ cd .ssh >> g:~/.ssh grahamwakefield$ ls >> id_rsa id_rsa.pub known_hosts >> g:~/.ssh grahamwakefield$ ssh-keygen -t dsa >> Generating public/private dsa key pair. >> Enter file in which to save the key (/Users/grahamwakefield/.ssh/ >> id_dsa): >> Enter passphrase (empty for no passphrase): >> Enter same passphrase again: >> Your identification has been saved in /Users/grahamwakefield/.ssh/ >> id_dsa. >> Your public key has been saved in /Users/grahamwakefield/.ssh/ >> id_dsa.pub. >> The key fingerprint is: >> 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 >> grahamwakefield@g.local >> g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub >> wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys >> /Users/grahamwakefield/.ssh/authorized_keys: Not a directory >> >> ? >> >> On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: >> >>> Grahhhhhaaaaaammmm, >>> >>> Aqui va: >>> >>> 1) Configure ssh to authenticate using dsa keys... >>> >>> ? Create a folder named ".ssh" in your home directory (if it >>> doesn't exist already) >>> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" >>> ? it will ask for a paraphrase. Leave it blank (just press enter >>> through the three prompts) >>> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your >>> home directory of the remote machine (rails in this case) and >>> rename the file in the remote machine to "authorized_keys". You can >>> do these two steps using: >>> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ >>> authorized_keys" >>> >>> * Note - Leaving the passphrase blank is not the most secure thing, >>> but that's the way it has to be for xcode and svnx to work. As an >>> alternative, you can use a key manager. I haven't use any, but you >>> could skip all the above and the manager would do all that >>> dynamically every time you connect. I think "SSHKeychain" does that >>> nicely in OSX. Never tried it though. >>> >>> Now you should be able to ssh to your account in rails without >>> entering any password. >>> >>> 2) Configure SvnX >>> >>> ? Open the "Repositories" window and create one. Fill the Path >>> field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ >>> tdg/svn/ >>> ? Double click the repository, and check it out. This should add >>> it to the "Working Copies" window. Now just use the working copy to >>> commit, update, etc... >>> >>> if I forgot something, please fill in... >>> >>> j >>> >>> >>> >>> >>> >>> On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: >>> >>> For a svn newbie, could you step me through how you did this? >>> Muchas Gracias! >>> >>> On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >>> >>>>> If I can figure out my SVN client, I'll try and build an Xcode >>>>> project and add it. >>>> >>>> I've got it go work with SvnX. Using svn+ssh. For that to work you >>>> HAVE to configure password-less authentication (keygen...). >>>> >>>> j >>>> >>>> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >>>> >>>> If I can figure out my SVN client, I'll try and build an Xcode >>>> project and add it. >>>> >>>> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >>>> >>>>> Ok.. It builds & runs.. The code base has been committed to >>>>> subversion repo. >>>>> >>>>> Heres what's there: >>>>> - New event stuff >>>>> - Minimal application & scheduler >>>>> - Placeholders for event queue, mem pool, etc. >>>>> - Core_easy as a separate library >>>>> - Example system library (graphics) >>>>> - Example app (test_app) >>>>> - Visual Studio solutions + projects >>>>> - lots of other stuff we discussed. >>>>> >>>>> The stuff is in the repository under: >>>>> \core\branch\mint >>>>> >>>>> The libs build a run in VS. I doubt it will build in gcc.. but >>>>> probably not far off. >>>>> >>>>> Rama >>>>> >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From alex at neisis.net Fri Mar 2 16:52:49 2007 From: alex at neisis.net (Alex Norman) Date: Fri Mar 2 16:52:56 2007 Subject: [Tdg] Code commit In-Reply-To: References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> Message-ID: <20070303005249.GX22044@silverninja.net> they are the same machine. I'm not sure if you can ssh to maize yet but you can ssh to rails, they are just different network adapters for the same box. so I just use "rails" -Alex On 0, Graham Wakefield wrote: > Are we using maize or rails? > > On Mar 2, 2007, at 4:33 PM, Alex Norman wrote: > > >I think you have to put some file in ~/.ssh/authorized_keys on > >maize... > >I don't really know much about ssh keys though.. > >-Alex > > > >On 0, Jorge Castellanos wrote: > >>You might have to create the .ssh directory in the home directory of > >>the remote machine. > >>After this, you should be able to ssh without a password. > >> > >> > >> > >> > >>On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: > >> > >>Hey Jorge - > >> > >>I'm stuck: > >> > >>g:~ grahamwakefield$ cd .ssh > >>g:~/.ssh grahamwakefield$ ls > >>id_rsa id_rsa.pub known_hosts > >>g:~/.ssh grahamwakefield$ ssh-keygen -t dsa > >>Generating public/private dsa key pair. > >>Enter file in which to save the key (/Users/grahamwakefield/.ssh/ > >>id_dsa): > >>Enter passphrase (empty for no passphrase): > >>Enter same passphrase again: > >>Your identification has been saved in /Users/grahamwakefield/.ssh/ > >>id_dsa. > >>Your public key has been saved in /Users/grahamwakefield/.ssh/ > >>id_dsa.pub. > >>The key fingerprint is: > >>27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 > >>grahamwakefield@g.local > >>g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub > >>wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys > >>/Users/grahamwakefield/.ssh/authorized_keys: Not a directory > >> > >>? > >> > >>On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: > >> > >>>Grahhhhhaaaaaammmm, > >>> > >>>Aqui va: > >>> > >>>1) Configure ssh to authenticate using dsa keys... > >>> > >>> ? Create a folder named ".ssh" in your home directory (if it > >>>doesn't exist already) > >>> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" > >>> ? it will ask for a paraphrase. Leave it blank (just press enter > >>>through the three prompts) > >>> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your > >>>home directory of the remote machine (rails in this case) and > >>>rename the file in the remote machine to "authorized_keys". You can > >>>do these two steps using: > >>> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ > >>>authorized_keys" > >>> > >>>* Note - Leaving the passphrase blank is not the most secure thing, > >>>but that's the way it has to be for xcode and svnx to work. As an > >>>alternative, you can use a key manager. I haven't use any, but you > >>>could skip all the above and the manager would do all that > >>>dynamically every time you connect. I think "SSHKeychain" does that > >>>nicely in OSX. Never tried it though. > >>> > >>>Now you should be able to ssh to your account in rails without > >>>entering any password. > >>> > >>>2) Configure SvnX > >>> > >>> ? Open the "Repositories" window and create one. Fill the Path > >>>field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ > >>>tdg/svn/ > >>> ? Double click the repository, and check it out. This should add > >>>it to the "Working Copies" window. Now just use the working copy to > >>>commit, update, etc... > >>> > >>>if I forgot something, please fill in... > >>> > >>>j > >>> > >>> > >>> > >>> > >>> > >>>On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: > >>> > >>>For a svn newbie, could you step me through how you did this? > >>>Muchas Gracias! > >>> > >>>On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: > >>> > >>>>>If I can figure out my SVN client, I'll try and build an Xcode > >>>>>project and add it. > >>>> > >>>>I've got it go work with SvnX. Using svn+ssh. For that to work you > >>>>HAVE to configure password-less authentication (keygen...). > >>>> > >>>>j > >>>> > >>>>On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: > >>>> > >>>>If I can figure out my SVN client, I'll try and build an Xcode > >>>>project and add it. > >>>> > >>>>On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > >>>> > >>>>>Ok.. It builds & runs.. The code base has been committed to > >>>>>subversion repo. > >>>>> > >>>>>Heres what's there: > >>>>>- New event stuff > >>>>>- Minimal application & scheduler > >>>>>- Placeholders for event queue, mem pool, etc. > >>>>>- Core_easy as a separate library > >>>>>- Example system library (graphics) > >>>>>- Example app (test_app) > >>>>>- Visual Studio solutions + projects > >>>>>- lots of other stuff we discussed. > >>>>> > >>>>>The stuff is in the repository under: > >>>>>\core\branch\mint > >>>>> > >>>>>The libs build a run in VS. I doubt it will build in gcc.. but > >>>>>probably not far off. > >>>>> > >>>>>Rama > >>>>> > >>>>>_______________________________________________ > >>>>>Tdg mailing list > >>>>>Tdg@mat.ucsb.edu > >>>>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>>> > >>>>_______________________________________________ > >>>>Tdg mailing list > >>>>Tdg@mat.ucsb.edu > >>>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>>> > >>>>_______________________________________________ > >>>>Tdg mailing list > >>>>Tdg@mat.ucsb.edu > >>>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>> > >>>_______________________________________________ > >>>Tdg mailing list > >>>Tdg@mat.ucsb.edu > >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>> > >>>_______________________________________________ > >>>Tdg mailing list > >>>Tdg@mat.ucsb.edu > >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > >>_______________________________________________ > >>Tdg mailing list > >>Tdg@mat.ucsb.edu > >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > >>_______________________________________________ > >>Tdg mailing list > >>Tdg@mat.ucsb.edu > >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >_______________________________________________ > >Tdg mailing list > >Tdg@mat.ucsb.edu > >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Fri Mar 2 16:52:54 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 16:53:03 2007 Subject: [Tdg] Code commit In-Reply-To: <20070303003337.GV22044@silverninja.net> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> Message-ID: <5F575B0D-CFB4-4E81-A6CD-C499C230C372@mat.ucsb.edu> I already have a .ssh in maize: g:~ grahamwakefield$ ssh wakefield@maize.mat.ucsb.edu Password: Last login: Tue Jan 30 11:52:16 2007 from freeip88.mat.ucsb.edu wakefield@maize ~ $ cd .ssh wakefield@maize ~/.ssh $ ls authorized_keys id_dsa id_dsa.pub If I ssh to rails.mat.ucsb.edu, I end up on maize anyway. I didn't realize they are the same server. On Mar 2, 2007, at 4:33 PM, Alex Norman wrote: > I think you have to put some file in ~/.ssh/authorized_keys on > maize... > I don't really know much about ssh keys though.. > -Alex > > On 0, Jorge Castellanos wrote: >> You might have to create the .ssh directory in the home directory of >> the remote machine. >> After this, you should be able to ssh without a password. >> >> >> >> >> On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: >> >> Hey Jorge - >> >> I'm stuck: >> >> g:~ grahamwakefield$ cd .ssh >> g:~/.ssh grahamwakefield$ ls >> id_rsa id_rsa.pub known_hosts >> g:~/.ssh grahamwakefield$ ssh-keygen -t dsa >> Generating public/private dsa key pair. >> Enter file in which to save the key (/Users/grahamwakefield/.ssh/ >> id_dsa): >> Enter passphrase (empty for no passphrase): >> Enter same passphrase again: >> Your identification has been saved in /Users/grahamwakefield/.ssh/ >> id_dsa. >> Your public key has been saved in /Users/grahamwakefield/.ssh/ >> id_dsa.pub. >> The key fingerprint is: >> 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 >> grahamwakefield@g.local >> g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub >> wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys >> /Users/grahamwakefield/.ssh/authorized_keys: Not a directory >> >> ? >> >> On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: >> >>> Grahhhhhaaaaaammmm, >>> >>> Aqui va: >>> >>> 1) Configure ssh to authenticate using dsa keys... >>> >>> ? Create a folder named ".ssh" in your home directory (if it >>> doesn't exist already) >>> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" >>> ? it will ask for a paraphrase. Leave it blank (just press enter >>> through the three prompts) >>> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your >>> home directory of the remote machine (rails in this case) and >>> rename the file in the remote machine to "authorized_keys". You can >>> do these two steps using: >>> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ >>> authorized_keys" >>> >>> * Note - Leaving the passphrase blank is not the most secure thing, >>> but that's the way it has to be for xcode and svnx to work. As an >>> alternative, you can use a key manager. I haven't use any, but you >>> could skip all the above and the manager would do all that >>> dynamically every time you connect. I think "SSHKeychain" does that >>> nicely in OSX. Never tried it though. >>> >>> Now you should be able to ssh to your account in rails without >>> entering any password. >>> >>> 2) Configure SvnX >>> >>> ? Open the "Repositories" window and create one. Fill the Path >>> field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ >>> tdg/svn/ >>> ? Double click the repository, and check it out. This should add >>> it to the "Working Copies" window. Now just use the working copy to >>> commit, update, etc... >>> >>> if I forgot something, please fill in... >>> >>> j >>> >>> >>> >>> >>> >>> On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: >>> >>> For a svn newbie, could you step me through how you did this? >>> Muchas Gracias! >>> >>> On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >>> >>>>> If I can figure out my SVN client, I'll try and build an Xcode >>>>> project and add it. >>>> >>>> I've got it go work with SvnX. Using svn+ssh. For that to work you >>>> HAVE to configure password-less authentication (keygen...). >>>> >>>> j >>>> >>>> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >>>> >>>> If I can figure out my SVN client, I'll try and build an Xcode >>>> project and add it. >>>> >>>> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >>>> >>>>> Ok.. It builds & runs.. The code base has been committed to >>>>> subversion repo. >>>>> >>>>> Heres what's there: >>>>> - New event stuff >>>>> - Minimal application & scheduler >>>>> - Placeholders for event queue, mem pool, etc. >>>>> - Core_easy as a separate library >>>>> - Example system library (graphics) >>>>> - Example app (test_app) >>>>> - Visual Studio solutions + projects >>>>> - lots of other stuff we discussed. >>>>> >>>>> The stuff is in the repository under: >>>>> \core\branch\mint >>>>> >>>>> The libs build a run in VS. I doubt it will build in gcc.. but >>>>> probably not far off. >>>>> >>>>> Rama >>>>> >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From alex at neisis.net Fri Mar 2 16:57:10 2007 From: alex at neisis.net (Alex Norman) Date: Fri Mar 2 16:57:17 2007 Subject: [Tdg] Code commit In-Reply-To: <5F575B0D-CFB4-4E81-A6CD-C499C230C372@mat.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> <5F575B0D-CFB4-4E81-A6CD-C499C230C372@mat.ucsb.edu> Message-ID: <20070303005710.GY22044@silverninja.net> you could just use the app "svn" from the command line for now, it isn't retarded. -Alex On 0, Graham Wakefield wrote: > I already have a .ssh in maize: > > > g:~ grahamwakefield$ ssh wakefield@maize.mat.ucsb.edu > Password: > Last login: Tue Jan 30 11:52:16 2007 from freeip88.mat.ucsb.edu > wakefield@maize ~ $ cd .ssh > wakefield@maize ~/.ssh $ ls > authorized_keys id_dsa id_dsa.pub > > If I ssh to rails.mat.ucsb.edu, I end up on maize anyway. I didn't > realize they are the same server. > > > > > On Mar 2, 2007, at 4:33 PM, Alex Norman wrote: > > >I think you have to put some file in ~/.ssh/authorized_keys on > >maize... > >I don't really know much about ssh keys though.. > >-Alex > > > >On 0, Jorge Castellanos wrote: > >>You might have to create the .ssh directory in the home directory of > >>the remote machine. > >>After this, you should be able to ssh without a password. > >> > >> > >> > >> > >>On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: > >> > >>Hey Jorge - > >> > >>I'm stuck: > >> > >>g:~ grahamwakefield$ cd .ssh > >>g:~/.ssh grahamwakefield$ ls > >>id_rsa id_rsa.pub known_hosts > >>g:~/.ssh grahamwakefield$ ssh-keygen -t dsa > >>Generating public/private dsa key pair. > >>Enter file in which to save the key (/Users/grahamwakefield/.ssh/ > >>id_dsa): > >>Enter passphrase (empty for no passphrase): > >>Enter same passphrase again: > >>Your identification has been saved in /Users/grahamwakefield/.ssh/ > >>id_dsa. > >>Your public key has been saved in /Users/grahamwakefield/.ssh/ > >>id_dsa.pub. > >>The key fingerprint is: > >>27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 > >>grahamwakefield@g.local > >>g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub > >>wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys > >>/Users/grahamwakefield/.ssh/authorized_keys: Not a directory > >> > >>? > >> > >>On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: > >> > >>>Grahhhhhaaaaaammmm, > >>> > >>>Aqui va: > >>> > >>>1) Configure ssh to authenticate using dsa keys... > >>> > >>> ? Create a folder named ".ssh" in your home directory (if it > >>>doesn't exist already) > >>> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" > >>> ? it will ask for a paraphrase. Leave it blank (just press enter > >>>through the three prompts) > >>> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your > >>>home directory of the remote machine (rails in this case) and > >>>rename the file in the remote machine to "authorized_keys". You can > >>>do these two steps using: > >>> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ > >>>authorized_keys" > >>> > >>>* Note - Leaving the passphrase blank is not the most secure thing, > >>>but that's the way it has to be for xcode and svnx to work. As an > >>>alternative, you can use a key manager. I haven't use any, but you > >>>could skip all the above and the manager would do all that > >>>dynamically every time you connect. I think "SSHKeychain" does that > >>>nicely in OSX. Never tried it though. > >>> > >>>Now you should be able to ssh to your account in rails without > >>>entering any password. > >>> > >>>2) Configure SvnX > >>> > >>> ? Open the "Repositories" window and create one. Fill the Path > >>>field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ > >>>tdg/svn/ > >>> ? Double click the repository, and check it out. This should add > >>>it to the "Working Copies" window. Now just use the working copy to > >>>commit, update, etc... > >>> > >>>if I forgot something, please fill in... > >>> > >>>j > >>> > >>> > >>> > >>> > >>> > >>>On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: > >>> > >>>For a svn newbie, could you step me through how you did this? > >>>Muchas Gracias! > >>> > >>>On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: > >>> > >>>>>If I can figure out my SVN client, I'll try and build an Xcode > >>>>>project and add it. > >>>> > >>>>I've got it go work with SvnX. Using svn+ssh. For that to work you > >>>>HAVE to configure password-less authentication (keygen...). > >>>> > >>>>j > >>>> > >>>>On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: > >>>> > >>>>If I can figure out my SVN client, I'll try and build an Xcode > >>>>project and add it. > >>>> > >>>>On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: > >>>> > >>>>>Ok.. It builds & runs.. The code base has been committed to > >>>>>subversion repo. > >>>>> > >>>>>Heres what's there: > >>>>>- New event stuff > >>>>>- Minimal application & scheduler > >>>>>- Placeholders for event queue, mem pool, etc. > >>>>>- Core_easy as a separate library > >>>>>- Example system library (graphics) > >>>>>- Example app (test_app) > >>>>>- Visual Studio solutions + projects > >>>>>- lots of other stuff we discussed. > >>>>> > >>>>>The stuff is in the repository under: > >>>>>\core\branch\mint > >>>>> > >>>>>The libs build a run in VS. I doubt it will build in gcc.. but > >>>>>probably not far off. > >>>>> > >>>>>Rama > >>>>> > >>>>>_______________________________________________ > >>>>>Tdg mailing list > >>>>>Tdg@mat.ucsb.edu > >>>>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>>> > >>>>_______________________________________________ > >>>>Tdg mailing list > >>>>Tdg@mat.ucsb.edu > >>>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>>> > >>>>_______________________________________________ > >>>>Tdg mailing list > >>>>Tdg@mat.ucsb.edu > >>>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>> > >>>_______________________________________________ > >>>Tdg mailing list > >>>Tdg@mat.ucsb.edu > >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >>> > >>>_______________________________________________ > >>>Tdg mailing list > >>>Tdg@mat.ucsb.edu > >>>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > >>_______________________________________________ > >>Tdg mailing list > >>Tdg@mat.ucsb.edu > >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >> > >>_______________________________________________ > >>Tdg mailing list > >>Tdg@mat.ucsb.edu > >>http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > >_______________________________________________ > >Tdg mailing list > >Tdg@mat.ucsb.edu > >http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Fri Mar 2 16:57:19 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 16:57:31 2007 Subject: [Tdg] Code commit In-Reply-To: <475258BD-CE3B-45D2-8A00-FBEBB0BFDCB2@umail.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> <475258BD-CE3B-45D2-8A00-FBEBB0BFDCB2@umail.ucsb.edu> Message-ID: <4F090703-E66D-4F02-9863-E859AA6539B9@mat.ucsb.edu> No, it complains that it is not a directory: g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys /Users/grahamwakefield/.ssh/authorized_keys: Not a directory Should I copy and then rename? Why does it think it is a directory in the first place? On Mar 2, 2007, at 4:39 PM, Jorge Castellanos wrote: >> I think you have to put some file in ~/.ssh/authorized_keys on >> maize... > > "authorized_keys" is not a directory. Is the new name for the file > being copied. > You are basically copying and renaming id_rsa.pub > > hope it works > > j > > > > On Mar 2, 2007, at 7:33 PM, Alex Norman wrote: > > I think you have to put some file in ~/.ssh/authorized_keys on > maize... > I don't really know much about ssh keys though.. > -Alex > > On 0, Jorge Castellanos wrote: >> You might have to create the .ssh directory in the home directory of >> the remote machine. >> After this, you should be able to ssh without a password. >> >> >> >> >> On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: >> >> Hey Jorge - >> >> I'm stuck: >> >> g:~ grahamwakefield$ cd .ssh >> g:~/.ssh grahamwakefield$ ls >> id_rsa id_rsa.pub known_hosts >> g:~/.ssh grahamwakefield$ ssh-keygen -t dsa >> Generating public/private dsa key pair. >> Enter file in which to save the key (/Users/grahamwakefield/.ssh/ >> id_dsa): >> Enter passphrase (empty for no passphrase): >> Enter same passphrase again: >> Your identification has been saved in /Users/grahamwakefield/.ssh/ >> id_dsa. >> Your public key has been saved in /Users/grahamwakefield/.ssh/ >> id_dsa.pub. >> The key fingerprint is: >> 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 >> grahamwakefield@g.local >> g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub >> wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys >> /Users/grahamwakefield/.ssh/authorized_keys: Not a directory >> >> ? >> >> On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: >> >>> Grahhhhhaaaaaammmm, >>> >>> Aqui va: >>> >>> 1) Configure ssh to authenticate using dsa keys... >>> >>> ? Create a folder named ".ssh" in your home directory (if it >>> doesn't exist already) >>> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" >>> ? it will ask for a paraphrase. Leave it blank (just press enter >>> through the three prompts) >>> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your >>> home directory of the remote machine (rails in this case) and >>> rename the file in the remote machine to "authorized_keys". You can >>> do these two steps using: >>> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ >>> authorized_keys" >>> >>> * Note - Leaving the passphrase blank is not the most secure thing, >>> but that's the way it has to be for xcode and svnx to work. As an >>> alternative, you can use a key manager. I haven't use any, but you >>> could skip all the above and the manager would do all that >>> dynamically every time you connect. I think "SSHKeychain" does that >>> nicely in OSX. Never tried it though. >>> >>> Now you should be able to ssh to your account in rails without >>> entering any password. >>> >>> 2) Configure SvnX >>> >>> ? Open the "Repositories" window and create one. Fill the Path >>> field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ >>> tdg/svn/ >>> ? Double click the repository, and check it out. This should add >>> it to the "Working Copies" window. Now just use the working copy to >>> commit, update, etc... >>> >>> if I forgot something, please fill in... >>> >>> j >>> >>> >>> >>> >>> >>> On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: >>> >>> For a svn newbie, could you step me through how you did this? >>> Muchas Gracias! >>> >>> On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >>> >>>>> If I can figure out my SVN client, I'll try and build an Xcode >>>>> project and add it. >>>> >>>> I've got it go work with SvnX. Using svn+ssh. For that to work you >>>> HAVE to configure password-less authentication (keygen...). >>>> >>>> j >>>> >>>> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >>>> >>>> If I can figure out my SVN client, I'll try and build an Xcode >>>> project and add it. >>>> >>>> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >>>> >>>>> Ok.. It builds & runs.. The code base has been committed to >>>>> subversion repo. >>>>> >>>>> Heres what's there: >>>>> - New event stuff >>>>> - Minimal application & scheduler >>>>> - Placeholders for event queue, mem pool, etc. >>>>> - Core_easy as a separate library >>>>> - Example system library (graphics) >>>>> - Example app (test_app) >>>>> - Visual Studio solutions + projects >>>>> - lots of other stuff we discussed. >>>>> >>>>> The stuff is in the repository under: >>>>> \core\branch\mint >>>>> >>>>> The libs build a run in VS. I doubt it will build in gcc.. but >>>>> probably not far off. >>>>> >>>>> Rama >>>>> >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From jcastellanos at umail.ucsb.edu Fri Mar 2 17:00:56 2007 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Fri Mar 2 17:01:12 2007 Subject: [Tdg] Code commit In-Reply-To: <4F090703-E66D-4F02-9863-E859AA6539B9@mat.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> <475258BD-CE3B-45D2-8A00-FBEBB0BFDCB2@umail.ucsb.edu> <4F090703-E66D-4F02-9863-E859AA6539B9@mat.ucsb.edu> Message-ID: Yes, you can copy and then rename Copy id_dsa.pub of your laptop into .ssh/ directory of rails Then rename the file of the remote machine to authorized_keys j On Mar 2, 2007, at 7:57 PM, Graham Wakefield wrote: No, it complains that it is not a directory: g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys /Users/grahamwakefield/.ssh/authorized_keys: Not a directory Should I copy and then rename? Why does it think it is a directory in the first place? On Mar 2, 2007, at 4:39 PM, Jorge Castellanos wrote: >> I think you have to put some file in ~/.ssh/authorized_keys on >> maize... > > "authorized_keys" is not a directory. Is the new name for the file > being copied. > You are basically copying and renaming id_rsa.pub > > hope it works > > j > > > > On Mar 2, 2007, at 7:33 PM, Alex Norman wrote: > > I think you have to put some file in ~/.ssh/authorized_keys on > maize... > I don't really know much about ssh keys though.. > -Alex > > On 0, Jorge Castellanos wrote: >> You might have to create the .ssh directory in the home directory of >> the remote machine. >> After this, you should be able to ssh without a password. >> >> >> >> >> On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: >> >> Hey Jorge - >> >> I'm stuck: >> >> g:~ grahamwakefield$ cd .ssh >> g:~/.ssh grahamwakefield$ ls >> id_rsa id_rsa.pub known_hosts >> g:~/.ssh grahamwakefield$ ssh-keygen -t dsa >> Generating public/private dsa key pair. >> Enter file in which to save the key (/Users/grahamwakefield/.ssh/ >> id_dsa): >> Enter passphrase (empty for no passphrase): >> Enter same passphrase again: >> Your identification has been saved in /Users/grahamwakefield/.ssh/ >> id_dsa. >> Your public key has been saved in /Users/grahamwakefield/.ssh/ >> id_dsa.pub. >> The key fingerprint is: >> 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 >> grahamwakefield@g.local >> g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub >> wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys >> /Users/grahamwakefield/.ssh/authorized_keys: Not a directory >> >> ? >> >> On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: >> >>> Grahhhhhaaaaaammmm, >>> >>> Aqui va: >>> >>> 1) Configure ssh to authenticate using dsa keys... >>> >>> ? Create a folder named ".ssh" in your home directory (if it >>> doesn't exist already) >>> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" >>> ? it will ask for a paraphrase. Leave it blank (just press enter >>> through the three prompts) >>> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your >>> home directory of the remote machine (rails in this case) and >>> rename the file in the remote machine to "authorized_keys". You can >>> do these two steps using: >>> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ >>> authorized_keys" >>> >>> * Note - Leaving the passphrase blank is not the most secure thing, >>> but that's the way it has to be for xcode and svnx to work. As an >>> alternative, you can use a key manager. I haven't use any, but you >>> could skip all the above and the manager would do all that >>> dynamically every time you connect. I think "SSHKeychain" does that >>> nicely in OSX. Never tried it though. >>> >>> Now you should be able to ssh to your account in rails without >>> entering any password. >>> >>> 2) Configure SvnX >>> >>> ? Open the "Repositories" window and create one. Fill the Path >>> field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ >>> tdg/svn/ >>> ? Double click the repository, and check it out. This should add >>> it to the "Working Copies" window. Now just use the working copy to >>> commit, update, etc... >>> >>> if I forgot something, please fill in... >>> >>> j >>> >>> >>> >>> >>> >>> On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: >>> >>> For a svn newbie, could you step me through how you did this? >>> Muchas Gracias! >>> >>> On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >>> >>>>> If I can figure out my SVN client, I'll try and build an Xcode >>>>> project and add it. >>>> >>>> I've got it go work with SvnX. Using svn+ssh. For that to work you >>>> HAVE to configure password-less authentication (keygen...). >>>> >>>> j >>>> >>>> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >>>> >>>> If I can figure out my SVN client, I'll try and build an Xcode >>>> project and add it. >>>> >>>> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >>>> >>>>> Ok.. It builds & runs.. The code base has been committed to >>>>> subversion repo. >>>>> >>>>> Heres what's there: >>>>> - New event stuff >>>>> - Minimal application & scheduler >>>>> - Placeholders for event queue, mem pool, etc. >>>>> - Core_easy as a separate library >>>>> - Example system library (graphics) >>>>> - Example app (test_app) >>>>> - Visual Studio solutions + projects >>>>> - lots of other stuff we discussed. >>>>> >>>>> The stuff is in the repository under: >>>>> \core\branch\mint >>>>> >>>>> The libs build a run in VS. I doubt it will build in gcc.. but >>>>> probably not far off. >>>>> >>>>> Rama >>>>> >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg _______________________________________________ Tdg mailing list Tdg@mat.ucsb.edu http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From wakefield at mat.ucsb.edu Fri Mar 2 17:01:51 2007 From: wakefield at mat.ucsb.edu (Graham Wakefield) Date: Fri Mar 2 17:02:01 2007 Subject: [Tdg] Code commit In-Reply-To: <5F575B0D-CFB4-4E81-A6CD-C499C230C372@mat.ucsb.edu> References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> <5F575B0D-CFB4-4E81-A6CD-C499C230C372@mat.ucsb.edu> Message-ID: Got it. I had a space character in the scp target address (I copied it from Jorge's email), which confused scp totally. On Mar 2, 2007, at 4:52 PM, Graham Wakefield wrote: > I already have a .ssh in maize: > > > g:~ grahamwakefield$ ssh wakefield@maize.mat.ucsb.edu > Password: > Last login: Tue Jan 30 11:52:16 2007 from freeip88.mat.ucsb.edu > wakefield@maize ~ $ cd .ssh > wakefield@maize ~/.ssh $ ls > authorized_keys id_dsa id_dsa.pub > > If I ssh to rails.mat.ucsb.edu, I end up on maize anyway. I didn't > realize they are the same server. > > > > > On Mar 2, 2007, at 4:33 PM, Alex Norman wrote: > >> I think you have to put some file in ~/.ssh/authorized_keys on >> maize... >> I don't really know much about ssh keys though.. >> -Alex >> >> On 0, Jorge Castellanos wrote: >>> You might have to create the .ssh directory in the home directory of >>> the remote machine. >>> After this, you should be able to ssh without a password. >>> >>> >>> >>> >>> On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: >>> >>> Hey Jorge - >>> >>> I'm stuck: >>> >>> g:~ grahamwakefield$ cd .ssh >>> g:~/.ssh grahamwakefield$ ls >>> id_rsa id_rsa.pub known_hosts >>> g:~/.ssh grahamwakefield$ ssh-keygen -t dsa >>> Generating public/private dsa key pair. >>> Enter file in which to save the key (/Users/grahamwakefield/.ssh/ >>> id_dsa): >>> Enter passphrase (empty for no passphrase): >>> Enter same passphrase again: >>> Your identification has been saved in /Users/grahamwakefield/.ssh/ >>> id_dsa. >>> Your public key has been saved in /Users/grahamwakefield/.ssh/ >>> id_dsa.pub. >>> The key fingerprint is: >>> 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 >>> grahamwakefield@g.local >>> g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub >>> wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys >>> /Users/grahamwakefield/.ssh/authorized_keys: Not a directory >>> >>> ? >>> >>> On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: >>> >>>> Grahhhhhaaaaaammmm, >>>> >>>> Aqui va: >>>> >>>> 1) Configure ssh to authenticate using dsa keys... >>>> >>>> ? Create a folder named ".ssh" in your home directory (if it >>>> doesn't exist already) >>>> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" >>>> ? it will ask for a paraphrase. Leave it blank (just press enter >>>> through the three prompts) >>>> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your >>>> home directory of the remote machine (rails in this case) and >>>> rename the file in the remote machine to "authorized_keys". You can >>>> do these two steps using: >>>> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ >>>> authorized_keys" >>>> >>>> * Note - Leaving the passphrase blank is not the most secure thing, >>>> but that's the way it has to be for xcode and svnx to work. As an >>>> alternative, you can use a key manager. I haven't use any, but you >>>> could skip all the above and the manager would do all that >>>> dynamically every time you connect. I think "SSHKeychain" does that >>>> nicely in OSX. Never tried it though. >>>> >>>> Now you should be able to ssh to your account in rails without >>>> entering any password. >>>> >>>> 2) Configure SvnX >>>> >>>> ? Open the "Repositories" window and create one. Fill the Path >>>> field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ >>>> tdg/svn/ >>>> ? Double click the repository, and check it out. This should add >>>> it to the "Working Copies" window. Now just use the working copy to >>>> commit, update, etc... >>>> >>>> if I forgot something, please fill in... >>>> >>>> j >>>> >>>> >>>> >>>> >>>> >>>> On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: >>>> >>>> For a svn newbie, could you step me through how you did this? >>>> Muchas Gracias! >>>> >>>> On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >>>> >>>>>> If I can figure out my SVN client, I'll try and build an Xcode >>>>>> project and add it. >>>>> >>>>> I've got it go work with SvnX. Using svn+ssh. For that to work you >>>>> HAVE to configure password-less authentication (keygen...). >>>>> >>>>> j >>>>> >>>>> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >>>>> >>>>> If I can figure out my SVN client, I'll try and build an Xcode >>>>> project and add it. >>>>> >>>>> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >>>>> >>>>>> Ok.. It builds & runs.. The code base has been committed to >>>>>> subversion repo. >>>>>> >>>>>> Heres what's there: >>>>>> - New event stuff >>>>>> - Minimal application & scheduler >>>>>> - Placeholders for event queue, mem pool, etc. >>>>>> - Core_easy as a separate library >>>>>> - Example system library (graphics) >>>>>> - Example app (test_app) >>>>>> - Visual Studio solutions + projects >>>>>> - lots of other stuff we discussed. >>>>>> >>>>>> The stuff is in the repository under: >>>>>> \core\branch\mint >>>>>> >>>>>> The libs build a run in VS. I doubt it will build in gcc.. but >>>>>> probably not far off. >>>>>> >>>>>> Rama >>>>>> >>>>>> _______________________________________________ >>>>>> Tdg mailing list >>>>>> Tdg@mat.ucsb.edu >>>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>>> >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>>> >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From jcastellanos at umail.ucsb.edu Fri Mar 2 17:03:04 2007 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Fri Mar 2 17:03:21 2007 Subject: [Tdg] Code commit In-Reply-To: References: <45E7A97D.2000204@umail.ucsb.edu> <77AD7962-8170-4A93-83F1-DDEE3039A197@mat.ucsb.edu> <77DEE60F-F9EE-4DF4-9071-DDE92D2FE836@umail.ucsb.edu> <1C342232-C5FC-4156-8460-D8FB13E4A418@mat.ucsb.edu> <4C9F41E2-C8E7-4871-A64C-3C7C1094D90B@umail.ucsb.edu> <4C89F891-1C9F-49FD-B9D7-BEDBD7AAD1C4@mat.ucsb.edu> <20070303003337.GV22044@silverninja.net> <5F575B0D-CFB4-4E81-A6CD-C499C230C372@mat.ucsb.edu> Message-ID: sorry :-) On Mar 2, 2007, at 8:01 PM, Graham Wakefield wrote: Got it. I had a space character in the scp target address (I copied it from Jorge's email), which confused scp totally. On Mar 2, 2007, at 4:52 PM, Graham Wakefield wrote: > I already have a .ssh in maize: > > > g:~ grahamwakefield$ ssh wakefield@maize.mat.ucsb.edu > Password: > Last login: Tue Jan 30 11:52:16 2007 from freeip88.mat.ucsb.edu > wakefield@maize ~ $ cd .ssh > wakefield@maize ~/.ssh $ ls > authorized_keys id_dsa id_dsa.pub > > If I ssh to rails.mat.ucsb.edu, I end up on maize anyway. I didn't > realize they are the same server. > > > > > On Mar 2, 2007, at 4:33 PM, Alex Norman wrote: > >> I think you have to put some file in ~/.ssh/authorized_keys on >> maize... >> I don't really know much about ssh keys though.. >> -Alex >> >> On 0, Jorge Castellanos wrote: >>> You might have to create the .ssh directory in the home directory of >>> the remote machine. >>> After this, you should be able to ssh without a password. >>> >>> >>> >>> >>> On Mar 2, 2007, at 7:04 PM, Graham Wakefield wrote: >>> >>> Hey Jorge - >>> >>> I'm stuck: >>> >>> g:~ grahamwakefield$ cd .ssh >>> g:~/.ssh grahamwakefield$ ls >>> id_rsa id_rsa.pub known_hosts >>> g:~/.ssh grahamwakefield$ ssh-keygen -t dsa >>> Generating public/private dsa key pair. >>> Enter file in which to save the key (/Users/grahamwakefield/.ssh/ >>> id_dsa): >>> Enter passphrase (empty for no passphrase): >>> Enter same passphrase again: >>> Your identification has been saved in /Users/grahamwakefield/.ssh/ >>> id_dsa. >>> Your public key has been saved in /Users/grahamwakefield/.ssh/ >>> id_dsa.pub. >>> The key fingerprint is: >>> 27:56:7a:4f:ad:0e:39:c0:d0:70:58:62:7f:56:16:45 >>> grahamwakefield@g.local >>> g:~/.ssh grahamwakefield$ scp ~/.ssh/id_dsa.pub >>> wakefield@rails.mat.ucsb.edu: ~/.ssh/authorized_keys >>> /Users/grahamwakefield/.ssh/authorized_keys: Not a directory >>> >>> ? >>> >>> On Mar 2, 2007, at 11:49 AM, Jorge Castellanos wrote: >>> >>>> Grahhhhhaaaaaammmm, >>>> >>>> Aqui va: >>>> >>>> 1) Configure ssh to authenticate using dsa keys... >>>> >>>> ? Create a folder named ".ssh" in your home directory (if it >>>> doesn't exist already) >>>> ? cd to the .ssh directory and type: "ssh-keygen -t dsa" >>>> ? it will ask for a paraphrase. Leave it blank (just press enter >>>> through the three prompts) >>>> ? Copy the public key "id_dsa_[ub" to the .ssh directory in your >>>> home directory of the remote machine (rails in this case) and >>>> rename the file in the remote machine to "authorized_keys". You can >>>> do these two steps using: >>>> "scp ~/.ssh/id_dsa.pub user@targetServer.com: ~/.ssh/ >>>> authorized_keys" >>>> >>>> * Note - Leaving the passphrase blank is not the most secure thing, >>>> but that's the way it has to be for xcode and svnx to work. As an >>>> alternative, you can use a key manager. I haven't use any, but you >>>> could skip all the above and the manager would do all that >>>> dynamically every time you connect. I think "SSHKeychain" does that >>>> nicely in OSX. Never tried it though. >>>> >>>> Now you should be able to ssh to your account in rails without >>>> entering any password. >>>> >>>> 2) Configure SvnX >>>> >>>> ? Open the "Repositories" window and create one. Fill the Path >>>> field with: svn+ssh://yourUserName@rails.mat.ucsb.edu/mat/groups/ >>>> tdg/svn/ >>>> ? Double click the repository, and check it out. This should add >>>> it to the "Working Copies" window. Now just use the working copy to >>>> commit, update, etc... >>>> >>>> if I forgot something, please fill in... >>>> >>>> j >>>> >>>> >>>> >>>> >>>> >>>> On Mar 2, 2007, at 1:35 PM, Graham Wakefield wrote: >>>> >>>> For a svn newbie, could you step me through how you did this? >>>> Muchas Gracias! >>>> >>>> On Mar 2, 2007, at 8:09 AM, Jorge Castellanos wrote: >>>> >>>>>> If I can figure out my SVN client, I'll try and build an Xcode >>>>>> project and add it. >>>>> >>>>> I've got it go work with SvnX. Using svn+ssh. For that to work you >>>>> HAVE to configure password-less authentication (keygen...). >>>>> >>>>> j >>>>> >>>>> On Mar 2, 2007, at 3:26 AM, Graham Wakefield wrote: >>>>> >>>>> If I can figure out my SVN client, I'll try and build an Xcode >>>>> project and add it. >>>>> >>>>> On Mar 1, 2007, at 8:35 PM, Rama Hoetzlein wrote: >>>>> >>>>>> Ok.. It builds & runs.. The code base has been committed to >>>>>> subversion repo. >>>>>> >>>>>> Heres what's there: >>>>>> - New event stuff >>>>>> - Minimal application & scheduler >>>>>> - Placeholders for event queue, mem pool, etc. >>>>>> - Core_easy as a separate library >>>>>> - Example system library (graphics) >>>>>> - Example app (test_app) >>>>>> - Visual Studio solutions + projects >>>>>> - lots of other stuff we discussed. >>>>>> >>>>>> The stuff is in the repository under: >>>>>> \core\branch\mint >>>>>> >>>>>> The libs build a run in VS. I doubt it will build in gcc.. but >>>>>> probably not far off. >>>>>> >>>>>> Rama >>>>>> >>>>>> _______________________________________________ >>>>>> Tdg mailing list >>>>>> Tdg@mat.ucsb.edu >>>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>>> >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>>> >>>>> _______________________________________________ >>>>> Tdg mailing list >>>>> Tdg@mat.ucsb.edu >>>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>>> >>>> _______________________________________________ >>>> Tdg mailing list >>>> Tdg@mat.ucsb.edu >>>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >>> >>> _______________________________________________ >>> Tdg mailing list >>> Tdg@mat.ucsb.edu >>> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg ________________________