Bug#586363: closed by maximilian attems (Re: Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated)
On Tue, Jun 22, 2010 at 11:30:58AM +0200, Michal Suchanek wrote: > > I am not concerned that initramfs would not boot (which is what the > backup initramfs is for) but that the new kernel might not boot (or > might boot but bring the system up in unusable state) which is > unfortunately not uncommon. Then I would appreciate having an > up-to-date initramfs for the running kernel rather than later, > possibly broken kernel. linux-2.6 early testers is not the major concern of the sorting alg, again thanks for raising the point. anyway if you want policy changes of initramfs next time please discuss that first on d-kernel or initra...@vger so that a consensus could emerge. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#586363: closed by maximilian attems (Re: Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated)
On 22 June 2010 11:15, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the initramfs-tools package: > > #586363: initramfs-tools: initramfs for the wrong kernel is updated > > It has been closed by maximilian attems . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact maximilian attems > by > replying to this email. > > > -- > 586363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586363 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > -- Forwarded message -- > From: maximilian attems > To: 586363-d...@bugs.debian.org > Date: Tue, 22 Jun 2010 11:02:57 +0200 > Subject: Re: Bug#586363: initramfs-tools: initramfs for the wrong kernel is > updated > On Tue, Jun 22, 2010 at 08:05:28AM +0200, Michal Suchanek wrote: >> >> And when the new on does not boot you get the old initrd. >> >> Also there was some mechanism in place for grub menu default to point >> to the same kernel even after new kernels are installed until you >> change that in case you resumed from disk or wanted to boot known >> working kernel. >> >> Thanks > > an initramfs not booting is a bug that needs to be hunted. it does > happen, but it is not the major concern on updating the latest or newest > linux-26 initramfs. closing as no convincing args to change policy that > close to release. > I am not concerned that initramfs would not boot (which is what the backup initramfs is for) but that the new kernel might not boot (or might boot but bring the system up in unusable state) which is unfortunately not uncommon. Then I would appreciate having an up-to-date initramfs for the running kernel rather than later, possibly broken kernel. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On 22 June 2010 00:13, maximilian attems wrote: > On Sat, 19 Jun 2010, Michal Suchanek wrote: > >> On 19 June 2010 15:23, maximilian attems wrote: >> > On Sat, Jun 19, 2010 at 03:17:20PM +0200, Michal Suchanek wrote: >> >> Why is sorting code required? >> > >> > dpkg --compare-versions does sort rc images before non rc ones. >> > as mentioned in the manpages initramfs-tools updates the "newest" one. >> > >> > here the assumption is that rc is newer then not rc, which is wrong. >> > but rc admin should be smart enough to kick rc once the real is out. >> > >> >> So the issue is that it updates the newest kernel, not the running >> kernel if that is different. > > please explain why it should update the running one? > > this makes zero sense for the most usual case of newer > linux-2.6 installed but not yet rebooted. > And when the new on does not boot you get the old initrd. Also there was some mechanism in place for grub menu default to point to the same kernel even after new kernels are installed until you change that in case you resumed from disk or wanted to boot known working kernel. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On Sat, 19 Jun 2010, Michal Suchanek wrote: > On 19 June 2010 15:23, maximilian attems wrote: > > On Sat, Jun 19, 2010 at 03:17:20PM +0200, Michal Suchanek wrote: > >> Why is sorting code required? > > > > dpkg --compare-versions does sort rc images before non rc ones. > > as mentioned in the manpages initramfs-tools updates the "newest" one. > > > > here the assumption is that rc is newer then not rc, which is wrong. > > but rc admin should be smart enough to kick rc once the real is out. > > > > So the issue is that it updates the newest kernel, not the running > kernel if that is different. please explain why it should update the running one? this makes zero sense for the most usual case of newer linux-2.6 installed but not yet rebooted. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On Sat, Jun 19, 2010 at 03:17:20PM +0200, Michal Suchanek wrote: > Why is sorting code required? dpkg --compare-versions does sort rc images before non rc ones. as mentioned in the manpages initramfs-tools updates the "newest" one. here the assumption is that rc is newer then not rc, which is wrong. but rc admin should be smart enough to kick rc once the real is out. > I would just expect that the running kernel is updated, no sorting is > required for that. so i do not see a special point for adding more complex sorting code. thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On 19 June 2010 03:11, maximilian attems wrote: > On Fri, Jun 18, 2010 at 09:55:12PM +0200, Michal Suchanek wrote: >> Package: initramfs-tools >> Version: 0.94.4~bpo50+1 >> Severity: normal >> >> >> Note that the initramfs is updated for a non-running kernel on package >> removal. >> >> The following packages will be REMOVED: >> plymouth plymouth-themes-solar{a} >> 0 packages upgraded, 0 newly installed, 2 to remove and 4 not upgraded. >> Need to get 0B of archives. After unpacking 1307kB will be freed. >> Do you want to continue? [Y/n/?] >> Writing extended state information... Done >> (Reading database ... 266342 files and directories currently installed.) >> Removing plymouth-themes-solar ... >> Removing plymouth ... >> Processing triggers for initramfs-tools ... >> update-initramfs: Generating /boot/initrd.img-2.6.34-rc4-amd64 >> Processing triggers for man-db ... >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Reading extended state information... Done >> Initializing package states... Done >> Writing extended state information... Done >> > > rc linux images are special, people having them are expected > to handle their initramfs. > > i don't see the point of introducing special sorting code that > would discriminate those rcs. > > Why is sorting code required? I would just expect that the running kernel is updated, no sorting is required for that. Thanks Michal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
On Fri, Jun 18, 2010 at 09:55:12PM +0200, Michal Suchanek wrote: > Package: initramfs-tools > Version: 0.94.4~bpo50+1 > Severity: normal > > > Note that the initramfs is updated for a non-running kernel on package > removal. > > The following packages will be REMOVED: > plymouth plymouth-themes-solar{a} > 0 packages upgraded, 0 newly installed, 2 to remove and 4 not upgraded. > Need to get 0B of archives. After unpacking 1307kB will be freed. > Do you want to continue? [Y/n/?] > Writing extended state information... Done > (Reading database ... 266342 files and directories currently installed.) > Removing plymouth-themes-solar ... > Removing plymouth ... > Processing triggers for initramfs-tools ... > update-initramfs: Generating /boot/initrd.img-2.6.34-rc4-amd64 > Processing triggers for man-db ... > Reading package lists... Done > Building dependency tree > Reading state information... Done > Reading extended state information... Done > Initializing package states... Done > Writing extended state information... Done > rc linux images are special, people having them are expected to handle their initramfs. i don't see the point of introducing special sorting code that would discriminate those rcs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#586363: initramfs-tools: initramfs for the wrong kernel is updated
Package: initramfs-tools Version: 0.94.4~bpo50+1 Severity: normal Note that the initramfs is updated for a non-running kernel on package removal. The following packages will be REMOVED: plymouth plymouth-themes-solar{a} 0 packages upgraded, 0 newly installed, 2 to remove and 4 not upgraded. Need to get 0B of archives. After unpacking 1307kB will be freed. Do you want to continue? [Y/n/?] Writing extended state information... Done (Reading database ... 266342 files and directories currently installed.) Removing plymouth-themes-solar ... Removing plymouth ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.34-rc4-amd64 Processing triggers for man-db ... Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information... Done Initializing package states... Done Writing extended state information... Done -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-2.6.34-1-amd64 root=UUID=ae7d5095-c8b3-4205-af0e-032b0e124ec3 ro quiet -- /proc/filesystems ext3 fuseblk reiserfs -- lsmod Module Size Used by tun12166 10 binfmt_misc 6558 1 openafs 602666 2 vboxnetadp 4241 0 oss_usb 118853 0 oss_hdaudio 146129 0 osscore 550925 2 oss_usb,oss_hdaudio ib_iser23647 0 rdma_cm21170 1 ib_iser ib_cm 26008 1 rdma_cm iw_cm 6465 1 rdma_cm ib_sa 16082 2 rdma_cm,ib_cm ib_mad 29813 2 ib_cm,ib_sa ib_core41391 6 ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad ib_addr 4038 1 rdma_cm iscsi_tcp 8153 0 libiscsi_tcp 11127 1 iscsi_tcp libiscsi 31537 3 ib_iser,iscsi_tcp,libiscsi_tcp scsi_transport_iscsi25151 4 ib_iser,iscsi_tcp,libiscsi bridge 53994 0 stp 1464 1 bridge reiserfs 195202 1 fuse 50697 1 coretemp4235 0 hwmon_vid 1804 0 radeonfb 50840 0 fb_ddc 1429 1 radeonfb vboxnetflt 12118 0 vboxdrv 1721774 2 vboxnetadp,vboxnetflt loop 12330 0 firewire_sbp2 11407 0 asus_atk01109268 0 processor 29010 0 led_class 2203 0 wacom 19865 0 tpm_tis 7349 0 joydev 8920 0 evdev 7426 9 i2c_i8017822 0 tpm 9843 1 tpm_tis tpm_bios4629 1 tpm parport_pc 18869 0 rng_core3166 0 psmouse45509 0 parport25598 1 parport_pc serio_raw 3726 0 ext3 106594 4 jbd37179 1 ext3 mbcache 5152 1 ext3 usbhid 33354 0 hid63831 1 usbhid radeon603657 2 ttm39481 1 radeon drm_kms_helper 20107 1 radeon drm 144377 4 radeon,ttm,drm_kms_helper i2c_algo_bit4297 2 radeonfb,radeon i2c_core 16076 7 radeonfb,fb_ddc,i2c_i801,radeon,drm_kms_helper,drm,i2c_algo_bit sg 19141 3 sr_mod 12711 0 cdrom 29769 1 sr_mod sd_mod 30469 7 crc_t10dif 1284 1 sd_mod ata_generic 2895 0 ata_piix 20652 8 ehci_hcd 30813 0 firewire_ohci 18688 0 thermal12046 0 uhci_hcd 18410 0 libata133830 2 ata_generic,ata_piix button 4706 0 thermal_sys12036 2 processor,thermal firewire_core 38607 2 firewire_sbp2,firewire_ohci crc_itu_t 1315 1 firewire_core usbcore 125665 6 oss_usb,wacom,usbhid,ehci_hcd,uhci_hcd scsi_mod 125191 9 ib_iser,iscsi_tcp,libiscsi,scsi_transport_iscsi,firewire_sbp2,sg,sr_mod,sd_mod,libata atl1 25914 0 mii 3250 1 atl1 nls_base6369 1 usbcore -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip BOOT=local DEVICE=eth0 NFSROOT=auto -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (300, 'unstable'), (295, 'experimental'), (290, 'stable-i386'), (280, 'testing-i386'), (270, 'unstable-i386'), (150, 'exper