Re: [DNG] UEFI and Secure Boot

On Mon, 2017-10-23 at 17:06 +0200, Didier Kryn wrote: > I've read previously on this list that secureboot doesn't prevent > booting from a usb key... Or did I misunderstood? Correct, so long as the boot loader on the USB key is signed by a key the system trusts. And you didn't disable

Re: [DNG] UEFI and Secure Boot

On Tue, 2017-10-24 at 09:01 +0200, marc wrote: > Secureboot is designed for them, not for you. You might come > up with a really exotic use case, where it might help you. But > if you look at it carefully enough, it relies on secureboot > redefining root to something weaker than what we want, and

Re: [DNG] Debian testing drop redis

Hi -dng, > […] I am the maintainer of Redis in Debian. All I have done is removed some ill-conceived hooks that were not used by anyone. I have not dropped sysvinit support and nor do I have any intention to do so. I only ask politely that you do stop to refering to my work as "vandalism".

Re: [DNG] Debian testing drop redis non systemd

On Tue, 24 Oct 2017 07:44:51 -0500 Patrick Meade wrote: > However, if they are on Devuan, there is no systemd. And without > restoring the old functionality or providing new functionality, our > answer will be an empty one: "Debian upstream broke it. Sorry." And > our poor

Re: [DNG] Virtualbox?

Hi Ozi, list, Ozi Traveller writes: > Has anyone installed virtualbox from jessie-backports? There is a systemd > dependency, but not sure whether it's functional or just a stub. I don't see where the systemd dependency is. Here's what I get $ apt-cache -t jessie-backports depends

Re: [DNG] Error after upgrade debian wheezy to devuan jessie...

Hi Olaf, Am 25.10.2017 um 12:41 schrieb Olaf Meeuwissen: > Thomas Besser writes: > >> [...] >> As far as I understand, package libc-bin registers dpkg (?) triggers >> scripts which are executed on every update of any package. >> >> How can I find out, which trigger script of libc-bin causes this

Re: [DNG] Error after upgrade debian wheezy to devuan jessie...

Hi, Thomas Besser writes: > [...] > As far as I understand, package libc-bin registers dpkg (?) triggers > scripts which are executed on every update of any package. > > How can I find out, which trigger script of libc-bin causes this error? > There must be a place, where dpkg stores this

Re: [DNG] ..proper use of /merged and /devuan, was: Trouble with apt-get upgrade over TOR

On Tue, 24 Oct 2017 21:18:37 +0200, Arnt wrote in message <20171024211837.11a60797@d44>: > On Tue, 24 Oct 2017 18:26:45 +0100, KatolaZ wrote in message > <20171024172645.gy4...@katolaz.homeunix.net>: > > > > > jessie-proposed is under /devuan > > jessie-proposed-updates is under

Re: [DNG] lantian problem on ASCII

On Wed, Oct 25, 2017 at 09:00:44AM +0200, m_maass wrote: [cut] > my sources.list: > > deb http://packages.devuan.org/merged/ ascii main contrib non-free > deb-src http://packages.devuan.org/merged/ ascii main contrib non-free > deb http://packages.devuan.org/merged/ ascii-updates main contrib

Re: [DNG] ..proper use of /merged and /devuan, was: Trouble with apt-get upgrade over TOR

On Tue, Oct 24, 2017 at 04:39:53PM -0400, Fungal-net wrote: [cut] > > I did not ask because I wanted to blame anyone, but asked so I can solve a > problem > The above instructions are what they SHOULD be and this is HOW THEY WERE. > Since the keyring was not updated prior to the shift to

[DNG] lantian problem on ASCII

Dear all, i want to build on ascii debian installer. This require module-init-tools, that do no more exist in ascii. It is replaced with kmod. Now i want to build kmod from sources, apt-get source kmod then debuild  -us -uc bring   Now running lintian...   Could not load