XOOPS, You Can Do It Again and Again
Now, we'll assume you have MySQL and Apache/PHP running, so it is time to start with the installation of XOOPS.
Point your Web browser to http://127.0.0.1/install/index.php if you are using your own server. Point it to http://yourdomain/install/index.php if you are using a commercial host.
This should take you to the install screen. See Figure 2 for an example.
Now, click on the Next button to see a brief introduction, as shown in Figure 3.
Click on the Next button once again. At this point, it is quite possible you will experience a problem with the permissions (see Figure 4 for an example).
Here's how to solve these permission problems:
$ chmod 777 uploads/ $ chmod 777 cache/ $ chmod 777 templates_c/ $ chmod 666 mainfile.php
Once you have set the correct permissions, press the Reload button, and you should see that there are no longer permission problems (Figure 5).
Press the Next button again. Before we explain how to fill in the next page, you need to create the XOOPS MySQL database and a user name and password for that database. Open a console or an X terminal, and run the following commands:
$ mysqladmin -u mysql -p create xoops4 $ mysql -u mysql -p
In this case, I selected xoops4 for the database name, and I used the default mysql as the MySQL user. You can use these names if you want to, but make sure to remember them. You'll need to fill in this information in a Web page shortly. The second command above logs you in to MySQL and presents you with a MySQL command prompt. Once you see the prompt, type the following command to give the mysql user privileges to the xoops4 database, and set the password:
mysql> GRANT ALL PRIVILEGES ON xoops4.* TO mysql@localhost --<IDENTIFIED BY 'password';
Now that you've made a database called xoops4, you must replace its password in the command shown as 'password'.
Now, back to the XOOPS Web configuration page. Fill in the correct information. Figure 6 shows the information for our sample installation. Normally, you would fill in the last field with the domain name for your Web server instead of using 127.0.0.1.
After you click the Next button, you should see a screen that confirms all the information you entered (Figure 7). If everything looks fine, click Next. If something went wrong, go back and modify the information to correct it.
When you press Next after the confirmation screen, you should see a new screen with the title Saving configuration data (Figure 8). Press the Next button again. XOOPS will check to see if the physical and virtual path to the XOOPS files are correct (Figure 9).
Click the Next button again. You should see a Web page that confirms the database settings (Figure 10).
Next, XOOPS checks to see if it can connect to the database and modify the database (Figure 11).
Click the Next button once again. Now the XOOPS installer creates all of the MySQL tables it needs (Figure 12).
Now you need to fill the text boxes with information about the administrator of the XOOPS site (Figure 13). XOOPS will ask you about the Admin name, Email and the password for the Admin account.
Click Next, and XOOPS uses this information to insert some starting data in various XOOPS tables (Figure 14).
Click the Next button once again and that should get your XOOPS site up and running. You should see a final confirmation screen like the one shown in Figure 15.
Press the HERE link to get to the login screen for your site. This is actually what your site looks like when you first start XOOPS. It is obviously bare bones, but that is because you haven't activated any of the XOOPS features yet.
Log in using the administrator user name and password you specified earlier.
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- My +1 Sword of Productivity
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide