DocScrutinizer05 changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
dandon has quit [Ping timeout: 258 seconds]
arhuaco has quit [*.net *.split]
Ornotermes has quit [*.net *.split]
apelete has quit [*.net *.split]
roh has quit [*.net *.split]
astr has quit [*.net *.split]
eintopf has quit [*.net *.split]
tumdedum has quit [*.net *.split]
mirko has quit [*.net *.split]
mirko has joined #qi-hardware
tumdedum has joined #qi-hardware
astr has joined #qi-hardware
eintopf has joined #qi-hardware
dandon_ has joined #qi-hardware
arhuaco has joined #qi-hardware
Ornotermes has joined #qi-hardware
apelete has joined #qi-hardware
roh has joined #qi-hardware
xiangfu has joined #qi-hardware
atommann has joined #qi-hardware
astr has quit [Ping timeout: 260 seconds]
Textmode has joined #qi-hardware
atommann has quit [Ping timeout: 250 seconds]
viric has quit [Read error: Connection reset by peer]
viric has joined #qi-hardware
atommann has joined #qi-hardware
viric_ has joined #qi-hardware
viric has quit [Ping timeout: 260 seconds]
viric_ is now known as viric
jluis has joined #qi-hardware
Luke-Jr has quit [Read error: Connection reset by peer]
Luke-Jr has joined #qi-hardware
<arhuaco> wpwrak: You're a veteran UNIX developer. You can vote! :-P This technical world is full of drama. All the time.
<larsc> Survivor of the Unix wars
sulky has quit [Ping timeout: 265 seconds]
sulky has joined #qi-hardware
wolfspraul has joined #qi-hardware
jbenedetto has quit [Ping timeout: 255 seconds]
jbenedetto has joined #qi-hardware
atommann has quit [Quit: Leaving]
xiangfu has quit [Quit: leaving]
Textmode has quit [Quit: "It was one dev, naked in a room with a carton of cigarettes, a thermos full of coffee and bourbon, and all his summoned angels."]
Luke-Jr has quit [Ping timeout: 265 seconds]
viric has quit [Read error: Connection reset by peer]
viric has joined #qi-hardware
<wpwrak> nicksydney: heavy stuff :)
<wpwrak> larsc: it was the winter of 1970, the beginning of the epoch. we were down to our last PDP-11 and we were running out of inodes. ...
xiangfu has joined #qi-hardware
<kyak> he was so old, that his birth day could not be expressed in unix time
<larsc> and his beard so long it seemingly never ended
<kyak> it was the day he decided that Debian shall be forked..
wolfspraul has quit [Quit: leaving]
<wpwrak> kyak: correction: he was so old that people rumored that he was born before the epoch
<viric> normal, if the story starts in the beggining of the epoch
<viric> beginning
<wpwrak> viric: but that's not a requirement :)
<viric> "it was the winter of 1970, the beginning of the epoch. we were ..."
<viric> :)
<wpwrak> in the lands below the red castle, people lived in fear. at night, the poettering would spread its dark wings and fly over the barren land, descend on its hapless victims, sink its cruel yellow claws into them, and carry their screaming dying bodies back to his keep
<kyak> wpwrak must be good at telling bedtime stories to kids :)
<wpwrak> people spoke in hushed voices about the evil of the poettering. some said, his victims would be spun into the web of the systemd and their grotesquely disfigured corpses would be kept alive by vile binary magic
<kyak> small kids
<wpwrak> scared kids ;-)
<kyak> thanks to you, yes :)
<wpwrak> some said his victims would at times awaken from their numb agony and make short high-pitched screams that didn't sound like anything ever heard from a living creature. when the wind carried over these sound from the red castle, people averted their eyes and muttered "pulse audio"
<kyak> --) we will have quite a few sophisticated words in topwords :)
<kyak> !topwords
<qi-bot> Most used words in #qi-hardware: 1. epoch (4) 2. people (4) 3. would (4) 4. their (4) 5. beginning (3) 6. victims (3) 7. winter (2) 8. castle (2) 9. poettering (2) 10. sound (2)
<wpwrak> woe upon you. now you have summoned the beast !
<kyak> my tv just lost signal
<kyak> please, no!!
<wpwrak> some of the old villagers told stories of the time when they were known as the debian, a proud and free people. and they told of the fall, when the debian let in the warlocks of politicking.
<wpwrak> it is with their help that the poettering rose to power in these lands and now the debian are forced to renounce their beliefs and wear red hats, as the mark of the beast
<wpwrak> stories told of the fate of the warlocks of politicking. some say they live among the people, doing their evil in secrecy. other say they dwell a the castle and ride forth on moonless nights, mounted on eight-legged beasts that had no color nor would they cast any shadow for they were made of darkness itself
* kyak will have to drink a lot to get this horrible visions out of the head
<kristianpaul> wpwrak: you still using ubuntu?
<wpwrak> yup
<wpwrak> with a very long list of packages i remove ;-)
<kristianpaul> (-:
Nik05 has quit [Quit: leaving]
Nik05 has joined #qi-hardware
<kyak> oh, that's calling for a fork! --)
<larsc> remix ;)
<kyak> ubuntu dark knight edition
<larsc> maybe we should fork the kernel and remove all the systemd enablement stuff like cgroups and kdbus
<larsc> and call the fork Freax
<larsc> http://linuxfork.org/ is still available
<kyak> Hellyeax!
nicksydney_ has joined #qi-hardware
nicksydney has quit [Ping timeout: 244 seconds]
nicksydney has joined #qi-hardware
nicksydney_ has quit [Ping timeout: 244 seconds]
Nik05 has quit [Quit: leaving]
Nik05 has joined #qi-hardware
xiangfu has quit [Quit: leaving]
<larsc> so for a change in topic:
<larsc> "Hi developer, [...] as part of a research team [...] we are studying the practical use of the C preprocessor. In particular, we ask questions about the following main topics:
<larsc> - Why the C preprocessor is still widely used in practice?
<larsc> - What are the common problems of using preprocessor directives?
<larsc> - What are the alternatives to preprocessor directives?"
<ysionneau> wow, I wouldn't know what to answer
<ysionneau> ah nice picture!
<larsc> those are all horrible horrible examples
<mth> for example the first question isn't really answerable without knowing how much code we're talking about (1 line, 100 lines?)
<mth> plus usually you shouldn't test OS, but feature
<mth> who knows when the OS will get forked ;)
<whitequark> larsc: wow, that code.
Luke-Jr has joined #qi-hardware
sulky has quit [Ping timeout: 245 seconds]
sulky has joined #qi-hardware
Textmode has joined #qi-hardware