Posted 02 March 2004 - 11:56 PM
Posted 03 March 2004 - 12:12 AM
Posted 03 March 2004 - 09:22 AM
Posted 03 March 2004 - 09:49 AM
if the following insults your intelligence in any way, i mean no offense:
When you are dealing with windows, drives (hdd, cdrom, whatever) use letter names. Typically, the floppy is A and or B, the hdd is C, and cdrom(s) go in D,E, and so on. Network drives typically start at J or somewhere in there. In linux, things are a bit different. /dev/hda would be like (A) /dev/hda1 would be like ( and so on. So when you get to the partitioning phase of your mandrake install, and you don't see C,D,E and whatever, dont worry.
I don't have much experience with mandrake, it didn't like the dvd/cdrom combo drive i used to install it, so redhat was my first distro by default. Also, in my redhat days i didnt know /dev/null from a hole in the ground (it is debatable weither i do now or not). But anyway, the plot thickens when it comes to mounting things like your floppy...
In slackware, my cdrom was originally found as /dev/hdb, but after doing the install it became /dev/cdrom all of a sudden. Im sure you can determine the difference between /dev/hda (the letters hd seem to give it away), and /dev/cdrom (hello mcfly)
sorry, i've been awake for over 24 hours... i know this post is crappy but working overnight is teh sux
Posted 03 March 2004 - 10:08 AM
Posted 03 March 2004 - 10:46 AM
Posted 03 March 2004 - 01:00 PM
Posted 03 March 2004 - 05:33 PM
Posted 03 March 2004 - 06:12 PM
pretty sure it does, not sure it will always work though, NTFS doesn't play well with others
I dunno if Mandrake does the Windows re-size and re-partitioning like I hear some distro's do, but you might need to slice it up and make room for another/more partition[s].
Posted 03 March 2004 - 07:08 PM
sorry i was thinking about that later and i figured it out!
blah. It's from the movie of where you avatar is from, Rejected by Don Hertzfeld, IIRC. Yeah, I've used Bochs x86, very cool stuff.
Posted 03 March 2004 - 08:46 PM
How to dual-boot Windows NT/2000/XP and Linux using NTLDR
This tutorial is based on using LILO (linux loader) as your boot loader. It assumes you already have NT/2000/XP install and booting.
At the time of this writing, I was booting Linux, WindowsNT, and DOS 6.22 at home, and Linux, WindowsNT, and DR-OpenDOS 7.02 at work. It was pretty annoying, to me at least, to have the LILO prompt come up, type 'dos', and THEN have to select an option from the NTLDR menu which would pop up afterwards. I liked the menu presentation that NT gave at the time, so I chose to use NTLDR to boot them all from one selection. The only apparent disadvantage to this setup is that you need to update the linux boot image in the NTLDR when you install a new kernel. However, I don't imagine most average users switch kernels all that often, and those of you that do won't mind doing this, or already have a better solution in mind/in place.
That said, if you need/want this, read on. If not, skip it.
The first step in the process is to remove the current installation of LILO from the Master Boot Record (MBR), if you're already using it. If not, ignore this part. To accomplish this, type 'lilo -u <boot device>'. On my machine, this was /dev/hda, which corresponds to the MBR of the first detected hard drive. If all goes well, LILO will be uninstalled. DO NOT REBOOT at this point, your system will be inaccessible without a boot disk or CD.
The next step is to edit your LILO configuration file. It's usually /etc/lilo.conf. If lilo was installed in the MBR, the lilo.conf will reflect this. There are a couple changes to be made. Here is an example lilo.conf file:
This lilo.conf file is configured so that the boot device is /dev/hda. Tha's the MBR on the first detected hard drive. So we want to change that to be the linux root partition, which NTLDR will load up for us, instead of LILO loading the NTLDR. In my case, this is /dev/hdb1, the first partition of the second hard drive. Next, since NTLDR will be handling the booting, LILO doesn't need to know anything about the WindowsNT or DOS installs, nor how to boot them, so take out or comment out the prompt, timeout and other sections. It should now look like this:
By commenting out prompt, we tell LILO not to ask which selection to boot, it just picks the first one it sees, which is our linux kernel. The timeout option is only needed in conjunction with prompt, so that goes, too. The other section is what LILO normally would use to pass us off to the NTLDR, and now it won't bother.
The next thing to do is install LILO. This time, we want it on our linux root partition, instead of in the MBR. Since we've edited lilo.conf to specify the correct location already, all that's necessary is to run lilo. It may complain that lilo isn't being installed on the first drive, but since there will be a boot loader there (NTLDR), that's ok, and we can safely ignore the warning. Once this is done, keep reading, linux isn't quite bootable yet.
LILO is now installed on our linux root partition, but there's still nothing pointing it to linux. To get around this, we create a boot sector image file or sorts for the NTLDR to look at to boot linux. The way we do this is to use the dd program (copy/convert utility). The syntax we're looking for is: 'dd if=<root partition> of=<boot pointer file> bs=512 count=1'. This is a little more complicated than the bootdisk dd usage. <root partition> is of course your linux root partition, /dev/hdb1 in this case. <boot pointer file> is a file that will contain the boot sector image that NTLDR uses to boot linux. It's a physical copy of the first 512 bytes of the linux root partition, where LILO is now installed. Making sense now? bs=512 sets the block size to 512 bytes, and count=1 ensures that we only get one block in the image. I used: 'dd if=/dev/hdb1 of=bootsect.lnx bs=512 count=1'. You should now have a file called bootsect.lnx (which, if you're using WindowsNT and DOS, needs to be in DOS 8.3 filename format, which bootsect.lnx fits in.
The bootsect.lnx file is basically your linux boot sector. It will go on the NT/2000/XP partition, and be loaded by NTLDR. To add this to your NTLDR menu, you only need to edit the boot.ini file located in your Windows root directory (usually c:\.) Here's a sample boot.ini:
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Workstation Version 4.00"
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT Workstation Version 4.00 [VGA mode]" /basevideo /sos
To add the bootsect.lnx file we created to the NTLDR configuration file, simply add a line that looks like this, reflecting your own decription:
C:\bootsect.lnx="Red Hat Linux Release 4.2 (Biltmore)"
Once you've edited the boot.ini and saved it, you should be good to go. When you reboot the machine, the NTLDR menu has a new option at the bottom, "Red Hat Linux Release 4.2 (Biltmore)" in this case. Select it, hit enter, and linux boots.
If you want linux to be your default cjoice, just change the default line to: default=C:\bootsect.lnx.
Posted 03 March 2004 - 09:53 PM
Posted 04 March 2004 - 08:23 AM
Never knew you could use the NT bootloader to load Linux, I may have to give that a go later
Oh jedibebop, I know we've never talked before, but I'm in the process of getting a working Gentoo system up, and all I can say is wow. It's a pain in the ass with a certain combo of hardware. I'm running an ATI 9600 on an NForce2 mobo. It's getting difficult!
Edited by spite, 04 March 2004 - 08:25 AM.
Posted 04 March 2004 - 09:38 AM
if you need help pm or something
Posted 04 March 2004 - 09:59 AM
is the onboard NIC well supported?
I have an nforce 2 mobo and a 9800 pro, both work fine
if you need help pm or something
Posted 04 March 2004 - 12:06 PM
I found spite on freenode and told him about it already heh
Posted 04 March 2004 - 12:24 PM
Posted 04 March 2004 - 11:06 PM
I just dunno if I'll stick with Gentoo. I love my Debian. Maybe there is something to ease of use
BinRev is hosted by the great people at Lunarpages!