[Bug 220884] syslogd doesn't include all files in include directories
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220884 Alexander Zagrebin changed: What|Removed |Added CC||a...@zagrebin.ru --- Comment #1 from Alexander Zagrebin --- Created attachment 185188 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185188&action=edit syslogd.c patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 220884] syslogd doesn't include all files in include directories
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220884 --- Comment #2 from Alexander Zagrebin --- Comment on attachment 185188 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185188 syslogd.c patch I can confirm that. There is bug in the usr.sbin/syslogd/syslogd.c An attached patch fixes issue. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 Mark Millard changed: What|Removed |Added CC||mar...@dsl-only.net --- Comment #1 from Mark Millard --- See bugzilla 206048 for more examples and notes. It is a long term issue, not new with 11.x . This submittal is a duplicate. There may be others besides 206048. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220971 exe...@gmail.com changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2060 ||48 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221367] i386 sanitizer runtimes not installed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221367 Bug ID: 221367 Summary: i386 sanitizer runtimes not installed Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: ema...@freebsd.org The 32-bit compat lib install is executed with MK_TOOLCHAIN=no as of r264930 https://reviews.freebsd.org/rS264930 which prevents the sanitizer runtimes from being installed. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221367] i386 sanitizer runtimes not installed during amd64 32-bit compat in make installworld
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221367 Ed Maste changed: What|Removed |Added CC||d...@freebsd.org, ||i...@freebsd.org Summary|i386 sanitizer runtimes not |i386 sanitizer runtimes not |installed |installed during amd64 ||32-bit compat in make ||installworld -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221367] i386 sanitizer runtimes not installed during amd64 32-bit compat in make installworld
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221367 --- Comment #1 from Ed Maste --- It seems just removing MK_TOOLCHAIN=no from Makefile.libcompat causes these additional files to be installed: ===> libc (install) ... install -o root -g wheel -m 444 libc_pic.a /usr/lib32/ ... ===> libclang_rt (install) ===> libclang_rt/include (install) install -C -o root -g wheel -m 444 /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/allocator_interface.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/asan_interface.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/common_interface_defs.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/coverage_interface.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/dfsan_interface.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/esan_interface.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/linux_syscall_hooks.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/lsan_interface.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/msan_interface.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/tsan_interface.h /usr/home/emaste/src/freebsd-wip/contrib/compiler-rt/include/sanitizer/tsan_interface_atomic.h /usr/lib/clang/5.0.0/include/sanitizer/ ===> libclang_rt/asan (install) install -C -o root -g wheel -m 444 libclang_rt.asan-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libclang_rt/asan-preinit (install) install -C -o root -g wheel -m 444 libclang_rt.asan-preinit-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libclang_rt/asan_dynamic (install) install -s -o root -g wheel -m 444 libclang_rt.asan-i386.so /usr/lib32/ install -o root -g wheel -m 444libclang_rt.asan-i386.so.debug /usr/lib/debug/usr/lib32/ ===> libclang_rt/asan_cxx (install) install -C -o root -g wheel -m 444 libclang_rt.asan_cxx-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libclang_rt/safestack (install) install -C -o root -g wheel -m 444 libclang_rt.safestack-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libclang_rt/stats (install) install -C -o root -g wheel -m 444 libclang_rt.stats-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libclang_rt/stats_client (install) install -C -o root -g wheel -m 444 libclang_rt.stats_client-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libclang_rt/ubsan_standalone (install) install -C -o root -g wheel -m 444 libclang_rt.ubsan_standalone-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libclang_rt/ubsan_standalone_cxx (install) install -C -o root -g wheel -m 444 libclang_rt.ubsan_standalone_cxx-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libclang_rt/profile (install) install -C -o root -g wheel -m 444 libclang_rt.profile-i386.a /usr/lib/clang/5.0.0/lib/freebsd/ ===> libelftc (install) ===> libpe (install) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221376] 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376 Bug ID: 221376 Summary: 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: v...@unislabs.com Created attachment 185211 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185211&action=edit dmesg with custom kernel 11.1 amd64. Few lines from dmidecode: Base Board Information Manufacturer: ASUSTeK Computer INC. Product Name: P5GD2-Deluxe Processor Information Socket Designation: Socket 775 Type: Central Processor Family: Pentium 4 Manufacturer: Intel ID: 43 0F 00 00 FF FB EB BF Signature: Type 0, Family 15, Model 4, Stepping 3 Version: Intel(R) Pentium(R) 4 CPU 3.00GHz Voltage: 1.4 V External Clock: 200 MHz Max Speed: 3600 MHz Current Speed: 3000 MHz Compiled self with option CPUTYPE?=nocona in /etc/make.conf GENERIC kernel run fine (dmesg.good). Without it during boot system freeze or freeze for 1 minute and then reboot in 90% tries after detect cd0 (no real dmesg, but I edit good dmesg to look same as real messages in console - dmesg.bad). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221376] 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376 --- Comment #1 from v...@unislabs.com --- Created attachment 185212 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185212&action=edit "bad" dmesg -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221350] Unable to boot/install on HPE Proliant MicroServer Gen10 (AMD Opteron X3000): Hangs/Panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 --- Comment #4 from Rafal Lukawiecki --- Following suggestion by Miroslav Lachman I have tested a few other releases of FreeBSD to see if this issue still persists and if it was a regression. Unfortunately, in all tests, 9.3-12.0-CURRENT, I get exactly the same error. To be precise, these are the versions that I have tested: FreeBSD-9.3-RELEASE-amd64-memstick.img FreeBSD-11.1-RELEASE-amd64-memstick.img FreeBSD-11.1-STABLE-amd64-20170807-r322164-memstick.img FreeBSD-12.0-CURRENT-amd64-20170807-r322167-memstick.img -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 11294] [patch] logger(1) direct logging to other hosts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=11294 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org Resolution|--- |FIXED Status|In Progress |Closed --- Comment #6 from Eugene Grosbein --- logger(1) got "-h" option long time ago. An idea of implementing this in a library got no attention (read: patch) over 10 years. There is no point in keeping this PR open for another decade. If one has an implementation, please fill new PR for a library enhancement. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 11294] [patch] logger(1) direct logging to other hosts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=11294 Mikhail T. changed: What|Removed |Added Resolution|FIXED |--- Status|Closed |Open --- Comment #7 from Mikhail T. --- (In reply to Eugene Grosbein from comment #6) > An idea of implementing this in a library got no attention (read: patch) over > 10 years. There is no point in keeping this PR open for another decade. If > one has an implementation, please fill new PR for a library enhancement. What? My 18 year-old patch does modify libc/gen/syslog.c adding two new library functions: syslogh and vsyslogh -- including man-page additions documenting both. The ticket's very first comment mentions this, as do some of the follow-up comments. How could you have missed that?.. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 14562] ioctl() codes should be provided for ejecting all removables
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=14562 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org Status|In Progress |Closed Resolution|--- |Overcome By Events --- Comment #5 from Eugene Grosbein --- The request got no attention for 18 years. And we now have CAM layer working not only for SCSI devices. And floppy drives are not so topical anymore. So close this. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 18909] select(2) timeout limited to 100000000 seconds
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=18909 Eugene Grosbein changed: What|Removed |Added Status|In Progress |Closed CC||eu...@freebsd.org Resolution|--- |FIXED --- Comment #7 from Eugene Grosbein --- FreeBSD 11.1/i386 does not have this problem anymore. That is, select(2) does not return EINVAL if a timeout is specified for longer than 1 seconds. Close this after 17 years. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221376] 11.1-RELEASE amd64: GENERIC kernel compiled without any CPUTYPE?= in /etc/make.conf fail to boot, but with CPUTYPE?=nocona it work fine
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221376 --- Comment #2 from v...@unislabs.com --- GENERIC 11.0 from installation media boot fine. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 19402] Signals 127 and 128 cannot be detected in wait4() interface
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=19402 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org Status|In Progress |Closed Resolution|--- |FIXED --- Comment #9 from Eugene Grosbein --- Closed at submitter's request (SIGRTMAX is 126). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 19573] Dot Files for Optional Shells
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=19573 Eugene Grosbein changed: What|Removed |Added Resolution|--- |Rejected CC||eu...@freebsd.org Status|In Progress |Closed --- Comment #9 from Eugene Grosbein --- No progress for 17 years for this misfilled PR. It should be Ports PR since the beginning. Please fill new PR for corresponding port if this is still relevant. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 20529] [ti] gigabit cards fail to link
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=20529 Eugene Grosbein changed: What|Removed |Added Resolution|--- |Overcome By Events CC||eu...@freebsd.org Status|In Progress |Closed --- Comment #11 from Eugene Grosbein --- As comment #7 says, originator is not in position to deal with the problem anymore. Close this after 15 years of inactivity. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 11294] [patch] logger(1) direct logging to other hosts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=11294 --- Comment #8 from Eugene Grosbein --- (In reply to Mikhail T. from comment #7) Sorry, misses that indeed. Would you like to re-format your patch for modern code base? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 11294] [patch] logger(1) direct logging to other hosts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=11294 --- Comment #9 from Mikhail T. --- (In reply to Eugene Grosbein from comment #8) > Would you like to re-format your patch for modern code base? That would have to wait for a weekend... Meanwhile could you look at Bug #210537, where I have just done a similar refreshening? Thanks! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 210537] [patch] [feature request] set MIME type in cron-generated e-mails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210537 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org --- Comment #5 from Eugene Grosbein --- While the intention is good and proposed feature would be useful, the solution has are some rough edges. First, it's not very flexible to implement this as global option. You could easily make it per-crontab depending on environment variable like CONTENT_TYPE. Cron already looks at per-crontab MAILTO environment variable, why not look at CONTENT_TYPE? Then, cutting contents at first 1024 bytes embedded in the code is error-prone. Note well: libmagic has MAGIC_PARAM_REGEX_MAX==8192 currently. I'd suggest "CONTENT_TYPE=libmagic:1024" format when ":1024" part would be optional to redefine default of MAGIC_PARAM_REGEX_MAX. Also, I would not be so sure about "Content-Transfer-Encoding: 8bit" header. 8bit does not mean "any data". According to RFC 2045 https://www.ietf.org/rfc/rfc2045.txt , it means short (998 octets or less) text strings without null bytes and CR/LF octets in CRLF sequences only. If the body contains binary data, the "binary" Content-Transfer-Encoding token must be used. Mentioned PNG would violate "8bit" for sure. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 210537] [patch] [feature request] set MIME type in cron-generated e-mails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210537
--- Comment #6 from Eugene Grosbein ---
Also, file/libmagic is contributed software with CDDL license and we have
src.conf(5) knob WITHOUT_FILE to build system without this dependency. It is
important for many reasons including embedded friendyness to minimize size of
compiled code, so please make sure you respect WITHOUT_FILE and make your
changes compile-time conditional, f.e:
.if ${MK_FILE} != "no"
CFLAGS+=-DLIBMAGIC
.endif
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029 --- Comment #67 from Nils Beyer --- (In reply to Nils Beyer from comment #66) well, it seems that we have to RMA our CPUs after all: https://community.amd.com/message/2816858#comment-2816858 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221379] bsdinstall(8): Installer doesn't support default router outside local subnet
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221379 Bug ID: 221379 Summary: bsdinstall(8): Installer doesn't support default router outside local subnet Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: nrg_freebsd-b...@voidptr.de *Problem:* When the default gateway isn't contained in the subnet described by the local system's IP address and Subnet mask, bsdinstall(8) fails when it tries to add the default route, throwing the user back to the start of the install process. *Background:* IPv4 exhaustion has led some server providers to use rather questionable networking hacks to conserve IP space — namely, using gateway addresses outside the local subnet so the first address on the local subnet (x.x.x.1) doesn't have to be a router and can be used for customer machines instead. I'm currently seeing this on a KVM virtual machine from OneProvider (an Online.net reseller), but apparently OVH, Hetzner, and a bunch of smaller players do the same thing. My (slightly anonymized) network config: vtnet0: inet 195.154.123.234 netmask 0x broadcast 195.154.123.234 DestinationGatewayFlags Netif Expire default62.210.112.1 UGS vtnet0 62.210.112.1 52:54:00:00:82:41 UHS vtnet0 On a "normal" FreeBSD system, this can be achieved using an rc.conf something like this: ifconfig_vtnet0="inet 195.154.123.234 netmask 255.255.255.255" gateway_if="vtnet0" gateway_ip="62.210.112.1" static_routes="gateway default" route_gateway="-host $gateway_ip -interface $gateway_if" route_default="default $gateway_ip" Or temporarily using route(8): route add -host 62.210.112.1 -iface vtnet0 route add default 62.210.112.1 *Problem details:* The installer tries `route add default 62.210.112.1` directly, which of course fails because there is no route to 62.210.112.1 yet (see usr.sbin/bsdinstall/scripts/netconfig_ipv4:94 in base). Manually configuring the network from a shell doesn't work because `netconfig_ipv4` *always* re-configures (and thereby breaks) the network, even when nothing was changed. Responding "No" to "Would you like to configure IPv4 for this interface?" also doesn't help because something in bsdinstall(8) deletes the file behind the /etc/resolv.conf symlink every time the installer is launched. *Possible solutions (as far as I can see):* 1. As a workaround, we could at least stop bsdinstall from deleting/overwriting /etc/resolv.conf unless the user explicitly requests changes to the configuration. I've attached `always-write-resolvconf.patch` that gives the user an option to configure resolv.conf even when they skipped the configuration of network addresses and gateways. 2. Preferably, `netconfig_ipv4` should detect the gateway-outside-subnet scenario and generate a working rc.conf for it. This is a bit more involved, mainly because we need to implement a portable method of detecting if a given IP (the gateway) is inside a given network (the IP + subnet mask of the local machine). For this, I've built a truly awk-ful function — I had to reimplement bitwise operations from scratch because the awk version in FreeBSD base doesn't support the `and()` function… From there on it's just some additional shell code along the lines of `if ! router_inside_subnet; then route add -host $defaultrouter -iface $interface; fi; route add default $defaultrouter`. See `router-outside-subnet.patch` for that one. Probably needs some improvements in terms of readability. Testing should be less of an issue: the only finicky bit is the is-it-inside-subnet check, and if that crashes or gives a false-negative result, the script just adds a superfluous route that doesn't hurt anyone. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221379] bsdinstall(8): Installer doesn't support default router outside local subnet
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221379 Nils Steinger changed: What|Removed |Added CC||nrg_freebsd-b...@voidptr.de --- Comment #1 from Nils Steinger --- Created attachment 185214 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185214&action=edit Give the user an option to configure resolv.conf even when they skipped the configuration of network addresses and gateways -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221379] bsdinstall(8): Installer doesn't support default router outside local subnet
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221379 --- Comment #2 from Nils Steinger --- Created attachment 185215 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185215&action=edit Detect the gateway-outside-subnet scenario and generate a working rc.conf for it -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221379] bsdinstall(8): Installer doesn't support default router outside local subnet
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221379
--- Comment #3 from Nils Steinger ---
And then…
*Same issue with IPv6:*
`netconfig_ipv6` has the exact same problem and should receive similar
treatment.
However, my solution for IPv4 can't be applied verbatim because awk loses
accuracy when going up to 2^64:
% awk 'BEGIN {print(2^64)}'
18446744073709551616
% awk 'BEGIN {print(2^64-1)}'
18446744073709551616
% awk 'BEGIN {print(2^64-1000)}'
18446744073709551616
So we would have to find another way to to subnet parsing for IPv6.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 210537] [patch] [feature request] set MIME type in cron-generated e-mails
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210537 Mikhail T. changed: What|Removed |Added CC||m...@aldan.algebra.com --- Comment #7 from Mikhail T. --- (In reply to Eugene Grosbein from comment #5) I don't think, it should be a per-user option, because the added behavior does not merely add a feature -- it fixes a bug. A non-textual e-mail without a MIME-type is invalid and a program generating it is buggy... I'm hoping, once merged and tested "in the wild", the change will become permanent . Which means, I need to reverse the meaning of the new `-M' option. (In reply to Eugene Grosbein from comment #6) > make sure you respect WITHOUT_FILE and make your changes compile-time > conditional Ah, didn't know about it. Yes, will do -- a few #ifdefs will be necessary... Thanks for the review. I'll get back to it... -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029 --- Comment #68 from Conrad Meyer --- Just curious -- what model Ryzens are you seeing the faults on? I'm curious to what extent better binning affects the symptoms. Are R3s and R5s mostly the affected? Or do R7s see the problem too? Are 1800X less susceptible than 1700, 1700X? Etc. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029 --- Comment #69 from Nils Beyer --- (In reply to Conrad Meyer from comment #68) - the poudriere segfault/unable to rename/kernel panic Ryzen is a 1700 stock, manufacturing date: UA 1707PGT - the unable to rename/never poudriere tested Ryzen is a 1700 stock, manufacturing date: -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
