Re: Now I am aware
> On Jan 19, 2016, at 09:21, Joe Nosay wrote: > > of how self-centered and selfish all of you are. (Removing @FreeBSD.org hat and also removing some of the individuals on the mailing lists and moving the public mailing lists to BCC) Hi Joe, It’s difficult proposing things like you are and have been in the past (especially when the world is very much driven by currency). I thought that the idea was a noble social endeavor, even if it was a bit rough planning wise to commit resources to in what you had presented. The FreeBSD community (in and of itself) has a limited number of resources tackling several issues on multiple fronts (many of which might be encouraged/driven by our employers), and not all of us might have your interests and ideas in mind for FreeBSD (diversity of thought). My focus and interests in FreeBSD are stability, quality of the operating system, testing, repeatability, etc. My days of tinkering with Unix on a desktop or laptop (anything non-ChromeOS, non-OSX, or non-Windows, e.g. FreeBSD, Linux, OpenSolaris) came to an end a couple years ago because I’ve found that running Unix (in particular X.org based Unix) is a time sink that I no longer am interested in committing to (I’ve run Fedora/Gentoo Linux on desktops/laptops with limited success as well as FreeBSD with limited success on laptops over the years [*]), especially when other vendors (Adobe in particular) look at Unix and decide to decommission support for their products. Outside of my “9-5” (in reality 10+ hour days), I focus on friends and social and political issues that have been impacting communities that I’m a part of (LGBT issues, #blacklivesmatter issues, housing issues in Seattle, etc), as well as myself personally (self-care is a good thing to practice to avoid emotional, mental, and/or physical burnout). Like I recommended before in private, I think you need to find the right audience of people who understand and have similar interests in what you’re trying to achieve in order to discuss and cultivate your ideas with, and bring it to the maturity that it needs to be at in order to be accepted and adopted. Having a team of advocates to work with will help with your endeavor. What you’ve proposed before is not a simple undertaking: it involves several moving parts that aren’t currently available as well as a vision to drive these from design to end-result, unless you have an engineering organization that you can fund (or lots of sports drinks and long sleepless nights to commit to in order to achieve the work… but beware — this leads to burnout). I really hope whatever living situation you’re dealing with improves. I can empathize with it having been exposed to several friends and acquaintances who’ve been at the short end of the stick lately housing wise in the Seattle area. Take care and I wish you the best, whatever the outcome. -NGie * The best laptop experience I’ve ever had was FreeBSD on an ASUS Netbook 4 years ago, which (unfortunately) was completely underpowered and underspec’ed (all of my other laptop experiences have been utter failures due to proprietary drivers, lack of suspend/resume, reliable wireless support, etc). It couldn’t build FreeBSD ports reasonably, and the wired NIC port wouldn’t properly reset the PHY every time I unplugged the cable on it (so once I unplugged the CAT6 cable it would stop transmitting data). Eventually I donated the Netbook to someone else because I had far too many computers to split my attention between. On the bright side, I got it to do source builds, wireless, suspend and resume (on i386 which was unheard of back then… thanks jkim@!!), and fluxbox on a tiny 12” screen — which was better than PCBSD at the time :)! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg/ports system terribly messed up?
On Mon, Sep 29, 2014 at 11:13 PM, O. Hartmann wrote: > > Hello. > > I just made the last update of the ports yesterday (I use portmaster -da > performing this > task) and obviously or superficially everything went all right. > > I'm running on the boxes in question most recent CURRENT. > > On one system, a subsequent start of updating ports starts to freak out when > updateing > lang/gcc: it loops over and over on some ports already updated, especially > devel/binutils, but the port looping on isn't specific and varies. > > On every CURRENT box I tried this morning to update the ports again, I find > this > frsutrating message (depends on installation, but it seems in principal the > same, only > the affected ports in dependency chain varies): Are you using portmaster? If so, it might be fallout from r272282. Cheers, ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: RFT: Please help testing the llvm/clang 3.5.0 import
On Fri, Nov 28, 2014 at 1:03 PM, Dimitry Andric wrote: > Hi, ... Hi Dimitry, As a request to speed up the build process further, - Would it be [easily] possible in the clang35 branch to bootstrap the compiler for a specific architecture? The bootstrap / cross compiler for instance always builds N targets instead of building just the desired TARGET/TARGET_ARCH combo. - Could a "MK_CLANG_ALL_TARGETS" or something similar option be added to src.opts.mk to fine tune this process for those of us who don't want to build a cross-compile toolchain every iteration for our target MACHINE/MACHINE_ARCH? I made a lot of progress on my faster-build branch ( https://github.com/yaneurabeya/freebsd/tree/faster-build ), but got mired down in the minutiae of how this needs to be implemented (it worked up until I ran make tinderbox, of course :)..), and had to work on other things... Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/openvpn build failure on 12-CURRENT/amd64
On Mon, Aug 1, 2016 at 7:31 AM, Shawn Webb wrote: ... > HardenedBSD's kernel and world matched and still had the very same > build error. > > Here's the build log: http://pastebin.com/TEBih1Sx Confirmed -- why's it looking for tcp6local/udp6local though (this isn't a valid protocol, and for some odd reason it's being picked up from the sample config file..?)? Looks like a port bug... Thanks, -Ngie $ sudo make -C /usr/ports/security/openvpn build ... PASS: t_lpback.sh The following test will take about two minutes. If the addresses are in use, this test will retry up to two times. Options error: Bad protocol: 'udp6local'. Allowed protocols with --proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client] [tcp] [udp6] [tcp6-server] [tcp6-client] [tcp6] Use --help for more information. Options error: Bad protocol: 'udp6local'. Allowed protocols with --proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client] [tcp] [udp6] [tcp6-server] [tcp6-client] [tcp6] Use --help for more information. FAIL: t_cltsrv.sh 1 of 2 tests failed (1 test was not run) Please report to openvpn-us...@lists.sourceforge.net *** [check-TESTS] Error code 1 $ grep -r udp6local work/ work/openvpn-2.3.11/sample/sample-config-files/loopback-client.test:proto udp6local ::1 work/openvpn-2.3.11/sample/sample-config-files/loopback-server.test:proto udp6local ::1 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Passwordless accounts vi ports!
> On Aug 10, 2016, at 22:05, O. Hartmann wrote: > > I just checked the security scanning outputs of FreeBSD and found this > surprising result: > > [...] > Checking for passwordless accounts: > polkitd::565:565::0:0:Polkit Daemon User:/var/empty:/usr/sbin/nologin > pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin > saned::194:194::0:0:SANE Scanner Daemon:/nonexistent:/bin/sh > clamav::106:106::0:0:Clamav Antivirus:/nonexistent:/usr/sbin/nologin > bacula::910:910::0:0:Bacula Daemon:/var/db/bacula:/usr/sbin/nologin > [...] > > Obviously, some ports install accounts but do not secure them as there is an > empty password. > > I consider this not a feature, but a bug. saned is the only one that might concern me because the login shell isn't nologin(1). Cheers, -Ngie ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Mosh regression between 10.x and 11-stable
> On Aug 11, 2016, at 09:30, John Hood wrote: > > I still can't reproduce this on 3 different 11.0-BETA4 servers and a > variety of clients and networks. Can you try and identify a more > portable repro or at least figure out why it fails on your system? > > Please try applying this patch, too. It's a shot in the dark, though. Dumb question: what ssh key type(s) (dsa, rsa, etc) are you using Peter :)? Thanks, -Ngie ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: recent change to vim defaults?
> On Jan 15, 2017, at 08:03, Julian Elischer wrote: > > I noticed that suddenly vim is grabbing mouse movements, which makes life > really hard. > > Was there a specific revision that brought in this change, and can it be > removed? "set mouse=" will disable the feature you're describing. -Ngie PS I find the new feature incredibly annoying and disable it on all FreeBSD clients where I install vim. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more)
> On Apr 14, 2017, at 19:53, Mark Millard wrote: > > On 2017-Apr-14, at 4:30 PM, Gerald Pfeifer wrote: > >> On Thu, 13 Apr 2017, Pedro Giffuni wrote: >>> I didn’t want to get into this but the problem is that as part of it's >>> build/bootstrapping process, GCC historically takes system headers >>> and attempts to “fix” them. I am unsure the fixes do anything at all >>> nowadays but the effect is that the compiler tends to take snapshots >>> of the system headers when it is built. cdefs.h is used by all the >>> system headers so changes in cdefs.h have good chances affecting >>> such builds but any change are likely to cause similar trouble. >>> >>> In the case of gcc-aux, it appears the compilation is based on a >>> bootstrap compiler which already carries outdated headers. >>> A workaround, suggested by gerald@ the last time a similar issue >>> happened was to run for install-tools/fixinc.sh. I think that may >>> regenerate the headers and let the build use updated headers. >>> Ultimately gcc-aux needs maintainer intervention and using >>> outdated headers will break sooner or later: especially on -current. >> >> Indeed, thanks for the analysis/background, Pedro! >> >> I had a look at gcc6-aux is based on the 20170202 snapshot of GCC 6, >> and perhaps John (as the maintainer of that port) has plans to update >> it? Let me copy him. > > [As I have a prior E-mail exchange with John M. indicating that > he was not intending to be the lang/gcc6-aux maintainer, I > avoid spamming him with this material: I've removed him from > the CC list in this reply. I can send the material to him if I > see evidence of his wanting it.] > > Just FYI: > > [Previously: temporarily adding __nonnull and __nonnull_all > back into into my local head FreeBSD variant got problems > with: __vm_ooffset_t and __vm_pindex_t no longer existing and > also the same pid_t issue indicated below.] > > > I tried using [on a Pine64+ 2GB aarch64 system]: > > # > /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap/libexec/gcc/aarch64-aux-freebsd12.0/6.3.1/install-tools/mkheaders > /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap > > to deal with __nonnull, __nonnull_all, __vm_ooffset_t, and __vm_pindex_t. > > I then built via portmaster -CDK usage. Various header issues > did go away but the build of lang/gcc6-aux still stopped with: > > In file included from > /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/simple-object.c:20:0: > ./config.h:556:15: error: two or more data types in declaration specifiers > #define pid_t int > ^ > > I'm guessing that the define for pid_t in config.h resulted > in something like: > > typedef ??? pid_t; > > that turned into something like a: > > typedef ??? int; > > for the error listed above. > > There were also implicit-declaration warnings: > > /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/simple-object.c: > In function 'simple_object_internal_read': > /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/simple-object.c:75:21: > warning: implicit declaration of function 'read' > [-Wimplicit-function-declaration] > ssize_t got = read (descriptor, buffer, size); > ^~~~ > /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/simple-object.c: > In function 'simple_object_internal_write': > /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/simple-object.c:119:23: > warning: implicit declaration of function 'write' > [-Wimplicit-function-declaration] > ssize_t wrote = write (descriptor, buffer, size); > ^ > > The implicit-declaration warnings for read and write may well > also not be expected/desirable. > > It may be that more than a script run is needed to make > things be appropriate. Is there a reason why you need ada support (that seems to be the only real reason for installing gcc6 vs gcc6-aux)? gcc6-aux uses a snapshot of gcc6 with custom options. Thanks! -Ngie signature.asc Description: Message signed with OpenPGP using GPGMail
