On Sb, 04 sep 21, 17:35:49, sp...@caiway.net wrote:
> SOLVED
>
> /usr/share/open-infrastructure/container/shutdown.txt
> is from package progress-linux-container:
>
> Progress Linux is a Debian derivative distribution focused on system
> integration.
>
> This package is a metapackage to be insta
Greg Wooledge [2021-09-04 11:35:25] wrote:
> On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
>> # file /sbin/reboot
>> /sbin/reboot: POSIX shell script, ASCII text executable
>
> That's not normal for a bullseye system using systemd for init.
Indeed.
> I'm not sure what you did
On Sat, 04 Sep 2021 14:46:21 -0400
The Wanderer wrote:
> On 2021-09-04 at 13:20, Greg Wooledge wrote:
>
> > On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
> >
> >> Greg Wooledge [2021-09-04 11:35:25] wrote:
> >> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
On 2021-09-04 at 13:20, Greg Wooledge wrote:
> On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
>
>> Greg Wooledge [2021-09-04 11:35:25] wrote:
>> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
>> >> # file /sbin/reboot
>> >> /sbin/reboot: POSIX shell script, AS
On Sat, Sep 04, 2021 at 12:54:35PM -0400, Stefan Monnier wrote:
> Greg Wooledge [2021-09-04 11:35:25] wrote:
> > On Sat, Sep 04, 2021 at 04:49:24PM +0200, sp...@caiway.net wrote:
> >> # file /sbin/reboot
> >> /sbin/reboot: POSIX shell script, ASCII text executable
> >
> > That's not normal for a bu
SOLVED
/usr/share/open-infrastructure/container/shutdown.txt
is from package progress-linux-container:
Progress Linux is a Debian derivative distribution focused on system
integration.
This package is a metapackage to be installed in a container
(systemd-nspawn).
# apt remove progress-linux-con
my up-to-date
> > > bullseye system:
> > >
> > > # reboot
> > > /usr/sbin/reboot: disabled in systemd-nspawn container
> >
> > Unless I'm mistaken, these messages are not generated by systemd.
> > In fact, there's nothing that resemb
my up-to-date
> > > bullseye system:
> > >
> > > # reboot
> > > /usr/sbin/reboot: disabled in systemd-nspawn container
> >
> > Unless I'm mistaken, these messages are not generated by systemd.
> > In fact, there's nothing that resemb
On Sat, 4 Sep 2021 16:42:45 +0300
Reco wrote:
> Hi.
> /bin/systemd reboot
>
> And, what about these:
>
> ls -al /sbin/reboot
> file /sbin/reboot
>
> Reco
>
the commands poweroff and reboot are textfiles.
I have no idea
# mcedit /sbin/reboot:
#!/bin/sh
echo "${0}: disabled in systemd
On Sat, 4 Sep 2021 16:42:45 +0300
Reco wrote:
> Hi.
>
> On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> > Suddenly I can no longer reboot or poweroff my up-to-date
> > bullseye system:
> >
> > # reboot
> > /usr/sbin/reboo
Hi.
On Sat, Sep 04, 2021 at 02:40:13PM +0200, sp...@caiway.net wrote:
> Suddenly I can no longer reboot or poweroff my up-to-date
> bullseye system:
>
> # reboot
> /usr/sbin/reboot: disabled in systemd-nspawn container
Unless I'm mistaken, these messages are not gene
Hi,
Suddenly I can no longer reboot or poweroff my up-to-date
bullseye system:
# reboot
/usr/sbin/reboot: disabled in systemd-nspawn container
Linux container share the kernel of the host system they are running on,
there is no need to reboot just the container.
However, please contact your
12 matches
Mail list logo
