From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 04:28:50 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0313C8E0 for ; Sun, 28 Sep 2014 04:28:50 +0000 (UTC) Received: from sdf.lonestar.org (mx.sdf.org [192.94.73.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "SDF.ORG" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CD517D7E for ; Sun, 28 Sep 2014 04:28:48 +0000 (UTC) Received: from sdf.org (IDENT:bennett@sdf.lonestar.org [192.94.73.15]) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s8S4Sfal001490 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Sun, 28 Sep 2014 04:28:42 GMT Received: (from bennett@localhost) by sdf.org (8.14.8/8.12.8/Submit) id s8S4SftK018265; Sat, 27 Sep 2014 23:28:41 -0500 (CDT) From: Scott Bennett Message-Id: <201409280428.s8S4SftK018265@sdf.org> Date: Sat, 27 Sep 2014 23:28:41 -0500 To: Andrew Berg Subject: Re: ZFS and 2 TB disk drive technology :-( User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 04:28:50 -0000 Thank you for your reply. On Wed, 24 Sep 2014 06:37:30 -0500 Andrew Berg wrote: >On 2014.09.24 06:08, Scott Bennett wrote: >> If anyone reading this has any suggestions for a course of action >> here, I'd be most interested in reading them. Thanks in advance for any >> ideas and also for any corrections if I've misunderstood what a ZFS >> mirror was supposed to have done to preserve the data and maintain >> correct operation at the application level. >I skimmed over the long message, and my first thought is that you have a messed >up controller that is lying. I've run into such a controller on a hard drive Yes, this thought has crossed my mind, too. I don't think it explains all of the evidence well, but OTOH, I can't quite rule it out yet either. The error rate appears to differ from drive to drive. >enclosure that is supposed to support disks larger than 2TB, but seems to write >to who knows where when you want a sector beyond 2TB, and the filesystem layer >has no idea anything is wrong. This is all just an educated, guess, but I ran into that problem last year when I had a 3 TB drive put into a case with the interface combination that I wanted. Someone on the list clued me in about old controllers, so we checked, and sure enough, the controller in that case was unable to handle devices larger than 2 TB. In the current situation, however, all four drives are 2 TB drives. >considering you get errors at a level below ZFS (would it be called the CAM >layer?), my advice would be to check the controllers and perhaps even the disks >themselves. AFAIK, issues at that layer are rarely software ones. Yes, as noted in earlier threads, I've already seen the problem of undetected write errors on these drives without ZFS being involved, just UFS2. I had been planning to set up a gvinum raid5 device until I realized that protection against loss of a drive would not protect me from corruption of data without loss. Although running a parity check on the raid5 device should reveal errors, it would not fix them, whereas the claim was made that raidzN would fix them. So I decided to try ZFS in hopes that errors would be both detected when they occurred (they are not) and corrected upon detection (they appear not to be, regardless of what ZFS scrub results say). Meanwhile, Seagate has not seemed willing to replace running drives that have errors with running drives that have been tested and shown to have no errors. :-( That leaves me with my money spent on equipment that does not work properly. I may have to buy another card and swap it with the one that is in the tower at present, but I'd rather not do that unless I find better evidence that the problems come from the card I have now, especially given that much of the evidence thus far gathered points to the quality of the drives as the culprit. I suppose I could reconnect the USB 3.0 drives to USB 2.0 ports and then repeat my tests, but I'm already kind of fed up with all the delays. Also, as previously noted, the Western Digital drive is connected via Firewire 400 and is showing scrub errors as well, albeit comparatively few. It has been several months now since I last had a place to write backups, and the lack of recent backups is giving me the heebie jeebies more and more by the day. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 09:06:39 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8CF9A76E for ; Sun, 28 Sep 2014 09:06:39 +0000 (UTC) Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F846889 for ; Sun, 28 Sep 2014 09:06:39 +0000 (UTC) Received: by mail-yh0-f50.google.com with SMTP id z6so409283yhz.23 for ; Sun, 28 Sep 2014 02:06:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hE1XmcWxm+Di1fPnqEVuy2Ca27kI+ZPWScBQ4Ngit/I=; b=FAQzBlxn9OoG8+fhdHLMHUMsQWZ2qLFOE+ZZcKdKeU72LEq+258SjkWOvBlnYo30/p NRXvSKQCRpCts7/GzA9rZGLCFeVuqmcvGxN8KY1DAEgBEvM0viSjNCa5u+jYGYuvo60C UA2Wbyaie0yU7L3Ubdohh4D7n5H/iL9fFbsh7vmW4BFsAjAZz3C3UJaRaq+v8x85PXq0 wBwNYcIg7KSdE+7EkTrgGtY7GIdhHo0O8iJpvMzKaxlPC8OTdJJWnJxiUqi770dkVkBL nn8PhNIQ0sJeDaF234E4sSwcufcL1xrptA4ukJipqWIFwyJb9wJpechrkxUb1GJKp7wm jyUg== MIME-Version: 1.0 X-Received: by 10.236.29.5 with SMTP id h5mr44914698yha.58.1411895197147; Sun, 28 Sep 2014 02:06:37 -0700 (PDT) Received: by 10.170.150.85 with HTTP; Sun, 28 Sep 2014 02:06:37 -0700 (PDT) In-Reply-To: References: <23187F4C-0413-4F84-9C86-6EC1084C794C@btinternet.com> Date: Sun, 28 Sep 2014 05:06:37 -0400 Message-ID: Subject: Re: freebsd-update question From: FF To: "firmdog@gmail.com" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-questions@freebsd.org, Dave X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 09:06:39 -0000 Can you provide the output of those commands? Freebsd-update is usually pretty good about telling you what's wrong. Thanks On Sat, Sep 27, 2014 at 3:02 PM, firmdog@gmail.com wrote: > Yes I ran freebsd-update install. Then I rebooted. Then I did it again. > Still at 8.3 > On Sep 27, 2014 2:37 PM, "Dave" wrote: > > > On 27 September 2014 18:22:15 BST, "firmdog@gmail.com" < > firmdog@gmail.com> > > wrote: > >> > >> Hi, > >> > >> Trying to use freebsd-update to go from 8.3 to 8.4 and I am doing this: > >> > >> # freebsd-update -r 8.4-RELEASE upgrade > >> # freebsd-update install > >> # reboot > >> > >> After reboot I am still at 8.3-RELEASE FreeBSD 8.3-RELEASE #0 > >> > >> What am I doing wrong? > >> ------------------------------ > >> > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > >> > >> > > Don't you need run rub "freebsd-update install"? > > -- > > Dave > > > > GPG/PGP ID: CDB94DA1 > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > -- FF From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 10:30:11 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C16506C4 for ; Sun, 28 Sep 2014 10:30:11 +0000 (UTC) Received: from sdf.lonestar.org (mx.sdf.org [192.94.73.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "SDF.ORG" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CE24F3A for ; Sun, 28 Sep 2014 10:30:11 +0000 (UTC) Received: from sdf.org (IDENT:bennett@sdf.lonestar.org [192.94.73.15]) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s8SAU8Hd027694 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Sun, 28 Sep 2014 10:30:08 GMT Received: (from bennett@localhost) by sdf.org (8.14.8/8.12.8/Submit) id s8SAU8dR027634; Sun, 28 Sep 2014 05:30:08 -0500 (CDT) From: Scott Bennett Message-Id: <201409281030.s8SAU8dR027634@sdf.org> Date: Sun, 28 Sep 2014 05:30:08 -0500 To: Paul Kraus Subject: Re: ZFS and 2 TB disk drive technology :-( User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 10:30:11 -0000 On Wed, 24 Sep 2014 11:24:35 -0400 Paul Kraus wrote: Thanks for chiming in, Paul. >On 9/24/14 7:08, Scott Bennett wrote: > > > >What version of FreeBSD are you running ? FreeBSD hellas 9.2-STABLE FreeBSD 9.2-STABLE #1 r264339: Fri Apr 11 05:16:25 CDT 2014 bennett@hellas:/usr/obj/usr/src/sys/hellas i386 >What hardware are you running it on ? The CPU is a Q6600 running on a PCIE2 Gigabyte motherboard, whose model number I did have written down around here somewhere but can't lay hands on at the moment. I looked it up at the gigabyte.com web site, and it supposed to be okay for a number of considerably faster CPU models. It has 4 GB of memory, but FreeBSD ignores the last ~1.1 GB of it, so ~2.9 GB usable. It has been running mprime worker threads on all four cores with no apparent problems for almost 11 months now. The USB 3.0 card is a "rocketfish USB 3.0 PCI Express Card", which reports a NEC uPD720200 USB 3.0 controller. It has two ports, into which I have two USB 3.0 hubs plugged. There are currently four 2 TB drives plugged into those hubs. The Firewire 400 card reports itself as a "VIA Fire II (VT6306)", and it has two ports on it with one 2 TB drive connected to each port. > >> Then I copied the 1.08 TB file again from another Seagate 2 TB drive >> to the mirror vdev. No errors were detected during the copy. Then I >> began creating a tar file from large parts of a nearly full 1.2 TB file >> system (UFS2) on yet another Seagate 2TB on the Firewire 400 bus with the >> tar output going to a file in the mirror in order to try to have written >> something to most of the sectors on the four-drive mirror. I terminated >> tar after the empty space in the mirror got down to about 3% because the >> process had slowed to a crawl. (Apparently, space allocation in ZFS >> slows down far more than UFS2 when available space gets down to the last >> few percent.:-( ) > >ZFS's space allocation algorithm will have trouble (performance issues) >allocating new blocks long before you get a few percent free. This is >known behavior and the threshold for performance degradation varies with >work load and historical write patterns. My rule of thumb is that you >really do not want to go past 75-80% full, but I have seen reports over >on the ZFS list of issues with very specific write patterns and work >load with as little as 50% used. For your work load, writing very large >files once, I would expect that you can get close to 90% used before >seeing real performance issues. Thanks for that information. Yeah, I think I saw it starting to slow when it got into the low 90s% full, but I wasn't watching all of the time, so I don't know when it first became noticeable. Anyway, I'll keep those examples in mind for planning purposes. > >> Next, I ran a scrub on the mirror and, after the scrub finished, got >> the following output from a "zpool status -v". >> >> pool: testmirror >> state: ONLINE >> status: One or more devices has experienced an error resulting in data >> corruption. Applications may be affected. >> action: Restore the file in question if possible. Otherwise restore the >> entire pool from backup. >> see: http://illumos.org/msg/ZFS-8000-8A >> scan: scrub repaired 1.38M in 17h59m with 1 errors on Mon Sep 15 19:53:45 2014 > >The above means that ZFS was able to repair 1.38MB of bad data but still >ran into 1 situation (unknown size) that it could not fix. But I'm not sure that the repairs actually took. Read on. > >> config: >> >> NAME STATE READ WRITE CKSUM >> testmirror ONLINE 0 0 1 >> mirror-0 ONLINE 0 0 2 >> da1p5 ONLINE 0 0 2 >> da2p5 ONLINE 0 0 2 >> da5p5 ONLINE 0 0 8 >> da7p5 ONLINE 0 0 7 >> >> errors: Permanent errors have been detected in the following files: >> >> /backups/testmirror/backups.s2A > >And here is the file that contains the bad data. > Yes. There are only two files, and that one is the larger one and was written first. >> >> Note that the choices of recommended action above do *not* include >> replacing a bad drive and having ZFS rebuild its content on the >> replacement. Why is that so? > >Correct, because for some reason ZFS was not able to read enough of the >data without checksum errors to gibe you back your data in tact. Okay, laying aside the question of why no drive out of four in a mirror vdev can provide the correct data, so that's why a rebuild wouldn't work. Couldn't it at least give a clue about drive(s) to be replaced/repaired? I.e., the drive(s) and sector number(s)? Otherwise, one would spend a lot of time reloading data without knowing whether a failure at the same place(s) would just happen again. > >> Thinking, apparently naively, that the scrub had repaired some or >> most of the errors > >It did, 1.38MB worth. But it also had errors it could not repair. It *says* it did, but did it really? How does it know? Did it read the results of its correction back in from the drive(s) to see? > >> and wanting to know which drives had ended up with >> permanent errors, I did a "zpool clear testmirror" and ran another scrub. >> During this scrub, I got some kernel messages on the console: >> >> (da7:umass-sim5:5:0:0): WRITE(10). CDB: 2a 00 3b 20 4d 36 00 00 05 00 >> (da7:umass-sim5:5:0:0): CAM status: CCB request completed with an error >> (da7:umass-sim5:5:0:0): Retrying command >> (da7:umass-sim5:5:0:0): WRITE(10). CDB: 2a 00 3b 20 4d 36 00 00 05 00 >> (da7:umass-sim5:5:0:0): CAM status: CCB request completed with an error >> (da7:umass-sim5:5:0:0): Retrying command > >How many device errors have you had since booting the system / creating >the zpool ? Those were the first two times that I've gotten kernel error messages on any of those devices ever. My (non-ZFS) comparison results presented here some weeks ago showed that the errors found in the comparisons went undetected by hardware or software while the file was being written to disk. No errors were detected during readback either, except by the application (cmp(1)). > >> I don't know how to decipher these error messages (i.e., what do the hex >> digits after "CDB: " mean?) > >I do not know the specifics in this case, but whenever I have seen >device errors it has always been due to either bad communication with a >drive or a drive reporting an error. If there are ANY device errors you >must address them before you go any further. Yes, but I need to know what those messages actually say when I talk to manufacturers. For example, if they contain addresses of failed sectors, then I need to know what those addresses are if the manufacturers want me to attempt to reassign them. Also, if I tell them there are kernel messages, they want to look up Micro$lop messages, and when I point out that I don't use Micro$lop and that I run FreeBSD, they usually try to tell me that "We don't support that", so it really helps if I can translate the messages to them. IOW, I can't address the device errors if I don't know how to read the messages, which I'm hoping someone reading this may be able to help with. (I wish the FreeBSD Handbook had a comprehensive list of kernel messages and what they mean.) > >As an anecdotal note, I have not had terribly good luck with USB >attached drives under FreeBSD, especially under 9.x. I suspect that the >USB stack just can't keep up and ends up dropping things (or hanging). I >have had better luck with the 10.x release but still do not trust it for >high traffic loads. I have had no issues with SAS or SATA interfaces Okay. I'll keep that in mind for the future, but for now I'm stuck with 9.2 until I can get some stable disk space to work with to do the upgrades to amd64 and then to later releases. The way things have been going, I may have to relegate at least four 2 TB drives to paperweight supply and then wait until I can replace them with smaller capacity drives that will actually work. Also, I have four 2 TB drives in external cases that have only USB 3.0 interfaces on them, so I have no other way to connect them (except USB 2.0, of course), so I'm stuck with (some) USB, too. >(using supported chipsets, I have had very good luck with any of the >Marvell JBOD SATA controllers), _except_ when I was using a SATA port >multiplier. Over on the ZFS list the consensus is that port multipliers >are problematic at best and they should be avoided. What kinds of problems did they mention? Also, how are those Marvell controllers connected to your system(s)? I'm just wondering whether I would be able to use any of those models of controllers. I've not dealt with SATA port multipliers. Would an eSATA card with two ports on it be classed as a port multiplier? At the moment, all of my ZFS devices are connected by either USB 3.0 or Firewire 400. I now have an eSATA card with two ports on it that I plan to install at some point, which will let me move the Firewire 400 drive to eSATA. Should I expect any new problem for that drive after the change? > >> When it had finished, another "zpool status >> -v" showed these results. >> >> pool: testmirror >> state: ONLINE >> status: One or more devices has experienced an error resulting in data >> corruption. Applications may be affected. >> action: Restore the file in question if possible. Otherwise restore the >> entire pool from backup. >> see: http://illumos.org/msg/ZFS-8000-8A >> scan: scrub repaired 1.25M in 18h4m with 1 errors on Tue Sep 16 15:02:56 2014 > >This time it fixed 1.25MB of data and still had an error (of unknown >size) that it could not fix. Unfortunately, ZFS did not report the addresses of any of the errors. If there are hard errors, how can I find out where the bad sectors are located on each disk? It might be possible to reassign those sectors to spares if ZFS can tell me their addresses. > >> config: >> >> NAME STATE READ WRITE CKSUM >> testmirror ONLINE 0 0 1 >> mirror-0 ONLINE 0 0 2 >> da1p5 ONLINE 0 0 2 >> da2p5 ONLINE 0 0 2 >> da5p5 ONLINE 0 0 6 >> da7p5 ONLINE 0 0 8 > >Once again you have errors on ALL your devices. This points to a Why did it not fix them during the first scrub? >systemic problem of some sort on your system. On the ZFS list people >have reported bad memory as sometimes being the cause of these errors. I >would look for a system component that is common to all the drives and >controllers. How healthy is your power supply ? How close to it's limits >are you ? The box is mostly empty and nowhere near the power supply's capacity. The box and all other attached devices are plugged into a SmartUPS 1000, which is plugged into a surge protector. As for the health of the power supply, I guess I don't know how to check that, but everything else that depends upon the power supply seems to be working fine. > >> >> errors: Permanent errors have been detected in the following files: >> >> /backups/testmirror/backups.s2A >> >> So it is not clear to me that either scrub fixed *any* errors at >> all. > >Why is it not clear? The message from zpool status is very clear: It is not clear because I got similar results reported after two consecutive scrubs with no changes made by me in between them. If it really fixed all but one error during the first scrub, why are there still more errors for the second one to correct? Unless ZFS checks the results of its corrections, how can it know whether it really succeeded in fixing anything? > >scan: scrub repaired 1.25M in 18h4m with 1 errors on Tue Sep 16 15:02:56 >2014 > >There were errors that were repaired and an error that was not. Yes, like it said the first time. > >> I next ran a comparison ("cmp -z -l") of the original against the >> copy > >If you are comparing the file that ZFS reported was corrupt, then you >should not expect them to match. Well, you omitted the results of the comparison that I ran after the second scrub had completed. As I wrote before, + Another issue revealed above is that ZFS, in spite of having *four* + copies of the data and checksums of them, failed to detect any problem + while reading the data back for cmp(1), much less feed cmp(1) the correct + version of the data rather than a corrupted version. Similarly, the hard + error (not otherwise logged by the kernel) apparently encountered by + vm_pager resulted in termination of cmp(1) rather than resulting in ZFS + reading the page from one of the other three drives. I don't see how ZFS + is of much help here, so I guess I must have misunderstood the claims for + ZFS that I've read on this list and in the available materials on-line. Now, given that there were 10 errors widely separated in that file (before the kernel-detected error that killed cmp(1)) that went undetected by hardware, drivers, or ZFS when the file was written and also went undetected by ZFS when read back in, in spite of all the data copies and checksum copies, and in view of two consecutive scrubs without changes made between them to the data yielding nearly identical numbers of errors "fixed", I am skeptical of the claims for ZFS's "self-healing" ability. With access to four copies of each of those 10 data blocks and four copies of each of the checksums, why did ZFS detect nothing while reading the file? And in the case of the uncorrectable error, why could ZFS not find any copy of the data block that matched any copy of the checksum or even two matching copies of the data block, so that it could provide the correct data to the application program anyway, while logging the sector(s) involved in the block containing the uncorrectable error? If it can't do any of those things, why have redundancy? > >> [stuff deleted --SB] > >It sounds like you are really pushing this system to do more than it >reasonably can. In a situation like this you should really not be doing >anything else at the same time given that you are already pushing what >the system can do. > It seems to me that the only places that could fail to keep up would be the motherboard's chip(set) or one of the controller cards. The motherboard controller knows the speed of the memory, so it will only cycle the memory at that speed. The CPU, of course, should be at a lower priority for bus cycles, so it would just use whatever were left over. There is no overclocking involved, so that is not an issue here. The machine goes as fast as it goes and no faster. If it takes longer for it to complete a task, then that's how long it takes. I don't see that "pushing this system to do more than it reasonably can" is even possible for me to do. It does what it does, and it does it when it gets to it. Would I like it to do things faster? Of course, I would, but what I want does not change physics. I'm not getting any machine check or overrun messages, either. Further, because one of the drives is limited to 50 MB/s (Firewire 400) transfer rates, ZFS really can't go any faster than that drive. Most of the time, a systat vmstat display during the scrubs showed the MB/s actually transferred for all four drives as being about the same (~23 - ~35 MB/s). The scrubs took from 5% to 25% of one core's time, and associated kernel functions took from 0% to ~9% (combined) from other cores. cmp(1) took 25% - 35% of one core with associated kernel functions taking 5% - 15% (combined) from other cores. I used cpuset(1) to keep cmp(1) from bothering the mprime thread I cared about the most. (Note that mprime runs niced to 18, so its threads should not slow any of the testing I was doing.) It really doesn't look to me like an overload situation, but I can try moving the three USB 3.0 drives to USB 2.0 to slow things down even further. That leaves still unexplained ZFS's failure to make use of multiple copies for error correction during the reading of a file or to fix in one scrub everything that was fixable. >> >> Script started on Wed Sep 17 01:37:38 2014 >> [hellas] 101 % time nice +12 cpuset -l 3,0 cmp -z -l /backups/s2C/save/backups.s2A /backups/testmirror/backups.s2A > >This is the file the ZFS told you was corrupt, all bets are off. > There should be only one bad block because the scrubs fixed everything else, right? And that bad block is bad on all four drives, right? > > >> [point made again elsewhere deleted --SB] > >ZFS told you that file was corrupt. You are choosing to try to read it. >ZFS used to not even let you try to access a corrupt file but that >behavior was changed to permit people to try to salvage what they could >instead of write it all off. See what I wrote above. It was a *four-way mirror*, not an unreplicated pool. It strikes me as extremely unlikely that the *same* blocks would be damaged on *all four* drives. ZFS ought to be able to identify and provide the correct version from one or more blocks and checksums. > >> [text included in a quotation above deleted here --SB] > >I suggest that you are ignoring what ZFS is telling you, specifically >that your system is incapable of reliably write to and reading from >_any_ of the four drives you are trying to use and that there is a >corrupt file due to this and here it the name of that corrupt file. > >Until you fix the underlying issues with your system, ZFS (or any FS for >that matter) will not be of much use to you. It looks to me as nearly certain that the underlying issue is poor manufacturing standards for 2 TB drives. > >> I don't know where to turn next. I will try to call Seagate/Samsung >> later today again about the bad Samsung drive and the bad, refurbished >> Seagate drive, but they already told me once that having a couple of kB >> of errors in a ~1.08 TB file copy does not mean that the drive is bad. >> I don't know whether they will consider a hard write error to mean the >> drive is bad. The kernel messages shown above are the first ones I've >> gotten about any of the drives involved in the copy operation or the >> tests described above. > >The fact that you have TWO different drives from TWO different vendors >exhibiting the same problem (and to the same degree) makes me think that >the problem is NOT with the drives but elsewhere with your system. I >have started tracking usage an failure statistics for my personal drives >(currently 26 of them, but I have 4 more coming back from Seagate as Whooweee! That's a heap of drives! IIRC, for a chi^2 distribution, 30 isn't bad for a sample size. How many of those drives are of larger capacity than 1 TB? >warranty replacements). I know that I do not have a statistically >significant sample, but it is what I have to work with. Taking into >account the drive I have as well as the hundreds of drives I managed at >a past client, I have never seen the kind of bad data failures you are >seeing UNLESS I had another underlying problem. Especially when the >problem appears on multiple drives. I suspect that the real odds of >having the same type of bad data failure on TWO drives in this case is >so small that another cause needs to be identified. Recall that I had two 2 TB drives that failed this year at, IIRC, 11 and 13 months since purchase, which is why two of the drives I was testing in the mirror were refurbished drives (supplied under warranty). One of those drives was showing hard errors on many sectors for a while before it failed completely. Having two drives that are bad doesn't seem so unlikely, although having two drives (much less four!) with an identical scattering of bad sectors on each is rather a stretch. You are referring to the two drives that showed two checksum errors each in both post-scrub status reports? Yes, those were from two manufacturers, but the two drives with the greatest numbers of checksum errors, along with one of the drives showing only 2 checksum errors, were all from one manufacturer, who claims that such occurrences are "normal" for those drives because they have no parity checking or parity recording. That manufacturer does not suggest that there is anything wrong with the system to which they are attached. (By that, I mean that the guy at that manufacturer who spoke with me on the phone made those claims.) > >> If anyone reading this has any suggestions for a course of action >> here, I'd be most interested in reading them. Thanks in advance for any >> ideas and also for any corrections if I've misunderstood what a ZFS >> mirror was supposed to have done to preserve the data and maintain >> correct operation at the application level. > >The system you are trying to use ZFS on may just not be able to handle >the throughput (both memory and disk I/O) generated by ZFS without >breaking. This may NOT just be a question of amount of RAM, but of the >reliability of the motherboard/CPU/RAM/device interfaces when stressed. I did do a fair amount of testing with mprime last year and found no problems. I monitor CPU temperatures frequently, especially when I'm running a test like the ones I've been doing, and the temperatures have remained reasonable throughout. (My air-conditioning bill has not been similarly reasonable, I'm sorry to say.) That having been said, though, between your remarks and Andrew Berg's, there does seem cause to run another scrub, perhaps two, with those three drives connected via USB 2.0 instead of USB 3.0 to see what happens when everything is slowed down drastically. I'll give that a try when I find time. That won't address the ZFS-related questions or the differences in error rates on different drives, but might reveal an underlying system hardware issue. Maybe a PCIE2 board is too slow for USB 3.0, although the motherboard controller, BIOS, USB 3.0 controller, and kernel all declined to complain. If it is, then the eSATA card I bought (SATA II) would likely be useless as well. :-< >In the early days of ZFS it was noticed that ZFS stressed the CPU and >memory systems of a server harder than virtually any other task. > When would that have been, please? (I don't know much ZFS history.) I believe this machine dates to 2006 or more likely 2007, although the USB 3.0 card was new last year. The VIA Firewire card was installed at the same time as the USB 3.0 card, but it was not new at that time. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 12:06:46 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 99D9598B for ; Sun, 28 Sep 2014 12:06:46 +0000 (UTC) Received: from sdf.lonestar.org (mx.sdf.org [192.94.73.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "SDF.ORG" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 614FCA16 for ; Sun, 28 Sep 2014 12:06:45 +0000 (UTC) Received: from sdf.org (IDENT:bennett@sdf.lonestar.org [192.94.73.15]) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s8SC6huw022606 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Sun, 28 Sep 2014 12:06:43 GMT Received: (from bennett@localhost) by sdf.org (8.14.8/8.12.8/Submit) id s8SC6h3L017080; Sun, 28 Sep 2014 07:06:43 -0500 (CDT) From: Scott Bennett Message-Id: <201409281206.s8SC6h3L017080@sdf.org> Date: Sun, 28 Sep 2014 07:06:43 -0500 To: paul@kraus-haus.org Subject: Re: ZFS and 2 TB disk drive technology :-( User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 12:06:46 -0000 I wrote: > On Wed, 24 Sep 2014 11:24:35 -0400 Paul Kraus >wrote: >>What hardware are you running it on ? > > The CPU is a Q6600 running on a PCIE2 Gigabyte motherboard, whose model >number I did have written down around here somewhere but can't lay hands on >at the moment. I looked it up at the gigabyte.com web site, and it supposed >to be okay for a number of considerably faster CPU models. It has 4 GB of >memory, but FreeBSD ignores the last ~1.1 GB of it, so ~2.9 GB usable. It >has been running mprime worker threads on all four cores with no apparent >problems for almost 11 months now. Here's the motherboard model info. Gigabyte Technology Co., Ltd. G41M-ES2L Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 14:45:37 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B311ECC0 for ; Sun, 28 Sep 2014 14:45:37 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 627A99F1 for ; Sun, 28 Sep 2014 14:45:37 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s8SEjZq4053214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 28 Sep 2014 08:45:36 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s8SEjZxe053211; Sun, 28 Sep 2014 08:45:35 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 28 Sep 2014 08:45:35 -0600 (MDT) From: Warren Block To: Scott Bennett Subject: Re: ZFS and 2 TB disk drive technology :-( In-Reply-To: <201409281030.s8SAU8dR027634@sdf.org> Message-ID: References: <201409281030.s8SAU8dR027634@sdf.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 28 Sep 2014 08:45:36 -0600 (MDT) Cc: Paul Kraus , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 14:45:37 -0000 On Sun, 28 Sep 2014, Scott Bennett wrote: > On Wed, 24 Sep 2014 11:24:35 -0400 Paul Kraus > wrote: > Thanks for chiming in, Paul. > >> On 9/24/14 7:08, Scott Bennett wrote: >> >> >> >> What version of FreeBSD are you running ? > > FreeBSD hellas 9.2-STABLE FreeBSD 9.2-STABLE #1 r264339: Fri Apr 11 05:16:25 CDT 2014 bennett@hellas:/usr/obj/usr/src/sys/hellas i386 > >> What hardware are you running it on ? > > The CPU is a Q6600 running on a PCIE2 Gigabyte motherboard, whose model > number I did have written down around here somewhere but can't lay hands on > at the moment. sysutils/dmidecode will show that without having to open the case. From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 15:02:01 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E68F28D0 for ; Sun, 28 Sep 2014 15:02:01 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6EC02EDA for ; Sun, 28 Sep 2014 15:02:01 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id n15so2374956lbi.12 for ; Sun, 28 Sep 2014 08:01:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=qqVBgX/HZkMN36VZrmR6axAV7XFfZdP6DanWh6ShjZ8=; b=pCZTzpnUqkZUeOoJA422Ne3EGyPulW4R+3sH5oO9aZ3zIzM2mY9dwh1hxGa0ZxKiFV DZ3VGb9o2r93pmLqLDTRqdurTYuJYTk8wwTh07UD18DFgjxTPa9dWrM8PKPfyn66aK3N OBisIvvyHKuNDMVtKktVb4pn6lOHf9+9M6nB0zn9gKXZxEQTirMRs7h0V4UV+LezkirL bmJryN29cnyLq7RNw/Gl3Igw3bu69MBRojbJPl2d2np8qkKEUFVejwXTrLx182jbKVGQ 79AtvPYBxrRPbblISGvZsmAcYi1CZS8JTu+qVr194SUvIOPl48A/2KamEHJgnGUq783g ZClQ== MIME-Version: 1.0 X-Received: by 10.152.203.167 with SMTP id kr7mr33662932lac.9.1411916519255; Sun, 28 Sep 2014 08:01:59 -0700 (PDT) Received: by 10.152.19.6 with HTTP; Sun, 28 Sep 2014 08:01:59 -0700 (PDT) In-Reply-To: References: <23187F4C-0413-4F84-9C86-6EC1084C794C@btinternet.com> Date: Sun, 28 Sep 2014 11:01:59 -0400 Message-ID: Subject: Re: freebsd-update question From: "firmdog@gmail.com" To: FF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-questions@freebsd.org" , Dave X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 15:02:02 -0000 I just installed a brand new 8.3 box and got the same behavior. I see in my output below that I have to build or update my own kernel? # uname -a FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 # Starting the upgrade attempt: # freebsd-update -r 8.4-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching public key from update6.freebsd.org... done. Fetching metadata signature for 8.3-RELEASE from update6.freebsd.org... don= e. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. WARNING: This system is running a "xenhvm" kernel, which is not a kernel configuration distributed as part of FreeBSD 8.3-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running "/usr/sbin/freebsd-update install". The following components of FreeBSD seem to be installed: src/base src/bin src/cddl src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: kernel/generic world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 8.4-RELEASE from update6.freebsd.org... don= e. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 8.3-RELEASE for merging... done. Preparing to download files... done. Fetching 32149 patches.....10....20....30....40....50....60....70....80....= 90....100....110....120....130....140....150....160....170....180.... SNIP=E2=80=A6. done. Applying patches... Fetching 778 files... done. Attempting to automatically merge changes in files... done. The following file could not be merged automatically: /etc/mail/freebsd.cf Press Enter to edit this file in vi and resolve the conflicts manually... Then a bunch more of /etc/mail files and also a merge of /etc/master.passwd= : Then this: The following files will be updated as part of updating to 8.4-RELEASE-p16: Then I run this: # freebsd-update install Installing updates... Kernel updates have been installed. Please reboot and run "/usr/sbin/freebsd-update install" again to finish installing updates. # reboot #uname -a FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 On Sun, Sep 28, 2014 at 5:06 AM, FF wrote: > Can you provide the output of those commands? Freebsd-update is usually > pretty good about telling you what's wrong. > > Thanks > > On Sat, Sep 27, 2014 at 3:02 PM, firmdog@gmail.com > wrote: >> >> Yes I ran freebsd-update install. Then I rebooted. Then I did it again. >> Still at 8.3 >> On Sep 27, 2014 2:37 PM, "Dave" wrote: >> >> > On 27 September 2014 18:22:15 BST, "firmdog@gmail.com" >> > >> > wrote: >> >> >> >> Hi, >> >> >> >> Trying to use freebsd-update to go from 8.3 to 8.4 and I am doing thi= s: >> >> >> >> # freebsd-update -r 8.4-RELEASE upgrade >> >> # freebsd-update install >> >> # reboot >> >> >> >> After reboot I am still at 8.3-RELEASE FreeBSD 8.3-RELEASE #0 >> >> >> >> What am I doing wrong? >> >> ------------------------------ >> >> >> >> freebsd-questions@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> >> To unsubscribe, send any mail to >> >> "freebsd-questions-unsubscribe@freebsd.org" >> >> >> >> >> > Don't you need run rub "freebsd-update install"? >> > -- >> > Dave >> > >> > GPG/PGP ID: CDB94DA1 >> > >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" > > > > > -- > FF From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 15:21:29 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3B16EC4F for ; Sun, 28 Sep 2014 15:21:29 +0000 (UTC) Received: from p3plsmtpa08-05.prod.phx3.secureserver.net (p3plsmtpa08-05.prod.phx3.secureserver.net [173.201.193.106]) by mx1.freebsd.org (Postfix) with ESMTP id EFBD310A for ; Sun, 28 Sep 2014 15:21:28 +0000 (UTC) Received: from titania.midsummerdream.org ([107.197.157.90]) by p3plsmtpa08-05.prod.phx3.secureserver.net with id wfML1o0041xJNYB01fMMKB; Sun, 28 Sep 2014 08:21:21 -0700 X-Sender: oberon@midsummerdream.org From: Rob Rati Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Freebsd 9.3-RELEASE and Virtualbox Date: Sun, 28 Sep 2014 11:21:18 -0400 Message-Id: <57884ABE-A0AB-4EC1-8B94-8998389196CB@midsummerdream.org> To: freebsd-questions@freebsd.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 15:21:29 -0000 I've tried upgrading my 9.2-RELEASE system to 9.3-RELEASE a few times, = but each time I had to revert because starting any Virtualbox VMs causes = a kernel panic. I found this thread about the issue: = https://lists.freebsd.org/pipermail/freebsd-emulation/2014-August/011767.h= tml What I don't understand is why it is expected that the repository kernel = module wouldn't be in sync with the 9.3-RELEASE kernel. Is it because = the packages are relevant to all 9.x releases and there's no way to have = a kernel module work with them all? If so, why bother having a kmod = package at all? On a related note, how difficult is it to build the kernel module? I = have never built it from source in the past and don't even have kernel = sources installed. I use stock kernels from the releases. Are there = ways this build can get screwed up if options/packages aren't correct? Rob= From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 15:47:16 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 89739A8 for ; Sun, 28 Sep 2014 15:47:16 +0000 (UTC) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FBA7338 for ; Sun, 28 Sep 2014 15:47:16 +0000 (UTC) Received: by mail-qg0-f53.google.com with SMTP id e89so10378468qgf.26 for ; Sun, 28 Sep 2014 08:47:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=date:from:to:subject:message-id:in-reply-to:references:organization :mime-version:content-type:content-transfer-encoding; bh=RjHhTWEacJq0Jx2degMYhhyvJyQfd0Id7o3aFsV4Yn4=; b=aD0ryflbkkCpfiRBt4UG5JOPlL0RWoOnzYMkprNe7ra3W23NXM8yWYCZLigLdkDujD R+dBQUtFBVdc1X4NLUmh2HLuNwZtqEPWmrtfCTL2nZ756NYqLDmcQ6mEuNIbdEBZUml+ mpKRZa1IOsE/u7Nxrz3tE2qXm/GebHGK0nhm8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:organization:mime-version:content-type :content-transfer-encoding; bh=RjHhTWEacJq0Jx2degMYhhyvJyQfd0Id7o3aFsV4Yn4=; b=h7KLPeszkWXczKww+3AZ37kMF/Y8WdngIxVBWppc3+LXyIwDX2Swpzfp/Ihp4euF+x Z+oHyqioRF7LyX0Iwn+aAuV1E3teYk1hUOxKHMPQgp3EngHkNSUC6dHiiwzKtj07qQ/Q VPlo/NjMHWHQ3+ouEdL6fVhw0A6lLOI1LMsworXJvpwelLacbHsMLZklKFN8cpXb1AhJ NmnzgOc/+N3p0iXyb5QEvM0+catUFe7M7crH0FJTEgqOIId8ow2BVIRTDhQOTxSWnA7z T5oqTjZeAsbgRx4JR9gSpGSBly/RKnM8mkTVT6UcpgEe3yL/qyFWPD7zqiGRJHbGvOhX yaCQ== X-Gm-Message-State: ALoCoQlDqP2DLbIJbzxQmp/SGRxyaOtBZsXrTd+fpQTKmbUPkWnfugEUl/RZd4INZqEmSgmNAQFi X-Received: by 10.224.122.137 with SMTP id l9mr46393950qar.76.1411919235073; Sun, 28 Sep 2014 08:47:15 -0700 (PDT) Received: from Papi ([177.43.8.234]) by mx.google.com with ESMTPSA id v10sm9205827qar.10.2014.09.28.08.47.13 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Sep 2014 08:47:14 -0700 (PDT) Date: Sun, 28 Sep 2014 12:47:29 -0300 From: Mario Lobo To: freebsd-questions@freebsd.org Subject: Re: Problems starting tor service .... Message-ID: <20140928124729.73ab0725@Papi> In-Reply-To: <5427000C.4040002@hiwaay.net> References: <20140928004052.C49907@sola.nimnet.asn.au> <5426FA18.1080209@hiwaay.net> <5426FDEA.2070803@hiwaay.net> <5427000C.4040002@hiwaay.net> Organization: BSD X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 15:47:16 -0000 On Sat, 27 Sep 2014 13:21:00 -0500 "William A. Mahaffey III" wrote: > On 09/27/14 13:11, William A. Mahaffey III wrote: > > On 09/27/14 12:55, William A. Mahaffey III wrote: > >> On 09/27/14 10:20, Ian Smith wrote: > >>> In freebsd-questions Digest, Vol 538, Issue 11, Message: 6 > >>> On Sat, 27 Sep 2014 06:43:16 +0200 Polytropon > >>> wrote: > >>> > >>> > The important information is this: > >>> > > >>> > On Fri, 26 Sep 2014 22:19:07 -0500, William A. Mahaffey III > >>> > wrote: > >>> > > # tor_enable (bool): Set it to "YES" to enable tor. > >>> Default: NO > >>> > > # tor_conf (str): Points to your torrc file. > >>> > > # Default: /usr/local/etc/tor/torrc > >>> > > # tor_user (str): Tor daemon user. Default: _tor > >>> > > # tor_datadir (str): Tor datadir. Default: /var/db/tor > >>> > > # tor_logfile (str): Tor log file. Default: /var/log/tor > >>> > > # tor_loglevel (str): Tor log severity level. Default: > >>> > > notice > >>> > [snip] > i.e. it is still using the old OpenSSL .... No biggie (& possibly > pilot error), but seems a bit off .... > Hi William; What follows is just about all I can add to help out. I hope this helps. Here is what I got running: #### torrc SocksPort 9050 SocksListenAddress 127.0.0.1 SocksPolicy accept 127.0.0.1/32 SocksPolicy reject * ReachableDirAddresses *:80 ReachableDirAddresses *:443 #HttpProxy 10.14.200.245:7777 #HttpsProxy 10.14.200.245:7777 KeepalivePeriod 30 mapaddress 10.40.40.40 mejokbp2brhw4omd.onion mapaddress 10.40.40.40 5t7o4shdbhotfuzp.onion # Log debug file /var/log/tor/debug.log [~]>ls -l /var/log/ drwxr-xr-x 2 _tor _tor 512 Jun 8 2013 tor [~]>ls -l /var/log/tor/ total 452 -rw-r--r-- 1 _tor _tor 69246 Jun 8 2013 debug.log -rw-r--r-- 1 _tor _tor 374478 Sep 28 12:31 notices.log [~]>ls -l /var/db drwx------ 3 _tor _tor 512 Sep 28 12:31 tor [~]>ls -l /var/db/tor/ total 6656 -rw------- 1 _tor _tor 19391 Sep 5 07:42 cached-certs -rw------- 1 _tor _tor 1229433 Sep 28 11:29 cached-microdesc-consensus -rw------- 1 _tor _tor 2984111 Sep 22 18:41 cached-microdescs -rw------- 1 _tor _tor 2487055 Sep 28 12:32 cached-microdescs.new drwx------ 2 _tor _tor 512 Jun 8 2013 data -rw------- 1 _tor _tor 0 Sep 28 12:30 lock -rw------- 1 _tor _tor 9258 Sep 28 12:30 state [~]>ps axww | grep tor 1007 ?? S 0:03.08 /usr/local/bin/tor -f /usr/local/etc/tor/torrc --PidFile /var/run/tor/tor.pid --RunAsDaemon 1 --DataDirectory /var/db/tor --+Log notice file /var/log/tor/notices.log [~]>cat /etc/rc.conf | grep tor tor_enable=YES [~]>tor --version Sep 28 12:45:20.665 [notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on FreeBSD. Sep 28 12:45:20.665 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Tor version 0.2.3.25 (git-17c24b3118224d65). -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winblows FREE) "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 16:21:17 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28B168C9 for ; Sun, 28 Sep 2014 16:21:17 +0000 (UTC) Received: from nm6-vm3.bullet.mail.ir2.yahoo.com (nm6-vm3.bullet.mail.ir2.yahoo.com [212.82.96.119]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 656928F6 for ; Sun, 28 Sep 2014 16:21:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.es; s=s2048; t=1411921070; bh=O+/BeaeKVa/ZXuEOVqzUY86SgKkWseDYLAXXqWLe17Q=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Date:From:To:Subject:Message-Id:In-Reply-To:References:X-Mailer:Disposition-Notification-To:Mime-Version:Content-Type:Content-Transfer-Encoding:From:Subject; b=ai41Ccf0phYDDeh4BD2e3kaH0Z7Ib7LRfv2hWq9HQjNs5TX/F791xlszUh7p48cNBfoX0JAvg9r2/Y+YH5m85Flm0Ojnn1LkDwqOd8KCk8dLbGzZLmFb8HL/EyTd6etQAPmaKoGrxIWRseepmT8WvumBYyNM956ntYMFjOcimThqSZnZOyJAe4+ps+rHO9ghEl6ydCJyLhH3BWvixHEoEwqo6GaTZEXGEO2KF7znhVnNRL2d0Zdmkof5ntRJ+t5Hd1IF2ylRXVtoox13ZCqBIja/PkXedGdUPl/HkyCMiLKTUDVwsD0JiXgSDrfbZQgCTQ1Luck+qSu9xYJDKUvsMw== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.es; b=DbTFEYlWWJzup3971yr/qbOT3ZK9kjV/vB8azeHpSkMgAyaf56QlQJlOPWy0MM5E3c4IsPVUHN7zodmNdWiRTDpQ/5V4GyBt9hXJHgfnm0MtjQy3B7xKvHTuBeZxPcc0VbdVn56PwRiwtCRdIIkuyfW8z9+6VlCpkJX8KQ7f4kGAFgxfAXtTWz+WiVQCcSFjiAnjoqtn/kK/RnQNOggubtqDtfB2H8t4L+Uhni2m71y9MpISginrSqmzSn7EW3majst8Aa6rR4TilNO1Mxo7k/H+f5iP96VbEyy06aqJtvZ0hVqn9bV5EfTqkOyFNKZmXtjPevhxRri2eKWQ2Jkq0g==; Received: from [212.82.98.48] by nm6.bullet.mail.ir2.yahoo.com with NNFMP; 28 Sep 2014 16:17:50 -0000 Received: from [46.228.39.99] by tm1.bullet.mail.ir2.yahoo.com with NNFMP; 28 Sep 2014 16:17:50 -0000 Received: from [127.0.0.1] by smtp136.mail.ir2.yahoo.com with NNFMP; 28 Sep 2014 16:17:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.es; s=s1024; t=1411921070; bh=O+/BeaeKVa/ZXuEOVqzUY86SgKkWseDYLAXXqWLe17Q=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Date:From:To:Subject:Message-Id:In-Reply-To:References:X-Mailer:Disposition-Notification-To:Mime-Version:Content-Type:Content-Transfer-Encoding; b=zNtwnjTCBrYBqB9PwhWdS/dH9V2DQLJGrLZq+rqyUjHBWsEbc+RcShV8nmCUBn4XshNJna3xIbkIrLkgbehZIxsZ9J0Xy6lNdNmVH2eB5pRspgVQ8GFEbNcStAKRwNexeZyuZiKxkNE7CRu7BehUBu9aEyZg9phG4n63EJv+Zqc= X-Yahoo-Newman-Id: 15055.45656.bm@smtp136.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 0ZM81CYVM1mRY9ayYrOwf.qm1dhKnjTWIB8gfCJzRcUmQtz FLPoajcYVMtdK.0MZc1gjlprdZFJG6dd8UCXLtm3sNAIgXb5IoMGk8zjJO0v cUTrakBkAKMlKL7Jb8La3niPIfuR3kMCeDNjyhRTW21sxrWGyRbj0bMBygwB UjYX.FHHEW1cOnLgkr6oonYEXYAEknIsUCeNuh1XF..x4osyaTRQJyzDEPV4 MXCH7aI5es5sSNHsdGTzoFaugjFZtcL4oOCybVG5RPfDVb0BeXKc2E1oHvyY UDN_5NKRyHppdgMglzs9Oa.KCKdwm_CD0g8tniZlU190nxhszaNHOUY3R4Ak MGOhmxYRuT2k4VwAP4Kuc5yD.gwj9BqJ5HiaCBE0W5zaBhE6nw14hbW3j3VG AuIIwtYEs.ecnCINQVs1I7TDyWFJrwgWHTTgVzBxw4My_D4hHGx0urVYMlGs kwdigD8RLqoFsiwsKBqH8JVfhoml3DrfHmp2Dq9YiKDmPLTzxSt5YsHk81yH niFFbd5Z4i9lNIRMoDZdgn5DntYa0vHx3QfMbhNZCSaFcAFkE2TeMdnWtdx1 43aKuEYUZ9SO5fybmJILSUV3eHUFUkM5e3BIYGY75NPcDp.Mv_8YTr0udmvZ wAP_V2vVITw-- X-Yahoo-SMTP: mX392iiswBAeJNdO_s.EW62LZDJR Date: Sun, 28 Sep 2014 18:18:21 +0200 From: Eduardo Morras To: freebsd-questions@freebsd.org Subject: Re: Freebsd 9.3-RELEASE and Virtualbox Message-Id: <20140928181821.76adad527982addeac22ceb5@yahoo.es> In-Reply-To: <57884ABE-A0AB-4EC1-8B94-8998389196CB@midsummerdream.org> References: <57884ABE-A0AB-4EC1-8B94-8998389196CB@midsummerdream.org> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd9.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 16:21:17 -0000 On Sun, 28 Sep 2014 11:21:18 -0400 Rob Rati wrote: > I've tried upgrading my 9.2-RELEASE system to 9.3-RELEASE a few > times, but each time I had to revert because starting any Virtualbox > VMs causes a kernel panic. I found this thread about the issue: > > https://lists.freebsd.org/pipermail/freebsd-emulation/2014-August/011767.html > > What I don't understand is why it is expected that the repository > kernel module wouldn't be in sync with the 9.3-RELEASE kernel. Is it > because the packages are relevant to all 9.x releases and there's no > way to have a kernel module work with them all? If so, why bother > having a kmod package at all? Did you update /usr/src to 9.3 too? Kernel module needs to use some /usr/src source code to compile and the resulting kernel module will work only on that /usr/src version kernel. > On a related note, how difficult is it to build the kernel module? I > have never built it from source in the past and don't even have > kernel sources installed. I use stock kernels from the releases. > Are there ways this build can get screwed up if options/packages > aren't correct? > > Rob --- --- Eduardo Morras From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 16:33:27 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94875BC2 for ; Sun, 28 Sep 2014 16:33:27 +0000 (UTC) Received: from BLU004-OMC4S17.hotmail.com (blu004-omc4s17.hotmail.com [65.55.111.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50C8E9C1 for ; Sun, 28 Sep 2014 16:33:26 +0000 (UTC) Received: from BLU437-SMTP4 ([65.55.111.136]) by BLU004-OMC4S17.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22724); Sun, 28 Sep 2014 09:32:19 -0700 X-TMN: [YukNTsG9Kvnt4C7QlcxKe0cE1SoWU5Kq] X-Originating-Email: [carmel_ny@outlook.com] Message-ID: Date: Sun, 28 Sep 2014 12:32:17 -0400 From: Carmel NY To: User questions Subject: update to linux_base-c6 Organization: seibercom NET X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 28 Sep 2014 16:32:19.0159 (UTC) FILETIME=[C595EE70:01CFDB39] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 16:33:27 -0000 Sun, 28 Sep 2014 12:30:18 -0400 I want to update to emulators/linux_base-c6. According to UPDATING, I should remove all linux-f10 ports. In my case, that would be: linux-f10-atk-1.24.0_1 linux-f10-cairo-1.8.0_3 linux-f10-cups-libs-1.3.11_1 linux-f10-curl-7.19.6_1 linux-f10-cyrus-sasl2-2.1.22_2 linux-f10-expat-2.0.1_1 linux-f10-flashplugin-11.2r202.400 linux-f10-fontconfig-2.6.0_1 linux-f10-gdk-pixbuf-0.22.0_1 linux-f10-gnutls-2.4.2_1 linux-f10-gtk2-2.14.7_5 linux-f10-jpeg-6b linux-f10-libgcrypt-1.4.4 linux-f10-libgpg-error-1.6_1 linux-f10-libssh2-0.18 linux-f10-libtasn1-1.5_1 linux-f10-libxml2-2.7.3_2 linux-f10-nspr-4.7.6_1 linux-f10-nss-3.12.3.99.3_1 linux-f10-openldap-2.4.12_1 linux-f10-openssl-0.9.8g linux-f10-pango-1.28.3_1 linux-f10-png-1.2.37_2 linux-f10-sqlite3-3.5.9_2 linux-f10-tiff-3.8.2 linux-f10-xorg-libs-7.4_1 However, in addition to them, I have the following ports that depend on linux_base-f10: acroread9-9.5.5_1 acroreadwrapper-0.0.20130208 linux-libgtkembedmoz-0.0.20100806 nspluginwrapper-1.4.4_4 nvidia-driver-331.67_1 My question is, after removing the linux-f10 ports and the linux_base-f10, making the necessary changes to the /etc/makefile, etcetera and then installing linux_base-c6, do I have to then install the corresponding c6 ports for the f10 ports that have deleted or is that done automatically I assume, that I have to rebuild the remaining ports that use to depend on linux_base-f10? -- Carmel From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 17:26:47 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D7228B92 for ; Sun, 28 Sep 2014 17:26:47 +0000 (UTC) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.52.97]) by mx1.freebsd.org (Postfix) with ESMTP id 9AE25E42 for ; Sun, 28 Sep 2014 17:26:47 +0000 (UTC) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 2EABECB8CA0; Sun, 28 Sep 2014 12:26:41 -0500 (CDT) Received: from 76.192.184.214 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Sun, 28 Sep 2014 12:26:41 -0500 (CDT) Message-ID: <50282.76.192.184.214.1411925201.squirrel@cosmo.uchicago.edu> In-Reply-To: References: <23187F4C-0413-4F84-9C86-6EC1084C794C@btinternet.com> Date: Sun, 28 Sep 2014 12:26:41 -0500 (CDT) Subject: Re: freebsd-update question From: "Valeri Galtsev" To: "firmdog@gmail.com" Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Dave , FF , "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 17:26:47 -0000 On Sun, September 28, 2014 10:01 am, firmdog@gmail.com wrote: > I just installed a brand new 8.3 box and got the same behavior. I see > in my output below that I have to build or update my own kernel? > > > # uname -a > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 > # > > Starting the upgrade attempt: > > # freebsd-update -r 8.4-RELEASE upgrade > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > Fetching public key from update6.freebsd.org... done. > Fetching metadata signature for 8.3-RELEASE from update6.freebsd.org... > done. > Fetching metadata index... done. > Fetching 2 metadata files... done. > Inspecting system... done. > > WARNING: This system is running a "xenhvm" kernel, which is not a > kernel configuration distributed as part of FreeBSD 8.3-RELEASE. > This kernel will not be updated: you MUST update the kernel manually > before running "/usr/sbin/freebsd-update install". > > The following components of FreeBSD seem to be installed: > src/base src/bin src/cddl src/contrib src/crypto src/etc src/games > src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue > src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin > world/base world/dict world/doc world/games world/info world/manpages > world/proflibs > > The following components of FreeBSD do not seem to be installed: > kernel/generic world/catpages > > Does this look reasonable (y/n)? y > > Fetching metadata signature for 8.4-RELEASE from update6.freebsd.org... > done. > Fetching metadata index... done. > Fetching 1 metadata patches. done. > Applying metadata patches... done. > Fetching 1 metadata files... done. > Inspecting system... done. > Fetching files from 8.3-RELEASE for merging... done. > Preparing to download files... > done. > Fetching 32149 > patches.....10....20....30....40....50....60....70....80....90....100....110....120....130....140....150....160....170....180.... > SNIPâ€Ĥ. > done. > Applying patches... > Fetching 778 files... done. > Attempting to automatically merge changes in files... done. > > The following file could not be merged automatically: /etc/mail/freebsd.cf > Press Enter to edit this file in vi and resolve the conflicts > manually... > > Then a bunch more of /etc/mail files and also a merge of > /etc/master.passwd: > > Then this: > > The following files will be updated as part of updating to > 8.4-RELEASE-p16: > > Then I run this: > > # freebsd-update install > Installing updates... > Kernel updates have been installed. Please reboot and run > "/usr/sbin/freebsd-update install" again to finish installing updates. > > # reboot > In last message before reboot it instructed to "reboot then run /usr/sbin/freebsd-update install again". Did you run "freebsd-update install" after reboot? Valeri > > #uname -a > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 > > > > > > > On Sun, Sep 28, 2014 at 5:06 AM, FF wrote: >> Can you provide the output of those commands? Freebsd-update is usually >> pretty good about telling you what's wrong. >> >> Thanks >> >> On Sat, Sep 27, 2014 at 3:02 PM, firmdog@gmail.com >> wrote: >>> >>> Yes I ran freebsd-update install. Then I rebooted. Then I did it again. >>> Still at 8.3 >>> On Sep 27, 2014 2:37 PM, "Dave" wrote: >>> >>> > On 27 September 2014 18:22:15 BST, "firmdog@gmail.com" >>> > >>> > wrote: >>> >> >>> >> Hi, >>> >> >>> >> Trying to use freebsd-update to go from 8.3 to 8.4 and I am doing >>> this: >>> >> >>> >> # freebsd-update -r 8.4-RELEASE upgrade >>> >> # freebsd-update install >>> >> # reboot >>> >> >>> >> After reboot I am still at 8.3-RELEASE FreeBSD 8.3-RELEASE #0 >>> >> >>> >> What am I doing wrong? >>> >> ------------------------------ >>> >> >>> >> freebsd-questions@freebsd.org mailing list >>> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> >> To unsubscribe, send any mail to >>> >> "freebsd-questions-unsubscribe@freebsd.org" >>> >> >>> >> >>> > Don't you need run rub "freebsd-update install"? >>> > -- >>> > Dave >>> > >>> > GPG/PGP ID: CDB94DA1 >>> > >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscribe@freebsd.org" >> >> >> >> >> -- >> FF > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 17:49:11 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 471D21E6 for ; Sun, 28 Sep 2014 17:49:11 +0000 (UTC) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7BCCFF6 for ; Sun, 28 Sep 2014 17:49:10 +0000 (UTC) Received: by mail-la0-f44.google.com with SMTP id gi9so6522297lab.31 for ; Sun, 28 Sep 2014 10:49:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=XlO3GPv661zSk99ddAzNLgWIokTMvXHfjda6KnlNGBk=; b=YfATr7G6u7mZdaFFLbOYACqgQp5yQRzdyUQh67et47ngHfkkJUXeFwWt4q1hFrtYOf JMBeTpXHyb54lPUa/OB2ZILvSWShRdoPfLI+Av0bPo2xL6a7SWs2+6kAj0+Un9flqaHq zRb0h99IW4un8vzel/+/4DlIpnjhYxiYGhLxom86VwEWQVOr4Bf+l9P3PnpxpXgcN6Dg vo4Q56Qbxrt4uE1Jy54gQz47mPSM9l4RcayZxx/UBxB/hbJhro1DCmV9fvllFfeUVTX8 5riLz5gMhjL7hZYFYHO0J/ctpnAMc9ICZiiyyb5ChzQ0VHDxlBEfHeDlFqLHJyTflhJo W/Bg== MIME-Version: 1.0 X-Received: by 10.112.83.235 with SMTP id t11mr673313lby.101.1411926548617; Sun, 28 Sep 2014 10:49:08 -0700 (PDT) Received: by 10.25.162.145 with HTTP; Sun, 28 Sep 2014 10:49:08 -0700 (PDT) Date: Sun, 28 Sep 2014 10:49:08 -0700 Message-ID: Subject: ZFS root failure after 9.2 -> 9.3 ugprade From: Patrick Gibson To: FreeBSD Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 17:49:11 -0000 I just did a freebsd-update upgrade on a 9.2 system with zfsroot and now when it boots, I get: Booting from Hard Disk... / Can't find /boot/zfsloader FreeBSD/x86 boot Default: disk0:/boot/kernel/kernel boot: \ Can't find /boot/kernel/kernel I've tried booting from a 9.3 install disc and going into the LiveCD and reinstalling the bootloader with: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 Which says it's installed correctly, but still won't boot. Any advice would be greatly appreciated. From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 18:26:06 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0723A153 for ; Sun, 28 Sep 2014 18:26:06 +0000 (UTC) Received: from nm5-vm8.access.bullet.mail.gq1.yahoo.com (nm5-vm8.access.bullet.mail.gq1.yahoo.com [216.39.63.213]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD898626 for ; Sun, 28 Sep 2014 18:26:05 +0000 (UTC) Received: from [216.39.60.176] by nm5.access.bullet.mail.gq1.yahoo.com with NNFMP; 28 Sep 2014 18:24:23 -0000 Received: from [216.39.60.252] by tm12.access.bullet.mail.gq1.yahoo.com with NNFMP; 28 Sep 2014 18:24:23 -0000 Received: from [127.0.0.1] by omp1023.access.mail.gq1.yahoo.com with NNFMP; 28 Sep 2014 18:24:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 806853.59369.bm@omp1023.access.mail.gq1.yahoo.com Received: (qmail 94540 invoked by uid 60001); 28 Sep 2014 18:24:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1411928663; bh=q6rdIwwkZdgvEJSJFvrJ6+c2BjabNPeC37i2lrmLDaE=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=MiDOH3Ky2lbiqCctYGARtf2oNdGuAkttDkRp3JTa7tWCexjHig3R0gE+BLH4UsGQ3Mdqs9LH6+tyLIgJVOGwZgwwsBgvuOGy26pdy8amPyamayPVPtTL3O5Vxf1f5VQPvpTLET1znSoXSuXyqjY40U4Ql1Io/DejIPigYVaUGvM= X-YMail-OSG: QkPYOewVM1nKrIQ4eIb3hMiSYzqrf9k0ROXFlkCvsTZT9lP lKYhko2TuTDIhGwoq3FOnsOdHV8ZVg7boX2nRi7eEerUMjM9bIkOiSZYff6O lVNQAu2MALUTzoN8gbMR529KK9oyfU9lWnFLkxkxrIzuusEIv7X5N8Xc5Vmk iSs1ku9MJORECCE2tC1yDOLLYA9sVlU1CvrvOKUtp.3uzpTmBccug6I8g17j Isc.metmw9yPhHcA5Ks8jXIO1rB3903UmRMl.pQz0h_XwBwvtxYsJHDuxJ5G awznfZEexQfx3Bmoa3CxM_eTmnNq6fAotqJYLimoI75490ZDomS6v_cM5cyn 5E3FZ_qZZmedJdIdAl67ZA26t3VQkZbU1CZWDseJdXmE3RI8CJBgUTdz821B 58PcO5GJa0sUqRGl8njR2IvK5ZkaJuf_jnoHpXS3cOGIWygtO_J32woRDXdN ogrfD_5RS5Ibz.sxupQDcT1uN1HnQq0blGk2nlEelUXUOeZjaftviMhy28zw Tqa3MPPxe1XQV5TzlhTmYX3n.GU.OghzchOFEZuCHLJEn8YWKthOxmOR1N7L 8kJvxhQbb9A-- Received: from [162.239.0.170] by web180901.mail.ne1.yahoo.com via HTTP; Sun, 28 Sep 2014 11:24:22 PDT X-Rocket-MIMEInfo: 002.001, Tm8sIEJJT1MgYm9vdCBpcyBjb21wbGV0ZWx5IGlycmVsZXZhbnQgdG8gdGhpcyBwcm9ibGVtLiAKCkl0IGxvb2tzIGxpa2UgSSBoYXZlIHRvIHJlLWFkZHJlc3MgdGhpcyBpc3N1ZSBkZWJhdGVkIDE1LTIwIHllYXJzIGFnby4KCkZpcnN0IG9mIGFsbCwgbGV0J3MgY2xlYXIgQklPUyBxdWVzdGlvbiBzbyB5b3Ugd2lsbCBub3QgYXJndWUgaXQgYWdhaW4uCkJJT1MgYm9vdCBzZXF1ZW5jZSBjYW4gYmUgc3BlY2lmaWVkIGluIGFueSBvcmRlciwgYW5kIGl0IGJvb3RzIGRlc2lyZWQgIGRyaXZlIGNvcnJlY3RseS4BMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 References: <1411851225.9364.YahooMailNeo@web180902.mail.ne1.yahoo.com> Message-ID: <1411928662.22540.YahooMailNeo@web180901.mail.ne1.yahoo.com> Date: Sun, 28 Sep 2014 11:24:22 -0700 From: Jin Guojun Reply-To: Jin Guojun Subject: Re: Inproper ada# assignment in 10-BETA2 To: Mehmet Erol Sanliturk In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "hackers@freebsd.org" , questions freebsd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 18:26:06 -0000 No, BIOS boot is completely irrelevant to this problem. It looks like I have to re-address this issue debated 15-20 years ago. First of all, let's clear BIOS question so you will not argue it again. BIOS boot sequence can be specified in any order, and it boots desired drive correctly. If not, 10.1-BETA2 will not be loaded, and we will not see this problem, period. After 10.1-BETA2 is loaded and booted, it enumerates drive(s) dynamically to assign ID to ada or da node. Kernel clearly knows which drive is ad1, 2, 3, ..., but it does not assigned proper ID to existing drive(s) for ada and da nodes. That is, ad note IDs are still correct, but ada and da node IDs are wrong. The dynamic enumeration is likely used for moving a boot drive from on system to another or from one bus to another without manually modifying fstab entries. That is, this mechanism wants to ensure no matter where this drive is plugged in, Boot drive should be always enumerated as ID 0 or the ID installation assigned to. How to ensure this? For boot drive, this is relatively easy -- the boot drive is always this first one in general, so this drive should always enumerated as ada0 or da0. If installation has assigned drive ID to not 0 somehow, then generic enumeration apply. Generic enumeration is drive serial number (S#) based enumeration mechanism, which has been used for at least two decades. For example, if two drives installed and their S# are AAAA and XXXXX (boot drive), regardless what SATA port they resides at -- AAAA at ad9 and XXXXX at ad5, We knew installation will likely name drive XXXXX as ada0 and AAAA as ada1. In fixed fashion, drive XXXXX is ad5 and AAAA is ad9, when a new drive is inserted as ad0, we knew drive XXXXX will be still ad5 and boot should not fail. But in current 10.1-BETA2, the new drive is likely will be ada0, drive XXXXX will be ada1, and AAAA will be ada2, then boot will fail. In case if new drive is inserted as ad8, drive XXXXX will remain as ada0 but AAAA will be ada21. Even though boot will succeed in this case, but mounting drive AAAA will fail. The S#-based enumeration will record the S# for corresponding device ID in a dynamic boot configuration file, which is used in boot time to determine what device ID should be assigned to each drive. After existing drive ID has been enumerated, any new drive(s) will be given a unused ID sequentially. This ensures that existing drive(s) will always get device ID originally assigned to, so the disk mounting operation will never fail no matter where a disk drive (has FreeBSD already installed) is plugged in. Hopefully, this explains what is correct the dynamic enumeration operation. In old time, we have a mechanisms to alter the dynamic enumeration to fixed one, but I do not know if this mechanism is still in 10.x-R. Because it looks like that current developers have no knowledge about this concept, I am going to open a bug to track this problem again soon, unless I will hear if we have a work around for this problem. On Saturday, September 27, 2014 3:15 PM, Mehmet Erol Sanliturk wrote: On Sat, Sep 27, 2014 at 1:53 PM, Jin Guojun wrote: Installed 10-BETA2 on SATA port 4 (ad8) and then added another SATA port 3 (ad6), the system has not correctly enumerate the ada # for the boot device. >As original boot (without the second SATA drive), the ad8 is enumerated as ada0 -- the boot drive: > >Sep 24 22:51:30 R10-B2 kernel: ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 >Sep 24 22:51:30 R10-B2 kernel: ada0: ATA-8 SATA 2.x device >... >Sep 24 22:51:30 R10-B2 kernel: ada0: Previously was known as ad8 > > >However, after added another SATA drive (ad6), this new drive is assigned to ada0, but ad8 has changed to ada1. This is incorrect dynamic device assignment. FreeBSD has kept using fixed disk ID assignment due to the same problem introduced in around 4-R (or may be slightly later), and after a simple debate, a decision was made to use fixed drive ID to avoid such hassle. > >If now we want to use dynamic enumeration for drive ID# assignment, this has to be done correctly -- boot drive MUST assigned to 0 or whatever the # as installation assigned to; otherwise, adding a new drive will cause system not bootable, or make other existing drive not mountable due to enumeration # changes. > >Has this been reported as a known problem for 10-R, or shall I open a bug to track? > >-Jin > One point should be checked : On mainboards SATA ports are numbered from 0 or 1 to upward . BIOS always uses first SATA drive for boot . This is NOT related to the operating system . Therefore , it is necessary to check port numbers of existing drives and the bootable SATA drive should be connected to the smallest numbered SATA port among existent drives . For example , assume bootable drive is connected to SATA port 2 . New drive should be connected to a higher numbered SATA port . If there are only two SATA ports , then bootable drive should be connected to the first SATA port . If mainboard BIOS allows definition of any SATA port for boot , and bootable SATA port and drive is specified in there , again it may boot from that drive . Up to now , I did not see any BIOS which supplies such an ordering among SATA ports . Please check your BIOS for such a feature . If it is present you may use it , otherwise it is necessary to reconnect SATA cables . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 18:36:14 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E97F04CD for ; Sun, 28 Sep 2014 18:36:14 +0000 (UTC) Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A64C1768 for ; Sun, 28 Sep 2014 18:36:14 +0000 (UTC) Received: by mail-yh0-f48.google.com with SMTP id c41so1259713yho.21 for ; Sun, 28 Sep 2014 11:36:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rvfzoNOlKS1SFKl7vjVC5pxd5OXhgsyRC2nMf93qoxs=; b=AGYxm5+8yGkHTfTzVO64gL5ZJuo6L/gU0F+Jglg2EW3pZdFdJdwffn1l4F7Yg0/vQz XjbLZlsgrx3KlfeoRSZcfWHZ2G0MEdUF7H2v/8VERk0RVLwQnhBWG0/20erz23QhKRSl nUtjKf2ORWBftmR5SPOwNS3D/V70jPXvNCfdL8xbe33ULbpRcOKeWoFpswkj6tDqt5HG E3S1XTzKAsb9xg8gQ3dt3R3CZT09nwXJsGj47ni/SXWQnsKzDj8uJbZdoqJYgRDpLsRq YMKNq8PfWuiTKoBU6sFb6StaD4/Z/htUD+iRxiDSN3qJhpnWNJ1NvU87xQX1QmY1jcMG 3lRg== MIME-Version: 1.0 X-Received: by 10.236.164.38 with SMTP id b26mr4168296yhl.2.1411929373710; Sun, 28 Sep 2014 11:36:13 -0700 (PDT) Received: by 10.170.150.213 with HTTP; Sun, 28 Sep 2014 11:36:13 -0700 (PDT) In-Reply-To: <50282.76.192.184.214.1411925201.squirrel@cosmo.uchicago.edu> References: <23187F4C-0413-4F84-9C86-6EC1084C794C@btinternet.com> <50282.76.192.184.214.1411925201.squirrel@cosmo.uchicago.edu> Date: Sun, 28 Sep 2014 14:36:13 -0400 Message-ID: Subject: Re: freebsd-update question From: FF To: galtsev@kicp.uchicago.edu Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "firmdog@gmail.com" , "freebsd-questions@freebsd.org" , Dave X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 18:36:15 -0000 So your kernel won't be updated because you are running a custom kernel. Your uname is based on the running kernel. If you want to confirm that you've in fact updated, you can reboot to the GENERIC kernel which will confirm you are at 8.4 or whatever. FreeBSD update is a binary update based on the release versions -- deviate from them and it doesn't break, but it can't touch those files. Since you know enough to put a custom kernel on there, you should follow the source rebuild instructions which would be basically be to svn down the whole 8.4 source tree, make the world, make the kernel and install it, reboot, and install the world. I think the directions are in the FreeBSD handbook. Best, On Sun, Sep 28, 2014 at 1:26 PM, Valeri Galtsev wrote: > > On Sun, September 28, 2014 10:01 am, firmdog@gmail.com wrote: > > I just installed a brand new 8.3 box and got the same behavior. I see > > in my output below that I have to build or update my own kernel? > > > > > > # uname -a > > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC > > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 > > # > > > > Starting the upgrade attempt: > > > > # freebsd-update -r 8.4-RELEASE upgrade > > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > > Fetching public key from update6.freebsd.org... done. > > Fetching metadata signature for 8.3-RELEASE from update6.freebsd.org... > > done. > > Fetching metadata index... done. > > Fetching 2 metadata files... done. > > Inspecting system... done. > > > > WARNING: This system is running a "xenhvm" kernel, which is not a > > kernel configuration distributed as part of FreeBSD 8.3-RELEASE. > > This kernel will not be updated: you MUST update the kernel manually > > before running "/usr/sbin/freebsd-update install". > > > > The following components of FreeBSD seem to be installed: > > src/base src/bin src/cddl src/contrib src/crypto src/etc src/games > > src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue > > src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin > > world/base world/dict world/doc world/games world/info world/manpages > > world/proflibs > > > > The following components of FreeBSD do not seem to be installed: > > kernel/generic world/catpages > > > > Does this look reasonable (y/n)? y > > > > Fetching metadata signature for 8.4-RELEASE from update6.freebsd.org... > > done. > > Fetching metadata index... done. > > Fetching 1 metadata patches. done. > > Applying metadata patches... done. > > Fetching 1 metadata files... done. > > Inspecting system... done. > > Fetching files from 8.3-RELEASE for merging... done. > > Preparing to download files... > > done. > > Fetching 32149 > > > patches.....10....20....30....40....50....60....70....80....90....100....= 110....120....130....140....150....160....170....180.... > > SNIP=E2=80=A6. > > done. > > Applying patches... > > Fetching 778 files... done. > > Attempting to automatically merge changes in files... done. > > > > The following file could not be merged automatically: /etc/mail/ > freebsd.cf > > Press Enter to edit this file in vi and resolve the conflicts > > manually... > > > > Then a bunch more of /etc/mail files and also a merge of > > /etc/master.passwd: > > > > Then this: > > > > The following files will be updated as part of updating to > > 8.4-RELEASE-p16: > > > > Then I run this: > > > > # freebsd-update install > > Installing updates... > > Kernel updates have been installed. Please reboot and run > > "/usr/sbin/freebsd-update install" again to finish installing updates. > > > > # reboot > > > > In last message before reboot it instructed to "reboot then run > > /usr/sbin/freebsd-update install > > again". Did you run "freebsd-update install" after reboot? > > Valeri > > > > > #uname -a > > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC > > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 > > > > > > > > > > > > > > On Sun, Sep 28, 2014 at 5:06 AM, FF wrote: > >> Can you provide the output of those commands? Freebsd-update is usuall= y > >> pretty good about telling you what's wrong. > >> > >> Thanks > >> > >> On Sat, Sep 27, 2014 at 3:02 PM, firmdog@gmail.com > >> wrote: > >>> > >>> Yes I ran freebsd-update install. Then I rebooted. Then I did it agai= n. > >>> Still at 8.3 > >>> On Sep 27, 2014 2:37 PM, "Dave" wrote: > >>> > >>> > On 27 September 2014 18:22:15 BST, "firmdog@gmail.com" > >>> > > >>> > wrote: > >>> >> > >>> >> Hi, > >>> >> > >>> >> Trying to use freebsd-update to go from 8.3 to 8.4 and I am doing > >>> this: > >>> >> > >>> >> # freebsd-update -r 8.4-RELEASE upgrade > >>> >> # freebsd-update install > >>> >> # reboot > >>> >> > >>> >> After reboot I am still at 8.3-RELEASE FreeBSD 8.3-RELEASE #0 > >>> >> > >>> >> What am I doing wrong? > >>> >> ------------------------------ > >>> >> > >>> >> freebsd-questions@freebsd.org mailing list > >>> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>> >> To unsubscribe, send any mail to > >>> >> "freebsd-questions-unsubscribe@freebsd.org" > >>> >> > >>> >> > >>> > Don't you need run rub "freebsd-update install"? > >>> > -- > >>> > Dave > >>> > > >>> > GPG/PGP ID: CDB94DA1 > >>> > > >>> _______________________________________________ > >>> freebsd-questions@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>> To unsubscribe, send any mail to > >>> "freebsd-questions-unsubscribe@freebsd.org" > >> > >> > >> > >> > >> -- > >> FF > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "freebsd-questions-unsubscribe@freebsd.org" > > > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ > --=20 FF From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 18:46:34 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41AFECFB for ; Sun, 28 Sep 2014 18:46:34 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BA55885E for ; Sun, 28 Sep 2014 18:46:33 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id mk6so584283lab.15 for ; Sun, 28 Sep 2014 11:46:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Ffn4QaAT8ReMDIblJIhJfQ2BAroGc2GV0QNzCGFGZe8=; b=GC396GCjLwsy3vYcTmx0F0WsOplsArUZGEjLp9pU34mpPUmmqKaR5OgkhVAjm2rPKT SBaBpo0L4ApmBCah4ZA/GF8KZ0DNcUJoU7bdp5nMpBOwHtXZdFE5VAErEreQJ8GnyYHs wHCajS/jDfLzWt2yEoyfwoKzmtUxHTsfZcHNvJk2aTlXu13FGZWP1i6HitrRJXOBEoLP 9/87aidsjUxKWOs00BwuXSllSzxM7JyWUJbfzmf/ahrAMFMHBfoXtcCJ1zPE7WQSfoxT wAmpgj3IJPQMTV0wXW4YzAT/s9/QJwl1bV4FgY49tHiIQc8SVgoLbA8GKYtydIURhe73 szTg== MIME-Version: 1.0 X-Received: by 10.112.209.2 with SMTP id mi2mr4249498lbc.51.1411929990958; Sun, 28 Sep 2014 11:46:30 -0700 (PDT) Received: by 10.152.19.6 with HTTP; Sun, 28 Sep 2014 11:46:30 -0700 (PDT) In-Reply-To: <50282.76.192.184.214.1411925201.squirrel@cosmo.uchicago.edu> References: <23187F4C-0413-4F84-9C86-6EC1084C794C@btinternet.com> <50282.76.192.184.214.1411925201.squirrel@cosmo.uchicago.edu> Date: Sun, 28 Sep 2014 14:46:30 -0400 Message-ID: Subject: Re: freebsd-update question From: "firmdog@gmail.com" To: galtsev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Dave , FF , "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 18:46:34 -0000 I did this multiple times: #freebsd-update install Installing updates... Completing this upgrade requires removing old shared object files. Please rebuild all installed 3rd party software (e.g., programs installed from the ports tree) and then run "/usr/sbin/freebsd-update insta= ll" again to finish installing updates. # reboot still at 8.3-RELEASE Since I am running the xenhvm kernel on an Amazon AWS server, I must update the kernel manually right? On Sun, Sep 28, 2014 at 1:26 PM, Valeri Galtsev wrote: > > On Sun, September 28, 2014 10:01 am, firmdog@gmail.com wrote: >> I just installed a brand new 8.3 box and got the same behavior. I see >> in my output below that I have to build or update my own kernel? >> >> >> # uname -a >> FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC >> 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 >> # >> >> Starting the upgrade attempt: >> >> # freebsd-update -r 8.4-RELEASE upgrade >> Looking up update.FreeBSD.org mirrors... 5 mirrors found. >> Fetching public key from update6.freebsd.org... done. >> Fetching metadata signature for 8.3-RELEASE from update6.freebsd.org... >> done. >> Fetching metadata index... done. >> Fetching 2 metadata files... done. >> Inspecting system... done. >> >> WARNING: This system is running a "xenhvm" kernel, which is not a >> kernel configuration distributed as part of FreeBSD 8.3-RELEASE. >> This kernel will not be updated: you MUST update the kernel manually >> before running "/usr/sbin/freebsd-update install". >> >> The following components of FreeBSD seem to be installed: >> src/base src/bin src/cddl src/contrib src/crypto src/etc src/games >> src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue >> src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin >> world/base world/dict world/doc world/games world/info world/manpages >> world/proflibs >> >> The following components of FreeBSD do not seem to be installed: >> kernel/generic world/catpages >> >> Does this look reasonable (y/n)? y >> >> Fetching metadata signature for 8.4-RELEASE from update6.freebsd.org... >> done. >> Fetching metadata index... done. >> Fetching 1 metadata patches. done. >> Applying metadata patches... done. >> Fetching 1 metadata files... done. >> Inspecting system... done. >> Fetching files from 8.3-RELEASE for merging... done. >> Preparing to download files... >> done. >> Fetching 32149 >> patches.....10....20....30....40....50....60....70....80....90....100...= .110....120....130....140....150....160....170....180.... >> SNIP=E2=80=A6. >> done. >> Applying patches... >> Fetching 778 files... done. >> Attempting to automatically merge changes in files... done. >> >> The following file could not be merged automatically: /etc/mail/freebsd.= cf >> Press Enter to edit this file in vi and resolve the conflicts >> manually... >> >> Then a bunch more of /etc/mail files and also a merge of >> /etc/master.passwd: >> >> Then this: >> >> The following files will be updated as part of updating to >> 8.4-RELEASE-p16: >> >> Then I run this: >> >> # freebsd-update install >> Installing updates... >> Kernel updates have been installed. Please reboot and run >> "/usr/sbin/freebsd-update install" again to finish installing updates. >> >> # reboot >> > > In last message before reboot it instructed to "reboot then run > > /usr/sbin/freebsd-update install > > again". Did you run "freebsd-update install" after reboot? > > Valeri > >> >> #uname -a >> FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC >> 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 >> >> >> >> >> >> >> On Sun, Sep 28, 2014 at 5:06 AM, FF wrote: >>> Can you provide the output of those commands? Freebsd-update is usually >>> pretty good about telling you what's wrong. >>> >>> Thanks >>> >>> On Sat, Sep 27, 2014 at 3:02 PM, firmdog@gmail.com >>> wrote: >>>> >>>> Yes I ran freebsd-update install. Then I rebooted. Then I did it again= . >>>> Still at 8.3 >>>> On Sep 27, 2014 2:37 PM, "Dave" wrote: >>>> >>>> > On 27 September 2014 18:22:15 BST, "firmdog@gmail.com" >>>> > >>>> > wrote: >>>> >> >>>> >> Hi, >>>> >> >>>> >> Trying to use freebsd-update to go from 8.3 to 8.4 and I am doing >>>> this: >>>> >> >>>> >> # freebsd-update -r 8.4-RELEASE upgrade >>>> >> # freebsd-update install >>>> >> # reboot >>>> >> >>>> >> After reboot I am still at 8.3-RELEASE FreeBSD 8.3-RELEASE #0 >>>> >> >>>> >> What am I doing wrong? >>>> >> ------------------------------ >>>> >> >>>> >> freebsd-questions@freebsd.org mailing list >>>> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>>> >> To unsubscribe, send any mail to >>>> >> "freebsd-questions-unsubscribe@freebsd.org" >>>> >> >>>> >> >>>> > Don't you need run rub "freebsd-update install"? >>>> > -- >>>> > Dave >>>> > >>>> > GPG/PGP ID: CDB94DA1 >>>> > >>>> _______________________________________________ >>>> freebsd-questions@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>>> To unsubscribe, send any mail to >>>> "freebsd-questions-unsubscribe@freebsd.org" >>> >>> >>> >>> >>> -- >>> FF >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" > > > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++ From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 18:50:19 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D554812A for ; Sun, 28 Sep 2014 18:50:19 +0000 (UTC) Received: from p3plsmtpa11-06.prod.phx3.secureserver.net (p3plsmtpa11-06.prod.phx3.secureserver.net [68.178.252.107]) by mx1.freebsd.org (Postfix) with ESMTP id A6AC289F for ; Sun, 28 Sep 2014 18:50:19 +0000 (UTC) Received: from titania.midsummerdream.org ([107.197.157.90]) by p3plsmtpa11-06.prod.phx3.secureserver.net with id wiob1o0011xJNYB01iobxq; Sun, 28 Sep 2014 11:48:42 -0700 X-Sender: oberon@midsummerdream.org Subject: Re: Freebsd 9.3-RELEASE and Virtualbox Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Rob Rati In-Reply-To: <20140928181821.76adad527982addeac22ceb5@yahoo.es> Date: Sun, 28 Sep 2014 14:48:33 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <79BD0C3C-FF83-4399-8250-12D3E4DA15CC@midsummerdream.org> References: <57884ABE-A0AB-4EC1-8B94-8998389196CB@midsummerdream.org> <20140928181821.76adad527982addeac22ceb5@yahoo.es> To: Eduardo Morras X-Mailer: Apple Mail (2.1283) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 18:50:19 -0000 On Sep 28, 2014, at 12:18 PM, Eduardo Morras wrote: > On Sun, 28 Sep 2014 11:21:18 -0400 > Rob Rati wrote: >=20 >> I've tried upgrading my 9.2-RELEASE system to 9.3-RELEASE a few >> times, but each time I had to revert because starting any Virtualbox >> VMs causes a kernel panic. I found this thread about the issue: >>=20 >> = https://lists.freebsd.org/pipermail/freebsd-emulation/2014-August/011767.h= tml >>=20 >> What I don't understand is why it is expected that the repository >> kernel module wouldn't be in sync with the 9.3-RELEASE kernel. Is it >> because the packages are relevant to all 9.x releases and there's no >> way to have a kernel module work with them all? If so, why bother >> having a kmod package at all? >=20 > Did you update /usr/src to 9.3 too? Kernel module needs to use some = /usr/src source code to compile and the resulting kernel module will = work only on that /usr/src version kernel. I don't have any src installed. The virtualbox kernel module I am using = is from the prebuild packages. I've never built the kernel module and = don't have the kernel src installed. >> On a related note, how difficult is it to build the kernel module? I >> have never built it from source in the past and don't even have >> kernel sources installed. I use stock kernels from the releases. >> Are there ways this build can get screwed up if options/packages >> aren't correct? >>=20 >> Rob >=20 > --- --- > Eduardo Morras >=20 Rob From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 19:04:17 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F41364D7 for ; Sun, 28 Sep 2014 19:04:16 +0000 (UTC) Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AF1CA18 for ; Sun, 28 Sep 2014 19:04:16 +0000 (UTC) Received: by mail-lb0-f178.google.com with SMTP id w7so41771lbi.23 for ; Sun, 28 Sep 2014 12:04:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/cJHKqI5riVYqggnKHCZaA5Tyn687HEWSrGLaIJeyG0=; b=W347LaioQOZAuR9/50LxOi6RPVPnZVMQCf7v9dx6GbXttPRxnb31oM2gqBRAawH+4q YA4Ct/hNyiKLi+8Oi4OPwLGA/iHOuEdwycf5Hsnp84ulw+BEF7F3Xjwfhlp5GqyC9Pr6 NVTFq2q+Z0L5FTVqgP0tMWTBo8tzg4mpQwRs7gmPFPlpU4zpKoPnIBU8D+tjcCTo979Y KR7DzmEVMz3YWAv4FI7duKI11+nOsI8bjjfkcvaoQbJKaSUazA/TAwhKL6c8JtBgEK1V NOIH8zrvH/P3g9qifj0bemjJyXBTNGfP/ba3ybaI5xqn0+w4qYaSPNOAWEUBDr9JmIhr nkMA== MIME-Version: 1.0 X-Received: by 10.152.42.194 with SMTP id q2mr21450980lal.75.1411931054248; Sun, 28 Sep 2014 12:04:14 -0700 (PDT) Received: by 10.152.19.6 with HTTP; Sun, 28 Sep 2014 12:04:14 -0700 (PDT) In-Reply-To: References: <23187F4C-0413-4F84-9C86-6EC1084C794C@btinternet.com> <50282.76.192.184.214.1411925201.squirrel@cosmo.uchicago.edu> Date: Sun, 28 Sep 2014 15:04:14 -0400 Message-ID: Subject: Re: freebsd-update question From: "firmdog@gmail.com" To: FF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Dave , "freebsd-questions@freebsd.org" , galtsev X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 19:04:17 -0000 OK. I will try that. Found these notes from 10 years ago. Gonna give this a try, not sure if cvsup will work anymore.... cvsup -g -L 2 update-file The update-file contains this: *default host=3Dcvsup11.us.FreeBSD.org *default base=3D/var/db *default prefix=3D/usr *default release=3Dcvs tag=3DRELENG_8 *default delete use-rel-suffix src-all ports-all tag=3D. doc-all tag=3D. cd /usr/src make buildworld make buildkernel make installkernel mergemaster make installworld On Sun, Sep 28, 2014 at 2:36 PM, FF wrote: > So your kernel won't be updated because you are running a custom kernel. > Your uname is based on the running kernel. > > If you want to confirm that you've in fact updated, you can reboot to the > GENERIC kernel which will confirm you are at 8.4 or whatever. FreeBSD upd= ate > is a binary update based on the release versions -- deviate from them and= it > doesn't break, but it can't touch those files. > > Since you know enough to put a custom kernel on there, you should follow = the > source rebuild instructions which would be basically be to svn down the > whole 8.4 source tree, make the world, make the kernel and install it, > reboot, and install the world. > > I think the directions are in the FreeBSD handbook. > > Best, > > > > On Sun, Sep 28, 2014 at 1:26 PM, Valeri Galtsev > wrote: >> >> >> On Sun, September 28, 2014 10:01 am, firmdog@gmail.com wrote: >> > I just installed a brand new 8.3 box and got the same behavior. I see >> > in my output below that I have to build or update my own kernel? >> > >> > >> > # uname -a >> > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC >> > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 >> > # >> > >> > Starting the upgrade attempt: >> > >> > # freebsd-update -r 8.4-RELEASE upgrade >> > Looking up update.FreeBSD.org mirrors... 5 mirrors found. >> > Fetching public key from update6.freebsd.org... done. >> > Fetching metadata signature for 8.3-RELEASE from update6.freebsd.org..= . >> > done. >> > Fetching metadata index... done. >> > Fetching 2 metadata files... done. >> > Inspecting system... done. >> > >> > WARNING: This system is running a "xenhvm" kernel, which is not a >> > kernel configuration distributed as part of FreeBSD 8.3-RELEASE. >> > This kernel will not be updated: you MUST update the kernel manually >> > before running "/usr/sbin/freebsd-update install". >> > >> > The following components of FreeBSD seem to be installed: >> > src/base src/bin src/cddl src/contrib src/crypto src/etc src/games >> > src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescu= e >> > src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin >> > world/base world/dict world/doc world/games world/info world/manpages >> > world/proflibs >> > >> > The following components of FreeBSD do not seem to be installed: >> > kernel/generic world/catpages >> > >> > Does this look reasonable (y/n)? y >> > >> > Fetching metadata signature for 8.4-RELEASE from update6.freebsd.org..= . >> > done. >> > Fetching metadata index... done. >> > Fetching 1 metadata patches. done. >> > Applying metadata patches... done. >> > Fetching 1 metadata files... done. >> > Inspecting system... done. >> > Fetching files from 8.3-RELEASE for merging... done. >> > Preparing to download files... >> > done. >> > Fetching 32149 >> > >> > patches.....10....20....30....40....50....60....70....80....90....100.= ...110....120....130....140....150....160....170....180.... >> > SNIP=E2=80=A6. >> > done. >> > Applying patches... >> > Fetching 778 files... done. >> > Attempting to automatically merge changes in files... done. >> > >> > The following file could not be merged automatically: >> > /etc/mail/freebsd.cf >> > Press Enter to edit this file in vi and resolve the conflicts >> > manually... >> > >> > Then a bunch more of /etc/mail files and also a merge of >> > /etc/master.passwd: >> > >> > Then this: >> > >> > The following files will be updated as part of updating to >> > 8.4-RELEASE-p16: >> > >> > Then I run this: >> > >> > # freebsd-update install >> > Installing updates... >> > Kernel updates have been installed. Please reboot and run >> > "/usr/sbin/freebsd-update install" again to finish installing updates. >> > >> > # reboot >> > >> >> In last message before reboot it instructed to "reboot then run >> >> /usr/sbin/freebsd-update install >> >> again". Did you run "freebsd-update install" after reboot? >> >> Valeri >> >> > >> > #uname -a >> > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC >> > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 >> > >> > >> > >> > >> > >> > >> > On Sun, Sep 28, 2014 at 5:06 AM, FF wrote: >> >> Can you provide the output of those commands? Freebsd-update is usual= ly >> >> pretty good about telling you what's wrong. >> >> >> >> Thanks >> >> >> >> On Sat, Sep 27, 2014 at 3:02 PM, firmdog@gmail.com >> >> wrote: >> >>> >> >>> Yes I ran freebsd-update install. Then I rebooted. Then I did it >> >>> again. >> >>> Still at 8.3 >> >>> On Sep 27, 2014 2:37 PM, "Dave" wrote= : >> >>> >> >>> > On 27 September 2014 18:22:15 BST, "firmdog@gmail.com" >> >>> > >> >>> > wrote: >> >>> >> >> >>> >> Hi, >> >>> >> >> >>> >> Trying to use freebsd-update to go from 8.3 to 8.4 and I am doing >> >>> this: >> >>> >> >> >>> >> # freebsd-update -r 8.4-RELEASE upgrade >> >>> >> # freebsd-update install >> >>> >> # reboot >> >>> >> >> >>> >> After reboot I am still at 8.3-RELEASE FreeBSD 8.3-RELEASE #0 >> >>> >> >> >>> >> What am I doing wrong? >> >>> >> ------------------------------ >> >>> >> >> >>> >> freebsd-questions@freebsd.org mailing list >> >>> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> >>> >> To unsubscribe, send any mail to >> >>> >> "freebsd-questions-unsubscribe@freebsd.org" >> >>> >> >> >>> >> >> >>> > Don't you need run rub "freebsd-update install"? >> >>> > -- >> >>> > Dave >> >>> > >> >>> > GPG/PGP ID: CDB94DA1 >> >>> > >> >>> _______________________________________________ >> >>> freebsd-questions@freebsd.org mailing list >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> >>> To unsubscribe, send any mail to >> >>> "freebsd-questions-unsubscribe@freebsd.org" >> >> >> >> >> >> >> >> >> >> -- >> >> FF >> > _______________________________________________ >> > freebsd-questions@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > To unsubscribe, send any mail to >> > "freebsd-questions-unsubscribe@freebsd.org" >> >> >> ++++++++++++++++++++++++++++++++++++++++ >> Valeri Galtsev >> Sr System Administrator >> Department of Astronomy and Astrophysics >> Kavli Institute for Cosmological Physics >> University of Chicago >> Phone: 773-702-4247 >> ++++++++++++++++++++++++++++++++++++++++ > > > > > -- > FF From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 19:33:45 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E3F0D83 for ; Sun, 28 Sep 2014 19:33:45 +0000 (UTC) Received: from nm35-vm3.bullet.mail.ir2.yahoo.com (nm35-vm3.bullet.mail.ir2.yahoo.com [212.82.97.126]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 999ABCC7 for ; Sun, 28 Sep 2014 19:33:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s2048; t=1411932644; bh=j5oFAuwc8kM2TlNXAJ1jQlS5V43V4YWHPmPQ//++jgc=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:X-Received:MIME-Version:Received:In-Reply-To:References:From:Date:Message-ID:Subject:To:Cc:Content-Type:From:Subject; b=XJtDQ7GWB4ef1y96drhW0XsJJvIPhaYE/7t/TyookE1uum5f9s64sr78IoNmu7cvnFG7Efqkah/Zx1aLh5S86U3rR8Y0qsi7ZlF0VKmTUpRtJFbc00udPGZW92yHW4ufzI2Fes7vdzHsqorLq64yohXvAP87xWwXBqf2wWyl++qHpy+OCjOjGplgByeAHRl0lEO9HVdFags/wc0LaYdzbrLu2IIxa+tJMqSqWMRDQM5XQob1W7n7uCgVVha1PhAFQGgO1Xc8QKxfc39uSkGUNRvSqtDOwqbogEezG7W+IPPoOVthkWhHyENi6MjwZ43FEUJjvZ5IoLpi6JLmIOrcyg== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=ymail.com; b=KlttK5VRCRCyu3JHLoyfKHSvaMavKxMl8vhls4BrBRa+AyTYY110C10zbLDXXEJ8W5iZlHZ44kWFGr40ZroqswHD40nyiG4JX1y7yRZ7O+mggkQ+pIQpQw1W7LjoWP6qcZi7kbWNBSlnD2exrAVZIywzVjVPH3FCS6tAPecKBnmPPGzOlkTVt+n8516u93CNo05QAWdlB4BrK3hiNtO5DAhxml1NcqN67TKW53wtgK1tqxiTX3We4fFHU/xMYJZPbOhU29k2cKYSMmZ0abX4iQqdXUjGdvoSW9YpD5samHBWLxl1Za5sHcMWNIyv63KSHxJgEjfZ2QinpQP4CBhlRA==; Received: from [212.82.98.62] by nm35.bullet.mail.ir2.yahoo.com with NNFMP; 28 Sep 2014 19:30:44 -0000 Received: from [46.228.39.84] by tm15.bullet.mail.ir2.yahoo.com with NNFMP; 28 Sep 2014 19:30:44 -0000 Received: from [127.0.0.1] by smtp121.mail.ir2.yahoo.com with NNFMP; 28 Sep 2014 19:30:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1411932644; bh=j5oFAuwc8kM2TlNXAJ1jQlS5V43V4YWHPmPQ//++jgc=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:X-Received:MIME-Version:Received:In-Reply-To:References:From:Date:Message-ID:Subject:To:Cc:Content-Type; b=mmdffAMVRuyGFoq9YhgZ3/QNnYJlinGQUd/8ySk3kYW1d17L5SaHSa11ZlSeHvOT56FkIcq+EJ5BNqcxQhu5m8S2ySMOVkB+rNm5o1GLuZzavYfW7m02Nqm/jWoYswPLtXHfQfgberqD5QtUAx4ZJl8+TjVXl5xLBbjIZtzcy5M= X-Yahoo-Newman-Id: 356206.53821.bm@smtp121.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: ApgcO5IVM1k_ev6RvKBO5cPgTDWidGAPq15MhDH.1gBSB4g vWyAa3SF3MeAAkWz4ENM4sgGMyexIctjdmPNMnID7zro2S9f6DsgrI1f9oeb UsfaHEmhchmMCCg3VPk6pSBicfaciPRhSSBptOs.JX_ldnj67_Ll7dN27oji tyXF1YXQ8fH6i54waqrKPB2xFG1aQ7j74fVKYHGAuu30_j0cOWNAikAIE74p CiCf9tEZnUTYjAYw5JGfw4nAue9EI2hztbLTRyts5MKyPMB821eybPuOJtVi PeTFCA5vfLP9USQK3qbu_Rt_sihgzxPgf.TFC4Q72Yu8IU0coQh0PBGOMgmW V5pF0F_dF.sPz7OtSw7xlQq0zo7CQMZORA2SSntjGTXUO5T7gcl5Abn9J5ql sU8SzUAZU1QAsfyp.uvgPh47xKJY8sqddhHTCLnf2hH3SgS5V.rb7gKxIh1H O7nURrsXhyD_8RgLV5sWEXuvhku7IhQCWMlliI2bwRNRay6WZtK7iDmuupC0 e5bAIXS27I0UIth2d_fNie_SaWstG5I0cPb37Iw.5HJgbqSN0MFVlSxx2JNK _VIwfjbzjDCfCT7tYwYgnoSXNrY4VCkhSOCYmhms2vrwM6zXz38tq0K3K8kE FnwkJgEC5C2t2ZwZXgK7spBSi2g-- X-Yahoo-SMTP: S65s63SswBDjU54Gjqw2GSWlZmfgiEU_X3tN1_9u Received: by mail-wg0-f48.google.com with SMTP id x13so8867021wgg.19 for ; Sun, 28 Sep 2014 12:30:41 -0700 (PDT) X-Received: by 10.194.103.200 with SMTP id fy8mr1965071wjb.123.1411932641076; Sun, 28 Sep 2014 12:30:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.27.137.130 with HTTP; Sun, 28 Sep 2014 12:30:20 -0700 (PDT) In-Reply-To: References: <23187F4C-0413-4F84-9C86-6EC1084C794C@btinternet.com> <50282.76.192.184.214.1411925201.squirrel@cosmo.uchicago.edu> From: Axel Date: Sun, 28 Sep 2014 21:30:20 +0200 Message-ID: Subject: Re: [Bulk] Re: freebsd-update question To: "firmdog@gmail.com" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-questions@freebsd.org" , galtsev , FF , Dave X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 19:33:45 -0000 On Sun, Sep 28, 2014 at 9:04 PM, firmdog@gmail.com wrote: > OK. I will try that. Found these notes from 10 years ago. Gonna give > this a try, not sure if cvsup will work anymore.... > > > cvsup -g -L 2 update-file > > The update-file contains this: > > *default host=3Dcvsup11.us.FreeBSD.org > *default base=3D/var/db > *default prefix=3D/usr > *default release=3Dcvs tag=3DRELENG_8 > *default delete use-rel-suffix > src-all > ports-all tag=3D. > doc-all tag=3D. > > cd /usr/src > > make buildworld > > make buildkernel > > make installkernel > > mergemaster > > make installworld > > > > > > > On Sun, Sep 28, 2014 at 2:36 PM, FF wrote: > > So your kernel won't be updated because you are running a custom kernel= . > > Your uname is based on the running kernel. > > > > If you want to confirm that you've in fact updated, you can reboot to t= he > > GENERIC kernel which will confirm you are at 8.4 or whatever. FreeBSD > update > > is a binary update based on the release versions -- deviate from them > and it > > doesn't break, but it can't touch those files. > > > > Since you know enough to put a custom kernel on there, you should follo= w > the > > source rebuild instructions which would be basically be to svn down the > > whole 8.4 source tree, make the world, make the kernel and install it, > > reboot, and install the world. > > > > I think the directions are in the FreeBSD handbook. > > > > Best, > > > > > > > > On Sun, Sep 28, 2014 at 1:26 PM, Valeri Galtsev < > galtsev@kicp.uchicago.edu> > > wrote: > >> > >> > >> On Sun, September 28, 2014 10:01 am, firmdog@gmail.com wrote: > >> > I just installed a brand new 8.3 box and got the same behavior. I se= e > >> > in my output below that I have to build or update my own kernel? > >> > > >> > > >> > # uname -a > >> > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC > >> > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 > >> > # > >> > > >> > Starting the upgrade attempt: > >> > > >> > # freebsd-update -r 8.4-RELEASE upgrade > >> > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > >> > Fetching public key from update6.freebsd.org... done. > >> > Fetching metadata signature for 8.3-RELEASE from > update6.freebsd.org... > >> > done. > >> > Fetching metadata index... done. > >> > Fetching 2 metadata files... done. > >> > Inspecting system... done. > >> > > >> > WARNING: This system is running a "xenhvm" kernel, which is not a > >> > kernel configuration distributed as part of FreeBSD 8.3-RELEASE. > >> > This kernel will not be updated: you MUST update the kernel manually > >> > before running "/usr/sbin/freebsd-update install". > >> > > >> > The following components of FreeBSD seem to be installed: > >> > src/base src/bin src/cddl src/contrib src/crypto src/etc src/games > >> > src/gnu src/include src/krb5 src/lib src/libexec src/release > src/rescue > >> > src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin > >> > world/base world/dict world/doc world/games world/info world/manpage= s > >> > world/proflibs > >> > > >> > The following components of FreeBSD do not seem to be installed: > >> > kernel/generic world/catpages > >> > > >> > Does this look reasonable (y/n)? y > >> > > >> > Fetching metadata signature for 8.4-RELEASE from > update6.freebsd.org... > >> > done. > >> > Fetching metadata index... done. > >> > Fetching 1 metadata patches. done. > >> > Applying metadata patches... done. > >> > Fetching 1 metadata files... done. > >> > Inspecting system... done. > >> > Fetching files from 8.3-RELEASE for merging... done. > >> > Preparing to download files... > >> > done. > >> > Fetching 32149 > >> > > >> > > patches.....10....20....30....40....50....60....70....80....90....100....= 110....120....130....140....150....160....170....180.... > >> > SNIP=E2=80=A6. > >> > done. > >> > Applying patches... > >> > Fetching 778 files... done. > >> > Attempting to automatically merge changes in files... done. > >> > > >> > The following file could not be merged automatically: > >> > /etc/mail/freebsd.cf > >> > Press Enter to edit this file in vi and resolve the conflicts > >> > manually... > >> > > >> > Then a bunch more of /etc/mail files and also a merge of > >> > /etc/master.passwd: > >> > > >> > Then this: > >> > > >> > The following files will be updated as part of updating to > >> > 8.4-RELEASE-p16: > >> > > >> > Then I run this: > >> > > >> > # freebsd-update install > >> > Installing updates... > >> > Kernel updates have been installed. Please reboot and run > >> > "/usr/sbin/freebsd-update install" again to finish installing update= s. > >> > > >> > # reboot > >> > > >> > >> In last message before reboot it instructed to "reboot then run > >> > >> /usr/sbin/freebsd-update install > >> > >> again". Did you run "freebsd-update install" after reboot? > >> > >> Valeri > >> > >> > > >> > #uname -a > >> > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC > >> > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 > >> > > >> > > >> > > >> > > >> > > >> > > >> > On Sun, Sep 28, 2014 at 5:06 AM, FF wrote: > >> >> Can you provide the output of those commands? Freebsd-update is > usually > >> >> pretty good about telling you what's wrong. > >> >> > >> >> Thanks > >> >> > >> >> On Sat, Sep 27, 2014 at 3:02 PM, firmdog@gmail.com < > firmdog@gmail.com> > >> >> wrote: > >> >>> > >> >>> Yes I ran freebsd-update install. Then I rebooted. Then I did it > >> >>> again. > >> >>> Still at 8.3 > >> >>> On Sep 27, 2014 2:37 PM, "Dave" > wrote: > >> >>> > >> >>> > On 27 September 2014 18:22:15 BST, "firmdog@gmail.com" > >> >>> > > >> >>> > wrote: > >> >>> >> > >> >>> >> Hi, > >> >>> >> > >> >>> >> Trying to use freebsd-update to go from 8.3 to 8.4 and I am doi= ng > >> >>> this: > >> >>> >> > >> >>> >> # freebsd-update -r 8.4-RELEASE upgrade > >> >>> >> # freebsd-update install > >> >>> >> # reboot > >> >>> >> > >> >>> >> After reboot I am still at 8.3-RELEASE FreeBSD 8.3-RELEASE #0 > >> >>> >> > >> >>> >> What am I doing wrong? > >> >>> >> ------------------------------ > >> >>> >> > >> >>> >> freebsd-questions@freebsd.org mailing list > >> >>> >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> >>> >> To unsubscribe, send any mail to > >> >>> >> "freebsd-questions-unsubscribe@freebsd.org" > >> >>> >> > >> >>> >> > >> >>> > Don't you need run rub "freebsd-update install"? > >> >>> > -- > >> >>> > Dave > >> >>> > > >> >>> > GPG/PGP ID: CDB94DA1 > >> >>> > > >> >>> _______________________________________________ > >> >>> freebsd-questions@freebsd.org mailing list > >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> >>> To unsubscribe, send any mail to > >> >>> "freebsd-questions-unsubscribe@freebsd.org" > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> FF > >> > _______________________________________________ > >> > freebsd-questions@freebsd.org mailing list > >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> > To unsubscribe, send any mail to > >> > "freebsd-questions-unsubscribe@freebsd.org" > >> > >> > >> ++++++++++++++++++++++++++++++++++++++++ > >> Valeri Galtsev > >> Sr System Administrator > >> Department of Astronomy and Astrophysics > >> Kavli Institute for Cosmological Physics > >> University of Chicago > >> Phone: 773-702-4247 > >> ++++++++++++++++++++++++++++++++++++++++ > > > > > > > > > > -- > > FF > Hi, CVS is now deprecated. Please use SVN instead if you prefer to follow the manual upgrade process [1] FreeBSD-update tool upgrades (binary upgrades) your base system and GENERIC kernel only. It syncs sources too. So you need to rebuild your custom kernel after the process. [2] Kind regards. Alexandre [1] http://www.freebsd.org/doc/handbook/svn.html [2] http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 20:59:14 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 099947C2 for ; Sun, 28 Sep 2014 20:59:14 +0000 (UTC) Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE4596CD for ; Sun, 28 Sep 2014 20:59:13 +0000 (UTC) Received: by mail-ob0-f178.google.com with SMTP id uy5so1361225obc.9 for ; Sun, 28 Sep 2014 13:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=tpzawyTWzzcIai4yGe7b5aaWdZu+nEZXPgBZIL5RHQQ=; b=vyiWf+GwhpiIoSxsywk+uxCoPSqsJyvY1CUJ4Z+hQnqaTqkwFVeMdRy0mT2ngsA+rI J5COU2S8rzMMbz0KcvyncvVwAo31sE3AMTPRem7VJ1/WE31lIQZtM+YU4kU3DLNQy7R4 dUgukIRrU4vVzcEefbQGyL5slVX5i7VcROoablC2apobk85oBUwSJYNmo2jIz1IPWbRf 4XlFfYu40HKNol/uxLOgXuZmkmKGI+UUvv8r4HB2H5XJNRS7hR8az+fMyCfCq2Jcic59 fRq09N02x/9Ta7R2InElUjyF8Tz9UFBxWclN7+t8QSZDl/sMLgIbrr+r8InidnFPEX+o u2RA== MIME-Version: 1.0 X-Received: by 10.182.80.66 with SMTP id p2mr4738826obx.77.1411937953189; Sun, 28 Sep 2014 13:59:13 -0700 (PDT) Received: by 10.76.188.72 with HTTP; Sun, 28 Sep 2014 13:59:13 -0700 (PDT) Date: Sun, 28 Sep 2014 13:59:13 -0700 Message-ID: Subject: BASH Shellshock and FreeBSD 4.X From: Everett Batey To: Questions at FreeBSD Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 20:59:14 -0000 Severely stuck in Time - OLD FBSD .. any bright ideas around /bin/bash risks AND NOT DONT TELL ME UPDATE FBSD .. - Dependencies I can NOT escape .. On other hand for FreeBSD 9.1-RELEASE-p7 is there an equivalent of yum update bash? -- Thnx / Everett (Flames PLEASE, I old and Cold) From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 21:04:46 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D80108F7 for ; Sun, 28 Sep 2014 21:04:46 +0000 (UTC) Received: from mail-la0-f46.google.com (mail-la0-f46.google.com [209.85.215.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F7DD7F4 for ; Sun, 28 Sep 2014 21:04:45 +0000 (UTC) Received: by mail-la0-f46.google.com with SMTP id gi9so6604338lab.5 for ; Sun, 28 Sep 2014 14:04:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=0jAw1iLaIyUj4XlpuHWgKwNQbsQujZQvAu+xrw2DV8M=; b=VouZSwLu7TrAH+7NCMlCVM2r1VpWX/EsxJN1tErqo3bor1URcLXuXEhbQouzxeRRi1 gIaDZAIXqFiPyqIUjwA+wwzNn1yFNgOjbLZrVxnmnKDXz/1NhNR5LdKaQj3ly/tHAFgE R3IarmpAcSDaOTUwC8AcVtjRxtW5C7ZMpk4iKHV9rMLT42pCUrJXhPxDKbSDs61K421v QlAj2f4+awYTO96jOpf9weiZYdY62JaWaCEJxus6i47mqMANT37T7AoUDs6pKiEhYJiV KTmDjxFp2POo8AZZOYt2TFU6pXTLtkVLwd5r5brtGezQnLCUmzQAtVAGnQ6KhLUnTVIA V3Eg== X-Gm-Message-State: ALoCoQnyoJo1I8a/P5IPBSFwC1RiRlYVIlvxzhV0v3+BZmIq5mt5IDbNsNBV9aYf+NhjypmlH1HI MIME-Version: 1.0 X-Received: by 10.152.6.228 with SMTP id e4mr4870553laa.12.1411938277814; Sun, 28 Sep 2014 14:04:37 -0700 (PDT) Received: by 10.25.20.159 with HTTP; Sun, 28 Sep 2014 14:04:37 -0700 (PDT) X-Originating-IP: [70.209.203.3] Received: by 10.25.20.159 with HTTP; Sun, 28 Sep 2014 14:04:37 -0700 (PDT) In-Reply-To: References: Date: Sun, 28 Sep 2014 14:04:37 -0700 Message-ID: Subject: Re: BASH Shellshock and FreeBSD 4.X From: "Brian W." To: Everett Batey Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Questions at FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 21:04:47 -0000 Re the bash query do you use portsnap? Presuming the old package system the easiest answer is portsnap fetch update and then portupgrade -P bash. Brian On Sep 28, 2014 1:59 PM, "Everett Batey" wrote: > Severely stuck in Time - OLD FBSD .. any bright ideas around /bin/bash > risks AND NOT DONT TELL ME UPDATE FBSD .. - Dependencies I can NOT > escape .. > > On other hand for FreeBSD 9.1-RELEASE-p7 is there an equivalent of yum > update bash? > > > -- > Thnx / Everett (Flames PLEASE, I old and Cold) > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 21:05:02 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D002697B for ; Sun, 28 Sep 2014 21:05:02 +0000 (UTC) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9FE7F7FE for ; Sun, 28 Sep 2014 21:05:02 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by gateway2.nyi.internal (Postfix) with ESMTP id 5290FF50 for ; Sun, 28 Sep 2014 17:04:55 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Sun, 28 Sep 2014 17:04:55 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:in-reply-to :references:subject:date; s=smtpout; bh=kQIX9iIrAfEdZZY0atmVQ1K3 hpw=; b=Py2zq+35W1+4gotps0yNQZWVDntXLobKpJTYN926E8w8JLbFN7TbOLY3 xLW6dZPpPJYLGkiWqsejOl82hTDzn3nMhIM6NNr7U2nAy2FlvV2DreMcSaVa5KDf KSboJzjNV+kGZfmMQoSpeKxBL1tKMS+fJgd3xR6BnRsQiIVZHd8= Received: by web3.nyi.internal (Postfix, from userid 99) id 1C29211C978; Sun, 28 Sep 2014 17:04:55 -0400 (EDT) Message-Id: <1411938295.1187673.172706457.3022C573@webmail.messagingengine.com> X-Sasl-Enc: 0lZT8EsThjAijO2BU0KlF3LukpbOgCd/KHnqITgDv+/K 1411938295 From: Mark Felder To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-cad53418 In-Reply-To: References: Subject: Re: BASH Shellshock and FreeBSD 4.X Date: Sun, 28 Sep 2014 16:04:55 -0500 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 21:05:02 -0000 On Sun, Sep 28, 2014, at 15:59, Everett Batey wrote: > Severely stuck in Time - OLD FBSD .. any bright ideas around /bin/bash > risks AND NOT DONT TELL ME UPDATE FBSD .. - Dependencies I can NOT > escape .. > Is bash the default shell of the system? The default shell of any users running exposed services? If not, it's not exploitable. Just having bash installed doesn't make you vulnerable. > On other hand for FreeBSD 9.1-RELEASE-p7 is there an equivalent of yum > update bash? > pkg upgrade bash From owner-freebsd-questions@FreeBSD.ORG Sun Sep 28 21:40:09 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A7CEFC29 for ; Sun, 28 Sep 2014 21:40:09 +0000 (UTC) Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D119BB1 for ; Sun, 28 Sep 2014 21:40:08 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id l4so16826618lbv.19 for ; Sun, 28 Sep 2014 14:40:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=oC/2KaknqqrJ8MQhoJpb3L8LcHbkUqZ2Q7gR3Xt0pYU=; b=HnN3tS9CR03Lyu3K9Kgw6+c53C7J5MUFZ2DiUw6H+TTojD5aKhW62gFO6O8pFuBw1B l0mp/oCdG2KTT0ELBCBUpXa1Nb/DngUGw6su0thfmFVSIwdJNxQ6UlLzn2xtc6Ph7j12 EJrxMsv0fosZOd+Rs9tr0ijaZ29YwMeVTt5ocJCepVK4uV9wgXw8Q4QS4mqY6sIgW3S3 tFoQRkFpuIQhFmz48HQqeQRNpa1Bhw0taL/rGigvEiQk9VwFapqIcEQPajakl/KoqrSK rVKXjN+aSIf/N53spEcYlxQC5+9IUQAQMCwqo2I+Hdea7cngWlbiPMciW14oMqCRvVzJ z7RQ== X-Gm-Message-State: ALoCoQk4GsPzkdZnYFgWj43Us+OhYxGKbOckV0KJeNwnE8PSJDFH7KE1D1WRNMXtU7xmWKHsFBwl MIME-Version: 1.0 X-Received: by 10.112.16.129 with SMTP id g1mr32948420lbd.19.1411940400934; Sun, 28 Sep 2014 14:40:00 -0700 (PDT) Received: by 10.25.20.159 with HTTP; Sun, 28 Sep 2014 14:40:00 -0700 (PDT) X-Originating-IP: [70.209.203.3] Received: by 10.25.20.159 with HTTP; Sun, 28 Sep 2014 14:40:00 -0700 (PDT) In-Reply-To: References: Date: Sun, 28 Sep 2014 14:40:00 -0700 Message-ID: Subject: Re: BASH Shellshock and FreeBSD 4.X From: "Brian W." To: FreeBSD Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2014 21:40:09 -0000 For your ancient system I would do 2 things. 1 Run one of the well publicized ways to check your system and see if it is vulnerable. The ancientness of your system suggests someone doesn't care honestly. 2 If it is then try to get the bash using users to another shell. On Sep 28, 2014 2:28 PM, "Everett Batey" wrote: > For SO OLD an FBSD .. will this try to immediately move me up over a > decade and maybe crash my very highly depended OLDBSD server ??? > > > On Sun, Sep 28, 2014 at 2:04 PM, Brian W. wrote: > > Re the bash query do you use portsnap? Presuming the old package system > the > > easiest answer is portsnap fetch update and then portupgrade -P bash. > > > > Brian > > > > On Sep 28, 2014 1:59 PM, "Everett Batey" wrote: > >> > >> Severely stuck in Time - OLD FBSD .. any bright ideas around /bin/bash > >> risks AND NOT DONT TELL ME UPDATE FBSD .. - Dependencies I can NOT > >> escape .. > >> > >> On other hand for FreeBSD 9.1-RELEASE-p7 is there an equivalent of yum > >> update bash? > >> > >> > >> -- > >> Thnx / Everett (Flames PLEASE, I old and Cold) > >> _______________________________________________ > >> freebsd-questions@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions > >> To unsubscribe, send any mail to > >> "freebsd-questions-unsubscribe@freebsd.org" > > > > -- > R/ Everett Batey / Skype: wa6cre-10 / efbatey@gmail.com > or efbarc@cotdazr.org or wa6cre@rabbitradio.org or lioneverett@gmail.com > Auxiliary Lions 4-A3 Web Lions 4-A3 Calendar / CrisisLinks > http://bit.ly/cw95Um > (805) 616-2471 / G-Talk/Twitter: efbatey / CrisisLinks > http://bit.ly/cw95Um > Please visit So Calif Linux Expo http://www.socallinuxexpo.org > From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 00:07:11 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD52C7A0 for ; Mon, 29 Sep 2014 00:07:11 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6DD07AA2 for ; Mon, 29 Sep 2014 00:07:11 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s8T079lc001982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 28 Sep 2014 18:07:09 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s8T078rS001979; Sun, 28 Sep 2014 18:07:09 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 28 Sep 2014 18:07:08 -0600 (MDT) From: Warren Block To: Rob Rati Subject: Re: Freebsd 9.3-RELEASE and Virtualbox In-Reply-To: <57884ABE-A0AB-4EC1-8B94-8998389196CB@midsummerdream.org> Message-ID: References: <57884ABE-A0AB-4EC1-8B94-8998389196CB@midsummerdream.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 28 Sep 2014 18:07:09 -0600 (MDT) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 00:07:11 -0000 On Sun, 28 Sep 2014, Rob Rati wrote: > On a related note, how difficult is it to build the kernel module? I > have never built it from source in the past and don't even have kernel > sources installed. I use stock kernels from the releases. Are there > ways this build can get screwed up if options/packages aren't correct? It's easy. Install source, then build emulators/virtualbox-ose-kmod. From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 00:13:37 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1A71B862 for ; Mon, 29 Sep 2014 00:13:37 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BF74BB58 for ; Mon, 29 Sep 2014 00:13:36 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s8T0DZT7003596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 28 Sep 2014 18:13:35 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s8T0DZ9W003589; Sun, 28 Sep 2014 18:13:35 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 28 Sep 2014 18:13:35 -0600 (MDT) From: Warren Block To: Carmel NY Subject: Re: update to linux_base-c6 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 28 Sep 2014 18:13:35 -0600 (MDT) Cc: User questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 00:13:37 -0000 On Sun, 28 Sep 2014, Carmel NY wrote: > Sun, 28 Sep 2014 12:30:18 -0400 > > I want to update to emulators/linux_base-c6. According to UPDATING, I should > remove all linux-f10 ports. In my case, that would be: > ... > However, in addition to them, I have the following ports that depend on > linux_base-f10: > > acroread9-9.5.5_1 > acroreadwrapper-0.0.20130208 > linux-libgtkembedmoz-0.0.20100806 > nspluginwrapper-1.4.4_4 > nvidia-driver-331.67_1 > > My question is, after removing the linux-f10 ports and the linux_base-f10, > making the necessary changes to the /etc/makefile, etcetera and then > installing linux_base-c6, do I have to then install the corresponding c6 > ports for the f10 ports that have deleted or is that done automatically I > assume, that I have to rebuild the remaining ports that use to depend on > linux_base-f10? Of those, I only use nspluginwrapper, and had to manually reinstall it after updating the linux ports. From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 00:29:05 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3CE3BA87 for ; Mon, 29 Sep 2014 00:29:05 +0000 (UTC) Received: from sdf.lonestar.org (mx.sdf.org [192.94.73.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.sdf.org", Issuer "SDF.ORG" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C365C40 for ; Mon, 29 Sep 2014 00:29:04 +0000 (UTC) Received: from sdf.org (IDENT:bennett@sdf.lonestar.org [192.94.73.15]) by sdf.lonestar.org (8.14.8/8.14.5) with ESMTP id s8T0T0kE017771 (using TLSv1/SSLv3 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Mon, 29 Sep 2014 00:29:00 GMT Received: (from bennett@localhost) by sdf.org (8.14.8/8.12.8/Submit) id s8T0T0KY029472; Sun, 28 Sep 2014 19:29:00 -0500 (CDT) From: Scott Bennett Message-Id: <201409290029.s8T0T0KY029472@sdf.org> Date: Sun, 28 Sep 2014 19:29:00 -0500 To: wblock@wonkity.com Subject: Re: ZFS and 2 TB disk drive technology :-( References: <201409281030.s8SAU8dR027634@sdf.org> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 00:29:05 -0000 On Sun Sep 28 14:59:43 2014 Warren Block wrote: > On Sun, 28 Sep 2014, Scott Bennett wrote: > > On Wed, 24 Sep 2014 11:24:35 -0400 Paul Kraus > > wrote: > > Thanks for chiming in, Paul. > > > >> On 9/24/14 7:08, Scott Bennett wrote: > >> > >> > >> > >> What version of FreeBSD are you running ? > > > > FreeBSD hellas 9.2-STABLE FreeBSD 9.2-STABLE #1 r264339: Fri Apr 11 05:16:25 CDT 2014 bennett@hellas:/usr/obj/usr/src/sys/hellas i386 > > > >> What hardware are you running it on ? > > > > The CPU is a Q6600 running on a PCIE2 Gigabyte motherboard, whose model > > number I did have written down around here somewhere but can't lay hands on > > at the moment. > > sysutils/dmidecode will show that without having to open the case. I had no idea, so thanks for that. I'll have to install it once I have stable space for a ports tree again in case it also shows other good stuff. In any case, I was pretty sure I had seen it somewhere else, and it turns out that the motherboard manufacturer and model number show up in a couple of places in the output of kenv(1). :-) BTW, your message showed up without a Date: header, so I used the date and timestamp from the From line of the envelope. Must be something weird about your mail interface. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 02:17:12 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A65DB384 for ; Mon, 29 Sep 2014 02:17:12 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 61B30805 for ; Mon, 29 Sep 2014 02:17:11 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XYQWM-0006pG-GM for freebsd-questions@freebsd.org; Mon, 29 Sep 2014 04:17:02 +0200 Received: from 49-156-16-16.rdns.orionvm.com.au ([49.156.16.16]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Sep 2014 04:17:02 +0200 Received: from newsgroups by 49-156-16-16.rdns.orionvm.com.au with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Sep 2014 04:17:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Ruben Schade Subject: Re: pkg must be version 1.3.8 or greater Date: Mon, 29 Sep 2014 12:16:49 +1000 Lines: 46 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 49-156-16-16.rdns.orionvm.com.au User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.7.0 In-Reply-To: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 02:17:12 -0000 On 23/09/14 16:44, Ruben Schade wrote: > Hi everyone, > > Running FreeBSD amd64 10.0-RELEAESE-p9. Installed everything from pkg, > very nice system. > > Prefer building nginx from ports, so portsnapped the latest tree and did > the usual: > > > # cd /usr/ports/www/nginx > > # make install clean > > Got the following error: > > ===> nginx-1.6.2,2 pkg(8) must be version 1.3.8 or greater, but you > have 1.3.7. You must upgrade pkg(8) first. > > Running pkg update however: > > > FreeBSD repository is up-to-date. > > All repositories are up-to-date. > > And pkg upgrade: > > > Updating FreeBSD repository catalogue... > > FreeBSD repository is up-to-date. > > All repositories are up-to-date. > > Checking for upgrades (1 candidates): 100% > > Checking integrity... done (0 conflicting) > > Your packages are up to date. > > Fairly new to pkgng, could that "1 candidates" line be the updated pkg I > need in waiting? > > Thanks, > Ruben > Just an update for those interested, ran pkg update this morning and 1.3.8_1 just came in. Can build nginx now without problem :) -- Ruben Schade VM chap in s/Singapore/Sydney/ Site: http://rubenschade.com/ Blog: http://rubenerd.com/ From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 02:21:57 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED05443E for ; Mon, 29 Sep 2014 02:21:57 +0000 (UTC) Received: from mail-pd0-x248.google.com (mail-pd0-x248.google.com [IPv6:2607:f8b0:400e:c02::248]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C57A08BD for ; Mon, 29 Sep 2014 02:21:57 +0000 (UTC) Received: by mail-pd0-f200.google.com with SMTP id p10so36030811pdj.11 for ; Sun, 28 Sep 2014 19:21:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:message-id:date:subject:from:to:content-type; bh=y4Eiqs3faP3S8Pr9aF7DJorz9tDT0QDxXuAel6WBmYw=; b=OTHUSA4uJB9+T/ZlM2dErSa8U6Vw7Oacqq+uUwIxw/2lTYrkWZxQri+PQig7umI5/p kGjsTLCQp9325fhWHXzWDvFv/3zvaDjAAxi18Z2xffCTf5tVak57qLdFrM/VWOJmtW7Y R7GplnrUO1AQHdRTDgvY0aYhXEfduQpzX6ry60gWaWHdAkZEcqE8Fk+WPQB4upaw0OxP r7fDcGBbDsOnKKsOqm5yfDi38n/OSwtuIokioCzJsA0n7tTx5rWCshEGfQAvD1AWHD9K r8tOazCZJ6skVbr+uJ+L7101lZe0xqMHIkReDBty1LxXkqPxe0wToYq9ISVDl+rH73Ad TNSg== MIME-Version: 1.0 X-Received: by 10.66.156.100 with SMTP id wd4mr31588250pab.31.1411957317149; Sun, 28 Sep 2014 19:21:57 -0700 (PDT) Message-ID: <047d7bacc10653a73805042aeeca@google.com> Date: Mon, 29 Sep 2014 02:21:57 +0000 Subject: Idea for getting more traffic: hk4u.com :RS From: Alex Luees To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 02:21:58 -0000 Hi Hk4u Team, Hope you are great and everything fine at your end. I have gone through your website and I felt its well built but can be improved in several ways to get better sales and revenue from the site. If you would like me to send you complete list of upgrading and improvements we could do to your site then kindly let me know so that I can send you the brief quotation for your website. After in-depth research about your website and analyzing the targeted market for your business to prevail, we also execute effective online marketing campaigns by targeting not only local markets but as well as provincial and international markets as well. So you will be getting *all-in-one services* when contacting us. It's only search engine tricks that need to keep changing when the ranking algorithm changes. We will help you to increase your visibility in all the major search engines by *improving keyword rankings* and *boosting your real time website traffic* with lots of back links which are always done through *White Hat* techniques, indeed you position your website properly to be found at the most critical points in the buying process or when people need your site. Our aim is to provide you with complete web marketing solutions to help your website rank high on the search engines. Before moving on further, we will have a consultation phase where we will discuss what your website goals are and how we can accomplish them. In addition, we may ask you certain questions that may be concerning on the website structure and strategic foundation for your social media marketing. Should you have any questions, please let us know. To improve the search engine visibility of your website, we will look forward to hear from you when you've time after reading our proposal. *Sincerely,* *Alex Luees* *Senior SEO Advisor* ........................................SS ...................................... From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 08:19:16 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D94959D3 for ; Mon, 29 Sep 2014 08:19:16 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C49A2A9 for ; Mon, 29 Sep 2014 08:19:16 +0000 (UTC) Received: from r56.edvax.de (port-92-195-3-171.dynamic.qsc.de [92.195.3.171]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 704BD3CBDE; Mon, 29 Sep 2014 10:09:38 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s8T89baP001959; Mon, 29 Sep 2014 10:09:37 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Mon, 29 Sep 2014 10:09:37 +0200 From: Polytropon To: Everett Batey Subject: Re: BASH Shellshock and FreeBSD 4.X Message-Id: <20140929100937.0527cbae.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Questions at FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 08:19:17 -0000 On Sun, 28 Sep 2014 13:59:13 -0700, Everett Batey wrote: > Severely stuck in Time - OLD FBSD .. any bright ideas around /bin/bash > risks AND NOT DONT TELL ME UPDATE FBSD .. - Dependencies I can NOT > escape .. Even if you actually have /bin/bash (in the root file system), it's not the system's scripting shell, standard subshell or standard interactive shell - except you made that change which usually is a Very Bad Idea(TM). Just because bash is installed doesn't imply your system is vulnerable to shellshock. If you have read about the construction of the exploit, you will know if you have vulnerable services running. But if you're just using bash as an interactive shell for a user, it shouldn't be a problem. :-) Updating a 3rd party shell does _not_ require updating your whole operating system. It _might_ be possible that you will encounter dependency problems (programs that depend on a specific version of bash, or bash itself that will require specific versions of other ports), but that should be a minimal problem and easily be solved. Note that bash is _not_ partof the FreeBSD operating system and therefore only lives in "/usr/local space". FreeBSD's standard scripting shell (and process subshell) is not bash, it's sh, a Bourne shell descendant in its implementation ash (Almquist shell) which is _not_ affected by shellshock. The C shell, FreeBSD's standard dialog shell, also doesn't care. > On other hand for FreeBSD 9.1-RELEASE-p7 is there an equivalent of yum > update bash? That depends on if you're using pkgng or pkg_ tools - or ports. The "impolite" method with (old) pkg_ tools: # pkg_delete -f /var/db/pkg/bash-x.y.z # pkg_add -r bash You can use tab completition to get the version number right. If you're using ports: # portsnap fetch update # cd /usr/ports/shells/bash # make deinstall # make # make reinstall You should now have the current (patched) version installed from source. Additionally, you can set custom options for bash if you need to (for example WITH_STATIC_BASH) - you only _have_ to do this if the default options (from which the packages are built) do not fit your requirements. Do you use a port management tool like portupgrade or portmaster? You can do it with one command: # portupgrade bash or # portmaster shells/bash Use the -P option if you don't want to compile from source, but use the binary package (similar to pkg_add mentioned above). See the manual of the program for reference. But if you're already using pkgng on your system, it's easier: # pkg upgrade bash This also uses a binary updating method. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 12:26:44 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8DBCBF8A; Mon, 29 Sep 2014 12:26:44 +0000 (UTC) Received: from webmail.dweimer.net (24-240-198-187.static.stls.mo.charter.com [24.240.198.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.dweimer.local", Issuer "webmail2.dweimer.local" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 590BF180; Mon, 29 Sep 2014 12:26:44 +0000 (UTC) Received: from www.dweimer.net (webmail [192.168.5.2]) by webmail.dweimer.net (8.14.7/8.14.7) with ESMTP id s8TCQaau060542 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 Sep 2014 07:26:37 -0500 (CDT) (envelope-from dweimer@dweimer.net) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 29 Sep 2014 07:26:36 -0500 From: dweimer To: Warren Block Subject: Re: update to =?UTF-8?Q?linux=5Fbase-c=36?= Organization: dweimer.net Reply-To: dweimer@dweimer.net Mail-Reply-To: dweimer@dweimer.net In-Reply-To: References: Message-ID: X-Sender: dweimer@dweimer.net User-Agent: Roundcube Webmail/1.0.2 Cc: owner-freebsd-questions@freebsd.org, Carmel NY , User questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 12:26:44 -0000 On 09/28/2014 7:13 pm, Warren Block wrote: > On Sun, 28 Sep 2014, Carmel NY wrote: > >> Sun, 28 Sep 2014 12:30:18 -0400 >> >> I want to update to emulators/linux_base-c6. According to UPDATING, I >> should >> remove all linux-f10 ports. In my case, that would be: >> > ... >> However, in addition to them, I have the following ports that depend >> on >> linux_base-f10: >> >> acroread9-9.5.5_1 >> acroreadwrapper-0.0.20130208 >> linux-libgtkembedmoz-0.0.20100806 >> nspluginwrapper-1.4.4_4 >> nvidia-driver-331.67_1 >> >> My question is, after removing the linux-f10 ports and the >> linux_base-f10, >> making the necessary changes to the /etc/makefile, etcetera and then >> installing linux_base-c6, do I have to then install the corresponding >> c6 >> ports for the f10 ports that have deleted or is that done >> automatically I >> assume, that I have to rebuild the remaining ports that use to depend >> on >> linux_base-f10? > > Of those, I only use nspluginwrapper, and had to manually reinstall it > after updating the linux ports. I upgraded my laptop on Saturday, I also had to rebuild nspluginwrapper, I am also using the nvidia-driver, and didn't rebuild it, all appears to be working fine this morning. -- Thanks, Dean E. Weimer http://www.dweimer.net/ From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 12:59:17 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D68387A for ; Mon, 29 Sep 2014 12:59:17 +0000 (UTC) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id 99E596C1 for ; Mon, 29 Sep 2014 12:59:15 +0000 (UTC) Received: from ppp118-210-82-160.lns20.adl2.internode.on.net (HELO leader.local) ([118.210.82.160]) by ipmail06.adl6.internode.on.net with ESMTP; 29 Sep 2014 22:29:07 +0930 Message-ID: <5429579A.7030501@ShaneWare.Biz> Date: Mon, 29 Sep 2014 22:29:06 +0930 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Everett Batey Subject: Re: BASH Shellshock and FreeBSD 4.X References: <20140929100937.0527cbae.freebsd@edvax.de> In-Reply-To: <20140929100937.0527cbae.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Questions at FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 12:59:17 -0000 On 29/09/2014 17:39, Polytropon wrote: > On Sun, 28 Sep 2014 13:59:13 -0700, Everett Batey wrote: >> Severely stuck in Time - OLD FBSD .. any bright ideas around /bin/bash >> risks AND NOT DONT TELL ME UPDATE FBSD .. - Dependencies I can NOT >> escape .. > If you're using ports: > > # portsnap fetch update > # cd /usr/ports/shells/bash > # make deinstall > # make > # make reinstall > I'm not 100% certain that the current ports tree will work on 4.x I'd keep a copy of your current tree before trying updates. If you have trouble with the current ports then put the old version back in place and look at the changes made to fix the issue and incorporate them into your tree. https://svnweb.freebsd.org/ports/head/shells/bash/ -- FreeBSD - the place to B...Serving Data Shane Ambler From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 13:04:25 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 786EF934 for ; Mon, 29 Sep 2014 13:04:25 +0000 (UTC) Received: from eu1sys200aog127.obsmtp.com (eu1sys200aog127.obsmtp.com [207.126.144.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA6E17CC for ; Mon, 29 Sep 2014 13:04:24 +0000 (UTC) Received: from mail-we0-f180.google.com ([74.125.82.180]) (using TLSv1) by eu1sys200aob127.postini.com ([207.126.147.11]) with SMTP ID DSNKVClY1jC/upui427jg7HhGN020zj6IjAS@postini.com; Mon, 29 Sep 2014 13:04:24 UTC Received: by mail-we0-f180.google.com with SMTP id x48so2143706wes.39 for ; Mon, 29 Sep 2014 06:04:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:message-id:to:subject:reply-to; bh=Yx5+O+ufdhmtpvtnSG0EUCcika+cmnqoamDCUgp/AWw=; b=UqLV7FQRam03+LQibGW/to/qeX2Lx+FrIIrW6lZMzsXX3yjLGNFaCvvZ98XqdJ1IE5 AoAsdyzG/snwJbGNHUu4MsDfiTJj4nKfebQVqgyCnMQN0uWfzERZTNzp/iD5ZRFJTzK+ 2SumDzpYMT6YRZbH/lKN8aVW7vqZcW/mlhOaM3S1g866GIM3YVisYzleJmpXXAPlIJDf vMbrHynXz1NRqpFqvz8wEFTZZtXFbIvVwO64QRJgCRewyUHEEHWUmwvxADVSmWViodmc WtduuG5+RyI+7OFdCVtz82RzXYc1Z7PDxBWkg/ORnVIW8/95h598epo4pWk3Jb+JIz2s EDYg== X-Received: by 10.194.94.165 with SMTP id dd5mr43007036wjb.75.1411994203196; Mon, 29 Sep 2014 05:36:43 -0700 (PDT) X-Gm-Message-State: ALoCoQkHOGx4o0UwQBHqX0CG2n2KR8ATyRQk775M1iAFWTJ1XydDfxM70Jz7rKy9MVVBC22VUBVICqcYYhA0zE7/aHKZIKBpdv7IJJg06aZT426l7g5ymaxSyy9YPijuSWPPwOaFv7rFx+U81nMD5HnI+NVvkBN67Ymm+lsrxgUuF7fT2g03XZo= X-Received: by 10.194.94.165 with SMTP id dd5mr43006968wjb.75.1411994202536; Mon, 29 Sep 2014 05:36:42 -0700 (PDT) Received: from mech-as221.men.bris.ac.uk (mech-as221.men.bris.ac.uk. [137.222.187.221]) by mx.google.com with ESMTPSA id ll20sm11548642wic.14.2014.09.29.05.36.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Sep 2014 05:36:41 -0700 (PDT) Received: from mech-as221.men.bris.ac.uk (localhost [127.0.0.1]) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9) with ESMTP id s8TCabj8096964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 29 Sep 2014 13:36:37 +0100 (BST) (envelope-from mexas@mech-as221.men.bris.ac.uk) Received: (from mexas@localhost) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9/Submit) id s8TCablW096962 for freebsd-questions@freebsd.org; Mon, 29 Sep 2014 13:36:37 +0100 (BST) (envelope-from mexas) Date: Mon, 29 Sep 2014 13:36:37 +0100 (BST) From: Anton Shterenlikht Message-Id: <201409291236.s8TCablW096962@mech-as221.men.bris.ac.uk> To: freebsd-questions@freebsd.org Subject: two hosts sharing the same data fia SAN? Reply-To: mexas@bristol.ac.uk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:04:25 -0000 Hello I've 2 separate freebsd boxes, each connected vi fibre to a disk array. I'd like to have a set of disk units to be read/write accessible to both boxes. Seems this is not allowed with just UFS. If one box mounts the disk units, then the other box cannot mount them, i.e. seems the disks cannot be mounted on both boxes simultaneously. How can this be achived? I've had a quick look at HAST, but it seems the model their is different. Thanks Anton From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 13:06:52 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C30A9F7 for ; Mon, 29 Sep 2014 13:06:52 +0000 (UTC) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2E3B77F8 for ; Mon, 29 Sep 2014 13:06:52 +0000 (UTC) Received: from kabini1.local (rbn1-216-180-19-71.adsl.hiwaay.net [216.180.19.71]) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id s8TD6h8v008944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 29 Sep 2014 08:06:44 -0500 Message-ID: <54295ADA.6020007@hiwaay.net> Date: Mon, 29 Sep 2014 08:12:58 -0500 From: "William A. Mahaffey III" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: two hosts sharing the same data fia SAN? References: <201409291236.s8TCablW096962@mech-as221.men.bris.ac.uk> In-Reply-To: <201409291236.s8TCablW096962@mech-as221.men.bris.ac.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:06:52 -0000 On 09/29/14 07:36, Anton Shterenlikht wrote: > Hello > > I've 2 separate freebsd boxes, each connected > vi fibre to a disk array. I'd like to have > a set of disk units to be read/write accessible > to both boxes. Seems this is not allowed with just > UFS. If one box mounts the disk units, then the > other box cannot mount them, i.e. seems the > disks cannot be mounted on both boxes simultaneously. > How can this be achived? > > I've had a quick look at HAST, but it seems the > model their is different. > > Thanks > > Anton > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > NFS ? -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 13:38:15 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9F12821B for ; Mon, 29 Sep 2014 13:38:15 +0000 (UTC) Received: from sbg-out.inti.gob.ar (sbg-out.inti.gov.ar [200.10.161.69]) by mx1.freebsd.org (Postfix) with ESMTP id 14049B8A for ; Mon, 29 Sep 2014 13:38:13 +0000 (UTC) X-AuditID: c80aa145-f790b6d000003bd1-7f-54295d390a89 Received: from [200.10.161.55] (jb.inti.gov.ar [200.10.161.55]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by sbg-out.inti.gob.ar (SMTP_INTI) with SMTP id C6.BA.15313.93D59245; Mon, 29 Sep 2014 10:23:06 -0300 (ART) Message-ID: <54295D32.4020908@inti.gob.ar> Date: Mon, 29 Sep 2014 10:22:58 -0300 From: Juan Bernhard User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: two hosts sharing the same data fia SAN? References: <201409291236.s8TCablW096962@mech-as221.men.bris.ac.uk> <54295ADA.6020007@hiwaay.net> In-Reply-To: <54295ADA.6020007@hiwaay.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnluLIzCtJLcpLzFFi42I5wbXQXNcqVjPE4ORiJouXXzexODB6zPg0 nyWAMYrLJiU1J7MstUjfLoEr4+7uD8wFvzkqZje/YWpgnMnexcjJISFgIrH0+RFmCFtM4sK9 9WxdjFwcQgJdTBIts28wgiR4BbQkpp97xAZiswioSkx9uYoFxGYTUJP4euYUK4gtKhAlcWF+ D1S9oMTJmU/AakQEFCXOnGkEqxEWMJX4v+kU0DIOoAWJEgf3BIGEOYHGL5j3Fmw8s4COxLu+ B8wQtrxE89bZzBMY+WYhmToLSdksJGULGJlXMQoXJ6Xr5peW6AGDKFMvPT9JL7FoEyMkmFx3 MO5dp36IUYCDUYmH1+C0RogQa2JZcWXuIUYJDmYlEV47W80QId6UxMqq1KL8+KLSnNTiQ4zS HCxK4rz7l74OFhJITyxJzU5NLUgtgskycXBKNTDapDkpJfy0eZjKOCda7XPkrcbZJ/l8Khcs Wxl6cO41mckyvg+AIokizr53+qrmn5Q5VmSm0H2Kc4nwmdbuLzeVG1/zPA1x7l27tO6V4/mL C2eYbu3IfJlgfutzeE6UPrOxtPe61AcNafrqj//1CK3/zOB792V8UYMGd/AFKyEW7eMakQf7 lViKMxINtZiLihMBUW3u7SICAAA= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:38:15 -0000 El 29/09/2014 10:12 a.m., William A. Mahaffey III escribió: > On 09/29/14 07:36, Anton Shterenlikht wrote: >> Hello >> >> I've 2 separate freebsd boxes, each connected >> vi fibre to a disk array. I'd like to have >> a set of disk units to be read/write accessible >> to both boxes. Seems this is not allowed with just >> UFS. If one box mounts the disk units, then the >> other box cannot mount them, i.e. seems the >> disks cannot be mounted on both boxes simultaneously. >> How can this be achived? >> >> I've had a quick look at HAST, but it seems the >> model their is different. >> >> Thanks >> >> Anton >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > > NFS ? You need a clustered file system, like GFS for linux. At the moment I dont know if there are any working on freebsd. NFS is for sharind disk at file level, but if you want to share a disk al block level, you need a clustered fs. Saludos, Juan. From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 13:41:14 2014 Return-Path: Delivered-To: FreeBSD-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AAC912DB for ; Mon, 29 Sep 2014 13:41:14 +0000 (UTC) Received: from feeder.usenet4all.se (1-1-1-38a.far.sth.bostream.se [82.182.32.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 31EE1BAF for ; Mon, 29 Sep 2014 13:41:13 +0000 (UTC) Received: from kw.news4all.se (localhost [127.0.0.1]) by feeder.usenet4all.se (8.13.1/8.13.1) with ESMTP id s8TDVYQA048205 for ; Mon, 29 Sep 2014 15:31:34 +0200 (CEST) (envelope-from bah@bananmonarki.se) Message-ID: <54295F36.5080001@bananmonarki.se> Date: Mon, 29 Sep 2014 15:31:34 +0200 From: Bernt Hansson User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: "f >> questions FreeBSD" Subject: Problems with pkg Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:41:14 -0000 Hello list! I want to install kicad but getting this error: root@kw:/usr/ports # make clean Child process pid=41973 terminated abnormally: Segmentation fault: 11 "/usr/ports/Mk/bsd.port.mk", line 1222: warning: "/usr/local/sbin/pkg-static ver sion -t 1.3.8 1.3.8" returned non-zero status Child process pid=41987 terminated abnormally: Segmentation fault: 11 "/usr/ports/Mk/bsd.port.mk", line 1222: warning: "/usr/local/sbin/pkg-static ver sion -t 1.3.8 1.3.8" returned non-zero status Child process pid=42001 terminated abnormally: Segmentation fault: 11 "/usr/ports/Mk/bsd.port.mk", line 1222: warning: "/usr/local/sbin/pkg-static ver sion -t 1.3.8 1.3.8" returned non-zero status Child process pid=42015 terminated abnormally: Segmentation fault: 11 "/usr/ports/Mk/bsd.port.mk", line 1222: warning: "/usr/local/sbin/pkg-static ver sion -t 1.3.8 1.3.8" returned non-zero status From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 13:51:48 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C28DD757 for ; Mon, 29 Sep 2014 13:51:48 +0000 (UTC) Received: from eu1sys200aog113.obsmtp.com (eu1sys200aog113.obsmtp.com [207.126.144.135]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2029ED58 for ; Mon, 29 Sep 2014 13:51:47 +0000 (UTC) Received: from mail-wi0-f173.google.com ([209.85.212.173]) (using TLSv1) by eu1sys200aob113.postini.com ([207.126.147.11]) with SMTP ID DSNKVClj1UBY0vkxJeZsn50MQs6W5rcq4wz8@postini.com; Mon, 29 Sep 2014 13:51:48 UTC Received: by mail-wi0-f173.google.com with SMTP id bs8so1979525wib.12 for ; Mon, 29 Sep 2014 06:51:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:message-id:to:subject:reply-to :in-reply-to; bh=GuIMQqSSh/PkwjuPQNyvpW/C+DCeoEe2YhnpJDeQhiM=; b=Oqjg1fHoj/27XoB/CJfKa7qBqAV34YWOPxHsQSDZ4gvCchebl9JuBWKlYrgTQygjMp SWq+1A+2zW1pyzN5H1BfwLFmtHIW+q75h+hBc6b4xiTqyYdN13SeI45HICJ14FTKP3qz bwBPDOiXk39yC6AI2p8RDCUT45VTuyTPll8wQvefcYXOvp2XffCb9EysuYzQnAADfPjV jUo4iqVEYiqFPeab5IguNntXqX/CcYtIvhXHIyscj/NRN8Zuya//3wWHOk2kY+FgN+jG YOVKaUec4SlaFaZ1qLTgSEH+x5Qlh9YJDMGtOudBZWE8lLsFYpVIMeh0uZmkzr9Gq0OY /mKg== X-Gm-Message-State: ALoCoQm3hHq9NwonnmD6qgBMQEp8MyTv0jjLBz5r2+Qw7GaUa0KqOfsqpKyCCXtBDT8pzfbj1GpuQFOMQRts1r5RrV1RzJeD9C8rBSAtgTitX5Kg7+YYrMpEbFkKcPO6BfhjGbqHxWbMmapgg1R/Pori/2Y1pD73/DSiElIr4/MpIgMoC+cp1EQ= X-Received: by 10.194.237.9 with SMTP id uy9mr2961257wjc.132.1411998677831; Mon, 29 Sep 2014 06:51:17 -0700 (PDT) X-Received: by 10.194.237.9 with SMTP id uy9mr2961249wjc.132.1411998677744; Mon, 29 Sep 2014 06:51:17 -0700 (PDT) Received: from mech-as221.men.bris.ac.uk (mech-as221.men.bris.ac.uk. [137.222.187.221]) by mx.google.com with ESMTPSA id q2sm11741927wiy.23.2014.09.29.06.51.16 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Sep 2014 06:51:17 -0700 (PDT) Received: from mech-as221.men.bris.ac.uk (localhost [127.0.0.1]) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9) with ESMTP id s8TDpF2a052014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 Sep 2014 14:51:16 +0100 (BST) (envelope-from mexas@mech-as221.men.bris.ac.uk) Received: (from mexas@localhost) by mech-as221.men.bris.ac.uk (8.14.9/8.14.9/Submit) id s8TDpFPY052009; Mon, 29 Sep 2014 14:51:15 +0100 (BST) (envelope-from mexas) Date: Mon, 29 Sep 2014 14:51:15 +0100 (BST) From: Anton Shterenlikht Message-Id: <201409291351.s8TDpFPY052009@mech-as221.men.bris.ac.uk> To: freebsd-questions@freebsd.org, juan@inti.gob.ar Subject: Re: two hosts sharing the same data fia SAN? Reply-To: mexas@bristol.ac.uk In-Reply-To: <54295D32.4020908@inti.gob.ar> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 13:51:48 -0000 >> On 09/29/14 07:36, Anton Shterenlikht wrote: >>> Hello >>> >>> I've 2 separate freebsd boxes, each connected >>> vi fibre to a disk array. I'd like to have >>> a set of disk units to be read/write accessible >>> to both boxes. Seems this is not allowed with just >>> UFS. If one box mounts the disk units, then the >>> other box cannot mount them, i.e. seems the >>> disks cannot be mounted on both boxes simultaneously. >>> How can this be achived? >>> >>> I've had a quick look at HAST, but it seems the >>> model their is different. >>> >>> Thanks >>> >>> Anton >>> _______________________________________________ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscribe@freebsd.org" >>> >> >> NFS ? > >You need a clustered file system, like GFS for linux. At the moment I >dont know if there are any working on freebsd. NFS is for sharind disk >at file level, but if you want to share a disk al block level, you need >a clustered fs. > >Saludos, Juan. cluster file system...? How do I get one in FreeBSD. >From looking in the archives, many people ask for one periodically, but it seems it's not there. NFS, HAST and iSCSI all seem do something different from what I need. In my case both nodes (actually I have more than two, but it's perhaps easier to explain with just two) have direct fibre access to the storage, no network required. Also, it makes no sense to delegate one node a server and another a client in my setup. I'd like them to be identical, so that access to the data is equally possible if either node fails. The disk array alreay provides multiple levels of RAID, so I don't need this. So is something like this really does not exist on FreeBSD (yet) ? Thanks Anton From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 14:03:23 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1984DBFB for ; Mon, 29 Sep 2014 14:03:23 +0000 (UTC) Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DF7F9E74 for ; Mon, 29 Sep 2014 14:03:22 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id p10so5354837pdj.14 for ; Mon, 29 Sep 2014 07:03:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=XU9LCjB9cOUA2YdDXE716AYHPE9KE2fyY0r15f2kDEw=; b=f0MRSa19RoPCEORheNmhMUl5rgEGSJLxut2buK0wJKG7p0R8niYAi/VRZkfYNaYQH9 QL5x2xRDLU9Q0k3EeZ/BgaqM7iUNgwWLxrlnmPOTYyt0VJii5p2tc9qLdwqOV/7D3IwT /E5mB6H26ss7sOfEHZ+iI4IoElJN8L89ZbpPh4ylIpZf6+vQGvo2rwAKmZm3P+RjHWqJ dTc82YCzjPcXfYp1j37sQxFO5gWL3JKL7CHEQqLAoA+pn7yRbx/xaqVVP+ABwuuKQR7q z20rzo7SqyVZlnE7D2MojDKzjKybEYT4IWhHrXmwGW7Cv/tlxaR9UWfsB0h/ZRk4jnQz tC+Q== X-Gm-Message-State: ALoCoQlBopb74VvI7Mp3W6aCnvZEIwD8yjqfQQKP37jblaXnqhX0A7aMwcVLi+lciduzCVzIrf8t X-Received: by 10.68.103.4 with SMTP id fs4mr61343804pbb.58.1411999396719; Mon, 29 Sep 2014 07:03:16 -0700 (PDT) Received: from wide.rdtan.net ([175.136.182.168]) by mx.google.com with ESMTPSA id xf9sm3203504pab.2.2014.09.29.07.03.13 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Sep 2014 07:03:15 -0700 (PDT) Received: from localhost (1000@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id bb9a1ef3; Mon, 29 Sep 2014 22:03:09 +0800 (MYT) Date: Mon, 29 Sep 2014 22:03:09 +0800 From: Edward To: kpneal@pobox.com Subject: Re: pkg_delete bash, logged out by accident, can't ssh back in (not good) Message-ID: <20140929140309.GC19085@wide.rdtan.net> References: <20140927030810.GC23533@wide.rdtan.net> <20140929133329.GA83452@neutralgood.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140929133329.GA83452@neutralgood.org> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "firmdog@gmail.com" , Edward , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 14:03:23 -0000 On Mon, Sep 29, 2014 at 09:33:29AM -0400, kpneal@pobox.com wrote: > On Sat, Sep 27, 2014 at 11:08:11AM +0800, Edward wrote: > > After a few times stepping on this problem when upgrading ports, picked > > up a habit. Leave /bin/{k}sh as default shell and always "tmux new" > > after remote login. > > FreeBSD does not ship with /bin/ksh, so I suggest not using it as the > default shell for either root or the account you use to log in remotely. Thanks for pointing that out. The default shells are /bin/{tc}sh, mentioned[1] in handbook. [1]https://www.freebsd.org/doc/handbook/shells.html From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 15:23:39 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94DDCCE0 for ; Mon, 29 Sep 2014 15:23:39 +0000 (UTC) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56B33A64 for ; Mon, 29 Sep 2014 15:23:38 +0000 (UTC) Received: from r56.edvax.de (port-92-195-99-5.dynamic.qsc.de [92.195.99.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 5AFBB2766E; Mon, 29 Sep 2014 17:23:30 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s8TFNTrB002144; Mon, 29 Sep 2014 17:23:29 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Mon, 29 Sep 2014 17:23:29 +0200 From: Polytropon To: Shane Ambler Subject: Re: BASH Shellshock and FreeBSD 4.X Message-Id: <20140929172329.08163a41.freebsd@edvax.de> In-Reply-To: <5429579A.7030501@ShaneWare.Biz> References: <20140929100937.0527cbae.freebsd@edvax.de> <5429579A.7030501@ShaneWare.Biz> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Questions at FreeBSD , Everett Batey X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 15:23:39 -0000 On Mon, 29 Sep 2014 22:29:06 +0930, Shane Ambler wrote: > On 29/09/2014 17:39, Polytropon wrote: > > On Sun, 28 Sep 2014 13:59:13 -0700, Everett Batey wrote: > >> Severely stuck in Time - OLD FBSD .. any bright ideas around /bin/bash > >> risks AND NOT DONT TELL ME UPDATE FBSD .. - Dependencies I can NOT > >> escape .. > > > If you're using ports: > > > > # portsnap fetch update > > # cd /usr/ports/shells/bash > > # make deinstall > > # make > > # make reinstall > > > > I'm not 100% certain that the current ports tree will work on 4.x > > I'd keep a copy of your current tree before trying updates. If you have > trouble with the current ports then put the old version back in place > and look at the changes made to fix the issue and incorporate them into > your tree. Yes, _that_ might be a problem... On the other hand, maybe it would even be possible to check out the current source for bssh (and maybe its dependencies) and build them "off the track", i. e., not using the ports infrastructure at all, and then manually copying the resulting binary to the required place, as well as its libraries (unless static linking has been enabled). It's worth having a look at ./configure's options to tune this approach. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-questions@FreeBSD.ORG Mon Sep 29 21:36:42 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94505A77 for ; Mon, 29 Sep 2014 21:36:42 +0000 (UTC) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B33AB5C for ; Mon, 29 Sep 2014 21:36:41 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id x3so2541529qcv.10 for ; Mon, 29 Sep 2014 14:36:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=date:from:to:subject:message-id:in-reply-to:references:organization :mime-version:content-type:content-transfer-encoding; bh=1wcphf5c80J2wVr9Q/NvsYZ9CMGyWtEAs/KOXut39EI=; b=Dv7CNuvzWUX59HJ4YgJHrqTARmsTVf4JiVFNG7BEPc1HdQvxjTG0Mu2yy/CXH0bs37 Qygk5KGQfGBHLkNV/e4b21y1OXG3Y/IRJSe3Q7NP5b3D80vRAldnwtmYj61Ya1tiBzCx Wn9JcGLEQknv0JmSXVokh3Yc7Jvn6keGIwLlc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:organization:mime-version:content-type :content-transfer-encoding; bh=1wcphf5c80J2wVr9Q/NvsYZ9CMGyWtEAs/KOXut39EI=; b=Z+0iwRYrhmv/GXJhQ4yCsiD19ZqTXAcPydlDEQaOgxrHiLtob6hBM4mmnoioSXuWGI 6fQHx6D32IVPO7AeePFT4q9ZO4fRfxRcgEhTUEpSH/9ypxCkkVwNg7W764BP8Kwzv+SW a/hX+//k6UiRASE6TORweRhaJ54QVhBB3uHODkDMjPJIzjn7yWKd6pdaLdwaD86WQzj0 1jWeHQ95R2XQIoLLbKxuxFWqBoZNIoVi2amCM5lslY33pvS/nlyQlZ6xy/xUIA5vKkua OpjU2rw37yWCY66W7DDoZykTBtKU9gEb3fve29rP8EmzW7rJh9P+to44m44FG4H6u64O FK1Q== X-Gm-Message-State: ALoCoQl/E/y6ze1X6wJUlaf4xuJO0TnhWvvuHCD1XIe6o7GufYJW/vPqF3ObG1f5ZVnwpQN29P3O X-Received: by 10.224.86.68 with SMTP id r4mr33724024qal.0.1412026600066; Mon, 29 Sep 2014 14:36:40 -0700 (PDT) Received: from Papi ([177.43.10.42]) by mx.google.com with ESMTPSA id 4sm12220866qax.48.2014.09.29.14.36.39 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Sep 2014 14:36:39 -0700 (PDT) Date: Mon, 29 Sep 2014 18:36:55 -0300 From: Mario Lobo To: freebsd-questions@freebsd.org Subject: Re: BASH Shellshock and FreeBSD 4.X Message-ID: <20140929183655.361534e8@Papi> In-Reply-To: <20140929172329.08163a41.freebsd@edvax.de> References: <20140929100937.0527cbae.freebsd@edvax.de> <5429579A.7030501@ShaneWare.Biz> <20140929172329.08163a41.freebsd@edvax.de> Organization: BSD X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 21:36:42 -0000 On Mon, 29 Sep 2014 17:23:29 +0200 Polytropon wrote: > On Mon, 29 Sep 2014 22:29:06 +0930, Shane Ambler wrote: > > On 29/09/2014 17:39, Polytropon wrote: > > > On Sun, 28 Sep 2014 13:59:13 -0700, Everett Batey wrote: > > >> Severely stuck in Time - OLD FBSD .. any bright ideas > > >> around /bin/bash risks AND NOT DONT TELL ME UPDATE FBSD .. - > > >> Dependencies I can NOT escape .. > > > > > If you're using ports: > > > > > > # portsnap fetch update > > > # cd /usr/ports/shells/bash > > > # make deinstall > > > # make > > > # make reinstall > > > > > > > I'm not 100% certain that the current ports tree will work on 4.x > > > > I'd keep a copy of your current tree before trying updates. If you > > have trouble with the current ports then put the old version back > > in place and look at the changes made to fix the issue and > > incorporate them into your tree. > > Yes, _that_ might be a problem... > > On the other hand, maybe it would even be possible to check > out the current source for bssh (and maybe its dependencies) > and build them "off the track", i. e., not using the ports > infrastructure at all, and then manually copying the resulting > binary to the required place, as well as its libraries (unless > static linking has been enabled). It's worth having a look at > ./configure's options to tune this approach. > > Everett; Why don't you give this a try: #--------------------------- #cat bash_bsd_fix.sh mkdir src cd src fetch http://ftp.gnu.org/gnu/bash/bash-4.3.tar.gz for i in $(jot -w %03d 25); do fetch http://ftp.gnu.org/gnu/bash/bash-4.3-patches/bash43-$i; done tar zxvf bash-4.3.tar.gz cd bash-4.3 for i in $(jot -w %03d 25);do patch -p0 < ../bash43-$i; done ./configure && make #--------------------------- If it compiles without errors, then: #--------------------------- make install cd .. cd .. rm -r src #--------------------------- I got this script from a colleague in the Brazilian BSD list. He used it to update his old servers. It was tested only on 8.1 and up but I don't see why you can't give it a spin. I used it withou any problems on all my 8.x servers. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winblows FREE) "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." From owner-freebsd-questions@FreeBSD.ORG Tue Sep 30 00:56:30 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 20C3DAC1 for ; Tue, 30 Sep 2014 00:56:30 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CDA16E7 for ; Tue, 30 Sep 2014 00:56:29 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.9/8.14.9) with ESMTP id s8U0uOWn055118; Mon, 29 Sep 2014 20:56:24 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <5429FFA3.7030200@sentex.net> Date: Mon, 29 Sep 2014 20:56:03 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Mario Lobo , freebsd-questions Subject: Re: BASH Shellshock and FreeBSD 4.X References: <20140929100937.0527cbae.freebsd@edvax.de> <5429579A.7030501@ShaneWare.Biz> <20140929172329.08163a41.freebsd@edvax.de> <20140929183655.361534e8@Papi> In-Reply-To: <20140929183655.361534e8@Papi> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.74 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 00:56:30 -0000 On 9/29/2014 5:36 PM, Mario Lobo wrote: > for i in $(jot -w %03d 25); do > for i in $(jot -w %03d 25);do patch -p0 < ../bash43-$i; done Hi, there are 27 patches now. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-questions@FreeBSD.ORG Tue Sep 30 01:32:26 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 06885FC0 for ; Tue, 30 Sep 2014 01:32:26 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6BA202DD for ; Tue, 30 Sep 2014 01:32:25 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id mk6so2944067lab.1 for ; Mon, 29 Sep 2014 18:32:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=3Nml9R8eoN5skUhYFC5jj1dbD615Rr84iKTAFEZfQ3U=; b=mOqnwayZ0ZuAQzu2a6CBa49D2UeZjxjCF63Mcw7hRxDpQmD/p9aFqRe9yvDBCkt2Hc E8cznFj5H4FgaENV7VJVIk784vsCv/yI2xNFFDgHFnZrRQoj3MUVAkHfDNEaOklaXzqf 72jjwWVo6ltzjWxr8euXOdf9RTF6qvWRn2kPvdSzUXzv1oWkk8yGnz5tfMX13aSVD+cG hUl/UViTng9eJ3NYV/4ZZwjmD0Hem6V/EWOqJ5JttraYzKsg+O4Z+TM3IFVbeOhGHCm1 8Nbg0OS5OTlAw4N3JVkKTtp5yF8AWNqMZItb9SHWf6CXFf4zodbMIqQ4yU0BKZdO4w7H oYzg== MIME-Version: 1.0 X-Received: by 10.152.21.168 with SMTP id w8mr44254469lae.59.1412040743226; Mon, 29 Sep 2014 18:32:23 -0700 (PDT) Received: by 10.152.19.6 with HTTP; Mon, 29 Sep 2014 18:32:23 -0700 (PDT) In-Reply-To: References: <23187F4C-0413-4F84-9C86-6EC1084C794C@btinternet.com> <50282.76.192.184.214.1411925201.squirrel@cosmo.uchicago.edu> Date: Mon, 29 Sep 2014 21:32:23 -0400 Message-ID: Subject: Re: [Bulk] Re: freebsd-update question From: "firmdog@gmail.com" To: Axel Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-questions@freebsd.org" , galtsev , FF , Dave X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 01:32:26 -0000 Thanks. My freebsd server is on Amazon AWS using http://www.daemonology.net/freebsd-on-ec2/ A bit nervous because there is no local console. Just installed a new test/obsolete 8.3 box and will try the upgrade to 8.4 using these commands: svn co svn://svn.freebsd.org/base/stable/8 /usr/src cd /usr/src make buildworld make kernel make installworld mergemaster -Ui reboot On Sun, Sep 28, 2014 at 3:30 PM, Axel wrote: > On Sun, Sep 28, 2014 at 9:04 PM, firmdog@gmail.com > wrote: >> >> OK. I will try that. Found these notes from 10 years ago. Gonna give >> this a try, not sure if cvsup will work anymore.... >> >> >> cvsup -g -L 2 update-file >> >> The update-file contains this: >> >> *default host=3Dcvsup11.us.FreeBSD.org >> *default base=3D/var/db >> *default prefix=3D/usr >> *default release=3Dcvs tag=3DRELENG_8 >> *default delete use-rel-suffix >> src-all >> ports-all tag=3D. >> doc-all tag=3D. >> >> cd /usr/src >> >> make buildworld >> >> make buildkernel >> >> make installkernel >> >> mergemaster >> >> make installworld >> >> >> >> >> >> >> On Sun, Sep 28, 2014 at 2:36 PM, FF wrote: >> > So your kernel won't be updated because you are running a custom kerne= l. >> > Your uname is based on the running kernel. >> > >> > If you want to confirm that you've in fact updated, you can reboot to >> > the >> > GENERIC kernel which will confirm you are at 8.4 or whatever. FreeBSD >> > update >> > is a binary update based on the release versions -- deviate from them >> > and it >> > doesn't break, but it can't touch those files. >> > >> > Since you know enough to put a custom kernel on there, you should foll= ow >> > the >> > source rebuild instructions which would be basically be to svn down th= e >> > whole 8.4 source tree, make the world, make the kernel and install it, >> > reboot, and install the world. >> > >> > I think the directions are in the FreeBSD handbook. >> > >> > Best, >> > >> > >> > >> > On Sun, Sep 28, 2014 at 1:26 PM, Valeri Galtsev >> > >> > wrote: >> >> >> >> >> >> On Sun, September 28, 2014 10:01 am, firmdog@gmail.com wrote: >> >> > I just installed a brand new 8.3 box and got the same behavior. I s= ee >> >> > in my output below that I have to build or update my own kernel? >> >> > >> >> > >> >> > # uname -a >> >> > FreeBSD 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 10 17:33:58 UTC >> >> > 2012 root@mynewhost:/usr/obj/i386/usr/src/sys/XENHVM i386 >> >> > # >> >> > >> >> > Starting the upgrade attempt: >> >> > >> >> > # freebsd-update -r 8.4-RELEASE upgrade >> >> > Looking up update.FreeBSD.org mirrors... 5 mirrors found. >> >> > Fetching public key from update6.freebsd.org... done. >> >> > Fetching metadata signature for 8.3-RELEASE from >> >> > update6.freebsd.org... >> >> > done. >> >> > Fetching metadata index... done. >> >> > Fetching 2 metadata files... done. >> >> > Inspecting system... done. >> >> > >> >> > WARNING: This system is running a "xenhvm" kernel, which is not a >> >> > kernel configuration distributed as part of FreeBSD 8.3-RELEASE. >> >> > This kernel will not be updated: you MUST update the kernel manuall= y >> >> > before running "/usr/sbin/freebsd-update install". >> >> > >> >> > The following components of FreeBSD seem to be installed: >> >> > src/bas