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.
Distribution: Red Hat Enterprise Workstation, Debian, Simply Mepis, Damn Small Linux
I'll take a not-working-so-well copy of Linux over a working perfectly copy of winodoze (is there such an animal?!) any day! Since I started using Linux, I've been challenged and force to use my hatrack more than I ever was with windoze. Besides, from what I've seen so far, forums like this, where users help each other, works out MUCH better than trying to call some tech support guy that's only concerned about whether he'll get his lunch break on time ( half the time, they don't speak your language very well, if at all, either). That's one of the things that makes Linux great - we work together to achieve common goals, fix the things that are broke, and make better the things that work. Sorry for the speach!
rafc: Gentoo's portage system can let anyone compile from source (altho knowing how to do it yourself, and how compiling works helps a lot)
the only time i ever got a broken package in Gentoo was in bootstraping it (it seems to be random, most of the time glibc doesn't compile right, so when its installed it breaks everything and portage errors out, but it works if you try it enough )
and the dependency's are mostly the precompiled packages, as the package was compiled on a system and expects to find that same system on your machine (by system i mean compiled libs, if it is a different version, it might be incompatible)
compiling from source solves this as the package will be compiled it will link up with your system and not force you to have like 3 versions of the same library just to run a few apps
in windows there isn't much of a problem as everything is the same (and thus why viruses/worms will can spread from computer to another one and still work,, in linux a virus/worm will probably run into dependency issues on quite a few systems (and who said dependence problems were a bad thing ? ))
Originally posted by rafc If you install from source you have to be very knowledgeable about what you need and can let go.
I disagree - you can be much less knowlegeable - i.e. you need only version x.y.z or above of a particular library rather than exactly version x.y.z as you would with RPM's. If anything this means that using make or configure scripts is likely to throw up fewer dependency problems as often with RPM's they complain about needing a version of a library older than the currently installed one.
I find that as long as I'm putting libraries likely to be used by more than one application into /usr/lib then I have very few dependency problems...usually none unless the app happens to use some proprietry and rare graphics or parsing library.
Autonomy is a good thing, mankind has had a few
Fuehrers too many already.
Sure, but the problem is not anyone has the time or will to be completely autonomous about everything.
Most of the time I just want things working in order to be productive, and only be knowledgeable about some specific things I'm interested in. Being confronted with broken dependencies, update hell etc and days reading manuals in order to find a possible solution to one of 10 problems encountered is not one of them.
I think we should aim for a system of principal autonomy: everyone can decide to have the amount of autonomy one likes in anything he likes. And others should be able to trust upon the realisations they do, being able to control their work when needed, but generally do their thing having a reliable backing in other areas.
And I am not troubled because some things don't work. But for now, everything brakes every time I do a simple apt-get eg. And that's really frustrating, not having a workable desktop anymore, no links working anymore etc.
I think things could be made easier for the general user., who just like to have things to work and be more knowledgeable eg in tweaking their desktop look under the hood (not in resolving a broken system).