Some advice... and unionfs :)
James, I think you need to learn to live with some discontentment, at least for a while. I have been extraordinarily lucky, in that I've known my calling pretty much all of my memorable life. Not entirely a good thing, but it certainly helps you feel content at the end of the day. I believe that you haven't found exactly what you want to be doing, and I'd hazard a guess that the longer you spend without knowing what you want to do, the harder it becomes to find out what it is you want to do.
Perhaps you already know, but you lack the conviction to throw yourself at it full tilt?
Until either situation changes, learn to live with this uncertainty - I can't speak from experience I'm afraid, so this may make my advice sound a little hollow, but I'm sure plenty of other people live with the same problem every day without feeling any the worse for it. Maybe you can take some happiness from it? Me, I have a basic outline for how the rest of my life will probably turn out. That can be a little disheartening at times; where as you, you still have the potential to be any number of things!
And like Mark said, as for it not being about you - it clearly is... Given that we see the world from our own perspective, it's hardly surprising that our thought processes revolve around ourselves. The likelihood of a truly (within reason, don't start with quantum theory or whatever...) random comment is quite low.
As for me, I'm feeling alright at the moment :) I'm not in a 'work' mood yet, I've just spent my post-exam time chilling so far (which took that awesome night out for me to realise this is what I needed).
When I supposed my idea to a post-grad friend of mine (about unionfs in regards to software located at multiple locations under multiple prefixes), he almost straight away came back with the problem of hard-coded paths when compiling applications. I figured out the solution today :) I was thinking about it incorrectly - unfortunately, you cannot just install to a seperate prefix, you need to install to the 'root' prefix (i.e. /usr). The magic comes in that before making the install target, you unionfs mount the prefix directory over whatever directory you've unionroot'd with the highest priority before installing - Then it'll get installed to the prefix, but be prepared to execute on the 'root'. Problem solved :)
I'm planning on making some scripts for all this, that use symlinking to simulate the features of unionfs somewhat... Given that I can't actually use unionfs in labs at the moment - I'll try to bribe help-desk into compiling the kernel module though, but I *VERY* much doubt this will happen. If it does, I will be a happy bunny :) Will find out tomorrow.
Also, Mark, that question looks like piss compared to the last question on my latest Scheme coursework that took me TEN fucking hours and ended up as like 12 lines of code :p (ends up the theory to the solution is quite simple, just implementation is a little more complex... Everything is easier in retrospect though...)
Perhaps you already know, but you lack the conviction to throw yourself at it full tilt?
Until either situation changes, learn to live with this uncertainty - I can't speak from experience I'm afraid, so this may make my advice sound a little hollow, but I'm sure plenty of other people live with the same problem every day without feeling any the worse for it. Maybe you can take some happiness from it? Me, I have a basic outline for how the rest of my life will probably turn out. That can be a little disheartening at times; where as you, you still have the potential to be any number of things!
And like Mark said, as for it not being about you - it clearly is... Given that we see the world from our own perspective, it's hardly surprising that our thought processes revolve around ourselves. The likelihood of a truly (within reason, don't start with quantum theory or whatever...) random comment is quite low.
As for me, I'm feeling alright at the moment :) I'm not in a 'work' mood yet, I've just spent my post-exam time chilling so far (which took that awesome night out for me to realise this is what I needed).
When I supposed my idea to a post-grad friend of mine (about unionfs in regards to software located at multiple locations under multiple prefixes), he almost straight away came back with the problem of hard-coded paths when compiling applications. I figured out the solution today :) I was thinking about it incorrectly - unfortunately, you cannot just install to a seperate prefix, you need to install to the 'root' prefix (i.e. /usr). The magic comes in that before making the install target, you unionfs mount the prefix directory over whatever directory you've unionroot'd with the highest priority before installing - Then it'll get installed to the prefix, but be prepared to execute on the 'root'. Problem solved :)
I'm planning on making some scripts for all this, that use symlinking to simulate the features of unionfs somewhat... Given that I can't actually use unionfs in labs at the moment - I'll try to bribe help-desk into compiling the kernel module though, but I *VERY* much doubt this will happen. If it does, I will be a happy bunny :) Will find out tomorrow.
Also, Mark, that question looks like piss compared to the last question on my latest Scheme coursework that took me TEN fucking hours and ended up as like 12 lines of code :p (ends up the theory to the solution is quite simple, just implementation is a little more complex... Everything is easier in retrospect though...)
posted by Chris at 11:15 pm
