On Wed, Jul 24, 2024 at 11:34 AM m...@freebsd.org
wrote:
>
>
> On 24.07.2024 17:47, Konstantin Belousov wrote:
> > On Wed, Jul 24, 2024 at 01:07:39PM +, John F Carr wrote:
> >>
> >>
> >>> On Jul 24, 2024, at 06:50, Konstantin Belousov
> wrote:
> >>>
> >>> On Wed, Jul 24, 2024 at 12:34:57PM
On 24.07.2024 17:47, Konstantin Belousov wrote:
On Wed, Jul 24, 2024 at 01:07:39PM +, John F Carr wrote:
On Jul 24, 2024, at 06:50, Konstantin Belousov wrote:
On Wed, Jul 24, 2024 at 12:34:57PM +0200, m...@freebsd.org wrote:
On 24.07.2024 12:24, Konstantin Belousov wrote:
On
On Wed, Jul 24, 2024 at 01:07:39PM +, John F Carr wrote:
>
>
> > On Jul 24, 2024, at 06:50, Konstantin Belousov wrote:
> >
> > On Wed, Jul 24, 2024 at 12:34:57PM +0200, m...@freebsd.org wrote:
> >>
> >>
> >> On 24.07.2024 12:24, Konstantin Belousov wrote:
> >>> On Tue, Jul 23, 2024 at
> On Jul 24, 2024, at 06:50, Konstantin Belousov wrote:
>
> On Wed, Jul 24, 2024 at 12:34:57PM +0200, m...@freebsd.org wrote:
>>
>>
>> On 24.07.2024 12:24, Konstantin Belousov wrote:
>>> On Tue, Jul 23, 2024 at 08:11:13PM +, John F Carr wrote:
On Jul 23, 2024, at 13:46, Michal
On Wed, Jul 24, 2024 at 12:34:57PM +0200, m...@freebsd.org wrote:
>
>
> On 24.07.2024 12:24, Konstantin Belousov wrote:
> > On Tue, Jul 23, 2024 at 08:11:13PM +, John F Carr wrote:
> > > On Jul 23, 2024, at 13:46, Michal Meloun wrote:
> > > >
> > > > On 23.07.2024 11:36, Konstantin
On 24.07.2024 12:24, Konstantin Belousov wrote:
On Tue, Jul 23, 2024 at 08:11:13PM +, John F Carr wrote:
On Jul 23, 2024, at 13:46, Michal Meloun wrote:
On 23.07.2024 11:36, Konstantin Belousov wrote:
On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
The good news is
On Tue, Jul 23, 2024 at 08:11:13PM +, John F Carr wrote:
> On Jul 23, 2024, at 13:46, Michal Meloun wrote:
> >
> > On 23.07.2024 11:36, Konstantin Belousov wrote:
> >> On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
> >>> The good news is that I'm finally able to generate a
On Tue, Jul 23, 2024 at 2:11 PM John F Carr wrote:
> On Jul 23, 2024, at 13:46, Michal Meloun wrote:
> >
> > On 23.07.2024 11:36, Konstantin Belousov wrote:
> >> On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
> >>> The good news is that I'm finally able to generate a
On Mon, Jul 22, 2024 at 01:00:11AM -0700, Gleb Smirnoff wrote:
T> This is an automated email to inform you that the July 2024 stabilization
week
T> started with FreeBSD/main at main-n271321-9ae91f59c500, which was tagged as
T> main-stabweek-2024-Jul.
Testing at Netflix didn't discover any
On Jul 23, 2024, at 13:46, Michal Meloun wrote:
>
> On 23.07.2024 11:36, Konstantin Belousov wrote:
>> On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
>>> The good news is that I'm finally able to generate a working/locking
>>> test case. The culprit (at least for me) is if
On Tue, Jul 23, 2024 at 07:46:51PM +0200, Michal Meloun wrote:
>
>
> On 23.07.2024 11:36, Konstantin Belousov wrote:
> > On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
> > > The good news is that I'm finally able to generate a working/locking
> > > test case. The culprit (at
On 23.07.2024 11:36, Konstantin Belousov wrote:
On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
The good news is that I'm finally able to generate a working/locking
test case. The culprit (at least for me) is if "-mcpu" is used when
compiling libthr (e.g. indirectly injected
On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote:
> The good news is that I'm finally able to generate a working/locking
> test case. The culprit (at least for me) is if "-mcpu" is used when
> compiling libthr (e.g. indirectly injected via CPUTYPE in /etc/make.conf).
> If it is not
On Jul 22, 2024, at 12:36, Michal Meloun wrote:
> On 22. 7. 2024 19:27, Mark Millard wrote:
>> On Jul 22, 2024, at 09:41, meloun.mic...@gmail.com wrote:
>>
>>
>>> On 22.07.2024 18:26, Mark Millard wrote:
>>>
On Jul 22, 2024, at 06:40, Michal Meloun wrote:
> On 22.07.2024 13:46,
> On Jul 22, 2024, at 12:51, Mark Millard wrote:
>
> Another systematic difference in my personal builds vs.
> official pkgbase builds, snapshots, releases, etc. is
> that my armv7 builds are built on aarch64-as-armv7, not
> on amd64. Not that I have any specific evidence that
> such matters
As this is stabilization week and as I'm virtually AFK next week, WPA 2.11
will be imported into main the week of August 12. If people do want to try
it out I can make it available for testing. But my time to work on problems
next week, starting this Friday, will be severely limited next week.
On Jul 22, 2024, at 09:41, meloun.mic...@gmail.com wrote:
> On 22.07.2024 18:26, Mark Millard wrote:
>> On Jul 22, 2024, at 06:40, Michal Meloun wrote:
>>> On 22.07.2024 13:46, Mark Millard wrote:
On Jul 21, 2024, at 22:59, Michal Meloun wrote:
> I don't want to hijack the original
Another systematic difference in my personal builds vs.
official pkgbase builds, snapshots, releases, etc. is
that my armv7 builds are built on aarch64-as-armv7, not
on amd64. Not that I have any specific evidence that
such matters here.
But Michal Meloun's report indicated not using builds
done
On Jul 22, 2024, at 06:40, Michal Meloun wrote:
> On 22.07.2024 13:46, Mark Millard wrote:
>> On Jul 21, 2024, at 22:59, Michal Meloun wrote:
>>> I don't want to hijack the original thread, so I'm replying in a new one.
>>>
>>> My tegra track current, has been running 24/7 by building
First, sorry for late response.
cglogic, thank you for bringing up this issue again since I nearly forgot that
this issue was still open.
Warner, as I can't access to my FreeBSD instance until the end of August, but I
can still edit and push the code through my Arm Mac. This means that I can't
On Jul 21, 2024, at 22:59, Michal Meloun wrote:
> I don't want to hijack the original thread, so I'm replying in a new one.
>
> My tegra track current, has been running 24/7 by building kernel/world and
> kde5 in a loop for a few years now. But I have never encountered the
> aforementioned
On Jul 21, 2024, at 21:08, Mark Millard wrote:
> On Jul 21, 2024, at 20:58, Mark Millard wrote:
>
>> I found a significant difference in my failing vs. working
>> armv7 contexts as installed: Presence vs. Lack of a .symtab
>> entry for the symbol _rtld_get_stack_prot in
>> /libexec/ld-elf.so.1
Hi FreeBSD/main users & developers:
This is an automated email to inform you that the July 2024 stabilization week
started with FreeBSD/main at main-n271321-9ae91f59c500, which was tagged as
main-stabweek-2024-Jul.
The tag main-stabweek-2024-Jul has been published at
On Jul 21, 2024, at 20:58, Mark Millard wrote:
> I found a significant difference in my failing vs. working
> armv7 contexts as installed: Presence vs. Lack of a .symtab
> entry for the symbol _rtld_get_stack_prot in
> /libexec/ld-elf.so.1 .
>
> gdb inspection of operation shows distinctions
I found a significant difference in my failing vs. working
armv7 contexts as installed: Presence vs. Lack of a .symtab
entry for the symbol _rtld_get_stack_prot in
/libexec/ld-elf.so.1 .
gdb inspection of operation shows distinctions based on
the difference.
This is related to the code:
(gdb)
[Correction to a rather misleading wording in
my description of the failure sequencing.]
On Jul 21, 2024, at 03:36, Mark Millard wrote:
> On Jul 20, 2024, at 16:42, Mark Millard wrote:
>
>> On Jul 20, 2024, at 01:57, Konstantin Belousov wrote:
>>
>>> [Everything and everybody in Cc: are
On Sun, Jul 21, 2024 at 2:03 PM cglogic wrote:
>
> On Sunday, July 21st, 2024 at 6:54 AM, Warner Losh wrote:
>
>
>
> On Sat, Jul 20, 2024 at 1:59 AM cglogic wrote:
>
>> Hello FreeBSD community,
>>
>> After Jason Evans stepped aside from maintaining jemalloc in FreeBSD,
>> it's not updating in
On Sunday, July 21st, 2024 at 6:54 AM, Warner Losh wrote:
> On Sat, Jul 20, 2024 at 1:59 AM cglogic wrote:
>
>> Hello FreeBSD community,
>>
>> After Jason Evans stepped aside from maintaining jemalloc in FreeBSD, it's
>> not updating in time anymore.
>> Version 5.3.0 was released May 6, 2022
On Jul 20, 2024, at 16:42, Mark Millard wrote:
> On Jul 20, 2024, at 01:57, Konstantin Belousov wrote:
>
>> [Everything and everybody in Cc: are stripped for good].
>>
>> On Fri, Jul 19, 2024 at 10:38:36PM -0700, Mark Millard wrote:
>>> 0x201375c0 - 0x2014092c is .bss in /lib/libthr.so.3
>>>
On Sat, Jul 20, 2024 at 1:59 AM cglogic wrote:
> Hello FreeBSD community,
>
> After Jason Evans stepped aside from maintaining jemalloc in FreeBSD,
> it's not updating in time anymore.
> Version 5.3.0 was released May 6, 2022 and FreeBSD still not imported it
> into the tree.
>
> There is a
On Jul 20, 2024, at 01:57, Konstantin Belousov wrote:
> [Everything and everybody in Cc: are stripped for good].
>
> On Fri, Jul 19, 2024 at 10:38:36PM -0700, Mark Millard wrote:
>> 0x201375c0 - 0x2014092c is .bss in /lib/libthr.so.3
>>
>> (gdb) bt
>> #0 0x201aeec0 in
On Jul 20, 2024, at 01:57, Konstantin Belousov wrote:
> [Everything and everybody in Cc: are stripped for good].
>
> On Fri, Jul 19, 2024 at 10:38:36PM -0700, Mark Millard wrote:
>> 0x201375c0 - 0x2014092c is .bss in /lib/libthr.so.3
>>
>> (gdb) bt
>> #0 0x201aeec0 in
On Jul 20, 2024, at 01:57, Konstantin Belousov wrote:
> [Everything and everybody in Cc: are stripped for good].
>
> On Fri, Jul 19, 2024 at 10:38:36PM -0700, Mark Millard wrote:
>> 0x201375c0 - 0x2014092c is .bss in /lib/libthr.so.3
>>
>> (gdb) bt
>> #0 0x201aeec0 in
[Everything and everybody in Cc: are stripped for good].
On Fri, Jul 19, 2024 at 10:38:36PM -0700, Mark Millard wrote:
> 0x201375c0 - 0x2014092c is .bss in /lib/libthr.so.3
>
> (gdb) bt
> #0 0x201aeec0 in __pthread_map_stacks_exec () from /lib/libc.so.7
> #1 0x2005d1e4 in ?? () from
Hello FreeBSD community,
After Jason Evans stepped aside from maintaining jemalloc in FreeBSD, it's not
updating in time anymore.
Version 5.3.0 was released May 6, 2022 and FreeBSD still not imported it into
the tree.
There is a pending review https://reviews.freebsd.org/D41421 from Aug 11,
On Jul 18, 2024, at 01:14, Mark Millard wrote:
> On Jul 16, 2024, at 23:45, Mark Millard wrote:
>
>> On Jul 16, 2024, at 18:41, Mark Millard wrote:
>>
>>> On Jul 16, 2024, at 11:37, Mark Millard wrote:
>>>
On Jul 16, 2024, at 10:42, Mark Millard wrote:
> No longer is the
I want to test the ZFS raidz expansion feature.
I have create a VM with vm-bhyve:
# vm iso
https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/FreeBSD-15.0-CURRENT-amd64-20240718-a4469a0d19b6-271237-bootonly.iso
# vm create fbsd15-bis
I have increased the VM memory to 2G:
# cat
Scanning the build typescript, I find:
...
Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/w/uptime.1.gz
ld: error: undefined symbol: libzfs_core_init
>>> referenced by zdb.c:9207 (/usr/src/sys/contrib/openzfs/cmd/zdb/zdb.c:9207)
>>> zdb.o:(main)
Building
On Jul 16, 2024, at 23:45, Mark Millard wrote:
> On Jul 16, 2024, at 18:41, Mark Millard wrote:
>
>> On Jul 16, 2024, at 11:37, Mark Millard wrote:
>>
>>> On Jul 16, 2024, at 10:42, Mark Millard wrote:
>>>
No longer is the problem only observed on ampere2! But this was with
a
On Jul 16, 2024, at 18:41, Mark Millard wrote:
> On Jul 16, 2024, at 11:37, Mark Millard wrote:
>
>> On Jul 16, 2024, at 10:42, Mark Millard wrote:
>>
>>> No longer is the problem only observed on ampere2! But this was with
>>> a non-debug, personally built kernel that has some of my now
On Jul 16, 2024, at 11:37, Mark Millard wrote:
> On Jul 16, 2024, at 10:42, Mark Millard wrote:
>
>> No longer is the problem only observed on ampere2! But this was with
>> a non-debug, personally built kernel that has some of my now patches.
>> I'll see if I can replicate the issue with an
13.2 works. 13.3 and 14.x panic.
an older system with two qlogic isp cards, isp0 and isp1, nothing attached to them, and it panics on boot with 13.3 and 14.x images.
13.2 works
Autoloading module: ichsmb
ichsmb0: port 0x300-0x31f irq 22 at device 31.3 on pci0
smbus0: on
[I CC'd Bryan D. in case this is related to the
failed rm activity tied to disamounts that are
not happening first. I had reported on an example.]
I got the following from poudriere-devel activity
on a system running a pkgbase main debug kernel.
Note that nullfs_unmount and null_lock are also
On Jul 16, 2024, at 10:42, Mark Millard wrote:
> No longer is the problem only observed on ampere2! But this was with
> a non-debug, personally built kernel that has some of my now patches.
> I'll see if I can replicate the issue with an official pkgbase debug
> kernel.
It replicated with the
No longer is the problem only observed on ampere2! But this was with
a non-debug, personally built kernel that has some of my now patches.
I'll see if I can replicate the issue with an official pkgbase debug
kernel.
FYI for the replication that I got:
/usr/local/sbin/pkg-static add -A
Thanks,
Another idea that could work
/Rescue had nothing to do with this, i was doing a normal boot
it was working , not all of it
Ivan
> -Mensagem original-
> De: Alexander Ziaee
> Enviada em: domingo, 14 de julho de 2024 22:06
> Para: tezeka
> Cc: freebsd-current
> Assunto:
Am 2024-07-15 03:05, schrieb Alexander Ziaee:
Eventually, you want to learn to snapshot your system when you're
touching critical directories. Then, it never matters. You can just
roll back stressfree.
Specific to updates and if on ZFS: man bectl
Even better than snapshots.
Bye,
Alexander.
Hello!
> I made a big mess here.
> I (deleted my system libraries)
If I have no snapshots:
- boot into the installer
- mount
- copy /usr/*
It's not good, but it's good enough to get going to restore from backup or
makeworld at your leisure.
Eventually, you want to learn to snapshot your
On 7/14/24 21:00, Warner Losh wrote:
M*ay*be try https://reviews.freebsd.org/D45554 and see if that works?
Warner
I confirm it works. Thank you very much!
M*ay*be try https://reviews.freebsd.org/D45554 and see if that works?
Warner
On Sun, Jul 14, 2024 at 7:18 AM Dmitry Salychev wrote:
>
> Goran Mekić writes:
>
> > On 7/13/24 18:18, Chris wrote:
> >> On 2024-07-13 15:23, Goran Mekić wrote:
> >>> Hello,
> >>>
> >>> I have a laptop with a weird
Goran Mekić writes:
> On 7/13/24 18:18, Chris wrote:
>> On 2024-07-13 15:23, Goran Mekić wrote:
>>> Hello,
>>>
>>> I have a laptop with a weird behaving keyboard. Under Linux
>>> everything is fine,
>>> but under FreeBSD it is out of sync. On single key stroke of letter
>>> 'c' (just for
>>>
On 7/13/24 18:18, Chris wrote:
On 2024-07-13 15:23, Goran Mekić wrote:
Hello,
I have a laptop with a weird behaving keyboard. Under Linux
everything is fine,
but under FreeBSD it is out of sync. On single key stroke of letter
'c' (just for
example) terminal first doesn't do anything for
Looks like thats the way ill go
Thank you , but takes time, will let you guys know when I have something
But thank you for the help, really appreciated
Ivan
Thanks too Rick
> -Mensagem original-
> De: Alastair Hogge
> Enviada em: sábado, 13 de julho de 2024 23:40
> Para: Ivan
On Sat, Jul 13, 2024 at 7:40 PM Alastair Hogge wrote:
>
> On 2024-07-14 09:54, Ivan Quitschal wrote:
> > One idea
> > Cant say it that would help , but ive checked here and 2 things are working
> >
> > mount command
> > usb is all good
> >
> > and the filesystem is fine too.
> > So does anybody
On 2024-07-14 09:54, Ivan Quitschal wrote:
> One idea
> Cant say it that would help , but ive checked here and 2 things are working
>
> mount command
> usb is all good
>
> and the filesystem is fine too.
> So does anybody knows where I could literally get the entire 15-CURRENT
> containing the
One idea
Cant say it that would help , but ive checked here and 2 things are working
mount command
usb is all good
and the filesystem is fine too.
So does anybody knows where I could literally get the entire 15-CURRENT
containing the entire /usr/src in tar.gz or something?
I could download it
Hi all
I made a big mess here. Please lets see if you guys have any idea
I did a
make buildkernel
make installkernel
Then forgot the buildworld
And went straight to
make delete-old
make delete-old-libs
now not even git command, or ports or nothing because everything is missing on
libraries,
On 2024-07-13 15:23, Goran Mekić wrote:
Hello,
I have a laptop with a weird behaving keyboard. Under Linux everything is
fine,
but under FreeBSD it is out of sync. On single key stroke of letter 'c'
(just for
example) terminal first doesn't do anything for about a second, then it
prints
Hello,
I have a laptop with a weird behaving keyboard. Under Linux everything
is fine, but under FreeBSD it is out of sync. On single key stroke of
letter 'c' (just for example) terminal first doesn't do anything for
about a second, then it prints multiple letters 'c' in a row. Is there
any
On 12/07/2024 18:45, Tomoaki AOKI wrote:
On Fri, 12 Jul 2024 14:35:15 +0200
Miroslav Lachman <000.f...@quip.cz> wrote:
On 12/07/2024 11:56, Tomoaki AOKI wrote:
[..]
*Hardware problem
*Main memory (including memory slot)
*Dedicated grhaphics memories, if any
(seems
On Fri, 12 Jul 2024 14:35:15 +0200
Miroslav Lachman <000.f...@quip.cz> wrote:
> On 12/07/2024 11:56, Tomoaki AOKI wrote:
> > On Fri, 12 Jul 2024 10:20:19 +0200
> > Miroslav Lachman <000.f...@quip.cz> wrote:
>
> [..]
>
> >> Something similar happens to me, but when logging into KDE Plasma.
> >>
On 12/07/2024 11:56, Tomoaki AOKI wrote:
On Fri, 12 Jul 2024 10:20:19 +0200
Miroslav Lachman <000.f...@quip.cz> wrote:
[..]
Something similar happens to me, but when logging into KDE Plasma.
Sometimes it happens that desktop applications that start from a saved
session (Firefox, Thunderbird,
Van: Konstantin Belousov
Datum: vrijdag, 12 juli 2024 13:15
Aan: FreeBSD Current
Onderwerp: Re: exited on signal 11 (no core dump - other error)
On Fri, Jul 12, 2024 at 10:45:31AM +, Dave Cottlehuber wrote:
> On Fri, 12 Jul 2024, at 03:39, Zhenlei Huang wrote:
> > Hi
> >
> > I observed
On Fri, Jul 12, 2024 at 10:45:31AM +, Dave Cottlehuber wrote:
> On Fri, 12 Jul 2024, at 03:39, Zhenlei Huang wrote:
> > Hi
> >
> > I observed something weird on Release 14.1.
> >
> > When rebooting my dev machine, I got
> > ...
> > IIUC all processes will get signal to quit on system reboot.
On Fri, 12 Jul 2024, at 03:39, Zhenlei Huang wrote:
> Hi
>
> I observed something weird on Release 14.1.
>
> When rebooting my dev machine, I got
> ...
> IIUC all processes will get signal to quit on system reboot. But what does the
> signal 11 mean ? Is it EDEADLK in sys/sys/errno.h ?
>
> If yes,
On 12/07/2024 07:02, Rick Macklem wrote:
On Thu, Jul 11, 2024 at 8:40 PM Zhenlei Huang wrote:
Hi
I observed something weird on Release 14.1.
When rebooting my dev machine, I got
---<>---
Copyright (c) 1992-2023 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991,
a very, very long time ago (late '90s) I reported something like that to
Jordan Hubbard. He suggested HW issues ... honestly can't remember whether
he was right :-/
On Fri, Jul 12, 2024 at 7:03 AM Rick Macklem wrote:
> On Thu, Jul 11, 2024 at 8:40 PM Zhenlei Huang wrote:
> >
> > Hi
> >
> > I
On Thu, Jul 11, 2024 at 8:40 PM Zhenlei Huang wrote:
>
> Hi
>
> I observed something weird on Release 14.1.
>
> When rebooting my dev machine, I got
>
> ---<>---
> Copyright (c) 1992-2023 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
> The
Hi
I observed something weird on Release 14.1.
When rebooting my dev machine, I got
---<>---
Copyright (c) 1992-2023 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is
Hi,
we've been running the stabilization week of FreeBSD/main aka CURRENT since
February. And it has been public since March. So we have had 5 cycles already
and 4 were public.
I'm eager to get some feedback from people who had been positively or
negatively affected by this initiative.
main's armv7 packages that are distributed are getting to be months
behind because of the build hangups preventing the builds on ampere2.
The hangups happen just-after graphics/graphviz installation during
the activity in a builder where that build depends on
graphics/graphviz .
I expect that
On Tue, Jul 2, 2024 at 7:30 AM Rodney W. Grimes
wrote:
>
> > On Sun, Jun 30, 2024 at 8:23?AM Rodney W. Grimes
> > wrote:
> > >
> > > > On Fri, Jun 28, 2024 at 6:26?PM Rick Macklem
> > > > wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I've installed FreeBSD current in a bhvye instance.
> On Sun, Jun 30, 2024 at 8:23?AM Rodney W. Grimes
> wrote:
> >
> > > On Fri, Jun 28, 2024 at 6:26?PM Rick Macklem
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I've installed FreeBSD current in a bhvye instance. Everything
> > > > went ok, with UFS as a root partition.
> > > > Then I
On 29. Jun 2024, at 03:26, Rick Macklem wrote:
>
> Hi,
>
> I've installed FreeBSD current in a bhvye instance. Everything
> went ok, with UFS as a root partition.
> Then I created a zpool in another partition...
> - Now, every time I boot it I have to
> OK set currdev=disk0s1a:
> to get it to
On Sun, Jun 30, 2024 at 8:23 AM Rodney W. Grimes
wrote:
>
> > On Fri, Jun 28, 2024 at 6:26?PM Rick Macklem wrote:
> > >
> > > Hi,
> > >
> > > I've installed FreeBSD current in a bhvye instance. Everything
> > > went ok, with UFS as a root partition.
> > > Then I created a zpool in another
Hi,
Since updating to 15-CURRENT, I have been unable to get some existing code that
used libzfs_core to take snapshots. There are a lot of reasons that this could
have broken and it’s hard to track it down:
- We ship both libnv and libnvpair. These define the same data structure but
with
Hi,
I just put a patch on phabricator (D45814) that adds support for multiple
sets of options for different hosts/networks to the ZFS sharenfs property.
(It is based loosely on a patch in bugzilla PR#147881, now 14 years old.)
I have listed a couple of reviewers, but please feel free to review
> On Fri, Jun 28, 2024 at 6:26?PM Rick Macklem wrote:
> >
> > Hi,
> >
> > I've installed FreeBSD current in a bhvye instance. Everything
> > went ok, with UFS as a root partition.
> > Then I created a zpool in another partition...
> > - Now, every time I boot it I have to
> > OK set
On Fri, Jun 28, 2024 at 6:26 PM Rick Macklem wrote:
>
> Hi,
>
> I've installed FreeBSD current in a bhvye instance. Everything
> went ok, with UFS as a root partition.
> Then I created a zpool in another partition...
> - Now, every time I boot it I have to
> OK set currdev=disk0s1a:
> to get it
Hi,
I've installed FreeBSD current in a bhvye instance. Everything
went ok, with UFS as a root partition.
Then I created a zpool in another partition...
- Now, every time I boot it I have to
OK set currdev=disk0s1a:
to get it to boot.
What is the trick to keep ZFS from messing up the boot
On Thu, Jun 27, 2024 at 03:12:47PM +0200, Baptiste Daroussin wrote:
> On Thu 27 Jun 05:29, David Wolfskill wrote:
> > ...
> > But my secondary laptop choked on ncurses while running
> > main-n270474-d2f1f71ec8c6, first after updating sources to
> > main-n270948-8521ea135f5b, then after the update
I normally track FreeBSD daily, but was away from home for the first
coule of weeks of June, and am trying to get back into my usual update
cadence.
My (headless) build machine had no trouble updating:
main-n270474-d2f1f71ec8c6 (30 May) -> main-n270948-8521ea135f5b (25 June)
Hi,
Since a couple of weeks I'm start seeing random USB detach for all my
devices once in a while.
The issue doesn't occurs so often and there is no other details in the
var log. I'm able to recover all my devices by just unplugging and
re-plug the devices.
I'm running 15.0-CURRENT
On Mon, Jun 24, 2024 at 01:00:05AM -0700, Gleb Smirnoff wrote:
T> This is an automated email to inform you that the June 2024 stabilization
week
T> started with FreeBSD/main at main-n270917-5dbf886104b4, which was tagged as
T> main-stabweek-2024-Jun.
The 5dbf886104b4 aka main-stabweek-2024-Jun
Hi FreeBSD/main users & developers:
This is an automated email to inform you that the June 2024 stabilization week
started with FreeBSD/main at main-n270917-5dbf886104b4, which was tagged as
main-stabweek-2024-Jun.
The tag main-stabweek-2024-Jun has been published at
Dear FreeBSD Community,
The deadline for the next FreeBSD Status Report update is
June, 30th 2024 for work done since the last round of quarterly reports:
April 2024 - June 2024.
I would like to remind you that reports are published on a quarterly
basis and are usually collected during the last
On 6/22/24 08:19, Warner Losh wrote:
The last core team announced one.
But you can add Approved by: imp
Thanks Warner! I've just committed the change.
Have a nice week-end,
Best regards,
--
Ganael LAPLANCHE
http://www.martymac.org | http://contribs.martymac.org
FreeBSD: martymac ,
The last core team announced one.
But you can add Approved by: imp
Warner
On Sat, Jun 22, 2024, 12:16 AM Ganael Laplanche <
ganael.laplan...@martymac.org> wrote:
>
>
> On 6/21/24 23:41, Yuri Pankov wrote:
>
> > .mailmap
>
> Thanks Yuri!
>
> I cannot see any blanket approval for a ports
On 6/21/24 23:41, Yuri Pankov wrote:
.mailmap
Thanks Yuri!
I cannot see any blanket approval for a ports committer modifying that
file within the src repo.
Can a src committer approve (or commit) the following change please ? :
diff --git a/.mailmap b/.mailmap
index
Ganael Laplanche wrote:
>
>
> Le 21/06/2024 à 18:58, Warner Losh a écrit :
>
>> My apologies... I didn't check, but. it's in your sig so I should
>> have.
>
> Hey, no pb :)
>
>> There's a mapping file that can be updated for cases like this.
>
> Hmmm, I could add my address there. Can you
Le 21/06/2024 à 18:58, Warner Losh a écrit :
My apologies... I didn't check, but. it's in your sig so I should have.
Hey, no pb :)
There's a mapping file that can be updated for cases like this.
Hmmm, I could add my address there. Can you point me to that file, I
can't find it in
On Fri, Jun 21, 2024 at 10:55 AM Ganael Laplanche <
ganael.laplan...@martymac.org> wrote:
> On 6/21/24 18:44, Warner Losh wrote:
>
> Hi Warner,
>
> > Fixed.
> >
> > commit 681fd2bed8eaba88693867ba928a1c03a5b152cc (HEAD -> main)
> > Author: Ganael Laplanche
> Thanks!
>
> > Wrote the commit
On 6/21/24 18:44, Warner Losh wrote:
Hi Warner,
Fixed.
>
commit 681fd2bed8eaba88693867ba928a1c03a5b152cc (HEAD -> main)
Author: Ganael Laplanche
Thanks!
Wrote the commit message and had to guess at the right email to use. But
it looked like bz and the mail here were the same.
You could
Fixed.
commit 681fd2bed8eaba88693867ba928a1c03a5b152cc (HEAD -> main)
Author: Ganael Laplanche
Date: Fri Jun 21 10:39:09 2024 -0600
pax: Terminate loop for empty directory names
..
Wrote the commit message and had to guess at the right email to use. But it
looked like bz and the mail
On Fri 21 Jun 15:23, Shawn Webb wrote:
> Hey all,
>
> With the recent changes to ncurses in base, I'm getting a bunch of
> messages (snippet below) on every single new PTY. Every time I open a
> new window in tmux or login via ssh, I'm getting spammed with a flood
> of messages like below.
>
>
Hey all,
With the recent changes to ncurses in base, I'm getting a bunch of
messages (snippet below) on every single new PTY. Every time I open a
new window in tmux or login via ssh, I'm getting spammed with a flood
of messages like below.
BEGIN LOG
Name collision 'tvi950-b' between
Hello,
Our pax(1) implementation has a small bug triggered when it is fed with
a directory containing a trailing slash.
Could a src committer have a look at:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277060
?
I've submitted a small patch that fixes the problem.
Thanks!
Cheers,
On Wed, Jun 19, 2024 at 06:34:24PM +0100, David Chisnall wrote:
> Hi all,
>
> I have some code using libzfs_core that works fine on 13, but seems not to on
> 15-CURRENT. The lzc_snapshot function is failing with exactly the same nv
> list argument. It is failing with errno 2 (ENOENT) from the
Hi all,
I have some code using libzfs_core that works fine on 13, but seems not to on
15-CURRENT. The lzc_snapshot function is failing with exactly the same nv list
argument. It is failing with errno 2 (ENOENT) from the ZFS ioctl (and not
returning an nvlist of errors).
My understanding is
I filed an issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279853
to take over maintainer for security/globalprotect-openconnect
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
1 - 100 of 138427 matches
Mail list logo
