psiguy

1. When you decide to try out a program you would usually... (a) Read the manual for documentation on how to use it. (b) Dive right in and hope to make something out of it. 2. When you want to install a new program or add a feature, how far are you willing to go? (a) All the way!!! No error is too tough for me. (b) I know my limits. I'll give up when all suggested methods do not work for the umpteenth time. (c) As long as they are friendly error messages, they can't bite! Right? (d) AHHHHHHHHHHH!!!!!!! Error!!!!!! run away!!!! 3. When an error interrupts your normal activities you would do the following to solve them. (check allthat

Final Project For My Unix Class: This will be the first project that will have my attention. I have to create a project that relates to Unix/linux and create an essay/presentation about it. Ive decided that since I am getting my hand dirty with my linux box, I'd be bound to break it once in a while. Therefore, my project will be the creation of a backup/restore utility from c++ compiled with G++. Currently, I'm fleshing out the node based archetecture of the filesystem that would represent my backed up files and folders. The nodes will allow for advanced backup/restore operations as well as provide (if enabled) the inherit securities found i

(Q: ) What have you been doing all this time? I've seen that you haven't yet... (1) finished the trade with ~Paperiapina (https://www.deviantart.com/paperiapina) (2) post your proposition on the integration of 3d into the transformations of Freeborn (3) Finish the man -> canine transformation (A: ) In general, I am a bit busy with going to colledge and doing chores and other miscellaneous nuisances of life. After experiencing all of that, I do tend to run out of "creative juices" to start those projects and procrastinate. It's not like I've forgotten all about them. They taunt me from time to time like a bad dream. In time I'll have to get off my lazy arse and obsessively tac