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 have been trying to get Win98, W2000, and Linux on one system for I while and finally thought I had succeeded.
However, now win2000 is as slow as it would be on a x386. I think this is because it cannot access the ext3 partitions, although it can see them. I was wondering whether any of you could assist here.
The setup I use is as follows:
device size(MB) type drive:label
/dev/hda1 10001 vfat C:win98
/dev/hda2 66284 extended
/dev/hda5 10001 vfat D:data
/dev/hda6 10001 vfat E:misc
/dev/hda7 10001 ntfs H:w2000
/dev/hda8 47 ext3 RedHat/boot
/dev/hda9 34703 ext3 RedHat/
/dev/hda10 1530 swap Redhat/swap
Grub is installed in MBR and provides options: a) RedHat b) Windows. When b), NTbootLoader starts and provides options 1)Win2000, 2) Win98.
So I can access all OS. When W2000 boots the hdd rattles more than usual and several minutes pass (AMD 1.4GHz processor). When finally it is booted is seems not too bad, but when I open DiskManager (like to assign drive letters) it stallls and prompts because of timeouts. Finally the partitions will be shown.
Is there any way to make W2000 realize it should not bother with those Linux partitions? Should I perhaps create these partitions as Non-Dos with FDISK?
I realize one could use something like Partition Magic, but if there would be a solution without such a utility, that would be prefered.
IMNSHO this is a bad question because it handles *wintendo* probs on a Linux board.
AFAIK, Diskmanager loads up some services (can't remember the names right now) that query the drives for volume, status, performance and whatnot pointers slowing it down when starting, but when an Ext(2|3) partition is found it should show as a grey block, wintendo(2K) doesn't bother with partitions it doesn't recognize, and you should not try to mess with it in Diskmanager.
Every thing was fine with Red hat linux 7.2 When I installed 8.0 version I started getting the same problem that Alan reported.
I've linux and win2000 installed on seperate hard drives. I tried to disable the drive in Bios but still did not solve the problem.
In the event viewer there is a warning that say:
"WMI ADAP was unable to process the perfdisk performance library due to a time violation in open function."
In the meantime I found a solution/workaround for this problem.
Apparantly, W2000 cannot cope with partitions made by the Linux installer.
So what I did, is have the Linux installer show how it would make the partitions, write this info down and abort the install. Then in Windows 2000, make the partitions (exaclty as the install program suggested) with My Computer -> Manage -> Disk Management ...
Then it all worked like a charm.
Hope this helps.
(What exactly causes this problem is beyond my understanding of the OS-es, but I'm guessing that the information written in the MBR are is not exactly the same when partitions are created by DIskDruid or Win2000)