You are not logged in.

#1 2011-08-25 10:24:11

whoops
Member
Registered: 2009-03-19
Posts: 891

[solved]Ignore menu.lst.pacnew?

Hi!

Just to be on the safe side...:
I was about to change the filenames in my menu.lst and remove the symlinks as mentioned here a while ago: http://www.archlinux.org/news/changes-t … filenames/

When I looked at the menu.lst.pacnew I noticed that it looks very different from the default file I remember...:

kernel /vmlinuz-linux [...]
initrd /initramfs-linux.img

Sort of looks as if I shouldn't use the full directory name (/boot/...) any more here like I used to...!? (doesn't sound like a good idea to me to try that...? big_smile). Also the default entry for "fallback" isn't there any more so I wonder if it's still supported like this...

Can those changes to the default menu.lst safely be ignored or do they mean anything?


thx!

Last edited by whoops (2011-08-25 11:49:37)

Offline

#2 2011-08-25 10:30:07

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [solved]Ignore menu.lst.pacnew?

well that menu.lst is just an example and you don't have to replace your current menu.lst with that.

what you have to do is to edit your menu.lst and change the names like in that news


Give what you have. To someone, it may be better than you dare to think.

Offline

#3 2011-08-25 11:49:23

whoops
Member
Registered: 2009-03-19
Posts: 891

Re: [solved]Ignore menu.lst.pacnew?

Ok thanks. I guess that means:
- Those kernel / init lines STILL require the full path (usually with "/boot") and there is no update planned I need to prepare / change that for...
- Also the "fallback" initramfs is (except for the name change) still generated like it used to and I don't have to change anything else to keep it working...

I was just being a little paranoid about why it was changed like this (usually when I ignore something like that, stuff breaks roll) - last time I saw the default / example file, it looked a lot more like what I was using now (it included the /boot and a fallback option). wink

Offline

#4 2011-08-25 11:58:53

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [solved]Ignore menu.lst.pacnew?

You need to include '/boot' in the path if your don't have a separate /boot partition.

Last edited by karol (2011-08-25 13:23:59)

Offline

#5 2011-08-25 13:15:37

whoops
Member
Registered: 2009-03-19
Posts: 891

Re: [solved]Ignore menu.lst.pacnew?

Ooo, thx, thats almost offtopic but good to know, didn't think of that: so those differences make sense after all! Did the default installation change to using an extra boot partition? Or did I customize that after all and forgot I did? Could have sworn mine was "/boot/*" by default, but it's been a while...

Is there an explanation why the fallback start option isn't there any more, too? Haven't used it for a long time anyway... has it been decided that this is (mostly) redundant / should be done by manually changing the line with the grub editor on boot if needed for some reason?

Last edited by whoops (2011-08-25 13:16:28)

Offline

#6 2011-08-25 13:20:21

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

Re: [solved]Ignore menu.lst.pacnew?

again, menu.lst from grub is JUST a simple example to have a starting point.

AIF is generating a brand new menu.lst for every systems and doesn't matter what is in menu.lst from grub.


Give what you have. To someone, it may be better than you dare to think.

Offline

#7 2011-08-25 13:35:15

whoops
Member
Registered: 2009-03-19
Posts: 891

Re: [solved]Ignore menu.lst.pacnew?

again, menu.lst from grub is JUST a simple example to have a starting point.

Yes, I never doubted that one. Just usually the "simple example" isn't changed without a reason.

wonder wrote:

AIF is generating a brand new menu.lst for every systems and doesn't matter what is in menu.lst from grub.

That I didn't know and I guess it's the explanation - I thought the .pacnew file I get with updates & the one I started out with came from the same source (= some archlinux script). Now I see, I've been comparing the "AIF-generated" default file I remembered with the one probably distributed with vanilla grub... which of course doesn't make any sense.

( Yes, I guess that means I finally really get it now - even the "offtopic part" - thx again, now I'm all out of questions big_smile )

Last edited by whoops (2011-08-25 13:37:09)

Offline

Board footer

Powered by FluxBB