|chadmaynard||thumbs: its not easy to tell someone what distro to go with before you are around|
|thumbs||well not to sound condescending, but rpms are nothing but trouble, most of the time|
a debian box, gentoo, or slackware is much easier to upgrade.
|chadmaynard||i know i hate them|
|ToeBee||heh. gentoo is easy to update... unless it is a really important package like, say, glibc :)|
|thumbs||ToeBee: I was comparing it to rpm-based distros, after all|
I don't want to start a distro fight, I merely want to point out easier option for him
|ToeBee||heh. yeah. I DO use gentoo a lot actually|
|thumbs||especially as they age.|
I'm a slackware person.
|chadmaynard||thumbs: me too|
upgrading anything is hard if it hasn't been touched in 5 years
|ToeBee||especially considering all the rootkits that will be on there :)|
|chadmaynard||no it has no access to the internet|
i don't think its been compromised
|ToeBee||yeah but the alien mind rays can still get to it!|
|chadmaynard||it has tcp80 inbound from the LAN|
ToeBee: I have anti-aliens.rpm installed
|ToeBee||ooh good work|
|loquitus_of_borg||Hey people... I have a database foo that has some tables in it. Is there a way to have another database bar on the same server to somehow have a "symbolic" link to some of the tables from foo?|
So that someone who accesses bar can do selects from those tables in foo....
|ToeBee||why not just let the user do selects on the tables directly? you can restrict privileges to specific operations on specific tables|
|Xgc||loquitus_of_borg: or use VIEWs to access the other database.|
|loquitus_of_borg||ToeBee: I realize that but if the user is logged in and connected to the database bar, I want then to only access bar and not mess with foo in any way or form... I want bar to be not visible to them for all intents|