> > # while true; do kill -ILL 1 ; echo -n "." ; sleep 0.5 ; done
> >
> > I found out PID 1 is killed when I tried to reboot:
> > # reboot
> > Failed to open /dev/initctl: No such device or address
> > Failed to talk to init daemon.
> >
> > So I will have to use SysReq keys
> >
>
> Can
On Sat, May 25, 2019 at 08:35:45AM -0400, Kenneth Parker wrote:
[...]
> Can somebody, please link me to the Documentation Files on those SysReq
> keys? Thanks!
https://en.wikipedia.org/wiki/Magic_SysRq_key
Cheers
-- t
signature.asc
Description: Digital signature
On Sat, May 25, 2019, 5:45 AM arne wrote:
> On Sat, 25 May 2019 00:21:07 +0200
> arne wrote:
>
> > On Fri, 24 May 2019 23:43:49 +0200
> > arne wrote:
> >
> > > On Fri, 24 May 2019 14:01:35 -0700
> > > Fred wrote:
> > >
> > > > Hello,
> > > > I subscribe to the Devuan Linux mailing list. This
On Sat, May 25, 2019 at 10:25:26AM +0300, Reco wrote:
[...]
> Seems harmless to me as one needs to be root to send signals to PID 1.
This is *exactly* the point. If you are root, there are far more creative
(and fun) ways to bring down your system, regardless of how your init
process is called.
to...@tuxteam.de (12019-05-25):
> That means that to send SIGILL to pid 1 you most probably gotta be
> root (systemd or not). And then, there are more classy ways to bring
> your system down anyway.
>
> Folks, please double-check that stuff before reposting. I don't want
> the Debian mailing list
On Sat, 25 May 2019 00:21:07 +0200
arne wrote:
> On Fri, 24 May 2019 23:43:49 +0200
> arne wrote:
>
> > On Fri, 24 May 2019 14:01:35 -0700
> > Fred wrote:
> >
> > > Hello,
> > > I subscribe to the Devuan Linux mailing list. This posting just
> > > arrived and it appears quite important to
On 2019-05-25 08:25, Reco wrote:
again no problem here.
Stretch's systemd:
# kill -ILL 1
Message from syslogd@xxx at May 25 10:19:09 ...
systemd[1]: Caught , dumped core as pid 822.
...
systemd[1]: Freezing execution.
The userspace and the kernel will work after this, but anything that's
On 2019-05-25, wrote:
>
> Folks, please double-check that stuff before reposting. I don't want
> the Debian mailing list to become Fakebook or Twitter.
>
Or Der Spiegel.
https://www.theatlantic.com/international/archive/2019/01/der-spiegal-fabrication-scandal-global/579889/
--
“Decisions are
Hi.
On Sat, May 25, 2019 at 12:21:07AM +0200, arne wrote:
> On Fri, 24 May 2019 23:43:49 +0200
> arne wrote:
>
> > On Fri, 24 May 2019 14:01:35 -0700
> > Fred wrote:
> >
> > > Hello,
> > > I subscribe to the Devuan Linux mailing list. This posting just
> > > arrived and it appears
On Fri, May 24, 2019 at 02:01:35PM -0700, Fred wrote:
> Hello,
> I subscribe to the Devuan Linux mailing list. This posting just
> arrived and it appears quite important to Debian.
[about sending SIGILL to systemd]
This is most probably fake news.
You have to have appropriate permissions to
On Fri, 24 May 2019 23:43:49 +0200
arne wrote:
> On Fri, 24 May 2019 14:01:35 -0700
> Fred wrote:
>
> > Hello,
> > I subscribe to the Devuan Linux mailing list. This posting just
> > arrived and it appears quite important to Debian.
> >
> > Forwarded Message
> > Subject:
On Fri, 24 May 2019 14:01:35 -0700
Fred wrote:
> Hello,
> I subscribe to the Devuan Linux mailing list. This posting just
> arrived and it appears quite important to Debian.
>
> Forwarded Message
> Subject: [DNG] Linux system can be brought down by sending
> SIGILL to
Hello,
I subscribe to the Devuan Linux mailing list. This posting just arrived
and it appears quite important to Debian.
Forwarded Message
Subject: [DNG] Linux system can be brought down by sending SIGILL to
Systemd
Date: Fri, 24 May 2019 22:04:34 +0200
From: Martin
13 matches
Mail list logo
