Re: problem installing grub-legacy
On Sun, Mar 28, 2010 at 05:25:34AM +, T o n g wrote: hi, Long story, I don't want Grub2/Grub-PC, etc, but get upgraded to it. Now I can't go back, because grub-common is listed as a dependency of grub- legacy. But the grub-common package has been upgraded for use with version 2 only. I posted this past week about grub-common confusion that turned a simple legacy install into a long session. Grub-common rides in with legacy and makes an /etc/grub.d directory and scatters files all over the /boot/grub directory, including grub.cfg . But then it just sits there and tries to look like Grub-PC is installed. My system still boots off /boot/grub/menu.lst, kernel updates and update-grub still modify menu.lst, ^c still drops into a grub 0.97 terminal from the boot menu. I did another legacy install last night. I do think I remember getting Grub-PC in some dependency resolution, but I was able to remove it and install legacy without forcing anything. -- Kind Regards, Freeman http://bugs.debian.org/release-critical/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100329075704.ga4...@europa.office
Conclusion: problem installing grub-legacy
On Mon, 29 Mar 2010 00:57:04 -0700, Freeman wrote: I don't want Grub2/Grub-PC, etc, but get upgraded to it. Now I can't go back, because grub-common is listed as a dependency of grub- legacy. But the grub-common package has been upgraded for use with version 2 only. I posted this past week about grub-common confusion that turned a simple legacy install into a long session. Grub-common rides in with legacy and makes an /etc/grub.d directory and scatters files all over the /boot/grub directory, including grub.cfg . But then it just sits there and tries to look like Grub-PC is installed. Yes, I saw that. In fact, you can see that my words are borrowed from yours, :-) Just that I wasn't sure of the solution. My system still boots off /boot/grub/menu.lst, kernel updates and update-grub still modify menu.lst, ^c still drops into a grub 0.97 terminal from the boot menu. I did another legacy install last night. I do think I remember getting Grub-PC in some dependency resolution, but I was able to remove it and install legacy without forcing anything. OK, thanks for the explanation. FYI, I hate grub-common messing up with my /boot/grub and /etc/grub.d directory, so I'll use 'equivs' to create a dummy packages to circumvent such silly package dependencies. equivs - Circumvent Debian package dependencies This package provides a tool to create Debian packages that only contain dependency information. HTH -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/hoqjia$os...@dough.gmane.org
Re: Conclusion: problem installing grub-legacy
On Mon, Mar 29, 2010 at 04:12:58PM +, T o n g wrote: On Mon, 29 Mar 2010 00:57:04 -0700, Freeman wrote: I don't want Grub2/Grub-PC, etc, but get upgraded to it. Now I can't go back, because grub-common is listed as a dependency of grub- legacy. But the grub-common package has been upgraded for use with version 2 only. I posted this past week about grub-common confusion that turned a simple legacy install into a long session. Grub-common rides in with legacy and makes an /etc/grub.d directory and scatters files all over the /boot/grub directory, including grub.cfg . But then it just sits there and tries to look like Grub-PC is installed. Yes, I saw that. In fact, you can see that my words are borrowed from yours, :-) Just that I wasn't sure of the solution. Right, missed that. Good choice of words. :-) ... FYI, I hate grub-common messing up with my /boot/grub and /etc/grub.d directory, so I'll use 'equivs' to create a dummy packages to circumvent such silly package dependencies. equivs - Circumvent Debian package dependencies This package provides a tool to create Debian packages that only contain dependency information. Noted, and thanks. I learn more than just one thing daily on this list. (Which is easy given my starting point.) -- Kind Regards, Freeman http://bugs.debian.org/release-critical/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100329174726.ga27...@europa.office
Re: problem installing grub-legacy
Stephen Powell wrote: Aren't you glad you use Dial? Don't you wish everybody did? s/Dial/lilo/ Given that I have in the past spent up to 2 days remotely walking family members through fixing machines that booted to LI or LIL .. no. I only wish lilo on enemies -- but still prefer enemies use soap. But seriously, it's obvious that somebody messed up with the package dependencies. There's not much point in having a grub-legacy package if it can't be installed, now is there? Except that's is clearly not the case that grub-legacy cannot be installed, if you actually look at the dependencies of grub-common. I have grub-legacy installed here, works fine. -- see shy jo signature.asc Description: Digital signature
Re: problem installing grub-legacy
On Mon, 29 Mar 2010 15:46:28 -0400 (EDT), Joey Hess wrote: Stephen Powell wrote: Aren't you glad you use Dial? Don't you wish everybody did? s/Dial/lilo/ Given that I have in the past spent up to 2 days remotely walking family members through fixing machines that booted to LI or LIL .. no. I only wish lilo on enemies -- but still prefer enemies use soap. Interesting. I've been using Linux for 10 years, and I've never seen, or even heard of, the error you describe. I'm sorry your family members had trouble with it. For me, it has always worked perfectly. But seriously, it's obvious that somebody messed up with the package dependencies. There's not much point in having a grub-legacy package if it can't be installed, now is there? Except that's is clearly not the case that grub-legacy cannot be installed, if you actually look at the dependencies of grub-common. I have grub-legacy installed here, works fine. The OP claimed that he could not install. I took his word for it. But he has subsequently found a way to circumvent his problems. I'm glad he found a way to do what he wanted to do. But I frankly don't see why grub-legacy requires grub-common. It brings in a lot of unnecessary files, from what I can see. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1370107920.167581269895486703.javamail.r...@md01.wow.synacor.com
Re: problem installing grub-legacy
T o n g wrote: hi, Long story, I don't want Grub2/Grub-PC, etc, but get upgraded to it. Now I can't go back, because grub-common is listed as a dependency of grub- legacy. But the grub-common package has been upgraded for use with version 2 only. Comment? Thanks I have such problem about two weeks with my Dedian testing working under a virtual machine. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4baf32d6.7000...@gmail.com
Re: problem installing grub-legacy
On Sun, 28 Mar 2010 01:25:34 -0400 (EDT), Tong wrote: Long story, I don't want Grub2/Grub-PC, etc, but get upgraded to it. Now I can't go back, because grub-common is listed as a dependency of grub- legacy. But the grub-common package has been upgraded for use with version 2 only. I don't mean to make light of your problem, but this reminds me of an old bath soap commercial. Many years ago, Dial soap had an advertising slogan that went like this: Aren't you glad you use Dial? Don't you wish everybody did? s/Dial/lilo/ No doubt my friends and acquaintances on this list will accuse me of having a lilo fixation, but this opportunity was too good to pass up. But seriously, it's obvious that somebody messed up with the package dependencies. There's not much point in having a grub-legacy package if it can't be installed, now is there? As I see it, you have the following options: (1) Force grub-legacy to be installed with overrides to the package management system, leaving you with a broken package management system. (2) Live with grub-pc until somebody gets their act together and fixes this problem, or (3) Forget the whole ugly grub mess and switch to lilo. I know what I would do, but it's your call. -- .''`. Stephen Powellzlinux...@wowway.com : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1004221449.22262471269833008563.javamail.r...@md01.wow.synacor.com
problem installing grub-legacy
hi, Long story, I don't want Grub2/Grub-PC, etc, but get upgraded to it. Now I can't go back, because grub-common is listed as a dependency of grub- legacy. But the grub-common package has been upgraded for use with version 2 only. Comment? Thanks -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/homp8e$fa...@dough.gmane.org
