From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lakostis@altlinux.org>
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
 sa.local.altlinux.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FSL_HELO_HOME
 autolearn=no autolearn_force=no version=3.4.1
Date: Sat, 9 Sep 2017 00:06:53 +0200
From: Konstantin Lepikhov <lakostis@altlinux.org>
To: devel@lists.altlinux.org
Message-ID: <20170908220652.GA4857@lks.home>
Mail-Followup-To: devel@lists.altlinux.org
References: <20170904115640.GA30835@lks.home>
 <20170904160138.GC15438@altlinux.org>
 <20170904191842.GA24238@lks.home>
 <20170904213509.GA18856@altlinux.org>
 <20170906120909.GA8403@lks.home>
 <20170906133734.GE13205@altlinux.org>
 <20170907074727.GA5493@lks.home>
 <20170907092831.GA27490@altlinux.org>
 <20170907101743.GA19849@lks.home>
 <20170908210136.GA19351@altlinux.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20170908210136.GA19351@altlinux.org>
X-Operation-System: ALT Linux starter kit (Trientalis) 4.12.0-lks-wks-alt0.3
User-Agent: Mutt/1.8.3 (2017-05-23)
Subject: Re: [devel] Q: postinst hook for firmware-*
X-BeenThere: devel@lists.altlinux.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ALT Linux Team development discussions <devel@lists.altlinux.org>
List-Id: ALT Linux Team development discussions <devel.lists.altlinux.org>
List-Unsubscribe: <https://lists.altlinux.org/mailman/options/devel>,
 <mailto:devel-request@lists.altlinux.org?subject=unsubscribe>
List-Archive: <http://lists.altlinux.org/pipermail/devel>
List-Post: <mailto:devel@lists.altlinux.org>
List-Help: <mailto:devel-request@lists.altlinux.org?subject=help>
List-Subscribe: <https://lists.altlinux.org/mailman/listinfo/devel>,
 <mailto:devel-request@lists.altlinux.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Sep 2017 22:05:08 -0000
Archived-At: <http://lore.altlinux.org/devel/20170908220652.GA4857@lks.home/>
List-Archive: <http://lore.altlinux.org/devel/>
List-Post: <mailto:devel@altlinux.org>

Hi Dmitry!

On 09/09/2017, at 12:01:37 AM you wrote:

> Что-то я сразу не спросил: для какого ядра хочется обновить initrd
> при обновлении ucode? текущее, как написано в патче?
> то, на которое /boot/vmlinuz указывает?
конечно текущее - для новых ядер ucode подхватится сам. Текущий
kernel.trigger не учитывает как раз случай, когда новый ucode приехал, а
ядра остались старые. 

-- 
WBR et al.