To expand on this slightly, I have had good success with duplicity.
It supports gpg signing and encrypting of archives and provides direct support for scp/ssh as a transport while handling full and incremental backups very nicely (well, after I wrote a few wrapper scripts just to make my life easier).
I have not used it on windows with cygwin, but I know people who are.
In short, these are my own opinions. I cannot think of anytime the CoC has ever tried to explain its thought process to students. In general we are left in the dark about their master plan. Personally I worry more about MLB tracking my every move than anything of that nature comming from the CoC.
First of all, CS1 is (or was for me) based on psycode, and will soon be a class focused on Matlab, digital media and some fundamentals of programming. So, yes I would agree with you saying the Pascal is not useful for CE's, however matlab and general digital media might come in handy, not to mention a basic understanding of recusion and iteration. (Side note: I don't know for sure, but I don't believe pascal has ever been taught for CS1 at Tech). My major is CS, however, of my non-CS friends almost all are glad they took CS1 when they finally got through the class, especially when they need to use matlab and maple to solve engineering and problems.
Most of you are misinterpriting the idea behind this type of rule. Yes, in the real world collaboration is increadably important, infact it is so important that we actually take classes in software design where the entire class is in groups. Learning how to interact with people and function in teams, methods of interaction and teamwork, dealing with problem members and managment, these are REQUIRED classes, and yes, groupwork is a required part of them. We even cover different philosophies of team interaction, the ancient methods and new concepts such as Extreme Programing. However, these rules are for the very begining, we are talking CS1 and 2 here, collaboration is not permitted. Yes, when I was taking the classes, I complained about the very constraining rules, and I did say that "In the real world, collaboration (and while I'm at it, not re-inventing the wheel) is important." However, it is also important to learn the basics yourself. Everyone in the entire university must take CS1 and most CS2, these are just intro programing classes to get people familure with coding and thinking on there own. That is their point, and to accomplish that, they must seperate the students out. Some of the strictness is misunderstood. The java API is not looked down upon, we are told to print it out and sleep with it under our pillows, to use it so much that by the end of the year it looks a bit the something from the 12th century. Granted that is in jest, but the point is, documentation, man pages, that type of stuff is encouraged. It is just the first few classes need to focus on the individual, not the team. You must first build yourself before you can build on yourself, and in order to assure that, rules must be in place. The CS majors know, or eventually realize once they reach the 2000 and above CS classes, that they benifitted from the artificial division. Maybe they knew everything going into CS1 and 2, but now all (or most) of their peers are strong on their own. So when it comes time to work together, each programmer could stand on their own, but together their skill is greater than the collective sum. In addition, it goes to teach the true value of working together, they know first hand how hard it can be to stand alone. Maybe it is difficult to see looking in, but there is a good concept behind the rules. Yes, they might not need to be there if everyone was honest, but unfortunately this is not a perfect world, and the restrictive environment helps in the long run.
Slashdot Mirror
To expand on this slightly, I have had good success with duplicity.
It supports gpg signing and encrypting of archives and provides direct support for scp/ssh as a transport while handling full and incremental backups very nicely (well, after I wrote a few wrapper scripts just to make my life easier).
I have not used it on windows with cygwin, but I know people who are.
In short, these are my own opinions. I cannot think of anytime the CoC has ever tried to explain its thought process to students. In general we are left in the dark about their master plan. Personally I worry more about MLB tracking my every move than anything of that nature comming from the CoC.
First of all, CS1 is (or was for me) based on psycode, and will soon be a class focused on Matlab, digital media and some fundamentals of programming. So, yes I would agree with you saying the Pascal is not useful for CE's, however matlab and general digital media might come in handy, not to mention a basic understanding of recusion and iteration. (Side note: I don't know for sure, but I don't believe pascal has ever been taught for CS1 at Tech). My major is CS, however, of my non-CS friends almost all are glad they took CS1 when they finally got through the class, especially when they need to use matlab and maple to solve engineering and problems.
Most of you are misinterpriting the idea behind this type of rule. Yes, in the real world collaboration is increadably important, infact it is so important that we actually take classes in software design where the entire class is in groups. Learning how to interact with people and function in teams, methods of interaction and teamwork, dealing with problem members and managment, these are REQUIRED classes, and yes, groupwork is a required part of them. We even cover different philosophies of team interaction, the ancient methods and new concepts such as Extreme Programing. However, these rules are for the very begining, we are talking CS1 and 2 here, collaboration is not permitted. Yes, when I was taking the classes, I complained about the very constraining rules, and I did say that "In the real world, collaboration (and while I'm at it, not re-inventing the wheel) is important." However, it is also important to learn the basics yourself. Everyone in the entire university must take CS1 and most CS2, these are just intro programing classes to get people familure with coding and thinking on there own. That is their point, and to accomplish that, they must seperate the students out. Some of the strictness is misunderstood. The java API is not looked down upon, we are told to print it out and sleep with it under our pillows, to use it so much that by the end of the year it looks a bit the something from the 12th century. Granted that is in jest, but the point is, documentation, man pages, that type of stuff is encouraged. It is just the first few classes need to focus on the individual, not the team. You must first build yourself before you can build on yourself, and in order to assure that, rules must be in place. The CS majors know, or eventually realize once they reach the 2000 and above CS classes, that they benifitted from the artificial division. Maybe they knew everything going into CS1 and 2, but now all (or most) of their peers are strong on their own. So when it comes time to work together, each programmer could stand on their own, but together their skill is greater than the collective sum. In addition, it goes to teach the true value of working together, they know first hand how hard it can be to stand alone. Maybe it is difficult to see looking in, but there is a good concept behind the rules. Yes, they might not need to be there if everyone was honest, but unfortunately this is not a perfect world, and the restrictive environment helps in the long run.