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.
To be fair to MS, the registry sounds like quite a good idea on paper.
A single system-wide repository of config data, with the ability to merge configuration sets without major (sed/grep/awk)-foo and a consistent API sounds pretty convincing.
I'll be sticking with flat text files myself, though. gconf, registry et al might be nice for developers, but they're a royal pain in the ass for users and admins on a day to day basis.
A centralized thing might sound like a good thing, on papers, as you say. But there's a lot of factors that would make this insanely complicated in linux
First, you would need an universal language. I've seen lots of threads talking about this in many forums. Some preople propose a standard based on xml tags, others like tabular text files. The plain truth is that each program has it's propers config format, and for a good reason.
Some config files are intended to be sourced on a shell at some point, so, using any other formated kind of file wouldn't work, since here you need shell syntax, and adding another layer would just overcomplicate the things
This same syntax is not suitable for some other things. And here the discussion could continue for years without the people agreeing. Definitely, I don't want my configs on binary files. If we had a registry alike, I'd vote for a plain text format, like xml. But if nothing is moving in that direction, it's maybe because no one has found a solution that is practical on the real world, and not just on papers.
Whatever it is, I'd prefer this hypothetical new solution to be file system based. If anything, I'd like a standard config file format, but a separate file (and dirs) for everything. I don't want a massive registry file. I never liked that idea.
Lost of efforts are dedicated to standarize some desktop related things, but none is interested in standarizing config files, because:
1.- they are most times trivial to use and understand
2.- they are accessible, even on minimal environments when everything is broken
3.- people is just used to them
And in all honesty, in Windoze I think the regristry just kind of took on a life of its own and outgrew what it was meant to do. Like when you see a cluttered office and the person says don't touch anything I know where everything is, even though its a huge mess. I think the users just adapted to the centralized system because they didn't have a choice. I think that system would work better if it could work without the user having to go in and change anything, because it becomes very confusing very quickly. And god forbid you forget to back up the registry first.
Hi there, I think you are getting confused about the link in here, this guy was editing his Windows registry, using Linux, on a dual boot machine. He was not editing a Linux registry, since such a thing does not exist.
thanks for the wine clarification! I knew wine was like an emulator that lets me run some win apps however I didn't know it came bundled with a ver of the registry (i just noticed it has a lot less values than a regular win system)
btw the REGISTRY IS A NIGHTMARE!!!!
Why waste time with the horrible WinDuhs registry? The old UNIX text configuration files are much easier to understand, are easily annotated, and you don't have to reinstall all your software if you accidentally screw up one configuration file.
...agreed 100%...get used to this system an you'll wonder why on earth anyone would invent the Windows registry
I think MS invented the registry to obscure operations from the users.
...although I disagree with that, slightly. I think it was part of an M$ campaign (around NT 4, if I remember correctly) to obfuscate the system as far as software suppliers were concerned. At that point, if you remember, it wasn't necessarily a done deal that M$ Office would win out over, for example, WordPerfect, and it was necessary for M$ to give its in-house program whatever edge they could over other software suppliers, so that they could cash in off both the Office package and the OS. (It was particularly not a done deal in the sense that early versions of both M$ Office and competing programs were crap, and the right solution wasn't yet apparent.)
The other part of that was making the OS as difficult to write good software for as possible (including hiding system calls, poor documentation of the registry, etc.). Of course this also gave rise to a situation which the reputation of windows was worsened (you may not believe this is possible...) by badly written apps, but, if you are M$, you probably think that job of selling Office against WordPathetic is now done and they don't have to be so 'hard line' any more, but, for a while, it was a tricky line to walk.
Part was also convincing independant software suppiers that OS2 was the future, and having sold them the dummy, and wrong footed them, it left the field clear for M$ for a time and a time was all M$ needed.
wine: created the configuration directory '/home/cesar/.wine'
Could not load Mozilla. HTML rendering will be disabled.
wine: configuration in '/home/cesar/.wine' has been updated.
and the Windows registry opened!!! is it because I have a dual boot system so linux opens the windows registry?
The WINE registry is nothing like the WinDuhs registry - information is stored in multiple files (you might compare that with a Microsoft 'hive') but it is all in text and not in binary. Have a look at the files with the settings for your favorite WinDuhs app.
Unix has been evolving since 1971
Linux was based on Unix it has all that evolution in it
the best way to handle the complexities evolved in a multi user multi tasking O/S
is modulation break the system up in to smaller parts
partly because not all systems will need all parts that could be added
( for example most file servers don't have a gui )
mostly because a problem in one part should never ever never cause a problem in another part
so the configuration files are broken up this configuration file for this part another for that part
why use plain text because humans can read plain text ( plain and simple )
etc stands for 'editable text configuration', which pretty much sums the files in this directory, despite a few exceptions such as 'shadow' and 'sudoers'. This directory was part of Kenneth Thompson's original Unix and has remained in all 'nixes ever since. So it must be doing something right!.
They did not make all that money developing basic technology or the best SW designs. MS is basically a marketing company.
I agree with you about that. But as much as we can debate it, you can't change the fact that they developed a stranglehold on the market, and in America it doesn't matter what kind of junk you put out as long as you can sell it. And lets be honest, mixed in with the garbage they've put out, there has been some good software and some really good ideas.