This is after having upgraded to and booted into (long output
line manually split for readability):
# uname -apKU
FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #65
main-n259064-f83db6441a2f-dirty: Sun Nov 6 17:08:00 PST 2022
The upgrade was to (long output line manually split for readability):
# uname -apKU
FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #65
main-n259064-f83db6441a2f-dirty: Sun Nov 6 17:08:00 PST 2022
etcupdate
=
On 06/11/2022 17:35, George Michaelson wrote:
I am probably alone in this
You're not alone.
… I find the …
markers in the update diffs intensely confusing.
diff3 bracketing.
<<< is where a conflict begins,
>>> is where it ends.
Beyond that, it was
On 29/10/2022 21:30, Graham Perrin wrote:
Subject: poudriere jail update from source: syscall.mk does not exist
After updating to yesterday's
aba921bd9e1869dae9ae4cc6e0c048f997401034, I aimed for a routine update
of the jail that I used for poudriere.
poudriere jail -u -J 1 -j main
…
On 6 Nov 2022, at 16:47, Alexander Motin wrote:
> Hi Louis,
>
> You should not try to disable ACPI these days. It was a recommendation in
> some cases probably ~15 years ago, but for many years now modern systems
> depend on ACPI for proper operation. I have no idea what causes crash in
>
Hi Louis,
You should not try to disable ACPI these days. It was a recommendation
in some cases probably ~15 years ago, but for many years now modern
systems depend on ACPI for proper operation. I have no idea what causes
crash in your case, but I would not expect it to end up good any way.
Chris,
On Fri, Nov 04, 2022 at 10:35:17AM -0700, Chris wrote:
C> > the reason I want to retire it is not that it consumes 40 Kb
C> > in the repository. The reason is that knows kernel structures,
C> > and fails to compile after changes to them. So the tool that
C> > nobody uses requires
I am probably alone in this but I find the CVS style
markers in the update diffs intensely confusing. Given many merges are
large blocks, its almost impossible to keep context flitting about in
vi to find the old/new insertions. The odd thing is that post edit,
the view you get afterward
On Nov 6, 2022, at 9:20 AM,
wrote:
> I try to get FreeBSD14 current running with both
> - GNOME
> - SAMBA
> That seems to be impossible ☹ GNOME and SAMBA416 seems to be conflicting !
> I need SAMBA416 since SAMBA413 is simply not working :(
>
> Installing SAMBA does remove GNOME components
I try to get FreeBSD14 current running with both
- GNOME
- SAMBA
That seems to be impossible ☹ GNOME and SAMBA416 seems to be conflicting !
I need SAMBA416 since SAMBA413 is simply not working :(
�
Installing SAMBA does remove GNOME components and vice versa.
�
How to work around this
I need to disable acpi and the indicated method for that is to add
^hint.acpi.0.disabled="1"^ in /boot/loader.conf .
However that crashes my system !!
Not only that, to make it work again I have to edit loader.conf on a system
which does ^not start^.
�
After a lot of searching
And the only commit after main-n259061-b1258b76435 so far is
004bb636ca65f3239da284c20abb7f9d1d953dee, which claims:
| tcp: Move sysctl OIDs related to ECN to tcp_ecn.
| Keep all ECN related code in (mostly) one place.
|
| No functional change.
I'm seeing:
...
building shared library
On Sat, 5 Nov 2022 20:12:04 -0700
bob prohaska wrote:
> On Mon, Oct 24, 2022 at 08:32:17PM -0700, Mark Millard wrote:
> >
> > Your /etc/rc.d/ldconfig script seems to have not been updated
> > by use of etcupdate or mergemaster or other such. (How much
> > else is also out of date? How much of
bob prohaska wrote on
Date: Sun, 06 Nov 2022 03:12:04 UTC :
> On Mon, Oct 24, 2022 at 08:32:17PM -0700, Mark Millard wrote:
> >
> > Your /etc/rc.d/ldconfig script seems to have not been updated
> > by use of etcupdate or mergemaster or other such. (How much
> > else is also out of date? How
14 matches
Mail list logo
