Despite the useful incorporation of poetical sources and the sound philological analysis, the contribution lacks an introduction to Paterculus, and does not provide any contextualisation of Velleius’ pro-Augustan use of the past. For presenting the reader with a pro-Augustan narrative, Paterculus severed connections between the different historical events. Roberto Cristofoli analyses of the use of previous historiographical traditions in Velleius Paterculus’ description of the battle of Actium. Despite the good overview of recent work on different usages of the past in Roman historiography, the work of Varro and Roman antiquarianism are conspicuously absent. These four usages form an implicit framework to the volume. Four usages of the past are discussed: 1) the past as a model, 2) the past as personal experience, 3) a past reinterpreted through engagement with previous texts, and 4) a reinterpretation of the past by changes in style or mode of writing.
#Pax liberas Patch
Public patch of grsecurity/PaX based on my understanding of the code.The introduction sets out the aims of the volume: building on the “rhetorical turn”, to treat Roman historiography as an intertextual set of texts constructing the past.
#Pax liberas code
$CODE is from Brad Spengler/PaX Team's code in the last For grsecurity copyright, when more specific details are not easy to find, the following could be used:Ĭopyright (C) 2001-2017 PaX Team, Bradley Spengler, Open Source Security Inc.Īdditionally, grsecurity has asked that contributors include this in commit messages for non-trivial code ported from grsecurity: For example, grsecurity's copyright notice from their most recent public patch does not include PaX Team's copyright notice, which is only listed in the patch for GCC plugins. This may require some examination of commit history. In the case of new files, or other places where a copyright notice would be expected to be added, be sure to retain all copyright notices from the other project.
#Pax liberas software
Grsecurity and other non-upstream patch sourcesĪs with any other Free Software project, it is particularly important that if you're working on upstreaming work from other projects, be sure your patches are giving credit to the original authors, that licenses are compatible, and that copyright notices are retained, etc. Even if you're only sending your patches to the mailing lists for some early review, it's best to get as much of the coding style and submission semantics correct to avoid reviewers needing to recommend changes in those areas. When contributing patches for the Linux kernel, be sure to follow the Linux kernel Coding Style Guide and read about Submitting Patches. Please send new topics and patch series to both and for the widest audience possible. We need kernel developers, compiler developers, testers, backporters, a documentation writers. If not, the Linux Foundation's Core Infrastructure Initiative is in a great position to fund specific work proposals. If your employer is brave enough to understand how critical this work is, they'll pay you to work on it. Pick something from the issue tracker (or add a new one), coordinate on the mailing lists, and get started.
#Pax liberas update
Come to the every-2-weeks status update meeting.Subscribe to the upstream Linux kernel hardening mailing list, where development, maintenance, and administrivia happen.4.1 grsecurity and other non-upstream patch sources.
0 kommentar(er)
