>> I promise you, people ARE using date -d '...' in shell scripts.
>> LOTS of people. Hell, I've done it.(*)
The Java Gregorian Calendar class was a delightful piece of software
when I last used it (15 or so years ago). It does know the difference
between the Julian and Gregorian calendars, among
On Tue, Feb 6, 2018 at 6:17 AM, Jonathan de Boyne Pollard wrote:
> Tangentially to that, it seems that someone needs to pick up the dropped
> baton and update the pictures.
Those are all copies of a diagram by Claudio Filho, if anyone updates
it, please send him a pull request to update the offic
On 06/02/18 18:38, Erik Christiansen wrote:
> Perl is the quintessential write-only language, which with a bit of luck
> will die out before it catches on
Now you're getting to fighting talk ... :-)
Richard
signature.asc
Description: OpenPGP digital signature
_
_ Cliquez ici pour vous inscrire ou inviter vos amis à s'inscrire à
la Newsletter de Bertrand Canavy en leur transférant cet email
[http://links.learnymail.fr/c/i5_/F2Rb/T1rfnJt6dhPF0UBDkwI_Ey/mzY/LySD/60515edb
Bonjour
Chère Lectrice, Cher Lecteur,
CONSTATEZ VOS DÉSÉQUILIBRES MÉTABOL
On 05.02.18 10:02, Michael Stone wrote:
> IIRC it started out as a YACC function in the late 80s, and is now a Bison
> (YACC+GNU extensions) library.
In that case it has a precise grammar, expressed in BNF (Backus Naur
Form), though the lexer (I've always used lex together with
yacc/bison) could a
On 2018-02-05 at 13:47, Brian wrote:
> On Mon 05 Feb 2018 at 10:24:14 -0500, The Wanderer wrote:
>> If there's an ongoing discussion on that mailing list, and one of
>> the participants wants to draw in a third person who also
>> subscribes, it's entirely appropriate to CC a reply to that third
>
Richard Hector writes:
> On 06/02/18 02:11, Vincent Lefevre wrote:
> > On 2018-02-05 01:53:02 +1300, Richard Hector wrote:
> > You should set up a "Mail-Followup-To:" for that.
For reference, this refers to one of two proposed (but never
standardised) fields “Mail-Followup-To” and “Mail-Reply-To
On 06/02/18 15:45, Michael Stone wrote:
>> ... and how do you deal with locales that have changed definition over
>> time? What was the country code for (eg) Prussia in 1752? It just gets
>> painful ...
>
> Yes, this is more a novelty than anything. Even apart from changing
> national borders, thi
On Tue, Feb 06, 2018 at 03:36:53PM +1300, Richard Hector wrote:
On 06/02/18 15:24, Michael Stone wrote:
On Tue, Feb 06, 2018 at 12:32:06PM +1100, Erik Christiansen wrote:
And for the far past, cal is superior; compare:
$ cal -3 9 1752
August 1752 September 1752 October 1752
On 06/02/18 15:24, Michael Stone wrote:
> On Tue, Feb 06, 2018 at 12:32:06PM +1100, Erik Christiansen wrote:
>> And for the far past, cal is superior; compare:
>>
>> $ cal -3 9 1752
>> August 1752 September 1752 October 1752
>> Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo T
On Mon, Feb 05, 2018 at 08:13:10PM -0600, David Wright wrote:
But how would you deal with the simplest (to express) problem of all,
that of
$ date -d 1/2/18
Tue Jan 2 00:00:00 CST 2018
$
which would mean a battery of locale-specific rules.
Yup. You'd need to accept something (probably iso860
On Tue, Feb 06, 2018 at 12:32:06PM +1100, Erik Christiansen wrote:
And for the far past, cal is superior; compare:
$ cal -3 9 1752
August 1752 September 1752 October 1752
Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa
1 1 2 14 15 1
On Tue 06 Feb 2018 at 12:32:06 (+1100), Erik Christiansen wrote:
> On 05.02.18 09:39, Greg Wooledge wrote:
> > On Sun, Feb 04, 2018 at 04:04:34PM +0100, Nicolas George wrote:
> > > All you describe is convenience for programmatic use. As I explained,
> > > this parser is meant for interactive use.
On Mon 05 Feb 2018 at 23:39:30 (+), Brian wrote:
> On Mon 05 Feb 2018 at 15:42:32 -0600, David Wright wrote:
>
> > On Mon 05 Feb 2018 at 19:37:45 (+), Brian wrote:
> > > On Mon 05 Feb 2018 at 13:12:45 -0600, David Wright wrote:
> > >
> > > > On Mon 05 Feb 2018 at 18:01:08 (+), Brian w
On 06/02/18 02:11, Vincent Lefevre wrote:
> On 2018-02-05 01:53:02 +1300, Richard Hector wrote:
>> On 05/02/18 01:44, Nicolas George wrote:
PS - please don't cc me; I'm on the list.
>>> Done this once, but I cannot promise I will think of it later. Document
>>> your preference in your mail mai
On 05.02.18 09:39, Greg Wooledge wrote:
> On Sun, Feb 04, 2018 at 04:04:34PM +0100, Nicolas George wrote:
> > All you describe is convenience for programmatic use. As I explained,
> > this parser is meant for interactive use.
>
> What on EARTH made you think THAT?
The fuzzy grammar of the date st
On Mon 05 Feb 2018 at 23:20:13 (+), Brian wrote:
> On Mon 05 Feb 2018 at 15:45:54 -0600, David Wright wrote:
>
> > On Mon 05 Feb 2018 at 20:26:46 (+), Brian wrote:
> > > On Mon 05 Feb 2018 at 13:13:18 -0600, David Wright wrote:
> > >
> > > > On Mon 05 Feb 2018 at 18:06:34 (+), Brian w
On Mon 05 Feb 2018 at 17:07:35 (-0500), Greg Wooledge wrote:
> > > Received: from david by alum with local (Exim 4.80)
> > > (envelope-from )
> > > id 1eimCc-EV-Nv; Mon, 05 Feb 2018 13:13:18 -0600
>
> > Is that meant to tell me something (as you wrote "but")?
>
> Without knowi
Michael Stone:
Anyway, if there was a simple solution someone would have implemented
it by now.
Indeed, that is the case; and it has been around for almost as long as
those 20 years that you have been watching people use the GNU tool. In
2001, Paul Jarc invented a fairly simple notation for
On Mon 05 Feb 2018 at 15:42:32 -0600, David Wright wrote:
> On Mon 05 Feb 2018 at 19:37:45 (+), Brian wrote:
> > On Mon 05 Feb 2018 at 13:12:45 -0600, David Wright wrote:
> >
> > > On Mon 05 Feb 2018 at 18:01:08 (+), Brian wrote:
> > > >
> > > > Now you have problems (or could have). The
On Mon 05 Feb 2018 at 15:45:54 -0600, David Wright wrote:
> On Mon 05 Feb 2018 at 20:26:46 (+), Brian wrote:
> > On Mon 05 Feb 2018 at 13:13:18 -0600, David Wright wrote:
> >
> > > On Mon 05 Feb 2018 at 18:06:34 (+), Brian wrote:
> > > > On Mon 05 Feb 2018 at 12:53:36 -0500, Greg Wooledge
rhkramer:
Intentionally cross posted. Aside: For those on the debian-user lists,
the thread came from the debian-backports list, but my frustration
should probably be expressed more to the debian-user list (or
debian-developer list, assuming there is such a list (to which I am
not subscribed)
> > Received: from david by alum with local (Exim 4.80)
> > (envelope-from )
> > id 1eimCc-EV-Nv; Mon, 05 Feb 2018 13:13:18 -0600
> Is that meant to tell me something (as you wrote "but")?
Without knowing exactly what piece Brian was focusing on, I can at
least point out that
On Mon 05 Feb 2018 at 20:26:46 (+), Brian wrote:
> On Mon 05 Feb 2018 at 13:13:18 -0600, David Wright wrote:
>
> > On Mon 05 Feb 2018 at 18:06:34 (+), Brian wrote:
> > > On Mon 05 Feb 2018 at 12:53:36 -0500, Greg Wooledge wrote:
> > >
> > > > On Mon, Feb 05, 2018 at 05:31:29PM +, Bria
On Mon 05 Feb 2018 at 19:37:45 (+), Brian wrote:
> On Mon 05 Feb 2018 at 13:12:45 -0600, David Wright wrote:
>
> > On Mon 05 Feb 2018 at 18:01:08 (+), Brian wrote:
> > >
> > > Now you have problems (or could have). The first problem is that the
> > > "duplicates" are not duplicates becaus
On 06/02/18 04:52, Stephen P. Molnar wrote:
I installed memtest86+ and ran it with all of the defaults. It took
over an hour, but no errors were reported.
Please try parallel memtester and stress. These found memory errors for
me that were not found by memtest86+.
In *eight* terminal window
On 06/02/18 07:32, David Wright wrote:
I'm not in the habit of upgrading BIOS/UEFI on my computers.
(I do have {amd64,intel}-microcode installed.) What old or
buggy code would I be running when booting a linux installation?
(I accept that Grub has to run, and the kernel and initramfs be
found, in
On Mon 05 Feb 2018 at 13:13:18 -0600, David Wright wrote:
> On Mon 05 Feb 2018 at 18:06:34 (+), Brian wrote:
> > On Mon 05 Feb 2018 at 12:53:36 -0500, Greg Wooledge wrote:
> >
> > > On Mon, Feb 05, 2018 at 05:31:29PM +, Brian wrote:
> > > > AfAIK. there isn't any way to determine whether
On Mon 05 Feb 2018 at 13:18:29 -0600, David Wright wrote:
> On Mon 05 Feb 2018 at 19:00:16 (+), Brian wrote:
> > On Mon 05 Feb 2018 at 08:32:32 -0600, David Wright wrote:
> >
> > > If it really worries you, the answer might be ~/.procmailrc and
> > >
> > > :0 Wh: $HOME/msgid.lock
> > > | for
On Mon 05 Feb 2018 at 13:12:45 -0600, David Wright wrote:
> On Mon 05 Feb 2018 at 18:01:08 (+), Brian wrote:
> >
> > Now you have problems (or could have). The first problem is that the
> > "duplicates" are not duplicates because the headers are different. The
> > second problem is - which on
On Mon 05 Feb 2018 at 19:00:16 (+), Brian wrote:
> On Mon 05 Feb 2018 at 08:32:32 -0600, David Wright wrote:
>
> > If it really worries you, the answer might be ~/.procmailrc and
> >
> > :0 Wh: $HOME/msgid.lock
> > | formail -D 19 $HOME/msgid.cache
> >
> > I used it for years.
>
> So ha
On Mon 05 Feb 2018 at 18:06:34 (+), Brian wrote:
> On Mon 05 Feb 2018 at 12:53:36 -0500, Greg Wooledge wrote:
>
> > On Mon, Feb 05, 2018 at 05:31:29PM +, Brian wrote:
> > > AfAIK. there isn't any way to determine whether a message posted to
> > > -user is from a non-subscriber.
> >
> > I
On Mon 05 Feb 2018 at 18:01:08 (+), Brian wrote:
> On Mon 05 Feb 2018 at 16:09:11 +0100, to...@tuxteam.de wrote:
>
> > On Mon, Feb 05, 2018 at 09:44:43AM -0500, The Wanderer wrote:
> > > On 2018-02-05 at 09:32, David Wright wrote:
> >
> > [...]
> >
> > > > :0 Wh: $HOME/msgid.lock
> > > > | f
On Mon, 2018-02-05 at 19:40 +0100, Felipe Salvador wrote:
> On Sun, Feb 04, 2018 at 11:06:21PM -0200, Henrique de Moraes Holschuh
> wrote:
> > On Sun, 04 Feb 2018, Stephen P. Molnar wrote:
> > > I am running Debian Stretch on am eight thread AMD GPU platform.
> > > Lately, it seems if I have been p
On Mon 05 Feb 2018 at 08:32:32 -0600, David Wright wrote:
> If it really worries you, the answer might be ~/.procmailrc and
>
> :0 Wh: $HOME/msgid.lock
> | formail -D 19 $HOME/msgid.cache
>
> I used it for years.
So has Microsoft in Exchange. They use it to delete a user's mails
silently. E
On Mon 05 Feb 2018 at 10:24:14 -0500, The Wanderer wrote:
> On 2018-02-05 at 10:09, to...@tuxteam.de wrote:
>
> > On Mon, Feb 05, 2018 at 09:44:43AM -0500, The Wanderer wrote:
> >
> >> On 2018-02-05 at 09:32, David Wright wrote:
> >
> > [...]
> >
> >> > :0 Wh: $HOME/msgid.lock
> >> > | formail
On Monday, February 05, 2018 10:02:50 AM Michael Stone wrote:
> On Mon, Feb 05, 2018 at 09:11:23AM -0500, rhkra...@gmail.com wrote:
> >I assume (I know) that the license for date is some free / open source
> >license that would allow you to incorporate the old code into a new
> >function (probably
On Sun, Feb 04, 2018 at 11:06:21PM -0200, Henrique de Moraes Holschuh wrote:
> On Sun, 04 Feb 2018, Stephen P. Molnar wrote:
> > I am running Debian Stretch on am eight thread AMD GPU platform.
> > Lately, it seems if I have been plagued by surfeit of orphaned nodes.
>
> That means:
>
> 1. "unlin
Thanks
On Monday, February 05, 2018 09:46:54 AM Greg Wooledge wrote:
> No need to guess. You can ask it.
>
> wooledg:~$ date --version
On Mon 05 Feb 2018 at 14:45:17 (-0200), Henrique de Moraes Holschuh wrote:
> On Mon, 05 Feb 2018, Stephen P. Molnar wrote:
> > I am rather hesitant about updating the BIOS/UFEI. In fact I can't
> > seem to find an upgrade for the FX-8320 on the AMD web site.
>
> An update, if any are available,
On Mon 05 Feb 2018 at 12:53:36 -0500, Greg Wooledge wrote:
> On Mon, Feb 05, 2018 at 05:31:29PM +, Brian wrote:
> > AfAIK. there isn't any way to determine whether a message posted to
> > -user is from a non-subscriber.
>
> I believe some people are using the one of the X-Spam* headers
> and
On 2/4/18, Henrique de Moraes Holschuh wrote:
> On Sun, 04 Feb 2018, Stephen P. Molnar wrote:
>> I am running Debian Stretch on am eight thread AMD GPU platform.
>> Lately, it seems if I have been plagued by surfeit of orphaned nodes.
>
> That means:
>
> 1. "unlinked" files or directories were sti
On Mon 05 Feb 2018 at 16:09:11 +0100, to...@tuxteam.de wrote:
> On Mon, Feb 05, 2018 at 09:44:43AM -0500, The Wanderer wrote:
> > On 2018-02-05 at 09:32, David Wright wrote:
>
> [...]
>
> > > :0 Wh: $HOME/msgid.lock
> > > | formail -D 19 $HOME/msgid.cache
> > >
> > > I used it for years.
>
On Mon, Feb 05, 2018 at 05:31:29PM +, Brian wrote:
> AfAIK. there isn't any way to determine whether a message posted to
> -user is from a non-subscriber.
I believe some people are using the one of the X-Spam* headers
and looking for the LDOSUBSCRIBER substring. Which is extremely
non-obvious
On Mon 05 Feb 2018 at 09:41:20 -0500, The Wanderer wrote:
> On 2018-02-05 at 08:58, Vincent Lefevre wrote:
>
> > On 2018-02-05 08:40:27 -0500, The Wanderer wrote:
> >
> >> On 2018-02-05 at 08:11, Vincent Lefevre wrote:
>
> >>> You should set up a "Mail-Followup-To:" for that. This is
> >>> enti
Stephen P. Molnar:
>
> I installed memtest86+ and ran it with all of the defaults. It took
> over an hour, but no errors were reported.
That's not long enough. From what I have read you should let it run for
a day or so and even then you cannot be sure that there are no memory
errors.
> I am ra
On Mon, 05 Feb 2018, Stephen P. Molnar wrote:
> I installed memtest86+ and ran it with all of the defaults. It took
> over an hour, but no errors were reported.
Memtest86 and memtest86+ are not always that good at finding memory
errors for some reason... Try a 24h/48h test over the weekend or
so
Hi.
On Mon, Feb 05, 2018 at 04:04:37PM +0100, Harald Dunkel wrote:
> Hi Reco,
>
> you mean this is a known issue???
Well, it's known to me (since then) at least as I merely read the
contents of /lib/lsb/init-functions in my Debian system.
Pinpointing the problem is easy, anyone who has a
Erkko Lahnajärvi schreef op 2018-02-05 15:49:
Hi,
I fetched a new computer few days ago. The equipment are:
Motherboard: Gigabyte AB350-Gaming
CPU: Amd Ryzen 3 1300x
RAM: 16Gb
Video card: GeForce GTX 1050 Ti
Hard disk: WD green 240 Gb
On this computer I installed Debian-9.3.0-amd64.
I've first
On Mon, 2018-02-05 at 10:15 +1300, Ben Caradoc-Davies wrote:
> On 05/02/18 09:49, Stephen P. Molnar wrote:
> > They seem to happen when I am
> > running four or more apps at the same time.
>
> I would never expect to see orphaned inodes except after a system
> crash
> or kernel memory corruption
On Sun, 2018-02-04 at 23:06 -0200, Henrique de Moraes Holschuh wrote:
> On Sun, 04 Feb 2018, Stephen P. Molnar wrote:
> > I am running Debian Stretch on am eight thread AMD GPU platform.
> > Lately, it seems if I have been plagued by surfeit of orphaned
> > nodes.
>
> That means:
>
> 1. "unlinked
On Mon, 2018-02-05 at 08:03 +0900, Mark Fletcher wrote:
> On Sun, Feb 04, 2018 at 03:49:36PM -0500, Stephen P. Molnar wrote:
> > I am running Debian Stretch on am eight thread AMD GPU platform.
> > Lately, it seems if I have been plagued by surfeit of orphaned
> > nodes.
> >
> > I have goggled the
On 2018-02-05 at 10:09, to...@tuxteam.de wrote:
> On Mon, Feb 05, 2018 at 09:44:43AM -0500, The Wanderer wrote:
>
>> On 2018-02-05 at 09:32, David Wright wrote:
>
> [...]
>
>> > :0 Wh: $HOME/msgid.lock
>> > | formail -D 19 $HOME/msgid.cache
>> >
>> > I used it for years.
>
>> I don't parse
On Sun, 2018-02-04 at 20:45 -0500, Gene Heskett wrote:
> On Sunday 04 February 2018 15:49:36 Stephen P. Molnar wrote:
>
> > I am running Debian Stretch on am eight thread AMD GPU platform.
> > Lately, it seems if I have been plagued by surfeit of orphaned
> nodes.
> >
> > I have goggled the causes
On Mon, 2018-02-05 at 07:37 +0100, deloptes wrote:
> Stephen P. Molnar wrote:
>
> > Can anyone give me some guidance in what I should be looking
> > for? It
> > would be much appreciated.
> > From my experience most probably inappropriate shutdown (no unmount
> > when
>
> shutdown).
> How do you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Feb 05, 2018 at 09:44:43AM -0500, The Wanderer wrote:
> On 2018-02-05 at 09:32, David Wright wrote:
[...]
> > :0 Wh: $HOME/msgid.lock
> > | formail -D 19 $HOME/msgid.cache
> >
> > I used it for years.
>
> I don't parse this well enough
Hi,
I fetched a new computer few days ago. The equipment are:
Motherboard: Gigabyte AB350-Gaming
CPU: Amd Ryzen 3 1300x
RAM: 16Gb
Video card: GeForce GTX 1050 Ti
Hard disk: WD green 240 Gb
On this computer I installed Debian-9.3.0-amd64.
I've first tried to install the video card. I found a par
Hi Reco,
you mean this is a known issue???
Harri
On Mon, Feb 05, 2018 at 09:11:23AM -0500, rhkra...@gmail.com wrote:
I assume (I know) that the license for date is some free / open source license
that would allow you to incorporate the old code into a new function (probably
with appropriate citation / credit) and then add / modify / delete code
On Mon, Feb 05, 2018 at 09:11:23AM -0500, rhkra...@gmail.com wrote:
> I assume (I know) that the license for date is some free / open source
> license
No need to guess. You can ask it.
wooledg:~$ date --version
date (GNU coreutils) 8.26
Copyright (C) 2016 Free Software Foundation, Inc.
License
On 2018-02-05 at 09:32, David Wright wrote:
> On Mon 05 Feb 2018 at 08:40:27 (-0500), The Wanderer wrote:
>
>> On 2018-02-05 at 08:11, Vincent Lefevre wrote:
>>> You should set up a "Mail-Followup-To:" for that. This is
>>> entirely your problem.
>>
>> That does seem to be the trend and positio
On 2018-02-05 at 08:58, Vincent Lefevre wrote:
> On 2018-02-05 08:40:27 -0500, The Wanderer wrote:
>
>> On 2018-02-05 at 08:11, Vincent Lefevre wrote:
>>> You should set up a "Mail-Followup-To:" for that. This is
>>> entirely your problem.
>>
>> That does seem to be the trend and position of th
On Sun, Feb 04, 2018 at 04:04:34PM +0100, Nicolas George wrote:
> All you describe is convenience for programmatic use. As I explained,
> this parser is meant for interactive use.
What on EARTH made you think THAT?
I promise you, people ARE using date -d '...' in shell scripts.
LOTS of people. H
On Mon 05 Feb 2018 at 08:40:27 (-0500), The Wanderer wrote:
> On 2018-02-05 at 08:11, Vincent Lefevre wrote:
>
> > On 2018-02-05 01:53:02 +1300, Richard Hector wrote:
> >
> >> On 05/02/18 01:44, Nicolas George wrote:
>
> >>> Done this once, but I cannot promise I will think of it later.
> >>> Do
On Monday, February 05, 2018 08:07:47 AM Vincent Lefevre wrote:
> On 2018-02-04 08:22:23 -0500, Michael Stone wrote:
> > On Mon, Feb 05, 2018 at 12:48:45AM +1300, Richard Hector wrote:
> > > In which case, it should refuse to accept '4/2/2018' at all, right?
> >
> > It can't, that would break work
On 2018-02-05 08:40:27 -0500, The Wanderer wrote:
> On 2018-02-05 at 08:11, Vincent Lefevre wrote:
> > On 2018-02-05 01:53:02 +1300, Richard Hector wrote:
> >> My preference is for any personal replies addressed to me to go to
> >> me, and I'd use the Reply-to header (as intended) if I needed it to
On 2018-02-05, Roberto C Sánchez wrote:
>>
>> It is not rare that the behavior of utilities change and break
>> scripts. So, why not here, in particular for a good reason?
>>
> It is equally common, perhaps even more so, that buggy behavior is
> retained (especially if it is not harmful) and th
On 2018-02-05 at 08:11, Vincent Lefevre wrote:
> On 2018-02-05 01:53:02 +1300, Richard Hector wrote:
>
>> On 05/02/18 01:44, Nicolas George wrote:
>>> Done this once, but I cannot promise I will think of it later.
>>> Document your preference in your mail mail header, the standard
>>> way, so th
On 2018-02-05 08:12:21 -0500, Roberto C. Sánchez wrote:
> On Mon, Feb 05, 2018 at 02:07:47PM +0100, Vincent Lefevre wrote:
> > On 2018-02-04 08:22:23 -0500, Michael Stone wrote:
> > > On Mon, Feb 05, 2018 at 12:48:45AM +1300, Richard Hector wrote:
> > > > In which case, it should refuse to accept '
On 2018-02-05, Henrique de Moraes Holschuh wrote:
> On Mon, 05 Feb 2018, Curt wrote:
>> At every shutdown; looks like another oldie but goodie bug affecting
>> those with encrypted swap (maybe some kind or race condition, if that is
>> indeed the proper term).
>
> Incorrect sequencing, actually.
On Mon, Feb 05, 2018 at 02:07:47PM +0100, Vincent Lefevre wrote:
> On 2018-02-04 08:22:23 -0500, Michael Stone wrote:
> > On Mon, Feb 05, 2018 at 12:48:45AM +1300, Richard Hector wrote:
> > > In which case, it should refuse to accept '4/2/2018' at all, right?
> >
> > It can't, that would break wor
On 2018-02-05 01:53:02 +1300, Richard Hector wrote:
> On 05/02/18 01:44, Nicolas George wrote:
> >> PS - please don't cc me; I'm on the list.
> > Done this once, but I cannot promise I will think of it later. Document
> > your preference in your mail mail header, the standard way, so that it
> > is
On 2018-02-04 08:22:23 -0500, Michael Stone wrote:
> On Mon, Feb 05, 2018 at 12:48:45AM +1300, Richard Hector wrote:
> > In which case, it should refuse to accept '4/2/2018' at all, right?
>
> It can't, that would break working scripts. This is the heart of the
> problem: we know the parser is hor
On Mon, 05 Feb 2018, Curt wrote:
> At every shutdown; looks like another oldie but goodie bug affecting
> those with encrypted swap (maybe some kind or race condition, if that is
> indeed the proper term).
Incorrect sequencing, actually. But if this is ephemeral swap (or
ephemeral *anything*), it
Failed "Stopped (with error) /dev/dm-0"
At every shutdown; looks like another oldie but goodie bug affecting
those with encrypted swap (maybe some kind or race condition, if that is
indeed the proper term).
Having said that, filesystems are unmounted cleanly (no fsck at reboot,
although the shut
75 matches
Mail list logo
