Am Wed, 11 Dec 2024 14:25:02 +0100
Ronald Klop schrieb:
> Op 09-12-2024 om 19:24 schreef Juraj Lutter:
> >
> >
> >> On 9 Dec 2024, at 19:19, FreeBSD User wrote:
> >>
> >> Am Tue, 10 Dec 2024 02:27:10 +0900
> >> Tomoaki AOKI schrieb:
> &
Am Mon, 9 Dec 2024 21:43:14 +0900
Tomoaki AOKI schrieb:
> On Mon, 9 Dec 2024 11:09:14 +0100
> Juraj Lutter wrote:
>
> > > On 8 Dec 2024, at 20:30, Ronald Klop wrote:
> > >
> > > Hi,
> > >
> > > I can reproduce your error.
> > >
> > > A cronjob which does a scp to another server didn't work
c/sysctl.conf.local ]
security.mac.bsdextended.enabled=0
security.mac.mls.enabled=0
security.mac.portacl.enabled=0
security.mac.do.enabled=0
security.mac.ipacl.ipv6=0
security.mac.ipacl.ipv4=0
#
net.bpf.optimize_writers=1
#
net.inet.ip.fw.verbose=1
#net.inet.ip.fw.verbose_limit=10
net.inet.ip.fw.
On Thu, 5 Dec 2024 16:55:00 +0100
Daniel Tameling wrote:
> On Thu, Dec 05, 2024 at 11:51:03AM +0100, FreeBSD User wrote:
> > On Wed, 04 Dec 2024 17:20:39 +
> > "Dave Cottlehuber" wrote:
> >
> > Thank you very much for responding!
> >
>
On Wed, 04 Dec 2024 17:20:39 +
"Dave Cottlehuber" wrote:
Thank you very much for responding!
> On Tue, 3 Dec 2024, at 19:46, FreeBSD User wrote:
> > On most recent CURRENT (on some boxes of ours, not all) fetch/git seem
> > to be stuck
> > forever fetchin
On most recent CURRENT (on some boxes of ours, not all) fetch/git seem to be
stuck
forever fetching tarballs from ports, fetching Emails via claws-mail (TLS),
opening
websites via librewolf and firefox or pulling repositories via git.
CURRENT: FreeBSD 15.0-CURRENT #1 main-n273978-b5a8abe9502e: M
Am Sat, 24 Aug 2024 15:21:16 -0600
Warner Losh schrieb:
> On Sat, Aug 24, 2024 at 1:39 PM Gordon Bergling wrote:
>
> > Hi Warner,
> >
> > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote:
> > > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote:
> > > > I got the following buil
Am Sat, 24 Aug 2024 15:21:16 -0600
Warner Losh schrieb:
> On Sat, Aug 24, 2024 at 1:39 PM Gordon Bergling wrote:
>
> > Hi Warner,
> >
> > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote:
> > > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote:
> > > > I got the following buil
Am Thu, 6 Jun 2024 10:39:33 GMT
Sumit Saxena schrieb:
> The branch main has been updated by ssaxena:
>
> URL:
> https://cgit.FreeBSD.org/src/commit/?id=8d3c3b52423f9740da424aa6dd73a20e694a9e08
>
> commit 8d3c3b52423f9740da424aa6dd73a20e694a9e08
> Author: Chandrakanth patil
> AuthorDate: 2
Am Tue, 04 Jun 2024 09:36:38 +0200
Alexander Leidinger schrieb:
> Am 2024-06-03 21:02, schrieb FreeBSD User:
> > Hello,
> >
> > I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running
> > several jails. Jails are
> > attached to a bridge de
Hello,
I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running several
jails. Jails are
attached to a bridge device (bridge1), the physical device on that bridge is
igb1 (i350 based
NIC). The bridge is created via host's rc scripts, adding and/or deleting epair
members of the
brid
Hello,
for customising my world and kernel, I try to "overlay" GENERIC via included
files containing
"nodevice" and "nooptions" tags starting from a top level config file like
include GENERIC
include NODEVICE-GENERIC
include SPECIAL
Within "NODEVICE-GENERIC" I utilize
[...]
# Debugging support.
Am Sun, 26 May 2024 09:29:08 +0200
Bojan Novković schrieb:
> Hi,
>
> da76d349b6b1 replaced a UMA-related symbol but missed three instances
> where the old one was used, ultimately causing the wrong UMA page
> allocator to get selected and crashing the machine.
>
> I tested this patch as a par
Am Sun, 26 May 2024 14:45:37 +0200
"Herbert J. Skuhra" schrieb:
> On Sun, May 26, 2024 at 02:35:16PM +0200, FreeBSD User wrote:
> > Hello,
> >
> > boxes running CURRENT are last good with FreeBSD 15.0-CURRENT #44
> > main-n270400-02d15215cef2: Sat May 25
Am Sat, 27 Apr 2024 11:28:55 +0200
FreeBSD User schrieb:
Just for the record: running a small "victim NAS" based on an HP EliteDesk 800
G2 mini,
XigmaNAS (latest official version, kernel see below), installing packages from
an official
FreeBSD site for FBSD 13.2-RELEASE, gives me o
Am Thu, 25 Apr 2024 21:51:21 +0200
Tomek CEDRO schrieb:
> CP2102 are pretty good ones and never let me down :-)
>
> Is your UART connection to ESP32 working correctly? Can you see the
> boot message and whatever happens next in terminal (cu / minicom)? Are
> RX TX pins not swapped? Power supply
Hello,
Host: 15.0-CURRENT FreeBSD 15.0-CURRENT #36 main-n269703-54c3aa02e926: Thu Apr
25 18:48:56
CEST 2024 amd64 or 14-STABLE recently compiled (dmesg/uname not at hand).
Hardware: oldish Z77Pro 4 based Asrock mainboard, a Lenovo T560 notebook,
Fujitsu Esprimo Q5XX
(simple desktop, Pentium Gol
Am Tue, 9 Apr 2024 09:18:49 -0700
Gleb Smirnoff schrieb:
> On Tue, Apr 09, 2024 at 04:47:07AM -0700, David Wolfskill wrote:
> D> --- trap 0xc, rip = 0x80b208c5, rsp = 0xfe048c204920, rbp =
> 0xfe
> D> 048c204960 ---
> D> __mtx_lock_flags() at __mtx_lock_flags+0x45/frame 0xfe0
Am Tue, 9 Apr 2024 17:10:52 +0200
Rainer Hurling schrieb:
> Am 09.04.24 um 09:20 schrieb Baptiste Daroussin:
> > On Sat 06 Apr 09:23, Rainer Hurling wrote:
> >> Am 06.04.24 um 09:05 schrieb FreeBSD User:
> >>> Hello,
> >>>
> >>> afte
Am Sat, 6 Apr 2024 09:05:00 +0200
FreeBSD User schrieb:
> Hello,
>
> after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0
> on CURRENT and
> 14-STABLE, I can't update several ports:
>
> www/apache24
> databases/redis
>
> pkg co
Am Thu, 4 Apr 2024 01:14:52 -0500
Kyle Evans schrieb:
> On 4/4/24 00:49, FreeBSD User wrote:
> > Hello,
> >
> > I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1:
> >
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094
> >
> >
Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0
on CURRENT and
14-STABLE, I can't update several ports:
www/apache24
databases/redis
pkg core dumps while performing installation. apache24 and redis are ports I
realized this
misbehaviour on ALL 14-STABLE and
Am Thu, 04 Apr 2024 08:06:26 +0200 (CEST)
sth...@nethelp.no schrieb:
> >> I have to report to my superiors (we're using 14-STABLE and CURRENT
> >> and I do so in private),
> >> so I would like to welcome any comment on that.
> >
> > No it does not affect FreeBSD.
> >
> > The autoconf script ch
x0, limit 0xf, type 0x1b
> >>> = DPL 0, pres 1, long 1, def32 0, gran 1
> >>> processor eflags = interrupt enabled, resume, IOPL = 0
> >>> current process = 6869 (csh)
> >>> trap number = 12
> >>> panic: page fault
> >>> cpuid = 2
&g
b7e
> > #7 0x804b9d90 at nfs_readdir+0x1f0
> > #8 0x8069c61a at vop_sigdefer+0x2a
> > #9 0x809f8ae0 at VOP_READDIR_APV+0x20
> > #10 0x81ce75de at autofs_readdir+0x2ce
> > #11 0x809f8ae0 at VOP_READDIR_APV+0x20
> > #12 0
Am Sun, 14 Jan 2024 20:34:12 -0800
Cy Schubert schrieb:
> In message om>
> , Rick Macklem writes:
> > On Sat, Jan 13, 2024 at 12:39=E2=80=AFPM Ronald Klop =
> > wrote:
> > >
> > >
> > > Van: FreeBSD User
> > > Datum: 13 januari 2024
Am Mon, 8 Jan 2024 01:33:53 +0100 (CET)
Felix Reichenberger schrieb:
> > Hello,
> >
> > I've got a problem with recent CURRENT, running vnet JAILs.
> > FreeBSD 15.0-CURRENT #28 main-n267432-e5b33e6eef7: Sun Jan 7 13:18:15 CET
> > 2024 amd64
> >
> > Main Host has IPFW configured and is open for
Am Sat, 13 Jan 2024 19:41:30 -0800
Rick Macklem schrieb:
> On Sat, Jan 13, 2024 at 12:39 PM Ronald Klop wrote:
> >
> >
> > Van: FreeBSD User
> > Datum: 13 januari 2024 19:34
> > Aan: FreeBSD CURRENT
> > Onderwerp: NFSv4 crash of CURRENT
> >
>
Hello,
I've got a problem with recent CURRENT, running vnet JAILs.
FreeBSD 15.0-CURRENT #28 main-n267432-e5b33e6eef7: Sun Jan 7 13:18:15 CET 2024
amd64
Main Host has IPFW configured and is open for services like OpenLDAP on UDP/TCP
and ICMP
(ipfw is configured via rc.conf in this case, host is
Am Thu, 23 Nov 2023 20:37:26 +0100
FreeBSD User schrieb:
> Hello,
>
> I'm facing some strange behaviour when connecting to a CP2102 USB-UART bridge
> built-in into
> a I2C-USB device (I2C is handled by an Amtel88, USB-UART is handled by an
> CP2102, see here:
>
&
Hello,
at first: observation is below, marked [OBSERVATION].
Running recent CURRENT (FreeBSD 15.0-CURRENT #26 main-n265831-3523f0677ef: Mon
Oct 9 14:00:42
CEST 2023 amd64), I've configured a bridge (bridge0), the hosts's interface
igb0 (I350-T2 two
port Gigabit Network Connection ) is member o
ere.
>
> Anyway, I will keep updating this branch until it's ready for a pull-up
> request, very likely with force-pushes in order to polish the commits
> before submission.
>
> Let me know how it goes!
>
> Cheers,
> -- Pierre
>
> On 6/29/23 23:56, Dustin
Am Thu, 29 Jun 2023 16:41:51 +0200
Guido Falsi schrieb:
> On 29/06/23 16:35, FreeBSD User wrote:
> > Hello,
> >
> > running a recent CURRENT, 14.0-CURRENT #10 main-n263871-fd774e065c5d: Thu
> > Jun 29 05:26:55
> > CEST 2023 amd64, xfreerdp (net/freerdp) d
Hello,
running a recent CURRENT, 14.0-CURRENT #10 main-n263871-fd774e065c5d: Thu Jun
29 05:26:55 CEST
2023 amd64, xfreerdp (net/freerdp) doesn't working anymore on Windows 10 guest
in bhyve. It
seems OpenSSL 3 is the culprit (see the error message from xfreerdp below). I
opened already a
PR (se
Am Wed, 31 May 2023 12:15:12 -0600
Warner Losh schrieb:
Sorry for the late response.
> On Mon, May 29, 2023 at 2:59 AM FreeBSD User wrote:
>
> > Hello,
> >
> > on CURRENT, enabling in /etc/src.conf
> >
> > WITH_BEARSSL=
> >
> > seems to re
Am Sat, 15 Apr 2023 07:36:25 -0700
Cy Schubert schrieb:
> In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>,
> FreeBSD Us
> er writes:
> > Am Thu, 13 Apr 2023 22:18:04 -0700
> > Mark Millard schrieb:
> >
> > > On Apr 13, 2023, at 21:44, Charlie Li wrote:
> > >
> > > > Ma
Am Thu, 13 Apr 2023 22:18:04 -0700
Mark Millard schrieb:
> On Apr 13, 2023, at 21:44, Charlie Li wrote:
>
> > Mark Millard wrote:
> >> FYI: in my original report for a context that has never had
> >> block_cloning enabled, I reported BOTH missing files and
> >> file content corruption in the
Am Sun, 9 Apr 2023 14:37:03 +0200
Mateusz Guzik schrieb:
> On 4/9/23, FreeBSD User wrote:
> > Today, after upgrading to FreeBSD 14.0-CURRENT #8 main-n262052-0d4038e3012b:
> > Sun Apr 9
> > 12:01:02 CEST 2023 amd64, AND upgrading ZPOOLs via
> >
> > zpool up
Am Thu, 30 Mar 2023 17:27:31 +0200
Dag-Erling Smørgrav schrieb:
> FreeBSD User writes:
> > I tried to put the option
> >
> > WITHOUT_MODULE="an"
>
> it's spelled WITHOUT_MODULES, cf. make.conf(5).
>
> DES
Correct, and so I use it ... ;-)
Am Thu, 30 Mar 2023 15:53:19 +0200
Mateusz Guzik schrieb:
> On 3/30/23, FreeBSD User wrote:
> > Hello folks,
> >
> > some strange misbehaviour in a NanoBSD compilation is driving me nuts.
> > Recently I posted some
> > error messages regarding
> >
> &g
Am Thu, 30 Mar 2023 16:56:09 +0200
Mateusz Guzik schrieb:
> On 3/30/23, Mateusz Guzik wrote:
> > On 3/30/23, FreeBSD User wrote:
> >> Hello folks,
> >>
> >> some strange misbehaviour in a NanoBSD compilation is driving me nuts.
> >> Recentl
Hello folks,
some strange misbehaviour in a NanoBSD compilation is driving me nuts. Recently
I posted some
error messages regarding
[...]
src/sys/dev/an/if_an_pci.c:143:1: error: a
function definition without a prototype is deprecated in all versions of C and
is not
supported in C2x [-Werror,-
Am Wed, 8 Mar 2023 12:13:49 +0100
tue...@freebsd.org schrieb:
> > On 8. Mar 2023, at 11:42, FreeBSD User wrote:
> >
> > Am Wed, 8 Mar 2023 11:28:11 +0100
> > Dimitry Andric schrieb:
> >
> >> On 8 Mar 2023, at 11:19, FreeBSD User wrote:
> >>
Am Wed, 8 Mar 2023 11:28:11 +0100
Dimitry Andric schrieb:
> On 8 Mar 2023, at 11:19, FreeBSD User wrote:
> ...
> > But I don't understand why the make environment is trying to compile a
> > piece of code that
> > is disabled via "nodevice&quo
Am Thu, 2 Mar 2023 11:13:51 +0100
Dimitry Andric schrieb:
> On 2 Mar 2023, at 06:41, FreeBSD User wrote:
> >
> > Am Mon, 27 Feb 2023 23:46:21 +0100
> > Dimitry Andric schrieb:
> ...
> >
> > I tried to find some documentation on my CURRENT host r
Am Thu, 2 Mar 2023 11:13:51 +0100
Dimitry Andric schrieb:
> On 2 Mar 2023, at 06:41, FreeBSD User wrote:
> >
> > Am Mon, 27 Feb 2023 23:46:21 +0100
> > Dimitry Andric schrieb:
> ...
> >
> > I tried to find some documentation on my CURRENT host r
Am Mon, 27 Feb 2023 23:46:21 +0100
Dimitry Andric schrieb:
> On 27 Feb 2023, at 22:23, Paul Mather wrote:
> >
> > On Feb 27, 2023, at 2:57 PM, Dimitry Andric wrote:
> >
> >> On 27 Feb 2023, at 19:19, FreeBSD User wrote:
> >>>
> >>>
Am Mon, 27 Feb 2023 20:57:19 +0100
Dimitry Andric schrieb:
> On 27 Feb 2023, at 19:19, FreeBSD User wrote:
> >
> > Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23
> > main-n261147-b8bb73ab724b: Sun
> > Feb 26 17:39:38 CET 2023 amd64), and nanoBSD (recent 13
Hallo everybody,
a week ago I compiled a new 13-STABLE (FreeBSD 13.2-STABLE #77
stable/13-n254681-44a6088278ea:
Sat Feb 25 07:44:36 CET 2023 amd64, custom kernel, same happens with the recent
regular
GENERIC kernel). ZFS root installation.
Graphics driver:
drm-510-kmod-5.10.163_2graphic
g as I finish my work. The I hope I can provide
you with a
backtrace. cpu-data has been updated recently, I use this on these two
IvyBridge methusalem
riggs, I may disable this first and see what happens ...
Regards
oh
>
> rick
>
> On Sun, Feb 19, 2023 at 1:38 AM FreeBSD User wrote
Am Sun, 19 Feb 2023 13:30:13 +0300
"Andrey V. Elsukov" schrieb:
> 18.02.2023 18:42, FreeBSD User пишет:
> > On a 24 hour basis, the ISP changes the IPv4 and IPv6 on the WAN
> > interface. We use NPTv6 to translate ULA addresses for the inner
> > IPv6 networks.
Hello,
most recent CURRENT crashes on shutdown from multiuser mode (singleuser mode,
used after
repairing failed FFS filesystems, is all right). The crashes go on since
roughly a 1/2 week
from now. The boxes involved are all cumtomized kernels (in most cases hard
linked modules
into kernel). Is
Hello,
running a small nanoBSD firewall/router appliance, the WAN interface (tun0) is
confugred via
SLAAC when it comes to IPv6. The allpliance is running in-kernel compiled IPFW.
The OS is
FreeBSD 13-STABLE, compiled on a recuurant weekly basis.
On a 24 hour basis, the ISP changes the IPv4 and
Hello,
well, the aim of my post sounds strange, but I'm serious.
Background: I run at home a 14-CURRENT based server with a ZFS volume (RAIDZ)
comprised from
4x 4 TB HDD. A couple of days I had to exchange the HGST NAS drives since one
got a permanent
SMART error. So all HDDs have been replaced
Hello folks,
I ran today into a problem, that the reolveer option "edns0" isn't documented
(as well as some
others). Searching the net reveals, that there is a PR open with exactly that
issue since
January 2016, since then, code has changed I presume.
Could someone please take care of that issu
Am Sun, 28 Aug 2022 06:11:20 -0700
Cy Schubert schrieb:
> In message <20220828130107.1a76d54a.gre...@freebsd.org>, Michael Gmelin
> writes:
> >
> >
> >
> > On Sun, 28 Aug 2022 03:21:24 -0700
> > Cy Schubert wrote:
> >
> > > In message <16b4-76a1-4e46-b7c3-60492d379...@freebsd.org>,
> > >
Am Sat, 27 Aug 2022 13:16:43 +0200
tue...@freebsd.org schrieb:
> > On 27. Aug 2022, at 08:30, FreeBSD User wrote:
> >
> > Hello,
> >
> > I'm referencing to Bug 259699 [2] and Bug 259585 [1].
> >
> > Port security/clamav is without doubt for m
Am Sat, 27 Aug 2022 11:21:40 +0200
Michael Gmelin schrieb:
> > On 27. Aug 2022, at 08:31, FreeBSD User wrote:
> >
> > Hello,
> >
> > I'm referencing to Bug 259699 [2] and Bug 259585 [1].
> >
> > Port security/clamav is without doubt for m
Hello,
I'm referencing to Bug 259699 [2] and Bug 259585 [1].
Port security/clamav is without doubt for many of FreeBSD users an important
piece of security
software so I assume a widespread usage.
It is also a not uncommon use case to use NanoBSD or any kind of
low-memory-footprint
installatio
Hello,
I'm running a FreeBSD 13.1-RELENG-p1 zroot-based guest in a VirtualBox
4.1.24/26 (do not know
exactly). The host is a special system based on Linux und VirtualBox and I have
no chances to
configure the VBox.
Somehow the VBox crashed and hung up the complete computer, so I had to cold
st
Am Sun, 3 Jul 2022 11:57:33 +0200
FreeBSD User schrieb:
Sorry for the noise, the learning process is still in progress and I learned
about the
until-now-not-fully-understood V4: entry in /etc/exports.
Thanks for reading and patience.
regards,
oh
> Hello folks,
>
>
> Trying to
Hello folks,
Trying to mount a NFS filesystem offered by a FreeBSD 12.3-p5 (XigmaNAS) from a
recent CURRENT
(FreeBSD 14.0-CURRENT #19 main-n256512-ef86876b846: Sat Jul 2 23:31:53 CEST
2022 amd64) via
:/etc # mount -t nfs -o vers=4 192.168.0.11:/mnt/NAS00/home /tmp/mnt
results in
mount_nfs:
Hello,
the problem I'm about to report is not specific to CURRENT, I report this to
CURRENT
because I'm list member. The problem occurs on FreeBSD 12.3-RELEASE-p5.
Setup: connecting to vnet jails bound to a dedicated NIC via if_bridge results
in an
erratic behaviour (from my point of view). The
On Thu, 28 Apr 2022 13:36:21 -0600
Alan Somers wrote:
> On Thu, Apr 28, 2022 at 1:29 PM Marek Zarychta
> wrote:
> >
> > W dniu 28.04.2022 o 21:21, FreeBSD User pisze:
> > > Running XigmaNAS 12.3.0.4.9009 on amd64 hardware, we try to mount HDD to
> > > res
Running XigmaNAS 12.3.0.4.9009 on amd64 hardware, we try to mount HDD to rescue
them and
store the data on ZFS volumes. Mounting of the HDD doesn't work, FreeBSD 12.3
obviously
lack in some etx2 features, namely "needs_recovery". The kernel reports:
WARNING: mount of da4p3 denied due to unsuppor
and install phases.
This is now working on the above reported builder host version. The key was,
indeed, setting WITHOUT_PROFILE=t. Thank you for the hint.
On CURRENT I can build both, 13.0-RELENG and 13.1-RELENG without issues.
Kind regards,
Oliver Hartmann
>
>
> On Tue, Apr 19, 2022
On Fri, 1 Apr 2022 12:09:21 -0400
Ed Maste wrote:
> On Fri, 1 Apr 2022 at 12:04, FreeBSD User wrote:
> >
> > I tried the patch given at the URL above (Phabricator). Patch applied on
> > recent CURRENT and trying to "make installworld" leaves me with this error
I regular build for a NanoBSD appliance 13-STABLE, 13.0-RELENG and 13.1-RELENG
on either 14-CURRENT and 13-STABLE. Several days ago, some changes has been
made to /usr/src/Makefile.inc1, first on CURRENT and shortly after on 13.
As with today, building from sources either 13.1-RELENG and 13.0-RELE
Hello fellows, happy Easter!
I run into a security issue this morning here and tried to look for a solution.
We use
OpenLDAP for all "regular users" login on hosts and web services.
Authentication is
required from some cloud/moodle services via LDAP, but some users not having any
homedirectory o
Am Fri, 1 Apr 2022 10:08:11 -0400
Ed Maste schrieb:
> On Fri, 1 Apr 2022 at 10:00, Jens Schweikhardt
> wrote:
> >
> > Hello *,
> > Looks like a semicolon is missing after the "fi".
>
> Indeed, and there was a close bracket missing as well. I've put a
> (hopefully) fixed version in review at
>
Am Fri, 1 Apr 2022 16:00:10 +0200 (CEST)
Jens Schweikhardt schrieb:
> Hello *,
> Looks like a semicolon is missing after the "fi".
> Jens
>
> - Ursprüngliche Mail -
> Von: "Ed Maste"
> An: "FreeBSD User"
> CC: "freebsd-curr
On 14.0-CURRENT #134 main-n253938-4ef6e56ae80: Thu Mar 24 16:11:07 CET 2022
amd64, it is without any problem possible to build most recent 13-STABLE
sources as of today (stable/13-n250195-26e8bb3a4e1).
On 14.0-CURRENT #18 main-n254160-4fc5a607fdf: Fri Apr 1 08:30:10 CEST 2022
amd64 this is not po
On Mon, 28 Feb 2022 17:11:27 +0100
Michael Gmelin wrote:
[...]
schnipp
[...]
> >
> > poudriere jail -l:
> >
> > # poudriere jail -l
> > JAILNAME VERSION ARCH METHOD TIMESTAMP PATH
> > 123-amd64 12.3-RELEASE amd64
> > url=https://download.freebsd.org/releases/a ... 3-RELEASE/ 2022-02-24
> > 14:1
Hello folks,
we run at least two poudriere build systems on recent CURRENT boxes and one of
these
poudriere build systems is working within a jail - setup via FreeBSD's
/etc/jail.conf and
by misusing the port ezjail for copying/deploying our self-compiled jail
binary. The
poudriere jail uses ZF
With mergin a recent commit today involving /usr/src/sys/x86/x86/tsc.c of
FreeBSD
13-STABLE, compiling the kernel results in the error shown below:
[...]
cc -target x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -shared -O3 -pipe
On Wed, 29 Dec 2021 09:10:02 +0200
Daniel Braniss wrote:
> > On 29 Dec 2021, at 01:25, FreeBSD User wrote:
> >
> > On Mon, 20 Dec 2021 14:35:10 +0100
> > Marc Fonvieille mailto:black...@freebsd.org>> wrote:
> >
> >> Le 19.12.2021 21:03, Andrew St
On Mon, 20 Dec 2021 14:35:10 +0100
Marc Fonvieille wrote:
> Le 19.12.2021 21:03, Andrew Stevenson a écrit :
> >
> >
> > > On 19. Dec 2021, at 12:18, FreeBSD User wrote:
> > >
> > > environment. Since I'm interested in coding for some smalle
Am Mon, 20 Dec 2021 14:35:10 +0100
schrieb Marc Fonvieille :
> Le 19.12.2021 21:03, Andrew Stevenson a écrit :
> >
> >
> > > On 19. Dec 2021, at 12:18, FreeBSD User
> > > wrote:
> > >
> > > environment. Since I'm interested in coding
Hello out there,
I'm using the port devel/arduino18 as the basis for some small projects. I'd
like to get
rid of that clumsy JAVA based IDF and move towards a more make/automake based
environment. Since I'm interested in coding for some smaller AMTEL MCUs and
ESP32 and
like to digg a bit deeper
On Mon, 13 Dec 2021 09:30:50 +0200
Andriy Gapon wrote:
> On 12/12/2021 18:45, Alan Somers wrote:
> > You need to look at what's causing those errors. What kind of disks
> > are you using, with what HBA? It's not surprising that any access to
> > ZFS hangs; that's what it's designed to do when a
On Fri, 10 Dec 2021 19:41:07 +1030
Daniel O'Connor via freebsd-current wrote:
> > On 25 Nov 2021, at 18:50, FreeBSD User wrote:
> >
> > Running CURRENT (FreeBSD 14.0-CURRENT #7 main-n250911-a11983366ea7: Mon Nov
> > 22
> > 18:17:54 CET 2021 amd64) trou
Running CURRENT (FreeBSD 14.0-CURRENT #52 main-n251260-156fbc64857: Thu
Dec 2 14:45:55 CET 2021 amd64), out of the sudden the ZFS RAIDZ pool
suffered from an error:
Solaris: WARNING: Pool 'POOL00' has encountered an uncorrectable I/O
failure and has been suspended.
The system does not repsond a
Am Wed, 8 Dec 2021 10:43:41 -0500
schrieb Mark Johnston :
> On Wed, Dec 08, 2021 at 04:05:16PM +0100, FreeBSD User wrote:
> > Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD
> > 14.0-CURRENT #7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET
> > 2021
Building recent 13-STABLE sources on a recent 14-CURRENT (FreeBSD 14.0-CURRENT
#7 main-n251463-935dc0de881: Wed Dec 8 06:49:25 CET 2021 amd64) fails with the
linker error shown below.
Due to this error, no FreeBSD pkg base nor NanoBSD Image can be build.
[...]
cc -O2 -pipe -O3 -fno-common
-I/po
Running CURRENT (FreeBSD 14.0-CURRENT #7 main-n250911-a11983366ea7: Mon Nov 22
18:17:54
CET 2021 amd64) troubles me with our DNS server/service.
Aproximately the same time we switched on CURRENT to the CURRENT LLVM13 version
and also,
after the compilation of a fresh OS with LLVM13, the upgrade f
On Fri, 15 Oct 2021 23:25:01 +0300
Konstantin Belousov wrote:
> On Fri, Oct 15, 2021 at 10:20:55PM +0200, Jan Beich wrote:
> > FreeBSD User writes:
> >
> > > After updating 13-STABLE to 13.0-STABLE #3 stable/13-n247671-70db230dcbd:
> > > Thu Oct 14
> >
After updating 13-STABLE to 13.0-STABLE #3 stable/13-n247671-70db230dcbd: Thu
Oct 14
20:48:53 CEST 2021 amd64 on a Lenovo E540 notebook with Intel iGPU and also
updating port
graphics/drm-fbsd13-kmod to drm-fbsd13-kmod-5.4.144.g20211013, graphics/libdrm
to
libdrm-2.4.107_1,1, Firefox (firefox-93
On Tue, 12 Oct 2021 10:01:00 -0600
Warner Losh wrote:
> On Tue, Oct 12, 2021 at 9:32 AM FreeBSD User wrote:
>
> > I do not know whether I'm right in this list, but since the subject is
> > mutual so common
> > in development and GIT, I have the strong feeling I&#
On Tue, 12 Oct 2021 18:01:56 +
Brooks Davis wrote:
> On Tue, Oct 12, 2021 at 05:31:48PM +0200, FreeBSD User wrote:
> > I'd like to ask how FreeBSD developers and maintainers do the trick. If
> > there is an official cookbook fpr maintainers (I haven't found it yet ..
I do not know whether I'm right in this list, but since the subject is mutual
so common
in development and GIT, I have the strong feeling I'm right here.
Im quite new to git, so apologizes for any inconvenience reading my question.
Using poudriere on 14-CURRENT to create a selection of packages
On recent CURRENT (FreeBSD 14.0-CURRENT #2 main-n249971-0525ece3554e:
Fri Oct 8 15:17:34 CEST 2021 amd64) building of an 13-STABLE based
appliance failed very early in the build process of the 13-STABLE
sources as shown below. 13-STABLE is most recent, since the sources are
fetched every time the
Hello,
I use FreeBSD-base packages built on self hosted systems to update 13-STABLE
and CURRENT hosts. I run into the problem, that the packages of the FreeBSD
base, built via the FreeBSD framework and from most recent 13-STABLE sources,
are often oit of synchronisation with our poudriere packagi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello list,
Trying to "crosscompile" a 13-STABLE appliance on 14-CURRENT ( FreeBSD
14.0-CURRENT #8
main-n249550-8db1669959ce: Wed Sep 22 05:39:53 CEST 2021 amd64) with
WITH_LLVM_BINUTILS=YES
set in /etc/src.conf (and a complete fresh rebuild of t
Am Fri, 10 Sep 2021 09:04:30 -0400
Ed Maste schrieb:
> On Fri, 10 Sept 2021 at 04:29, Gary Jennejohn wrote:
> >
> > Was the config.h in the patch the same as the one you committed?
>
> No it wasn't - USE_PAM was #defined in config.h after applying the
> patch, while the committed version acci
Am Thu, 9 Sep 2021 22:12:09 +0200
Philipp Ost schrieb:
> On 9/9/21 9:15 PM, FreeBSD User wrote:
> [...]
> > What has changed in the recent 14-CURRENT OpenSSH update that dramatically
> > that working
> > schematics do not work any more?
>
> OpenSSH has been
Hello,
after upgrading 14-CURRENT to recent sources September, the 8th 2021, we
realizes today a
strange non-standard behaviour when connecting attempts from several clients to
14-CURRENT
based machines were made involving sshd.
First discovered on 13-STABLE clients (NanoBSD, router/fw applianc
Am Wed, 11 Aug 2021 15:03:54 -0400
Ed Maste schrieb:
> On Wed, 11 Aug 2021 at 05:41, FreeBSD User wrote:
> >
> > Hallo,
> >
> > latest upgrade of CURRENT sources renders buildworld into failure, box is
> > running
> > FreeBSD 14.0-CURRENT #1 main-n24861
Hello,
enabling
WITH_BEARSSL
in src.conf renders buildworld on 13-STABLE to fail, but not on
14-CURRENT.
This is the difference between the sources, obviously 14-CURRENT contains the
correct
definition of SOPEN_MAX, while 13-STABLE not (undefinied SOPNE_MAX triggers the
compiler to
fail,
Running several flavours of CURRENT (all within the last three days rebuilt and
updated, FreeBSD 14.0-CURRENT #16 main-n248811-1a4d7030bbf: Thu Aug 19
15:13:39 CEST 2021 amd64, and today, for instance, fail either to build a
poudriere 13-STABLE jail or buildworld for 13-STABLE for FreeBSD base pa
Am Wed, 11 Aug 2021 15:03:54 -0400
Ed Maste schrieb:
> On Wed, 11 Aug 2021 at 05:41, FreeBSD User wrote:
> >
> > Hallo,
> >
> > latest upgrade of CURRENT sources renders buildworld into failure, box is
> > running
> > FreeBSD 14.0-CURRENT #1 main-n24861
1 - 100 of 104 matches
Mail list logo
