thin clients not updating to the latest kernel - some extra thoughts

[Spyros Tsiolis]

--------------------------------------------
On Thu, 17/3/16, Spyros Tsiolis <stsiol at yahoo.co.uk> wrote:

 Subject: Re: thin clients not updating to the latest kernel
 To: "Users Ubuntu" <ubuntu-users at lists.ubuntu.com>
 Date: Thursday, 17 March, 2016, 14:54
 
 
 --------------------------------------------
 On Thu, 17/3/16, Tony Baechler <bats at batsupport.com>
 wrote:
 
  Subject: Re: thin clients not updating to the latest
 kernel
  To: "Spyros Tsiolis" <stsiol at yahoo.co.uk>,
 "Ubuntu user technical support, not for general discussions"
 <ubuntu-users at lists.ubuntu.com>
  Date: Thursday, 17 March, 2016, 15:26
  
  On 3/16/2016 10:16 AM,
  Spyros Tsiolis wrote:
  > When the kernel gets
  updated through the ubuntu update
  >
  system, where does it go exactly and what does it update
  ?
  
  You can find this
  out easily enough. On an existing system with a kernel 
  installed, try this command, but be warned
  there is a lot of output:
  
  dpkg -L linux-image-3.XXX|less
  
  Replace XXX with the package
  name of the actual kernel. You can determine 
  this with this command:
  
  dpkg -l | grep linux-image
  
  Another way is to download the kernel package
  by hand from any Ubuntu 
  mirror. You should
  find it under /ubuntu/pool/main/l/linux-image/. Use
  "dpkg 
  --extract" to extract it to
  a temporary directory. That lets you look at the 
  installation scripts, so you can see exactly
  what gets updated.
  --------------------------------------------
 
 
 
 OK, 

so I was thinking about his (duh ! :-) and have a 
new question ;

Say you boot from the latest kernel release.
You logon to the thin client and you find out that
in the new updates that the system wants to perform,
there is even a newer kernel.
We'll call the current kernel kernel-v3.2.1 and
the new kernel kernel-v3.2.2

Here's the question ;
If you've upgraded to the v3.2.2 but you want to build
initrd.img but you are running the kernel-v.3.2.1
How can you do that ?
I am not asking about System.map and vmlinuz because
they have already been created for kernel-v3.2.2
However, as far as I know, "initrd.img" is not there
for v3.2.2.

Can I create the "initrd.img" file _for_ v3.2.2 while
running in the v3.2.1 evnironment ?

Any ideas ?

Thank you ,

s.