At the moment work items are enqueued in the order the CA intended them
to appear on a Manifest. However, I don't see any benefit to letting
third parties decide the order in which things are processed. Instead,
let's randomize: ordering has no meaning anyway, and the number of
concurrent
lfilled
> permanently and should be reported as an error.
>
> M_WAITOK is for all other cases. If it panics, fix the underlying
> bug that requested unrealistic memory size.
>
> Here use number of queues which should be reasonable low and limited
> by the driver code. Keep
o deal with
a temporary failure, e.g. drop the packet.
M_CANFAIL | M_WAITOK deals with user input that cannot be fullfilled
permanently and should be reported as an error.
M_WAITOK is for all other cases. If it panics, fix the underlying
bug that requested unrealistic memory size.
Here use numbe
On Fri, Apr 14, 2023 at 02:01:29PM +0200, Alexander Bluhm wrote:
>
> On Thu, Apr 13, 2023 at 10:43:30AM +0800, Kevin Lo wrote:
> > M_CANFAIL
> > In the M_WAITOK case, if not enough memory is available,
> > return NULL instead of calling panic(9). If mallocarray()
>
> Did you see such
On Thu, Apr 13, 2023 at 10:43:30AM +0800, Kevin Lo wrote:
> M_CANFAIL
> In the M_WAITOK case, if not enough memory is available,
> return NULL instead of calling panic(9). If mallocarray()
Did you see such a panic? If yes it would be better to understand
and fix the root cause.
>
On Thu, Apr 06, 2023 at 02:09:23PM +0200, Alexander Bluhm wrote:
>
> On Thu, Apr 06, 2023 at 02:58:56PM +0800, Kevin Lo wrote:
> > The diff below adds M_CANFAIL to the flag passed to malloc() since we are
> > able
> > to fail gracefully.
>
> I would not call a return ENOMEM a gracefull fail.
>
On Thu, Apr 06, 2023 at 02:58:56PM +0800, Kevin Lo wrote:
> The diff below adds M_CANFAIL to the flag passed to malloc() since we are able
> to fail gracefully.
I would not call a return ENOMEM a gracefull fail.
Usually if we can wait with M_WAITOK and everyting is fine afterwards,
that's a good
Hi,
The diff below adds M_CANFAIL to the flag passed to malloc() since we are able
to fail gracefully.
ok?
Index: sys/dev/pci/if_igc.c
===
RCS file: /cvs/src/sys/dev/pci/if_igc.c,v
retrieving revision 1.12
diff -u -p -u -p -r1.12
https://bugs.llvm.org/show_bug.cgi?id=50026
I reported it to the llvm people. it is two slightly different quicksort
algorithms which perform radically differently. The one which you could
assume would take more time, performs MUCH better.
I made a custom quicksort algorithm which outperforms
s happens on hosts on VMware ESXi 6.7,
> >> > 7.0 and asou's physical machine.
> >> >
> >> > The problem happens because efiboot calls ReadBlocks function with an
> >> > unaligned pointer for medias which requires an aligned pointer. Whe
> >booting cd0a:. [359648read symbols: Unknown error: code 255
>>> >
>>> > As far as Asou and my test, this happens on hosts on VMware ESXi 6.7,
>>> > 7.0 and asou's physical machine.
>>> >
>>> > The problem happens because
ils with a message like follow:
>> >
>> >booting cd0a:. [359648read symbols: Unknown error: code 255
>> >
>> > As far as Asou and my test, this happens on hosts on VMware ESXi 6.7,
>> > 7.0 and asou's physical machine.
>> >
>> > The problem happ
rom CD-ROM. In that case boot fails with a message like follow:
> >
> >booting cd0a:. [359648read symbols: Unknown error: code 255
> >
> > As far as Asou and my test, this happens on hosts on VMware ESXi 6.7,
> > 7.0 and asou's physical machine.
> >
> &g
> As far as Asou and my test, this happens on hosts on VMware ESXi 6.7,
> 7.0 and asou's physical machine.
>
> The problem happens because efiboot calls ReadBlocks function with an
> unaligned pointer for medias which requires an aligned pointer. When
> efiboot loads a kernel
physical machine.
The problem happens because efiboot calls ReadBlocks function with an
unaligned pointer for medias which requires an aligned pointer. When
efiboot loads a kernel, the pointer becomes unaligned since there is
an ELF section located at unaligned place in CD-ROM. Previously our
kernel
On Tue, Dec 08, 2020 at 03:04:58PM -0300, Daniel Bolgheroni wrote:
> Hi tech@,
>
Sorry, duplicate, disconsider since I sent it again just to find out I had no
rDNS.
--
db
Hi tech@,
I have a FT232H variant (marked FT232HQ, 0403:6014) which works with uftdi(4).
Still related to uftdi(4), sys/dev/usb/ftdi.c has a comment saying uftdi(4)
does not support multiple serial ports because ucom(4), but I'm able to use
both ucom(4) in parallel from a FT2232H (dual).
Thank
Hello OpenBSD devs. It has come to my attention that a mysterious commit
, unlogged by CVS, has appeared. This commit changes language, breaking
compatibility on header and source files.
Thankfully, it was logged by the Github mirror.
The commit's author is the Github username "djmdjm", and the
Go away troll.
- todd
On Thu, Jul 23, 2020 at 09:54:56PM +, goldeneagle96 wrote:
> Hello OpenBSD devs. It has come to my attention that a mysterious commit
> , unlogged by CVS, has appeared. This commit changes language, breaking
> compatibility on header and source files.
> Thankfully, it was logged by the Github
(Re-phrased for clarity.)
Please also log the user accounts which attempt to use revoked keys.
It would much more easily identify the problem account in question by
listing it on the same line as the offending revoked key in the log,
instead of in a separate log entry as it the case now
On Tue, Oct 23, 2018 at 09:53:48PM +, Adam Steen wrote:
> Hi tech
>
> The following diff allows vmd to specify which ports it can handle
> or fix "XXX something better than a hardcoded list here, maybe configure via
> vmd via the device list in vm create params?"
>
Hi tech
The following diff allows vmd to specify which ports it can handle
or fix "XXX something better than a hardcoded list here, maybe configure via
vmd via the device list in vm create params?"
There are currently two implementation of bsearch in the kernel and this patch
would a
On Tue, Jul 24, 2018 at 05:46:15PM +0100, Jason McIntyre wrote:
> On Tue, Jul 24, 2018 at 04:18:38PM +0200, Sebastian Benoit wrote:
> > phessler@ noticed that we dont document which redistribute settings
> > cause the priority filter to be enabled/disabled.
> &g
On Tue, Jul 24, 2018 at 04:18:38PM +0200, Sebastian Benoit wrote:
> phessler@ noticed that we dont document which redistribute settings
> cause the priority filter to be enabled/disabled.
>
> Add this text:
>
> The use of redistribute prefix and redist
phessler@ noticed that we dont document which redistribute settings
cause the priority filter to be enabled/disabled.
Add this text:
The use of redistribute prefix and redistribute rtlabel can in
some situations result in higher cpu usage because ospfd(8
On Mon, May 21, 2018 at 08:47:29PM +0200, Karel Gardas wrote:
>
> Hi,
>
> I do have 2 USB ethernet adapters based on Realtek 8153:
>
> TP-Link UE 300
> Lenovo Thinkpad USB 3.0 Gigabit Adapter
>
> both adapters work well with 6.3-current on amd64 platform. If however I try
> to use them on
Hi,
I do have 2 USB ethernet adapters based on Realtek 8153:
TP-Link UE 300
Lenovo Thinkpad USB 3.0 Gigabit Adapter
both adapters work well with 6.3-current on amd64 platform. If however I try to
use them on RPi3 with 6.3-current, both lead to system freeze. As I see it now,
there may be two
On Mon, Apr 16, 2018 at 12:32:25AM +0300, IL Ka wrote:
> See:
> https://marc.info/?l=openbsd-bugs=152380023916176=2
>
>
> diff --git usr.sbin/config/config.8 usr.sbin/config/config.8
> index 748aaab7a..10fdf7b92 100644
> --- usr.sbin/config/config.8
> +++ usr.sbin/config/config.8
> @@ -341,6
Hello,
> i'd be tempted to remove the instructions for building off a cd-rom, and
> leaving it as an exercise to the reader.
I am OK with it.
Lack of instructions is better than instruction that leads to
broken relink.
> the second (more common usage case) works fine, right?
Yes.
On Mon, Apr 16, 2018 at 12:32:25AM +0300, IL Ka wrote:
> See:
> https://marc.info/?l=openbsd-bugs=152380023916176=2
>
>
> diff --git usr.sbin/config/config.8 usr.sbin/config/config.8
> index 748aaab7a..10fdf7b92 100644
> --- usr.sbin/config/config.8
> +++ usr.sbin/config/config.8
> @@ -341,6
See:
https://marc.info/?l=openbsd-bugs=152380023916176=2
diff --git usr.sbin/config/config.8 usr.sbin/config/config.8
index 748aaab7a..10fdf7b92 100644
--- usr.sbin/config/config.8
+++ usr.sbin/config/config.8
@@ -341,6 +341,7 @@ mounted on
do the following:
.Bd -literal -offset indent
# cd
I'd like to easily see which CPU is holding the KERNEL_LOCK() in
ddb(4)'s "ps /o" output. This is really handy when debugging deadlocks.
So the diff below adds a 'struct cpu_info *' argument to __mp_lock_held()
and use it in the corresponding DDB command.
Note that this requires th
http://www.emojicode.org <http://www.emojicode.org/>
Unfortunately, I don't think that it has been ported to OpenBSD yet
(and you'll need a terminal with an emoji font)
Reyk
> On 19.07.2017, at 12:13, Peer Dong <peerd...@hotmail.com> wrote:
>
> Hi Tech,
>
>
&
On 19/07/17 13:13, Peer Dong wrote:
> Hi Tech,
>
>
> which programming language should i dig on to understand the programming
> codes i am reading.
>
>
> thanks again.
>
> Peerdong.
C
https://en.wikipedia.org/wiki/C_(programming_language)
Hi Tech,
which programming language should i dig on to understand the programming codes
i am reading.
thanks again.
Peerdong.
Theo Buehler wrote:
> On Sat, Dec 24, 2016 at 10:45:16PM +0100, Theo Buehler wrote:
> > On Sat, Dec 24, 2016 at 05:44:07PM +0100, Jérôme FRGACIC wrote:
> > > Hi @tech,
> > >
> > > I remark that ed(1) do not support adress ranges which begin with
> > >
On Sat, Dec 24, 2016 at 10:45:16PM +0100, Theo Buehler wrote:
> On Sat, Dec 24, 2016 at 05:44:07PM +0100, Jérôme FRGACIC wrote:
> > Hi @tech,
> >
> > I remark that ed(1) do not support adress ranges which begin with
> > comma or semicolon, for example ",10
On Sat, Dec 24, 2016 at 05:44:07PM +0100, Jérôme FRGACIC wrote:
> Hi @tech,
>
> I remark that ed(1) do not support adress ranges which begin with
> comma or semicolon, for example ",10p" which is equivalent to "1,10p" or
> "; +10p" which i
Hi @tech,
I remark that ed(1) do not support adress ranges which begin with
comma or semicolon, for example ",10p" which is equivalent to "1,10p" or
"; +10p" which is equivalent to ".;+10p". These adress ranges are
specified by Open Group Base Specification
nd does nothing (a SCAN->SCAN transition is a no-op in the driver).
> > So the second scan attempt times out, and ifconfig gets no results.
> >
> > This diff adds a 'scan all bands' capability which the driver can advertise
> > to tell the net80211 layer that it should n
efore results are returned to ifconfig, and retries on a different band.
> The driver however insists that it is already done scanning everything,
> and does nothing (a SCAN->SCAN transition is a no-op in the driver).
> So the second scan attempt times out, and ifconfig gets no results.
>
&
->SCAN transition is a no-op in the driver).
So the second scan attempt times out, and ifconfig gets no results.
This diff adds a 'scan all bands' capability which the driver can advertise
to tell the net80211 layer that it should not retry the scan on a different
band. Setting this flag in the
This file forms a character set for banners that should work on almost
any printer.
Differs from banner program characters, they have an extra line above
for characters like %,},etc and vertical bar is split in banner program
but full here.
Index: lpdchar.c
On Wed, Jan 27, 2016 at 03:43:55PM -0600, Chris Bennett wrote:
> This file forms a character set for banners that should work on almost
> any printer.
> Differs from banner program characters, they have an extra line above
> for characters like %,},etc and vertical bar is split in banner program
>
I think using _PATH_DEFPATH in the absence of PATH is better.
- todd
Index: Makefile
===
RCS file: /cvs/src/usr.bin/which/Makefile,v
retrieving revision 1.8
diff -u -p -u -r1.8 Makefile
--- Makefile15 Apr 2013 16:34:19 -
On Thu, 14 Jan 2016 01:28:02 +0100, Max Fillinger wrote:
> If PATH starts with "/:", which(1) reads outside of allocated memory.
> Maybe that caused the non-reproduceable coredump mentioned in [0]?
Committed, thanks.
- todd
If PATH starts with "/:", which(1) reads outside of allocated memory.
Maybe that caused the non-reproduceable coredump mentioned in [0]?
The function progname sets path = strdup(path) and pathcpy = path and
runs the following loop:
> while ((p = strsep(, ":")) != NULL) {
The man page says that which(1) works with unset PATH environment
variable, as long as the argument is a pathname. However:
$ unset PATH
$ /usr/bin/which /usr/bin/which
which: can't get $PATH from environment: Undefined error: 0
Index: usr.bin/which/which.1
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
On Sun, Jan 04, 2015 at 08:38:03PM EST, Riley Baird wrote:
This is my last post. I'm leaving all of the OpenBSD mailing lists
because quite frankly I don't want to argue about this anymore,
especially not with someone who themselves did *exactly the same thing*
Even when building with the NOMAN option, which will not build without
the manpage whereis.1 being present.
This patch checks to see whether NOMAN is defined, and if not, does not
do the tests related to path expansion.
Index: usr.bin/which/Makefile
On Sun, Jan 4, 2015 at 12:52 PM, Riley Baird
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote:
Even when building with the NOMAN option, which will not build without
the manpage whereis.1 being present.
Building from an incomplete source tree is not supported (deleting
just
On Sun, Jan 4, 2015 at 12:52 PM, Riley Baird
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote:
Even when building with the NOMAN option, which will not build without
the manpage whereis.1 being present.
Building from an incomplete source tree is not supported (deleting
just
On 05/01/15 11:17, Theo de Raadt wrote:
On Sun, Jan 4, 2015 at 12:52 PM, Riley Baird
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote:
Even when building with the NOMAN option, which will not build without
the manpage whereis.1 being present.
Building from an incomplete source tree
On 05/01/15 11:17, Theo de Raadt wrote:
On Sun, Jan 4, 2015 at 12:52 PM, Riley Baird
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote:
Even when building with the NOMAN option, which will not build without
the manpage whereis.1 being present.
Building from an incomplete source tree
On 05/01/15 11:41, Theo de Raadt wrote:
On 05/01/15 11:17, Theo de Raadt wrote:
On Sun, Jan 4, 2015 at 12:52 PM, Riley Baird
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote:
Even when building with the NOMAN option, which will not build without
the manpage whereis.1 being present
On 01/04/15 19:38, Riley Baird wrote:
On 05/01/15 11:41, Theo de Raadt wrote:
On 05/01/15 11:17, Theo de Raadt wrote:
On Sun, Jan 4, 2015 at 12:52 PM, Riley Baird
bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote:
Even when building with the NOMAN option, which will not build without
Re: hi, hope you are fine, my Name is Paulina, I will want us to be
friends, for something important which I would like to share with u, we
will get to know each other better i am waiting for your responds, (
distance or colour does not matter ) urs Paul thought you would be
interested
On Fri, 2011-03-11 at 15:44 +0500, Anton Maksimenkov wrote:
Hi.
If someone has te vte (r6040 chip) network interface please, test this diff.
It solves problems like these:
First, it seems that dhclient don't work on vte.
Second, it seems vte looses network after minute(s) of inactivity
Hi.
If someone has te vte (r6040 chip) network interface please, test this diff.
It solves problems like these:
First, it seems that dhclient don't work on vte.
Second, it seems vte looses network after minute(s) of inactivity
(machine don't responds to ping etc).
Network restores when I type
On Mon, Feb 14, 2011 at 3:31 AM, David Julio david.a.ju...@gmail.com wrote:
...
Index: which.c
===
RCS file: /cvs/src/usr.bin/which/which.c,v
retrieving revision 1.16
diff -u -r1.16 which.c
--- which.c 31 May 2010 14:01:49
On 3/1/11, Jason McIntyre j...@cava.myzen.co.uk wrote:
On Mon, Feb 14, 2011 at 11:31:18AM +, David Julio wrote:
Is the exit status of which(1)/whereis(1) correct?
is any developer interested in looking at this?
I like the diff and will commit it in 24hrs if no objects.
I'll note
On Mon, Feb 14, 2011 at 11:31:18AM +, David Julio wrote:
Is the exit status of which(1)/whereis(1) correct?
$ which a b c
which: a: Command not found
which: b: Command not found
which: c: Command not found
$ echo $?
2
$ which -a a b c
which: a: Command not found
which: b
On Tue, Feb 15, 2011 at 05:30:11PM +, Jason McIntyre wrote:
On Mon, Feb 14, 2011 at 11:31:18AM +, David Julio wrote:
Is the exit status of which(1)/whereis(1) correct?
$ which a b c
which: a: Command not found
which: b: Command not found
which: c: Command not found
Is the exit status of which(1)/whereis(1) correct?
$ which a b c
which: a: Command not found
which: b: Command not found
which: c: Command not found
$ echo $?
2
$ which -a a b c
which: a: Command not found
which: b: Command not found
which: c: Command not found
$ echo $?
1
If it is incorrect
Dear Marketer, Generating new business is tougher than ever, and you might
feel like marketing is a losing battle. I'd like to invite you do download my
FREE audio book (http://mym411.com/) and find real answers that can help you
find solutions to any marketing challenge you may be facing,
which(1) prints error messages on stdout, breaking shell scripts and
common usage patterns:
ldd `which foo`
ldd: foo:: No such file or directory
ldd: Command: No such file or directory
ldd: not: No such file or directory
ldd: found.: No such file or directory
X=$(which foo 2/dev/null)
test -n $X
versions of VirtualBox using
different host operating systems, however there were always issues which
would generally lead to various issues including kernel panics.
My advice is to not run it virtualized.
Rich
I run 3 openbsd 4.6 virtualized with VBox (3.1.6 ) on a MacBook
and I have
On Mon, Apr 5, 2010 at 11:38 AM, Sean Kennedy woodentu...@hotmail.com
wrote:
I concur, it was a Valid question on running OpenBSD in a VM.
really, i was very radical in the last email. really. shut it up and
hack. maybe starting helping the virtualbox guys to close the related
bug at
operating systems, however there were always issues which
would generally lead to various issues including kernel panics.
My advice is to not run it virtualized.
Rich
virtualize your brain. it is nice.
On Fri, Apr 2, 2010 at 6:23 AM, Zachary Uram net...@gmail.com wrote:
I have never run OpenBSD before and want to try it out. Wondering if
there is an ISO I can run in VirtualBox? If not what is the
recommended method for users who wish to run OpenBSD in
72 matches
Mail list logo
