Automating patch generation and application for configuration files
1. Automating patch generation and application for configuration files
Anyone following mailing lists will have seem messages where a developer asks an user to apply a source code patch for solving a problem or enabling support for a new piece of hardware. This is only one of the multiple uses of patches, they also can be used to customize configuration files.
What does the man pages for patch(1) tell us?
NAME patch - apply a diff file to an original DESCRIPTION patch will take a patch file containing any of the four forms of differ- ence listing produced by the diff(1) program and apply those differences to an original file, producing a patched version. If patchfile is omit- ted, or is a hyphen, the patch will be read from the standard input.
NAME diff - differential file and directory comparator DESCRIPTION The diff utility compares the contents of file1 and file2 and writes to the standard output the list of changes necessary to convert one file in- to the other. No output is produced if the files are identical.
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
|custom configuration, diff(1), install.site, makefile, need an operator, patch(1), sitexx.tgz|
|Thread||Thread Starter||Forum||Replies||Last Post|
|Automating FreeBSD release downloads with a .netrc file||J65nko||Guides||4||11th February 2010 09:02 PM|
|managing configuration files||JMJ_coder||General software and network||1||21st January 2010 06:57 AM|
|Automating OpenBSD snapshot downloads with a .netrc file||J65nko||Guides||1||7th January 2010 03:09 AM|
|patch application for usb mouse?||aesop||FreeBSD Installation and Upgrading||1||17th January 2009 11:15 PM|
|Automating ports update with portmaster||jaymax||FreeBSD Ports and Packages||3||12th June 2008 07:56 AM|