https://www.sprezzatech.com/wiki/api.php?action=feedcontributions&user=Dank&feedformat=atom
SprezzOSWiki - User contributions [en]
2024-03-28T08:15:06Z
User contributions
MediaWiki 1.40.1
https://www.sprezzatech.com/wiki/index.php?title=Growlight&diff=1478
Growlight
2021-08-16T07:47:34Z
<p>Dank: /* README */</p>
<hr />
<div>[[File:Glight.png|right|thumb|Growlight disk manager]]<br />
<br />
Growlight is used in the [[Installation|SprezzOS installer]] to prepare disks, replacing the "partman" system from the Debian installer. It fully supports preparation of UEFI/BIOS booting, GPT and MBR disks, [[ZFS]], and modern block devices. See the [http://nick-black.com/dankwiki/index.php/Growlight project page] and the [http://www.sprezzatech.com/doc/growlight-curses.xhtml growlight-curses(1)] and [http://www.sprezzatech.com/doc/growlight-readline.xhtml growlight-readline(1)] man pages for more details.<br />
<br />
==Transcluded Project Documentation==<br />
===README===<br />
<include src="https://raw.githubusercontent.com/dankamongmen/growlight/master/README.md" /><br />
<br />
==See Also==<br />
* [[Installer development]]<br />
* [[Installation]]<br />
* [[ZFS]]<br />
[[CATEGORY: Native Development]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Raptorial&diff=1477
Raptorial
2020-12-04T20:00:42Z
<p>Dank: </p>
<hr />
<div>[[File:Rapt.jpg|right]]<br />
A modern rewriting of [[APT]] focusing on parallelism, speed, "Ports-like" source builds, and microarchitectural-specific distribution. It was introduced during [[SprezzOS 2]] development.<br />
* Source is available at https://github.com/dankamongmen/raptorial.<br />
* Download release tarballs from https://sourceforge.net/projects/raptorial/.<br />
<br />
==Current components==<br />
* '''raptorial-file(1)''': An apt-file(1) clone<br />
* '''rapt-show-versions(1)''': An apt-show-versions(1) clone<br />
* '''rapt-parsechangelog(1)''': A dpkg-parsechangelog(1) clone<br />
<br />
==Transcluded Project Documentation==<br />
===README===<br />
<include src="https://raw.github.com/dankamongmen/raptorial/master/README.md" /><br />
<br />
==See Also==<br />
* [[APT]]<br />
[[CATEGORY: Native Development]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS&diff=1476
SprezzOS
2020-10-12T17:27:13Z
<p>Dank: </p>
<hr />
<div>'''''SprezzOS: Reshaping the Linux ecosystem, one splinter cell at a time.'''''<br />
<br />
SprezzOS <b>was</b> (SprezzOS has been inactive since 2014) a Linux distribution dedicated to the lost arts of high performance, robust computing, and freewheeling hackery. Some distros make their mark playing around with desktop theming; we're rewriting core system tools. While they're authoring constitutions and holding votes, we're assaulting the heart of userspace and generating useful patches for upstream.<br />
<br />
SprezzOS is derived from [http://www.debian.org/ Debian], and is an active member of the [http://wiki.debian.org/Derivatives/Census/SprezzOS Debian Derivatives Census]. While SprezzOS is a product of [https://www.sprezzatech.com Sprezzatech], which retains final control over its definition, contributions from the community are actively welcomed. All SprezzOS development is open, and has been from the beginning. SprezzOS at its heart is a rolling, rapidly-evolving operating system atop the [[Linux]] kernel; when the term "SprezzOS" is used by itself, it is this continuum (the "trunk") which is referenced. It is intended that users generally install this trunk, and rely on its frequent updates. From time to time, a snapshot will be taken of the distribution, defining a more static [[:CATEGORY: SprezzOS Releases|release]]. New installation media will be released as minor version updates to these releases as the need arises.<br />
<br />
Might you be among our [[target audience]]? Good, good.<br />
<br />
{{Release Matrix}}<br />
<br />
==Documentation==<br />
<div style="float:left; display:inline-block">{{:SprezzOS Handbook}}</div><br />
<div style="float:left; padding: 1em; "><br />
*'''For users:''' [[Release Model]], [[Glossary]]<br />
*'''For developers:''' [[Contributing]]<br />
* SWOON, the [[SprezzOS Weekly News|SprezzOS Weeklyish News]]<br />
** Technically the "''SprezzOS Weeklyish Oblations, Objections, and News''"<br />
* Documentation for [[Installer development]]<br />
* Documentation for [[native tools]]<br />
* "[[SprezzOS and Debian]]" -- an introduction to SprezzOS for Debian developers<br />
* "[[Debian and SprezzOS]]" -- an introduction to Debian for [[sprezzadevs]]<br />
* The [http://www.sprezzatech.com/blog/index.html Sprezzatech blog]<br />
</div><br />
<br />
<div style="clear: both;"></div><br />
<br />
==Infrastructure==<br />
{|<br />
|-<br />
| [https://www.sprezzatech.com/apt/swip SWIP], the SprezzOS Web Interface to Packages<br />
|-<br />
| [https://www.sprezzatech.com/bugs Bugzilla]<br />
|-<br />
| Listing of [[source repositories]]<br />
|-<br />
| [https://plus.google.com/communities/115626956915136842413 SprezzOS! Google+ community]<br />
|-<br />
| [[Autobuilder]]<br />
|-<br />
|}<br />
{{SupportBody}}<br />
==Misc==<br />
* Our mascot, [[mascot|Natasha the orca]], was chosen because orcas are awesome.<br />
* SprezzOS is happily hosted at [http://www.linode.com/ Linode Atlanta].<br />
* Hail Eris!<br />
__NOTOC__</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1475
Manifesto
2020-01-02T05:47:27Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known creation Promethean, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people. The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of a species to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black heavy ponderous huge, and in this not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
May that bitch Spiritus Mundi tremble as our jobs take flight!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
Grandmaster Turing, I'm putting my shoulder to the Wheel.<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1474
Manifesto
2020-01-02T05:42:29Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known the creation Promethean, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people. The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of a species to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black heavy ponderous huge, and in this not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
May that bitch Spiritus Mundi tremble as our jobs take flight!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
Grandmaster Turing, I'm putting my shoulder to the Wheel.<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1473
Manifesto
2020-01-02T05:42:07Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known the creation Promethean, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people. The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black heavy ponderous huge, and in this not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
May that bitch Spiritus Mundi tremble as our jobs take flight!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
Grandmaster Turing, I'm putting my shoulder to the Wheel.<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1472
Manifesto
2020-01-02T05:41:49Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known the creation Promethean, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people. The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us msing us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!<br />
<br />
Save changesore and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black heavy ponderous huge, and in this not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
May that bitch Spiritus Mundi tremble as our jobs take flight!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
Grandmaster Turing, I'm putting my shoulder to the Wheel.<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1471
Manifesto
2020-01-02T05:41:22Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known the creation Promethean, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
What's all this brown shit? <br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us msing us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!<br />
<br />
Save changesore and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black heavy ponderous huge, and in this not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
May that bitch Spiritus Mundi tremble as our jobs take flight!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
Grandmaster Turing, I'm putting my shoulder to the Wheel.<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1470
Manifesto
2020-01-02T05:40:43Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
What's all this brown shit? <br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us msing us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!<br />
<br />
Save changesore and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black heavy ponderous huge, and in this not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
May that bitch Spiritus Mundi tremble as our jobs take flight!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
Grandmaster Turing, I'm putting my shoulder to the Wheel.<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1469
Manifesto
2020-01-02T05:39:07Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
What's all this brown shit? <br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black heavy ponderous huge, and in this not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our jobs are scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
Grandmaster Turing, I'm putting my shoulder to the Wheel.<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1468
Manifesto
2020-01-02T05:37:22Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
What's all this brown shit? <br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black and heavy and huge and ponderous--not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our jobs are scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
Grandmaster Turing, I'm putting my shoulder to the Wheel.<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1467
Manifesto
2020-01-02T05:36:12Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
What's all this brown shit? <br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black and heavy and huge and ponderous--not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. Teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our FORTRAN is scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1466
Manifesto
2020-01-02T05:35:48Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
What's all this brown shit? <br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black and heavy and huge and ponderous--not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. My teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to crave a "Ninja"? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our FORTRAN is scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1465
Manifesto
2020-01-02T05:35:11Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
What's all this brown shit? <br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black and heavy and huge and ponderous--not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly. My teeth glint phosphoric as I grin behind the CRT.<br />
<br />
It augurs some days positively lethal.<br />
<br />
You claim to want a Ninja? A "rock star"? I'm only a little embarrassed about sometimes feeling a God.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our FORTRAN is scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1464
Manifesto
2020-01-02T05:32:22Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
What's all this brown shit? <br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black and heavy and huge and ponderous--not unlike its owner. We move like a tremendous machine. With great gusto it roars '''CLACK CLACK CLACK''', flirting with the speed of synapses in a vacuum. We mow down thoughtstuff like doughboys, bent double like old beggars under sacks, falling at Somme into the long grave already dug.<br />
<br />
We are ferociously jolly.<br />
My teeth glint phosphoric as I grin behind the CRT.<br />
Some days I feel positively lethal.<br />
Unauthorized access is not so unfar from Godhood.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our FORTRAN is scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1463
Manifesto
2020-01-02T05:20:27Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
<br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
Mark Shuttleworth seems sexually attracted to the color brown.<br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black, and huge, and goes '''CLACK CLACK CLACK''' because twenty-five thousand lights winked out in the struggle against a perfidious and tyrannical Albion, goddamnit.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our FORTRAN is scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1462
Manifesto
2020-01-02T05:18:08Z
<p>Dank: </p>
<hr />
<div>The ideas herein are stated more prosaically and less personally in my kinda-essay, "[https://www.sprezzatech.com/blog/0010-why-sprezzos-is-necessary.html Why is SprezzOS Necessary?]"<br />
<hr/><br />
<br />
<br />
<tt>We are the hackers, dreamers of the Electric Dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
<br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
What's all this brown shit? <br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black, and huge, and goes '''CLACK CLACK CLACK''' because twenty-five thousand lights winked out in the struggle against a perfidious and tyrannical Albion, goddamnit.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our FORTRAN is scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1461
Manifesto
2020-01-02T05:12:36Z
<p>Dank: </p>
<hr />
<div><tt>We are the hackers, dreamers of electric dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
<br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
What's all this brown shit? <br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black, and huge, and goes '''CLACK CLACK CLACK''' because twenty-five thousand lights winked out in the struggle against a perfidious and tyrannical Albion, goddamnit.<br />
<br />
My workstation? A one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell? My bard. Pray sing my story to the ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This Machine Kills Fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our FORTRAN is scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Manifesto&diff=1460
Manifesto
2020-01-02T05:10:15Z
<p>Dank: </p>
<hr />
<div><tt>We are the hackers, dreamers of electric dreams.<br />
<br />
<br />
We have known promethean creation, willing potent effect from exertion of the imagination.<br />
<br />
We took a brief excursion through a forbidden zone -- just a few nanoseconds -- and came out 0 having gone in 1.<br />
<br />
The creative life is a beautiful thing, a gift not meted to all people.<br />
<br />
The price of these powers is an unrelenting call, capable of drowning out the rest of life.<br />
<br />
We begat the boxes. The computers make us more and less than we were.<br />
<br />
We press on.<br />
<br />
<br />
We celebrate Grandmaster Turing's Machines, cheer their ever more pervasive ubiquity,<br />
<br />
and look to the elimination of the menial, and the life of the world to come.<br />
<br />
Not a single aspect of our essence will go untouched by these magnificent automata.<br />
<br />
At the frontiers of application and design you'll find always hackers,<br />
<br />
humming in tymbalic swarm and batrachian chorus<br />
<br />
(also lone diving silent screaming eagles),<br />
<br />
angelheaded hipsters burning for a connection to the evanescent IRC dynamo in the machinery of night.<br />
<br />
When gone, our code will speak for us. Our code too then will go.<br />
<br />
Codefined now with our repos, we'll leave legacy tripartite:<br />
<br />
genetic, energetic, algorithmic. But all are code.<br />
<br />
<br />
That said, I don't necessarily care for my desktop to look like a fucking cellphone.<br />
<br />
When I want an Apple, I'll buy one. What I lack in empathy I make up in disposable income.<br />
<br />
Furthermore, you *will* give me a "shutdown" button.<br />
<br />
I wish to unhear this twice-digested bullshit about sending desktop searches to Amazon.<br />
<br />
Did we lose a war?<br />
<br />
That isn't America.<br />
<br />
That isn't even Mexico.<br />
<br />
And no, I do not care to consult the Info page; I am furthermore uninterested in the Free Software Foundation's opinions regarding man pages.<br />
<br />
The GNU info browser suggests nothing more than the squaring of autism itself, stuffed into some broken fork of UW-Pine.<br />
<br />
When did people start misspelling "d" as "Kit"?<br />
<br />
When did it become acceptable for the output of the "set" shell builtin to scroll?<br />
<br />
What's all this brown shit? <br />
<br />
I'm long-consumed by crotchet. bash as /bin/sh gets my hackles up.<br />
<br />
I worry sometimes that in the mirror I've found the Last FORTRAN Hero.<br />
<br />
When I press "delete" in a file manager, why am I surprised by a result strangely unrelated to prompt deletion of files?<br />
<br />
We stand at the cusp of a world that would have /bin/rm removed, if anyone was thought to use a "shell", on their "workstations", with a "keyboard".<br />
<br />
My keyboard is black, and huge, and goes '''CLACK CLACK CLACK''' because twenty-five thousand lights winked out in the struggle against a perfidious and tyrannical Albion, goddamnit.<br />
<br />
My workstation is the one-man band that starts with the bleedin' mouf organ and ends with the big bass drum.<br />
<br />
My shell is my bard. It sings my story to ladies of history's court.<br />
<br />
From springs' bucklings ring peals of freedom's tintinnabulations.<br />
<br />
At night, my terminal defends the Dream.<br />
<br />
This machine kills fascists.<br />
<br />
<br />
When you want to experiment with violent UI changes, start a new project. Until then,<br />
<br />
cube my desktop, tile my windows, for the love of god switch between them when I press Alt-Tab,<br />
<br />
and do cool things with my video card when I'm not CUDAing my way to petrochemical exploration and missile guidance.<br />
<br />
Together -- I, hacker; you, machine, begotten not made, consubstantial -- we are unstoppable.<br />
<br />
We sound our barbaric YAWP over the rooftops of the world.<br />
<br />
Let the Earth tremble as our FORTRAN is scheduled!<br />
<br />
<br />
Nothing is too big to be knocked on its ass, and everything is cool.<br />
<br />
Making an apple pie from scratch requires first inventing a Universe.<br />
<br />
'''CLACK CLACK CLACK''', baby. Let's get to work.<br />
<br />
<br />
<br />
''2013-01-25 0100 EST''</tt></div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Copyright&diff=1459
MediaWiki:Copyright
2020-01-02T04:38:02Z
<p>Dank: </p>
<hr />
<div>Copyright © Sprezzatech 2012–2020. Content is available under $1.</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS&diff=1458
SprezzOS
2019-07-11T01:42:16Z
<p>Dank: /* Misc */ we don't load the rssfeed extension anymore</p>
<hr />
<div>'''''SprezzOS: Reshaping the Linux ecosystem, one splinter cell at a time.'''''<br />
<br />
SprezzOS is a Linux distribution dedicated to the lost arts of high performance, robust computing, and freewheeling hackery. Some distros make their mark playing around with desktop theming; we're rewriting core system tools. While they're authoring constitutions and holding votes, we're assaulting the heart of userspace and generating useful patches for upstream.<br />
<br />
SprezzOS is derived from [http://www.debian.org/ Debian], and is an active member of the [http://wiki.debian.org/Derivatives/Census/SprezzOS Debian Derivatives Census]. While SprezzOS is a product of [https://www.sprezzatech.com Sprezzatech], which retains final control over its definition, contributions from the community are actively welcomed. All SprezzOS development is open, and has been from the beginning. SprezzOS at its heart is a rolling, rapidly-evolving operating system atop the [[Linux]] kernel; when the term "SprezzOS" is used by itself, it is this continuum (the "trunk") which is referenced. It is intended that users generally install this trunk, and rely on its frequent updates. From time to time, a snapshot will be taken of the distribution, defining a more static [[:CATEGORY: SprezzOS Releases|release]]. New installation media will be released as minor version updates to these releases as the need arises.<br />
<br />
Might you be among our [[target audience]]? Good, good.<br />
<br />
{{Release Matrix}}<br />
<br />
==Documentation==<br />
<div style="float:left; display:inline-block">{{:SprezzOS Handbook}}</div><br />
<div style="float:left; padding: 1em; "><br />
*'''For users:''' [[Release Model]], [[Glossary]]<br />
*'''For developers:''' [[Contributing]]<br />
* SWOON, the [[SprezzOS Weekly News|SprezzOS Weeklyish News]]<br />
** Technically the "''SprezzOS Weeklyish Oblations, Objections, and News''"<br />
* Documentation for [[Installer development]]<br />
* Documentation for [[native tools]]<br />
* "[[SprezzOS and Debian]]" -- an introduction to SprezzOS for Debian developers<br />
* "[[Debian and SprezzOS]]" -- an introduction to Debian for [[sprezzadevs]]<br />
* The [http://www.sprezzatech.com/blog/index.html Sprezzatech blog]<br />
</div><br />
<br />
<div style="clear: both;"></div><br />
<br />
==Infrastructure==<br />
{|<br />
|-<br />
| [https://www.sprezzatech.com/apt/swip SWIP], the SprezzOS Web Interface to Packages<br />
|-<br />
| [https://www.sprezzatech.com/bugs Bugzilla]<br />
|-<br />
| Listing of [[source repositories]]<br />
|-<br />
| [https://plus.google.com/communities/115626956915136842413 SprezzOS! Google+ community]<br />
|-<br />
| [[Autobuilder]]<br />
|-<br />
|}<br />
{{SupportBody}}<br />
==Misc==<br />
* Our mascot, [[mascot|Natasha the orca]], was chosen because orcas are awesome.<br />
* SprezzOS is happily hosted at [http://www.linode.com/ Linode Atlanta].<br />
* Hail Eris!<br />
__NOTOC__</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Template:SupportBody&diff=1457
Template:SupportBody
2013-09-27T23:03:38Z
<p>Dank: /* Mailing Lists */</p>
<hr />
<div>==Mailing Lists==<br />
* The low-traffic [https://groups.google.com/forum/#!forum/sprezzos-announce sprezzos-announce] Google Group features moderated announcements.<br />
** You are strongly advised to subscribe to sprezzos-announce.<br />
* The [https://groups.google.com/forum/#!forum/sprezzos-dev sprezzos-dev] Google Group covers development discussion.<br />
** It also receives copies of all Bugzilla mail.<br />
** It also receives copies of all commits.<br />
** This mailing list is quite data-intense.<br />
* The [https://groups.google.com/forum/#!forum/sprezzos-users sprezzos-users] Google Group covers all other discussion.<br />
<br />
==Paid Support==<br />
Custom development and SLA-driven support for SprezzOS is available from [https://www.sprezzatech.com Sprezzatech], the SprezzOS Project's commercial governing body and primary sponsor.</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Autobuilder&diff=1456
Autobuilder
2013-05-20T18:13:25Z
<p>Dank: Created page with "We wish for package updates to be as automatic as is possible."</p>
<hr />
<div>We wish for package updates to be as automatic as is possible.</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS&diff=1455
SprezzOS
2013-05-20T18:13:02Z
<p>Dank: </p>
<hr />
<div>'''''SprezzOS: Reshaping the Linux ecosystem, one splinter cell at a time.'''''<br />
<br />
SprezzOS is a Linux distribution dedicated to the lost arts of high performance, robust computing, and freewheeling hackery. Some distros make their mark playing around with desktop theming; we're rewriting core system tools. While they're authoring constitutions and holding votes, we're assaulting the heart of userspace and generating useful patches for upstream.<br />
<br />
SprezzOS is derived from [http://www.debian.org/ Debian], and is an active member of the [http://wiki.debian.org/Derivatives/Census/SprezzOS Debian Derivatives Census]. While SprezzOS is a product of [https://www.sprezzatech.com Sprezzatech], which retains final control over its definition, contributions from the community are actively welcomed. All SprezzOS development is open, and has been from the beginning. SprezzOS at its heart is a rolling, rapidly-evolving operating system atop the [[Linux]] kernel; when the term "SprezzOS" is used by itself, it is this continuum (the "trunk") which is referenced. It is intended that users generally install this trunk, and rely on its frequent updates. From time to time, a snapshot will be taken of the distribution, defining a more static [[:CATEGORY: SprezzOS Releases|release]]. New installation media will be released as minor version updates to these releases as the need arises.<br />
<br />
Might you be among our [[target audience]]? Good, good.<br />
<br />
{{Release Matrix}}<br />
<br />
==Documentation==<br />
<div style="float:left; display:inline-block">{{:SprezzOS Handbook}}</div><br />
<div style="float:left; padding: 1em; "><br />
*'''For users:''' [[Release Model]], [[Glossary]]<br />
*'''For developers:''' [[Contributing]]<br />
* SWOON, the [[SprezzOS Weekly News|SprezzOS Weeklyish News]]<br />
** Technically the "''SprezzOS Weeklyish Oblations, Objections, and News''"<br />
* Documentation for [[Installer development]]<br />
* Documentation for [[native tools]]<br />
* "[[SprezzOS and Debian]]" -- an introduction to SprezzOS for Debian developers<br />
* "[[Debian and SprezzOS]]" -- an introduction to Debian for [[sprezzadevs]]<br />
* The [http://www.sprezzatech.com/blog/index.html Sprezzatech blog]<br />
</div><br />
<br />
<div style="clear: both;"></div><br />
<br />
==Infrastructure==<br />
{|<br />
|-<br />
| [https://www.sprezzatech.com/apt/swip SWIP], the SprezzOS Web Interface to Packages<br />
|-<br />
| [https://www.sprezzatech.com/bugs Bugzilla]<br />
|-<br />
| Listing of [[source repositories]]<br />
|-<br />
| [https://plus.google.com/communities/115626956915136842413 SprezzOS! Google+ community]<br />
|-<br />
| [[Autobuilder]]<br />
|-<br />
|}<br />
{{SupportBody}}<br />
==Misc==<br />
* Our mascot, [[mascot|Natasha the orca]], was chosen because orcas are awesome.<br />
* SprezzOS is happily hosted at [http://www.linode.com/ Linode Atlanta].<br />
* Hail Eris!<br />
<rss>http://www.sprezzatech.com/rss.xml|charset=UTF-8|max=5</rss><br />
__NOTOC__</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=APT&diff=1454
APT
2013-05-09T05:28:41Z
<p>Dank: /* Best Practices */</p>
<hr />
<div>The Advanced Packaging Tool and its various frontends form the package management core of Debian and Debian-derived distributions such as SprezzOS. There are two types of packages -- sources (<tt>.dsc</tt>) and binaries (<tt>.deb</tt>). A source package typically contains (usually platform-neutral) original source code and associated files from an upstream vendor. In addition to making available these source packages, the distribution builds zero or more (usually several) binary packages from each source package. Most users will make exclusive use of binary packages, but source packages are available to facilitate unlimited customization, optimization, and flexibility. It is quite possible to build all installed packages locally from source, though not usually desirable.<br />
<br />
There are roughly 5,000 ways to do any given thing with APT. I do not mean to imply that this is a feature.<br />
<br />
==Default paths==<br />
* <tt>/var/lib/apt</tt> and <tt>/var/lib/dpkg</tt> -- the local APT database. It's best not to touch these by hand.<br />
* <tt>/var/cache/apt/archives</tt> -- locally downloaded packages.<br />
* <tt>/etc/apt/trusted.gpg.*</tt> -- the local key database<br />
* <tt>/etc/apt/sources.*</tt> -- the local archives database<br />
* <tt>/etc/apt/apt.conf.*</tt> -- the local configuration database<br />
* <tt>/var/cache/apt/apt-file</tt> -- the local Contents database<br />
* <tt>/var/log/apt/</tt> and <tt>/var/log/aptitude*</tt> -- local APT and aptitude logs<br />
<br />
==Relevant man pages==<br />
* <tt>deb(5)</tt> -- The deb binary package format, since Debian 0.93. Older versions are documented in <tt>deb-old(5)</tt>.<br />
* <tt>deb-version(5)</tt> -- Version number semantics.<br />
===Working with the database===<br />
* <tt>apt-get(8)</tt> -- command line interactive package tool<br />
* <tt>dpkg(1)</tt> -- command line local package database management<br />
* <tt>aptitude(8)</tt> -- modern ncurses interactive package tool.<br />
* <tt>dselect(1)</tt> -- horrible old ncurses interactive package tool. Avoid at all costs.<br />
* <tt>apt-cache(8)</tt>, <tt>dpkg-query(1)</tt> -- query the database<br />
====Special databases====<br />
* <tt>apt-key(8)</tt> -- manage the key database<br />
* <tt>apt-file(8)</tt> -- query the Contents database (file contents of packages in archives)<br />
* <tt>apt-mark(8)</tt> -- manage automatic-installs database<br />
===Creating packages===<br />
* <tt>deb-control(5)</tt> -- The <tt>control</tt> files required to generate binary packages from source.<br />
** A given source package maps to a single control file, in which it is described.<br />
** A given source package can yield one or more binary packages. Each will have an entry in the control file.<br />
* <tt>dch(1)</tt>, <tt>debchange(1)</tt> -- Tools for managing <tt>changelog</tt> files.<br />
===Working with debs===<br />
* <tt>dpkg-deb(1)</tt> -- Unpacks, packs, dumps information about local <tt>.deb</tt> files.<br />
===Working with dscs===<br />
* <tt>apt-src(1p)</tt> -- Downloads, builds, and upgrades locally-unpackaged <tt>.dsc</tt> files<br />
<br />
==Repositories==<br />
A repository toplevel contains at least two subdirectories, <tt>dists</tt> and <tt>pool</tt>.<br />
===dists===<br />
<tt>dists</tt> contains subdirectories corresponding to distributions, and optionally symlinks (to facilitate distribution aliases). Each subdirectory contains:<br />
* <tt>Release</tt> -- Information about the distribution (including what components are available), and cryptographic hashes of all files in subdirectories of the distribution toplevel,<br />
* <tt>Release.gpg</tt> -- A signature of <tt>Release</tt><br />
* <tt>InRelease</tt> -- A copy of <tt>Release</tt> with an inline signature<br />
* subdirectories corresponding to each Component contained within <tt>Release</tt>. Within each is:<br />
** Contents files listing the files in each package, used by <tt>apt-file</tt><br />
** Subdirectories corresponding to the various architectures contained in each distributionXcomponent, containing:<br />
*** <tt>Packages</tt> -- A listing of control file data from the packages in this distributionXcomponentXarchitecture<br />
*** <tt>Packages.gz</tt> -- A compressed version of same<br />
*** <tt>Release</tt> -- Information about this distributionXcomponentXarchitecture<br />
===pools===<br />
<tt>pools</tt> contains subdirectories corresponding to components. Within each component's subdirectory are 52 subdirectories, a-z and liba-libz. Within each is a subdirectory for every source package prefixed by that subdirectory's name. Within each of these subdirectories are the various outputs of the package-building process:<br />
* An original source file<br />
* A gzipped diff<br />
* A .dsc file<br />
* Generated packages<br />
<br />
<br />
==Packaging==<br />
===Best Practices===<br />
* Make sure <tt>dh_install</tt> is invoked with <tt>--fail-missing</tt>. This can be done in cdbs by adding to <tt>rules</tt>:<br />
<pre>DEB_DH_INSTALL_ARGS+=--fail-missing</pre><br />
or in debhelper with:<br />
<pre>override_dh_install:<br />
dh_install --fail-missing</pre><br />
* Remove .la files unless they're truly necessary. In CDBS, add something like the following to <tt>rules</tt>:<br />
<pre>common-build-arch::<br />
find debian -name '*.la' -delete -print</pre><br />
Alternatively, simply don't install these files. In that case, add <tt>-X.la</tt> to <tt>dh_install --fail-missing</tt>.<br />
<br />
===Recipes===<br />
====Autoreconf====<br />
* Run <tt>autoreconf</tt> at the configure step using debhelper:<br />
** Add a Build-Depends on dh-autoreconf<br />
** Replace %: with<br />
<pre>%:<br />
dh $@ --with autoreconf</pre><br />
* Run <tt>./autogen.sh</tt> rather than <tt>autoreconf</tt>, still using debhelper:<br />
** Repeat the steps taken above<br />
** Override dh_autoreconf, and pass the script as a parameter:<br />
<pre>override_dh_autoreconf:<br />
dh_autoreconf ./autogen.sh</pre><br />
* Call ./autogen.sh at the configure step, but using CDBS:<br />
** Add a Build-Depends on dh-autoreconf<br />
** Add the following:<br />
<pre>include /usr/share/cdbs/1/rules/autoreconf.mk<br />
DEB_DH_AUTORECONF_ARGS += $(CURDIR)/autogen.sh</pre><br />
* Pass an extra argument to configure using CDBS:<br />
** Add the following to rules:<br />
<pre>DEB_CONFIGURE_EXTRA_FLAGS += extraarg</pre><br />
<br />
====Cmake====<br />
* Use <tt>cmake</tt> with CDBS:<br />
** Add the following to rules:<br />
<pre>include /usr/share/cdbs/1/rules/debhelper.mk<br />
include /usr/share/cdbs/1/class/cmake.mk</pre><br />
* Pass arguments to <tt>cmake</tt> from CDBS:<br />
** Augment and export DEB_CMAKE_CFLAGS, eg:<br />
<pre>export DEB_CMAKE_CFLAGS+=-DGLIB_DISABLE_DEPRECATION_WARNINGS<br />
export DEB_CMAKE_EXTRA_FLAGS+="-DCMAKE_BACKWARDS_COMPATIBILITY=2.2"<br />
</pre><br />
<br />
====Testing====<br />
* To disable the testing step in debhelper, override dh_auto_test with any empty target:<br />
<pre>override_dh_auto_test:</pre><br />
* To override the testing step in cdbs, provide the nocheck option:<br />
<pre>DEB_BUILD_OPTIONS=nocheck</pre><br />
<br />
===Watchfiles===<br />
Watchfiles are used together with the <tt>uscan</tt> tool to check for new upstream releases. <br />
* [https://launchpad.net/ Launchpad]: <pre>http://launchpad.net/package/+download .*/package-([\d\.]+)\.tar\..*</pre><br />
* [http://sourceforge.net/ SourceForge]: <pre>http://sf.net/owner/package-([\d\.]+)\.tar\..*</pre><br />
* [http://github.com GitHub tag]: <pre>https://github.com/owner/package/tags/ .*/v([\d\.]+)\.tar\..*</pre><br />
<br />
==See Also==<br />
* [[Raptorial]]<br />
<br />
{{Handbook}}<br />
<br />
[[CATEGORY: Glossaried]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1453
SprezzOS and Debian
2013-05-09T05:18:31Z
<p>Dank: /* Non-philosophical differences */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences arise from this distinction. Generally, SprezzOS applauds the aims and decisions of Debian, and most divergences are based on pragmatic (rather than philosophical or technical) concerns.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG (see "[[Why SprezzOS?]]" for more details). As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories of / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* SprezzOS currently targets only the amd64 architecture<br />
* SprezzOS currently distributes only the Linux kernel<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
* Considerable latitude is taken with the Debian Policy Manual, including but not limited to:<br />
** 4.4 The [[world|sprezzos-world]] git repository is the history of record. Changelog files would ideally be derived automatically from this history. In the meantime, they are officially used only to drive package versioning. Other information ought not be expected therein, though it may at times be provided.<br />
** 4.5 & 12.5 Life being short, and our time finite, SprezzOS does not require the inclusion nor maintenance of machine-readable copyright files<br />
** 12.1 Missing man pages ought be reported to either the Debian bugtracker, or the upstream bugtracker if the package was not a Debian package<br />
*** SprezzOS is not in the business of maintaining man pages. If you write one, fork upstream and convince us to use your fork.<br />
** 12.3 It is desirable that all distributed documentation be installed in the main package.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1452
SprezzOS and Debian
2013-05-09T05:12:42Z
<p>Dank: /* Non-philosophical differences */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences arise from this distinction. Generally, SprezzOS applauds the aims and decisions of Debian, and most divergences are based on pragmatic (rather than philosophical or technical) concerns.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG (see "[[Why SprezzOS?]]" for more details). As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories of / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* SprezzOS currently targets only the amd64 architecture<br />
* SprezzOS currently distributes only the Linux kernel<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
* Considerable latitude is taken with the Debian Policy Manual, including but not excluded to:<br />
** 4.4 The [[world|sprezzos-world]] git repository is the history of record. Changelog files would ideally be derived automatically from this history. In the meantime, they are officially used only to drive package versioning. Other information ought not be expected therein, though it may at times be provided.<br />
** 4.5 & 12.5 Life being short, and our time finite, SprezzOS does not require the inclusion nor maintenance of machine-readable copyright files<br />
** 12.1 Missing man pages ought be reported to either the Debian bugtracker, or the upstream bugtracker if the package was not a Debian package<br />
*** SprezzOS is not in the business of maintaining man pages. If you write one, fork upstream and convince us to use your fork.<br />
** 12.3 It is desirable that all distributed documentation be installed in the main package.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1451
SprezzOS and Debian
2013-05-09T05:08:38Z
<p>Dank: /* SprezzOS eschews maintainers */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences arise from this distinction. Generally, SprezzOS applauds the aims and decisions of Debian, and most divergences are based on pragmatic (rather than philosophical or technical) concerns.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG (see "[[Why SprezzOS?]]" for more details). As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories of / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
* Considerable latitude is taken with the Debian Policy Manual, including but not excluded to:<br />
** 4.4 The [[world|sprezzos-world]] git repository is the history of record. Changelog files would ideally be derived automatically from this history. In the meantime, they are officially used only to drive package versioning. Other information ought not be expected therein, though it may at times be provided.<br />
** 4.5 & 12.5 Life being short, and our time finite, SprezzOS does not require the inclusion nor maintenance of machine-readable copyright files<br />
** 12.1 Missing man pages ought be reported to either the Debian bugtracker, or the upstream bugtracker if the package was not a Debian package<br />
*** SprezzOS is not in the business of maintaining man pages. If you write one, fork upstream and convince us to use your fork.<br />
** 12.3 It is desirable that all distributed documentation be installed in the main package.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1450
SprezzOS and Debian
2013-05-09T04:11:28Z
<p>Dank: /* SprezzOS eschews maintainers */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences arise from this distinction. Generally, SprezzOS applauds the aims and decisions of Debian, and most divergences are based on pragmatic (rather than philosophical or technical) concerns.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG (see "[[Why SprezzOS?]]" for more details). As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories off / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
* Considerable latitude is taken with the Debian Policy Manual, including but not excluded to:<br />
** 4.4 The [[world|sprezzos-world]] git repository is the history of record. Changelog files would ideally be derived automatically from this history. In the meantime, they are officially used only to drive package versioning. Other information ought not be expected therein, though it may at times be provided.<br />
** 4.5 & 12.5 Life being short, and our time finite, SprezzOS does not require the inclusion nor maintenance of machine-readable copyright files<br />
** 12.1 Missing man pages ought be reported to either the Debian bugtracker, or the upstream bugtracker if the package was not a Debian package<br />
*** SprezzOS is not in the business of maintaining man pages. If you write one, fork upstream and convince us to use your fork.<br />
** 12.3 It is desirable that all distributed documentation be installed in the main package.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1449
SprezzOS and Debian
2013-05-09T03:56:58Z
<p>Dank: /* How does SprezzOS differ from Debian? */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences arise from this distinction. Generally, SprezzOS applauds the aims and decisions of Debian, and most divergences are based on pragmatic (rather than philosophical or technical) concerns.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG (see "[[Why SprezzOS?]]" for more details). As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership)). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories off / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
* Considerable latitude is taken with the Debian Policy Manual, including but not excluded to:<br />
** 4.4 The [[world|sprezzos-world]] git repository is the history of record. Changelog files would ideally be derived automatically from this history. In the meantime, they are officially used only to drive package versioning. Other information ought not be expected therein, though it may at times be provided.<br />
** 4.5 & 12.5 Life being short, and our time finite, SprezzOS does not require the inclusion nor maintenance of machine-readable copyright files<br />
** 12.1 Missing man pages ought be reported to either the Debian bugtracker, or the upstream bugtracker if the package was not a Debian package<br />
*** SprezzOS is not in the business of maintaining man pages. If you write one, fork upstream and convince us to use your fork.<br />
** 12.3 It is desirable that all distributed documentation be installed in the main package.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1448
SprezzOS and Debian
2013-05-09T03:55:39Z
<p>Dank: /* Non-philosophical differences */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences arise from this distinction.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG (see "[[Why SprezzOS?]]" for more details). As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership)). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories off / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
* Considerable latitude is taken with the Debian Policy Manual, including but not excluded to:<br />
** 4.4 The [[world|sprezzos-world]] git repository is the history of record. Changelog files would ideally be derived automatically from this history. In the meantime, they are officially used only to drive package versioning. Other information ought not be expected therein, though it may at times be provided.<br />
** 4.5 & 12.5 Life being short, and our time finite, SprezzOS does not require the inclusion nor maintenance of machine-readable copyright files<br />
** 12.1 Missing man pages ought be reported to either the Debian bugtracker, or the upstream bugtracker if the package was not a Debian package<br />
*** SprezzOS is not in the business of maintaining man pages. If you write one, fork upstream and convince us to use your fork.<br />
** 12.3 It is desirable that all distributed documentation be installed in the main package.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1447
SprezzOS and Debian
2013-05-09T03:43:13Z
<p>Dank: /* SprezzOS operates outside the DFSG */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences arise from this distinction.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG (see "[[Why SprezzOS?]]" for more details). As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership)). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories off / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1446
SprezzOS and Debian
2013-05-09T03:42:48Z
<p>Dank: /* How does SprezzOS differ from Debian? */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences arise from this distinction.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG; see "[[Why SprezzOS?]]" for more details. As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership)). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories off / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=Glossary&diff=1445
Glossary
2013-05-09T03:41:49Z
<p>Dank: </p>
<hr />
<div>Lingo and terminology you'll hear bandied about among the users and developers of SprezzOS:<br />
<br />
* '''Allotrion.''' SprezzOS's default [[GUI#theming|theming]], as it applies to [[GRUB]], [[X.org]], window managers and widget toolkits.<br />
<br />
* '''APT.''' Debian's [http://en.wikipedia.org/wiki/Advanced_Packaging_Tool Advanced Packaging Tool], a system used to track and manage debs.<br />
** APT has multiple frontends, including [http://wiki.debian.org/apt-get apt-get], [http://wiki.debian.org/Aptitude Aptitude], [http://www.nongnu.org/synaptic/ Synaptic], and our own [[Raptorial]].<br />
<br />
* '''d-i.''' The Debian installer, on which s-i is based.<br />
<br />
* '''DBTS.''' The Debian Bug Tracking System (custom software) at http://www.debian.org/Bugs/.<br />
** Appropriate bugs are forwarded there from Sprezzabugs.<br />
<br />
* '''DD.''' A [http://wiki.debian.org/DebianDeveloper Debian Developer], a DPM with voting rights.<br />
** There being no votes within the SprezzOS Project, there is no class of sprezzadevs corresponding to DDs.<br />
<br />
* '''deb.''' The Debian [http://en.wikipedia.org/wiki/Deb_%28file_format%29 software package format], used by SprezzOS and other Debian-based distributions.<br />
** debs are generally served from an APT repository.<br />
<br />
* '''DPM.''' A [http://wiki.debian.org/DebianProjectMember Debian Project Member]. Corresponds to a SprezzOS Project sprezzadev.<br />
<br />
* '''FWTS.''' Ubuntu's [https://wiki.ubuntu.com/Kernel/Reference/fwts Firmware Test Suite], included on SprezzOS's install media.<br />
<br />
* '''[[HIC]].''' Hacker-in-Charge. A ([http://www.sprezzatech.com Sprezzatech]-appointed) governor herding the SprezzOS Project's team of cats.<br />
<br />
* '''NtO.''' Natasha the Orca, our [[mascot]]. She is consulted in moments of crisis; her blessing is sought for all our endeavors.<br />
<br />
* '''s-i.''' The SprezzOS [[Installer development|installer]], based off the Debian installer "d-i".<br />
** s-i involves several source trees:<br />
*** [https://github.com:dankamongmen/s-i.git s-i] (installer + udeb collection) at https://github.com:dankamongmen/s-i.git, corresponding to svn://svn.debian.org/svn/d-i/trunk<br />
*** [https://github.com:dankamongmen/sprezzos-installer.git sprezzos-installer] (installer core) at https://github.com:dankamongmen/sprezzos-installer.git, corresponding to git://git.debian.org/d-i/debian-installer<br />
*** [https://github.com:dankamongmen/SprezzOS.git SprezzOS] (install media builder) at https://github.com:dankamongmen/SprezzOS.git, with no known Debian correspondence<br />
*** Various udebs<br />
<br />
* '''Sprezzabugs.''' The SprezzOS bug tracker ([http://www.bugzilla.org/ Bugzilla]) at https://www.sprezzatech.com/bugs/.<br />
** When appropriate, bugs are forwarded to the DBTS; such bugs ought be tagged with the [https://www.sprezzatech.com/bugs/buglist.cgi?keywords=dbts%2C%20&keywords_type=allwords&list_id=880 dbts keyword].<br />
<br />
* '''[[sprezzadevs|sprezzadev]].''' A SprezzOS Project developer, i.e. anyone with commit access to the canonical [https://github.com/Sprezzatech SprezzOS repositories]. Corresponds to a Debian DPM.<br />
<br />
* '''Sprezzawiki.''' The SprezzOS wiki ([http://www.mediawiki.org/wiki/MediaWiki MediaWiki]) at https://www.sprezzatech.com/wiki, used to provide hyperlinked SprezzOS documentation.<br />
<br />
* '''SprezzOS Project.''' The totality of software, assets, and people (sprezzadevs) coming together to form SprezzOS.<br />
** The SprezzOS Project is sponsored (but not owned by) [http://www.sprezzatech.com Sprezzatech].<br />
** sprezzadevs retain copyright to their contributions to the Project.<br />
** This might be spun off into a non-profit organization.<br />
<br />
* '''udeb.''' "Microdeb" aka μdeb. A deb used in the installer, stripped down to bare essentials. See [http://d-i.alioth.debian.org/doc/internals/ch03.html Chapter 3] of the d-i manual, "D-I Components or udebs".<br />
<br />
* '''[[World]].''' All the software packaged for distribution with SprezzOS.<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=World&diff=1444
World
2013-05-09T03:41:03Z
<p>Dank: Created page with ""world" as used in the context of the SprezzOS Project is: * the body of software that is packaged for use with APT, and * the metadata used in the course of that packagin..."</p>
<hr />
<div>"world" as used in the context of the SprezzOS Project is:<br />
* the body of software that is packaged for use with [[APT]], and<br />
* the metadata used in the course of that packaging<br />
It lives in the [https://github.com/dankamongmen/sprezzos-world sprezzos-world] GitHub repository:<br />
* git clone https://github.com/dankamongmen/sprezzos-world.git<br />
[[CATEGORY: Glossaried]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_2&diff=1443
SprezzOS 2
2013-05-09T03:38:33Z
<p>Dank: </p>
<hr />
<div>{{Infobox Release<br />
| relmajor=2<br />
| image=[[File:kolmogorov-m.jpg|200px]]<br />
| caption=Андре́й Никола́евич Колмого́ро<br />
}}<br />
SprezzOS 2 will be named after Andrey Nikolaevich Kolmogorov. SprezzOS 2 will begin to differentiate SprezzOS from other distributions less by its choice of upstream software, and more by its native tools.<br />
<br />
Major goals include:<br />
* Introduction of [[raptorial]],<br />
* Automatic clustering for package downloads,<br />
* Automatic clustering for configuration backup, and<br />
* Collaborative gPXE<br />
<br />
==Release Goals==<br />
{|class="wikitable" border="1"<br />
! Major goal<br />
! Associated bug(s)<br />
|- <br />
|style="background: lightcyan;"| Support i686 multiarch<br />
|{{#bugzilla:id=634}}<br />
|-<br />
| style="background: lightskyblue;" | Speed up [[APT]]<br />
|{{#bugzilla:id=635,705,706,697,698}}<br />
|-<br />
| style="background: sandybrown;"| Provide a default, themed GUI<br />
||{{#bugzilla:id=250,484}}<br />
|-<br />
|}<br />
<br />
==Open bugs==<br />
===[[Raptorial]]===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=CONFIRMED,REOPENED,INPROGRESS<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|component=Raptorial<br />
|noresultsmessage=No matching bugs found.<br />
}}<br />
<br />
===Kernel and Installer===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=CONFIRMED,REOPENED,INPROGRESS<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|component=Kernel,Installer<br />
|noresultsmessage=No matching bugs found.<br />
}}<br />
<br />
===Growlight===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=CONFIRMED,REOPENED,INPROGRESS<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|component=Growlight<br />
|noresultsmessage=No matching bugs found.<br />
}}<br />
<br />
===World===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=CONFIRMED,REOPENED,INPROGRESS<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|component=World,World-KDE,World-GNOME<br />
|noresultsmessage=No matching bugs found.<br />
}}<br />
<br />
==Bugs closed by this release==<br />
===[[Raptorial]]===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=RESOLVED,VERIFIED<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|component=Raptorial<br />
|noresultsmessage=No matching bugs found.<br />
}}<br />
<br />
===Kernel and Installer===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=RESOLVED,VERIFIED<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|component=Kernel,Installer<br />
|noresultsmessage=No matching bugs found.<br />
}}<br />
<br />
===Growlight===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=RESOLVED,VERIFIED<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|component=Growlight<br />
|noresultsmessage=No matching bugs found.<br />
}}<br />
<br />
===[[World]]===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=RESOLVED,VERIFIED<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|component=World,World-KDE,World-GNOME<br />
|noresultsmessage=No matching bugs found.<br />
}}<br />
<br />
==Closed bugs==<br />
{{#bugzilla:columns=id,priority,status,to,component,summary,status<br />
|status=RESOLVED,VERIFIED<br />
|sort=priority,id<br />
|milestone=2.0.0 (Kolmogorov)<br />
|noresultsmessage="No matching bugs found."<br />
}}<br />
[[CATEGORY: SprezzOS Releases]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_1&diff=1442
SprezzOS 1
2013-05-09T03:38:10Z
<p>Dank: </p>
<hr />
<div>{{Infobox Release<br />
| relmajor=1<br />
| image=[[File:JohnvonNeumann.gif|200px]]<br />
| caption=[http://en.wikipedia.org/wiki/John_von_Neumann John von Neumann]<br />
}}<br />
The "von Neumann" release is the first mainstream, supported release of SprezzOS. It was released 2013-01-13, after being initially scheduled for release 2012-12-28.<br />
<br />
'''Download the current SprezzOS 1-series ISO ({{SprezzOS1Version}}) [https://www.sprezzatech.com/pub/sprezzos/releases/SprezzOS-{{SprezzOS1Version}}.iso here].'''<br />
<br />
The next epoch of SprezzOS development will yield [[SprezzOS 2|SprezzOS 2, "Kolmogorov"]].<br />
<br />
...and of course there's a release video, "[http://www.youtube.com/watch?v=BqPCINSLRPQ Orcas on Segways]".<br />
<br />
This [https://plus.google.com/photos/118364511747568235669/albums/5841122304857060513 Google+ album] walks through use of Growlight in an install.<br />
<br />
==Release Notes==<br />
* The current installer version is '''{{SprezzOS1Version}}'''.<br />
** There is one known critical issue in this version:{{#bugzilla:id=390}}<br />
<pre>There is no known workaround for 390 save using other hardware.</pre><br />
* [https://www.sprezzatech.com/wiki/index.php/SprezzOS_Weekly_News SWOON 2013-01-30] has some relevant information about 1.0.3<br />
* As of SprezzOS 1's release, there were 5525 packages in the SprezzOS repositories.<br />
* 108 filed bugs were resolved in this development cycle.<br />
* Previous SprezzOS 1 installers are strongly deprecated by {{SprezzOS1Version}}.<br />
<br />
==Major changes since [[SprezzOS 0]]==<br />
* The Linux kernel has been upgraded to version 3.7.5<br />
* GRUB has been updated from 1.99 to 2.<br />
* EGLIBC 2.13 has been replaced with GNU libc 2.16<br />
* Systemd 197 has replaced sysvinit<br />
** biosdevname is now used to initially name network devices based off DMI<br />
* Perl has been updated to 5.16 from 5.14<br />
** A great many packages have been rebuilt<br />
** Many remain to be rebuilt; this is proceeding forthrightly<br />
* PulseAudio has been upgraded from 2.0 to 3.0<br />
* WPAsupplicant has been upgraded from 1.1 to 2.0<br />
* libjpeg has gone from soname 8 to 9<br />
* KDE has been upgraded from 4.8.4 to 4.9.5<br />
* Ubuntu's Unity and its subcomponents have been packaged<br />
* Mint's Cinnamon and its subcomponents have been packaged<br />
* Enlightenment 17 (E17) and its subcomponents have been packaged<br />
* cairo-dock and avant-window-navigator have been brought up-to-date with the ecosystem and repackaged<br />
* XFCE packages have been updated to 4.10 where possible<br />
* XBMC 12 rc3 has been packaged<br />
* Python 3.3 has been introduced<br />
* LLVM and Clang 3.2 have been introduced<br />
<br />
==Release Goals==<br />
{|class="wikitable" border="1"<br />
! Major goal<br />
! Associated bug(s)<br />
|- <br />
|style="background: sandybrown;"| Move from sysvinit to systemd.<br />
|{{#bugzilla:id=364,509,511,512,506,375}}<br />
|-<br />
| style="background: lightskyblue;" |Become self-hosting (build our own versions of all Essential/Required packages, and all packages used in the installer).<br />
|{{#bugzilla:id=249,231,466,491}}<br />
|-<br />
| style="background: sandybrown;"| Get installer working without intervention on most mainstream hardware.<br />
||{{#bugzilla:id=499,344,390,477,565}}<br />
|-<br />
|}<br />
<br />
==Open bugs==<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=CONFIRMED,REOPENED,INPROGRESS<br />
|sort=priority,id<br />
|milestone=1.0.0 (von Neumann)<br />
|noresultsmessage="No matching bugs found."<br />
}}<br />
<br />
==Closed bugs==<br />
===Kernel and Installer===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=RESOLVED,VERIFIED<br />
|sort=priority,id<br />
|milestone=1.0.0 (von Neumann)<br />
|component=Kernel,Installer<br />
|noresultsmessage="No matching bugs found."<br />
}}<br />
<br />
===Growlight===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=RESOLVED,VERIFIED<br />
|sort=priority,id<br />
|milestone=1.0.0 (von Neumann)<br />
|component=Growlight<br />
|noresultsmessage="No matching bugs found."<br />
}}<br />
<br />
===[[World]]===<br />
{{#bugzilla:columns=id,priority,to,component,summary,status<br />
|status=RESOLVED,VERIFIED<br />
|sort=priority,id<br />
|milestone=1.0.0 (von Neumann)<br />
|component=World,World-KDE,World-GNOME<br />
|noresultsmessage="No matching bugs found."<br />
}}<br />
<br />
[[CATEGORY: SprezzOS Releases]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1441
SprezzOS and Debian
2013-05-09T03:36:15Z
<p>Dank: </p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
There is one primary difference between SprezzOS and Debian: Debian is a large, worldwide community of volunteers operating under principles of explicit social consciousness, whereas SprezzOS is an investor-directed effort involving comparatively few people. The SprezzOS Project, despite being composed largely of free software, is a commercial endeavor existing at the pleasure, and in the interests, of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences flow from this distinction.<br />
<br />
===SprezzOS operates outside the DFSG===<br />
'''The SprezzOS Project has at no time adopted either the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines], or the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part)'''. Aside from the fact that doing so would restrict the Project's freedom to include that software it deems fit and useful, the SprezzOS Project has philosophical differences with the DFSG; see "[[Why SprezzOS?]]" for more details. As a happy side-effect, SprezzOS can thus remove all changes to upstream which exist only to facilitate the DFSG, which aids in other efforts (see below).<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership)). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' The .install files which drive dh_install and CDBS will, wherever possible, be minimized both in number and content. Specification of subdirectories off / and /usr/ is encouraged. Wildcards are considered preferable to explicit enumerations.<br />
* '''All files must be accounted for.''' The use of --fail-missing or an equivalent is strongly encouraged (see [[APT#Best_Practices|APT Best Practices]]). --list-missing is not much better than nothing at all, since most updates will proceed unobserved.<br />
===Build deps trigger rebuilds===<br />
When a new version of a build-dep is uploaded, it ought trigger an (artificially) acyclic wave of rebuilds (ideally, we would rebuild with cycles until a [http://en.wikipedia.org/wiki/Fixed_point_%28mathematics%29 fixed point] was reached, but this is probably not possible in the short term). This is ''not'' to be done using the means of, e.g. the [http://wiki.debian.org/Haskell DHG], wherein the version of build deps is strictly coded into the package deps. Instead, on the archive side, automated rebuilds will be authored and triggered, with cycles cut off via analysis of the (automatically-generated and thus strictly-formed) changelog entries. This is desirable (a) to reap the benefits of toolchain improvements, (b) to test the new toolchain, and (c) to ensure our source packages continue to build in a current binary environment.<br />
===Just say no to patching===<br />
Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
* They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
* By definition, they create divergence from upstream and fragment the ecosystem<br />
* and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines].<br />
===Non-philosophical differences===<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=SprezzOS_and_Debian&diff=1440
SprezzOS and Debian
2013-05-09T03:16:17Z
<p>Dank: /* How does SprezzOS differ from Debian? */</p>
<hr />
<div>''(This document is consciously modeled on "[https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Ubuntu for Debian Developers]".)''<br />
<br />
SprezzOS is proud to be based on [http://debian.org Debian], and wants to maintain a healthy and collaborative relationship with Debian developers.<br />
<br />
==How does SprezzOS differ from Debian?==<br />
There is one primary difference between SprezzOS and Debian: Debian is a large, worldwide community of volunteers, whereas SprezzOS is a commercial project with very few people involved. The SprezzOS Project, despite being composed largely of free software, is a commercial effort. It exists at the pleasure and in the interests of the [http://sprezzatech.com Sprezzatura Computing Corporation] ("Sprezzatech"). All meaningful differences flow from this distinction.<br />
<br />
===SprezzOS eschews maintainers===<br />
Debian relies upon (and explicitly states a design based around) "package maintainers": individuals or teams having primary responsibility for any given source package (where SprezzOS packages have been adapted from their Debian counterparts, these people (at the time of adaptation) are listed as <tt>XSBC-Original-Maintainer</tt>. Note that no effort is made to update these identifications when the upstream package changes maintainership)). This "ownership" ties into privileges to upload new packages. Note that the maintainers' wishes can be overruled by others in Debian, including the Technical Committee, and that "Non-Maintainer Uploads" (NMUs) are a regular occurrence. Ubuntu appears to place all packages under community maintenance, but also to tie "ownership" on their "Launchpad" system to the ability to upload.<br />
<br />
SprezzOS aims, to the greatest degree possible, to be automatically constructible. This is a practical necessity for the implementation of other agendas, such as automatic upstream-triggered updates and buildtools-triggered updates. As a result, package autobuilds are triggered by commits to the [[world|sprezzos-world]] git tree, and uploaded following successful autobuild. Commit access to [[world]] is an all-or-nothing proposition, and is held by all [[Sprezzadevs]]. In an ideal world, no one would need get involved in the packaging process -- updates would be detected on upstream servers, and the package appropriately rebuilt and repacked, all without user intervention. This is necessary for the long-term survival of SprezzOS: without a volunteer community, automation is the only means for keeping the many thousands of packages up to date. With this goal in mind, SprezzOS often makes the following amendments to Debian packages:<br />
* '''Combination of binary packages.''' Ideally, every source package would generate exactly one binary package per architecture (multiarch requirements seem to make this impossible given current packaging semantics). Some packages have good reasons for their division, others less so. Unfortunately, using existing packaging tools, construction of multiple binary packages from a given source is most reasonably accomplished via enumerative install manifests. No standard means of automating the addition of new output files to these lists is known. Essentially, anywhere that a division is made according to reasoning that can't easily be summarized in an algorithm, no such means ''can'' exist. SprezzOS thus prefers to merge binary packages wherever possible (typical examples include: multiple library binaries from one source, -doc packages, -dbg packages, and plugin packages (even where they add dependency chains to the main package)).<br />
* '''Minimization of install manifests.''' <br />
<br />
* The SprezzOS Project has adopted neither the [http://www.debian.org/social_contract.html#guidelines Debian Free Software Guidelines] nor the [http://ww.debian.org/social_contract.html Debian Social Contract] (of which they are a part).<br />
* The SprezzOS installer broadly diverges from the Debian installer (from which it is forked).<br />
* [[ZFS]] is used as a default filesystem and volume manager.<br />
* [[systemd]] has replaced sysvinit.<br />
* TCP wrapper support has been removed from most packages.<br />
* Mainline kernel security mechanisms are favored over userspace solutions and esoterica.<br />
** In particular, SELinux and TCP wrappers are not supported. The former almost certainly introduces security problems (atop the complexity it definitely introduces). The latter are better implemented using [[Networking#NAT_via_iptables|iptables]].<br />
* The kernel is likely to be more closely tracked in SprezzOS.<br />
* Maximal support of modern hardware is favored over broader support of older hardware.<br />
* [http://wiki.debian.org/Hardening Hardening flags] are not considered universally desirable.<br />
* Updates to the toolchain result in immediately-scheduled rebuilds of affected packages.<br />
* Patching the upstream sources is strongly frowned upon in SprezzOS, and Debian patches will be removed wherever possible.<br />
** They create multiple maintenance hassles, and make it more difficult to automatically update packages<br />
** By definition, they create divergence from upstream and fragment the ecosystem<br />
** <br />
** and, finally, let us never forget [http://xkcd.com/221/ this] [http://www.schneier.com/blog/archives/2008/05/random_number_b.html incident].<br />
** Where patching is done, SprezzOS adheres to the Debian [http://www.debian.org/doc/manuals/maint-guide/modify.en.html patching guidelines]<br />
<br />
===Archives===<br />
* Debian supports three ''archive areas'': <tt>main</tt>, <tt>contrib</tt>, and <tt>non-free</tt>.<br />
** Please see "[http://www.debian.org/doc/debian-policy/ch-archive.html#s-sections Archive Areas]" from the Debian Policy Manual for more details.<br />
** SprezzOS features only two: <tt>main</tt> and <tt>[[External_software#Blobs_repository|blobs]]</tt><br />
*** Please see ''[[External software]]'' from the [[SprezzOS Handbook|SprezzOS Handbook]] for more details.<br />
<br />
==What kind of changes does SprezzOS make to Debian packages?==<br />
This is in no way, and does not attempt to be, a comprehensive list of differences.<br />
===d-i and udebs===<br />
* Branding is modified in rootskel, main-menu, installer, and netcfg<br />
* A few helper binaries related to the console (fbvfbterm, tangoize, etc.) are added to rootskel<br />
* The i386 images are not built by default<br />
* The gtk installer is not built by default<br />
* Some configuration changes are effected via our initramfs-embedded preseed<br />
===Install media===<br />
* GRUB2 is used as our bootloader on all media<br />
===Kernel===<br />
* No firmware is removed for reasons of DGSF incompatibility<br />
* ReiserFS is removed for reasons of project-leader-in-prison incompatibility<br />
===Userspace===<br />
* Branding is modified in base-files<br />
* Packages are built with a SprezzOS suffix prior to the Debian revision number<br />
<br />
==What can I do if I feel SprezzOS has acted inappropriately?==<br />
Please contact the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
==How does SprezzOS cooperate with Debian?==<br />
* SprezzOS is an active member of the [http://wiki.debian.org/Derivatives/Census Debian Derivatives Census]<br />
* Bugs common to SprezzOS and Debian are filed in the [http://www.debian.org/Bugs/ DBTS]<br />
<br />
==Resources==<br />
* The [http://wiki.debian.org/Derivatives/Census/SprezzOS SprezzOS entry] in the Debian Derivatives Census.<br />
* The [http://sprezzos.com/debversions.html .deb versions matrix] is a table of package versions in SprezzOS, Debian, and Ubuntu.<br />
<br />
==Contact==<br />
The SprezzOS project ''in toto'' can be reached at the [mailto:sprezzos-dev@googlegroups.com sprezzos-dev] mailing list.<br />
<br />
The [[HIC]] (currently [[User:Dank|Nick Black]]) can be reached at [mailto:hic@sprezzatech.com spl@sprezzatech.com].<br />
<br />
==See also==<br />
* [[Debian and SprezzOS]], the inverse of this article<br />
<br />
[[CATEGORY: Census Links]]</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1439
MediaWiki:Sidebar
2013-05-04T07:38:07Z
<p>Dank: </p>
<hr />
<div>** SprezzOS_FAQ|FAQ<br />
** SprezzOS_1|SprezzOS 1<br />
** https://www.sprezzatech.com/bugs|SprezzaBugs</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1438
MediaWiki:Sidebar
2013-05-04T07:37:48Z
<p>Dank: </p>
<hr />
<div>** SprezzOS_FAQ|FAQ<br />
** SprezzOS_1|SprezzOS 1<br />
** https://www.sprezzatech.com/bugs|SprezzaBugs<br />
** Special:Recentchanges|Recent changes<br />
* TOOLBOX</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1437
MediaWiki:Sidebar
2013-05-04T07:37:28Z
<p>Dank: </p>
<hr />
<div>** SprezzOS_FAQ|FAQ<br />
** SprezzOS_1|SprezzOS 1<br />
** https://www.sprezzatech.com/bugs SprezzaBugs<br />
** Special:Recentchanges|Recent changes<br />
* TOOLBOX</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1436
MediaWiki:Sidebar
2013-05-04T07:35:46Z
<p>Dank: </p>
<hr />
<div>** SprezzOS_FAQ|FAQ<br />
** SprezzOS_1|SprezzOS 1<br />
** Special:Recentchanges|Recent changes<br />
* TOOLBOX</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1435
MediaWiki:Sidebar
2013-05-04T07:35:31Z
<p>Dank: </p>
<hr />
<div>** Special:Recentchanges|Recent changes<br />
** SprezzOS_FAQ|FAQ<br />
** SprezzOS_1|SprezzOS 1<br />
* TOOLBOX</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1434
MediaWiki:Sidebar
2013-05-04T07:35:09Z
<p>Dank: </p>
<hr />
<div>** Special:Recentchanges|Recent changes<br />
** SprezzOS_FAQ|FAQ<br />
* TOOLBOX</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1433
MediaWiki:Sidebar
2013-05-04T07:34:56Z
<p>Dank: </p>
<hr />
<div><br />
* TOOLBOX<br />
<br />
** Special:Recentchanges|Recent changes<br />
** SprezzOS_FAQ|FAQ</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1432
MediaWiki:Sidebar
2013-05-04T07:34:24Z
<p>Dank: </p>
<hr />
<div><br />
* TOOLBOX<br />
* Special:Recentchanges|Recent changes<br />
** SprezzOS_FAQ|FAQ</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1431
MediaWiki:Sidebar
2013-05-04T07:34:14Z
<p>Dank: </p>
<hr />
<div><br />
* TOOLBOX<br />
* Special:Recentchanges|Recent changes<br />
* SprezzOS_FAQ|FAQ</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1430
MediaWiki:Sidebar
2013-05-04T07:33:56Z
<p>Dank: </p>
<hr />
<div><br />
* TOOLBOX<br />
** Special:Recentchanges|Recent changes<br />
** SprezzOS_FAQ|FAQ</div>
Dank
https://www.sprezzatech.com/wiki/index.php?title=MediaWiki:Sidebar&diff=1429
MediaWiki:Sidebar
2013-05-04T07:33:26Z
<p>Dank: </p>
<hr />
<div><br />
* TOOLBOX<br />
* recentchanges-url|recentchanges<br />
** SprezzOS_FAQ|FAQ</div>
Dank