menu.lst problem
Hi, It seems to me that every time I do some upgrade via apt-get, maybe it's kernel upgrades, my menu.lst entries changes from /dev/sda1 to /dev/hda1. As a result, the system don't find the disk. It occurs to me like three times already. Why does it keep on getting changed incorrectly? Is there anyway to fix this at the time of the upgrade? Because I don't think I been shown an option to keep my menu.lst or anything like that. It may be worthy to note that I'm running on the testing branch. Timothy
Re: menu.lst problem
On Fri, Jul 31, 2009 at 14:18 +0800, Timothy Wu wrote: Hi, It seems to me that every time I do some upgrade via apt-get, maybe it's kernel upgrades, my menu.lst entries changes from /dev/sda1 to /dev/hda1. As a result, the system don't find the disk. It occurs to me like three times already. Why does it keep on getting changed incorrectly? I never experienced such behaviour. menu.lst should be touched only on kernel and grub upgrades. Do you have logs of the upgrades in question? If you have, look at them and come back with these in case you couldn't solve it on your own. Is there anyway to fix this at the time of the upgrade? Because I don't think I been shown an option to keep my menu.lst or anything like that. Sure there is but we have to know what's really happening, the info you provide isn't sufficient. It may be worthy to note that I'm running on the testing branch. If it's incorrect behaviour, report a bug. Regs Siggy -- Please don't Cc: me when replying, I might not see either copy. bsb-at-psycho-dot-informationsanarchistik-dot-de or:bsb-at-psycho-dot-i21k-dot-de O ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: Digital signature
Re: menu.lst problem
On Fri, 2009-07-31 at 14:18 +0800, Timothy Wu wrote: It seems to me that every time I do some upgrade via apt-get, maybe it's kernel upgrades, my menu.lst entries changes from /dev/sda1 to /dev/hda1. As a result, the system don't find the disk. It occurs to me like three times already. Why does it keep on getting changed incorrectly? Is there anyway to fix this at the time of the upgrade? Because I don't think I been shown an option to keep my menu.lst or anything like that. It may be worthy to note that I'm running on the testing branch. Check out the menu.lst file. snip ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=/dev/cciss/c0d0p1 ro console=tty0 console=ttyS1,19200n8 /snip Change the kopt line to fit you needs and you are done. Cheers Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: menu.lst problem
On Fri, Jul 31, 2009 at 2:31 PM, Siggy Brentrup deb...@psycho.i21k.dewrote: On Fri, Jul 31, 2009 at 14:18 +0800, Timothy Wu wrote: Hi, It seems to me that every time I do some upgrade via apt-get, maybe it's kernel upgrades, my menu.lst entries changes from /dev/sda1 to /dev/hda1. As a result, the system don't find the disk. It occurs to me like three times already. Why does it keep on getting changed incorrectly? I never experienced such behaviour. menu.lst should be touched only on kernel and grub upgrades. Do you have logs of the upgrades in question? If you have, look at them and come back with these in case you couldn't solve it on your own. Well, yeah kernel upgrade is what I am suspecting. (I did it via apt-get, though. Not via other method.) So this is completely expected then? And where might the upgrade log be? Timothy
Re: menu.lst problem
On Fri, Jul 31, 2009 at 3:53 PM, frank fr...@anotheria.net wrote: Check out the menu.lst file. snip ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=/dev/cciss/c0d0p1 ro console=tty0 console=ttyS1,19200n8 /snip Whoa! I didn't know text hidden in those comments are actually in-use. Thanks Frank, this is exactly what I need. :) Timothy
Re: menu.lst problem
On Friday July 31 2009 12:18:28 am Timothy Wu wrote: It seems to me that every time I do some upgrade via apt-get, maybe it's kernel upgrades, my menu.lst entries changes from /dev/sda1 to /dev/hda1. As a result, the system don't find the disk. It occurs to me like three times already. Why does it keep on getting changed incorrectly? Is there anyway to fix this at the time of the upgrade? Kernel updates run update-grub, which automatically and automagically creates the right menu.lst (at least that is what is supposed to happen). Your problem might be with the system map file, system.map. This file contains the linux device names that correspond to the grub device names. Take a look at the file and see if it is correct. If it is not right, you can try to regenerate it or you can edit it by hand. MM -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: menu.lst problem
On Fri, Jul 31, 2009 at 16:08 +0800, Timothy Wu wrote: On Fri, Jul 31, 2009 at 2:31 PM, Siggy Brentrup deb...@psycho.i21k.dewrote: On Fri, Jul 31, 2009 at 14:18 +0800, Timothy Wu wrote: Hi, It seems to me that every time I do some upgrade via apt-get, maybe it's kernel upgrades, my menu.lst entries changes from /dev/sda1 to /dev/hda1. As a result, the system don't find the disk. It occurs to me like three times already. Why does it keep on getting changed incorrectly? I never experienced such behaviour. menu.lst should be touched only on kernel and grub upgrades. Do you have logs of the upgrades in question? If you have, look at them and come back with these in case you couldn't solve it on your own. Well, yeah kernel upgrade is what I am suspecting. (I did it via apt-get, though. Not via other method.) So this is completely expected then? And where might the upgrade log be? *where logs belong* % ls -lRA /var/log/apt* /var/log/dpkg* -rw-r--r-- 1 root root 19954 2009-07-30 07:35 /var/log/aptitude -rw-r--r-- 1 root root5663 2009-06-08 04:35 /var/log/aptitude.1.gz -rw-r--r-- 1 root root 2008616 2009-07-29 19:40 /var/log/dpkg.log -rw-r- 1 root adm 1715230 2009-06-30 17:14 /var/log/dpkg.log.1 /var/log/apt: total 808 -rw--- 1 root root 727945 2009-07-30 07:35 term.log -rw--- 1 root root 88104 2009-06-30 17:15 term.log.1.gz This is on a box running Debian/squeeze hth Siggy -- Please don't Cc: me when replying, I might not see either copy. bsb-at-psycho-dot-informationsanarchistik-dot-de or:bsb-at-psycho-dot-i21k-dot-de O ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: Digital signature
Re: menu.lst problem
On Fri, Jul 31, 2009 at 16:08 +0800, Timothy Wu wrote: On Fri, Jul 31, 2009 at 2:31 PM, Siggy Brentrup deb...@psycho.i21k.dewrote: On Fri, Jul 31, 2009 at 14:18 +0800, Timothy Wu wrote: Hi, It seems to me that every time I do some upgrade via apt-get, maybe it's kernel upgrades, my menu.lst entries changes from /dev/sda1 to /dev/hda1. As a result, the system don't find the disk. It occurs to me like three times already. Why does it keep on getting changed incorrectly? I never experienced such behaviour. menu.lst should be touched only on kernel and grub upgrades. Do you have logs of the upgrades in question? If you have, look at them and come back with these in case you couldn't solve it on your own. Well, yeah kernel upgrade is what I am suspecting. (I did it via apt-get, though. Not via other method.) So this is completely expected then? And where might the upgrade log be? Forgot to mention: *please*, /please/, _please_ cut down irrelevant stuff and use pastebin when showing us the logs. Siggy -- Please don't Cc: me when replying, I might not see either copy. bsb-at-psycho-dot-informationsanarchistik-dot-de or:bsb-at-psycho-dot-i21k-dot-de O ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: Digital signature
Re: menu.lst problem
On Fri, Jul 31, 2009 at 16:48 +0800, Timothy Wu wrote: On Fri, Jul 31, 2009 at 3:53 PM, frank fr...@anotheria.net wrote: Check out the menu.lst file. snip ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specific kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro ## kopt_2_6_8=root=/dev/hdc1 ro ## kopt_2_6_8_2_686=root=/dev/hdc2 ro # kopt=root=/dev/cciss/c0d0p1 ro console=tty0 console=ttyS1,19200n8 /snip Whoa! I didn't know text hidden in those comments are actually in-use. Thanks Frank, this is exactly what I need. :) ARRGs, that's the 1st program I saw in 35 year of programming that analyzes comments to change behaviour (apart from documentation generators). Siggy -- Please don't Cc: me when replying, I might not see either copy. bsb-at-psycho-dot-informationsanarchistik-dot-de or:bsb-at-psycho-dot-i21k-dot-de O ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: Digital signature
Re: menu.lst problem
In 20090731124204.gw7...@keuner.winnegan.fake, Siggy Brentrup wrote: On Fri, Jul 31, 2009 at 16:48 +0800, Timothy Wu wrote: On Fri, Jul 31, 2009 at 3:53 PM, frank fr...@anotheria.net wrote: Check out the menu.lst file. Whoa! I didn't know text hidden in those comments are actually in-use. They aren't really comments. Reading the file would have clarified that. ARRGs, that's the 1st program I saw in 35 year of programming that analyzes comments to change behaviour (apart from documentation generators). 1. It is well documented. Basically everything you need to know is in the file and there are additional man pages. 2. The lines starting this a single '#' are comments to *grub*. The lines between the markers starting with a single '#' are not comments *update- grub*. 3. Lines starting with a single '#' are comments in C *unless* the '#' is immediately followed by a pre-processor command. This is similar -- you can think of update-grub as a GRUB menu.lst pre-processor. 4. It's been that way for a very long time. I'm not sure how GRUB2 will affect it, but I don't think it will change for GRUB1 for the foreseeable future. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: menu.lst problem
Boyd Stephen Smith Jr. wrote:
In 20090731124204.gw7...@keuner.winnegan.fake, Siggy Brentrup wrote:
On Fri, Jul 31, 2009 at 16:48 +0800, Timothy Wu wrote:
On Fri, Jul 31, 2009 at 3:53 PM, frank fr...@anotheria.net wrote:
Check out the menu.lst file.
Whoa! I didn't know text hidden in those comments are actually in-use.
--deleted--
3. Lines starting with a single '#' are comments in C *unless* the '#' is
immediately followed by a pre-processor command. This is similar -- you can
think of update-grub as a GRUB menu.lst pre-processor.
The sharp/hash symbol is a preprocessor indicator. Pure C has never
supported anything other than '/*...*/' for comments. C++ added the
single line comment marker '//' (double forward slash).
#include stdio.h
# Is this a comment?
main()
{
printf(Hello, world.\n);
}
$ make tstit
cc tstit.c -o tstit
tstit.c:4:3: error: invalid preprocessing directive #Is
make: *** [tstit] Error 1
$
--deleted--
It is possible to use the preprocessor to do weird and wonderful,
things, so I believe you could even have it ignore lines beginning with
a hash mark, effectively treating them as comments, but that is
definitely not normal.
--
Bob McGowan
smime.p7s
Description: S/MIME Cryptographic Signature
Re: menu.lst problem
In 4a731c61.3080...@symantec.com, Bob McGowan wrote: Boyd Stephen Smith Jr. wrote: 3. Lines starting with a single '#' are comments in C *unless* the '#' is immediately followed by a pre-processor command. This is similar -- you can think of update-grub as a GRUB menu.lst pre-processor. The sharp/hash symbol is a preprocessor indicator. Pure C has never supported anything other than '/*...*/' for comments. C++ added the single line comment marker '//' (double forward slash). From the latest C standard: 6.10 Preprocessing directives Syntax preprocessing-file: groupopt group: group-part group group-part group-part: if-section control-line text-line # non-directive [...] A text line shall not begin with a # preprocessing token. A non-directive shall not begin with any of the directive names appearing in the syntax. It is possible to use the preprocessor to do weird and wonderful, things, so I believe you could even have it ignore lines beginning with a hash mark, effectively treating them as comments, but that is definitely not normal. From what I can tell, there's no additional requirements on the implementation for what to do with non-directives, but traditional C compilers would ignore them -- effectively making them comments. Since the standard doesn't specify what to do with them, any behavior is acceptable. I agree that they are not standard comments and are not accepted by your C compiler, which might be conforming. (FWIW, I don't believe gcc is completely conforming.) -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: menu.lst problem
On Fri, Jul 31, 2009 at 11:05 -0500, Boyd Stephen Smith Jr. wrote: In 20090731124204.gw7...@keuner.winnegan.fake, Siggy Brentrup wrote: On Fri, Jul 31, 2009 at 16:48 +0800, Timothy Wu wrote: On Fri, Jul 31, 2009 at 3:53 PM, frank fr...@anotheria.net wrote: Check out the menu.lst file. Whoa! I didn't know text hidden in those comments are actually in-use. They aren't really comments. Reading the file would have clarified that. ARRGs, that's the 1st program I saw in 35 year of programming that analyzes comments to change behaviour (apart from documentation generators). 1. It is well documented. Basically everything you need to know is in the file and there are additional man pages. Well documented mis-features still are mis-features. 2. The lines starting this a single '#' are comments to *grub*. The lines between the markers starting with a single '#' are not comments *update- grub*. ^ to ? 3. Lines starting with a single '#' are comments in C *unless* the '#' is immediately followed by a pre-processor command. This is similar -- you can think of update-grub as a GRUB menu.lst pre-processor. _This_statement_is_wrong_. # in C is a preprocessing token, look into the Ansi C standard ISO/IEC 9899:TC3 commonly known as c99; I found a reference to a PDF on http://en.wikipedia.org/wiki/C99, but be warned, it's no easy reading. On an aside gnu cpp deviates from my reading of the standard in that it removes comments; but that matters only insofar as cpp output is even less human readable than it might be. 4. It's been that way for a very long time. I'm not sure how GRUB2 will affect it, but I don't think it will change for GRUB1 for the foreseeable future. An argument starting like this never has been very convincing :) I can't remember seeing anything like this when I last edited a menu.lst back in '04. I still have a not yet recovered root FS on my vaio, nothing indicating that change can be found, must have occurred in the meantime. Be assured if I had been with the project when it occurred, I'd argued against it. IMHO this is configuration that can and should be handled using debconf, but I'm almost certain YMDV. With grub being replaced by grub2 all this doesn't really matter. Regs Siggy -- Please don't Cc: me when replying, I might not see either copy. bsb-at-psycho-dot-informationsanarchistik-dot-de or:bsb-at-psycho-dot-i21k-dot-de O ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: Digital signature
