I like that.
Sebastien Marie wrote:
> Hi,
>
> arm64 ramdisk has customization in mr.fs target, in order to create
> usr/mdec/pine64 and usr/mdec/rpi directories (files will be copied
> inside them by runlist.sh).
>
> I will argue that mr.fs target isn't the place for such per-arch
>
Hi,
arm64 ramdisk has customization in mr.fs target, in order to create
usr/mdec/pine64 and usr/mdec/rpi directories (files will be copied
inside them by runlist.sh).
I will argue that mr.fs target isn't the place for such per-arch
customization as runlist.sh supports MKDIR directive from the
It's fairly easy to accidentally configure relayd to try to run check scripts
faster than they finish, for example if you have a check interval of one
second and the check script makes a tcp connection to a host that doesn't
exist any more.
In this situation, the hce process will keep writing
i was bored at home a few weeks back, so i had a go at scratching
an itch i've had for a while now which was to write a quick and
dirty ethernet switch. the itch got worse recently when stsp@ asked
about some weird packet behaviour that may or may not have been
caused by bridge(4). trying to
Am Mon, Feb 15, 2021 at 09:55:56AM +1000 schrieb David Gwynne:
>
>
> > On 15 Feb 2021, at 07:54, Mark Kettenis wrote:
> >
> > One of the aspects of device access is whether CPU writes to a device
> > are posted or non-posted. For non-posted writes, the CPU will wait
> > for the device to
> On 15 Feb 2021, at 07:54, Mark Kettenis wrote:
>
> One of the aspects of device access is whether CPU writes to a device
> are posted or non-posted. For non-posted writes, the CPU will wait
> for the device to acknowledge that the write has performed. If the
> device sits on a bus far
One of the aspects of device access is whether CPU writes to a device
are posted or non-posted. For non-posted writes, the CPU will wait
for the device to acknowledge that the write has performed. If the
device sits on a bus far away, this can take a while and slow things
down. The alternative
On Sun, Feb 14, 2021 at 04:43:17PM +, Stuart Henderson wrote:
> On 2021/02/14 15:22, Marcus Glocker wrote:
> > Unfortunately I'm seeing more and more USB device breakages reported
> > the last few days related to the USB data toggle fix which we did
> > commit 2-3 weeks ago.
>
> Do you think
Christian Weisgerber:
> > Make use of getline(3) in ftp(1).
> >
> > Replace fparseln(3) with getline(3). This removes the only use
> > of libutil.a(fparseln.o) from the ramdisk.
> > Replace a complicated fgetln(3) idiom with the much simpler getline(3).
>
> OK?
ping?
I've been fetching
Hi,
I stumbled upon some compiler warnings in bin/.
This diff removes two unused variables in bin/ps/print.c.
I hope that such tiny contributions are welcome.
For me, it's a test of whether I am contributing the right way.
diff --git bin/ps/print.c bin/ps/print.c
index 71d4a72a842..c10d8aa0523
On Thu, Dec 10, 2020 at 10:03:16PM -0800, Bryan Vyhmeister wrote:
> On Mon, Nov 30, 2020 at 07:58:39AM -0800, Bryan Vyhmeister wrote:
> > On Mon, Oct 19, 2020 at 08:11:04PM -0700, Bryan Vyhmeister wrote:
> > > On Fri, Oct 02, 2020 at 12:33:15PM -0700, Bryan Vyhmeister wrote:
> > > > On Wed, Sep
Make the AIA more easily available for debugging purposes & future
changesets
In the context of the RPKI, the AIA extension identifies the publication
point of the certificate of the issuer of the certificate in which the
extension appears. A single reference to the publication point of the
On Sun, Feb 14, 2021 at 09:46:32AM -0700, Theo de Raadt wrote:
> Sure.
>
> I guess the next thing to do would be using gzopen type functions,
> to edit a gzip'd version of the file.
I am unsure it would be doable in sane manner. rdsetroot is using
libelf to do elf manipulation, and the
Sure.
I guess the next thing to do would be using gzopen type functions,
to edit a gzip'd version of the file.
Then the recent move to .gz files would be more transparent for this
specific use case (which I think is very rare, honestly). I'm not sure
if it matters.
> The following diff makes
Sebastien Marie wrote:
> Please note I am unsure about sgi: disklabel -w is using
> "OpenBSD/sgi " as packid, and I changed it to "OpenBSD/${MACHINE}".
> But the packid used isn't uniform across archs, so it might not matter.
I think you mean "volid", this is the -V option. The thing to
On 2021/02/14 15:22, Marcus Glocker wrote:
> Unfortunately I'm seeing more and more USB device breakages reported
> the last few days related to the USB data toggle fix which we did
> commit 2-3 weeks ago.
Do you think this could this be implicated in a keyboard with 'stuck'
keys i.e. keep
On Sun, Feb 14, 2021 at 03:22:28PM +0100, Marcus Glocker wrote:
> Unfortunately I'm seeing more and more USB device breakages reported
> the last few days related to the USB data toggle fix which we did
> commit 2-3 weeks ago.
>
> Since I can't reproduce the issue here with my USB gear, it's very
On Sun, Feb 14, 2021 at 09:54:15AM -0500, Daniel Jakots wrote:
> On Sun, 14 Feb 2021 15:23:05 +0100, Sebastien Marie
> wrote:
>
> In the alpha diff, I would put the "-R .eh_frame -R .shstrtab \" line
> before the -K line so the -R things are grouped together.
I put it after in order to make
On Sun, 14 Feb 2021 15:23:05 +0100, Sebastien Marie
wrote:
> Hi,
>
> The following diff makes rdsetroot -x (extract the disk.fs image) to
> work again for stripped bsd.rd.
>
> It passes options to keep rd_root_size and rd_root_image symbols while
> stripping. These symbols are the ones used by
On Fri, Feb 12, 2021 at 03:48:51AM -0800, Anindya Mukherjee wrote:
> Hi,
>
> Sorry for the delay. I am running the latest snapshot:
> kern.version=OpenBSD 6.9-beta (GENERIC.MP) #331: Thu Feb 11 20:28:45 MST 2021
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> which
Hi,
The following diff makes rdsetroot -x (extract the disk.fs image) to
work again for stripped bsd.rd.
It passes options to keep rd_root_size and rd_root_image symbols while
stripping. These symbols are the ones used by rdsetroot to insert or
extract disk image into RAMDISK.
If it matter, on
Unfortunately I'm seeing more and more USB device breakages reported
the last few days related to the USB data toggle fix which we did
commit 2-3 weeks ago.
Since I can't reproduce the issue here with my USB gear, it's very
difficult for me to pin point the issue. Therefore I think we should
Hi,
The following diff makes various distrib Makefile to use ${MACHINE}
instead of hardcoded value.
Currently, some archs are using ${MACHINE} and others are using
hardcoded value.
Please note I am unsure about sgi: disklabel -w is using
"OpenBSD/sgi " as packid, and I changed it to
On Sun, Feb 07, 2021 at 06:55:37PM +0100, Sebastian Benoit wrote:
> David Gwynne(da...@gwynne.id.au) on 2021.01.27 17:13:09 +1000:
> > some of the discussion around dup-to made me think that a diff we
> > have here at work might be more broadly useful.
> >
> > we run a box here with a bunch of
On Wed, Jan 27, 2021 at 10:51:38AM +0100, Klemens Nanni wrote:
> On Wed, Jan 27, 2021 at 01:41:52AM +0100, Ingo Schwarze wrote:
> > It's maybe just a bikeshed, but could you put the logic selecting
> > the filename extension (either "" or ".html") at the place where
> > term_tag_init() is called?
Another month has passed, another friendly bump...
patch against -current attached, for convenience...
Marcus
Index: relay_http.c
===
RCS file: /cvs/src/usr.sbin/relayd/relay_http.c,v
retrieving revision 1.80
diff -u -p -u -r1.80
26 matches
Mail list logo
