If you want to connect to an Oracle database with PHP you will need the pecl module named oci8
First in order to compile it you will need Oracle Instant Client ( both basic & sdk ) . You can download them from here:
If you don’t have an Oracle account you will need to create one.
At the time of this post the following files are available: instantclient-basic-linux32-220.127.116.11.zip , instantclient-sdk-linux32-18.104.22.168.zip .
Create a directory in /opt mkdir /opt/oracle/instantclient and copy those files there . Then unzip them . You will need to create a symbolic link ln -s libclntsh.so.11.1 libclntsh.so
Then you will need to install libaio if you don’t have it already . Don’t forget to add /opt/oracle/instantclient/instantclient_11_2 to /etc/ld.so.conf .
At this point you are ready to install the pecl extension to php.Create a temporary directory ( /tmp/1 ) and cd there.
pecl download oci8
tar xf oci8-1.3.5.tar
edit /etc/php.ini and add
And enjoy oracle extension for php. Note: if you have apache running restart it.
From time to time i need to know what mac is on a cisco port. This is a reminder on how this is done:
sh mac-address-table interface <Interface>
tfm.ro needs a new face. in the beginning we started with an inhouse mini CMS. Then we switched to mediawiki and focused on end user documentation and howto. At this point we use wordpress with Structure theme .
What is not ok:
- Community options are limited
- User generated content is limited to comments
- Integration with the development site is done only via an RSS feed
- Looks old and dusty
- We focus on development and by doing this the site is most of informations are old and sometime obsolete
So , i’m begining to search for an alternative that will have to provide:
- community options ( registration , posibility to upload pictures , patches , docs etc )
- bug tracker integrated with the main site
- online manuals creation / gathering
Do you know what options are out there ?
How NOT to take part in the events:
- If you want to win, don’t bother.
- If you think events are something you should get, because you are kewl, don’t bother.
- If you think that prizes in events are for free, you’re wrong and don’t bother.
- If you want to take part in event just to bitch at prizes, DO NOT bother.
- If you think that the hints should give you precise walkthrough, guess what? – don’t bother!
- If you are not used to use the content of you head to the purposes Mother Nature created it – don’t bother!
- If you’re not able to read and understand hints – don’t bother!
- If you think you’re too 1337 for events, don’t bother!
How NOT to host an event:
- If you think that everything will go as you planned, you’re wrong.
- If you think that everybody will be happy with prizez, you’re wrong.
- If you think contesters will understand your hints and follow them, you’re wrong.
- If you hope to hear a ‘thank you’, you’re optimists.
- If you are not ready to read complaints, bitching and ‘This should be done this way, not as it was’, contests are not for you.
How to take part in the events:
- If you want to take part in the event for fun, not prizes. You’re precious, hope you will do it each time.
- If you do use your brain, read hints and do not whine – hope you will take part in all events.
- If you’re able to have fun without getting prize – :thumbs up:
- If you are able to give sensible critic with good arguments, I bet contest holders will love you.
How to host an event:
- Be ready for frustration.
- Be ready for bitching.
- Be ready for disappointment.
- Be ready for nobody understanding your hints.
- Be ready for huge costs.
- Be ready for everything going wrong.
- You know what? SCREW it, go and have a beer with friends. It’s surelly better idea.
When you manage a project with svn there are a lot of things to consider: how you create the repository, what external resources will be imported in the repository. Basically it’s a constant job on how to organize things better to keep developers happy.
After lots of try/fail cycles i came to the conclusion that for linux distribution the best approach would be a tree like this
What is wrong with this structure? In time a developer will update bzip2 from server 32 tree but will forget or won’t have the time to update server64 tree. So the trees will not stay in sync. And this is bad because it might happen that the projects will have different sources.
What can be done? Use svn:external declarations. First idea was to create a common tree and create externals from both server and server64. But this way we will have 3 trees and lot of work to do. And it will become hard to manage. Another approach was needed. We decided that server is the main tree. In the server64 tree we declared bzip2 to be external and pulled from 32 bit tree.
This way if a developer commits a change will go in both trees simultaneously.
How to use svn: external? Let’s take for example bzip2 from server64
svn del bzip2; svn commit ; svn pedit svn:externals . ; svn up ; svn commit
and when editing svn external you should add a like like this: