Re: Sitting inside, looking out...
To avoid the crosspost police, I've removed -stable from the thread. Speaking of incentives, prizes, etc. you might want to read the book: "Punished by Rewards" by Alfie Kohn. H To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: REQ: Test /etc/rc clean-up
I understand that folks use X$foo becuase if $foo evaluates to -whatever then there is a *chance* that test will misunderstand. I gather the reason for using the X trick *and* the quotes is because there might be some whitespace in there, too. Given that "case" is a builtin and using "case" instead of "test" is both faster, easier to read (less clutter), and supports mixed-case easier, I prefer "case". But I went down this road before. H To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NTP daemon and Y2K issues
If you are saying that FreeBSD has patches to ntp that are missing from ntp4, please submit them to UDel. Don't bother sending patches that only fix problems with ntp3; ntp3 is no longer supported. ntp-4.1.0 should be available in a few weeks. I'm waiting for some portability patches to settle down, some minor NT cleanup, and perhaps some parse code cleanup before making the release. H To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libbind, etc.
I believe an upgrade to the eventlib is coming Real Soon Now. I'm not sure about this - it might have been the logging module. H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DEVFS, the time has come...
Also the eth[0..x] thing means you can replace your ethernet card with a new one of a different type without having to look through your config code for references to ed0 or whatever. Just to ask, what happens when the probe order changes and your multiple NICs start popping up on the wrong eth port? This may be *much* more difficult when one of several cards die (how do you know which one broke?) and then you replace it and discover the new probe order is different... Or will be be able to wire them down in the config file (which will at least address part of the problem)? H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NTP nanokernel support (experimental)
I just got a new set of PARSE patches from Frank Kardel, and I'm waiting for Dave Mills to give me the go-ahead to commit them. Dave is chasing some possible bugs and wanted a stable codebase for a while. H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
BitKeeper should be ready soon. Once it's been proven stable, might it be a better alternative to CVS? H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files)
As I understand it, BitKeeper is indeed based on SCCS, and is a superset of it. The performance hit of SCCS has been solved. There are several significant commercial users of BitKeeper waiting for the first production release, and Larry McVoy seems to be a bit of a maniac when it comes to things being production stable. He said that a CVS-BitKeeper conversion tool is not far off. I'm mostly interested in the lines of development features, the ability to check in various revisions of my *local* work, the ability to apply a patch set as an atomic unit, and several of the GUI tools. H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: BitKeeper (was Re: solid NFS patch #6 avail for -current - need testers files)
The folks who did BitKeeper have a compare/contrast section in their web page that talks about BitKeeper vs. CVS and Perforce. http://www.bitkeeper.com I'm running CVS at several places, and I'm going to try BitKeeper for a couple of projects. H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Announcing a new cvsup server - cvsup6.freebsd.org
Several questions. First, what's wrong with stamping the files in a mirror with the timestamp it has on the master? Second, how much work would it be to add, say, md5 checksums to CVS. Third, isn't the version number useful for something? Just some ramblings... H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: tcp_wrapper in contrib and ports?
My current source of confusion is with the tcpd from ports, which doesn't mention what level it is syslogging at: I can't find any of it's log messages... Try adding a '-v' to the syslogd startup (or '-vv'). Funny, that used to be documented in the man page... If that's not enough, add a '-d' so you can watch what happens. It shouldn't take long to find what you want. Checking the source, it looks like it uses LOG_MAIL as the facility. You can also use the ! stuff in syslog.conf - the tcp wrappers use the invoking program name to log stuff. H To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ntpd segfaults on start
Cy, On 9/6/2019 4:56 PM, Cy Schubert wrote: > ... > > For those who enable ASLR, a better workaround is, to add this to your > ntp.conf: > > rlimit memlock 64 > > Until a more precise default is determined. Should I change the default value for FreeBSD-12 to be 64 for now? I can get this change in place for the upcoming ntp-4.2.8p14 release, and we can change it later if needed. -- Harlan Stenn, Network Time Foundation http://nwtime.org - be a Member! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
