grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: About grub.cfg{.new,} generation


From: appzer0
Subject: Re: About grub.cfg{.new,} generation
Date: Wed, 12 Jan 2011 17:07:11 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101226 Icedove/3.0.11

Le 12/01/2011 16:20, Vladimir 'φ-coder/phcoder' Serbinenko a écrit :
You can change the "s,x,x" part adding --transform command line option
to configure. It's useful to change all the pathes used.
The problem is that slackware and other distributions use a "*.new"
renaming pattern when upgrading packages, in order to not overwrite
important config files. Then the user has to deal with these .new
files, rename, overwrite or toss away.

If 'grub-mkconfig' is really doing what I think it does, then it would
just overwrite this important file, '/boot/grub/grub.cfg.new'.

grub.cfg shouldn't be packaged at all. It's autogenerated on the target
system.

Thank you very much for the info. I'll stick with the '40_custom' file then.


appzer0



reply via email to

[Prev in Thread] Current Thread [Next in Thread]