|teferi||more or less|
|slyphon||for some reason with jfs partitions, they get wedged in "uninterruptible sleep" state|
|apeiros||jakehow, still, paths don't have to be absolute.|
|jakehow||does a require statement look in each value in the LOAD_PATH array?|
|apeiros||they have to be relative to $: for normal requires and work somewhat similarly for gems|
yes, but gems hijacks require
I don't know if it searches for a gem first and then $: or otherway round. I think gem first.
rofl: "Theory and practice are two completely different things." - "Not in theory."
|stouset||apeiros: I like the fact that things that work in practice is not a proper subset of things that work in theory.|
|apeiros||stouset, those occurances just show flaws in the theory ;-)|
|slyphon||what's the deal with "bsd disklabel"s|
|teferi||slyphon: oh man, you're in for a treat|
ready for this?
|slyphon||i withdraw the quesiton!|
it's not slices, right?
|teferi||too late, you get it anyway|
|teferi||so, what everyone else calls partitions, bsd calls slices|
|nullie||theory is approximation|
|teferi||and then you put a disklabel on a slice and divide THAT up into what it calls partitions|
|slyphon||right, but, uhm, bah, nvm|
|apeiros||nullie, and practice is poking with a stick in the dark :)|
|teferi||so, for example, ad0s1a is ata disk 0, slice (aka what everyone else calls partition) 1, partition 'a' (first 'partition')|
|nullie||yeah, theory tells you where to poke|
|apeiros||(hoping to push the buttons that theory claims are there, well, maybe slightly somewhere else)|
|jakehow||apeiros: does File.readlines require an absolute path?|
sometimes stuff like that is in there. but only sometimes.
|jakehow||apeiros: hmm... b/c it works only if i make the path absolute|
|apeiros||jakehow, that just means your relative path is wrong|
relative to $0, not __FILE__
don't forget that.
|LoganCapaldo||relative to Dir.pwd, not $0 or __FILE__|