Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

On Tue, 4 May 2021 at 11:52, Mark Millard wrote: > > > As far as the utf-8 issues go, diffoscope requires a utf-8 locale and > > I suspect that is the issue. If you don't have LANG set already, try > > setting LANG=C.UTF-8 in your environment. > > That is not the issue for the UnicodeDecodeError:

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

On Mon, 3 May 2021 at 22:26, Mark Millard wrote: > > But I'll note that I've built and stalled py37-diffoscope > (new to me). A basic quick test showed that it reports: > > W: diffoscope.main: Fuzzy-matching is currently disabled as the "tlsh" module > is unavailable. I just looked up tlsh -

Re: FYI: WITH_REPRODUCIBLE_BUILD= problem for some files?

On Thu, 29 Apr 2021 at 02:50, Mark Millard via freebsd-current wrote: > > Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping and > /usr/obj/DESTDIRs/13_0R-CA7-poud/sbin/ping differ > Files /usr/obj/DESTDIRs/13_0R-CA7-chroot/sbin/ping6 and > /usr/obj/DESTDIRs/13_0R-CA7-poud/sbin/ping6 differ >

Re: Portsnap no updates since 3/31/2021 ?

On Tue, 6 Apr 2021 at 06:49, Robert Blayzor via freebsd-stable wrote: > > I have several servers running 11.4 and 12.2 that do nightly portsnap > updates and the last time they've seen anything new is 3/31/2021, since > then, nothing. > > This seems highly unusual since seems like there was

Re: Deprecating base system ftpd?

On Sat, 3 Apr 2021 at 16:39, Ed Maste wrote: > > I propose deprecating the ftpd currently included in the base system > before FreeBSD 14, and opened review D26447 > (https://reviews.freebsd.org/D26447) to add a notice to the man page. I posted this as a proposal for commun

Deprecating base system ftpd?

I propose deprecating the ftpd currently included in the base system before FreeBSD 14, and opened review D26447 (https://reviews.freebsd.org/D26447) to add a notice to the man page. I had originally planned to try to do this before 13.0, but it dropped off my list. FTP is not nearly as relevant

Re: Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

On Thu, 25 Mar 2021 at 15:09, Chris wrote: > > I can only state that I use it only occasionally, and that when I do. I > have had no problems with it. I'm glad that it's there when I need it. Thanks for the reply. Can you comment on your use cases - in particular, did you use mirror, stripe, or

Vinum deprecation for FreeBSD 14 - are there any remaining Vinum users?

Vinum is a Logical Volume Manager that was introduced in FreeBSD 3.0, and for FreeBSD 5 was ported to geom(4) as gvinum. gvinum has had no specific development at least as far back as 2010 and it is not clear how well it works today. There are open PRs with reports of panics upon removing disks,

Re: How do I know if my 13-stable has security patches?

On Fri, 26 Feb 2021 at 12:10, Helge Oldach wrote: > > A shallow tree is about 1.6G. If you want to patch source (say, from > a SA or EN) you certainly also need space for an object tree which is > about 4.5G. The total is >6G. > > I'd say relative to the total required to build, the 1.1G

Re: How do I know if my 13-stable has security patches?

On Thu, 25 Feb 2021 at 15:58, Warner Losh wrote: > > The problem, though, can happen when you run a shallow clone or gitup to > get the sources and build from that. In that case the v number is bogus > (hmmm, we should omit it when we have a shallow clone maybe). I want to clarify one point here

Re: How do I know if my 13-stable has security patches?

On Thu, 25 Feb 2021 at 16:57, Karl Denninger wrote: > > The time (and present items) on a given machine to know whether it is > covered by a given advisory under the "svn view of the world" is one > command, and no sources. That is, if the advisory says "r123456" has > the fix, then if I do a

Re: How do I know if my 13-stable has security patches?

On Thu, 25 Feb 2021 at 02:42, Kevin Oberman wrote: > > Thanks, Ed, but where do I find this? uname -a" gives me stable/13-007101f87. > For a while I was seeing a hyphenated number prefixed with a 'c' and I had > assumed that that number was the sequence. It is (was) - w

Re: How do I know if my 13-stable has security patches?

On Wed, 24 Feb 2021 at 12:35, Kevin Oberman wrote: > > In the svn days, I could just look at my svn revision to check on whether a > security patch was required. Now I have a git hash. I have no idea how to > tell if my system running 13-STABLE of a few days ago has the patch. Thanks for posting

Re: stable/12 git -> svn mirror delayed

On Thu, 18 Feb 2021 at 15:29, Ed Maste wrote: > > The git-svn stable/12 mirror is currently stuck. It encountered an > issue with the OpenSSL 1.1.1j import (e3a8c0df593b) and hasn't been > able to make progress past it. It's under investigation and will > hopefully b

stable/12 git -> svn mirror delayed

The git-svn stable/12 mirror is currently stuck. It encountered an issue with the OpenSSL 1.1.1j import (e3a8c0df593b) and hasn't been able to make progress past it. It's under investigation and will hopefully be resolved soon. (I think the git-svn converter is trying to cherry-pick each of the

Re: where to upgrade 12-stable now, svn still, or git?

On Fri, 12 Feb 2021 at 23:11, tech-lists wrote: > > I saw on cgit that stable/12 was there. These older systems weekly > update their sources via svn till now, in a cron job. At the time I wrote > my message, I saw that svn still works, so was wondering which to use, > which has the latest

Re: where to upgrade 12-stable now, svn still, or git?

On Sat, 13 Feb 2021 at 01:04, Dewayne Geraghty wrote: > > Is there a timeline when svn for stable-12 /usr/src disappears? stable/11 and stable/12 will exist in svn for at least as long as the branches are supported - stable/12 expected EOL is June 30,2024. If you're tracking stable you don't

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

On Thu, 31 Dec 2020 at 02:50, Helge Oldach wrote: > > The only sensible way out is to retire mergemaster and switch to > etcupdate. This would affect any stable/1? users building from source. stable/11 and stable/12 users can continue to update via svn and have $FreeBSD$ expanded, for the life

Deprecating userland a.out support

FreeBSD has used ELF binaries/libraries for decades, but still has support for legacy a.out binaries. Portions of this have been retired over time, and I propose removing the remaining pieces before FreeBSD 13. I'm not proposing making any change to kernel a.out support, but users needing userland

Re: Removing obsolete GDB 6.1.1 for FreeBSD 13

Adding the FreeBSD-stable list to CC for more visibility. On Wed, 2 Dec 2020 at 12:43, Ed Maste wrote: > > I would like to remove GDB 6.1.1 before FreeBSD 13, and propose to > switch the GDB knob to default to NO in the near future. If the > crashinfo utility and related man pages do

Re: after latest patches i386 not fully patched

On Mon, 21 Sep 2020 at 10:04, Ed Maste wrote: > > On Mon, 21 Sep 2020 at 03:42, Walter von Entferndt > wrote: > > > > At Sonntag, 20. September 2020, 14:00:00 CEST, Ed Maste > > wrote: > > > Until pkgbase is in place the most straightforward way to ad

Re: after latest patches i386 not fully patched

On Mon, 21 Sep 2020 at 03:42, Walter von Entferndt wrote: > > At Sonntag, 20. September 2020, 14:00:00 CEST, Ed Maste > wrote: > > Until pkgbase is in place the most straightforward way to address this > > issue will probably be for us to ship a new kernel even if no

Re: after latest patches i386 not fully patched

On Thu, 17 Sep 2020 at 18:45, Dan Langille wrote: > > I understand why this occurs. I have reported it before: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245878 Until pkgbase is in place the most straightforward way to address this issue will probably be for us to ship a new kernel

Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-20:14.linuxkpi

On Wed, 8 Jul 2020 at 17:08, FreeBSD Errata Notices wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > = > FreeBSD-EN-20:14.linuxkpi Errata Notice >

Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

On Tue, 10 Mar 2020 at 19:15, Andy Farkas wrote: > > Is it just a matter of putting "syscons=[sc|vt]" in loader.conf > to select whatever driver? Have a look at sc(4) and vt(4) - in loader.conf: kern.vty=sc or kern.vty=vt And sysctl kern.vty will let you know which you're using.

Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

On Mon, 9 Mar 2020 at 15:15, Andy Farkas wrote: > > On 2020-03-10 01:04, Konstantin Belousov wrote: > > Take a look at r334530. > > "or the user really hates this feature and can't wait to turn it off" So to confirm, your issue is with sc(4), not vt(4)?

Re: Any sync-serial driver users (ce/cp/ctau/cx)?

On Mon, 2 Mar 2020 at 14:03, Ed Maste wrote: > > On Sat, 29 Feb 2020 at 15:57, Warner Losh wrote: > > > > Given the ~15 years of nothing but API changes to these cards, and the lack > > of testing of those changes, and the large technology transitions in net > >

Re: vt [was: Re: [Bug 235564] INDEX.keymaps for vt contains "from-" keymaps but the files are missing]

On Sun, 8 Mar 2020 at 17:13, Andy Farkas wrote: > > Is anyone actually working on the vt(4) driver? Will it ever > become feature-parity with the old sc(4) driver? Yes, and yes. What specific missing functionality are you affected by? > I've noticed some weird things happening on my console

Re: Any sync-serial driver users (ce/cp/ctau/cx)?

On Sat, 29 Feb 2020 at 15:57, Warner Losh wrote: > > Given the ~15 years of nothing but API changes to these cards, and the lack > of testing of those changes, and the large technology transitions in net and > tty layers of the system, I'd honestly be surprised if these drivers still > work.

Any sync-serial driver users (ce/cp/ctau/cx)?

Is anyone using sync serial drivers ce, cp, ctau, or cx? NYCBUG's dmesg didn't turn up any entries. I suspect these are obsolete and ought to be removed. ___ freebsd-stable@freebsd.org mailing list

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

On Sun, 23 Feb 2020 at 12:48, Gerard E. Seibert wrote: > > Until they squash that bug, they should not be in a rush to push out > the door another defective model. Unfortunately complaining that there's a bug in 12.0 or 12.1 or providing additional reports of this will do nothing to help resolve

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

On Tue, 18 Feb 2020 at 05:37, Tomasz CEDRO wrote: > > Maybe its a time to give OpenBSD a try.. I really don't understand this comment, either. Certainly give OpenBSD a try and if it fits your needs better that's great. As far as I'm aware OpenBSD issues a release every six months and supports

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

On Mon, 17 Feb 2020 at 22:24, Tomasz CEDRO wrote: > > Why so short End-Of-Life? Why so many fast and short releases? What for? > > Why pushing problems to production? What was wrong with having one > well tested stable system for a long time? I really don't understand this - FreeBSD 12 is

Re: Light GeoIP support dropped?

On Mon, 6 Jan 2020 at 16:17, Alexander Koeppe wrote: > > Hi, > > since I've upgraded to FreeBSD 12, I don't find a package providing the > lightweight geoip database API incl. GeoIP.h and libGeoIP.so. > > I only find `geoipupdate` which is the non-free variant of the API. Looking at ports

Re: Disabling speculative execution mitigations

On Fri, 6 Dec 2019 at 22:54, O'Connor, Daniel wrote: > > With respect to the man page, I find it difficult to know what a given value > for each sysctl will do, as evidenced by my confusion above about IBRS. scottl recently moved these sysctls to machdep.mitigations in r355436, but they've kept

Re: Missing 12 MFCs

On Thu, 19 Sep 2019 at 18:30, David Cross wrote: > > There are a set of commits in head that have not been pulled into the > stable/12 branch. Many of these are marked as MFC (and are quite old). I'm looking at the WITH_PIE / WITH_BIND_NOW changes, and am looking for re@'s opinion. I'll merge

Re: FreeBSD Quarterly Status Report - Second Quarter 2019

talked about methods for making for more training material available. Partnerships and Commercial User Support We help facilitate collaboration between commercial users and FreeBSD developers. We also meet with companies to discuss their needs and bring that information back to the Project. In Q2, Ed M

Re: Buildworld times (was Re: svn commit: r350256 - in stable/12: . contrib/compiler-rt/lib/sanitizer_common contrib/libunwind/src contrib/llvm/lib/DebugInfo/DWARF contrib/llvm/lib/MC contrib/llvm/lib

On Fri, 26 Jul 2019 at 22:44, Jeremy Chadwick via freebsd-stable wrote: > > TL;DR for lazy folks: > > stable/11 r350330 world + minimal clang = 1:29:34 > stable/11 r350330 world + full clang= 1:46:31 > stable/11 r350252 world + minimal clang = 56:52 > stable/11 r350252 world + full clang

Re: 12.0-RELEASE-p4 kernel panic on i386 boot

On Wed, 15 May 2019 at 00:03, Ed Maste wrote: > > On Wed, 15 May 2019 at 15:09, wintellect Auser > wrote: > > > > Hi all, > > > > Wanted to make you aware of an issue I have encountered, sorry if this is > > the wrong list. > > This is the rig

Re: 12.0-RELEASE-p4 kernel panic on i386 boot

On Wed, 15 May 2019 at 15:09, wintellect Auser wrote: > > Hi all, > > Wanted to make you aware of an issue I have encountered, sorry if this is > the wrong list. This is the right place and thank you for reporting. Looking into it. ___

Re: ifuncs check flawed?

On Tue, 19 Mar 2019 at 16:54, Dan Allen wrote: > > That is why I think the check is flawed! The check works as intended, as suggested by the non-booting kernel produced with the checks removed. To help track this down can you run `make buildenv` and then in the resulting shell collect the

Re: ifuncs check flawed?

On Mon, 18 Mar 2019 at 13:03, Dan Allen wrote: > > The buildworld and buildkernel steps both immediately fail due to the linker > not supporting ifuncs. By default FreeBSD/i386 uses lld as the bootstrap linker (i.e., the linker used for building the kernel, libraries, and userland binaries) but

Re: FreeBSD 12.0 RELEASE i386 can not build a kernel?

On Thu, 28 Feb 2019 at 09:33, Rodney W. Grimes wrote: > > LD?=ld.lld in the right place(s)? Perhaps, I seem to recall some issue with that, but not the specifics. > And is this still an issue for stable/12 i386? > or has ld been changed to ld.lld? stable/12 i386 still has GNU ld as /usr/bin/ld

Re: FreeBSD 12.0 RELEASE i386 can not build a kernel?

On Thu, 28 Feb 2019 at 08:26, Rodney W. Grimes wrote: > > Are you really rally expecting a user to rebuild the world that > he just installed that should be exactly the same world he gets > build (reproduceable builds and all??). I'm expecting that a user will either follow the directions in the

Re: FreeBSD 12.0 RELEASE i386 can not build a kernel?

> > Let me guess. You use 'make' in sys/i386/build/YOUR_KERNEL ? > > Then you need to use 'LD=ld.ldd make'. The proper way of > > 'make buildkernel' from top-level src handles it automatically. > > > If you back up in the thread you would also see the output > is the same for cd /usr/src; make

Re: FreeBSD 12.0 RELEASE i386 can not build a kernel?

On Thu, 28 Feb 2019 at 03:50, Rodney W. Grimes wrote: > > Now the begging question, why isnt the toolchain as shipped > already properly built? The required toolchain is included in 12.0-RELEASE i386 - the linker is /usr/bin/ld.lld. It just needs to be specified explicitly if build via a method

Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-19:05.kqueue

On Wed, 9 Jan 2019 at 15:23, Kurt Jaeger wrote: > > Hi! > > > > Credits:Mark Johnston > > > Affects:FreeBSD 11.2 > > > Corrected: 2019-11-24 17:11:47 UTC (stable/11, 11.2-STABLE) > > > > Should this be 2018 or is this yet in the future? > > And why does fbsd-update fail like

Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-19:05.kqueue

On Wed, 9 Jan 2019 at 15:03, Cy Schubert wrote: > > > Corrected: 2019-11-24 17:11:47 UTC (stable/11, 11.2-STABLE) > > Should this be 2018 or is this yet in the future? Yes, this should be 2018-11-24. Gordon's updating it. ___

Re: Error upgrading 11-STABLE to 12-STABLE in ifunc resolver

On Thu, 27 Dec 2018 at 17:20, Warner Losh wrote: > > > Yes, you should update to the latest stable/11. More details, you need > > to have host clang which includes the r339284 commit. > > We either need to fix this problem, or we need to bump the minimum in > Makefile.inc1. amd64_get_fsbase.c

Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11)

ote, let's give this a week to settle in HEAD before merging it to 11-STABLE. I'll close PR 229236 once it's been merged. -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mail

Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11)

e a try? Thanks! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands syslogd-optional-timestamp-v2.diff Description: Binary data ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe

Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11)

acy' RFC 3164 parser also accept messages without a timestamp. The time on the syslogd server will be used instead. Michael, Marek, could you please give this patch a try? Thanks! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands Index: usr.sbin/syslogd/syslogd.c ===

Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282

2018-06-18 8:02 GMT+02:00 Ed Schouten : > I've just committed the patch (r335314) and > will MFC it to 11-STABLE before the end of the week. Done, in r335492. Thanks again for reporting this issue! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Nethe

Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282

s all right. I've just committed the patch (r335314) and will MFC it to 11-STABLE before the end of the week. Best regards, -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/li

Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282

o need to patch the central (storage) server. -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Deprecating the lmc(4) driver

The lmc(4) driver supports hardware for a number of legacy interfaces, including EIA612/613, T1/E1, T3, etc. The driver's license is ambiguous and attempts to contact the author failed. I would like to remove this driver from 12.0, and have a deprecation notice in review D15182 [1]; I would

HEADS-UP: Deprecation of legacy (v3) password database support

FreeBSD password databases (/etc/pwd.db, /etc/spwd.db) can contain records in one or both of two versions: * v3, a legacy architecture-dependent format * v4, the current architecture- and endian-independent format When v4 support was added in 2003 (r113596) pwd_mkdb emitted both v3 and v4

Re: svn commit: r332493 - stable/11/sys/net

On 14 April 2018 at 07:31, Magnus Ringman wrote: > Hi Brooks, this MFC missed your r331077 > (https://reviews.freebsd.org/D14706) thus stable buildkernel currently > breaks on missing those two macros. Thanks for identifying the missing commit Magnus. I've now merged it in

Call for Testing: 11.1-RELEASE Meltdown/Spectre mitigation merge

Background -- A number of issues relating to speculative execution were found last year and publicly announced January 3rd. A variety of techniques used to mitigate these issues have been committed to FreeBSD-CURRENT and have been merged to the stable/11 branch. The changes will be

Re: Ryzen issues on FreeBSD ? (with sort of workaround)

On 30 January 2018 at 19:48, Mike Tancsa wrote: >> > I also just tried upgrading to the latest HEAD with a generic kernel and > same / similar lockups although procstat -kk gives some odd results > > > root@amdtestr12:/home/mdtancsa # procstat -kk 6067 > PIDTID COMM

Re: date -r {big number} results in segmentation fault

On 30 August 2017 at 01:12, Xin LI wrote: > I think emaste@ have fixed it in r321293. MFC? Thanks for the note, now merged in r323044. ___ freebsd-stable@freebsd.org mailing list

Re: svn commit: r322875 - head/sys/dev/nvme

error, no > warning). Perfect! I've committed this change as r322965. Thanks for testing! -- Ed Schouten <e...@nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 ___ freebsd-stable@freebsd.org mailing list https://lists.free

Re: svn commit: r322875 - head/sys/dev/nvme

Mark, 2017-08-25 14:53 GMT+02:00 Ed Schouten <e...@nuxi.nl>: > 2017-08-25 9:46 GMT+02:00 Mark Millard <mar...@dsl-only.net>: >> It appears that at least 11.1-STABLE -r322807 does not handle >> -std=c++98 styles of use of _Static_assert for g++7 in that >> g++7 re

Re: svn commit: r322875 - head/sys/dev/nvme

static_assert(x, y) -#elif __GNUC_PREREQ__(4,6) +#elif __GNUC_PREREQ__(4,6) && !defined(__cplusplus) /* Nothing, gcc 4.6 and higher has _Static_assert built-in */ #elif defined(__COUNTER__) #define _Static_assert(x, y) __Static_assert(x, __COUNTER__) -- Ed Schouten <e...@nuxi.nl>

Re: svn commit: r322875 - head/sys/dev/nvme

ng does get it right, in my opinion. We should just extend to define _Static_assert() when using GCC in C++ mode (if we're not doing so already). -- Ed Schouten <e...@nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 ___

Re: stable/11 src update r321515 -> r321613 fail in src/usr.sbin/acpi/acpidump/

On 27 July 2017 at 07:02, David Wolfskill wrote: > /usr/src/usr.sbin/acpi/acpidump/acpi.c:1089:6: error: use of undeclared > identifier 'ACPI_SRAT_TYPE_GIC_ITS_AFFINITY'; did you mean > 'ACPI_SRAT_TYPE_GICC_AFFINITY'? Sorry about that, reverted in r321617.

Re: 11.1-BETA2 builds and 11.1-RELEASE schedule reminder

ll the quick replies! -- Ed Schouten <e...@nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "

Re: 11.1-BETA2 builds and 11.1-RELEASE schedule reminder

BSD/i386, so this may be a regression. Can others reproduce this as well? -- Ed Schouten <e...@nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listi

Re: FreeBSD 11.1-BETA1 Now Available

On 12 June 2017 at 00:43, Warner Losh wrote: > > aarch64 support isn't completely integrated into FreeBSD 11 yet. A clarification: arm64/aarch64 support has been available as of FreeBSD 11.0 for Cavium ThunderX, and the SoftIron arm64 hardware is also supported now. What we

FreeBSD-update incorrectly reporting that it is approaching End of Life

FreeBSD-update has outdated release lifetime data, and is emitting a false warning that the End-of-Life date for FreeBSD 11.0-RELEASE-p8 is approaching. | WARNING: FreeBSD 11.0-RELEASE-p8 is approaching its End-of-Life date. | It is strongly recommended that you upgrade to a newer | release

Looking for libvgl users

2014 at 11:26, Ed Maste <ema...@freebsd.org> wrote: > vgl(3) is a graphics library for syscons(4) that provides some basic > graphics operations (e.g. some mode setting, bitmaps, boxes, > ellipses). Right now it does not support the newer vt(4) console. > > In order to help d

Re: cc: error: no such file or directory: '/usr/obj/jenkins/workspace/HardenedBSD-10-STABLE-unstable-amd64/sys/boot/efi/loader/../../ficl/libficl.a' *** [loader.sym] Error code 1

../../ficl/libficl.a' > *** [loader.sym] Error code 1" Out of curiosity, why is this email sent to a FreeBSD mailing list and am I on the Cc? This concerns HardenedBSD, right? -- Ed Schouten <e...@nuxi.nl> Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717

Re: cc: error: no such file or directory: '/usr/obj/jenkins/workspace/HardenedBSD-10-STABLE-unstable-amd64/sys/boot/efi/loader/../../ficl/libficl.a' *** [loader.sym] Error code 1

On 7 January 2016 at 16:53, Ed Schouten <e...@nuxi.nl> wrote: > Hi Oliver, > > 2016-01-07 19:32 GMT+01:00 Oliver Pinter <oliver.pin...@hardenedbsd.org>: >> We got this error during the jenkins build: "cc: error: no such file >> or directory: >> '/usr

Re: vt_core.c vt_is_cursor_in_area different behavior after r282823

On 13 May 2015 at 03:02, Marko Turk mark...@markoturk.info wrote: Hi, after r282823, new vt_is_cursor_in_area is, in some cases, returning different values than the old function. For example: If (my + vd-vd_mcursor-height) is equal to (area-tr_begin.tp_row), old function will return 1 and

Re: pty/tty or signal strangeness, or grep/bsdgrep bug?

Hi all, 2012/10/23 Ed Schouten e...@80386.nl: Will try to come up with a decent patch tomorrow evening. Ahem; the day after tomorrow. Jeremy, could you please try the following patch? http://80386.nl/pub/tty-bg-read.txt I decomposed the TTY read routine into four separate functions to improve

Re: pty/tty or signal strangeness, or grep/bsdgrep bug?

2012/10/25 Jeremy Chadwick j...@koitsu.org: I assume a commit to HEAD + MFC in 2 weeks is in order? Yes. We're far too late to get this into 9.1, so I'll MFC it after the release. Patch committed as r242078! -- Ed Schouten e...@80386.nl ___ freebsd

Re: pty/tty or signal strangeness, or grep/bsdgrep bug?

there still was some kind of freeze in effect or not. Thanks for clarifying. -- Ed Schouten e...@80386.nl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable

Re: pty/tty or signal strangeness, or grep/bsdgrep bug?

when input is available. Old tty code did the recheck for background state inside the loop after the sleep. Exactly. Was just debugging this as well and came to the same conclusion. Will try to come up with a decent patch tomorrow evening. Thanks for reporting the issue! -- Ed Schouten e

Re: Inconsistent utx.active?

UseLogin enabled on one of my systems from now on to see whether it occurs sporadically. Thanks for reporting the issue. -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgp0DE1Ur5bxA.pgp Description: PGP signature

Re: Inconsistent utx.active?

Hi Vlad, Has anyone else noticed erratic bookkeeping by utmpx in RELENG_9? Would you mind explaining to me what you're seeing? It's hard for me to fix bugs if I don't get proper reports. -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpcKCladCJsr.pgp Description: PGP signature

Re: Inconsistent utx.active?

pasting the output of `getent utmpx active'? Thanks, -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpsQaKT9RQiy.pgp Description: PGP signature

Re: Inconsistent utx.active?

-- Fri Feb 24 23:57:53 2012] user process: id=7074732f3000 pid=15880 user=ed line=pts/0 host=m.fxq.nl 0x7074732f30 is equal to pts/0. Maybe they're generated by some different login service or you've configured PAM/OpenSSH/etc. in a non-default way? Thanks so far, -- Ed Schouten e...@80386.nl

Re: mpslsi0 : Trying sleep, but thread marked as sleeping prohibited

Hi Kashyap, * Desai, Kashyap kashyap.de...@lsi.com, 20120222 18:51: Adding Ed Schouten and Jorg Wunsch as I see there are author of msleep/mtx related APIs. Am I? :-) 1. When any irq is register with FreeBSD OS, it sets TDP_NOSLEEPING pflag. It means though irq in freebsd is treated

Re: Two problems still present in RC3

? Thanks, -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpXk4FUWsqI1.pgp Description: PGP signature

Re: Two problems still present in RC3

can do the following: - run script -t 0 ~/log jove ... - Delete characters - As soon as possible as jove starts to misbehave and the screen contents are wrong, run `killall -9 script' - Send me the log Thanks, -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgp1bNN1gIMbA.pgp Description

Re: mysqld_safe holding open a pty/tty on FreeBSD (7.x and 8.x)

there is still a session associated with the TTY. See the following thread: http://lists.freebsd.org/pipermail/freebsd-ports/2010-July/062417.html -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpq5AlaJIXSZ.pgp Description: PGP signature

Re: After 7.3-8.1, moused on serial mouse draws 100% CPU

me the output of `pstat -t` for cuau0? It's a bit strange the read() on the TTY returns EAGAIN, since this doesn't seem to be generated by the TTY layer itself. It also seems moused is pretty badly written, looking at how it operates on fd_sets. -- Ed Schouten e...@80386.nl WWW: http://80386.nl

Re: After 7.3-8.1, moused on serial mouse draws 100% CPU

Hi all, I should really get myself subscribed to sta...@... Anyway, Michael, can you attach truss to the process to see what it's actually doing (truss -p $pid)? I'm interested in a single `iteration' of what it's doing. Thanks! -- Ed Schouten e...@80386.nl WWW: http://80386.nl

Re: Serial console problems with stable/8

) { error = tty_wait(tp, tp-t_dcdwait); if (error != 0) %%% -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgp5bVOCevFGN.pgp Description: PGP signature

Re: Serial console problems with stable/8

some of the drivers enforced CLOCAL when the device is used as a boot device. Maybe sio(4) does this, while uart(4) does not? An advantage of the patch is that it makes this construct superfluous. -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpEAKnJjfUKU.pgp Description: PGP signature

Re: Panic in destroy_dev_sched_cb() for tty

commit it to SVN. Thanks for reporting! -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpVPlQxKBSgQ.pgp Description: PGP signature

Re: mounting ext3 for rw

On Sunday 10 January 2010 08:24, Zoran Kolic wrote: Looking at GENERIC in 8.0, I don't see ext2 at all. Just as module. Probably could be added. hmmm. indeed. there isn't the option in the default GENERIC. must have been in one of the betas, and i kept it. it is options EXT2FS

Re: mounting ext3 for rw

On Saturday 09 January 2010 08:40, Zoran Kolic wrote: I should probably kldload ext2fs.ko first to have support. the way i use it to mount them since it's a fuse-implementation, i use /usr/local/etc/rc.d/fusefs(or fuse, i don't remember) onestart and it loads the fuse module. contrary to

Re: mounting ext3 for rw

On Monday 04 January 2010 17:58, Zoran Kolic wrote: Hi all! I prepare to make plug music server with usb connected hard drive, formated ext3, since the system is ubuntu 9.04 as default. My rips are back-uped on spare usb disk, formated as ufs. My idea is to copy files from ufs to ext3 drive,

Re: TIOCSTI possibly broken under 8.0 ?

* Jeremy Chadwick free...@jdc.parodius.com wrote: Adding Ed Schouten to the thread, who will probably be able to shed some light on things. :-) http://80386.nl/pub/tty.diff Wrote it some time ago, but nobody wanted to test it for me, which made me asume nobody cared. ;-) -- Ed

Re: mounting ext3 for rw

used sheevaplug, so i can't be of any assistance there. hope i was helpful, Ed -- Real programmers don't document. If it was hard to write, it should be hard to understand. signature.asc Description: This is a digitally signed message part.

Re: TIOCSTI possibly broken under 8.0 ?

* Pete French petefre...@ticketswitch.com wrote: http://80386.nl/pub/tty.diff Just tested the patch - works beautifully! Please commit and MFC if you can :-) Done. Will MFC it in two weeks from now. Greetings, -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpx5Et2x4Za4.pgp

Re: something fails with svn

* jhell jh...@dataix.net wrote: With those remarks I will leave it up to your honed skills to figure out. If you don't have anything constructive to say, please refrain from responding to any message on these lists. The purpose of these lists is to help each other. -- Ed Schouten e...@80386

Re: something fails with svn

* jhell jh...@dataix.net wrote: Take a look at your git config. The problem lies there and is very visible. After you are done fixing that re-read the whole email that you posted. Would you mind sharing what causes the problem then, Sherlock Holmes? -- Ed Schouten e...@80386.nl WWW: http

Re: cannot alter 'to' addess in email on 8.0

Pete, According to jilles@ this seems to because the new TTY code lacks an implementation of TIOCSTI (simulate keyboard input -- yuck). Could you try the following patch, please? http://80386.nl/pub/tty.diff Thanks! -- Ed Schouten e...@80386.nl WWW: http://80386.nl

  1   2   >