iterature on that subject (IPv6
routing), please share
with me.
Thanks for the patience and help in advance,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Mon, 28 Jun 2021 23:34:44 +0200
Michael Gmelin schrieb:
> > On 28. Jun 2021, at 22:41, O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> >
> > Hello,
> >
hint me to what to do track this nasty error?
Thanks in advance,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-
Hello out there.
I have a bunch of Fujitsu PRAID400i Controller from some servers we switch to
FreeBSD driven systems and ZFS. I will not use RAID controllers with ZFS so I
tried to cross flash these controllers, but without any success. The DOS tools
I use produce on several mainboards a PAL erro
piling, so if there is in general an issue
with this "brute
force method" I would appreciate any recommendation to avoid such malfunctions
using other
techniques - as long as they are moderate to implement.
Thanks in advance and kind regards,
O. Hartmann
[...]
- --- acpi_wakecode.o -
On Fri, 9 Apr 2021 12:59:59 +0200
Gary Jennejohn wrote:
> On Fri, 9 Apr 2021 12:12:45 +0200
> Guido Falsi via freebsd-current wrote:
>
> > On 09/04/21 11:56, O. Hartmann wrote:
> > > On Fri, 9 Apr 2021 10:16:27 +0200 (CEST)
> > > Ronald Klop wrote:
> >
n "stage/runaway" for 61 hours now.
> http://beefy18.nyi.freebsd.org/build.html?mastername=main-amd64-default&build=p569609_s5b3b19db73
> (ipv6 only)
>
> NB: I'm not involved in the pkg building cluster.
>
> Regards,
> Ronald.
>
>
> Van: "O. Hartman
BIOS 639kB/3405336kB available memory
FreeBSD/x86 bootstrap loader, Revision 1.1
(Mon Feb 22 18:17:30 CET 2021 root@thor)
|
VBE not available
... and its stuck forever ...
What is wrong here?
Thanks for your help,
kind regards
Oliver
- --
O. Hartmann
Ich widerspreche der Nutzung oder Über
> > ]+([^ ]+)[
> > ]+([^ ]+).*$/\1 \3 \4/' | sort | uniq -c 12 zroot active local
> > 21 zroot enabled local
> >
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd
fast_lookup=0
reverting the mentioned commit helped and made things working as expected again.
Thank you very much.
oh
>
> On 2/15/21, O. Hartmann wrote:
> > The base host is running FreeBSD 14.0-CURRENT #6 main-n244784-8563de2f279:
> > Fri
> > Feb 12 12:48:34 CET 2021 amd6
The base host is running FreeBSD 14.0-CURRENT #6 main-n244784-8563de2f279: Fri
Feb 12 12:48:34 CET 2021 amd64, the source tree is at "commit
5dce03847fdc7bc6eb959282c0ae2117b1991746".
Updating jails via "ezjail-admin update -i", or for poudriere based CURRENT
(14-CURRENT) jails via "poudriere jai
Just updated CURRENT to r367415 and loading linux kernel module(s) fail with
# kldload linux
link_elf_obj: symbol sdt_provider_linuxulator undefined
linker_load_file: /boot/kernel/linux_common.ko - unsupported file type
KLD linux.ko: depends on linux_common - not available or version mismatch
lin
On Thu, 10 Sep 2020 10:44:08 -0600
Alan Somers wrote:
> No, it's devfs. I'll fix it.
>
> On Thu, Sep 10, 2020 at 10:18 AM Ryan Stone wrote:
>
> > I'm curious: does this give a similar issue?
> >
> > touch /tmp/foo
> > cp /tmp/foo /tmo/foo2
> >
> > I'm wondering if the issue is that copy_file_ra
Begin forwarded message:
Date: Fri, 4 Sep 2020 14:06:12 +0200
From: "O. Hartmann"
To: Matthew Macy
Cc: freebsd-current , freebsd-fs
, freebsd-hack...@freebsd.org Subject: Re: OpenZFS
support merged: problem mounting ZFS within JAILs
On Mon, 24 Aug 2020 19:38:53 -0700
Matthew M
On Mon, 24 Aug 2020 19:38:53 -0700
Matthew Macy wrote:
> r364746 merged OpenZFS support in to HEAD.
>
> The change should be transparent unless you want to use new features.
> I caution against 'zpool upgrade' for the next few weeks.
>
> https://svnweb.freebsd.org/base?view=revision&revision=3647
On Tue, 1 Sep 2020 19:21:36 +0200
Mateusz Guzik wrote:
> It's not my bug but i'll make sure it is taken care of.
Oh, I'm sorry. But I grasp for every help I can get ...
The problem is that I do not know whether the process "make installkernel" does
silently proceed and drop the error message an
Running a most recent CURRENT (FreeBSD 13.0-CURRENT #1 r365325: Fri Sep 4
11:28:14 CEST 2020 amd64) with JAILS also running CURRENT of the very same
version, one specific jail which is designated to be a poudriere jail with ZFS
filesystems doesn't start after an update today.
The message is:
[..
On CURRENT 9not necessarily most recent with LLVM11, but since noon of today it
is FreeBSD 13.0-CURRENT #15 r364297: Mon Aug 17 14:39:06 CEST 2020 amd64) I'm
faced with some very sticky and nasty micompilations in several essential
ports, for instance
ports-mgmt/pkg
devel/libunwind
devel/binutils
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Fri, 3 Jul 2020 17:24:36 +0200
"O. Hartmann" schrieb:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello list,
>
> running some scripts caluclating via bc() the expression shown below:
>
> bc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello list,
running some scripts caluclating via bc() the expression shown below:
bc -e '6582031 - 1048576 - 0 - 409600 - 1024 - 40 - 4096' -e quit
results on recent CURRENT ( FreeBSD 13.0-CURRENT #80 r362884: Thu Jul 2
10:08:23 CEST 2020
amd64)
Due to the circumstance I have no access anymore to the host in question, I'll
report a problem occured out of the blue around last week's update of CURRENT
with poudriere and swapspace.
Problem: under heavy load, the host dies - no ssh connection possible anymore,
all jails are in the state "dead
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Sat, 25 Apr 2020 11:32:49 +0100
Alexander V. Chernikov schrieb:
> 25.04.2020, 11:18, "O. Hartmann" :
> > Hello,
> >
> > recent commits to CURRENT makes buildkernel to fail due to some incomplete
> > d
note: forward declaration of 'struct nhop_object'
struct nhop_object *ro_nh;
^
- --- all_subdir_sound ---
Kind regards,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Mein
rc.conf
or using own scripts containing "any" as keyword for either source or
destination to brick the system.
Kind regards,
O. Hartmann
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
t 08:28:03PM -0500, Thomas Dickey wrote:
> > > > On Mon, Feb 24, 2020 at 06:35:16PM -0500, Thomas Dickey wrote:
> > > > > On Mon, Feb 24, 2020 at 06:25:30PM -0500, Thomas Dickey wrote:
> > > > > > On Tue, Feb 25, 2020 at 04:37:11AM +
installed on a system rely on ncurses provided by the system?
Thanks in advance,
oh
--
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
___
freebsd-current
tem_error:145:10: fatal
error: '__errc'
file not found #include <__errc>
[...]
Kind regards,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4
macro 'TASK_INIT_FLAGS'
MPASS((priority) >= 0 && (priority) <= 255); \ ^ 1 error generated.
*** Error code 1
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Mark
RRENT do not support this chip
although it seems
very common and well supported by several Linux distributions including the
OpenWRT router
project (I think that is the ath10k driver suite as far as I recall).
Thanks in adavnce,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittl
Trying to buildworld and/or buildkernel fails after upgrading 13-CURRENT today
to FreeBSD 13.0-CURRENT #25 r354673: Wed Nov 13 06:47:48 CET 2019 amd64.
After a "make -j8 cleanworld cleandir" (trying to circumvent the problem) I
still face the ccp error shown below rendering the system impossible t
The last known good update of CURRENT on a Fujitsu Primergy RX2530-M5 (only one
of two sockets equipted, 64 GB RAM) was October, 17th, 2019 before 15 o'clock,
I suppose that was r353680 that time. Today's update to r353881 resulted in an
immediate crash when the network (igb0-igb3, two built-in i35
The last known good update of CURRENT on a Fujitsu Primergy RX2530-M5 (only one
of two sockets equipted, 64 GB RAM) was October, 17th, 2019 before 15 o'clock,
I suppose that was r353680 that time. Today's update to r353881 resulted in an
immediate crash when the network (igb0-igb3, two built-in i35
On Tue, 27 Aug 2019 08:43:53 +0300
Toomas Soome wrote:
> > On 27 Aug 2019, at 08:08, Warner Losh wrote:
> >
> > On Mon, Aug 26, 2019, 5:32 PM Rebecca Cran > <mailto:rebe...@bsdio.com>> wrote:
> >> On 8/26/19 5:22 AM, O. Hartmann wrote:
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 21 Aug 2019 22:34:21 +0300
Toomas Soome schrieb:
> > On 21 Aug 2019, at 22:30, O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Am Wed, 21 Aug 2019 22:14:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 21 Aug 2019 22:29:29 +
greg@unrelenting.technology schrieb:
> August 22, 2019 12:23 AM, "O. Hartmann" wrote:
>
> > Am Wed, 21 Aug 2019 15:58:24 -0500
> > Karl Denninger schrieb:
> >
> >&g
On Thu, 12 Sep 2019 06:27:00 +0200
"O. Hartmann" wrote:
> Hello,
>
> we install several pkg-based systems and poudriere from a dedicated tree of
> sources, instead of /usr/src it is in our case /pool/sources/CURRENT/src and
> 12-STABLE/src. Compilation of the sour
Hello,
we install several pkg-based systems and poudriere from a dedicated tree of
sources, instead of /usr/src it is in our case /pool/sources/CURRENT/src and
12-STABLE/src. Compilation of the sources is done within a JAIL!
For a couple of days now, both trees, CURRENT (r352239 now) and 12-STABL
On Wed, 28 Aug 2019 13:57:00 +0200
Alexander Leidinger wrote:
> Quoting "O. Hartmann" (from Tue, 27 Aug 2019
> 10:11:54 +0200):
>
> > We have a single ZFS pool (raidz), call it pool00 and this pool00 conatins a
> > ZFS dataset pool00/poudriere which we want
Hello list,
trying to setup a poudriere jail on recent CURRENT and have some severe trouble.
We have a single ZFS pool (raidz), call it pool00 and this pool00 conatins a
ZFS dataset pool00/poudriere which we want to exclusively attach to a jail.
pool00/poudriere contains a complete clone of a for
On Thu, 22 Aug 2019 08:58:55 +0300
Toomas Soome wrote:
> > On 22 Aug 2019, at 06:04, O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Am Wed, 21 Aug 2019 22:29:29 +
> > greg@unrelenting.technology schrieb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 21 Aug 2019 15:58:24 -0500
Karl Denninger schrieb:
> BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Am Wed, 21 Aug 2019 22:34:21 +0300
> > Toomas Soome schrieb:
> >
> > >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 21 Aug 2019 22:34:21 +0300
Toomas Soome schrieb:
> > On 21 Aug 2019, at 22:30, O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Am Wed, 21 Aug 2019 22:14:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 21 Aug 2019 22:34:21 +0300
Toomas Soome schrieb:
> > On 21 Aug 2019, at 22:30, O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
>
p to gain access to the shell; there is no timeframe to hit any
key to stop by
and access the efi shell.
Kind regards,
oh
>
> > On 21 Aug 2019, at 20:58, O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > I ran
I ran into serious trouble booting several boxes off UEFI. On modern hardware,
the ESP is around 200 - 300 MB in size and usually I install
/efi/freebsd/loader.efi, loader.efi taken from /boot/loader.efi. On some older
hardware, specifically on a Lenovo E540 with latest available firmware (2.28),
w
ssing?
Thanks in advance,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXV2Gb
Recent CURRENT (r351247) fails to buildkernel due to a compilation error,
pointing to an mii issue.
For almost every mii-related if_ the compiler drops an error like:
[...]
Building
/usr/obj/usr/src/amd64.amd64/sys/WOTAN/modules/usr/src/sys/modules/usb/udl/udl.ko
===> usb/uether (all) Building
/u
Tomorrow I try to install a prepared pkg tar arcive
FreeBSD-kernel from
aCURRENT pkg base and hope this will fix the issue.
Regards,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder
Hello,
today I ran into a ctastrophy with r350671. After installing a fresh compiled
system and rebooted the box, UEFI loader dropped a bunch of errors, like some
hex numbers stating, that a hash/superblock has is wrong and then the booting
stopped at the OK loader prompt.
Rebooting the machine w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Tue, 30 Jul 2019 17:01:57 +0300
Toomas Soome schrieb:
> > On 30 Jul 2019, at 15:43, O. Hartmann wrote:
> >
> > On Wed, 24 Jul 2019 18:07:22 +0300
> > Toomas Soome wrote:
> >
> >>> On
On Wed, 24 Jul 2019 18:07:22 +0300
Toomas Soome wrote:
> > On 24 Jul 2019, at 16:48, O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Am Wed, 24 Jul 2019 12:06:53 +0200
> > "O. Hartmann" mailto:o.hartm
Enabling debug messages in /etc/rc.conf results in a last line showing some
code containing "devmatch()" (can't remember, box is at a remote site now).
The machine is a two socket box but with only one socket populated and 64GB
RAM, see the following dmesg.
Kind regards,
O. Hartman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 24 Jul 2019 12:06:53 +0200
"O. Hartmann" schrieb:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Am Wed, 24 Jul 2019 12:09:16 +0300
> Toomas Soome schrieb:
>
> > > On 24 J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 24 Jul 2019 12:09:16 +0300
Toomas Soome schrieb:
> > On 24 Jul 2019, at 11:11, O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hallo,
> >
> &g
prove concurrent Fortuna
performance
kern.random.fortuna.concurrent_read="1"
# Forward Information Bases (FIBs)
net.fibs=10
net.add_addr_allfibs=0
[...]
Again, with the exact same setting 12-STABLE r349288 boots fine, rr350274
doesn't.
FreeBSD 12-STABLE r
Can someone
On all CURRENT boxes running CURRENT > r349150 we face the very same boot
failure, if /etc/rc.conf.local is present (i.e. on CURRENT, 13.0-CURRENT #7
r349169: Tue Jun 18 10:34:13 CEST 2019 amd64):
The box boots and thentries to start services denominated
in /etc/rc.conf.local, like net/openldap-se
On Tue, 4 Jun 2019 07:44:09 +0200
Baptiste Daroussin wrote:
> On Tue, Jun 04, 2019 at 07:32:16AM +0200, O. Hartmann wrote:
> > Hello List,
> >
> > lately I ran into a serious problem installing packages in a nanoBSD
> > environment, in which the package repository s
Hello List,
lately I ran into a serious problem installing packages in a nanoBSD
environment, in which the package repository server is "remotely" on site. The
issue as documented below occurs on both 12-STABLE r348529 and CURRENT r348600
and must have been introduced shortly, since the last known
d/11.edit
/usr/share/doc/usd/12.vi /usr/share/doc/usd/13.viref;
do if [ -f /${file} ]; then rm -f /${file}; fi; done --- distrib-dirs ---
-deU -i
- -f /usr/src/etc/mtree/BSD.root.dist -p / sh: -deU: not found
*** [distrib-dirs] Error code 127
Greetings,
oh
- --
O. Hartmann
Ich widersp
Recently an error seem to have spread across our 12-STABLE platforms offering
poudriere. Building the binaries for FreeBSD 12-STABLE (recent version r347613)
on systems running FreeBSD 12-STABLE (r347613) worked very well before, but now
the install process seem to fail on all boxes the very same w
here first.
I need supported fibre NICs for both 100 MBit and 1GBit for FreeBSD 11 as
well as 12 and if there is a suggestion, please, I'm open to it.
Thanks in advance,
O. Hartmann
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd
On Tue, 9 Apr 2019 10:42:47 +0200 (CEST)
Trond Endrestøl wrote:
> On Tue, 9 Apr 2019 10:06+0200, Trond Endrestøl wrote:
>
> > On Mon, 8 Apr 2019 19:58+0200, O. Hartmann wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
ounting all ZFS filesystems via "zfs mount -a"
operates as
expected and all filesystems are available as usual.
Kind regards,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Tue, 5 Mar 2019 23:08:32 +0100
Dimitry Andric schrieb:
> On 5 Mar 2019, at 21:54, O. Hartmann wrote:
> >
> > Am Tue, 5 Mar 2019 13:16:26 -0500
> > Shawn Webb schrieb:
> >
> > > On Tue, Mar 05, 2019 at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Tue, 5 Mar 2019 13:16:26 -0500
Shawn Webb schrieb:
> On Tue, Mar 05, 2019 at 05:45:11PM +0100, O. Hartmann wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hello,
> >
> > recent bu
archive
>>> /usr/obj/usr/src/amd64.amd64/tmp/obj-tools/lib/clang/libllvm/libllvm.a
c++: error: linker command failed with exit code 1 (use -v to see invocation)
*** [clang] Error code 1
make[4]: stopped in /usr/src/usr.bin/clang/clang
[...]
I tried to rebuild world from a fresh /usr/s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 27 Feb 2019 14:18:28 -0500
Shawn Webb schrieb:
> On Wed, Feb 27, 2019 at 08:08:24PM +0100, O. Hartmann wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Running 12-STABLE and CURRENT on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Running 12-STABLE and CURRENT on a PCengine APU4C (CPU: AMD GX-412TC SOC,
Coreboot Version:
v4.9.0.2), I ran into trouble running latest 12-STABLE on that hardware.
The box is quitting with
[...]
mmcsd0: 31GB at mmc0
50.0MHz/4bit/65535-block
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Mon, 18 Feb 2019 08:06:54 +0100
"O. Hartmann" schrieb:
> On Sun, 17 Feb 2019 19:07:53 +0100
> "O. Hartmann" wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hell
On Sun, 17 Feb 2019 19:07:53 +0100
"O. Hartmann" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello,
>
> after the bump of 12-STABE to 1200503 I'm unable to update AMD64 poudriere
> jails's to this version anymor
On Sun, 17 Feb 2019 18:35:25 -0800 (PST)
"Rodney W. Grimes" wrote:
> > On Sun, Feb 17, 2019 at 03:04:41PM -0800, Mark Millard wrote:
> > >
> > >
> > > On 2019-Feb-17, at 10:03, Steve Kargl > > troutmask.apl.washington.edu> wrote:
> > >
> > > Anyone have insight into what evdev is? There ap
URRENT, same 12-STABLE revision).
How to fix this?
Thanks in advance,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGI
On Tue, 29 Jan 2019 11:36:37 +0300
"Andrey V. Elsukov" wrote:
> On 28.01.2019 15:44, O. Hartmann wrote:
> > Stopping all jails, destroying all epairs and bridge0 doesn't change
> > anything. The problems occured when IPv6 came into play on the specific
> > ho
Hello out there.
I'm using some dual stack installations and I'd like to configure FreeBSD's
(CURRENT at the moment) syslogd on a syslog-server to handle incoming logging
messages from remote FBSD boxes (mixed, 11.2, 12.0 and CURRENT).
I' facing a very weird situation.
Scenario:
The server has
I ran into severe problems on CURRENT ( FreeBSD 13.0-CURRENT #193
r343521: Mon Jan 28 10:26:36 CET 2019 amd64), VIMAGE enabled host with jails
utilizing IPv6.
Scenario:
The main host has two Braodcom (bce0|1) NICs. bce0 is the physical NIC attached
to a routed/switched network for the main host.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Wed, 16 Jan 2019 18:33:36 +0100
Tijl Coosemans schrieb:
> On Wed, 16 Jan 2019 15:23:40 +0100 "O. Hartmann"
> wrote:
> > We have an experimental IPV6 network and within this network, FreebSD
> > CURRENT
> > (
t variable to use to boot. Some will even create new Boot
> variables that they use when you choose a raw device to boot from.
>
> There's other people that have efi programs that will pop up a menu for you
> to select a particular Boot to use. They then set BootNext an
We have an experimental IPV6 network and within this network, FreebSD CURRENT
(r343087) is acting as a CUPS print server, while a bunch FreeBSD 12-STABLE
boxes are CUPS clients.
The setup, so far, worked with IPv4. Introducing IPv6 addresses on both server
and host results in the error
[Client 1]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Thu, 10 Jan 2019 22:22:05 +0100
"O. Hartmann" schrieb:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Am Thu, 10 Jan 2019 12:02:15 -0800
> Cy Schubert schrieb:
>
> > I'm not able to reproduce
? The system is a "pkg system"
completely, so I have to switch on debugging without kernel rebuilds. Any
advice?
Kind regards,
O. Hartmann
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28
On Thu, 27 Dec 2018 08:38:20 -0700
Warner Losh wrote:
> On Dec 27, 2018 7:42 AM, "O. Hartmann" wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Am Thu, 27 Dec 2018 13:29:44 +0100
> "Hartmann, O." schrieb:
>
>
> > Updated
OOTX64.EFI' to UEFI: No error: 0
>
> What the heck is that?
>
> What does this error mean? No error: 0?
>
> The box is unusable.
>
>
> Kind regards,
>
> O. Hartmann
>
>
>
I found this PR, Bug 229191, from June, 2018:
https://bugs.freebsd.org/b
te named[3195]: starting BIND 9.12.3-P1
Prior to the last update of dns/bind912, this router/firewall appliance was
running more
than a month without having such trouble, even the ISP is randomly changing the
IPv4/IPv6
addresses spread over the day.
What is wrong?
Kind regards,
O. Hartman
re
on all
systems I've running FBSD 13-CURRENT and 12-STABLE so far.
Can someone please look into this and fix the problem or point me to my
mistake? I'm out
of clues.
Thanks in advance and kind regards,
O. Hartmann
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meine
nd, I have textproc/docproj installed
(FOP and
DBLATEX enabled, as it seems they are needed by some PDF tools necessary to aim
for the
PDF build).
What is wrong?
Thanks in advance and kind regards,
O. Hartmann
[...]
dbook/imagelib/callouts/'" --maxdepth 12000 -o eresources.xm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Wed, 12 Dec 2018 16:25:56 -0800
"Simon J. Gerraty" schrieb:
Hello,
thanks for your resonse.
> O. Hartmann wrote:
> > delete-old|-libs afterwards, I started again a build (filemon loaded!).
> > And, surprise,
>
thread XEON box, base system on UFS/FFS 256 GB Samsung 850
Pro SSD,
ZFS RAIDZ volume of 16 TB as data graveyard).
Thanks in advance.
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
vm/tools/clang/lib/Serialization/GeneratePCH.cpp:51)
> > >>> GeneratePCH.o:(clang::PCHGenerator::HandleTranslationUnit(clang::ASTContext&))
> > >>> in
> > >>> archive /usr/obj/usr/src/amd64.amd64/lib/clang/libclang/libclang.a
> >
> > ld:
der/writer just in case the error
indicates
a hardware failure.
Kind regards,
O. Hartmann
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-
iLUEARMKAB0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Mon, 3 Dec 2018 09:26:14 +0100
"O. Hartmann" schrieb:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Fri, 30 Nov 2018 23:14:07 +0900
> Tomoaki AOKI schrieb:
>
> > On Wed, 28 Nov 2018 19:39
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Fri, 30 Nov 2018 23:14:07 +0900
Tomoaki AOKI schrieb:
> On Wed, 28 Nov 2018 19:39:21 +0100
> "O. Hartmann" wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Am Wed, 28
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Fri, 30 Nov 2018 14:32:52 +
Gary Palmer schrieb:
> On Fri, Nov 30, 2018 at 01:12:32PM +0100, O. Hartmann wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > My ISP is offering IPv6 only "a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Fri, 30 Nov 2018 16:41:02 +
"Bjoern A. Zeeb" schrieb:
Sorry for the late reply, had a long weekend off ...
> On 30 Nov 2018, at 15:59, Christoph Moench-Tegeder wrote:
>
> > ## O. Hartmann (ohartm...@walstatt.org):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
My ISP is offering IPv6 only "as an experimental feature", so I had to ask to
enable the
IPv6 stack on my connection. I'm using FreeBSD 12-STABLE as the basis for a
router/firewall/PBX system, FreeBSD's onboard ppp client is performing the
uplink a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Wed, 28 Nov 2018 15:00:42 +0100
Emmanuel Vadot schrieb:
> Hi,
>
> On Wed, 28 Nov 2018 10:51:11 +0100
> "O. Hartmann" wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> &
upposed to reside) but no chance.
Before starting investigating this issue further I'd like to ask wether there
is a
general support provided or is that type of notebook dead matter for FreeBSD of
the
modern kind?
Thanks in advance,
oh
p.s. please CC me, I'm not subscribing all lists
ere linked to /usr/lib/libssl.so.8 where the
> > openssl update creates libssl.so.9. There may be more I haven't found yet,
>
> add multimedia/ffmpeg to this list ..
>
> imb
>
> ___
> freebsd-current@freebsd.org
rg mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
dns/samba-nsupdate
net/liboauth
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder fü
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Thu, 30 Aug 2018 10:44:25 -0500
Kyle Evans schrieb:
> On Thu, Aug 30, 2018 at 10:41 AM O. Hartmann wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Running a NanoBSD with lots of &quo
monolithic on that appliance in question - I do not
allow the
loading of kernel modules.
I guess this is a bug or do I miss something here?
Kind regards,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Mei
1 - 100 of 1408 matches
Mail list logo
