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 shutdown your machine?
Can you try without systemd (just install sysvinit a
On 2/4/18 12:49 PM, Stephen P. Molnar wrote:
receiving warning messages from the OS,
Please post the warning messages from the OS, and identify where they
are coming from.
Please run 'mount' and post the prompt, the command, and the relevant
portions of the output. Please do the same for
On 2018-02-04 at 20:06, 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 dir
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. cures and prevention, but have gotten no
> results that make any se
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 still open when the filesystem
had to be shutdown/made re
On 4 February 2018 at 22:50, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:
>
>
> On 4 February 2018 at 15:20, Andy Smith wrote:
>
>> Hi Michael,
>>
>> On Sat, Feb 03, 2018 at 11:44:39PM +, Michael Fothergill wrote:
>> > On 3 February 2018 at 23:14, Andy Smith wrote:
>> > > If you
On 4 February 2018 at 15:20, Andy Smith wrote:
> Hi Michael,
>
> On Sat, Feb 03, 2018 at 11:44:39PM +, Michael Fothergill wrote:
> > On 3 February 2018 at 23:14, Andy Smith wrote:
> > > If you want to make genuine constructive suggestions for how things
> > > could be improved, I think you s
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 causes. cures and prevention, but have gotten no
> results that make
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. How did you test your CPU and RAM? Do you
see any other symptoms such as
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. cures and prevention, but have gotten no
results that make any sense to me. I've been using computer since the
early 1960's but am an or
Hello,
I would like to open a LUKS container (which is the OS Debian) through
GRUB, but with the header stored in a USB key for example. Through the
file crypttab
(https://manpages.debian.org/stretch/cryptsetup/crypttab.5.en.html), it
seems possible to specify the path of the header, but I h
On Sun, Feb 04, 2018 at 06:45:16PM +0100, Nicolas George wrote:
David Wright (2018-02-04):
$ TZ=London date
Sun Feb 4 17:17:56 London 2018
$ TZ=UtterNonsense date
Sun Feb 4 17:44:00 UtterNonsense 2018
The fact that it printed the name you put and not the official name of
the time zone shows
On Sun 04 Feb 2018 at 18:45:16 (+0100), Nicolas George wrote:
> David Wright (2018-02-04):
> > $ TZ=London date
> > Sun Feb 4 17:17:56 London 2018
>
> $ TZ=UtterNonsense date
> Sun Feb 4 17:44:00 UtterNonsense 2018
>
> The fact that it printed the name you put and not the official name of
> the
David Wright (2018-02-04):
> $ TZ=London date
> Sun Feb 4 17:17:56 London 2018
$ TZ=UtterNonsense date
Sun Feb 4 17:44:00 UtterNonsense 2018
The fact that it printed the name you put and not the official name of
the time zone shows that the value is invalid. The correct value would
have been:
On Sun 04 Feb 2018 at 17:44:54 (+0100), Thomas Schmitt wrote:
> Hi,
>
> Mike Stone wrote:
> > So it must be that "first tuesday" means
> > the first tuesday in the month, but "second tuesday" sadly means the first
> > tuesday plus one second because "second" has more than one meaning and I
> > wan
On Sun 04 Feb 2018 at 14:39:44 (+0100), Thomas Schmitt wrote:
> Hi,
>
> Richard Hector wrote:
> > Incidentally, the gnu 'Date input formats' link above does talk about
> > only accepting English names for days and months, but doesn't say
> > anything about the ordering of day and month (except, un
Hi,
Mike Stone wrote:
> So it must be that "first tuesday" means
> the first tuesday in the month, but "second tuesday" sadly means the first
> tuesday plus one second because "second" has more than one meaning and I
> wanted the other one.
This illustrates the fundamental problem with natural en
On Sun, Feb 04, 2018 at 05:00:14PM +0100, Nicolas George wrote:
Anyway, if you propose to remove the ability to write something like
"2017-12-04 + 73 days", I veto as strongly as I can.
The above is a very restricted subset of the date(1) grammar. Your
confusion seems to stem from the fact tha
Michael Stone (2018-02-04):
> Again, 20 years of dealing with people actually having trouble with this.
> I'm really not making this up.
Ok. Then please let me tell you that you have an observation bias: as (I
suppose) a maintainer of the package, you have to deal with people who
have a problem, b
On Sun, Feb 04, 2018 at 04:54:07PM +0100, Nicolas George wrote:
I hope you enjoy the warmth of the burning straw men. Good day.
Again, 20 years of dealing with people actually having trouble with
this. I'm really not making this up.
Mike Stone
Michael Stone (2018-02-04):
> Heck, let's try some natural language right now:
I hope you enjoy the warmth of the burning straw men. Good day.
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
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. For interactive use,
flexibility and natural language are a convenience.
And you keep ignoring the fact that actual hum
Hi Michael,
On Sat, Feb 03, 2018 at 11:44:39PM +, Michael Fothergill wrote:
> On 3 February 2018 at 23:14, Andy Smith wrote:
> > If you want to make genuine constructive suggestions for how things
> > could be improved, I think you should start by identifying what
> > exactly the deficiencies
Michael Stone (2018-02-04):
> Well, it's not particularly convenient for people to have to constantly
> wonder why the parser isn't doing what they think it should do. I've been
> getting the questions and bug reports for 20 years, so trust me when I say
> that people have trouble predicting the ou
On Sun, Feb 04, 2018 at 02:27:00PM +0100, Nicolas George wrote:
Michael Stone (2018-02-04):
But a better parser would allow the same functionality, without being
confusing, inconsistent, and hard to maintain. So yes, I'll stand by
"complete misfeature".
Can you describe what you mean by "bette
Thomas Schmitt (2018-02-04):
> And what should human or machine think of my mail client's idea about
> when you sent your mail ?
>
>Tomorrow Richard Hector Re: policy around 'wontfix' bug tag
That it should learn to parse timezones and take them into account. The
date in Richard's mail is
On 05/02/18 02:39, Thomas Schmitt wrote:
> And what should human or machine think of my mail client's idea about
> when you sent your mail ?
>
>Tomorrow Richard Hector Re: policy around 'wontfix' bug tag
Ha! That I'm in NZ, of course. And I'm up too late. I never see that,
because we pret
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Feb 04, 2018 at 08:22:23AM -0500, Michael Stone wrote:
[...]
> But a better parser would allow the same functionality, without
> being confusing, inconsistent, and hard to maintain. So
> yes, I'll stand by "complete misfeat
Hi,
Richard Hector wrote:
> Incidentally, the gnu 'Date input formats' link above does talk about
> only accepting English names for days and months, but doesn't say
> anything about the ordering of day and month (except, under 'General
> date syntax', saying that 'Order of the items is immaterial
Michael Stone (2018-02-04):
> But a better parser would allow the same functionality, without being
> confusing, inconsistent, and hard to maintain. So yes, I'll stand by
> "complete misfeature".
Can you describe what you mean by "better parser" in more details?
Beware that the "same functionalit
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 horrible, confusing, and irregular, but
any attempt to change
On Mon, 05 Feb 2018, Richard Hector wrote:
> On 05/02/18 00:43, Nicolas George wrote:
> > Richard Hector (2018-02-05):
> >> #389251 (coreutils: date's -d switch doesn't honour locale) - it's quite
> >> an old one. But I found another instance in which the same claim applies:
> >>
> >> richard@zirco
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 automatic and works for everybody, just like I did. Too bad t
Richard Hector (2018-02-05):
> Now that you mention it ... ls was where I started this adventure,
> reading coreutils bugs :-)
>
> And you mention SI prefixes - IMHO, the output of ls should be extended
> to actually show 'GiB' rather than 'G' where that is what is meant.
> Assumptions that the us
On 05/02/18 01:32, Nicolas George wrote:
> Richard Hector (2018-02-05):
>> Actually, a good(ish) explanation is provided in a later bug, #729952:
>>
>> --8<--
>> The date parsing feature exists in Debian only for compatibility with
>> upstream. It is a complete misfeature, and I would prefe
Richard Hector (2018-02-05):
> Actually, a good(ish) explanation is provided in a later bug, #729952:
>
> --8<--
> The date parsing feature exists in Debian only for compatibility with
> upstream. It is a complete misfeature, and I would prefer that it didn't
> exist at all. In an ideal wo
On 05/02/18 01:13, Thomas Schmitt wrote:
> Hi,
>
> Richard Hector wrote:
>> #389251 (coreutils: date's -d switch doesn't honour locale) - it's quite
>> an old one. But I found another instance in which the same claim applies:
>
> Its age makes it hard to conclude nowadays' habits with newly submi
Hi,
Richard Hector wrote:
> #389251 (coreutils: date's -d switch doesn't honour locale) - it's quite
> an old one. But I found another instance in which the same claim applies:
Its age makes it hard to conclude nowadays' habits with newly submitted bugs.
The topic looks as promising for Debian b
On 05/02/18 00:30, Richard Hector wrote:
> On 05/02/18 00:16, Thomas Schmitt wrote:
>> Hi,
>>
>> Richard Hector wrote:
>>> When a maintainer tags a bug report with 'wontfix', is there not an
>>> expectation that they will say why?
>>
>> Obviously the Debian Developers have much freedom how to act.
On 05/02/18 00:43, Nicolas George wrote:
> Richard Hector (2018-02-05):
>> #389251 (coreutils: date's -d switch doesn't honour locale) - it's quite
>> an old one. But I found another instance in which the same claim applies:
>>
>> richard@zircon:~$ date -d '4/2/2018'
>> Mon Apr 2 00:00:00 NZST 201
Richard Hector (2018-02-05):
> #389251 (coreutils: date's -d switch doesn't honour locale) - it's quite
> an old one. But I found another instance in which the same claim applies:
>
> richard@zircon:~$ date -d '4/2/2018'
> Mon Apr 2 00:00:00 NZST 2018
>
> In my NZ locale, that date should be int
On 05/02/18 00:16, Thomas Schmitt wrote:
> Hi,
>
> Richard Hector wrote:
>> When a maintainer tags a bug report with 'wontfix', is there not an
>> expectation that they will say why?
>
> Obviously the Debian Developers have much freedom how to act. At least
> if it is about packaging and bug repo
Hi,
Richard Hector wrote:
> When a maintainer tags a bug report with 'wontfix', is there not an
> expectation that they will say why?
Obviously the Debian Developers have much freedom how to act. At least
if it is about packaging and bug report processing.
As for Debian policy, in this case it i
Hi all,
This might not be the most useful list, but I'm not subscribed to -devel
and don't want to jump in there without good reason.
When a maintainer tags a bug report with 'wontfix', is there not an
expectation that they will say why?
I was just reading a bug report that seemed valid (if corr
I'm getting the error
avahi-daemon: Failed to open /etc/resolv.conf: Invalid argument
chroot.c: open() failed: No such file or directory
at boot.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800643
Is the workaround mentioned above (and below) still valid (bug date Oct 2015)?
Appending
45 matches
Mail list logo
