#2059 closed enhancement (fixed)
Linux-2.6.22.2
| Reported by: | Matthew Burgess | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Book | Version: | SVN |
| Severity: | normal | Keywords: | |
| Cc: |
Description
New version. Announcement at http://www.ussg.iu.edu/hypermail/linux/kernel/0708.1/1085.html. I know we're deep into the 6.3 release cycle now, but I'd prefer to see us get this in if possible as the announcement mentions "lots of bugfixes and some security updates so all users of the 2.6.22 series should update to it".
Change History (6)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Users should be using 2.6.22.2 anyway, but jhalfs won't do it unless you update the version in the book.
comment:3 by , 17 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
I've analyzed the changes to the headers - one change in netfilter, which cannot affect the LFS book (we don't build iptables), and one new header, linux/serial_reg.h which is not referenced by other exported kernel headers and unsurprisingly is not referenced by glibc-2.5.1. Building 2.6.22.2 now to make sure it compiles.
comment:5 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Updatd book to Linux 2.6.22.2 at revision 8306.
Well, the book says "use the latest 2.6.22 version", so users should be using 2.6.22.2 anyway. However, it shouldn't hurt to make that the official kernel version used by the book at release time, either.
I read through the kernel changelog earlier today. I skipped lots of stuff that didn't affect me because I didn't use the drivers that got fixed, but there were several deadlock fixes, a bunch of driver fixes, an ABI change (bugfix) to make timerfd work right (!), a fix or two to netfilter, etc. I don't *think* there was anything that would make LFS start failing.