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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
With all due respect, you did not edit your Master Boot Record. You used the BIOS setup utility to edit your CMOS memory where the boot order of your drives is stored. The Master Boot Record is the first sector of your hard drive, and there are probably remnants of an old Windows boot loader there. jefro's suggestion is a good one, and you should go ahead and try it.
GVrooman,
Thank you for the correction. I realized my mistake once you pointed it out.
The MBR is what the BIOS loads, not what devise is used to boot at start up. Partitioned disks, OS directories and such are part of the MBR.
Thanks again for the correction.
Shaun
Quote:
The BIOS is booting the hard drive. Probably you correctly changed the boot sequence, but incorrectly burned the CD, so the BIOS looks at the CD first, sees it is incorrect, skips it and then boots the hard drive.
I do believe you are correct in assuming that I burned the image incorrectly. I remember burning it as data, not an image. I will correct it. Thank you.
Quote:
We are providing help. You should be looking for help, not respect. You made incorrect statements that indicate misunderstandings that interfere with your ability to reach the solution. It is helpful to try to correct your misunderstandings. It is respectful to treat your incorrect beliefs as equally valid with correct beliefs, and leave you unable to solve the problem. If you want the second of those choices, you're in the wrong forum.
However,
You do not provide help by being a pedantic jerk. Respect should be mutual. I have not gotten where I have in my professional capacity by using my knowledge as a battering ram against others who do not have the same degree of experience or knowledge in a particular area.
If you do not agree with that philosophy then avoid me, as I will you. If the community does not share that philosophy, you are probably right I am in the wrong place.
The comment was directed to an individual(not you) that made a crass comment. It has been handled, in my opinion, and I will be moving on from that incident.
Otherwise, I appreciate everything that you have helped me with. I will continue to seek out this forums help and advise. There are a lot of knowledgeable individuals here, including yourself. I look forward to learning, understanding, and eventually becoming a subject matter expert in Linux/UNIX.
Thank you all.
Last edited by smturner1; 05-14-2011 at 09:00 AM.
Click here to see the post LQ members have rated as the most helpful post in this thread.
One other option, if burning/reading a bootable CD or DVD is problematic, is to make a bootable USB stick instead. Here are several (fairly easy/robust) alternatives:
I do have another question ,I am a System Admin at a Telecom and have recently acquired a position that requires me to monitor systems that are UNIX based. I did have a couple of classes in my undergrad that briefly covered Linux/UNIX, but as you can see it was a while ago and basically covered file systems, chmod, file/directory manipulation and some sh.
The OS's that I am working with are strictly CLI. I run commands, build basic scripts, and trouble-shoot the equipment and software remotely. What I am getting at is, based on my lack of experience, but the urgency to learn and the fact that I am in front of these systems 40 hours a week, which Linux Distro (in your opinion) would be better than what I am currently using.....Arch?
I do have another question ,I am a System Admin at a Telecom and have recently acquired a position that requires me to monitor systems that are UNIX based. I did have a couple of classes in my undergrad that briefly covered Linux/UNIX, but as you can see it was a while ago and basically covered file systems, chmod, file/directory manipulation and some sh.
The OS's that I am working with are strictly CLI. I run commands, build basic scripts, and trouble-shoot the equipment and software remotely. What I am getting at is, based on my lack of experience, but the urgency to learn and the fact that I am in front of these systems 40 hours a week, which Linux Distro (in your opinion) would be better than what I am currently using.....Arch?
Thx,
Shaun
Probably best to move this to a new thread.
However, since I'm already responding, I'll address your question - my answer is none. All the major distros (except those designed to work on very RAM-limited systems) will include or make readily available a full set of CLI tools.
Distribution: Slackware 13.1, Windows 7 (on game box only), Mac OSX
Posts: 18
Rep:
Quote:
Originally Posted by smturner1
I do have another question ,I am a System Admin at a Telecom and have recently acquired a position that requires me to monitor systems that are UNIX based. I did have a couple of classes in my undergrad that briefly covered Linux/UNIX, but as you can see it was a while ago and basically covered file systems, chmod, file/directory manipulation and some sh.
The OS's that I am working with are strictly CLI. I run commands, build basic scripts, and trouble-shoot the equipment and software remotely. What I am getting at is, based on my lack of experience, but the urgency to learn and the fact that I am in front of these systems 40 hours a week, which Linux Distro (in your opinion) would be better than what I am currently using.....Arch?
Thx,
Shaun
Slackware is nice because it doesn't have a lot of shiny objects to divert your attention.
I hope that is not a provisioning or billing system you are monkeying with!
I'm glad you're squared away, and I sincerely apologize. It's great to have you as part of LQ, and I hope your experience here is favorable and productive.
Sincerely .. PSM
PS:
I have absolutely no recommendations for one distro over another. It's either a matter of necessity (whatever OS your company/organization happens to be using), or preference (there are many, many excellent choices available to you).
Please feel free to post back with any specific questions you might have about any of those choices.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.