Well my next semester changed quite a bit

only taking 3 classes

still taking software engineering (apparently we have to buy an ethics book for it, interesting), network comm....but I am taking the capstone Operating Systems class as well. I have heard it is quite difficult.

Professors keep changing shit left and right so it might change more before the semester starts, who know.

Time to get intimate with C and unix this semester

Our professor is making us use RCS for projects. I only know ic/oc [-l]/rlog and ident so far. Not sure how much more I will need yet.

This post was edited by Eep on Jan 27 2014 02:46am

I know I've been a bit of a harsh asshole in the past but I'm really impressed at how far you've come since you started posting here. It's amazing what full immersion in a subject can do.

haha thanks. Yeah, to be honest I came in with a very narrow understanding and now that I have kind of seen things from the other side a bit. I can understand where a lot of the frustration from you and others came from.

I for one acted waaay too douchey and defensive when faced with criticism and new ideas. Nowadays, I understand that even with a 4 year degree and some internship experience, I haven't even scraped 1% of the true CS world.

The science is young still, and there is still so much left to be discovered. We have a few 'concrete' results people tend to fall on, but for the most part new methods are being created every day.

I personally got really absorbed into it because I like understanding how things work, and I want to be a part of the CS community because I have great respect for the ones who have pioneered our current levels of technology.

I almost feel like I 'owe' the world some due with how much technology I have used.

So here is to another difficult and hopefully fulfilling semester. I'll try and keep the thread updated with fun OS projects.

First project is to do a breadth-first traversal of a given unix path, eventually displaying the contents. (indented by hierarchy)

Using lstat, various directory functions etc.

Later we have to add command options to have it display all relevant info, follow symbolic links or change printed indentation.

This post was edited by Eep on Jan 30 2014 11:59am

I don't know if this has been brought up already, not going through 12 pages of reading. But you shouldn't get into the habit of using namespace. Better to practice using std:: infront of the standard library for when you get into other libraries that use same namespaces.

if you can't bother to figure out where thread is currently you can feel free to not post either

let me know how you handle symlinks

currently trying to handle that in one of my projects, seems a symlink creates a folder in the dir it's symlinked too so if I choose to do a foreach file in that folder statement I have to add the exception for that folder that's generated and it's annoying

might just be an ubuntu thing, haven't seen this on my centos5.10 box but have seen this on ubuntu 12

remember to always use a const whenever possible.

yeah, it is the last thing I gotta implement.

My shit is mostly working now, there is just a few things I gotta iron out.

-->Adding a value to my queue struct to keep track of directory depth

-->Fix printf formatting so it looks more like an ls -lA ;{ (I fucking suck at this)