Re: [Fwd: Custom termcap entries and installworld]
Stephen Hurd wrote: 1) How do people cope with custom termcap entries? One workaround is to not modify /etc/termcap at all. Instead just store them in a file somewhere and (depending on your shell) do export TERMCAP=/my/custom/termcap Or even export TERMCAP=custom:my custom entry See the ENVIRONMENT section near the bottom of "man 3 curses". Hrm... I don't *think* this can be done by frobbing /etc/gettytab, but perhaps it can... I'll give it a shot. login.conf/.login_conf may help (to set environment variables before login shell starts, assuming that is what you need). But ~/.termcap should work regardless and will override termcap entries in the system termcap db. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [Fwd: Custom termcap entries and installworld]
1) How do people cope with custom termcap entries? One workaround is to not modify /etc/termcap at all. Instead just store them in a file somewhere and (depending on your shell) do export TERMCAP=/my/custom/termcap Or even export TERMCAP=custom:my custom entry See the ENVIRONMENT section near the bottom of "man 3 curses". Hrm... I don't *think* this can be done by frobbing /etc/gettytab, but perhaps it can... I'll give it a shot. Thanks for the reply. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panic: trying to sleep while sleeping is prohibited - USB network panic after ifconfig
Sleeping on "usbsyn" with the following non-sleepable locks held: exclusive sleep mutex in_multi_mtx r = 0 (0xc0acfbc0) locked @ /usr/src/sys/neti net/in.c:971 KDB: stack backtrace: kdb_backtrace(1,c27e5418,c27e7000,1,ccfe3a50) at kdb_backtrace+0x29 witness_warn(5,0,c0993d00,c09846cb) at witness_warn+0x18e msleep(c27ffb00,0,4c,c09846cb,0) at msleep+0x42 usbd_transfer(c27ffb00,ccfe3ab0,c0649b2d,c27ffb00,c24a1580) at usbd_transfer+0x1 21 usbd_sync_transfer(c27ffb00,c24a1580,ccfe3acc,c06c6ea4,c25d0a00) at usbd_sync_tr ansfer+0x11 usbd_do_request_flags_pipe(c257d600,c257d280,ccfe3b0c,ccfe3b0b,0) at usbd_do_req uest_flags_pipe+0x5d usbd_do_request_flags(c257d600,ccfe3b0c,ccfe3b0b,0,0) at usbd_do_request_flags+0 x20 usbd_do_request(c257d600,ccfe3b0c,ccfe3b0b) at usbd_do_request+0x1a aue_csr_read_1(c25d0a00,0) at aue_csr_read_1+0x50 aue_setmulti(c25d0a00,c280e280,c25d3000,ccfe3ba8,ccfe3b78) at aue_setmulti+0x4a aue_ioctl(c25d3000,80206931,0) at aue_ioctl+0x106 if_addmulti(c25d3000,ccfe3ba8,ccfe3ba4,ccfe3ba8,10,c0acfbc0,0,c09a3cd4,3cb) at i f_addmulti+0x1b8 in_addmulti(ccfe3bdc,c25d3000) at in_addmulti+0x69 in_ifinit(c25d3000,c27da500,c262dcd0,0,ccfe3c38) at in_ifinit+0x529 in_control(c28206f4,8040691a,c262dcc0,c25d3000,c27e7000) at in_control+0x882 ifioctl(c28206f4,8040691a,c262dcc0,c27e7000,0) at ifioctl+0x198 soo_ioctl(c2678c60,8040691a,c262dcc0,c2480780,c27e7000) at soo_ioctl+0x2db ioctl(c27e7000,ccfe3d04,3,2,286) at ioctl+0x370 syscall(3b,3b,3b,8056080,80583c0) at syscall+0x22f Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x28131603, esp = 0xbfbfe59c, ebp = 0xbfbfede8 --- panic: trying to sleep while sleeping is prohibited cpuid = 0 KDB: enter: panic [thread pid 13 tid 13 ] Stopped at kdb_enter+0x2b: nop More information (bt, bt all, show alllocks) can be found at http://www.pfsense.com/~sullrich/panics/usb_network_nic_panic.txt Let me know if you need any more information. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HylaFAX port not work but related to sendmail
Paul.LKW wrote: Dear all: Recently I installed HylaFAX port on 6.1 and find that the fax received (Fax is received in /var/hylafax/recvq and changed to tiff format) can not sent to specified email user and find the error log below: May 30 04:08:56 office sendmail[624]: k4TK8t7A000620: to=ee-fax, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=30505, dsn=5.3.0, stat=unknown mailer error 1 ^^^ Sendmail's configuration will be the problem. It isn't clear what you're trying to do here though so I can't make suggestions without seeing your .mc and knowing what your intention is (who is user ee-fax?). Sorry I haven't used any recent version of hylafax. Regards, DAvid ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HylaFAX port not work but related to sendmail
Dear all: Recently I installed HylaFAX port on 6.1 and find that the fax received (Fax is received in /var/hylafax/recvq and changed to tiff format) can not sent to specified email user and find the error log below: May 30 04:08:56 office sendmail[624]: k4TK8t7A000620: to=ee-fax, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=30505, dsn=5.3.0, stat=unknown mailer error 1 May 30 04:08:56 office sendmail[624]: k4TK8t7A000620: to=fax, delay=00:00:01, mailer=local, pri=30505, dsn=5.1.1, stat=User unknown May 30 04:08:56 office sendmail[626]: k4TK8t5k000626: from=fax, size=42953, class=0, nrcpts=1, msgid=<[EMAIL PROTECTED]>, relay= [EMAIL PROTECTED] May 30 04:08:56 office sendmail[633]: k4TK8t5k000626: to=ee-fax, delay=00:00:01, xdelay=00:00:00, mailer=local, pri=72953, dsn=5.3.0, stat=unknown mailer error 1 May 30 04:08:56 office sendmail[633]: k4TK8t5k000626: to=fax, delay=00:00:01, mailer=local, pri=72953, dsn=5.1.1, stat=User unknown May 30 04:08:56 office sendmail[633]: k4TK8u5j000633: Losing ./qfk4TK8u5j000633: savemail panic May 30 04:08:56 office sendmail[633]: k4TK8u5j000633: SYSERR(uucp): savemail: cannot save rejected email anywhere I thank this is the uucp problem and find freebsd-6.1 will not with uucp and installed freebsd-uucp but still get the same! I also find 'stat=User unknown' every time as system sent message to local user in just the user name format! What's wrong with 6.1 ? Thanks for your Help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
reproduceable kernel panic when trying to use tap0 interface (sparc64)
hello, im using 6_stable on sparc64 and get a 100% reproduceable kernel panic. it crashes when i try to usr/create the tap0 interface. (i discovered it when i tried to run openvpn). so i guess it may be the tap driver on sparc64. i can provice kernel core and offer my help. i wrote to the sparc64 mailinglist before but now i guess its better off here. regards, Michael Ortmann == how to reproduce the kernel panic == # cat /dev/zero >/dev/tap0 tap0: Ethernet address: 00:bd:00:02:10:00 panic: trap: memory address not aligned cpuid = 0 KDB: enter: panic [thread 449 tid 100044] Stopped at kdb_enter+0x3c: ta %xcc, 1 == uname -a = FreeBSD server5.q-fin 6.1-STABLE FreeBSD 6.1-STABLE #0: Sun May 28 01:53:54 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SERVER5 sparc64 == kernel conf == machine sparc64 cpu SUN4U ident SERVER5 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols # Platforms supported # At this time all platforms are supported, as-is. #optionsSCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler #optionsPREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #optionsMD_ROOT # MD is a potential root device #optionsNFSCLIENT # Network Filesystem Client #optionsNFSSERVER # Network Filesystem Server #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT #optionsMSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_GPT# GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. # To make an SMP kernel, the next line is needed options SMP # Symmetric MultiProcessor Kernel # Standard busses device ebus device isa device pci device sbus device central device fhc # Floppy drives #device fdc # SCSI Controllers device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse # syscons is the default console driver, resembling an SCO console device sc device creator # Creator, Creator3D and Elite3D framebuffers device splash # Splash screen and screen saver support options KBD_INSTALL_CDEV # install a CDEV entry in /dev #device ofw_console # Open Firmware console device # Builtin hardware device auxio # auxiliary I/O device device clkbrd # Clock Board (blinkenlight on Sun Exx00) device genclock# Generic clock interface device eeprom # eeprom (really a front-end for the MK48Txx) device mk48txx # Mostek MK48Txx clocks d
[chat] upgrade 5.5 -> 6.1 with success
Hello, Today I did a succesfull remote upgrade from 5.5 to 6.1 without going to single user. Nice work! Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kmem leak in tmpmfs?
On Mon, 29 May 2006, Ulrich Spoerlein wrote: Greg Rivers wrote: On Thursday 25 May 2006 19:43, Paul Allen wrote: From Jonathan Noack <[EMAIL PROTECTED]>, Thu, May 25, 2006 at 07:56:07PM -0400: I am currently running with the following in /etc/rc.conf and haven't experienced any problems: tmpmfs_flags="-S -o async" Is there a way to accomplish this with an fstab entry? md /tmpmfs rw,async,-s1024m,-S no,I don't think so. But surely it would be better to just fixup the standard mount -t path to not call mount_mfs... Actually there is a way. I too have not been satisfied with the tmpmfs features in rc, so for some time now I've simply created a hard link: cd /sbin && ln -f mdmfs mount_md and then used an entry like this in /etc/fstab: md /tmpmd rw,async,-Sp1777,-s768M 0 0 This works great for me. A simple patch to mtree could make this hard link part of the base system. Nothing else is needed. You should use the 'mfs' file system. This works out of the box: md /tmpmfs rw,-s256m,-S,-Otime,async,noatime 0 0 Ulrich Spoerlein Using 'mfs' as you suggest doesn't work; you'll only get a usage message when you try to mount: usage: mount_mfs -C [-lNU] [-a maxcontig] [-b block-size] [-c cylinders] [-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes] [-m percent-free] [-n rotational-positions] [-O optimization] [-o mount-options] [-s size] [-v version] md-device mount-point This is because not all mdmfs options are available in "mount_mfs compatibility" mode as described at the bottom of mdmfs(8). Conspicuously absent are -p, -S, and -w. With 'mfs', you can't turn off softupdates (ie. can't have async), and you can't set arbitrary modes and ownerships on the file system. Creating the "mount_md" hard link to mdmfs and using type 'md' in fstab allows you to use all the features of mdmfs. -- Greg ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
how can I tell if config-entry "device da0 at scbus0 target 0" is working?
Hello, this might be a stupid question, but how can I find out whether a 4.11 kernel configuration with device mpt0 device mpt1 device scbus0 at mpt0 bus 0 device scbus1 at mpt1 bus 0 device da0 at scbus0 target 0 device da1 at scbus0 target 1 device da2 at scbus0 target 2 device da3 at scbus1 target 9 device da4 at scbus1 target 10 device da5 at scbus1 target 11 device da6 at scbus1 target 12 is working correctly or not? For obvious reasons I don't want to attach another drive to test this ;-) Best regards, Holger Kipp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ciss0: ADAPTER HEARTBEAT FAILED? on a new bought HP dl360g3
I forgot to tell that after this kernel message appears the maschine is still pingable, but whatever needs disk access doesn't work including sshd login. Dennis Berger wrote: Hey list, after a few hours of uptime I get an highlighted kernelmessage. "ciss0: ADAPTER HEARTBEAT FAILED" yes this are capital chars. I wonder if this can be a driver problem or if it definitly a hardware failure. Server is a fresh HP DL360g3 sorry i can't attach a dmesg cause the machine don't boot anymore. stuck during bootloader with IO/ error. regards, Dennis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ciss0: ADAPTER HEARTBEAT FAILED? on a new bought HP dl360g3
Hey list, after a few hours of uptime I get an highlighted kernelmessage. "ciss0: ADAPTER HEARTBEAT FAILED" yes this are capital chars. I wonder if this can be a driver problem or if it definitly a hardware failure. Server is a fresh HP DL360g3 sorry i can't attach a dmesg cause the machine don't boot anymore. stuck during bootloader with IO/ error. regards, Dennis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kmem leak in tmpmfs?
Greg Rivers wrote: > On Thursday 25 May 2006 19:43, Paul Allen wrote: > > >From Jonathan Noack <[EMAIL PROTECTED]>, Thu, May 25, 2006 at > > > 07:56:07PM -0400: I am currently running with the following in > > > /etc/rc.conf and haven't experienced any problems: > > > tmpmfs_flags="-S -o async" > > > > Is there a way to accomplish this with an fstab entry? > > > > md /tmpmfs rw,async,-s1024m,-S > > > > no,I don't think so. But surely it would be better to just fixup the > > standard mount -t path to not call mount_mfs... > > > > Actually there is a way. I too have not been satisfied with the tmpmfs > features in rc, so for some time now I've simply created a hard link: > > cd /sbin && ln -f mdmfs mount_md > > and then used an entry like this in /etc/fstab: > > md /tmpmd rw,async,-Sp1777,-s768M 0 > 0 > > This works great for me. A simple patch to mtree could make this hard link > part of the base system. Nothing else is needed. You should use the 'mfs' file system. This works out of the box: md /tmpmfs rw,-s256m,-S,-Otime,async,noatime 0 0 Ulrich Spoerlein -- PGP Key ID: 20FEE9DD Encrypted mail welcome! Fingerprint: AEC9 AF5E 01AC 4EE1 8F70 6CBD E76E 2227 20FE E9DD Which is worse: ignorance or apathy? Don't know. Don't care. pgpySLY1X1gBs.pgp Description: PGP signature
Re: LOR in vnode interlock and system map
On Mon, May 29, 2006 at 12:09:24AM +0200, V??clav Haisman wrote: > See attached file. The kernel is todays CVS 6.1. > > -- > Vaclav Haisman > > > May 28 19:16:55 logout kernel: lock order reversal: > May 28 19:16:55 logout kernel: 1st 0xc3d4bb1c vnode interlock (vnode > interlock) @ /usr/src/sys/kern/vfs_subr.c:2218 > May 28 19:16:55 logout kernel: 2nd 0xc1043144 system map (system map) @ > /usr/src/sys/vm/vm_kern.c:295 > May 28 19:16:55 logout kernel: KDB: stack backtrace: > May 28 19:16:55 logout kernel: > kdb_backtrace(c081a0c7,c1043144,c0819bfa,c0819bfa,c082f5af) at > kdb_backtrace+0x2e > May 28 19:16:55 logout kernel: > witness_checkorder(c1043144,9,c082f5af,127,c08bdbc0) at > witness_checkorder+0x5ef > May 28 19:16:55 logout kernel: > _mtx_lock_flags(c1043144,0,c082f5af,127,c104e460) at _mtx_lock_flags+0x32 > May 28 19:16:55 logout kernel: > _vm_map_lock(c10430c0,c082f5af,127,c3375900,c3375900) at _vm_map_lock+0x37 > May 28 19:16:55 logout kernel: > kmem_malloc(c10430c0,1000,101,d5688afc,c0766493) at kmem_malloc+0x3a > May 28 19:16:55 logout kernel: > page_alloc(c104d300,1000,d5688aef,101,c05e0ed6) at page_alloc+0x27 > May 28 19:16:55 logout kernel: slab_zalloc(c104d300,101,c082ed67,8a2,80246) > at slab_zalloc+0xd3 > May 28 19:16:55 logout kernel: > uma_zone_slab(c104d300,1,c082ed67,8a2,c082ed67) at uma_zone_slab+0x112 > May 28 19:16:55 logout kernel: uma_zalloc_internal(c104d300,0,1,0,d5688b94) > at uma_zalloc_internal+0x41 > May 28 19:16:55 logout kernel: bucket_alloc(80,1,c082ed67,95e,105) at > bucket_alloc+0x3b > May 28 19:16:55 logout kernel: > uma_zfree_arg(c104dc00,c389712c,0,d5688bbc,c072e964) at uma_zfree_arg+0x253 > May 28 19:16:55 logout kernel: mac_labelzone_free(c389712c) at > mac_labelzone_free+0x22 > May 28 19:16:55 logout kernel: > mac_vnode_label_free(c389712c,c3d4baa0,d5688be8,c061aa00,c3d4baa0) at > mac_vnode_label_free+0x94 > May 28 19:16:55 logout kernel: > mac_destroy_vnode(c3d4baa0,0,c081e172,30a,c3d4baa0) at mac_destroy_vnode+0x18 > May 28 19:16:55 logout kernel: > vdestroy(c3d4baa0,d5688c1c,0,c3d4e9cc,c3d4e9cc) at vdestroy+0x60 > May 28 19:16:55 logout kernel: > vdropl(c3d4baa0,d5688c1c,c081e172,835,c08b1440) at vdropl+0x50 > May 28 19:16:55 logout kernel: vput(c3d4baa0,0,c082c8a2,df7,c09117a0) at > vput+0x1ae > May 28 19:16:55 logout kernel: handle_workitem_remove(c36de9e0,0,2,3b3,1) at > handle_workitem_remove+0x15a > May 28 19:16:55 logout kernel: > process_worklist_item(c35a0400,0,c082c8a2,348,4479db07) at > process_worklist_item+0x1e1 > May 28 19:16:55 logout kernel: > softdep_process_worklist(c35a0400,0,c082c8a2,2f2,3e8) at > softdep_process_worklist+0x73 > May 28 19:16:55 logout kernel: softdep_flush(0,d5688d38,c08150d4,31d,0) at > softdep_flush+0x193 > May 28 19:16:55 logout kernel: fork_exit(c0744170,0,d5688d38) at > fork_exit+0x78 > May 28 19:16:55 logout kernel: fork_trampoline() at fork_trampoline+0x8 > May 28 19:16:55 logout kernel: --- trap 0x1, eip = 0, esp = 0xd5688d6c, ebp = > 0 --- I already reported similar LOR to Jeff Roberson, when latest big pile of VFS fixes where to be MFCed. Try the following patch (note, to trigger the situation you need really high load, and, desirably, low amount of memory installed). My backtrace was almost identical, the difference is that your trace coming from softdepflush daemon, and mine comes from vnlru. lock order reversal: 1st 0xc1a018f0 vnode interlock (vnode interlock) @ /usr/home/kostik/work/b= sd/sys/kern/vfs_subr.c:2449 2nd 0xc0c43144 system map (system map) @ /usr/home/kostik/work/bsd/sys/vm/= vm_kern.c:295 KDB: stack backtrace: kdb_backtrace(0,,c06676b0,c0667700,c0636024) at 0xc049d3c9 =3D kdb_= backtrace+0x29 witness_checkorder(c0c43144,9,c061fe28,127) at 0xc04a80c2 =3D witness_check= order+0x582 _mtx_lock_flags(c0c43144,0,c061fe28,127) at 0xc047b998 =3D _mtx_lock_flags+= 0x58 _vm_map_lock(c0c430c0,c061fe28,127) at 0xc059eb46 =3D _vm_map_lock+0x26 kmem_malloc(c0c430c0,1000,101,c819fbe0,c059679f) at 0xc059e0d2 =3D kmem_mal= loc+0x32 page_alloc(c0c4d300,1000,c819fbd3,101,c06a3bf8) at 0xc0596bda =3D page_allo= c+0x1a slab_zalloc(c0c4d300,101,c0c4d300,c0647a64,c0c4e460) at 0xc059679f =3D slab= _zalloc+0x9f uma_zone_slab(c0c4d300,1,c0c4e468,0,c061f05a,8a2) at 0xc0597dec =3D uma_zon= e_slab+0xec uma_zalloc_internal(c0c4d300,0,1,0,c0c4dc48) at 0xc0598129 =3D uma_zalloc_i= nternal+0x29 bucket_alloc(80,1,c0c380a0,0,c19ab6a4) at 0xc0595eac =3D bucket_alloc+0x2c uma_zfree_arg(c0c4dc00,c19ab6a4,0) at 0xc0598483 =3D uma_zfree_arg+0x283 mac_labelzone_free(c19ab6a4,c1a01828,e8,c819fc9c,c0565ad2) at 0xc055dab3 = =3D mac_labelzone_free+0x13 mac_vnode_label_free(c19ab6a4,c1a01828,c819fcac,c04d8766,c1a01828) at 0xc05= 65aaa =3D mac_vnode_label_free+0x6a mac_destroy_vnode(c1a01828) at 0xc0565ad2 =3D mac_destroy_vnode+0x12 vdestroy(c1a01828,c1a01828,c819fcec,c04d8142,c1a01828) at 0xc04d8766 =3D vd= estroy+0x1c6 vdropl(c1a01828,7,a8,c0653ee0,c1a01828) at 0xc04dad1e =3D vdropl+0x3e vlrurecl
Re: [Fwd: Custom termcap entries and installworld]
Stephen Hurd wrote: > > > > > > 1) How do people cope with custom termcap entries? One workaround is to not modify /etc/termcap at all. Instead just store them in a file somewhere and (depending on your shell) do export TERMCAP=/my/custom/termcap Or even export TERMCAP=custom:my custom entry See the ENVIRONMENT section near the bottom of "man 3 curses". Graham ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
