Disklabel Spoofing and the GPT "Required" Partition Attribute

2023-09-24 Thread Philippe Meunier
Hi, So I was using OpenBSD on a USB thumb drive to have a look at the EFI system partition of two laptops (one Windows 10, one Windows 11) when I realized that I couldn't mount the EFI system partition of the Windows 11 laptop at all because there simply wasn't any partition letter defined for it.

Re: execve -1 errno 12 Cannot allocate memory

2021-02-02 Thread Philippe Meunier
Theo de Raadt wrote: >Otto Moerbeek wrote: >> Fixing a particluar issue is fine, but more important is an assessment >> it does not break other things. In particular, does this limit the VM >> for data available to any program (which is already quite limited on >> i386)? MAXTSIZ is used in one an

Re: execve -1 errno 12 Cannot allocate memory

2021-02-01 Thread Philippe Meunier
Anyone? Philippe Philippe Meunier wrote: >Jonathan Gray wrote: >>MAXTSIZ is 128 MB on i386 >>see sys/arch/i386/include/vmparam.h > >Mark Kettenis wrote: >>sys/arch/i386/include/vmparam.h has: >>#define MAXTSIZ (128*1024*1024) /* max text size */

Re: execve -1 errno 12 Cannot allocate memory

2021-01-31 Thread Philippe Meunier
Jonathan Gray wrote: >MAXTSIZ is 128 MB on i386 >see sys/arch/i386/include/vmparam.h Mark Kettenis wrote: >sys/arch/i386/include/vmparam.h has: >#define MAXTSIZ (128*1024*1024) /* max text size */ Thanks to both of you for the pointer! So what about the patch below? I've checked

Re: execve -1 errno 12 Cannot allocate memory

2021-01-29 Thread Philippe Meunier
Philippe Meunier wrote: >Is there some kind of limitation on the size of an ELF executable that can >be executed on i386? I mean, in addition to the limits in /etc/login.conf? When using readelf(1) on the chrome executable from chromium-81.0.4044.138.tgz from OpenBSD 6.7-release i386 packa

execve -1 errno 12 Cannot allocate memory

2021-01-29 Thread Philippe Meunier
Hello, Is there some kind of limitation on the size of an ELF executable that can be executed on i386? I mean, in addition to the limits in /etc/login.conf? Here's why I'm asking: $ uname -a OpenBSD t43.my.domain 6.8 GENERIC#4 i386 $ cat /etc/login.conf [...] default:\ :path=/usr/bin /

Re: inteldrm(4) regression from 6.1 to 6.2: wrong console resolution

2018-08-29 Thread Philippe Meunier
Mark Kettenis wrote: >I have to think through the consequences of simply doing a delay >without checking the condition here though. Ping? Philippe

Re: inteldrm(4) regression from 6.1 to 6.2: wrong console resolution

2018-08-19 Thread Philippe Meunier
Mark Kettenis wrote: >I have to think through the consequences of simply doing a delay >without checking the condition here though. Right now __wait_event_intr_timeout has a KASSERT(!cold), so, if its code is changed to have an "if (cold) { delay(tick); ret = 1; }" then we know that this new code

Re: inteldrm(4) regression from 6.1 to 6.2: wrong console resolution

2018-08-17 Thread Philippe Meunier
Mark Kettenis wrote: >Maybe you can add some printf's to figure out why the timeout is >happening? Is it actually doing a delay? Is the delay too long? Or >too short? Yes, the delay is okay. The problem is that when "cold" is 1, the vblank counter never changes during a call to drm_wait_one_vb

Re: inteldrm(4) regression from 6.1 to 6.2: wrong console resolution

2018-08-14 Thread Philippe Meunier
Philippe Meunier wrote: >Mark Kettenis wrote: >>Does the diff below fix things? > >Yes, it fixes the console resolution problem, although a bunch of "vblank >wait timed out on crtc 0" messages now show up (see dmesg's output below). How about the patch below? I

Re: inteldrm(4) regression from 6.1 to 6.2: wrong console resolution

2018-08-14 Thread Philippe Meunier
Mark Kettenis wrote: >Does the diff below fix things? Yes, it fixes the console resolution problem, although a bunch of "vblank wait timed out on crtc 0" messages now show up (see dmesg's output below). Philippe OpenBSD 6.4-beta (GENERIC) #5: Tue Aug 14 22:20:08 CST 2018 r...@usb.my.domain

Re: dc(1); fix 0Z

2017-12-05 Thread Philippe Meunier
kshe wrote: >If the number `002' is said to have only one digit because the zeros in [...] >the integer logarithm, thus being nothing but arbitrary, and as such of >little practical value. Yes, yes, but "number of digits" and "integer logarithm" are two different things. You sound suspiciously li

Re: dc(1); fix 0Z

2017-12-03 Thread Philippe Meunier
kshe wrote: >Also, the manual defines the length of a number as its number of digits, >so perhaps it should be precised that zero is considered to have no >digits, which might not be obvious to everyone. Am I the only who thinks this is not just not obvious, but actually wrong? On a related note,

Re: Remove accents from fortunes

2017-07-11 Thread Philippe Meunier
Anthony J. Bentley wrote: >And since nobody's complained in the past few years that they couldn't >see the accents in Jabberwocky... But then some Frenchman might suddenly complain about René Descartes's name being misspelt (not that I had ever noticed that the accent didn't show up before reading

Re: [patch 1/2] doas(1): Moved some parsing from env.c into parse.y

2017-03-16 Thread Philippe Meunier
Ted Unangst wrote: >Did I get it backwards? If you have setenv { HERE= there }, your diff >changes behavior. Speaking from the peanut gallery here, but I find this syntax rather confusing and error-prone, especially for a security-related file such as doas.conf. How about making the list of varia

Re: [patch] which(1): out of bounds read

2016-01-13 Thread Philippe Meunier
Max Fillinger wrote: >If PATH starts with "/:", which(1) reads outside of allocated memory. >Maybe that caused the non-reproduceable coredump mentioned in [0]? I think you're right as I did have / at the beginning of my PATH when which(1) coredumped on me. I was planning to look at it today but y

ntpd.conf and Google

2016-01-12 Thread Philippe Meunier
Hello, $ fgrep constraint /etc/ntpd.conf constraints from "https://www.google.com"; $ www.google.com and other Google services are not accessible from countries like China or Vietnam. It's easy enough for people to change their ntpd.conf if necessary but how about using a default value that is m

Re: dhclient ignore

2012-07-26 Thread Philippe Meunier
Ted Unangst wrote: >[...] I just want to say "pretend this option did not arrive." > >Diff below adds a little support for an ignore keyword. Like >supersede, except don't actually use the supplied value. Put another way, dhclient has a "default permit" policy (it will use any nameserver informat

dhclient, DHCP options, and some opinions

2011-08-10 Thread Philippe Meunier
Hello, FYI: 1) The OPTION MODIFIERS section of dhclient.conf(5) indicates that the default client configuration script processes only options 1 (subnet mask), 3 (routers), 6 (domain name servers), and 15 (domain-name). In fact /sbin/dhclient-script also uses option 28 (broadcast address). 2) dh

RLIMIT_AS missing

2010-08-15 Thread Philippe Meunier
Hello, I just tried to compile some software on OpenBSD and it failed because OpenBSD does not provide RLIMIT_AS: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/sys/resource.h?rev=1.8;content-type=text%2Fplain even though RLIMIT_AS seems to be part of POSIX: http://www.opengroup.org/onlinepubs/0096