dev/console 2>&1' ERR
> -trap 'logger -t $PROGNAME "kernel relinking done"' EXIT
> +trap 'trap - EXIT
> + logger -st $PROGNAME "$ERRMSG" 2>/dev/console
> + restore_mount' ERR
> +trap 'logger -t $PROGNAME "kernel relinking done"
> + restore_mount' EXIT
>
> # Create kernel compile dir and redirect stdout/stderr to a logfile.
> mkdir -m 700 -p $KERNEL_DIR/$KERNEL
>
>
--
Thomas de Grivel
https://www.kmx.io
k < 2) {
- sr_error(sd->sd_sc, "%s requires two or more chunks",
+ if (no_chunk < 1) {
+ sr_error(sd->sd_sc, "%s requires one or more chunks",
sd->sd_name);
r
ss those warnings.
> >
> > I can't reproduce this using clang (base or ports) or gcc (base or
> > ports) using -Wall, -Wextra and -Wunused-parameter. But since you
> > haven't provided any details, we just have to guess at what you are
> > doing.
>
> Or not guess, but simply delete the mail
--
Thomas de Grivel
kmx.io
Actually I see the same problem on 6.6-stable :
including readline/readline.h produces warnings.
Any -Werror hope some day ?
cheers
Le mer. 4 mars 2020 à 13:41, Thomas de Grivel a écrit :
>
> With latest OpenBSD snapshot on amd64
>
> In file included from /usr/include/readline/c
video1
Le jeu. 23 janv. 2020 à 04:51, Thomas Frohwein
a écrit :
>
> On Tue, Jan 21, 2020, at 7:10 PM, Mark Kettenis wrote:
> > The attached diff fixes amdgpu(4) and might very well fix radeondrm(4)
> > as well.
> [...]
>
> For the record, this fixes running piglit with radeon on my HD7570 since this
> was committed. It used to lock up on the test spec/arb_sync/sync_api, but
> now piglit completes. I haven't done further investigations how that may be
> related, but though it may be good to know that this means progress with
> the piglit testing suite.
> --
>
> tfrohw...@fastmail.com
>
> PGP Public Key:
> https://pgp.mit.edu/pks/lookup?op=get&search=0xE1A22D58D20C6D22
>
--
Thomas de Grivel
kmx.io
My bad, SBCL uses the libc's wrappers indeed looking at the sources.
Le ven. 29 nov. 2019 à 22:41, Josh Elsasser a écrit :
>
> On Fri, Nov 29, 2019 at 10:12:10AM +0100, Thomas de Grivel wrote:
> > Maybe Go is not the only problem, I see SBCL compiling syscalls too.
> >
>
egitimate compelling reasons to avoid calling the libc stubs?
> I don't believe so. Especially if those segments are in network facing
> programs and/or generated on the fly. At worst a nasty JIT can generate code
> to call & of libc syscall(2) stub with SYS_* symbolic names. That approach
> remains simple and workable for the developer, but somewhat more difficult for
> an attacker who not know the relevant locations.
>
--
Thomas de Grivel
kmx.io
plus it's really 6 new lines in rc.subr, no big deal.
Le mar. 4 sept. 2018 à 10:53, Thomas de Grivel a écrit :
>
> why ? well all interactive process get a quarter range nice priority
> advance compared to all daemon tasks, at least for a laptop
> environment it really makes
ter, but
if you don't like it nobody foces you huh ?
--
Thomas de Grivel
http://kmx.io
Le mar. 4 sept. 2018 à 07:57, Alexandre Ratchov a écrit :
>
> On Tue, Sep 04, 2018 at 04:58:53AM +0200, Thomas de Grivel wrote:
> >
> > And I still feel the default nice priority
at 10:34:51PM +0200, Thomas de Grivel wrote:
> > Hello,
>
> Hi.
>
> > Following patch allows sysadmins to configure nice values for RC daemons.
> > Default nice value is set to 10 as I wish to prioritize interactive
> > applications over system daemons and I think m
Le lun. 3 sept. 2018 à 23:33, Philip Guenther a écrit :
>
> On Mon, Sep 3, 2018 at 11:46 AM Thomas de Grivel wrote:
>>
>> I was browsing the DRM code ported from Linux and it's a terrible
>> mess, is there any ongoing project to clean up that codebase or
>
I was browsing the DRM code ported from Linux and it's a terrible
mess, is there any ongoing project to clean up that codebase or
rewrite it entirely ?
--
Thomas de Grivel
me know if it is of any interest to you.
commit 1f4121df3ae31121d435571ffdbd93a20c1e8a07
Author: Thomas de Grivel
Date: Mon Sep 3 21:52:37 2018 +0200
Add a $daemon_nice parameter.
If not overriden by the launched daemon the default nice value is 10.
See nice(1) for more details
error
message, and not bury it inside a bunch of informations about the
interface. Now if the rest is sent to stdout it's easy to send it to
/dev/null and just get the error message.
--
Thomas de Grivel
Hi,
Index: ifconfig.c
===
RCS file: /cvs/src/sbin/ifconfig/ifconfig.c,v
retrieving revision 1.252
diff -u -p -r1.252 ifconfig.c
--- ifconfig.c26 Nov 2011 23:38:18 -1.252
+++ ifconfig.c30 Nov 2011 14:35:52 -
@@ -216
/include/netinet6/in6.h:823: error: expected declaration specifiers
or '...' before 'socklen_t'
/usr//include/netinet6/in6.h:823: error: expected declaration specifiers
or '...' before 'u_int8_t'
/usr//include/netinet6/in6.h:824: error: expected declaration specifiers
or '...' before 'socklen_t'
/usr//include/netinet6/in6.h:825: error: expected declaration specifiers
or '...' before 'socklen_t'
/usr//include/netinet6/in6.h:825: error: expected declaration specifiers
or '...' before 'u_int8_t'
/usr//include/netinet6/in6.h:826: error: expected declaration specifiers
or '...' before 'socklen_t'
/usr//include/netinet6/in6.h:827: error: expected declaration specifiers
or '...' before 'socklen_t'
/usr//include/netinet6/in6.h:829: error: expected '=', ',', ';', 'asm'
or '__attribute__' before 'inet6_rth_space'
/usr//include/netinet6/in6.h:830: error: expected declaration specifiers
or '...' before 'socklen_t'
Including before makes it ok.
So either the manual is wrong
or sys/socket.h or netinet/in.h is wrong.
--
Thomas de Grivel
http://b.lowh.net/billitch
"I must plunge into the water of doubt again and again."
Le 08/25/11 14:44, Thomas de Grivel a icrit :
Hi,
From ip(4) :
SYNOPSIS
#include
#include
However this fails :
$ cat > ip.c
#include
#include
int main() {
return 0;
}
^D
$ gcc ip.c
In file included from ip.c:1:
/usr//include/sys/socket.h:105: error: expected specifier-qualifier-l
Hi
I'd like to donate a small patch to share/man/man5/forward.5
It explains the \user syntax a bit more explicitly.
Cheers
--
Thomas de Grivel
http://b.lowh.net/billitch
"I must plunge into the water of doubt again and again."
--- forward.5.~1.9.~Wed May 4 17:24:22 201
First: double checking is far from bad,
second: a test is much faster than a function call.
On 09/28/10 13:40, Vladimir Kirillov wrote:
Hello, t...@!
Subj, cpu_unidle() does that check itself.
Index: i386/machdep.c
===
RCS file: /
On 08/17/10 12:49, Nick Holland wrote:
On 08/17/10 03:24, Thomas de Grivel wrote:
For the record, i met a couple problems with the snapshot install
- when selecting custom layout of an existing OpenBSD partition, the
disklabel utility had kept the mount points from the auto layout, and
be configurable but asked for IP
configuration, but i guess this is expected and that there is no support
for wireless installation.
The rest of the install went real smooth, as usual.
--
Thomas de Grivel
http://b.lowh.net/billitch
+++ diff.1 15 Aug 2010 14:26:46 -
@@ -465,6 +465,7 @@ Differences were found.
An error occurred.
.El
.Sh SEE ALSO
+.Xr patch 1 ,
.Xr cmp 1 ,
.Xr comm 1 ,
.Xr diff3 1 ,
--
Thomas de Grivel
22 matches
Mail list logo
