Re: [DNG] calendars, contacts, to do lists
On 5/23/19 5:44 PM, Hendrik Boom wrote: > Any ideas? using thunderbird/lightning with tbsync/enigmail. all connected to private nextcloud instance for calendar, tasks, contacts, and even using filelink regularly. another email client/suite i tried lately and was impressed that everything "just worked", was evolution. d. signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Where to reply for Steve Litt
Il giorno giovedì 23/05/2019 20:07:17 -0400 Steve Litt ha scritto: > On Thu, 23 May 2019 15:21:30 -0700 > Rick Moen wrote: > > [snip] > > My claws-mail has a reply-to-list, which *usually* does the right thing My cent in this regard... At the ML side: - dng ML user configuration (https://mailinglists.dyne.org/cgi-bin/mailman/options/dng) has the 'Avoid duplicate copies of messages?' option which could be set ON At the user side, claws-mail (IMO the best available email client) is great handling MLs [1]: - has a Reply-to-list feature (needs the ML has been configured (by admins) to send the 'List-Id:' header, as is with the dng ML) - let users to perform a Reply-to-list when receiving ML emails in digest mode with respect to _each_ single message in the digest (needs MIME digests has been activated in the ML user configuration) - let user to define 'actions' to run terminal commands with emails... - let user to define filtering and pre and/or post processing rules... and more [1]: - let user complete control over spam management (official plugin) - handle signed and/or encripted emails (PGP/GPG and S/MIME) (official plugin) - multiple accounts and both mailbox and mbox formats are supported - ... I am sending this message with claws-mail, from one of my several email accounts, selecting the message to which to reply from the digest, signing the reply with GnuPG directly in the compose windows, and using reply-to-list to send... Regards [1] https://www.claws-mail.org/features.php -- al3xu5 Say NO to copyright, patents, trademarks and any industrial design restrictions. Public GPG/PGP key block ID: 4096 bit RSA key 69C5977BF94CFE23 Fingerprint: 59C6 9DC7 CD4B CF2F A190 E3DE 69C5 977B F94C FE23 pgplSnVfwXD2v.pgp Description: Firma digitale OpenPGP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] email clients: was Where to reply for Steve Litt
On Thu, May 23, 2019 at 08:15:22PM -0400, Steve Litt wrote: [cut] > > Can GNUS be used as a window into a local multilevel many-mailboxed > Dovecot IMAPserver? Same question with mutt: I haven't gotten it to > happen, correctly, all the time. > IMAP support in mutt works just fine. There were issues with network timeouts until a few years ago, but all of them should be solved by now. My2Cents KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] email clients: was Where to reply for Steve Litt
On Thu, May 23, 2019 at 06:42:02PM -0700, Rick Moen wrote: > Um, dunno, sorry. I don't do emacs. (I'm a sysadmin, not a coder. > C-x C-c is just about all the emacs I know -- the commands to get the > hell out.) Switch to another session, kill -9. This has the upside of working with other monstrosities, such as vi[m]. Hope this helps. :þ > 1. You run an SMTP smarthost, which sends/receives mail to/from other > smarthosts, and hands off incoming mail to an LDA (local delivery > agent), which was procmail. > 2. Your MUA operated _there_, because that's where the mail was. And why are you using past tense? Such setup works just as well today as it did in the past. Trying to access mail remotely is a hassle, while ssh Just Works™. Add IMAP for other users and that's it. > That works and is dirt-simple. Your mail is always _right there_; none > of this bullshit of 'Oh, I don't have access to that mail now because I > pulled it down over IMAP at work and now I'm at home. Uh? The whole point of IMAP is that the mail you did read at work is still available for a MUA at home. And even for local mutt. I for one use Thunderbird as a glorified biff and to view some html monstrosities and/or images (although elinks and chafa from mutt are often enough), this old-style setup works perfectly. > in bog-standard Neanderthal mbox format. The rest is in > ~/inboxes/[thing] in bog-standard Neanderthal mbox format -- except for > archived old mail that's tucked away in bog-standard Neanderthal mbox > format, gzipped. That's indeed Neanderthal -- you should be using Maildir :p (although mbox is still De??an default). > Accordingly, mutt has absolutely no access problems getting to my > mboxes, in as much as they are local to mutt. Best solution to IMAP > problems ever invented: no IMAP! No idea what your beef with IMAP is. It works well, without any of flaws POP has. > In case you're curious, I leave a couple of specialised-role instances > of mutt running 24x7 under GNU screen.[1] Anywhere I am in the world, I > just ssh to my server, reattach the screen sessions of interest, running > their respective mutt copies, and I'm exactly where I was with mutt the > last time I connected. Disconnect screen later, close ssh session, go > to sleep. Lather, rinse, repeat. I found it better to exit mutt instead. Even if you use a superior format like Maildir, mutt still thinks it's using that useless mbox crap, that needs costly rewrites to save message state. And that means mails you have deleted are still there, etc. This sucks if you open another instance of mutt. There's '$' but I never got into the habit of syncing often. Long-running screen sessions can also suffer if you reboot the machine due to a kernel sec hole, etc. > And yes, I've heard many times that mbox is terrible and that I should > use Maildir instead because it's much better for NFS file locking and > for IMAP access. But: no NFS here, no IMAP here. Thus, no NFS > problems and no IMAP problems. I can't fathom why anyone would use mail over NFS; IMAP does local caching so any accesses are fast even on an abysmal link. Individual mails from, ahem, certain users, have grown so much over the years that stuffing it in a linear-access mbox just doesn't work sanely anymore. Mailbox doesn't suffer from this problem, and doesn't care about that 100MB attachment mbox would have to rewrite over and over. > The Neaderthal lifestyle has its advantages, y'see. Yeah, but there's that fire and copper arrowhead goodness. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Latin: meow 4 characters, 4 columns, 4 bytes ⣾⠁⢠⠒⠀⣿⡁ Greek: μεου 4 characters, 4 columns, 8 bytes ⢿⡄⠘⠷⠚⠋ Runes: ᛗᛖᛟᚹ 4 characters, 4 columns, 12 bytes ⠈⠳⣄ Chinese: 喵 1 character, 2 columns, 3 bytes <-- best! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan AMI
Hi Steve, list,
Steve Litt writes:
> On Thu, 23 May 2019 12:15:06 -0700
> Rick Moen wrote:
>
>> Quoting Bruce Ferrell (bferr...@baywinds.org):
>>
>> > I could be wrong, but based on the context of his question:
>> >
>> > AMI = Amazon Machine Image
>>
>> I know Josef, and, yes, that's exactly what he meant. Amazon EC2 and
>> all that.
>>
>> (Asterisk Management Interface, really? {snort})
>
> On the other hand, before we make little in-groups based on knowledge
> of ambiguous acronyms, consider what I do. If I introduce any acronym
> that isn't public knowledge to every Linux user (DHCP, NIS, NFS), on
> first use in the email I associate the spelled out version with the
> acronym. 5 seconds more typing, and everything's clear.
ACK.
# That's the American Standard Code for Information Interchange (ASCII,
# see https://en.wikipedia.org/wiki/ASCII) for acknowledge. Numerical
# value is 6 in all of octal, decimal and hexadecimal ;-)
> Of course I
> *do* lose that "knowledgeable expert" status I could have gained by
> whipping out an unknown acronym.
On more than one occasion I've found that some acronym "flashers" are
just wildly flapping arms and waving hands in thin air trying to make an
impresssion rather than "knowledgeable experts". Anyone serious about
trying to get something across to an audience whose knowledge level is
not known a priori would spell it out first time around (with the
acronym in parentheses) *or* provide a link to a (wikipedia?) page
explaining the thing.
As per above.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
Support Free Softwarehttps://my.fsf.org/donate
Join the Free Software Foundation https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] calendars, contacts, to do lists
Hi, viverna writes: > il devuanizzato Hendrik Boom il 23-05-19 16:44:00 ha > scritto: >> I'm looking for software to handle appointment calendars, contact >> lists, and todo lists. > Org mode: > https://orgmode.org/ Using that myself in combination with mu4e to handle my maildirs. These are fed by maildrop, which gets its food from getmail4 which, in turn, probes the various mailboxen that I have. I haven't really done a lot of customization but things have been working okay for me. I really should take a look at improving the handling of iCalendar attachments at the office but can't be bothered to do so anytime soon so still copy-n-paste stuff to my org-mode planner file. Speaking of the office, I'm using davmail there to automate the Outlook Web Interface (OWA) interaction so I can direct getmail4 at the POP3 or IMAP servers provided by davmail. The office's Exchange server doesn't expose either anymore :-( # Rumour has it we're moving to Exchange Online ... :-/ # Guess I'll have a bumpy road ahead ... again. Emacs' calendar is pretty good and integrates nicely with org-mode. I'm quite pleased with the japanese-holidays extension which helps me keep the national holidays sorted out all right :-) # We just had a few odd-ball ones due to getting a new emperor. Org mode also integrates with BBDB (Big Brother DataBase), a contacts manager of sorts, and I seem to remember someone working on (perhaps already mostly completed) support for vCards integration for org-mode. Of course if you don't use Emacs already (or are hooked on vi/mutt) then most or all of the above is of little use and concern. Anyway, hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] email clients: was Where to reply for Steve Litt
Quoting Adam Borowski (kilob...@angband.pl): > And why are you using past tense? Because, at that point, I was talking about the 1980s? > Such setup works just as well today as it did in the past. [/me thumps server.] Yes, I can confirm this. > Uh? The whole point of IMAP is that the mail you did read at work is still > available for a MUA at home. And even for local mutt. Yes, it was primarily a syndrome you encountered with POP3, and IMAP defaults to leaving mail on the server, so you don't _need_ to pull down anything, correct. But the larger point is, remote MDAs in the first place, of either protocol, are a solution to a problem I perceive myself as no having, therefore I keep everything simpler by never installing one. > I for one use Thunderbird as a glorified biff and to view some html > monstrosities and/or images (although elinks and chafa from mutt are often > enough), this old-style setup works perfectly. [/me thumps server, again. Gloriously.] > That's indeed Neanderthal -- you should be using Maildir :p Can't be bothered. Works great without. > No idea what your beef with IMAP is. It works well, without any of flaws > POP has. You know what works even better? No need for any remote MDA at all, because your mail client is local to the mail spool in the first place, making remote MDAs a solution to a problem you _just don't have_. As a bonus, having no remote MDA problems means never having toe worry about remote-MDA security problems, remote-MDA performance problems, or any other remote-MDA complications, RAM/CPU wasted on remote-MDA processes. Everything is simple and easy to understand and all in one place (see 'Neanderthal'). Checking my watch, I note that it's 2019, when _some_ IMAP4 MDAs (such as Dovecot) are no longer dreadful piles of bugs. Originally, one contemplated woeful choices like the UW IMAP daemon, and my choice was 'How about not, instead? Not works for me.' Although _that_ problem (dreadful spaghetti code) has been alleviated, I still just don't need one. It's rather like when a salesman offers me a way to get better eyeglasses, and my reaction is 'I'm sure that's great, but I personally prefer not needing eyeglasses at all for life, monovision LASIK being actually a thing.' ;-> > I found it better to exit mutt instead. Even if you use a superior format > like Maildir, mutt still thinks it's using that useless mbox crap, that > needs costly rewrites to save message state. And that means mails you have > deleted are still there, etc. This sucks if you open another instance of > mutt. There's '$' but I never got into the habit of syncing often. I do '$' occasionally (when convenient). It's fast because everything's local (in addition to being conceptually simple). Search is fast, for lack of need to grovel through labyrinthine Maildir trees. And I really have no idea what's supposed to be 'costly' about the rewrites. The hardware was paid for long ago. ;-> (Every time I have to find something in someone's vast Maildir trees, I think fond thoughts about how much easier it all is at home.) > Long-running screen sessions can also suffer if you reboot the machine due > to a kernel sec hole, etc. Kernel sec holes, especially if you do not permit kernel featuritis (as part of that 'am a sysadmin' thing) happen so extremely rarely as to be hardly worth thinking about, in this regard. Very slightly less rare are transient main power interruptions on acount of thunderstorms, but fortunately Chez Moen is in Silicon Valley, not Florida or Maracaibo Lake. (We're actually rather civilised, here. There are even rumours of flush toilets arriving next year, and our state governor's a promising lad who doesn't think attempting to win deliberate tradewars is an intelligent idea, accepts that both anthropogenic climate change and heliocentrism are established science, and doesn't walk onto airplanes in front of the world's press corps with toilet paper trailing from his shoe.) > I can't fathom why anyone would use mail over NFS; IMAP does local caching > so any accesses are fast even on an abysmal link. I can't fathom why clients and employers do incredibly dumb things, either. Fortuately, the happy outcome of my getting paid still emerges from it. Except when the client/employer joins the Darwin Club in various ways, of course. I remember the major client that decided to be acquired by Enron Corporation, for example. Sad. Oh well: No omelets without breaking of eggs. Cheap gear to be had at the liquidation sale, so there's always a silver lining. > Individual mails from, ahem, certain users, have grown so much over the > years that stuffing it in a linear-access mbox just doesn't work sanely > anymore. Yeah, well, Works for Me.[tm] > Mailbox [RM: doubtless typo for 'Maildir'] doesn't suffer from this > problem, and doesn't care about that 100MB attachment mbox would have > to rewrite over and over. I prefer to not know _almost_ entir
Re: [DNG] Devuan AMI
Quoting Olaf Meeuwissen via Dng (dng@lists.dyne.org): > Hi Steve, list, All: OH HAI! > On more than one occasion I've found that some acronym "flashers" are > just wildly flapping arms and waving hands in thin air trying to make an > impresssion rather than "knowledgeable experts". Anyone serious about > trying to get something across to an audience whose knowledge level is > not known a priori would spell it out first time around (with the > acronym in parentheses) *or* provide a link to a (wikipedia?) page > explaining the thing. I appreciate not having to deploy radar (RAdio Detection And Ranging) to find your meaning. But would you mind explaining that again using a laser (Light Amplification by Stimulated Emission of Radiation) pointer? Goodbye (god be with ye), Rick M. Etc. (et cetera). Please excuse me, I believe I need to walk around a pram (perambulator) in order to board my bus (short for omnibus, meaning to or for, by, with, or from everybody - which is a very good description, as Michael Flanders said).[1] [1] https://www.elyrics.net/read/f/flanders-&-swann-lyrics/a-transport-of-delight-lyrics.html ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] calendars, contacts, to do lists
On 5/23/19 7:52 PM, Rick Moen wrote: Quoting Hendrik Boom (hend...@topoi.pooq.com): Radicale does look good. The one thing I haven't found is sync with Google calendar. It's mentioned over and over that Google doesn't talk CalDAV. Talk about "not doing evil." They USED to talk CalDAV. Microsoft Exchange still does. Go figure. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] systemd Clocks In At More Than 1.2 Million Lines
https://phoronix.com/scan.php?page=news_item&px=Systemd-1.2-Million I will write you a whole operating system with such a number of code lines! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Linux system can be brought down by sending SIGILL to Systemd
Hi! Today in a Linux training a participant attempted to bring down Debian workstation with Systemd by sending signals to PID 1 as I invited them to try to bring down PID 1 while thinking for myself that this would not be possible from my past experiences about trying to bring down PID 1 – init – myself. While sending SIGKILL to Systemd did not have any effect, sending SIGILL – illegal instruction – to it brought the machine to an halt. I reproduced it with while true; do kill -ILL 1 ; echo -n "." ; sleep 0.5 ; done on my training workstation (Debian 9.9 with Systemd 232 and 4.9.0-9 Debian Kernel with MDS mitigation). The mouse pointer froze and the machine did not even respond to ping anymore! According to participants about 4 to 5 times sending the signal would be enough to bring down a workstation with Systemd as PID 1. Despite all the bugs and issues I have seen or read about with Systemd I was very surprised about that result. Curiously I attempted the same with the Debian on my laptop that I switched to SysVInit and elogind. As the elogind stuff mostly works I think I will switch it to Devuan once I come around to it. I am able to run while true; do kill -ILL 1 ; echo -n "." ; done against SysVinit's "init" process without any issue for minutes (Debian Sid with sysvinit 2.93-8 and self-compiled 5.1.2 kernel, also with MDS mitigation). It is even running while I write this mail normally now. Also the participants found in the manpage kill(2): NOTES The only signals that can be sent to process ID 1, the init process, are those for which init has explicitly installed sig‐ nal handlers. This is done to assure the system is not brought down accidentally. So if that is actually true, then it appears that Systemd initiates a signal handler for SIGILL for whatever reason. I pondered about writing a bug report to Systemd developers, but honestly from my past experiences with upstream feedback about bug reports regarding Systemd I then decided not to bother about it. I am not willing to take in and deal with any more "this is by design, go away" or "this works as intended, go away" kind of responses. I am not interested in Systemd to a larger extent than teaching participants of my training what they need to know about it, when they have to deal with it due to distribution choices made at their employer. And yes, I also have a slide that summarizes critique about it, complete with links, so they can make up their own opinion. And no, for me it is not black and white, but my own decision is to go without Systemd. This is another reason for me to start to provide Devuan VMs in the Proxmox VE environment I use to provide VMs of various distributions to the participants of my trainings. So participants can have a look at it and do exercises with it if they like. I already started to incorporate information about Devuan in some of my slides. I share it here not to invite another bashing about Systemd, we really do not need to go there, but instead can focus on strengthening the alternatives. But I share it here to provide another reason to use a Systemd-free distribution like Devuan. I also share it as an example of the robustness of the SysVInit init process! Thanks, -- Martin ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Linux system can be brought down by sending SIGILL to Systemd
Quoting Martin Steigerwald (mar...@lichtvoll.de): [...] > While sending SIGKILL to Systemd did not have any effect, sending SIGILL > – illegal instruction – to it brought the machine to an halt. I > reproduced it with > > while true; do kill -ILL 1 ; echo -n "." ; sleep 0.5 ; done [...] OMG, that's both sad and hilarious. The jokes about systemd being ILL almost tell themselves. -- Rick Moen "The race is not to the swift, nor the battle r...@linuxmafia.com to the strong..., but that's the way to bet." McQ! (4x80) -- Damon Runyon, riffing off Ecclesiastes 9:11 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Linux system can be brought down by sending SIGILL to Systemd
[correcting unexplained departure into offlist personal mail, by forwarding back onlist.] Quoting John Hughes (j...@atlantech.com): > So, what we learn from this exercise is that on Unix derived systems root can > crash the system, an unexpected result, no? If my system crashed four of the five times I accidentally asked kill(8) to generate a non-existent signal type, personally, I'd consider that highly undesirable behaviour. It's tantamount to 'I'm sorry, you have no right to be dissatisifed that your system suddenly fell over just because you sneezed: You were UID 0 at the time.' That chain of reasoning actually doesn't work for me. Your understanding of acceptable root-user system semantics may Differ A Lot.[tm] OK with me, if so. Dad used to say, 'Life is anthopology.' ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] wireless bobbles (was: system can be brought down by sending SIGILL to Systemd
Rob is Good People. (So is Sarah.) I have no idea if either or both of them is on Dng. - Forwarded message from Rob Landley - Date: Fri, 24 May 2019 18:44:46 -0500 From: Rob Landley To: Sarah Newman , Rick Moen , sv...@lists.svlug.org Subject: Re: [svlug] (forw) [DNG] Linux system can be brought down by sending SIGILL to Systemd On 5/24/19 6:18 PM, Sarah Newman wrote: > On 5/24/19 2:04 PM, Rick Moen wrote: > >> - Forwarded message from Martin Steigerwald - > >> >> This is another reason for me to start to provide Devuan VMs in the >> Proxmox VE environment I use to provide VMs of various distributions to >> the participants of my trainings. So participants can have a look at it >> and do exercises with it if they like. I already started to incorporate >> information about Devuan in some of my slides. > > > Anyone have opinions on whether Devuan worth it compared to just removing > systemd? We make Debian images without systemd (except for udev, udev is > still systemd) and they work. I moved from xubuntu 14.04 to devuan ascii a month or so back and it's... fine? It's debian. I have the usual complaints and bugs and weird version skew moving from one distro to another, but red hat -> knoppix -> fedora -> ubuntu -> xubuntu (and I'm probably missing at least one) means that's totally not a new thing. (Plus needing to use RHELL and SLES and such at work over the years.) I want to set their wireless network manager gui thing on fire (it remembers the network access point password I typed in during system setup, but none of the ones since ever save, nor does the "autoconnect" button; and of couse half the time it doesn't notice wireless has changed until I open the gui, and if I open the gui at the university it times out enumerating access points and the window stays blank _forever_). But then I wanted to set networkmangler on fire for most of a decade too. Apparently parsing the output if iwlist is hard for gui people to wrap their heads around. Rob - End forwarded message - ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Linux system can be brought down by sending SIGILL to Systemd
Hi Martin, Perhaps Proxmox could ship running Devuan one day? *wink,nudge* ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] New VPN instructions using tinc
Hi all, I just posted a “Hello World” instruction set for creating a VPN (Virtual Private Network) with the tinc VPN tool. Tinc is one of the simplest VPN tools: Simple enough that it has nor needs a GUI design tool. Make a few directories, edit a few config files, and you have a VPN. These instructions are at: http://troubleshooters.com/linux/tinc/hello_peer.htm This document is written for the person unfamiliar with VPNs. It has plenty of explanation plus a little redundancy to unambiguously guide the reader the VPN newbie in setting up a tinc peer to peer VPN. So please recommend this resource to your friends who aren't yet familiar with how VPNs work. Thanks, SteveT Steve Litt June 2019 featured book: Thriving in Tough Times http://www.troubleshooters.com/thrive ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Linux system can be brought down by sending SIGILL to Systemd
Hi, Rick Moen writes: > Quoting Martin Steigerwald (mar...@lichtvoll.de): > > [...] >> While sending SIGKILL to Systemd did not have any effect, sending SIGILL >> – illegal instruction – to it brought the machine to an halt. I >> reproduced it with >> >> while true; do kill -ILL 1 ; echo -n "." ; sleep 0.5 ; done > [...] > > OMG, that's both sad and hilarious. > > The jokes about systemd being ILL almost tell themselves. And the systemd fan-folk will be complaining about ILL will, no doubt. -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
