Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#5651 - kernel upgrades use their own mkinitcpio.confs
Attached to Project:
Arch Linux
Opened by hypermegachi (hypermegachi) - Monday, 23 October 2006, 14:00 GMT
Last edited by Thomas Bächler (brain0) - Monday, 06 November 2006, 09:09 GMT
Opened by hypermegachi (hypermegachi) - Monday, 23 October 2006, 14:00 GMT
Last edited by Thomas Bächler (brain0) - Monday, 06 November 2006, 09:09 GMT
|
Detailsthe /boot directory already has a the mkinitcpio.conf for the respective kernel, and i think that they should be used when the kernel is upgraded.
for example, the mkinitcpio.conf is most likely different between a kernel26ck and kernel26suspend2 kernel, since ck has no use for the resume hook. i got caught with this problem, because my /etc/mkinitcpio.conf is an image for kernel26, so when suspend2 was upgraded, it used that config file to regenerate the initrd image, and i was unable to resume, until i realized what happened. so...in summary, i think it'd be a good idea to use the files in /boot/ and not use the one in /etc anymore. |
This task depends upon
Closed by Thomas Bächler (brain0)
Sunday, 03 December 2006, 12:35 GMT
Reason for closing: Fixed
Additional comments about closing: All arch kernels have been updated to use preset files. Users can now create any number of images with different configuration files.
Sunday, 03 December 2006, 12:35 GMT
Reason for closing: Fixed
Additional comments about closing: All arch kernels have been updated to use preset files. Users can now create any number of images with different configuration files.
Comment by Thomas Bächler (brain0) -
Tuesday, 24 October 2006, 06:31 GMT
The files in /boot are for the fallback images only. Right now there is only one configuration file for all "default" images. Maybe we can change that, I'll look into our possibilities here.
Comment by Thomas Bächler (brain0) -
Saturday, 04 November 2006, 11:47 GMT
Okay, this has been already implemented for kernel26, kernel26ck, kernel26suspend2 and kernel26mm: You can specify different configuration files and image names in /etc/mkinitcpio.d/*.preset. It is only missing for kernel26beyond.