Re: portupgrade-2.1.3.2,2 doesn't work with db42
Miroslav Lachman wrote: > Odhiambo Washington wrote: >> rm /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so >> >> then tell me what happens if you run portupgrade again! >> >> I've gone through this today, so it's still fresh in my mind! > > After removing bdb.so portupgrade is working again. Thank you! > > Just for my knowledge - from where goes this error? What should be > fixed? Ruby-bdb or portupgrade? ports/99697 Please note the topic is ports@ relate. And was discussed there. -- Dixi. Sem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1 quota issues
On Mon, 10 Jul 2006, Kostik Belousov wrote: On Mon, Jul 10, 2006 at 12:41:07AM -0400, Charles Sprickman wrote: On Sat, 8 Jul 2006, Matthew D. Fuller wrote: On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of Charles Sprickman, and lo! it spake thus: Trying again, it reported the same inconsistencies then sat there for more than an hour taking up all the available CPU on the box until I killed it. The mtime on quota.user had not changed during the run. FWIW, I saw this on a box I setup running a late November -CURRENT last year; I could never get the quotas setup and running right because the check always just looped itself up. The partition they're on has about 3 gig used out of ~45, with maybe a dozen users. I never spent much time on it, since it's just a personal box, and the quotas are mostly just to provide a handy measure of who's using what (no limits set). I just gave it up and decided to worry about it later. What should I do here? It's consistently failing. What information should I gather to forumulate a PR that won't burden the assignee with lots of troubleshooting mess? The machine is not in production, but there is user data on it. I could allow a trusted developer access to it, or even create another jail to illustrate the problem. It is not clear from your report whether you run fsck on the problem partition. I think (and my view is backed by "unexpected inconsistencies" message) that this is the must. Sorry about that, I did not mention it, but thinking the same thing you did, I unmounted the partition and fsck'd twice for good measure. Both runs came back clean. I think its quotacheck complaining about the quota.user file... Thanks, Charles ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1 quota issues
On Mon, Jul 10, 2006 at 12:41:07AM -0400, Charles Sprickman wrote: > On Sat, 8 Jul 2006, Matthew D. Fuller wrote: > > >On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of > >Charles Sprickman, and lo! it spake thus: > >> > >>Trying again, it reported the same inconsistencies then sat there > >>for more than an hour taking up all the available CPU on the box > >>until I killed it. The mtime on quota.user had not changed during > >>the run. > > > >FWIW, I saw this on a box I setup running a late November -CURRENT > >last year; I could never get the quotas setup and running right > >because the check always just looped itself up. The partition they're > >on has about 3 gig used out of ~45, with maybe a dozen users. I never > >spent much time on it, since it's just a personal box, and the quotas > >are mostly just to provide a handy measure of who's using what (no > >limits set). I just gave it up and decided to worry about it later. > > What should I do here? It's consistently failing. What information > should I gather to forumulate a PR that won't burden the assignee with > lots of troubleshooting mess? The machine is not in production, but there > is user data on it. I could allow a trusted developer access to it, or > even create another jail to illustrate the problem. It is not clear from your report whether you run fsck on the problem partition. I think (and my view is backed by "unexpected inconsistencies" message) that this is the must. pgplgXR1bm8rH.pgp Description: PGP signature
interrupt oddity
I just installed 6.1 on a dual core amd machine. That went fine and it was using the generic SMP kernel. I created a custom kernel using my previous config but forgot to add the SMP line. It worked well except for one odd thing. The nvidia card would start using up a nice chunk of processor time with interrupts and intterupts seem to use a lot more time in general. I added the line, recompiled, rebooted, and every thing worked well. Any one else ever seen any thing like this before or have any idea what happened or why? signature.asc Description: PGP signature
Re: 6.1 quota issues
On Sat, 8 Jul 2006, Matthew D. Fuller wrote: On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of Charles Sprickman, and lo! it spake thus: Trying again, it reported the same inconsistencies then sat there for more than an hour taking up all the available CPU on the box until I killed it. The mtime on quota.user had not changed during the run. FWIW, I saw this on a box I setup running a late November -CURRENT last year; I could never get the quotas setup and running right because the check always just looped itself up. The partition they're on has about 3 gig used out of ~45, with maybe a dozen users. I never spent much time on it, since it's just a personal box, and the quotas are mostly just to provide a handy measure of who's using what (no limits set). I just gave it up and decided to worry about it later. What should I do here? It's consistently failing. What information should I gather to forumulate a PR that won't burden the assignee with lots of troubleshooting mess? The machine is not in production, but there is user data on it. I could allow a trusted developer access to it, or even create another jail to illustrate the problem. Thanks, Charles -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em device hangs on ifconfig alias ...
At 12:06 AM 10/07/2006, User Freebsd wrote: Not sure what STP is Spanning Tree Protocol. Having the link go up and down would cause the switch port to block traffic for a period of time. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em device hangs on ifconfig alias ...
On Mon, 10 Jul 2006, Mike Tancsa wrote: At 01:20 PM 08/07/2006, Ruslan Ermilov wrote: > > Ah, I see. Thanks for the insight. > How about the attached patch? > I've been working on this problem for Mike Tancsa about a year ago, and my fix was naive. I ended up not committing it because I found that it broke something else, but I don't remember what exactly now. Ahh, I seem to remember now -- setting a different MAC address was not programmed into a hardware with my patch applied. For my uses, this was a non issue. Having STP block for 20 seconds because I add or remove an alias made it kind of a non issue. Not sure what STP is, but I've not noticed any blocking on removing an alias, only on adding one ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em device hangs on ifconfig alias ...
At 01:20 PM 08/07/2006, Ruslan Ermilov wrote: > > Ah, I see. Thanks for the insight. > How about the attached patch? > I've been working on this problem for Mike Tancsa about a year ago, and my fix was naive. I ended up not committing it because I found that it broke something else, but I don't remember what exactly now. Ahh, I seem to remember now -- setting a different MAC address was not programmed into a hardware with my patch applied. For my uses, this was a non issue. Having STP block for 20 seconds because I add or remove an alias made it kind of a non issue. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em device hangs on ifconfig alias ...
On Sat, Jul 08, 2006 at 08:20:01PM +0300, Ruslan Ermilov wrote: > On Sat, Jul 08, 2006 at 12:32:55PM +0900, Pyun YongHyeon wrote: > > On Fri, Jul 07, 2006 at 10:38:01PM +0100, Robert Watson wrote: > > > > > > On Fri, 7 Jul 2006, User Freebsd wrote: > > > > > > >>I think that I have patched, built and loaded the em(4) kernel module > > > >>correctly. After applying the patch there were no rejects, before > > > >>building the module I intentionally appended " (patched)" to its > > version > > > >>string in if_em.c, and could see that in dmesg every time I loaded > > the > > > >>module: em1: > > >>(patched)> > > > > > > > >Is it possible that we're going at this issue backwards? It isn't the > > > >lack of ARP packet going out that is causing the problems with moving > > IPs, > > > >but that delay that we're seeing when aliasing a new IP on the stack? > > The > > > >ARP packet *is* being attempted, but is timing out before the re-init > > is > > > >completing? > > > > > > Yes -- basically, there are two problems: > > > > > > (1) A little problem, in which an arp announcement is sent before the > > link > > > has > > > settled after reset. > > > > > > (2) A big problem, in which the interface is gratuitously recent > > requiring > > > long settling times. > > > > > > I'd really like to see a fix to the second of these problems (not > > resetting > > > when an IP is added or removed, resulting in link renegotiation); the > > first > > > one I'm less concerned about, although it would make some amount of > > sense > > > to do an arp announcement when the link goes up. > > > > > > > Ah, I see. Thanks for the insight. > > How about the attached patch? > > > I've been working on this problem for Mike Tancsa about a year ago, > and my fix was naive. I ended up not committing it because I found > that it broke something else, but I don't remember what exactly now. > Ahh, I seem to remember now -- setting a different MAC address was > not programmed into a hardware with my patch applied. > > I guess, in some cases(FIFO overrun/underrun, link duplex changes, hardware malfunction or watchdog error etc) the hardware needs a global reset which in turn needs em_hardware_init(). If we can invoke em_hardware_init() under absolutely required condition it would work as expected. This will also eliminates long time delay needed to add alias addresses. See my other post in the list.( It has a layering violation, handled protocol specific operation in a driver, but I failed to find a better way to fix the issue without rewriting bunch of hardware specific parts of 8254x.) -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
Mike Jakubik wrote: Mathieu Arnold wrote: +-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit : | Mathieu Arnold wrote: |> [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't |> appear in sysctl. | | Gotta love namespace collisions. Well, in fact, most of the tunables do have a read only sysctl so that people don't have to search the code for the value it has/takes :-) Not this one though :-) Exactly, its nice being able to see the current values. How else can i see what the values are set to? The commands limit and limits (one of them is a csh only command) will tell you (although they might be set lower for a particular user via /etc/login.conf, or for a particular process, but that's unlikely). Stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
Mathieu Arnold wrote: | Exactly, its nice being able to see the current values. How else can i | see what the values are set to? As I previously said, it's 512M on i386, and 1G on 64 bit platforms. Right, this explains why my amd64 system works just fine. Shouldn't this be a dynamic value based on total amount of ram? Say 70% of RAM, I mean servers have plenty of RAM nowadays, this seems like an old hard limit, which many new users will trip over I set my value to 805306368, and mysql seems to be happy now. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
+-Le 09/07/2006 17:36 -0400, Mike Jakubik a dit : | Mathieu Arnold wrote: |> +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : |> | I just setup a new system with MySQL 5.0.22, and to my surprise i get |> | this error in MySQL's log. |> | |> | /usr/local/libexec/mysqld: Out of memory (Needed 237527040 bytes) |> | /usr/local/libexec/mysqld: Out of memory (Needed 178145280 bytes) |> | |> | The system has 1GB of ram, which is plenty for MySQLs configuration |> | (its using the my-large.cnf, which is tuned for a system of 512MB) |> | |> | |> | Why am i getting this error? I read somewhere that FreeBSD by default |> | limits process size to 512MB, however the variables used to tune it do |> | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use |> | more memory? |> |> If you're using a i386, the max process memory size limit is at 512M, |> you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. |> |> | | Why are the limits so low by default? In any case, this is what i found | in LINT. | | options MAXDSIZ=(1024UL*1024*1024) | options MAXSSIZ=(128UL*1024*1024) | options DFLDSIZ=(1024UL*1024*1024) That's the LINT value, the *real* default values are in /include/vmparam.h that is, 1G on alpha, ia64 and sparc64, 512K on i386, powerpc and arm and 32G (?) on amd64 | I have no idea what those values mean, what should i set them to to be | safe? A limit 768MB should work for me. You can put 1G and you'd be safe for some time. It has no real, hum, relation with the amount of ram you get, because some parts of your process will get swapped out : PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 9860 mysql 18 960 614M 257M ucond 1 1:22 1.22% mysqld so, as I understand it, mysqld has 614M allocated, from which 257 are actually in RAM (the rest being swapped out.) -- Mathieu Arnold pgpiP2MMQij3W.pgp Description: PGP signature
Re: MySQL and default memory limits (mysqld: Out of memory)
+-Le 09/07/2006 17:36 -0400, Mike Jakubik a dit : | Mathieu Arnold wrote: |> +-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit : |> | Mathieu Arnold wrote: |> |> [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't |> |> appear in sysctl. |> | |> | Gotta love namespace collisions. |> |> Well, in fact, most of the tunables do have a read only sysctl so that |> people don't have to search the code for the value it has/takes :-) |> Not this one though :-) |> | | Exactly, its nice being able to see the current values. How else can i | see what the values are set to? As I previously said, it's 512M on i386, and 1G on 64 bit platforms. -- Mathieu Arnold pgpaFwvIl5BIJ.pgp Description: PGP signature
Re: MySQL and default memory limits (mysqld: Out of memory)
Mathieu Arnold wrote: +-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit : | Mathieu Arnold wrote: |> [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't |> appear in sysctl. | | Gotta love namespace collisions. Well, in fact, most of the tunables do have a read only sysctl so that people don't have to search the code for the value it has/takes :-) Not this one though :-) Exactly, its nice being able to see the current values. How else can i see what the values are set to? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
Mathieu Arnold wrote: +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : | I just setup a new system with MySQL 5.0.22, and to my surprise i get | this error in MySQL's log. | | /usr/local/libexec/mysqld: Out of memory (Needed 237527040 bytes) | /usr/local/libexec/mysqld: Out of memory (Needed 178145280 bytes) | | The system has 1GB of ram, which is plenty for MySQLs configuration (its | using the my-large.cnf, which is tuned for a system of 512MB) | | | Why am i getting this error? I read somewhere that FreeBSD by default | limits process size to 512MB, however the variables used to tune it do | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more | memory? If you're using a i386, the max process memory size limit is at 512M, you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. Why are the limits so low by default? In any case, this is what i found in LINT. options MAXDSIZ=(1024UL*1024*1024) options MAXSSIZ=(128UL*1024*1024) options DFLDSIZ=(1024UL*1024*1024) I have no idea what those values mean, what should i set them to to be safe? A limit 768MB should work for me. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
+-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit : | Mathieu Arnold wrote: |> [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't |> appear in sysctl. | | Gotta love namespace collisions. Well, in fact, most of the tunables do have a read only sysctl so that people don't have to search the code for the value it has/takes :-) Not this one though :-) -- Mathieu Arnold pgpP6rijvweto.pgp Description: PGP signature
Re: MySQL and default memory limits (mysqld: Out of memory)
Mathieu Arnold wrote: [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't appear in sysctl. Gotta love namespace collisions. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
+-Le 09/07/2006 14:14 -0700, Darren Pilgrim a dit : | Mathieu Arnold wrote: |> +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : | > | I read somewhere that FreeBSD by default |> | limits process size to 512MB, however the variables used to tune it do |> | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use |> | more memory? |> |> If you're using a i386, the max process memory size limit is at 512M, |> you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. | | That OID doesn't seem to exist: | | > uname -pr | 6.0-RELEASE-p1 i386 | > sysctl -N kern | grep max That's not a sysctl, it's a tunable thing, which don't appear in sysctl. -- Mathieu Arnold pgpVQik8RtqP2.pgp Description: PGP signature
Re: MySQL and default memory limits (mysqld: Out of memory)
Mathieu Arnold wrote: +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : > | I read somewhere that FreeBSD by default | limits process size to 512MB, however the variables used to tune it do | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more | memory? If you're using a i386, the max process memory size limit is at 512M, you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. That OID doesn't seem to exist: > uname -pr 6.0-RELEASE-p1 i386 > sysctl -N kern | grep max kern.maxvnodes kern.maxproc kern.maxfiles kern.argmax kern.maxfilesperproc kern.maxprocperuid kern.ipc.maxsockbuf kern.ipc.somaxconn kern.ipc.max_linkhdr kern.ipc.max_protohdr kern.ipc.max_hdr kern.ipc.max_datalen kern.ipc.maxpipekva kern.ipc.msgmax kern.ipc.shmmax kern.ipc.maxsockets kern.iov_max kern.kq_calloutmax kern.maxusers kern.threads.max_threads_per_proc kern.threads.max_groups_per_proc kern.threads.max_threads_hits kern.smp.maxcpus -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
+-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : | I just setup a new system with MySQL 5.0.22, and to my surprise i get | this error in MySQL's log. | | /usr/local/libexec/mysqld: Out of memory (Needed 237527040 bytes) | /usr/local/libexec/mysqld: Out of memory (Needed 178145280 bytes) | | The system has 1GB of ram, which is plenty for MySQLs configuration (its | using the my-large.cnf, which is tuned for a system of 512MB) | | | Why am i getting this error? I read somewhere that FreeBSD by default | limits process size to 512MB, however the variables used to tune it do | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more | memory? If you're using a i386, the max process memory size limit is at 512M, you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. -- Mathieu Arnold pgpQkRZMtXJwG.pgp Description: PGP signature
MySQL and default memory limits (mysqld: Out of memory)
I just setup a new system with MySQL 5.0.22, and to my surprise i get this error in MySQL's log. /usr/local/libexec/mysqld: Out of memory (Needed 237527040 bytes) /usr/local/libexec/mysqld: Out of memory (Needed 178145280 bytes) The system has 1GB of ram, which is plenty for MySQLs configuration (its using the my-large.cnf, which is tuned for a system of 512MB) Why am i getting this error? I read somewhere that FreeBSD by default limits process size to 512MB, however the variables used to tune it do not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more memory? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmake: virtual memory exhausted
On 7/8/06, Dan Nelson <[EMAIL PROTECTED]> wrote: In the last episode (Jul 08), Kim Culhan said: > Greetings- > > Compiling Asterisk on 6.1-STABLE: > > gmake -C db1-ast libdb1.a > gmake[1]: Entering directory `/usr/local/src/asterisk/asterisk/db1-ast' > gmake[1]: *** virtual memory exhausted. Stop. > > Any suggestion of a tuning parameter to work around this is > greatly appreciated. Does the port compile? This is Asterisk HEAD I've tried setting several memory parameters to unlimited but this did not work. Also ran the configure script with the --with-low-memory flag but this does not help either. -kim -- [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0->6.1 binary upgrade script
Peter Jeremy wrote: > On Sun, 2006-Jul-09 00:42:31 -0700, Colin Percival wrote: >> I have written an automatic script >> for performing binary FreeBSD 6.0 -> FreeBSD 6.1 upgrades. > > That sounds useful. Are you intending to provide this for future > FreeBSD minor-revision releases? Yes. This is made much easier by the work I'm doing rewriting FreeBSD Update. > But how can I tell that the script came from the FreeBSD Security > Officer? You have signed your mail with a key (ID 0xD09347FC) that > claims to be a Colin Percival with an Oxford Uni address (whereas this > mail has a freebsd.org address) but the key that I downloaded from a > PGP keyserver has no other signatures. You don't have a key in the > FreeBSD CVS repository that I can locate Oops. I really ought to add my key there some day -- it hasn't mattered until now since I've always signed security-related emails with the SO key. Here's my PGP public key, which you will note is signed with the FreeBSD Security Officer key. -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.3 (FreeBSD) mQGiBD5ST1YRBADxgAihxhkd5+87xPxAD3OvMzKKrAhWX9VPaABzjrQmDJrJ0cyb Boa6+aHlnaFZYEIv7DVDylNg5aUDRRDJOrKeWnSXs9Kizg9+ek/3V6202Z5mZiBG YjShN2nhApkTHTN0QfogOEXmY9BHzJzHix75fJZ5wk4q4X28FKVCReoeAwCg/2p/ rgnDBQFkJy/0Lnj6MZQw2KkEAKQ/nNK/KlKNlfA5KAuqS16l1WQKgOP+ispUoaVN arhTU7NCB+UKBAJHPQVeVAe+UvgeUhjh7psCp9C1Au0hmxnpluF1ljknRUzF2WlX ql38/1cHT2RxHr9i/fG8hHQCQkRLp1k01n7rVTzXX3j/K0V+CVbGWIJK7h47ceEL 4tk9A/0T7H1vCeuiu50aMDaigCOmd1XQb+dZlEs50mzLlC1mwtTodRBLqo3Ol78R nZ7DN73AHH7w2197kJ0I10dA6Q5MpScfXKUtnUuItSxv59E9O7SDus6ya77L0lCR cooYL49EuB/pwL/P+c/p+Ki9TmzauGE3Wji6gDH7kH/aVMFwwbQvQ29saW4gUGVy Y2l2YWwgPGNvbGluLnBlcmNpdmFsQHdhZGhhbS5veC5hYy51az6IWAQQEQIAGAUC PlJPVggLCQgHAwIBCgIZAQUbAwAKCRAy3h7N0JNH/EDpAKDEN7HNTjpDEf0K hlVxk8c868mrLwCcDDQ7TEi4XqeonghuoWYRE/oooq+IRgQQEQIABgUCQnhSngAK CRAV1ogEymzfsiShAJ4yFvxZXVWbuzG9lyZLgoUVeQ55FACfeVwS0Clf+93BByQq U0E8HE4rXsm0JUNvbGluIFBlcmNpdmFsIDxjcGVyY2l2YUBmcmVlYnNkLm9yZz6I TwQQEQIADwUCQSYZ3AgLCQgHAwIBCgAKCRAy3h7N0JNH/JU9AKCZEbOE4KD5FRmz xUhoJRJOKS6prwCeNNqyRB+lTg9006K7LAgMLYuUrDuIRgQQEQIABgUCQnhSpQAK CRAV1ogEymzfsivAAJ97Vk22Grq9IrmnKfQY3DHlReLBrQCeO7KaNWoct9y8t2FG pAiqEM02Kl25Ag0EPlJPVhAIAPZCV7cIfwgXcqK61qlC8wXo+VMROU+28W65Szgg 2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvO meFXklnN/biudE/F/Ha8g8VHMGHOfMlm/xX5u/2RXscBqtNbno2gpXI61Brwv0YA WCvl9Ij9WE5J280gtJ3kkQc2azNsOA1FHQ98iLMcfFstjvbzySPAQ/ClWxiNjrtV jLhdONM0/XwXV0OjHRhs3jMhLLUq/zzhsSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZ lp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZJrqrol7DVekyCzsAAgIIAPIwHNo3BY8l 8T54p1GbRXqGxw10B7/wuxc6XgdfDfJOMOjn48+O0LNwyWXWLPR5apGaqlubzG+O okQNP8okLQ5W6vRh09/Y3XfAlHh5nx5bwEFOmrRJPKvyZIY/KjvAA8PAgCIRKVfH IzUqvXbjESrzMuskkxoVRVyrx52FHx6XqQWGY+DJJV9VFDSxzwfq9K4JHQ3yRm7G 75hrPXUB8VC28mOLCEwwkKNyh9PQj27PEwjErPLJ0gKkkK0cfnvcv6pMBkRAHfL7 RqM4Z4yqqfaofS3B50Nr6dvpPx2Xyus3y03Zr9QZuKfFVYJ6Gb3oZuJnRXT5XIwD 5Fiw/V3xaD6ITAQYEQIADAUCPlJPVgUbDAAKCRAy3h7N0JNH/BntAKD/JPN0 g8NrWUVUfiKonbtL1vgMEgCdH+G2T8UJC2wyRTdp4+Io42+tsA0= =7ABx -END PGP PUBLIC KEY BLOCK- Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0->6.1 binary upgrade script
On Sun, 2006-Jul-09 00:42:31 -0700, Colin Percival wrote: > I have written an automatic script >for performing binary FreeBSD 6.0 -> FreeBSD 6.1 upgrades. That sounds useful. Are you intending to provide this for future FreeBSD minor-revision releases? >Naturally, the cryptographic hashes of all the files are verified >against values stored in the script, so as long as you trust the >FreeBSD Security Officer (and if you don't, why are you running >FreeBSD?), the process is entirely secure. But how can I tell that the script came from the FreeBSD Security Officer? You have signed your mail with a key (ID 0xD09347FC) that claims to be a Colin Percival with an Oxford Uni address (whereas this mail has a freebsd.org address) but the key that I downloaded from a PGP keyserver has no other signatures. You don't have a key in the FreeBSD CVS repository that I can locate and I can't find any keys on www.daemonology.net. Basically, I only have your word that you are who you claim to be. (Of course, I still need to be able to trust the FreeBSD CVS repository but if I can't trust that, I can't trust my OS either). If you really are the FreeBSD Security Officer why can't I find copies of your key and FreeBSD SO key (0xCA6CDFB2) that are counter-signed by each other? -- Peter Jeremy pgpi5U6qviUzV.pgp Description: PGP signature
FreeBSD 6.0->6.1 binary upgrade script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear FreeBSD 6.0 users, Those of you who read my blog (http://www.daemonology.net/blog/) will have seen this already; but for those of you who don't: I have written an automatic script for performing binary FreeBSD 6.0 -> FreeBSD 6.1 upgrades. This script will install exactly the same files as are distributed on the ISO image, and it will attempt to automatically merge configuration file changes (in the very unlikely case that it cannot automatically merge changes, it will ask you to merge the changes for it). The script takes approximately 15 minutes, and typically downloads under 20MB of files and binary patches. Naturally, the cryptographic hashes of all the files are verified against values stored in the script, so as long as you trust the FreeBSD Security Officer (and if you don't, why are you running FreeBSD?), the process is entirely secure. The script can be obtained from http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/ and the SHA256 hash of the download is 29075fc5711e0b20d879c69d12bbe5414c1c56d597c8116da7acc0d291116d2f . Colin Percival FreeBSD Security Officer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEsLNnMt4ezdCTR/wRAmRUAKDQFOFxK3y58/vy0Vzx8sov8synWgCg4sYG UfDhAxNjWRq7+zawVvM8cp0= =3gBy -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
