Re: advice on compiling a new kernel upgrading to the latest sources
On Sun, 14 Jan 2007 23:24:56 +0200 Giorgos Keramidas [EMAIL PROTECTED] wrote: On 2007-01-14 15:35, Bill Moran [EMAIL PROTECTED] wrote: Giorgos Keramidas [EMAIL PROTECTED] wrote: [copious snippage] 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL No it doesn't. CVSup will delete the files it doesn't know about, so you should *SAVE a copy* of your favorite kernel config file outside of the source tree and *copy* it into `/usr/src/sys/amd64/conf' after CVSup finishes updates the sources. Really? What have I been doing wrong? I've been keeping custom kernel configs for years and cvsup has never deleted any of them. That's what the ``*default delete use-rel-suffix'' option does, AFAIK. The default supfile examples in `/usr/share/examples/cvsup' have this option enabled, and cvsup(1) says about it: delete The presence of this keyword gives cvsup permission to delete files. If it is missing, no files will be deleted. The presence of the delete keyword puts cvsup into so-called exact mode. In exact mode, CVSup does its best to make the client's files correspond to those on the server. This includes deleting individual deltas and symbolic tags from RCS files, as well as deleting entire files. In exact mode, CVSup verifies every edited file with a checksum, to ensure that the edits have produced a file identical to the master copy on the server. If the checksum test fails for a file, then CVSup falls back upon transferring the entire file. In general, CVSup deletes only files which are known to the server. Extra files present in the client's tree are left alone, even in exact mode. More precisely, CVSup is willing to delete two classes of files: o Files that were previously created or updated by CVSup itself. o Checked-out versions of files which are marked as dead on the server. If the option doesn't work this way, then I stand corrected. Note the sentence: Extra files present in the client's tree are left alone, even in exact mode If a file has *never* been under CVS it's left alone. Having said that I still prefer to symlink because I like to be able to delete directories maintained by cvsup without losing anything. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
advice on compiling a new kernel upgrading to the latest sources
Hi folks, from different sources I have written my steps to compile a new kernel upgrade to the latest sources. Can anyone have a look into them and tell me if I won't run into troubles or if there are better ways to achieve the same? Upgrade procedure to the newest freebsd kernel and userland. 1.Make sure that the cvsup file (src-supfile) is adjusted in the right way. 2.Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL 3.MYKERNEL is then adjusted, if necessary and copied to root/kernels/MYKERNEL 4.Copy everything under /etc to /root/etc 5.cvsup -g -L 2 src-supfile 6.cd /usr/src 7.make cleanworld 8.make buildworld 9.make buildkernel KERNCONF=MYKERNEL 10.Go into single user mode 11.If the new kernel doesn't boot reboot and hit the space bar at the boot prompt and boot kernel.old If the new kernel boots OK mount -a 12.cd /usr/src 13.make installkernel KERNCONF=MYKERNEL 14.Go into single user mode 15.cd /usr/src 16.mergemaster -p 17.make installworld 18.mergemaster -i 19.exit and reboot Is this ok? Or have I forgot about something? I'm running a freebsd 6.1 machine on a amd64 system with an adjusted kernel called MYKERNEL. Thanks inadvanced, Dino Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
From: Dino Vliet [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Sunday, January 14, 2007 9:56 PM Subject: advice on compiling a new kernel upgrading to the latest sources Hi folks, from different sources I have written my steps to compile a new kernel upgrade to the latest sources. Can anyone have a look into them and tell me if I won't run into troubles or if there are better ways to achieve the same? //snip The order how things are done is slightly different, I kept the numbers original though,but the sequence is: 12.cd /usr/src 13.make installkernel KERNCONF=MYKERNEL Reboot after installing the new kernel. New kernel isn't there just after droppping to singleuser, but you need to boot. 11.If the new kernel doesn't boot reboot and hit the space bar at the boot prompt and boot kernel.old If the new kernel boots OK mount -a Check that new kernel acts somewhat sane (some programs might fail though due changed kernel interfaces, like top or ps for example - I do go full multiuser to check this) 14.Go into single user mode 15.cd /usr/src 16.mergemaster -p 17.make installworld 18.mergemaster -i 19.exit and reboot Shouldn't be need for reboot after this, just hit ctrl-D and enjoy the updated system. Updated scripts are executed only after machine goes into full multiuser. -Reko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
On 2007-01-14 11:56, Dino Vliet [EMAIL PROTECTED] wrote: Hi folks, from different sources I have written my steps to compile a new kernel upgrade to the latest sources. Your instructions, however, are different from what /usr/src/UPDATING contains. Please, make *sure* you read `/usr/src/UPDATING' very carefully. Especially the commands of the section ``To upgrade in-place ...'' and *all* the footnotes they reference. Can anyone have a look into them and tell me if I won't run into troubles or if there are better ways to achieve the same? Upgrade procedure to the newest freebsd kernel and userland. 1.Make sure that the cvsup file (src-supfile) is adjusted in the right way. That's ok. 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL No it doesn't. CVSup will delete the files it doesn't know about, so you should *SAVE a copy* of your favorite kernel config file outside of the source tree and *copy* it into `/usr/src/sys/amd64/conf' after CVSup finishes updates the sources. 3.MYKERNEL is then adjusted, if necessary and copied to root/kernels/MYKERNEL Nice :) 4.Copy everything under /etc to /root/etc Why? This isn't mentioned in `/usr/src/UPDATING' and it doesn't really help much if you manage to trash your /lib and /usr/lib trees. A better suggestion is to ``make sure you have good level 0 dumps'', as suggested by ``/usr/src/UPDATING''. 5.cvsup -g -L 2 src-supfile You've deleted MYKERNEL here. 6. cd /usr/src 7. make cleanworld The ``make cleanworld'' command is unnecessary if you haven't been building stuff manually inside the tree. 8. make buildworld 9. make buildkernel KERNCONF=MYKERNEL You can do both at the same time, with: # cd /usr/src # make KERNCONF=MYKERNEL buildworld buildkernel 10. Go into single user mode You forgot to install the new kernel *before* rebooting here. This should be done with: # cd /usr/src # make KERNCONF=MYKERNEL installkernel 11. If the new kernel doesn't boot reboot and hit the space bar at the boot prompt and boot kernel.old If the new kernel boots OK mount -a No, mount -a is not enough. Please read the `UPDATING' file. The full sequence of commands would be something like: (escape to loader prompt) (at the OK prompt of the boot loader, type): boot -s Then, when the system starts a /bin/sh shell instance, type: # adjkerntz -i # fsck -p # mount -u / # mount -a 12. cd /usr/src 13. make installkernel KERNCONF=MYKERNEL It is too late to install a new kernel here, if you didn't do it *before* rebooting into single user mode. The whole 'exercise' of installing the new kernel and booting into single user mode is meant to provide a level of testing for the new kernel. If you haven't installed it and booted into the old kernel, some things may fail to install later on, you don't know if the new kernel actually works, etc. 14. Go into single user mode You *ARE* in single-user mode already. 15. cd /usr/src 16. mergemaster -p 17. make installworld 18. mergemaster -i 19. exit and reboot These look fine. Is this ok? Or have I forgot about something? I'm running a freebsd 6.1 machine on a amd64 system with an adjusted kernel called MYKERNEL. Please read ``/usr/src/UPDATING''. Then read it again. Let the text and all its footnotes sink in, and if you don't understand *why* a particular step exists, or what a specific step is supposed to do, feel free to ask. We are here to help you update the system, but we are *also* here to help you understand the why, when, how and what for of each step of the process :-) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
Dino Vliet wrote: Hi folks, from different sources I have written my steps to compile a new kernel upgrade to the latest sources. Can anyone have a look into them and tell me if I won't run into troubles or if there are better ways to achieve the same? Upgrade procedure to the newest freebsd kernel and userland. 1.Make sure that the cvsup file (src-supfile) is adjusted in the right way. 2.Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL 3.MYKERNEL is then adjusted, if necessary and copied to root/kernels/MYKERNEL 4.Copy everything under /etc to /root/etc 5.cvsup -g -L 2 src-supfile 6.cd /usr/src so far so good 7.make cleanworld The handbook suggest: rm -rf /usr/obj/* , the cleanworld might do the same you might check that 8.make buildworld 9.make buildkernel KERNCONF=MYKERNEL 10.Go into single user mode OK 11.If the new kernel doesn't boot reboot and hit the space bar at the boot prompt and boot kernel.old If the new kernel boots OK mount -a You have to install your kernel first, step 13 is next now. Also when allready running in the 'multi'-user mode a 'shutdown now' will bring you in single user mode 12.cd /usr/src 13.make installkernel KERNCONF=MYKERNEL asuming you still are in single user mode you now have to do 'make installworld' ( your step 17 ), after you've done that run a 'mergemaster' and you are finished. Basically everything you have to do is documented perfectly in the FreeBSD Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I suggest reading it (again?) and if possible open the page on a 2nd computer or something so you can read whatever step is next when rebuilding world. Also you might want to run 'script /path/to/logfile/' as also described in the handbook . 14.Go into single user mode 15.cd /usr/src 16.mergemaster -p 17.make installworld 18.mergemaster -i 19.exit and reboot Is this ok? Or have I forgot about something? I'm running a freebsd 6.1 machine on a amd64 system with an adjusted kernel called MYKERNEL. Thanks inadvanced, Dino Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- -Frank Staals ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
Giorgos Keramidas [EMAIL PROTECTED] wrote: [copious snippage] 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL No it doesn't. CVSup will delete the files it doesn't know about, so you should *SAVE a copy* of your favorite kernel config file outside of the source tree and *copy* it into `/usr/src/sys/amd64/conf' after CVSup finishes updates the sources. Really? What have I been doing wrong? I've been keeping custom kernel configs for years and cvsup has never deleted any of them. 4.Copy everything under /etc to /root/etc Why? This isn't mentioned in `/usr/src/UPDATING' and it doesn't really help much if you manage to trash your /lib and /usr/lib trees. A better suggestion is to ``make sure you have good level 0 dumps'', as suggested by ``/usr/src/UPDATING''. While not mentioned in /usr/src/UPDATING, this is good practice in my opinion. mergemaster can be a tedious task, and making a local backup of /etc has allowed me to undo some careless keystrokes a number of times. I don't disagree with the dump advice, but an additional copy of /etc around doesn't hurt anything and occasionally makes fixing a mistake much faster an easier. -Bill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
Giorgos Keramidas wrote: On 2007-01-14 11:56, Dino Vliet [EMAIL PROTECTED] wrote: Hi folks, from different sources I have written my steps to compile a new kernel upgrade to the latest sources. Your instructions, however, are different from what /usr/src/UPDATING contains. Please, make *sure* you read `/usr/src/UPDATING' very carefully. Especially the commands of the section ``To upgrade in-place ...'' and *all* the footnotes they reference. Can anyone have a look into them and tell me if I won't run into troubles or if there are better ways to achieve the same? Upgrade procedure to the newest freebsd kernel and userland. 1.Make sure that the cvsup file (src-supfile) is adjusted in the right way. That's ok. 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL No it doesn't. CVSup will delete the files it doesn't know about, so you should *SAVE a copy* of your favorite kernel config file outside of the source tree and *copy* it into `/usr/src/sys/amd64/conf' after CVSup finishes updates the sources. But in my practice, CVSup did nothing with my own kernel config file. In my memory, cvs did nothing with the files not in the source tree. 3.MYKERNEL is then adjusted, if necessary and copied to root/kernels/MYKERNEL Nice :) 4.Copy everything under /etc to /root/etc Why? This isn't mentioned in `/usr/src/UPDATING' and it doesn't really help much if you manage to trash your /lib and /usr/lib trees. A better suggestion is to ``make sure you have good level 0 dumps'', as suggested by ``/usr/src/UPDATING''. 5.cvsup -g -L 2 src-supfile You've deleted MYKERNEL here. 6. cd /usr/src 7. make cleanworld The ``make cleanworld'' command is unnecessary if you haven't been building stuff manually inside the tree. 8. make buildworld 9. make buildkernel KERNCONF=MYKERNEL You can do both at the same time, with: # cd /usr/src # make KERNCONF=MYKERNEL buildworld buildkernel 10. Go into single user mode You forgot to install the new kernel *before* rebooting here. This should be done with: # cd /usr/src # make KERNCONF=MYKERNEL installkernel 11. If the new kernel doesn't boot reboot and hit the space bar at the boot prompt and boot kernel.old If the new kernel boots OK mount -a No, mount -a is not enough. Please read the `UPDATING' file. The full sequence of commands would be something like: (escape to loader prompt) (at the OK prompt of the boot loader, type): boot -s Then, when the system starts a /bin/sh shell instance, type: # adjkerntz -i # fsck -p # mount -u / # mount -a 12. cd /usr/src 13. make installkernel KERNCONF=MYKERNEL It is too late to install a new kernel here, if you didn't do it *before* rebooting into single user mode. The whole 'exercise' of installing the new kernel and booting into single user mode is meant to provide a level of testing for the new kernel. If you haven't installed it and booted into the old kernel, some things may fail to install later on, you don't know if the new kernel actually works, etc. 14. Go into single user mode You *ARE* in single-user mode already. 15. cd /usr/src 16. mergemaster -p 17. make installworld 18. mergemaster -i 19. exit and reboot These look fine. Is this ok? Or have I forgot about something? I'm running a freebsd 6.1 machine on a amd64 system with an adjusted kernel called MYKERNEL. Please read ``/usr/src/UPDATING''. Then read it again. Let the text and all its footnotes sink in, and if you don't understand *why* a particular step exists, or what a specific step is supposed to do, feel free to ask. We are here to help you update the system, but we are *also* here to help you understand the why, when, how and what for of each step of the process :-) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
On Sunday 14 January 2007 15:44, kbtrace wrote: Giorgos Keramidas wrote: On 2007-01-14 11:56, Dino Vliet [EMAIL PROTECTED] wrote: 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL No it doesn't. CVSup will delete the files it doesn't know about, so you should *SAVE a copy* of your favorite kernel config file outside of the source tree and *copy* it into `/usr/src/sys/amd64/conf' after CVSup finishes updates the sources. But in my practice, CVSup did nothing with my own kernel config file. In my memory, cvs did nothing with the files not in the source tree. Generally speaking, CVSup will delete files it doesn't know about. However, all of the src/sys/arch/conf directories have .cvsignore files in them which prevents this behavior. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
John Nielsen wrote: On Sunday 14 January 2007 15:44, kbtrace wrote: Giorgos Keramidas wrote: On 2007-01-14 11:56, Dino Vliet [EMAIL PROTECTED] wrote: 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL No it doesn't. CVSup will delete the files it doesn't know about, so you should *SAVE a copy* of your favorite kernel config file outside of the source tree and *copy* it into `/usr/src/sys/amd64/conf' after CVSup finishes updates the sources. But in my practice, CVSup did nothing with my own kernel config file. In my memory, cvs did nothing with the files not in the source tree. Generally speaking, CVSup will delete files it doesn't know about. However, all of the src/sys/arch/conf directories have .cvsignore files in them which prevents this behavior. JN This line in the cvsup file changes that behavior (from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html): *default release=cvs delete use-rel-suffix compress Don't want stuff deleted when cvsup runs (not wise, but you can do it)?, remove the delete keyword in your cvsup file. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
--- Giorgos Keramidas [EMAIL PROTECTED] wrote: On:56, Dino Vliet [EMAIL PROTECTED] wrote: Hi folks, from different sources I have written my steps to compile a new kernel upgrade to the latest sources. Your instructions, however, are different from what /usr/src/UPDATING contains. Please, make *sure* you read `/usr/src/UPDATING' very carefully. Especially the commands of the section ``To upgrade in-place ...'' and *all* the footnotes they reference. Can anyone have a look into them and tell me if I won't run into troubles or if there are better ways to achieve the same? Upgrade procedure to the newest freebsd kernel and userland. 1.Make sure that the cvsup file (src-supfile) is adjusted in the right way. That's ok. 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL No it doesn't. CVSup will delete the files it doesn't know about, so you should *SAVE a copy* of your favorite kernel config file outside of the source tree and *copy* it into `/usr/src/sys/amd64/conf' after CVSup finishes updates the sources. 3.MYKERNEL is then adjusted, if necessary and copied to root/kernels/MYKERNEL Nice :) 4.Copy everything under /etc to /root/etc Why? This isn't mentioned in `/usr/src/UPDATING' and it doesn't really help much if you manage to trash your /lib and /usr/lib trees. A better suggestion is to ``make sure you have good level 0 dumps'', as suggested by ``/usr/src/UPDATING''. 5.cvsup -g -L 2 src-supfile You've deleted MYKERNEL here. 6. cd /usr/src 7. make cleanworld The ``make cleanworld'' command is unnecessary if you haven't been building stuff manually inside the tree. 8. make buildworld 9. make buildkernel KERNCONF=MYKERNEL You can do both at the same time, with: # cd /usr/src # make KERNCONF=MYKERNEL buildworld buildkernel 10. Go into single user mode You forgot to install the new kernel *before* rebooting here. This should be done with: # cd /usr/src # make KERNCONF=MYKERNEL installkernel 11. If the new kernel doesn't boot reboot and hit the space bar at the boot prompt and boot kernel.old If the new kernel boots OK mount -a No, mount -a is not enough. Please read the `UPDATING' file. The full sequence of commands would be something like: (escape to loader prompt) (at the OK prompt of the boot loader, type): boot -s Then, when the system starts a /bin/sh shell instance, type: # adjkerntz -i # fsck -p # mount -u / # mount -a 12. cd /usr/src 13. make installkernel KERNCONF=MYKERNEL It is too late to install a new kernel here, if you didn't do it *before* rebooting into single user mode. The whole 'exercise' of installing the new kernel and booting into single user mode is meant to provide a level of testing for the new kernel. If you haven't installed it and booted into the old kernel, some things may fail to install later on, you don't know if the new kernel actually works, etc. 14. Go into single user mode You *ARE* in single-user mode already. 15. cd /usr/src 16. mergemaster -p 17. make installworld 18. mergemaster -i 19. exit and reboot These look fine. Is this ok? Or have I forgot about something? I'm running a freebsd 6.1 machine on a amd64 system with an adjusted kernel called MYKERNEL. Please read ``/usr/src/UPDATING''. Then read it again. Let the text and all its footnotes sink in, and if you don't understand *why* a particular step exists, or what a specific step is supposed to do, feel free to ask. We are here to help you update the system, but we are *also* here to help you understand the why, when, how and what for of each step of the process :-) - Giorgos Thanks for your help! I am glad I asked before doing it, so now I can check out the resources given and try to learn why things are they way they are. Your post gave me a lit of valuable insights and I will have to print everything out and read it carefully. I really like the FreeBSD way though (have just donated to the foundation because of the nice way people like you treat this cry for help:-) Thanks again! Dino Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: advice on compiling a new kernel upgrading to the latest sources
On 2007-01-14 15:35, Bill Moran [EMAIL PROTECTED] wrote: Giorgos Keramidas [EMAIL PROTECTED] wrote: [copious snippage] 2. Cd /usr/src/sys/amd64/conf which contains the file MYKERNEL No it doesn't. CVSup will delete the files it doesn't know about, so you should *SAVE a copy* of your favorite kernel config file outside of the source tree and *copy* it into `/usr/src/sys/amd64/conf' after CVSup finishes updates the sources. Really? What have I been doing wrong? I've been keeping custom kernel configs for years and cvsup has never deleted any of them. That's what the ``*default delete use-rel-suffix'' option does, AFAIK. The default supfile examples in `/usr/share/examples/cvsup' have this option enabled, and cvsup(1) says about it: delete The presence of this keyword gives cvsup permission to delete files. If it is missing, no files will be deleted. The presence of the delete keyword puts cvsup into so-called exact mode. In exact mode, CVSup does its best to make the client's files correspond to those on the server. This includes deleting individual deltas and symbolic tags from RCS files, as well as deleting entire files. In exact mode, CVSup verifies every edited file with a checksum, to ensure that the edits have produced a file identical to the master copy on the server. If the checksum test fails for a file, then CVSup falls back upon transferring the entire file. In general, CVSup deletes only files which are known to the server. Extra files present in the client's tree are left alone, even in exact mode. More precisely, CVSup is willing to delete two classes of files: o Files that were previously created or updated by CVSup itself. o Checked-out versions of files which are marked as dead on the server. If the option doesn't work this way, then I stand corrected. 4.Copy everything under /etc to /root/etc Why? This isn't mentioned in `/usr/src/UPDATING' and it doesn't really help much if you manage to trash your /lib and /usr/lib trees. A better suggestion is to ``make sure you have good level 0 dumps'', as suggested by ``/usr/src/UPDATING''. While not mentioned in /usr/src/UPDATING, this is good practice in my opinion. mergemaster can be a tedious task, and making a local backup of /etc has allowed me to undo some careless keystrokes a number of times. I don't disagree with the dump advice, but an additional copy of /etc around doesn't hurt anything and occasionally makes fixing a mistake much faster an easier. Heh, true :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
