Re: Follow up....Re: Updating for the FreeBSD Security Advisory FreeBSD-SA-12:01.openssl
On Thu 2012-05-03 19:17:05 UTC+0200, Leslie Jensen (les...@eskk.nu) wrote: After a reboot my system now has the following label FreeBSD 8.2-RELEASE-p3 #0 How come it downgrades the label from p6 to p3 when upgrading to p7. This is a FAQ. There's a thread about it here: http://lists.freebsd.org/pipermail/freebsd-questions/2010-June/217031.html Short answer: The patch level (-p3) displayed by uname -r after a reboot will not change if freebsd-update has not touched the kernel. As far as I know there haven't been any patches to the 8.2-REL kernel since -p3. /usr/src/sys/conf/newvers.sh is always updated by freebsd-update when there is an update. (Although now that I think about it that might not be true if you don't have the kernel sources installed?) Not exactly intuitive. Several Linux distros have a file named /etc/issue that shows the distro name and version. Perhaps this or something similar could be provided in future FreeBSD releases and updated by freebsd-update. $ cat /etc/issue Ubuntu 12.04 LTS \n \l Regards Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Follow up....Re: Updating for the FreeBSD Security Advisory FreeBSD-SA-12:01.openssl
2012-05-03 20:35, andrew clarke skrev: On Thu 2012-05-03 19:17:05 UTC+0200, Leslie Jensen (les...@eskk.nu) wrote: After a reboot my system now has the following label FreeBSD 8.2-RELEASE-p3 #0 How come it downgrades the label from p6 to p3 when upgrading to p7. This is a FAQ. There's a thread about it here: http://lists.freebsd.org/pipermail/freebsd-questions/2010-June/217031.html Short answer: The patch level (-p3) displayed by uname -r after a reboot will not change if freebsd-update has not touched the kernel. As far as I know there haven't been any patches to the 8.2-REL kernel since -p3. /usr/src/sys/conf/newvers.sh is always updated by freebsd-update when there is an update. (Although now that I think about it that might not be true if you don't have the kernel sources installed?) Not exactly intuitive. Several Linux distros have a file named /etc/issue that shows the distro name and version. Perhaps this or something similar could be provided in future FreeBSD releases and updated by freebsd-update. $ cat /etc/issue Ubuntu 12.04 LTS \n \l Regards Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Thank you :-) I have read similar answers and was partly aware of this. But I was just curious to why. I'll accept it and let a kernel rebuild be a part of my updates. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Follow up....Re: Updating for the FreeBSD Security Advisory FreeBSD-SA-12:01.openssl
On Thu 2012-05-03 20:48:17 UTC+0200, Leslie Jensen (les...@eskk.nu) wrote: Short answer: The patch level (-p3) displayed by uname -r after a reboot will not change if freebsd-update has not touched the kernel. ... I have read similar answers and was partly aware of this. But I was just curious to why. I'll accept it and let a kernel rebuild be a part of my updates. If you're running the GENERIC kernel then you're only creating extra work for yourself by rebuilding it for the sole purpose of having uname -r show the correct patchlevel... On the other hand if you're running a custom kernel then you only need to rebuild the kernel when freebsd-update touches the kernel sources. I don't recall the kernel was touched at all with the most recently -p7 patch (openssl), for example, so there's absolutely no need to rebuild it. Apologies if this was already obvious. Regards Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: follow up...
On Sun, 23 Jan 2011 15:31:40 +1000 Da Rock freebsd-questi...@herveybayaustralia.com.au articulated: Actually the consensus on this list _is_ to hit reply all- some only get digest or are not even subscribed, so they won't receive posts only posted to the list. Unfortunately that can mean you can continue receiving replies not necessarily directly to your own posts. consensus Meaning: : a general agreement about something : an idea or opinion that is shared by all the people in a group [singular] OK, when was the vote on this issue taken? I must have been out of town that week. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ If you think it's expensive to hire a professional to do the job, wait until you hire an amateur. Red Adair ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Duplicate mails (was Re: follow up...)
On Sun, 23 Jan 2011, Da Rock wrote: On 01/23/11 07:43, Gary Kline wrote: something else, probly not related to my web/dns troubles is that for days i seem to be getting spammed with multiple copies of some mail. these dup mail are ones that i _have_ sub'd to. Just strange that this mail bug happened at the same time that my bind troubles began. Is it related to the threads you have been posting? You'll get multiples of those even if others are replying to replied posts. % man procmailex | less +/duplicate shows an effective way to filter out duplicates, if you use or can use mail/procmail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: follow up...
On Sun, Jan 23, 2011 at 06:18:37AM -0500, Jerry wrote: On Sun, 23 Jan 2011 15:31:40 +1000 Da Rock freebsd-questi...@herveybayaustralia.com.au articulated: Actually the consensus on this list _is_ to hit reply all- some only get digest or are not even subscribed, so they won't receive posts only posted to the list. Unfortunately that can mean you can continue receiving replies not necessarily directly to your own posts. consensus Meaning: : a general agreement about something : an idea or opinion that is shared by all the people in a group [singular] OK, when was the vote on this issue taken? I must have been out of town that week. You and me both. I loathe getting multiples of emails. I'm on the list, so I already get a copy. I have no problem doing a group reply by request when someone's not on the list or only gets digest mails, though, or getting duplicates as a side-effect of that -- again, *by request*. Just spamming people with duplicates all the time for no good reason is a mite annoying, though. If I was aware of a vote, I would have voted list reply. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpKrJ69YiNxZ.pgp Description: PGP signature
Re: follow up...
Quoth Chad Perrin on Sunday, 23 January 2011: On Sun, Jan 23, 2011 at 06:18:37AM -0500, Jerry wrote: On Sun, 23 Jan 2011 15:31:40 +1000 Da Rock freebsd-questi...@herveybayaustralia.com.au articulated: Actually the consensus on this list _is_ to hit reply all- some only get digest or are not even subscribed, so they won't receive posts only posted to the list. Unfortunately that can mean you can continue receiving replies not necessarily directly to your own posts. consensus Meaning: : a general agreement about something : an idea or opinion that is shared by all the people in a group [singular] OK, when was the vote on this issue taken? I must have been out of town that week. You and me both. I loathe getting multiples of emails. I'm on the list, so I already get a copy. I have no problem doing a group reply by request when someone's not on the list or only gets digest mails, though, or getting duplicates as a side-effect of that -- again, *by request*. Just spamming people with duplicates all the time for no good reason is a mite annoying, though. If I was aware of a vote, I would have voted list reply. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] +1 -- Sterling (Chip) Camden | sterl...@camdensoftware.com | 2048D/3A978E4F http://chipsquips.com | http://camdensoftware.com | http://chipstips.com pgpE2F6Qa8qHq.pgp Description: PGP signature
Re: follow up...
On 01/24/11 06:38, Chip Camden wrote: Quoth Chad Perrin on Sunday, 23 January 2011: On Sun, Jan 23, 2011 at 06:18:37AM -0500, Jerry wrote: On Sun, 23 Jan 2011 15:31:40 +1000 Da Rockfreebsd-questi...@herveybayaustralia.com.au articulated: Actually the consensus on this list _is_ to hit reply all- some only get digest or are not even subscribed, so they won't receive posts only posted to the list. Unfortunately that can mean you can continue receiving replies not necessarily directly to your own posts. consensus Meaning: : a general agreement about something : an idea or opinion that is shared by all the people in a group [singular] OK, when was the vote on this issue taken? I must have been out of town that week. You and me both. I loathe getting multiples of emails. I'm on the list, so I already get a copy. I have no problem doing a group reply by request when someone's not on the list or only gets digest mails, though, or getting duplicates as a side-effect of that -- again, *by request*. Just spamming people with duplicates all the time for no good reason is a mite annoying, though. If I was aware of a vote, I would have voted list reply. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] +1 Now I'm feeling very alone... :) Mind you I was on your side when it was decided- where are all the old listers? It was a few years ago now. I thought one of the original deciders would have chimed in by now, but it appears quite a few have now moved on- I'm not even getting as many posts these days. In times past it was hard to keep up with it all, a fulltime job to read them all- let alone reply! Well arguments were: reply-list replies are posted back anyway duplicates taking up space etc reply-all posters don't have to subscribe so they won't receive list posts digesters won't keep up with replies -questions@ is meant to be first port of call, user friendly, easy access for help I'm happy to list post. I was talked around last time the vote was taken :) I suppose it depends more on the configuration of the list itself... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: follow up...
On Mon, Jan 24, 2011 at 09:41:50AM +1000, Da Rock wrote: On 01/24/11 06:38, Chip Camden wrote: Quoth Chad Perrin on Sunday, 23 January 2011: On Sun, Jan 23, 2011 at 06:18:37AM -0500, Jerry wrote: On Sun, 23 Jan 2011 15:31:40 +1000 Da Rockfreebsd-questi...@herveybayaustralia.com.au articulated: was decided- where are all the old listers? It was a few years ago now. I thought one of the original deciders would have chimed in by now, but it appears quite a few have now moved on- I'm not even getting as many posts these days. In times past it was hard to keep up with it all, a fulltime job to read them all- let alone reply! Well arguments were: reply-list replies are posted back anyway duplicates taking up space etc reply-all posters don't have to subscribe so they won't receive list posts digesters won't keep up with replies -questions@ is meant to be first port of call, user friendly, easy access for help I'm happy to list post. I was talked around last time the vote was taken :) I suppose it depends more on the configuration of the list itself... Hm. Hopefully, more help when it is Monday [in my locale :)] I've tried addring A records all over the place. Back to square -1. not loaded due to errors I's tuckered out... -g -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 7.97a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: follow up...
On 01/23/11 07:43, Gary Kline wrote: something else, probly not related to my web/dns troubles is that for days i seem to be getting spammed with multiple copies of some mail. these dup mail are ones that i _have_ sub'd to. Just strange that this mail bug happened at the same time that my bind troubles began. Is it related to the threads you have been posting? You'll get multiples of those even if others are replying to replied posts. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: follow up...
On Sun, Jan 23, 2011 at 10:25:05AM +1000, Da Rock wrote: On 01/23/11 07:43, Gary Kline wrote: something else, probly not related to my web/dns troubles is that for days i seem to be getting spammed with multiple copies of some mail. these dup mail are ones that i _have_ sub'd to. Just strange that this mail bug happened at the same time that my bind troubles began. Is it related to the threads you have been posting? You'll get multiples of those even if others are replying to replied posts. More specifically, I think it's because people tend to group-reply rather than list-reply. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgp1NfFpsv0xl.pgp Description: PGP signature
Re: follow up...
On 01/23/11 11:37, Chad Perrin wrote: On Sun, Jan 23, 2011 at 10:25:05AM +1000, Da Rock wrote: On 01/23/11 07:43, Gary Kline wrote: something else, probly not related to my web/dns troubles is that for days i seem to be getting spammed with multiple copies of some mail. these dup mail are ones that i _have_ sub'd to. Just strange that this mail bug happened at the same time that my bind troubles began. Is it related to the threads you have been posting? You'll get multiples of those even if others are replying to replied posts. More specifically, I think it's because people tend to group-reply rather than list-reply. Actually the consensus on this list _is_ to hit reply all- some only get digest or are not even subscribed, so they won't receive posts only posted to the list. Unfortunately that can mean you can continue receiving replies not necessarily directly to your own posts. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Follow Up Question On Upgrading And Ports
On 08/02/2010 17:38, Tim Daneliuk wrote: My ordinary practice with production FreeBSD machines is to: - Regularly (weekly), update the sources, rebuild and reinstall world and kernels. This implies you're running one of the -STABLE branches, rather than -RELEASE: updates to -RELEASE happen much less frequently than weekly... - Regularly (several times a week), do a 'portupgrade -arR' - Somewhat frequently do a 'pkgdb -F' IOW, I keep the OS, kernels, and ports fairly up-to-date. Yep. It's good to do that, although your methodology would be pretty hard to cope with on any more than a few machines. However, per the thread on the proper updating method a few days ago, I just ran 'make delete-old' and 'make delete-old-libs' for the first time ever. After a reboot the system started grumbling about not being able to find libssl.so.4. I reinstalled the compat5,6,7 ports and all is well again. Running 'make delete-old-libs' seems to no longer want to get rid of libssl.so.4. make delete-old-libs will blow away /usr/lib/libssl.so.X, but the compat ports will provide /usr/local/lib/compat/libssl.so.X This leads to my questions: 1) With all the regular portupgrades I do, why is libssl.so.4 even being used any more? Isn't this a relic from the FBSD 4.x branch? No -- libssl.so.4 would be from RELENG_6. RELENG_8 provides libssl.so.6, and the ports version of OpenSSL (and presumably 9-CURRENT too) has libssl.so.7 It's libc.so where the ABI version number is the same as the OS major version number. Other shlibs in base can have completely different ABI version numbers. 2) Why did the initial 'make delete-old-libs' clobber this file, but after the compat reinstalls, the same command no longer cares? Compat libs are in a different location under /usr/local. 3) If I do an in-place upgrade to 8.x (I'll probably wait until 8.1) and immediately follow it with a 'portupgrade -arR', will I be guaranteed that every port will be migrated to the very latest 8.x libs? Every port that is capable of being built from source, yes: some binary blobs may still need compat versions of shlibs. diablo-jdk comes to mind as a good example (needs compat7x). nvidia-driver-173 needs compat5x on my machine. However, such binary blobs are the exception rather than the rule. Rebuilding all your ports is difficult and time-consuming, but it pays off in easier future maintenance, improved performance and better stability. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard, Flat 3 Black Earth Consulting Ramsgate Kent, CT11 9PW Free and Open Source Solutions Tel: +44 (0)1843 580647 signature.asc Description: OpenPGP digital signature
Re: Follow Up Question On Upgrading And Ports
Tim Daneliuk tun...@tundraware.com writes: 3) If I do an in-place upgrade to 8.x (I'll probably wait until 8.1) and immediately follow it with a 'portupgrade -arR', will I be guaranteed that every port will be migrated to the very latest 8.x libs? You want 'portupgrade -af' instead. [You can add the 'rR' if you like, but they're redundant with '-a'.] -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Follow Up Question On Upgrading And Ports
On 2/8/2010 12:30 PM, Matthew Seaman wrote: On 08/02/2010 17:38, Tim Daneliuk wrote: My ordinary practice with production FreeBSD machines is to: - Regularly (weekly), update the sources, rebuild and reinstall world and kernels. This implies you're running one of the -STABLE branches, rather than -RELEASE: updates to -RELEASE happen much less frequently than weekly... - Regularly (several times a week), do a 'portupgrade -arR' - Somewhat frequently do a 'pkgdb -F' IOW, I keep the OS, kernels, and ports fairly up-to-date. Yep. It's good to do that, although your methodology would be pretty hard to cope with on any more than a few machines. Yup, 'tis -stable. And, no, I wouldn't do a farm of machines this way. For that, I wrote/use this: http://www.tundraware.com/Software/tbku/ Matthew Lowell - thanks for taking the time ... Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Follow-up: Tape conversion
On Friday, 26 September 2003 at 17:58:45 -0700, Frank Jahnke wrote: Finally, I received a gentle admonishment to follow up to this list. My experience with mailing lists (mostly on Usenet over the last 15 years) has been that my public inquiries have given rise to a mixture of public and personal responses, as it was with this one. It has been my practise to collect the responses, and follow up publicly with those that also post to the list. Since I receive this list as a digest, that takes a bit of time. It seems that this list works a bit differently, and if it is expected that each reply be answered publicly to the list, I'd certainly be happy to do so in the future. Yes, this is a general request--see my .signature, which adds the first three lines automatically. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. NOTE: Due to the currently active Microsoft-based worms, I am limiting all incoming mail to 131,072 bytes. This is enough for normal mail, but not for large attachments. Please send these as URLs. pgp0.pgp Description: PGP signature
Re: Follow-up: Yet Another make release fails on ghostscript-gnu
Michael Dexter [EMAIL PROTECTED] writes: Having complete control over the build of my network OS is simply revolutionary... but I was hoping this revolution would not be so bloody. You can get *that* with one of the supported update options. make release was never intended for anybody but release engineers. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
