On Sat, Oct 08, 2022 at 03:10:18PM +0300, Mikhail wrote:
> I'm troubleshooting battery status for my Lenovo IdeaPad 3 14ITL05, on
> latest -current it shows that battery is absent and AC not connected:
>
> Battery state: absent, 0% remaining, unknown life estimate
> AC adapter state: not connected
YASUOKA Masahiko wrote:
> Currently the value on VMware may be truncated silently. It's simply
> broken. I think we should fix it by having a way to know if the value
> is reached the limit.
>
> Also I think we should be able to pass larger size of data. Since at
> least on VMware, people is
On Wed, 12 Oct 2022 03:01:04 +0400, Klemens Nanni wrote:
> sparc64 also has its own under stand/,
> or do you mean that the alpha one is worse than the sparc64?
Oh yes, the alpha one is needlessly complicated. I suppose this
is not surprising considering the source.
- todd
Index: ps.1
===
RCS file: /cvs/src/bin/ps/ps.1,v
retrieving revision 1.128
diff -u -p -r1.128 ps.1
--- ps.13 Sep 2022 15:59:04 - 1.128
+++ ps.111 Oct 2022 23:20:34 -
@@ -443,7 +443,8 @@ information:
.Pp
12 Oct 2022 02:22:15 Todd C. Miller :
> This problem is not confined to sparc64 is it? At least macppc
> seems to have the same issue.
Looks like it, I have not yet tested other architectures.
> Some, like amd64 and i386, cheat and
> just pull in the 4 source files from the libz directory.
Y
Hello,
On Wed, 05 Oct 2022 13:37:35 +0900 (JST)
Masato Asou wrote:
> From: "Theo de Raadt"
> Date: Tue, 04 Oct 2022 21:58:13 -0600
>> Userland may not ask the kernel to allocate such a huge object. The
>> kernel address space is quite small. First off, huge allocations will
>> fail.
>>
>> But
This problem is not confined to sparc64 is it? At least macppc
seems to have the same issue. Some, like amd64 and i386, cheat and
just pull in the 4 source files from the libz directory.
It looks like alpha has its own libz and libsa directories which
seems even worse.
- todd
Testing the libz size fix in ofwboot.net showed that rebuilding ofwboot
after updating libz sources did not relink ofwboot as it should, imho:
$ cd sys/arch/sparc64/stand
$ make
...
$ touch ../../../lib/libz/crc32.c
$ make
===> bootblk
===> l
This builds on top of the previous two diffs.
Easiest way to test is to add the following line to vm.conf in
combination with snmpd(8):
agentx context foo
This results in:
[fd:6 sess:4009008336 ctx:foo]: region .1.3.6.1.2.1.236: opening
[fd:6 sess:4009008336 ctx:foo]: region .1.3.6.1.2.1.236: Uns
This one is on top of the don't reset errors diff.
This diff includes a minor bump. Don't know if we're still to close
after unlock.
If certain components (session, agentcaps, region, index, object) are
in a closed state while they are expected to be open, there is no way
to retry them without de
There's a couple of cases in libagentx where we call agentx_reset on
error cases returned by the server, which in turn results in the
connection being closed and retried.
There's no reason to expect the server to return another response on
the next try. I think it's better to just keep the differe
sparc64 RAMDISK already has NFSCLIENT enabled and miniroot's FSSIZE
still fits after linking mount_nfs:
/dev/vnd0a6312 5592 72089% 3 59
5% /mnt
This boots fine on T4-2 guest domains and I can upgrade via NFS:
Location of sets? (disk http n
On 11.10.2022. 17:16, Stuart Henderson wrote:
Hi,
> I tried this on my laptop which has I219-V em (I run it in a trunk
> with iwm). It breaks tx (packets don't show up on the other side).
> rx seems ok.
>
> There is also a "em0: watchdog: head 111 tail 20 TDH 20 TDT 111"
this em log can be trig
On 11.10.2022. 15:03, Moritz Buhl wrote:
> Here is a new diff for checksum offloading (ipv4, udp, tcp) for em(4).
>
> The previous diff didn't implement hardware vlan tagging for >em82578
> which should result in variable ethernet header lengths and thus
> wrong checksums inserted at wrong places.
On Tue, Oct 11, 2022 at 01:32:43PM +0200, Janne Johansson wrote:
> > On Mon, Oct 10, 2022 at 11:17:32AM -0600, Theo de Raadt wrote:
> > > It's been explained a few times that being up-to-date is not an error.
> > > It's a good thing, and no action is neccessary when up-to-date.
> > > Any non-zero v
On Mon, 10 Oct 2022 20:58:29 -, Klemens Nanni wrote:
> The ERR trap is supposed to be run once, regardless of errexit:
>
> $ ksh -c 'trap "echo ERR" ERR; false'
> ERR
> $ ksh -c 'trap "echo ERR" ERR; false' -e
> ERR
> ERR
>
> This duplication is a regression of th
On 2022/10/11 15:03, Moritz Buhl wrote:
> Here is a new diff for checksum offloading (ipv4, udp, tcp) for em(4).
>
> The previous diff didn't implement hardware vlan tagging for >em82578
> which should result in variable ethernet header lengths and thus
> wrong checksums inserted at wrong places.
Here is a new diff for checksum offloading (ipv4, udp, tcp) for em(4).
The previous diff didn't implement hardware vlan tagging for >em82578
which should result in variable ethernet header lengths and thus
wrong checksums inserted at wrong places.
The diff below addresses this.
I would appreciate
> After reading the script, I'd nitpick that it merely advances the
> version by one step rather than ensures the system is up-to-date, but I
Then again, this seem to match exactly what the manpage says it should be doing:
sysupgrade is a utility to upgrade OpenBSD to the next release or a n
On Tue, Oct 11, 2022 at 01:34:08PM +0200, Renaud Allard wrote:
>
>
> On 10/11/22 13:10, bug wrote:
> > On Mon, Oct 10, 2022 at 11:17:32AM -0600, Theo de Raadt wrote:
> > > It's been explained a few times that being up-to-date is not an error.
> > > It's a good thing, and no action is neccessary w
On 10/11/22 13:10, bug wrote:
On Mon, Oct 10, 2022 at 11:17:32AM -0600, Theo de Raadt wrote:
It's been explained a few times that being up-to-date is not an error.
It's a good thing, and no action is neccessary when up-to-date.
Any non-zero value indicates an error, that would include 2. You
> On Mon, Oct 10, 2022 at 11:17:32AM -0600, Theo de Raadt wrote:
> > It's been explained a few times that being up-to-date is not an error.
> > It's a good thing, and no action is neccessary when up-to-date.
> > Any non-zero value indicates an error, that would include 2. You are
> > marking this
On Mon, Oct 10, 2022 at 11:17:32AM -0600, Theo de Raadt wrote:
> It's been explained a few times that being up-to-date is not an error.
> It's a good thing, and no action is neccessary when up-to-date.
>
> Any non-zero value indicates an error, that would include 2. You are
> marking this as an e
On 2022/10/11 03:44, Mikolaj Kucharski wrote:
> On Mon, Oct 10, 2022 at 11:17:32AM -0600, Theo de Raadt wrote:
>
> > Any non-zero value indicates an error, that would include 2. You are
> > marking this as an error, when it isn't.
> >
> > You think this will help your scripting. Do you not real
24 matches
Mail list logo
