From owner-freebsd-questions@FreeBSD.ORG Sun Feb 20 16:15:48 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2A64106564A for ; Sun, 20 Feb 2011 16:15:48 +0000 (UTC) (envelope-from mats.w.lindberg@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 121438FC17 for ; Sun, 20 Feb 2011 16:15:47 +0000 (UTC) Received: by ewy9 with SMTP id 9so686169ewy.13 for ; Sun, 20 Feb 2011 08:15:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:references:from:content-type:x-mailer :in-reply-to:message-id:date:to:content-transfer-encoding :mime-version; bh=8OlanGHi6cv5BjaDoAPmVb/iGpRk/iOCaPGxfnmJFrQ=; b=Uig37uCOmHpKk8MdKACFo8C4UsOptKgNTv2zxTSIpW6YB9m17gaSdCuw41ucWXJfeZ p1wSMTSIC5lUuL1fsbl45/ugV09k3WM1XWY4XMNaf53vn8TSLXVLbwF80FKELQdrfUar zAXWecJVSvl85xO6H+uw6jaX6gZd/smSTiWWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; b=s5QkZg+Uyhz+FSPUO5ftIMH3R4V4GLH6MmEEMxrE/nuBz2rENoSFA8vl5H1RBihjY1 D3e6FmOil5tipbBcA4N0haqb8DbelDEleE5T5jTYruurYdZq6qzox+Pnd8J9x9PsJoWE v9eMENPoASEEOLzRR3ZN9yysU1VbiIXnw24I8= Received: by 10.213.14.137 with SMTP id g9mr170030eba.69.1298218545624; Sun, 20 Feb 2011 08:15:45 -0800 (PST) Received: from [10.0.1.3] (h139n1fls306o1032.telia.com [81.226.106.139]) by mx.google.com with ESMTPS id t5sm4030721eeh.14.2011.02.20.08.15.42 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 20 Feb 2011 08:15:44 -0800 (PST) References: <20110219221457.0E12610656EB@hub.freebsd.org> From: Mats Lindbeg Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (8C148) In-Reply-To: <20110219221457.0E12610656EB@hub.freebsd.org> Message-Id: <03DE2E55-E3F3-4E20-9142-70C7BEAE81C7@gmail.com> Date: Sun, 20 Feb 2011 17:15:35 +0100 To: "freebsd-questions@freebsd.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPhone Mail 8C148) Subject: Re: freebsd-questions Digest, Vol 350, Issue 10 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2011 16:15:48 -0000 19 feb 2011 kl. 23:14 skrev freebsd-questions-request@freebsd.org: > Send freebsd-questions mailing list submissions to > freebsd-questions@freebsd.org >=20 > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > or, via email, send a message with subject or body 'help' to > freebsd-questions-request@freebsd.org >=20 > You can reach the person managing the list at > freebsd-questions-owner@freebsd.org >=20 > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-questions digest..." >=20 >=20 > Today's Topics: >=20 > 1. Re: ZFS-only booting on FreeBSD (Matthew Seaman) > 2. Re: booting a kernel directly from stage 1/2 (Matthew Seaman) > 3. Re: booting a kernel directly from stage 1/2 (Alexander Best) > 4. Re: ZFS-only booting on FreeBSD (Daniel Staal) > 5. Developing Embedded Network Device on FreeBSD (David) > 6. Re: ZFS-only booting on FreeBSD (Matthew Seaman) > 7. Re: Best Laptop to buy for Freebsd Without OS? (Maciej Milewski) > 8. Re: Developing Embedded Network Device on FreeBSD (Matthew Seaman) > 9. 8.2-PRERELEASE? (Harald Servat) > 10. Re: ZFS-only booting on FreeBSD (Daniel Staal) > 11. Re: Developing Embedded Network Device on FreeBSD (David) > 12. Re: Developing Embedded Network Device on FreeBSD (David Lapsley) > 13. Re: ZFS-only booting on FreeBSD (krad) > 14. Re: ZFS-only booting on FreeBSD (Andy Tornquist) > 15. Re: Best Laptop to buy for Freebsd Without OS? > (Christopher J. Ruwe) > 16. Re: ZFS-only booting on FreeBSD (Robert Bonomi) > 17. Re: Best Laptop to buy for Freebsd Without OS? (David Brodbeck) > 18. How to forward old root mails to an external email address? > (Andy Wodfer) > 19. Re: How to forward old root mails to an external email > address? (Daniel Staal) > 20. Re: ZFS-only booting on FreeBSD (Matthew Seaman) > 21. Re: BSD Magazine PDFs (Alfredo Perez) > 22. Re: How to forward old root mails to an external email > address? (Andy Wodfer) > 23. Re: BSD Magazine PDFs (Mike Jeays) > 24. Re: ZFS-only booting on FreeBSD (Daniel Staal) > 25. Re: ZFS-only booting on FreeBSD (David Brodbeck) > 26. Can motorola v195 be supported as network interface? (Yuri) > 27. Re: How to forward old root mails to an external email > address? (RW) >=20 >=20 > ---------------------------------------------------------------------- >=20 > Message: 1 > Date: Sat, 19 Feb 2011 12:01:37 +0000 > From: Matthew Seaman > Subject: Re: ZFS-only booting on FreeBSD > To: DStaal@usa.net > Cc: freebsd-questions@freebsd.org > Message-ID: <4D5FB121.6090102@infracaninophile.co.uk> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On 18/02/2011 15:59, Daniel Staal wrote: >>=20 >> I've been reading over the ZFS-only-boot instructions linked here: >> (and further linked from there) and have on= e >> worry: >>=20 >> Let's say I install a FreeBSD system using a ZFS-only filesystem into a >> box with hotswapable hard drives, configured with some redundancy. Time >> passes, one of the drives fails, and it is replaced and rebuilt using the= >> ZFS tools. (Possibly on auto, or possibly by just doing a 'zpool >> replace'.) >>=20 >> Is that box still bootable? (It's still running, but could it *boot*?) >=20 > Why wouldn't it be? The configuration in the Wiki article sets aside a > small freebsd-boot partition on each drive, and the instructions tell > you to install boot blocks as part of that partitioning process. You > would have to repeat those steps when you install your replacement drive > before you added the new disk into your zpool. >=20 > So long as the BIOS can read the bootcode from one or other drives, and > can then access /boot/zfs/zpool.cache to learn about what zpools you > have, then the system should boot. >=20 >> Extend further: If *all* the original drives are replaced (not at the sam= e >> time, obviously) and rebuilt/resilvered using the ZFS utilities, is the >> box still bootable? >=20 > Yes, this will still work. You can even replace all the drives > one-by-one with bigger ones, and it will still work and be bootable (and > give you more space without *requiring* the system be rebooted). >=20 >> If not, what's the minimum needed to support booting from another disk, >> and using the ZFS filesystem for everything else? >=20 > This situation is described in the Boot ZFS system from UFS article > here: http://wiki.freebsd.org/RootOnZFS/UFSBoot >=20 > I use this sort of setup for one system where the zpool has too many > drives in it for the BIOS to cope with; works very well booting from a > USB key. >=20 > In fact, while the partitioning layout described in the > http://wiki.freebsd.org/RootOnZFS articles is great for holding the OS > and making it bootable, for using ZFS to manage serious quantities of > disk storage, other strategies might be better. It would probably be a > good idea to have two zpools: one for the bulk of the space built from > whole disks (ie. without using gpart or similar partitioning), in > addition to your bootable zroot pool. Quite apart from wringing the > maximum usable space out of your available disks, this also makes it > much easier to replace failed disks or use hot spares. >=20 > Cheers, >=20 > Matthew >=20 > --=20 > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >=20 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 267 bytes > Desc: OpenPGP digital signature > Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/201= 10219/94f7cc99/signature-0001.pgp >=20 > ------------------------------ >=20 > Message: 2 > Date: Sat, 19 Feb 2011 12:08:39 +0000 > From: Matthew Seaman > Subject: Re: booting a kernel directly from stage 1/2 > To: Alexander Best > Cc: freebsd-questions@freebsd.org > Message-ID: <4D5FB2C7.7060200@infracaninophile.co.uk> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On 19/02/2011 02:47, Alexander Best wrote: >> but that won't work. i get some numbers and then it says: >> btx halted or something like that. >=20 > Can't you boot into fixit mode from installation media? That should > allow you to repair the boot blocks and make your system bootable again. >=20 > Cheers, >=20 > Matthew >=20 > --=20 > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >=20 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 267 bytes > Desc: OpenPGP digital signature > Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/201= 10219/bd69a12e/signature-0001.pgp >=20 > ------------------------------ >=20 > Message: 3 > Date: Sat, 19 Feb 2011 12:12:42 +0000 > From: Alexander Best > Subject: Re: booting a kernel directly from stage 1/2 > To: Matthew Seaman > Cc: freebsd-questions@freebsd.org > Message-ID: <20110219121242.GA55551@freebsd.org> > Content-Type: text/plain; charset=3Dus-ascii >=20 > On Sat Feb 19 11, Matthew Seaman wrote: >> On 19/02/2011 02:47, Alexander Best wrote: >>> but that won't work. i get some numbers and then it says: >>> btx halted or something like that. >>=20 >> Can't you boot into fixit mode from installation media? That should >> allow you to repair the boot blocks and make your system bootable again. >=20 > sorry if i wasn't clear enough. my system works perfectly normal. all i wa= nt > is to avoid running through the booting stage 3 (i.e. running /boot/loader= ), > because i want to speed up the boot time. >=20 > cheers. > alex >=20 >>=20 >> Cheers, >>=20 >> Matthew >>=20 >> --=20 >> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard >> Flat 3 >> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate >> JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >>=20 >=20 >=20 >=20 > --=20 > a13x >=20 >=20 > ------------------------------ >=20 > Message: 4 > Date: Sat, 19 Feb 2011 08:18:00 -0500 > From: Daniel Staal > Subject: Re: ZFS-only booting on FreeBSD > To: Matthew Seaman , > freebsd-questions@freebsd.org > Message-ID: > Content-Type: text/plain; charset=3Dus-ascii; format=3Dflowed >=20 > --As of February 19, 2011 12:01:37 PM +0000, Matthew Seaman is alleged to=20= > have said: >=20 >>> Let's say I install a FreeBSD system using a ZFS-only filesystem into a >>> box with hotswapable hard drives, configured with some redundancy. Time= >>> passes, one of the drives fails, and it is replaced and rebuilt using th= e >>> ZFS tools. (Possibly on auto, or possibly by just doing a 'zpool >>> replace'.) >>>=20 >>> Is that box still bootable? (It's still running, but could it *boot*?) >>=20 >> Why wouldn't it be? The configuration in the Wiki article sets aside a >> small freebsd-boot partition on each drive, and the instructions tell >> you to install boot blocks as part of that partitioning process. You >> would have to repeat those steps when you install your replacement drive >> before you added the new disk into your zpool. >>=20 >> So long as the BIOS can read the bootcode from one or other drives, and >> can then access /boot/zfs/zpool.cache to learn about what zpools you >> have, then the system should boot. >=20 > So, assuming a forgetful sysadmin (or someone who is new didn't know about= =20 > the setup in the first place) is that a yes or a no for the one-drive=20 > replaced case? >=20 > It definitely is a 'no' for the all-drives replaced case, as I suspected:=20= > You would need to have repeated the partitioning manually. (And not=20 > letting ZFS handle it.) >=20 >>> If not, what's the minimum needed to support booting from another disk, >>> and using the ZFS filesystem for everything else? >>=20 >> This situation is described in the Boot ZFS system from UFS article >> here: http://wiki.freebsd.org/RootOnZFS/UFSBoot >>=20 >> I use this sort of setup for one system where the zpool has too many >> drives in it for the BIOS to cope with; works very well booting from a >> USB key. >=20 > Thanks; I wasn't sure if that procedure would work if the bootloader was o= n=20 > a different physical disk than the rest of the filesystem. Nice to hear=20= > from someone who's tried it that it works. ;) >=20 >> In fact, while the partitioning layout described in the >> http://wiki.freebsd.org/RootOnZFS articles is great for holding the OS >> and making it bootable, for using ZFS to manage serious quantities of >> disk storage, other strategies might be better. It would probably be a >> good idea to have two zpools: one for the bulk of the space built from >> whole disks (ie. without using gpart or similar partitioning), in >> addition to your bootable zroot pool. Quite apart from wringing the >> maximum usable space out of your available disks, this also makes it >> much easier to replace failed disks or use hot spares. >=20 > If a single disk failure in the zpool can render the machine unbootable,=20= > it's better yet to have a dedicated bootloader drive: It increases the mea= n=20 > time between failures of your boot device (and therefore your machine), an= d=20 > it reduces the 'gotcha' value. In a hot-swap environment booting directly= =20 > off of ZFS you could fail a reboot a month (or more...) after the disk=20 > replacement, and finding your problem then will be a headache until someon= e=20 > remembers this setup tidbit. >=20 > If the 'fail to boot' only happens once *all* the original drives have bee= n=20 > replaced the mean time between failures is better in the ZFS situation, bu= t=20 > the 'gotcha' value becomes absolutely huge: Since you can replace one (or=20= > two, or more) disks without issue, the problem will likely take years to=20= > develop. >=20 > Ah well, price of the bleeding edge. ;) >=20 > Daniel T. Staal >=20 > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- >=20 >=20 > ------------------------------ >=20 > Message: 5 > Date: Sat, 19 Feb 2011 09:04:53 -0500 > From: David > Subject: Developing Embedded Network Device on FreeBSD > To: freebsd-questions@freebsd.org > Message-ID: <7E0B1096-3250-4B27-A541-61CA2E5F3F7B@gmail.com> > Content-Type: text/plain; charset=3Dus-ascii >=20 > Hello All: >=20 > I am new to FreeBSD development (I've done some work on NetBSD, but mostly= > on Linux). >=20 > I am developing a COTS-based network appliance. After doing my research, I= 've decided to > use FreeBSD as my development platform. I would like to get my development= environment > to the point where I can build a single ISO image that will contain OS and= application > ready to install. After reading through the handbook, porter's guide, and g= oogling, I think I have > a rough idea of how to do this, but I still have some gaps in how I set th= is up. >=20 > My current understanding is that all of the application specific, user lan= d software should=20 > reside in the ports tree. I have two questions with respect to this: >=20 > 1. If I don't want to publish my software, how do I manage the source (do I= just generate a tarball > on my build machine and place it in DISTDIR?). >=20 > 2. How do I integrate a ports-based application with a "make release" so t= hat I can have my > application binaries and dependancies included on the ISO ready for instal= lation? >=20 > I'd greatly appreciate any pointers. I'm really looking forward to develop= ing > under FreeBSD, but just need a few pointers to get me started. >=20 > Thanks! >=20 > David. >=20 >=20 >=20 >=20 > ------------------------------ >=20 > Message: 6 > Date: Sat, 19 Feb 2011 14:44:38 +0000 > From: Matthew Seaman > Subject: Re: ZFS-only booting on FreeBSD > To: Daniel Staal > Cc: freebsd-questions@freebsd.org > Message-ID: <4D5FD756.5020306@infracaninophile.co.uk> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On 19/02/2011 13:18, Daniel Staal wrote: >>> Why wouldn't it be? The configuration in the Wiki article sets aside a >>> small freebsd-boot partition on each drive, and the instructions tell >>> you to install boot blocks as part of that partitioning process. You >>> would have to repeat those steps when you install your replacement drive= >>> before you added the new disk into your zpool. >>>=20 >>> So long as the BIOS can read the bootcode from one or other drives, and >>> can then access /boot/zfs/zpool.cache to learn about what zpools you >>> have, then the system should boot. >>=20 >> So, assuming a forgetful sysadmin (or someone who is new didn't know >> about the setup in the first place) is that a yes or a no for the >> one-drive replaced case? >=20 > Umm... a sufficiently forgetful sysadmin can break *anything*. This > isn't really a fair test: forgetting to write the boot blocks onto a > disk could similarly render a UFS based system unbootable. That's why > scripting this sort of stuff is a really good idea. Any new sysadmin > should of course be referred to the copious and accurate documentation > detailing exactly the steps needed to replace a drive... >=20 > ZFS is definitely advantageous in this respect, because the sysadmin has > to do fewer steps to repair a failed drive, so there's less opportunity > for anything to be missed out or got wrong. >=20 > The best solution in this respect is one where you can simply unplug the > dead drive and plug in the replacement. You can do that with many > hardware RAID systems, but you're going to have to pay a premium price > for them. Also, you loose out on the general day-to-day benefits of > using ZFS. >=20 >> It definitely is a 'no' for the all-drives replaced case, as I >> suspected: You would need to have repeated the partitioning manually.=20 >> (And not letting ZFS handle it.) >=20 > Oh, assuming your sysadmins consistently fail to replace the drives > correctly, then depending on your BIOS you can be in deep do-do as far > as rebooting goes rather sooner than that. >=20 >> If a single disk failure in the zpool can render the machine >> unbootable, it's better yet to have a dedicated bootloader drive >=20 > If a single disk failure renders your system unbootable, then you're > doing it wrong. ZFS-root systems should certainly reboot if zfs can > still assemble the root pool -- so with one disk failed for RAIDZ1, or > two for RAIDZ2 or up to half the drives for mirror. >=20 > If this failure to correctly replace broken drives is going to be a > significant problem in your environment, then I guess you're going to > have to define appropriate processes. You might say that in the event > of a hard drive being replaced, it is mandatory to book some planned > downtime at the next convenient point, and do a test reboot + apply any > remedial work needed. If your system design is such that you can't take > any one machine down for maintenance, even with advance warning then > you've got more important problems to solve before you worry about using > ZFS or not. >=20 > Cheers, >=20 > Matthew >=20 > --=20 > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >=20 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 267 bytes > Desc: OpenPGP digital signature > Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/201= 10219/66a8256d/signature-0001.pgp >=20 > ------------------------------ >=20 > Message: 7 > Date: Sat, 19 Feb 2011 16:10:16 +0100 > From: Maciej Milewski > Subject: Re: Best Laptop to buy for Freebsd Without OS? > To: freebsd-questions@freebsd.org > Cc: Craig Butler > Message-ID: <201102191610.16919.milu@dat.pl> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On Saturday 19 of February 2011 06:12:52, Craig Butler wrote: >> Lenovo destroyed thinkpad in the t410i range; >> * stupid flimsy/flexi keyboard with massive delete and escape keys >> (why ???) > I don't liked it either so I stayed with R400. >> * gobi 2000 3g connectivity, cant get it working on anything none M$ > Have you tried gobi_loader and > http://old.nabble.com/-dev-ttyU0---block-at-open-td29876841.html > ? >=20 > As for the subject - my R400 is working fine and I have no problems with i= t.=20 > Opposite to when I had Lenovo 3000 series(poor performance,hot palm rest=20= > place, poor technical design: plastic cover too thin and too plastic. It m= ade=20 > my lcd with background artefact of the 5cm circle in the centre of the scr= een) > I think this line was transformed into the IdeaPad line > Earlier I had Acer's Travelmate 3012 where it has issues with acpi and ove= rall=20 > performance not to mention surprisingly hot keyboard. >=20 > - > Maciej >=20 >=20 > ------------------------------ >=20 > Message: 8 > Date: Sat, 19 Feb 2011 15:10:04 +0000 > From: Matthew Seaman > Subject: Re: Developing Embedded Network Device on FreeBSD > To: freebsd-questions@freebsd.org > Message-ID: <4D5FDD4C.5050503@infracaninophile.co.uk> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On 19/02/2011 14:04, David wrote: >> I am new to FreeBSD development (I've done some work on NetBSD, but mostl= y >> on Linux). >>=20 >> I am developing a COTS-based network appliance. After doing my research, I= 've decided to >> use FreeBSD as my development platform. I would like to get my developmen= t environment >> to the point where I can build a single ISO image that will contain OS an= d application >> ready to install. After reading through the handbook, porter's guide, and= googling, I think I have >> a rough idea of how to do this, but I still have some gaps in how I set t= his up. >=20 > Cool. There's pretty good support for building custom install media in > FreeBSD -- see release(7) for starters. >=20 >> My current understanding is that all of the application specific, user la= nd software should=20 >> reside in the ports tree. I have two questions with respect to this: >=20 > They don't *have* to reside in the ports -- it's just that the > advantages of using ports are such that you'ld need a really compelling > reason not to. >=20 > Also, "using the ports" and "using packages" come to pretty much the > same thing in the end. Ports are just a structure for building packages > -- and packages can be in two states: installed into your filesystem, or > collected together as a pkg tarball. >=20 >> 1. If I don't want to publish my software, how do I manage the source (do= I just generate a tarball >> on my build machine and place it in DISTDIR?). >=20 > You can create private ports that you can manage yourself and that > integrate with the regular ports tree pretty easily. In that case, you > should be able to build pre-compiled packages for your software which > you can include on your custom media. It's trickier if you need several > custom ports with dependencies between them, but still doable. >=20 > For a simple custom port, you can create a directory containing a port > Makefile, pkg-descr, pkg-plist etc. etc. anywhere in your filesystem. > Follow the Porter's Handbook for creating your port > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/) -- > the structure you need is identical to what you'ld write for a port > intended to be committed to the public ports tree. >=20 >> 2. How do I integrate a ports-based application with a "make release" so t= hat I can have my >> application binaries and dependancies included on the ISO ready for insta= llation? >=20 > This is a standard feature when building install media using 'make > release' -- you should even be able to set up a scripted sysinstall that > will do practically everything automatically, including installing your > custom packages. Or check out the new bsdinstall stuff going into > current right about now. >=20 >> I'd greatly appreciate any pointers. I'm really looking forward to develo= ping >> under FreeBSD, but just need a few pointers to get me started. >=20 > You'll find that FreeBSD documentation is rather more comprehensive than > is typical under Linux. Just about everything has a man page, and the > Handbook and various other online publications are generally rated as > excellent. Anything else, the FreeBSD mailing lists or forums can > usually be relied upon to provide answers about. There are specialised > lists for most interesting topics. >=20 > Cheers, >=20 > Matthew >=20 >=20 > --=20 > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >=20 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 267 bytes > Desc: OpenPGP digital signature > Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/201= 10219/b5bd5a51/signature-0001.pgp >=20 > ------------------------------ >=20 > Message: 9 > Date: Sat, 19 Feb 2011 16:04:19 +0100 > From: Harald Servat > Subject: 8.2-PRERELEASE? > To: freebsd-questions@freebsd.org > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > Hello list, >=20 > yesterday (Feb, 17th) I performed a cvsup (using csup, infact) of my > /usr/src tree using > *default release=3Dcvs tag=3DRELENG_8 > in my csup file (based on the csup > file /usr/share/examples/cvsup/stable-supfile). >=20 > According to [1], RELENG_8_2 and RELENG_8_2_0_RELEASE were created before= , > however, running uname ony machine after building world reports "FreeBSD > 8.2-PRERELEASE". I expect it not to show 8.2-PRERELEASE but something newe= r > (maybe 8.3-PRERELEASE?) Is uname reporting that I'm stick in some old bits= ? > If so, how can I move to the newer 8.x bits? If not, when does the version= > change? >=20 > Thank you! >=20 > [1] http://wiki.freebsd.org/Releng/8.2TODO > --=20 > _________________________________________________________________ > Fry: You can see how I lived before I met you. > Bender: You lived before you met me?! > Fry: Yeah, lots of people did. > Bender: Really?! >=20 >=20 > ------------------------------ >=20 > Message: 10 > Date: Sat, 19 Feb 2011 10:35:35 -0500 > From: Daniel Staal > Subject: Re: ZFS-only booting on FreeBSD > To: Matthew Seaman , > freebsd-questions@freebsd.org > Message-ID: > Content-Type: text/plain; charset=3Dus-ascii; format=3Dflowed >=20 > --As of February 19, 2011 2:44:38 PM +0000, Matthew Seaman is alleged to=20= > have said: >=20 >> Umm... a sufficiently forgetful sysadmin can break *anything*. This >> isn't really a fair test: forgetting to write the boot blocks onto a >> disk could similarly render a UFS based system unbootable. That's why >> scripting this sort of stuff is a really good idea. Any new sysadmin >> should of course be referred to the copious and accurate documentation >> detailing exactly the steps needed to replace a drive... >>=20 >> ZFS is definitely advantageous in this respect, because the sysadmin has >> to do fewer steps to repair a failed drive, so there's less opportunity >> for anything to be missed out or got wrong. >>=20 >> The best solution in this respect is one where you can simply unplug the >> dead drive and plug in the replacement. You can do that with many >> hardware RAID systems, but you're going to have to pay a premium price >> for them. Also, you loose out on the general day-to-day benefits of >> using ZFS. >=20 > --As for the rest, it is mine. >=20 > True, best case is hardware RAID for this specific problem. What I'm=20 > looking at here is basically reducing the surprise: A ZFS pool being used=20= > as the boot drive has the 'surprising' behavior that if you replace a driv= e=20 > using the instructions from the man pages or a naive Google search, you=20= > will have a drive that *appears* to work, until some point later where you= =20 > attempt to reboot your system. (At which point you will need to start=20 > over.) To avoid this you need to read local documentation and/or remember= =20 > that there is something beyond the man pages needs to be done. >=20 > With a normal UFS/etc. filesystem the standard failure recovery systems=20= > will point out that this is a boot drive, and handle as necessary. It wil= l=20 > either work or not, it will never *appear* to work, and then fail at some=20= > future point from a current error. It might be more steps to repair a=20 > specific drive, but all the steps are handled together. >=20 > Basically, if a ZFS boot drive fails, you are likely to get the following=20= > scenario: > 1) 'What do I need to do to replace a disk in the ZFS pool?' > 2) 'Oh, that's easy.' Replaces disk. > 3) System fails to boot at some later point. > 4) 'Oh, right, you need to do this *as well* on the *boot* pool...' >=20 > Where if a UFS boot drive fails on an otherwise ZFS system, you'll get: > 1) 'What's this drive?' > 2) 'Oh, so how do I set that up again?' > 3) Set up replacement boot drive. >=20 > The first situation hides that it's a special case, where the second one=20= > doesn't. >=20 > To avoid the first scenario you need to make sure your sysadmins are=20 > following *local* (and probably out-of-band) docs, and aware of potential=20= > problems. And awake. ;) The scenario in the second situation presents=20= > it's problem as a unified package, and you can rely on normal levels of=20= > alertness to be able to handle it correctly. (The sysadmin will realize i= t=20 > needs to be set up as a boot device because it's the boot device. ;) It=20= > may be complicated, but it's *obviously* complicated.) >=20 > I'm still not clear on whether a ZFS-only system will boot with a failed=20= > drive in the root ZFS pool. Once booted, of course a decent ZFS setup=20 > should be able to recover from the failed drive. But the question is if=20= > the FreeBSD boot process will handle the redundancy or not. At this point= =20 > I'm actually guessing it will, which of course only exasperates the above=20= > surprise problem: 'The easy ZFS disk replacement procedure *did* work in=20= > the past, why did it cause a problem now?' (And conceivably it could caus= e=20 > *major* data problems at that point, as ZFS will *grow* a pool quite=20 > easily, but *shrinking* one is a problem.) >=20 > Daniel T. Staal >=20 > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- >=20 >=20 > ------------------------------ >=20 > Message: 11 > Date: Sat, 19 Feb 2011 10:35:51 -0500 > From: David > Subject: Re: Developing Embedded Network Device on FreeBSD > To: Matthew Seaman > Cc: freebsd-questions@freebsd.org > Message-ID: <3DA6F44D-FABF-4E2A-9E32-B3D617C36B61@gmail.com> > Content-Type: text/plain; charset=3Dus-ascii >=20 > On Feb 19, 2011, at 10:10 AM, Matthew Seaman wrote: >=20 >> On 19/02/2011 14:04, David wrote: >>> [Snip] >>> I'd greatly appreciate any pointers. I'm really looking forward to devel= oping >>> under FreeBSD, but just need a few pointers to get me started. >>=20 >> You'll find that FreeBSD documentation is rather more comprehensive than >> is typical under Linux. Just about everything has a man page, and the >> Handbook and various other online publications are generally rated as >> excellent. Anything else, the FreeBSD mailing lists or forums can >> usually be relied upon to provide answers about. There are specialised >> lists for most interesting topics. >=20 > Thank you for the pointers Matt, that is very helpful. I am already enjoyi= ng > working with FreeBSD and looking forward to learning more about it as I pr= ogress. >=20 > Cheers, >=20 > David. >=20 >=20 >=20 > ------------------------------ >=20 > Message: 12 > Date: Sat, 19 Feb 2011 09:59:28 -0500 > From: David Lapsley > Subject: Re: Developing Embedded Network Device on FreeBSD > To: freebsd-questions@freebsd.org > Message-ID: <296734BA-B2D9-4987-A1F1-BE7CE7540C03@me.com> > Content-Type: text/plain; CHARSET=3DUS-ASCII >=20 > After a little more research ... >=20 > On Feb 19, 2011, at 9:04 AM, David wrote: >=20 >> Hello All: >>=20 >> I am new to FreeBSD development (I've done some work on NetBSD, but mostl= y >> on Linux). >>=20 >> I am developing a COTS-based network appliance. After doing my research, I= 've decided to >> use FreeBSD as my development platform. I would like to get my developmen= t environment >> to the point where I can build a single ISO image that will contain OS an= d application >> ready to install. After reading through the handbook, porter's guide, and= googling, I think I have >> a rough idea of how to do this, but I still have some gaps in how I set t= his up. >>=20 >> My current understanding is that all of the application specific, user la= nd software should=20 >> reside in the ports tree. I have two questions with respect to this: >>=20 >> 1. If I don't want to publish my software, how do I manage the source (do= I just generate a tarball >> on my build machine and place it in DISTDIR?). >=20 > After reading Chapter 11 of "Absolute FreeBSD, 2nd Edition" (very helpful!= ), it seems like > "make package" is my friend in this case. I've created a "packages" direct= ory in /usr/ports > so that my software and dependancies will be packaged and placed in this d= irectory. >=20 >> =46rom there, it seems like it should be fairly straightforward to have t= hese incorporated > into the ISO build. Then I can do OS install from the ISO build, followed b= y a pkg_add > (with appropriate environment variables set) to install the binary package= s. >=20 > This seems workable. I'm not sure if it is the Right way to do it. I'd app= reciate any > thoughts/comments on this. >=20 > Thanks, >=20 > David. >=20 >=20 >=20 > ------------------------------ >=20 > Message: 13 > Date: Sat, 19 Feb 2011 17:29:41 +0000 > From: krad > Subject: Re: ZFS-only booting on FreeBSD > To: Daniel Staal > Cc: freebsd-questions@freebsd.org > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > On 19 February 2011 15:35, Daniel Staal wrote: >> --As of February 19, 2011 2:44:38 PM +0000, Matthew Seaman is alleged to >> have said: >>=20 >>> Umm... a sufficiently forgetful sysadmin can break *anything*. This >>> isn't really a fair test: forgetting to write the boot blocks onto a >>> disk could similarly render a UFS based system unbootable. That's why >>> scripting this sort of stuff is a really good idea. Any new sysadmin >>> should of course be referred to the copious and accurate documentation >>> detailing exactly the steps needed to replace a drive... >>>=20 >>> ZFS is definitely advantageous in this respect, because the sysadmin has= >>> to do fewer steps to repair a failed drive, so there's less opportunity >>> for anything to be missed out or got wrong. >>>=20 >>> The best solution in this respect is one where you can simply unplug the= >>> dead drive and plug in the replacement. You can do that with many >>> hardware RAID systems, but you're going to have to pay a premium price >>> for them. Also, you loose out on the general day-to-day benefits of >>> using ZFS. >>=20 >> --As for the rest, it is mine. >>=20 >> True, best case is hardware RAID for this specific problem. What I'm >> looking at here is basically reducing the surprise: A ZFS pool being used= as >> the boot drive has the 'surprising' behavior that if you replace a drive >> using the instructions from the man pages or a naive Google search, you w= ill >> have a drive that *appears* to work, until some point later where you >> attempt to reboot your system. (At which point you will need to start >> over.) To avoid this you need to read local documentation and/or remembe= r >> that there is something beyond the man pages needs to be done. >>=20 >> With a normal UFS/etc. filesystem the standard failure recovery systems w= ill >> point out that this is a boot drive, and handle as necessary. It will >> either work or not, it will never *appear* to work, and then fail at some= >> future point from a current error. It might be more steps to repair a >> specific drive, but all the steps are handled together. >>=20 >> Basically, if a ZFS boot drive fails, you are likely to get the following= >> scenario: >> 1) 'What do I need to do to replace a disk in the ZFS pool?' >> 2) 'Oh, that's easy.' Replaces disk. >> 3) System fails to boot at some later point. >> 4) 'Oh, right, you need to do this *as well* on the *boot* pool...' >>=20 >> Where if a UFS boot drive fails on an otherwise ZFS system, you'll get: >> 1) 'What's this drive?' >> 2) 'Oh, so how do I set that up again?' >> 3) Set up replacement boot drive. >>=20 >> The first situation hides that it's a special case, where the second one >> doesn't. >>=20 >> To avoid the first scenario you need to make sure your sysadmins are >> following *local* (and probably out-of-band) docs, and aware of potential= >> problems. And awake. ;) The scenario in the second situation presents >> it's problem as a unified package, and you can rely on normal levels of >> alertness to be able to handle it correctly. (The sysadmin will realize i= t >> needs to be set up as a boot device because it's the boot device. ;) It= >> may be complicated, but it's *obviously* complicated.) >>=20 >> I'm still not clear on whether a ZFS-only system will boot with a failed >> drive in the root ZFS pool. Once booted, of course a decent ZFS setup >> should be able to recover from the failed drive. But the question is if t= he >> FreeBSD boot process will handle the redundancy or not. At this point I'= m >> actually guessing it will, which of course only exasperates the above >> surprise problem: 'The easy ZFS disk replacement procedure *did* work in t= he >> past, why did it cause a problem now?' (And conceivably it could cause >> *major* data problems at that point, as ZFS will *grow* a pool quite easi= ly, >> but *shrinking* one is a problem.) >>=20 >> Daniel T. Staal >>=20 >> --------------------------------------------------------------- >> This email copyright the author. Unless otherwise noted, you >> are expressly allowed to retransmit, quote, or otherwise use >> the contents for non-commercial purposes. This copyright will >> expire 5 year s after the author's death, or in 30 years, >> whichever is longer, unless such a period is in excess of >> local copyright law. >> --------------------------------------------------------------- >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" >>=20 >=20 > on slightly different note, make sure you align your partitions so the > zfs partitions 1st sector is divisible by 8, eg 1st sector 2048. Also > when you create the zpool, use the gnop -s 4096 trick to make sure the > pool has ashift=3D12. You may not be using advanced format drives yet, > but when you do in the future you will be glad you started out like > this. >=20 >=20 > ------------------------------ >=20 > Message: 14 > Date: Sat, 19 Feb 2011 13:11:59 -0500 > From: Andy Tornquist > Subject: Re: ZFS-only booting on FreeBSD > To: Daniel Staal , freebsd-questions@freebsd.org > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > P0r c qpppqppqpqapprfpprkkqroikiujpou >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > Q >=20 > R >=20 > F >=20 >=20 > Rf >=20 >=20 >=20 >=20 >=20 >=20 >=20 > On 2/18/11, Daniel Staal wrote: >>=20 >> I've been reading over the ZFS-only-boot instructions linked here: >> (and further linked from there) and have on= e >> worry: >>=20 >> Let's say I install a FreeBSD system using a ZFS-only filesystem into a >> box with hotswapable hard drives, configured with some redundancy. Time >> passes, one of the drives fails, and it is replaced and rebuilt using the= >> ZFS tools. (Possibly on auto, or possibly by just doing a 'zpool >> replace'.) >>=20 >> Is that box still bootable? (It's still running, but could it *boot*?) >>=20 >> Extend further: If *all* the original drives are replaced (not at the sam= e >> time, obviously) and rebuilt/resilvered using the ZFS utilities, is the >> box still bootable? >>=20 >> If not, what's the minimum needed to support booting from another disk, >> and using the ZFS filesystem for everything else? >>=20 >> Daniel T. Staal >>=20 >> --------------------------------------------------------------- >> This email copyright the author. Unless otherwise noted, you >> are expressly allowed to retransmit, quote, or otherwise use >> the contents for non-commercial purposes. This copyright will >> expire 5 years after the author's death, or in 30 years, >> whichever is longer, unless such a period is in excess of >> local copyright law. >> --------------------------------------------------------------- >>=20 >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" >>=20 >=20 > --=20 > Sent from my mobile device >=20 >=20 > ------------------------------ >=20 > Message: 15 > Date: Sat, 19 Feb 2011 20:06:46 +0100 > From: "Christopher J. Ruwe" > Subject: Re: Best Laptop to buy for Freebsd Without OS? > To: freebsd-questions@freebsd.org > Message-ID: <20110219200646.6a372e42@dijkstra> > Content-Type: text/plain; charset=3D"us-ascii" >=20 > I am typing on a Lenovo Thinkpad R500 running 8-stable, after (a very > high quality) instruction installation by Yamagi Burmeister > (http://www.bsdforen.de/showthread.php?s=3De2db5256b283497ca371738ad34b757= 2&t=3D24823). >=20 > I am very happy with both FreeBSD and my notebook since I switched > (unnerved) from Gentoo Linux to FreeBSD last year. > --=20 > Christopher J. Ruwe > TZ GMT + 1 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 834 bytes > Desc: not available > Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/201= 10219/3bb642cd/signature-0001.pgp >=20 > ------------------------------ >=20 > Message: 16 > Date: Sat, 19 Feb 2011 14:12:20 -0600 (CST) > From: Robert Bonomi > Subject: Re: ZFS-only booting on FreeBSD > To: freebsd-questions@freebsd.org > Message-ID: <201102192012.p1JKCKnP038248@mail.r-bonomi.com> >=20 >=20 >> Date: Sat, 19 Feb 2011 10:35:35 -0500 >> From: Daniel Staal >> Subject: Re: ZFS-only booting on FreeBSD >>=20 > [[.. sneck ..]] >>=20 >> Basically, if a ZFS boot drive fails, you are likely to get the following= =20 >> scenario: >> 1) 'What do I need to do to replace a disk in the ZFS pool?' >> 2) 'Oh, that's easy.' Replaces disk. >> 3) System fails to boot at some later point. >> 4) 'Oh, right, you need to do this *as well* on the *boot* pool...' >>=20 >> Where if a UFS boot drive fails on an otherwise ZFS system, you'll get: >> 1) 'What's this drive?' >> 2) 'Oh, so how do I set that up again?' >> 3) Set up replacement boot drive. >>=20 >> The first situation hides that it's a special case, where the second one=20= >> doesn't. >=20 > "For any foolproof system, there exists a _sufficiently-determined_ fool > capable of breaking it" applies. >=20 >> To avoid the first scenario you need to make sure your sysadmins are=20 >> following *local* (and probably out-of-band) docs, and aware of potential= =20 >> problems. And awake. ;) The scenario in the second situation presents=20= >> it's problem as a unified package, and you can rely on normal levels of=20= >> alertness to be able to handle it correctly. (The sysadmin will realize=20= >> it needs to be set up as a boot device because it's the boot device. ;) = =20 >> It may be complicated, but it's *obviously* complicated.) >>=20 >> I'm still not clear on whether a ZFS-only system will boot with a failed=20= >> drive in the root ZFS pool. Once booted, of course a decent ZFS setup=20= >> should be able to recover from the failed drive. But the question is if=20= >> the FreeBSD boot process will handle the redundancy or not. At this=20 >> point I'm actually guessing it will, which of course only exasperates the= =20 >> above surprise problem: 'The easy ZFS disk replacement procedure *did*=20= >> work in the past, why did it cause a problem now?' (And conceivably it=20= >> could cause *major* data problems at that point, as ZFS will *grow* a=20 >> pool quite easily, but *shrinking* one is a problem.) >=20 > A non-ZFS boot drive results in immediate, _guaranteed_, down-time for > replacement if/when it fails. >=20 > A ZFS boot drive lets you replace the drive and *schedule* the down-time > (for a 'test' re-boot, to make *sure* everything works) at a convenient > time. >=20 > Failure to schedule the required down time is a management failure, not > a methodology issue. One has located the requisite "sufficiently- > determined" fool, and the results thereof are to be expected. >=20 >=20 >=20 >=20 >=20 > ------------------------------ >=20 > Message: 17 > Date: Sat, 19 Feb 2011 12:57:02 -0800 > From: David Brodbeck > Subject: Re: Best Laptop to buy for Freebsd Without OS? > To: freebsd-questions@freebsd.org > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > On Fri, Feb 18, 2011 at 6:36 PM, Julian H. Stacey wrote:= >> Reality: >> XP purchased with a Toshiba laptop runs native, but fails on >> virtualbox, on the same laptop. I believe XP is crippled to only >> run on Toshiba, & vbox presents too clean/generic an environment ;-) >=20 > Sometimes there can be activation issues with OEM versions of Windows > XP. They're usually keyed to the manufacturer's BIOS. >=20 >=20 > ------------------------------ >=20 > Message: 18 > Date: Sat, 19 Feb 2011 21:33:26 +0100 > From: Andy Wodfer > Subject: How to forward old root mails to an external email address? > To: freebsd-questions > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > Hi all! >=20 > I'm running FreeBSD 8.0 Release on this particular server and I have a > rather large root mailbox under /var/mail/root. >=20 > I have set up an alias under /etc/aliases for new emails, but I need to > forward all the old emails in this mailbox to an external email address. >=20 > How can I do that? >=20 > Thanks for your help! > Andreas >=20 >=20 > ------------------------------ >=20 > Message: 19 > Date: Sat, 19 Feb 2011 16:24:43 -0500 > From: Daniel Staal > Subject: Re: How to forward old root mails to an external email > address? > To: Andy Wodfer , freebsd-questions > > Message-ID: <1837CB358903EB8C60F348FA@mac-pro.magehandbook.com> > Content-Type: text/plain; charset=3Dus-ascii; format=3Dflowed >=20 > --As of February 19, 2011 9:33:26 PM +0100, Andy Wodfer is alleged to have= =20 > said: >=20 >> 'm running FreeBSD 8.0 Release on this particular server and I have a >> rather large root mailbox under /var/mail/root. >>=20 >> I have set up an alias under /etc/aliases for new emails, but I need to >> forward all the old emails in this mailbox to an external email address. >>=20 >> How can I do that? >=20 > --As for the rest, it is mine. >=20 > Easiest way I know of is to set up a procmail rule to forward everything t= o=20 > the external address, then feed the old mailbox to procmail via formail. >=20 > =3D=3D=3D=3D=3D .procmailrc: > :0 > ! new@example.com >=20 > =3D=3D=3D=3D Command line: > cat /var/mail/root | formail -s procmail >=20 > Daniel T. Staal >=20 > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- >=20 >=20 > ------------------------------ >=20 > Message: 20 > Date: Sat, 19 Feb 2011 21:27:36 +0000 > From: Matthew Seaman > Subject: Re: ZFS-only booting on FreeBSD > To: Daniel Staal > Cc: freebsd-questions@freebsd.org > Message-ID: <4D6035C8.9040700@infracaninophile.co.uk> > Content-Type: text/plain; charset=3D"iso-8859-1" >=20 > On 19/02/2011 15:35, Daniel Staal wrote: >> I'm still not clear on whether a ZFS-only system will boot with a failed >> drive in the root ZFS pool. >=20 > If it's a mirror, raidz or similar pool type with resilience, then yes, > it certainly will boot with a failed drive. Been there, done that. >=20 > Cheers, >=20 > Matthew >=20 > --=20 > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW >=20 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 267 bytes > Desc: OpenPGP digital signature > Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/201= 10219/8a4da1cd/signature-0001.pgp >=20 > ------------------------------ >=20 > Message: 21 > Date: Sat, 19 Feb 2011 16:37:14 -0500 > From: Alfredo Perez > Subject: Re: BSD Magazine PDFs > To: Xn Nooby > Cc: freebsd-questions@freebsd.org > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > I am missing them all, can you upload them somewhere? >=20 > Thanks in advance >=20 > On Fri, Feb 18, 2011 at 1:48 PM, Xn Nooby wrote: >=20 >> Thanks for the replies, good to know I'm not missing any issues. >>=20 >>=20 >> On Fri, Feb 18, 2011 at 11:46 AM, Charlie Kester >> wrote: >>> On Fri 18 Feb 2011 at 08:13:19 PST MFV wrote: >>>>=20 >>>> Hello, >>>>=20 >>>> I've been downloading BSD Mag since it first came out and your list is >>>> identical to mine. >>>=20 >>> Same here. >>>=20 >>>=20 >>> _______________________________________________ >>> 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" >>>=20 >> _______________________________________________ >> 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" >>=20 >=20 >=20 > ------------------------------ >=20 > Message: 22 > Date: Sat, 19 Feb 2011 22:39:59 +0100 > From: Andy Wodfer > Subject: Re: How to forward old root mails to an external email > address? > To: freebsd-questions > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > On Sat, Feb 19, 2011 at 10:24 PM, Daniel Staal wrote: >=20 >> --As of February 19, 2011 9:33:26 PM +0100, Andy Wodfer is alleged to hav= e >> said: >>=20 >> 'm running FreeBSD 8.0 Release on this particular server and I have a >>> rather large root mailbox under /var/mail/root. >>>=20 >>> I have set up an alias under /etc/aliases for new emails, but I need to >>> forward all the old emails in this mailbox to an external email address.= >>>=20 >>> How can I do that? >>>=20 >>=20 >> --As for the rest, it is mine. >>=20 >> Easiest way I know of is to set up a procmail rule to forward everything t= o >> the external address, then feed the old mailbox to procmail via formail. >>=20 >> =3D=3D=3D=3D=3D .procmailrc: >> :0 >> ! new@example.com >>=20 >> =3D=3D=3D=3D Command line: >> cat /var/mail/root | formail -s procmail >>=20 >=20 > Hi Daniel and thanks for your reply! >=20 > I already tried something similare, but I keep getting command not found f= or > formail. I was hoping there was a way of doing this without installing > additional software - just use what comes with a default FreeBSD > installation. >=20 > Cheers, > Andreas >=20 >=20 > ------------------------------ >=20 > Message: 23 > Date: Sat, 19 Feb 2011 16:50:22 -0500 > From: Mike Jeays > Subject: Re: BSD Magazine PDFs > To: freebsd-questions@freebsd.org > Message-ID: <20110219165022.180026b5@napoleon> > Content-Type: text/plain; charset=3DUS-ASCII >=20 > On Sat, 19 Feb 2011 16:37:14 -0500 > Alfredo Perez wrote: >=20 >> I am missing them all, can you upload them somewhere? >>=20 >> Thanks in advance >>=20 >> On Fri, Feb 18, 2011 at 1:48 PM, Xn Nooby wrote: >>=20 >>> Thanks for the replies, good to know I'm not missing any issues. >>>=20 >>>=20 >>> On Fri, Feb 18, 2011 at 11:46 AM, Charlie Kester = >>> wrote: >>>> On Fri 18 Feb 2011 at 08:13:19 PST MFV wrote: >>>>>=20 >>>>> Hello, >>>>>=20 >>>>> I've been downloading BSD Mag since it first came out and your list is= >>>>> identical to mine. >>>>=20 >>>> Same here. >>>>=20 >>>>=20 >>>> _______________________________________________ >>>> 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" >>>>=20 >>> _______________________________________________ >>> 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" >>>=20 >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" >=20 > They are all online at bsdmag.org >=20 >=20 >=20 > ------------------------------ >=20 > Message: 24 > Date: Sat, 19 Feb 2011 16:52:43 -0500 > From: Daniel Staal > Subject: Re: ZFS-only booting on FreeBSD > To: Robert Bonomi , > freebsd-questions@freebsd.org > Message-ID: > Content-Type: text/plain; charset=3Dus-ascii; format=3Dflowed >=20 > --As of February 19, 2011 2:12:20 PM -0600, Robert Bonomi is alleged to=20= > have said: >=20 >> A non-ZFS boot drive results in immediate, _guaranteed_, down-time for >> replacement if/when it fails. >>=20 >> A ZFS boot drive lets you replace the drive and *schedule* the down-time >> (for a 'test' re-boot, to make *sure* everything works) at a convenient >> time. >=20 > --As for the rest, it is mine. >=20 > No it doesn't. It only extends the next scheduled downtime until you deal= =20 > with it. ;) (Or, in a hot-swap environment with sufficient monitoring,=20= > means you need to deal with it before the next scheduled downtime.) >=20 > Or, from what it sounds like, you could have a redundant/backup boot disk.= =20 > I'm planning on using a $5 USB drive as my boot disk. Triple redundancy=20= > would cost $15. I paid more for lunch today. (Hmm. I'll have to test to= =20 > see if that setup works, although given the rest of this discussion I don'= t=20 > see why it shouldn't...) >=20 > I see the advantage, and that it offers higher levels of resiliency and if= =20 > properly handled should cause no problems. I just hate relying on humans=20= > to remember things and follow directions. That's what computers are for.=20= > Repairing a failed disk in a ZFS boot pool requires a human to remember to= =20 > look for directions in an unusual place, and then follow them correctly.=20= > If they don't, nothing happens immediately, but there is the possibility o= f=20 > failure at some later unspecified time. (Meanwhile if they look for=20 > directions in the *usual* place, they get a simple and straightforward set= =20 > of instructions that will appear to work.) >=20 > *If* that failure occurs, that downtime will be longer than the downtime=20= > you would save from a dozen boxes being handled using the correct ZFS=20 > procedure, as everyone tears their hair out going 'Why doesn't it work?!?=20= > It worked just fine a moment ago!' until someone remembers this quirk. >=20 > I don't like quirky computers. That's why I'm not a Windows admin. ;) >=20 > Daniel T. Staal >=20 > --------------------------------------------------------------- > This email copyright the author. Unless otherwise noted, you > are expressly allowed to retransmit, quote, or otherwise use > the contents for non-commercial purposes. This copyright will > expire 5 years after the author's death, or in 30 years, > whichever is longer, unless such a period is in excess of > local copyright law. > --------------------------------------------------------------- >=20 >=20 > ------------------------------ >=20 > Message: 25 > Date: Sat, 19 Feb 2011 14:00:10 -0800 > From: David Brodbeck > Subject: Re: ZFS-only booting on FreeBSD > To: FreeBSD Questions > Message-ID: > > Content-Type: text/plain; charset=3DISO-8859-1 >=20 > On Sat, Feb 19, 2011 at 1:52 PM, Daniel Staal wrote: >> I see the advantage, and that it offers higher levels of resiliency and i= f >> properly handled should cause no problems. I just hate relying on humans= to >> remember things and follow directions. That's what computers are for. >> Repairing a failed disk in a ZFS boot pool requires a human to remember t= o >> look for directions in an unusual place, and then follow them correctly. >=20 > That's why I generally prefer to boot off hardware RAID 1 in > situations where reliability is critical. There are too many fiddly > unknown factors in booting off software RAID. Even if you do > everything else right, the BIOS may refuse to look beyond the failed > drive and boot off the good one. I save the software RAID for data > spindles (which I tend to keep separate from the boot/OS spindles, > anyway.) >=20 > 2-port 3ware cards are relatively inexpensive, and well supported by > every OS I've used except Solaris. If you're going for RAID 1 you > don't need expensive battery-backed cache. >=20 >=20 > ------------------------------ >=20 > Message: 26 > Date: Sat, 19 Feb 2011 14:12:02 -0800 > From: Yuri > Subject: Can motorola v195 be supported as network interface? > To: freebsd-questions@freebsd.org > Message-ID: <4D604032.1070206@rawbw.com> > Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed >=20 > I have this phone, 'usbconfig -d ugen1.2 dump_device_desc' shows it like=20= > this: >=20 > ugen1.2: at usbus1, cfg=3D0 md=3DHOS= T=20 > spd=3DFULL (12Mbps) pwr=3DON >=20 > bLength =3D 0x0012 > bDescriptorType =3D 0x0001 > bcdUSB =3D 0x0110 > bDeviceClass =3D 0x0002 > bDeviceSubClass =3D 0x0000 > bDeviceProtocol =3D 0x0000 > bMaxPacketSize0 =3D 0x0008 > idVendor =3D 0x22b8 > idProduct =3D 0x4902 > bcdDevice =3D 0x0001 > iManufacturer =3D 0x0001 > iProduct =3D 0x0002 > iSerialNumber =3D 0x0000 > bNumConfigurations =3D 0x0002 >=20 > It doesn't show up as a network interface, only as ugen. > What would it take to support it? How hard can it be to make it show up=20= > as network interface? > MacOS for example sees it as a PPP modem asking for user name/password. >=20 > Yuri >=20 >=20 > ------------------------------ >=20 > Message: 27 > Date: Sat, 19 Feb 2011 22:14:42 +0000 > From: RW > Subject: Re: How to forward old root mails to an external email > address? > To: freebsd-questions@freebsd.org > Message-ID: <20110219221442.39aacc81@gumby.homeunix.com> > Content-Type: text/plain; charset=3DUS-ASCII >=20 > On Sat, 19 Feb 2011 22:39:59 +0100 > Andy Wodfer wrote: >=20 >> I already tried something similare, but I keep getting command not >> found for formail. I was hoping there was a way of doing this without >> installing additional software - just use what comes with a default >> FreeBSD installation. >=20 > formail is installed as part of the procmail package. Check for typos > and that PATH is set correctly.=20 >=20 >=20 > ------------------------------ >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.or= g" >=20 > End of freebsd-questions Digest, Vol 350, Issue 10 > **************************************************