Re: Wheezy GRUB problem
On Thu, Aug 7, 2014 at 7:44 PM, Brian a...@cityscape.co.uk wrote: On Tue 05 Aug 2014 at 09:36:18 +0200, Artifex Maximus wrote: Hello! I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian partition installed. Not recommended I know but basically works. Until last upgrade when my GRUB loader only writes GRUB then halts. Or at least not continue loading. No errors just stops. I have tried latest (7.6.0) Debian install disc Recovery function to reinstall grub with grub-install /dev/sda2 without success. Still just a GRUB line on screen when Debian partition is active. When I switch active partition back to XP it runs. I am able to mount sda2 from Debian installer and there is no fsck error. What messages did you get when did 'grub-install /dev/sda2'? Sorry I cannot recall exactly but something about some /dev/sda2/... file when execute shell on mounted /dev/sda2. With installer environment there was no grub-install just grub-installer. Because I do not know what is the difference I had not enough courage to execute. The good new I was able to recover my system with supergrub disk. I was able to boot into my original system with supergrub then update-grub. For sure I run grub-install -f /dev/sda2 and now I am using my good old Debian system. What was strange I got a lot of errors about fake start-stop-daemon and needed to rename start-stop-daemon.REAL to start-stop-daemon for a successful boot. No idea at all what, when, and why created that fake start-stop-daemon script. Hope no more surprise in my system. Bye, a -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/capkuxveouae+-uv1wmkjlb1ybjuowivx41pddthorjgszbh...@mail.gmail.com
Re: Wheezy GRUB problem
On Fri 08 Aug 2014 at 21:42:01 +0200, Artifex Maximus wrote: On Thu, Aug 7, 2014 at 7:44 PM, Brian a...@cityscape.co.uk wrote: On Tue 05 Aug 2014 at 09:36:18 +0200, Artifex Maximus wrote: Hello! I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian partition installed. Not recommended I know but basically works. Until last upgrade when my GRUB loader only writes GRUB then halts. Or at least not continue loading. No errors just stops. I have tried latest (7.6.0) Debian install disc Recovery function to reinstall grub with grub-install /dev/sda2 without success. Still just a GRUB line on screen when Debian partition is active. When I switch active partition back to XP it runs. I am able to mount sda2 from Debian installer and there is no fsck error. What messages did you get when did 'grub-install /dev/sda2'? Sorry I cannot recall exactly but something about some /dev/sda2/... file when execute shell on mounted /dev/sda2. With installer environment there was no grub-install just grub-installer. Because I do not know what is the difference I had not enough courage to execute. Recalling the exact wording of an onscreen message is not something human beings have evolved to do yet. :) I have the same problem myself. The good new I was able to recover my system with supergrub disk. I was able to boot into my original system with supergrub then update-grub. For sure I run grub-install -f /dev/sda2 and now I am using my good old Debian system. What was strange I got a lot of errors about fake start-stop-daemon and needed to rename start-stop-daemon.REAL to start-stop-daemon for a successful boot. No idea at all what, when, and why created that fake start-stop-daemon script. Hope no more surprise in my system. Glad you could sort it. Running 'grub-install --force' (-f is an invalid option) is obligatory to get grub to install itself in a partition. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/08082014222143.5a2cb6a1d...@desktop.copernicus.demon.co.uk
Re: Wheezy GRUB problem
On Tue 05 Aug 2014 at 09:36:18 +0200, Artifex Maximus wrote: Hello! I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian partition installed. Not recommended I know but basically works. Until last upgrade when my GRUB loader only writes GRUB then halts. Or at least not continue loading. No errors just stops. I have tried latest (7.6.0) Debian install disc Recovery function to reinstall grub with grub-install /dev/sda2 without success. Still just a GRUB line on screen when Debian partition is active. When I switch active partition back to XP it runs. I am able to mount sda2 from Debian installer and there is no fsck error. What messages did you get when did 'grub-install /dev/sda2'? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/07082014184256.e865cfb7d...@desktop.copernicus.demon.co.uk
Re: Wheezy GRUB problem
On Tue, Aug 5, 2014 at 4:14 PM, Gary Dale garyd...@torfree.net wrote: On 05/08/14 03:36 AM, Artifex Maximus wrote: Hello! I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian partition installed. Not recommended I know but basically works. Until last upgrade when my GRUB loader only writes GRUB then halts. Or at least not continue loading. No errors just stops. I have tried latest (7.6.0) Debian install disc Recovery function to reinstall grub with grub-install /dev/sda2 without success. Still just a GRUB line on screen when Debian partition is active. When I switch active partition back to XP it runs. I am able to mount sda2 from Debian installer and there is no fsck error. So my MBR is good and there is some error in sda2 partition loader which I cannot recover with grub-install. Any idea where to go then? Bye, a Why not try installing grub in the MBR? It usually can boot both Windows XP and Linux without problems. If you were using a version of Windows that required UEFI then you night have a problem, but not with XP. Thanks for your answer. I would like to keep my current configuration because it is more flexible I think. For example I just had to change boot partition to XP for a successful boot which is a very simple process. I've found supergrubdisk project and I will give it a try. I hope that works. As a last resort I would like to know how to convert my loader from VBR GRUB to MBR GRUB? Bye, a
Wheezy GRUB problem
Hello! I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian partition installed. Not recommended I know but basically works. Until last upgrade when my GRUB loader only writes GRUB then halts. Or at least not continue loading. No errors just stops. I have tried latest (7.6.0) Debian install disc Recovery function to reinstall grub with grub-install /dev/sda2 without success. Still just a GRUB line on screen when Debian partition is active. When I switch active partition back to XP it runs. I am able to mount sda2 from Debian installer and there is no fsck error. So my MBR is good and there is some error in sda2 partition loader which I cannot recover with grub-install. Any idea where to go then? Bye, a
Re: Wheezy GRUB problem
On 05/08/14 03:36 AM, Artifex Maximus wrote: Hello! I have a Wheezy system shared with MS XP. GRUB is not in MBR but in Debian partition installed. Not recommended I know but basically works. Until last upgrade when my GRUB loader only writes GRUB then halts. Or at least not continue loading. No errors just stops. I have tried latest (7.6.0) Debian install disc Recovery function to reinstall grub with grub-install /dev/sda2 without success. Still just a GRUB line on screen when Debian partition is active. When I switch active partition back to XP it runs. I am able to mount sda2 from Debian installer and there is no fsck error. So my MBR is good and there is some error in sda2 partition loader which I cannot recover with grub-install. Any idea where to go then? Bye, a Why not try installing grub in the MBR? It usually can boot both Windows XP and Linux without problems. If you were using a version of Windows that required UEFI then you night have a problem, but not with XP. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53e0e6b7.7070...@torfree.net
Re: Debian Wheezy Grub Problem
On Tue, Mar 12, 2013 at 2:59 PM, Stephen P. Molnar s.mol...@sbcglobal.net wrote: My main Linux computer (64bit CPU) is about six or seven years old now and has had a number of distributions running. As I haven't had any luck with upgrades, I've always done a complete installation. Currently the Grub boot menu has a number of choices: openSUSE Advanced options for openSUSE openSUSE 12.1 (x86_64) Advanced options for openSUSE 12.1 (x86_64) Debian GNU/Linux (6.0.5) Advanced options for Debian GNU/Linux (6.0.5) Debian GNU/Linux (6.0.4) Advanced options for Debian GNU/Linux (6.0.4) There are a number of things that I find puzzling. First of all, the most recent installation is Debian Wheezy/Testing (7.0), and, in fact, WebMin tells me that the installed Operating system is Debian Linux 7.0. In order to boot into what is now my default Linux, installed on /dev/hda I have to select the seventh option of the menu which is mislabeled as 6.0.4. I had successfully installed some of the distributions on other than /dev/hda, but the last several installation have been on the Primary Master HD. The computer boots well with the seventh entry in the menu, which is not the default. This is rather annoying. I have become thoroughly confused by the information I've found about grub2. I am not a hardware person and am rather loathe to make any changes to the boot loader, given my current high degree of mental entropy. I thought about switching to lilo and, in fact, tried that out successfully on a laptop running Wheeezy in a VM. When I tried that on the tower /sbin/lilo complained that it couldn't open /etc/lilo.conf, even though I used sudo. Fortunately, my act of desperation didn't render grub inoperable. You can set the default in /etc/default/grub as 'GRUB_DEFAULT=Debian GNU/Linux (6.0.4)'. -- 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/CAOdo=swb2kudl3pwdeatdb8u5dktq4ufve2zjtamcr7xeon...@mail.gmail.com
Re: Debian Wheezy Grub Problem
On Wed, 2013-03-13 at 04:34 -0400, Tom H wrote:
On Tue, Mar 12, 2013 at 2:59 PM, Stephen P. Molnar
s.mol...@sbcglobal.net wrote:
My main Linux computer (64bit CPU) is about six or seven years old now
and has had a number of distributions running. As I haven't had any
luck with upgrades, I've always done a complete installation.
Currently the Grub boot menu has a number of choices:
openSUSE
Advanced options for openSUSE
openSUSE 12.1 (x86_64)
Advanced options for openSUSE 12.1 (x86_64)
Debian GNU/Linux (6.0.5)
Advanced options for Debian GNU/Linux (6.0.5)
Debian GNU/Linux (6.0.4)
Advanced options for Debian GNU/Linux (6.0.4)
There are a number of things that I find puzzling.
First of all, the most recent installation is Debian Wheezy/Testing
(7.0), and, in fact, WebMin tells me that the installed Operating
system is Debian Linux 7.0. In order to boot into what is now my
default Linux, installed on /dev/hda I have to select the seventh
option of the menu which is mislabeled as 6.0.4.
I had successfully installed some of the distributions on other
than /dev/hda, but the last several installation have been on the
Primary Master HD.
The computer boots well with the seventh entry in the menu, which is
not the default. This is rather annoying.
I have become thoroughly confused by the information I've found about
grub2. I am not a hardware person and am rather loathe to make any
changes to the boot loader, given my current high degree of mental
entropy.
I thought about switching to lilo and, in fact, tried that out
successfully on a laptop running Wheeezy in a VM. When I tried that on
the tower /sbin/lilo complained that it couldn't open /etc/lilo.conf,
even though I used sudo. Fortunately, my act of desperation didn't
render grub inoperable.
You can set the default in /etc/default/grub as
'GRUB_DEFAULT=Debian GNU/Linux (6.0.4)'.
The automation for GRUB2 is crap, edit the grub.cfg manually, then you
also could tidy up grub.cfg and get rid of all the nonsense.
If you keep GRUB provided by an install that is less maintained you even
don't need to remove this automation. The updater or what it's called on
my machine, even does include installs that aren't existing ;). It just
takes a minute to edit grub.cfg directly and to get exactly what you
want, but you can study how to fix (configure) grub and spend a year to
anyway get a bad menu.
Many people claim that GRUB in general is crappy software, a lot of
professionals seem to prefer SYSLINUX. I don't know, I prefer GRUB
legacy, but I switched to GRUB2 when I planned to tested different
options to boot FreeBSD. I never tested different options, however, as
you can see, my grub.cfg is very clean:
$ cat /run/media/rocketmouse/q/boot/grub/grub.cfg
set timeout=8
set default='0'; if [ x$default = xsaved ]; then load_env; set
default=$saved_entry; fi
set color_normal='light-blue/black'; set
color_highlight='light-cyan/blue'
menuentry FreeBSD{
set root=(hd0,msdos1)
chainloader +1
}
menuentry 'Ubuntu Quantal,kernel 3.6.5-rt14' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb9' 'ro' 'quiet' ''
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
menuentry 'Ubuntu Quantal,kernel 3.5.0-18-lowlatency
threadirqs' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb9' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Quantal,kernel 3.5.0-18-lowlatency (recovery
mode)' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb9' 'ro' 'single'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Studio Quantal, Kernel 3.6.5-rt14' {
set root='(hd1,13)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb13' 'ro' 'quiet'
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
menuentry 'Ubuntu Studio Quantal, Kernel 3.5.0-18-lowlatency
threadirqs' {
set root='(hd1,13)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb13' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Studio Precise, Kernel 3.0.30 threadirqs' {
set root='(hd1,1)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.0.30' '/boot/vmlinuz-3.0.30'
'root=UUID=338316fb-364e-4a43-8deb-738127f878ce' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.0.30'
Re: Debian Wheezy Grub Problem
On Wed, Mar 13, 2013 at 10:00:35AM +0100, Ralf Mardorf wrote: The automation for GRUB2 is crap, edit the grub.cfg manually, then you also could tidy up grub.cfg and get rid of all the nonsense. root@tal:~# ls -al /boot/grub/grub.cfg -r--r--r-- 1 root root 3356 Mar 1 22:53 /boot/grub/grub.cfg Come on now Ralf, you know better than to offer advice like that. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- 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/20130313112832.GD14358@tal
Re: Debian Wheezy Grub Problem
On Thu, 2013-03-14 at 00:28 +1300, Chris Bannister wrote: On Wed, Mar 13, 2013 at 10:00:35AM +0100, Ralf Mardorf wrote: The automation for GRUB2 is crap, edit the grub.cfg manually, then you also could tidy up grub.cfg and get rid of all the nonsense. root@tal:~# ls -al /boot/grub/grub.cfg -r--r--r-- 1 root root 3356 Mar 1 22:53 /boot/grub/grub.cfg Come on now Ralf, you know better than to offer advice like that. I'm serious and I guess in this case my opinion for a change isn't eccentric. It's a bad fashion, that things we once configured by one file, now should be configured by several files. GRUB isn't an exception. Idiotic for many Debian based distros is, that it could be, that e.g. audio priorities are set by /etc/security/limits-conf and /etc/security/limits.d/audio.conf with different values, at the same time. xorg.conf today often is split too and well, I won't talk about other distros now, not using init anymore. -- 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/1363175985.6809.46.camel@archlinux
Re: Debian Wheezy Grub Problem
On Wed, Mar 13, 2013 at 5:00 AM, Ralf Mardorf
ralf.mard...@alice-dsl.net wrote:
On Wed, 2013-03-13 at 04:34 -0400, Tom H wrote:
You can set the default in /etc/default/grub as
'GRUB_DEFAULT=Debian GNU/Linux (6.0.4)'.
The automation for GRUB2 is crap, edit the grub.cfg manually, then you
also could tidy up grub.cfg and get rid of all the nonsense.
The fact that grub's finding all of the OP's installs means that it's
working perfectly well (even though its innards are ugly and overly
complex!
The OP's preferred kernel isn't the default because he has
'GRUB_DEFAULT=0' in /etc/default/grub. 'GRUB_DEFAULT=0' is the
upstream and distro default and it's what the majority of users want.
I've dumped grub from my laptop because I only need a boot manager and
not a boot loader. But I still use it on my servers and VMs and it
works perfectly well.
If you keep GRUB provided by an install that is less maintained you even
don't need to remove this automation. The updater or what it's called on
my machine, even does include installs that aren't existing ;). It just
takes a minute to edit grub.cfg directly and to get exactly what you
want, but you can study how to fix (configure) grub and spend a year to
anyway get a bad menu.
If you really want to write out your own complete grub.cfg, you should
use 40_custom and either delete or chmod -x the other files in
/etc/grub.d/.
menuentry 'Ubuntu Quantal, kernel 3.6.5-rt14' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb9' 'ro' 'quiet' ''
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
So not only are you advising people to edit a file that'll be
overwritten when linux-image is upgraded but you're using unorthodox
legacy_kernel and legacy_initrd commands simply for the sake of
being different. I don't have a squeeze install on which to check but
I don't think that its version of grub has legacycfg.mod, which you
need for the legacy_... commands.
--
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/CAOdo=SxJ+oOa0TshXob6e8xR2dr02nZ2FREs=M=w931hxnv...@mail.gmail.com
Re: Debian Wheezy Grub Problem
On Wed, 2013-03-13 at 09:07 -0400, Tom H wrote:
menuentry 'Ubuntu Quantal, kernel 3.6.5-rt14' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb9' 'ro' 'quiet' ''
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
So not only are you advising people to edit a file that'll be
overwritten when linux-image is upgraded but you're using unorthodox
legacy_kernel and legacy_initrd commands simply for the sake of
being different. I don't have a squeeze install on which to check but
I don't think that its version of grub has legacycfg.mod, which you
need for the legacy_... commands.
I missed that, wasn't care full enough. The entries were transformed
from menu.lst to grub.cfg by an Ubuntu or Debian application, I didn't
edit them manually.
--
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/1363184486.6809.131.camel@archlinux
Re: Debian Wheezy Grub Problem
On 2013-03-13 12:59 +0100, Ralf Mardorf wrote: On Thu, 2013-03-14 at 00:28 +1300, Chris Bannister wrote: On Wed, Mar 13, 2013 at 10:00:35AM +0100, Ralf Mardorf wrote: The automation for GRUB2 is crap, edit the grub.cfg manually, then you also could tidy up grub.cfg and get rid of all the nonsense. For anyone who actually thinks about following Ralf's advice: if you do that, it is also necessary to divert /usr/sbin/update-grub and replace it with something harmless, say a symlink to /bin/true. Otherwise the local changes to grub.cfg will be overwritten. root@tal:~# ls -al /boot/grub/grub.cfg -r--r--r-- 1 root root 3356 Mar 1 22:53 /boot/grub/grub.cfg Come on now Ralf, you know better than to offer advice like that. I'm serious and I guess in this case my opinion for a change isn't eccentric. It's a bad fashion, that things we once configured by one file, now should be configured by several files. This is not bad fashion, but rather a useful (and often the only sane) way for multiple packages to add configuration snippets without stomping on each other and on the local admin's changes. GRUB isn't an exception. The grub.cfg file is special in that it's generated from other files. Part of the reason is that it lives in /boot and not /etc. Idiotic for many Debian based distros is, that it could be, that e.g. audio priorities are set by /etc/security/limits-conf and /etc/security/limits.d/audio.conf with different values, at the same time. There does not seem to be a package in Debian which ships /etc/security/limits.d/audio.conf? At least apt-file does not find any. And certainly packages must not touch /etc/security/limits.conf, since that file is owned by libpam-modules. xorg.conf today often is split too and well, There is no xorg.conf at all by default these days, thankfully. Cheers, Sven -- 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/87ppz3rr6t@turtle.gmx.de
Re: Debian Wheezy Grub Problem
On Wed, 2013-03-13 at 21:16 +0100, Sven Joachim wrote: For anyone who actually thinks about following Ralf's advice: if you do that, it is also necessary to divert /usr/sbin/update-grub and replace it with something harmless, say a symlink to /bin/true. Otherwise the local changes to grub.cfg will be overwritten. It's better to use GRUB of a locked Linux install. If there would be an upgrade for GRUB 2 /usr/sbin/update-grub would be reinstalled. -- 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/1363213197.654.93.camel@archlinux
Re: Debian Wheezy Grub Problem
On 2013-03-13 23:19 +0100, Ralf Mardorf wrote: On Wed, 2013-03-13 at 21:16 +0100, Sven Joachim wrote: For anyone who actually thinks about following Ralf's advice: if you do that, it is also necessary to divert /usr/sbin/update-grub and replace it with something harmless, say a symlink to /bin/true. Otherwise the local changes to grub.cfg will be overwritten. It's better to use GRUB of a locked Linux install. If there would be an upgrade for GRUB 2 /usr/sbin/update-grub would be reinstalled. Not if you move it away with dpkg-divert(8); that's what I meant with it is necessary to _divert_ /usr/sbin/update-grub, just overwriting it is indeed not enough. Sorry for my brevity. Cheers, Sven -- 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/87obemrjli@turtle.gmx.de
Re: Debian Wheezy Grub Problem
On Wed 13 Mar 2013 at 23:19:57 +0100, Ralf Mardorf wrote: On Wed, 2013-03-13 at 21:16 +0100, Sven Joachim wrote: For anyone who actually thinks about following Ralf's advice: if you do that, it is also necessary to divert /usr/sbin/update-grub and replace it with something harmless, say a symlink to /bin/true. Otherwise the local changes to grub.cfg will be overwritten. It's better to use GRUB of a locked Linux install. If there would be an upgrade for GRUB 2 /usr/sbin/update-grub would be reinstalled. Sven's advice is expanded on here: http://lists.gnu.org/archive/html/grub-devel/2011-03/msg00111.html On Debian/Ubuntu, you can reliably disable all automatic calls to update-grub like this: dpkg-divert --rename --add /usr/sbin/update-grub ln -s /bin/true /usr/sbin/update-grub (To undo this, 'rm /usr/sbin/update-grub; dpkg-divert --rename --remove /usr/sbin/update-grub'.) I've used this technique successfully for some time and cannot see your suggestion offering any advantage. -- 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/20130313231126.GQ32477@desktop
Re: Debian Wheezy Grub Problem
On Thu, 2013-03-14 at 00:00 +0100, Sven Joachim wrote: dpkg-divert http://www.debian-administration.org/articles/118 I wasn't aware that it's that easy :D, not especially regarding to the GRUB issue, but it would have saved me some work with other packages. OTOH, because I wasn't aware of this, I learned a lot of other things. -- 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/1363216512.654.118.camel@archlinux
Debian Wheezy Grub Problem
My main Linux computer (64bit CPU) is about six or seven years old now and has had a number of distributions running. As I haven't had any luck with upgrades, I've always done a complete installation. Currently the Grub boot menu has a number of choices: openSUSE Advanced options for openSUSE openSUSE 12.1 (x86_64) Advanced options for openSUSE 12.1 (x86_64) Debian GNU/Linux (6.0.5) Advanced options for Debian GNU/Linux (6.0.5) Debian GNU/Linux (6.0.4) Advanced options for Debian GNU/Linux (6.0.4) There are a number of things that I find puzzling. First of all, the most recent installation is Debian Wheezy/Testing (7.0), and, in fact, WebMin tells me that the installed Operating system is Debian Linux 7.0. In order to boot into what is now my default Linux, installed on /dev/hda I have to select the seventh option of the menu which is mislabeled as 6.0.4. I had successfully installed some of the distributions on other than /dev/hda, but the last several installation have been on the Primary Master HD. The computer boots well with the seventh entry in the menu, which is not the default. This is rather annoying. I have become thoroughly confused by the information I've found about grub2. I am not a hardware person and am rather loathe to make any changes to the boot loader, given my current high degree of mental entropy. I thought about switching to lilo and, in fact, tried that out successfully on a laptop running Wheeezy in a VM. When I tried that on the tower /sbin/lilo complained that it couldn't open /etc/lilo.conf, even though I used sudo. Fortunately, my act of desperation didn't render grub inoperable. I would appreciate any insights. Thanks in advance. -- 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/20130312145952.30b5e...@abnormal.att.net
Re: Debian Wheezy Grub Problem
On 03/12/2013 02:59 PM, Stephen P. Molnar wrote: My main Linux computer (64bit CPU) is about six or seven years old now and has had a number of distributions running. As I haven't had any luck with upgrades, I've always done a complete installation. Currently the Grub boot menu has a number of choices: openSUSE Advanced options for openSUSE openSUSE 12.1 (x86_64) Advanced options for openSUSE 12.1 (x86_64) Debian GNU/Linux (6.0.5) Advanced options for Debian GNU/Linux (6.0.5) Debian GNU/Linux (6.0.4) Advanced options for Debian GNU/Linux (6.0.4) There are a number of things that I find puzzling. First of all, the most recent installation is Debian Wheezy/Testing (7.0), and, in fact, WebMin tells me that the installed Operating system is Debian Linux 7.0. In order to boot into what is now my default Linux, installed on /dev/hda I have to select the seventh option of the menu which is mislabeled as 6.0.4. I had successfully installed some of the distributions on other than /dev/hda, but the last several installation have been on the Primary Master HD. The computer boots well with the seventh entry in the menu, which is not the default. This is rather annoying. I have become thoroughly confused by the information I've found about grub2. I am not a hardware person and am rather loathe to make any changes to the boot loader, given my current high degree of mental entropy. I thought about switching to lilo and, in fact, tried that out successfully on a laptop running Wheeezy in a VM. When I tried that on the tower /sbin/lilo complained that it couldn't open /etc/lilo.conf, even though I used sudo. Fortunately, my act of desperation didn't render grub inoperable. I was where you are so know your pain. I search the net for how to customize the Grup2 menu and finally got it working using this link. http://lists.debian.org/debian-user/2013/01/msg00363.html. You have to configure a custom file in /etc/grub.d/I used 06_custom using the, already there 40_custom, as a guide. To be sure you can still boot if you made a mistake, be sure you have a Super Grub CD available. Google customizing grup2 for more information; HTH -- WT -- 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/513f9ed6.9090...@gmail.com
