IRC log for #devuan on 20160508

07:37.22*** join/#devuan infobot (ibot@rikers.org)
07:37.22*** topic/#devuan is Devuan discussion channel - Beta is out https://www.devuan.org - forum on https://talk.devuan.org - irc logs https://botbot.me/freenode/devuan/
07:37.52DocScrutinizer05btw works again
07:38.10DocScrutinizer05nevertheless there's
07:38.14DocScrutinizer05!mirrors
07:38.14infobotsomebody said mirrors was https://devuan.voyanet.org/  http://devuan.lucylaika.ovh  http://devuan.ksx4system.net/  ftp, http://tux.rainside.sk/devuan/  http://devuan.selea.se/  http & ftp://ftp.nluug.nl/pub/os/Linux/distr/devuan/  http://devuan.c3l.lu/  http://neo900-devuanfiles.dev-one.org (eventually, until then:)  http://devuan-temporary-mirror.almesberger.net
07:42.01DocScrutinizer05re "works again" see http://devuan-temporary-mirror.almesberger.net/log.txt
07:50.59DocScrutinizer05and moinmoin devuan
08:10.28*** join/#devuan radsy (~irc@unaffiliated/radsy)
08:15.01*** join/#devuan SylvieLorxu (~TheLastPr@dhcp-077-251-165-191.chello.nl)
08:23.32*** join/#devuan j3nkins (~jenkins@e2.85.7a9f.ip4.static.sl-reverse.com)
08:39.00*** join/#devuan Pali (~pali@Maemo/community/contributor/Pali)
09:07.11*** join/#devuan midasvdr__ (~quassel@p3E9EB1B6.dip0.t-ipconnect.de)
09:14.05*** join/#devuan ruenoak (~chatzilla@122-59-243-80.jetstream.xtra.co.nz)
09:35.49Defianthmm wine fails in devuan because of missing /etc/debian_version is there a devuan bugtracker?
09:42.21debdogit's on https://git.devuan.org
09:49.16Defiantthx
09:52.03*** join/#devuan antofox (4e0c2a4c@gateway/web/freenode/ip.78.12.42.76)
09:53.08Defianthmm now I'm on https://git.devuan.org/groups/devuan-packages/issues registered and click on "new issue" but all I get is a search box instead of a formular for a new ticket?
10:00.13nextimeDefiant: new issues has to be done on projects, not on groups
10:00.22nextimeif isn't anything specific to any specific package
10:00.44nextimehttps://git.devuan.org/devuan/devuan-project open an issue here
10:01.08Defiantk thx
10:01.22nextimefor your issue
10:01.33nextimetry to symlink devuan_version to debian_version
10:01.39Defiantalready done
10:01.46nextimeit works?
10:01.48Defiantsure
10:02.35nextimegreat, then it's better to synlink it by default at least until we will have forked all packages :)
10:14.29*** join/#devuan fsmithred (~fsmithred@68-184-46-18.dhcp.oxfr.ma.charter.com)
10:29.22Centurion_Dannextime: it should be done in base-files package.  I can attend to it tomorrow if you don't have time.
10:34.48jaromilits wise to put this symlink or even a hard-link
10:35.05jaromilsome programs fail recognizing is an apt based distro indeed.
10:42.36*** join/#devuan Markus_KMi (uid95611@gateway/web/irccloud.com/x-jdgcxvwnlvpcsbqj)
10:51.34DocScrutinizer05:-)
10:52.51DocScrutinizer05([sym]link) would wine also test for a certain content of /etc/debian_version?
10:53.35*** join/#devuan argwings (~tod@71-211-118-75.phnx.qwest.net)
10:54.24Defiantits just print its output, e.g. Executing wine (wineserver32) 1.8.1 on Debian ascii/ceres (amd64).
10:54.35DocScrutinizer05meh :-)
10:55.00DocScrutinizer05IroN900:~# cat /etc/debian_version
10:55.02DocScrutinizer05testing/unstable
10:55.15DocScrutinizer05(maemo)
10:57.08DocScrutinizer05prolly wine shouldn't fail when the file is missing
10:58.55DocScrutinizer05ln -s /dev/urandom /etc/debian_version   ;-)
11:00.14Defiantread will block
11:00.15DocScrutinizer05for less specacular effects make that /dev/null
11:00.38Defiant/dev/null works
11:00.53DocScrutinizer05Defiant: read will never return, that's true. Unless read buffer full
11:01.13DocScrutinizer05aiui
11:01.29DocScrutinizer05was just kidding anyway, SCNR
11:03.21DocScrutinizer05(buffer full) or overrun and segfault ;-P
11:05.42DocScrutinizer05idly tries to recall how much of any "standard" been defined with /etc/*version*|*release* anyway
11:06.39DocScrutinizer05when you already need to know the distro you're running on, to make a successful call to the files describing the distro, it somehwat defeats the purpose, no?
11:07.39Defiantcheck /etc/os-release
11:08.03DocScrutinizer05I ran into this issue when trying to make sure in a generic script that there's a certain lib (libusb0.1.4_32) available on arbitrary linux systems
11:08.57DocScrutinizer05IroN900:~# cat /etc/os-release
11:08.59DocScrutinizer05cat: /etc/os-release: No such file or directory
11:09.39DocScrutinizer05however:
11:09.42DocScrutinizer05jr@saturn:~> cat /etc/os-release
11:09.43DocScrutinizer05NAME=openSUSE
11:09.45DocScrutinizer05VERSION="13.1 (Bottle)"
11:10.58DocScrutinizer05channel CTCP enabled?
11:14.50DocScrutinizer05/mode #devuan +C
11:16.46nextimeCenturion_Dan: : today i can't, but tonight i will
11:17.01*** join/#devuan Human_G33k (~Human_G33@212.83.185.179)
11:20.09*** join/#devuan argwings (~user@71-211-118-75.phnx.qwest.net)
11:24.28*** join/#devuan berndj (~berndj@azna.co.za)
11:32.15DocScrutinizer05!amprolla is <reply>nextime gave an excellent explanation how amprolla works, at https://botbot.me/freenode/devuan/2016-05-07/?msg=65646427&page=4
11:32.15infobotokay, DocScrutinizer05
11:35.11jaromilthis should go also in the docs on talk
11:35.33jaromilalso last day when enyc asked i had no time to explain (weekends!) and i was sorry
11:36.13jaromilplease do use talk.devuan.org that is the collectively edited source of info, with tags on topics, also linked from webpage
11:40.08*** join/#devuan cocoadaemon (~foo@x53.octopuce.fr)
11:47.56*** join/#devuan mns` (~mns@177.13.50.194)
12:13.57DocScrutinizer05pukes on reading http://0pointer.de/blog/projects/os-release.html
12:15.00DocScrutinizer05>>It's our hope that by dropping support for non-compliant distributions we gently put some pressure on the remaining hold-outs to adopt this scheme as well.<< it's this mindset I really *hate*
12:17.13nextimewho cares if systemd doesn't support us? WE don't support systemd :P
12:17.37fsmithredsilly me - I thought /etc/issue was the standard place to put that info.
12:18.26fsmithredI think those guys like to make up their own names for stuff.
12:19.11nextimefsmithred:  let's them make lindows, we are working to continue the UNIX-Like environment for linux
12:19.15nextime:)
12:19.46nextimei don't really care about them anymore.
12:19.47fsmithredyeah, I like that idea.
12:20.41nextimewe and the "systemd crew" have oposite ideas
12:21.24nextimethey are trying to delete diversity and to make an omogeneous linux environament for all, thinking that unification is good, posix and unix compatibility isn't
12:21.54nextimewe, as opposite, think that diversity is a value, linux success is what it is thanks to it, and posix and unix are the best environment
12:21.58fsmithredyes, that scares me.
12:22.07nextimei'm not scared
12:22.20nextimelinux and open source works this way
12:22.31nextimewhan someone doesn't agree with someone else
12:22.33nextimeforks appen
12:22.46j3nkinsthe only diversity they care about this days is the diversity of gender and skin color, which is irrelevant
12:22.51nextimeand anyone follow the way is the best in he's own view
12:22.58fsmithredlol
12:23.04nextimeas long as we have enough horses and people thinking like us
12:23.06nextimethere is no risks
12:23.17nextimeand the success of this  project and other non-systemd projects
12:23.24nextimeprove there is meat for all of us
12:24.40DocScrutinizer05:-)
12:24.53*** join/#devuan enyc (~enyc@muddle.enyc.org.uk)
12:24.54DocScrutinizer05saved my day
12:24.59nextimewill systemd/linux conquer the world? maybe, i don't care, 20 years ago we were 4 cats using linux, and today we drive the world
12:25.03nextimewill happen again.
12:25.36fsmithredneed to go get some food. bbl.
12:25.49fsmithred(all this talk of meat...)
12:26.13DocScrutinizer05hehe, same here
12:26.33nextimejust finished to eat
12:26.38nextime"ossibuchi alla milanese"
12:26.39nextime:D
12:27.53DocScrutinizer05>>Also, you are kinda working towards the further balkanization of the Linux landscape, but maybe that's your intention?<< err YES!!!
12:27.55nextimehttps://en.wikibooks.org/wiki/Cookbook:Ossobuco_Alla_Milanese
12:28.40DocScrutinizer05when the alternative is a Poettering kindom, then for sure
12:28.47j3nkinsI had some "parmigiana di melanzane"
12:30.12nextimej3nkins: well, the italian cousine is well respected in whole world also cause of huge variety of food. The same deserve to linux world. Systemd is like the mac donald's of linux :D
12:30.39j3nkinsgreat quote right there
12:31.26nextimeprobably @ShitDevuanSays will quote me for that
12:31.37nextimeand many peoplw will say i hate systemd.
12:31.38nextime:D
12:32.00nextime( but i don't care, haters gona hate )
12:33.23DocScrutinizer05hating systemd is not something you chose to do, it's something you can't help but have to do once you understand it completely
12:34.12nextimeDocScrutinizer05: i don't really hate systemd. What i hate is the philosophy it's trying to evangelize and the imposition to use it.
12:34.27DocScrutinizer05that's right
12:34.33nextimesystemd itself is just another piece of software i'm not interested to use. like many others.
12:34.41DocScrutinizer05it's hard to hate a set of bytes
12:35.08DocScrutinizer05it's the hype about it that I hate
12:35.34DocScrutinizer05also the trouble this hype causes for me
12:39.15nextimewell
12:39.48DocScrutinizer05I think we don't need to discuss this for us here, we prolly all ate at McD's eventually. And Devuan would even allow systemd when systemd wouldn't introduce claims of exclusiveness and mutual incompatibilities
12:40.48nextimewhen someone point me in the direction of "but all major distro now are using it!" "eat shit, millions of flies can't be wrong" :D
12:41.02DocScrutinizer05indeed
12:41.22DocScrutinizer05I think I'm quoting the latter one at least weekly
12:41.51nextimeyes, as i said many times, we are ready to include systemd if and when systemd will not try to hijack the base system and will respect diversity
12:42.31nextimeit isn't us blocking systemd, is systemd blocking us to adopt it :)
12:42.43DocScrutinizer05yep, well put
12:44.06nextimeplenty of new material for @ShitDevuanSays today
12:44.09nextime:)
12:44.26DocScrutinizer05hehe
12:47.28jaromili submitted a Devuan talk for this CfP btw http://www.olografix.org/call-for-papers-moca-2016/
12:47.47jaromilmostly because is a relaxed environment full of friendly hackers and because I'll be around there anyway
12:48.49jaromilI recommend submitting or coming over to anyone interested in visiting a beach town in Italy at end of august. its every 2 years, last time a dev from coreboot was with us too from .de
12:52.22*** join/#devuan nioanto (4e0c2a4c@gateway/web/freenode/ip.78.12.42.76)
13:02.43DocScrutinizer05jaromil: alas the page truncates text
13:03.31DocScrutinizer05http://wstaw.org/m/2016/05/08/plasma-desktopqo2219.png
13:05.27DocScrutinizer05ooh there's a scrillbar all the way down to the bottom ;-P
13:05.35DocScrutinizer05scrollbar even
13:05.53jaromili'm sure somebody knows but has no time to fix it :)
13:06.00jaromilbbl
13:06.14DocScrutinizer05as always ;-)
13:06.18DocScrutinizer05cya
13:26.51*** join/#devuan cocoadaemon (~foo@x53.octopuce.fr)
13:33.45*** join/#devuan firegarden (~dionysos@host188-163-dynamic.12-79-r.retail.telecomitalia.it)
13:38.32fsmithredjaromil, what beach town?
13:39.45Inocuousgreetings everyone
13:40.02fsmithredhi
13:41.09*** join/#devuan Drugo (~andrea@host33-205-dynamic.17-87-r.retail.telecomitalia.it)
13:43.38InocuousI forgot who I was chatting with about modifying notifications the other day. That turned out to be pretty straight forward editing. Though some of the things I would like to change appear to be hard coded.
13:43.56fsmithredme
13:44.02fsmithredand golinux
13:44.58fsmithredI broke down and looked at the ponies. Not as bad as I'd feared.
13:45.33Inocuousthat one theme shows up really big for me,
13:45.41fsmithredyes
13:46.16fsmithredthere seems to be a widespread belief that kids like bad art.
13:46.29Inocuoushaha, yeah.
13:49.39InocuousI asked someone too about updates, but I wasn't sure of the answer, where Devuan is still beta, are they no system updates being issued?
13:50.03fsmithredI get updates
13:50.03DocScrutinizer05random systemd bugreport: running a cronjob for user XY *creates* a stale symlink ~XY/.local/share/systemd/user
13:50.42InocuousI must not have something set right. I"ve never been prompted or notified
13:52.31*** join/#devuan penelopa (~penelopa@unstable.nl)
13:52.48*** part/#devuan penelopa (~penelopa@unstable.nl)
13:53.00fsmithredprompted? I think you have to ask.
13:53.21*** join/#devuan MobileKittuns (~KittenGNU@unaffiliated/kittengnu)
13:53.25fsmithredapt-get update, apt-get dist-upgrade is what I usually do.
13:53.29Inocuousok. The only other linux I've run was ubuntu and it had a tool that would run daily and advise
13:53.42fsmithredupdate-notifier
13:54.32fsmithredbut it requires libpam-systemd
13:55.22Inocuousoh, I see.
13:56.29InocuousI'll try that update and see what I get.
13:57.06fsmithredI like to do aptitude -s full-upgrade between update and dist-upgrade, because the output is easy to read.
13:57.30*** join/#devuan Ryushin (~Ryushin@65.114.195.184)
13:58.47fsmithredwrite a script that does the update and the simulated upgrade, put the results from the latter in a text file that gets dumped on your destop, and run it as a cron job.
14:01.35InocuousI've set up cron jobs on websites, but never locally.
14:02.48fsmithredthe update part needs to be run by root, but the simulated upgrade can be run by user.
14:04.20Inocuouswhich is the simulated upgrade?
14:05.27InocuousOh, I see, the -s
14:05.47DocScrutinizer05fsmithred: see my last post, prolly related. also http://paste.opensuse.org/48973407
14:09.19DocScrutinizer05systemd, fubar
14:09.23fsmithredDocScrutinizer05, I'm looking, but I don't understand.
14:09.31fsmithredwhere'd you get .local/share/systemd?
14:09.50DocScrutinizer05a crontab job makes systemd create ~/.local/share/systemd/user
14:10.32fsmithreduser instead of $USER?
14:10.39DocScrutinizer05no
14:10.53DocScrutinizer05nfc
14:10.58fsmithredlol
14:11.15DocScrutinizer05I see that stael symlink showing up again after cronjob, when I delete it
14:11.17fsmithredI'm gonna wait until the kinks are worked out before I use systemd
14:11.27fsmithredif I live long enought
14:11.35DocScrutinizer05you won't
14:12.04fsmithredyeah, still waiting for pulseaudio
14:12.16DocScrutinizer05*cough*
14:12.21fsmithredsorry
14:14.58fsmithredbrb
14:21.43*** join/#devuan cyteen_ (~cyteen@39.104.125.91.dyn.plus.net)
14:49.13*** join/#devuan furrywolf (~randyg@72-57-199-236.pools.spcsdns.net)
14:51.04*** join/#devuan SylvieLorxu (~TheLastPr@dhcp-077-251-165-191.chello.nl)
14:52.03*** join/#devuan golinux (~golinux@2605:6000:ebc6:d200:96de:80ff:febc:9ea8)
14:52.03*** join/#devuan golinux (~golinux@unaffiliated/golinux)
15:03.57*** join/#devuan wildlander (~wild@unaffiliated/wildlander)
15:10.59*** join/#devuan FrozenWes (~FrozenWes@unaffiliated/frozenwes)
15:18.13*** join/#devuan cocoadaemon_ (~foo@x53.octopuce.fr)
15:20.48golinuxJust reading the scrollback comments about wine.  I just dropped my old home directory from squeeze including .wine into Devuan and it's working perfectly.
15:21.26golinuxwine 1.6.2-20 is installed and I'm on 32 bit if that matters.
15:22.22golinuxDefiant: ^^^
15:23.12*** join/#devuan markm__ (~cyteen@244.37.208.46.dyn.plus.net)
15:28.30golinuxDocScrutinizer05: I have never eaten at McD!
15:29.00golinuxGrew up pon real food before McD existed
15:29.59*** join/#devuan penelopa (~penelopa@unstable.nl)
15:30.19*** part/#devuan penelopa (~penelopa@unstable.nl)
15:33.23DocScrutinizer05would you believe me when I say I anticipated that reply when I wrote that? ;-)
15:38.14fsmithredgolinux, you're not missing much
15:38.28DocScrutinizer05btw McD exists quite a while, prolly longer than you'd guess, however it's clearly not been that prevalent until maybe the 60s
15:38.38fsmithredI used to know a doctor who said that the golden arches represent all the kidneys they've destroyed.
15:44.11DocScrutinizer05guesses McD exists a tiny bit longer than golinux
15:44.40DocScrutinizer05maybe not as frenchise
15:44.41*** join/#devuan markm__ (~cyteen@98.253.113.87.dyn.plus.net)
15:46.18*** join/#devuan Inocuous (~Inocuous@144-141-135-64.dsl.sacoriver.net)
15:48.18*** join/#devuan egon0 (~quassel@2a01:1e8:e100:8035:990c:ea82:83ce:b289)
15:50.58golinuxDocScrutinizer05: More than a decade.  Almost two!
15:51.15golinuxMe before McD
15:52.08golinuxgoes to verify with startpage
15:52.12DocScrutinizer05hardly, that would mean you're almost 100 years old now
15:52.54DocScrutinizer05you're right though when you talk about the Mc domald's *Corporation*
15:53.07golinuxOur History. Since 1955, we've been proud to serve the world some of its favorite food.
15:53.26DocScrutinizer05which been founded as late as April 15, 1955
15:54.04DocScrutinizer05McD the name/restaurant opened at May 15, 1940
15:54.28golinuxLet's just say I had never heard of it until I was well formed.
15:54.42DocScrutinizer05we can easily agree on that :-)
15:54.56golinuxLet's move on . . . very OT
15:55.02DocScrutinizer05hehe indeed
15:55.19golinuxMy fault for 'biting' into it
15:55.32DocScrutinizer05no damage done
15:55.53fsmithredmoving right along...
15:56.23fsmithrednew version of refractainstaller is ready and in the testing folder at sourceforge (because I haven't actually tested it yet.)
15:56.40fsmithredit handles disabling autologin with slim.
15:57.32golinuxfsmithred: You have a msg
15:57.41fsmithredI'm not going to do anything with /etc/default/grub unless someone tells me to do it.
16:10.02Inocuousthis may sound like a stupid question, and it probably is, but what is the normal directory to use for cron scripts?
16:10.51fsmithredmake a cron job to run a script. You can put the script wherever you want.
16:11.43fsmithredmy last post didn't show
16:11.48fsmithredoh
16:11.59fsmithredit was /usr/local/bin is a good place to put scripts
16:12.06fsmithreddon't start a line with / here
16:12.11fsmithredduh
16:12.24Inocuoushaha, ok. thanks for both tips :)
16:12.36FrozenWesmost clients allow some form of escaping
16:12.50FrozenWes/I started this line by typing // for example
16:13.12Inocuousnice.
16:13.39muep_is there a downside to putting it just directly to one of the /etc/cron.{hourly,daily,weekly} directories if the schedules of those seem ok?
16:14.03muep_also assuming that the script is not terribly long so that it'd take too much space from /etc
16:15.13fsmithredI can't recall if stuff in /etc/cron.* gets automatically logged. If you, you'd need to add something to logrotate.
16:15.31fsmithred/if you/if yes/
16:15.39FrozenWescrontab and thos directories are not designed for the same use cases iirc, I'm sure there's a man page or website that details it
16:16.12fsmithredyeah, I think that's for services
16:16.33fsmithredjust do crontab -e and point it to your script however often you want.
16:16.46muep_I guess the logging thing is a bit distribution specific
16:29.51Inocuousthe fancy Devuan logo that is on the website, is that an installable font by any chance?
16:34.52DocScrutinizer05re the /etc/cron.{hourly,daily,weekly} I'd consider it poor style to have complete scripts in there
16:35.04*** join/#devuan Scartozzo (~flavio@2-233-3-55.ip215.fastwebnet.it)
16:35.56DocScrutinizer05otoh everybody seems to do it
16:36.49DocScrutinizer05Inocuous: http://paste.opensuse.org/56133295
16:36.50muep_wouldn't it be consistent with having complete scripts in /etc/init.d/ ?
16:37.20fsmithredDocScrutinizer05, talk to golinux about the desktop theme and logo
16:37.50DocScrutinizer05hmm, you have complete scripts in /etc/init.d/  but not in /etc/init.d/rc?.d/
16:37.51muep_I used to have just one-liners that'd then invoke a script from elsewhere, but I did not seem to be getting any benefit when compared to just having the script directly in /etc/cron.*
16:38.06muep_DocScrutinizer05: complete scripts in both
16:38.36DocScrutinizer05muep_: no, in rc?.d/ I at least got only symlinks
16:39.07muep_ah, indeed the scripts are actually in /etc/rc.d. but they are not under /usr outside the configuration tree
16:39.18DocScrutinizer05yes
16:39.40DocScrutinizer05anyway the scripts in /etc/cron.{hourly,daily,weekly} seem to be real files
16:39.55DocScrutinizer05I would use a symlink scheme like in init.d
16:40.06muep_having full scripts in /usr/local and referring to them from /etc seemed to just give me extra steps to follow when investigating a problem
16:40.41DocScrutinizer05is afk
16:42.42DocScrutinizer05http://paste.opensuse.org/32679006
16:44.49golinuxInocuous: No that is not an installable font.
16:45.08golinuxIt is a variant of Fira Sans
16:45.16DocScrutinizer05awesome: http://paste.opensuse.org/17439418
16:45.36Inocuousthanks golinux
16:45.50golinuxhellekin and worked it out together.  He turned letters upside down and on their side
16:45.53DocScrutinizer05anyway I feel like it been said that executables of any kind in /etc were generally a poor idea
16:46.32golinuxAnd then letter placement was adjusted etc.
16:47.03golinuxAnd then of course we integrated the swoosh
16:47.34golinuxIt took quite some time to get it right
16:47.57golinuxInocuous: ^^^
16:49.06golinuxHere's where we hammered it out: https://git.devuan.org/devuan/devuan-project/issues/20
16:49.54InocuousIt came out great golinux, very professional.
16:50.47golinuxThanks
16:51.16DocScrutinizer05So I for one would split the whole thing into a cronjob-specific "config file" in /etc/cron.{hourly,daily,weekly} which isn't meant to ever get called interactively or in a different environment, and this calling a commandline executable to do the real work that lives in /usr/local/bin
16:56.30Defiantgolinux: you probably migrated from debian, right?
16:57.12golinuxNo a fresh install
16:57.40Defiantgolinux: this is strange, so you do not have /etc/debian_version?
16:57.54fsmithredThe files under /etc/cron.d
16:57.54fsmithred<PROTECTED>
16:57.54fsmithred<PROTECTED>
16:57.54fsmithred<PROTECTED>
16:58.05golinuxStill have squeeze and wheezy running elsewhere
16:58.45golinuxDefiant: No grokking your question
16:59.06DocScrutinizer05err mhm:  http://paste.opensuse.org/67938961  never even heard of /root/bin/cron.daily.local
17:01.16golinuxDefiant: Ah I see I have /etc/devuan_version
17:01.34golinuxNot /etc/debian_version
17:02.14DocScrutinizer05fsmithred: no manpage for run-parts on my system
17:02.17Defiantgolinux: and what wine package did you install?
17:02.26*** join/#devuan firegarden (~dionysos@host58-124-dynamic.117-80-r.retail.telecomitalia.it)
17:02.53fsmithredDocScrutinizer05, what are you running?
17:02.58DocScrutinizer05suse
17:03.01fsmithredoh
17:03.05DocScrutinizer05:-D
17:03.09fsmithredbeen a decade since I used suse
17:03.46golinuxDefiant: wine 1.6.2-20
17:03.56golinuxI'm on 32bit
17:04.09DocScrutinizer05but yeah, stuff like cron.daily hardly is posix or any standard at all, eh?
17:04.15Defiantgolinux: hmm is that jessie?
17:04.25fsmithredI don't know
17:04.41fsmithrednever messed with it until I was using debian
17:04.46DocScrutinizer05prolly highly distro specific
17:04.55golinuxDevuan jessie
17:04.56fsmithredyeah, that wouldn't surprise me
17:05.23Defiantgolinux: I'm on testing, might be the difference
17:05.27golinuxBut I upgraded from alpha2
17:05.50golinuxTesting could be the diff
17:05.56*** join/#devuan j3nkins (~jenkins@d7.85.7a9f.ip4.static.sl-reverse.com)
17:06.05golinuxI always run stable
17:06.44golinuxis not very adventurous
17:07.35furrywolfnoticed!
17:10.24*** join/#devuan cyteen (~cyteen@31.185.164.105)
17:22.25fsmithredDocScrutinizer05, did you find a man page for run-parts?
17:25.37DocScrutinizer05I didn't even find a run-parts binary on my system ;-)
17:26.47DocScrutinizer05>>runcon     rundig     rungs      runidn     runlevel   runscript  runuser << is about it with run*
17:28.37DocScrutinizer05I however *guess* runparts is a oneliner script like "for script in $1/*; do sh $script; done"
17:47.41DocScrutinizer05found manpage and binary on maemo
17:51.39DocScrutinizer05actually a symlink to messybox
17:56.49DocScrutinizer05I'm absolutely sure a few years ago this been a script on suse systems, iirc in /etc/init.d/. Of course now nuked for systemd
17:57.13enycrandom idea,  --   I've wondered, what it would take to  build  devuan stable (or later ascii) i386  with   e.g. 486 compatible gcc   (and kernel obviously but that bits' easy),  producing version compatible with ''legacy'' machines =)
17:58.26DusXMTI thought that was the default? (it is at least on debian, from what I recall)
17:58.59enycDusXMT: no, hasn't been a while
17:59.07enycDusXMT: and is chaniging again for stretch
17:59.36enycDusXMT: stretch will strictly require ''686''  (but not yet require SSE / pentium-III etc)
17:59.49Defiantenyc: debian just tropped 586
17:59.55enycDefiant: exactly
18:00.11DusXMTpets his pentium3 based machine :)
18:00.14golinuxDusXMT: https://lists.dyne.org/lurker/message/20160505.211556.4d82359c.en.html
18:01.00enycthough
18:01.27enycI wonder, how devuan's changes ,  no systemd,  different udev,  etc. --  translate into compatibility with 'older' (even unsupported) linux kernels
18:01.31DusXMTThanks for enlightening me
18:02.13enyccould you optionally run devuan in static /dev nodes  without udev?  i wonder.. .  i know this isn't what the project was aimed at, but makes me wonder
18:04.09enycseemingly libc6 is currently wired to 'insist' on 2.6.32 but can e.g. be told to 'accept 2.6.28 anyway' ... interesting =)
18:05.05DocScrutinizer05static /dev should just work aiui
18:05.44muep_I think it would normally require a rebuild with headers of an older kernel to make it consider it safe to run itself against an older kernel
18:07.20DocScrutinizer05has a P-II machine
18:07.41DocScrutinizer05with 128some MB RAM
18:08.27DocScrutinizer05CF-27
18:10.55enycDocScrutinizer05: the P-II will work in stretch current plan, but maybe not after that fi some level of SSE is assumed
18:11.16enycmuep_: rebuild with headers?  of libc6 ?? or what?
18:11.26DusXMTenyc: kernel headers
18:11.35enycmuep_: and iptables/ip6tables that messed around in kernel momory =)
18:11.44enycDusXMT: yes, but rebuild **what** against the older kernel headers
18:11.56DusXMTlibc6, of course
18:12.02muep_enyc: glibc with kernel headers
18:13.02enycDocScrutinizer05: i have some dual-PIII with 1gb ECC ram ... venerable 440BX ...  seems so stable and robust !!!   seem do hav avoided capacitor plague too!
18:13.08DusXMT(it's interesting that we still call it libc6, to have a compatible name with the "linux libc" from back in the day)
18:15.39DusXMThas one of those small, compacted computers, 900MHz single P-III with 512MB of ram, and I've been putting it through compiling hell (gentoo, guixsd, and then manual compiling of some things in Devuan) and it's withstood it like a champ
18:16.08DusXMTs/and then manual/and now manual/
18:16.10muep_The oldest ones I have are some pentium-m ones
18:16.22muep_also used for compiling source-based distros
18:16.56DusXMTWhy do we enjoy torturing the poor things? :)
18:18.09enycso anyway...
18:18.46enycany idea how possible it would be to later compile devuan for 486, instead of 686 or 686+SSE  ,  at least a 'stable' release then a buildd  run on other packages ?
18:19.25enyc'what would it take' ?
18:20.38muep_https://wiki.debian.org/DebianBootstrap
18:21.03minnesotagsDocScrutinizer05; I'm running devuan on my CF-30 centrino2 vpro, formerly a Vista machine. :-D
18:21.51enycmuep_: oooooooooooooo
18:21.52minnesotagsStill having problems with both suspending, sleeping, and with the stupid external speaker. My understanding is the speaker is a kernel bug.
18:22.49muep_enyc: for i486, you might get away without a full bootstrap by just incrementally rebuilding packages with flags that avoid instructions that an i486 CPU would not run
18:22.50enycmuep_: thatkyou for pointer... though I'm currently too braintired to fallow  all of it, iwll rethink another day =)  core of system could be cross-built ... by looks of thing ...
18:23.25enycmuep_: yes, as ABI change in calling environment etc not needed
18:23.42muep_but there is some effort in debian to track how it can be bootstrapped, in order to be able to support new architectures as they show up
18:24.03enycmuep_: nods, as that article says
18:33.55DusXMThad to build a bootstrap rust compiler in a virtual machine so he could use it on his pentium 3 machine (it's a self-hosting compiler), so Debian's not the only one slowly dropping support for these things
18:35.19DusXMTWhich is kind of interesting, as the 32-bit x86 don't get all that much more powerful. Okay, there's the pentium 4 and some flavors of the Celeron, but still
18:36.02*** join/#devuan Levure (~quassel@151.32-247-81.adsl-dyn.isp.belgacom.be)
18:36.12enycDusXMT: seems to me  theres' a potential ''market'' for devuan-for-486-compatible or-so  etc   seems like ought to be  do-able, question is how much  on going build daemon  functionality to keep archive built would be needed =)
18:37.13enycwhat is the development state of devuan ascii  compared to  stretch  at present ??
18:38.56DocScrutinizer05doesn't grok where's the trouble to build for 486 (even 386) target. Shouldn't the compiler still know how to do it, even on a i7 platform?
18:39.16enycDocScrutinizer05: probably should, though maybe less tested than it used to
18:39.25DocScrutinizer05sure
18:39.32enycDocScrutinizer05: im not familiar with building-from-scratch, however
18:40.00enycDocScrutinizer05: also, there are certain packages (e.g. libssl) that build multiple versions with different optimizations  and linker or so selects 'best usable' version at runtime i think
18:40.04DusXMTshould probably get a 486 computer for testing one day... though I think I'd need a lot of swap space with such machines
18:40.39enycDusXMT: typically 486s wouldn't l2-cache more than about 32mb ram  i believe
18:41.12muep_if the compiler knows how i386 code is generated, it does not matter if it is being run on an i7
18:41.16DocScrutinizer05yeah packages with optimizations that use the advanced hw are a mess to port to old CPUs
18:41.57enycDusXMT: make me wonder now, i have a tulup-computers 486 server board somewhere
18:42.17muep_but I guess the i486 target is getting less and less real-world use so it might have bugs that few people know about
18:42.25enycexactly
18:43.25enyci (thought) 386dx original and 486DX were little different, except  386s's always needed external math, and 486sx existed without math too....
18:45.09enyclinux (used) to have fpu sotware-emulation option but  i wouldn't be too bothered by this
18:45.49muep_it would be better to have the compiler do the software floating point stuff
18:49.30enyci'm intrigued to see the interest here =)
18:50.07enycmain 'practical stumbling block' i'd see, is  kernel versions  and minimum-amounts-of-ram  compatibility
18:53.40DusXMTSpeaking of these machines: gcc-compiled LLVM/Clang compiles LLVM/Clang in 20 hours on my old testing comuter, clang-compiled LLVM/Clang compiles LLVM/Clang in 14 hours... Looks like LLVM/Clang makes better-performing code on the Pentium 3 than gcc =3  (or the LLVM/Clang is written in a way to perform the best when compiled by itself)
18:54.31DusXMT(version 3.8.0, on Devuan)
18:54.35enycrecalls stories of compilers optimizing for performing well in tests =)
18:54.56DocScrutinizer05muep_: s/bugs/regressions/ ?
18:55.27muep_regressions are bugs. but there might also be bugs that concern only new functionality in the compiler
18:55.33DusXMTYeah, I think the first objective test will be to see if the web browser will perform noticably better when compiled by this clang
18:58.25DocScrutinizer05muep_: aah yep, new functionality that never been tested with old 486 code
18:59.49DocScrutinizer05there might be functions that are not even supported in 486
19:00.16DocScrutinizer05since nobody ever bothered to write the "emu code" for this
19:02.51muep_at some point, fedora was one of few distros targeting i586 as the minimum. then they decided to bump the minimum requirement to i686 and "obscure i586-specific bugs" was cited as one of the reasons to prefer i686
19:06.46*** join/#devuan cocoadaemon (~foo@2a01:e35:8a99:e90:9805:5747:3698:2c42)
19:08.33*** join/#devuan TwistedFate (~TwistedFa@unaffiliated/twistedfate)
19:17.19*** join/#devuan asbesto (~asbesto@88-149-241-188.v4.ngi.it)
19:19.46*** join/#devuan Markus_KMi (uid95611@gateway/web/irccloud.com/x-pzyuimqecxwllnos)
19:27.22*** join/#devuan penelopa (~penelopa@unstable.nl)
19:27.44*** part/#devuan penelopa (~penelopa@unstable.nl)
19:28.18asbestoYEH
19:28.26asbestofinally installing devuan on a laptop here :D
19:28.34asbestoMSI U100
19:48.00parazydasbesto: what's the screen resolution?
19:49.11Centurion_DanI don't understand why debian continues naming it's x86 arch i386 when it is no longer compatible with the i386.  With regards to Devuan, if their is strong interest - and sponsorship to cover the work we could indeed compile for i486 and i586.  However to do so we'd need import the complete source archive into gitlab, and currently that is not possible with gitlab.
19:49.35parazydsame reason why they name 64bit amd64
19:49.47parazydnnot only amd makes 64bit cpus >.<
19:51.24muep_it's kind of expensive to change the names
19:52.05Centurion_Danamd64 is kept as a recognition of the company that dev'd the 64bit instruction set.  Using x86-64 would imply that the architecture is a product of intel which is not the case.
19:53.14muep_I think x86-64 would be a quite vendor neutral name
19:54.01muep_but also here, changing it from amd64 to x86-64 or whatever would make quite a large amount of unnecessary work for various downstreams and users
19:54.23parazyduname -m also doesn't spit out amd64
19:56.41DocScrutinizer05I can say that amd64 moniker puzzled me quite a lot, tricking me into choosing i386 instead
19:56.56*** join/#devuan cyteen (~cyteen@31.185.164.105)
20:00.50muep_nowadays the debian web page has an item named like "download debian x.y - (32/64-bit PC network installer)"
20:01.25DocScrutinizer05now maybe I'm the least up-to-date linux user when it comes to such naming stuff, but I'm quite sure people that have no idea about linux will have a hard time picking the right arch when trying to make their way through devuan website
20:02.09muep_the download page can just avoid using the internal architecture names
20:02.21DocScrutinizer05indeed
20:04.04asbestoI don't remember parazyd
20:04.18asbestoIt was my laptop some years ago until I had my thinkpad X201
20:05.27parazydha! x201 also with me
20:05.38parazydi was wondering because i wanted to compare the two of them
20:05.49parazydthe 10" screen seems interesting
20:23.53*** join/#devuan Guest4314 (~Guest4317@83.220.236.225)
20:24.12Guest4314Hello World!
20:26.22Inocuoushello Guest4314
20:27.01InocuousI saw a headline earlier how Microsoft was happy about systemd, which makes me all the more anti-systemd, and anti-microsoft.
20:27.54InocuousMicrosoft drove really hard for windows 10 upgrades, that tells me it's rife with privacy invasion software.
20:28.35Centurion_Dansuspects a lot of blackhats are also very happy about systemd - lots of unaudited code...
20:31.56InocuousI don't know the exactly definistion of a black hat but I think it's bad. And I'm sure they are involved. Why not, it's subversion of the core of the operating system, that's what they want.
20:32.42zdzichuwouldn't Red Hat, Oracle and SUSE audit critical software before including it in their enterprise distros?
20:32.43InocuousIt's really reckless what's happening I think. I'm sure I'm preaching to the choir, just venting a little.
20:33.29fsmithredInocuous, you gotta watch old western movies - the good guys weaer white hats and the bad guys wear black hats.
20:33.30muep_I do not think any general-purpose distro has been doing thorough auditing for included programs
20:33.49fsmithredred looks black in monochrome
20:34.21muep_even just the kernel is enormous. and also glibc and gcc are of similar scale
20:34.59*** join/#devuan Scartozzo (~flavio@2-233-3-55.ip215.fastwebnet.it)
20:36.15fsmithredsomeone posted a link to a document from redhat where they come right out and say that they want to increase complexity so people will want to buy support.
20:37.16zdzichufsmithred: that was an interview
20:37.26fsmithredah, thanks
20:38.49asbestofantastic
20:38.51asbestoI installed it
20:38.51asbesto:D
20:38.56*** join/#devuan radsy (~irc@unaffiliated/radsy)
20:39.17zdzichufsmithred: found it, this one: http://asay.blogspot.ru/2006/10/interview-with-red-hat-cto-brian.html
20:39.36Inocuousfsmithred, I remember Clint always wore a light colored hat, come to think of it. haha
21:06.34*** join/#devuan mns` (~mns@177.13.50.194)
21:26.53*** join/#devuan golinux (~golinux@2605:6000:ebc6:d200:96de:80ff:febc:9ea8)
21:26.54*** join/#devuan golinux (~golinux@unaffiliated/golinux)
21:45.00*** join/#devuan argwings (~user@71-211-118-75.phnx.qwest.net)
21:50.05*** join/#devuan argwings (~user@71-211-118-75.phnx.qwest.net)
21:53.46Centurion_Danfor anybody interested there is a new dbus available in /devuan ascii-proposed repository.  I'm keen for a few testers to give it a spin before we move it in to ascii - it hasn't had the testsuite run on it...
22:14.50InocuousI see XFce has release a newer version of their desktop manager.
22:16.04InocuousI wonder if it's systemd dependent. They are saying it's their best release
22:17.51Inocuous4.10 is really easy on my processor but it's not the most appealing desktop, it reminds me of windows 3.1
22:20.26*** join/#devuan furrywolf (~randyg@68.26.14.214)
22:26.10LiekeInocuous: you mean xfce 4.12? see the very end of this page: http://xfce.org/about/tour
22:27.21Inocuousopenbsd? Is that good or bad? I don't know.
22:27.37Liekethere is no systemd for bsd, so it's good
22:27.54Inocuousahh. nice.
22:38.41Inocuous4.10 is pretty easy on the processor. It has a couple quircks but I'ld be nervous about upgrading.  These changes are not likely to be more lean than the older version I suspect.
22:41.49DocScrutinizer05hands ksx4system a drink
22:42.21Inocuoussays pass the bottle please....
22:44.12*** join/#devuan asbesto (~asbesto@88-149-241-188.v4.ngi.it)
22:56.33DocScrutinizer05next drink is on me
23:03.25ksx4systemreaches to backpack and takes out another bottle then passing it to DocScrutinizer05
23:03.26ksx4systemlol
23:04.07ksx4systemCenturion_Dan: is there jessie-security-proposed yet?
23:04.23DocScrutinizer05on the taurus
23:04.27DocScrutinizer05cheers
23:04.48Centurion_Danksx4system: jessie-proposed-security
23:05.20ksx4systemCenturion_Dan: oh, so it does exist :) I'll update my sources.list then
23:06.24ksx4systemW: Failed to fetch http://auto.mirror.devuan.org/merged/dists/jessie-proposed-security/main/binary-amd64/Packages  404  Not Found [IP: 46.105.191.77 80]
23:06.27ksx4systemmeh
23:07.32DocScrutinizer05hmmm
23:08.11DocScrutinizer05!amprolla
23:08.11infobotnextime gave an excellent explanation how amprolla works, at https://botbot.me/freenode/devuan/2016-05-07/?msg=65646427&page=4, or https://git.devuan.org/devuan-infrastructure/amprolla
23:11.20Centurion_Danksx4system: it's only in /devuan - we don't merge the -proposed branches
23:12.40Centurion_Danso deb http://auto.mirror.devuan.org/merged jessie-proposed-security main
23:12.54Centurion_Danoops...
23:13.11Centurion_Danshould be: deb http://auto.mirror.devuan.org/devuan jessie-proposed-security main
23:13.46Centurion_Danbut there is nothing there yet so it will probably bomb out.
23:14.31ksx4systemshould I use /merged or /debian for proposed-updates?
23:15.00ksx4systemno errors whatsoever when using /merged
23:15.24*** join/#devuan antofox (~antofox@dynamic-adsl-78-12-42-76.clienti.tiscali.it)
23:15.57*** join/#devuan golinux (~golinux@unaffiliated/golinux)
23:17.55Centurion_Danksx4system: we don't merge -proposed-updates at the moment... but maybe we should as there is a matching debian mirror for that.
23:18.50ksx4systemhttp://auto.mirror.devuan.org/merged/dists/jessie-proposed-updates/main/binary-amd64/
23:19.17ksx4system~500k Packages file
23:19.47Centurion_Danmaybe we do then... ;-)
23:20.05ksx4systemlol :D
23:21.42Centurion_Danwe also have jessie-proposed and ascii-proposed as in /devuan as scratch spaces for testing packages we are preparing to drop into jessie and ascii directly
23:22.13Centurion_Danfor unstable/ceres we will use either incoming or experimental

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