Maybe I can help with the boot problem. Debian doesn't use LILO as a MBR boot manager. They use a program known just as MBR. (At least this is true for the bo release, is it true for hamm?) I'm not quite sure why LILO isn't used as the MBR boot manager, because it appears to be superior to MBR in many ways. Anyway, LILO, when installed as an MBR boot manager can boot Linux on a second drive, the MBR program can't. If you want to install LILO as MBR you can do what I did. Just make a boot floppy. Use it to start Linux and then configure LILO to be installed as MBR.
It sounds as if you'd rather start Linux through the NT Loader (a boot sector loader instead of an MBR loader). To do this make a LILO config file that installs LILO as a boot sector loader on your Linux partition. Then copy the boot sector (dd if=/dev/hdb1 of=bootsect.lnx bs=512 count=1) to your NT Loader partition and modify your boot.ini file or use bootpart to do all of this for you. Everytime you install a new kernel you will need to re-run LILO and copy the boot sector to the NT partition. Sorry I can't help with the more serious boot failure problem. Good luck, Tony Richardson -----Original Message----- From: Mike Harmon [SMTP:[EMAIL PROTECTED] Sent: Monday, July 13, 1998 2:44 PM To: debian-user Subject: Two Questions Hi Everyone, I am a Debian newbie. Actually I'm ALMOST a Linux newbie. My system environment is as follows: IBM Mod 365 200 MHz Pentium Pro system (32 MB RAM) HD 0 is a 2.5 GB IDE (NT 4.0 loaded) HD1 is a 540 MB IDE (Linux) Network Card is an IBM Auto 16/4 Token Ring ISA card I'm using BOOTPART to allow my NT boot manager to boot Linux Here are my questions/problems: 1. After I installed the base disks and went through the config steps, I got to the point where I was asked whether I wanted to set up Linux to boot from the HD. I said 'yes'. I received an error message telling me that it was impossible to boot from the second HD, even though it used to work fine with Red Hat 4.2. I was expecting the config program to ask me whether I wanted to use the MBR or place the boot sector on the first track of the Linux boot partition, but it didn't. 2. When I tried to reboot the system (by selecting my 'Linux' choice from the NT boot menu), I got the following screen: Disk formatted with WinImage 2.20 (c) 1993-95 Gilles Vollant. Bootsector from C. H. Hochstatter. No Systemdisk. Booting from harddisk. Cannot load from harddisk. Insert Systemdisk and press any key. 3. I inserted my rescue disk and pressed <enter>. At the boot: prompt, I entered: rescue root=/dev/hdb1 4. The system responded with: Loading linux . . . and proceeded with the boot process. After the normal two dozen or so boot messages, I got to the following point in the boot process: Checking all file systems . . . Parallelizing fsck version 1.10 (24-Apr-97) /dev/hdb5: clean, 11/16632 files, 2129/66496 blocks /dev/hdb6: clean, 2333/92520 files, 22425/368641 blocks Mounting local file systems . . . /dev/hdb5 on /home type ext2 (rw) /dev/hdb6 on /usr type ext2 (rw) and then my system froze up tight. I suspect that the boot freezeup is some kind of difugilty with the Token Ring card (I never did get it to work with Red Hat 4.2). A few lines earlier on the boot process, I got messages indicating that the tr0 device was found, but I never received any message indicating that the adapter had been opened successfully. I'd really like to get the TR support to work, because that's what we use here at work, and I'd like to be able to use Linux to connect to the LAN. I know I have all the IP stuff set up correctly, because I had our telecomm guru on the line while I was filling in the blanks. Can anyone shed some light on my somewhat dimly-lit world regarding these two issues. All help will be greatly rewarded with virtual beer. Thanks, Mike Harmon -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
