Re: [DNG] Debian testing drop redis non systemd

[Joel Roth]

Jaromil wrote:
> I would like to know here if anyone knows in detail the "reasons"
> Debian is removing the support for sysvinit scripts in the redis
> package. Is there a limitation of sorts, or a problem generated by
> having the init scripts left in the package, or is it just vandalism?
> is there a discussion or bug open?

Don't know if a bug is open, but ISTR that reducing the
burden of maintaining and supporting users of sysv init
scripts was mentioned as one of Debian's reasons for
adopting systemd.

-- 
Joel Roth
  

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[Jaromil]

On Thu, 19 Oct 2017, Steve Litt wrote:

> When you contact them, you might want to also give them the runit run
> script for redis from the Void distro:

cheers Steve, I will pass it on.

ah!! now you like redis do you??? :^

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[Steve Litt]

On Thu, 19 Oct 2017 10:22:33 +0200
Jaromil  wrote:

> On Wed, 18 Oct 2017, Arnt Gulbrandsen wrote:
> 
> > Steve Litt writes:  
> > > Does anyone here actually use redis? I looked it up, and to me it
> > > looks like dbus on steroids. An in-memory data store accessible
> > > by lots of different applications. What could POSSIBLY go wrong?  
> > 
> > I've used in several contexts, it's great at its job and a joy to
> > use.  
> 
> Same here, its a core part of many software projects, not only web
> based but also on embedded systems and micro-service related.
> 
> One of its authors, antirez, is an old friend and coding made of some
> of us here. Redis is heavily inspired by minimalism, simplicity and
> UNIX principles since its inception. We will contact upstream so they
> notice the fact the Debian maintainers are removing a support which is
> provided upstream, since redis does pack scripts for sysvinit that
> should be left in place.

Hi Jaromil,

When you contact them, you might want to also give them the runit run
script for redis from the Void distro:

=
#!/bin/sh
if [ ! -d /var/lib/redis ]; then
mkdir -m0700 -p /var/lib/redis
fi
chown redis:redis /var/lib/redis
if [ ! -d /run/redis ]; then
mkdir -m0750 -p /run/redis
fi
chown redis:redis /run/redis
exec chpst -u redis:redis redis-server /etc/redis/redis.conf > /dev/null

=

Everything but the last line sets up properly permissioned directories.
The last line replaces the run script's process with redis-server,
running as user redis, group redis, configured
by /etc/redis/redis.conf. The fact that it's piped to /dev/null means
no logging takes place,  which is kind of weird. Maybe redis has a
logging facility of its own???

I installed it on my Void box, and it runs the command 
redis-server 127.0.0.1:6379
as a daemon.

Thanks,
 
SteveT

Steve Litt 
October 2017 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[golinux]

On 2017-10-19 06:24, Arnt Karlsen wrote:

On Thu, 19 Oct 2017 11:09:34 +0300, Aldemir wrote in message
:


>
> No need to panic. The situation is under control. Noone will pull
> sysv init support from redis.
>
> HND
>
> KatolaZ
>
>
That's the spirit! Many many thanks!
--
aldemir


..maybe we should file a bug (fix) demonstrating this proper
Devuan way to fix this and future such Debian/systemd bugs?



Choice is rapidly disappearing in the Debian camp.  In addition to 
Arnt's suggestion, this should be brought to light in the Debian user 
community - FDN and debian-user for starts. It is yet another wake up 
call for those who have been slow to grasp the gravity of the path that 
Debian has chosen.


I no longer have a Debian user account but when I have the time and 
mental clarity to find the right words (that won't be today), I will 
post to FDN. That should produce some lively discussion!


golinux

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[Arnt Karlsen]

On Thu, 19 Oct 2017 11:09:34 +0300, Aldemir wrote in message 
:

> >
> >
> >
> >
> > No need to panic. The situation is under control. Noone will pull
> > sysv init support from redis.
> >
> > HND
> >
> > KatolaZ
> >
> >  
> That's the spirit! Many many thanks!
> --
> aldemir

..maybe we should file a bug (fix) demonstrating this proper 
Devuan way to fix this and future such Debian/systemd bugs?

-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[Jaromil]

On Wed, 18 Oct 2017, Alberto Zuin - Liste wrote:

> Redis project started by an Italian guy which is also in the VUA
> group.


indeed. yet another VUA being outed :^) let's hope systemd-hooligans
don't go and delete wikipedia pages about him and his work too now.


antirez just replied me on the fly because he is traveling and
confirms that official Redis position is that of supporting all init
systems. He also says that: the most "obvious" way to start redis is
from init.d scripts. distros may do whatever they want, but the
support to start redis from a sysvinit script will never be removed.

I would like to know here if anyone knows in detail the "reasons"
Debian is removing the support for sysvinit scripts in the redis
package. Is there a limitation of sorts, or a problem generated by
having the init scripts left in the package, or is it just vandalism?
is there a discussion or bug open?

ciao

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] trusting components (was: systemd-udevd: renamed network interface eth0 to eth1)

[Rick Moen]

Quoting Simon Hobson (li...@thehobsons.co.uk):

> Many years ago there was a demonstration of how to build a backdoor
> into the "login" binary.

https://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thompson.pdf

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] trusting components (was: systemd-udevd: renamed network interface eth0 to eth1)

[Simon Hobson]

John Franklin  wrote:

> Note, I say, “possible”, not guaranteed or anything like that.  Signing 
> doesn’t prevent malware from getting in to the system.  If the build system 
> is compromised, as was the case recently with CCleaner, the malware gets 
> signed.

There was a much earlier example - though not in the wild.

My memory on the details are vague, but there's been a project (Part of Debian 
?) to "prove" that a binary was created from a given source - not trivial since 
slight differences in environment and compiler optimisations mean that simply 
compiling the source won't always create an identical binary.

Many years ago there was a demonstration of how to build a backdoor into the 
"login" binary. It involved changing the C compiler to detect when it is 
compiling "login" and automatically add the code for the backdoor. The user can 
inspect the code and find nothing wrong, but silently the binary has been 
compromised by a compromised build tool. Without the means to prove that a 
binary is in fact the result of compiling specific code, there's no practical 
way to detect such a compromise.

So yes, to be able to trust anything, you have to be able to trust every 
component of the system - and the tools used to build them.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[Arnt Gulbrandsen]

jaro...@dyne.org writes:

Same here, its a core part of many software projects, not only web
based but also on embedded systems and micro-service related.


Totally offtopic but some if you will be fascinated by the references to 
redis in this talk by John Regehr: https://youtu.be/Ux0YnVEaI6A


Summary: Compiler research (and in particular superoptimiser research) 
involves spending a LOT of CPU time on finding optimisation candidates and 
judging their potential. Hours or even days to compile an executable. 
Caching across invocations helps speed that up, and sharing redis dumps is 
useful for discussing results and reporting bugs.


Arnt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[Jaromil]

On Wed, 18 Oct 2017, Arnt Gulbrandsen wrote:

> Steve Litt writes:
> > Does anyone here actually use redis? I looked it up, and to me it looks
> > like dbus on steroids. An in-memory data store accessible by lots of
> > different applications. What could POSSIBLY go wrong?
> 
> I've used in several contexts, it's great at its job and a joy to use.

Same here, its a core part of many software projects, not only web
based but also on embedded systems and micro-service related.

One of its authors, antirez, is an old friend and coding made of some
of us here. Redis is heavily inspired by minimalism, simplicity and
UNIX principles since its inception. We will contact upstream so they
notice the fact the Debian maintainers are removing a support which is
provided upstream, since redis does pack scripts for sysvinit that
should be left in place.

This episode is again of great shame on Debian maintainers, but it
should be addressed by upstream.

ciao

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[Aldemir Akpinar]

>
>
>
>
> No need to panic. The situation is under control. Noone will pull sysv
> init support from redis.
>
> HND
>
> KatolaZ
>
>
That's the spirit! Many many thanks!
--
aldemir
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[KatolaZ]

On Wed, Oct 18, 2017 at 03:46:39PM +0200, Bardot Jérôme wrote:
> redis (4:4.0.2-3) unstable; urgency=medium
> 
>   This version drops the Debian-specific support for the
>   /etc/redis/redis-{server}.sentinel.{pre,post}-{up,down}.d directories in
>   favour of using systemd's ExecStartPre, ExecStartPost, ExecStopPre,
>   ExecStopPost commands.
> 
>  -- Chris Lamb   Wed, 11 Oct 2017 22:55:00 -0400
> 


No need to panic. The situation is under control. Noone will pull sysv
init support from redis. 

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Debian testing drop redis non systemd

[tirveni yadav]

On Thu, Oct 19, 2017 at 4:56 AM, Hendrik Boom  wrote:
> On Wed, Oct 18, 2017 at 03:46:39PM +0200, Bardot Jérôme wrote:
>> redis (4:4.0.2-3) unstable; urgency=medium
>>
>>   This version drops the Debian-specific support for the
>>   /etc/redis/redis-{server}.sentinel.{pre,post}-{up,down}.d directories in
>>   favour of using systemd's ExecStartPre, ExecStartPost, ExecStopPre,
>>   ExecStopPost commands.
>>
>>  -- Chris Lamb   Wed, 11 Oct 2017 22:55:00 -0400
>>
>
>> pub  4096R/03878A98 2015-08-26 Bardot Jérôme 
>> sub  4096R/4144A514 2015-08-26 [expires: 2020-08-24]
>
> From all the responses in this thread, it looks as if there is ample
> reason to keep it around for Devuan.
>
> -- hendrik
>

+1

We are using Redis for caching and sessions in the applications servers.

Redis is very useful application.


-- 
Regards,

Tirveni Yadav
www.udyansh.org
www.bael.io

What is this Universe ? From what it arises ? Into what does it go?
In freedom it arises, In freedom it rests and into freedom it melts away.
Upanishads.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng