Re: Unfamiliar console message: in prompt_tty(): caught signal 2

> On Apr 21, 2024, at 1:48 PM, bob prohaska wrote: > > On Sun, Apr 21, 2024 at 10:16:55PM +0200, Dag-Erling Smørgrav wrote: >> bob prohaska writes: >>> Apr 20 22:14:37 www su[30398]: in prompt_tty(): caught signal 2 >> >> This means someone ran `su` and pressed Ctrl-C instead of entering a >>

Re: pkg scripts need updating

> On May 14, 2024, at 7:19 AM, Michael Butler > wrote: > > After commit aa48259f337100e79933d660fec8856371f761ed to src which removed > security_daily_compat_var, I get these warnings daily.. > > aaron.protected-networks.net login failures: > > aaron.protected-networks.net refused

Re: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

> On Jan 9, 2024, at 7:17 AM, void wrote: > > On Tue, Jan 09, 2024 at 12:24:40PM +, void wrote: >> On Tue, Jan 09, 2024 at 10:24:53AM +, void wrote: >>> On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote: >>>> >>>> Was th

Re: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

> On Jan 7, 2024, at 6:29 AM, void wrote: > > Hi, > > on a rpi4/8GB, my rc.conf looks like so. It's an ipv4-only system on a LAN > not directly connected to the internet > > hostname="generic.home.arpa" > ifconfig_genet0="inet 192.168.1.199 netmask 255.255.255.0" >

Re: Proposal: Disable compression of newsyslog by default

> On Dec 22, 2023, at 23:18, Xin Li wrote: > > Hi, > > Inspired by D42961, I propose that we move forward with disabling the > compression by default in newsyslog, as implemented in > https://reviews.freebsd.org/D43169 > > Historically, newsyslog has compressed rotated log files to save

Re: src.conf(5) to specify multiple flavours of a port

> On Aug 21, 2023, at 9:34 PM, Warner Losh wrote: > > On Mon, Aug 21, 2023, 10:24 PM Graham Perrin > wrote: >> In a thread elsewhere, as an example that did not involve src.conf, Mark >> Johnston wrote: >> >>> $ cd /usr/ports/graphics/gpu-firmware-intel-kmod

Re: src.conf(5) to specify multiple flavours of a port

> On Aug 21, 2023, at 10:01 PM, Bakul Shah wrote: > > On Aug 21, 2023, at 9:24 PM, Graham Perrin wrote: >> >> In a thread elsewhere, as an example that did not involve src.conf, Mark >> Johnston wrote: >> >>> $ cd /usr/ports/graphics/gpu-firmware-intel-kmod >>> $ sudo make reinstall

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

> On Aug 10, 2023, at 2:56 PM, Matthias Apitz wrote: … > Don't know if I can answer your questions. I'm building ports with > poudriere and lang/python27 is pulled in from some other ports. The port > lang/python27 itself is not on my list for poudriere: > > # grep python

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

> On Aug 10, 2023, at 2:38 AM, Matthias Apitz wrote: > > El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman > escribió: > >> This perfectly builds on the latest HEAD without any problem as shared in my >> build log. I am not sure what is wrong at your end. Neither can I

Re: armv7 kyua runs via chroot on aarch64: zfs tests leave behind processes from timed out tests

> On Aug 3, 2023, at 10:20 AM, Mark Millard wrote: > > On Aug 3, 2023, at 07:18, Mark Millard wrote: > >> On Aug 3, 2023, at 00:19, Mark Millard wrote: >> >>> This is after the patch (leading whitespace might >>> not have been preserved in what you see): >>> >>> # git -C /usr/main-src/

Re: Does kyua based testing need some hazmat/bindings/_openssl.abi3.so related updating?: Undefined symbol "ERR_GET_FUNC"

> On Jul 10, 2023, at 3:27 PM, Mark Millard wrote: > > On Jul 10, 2023, at 15:03, Mark Millard > wrote: > >> On Jul 10, 2023, at 11:42, The Doctor wrote: >> >>> On Mon, Jul 10, 2023 at 08:56:22AM -0700, Mark Millard wrote: The subject line's question was

Re: "make hierarchy" from main tree breaks c++ headers on older branches with unclear errors if "make install world" is interrupted

> On May 31, 2023, at 2:06 AM, Dimitry Andric wrote: > > On 31 May 2023, at 01:07, Enji Cooper <mailto:yaneurab...@gmail.com>> wrote: … >> That’s a fair point, however, given that this follows the standard >> installation workflow… >> 1. etcupdate pre-ru

Re: "make hierarchy" from main tree breaks c++ headers on older branches with unclear errors if "make install world" is interrupted

> On May 28, 2023, at 3:53 AM, Dimitry Andric wrote: > > On 28 May 2023, at 07:18, Enji Cooper wrote: >> >> I just tried to run “make hierarchy” from a main tree on a 13.2-RELEASE >> system, and doing so completely broke my headers. >> It took me about 30 mi

"make hierarchy" from main tree breaks c++ headers on older branches with unclear errors if "make install world" is interrupted

Hi all, I just tried to run “make hierarchy” from a main tree on a 13.2-RELEASE system, and doing so completely broke my headers. It took me about 30 minutes to figure out what happened… /usr/include/c++/v1/__string was a header, whereas on :main it’s a directory?! $ git diff

Re: MOTD is not created correctly (since 2022/02/18)

> On May 22, 2023, at 11:06 PM, Enji Cooper wrote: > >> >> On May 22, 2023, at 8:18 PM, Jamie Landeg-Jones wrote: >> >> I've just finally updated to 13-stable, and can't be the first to notice >> this?! >> >> /etc/rc.d/mot

Re: MOTD is not created correctly (since 2022/02/18)

> On May 22, 2023, at 8:18 PM, Jamie Landeg-Jones wrote: > > I've just finally updated to 13-stable, and can't be the first to notice > this?! > > /etc/rc.d/motd contains the line: > > uname -v | sed -e 's,^\([^#]*\) #\(.* [1-2][0-9][0-9][0-9]\).*/\([^\]*\) $,\1 > (\3) #\2,' > > Note the

Re: Call for participation

Hi, > On Sep 2, 2021, at 07:44, Warner Losh wrote: > > Greetings, > > As teased on twitter, now that summer is over, it's a good time to start > working on the next steps with git. When we moved to git, we knew a number > of things would come in phase 2 since phase 1 was limited to moving

Re: Files in /usr/share/misc

> On Jan 24, 2021, at 05:36, mj-mailingl...@gmx.de wrote: > What is the history behind /usr/share/misc? Hi Martin, Have you read “man hier”, by chance? This might elucidate things a bit. Cheers, -Enji ___ freebsd-current@freebsd.org mailing list

Re: CURRENT, usr/src on git, howto "mergemaster"?

> On Jan 4, 2021, at 11:42 AM, Marek Zarychta > wrote: … > it's probably high time to stop escalating this thread. Some people like > the way in which mergemaster copes with updates, some people like > etcupdate. With Git clean and smudge filters applied on local repo and > $FreeBSD$ IDs

Re: CURRENT, usr/src on git, howto "mergemaster"?

> On Jan 4, 2021, at 11:15 AM, Jeffrey Bouquet > wrote: … >> Dear Enji, >> >> to satisfy your curiosity: Yes, I have tried etcupdate(8) a few times >> over years. It works fine, but I don't like the idea of editing >> conflicted files. >> >> I won't complain about etcupdate(8), but please

Re: CURRENT, usr/src on git, howto "mergemaster"?

> On Jan 4, 2021, at 10:59 AM, Steve Kargl > wrote: > > On Mon, Jan 04, 2021 at 10:30:28AM -0800, Enji Cooper wrote: >> >>> On Jan 4, 2021, at 10:19, Warner Losh wrote: >>> >>> mergemaster has been on its way out since well before the switch

Re: CURRENT, usr/src on git, howto "mergemaster"?

> On Jan 4, 2021, at 10:54 AM, Enji Cooper wrote: > > >> On Jan 4, 2021, at 10:49 AM, Marek Zarychta > <mailto:zarych...@plan-b.pwste.edu.pl>> wrote: > > … > >> Terrible idea IMHO, but I am only the weak voice from the userbase. >>

Re: CURRENT, usr/src on git, howto "mergemaster"?

> On Jan 4, 2021, at 10:49 AM, Marek Zarychta > wrote: … > Terrible idea IMHO, but I am only the weak voice from the userbase. > > It's like deprecating old, well-worn hammer in the favour of the nail > gun. Why not deprecate biff(1), pom(6), nvi(1) etc.? Marek, I’m curious: have

Re: git non-time-sequential logs

> On Jan 4, 2021, at 9:05 AM, Alan Somers wrote: > > On Mon, Jan 4, 2021 at 9:58 AM Poul-Henning Kamp > wrote: > >> >> John Kennedy writes: >> >>> This might be perfectly natural and just new to me, but when I look at >> the >>> git logs this morning I

Re: CURRENT, usr/src on git, howto "mergemaster"?

> On Jan 4, 2021, at 10:33 AM, David Wolfskill wrote: > > On Mon, Jan 04, 2021 at 10:30:28AM -0800, Enji Cooper wrote: >> ... >> Adding to this: it has no maintainer, it’s less featureful, and it lacks >> tests. Once I switched to etcupdate a few yea

Re: CURRENT, usr/src on git, howto "mergemaster"?

> On Jan 4, 2021, at 10:19, Warner Losh wrote: > > On Mon, Jan 4, 2021 at 9:36 AM Marek Zarychta > wrote: > >> W dniu 04.01.2021 o 17:14, Warner Losh pisze: >> >>> etcupdate does a full three merge, while mergemaster fakes it in a number >>> of ways. etcupdate directly keeps track of the

Re: Undeletable files after kyua test runs

> On Jul 4, 2020, at 8:59 AM, Enji Cooper wrote: > >> >> On Jul 2, 2020, at 7:57 PM, Enji Cooper > <mailto:yaneurab...@gmail.com>> wrote: >> >>> >>> On Jun 29, 2020, at 10:26 AM, Gordon Bergling >> <mailto:g...@freebsd.org>>

Re: Undeletable files after kyua test runs

> On Jul 2, 2020, at 7:57 PM, Enji Cooper wrote: > >> >> On Jun 29, 2020, at 10:26 AM, Gordon Bergling wrote: >> >> Hi, >> >> I recently stumbled across undeletable files that are generated by kyua test >> runs, >> for example >

Re: Undeletable files after kyua test runs

> On Jun 29, 2020, at 10:26 AM, Gordon Bergling wrote: > > Hi, > > I recently stumbled across undeletable files that are generated by kyua test > runs, > for example > > -rwxr-xr-x 1 root wheel 0 May 9 13:10 > /tmp/kyua.aB4q62/8676/work/fileforaudit > > I haven't yet identified the

Re: r362666 breaking buildworld (don't know how to make nvpair.c) & Fix/Patch

(Moving hackers to BCC since the issue is current-related) > On Jun 26, 2020, at 6:56 PM, Neel Chauhan wrote: > > Hi, > > When I attempt to build world in 13-CURRENT, I get this error: … > The build broke with mmacy@'s commit r362666 which renamed nvpair.c to > bsd_nvpair.c without renaming

Re: src/usr.bin/kyua breaks on manbuild.sh: Permission denied

> On Mar 27, 2020, at 6:04 PM, Ed Maste wrote: > > On Fri, 27 Mar 2020 at 20:48, Julian H. Stacey wrote: >> >> l /usr/src/contrib/kyua/doc/manbuild.sh >>-rw-r--r-- 1 jhs staff 5187 Mar 25 12:34 >> /usr/src/contrib/kyua/doc/manbuild.sh > > Indeed, this is the problem.

Re: Best way to print something from the kernel at 1s intervals?

> On Nov 28, 2019, at 12:52, Peter Eriksson wrote: > > I’ve been looking into the “kernel looks to be hung at reboot” problem at > bit. Adding a lot of printf() calls to the relevant parts it looks like it > actually isn’t hung but busy unmounting filesystems (which we have thousands > of),

Re: Weird goings on with make::empty()

> On Sep 4, 2019, at 07:58, Ian Lepore wrote: > >> On Wed, 2019-09-04 at 09:33 -0500, Kyle Evans wrote: >> On Wed, Sep 4, 2019 at 9:27 AM Enji Cooper >> wrote: >>> >>> >>>> On Sep 4, 2019, at 04:59, Poul-Henning Kamp >>&g

Re: Weird goings on with make::empty()

> On Sep 4, 2019, at 04:59, Poul-Henning Kamp wrote: > > On: > >Repository Root: svn+ssh://repo.freebsd.org/base >Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >Revision: 351809 > > I built a kernel, but drm-current-kmod did not get compiled > from the new world order in

Re: CURRENT: supeblock hash failure - CURRENT wrecking disks

(CCing Kirk) > On Aug 7, 2019, at 01:37, O. Hartmann wrote: > > 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

Re: rc script: manual stop vs system shutdown

> On Aug 1, 2019, at 11:07, Andriy Gapon wrote: > >> On 01/08/2019 20:30, Enji Cooper wrote: >> On Aug 1, 2019, at 08:53, Rodney W. Grimes >> wrote: >> >>>> >>>> Is it possible in an rc script to distinguish between a manual stop &g

Re: rc script: manual stop vs system shutdown

On Aug 1, 2019, at 08:53, Rodney W. Grimes wrote: >> >> Is it possible in an rc script to distinguish between a manual stop >> (e.g., service foo stop) and a stop during a system shutdown (via >> rc.shutdown) ? >> Are there any marker variables for that? >> Or something in the global system

Re: Someone broke USB

> On Jul 8, 2019, at 03:16, Hans Petter Selasky wrote: > >> On 2019-07-08 12:06, Gary Jennejohn wrote: >> On Mon, 8 Jul 2019 11:50:31 +0200 >> Hans Petter Selasky wrote: >>> Hi Steve, >>> >>> Can you test this patch? >>> >>> I made a slight variant which delay the explore threads instead of

Re: error: yacc.h: No such file or directory

> On Jun 18, 2019, at 06:59, Enji Cooper wrote: > > >> On Jun 18, 2019, at 06:53, Ian Lepore wrote: > > ... > >> Last Saturday, Bryan (cc'd) made a series of commits (r349061-69) that >> were all somehow related to dependency processing in the build

Re: error: yacc.h: No such file or directory

> On Jun 18, 2019, at 06:53, Ian Lepore wrote: ... > Last Saturday, Bryan (cc'd) made a series of commits (r349061-69) that > were all somehow related to dependency processing in the build. I > don't know the details, just remember seeing some commits about that. I remember that as well.

Re: sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

> On Jun 17, 2019, at 18:26, Cy Schubert wrote: > > Now that I'm back home, to reply inline re the yacc.h issue. > > In message <201906180021.x5i0l2rk057...@fire.js.berklix.net>, "Julian > H. Stacey > " writes: >> "Julian H. Stacey" wrote: >>> "Bjoern A. Zeeb" wrote: > On 17 Jun 2019, at

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

> On May 27, 2019, at 7:20 PM, Warner Losh wrote: > > On Mon, May 27, 2019, 6:49 PM Enji Cooper <mailto:yaneurab...@gmail.com>> wrote: > > > On May 27, 2019, at 08:27, rai...@ultra-secure.de > > <mailto:rai...@ultra-secure.de> wrote: > >

Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option

> On May 27, 2019, at 08:27, rai...@ultra-secure.de wrote: > > Am 2019-05-27 17:05, schrieb Conrad Meyer: >> Hi Rainier, >> On Mon, May 27, 2019 at 7:47 AM wrote: >>> I have a 32bit FreeBSD 6 binary that I'll need for a bit until the >>> department who is technically responsible for the service

ci.freebsd.org: powerpcspe build failing due to linker error in assembly code

Hi, The following build issue has been cropping up over the past 6 hours. From https://ci.freebsd.org/job/FreeBSD-head-powerpcspe-build/11154/console : 12:49:01 /usr/src/stand/powerpc/kboot/kerneltramp.S: Assembler messages: 12:49:01 /usr/src/stand/powerpc/kboot/kerneltramp.S:88: Error:

Re: Inability to build FreeBSD-current amd64

> On May 14, 2019, at 13:18, Thomas Mueller wrote: > > I have failed in three attempts over the past week to build FreeBSD-current > amd64, error message is about the same each time. > > Build host uname -a shows > > FreeBSD amelia 11.1-STABLE FreeBSD 11.1-STABLE #4: Sun Jul 30 17:28:39 UTC

Re: Danish FreeBSD Developer hates jews collectively

> On May 9, 2019, at 11:03 AM, ossobser...@redchan.it wrote: This is the only reply I’m going to give to this thread that seems like obvious troll bait. As a native English speaker who often gets into debates about controversial issues with respect to concepts like classism, LGBTIQ issues,

Re: New vm-image size is much smaller than previos

> On May 3, 2019, at 9:57 AM, Alan Somers wrote: > > See r346959. Before first boot, you should expand the image up to > whatever size you want. growfs(8) will automatically expand the file > system. > -Alan > > On Fri, May 3, 2019 at 10:32 AM David Boyd wrote: >> >> The vm-image for

Re: SVN r346700 breaks build

> On Apr 25, 2019, at 13:49, Kyle Evans wrote: > > On Thu, Apr 25, 2019 at 3:33 PM Michael Butler > wrote: >> >> Seems that the lib32 piece (on amd64) is now broken; as follows: >> > > *sigh* > > Strike two of three for me today, it seems. Should be fixed in > r346705... sorry about that,

Re: SVN r346645 breaks build of DRM drivers

(Fixing CC) > On Apr 24, 2019, at 8:03 PM, Michael Butler > wrote: > > The removal of dma_mask (around line 105) in > /usr/src/sys/compat/linuxkpi/common/include/linux/device.h breaks the > DRM loadable modules :-( > > As follows .. > > --- amdgpu_amdkfd.o --- >

Panic with r346530 [Re: svn commit: r346530 - in head/sys: netinet netinet6]

Hi Hans, > On Apr 22, 2019, at 1:32 AM, Hans Petter Selasky wrote: > > On 4/22/19 10:10 AM, Hans Petter Selasky wrote: >> On 4/22/19 9:52 AM, Enji Cooper wrote: >>> >>>> On Apr 22, 2019, at 12:27 AM, Hans Petter Selasky >>>> wrote: >>&g

Re: r346025: ZFS filesystems do not mount anymore

> On Apr 9, 2019, at 21:51, Enji Cooper wrote: … > CCing crees@, the author of r346017, for context. I will file a PR soon if > one hasn’t already been filed. I filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237172 to track the issue. Chee

Re: r346025: ZFS filesystems do not mount anymore

> On Apr 9, 2019, at 18:29, Michael Butler wrote: > >> On 2019-04-09 09:30, O. Hartmann wrote: >> 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:

Re: SVN r345859: libxo broke netstat?

> On Apr 5, 2019, at 5:19 AM, Michael Butler > wrote: > > Something changed in libxo that causes 'netstat -i' to segfault as below: > > imb@toshi:/usr/src/usr.bin/netstat> lldb > /usr/obj/usr/src/amd64.amd64/usr.bin/netstat/netstat > (lldb) target create

Re: PMC Sierra SPC SAS-SATA Card + ESXi

> On Mar 9, 2019, at 18:50, Evgheni Melman wrote: > > So I got this weird setup, where I need to passthrough a PMC-Sierra PM8003 > card (same as PM8001, but with external QSFP afaik) to FreeBSD 11-STABLE > running in ESXi. > The card works fine in baremetal FreeBSD 11. Boot is ok, all disks >

Re: problem building dev/e1000

> On Feb 15, 2019, at 11:47, Robert Huff wrote: > > Lev Serebryakov writes: > >>> My question would be: why? If some drivers have a new >>> dependency on iflib, why isn't that expressed in sys/conf/files >>> and handled automatically? >> >> My question exactly. > >I am so glad people

Re: problem building dev/e1000

> On Feb 15, 2019, at 10:46, Eric Joyner wrote: > > ifdi_if.h is a system generated interface file that network drivers that > depend on iflib use. It's generated from ifdi_if.m in sys/net. > > My guess is that you don't have "device iflib" defined in your kernel > configuration. em(4)

Re: problem building dev/e1000

> On Feb 14, 2019, at 13:24, Robert Huff wrote: > > >On a system running: > > FreeBSD 13.0-CURRENT r343080 amd64 > >with source tree updated at midnight last night, attempts to > build a kernel with "device em" die with: > > > ctfconvert -L VERSION -g efirtc.o > cc -target

Re: drm2 removed?

Hi Steve, This looks like breakage from unifying PAE and non-PAE kernels in r343567. CCing kib@ for context. Cheers, -Enji > On Feb 11, 2019, at 08:12, Steve Kargl > wrote: > > Anyone have any idea which recent change broke the > drm-legacy-kmod port. This is why I raised an issue > with

Re: Updating bugzilla password?

> On Feb 4, 2019, at 10:07 AM, Steve Kargl > wrote: > > On Mon, Feb 04, 2019 at 09:39:49AM -0800, Enji Cooper wrote: >> >> >> Let me loop in some other folks. Something might be up with mail forwarding >> for your account. >> > > Just sent

Re: Updating bugzilla password?

> On Feb 4, 2019, at 9:35 AM, Enji Cooper wrote: > > > >> On Feb 4, 2019, at 9:24 AM, Steve Kargl > <mailto:s...@troutmask.apl.washington.edu>> wrote: >> >> On Mon, Feb 04, 2019 at 09:15:28AM -0800, Enji Cooper wrote: >>> >&

Re: Updating bugzilla password?

> On Feb 4, 2019, at 9:24 AM, Steve Kargl > wrote: > > On Mon, Feb 04, 2019 at 09:15:28AM -0800, Enji Cooper wrote: >> >>> On Feb 4, 2019, at 08:34, Steve Kargl >>> wrote: >>> >>> I have forgotten my bugzilla account password.

Re: Updating bugzilla password?

> On Feb 4, 2019, at 08:34, Steve Kargl > wrote: > > I have forgotten my bugzilla account password. I've > entered the Login: account name, and clicked the > "Forgot Password" button. Expecting to receiving an > email that would provide instructions for updating > the password. That email

Re: openssl 1.1.1 utils mkerr.pl

> On Jan 15, 2019, at 5:55 PM, David Cornejo wrote: > > Hi, > > I am working on some code that wants to use mkerr.pl from the openssl > distribution - but this appears to have been left out of the import to > base. > > Is there an alternative method to create the include files produced > from

Re: uname -a output without svn revision number

> On Jan 4, 2019, at 19:00, Yoshihiro Ota wrote: > > I've seen such failures with NFS without lockd. > > Svn fails as it cannot lock its files, too. Yeah. lockd must be running in order for this to work. This hasn’t changed in the last few years. Cheers, -Enji

Re: ld-elf.so.1: /usr/local/lib/libglib-2.0.so.0: Undefined symbol "environ" (RPI/arm64)

> On Dec 27, 2018, at 2:17 AM, Trev wrote: > > Graham Perrin wrote on 26/12/2018 21:20: >> grahamperrin@momh167-gjp4-8570p:~ % date ; uname -v >> Wed Dec 26 10:18:52 GMT 2018 >> FreeBSD 13.0-CURRENT r342466 GENERIC-NODEBUG >> grahamperrin@momh167-gjp4-8570p:~ % iridium >> ld-elf.so.1:

Re: /usr/src/lib/clang/libclang 'emmintrin.h' file not found

> On Dec 27, 2018, at 3:48 AM, Julian H. Stacey wrote: > > Hi current@ > Anyone else seeing make buildworld Clang failures ? > ls -l /usr/bin suggests I last made world on Dec 9, > since then I've failed twice below > Seems the UPDATING doesnt give enough to rescue this. > --- > >

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

> On Dec 22, 2018, at 1:03 PM, Cy Schubert wrote: … > Regarding the Red Hat bugzilla bug, looks like they're doing the right > thing by reaching out to VMware. This should be our position as well. > Add it to ssh_config or sshd_config if one must but have VMware fix > their bugs. Putting

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > > Mark Peek wrote: >> Thanks for the cc:. I forwarded the original report on to an internal >> VMware desktop product contact. > > Thank you. > >> What version of Workstation or Fusion is this occurring on? I saw >> Workstation 14 mentioned

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

> On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: > > Hi, > > There's apparently a bug in VMware Workstation NAT implementation, made > visible by the change to default values of IPQoS in OpenSSH 7.8p1, > making all ssh connections from the guest behind the NAT to fail with > obscure

Re: The future of ZFS in FreeBSD

Hello Matthew, I appreciate the long write up, as someone who still uses FreeBSD ZFS on my NAS box and knowing some of the history with ZFS on *Solaris, etc. Something like this was bound to happen with post the Oracle buyout. > On Dec 18, 2018, at 10:49 PM, Matthew Macy wrote: > > The

Re: cannot build i386 12.0-RELEASE kernel on -current

Hi Henry, > On Dec 12, 2018, at 8:29 AM, Henry Vogt wrote: > > Hi, > > my build machine (FreeBSD:13:amd64 r341429) builds world/kernel ok for amd64, > world for i386 ok, but fails 'make buildkernel' for i386: > > -- snip > > ... > > --- if_vte.o --- >

Re: pkg-base noise

> On Dec 11, 2018, at 11:14 AM, Ian Lepore wrote: > > On Tue, 2018-12-11 at 11:40 -0700, Sean Bruno wrote: >> make[8]: "/home/sbruno/bsd/fbsd_head/share/mk/bsd.files.mk" line 92: >> warning: duplicate script for target "_testsFILESINS_cleanup.ksh" >> ignored >> make[8]:

Re: fix WARNING pid 24503 (uhsoctl): ioctl sign-extension ioctl ffffffff8044692b

FYI! > On Oct 25, 2018, at 4:38 AM, Marcin Cieslak wrote: > > The following patch seems to fix the signed ioctl value warnings > in uhsoctl(). > > The code is the same in the current and stable branches. > > Marcin > > Index: usr.sbin/uhsoctl/uhsoctl.c >

Re: which way to update export_args structure?

> On Oct 22, 2018, at 09:49, Josh Paetzel wrote: > > > >> On Mon, Oct 22, 2018, at 11:05 AM, Brooks Davis wrote: >> >> >> This is the direction I'd been thinking. FWIW, the usecase is more that >> once you've moved away from the struct it's easy to make incremental >> changes then to use a

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 15, 2018, at 6:10 AM, Gleb Smirnoff wrote: > > Enji, > > can you please check that with this patch all your tests pass? Hi Gleb! It almost compiled. I just needed to dereference the `so` pointer: $ git diff /usr/src/sys/kern/kern_sendfile.c diff --git

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 14, 2018, at 10:17 PM, Enji Cooper (yaneurabeya) > wrote: ... > Oh yipes. I guess passing in a server socket (a bound and listening socket) > instead of a client socket (connect’ed to a server socket) for `s` will > result in a crash? > > From > http

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 14, 2018, at 10:12 PM, Enji Cooper (yaneurabeya) > wrote: > >> On Oct 14, 2018, at 9:45 PM, Enji Cooper (yaneurabeya) >> mailto:yaneurab...@gmail.com>> wrote: >> >> >> >>> On Oct 14, 2018, at 7:25 PM, Gleb Smirnoff >

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 14, 2018, at 9:45 PM, Enji Cooper (yaneurabeya) > wrote: > > > >> On Oct 14, 2018, at 7:25 PM, Gleb Smirnoff > <mailto:gleb...@freebsd.org>> wrote: >> >> Hi Enji, >> >> On Sun, Oct 14, 2018 at 06:51:42PM -0700, Enji Cooper

Re: Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

> On Oct 14, 2018, at 7:25 PM, Gleb Smirnoff wrote: > > Hi Enji, > > On Sun, Oct 14, 2018 at 06:51:42PM -0700, Enji Cooper (yaneurabeya) wrote: > E> Hi, > E>I’m seeing a semi-deterministic panic on 12.0-ALPHA9 related to > sendfile(2) when running sendf

Relatively deterministic panic with sendfile(2) when running tests in the sxlock code

Hi, I’m seeing a semi-deterministic panic on 12.0-ALPHA9 related to sendfile(2) when running sendfile_test on the host: https://pastebin.com/raw/6Y7xg0ki; it looks like it’s crashing in the sxlock code when calling sblock on a sockbuf. Are there any commands in gdb you would like me to