On Sun, Feb 28, 2016 at 1:35 PM, Edgar Pettijohn
wrote:
> --- rdist.c.origSun Feb 28 15:29:27 2016
> +++ rdist.cSun Feb 28 15:32:06 2016
> @@ -57,8 +57,7 @@
> char *path_remsh = NULL;
>
> static void addhostlist(char *, struct namelist **);
> -static void usage(void);
> -int ma
On Sat, Mar 5, 2016 at 12:08 AM, Michal Mazurek wrote:
> PT_GET_THREAD_FIRST and PT_GET_THREAD_NEXT are undocumented, I don't
> believe it's by design.
>
> The only place these are used is gnu/usr.bin/binutils/gdb/obsd-nat.c
Committed.
(Side note: best practice is to run "mandoc -Tlint -Wwarning
On Thu, Mar 3, 2016 at 10:16 AM, Michal Mazurek wrote:
> These functions appear to only be used in kern_exit.
There was a time when increasing linux compat support would have
required at least one of those to be used elsewhere. Happily, that's
gone. Diff applied.
Philip Guenther
The command 'set -o' shows the current shell options in an unspecified
format. Less well-known is the variant 'set +o', which should output the
current shell options "in a format that is suitable for reinput to the
shell as commands that achieve the same options settings".[*]
That means it should
During make build the distrib/sets/makeetcset script does not preserve
ownership when installing /etc and /var files from the base set.
I've noticed that this leads to some discrepancies compared with a normal
install / upgrade.
Nathanael
Index: makeetcset
===
> Looks good to me. Fwiw, linux_pid_t was typedefed as int, so the
> limitation to SHRT_MAX must have been for another compate module.
COMPAT_HPUX in the good old hp300 days.
David Vasek schreef op 05-03-16 om 23:16:
> while echo n; do done
> is shorter (and even faster). But it doesn't help either.
It's also a syntax error on everything except {pd,m}ksh and zsh. Even
AT&T ksh doesn't support it.
>>> pax -rwk ${files} dst/
>
> It works when the ${files} contains
On 2016-02-28, Vadim Zhukov wrote:
> It looks like decided to use TM_ZONE as a wrapper for tm.tm_zone,
> until the tm_zone is gone. So, until the later happens (I found
> no usage of tm_zone in base, BTW), we should at least use TM_ZONE
> consistently. Okay for the patch?
ok naddy@
Note that tm
On Sat, Mar 05, 2016 at 02:08:07PM -0800, Serguey Parkhomovsky wrote:
> This fixes a small typo in the release notes for 5.9.
fixed, thanks
On Sat, 5 Mar 2016, Timo Buhrmester wrote:
Not really, because this is about the 'cp -i' part rather than the 'yes n'.
Consider the latter an alias for ``while true; do echo n; done'' :-).
while echo n; do done
is shorter (and even faster). But it doesn't help either.
'pax', which is the POS
This fixes a small typo in the release notes for 5.9.
Index: 59.html
===
RCS file: /cvs/www/59.html,v
retrieving revision 1.55
diff -u -r1.55 59.html
--- 59.html 5 Mar 2016 03:25:49 - 1.55
+++ 59.html 5 Mar 2016 21:5
On Sat, Mar 05, 2016 at 01:41:32AM +0100, Timo Buhrmester wrote:
> From src/bin/cp/cp.c:
> > while ((ch = getopt(argc, argv, "HLNPRfailprv")) != -1)
> > [...]
> > case 'i':
> > iflag = isatty(fileno(stdin));
> The -i in cp -i is ignored if standard i
> It's kind of ironic that we're arguing about the POSIX compliance of 'cp
> -i' while the 'yes' command doesn't even exist in POSIX.
Not really, because this is about the 'cp -i' part rather than the 'yes n'.
Consider the latter an alias for ``while true; do echo n; done'' :-).
> 'pax', which is
On Sat, Mar 05, 2016 at 11:32:04AM -0800, Philip Guenther wrote:
> On Sat, Mar 5, 2016 at 8:10 AM, Michal Mazurek wrote:
> > sys/compat is gone. I don't know if PID_MAX can or should be increased,
> > but I don't think the comment is now useful.
>
> I think we can go a bit further now and include
See subject.
ok?
diff --git a/uvm/uvm_amap.c b/uvm/uvm_amap.c
index ef8e505..3cc7ed1 100644
--- a/uvm/uvm_amap.c
+++ b/uvm/uvm_amap.c
@@ -403,49 +403,6 @@ amap_extend(struct vm_map_entry *entry, vsize_t addsize)
}
/*
- * amap_share_protect: change protection of anons in a shared amap
- *
- *
On Sat, Mar 5, 2016 at 8:10 AM, Michal Mazurek wrote:
> sys/compat is gone. I don't know if PID_MAX can or should be increased,
> but I don't think the comment is now useful.
I think we can go a bit further now and include PID_MAX to 9 (to
keep it in 5 columns).
ok?
Philip Guenther
Index:
David Vasek schreef op 05-03-16 om 10:34:
> On Sat, 5 Mar 2016, Dmitrij D. Czarkoff wrote:
>
>> So the goal of the diff is to replace something like
>>
>> $ for src in ${files}; do [ -r "$src" ] && cp ${src} dst/; done
>>
>> with
>>
>> $ yes n | cp -i ${files} dst/
>>
>
> The former line doesn'
sys/compat is gone. I don't know if PID_MAX can or should be increased,
but I don't think the comment is now useful.
Index: sys/sys/proc.h
===
RCS file: /cvs/src/sys/sys/proc.h,v
retrieving revision 1.214
diff -u -p -r1.214 proc.h
---
> Maybe it's just the alias being ignored by nice:
nice executes the utility with execvp(), so it doesn't have a way to
know about your alias, as the shell is not involved. The alias is also
not expanded before calling nice, because it is not the first word in
the line.
natano
On 2016-03-05 Sat 01:41 AM |, Timo Buhrmester wrote:
> From src/bin/cp/cp.c:
> > while ((ch = getopt(argc, argv, "HLNPRfailprv")) != -1)
> > [...]
> > case 'i':
> > iflag = isatty(fileno(stdin));
> The -i in cp -i is ignored if standard input isn't a
The code involving the posfile member of the FILEDESC struct is
effectively dead for a long time and also cannot be enabled anymore
since semarie unifdef'ed OK_TO_WRITE_DISK in revision 1.43.
Index: games/fortune/fortune/fortune.c
===
Martin Natano wrote:
> The VOP_UNLOCK() function has a flags parameter, which is documented to
> should be zero in most cases. It turns out that the flags argument is
> zero for all ~200 callers in the tree. On a closer look it is revealed
> that VOP_UNLOCK() uses lockmgr() for all filesystems tha
On Fri, Mar 04, 2016 at 10:32:01PM +, Miod Vallat wrote:
>
> > SH4 CPUs with EMODE bit set have a cache twice as big. Fix the obvious
> > copy&paste mistake.
>
> There is nothing to fix in these routines.
>
> When EMODE is enabled, the cache becomes two way, instead of one way,
> which is w
Hi to all,
The 1.13 revision of /src/usr.sbin/npppd/npppd/npppd_local.h forgot to remove
the bottom __cplusplus include guard.
--- /src/usr.sbin/npppd/npppd/npppd_local.h Thu Jul 23 09:04:06 2015
+++ /src/usr.sbin/npppd/npppd/npppd_local.h Sat Mar 05 09:05:59 2016
@@ -187,8 +187,4 @@
On Sat, 5 Mar 2016, Dmitrij D. Czarkoff wrote:
So the goal of the diff is to replace something like
$ for src in ${files}; do [ -r "$src" ] && cp ${src} dst/; done
with
$ yes n | cp -i ${files} dst/
The former line doesn't prevent you from overwriting files in dst/ . More
tests are nece
On 16:20:11, 1.03.16, Michal Mazurek wrote:
>
> Index: sys/kern/sched_bsd.c
> ===
> RCS file: /cvs/src/sys/kern/sched_bsd.c,v
> retrieving revision 1.42
> diff -u -p -r1.42 sched_bsd.c
> --- sys/kern/sched_bsd.c 8 Nov 2015 20:45
PT_GET_THREAD_FIRST and PT_GET_THREAD_NEXT are undocumented, I don't
believe it's by design.
The only place these are used is gnu/usr.bin/binutils/gdb/obsd-nat.c
Index: ptrace.2
===
RCS file: /cvs/src/lib/libc/sys/ptrace.2,v
retrievi
27 matches
Mail list logo
