Theo de Raadt wrote:
> If you are going to introduce such complicated semantics, please
> include a proposal for the manual page change so that we can see
> if this can be simply described. Being dimply described in the
> manual page is a marker for whether a change is suitable.
Stealing some
Daniel Jakots wrote:
> Hi,
>
> With nc(1) you can do:
> nc -zv example.com 80
> or
> nc -zv example.com http
> which does the same. This works well unless the service name has a dash:
> $ nc -zv example.com syslog-tls
> nc: service "tls" unknown
>
> This is because nc(1) is able to do some port
Ingo Schwarze wrote:
> What about making -O style= *compulsory* unless "option style" is
> defined in man.conf(5)? Just error out when no style sheet is
> configured? That can be combined with inlining the full set of
> rules when -O style=inline is explicitly specified.
This seems
Ingo Schwarze wrote:
> 2. When calling "mandoc -T html" without specifying "-O style=",
> fall back to "-O style=/var/www/htdocs/mandoc.css" by default.
> That might be sensible because it is adequate for local
> viewing of the file, which is likely intended with files
> generated
Raphael Graf wrote:
> The diff inserts some space above the footer.
> This improves readability and makes it similar to the other output formats.
>
> Here is an example found in the wild, demonstrating the problem:
> https://webassembly.github.io/wabt/doc/wasm-objdump.1.html
So I think one
Jan Klemkow wrote:
> I run into double definition problems because of a missing include guard
> in dev/biovar.h. The diff below should fix that issue.
Where and how? I don't like adding guards blindly because it leads to laziness
and eventually the include situation is a giant tangled mess. Each
Otto Moerbeek wrote:
> That would boil down to this,
>
> ok?
ok with me
Marc Espie wrote:
> Well, apart from the bike-shedding, it seems like the most correct
> short-term solution.
>
> So I will commit it tomorrow, unless someone has an actual better idea.
Nobody answered if SUDO_CLEAN is actualy set. I checked. It's not.
Index: Makefile
Otto Moerbeek wrote:
> int
> biosd_diskio(int rw, struct diskinfo *dip, u_int off, int nsect, void *buf)
> {
> - return biosd_io(rw, >bios_info, off, nsect, buf);
> + int i, n, ret;
> +
> + /*
> + * Avoid doing too large reads, the bounce buffer used by biosd_io()
> + *
Klemens Nanni wrote:
> On Tue, Dec 11, 2018 at 10:31:37PM -0500, Ted Unangst wrote:
> > I have some trace files that are gzipped to save space. (They compress
> > really
> > well.) It would be convenient if I could simply zcat them into kdump for
> > inspection.
> F
Marc Espie wrote:
> There is a kind of mixed model there.
>
> Because make build still goes thru regress for obj and cleandir
>
> Yet the rest of the build doesn't!
>
> So, if we agree that it needs to stay the way it currently is, then
> the SUDO in that Makefile might trigger while running as
I have some trace files that are gzipped to save space. (They compress really
well.) It would be convenient if I could simply zcat them into kdump for
inspection.
This patch allows -f - to read from stdin. (Curiously, kdump always reads from
stdin, but uses freopen on the trace file.)
Unsure
Marc Espie wrote:
> > > - try to remove the files normally first
> > > rm -f ${SUDO_CLEAN} || test -z "${SUDO}" || ${SUDO} rm -f
> > > ${SUDO_CLEAN}
> > >
> > > this should actually fix the issue.
> > >
> > > Any other directory with that problem ?
> >
> > that fix the issue and the
Mark Kettenis wrote:
> > From: "Ted Unangst"
> > Date: Mon, 10 Dec 2018 14:14:08 -0500
> > Content-Type: text/plain; charset=utf-8
> >
> > So I was actually looking at the passwd check rules because I wanted
> > to add a flag to disable the 3 bad
Solene Rapenne wrote:
> Not sure how to fix it. Maybe people shouldn't try to compile as root when
> having SUDO=doas set and then, it's not an issue anymore?
yeah, i would say this is an issue of your own making. you ask to use doas,
make is going to use doas.
So I was actually looking at the passwd check rules because I wanted to add a
flag to disable the 3 bad passwords then ok whatever.
This adds passwd -w to allow user to skip the default 3 warnings and just do
what they want. If, by chance, you have configured warnings in login.conf then
they
if MAIL is unset, we can short circuit the check a little bit.
Index: mail.c
===
RCS file: /cvs/src/bin/ksh/mail.c,v
retrieving revision 1.24
diff -u -p -r1.24 mail.c
--- mail.c 25 Jun 2018 15:22:30 - 1.24
+++ mail.c
These patterns try to detect a1a1a1 style passwords. By making the regex a bit
more flexible we can just use one. Also now catches mMmMmM fwiw.
Index: pwd_check.c
===
RCS file: /cvs/src/usr.bin/passwd/pwd_check.c,v
retrieving
Heppler, J. Scott wrote:
> Is there interest in installing/booting OpenBSD on eMMC?
this is expected to work.
ktrace -C will return an error if you don't have a ktrace.out file because
sys_ktrace tries to open it whenever it has a filename, even if it won't be
used. I think it is more consistent to require it be null, so that we aren't
opening files we won't be using.
man page and utility diff below.
Jason McIntyre wrote:
> On Thu, Dec 06, 2018 at 10:21:47PM +1100, Ross L Richardson wrote:
> >
> > The number is in seconds, but that's currently not specified.
> >
> > Wording which preserved "frequency" but made sense with "seconds"
> > eluded me, so I changed things to refer to "interval".
>
Seen in the wild. Alias for ! that's friendlier to the shell.
Index: find.1
===
RCS file: /cvs/src/usr.bin/find/find.1,v
retrieving revision 1.95
diff -u -p -r1.95 find.1
--- find.1 1 Aug 2018 07:09:15 - 1.95
+++
Developers who shall remain anonymous were confused by the behavior of apmd -d
because the behavior of apmd -d is confusing. It doesn't do anything like any
other daemon in the system when running with -d.
This introduces a logmsg function to replace syslog, which will either syslog
or printf
Klemens Nanni wrote:
> On Thu, Nov 29, 2018 at 02:50:58PM -0500, Ted Unangst wrote:
> > I would find it useful to know battery percentage at the time of suspend and
> > resume. This makes it possible to see how much battery was consumed while
> > sleeping. I don't think this
I would find it useful to know battery percentage at the time of suspend and
resume. This makes it possible to see how much battery was consumed while
sleeping. I don't think this is much noisier than things already are.
Index: apmd.c
6 tedu Exp $ */
+/*
+ * Copyright (c) 2018 Ted Unangst
+ *
+ * Permission to use, copy, modify, and distribute this software for any
+ * purpose with or without fee is hereby granted, provided that the above
+ * copyright notice and this permission notice appear in all copies.
+ *
+ * THE SOFTWARE I
Edgar Pettijohn III wrote:
> remove a bunch of `_' where there shouldn't be `_'s
please resend without nonbreaking spaces breaking the diff.
Mark Kettenis wrote:
> SENSOR_VELOCITY would make sense. It should be m/s with some
> appropriate scaling. We don't need to represent speeds higer than
> 299792458 m/s, so micrometers per second would be a good choice.
is it reasonable to use mm/s so that distance and velocity are consistent?
Klemens Nanni wrote:
> Prompted by tedu@'s recent reply, here's a fix for getent(1) to lookup
> keys as UIDs only if the username lookup fails to prevent clobbering
> numerical usernames.
yes, this is how it should be. please fix group lookup as well.
Klemens Nanni wrote:
> On Thu, Nov 01, 2018 at 02:56:38PM -0400, Ted Unangst wrote:
> > this looks to be in the wrong order. if 1000 is a username, that should be
> > matched first before numeric lookup.
> Preferring UIDs indeed clobbers usernames with the respective nu
Klemens Nanni wrote:
> This makes `top -U 0' and "u-1000" work.
>
> Overview:
>
> "kn" ok"10kn"ok if "10kn" exists else error
> "-kn"ok"-10kn" ok if "10kn" exists else error
> "1000" ok"--1000" error, negative UID and "-1000" not valid
>
Rian Hunter wrote:
> Another gentle bump on this patch:
this looks about right.
Dave Cameron wrote:
> doas(1) currently states:
> -clip-
> EXIT STATUS
> The doas utility exits 0 on success, and >0 if an error occurs. It may
> fail for one of the following reasons:
>
> o The config file /etc/doas.conf could not be parsed.
> o The user attempted to run
Anton Lindqvist wrote:
> > > > Since it's a daemon I guess it makes sense to continue execution instead
> > > > of dying. However, we should make sure to not leak memory along the
> > > > error paths. Also, log something when preloading the cache fails.
>
> Committed, I settled on using goto.
Brent Cook wrote:
> On Mon, Feb 12, 2018 at 09:27:16AM -0600, ed...@pettijohn-web.com wrote:
> > Has there been any discussion of packaging libtls separately from libressl
> > for portable use? With my limited skills I was able to write a program to
> > talk to smtpd and starttls using nothing
Neeraj Pal wrote:
>
> In file included from /usr/src/sys/kern/sys_test.c:4:
> /usr/src/sys/sys/syscallargs.h:153:13: error: unknown type name
> 'socklen_t'; did you mean '__socklen_t'?
Your includes are in the wrong or some are missing. I think you should start
by adding code to a file that
Neeraj Pal wrote:
> 4) echo "file kern/sys_hello.c" >> /usr/src/sys/conf/files
>
> 5) cd /usr/src/sys/arch/amd64/compile/CUSTOM.MP/
>
> 6) make obj && make -j4
>
> And, then, It throws an error given below,
>
> "
> ld -T ld.script -X --warn-common -nopie -o bsd ${SYSTEM_HEAD} vers.o ${OBJS}
>
Sebastien Marie wrote:
> Assuming the check on protection is a bit too restrictive, and it is
> fine to have some chunks with PROT_NONE, I think we want something like:
are readonly stacks meaningful? if so, we should fix that too now instead of
waiting.
>
> Index: uvm/uvm_map.c
>
Job Snijders wrote:
> I’m not great at math, with a 16 bit random value, wouldn’t we start
> running into ID collisions around 256 concurrent ping processes? Perhaps
> that already is the case today and this patch does nothing to improve that,
> but also doesn’t make it worse.
what we need is an
Mark Kettenis wrote:
> We should allways use mmio instead of io if possible. The cascading
> if statements are a bit ugly, but I can't come up with a better solution.
mapped = 0;
if (pcimap() == 0)
mapped = 1;
if (!mapped && pcimap() == 0)
Franco Fichtner wrote:
> What can we do to help?
Write smaller code...
Delan Azabani wrote:
> Are there any interesting reasons behind this difference (aside from
> a simple mistake in either the implementation or the paper)?
>
> Does the difference in order have any cryptanalytic implications (it
> would surprise me if there were, but I’m not really a
Mateusz Guzik wrote:
> As the subject states. By the time the code gets to copyout, buf is
> already populated. Clearing it only if copyout succeeds looks like a
> braino, thus the following trivial proposal:
If the secret random data is not copied out, it will not be used, and there's
nothing to
Martin Pieuchot wrote:
> Diff below moves some job control bits out of exit1(). It is extracted
> from guenther@'s proctreelk diff. It's currently a noop so I'd like to
> get it in to reduce the locking diff.
>
> ok?
i misread subject as kill objc, but ok anyway.
Martijn van Duren wrote:
> Some manpage nits found by jmc.
heh, was about to say the same. not a big systat user, but
i don't see why not.
ok
>
> Index: engine.c
> ===
> RCS file: /cvs/src/usr.bin/systat/engine.c,v
> retrieving
Martin Pieuchot wrote:
> Diff below shuffles sys_socket() to look like sys_socketpair().
>
> The goal is to do socket operations first in both functions. Since
> they don't need the KERNEL_LOCK(), we will be able to mark the syscalls
> NOLOCK and only grab it before messing with file
Theo Buehler wrote:
> The diff below only skips 6 letters if they actually are '--- a/' or
> '+++ b/' and seems to do the trick for me in various scenarios.
asymptotically approaching correct, i like it.
Alexander Kuleshov wrote:
> pipe()/pipe2() system calls may fail now with ENOMEM error during creation in
> pipe_create() -> pipespace(). The bellow diff replaces ENOMEM with ENFILE
> errno which is already documented for pipe()/pipe2() to decrease amount of
> possible errno(s) with similar
Jeremie Courreges-Anglas wrote:
>
> I don't think anything has been committed regarding this issue, right?
this looks ok to me.
Stefan Sperling wrote:
> Or is modifying ifconfig sufficient?
> We are more concerned about textual display rather than the
> kernel/userland ioctl boundary, correct?
>
> The option list for ifconfig is [-AaC]. Plenty of letters available.
> We could add:
>
>-P Show authentication details
Ingo Schwarze wrote:
> [EILSEQ]
> A wide-character code that does not correspond to a valid
> character has been detected.
>
> That means that the functions are *required* to fail ("shall fail")
> if encoding errors can be detected, that -1 must be returned, and
> that errno must
Stuart Henderson wrote:
> I have been bumping into maxproc limits a lot recently on my
> workstation. While I do have quite a lot of processes at times, I don't
> think I have quite been tripping into the limits of number of actual
> processes.
>
> It seems that perhaps threads are counted
Otto Moerbeek wrote:
> Hi,
>
> Malloc maintains a list if 16 slots of chunks to be freed. On free a
> chunk is put in a random slot and the existing chunk in that slot is
> actually freed. Currently, the code only checks the slot selected for
> a double free.
>
> This diff adds code to check all
Raf Czlonka wrote:
> This is unrelated to your diff but what I do instead is to check
> the BUILDINFO file - it's tiny and all the information you need,
> is already there.
While we're on the subject, I'll point out that sometimes only the base sets
change, but not the x sets. If you download
Jesper Wallin wrote:
> On Tue, Aug 15, 2017 at 07:24:47PM -0400, Ted Unangst wrote:
> > this looks good. will commit soon.
> >
> > (one nit, i'll correct, is man page options are upper case first.)
>
> Sorry if this comes on as a bit pushy, but any news here? I don't
make things a little more convenient.
a backslash indicates escape, which we don't need to support for keywords. so
always set nonkw for those tokens. this lets "permit \permit" work.
there are no keywords after the args keyword, so we can create a lexer
backdoor. this lets "permit user cmd ls
Jesper Wallin wrote:
> On Sun, Aug 13, 2017 at 09:52:22AM +0200, Martijn van Duren wrote:
> > I've also been bitten by this a couple of times, but you can also solve
> > this via the sensorsd framework, which is how I've done it.
>
> Yeah, someone on IRC also suggested sensorsd or even ksh and a
Jesper Wallin wrote:
> On Mon, Aug 14, 2017 at 05:12:05PM +0200, Klemens Nanni wrote:
> > Personally I'd also prefer having this in apmd(8) rather than some other
> > daemon or script. Some comments:
> >
> > You should pass optarg instead of errstr to error(). Either ways error()
> > will still
Ted Unangst wrote:
> Martin Pieuchot wrote:
> > I'd like to improve the fairness of the scheduler, with the goal of
> > mitigating userland starvations. For that the kernel needs to have
> > a better understanding of the amount of executed time per task.
> >
> >
Martin Pieuchot wrote:
> I'd like to improve the fairness of the scheduler, with the goal of
> mitigating userland starvations. For that the kernel needs to have
> a better understanding of the amount of executed time per task.
>
> The smallest interval currently usable on all our architectures
Klemens Nanni wrote:
> > + case 'z':
> > + autoaction = AUTO_SUSPEND;
> > + autolimit = strtonum(optarg, 1, 100, );
> > + if (errstr != NULL)
> > + error("invalid percent: %s", errstr);
> > +
Alexander Bluhm wrote:
> On Sun, Aug 13, 2017 at 05:20:05PM -0400, Ted Unangst wrote:
> > - if (nmp->nm_sotype != SOCK_STREAM)
> > - panic("nfscon sotype");
> > + } else {
> > + panic("nfscon sotype&quo
discovered this looking at something else. we don't and won't support
seqpacket for nfs sockets.
perhaps a bit more can be cleaned up too. i don't think we support any stream
sockets that don't require connections, etc...
Index: nfs_socket.c
adds fktrace syscall. currently with same behavior (regular files only) as
existing code.
tested with ktrace and...
#include
#include
#include
#include
#include
int
main()
{
int fd;
fd = open("ledump", O_CREAT, 0666);
syscall(113, fd, KTROP_SET, KTRFAC_NAMEI,
this moves writes into a thread. we need to do reads too, but the write side
is much easier... could use a little more testing.
Index: virtio.c
===
RCS file: /cvs/src/usr.sbin/vmd/virtio.c,v
retrieving revision 1.49
diff -u -p
Adam Steen wrote:
> I initially thought the calibration would take place at line 470 of
> amd64/identcpu.c
> (https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/arch/amd64/amd64/identcpu.c?annotate=1.87)
>
> But I looked into using the acpihpet directly but it is never exposed
> outside of
Joerg Sonnenberger wrote:
> On Wed, Aug 02, 2017 at 09:03:30PM +0200, Mark Kettenis wrote:
> > Couldn't convince clang not to inline duplicateFun() into bbTest2().
> > Splitting things out in a seperate file avoids the issue. Fixes the
> > regression test.
>
> Have you tried the combiniation of
Mark Kettenis wrote:
> FAIL libexec/ld.so/dlclose/test1/prog3/prog3
>
> This fails because clang doesn't respect ELF interposition:
>
> http://lists.llvm.org/pipermail/llvm-dev/2016-November/107625.html
>
> We generally frown upon interposition so I can have some sympathy
> for their
Florian Obser wrote:
> OK florian@
>
> p.s. whoever commits this please add extra ( ) around the && term,
> Apparently clang no longer supports operator precedence *sigh*.
>
> I'm wondering if it also warns for a * b + c
>
> /usr/src/usr.sbin/httpd/server_fcgi.c:665:56: warning: '&&' within
Ingo Schwarze wrote:
> So i say in all cases above, return -1, set ENOMEM, and it doesn't
> matter much whether anything is printed, except that asprintf(3)
> must of course free(3) any allocated memory before returning and
> set the pointer to NULL.
yeah. the number of bytes returned seems like
Klemens Nanni wrote:
> usage() never returns, all functions are to be used within this unit
> only.
>
> Since changes are conflicting, I'll wait for this diff first, but I'd
> like to remove the void casts for fprintf and use getprogname(3) over
> __progname as well.
>
> Feedback? Comments?
I
Scott Cheloha wrote:
> crypt_newhash(3) will return -1 and set errno to EINVAL if hashsize is
> too small to accommodate bcrypt's hash space. I imagine this would
> also be the case if anything other than bcrypt were supported.
i went ahead and reworked the page a bit. i think it clarifies a few
David CARLIER wrote:
> Hi.
>
> I sent a diff originally to a smaller audience but finally decided to post
> it in the mailing list.
> So it is to introduce the pthread_set_name_np's counterpart so
> pthread_get_name_np.
> Some softwares use it (NSPR for example) and anyway internally in my
>
David Gwynne wrote:
> secondly, im always wary of truncating hash output in case it throws away
> some of the guarantees it's supposed to provide. if you cut sha512 output
> down to an 8th of its size, is it 8 times easier to calculate a collision, or
> more than 8 times easier? sha384 being a
Martin Natano wrote:
> Go ahead replacing machdep.lidsuspend with cpu.lidaction. OpenBSD 6.1
> contains both MIBs, so there is a clear path for migration.
i have updated my sysctl.conf. fire away!
Ingo Schwarze wrote:
> Hi,
>
> Ted Unangst wrote on Tue, Jul 11, 2017 at 09:41:36AM -0400:
>
> > and it always sucks to lose information if somebody went to the
> > trouble of recording the necessary accents already.
>
> So here is a patch that makes putting U
Anthony J. Bentley wrote:
> "Ted Unangst" writes:
> > Anthony J. Bentley wrote:
> > > Hi,
> > >
> > > "Punctuation followed by backspace" hasn't been the right way to enter
> > > accents for a long time.
> >
&g
Anthony J. Bentley wrote:
> Hi,
>
> "Punctuation followed by backspace" hasn't been the right way to enter
> accents for a long time.
hard to see what the diff is doing since i coudn't see the backspaces. :)
do we want to delete them? or replace them with proper utf-8 sequences?
Matthew Martin wrote:
> Since __progname is not exposed in stdlib.h, use getprogname(3) instead.
> While here remove the useless cast.
yes. i also removed the declaration a few lines above.
> If this is ok, I'd like to also replace the uses of __progname
> throughout the tree with getprogname().
Mark Kettenis wrote:
> This diff has been in snaps for a while now. This matches what
> several major Linux distros do.
>
> ok?
for those of us who haven't memorized hex PCI IDs, can we add a comment
indicating the codename of the cutoff? broadwell or skylake or whatever?
everything becomes
i've found ktrace of libevent to be a little noisy and hard to read because it
always passes in a changes pointer to kevent, even with a count of 0. this is
just a tiny change to pass NULL in that case, so that kdump doesn't spit out
big hex numbers at me.
Index: kqueue.c
Olivier Antoine wrote:
> Hi all,
>
> Recently a bug has been identified in Tor:
>
> https://trac.torproject.org/projects/tor/ticket/22789
>
> As comments were made, questions were raised about the use of strtol(3),
> the different interpretations of the standard and their implementation.
>
>
Denis wrote:
> Looking for ifconfig '[[-]txpower dBm]' option which was present in
> OpenBSD 5.4 amd64. Try to find 'txpower' on 6.0 amd64 but seems it
> missed out.
>
> Actively using it to match power for 802.11 card and it's RF recipient
> (post amp). What mechanism of output power matching is
I received a similar diff from Angelos a while back, though I turned it down
on the grounds that rebound wasn't ready to be a recursive resolver. But I
think we're in better shape now.
This adds a -l address option to specify the listening address, turning
rebound into a lightweight partial
If the username starts with a digit, but isn't a number, treat it like root.
Index: doas.c
===
RCS file: /cvs/src/usr.bin/doas/doas.c,v
retrieving revision 1.72
diff -u -p -r1.72 doas.c
--- doas.c 27 May 2017 09:51:07 -
Ricardo Mestre wrote:
> Of course the diff still may make sense if working with different bases,
> apart from 10, is not required anymore.
i had a glance through and didn't see any that made sense to keep support for
octal or hex. was hoping a more serious brconfig user would also take a look
at
Peter Piwowarski wrote:
> At present, what exactly was patched is not immediately obvious from
> syspatch output, which could be annoying for administrators who want to
> take some action based on what was changed (restart daemons linked to
> patched libraries, etc). Could a -v option for syspatch
Stuart Henderson wrote:
> On 2017/06/27 18:11, Ted Unangst wrote:
> > so chrome at least has gotten pretty uppity about certs that lack subject
> > altnames.
>
> Oh that's going to be hilarious. There are at least valid reasons for
> doing this (e.g. nameConstraints don'
so chrome at least has gotten pretty uppity about certs that lack subject
altnames. following the instructions in ssl.8 is no longer sufficient.
here's a short hint about how to fix this.
Index: ssl.8
===
RCS file:
Bryan Steele wrote:
> OpenBSD's file(1) implementation was written by nicm@, first introduced
> in 5.8, the inital design included a privileged parent process which
> forked an unprivileged child which would handle potentially unsafe
> file parsing.
>
> It also had 'sandboxing' using systrace(4),
Scott Cheloha wrote:
> Hi,
>
> Using strcmp(3) to check a password is just asking for a timing
> attack.
>
> I admit that setting up such an attack on a custom lock(1) key at,
> say, a physical terminal would be cumbersome, so maybe this is just
> paranoia.
>
> However, passwords *do* get
Job Snijders wrote:
> On Sun, Jun 25, 2017 at 02:06:20PM +0200, Job Snijders wrote:
> > This patch adds a -v option to cp(1) for more verbose output.
>
> NetBSD/FreeBSD/DragonFly/OSX's cp(1) with "-v" print file names without
> the single quotes, which might indeed be more appealing to the eye:
Dmitry Chestnykh wrote:
> Hello,
>
> In ffs_inode_alloc(), inode generation numbers are incremented after
> being assigned an initial random value. Since the di_gen field is a
> signed integer, it may overflow, causing undefined behavior (this is
> unlikely to ever happen, though).
>
> This
Jonathan Gray wrote:
> On Sat, Jun 24, 2017 at 11:20:00AM +1000, Jonathan Gray wrote:
> > On Sat, Jun 24, 2017 at 03:00:19AM +0200, Mark Kettenis wrote:
> > > The code doesn't fully initialize the structure, which was extended to
> > > include a flags member at some point. Since the pending
Klemens Nanni wrote:
> I wanted to quickly debug some program without actually dumping to disk
> by using FIFOs, however ktrace(2) wouldn't accept anything but regular
> files.
>
> Are there any pitfalls or limitations I am currently not aware of that
> justify this strict behaviour?
oh, neat,
Frederic Cambus wrote:
> On Sat, Jun 17, 2017 at 05:27:38PM -0400, Ted Unangst wrote:
>
> > > Add a handler for the WSDISPLAYIO_GINFO ioctl in inteldrm, allowing
> > > to retrieve basic information about a framebuffer display.
>
> [...]
>
> > why?
Frederic Cambus wrote:
> Hi tech@,
>
> Add a handler for the WSDISPLAYIO_GINFO ioctl in inteldrm, allowing
> to retrieve basic information about a framebuffer display.
>
> When running wsconsctl on a machine with inteldrm support, this now
> returns those additional fields:
>
>
Charles Collicutt wrote:
> On 14 June 2017 at 19:22, Ted Unangst <t...@tedunangst.com> wrote:
>
> > Charles Collicutt wrote:
> > > That works, thank you. gcc-local(1) only mentions -nopie as an option for
> > > the linker, so I thought it ought to be passed
Charles Collicutt wrote:
> On 14 June 2017 at 17:34, Ted Unangst <t...@tedunangst.com> wrote:
>
> > gcc -static -nopie -o foo foo.c
> >
>
> That works, thank you. gcc-local(1) only mentions -nopie as an option for
> the linker, so I thought it ought to be pa
Mike Belopuhov wrote:
> On Wed, Jun 14, 2017 at 11:43 -0400, Ted Unangst wrote:
> > Mike Belopuhov wrote:
> > > still looking forward to replies to the original set of changes.
> >
> > i'm a little in between. on the one hand, yes, ok, it's good that we don't
>
201 - 300 of 1656 matches
Mail list logo
