Finding a rogue src/sys commit with bisection?
Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, Nov 15, 2014 at 10:43:32AM -0800, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). http://search.cpan.org/dist/App-SVN-Bisect/bin/svn-bisect Unteste though, they keyword to use bisect. In absolutely worst case yu can check out git tree and bisect that :- -- Mateusz Guzik mjguzik gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, 2014-11-15 at 10:43 -0800, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. I've always used 'svn up -rnn' to bisect. No need to revert, just repeatedly update to the next halfway point, and when you're all done, -rHEAD to get back to normal. I've also had very good results with using -DNO_CLEAN on kernel bisects, it lets you zoom in quickly then when you think you have a candidate you can do a more complete clean-and-rebuild to be sure. Sometimes build glitches will require a clean rebuild at some bisect points. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, Nov 15, 2014 at 07:46:09PM +0100, Mateusz Guzik wrote: On Sat, Nov 15, 2014 at 10:43:32AM -0800, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). http://search.cpan.org/dist/App-SVN-Bisect/bin/svn-bisect There's no instructions on how to install it. In absolutely worst case yu can check out git tree and bisect that :- Nope. Learning how to use git and github is well beyond any interest I have. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, Nov 15, 2014 at 11:52:24AM -0700, Ian Lepore wrote: On Sat, 2014-11-15 at 10:43 -0800, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. I've always used 'svn up -rnn' to bisect. No need to revert, just repeatedly update to the next halfway point, and when you're all done, -rHEAD to get back to normal. I've also had very good results with using -DNO_CLEAN on kernel bisects, it lets you zoom in quickly then when you think you have a candidate you can do a more complete clean-and-rebuild to be sure. Sometimes build glitches will require a clean rebuild at some bisect points. Ian, Thanks! I, obviously, had not considered 'svn update' as a method to achieve what I wanti/need to do. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 11/15/14, 10:43 AM, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. Use git, it has a built in bisector to shake this sort of thing out: git clone --config remote.origin.fetch='+refs/notes/*:refs/notes/*' https://github.com/freebsd/freebsd.git cd freebsd git log # find the hash of the commit for r271273 HASH=the git hash you found # then: git bisect start git bisect bad # Current version is bad git bisect good $HASH Now test compile / etc... Then as things work or don't work you keep running: git bisect good -or- git bisect bad Then compile and test.. you should converge on the problem. -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 11/15/14, 10:52 AM, Steve Kargl wrote: On Sat, Nov 15, 2014 at 07:46:09PM +0100, Mateusz Guzik wrote: On Sat, Nov 15, 2014 at 10:43:32AM -0800, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). http://search.cpan.org/dist/App-SVN-Bisect/bin/svn-bisect There's no instructions on how to install it. In absolutely worst case yu can check out git tree and bisect that :- Nope. Learning how to use git and github is well beyond any interest I have. I just sent you a workflow that will take you about 10 minutes to sort out for git. If you want reply in private and I can send you my phone number to show how if you get stuck. -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, Nov 15, 2014 at 10:56:50AM -0800, Alfred Perlstein wrote: On 11/15/14, 10:43 AM, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. Use git, it has a built in bisector to shake this sort of thing out: I won't be drawn into the git debate. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 15 Nov 2014, at 18:56, Alfred Perlstein bri...@mu.org wrote: git clone --config remote.origin.fetch='+refs/notes/*:refs/notes/*' https://github.com/freebsd/freebsd.git You might want to add --depth 2000 (where 2000 is a guess at how many commits there have been since when it broke and now), to avoid downloading the entire history of the FreeBSD repo (not necessary if you have loads of bandwidth and disk space). Just grabbing the last few thousand revisions is faster than an svn checkout. David ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 11/15/14, 11:01 AM, Steve Kargl wrote: On Sat, Nov 15, 2014 at 10:56:50AM -0800, Alfred Perlstein wrote: On 11/15/14, 10:43 AM, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. Use git, it has a built in bisector to shake this sort of thing out: I won't be drawn into the git debate. OK, so we don't want to use a tool purposefully built for the problem you are facing? Doesn't seem like a git debate more like hammering in screws... -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, Nov 15, 2014 at 11:03:23AM -0800, Alfred Perlstein wrote: On 11/15/14, 11:01 AM, Steve Kargl wrote: I won't be drawn into the git debate. OK, so we don't want to use a tool purposefully built for the problem you are facing? Doesn't seem like a git debate more like hammering in screws... In imy high school years, I worked little construction. More than one old timer told me that a hammer was the best screwdriver they owned. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, 2014-11-15 at 11:03 -0800, Alfred Perlstein wrote: On 11/15/14, 11:01 AM, Steve Kargl wrote: On Sat, Nov 15, 2014 at 10:56:50AM -0800, Alfred Perlstein wrote: On 11/15/14, 10:43 AM, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. Use git, it has a built in bisector to shake this sort of thing out: I won't be drawn into the git debate. OK, so we don't want to use a tool purposefully built for the problem you are facing? Doesn't seem like a git debate more like hammering in screws... This in-your-face git evangelism is getting REALLY OLD, REALLY FAST. Please stop it. I have nothing in particular against git, I just have no interest in it. But that's rapidly transforming into active dislike in exact proportion to being repeatedly talked down to by someone with a different opinion, and apparently the belief that folks with other opinions just need more repetitious condescention to see the light. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 11/15/14, 11:32 AM, Ian Lepore wrote: On Sat, 2014-11-15 at 11:03 -0800, Alfred Perlstein wrote: On 11/15/14, 11:01 AM, Steve Kargl wrote: On Sat, Nov 15, 2014 at 10:56:50AM -0800, Alfred Perlstein wrote: On 11/15/14, 10:43 AM, Steve Kargl wrote: Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. Use git, it has a built in bisector to shake this sort of thing out: I won't be drawn into the git debate. OK, so we don't want to use a tool purposefully built for the problem you are facing? Doesn't seem like a git debate more like hammering in screws... This in-your-face git evangelism is getting REALLY OLD, REALLY FAST. Please stop it. I have nothing in particular against git, I just have no interest in it. But that's rapidly transforming into active dislike in exact proportion to being repeatedly talked down to by someone with a different opinion, and apparently the belief that folks with other opinions just need more repetitious condescention to see the light. This is really over the top. It's not evangelism, the guy asked how do I do X? I showed him how to do it in a few simple steps. If you take git out of the equation it would have been a simple thank you. I could have just as simply replied with the steps needed, however s/git/frob/g and it wouldn't have triggered any reaction from people. -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, Nov 15, 2014 at 11:39:33AM -0800, Alfred Perlstein wrote: This is really over the top. It's not evangelism, the guy asked how do I do X? I showed him how to do it in a few simple steps. The guy, that would be me, asked how to do it with svn. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 11/15/14, 11:42 AM, Steve Kargl wrote: On Sat, Nov 15, 2014 at 11:39:33AM -0800, Alfred Perlstein wrote: This is really over the top. It's not evangelism, the guy asked how do I do X? I showed him how to do it in a few simple steps. The guy, that would be me, asked how to do it with svn. Nope. You showed some svn commands to not do it, you weren't explicit in asking for ways to do it in svn, go ahead, look: ~ % grep -i svn foo.out Before I totally hose by /usr/src directory, does anyone have some guidelines on doing a binary search for a rogue commit in /usr/src/sys?. Either cam or usb (or acpi?) has broken the ability to remove a external USB device once it is plugged into a usb port on my Dell Latitude D530 laptop. I know that a good kernel can be built with r271273 and a bad kernel comes from (nearly) top of tree at r274456. I assume I need to do somthing along the lines % cd /usr/src/sys % svn merge -r 274456:272864(half way point between good and bad) (build kernel and test) % cd /usr/src/sys % svn revert -R . (assume 272864 builds working kernel) % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). Rinse and repeat. .(11:46:36)(alfred@AlfredMacbookAir.local) ~ % cat foo.out % svn merge -r 274456:272864(half way point between good and bad) % svn revert -R . % svn merge -r 274456:273660 (1/2 point between 272864 and 274456). .(11:46:38)(alfred@AlfredMacbookAir.local) ~ % ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
In message 5467adf7.1020...@mu.org, Alfred Perlstein writes: Nope. You showed some svn commands to not do it, you weren't explicit in asking for ways to do it in svn, go ahead, look: I didn't realize that the git-zealots also wanted us to adopt the petty and childish behaviour of the linux email-culture ? Can everybody please just shut up and code now ? Thankyou! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On Sat, Nov 15, 2014 at 11:48:07AM -0800, Alfred Perlstein wrote: On 11/15/14, 11:42 AM, Steve Kargl wrote: On Sat, Nov 15, 2014 at 11:39:33AM -0800, Alfred Perlstein wrote: This is really over the top. It's not evangelism, the guy asked how do I do X? I showed him how to do it in a few simple steps. The guy, that would be me, asked how to do it with svn. Nope. You showed some svn commands to not do it, you weren't explicit in asking for ways to do it in svn, go ahead, look: I won't insult your intelligence. Oh what the hell, it is clear from the list of commands I meant how to do it with svn. Go ahead twist it however suits your needs. Ian's suggestion on using 'svn update -r#' was exactly what I was looking for. PS: 'svn up -r271000' has already shown to provide a good kernel. PPS: I currently building a -r272728 kernel. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 11/15/14, 11:51 AM, Poul-Henning Kamp wrote: In message 5467adf7.1020...@mu.org, Alfred Perlstein writes: Nope. You showed some svn commands to not do it, you weren't explicit in asking for ways to do it in svn, go ahead, look: I didn't realize that the git-zealots also wanted us to adopt the petty and childish behaviour of the linux email-culture ? Can everybody please just shut up and code now ? Thankyou! I resent your implications. Seriously I do. There was no intent to be childish or anything as such. He asked: how do i bisect code. I gave a tool that can do it in a few easy steps? I didn't realize that git has become a trigger word for some people in the project. I will proceed to warn people going forward. -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 11/15/14, 11:53 AM, Steve Kargl wrote: On Sat, Nov 15, 2014 at 11:48:07AM -0800, Alfred Perlstein wrote: On 11/15/14, 11:42 AM, Steve Kargl wrote: On Sat, Nov 15, 2014 at 11:39:33AM -0800, Alfred Perlstein wrote: This is really over the top. It's not evangelism, the guy asked how do I do X? I showed him how to do it in a few simple steps. The guy, that would be me, asked how to do it with svn. Nope. You showed some svn commands to not do it, you weren't explicit in asking for ways to do it in svn, go ahead, look: I won't insult your intelligence. Oh what the hell, it is clear from the list of commands I meant how to do it with svn. Go ahead twist it however suits your needs. Ian's suggestion on using 'svn update -r#' was exactly what I was looking for. PS: 'svn up -r271000' has already shown to provide a good kernel. PPS: I currently building a -r272728 kernel. There was no intention to twist anything. Just intended to lend a hand. Steve, if there are other technologies you never want discussed, please just let me know I'll not reply with help if it involves those tools. My goal is to help, not to traumatize. -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
In message 5467af7a.2080...@mu.org, Alfred Perlstein writes: I resent your implications. Seriously I do. There was no intent to be childish or anything as such. Well, you were, and intentional or not, you're wasting a hell of a lot of peoples time right now. See also: www.bikeshed.org -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Finding a rogue src/sys commit with bisection?
On 11/15/14, 11:56 AM, Poul-Henning Kamp wrote: In message 5467af7a.2080...@mu.org, Alfred Perlstein writes: I resent your implications. Seriously I do. There was no intent to be childish or anything as such. Well, you were, and intentional or not, you're wasting a hell of a lot of peoples time right now. See also: www.bikeshed.org I do not believe it wasteful of people's time to give them to tools to do the job they asked for. Poul, be careful, there comes a time that when everything minor seems childish, and you start slinging it as an insult left and right, that it is quite possible that you've gone too far in the opposite of the spectrum, that being a cantankerous old fart. Take inventory. -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
