text:
Summer Courses in China for NM Teachers, March 6, 2000
SOCORRO, N.M., March 6, 2000 -- As part of its curriculum this coming summer, New Mexico Tech's Master of Science Teaching (MST) program will offer 12 selected state educators -- culled primarily from rural, ethnically diverse areas of New Mexico -- the opportunity to take summer field courses in the People's Republic of China.
Through funding provided by a prestigious U.S. Department of Education program, Tech's MST program is vastly expanding its boundaries this summer to the Huebei Province of China, including
stopovers in the cities of Beijing, Wuhan, and Yichang.
Because of a special monetary award acquired from the Fulbright-Hays Group Projects Abroad Program, teachers enrolled in two of the ten classes offered this summer through the MST program will be conducting environmental science field, lab, and classroom studies of water quality analysis and environmental law and regulations pertaining to water resource management in China.
"This is an exciting opportunity for MST participants to include an international component in their graduate studies," says Vannetta R. Perry, New Mexico Tech's coordinator for educational outreach programs.
"New Mexico Tech was very fortunate to get Fulbright-Hays funding for this particular project, since out of about 300 proposals which are submitted annually, only 35 to 40 projects are actually funded each year throughout the nation," she adds.
In one of the classes, MST program participants taking the 32-day-long "Chinese Area Studies in Water Law and Water Quality: An International Perspective" will be conducting surveys and analyses of Chinese water resources, particularly those related to the Three Gorges Dam Project on the Yangtze River.
Cross-cultural activities will be interspersed throughout the project and will be augmented with various field excursions that explore Chinese culture, history, religion, philosophy, geography, and educational systems.
By also presenting summations and completing papers which focus on integrating what was learned during the seminars into their respective instructional programs, participants can earn up to six graduate science teaching credit hours through New Mexico Tech's MST degree-granting program.
"As educators, it is important for us to open the world to our students and the Chinese Area Studies in Water Law and Water Quality courses also will provide that opportunity," adds Perry.
"We all will learn far beyond the environmental law and environmental engineering aspects of the course components. The cultural awareness and experiences will be invaluable, and bringing that knowledge back to New Mexico will enrich the teaching and learning of our state's K-12 students."
Perry also points out that results derived from the Chinese study may potentially have "significant applications" to water- quality problems in other countries.
Applicants who are chosen to participate in the Chinese Area Studies in Water Law and Water Quality summer courses will be provided with air travel to and from China, plus per diem expenses, as part of the funding contributed by the Fulbright- Hays Group Projects Abroad Program. However, participants will be responsible for paying all other expenses associated with the program, including registration and fees for the MST classes.
Applications for the Chinese program must be completed, submitted, and postmarked no later than Saturday, March 25.
Those interested in applying for the program, or those who wish to receive more information about these or other MST courses being offered this summer, are asked to contact Perry as soon as
possible at (505) 835-5678, or by e-mail at email@example.com.
Applications and detailed information about the program also are available at the New Mexico Tech MST website at www.nmt.edu/~science/mst.


text:
Rangers rev up offense, but big inning lifts Astros
ARLINGTON -- Two teams, 28 hits, 19 runs.
Monday night was an offensive showdown between the AL West's two bottom teams, each desperately seeking a win -- the Astros with a seven-game losing skid, the Rangers returning home after a 1-6 road trip.View Full Game Coverage
ARLINGTON -- Two teams, 28 hits, 19 runs.
Monday night was an offensive showdown between the AL West's two bottom teams, each desperately seeking a win -- the Astros with a seven-game losing skid, the Rangers returning home after a 1-6 road trip.View Full Game Coverage
And as their bats showed, each were relentless in their quest for the win column.
The Astros set the tone early, and it carried them to a 12-7 win.
In the second inning alone, they scored six runs off seven hits -- six singles and a triple.
"I think I made some good pitches there in the second inning. Some of them might have caught a little too much plate, but I think the first four or five hits that inning were all pretty weak contact," Rangers starter Miles Mikolas said. "And then a triple scores a lot of those guys."
The Rangers found the scoreboard in the second, as well, but their one run was just a fraction of the six the Astros had put up in their half of the inning.
Leonys Martin walked and scored to make it 6-1 after Rougned Odor reached first base on a fielding error by Jon Singleton.
In the third, Alex Rios doubled to center field and scored to make it 6-2 when Adrian Beltre extended his hitting streak to 11 games and doubled to right field.
"They've been coming around. They've been putting runs on the board," Rangers manager Ron Washington said of the middle of his lineup. "We just haven't been able to stop the other team once we put some on the board."
For a moment, it seemed as if the Astros had crushed the Rangers' chances of mounting a comeback for good in the fourth when Singleton sent his sixth homer of the season over the fence in right-center, plating three runs. The Astros went up 9-2.
"If he executes the pitch right there, different story," Washington said of Mikolas, who gave up the homer. "Those are the things that he has to learn. You can throw strikes, but you have to make them quality."
But the Rangers pressed on. With two outs and the bases loaded in the fourth, Elvis Andrus cleared them with a double to deep left field to cut the Astros' lead to 9-5.
Then Beltre homered in the fifth -- and all of a sudden the Rangers were down just three runs, their smallest deficit of the night.
Houston starter Jarred Cosart went five innings with nine hits and six runs, five of which were earned. He struck out just two.
But the Astros extended it to four again in the top of the sixth when Alex Presley homered off Scott Baker, who had replaced Shawn Tolleson. Tolleson pitched 1 2/3 innings in relief of Mikolas, who lasted for just 3 1/3. Mikolas gave up 12 hits and nine runs -- all earned -- to go along with five strikeouts.
Meanwhile Baker went for 3 1/3 innings with three hits, three runs and two strikeouts, earning the praise of his manager.
"Each time we've brought him in he's saved the bullpen. He did it again tonight," Washington said. "Can't say enough about what Baker's done. Every time he's come in, he's saved us."
The Astros scored their 11th and 12th runs in the eighth, the game's final tallies. And though the Rangers had rallied for seven runs -- their most since June 16 -- they had still scored just one run more in the whole game than Houston had in the second inning.
"It was really good to see the offense finally break out. We had been scuffling," Astros manager Bo Porter said. "The fact that we were able to continue to add on runs even when they responded, spoke a lot to the value of today's win."
Washington's offense broke out, too -- just not to that extent.
"They put seven on the board tonight. That should be enough to win a ballgame," Washington said. "But [Houston] put up 12. Had 18 hits. Just couldn't stop them."
Grace Raynor is an associate reporter for MLB.com.

subset: commoncrawl


text:
Cover Story
Jubilee 2000 has surprised people with its phenomenal success. A look at how and why it caught fire - and what's around the bend.
The Jubilee 2000/USA campaign
Church leaders came together to declare widespread poverty 'morally unacceptable.' And they promised to do something about it.
Pocket Canons are the most radical approach to the Bible since Gutenberg. Or at least Ginsberg.
The power of ministering to the bereaved.
Adapted from the Free Time/Free People Campaign statement.
Honorable work and restful renewal are both aspects of responsibility.
Together Palestinian and Israeli activists fight 'functional apartheid' in the West Bank.
But does it have to COST SO MUCH!?
Steps to getting the funeral you want and can afford.
Missile defense: the wrong path to security.
The battle over who owns the Net rages on.
Family farms---and farmers---are looking different these days.
You can't be laid off for bad genes. Can you?
Benetton's ads open eyes. Can they say lives?
China is the current battleground---as Seattle was last fall---over the rules of global trade.
Youthful idealism can grow into life-long commitment to justice.
Wherever self-censorship rules, a real debate is not taking place.
The Covenant to Overcome Poverty is as simple as it is potentially life-changing.
There comes a time in every man's life when he has to begin a sentence with a really bad cliche. This is one of those times. You see, words are not coming easy to me these days.
Culture Watch
Breaking our deadly addiction to advertising.
Vassar Miller is the Emily Dickinson of the 20th century.
Native struggles for environmental justice.
E-commerce guerrillas are the direct descendants of Abbie Hoffman.
Ambivalence as a religious virtue?
Scripted hope in The West Wing.
Sorting out justice in South Africa.
A prophetic voice in the Christian pop wilderness.
THE JANUARY-FEBRUARY 2000 issues theme of "Ethics and the Bottom Line" brought to mind the different standards of accountability for the business and the nonprofit sectors.
Bringing people together.
For around $2,500 you too can be a DJ in the micro-radio revolution.
I didn't follow the holy man around
I FOUND HELENE SLESSAREV'S article "Saul Alinsky Goes to Church" (March-April 2000) interesting because the situation in the United Kingdom is very different.
While the U.S.-backed sanctions against Iraq continue to devastate that country, a growing clamor of voices is rising up in opposition
SOJOURNERS IS ALWAYS "on target" in challenging us to be peacemakers, but the January-February 2000 issue is stunning! Thank you for each article.
Speak Up!
I WAS GREATLY heartened to read Ched Myers' account of a people's Bible reading, motivated by a commitment to transformation and accepting of diverse readings.
Defying the assumption that Serbs and ethnic Albanians are incapable of peaceful coexistence, leaders of the religious communities of Kosovo issued a common statement for reconciliation.
THANK YOU FOR the subscription to Sojourners.
Coming together to say no to poverty.
JUST WHEN I THOUGHT Sojourners had gotten to the mountaintop in articles and analysis of truth and faith...it gets better.
A new report shows that the current economic boom is not finding its way to the collection plate.
Citizens call a new tune.
JIM WALLIS VIVIDLY recalls the optimism at the ecumenical "Call to Jubilee" service on the eve of the WTO conference ("Seattle: Changing the Rules," March-April 2000).
Two Guatemalan military officers have been arrested and charged with the April 1998 murder of Catholic bishop and human rights advocate Juan Jose Gerardi.
I WANTED TO THANK you for Ted Parks thoughtful article about our beloved City of the Angels Film Festival ("Strange Bedfellows," March-April 2000).
The U.S. prison population passed the two million mark in February, provoking vigils and protests in more than 40 U.S. cities.
A rag-tag movement of churches, development organizations, and trade unions...
IN RESPONSE TO Rose Marie Berger's "Why I'm Walking to Work Tomorrow" (January-February 2000), I ask: What will it take for us to slow down and take a good, hard look at what we're doing?
I'm sorry to sound cynical, but as Gil Scott-Heron rapped long ago, "the revolution will not be televised."


text:
Three down, 67 to go.
In the past two weeks, Navy (Kraft Fight Hunger) and BYU (San Diego County Credit Union Poinsettia) have accepted invitations to one of the 35 bowl games that will be played this season. Friday night, Air Force became the third.
Following the Falcons' 21-7 win over Hawaii, their sixth of the season, the service academy received an invitation to the, appropriately enough, Armed Forces Bowl by the game's executive director, who was in attendance last night. Suffice to say, the Falcons quickly accepted the bid to the Fort Worth-based bowl.
"We didn't expect what happened," linebacker Alex Means said of the invitation. "I'm so proud of these guys. We're going bowling."
Just who Air Force will be bowling against remains to be seen, although it will very likely be a team from Conference USA.


text:
A great deal of your time will be spent keeping your Linux system up to date with the latest and greatest software. There are three basic methods to installing software on a Linux system. One, use the package manager for the distribution. This is typically the Red Hat Package Manager (RPM). Two, compile the software using the standard GNU compilation method. Three, compile and install the software by hand. We will cover these methods in this module.
When installing software, you typically need to be the root user. (Module 6 will cover how to change user IDs with the su command.) In a terminal window, just type su – root.
Use the Red Hat Package Manager
The Red Hat Package Manager's primary function is to allow the installation and removal of files (typically, precompiled software). It is wonderfully easy to use, and several graphical interfaces have been built around it to make it even easier. Red Hat, Caldera, and other distributions have started using this tool to distribute their software. In fact, almost all of the software mentioned in this book is available in RPM form. The reason you'll go through the process of compiling software yourself in other modules is so that you can customize the software to your system, as such customizations might not exist in an RPM.
An RPM file is a package that contains files needed for the software to function correctly. These files can be configuration files, binaries, and even pre and post scripts to run while installing the software.
NOTE In this context, we are assuming that the RPM files contain precompiled binaries. Several groups, such as Red Hat, also make source code available as an RPM, but it is uncommon to download and compile source code in this fashion.
The RPM tool performs the installation and uninstallation of RPMs. The tool also maintains a central database of what RPMs you have installed and other information about the package.
In general, software that comes in the form of an RPM is less work to install and maintain than software that needs to be compiled. The tradeoff is that by using an RPM, you accept the default parameters supplied in the RPM. In most cases, these defaults are acceptable. However, if you need to be more intimately aware of what is going on with a service, you may find that compiling the source yourself will prove more educational about what package components exist and how they work together.
Assuming that all you want to do is install a simple package, RPM is perfect. There are several great resources for RPM packages, including the following:
Of course, if you are interested in more details about RPM itself, you can visit the RPM Web site at http://www.rpm.org/. RPM comes with Red Hat Linux (and derivatives) as well as Caldera Linux. If you aren't sure if RPM comes with your distribution, check with your vendor.
NOTE Although the name of the package says "Red Hat," the software can be used with other distributions as well. In fact, RPM has even been ported to other operating systems, such as Solaris and IRIX. The source code to RPM is open-source software, so anyone can take the initiative to make the system work for them.
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Installing a New Package}
The easiest way to install a new package is to use the -i option with RPM. For example, if you downloaded a package called bc-1.05a-4.i386.rpm and wanted to install it, you would type:
[root@ford /root]# rpm -ivh bc-1.05a-4.i386.rpm
If the installation went fine, you would not see any errors or messages. This is the most common method of installing RPMs. On the other hand, if the package already exists, you would see this message:
error: package bc-1.05a-4 is already installed
Some packages rely on other packages. A game, for example, may depend on SVGA libraries having already been installed. In those instances, you will get a message indicating which packages need to be installed first. Simply install those packages and then come back to the original package.
If you need to upgrade a package that already exists, use the -U option, like so:
[root@ford /root]# rpm -Uv bc-1.05a-4.i386.rpm
Some additional command-line options to RPM are listed in Table 1.
|Command-Line Option
|This is the sledgehammer of installation. Typically, you use it when you're knowingly installing an odd or unusual configuration, and RPM's safeguards are trying to keep you from doing so. The –force option tells RPM to forego any sanity checks and just do it, even if it thinks you're trying to fit a square peg into a round hole. Be careful with this option.
|Prints hash marks to indicate progress during an installation. Use with the -v option for a pretty display.
Prints the percentage completed to indicate progress. It is handy if you're running RPM from another program, such as a Perl script, and you want to know the status of the install.
|If RPM is complaining about missing dependency files, but you want the installation to happen anyway, passing this option at the command line will cause RPM to not perform any dependency checks.
|Queries the RPM system for information.
|This option does not perform a real installation; it just checks to see whether an installation would succeed. If it anticipates problems, it displays what they'll be.
|Verifies RPMs or files on the system.
|Tells RPM to be verbose about its actions.
Table 1 RPM Command-Line Options
For example, to force the installation of a package regardless of dependencies or other errors, you would type:
[root@ford /root]# rpm -i –force -nodeps packagename.rpm
where packagename.rpm is the name of the package being installed.
Querying a Package
Sometimes it is handy to know which packages are currently installed and what they do. You can do that with the RPM query options.
To list all installed packages, simply type:
[root@ford /root]# rpm -qa
Be ready for a long list of packages! If you are looking for a particular package name, you can use the grep command to specify the name (or part of the name) of the package, like so:
[root@ford /root]# rpm -qa | grep -i ' name'
NOTE The -i parameter in grep tells it to make its search case-insensitive.
If you just want to view all of the packages one screen at a time, you can use the more command, like so:
[root@ford /root]# rpm -qa | more
To find out which package a particular file belongs to, type:
[root@ford /root]# rpm -qf filename
where filename is the name of the file that you want to check on.
To find out the purpose of a package that is already installed, you must first know the name of the package (taken from the listing in rpm -qa) and then specify it, like so:
[root@ford /root]# rpm -qi packagename
where packagename is the name of the package that you want information about.
To find out what files are contained in a package, type:
[root@ford /root]# rpm -qlp packagename
where packagename is the name of the package that you want information about.
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Uninstalling a Package}
Uninstalling packages with RPM is just as easy as installing them. In most cases, all you will need to type is
[root@ford /root]# rpm -e packagename
where packagename is the name of the package as listed in rpm -qa.
Verifying an RPM
A very cool option to the RPM tool is the ability to verify a package. What happens is RPM looks at the package information in its database, which is assumed to be good. It then compares that information with the binaries and files that are on your system. Unfortunately, in today's Internet world, where being hacked is a real possibility, this kind of test should tell you instantly if anyone has done something to your system (see Module 11 for tips on securing your system from attacks). For example, if you want to verify that the /bin/ls command is valid, you would type:
[root@ford /root]# rpm –Vf /bin/ls
If everything is okay with /bin/ls, nothing will be displayed to the terminal. If something is wrong, RPM will inform you of what test failed. Some example tests are the MD5 checksum test, file size, and modification times. The moral of the story is: RPM is an ally in finding out what is wrong with your system. If you suspect several things might be wrong, you can verify all installed packages on your system by typing:
[root@ford /root]# rpm –Va
This command verifies all of the packages installed on your system. That's a lot of files, so you might have to give it some time to complete.
GUI RPM Installers
For those who like a good GUI tool to help simplify their lives, there are several package managers included with your distribution. Gnorpm is a good GNOME tool that will typically work under KDE as well. It performs all of the functions that the command-line version does without forcing you to remember command-line parameters. Of course, this comes at the price of not being scriptable, but that's why you have the command-line version, too.
Progress Check
- What does RPM stand for? (Red Hat Package Manager)
- What command is used to query the RPM database? (rpm -q)
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Compile and Install GNU Software}
One of the key benefits of open-source software is that you have the source code in your hands. If the developer chooses to stop working on it, you can continue. If you find a problem, you can fix it. In other words, you are in control of the situation and not at the mercy of a commercial developer you can't control. But having the source code means you need to be able to compile it, too. Otherwise all you have is a bunch of text files that can't do much.
Although almost every piece of software in this book is available as an RPM, we will step through the process of compiling it yourself so that you can pick and choose compile time options, which is something you can't do with RPMs. Also, an RPM might be compiled for a specific architecture such as the Intel 486. That code might run better if you compiled it natively on your Intel 686 Pentium III class CPU.
In this section, we will step through the process of compiling the Hello package, a GNU software package that might seem useless at first, but there are reasons for its existence. Most GNU software conforms to a standard method of installing, so let's go ahead and get the package.
Getting and Unpacking the Package
Software that comes in source form is generally made available as a tarball–that is, it is archived into a single large file and then compressed. The tools used to do this are tar and gzip. tar handles the process of combining many files into a single large file, and gzip is responsible for the compression.
NOTE Do not confuse gzip with WinZip. They are two different programs that use two different (but comparable) methods of compression. It should be noted, though, that WinZip does know how to handle tarballs.
Typically, a single directory is selected in which to build and store tarballs. This allows the system administrator to keep the tarball of each package in a safe place in the event he or she needs to pull something out of it later. It also lets all the administrators know which packages are installed on the system in addition to the base system. A good directory for this is /usr/local/src, since software local to a site is generally installed in /usr/local.
When unpacked, a tarball will generally create a new directory for all of its files. The hello tarball (hello-1.3.tar.gz), for example, creates the subdirectory hello-1.3. Most packages follow this standard. If you find a package that does not follow it, it is a good idea to create a subdirectory with a reasonable name and place all the unpacked source files there. This allows multiple builds to occur at the same time without the risk of the two builds conflicting.
First, let's get into the directory we want to compile in:
[root@ford /root]# cd /usr/local/src
Download the hello-1.3.tar.gz file from the GNU FTP site at ftp://ftp.gnu.org/gnu/hello/. You can type the URL into a browser and download the package or you can use the ftp command-line tool to download the package
[root@ford src]# ftp ftp.gnu.org
Connected to ftp.gnu.org
220 GNU FTP server ready.
330 Please specify the password.
Password:email@example.com (You won't see this when you type it)
ftp>cd /gnu/hello
ftp>get hello-1.3.tar.gz
It is a common courtesy to type in your e-mail address as the password. If the ftp account doesn't work you might want to try anonymous. Once in the ftp command prompt, the bin option tells ftp that you want to transfer the files using binary mode. The hash option will print a hash mark for every 1024 bytes of data sent. Finally, you cd into the directory and then issue the FTP get command to grab the file. You exit the FTP program by typing bye. Then unpack the tarball with the following command:
[root@ford src]# tar -xvzf hello-1.3.tar.gz
NOTE You might encounter files that end with the .tar.bz2 extension. Bzip2 is a compression algorithm that is gaining popularity, and GNU tar does support decompressing it on the command line with the y or j option (instead of the z parameter).
The z parameter in the tar command invokes gzip to decompress the file before the untar process occurs. The v parameter tells tar to show the name of the file it is untarring as it goes through the process. This way you'll know the name of the directory where all the sources are being unpacked. You should now have a directory called /usr/local/src/hello-1.3. You can test this by using the cd command to move into it:
[root@ford src]# cd /usr/local/src/hello-1.3
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Looking for Documentation}
Once you are inside the directory with all of the source code, begin looking for documentation. Always read the documentation that comes with the source code! If there are any special compile directions, notes, or warnings, they will most likely be mentioned here. You will save yourself a great deal of agony by reading the relevant files first.
So then, what are the relevant files? Typically there are two files in a distribution, README and INSTALL, both of which are located in the root of the source code directory. The README file generally includes a description of the package, references to additional documentation (including the installation documentation), and references to the author of the package. The INSTALL file typically has directions for compiling and installing the package.
These are not, of course, absolutes. Every package has its quirks. The best way to find out is to simply list the directory contents and look for obvious signs of additional documentation. Some packages use different capitalization: readme, README, ReadMe, and so on. Some introduce variations on a theme, such as README.1ST or README.NOW, and so on.
Another common place for additional information is a subdirectory that is appropriately called "doc" or "documentation."
To view a text file, use the more command:
[root@ford hello-1.3]# more README
To view the text file in the pico editor, use the pico command:
[root@ford hello-1.3]# pico README
TIP To get a quick list of all the directories in a source tree, enter the command [root@ford hello-1.3]# ls -l | grep drwx.
Configuring and Compiling the Package
Most packages ship with an autoconfiguration script; it is safe to assume they do unless their documentation says otherwise. These scripts are typically named configure, and they take parameters. There are a handful of stock parameters that are available across all configure scripts, but the interesting stuff occurs on a program-by-program basis. Each package will have a handful of features that can be enabled or disabled or that have special values set at compile time, and they must be set up via configure.
To see what configure options come with a package, simply run:
[root@ford hello-1.3]# ./configure –help
Yes, those are two hyphens (—) before the word "help."
One commonly available option is –prefix. This option allows you to set the base directory where the package gets installed. By default, most packages use /usr/local. Each component in the package will install into the appropriate directory in /usr/local.
With all of the options you want set up, a final run of configure will create a special type of file called a makefile. Makefiles are the foundation of the compilation phase. Generally, if configure fails you will not get a makefile. Make sure that the configure command did indeed complete without any errors.
Compiling Your Package
Compiling your package is the easy part. All you need to do is run make, like so:
[root@ford hello-1.3]# make
The make tool reads all of the makefiles that were created by the configure script. These files tell make which files to compile and the order in which to compile them–which is crucial since there could be hundreds of source files.
Depending on the speed of your system, the available memory, and how busy it is doing other things, the compilation process could take a while to complete, so don't be surprised.
As make is working, it will display each command it is running and all of the parameters associated with it. This output is usually the invocation of the compiler and all of the parameters passed to the compiler—it's pretty tedious stuff that even the programmers were inclined to automate!
If the compile goes through smoothly, you won't see any error messages. Most compiler error messages are very clear and distinct, so don't worry about possibly missing an error. If you do see an error, don't panic. Most error messages don't reflect a problem with the program itself, but usually with the system in some way or another. Typically, these messages are the result of inappropriate file permissions (see the chmod command in Module 6) or files that cannot be found. In the latter case, make sure your path has at the very least the /bin, /sbin, /usr/bin, /usr/sbin, /usr/local/bin, /usr/local/sbin, and /usr/X11R6/bin directories in it. You can see your path by issuing the following command:
[root@ford hello-1.3]# echo $PATH
See Module 6 for information on environment variables so that you can set your path correctly.
In general, slow down and read the error message. Even if the format is a little odd, it may explain what is wrong in plain English, thereby allowing you to quickly fix it. If the error is still confusing, look at the documentation that came with the package to see if there is a mailing list or e-mail address you can contact for help. Most developers are more than happy to provide help, but you need to remember to be nice and to the point. (In other words, don't start an e-mail with a rant about why their software is terrible.)
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Installing the Package and Testing the Software}
As with the compile stage, the installation stage typically goes smoothly. In most cases, once the compile is done, all you need to run is
[root@ford hello-1.3]# make install
This will start the installation script (which is usually embedded in the makefile). Because make displays each command as it is executing it, you will see a lot of text fly by. Don't worry about it–it's perfectly normal. Unless you see an error message, the package is installed.
If you do see an error message, it is most likely because of permissions problems. Look at the last file it was trying to install before failure, and then go check on all the permissions required to place a file there. You may need to use the chmod, chown, and chgrp commands for this step; see Module 6 for additional details.
Testing the Software
A common mistake administrators make is to go through all of the process of configuring and compiling and then when they install they don't test out the software. Testing the software also needs be done as a regular user, if the software is to be used by non-root users. In our example, you run the hello command to verify the permissions are correct and users won't have problems running the program. You will quickly change users to make sure the software is usable by everyone. We'll cover the su command in Module 6.
[root@ford /]# su – sgraham
[sgraham@ford ]-> /usr/local/bin/hello
Hello, world!
[sgraham@ford ]-> exit
[root@ford /]#
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Common Software Problems}
The GNU hello program might not seem like a very useful tool, for the most part I will agree it is not. But one valuable thing it provides is the ability to test the compiler on your system. If you've just finished the task of upgrading your compiler, compiling this simple program will provide a sanity check that indeed the compiler is working.
One problem you might run into is when the program can't find a file of the type "libsomthing.so" and the program terminates because it can't find the file. This file is what is called a library. This is synonymous with DLLs in Windows. These libraries are stored in several locations on the Linux system and typically reside in /usr/lib/ and /usr/local/lib/. If you have installed a software package in a different location than /usr/local you will have to configure your system or shell to know where to look for those new libraries.
NOTE Linux libraries can be located anywhere in your file system. Typically Windows only allows you to store libraries in one location. You'll see that with the use of NFS you can share a directory (in our case, software from one server) and allow any client using that share to use the software residing on the share. With Windows, you're stuck installing the software on each and every machine.
There are two methods for configuring libraries on a Linux system. One is to modify /etc/ld.conf, add the path of your new libraries, and use the ldconfig –m command to load in the new directories. You can also use the LD_LIBRARY_PATH environment variable to hold a list of library directories to look for library files. Read the man page for ld.conf for more information.
Progress Check
1. What is the README file used for? (The README file holds information on how to compile/install and use the software.)
2. What three steps are used to compile a typical GNU software package? (First configure, then make, and then make install.)
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Cleanup and When There is No Configure Script}
Once the package is installed, you can do some cleanup to get rid of all the temporary files created during the installation. Since you have the original source code tarball, it is okay to simply get rid of the entire directory from which you compiled the source code. In the case of the hello program, you would get rid of /usr/local/src/hello-1.3. Begin by going one directory level above the directory you want to remove. In this case, that would be /usr/local/src.
[root@ford hello-1.3]# cd /usr/local/src
Now use the rm command to remove the actual directory, like so:
[root@ford src]# rm -rf hello-1.3
CAUTION The rm command, especially with the -rf parameter, is very dangerous. It recursively removes an entire directory without stopping to verify any of the files. When run by the root user, this has the potential to really cause problems on your system. Be very careful and make sure you are erasing what you mean to erase. There is no "undelete" command. I repeat, there is no "undelete" command.
When There Is No configure Script
Sometimes you will download a package and instantly cd into a directory and run ./configure. And you will probably be shocked when you see the message, "No such file or directory." As stated earlier in the module, read the README and INSTALL files in the distribution. Typically, the authors of the software are courteous enough to provide at least these two files. I don't know how many times I've tried compiling something without first looking at the docs and then come back hours later to find that I missed a step. The first step you take when installing software is to read the documentation. It will probably point out the fact that you need to run imake first, then run make. You get the idea: always read the documentation first, then proceed to compiling the software.
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Compiling and Installing a GNU Program}
In this project, you will download a GNU software package, compile, and install it. I am a big emacs fan, so I am going to show how to download and compile it in this project. emacs most likely already comes standard on a Linux system, as it is a fairly popular editor. As an administrator, you will be exposed to many editors, such as vi, pico, and emacs. You are always guaranteed to have vi on the system. You don't have to install emacs, just pick a package that sounds interesting (stay away from gcc, though)
Step by Step
1. Change your directory to a scratch space that will allow you to compile (typically /usr/local/src).
[root@ford /root ]# cd /usr/local/src
2. Go to the GNU FTP site and download emacs. The latest version as of this writing is emacs-21.2. The software is located at ftp://ftp.gnu.org/gnu/emacs/.
3. Untar the package.
[root@ford /usr/local/src ]# tar -xvzf emacs-21.2.tar.gz
4. cd into the package directory and read the documentation, notably README and INSTALL.
[root@ford /usr/local/src ]# cd emacs-21.2
[root@ford emacs-21.2]# more README
[root@ford emacs-21.2]# more INSTALL
5. Run the configure script with the standard options: –prefix=/usr/local.
[root@ford emacs-21.2]# ./configure –prefix=/usr/local
6. Run make.
[root@ford emacs-21.2]# make
7. If the make completed without any errors, type make install.
[root@ford emacs-21.2]# make install
8. Make sure that you can run the software as both root and a regular user.
[root@ford emacs-21.2]# cd /usr/local/bin
[root@ford bin]# ./emacs
[root@ford bin]# su – sgraham
[sgraham@ford ]-> /usr/local/bin/emacs
[sgraham@ford ]-> exit
[root@ford bin]#
9. Do any cleanup and have a fun time using the software.
[root@ford bin]# cd /usr/local/src/emacs-21.2
[root@ford bin]# make clean
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.
{mospagebreak title=Project Summary}
You have now compiled and installed the emacs editor. I usually leave the source sitting around for a while, just in case I need to make some changes to the software. If you are running low on space you might want to do a make clean in the package directory to clear out any object files (.o) and other files needed for the compilation. Or you can simply delete the directory. Please note that emacs is a fairly big package to download and to compile. On a slow system it can take quite a while to compile. You now know how to download and compile software for your system. Luckily, most software is distributed in the GNU format where you just have to type ./configure, then make, then make install to compile and install the software.
Module 4 Mastery Check
- What is a .gz file?
- What does the tar command do?
- How do you configure a typical GNU software package?
- What file tells make what to do?
- What command would you issue to install the package hello-1.3.i386.rpm?
- What command would you issue to see all the RPM packages installed on your system?
- How would you verify all of the RPM packages on your system?
- What two files should you always look for when installing software?
- You have just gotten done installing some software by hand. As a regular user, you try running the command and it doesn't work the way you thought. What steps would you take in troubleshooting the problem?
- How do you become the root user?
- Name some advantages to using the RPM tool.
- Name some disadvantages to using the RPM tool.
- What does the make program do?
- What does the command make clean do?
- What command would you issue to install the software you just got done compiling?
This chapter is from Linux Administration, A Beginner's Guide, third edition, by Graham and Shah. (McGraw-Hill/Osborne, 2002, ISBN: 0072225629). Check it out at your favorite bookstore today.


text:
Nashville, Tenn. - After falling behind 2-0, the Tennessee State volleyball team couldn't duplicate its comeback win over Belmont on Sept. 28, falling to the Bruins, 0-3 (21-25, 19-25, 23-25).
Sophomore Naomi Wells recorded a double-double for the Tigers (15-13, 9-6 OVC) with a team-high 12 kills to go along with 13 digs.
However, TSU held just a .161 hitting percentage in the match and committed eight service errors.
Sherryce Butler got TSU going with a pair of kills to open the match. She added another two points later to give the Tigers an early 3-1 lead.
The Bruins (14-15, 10-5 OVC) fought back and eventually took a 6-5 lead when an attack from freshman Lindsay Hornsby went long. Hornsby redeemed herself with a kill two points later, but TSU still trailed by one.
Belmont added to its lead later in the first frame when a block attempt by Ambroch backfired, making the score 12-9 in favor of the Bruins. TSU coach Kathy Rouhlac called timeout following the Belmont point. The strategy worked, as TSU rattled off a 6-2 run to take the lead at 15-14.
Following the string of TSU points, Belmont cobbled together a run of its own and eventually made the score 22-17 with the visitors on top.
TSU could only chip away at Belmont's advantage, and the Bruins eventually took the first set with a kill.
Butler once again got TSU off to a hot start with a kill to open the second frame. She then added a block assist and another kill, putting the Tigers in the lead, 5-2.
Just like in set one, Belmont came back from the early deficit and this time, took the lead at 8-7 with a kill. The Bruins eventually padded their cushion to three before TSU called time.
This time, Rouhlac's game plan did nothing to stop the Bruins' run as Belmont added five straight points following the stoppage of play to make the score 16-8.
Erika Moss had a pretty kill later in the period that landed on the line, and Rachel Ambroch added four points down the stretch, but their efforts were not enough as Belmont took set two.
Moss had 36 assists from the setter position and Ambroch had eight kills.
The Tigers only hit .132 in the second period, racking up 13 kills, but committing eight errors.
Butler recorded the opening point of the next set for the third straight time, but the Tigers' time on top of the scoreboard was short-lived at Belmont tallied five of the next six points.
The Tigers came roaring back with a 5-0 run that included kills by freshman Emilie Aase and Wells. The run made the score 7-5 in favor of TSU.
Tennessee State maintained a narrow lead through the next portion of the set, but an error on Hornsby tied the third frame at 15 apiece. Hornsby recorded a kill immediately after the error, and the Tigers were back in the driver's seat.
A 5-2 Belmont run after Hornsby's kill made the score 20-18 with the visitors on top. The sudden outburst by the Bruins caused TSU to burn a timeout, and the Tigers immediately responded with a pair of points to tie the frame.
Each side used a timeout during the final stretch of the set, as the teams traded kills. A final net violation on TSU ended the match.
Hear Naomi Wells' thoughts on the match, below:
The Tigers will travel to SIUE on Nov. 10 to close the regular season before starting the OVC Tournament.
--TSU Tigers--


text:
2014 1099 Form
Creating these legal forms is a common practice in business and is widely accepted. Most business forms that are self created are accepted in court and can be legally upheld as long as both parties have signed the forms. If creating forms seems to be to daunting, than purchasing them can the preferred option.
Planning is an important aspect of creating business forms. It is important to plan what exactly the forms will be used for. There is certain criteria that should be considered. How important is the form? What specifics need to be addressed in the form? A business legal form is usually legally binding so being sure that the form fits all the local rules and requirements is also very important. Coming up with several prototypes is typical when planning a business form. Generating the forms than reviewing the finished product is also a common practice. Ideas during the planning stage can come from different sources. There are a lot of online websites that will provide a sample of various forms, it violates copyright laws to use the form verbatim in most cases, but looking at the form and using the same format is not a violation, and there may be some good ideas that will inspire the creation of the form.
Once the planning stage is complete and feedback has been considered creating the finished product should not be as difficult. Using a word processing program is the best way to create a business form. Setting the format up using the tool bar will insure that everything will be lined up correctly. There is software that is dedicated to creating business forms that also may be an option. The most important aspect in creating business forms is not in the software that is being used but instead with the content of the forms.
There are online options for purchasing business forms. Usually the fee is much lower than purchasing them from a store. Simply typing in the kind of form that is required will result in multiple websites that offer the forms for sale.
There are many stationary stores and office supply stores that carry generic business forms that can be customized to fit any business. There are also ways to customize the forms to even have them reflect the businesses letterhead.


text:
Have you ever had a meeting where you've thought you were being crystal clear with a coworker of the opposite gender, only to find out that you and your coworker are on completely different pages, maybe even different planets? According to "Work with Me: The 8 Blind Spots Between Men and Women in Business," by Barbara Annis and John Challenger (May 2013), 9 percent of men say they understand women, while 68 percent of women say they understand men. That's a big difference and an even bigger gap in understanding.
According to Joanna L. Krotz, The Woman's Playbook, women and men who work closely together often get tied up in communication knots, especially over issues that involve power, advocacy and managing the troops. That's because the sexes have distinct ways of communicating. It's been scientifically shown that the brains of men and women are hardwired differently. Men's brains are typically 10 percent larger than women's and tend to have stronger left-brain skills. Women, on the other hand, typically have more nerve cells in certain areas of the brain and have a larger corpus callosum (connecting the left and right sides of the brain). As a result, men are generally stronger at analytics and abstract concepts, while women are more intuitive, swifter to pick up on nonverbal cues and process information faster.
Hormones and cultural factors also heavily influence how men and women communicate. Women tend to be more people oriented and better at multitasking, while men are better at single-minded focus and top-down motivation, exchanging rewards for results. Male vs. female conversation objectives often differ, as well — for example, status vs. support, report talk vs. rapport talk, independence vs. intimacy, advice vs. understanding, and information vs. feelings.
In this slideshow, Krotz has identified six scenarios where communication between men and women frequently jumps the rails and provides tips for getting back on track.
Related Topics : A Big Market for Big Data Jobs, Midmarket CIO, IT Management Automation, SharePoint, Technology Markets
The gig economy is clearly disrupting the tech industry, both in positive and negative ways. ... More >>
Is fake news a security issue? Some say yes, as it can be used as a social engineering tool to spread disinformation and conceivably to get unsuspecting users to click on malicious links. ... More >>
Executives at several top tech firms outline the skills they need now and in the near future, including IaaS and IoT security expertise. Other skills listed may surprise you. ... More >>


text:
Occupy Wall Street rallies in New York's Zuccotti Park in support of Greek resistance to austerity on February 18, 2012. (Photo: Sunset Parkerpix)
One of the Zuccotti Park protesters, Costas Panayotakis, is an associate professor of sociology at City College of Technology and author of "Remaking Scarcity: From Capitalist Inefficiency to Economic Democracy." "Greece is just a more extreme example of what's going on around Europe and around the world," he said in an interview with Truthout, explaining the impetus behind the solidarity demonstration.Christa Calbos, a student activist who goes to Manhattanville College and who has spent time in Greece, agreed that the solidarity stems from people worldwide seeing their own situation in the Greeks'. "It is important for Americans," she said, "and all citizens of the world fighting against austerity to show solidarity because the challenges Greece now faces are not unique to Greece.""There is a growing global consciousness that has resulted from the crisis," Panayotakis elaborated. "There are global movements. The Occupy movement itself is part of the global movement going back to the occupations in Spain and Athens and even before that, of course, in Tahrir Square in Egypt. There is a global growth in solidarity, because what we have is the failure of global neo-liberalism has become manifest during the crisis and so has the failure of the political and economic elites that have been administering this neo-liberal project."The Greek government, in order to shore up its fiscal health - its debt to private foreign banks is expected to reach 129 percent of the country's gross domestic product in 2020 - has repeatedly had to accept bailouts from the International Monetary Fund (IMF) and the German-run European Central Bank (ECB). The austerity the IMF and ECB insist on imposing as a condition of the bailouts resembles similar measures imposed throughout the global South in recent decades - privatization of the commons, deep cuts to social services, dismemberment of labor unions, the imposition of a greatly lowered standard of living on the average Greek citizen. Calbos noted this similarity. "These words that have become so common after the start of OWS such as 'austerity,' 'free market,' 'bail-outs,' 'debt relief.' The true meaning and impact of these words have been understood and felt within the developing world for decades. Countries in Africa, Latin America, and Asia have been bailed out - or bought out rather - by the IMF, World Bank, and other international financial institutions. When this happens, of course, it does away with a truly democratic government and any form of public social services."Panayotakis indicated that these phenomena are closer to home than the third world, saying, "There is a very brutal assault on people's living standards. There is a liquidation of labor rights that go back more than 50 years. And of course we've seen similar kinds of things going on even in the U.S., with the attack on labor rights of the public sector workers in Wisconsin and other parts of the country."This bringing-home of third-world conditions has ignited a radical spirit here, said Calbos. "It was easy for the west and the 1% to stomach this happening in the developing world," she said. "They could paternalistically blame it on lack of education. However, Greece has suddenly now shown us that the white, western, middle class is not immune to the damaging effects of the neo-liberal economic system. This should be a wake up call, a call to action, a perfect example of how capitalism and democracy are not inextricably intertwined but rather at odds with each other."Almost no one in Greek society has suffered during the past few years as desperately as students. Said Calbos, "Students in Greece are at the heart of resistance, and I believe this is also important to the Occupy movement here in the U.S. In Greece, 50% of the population under 25 is currently unemployed. With incredible student debt, tuition hikes, and an ever-difficult job market, we in the U.S are facing many of the same obstacles."Rather than defaulting on the banks, the Greek government has decided to default on its people. "Basically there is an effort to push the cost of the crisis on the people least responsible for it," said Panayotakis. "The priority in responding to the crisis has been to protect the banks and the financial sector. This is what we see in Greece and in Europe and the people who get penalized the most are ordinary workers and ordinary citizens."Greece, where democracy originated, was thrust into so deep a crisis by the financial crash that it abandoned democracy, turning its government over to a "technocrat" (read: banker), Lucas Papademos, formerly an ECB vice president. The result of this bloodless coup (i.e. whether Papademos' government can bring Greece back from the precipice of collapse) will reverberate worldwide, said Panayotakis. "What happens in Greece, of course, has great repercussions obviously for the European economy and, via the European economy, on the American economy and therefore the global economy." This largely depends on the willingness of the German government, the economy of which is still strong, to help out, he explained. "There is a joke that the most dangerous opponent of President Obama is Angela Merkel. Her policies are threatening to basically throw the European economy into a meltdown, which of course would affect the rest of the world."And the whole world, they say, is watching.
This work by Truthout is licensed under a Creative Commons Attribution-Noncommercial 3.0 United States License.


text:
Love & Hip Hop NY Episode 6 Best Moments: Kaylin Vs Tahiry And Mendeecees Vs Yandy's Cousin… CATCH FADE!! [Video]
Raqi talks to Yandy about her fight with Jen and dragging Consequence into the argument.
Raqi visits Cons to apologize for dragging him into her fight with Jen, but Cons does not accept.
Lore'l talks with her manager, Angela Yee, about her frustrations with her music career.
Tahiry and Kaylin get into a nasty argument in Joe's dressing room before his show.
Erica confronts Rich about her stalled music video project for the song she just recorded.
Mendeecees confronts Yandy's cousin, Maurice, about the gym pictures he took of Yandy and the confrontation ends in a major blowout.
Continue Slideshow
Yandy laughs at being checked by Mendeecees while Tahiry gets excited about her fight with Kaylin, but Joe calls them both selfish.
Jen talks to Cons about finding time in his schedule to help her interview babysitters.
When Joe tries to calm Kaylin down after the fight with Tahiry, Kaylin goes into defense mode.
While out shopping with their son, Caiden, Jen talks to Cons about how the argument with Raqi is still bugging her.
More Stories From Bossip
Bossip Comment Policy
Please read our Comment Policy before commenting.


text:
Stafford Boy Playing with Tiki Torch Fluid Flown to Burn Center
hAn 11-year-old Stafford boy is flown a Philadelphia burn center with second and third degree burns after playing with tiki torch lighter fluid.
Township Police say the incident occured early Tuesday evening in the backyard of his Ocean Acres home on Atlantis Avenue. According to the Asbury Park Press, the boy, who was with his 12-year-old brother at the time, spilled the lighter fluid on his leg and rib cage when it ignited. The boy's mother called 9-1-1.