Re: Lilo Help
These steps form the 'Gentoo' install procedure might help when using chroot to to such things. I believe running lilo without a /proc will cause it to at least whine... -- __ | 0|___||. Andrew Gaunt - Computing Development Environment _| _| : : } Lucent Intranet: http://mvcde.inse.lucent.com/~quantum -(O)-==-o\ Internet: http://www.gaunt.org mount -t proc proc /mnt/gentoo/proc cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf chroot /mnt/gentoo /bin/bash Kenneth E. Lussier wrote: On Tue, 2004-06-22 at 12:18, Mansur, Warren wrote: - Open a terminal - Go to the directory that contains your original mounted hard drive - executed 'chroot' so that now your hard drive looks like '/' instead Ah, yes... chroot. I knew I was forgetting something. Thanks, Warren! It has been so long since I hosed up Lilo But, as a side note to anyone that may encounter this, it does not work from Knoppix. I chrooted /mnt/hda4 (my root drive), and made sure everything is as it should be. It was. I tried to run lilo, and I got errors about open /dev/hda: permission denied. I made sure I was root, I made sure everything had correct permissions. I was, and everything did. I tried a few other things, and I got permission denied errors on /dev/null, too. Apparently, no matter what you do, Knoppix just won't let you work with files in /dev. I even changed the permissions to a+rwx on a few things (that it let me do), and I still couldn't run lilo or write to /dev/null. So, I used a Debian install/rescue disk, did everything exactly the same, and it worked fine. Things that make you go WTF?!?!?!?! Thanks, Kenny ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Lilo Help
Title: Lilo Help Hi, Yes first you need to use a boot CD that can mount your original disk (such as your Knoppx CD). Next, execute these steps: - Open a terminal - Go to the directory that contains your original mounted hard drive - executed 'chroot' so that now your hard drive looks like '/' instead of '/mnt/hard_drive' (or whatever it's mounted as) - Run lilo to get it to re-write the boot record to the disk Cheers, Warren -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Kenny LussierSent: Tuesday, June 22, 2004 12:13 PMTo: [EMAIL PROTECTED]Subject: Lilo Help Hi All,While updating my system, I managed to fsck it pretty good. When I boot, I get LI and it stops. I remember that that means that the second stage loader doesn't take over. I just don't remember how to fix it. I can boot up Knoppix and mount the file systems, and everything seems to be there. Can anyone smack me upside the head with a clue stick on how to fix this while I go searching google?TIA,Kenny
RE: Lilo Help
On Tue, 2004-06-22 at 12:18, Mansur, Warren wrote: - Open a terminal - Go to the directory that contains your original mounted hard drive - executed 'chroot' so that now your hard drive looks like '/' instead Ah, yes... chroot. I knew I was forgetting something. Thanks, Warren! It has been so long since I hosed up Lilo But, as a side note to anyone that may encounter this, it does not work from Knoppix. I chrooted /mnt/hda4 (my root drive), and made sure everything is as it should be. It was. I tried to run lilo, and I got errors about open /dev/hda: permission denied. I made sure I was root, I made sure everything had correct permissions. I was, and everything did. I tried a few other things, and I got permission denied errors on /dev/null, too. Apparently, no matter what you do, Knoppix just won't let you work with files in /dev. I even changed the permissions to a+rwx on a few things (that it let me do), and I still couldn't run lilo or write to /dev/null. So, I used a Debian install/rescue disk, did everything exactly the same, and it worked fine. Things that make you go WTF?!?!?!?! Thanks, Kenny ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
RE: Lilo Help
By default, KNOPPIX mounts hard drive partitions with the ro flag. In other words, no writing allowed. 8) There's a way to mount it rw through the gui, but I don't remember it off the top of my head. You should be able to do it from the command line, or so I would imagine. -- The best firewall is a pair of wire cutters. -Unknown, from the net Cole Tuininga Lead Developer Code Energy, Inc [EMAIL PROTECTED] PGP Key ID: 0x43E5755D ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Lilo Help
On Tue, Jun 22, 2004 at 01:59:38PM -0400, Cole Tuininga wrote: By default, KNOPPIX mounts hard drive partitions with the ro flag. In other words, no writing allowed. 8) There's a way to mount it rw through the gui, but I don't remember it off the top of my head. You should be able to do it from the command line, or so I would imagine. I've been using knoppix to bootstrap Debian stable to new boxes we're getting. You can mount R/W by hand. If it's already mounted, you should be able to mount -o remount,rw /dev/hda and you won't have to umount/mount the partition. -Mark signature.asc Description: Digital signature
Re: Lilo Help
On Tue, 2004-06-22 at 14:16, Mark Komarinski wrote: It was mounted rw. I could touch a file, I could delete files, I could change permissions, etc. It just wouldn't let me do anything in /dev, and only in /dev. Oh right. Was /proc mounted? Oddly enough, that came up in a conversation I had with someone else. At first it wasn't. I did a mount -a and got everything mounted, and everything looked great. But nope, nothing changed. /dev was still unavailable. I'm pretty sure that it must be something that I did wrong, I just don't know what. And, I don't know of anyone that has done this in Knoppix. The debian cd worked just fine. My system is purring along just fine now. I just couldn't believe that I couldn't do it in Knoppix C-Ya, Kenny signature.asc Description: This is a digitally signed message part
RE: LILO
-Original Message- From: Stephen Ryan [mailto:sryan;gargantubrain.dartmouth.edu] Sent: Friday, October 25, 2002 10:46 AM To: [EMAIL PROTECTED] Subject: Re: LILO On Fri, 2002-10-25 at 10:25, Price, Erik wrote: Hi, On my work computer (which currently has one drive for Win2k and another drive for Debian3.0), I had at one time installed SuSE Linux. I later wrote Debian3.0 over the SuSE Linux install, but forgot that I had installed LILO from SuSE. I boot into Debian by using a boot disk. When the computer boots up, if I don't have the Debian boot disk in the floppy drive, the SuSE LILO choice comes up, and if I forget to choose Windows, it tries to boot the SuSE distro. I guess the Debian install never overwrote the vmlinuz file pointed to by the SuSE LILO. (It is definitely booting the SuSE distro b/c the Debian boot output is very different from the SuSE boot output and when the prompt comes up, it's the old name for the computer when I had SuSE on it, not the new one that I gave the machine when I installed Debian). So my question is this -- if I use apt-get to install LILO from Debian, will it overwrite the LILO that's already there from SuSE? Safely? I'd like to kill a few birds with one stone -- 1) No longer use a boot disk to boot into Debian 2) Set the system to boot Windows by default 3) Get rid of the SuSE LILO screen and the inadvertent boot into the SuSE distro I would assume that I could do this by installing LILO from Debian. Ideally it will overwrite the LILO that was installed by SuSE, and then I can run the LILO commands to change the defaults. But I thought I'd run it by the list first, so I don't screw anything up. Sounds good to me. You'll just have to put a default line in the block for Windows, and boot=/dev/hda at the top to make sure that this lilo overwrites anything previously installed. Well, the only problem is that it appears that LILO *is* installed by default by my Debian installation, only it's not active or whatever the term is, since the SuSE LILO screen still comes up. Because this involves writing to MBR and /dev/sda, I'm really hesitant to do anything that could jeopardize the Windows disk (sda has windows, sdb has Debian) -- paranoid, actually. Having never configured a LILO.conf file before, I was wondering if someone could post a copy of theirs (ideally one similar to my own setup, with Windows on one disk and Linux on another). TIA, Erik ___ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
