On Tue, 2020-03-10 at 18:48 +0100, Simon Richter wrote:
> Hi,
>
> On Tue, Mar 10, 2020 at 03:50:42PM +, jnq...@gmail.com wrote:
>
> > - the 'move start-stop-daemon' trick is the old-old solution, kept
> > around because some packages failed to get on board with the
> > policy-
> > rc.d
On Tue, 2020-03-10 at 16:23 +0100, Marco d'Itri wrote:
> On Mar 10, jnq...@gmail.com wrote:
>
> > If the policy-rc.d solution is the modern/best/whatever solution,
> > the
> No. policy-rc.d is the old solution which was implemented because
> there
> was no better way to implement this with init
On Tue, 2020-03-10 at 19:39 +0500, Andrey Rahmatullin wrote:
> On Tue, Mar 10, 2020 at 02:33:50PM +, jnq...@gmail.com wrote:
> > If the policy-rc.d solution is the modern/best/whatever solution,
> > the
> > fact that live-build/debootstrap also includes the 'moving start-
> > stop-
> > daemon'
On Tue, 2020-03-10 at 08:47 -0400, Marvin Renich wrote:
> I think the OP's question was not about creating a package with a
> daemon
> that is disabled by default, but about preventing an existing
> package,
> that would otherwise start its daemon, from starting it.
That was my understanding
On Sun, 2020-03-08 at 11:44 -0400, Marvin Renich wrote:
> * jnq...@gmail.com [200308 10:58]:
> > On Sat, 2020-03-07 at 21:30 +0100, Tomas Pospisek wrote:
> > > The problem is that installing the package will automatically
> > > start
> > > the
> > > daemon cluster in a "default" configuration.
>
On Sun, 2020-03-08 at 18:50 +0100, Marc Haber wrote:
> debootstrap's files don't contain the string "divert". They do,
> however, dump "exit 101" to $TARGET/usr/sbin/poliy-rc.d.
I should issue a small correction to my earlier statement of live-build
using a dpkg-divert of start-stop-daemon as
On Sun, 2020-03-08 at 18:50 +0100, Marc Haber wrote:
> On Sun, 08 Mar 2020 14:58:01 +, jnq...@gmail.com wrote:
> > how live-build achieves this is essentially the same as happens to
> > be
> > discussed in the linked page for Debian's debootstrap package (the
> > tool
> > for building the base
On Sat, 2020-03-07 at 21:30 +0100, Tomas Pospisek wrote:
> The problem is that installing the package will automatically start
> the
> daemon cluster in a "default" configuration.
>
> That's a problem for me because etcd differentiates between starting
> the
> cluster for the first time and
On Tue, 2020-02-18 at 17:35 +, jnq...@gmail.com wrote:
> On Tue, 2020-02-18 at 17:58 +0100, Svante Signell wrote:
> > Hello,
> >
> > I recently installed Debian/bullseye/sid in a VM from a snapshot.
> > After running
> > that image I realized the I got a merged-user installation.
> >
> > As
On Tue, 2020-02-18 at 17:58 +0100, Svante Signell wrote:
> Hello,
>
> I recently installed Debian/bullseye/sid in a VM from a snapshot.
> After running
> that image I realized the I got a merged-user installation.
>
> As for now I have:
> bin -> usr/bin
> lib -> usr/lib
> lib32 -> usr/lib32
>
I think that Ideally the BTS should offer per-bug subscription
functionality, like bugzilla. Submitter and maintainer would be added to
the list automatically upon submission of the bug report; contributors
to the bug report could also be added automatically upon submission of
their message.
Direct link:
https://lists.debian.org/debian-efi/
Joined!
On 17/01/2015 09:57, Steve McIntyre wrote:
In article 20141216233320.gg14...@einval.com I wrote:
On Thu, Dec 11, 2014 at 07:00:34PM +, Steve McIntyre wrote:
Hi folks,
I'm thinking it might be useful to set up a specific
12 matches
Mail list logo
