list of standards that OpenGroup publishes/maintains.
The OpenGroup is _completely_ unrelated to OpenBSD. If you want
information about their stuff you need to ask them.
Philip Guenther
On Fri, Sep 27, 2024 at 1:45 AM Christian Schulte wrote:
> On 9/26/24 10:47, Philip Guenther wrote:
> > On Thu, Sep 26, 2024 at 12:30 AM Christian Schulte wrote:
...
> > Does there exist a documented, maintained, and tested way to "build
> > base incrementally&
o avoid.
tl;dr: no really, snaps are full builds; if you take short cuts and it
breaks you get to keep both pieces but you'll just get told to follow
the normal process to get back and not waste people's time.
Philip Guenther
lve its meaning for the term
PFS, but calling anything that has actually been built and
standardized 'perfect' is just spitting in the face of the forward
progress of science.
tl;dr, sure, it'll be secure.
Philip Guenther
Whee. Can someone send me or point me to a reproducer for this; e.g.,
does postgresql's own test suite hit this?
Philip
On Thu, Aug 22, 2024 at 10:35 AM Jeremy Evans wrote:
>
> On 08/22 03:43, Stuart Henderson wrote:
> > On 2024/08/22 14:14, Jeremy Evans wrote:
> > > On 08/22 11:53, Markus Hen
the wrong value) on the one
box? That's the only remaining factor I can think of...
Philip Guenther
write a configure test for “doesn’t have working .rodata
so use .text instead” but it was the previous millenium when I last saw a
working system like that…
Philip Guenther
On Saturday, July 27, 2024, Shein Asker wrote:
> Dear Mr. Claudio, @misc readers,
>
> Thank you for your pro
On Thursday, July 18, 2024, Katherine Mcmillan wrote:
>
> In the Core Program for the POSIX standards, a relational database is
> listed. I am wondering what this is referring to?
>
You’ll need to be more specific about what you’re referring to and how it
relates to OpenBSD.
Philip Guenther
ion about
your laptop and the cpus inside it.
Philip Guenther
st you developed yourself based on testing
other systems or something you read about?
Philip Guenther
On Thu, May 16, 2024 at 12:08 AM Philip Guenther wrote:
> On Wed, May 15, 2024 at 1:14 AM Philip Guenther wrote:
...
>> I think you've managed to hit a spot where the POSIX standard doesn't
>> provide a way for a program to find the information it needs to do its job
On Thu, May 16, 2024 at 5:33 AM Walter Alejandro Iglesias
wrote:
>
> On Thu May 16 09:48:45 2024 Philip Guenther wrote:
> > So yeah, what's needed is pathconfat(2)** but whether this winding loose
> > end ("That poor yak.") merits that much code and surface
On Wed, May 15, 2024 at 1:14 AM Philip Guenther wrote:
> On Tue, May 14, 2024 at 11:59 AM Walter Alejandro Iglesias <
> w...@roquesor.com> wrote:
>
>> Hi Philip,
>>
>> On Tue May 14 19:40:04 2024 Philip Guenther wrote:
>> > If you like, you could try the
On Tue, May 14, 2024 at 11:59 AM Walter Alejandro Iglesias
wrote:
> Hi Philip,
>
> On Tue May 14 19:40:04 2024 Philip Guenther wrote:
> > If you like, you could try the following patch to pax to more gracefully
> > handle filesystems with time resolution more granular than n
r at least so that the OpenBSD
guest(s) isn't the one being asked to slim itself (possibly by giving it
*less* but _reserved_ memory, so that the VM host never tries to shrink
its usage).
Philip Guenther
On Tue, May 14, 2024 at 4:16 PM F Bax wrote:
> I'm not a coder; but I found
If you like, you could try the following patch to pax to more gracefully
handle filesystems with time resolution more granular than nanoseconds.
The whitespace will presumably be mauled by gmail so use patch's -l option.
Philip Guenther
Index: ar_s
-Z options
> don't work with ext2fs?
>
It should work the same as on ffs, but since you put zero effort into
describing _how_ its behavior didn't match your expectations, I wouldn't
expect anyone to put more than zero effort in reading your mind.
Good luck!
Philip Guenther
RAID replicates the data in the RAIDed area, yes?
Do you have some reason to believe that the boot information (MBR, etc) is
_inside_ the RAID area, because I do not believe that. Really feels like
installboot needs to be run on this drive to, uh, install the proper boot
info.
Philip Guenther
ho try to help, particularly when doing
exactly what you requested would NOT HAVE HELPED, unless you *want* people
to drop you in their kill-file as "not worth trying to help".)
Philip Guenther
Ah, sorry for my misreading what you wrote.
Please use 'sendbug' to report the sequence of pkg_add operations that
didn't work.
Philip Guenther
On Sun, Oct 22, 2023 at 5:50 PM Mark wrote:
> It wasn't an upgraded system, that's fresh install, a completely new
>
icture but capture
/var/log/Xorg.0.log both before suspending and then after resuming (ssh in
if necessary) and see what X is falling over on.
Philip Guenther
On Wed, Oct 18, 2023 at 4:17 AM Jan Stary wrote:
> On Oct 18 11:11:54, h...@stare.cz wrote:
> > This is current/amd64 o
/var/db/pkg/ or
/usr/local/*
4) pkg_add -l manual
Or maybe now's a good time to do a fresh install.
Philip Guenther
On Sun, Oct 22, 2023 at 3:34 PM Mark wrote:
> Tried changing the installurl, an another mirror, but didn't help.
>
> Here's what actually happens;
>
If this had been observed _during_ 7.4 development then it would have been
simpler to isolate what set of changes caused it. Since that didn't happen
you'll have to debug this yourself on the affected systems. For starters,
I would suggest turning up ssh logging with the -v option and capturing
t
On Sat, Oct 21, 2023 at 2:27 AM wrote:
> Hi Philip,
>
> Thank you very much for your answer.
>
> I tried to disable all options (+devices) possible. Same issue.
> And what's about disable acpi in the kernel using the bsd.re-config?
>
As Mike and Theo noted, this will certainly cause problems.
The last possibility would be to build a kernel which allocates more pages
per thread for its kernel stack by bumping the UPAGES #define
in /usr/src/sys/arch/amd64/include/param.h and building a new kernel. It's
really only the ACPI thread that needs this, but we don't currently have
code to control that on a per-thread basis.
Philip Guenther
/ /bsd
?
If it *is* marked immutable, then uh, you'll need to undo that and figure
how the heck that happened and make sure it doesn't happen again.
(If _you_ marked it immutable, then don't, or at least don't waste people's
time when that breaks things.)
Philip Guenther
On Tue, Oct 10, 2023 at 11:44 PM Lorenz (xha) wrote:
> On Mon, Oct 09, 2023 at 01:29:52PM -0700, Philip Guenther wrote:
> > On Mon, Oct 9, 2023 at 11:21 AM Lorenz (xha) wrote:
> >
> > > hi misc@,
> > >
> > > i'm currently porting the hare progra
he logic around the 10
occurrences of EINVAL in that code. Presumably the differences you
identified will point to one or more of them
Philip Guenther
7;t include that, you would appear to be running some
>> other version of dump, which would make this the wrong place to get help.
>>
>> ...unless you truncated an error message before asking about it, which is
>> kinda self-defeating.
>>
>>
>> Philip Guenther
>>
>>
x27;t let untrusted people alter libc on your system"
You *do* understand that you are trusting the OpenBSD developers by using
OpenBSD, just as you are trusting the FreeBSD developers if you use
FreeBSD, and trusting the Linux kernel and glibc and GNU-whatever utils,
and systemd, and distro de
On Mon, Sep 11, 2023 at 12:01 PM Benjamin Stürz
wrote:
> I'm writing a little toy /proc fuse-fs for OpenBSD.
>
> The field p_schedflags defined in struct kinfo_proc
> in file /usr/include/sys/sysctl.h refers to PSCHED_*,
> but I can't find any references to these macros with:
> $ grep -rn PSCHED_
to read the SHA256 file.
Perhaps you should follow all the examples for signify and pass it the
SHA256.sig file.
Philip Guenther
ven if
the filesystem provided enough info for dump to know that only the file's
mode had been changed, there's nothing it can do about it other than back
up the entire file.)
Philip Guenther
ems a plausible explanation of
the expansion.
Philip Guenther
0, inum = 7, fs = /tmp
> panic: ffs_valloc: dup alloc
> Stopped at db_enter+0x10: popq %rbp
>
You have at least one filesystem with latent corruption. You should reboot
in single-user mode and run fsck with the -f option on each partition.
Philip Guenther
rdist
is smart enough to know that it can't remove a directory without first
removing its contents, so it tried that and presumably failed. If it
_could_ remove the contents it would then remove the directory...and then
fail when it tried to create a tempfile with prefix "/tmp/".
Co
Take a look at the Makefile for the sysutils/cpuid port, which has just one
C file included in the ports source tree itself.
Philip Guenther
On Wed, Jun 29, 2022 at 3:53 PM Lyndon Nerenberg (VE7TFX/VE6BBM) <
lyn...@orthanc.ca> wrote:
> We have a number of in-house utilities that we pu
.
(There is no rpcbind program in OpenBSD and that word doesn't appear in the
manuals. If you see an rpcbind process then you're not on OpenBSD and
need to check with a different mailing list.)
Philip Guenther
depending on, say, whether the box is plugged in.
You could give this diff a shot. It enables processing of CST change
notifications. No committers have a (working) box that does that, so I
couldn't get any interest and I have no idea when--or even if--it might go
in.
Philip Guenthe
ess tree, which breaks assumptions by both
kernel and userspace programs. If that's the case, run gdb from an ssh
session or something like that.
Hmm, I guess I never updated the ptrace(2) manpage to mention that...
Philip Guenther
pluging.
>
That aml_register_notify() path is a *boot* time path, when acpicpu is
attaching. What printf() did you add and did it appear during boot? If
not, then the OS isn't registering the notify callback.
Please send a report to bugs@ with sendbug as root, including the acpidump
output.
Philip Guenther
would suggest adding a printf() right before the aml_register_notify()
call in acpicpu.c to see if it's actually being hit, and if it is then dump
the tables on your box and grovel around in them to see if you see
notification support on the CPU nodes.
Philip Guenther
he
FAQ about upgrades so that you can keep your system up to date after
installing.
Philip Guenther
The machine hosting your guest probably suffered some failure (thus the
crash that you experienced) and they migrated your guest to another host to
get you back up and running. I periodically see the tickets go by at my
$DAYJOB of this sort of replacement. Hardware, especially modern PCs,
don't live anywhere near forever...
Philip Guenther
On Tue, Aug 10, 2021 at 12:13 PM mid wrote:
> On Monday, August 9th, 2021 at 5:36 AM, Philip Guenther <
> guent...@gmail.com> wrote:
>
> > If you're 100% sure you have it right, then it should be easy to provide
> a
> > program that demonstrates
> >
On Sun, Aug 8, 2021 at 10:13 AM mid wrote:
...
> I have tried sending the file descriptors associated with the connection
> to process B via sendmsg, thinking that maybe the
> file descriptors are reference-counted. It's a logical
> assumption, but it didn't work - the connection closed with
> pr
/usr/src/usr.bin/login/failedlogin.c and
consists of an array of the 'badlogin' structure specified there. If you
want to dump its contents in a more readable format then you should write a
small program to do so in C or some other language which can easily handle
binary files.
Philip Guenther
ever, if
you have a target and are trying to figure out whether a setup can _reach_
that target then measuring an older release tells you nothing, because you
would never deploy an out of date release. I Would Dearly Hope.
Philip Guenther
etsockopt()
calls?
You say "I can confirm the packet was not sent to a broadcast address":
*how* have you confirmed that your understanding of 'broadcast address'
matches the kernel's understanding? It ain't just 255.255.255.255
Philip Guenther
>
>
> Siegfried
d
actively hostile to portability of tooling.
If you find that ELF note obnoxious, just fix the linkers to instead set
the ELF ABI field correctly. As I understand it, the 'go' tool chain has
done that for years. It's really the better choice for this, would take
less space a
your game_mode_start_audio_thread(), where you advance
the pointer from uvm_map() by four.
Philip Guenther
;
> if(uvm_map(&p->p_vmspace->vm_map, &memory_in_proc_space,
> round_page(memory_size), uvm_object,
>0, 0, UVM_MAPFLAG(PROT_READ | PROT_WRITE, PROT_READ | PROT_WRITE,
>MAP_INHERIT_NONE, MADV_NORMAL, 0))) {
> memory = 0;
>
This error handling is incomplete, lacking an unmap.
Philip Guenther
port, which is enabled by
default. If you're a masochist and likes making your life more difficult,
you can use that port for your own purposes by disabling that sysctl. If
you're not a masochist, use a different port.
Philip Guenther
On Tue, Dec 8, 2020 at 4:13 PM Chris Johnson
closing quote is actually proper
> behavior.
>
Nope. This is a bug in OpenBSD ksh.
> As well it is good idea to avoid reserved words as a names for variables
> ;-)
> (test)
Hmm?
* 'test' is not a reserved word in the shell
* shell variable names are a completely different namespace than shell
reserved words or commands
* code written to check whether something is a bug is 1000% out-of-bounds
for style comments: either there's a bug or there isn't
Philip Guenther
the
qemu people and figure out why your host kernel isn't applying a documented
fix.
Paying attention to what the kernel tells you is a Good Thing. Honestly,
what you showed above, that it trapped on wrmsr with those registers should
have been enough for the qemu people to figure out what wasn't working.
Philip Guenther
ze, solving both the field size limit problem and the lack
of subsecond resolution.
Philip Guenther
direct CPU instructions for I/O. To use them, the code must use
i386_iopl(2) from libarch.a to enable it, which in turn requires the
machdep.allowaperture sysctl to a non-zero value (per the manpage).
> Any advice about this? Is this code amenable to being 'modernized'?
>
> If can't modernize the lcdproc code, can you give me specifics about:
> Do I just put a line in /etc/rc.securelevel
> kern.allowkmem=1
>
Try machdep.allowaperture=1 instead.
Philip Guenther
still supported ?
>
Yes.
Philip Guenther
the so-called poetry extension, where a bare word like aF is
treated as a string. Turn on strict...
$ perl -Mstrict -le 'print hex Af;'
Bareword "Af" not allowed while "strict subs" in use at -e line 1.
Execution of -e aborted due to compilation errors.
$
> I'm guessing there is a bug here but not sure if its software or
> documentation.
>
No bug, just shell quoting traps.
Philip Guenther
ore places
that need to change for the reported problem to be handled safely.
Philip Guenther
On Tue, Jun 23, 2020 at 9:58 PM Martijn van Duren <
open...@list.imperialat.at> wrote:
> This seems to fix the issue for me.
>
> OK?
>
> martijn@
>
> On Tue, 2020-06-23 a
Cell *bltin(Node **a, int n)/* builtin
u = strlen(getsval(x));
break;
case FLOG:
+ errno = 0;
u = errcheck(log(getfval(x)), "log"); break;
case FINT:
modf(getfval(x), &u); break;
case FEXP:
+ errno = 0;
u = errcheck(exp(getfval(x)), "exp"); break;
case FSQRT:
+ errno = 0;
u = errcheck(sqrt(getfval(x)), "sqrt"); break;
case FSIN:
u = sin(getfval(x)); break;
Todd, are we up to date with upstream, or is this latent there too?
Philip Guenther
re the proper question...and the answer appears to be *no*.
Philip Guenther
them you
should stay away from OpenBSD because I am a committer and if you can't
trust my questions then you shouldn't trust my code.
Philip Guenther
in part by
someone who is/was a US citizen, in OpenSSH even, as a check of
copyright/license statements on source files show. How does that change
your world view?
Philip Guenther
ld require you providing the full
stack trace to the list, so that the correct parties can see it and
identify where it's incorrectly looping.
Philip Guenther
Because it would be a total PITA now and in the future and benefit only
that small set of machines that have >4GB of memory but that can't run
64bit.
Since you like one-liner questions: why do you care?
anges have been included in OpenBSD. Check his biography and his
personal website for links to papers and presentations.
Philip Guenther
eed to work with the the
docs, mailling lists, etc of the upstream gnu fortran project about how to
have it generate code for the medium or large data models per the amd64 ABI.
Philip Guenther
ng further to
contribute to this thread)
Philip Guenther
On Mon, Dec 23, 2019 at 3:10 PM Stuart Longland
wrote:
...
> Where do you get `sysclean` from? I don't seem to have it:
> > sjl-router# man sysclean
>
> > man: No entry for sysclean in the manual.
> > sjl-router# which sysclean
> > which: sysclean: Command not found.
>
$ pkg_info sysclean
Infor
On Mon, Dec 23, 2019 at 6:07 AM Ingo Schwarze wrote:
> Theo de Raadt wrote on Sun, Dec 22, 2019 at 05:34:45PM -0700:
> > Philip Guenther wrote:
> >> Somebody wrote:
>
> >>> The man pages for readv and writev don't document the possibility of
> >&
ith this.
...
> acpipci0 at acpi0 PCI0panic: malloc: allocation too large, type = 33, size
> = 292057776136
>
Philip Guenther
At this point I think you're clearly in the "device driver is buggy"
situation. If this device has an in-tree driver (and not something you're
compiling locally into your kernel) then you should start a new thread
starting with a dmesg and a clear description of the involved hardware.
Philip Guenther
7;t document the possibility of
> such errors.
IMO, weird errnos from devices should be documented in the manpage for the
device. Consider the termios(4) manpage, for example.
Philip Guenther
t", then my recommendation would be to grab
the 6.6 bsd.rd, boot to it, and (u)pgrade to 6.6 being sure to include the
comp66 set in your install, and _then_ try building things...or just run
syspatch.
Philip Guenther
On Sun, Nov 24, 2019 at 7:53 PM Jeffrey Walton wrote:
> On Sun, Nov 24, 2019 at 10:10 PM Philip Guenther
> wrote:
> >
> > On Sun, Nov 24, 2019 at 3:11 AM Jeffrey Walton
> wrote:
> >>
> >> I am struggling to get a USB modem and terminal configured proper
to be done to
initialize a tty on first open. We can (and I guess we should at this
point) define O_TTY_INIT to be zero.
How do I achieve O_TTY_INIT when
> using a struct termios tty?
>
Before calling tcsetattr(3) you should call tcgetattr(3) to get the tty
device's current settings and only alter the setting you care about.
Philip Guenther
On Friday, November 8, 2019, Theo de Raadt wrote:
> Philip Guenther wrote:
>
> > No, it should be the other way, moving the “clear NT flag” block down
> after
> > the “save registers into save area” block
>
> Ah.
>
> Ind
On Friday, November 8, 2019, Theo de Raadt wrote:
> Philip Guenther wrote:
>
> > Since we're unlikely to do _more_ with BIOS calls in the boot loader, my
> > inclination would be to eliminate the structure value and the code that
> > sets it (incorrectly). Opin
o use the ramdisks for (installing,
reinstalling, upgrading, fixing boot and set issues), vi is not necessary,
while other functionality and drivers extend their applicability. We will
keep the latter and not include the former.
Philip Guenther
so the fact that the wrong
value is saved there hasn't mattered.
Since we're unlikely to do _more_ with BIOS calls in the boot loader, my
inclination would be to eliminate the structure value and the code that
sets it (incorrectly). Opinions?
Philip Guenther
than in ASM. I've touched ASM on every single current OpenBSD arch, so
I understand the high cost of doing that when it _has_ been necessary and
I have no interest in borking around in ASM for stuff C can reasonably do.
Philip Guenther
_SOURCE -- standardized: specifies a POSIX version
_XOPEN_SOURCE-- standardized: specifies a POSIX + XSI version
_ISOC11_SOURCE-- adds C2011 interfaces
_BSD_SOURCE -- adds all BSD and obsoleted interfaces
Make sense?
Philip Guenther
om an over-zealous optimization in the
logic handling subshells where the possibility that an inner redirection
could be blocking wasn't taken into account when it tries to avoid
unnecessary forks.
Sorry, I don't have a fix in my back pocket. Your workaround is good; I'll
note the intermediate set of parens can also be braces, which would let you
avoid the otherwise necessary whitespace between open-parens if that grates
on your soul like it does mine. :)
Philip Guenther
ther processes
accessing the disk"? The word 'interrupt' is overloaded in computing and
what you saw may be a real problem with device support, or it may be
completely innocuous, something which you should be ignoring.
Philip Guenther
behavior. The use of the SGID bit on
directories to request BSD behavior was an addition in SystemV-based
systems when enough of their devs and users yelled at them to Not Be Stupid
And Provide the Better Behavior. I'm not sure who or when first added the
mount option. Linux certainly has both of those, but is not the only one.
Philip Guenther
CK when allocating memory for
thread stacks.
Philip Guenther
>
> The easy fix is to change the format to '%llu', but this brakes FreeBSD
> and Linux. Am i missing something or should i be investigating the log
> implementation?
>
Option 1)
log(DEBUG, "Solo5: clock_init(): freq=%llu\n", (unsigned long
long)freq);
Option 2)
#include
log(DEBUG, "Solo5: clock_init(): freq=%"PRIu64"\n", freq);
Software native to OpenBSD uses option 1 when necessary.
Philip Guenther
kets, but for SysV stuff it affects what
operations processes can perform.
Philip Guenther
o
this wasn't source files updated in the middle of the builds.
Without know the exact sequence of operations on this tree it would be hard
to diagnose how this happened.
"When in doubt, rm -rf /usr/obj/* before building"
Philip Guenther
ross
CPUs, real or virtual.
Philip Guenther
ports?
>
Those are just UDP sockets on which connect() hasn't been called and that
aren't in the middle of a recvfrom() or recvmsg(), no?
And, perhaps more directly, how would I block this in pf.conf?
>
Excellent choice, blocking dhclient from receiving the leases that it
reque
tems that were
_clearly_ going to happen is completely believable.
Philip Guenther
www.openbsd.org/64.html
* Implemented MAP_STACK option for mmap(2). At pagefaults and
syscalls the kernel will check that the stack pointer points
to MAP_STACK memory, which mitigates against attacks using
stack pivots.
To confirm, if you check your dmesg(8) or /var/log/messages you should
find the kernel complaining something like
syscall [server]65554/### sp 13cd24a## not inside 0x7f7f###-0x7f7f###
Philip Guenther
On Sun, Dec 2, 2018 at 7:51 PM Edgar Pettijohn
wrote:
> Sorry just saw it came with some examples. Testing with the `lookupdns'
> program
> ended with a Bus error (core dumped). Here is gdb output:
>
> Core was generated by `lookupdns'.
> Program terminated with signal SIGBUS, Bus error.
> #0 _l
> but I have no idea what on earth could be causing it.
>
It requested a sleep of 1 second and 15 seconds passed. That's a kernel
timetracking issue, so the output of "sysctl kern.timecounter" would be a
good place to start. Is this is an MP kernel using the CPU TSC, but on a
VM where the virtual CPU's TSCs aren't in sync?
Philip Guenther
e syscalls leading up to signal were (and what extra info was
in the signal) tells a lot.
Philip Guenther
hread function was disabled in this release?
> Is it security reason?
>
Upstream has it off by default, nothing so far has needed it, and it makes
things slower (or at least that's why upstream says). Why would we enable
it?
Philip Guenther
kill 16632
[3] - Terminated sh -c "while :; do :; done"
: morgaine;
: morgaine; sh -c 'while :; do sleep 1; done' &
[3] 59539
: morgaine; kill 59539
: morgaine;
[3] - Terminated sh -c "while :; do sleep 1; done"
: morgaine;
sh itself doesn't ignore SIGTERM, but rather exits after receiving it.
Philip Guenther
t mention the non-interactive case.
>
In my quick test it doesn't ignore SIGTERM, so you'll need to provide
additional information for us to help you.
Philip Guenther
1 - 100 of 989 matches
Mail list logo
