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.
Hey that sounds good to me, I have tried current before, and I told it to update to current, but there is probably something I missed. There is most likely something somewhere that I would have to tell for all the updates to step into effect. Yeah, us men just don't read directions LOL. I think I will try to read a bit more about it though, so I can get Slackware Current. Well, it's off to installing stupid Windows XP Pro and then Slackware 9.1 (then hopefully upgrade to Current).
Thanks for all of your help!
(I created a new thread about swaret b/c it doesn't really belong in this thread, but you gave me an answer about it that I "wanted" to hear so thanks!)
Yet another option, how about using NTLDR to boot Linux? You'll still need to install a boot loader on the Linux boot partition to get this to work, but you can leave your MBR alone. Here is a set of instructions for you to peruse http://www.geocities.com/epark/linux...2k-HOWTO.html. There are a lot of other sites out there that cover this. Just use google and search for ntldr boot linux.
Yes, you can switch boot loaders on a whim, but once you get a boot loader working there really isn't much need to do so unless you feel like becoming the next expert boot loader loader.
Interestingly enough I have three computers and they all use a different loader (LILO, NTLDR, and GRUB). I tried out the NTLDR method after correcting a problem with my MBR and wiping out GRUB during the fix. I knew I could get GRUB to work again, but thought I would experiment with NTLDR. Low and behold it worked the first time and I decided to keep it in place. Be sure and let us know how things turn out.
Hey, I did the setup I mentioned earlier, Windows on HDE1, SWAP on HDE2, "/" on HDE3, and "/home" on HDE4. LILO works fine now, YAY!!! NTLoader is just the windows loader right? I know how to do that one and I don't like it (if it is the one you're talking about). I think I will give GRUB a try, just to see the diffence, but LILO is really easy.
Congrats! Must feel good to finally get it working and booting without a boot disk. Yes, NTLDR is the windows loader. I would agree that it doesn't give you the kind of flexibility that LILO and GRUB have.
LOL yeah I think I did leave Slackware on the 200GB hard drive, I might do that to recover some of the old stuff. I have KDE 3.2.2 now, OMG it looks so much better than 3.1.4, who would have ever believed it. Almost like going from Windows 98/ME to Windowx XP, looks great. I can't thank you enough vectordrake for helping me out so much.
And yes it does feel great not having to use that stupid boot disk. The resolution is higher too, 1024x768, loads much faster, and I see the penguin!
ha ha! Yeah! BTW, 3.2 has a cute eye candy thing that I just love - bouncing busy cursor! I know its silly, but I love watching that bouncy icon instead of the blinky one of past (you have to enable it, of course)
I was thinking that if you wanted to wait to add the old install to your lilo config, you could add the partitions to your /etc/fstab, so that you could have them mounted and accessible at boot. Perhaps you'll just wipe 'em after all, but you have time to do that.
Ohhhhh, that's how you mount drives at boot!!! I've been wanting to do that, thanks for the tip. Now I have a really embarrassing problem... Last time I installed Slackware, my mouse didn't work at start, so I searched online and found out that if you edit your XF86Config file, by either browsing to it or using the xf86config wizard, that you can get your mouse working in there. I have the same mouse this time as I did last time, a Logitech Mx700 (a wireless optical mouse) and it is connected via USB. Last time, I got my mouse working no problem, I guess I chose the correct options the first time through, this time I have ran through xf86config so many times and I have been tryin all day to get my mouse to work. I've done several searches here and on google and everything I've found isn't working for me. Also, unfortunately I decided to delete my old Slackware installation (when I was installing the new one on /dev/hde). I know my mouse is working, batteries are full and it works on Windows XP. I just wonder what I am doing wrong this time around...
If anyone can help, I appreciate it very much. Also, the following post is my XF86Config for my mouse.
# Identifier and driver
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Also, I have just thought of something.. Last time I don't think I had Hotplug enabled and this time I remember that I enabled it during the installation. Maybe that could be the problem...?
VECTORDRAKE!!! I'm sorry but can you be anymore of "THE MAN"??? You are too freaking awesome! When I read your reply, I thought to myself, I doubt that will work. IT WORKED!!! I am in such disbelief right now. You are my favorite person in Linuxquestions.org, you have helped me out so much!
This would be the color of my face right now. I'm glad you're back in the saddle! BTW, if you're nuts enough to go with the latest kernel and KDE, you're gonna be surprised by the performance difference. I just pointed my sources at "Cooker" instead of "Official", so now I am getting the freshest Mandrake stuff. I have kernel 2.6.7 rc1 and KDE 3.2.2 loaded up right now. aRTs decided to crash, but I'm gonna try to downgrade it and see if I can get DKE sound sooner than later (although Cooker is quick like Debian Sid - it won't be broken for long). I can't believe the difference in response between 2.6.3-13/KDE 3.2.1 and the newer stuff. Wow, 2004 is gonna be a good year for the penguin.