Other *NIXThis forum is for the discussion of any UNIX platform that does not have its own forum. Examples would include HP-UX, IRIX, Darwin, Tru64 and OS X.
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.
That would depend on what the heck "Unix 7" is. Do you mean UnixWare 7?
The answer is likely that there were almost certainly "dependencies" but that such dependencies may not have been labeled that way. (For example many package management systems have "prerequisites".) Also most commercial UNIX products are sold as an overall package so the dependencies are installed with the base OS on the expectation you'll be using something somewhat monolithic. Many have package updates that do have "dependencies" on other package updates being in place but again may not call them that (e.g. they might call them "corequisites").
I have not the pleasure of understanding you. To the extent that anything uses libraries it has dependencies.
In the early days things were much different. I've seen a system from 1974 - no dns, but /etc/hosts held the entire internet. It was a 200k file. How things have changed. In 1974 they had libs, and a libc which was needed for any output.
Yes. It too releases updates for various items it contains. Some of these are one offs to fix specific bugs or security issues. For XP they also created "Service Packs" that had a plethora of changes so you might be running XP SP1, XP SP2 or XP SP3. Of course Windows is NOT *nix variant - except that old AT&Ters [AT&T originated UNIX] I knew used to say MSDOS stood for:
S tole our
And windows is based on DOS.
Last edited by MensaWater; 10-29-2010 at 09:56 AM.
"GNU/Linux-like dependencies" means that package A depends on package B and can't work without it.
Okay, so the answer would be no as there was not yet any notion of software packaging (i.e. standardized way to bundle software including metadata) when version 7 was used. The common way to send software was to use tarballs (tar was precisely introduced with Unix v7) and possibly "shar" files, but maybe that was created later.
Can you call it "libraries" - I don't know...
Dependencies aren't necessarily libraries, they can be anything required for a piece of software to work. With Unix v7, as already stated, there was no shared libraries either so software was always linked with the required libraries.
Only very loosely anymore. The days of true DOS-based Windows pretty much ended when Windows 2000/XP came around. Everything is NT-based now, and NT is a different system from DOS entirely. For example, Win 3.1/95 used cooperative multitasking (i.e. non-preemptive; programs had to free resources on their own. This is why the whole system locked up when one program crashed), as DOS didn't support *real* multitasking at the time. Win NT 3.1 and up use the NT kernel, which has preemptive multitasking and memory protection (i.e. programs can't write into/access other programs' memory, etc.).
...Linux (and other UNIX-likes) on the other hand have always had real multitasking.
Maybe but you still don't have any real control over things until you drop to CMD prompt and that looks very much like the old DOS window.
However, when I said "based on" I meant it started there. Even a UNIX fan boy like me would never say that even XP was as bad as say Windows 95 let alone something like Windows 2. I remember back when I still did a lot of work on DOS I inherited a system that had Windows 2 loaded on top of DOS (the way it was done in those days). After tinkering with it for about an hour I modified the autoexec.bat to prevent it from loading "that useless Windows stuff". It wasn't until I joined a company that was using 3.11 on desktops that I started using Windows with any regularity. Even then it was mainly to launch Exceed to get to my lovely UNIX systems.