Lilo question
Hi. I am having a little problem with LILO. I have a machine with Win2000 on the first IDE drive and I want install Debian on the other drive, which happens to be SCSI. If in /etc/lilo.conf I specify boot=/dev/hda -asking LILO to install itself into the MBR, how will I make it aware that Debian kernel resides in /dev/sda? Meaning the line image=/boot/kernel-2.6 will make LILO think that Debian is also in /dev/hda. Has anyone encountered a similar situation? Thanks in advance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question
Sherman, Michael (GE Energy) wrote: Hi. I am having a little problem with LILO. I have a machine with Win2000 on the first IDE drive and I want install Debian on the other drive, which happens to be SCSI. If in /etc/lilo.conf I specify boot=/dev/hda -asking LILO to install itself into the MBR, how will I make it aware that Debian kernel resides in /dev/sda? Meaning the line image=/boot/kernel-2.6 will make LILO think that Debian is also in /dev/hda. Has anyone encountered a similar situation? Thanks in advance. boot=/dev/hda root=/dev/sda1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question..
http://www.knoppix.net/forum/viewtopic.php?t=3311postdays=0postorder=ascstart=0 should help you get started. roughly, after booting from the disk, from a command line (xterm or tty) you'll need to mount the debian partitions that you would want to work with (mount /dev/hd5 /mnt/hda5) and from there, chroot that directory, and from within the chroot mount the /boot partition; you may also need to mount /proc but this depends on your setup. -d. Ishwar Rattan wrote: On Mon, 31 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: On Sun, 30 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: On Sun, 30 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: Got a Debian CD? Or Knoppix? I have Knoppix-3.4 cd. Then you can do anything including boot Debian, make a boot floppy, fix lilo.conf, move kernels around, etc. Heck, if your Mandrake boots, you can do all that too. Can you give me poiters to do that? -ishwar -- David Piniella University of Miami -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question..
Ishwar Rattan [EMAIL PROTECTED] writes: I have Debian/testing on /dev/hda5, Mandrake-10.0 on /dev/hda7 and swap on /dev/hda1 The /etc/lilo.conf (currently set up for Mandrake boot) [snip] System does boot correctly. I added the entry image=/boot/vmlinuz-2.6.5 label=debian root=/dev/hda5 initrd=/boot/initrd.img-2.6.5 append=xx...xx read-only and when command /sbin/lio is run it generates the error Fatal: open /boot/vmlinuz-2.6.5: No such file or directory How do I make it work? My expertise on lilo is limited.. I assume you did run /sbin/lilo from your mandrake system. The /boot directory of your mandrake system is not the same as the one from /debian. That's why lilo can't find the kernel. So either copy the debian kernel and initrd into the mandrake /boot directory or mount the debian files somewhere before running lilo (adapting the paths in lilo.conf) Robert Epprecht -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question..
On Sun, 30 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: On Sun, 30 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: Fatal: open /boot/vmlinuz-2.6.5: No such file or directory When running your debian, what does this say: ls -l /boot/vmlinuz Can't boot or run debian as I did not make a boot-floppy :-( Got a Debian CD? Or Knoppix? I have Knoppix-3.4 cd. -ishwar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question..
Incoming from Ishwar Rattan: On Sun, 30 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: On Sun, 30 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: Fatal: open /boot/vmlinuz-2.6.5: No such file or directory When running your debian, what does this say: ls -l /boot/vmlinuz* Can't boot or run debian as I did not make a boot-floppy :-( Got a Debian CD? Or Knoppix? I have Knoppix-3.4 cd. Then you can do anything including boot Debian, make a boot floppy, fix lilo.conf, move kernels around, etc. Heck, if your Mandrake boots, you can do all that too. Find some empty directories in Mandrake, mount your Debian partitions on them, then fix away. Or use Knoppix as a rescue disk, boot to single user, mount Debian partitions, ... -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Lilo question..
I have Debian/testing on /dev/hda5, Mandrake-10.0 on /dev/hda7 and swap on /dev/hda1 The /etc/lilo.conf (currently set up for Mandrake boot) boot=/dev/hda map=/boot/map default=linux prompt nowarn timeout=100 message= menu-scheme= image=/boot/vmlinuz label=linux root=/dev/hda7 initrd-/boot/initrd.img append=xx..xx vga=788 read-only image= other-entries.. System does boot correctly. I added the entry image=/boot/vmlinuz-2.6.5 label=debian root=/dev/hda5 initrd=/boot/initrd.img-2.6.5 append=xx...xx read-only and when command /sbin/lio is run it generates the error Fatal: open /boot/vmlinuz-2.6.5: No such file or directory How do I make it work? My expertise on lilo is limited.. -ishwar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question..
Incoming from Ishwar Rattan: image=/boot/vmlinuz-2.6.5 label=debian root=/dev/hda5 initrd=/boot/initrd.img-2.6.5 append=xx...xx read-only and when command /sbin/lio is run it generates the error Fatal: open /boot/vmlinuz-2.6.5: No such file or directory When running your debian, what does this say: ls -l /boot/vmlinuz* -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question..
Hello Ishwar Rattan ([EMAIL PROTECTED]) wrote: I have Debian/testing on /dev/hda5, Mandrake-10.0 on /dev/hda7 and swap on /dev/hda1 The /etc/lilo.conf (currently set up for Mandrake boot) boot=/dev/hda map=/boot/map default=linux prompt nowarn timeout=100 message= menu-scheme= image=/boot/vmlinuz label=linux root=/dev/hda7 initrd-/boot/initrd.img append=xx..xx vga=788 read-only image= other-entries.. System does boot correctly. I added the entry image=/boot/vmlinuz-2.6.5 label=debian root=/dev/hda5 initrd=/boot/initrd.img-2.6.5 append=xx...xx read-only and when command /sbin/lio is run it generates the error Fatal: open /boot/vmlinuz-2.6.5: No such file or directory Probably because the kernel 2.6.5 is in the boot directory on hda5 (the Debian system), but lilo was run from within Mandrake, and at that time /boot is on hda7 and lilo cannot find the Debian Kernel. You should either copy the kernel to the Mandrake boot directory, or mount hda5 somewhere and point lilo to the correct location (e.g. image=/mnt/debian/boot/vmlinuz-2.6.5), or (this is what I normally do) you configure a boot loader in Debian, save it to /dev/hda5 (boot=/dev/hda5 in lilo.conf on your Debian system), and you add an entry other=/dev/hda5 label=Debian in the Mandrake lilo configuration. This is quite easy to maintain. If you install a new Kernel on your Debian system, you do not need to boot or chroot into your Mandrake system and reinstall lilo. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question..
On Sun, 30 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: image=/boot/vmlinuz-2.6.5 label=debian root=/dev/hda5 initrd=/boot/initrd.img-2.6.5 append=xx...xx read-only and when command /sbin/lio is run it generates the error Fatal: open /boot/vmlinuz-2.6.5: No such file or directory When running your debian, what does this say: ls -l /boot/vmlinuz Can't boot or run debian as I did not make a boot-floppy :-( -ishwar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo question..
Incoming from Ishwar Rattan: On Sun, 30 May 2004, s. keeling wrote: Incoming from Ishwar Rattan: image=/boot/vmlinuz-2.6.5 label=debian root=/dev/hda5 initrd=/boot/initrd.img-2.6.5 append=xx...xx read-only and when command /sbin/lio is run it generates the error Fatal: open /boot/vmlinuz-2.6.5: No such file or directory When running your debian, what does this say: ls -l /boot/vmlinuz Can't boot or run debian as I did not make a boot-floppy :-( Got a Debian CD? Or Knoppix? -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/lilo question
* Clive Menzies ([EMAIL PROTECTED]) [030917 14:50]: On (17/09/03 16:46), Victory wrote: Some one please let me know the advantage/disadvantage about grub/lilo ext2/ext3. As I understand it lilo is the official debian bootloader [...] default != official. my grub systems are no less debian than any lilo systems! IMO, grub is vastly superior to LILO. The ability to reconfigure everything at run-time is one of those features that you just can't go back from. LILO gets the job done for day-to-day work, generally, but whenever you have to reconfigure the boot loader, if you're working with a grub system, you're a much happier camper. good times, Vineet -- http://www.doorstop.net/ -- http://www.digitalconsumer.org/ Protecting fair-use rights in the digital world pgp0.pgp Description: PGP signature
Re: grub/lilo question
* Victory ([EMAIL PROTECTED]) [030917 13:51]: Some one please let me know the advantage/disadvantage about grub/lilo ext2/ext3. Please don't post questions to the list by replying to unrelated posts. While you changed the subject of your message to something appropriate, your message includes headers (In-Reply-To and References) marking it as a reply to the unrelated message. This screws up people using mail readers capable of displaying the threaded nature of the mailing list (which I advise you to use as well; I can't imagine following a list of this volume without it!). The programs that run to generate the mailing list archives on the web also display the messages sorted and referenced by thread, so stringing together unrelated messages in the same thread is distracting and potentially confusing to later readers of the archives as well. If you don't understand what I'm talking about with threading, please go see the list archives on the web. good times, Vineet -- http://www.doorstop.net/ -- If you can put it on a T-shirt, it's speech... To enjoin the T-shirts as a circumvention device is ludicrous. --Robin Gross, EFF staff attorney pgp0.pgp Description: PGP signature
Re: grub/lilo question
On Thu, 18 Sep 2003 01:20:09 +0200, Chris McQueeny wrote: As Ext/3 has matured a great deal since it was released, my opinion is that it is entirely superior to Ext/2 at least. The journalling capabilities greatly increase speed and reliability in many cases. It increases speed in exactly one case: When the system has crashed or suffered a power loss without cleanly unmounting the disks. Then, ext3 will save you a fsck run. In all other cases, performance can't be any better than plain old ext2. I'd expect it to perform worse than ext2 actually. -- Best Regards, | Hi! I'm a .signature virus. Copy me into Sebastian | your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/lilo question
The reason I'm asking for this because in the past I been using GRUB for RH and now I'm switch to Debian and now using LILO w. ext3 fs. The problem I have right now is if someone turn the power off without shutting computer down proper way, then when the system turn back on, it go through fsck .../dev/sda1 and got to the point: /dev/sda1: UNXEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p option) at this point, it give me a option to: Give root passwd for maintenance (or type Control-D for nornal startup): This is the problem for me because this machine is only networking and had no monitor attach to it, so I don't know what going with the system. Is there a way to force the system run fsck without going to maintenane mode to run fsck for /dev/sda1 ??? Regards, Victory, - Original Message - From: Carla Schroder [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 17, 2003 7:20 PM Subject: Re: grub/lilo question On Wednesday 17 September 2003 1:46 pm, Victory wrote: Some one please let me know the advantage/disadvantage about grub/lilo ext2/ext3. Regards, Victor. 1. GRUB contains its own little command shell, for passing in or editing commands at boot time. It can read from a configuration file. It supports many filesystems, currently BSD FFS, DOS FAT16 and FAT32, Minix fs, Linux ext2fs, ReiserFS, and VSTa fs; and blocklists for files that do not appear in filesystems, such as chainloaders. GRUB reads filesystems and kernel executables, rather than inflexibly restricting the user to disk geometry. Install and remove operating systems as needed. Boot bare kernels, passing in modules and parameters from the command line. GRUB will even download OS images over the network. GRUB does not need a /boot partition, just let it own the MBR. 2. ext3 is the journaled version of ext2. It's really just an extension to ext2. You can convert back and forth, I don't know why you would want to, but you can. With other journaling filesystems, such as ReiserFS or JFS, there is no compatibility with other filesystems, so once you choose it, it's not easy to make a change. There is no reason I can think of to not use a journaling filesystem, any of the major Linux ones are good. -- ~ Carla Schroder www.tuxcomputing.com this message brought to you by Libranet 2.8 and Kmail ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
grub/lilo question
Some one please let me know the advantage/disadvantage about grub/lilo ext2/ext3. Regards, Victor. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/lilo question
On (17/09/03 16:46), Victory wrote: Some one please let me know the advantage/disadvantage about grub/lilo ext2/ext3. As I understand it lilo is the official debian bootloader but is not as flexible as grub for booting many different kernels. I've used both and lilo is automatically set up during the install. Grub requires a bit of configuring but once working it is straight forward and smooth ;) http://linuxtoday.com/infrastructure/2002102200426NWDBSW describes the grub set up well ext2 v ext3 is a bit beyond my knowledge ;) HTH Clive -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/lilo question
If you mean how well they (e.g., grub and ext2) work together, any combination of these should work harmoniously. If you have a seperate /boot partition though, it will need to be ~64 mb to use Ext/3. (This extra space is taken up by the journal file.) If, on the other hand, you mean how are they individually, then I would first say that the choice between grub lilo is mostly arbitrary. On a modern computer, either should work well; lilo has easier configuration syntax, but grub is much more advanced. As far as the filesystems are concerned, nowadays it is very clear-cut. As Ext/3 has matured a great deal since it was released, my opinion is that it is entirely superior to Ext/2 at least. The journalling capabilities greatly increase speed and reliability in many cases. I personally use SGI's XFS, but Ext/3 is a good choice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/lilo question
On Wednesday 17 September 2003 1:46 pm, Victory wrote: Some one please let me know the advantage/disadvantage about grub/lilo ext2/ext3. Regards, Victor. 1. GRUB contains its own little command shell, for passing in or editing commands at boot time. It can read from a configuration file. It supports many filesystems, currently BSD FFS, DOS FAT16 and FAT32, Minix fs, Linux ext2fs, ReiserFS, and VSTa fs; and blocklists for files that do not appear in filesystems, such as chainloaders. GRUB reads filesystems and kernel executables, rather than inflexibly restricting the user to disk geometry. Install and remove operating systems as needed. Boot bare kernels, passing in modules and parameters from the command line. GRUB will even download OS images over the network. GRUB does not need a /boot partition, just let it own the MBR. 2. ext3 is the journaled version of ext2. It's really just an extension to ext2. You can convert back and forth, I don't know why you would want to, but you can. With other journaling filesystems, such as ReiserFS or JFS, there is no compatibility with other filesystems, so once you choose it, it's not easy to make a change. There is no reason I can think of to not use a journaling filesystem, any of the major Linux ones are good. -- ~ Carla Schroder www.tuxcomputing.com this message brought to you by Libranet 2.8 and Kmail ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/lilo question
On Wed, 17 Sep 2003 16:20:05 -0700, Carla Schroder [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]: On Wednesday 17 September 2003 1:46 pm, Victory wrote: Some one please let me know the advantage/disadvantage about grub/lilo ext2/ext3. Regards, Victor. 1. GRUB contains its own little command shell, for passing in or editing commands at boot time. It can read from a configuration file. It supports many filesystems, currently BSD FFS, DOS FAT16 and FAT32, Minix fs, Linux ext2fs, ReiserFS, and VSTa fs; and blocklists for files that do not appear in filesystems, such as chainloaders. GRUB reads filesystems and kernel executables, rather than inflexibly restricting the user to disk geometry. Install and remove operating systems as needed. Boot bare kernels, passing in modules and parameters from the command line. GRUB will even download OS images over the network. GRUB does not need a /boot partition, just let it own the MBR. ..is Grub far from being able to boot off a cd now? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Newbee Dual Linux Install and Lilo question...
Ok I have a fully installed and functioning debian install of Linux on 1 partition. I now have a second partition of 700mb that I want to install a second fully functional debian on. I was going to do this via the cd and have it install on the second partition this time. Do I need to make any changes to lilo before I do this or do I make the changes after I install the fully functional Linux on the second partition. Thanks Kris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: LILO question
Duh; sorry I forgot about this... I don't know if you can get away with doing this the easy way. Ok first stage, Lilo is installed on /dev/hda so it's in the MBR. Second you need to make /dev/hdb1 ACTIVE. If you do not know how to do this read 'man fdisk'. You only need to make it active, not otherwise change your partition table... It will either then boot, or you're going to have to fake windows out about your partition table... That's hard and I've never done it before. It's in the lilo documentation though. Which should be someplace like /usr/doc/lilo/ and you'll need to be root to run lilo anyway... -Original Message- From: Mannequin* [mailto:[EMAIL PROTECTED] Behalf Of Mannequin* Sent: Saturday, July 14, 2001 01:13 To: mjevans1983011 Subject: Re: LILO question mjevans1983011 [EMAIL PROTECTED] writes: Your windows entry looks like... other=/dev/hdb1 label=winlabel etc? Yeah, I've tried that and other=/dev/hdb. Neither of them have worked. One locks the computer up, and the other asks for a boot disk. -Mannequin* -Original Message- From: Mannequin* [mailto:[EMAIL PROTECTED] Behalf Of Mannequin* Sent: Wednesday, July 11, 2001 04:12 To: debian-user@lists.debian.org Subject: LILO question I know this has probably been asked on here before, but I'm running Debian Stable on my i686 and I'm having problems with LILO. Basically, I have Debian installed on /dev/hda and Windoze on /dev/hdb. LILO is install on the boot block of /dev/hda. So here is where my problem lies; I cannot get LILO to boot my Windoze drive at all. I've looked through the man pages for lilo.conf, but to no avail. I'm assuming from previous installations that Windozes' boot block is on /dev/hdb1. Can anyone give me any help in this situation? Thanks. -Mannequin* _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: LILO question
mjevans1983011 [EMAIL PROTECTED] writes: Duh; sorry I forgot about this... I don't know if you can get away with doing this the easy way. Ok first stage, Lilo is installed on /dev/hda so it's in the MBR. Second you need to make /dev/hdb1 ACTIVE. If you do not know how to do this read 'man fdisk'. You only need to make it active, not otherwise change your partition table... It will either then boot, or you're going to have to fake windows out about your partition table... That's hard and I've never done it before. It's in the lilo documentation though. Which should be someplace like /usr/doc/lilo/ and you'll need to be root to run lilo anyway... Well, I think I might have done it the hard way. *grins* Romain Lerallut responded and said to do this to my /etc/lilo.conf: ... other=/dev/hdb1 label=windows map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 ... I just did that, and it worked immediately. Thanks for your help, though. -Mannequin*
Re: LILO question
mannequin == mannequin [EMAIL PROTECTED] writes: mannequin I know this has probably been asked on here before, but I'm mannequin running Debian Stable on my i686 and I'm having problems mannequin with LILO. Basically, I have Debian installed on /dev/hda mannequin and Windoze on /dev/hdb. LILO is install on the boot block mannequin of /dev/hda. So here is where my problem lies; I cannot get mannequin LILO to boot my Windoze drive at all. I've looked through AFAIK, Windows doesn't like to be booted from the second hard disk. Swap the drives, and life will be a lot easier. -- G. ``Iggy'' Geens - ICQ: #64109250 Home: [EMAIL PROTECTED] - Work: [EMAIL PROTECTED] WWW: http://users.pandora.be/guy.geens/ `I want quality, not quantity. But I want lots of it!'
Re: LILO question
Thus spake Guy Geens on Wed, Jul 11, 2001 at 07:41:00PM +0200: mannequin == mannequin [EMAIL PROTECTED] writes: mannequin I know this has probably been asked on here before, but I'm mannequin running Debian Stable on my i686 and I'm having problems mannequin with LILO. Basically, I have Debian installed on /dev/hda mannequin and Windoze on /dev/hdb. LILO is install on the boot block mannequin of /dev/hda. So here is where my problem lies; I cannot get mannequin LILO to boot my Windoze drive at all. I've looked through AFAIK, Windows doesn't like to be booted from the second hard disk. Swap the drives, and life will be a lot easier. I agree, lilo can swap drives depending on which image you want to boot: /etc/lilo.conf ... other=/dev/hdb1 label=windows map-drive=0x80 to=0x81 map-drive=0x81 to=0x80 ... HTH, Romain -- This is a test of the emergency broadcast system. Had there been an actual emergency, then you would no longer be here.
LILO question
I know this has probably been asked on here before, but I'm running Debian Stable on my i686 and I'm having problems with LILO. Basically, I have Debian installed on /dev/hda and Windoze on /dev/hdb. LILO is install on the boot block of /dev/hda. So here is where my problem lies; I cannot get LILO to boot my Windoze drive at all. I've looked through the man pages for lilo.conf, but to no avail. I'm assuming from previous installations that Windozes' boot block is on /dev/hdb1. Can anyone give me any help in this situation? Thanks. -Mannequin*
Quick Lilo question...
I've finally got Lilo set up just how I want it, almost. I'd like a boot option that sends me straight into single user mode. Yes, I know I can just enter Linux single at the boot prompt (or something similar... I don't quite remember), but I'm lazy, and would like a boot option I can select from the boot menu. Thanks! --Aaron
Re: Quick Lilo question...
On Sun, Jul 01, 2001 at 12:54:16PM -0400, Aaron Traas wrote: I've finally got Lilo set up just how I want it, almost. I'd like a boot option that sends me straight into single user mode. Yes, I know I can just enter Linux single at the boot prompt (or something similar... I don't quite remember), but I'm lazy, and would like a boot option I can select from the boot menu. It's in lilo.conf(5), look for append. Cheers, Joost
Lilo Question
After hours and hours of aggravation I was finally able to get both Windoze and Debian installed on my wife's compaq presario. Because of partioning problems (I think) I had to install win98 in the first partition and it finally worked fine. I will copy some of the files from the CD to drive, as suggested by folks here on the list. My problem now is that when I installed and configured the kernel for libranet debian, it overwrote the mbr and now I can't boot windoze from the hd. Lilo just gives me linux. I will get to the man page as soon as I'm not so tired, in the meantime, I have a couple of questions: 1.) Can I use the Liloconfig tool to include windoze in my lilo configuration. I know this is a dumb question, I'm just overly cautious about blowing my /mbr because I have a LS-120 floppy drive that so far has not allowed me to make any boot floppies. I also have linuxconf on the machine. 2.) Because of this lack of boot floppies, is there a bullet-proof way to configure LILO for both OS's? thanks -- For de little stealin 'dey gets you in jail soon or late. For de big stealin 'dey makes you Emperor and puts you in de Hall o' Fame when you croaks. Eugene O'Neill, 'The Emperor Jones' 1921
RE: Lilo Question
Hi, After hours and hours of aggravation I was finally able to get both Windoze and Debian installed on my wife's compaq presario. Because of partioning problems (I think) I had to install win98 in the first partition and it finally worked fine. I will copy some of the files from the CD to drive, as suggested by folks here on the list. Everyone goes through this, its a rite of passage. :) My problem now is that when I installed and configured the kernel for libranet debian, it overwrote the mbr and now I can't boot windoze from the hd. Lilo just gives me linux. I will get to the man page as soon as I'm not so tired, in the meantime, I have a couple of questions: 1.) Can I use the Liloconfig tool to include windoze in my lilo configuration. I know this is a dumb question, I'm just overly cautious about blowing my /mbr because I have a LS-120 floppy drive that so far has not allowed me to make any boot floppies. I also have linuxconf on the machine. i don't know about liloconfig. but if you add these lines to your /etc/lilo.conf file, you should have no problems other=/dev/hda1 label=windows and rerun /sbin/lilo to rewrite the changes. that is assuming windows is on the first hard drive (hda), partition 1. 2.) Because of this lack of boot floppies, is there a bullet-proof way to configure LILO for both OS's? thanks hope that helps. Jason
Re: Lilo Question
Thanks for the reply Jason, but it didn't work, probably because of the boot block I have installed (per directions). Here's a copy of my lilo.conf file, maybe you can suggest how to edit it properly? cheers Everyone goes through this, its a rite of passage. :) My problem now is that when I installed and configured the kernel for libranet debian, it overwrote the mbr and now I can't boot windoze from the hd. Lilo just gives me linux. I will get to the man page as soon as I'm not so tired, in the meantime, I have a couple of questions: 1.) Can I use the Liloconfig tool to include windoze in my lilo configuration. I know this is a dumb question, I'm just overly cautious about blowing my /mbr because I have a LS-120 floppy drive that so far has not allowed me to make any boot floppies. I also have linuxconf on the machine. i don't know about liloconfig. but if you add these lines to your /etc/lilo.conf file, you should have no problems other=/dev/hda1 label=windows and rerun /sbin/lilo to rewrite the changes. that is assuming windows is on the first hard drive (hda), partition 1. 2.) Because of this lack of boot floppies, is there a bullet-proof way to configure LILO for both OS's? thanks hope that helps. Jason -- For de little stealin 'dey gets you in jail soon or late. For de big stealin 'dey makes you Emperor and puts you in de Hall o' Fame when you croaks. Eugene O'Neill, 'The Emperor Jones' 1921
newbie Lilo question
Hi, I'm getting an x86 machine, and would like to install Debian along with Win98. So far, my Debian experience has been limited to the ppc (mac), so I don't know too much about LILO. Is the option for LILO in the install? And I heard something about the curent lilo supporting booting beyond the 1024th cylinder. Does potato come with this ? Thanks for any help.. kevin
Lilo-question
I have recently started to use lilo after a few years of using loadlin. I have a bit of an unusual setup so please be patient with my long message. My setup is as follows: /dev/hda1 redhat /dev/hdc2 debian (about 8Gb) I installed redhat after my /dev/hda broke and I bought a new one. At that stage I was moving and my debian-stuff was packed already. So I only use redhat to start up my debian. Debian's lilo complains that my debian partition is to large to boot. My redhat's lilo.conf looks like this: boot = /dev/hda timeout = 50 prompt vga = normal read-only map=/boot/map install=/boot/boot.b image = /boot/debian label = Debian root = /dev/hdc2 hdb=ide-scsi image = /boot/vmlinuz-2.2.5-15 label = Redhat root = /dev/hda1 First problem: Redhat's lilo complains about line 12: hdb=ide-scsi Despite this problem I could boot debian as default system and my scsi-emulation on my cdrom worked. I was using kernel 2.2.9 so far. Last night I compiled and installed 2.2.14 with the result: vmlinuz - boot/vmlinuz-2.2.14 I ran Redhat's lilo again with the same merror message about hdb=ide-scsi. Second problem: When I boot the normal way, 2.2.9 comes up as my active kernel. Why? How do I fix it? Johann -- J.H. Spies, Hugenotestraat 29, Posbus 80, Franschhoek, 7690, South Africa Tel/Faks 021-876-2337 Sel/Cell 082-255-2388 Live in harmony with one another. Do not be proud, but be willing to associate with people of low position. Do not be conceited.Romans 12:16
Re: Lilo-question - solved
On Thu, May 04, 2000 at 09:55:10AM +0200, Johann Spies wrote: Second problem: When I boot the normal way, 2.2.9 comes up as my active kernel. Why? How do I fix it? Sorry. I was stupid. I did not see that I my lilo.conf refers not to /vmlinuz but to redhat's /boot/debian. After copying vmlinuz to redhat's /boot/debian the problem was solved. Johann -- J.H. Spies, Hugenotestraat 29, Posbus 80, Franschhoek, 7690, South Africa Tel/Faks 021-876-2337 Sel/Cell 082-255-2388 Live in harmony with one another. Do not be proud, but be willing to associate with people of low position. Do not be conceited.Romans 12:16
Strange LILO question
Is it possible to set LILO on a DOS floppy disk with the default boot for the hard disk and an alternate boot for the DOS floppy itself? Regards, Onno
Re: Strange LILO question
On 20/1/2000 Onno Ebbinge wrote: Is it possible to set LILO on a DOS floppy disk with the default boot for the hard disk and an alternate boot for the DOS floppy itself? if you mean install the lilo boot sector on the DOS floppy then no, dosfs does not leave any room for a bootblock, so installing lilo on it would destroy the dos filesystem, which would not be problem except you say you want to boot from it. you can however install lilo on a floppy and have it boot the hard disk. -- Ethan Benson To obtain my PGP key: http://www.alaska.net/~erbenson/pgp/
Re: Strange LILO question
At 01:43 PM 1/20/00 +, Ethan Benson wrote: On 20/1/2000 Onno Ebbinge wrote: Is it possible to set LILO on a DOS floppy disk with the default boot for the hard disk and an alternate boot for the DOS floppy itself? if you mean install the lilo boot sector on the DOS floppy then no, dosfs does not leave any room for a bootblock, so installing lilo on it would destroy the dos filesystem, which would not be problem except you say you want to boot from it. Yes, that is what I ment, maybe I should put LILO on the hard disk and then set the default boot to the hard disk with an option to boot from A: ??? you can however install lilo on a floppy and have it boot the hard disk. Is there then realy no way to boot the floppy also WITH a DOS filesystem? Probably not :-( Thanks, Onno
Re: Strange LILO question
On 20/1/2000 Onno Ebbinge wrote: Yes, that is what I ment, maybe I should put LILO on the hard disk and then set the default boot to the hard disk with an option to boot from A: ??? perhaps, i have never tried it on a floppy (did with a cd and it didnt work) you could add: other=/dev/fd0 label=floppy to lilo.conf and run lilo WITH the floppy in the drive (otherwise it won't work) you can however install lilo on a floppy and have it boot the hard disk. Is there then realy no way to boot the floppy also WITH a DOS filesystem? Probably not :-( not with lilo, maybe with syslinux or something. -- Ethan Benson To obtain my PGP key: http://www.alaska.net/~erbenson/pgp/
Re: Strange LILO question
Is there then realy no way to boot the floppy also WITH a DOS filesystem? Probably not :-( I think there is a way, just not using LILO, but loadlin. You just take a DOS disk boot DOS and make some kind of menu in you're autoexec.bat file with the choice between dos and linux. (For linux you just do a dos command loadlin with some arguments. Ron
Easy lilo question (win95 on /dev/hda, deb. on /dev/hdb)
Hello, Having had to installk win95, I did (on the first hard drive /dev/hda) and then installed debian (on second ide drive /dev/hdb). When it came to the lilo bit, it asked me if wanted to install lilo on on /dev/hdb - well, I wanted it on /dev/hda so I said no but it didn;t give me the option. Evreything's installed Ok except I need to use f loppy to boot it. How can I install lilo on /dev/hda so i can chose between winb95 anf debian? The docs. I'm afraid have confused me as they are about multiple OS's and I'm not really quite sure about installing lilo on /dev/hda - I daren't experiment lest I balls things up. Martin __ Get Your Private, Free Email at http://www.hotmail.com
Re: Easy lilo question (win95 on /dev/hda, deb. on /dev/hdb)
Hi Martin On Wed, Oct 06, 1999 at 02:52:09AM -0700, Martin Waller wrote: Hello, Having had to installk win95, I did (on the first hard drive /dev/hda) and then installed debian (on second ide drive /dev/hdb). Take a /etc/lilo.conf like that: # LILO Konfigurations-Datei # Start LILO global Section append=auto boot=/dev/hda #compact # faster, but won't work on all systems. linear read-only prompt timeout=100 vga = normal# force sane state # End LILO global section # Linux bootable partition config begins image = /boot/vmlinuz # # ^ Martin, where is Your kernel? root = /dev/hdb1 # ^ Martin, where sits your debian ? # label = linux # Linux bootable partition config ends # # DOS bootable partition config begins other = /dev/hda1 #^^ Martin, what is your Primary Dos Partition? # # label = Win95 table = /dev/hda # DOS bootable partition config ends # Try that. You have to put the correct values for your partitions of that so called OS from Redmont and for your debian. Where is your kernel located? put that in the line image= i suppose either image =/vmlinuz or image=/boot/vmlinuz then run lilo as root. that should work Ingo
LILO question
Hello, I have two hard drives. Disk0 has Windoze98 and Disk1 has Linux. I can boot to Linux with a floppy. Without the Linux boot floppy Windoze boots up. What do I have to do to have a prompt come up at boot time to select one operating system or another? Please be specific as possible so I don't mess up. Thanks in advance!
Re: LILO question
On Tue, 10 Nov 1998, Jeff Miller wrote: I have two hard drives. Disk0 has Windoze98 and Disk1 has Linux. I can boot to Linux with a floppy. Without the Linux boot floppy Windoze boots up. What do I have to do to have a prompt come up at boot time to select one operating system or another? Please be specific as possible so I don't mess up. There was a thread on exactly this subject last month. Check the Debian web pages http://www.debian.org/ or mirrors for the list archives and look for the thread lilo (linux only hd - dos only hd), no solution possible? Several solutions were suggested. My heretical one near the end of the thread is now working happily on my W98/Debian machine. All the best Hugh == Hugh C. Pumphrey, Dept. of -| Tel. 0131-650-6026,Fax:0131-650-5780 Meteorology, Univ. of Edinburgh | Replace 0131 with +44-131 if outside U.K EDINBURGH EH9 3JZ, Scotland | Email [EMAIL PROTECTED] ==P=l=e=a=s=e==N=o=t=e==t=h=e==N=e=w==F=A=X==N=u=m=b=e=r==
Yet another lilo question!!!
What I want to do is very simple. Yet i can't find a solution to the problem. Here is the situation. (I am asking for someone else i may not have all the correct informatiofn) partion my drive with the following hda1win98 4gig hda2/ 100megs hda2swap 64mgegs hda3/usr 2gig i want to have a lilo.conf file be able to boot either win98. i can' figure out what the image=? for the win98 part should be. please can somebody email me their copy of the linux.conf or tell me what to do. I looked into the documentation of lilo and looked on the mail archives and couldn't find anything. thank you Paul
Re: Yet another lilo question!!!
On Fri, 6 Nov 1998, Paul McDermott wrote: What I want to do is very simple. Yet i can't find a solution to the problem. Here is the situation. (I am asking for someone else i may not have all the correct informatiofn) partion my drive with the following hda1 win98 4gig hda2/ 100megs hda2swap 64mgegs hda3 /usr 2gig i want to have a lilo.conf file be able to boot either win98. i can' figure out what the image=? for the win98 part should be. please can somebody email me their copy of the linux.conf or tell me what to do. I looked into the documentation of lilo and looked on the mail archives and couldn't find anything. thank you Paul I use this, change it for yourself, and it should work fine.: boot=/dev/hda install=/boot/boot.b map=/boot/map compact vga=5 delay=100 default=linux image=/vmlinuz label=linux root=/dev/hdc1 read-only password=password restricted image=/vmlinuz.old label=oldlinux root=/dev/hdc1 optional read-only other=/dev/hda1 label=Win98 loader=/boot/chain.b table=/dev/hda Michael Beattie ([EMAIL PROTECTED]) PGP Key available, reply with pgpkey as subject. - I've got places to go... People to annoy. - Debian GNU/Linux Ooohh You are missing out!
Lilo question
I have a 240mb hard drive and a 850mb hard drive in my computer. I have my partions set up like this hda1 dos 210mb (soon to be open dos) hda2 boot for linux 10mb hda3 swap for linux 20mb hdc1 ext2 root partion for linux(850mb) now I was told by a friend to do my partions this way after I moved my data over from old 204mb ...(thanks for the help on that) now my problem is this I can't get the hda2 partion to boot? I have run and rerun lilo after makeing the lilo.conf refer to my new hd and the new partion sceme. the changes are boot /dev/hda2 root /dev/hdc1 from boot /dev/hdb1 root /dev/hdb1 but when I run lilo (after booting from the rescue/install disk) I get this message Added 2.0.30a * creat /boo/boot.0302 no such file of directory ... please any help would be appreceaited -kevin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
