Anything to note about the new kernelll?
Trivial question, why is it 4.9.30-203 and not 4.9.30-204, replacing 4.9.13-203?
Also how do people claim to have the linux box up for 6 mo or more when kernel updates come out more frequently than that? Not that I mind having to install a new kernel...
thanks
Bob
On 15/06/17 14:58, Robert Moskowitz wrote:
Anything to note about the new kernelll?
Nothing special (and not Critical CVE either that I could see in that LTS branch), but as Johnny built a newer one for AltArch/i686 I decided to also rebase to latest from kernel LTS branch
Trivial question, why is it 4.9.30-203 and not 4.9.30-204, replacing 4.9.13-203?
The important bit is 4.9.30 vs 4.9.13 (the rest is for rpm versioning)
Also how do people claim to have the linux box up for 6 mo or more when kernel updates come out more frequently than that? Not that I mind having to install a new kernel...
It's up to each admin to decide if they want to reboot on newer kernel or not :-)
On 06/15/2017 10:06 AM, Fabian Arrotin wrote:
On 15/06/17 14:58, Robert Moskowitz wrote:
Anything to note about the new kernelll?
Nothing special (and not Critical CVE either that I could see in that LTS branch), but as Johnny built a newer one for AltArch/i686 I decided to also rebase to latest from kernel LTS branch
Trivial question, why is it 4.9.30-203 and not 4.9.30-204, replacing 4.9.13-203?
The important bit is 4.9.30 vs 4.9.13 (the rest is for rpm versioning)
Also how do people claim to have the linux box up for 6 mo or more when kernel updates come out more frequently than that? Not that I mind having to install a new kernel...
It's up to each admin to decide if they want to reboot on newer kernel or not :-)
Why does /boot/extlinux/extlinux.conf not get updated when a new kernel is installed?
I probably should learn on how to create a menu, as all I do is a simple sed command to replace the old kernel with the new since there is no menuing control? in a kernel update.
On 16/06/17 22:02, Robert Moskowitz wrote:
On 06/15/2017 10:06 AM, Fabian Arrotin wrote:
On 15/06/17 14:58, Robert Moskowitz wrote:
Anything to note about the new kernelll?
Nothing special (and not Critical CVE either that I could see in that LTS branch), but as Johnny built a newer one for AltArch/i686 I decided to also rebase to latest from kernel LTS branch
Trivial question, why is it 4.9.30-203 and not 4.9.30-204, replacing 4.9.13-203?
The important bit is 4.9.30 vs 4.9.13 (the rest is for rpm versioning)
Also how do people claim to have the linux box up for 6 mo or more when kernel updates come out more frequently than that? Not that I mind having to install a new kernel...
It's up to each admin to decide if they want to reboot on newer kernel or not :-)
Why does /boot/extlinux/extlinux.conf not get updated when a new kernel is installed?
I probably should learn on how to create a menu, as all I do is a simple sed command to replace the old kernel with the new since there is no menuing control? in a kernel update.
Reason why the update-boot tool exists and is mentioned for quite some time on the dedicated wiki page (https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32?highlight=%28arm3...)
On 06/16/2017 05:11 PM, Fabian Arrotin wrote:
On 16/06/17 22:02, Robert Moskowitz wrote:
On 06/15/2017 10:06 AM, Fabian Arrotin wrote:
On 15/06/17 14:58, Robert Moskowitz wrote:
Anything to note about the new kernelll?
Nothing special (and not Critical CVE either that I could see in that LTS branch), but as Johnny built a newer one for AltArch/i686 I decided to also rebase to latest from kernel LTS branch
Trivial question, why is it 4.9.30-203 and not 4.9.30-204, replacing 4.9.13-203?
The important bit is 4.9.30 vs 4.9.13 (the rest is for rpm versioning)
Also how do people claim to have the linux box up for 6 mo or more when kernel updates come out more frequently than that? Not that I mind having to install a new kernel...
It's up to each admin to decide if they want to reboot on newer kernel or not :-)
Why does /boot/extlinux/extlinux.conf not get updated when a new kernel is installed?
I probably should learn on how to create a menu, as all I do is a simple sed command to replace the old kernel with the new since there is no menuing control? in a kernel update.
Reason why the update-boot tool exists and is mentioned for quite some time on the dedicated wiki page (https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32?highlight=%28arm3...)
Thanks. Now how did I miss that... Probably did not go back and reread once 1611 came out.
Now I will have to test this and see about updating my howto accordingly.
On 06/16/2017 05:11 PM, Fabian Arrotin wrote:
On 16/06/17 22:02, Robert Moskowitz wrote:
On 06/15/2017 10:06 AM, Fabian Arrotin wrote:
On 15/06/17 14:58, Robert Moskowitz wrote:
Anything to note about the new kernelll?
Nothing special (and not Critical CVE either that I could see in that LTS branch), but as Johnny built a newer one for AltArch/i686 I decided to also rebase to latest from kernel LTS branch
Trivial question, why is it 4.9.30-203 and not 4.9.30-204, replacing 4.9.13-203?
The important bit is 4.9.30 vs 4.9.13 (the rest is for rpm versioning)
Also how do people claim to have the linux box up for 6 mo or more when kernel updates come out more frequently than that? Not that I mind having to install a new kernel...
It's up to each admin to decide if they want to reboot on newer kernel or not :-)
Why does /boot/extlinux/extlinux.conf not get updated when a new kernel is installed?
I probably should learn on how to create a menu, as all I do is a simple sed command to replace the old kernel with the new since there is no menuing control? in a kernel update.
Reason why the update-boot tool exists and is mentioned for quite some time on the dedicated wiki page (https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32?highlight=%28arm3...)
OK. I read the script, and tested it. Better than my simple sed, though I did it in one sed command...
I have updated my howto to use update-boot
thanks
-
Fabian Arrotin -
Robert Moskowitz