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.
Originally posted by Crashed_Again Have you checked that the cables are properly seated?
Have you checked that the power cables are properly seated?
Have you flashed the BIOS?
Arggggg just send me a new freakin hard drive!
Tell me about it. Dell were OK with me the last time - Next day delivery for a new hotswap PSU under warranty.
The worst system we have is Novell. It runs our mail server. (We are currently building a new linux one ) The "latest" problem with Novell is that we can't add user accounts. The name appears but the users database files aren't created. This has been on the go for about 2 months now. Accounts are sometimes created when the system restarts so we can "just" add new users. Our support company have had us rebuilding database files and repairing dictionary files etc etc. Now after 2 months their latest idea is to. Wait for it... "reinstall".
The other problem we have is with changing passwords. Im not sure if you have used Novell but you can access your mail using:
The last 2 are propriatry. This used to work but now - when you change a users password they can't log in to pop, imap or WebAccess. This is despite the fact that they all use the same password file (or so I'm told).
The annoying thing is that "GroupWise" is a horrible piece of software that crashes PCs and we therefore don't use it. So to change the user password we need to change it in nwadmin (Novell admin utility), then login as the user and change their password "again" for them. After changing it the second time they can login by any means they want.
whew - that was a long post! Who knows maybe there is a Novell junkie hanging about that can figure it out
I worked for 6 months at a court house helping them migrate to a Windows2000 network. I saw some books on GroupWise and I asked them about it. They all cringed at the word. They had gotten rid of it right before I got there.
I don't blame them. I think our server may be going for a new record. I haven't had to reboot it for over a week
I work for the NHS and one of my colleagues has just moved to a different area and now works for their IT department. I spoke to him yesterday and they have 18 (yes eighteen) Novell servers ranging from Novell 3 to Novell 6. I was joking with him that they must employ someone just to reboot them. Then he told me that the week before he started the "root" server had crashed the and in turn all the other servers lost time and crashed too
I think the Novell philosophy must be "fallover" rather than "failover".