Hi all,
I am soon going to add an ATF test for sh pattern matching (it tests all
3 forms, glob expansion, case patterns, and ${var#patern})
There are many tests, some of them quite esoteric...
First a general heads up ... the glob tests need files to match
against, and many of them ... so the te
Date:Sun, 24 Jun 2018 13:19:00 +0200
From:tlaro...@polynum.com
Message-ID: <20180624111859.ga...@polynum.com>
First, thanks for reading the message, and looking at the tests
and sending the comments/question - this is exactly the kind of
response I was hoping for.
Asi
Date:Sun, 24 Jun 2018 15:52:21 +0200
From:tlaro...@polynum.com
Message-ID: <20180624135221.gb...@polynum.com>
| It's a mess...
Yes...
| Wouldn't it be simple for POSIX to let the case...esac
| as is and introduce a ecase...esac[e] (à la grep, egrep) with somet
Date:Sun, 24 Jun 2018 19:09:58 +0200
From:Rhialto
Message-ID: <20180624170958.gj8...@falu.nl>
| Are we to assume that NetBSD's sh(1) manual page is correct?
Well, yes and no...
| Since that clearly says that your example above should not match.
Actually, it doe
Date:Mon, 25 Jun 2018 17:30:25 +0200
From:tlaro...@polynum.com
Message-ID: <20180625153025.ga2...@polynum.com>
| About the POSIX description "2.13.1 Patterns Matching a Single
| Character", have the draft assigned a precedence between "XBD RE Bracket
| Expression
Date:Mon, 02 Jul 2018 17:17:43 +0200
From:Leonardo Taccari
Message-ID: <20180702151748.7d45a84...@mail.netbsd.org>
| What should we do if we receive just a `printf '\''?
Pretty much whatever we please ... (including printing the environment, if
that was sane..., e
Date:Tue, 3 Jul 2018 10:39:37 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20180703083936.gi48...@trav.math.uni-bonn.de>
| > that is, \0123 in a format string, and in a %b arg are treated
differently.
| There's always something new to learn.
| Do you hav
Date:Tue, 17 Jul 2018 09:06:53 -0400
From:"D'Arcy Cain"
Message-ID: <409f3df1-c91c-897c-e4ea-98413263f...@netbsd.org>
| Do you think that this is a candidate for a pullup to 8?
You've already been informed that it is too late for 8.0 (and I don't think
that is the
Date:Wed, 18 Jul 2018 07:04:24 -0400
From:chris...@zoulas.com (Christos Zoulas)
Message-ID: <20180718110424.78f0f17f...@rebar.astron.com>
| Well, in that case we should check what POSIX says about it
There is no -l in posix cp
| and what do other implementation
I have just added support for the F a and A formats to printf(1).
These are not required by POSIX, but nor are the e E f g or G formats,
which we did support. and supporting those 5 without the other 3 makes
allmost no sense (in the code they are essentially free, the only real cost
is a little mo
Date:Tue, 24 Jul 2018 13:56:51 -0700
From:Alistair Crooks
Message-ID:
| No objections, I'd love to see these. I have trouble remembering printf
| field specifiers, and almost always have to resort to a trial and error
| compile-run-wtf frenzy when I least nee
Date:Fri, 27 Jul 2018 13:39:18 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20180727113917.gd48...@trav.math.uni-bonn.de>
| It has been brought to my attention that quoting the "word" in sh's
| substring processing causes word to be matched literally rathe
Date:Sun, 12 Aug 2018 20:23:05 +0200
From:Rhialto
Message-ID: <20180812182305.gc5...@falu.nl>
| I tried commenting out some stuff related to the -v option, and if I do
| this, then it works:
| Maybe the redirection isn't reset in some cases?
That is exactly it
Date:Tue, 14 Aug 2018 16:40:52 +0200
From:Rhialto
Message-ID: <20180814144052.gd5...@falu.nl>
| On Mon 13 Aug 2018 at 07:09:41 +0700, Robert Elz wrote:
| > This patch ...
|
| indeed fixes the problem for me.
Actually it is incomplete. If you l
Date:Tue, 14 Aug 2018 22:01:27 +0100
From:Roy Marples
Message-ID:
| I'm tempted to add code to exlcude all old messages so that line isn't
| even printed. Opinions?
Not a good idea, whether they are printed as "unknown message"
(or similar) as now, or whether t
Date:Tue, 14 Aug 2018 20:52:49 +0100
From:David Brownlee
Message-ID:
| If you had any other comments on obvious things you noticed which
| could be transitioned from "technically works" to "correct" I would be
| all ears :-p
Another is that the test (aka '[')
Hi...
I am in the process of creating ATF tests for printf (which is
why the activity in the sources recently...)
The tests will test both /usr/bin/printf and the shell's builtin
printf.(Actually, any shell's builtin printf, and any external
printf command, but that is not important here).
A
Date:Thu, 13 Sep 2018 14:00:10 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20180913120009.ge5...@trav.math.uni-bonn.de>
| is the job then supposed to show up in "jobs -p" output?
| In bash, at least for a), the job does show up until you call jobs without
Date:Thu, 13 Sep 2018 17:22:46 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20180913152246.gm5...@trav.math.uni-bonn.de>
| > You're using an old version, not NetBSD current (or 8) right?
| 6.1, mostly (for the ash part), yes.
The jobs command implementatio
I am doing a run through the NetBSD sources looking for old scripts
that contain vartious poor mechanisms...
My current target is the old "getopt" which we should remove from
everywhere (not the getopt binary, of course, but everything that
actually uses it in our tree.)
Fortunately, the most com
Date:Sat, 22 Sep 2018 10:06:24 +0200
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20180922080623.gf34...@trav.math.uni-bonn.de>
| It looks like you are looking for a script that reads and understands the
| documentation (which is wrong wrt. the current implement
Date:Sat, 22 Sep 2018 17:10:23 +
From:David Holland
Message-ID: <20180922171023.ga11...@netbsd.org>
| Just fix the doc. I know of no testing thingy that is running ypinit;
| if there were one this issue would have come up ages ago.
OK, since you (and Edgar, r
Date:Tue, 25 Sep 2018 16:32:03 +1000
From:Simon Burge
Message-ID: <20180925063203.2b92920...@thoreau.thistledown.com.au>
| Is the correct fix to use memmove(3) instead of memcpy(3) inside
| dirname(3), or are we restricted by some standard from having dirname(3)
Date:Tue, 25 Sep 2018 08:44:59 +
From:Emmanuel Dreyfus
Message-ID: <20180925084459.gd25...@homeworld.netbsd.org>
| What a pity they do that without introducing basename_r().
If that existed in some kind of wodespread use, that might have happened,
otherwise, i
Date:Wed, 26 Sep 2018 16:42:27 + (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| Well, it will return the wrong results... so might as well change the
| memcpy to memmove? No?
That would certainly not do any harm, but it would still be better t
Date:Wed, 26 Sep 2018 16:42:27 + (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| Well, it will return the wrong results... so might as well change the
| memcpy to memmove? No?
The results would not have been wrong - this was purely a SSP detect
Date:Sun, 30 Sep 2018 17:39:47 -0500
From:=?utf-8?B?Q8OhZw==?=
Message-ID: <20180930223947.sfc8-%c...@bitmessage.ch>
| It'd be more consistent with the rest of the file.
More consistent with a file that contains NAME=thing ... ?
The proposed change looks fine to
Date:Mon, 1 Oct 2018 06:49:55 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| With wedges you would just reference them by name.
Yes, of course, that's better, when it is possible, but to work usefully
(as opposed to simply substituting a dkN
Date:Mon, 1 Oct 2018 12:59:37 +0200
From:Piotr Meyer
Message-ID: <20181001105936.ga31...@czajka.smutek.pl>
| Maybe something like this will be better:
|
| NAME=@root/a/ ffs rw,log 1 1
| or even:
| NAME=@kern.root_device/
Date:Mon, 1 Oct 2018 17:52:15 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| The device doesn't know anything about it.
The device, obviously not, the filesystem on the device does though,
at least when it is using disklabel type partitioning,
Date:Tue, 2 Oct 2018 05:13:13 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| >Yes, that is what we need - but without knowing what the drive name is, as
| >that can vary.
|
| But you are not asking for that.
It wasn't me doing the asking
Date:Tue, 2 Oct 2018 11:28:59 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| Can you please check, you are misquoting, reversing the sense what I wrote.
This is what Jared said in the original message...
I came up with this simple pat
A question on what the shell should do:
POSIX specifies that a redirect error on a special builtin command
causes the shell to exit.
It also specifies that a redirect error on a utility that isn't a special
builting doesn't cause the shell to exit (but just fail the utility with
a non-zero exit s
Date:Sat, 24 Nov 2018 23:46:10 +0100 (CET)
From:neit...@hackett.marshlabs.gaertner.de (Martin Neitzel)
Message-ID: <20181124224610.254de34...@marshlabs-mx.gaertner.de>
| As admin I quite often use a simple
| > foo.log
Oh, yes, of course, I wasn't thinking of t
Date:Sun, 25 Nov 2018 10:38:36 +0100
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20181125093836.ge12...@trav.math.uni-bonn.de>
| > All other shells seem to not exit
| As even dash seem not to exit: Did they change their behaviour on purpose
to
| match ksh/ba
Date:Sun, 25 Nov 2018 23:02:09 +0100
From:Rhialto
Message-ID: <20181125220209.gl20...@falu.nl>
| Maybe this:
| From
|
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_01
Thanks - and I should have remembered that, I had seen i
Date:Sun, 25 Nov 2018 23:00:08 +0100
From:Rhialto
Message-ID: <20181125220008.gk20...@falu.nl>
| This may not be documented in sh(1) but here I find some description:
There is a limit to just how muct we can put in sh(1) - the posix spec is
60 pages (without any of
Date:Wed, 28 Nov 2018 00:23:47 +0100
From:=?UTF-8?Q?Micha=C5=82_G=C3=B3rny?=
Message-ID: <1543361027.17222.11.ca...@gentoo.org>
I have no idea whether this is something that we want or not,
but assuming that we do ...
| so I'd appreciate some pointers if I'm doing
I am (soon -- perhaps it will have happened before you
read this for some of you) going to commit changes to /bin/sh
to (finally!) get rid of internal uses of atoi() - completely.
Mostly this will have no visible effect, but there may be a few
places where sh will now report a "number out of range
Some (or many) of you may be aware (and if not, please read the PR)
that the code added in 2016 to deal with PR bin/48875 was never really
correct - it just had not, until recently, caused anyone any problems
so it had just been sitting there, doing its thing, and bothering no-one
really, until jus
Date:Fri, 17 Aug 2018 11:37:18 -0500
From:"J. Lewis Muir"
Message-ID: <20180817163717.ga21...@tuna.imca.aps.anl.gov>
| I think this sentence would read better if it used the same verb tense
Thanks, that is the kind of improvement I was looking for (since I don't
of
Date:Sat, 18 Aug 2018 08:00:40 -0500
From:"J. Lewis Muir"
Message-ID: <20180818130040.ga1...@tuna.imca.aps.anl.gov>
| I see your point. Yes, this seems too long. Maybe it would be more
| appropriate in the POSIX sh shell book you were planning to write. :-)
Yea
There has been a recent (very recent, like within the past few hours) proposal
to add the ability to do a chdir() (or fchdir()) to posix_spawn
There are more changes than what are included here, but the rest are mostly
all just boilerplate changes to support this addition.
If anyone has any comme
I notice in the most recent builtbot build of current, the atari build failed
because of install floppy overflow.
[Several arm builds failed as well, but those look to be from an entirely
unrelated reason, and were failing earlier for the same reason.]
This recent build would have included
I have just committed the changes that allow parameter expansion on $ENV
before processing (as required by POSIX) - it will make no difference to most
people who have ENV set to a simple filename (if there are no $'s in the value
of ENV (and no backticks) then it is used just like before. We also
Date:Thu, 13 Dec 2018 09:39:44 +0100
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20181213083944.gb46...@trav.math.uni-bonn.de>
| though. In the current version, what's a login-sh's wd at that time?
unless /etc/profile changes it, $HOME (for .profile) and unless
Date:Thu, 13 Dec 2018 18:36:35 +0100
From:Edgar =?iso-8859-1?B?RnXf?=
Message-ID: <20181213173634.ge46...@trav.math.uni-bonn.de>
| > unless /etc/profile changes it, $HOME (for .profile)
| So, would it make sense to treat relative paths as relative to $HOME, then?
Date:Fri, 14 Dec 2018 04:56:02 +
From:co...@sdf.org
Message-ID: <20181214045601.ga12...@sdf.org>
| The maintenance burden is as follows:
|
| - Y'all seem to think it's totally reasonable to telnet in the open
| internet
|
| This means it begs for a re
Date:Fri, 14 Dec 2018 21:28:34 -0800
From:John Nemeth
Message-ID: <201812150528.wbf5syhr025...@server.cornerstoneservice.ca>
| As kre noted, it is probably the oldest network application
| around. According to Wikipedia, the protocol was developed in
| 1969, pr
Date:Wed, 19 Dec 2018 08:06:19 +1030
From:Brett Lymn
Message-ID: <20181218213619.gb1...@internode.on.net>
| I don't do this personally but I think there are people out there that
| have older, slower machines on their local network
Aside from that, telnet is quit
Date:Wed, 19 Dec 2018 21:03:27 +
From:David Holland
Message-ID: <20181219210327.ga5...@netbsd.org>
| But it can't be fixed and sooner or later someone's going to
| find a critical problem with it.
Nothing can't be fixed. It all depends what the objective is
An issue was recently dealt with wrt the POSIX spec, in respose to
a question whether fflush(NULL) is required to flush memory streams,
or only ones backed by files.
The response was to (plan to) change the wording to not require
memory streams be flushed on fflush(NULL).
That was until it was po
Date:Sat, 12 Jan 2019 17:42:18 +0100
From:Rhialto
Message-ID: <20190112164218.gh2...@falu.nl>
| When I saw this, my first reaction was "What does it even *mean* to
| flush a memory stream!? They don't have a buffer, they *are* the
| buffer!"
That is an implemen
The shell (/bin/sh) has a number of "special" or "magic" variables.
One of those (LINENO) is required by POSIX (and autoconf) so the
general concept is not going away (so please don't bother replying
to this message along the lines of "the whole thing is a bad idea
and should be done another way"
Date:Sat, 9 Feb 2019 13:08:15 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| Doesn't POSIX require that the variable is non-magic once set or unset
| for the lifetime of the shell?
POSIX has only LINENO that is like this, and is very wishy-w
Inspired by something joerg@ said a while ago (about not wanting
more delays in sh startup by linking against an extra library)
I have been wondering whether we need the cost of linking libedit
and libtermlib into non-interactive shells.
So, I made the patch appended below (assuming I remember it!
Date:Mon, 11 Feb 2019 09:10:48 +0100
From:Martin Husemann
Message-ID: <20190211081048.ga16...@mail.duskware.de>
| Just drop the version and ignore the path. There should be a proper symlink
| for "libedit.so" that does all what you want.
Ignoring the path is what
Date:Mon, 11 Feb 2019 09:05:53 +
From:m...@netbsd.org
Message-ID: <20190211090553.ga2...@homeworld.netbsd.org>
| I feel like we should dig into why it makes a big difference.
It is really only a fairly small difference, 170 us isn't big
by anyone's measure...
Date:Mon, 11 Feb 2019 18:36:16 +0700
From:Robert Elz
Message-ID: <26894.1549884...@jinx.noi.kre.to>
| It is really only a fairly small difference, 170 us isn't big
| by anyone's measure...
As another data point, I ran my stupid 1 execs o
Date:Mon, 11 Feb 2019 09:10:48 +0100
From:Martin Husemann
Message-ID: <20190211081048.ga16...@mail.duskware.de>
| Make the makefile define that depending on LDSTATIC being defined/empty?
| That would also cover the MKDYNAMICROOT=no case (I think).
I currently hav
Date:Mon, 11 Feb 2019 16:54:47 +
From:David Holland
Message-ID: <20190211165447.ga12...@netbsd.org>
| Maybe one of the necrocomputing folks wants to measure rc.d
| performance with and without it :-)
Didn't test that before, but I have now ... well kind of ha
Date:Mon, 11 Feb 2019 19:56:41 +0100
From:=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=
Message-ID:
| IMO 2% speedup is not worth this.
Entirely reasonable - I'm not sure it is worth it either.
| What exactly does take libedit do to take it so long? Does it trigger
Date:Fri, 15 Feb 2019 05:59:33 +
From:m...@netbsd.org
Message-ID: <20190215055933.ga10...@homeworld.netbsd.org>
I have seen Rin's later message so don't need to add my THB1 (about
USD0.03) indicating how bad an idea that would be, but ...
| On Fri, Feb 15, 2019
Date:Sat, 16 Feb 2019 15:02:58 - (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| Yes, what I don't understand (because nobody has stated a technical
| reason other than 'fluff'), why we shouldn't we have the feature in base
| at all. Nobody pr
In response to bug report 1198
http://austingroupbugs.net/view.php?id=1198
which said (inter alia):
The "Expressions In Awk" section of the standard says:
---
Comparisons (with the '<', "<=", "!=", "==", '>', and ">=" operators) shall
be made numerically if both operands ar
Date:Thu, 28 Mar 2019 03:44:32 +0100
From:m...@netbsd.org (Emmanuel Dreyfus)
Message-ID: <1o54q7j.12nkmgacatowxm%m...@netbsd.org>
| Would it make sense to add a knote in wscons for keypresses, so that
| they can be readen using kevent?
If modifying wscons is an ac
Date:Thu, 4 Apr 2019 10:12:35 +
From:co...@sdf.org
Message-ID: <20190404101235.gb6...@sdf.org>
| I understand the need for correctness, but the limits for find ... -exec
| are really low,
What limits do you think are being encountered here?
| and it's quite
Date:Sat, 6 Apr 2019 07:02:34 +
From:co...@sdf.org
Message-ID: <20190406070234.ga5...@sdf.org>
| Thanks. I committed that.
| I'm slightly horrified by this being the problem.
I hope it was tested ... I don't often install fonts. As I said
while it looked to
Date:Sat, 6 Apr 2019 08:30:26 +
From:co...@sdf.org
Message-ID: <20190406083025.ga22...@sdf.org>
| The command failing is, for urbanrenewal-ttf,
I found the sources for install (xinstall!) and I think I
understand what happens now...
/* pseudo-code ... o
Date:Mon, 8 Apr 2019 15:31:38 +0200
From:rudolf
Message-ID: <2628128b-c24e-2f8b-04f0-6405936f3...@eq.cz>
| Is there any problem with the PR (is the problem questionable or the
| patch funny in any way)? I've received no feedback.
No problem I can see ... sometim
Date:Sat, 13 Apr 2019 13:58:55 +0200
From:tlaro...@polynum.com
Message-ID: <20190413115855.ga1...@polynum.com>
| The question was more: why is it not the very last thing invoked?
An equally valid question would be why not the first? Or the last before
logins are e
Date:Sun, 14 Apr 2019 11:50:47 +0200
From:tlaro...@polynum.com
Message-ID: <20190414095047.ga...@polynum.com>
| It is definitively not a technical problem: the rc.d structure
| allows to solve my problem (as well as others'). It is more a lack of
| consistency. r
I have seen this question:
does anyone know of an implementation that has pthreads and
C11/C17 threads, with pthread_t and thrd_t defined as different types?
As best I can tell in NetBSD we do not have a thrd_t at all (but I
might be missing something). If we do, or someday we m
Date:Wed, 17 Apr 2019 19:02:47 +0200
From:Kamil Rytarowski
Message-ID:
Thanks, and
| +typedef pthread_tthrd_t;
is a very clear answer to the question... Unless anyone
has any objections to that method, I think we can ignore the
(possible) posix requirement
I have a fix for PR bin/53550 wrong exit status of a command that is
(more or less) just a here-doc which contains a command substitution...
Yes, I know, no-one cares ... that fix is done, but is waiting for
me to get up the energy to add some ATF tests for it (& perhaps various
similar related
Date:Fri, 24 May 2019 06:34:58 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| That's probably the shell that must read input byte by byte in most cases.
The shell actually very rarely does one byte reads when not reading
from the terminal (and
Date:Fri, 24 May 2019 13:57:26 +0200
From:Kamil Rytarowski
Message-ID: <049cb255-b647-a241-7d41-4ec2a1151...@gmx.com>
| It prints now program name for the -f option and decodes properly text
| string for read(2).
|
| =2E/truss -o /tmp/log.txt -f /usr/src/buil
Date:Fri, 24 May 2019 20:29:03 +0700
From:Robert Elz
Message-ID: <27280.1558704...@jinx.noi.kre.to>
And now that I look at this again (unrelated to the issue
of what the trace was showing reading one byte at a time)
I wonder what this is doing...
| i
Date:Sat, 25 May 2019 02:04:13 +0200
From:Kamil Rytarowski
Message-ID: <4fefdf41-44fa-12f9-705d-5187732d7...@gmx.com>
| As far as I'm aware we can use read(2) and write(2) in pipes with longer
| transfers than 1 byte.
Of course. But once read we cannot go back
Date:Sat, 25 May 2019 08:47:46 +0200
From:Kamil Rytarowski
Message-ID: <9c91afa3-8fc5-1669-8b6b-035574137...@gmx.com>
| > | As far as I'm aware we can use read(2) and write(2) in pipes with
| > | longer transfers than 1 byte.
| >
| > Of course. But once
Date:Sun, 21 Jul 2019 10:53:35 +0200
From:tlaro...@polynum.com
Message-ID: <20190721085335.ga...@polynum.com>
| Am I correct? Is it worth a PR?
I believe you are correct, though this is a common problem
(one shared by dash and bash which makes it very common out
the
Date:Sun, 21 Jul 2019 16:15:05 +0200
From:tlaro...@polynum.com
Message-ID: <20190721141505.ga4...@polynum.com>
| For safety, in my scripts, I simply circumvent by a
| leading "%c" or "\055"
I'd suggest %s (with a '' arg) (even %.0s to make it blatant)
as a clearer
Date:Fri, 13 Sep 2019 08:33:31 +0200
From:Thomas Klausner
Message-ID: <20190913063330.jl6qb35ifszulh3z@danbala>
| I'm sorry, I totally do not get it the problem with -- in general --
| writing the code in such a way that it properly frees any allocations
| it ma
Date:Wed, 16 Oct 2019 20:21:09 +
From:co...@sdf.org
Message-ID: <20191016202109.ga15...@sdf.org>
| > and define _POSIX_RTSIG_MAX to 8 in limits.h
|
| What is POSIX thinking with that requirement...?
That this value is a number that simply specifies the minim
Date:Sun, 10 Nov 2019 00:52:46 +
From:Jason High
Message-ID: <20191110005246.ga29...@homeworld.netbsd.org>
| When using cgdconfig in do_all mode (-C|-U), it will attempt to
| configure/unconfigure all devices specified in cgd.conf regardless of
| whether the
Date:Sun, 10 Nov 2019 10:00:48 -0600
From:Jason High
Message-ID:
| Ok?
Aside from other issues, this should still be enabled by a new
flag (whether the new flag causes -C or is used in conjunction
with -C doesn't matter) - simply doing "cgdconfig -C" should not
c
Date:Sun, 24 Nov 2019 13:49:56 +0600
From:Alexander Kuleshov
Message-ID:
| +addr = strtol(optarg, &ep, 10);
| Any comments?
strtol() returns a long, addr is just int - something needs to be
adjusted to avoid value truncation, depending upon what's
Apologies for the multi-list posting, but I think this needs a wide
audience - please respect the Reply-To and send replies only to
current-users@
I have been looking into this, a little.
First, while the t_mlock() test is most likely broken, it
should never cause a kernel panic (or even a kernel
Date:Tue, 3 Dec 2019 08:29:20 +
From:Emmanuel Dreyfus
Message-ID: <20191203082920.ga6...@homeworld.netbsd.org>
| Today I discovered the let and exp shell builtins. They exist in /bin/sh
| but are only documented in ksh(1). CVS tells us it came from 4.4BSD lite
Date:Tue, 3 Dec 2019 08:29:20 +
From:Emmanuel Dreyfus
Message-ID: <20191203082920.ga6...@homeworld.netbsd.org>
| Today I discovered the let and exp shell builtins. They exist in /bin/sh
| but are only documented in ksh(1).
Incidentally, note that the sh and k
Date:Wed, 29 Jan 2020 19:33:56 - (UTC)
From:chris...@astron.com (Christos Zoulas)
Message-ID:
| Having a split /usr makes little sense today though as joerg mentioned,
| even in the space-constrained systems.
Space constraints may have once been the primary m
Date:Thu, 30 Jan 2020 21:12:43 +0100
From:Joerg Sonnenberger
Message-ID: <20200130201243.gb90...@bec.de>
| Size constraints for root (and not the rest) seems a bit strange.
A result of technology changes, but ...
| That's more an argument for having a /boot file
Date:Mon, 3 Feb 2020 22:57:21 +0100
From:Joerg Sonnenberger
Message-ID: <20200203215721.ga26...@bec.de>
| I don't think the size distribution for / is really that much different
| from most of /usr.
Most of /usr or all of /usr ?
jinx$ df -i / /usr
Filesystem
Date:Mon, 30 Mar 2020 03:26:23 +0100
From:Roy Marples
Message-ID:
| Without ncurses installed I have no idea how to test that.
| Ideas of course welcome.
You can write ATF tests that use programs not normally installed,
they just need an atf_require_prog (or wha
Our man page for posix_spawnp() says...
The file parameter to posix_spawnp() is used to construct a pathname that
identifies the new process image file. If the file parameter contains a
slash character, the file parameter is used as the pathname for the new
process image file.
Date:Wed, 6 May 2020 15:16:06 +0200
From:Martin Husemann
Message-ID: <20200506131606.gb2...@mail.duskware.de>
| Ok, but you can set PATH to : or something.
Not that, at least not to make posix_spawnp() work - that uses
strtok() to parse PATH, and that (apparently)
Date:Mon, 25 May 2020 06:06:09 +0200
From:Martin Husemann
Message-ID: <20200525040609.ga28...@mail.duskware.de>
| The man page diff does not suggest any standards that define this function.
It has been (twice now) proposed to posix to be added (both still pending,
Date:Tue, 2 Jun 2020 16:14:20 +0200
From:Martin Husemann
Message-ID: <20200602141420.ga5...@mail.duskware.de>
| I would like to create directory hierachies from mtree spec files, but
| restrict this to selected hierachies (where the mtree files contain a
| bit m
Date:Thu, 04 Jun 2020 05:45:01 +0700
From:Robert Elz
Message-ID: <1215.1591224...@jinx.noi.kre.to>
| If a change/addition to mtree is desirable, [...]
And of course, I should have really read mtree(1) before replying,
so the suggested method would j
Date:Sun, 12 Jul 2020 13:01:59 +1000
From:Luke Mewburn
Message-ID: <20200712030159.gh12...@mewburn.net>
| | IMHO, permitting braces to be consistently used:
| | - Adds to clarity of intent.
| | - Aids code review.
| | - Avoids gotofail:
https://en.wi
1 - 100 of 408 matches
Mail list logo
