Search options

I learned Perl, PHP, and HTML pretty much on my own --  Perl and PHP have pretty good APIs (http://perldoc.perl.org/ and http://www.php.net/manual/en/). HTML tutorials can be found just about anywhere -- Short Order HTML is a great start (old, but great) http://www.amazon.com/Short-Order-HTML- … 0789720493

But as far as real programming languages, C++ used to be the standard in classes (C before that, I think). Now they usually start with Java. The important part is to decide whether you want to start with object-oriented languages. If you've not run into O-O stuff before, you might want to take a look at it before you start learning anything. It usually takes a couple times before it really sinks in.

As far as which to study, Python, Java, and C++ will probably be great, but I'd start with C++ until you feel like you have a good grasp on programming, then move on to one of the others. O'Reilly books are generally very good and available for most languages. They're a little pricey (like all computer books), but they're a great resource and reference guide.

I had a similar problem on my EEE when I first got it. Turns out there were two problems I had:

1) Sleeping or hibernation will screw up the connection when on campus -- for a large network like that, they refresh your connection info every time you log on. Unfortunately when you resume, the OS may try to use the same connection info while the network has moved on. A simple reboot solves this -- however, this doesn't sound like your issue.

2) I've done this a few times myself -- accidentally turning off WiFi using the Fn hotkeys. I've also (with no clue how) accidentally turned of WiFi in the Bios. Next time you reboot, drop by the bios and make sure the WiFi is enabled.

Hope this helps.

Nice! It's a good idea...I've always hated typing in the repeated junk.

A couple of ideas:
1) It's a good idea to include warnings and strict rules:

#!/usr/bin/perl -w
use strict;

2) I like to toss in

use Carp;

to get a bit more feedback for debugging

3) Perl has a built in chmod function: http://perldoc.perl.org/functions/chmod.html

Essentially its

chmod 0755 $file

4) I'd probably use

exec

over

system

since you don't really need to come back to the script -- just end it and forget about it.

5) However, that means you'll want to close the file immediately after you write to it. Another solution (to make Perl more forgivable, and also a little better) would be to change your file handle:

open(my $fh, '>', $file);
print $fh '#!...'."\n".'use strict'."\n";
close($fh);

You use the variable just as you would any other filehandle, but it gets included in garbage collection (i think)...either way, it's a little cleaner. You also don't need the append if the file hasn't been created yet.

Good code...I'll have to use this for template creation myself. Kudos!

Trying to get the iso now  -- I don't have unlimited bandwith, but should be enough to help ride the wave. I'll post the links asap.

I'd love to help -- just joined Launchpad. I've never done any OS development, but I'd love to get my hands dirty. I have a good amount of programming / project development experience, just lacking a bit in the time area (grad school tends to do that).

How does this work? Are there particular projects or just look at known bugs and try to fix 'em?

I'm a bit of an eclectic when it comes to Linux -- I can't help trying out different distributions and changing things up. Since I've come to #!, I can't bring myself to go anywhere else .