Re: [dev] Suckless e-comerce script proposal

2016-09-23 Thread Joseph Graham
On Fri, Sep 23, 2016 at 10:24:46AM +0800, Kai Hendry wrote: > Yes, make the site static & host on S3/CloudFront. Generate from a DB > of your stock/inventory. Go lang's html/template makes this painless. > > Dynamic bits should be ReactJS chatting with Stripe APIs. I would go > so far as use Strip

Re: [dev] ot: C Standard noreturn

2016-09-23 Thread Mahdi Khanalizadeh
Hi, noreturn is part of the C11 header stdnoreturn.h. Either use _Noreturn or include that header beforehand. See: http://en.cppreference.com/w/c/language/_Noreturn Cheers pgpIkErznIOL8.pgp Description: PGP signature

[dev] [ST] scroll patch build failure

2016-09-23 Thread Nick Warne
I am not getting much luck here (do _I_ suck?) :( dwm and st work great so far and I am well impressed and happy; but any patches I apply either fail: http://lists.suckless.org/dev/1609/30448.html (I have since tried git versions, and it fails to build - but more later, that is on the back-burne

[dev] [slcon3] schedule update

2016-09-23 Thread Anselm R Garbe
Hi there, please note the updated schedule[0], especially the dinner location[1] for tonight. http://suckless.org/conference http://www.derwaldgeist.de Best regards, Anselm

Re: [dev] [ST] scroll patch build failure [SOLVED]

2016-09-23 Thread Nick Warne
On Fri, 23 Sep 2016 17:09:36 +0100 Nick Warne wrote: > I am not getting much luck here (do _I_ suck?) :( > > dwm and st work great so far and I am well impressed and happy; but > any patches I apply either fail: > > http://lists.suckless.org/dev/1609/30448.html > > (I have since tried git vers

Re: [dev] [ST] scroll patch build failure

2016-09-23 Thread Rodrigo S. Cañibano
> st.c:337:12: error: ‘histsize’ undeclared here (not in a function) > Line hist[histsize]; /* history buffer */ In the scroll patch 'histsize' is added to config.def.h, and therefore to config.h. Didn't that patch apply? Does your config.h have a line with "#define histsize 5000"?

Re: [dev] [ST] scroll patch build failure

2016-09-23 Thread Nick Warne
On Fri, 23 Sep 2016 17:36:21 +0100 Nick Warne wrote: > On Fri, 23 Sep 2016 13:32:14 -0300 > Draco Metallium(Rodrigo S. Cañibano) wrote: > > > > st.c:337:12: error: ‘histsize’ undeclared here (not in a function) > > > Line hist[histsize]; /* history buffer */ > > > > In the scroll patch '

Re: [dev] [ST] scroll patch build failure

2016-09-23 Thread Nick Warne
On Fri, 23 Sep 2016 13:32:14 -0300 Draco Metallium(Rodrigo S. Cañibano) wrote: > > st.c:337:12: error: ‘histsize’ undeclared here (not in a function) > > Line hist[histsize]; /* history buffer */ > > In the scroll patch 'histsize' is added to config.def.h, and therefore > to config.h. Didn't

Re: [dev] [ST] scroll patch build failure

2016-09-23 Thread Rodrigo S. Cañibano
My bad! I should have copy the line from the patch itself and not from my config. On 23 September 2016 at 13:40, Nick Warne wrote: > On Fri, 23 Sep 2016 17:36:21 +0100 > Nick Warne wrote: > >> On Fri, 23 Sep 2016 13:32:14 -0300 >> Draco Metallium(Rodrigo S. Cañibano) wrote: >> >> > > st.c:337:

Re: [dev] [ST] scroll patch build failure

2016-09-23 Thread Nick Warne
On Fri, 23 Sep 2016 13:43:22 -0300 Draco Metallium(Rodrigo S. Cañibano) wrote: > My bad! No way! I just cloned st again, got the patch, applied, all builds now and works OK. Thanks, Works a treat. Nick > I should have copy the line from the patch itself and not from my > config. > > On 23

[dev] containers opinion

2016-09-23 Thread stephen Turner
whats the suckless view of containers and why? what about a containerized init helper where sinit calls the container program and then runs daemons and the rest of the system from containers? Do you feel containers offer additional security/stability? Just thinking about "cloud" stuff again and da

Re: [dev] containers opinion

2016-09-23 Thread Thomas Levine
My personal view is that separate users are enough software separation for everything that I have ever wanted to do. Dunno about the party line though. On Fri, Sep 23, 2016, at 05:19 PM, stephen Turner wrote: > whats the suckless view of containers and why? what about a > containerized init helper

Re: [dev] containers opinion

2016-09-23 Thread hiro
containers are there to emulate static linking or the common portable windows programs in the form of a single .exe there is no security benefit of running more people's software on your computer.

Re: [dev] containers opinion

2016-09-23 Thread Daniel Abrecht
I am new here. I am using devuan + libvirt + lxc containers. I think in terms of security, it's less secure than a VM, since it shares the kernel & resources with the host system. But I think it's easier to backup & update containers. I like that I can just copy a container to another computer, and

Re: [dev] containers opinion

2016-09-23 Thread Ben Woolley
> On Sep 23, 2016, at 12:18 PM, hiro <23h...@gmail.com> wrote: > > containers are there to emulate static linking or the common portable > windows programs in the form of a single .exe > > there is no security benefit of running more people's software on your > computer. > I am reminded of th

Re: [dev] containers opinion

2016-09-23 Thread Kamil Cholewiński
On Fri, 23 Sep 2016, stephen Turner wrote: > whats the suckless view of containers and why? what about a > containerized init helper where sinit calls the container program and > then runs daemons and the rest of the system from containers? Do you > feel containers offer additional security/stabil

Re: [dev] containers opinion

2016-09-23 Thread Martin Kühne
Only slightly relevant, but I found this on Alan Cox' feed today: https://ptpb.pw/R5ZJ.jpg cheers! mar77i

Re: [dev] containers opinion

2016-09-23 Thread hiro
> Docker daemon is a single, statically > linked binary. that's irrelevant. you still need the right version of loonix with namespaces support, etc. containers are not independent of the operating system.

Re: [dev] containers opinion

2016-09-23 Thread Anselm R Garbe
On 23 September 2016 at 19:19, stephen Turner wrote: > whats the suckless view of containers and why? what about a Containers are an indicator of conceptual decay. Application developer code has now become infrastructure and is due to the juniority far away from any half-standardized protocols. I