[thesite] if anyones bored..

[Daniel J. Cody]

.jeff wrote:

>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
>>From: Daniel J. Cody
>>
>>i also think a lot more people here *and* on thelist
>>would contribute code(if you think about it, there are
>>only about 3, maybe four of us(jeff, me, josh, matt)
>>that contribute right now). and we get a lot of shit
>>done between us 4, but i think a lot of people that
>>have PHP skills are sitting here on their hands waiting
>>to contribute.. maybe i'm wrong, but thats the feelign
>>i got from 3 other people who are on this list and were
>>at codefest last weekend..
>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
>>
> 
> so you think there are enough people willing to contribute code over the
> long haul (not just the initial honeymoon stage) to offset the loss of 4
> people that currently "get a lot of shit done"?  and you think these people
> that are willing to contribute are on par experience and talent wise with
> those that'd be replaced?
 

yes, yes, and yes.

 
>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
>>also, having to alter *every* m.e.o account that uses
>>PHP(80% of them) after installing CF5 so they'd point
>>to the right mysql.sock file was pretty discouraging.
>>it had to be changed, becuase CF is only configured to
>>look for that file in one place(/var/lib/mysql/mysql.sock)
>>and you couldn't configure it to look anywhere else.
>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
>>
> 
> i don't know jack about linux, but couldn't you do something like a symlink
> (is that what it's called?) or something to the place cf is configured to
> look?  something like this?
> 
> ln -s /tmp/mysql.sock /var/lib/mysql/mysql.sock


ya, hi. of course i tried that. thankfully, linux has a strong enough 
security backbone where thats not allowed. heres why:

ln -s /tmp/mysql.sock /home/djc/hackmysql.sock

all the sudden, i can read the contents of that unix socket. second, 
even if it were possible, you can't just symlink socket files.

obviously, a bad idea. my point was that this should be a confiurable 
thing. only the RedHat RPM file puts that file in /var/lib/mysql. you're 
screwed if you have a default MySQL install on anything but 
redhat(Caldera, SuSe, Debian). why should i have to hack around CF just 
to get it to work? its seriously counter-intuitive and one of my major 
problems with CF lately(Rearrange your system to work with how we think 
it should. Macromedia, the company that has about 3 people that know 
Linux. ahem.). its either 'their' way, or the hard way. <asshole 
remark>if they want to impose that kind of shit on people, they 
should've stayed in the win32 market</ar>. people that work with linux 
systems expect to able to change a thing here or there. whether thats 
where a socket file for a DB driver sits, or how many times you have to 
click 'OK' to add a datasource. sorry, its a bit outside our 
converstation, but something i've been thinking about, take it as you 
will :)


> what i'm getting at is there are always going to be snags when installing
> software.  either you can change it, but you don't have time to figure out
> how or you can't which means you gotta make changes somewhere else to
> account for it.


sure. you shouldn't have to rework the basis of your DB connectivity 
across the board to accomdate CF though. thats all i'm saying.


.djc.