Installing Linux on Windows XP AMD 64 - Risks & Setup

  • Thread starter Thread starter franznietzsche
  • Start date Start date
  • Tags Tags
    Linux Windows
Click For Summary
SUMMARY

The discussion centers on installing Linux, specifically Mandrake 10, on a Windows XP AMD 64 system with a 200 GB SATA hard drive. The user plans to allocate a 20 GB partition for Linux while keeping the existing Windows installation intact. Key concerns include potential risks during partitioning, the setup of Linux directories, and the reliability of Mandrake's built-in partitioning tool. Recommendations suggest using Fedora Core 3 for its user-friendly interface and robust package management, along with the importance of backing up data before proceeding with the installation.

PREREQUISITES
  • Understanding of partitioning concepts and tools, specifically using Mandrake's partitioning interface.
  • Familiarity with Linux directory structures, including /, /home, and /boot partitions.
  • Knowledge of dual-boot configurations, particularly with GRUB bootloader.
  • Basic understanding of Linux distributions, especially Fedora and Mandrake.
NEXT STEPS
  • Research how to safely partition a hard drive using tools like GParted or Partition Magic.
  • Learn about configuring GRUB for dual-booting Windows and Linux systems.
  • Explore Fedora Core 3 installation guides and its package management system.
  • Investigate the installation and usage of Intel's FORTRAN compiler on Linux.
USEFUL FOR

Individuals interested in dual-booting Windows and Linux, particularly programmers and students seeking a UNIX-compatible environment for development. This discussion is beneficial for those considering using Fedora or Mandrake for their Linux installations.

Computer science news on Phys.org
  • #32
graphic7 said:
As I recall, Intel only offers their compilers in an RPM package install format. I could be wrong, but if this is true, then an RPM-based distribution like Fedora or SuSE will be your only choice. If you do choose to run, say a Debian-based package distribution, conversion utilities do exist to convert the RPM to the native package format, however, I would not put too much faith in those.

Gentoo's portage offers intel's compiler for both C++ and Fortran:

http://www.gentoo-portage.com/s?search=intel+compiler
 
Last edited by a moderator:
  • #33
franznietzsche said:
Well I'm currently posting while running under Fedora, haven't tried booting to windows yet though.

I gave the root 5 Gb, same for boot, swap 1 Gb (i have 768 Mb of RAM) and about 40 to /home.

Up and running fine, though i need to find printer drivers, my printer wasn't listed in the list that came up at startup (not sure why)and the disc only has Mac and Windows drivers.

I will have to agree with gerben and say that your boot parition is WAY too big. Mine is 32MB, but you could go smaller depending on how many kernel versions you keep around.
 
  • #34
franznietzsche said:
Well I'm currently posting while running under Fedora, haven't tried booting to windows yet though.

I gave the root 5 Gb, same for boot, swap 1 Gb (i have 768 Mb of RAM) and about 40 to /home.

Up and running fine, though i need to find printer drivers, my printer wasn't listed in the list that came up at startup (not sure why)and the disc only has Mac and Windows drivers.

You won't find any printer drivers for UNIX/Linux on the CD or the manufacturer's site. Find out if the printer is a 'Postscript' printer. If this is true, getting it supported by LPD or Cups will be a simple matter. As I recall, there's a KDE app that configures Cups. You could go ahead and attempt to configure it using this app, and see if the printer is on the list.

Not all printers are Postscript. I bought a printer made in 94' or 95' by Lexmark; it upon non-Postscript and relied about the Windows GDI. Neither Cups or LPD supported it.
 
Last edited:
  • #35
When you were configuring your printer you did switch from "generic" to the company of your printer right?
 
  • #36
mattmns said:
When you were configuring your printer you did switch from "generic" to the company of your printer right?

You misunderstand. LPD and CUPS both depend on the printer being Postscript-capable. If it's not, the printer is not supported, regardless.
 
  • #37
mattmns said:
When you were configuring your printer you did switch from "generic" to the company of your printer right?


yeah, but the model number is not listed as a choice.
 
  • #38
I'm having a problem with glibc-devel, specifically /usr/lib/crt1.o which seems to be missing and is preventing me from running the intel compiler. How do i fix this? I've found posts from people with this problem all over hte place, but haven't found a solution.
 
  • #39
franznietzsche said:
I'm having a problem with glibc-devel, specifically /usr/lib/crt1.o which seems to be missing and is preventing me from running the intel compiler. How do i fix this? I've found posts from people with this problem all over hte place, but haven't found a solution.

Do a 'find / -name crt1.o' from a shell, and post your output. You could also verify that crt1.o is in /usr/lib.

Take a look at the release notes:

http://neumann.cem.msu.edu/docs/icc/C++ReleaseNotes.htm

There's an insert about the 'crt1.o' error you are encountering. If your error message looks similar to that, modifying your LD_LIBRARY_PATH environment variable will be trivial.
 
Last edited by a moderator:
  • #40
[]$ ifort hw1c.f90
ld: /usr/lib/crt1.o: No such file: No such file or directory
[]$ find -name crt1.o
[]$

It doesn't disply anything when i enter the find command, just brings up another prompt.

ONly thing I've found online is that this has to do with a problem with the gnu library, but fixing that seems to be very difficult.
 
  • #41
franznietzsche said:
[]$ ifort hw1c.f90
ld: /usr/lib/crt1.o: No such file: No such file or directory
[]$ find -name crt1.o
[]$

It doesn't disply anything when i enter the find command, just brings up another prompt.

ONly thing I've found online is that this has to do with a problem with the gnu library, but fixing that seems to be very difficult.

Did you do a full Fedora install?

This shouldn't be difficult at all. If you didn't do an install it's a matter of 1) installing the glibc-devel rpm and 2) setting the correct LD_LIBRARY_PATH. Both of these are trivial.
 
  • #42
graphic7 said:
Did you do a full Fedora install?

This shouldn't be difficult at all. If you didn't do an install it's a matter of 1) installing the glibc-devel rpm and 2) setting the correct LD_LIBRARY_PATH. Both of these are trivial.


I tried installing the glibc-devel rpm, but the the entire glibc is missing.

And it may be trivial, but i still don't know how to do it
 
  • #43
The only thing i can think of is that there is something wrong with the GNU library on Fedora. I can't find a solution for this problem anywhere, i tried reinstalling, made sure that glibc was included, and the probelm is still there. Every other report I've found of this problem has been running fedora.

Any ideas?
 
  • #44
I looked in the install.log and found that

glib-devel-1.2.10-15.x86_64.rpm
glibc-devel-2.3.3-74.i386.rpm
glibc-profile-2.3.3-74.x86_64.rpm
glibc-utils-2.3.3-74.x86_64.rpm

Were all NOT installed.

glibc-2.3.3-74.i686
glibc-2.3.3-74.x86_64

Were installed
 
  • #45
I checked the MD5 checksum on the isos to be sure they matched(it did). However, when i booted from the fedora disc, it failed the media check. Could this be related? Why would the MD5 match when the media check failed though?
 
  • #46
glibc-2.3.3-74.i686
glibc-2.3.3-74.x86_64

Were installed
Shouldn't it be one or the other?
 
  • #47
gnome said:
Shouldn't it be one or the other?


I would think so, but that's what the install.log said.

I'm running yum update right now, I'm hoping that maybe that will fix the problem, it listed all the glibc files (glibc, glibc-devel, glibc-common) that i was apparently missing.
 
  • #48
Arrr. This is exactly why I like emerge. It is just better at installing and keeping track of software. I just installed suse 9.2 on someones computer because they got pentrated for NOT CHANGING DEFAULT PASSWORDS. Actually it was partially my fault for forgetting to disable root login through ssh, but anyway. They previosly ran gentoo. The first thing that they complain to me about is how bad installing programs is. Even for myself it was a pain in the butt to install stuff. So know they are going back to gentoo.

The moral of the story:
If you had installed gentoo and typed: emerge icc, you would have been done a long time ago.
 
Last edited:
  • #49
dduardo said:
Arrr. This is exactly why I like emerge. It is just better at installing and keeping track of software. I just installed suse 9.2 on someones computer because they got pentrated for NOT CHANGING DEFAULT PASSWORDS. Actually it was partially my fault for forgetting to disable root login through ssh, but anyway. They previosly ran gentoo. The first thing that they complain to me about is how bad installing programs is. Even for myself it was a pain in the butt to install stuff. So know they are going back to gentoo.

The moral of the story:
If you had installed gentoo and typed: emerge icc, you would have been done a long time ago.


Yeah, but oh well. Its working now, so no worries. Thanx for the input and help everyone.
 

Similar threads

  • · Replies 1 ·
Replies
1
Views
921
  • · Replies 43 ·
2
Replies
43
Views
5K
  • · Replies 1 ·
Replies
1
Views
4K
  • · Replies 10 ·
Replies
10
Views
3K
Replies
2
Views
6K
Replies
46
Views
7K
Replies
6
Views
3K
Replies
31
Views
5K
  • · Replies 1 ·
Replies
1
Views
7K