Jason A. Donenfeld wrote:
> Wow, that's magic, and works perfectly:
> https://data.zx2c4.com/openbsd-qemu-sparc64-pretty-vga-with-serif-font.png
> Pretty font too.
>
> It sounds like the issue we're facing here is that the addr function
> is missing from QEMU's firmware? Would it be quasi
On Mon, Jun 01, 2020 at 06:28:40PM -0400, Daniel Jakots wrote:
> To be sure I don't accidentally overwrite the passphrase files, I'd
> like to make them read only. The current code expects them to be
> readable and writable. I took the new code from ssh (sshkey_perm_ok
> function).
Permissions
Hi,
To be sure I don't accidentally overwrite the passphrase files, I'd
like to make them read only. The current code expects them to be
readable and writable. I took the new code from ssh (sshkey_perm_ok
function).
While there, I changed the error message (also based on ssh) so the
user has a
On Mon, Jun 01, 2020 at 03:37:45PM -0600, Anthony J. Bentley wrote:
> Marc Espie writes:
> > > To setup the right alt key as compose, you can either:
> > >
> > > - run 'setxkbmap -option compose:ralt' somewhere in your session
> > > startup script
> > >
> > > - create
Installing an unstripped boot loader on softraid on sparc64 fails
without proper error message.
Make BIOCINSTALLBOOT return a proper errno, make installboot(8) use it
to provide proper usage errors plus unique code paths for debugging.
At first, I made sr_ioctl_installboot() use sr_error() in
Hi,
RFC 5681 Section 3.1 has an Implementation Note that covers the bug fixed by
the following patch. I ran into this bug testing on a high latency link. My
congestion window was pinned to a specific value and could not open further,
causing a lack of bandwidth utilization.
I chose
Marc Espie writes:
> > To setup the right alt key as compose, you can either:
> >
> > - run 'setxkbmap -option compose:ralt' somewhere in your session
> > startup script
> >
> > - create /etc/X11/xorg.conf.d/90-keyboard.conf containing
> >
> > --- Cut ---
> > Section "InputClass"
> >
On Mon, Jun 01, 2020 at 03:46:09PM +0200, Matthieu Herrb wrote:
> On Mon, Jun 01, 2020 at 03:28:52PM +0200, Stéphane Aulery wrote:
> > Hello,
> >
> > Le 01/06/2020 14:55, Matthieu Herrb a écrit :
> > >
> > > >
> > > > (I have just tried with a test user with nothing configured besides
> > > >
On Mon, Jun 1, 2020 at 2:37 PM Mark Cave-Ayland
wrote:
> Oh wow it looks great!
Totally. I was super impressed as well.
> I also have commit access to OpenBIOS so I can tidy that up
> and get it posted over on the OpenBIOS mailing list. Probably the main thing
> is to
> figure out what to do
On 01/06/2020 21:08, Jason A. Donenfeld wrote:
> On Mon, Jun 1, 2020 at 1:54 PM Mark Cave-Ayland
> wrote:
>>
>> On 01/06/2020 08:23, Jason A. Donenfeld wrote:
>>
>>> On Sun, May 31, 2020 at 3:18 AM Mark Cave-Ayland
>>> wrote:
AFAICT the problem here is the Forth being used at
On Mon, Jun 1, 2020 at 2:08 PM Jason A. Donenfeld wrote:
>
> Hi Mark,
>
> On Mon, Jun 1, 2020 at 1:54 PM Mark Cave-Ayland
> wrote:
> >
> > On 01/06/2020 08:23, Jason A. Donenfeld wrote:
> >
> > > On Sun, May 31, 2020 at 3:18 AM Mark Cave-Ayland
> > > wrote:
> > >>
> > >> AFAICT the problem here
Hi Mark,
On Mon, Jun 1, 2020 at 1:54 PM Mark Cave-Ayland
wrote:
>
> On 01/06/2020 08:23, Jason A. Donenfeld wrote:
>
> > On Sun, May 31, 2020 at 3:18 AM Mark Cave-Ayland
> > wrote:
> >>
> >> AFAICT the problem here is the Forth being used at
> >>
On 01/06/2020 08:23, Jason A. Donenfeld wrote:
> On Sun, May 31, 2020 at 3:18 AM Mark Cave-Ayland
> wrote:
>>
>> AFAICT the problem here is the Forth being used at
>> https://github.com/openbsd/src/blob/master/sys/arch/sparc64/dev/fb.c#L511:
>> since the
>> addr word isn't part of the IEEE-1275
On Mon, Jun 01, 2020 at 06:04:17PM +0100, Stuart Henderson wrote:
> OK to drop the expired AddTrust cert from cert.pem?
Thanks for taking care of this (and for checking the firefox set). I see
no reason to keep it.
ok
> I checked against the firefox set, there are no new/removed certs that
>
OK to drop the expired AddTrust cert from cert.pem?
I checked against the firefox set, there are no new/removed certs that
work with libressl there. There are now two with GENERALIZEDTIME notAfter
dates from before 2050 that don't work though (I only remember seeing one
of those when I last
On 2020/06/01 15:56, Stéphane Aulery wrote:
> Le 01/06/2020 15:46, Matthieu Herrb a écrit :
> > On Mon, Jun 01, 2020 at 03:28:52PM +0200, Stéphane Aulery wrote:
> > > Le 01/06/2020 14:55, Matthieu Herrb a écrit :
> > > >
> > > > >
> > > > > (I have just tried with a test user with nothing
Theo de Raadt:
> > Then you still need to check on every call whether the clockid has
> > changed (because the kern.timecounter.hardware sysctl was changed)
> > and refetch the function pointer in that case.
>
> Then really, we should remove that sysctl support.
>
> Because otherwise I don't
Christian Weisgerber wrote:
> On 2020-05-31, "Theo de Raadt" wrote:
>
> >> > particular timecounter type can be supported. My proposal would be to
> >> > implement a function *on all architecture* that takes the clockid as
> >> > an argument and returns a pointer to the function that
Marc Espie:
> If I type 'c
>
> I get a ç in programs like firefox or chrome, BUT I get
> ć in xterm ?
>
> why are things different ? which program is right ?
GTK comes with its own compose rules that are occasionally different
from the default X11 ones.
Personally, I disable GTK's compose
Le 01/06/2020 15:46, Matthieu Herrb a écrit :
On Mon, Jun 01, 2020 at 03:28:52PM +0200, Stéphane Aulery wrote:
Le 01/06/2020 14:55, Matthieu Herrb a écrit :
>
> >
> > (I have just tried with a test user with nothing configured besides
> > LC_CTYPE=en_US.UTF-8, without which xterm/vim doesn't
On Mon, Jun 01, 2020 at 03:28:52PM +0200, Stéphane Aulery wrote:
> Hello,
>
> Le 01/06/2020 14:55, Matthieu Herrb a écrit :
> >
> > >
> > > (I have just tried with a test user with nothing configured besides
> > > LC_CTYPE=en_US.UTF-8, without which xterm/vim doesn't show proper
> > >
Hello,
Le 01/06/2020 14:55, Matthieu Herrb a écrit :
(I have just tried with a test user with nothing configured besides
LC_CTYPE=en_US.UTF-8, without which xterm/vim doesn't show proper
characters)
I'm using a real US keyboard with AltGr or the Menu Key (depending on
the actual keyboard)
On Mon, Jun 01, 2020 at 02:16:16PM +0200, Marc Espie wrote:
> I occasionnally use setxkbmap 'us(intl)' in order to have diacritics
> as dead keys.
>
> I have LC_CTYPE=en_US.UTF-8
>
> If I type 'c
>
> I get a ç in programs like firefox or chrome, BUT I get
> ć in xterm ?
>
> why are things
I occasionnally use setxkbmap 'us(intl)' in order to have diacritics
as dead keys.
I have LC_CTYPE=en_US.UTF-8
If I type 'c
I get a ç in programs like firefox or chrome, BUT I get
ć in xterm ?
why are things different ? which program is right ?
(I have just tried with a test user with
On Sun, May 31, 2020 at 7:22 AM Otto Moerbeek wrote:
> Thanks, the following works indeed.
>
> -Otto
>
> Index: bootblk.fth
> ===
> RCS file: /cvs/src/sys/arch/sparc64/stand/bootblk/bootblk.fth,v
> retrieving revision 1.9
>
On Sun, May 31, 2020 at 3:18 AM Mark Cave-Ayland
wrote:
>
> AFAICT the problem here is the Forth being used at
> https://github.com/openbsd/src/blob/master/sys/arch/sparc64/dev/fb.c#L511:
> since the
> addr word isn't part of the IEEE-1275 specification, it is currently
> unimplemented in
>
Hi,
Just a quick bump, wondering if someone could take a look at the diff,
conscious there appears to have been a lot going on recently!
I want to do some more detailed work on the json output, but would
ideally get this first iteration in first.
Richard
On Sat, May 23, 2020 at 9:28 AM Richard
27 matches
Mail list logo
