panic: don't do that
Hi, After a migration of a complete / Filesystem with dump - restore. I made the mistake to already have a small new system on the new disk. So I decided to do a # cd / # restore urf root.dump I got at the end: /dev/ad0d: cannot create special file: File exists WARNING: Driver mistake: repeat make_dev(ad0s1) panic: don't do that Debugger(panic) Is this really a Driver mistake ? Or am I mistaken ? I guess we should do a # chflags nodump /dev during the install on CURRENT. Why has been /dev dumped anyway ? Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 061 826 93 00: +41 61 826 93 01 PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: don't do that
On Tue, 8 Jan 2002, Martin Blapp wrote: ... during the install on CURRENT. Why has been /dev dumped anyway ? I bet you have old /dev entries as a fallback left which got backed up. What do you see on a unmounted /dev? Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: don't do that
Hi, during the install on CURRENT. Why has been /dev dumped anyway ? I bet you have old /dev entries as a fallback left which got backed up. I guess no. This was a fresh CURRENT installation from November 2001. What do you see on a unmounted /dev? devfs cannot be unmounted as I know. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
conf/31358: Updated patch for -CURRENT
Attached to this email is an update to the patch supplied with PR
conf/31358, which fixes two issues:
* amd can only be started when NFS client is enabled;
* when nfs_client_enable is set and no NFS file systems are mounted
at boot time from /etc/fstab, rc.network needs to ensure that the
nfsclient module is loaded.
Can someone please take a look at this PR?
Thanks,
Thomas.
diff -u ../rc rc
--- ../rc Tue Jan 8 10:11:48 2002
+++ rc Tue Jan 8 10:42:38 2002
@@ -103,6 +103,7 @@
}
chkdepend amd amd_enableportmap portmap_enable
+chkdepend amd amd_enableNFSnfs_client_enable
chkdepend NFS nfs_server_enable portmap portmap_enable
chkdepend NIS nis_server_enable portmap portmap_enable
chkdepend NIS nis_client_enable portmap portmap_enable
diff -u ../rc.network rc.network
--- ../rc.network Tue Jan 8 10:11:48 2002
+++ rc.network Tue Jan 8 10:57:58 2002
@@ -712,8 +712,30 @@
;;
esac
+ # Handle absent nfs client support
+ if sysctl vfs.nfs /dev/null 21; then
+ nfsclient_in_kernel=1
+ else
+ nfsclient_in_kernel=0
+ fi
+
case ${nfs_client_enable} in
[Yy][Ee][Ss])
+ kldload nfsclient nfsclient_in_kernel=1
+
+ case $nfsclient_in_kernel in
+ 1)
+ ;;
+ *)
+ echo 'Warning: NFS client kernel module failed to load'
+ nfs_client_enable=NO
+ ;;
+ esac
+ ;;
+ esac
+
+ case ${nfs_client_enable} in
+ [Yy][Ee][Ss])
if [ -n ${nfs_access_cache} ]; then
echo -n NFS access cache time=${nfs_access_cache}
sysctl
vfs.nfs.access_cache_timeout=${nfs_access_cache} /dev/null
@@ -732,6 +754,27 @@
echo -n ' rpc.lockd'; rpc.lockd
;;
esac
+
+ case ${amd_enable} in
+ [Yy][Ee][Ss])
+ echo -n ' amd'
+ case ${amd_map_program} in
+ [Nn][Oo] | '')
+ ;;
+ *)
+ amd_flags=${amd_flags} `eval\
+ ${amd_map_program}`
+ ;;
+ esac
+
+ if [ -n ${amd_flags} ]; then
+ amd -p ${amd_flags}\
+/var/run/amd.pid 2 /dev/null
+ else
+ amd 2 /dev/null
+ fi
+ ;;
+ esac
;;
esac
@@ -742,26 +785,6 @@
rpc.umntall -k
fi
- case ${amd_enable} in
- [Yy][Ee][Ss])
- echo -n ' amd'
- case ${amd_map_program} in
- [Nn][Oo] | '')
- ;;
- *)
- amd_flags=${amd_flags} `eval\
- ${amd_map_program}`
- ;;
- esac
-
- if [ -n ${amd_flags} ]; then
- amd -p ${amd_flags}\
-/var/run/amd.pid 2 /dev/null
- else
- amd 2 /dev/null
- fi
- ;;
- esac
;;
esac
--
Thomas Quinot ** Département Informatique Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: conf/31358: Updated patch for -CURRENT
Le 2002-01-08, Thomas Quinot écrivait :
case ${nfs_client_enable} in
[Yy][Ee][Ss])
+kldload nfsclient nfsclient_in_kernel=1
Ooops, this is *far* too aggressive!
Here is a corrected version of the previous patch. Sorry!
diff -u ../rc rc
--- ../rc Tue Jan 8 10:11:48 2002
+++ rc Tue Jan 8 10:42:38 2002
@@ -103,6 +103,7 @@
}
chkdepend amd amd_enableportmap portmap_enable
+chkdepend amd amd_enableNFSnfs_client_enable
chkdepend NFS nfs_server_enable portmap portmap_enable
chkdepend NIS nis_server_enable portmap portmap_enable
chkdepend NIS nis_client_enable portmap portmap_enable
diff -u ../rc.network rc.network
--- ../rc.network Tue Jan 8 10:11:48 2002
+++ rc.network Tue Jan 8 11:12:14 2002
@@ -712,8 +712,33 @@
;;
esac
+ # Handle absent nfs client support
+ if sysctl vfs.nfs /dev/null 21; then
+ nfsclient_in_kernel=1
+ else
+ nfsclient_in_kernel=0
+ fi
+
case ${nfs_client_enable} in
[Yy][Ee][Ss])
+ case $nfsclient_in_kernel in
+ 1)
+ ;;
+ *)
+ if kldload nfsclient
+ then
+ nfsclient_in_kernel=1
+ else
+ echo 'Warning: NFS client kernel module failed
+to load'
+ nfs_client_enable=NO
+ fi
+ ;;
+ esac
+ ;;
+ esac
+
+ case ${nfs_client_enable} in
+ [Yy][Ee][Ss])
if [ -n ${nfs_access_cache} ]; then
echo -n NFS access cache time=${nfs_access_cache}
sysctl
vfs.nfs.access_cache_timeout=${nfs_access_cache} /dev/null
@@ -732,6 +757,27 @@
echo -n ' rpc.lockd'; rpc.lockd
;;
esac
+
+ case ${amd_enable} in
+ [Yy][Ee][Ss])
+ echo -n ' amd'
+ case ${amd_map_program} in
+ [Nn][Oo] | '')
+ ;;
+ *)
+ amd_flags=${amd_flags} `eval\
+ ${amd_map_program}`
+ ;;
+ esac
+
+ if [ -n ${amd_flags} ]; then
+ amd -p ${amd_flags}\
+/var/run/amd.pid 2 /dev/null
+ else
+ amd 2 /dev/null
+ fi
+ ;;
+ esac
;;
esac
@@ -742,26 +788,6 @@
rpc.umntall -k
fi
- case ${amd_enable} in
- [Yy][Ee][Ss])
- echo -n ' amd'
- case ${amd_map_program} in
- [Nn][Oo] | '')
- ;;
- *)
- amd_flags=${amd_flags} `eval\
- ${amd_map_program}`
- ;;
- esac
-
- if [ -n ${amd_flags} ]; then
- amd -p ${amd_flags}\
-/var/run/amd.pid 2 /dev/null
- else
- amd 2 /dev/null
- fi
- ;;
- esac
;;
esac
--
Thomas Quinot ** Département Informatique Réseaux ** [EMAIL PROTECTED]
ENST // 46 rue Barrault // 75634 PARIS CEDEX 13
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
panic during fdisk'ing a md(4) device
Hi, the following script panics my system when executed twice: (uncomment the dd lines for the first time or do it manually) ## #!bin/sh block_size=512 blocks=$((120 * 1024 * 1024 / $block_size)) heads=16 sectors=63 cyl_size=$(($heads * $sectors)); cylinders=$(($blocks / $cyl_size + 2)) #dd if=/dev/zero of=root.image \ # bs=$block_size count=$(($cyl_size * $cylinders)) mdconfig -d -u 11 mdconfig -a -t vnode -f root.image -u 11 fdisk -f - -iv /dev/md11 EOF1 g c$cylinders h$heads s$sectors p 1 165 $sectors $(($cyl_size * $cylinders)) a 1 EOF1 echo $cyl_size $blocks $cylinders Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: conf/31358: Updated patch for -CURRENT
On Tue, 8 Jan 2002 11:02:06 +0100
Thomas Quinot [EMAIL PROTECTED] wrote:
[snip]
+ # Handle absent nfs client support
+ if sysctl vfs.nfs /dev/null 21; then
+ nfsclient_in_kernel=1
+ else
+ nfsclient_in_kernel=0
+ fi
+
This should be handled inside the case statement for ${nfs_client_enable}, as you want
to load the nfsclient kld only if the nfs client is enabled.
case ${nfs_client_enable} in
[Yy][Ee][Ss])
+ kldload nfsclient nfsclient_in_kernel=1
+
+ case $nfsclient_in_kernel in
+ 1)
+ ;;
+ *)
+ echo 'Warning: NFS client kernel module failed to load'
+ nfs_client_enable=NO
+ ;;
+ esac
+ ;;
+ esac
+
+ case ${nfs_client_enable} in
+ [Yy][Ee][Ss])
if [ -n ${nfs_access_cache} ]; then
echo -n NFS access cache time=${nfs_access_cache}
sysctl
vfs.nfs.access_cache_timeout=${nfs_access_cache} /dev/null
@@ -732,6 +754,27 @@
echo -n ' rpc.lockd'; rpc.lockd
;;
esac
You should clean this up so there is only *one* 'case ${nfs_client_enable}'.
Look at the implementation of case ${nfs_server_enable}, earlier in rc.network for an
example of how it should be done.
Cheers,
mike makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
RE: Offerings 28447
Title: spamscan BRAND NEW ANTI-SPAM TECHNOLOGY! Detect eliminate spam BEFORE it gets to your mail client! Tired of the hundreds of unsolicited commercial email (UCE) infiltrating you mailbox everyday? Now you can do something about it! Seek and Destroy all unwanted junk e-mail at the click of a button, BEFORE it reaches your mailbox! FEATURES: Connects to any pop3 server! Eliminates spam BEFORE it reaches your mailbox! Unlimited Account capability! Add as many e-mail accounts as you desire User friendly, graphic interface makes spamscanner very easy to use Scan manually, or let the scanner scan automatically at an auto time interval CLICK HERE TO LEARN MORE Please Note: No trees were destroyed in the sending of this contaminant free message We do concede, a signicant number of electrons may have been inconvenienced. This email was sent to you on behalf of the the coalition for responsible internet marketing. You are receiving this email because you purchased a product from us in the past, or downloaded software from one of our websites and agreed to allow us to send you offers. If you wished to be removed from this mailing, please utilize our automated removal system here. If you request to be removed, we guarantee that you will never receive another email from us, but ONLY through the use of this product can you ensure that you do not receive ANY commercial emails To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Offerings 11641
Title: COPY ANY DVD MOVIE COPY ANY DVD MOVIE!! With our revolutionary system you can copy virtuallyany DVD Movie using your existing equipment! Conventional DVD copying equipment can cost thousands of $$$This revolutionary system costs less than the price of 3 DVD Movies! CLICK HERE FOR MORE INFO If you wish to be removed simply Click Here To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Offerings 28447
On Tue, 8 Jan 2002 [EMAIL PROTECTED] wrote: BRAND NEW ANTI-SPAM TECHNOLOGY! A spammer selling anti-spamming tools? Oh the irony! :-) Cheers, Emiel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Mutt segfaulting on current revisited...
Hey folks... I just found out why my mutt MUA segfaulted. It came down to old libs lying around that were still linked with libc4 instead of libc5. Mutt (from mutt-devel port) compiled beautifully, but it segfaulted on startup. Could this be one for the FAQ or something? Maybe explaining library differences between STABLE and CURRENT and you should be extra careful when an app mixes libc4 and libc5? I solved my problem by recompiling the dependancy libraries (in my case libiconv and libslang) so they use libc5 as well. As you can see from my X-Mailer header, mutt works again :-) Cheers, Emiel -- When the Universe was not so out of whack as it is today, and all the stars were lined up in their proper places, you could easily count them from left to right, or top to bottom, and the larger and bluer ones were set apart, and the smaller yellowing types pushed off to the corners as bodies of a lower grade ... -- Stanislaw Lem, Cyberiad To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mutt segfaulting on current revisited...
In the last episode (Jan 08), Emiel Kollof said: I just found out why my mutt MUA segfaulted. It came down to old libs lying around that were still linked with libc4 instead of libc5. Mutt (from mutt-devel port) compiled beautifully, but it segfaulted on startup. Could this be one for the FAQ or something? Maybe explaining library differences between STABLE and CURRENT and you should be extra careful when an app mixes libc4 and libc5? Actually, you should have gotten a linker warning about having dependencies on multiple versions of a library. Usually it'll just fail to link though. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Mutt segfaulting on current revisited...
* Dan Nelson ([EMAIL PROTECTED]) wrote: I just found out why my mutt MUA segfaulted. It came down to old libs lying around that were still linked with libc4 instead of libc5. Mutt (from mutt-devel port) compiled beautifully, but it segfaulted on startup. Could this be one for the FAQ or something? Maybe explaining library differences between STABLE and CURRENT and you should be extra careful when an app mixes libc4 and libc5? Actually, you should have gotten a linker warning about having dependencies on multiple versions of a library. Usually it'll just fail to link though. Well, it didn't fail, and I never saw that linker warning. I spend quite some time with a Mutt developer going back and forth, and trying out different stuff. I decided to build mutt and its dependancies again which solved the problem. Maybe the linker warning scolled by too fast. Well at least my trusty mutt works now :-) I do have COMPAT4X in my make.conf though... Maybe that had something to do with it? Cheers, Emiel -- What is wanted is not the will to believe, but the will to find out, which is the exact opposite. -- Bertrand Russell, Skeptical_Essays, 1928 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: conf/31358: Updated patch for -CURRENT
Le 2002-01-08, Sheldon Hearn écrivait : Nits follow: [ whitespace ] [ style ] I'd suggest getting your patch tested by -CURRENT users by posting the patch to the freebsd-current mailing list. I have produced a new diff that incorporates the changes suggested by Sheldon. Those interested can fetch it from http://www.cuivre.fr.eu.org/~thomas/31358.diff Thomas. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
sys/dev/usb/uhci.c needs patch to compile
I've been having to apply the following patch to get a kernel
compile to go through. The problem sees to be that when
you have
options UHCI_DEBUG
AND
options DIAGNOSTIC
some conditional code gets added that trys to call uhci_dump_ii
which isn't defined anywhere. Also on line 694 there is:
uhci_dump_qh(sc-sc_ctl_start-qh.hlink);
which produces
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../..
-I../../../dev -I../../../contrib/dev/acpica
-I../../../contrib/ipfilter -I../../../../include -D_KERNEL
-ffreestanding -include opt_global.h -elf -mpreferred-stack-boundary=2
../../../dev/usb/uhci.c
../../../dev/usb/uhci.c: In function `uhci_dump_all':
../../../dev/usb/uhci.c:693: structure has no member named `hlink'
../../../dev/usb/uhci.c: At top level:
../../../dev/usb/uhci.c:1268: warning: `uhci_reset' defined but not used
*** Error code 1
patch starts on the next line --
*** uhci.c.orig Mon Jan 7 07:32:06 2002
--- uhci.c Mon Jan 7 07:37:32 2002
***
*** 258,264
Static void uhci_dump_qh(uhci_soft_qh_t *);
Static void uhci_dump_tds(uhci_soft_td_t *);
Static void uhci_dump_td(uhci_soft_td_t *);
- Static void uhci_dump_ii(uhci_intr_info_t *ii);
void uhci_dump(void);
#endif
--- 258,263
***
*** 691,697
uhci_dumpregs(sc);
printf(intrs=%d\n, sc-sc_bus.no_intrs);
/*printf(framelist[i].link = %08x\n,
sc-sc_framelist[0].link);*/
! uhci_dump_qh(sc-sc_ctl_start-qh.hlink);
}
--- 690,696
uhci_dumpregs(sc);
printf(intrs=%d\n, sc-sc_bus.no_intrs);
/*printf(framelist[i].link = %08x\n,
sc-sc_framelist[0].link);*/
! /*uhci_dump_qh(sc-sc_ctl_start-qh.hlink); */
}
***
*** 1093,1099
splx(s);
#ifdef UHCI_DEBUG
printf(uhci_idone: ii is done!\n );
- uhci_dump_ii(ii);
#else
printf(uhci_idone: ii=%p is done!\n, ii);
#endif
--- 1092,1097
***
*** 2296,2302
if (ii-stdend == NULL) {
printf(uhci_device_isoc_done: xfer=%p
stdend==NULL\n, xfer);
#ifdef UHCI_DEBUG
- uhci_dump_ii(ii);
#endif
return;
}
--- 2294,2299
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: today's current: boot/loader and console
Are your loader and 4th files in sync? There was a change to the 4th scripts that I thought I sent a heads up about. Anyways, do this to get the error message: go into /sys/boot/i386/loader, edit main.c, and change the exit() function to do a while(1); loop before callign __exit(). Compile a new loader and install it and then see what message you get. Well, interestingly enough, the problem disappeared after I simply did make make install in /sys/boot/i386/ ... All I did before was the usual buildworld, installworld, buidlkernel, installkernel, mergemaster, reboot. Yours, -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
zombie linux processes remain
Hello! I'm sure, this is a bug in the program itself (graphics/mtv v. 1.2.5), but can't we do something about it? Notice the parent process id: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 105 6536 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6537 1 4 96 0 00 - Z p40:00,00 (mtvp) 105 6538 1 32 100 0 00 - Z p40:00,00 (mtvp) 105 6539 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6541 1 2 96 0 00 - Z p40:00,00 (mtvp) 105 6542 1 5 96 0 00 - Z p40:00,00 (mtvp) 105 6543 1 43 101 0 00 - Z p40:00,00 (mtvp) 105 6544 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6548 1 1 96 0 00 - Z p40:00,00 (mtvp) 105 6549 1 6 96 0 00 - Z p40:00,00 (mtvp) 105 6550 1 34 100 0 00 - Z p40:00,00 (mtvp) 105 6551 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6553 1 2 96 0 00 - Z p40:00,00 (mtvp) 105 6554 1 7 96 0 00 - Z p40:00,00 (mtvp) 105 6555 1 39 100 0 00 - Z p40:00,00 (mtvp) 105 6556 1 0 107 0 00 - Z p40:00,00 (mtvp) 105 6560 1 3 96 0 00 - Z p40:00,00 (mtvp) 105 6561 1 8 97 0 00 - Z p40:00,00 (mtvp) 105 6562 1 35 100 0 00 - Z p40:00,00 (mtvp) 105 6563 1 0 76 0 00 - Z p40:00,00 (mtvp) 105 6565 1 2 96 0 00 - Z p40:00,00 (mtvp) 105 6566 1 7 96 0 00 - Z p40:00,00 (mtvp) 105 6567 1 43 101 0 00 - Z p40:00,00 (mtvp) 105 6568 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6572 1 2 96 0 00 - Z p40:00,00 (mtvp) 105 6573 1 8 97 0 00 - Z p40:00,00 (mtvp) 105 6574 1 40 101 0 00 - Z p40:00,00 (mtvp) 105 6575 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6577 1 2 96 0 00 - Z p40:00,00 (mtvp) 105 6578 1 6 107 0 00 - Z p40:00,00 (mtvp) 105 6579 1 43 101 0 00 - Z p40:00,00 (mtvp) 105 6580 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6584 1 1 96 0 00 - Z p40:00,00 (mtvp) 105 6585 1 5 96 0 00 - Z p40:00,00 (mtvp) 105 6586 1 38 100 0 00 - Z p40:00,00 (mtvp) 105 6587 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6591 1 1 96 0 00 - Z p40:00,00 (mtvp) 105 6592 1 6 96 0 00 - Z p40:00,00 (mtvp) 105 6593 1 33 100 0 00 - Z p40:00,00 (mtvp) 105 6594 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6596 1 1 96 0 00 - Z p40:00,00 (mtvp) 105 6597 1 6 96 0 00 - Z p40:00,00 (mtvp) 105 6598 1 43 98 0 00 - Z p40:00,00 (mtvp) 105 6599 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6603 1 1 96 0 00 - Z p40:00,00 (mtvp) 105 6604 1 5 96 0 00 - Z p40:00,00 (mtvp) 105 6605 1 32 100 0 00 - Z p40:00,00 (mtvp) 105 6606 1 1 96 0 00 - Z p40:00,00 (mtvp) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: zombie linux processes remain
* Mikhail Teterin [EMAIL PROTECTED] [020108 15:06] wrote: Hello! I'm sure, this is a bug in the program itself (graphics/mtv v. 1.2.5), but can't we do something about it? Notice the parent process id: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 105 6536 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6537 1 4 96 0 00 - Z p40:00,00 (mtvp) Some fixes went in recently that might address this, what version of FreeBSD are you using and when was the last update you did? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: zombie linux processes remain
On 8 Jan, Alfred Perlstein wrote: I'm sure, this is a bug in the program itself (graphics/mtv v. 1.2.5), but can't we do something about it? Notice the parent process id: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 105 6536 1 0 96 0 00 - Z p40:00,00 (mtvp) 105 6537 1 4 96 0 00 - Z p40:00,00 (mtvp) Some fixes went in recently that might address this, what version of FreeBSD are you using and when was the last update you did? FreeBSD aldan.algebra.com 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Thu Jan 3 21:38:15 EST 2002 [EMAIL PROTECTED]:/ccd/obj/ccd/src/sys/DEBUG i386 -- |\__-__/| _/ : :::\_ '__--( ..::)--__`-mi If you have a / _- \/ :::\/ -_ serious knowledge/ / :. .\ \ about computers -- | | Ok, let's say you broke keep it in a secret! _|/ ::\|_the wall with your head Rules of dating, / /:/:_::\::\:.\ What are you going to 'Playboy', ? 1994 | :| ..:(_/ \::|::|::| do in the next cell? | :|:. ::|: |::|.:| Stanislaw J. Lec \ |:: :::_/::/: :|:/ ((___\\/___/___)) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
today's current: acpi fails to load
link_elf: symbol find_devclass undefined KLD file acpi.ko - could not finalize loading -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran ChurchWashburn, Iowa 1L, UST School of Law Minneapolis, Minnesota The opposite of a correct statement is a false statement. The opposite of a profound truth may well be another profound truth. -- Niels Bohr To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
undefined reference to `pfs_statfs'
Anyone got any ideas kern.version: FreeBSD 5.0-20020102-CURRENT #0: Wed Jan 2 12:00:48 GMT 2002 make failed on /usr/src/sys/i386/compile/WARSPITE/../../../fs/procfs/procfs.c(.data+0x6c): undefined reference to `pfs_root' /usr/src/sys/i386/compile/WARSPITE/../../../fs/procfs/procfs.c(.data+0x74): undefined reference to `pfs_statfs' *** Error code 1 source updated by cvs on 8-1-2002 still failed :( [EMAIL PROTECTED] __ _ / /___ ___ / __ ) ___// __ \ / /_ / ___/ _ \/ _ \/ __ \__ \/ / / / / __/ / / / __/ __/ /_/ /__/ / /_/ / /_/ /_/ \___/\___/_//_/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: undefined reference to `pfs_statfs'
On Tue, Jan 08, 2002 at 11:48:44PM -, ADRIAN.BROWNE wrote: Anyone got any ideas kern.version: FreeBSD 5.0-20020102-CURRENT #0: Wed Jan 2 12:00:48 GMT 2002 make failed on /usr/src/sys/i386/compile/WARSPITE/../../../fs/procfs/procfs.c(.data+0x6c): undefined reference to `pfs_root' /usr/src/sys/i386/compile/WARSPITE/../../../fs/procfs/procfs.c(.data+0x74): undefined reference to `pfs_statfs' *** Error code 1 source updated by cvs on 8-1-2002 still failed :( You need 'options PSEUDOFS' for PROCFS (see the 20011203 UPDATING entry). -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org msg33464/pgp0.pgp Description: PGP signature
Re: undefined reference to `pfs_statfs'
hi, there is a note for this in the UPDATING file, that u have to add the following to your kernel config: options PSEUDOFS the latest kernels have to have pseudofs inorder for PROCFS to work.. a dependancy... regards, - Hiten - [EMAIL PROTECTED] --- ADRIAN.BROWNE [EMAIL PROTECTED] wrote: Anyone got any ideas kern.version: FreeBSD 5.0-20020102-CURRENT #0: Wed Jan 2 12:00:48 GMT 2002 make failed on /usr/src/sys/i386/compile/WARSPITE/../../../fs/procfs/procfs.c(.data+0x6c): undefined reference to `pfs_root' /usr/src/sys/i386/compile/WARSPITE/../../../fs/procfs/procfs.c(.data+0x74): undefined reference to `pfs_statfs' *** Error code 1 source updated by cvs on 8-1-2002 still failed :( [EMAIL PROTECTED] __ _ / /___ ___ / __ ) ___// __ \ / /_ / ___/ _ \/ _ \/ __ \__ \/ / / / / __/ / / / __/ __/ /_/ /__/ / /_/ / /_/ /_/ \___/\___/_//_/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message = SSH Fingerprint: 1024 45:a5:9c:f2:fb:07:da:70:18:02:0b:f3:63:f1:7a:a6 [EMAIL PROTECTED] __ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: undefined reference to `pfs_statfs'
You should read UPDATING. PROCFS now requires PSEUDOFS. mike makonnen On Tue, 8 Jan 2002 23:48:44 - ADRIAN.BROWNE [EMAIL PROTECTED] wrote: Anyone got any ideas kern.version: FreeBSD 5.0-20020102-CURRENT #0: Wed Jan 2 12:00:48 GMT 2002 make failed on /usr/src/sys/i386/compile/WARSPITE/../../../fs/procfs/procfs.c(.data+0x6c): undefined reference to `pfs_root' /usr/src/sys/i386/compile/WARSPITE/../../../fs/procfs/procfs.c(.data+0x74): undefined reference to `pfs_statfs' *** Error code 1 source updated by cvs on 8-1-2002 still failed :( [EMAIL PROTECTED] __ _ / /___ ___ / __ ) ___// __ \ / /_ / ___/ _ \/ _ \/ __ \__ \/ / / / / __/ / / / __/ __/ /_/ /__/ / /_/ / /_/ /_/ \___/\___/_//_/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
