sr/local/share/games/fortune/ru/foo".
I decided to call readlink(2) explicitly rather than adding
check of file type being open, since that resulted in less code.
Ah, and yes, I have a port of Russian fortune files pending,
but that's for another list and another day.
So... okay/notok
can return NULL, and that value isn't checked.
So I'm posting the whole diff for the sake of completeness, and what
I really think worths committing is the last chunk, replacing "return
NULL" with "err(1, NULL)" in copy(). Okay for it?
> martijn@
>
> On Tue,
ing).
I'm too lazy to check why. :-)
Okay anyone?
--
WBR,
Vadim Zhukov
Index: regress/bin/ksh/obsd-regress.t
===
RCS file: /cvs/src/regress/bin/ksh/obsd-regress.t,v
retrieving revision 1.10
diff -u -p -r1.10 obsd-regress.t
--
Hello all.
Since xenodm has DEF_USER_AUTH_DIR set to "/tmp", we need to ignore
/tmp/.Xauth* in daily cleanup, don't we?
Found the hard way a few minutes ago on my X240.
Okay?
--
WBR,
Vadim Zhukov
Index: daily
=
пт, 5 мар. 2021 г. в 18:14, Theo Buehler :
>
> On Sun, Feb 21, 2021 at 10:04:07PM +0300, Vadim Zhukov wrote:
> > Hello all.
> >
> > This continues the 'Another potential ksh bug?' thread on misc@:
> > https://marc.info/?l=openbsd-misc&m=16073670022062
чт, 4 мар. 2021 г. в 02:02, Vadim Zhukov :
>
> Hello all.
>
> Since xenodm has DEF_USER_AUTH_DIR set to "/tmp", we need to ignore
> /tmp/.Xauth* in daily cleanup, don't we?
>
> Found the hard way a few minutes ago on my X240.
Thanks sthen@, I've realize
сб, 6 мар. 2021 г. в 20:41, Matthieu Herrb :
>
> On Sat, Mar 06, 2021 at 09:56:34AM -0700, Theo de Raadt wrote:
> > Matthieu Herrb wrote:
> >
> > > On Fri, Mar 05, 2021 at 09:10:32PM +0300, Vadim Zhukov wrote:
> > > > чт, 4 мар. 2021 г. в 02:02, Vadim
сб, 6 мар. 2021 г. в 20:50, Theo de Raadt :
>
> Matthieu Herrb wrote:
>
> > On Sat, Mar 06, 2021 at 09:56:34AM -0700, Theo de Raadt wrote:
> > > Matthieu Herrb wrote:
> > >
> > > > On Fri, Mar 05, 2021 at 09:10:32PM +0300, Vadim Zhukov wrote:
>
сб, 6 мар. 2021 г. в 20:53, Theo de Raadt :
>
> Vadim Zhukov wrote:
>
> > > The backup dir can be configured to something else, but it needs to be
> > > writeable by the user whois login in. It could be a subdir of /tmp (if
> > > the rc.d script takes care
(b) is a variant of my case, as I
said, I can live without this feature. In the case of (c) users
(non-admins) won't be able to do something anyway. Can't speak for NFS
(I've quit the job where /home on NFS has been set up a few years ago)
so no opinion on (d).
--
WBR,
Vadim Zhukov
сб, 6 мар. 2021 г. в 23:14, Matthieu Herrb :
>
> On Sat, Mar 06, 2021 at 09:52:58PM +0300, Vadim Zhukov wrote:
> > сб, 6 мар. 2021 г. в 21:30, Theo de Raadt :
> > >
> > > Matthieu Herrb wrote:
> > >
> > > > Linux, systemd and XDG have inventen
lue.
Or we should do this in IPv4 too, then: I'm not opposed, but
at least consistency should be honored, IMHO.
Okay? Comments?
--
WBR,
Vadim Zhukov
P.S.: I'm not fully back yet, sorry.
Index: ping.c
===
RCS fil
Hi all.
Lets stop lying that patch(1) runs ed(1). Okay? Or should we tell
explicitly mention that we don't do bad things?
--
WBR,
Vadim Zhukov
Index: patch.1
===
RCS file: /cvs/src/usr.bin/patch/patch.1,v
retrieving rev
, to be addressed in
another letter.
So, does any libkvm hacker have any clues where to look for this
argv-envp bug? I'm not sure that I'll find the root issue myself fast
enough (in less than half a year).
--
WBR,
Vadim Zhukov
Index: print.c
===
Hi all.
The "p = realloc(p, size)" idiom is obviously wrong. Since both
places to be fixed were similar, I went further and unified the code
as well.
Note that "argv" is later initialized from kd->argv, so there is
no problem in reusing it here.
The amd64 is happy. Okay?
t splitting kd->argbuf into kd->argbuf and
kd->envbuf. Seems a bit saner.
I'm fine with any direction. The patch below implements (a), since
it's less patching. Is it okay, or should it be (b)?
--
WBR,
Vadim Zhukov
Index: kvm_proc.c
=
ky that this didn't
strike us on 64-bit archs yet. The is needed only
for the ptrdiff_t.
If required, I'll split (1), (2) and (3) in separate commits; it's
that reviewing them in a single mail and a single context looks like
easier for me; please correct me if I'm wrong
e it's done
for other archs.
--
WBR,
Vadim Zhukov
Index: kvm.c
===
RCS file: /cvs/src/lib/libkvm/kvm.c,v
retrieving revision 1.64
diff -u -p -r1.64 kvm.c
--- kvm.c 3 May 2018 15:47:41 - 1.64
+++ kvm.c
libc code I've also found that __sread() drops
__SOFF flag unconditionally for all read errors. IMHO, the EAGAIN case
shouldn't be affected here, since, obviously current offset doesn't
change and is still well-known.
So... any comments, or ever oka
2018-05-05 22:12 GMT+03:00 Vadim Zhukov :
> Hi all!
>
> Recently I was working on a program that uses stdio functions heavily.
> While hunting for a bug, I've temporarily disabled buffering (via
> setvbuf(f, NULL, _IONBF, 0)) and realized that program behavior was
> changed
etsockopt(TCP_MAXSEG) call compiles still)?
--
WBR,
Vadim Zhukov
Index: tcp.4
===
RCS file: /cvs/src/share/man/man4/tcp.4,v
retrieving revision 1.23
diff -u -p -r1.23 tcp.4
--- tcp.4 10 Sep 2015 17:55:21 - 1.23
+++ tcp.4
#if 0
2018-05-05 22:17 GMT+03:00 Vadim Zhukov :
> 2018-05-05 22:12 GMT+03:00 Vadim Zhukov :
>> Hi all!
>>
>> Recently I was working on a program that uses stdio functions heavily.
>> While hunting for a bug, I've temporarily disabled buffering (via
>> setvbuf(
anyway.
Would it be okay to add --binary as a no-op option to our patch?
--
WBR,
Vadim Zhukov
ср, 20 июн. 2018 г. в 21:17, Vadim Zhukov :
>
> Hi,
>
> The Ansible "patch" module fails to work on OpenBSD because it tries
> to use "--dry-run" command-line option on patch(1), while ours
> supports -C/--check instead. For now, I have an obvious, hm, patch
ср, 20 июн. 2018 г. в 21:59, Chris Cappuccio :
>
> Vadim Zhukov [persg...@gmail.com] wrote:
> > , 20 ??. 2018 ??. ?? 21:17, Vadim Zhukov :
> > >
> > > Hi,
> > >
> > > The Ansible "patch" module fails to work on OpenBSD because it t
ср, 20 июн. 2018 г. в 22:09, Stuart Henderson :
>
> On 2018/06/20 21:17, Vadim Zhukov wrote:
> > Hi,
> >
> > The Ansible "patch" module fails to work on OpenBSD because it tries
> > to use "--dry-run" command-line option on patch(1), while ours
&
and runs on (almost) -CURRENT. Okay or not?
--
WBR,
Vadim Zhukov
Index: patch.c
===
RCS file: /cvs/src/usr.bin/patch/patch.c,v
retrieving revision 1.65
diff -u -p -r1.65 patch.c
--- patch.c 7 Apr 2018 14:55:13 - 1.65
++
The patch was tested on 6.6. Well, it doesn't apply cleanly to 6.6,
since "set +e" magic you see arrived in -CURRENT, but tweaked version
runs smoothly.
BTW, why do we ever call eval in unpriv()? Without eval, set +e isn't
needed, FWIW.
-
сб, 14 дек. 2019 г. в 14:35, Antoine Jacoutot :
>
> On Sat, Dec 14, 2019 at 10:12:36AM +0300, Vadim Zhukov wrote:
> > Hello all (long time no see!)
> >
> > TL;DR: Allow syspatch -c run under non-priviledged user.
> >
> > Reasoning: instead of putting syspatch -
c to using multi-byte sequences,
or whatever is needed for proper handling of those keys.
Ideas, comments and (may I hope?) okays are welcome. :)
--
WBR,
Vadim Zhukov
Index: machine.c
===
RCS file: /cvs/src/usr.bin/top/m
5 января 2020 г. 22:37:05 GMT+02:00, Ted Unangst пишет:
>Vadim Zhukov wrote:
>> Today I get really upset and angry due limitation of top(1): it shows
>> only hrrm, top processes (thank you, Chromium). Now here is a diff
>that
>> allows you to scroll process list by
rror we keep bulk_running set. This seems just
a leftover, as well as the first chunk: if we failed to create kthread,
there won't be anything running under bulk_running==1 for sure.
I must thank kettenis@ for help during diagnosis and mpi@ for a patch
for related issue.
OK?
f also adds a regression test, for the sake of completeness.
Existing regression tests pass on amd64.
OK?
--
WBR,
Vadim Zhukov
Index: sbin/pfctl/parse.y
===
RCS file: /cvs/src/sbin/pfctl/parse.y,v
retrieving revision 1.699
diff -u
allow all of them to connect e.g. to Github or
anoncvs, but not to whole Internet.
I can use "1999><6000" as alternative, of course, but then manual must be
tweaked, IMO.
>Vadim Zhukov wrote:
>
>> I've just found that pfctl doesn't like 'X:Y' syntax
on" feature could be used wrong for other config clauses as well,
especially when negation comes to play. I'm not sure if this should be changed
at all... We may force that only one of two syntaxes may be used:
user { foo, bar }
user { 1000 till 1999, >=1 }
--
With best regards,
Vadim Zhukov
lag
set. The second one says its all.
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Index: netin
On many arches there are "wsmouse" and "wsmouse*" entries in MAKEDEV,
with "wsmouse*" going first. Therefore, "wsmouse" never gets matched.
Here is a fix.
Note/question on vax: while it has wsmouseN devices, it does not have
wsmouse device - is it normal?
ed
it from the another work doing now).
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Ind
EASON_SET(&reason, PFRES_SHORT);
log = 1;
goto done;
}
if (m->m_pkthdr.pf.flags & PF_TAG_GENERATED)
return (PF_PASS);
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
On 7 October 2009 c. 13:38:54 Henning Brauer wrote:
> * Vadim Zhukov [2009-10-07 10:30]:
> > Hello all again.
> >
> > Could anyone explain the reasons of the following difference? More
> > precisely:
> >
> > 1. Why does pf_test() add log flag PF_LOG_FORCE
uits, but the intro(2)
> description doesn't).
Maybe do not return error at all, just zero?
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Hello all.
Do not know where to send this patch, so sending here.
I updated Russian libc translation: fixed EREMOTE and added a bunch of
error codes too.
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad
g is in KOI8-R, yours seems to be something
> else?
Sorry, I forgot that I'm using UTf-8 by default for emails. Here it is in
KOI8-R, raw and Base64-encoded version (so it can be easily decoded and
applied).
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which p
;\0'" does not give any actual
speed gain.
Having that patch applied, mktemp(1) no longer segfaults for me.
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is th
ronment variable, say,
LIVEFASTDIEYOUNG. If it's not defined, or empty, then current, sane
defaults will be used in programs; otherwise, programs should go
searching the shortest way to strike yourself in the foot.
Then each program you want can be modified to depend on it:
const char *lfdy
rce code?
Yes, there is an error. Use random(3), as suggested in the rand(3).
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
On 7 February 2010 c. 22:57:31 Otto Moerbeek wrote:
> On Sun, Feb 07, 2010 at 08:54:04PM +0100, Otto Moerbeek wrote:
> > On Sun, Feb 07, 2010 at 10:42:40PM +0300, Vadim Zhukov wrote:
> > > On 7 February 2010 c. 21:59:33 Brad Tilley wrote:
> > > > I wrote a sma
On 8 February 2010 c. 21:00:53 Philip Guenther wrote:
> 2010/1/27 Vadim Zhukov :
> > Current implementation of mktemp_internal() access memory before the
> > string given when the whole template given consists of 'X'
> > characters.
>
> Nice catch! I've c
On 8 February 2010 c. 23:50:53 Philip Guenther wrote:
> 2010/2/8 Vadim Zhukov :
> > Thank you for your attention. And sorry, but I think that your
> > version is wrong: in case of only one "X" you'll have "tries" set to
> > 1 instead of NUM_CHARS.
ddress space of the process
starting at address addr and continuing for len bytes."
So either sys_mprotect(), uvm_map_protect() or man page is not correct.
As I'm totally newbie in UVM, please, do not bite me for the patch
proposed below. At least, very much. :)
--
Best wishes,
quot;The function
mprotect specifies the desired protection for the memory page(s)
containing part or all of the interval [addr,addr+len-1]".
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
ou fix that then, please?
> jmc
Maybe it's better to say that this is not treated as error too? See the
patch at the end of this letter.
> > 2010/2/11 Vadim Zhukov :
> > > Hello all.
> > >
> > > mprotect(2) says: "If len is 0, then action will
On 12 February 2010 c. 11:11:33 Jason McIntyre wrote:
> On Fri, Feb 12, 2010 at 10:57:32AM +0300, Vadim Zhukov wrote:
> > On 12 February 2010 ?. 10:42:09 Jason McIntyre wrote:
> > > On Thu, Feb 11, 2010 at 08:24:52PM -0500, Ted Unangst wrote:
> > > > The man page
but seen another one - about TAB _after_ exiting vi mode, will
investigate it later...)
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
w 0xf000 product ID; sorry, I forgot to run it
when three umsms and ucoms were attached. :(
The USB_PRODUCT_LONGCHEER_U12 code was taken from MS Windows Device
Manager (the modem runs fine there).
I'll try to buy another one but dunno how to send it to interested
person - I live in Moscow, Rus
Hello all, especially softraid(4) developers and j...@. :)
Looks like bio(4) is missing description of softraid(4)-specific ioctls:
BIOCCREATERAID, BIOCDELETERAID and BIOCDISCIPLINE. Here is a patch
proposal, feel free to fight me for it. :)
--
Best wishes,
Vadim Zhukov
A: Because
c dance, and now
things work as expected. The patch is at the end of letter.
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
hain - is
>> it right (method to do so)?
>>
>> Currently, it compiles, runs, but doesn't work - please do not actually
>> run this patch unless you want to duplicate my work. :)
>>
>> Thanks in advance.
>>
>> --
>> Best wishes,
>>
at 12:41:01PM +0400, Vadim Zhukov wrote:
>> Hm-m-m, could you explain better, please? I don't see the way to do
>> such filtering with diverting, excluding writing a proxy app listening
>> all the traffic.
>
> Why do you assume I'm excluding a proxy app?
>
>>
&
relayd(8). ;)
2010/6/13, Damien Miller :
> On Sun, 13 Jun 2010, Vadim Zhukov wrote:
>
>> No, no, it's me who is excluding this way. :) Moving packets through
>> userland and reimplementing states in the app is not the simpliest,
>> most reliable and - last but not leas
this way as it looked simple enough for me. To compare,
what's better, BPF or "hand-rolled" check, I need to see both
implementations. :) I'm doing this work in my spare time, and do not
bother about time as much as about getting reliable, compact, simple
and fast code.
--
WBR,
Vadim Zhukov
#x27;ll try. If anyone have any ideas
regarding implementation, I'll be glad to listen.
Thank you all who paid attention and responded!
--
WBR,
Vadim Zhukov
few IPSec
tunnels set up that are not used that much now, so I can experiment
freely, but only on my own side.
--
WBR,
Vadim Zhukov
pert in this area; 2) open
for improvements.
How to reproduce: tunefs /
Before patch:
tunefs: /dev/r286cb876606dc1e0.l: No such file or directory
After patch:
tunefs: /dev/sd0l: Device busy
Okay?
--
WBR,
Vadim Zhukov
Index: opendev.c
2016-01-20 1:10 GMT+03:00 Vadim Zhukov :
> Not all errors coming from diskmap should be overwritten.
> In particular, if we get EBUSY, that doesn't mean "try again with
> accessing /dev/foo, fail and return ENOENT instead".
>
> Maybe we should add more errors to
ch, since they also included a v_wstrdup
> function which takes CHAR_T, which in their code can be an u_char or a
> wchar_t depending on the compile options and I don't want to get entangled
> in there.
> The 6th patch should speak for itself.
Cool, thank you for work!
--
WBR,
Vadim Zhukov
things in case of ENOMEM. My point is that we should make them visible
first, by doing a simple, reviewable change like unmacrosing the C
module files, and only then remove/rework stuff.
--
WBR,
Vadim Zhukov
major bump?
Please note that some software doesn't zero out struct tm before
use, resulting in garbage being written to this field. If you'd
call the strftime() or wcsftime() on such struct, you'll get core
dumped (in the best case). I'm looking at you, Qt!
--
WBR,
to empty
string, as specified in strftime(3).
Okay for this version?
--
WBR,
Vadim Zhukov
Index: wcsftime.c
===
RCS file: /cvs/src/lib/libc/time/wcsftime.c,v
retrieving revision 1.6
diff -u -p -r1.6 wcsftime.c
--- wcs
cables from motherboard, to avoid
it generating electricity when spinning. I know two cases of killed this
way motherboards (not ThinkPad, but still).
--
WBR,
Vadim Zhukov
> 2 packets transmitted, 0 packets received, 100.0% packet loss :)
I see many people are doing something in persistent memory
subsystems now. Maybe this diff could get some attention now
as well. :) Resending the whole thing.
--
WBR,
Vadim Zhukov
Index: bioct
ar x ${_lib}.a
cc -shared -o $_lib $(ls *.so | sort -R) $(cat .ldadd)
[[ -s $_lib ]] && file $_lib | fgrep -q 'shared object'
LD_BIND_NOW=1 LD_LIBRARY_PATH=$_tmpdir awk 'BEGIN {exit 0}'
install -S -o root -g bin -m 0444 $_lib /usr/lib/$_lib
)
}
--
WBR,
Vadim Zhukov
for ESRCH to avoid going inside
kmem without real need.
Tested on amd64.
Comments? Okays?
--
WBR,
Vadim Zhukov
Index: sys/kern/kern_sysctl.c
===
RCS file: /cvs/src/sys/kern/kern_sysctl.c,v
retrieving revision 1.300
diff -u
+ SIZE_LEN;
> tracks[t].end = tracks[t].start + len;
> tracks[t].curtime = getvar(&tracks[t]);
> t++;
> }
>
--
WBR,
Vadim Zhukov
2016-05-03 1:04 GMT+03:00 Alexander Bluhm :
> On Sun, May 01, 2016 at 01:24:19AM +0300, Vadim Zhukov wrote:
>> When matching by PID, we'd better return ESRCH expicitly rather
>> than zero entries. This makes, for example, fstat(1) behaviour
>> more consistent and make
2016-05-03 1:19 GMT+03:00 Mark Kettenis :
>> Date: Tue, 3 May 2016 00:04:13 +0200
>> From: Alexander Bluhm
>>
>> On Sun, May 01, 2016 at 01:24:19AM +0300, Vadim Zhukov wrote:
>> > When matching by PID, we'd better return ESRCH expicitly rather
>>
section a bit up, IMHO, that makes more sense; but if any
our documentation maintainer will object, I'll revert, of course.
Okay to commit this version?
--
WBR,
Vadim Zhukov
Index: sys/kern/kern_sysctl.c
===
RCS file: /c
Is there any point in keeping lib/libc/regex/WHATSNEW? Okay to rm?
--
WBR,
Vadim Zhukov
Index: WHATSNEW
===
RCS file: WHATSNEW
diff -N WHATSNEW
--- WHATSNEW28 Apr 1997 20:44:56 - 1.3
+++ /dev/null 1 Jan 1970 00:00
This makes fstat(1) behave more like grep(1), regarding exit status.
The idea itself came from bluhm@.
For manpage, I mostly copied the text from grep(1), but changed
phrases talking about selected lines to matching processes. Or
should those be selected processes?..
--
WBR,
Vadim Zhukov
Let's make it more informative and smaller size at the same time?
Index: install.sub
===
RCS file: /cvs/src/distrib/miniroot/install.sub,v
retrieving revision 1.958
diff -u -p -r1.958 install.sub
--- install.sub 24 Jan 2017 10:14:14 -
2017-05-27 22:45 GMT+03:00 Joerg Jung :
> Hi,
>
> I think devel/waf is gone since two years and may not come back, so no
> need to mention in port-modules(5).
>
> OK?
Yes, and don't forget to bring some gas for nice burning!
the firmware.
>
> This might silence some error messages people have seen with iwm(4).
>
> Briefly tested on an 8260 device.
Seems correct to me.
--
WBR,
Vadim Zhukov
wing
change, which likely worths getting upstream as well.
--
WBR,
Vadim Zhukov
Index: __config
===
RCS file: /cvs/src/lib/libcxx/include/__config,v
retrieving revision 1.3
diff -u -p -r1.3 __config
--- __config19 Sep 2016 22:1
2017-05-28 18:16 GMT+03:00 Ted Unangst :
> Vadim Zhukov wrote:
>> While working on getting Boost & its friends work under Clang,
>> I've stumbled upon the code that looks like the following:
>>
>>decltype(x, y) z = w;
>
> why not espie's fix from
2017-05-28 18:35 GMT+03:00 Vadim Zhukov :
> 2017-05-28 18:16 GMT+03:00 Ted Unangst :
>> Vadim Zhukov wrote:
>>> While working on getting Boost & its friends work under Clang,
>>> I've stumbled upon the code that looks like the following:
>>>
>>&
2017-05-28 18:32 GMT+03:00 Mark Kettenis :
>> From: "Ted Unangst"
>> Date: Sun, 28 May 2017 11:16:21 -0400
>>
>> Vadim Zhukov wrote:
>> > While working on getting Boost & its friends work under Clang,
>> > I've stumbled upon the code
ata
fails with error:
$ ksh tt.sh
./tt.sh[4]: syntax error: `;;' unexpected
What's worse, it fails even if I comment the line it's whining after.
So... okay to add a regression test?
--
WBR,
Vadim Zh
f a patch like
that would be acceptable? And if yes, how do you want it look like
to make supporting it easier?
Thank you in advance.
--
WBR,
Vadim Zhukov
Index: tools/clang/lib/Driver/ToolChain.cpp
===
RCS file: /cvs/src/gnu/ll
2017-05-29 20:26 GMT+03:00 Vadim Zhukov :
> The clang and gcc behave differently regarding executing tools.
> While gcc simply runs what he said to, clang tries to be clever
> and always find absolute path for a tool, refusing start otherwise.
>
> The actual problem is starting
2017-05-29 20:54 GMT+03:00 Stuart Henderson :
> On 2017/05/29 20:26, Vadim Zhukov wrote:
>> The clang and gcc behave differently regarding executing tools.
>> While gcc simply runs what he said to, clang tries to be clever
>> and always find absolute path for a tool, ref
2017-05-29 21:14 GMT+03:00 Mark Kettenis :
>> From: Vadim Zhukov
>> Date: Mon, 29 May 2017 20:29:20 +0300
>>
>> 2017-05-29 20:26 GMT+03:00 Vadim Zhukov :
>> > The clang and gcc behave differently regarding executing tools.
>> > While gcc simply runs
2017-07-16 14:55 GMT+03:00 Klemens Nanni :
> On Sun, Jul 16, 2017 at 10:26:25AM +, Robert Peichaer wrote:
>> But I'd like to stay strict matching the filenames.
>>
>> + for _liba in /usr/lib/lib{c,crypto}; do
>> + _libas="$_libas $(ls $_liba.so.+([0-9.]).a | sort -V | tail
>> -
2017-07-17 14:03 GMT+03:00 Klemens Nanni :
> On Mon, Jul 17, 2017 at 11:57:02AM +0300, Vadim Zhukov wrote:
>> > + for _liba in /usr/lib/lib{c,crypto}; do
>> > + _libas="$_libas $(ls $_liba.so.+([0-9.]).a | sort -V |
>> > tail -1)"
>&g
> + pass out proto carp !received-on any keep state (no-sync)"
> +
> + # Don't kill NFS.
> if [[ $(sysctl vfs.mounts.nfs 2>/dev/null) == *[1-9]* ]]; then
> - # Don't kill NFS.
> - RULES="set reassemble yes no-df\n$RULES"
> - RULES="$RULES\npass in proto { tcp, udp } from any port {
> sunrpc, nfsd } to any"
> - RULES="$RULES\npass out proto { tcp, udp } from any to any
> port { sunrpc, nfsd } !received-on any"
> + RULES="set reassemble yes no-df
> + $RULES
> + pass in proto { tcp, udp } from any port { sunrpc, nfsd } to
> any
> + pass out proto { tcp, udp } from any to any port { sunrpc,
> nfsd } !received-on any"
> fi
> print -- "$RULES" | pfctl -f -
> pfctl -e
I like this, okay zhuk@.
--
WBR,
Vadim Zhukov
strib/sets/lists/comp/mi, but otherwise works fine here.
--
WBR,
Vadim Zhukov
2017-07-29 2:15 GMT+03:00 Андрей Болконский :
> sorry. correct patch:
>
> 2017-07-28 23:52 GMT+03:00 Андрей Болконский :
>
>> This header not used since retire sparc.
>> build amd64 is ok
Committed, thanks.
--
WBR,
Vadim Zhukov
2016-05-21 23:49 GMT+03:00 Martin Natano :
> VOP_ALLOCBLKS() and related code is unused since the removal of
> cluster_write(). This diff even shrinks /bsd by 8kb. Ok?
Unless someone really wants to reuse this code, it obviously serves no
purpose. Nice finding! :)
okay@ zhuk
didn't document all of the flags involved in mount calls, since
some of them are purely kernel internal. But I could easily miss
something crucial...
So this is my first public draft of mount(2) patch. Looking for
comments & thanks in advance!
--
WBR,
Vadim Zhukov
Index
descriptions of the MNT_FORCE and MNT_UPDATE flags were reworked
and moved to separate paragraphs.
Okay to commit?
--
WBR,
Vadim Zhukov
Index: mount.2
===
RCS file: /cvs/src/lib/libc/sys/mount.2,v
retrieving revision 1.46
diff
Hi all.
I had to dig into sa sources to get know what trailing '*' in
command names mean. IMHO, that's not how manuals should work. :)
Okay?
--
WBR,
Vadim Zhukov
Index: sa.8
===
RCS file: /cvs/src/usr.sbin/sa/sa
1 - 100 of 284 matches
Mail list logo
