Create new chapter regarding security and package updates

[steve.crosby@…]

It would be benificial to have a chapter\paragraph at the end of the book giving a brief outline of security issues that might occur in software packages, and perhaps providing the reader with some resources they can use to keep track of these.

Possibly mention resources such as freshmeat as well for tracking package version changes, although we would need a big note saying that updating a package in LFS carries it's own risks re: lack of testing, and therefore may not be supported...

[Matthew Burgess]

Fixed by way of prologue/errata.xml.

[steve.crosby@…]

hmmm...

I was thinking more along the following as a new bullet point in 9.4 What Now

• Maintenance

Now that your LFS system is built, you should maintain it as new software, security notices and bug fixes are made available. There are several online resources you can use to keep track of this, some of which are shown below:

freshmeat.net - Can notify you of upgrades to packages in your system via

email

CERT - A mailing list to publicise security problems with various operating

systems and applications

bugtrack - An online forum and mailing list that notifies of newly

discovered security issues, and occasionally possible fixes

etc.

No problem if this isn't desired in the book.

[Matthew Burgess]

Nope, looks like I was far too hasty in closing this one off. Your suggested text looks good to me.