ion patch? This will more than
confirm that this is an upstream problem and not in the FreeBSD Makefiles.
This would be of great help as I cannot reproduce the problem at boot but
after boot using service netif (which the old wpa_supplicant 2.9 also had).
An additional confirmation that the -dev
In message , David Wolfskill writes:
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
> On Tue, Sep 07, 2021 at 10:13:23AM +0200, Jakob Alvermark wrote:
> &g
rks because command associated
>with process 19463 is not really 'display' and the
>symlink isn't resolved to actually kill 'magick'.
>
>So, just chekcing (2), here. Is this a change in behvior
>for FreeBSD?
>
It's likely your app is rep
Sorry for the breakage.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
In message
, Idwer Vollering writes:
> I can confirm this commit has addressed
t;
> create_args_wlan0=3D"country BR regdomain FCC"
> [...]
>
> The last fix still works, although `sleep' isn't necessary.
>
> @@ -29,6 +29,7 @@
> }
> =20
> wpa_poststart() {
> + ifconfig ${ifn} down
> ifconfig ${ifn} up
> }
>
d06d7eb09131 has taken care of this.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
n all my FreeBSD machines, here and
at $JOB, except for only one, I feel this is perfectly reasonable.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
x is rebuild it. That usually
fixes any panics I experience here. Of course, make sure your virtualbox
ports subdirs are fully patched, as it's an opportune time to update it too.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
-nodbg-clang/usr/main-src/arm64.aarch64/tmp/usr/lib/
> libc++.so:GROUP ( /lib/libc++.so.1 /usr/lib/libcxxrt.so )
>
> Again the tmp/usr/lib/libc++.so path but the content has /lib/libc++.so.1 .
>
> Again it was a META_MODE build.
>
> https://ci.freebsd.org and https://ci.fr
mh uses only that port
though it can pipe directly to the sendmail binary when built that way. If
dma doesn't support SMTP submission, we may need to review various port
default options or whether ports even support it.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
/dtrace.sh
dtrace: invalid probe specifier fbt::uma_reclaim:entry { printf("in
uma_reclaim\n"); }: "/usr/lib/dtrace/psinfo.d", line 1: cannot translate
from "struct thread *" to "lwpsinfo_t *"
slippy#
I'm not sure if this is related to 2d5d2a986ce or
A full clean build resolved the problem. It was likely some incompatible
CTF or possibly some other patch that touched DTrace that left my obj tree
in an inconsistent state.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
In message <20220319022405.ga29...@lonesome.com>, Mark Linimon writes:
> Anyone objecting to this, be careful, I might ship a pile of such
> things to you from the depths of the closets :-)
<<=1
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP:
.html
> >
> > I don't think 2.2.10 is warranted.
>
> Agreed. The upgrade isn't sufficiently important.
>
> How about 2.2.9.1?
I had a different more sinister thought: Announcing that we've moved from
BSDL to GPLv3 to be more like Linux.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
The need of the many outweighs the greed of the few.
ntel
laptop?
If my hunch that this may be caused by a malloc() failure, would it be a
good idea to print a nasty warning when malloc failures in loader occur?
Because silently failing, resulting in weird behaviour is more of a POLA
than a nasty message. If not this, a loader variable to enable verbose
messages might help in debugging these kinds of problems. Again, this
assumes my hunch that it's a malloc() failure is what actually happened.
--
Cheers,
Cy Schubert or
FreeBSD UNIX: Web: http://www.FreeBSD.org
NTP: Web: https://nwtime.org
e**(i*pi)+1=0
Old DTrace scripts I've used months or even years ago also fail with the
same error. It's not this one probe. All probes result in the pr_gid error.
I'm currently rebuilding my "prod" tree from scratch with the hope that
it's simply something out of sync. But,
In message <20220723035223.57cd...@slippy.cwsent.com>, Cy Schubert writes:
> I'm not sure if this is because my obj tree needs a fresh rebuild and
> reinstall or if this is a legitimate problem. Regardless of the dtrace
> command entered, whether it be a fbt or sdt, the fo
In message , Mark Johnston writes:
> On Sat, Jul 23, 2022 at 07:14:44AM -0700, Cy Schubert wrote:
> > In message <20220723035223.57cd...@slippy.cwsent.com>, Cy Schubert writes:
> > > I'm not sure if this is because my obj tree needs a fresh rebuild and
> > >
In message <20220723185533.9ea7d...@slippy.cwsent.com>, Cy Schubert writes:
> In message , Mark Johnston writes:
> > On Sat, Jul 23, 2022 at 07:14:44AM -0700, Cy Schubert wrote:
> > > In message <20220723035223.57cd...@slippy.cwsent.com>, Cy Schubert writes
>
In message <20220724030857.b57f...@slippy.cwsent.com>, Cy Schubert writes:
> In message <20220723185533.9ea7d...@slippy.cwsent.com>, Cy Schubert writes:
> > In message , Mark Johnston writes:
> > > On Sat, Jul 23, 2022 at 07:14:44AM -0700, Cy Schubert wrote:
> >
In message , Mark Johnston writes:
> On Sun, Jul 24, 2022 at 10:07:19AM -0700, Cy Schubert wrote:
> > In message <20220724030857.b57f...@slippy.cwsent.com>, Cy Schubert writes:
> > > In message <20220723185533.9ea7d...@slippy.cwsent.com>, Cy Schubert write
> s:
&
In message <20220725153706.a2bb...@slippy.cwsent.com>, Cy Schubert writes:
> In message , Mark Johnston writes:
> > On Sun, Jul 24, 2022 at 10:07:19AM -0700, Cy Schubert wrote:
> > > In message <20220724030857.b57f...@slippy.cwsent.com>, Cy Schubert
e process of changing build and boot processes and the
potential POLA fallout from such a change. A change like this needs to
be architected.
I don't think this is the mailing list to discuss this topic. This
should be discussed on ports@. Not here. Maybe it should be moved there
as this is a ports not a base O/S issue.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
In message <20220827082638.57901a72@slippy>, Cy Schubert writes:
> On Sat, 27 Aug 2022 15:38:44 +0200
> Juraj Lutter wrote:
>
> > > On 27 Aug 2022, at 15:27, Michael Gmelin wrote:
> > >=20
> > >=20
> > > =20
> > >> On 27. Aug 20
In message <202208280842.27s8gdxn055...@nuc.oldach.net>, Helge Oldach
writes:
> Cy Schubert wrote on Sat, 27 Aug 2022 17:26:38 +0200 (CEST):
> > As stated before in this thread, replacing /var/run with tmpfs is not a
> > supported configuration.
>
> Not supported? What
ult in more human
error. I've learned over my long career to rely more on automation than
human beings. Automation [should] never fail and when it does it does
temporarily until the bug is found and fixed. Human beings inconsistently
fail.
If it were an auto-discovery script that created a
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>,
> > Michael Gmelin w
> > rites:
In message <20220829082514.63926...@thor.intern.walstatt.dynvpn.de>,
FreeBSD Us
er writes:
> Am Sun, 28 Aug 2022 06:11:20 -0700
> Cy Schubert schrieb:
>
> > In message <20220828130107.1a76d54a.gre...@freebsd.org>, Michael Gmelin
> > writes:
> > >
>
I. Instead, they really need to have bindings
> automatically generated at build time. That's possible, but it's not
> the default.
This is exactly what happened with DMD D. When 64-bit statfs was introduced
all DMD D compiled programs failed to run and recompiling didn't help. The
DMD upstream failed to understand the problem. Eventually the port had to
be removed.
>
> So what the Rust community really needs is a way to know which symbols
> will be stable across releases, and which might vary. Are you
> suggesting that anything from a non-POSIX header file should be
> considered variable?
>
Rust and every other community.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
it shouldn't, because the strange behaviour
I had encountered a couple of months ago would never have happened had I
been using meta mode.
Though I can't prove it, my sense is that it does "gratuitously" rebuild
llvm more often than without. I can't prove this scientifically. Just a
seat of the pants "assessment."
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
5) option could serve the same purpose it does in linux,
immediately prior to late option handling.
Altering the kernel wait forever is undesirable. This would result in
boot hangs requiring console access to work around the problem. This
would be a PITA and POLA for unattended remote sites.
--
making his patch. Our
> resolver can't tell us a negative answer versus a timeour. This definitely i
> s
> a problem and I already started investigating it. But definitely out of scop
> e
> of NFS.
>
> --
> Gleb Smirnoff
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
it will run on these older machines or
should I wait until -current settles down, e.g. is more or less in a
bug-fix state?
Any other pitfalls one would need to consider prior to running this
kind of test?
Regards, Phone: (250)387-8437
Cy Schubert
(250)387-8437
Cy Schubert Fax: (250)387-5766
Sun/DEC Team, UNIX GroupInternet: [EMAIL PROTECTED]
ITSD
Province of BC
"COBOL IS A WASTE OF CARDS."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-
o the stream at
> this point would do no one any good.
Why not a port? Anyone who want to "test" it out can do so yet we can
still ship tried and proven code in 4.0R. Once core is comfortable
with the port it can be put into the base tree. I think mergemaster
mig
as password.
530 Login incorrect.
ftp: Login failed.
ftp> 221 Goodbye.
cwtest$
It's been "broken" for the last couple of days.
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Team Leader, Sun/DEC Team Internet: [EMA
The following is from BUGTRAQ. There's a fix for -stable, though there
is none for -current. Is -current vulnerable?
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Open Systems Group Internet: [EMAIL PROTECTED]
e could so far as having a INSTALL_SUID_root='su passwd ...',
INSTALL_SUID_man='man', INSTALL_SUID_uucp='uuname uustat uux ...'
options, just to name three, which would list all of the setuid
binaries in FreeBSD. You would remove the ones you don't need from
use EPSV/EPRT pair and LPSV/LPRT pair, in-
stead of PASV and PORT. The meaning is the same.)
I've removed all IPv6 options from my kernel at home (to circumvent a
Kerberos V through pipsecd through NAT problem) and I have no problems
with ftp(1).
What would make ftp(1) think it has a
This might even solve my Kerberos V problem when IPv6 is enabled in the
kernel.
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Team Leader, Sun/DEC Team Internet: [EMAIL PROTECTED]
Open Systems Group, ITSD, ISTA
Province of BC
In
mmary, the patch is a huge step in the right direction. It could
very well be that KRB5 ftp may be at fault, not IPv6 in FreeBSD. I
don't know at this time.
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Team Leader, Sun/DEC Team
;ing an array of 14 9.1 giggers
An Alpha my team manages with 1 TB of images on UFS takes 4 hours to
fsck.
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Team Leader, Sun/DEC Team Internet: [EMAIL PROTECTED]
Open Systems Group, ITSD,
In message <[EMAIL PROTECTED]>, Garrett
Wollman w
rites:
> <
> said:
>
> >> 79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished in 0:4
> 3 (dump)
>
> SIGINFO! SIGINFO! SIGINFO!
Much better idea!
Regards,
ogin class, and was able to get master.passwd to
> print... This was 4.x though, not CURRENT, so maybe this is something that
> wasn't affected in CURRENT, and that's what you're referring to, or
> something.
I am able to exploit the bug in 4.4-RC. I am not able to exploit
g compatibility across platforms is more important
than adjusting tcsh's quirky behaviour, which BTW matches the quirky
behaviour of the original csh on other platforms, rather than to have
csh conform to what the Bourne family of shells do.
Regards, Phone: (250)38
e and lost once it scrolls of your console.
It's a no-brainer. Let's do it.
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Team Leader, Sun/DEC Team Internet: [EMAIL PROTECTED]
Open Systems Group, ITSD, ISTA
Province o
I just submitted a PR and patch in kern/24740 to fix a tagged queueing
related filesystem corruption problem on CONNER CFP1080 drives. The
patch adds an entry to the xpt_quirk_tabke. Anyone willing to commit
this for me?
Regards, Phone: (250)387-8437
Cy Schubert
Regards, Phone: (250)387-8437
Cy SchubertFax: (250)387-5766
Team Leader, Sun/Alpha Team Internet: [EMAIL PROTECTED]
Open Systems Group, ITSD, ISTA
Province of BC
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav
writes:
> Cy
In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav
writes:
> Cy Schubert - ITSD Open Systems Group <[EMAIL PROTECTED]> writes:
> > In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav
> > writes:
> > > Hmm, I've had a CFP1080S (Antigua) for years,
ed this.
Would anyone care to point me in the right direction?
--
Cheers, Phone: 250-387-8437
Cy SchubertFax: 250-387-5231
Team Leader, Sun/Alpha Team Email: [EMAIL PROTECTED]
Open Systems Group, CITS
Ministry of Management Services
Province
In message <[EMAIL PROTECTED]>, Craig Rodrigues writes:
> On Sat, Nov 30, 2002 at 03:48:00PM -0800, Cy Schubert - CITS Open Systems Gro
> up wrote:
> > I've been working on getting the tripwire port to build on -CURRENT.
> > Through this process I've stumbled
; > function
> >it appears in.)
>
> does the problem still occur if you add in 'using namespace std'?
Thanks. That also fixed it.
--
Cheers, Phone: 250-387-8437
Cy SchubertFax: 250-387-5231
Team Leader, Sun/Alpha Te
clude/g++. Make sure that you clean out this directory before doing
> an installworld.
My email that started this thread stated that I had already done this.
Actually, I had done this months ago when I installed current on my new
(well... old) testbed. I did it yet again (and reinstalled wor
401 - 452 of 452 matches
Mail list logo
