IRC log for #neo900 on 20150115

00:01.03DocScrutinizer05black, brown, red, orange, yellow, green, blue violet, gray, white
00:01.09DocScrutinizer05all you need to memorize
00:02.07DocScrutinizer05knowing brown=1, red=2, violet=7 helps a lot. yellow=4 comes automatically with all the 4k7
00:02.45DocScrutinizer05orange orange brown for 330 is also nice to remember
00:05.07DocScrutinizer05brown black red is almost the stereotype of a resistor
00:05.46DocScrutinizer051 0 00
00:06.29DocScrutinizer05<PROTECTED>
00:06.36DocScrutinizer05<PROTECTED>
00:07.09DocScrutinizer05now you almost must have learned it ;-)
00:08.28DocScrutinizer05next lesson: E12 ;-)
00:34.53*** join/#neo900 GMsoft (~gmsoft@cl-60.bru-01.be.sixxs.net)
00:45.50arossdotmeDocScrutinizer05, snag is when i'm working with not so typical usual resistors
00:47.07DocScrutinizer05:-)
00:47.19DocScrutinizer05I admit I often use a SMM then
00:47.24DocScrutinizer05DMM
00:48.23DocScrutinizer05it gets really nasty when you can't tell is it a inductor or a resistor or maybe even a capacitor
00:49.07DocScrutinizer05add to that some bleach out of colors, or white going gray or brown due to age and heat...
00:49.31DocScrutinizer05or yellow going white
00:49.44DocScrutinizer05add to that silver which often isn't
01:18.21*** join/#neo900 wpwrak (~werner@154-164-231-201.fibertel.com.ar)
01:18.21*** mode/#neo900 [+v wpwrak] by ChanServ
01:38.34*** join/#neo900 burper (~burper@modemcable082.140-131-66.mc.videotron.ca)
01:38.35*** part/#neo900 burper (~burper@modemcable082.140-131-66.mc.videotron.ca)
02:18.05*** join/#neo900 burper (~burper@modemcable082.140-131-66.mc.videotron.ca)
02:18.07*** part/#neo900 burper (~burper@modemcable082.140-131-66.mc.videotron.ca)
03:22.21DocScrutinizer05[2015-01-14 Wed 13:28:48] <SylvieLorxu> Oh god systemd actually has a firewall. I thought people in #debianfork were kidding...
03:24.02DocScrutinizer05http://www.phoronix.com/scan.php?page=news_item&px=systemd-networkd-IP-Forward
05:03.16wpwrakfirst then laugh about devuan, then they fight devuan, then devuan wins :)
05:04.00MonkeyofDoomdoes devuan have something *better* than systemd?
05:04.05MonkeyofDoomor do they just not have systemd
05:05.07OksanaThey do not have bloated I-am-Everything. They have separate thingies: init system, daemons, whatever. Just, not tying everything into one package.
05:05.39MonkeyofDoomright--do they have a good init system?
05:08.06Oksanahttps://www.devuan.org Currently, they are speaking about sysvinit. https://en.wikipedia.org/wiki/Init#SYSV
05:08.37MonkeyofDoomsysvinit is awful
05:12.38wpwrakit's nice and easy. the problem is more in how it's often used. but i think they may want to look at openrc later on. that's what gentoo uses, which alone pretty much guarantees that it's in the traditional spirit :)
05:13.04MonkeyofDoomlots of systems are easy
05:13.42MonkeyofDoomthe problem is that it's incredibly inefficient and that it's flexible in the wrong places
05:14.55MonkeyofDooma pile of shell scripts is great for one-off jobs but for core system management something that does more to guarantee correctness and allow people to work on a high-level is a pretty good idea
05:15.07wpwraki doubt systemd is noticeably more efficient than a well-written sysvinit-based system
05:15.47wpwrakwell, write a checker if you want such assurances
05:16.05MonkeyofDooma checker that parses shell scripts and performs static analysis?
05:16.08wpwrakby the time systemd runs it's too late to report problems anyway :)
05:16.28OksanaYes, found OpenRC. It's higher-level than sysVinit: https://wiki.manjaro.org/index.php?title=OpenRC,_an_alternative_to_systemd
05:16.43MonkeyofDoomformalizing the semantics of shell languages sounds like a true hell
05:16.55wpwrak(parse shell scripts) define a meta-syntax to goes along with it, if you want.
05:17.03wpwrakit's been done before :)
05:17.10MonkeyofDoomyou could surely do some ad-hoc analysis, but it wouldn't be a guarantee of anything
05:17.27wpwraki think you're just trolling ;-)
05:17.30MonkeyofDoomI'm not
05:17.58MonkeyofDoomshell scripts are a good way to automate sequences of tasks with a little structure
05:18.13MonkeyofDoombut a good init system actually does perform some nontrivial computations
05:18.40wpwrakhence my suggestion to add a meta-syntax for that
05:18.44MonkeyofDoomand has some resource management responsibilities where it's good to have some checked assurances that you don't mess up
05:18.55MonkeyofDoommeta-syntax would help
05:19.15MonkeyofDoomI just don't understand the motivation to keep shell scripts so tightly integrated into the system
05:19.27MonkeyofDoomyou can always write them and call them like programs as is done in the systemd model
05:19.52MonkeyofDoombut I don't see the advantage of using them for the logic of the init system
05:19.54OksanaLook at this init, from Solaris: https://en.wikipedia.org/wiki/Service_Management_Facility
05:20.21wpwrakOksana: http://wiki.gentoo.org/wiki/Comparison_of_init_systems
05:20.47MonkeyofDoomOksana: sounds fairly reasonable
05:21.07MonkeyofDoomif I were to implement something with those properties I would *not* go off and start writing shell scripts :P
05:21.54OksanaGreat! No need to lock yourself down to one thing. Be it systemd or sysVinit. Look for alternatives, always :P
05:22.05wpwraki guess i'd use perl for the tricky bits :)
05:23.27wpwrakanyway, the main concern about systemd is not the choice of language for the core functionality but that it does a gazillion other things that have nothing to do with being a good "init"
05:24.09MonkeyofDoomwpwrak: I agree systemd does seem to grow tentacles
05:24.33MonkeyofDoomjust I don't think "the old 1970s way is perfect" is right either
05:24.45wpwrakand tolkien taught us what to do with items that aim to rule over everything ... :)
05:25.04MonkeyofDoomwrite books about them!
05:25.11wpwrakhehe :)
05:25.26wpwrakdevuan, paperback edition. all the punch cards :)
06:34.55*** join/#neo900 SylvieLorxu (~SylvieLor@dhcp-077-251-165-191.chello.nl)
07:15.18*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
09:19.24*** join/#neo900 arcean (~arcean@aacr27.neoplus.adsl.tpnet.pl)
09:30.16*** join/#neo900 nicksydney_ (~quassel@43.230.dsl.syd.iprimus.net.au)
09:58.05*** join/#neo900 nicksydney (~quassel@43.230.dsl.syd.iprimus.net.au)
10:21.24*** join/#neo900 SylvieLorxu (~SylvieLor@dhcp-077-251-165-191.chello.nl)
10:31.59*** join/#neo900 mvaenskae (~mvaenskae@unaffiliated/mvaenskae)
11:36.00*** join/#neo900 phre4k (~phre4k@HSI-KBW-46-237-208-199.hsi.kabel-badenwuerttemberg.de)
12:28.38*** join/#neo900 ashneo76 (~ashneo76@c-71-194-247-250.hsd1.il.comcast.net)
12:41.27*** join/#neo900 phre4k (~phre4k@HSI-KBW-46-237-208-199.hsi.kabel-badenwuerttemberg.de)
12:44.18*** join/#neo900 che1 (~che@h231.tum.vpn.lrz.de)
13:19.42*** join/#neo900 illwieckz (~illwieckz@AToulon-256-1-159-41.w83-113.abo.wanadoo.fr)
13:30.46*** join/#neo900 quatrox (~quatrox@cm-84.211.174.137.getinternet.no)
16:00.02*** join/#neo900 SylvieLorxu (~SylvieLor@dhcp-077-251-165-191.chello.nl)
16:22.17*** join/#neo900 sparetire_ (~sparetire@unaffiliated/sparetire)
16:27.33*** join/#neo900 arcean (~arcean@aacr27.neoplus.adsl.tpnet.pl)
16:40.49*** join/#neo900 paulk-collins (~paulk@gagarine.paulk.fr)
18:03.03DocScrutinizer05devuan is about _my_ freedom to choose the possibly inferior init system, not getting forcefed a supposedly best systemd and if my system doesn't match the usecase I can go f* myself (quoting words to the effect of Poettering). It's not only system init, systemd comes with a truckload of dependencies and already hijacked stuff like network management and udev and FHS-conforming /usr/ volume
18:04.11DocScrutinizer05and I strongly disagree an init system shall "manage resources"
18:04.28SylvieLorxuDocScrutinizer05: That's literally the worst part about systemd: It actively attacks freedom of choice. Normally, you could just switch tools if one didn't work, but systemd is changing that to a "you're screwed" scenario
18:04.33DocScrutinizer05an init system shall start resource managers
18:04.54SylvieLorxuIs it the worst part? It's one of the many, I suppose
18:04.56DocScrutinizer05SylvieLorxu: exactly
18:05.17SylvieLorxuBut yeah, I'm excitedly waiting for Devuan, want to upgrade to that, instead of to the latest Debian
18:05.37SylvieLorxuMy customers deserve better than software that is collecting CVEs like trophies
18:25.02DocScrutinizer05couldn't have put it better
18:31.03bencohI'll just say "+1" as well :)
18:31.31DocScrutinizer05I'll try nevertheless to emphasize yet another aspect: there's nothing wrong in - even vast - refactoring of the way how Linux works, IF CLEARLY NEEDED. However I a) think the guys in systemd cabal are quite obviously not "old enough" to do a decent job as system architects, nor even as developers or project leads (http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01331.html http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01488.html),
18:31.33DocScrutinizer05nor b) have they shown there's actually a particular need to do such massive refacturing, and c) their plans for future of Linux (http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html) are explicitly not in line with what any sane tech savvy user would expect Linux to be
18:33.07DocScrutinizer05I don't want a Linux that tries to be a me-too Android or even windows
18:33.31DocScrutinizer05I don't want app shops
18:34.43DocScrutinizer05and I don't want sealed distros that follow a teke-it-or-leave-it approach and don't allow any configuration except when done by the distro maintainers
18:34.54DocScrutinizer05take*
18:35.26*** join/#neo900 vakkov (~vakkov@134.83.207.11)
18:37.23SylvieLorxuDocScrutinizer05: I think Poettering should just buy a Mac instead :x
18:37.43DocScrutinizer05I'm absolutely sure he already has one
18:38.00SylvieLorxuLike most of the GNOME devs, I guess...
18:54.45arossdotmewhy do the gnome devs like systemd?
18:55.11Humpelstilzchenarossdotme: when was the last time you used gnome?
18:55.17arossdotmepersonally I love gnome 3
18:55.23DocScrutinizer05honestly when you know the faintest detail about repositories and how Linux works in general, read http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html but get a good booze before, you'll need it
18:59.22DocScrutinizer05>>The toolbox approach of classic Linux distributions is fantastic for people who want to put together their individual system [... However]  you frequently do your work based on complete system images [...] The current Linux distributions are not particularly good at providing for this major use-case of Linux [...] is incompatible with what many system vendors want.<<
18:59.37*** join/#neo900 unknown_ (unknown@shell.nethack.be)
18:59.53DocScrutinizer05do *YOU* want a linux that's tailored to meet the needs of system vendors?
19:03.02DocScrutinizer05let me summarize: >>One of the major usecases of Linux is to allow system vendors to sell sealed non-configurable Linux based systems<<
19:03.53DocScrutinizer05IOW stuff like Tivo, Android, even iOS
19:03.53kerioDocScrutinizer05: btrfs subvolumes are so fucking awkward to deal with
19:03.55kerioit's not even funny
19:04.11keriohow one plans to make them the basis of the supreme packaging system is beyond me
19:06.43DocScrutinizer05exactly the reason why I think the systemd cabal has no savvy system architects, neither sufficient "pragmatism" that comes with experience
19:07.56DocScrutinizer05well, either that or they bent over to what the spin doctors way up in RedHat hierarchy ordered them to build
19:08.16*** join/#neo900 unknown_ (unknown@shell.nethack.be)
19:08.32bencoh19:37 < SylvieLorxu> DocScrutinizer05: I think Poettering should just buy a  Mac instead :x
19:08.52DocScrutinizer05then they actually did an excellent job, pretty much disguising what's the ultimate destiny of Linux RH flavor
19:09.10bencohThat's what h's been told for years :)
19:09.50SylvieLorxuDocScrutinizer05: BUT THEY NEED TO SUPPORT SO MANY USE CASES (except yours because fuck you I guess)
19:10.22SylvieLorxuBut yeah, Poettering is delusional
19:10.44*** join/#neo900 vakkov (~vakkov@s3n104.brunel.ac.uk)
19:10.49SylvieLorxuMaybe, if Linux was so useless, it wouldn't have become the most-used system ever?
19:11.15bencohmost-used ?
19:11.44SylvieLorxubencoh: Smartphones, tablets, servers, supercomputers, etc., etc.
19:11.51bencohI guess you need to be more specific about the market
19:12.04SylvieLorxuIT altogether, the complete image
19:12.19bencohphones/tablets are androstuff ;)
19:12.22SylvieLorxuOn desktop it's obviously not the most-used
19:12.24SylvieLorxuAndroid is Linux
19:12.37bencohyeah sure, but not exactly ;)
19:13.29kerioto be fair
19:13.39kerioi installed openbsd on a VM recently
19:13.51kerioi literally just pushed "enter" a bunch of times and answered like two questions
19:14.08kerioand it worked
19:15.18*** join/#neo900 unknown_ (unknown@shell.nethack.be)
19:16.09DocScrutinizer05that's not a criterion
19:16.33DocScrutinizer05every decent Linux distro installer nowadays works this way
19:17.12DocScrutinizer05the question is: does it allow easy config changes *after* (or during) you installed the default image
19:17.39*** join/#neo900 Kabouik (~quassel@144.193.95.79.rev.sfr.net)
19:17.46DocScrutinizer05are you free to choose your desktop, your init system, your filesystem etc
19:18.16sixwheeledbeastThe Linux kernel is widely used yes.
19:18.40DocScrutinizer05how many tweaks/patches do standard linux package sources need to compile and work on such system?
19:20.24DocScrutinizer05I mean, installing Android to a SG is a matter of ... prolly not even pushing a button, you just insert a CD into your windows PC and hook up the phone via USB, right?
19:20.48DocScrutinizer05but does Android allow you to do any of the changes mentioned above? No
19:22.56*** join/#neo900 Kabouik (~quassel@144.193.95.79.rev.sfr.net)
19:25.05DocScrutinizer05you need cyanogen mod since not even experienced linux admins have a way to understand how to "root" an android system
19:26.58DocScrutinizer05is this what you want to get served by Poettering and & co to you for your desktop PC, and - when you're lucky - for your server. And no way to port the system to e.g. a Neo900 since it would take dozens of man-years to port the stuff?
19:27.49DocScrutinizer05and since it takes lots of work, devuan already started *doing* that work
19:29.08DocScrutinizer05...right now, when it's still feasible to implement and support an alternative to such "closed" system that doesn't give you a choise
19:30.44DocScrutinizer05NB you could use systemd even on devuan. It's just that devuan adds freedom of choice to the picture. On other systemd infested distros you MUST use systemd
19:31.49HumpelstilzchenMy debian still doesn't have systemd...
19:32.11sixwheeledbeastI can't see why it isn't left for you to choose your init system on debian
19:32.43Humpelstilzchensixwheeledbeast: you still can choose it on debian
19:33.40sixwheeledbeastHumpelstilzchen: in the future, to avoid the whole devuan situation
19:34.06kerioDocScrutinizer05: daemons started at boot time are just lines appended to /etc/rc.conf.local :3
19:34.21kerioer, /etc/rc.local
19:34.47Humpelstilzchensixwheeledbeast: you probably still can...my guess is only when e.g. using gnome or kde that systemd is required.
19:36.40kerioDocScrutinizer05: no srsly install openbsd in a VM
19:36.42kerioit's super fun
19:39.17DocScrutinizer05Humpelstilzchen: you're mistaken on that. Systemd comes with such an awesome trucjload of dependencies, you will have a 70% system when you rip out systemd. You need to fix *a lot* of stuff to make your system work without systemd, and that's exactly what devuan does
19:43.27DocScrutinizer05just think automounter and udev
19:43.54DocScrutinizer05and there's quite a bit more than those, which systemd hijacked
19:43.58sixwheeledbeastYep that was what I thought too. before systemd turned into a huge systemmetaball you could have a "shim" to satisfy systemd dependences without using it as an init sys. Like Ubuntu does at the moment.
19:44.47DocScrutinizer05and systemd is only the beginning. See http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html
19:45.20*** join/#neo900 edwin1 (~edwin@2a02:2f09:41d5:a800:81fc:c77b:8b2a:527f)
19:45.47DocScrutinizer05when we don't start *now* to reject and oppose this occupation, in a year or two the leatest we won't be able to do so anymore
19:45.59edwin1DocScrutinizer05: thanks for the LCD PWM freq measurement, found it in the logs after I left
19:46.11DocScrutinizer05:-) YW
19:46.22HumpelstilzchenDocScrutinizer05: which doesn't make it required
19:46.26DocScrutinizer05did I share the scope screenshot?
19:46.35edwin1yep
19:46.51edwin1http://irclog.whitequark.org/neo900/2015-01-09#11438646;
19:47.03Humpelstilzchenif the day comes where something popular like apache or openssh depends on systemd I'm gonna grab some popcorn
19:47.20edwin1it probably indirectly does via libpam-systemd
19:47.28DocScrutinizer05sure, as little "required" as the engine for a car is. You're free to built a steam engine and power your car with that one
19:48.41DocScrutinizer05the question is: *can* you do that?
19:49.30DocScrutinizer05or isn't it rather the case that your options are limited to what's available and supported on the market?
19:50.33edwin1right now I can still get away without systemd as pid 1 with systemd-shim + cgmanager + systemd, but it still runs systemd-logind
19:50.39DocScrutinizer05and there are sound claims that "cars would be better off if 100 years ago the choice had been for steam engines instead of combustion engines"
19:51.24DocScrutinizer05edwin1: there's hope: devuan
19:51.50edwin1I know about it, will wait and see
19:52.50edwin1since you don't have to login to a desktop on a phone, hopefully logind or its equivalent won't be needed on neo900 :)
19:53.26Humpelstilzchenedwin1: hmm I still login on my desktop with a systemd process..
19:53.52edwin1Humpelstilzchen: yeah I have it too, systemd-logind
19:54.26Humpelstilzchenedwin1: whatever this is, I don't have it installed
19:58.35DocScrutinizer05edwin1: openfremantle will not have any systemd garbage. I'm pretty sure SHR also won't go systemd path of doom. Our factory test and board support system will be based on devuan
19:59.13edwin1nice
19:59.13*** join/#neo900 unknown__ (~unknown@shell.nethack.be)
20:01.07edwin1Debian is still responsive to bugreports about systemd breakage, if slowly: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747180 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766237 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764511
20:01.55DocScrutinizer05we can't use a system for factory test that considers complete system log corruption after inregular system shutdown a non-issue
20:02.10edwin1indeed, no journald pls
20:02.25DocScrutinizer05and we'll appreciate simplicity and ease of use of a system-v init
20:03.45DocScrutinizer05edwin1: ((Debian is still responsive to bugreports)) the problem is: they seem to have stopped listening to complaints of people who want another init system than systemd
20:05.28edwin1btw it doesn't mean that I wouldn't be open to a  better init system, as long as it is *better*  and *not*  systemd. I wouldn't mind runit as in http://www.voidlinux.eu/#features for example
20:06.25DocScrutinizer05as I said above: there's nothing immanently bad with improving the way linux works, as long as you keep freedom of choice
20:07.14edwin1yep
20:08.34sixwheeledbeastI agree with that, freedom is why many use Linux in the first place.
20:11.33edwin1hmm the block diagram for neo900 keeps turning up interesting pieces. Do I read it correctly that there will be dual SIM support? (multiplexed, not both on at same time)
20:13.41edwin1will it work like this? https://en.wikipedia.org/wiki/Dual_SIM#Standby
20:14.43DocScrutinizer05edwin1: correct
20:15.18DocScrutinizer05for the dual SIM. Alas the modem module doesn't support dual-standby
20:15.23DocScrutinizer05yet?
20:15.54DocScrutinizer05we implement the hardware in a way so a modem firmware update *could* enable such dual-standby though
20:16.40DocScrutinizer05we can't force Gemalto to do such augmented firmware, but of course we will push and hope :-)
20:17.37DocScrutinizer05the modem in fact has GPIO pins that could get used to control the mux
20:18.52*** join/#neo900 Pali_ (~pali@Maemo/community/contributor/Pali)
20:19.33edwin1the passive mode/switching from software would still work without that update?
20:19.33DocScrutinizer05I don't know if the modem internally has all the needed resources (ability to backup DSP and other registers to RAM, enough RAM to run two concurrent radio stack processes), but the application interface (~= hw pinout) has all it needs to support DSDS
20:19.56DocScrutinizer05sure, you can switch SIMs under control of APE
20:20.46DocScrutinizer05for now my basically logiing out modem from one network, switching SIM and then logging in modem again, to the new network under new IMSI
20:21.07edwin1yeah probably too battery hungry to do that automatically
20:21.10DocScrutinizer05for now by* logging* out
20:21.12edwin1but better than manually swapping
20:22.06DocScrutinizer05that's not an issue of energy needed. It's the problem that modem loses the temporary ID it gets assigned when logging in to a network
20:22.38DocScrutinizer05you cannot 'boot' the modem into a still active registration and resume it
20:22.59edwin1ah so probably quite time consuming as well to search&register
20:23.26DocScrutinizer05the trick with DSDS is the time sharing where modem does _not_ drop the login to either of both networks
20:24.07DocScrutinizer05it just takes maybe a second or two longer until the modem answers whatever inbound request from network
20:24.13*** join/#neo900 unknown_ (unknown@shell.nethack.be)
20:25.16DocScrutinizer05since the network - when it sends e.g. an INVITE (inbound call) in vain - just repeats the same request several times
20:26.55ds2sounds very battery friendly :D
20:26.55DocScrutinizer05when the modem forgets that it is #12345 currently and logs in again, asking for a new temporary ID that might them be #34567, any repeating requests to #12345 will fail eventually and never succeed
20:27.49DocScrutinizer05time multiplex is about resume operation, not start over of operation
20:29.38DocScrutinizer05lemme put it this way: modem is a state machine that is controlled by network (among other), and re-login resets the state of the state machine since it loses all internal data defining the state
20:31.05DocScrutinizer05(lamost all, serving cell is stored to persistent storage on SIM to speed up relogin time by reducing the effort to find the channel of a valid cell/station)
20:31.57*** join/#neo900 unknown_ (unknown@shell.nethack.be)
20:32.44DocScrutinizer05or, more colloquially, modem on logout left the party, and when it returns it needs to buy a new entrance ticket
20:33.58DocScrutinizer05no matter if the party host (network) noticed modem leaving the party or not (regular logout or brute force shutdown), in any case to enter a new ticket is needed
20:34.55DocScrutinizer05particularly since modem lost the old ticket when shutting down
20:47.12DocScrutinizer05while real DSDS is like joining two parties that happen in adjacent gardens and modem just jumps over the fence from one into the other every 2 seconds - until somebody talks to it at one of both parties so it stays there until the conversation finished, then resumes hopping over the fence back and forth
20:56.42edwin1got it
20:58.47edwin1the ambient light sensor ... does it just measure intensity, or RGB/XYZ color?
21:14.52quatroxDocScrutinizer05: after reading about systemd, I cannot believe anybody actually wants it.  I wonder how much money RedHat will loose if they go for systemd only
21:15.44*** join/#neo900 norly (~norly@enpas.org)
21:19.08*** join/#neo900 unknown_ (unknown@shell.nethack.be)
21:20.55arceanquatrox: isn't it already in RHEL7?
21:22.25kerioquatrox: it's already in RHEL, it's in debian sid
21:22.41kerioi think it's in arch
21:23.57quatroxisn't arch all about freedom of choice and control?
21:24.10kerioi think arch is about using the most recent software possible
21:24.21keriofreedom of choice and control is gentoo i guess
21:24.44quatroxGentoo is actually my favorite distro
21:29.08quatroxhmm... I guess I have to switch to Gentoo on all my computers.  The only pain is to optimize the kernel config for each of my (way too many) computers.
21:37.06kerioor you could just switch to openbsd
21:37.28DocScrutinizer05edwin1: the ALS probes two bands: IR and <visble+IR>
21:37.40kerioliterally banned from hacking competitions because it's too secure
21:38.07kerioOnly two remote holes in the default install, in a heck of a long time!
21:44.04*** join/#neo900 unknown_ (unknown@shell.nethack.be)
21:52.16quatroxkerio: I have thought about it.  Maybe I will install openbsd on my laptop and keep GNU/Linux on the rest.
21:54.46Wizzupkerio: that slogan is silly
21:54.55WizzupConsidering they have weird definitions of 'remote holes'
21:59.43kerio?
22:00.13WizzupTranslated: they've had much more problems but somehow choose not to count them as remote holes
22:06.22keriobecause... they're not?
22:06.27kerioi dunno, give me an example
22:10.05quatroxthat is the same with Linux
22:11.35quatroxBecause every bug can potentially be a security bug, it is hard to group the bugs into security bug vs non-security bug
22:13.00quatroxs/every bug can/most bus may/
22:19.53*** join/#neo900 vakkov (~vakkov@s3n104.brunel.ac.uk)
22:32.41*** join/#neo900 nox- (noident@freebsd/developer/nox)
23:23.18*** join/#neo900 infobot (ibot@rikers.org)
23:23.18*** topic/#neo900 is http://neo900.org | conversations are logged to http://infobot.rikers.org/%23neo900/ and http://irclog.whitequark.org/neo900
23:23.18*** mode/#neo900 [+v infobot] by ChanServ
23:23.26DocScrutinizer05~wb
23:23.26infobotIt's great to be back!
23:24.28DocScrutinizer05now only dos1 needs to authenticate ;)
23:27.04*** join/#neo900 lexik|m (uid55801@gateway/web/irccloud.com/x-jwzapervejyphxmj)
23:27.21bencohlooks like he chose to leave instead :>
23:27.28*** join/#neo900 bencoh (~bencoh@unaffiliated/bencoh/x-184637)
23:27.31*** join/#neo900 dos1 (~dos1@unaffiliated/dos1)
23:27.31*** mode/#neo900 [+v dos1] by ChanServ
23:28.41*** join/#neo900 ecloud (quassel@nat/digia/x-mhfsylydepgpbnox)
23:28.55*** join/#neo900 useretail (useretail_@gateway/shell/elitebnc/x-opoywksgqoskhzsw)
23:29.07*** join/#neo900 norly (~norly@enpas.org)
23:30.04dos1seems like znc got into some weird state, so I just restarted it :P
23:31.15*** join/#neo900 PeperPots___ (sid1218@gateway/web/irccloud.com/x-glozkejttlsjdbtt)
23:31.19dos1hmm, or maybe that was freenode actually
23:33.27quatroxdos1: it looked like freenode did another rehub and then disconnecting everybody
23:35.04dos1yeah, and NickServ is still not responding
23:35.23quatroxohh.. I didn't even notice that
23:36.11Oksana((NickServ is still not responding)) ? I identified myself just recently, after freenode re-connect
23:36.21bencohsame here (just identified)
23:39.16quatroxUsually my client do the identification automatically, but this time it failed 3 times and gave up.  When I tried now (manually), it worked
23:39.17*** join/#neo900 vakkov (~vakkov@134.83.207.11)
23:43.24OksanaGood morning!
23:43.47quatroxGood morning, Oksana
23:58.37DocScrutinizer05[2015-01-16 Fri 00:33:27] <quatrox> dos1: it looked like freenode did another rehub and then disconnecting everybody
23:58.38DocScrutinizer05[2015-01-16 Fri 00:33:58] [Notice] -tomaw- [Global Notice] Hi all. Yes, it seems we erred with a firewall rule there. Everything should be back to normal now.
23:59.33quatroxI saw that one minute after I sent that message

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.