From: Robert P. J. D. <rp...@mi...> - 2003-02-03 23:19:54
|
sorry i've been so out of touch lately -- lots of projects on the go at the moment. at the moment, i'm writing a short chapter on how to start programming on linux -- scripting, setting up java, and so on. i'm going to discuss how to start writing code in shell, perl, c and c++, ruby and java. any others that should be included here? without getting obscenely obscure, that is. rday -- Robert P. J. Day, RHCE Eno River Technologies, Inc. Unix, Linux and Open Source training Chapel Hill, NC Waterloo, ON http://www.linux-migration.org |
From: Taylor, F. <for...@in...> - 2003-02-04 00:08:13
|
Robert P. J. Day wrote: > > > sorry i've been so out of touch lately -- lots of projects on the > go at the moment. > > at the moment, i'm writing a short chapter on how to start > programming on linux -- scripting, setting up java, and so on. > i'm going to discuss how to start writing code in shell, perl, > c and c++, ruby and java. > > any others that should be included here? without getting > obscenely obscure, that is. > > rday How about python, as it seems to be the favorite of the Red Hat developpers. Forrest -- |
From: Robert P. J. D. <rp...@mi...> - 2003-02-04 00:14:53
|
On Mon, 3 Feb 2003, Taylor, ForrestX wrote: > How about python, as it seems to be the favorite of the Red Hat developpers. already there. keep in mind that i'm not trying to show anyone how to *program* in any of these languages, just how to set up the infrastructure -- search path, chmod, that sort of thing. so, any other languages? i figured i'd draw the line at stuff like tcl/tk. rday |
From: Joe K. <kle...@we...> - 2003-02-04 01:51:00
|
On Mon, 2003-02-03 at 19:13, Robert P. J. Day wrote: > > How about python, as it seems to be the favorite of the Red Hat developpers. > > already there. keep in mind that i'm not trying to show anyone > how to *program* in any of these languages, just how to set up > the infrastructure -- search path, chmod, that sort of thing. I'm still inclined to keep this as minimal as possible. Discussing anything beyond shell (as related to batch programs) would be excessive. > so, any other languages? i figured i'd draw the line at stuff > like tcl/tk. If you're gonna have python you should also include tcl/tk as it's just about as popular in the wild. :-) -- "It's time to KISS your BOT goodBYYYYYYEEEEEE!!!!!" -- Metabee, 'Medabots' |
From: Martin S. <sh...@gm...> - 2003-02-05 00:11:02
|
Joe Klemmer wrote: > I'm still inclined to keep this as minimal as possible. > Discussing anything beyond shell (as related to batch programs) would > be excessive. Point taken. But since he just shows how to *set up the environment* I think he should go for it. > > so, any other languages? I don't know it that's possible, but it would be nice to show the migrants how to use languages they already know like Visual Basic or (maybe) C#. > > i figured i'd draw the line at stuff like tcl/tk. > > If you're gonna have python you should also include tcl/tk > as it's just about as popular in the wild. :-) And it's platform independent. I often use Perl's Tk package to create cross-platform graphical applications. Just copy the scripts over and they'll run on *nix, Win, Mac... (well, there are a few dangers there) Best regards, Martin Stricker -- Homepage: http://www.martin-stricker.de/ Linux Migration Project: http://www.linux-migration.org/ Red Hat Linux 7.3 for low memory: http://www.rule-project.org/ Registered Linux user #210635: http://counter.li.org/ |
From: Joe K. <kle...@we...> - 2003-02-04 01:47:36
|
On Mon, 2003-02-03 at 18:18, Robert P. J. Day wrote: > sorry i've been so out of touch lately -- lots of projects on the > go at the moment. > > at the moment, i'm writing a short chapter on how to start > programming on linux -- scripting, setting up java, and so on. > i'm going to discuss how to start writing code in shell, perl, > c and c++, ruby and java. > > any others that should be included here? without getting > obscenely obscure, that is. I wouldn't go to deep into this. IMO, programming would be beyond the scope of this project. I think it would be best to limit this to only programming requirements needed by sysadmin types. A basic bash rundown and an intro to perl (enough to get them to be able to port their batch files and such) would be enough. Then just point to the wealth of programming info available on the 'Net and the book stores. At least this is my opinion (speaking as a programmer and a sysadmin). -- "It's time to KISS your BOT goodBYYYYYYEEEEEE!!!!!" -- Metabee, 'Medabots' |
From: Robert P. J. D. <rp...@mi...> - 2003-02-04 01:51:51
|
On 3 Feb 2003, Joe Klemmer wrote: > I wouldn't go to deep into this. IMO, programming would be beyond > the scope of this project. I think it would be best to limit this to > only programming requirements needed by sysadmin types. A basic bash > rundown and an intro to perl (enough to get them to be able to port > their batch files and such) would be enough. Then just point to the > wealth of programming info available on the 'Net and the book stores. > actually, that section is almost done, so i'll send it on to martin to post as soon as it it. no, it doesn't get very deep -- you'll see what i mean shortly. rday |
From: Joe K. <kle...@we...> - 2003-02-04 12:03:09
|
On Mon, 2003-02-03 at 20:50, Robert P. J. Day wrote: > actually, that section is almost done, so i'll send it on to martin > to post as soon as it it. no, it doesn't get very deep -- > you'll see what i mean shortly. Ok. I actually trust your judgment. I'm just keeping my eye on what the MS admins are asking about at work. -- "It's time to KISS your BOT goodBYYYYYYEEEEEE!!!!!" -- Metabee, 'Medabots' |