Hi Mark,
On 6/18/23 10:33, Mark Hindley wrote:
> I would still disagree with that.
just to avoid misunderstandings, my current understanding is:
1) technical issue: non-bootable systems on some non-systemd systems
- can be handled by moving mdadm initscripts into
orphan-sysvinit-sc
Daniel,
Many thanks.
On Sun, Jun 18, 2023 at 07:48:03AM +0200, Daniel Baumann wrote:
> Assuming there are no problems of having mdadm initscripts in
> orphan-sysvinit-scripts, I think this is the best way forward.
I would still disagree with that. However, even if that were the path taken, it
do
Hi Mark,
On 6/17/23 19:13, Mark Hindley wrote:
> I am asking gently for the reinstatement of the recently removed non-systemd
> initscripts.
I hear you, but I prefer not doing this for the stated reasons.
How about getting the mdadm initscript into orphan-sysvinit-scripts? I
read the section ab
Michael,
On Sat, Jun 17, 2023 at 07:17:40PM +0300, Michael Tokarev wrote:
> You're still not getting the point. Which is the lack of real infrastructure
> within other init systems, which needs real work. Which, apparently,
> neither you nor other complainers are willing to do.
I am not complain
17.06.2023 19:05, Mark Hindley wrote:
Michael,
On Sat, Jun 17, 2023 at 08:07:52AM +0300, Michael Tokarev wrote:
I wonder do we want no mdadm in debian at all or working mdadm with systemd?
From the two alternatives I definitely prefer the working one..
That isn't the choice on offer.
It i
Michael,
On Sat, Jun 17, 2023 at 08:07:52AM +0300, Michael Tokarev wrote:
> I wonder do we want no mdadm in debian at all or working mdadm with systemd?
> From the two alternatives I definitely prefer the working one..
That isn't the choice on offer. The choice is mdadm in Debian which is only
us
17.06.2023 06:30, Olaf Meeuwissen wrote:
..
Please consider bumping this bug to a Severity that keeps it from
migrating to testing/trixie until this is resolved.
# I'll be putting mdadm on hold on my systems for the time being.
I wonder do we want no mdadm in debian at all or working mdadm wit
Hi,
Thanks for forwarding this, Mark.
Daniel, I'm not particularly charmed by the retitling to
show note about missing boot integration for non-systemd
I have a few runit-init based systems with mdadm that run testing,
which, thankfully, still has 4.2-5.
The version in sid is old enough to m
Daniel,
Many thanks for your reply.
On Tue, Jun 13, 2023 at 03:32:23PM +0200, Daniel Baumann wrote:
> > It would be a great help to users of non-systemd inits if you could restore
> > them.
>
> thanks you for your report.
>
> Personally I'm using systemd, but in general I fully agree that as
retitle 1037496 show note about missing boot integration for non-systemd
thanks
Hi Mark,
On 6/13/23 14:28, Mark Hindley wrote:
> It would be a great help to users of non-systemd inits if you could restore
> them.
thanks you for your report.
Personally I'm using systemd, but in general I fully
Source: mdadm
Version: 4.2+20230227-1
Severity: normal
Dear Daniel,
SysV initscripts and cron jobs have recently been removed from mdadm. It would
be a great help to users of non-systemd inits if you could restore them. Service
files and initscripts can happily coexist and systemd will use the a
11 matches
Mail list logo
