update manager refuses to upgrade kernel to newer version

[Oliver Grawert]

hi,
Am Sonntag, den 14.02.2016, 20:05 +0000 schrieb Spyros Tsiolis:

> I think they are the *-46 kernel files , yes. I agree with you
> totally.
> What I can't stop my mind from thinking though, is why on one
> installation
> the kernels get updated and run the newest kernel version and on the
> other
> installation this no longer applies. . . . .
>  
if you say "one installation" vs "other istallation" i assume you refer
to the server vs the NFS root ? 

the way you install an ubuntu (or debian) system is pretty essential
for the initial configuration, so while you likely used ubiquity or the
text based installer for the server, how did you install the nfs root,
this might explain different behavior (i.e. if you use debootstrap to
create an initial chroot that gets you a completely unconfigured system
which will differ from what you get using one of the installers that
apply a debconf preseed by default ...)

and on a sidenote, as i mentioned before, you should make sure that
/proc, /sys and /dev are mounted when you are inside the chroot (and
also make sure to unmount these before (or even after) leaving it). the
pre/postinst scripts of packages often use info from these dirs to do
the pre/post configuration

for the PXE issue, i'd start with copying the new vmlinuz and
initrd.img files into the PXE dir, that should get you going with the
updated kernel ... once you have this fixed we can move on and look at
the remaining probs.

...one thing at a time ;)

ciao
	oli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 173 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20160214/4dd547a5/attachment.sig>