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 purchased a Newegg combo (case, power supply, mother board, CPU, hard drives, and DVD burner) with the intent of running Linux on it. I have taken the Test on Linux Distribution Chooser and will probably go with Ubuntu. Is there a place to go for advise from others who have already put together a Newegg combo with Linux?
No problem, I have built several systems from Newegg parts. You did not specify whether the Motherboards is UEFI.
I would get a good diagnostic like SystemRescueCD;
SystemRescueCd <- 'is a Linux system on a bootable CD-ROM for repairing your system and recovering your data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the partitions of the hard disk. It contains a lot of system utilities (parted, partimage, fstools, ...) and basic tools (editors, midnight commander, network tools).' + 'Online-Manual
That way you can use memtest86+ to verify memory without errors. You will have several other diagnostics on the SystemRescueCD to help you with the build. I do not use Ubuntu but it seems a UEFI install is doable.
The choice is yours. I am not a fan of hold your hand distributions. I use Slackware and have been using Slackware since it was first released. Slackware's 21st birthday was on July 16,2014. Oldest active distribution still in use. Once you slack you will find a stable machine so why choose something else.
LiveCD would be a way to test drive on the new hardware. Look at;
LiveCD: The LiveCD List <- Very Good List LiveCD Wiki <- 'Good detailed explanation plus resource' Live USB: Live USB_Wiki <- 'A live USB is a USB flash drive or a USB external hard disk drive containing a full operating system which can be booted. Live USBs are closely related to live CDs, but typically have the ability to save settings and permanently install software packages back onto the USB device.' + 'system administration, data recovery method' + includes distribution table reference
Hope this helps.
Have fun & enjoy!
Last edited by onebuck; 07-22-2014 at 05:37 PM.
The only suggestion I have is to double check the motherboard.
Frequently there are a number of embedded controllers that say "linux compatible" but aren't really. This shouldn't be a problem for most controllers - but some have a "raid" controller in front of the SCSI controllers, and you can't always bypass the raid controller to get direct access to the SCSI (this was my problem). Fortunately, my motherboard also had 5 SATA connections that I could use in place of the 8 SAS connections (provided through the unusable RAID controller).
I suggest that you create a written system log at the start. Document all the specs for component manufacture model, Serial number along with device specifications. That way you will have on hand information that can be of use in the future. I even document the BIOS information, version, build and type under the motherboard specifications. You can extend the system log as the the build progresses whenever you encounter issues and then placing the solution within the log. I use college ruled 70 page spiral notebooks that cost me <$.25/spiral during Walmart's school sales. I will number each page, do not remove or erase errors, just line out then initial with time stamp. This technique is used throughout industry to document. Lab books are one area this is used to document issues/results with LAB stations. That way anyone can read the entries to get a feel for the status of a station. The same is true for a computer system.
By documenting each system you will have good library of information that does not rely on your memory for a way to trail things. This technique has saved me more than once.
Excellent advice -- I'll definitely follow it to the letter. Already have some ruled spiral notebooks that we bought for my grandaughter many years ago and she later returned to us unused. Now I have a good use for at least one of them. I know it will surely pay big in the long run. Thank you!