FreeBSD's install needs a ton of help. I tried to use sysinstall (yeh, I'm smart enough not to need it) to install from da0 onto a new disk, ad0, but it just installed over the existing system. Also, as of 4.0-R and 4.1-R (haven't tried with 4.1.1-R, you can't install on a Tekram 390F card. The included sym device driver is broken with these cards. Guess that's why there's an amd device driver, though I haven't tried it yet. Had to drop back to 3.4-R on this machine (don't have 3.5-R handy) just to get it installed. Then 3.4-R installer was broken that caused it to segfault when selecting the distribution options on a custom install. This is really making me think of rewriting FreeBSD's install. It's a joke that this can't work better. I also wonder if the boot blocks in 3.4-R suffer from the same problems that's noted in the errata of 4.1-R. Guess I really shouldn't complain as I haven't done that much FreeBSD work reciently.
I really think there needs to be a replacement for CVS, I've been thinking about one, and started writing up a paper for the goals of the project. Needs some more fleshing out, but when I come to sit down and think about how to implement it, I get a bit lost. Guess I should go on a walkabout thinking about how to do it. The hard part is being able to cordinate merging diffs between three branches. I may just break down and do a really braindead algo at first and hope someone improves afterward. Pretty sure I'll do it in python intialy. So much quicker, but I'm just not motivated.
I am looking at possibly doing some outside consulting work in the BSD kernel/VFS/file system/device driver area part of things. It'll be all the way in Condon(?), Mass. If I do it, it'll definately be telecomute as I'm not going to move to Mass for a 6+ month contract. Should be interesting, I feel a bit out of my leage as this is my first contract that I'd do on my own in naming the price, but it'll be a good learning experience. I hope the project is interesting that I'd be into working on for 30+ hours/wk.
Just as a hint, if you're going to use qbasic, learn about sub and function. I started (real) programming with qbasic, and have to say that you don't need to use goto's in qbasic. You'll found out that goto's are evil and pretty much should be avoided. If you start using sub/function, I'm sure your prof will be impressed. Now if the prof told you not to use sub/function, then ignore everything he says.