FreeBSD 4.9-RC4 vs 5.1-CURRENT-20031021-JPSNAP

Hardware: Soekris Net4801 (ComBIOS 1.21), SanDisk 512MB Ultra Compact Flash Software: 5.1-CURRENT Symptom:ad0: FAILURE - SET_MULTI status=51READY,DSC,ERROR error=4ABORTED GEOM: create disk ad0 dp=0xc47ffb70 ad0: 488MB SanDisk SDFCH-512

current status of digi driver

While attempting to upgrade our comm servers from 7.4-RELEASE to 8.2-RELEASE, I discovered that the digi driver didn't make the grade. I searched the archives and found discussions in August 2008 concerning drivers that were disconnected for lack of MPSAFEness. The threads continued right up to

missing perl module (p5-Sys-Filesystem) for amd64

This appears to be a problem only in 9.0-current and 9.0-beta1. The perl module p5-Sys-Filesystem appears in i386 but not in amd64. It is part of our automated installation. Thanks in advance for any information you can provide, for assisting with the proper resolution of this problem or for

pucdata.c addition

(2 ports) is expandable to 4 ports and registers four uart devices with FreeBSD (even without the expansion chip). The chipset is by Oxford Semicondutor (OX16PCI954). The card has a non-standard clock. Thanks. David Boyd ___ freebsd-current@freebsd.org

new dialog/libdialog testing

Having some time to test 9.0-CURRENT with the new dialog command has uncovered only one major omission (for us): prgbox/dialog_prgbox. This is used in most (if not all) of our installation/management scripts. Was prgbox omitted for any particular reason? I realize that change is inevitable. Is

pc-sysinstall and pxeboot

Has anyone noodled through the details of pxeboot and pc-sysinstall for automated installs? I have working configurations for pxeboot and sysinstall for 8.1-RELEASE and prior. What are the gotchas for 9.0-CURRENT? I have lots of testing time available. Thanks.

AUTOFS and NFS not playing together nicely

assistance that you may be able to supply. David Boyd. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: nmount, mountd drops high order MNT_xx flags during a mount update

. Thanks for the suggestion Doug, rick On 7 May 2015 at 02:10, Rick Macklem rmack...@uoguelph.ca wrote: David Boyd reported a problem to freebsd-current@ w.r.t. the MNT_AUTOMOUNTED flag getting cleared by mountd. http://docs.FreeBSD.org/cgi/mid.cgi

VM images for 12.0-CURRENT showing checksum failed messages

. This is easily fixed by "fsck -y /" in single-user mode during the boot process. I can test any updates at almost any time. Thanks. David Boyd. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freeb

12.0-CURRENT VM image won't mount USB flash drive

in any 10.4-STABLE or 11.1-STABLE VM images. The host system is CentOS EL7 7.1708. VirtualBox version is 5.2.6. The USB 3.0 controller uses a VIA chipset. System is for test purposes only, so it is easy to try anything that might help resolve this problem. Thanks. David Boyd <david.

VM images for 12.0-CURRENT have problem with USB 3.0 flash drives

-STABLE VM images. The host system is CentOS EL7 7.1708. VirtualBox version is 5.2.6. The USB 3.0 controller uses a VIA chipset. System is for test purposes only, so it is easy to try anything that might help resolve this problem. Thanks. David Boyd <david.boy...@twc.

12.0-CURRENT missing timezones

populated with directories. The only file present is "zone.tab". Thanks for looking into this. David Boyd <david.boy...@twc.com> ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To u

Re: 12.0-CURRENT missing timezones

On Fri, 2018-02-09 at 10:16 -0700, Warner Losh wrote: > On Fri, Feb 9, 2018 at 10:13 AM, Warner Losh <i...@bsdimp.com> wrote: > > On Fri, Feb 9, 2018 at 9:56 AM, David Boyd <david.boy...@twc.com> > > wrote: > > > In the most recent images for 12.0-CURRENT > &

13.0-CURRENT drops to debugger on shutdown with IPNAT enabled

the root of this problem. I have included screenshots of the debug output and a backtrace. Thanks. David Boyd. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail

Re: 13.0-CURRENT drops to debugger on shutdown with IPNAT enabled

On Mon, 2019-01-21 at 10:17 -0500, David Boyd wrote: > On Mon, 2019-01-21 at 10:37 +0100, Trond Endrestøl wrote: > > On Sun, 20 Jan 2019 13:09-0500, David Boyd wrote: > > > > > 13.0-CURRENT drops to debugger on shutdown with IPNAT enabled. > > >

Re: 13.0-CURRENT drops to debugger on shutdown with IPNAT enabled

On Mon, 2019-01-21 at 10:37 +0100, Trond Endrestøl wrote: > On Sun, 20 Jan 2019 13:09-0500, David Boyd wrote: > > > 13.0-CURRENT drops to debugger on shutdown with IPNAT enabled. > > > > Running in VirtualBox 6.0.2. > > > > The identical configuration

13.0-CURRENT oddity in output of dialog(1)

-RELEASE) releases. To recreate: cat /etc/rc.conf | dialog --programbox 23 76 No other problems have been observed in the dialog(1) utility. Thanks. David Boyd. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo

lsof hangs with latest 13.0-CURRENT snapshot

. Thanks. David Boyd. ___ 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"

Re: lsof hangs with latest 13.0-CURRENT snapshot

our lsof binary from? > > lsof has internal knowledge of kernel data structures > and must be compiled to match the running system. > > > > Thanks. > > David Boyd. lsof was installed via pkg install from pkg.freebsd.org. ___

New vm-image size is much smaller than previos

The vm-image for 13.0-CURRENT FreeBSD-13.0-CURRENT-amd64-20190503-r347033.vmdk is only 4.0 GB in size. Previous images were about 31.0 GB. This smaller image doesn't leave much room to add packages and other customizations. Thanks. David Boyd