Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i have to make an rpm for our software and install it on another linux
i have created the following .spec file for it....
%define name dashboard
%define version 2.0.1
%define release 1mdk
Summary: Tools for converting websites from using GIFs to using PNGs
The broken pipe error is caused when the output of a program (A) is being send to another program (B). Program B is exiting (crashing) before program A has finished producing all its data.
A problem with your .spec file shouldn't cause this problem. One possibility is a bug in your RPM tools; make sure that you have installed any available updates.
Given that the problem is intermittent, the most likely explanation here, I'm afraid, is a hardware problem. This kind of error (one program crashing intermittently) is most commonly caused by an intermittent fault in your hardware; RAM being the most common culprit, followed by an overclocked CPU. You might try running a decent RAM tester for a few hours. Another test you can do is attempt to compile a complex program like gcc from source (gcc uses lots of pointers so it tends to break if your RAM isn't working too well); it should get through the compile process in one go. If it fails intermittently, but then fails at a different point after reissuing the make command, then you know your memory isn't good.