MVB
ÂÛ ÇÍÀÅÒÅ ×ÒÎ ÒÀÊÎÅ ÃÐÈÍÌÅÉË ? ÝÒÎ ÀÊÖÈÎÍÅÐÍÛÉ ØÀÍÒÀÆ, ÀÃÐÅÑÑÈÂÍÎÅ ÏÎÃËÎÙÅÍÈÅ ÏÐÅÄÏÐÈßÒÈÉ, ÏÅÐÅÕÂÀÒ ÓÏÐÀÂËÅÍÈß ÀÎ, ÑÀÁÎÒÀÆ ÐÀÁÎÒÛ ÏÐÅÄÏÐÈßÒÈß, ÓÑÒÐÀÍÅÍÈÅ ÊÎÍÊÓÐÅÍÒÎÂ È ÌÍÎÃÎÅ ÄÐÓÃÎÅ, ÍÎ ÇÀÌÅÒÜÒÅ, ÊÀÊ ÍÅ ÏÀÐÀÄÎÊÑÀËÜÍÎ, ÂѨ  ÐÀÌÊÀÕ ÇÀÊÎÍÀ! Åñëè åù¸ 5-10 ëåò íàçàä ÿâëåíèå ãðèíìåéëà áûëî ïðåðîãàòèâîé çàïàäíîé ýêîíîìèêè, òî ñåé÷àñ ìîæíî óòâåðæäàòü, ÷òî ðîññèéñêèé ãðèíìåéë óæå âñòàë íà íîãè (ïðèíöèï ñîçäàíèÿ èìïåðèè Ðóññêèé Àëþìèíèé), õîòÿ â íàøåé ñòðàíå ïðèñóòñòâóåò è ãîñóäàðñòâåííûé ãðèíìåéë (ÍÒÂ). Âû õîòèòå çíàòü îá ýòîì áîëüøå ? Õîòèòå çíàòü, êàê îòáèðàþòñÿ ïðåäïðèÿòèÿ, íåîæèäàííî ìåíÿåòñÿ ðóêîâîäñòâî ÀÎ, êàê äåëàþòñÿ ïðåäëîæåíèÿ îò êîòîðûõ íåëüçÿ îòêàçàòüñÿ, êàê áîãàòûå ñòàíîâÿòñÿ áåäíûìè è êàê çàùèòèòñÿ îò íåäðóæåñòâåííûõ äåéñòâèé, òîãäà Âàì íåîáõîäèìî çíàòü, ÷òî 3 èþíÿ îòêðûëñÿ ôîðóì ÀÊÖÈÎÍÅÐÍÛÅ ÂÎÉÍÛ, ïîñâÿù¸ííûé òåìàòèêå ãðèíìåéëà íà ñàéòå ÈÍÂÅÑÒÈÖÈÎÍÍÛÅ ÐÅÑÓÐÑÛ www.mvb.ru . Íà ôîðóìå Âû ìîæåòå ïîëó÷èòü áåñïëàòíûå êîíñóëüòàöèè îò þðèñòîâ, ñïåöèàëèçèðóþùèõñÿ íà ãðèíìåéëå. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux JDK 1.3 and hotspot (native threads)
At Mon, 30 Apr 2001 11:59:38 +0200, Georg-W. Koltermann [EMAIL PROTECTED] wrote: On Fri, Apr 27, 2001 at 09:32:58PM -0400, Andrew Gallatin wrote: Georg-W. Koltermann writes: ... In order to get real performance I would like to run either the SUN JDK with -hotspot, or the IBM 1.3 JVM. Both of these use native linux threads. With a recent -current I can successfully execute small JAVA test programs, but when I start a real application (e.g. Together from togethersoft.com), it fails with a core dump. ... Also, are there any non commercial apps that demonstrate the problem? Or at least things that I don't have to sign my life away to get access to? Hi Andrew, I just tried Forte for Java 3.0 Early Access, and it shows the above problem quite easily during startup. I ran it with truss(1), and the last part of the output is: linux_kill(0x15bc,0x20) = 2 (0x2) linux_brk(0x8232000) = 1 (0x1) linux_rt_sigprocmask(0x2,0x0,0xbfbfc73c,0x8) = 4 (0x4) write(4,0xbfbfc728,148) = 3 (0x3) linux_rt_sigprocmask(0x2,0x0,0xbfbfc6a8,0x8) = 4 (0x4) SIGNAL 32 SIGNAL 32 SIGNAL 32 linux_rt_sigsuspend(0xbfbfc6a8,0x8) ERR#4 'Interrupted system call' linux_sigreturn(0xbfbfc3a0) ERR#4 'Interrupted system call' linux_sched_getscheduler(0x15c2) ERR#1 'Operation not permitted' linux_kill(0x15c2,0x20) = 2 (0x2) linux_kill(0x15c2,0x20) = 2 (0x2) getpid() = 0 (0x0) linux_mmap(0xbfbfc9bc) = 1 (0x1) mprotect(0xbfa0e000,0x2000,0x0) = 3 (0x3) linux_mmap(0xbfbfc9bc) = 1 (0x1) linux_sigaltstack(0xbfbfc9f8,0x0)= 2 (0x2) -- System info linux_rt_sigprocmask(0x1,0xbfbfc968,0x0,0x8) = 4 (0x4) linux_sched_getscheduler(0x15b9) ERR#1 'Operation not permitted' Product Version = Forte for Java, CE v. 3.0 (Build 010523) IDE Versioning= IDE/1 spec=1.2.1 impl=010523 Operating System = Linux version 2.2.12 running on i386 Java; VM; Vendor = 1.3.1; Java HotSpot(TM) Client VM 1.3.1-b24; Sun Microsystems Inc. Java Home = /opt/jdk1.3.1/jre System Locale = en_US (f4j_ce) Home Dir; Current Dir = /home/hunter/gwk; /home/hunter/gwk IDE Install; User Dir = /opt/forte30; /home/hunter/gwk/ffjuser30 CLASSPATH = /opt/forte30/lib/patches/openide-compat.jar:/opt/forte30/lib/ext/bsh-1_0-fj.jar:/opt/forte30/lib/ext/cmd.jar:/opt/forte30/lib/ext/cosnaming.jar:/opt/forte30/lib/ext/dd2beans.jar:/opt/forte30/lib/ext/ddl.jar:/opt/forte30/lib/ext/fjscript.jar:/opt/forte30/lib/ext/fscontext.jar:/opt/forte30/lib/ext/idlcompilers.jar:/opt/forte30/lib/ext/jaas.jar:/opt/forte30/lib/ext/jaxp.jar:/opt/forte30/lib/ext/jh.jar:/opt/forte30/lib/ext/jndi.jar:/opt/forte30/lib/ext/ldap.jar:/opt/forte30/lib/ext/ldapbp.jar:/opt/forte30/lib/ext/logger.jar:/opt/forte30/lib/ext/nis.jar:/opt/forte30/lib/ext/openorb-1.0.2.jar:/opt/forte30/lib/ext/oracle.jar:/opt/forte30/lib/ext/parser.jar:/opt/forte30/lib/ext/pbembeddedeval.jar:/opt/forte30/lib/ext/providerutil.jar:/opt/forte30/lib/ext/regexp.jar:/opt/forte30/lib/ext/rmi-ext.jar:/opt/forte30/lib/ext/rmiregistry.jar:/opt/forte30/lib/ext/sax2.jar:/opt/forte30/lib/ext/servlet.jar:/opt/forte30/lib/ext/xerces.jar:/opt/forte30/lib/ext/jdbc20x.zip:/opt/forte30/lib/locale/core_f4j.jar:/opt/forte30/lib/locale/core_f4j_ce.jar:/opt/forte30/lib/locale/openide_f4j.jar:/opt/forte30/lib/core.jar:/opt/forte30/lib/openide-fs.jar:/opt/forte30/lib/openide-nodes.jar:/opt/forte30/lib/openide-util.jar:/opt/forte30/lib/openide.jar:/opt/jdk1.3.1/lib/dt.jar:/opt/jdk1.3.1/lib/htmlconverter.jar:/opt/jdk1.3.1/lib/tools.jar --- linux_rt_sigprocmask(0x2,0x0,0xbfbfc9cc,0x8) = 4 (0x4) Unexpected Signal : 11 occurred at PC=0x806535a Function name=(N/A) Library=(N/A) NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: Dynamic libraries: Can not get information for pid = 5570 Local Time = Fri Jun 8 23:14:38 2001 Elapsed Time = 2 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002CC # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode) # # An error report file has been saved as hs_err_pid5570.log. # Please refer to the file for
Re: PCCARD and -current
In message [EMAIL PROTECTED] Julian Elischer writes: : Failed to allocate IRQ for Linksys Add -I to your pccardd_flags in rc.conf. Others have suggested '-I -i 11' for your case. Also, it is very important that you install a new pccardd too. Otherwise, you may find your system hanging when the card is reset after power on, but before it is assigned resources. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Seth Kingsley writes: : Sorry, I guess maybe this directive is counter-intuative. It supposed to : be a list of the free irq's in the system for pccardd to use with : inserted pccards when configuring them. Trying to use the irq that the : cardbus bridge already has will definetly result in a resource : allocation failure. But it shouldn't with the pci attachment in very current currents :-) Actaully, the irq in pccard.conf will likely be ignored in the not too distant future. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
I got the same results as you. It eventually worked when I copied the entry matching my card into /etc/pccard.conf and hard-wired the irq as the same as the pcic device (9 in my case): $ cat /etc/pccard.conf irq 9 card Lucent Technologies WaveLAN/IEEE config auto wi 9 insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop With a ? instead of the 9 on the config line, I got an irq resource allocation failure. Go figure ! So the question remains.. where was I supposed to change the interrupt mentionned in the UPDATING entry.. if not in the pccard.conf, then where? I certainly get the 'hangs' mentionned as being a symptom of NOT doing it.. Warner? On Fri, 8 Jun 2001, Mike Smith wrote: On Fri, Jun 08, 2001 at 11:19:10AM -0700, Julian Elischer wrote: kernel: pcic1: TI PCI-1225 PCI-CardBus Bridge irq 11 at device 4.1 on pci0 in pccard.conf I had irq 11 is this not what I was supposed to do? Sorry, I guess maybe this directive is counter-intuative. It supposed to be a list of the free irq's in the system for pccardd to use with inserted pccards when configuring them. Trying to use the irq that the cardbus bridge already has will definetly result in a resource allocation failure. Er, well, it shouldn't, and more to the point, in most modern laptops you *have* to share the two. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mozilla 0.9 and 0.9.1 with freebsd
On Sat, Jun 09, 2001 at 09:27:45PM +0200, Szilveszter Adam wrote: Hello, On Sat, Jun 09, 2001 at 11:24:42PM +0400, Juriy Goloveshkin wrote: Hello, Is mozilla built in current? I tried to build it with /usr/ports/www/mozilla and from only tar-ball. Building stopped. What's wrong? THe problem is that -CURRENT's VM options are set for debugging which means that some (not well written) programs will suffer. It seems that on some configurations you need to set MALLOC_OPTIONS to j in order to be able to build Mozilla. However it does not occur on all systems (according to the freebsd-mozilla ml) so it may be related to the amount of RAM, swap etc in the system. It certainly needs this flag on my machine. I hope that this helps somewhat... thanks. it works! -- bye Juriy Goloveshkin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Couple Giant not locked at vm_object.c:261 panics I had today....
Backtraces posted here in hopes they might enlighten someone.
This is with kernel source from June 6 (specifically,
Sticky Date: 2001.06.06.22.16.24 according to cvs status). The machine
is a dual PII/400; dmesg follows the backtraces from the two panics. If you
want more information from these two core files, please let me know.
Note that the first panic is somewhat muddled by the fact that, while
syncing disks from the vm_object.c panic, it apparently paniced again with
Giant locked at i386/trap.c:1153. That probably confuses the issue
greatly.
P.S. Stupid -current question: How does one tell what process was running
that triggered a panic? This used to be findable with p *curproc in
gdb, but that doesn't seem to work anymore.
Script started on Sat Jun 9 16:02:27 2001
You have mail.
ichotolot# gdb -k kernel.debug vmcore.19
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-unknown-freebsd...
IdlePTD 6516736
initial pcb at 529440
panicstr: witness_restore: lock (sleep mutex) Giant not locked
panic messages:
---
panic: mutex Giant not owned at ../../vm/vm_object.c:261
cpuid = 1; lapic.id = 0100
boot() called on cpu#1
syncing disks... exclusive (sleep mutex) Giant (0xc0576ca0) locked @
../../i386/i386/trap.c:1153
exclusive (spin mutex) sched lock (0xc05763e0) locked @ ../../kern/kern_mutex.c:312
panic: witness_restore: lock (sleep mutex) Giant not locked
cpuid = 1; lapic.id = 0100
boot() called on cpu#1
Uptime: 2d2h35m38s
dumping to dev da0s2b, offset 270336
dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109
108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83
82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54
53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25
24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
---
#0 dumpsys () at ../../kern/kern_shutdown.c:478
478 if (dumping++) {
(kgdb) p curproc
No symbol curproc in current context.
(kgdb) bt
#0 dumpsys () at ../../kern/kern_shutdown.c:478
#1 0xc026b35f in boot (howto=260) at ../../kern/kern_shutdown.c:321
#2 0xc026b7d1 in panic (fmt=0xc0488ae5 %s: lock (%s) %s not locked)
at ../../kern/kern_shutdown.c:600
#3 0xc02878a5 in witness_restore (lock=0xc0576ca0,
file=0xc048bc20 ../../kern/vfs_bio.c, line=1827)
at ../../kern/subr_witness.c:1297
#4 0xc0273836 in msleep (ident=0xc054eaec, mtx=0x0, priority=68,
wmesg=0xc048c09e psleep, timo=100) at ../../kern/kern_synch.c:500
#5 0xc02ab0a5 in buf_daemon () at ../../kern/vfs_bio.c:1883
#6 0xc025af78 in fork_exit (callout=0xc02aaf20 buf_daemon, arg=0x0,
frame=0xc80cbfa8) at ../../kern/kern_fork.c:727
(kgdb) fr 6
#6 0xc025af78 in fork_exit (callout=0xc02aaf20 buf_daemon, arg=0x0,
frame=0xc80cbfa8) at ../../kern/kern_fork.c:727
727 callout(arg, frame);
(kgdb) l
722 * cpu_set_fork_handler intercepts this function call to
723 * have this call a non-return function to stay in kernel mode.
724 * initproc has its own fork handler, but it does return.
725 */
726 KASSERT(callout != NULL, (NULL callout in fork_exit));
727 callout(arg, frame);
728
729 /*
730 * Check if a kernel thread misbehaved and returned from its main
731 * function.
(kgdb) l
732 */
733 PROC_LOCK(p);
734 if (p-p_flag P_KTHREAD) {
735 PROC_UNLOCK(p);
736 mtx_lock(Giant);
737 printf(Kernel thread \%s\ (pid %d) exited prematurely.\n,
738 p-p_comm, p-p_pid);
739 kthread_exit(0);
740 }
741 PROC_UNLOCK(p);
(kgdb) p frame
$1 = (struct trapframe *) 0xc80cbfa8
(kgdb) p frame[0]
$2 = {tf_fs = 0, tf_es = 0, tf_ds = 0, tf_edi = 0, tf_esi = 0, tf_ebp = 0,
tf_isp = 0, tf_ebx = 0, tf_edx = 1, tf_ecx = 0, tf_eax = 0, tf_trapno = 0,
tf_err = 0, tf_eip = 0, tf_cs = 0, tf_eflags = 0, tf_esp = 0, tf_ss = 0}
(kgdb) fr 5
#5 0xc02ab0a5 in buf_daemon () at ../../kern/vfs_bio.c:1883
1883tsleep(bd_request, PVM, qsleep, hz / 2);
(kgdb) l
1878/*
1879 * We couldn't find any flushable dirty buffers but
1880 * still have too many dirty buffers, we
1881 * have to sleep and try again. (rare)
1882 */
1883tsleep(bd_request, PVM, qsleep, hz / 2);
1884
Re: panic: ufs_extattr_uepm_destroy: not initialized
Joerg Wunsch [EMAIL PROTECTED] wrote: It /only/ happens after a mount -a, not after just mounting /tmp only. No idea why, the only `obscure' filesystems i've got are procfs and portalfs. portalfs indeed seems to be the culprit for leaving an unreferenced file in /tmp. However, the panic for forcibly umounting /tmp then clearly belongs to the extattr code. Removed the option from my config again (i just wanted to give ACLs a try only anyway), and now i'm living without that panic again. -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
world broken by ipfilter move
Script started on Sun Jun 10 08:55:08 2001 ttyp0:bde@gamplex:/usr/src/usr.bin/kdump make depend sh /usr/src/usr.bin/kdump/mkioctls /usr/include ioctl.c In file included from :66: /usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/include/pccard/cardinfo.h:81: warning: this is the location of the previous definition rm -f .depend mkdep -f .depend -a-I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. /usr/src/usr.bin/kdump/kdump.c ioctl.c /usr/src/usr.bin/kdump/../ktrace/subr.c ioctl.c:18: netinet/ip_compat.h: No such file or directory ioctl.c:19: netinet/ip_fil.h: No such file or directory ioctl.c:20: netinet/ip_auth.h: No such file or directory ioctl.c:21: netinet/ip_nat.h: No such file or directory ioctl.c:22: netinet/ip_frag.h: No such file or directory ioctl.c:23: netinet/ip_state.h: No such file or directory In file included from ioctl.c:96: /usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/include/pccard/cardinfo.h:81: warning: this is the location of the previous definition mkdep: compile failed *** Error code 1 Stop in /usr/src/usr.bin/kdump. ttyp0:bde@gamplex:/usr/src/usr.bin/kdump exit Script done on Sun Jun 10 08:55:13 2001 Everything thet uses the ipfilter headers is similarly broken. This is because I use SHARED=symlinks, and src/include/Makefile doesn't install the ipfilter headers in this case. Nor could it, since installing them would spam the source tree. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCCARD and -current
In message [EMAIL PROTECTED] Brian Somers writes: : With a ? instead of the 9 on the config line, I got an irq resource : allocation failure. Go figure ! Add -I to pccardd_flags. warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
no subject
I installed a corpsys 40 gig ide into my Mac G4. The drive sends an error message that the proper drivers have not been installed. I have had no luck contacting the manufacturer can you help me? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FORTH: Modifying loader...
Daniel C. Sobral wrote: Actually, : Short-Appplication . Hello World! cr ; might even work... :-) I've been waiting for a FORTH-geek to pop his head up; I have most of nextboot reimplemented... I've added fwrite and flseek verbs. I've thought about kidnapping an astronomer. 8-). The current problem is that the biosdisk.c doesn't contain write code, and that the libstand code wouldn't call it if it did. I'm not really interested in creating or extending files, and with those restrictions, it seems possible to do the job. Is anyone interested in helping out with the code? The basic plan is to take a file that has: A A A B B B\n and rewrite it as: A A B B B A\n (a rotor; slightly different than the original nextboot, but acceptable, given the constraint of keeping the file exactly the same length), and then use the first string A (might be disk1s1a:/kernel) to set curr_dev to the disk1s1a: part, and then try to boot the /kernel part. I'll write the user space utility, and I'm willing to do the UFS code as well, but it's been 15 years since I've done FORTH, and I'm not too confident of the VM86 calls in biosboot.c for writing, either. We could guard the code against extending the file, and that's enough to ignore the allocation problems without damaging any FS to which it is applied, since we would only rewrite existing disk blocks. The fread verb already returns the exact length of the file, so that's not a problem, either. So do we have a BIOS write hacker and a FORTH hacker in the house? Worse comes to worse, I can find a sacrificial disk and do the BIOS write stuff myself, if I have to. Modified code for libstand to go back to CMU Mach, per the request, of course... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FORTH: Modifying loader...
I've been waiting for a FORTH-geek to pop his head up; I have most of nextboot reimplemented... I've added fwrite and flseek verbs. I've thought about kidnapping an astronomer. 8-). The current problem is that the biosdisk.c doesn't contain write code, and that the libstand code wouldn't call it if it did. I'm not really interested in creating or extending files, and with those restrictions, it seems possible to do the job. Is anyone interested in helping out with the code? I've wanted someone to fix the libstand filesystems to support overwrite for some time, so yes, I'd be happy to help here. The basic plan is to take a file that has: A A A B B B\n and rewrite it as: A A B B B A\n (a rotor; slightly different than the original nextboot, but acceptable, given the constraint of keeping the file exactly the same length), and then use the first string A (might be disk1s1a:/kernel) to set curr_dev to the disk1s1a: part, and then try to boot the /kernel part. I actually had a fairly different and more generic idea in mind; an 8k boot.variables file in /boot, which holds variables marked with 'save variable'. So you would do something like: set kernel_list=kernel.new,kernel.default,kernel.emergency set kernel_index=0 save kernel_list save kernel_index to set things up. If the format of the file was sensible, manipulating it from userspace would be trivial as well. I'll write the user space utility, and I'm willing to do the UFS code as well, but it's been 15 years since I've done FORTH, and I'm not too confident of the VM86 calls in biosboot.c for writing, either. I can't help with the FORTH, but I certainly know what needs to be done in biosdisk.c. Note that the SRM equivalent can't write to the disk, so this *won't* work for the Alpha. 8( Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
