From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 07:30:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2FEAE256; Sun, 6 Oct 2013 07:30:51 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-ee0-x236.google.com (mail-ee0-x236.google.com [IPv6:2a00:1450:4013:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 46B442C09; Sun, 6 Oct 2013 07:30:50 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id e53so2611084eek.13 for ; Sun, 06 Oct 2013 00:30:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=aEAivdcImJx+yXZI5NuiWTYkGe49ecX2SIFKvkhmty4=; b=WTTPkWUGjjMcV/bRX+SexY5dQnvUyNu9KLmpcu9rMwlLyv1kv97pWT1OLOOKpOdTn4 QPTY14AsZt8qAXxVvWshXTTQtJ2Gyn5rd/HXhwUKjup6CKx9GqtA+/18QCAI5iNs5Ky+ q/kiOiqIwauSh6osx3JUc4J9LJKaVsa/LoTZhGhJNCnRKLDn/TYmnDYL+yz8/XRlNSXR FktfHaKSiaRKpV/UT7teb3HA7lYhgQ6dMXjHwLFPvIVUIDp2BX344a1irStjc/udZomn OaiagxOFiZyoO8vJOnHU9KOguY26lf2soDNBuj0SYZ+Mylm6O70Z2TN2SBe81iQ3jDMG X9VA== X-Received: by 10.15.43.13 with SMTP id w13mr37255953eev.37.1381044647533; Sun, 06 Oct 2013 00:30:47 -0700 (PDT) Received: from mavbook.mavhome.dp.ua ([46.211.77.102]) by mx.google.com with ESMTPSA id v8sm48252297eeo.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 06 Oct 2013 00:30:45 -0700 (PDT) Sender: Alexander Motin Message-ID: <525111A2.1020106@FreeBSD.org> Date: Sun, 06 Oct 2013 10:30:42 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130616 Thunderbird/17.0.6 MIME-Version: 1.0 To: John Baldwin Subject: Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking References: <5224511D.4090503@FreeBSD.org> <20130906230236.GI43281@caravan.chchile.org> <522AC88D.4070005@FreeBSD.org> <201310021330.23251.jhb@freebsd.org> In-Reply-To: <201310021330.23251.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-geom@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 07:30:51 -0000 On 02.10.2013 20:30, John Baldwin wrote: > On Saturday, September 07, 2013 2:32:45 am Alexander Motin wrote: >> On 07.09.2013 02:02, Jeremie Le Hen wrote: >>> On Fri, Sep 06, 2013 at 11:29:11AM +0300, Alexander Motin wrote: >>>> On 06.09.2013 11:06, Jeremie Le Hen wrote: >>>>> On Fri, Sep 06, 2013 at 12:46:27AM +0200, Olivier Cochard-Labbé wrote: >>>>>> On Thu, Sep 5, 2013 at 11:38 PM, Alexander Motin > wrote: >>>>>>> I've found and fixed possible double request completion, that could > cause >>>>>>> such symptoms if happened. Updated patch located as usual: >>>>>>> http://people.freebsd.org/~mav/camlock_patches/camlock_20130905.patch >>>>>>> >>>>> With this new one I cannot boot any more (I also updated the source >>>>> tree). This is a hand transcripted version: >>>>> >>>>> Trying to mount root from zfs:zroot/root []... >>>>> panic: Batch flag already set >>>>> cpuid = 1 >>>>> KDB: stack backtrace: >>>>> db_trace_self_wrapper() >>>>> kdb_backtrace() >>>>> vpanic() >>>>> kassert_panic() >>>>> xpt_batch_start() >>>>> ata_interrupt() >>>>> softclock_call_cc() >>>>> softclock() >>>>> ithread_loop() >>>>> fork_exit() >>>>> fork_trampoline() >>>> >>>> Thank you for the report. I see my fault. It is probably specific to >>>> ata(4) driver only. I've workarounded that in new patch version, but >>>> probably that area needs some rethinking. >>>> >>>> http://people.freebsd.org/~mav/camlock_patches/camlock_20130906.patch >>> >>> I'm not sure you needed a confirmation, but it boots. Thanks :). >>> >>> I didn't quite understand the thread; is direct dispatch enabled for >>> amd64? ISTR you said only i386 but someone else posted the macro for >>> amd64. >> >> Yes, it is enabled for amd64. I've said x86, meaning both i386 and amd64. > > FYI, I tested mfi with this patch set and mfid worked fine for handling g_up > directly: > > Index: dev/mfi/mfi_disk.c > =================================================================== > --- dev/mfi/mfi_disk.c (revision 257407) > +++ dev/mfi/mfi_disk.c (working copy) > @@ -162,6 +162,7 @@ > sc->ld_disk->d_unit = sc->ld_unit; > sc->ld_disk->d_sectorsize = secsize; > sc->ld_disk->d_mediasize = sectors * secsize; > + sc->ld_disk->d_flags = DISKFLAG_DIRECT_COMPLETION; > if (sc->ld_disk->d_mediasize >= (1 * 1024 * 1024)) { > sc->ld_disk->d_fwheads = 255; > sc->ld_disk->d_fwsectors = 63; > Thank you for the feedback. But looking on mfi driver sources I would say that it calls biodone() from mfi_disk_complete() from cm_complete() method, which is called while holding mfi_io_lock mutex. I guess that if on top of mfi device would be some GEOM class, supporting direct dispatch and sending new requests down on previous request completion (or retrying requests), that could cause recursive mfi_io_lock acquisition. That is exactly the cause why I've added this flag. May be it is a bit paranoid, but it is better to be safe then sorry. Another good reason to drop the lock before calling biodone() would be reducing the lock hold time. Otherwise it may just increase lock congestion there and destroy all benefits of the direct dispatch. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 13:44:52 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A4A3F271 for ; Sun, 6 Oct 2013 13:44:52 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 26F8F2AA4 for ; Sun, 6 Oct 2013 13:44:51 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBE2C9.dip0.t-ipconnect.de [217.251.226.201]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r96DihjL082189 for ; Sun, 6 Oct 2013 13:44:43 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r96DiRMd026177 for ; Sun, 6 Oct 2013 15:44:27 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r96DiLnN059117 for ; Sun, 6 Oct 2013 15:44:27 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310061344.r96DiLnN059117@fire.js.berklix.net> To: current@freebsd.org Subject: lock order reversals on 10.0-ALPHA4 From: "Julian H. Stacey" Organization: http://berklix.com BSD Linux Unix Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com/~jhs/cv/ Date: Sun, 06 Oct 2013 15:44:21 +0200 Sender: jhs@berklix.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 13:44:52 -0000 With: FreeBSD lapr.js.berklix.net 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #0 r255933: Sun Sep 29 02:50:54 UTC 2013 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 At boot dmesg shows several lock order reversals, eg ------ Trying to mount root from ufs:/dev/ad4s2a [rw]... ipfw2 (+ipv6) initialized, divert loadable, nat loadable, default to deny, logging disabled lock order reversal: 1st 0xfffffe00a6e26b48 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3059 2nd 0xfffff80005cf8400 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00c8f3d3f0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00c8f3d4a0 witness_checkorder() at witness_checkorder+0xd23/frame 0xfffffe00c8f3d530 _sx_xlock() at _sx_xlock+0x75/frame 0xfffffe00c8f3d570 ufsdirhash_add() at ufsdirhash_add+0x3b/frame 0xfffffe00c8f3d5b0 ufs_direnter() at ufs_direnter+0x688/frame 0xfffffe00c8f3d670 ufs_makeinode() at ufs_makeinode+0x573/frame 0xfffffe00c8f3d830 ufs_symlink() at ufs_symlink+0x32/frame 0xfffffe00c8f3d880 VOP_SYMLINK_APV() at VOP_SYMLINK_APV+0xf0/frame 0xfffffe00c8f3d8b0 kern_symlinkat() at kern_symlinkat+0x23e/frame 0xfffffe00c8f3dae0 amd64_syscall() at amd64_syscall+0x265/frame 0xfffffe00c8f3dbf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00c8f3dbf0 --- syscall (57, FreeBSD ELF64, sys_symlink), rip = 0x800888ffa, rsp = 0x7fffffffca58, rbp = 0x7fffffffdc10 --- lock order reversal: 1st 0xfffff800881b9d50 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:851 2nd 0xfffff800881b99a0 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2099 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00c8ed93d0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00c8ed9480 witness_checkorder() at witness_checkorder+0xd23/frame 0xfffffe00c8ed9510 __lockmgr_args() at __lockmgr_args+0x6f2/frame 0xfffffe00c8ed9640 vop_stdlock() at vop_stdlock+0x3c/frame 0xfffffe00c8ed9660 VOP_LOCK1_APV() at VOP_LOCK1_APV+0xf5/frame 0xfffffe00c8ed9690 _vn_lock() at _vn_lock+0xab/frame 0xfffffe00c8ed9700 vget() at vget+0x70/frame 0xfffffe00c8ed9750 devfs_allocv() at devfs_allocv+0xfd/frame 0xfffffe00c8ed97a0 devfs_root() at devfs_root+0x43/frame 0xfffffe00c8ed97d0 vfs_donmount() at vfs_donmount+0x115e/frame 0xfffffe00c8ed9aa0 sys_nmount() at sys_nmount+0x72/frame 0xfffffe00c8ed9ae0 amd64_syscall() at amd64_syscall+0x265/frame 0xfffffe00c8ed9bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00c8ed9bf0 --- syscall (378, FreeBSD ELF64, sys_nmount), rip = 0x800a9dd7a, rsp = 0x7fffffffccb8, rbp = 0x7fffffffd220 --- ---- It comes up multi user OK, Do you already have enough lock order reversal to work on, or do you want me to run diagnostics ? what ? Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 15:22:09 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7350BAD1; Sun, 6 Oct 2013 15:22:09 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F0DAC2FBA; Sun, 6 Oct 2013 15:22:08 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBFF7C.dip0.t-ipconnect.de [93.203.255.124]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r96FM6q9084916; Sun, 6 Oct 2013 15:22:06 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r96FLscY026762; Sun, 6 Oct 2013 17:21:55 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r96FLmxw077281; Sun, 6 Oct 2013 17:21:54 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310061521.r96FLmxw077281@fire.js.berklix.net> Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Thu, 03 Oct 2013 23:28:43 +0200." <201310032128.r93LShdV030701@fire.js.berklix.net> Date: Sun, 06 Oct 2013 17:21:48 +0200 Sender: jhs@berklix.com Cc: Rui Paulo , current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 15:22:09 -0000 I wrote Thu, 03 Oct 2013 23:28:43 +0200 > Rui Paulo wrote: > > > > On 2 Oct 2013, at 16:57, Julian H. Stacey wrote: > > > > > Hi current@, > > > It seems I need if_urtwn driver for a really miniature WLAN USB stick, > > > & if_urtwn is only in current ? > > > man 4 if_urtwn refers to ports/net/urtwn-firmware-kmod which is missing ? > > > > > > This driver was never merged to FreeBSD 9. > > OK, Thanks for confirmation. > > > > Can you use FreeBSD 10 instead? > > Yes, easier than building from 9.X I guess (& helps test alpha :-). > I'll fetch from local mirror, per > http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044951.html > > > > The port reference in the man page is wrong. The firmware is now shipped as part of the base system. > > Oh nice, easier :-) I'm happy to report with 10.0-ALPHA4 /boot/loader.conf if_urtwn_load="YES" `ifconfig wlan0 scan` works OK. Thanks :-) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 15:22:29 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 91E30CB9 for ; Sun, 6 Oct 2013 15:22:29 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 53C0B2FCA for ; Sun, 6 Oct 2013 15:22:29 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id x12so4075919qcv.22 for ; Sun, 06 Oct 2013 08:22:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=u1DJ9OLMUNhSPTKXdHuxHwCLleeAFtRYcPNYORBVN0o=; b=VMgacoi0zTI0As/w7Ef3NW1gsjiF64AJ+/JZ7tiQZaUpdfnNDzSsyuKs1G7+qBlqMO CBqwuUmXxy/RsQeoj6ijFHUKB0PtO+TSNPJyEQUcGdofaXwa0obwhCh8kAmkICQw/EQR KcKOtj3Tgbz2D9gb3OXHkzb7Olm6ObZSK2TKB1UvZzZRKPzmUH8Jx9cZZRg1BB4l6mwH 6wXBsaqcrWx4X8iaPOQWWyzveYlEGs9M3GhX04ci2GvcRmCuS1qJ9wWTUFXDwimkbVew drsVzCNGP8itcxQddbXK+X4kOKs0EKSvTgmHALD7Kisl88cbkAjEhw0RI8mSH6g7Qbnw tbGQ== MIME-Version: 1.0 X-Received: by 10.224.8.10 with SMTP id f10mr31611773qaf.29.1381072947978; Sun, 06 Oct 2013 08:22:27 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.229.225.129 with HTTP; Sun, 6 Oct 2013 08:22:27 -0700 (PDT) In-Reply-To: <201310061344.r96DiLnN059117@fire.js.berklix.net> References: <201310061344.r96DiLnN059117@fire.js.berklix.net> Date: Sun, 6 Oct 2013 08:22:27 -0700 X-Google-Sender-Auth: PMESMKChRqabFFxaMMzHB9LNIRI Message-ID: Subject: Re: lock order reversals on 10.0-ALPHA4 From: Matthew Fleming To: "Julian H. Stacey" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "current@freebsd.org Current" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 15:22:29 -0000 On Sun, Oct 6, 2013 at 6:44 AM, Julian H. Stacey wrote: > With: > FreeBSD lapr.js.berklix.net 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #0 > r255933: Sun Sep 29 02:50:54 UTC 2013 > root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > At boot dmesg shows several lock order reversals, eg > > ------ > Trying to mount root from ufs:/dev/ad4s2a [rw]... > ipfw2 (+ipv6) initialized, divert loadable, nat loadable, default to deny, > logging disabled > lock order reversal: > 1st 0xfffffe00a6e26b48 bufwait (bufwait) @ > /usr/src/sys/kern/vfs_bio.c:3059 > 2nd 0xfffff80005cf8400 dirhash (dirhash) @ > /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00c8f3d3f0 > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00c8f3d4a0 > witness_checkorder() at witness_checkorder+0xd23/frame 0xfffffe00c8f3d530 > _sx_xlock() at _sx_xlock+0x75/frame 0xfffffe00c8f3d570 > ufsdirhash_add() at ufsdirhash_add+0x3b/frame 0xfffffe00c8f3d5b0 > ufs_direnter() at ufs_direnter+0x688/frame 0xfffffe00c8f3d670 > ufs_makeinode() at ufs_makeinode+0x573/frame 0xfffffe00c8f3d830 > ufs_symlink() at ufs_symlink+0x32/frame 0xfffffe00c8f3d880 > VOP_SYMLINK_APV() at VOP_SYMLINK_APV+0xf0/frame 0xfffffe00c8f3d8b0 > kern_symlinkat() at kern_symlinkat+0x23e/frame 0xfffffe00c8f3dae0 > amd64_syscall() at amd64_syscall+0x265/frame 0xfffffe00c8f3dbf0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00c8f3dbf0 > --- syscall (57, FreeBSD ELF64, sys_symlink), rip = 0x800888ffa, rsp = > 0x7fffffffca58, rbp = 0x7fffffffdc10 --- > lock order reversal: > 1st 0xfffff800881b9d50 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:851 > 2nd 0xfffff800881b99a0 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2099 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00c8ed93d0 > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00c8ed9480 > witness_checkorder() at witness_checkorder+0xd23/frame 0xfffffe00c8ed9510 > __lockmgr_args() at __lockmgr_args+0x6f2/frame 0xfffffe00c8ed9640 > vop_stdlock() at vop_stdlock+0x3c/frame 0xfffffe00c8ed9660 > VOP_LOCK1_APV() at VOP_LOCK1_APV+0xf5/frame 0xfffffe00c8ed9690 > _vn_lock() at _vn_lock+0xab/frame 0xfffffe00c8ed9700 > vget() at vget+0x70/frame 0xfffffe00c8ed9750 > devfs_allocv() at devfs_allocv+0xfd/frame 0xfffffe00c8ed97a0 > devfs_root() at devfs_root+0x43/frame 0xfffffe00c8ed97d0 > vfs_donmount() at vfs_donmount+0x115e/frame 0xfffffe00c8ed9aa0 > sys_nmount() at sys_nmount+0x72/frame 0xfffffe00c8ed9ae0 > amd64_syscall() at amd64_syscall+0x265/frame 0xfffffe00c8ed9bf0 > Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00c8ed9bf0 > --- syscall (378, FreeBSD ELF64, sys_nmount), rip = 0x800a9dd7a, rsp = > 0x7fffffffccb8, rbp = 0x7fffffffd220 --- > ---- > > Those two LORs are well-known and at least the fist is definitely a false positive. They're rather tricky to fix; there's been previous discussion. The first one is #261 at http://sources.zabbadoz.net/freebsd/lor.html . The second one is probably #280. Cheers, matthew From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 17:24:11 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F090CDC6 for ; Sun, 6 Oct 2013 17:24:11 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id DE8E02584 for ; Sun, 6 Oct 2013 17:24:11 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 7432C1A3C1A for ; Sun, 6 Oct 2013 10:24:11 -0700 (PDT) Message-ID: <52519CB9.8040203@mu.org> Date: Sun, 06 Oct 2013 10:24:09 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter References: <201310061521.r96FLmxw077281@fire.js.berklix.net> In-Reply-To: <201310061521.r96FLmxw077281@fire.js.berklix.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 17:24:12 -0000 On 10/6/13 8:21 AM, Julian H. Stacey wrote: > I wrote Thu, 03 Oct 2013 23:28:43 +0200 >> Rui Paulo wrote: >>> On 2 Oct 2013, at 16:57, Julian H. Stacey wrote: >>> >>>> Hi current@, >>>> It seems I need if_urtwn driver for a really miniature WLAN USB stick, >>>> & if_urtwn is only in current ? >>>> man 4 if_urtwn refers to ports/net/urtwn-firmware-kmod which is missing ? >>> >>> This driver was never merged to FreeBSD 9. >> OK, Thanks for confirmation. >> >> >>> Can you use FreeBSD 10 instead? >> Yes, easier than building from 9.X I guess (& helps test alpha :-). >> I'll fetch from local mirror, per >> http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044951.html >> >> >>> The port reference in the man page is wrong. The firmware is now shipped as part of the base system. >> Oh nice, easier :-) > I'm happy to report with 10.0-ALPHA4 /boot/loader.conf if_urtwn_load="YES" > `ifconfig wlan0 scan` works OK. Thanks :-) > > Cheers, > Julian Cool! I have a g4 tibook 12in with an if_bwn that doesn't really work at all. I got one of these (if_urtwn) and it works enough to download about a meg or so before the watchdog kicks in and I have to ifconfig down/up it to get it to respond again. I even have a patch pending to add the usb identifier for this. Is there someone I can provide debug information for to help resolve this? -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 19:05:34 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D6DAA377; Sun, 6 Oct 2013 19:05:34 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 69CC72A4D; Sun, 6 Oct 2013 19:05:31 +0000 (UTC) Received: from alph.d.allbsd.org (p4181-ipbf1307funabasi.chiba.ocn.ne.jp [123.225.173.181]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r96J59Qt010650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 04:05:20 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.7/8.14.5) with ESMTP id r96J56pe079701; Mon, 7 Oct 2013 04:05:07 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Mon, 07 Oct 2013 04:04:11 +0900 (JST) Message-Id: <20131007.040411.272534607754482379.hrs@allbsd.org> To: current@FreeBSD.org Subject: CFT: rc.d/jail rewrite (was: jail configuration) From: Hiroki Sato X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D In-Reply-To: <8638oerh39.fsf@nine.des.no> X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart0(Mon_Oct__7_04_04_11_2013_176)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Mon, 07 Oct 2013 04:05:21 +0900 (JST) X-Spam-Status: No, score=-94.9 required=13.0 tests=CONTENT_TYPE_PRESENT, FAKEDWORD_BACKQUOTE,MIMEQENC,ONLY1HOPDIRECT,QENCPTR2,RCVD_IN_RP_RNBL, SAMEHELOBY2HOP,SPF_SOFTFAIL,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: arch@FreeBSD.org, dteske@FreeBSD.org, jamie@FreeBSD.org, slw@zxy.spb.ru X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: current@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 19:05:34 -0000 ----Security_Multipart0(Mon_Oct__7_04_04_11_2013_176)-- Content-Type: Multipart/Mixed; boundary="--Next_Part(Mon_Oct__7_04_04_11_2013_092)--" Content-Transfer-Encoding: 7bit ----Next_Part(Mon_Oct__7_04_04_11_2013_092)-- Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable [Please reply to freebsd-current@] Hi, Can anyone who are using jail_* variables in rc.conf test the attached patch? On freebsd-arch@ there is a discussion about deprecating jail__* variables in favor of jail.conf. This rewrite is one to support the both in a backward compatible way. I want to make sure if this does not break the existing configurations. The following is the entry in UPDATING: +20131007: + The rc.d/jail script has been updated to support jail(8) + configuration file. The "jail__*" rc.conf(5) variables + for per-jail configuration are automatically converted to + /var/run/jail..conf before the jail(8) utility is invoke= d. + This is transparently backward compatible. See the below about= some + incompatibilities. + + These variables are now deprecated in favor of jail(8) configur= ation + file. One can use "rc.d/jail config " command to genera= te + a jail(8) configuration file in /var/run/jail..conf with= out + running the jail(8) utility. The default pathname of the + configuration file is /etc/jail.conf and can be specified by + using $jail_conf or $jail__conf variables. + + Please note that jail_fdesc_enable and jail_procfs_enable are + not supported, and jail_devfs_ruleset accepts an integer at + this moment. Please consider to use exec.fstab for the + additional mount and rewrite the ruleset name with an integer. Dag-Erling Sm=F8rgrav wrote in <8638oerh39.fsf@nine.des.no>: de> I didn't look at the patch very closely, but I see that you print a= de> warning when you generate a configuration for an old-style jail whi= le de> jail.conf exists. I think you should *always* print that warning f= or de> every old-style jail so people will be reminded to convert. We sho= uld de> also remove the examples from /etc/defaults/rc.conf and replace the= de> documentation for jail_${_j}_* in rc.conf(5) with a short paragraph= that de> says they are for compatibility only. Thank you for your feedback. The warning message is always displayed in "rc.d/jail start", and rc.conf(5) and defaults/rc.conf are updated in this patch. -- Hiroki ----Next_Part(Mon_Oct__7_04_04_11_2013_092)-- Content-Type: Text/X-Patch; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="jail_20131007-1.diff" Index: UPDATING =================================================================== --- UPDATING (revision 256090) +++ UPDATING (working copy) @@ -31,6 +31,26 @@ disable the most expensive debugging functionality run "ln -s 'abort:false,junk:false' /etc/malloc.conf".) +20131007: + The rc.d/jail script has been updated to support jail(8) + configuration file. The "jail__*" rc.conf(5) variables + for per-jail configuration are automatically converted to + /var/run/jail..conf before the jail(8) utility is invoked. + This is transparently backward compatible. See the below about some + incompatibilities. + + These variables are now deprecated in favor of jail(8) configuration + file. One can use "rc.d/jail config " command to generate + a jail(8) configuration file in /var/run/jail..conf without + running the jail(8) utility. The default pathname of the + configuration file is /etc/jail.conf and can be specified by + using $jail_conf or $jail__conf variables. + + Please note that jail_fdesc_enable and jail_procfs_enable are + not supported, and jail_devfs_ruleset accepts an integer at + this moment. Please consider to use exec.fstab for the + additional mount and rewrite the ruleset name with an integer. + 20130930: BIND has been removed from the base system. If all you need is a local resolver, simply enable and start the local_unbound Index: etc/rc.d/jail =================================================================== --- etc/rc.d/jail (revision 256090) +++ etc/rc.d/jail (working copy) @@ -8,81 +8,138 @@ # BEFORE: securelevel # KEYWORD: nojail shutdown -# WARNING: This script deals with untrusted data (the data and -# processes inside the jails) and care must be taken when changing the -# code related to this! If you have any doubt whether a change is -# correct and have security impact, please get the patch reviewed by -# the FreeBSD Security Team prior to commit. - . /etc/rc.subr name="jail" rcvar="jail_enable" -start_precmd="jail_prestart" start_cmd="jail_start" +start_postcmd="jail_warn" stop_cmd="jail_stop" +config_cmd="jail_config" +console_cmd="jail_console" +status_cmd="jail_status" +extra_commands="config console status" +: ${jail_conf:=/etc/jail.conf} +: ${jail_program:=/usr/sbin/jail} +: ${jail_consolecmd:=/bin/sh} +: ${jail_jexec:=/usr/sbin/jexec} +: ${jail_jls:=/usr/sbin/jls} -# init_variables _j -# Initialize the various jail variables for jail _j. +need_dad_wait= + +# extact_var jail name param num defval +# Extract value from ${jail_$jail_$name} or ${jail_$name} and +# set it to $param. If not defined, $defval is used. +# When $num is [0-9]*, ${jail_$jail_$name$num} are looked up and +# $param is set by using +=. +# When $num is YN or NY, the value is interpret as boolean. +extract_var() +{ + local i _j _name _param _num _def _name1 _name2 + _j=$1 + _name=$2 + _param=$3 + _num=$4 + _def=$5 + + case $_num in + YN) + _name1=jail_${_j}_${_name} + _name2=jail_${_name} + eval $_name1=\"\${$_name1:-\${$_name2:-$_def}}\" + if checkyesno $_name1; then + echo " $_param = 1;" + else + echo " $_param = 0;" + fi + ;; + NY) + _name1=jail_${_j}_${_name} + _name2=jail_${_name} + eval $_name1=\"\${$_name1:-\${$_name2:-$_def}}\" + if checkyesno $_name1; then + echo " $_param = 0;" + else + echo " $_param = 1;" + fi + ;; + [0-9]*) + i=$_num + while : ; do + _name1=jail_${_j}_${_name}${i} + _name2=jail_${_name}${i} + eval _tmpargs=\"\${$_name1:-\${$_name2:-$_def}}\" + if [ -n "$_tmpargs" ]; then + echo " $_param += \"$_tmpargs\";" + else + break; + fi + i=$(($i + 1)) + done + ;; + *) + _name1=jail_${_j}_${_name} + _name2=jail_${_name} + eval _tmpargs=\"\${$_name1:-\${$_name2:-$_def}}\" + if [ -n "$_tmpargs" ]; then + echo " $_param = \"$_tmpargs\";" + fi + ;; + esac +} + +# parse_options _j +# Parse options and create a temporary configuration file if necessary. # -init_variables() +parse_options() { - _j="$1" + local _j + _j=$1 + _confwarn=0 if [ -z "$_j" ]; then - warn "init_variables: you must specify a jail" + warn "parse_options: you must specify a jail" return fi - + eval _jconf=\"\${jail_${_j}_conf:-/etc/jail.${_j}.conf}\" eval _rootdir=\"\$jail_${_j}_rootdir\" - _devdir="${_rootdir}/dev" - _fdescdir="${_devdir}/fd" - _procdir="${_rootdir}/proc" eval _hostname=\"\$jail_${_j}_hostname\" + if [ -z "$_rootdir" -o \ + -z "$_hostname" ]; then + if [ -r "$_jconf" ]; then + _conf="$_jconf" + return 0 + elif [ -r "$jail_conf" ]; then + _conf="$jail_conf" + return 0 + else + warn "Invalid configuration for $_j " \ + "(no jail.conf, no hostname, or no path). " \ + "Jail $_j was ignored." + fi + return 1 + fi eval _ip=\"\$jail_${_j}_ip\" - eval _interface=\"\${jail_${_j}_interface:-${jail_interface}}\" + if [ -z "$_ip" ] && ! check_kern_features vimage; then + warn "no ipaddress specified and no vimage support. " \ + "Jail $_j was ignored." + return 1 + fi + _conf=/var/run/jail.${_j}.conf + # + # To relieve confusion, show a warning message. + # + _confwarn=1 + if [ -r "$jail_conf" -o -r "$_jconf" ]; then + warn "$_conf is created and used for jail $_j." + fi + /usr/bin/install -m 0644 -o root -g wheel /dev/null $_conf || return 1 + + eval : \${jail_${_j}_flags:=${jail_flags}} eval _exec=\"\$jail_${_j}_exec\" - - i=0 - while : ; do - eval _exec_prestart${i}=\"\${jail_${_j}_exec_prestart${i}:-\${jail_exec_prestart${i}}}\" - [ -z "$(eval echo \"\$_exec_prestart${i}\")" ] && break - i=$((i + 1)) - done - - eval _exec_start=\"\${jail_${_j}_exec_start:-${jail_exec_start}}\" - - i=1 - while : ; do - eval _exec_afterstart${i}=\"\${jail_${_j}_exec_afterstart${i}:-\${jail_exec_afterstart${i}}}\" - [ -z "$(eval echo \"\$_exec_afterstart${i}\")" ] && break - i=$((i + 1)) - done - - i=0 - while : ; do - eval _exec_poststart${i}=\"\${jail_${_j}_exec_poststart${i}:-\${jail_exec_poststart${i}}}\" - [ -z "$(eval echo \"\$_exec_poststart${i}\")" ] && break - i=$((i + 1)) - done - - i=0 - while : ; do - eval _exec_prestop${i}=\"\${jail_${_j}_exec_prestop${i}:-\${jail_exec_prestop${i}}}\" - [ -z "$(eval echo \"\$_exec_prestop${i}\")" ] && break - i=$((i + 1)) - done - - eval _exec_stop=\"\${jail_${_j}_exec_stop:-${jail_exec_stop}}\" - - i=0 - while : ; do - eval _exec_poststop${i}=\"\${jail_${_j}_exec_poststop${i}:-\${jail_exec_poststop${i}}}\" - [ -z "$(eval echo \"\$_exec_poststop${i}\")" ] && break - i=$((i + 1)) - done - + eval _exec_start=\"\$jail_${_j}_exec_start\" + eval _exec_stop=\"\$jail_${_j}_exec_stop\" if [ -n "${_exec}" ]; then # simple/backward-compatible execution _exec_start="${_exec}" @@ -96,285 +153,96 @@ fi fi fi - - # The default jail ruleset will be used by rc.subr if none is specified. - eval _ruleset=\"\${jail_${_j}_devfs_ruleset:-${jail_devfs_ruleset}}\" - eval _devfs=\"\${jail_${_j}_devfs_enable:-${jail_devfs_enable}}\" - [ -z "${_devfs}" ] && _devfs="NO" - eval _fdescfs=\"\${jail_${_j}_fdescfs_enable:-${jail_fdescfs_enable}}\" - [ -z "${_fdescfs}" ] && _fdescfs="NO" - eval _procfs=\"\${jail_${_j}_procfs_enable:-${jail_procfs_enable}}\" - [ -z "${_procfs}" ] && _procfs="NO" - - eval _mount=\"\${jail_${_j}_mount_enable:-${jail_mount_enable}}\" - [ -z "${_mount}" ] && _mount="NO" - # "/etc/fstab.${_j}" will be used for {,u}mount(8) if none is specified. - eval _fstab=\"\${jail_${_j}_fstab:-${jail_fstab}}\" - [ -z "${_fstab}" ] && _fstab="/etc/fstab.${_j}" - eval _flags=\"\${jail_${_j}_flags:-${jail_flags}}\" - [ -z "${_flags}" ] && _flags="-l -U root" - eval _consolelog=\"\${jail_${_j}_consolelog:-${jail_consolelog}}\" - [ -z "${_consolelog}" ] && _consolelog="/var/log/jail_${_j}_console.log" + eval _interface=\"\${jail_${_j}_interface:-${jail_interface}}\" eval _parameters=\"\${jail_${_j}_parameters:-${jail_parameters}}\" - [ -z "${_parameters}" ] && _parameters="" - eval _fib=\"\${jail_${_j}_fib:-${jail_fib}}\" + eval _fstab=\"\${jail_${_j}_fstab:-${jail_fstab:-/etc/fstab.$_j}}\" + ( + date +"# Generated by rc.d/jail at %Y-%m-%d %H:%M:%S" + echo "$_j {" + extract_var $_j hostname host.hostname - "" + extract_var $_j rootdir path - "" + if [ -n "$_ip" ]; then + extract_var $_j interface interface - "" + jail_handle_ips_option $_ip $_interface + alias=0 + while : ; do + eval _x=\"\$jail_${_jail}_ip_multi${alias}\" + [ -z "$_x" ] && break - # Debugging aid - # - debug "$_j devfs enable: $_devfs" - debug "$_j fdescfs enable: $_fdescfs" - debug "$_j procfs enable: $_procfs" - debug "$_j mount enable: $_mount" - debug "$_j hostname: $_hostname" - debug "$_j ip: $_ip" - jail_show_addresses ${_j} - debug "$_j interface: $_interface" - debug "$_j fib: $_fib" - debug "$_j root: $_rootdir" - debug "$_j devdir: $_devdir" - debug "$_j fdescdir: $_fdescdir" - debug "$_j procdir: $_procdir" - debug "$_j ruleset: $_ruleset" - debug "$_j fstab: $_fstab" - - i=0 - while : ; do - eval out=\"\${_exec_prestart${i}:-''}\" - if [ -z "$out" ]; then - break + jail_handle_ips_option $_x $_interface + alias=$(($alias + 1)) + done + case $need_dad_wait in + 1) + # Sleep to let DAD complete before + # starting services. + echo " exec.start += \"sleep " \ + $(($(${SYSCTL_N} net.inet6.ip6.dad_count) + 1)) \ + "\";" + ;; + esac + # These are applicable only to non-vimage jails. + extract_var $_j fib exec.fib - "" + extract_var $_j socket_unixiproute_only \ + allow.raw_sockets NY YES + else + echo " vnet;" + extract_var $_j vnet_interface vnet.interface - "" fi - debug "$_j exec pre-start #${i}: ${out}" - i=$((i + 1)) - done - debug "$_j exec start: $_exec_start" + echo " exec.clean;" + echo " exec.system_user = \"root\";" + echo " exec.jail_user = \"root\";" + extract_var $_j exec_prestart exec.prestart 0 "" + extract_var $_j exec_poststart exec.poststart 0 "" + extract_var $_j exec_prestop exec.prestop 0 "" + extract_var $_j exec_poststop exec.poststop 0 "" - i=1 - while : ; do - eval out=\"\${_exec_afterstart${i}:-''}\" + echo " exec.start += \"$_exec_start\";" + extract_var $_j exec_afterstart exec.start 1 "" + echo " exec.stop = \"$_exec_stop\";" - if [ -z "$out" ]; then - break; - fi + extract_var $_j consolelog exec.consolelog - \ + /var/log/jail_${_j}_console.log - debug "$_j exec after start #${i}: ${out}" - i=$((i + 1)) - done - - i=0 - while : ; do - eval out=\"\${_exec_poststart${i}:-''}\" - if [ -z "$out" ]; then - break + eval : \${jail_${_j}_devfs_enable:=${jail_devfs_enable:-NO}} + if checkyesno jail_${_j}_devfs_enable; then + echo " mount.devfs;" + case $_ruleset in + "") ;; + [0-9]*) echo " devfs_ruleset = \"$_ruleset\";" ;; + devfsrules_jail) + # XXX: This is the default value, + # Let jail(8) to use the default because + # mount(8) only accepts an integer. + # This should accept a ruleset name. + ;; + *) warn "devfs_ruleset must be integer." ;; + esac + if [ -r $_fstab ]; then + echo " mount.fstab = \"$_fstab\";" + fi fi - debug "$_j exec post-start #${i}: ${out}" - i=$((i + 1)) - done - i=0 - while : ; do - eval out=\"\${_exec_prestop${i}:-''}\" - if [ -z "$out" ]; then - break - fi - debug "$_j exec pre-stop #${i}: ${out}" - i=$((i + 1)) - done + # XXX: fdescfs and procfs should be added for + # backward compatibility. - debug "$_j exec stop: $_exec_stop" + echo " ${_parameters};" - i=0 - while : ; do - eval out=\"\${_exec_poststop${i}:-''}\" - if [ -z "$out" ]; then - break + eval : \${jail_${_j}_mount_enable:=${jail_mount_enable:-NO}} + if checkyesno jail_${_j}_mount_enable; then + echo " allow.mount;" >> $_conf fi - debug "$_j exec post-stop #${i}: ${out}" - i=$((i + 1)) - done - debug "$_j flags: $_flags" - debug "$_j consolelog: $_consolelog" - debug "$_j parameters: $_parameters" + extract_var $_j set_hostname_allow allow.set_hostname YN NO + extract_var $_j sysvipc_allow allow.sysvipc YN NO + echo "}" + ) >> $_conf - if [ -z "${_hostname}" ]; then - err 3 "$name: No hostname has been defined for ${_j}" - fi - if [ -z "${_rootdir}" ]; then - err 3 "$name: No root directory has been defined for ${_j}" - fi + return 0 } -# set_sysctl rc_knob mib msg -# If the mib sysctl is set according to what rc_knob -# specifies, this function does nothing. However if -# rc_knob is set differently than mib, then the mib -# is set accordingly and msg is displayed followed by -# an '=" sign and the word 'YES' or 'NO'. -# -set_sysctl() -{ - _knob="$1" - _mib="$2" - _msg="$3" - - _current=`${SYSCTL} -n $_mib 2>/dev/null` - if checkyesno $_knob ; then - if [ "$_current" -ne 1 ]; then - echo -n " ${_msg}=YES" - ${SYSCTL} 1>/dev/null ${_mib}=1 - fi - else - if [ "$_current" -ne 0 ]; then - echo -n " ${_msg}=NO" - ${SYSCTL} 1>/dev/null ${_mib}=0 - fi - fi -} - -# is_current_mountpoint() -# Is the directory mount point for a currently mounted file -# system? -# -is_current_mountpoint() -{ - local _dir _dir2 - - _dir=$1 - - _dir=`echo $_dir | sed -Ee 's#//+#/#g' -e 's#/$##'` - [ ! -d "${_dir}" ] && return 1 - _dir2=`df ${_dir} | tail +2 | awk '{ print $6 }'` - [ "${_dir}" = "${_dir2}" ] - return $? -} - -# is_symlinked_mountpoint() -# Is a mount point, or any of its parent directories, a symlink? -# -is_symlinked_mountpoint() -{ - local _dir - - _dir=$1 - - [ -L "$_dir" ] && return 0 - [ "$_dir" = "/" ] && return 1 - is_symlinked_mountpoint `dirname $_dir` - return $? -} - -# secure_umount -# Try to unmount a mount point without being vulnerable to -# symlink attacks. -# -secure_umount() -{ - local _dir - - _dir=$1 - - if is_current_mountpoint ${_dir}; then - umount -f ${_dir} >/dev/null 2>&1 - else - debug "Nothing mounted on ${_dir} - not unmounting" - fi -} - - -# jail_umount_fs -# This function unmounts certain special filesystems in the -# currently selected jail. The caller must call the init_variables() -# routine before calling this one. -# -jail_umount_fs() -{ - local _device _mountpt _rest - - if checkyesno _fdescfs; then - if [ -d "${_fdescdir}" ] ; then - secure_umount ${_fdescdir} - fi - fi - if checkyesno _devfs; then - if [ -d "${_devdir}" ] ; then - secure_umount ${_devdir} - fi - fi - if checkyesno _procfs; then - if [ -d "${_procdir}" ] ; then - secure_umount ${_procdir} - fi - fi - if checkyesno _mount; then - [ -f "${_fstab}" ] || warn "${_fstab} does not exist" - tail -r ${_fstab} | while read _device _mountpt _rest; do - case ":${_device}" in - :#* | :) - continue - ;; - esac - secure_umount ${_mountpt} - done - fi -} - -# jail_mount_fstab() -# Mount file systems from a per jail fstab while trying to -# secure against symlink attacks at the mount points. -# -# If we are certain we cannot secure against symlink attacks we -# do not mount all of the file systems (since we cannot just not -# mount the file system with the problematic mount point). -# -# The caller must call the init_variables() routine before -# calling this one. -# -jail_mount_fstab() -{ - local _device _mountpt _rest - - while read _device _mountpt _rest; do - case ":${_device}" in - :#* | :) - continue - ;; - esac - if is_symlinked_mountpoint ${_mountpt}; then - warn "${_mountpt} has symlink as parent - not mounting from ${_fstab}" - return - fi - done <${_fstab} - mount -a -F "${_fstab}" -} - -# jail_show_addresses jail -# Debug print the input for the given _multi aliases -# for a jail for init_variables(). -# -jail_show_addresses() -{ - local _j _type alias - _j="$1" - alias=0 - - if [ -z "${_j}" ]; then - warn "jail_show_addresses: you must specify a jail" - return - fi - - while : ; do - eval _addr=\"\$jail_${_j}_ip_multi${alias}\" - if [ -n "${_addr}" ]; then - debug "${_j} ip_multi${alias}: $_addr" - alias=$((${alias} + 1)) - else - break - fi - done -} - -# jail_extract_address argument +# jail_extract_address argument iface # The second argument is the string from one of the _ip # or the _multi variables. In case of a comma separated list # only one argument must be passed in at a time. @@ -382,8 +250,9 @@ # jail_extract_address() { - local _i + local _i _interface _i=$1 + _interface=$2 if [ -z "${_i}" ]; then warn "jail_extract_address: called without input" @@ -439,12 +308,12 @@ _mask=${_mask:-/32} elif [ "${_type}" = "inet6" ]; then - # In case _maske is not set for IPv6, use /128. - _mask=${_mask:-/128} + # In case _maske is not set for IPv6, use /64. + _mask=${_mask:-/64} fi } -# jail_handle_ips_option {add,del} input +# jail_handle_ips_option input iface # Handle a single argument imput which can be a comma separated # list of addresses (theoretically with an option interface and # prefix/netmask/prefixlen). @@ -451,9 +320,9 @@ # jail_handle_ips_option() { - local _x _action _type _i - _action=$1 - _x=$2 + local _x _type _i _iface + _x=$1 + _iface=$2 if [ -z "${_x}" ]; then # No IP given. This can happen for the primary address @@ -468,294 +337,146 @@ *,*) # Extract the first argument and strip it off the list. _i=`expr "${_x}" : '^\([^,]*\)'` _x=`expr "${_x}" : "^[^,]*,\(.*\)"` - ;; + ;; *) _i=${_x} _x="" - ;; + ;; esac _type="" - _iface="" _addr="" _mask="" - jail_extract_address "${_i}" + jail_extract_address $_i $_iface # make sure we got an address. - case "${_addr}" in + case $_addr in "") continue ;; *) ;; esac # Append address to list of addresses for the jail command. - case "${_type}" in + case $_type in inet) - case "${_addrl}" in - "") _addrl="${_addr}" ;; - *) _addrl="${_addrl},${_addr}" ;; - esac - ;; + echo " ip4.addr += \"${_addr}${_mask}\";" + ;; inet6) - case "${_addr6l}" in - "") _addr6l="${_addr}" ;; - *) _addr6l="${_addr6l},${_addr}" ;; - esac - ;; + echo " ip6.addr += \"${_addr}${_mask}\";" + need_dad_wait=1 + ;; esac - - # Configure interface alias if requested by a given interface - # and if we could correctly parse everything. - case "${_iface}" in - "") continue ;; - esac - case "${_type}" in - inet) ;; - inet6) ipv6_address_count=$((ipv6_address_count + 1)) ;; - *) warn "Could not determine address family. Not going" \ - "to ${_action} address '${_addr}' for ${_jail}." - continue - ;; - esac - case "${_action}" in - add) ifconfig ${_iface} ${_type} ${_addr}${_mask} alias - ;; - del) # When removing the IP, ignore the _mask. - ifconfig ${_iface} ${_type} ${_addr} -alias - ;; - esac done } -# jail_ips {add,del} -# Extract the comma separated list of addresses and return them -# for the jail command. -# Handle more than one address via the _multi option as well. -# If an interface is given also add/remove an alias for the -# address with an optional netmask. -# -jail_ips() +jail_config() { - local _action - _action=$1 - - case "${_action}" in - add) ;; - del) ;; - *) warn "jail_ips: invalid action '${_action}'" - return - ;; + case $1 in + _ALL) return ;; esac + for _jail in $@; do + if parse_options $_jail; then + echo "$_jail: parameters are in $_conf." + fi + done +} - # Handle addresses. - ipv6_address_count=0 - jail_handle_ips_option ${_action} "${_ip}" - # Handle jail_xxx_ip_multi - alias=0 - while : ; do - eval _x=\"\$jail_${_jail}_ip_multi${alias}\" - case "${_x}" in - "") break ;; - *) jail_handle_ips_option ${_action} "${_x}" - alias=$((${alias} + 1)) - ;; - esac - done - case ${ipv6_address_count} in - 0) ;; - *) # Sleep 1 second to let DAD complete before starting services. - sleep 1 - ;; +jail_console() +{ + # One argument that is not _ALL. + case $#:$1 in + 1:_ALL) err 3 "Specify a jail name." ;; + 1:*) ;; + *) err 3 "Specify a jail name." ;; esac + eval _cmd=\${jail_$1_consolecmd:-$jail_consolecmd} + $jail_jexec $1 $_cmd } -jail_prestart() +jail_status() { - if checkyesno jail_parallel_start; then - command_args='&' - fi + + $jail_jls -N } jail_start() { - echo -n 'Configuring jails:' - set_sysctl jail_set_hostname_allow security.jail.set_hostname_allowed \ - set_hostname_allow - set_sysctl jail_socket_unixiproute_only \ - security.jail.socket_unixiproute_only unixiproute_only - set_sysctl jail_sysvipc_allow security.jail.sysvipc_allowed \ - sysvipc_allow - echo '.' + if [ $# = 0 ]; then + return + fi + echo -n 'Starting jails:' + case $1 in + _ALL) + echo -n ' ' + command=$jail_program + rc_flags=$jail_flags + command_args="-f $jail_conf -c" + $command $rc_flags $command_args "*" + echo '.' + return + ;; + esac + _tmp=`mktemp -t jail` || exit 3 + for _jail in $@; do + parse_options $_jail || continue - echo -n 'Starting jails:' - _tmp_dir=`mktemp -d /tmp/jail.XXXXXXXX` || \ - err 3 "$name: Can't create temp dir, exiting..." - for _jail in ${jail_list} - do - init_variables $_jail - if [ -f /var/run/jail_${_jail}.id ]; then - echo -n " [${_hostname} already running (/var/run/jail_${_jail}.id exists)]" - continue; - fi - _addrl="" - _addr6l="" - jail_ips "add" - if [ -n "${_fib}" ]; then - _setfib="setfib -F '${_fib}'" + eval rc_flags=\${jail_${_j}_flags:-$jail_flags} + eval command=\${jail_${_j}_program:-$jail_program} + if checkyesno jail_parallel_start; then + command_args="-i -f $_conf -c $_jail &" else - _setfib="" + command_args="-i -f $_conf -c $_jail" fi - if checkyesno _mount; then - info "Mounting fstab for jail ${_jail} (${_fstab})" - if [ ! -f "${_fstab}" ]; then - err 3 "$name: ${_fstab} does not exist" - fi - jail_mount_fstab - fi - if checkyesno _devfs; then - # If devfs is already mounted here, skip it. - df -t devfs "${_devdir}" >/dev/null - if [ $? -ne 0 ]; then - if is_symlinked_mountpoint ${_devdir}; then - warn "${_devdir} has symlink as parent - not starting jail ${_jail}" - continue - fi - info "Mounting devfs on ${_devdir}" - devfs_mount_jail "${_devdir}" ${_ruleset} - # Transitional symlink for old binaries - if [ ! -L "${_devdir}/log" ]; then - ln -sf ../var/run/log "${_devdir}/log" - fi - fi - - # XXX - It seems symlinks don't work when there - # is a devfs(5) device of the same name. - # Jail console output - # __pwd="`pwd`" - # cd "${_devdir}" - # ln -sf ../var/log/console console - # cd "$__pwd" - fi - if checkyesno _fdescfs; then - if is_symlinked_mountpoint ${_fdescdir}; then - warn "${_fdescdir} has symlink as parent, not mounting" - else - info "Mounting fdescfs on ${_fdescdir}" - mount -t fdescfs fdesc "${_fdescdir}" - fi - fi - if checkyesno _procfs; then - if is_symlinked_mountpoint ${_procdir}; then - warn "${_procdir} has symlink as parent, not mounting" - else - info "Mounting procfs onto ${_procdir}" - if [ -d "${_procdir}" ] ; then - mount -t procfs proc "${_procdir}" - fi - fi - fi - _tmp_jail=${_tmp_dir}/jail.$$ - - i=0 - while : ; do - eval out=\"\${_exec_prestart${i}:-''}\" - [ -z "$out" ] && break - ${out} - i=$((i + 1)) - done - - eval ${_setfib} jail -n ${_jail} ${_flags} -i -c path=${_rootdir} host.hostname=${_hostname} \ - ${_addrl:+ip4.addr=\"${_addrl}\"} ${_addr6l:+ip6.addr=\"${_addr6l}\"} \ - ${_parameters} command=${_exec_start} > ${_tmp_jail} 2>&1 \ - ${_consolelog} - echo ${_jail_id} > /var/run/jail_${_jail}.id - - i=0 - while : ; do - eval out=\"\${_exec_poststart${i}:-''}\" - [ -z "$out" ] && break - ${out} - i=$((i + 1)) - done + if $command $rc_flags $command_args \ + >> $_tmp 2>&1 > ${_consolelog} 2>&1 - fi - killall -j ${_jail_id} -TERM > /dev/null 2>&1 - sleep 1 - killall -j ${_jail_id} -KILL > /dev/null 2>&1 - jail_umount_fs - echo -n " $_hostname" - - i=0 - while : ; do - eval out=\"\${_exec_poststop${i}:-''}\" - [ -z "$out" ] && break - ${out} - i=$((i + 1)) - done - fi - jail_ips "del" - rm /var/run/jail_${_jail}.id - else - echo " cannot stop jail ${_jail}. No jail id in /var/run" + case $1 in + _ALL) + echo -n ' ' + command=$jail_program + rc_flags=$jail_flags + command_args="-f $jail_conf -r" + $command $rc_flags $command_args "*" + echo '.' + return + ;; + esac + for _jail in $@; do + parse_options $_jail || continue + eval command=\${jail_${_j}_program:-$jail_program} + if $command -q -f $_conf -r $_jail; then + echo -n " ${_hostname:-${_jail}}" fi done echo '.' } +jail_warn() +{ + + # To relieve confusion, show a warning message. + case $_confwarn in + 1) warn "Per-jail configuration via jail_* variables " \ + "is obsolete. Please consider to migrate to $jail_conf." + ;; + esac +} + load_rc_config $name -cmd="$1" -if [ $# -gt 0 ]; then - shift -fi -if [ -n "$*" ]; then - jail_list="$*" -fi - -run_rc_command "${cmd}" +case $# in +1) run_rc_command $@ ${jail_list:-_ALL} ;; +*) run_rc_command $@ ;; +esac Index: etc/rc.subr =================================================================== --- etc/rc.subr (revision 256090) +++ etc/rc.subr (working copy) @@ -1463,28 +1463,6 @@ return 0 } -# devfs_mount_jail dir [ruleset] -# Mounts a devfs file system appropriate for jails -# on the directory dir. If ruleset is specified, the ruleset -# it names will be used instead. If present, ruleset must -# be the name of a ruleset as defined in a devfs.rules(5) file. -# This function returns non-zero if an error occurs. -# -devfs_mount_jail() -{ - local jdev rs _me - jdev="$1" - [ -n "$2" ] && rs=$2 || rs="devfsrules_jail" - _me="devfs_mount_jail" - - devfs_init_rulesets - if ! devfs_domount "$jdev" $rs; then - warn "$_me: devfs was not mounted on $jdev" - return 1 - fi - return 0 -} - # Provide a function for normalizing the mounting of memory # filesystems. This should allow the rest of the code here to remain # as close as possible between 5-current and 4-stable. Index: etc/defaults/rc.conf =================================================================== --- etc/defaults/rc.conf (revision 256090) +++ etc/defaults/rc.conf (working copy) @@ -674,45 +674,12 @@ opensm_enable="NO" # Opensm(8) for infiniband devices defaults to off ############################################################## -### Jail Configuration ####################################### +### Jail Configuration (see rc.conf(5) manual page) ########## ############################################################## jail_enable="NO" # Set to NO to disable starting of any jails jail_parallel_start="NO" # Start jails in the background jail_list="" # Space separated list of names of jails -jail_set_hostname_allow="YES" # Allow root user in a jail to change its hostname -jail_socket_unixiproute_only="YES" # Route only TCP/IP within a jail -jail_sysvipc_allow="NO" # Allow SystemV IPC use from within a jail -# -# To use rc's built-in jail infrastructure create entries for -# each jail, specified in jail_list, with the following variables. -# NOTES: -# - replace 'example' with the jail's name. -# - except rootdir, hostname, ip and the _multi addresses, -# all of the following variables may be made global jail variables -# if you don't specify a jail name (ie. jail_interface, jail_devfs_ruleset). -# -#jail_example_rootdir="/usr/jail/default" # Jail's root directory -#jail_example_hostname="default.domain.com" # Jail's hostname -#jail_example_interface="" # Jail's interface variable to create IP aliases on -#jail_example_fib="0" # Routing table for setfib(1) -#jail_example_ip="192.0.2.10,2001:db8::17" # Jail's primary IPv4 and IPv6 address -#jail_example_ip_multi0="2001:db8::10" # and another IPv6 address -#jail_example_exec_start="/bin/sh /etc/rc" # command to execute in jail for starting -#jail_example_exec_afterstart0="/bin/sh command" # command to execute after the one for - # starting the jail. More than one can be - # specified using a trailing number -#jail_example_exec_stop="/bin/sh /etc/rc.shutdown" # command to execute in jail for stopping -#jail_example_devfs_enable="NO" # mount devfs in the jail -#jail_example_devfs_ruleset="ruleset_name" # devfs ruleset to apply to jail - - # usually you want "devfsrules_jail". -#jail_example_fdescfs_enable="NO" # mount fdescfs in the jail -#jail_example_procfs_enable="NO" # mount procfs in jail -#jail_example_mount_enable="NO" # mount/umount jail's fs -#jail_example_fstab="" # fstab(5) for mount/umount -#jail_example_flags="-l -U root" # flags for jail(8) -#jail_example_parameters="allow.raw_sockets=1" # extra parameters for this jail - ############################################################## ### Define source_rc_confs, the mechanism used by /etc/rc.* ## ### scripts to source rc_conf_files overrides safely. ## Index: share/man/man5/rc.conf.5 =================================================================== --- share/man/man5/rc.conf.5 (revision 256090) +++ share/man/man5/rc.conf.5 (working copy) @@ -3891,14 +3891,32 @@ If set to .Dq Li NO , any configured jails will not be started. +.It Va jail_conf +.Pq Vt str +The configuration filename used by +.Xr jail 8 +utility. +The default value is +.Pa /etc/jail.conf . .It Va jail_parallel_start .Pq Vt bool If set to .Dq Li YES , all configured jails will be started in the background (in parallel). +.It Va jail_flags +.Pq Vt str +Unset by default. +When set, use as default value for +.Va jail_ Ns Ao Ar jname Ac Ns Va _flags +for every jail in +.Va jail_list . .It Va jail_list .Pq Vt str A space separated list of names for jails. +If this variable is empty, +all of +.Xr jail 8 +instances in the configuration file will be configured. This is purely a configuration aid to help identify and configure multiple jails. The names specified in this list will be used to @@ -3908,171 +3926,41 @@ .Dq Li 0 .Pq zero is not allowed. +.It Va jail_* variables +Note that older releases supported per-jail configuration via +.Xr rc.conf 5 +variables. +For example, +hostname of a jail named +.Li vjail +was able to be set by +.Li jail_vjail_hostname . +These per-jail configuration variables are now obsolete in favor of +.Xr jail 8 +configuration file. +For backward compatibility, +when per-jail configuration variables are defined, +.Xr jail 8 +configuration files are created as +.Pa /var/run/jail. Ns Ao Ar jname Ac Ns Pa .conf +and used. .Pp -Assuming that the jail in question was named -.Li vjail , -you would have the following dependent variables: -.Bd -literal -jail_vjail_hostname="jail.example.com" -jail_vjail_ip="192.0.2.100" -jail_vjail_rootdir="/var/jails/vjail/root" -.Ed -.Pp -.It Va jail_flags -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _flags -for every jail in -.Va jail_list . -.It Va jail_interface -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _interface -for every jail in -.Va jail_list . -.It Va jail_fstab -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _fstab -for every jail in -.Va jail_list . -.It Va jail_mount_enable -.Pq Vt bool -Set to -.Dq Li NO -by default. -When set to -.Dq Li YES , -sets -.Va jail_ Ns Ao Ar jname Ac Ns Va _mount_enable -to -.Dq Li YES -by default for every jail in -.Va jail_list . -.It Va jail_devfs_ruleset -.Pq Vt str -Unset by default. -When set, sets -.Va jail_ Ns Ao Ar jname Ac Ns Va _devfs_ruleset -to given value for every jail in -.Va jail_list . -.It Va jail_devfs_enable -.Pq Vt bool -Set to -.Dq Li NO -by default. -When set to -.Dq Li YES , -sets -.Va jail_ Ns Ao Ar jname Ac Ns Va _devfs_enable -to -.Dq Li YES -by default for every jail in -.Va jail_list . -.It Va jail_fdescfs_enable -.Pq Vt bool -Set to -.Dq Li NO -by default. -When set to -.Dq Li YES , -sets -.Va jail_ Ns Ao Ar jname Ac Ns Va _fdescfs_enable -to -.Dq Li YES -by default for every jail in -.Va jail_list . -.It Va jail_procfs_enable -.Pq Vt bool -Set to -.Dq Li NO -by default. -When set to -.Dq Li YES , -sets -.Va jail_ Ns Ao Ar jname Ac Ns Va _fdescfs_enable -to -.Dq Li YES -by default for every jail in -.Va jail_list . -.It Va jail_exec_prestart Ns Aq Ar N -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_prestart Ns Aq Ar N -for every jail in -.Va jail_list . -.It Va jail_exec_start -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_start -for every jail in -.Va jail_list . -.It Va jail_exec_afterstart Ns Aq Ar N -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_afterstart Ns Aq Ar N -for every jail in -.Va jail_list . -.It Va jail_exec_poststart Ns Aq Ar N -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_poststart Ns Aq Ar N -for every jail in -.Va jail_list . -.It Va jail_exec_prestop Ns Aq Ar N -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_prestop Ns Aq Ar N -for every jail in -.Va jail_list . -.It Va jail_exec_stop -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_stop -for every jail in -.Va jail_list . -.It Va jail_exec_poststop Ns Aq Ar N -.Pq Vt str -Unset by default. -When set, use as default value for -.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_poststop Ns Aq Ar N -for every jail in -.Va jail_list . -.It Va jail_ Ns Ao Ar jname Ac Ns Va _rootdir -.Pq Vt str -Unset by default. -Set to the root directory used by jail -.Va jname . -.It Va jail_ Ns Ao Ar jname Ac Ns Va _hostname -.Pq Vt str -Unset by default. -Set to the fully qualified domain name (FQDN) assigned to jail -.Va jname . -.It Va jail_ Ns Ao Ar jname Ac Ns Va _parameters -.Pq Vt str -Unset by default. -Set extra parameters for jail -.Va jname , -such as -.Dq Li allow.chflags -or -.Dq Li children.max . -See -.Xr jail 8 -for a list of available parameters. -Note that the following parameters are already defined by +The following per-jail parameters are handled by .Pa rc.d/jail script out of their corresponding .Nm -variables: +variables. +In addition to them, parameters in +.Va jail_ Ns Ao Ar jname Ac Ns Va _parameters +will be added to the configuration file. +They must be a semi-colon +.Pq Ql \&; +delimited list of +.Dq key=value . +For more details, +see +.Xr jail 8 +manual page. .Bl -tag -width "host.hostname" -offset indent .It Li path set from @@ -4080,202 +3968,85 @@ .It Li host.hostname set from .Va jail_ Ns Ao Ar jname Ac Ns Va _hostname -.It Li command +.It Li exec.consolelog set from -.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_start +.Va jail_ Ns Ao Ar jname Ac Ns Va _consolelog . +The default value is +.Pa /var/log/jail_ Ao Ar jname Ac Pa _console.log . +.It Li interface +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _interface . +.It Li vnet.interface +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _vnet_interface . +This implies +.Li vnet +parameter will be enabled and cannot be specified with +.Va jail_ Ns Ao Ar jname Ac Ns Va _interface , +.Va jail_ Ns Ao Ar jname Ac Ns Va _ip +and/or +.Va jail_ Ns Ao Ar jname Ac Ns Va _ip_multi Ns Aq Ar n +at the same time. +.It Li fstab +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _fstab +.It Li exec.fib +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _fib +.It Li exec.start +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_start . +The parameter name was +.Li command +in some older releases. +.It Li exec.prestart +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_prestart +.It Li exec.poststart +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_poststart +.It Li exec.stop +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_stop +.It Li exec.prestop +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_prestop +.It Li exec.poststop +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _exec_poststop .It Li ip4.addr set if .Va jail_ Ns Ao Ar jname Ac Ns Va _ip -contains IPv4 addresses +or +.Va jail_ Ns Ao Ar jname Ac Ns Va _ip_multi Ns Aq Ar n +contain IPv4 addresses .It Li ip6.addr set if -.Va jail_ Ns Ao Ar jname Ac Ns Va _ip6 -contains IPv6 addresses +.Va jail_ Ns Ao Ar jname Ac Ns Va _ip +or +.Va jail_ Ns Ao Ar jname Ac Ns Va _ip_multi Ns Aq Ar n +contain IPv6 addresses +.It Li allow.mount +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _mount_enable +.It Li mount.devfs +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _devfs_enable +.It Li devfs_ruleset +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _devfs_ruleset . +This must be an integer, +not a string. +.It Li allow.set_hostname +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _set_hostname_allow +.It Li allow.rawsocket +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _socket_unixiproute_only +.It Li allow.sysvipc +set from +.Va jail_ Ns Ao Ar jname Ac Ns Va _sysvipc_allow .El -.It Va jail_ Ns Ao Ar jname Ac Ns Va _ip -.Pq Vt str -Unset by default. -Set to the (primary) IPv4 and/or IPv6 address(es) assigned to the jail. -The argument can be a sole address or a comma separated list of addresses. -Additionally each address can be prefixed by the name of an interface -followed by a pipe to overwrite -.Va jail_ Ns Ao Ar jname Ac Ns Va _interface -or -.Va jail_interface -and/or suffixed by a netmask, prefixlen or prefix. -In case no netmask, prefixlen or prefix is given, -.Sq /32 -will be used for IPv4 and -.Sq /128 -will be used for an IPv6 address. -If no address is given for the jail then the jail will be started with -no networking support. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _ip_multi Ns Aq Ar n -.Pq Vt str -Unset by default. -Set additional IPv4 and/or IPv6 address(es) assigned to the jail. -The sequence starts with -.Dq Li _multi0 -and the numbers have to be strictly ascending. -These entries follow the same syntax as their primary -.Va jail_ Ns Ao Ar jname Ac Ns Va _ip -entry. -The order of the entries can be important as the first address for -each address family found will be the primary address of the jail. -See -.Va ip-addresses -option in -.Xr jail 8 -for more details. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _flags -.Pq Vt str -Set to -.Dq Li -l -U root -by default. -These are flags to pass to -.Xr jail 8 . -.It Va jail_ Ns Ao Ar jname Ac Ns Va _interface -.Pq Vt str -Unset by default. -When set, sets the interface to use when setting IP address alias. -Note that the alias is created at jail startup and removed at jail shutdown. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _fib -.Pq Vt str -Unset by default. -When set, the jail is started with the specified forwarding table (sometimes -referred to as a routing table) via -.Xr setfib 1 . -.It Va jail_ Ns Ao Ar jname Ac Ns Va _fstab -.Pq Vt str -Set to -.Pa /etc/fstab. Ns Aq Ar jname -by default. -This is the file system information file to use for jail -.Va jname . -.It Va jail_ Ns Ao Ar jname Ac Ns Va _mount_enable -.Pq Vt bool -Set to -.Dq Li NO -by default. -When set to -.Dq Li YES , -mount all file systems from -.Va jail_ Ns Ao Ar jname Ac Ns Va _fstab -at jail startup. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _devfs_ruleset -.Pq Vt str -Unset by default. -When set, defines the device file system ruleset file to use for jail -.Va jname . -.It Va jail_ Ns Ao Ar jname Ac Ns Va _devfs_enable -.Pq Vt bool -Set to -.Dq Li NO -by default. -When set to -.Dq Li YES , -mount the device file system inside jail -.Ar jname -at jail startup. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _fdescfs_enable -.Pq Vt bool -Set to -.Dq Li NO -by default. -When set to -.Dq Li YES , -mount the file-descriptor file system inside jail -.Ar jname -at jail startup. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _procfs_enable -.Pq Vt bool -Set to -.Dq Li NO -by default. -When set to -.Dq Li YES , -mount the process file system inside jail -.Ar jname -at jail startup. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _exec_prestart Ns Aq Ar N -.Pq Vt str -Unset by default. -This is the command run as -.Ar N Ns -th command -before jail startup, where -.Ar N -is 0, 1, and so on. -It is run outside the jail. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _exec_start -.Pq Vt str -Set to -.Dq Li /bin/sh /etc/rc -by default. -This is the command executed in a jail at jail startup. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _exec_afterstart Ns Aq Ar N -.Pq Vt str -Unset by default. -This is the command run as -.Ar N Ns -th command -in a jail -after jail startup, where -.Ar N -is 1, 2, and so on. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _exec_poststart Ns Aq Ar N -.Pq Vt str -Unset by default. -This is the command run as -.Ar N Ns -th command -after jail startup, where -.Ar N -is 0, 1, and so on. -It is run outside the jail. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _exec_prestop Ns Aq Ar N -.Pq Vt str -Unset by default. -This is the command run as -.Ar N Ns -th command -before jail shutdown, where -.Ar N -is 0, 1, and so on. -It is run outside the jail. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _exec_stop -.Pq Vt str -Set to -.Dq Li /bin/sh /etc/rc.shutdown -by default. -This is the command executed in a jail at jail shutdown. -.It Va jail_ Ns Ao Ar jname Ac Ns Va _exec_poststop Ns Aq Ar N -.Pq Vt str -Unset by default. -This is the command run as -.Ar N Ns -th command -after jail shutdown, where -.Ar N -is 0, 1, and so on. -It is run outside the jail. -.It Va jail_set_hostname_allow -.Pq Vt bool -If set to -.Dq Li NO , -do not allow the root user in a jail to set its hostname. -.It Va jail_socket_unixiproute_only -.Pq Vt bool -If set to -.Dq Li YES , -do not allow any sockets, -besides UNIX/IP/route sockets, -to be used within a jail. -.It Va jail_sysvipc_allow -.Pq Vt bool -If set to -.Dq Li YES , -allow applications within a jail to use System V IPC. .\" ----------------------------------------------------- .It Va harvest_interrupt .Pq Vt bool Index: usr.sbin/jail/jail.c =================================================================== --- usr.sbin/jail/jail.c (revision 256090) +++ usr.sbin/jail/jail.c (working copy) @@ -470,10 +470,12 @@ if (dep_check(j)) continue; if (j->jid < 0) { - if (!(j->flags & (JF_DEPEND | JF_WILD)) - && verbose >= 0) - jail_quoted_warnx(j, - "not found", NULL); + if (!(j->flags & (JF_DEPEND|JF_WILD))) { + if (verbose >= 0) + jail_quoted_warnx(j, + "not found", NULL); + failed(j); + } goto jail_remove_done; } j->comparam = stopcommands; ----Next_Part(Mon_Oct__7_04_04_11_2013_092)---- ----Security_Multipart0(Mon_Oct__7_04_04_11_2013_176)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlJRtCsACgkQTyzT2CeTzy1z3QCeJ6/3B1fnadI52oGwyepBf6KX 4iUAoNdGI+MKRXsAn4QLzej5+rvkMYxZ =sH1M -----END PGP SIGNATURE----- ----Security_Multipart0(Mon_Oct__7_04_04_11_2013_176)---- From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 19:12:48 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7CA93607; Sun, 6 Oct 2013 19:12:48 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0AE562ABD; Sun, 6 Oct 2013 19:12:47 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBF6E6.dip0.t-ipconnect.de [217.251.246.230]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r96JCjgH091925; Sun, 6 Oct 2013 19:12:45 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r96JCXDO028077; Sun, 6 Oct 2013 21:12:33 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r96JCRxR014304; Sun, 6 Oct 2013 21:12:33 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310061912.r96JCRxR014304@fire.js.berklix.net> To: Matthew Fleming Subject: Re: lock order reversals on 10.0-ALPHA4 From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sun, 06 Oct 2013 08:22:27 PDT." Date: Sun, 06 Oct 2013 21:12:27 +0200 Sender: jhs@berklix.com Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 19:12:48 -0000 > > Those two LORs are well-known and at least the fist is definitely a false > positive. They're rather tricky to fix; there's been previous discussion. > > The first one is #261 at http://sources.zabbadoz.net/freebsd/lor.html . > The second one is probably #280. > > Cheers, > matthew Thanks Matthew, I'll ignore them then, plenty else to do :-) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 19:26:15 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A5C559B9; Sun, 6 Oct 2013 19:26:15 +0000 (UTC) (envelope-from pali.gabor@gmail.com) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 61C122B4F; Sun, 6 Oct 2013 19:26:15 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id ar20so14018835iec.32 for ; Sun, 06 Oct 2013 12:26:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=RzVULWIPIobqqS7Av5No7zALvJOMfptbl22Hz3Tes+w=; b=QS1NeAjjmUMFEQzn+cXlmNiVlja4JB2iDVYhTFO7foVUS//nxwBjziJoNEppOqdav0 OcgK4I7ORV5xR2z80bpqlac0VQgRQNJNq8RpQ9SkUvjHQBGSkPTvru2oBQyjMXhhjwsb SLEiHwBgV1LLRE9Tt0iJvNlOSJz/vkqP/LRywXUmf0ruVrO5uhZcnXuUX0JTjQWuiWIL 5F49YLho6lAZ9rShBsdUGJvgkjBExjhgW73IT+dIfPqKAqZgjw2ou1tDMFmFyhgy2D0F ZjrrpmJwN8aOjPnfyLo1i5yRFt57id2CnLCb6rZF5lzi8WvLHbermJ0TYgvmjupyf0qo A/wg== MIME-Version: 1.0 X-Received: by 10.50.45.100 with SMTP id l4mr14110990igm.60.1381087574830; Sun, 06 Oct 2013 12:26:14 -0700 (PDT) Sender: pali.gabor@gmail.com Received: by 10.64.27.105 with HTTP; Sun, 6 Oct 2013 12:26:14 -0700 (PDT) Date: Sun, 6 Oct 2013 21:26:14 +0200 X-Google-Sender-Auth: L1jQTvfLxuSh8bc30BKa8hSdZ_A Message-ID: Subject: Re: Call for FreeBSD 2013Q3 (July-September) Status Reports From: Gabor Pali To: hackers@freebsd.org, current@freebsd.org, stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 19:26:15 -0000 Dear FreeBSD Community, This is another gentle reminder that the deadline for submissions for the third Quarterly Status Report is tomorrow! Please find the details quoted below. On Sun, Sep 29, 2013 at 12:22 PM, Gabor Pali wrote: > Dear FreeBSD Community, > > Please note that the next submission date for the July to September > Quarterly Status Reports is October 7th, 2013, bit more than a week > away. Please consult my previous message for the details: > > On Mon, Sep 9, 2013 at 12:04 AM, Gabor Pali wrote: >> They do not have to be very long -- basically they may be about >> anything that lets people know what is going on around the FreeBSD >> Project. Submission of reports is not restricted to committers: >> Anyone who is doing anything interesting and FreeBSD-related can (and >> therefore encouraged to) write one! >> >> The preferred and easiest submission method is to use the XML >> generator [1] with the result emailed as an attachment to us, that is, >> monthly@FreeBSD.org [2]. There is also an XML template [3] which can >> be filled out manually and attached if preferred. >> >> To enable compilation and publication of the Q3 report as soon as >> possible for the October 7th deadline, please be prompt with any >> report submissions you may have. >> >> We are looking forward to all of your 2013Q3 reports! >> >> Cheers, >> Gabor >> >> >> [1] http://www.freebsd.org/cgi/monthly.cgi >> [2] mailto:monthly@freebsd.org >> [3] http://www.freebsd.org/news/status/report-sample.xml From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 21:39:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1DE0A5BD for ; Sun, 6 Oct 2013 21:39:19 +0000 (UTC) (envelope-from sean_bruno@yahoo.com) Received: from nm34-vm3.bullet.mail.bf1.yahoo.com (nm34-vm3.bullet.mail.bf1.yahoo.com [72.30.239.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 971A020D8 for ; Sun, 6 Oct 2013 21:39:18 +0000 (UTC) Received: from [98.139.212.144] by nm34.bullet.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 21:39:11 -0000 Received: from [98.139.211.206] by tm1.bullet.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 21:39:11 -0000 Received: from [127.0.0.1] by smtp215.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 21:39:11 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381095551; bh=xWaI0dqZPB3dp8Pja39gSbb+GykhJecJ0JBwibpC7CI=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=pw9Wo8bH5KwDjYo19N7ZhWqetur++qAoZx3Lq8J1b4jk2na4jt+eUpBgLlZ/FkuwZWHNJM5Ryt6Nvt4m9BjPRiLc9YsdZFgQ6970aTFlIYVBOYttE4fQn0BuyNFgNsxfoWkVD/KZjaK5TKOTLmiGtr59P/T4UWbcxcJLZayMps4= X-Yahoo-Newman-Id: 423583.23012.bm@smtp215.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: AZQ.MFUVM1mW6boJS7kMEMd8GoNuzlv7kPNRfADLbx8RneU HlrMjTTTubdYo33x9QsmQl7t02OjUobqAMLTSgZVbepQx7CiKDhjtKu9x2wJ cTUwn5QqjIUujLdsw41AUzUOgNOLsVJp88fm35aPbUKE_epsMwuxnmmR3b1z 6HortYG3elNHKCgidFOpnLstty_eMiVl.6h8DEbF4fh95bohGJ3JKFUTAHgx YCF7zxkFY0mUW5OgeSE1i9DCYOwZV532faEYcJTX8VlRHWM7riyzgGJpqjBI _AV5cHP2J4aVwwbA9_yMZ8cTYyGG6j2huWGUHRWuh7oJ82dYX9LqPa1XEp_d v8jecjAMthzStOsHb1Tsk8zoRlWjNrSd7s_N65Jik63bcjsIYC7y5QpFfN7Q ItQMzfLBLIKGVRFO.oNI8uriVGKJakuT2CRVLxeKXQ_M1MLt8ci0kx3YESiY rQiBQvMS29k_5A8N8mDdaCEgOzwu3T8kuvOoHQA81KYq0Wy6OlPwVTjzQKnj TcGb5YqvH5_Ii8q6kJ4yqHNY3cP5Cc3xN_XzMARuFxsUCNawO_4EK X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [192.168.100.228] (sean_bruno@24.23.220.111 with ) by smtp215.mail.bf1.yahoo.com with SMTP; 06 Oct 2013 14:39:11 -0700 PDT Subject: drm2/radeon dfixed_trunc() warnings From: Sean Bruno To: "freebsd-current@freebsd.org" Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-rgtCoYwmDgK4fOHKYw7y" Date: Sun, 06 Oct 2013 14:39:09 -0700 Message-ID: <1381095549.1586.7.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 21:39:19 -0000 --=-rgtCoYwmDgK4fOHKYw7y Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable These caught my eye today, and the checks strewn about sys/dev/drm2/radeon seem completely bogus to me, but I don't have the h/w to test it at the moment. /usr/src/sys/modules/drm2/radeonkms/../../../dev/drm2/radeon/rs690.c:491:37= : warning: comparison of unsigned expression < 0 is always false [-Wtautolo= gical-compare] if (dfixed_trunc(priority_mark02) < 0) dfixed_trunc is a macro: drm_fixed.h:#define dfixed_trunc(A) ((A).full >> 12) that returns the output of a shift right operation ... priority_mark02 is of type union fixed20_12, single element union of type u32, so I can't see this check ever doing anything useful. But, as always, I'm probably missing something obvious. =20 Sean --=-rgtCoYwmDgK4fOHKYw7y Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (FreeBSD) iQEcBAABAgAGBQJSUdh5AAoJEBkJRdwI6BaHMXoH/2a5cP+Wo/00dPi//49N/Jqq jzd1UE3Fy2ZAIsesPmSMMmY3i2ZnvcTFrhrXYuAIoviagREd24SEATm98SHNpOO2 Q4LmnQ2oSMBvoERA/ORnKqG6hPUNAl2WshfpC6OA/1DToy8mN58/moX1jQNNbO3d ulFKW1kTsXTf4LQmspGl0lcytVoONVfk3RY6FXzUKnYJ84VQ0C04Ya987hV3vwjZ 3kg7dgYqhqCELSzxh+XGznPb8iBk+9mYrs3d8oe6X/m694opVaohPQr7nrUFdH70 oIGcaUhn5Lny9yYt+VYcvAh9XZh9JHwIy9r4LPk4avJNJaPqksEef0oNayzglBE= =zlR4 -----END PGP SIGNATURE----- --=-rgtCoYwmDgK4fOHKYw7y-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 22:29:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D0700ED8 for ; Sun, 6 Oct 2013 22:29:07 +0000 (UTC) (envelope-from sean_bruno@yahoo.com) Received: from nm45-vm8.bullet.mail.bf1.yahoo.com (nm45-vm8.bullet.mail.bf1.yahoo.com [216.109.115.79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6D2D122AC for ; Sun, 6 Oct 2013 22:29:06 +0000 (UTC) Received: from [98.139.215.141] by nm45.bullet.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 22:28:59 -0000 Received: from [68.142.230.64] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 22:28:59 -0000 Received: from [127.0.0.1] by smtp221.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 22:28:59 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381098539; bh=wzlyVRJAH0G71jROjuU/uO+ySo1gn4gsApRCr+WTfjQ=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=c7bVFB+38lbp27s1GCJ0capDuJGfQ+7H2I74PkECrexolUXsSe3BM84V4KWDyuJGLLXskrwdshI4LqjD9uA02pmoSWbgWTYjr8qppJk7kq5il+fP1z0zn/9hQkW+TCKlT9NYG8puyo0la7Xrt5wtZpUOvXFj1gKXCl0sfeP/l/0= X-Yahoo-Newman-Id: 830722.53135.bm@smtp221.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: wW1Z9F0VM1mei6VLaeYoDMf6WFSqBSrvzeswPumMN5r06Gh CzcGAvr3qdwO23BEwncp7a2mUUQundrAG.9wfibOU7s04PtSFt0616udogCN E8C7rDzfIWpmnLJmgfcHNYOJvkO9j3vEHJre.1.lkdrxdGG5G97KwinK.Xoz 3qGH16VU3xitm5xYfywY2TQHnluGK0RGpMpVcRWz4Dx.ZllGjIfaOWfbHxFT Nnww_qKeX.Mw6caejjCAjSZNI09fKyh8fcjnEDimsRSMN42H4On_FEwu7Fv1 x.Tpx6yhkPCBCaYYnrY3gHMKmpSRSOhpG5zAOW.hFlUH2zA88na1HZgEGLVR NsMqnVYY_GYezT89CH.whVnzGI1EYMS_hiR4zMS8JHg3mBX9qHRhojo6lSJ4 qS_vDVFLGP_jIuhE5m54QPLbzwfTwtVwWtuWc6tEjeQZ9NCfGgShBN4A0l1P CXxFWlKoJstyERPVXcqy4EgacebMcennAkVZygpvI6lsOY.1BfL3gVkAQHUI kuDKyTzs7u0dZsJ3iIKXxFtcC6bA8IbWhnDrblVGhaY2TlRHoA0.XktN2d7g LU3hltFBpeM1jQbQ.EC8owOfD.iXdqwdgKXYnGrbJU66O2_eHCYGvD4.XWVe bkFBb8A2kk776 X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [192.168.100.228] (sean_bruno@24.23.220.111 with ) by smtp221.mail.bf1.yahoo.com with SMTP; 06 Oct 2013 22:28:59 +0000 UTC Subject: X related ports not finding version strings and hanging From: Sean Bruno To: "freebsd-current@freebsd.org" Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-Gzp1Z7qZUxf1PxFToQQQ" Date: Sun, 06 Oct 2013 15:28:58 -0700 Message-ID: <1381098538.1683.1.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 22:29:08 -0000 --=-Gzp1Z7qZUxf1PxFToQQQ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Was doing a portmaster -a today and noted that bsd.xorg.mk seems to be causing problems duing the update. When this happens, some prompt is waiting for me to hit "enter" that has scrolled past and I cannot see it. =20 =3D=3D=3D>>> All >> cairo-1.10.2_5,2 >> libGL-8.0.5_4 (13/35) make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X Server \([^ ]*\).*;\1;p'" make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X Server \([^ ]*\).*;\1;p'" make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X Server \([^ ]*\).*;\1;p'" make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X Server \([^ ]*\).*;\1;p'" --=-Gzp1Z7qZUxf1PxFToQQQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (FreeBSD) iQEcBAABAgAGBQJSUeQmAAoJEBkJRdwI6BaHrdoH/A79vnEy1V8n9O28256YXEey 7mrkQwSDTfhk9GcJqhTDANtgh8U4ctzdFcTskBncB99GQvavY9qXO7lk7S/oF6vQ ldM2MTrlgDkwUC25QyQmrKQnOj9O8Ts3/oW1CWHiuOidoAJc+Ip3Q0bGFr1OBhwc xMIEMqYu+5kBD0Jw9eG3bvZgcYLKADOo4DPfkZNiJa0Cc/EP6gowvuEfneMYtlqB 0ToQ7Ztew+THNSHjVC/Lkrx9YhpBbBMcn78jOcl4o8uchk6ZPZs2ZmB80x/m2JQq aYOn5pVlv/fzaIcWjdMX+ozBOVazFAjgJykHMvozdWUHVOy6xc/6/Q5fU044dMQ= =sh/f -----END PGP SIGNATURE----- --=-Gzp1Z7qZUxf1PxFToQQQ-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 22:36:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 26E6A100 for ; Sun, 6 Oct 2013 22:36:52 +0000 (UTC) (envelope-from sean_bruno@yahoo.com) Received: from nm27-vm1.bullet.mail.bf1.yahoo.com (nm27-vm1.bullet.mail.bf1.yahoo.com [98.139.213.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C73052303 for ; Sun, 6 Oct 2013 22:36:51 +0000 (UTC) Received: from [98.139.212.151] by nm27.bullet.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 22:36:44 -0000 Received: from [98.139.213.15] by tm8.bullet.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 22:36:44 -0000 Received: from [127.0.0.1] by smtp115.mail.bf1.yahoo.com with NNFMP; 06 Oct 2013 22:36:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381099004; bh=iZBFKH7S4kmLtO1/0oolV/zmOPDZb4ZxCmblr2KFrmE=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:Cc:In-Reply-To:References:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=KSP4lr80xhU2EWVHF1XenM5cGw6aIE4PkEJ1i30JmjWPavuArIcIEOl+khhpwSHHOICzo2hc/jZPeFbbT2AsDtDq5f2MvFPDzf0kHjNfcw1ByKfCTYO+p1QXQIkvqyCByjhP404cU+AJ5SJkCkQhOwAEW64LkTwqC9g8W1exs+M= X-Yahoo-Newman-Id: 509574.7004.bm@smtp115.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: ugDD4DoVM1mgrYNTOOF3N.deSRBqUnccGZLG.WBFcqd7hAR xNPnKBI3A6Gi3yAOl0akPx1PWZvOPfYuOCwEk3qmtCCrXM8hmysvSsTjKeuf qdzs7B5SFXciYySDm9ZyTokFSFAgGmrhL51SiFtkg9bdVWqdZew_oG9pkkJK tNPEoij9D8CwuBDe0j2sU.43sgBTTKOaCbr28XN5BRhiaYmKvKxlR91ZGNKN X2OxU5PoIqRO8gq7p5klQNWgG7MqscJD8koWQtkjH3eD6ICDx4m7j3fIcJ8E RslkumByDBwIvJBEOxCAoiqUlgm.vOkhiRcActey2dNpxLOU1xrKhjKhs716 3xZtDU4JoMGQf7UBo_VTixjgjeF6tEaUCBwyDr09dq4F6SN6mJLFKL9meoja 0.4eaMIOhF8a1mzVlSD7321Cc.L_cOA6gtVbLjqj_In4d.P_iIUy0Iq0KYoW 8IvxwZyRwY7tkRs0lRVib5tdCVhzUUShMuFJbGwgTyjRkkn67kZREzGeB6W8 v5xgkEs8ej66Dkb.8zrGOZjibM7.7b6WNf8TJzkiEaiSCto1AVEhVmz6we.U 8mhFDT.1ZQhGyL20rqi8jbxDE193A8yNpJFJxNGZhwvOASThzlApNMvVgu6X aKRnZDZiuz5.f X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [192.168.100.228] (sean_bruno@24.23.220.111 with ) by smtp115.mail.bf1.yahoo.com with SMTP; 06 Oct 2013 15:36:44 -0700 PDT Subject: Re: X related ports not finding version strings and hanging From: Sean Bruno To: sbruno@freebsd.org In-Reply-To: <1381098538.1683.1.camel@localhost> References: <1381098538.1683.1.camel@localhost> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-xzvFKc2j7T+tZmRPHaUU" Date: Sun, 06 Oct 2013 15:36:42 -0700 Message-ID: <1381099002.1683.2.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 22:36:52 -0000 --=-xzvFKc2j7T+tZmRPHaUU Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Sun, 2013-10-06 at 15:28 -0700, Sean Bruno wrote: > Was doing a portmaster -a today and noted that bsd.xorg.mk seems to be > causing problems duing the update. When this happens, some prompt is > waiting for me to hit "enter" that has scrolled past and I cannot see > it. =20 >=20 >=20 > =3D=3D=3D>>> All >> cairo-1.10.2_5,2 >> libGL-8.0.5_4 (13/35) >=20 > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X > Server \([^ ]*\).*;\1;p'" > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X > Server \([^ ]*\).*;\1;p'" > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X > Server \([^ ]*\).*;\1;p'" > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X > Server \([^ ]*\).*;\1;p'" >=20 Oh ... this is due to the bump in pixman. Wow. Let me *try* to rebuild it. sean --=-xzvFKc2j7T+tZmRPHaUU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (FreeBSD) iQEcBAABAgAGBQJSUeX6AAoJEBkJRdwI6BaHRNAIAJFPNLJ6gYt6tOdAEPbP6UE3 2XSPfrQ6wtfdYkP8wLSxdATNScVuebXSSVZuzDpsxrKWMIpow+7NZ8ZkX179gyJ6 IU1G31J60Q6TUWblnp7y1+I6StZ0tL+ZAzutnmH8nA4sPqkIvuVDY5BiF407Enic oBK6vTHsa7wgqEw8nXtSls3TdWRhmGnix5sxJOoZ3NgMZVsGK9hqL/k7uID8EP8N X6/ew4SpjNHMNisYUDjitaqqesk+p4HoervWryqwJ/UuJjcKndjwRxDpasV69tU3 43EhClQZM5qqbJPABKUzq6JfdXMryowF2WFJVzU9D2dwuivxejDFfAWbgHugOfg= =2fit -----END PGP SIGNATURE----- --=-xzvFKc2j7T+tZmRPHaUU-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 6 23:29:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4FFFC7C; Sun, 6 Oct 2013 23:29:19 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9B18824D3; Sun, 6 Oct 2013 23:29:19 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r96NTDUZ050031; Sun, 6 Oct 2013 16:29:13 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r96NTD6j050030; Sun, 6 Oct 2013 16:29:13 -0700 (PDT) (envelope-from sgk) Date: Sun, 6 Oct 2013 16:29:13 -0700 From: Steve Kargl To: sbruno@freebsd.org Subject: Re: X related ports not finding version strings and hanging Message-ID: <20131006232913.GA50021@troutmask.apl.washington.edu> References: <1381098538.1683.1.camel@localhost> <1381099002.1683.2.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1381099002.1683.2.camel@localhost> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Oct 2013 23:29:19 -0000 On Sun, Oct 06, 2013 at 03:36:42PM -0700, Sean Bruno wrote: > On Sun, 2013-10-06 at 15:28 -0700, Sean Bruno wrote: > > Was doing a portmaster -a today and noted that bsd.xorg.mk seems to be > > causing problems duing the update. When this happens, some prompt is > > waiting for me to hit "enter" that has scrolled past and I cannot see > > it. > > > > > > ===>>> All >> cairo-1.10.2_5,2 >> libGL-8.0.5_4 (13/35) > > > > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X > > Server \([^ ]*\).*;\1;p'" > > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X > > Server \([^ ]*\).*;\1;p'" > > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X > > Server \([^ ]*\).*;\1;p'" > > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org X > > Server \([^ ]*\).*;\1;p'" > > > > > Oh ... this is due to the bump in pixman. Wow. Let me *try* to rebuild > it. > Yep. Yet another port change disaster during a code freeze. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 02:01:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9DEB83CC for ; Mon, 7 Oct 2013 02:01:26 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 5DC412C50 for ; Mon, 7 Oct 2013 02:01:25 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:24590] helo=localhost) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 4D/24-15529-EE512525; Mon, 07 Oct 2013 02:01:19 +0000 Date: Mon, 07 Oct 2013 02:01:18 +0000 Message-ID: <4D.24.15529.EE512525@cdptpa-oedge01> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 02:01:26 -0000 I just happened to be browsing man urtwn in NetBSD-current (6.99.23), and Edimax EW-7811Un is listed as supported by this driver. This strongly suggests it should work for FreeBSD-current (barring bugs). Tom From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 02:43:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 03850B52 for ; Mon, 7 Oct 2013 02:43:52 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CF82B2DED for ; Mon, 7 Oct 2013 02:43:51 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id hz1so6668189pad.2 for ; Sun, 06 Oct 2013 19:43:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to:content-type; bh=N9fU7s/kBMobJgaEYWPzhfhlqsqhmksp0/3nbhvQXU0=; b=NFXBNVhUoWXRkqXJZFRAJabbFFRG8cRAnKldnoDpnZy1re0UOyi3S4imTvH/4+T9KU DoUIXBDriUbfOsHNbg4EubGdpurz0F5pmmIIS2WdQzki9S10IndzKlLYDDSOcr9v9RtU 64723F+0UkzcCNqEZPGdVMsynpVMGlfqF9k8Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=N9fU7s/kBMobJgaEYWPzhfhlqsqhmksp0/3nbhvQXU0=; b=dxekaXF/PLowjjK1Ngp71U4ysC+TmE9FZNmFKCrNosj6IJF4G7+ieabssDJaLCGzID 8IibDp6Ti+6k6bkohOlSRlDkkVF4jfKqn7OBtnkWe0gJwUSWVP/7QEUEIffpiUoKYGTI muZt4gfzOww77AkRmqkjVa4oHV6M1jekX2h35sCeYhukyt+kUhKSFTRVKJG92fH/cYP+ Mc4Rj+84tZ57uZKcGiANX4r4rMO585Lp+0g2fbQ9WswzQZZKyxSVoXL0DaktSms42hJI QhBMv1JtV/V/Nflz8sHF7qe8NAQ8UI7V3Lazf56p8jcpuRXRvYPz7tZw5YAdJ68Hc78v 0DXw== X-Gm-Message-State: ALoCoQmB49ri6i1Ud0U+Y4J8+ngRoon3o6Zp10WRmU1laIdqZjNi1ncWKI6FQjbtMCGo7HQ1ZPnl X-Received: by 10.68.189.163 with SMTP id gj3mr28170718pbc.102.1381113831505; Sun, 06 Oct 2013 19:43:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.6.3 with HTTP; Sun, 6 Oct 2013 19:43:21 -0700 (PDT) From: Eitan Adler Date: Sun, 6 Oct 2013 22:43:21 -0400 Message-ID: Subject: [Heads Up] RCS removed from base To: freebsd-current Current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 02:43:52 -0000 Hey all, RCS was removed from the base system in r256095. If you still want to use RCS please install either devel/rcs or devel/rcs57. If not, be sure to check out the alternatives (pun stolen and intended). -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 03:21:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C5CCC4F2 for ; Mon, 7 Oct 2013 03:21:46 +0000 (UTC) (envelope-from xenophon+freebsd@irtnog.org) Received: from mx1.irtnog.org (rrcs-24-123-13-55.central.biz.rr.com [24.123.13.55]) by mx1.freebsd.org (Postfix) with ESMTP id 9805B205B for ; Mon, 7 Oct 2013 03:21:46 +0000 (UTC) Received: from cinep001bsdgw.irtnog.net (localhost [127.0.0.1]) by mx1.irtnog.org (Postfix) with ESMTP id 51AC3C49 for ; Sun, 6 Oct 2013 23:21:45 -0400 (EDT) X-Virus-Scanned: amavisd-new at irtnog.org Received: from mx1.irtnog.org ([127.0.0.1]) by cinep001bsdgw.irtnog.net (mx1.irtnog.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 185wAkcqUv8r for ; Sun, 6 Oct 2013 23:21:39 -0400 (EDT) Received: from cinip100ntsbs.irtnog.net (cinip100ntsbs.irtnog.net [10.63.1.100]) by mx1.irtnog.org (Postfix) with ESMTP for ; Sun, 6 Oct 2013 23:21:39 -0400 (EDT) Subject: Hyper-V virtual DVD not detected Date: Sun, 6 Oct 2013 23:21:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.5 Thread-Topic: Hyper-V virtual DVD not detected thread-index: Ac7DB4nyYzEbusN+R7CaVgGxZgrzSA== From: "xenophon\\+freebsd" To: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 03:21:46 -0000 Hi everybody! Is anyone else running FreeBSD-current under Hyper-V? I can boot 10.0-ALPHA4 under Hyper-V Server 2012 using the installation CD image, but once running FreeBSD doesn't detect the virtual DVD drive - or at least the cd0 device is missing. Virtual hard disks attached to the same storage controller work just fine, IDE or SCSI. Conversely, everything works as expected under FreeBSD 9.2. I was able to install 10.0-ALPHA4 by attaching a second hard drive and copying the ISO image over the top of it. (The installer had no problems locating the FREEBSD_INSTALL volume on the second hard drive.) I'm not sure how to go about troubleshooting this. To start I am upgrading to r256072 in case any commits since ALPHA4 have fixed this problem. I'm also going to take a look at the source to the Hyper-V drivers. Beyond that, I'm open to any suggestions. Best wishes, Matthew --=20 I FIGHT FOR THE USERS From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 03:32:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2A65C6A0 for ; Mon, 7 Oct 2013 03:32:51 +0000 (UTC) (envelope-from xenophon@irtnog.org) Received: from mx1.irtnog.org (rrcs-24-123-13-55.central.biz.rr.com [24.123.13.55]) by mx1.freebsd.org (Postfix) with ESMTP id EB34220D1 for ; Mon, 7 Oct 2013 03:32:50 +0000 (UTC) Received: from cinep001bsdgw.irtnog.net (localhost [127.0.0.1]) by mx1.irtnog.org (Postfix) with ESMTP id 0E2FDC77 for ; Sun, 6 Oct 2013 23:32:49 -0400 (EDT) X-Virus-Scanned: amavisd-new at irtnog.org Received: from mx1.irtnog.org ([127.0.0.1]) by cinep001bsdgw.irtnog.net (mx1.irtnog.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BG8azaQ4Z4NR for ; Sun, 6 Oct 2013 23:32:31 -0400 (EDT) Received: from cinip100ntsbs.irtnog.net (cinip100ntsbs.irtnog.net [10.63.1.100]) by mx1.irtnog.org (Postfix) with ESMTP for ; Sun, 6 Oct 2013 23:32:30 -0400 (EDT) Subject: RE: Hyper-V virtual DVD not detected Date: Sun, 6 Oct 2013 23:32:29 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: In-Reply-To: Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.5 Thread-Topic: Hyper-V virtual DVD not detected thread-index: Ac7DB4nyYzEbusN+R7CaVgGxZgrzSAABbyVg References: From: "Matthew X. Economou" To: X-Mailman-Approved-At: Mon, 07 Oct 2013 03:34:41 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 03:32:51 -0000 Oh, never mind - apparently, this particular party has already started over in freebsd-virtualization@, something about how Hyper-V doesn't virtualize the CD/DVD drive. It's a work in progress. Best wishes, Matthew --=20 I FIGHT FOR THE USERS From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 03:39:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D8D2D7FB; Mon, 7 Oct 2013 03:39:09 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AAA9D2102; Mon, 7 Oct 2013 03:39:09 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id ro12so6562105pbb.27 for ; Sun, 06 Oct 2013 20:39:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=WSBHMEPmKocY/fu2pZzTAiBm2szoQoWTy4NShcHJPjY=; b=iDahxl1iHT6iGfXAiw7cAsYS87U9oPImvCDoc76GGQS6oskcS0YoYH+UB4Ebevbi0i Z1pK/nvNew9X5RVHghqlalHExxrWOxgKfckoR0LnMSJc2bUO1VnS8ecg7iNwbi/QPIHY LTdksBO+X2aKa9jfSTCTjsgY2EUao1GyaPsIeGtSiI2zf+ySbwL2GtqiKElEUAgvBa3t f3P+H0aLqOaVwoVTgAzj2eIklT/h5tTi0qrHhyJTA4KtOZUtCKf3NgqOVHQi//pDXNuL Y3OKDZLcAdjdk9Cp+37IOsLpR1KFjaUheKh3MhfzBrZBV4c+NjnKw/uLSmNwj3tNkRcM Y9IQ== MIME-Version: 1.0 X-Received: by 10.69.4.100 with SMTP id cd4mr19969732pbd.120.1381117148932; Sun, 06 Oct 2013 20:39:08 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.219.74 with HTTP; Sun, 6 Oct 2013 20:39:08 -0700 (PDT) In-Reply-To: <20131006232913.GA50021@troutmask.apl.washington.edu> References: <1381098538.1683.1.camel@localhost> <1381099002.1683.2.camel@localhost> <20131006232913.GA50021@troutmask.apl.washington.edu> Date: Sun, 6 Oct 2013 20:39:08 -0700 X-Google-Sender-Auth: m6Q2h2kC4q5Vv3JDH2sUM9T9FTw Message-ID: Subject: Re: X related ports not finding version strings and hanging From: Kevin Oberman To: Steve Kargl Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 03:39:10 -0000 On Sun, Oct 6, 2013 at 4:29 PM, Steve Kargl < sgk@troutmask.apl.washington.edu> wrote: > On Sun, Oct 06, 2013 at 03:36:42PM -0700, Sean Bruno wrote: > > On Sun, 2013-10-06 at 15:28 -0700, Sean Bruno wrote: > > > Was doing a portmaster -a today and noted that bsd.xorg.mk seems to be > > > causing problems duing the update. When this happens, some prompt is > > > waiting for me to hit "enter" that has scrolled past and I cannot see > > > it. > > > > > > > > > ===>>> All >> cairo-1.10.2_5,2 >> libGL-8.0.5_4 (13/35) > > > > > > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > > > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org > X > > > Server \([^ ]*\).*;\1;p'" > > > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > > > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org > X > > > Server \([^ ]*\).*;\1;p'" > > > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > > > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org > X > > > Server \([^ ]*\).*;\1;p'" > > > make: "/usr/ports/Mk/bsd.xorg.mk" line 158: warning: Couldn't read > > > shell's output for "/usr/local/bin/X -version 2>&1 | sed -n 's;^X\.Org > X > > > Server \([^ ]*\).*;\1;p'" > > > > > > > > > Oh ... this is due to the bump in pixman. Wow. Let me *try* to rebuild > > it. > > > > Yep. Yet another port change disaster during a code freeze. > > As usual with such upgrades, pkg_libchk is your friend. Assuming you have updated pixman: portmaster graphics/libGL graphics/dri pkg_libchk -o | grep pixman | cut -d: -f1 | sort | uniq > pixman-files.txt portmaster =D `cat pixman-files.txt` portmaster -aD portmaster -y -clean-distfiles This will do the job much more quickly than "portmaster -r pixman -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 13:28:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D42BF439; Mon, 7 Oct 2013 13:28:08 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 627D6236C; Mon, 7 Oct 2013 13:28:08 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBE81A.dip0.t-ipconnect.de [217.251.232.26]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r97DS5bi027609; Mon, 7 Oct 2013 13:28:06 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r97DRrEm035243; Mon, 7 Oct 2013 15:27:53 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r97DRl9W053828; Mon, 7 Oct 2013 15:27:53 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310071327.r97DRl9W053828@fire.js.berklix.net> To: Glen Barber Subject: Re: FreeBSD 10.0-ALPHA4 now available From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sun, 29 Sep 2013 21:58:17 EDT." <20130930015817.GC40093@glenbarber.us> Date: Mon, 07 Oct 2013 15:27:47 +0200 Sender: jhs@berklix.com Cc: freebsd-current@freebsd.org, FreeBSD Release Engineering Team X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 13:28:08 -0000 > The fourth ALPHA build of the 10.0-RELEASE release cycle is now available > on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and > sparc64 architectures. > > Note: Due to build issues within the head/ branch, ALPHA3 ISO builds > were skipped. > > The 10.0-ALPHA4 builds correlate to svn revision r255933 of the head/ > branch. (After zapping boot on an adjacent parition & repairing,) I avoided installer, & booted another partition, mounted FreeBSD-10.0-ALPHA4-amd64-memstick.img & tar'ed to empty partition 10.0-ALPHA4 runs, built & ran new generic kernel & ports X11 etc. :-) I had supposed an Alpha /usr/src would compile even if it broke at run time. Not so, 10.0-ALPHA4 src/ is broken (with & without obj & depend). cd /usr/src ; make -i install killed the system. To avoid killing, I hacked Makefiles, list below. Reinstalled & survived. I'll try with a newer current later, but Alpha4 src/ needs fixing. cd /usr/src ; cp /dev/null ~/tmp/`uname -r`.diffs foreach i ( `find . -name Makefile\*.pre_jhs | sort`) echo >> ~/tmp/`uname -r`.diffs diff -c $i `dirname $i`/`basename $i .pre_jhs` >> ~/tmp/`uname -r`.diffs end *** ./Makefile.inc1.pre_jhs Mon Oct 7 12:51:25 2013 --- ./Makefile.inc1 Mon Oct 7 12:51:57 2013 *************** *** 71,77 **** .endif SUBDIR+=gnu include .if ${MK_KERBEROS} != "no" ! SUBDIR+=kerberos5 .endif .if ${MK_RESCUE} != "no" SUBDIR+=rescue --- 71,77 ---- .endif SUBDIR+=gnu include .if ${MK_KERBEROS} != "no" ! # pre_jhs SUBDIR+=kerberos5 .endif .if ${MK_RESCUE} != "no" SUBDIR+=rescue *** ./lib/ncurses/Makefile.pre_jhs Mon Oct 7 12:48:21 2013 --- ./lib/ncurses/Makefile Mon Oct 7 14:53:27 2013 *************** *** 1,6 **** # $FreeBSD: head/lib/ncurses/Makefile 167359 2007-03-09 12:11:58Z rafan $ ! SUBDIR= ncurses form menu panel \ ! ncursesw formw menuw panelw .include --- 1,9 ---- # $FreeBSD: head/lib/ncurses/Makefile 167359 2007-03-09 12:11:58Z rafan $ ! SUBDIR= form menu panel \ ! formw menuw panelw ! # pre_jhs breaks compiling SUBDIR += ncurses ! # pre_jhs breaks compiling SUBDIR += ncursesw ! # pre_jhs install breaks /lib/libncurses.so.8: Undefined symbol "_nc_wacs" SUBDIR += ncursesw .include *** ./rescue/Makefile.pre_jhs Mon Oct 7 13:23:46 2013 --- ./rescue/Makefile Mon Oct 7 13:25:57 2013 *************** *** 1,6 **** # $FreeBSD: head/rescue/Makefile 117035 2003-06-29 18:35:37Z gordon $ SUBDIR= librescue \ ! rescue .include --- 1,7 ---- # $FreeBSD: head/rescue/Makefile 117035 2003-06-29 18:35:37Z gordon $ SUBDIR= librescue \ ! ! # pre_jhs rescue .include *** ./sbin/atm/Makefile.pre_jhs Sun Sep 29 03:14:17 2013 --- ./sbin/atm/Makefile Mon Oct 7 13:37:45 2013 *************** *** 23,28 **** # @(#) $Id: Makefile,v 1.5 1998/07/10 16:01:58 jpt Exp $ # $FreeBSD: head/sbin/atm/Makefile 179308 2008-05-25 22:11:40Z rwatson $ ! SUBDIR= atmconfig .include --- 23,28 ---- # @(#) $Id: Makefile,v 1.5 1998/07/10 16:01:58 jpt Exp $ # $FreeBSD: head/sbin/atm/Makefile 179308 2008-05-25 22:11:40Z rwatson $ ! #pre_jhs SUBDIR= atmconfig .include *** ./share/i18n/Makefile.pre_jhs Sun Sep 29 03:09:07 2013 --- ./share/i18n/Makefile Mon Oct 7 13:58:44 2013 *************** *** 3,8 **** .include ! SUBDIR= csmapper esdb .include --- 3,9 ---- .include ! # pre_jhs both break SUBDIR= csmapper esdb ! SUBDIR= .include *** ./sys/boot/userboot/Makefile.pre_jhs Sun Sep 29 03:12:25 2013 --- ./sys/boot/userboot/Makefile Mon Oct 7 14:05:33 2013 *************** *** 2,8 **** .include ! SUBDIR= ficl libstand test userboot .include --- 2,9 ---- .include ! # pre_jhs SUBDIR= ficl libstand test userboot ! SUBDIR= ficl libstand test .include *** ./usr.bin/Makefile.pre_jhs Sun Sep 29 03:13:01 2013 --- ./usr.bin/Makefile Mon Oct 7 14:13:43 2013 *************** *** 261,267 **** .endif .if ${MK_KERBEROS_SUPPORT} != "no" ! SUBDIR+= compile_et .endif .if ${MK_LDNS_UTILS} != "no" --- 261,267 ---- .endif .if ${MK_KERBEROS_SUPPORT} != "no" ! #pre_jhs SUBDIR+= compile_et .endif .if ${MK_LDNS_UTILS} != "no" Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 14:44:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 16E32D95 for ; Mon, 7 Oct 2013 14:44:24 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB1FB2858 for ; Mon, 7 Oct 2013 14:44:23 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id t60so1669491wes.30 for ; Mon, 07 Oct 2013 07:44:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=IYJqUTTfta8e8TNQHAcGhYevFD0u2lV1iMMrNNM6UPo=; b=nCWDTWcJw/Y9HZAhc9zAYjE77tqkZTWYsrBIHmDJeroBdsSFQ5rAl0m2ebbAMpsToy QwC5vneHhS8L5ek4XnT0jrlXBH11OdfW5f6F6eYsG9arLHvk2XE43M1O861abjuc+VYu kNl28QEIC0wanaSv5vzh5TysQDkkRA1lhQpAL790xLcTg+QzBk/iRCNEJd3uRY3BqXmm smv6sKTNArpgbHYZilfD2+lrx41rWdVFsv/Ch9u2CxbWU8lGcJ5vJYsfPqd4LA/1d7LK P1zaZ2V8PMS2/vYw6mui3x7/iN3kCrPNl91HYvdr4N1vNPOSWMUr6pCTn9WFTYb+x5Ha PY1Q== X-Received: by 10.194.104.42 with SMTP id gb10mr24846905wjb.16.1381157061857; Mon, 07 Oct 2013 07:44:21 -0700 (PDT) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.194.236.131 with HTTP; Mon, 7 Oct 2013 07:44:01 -0700 (PDT) From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Date: Mon, 7 Oct 2013 16:44:01 +0200 X-Google-Sender-Auth: -XCH5vXhzJbTBb-H-TdJw-PUIXs Message-ID: Subject: unionfs related panic on 10.0-ALPHA4 To: "freebsd-current@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 14:44:24 -0000 Hi all, I've got a panic on my 10.0 FreeBSD. This system was building port with poudriere and generate special nanobsd images (with unionfs usage) when it panic. I didn't have enough swap space for a full dump, I've just have a text dump: root@orange:/var/crash # cat info.last Dump header from device /dev/gpt/swap0 Architecture: amd64 Architecture Version: 1 Dump Length: 30720B (0 MB) Blocksize: 512 Dumptime: Mon Oct 7 15:16:55 2013 Hostname: orange.bsdrp.net Magic: FreeBSD Text Dump Version String: FreeBSD 10.0-ALPHA4 #15 r256062: Sat Oct 5 20:51:12 CEST 2013 root@orange.bsdrp.net:/usr/obj/usr/local/BSDRP/BSDRPcur/FreeBSD/src/sys/PROD Panic String: __lockmgr_args: downgrade a recursed lockmgr zfs @ /usr/local/BSDRP/BSDRPcur/FreeBSD/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1906 Dump Parity: 1116491583 Bounds: 1 Dump Status: good root@orange:/var/crash # cat version.txt FreeBSD 10.0-ALPHA4 #15 r256062: Sat Oct 5 20:51:12 CEST 2013 root@orange.bsdrp.net:/usr/obj/usr/local/BSDRP/BSDRPcur/FreeBSD/src/sys/PROD root@orange:/var/crash # cat msgbuf.txt ... panic: __lockmgr_args: downgrade a recursed lockmgr zfs @ /usr/local/BSDRP/BSDRPcur/FreeBSD/src/sys/modules/unionfs/../../fs/unionfs/union_vnops.c:1906 cpuid = 4 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe095d7d5480 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe095d7d5530 panic() at panic+0x155/frame 0xfffffe095d7d55b0 __lockmgr_args() at __lockmgr_args+0xdd3/frame 0xfffffe095d7d56c0 vop_stdlock() at vop_stdlock+0x3c/frame 0xfffffe095d7d56e0 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9d/frame 0xfffffe095d7d5710 unionfs_lock() at unionfs_lock+0x2bc/frame 0xfffffe095d7d57a0 VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9d/frame 0xfffffe095d7d57d0 _vn_lock() at _vn_lock+0x43/frame 0xfffffe095d7d5830 unionfs_readdir() at unionfs_readdir+0x13f/frame 0xfffffe095d7d5980 VOP_READDIR_APV() at VOP_READDIR_APV+0x98/frame 0xfffffe095d7d59b0 kern_getdirentries() at kern_getdirentries+0x20b/frame 0xfffffe095d7d5ab0 sys_getdirentries() at sys_getdirentries+0x28/frame 0xfffffe095d7d5ae0 amd64_syscall() at amd64_syscall+0x357/frame 0xfffffe095d7d5bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe095d7d5bf0 --- syscall (196, FreeBSD ELF64, sys_getdirentries), rip = 0x8008adcea, rsp = 0x7fffffffcfd8, rbp = 0x7fffffffd210 --- KDB: enter: panic Regards, Olivier From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 15:07:00 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7546F73E for ; Mon, 7 Oct 2013 15:07:00 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3B4D729CC for ; Mon, 7 Oct 2013 15:07:00 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r97F6wep082545; Mon, 7 Oct 2013 08:06:58 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r97F6ws3082542; Mon, 7 Oct 2013 08:06:58 -0700 (PDT) (envelope-from sgk) Date: Mon, 7 Oct 2013 08:06:58 -0700 From: Steve Kargl To: Eitan Adler Subject: Re: [Heads Up] RCS removed from base Message-ID: <20131007150658.GA79233@troutmask.apl.washington.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 15:07:00 -0000 On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: > Hey all, > > RCS was removed from the base system in r256095. If you still want to > use RCS please install either devel/rcs or devel/rcs57. If not, be > sure to check out the alternatives (pun stolen and intended). > Perhaps, a note in src/UPDATING is appropriate? -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 16:17:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C8F5EBA0; Mon, 7 Oct 2013 16:17:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 998872E6E; Mon, 7 Oct 2013 16:17:27 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id BD351B962; Mon, 7 Oct 2013 12:17:26 -0400 (EDT) From: John Baldwin To: Alexander Motin Subject: Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking Date: Mon, 7 Oct 2013 12:09:56 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <5224511D.4090503@FreeBSD.org> <201310021330.23251.jhb@freebsd.org> <525111A2.1020106@FreeBSD.org> In-Reply-To: <525111A2.1020106@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201310071209.56312.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 07 Oct 2013 12:17:26 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-geom@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 16:17:28 -0000 On Sunday, October 06, 2013 3:30:42 am Alexander Motin wrote: > On 02.10.2013 20:30, John Baldwin wrote: > > On Saturday, September 07, 2013 2:32:45 am Alexander Motin wrote: > >> On 07.09.2013 02:02, Jeremie Le Hen wrote: > >>> On Fri, Sep 06, 2013 at 11:29:11AM +0300, Alexander Motin wrote: > >>>> On 06.09.2013 11:06, Jeremie Le Hen wrote: > >>>>> On Fri, Sep 06, 2013 at 12:46:27AM +0200, Olivier Cochard-Labb=E9 w= rote: > >>>>>> On Thu, Sep 5, 2013 at 11:38 PM, Alexander Motin > > wrote: > >>>>>>> I've found and fixed possible double request completion, that cou= ld > > cause > >>>>>>> such symptoms if happened. Updated patch located as usual: > >>>>>>>=20 http://people.freebsd.org/~mav/camlock_patches/camlock_20130905.patch > >>>>>>> > >>>>> With this new one I cannot boot any more (I also updated the source > >>>>> tree). This is a hand transcripted version: > >>>>> > >>>>> Trying to mount root from zfs:zroot/root []... > >>>>> panic: Batch flag already set > >>>>> cpuid =3D 1 > >>>>> KDB: stack backtrace: > >>>>> db_trace_self_wrapper() > >>>>> kdb_backtrace() > >>>>> vpanic() > >>>>> kassert_panic() > >>>>> xpt_batch_start() > >>>>> ata_interrupt() > >>>>> softclock_call_cc() > >>>>> softclock() > >>>>> ithread_loop() > >>>>> fork_exit() > >>>>> fork_trampoline() > >>>> > >>>> Thank you for the report. I see my fault. It is probably specific to > >>>> ata(4) driver only. I've workarounded that in new patch version, but > >>>> probably that area needs some rethinking. > >>>> > >>>> http://people.freebsd.org/~mav/camlock_patches/camlock_20130906.patch > >>> > >>> I'm not sure you needed a confirmation, but it boots. Thanks :). > >>> > >>> I didn't quite understand the thread; is direct dispatch enabled for > >>> amd64? ISTR you said only i386 but someone else posted the macro for > >>> amd64. > >> > >> Yes, it is enabled for amd64. I've said x86, meaning both i386 and amd= 64. > > > > FYI, I tested mfi with this patch set and mfid worked fine for handling= =20 g_up > > directly: > > > > Index: dev/mfi/mfi_disk.c > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > --- dev/mfi/mfi_disk.c (revision 257407) > > +++ dev/mfi/mfi_disk.c (working copy) > > @@ -162,6 +162,7 @@ > > sc->ld_disk->d_unit =3D sc->ld_unit; > > sc->ld_disk->d_sectorsize =3D secsize; > > sc->ld_disk->d_mediasize =3D sectors * secsize; > > + sc->ld_disk->d_flags =3D DISKFLAG_DIRECT_COMPLETION; > > if (sc->ld_disk->d_mediasize >=3D (1 * 1024 * 1024)) { > > sc->ld_disk->d_fwheads =3D 255; > > sc->ld_disk->d_fwsectors =3D 63; > > >=20 > Thank you for the feedback. But looking on mfi driver sources I would=20 > say that it calls biodone() from mfi_disk_complete() from cm_complete()=20 > method, which is called while holding mfi_io_lock mutex. I guess that if= =20 > on top of mfi device would be some GEOM class, supporting direct=20 > dispatch and sending new requests down on previous request completion=20 > (or retrying requests), that could cause recursive mfi_io_lock=20 > acquisition. That is exactly the cause why I've added this flag. May be=20 > it is a bit paranoid, but it is better to be safe then sorry. >=20 > Another good reason to drop the lock before calling biodone() would be=20 > reducing the lock hold time. Otherwise it may just increase lock=20 > congestion there and destroy all benefits of the direct dispatch. Ah, interesting. What is your policy for such drivers? Should they be left using g_up, should they drop the lock around biodone when completeing multiple requests in an interrupt? Should they try to batch them by waiting and doing biodone at the end after dropping the lock? =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 16:30:34 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 776DC278; Mon, 7 Oct 2013 16:30:34 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B5D62F60; Mon, 7 Oct 2013 16:30:34 +0000 (UTC) Received: by mail-pd0-f176.google.com with SMTP id q10so7344927pdj.35 for ; Mon, 07 Oct 2013 09:30:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=6YTiqRUdh8tjnoygijfbDyM0qcyPWtStbckY38DfQQo=; b=nXumBb0ziWEqzhwbpxMx403kYr6MgGxoqSlXXnoxn4EnuC3iQ0xmULErZyoGvmcZnp 2QUDmFkHwoG1RN9Xxwsxn2khNDYfk0jNwkW+VdUV0uJcOQG/SmRAH75A7bIfd2FTSm1J 1dh601Bbv4x1B96HoB7+jFWr3YhqKrMS9F6e+IjvAXIHQkPuIyvRemquWh29l8ziDquN SR15ERGHUIDwQ6As3CGbzizPZsiRK5lM0Q5jC1uzxHdc+yb06JPTc7o9DaQOz36Pi01Z iK7ha1mMshGR/dbROnNF4EXiufQ9xstIcg6F+D7dqa0rmHMVqORQufuMbUGZj9gPzows ntFA== X-Received: by 10.66.250.47 with SMTP id yz15mr4196712pac.154.1381163433814; Mon, 07 Oct 2013 09:30:33 -0700 (PDT) Received: from localhost (c-76-21-78-151.hsd1.ca.comcast.net. [76.21.78.151]) by mx.google.com with ESMTPSA id bt1sm34353868pbb.2.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 09:30:33 -0700 (PDT) Sender: Gleb Kurtsou Date: Mon, 7 Oct 2013 09:31:11 -0700 From: Gleb Kurtsou To: freebsd-current@freebsd.org Subject: Committing PEFS to CURRENT Message-ID: <20131007163111.GB1590@reks.swifttest.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: delphij@freebsd.org, Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 16:30:34 -0000 Hello, I would like to ask everybody's opinion regarding committing PEFS to CURRENT. PEFS is a stacked cryptographic file system for FreeBSD. Development started as Google Summer of Code project in 2009. It has been in ports since Sept 2011. I maintain the project. Conceptually PEFS is similar to nullfs adding encryption layer on top of it. But it differs technically by not using vop_bypass. Another popular stacked cryptographic file systems include eCryptfs (linux) and encfs (fuse). There is also pam_pefs pam module to allow user authentication with their PEFS-encrypted home directory password. For those interested in high level introduction I would highly recommend article by Kris Moore in the BSD Magazine Issue 09/2013(50) - http://bsdmag.org/magazine/1848-day-to-day-bsd-administration We are very close to branching 10-STABLE now, but patch is non-intrusive, it only adds new functionality, enabling PEFS for i386 and amd64 (platforms it's known to work on). Patch passes make universe. Patch is available here: https://github.com/glk/freebsd-head/commit/b4d2c4a5f42f88fdd07cb75feba3467e4d4c043c.patch Pros/cons: - Having PEFS in base would be a huge maintenance help for PCBSD/TrueOS who are already committed to use PEFS in next product releases, e.g. PCBSD provides encrypted home directories. - There is steady interest in the project from users (emails, etc). Many of them note that file system is not well known yet. Moving PEFS to base would greatly increase its exposure. - Committing PEFS to base would also simplify maintenance by keeping it in sync with other subsystems, e.g. it will be updated on large scale changes like VM locking. - There are no bugs known at the moment. I've been using it to encrypt home directory since day one. pho@ ran stress test suite on it a while back, number of bugs was fixed. - PEFS is known to work on amd64 and i386 only. Big endian system and systems with page size larger than 4k are not tested. - NOTE! There has been no cryptography review. I'd like to suggest to add warning about file system and crypto used is experimental and hasn't undergone professional review. Similar to one we had in tmpfs. BSD Magazine article: http://bsdmag.org/magazine/1848-day-to-day-bsd-administration Port: http://www.freshports.org/sysutils/pefs-kmod/ Source code repository: https://github.com/glk/pefs FreeBSD DevSummit'2011 - pefs presentation slides: https://pefs.googlecode.com/files/pefs-devsummit.pdf FreeBSD wiki page: https://wiki.freebsd.org/PEFS I would really appreciate any comments or suggestions. Thank you, Gleb. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 16:44:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0E2CC951; Mon, 7 Oct 2013 16:44:40 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-ee0-x22a.google.com (mail-ee0-x22a.google.com [IPv6:2a00:1450:4013:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 18D0C20BB; Mon, 7 Oct 2013 16:44:38 +0000 (UTC) Received: by mail-ee0-f42.google.com with SMTP id b45so3411643eek.15 for ; Mon, 07 Oct 2013 09:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=35KWtTscl4vVGFofXojrrZELOiiZi7dj5Nw0m1SbJ74=; b=j51PA/X69Fs1qIT6aHHz1NvmV/+dUI22Nyqg0kq6Hm+aFiE61IqvFwB9h6xQIHw18U JIhtfFT8gG9gqEDJlWOUWS/b8G9kxIAcAIR7ayN42AzeEtR/zFnNVM5sxKjFX3wFJdGL /gpTUO4MWCIZRpdR/4Oc736lBJUy2RkPz2N53WZUS5C+XNuOGE1xOFyrAfWP1Hkj3kbO b64oi17jwW/F1h2T/0H1TB9lCSy8VgtKRsG2q9WGRZz7/ymbknp3n3okhOJZkI17zW0j rusZntKOpLwDPivPpfPebhkV2RY+eGSpCsZAKvgMXUepIBuYUm52+TyyOHWoQ26AcmWM 3qqQ== X-Received: by 10.14.88.65 with SMTP id z41mr49832497eee.38.1381164277446; Mon, 07 Oct 2013 09:44:37 -0700 (PDT) Received: from mavbook.mavhome.dp.ua ([46.211.77.102]) by mx.google.com with ESMTPSA id r48sm65342167eev.14.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 09:44:36 -0700 (PDT) Sender: Alexander Motin Message-ID: <5252E4F1.9070604@FreeBSD.org> Date: Mon, 07 Oct 2013 19:44:33 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130616 Thunderbird/17.0.6 MIME-Version: 1.0 To: John Baldwin Subject: Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking References: <5224511D.4090503@FreeBSD.org> <201310021330.23251.jhb@freebsd.org> <525111A2.1020106@FreeBSD.org> <201310071209.56312.jhb@freebsd.org> In-Reply-To: <201310071209.56312.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-geom@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 16:44:40 -0000 On 07.10.2013 19:09, John Baldwin wrote: > On Sunday, October 06, 2013 3:30:42 am Alexander Motin wrote: >> On 02.10.2013 20:30, John Baldwin wrote: >>> On Saturday, September 07, 2013 2:32:45 am Alexander Motin wrote: >>>> On 07.09.2013 02:02, Jeremie Le Hen wrote: >>>>> On Fri, Sep 06, 2013 at 11:29:11AM +0300, Alexander Motin wrote: >>>>>> On 06.09.2013 11:06, Jeremie Le Hen wrote: >>>>>>> On Fri, Sep 06, 2013 at 12:46:27AM +0200, Olivier Cochard-Labbé wrote: >>>>>>>> On Thu, Sep 5, 2013 at 11:38 PM, Alexander Motin >>> wrote: >>>>>>>>> I've found and fixed possible double request completion, that could >>> cause >>>>>>>>> such symptoms if happened. Updated patch located as usual: >>>>>>>>> > http://people.freebsd.org/~mav/camlock_patches/camlock_20130905.patch >>>>>>>>> >>>>>>> With this new one I cannot boot any more (I also updated the source >>>>>>> tree). This is a hand transcripted version: >>>>>>> >>>>>>> Trying to mount root from zfs:zroot/root []... >>>>>>> panic: Batch flag already set >>>>>>> cpuid = 1 >>>>>>> KDB: stack backtrace: >>>>>>> db_trace_self_wrapper() >>>>>>> kdb_backtrace() >>>>>>> vpanic() >>>>>>> kassert_panic() >>>>>>> xpt_batch_start() >>>>>>> ata_interrupt() >>>>>>> softclock_call_cc() >>>>>>> softclock() >>>>>>> ithread_loop() >>>>>>> fork_exit() >>>>>>> fork_trampoline() >>>>>> >>>>>> Thank you for the report. I see my fault. It is probably specific to >>>>>> ata(4) driver only. I've workarounded that in new patch version, but >>>>>> probably that area needs some rethinking. >>>>>> >>>>>> http://people.freebsd.org/~mav/camlock_patches/camlock_20130906.patch >>>>> >>>>> I'm not sure you needed a confirmation, but it boots. Thanks :). >>>>> >>>>> I didn't quite understand the thread; is direct dispatch enabled for >>>>> amd64? ISTR you said only i386 but someone else posted the macro for >>>>> amd64. >>>> >>>> Yes, it is enabled for amd64. I've said x86, meaning both i386 and amd64. >>> >>> FYI, I tested mfi with this patch set and mfid worked fine for handling > g_up >>> directly: >>> >>> Index: dev/mfi/mfi_disk.c >>> =================================================================== >>> --- dev/mfi/mfi_disk.c (revision 257407) >>> +++ dev/mfi/mfi_disk.c (working copy) >>> @@ -162,6 +162,7 @@ >>> sc->ld_disk->d_unit = sc->ld_unit; >>> sc->ld_disk->d_sectorsize = secsize; >>> sc->ld_disk->d_mediasize = sectors * secsize; >>> + sc->ld_disk->d_flags = DISKFLAG_DIRECT_COMPLETION; >>> if (sc->ld_disk->d_mediasize >= (1 * 1024 * 1024)) { >>> sc->ld_disk->d_fwheads = 255; >>> sc->ld_disk->d_fwsectors = 63; >>> >> >> Thank you for the feedback. But looking on mfi driver sources I would >> say that it calls biodone() from mfi_disk_complete() from cm_complete() >> method, which is called while holding mfi_io_lock mutex. I guess that if >> on top of mfi device would be some GEOM class, supporting direct >> dispatch and sending new requests down on previous request completion >> (or retrying requests), that could cause recursive mfi_io_lock >> acquisition. That is exactly the cause why I've added this flag. May be >> it is a bit paranoid, but it is better to be safe then sorry. >> >> Another good reason to drop the lock before calling biodone() would be >> reducing the lock hold time. Otherwise it may just increase lock >> congestion there and destroy all benefits of the direct dispatch. > > Ah, interesting. What is your policy for such drivers? Should they be > left using g_up, should they drop the lock around biodone when completeing > multiple requests in an interrupt? Should they try to batch them by > waiting and doing biodone at the end after dropping the lock? In CAM's da and ada drivers I've managed to drop the periph lock before calling biodone(). New CAM locking design allowed to do it safe. Possibility of dropping CAM SIM (HBA driver) locks on completion though depends on HBA design. For example, for ATA/SATA drivers I haven't found safe way to drop the lock in place, so I delay commands completions up to the moment when lock can be safely dropped and then process completions in a batch. For SCSI HBAs with more separated request and response queues I guess that may be easier. But now all SCSI drivers are still queuing requests completion to separate CAM threads to decouple the locks that way. I've just added more of them to spread the load between cores. But I hope that, for example, mps driver could be reworked to allow both using multiple MSI-X interrupt threads and lock-less request completion. Whether it is possible to do it safe for mfi I don't know. For cases when dropping the locks is not possible, there is g_up thread to use. For setups with single controller in a system with single interrupt thread queuing to g_up thread may even be better, helping to split load between two CPUs instead of one. But that is in case if HBA is fast or ineffective enough to saturate one CPU. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 16:53:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4F2EB121; Mon, 7 Oct 2013 16:53:18 +0000 (UTC) (envelope-from lifanov@mail.lifanov.com) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3821E2173; Mon, 7 Oct 2013 16:53:18 +0000 (UTC) Received: from [10.1.3.5] (cnet520-windstream.mcclatchyinteractive.com [166.108.16.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.lifanov.com (Postfix) with ESMTPSA id F38DE1A281C; Mon, 7 Oct 2013 12:53:11 -0400 (EDT) Message-ID: <5252E6F6.80009@mail.lifanov.com> Date: Mon, 07 Oct 2013 12:53:10 -0400 From: Nikolai Lifanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Gleb Kurtsou Subject: Re: Committing PEFS to CURRENT References: <20131007163111.GB1590@reks.swifttest.com> In-Reply-To: <20131007163111.GB1590@reks.swifttest.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 16:53:18 -0000 On 10/07/13 12:31, Gleb Kurtsou wrote: > Hello, > > I would like to ask everybody's opinion regarding committing PEFS to > CURRENT. > > PEFS is a stacked cryptographic file system for FreeBSD. Development > started as Google Summer of Code project in 2009. It has been in ports > since Sept 2011. I maintain the project. > > Conceptually PEFS is similar to nullfs adding encryption layer on top of > it. But it differs technically by not using vop_bypass. Another popular > stacked cryptographic file systems include eCryptfs (linux) and encfs > (fuse). There is also pam_pefs pam module to allow user authentication > with their PEFS-encrypted home directory password. > > For those interested in high level introduction I would highly recommend > article by Kris Moore in the BSD Magazine Issue 09/2013(50) - > http://bsdmag.org/magazine/1848-day-to-day-bsd-administration > > We are very close to branching 10-STABLE now, but patch is > non-intrusive, it only adds new functionality, enabling PEFS for i386 > and amd64 (platforms it's known to work on). Patch passes make universe. > > Patch is available here: > https://github.com/glk/freebsd-head/commit/b4d2c4a5f42f88fdd07cb75feba3467e4d4c043c.patch > > Pros/cons: > > - Having PEFS in base would be a huge maintenance help for PCBSD/TrueOS > who are already committed to use PEFS in next product releases, e.g. > PCBSD provides encrypted home directories. > > - There is steady interest in the project from users (emails, etc). > Many of them note that file system is not well known yet. Moving PEFS > to base would greatly increase its exposure. > > - Committing PEFS to base would also simplify maintenance by keeping it > in sync with other subsystems, e.g. it will be updated on large scale > changes like VM locking. > > - There are no bugs known at the moment. I've been using it to encrypt > home directory since day one. pho@ ran stress test suite on it a > while back, number of bugs was fixed. > > - PEFS is known to work on amd64 and i386 only. Big endian system and > systems with page size larger than 4k are not tested. > > - NOTE! There has been no cryptography review. I'd like to suggest to > add warning about file system and crypto used is experimental and hasn't > undergone professional review. Similar to one we had in tmpfs. > > > BSD Magazine article: > http://bsdmag.org/magazine/1848-day-to-day-bsd-administration > > Port: > http://www.freshports.org/sysutils/pefs-kmod/ > > Source code repository: > https://github.com/glk/pefs > > FreeBSD DevSummit'2011 - pefs presentation slides: > https://pefs.googlecode.com/files/pefs-devsummit.pdf > > FreeBSD wiki page: > https://wiki.freebsd.org/PEFS > > > I would really appreciate any comments or suggestions. > > > Thank you, > Gleb. Just a personal note: I hoped that you would commit pefs to base someday. It works well, and is the type of a core functionality that would be nice to have as early as the install ISO, before skel is copied over for the first user. I would be happy if this happened. - Nikolai Lifanov From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 18:25:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 75B76900 for ; Mon, 7 Oct 2013 18:25:13 +0000 (UTC) (envelope-from supportme@ukr.net) Received: from mx-out1.ukr.net (mx-out1.ukr.net [195.214.192.21]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0594427BF for ; Mon, 7 Oct 2013 18:25:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-Id:To:Subject:From:Date; bh=ocWKe6JVDLlnfKyPEcEu05XuU+MbFecIBGbIzFbgaXQ=; b=Q7mz6Iupb9ZmU7A/cYRB/GBMx9AjFrW72lwsVVe5jeUnCNsQNFXckU1XVKlH2jnjNZ4mDksRgefPp/2S06FKM6zQTEWNxnTKGw/pmb+QHMQW4IB24z4VBm4gPWxlFzWYN6ss46ZNXVGBDjSvIKOwofWNt5kpdzzpsW1Vbx9bLxk=; Received: from [10.10.10.45] (helo=frv45.ukr.net) by mx-out1.ukr.net with smtp ID 1VTFEz-000O8r-T6 for freebsd-current@freebsd.org; Mon, 07 Oct 2013 21:09:10 +0300 Date: Mon, 07 Oct 2013 21:09:06 +0300 From: Dmitriy Makarov Subject: ZFS L2ARC - incorrect size and abnormal system load on r255173 To: freebsd-current@freebsd.org X-Mailer: freemail.ukr.net 5.0 Message-Id: <1381166916.122992963.5h9ygiri@frv45.ukr.net> MIME-Version: 1.0 Received: from supportme@ukr.net by frv45.ukr.net; Mon, 07 Oct 2013 21:09:08 +0300 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 18:25:13 -0000 Hi all, On our production system on r255173 we have problem with abnormal high system load caused (not sure) with L2ARC placed on a few SSD, 490 GB total size. After a fresh boot everything seems to be fine, Load Average less then 5.00. But after some time (nearly day-two) Load Average jump to 10.. 20+ and system goes really slow, IO opearations with zfs pool grows from ms to even seconds. And L2ARC sysctls are pretty disturbing: [frv:~]$ sysctl -a | grep l2 vfs.zfs.l2arc_write_max: 25000000 vfs.zfs.l2arc_write_boost: 50000000 vfs.zfs.l2arc_headroom: 8 vfs.zfs.l2arc_feed_secs: 1 vfs.zfs.l2arc_feed_min_ms: 30 vfs.zfs.l2arc_noprefetch: 0 vfs.zfs.l2arc_feed_again: 1 vfs.zfs.l2arc_norw: 1 vfs.zfs.l2c_only_size: 1525206040064 vfs.cache.numfullpathfail2: 4 kstat.zfs.misc.arcstats.evict_l2_cached: 6592742547456 kstat.zfs.misc.arcstats.evict_l2_eligible: 734016778752 kstat.zfs.misc.arcstats.evict_l2_ineligible: 29462561417216 kstat.zfs.misc.arcstats.l2_hits: 576550808 kstat.zfs.misc.arcstats.l2_misses: 128158998 kstat.zfs.misc.arcstats.l2_feeds: 1524059 kstat.zfs.misc.arcstats.l2_rw_clash: 1429740 kstat.zfs.misc.arcstats.l2_read_bytes: 2896069043200 kstat.zfs.misc.arcstats.l2_write_bytes: 2405022640128 kstat.zfs.misc.arcstats.l2_writes_sent: 826642 kstat.zfs.misc.arcstats.l2_writes_done: 826642 kstat.zfs.misc.arcstats.l2_writes_error: 0 kstat.zfs.misc.arcstats.l2_writes_hdr_miss: 1059415 kstat.zfs.misc.arcstats.l2_evict_lock_retry: 1640 kstat.zfs.misc.arcstats.l2_evict_reading: 0 kstat.zfs.misc.arcstats.l2_free_on_write: 8580680 kstat.zfs.misc.arcstats.l2_abort_lowmem: 2096 kstat.zfs.misc.arcstats.l2_cksum_bad: 212832715 kstat.zfs.misc.arcstats.l2_io_error: 5501886 kstat.zfs.misc.arcstats.l2_size: 1587962307584 kstat.zfs.misc.arcstats.l2_asize: 1425666718720 kstat.zfs.misc.arcstats.l2_hdr_size: 82346948208 kstat.zfs.misc.arcstats.l2_compress_successes: 41707766 kstat.zfs.misc.arcstats.l2_compress_zeros: 0 kstat.zfs.misc.arcstats.l2_compress_failures: 0 kstat.zfs.misc.arcstats.l2_write_trylock_fail: 8847701930 kstat.zfs.misc.arcstats.l2_write_passed_headroom: 21220076 kstat.zfs.misc.arcstats.l2_write_spa_mismatch: 27619372107 kstat.zfs.misc.arcstats.l2_write_in_l2: 418007172085 kstat.zfs.misc.arcstats.l2_write_io_in_progress: 29279 kstat.zfs.misc.arcstats.l2_write_not_cacheable: 131001473113 kstat.zfs.misc.arcstats.l2_write_full: 63699 kstat.zfs.misc.arcstats.l2_write_buffer_iter: 1524059 kstat.zfs.misc.arcstats.l2_write_pios: 826642 kstat.zfs.misc.arcstats.l2_write_buffer_bytes_scanned: 8433038008130560 kstat.zfs.misc.arcstats.l2_write_buffer_list_iter: 96529899 kstat.zfs.misc.arcstats.l2_write_buffer_list_null_iter: 9228464 Here is output from zfs-stats about L2: [frv:~]$ zfs-stats -L ------------------------------------------------------------------------ ZFS Subsystem Report Mon Oct 7 20:50:19 2013 ------------------------------------------------------------------------ L2 ARC Summary: (DEGRADED) Passed Headroom: 21.22m Tried Lock Failures: 8.85b IO In Progress: 29.32k Low Memory Aborts: 2.10k Free on Write: 8.59m Writes While Full: 63.71k R/W Clashes: 1.43m Bad Checksums: 213.07m IO Errors: 5.51m SPA Mismatch: 27.62b L2 ARC Size: (Adaptive) 1.44 TiB Header Size: 5.19% 76.70 GiB L2 ARC Evicts: Lock Retries: 1.64k Upon Reading: 0 L2 ARC Breakdown: 705.25m Hit Ratio: 81.82% 577.01m Miss Ratio: 18.18% 128.24m Feeds: 1.52m L2 ARC Buffer: Bytes Scanned: 7.49 PiB Buffer Iterations: 1.52m List Iterations: 96.55m NULL List Iterations: 9.23m L2 ARC Writes: Writes Sent: 100.00% 826.96k ---------------------------------------------------------------------- In /boot/loader.conf (128GB RAM in system): vm.kmem_size="110G" vfs.zfs.arc_max="100G" vfs.zfs.arc_min="80G" vfs.zfs.vdev.cache.size=16M vfs.zfs.vdev.cache.max="16384" vfs.zfs.txg.timeout="10" vfs.zfs.write_limit_min="134217728" vfs.zfs.vdev.cache.bshift="14" vfs.zfs.arc_meta_limit=53687091200 vfs.zfs.l2arc_write_max=25165824 vfs.zfs.l2arc_write_boost=50331648 vfs.zfs.l2arc_noprefetch=0 In /etc/sysctl.conf: vfs.zfs.l2arc_write_max=25000000 vfs.zfs.l2arc_write_boost=50000000 vfs.zfs.l2arc_noprefetch=0 vfs.zfs.l2arc_headroom=8 vfs.zfs.l2arc_feed_min_ms=30 vfs.zfs.arc_meta_limit=53687091200 How can L2 ARC Size: (Adaptive) be 1.44 TiB (up) with total physical size of L2ARC devices 490GB? Why this values can grow and become so high? kstat.zfs.misc.arcstats.l2_cksum_bad: 212832715 kstat.zfs.misc.arcstats.l2_io_error: 5501886 Thanks for any help and ideas! From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 18:32:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AB6F1BBF for ; Mon, 7 Oct 2013 18:32:46 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 80A882838 for ; Mon, 7 Oct 2013 18:32:46 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 09A28220DD for ; Mon, 7 Oct 2013 14:32:45 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Mon, 07 Oct 2013 14:32:45 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=BL7qIoKx0QN4ISXpkMxpCbHxTWQ=; b=G7V Jho9HUG4rZKamA4o35HSNDdGLlnpS5F3cfUpkOavXa18m47gg+ctT4IrfYMpECmh 7Dhpjk2SzYgaYzzn1DJQxJpWSPXerlhzMuN7h7pkpTkd/RRMrqs/PuhzlBgb9+JP MOg2CwWIQp9s0kvaDKyNjhSHTrtPK9il2gnBWIo8= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id C99B8114991; Mon, 7 Oct 2013 14:32:44 -0400 (EDT) Message-Id: <1381170764.32684.31088349.343931EE@webmail.messagingengine.com> X-Sasl-Enc: a1ciD5Zqt0+57PfGwqf+CJaxjK5noVToJPWxGRdz3qWo 1381170764 From: Mark Felder To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 In-Reply-To: <1381166916.122992963.5h9ygiri@frv45.ukr.net> References: <1381166916.122992963.5h9ygiri@frv45.ukr.net> Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173 Date: Mon, 07 Oct 2013 13:32:44 -0500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 18:32:46 -0000 On Mon, Oct 7, 2013, at 13:09, Dmitriy Makarov wrote: > > How can L2 ARC Size: (Adaptive) be 1.44 TiB (up) with total physical size > of L2ARC devices 490GB? > http://svnweb.freebsd.org/base?view=revision&revision=251478 L2ARC compression perhaps? From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 19:04:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D3E728C7 for ; Mon, 7 Oct 2013 19:04:43 +0000 (UTC) (envelope-from sean_bruno@yahoo.com) Received: from nm24-vm1.bullet.mail.gq1.yahoo.com (nm24-vm1.bullet.mail.gq1.yahoo.com [98.136.217.96]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 94B042A22 for ; Mon, 7 Oct 2013 19:04:43 +0000 (UTC) Received: from [98.137.12.59] by nm24.bullet.mail.gq1.yahoo.com with NNFMP; 07 Oct 2013 19:04:37 -0000 Received: from [208.71.42.214] by tm4.bullet.mail.gq1.yahoo.com with NNFMP; 07 Oct 2013 19:04:37 -0000 Received: from [127.0.0.1] by smtp225.mail.gq1.yahoo.com with NNFMP; 07 Oct 2013 19:04:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381172677; bh=zNOi59ZVnlKe1zzhY/rVzK/4O7FqQkDDiCWaucyvLjQ=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:In-Reply-To:References:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=k8WoP3MgQzd+x9RWJq8FOJzBMbAkU25IGIMKhfQfBRPtHNI06PthTt7Bo0Fu4kdpy6qEHeKGDW9xqp3jrecYIo+AdBdFkW7QHNMAuv3KutR5ld5aYwNc9qfCT3CSnRponRLcUWNss/M6J7PP16IfcEHHGXjdCjwoIKyTUgrJSM8= X-Yahoo-Newman-Id: 163444.62368.bm@smtp225.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: ArHPTS0VM1kNXaER3aqdIWY5JEJkYUxboFPWmt8JAJHbZio 7PDLSEabnqAxdlCyRbuyffbAdusMN2JZ53zO1PAKCm0vxEXpEAak15CBZUms fbkCVHtTZjigQWZ9W8_d2Pta2sUZFO84Q60hu9LnkgrCkazY9fc13OoLGrN5 q.9eK8szRrGT6DeK.4MGSTiNhzPQNKtuzS_IDmON.YEFHRG357yUGGbNOAc2 8Scb0BQpeG_8n2onpaDuVpXZp0F.LIpnl7D_P1OeCjnZlWycU6oVMjABdlrI SZRbHRToAkwrdSNlHbjSc4Gi6kT7Rmu.jZxCTLboFS85SRAnjNHt5TayICci aJwsV3CNm7GfzaNJP_Xz5aAFuA9kMe_90Pp_oqmE0Huihlsq_5MjhxVyg.4t wxta9YCyWxnwXwS8qa_pri_k8bN8u9dR1Z7pmNBl7iv47BiQaJ9AMTITXiJz G.MH1aCEh663g8XsY1OpN3H1YF6Zc5j.tZemXHNFP2SnAlHUaVaNtYD4BcBu v9Oqpd9N4lw83Wh5688LoRCXFkbMS6_DqT_PXmXarhBXOmA1sjHce.PkeEJZ Kdo08h.NtJYDorc4RyHvC3TUfQZigaLzNq4nkrShsLLzEJ6KVuPicz9lL.Lg 0dij8t.QzaS5OLzAE7BYUcaVAm7fJN9Q6ZRE4YEK5uNHE9pia X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [10.73.160.242] (sean_bruno@209.131.62.116 with ) by smtp225.mail.gq1.yahoo.com with SMTP; 07 Oct 2013 19:04:37 +0000 UTC Subject: [patch] Re: drm2/radeon dfixed_trunc() warnings From: Sean Bruno To: "freebsd-current@freebsd.org" In-Reply-To: <1381095549.1586.7.camel@localhost> References: <1381095549.1586.7.camel@localhost> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-KslReGfPW9C9628YLhIx" Date: Mon, 07 Oct 2013 12:04:36 -0700 Message-ID: <1381172676.3091.0.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 19:04:44 -0000 --=-KslReGfPW9C9628YLhIx Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Sun, 2013-10-06 at 14:39 -0700, Sean Bruno wrote:=20 > These caught my eye today, and the checks strewn about > sys/dev/drm2/radeon seem completely bogus to me, but I don't have the > h/w to test it at the moment. >=20 > /usr/src/sys/modules/drm2/radeonkms/../../../dev/drm2/radeon/rs690.c:491:= 37: warning: comparison of unsigned expression < 0 is always false [-Wtauto= logical-compare] > if (dfixed_trunc(priority_mark02) < 0) >=20 >=20 > dfixed_trunc is a macro: > drm_fixed.h:#define dfixed_trunc(A) ((A).full >> 12) >=20 > that returns the output of a shift right operation ... priority_mark02 > is of type union fixed20_12, single element union of type u32, so I > can't see this check ever doing anything useful. >=20 > But, as always, I'm probably missing something obvious. =20 >=20 > Sean Proposed patch to eliminate this check. If I understand the macro correctly, there's no way for these checks to ever do anything as bit shifting an unsigned will simply clear out the value. So, the check for <0 is completely bogus? Sean http://people.freebsd.org/~sbruno/drm2_radeon_useless.txt=20 --=-KslReGfPW9C9628YLhIx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (FreeBSD) iQEcBAABAgAGBQJSUwXBAAoJEBkJRdwI6BaHkV0H/2fKecxd9JKu/1Zsvh5bbqS+ uQYqab0ralSU39cuPCw1+aZ5hM08dBRsCoZS3uddC5GPRBYvvBIICxNVffuqfdSD RJPHFqSo/0wZhkcIFks/MbWSOUMBnsL/IbEu4Nrl6DXVbrJvs0KQuyBxvRkxi8LS ZBATQr6404rkqyi5si8rlpRl7ajQ02OB5f7N7GxwtBU8OkLi2LQPPb3xqiekhNc6 Ff/okihzRdyYeW5B10/wz5uHZkTmsNa7zun4k5aO50KzKh5hBk0DYiEjkGkhShLV tl2yF/TSk70CVlR62x7iZn+hgvcIbD80aEUFXAoCxgHqqQYfahKxfTKmBqqh6ns= =XVwr -----END PGP SIGNATURE----- --=-KslReGfPW9C9628YLhIx-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 19:04:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E0E219D2 for ; Mon, 7 Oct 2013 19:04:52 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B79592A2A for ; Mon, 7 Oct 2013 19:04:52 +0000 (UTC) Received: by mail-pb0-f53.google.com with SMTP id up15so7475884pbc.26 for ; Mon, 07 Oct 2013 12:04:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1+mR4+1XsoJhDTOV7LnphaFYFpmSHDLmSKjsQkRGW6M=; b=AVbOQ+x/9c6hAeltCHPJMaaC0v+37oTN2UucjLR3ehyV6zXZEddNrY4byEv6e8GqXg cSyv21ehPwiFijmPiVHthrGHmUeQn69uf5DniKs4UcbRApd56Iv7CKS3MSJL3fWJGDu7 JWmfMnuv3dAoe33SCx335APki+iuEZ89YN3fg= 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:from:date :message-id:subject:to:cc:content-type; bh=1+mR4+1XsoJhDTOV7LnphaFYFpmSHDLmSKjsQkRGW6M=; b=P69ITZna1xXQ+RWIaNlwuckaLjGaFUrVKwXltwlkjgys3s8j+/nw/I4+N7SqKiU7uN NDPpwGK8v5ln7eENnQroICxz2ygzGg2mB9L+AnHKzMgdiupwIp6iCblsLP/91Sz0C6QL 6oAmxsqW6M84rTWVxUT9VhgajadPKuNaL3m5ffk6tCXy2o/2qDuPCailCKyogx2zRCHg 5silz3PDX/7Ijt0oAltwEzRzBi2s1Km2ws64aCU6L42q7/ajxmnfoJYLnODdkpa4fpPT KD5m1pKmUz1KKVkxJH/jASRDBlk67xwY425K7SOEIrWxNiP+W8jQ7EiE15JBjz+meE43 pWcg== X-Gm-Message-State: ALoCoQlAtORrOEq0dLMnLfRBYSunaav30oxBZAQPQc05uEHv8TRW62bez5Qp/SORoY3g2LXHMcpa X-Received: by 10.68.4.197 with SMTP id m5mr32563350pbm.46.1381172692465; Mon, 07 Oct 2013 12:04:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.6.3 with HTTP; Mon, 7 Oct 2013 12:04:22 -0700 (PDT) In-Reply-To: <20131007150658.GA79233@troutmask.apl.washington.edu> References: <20131007150658.GA79233@troutmask.apl.washington.edu> From: Eitan Adler Date: Mon, 7 Oct 2013 15:04:22 -0400 Message-ID: Subject: Re: [Heads Up] RCS removed from base To: Steve Kargl Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 19:04:52 -0000 On Mon, Oct 7, 2013 at 11:06 AM, Steve Kargl wrote: > On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: >> Hey all, >> >> RCS was removed from the base system in r256095. If you still want to >> use RCS please install either devel/rcs or devel/rcs57. If not, be >> sure to check out the alternatives (pun stolen and intended). >> > > Perhaps, a note in src/UPDATING is appropriate? Absolutely! I've sent a request to re@. -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 19:08:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D5776C42; Mon, 7 Oct 2013 19:08:27 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 909722A76; Mon, 7 Oct 2013 19:08:27 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1VTFt2-000Lbt-E4 ; Mon, 07 Oct 2013 21:50:32 +0300 Date: Mon, 7 Oct 2013 21:50:32 +0300 From: Vitalij Satanivskij To: Mark Felder Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173 Message-ID: <20131007185032.GA82932@hell.ukr.net> References: <1381166916.122992963.5h9ygiri@frv45.ukr.net> <1381170764.32684.31088349.343931EE@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1381170764.32684.31088349.343931EE@webmail.messagingengine.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 19:08:27 -0000 Data on pool have compressratio around 1.4 On diferent servers with same data type and load L2 ARC Size: (Adaptive) can be diferent for example 1.04 TiB vs 1.45 TiB But it's all have same porblem - grow in time. More stange for us - ARC: 80G Total, 4412M MFU, 5040M MRU, 76M Anon, 78G Header, 2195M Other 78G header size and ubnormal - kstat.zfs.misc.arcstats.l2_cksum_bad: 210920592 kstat.zfs.misc.arcstats.l2_io_error: 7362414 sysctl's growing avery second. All part's of server (as hardware part's) in in normal state. After reboot no problem's for some period untile cache size grow to some limit. Mark Felder wrote: MF> On Mon, Oct 7, 2013, at 13:09, Dmitriy Makarov wrote: MF> > MF> > How can L2 ARC Size: (Adaptive) be 1.44 TiB (up) with total physical size MF> > of L2ARC devices 490GB? MF> > MF> MF> http://svnweb.freebsd.org/base?view=revision&revision=251478 MF> MF> L2ARC compression perhaps? MF> _______________________________________________ MF> freebsd-current@freebsd.org mailing list MF> http://lists.freebsd.org/mailman/listinfo/freebsd-current MF> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 19:54:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2219D335; Mon, 7 Oct 2013 19:54:18 +0000 (UTC) (envelope-from zbodek@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 56C9C2D87; Mon, 7 Oct 2013 19:54:17 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hj3so5421977wib.7 for ; Mon, 07 Oct 2013 12:54:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=1StacpTJvA4GeZgXVaL3iLFSyZ3I1jQdD/4aJcwuA6I=; b=Z7QBpD4XVC3NvCFpvzFauX1A05qH56NYm32TullTQ+pAR29tssByVmYR6m31e4DlDY M7ooJIleB+ogdRUUSBW6Efyi/uJPo+ZcoRJY/o+5vK+klYYt7WBNUEUW6BbWGCPtP9in nKnTbIJsiD/uUwTXpl8J5ZLtVZF9naO+mX5h/e8GvX/uZoX9XXzreIrA+1d8yPPOt0Pw KMS71P57nYy7P5xsbeZdC3y4FVuxlbEGAE4aXRCduOlsHi6IWAaExo6lXyR4i/4TlLMN F80eYPF99tuIBkXSlMKUdUDspU+j6HQ0K4huB3MFz4MkWqsgHSLzWs6M4qsa7izRfAR0 Gxzg== MIME-Version: 1.0 X-Received: by 10.180.189.205 with SMTP id gk13mr20307097wic.12.1381175655522; Mon, 07 Oct 2013 12:54:15 -0700 (PDT) Sender: zbodek@gmail.com Received: by 10.216.160.70 with HTTP; Mon, 7 Oct 2013 12:54:15 -0700 (PDT) Date: Mon, 7 Oct 2013 21:54:15 +0200 X-Google-Sender-Auth: UT-vnNHObIgX6J0X5BA0I4Qvxn8 Message-ID: Subject: Changes to UART ns8250 From: Zbigniew Bodek To: freebsd-embedded@freebsd.org Content-Type: multipart/mixed; boundary=001a11c366d052011d04e82c04a8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 19:54:18 -0000 --001a11c366d052011d04e82c04a8 Content-Type: text/plain; charset=ISO-8859-1 Hello. I would like to present a patch for ns8250 serial that I would like to commit in the near future (if there are no objections). The patch is fixing newest DesignWare UART with busy detection. During frequency divisors configuration when UART is busy transferring or receiving data, line control register manipulation will not take effect. Therefore, we will not set divisor latch access bit and we will corrupt LCR instead of configuring divisors. It is necessary to wait until UART finishes all transfers to proceed with the configuration. This was detected on Armada XP as UART fails on this issue 100/100 attempts. The patch was tested by kevlo@ and me and it works on our Armada XP - based systems. Please send your comment or remarks if there are any. Best regards Zbigniew Bodek --001a11c366d052011d04e82c04a8 Content-Type: application/octet-stream; name="0001-Wait-for-DesignWare-UART-transfers-completion-before.patch" Content-Disposition: attachment; filename="0001-Wait-for-DesignWare-UART-transfers-completion-before.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hmi48egp0 RnJvbSBiMWU0Nzc5OGFlMjY5OGY0MjI3N2YwOTFlODQxZGZiNzEyNTY2MzA0IE1vbiBTZXAgMTcg MDA6MDA6MDAgMjAwMQpGcm9tOiBaYmlnbmlldyBCb2RlayA8emJiQHNlbWloYWxmLmNvbT4KRGF0 ZTogU2F0LCA1IE9jdCAyMDEzIDAyOjI1OjIzICswMjAwClN1YmplY3Q6IFtQQVRDSCAxLzNdIFdh aXQgZm9yIERlc2lnbldhcmUgVUFSVCB0cmFuc2ZlcnMgY29tcGxldGlvbiBiZWZvcmUKIGFjY2Vz c2luZyBsaW5lIGNvbnRyb2wKCldoZW4gdXNpbmcgRFcgVUFSVCB3aXRoIEJVU1kgZGV0ZWN0aW9u IGl0IGlzIG5lY2Vzc2FyeSB0byB3YWl0CnVudGlsIGFsbCBzZXJpYWwgdHJhbnNmZXJzIGFyZSBm aW5pc2hlZCBiZWZvcmUgbWFuaXB1bGF0aW5nIHRoZQpsaW5lIGNvbnRyb2wuIExDUiB3aWxsIG5v dCBiZSBhZmZlY3RlZCB3aGVuIFVBUlQgaXMgYnVzeS4KSW4gYWRkaXRpb24sIGlmIERpdmlzb3Ig TGF0Y2ggQWNjZXNzIEJpdCBpcyBiZWluZyBzZXQgaW4gb3JkZXIgdG8KbW9kaWZ5IFVBUlQgZGl2 aXNvcnM6CjEuIFdlIHdpbGwgZ2V0IEJVU1kgaW50ZXJydXB0IGlmIGludGVycnVwdHMgYXJlIGVu YWJsZWQuCjIuIEJlY2F1c2UgTENSIHdpbGwgbm90IGJlIGFmZmVjdGVkIHRoZSBUSFIgYW5kIChl dmVuIHdvcnNlKSBJRVIKICAgY29udGVudHMgd2lsbCBiZSBjb3JydXB0ZWQuIFRoaXMgd2lsbCBs ZWFkIHRvIGNvbnNvbGUgaGFuZy4KClRlc3RlZCBieToJa2V2bG8KQXBwcm92ZWQgYnk6CWNvZ25l dCAobWVudG9yKQotLS0KIHN5cy9kZXYvaWMvbnMxNjU1MC5oICAgICAgICAgICB8ICAxICsKIHN5 cy9kZXYvdWFydC91YXJ0X2Rldl9uczgyNTAuYyB8IDEwICsrKysrKysrKysKIDIgZmlsZXMgY2hh bmdlZCwgMTEgaW5zZXJ0aW9ucygrKQoKZGlmZiAtLWdpdCBhL3N5cy9kZXYvaWMvbnMxNjU1MC5o IGIvc3lzL2Rldi9pYy9uczE2NTUwLmgKaW5kZXggNjU5ZjU5MS4uMzNhN2RkMSAxMDA2NDQKLS0t IGEvc3lzL2Rldi9pYy9uczE2NTUwLmgKKysrIGIvc3lzL2Rldi9pYy9uczE2NTUwLmgKQEAgLTE4 NSw2ICsxODUsNyBAQAogI2RlZmluZSBEV19SRUdfVVNSCTMxCS8qIERlc2lnbldhcmUgZGVyaXZl ZCBVYXJ0IFN0YXR1cyBSZWcgKi8KICNkZWZpbmUgY29tX3VzcgkJMzkJLyogT2N0ZW9uIDE2NzUw LzE2NTUwIFVhcnQgU3RhdHVzIFJlZyAqLwogI2RlZmluZSBSRUdfVVNSCQljb21fdXNyCisjZGVm aW5lIFVTUl9CVVNZCTEJLyogVWFydCBCdXN5LiBTZXJpYWwgdHJhbnNmZXIgaW4gcHJvZ3Jlc3Mg Ki8KICNkZWZpbmUgVVNSX1RYRklGT19OT1RGVUxMIDIgICAgLyogVWFydCBUWCBGSUZPIE5vdCBm dWxsICovCiAKIC8qIDE2OTUwIHJlZ2lzdGVyICMxLiAgQWNjZXNzIGVuYWJsZWQgYnkgQUNSWzdd LiAgQWxzbyByZXF1aXJlcyAhTENSWzddLiAqLwpkaWZmIC0tZ2l0IGEvc3lzL2Rldi91YXJ0L3Vh cnRfZGV2X25zODI1MC5jIGIvc3lzL2Rldi91YXJ0L3VhcnRfZGV2X25zODI1MC5jCmluZGV4IDIx MWQxMTMuLjVjOTM5Y2UgMTAwNjQ0Ci0tLSBhL3N5cy9kZXYvdWFydC91YXJ0X2Rldl9uczgyNTAu YworKysgYi9zeXMvZGV2L3VhcnQvdWFydF9kZXZfbnM4MjUwLmMKQEAgLTY0NywxMSArNjQ3LDIx IEBAIGludAogbnM4MjUwX2J1c19wYXJhbShzdHJ1Y3QgdWFydF9zb2Z0YyAqc2MsIGludCBiYXVk cmF0ZSwgaW50IGRhdGFiaXRzLAogICAgIGludCBzdG9wYml0cywgaW50IHBhcml0eSkKIHsKKwlz dHJ1Y3QgbnM4MjUwX3NvZnRjICpuczgyNTA7CiAJc3RydWN0IHVhcnRfYmFzICpiYXM7CiAJaW50 IGVycm9yOwogCisJbnM4MjUwID0gKHN0cnVjdCBuczgyNTBfc29mdGMqKXNjOwogCWJhcyA9ICZz Yy0+c2NfYmFzOwogCXVhcnRfbG9jayhzYy0+c2NfaHdtdHgpOworCS8qCisJICogV2hlbiB1c2lu ZyBEVyBVQVJUIHdpdGggQlVTWSBkZXRlY3Rpb24gaXQgaXMgbmVjZXNzYXJ5IHRvIHdhaXQKKwkg KiB1bnRpbCBhbGwgc2VyaWFsIHRyYW5zZmVycyBhcmUgZmluaXNoZWQgYmVmb3JlIG1hbmlwdWxh dGluZyB0aGUKKwkgKiBsaW5lIGNvbnRyb2wuIExDUiB3aWxsIG5vdCBiZSBhZmZlY3RlZCB3aGVu IFVBUlQgaXMgYnVzeS4KKwkgKi8KKwl3aGlsZSAobnM4MjUwLT5idXN5X2RldGVjdCAhPSAwICYm CisJICAgICh1YXJ0X2dldHJlZyhiYXMsIERXX1JFR19VU1IpICYgVVNSX0JVU1kpICE9IDApCisJ CTsKIAllcnJvciA9IG5zODI1MF9wYXJhbShiYXMsIGJhdWRyYXRlLCBkYXRhYml0cywgc3RvcGJp dHMsIHBhcml0eSk7CiAJdWFydF91bmxvY2soc2MtPnNjX2h3bXR4KTsKIAlyZXR1cm4gKGVycm9y KTsKLS0gCjEuOC40Cgo= --001a11c366d052011d04e82c04a8-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 19:58:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C2C316BA; Mon, 7 Oct 2013 19:58:40 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 366952DD6; Mon, 7 Oct 2013 19:58:39 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBE81A.dip0.t-ipconnect.de [217.251.232.26]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r97JwUHR041530; Mon, 7 Oct 2013 19:58:31 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r97JwHIQ040925; Mon, 7 Oct 2013 21:58:17 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r97Jw56I096162; Mon, 7 Oct 2013 21:58:11 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310071958.r97Jw56I096162@fire.js.berklix.net> To: Gleb Kurtsou Subject: Re: Committing PEFS to CURRENT From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 07 Oct 2013 09:31:11 PDT." <20131007163111.GB1590@reks.swifttest.com> Date: Mon, 07 Oct 2013 21:58:05 +0200 Sender: jhs@berklix.com Cc: freebsd-current@freebsd.org, delphij@freebsd.org, Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 19:58:40 -0000 Hi Gleb & All Gleb Kurtsou wrote: > Hello, > > I would like to ask everybody's opinion regarding committing PEFS to > CURRENT. > > PEFS is a stacked cryptographic file system for FreeBSD. Development > started as Google Summer of Code project in 2009. It has been in ports > since Sept 2011. I maintain the project. > > Conceptually PEFS is similar to nullfs adding encryption layer on top of > it. But it differs technically by not using vop_bypass. Another popular > stacked cryptographic file systems include eCryptfs (linux) and encfs > (fuse). There is also pam_pefs pam module to allow user authentication > with their PEFS-encrypted home directory password. 2 others are also already in FreeBSD src/ (not just ports) gbde & geli. Whether moved from ports to src or not, either way, I sggest add to man section SEE ALSO gbde(8) & geli(8) Also, SEE ALSO of gbde & geli should probably ref ports/sysutils/pefs-kmod ft: Command not found. No pefs yet i SEE ALSO of http://www.freebsd.org/cgi/man.cgi?query=gbde&apropos=0&sektion=8&manpath=FreeBSD+9.2-RELEASE&arch=default&format=html http://www.freebsd.org/cgi/man.cgi?query=geli&apropos=0&sektion=8&manpath=FreeBSD+9.2-RELEASE&arch=default&format=html I suggest add an href inside: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html Even if just a 1 liner to start, to expand to a section later. (None there for 'pefs', I just searched) Personaly I've been using gbde based on top of a file inside a UFS for a long time, I can't remember why I chose gbde rather than geli, I guess because it was there first ? A dummy's guide short notes along the lines of "Which of these 3 should I use?" might also later be nice at the top of that web page :-) Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 19:59:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5382D7CB for ; Mon, 7 Oct 2013 19:59:01 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 311902DE5 for ; Mon, 7 Oct 2013 19:59:00 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 664741D106 for ; Mon, 7 Oct 2013 19:58:53 +0000 (UTC) Message-ID: <52531295.7090700@allanjude.com> Date: Mon, 07 Oct 2013 15:59:17 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 19:59:01 -0000 Devin Teske and I have been working on a big patch to bsdinstall to implement installing on a ZFS pool. It supports both GPT and MBR, the 4k sector gnop trick, and optional GELI encryption. We would like to commit this in time for 10.0-BETA1 so it needs some testing to work out any obvious bugs before we send it off to re@ to get it committed. It includes a single configuration menu that allows you to select all of the required details, including which drives to use (gets details from camcontrol, also includes an inspection utility that presents the detailed output of camcontrol inquiry/identify, and gpart show), what ZFS RAID level to use (taking in to consideration the selected number of drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. Additional, it includes some other changes to bsdinstall: 1. Change the default to the 'non-standard keyboard mapping' prompt to no 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 3. Remove the dialog asking if you wish to enable crash dumps, this feature has been combined into the regular 'services to enable' dialog and enabled by default You can browse the patches here: http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, available compressed (48 MB) or uncompressed (211 MB): http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso We look forward to your feedback -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 19:25:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 66C6D80A for ; Mon, 7 Oct 2013 19:25:29 +0000 (UTC) (envelope-from BSD@shaneware.biz) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:6]) by mx1.freebsd.org (Postfix) with ESMTP id F394F2BC9 for ; Mon, 7 Oct 2013 19:25:28 +0000 (UTC) Received: from ppp118-210-127-6.lns20.adl2.internode.on.net (HELO leader.local) ([118.210.127.6]) by ipmail06.adl2.internode.on.net with ESMTP; 08 Oct 2013 05:55:28 +1030 Message-ID: <52530AA5.7000304@ShaneWare.Biz> Date: Tue, 08 Oct 2013 05:55:25 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Continuous timeout messages from 10.0 alpha4 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 07 Oct 2013 20:09:11 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 19:25:29 -0000 Resending to current This is a regression between alpha2 and alpha4. I first setup a disk to boot 10 just after alpha2 was tagged. A few days ago I updated to alpha4 and started getting timeout messages, I have just built alpha5 r256098 and still get them. I just had 10 running for a few hours and 3 of the messages log archives which syslog rotates each hour due to size contain 3370 2508 and 3162 timeout messages over 3 hours uptime. each entry is similar to -- Oct 7 19:00:02 leader kernel: ahcich1: Timeout on slot 15 port 0 Oct 7 19:00:02 leader kernel: ahcich1: is 40000001 cs 00008000 ss 00000000 rs 00008000 tfd 2451 serr 00000000 cmd 00004f17 With slot x cycling from 0-31 but not always in sequence. MB is ASUS P8H61M LE/USB3 - corei5 - 8MB - nvidia GT520 ahci0: port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xfb305000-0xfb3057ff irq 20 at device 31.2 on pci0 ahci0: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported With the following connected to ahcich1 (LG blu-ray burner) cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device Most relevant dmesg info would be (full dmesg/logs available) -- ahci0: port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xfb305000-0xfb3057ff irq 20 at device 31.2 on pci0 ahci0: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ahciem0: on ahci0 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 3.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=0x1<4K> ada0: Previously was known as ad4 ada1 at ahcich4 bus 0 scbus2 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1: quirks=0x1<4K> ada1: Previously was known as ad8 ada2 at ahcich5 bus 0 scbus3 target 0 lun 0 ada2: ATA-6 SATA 2.x device ada2: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 512bytes) ada2: 76324MB (156312576 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad10 ses0 at ahciem0 bus 0 scbus4 target 0 lun 0 ses0: SEMB S-E-S 2.00 device ses0: SEMB SES Device From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:11:36 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 57146321; Mon, 7 Oct 2013 20:11:36 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 109292F11; Mon, 7 Oct 2013 20:11:36 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 7221882C4; Mon, 7 Oct 2013 20:11:34 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 7221882C4 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 7 Oct 2013 16:11:32 -0400 From: Glen Barber To: freebsd-current@FreeBSD.org, freebsd-snapshots@FreeBSD.org Subject: FreeBSD 10.0-ALPHA5 now available Message-ID: <20131007201132.GA3890@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Release Engineering Team X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:11:36 -0000 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The fifth ALPHA build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. The 10.0-ALPHA5 builds correlate to svn revision r256092 of the head/ branch. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.0/ (or any of the FreeBSD mirror sites). If you notice problems you can report them through the normal GNATS PR system or here on the -current mailing list. If you would like to use SVN to do a source based update of an existing system, use the "head/" branch. Please be aware that cvsup and CVS are not supported methods of updating the src/ tree. Important note to freebsd-update(8) users: freebsd-update(8) is not a supported upgrade path for the 10.0-ALPHA builds. Changes between -ALPHA4 and -ALPHA5 include: - Removal of BIND from the base system; replacements may be found within the Ports Collection. - Bug fix introduced with the latest infiniband update. - The GNU ar(1) and ranlib(1) have been removed from the base system. - Bug fixes and updates to the base llvm. - Various bhyve enhancements. - Various XEN enhancements. Checksums: amd64: SHA256 (FreeBSD-10.0-ALPHA5-amd64-bootonly.iso) = a77eefe1d8e14dc790573c6b942cd91cd5bd40f14d16b9e47696d50efa3f7b29 SHA256 (FreeBSD-10.0-ALPHA5-amd64-disc1.iso) = 4b93431f2d72a30e149cbb35cae365e90eb795bfb03186446984f6fa7a8ea167 SHA256 (FreeBSD-10.0-ALPHA5-amd64-memstick.img) = e8d168d68a6bae170238a9c07999d7d697ee1eba68704b4b5f30fadd4f955a8d MD5 (FreeBSD-10.0-ALPHA5-amd64-bootonly.iso) = 634f132e07922d8a09c338f5009034b8 MD5 (FreeBSD-10.0-ALPHA5-amd64-disc1.iso) = 42ae98b45bc74728e61653c8154024e6 MD5 (FreeBSD-10.0-ALPHA5-amd64-memstick.img) = be8c9ce57c26ca02b4628857f4377894 i386: SHA256 (FreeBSD-10.0-ALPHA5-i386-bootonly.iso) = 98ac167991c52cba1902905a6f0cd804361f3692396fb0ecd60060cfde8fb33c SHA256 (FreeBSD-10.0-ALPHA5-i386-disc1.iso) = 02d2cf027aae152bb4c70a32db1a7b3401733f7bd62cc4871aa6ada9405f16af SHA256 (FreeBSD-10.0-ALPHA5-i386-memstick.img) = f407616cce2ca9884014baf150ecbef48e6afc39e8ae04b49c42ca7b335c25e1 MD5 (FreeBSD-10.0-ALPHA5-i386-bootonly.iso) = 2df6f291e9d6e66bfe96b14523249f4a MD5 (FreeBSD-10.0-ALPHA5-i386-disc1.iso) = 999eb957675040629b2d02f851495977 MD5 (FreeBSD-10.0-ALPHA5-i386-memstick.img) = 2543707c92cf6cc3414b7492bb2e0727 ia64: SHA256 (FreeBSD-10.0-ALPHA5-ia64-bootonly.iso) = d24f816b8d87dbe5af8fe982fdeb4bb09badd81c61313dc420a513356a8c3a69 SHA256 (FreeBSD-10.0-ALPHA5-ia64-disc1.iso) = 302d23354f4046b8fe91266cac407f024d6a73ddd040c1181a37a07118fc130f SHA256 (FreeBSD-10.0-ALPHA5-ia64-memstick.img) = 0b8214d14a709ff3817a55968e8ae2c25f6e8b35ab96842d315ef786aa93ba13 MD5 (FreeBSD-10.0-ALPHA5-ia64-bootonly.iso) = 7a7f7c16202b6575943ce5e8f3fe9048 MD5 (FreeBSD-10.0-ALPHA5-ia64-disc1.iso) = 1e78b1c39773f4ee999c82074bad0d68 MD5 (FreeBSD-10.0-ALPHA5-ia64-memstick.img) = c8ec96004ddf8de5e62524dd074ee7a1 powerpc: SHA256 (FreeBSD-10.0-ALPHA5-powerpc-bootonly.iso) = 9ee848156256e46efc067295e7b2d6a95050dfee75e5917bfa1cbda25f950dd8 SHA256 (FreeBSD-10.0-ALPHA5-powerpc-disc1.iso) = cb6214a2691ba2d4090228d35abfc04d249b42b920e0d0081ae09b9dd5ee3f65 SHA256 (FreeBSD-10.0-ALPHA5-powerpc-memstick.img) = 1890435a15ad62893ab880af721d16aa7d70c8297cdbaf9c496dc9e6ee9b3b87 MD5 (FreeBSD-10.0-ALPHA5-powerpc-bootonly.iso) = 677a138a9cfa139e03f91c1a2150fa47 MD5 (FreeBSD-10.0-ALPHA5-powerpc-disc1.iso) = 9b5d07e41c8871ac1ab56f543a89ce8a MD5 (FreeBSD-10.0-ALPHA5-powerpc-memstick.img) = 1c9000b369fdc5dac54df43329f9a8d0 powerpc64: SHA256 (FreeBSD-10.0-ALPHA5-powerpc-powerpc64-bootonly.iso) = 2f6fcbdc1577e908511b98b631331489971fb3e7f0d3b6cdfb2be0b8b05898a1 SHA256 (FreeBSD-10.0-ALPHA5-powerpc-powerpc64-disc1.iso) = cf62b59fd58f40103d340cacb67e38facefb8006f6927e9b1ba319ac611668c9 SHA256 (FreeBSD-10.0-ALPHA5-powerpc-powerpc64-memstick.img) = 6f01baad645819d44a45130cf9f973b2cc99760cab82800ac1fda07881e0235e MD5 (FreeBSD-10.0-ALPHA5-powerpc-powerpc64-bootonly.iso) = 7e4d5996cf2c566724651454abaf08d3 MD5 (FreeBSD-10.0-ALPHA5-powerpc-powerpc64-disc1.iso) = a8b4c40f76b844761d3d84be11c0b517 MD5 (FreeBSD-10.0-ALPHA5-powerpc-powerpc64-memstick.img) = 95d412c35fcba1abb62fdef5f28d6e32 sparc64: SHA256 (FreeBSD-10.0-ALPHA5-sparc64-bootonly.iso) = 7fc48a5098948da7c9b89b6b496bd2942b30e9f4cfe21fe12b62401bdc9fc69a SHA256 (FreeBSD-10.0-ALPHA5-sparc64-disc1.iso) = 8bdaf1ea56e814bb2aba5953fb00ec95d9813dc1f63d83a274cab954a1435e93 MD5 (FreeBSD-10.0-ALPHA5-sparc64-bootonly.iso) = b81d78160fe7ee1092aca01833399ce1 MD5 (FreeBSD-10.0-ALPHA5-sparc64-disc1.iso) = df475bfba115e7c16a43a1832bd5d8a3 Glen --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSUxV0AAoJELls3eqvi17Q93MP/j9sp2iVNJ3VmBLPonuUDs0c 6gersMZ0SItJ6/9/aP8Sc81I+s7FX6//gi2kAoX3tF0/pblSeigxRqW8GdkW9Msl sqiFy2g8rFtGfOjWgKyioQdxFZ/igFy6bKedqYwjgziLdZ8jifu4n6FFVBjruBTp zuvKtnBUpH0pjyw7koowOPG4M9aO/cSSy2RVZzewTmdT5aKftu+g+4d4uff9pI6G MLOJLPNi2827KW70x76nRPbWArSbcdrxSo1Rd9YSVTXhyxFT+Md3MI9TEhzVVnHG WugJIxilnBlFwbl0+xfF2j2Oi6NvgbmKr0TSYf47xEuRePG/2fCtnCgYrqfaEd1l j251+y+AuFESbXEASBiockvhBcWqJDPmEjHb0ODFU0Uele5oEdh6fO65MbJvOonR 9nbnAzB9txZ+dX0KbCTshR1w3EXbThJ+B2gpjsqc2iPfY+2jJupizq/f3iK0pWaJ NVv0IqOwuTveVXwCjs0E+afjaX0oERAx8YH17gJ2wt3X7dA+gdW6c4nd/GkUH2ZG qcFI9YvFza4kKrm7BZzxozwrnHLTiAIjBHH7obz8tfALTbWqRisJNhyUUb3+cMl8 wtJO0Qtu1GCTQDkfgo95KMeoRho2hWPKaTIzQwYn9LxfgJmnQbY+PHxeq/YrMmHR EmbV6vYhrO7dySZ2MYe0 =rhI3 -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:15:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 714EF9EE; Mon, 7 Oct 2013 20:15:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x22c.google.com (mail-qe0-x22c.google.com [IPv6:2607:f8b0:400d:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F02642F5C; Mon, 7 Oct 2013 20:15:16 +0000 (UTC) Received: by mail-qe0-f44.google.com with SMTP id 6so2989873qeb.31 for ; Mon, 07 Oct 2013 13:15:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=GBi01RdvJa/jwavzBSnrAgiK0r5Pe0/Yd32ZEQ1tCaY=; b=EQ0J3ofsKVb1ZY3Ic6c+NjMShUYPzdNjIRcZCjac15iWxDdq9Jikldf+Ih0rJ3xJCX x07aPl+P6H8k3tcv2SGsFAIS+yF5PqOV6BuHe7YBmCYyJ2svUwNg8nt2zLRxRWgW95Mu AsKFvkawrDvx3UJ/qCpmEdNbeRQ++a5CSYhPH4ipC3KXuYE40Z9Gj0onnqcpjZpCZVts bJb5VvASZwtVhn5oUnIl8Cdio+KNy8rwDHoSwF+mULxy5jl9n7ourKYCEG9uQipR1Uvi YGGMK5qaTfJrVvjVUF068j9NxvsQfOIMxSjsPONb0+D8RvaMnb9kzEdvNxzkrKlF4AjA 1PMg== MIME-Version: 1.0 X-Received: by 10.224.157.14 with SMTP id z14mr5169015qaw.90.1381176916112; Mon, 07 Oct 2013 13:15:16 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 7 Oct 2013 13:15:16 -0700 (PDT) In-Reply-To: References: Date: Mon, 7 Oct 2013 13:15:16 -0700 X-Google-Sender-Auth: NNgCXYLGRSNjy6J5wKblc7oqS8I Message-ID: Subject: Re: Changes to UART ns8250 From: Adrian Chadd To: Zbigniew Bodek Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" , freebsd-current , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:15:17 -0000 Hi, You should add: * a loop counter, to break out after a while; * a DELAY(1) or something. -adrian On 7 October 2013 12:54, Zbigniew Bodek wrote: > Hello. > > I would like to present a patch for ns8250 serial that I would like to > commit in the near future (if there are no objections). > > The patch is fixing newest DesignWare UART with busy detection. > During frequency divisors configuration when UART is busy transferring or > receiving data, line control register manipulation will not take effect. > Therefore, we will not set divisor latch access bit and we will corrupt LCR > instead of configuring divisors. > It is necessary to wait until UART finishes all transfers to proceed with > the configuration. > > This was detected on Armada XP as UART fails on this issue 100/100 > attempts. > The patch was tested by kevlo@ and me and it works on our Armada XP - > based > systems. > > Please send your comment or remarks if there are any. > > Best regards > Zbigniew Bodek > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:17:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B6448DEE for ; Mon, 7 Oct 2013 20:17:59 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ve0-x236.google.com (mail-ve0-x236.google.com [IPv6:2607:f8b0:400c:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7682E2F9D for ; Mon, 7 Oct 2013 20:17:59 +0000 (UTC) Received: by mail-ve0-f182.google.com with SMTP id oy12so4091609veb.13 for ; Mon, 07 Oct 2013 13:17:58 -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=Z68pefEkzjabQ29Jc54bC1orC639ukK4B/2glTxsg8Q=; b=qdQd1adM9dVK0OivJ7GsL10Cw+5flzvX8Xdpbmi2aRbhN9V0c+AhuhOIU//2zRfv39 geE+gKrpDCwUzxD7mD7hBzTsDmiSUdq9Hj4dCHnp9CRDzr7r5BBIwlYW/6B/h0/4Je3h eexQH529uWIbN32GUpVQl/kFby3NXVG/QZeJjMn7pb0pKwrbKvUumhFj8Hkl+FwlkHTc O29kXD5Q0FgAhDmgJX1bzsG6BCUJRdI7t7N2iAk7clSyHkkoxmk+/O1gXqaKsvI0UJXi Uv3n36rc9DGJQeieyWsOkt71jF1DZFo3BuIhqcSOb5ibE3gLOOBA/NXDTpb5BzLFMQ2B dl4w== MIME-Version: 1.0 X-Received: by 10.52.64.143 with SMTP id o15mr23798052vds.16.1381177078551; Mon, 07 Oct 2013 13:17:58 -0700 (PDT) Received: by 10.220.65.4 with HTTP; Mon, 7 Oct 2013 13:17:58 -0700 (PDT) In-Reply-To: <52530AA5.7000304@ShaneWare.Biz> References: <52530AA5.7000304@ShaneWare.Biz> Date: Mon, 7 Oct 2013 16:17:58 -0400 Message-ID: Subject: Re: Continuous timeout messages from 10.0 alpha4 From: Mark Johnston To: Shane Ambler Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:17:59 -0000 Rebuilding sysutils/hal should fix this problem. It's been reported several times in the past week or two, and rebuilding this port fixed it for me when I ran into it. On Mon, Oct 7, 2013 at 3:25 PM, Shane Ambler wrote: > Resending to current > > This is a regression between alpha2 and alpha4. I first setup a disk to > boot 10 just after alpha2 was tagged. A few days ago I updated to > alpha4 and started getting timeout messages, I have just built alpha5 > r256098 and still get them. > > I just had 10 running for a few hours and 3 of the messages log archives > which syslog rotates each hour due to size contain 3370 2508 and 3162 > timeout messages over 3 hours uptime. > > each entry is similar to -- > Oct 7 19:00:02 leader kernel: ahcich1: Timeout on slot 15 port 0 > Oct 7 19:00:02 leader kernel: ahcich1: is 40000001 cs 00008000 ss > 00000000 rs 00008000 tfd 2451 serr 00000000 cmd 00004f17 > > With slot x cycling from 0-31 but not always in sequence. > > MB is ASUS P8H61M LE/USB3 - corei5 - 8MB - nvidia GT520 > > ahci0: port > 0xf070-0xf077,0xf060-0xf063,**0xf050-0xf057,0xf040-0xf043,**0xf020-0xf03f > mem 0xfb305000-0xfb3057ff irq 20 at device 31.2 on pci0 > ahci0: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported > > With the following connected to ahcich1 (LG blu-ray burner) > cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 > cd0: Removable CD-ROM SCSI-0 device > > > > Most relevant dmesg info would be (full dmesg/logs available) -- > > ahci0: port > 0xf070-0xf077,0xf060-0xf063,**0xf050-0xf057,0xf040-0xf043,**0xf020-0xf03f > mem 0xfb305000-0xfb3057ff irq 20 at device 31.2 on pci0 > ahci0: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported > ahcich0: at channel 0 on ahci0 > ahcich1: at channel 1 on ahci0 > ahcich4: at channel 4 on ahci0 > ahcich5: at channel 5 on ahci0 > ahciem0: on ahci0 > > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ATA-8 SATA 3.x device > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) > ada0: quirks=0x1<4K> > ada0: Previously was known as ad4 > ada1 at ahcich4 bus 0 scbus2 target 0 lun 0 > ada1: ATA-8 SATA 2.x device > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) > ada1: quirks=0x1<4K> > ada1: Previously was known as ad8 > ada2 at ahcich5 bus 0 scbus3 target 0 lun 0 > ada2: ATA-6 SATA 2.x device > ada2: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 512bytes) > ada2: 76324MB (156312576 512 byte sectors: 16H 63S/T 16383C) > ada2: Previously was known as ad10 > ses0 at ahciem0 bus 0 scbus4 target 0 lun 0 > ses0: SEMB S-E-S 2.00 device > ses0: SEMB SES Device > ______________________________**_________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@** > freebsd.org " > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:25:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B7BE812E for ; Mon, 7 Oct 2013 20:25:06 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-qe0-x236.google.com (mail-qe0-x236.google.com [IPv6:2607:f8b0:400d:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B9672059 for ; Mon, 7 Oct 2013 20:25:06 +0000 (UTC) Received: by mail-qe0-f54.google.com with SMTP id 1so1841449qec.41 for ; Mon, 07 Oct 2013 13:25:05 -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=kiWPEGg7cg72WuyE3rM5Oa1vtz1A/XOdGcSIzkmvSAg=; b=rhrXTkjnnwOEkPSzrh38SPEx/RpNb4lHTeSwzHMron6FS22GafCBqtVbC5u5k+91n5 1UOuXroFFLdIahXuX9orTf2QeYxs/DhPwo6bli0UM0kXWIsm8j+GMITAAa+5UHBZyQhJ mFwtO0O6SOaZeQNUeTBDGeijD2+WWEyrYRECcnupWd46Zu6l/4olSf5vP0Z1Rd98t3HI UR68uhMXHvXfSRLFvzpHyu0WIGTWm6t7hqAx9Jfypj5HLaQEXakYS9wEquFpW53WCjE0 nZEoGrNI693FeBd5BZ/yHQVkAABM5oU8POwtfT0QZShwNDM3lWSnjtIlmp413mfP6r7Y cXcw== MIME-Version: 1.0 X-Received: by 10.224.11.133 with SMTP id t5mr40212118qat.34.1381177505518; Mon, 07 Oct 2013 13:25:05 -0700 (PDT) Received: by 10.229.114.5 with HTTP; Mon, 7 Oct 2013 13:25:05 -0700 (PDT) In-Reply-To: <5252E6F6.80009@mail.lifanov.com> References: <20131007163111.GB1590@reks.swifttest.com> <5252E6F6.80009@mail.lifanov.com> Date: Mon, 7 Oct 2013 13:25:05 -0700 Message-ID: Subject: Re: Committing PEFS to CURRENT From: Gleb Kurtsou To: Nikolai Lifanov Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:25:06 -0000 On Mon, Oct 7, 2013 at 9:53 AM, Nikolai Lifanov wrote: > On 10/07/13 12:31, Gleb Kurtsou wrote: >> Hello, >> >> I would like to ask everybody's opinion regarding committing PEFS to >> CURRENT. >> >> PEFS is a stacked cryptographic file system for FreeBSD. Development >> started as Google Summer of Code project in 2009. It has been in ports >> since Sept 2011. I maintain the project. >> >> Conceptually PEFS is similar to nullfs adding encryption layer on top of >> it. But it differs technically by not using vop_bypass. Another popular >> stacked cryptographic file systems include eCryptfs (linux) and encfs >> (fuse). There is also pam_pefs pam module to allow user authentication >> with their PEFS-encrypted home directory password. >> >> For those interested in high level introduction I would highly recommend >> article by Kris Moore in the BSD Magazine Issue 09/2013(50) - >> http://bsdmag.org/magazine/1848-day-to-day-bsd-administration >> >> We are very close to branching 10-STABLE now, but patch is >> non-intrusive, it only adds new functionality, enabling PEFS for i386 >> and amd64 (platforms it's known to work on). Patch passes make universe. >> >> Patch is available here: >> https://github.com/glk/freebsd-head/commit/b4d2c4a5f42f88fdd07cb75feba3467e4d4c043c.patch >> >> Pros/cons: >> >> - Having PEFS in base would be a huge maintenance help for PCBSD/TrueOS >> who are already committed to use PEFS in next product releases, e.g. >> PCBSD provides encrypted home directories. >> >> - There is steady interest in the project from users (emails, etc). >> Many of them note that file system is not well known yet. Moving PEFS >> to base would greatly increase its exposure. >> >> - Committing PEFS to base would also simplify maintenance by keeping it >> in sync with other subsystems, e.g. it will be updated on large scale >> changes like VM locking. >> >> - There are no bugs known at the moment. I've been using it to encrypt >> home directory since day one. pho@ ran stress test suite on it a >> while back, number of bugs was fixed. >> >> - PEFS is known to work on amd64 and i386 only. Big endian system and >> systems with page size larger than 4k are not tested. >> >> - NOTE! There has been no cryptography review. I'd like to suggest to >> add warning about file system and crypto used is experimental and hasn't >> undergone professional review. Similar to one we had in tmpfs. >> >> >> BSD Magazine article: >> http://bsdmag.org/magazine/1848-day-to-day-bsd-administration >> >> Port: >> http://www.freshports.org/sysutils/pefs-kmod/ >> >> Source code repository: >> https://github.com/glk/pefs >> >> FreeBSD DevSummit'2011 - pefs presentation slides: >> https://pefs.googlecode.com/files/pefs-devsummit.pdf >> >> FreeBSD wiki page: >> https://wiki.freebsd.org/PEFS >> >> >> I would really appreciate any comments or suggestions. >> >> >> Thank you, >> Gleb. > > Just a personal note: I hoped that you would commit pefs to base > someday. It works well, and is the type of a core functionality that > would be nice to have as early as the install ISO, before skel is copied > over for the first user. I would be happy if this happened. > Agree. It would also be nice to have standard way to mount pefs file systems because they need to be mounted at later point during boot after other file systems mounted. Small rc.d script should do the trick. I think those issues should be addressed after PEFS is committed > - Nikolai Lifanov > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:26:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7C636255; Mon, 7 Oct 2013 20:26:24 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2B9122072; Mon, 7 Oct 2013 20:26:24 +0000 (UTC) Received: by mail-qe0-f47.google.com with SMTP id b10so161822qen.20 for ; Mon, 07 Oct 2013 13:26: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; bh=VVud3eu4SGBJi24KFebkmHRkPUgiLk/jMO4gOtJjbdY=; b=zqq59Gu2Iujbg3bJE/qv4vu4IeJK7ibO9AeCGU9x1CY35Jcb9K7blrc5Aki9tImy0M AyCwNwVmanMUjD0d+4vQPTQkLu7abO7uSVEPsa4zr1caWTcHrJJzn/AJV01jQjtokl/0 f8yzpk0aBBKl6UCnvWN84SDLoEaTXZk3Mvi5X21VISZoXDznqJeXZGY72PIFr5zsm7H+ QEkEHZw4oRFUCU2IIGjCQ6ouFaYyDNgRCetcyzj/gnzf14DIVAn2zqd8xkDlbkhTbc30 d4A3AXUfmu4dHKgzulJ5Jhw8Sno9vzlky3r/Lc6pknlm0Cu25hZI4xXn2U5pIPKoTwXU 4jCQ== MIME-Version: 1.0 X-Received: by 10.224.36.201 with SMTP id u9mr39231274qad.76.1381177583381; Mon, 07 Oct 2013 13:26:23 -0700 (PDT) Received: by 10.229.114.5 with HTTP; Mon, 7 Oct 2013 13:26:23 -0700 (PDT) In-Reply-To: <201310071958.r97Jw56I096162@fire.js.berklix.net> References: <20131007163111.GB1590@reks.swifttest.com> <201310071958.r97Jw56I096162@fire.js.berklix.net> Date: Mon, 7 Oct 2013 13:26:23 -0700 Message-ID: Subject: Re: Committing PEFS to CURRENT From: Gleb Kurtsou To: "Julian H. Stacey" Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:26:24 -0000 On Mon, Oct 7, 2013 at 12:58 PM, Julian H. Stacey wrote: > Hi Gleb & All > Gleb Kurtsou wrote: >> Hello, >> >> I would like to ask everybody's opinion regarding committing PEFS to >> CURRENT. >> >> PEFS is a stacked cryptographic file system for FreeBSD. Development >> started as Google Summer of Code project in 2009. It has been in ports >> since Sept 2011. I maintain the project. >> >> Conceptually PEFS is similar to nullfs adding encryption layer on top of >> it. But it differs technically by not using vop_bypass. Another popular >> stacked cryptographic file systems include eCryptfs (linux) and encfs >> (fuse). There is also pam_pefs pam module to allow user authentication >> with their PEFS-encrypted home directory password. > > 2 others are also already in FreeBSD src/ (not just ports) gbde & geli. geli and gbde are different concept, they provide encrypted block level devices. PEFS transparently encrypts data on existing file system. Here is what you can do with PEFS: % mkdir ~/Private % pefs mount ~/Private ~/Private % pefs addkey ~/Private % echo "Hello WORLD" > ~/Private/test % ls -Al ~/Private total 1 -rw-r--r-- 1 gleb gleb 12 Oct 1 12:55 test % cat ~/Private/test Hello WORLD % pefs unmount ~/Private % ls -Al ~/Private total 1 -rw-r--r-- 1 gleb gleb 12 Oct 1 12:55 .DU6eudxZGtO8Ry_2Z3Sl+tq2hV3O75jq % hd ~/Private/.DU6eudxZGtO8Ry_2Z3Sl+tq2hV3O75jq 00000000 7f 1e 1b 05 fc 8a 5c 38 fc d8 2d 5f |......\8..-_| 0000000c Take a look a great article in the BSD Magazine or http://glebkurtsou.blogspot.com/2009/10/encrypting-private-directory-with-pefs.html > Whether moved from ports to src or not, either way, > I sggest add to man section SEE ALSO gbde(8) & geli(8) Good point, thanks. > Also, SEE ALSO of gbde & geli should probably ref ports/sysutils/pefs-kmod > ft: Command not found. > > No pefs yet i SEE ALSO of > http://www.freebsd.org/cgi/man.cgi?query=gbde&apropos=0&sektion=8&manpath=FreeBSD+9.2-RELEASE&arch=default&format=html > http://www.freebsd.org/cgi/man.cgi?query=geli&apropos=0&sektion=8&manpath=FreeBSD+9.2-RELEASE&arch=default&format=html > > I suggest add an href inside: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html > Even if just a 1 liner to start, to expand to a section later. > (None there for 'pefs', I just searched) > > Personaly I've been using gbde based on top of a file inside a UFS > for a long time, I can't remember why I chose gbde rather than geli, > I guess because it was there first ? > > A dummy's guide short notes along the lines of "Which of these 3 should I use?" > might also later be nice at the top of that web page :-) > There is no answer for the question, each system does it's own thing and does it differently: * With PEFS backups are much easier: - Use regular backup software for backing up encrypted data (lower level file system), that would allow delta backup only. - Create file system snapshots, e.g. zfs, then zfs send/receive, regardless whether file system is encrypted or not. * Setting up multiple encrypted file system is much easier -- no need to preallocate storage and create file system. * With PEFS it's possible to add key to encrypted home directory during login (pam_pefs). * PEFS let's you use multiple key in same file system. Thanks, Gleb. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:26:34 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4E109362; Mon, 7 Oct 2013 20:26:34 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 21C04207A; Mon, 7 Oct 2013 20:26:33 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VTHNr-000457-0O; Mon, 07 Oct 2013 20:26:27 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r97KQNcE017584; Mon, 7 Oct 2013 14:26:23 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+SL+29gBFrnv96HWTdirAU Subject: Re: Changes to UART ns8250 From: Ian Lepore To: Adrian Chadd In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Mon, 07 Oct 2013 14:26:23 -0600 Message-ID: <1381177583.1130.17.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Zbigniew Bodek , "freebsd-arm@freebsd.org" , freebsd-current , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:26:34 -0000 On Mon, 2013-10-07 at 13:15 -0700, Adrian Chadd wrote: > Hi, > > You should add: > > *[snip] > * a DELAY(1) or something. > Why? Why oh why do people write while (!read_some_status_register()) DELAY(n); when DELAY() is implemented as, roughly: while (read_some_counter_register() < something) continue; The whole point of DELAY() is to busy-wait. What might be nice is some function that we can call in such a loop such as cpu_busywait(), so that when running in an emulated or virtualized environment the emulator or hypervisor could use that as a hint to do something smart. -- Ian From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:28:43 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E3CBC4EB; Mon, 7 Oct 2013 20:28:43 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B85F1209B; Mon, 7 Oct 2013 20:28:43 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 877178444; Mon, 7 Oct 2013 20:28:42 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 877178444 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 7 Oct 2013 16:28:41 -0400 From: Glen Barber To: freebsd-current@FreeBSD.org, freebsd-snapshots@FreeBSD.org Subject: FreeBSD 10.0-ALPHA5 Virtual Machine Images Available Message-ID: <20131007202841.GB3890@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jq0ap7NbKX2Kqbes" Content-Disposition: inline X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Release Engineering Team X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:28:44 -0000 --jq0ap7NbKX2Kqbes Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In somewhat of a followup to the 10.0-ALPHA5 announcement... Preinstalled virtual machine images for 10.0-ALPHA5 are now available for amd64 and i386 architectures. The images are located under the 'snapshots' directory on FTP, here: http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/Latest/10.0-ALPHA5/ Checksums for the images follow at the end of this email. The disk images are available in both QCOW2 and VMDK format. The image download size is approximagely 136 MB, which decompress to a 10GB sparse image. The partition layout is: - 512k - freebsd-boot GPT partition type (bootfs GPT label) - 1GB - freebsd-swap GPT partition type (swapfs GPT label) - ~8GB - freebsd-ufs GPT partition type (rootfs UFS label) Checksums: amd64: SHA256 (FreeBSD-10.0-ALPHA5-amd64.qcow2.xz) = 3ede8c876096fc223b88170210a1a3cac94bc07a6fe0d9b8ee83aac9b807b166 SHA256 (FreeBSD-10.0-ALPHA5-amd64.vmdk.xz) = 6cdc1d1643975deaf15b4113880d31a75b50856774166fe77e99c08cf804e768 MD5 (FreeBSD-10.0-ALPHA5-amd64.qcow2.xz) = a74be7f2b1e88609da1504fd69def40d MD5 (FreeBSD-10.0-ALPHA5-amd64.vmdk.xz) = 1e42d54eb64fef95f0a4ab00b8f58e90 i386: SHA256 (FreeBSD-10.0-ALPHA5-i386.qcow2.xz) = a5f93578a79ce0092275158158d8ae5166f03046cdd54e105a08f0caf5d8ef9c SHA256 (FreeBSD-10.0-ALPHA5-i386.vmdk.xz) = e8d7046d067a3e97eb5b597e6f02154bc45194db25560d2d6a566dbbb9128847 MD5 (FreeBSD-10.0-ALPHA5-i386.qcow2.xz) = 7ec0caec7aace8c135803d4aee0691ad MD5 (FreeBSD-10.0-ALPHA5-i386.vmdk.xz) = 765162922909c044d74d5dcfc30bda26 Glen --jq0ap7NbKX2Kqbes Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSUxl5AAoJELls3eqvi17QM7EP/0tQdlrUwPb2u8QrQV9dxD3I F5TzOiGZHtzpLnz7kPIwM4RhSuN74/bbyxMES1n3G1sq8w7I562JfRQxkacI3ImH KS3BOMRbK2Yg7l9jzjMR6/HAOe2JLTjn7JwFnI6T/bxldVAV+FP6Q2KQADkrtWI4 Nrfby2QcSx3UrqW4xkFhP1Kdn4QGze/vMZ3nJWdjlweodxBuzadAtzuFVN//Lyfg 9C4BeVqVyC3JEejf8kyhvnTzIKO53IiOlqpZoNUCDS6oATcvvifc4scbzMF10sUF vXoSU1mTE0Ie3wOueaotN1n3hge/YkrmtA/NN360RA1nJ5Xx2pe+RH0a5MzlCQoq hU3IIzFAmZUjzUr/ayIwTEQXQg7aHAqCeoZKN655Wx7HR9+7zjI/qK27dkr8RUi9 XqUN/OgY36mOKlGpHa9fwp4HBlS1fCfHcFwnvLwboK5eh6Wok5XmYoEa+JPGARrL 1FfiBdVFQ9MqXKWqKOpYnmt6uHdDckEHlFJff/RpOtv4o5cxjEgA1rsaOldz06C0 BWePyGoa1NT9igkasTC1S5H8mLIGbABCC9rLY4uM9GFs0kEkaH+f2+KvsJUh/WC9 qus1FHK+C7bQcyVyVNI801vJZExlTO/5aEjQQmwlQ+A/qeKYvLaF/w1c/RP7XpJt 0V3t8hV99gdVoXEYS2jF =Qm4s -----END PGP SIGNATURE----- --jq0ap7NbKX2Kqbes-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:34:34 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 31D0E93E for ; Mon, 7 Oct 2013 20:34:34 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D7BE52114 for ; Mon, 7 Oct 2013 20:34:33 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r97KYWvk091624; Mon, 7 Oct 2013 14:34:32 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r97KYWk9091621; Mon, 7 Oct 2013 14:34:32 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 7 Oct 2013 14:34:32 -0600 (MDT) From: Warren Block To: Kevin Oberman Subject: Re: X related ports not finding version strings and hanging In-Reply-To: Message-ID: References: <1381098538.1683.1.camel@localhost> <1381099002.1683.2.camel@localhost> <20131006232913.GA50021@troutmask.apl.washington.edu> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) 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]); Mon, 07 Oct 2013 14:34:32 -0600 (MDT) Cc: "freebsd-current@freebsd.org" , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:34:34 -0000 On Sun, 6 Oct 2013, Kevin Oberman wrote: > As usual with such upgrades, pkg_libchk is your friend. Assuming you have > updated pixman: > portmaster graphics/libGL graphics/dri > pkg_libchk -o | grep pixman | cut -d: -f1 | sort | uniq > pixman-files.txt > portmaster =D `cat pixman-files.txt` > portmaster -aD > portmaster -y -clean-distfiles pkg_libchk -q > /tmp/to-be-rebuilt.txt portmaster `cat /tmp/to-be-rebuilt.txt` worked for me, although I did it after following the pixman instructions in /usr/ports/UPDATING. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:35:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4AA1A53; Mon, 7 Oct 2013 20:35:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x229.google.com (mail-qe0-x229.google.com [IPv6:2607:f8b0:400d:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4D9A72125; Mon, 7 Oct 2013 20:35:17 +0000 (UTC) Received: by mail-qe0-f41.google.com with SMTP id 1so5886348qee.28 for ; Mon, 07 Oct 2013 13:35:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=C0bVkeqCeSIkBzP0hQRakNb4vw/Kr+rxE1as5CfGiOc=; b=r56pKS6hicCewTo1XG904txIP9Pt1WNzvJlFRnFliYTSWEOZ0lpEfHzTD7fL20uld9 qqmwkeoK+t7a5yKtqybYEXAXhRPPjJT1cJ+pqniMRh9OHzdCz8HnzyZpUwA9x2IRvk4B vKwsxi9GaQIer1ib88HQFdS7Lm0mH2C+Od7fqQTXaiTxH2D6na7YU0gKOwPMxPUmayOE B0YkrgUMf8P/TkbLSGgkWfaUFxnnzHIMp63028LNRkbs/7yc36CASrbchz1fyF9uyf4j FDSGUyVrTe4/azmGoHP+QdcgnUlgADWv9mbOlNkF6HJTqUjT+/USJwk+UlVe1QonkYp5 1dBw== MIME-Version: 1.0 X-Received: by 10.224.114.201 with SMTP id f9mr40013910qaq.4.1381178116392; Mon, 07 Oct 2013 13:35:16 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Mon, 7 Oct 2013 13:35:16 -0700 (PDT) In-Reply-To: <1381177583.1130.17.camel@revolution.hippie.lan> References: <1381177583.1130.17.camel@revolution.hippie.lan> Date: Mon, 7 Oct 2013 13:35:16 -0700 X-Google-Sender-Auth: KqZl9pJp_NdYLenJ5mi2a7PL3GM Message-ID: Subject: Re: Changes to UART ns8250 From: Adrian Chadd To: Ian Lepore Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Zbigniew Bodek , "freebsd-arm@freebsd.org" , freebsd-current , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:35:18 -0000 I'd love to see a linux style way of saying "I'd like to sleep from roughly this time interval to this time interval; feel free to do what you need." Then yes, it could be implemented as a sleep wakeup from a timer, or as a call to a hypervisor to do the same, or .. or... -adrian On 7 October 2013 13:26, Ian Lepore wrote: > On Mon, 2013-10-07 at 13:15 -0700, Adrian Chadd wrote: > > Hi, > > > > You should add: > > > > *[snip] > > * a DELAY(1) or something. > > > > Why? Why oh why do people write > > while (!read_some_status_register()) > DELAY(n); > > when DELAY() is implemented as, roughly: > > while (read_some_counter_register() < something) > continue; > > The whole point of DELAY() is to busy-wait. > > What might be nice is some function that we can call in such a loop such > as cpu_busywait(), so that when running in an emulated or virtualized > environment the emulator or hypervisor could use that as a hint to do > something smart. > > -- Ian > > > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:35:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 43EB7BC5 for ; Mon, 7 Oct 2013 20:35:35 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D65422137 for ; Mon, 7 Oct 2013 20:35:34 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id f12so7634723wgh.26 for ; Mon, 07 Oct 2013 13:35:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=dty5i3wPoHKh6cfAGjiUFcQ+mxTMF81bPviNxh1dLPM=; b=JiRoOTFg8ZeP+a8+lZfLoUOLlucH+YLfd5IrKfT9ZggooJdV6MutC58WalVlJV95+F mDTF8ZN7SzwZK41Mb6pV5idnAREA7YnJL2Xabm//vhGNsbVp0XcpcsatUtRdEObnzjXw iYTDqYiHY46q6NSrIi0n88Sjky5KvzvZTarzFp1xJjKELXRD9b6SiBttmZKiu3xDGW0/ KzwKS0MKpNcC5ibLrgqWQuT7Dv6wRStpxQBpJdN4Eg52TqGBJSrETf9nNzTECksyV+Ft CyftKvaNhAR426kGpelHbsnGwlkCFAQoKmKnJ8aG/kuWCKc2Sq4FEL4deWIC3GebSMoz v37A== X-Received: by 10.180.189.205 with SMTP id gk13mr20441140wic.12.1381178133285; Mon, 07 Oct 2013 13:35:33 -0700 (PDT) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.194.236.131 with HTTP; Mon, 7 Oct 2013 13:35:13 -0700 (PDT) In-Reply-To: References: From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Date: Mon, 7 Oct 2013 22:35:13 +0200 X-Google-Sender-Auth: 7x1jv9ZvxUFDZfYRQzdiib8NHn4 Message-ID: Subject: Re: unionfs related panic on 10.0-ALPHA4 To: "freebsd-current@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:35:35 -0000 I've just have another crash related to mount_unionfs but on sparc64 arch this time ( 10.0-ALPHA4 #2 r255947). Still no core dump: panic: vm_fault: fault on nofault entry, addr: 1c05f2000 cpuid = 0 KDB: stack backtrace: panic() at panic+0x1d4 vm_fault_hold() at vm_fault_hold+0x174 vm_fault() at vm_fault+0x88 trap_pfault() at trap_pfault+0x2e4 trap() at trap+0x308 -- fast instruction access mmu miss tar=0x1c05f2000 %o7=0x17ae23b4c -- _end() at 0x1c05f21a0 vfs_donmount() at vfs_donmount+0x1958 sys_nmount() at sys_nmount+0x78 syscall() at syscall+0x320 -- syscall (378, FreeBSD ELF64, sys_nmount) %o7=0x10141c -- userland() at 0x4047f968 user trace: trap %o7=0x10141c pc 0x4047f968, sp 0x7fdffffcff1 pc 0x100e24, sp 0x7fdffffda01 pc 0x402058f4, sp 0x7fdffffdac1 done KDB: enter: panic [ thread pid 73492 tid 100396 ] Stopped at kdb_enter+0x80: ta %xcc, 1 db> show thread Thread 100396 at 0xfffff80005598920: proc (pid 73492): 0xfffff8000591c4b0 name: mount_unionfs stack: 0xed2aa000-0xed2b1fff flags: 0x4 pflags: 0 state: RUNNING (CPU 0) priority: 152 container lock: sched lock 0 (0xc0c4a800) db> show all trace Tracing command mount_unionfs pid 73492 tid 100396 td 0xfffff80005598920 panic() at panic+0x218 vm_fault_hold() at vm_fault_hold+0x174 vm_fault() at vm_fault+0x88 trap_pfault() at trap_pfault+0x2e4 trap() at trap+0x308 -- fast instruction access mmu miss tar=0x1c05f2000 %o7=0x17ae23b4c -- _end() at 0x1c05f21a0 vfs_donmount() at vfs_donmount+0x1958 sys_nmount() at sys_nmount+0x78 syscall() at syscall+0x320 -- syscall (378, FreeBSD ELF64, sys_nmount) %o7=0x10141c -- userland() at 0x4047f968 user trace: trap %o7=0x10141c pc 0x4047f968, sp 0x7fdffffcff1 pc 0x100e24, sp 0x7fdffffda01 pc 0x402058f4, sp 0x7fdffffdac1 done ... From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:36:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4EFAECD9; Mon, 7 Oct 2013 20:36:19 +0000 (UTC) (envelope-from zbodek@gmail.com) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 61A242147; Mon, 7 Oct 2013 20:36:18 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id c11so7890971wgh.30 for ; Mon, 07 Oct 2013 13:36:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=FlVYaZZeloUadN3cx21BoJN+DCt5HL06Hb6/609+ZF0=; b=09dRTNBY66t4wKCEi1AVSB2jlEz1lSd5pkQ3TG0zTRzSvJdOjWEOS8X3sOrggJgLcg r4Ab1G4aDFzZOR0ZGh6gUvXu9+szEUqO7YSOBtPpiVVUyTxP5RAYNDnv4TndhilJLfmN xtVgRrIzUYs6uyR6mtiCPa2l7reOtTH1c1jsCo2UF1pRmnQrj48vIuHxauzuqk/ALFj6 +diljGJAvPRrp/fNHTUpKbGdM/PLbeeIFoOOgDtkp8GiS1P5XYxIFSKHbBiIX88hAnnN C0gYxiwBPGLXvaxYfjnMO26cpS+rk3jHtBneu0a+CjUxapTNuSR0Qu3Ko1oby+Lv3uWm 6U6g== MIME-Version: 1.0 X-Received: by 10.194.63.228 with SMTP id j4mr7512079wjs.34.1381178176735; Mon, 07 Oct 2013 13:36:16 -0700 (PDT) Sender: zbodek@gmail.com Received: by 10.216.160.70 with HTTP; Mon, 7 Oct 2013 13:36:16 -0700 (PDT) In-Reply-To: References: Date: Mon, 7 Oct 2013 22:36:16 +0200 X-Google-Sender-Auth: uyj11NzTjbvpMumKmM39MjLoboc Message-ID: Subject: Re: Changes to UART ns8250 From: Zbigniew Bodek To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" , freebsd-current , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:36:19 -0000 Hello Adrian, Thank you for your remarks. Please check my answers in-line. Best regards Zbigniew Bodek 2013/10/7 Adrian Chadd > Hi, > > You should add: > > * a loop counter, to break out after a while; > [ZBB] In general as long as UART is busy we cannot proceed but if the timeout occurs we could return an error. Do you agree? > * a DELAY(1) or something. > [ZBB] DELAY is also a busy wait after all. The reasonable solution might be to use ns8250_delay() to get the transmission time and use it for timeout from the first point. I would DELAY(1) in each loop and decrement value acquired from ns8250_delay(). The loop should break during that time or we return an error. What do you think? > > > > -adrian > > > > On 7 October 2013 12:54, Zbigniew Bodek wrote: > >> Hello. >> >> I would like to present a patch for ns8250 serial that I would like to >> commit in the near future (if there are no objections). >> >> The patch is fixing newest DesignWare UART with busy detection. >> During frequency divisors configuration when UART is busy transferring or >> receiving data, line control register manipulation will not take effect. >> Therefore, we will not set divisor latch access bit and we will corrupt >> LCR >> instead of configuring divisors. >> It is necessary to wait until UART finishes all transfers to proceed with >> the configuration. >> >> This was detected on Armada XP as UART fails on this issue 100/100 >> attempts. >> The patch was tested by kevlo@ and me and it works on our Armada XP - >> based >> systems. >> >> Please send your comment or remarks if there are any. >> >> Best regards >> Zbigniew Bodek >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> > > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:43:39 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EE50DF5E for ; Mon, 7 Oct 2013 20:43:39 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 87C1721BD for ; Mon, 7 Oct 2013 20:43:38 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r97KhZSn091807; Mon, 7 Oct 2013 14:43:35 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r97KhZQr091804; Mon, 7 Oct 2013 14:43:35 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 7 Oct 2013 14:43:35 -0600 (MDT) From: Warren Block To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI In-Reply-To: <52531295.7090700@allanjude.com> Message-ID: References: <52531295.7090700@allanjude.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 07 Oct 2013 14:43:35 -0600 (MDT) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:43:40 -0000 On Mon, 7 Oct 2013, Allan Jude wrote: > Additional, it includes some other changes to bsdinstall: > 1. Change the default to the 'non-standard keyboard mapping' prompt to no Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 . From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:52:11 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6C06753A for ; Mon, 7 Oct 2013 20:52:11 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 39A9A226B for ; Mon, 7 Oct 2013 20:52:11 +0000 (UTC) Received: by mail-oa0-f44.google.com with SMTP id l10so6748547oag.31 for ; Mon, 07 Oct 2013 13:52:10 -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=bRqW/daQtllfH/4h+K21uf/6QrmYkWumS35HqkWIL1Y=; b=FkCyH2vSm6PNij1+lK4+/eGVVE+GbFTJ0WwOAZ9ATKzPYw27QQBaeOhrW0N7V10lNX nStxi36xxfKYHuH8tGIBHXBRxmzp0grdj+BxwRnZZqRNavB2Oh7g8vqFssas/ig3PkC2 SpM1HYjsop7UyEo2+SQsI+pEQ48LqVjJNsaxDM9butUlOsPlk1zoJYCkvfJVuNulL4Rq oEgSGp23IkjfflPe5Zclh8jrDVR7bvo7N/+onLRP2z/GNHqNc1WggtKrbZqwW+q/dVb4 +pcKlx4Y+PvoFaB00NTMJkuG6jEYA0v5mPzGe+1kB6pKtZhlmDUNbP/OesiDZW4V585T Bl7g== MIME-Version: 1.0 X-Received: by 10.60.70.209 with SMTP id o17mr79003oeu.65.1381179130452; Mon, 07 Oct 2013 13:52:10 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Mon, 7 Oct 2013 13:52:10 -0700 (PDT) Date: Mon, 7 Oct 2013 16:52:10 -0400 Message-ID: Subject: CURRENT BUILD FAILURE sys/modules/cxgbe From: Outback Dingo To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:52:11 -0000 cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -c /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:228:12: error: use of undeclared identifier 'cpu_clflush_line_size' pad = max(cpu_clflush_line_size, 16); ^ /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:273:9: error: use of undeclared identifier 'cpu_clflush_line_size' len = cpu_clflush_line_size > 64 ? 128 : 64; ^ 2 errors generated. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:54:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 29E0970A for ; Mon, 7 Oct 2013 20:54:25 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 0615222AC for ; Mon, 7 Oct 2013 20:54:24 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 5C5B81D2B9 for ; Mon, 7 Oct 2013 20:54:23 +0000 (UTC) Message-ID: <52531F95.6050002@allanjude.com> Date: Mon, 07 Oct 2013 16:54:45 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:54:25 -0000 On 2013-10-07 16:43, Warren Block wrote: > On Mon, 7 Oct 2013, Allan Jude wrote: > >> Additional, it includes some other changes to bsdinstall: >> 1. Change the default to the 'non-standard keyboard mapping' prompt >> to no > > Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 . > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" That is a good idea, I'll add that I've also hit this: http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html and plan to throw in a fix for that. Which makes more sense, blindly 'killall dhclient' before we try to acquire a new lease, or detect that dhclient is running and try to use the IP that has already been assigned? -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 20:56:35 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 078A0917; Mon, 7 Oct 2013 20:56:35 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CC08B22CC; Mon, 7 Oct 2013 20:56:34 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VTHqu-000Bea-BJ; Mon, 07 Oct 2013 20:56:28 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r97KuPpa017656; Mon, 7 Oct 2013 14:56:25 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19BSbxbcp5aiKIGKTOX+AWR Subject: Re: Changes to UART ns8250 From: Ian Lepore To: Zbigniew Bodek In-Reply-To: References: Content-Type: multipart/mixed; boundary="=-Kqv6EfxlCQV1TR9DVG7S" Date: Mon, 07 Oct 2013 14:56:25 -0600 Message-ID: <1381179385.1130.18.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: Adrian Chadd , freebsd-current , "freebsd-arm@freebsd.org" , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 20:56:35 -0000 --=-Kqv6EfxlCQV1TR9DVG7S Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Mon, 2013-10-07 at 22:36 +0200, Zbigniew Bodek wrote: > Hello Adrian, > > Thank you for your remarks. > Please check my answers in-line. > > Best regards > Zbigniew Bodek > > > 2013/10/7 Adrian Chadd > > > Hi, > > > > You should add: > > > > * a loop counter, to break out after a while; > > > [ZBB] In general as long as UART is busy we cannot proceed but if the > timeout occurs we could return an error. Do you agree? > > > * a DELAY(1) or something. > > > [ZBB] DELAY is also a busy wait after all. The reasonable solution might be > to use ns8250_delay() to get the transmission time and use it for timeout > from the first point. I would DELAY(1) in each loop and decrement value > acquired from ns8250_delay(). The loop should break during that time or we > return an error. What do you think? > Is it possible to not busy-wait at all? Something like the attached? -- Ian --=-Kqv6EfxlCQV1TR9DVG7S Content-Disposition: inline; filename="temp.diff" Content-Type: text/x-patch; name="temp.diff"; charset="us-ascii" Content-Transfer-Encoding: 7bit Index: sys/dev/uart/uart_dev_ns8250.c =================================================================== --- sys/dev/uart/uart_dev_ns8250.c (revision 255916) +++ sys/dev/uart/uart_dev_ns8250.c (working copy) @@ -614,6 +614,7 @@ ns8250_bus_ipend(struct uart_softc *sc) if (ns8250->busy_detect && (iir & IIR_BUSY) == IIR_BUSY) { (void)uart_getreg(bas, DW_REG_USR); + wakeup(&ns8250->busy_detect); uart_unlock(sc->sc_hwmtx); return (0); } @@ -652,6 +653,16 @@ ns8250_bus_param(struct uart_softc *sc, int baudra bas = &sc->sc_bas; uart_lock(sc->sc_hwmtx); + /* + * When using DW UART with BUSY detection it is necessary to wait + * until all serial transfers are finished before manipulating the + * line control. LCR will not be affected when UART is busy. + */ + while (ns8250->busy_detect && + (uart_getreg(bas, DW_REG_USR) & USR_BUSY) == 0) { + msleep(&ns8250->busy_detect, sc->sc_hwmtx, "dwbusy", 10); + } + error = ns8250_param(bas, baudrate, databits, stopbits, parity); uart_unlock(sc->sc_hwmtx); return (error); --=-Kqv6EfxlCQV1TR9DVG7S-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:00:14 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DBFF0CA4 for ; Mon, 7 Oct 2013 21:00:14 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B2644232E for ; Mon, 7 Oct 2013 21:00:14 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VTHuX-00029b-OS; Mon, 07 Oct 2013 21:00:13 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r97L0BDL017671; Mon, 7 Oct 2013 15:00:11 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18Ib8WILCnBXpj8yBXpIj4m Subject: Re: CURRENT BUILD FAILURE sys/modules/cxgbe From: Ian Lepore To: Outback Dingo In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Mon, 07 Oct 2013 15:00:11 -0600 Message-ID: <1381179611.1130.19.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:00:14 -0000 On Mon, 2013-10-07 at 16:52 -0400, Outback Dingo wrote: > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc > -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe > -DHAVE_KERNEL_OPTION_HEADERS -include > /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq > -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer > -I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mcmodel=kernel > -mno-red-zone -mno-mmx -mno-sse -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector > -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs > -fdiagnostics-show-option -Wno-error-tautological-compare > -Wno-error-empty-body -Wno-error-parentheses-equality -c > /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c > /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:228:12: > error: use of undeclared identifier 'cpu_clflush_line_size' > pad = max(cpu_clflush_line_size, 16); > ^ > /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:273:9: > error: use of undeclared identifier 'cpu_clflush_line_size' > len = cpu_clflush_line_size > 64 ? 128 : 64; > ^ > 2 errors generated. Fixed in r256118. -- Ian From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:00:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F3F91DB8 for ; Mon, 7 Oct 2013 21:00:45 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BE8FA2343 for ; Mon, 7 Oct 2013 21:00:45 +0000 (UTC) Received: by mail-oa0-f42.google.com with SMTP id g12so6918764oah.29 for ; Mon, 07 Oct 2013 14:00:45 -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=wGKzXT23fAwOlUfUTIUtcxdf4Rmpt+v/mx2/yAPM7tA=; b=SDocjtd1d3XOd0BjBYTZR47McPbVJ9+djdCPaGojXsglxFc0c3mPG5je+3vN4v7J0v kFjfw0u9t9KS3R+anm18yhs8H7/SKU9exU7iRASyyYmLEudgWo3XiJ4xrc9YZ5lbabO+ FJt9cmL6UL/deNK/cdb1iPcY7efZcoWJXqbs8iDHjX3Y0sN8KhlrPTkF/NBFOHKZkNJ0 Sjtv1DdASMvxR0yqNNptA2JbXS7cMwze6zkU4IEa9pNr1VW4+1gWOHzaIjpsYj3sI4Kn NQXby3DcBcLG21lIXJ0x9XGmFs9khO6ExSXdSHfwJve5s9Fug9w8uwACoY5kbXtN3iu+ CISg== MIME-Version: 1.0 X-Received: by 10.60.63.9 with SMTP id c9mr5289492oes.35.1381179645116; Mon, 07 Oct 2013 14:00:45 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Mon, 7 Oct 2013 14:00:45 -0700 (PDT) In-Reply-To: <52531F95.6050002@allanjude.com> References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> Date: Mon, 7 Oct 2013 17:00:45 -0400 Message-ID: Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI From: Outback Dingo To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:00:46 -0000 On Mon, Oct 7, 2013 at 4:54 PM, Allan Jude wrote: > On 2013-10-07 16:43, Warren Block wrote: > > On Mon, 7 Oct 2013, Allan Jude wrote: > > > >> Additional, it includes some other changes to bsdinstall: > >> 1. Change the default to the 'non-standard keyboard mapping' prompt > >> to no > > > > Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 . > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" > That is a good idea, I'll add that > > I've also hit this: > > http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html > and plan to throw in a fix for that. > Which makes more sense, blindly 'killall dhclient' before we try to > acquire a new lease, or detect that dhclient is running and try to use > the IP that has already been assigned? > > > jeeeeeez after i just updated and patched my source tree to do a build, you go and fix things :P anyway you can just generate a master diff against the tree that we can apply, seems not ive to revert the patches and reapply all the newest ones. > > -- > Allan Jude > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:02:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1F075FDB for ; Mon, 7 Oct 2013 21:02:58 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BDFC9236F for ; Mon, 7 Oct 2013 21:02:57 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r97L2sCu024825 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 7 Oct 2013 14:02:56 -0700 (PDT) (envelope-from lyndon@orthanc.ca) From: Lyndon Nerenberg Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: rcs is gone? Message-Id: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> Date: Mon, 7 Oct 2013 14:02:50 -0700 To: "freebsd-current@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:02:58 -0000 I know I am a certified crank, but ... why? This is some of the = simplest code on the planet. Is it broken by recent OS releases? I use = ci/co every single day to track changes to individual config files on = individual machines. For simple things like ntp.conf, rc.conf, = sysctl.conf, a simple 'ci -l xxx' is a trivial way to maintain local = revision control. For small stand-alone systems, RCS is more than adequate. Why ditch it? --lyndon From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:03:23 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7ADA7177; Mon, 7 Oct 2013 21:03:23 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4DBE9237D; Mon, 7 Oct 2013 21:03:23 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VTHxa-0004Up-FU; Mon, 07 Oct 2013 21:03:22 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r97L3K0w017687; Mon, 7 Oct 2013 15:03:20 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18yUum+GocSwAgbUtIwc8cE Subject: Re: Changes to UART ns8250 From: Ian Lepore To: Zbigniew Bodek In-Reply-To: <1381179385.1130.18.camel@revolution.hippie.lan> References: <1381179385.1130.18.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Mon, 07 Oct 2013 15:03:20 -0600 Message-ID: <1381179800.1130.21.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" , freebsd-current , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:03:23 -0000 On Mon, 2013-10-07 at 14:56 -0600, Ian Lepore wrote: > On Mon, 2013-10-07 at 22:36 +0200, Zbigniew Bodek wrote: > > Hello Adrian, > > > > Thank you for your remarks. > > Please check my answers in-line. > > > > Best regards > > Zbigniew Bodek > > > > > > 2013/10/7 Adrian Chadd > > > > > Hi, > > > > > > You should add: > > > > > > * a loop counter, to break out after a while; > > > > > [ZBB] In general as long as UART is busy we cannot proceed but if the > > timeout occurs we could return an error. Do you agree? > > > > > * a DELAY(1) or something. > > > > > [ZBB] DELAY is also a busy wait after all. The reasonable solution might be > > to use ns8250_delay() to get the transmission time and use it for timeout > > from the first point. I would DELAY(1) in each loop and decrement value > > acquired from ns8250_delay(). The loop should break during that time or we > > return an error. What do you think? > > > > Is it possible to not busy-wait at all? Something like the attached? > > -- Ian > > differences between files attachment (temp.diff) > Index: sys/dev/uart/uart_dev_ns8250.c > =================================================================== > --- sys/dev/uart/uart_dev_ns8250.c (revision 255916) > +++ sys/dev/uart/uart_dev_ns8250.c (working copy) > @@ -614,6 +614,7 @@ ns8250_bus_ipend(struct uart_softc *sc) > > if (ns8250->busy_detect && (iir & IIR_BUSY) == IIR_BUSY) { > (void)uart_getreg(bas, DW_REG_USR); > + wakeup(&ns8250->busy_detect); > uart_unlock(sc->sc_hwmtx); > return (0); > } > @@ -652,6 +653,16 @@ ns8250_bus_param(struct uart_softc *sc, int baudra > > bas = &sc->sc_bas; > uart_lock(sc->sc_hwmtx); > + /* > + * When using DW UART with BUSY detection it is necessary to wait > + * until all serial transfers are finished before manipulating the > + * line control. LCR will not be affected when UART is busy. > + */ > + while (ns8250->busy_detect && > + (uart_getreg(bas, DW_REG_USR) & USR_BUSY) == 0) { > + msleep(&ns8250->busy_detect, sc->sc_hwmtx, "dwbusy", 10); > + } > + > error = ns8250_param(bas, baudrate, databits, stopbits, parity); > uart_unlock(sc->sc_hwmtx); > return (error); Ooops, that should be != 0 in that USR_BUSY test. Also, I haven't tested this at all because I don't I have any boards that use DW uarts. -- Ian From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:04:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A452E30D; Mon, 7 Oct 2013 21:04:22 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 617DB23A2; Mon, 7 Oct 2013 21:04:22 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id o17so6801078oag.18 for ; Mon, 07 Oct 2013 14:04:21 -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=0c2Mj6f1hRMM4PcN+Z/OyXCpg3AAv/na7QTde0hv5jM=; b=zoGMTVlXZs0L9e4ClzUSO0hWnAVus7sn6XS0PZL+yRK8GYddGTrTV6EqfesJ8UtnSQ OmO62Lc2S5VaVmaai+Pehc6s55HNLoi6xuxW9NyJlSpkRBnpu+c+kJ7F4nK+E/2uVAmj mwsPMOa7xRavb5yR0J3nhn9zrxaRa7jX31hEz6sf+Kd3UUL9n7FuWBWEGv9QJOfgn4aq 9wDmk8GOUXv51elMUuYZZG0iHp9c0WFFFyK258ipZPZCQOPiOsu52icsM/WDwRaq46dg QEPF6VL4+VYNb3ZtIKO2Rd1FP02EujY0pJS4sAx6O+0aH0XLJl/FbQxkudvpM8onkeAp hp6A== MIME-Version: 1.0 X-Received: by 10.60.45.102 with SMTP id l6mr5202616oem.36.1381179861618; Mon, 07 Oct 2013 14:04:21 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Mon, 7 Oct 2013 14:04:21 -0700 (PDT) In-Reply-To: <1381179611.1130.19.camel@revolution.hippie.lan> References: <1381179611.1130.19.camel@revolution.hippie.lan> Date: Mon, 7 Oct 2013 17:04:21 -0400 Message-ID: Subject: Re: CURRENT BUILD FAILURE sys/modules/cxgbe From: Outback Dingo To: Ian Lepore Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:04:22 -0000 On Mon, Oct 7, 2013 at 5:00 PM, Ian Lepore wrote: > On Mon, 2013-10-07 at 16:52 -0400, Outback Dingo wrote: > > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc > > -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe > > -DHAVE_KERNEL_OPTION_HEADERS -include > > /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq > > -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer > > -I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mcmodel=kernel > > -mno-red-zone -mno-mmx -mno-sse -msoft-float > > -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector > > -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall > > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > > -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs > > -fdiagnostics-show-option -Wno-error-tautological-compare > > -Wno-error-empty-body -Wno-error-parentheses-equality -c > > /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c > > /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:228:12: > > error: use of undeclared identifier 'cpu_clflush_line_size' > > pad = max(cpu_clflush_line_size, 16); > > ^ > > /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:273:9: > > error: use of undeclared identifier 'cpu_clflush_line_size' > > len = cpu_clflush_line_size > 64 ? 128 : 64; > > ^ > > 2 errors generated. > > Fixed in r256118. > odd i show that commit in my svn log however, kernel build still fails ------------------------------------------------------------------------ r256120 | eadler | 2013-10-07 15:22:53 -0400 (Mon, 07 Oct 2013) | 4 lines This regenerates src.conf.5 for both the RCS removal as well as r255784. Approved by: re (glebius) ------------------------------------------------------------------------ r256119 | dim | 2013-10-07 12:57:48 -0400 (Mon, 07 Oct 2013) | 6 lines Remove redundant declarations of szsigcode and sigcode in sys/i386/ibcs2/ibcs2_sysvec.c, to silence two gcc warnings. Approved by: re (gjb) MFC after: 3 days ------------------------------------------------------------------------ r256118 | dim | 2013-10-07 12:56:56 -0400 (Mon, 07 Oct 2013) | 6 lines Remove redundant declaration of cpu_clflush_line_size in sys/dev/cxgbe/t4_sge.c, to silence a gcc warning. Approved by: re (gjb) MFC after: 3 days ------------------------------------------------------------------------ r256117 | dim | 2013-10-07 12:55:34 -0400 (Mon, 07 Oct 2013) | 6 lines Initialize a variable in sys/dev/xen/control/control.c, to silence a gcc warning. Approved by: re (gjb) > -- Ian > > > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:08:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 573C7480 for ; Mon, 7 Oct 2013 21:08:24 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2F30B23DB for ; Mon, 7 Oct 2013 21:08:24 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r97L8Kck024848 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 7 Oct 2013 14:08:22 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> Date: Mon, 7 Oct 2013 14:08:19 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> To: "freebsd-current@freebsd.org" X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:08:24 -0000 On 2013-10-07, at 2:02 PM, Lyndon Nerenberg wrote: > I use ci/co every single day to track changes to individual config = files on individual machines. For simple things like ntp.conf, rc.conf, = sysctl.conf, a simple 'ci -l xxx' is a trivial way to maintain local = revision control. And sorry, what I left out was how having ci/co in the base is immensely = helpful with the installer scripts I write. The server installation = scripts I've cooked up use ci(1) to keep a record of changes made during = the (possibly customized) installation process. This is impossible if = there isn't a basic RCS in the base system. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:12:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D7B99607; Mon, 7 Oct 2013 21:12:04 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9237A2445; Mon, 7 Oct 2013 21:12:04 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1VTI5x-000NFl-QU ; Tue, 08 Oct 2013 00:12:01 +0300 Date: Tue, 8 Oct 2013 00:12:01 +0300 From: Vitalij Satanivskij To: Vitalij Satanivskij Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173 Message-ID: <20131007211201.GA89306@hell.ukr.net> References: <1381166916.122992963.5h9ygiri@frv45.ukr.net> <1381170764.32684.31088349.343931EE@webmail.messagingengine.com> <20131007185032.GA82932@hell.ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131007185032.GA82932@hell.ukr.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:12:04 -0000 One more question - we have two counter - kstat.zfs.misc.arcstats.l2_size: 1256609410560 kstat.zfs.misc.arcstats.l2_asize: 1149007667712 can anybody explain how to understand them i.e. l2_asize - real used space on l2arc an l2_size - uncompressed size, or maybe something else ? Vitalij Satanivskij wrote: VS> VS> Data on pool have compressratio around 1.4 VS> VS> On diferent servers with same data type and load L2 ARC Size: (Adaptive) can be diferent VS> VS> for example 1.04 TiB vs 1.45 TiB VS> VS> But it's all have same porblem - grow in time. VS> VS> VS> More stange for us - VS> VS> ARC: 80G Total, 4412M MFU, 5040M MRU, 76M Anon, 78G Header, 2195M Other VS> VS> 78G header size and ubnormal - VS> VS> kstat.zfs.misc.arcstats.l2_cksum_bad: 210920592 VS> kstat.zfs.misc.arcstats.l2_io_error: 7362414 VS> VS> sysctl's growing avery second. VS> VS> All part's of server (as hardware part's) in in normal state. VS> VS> After reboot no problem's for some period untile cache size grow to some limit. VS> VS> VS> VS> Mark Felder wrote: VS> MF> On Mon, Oct 7, 2013, at 13:09, Dmitriy Makarov wrote: VS> MF> > VS> MF> > How can L2 ARC Size: (Adaptive) be 1.44 TiB (up) with total physical size VS> MF> > of L2ARC devices 490GB? VS> MF> > VS> MF> VS> MF> http://svnweb.freebsd.org/base?view=revision&revision=251478 VS> MF> VS> MF> L2ARC compression perhaps? VS> MF> _______________________________________________ VS> MF> freebsd-current@freebsd.org mailing list VS> MF> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> MF> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" VS> _______________________________________________ VS> freebsd-current@freebsd.org mailing list VS> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:13:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 908D171F for ; Mon, 7 Oct 2013 21:13:21 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qe0-x236.google.com (mail-qe0-x236.google.com [IPv6:2607:f8b0:400d:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 51C792459 for ; Mon, 7 Oct 2013 21:13:21 +0000 (UTC) Received: by mail-qe0-f54.google.com with SMTP id 1so1949039qec.27 for ; Mon, 07 Oct 2013 14:13:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=5qS41wSIg/ud+Kww1fSxSyPKOIQKL6ehIdGNf48Rh9A=; b=M/5EaeOe0FbbfmMPYELsz8xnzQnLgbj+Lklisaxul62KF4pJBjU0q0Mh6Q1+oZonn/ Sp39P2pzzGYh8NmFioB87sHDncfi6hd2HK2LZSn1u5H0ZUcTdfaCR0Zq18/3NOpBu+Tc MZo0W2a7yt7VG7ZWSV4/4L5kasC2LiviqBZPIQATZZnq6OU3LPVpyVF8RdSIajNC+kDW hbnRATRyv4hr3sJ0kYDRQ2AncLw4eaBbn1MWnRIM7HKshaT/cc0aPM4cgVAc4NnTZOw3 J5le/Y8FYS39PaVxvTv8yw98lXQ7BLBjy3aRxwlcnFteqILx/ZGhtQGnQXk4qb9lhhiz kEYA== X-Received: by 10.224.166.67 with SMTP id l3mr39442058qay.39.1381180400492; Mon, 07 Oct 2013 14:13:20 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Mon, 7 Oct 2013 14:12:40 -0700 (PDT) In-Reply-To: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> From: Igor Mozolevsky Date: Mon, 7 Oct 2013 22:12:40 +0100 X-Google-Sender-Auth: kvpSdS265EvHfIjmoE7qeMzSRTw Message-ID: Subject: Re: rcs is gone? To: Lyndon Nerenberg Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:13:21 -0000 On 7 October 2013 22:08, Lyndon Nerenberg wrote: > > On 2013-10-07, at 2:02 PM, Lyndon Nerenberg wrote: > > > I use ci/co every single day to track changes to individual config files > on individual machines. For simple things like ntp.conf, rc.conf, > sysctl.conf, a simple 'ci -l xxx' is a trivial way to maintain local > revision control. > > And sorry, what I left out was how having ci/co in the base is immensely > helpful with the installer scripts I write. ... and probably screw up change control management for those who use rcs for that... -- Igor M. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:14:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9E6638D1 for ; Mon, 7 Oct 2013 21:14:46 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 61025247A for ; Mon, 7 Oct 2013 21:14:46 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r97LEgsQ024900 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 7 Oct 2013 14:14:44 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: Date: Mon, 7 Oct 2013 14:14:41 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> To: "freebsd-current@freebsd.org" X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:14:46 -0000 On 2013-10-07, at 2:08 PM, Lyndon Nerenberg wrote: > And sorry, what I left out was how having ci/co in the base is = immensely helpful with the installer scripts I write. The server = installation scripts I've cooked up use ci(1) to keep a record of = changes made during the (possibly customized) installation process. = This is impossible if there isn't a basic RCS in the base system. Finally, an issue with missing SCCS in the base is for those of us who = work in shops behind an air-gapped firewall. "Install from ports" is a non-starter. Our development systems will = never be connected to the internet for a ports upgrade. In this = environment, in-base RCS is a very useful tool.= From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:20:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 09EDABFB; Mon, 7 Oct 2013 21:20:45 +0000 (UTC) (envelope-from zbodek@gmail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1D58024F5; Mon, 7 Oct 2013 21:20:43 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id hq15so5539069wib.12 for ; Mon, 07 Oct 2013 14:20:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HkVwl181jzxkRBOQX0mJoFpolErA49EzP70seO12wfA=; b=daUyBm7fbigZehpVk2hPCGXI46B+tZIfVTJyAPhq+tLmPP7ppU3pvS5rJgMUv+ASKW Dn1C8d8ovdYK3tGdrxA6R82gGY9aQOpg7l/c7r0MgLpF5upDiW6XgU9XsHlKv0RzIVEU uWnu4qKQB2mU19XHr51DgBnThxN0LScYmMlZxLvcqHAe3fmsNhaDk7eZCyOYseU2sI5T 039j1FBpbPi/3m6j24FwCYbhB+uSHMIuZqLSA/WnWC76Q6BOB4ebzHT9g/R8V1nCs7Zt A1Dmk9PVkykNkFLtL7hla927HV/fptiwDiR1cGGH4M/MR+9/i1v2aUrENoRX5sZBTu3R b/rQ== MIME-Version: 1.0 X-Received: by 10.180.81.71 with SMTP id y7mr20587288wix.63.1381180842515; Mon, 07 Oct 2013 14:20:42 -0700 (PDT) Sender: zbodek@gmail.com Received: by 10.216.160.70 with HTTP; Mon, 7 Oct 2013 14:20:42 -0700 (PDT) In-Reply-To: <1381179800.1130.21.camel@revolution.hippie.lan> References: <1381179385.1130.18.camel@revolution.hippie.lan> <1381179800.1130.21.camel@revolution.hippie.lan> Date: Mon, 7 Oct 2013 23:20:42 +0200 X-Google-Sender-Auth: -5ze0Vq-CNFksmlSBW2M3ilboD0 Message-ID: Subject: Re: Changes to UART ns8250 From: Zbigniew Bodek To: Ian Lepore Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" , freebsd-current , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:20:45 -0000 Hello Ian. Well you can't really perform wake event basing on busy interrupt because we are busy waiting/sleeping i.a. to avoid that interrupt to occur. I tried to use pause() that should switch to another task for the declared amount of time and I got: "panic: mi_switch: switch in a critical section" Best regards Zbigniew Bodek 2013/10/7 Ian Lepore > On Mon, 2013-10-07 at 14:56 -0600, Ian Lepore wrote: > > On Mon, 2013-10-07 at 22:36 +0200, Zbigniew Bodek wrote: > > > Hello Adrian, > > > > > > Thank you for your remarks. > > > Please check my answers in-line. > > > > > > Best regards > > > Zbigniew Bodek > > > > > > > > > 2013/10/7 Adrian Chadd > > > > > > > Hi, > > > > > > > > You should add: > > > > > > > > * a loop counter, to break out after a while; > > > > > > > [ZBB] In general as long as UART is busy we cannot proceed but if the > > > timeout occurs we could return an error. Do you agree? > > > > > > > * a DELAY(1) or something. > > > > > > > [ZBB] DELAY is also a busy wait after all. The reasonable solution > might be > > > to use ns8250_delay() to get the transmission time and use it for > timeout > > > from the first point. I would DELAY(1) in each loop and decrement value > > > acquired from ns8250_delay(). The loop should break during that time > or we > > > return an error. What do you think? > > > > > > > Is it possible to not busy-wait at all? Something like the attached? > > > > -- Ian > > > > differences between files attachment (temp.diff) > > Index: sys/dev/uart/uart_dev_ns8250.c > > =================================================================== > > --- sys/dev/uart/uart_dev_ns8250.c (revision 255916) > > +++ sys/dev/uart/uart_dev_ns8250.c (working copy) > > @@ -614,6 +614,7 @@ ns8250_bus_ipend(struct uart_softc *sc) > > > > if (ns8250->busy_detect && (iir & IIR_BUSY) == IIR_BUSY) { > > (void)uart_getreg(bas, DW_REG_USR); > > + wakeup(&ns8250->busy_detect); > > uart_unlock(sc->sc_hwmtx); > > return (0); > > } > > @@ -652,6 +653,16 @@ ns8250_bus_param(struct uart_softc *sc, int baudra > > > > bas = &sc->sc_bas; > > uart_lock(sc->sc_hwmtx); > > + /* > > + * When using DW UART with BUSY detection it is necessary to wait > > + * until all serial transfers are finished before manipulating the > > + * line control. LCR will not be affected when UART is busy. > > + */ > > + while (ns8250->busy_detect && > > + (uart_getreg(bas, DW_REG_USR) & USR_BUSY) == 0) { > > + msleep(&ns8250->busy_detect, sc->sc_hwmtx, "dwbusy", 10); > > + } > > + > > error = ns8250_param(bas, baudrate, databits, stopbits, parity); > > uart_unlock(sc->sc_hwmtx); > > return (error); > > Ooops, that should be != 0 in that USR_BUSY test. Also, I haven't > tested this at all because I don't I have any boards that use DW uarts. > > -- Ian > > > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:21:37 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7E659D73 for ; Mon, 7 Oct 2013 21:21:37 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 6B3C02509 for ; Mon, 7 Oct 2013 21:21:37 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id BB54E1A3C7D; Mon, 7 Oct 2013 14:21:36 -0700 (PDT) Message-ID: <525325E0.4050207@mu.org> Date: Mon, 07 Oct 2013 14:21:36 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Lyndon Nerenberg Subject: Re: rcs is gone? References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:21:37 -0000 On 10/7/13 2:14 PM, Lyndon Nerenberg wrote: > On 2013-10-07, at 2:08 PM, Lyndon Nerenberg wrote: > >> And sorry, what I left out was how having ci/co in the base is immensely helpful with the installer scripts I write. The server installation scripts I've cooked up use ci(1) to keep a record of changes made during the (possibly customized) installation process. This is impossible if there isn't a basic RCS in the base system. > Finally, an issue with missing SCCS in the base is for those of us who work in shops behind an air-gapped firewall. > > "Install from ports" is a non-starter. Our development systems will never be connected to the internet for a ports upgrade. In this environment, in-base RCS is a very useful tool. > _______________________________________________ > How do you do your initial install? -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:26:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2E325F05 for ; Mon, 7 Oct 2013 21:26:49 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E28FF253B for ; Mon, 7 Oct 2013 21:26:48 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id n9so5276846qcw.19 for ; Mon, 07 Oct 2013 14:26:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=sJk5Zebp0I50ZDKsOrDHDVl0BQrY85+IVodMHdTT/R4=; b=iiS0hyft1mm8vF1T55cPg1UEyFr5u8nWfMqC7DzsT8TjcpvYgR2jWmoVRJp890wECm 03LyJ4nPjtWlW1bbC9tY0HTiDvtjBWLAIuKZGxp1eXnqm4mhSjm4L8liTnxVjYMMvbMU uiUsBAF5ckgVWbnF4NDvV4fObFbcgiqzMG073iK4SO43Q4+eDmY3aZo17jimQIWaInqU CZMi164tPVogNBg+ZDK0bvo1q6f+hUKmxTCrWUB+edyg5uPJn9bwB6MtR/prPQF8xrzC /MQYqG6fC3KzzXBhrPRnntvEzcid24Mprp7YpdRvC4OPDrofGqnjuh8qHeZcE3luWcTB kH9g== X-Received: by 10.224.166.67 with SMTP id l3mr39501934qay.39.1381181208003; Mon, 07 Oct 2013 14:26:48 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Mon, 7 Oct 2013 14:26:07 -0700 (PDT) In-Reply-To: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> From: Igor Mozolevsky Date: Mon, 7 Oct 2013 22:26:07 +0100 X-Google-Sender-Auth: OA_xw2qBCri-liZzL6798ubOl7I Message-ID: Subject: Re: rcs is gone? To: Andreas Nilsson Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:26:49 -0000 On 7 October 2013 22:15, Andreas Nilsson wrote: > Well, it has been announced, and is available as a port. > So there's no version control in the base at all now?.. When did FreeBSD decide to move away from distributing a usable OS? Why not just distribute a kernel and a few bits that are barely sufficient for the initial set up, and then make users fetch everything from ports? -- Igor M. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:28:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7AFE3DE for ; Mon, 7 Oct 2013 21:28:44 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3D4282567 for ; Mon, 7 Oct 2013 21:28:44 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:402a:9533:e91d:ef08]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 729204AC2D; Tue, 8 Oct 2013 01:28:42 +0400 (MSK) Date: Tue, 8 Oct 2013 01:28:39 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <22543819.20131008012839@serebryakov.spb.ru> To: Igor Mozolevsky Subject: Re: rcs is gone? In-Reply-To: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-current@freebsd.org" , Andreas Nilsson X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:28:44 -0000 Hello, Igor. You wrote 8 =D0=BE=D0=BA=D1=82=D1=8F=D0=B1=D1=80=D1=8F 2013 =D0=B3., 1:26:0= 7: >> Well, it has been announced, and is available as a port. IM> So there's no version control in the base at all now?.. When did FreeBSD IM> decide to move away from distributing a usable OS? Why not just distrib= ute IM> a kernel and a few bits that are barely sufficient for the initial set = up, IM> and then make users fetch everything from ports? svnlite? :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:29:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4D7BB1F4; Mon, 7 Oct 2013 21:29:29 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 20E8A2578; Mon, 7 Oct 2013 21:29:28 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id B7A8189CB; Mon, 7 Oct 2013 21:29:27 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us B7A8189CB Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 7 Oct 2013 17:29:25 -0400 From: Glen Barber To: Igor Mozolevsky Subject: Re: rcs is gone? Message-ID: <20131007212925.GC2133@glenbarber.us> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="E13BgyNx05feLLmH" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-current@freebsd.org" , Andreas Nilsson X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:29:29 -0000 --E13BgyNx05feLLmH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 07, 2013 at 10:26:07PM +0100, Igor Mozolevsky wrote: > On 7 October 2013 22:15, Andreas Nilsson wrote: >=20 >=20 > > Well, it has been announced, and is available as a port. > > >=20 > So there's no version control in the base at all now?.. When did FreeBSD > decide to move away from distributing a usable OS? Why not just distribute > a kernel and a few bits that are barely sufficient for the initial set up, > and then make users fetch everything from ports? >=20 svnlite? Glen --E13BgyNx05feLLmH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSUye1AAoJELls3eqvi17QfIUQANNoUk4O9ui1oNPzcaLdR694 a5BUMCU9clBs7N66ky8cWM9UeIeKCy6l/fwo29+YDqGiTfl9Rug2NbNR29VTxssY G/4a6c8cgAXw4X81X0g1hx1gYeeUJ33u1Gu5ZcySp4jA8emQdISq9eNqxdCWS75K vqgVpJgiZwGSKKUhWJl5OlQvkFejnzoguO1NIVByj+ATHHohXUAeBQceASyG/425 j765U7v6SNNkz7jePclURVFndw6uXxcL6nNSDi7Ev/D50aGvrNgmL8V3m8N1iDrU lDnIis9hUgxpjuwKm4uIwKTgd8XyWA1OFjRD/hQSpt5QYCbZD0dWW8nfeiWTEwxb yJFz0AjlUG8o97qhrQhZehHcavK8DGzz0+AA65YeKPO2kGxSdc6Kcu6fAr/Aa8cu krEJp004EKAaiwVbXBEAJlDardYuU0GjVo4IBqC/rJ2IxGB8ZDdJqjVOhEbKGfFs AfVscUBxmzHi7dnwlzWOF+x6xw5TtnYzg/J96H5OG3WoxEILieGaR3fMa2nHyvNS 4IFIXpRZ35M1N/c1Pe21Ps+mITpNdJXh7WzF3HNQZoNBJFoLavM7KiQq/+iVGBTg CNCUnVWurXVa3RQo8qA24PhNd8mC/g7BixoOY2RKwYvMNutiqVWFUxyzuPJM6cKy hwl33C30P3bgzxtJWxa6 =MUVJ -----END PGP SIGNATURE----- --E13BgyNx05feLLmH-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:42:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F2796779 for ; Mon, 7 Oct 2013 21:42:41 +0000 (UTC) (envelope-from paul.g.webster.lists@gmail.com) Received: from mail-we0-x242.google.com (mail-we0-x242.google.com [IPv6:2a00:1450:400c:c03::242]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 92FD8266F for ; Mon, 7 Oct 2013 21:42:41 +0000 (UTC) Received: by mail-we0-f194.google.com with SMTP id u57so1092882wes.1 for ; Mon, 07 Oct 2013 14:42:40 -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=L9hM0m4JKPZR4LhTQHtCZ5CMSLqly5C+SLdaPqCho24=; b=jFk2IWtLux6JNIvBPSRfrTqV7aZDKUK67YhQfZKPgZFot78VE4F3/EBle8LS9Qn/Zd Cot9N64CWdUVkozITTb84a49YoiEtq4zpAJtsAa2PCn2bKnImh/Z3GwpCgho09aqeErc kCvw3bVZPLZdoCMKaSffEIGhTjNVeAJ6iGuJTK6Rk0ACakD41Fzlu7GVUtE0cqA6pybK QKVBxUy2UcS9z132OzEUeyfS/zLqC7YTPO85Nd5DCRyDC6WWbuYF6d4BZWlipkwECDUI xfc5uQ/iL63ub5kO8/K8gVtnSj5Xvsdq6zxM19So29X7q3uzAC9HsL5dolLJLJYhM4yl BArQ== MIME-Version: 1.0 X-Received: by 10.180.13.13 with SMTP id d13mr21370474wic.34.1381182160018; Mon, 07 Oct 2013 14:42:40 -0700 (PDT) Received: by 10.180.20.69 with HTTP; Mon, 7 Oct 2013 14:42:39 -0700 (PDT) Date: Mon, 7 Oct 2013 22:42:39 +0100 Message-ID: Subject: Kernel build fail for generic on r256122 (if_cxgbe) From: Paul Webster To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:42:42 -0000 Details on pastebin: http://pastebin.com/raw.php?i=dNzL3yXR From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:46:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A705F9BB for ; Mon, 7 Oct 2013 21:46:43 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 520C626A4 for ; Mon, 7 Oct 2013 21:46:42 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id B055B1D50A for ; Mon, 7 Oct 2013 21:46:40 +0000 (UTC) Message-ID: <52532BD8.2070509@allanjude.com> Date: Mon, 07 Oct 2013 17:47:04 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> In-Reply-To: Content-Type: multipart/mixed; boundary="------------000300000003070506000001" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:46:43 -0000 This is a multi-part message in MIME format. --------------000300000003070506000001 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 2013-10-07 17:00, Outback Dingo wrote: > On Mon, Oct 7, 2013 at 4:54 PM, Allan Jude wrote: > >> On 2013-10-07 16:43, Warren Block wrote: >>> On Mon, 7 Oct 2013, Allan Jude wrote: >>> >>>> Additional, it includes some other changes to bsdinstall: >>>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>>> to no >>> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 . >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >> That is a good idea, I'll add that >> >> I've also hit this: >> >> http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html >> and plan to throw in a fix for that. >> Which makes more sense, blindly 'killall dhclient' before we try to >> acquire a new lease, or detect that dhclient is running and try to use >> the IP that has already been assigned? >> >> >> > jeeeeeez after i just updated and patched my source tree to do a build, you > go and fix things :P > anyway you can just generate a master diff against the tree that we can > apply, seems not ive to > revert the patches and reapply all the newest ones. > > >> -- >> Allan Jude >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Attached find the patch from last night against a fresh HEAD I am working on incorporating Warren's patch now -- Allan Jude --------------000300000003070506000001 Content-Type: text/plain; charset=windows-1252; name="zfsboot.2013-10-06.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="zfsboot.2013-10-06.patch" Index: usr.sbin/bsdconfig/share/device.subr =================================================================== --- usr.sbin/bsdconfig/share/device.subr (revision 256125) +++ usr.sbin/bsdconfig/share/device.subr (working copy) @@ -208,6 +208,10 @@ f_device_get_all() n=$(( $n + 1 )) # Get the desc, type, and max (with debugging disabled) # NOTE: Bypassing f_device_name_get() for efficiency + # ASIDE: This would be equivalent to the following: + # debug= f_device_name_get $dev desc + # debug= f_device_name_get $dev type + # debug= f_device_name_get $dev max debug= f_getvar _device_desc$n desc debug= f_getvar _device_type$n type debug= f_getvar _device_max$n max @@ -313,7 +317,10 @@ f_device_get_all() continue fi - f_device_register "$diskname" "" \ + # Try and find its description + f_device_desc "$diskname" $DEVICE_TYPE_DISK desc + + f_device_register "$diskname" "$desc" \ "/dev/$diskname" $DEVICE_TYPE_DISK 0 f_dprintf "Found a disk device named %s" "$diskname" @@ -379,10 +386,27 @@ f_device_name_get() case "$__prop" in type|desc|max) : good ;; *) return $FAILURE; esac + # + # Attempt to create an alternate-form of $__name that contains the + # first contiguous string of numbers replaced with `%d' for comparison + # against stored pattern names (see MAIN). + # + local __left="${__name%%[0-9]*}" __right="${__name#*[0-9]}" __dname= + if [ "$__left" != "$__name" ]; then + # Chop leading digits from right 'til we hit first non-digit + while :; do + case "$__right" in + [0-9]*) __right="${__right#[0-9]}" ;; + *) break + esac + done + __dname="${__left}%d$__right" + fi + [ "$__type" = "$DEVICE_TYPE_ANY" ] && __type= for __dev in $DEVICE_NAMES; do __n=$(( $__n + 1 )) - [ "$__dev" = "$__name" ] || continue + [ "$__dev" = "$__name" -o "$__dev" = "$__dname" ] || continue f_getvar _device_type$__n __devtype [ "${__type:-$__devtype}" = "$__devtype" ] || continue f_getvar _device_$__prop$__n $__var_to_set @@ -463,6 +487,39 @@ f_device_desc() fi fi + # + # For disks, attempt to return camcontrol(8) descriptions. + # Otherwise fall through to below static list. + # + f_have camcontrol && + [ "${__type:-$DEVICE_TYPE_DISK}" = "$DEVICE_TYPE_DISK" ] && + __cp=$( camcontrol devlist 2> /dev/null | awk -v disk="$__name" ' + $0~"(\\(|,)"disk"(,|\\))" { + if (!match($0, "<[^>]+>")) next + print substr($0, RSTART+1, RLENGTH-2) + found = 1 + exit + } + END { exit ! found } + ' ) && setvar "$__var_to_set" "$__cp" && return $SUCCESS + + # + # Attempt to create an alternate-form of $__name that contains the + # first contiguous string of numbers replaced with `%d' for comparison + # against stored pattern names (see MAIN). + # + local __left="${__name%%[0-9]*}" __right="${__name#*[0-9]}" __dname= + if [ "$__left" != "$__name" ]; then + # Chop leading digits from right 'til we hit first non-digit + while :; do + case "$__right" in + [0-9]*) __right="${__right#[0-9]}" ;; + *) break + esac + done + __dname="${__left}%d$__right" + fi + local __dev __devtype __n=0 for __dev in $DEVICE_NAMES; do __n=$(( $__n + 1 )) @@ -472,11 +529,8 @@ f_device_desc() __devname=$( f_substr "$__name" 0 ${#__dev} ) [ "$__devname" = "$__dev" ] || continue else - __devname="${__name%%[0-9]*}" - __devunit="${__name#$__devname}" - __devunit="${__devunit%%[!0-9]*}" - __devname=$( printf "$__dev" $__devunit ) - [ "$__devname" = "$__name" ] || continue + [ "$__dev" = "$__name" -o "$__dev" = "$__dname" ] || + continue fi debug= f_getvar _device_desc$__n $__var_to_set return $? @@ -655,7 +709,25 @@ f_device_menu() return $retval } +# f_disk_size_bytes $disk # +# Return the size of the disk in bytes +# +f_disk_size_bytes() +{ + local disk="$1" + + local size_bytes=`diskinfo -v $disk|grep '# mediasize in bytes' | awk '{ print $1 }'` + local retval=$? + + if [ $retval -ne 0 ]; then + exit $retval + fi + + echo "$size_bytes" +} + +# # Short-hand # f_cdrom() { f_device_name_set $DEVICE_TYPE_CDROM "$1" "$2" "$3"; } @@ -680,6 +752,7 @@ f_disk "ipsd%d" "IBM ServeRAID RAID array" f_disk "mfid%d" "LSI MegaRAID SAS array" 4 f_disk "mlxd%d" "Mylex RAID disk" 4 f_disk "twed%d" "3ware ATA RAID array" 4 +f_disk "vtbd%d" "VirtIO Block Device" 16 f_floppy "fd%d" "Floppy Drive unit A" 4 f_serial "cuau%d" "%s on device %s (COM%d)" 16 f_usb "da%da" "USB Mass Storage Device" 16 Index: usr.sbin/bsdconfig/share/strings.subr =================================================================== --- usr.sbin/bsdconfig/share/strings.subr (revision 256125) +++ usr.sbin/bsdconfig/share/strings.subr (working copy) @@ -26,6 +26,11 @@ if [ ! "$_STRINGS_SUBR" ]; then _STRINGS_SUBR=1 # # $FreeBSD$ # +############################################################ INCLUDES + +BSDCFG_SHARE="/usr/share/bsdconfig" +. $BSDCFG_SHARE/common.subr || exit 1 + ############################################################ GLOBALS # @@ -319,6 +324,112 @@ f_shell_unescape() f_replaceall "$__string" "'\\''" "'" "$__var_to_set" } +# f_expand_number $string [$var_to_set] +# +# Unformat $string into a number, optionally to be stored in $var_to_set. This +# function follows the SI power of two convention. +# +# The prefixes are: +# +# Prefix Description Multiplier +# k kilo 1024 +# M mega 1048576 +# G giga 1073741824 +# T tera 1099511627776 +# P peta 1125899906842624 +# E exa 1152921504606846976 +# +# NOTE: Prefixes are case-insensitive. +# +# Upon successful completion, the value 0 is returned (or stored to +# $var_to_set); otherwise -1. Reasons for a -1 return include: +# +# Given $string contains no digits. +# An unrecognized prefix was given. +# Result too large to calculate. +# +f_expand_number() +{ + local __string="$1" __var_to_set="$2" + local __cp __num + + # Remove any leading non-digits + while :; do + __cp="$__string" + __string="${__cp#[!0-9]}" + [ "$__string" = "$__cp" ] && break + done + + # Return `-1' if string didn't contain any digits + if [ ! "$__string" ]; then + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + fi + + # Store the numbers + __num="${__string%%[!0-9]*}" + + # Shortcut + if [ $__num -eq 0 ]; then + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" 0 + else + echo 0 + fi + return $SUCCESS + fi + + # Remove all the leading numbers from the string to get at the prefix + while :; do + __cp="$__string" + __string="${__cp#[0-9]}" + [ "$__string" = "$__cp" ] && break + done + + # Test for invalid prefix + case "$__string" in + ""|[KkMmGgTtPpEe]*) : known prefix ;; + *) + # Unknown prefix + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + esac + + # Multiply the number out + case "$__string" in + [Kk]) __num=$(( $__num * 1024 )) ;; + [Mm]) __num=$(( $__num * 1048576 )) ;; + [Gg]) __num=$(( $__num * 1073741824 )) ;; + [Tt]) __num=$(( $__num * 1099511627776 )) ;; + [Pp]) __num=$(( $__num * 1125899906842624 )) ;; + [Ee]) __num=$(( $__num * 1152921504606846976 )) ;; + esac + if [ $__num -le 0 ]; then + # Arithmetic overflow + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + fi + + # Return the number + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" $__num + else + echo $__num + fi +} + ############################################################ MAIN f_dprintf "%s: Successfully loaded." strings.subr Index: usr.sbin/bsdinstall/bsdinstall =================================================================== --- usr.sbin/bsdinstall/bsdinstall (revision 256125) +++ usr.sbin/bsdinstall/bsdinstall (working copy) @@ -28,6 +28,7 @@ : ${BSDINSTALL_LOG="/tmp/bsdinstall_log"}; export BSDINSTALL_LOG : ${BSDINSTALL_TMPETC="/tmp/bsdinstall_etc"}; export BSDINSTALL_TMPETC +: ${BSDINSTALL_TMPBOOT="/tmp/bsdinstall_boot"}; export BSDINSTALL_TMPBOOT : ${PATH_FSTAB="$BSDINSTALL_TMPETC/fstab"}; export PATH_FSTAB : ${BSDINSTALL_DISTDIR="/usr/freebsd-dist"}; export BSDINSTALL_DISTDIR : ${BSDINSTALL_CHROOT="/mnt"}; export BSDINSTALL_CHROOT @@ -35,5 +36,6 @@ VERB=${1:-auto}; shift [ -d "$BSDINSTALL_TMPETC" ] || mkdir -p "$BSDINSTALL_TMPETC" +[ -d "$BSDINSTALL_TMPBOOT" ] || mkdir -p "$BSDINSTALL_TMPBOOT" echo "Running installation step: $VERB $@" >> "$BSDINSTALL_LOG" exec "/usr/libexec/bsdinstall/$VERB" "$@" 2>> "$BSDINSTALL_LOG" Index: usr.sbin/bsdinstall/scripts/Makefile =================================================================== --- usr.sbin/bsdinstall/scripts/Makefile (revision 256125) +++ usr.sbin/bsdinstall/scripts/Makefile (working copy) @@ -2,7 +2,7 @@ SCRIPTS= auto adduser checksum config docsinstall hostname jail keymap \ mirrorselect mount netconfig netconfig_ipv4 netconfig_ipv6 rootpass \ - script services time umount wlanconfig + script services time umount wlanconfig zfsboot BINDIR= /usr/libexec/bsdinstall NO_MAN= true Index: usr.sbin/bsdinstall/scripts/auto =================================================================== --- usr.sbin/bsdinstall/scripts/auto (revision 256125) +++ usr.sbin/bsdinstall/scripts/auto (working copy) @@ -93,24 +93,39 @@ fi rm $PATH_FSTAB touch $PATH_FSTAB -dialog --backtitle "FreeBSD Installer" --title "Partitioning" --extra-button \ - --extra-label "Manual" --ok-label "Guided" --cancel-label "Shell" \ - --yesno "Would you like to use the guided partitioning tool (recommended for beginners) or to set up partitions manually (experts)? You can also open a shell and set up partitions entirely by hand." 0 0 +PMODES="\ +Guided \"Partitioning Tool (Recommended for Beginners)\" \ +Manual \"Manually Configure Partitions (Expert)\" \ +ZFS \"Automatic Root-on-ZFS (Experimental)\" \ +Shell \"Open a shell and partition by hand\" \ +" -case $? in -0) # Guided +exec 3>&1 +PARTMODE=`echo $PMODES | xargs dialog --backtitle "FreeBSD Installer" \ + --title "Partitioning" \ + --menu "How would you like to partition your disk?" \ + 0 0 0 2>&1 1>&3` +if [ $? -eq $DIALOG_CANCEL ]; then exit 1; fi +exec 3>&- + +case "$PARTMODE" in +"Guided") # Guided bsdinstall autopart || error bsdinstall mount || error ;; -1) # Shell +"Shell") # Shell clear echo "Use this shell to set up partitions for the new system. When finished, mount the system at $BSDINSTALL_CHROOT and place an fstab file for the new system at $PATH_FSTAB. Then type 'exit'. You can also enter the partition editor at any time by entering 'bsdinstall partedit'." sh 2>&1 ;; -3) # Manual +"Manual") # Manual bsdinstall partedit || error bsdinstall mount || error ;; +"ZFS") # ZFS + bsdinstall zfsboot || error + bsdinstall mount || error + ;; *) error ;; Index: usr.sbin/bsdinstall/scripts/config =================================================================== --- usr.sbin/bsdinstall/scripts/config (revision 256125) +++ usr.sbin/bsdinstall/scripts/config (working copy) @@ -31,6 +31,11 @@ rm $BSDINSTALL_TMPETC/rc.conf.* cp $BSDINSTALL_TMPETC/* $BSDINSTALL_CHROOT/etc +cat $BSDINSTALL_TMPBOOT/loader.conf.* >> $BSDINSTALL_TMPBOOT/loader.conf +rm $BSDINSTALL_TMPBOOT/loader.conf.* + +cp $BSDINSTALL_TMPBOOT/* $BSDINSTALL_CHROOT/boot + # Set up other things from installed config chroot $BSDINSTALL_CHROOT /usr/bin/newaliases Index: usr.sbin/bsdinstall/scripts/keymap =================================================================== --- usr.sbin/bsdinstall/scripts/keymap (revision 256125) +++ usr.sbin/bsdinstall/scripts/keymap (working copy) @@ -29,7 +29,8 @@ kbdcontrol -d >/dev/null 2>&1 if [ $? -eq 0 ]; then dialog --backtitle "FreeBSD Installer" --title "Keymap Selection" \ - --yesno "Would you like to set a non-default key mapping for your keyboard?" 0 0 || exit 0 + --defaultno --yesno "Would you like to set a non-default key \ + mapping for your keyboard?" 0 0 || exit 0 exec 3>&1 kbdmap 2>&1 1>&3 | grep 'keymap=' > $BSDINSTALL_TMPETC/rc.conf.keymap fi Index: usr.sbin/bsdinstall/scripts/netconfig =================================================================== --- usr.sbin/bsdinstall/scripts/netconfig (revision 256125) +++ usr.sbin/bsdinstall/scripts/netconfig (working copy) @@ -90,14 +90,18 @@ case $? in esac if [ ${IPV4_AVAIL} -eq 1 ]; then - dialog --backtitle 'FreeBSD Installer' --title 'Network Configuration' \ - --yesno 'Would you like to configure IPv4 for this interface?' 0 0 - if [ $? -eq $DIALOG_OK ]; then - bsdinstall netconfig_ipv4 ${INTERFACE} "${IFCONFIG_PREFIX}" || \ - exec $0 - else - IPV4_AVAIL=0 - fi + bsdinstall netconfig_ipv4 ${INTERFACE} "${IFCONFIG_PREFIX}" + case $? in + 0) #OK + break + ;; + 4) #No ipv4 + IPV4_AVAIL=0 + ;; + *) #Error + exec $0 + ;; + esac fi # In case wlanconfig left an option and we do not support IPv4 we need to write # it out on its own. We cannot write it out with IPv6 as that suffix. Index: usr.sbin/bsdinstall/scripts/netconfig_ipv4 =================================================================== --- usr.sbin/bsdinstall/scripts/netconfig_ipv4 (revision 256125) +++ usr.sbin/bsdinstall/scripts/netconfig_ipv4 (working copy) @@ -43,34 +43,58 @@ case "${INTERFACE}" in ;; esac -dialog --backtitle 'FreeBSD Installer' --title 'Network Configuration' --yesno 'Would you like to use DHCP to configure this interface?' 0 0 -if [ $? -eq $DIALOG_OK ]; then - echo ifconfig_$INTERFACE=\"${IFCONFIG_PREFIX}DHCP\" >> $BSDINSTALL_TMPETC/._rc.conf.net - - if [ ! -z $BSDINSTALL_CONFIGCURRENT ]; then - dialog --backtitle 'FreeBSD Installer' --infobox "Acquiring DHCP lease..." 0 0 - dhclient $INTERFACE 2>> $BSDINSTALL_LOG - if [ $? -ne 0 ]; then - dialog --backtitle 'FreeBSD Installer' --msgbox "DHCP lease acquisition failed." 0 0 - exec $0 ${INTERFACE} "${IFCONFIG_PREFIX}" - fi - fi - exit 0 -fi - IP_ADDRESS=`ifconfig $INTERFACE inet | awk '/inet/ {printf("%s\n", $2); }'` NETMASK=`ifconfig $INTERFACE inet | awk '/inet/ {printf("%s\n", $4); }'` ROUTER=`netstat -rn -f inet | awk '/default/ {printf("%s\n", $2);}'` exec 3>&1 -IF_CONFIG=$(dialog --backtitle 'FreeBSD Installer' --title 'Network Configuration' --form 'Static Network Interface Configuration' 0 0 0 \ + + +#dialog --backtitle 'FreeBSD Installer' --title 'Network Configuration' \ +# --extra-button --ok-label "DHCP" --extra-label "Static" \ +# --cancel-label "None" \ +# --yesno 'How would you like to configure this interface?' 0 0 + +IF_CONFIG=$(dialog --backtitle 'FreeBSD Installer' \ + --title 'Network Configuration' \ + --extra-button --extra-label "No IPv4" --defaultno \ + --cancel-label "DHCP" --ok-label "Static" \ + --form 'Network Interface Configuration' 0 0 0 \ 'IP Address' 1 0 "$IP_ADDRESS" 1 20 16 0 \ 'Subnet Mask' 2 0 "$NETMASK" 2 20 16 0 \ 'Default Router' 3 0 "$ROUTER" 3 20 16 0 \ 2>&1 1>&3) -if [ $? -eq $DIALOG_CANCEL ]; then exit 1; fi +case $? in + 1) #DHCP + echo ifconfig_$INTERFACE=\"${IFCONFIG_PREFIX}DHCP\" >> \ + $BSDINSTALL_TMPETC/._rc.conf.net + + if [ ! -z $BSDINSTALL_CONFIGCURRENT ]; then + dialog --backtitle 'FreeBSD Installer' \ + --infobox "Acquiring DHCP lease..." 0 0 + dhclient $INTERFACE 2>> $BSDINSTALL_LOG + if [ $? -ne 0 ]; then + dialog --backtitle 'FreeBSD Installer' \ + --msgbox "DHCP lease acquisition failed." 0 0 + exec $0 ${INTERFACE} "${IFCONFIG_PREFIX}" + fi + fi + exit 0 + ;; + 3) #None + exit 4 + ;; + 0) #Static + break + ;; + *) + error + ;; +esac exec 3>&- + + echo $INTERFACE $IF_CONFIG | awk -v prefix="$IFCONFIG_PREFIX" '{ printf("ifconfig_%s=\"%s\inet %s netmask %s\"\n", $1, prefix, $2, $3); @@ -85,4 +109,3 @@ if [ ! -z $BSDINSTALL_CONFIGCURRENT ]; then route add -inet default $defaultrouter fi fi - Index: usr.sbin/bsdinstall/scripts/services =================================================================== --- usr.sbin/bsdinstall/scripts/services (revision 256125) +++ usr.sbin/bsdinstall/scripts/services (working copy) @@ -46,22 +46,23 @@ DAEMONS=$(dialog --backtitle "FreeBSD Installer" \ moused "PS/2 mouse pointer on console" ${moused_enable:-off} \ ntpd "Synchronize system and network time" ${ntpd_enable:-off} \ powerd "Adjust CPU frequency dynamically if supported" ${powerd_enable:-off} \ + dumpdev "Would you like to enable crash dumps to /var ?" ${dumpdev:-on} \ 2>&1 1>&3) exec 3>&- +local havedump= for daemon in $DAEMONS; do + if [ "$daemon" == "dumpdev" ]; then + havedump=1 + echo \# Set dumpdev to \"AUTO\" to enable crash dumps, \ + \"NO\" to disable >> \ + $BSDINSTALL_TMPETC/rc.conf.services + echo dumpdev=\"AUTO\" >> $BSDINSTALL_TMPETC/rc.conf.services + continue + fi echo ${daemon}_enable=\"YES\" >> $BSDINSTALL_TMPETC/rc.conf.services done -echo \# Set dumpdev to \"AUTO\" to enable crash dumps, \"NO\" to disable >> \ - $BSDINSTALL_TMPETC/rc.conf.services - -dialog --backtitle "FreeBSD Installer" --title "Dumpdev Configuration" \ - --nocancel --yesno \ - "Would you like to enable crash dumps? If you start having problems with the system it can help the FreeBSD developers debug the problem. But the crash dumps can take up a lot of disk space in /var." 0 0 - -if [ $? -eq $DIALOG_OK ]; then - echo dumpdev=\"AUTO\" >> $BSDINSTALL_TMPETC/rc.conf.services -else +if [ ! "$havedump" ]; then echo dumpdev=\"NO\" >> $BSDINSTALL_TMPETC/rc.conf.services fi Index: usr.sbin/bsdinstall/scripts/zfsboot =================================================================== --- usr.sbin/bsdinstall/scripts/zfsboot (revision 0) +++ usr.sbin/bsdinstall/scripts/zfsboot (working copy) @@ -0,0 +1,937 @@ +#!/bin/sh +#- +# Copyright (c) 2013 Allan Jude +# Copyright (c) 2013 Devin Teske +# All rights reserved. +# +# Redistribution and use in source and binary forms, with or without +# modification, are permitted provided that the following conditions +# are met: +# 1. Redistributions of source code must retain the above copyright +# notice, this list of conditions and the following disclaimer. +# 2. Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# +# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. +# +# $FreeBSD$ +# +############################################################ INCLUDES + +BSDCFG_SHARE="/usr/share/bsdconfig" +. $BSDCFG_SHARE/common.subr || exit 1 +f_dprintf "%s: loading includes..." "$0" +f_include $BSDCFG_SHARE/device.subr +f_include $BSDCFG_SHARE/dialog.subr + +############################################################ CONFIGURATION + +# +# Default name of the boot-pool +# +: ${ZFSBOOT_POOL_NAME:=zroot} + +# +# Default name for the boot environment parent dataset +# +: ${ZFSBOOT_BEROOT_NAME:=bootenv} + +# +# Default name for the primany boot environment +# +: ${ZFSBOOT_BOOTFS_NAME:=default} + +# +# Default Virtual Device (vdev) type to create +# +: ${ZFSBOOT_VDEV_TYPE:=stripe} + +# +# Should we use gnop(8) to configure a transparent mapping to 4K sectors? +# +: ${ZFSBOOT_GNOP_4K_FORCE_ALIGN:=1} + +# +# Should we use geli(8) to encrypt the drives +# +: ${ZFSBOOT_GELI_ENCRYPTION:=} + +# +# What should we name the unencrypted pool +# +: ${ZFSBOOT_GELI_POOL_NAME:=geliboot} + +# +# How big should the unencrypted boot pool be +# +: ${ZFSBOOT_GELI_BOOT_SIZE:=2g} + +# +# Default disks to use (always empty unless being scripted) +# +: ${ZFSBOOT_DISKS:=} + +# +# Default partitioning scheme to use on disks +# +: ${ZFSBOOT_PARTITION_SCHEME:=GPT} + +# +# How much swap to put on each block device in the boot zpool +# NOTE: Value passed to gpart(8); which supports SI unit suffixes. +# +: ${ZFSBOOT_SWAP_SIZE:=2g} + +# +# Default ZFS layout for root zpool +# +# NOTE: Requires `/tmp', `/var/tmp', and `/$ZFSBOOT_BOOTFS_NAME/default' +# NOTE: Anything after pound/hash character [#] is ignored as a comment. +# +f_isset ZFSBOOT_DATASETS || ZFSBOOT_DATASETS=" + # Dataset Options (comma or space separated; or both) + #Boot Envionment Root, contains all boot datasets + /$ZFSBOOT_BEROOT_NAME \ + mountpoint=none + #Default boot environment dataset + /$ZFSBOOT_BEROOT_NAME/$ZFSBOOT_BOOTFS_NAME \ + mountpoint=/ + #compress /tmp, allow exec but not setuid + /tmp mountpoint=/tmp,compression=lz4,exec=on,setuid=off + #/usr is not mounted so that 'base' files go to the BEROOT + /usr mountpoint=/usr,canmount=off + #keep local files, like packages separate from the base system + /usr/local + #keep home directories separate so they are common to all BEs + /usr/home setuid=off + #we only need 1 copy of the ports tree + /usr/ports compression=lz4,setuid=off + /usr/ports/distfiles compression=off,exec=off,setuid=off + /usr/ports/packages compression=off,exec=off,setuid=off + #One source tree, compressed + /usr/src compression=lz4,exec=off,setuid=off + /usr/obj + #create /var and friends + /var mountpoint=/var + /var/crash compression=lz4,exec=off,setuid=off + /var/db exec=off,setuid=off + /var/db/pkg compression=lz4,exec=off,setuid=off + /var/empty exec=off,setuid=off + /var/log compression=lz4,exec=off,setuid=off + /var/mail compression=lz4,exec=off,setuid=off + /var/run exec=off,setuid=off + /var/tmp compression=lz4,exec=on,setuid=off +" # END-QUOTE + +############################################################ GLOBALS + +# +# Strings that should be moved to an i18n file and loaded with f_include_lang() +# +hline_alnum_arrows_punc_tab_enter="Use alnum, arrows, punctuation, TAB or ENTER" +hline_arrows_space_tab_enter="Use arrows, SPACE, TAB or ENTER" +hline_arrows_tab_enter="Press arrows, TAB or ENTER" +msg_cancel="Cancel" +msg_configure_options="Configure Options:" +msg_create="Install" +msg_create_desc="Proceed with Installation" +msg_create_help="Create ZFS boot pool with displayed options" +msg_detailed_disk_info="gpart(8) show %s:\n%s\n\ncamcontrol(8) inquiry %s:\n%s\n\n\ncamcontrol(8) identify %s:\n%s\n" +msg_disk_info="Disk Info" +msg_disk_info_help="Get detailed information on disk device(s)" +msg_disks_to_use="Disks To Use" +msg_disks_to_use_help="Choose which disks to use for the Virtual Device (Required)" +msg_force_4k_sectors="Force 4K Sectors?" +msg_force_4k_sectors_help="Use gnop(8) to configure forced 4K sector alignment" +msg_geli_encryption="Encrypt Disks?" +msg_geli_encryption_help="Use geli(8) to encrypt all data partitions" +msg_freebsd_installer="FreeBSD Installer" +msg_invalid_virtual_device_type="Invalid Virtual Device type \`%s'" +msg_last_chance_are_you_sure="Last Chance! Are you sure you want to destroy\nthe current contents of the following disks:\n%s" +msg_mirror_desc="Mirror - n-Way Mirroring" +msg_no="NO" +msg_no_disks_present_to_configure="No disk(s) present to configure" +msg_no_disks_selected="No disks selected." +msg_not_enough_disks_selected="Not enough disks selected (minimum %u)" +msg_ok="OK" +msg_partition_scheme="Partition Scheme" +msg_partition_scheme_help="Toggle between GPT and MBR partitioning schemes" +msg_please_enter_a_name_for_your_zpool="Please enter a name for your zpool:" +msg_please_enter_amount_of_swap_space="Please enter amount of swap space (SI-Unit suffixes\nrecommended; e.g., \`2g' for 2 Gigabytes):" +msg_please_select_one_or_more_disks="Please select one or more disks to create a zpool:" +msg_pool_name="Pool Name" +msg_pool_name_cannot_be_empty="Pool name cannot be empty." +msg_pool_name_help="Customize the name of the zpool to be created (Required)" +msg_raidz1_desc="RAID-Z1 - Single Redundant RAID" +msg_raidz2_desc="RAID-Z2 - Double Redundant RAID" +msg_raidz3_desc="RAID-Z3 - Triple Redundant RAID" +msg_rescan_devices="Rescan Devices" +msg_rescan_devices_help="Scan for device changes" +msg_select_disk_device="Select a disk device" +msg_select_virtual_device_type="Select Virtual Device type:" +msg_stripe_desc="Stripe - No Redundancy" +msg_swap_size="Swap Size" +msg_swap_size_help="Customize how much swap space is allocated to each selected disk" +msg_yes="YES" +msg_zfs_configuration="ZFS Configuration" +msg_zfs_vdev_type="ZFS VDev Type" +msg_zfs_vdev_type_help="Select type of ZFS Virtual Device to create" + +############################################################ FUNCTIONS + +# dialog_menu_main +# +# Display the dialog(1)-based application main menu. +# +dialog_menu_main() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_configure_options" + local force4k="$msg_no" + local usegeli="$msg_no" + [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ] && force4k="$msg_yes" + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && usegeli="$msg_yes" + local menu_list=" + '>>> $msg_create' '$msg_create_desc' + '$msg_create_help' + '- $msg_rescan_devices' '*' + '$msg_rescan_devices_help' + '- $msg_disk_info' '*' + '$msg_disk_info_help' + '1 $msg_pool_name' '$ZFSBOOT_POOL_NAME' + '$msg_pool_name_help' + '2 $msg_disks_to_use' '$ZFSBOOT_DISKS' + '$msg_disks_to_use_help' + '3 $msg_zfs_vdev_type' '$ZFSBOOT_VDEV_TYPE' + '$msg_zfs_vdev_help' + '4 $msg_force_4k_sectors' '$force4k' + '$msg_force_4k_sectors_help' + '5 $msg_geli_encryption' '$usegeli' + '$msg_geli_encryption_help' + '6 $msg_partition_scheme' '$ZFSBOOT_PARTITION_SCHEME' + '$msg_partition_scheme_help' + '7 $msg_swap_size' '$ZFSBOOT_SWAP_SIZE' + '$msg_swap_size_help' + " # END-QUOTE + local defaultitem= # Calculated below + local hline="$hline_alnum_arrows_punc_tab_enter" + + local height width rows + eval f_dialog_menu_with_help_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $menu_list + + # Obtain default-item from previously stored selection + f_dialog_default_fetch defaultitem + + local menu_choice + menu_choice=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --item-help \ + --nook --nocancel \ + --default-item \"\$defaultitem\" \ + --menu \"\$prompt\" \ + $height $width $rows \ + $menu_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) + local retval=$? + f_dialog_data_sanitize menu_choice + f_dialog_menutag_store "$menu_choice" + + # Only update default-item on success + [ $retval -eq 0 ] && f_dialog_default_store "$menu_choice" + + return $retval +} + +# dialog_edit_disks +# +# Edit the list of disks to be used by the ZFS boot pool. +# +dialog_edit_disks() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_please_select_one_or_more_disks" + local check_list= # Calculated below + local hline="$hline_arrows_space_tab_enter" + local dev vardev disks= + + # + # Get a [new] list of disk devices + # + f_device_find "" $DEVICE_TYPE_DISK disks + if [ ! "$disks" ]; then + f_show_msg "$msg_no_disks_present_to_configure" + return $FAILURE + fi + + # Lets sort the disks array to be more user friendly + disks=`echo "$disks" | tr " " "\n" | sort | tr "\n" " "` + + # + # Loop through the list of selected disks and create temporary local + # variables mapping their status onto an up-to-date list of disks. + # + for dev in $ZFSBOOT_DISKS; do + f_str2varname "$dev" vardev + local _${vardev}_status=on + done + + # + # Create the checklist menu of discovered disk devices + # + local on_off + for dev in $disks; do + local desc= + device_$dev get desc desc + f_shell_escape "$desc" desc + f_str2varname "$dev" vardev + f_getvar _${vardev}_status:-off on_off + check_list="$check_list '$dev' '$desc' $on_off" + done + + # + # Prompt the user to check some disks + # + local height width rows + eval f_dialog_checklist_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $check_list + disks=$( eval $DIALOG \ + --title \"\$DIALOG_TITLE\" \ + --backtitle \"\$DIALOG_BACKTITLE\" \ + --hline \"\$hline\" \ + --ok-label \"\$msg_ok\" \ + --cancel-label \"\$msg_cancel\" \ + --checklist \"\$prompt\" \ + $height $width $rows \ + $check_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) || return $? + # Exit if user either pressed ESC or chose Cancel/No + f_dialog_data_sanitize disks + + ZFSBOOT_DISKS="$disks" + + return $SUCCESS +} + +# dialog_menu_vdev +# +# Prompt the user to select a a Virtual Device type. +# +dialog_menu_vdev() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_select_virtual_device_type" + + # Make sure [potentially scripted] selections are real + real_disks= + for disk in $ZFSBOOT_DISKS; do + f_struct device_$disk && real_disks="$real_disks $disk" + done + # Make sure we have at least one real disk selected + ndisks=$( set -- $real_disks; echo $# ) + + local menu_list=" + 'stripe' '$msg_stripe_desc' + " # END-QUOTE + if [ $ndisks -ge 2 ]; then + menu_list="$menu_list 'mirror' '$msg_mirror_desc' + " # END-QUOTE + fi + if [ $ndisks -ge 3 ]; then + menu_list="$menu_list 'raidz1' '$msg_raidz1_desc' + " # END-QUOTE + fi + if [ $ndisks -ge 4 ]; then + menu_list="$menu_list 'raidz2' '$msg_raidz2_desc' + " # END-QUOTE + fi + if [ $ndisks -ge 5 ]; then + menu_list="$menu_list 'raidz3' '$msg_raidz3_desc' + " # END-QUOTE + fi + + local defaultitem="$ZFSBOOT_VDEV_TYPE" + local hline="$hline_arrows_tab_enter" + + local height width rows + eval f_dialog_menu_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $menu_list + + local menu_choice + menu_choice=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --ok-label \"\$msg_ok\" \ + --cancel-label \"\$msg_cancel\" \ + --default-item \"\$defaultitem\" \ + --menu \"\$prompt\" \ + $height $width $rows \ + $menu_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) || return $FAILURE + f_dialog_data_sanitize menu_choice + + ZFSBOOT_VDEV_TYPE="$menu_choice" +} + +# zfs_create_boot $poolname $vdev_type $real_disks ... +# +# Creates boot pool and dataset layout. Returns error if something goes wrong. +# Errors are printed to stderr for collection and display. +# +zfs_create_boot() +{ + local poolname="$1" vdev_type="$2" + local fstab_fmt="%s\t\t%s\t%s\t%s\t\t%s\t%s\n" + local funcname=zfs_create_boot + + shift 2 # name vdev_type + + # We may need this later + local realdisks=$* + + local targetpart=p2 + local bootpart=p2 + + # Pedantic checks; should never be seen + if [ ! "$poolname" ]; then + echo "$funcname: NULL poolname" >&2 + return $FAILURE + fi + if [ $# -lt 1 ]; then + echo "$funcname: missing disk arguments" >&2 + return $FAILURE + fi + + # Initialize fstab(5) + printf "$fstab_fmt" \ + "# Device" Mountpoint FStype Options Dump "Pass#" \ + >> $BSDINSTALL_TMPETC/fstab || return $FAILURE + + # + # For each block device to be used in the zpool, rather than just + # create the zpool with the raw block devices (e.g., da0, da1, etc.) + # we create partitions so we can have some real swap. This also + # provides wiggle room incase your replacement drivers do not have + # the exact same sector counts + # + # The layout for MBR is more complicated, hopefully everyone uses GPT + # + local disk swapsize gelisize partsize n=0 + for disk in $*; do + # Destroy whatever partition layout is currently on disk + # NOTE: `-F' required to destroy if partitions still exist + # Failure is ok here, blank disk will have nothing to destroy + gpart destroy -F $disk 2>&1 > /dev/null + # Kill it with fire + zpool labelclear -f /dev/${disk} + # Suggested by wblock, make sure backup gpt is destroyed + gpart create -s gpt $disk 2>&1 > /dev/null || return $FAILURE + gpart destroy -F $disk 2>&1 > /dev/null || return $FAILURE + + # Calculate the size of the disk + local disksize=`f_disk_size_bytes ${disk}` + # Calculate the size of the swap + f_expand_number "$ZFSBOOT_SWAP_SIZE" swapsize || + return $FAILURE + # Calculate the difference + partsize=$(( $disksize - $swapsize )) + # How big should the unencrypted partition be + f_expand_number "$ZFSBOOT_GELI_BOOT_SIZE" gelisize || + return $FAILURE + + case "$ZFSBOOT_PARTITION_SCHEME" in + ""|GPT) + # 1. Create a GPT layout using labels + # 2. Add a small freebsd-boot partition labeled `boot#' + # 3. Add a freebsd-zfs partition labeled `zfs#' + # 3. Add a 2G freebsd-swap partition labeled `swap#' + # The zpool will use the `zfs#' GPT labels. + # + # Put a GPT scheme on the disk + gpart create -s gpt $disk || return $FAILURE + # Add the `gptboot#' labeled partition + gpart add -l gptboot$n -t freebsd-boot -s 512k $disk || + return $FAILURE + gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 \ + $disk || return $FAILURE + # Change things around if we are using GELI + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + targetpart=p3 + bootpart=p2 + partsize=$(( $partsize - $gelisize )) + gpart add -l boot$n -t freebsd-zfs \ + -s ${gelisize}b -a 1m $disk || + return $FAILURE + # Nuke anything we find here + zpool labelclear -f /dev/${disk}${bootpart} + fi + # Add ZFS partition (to be used in the zpool) + # Use calculated size to leave room for swap + local setsize="-s ${partsize}b" + if [ ! $swapsize -gt 0 ]; then + setsize= + fi + gpart add -l zfs$n -t freebsd-zfs $setsize \ + -a 1m $disk || return $FAILURE + # Nuke anything we find here + zpool labelclear -f /dev/${disk}${targetpart} + + if [ $swapsize -gt 0 ]; then + # Add swap partition (labeled `swap#') + # Uses the rest of the space + gpart add -l swap$n -t freebsd-swap -a 1m \ + $disk || return $FAILURE + # Update fstab(5) + printf "$fstab_fmt" /dev/gpt/swap$n none swap sw 0 0 \ + >> $BSDINSTALL_TMPETC/fstab || \ + return $FAILURE + fi + ;; + MBR) + # 1. Create a MBR layout (no labels) + # 2. Add a freebsd slice with all available space + # 3. write a BSD sceme to the freebsd slice + # 4. Partition the BSD slice for ZFS + # 5. Add a 2G freebsd-swap partition + # + # The zpool will use s1a (no labels) + # + # Put an MBR scheme on the disk + gpart create -s mbr $disk || return $FAILURE + # Write bootcode + gpart bootcode -b /boot/boot0 $disk || return $FAILURE + # Create FreeBSD slice and mark it active + gpart add -t freebsd $disk || return $FAILURE + gpart set -a active -i 1 $disk || return $FAILURE + # Make sure there isn't a hidden BSD partition + gpart destroy -F ${disk}s1 2>&1 > /dev/null + # Create BSD partition table + gpart create -s BSD ${disk}s1 || return $FAILURE + # Change things around if we are using GELI + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + targetpart=s1d + bootpart=s1a + partsize=$(( $partsize - $gelisize )) + gpart add -t freebsd-zfs -s ${gelisize}b \ + ${disk}s1 || return $FAILURE + # Nuke anything we find here + zpool labelclear -f /dev/${disk}${bootpart} + else + targetpart=s1a + bootpart=s1a + fi + # Add ZFS partition (to be used in the zpool) + # Use calculated size to leave room for swap + local setsize="-s ${partsize}b" + if [ ! $swapsize -gt 0 ]; then + setsize= + fi + gpart add -t freebsd-zfs $setsize \ + ${disk}s1 || return $FAILURE + # Nuke anything we find here + zpool labelclear -f /dev/${disk}${targetpart} + + if [ $swapsize -gt 0 ]; then + # Add swap partition, uses the rest of the space + gpart add -t freebsd-swap ${disk}s1 || \ + return $FAILURE + # Update fstab(5) + printf "$fstab_fmt" /dev/${disk}s1b none swap sw 0 0 \ + >> $BSDINSTALL_TMPETC/fstab || \ + return $FAILURE + fi + ;; + *) + printf "%s: %s is an unsupported partition scheme" \ + "$funcname" "$ZFSBOOT_PARTITION_SCHEME" >&2 + return $FAILURE + ;; + esac + n=$(( $n + 1 )) + done + + # MBR boot loader hack part 1 + # We have to do this early because geli gets in the way later + if [ "$ZFSBOOT_PARTITION_SCHEME" = "MBR" ]; then + for disk in $realdisks; do + dd if=/boot/zfsboot of=/dev/${disk}s1 count=1 || + return $FAILURE + done + fi + + # Forced 4k alignment support provided by Geom NOP (see gnop(8)) + local unenc_list= + if [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ]; then + local new_list= + for disk in $*; do + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + # We don't gnop the encrypted partition + # because geli will do this for us + # gnop the unencrypted disk + gnop create -S 4096 ${disk}${bootpart} \ + || return $FAILURE + unenc_list="$unenc_list \ + ${disk}${bootpart}.nop" + else + gnop create -S 4096 ${disk}${targetpart} \ + || return $FAILURE + new_list="$new_list \ + ${disk}${targetpart}.nop" + fi + done + set -- $new_list + else + local new_list= + for disk in $*; do + new_list="$new_list ${disk}${targetpart}" + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + unenc_list="$unenc_list ${disk}${bootpart}" + fi + done + set -- $new_list + fi + + # If encryption is enabled, we need to create the GEOMs + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + ## Create the parent directories for our unencrypted pool + umount /mnt 2>&1 > /dev/null + mount -t tmpfs none ${BSDINSTALL_CHROOT} || return $FAILURE + + # Create mirror across the unencrypted partition on all disks + local bootvdev= + if [ `echo $unenc_list | wc -w` -gt 1 ]; then + bootvdev=mirror + fi + zpool create -o altroot=${BSDINSTALL_CHROOT} \ + -m /$ZFSBOOT_GELI_POOL_NAME \ + -f $ZFSBOOT_GELI_POOL_NAME $bootvdev $unenc_list || + return $FAILURE + mkdir -p ${BSDINSTALL_CHROOT}/$ZFSBOOT_GELI_POOL_NAME/boot || + return $FAILURE + # Generate a random encryption key + dd if=/dev/random \ + of=${BSDINSTALL_CHROOT}/$ZFSBOOT_GELI_POOL_NAME/boot/encryption.key \ + bs=4096 count=1 || return $FAILURE + # Create the geli(8) GEOMS + local geli_list= + for disk in $realdisks; do + geli init -b -B \ + ${BSDINSTALL_CHROOT}/$ZFSBOOT_GELI_POOL_NAME/boot/${disk}${targetpart}.eli \ + -e AES-XTS \ + -K ${BSDINSTALL_CHROOT}/$ZFSBOOT_GELI_POOL_NAME/boot/encryption.key \ + -l 256 -s 4096 ${disk}${targetpart} || + return $FAILURE + geli attach \ + -k ${BSDINSTALL_CHROOT}/$ZFSBOOT_GELI_POOL_NAME/boot/encryption.key \ + ${disk}${targetpart} || + return $FAILURE + geli_list="$geli_list ${disk}${targetpart}.eli" + done + set -- $geli_list + zfs unmount $ZFSBOOT_GELI_POOL_NAME || return $FAILURE + fi + + # + # Create the ZFS pool with desired type and disk devices + # + zpool create -o altroot=$BSDINSTALL_CHROOT -m none -f \ + $poolname $vdevtype $* || return $FAILURE + + # Customize the zpool a bit... + zfs set checksum=fletcher4 $poolname || return $FAILURE + zfs set atime=off $poolname || return $FAILURE + + # + # Create ZFS dataset layout within the new boot pool + # + echo "$ZFSBOOT_DATASETS" | while read dataset options; do + # Skip blank lines and comments + case "$dataset" in "#"*|"") continue; esac + # Remove potential inline comments in options + options="${options%%#*}" + # Replace tabs with spaces + f_replaceall "$options" " " " " foo + # Reduce contiguous runs of space to one single space + oldoptions= + while [ "$oldoptions" != "$options" ]; do + oldoptions="$options" + f_replaceall "$options" " " " " options + done + # Replace both commas and spaces with ` -o ' + f_replaceall "$options" "[ ,]" " -o " options + # Create the dataset with desired options + zfs create ${options:+-o $options} $poolname$dataset || + return $FAILURE + done + + # Touch up permissions on the tmp directories + chmod 1777 $BSDINSTALL_CHROOT/tmp || return $FAILURE + chmod 1777 $BSDINSTALL_CHROOT/var/tmp || return $FAILURE + + if [ "$ZFSBOOT_GELI_ENCRYPTION" ];then + ln -s $ZFSBOOT_GELI_POOL_NAME/boot \ + $BSDINSTALL_CHROOT/boot || return $FAILURE + fi + # Set bootfs property + zpool set bootfs=$poolname/$ZFSBOOT_BEROOT_NAME/$ZFSBOOT_BOOTFS_NAME $poolname || + return $FAILURE + + # Export the pool + zpool export $poolname || return $FAILURE + + if [ "$ZFSBOOT_GELI_ENCRYPTION" ];then + zpool export $ZFSBOOT_GELI_POOL_NAME || return $FAILURE + fi + # Destroy the gnop devices + if [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ]; then + for disk in $realdisks; do + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + gnop destroy ${disk}${bootpart}.nop \ + 2>&1 > /dev/null + else + gnop destroy ${disk}${targetpart}.nop \ + 2>&1 > /dev/null + fi + done + fi + + # MBR boot loader hack part 2 + if [ "$ZFSBOOT_PARTITION_SCHEME" = "MBR" ]; then + # Stick the ZFS boot loader in the "convienient hole" after + # the ZFS internal metadata + for disk in $realdisks; do + dd if=/boot/zfsboot of=/dev/${disk}${bootpart} \ + skip=1 seek=1024 || return $FAILURE + done + fi + + # Re-import the ZFS pool + zpool import -o altroot=$BSDINSTALL_CHROOT $poolname || + return $FAILURE + + if [ "$ZFSBOOT_GELI_ENCRYPTION" ];then + # Re-import the unencrypted pool + zpool import -o altroot=${BSDINSTALL_CHROOT} \ + $ZFSBOOT_GELI_POOL_NAME || + return $FAILURE + fi + + # While this is apparently not needed, it seems to help MBR + mkdir -p ${BSDINSTALL_CHROOT}/boot/zfs || return $FAILURE + zpool set cachefile=${BSDINSTALL_CHROOT}/boot/zfs/zpool.cache \ + $poolname || return $FAILURE + + # Last, but not least... add required lines to rc.conf(5) + # NOTE: We later concatenate these into their destination + echo 'zfs_enable="YES"' > $BSDINSTALL_TMPETC/rc.conf.zfs || + return $FAILURE + echo 'zfs_load="YES"' > $BSDINSTALL_TMPBOOT/loader.conf.zfs || + return $FAILURE + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + echo 'aesni_load="YES"' > \ + $BSDINSTALL_TMPBOOT/loader.conf.aesni || + return $FAILURE + echo 'geom_eli_load="YES"' > \ + $BSDINSTALL_TMPBOOT/loader.conf.geli || + return $FAILURE + echo "vfs.root.mountfrom=\"zfs:$poolname/$ZFSBOOT_BEROOT_NAME/$ZFSBOOT_BOOTFS_NAME\"" > \ + $BSDINSTALL_TMPBOOT/loader.conf.root || + return $FAILURE + for disk in $realdisks; do + echo "geli_${disk}${targetpart}_keyfile0_load=\"YES\"" \ + > $BSDINSTALL_TMPBOOT/loader.conf.${disk}${targetpart} || + return $FAILURE + echo "geli_${disk}${targetpart}_keyfile0_type=\"${disk}${targetpart}:geli_keyfile0\"" \ + >> $BSDINSTALL_TMPBOOT/loader.conf.${disk}${targetpart} || + return $FAILURE + echo "geli_${disk}${targetpart}_keyfile0_name=\"/boot/encryption.key\"" \ + >> $BSDINSTALL_TMPBOOT/loader.conf.${disk}${targetpart} || + return $FAILURE + done + fi + + return $SUCCESS +} + +# dialog_menu_diskinfo +# +# Prompt the user to select a disk and then provide detailed info on it. +# +dialog_menu_diskinfo() +{ + local disk + + # + # Break from loop when user cancels disk selection + # + while :; do + disk=$( f_device_menu "$DIALOG_TITLE" \ + "$msg_select_a_disk_device" "" \ + $DEVICE_TYPE_DISK 2>&1 ) || break + + # Show gpart(8) `show' and camcontrol(8) `inquiry' data + f_show_msg "$msg_detailed_disk_info" \ + "$disk" "$( gpart show $disk 2> /dev/null )" \ + "$disk" "$( camcontrol inquiry $disk 2> /dev/null )" \ + "$disk" "$( camcontrol identify $disk 2> /dev/null )" + done + + return $SUCCESS +} + +############################################################ MAIN + +# +# Initialize +# +f_dialog_title "$msg_zfs_configuration" +f_dialog_backtitle "$msg_freebsd_installer" + +# +# Loop over the main menu until we've accomplished what we came here to do +# +while :; do + dialog_menu_main + retval=$? + f_dialog_menutag_fetch mtag + f_dprintf "retval=%u mtag=[%s]" $reval "$mtag" + + if [ $retval -eq 255 ]; then + # User hit escape + exit 1 + fi + [ $retval -eq 0 ] || f_die + + case "$mtag" in + ">>> $msg_create") + # + # First, validate the user's selections + # + + # Make sure they gave us a name for the pool + if [ ! "$ZFSBOOT_POOL_NAME" ]; then + f_show_msg "$msg_pool_name_cannot_be_empty" + continue + fi + # Make sure [potentially scripted] selections are real + real_disks= + for disk in $ZFSBOOT_DISKS; do + f_struct device_$disk && real_disks="$real_disks $disk" + done + # Make sure we have at least one real disk selected + ndisks=$( set -- $real_disks; echo $# ) + if [ $ndisks -lt 1 ]; then + f_show_msg "$msg_no_disks_selected" + continue + fi + # Make sure we have enough disks for the desired vdev type + case "$ZFSBOOT_VDEV_TYPE" in + stripe) want_disks=1 ;; + mirror) want_disks=2 ;; + raidz1) want_disks=3 ;; + raidz2) want_disks=4 ;; + raidz3) want_disks=5 ;; + *) + f_show_msg "$msg_invalid_virtual_device_type" \ + "$ZFSBOOT_VDEV_TYPE" + continue + ;; + esac + if [ $ndisks -lt $want_disks ]; then + f_show_msg "%s: $msg_not_enough_disks_selected" \ + "$ZFSBOOT_VDEV_TYPE" "$want_disks" + continue + fi + + # + # Last Chance! + # + f_noyes "$msg_last_chance_are_you_sure" "$ZFSBOOT_DISKS" || + continue + + # + # Let's do this + # + + vdev_type="$ZFSBOOT_VDEV_TYPE" + + # Blank the vdev type for the default layout + [ "$vdev_type" = "stripe" ] && vdev_type= + + if ! error=$( zfs_create_boot "$ZFSBOOT_POOL_NAME" \ + "$vdev_type" $real_disks 2>&1 ) + then + f_dialog_msgbox "$error" + continue + fi + + break # to success + ;; + "- $msg_rescan_devices") f_device_rescan ;; + "- $msg_disk_info") dialog_menu_diskinfo ;; + ?" $msg_pool_name") + # Prompt the user to input/change the name for the new pool + f_dialog_input input \ + "$msg_please_enter_a_name_for_your_zpool" && + ZFSBOOT_POOL_NAME="$input" + ;; + ?" $msg_disks_to_use") dialog_edit_disks ;; + ?" $msg_zfs_vdev_type") dialog_menu_vdev ;; + ?" $msg_force_4k_sectors") + # Toggle the variable referenced both by the menu and later + if [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ]; then + ZFSBOOT_GNOP_4K_FORCE_ALIGN= + else + ZFSBOOT_GNOP_4K_FORCE_ALIGN=1 + fi + ;; + ?" $msg_geli_encryption") + # Toggle the variable referenced both by the menu and later + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + ZFSBOOT_GELI_ENCRYPTION= + else + ZFSBOOT_GELI_ENCRYPTION=1 + fi + ;; + ?" $msg_partition_scheme") + # Toggle between GPT and MBR + if [ "$ZFSBOOT_PARTITION_SCHEME" = GPT ]; then + ZFSBOOT_PARTITION_SCHEME=MBR + else + ZFSBOOT_PARTITION_SCHEME=GPT + fi + ;; + ?" $msg_swap_size") + # Prompt the user to input/change the swap size for each disk + f_dialog_input input \ + "$msg_please_enter_amount_of_swap_space" && + ZFSBOOT_SWAP_SIZE="$input" + ;; + esac +done + +return $SUCCESS + +################################################################################ +# END +################################################################################ Property changes on: usr.sbin/bsdinstall/scripts/zfsboot ___________________________________________________________________ Added: svn:executable ## -0,0 +1 ## +* \ No newline at end of property --------------000300000003070506000001-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:48:11 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0AC49B74; Mon, 7 Oct 2013 21:48:11 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C369426C4; Mon, 7 Oct 2013 21:48:10 +0000 (UTC) Received: by mail-ie0-f181.google.com with SMTP id tp5so17113692ieb.40 for ; Mon, 07 Oct 2013 14:48:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=5ZCsJimB8igfSs14QSZAI2/zVkXADggJ1ZPkSJE713o=; b=rZOuaQ/K4z9uJAOexqnQRE4YmL+oGnCOEtQk+dWckKiCn1EcMFx8g7F7Vh9LTGTjvc WcpwIFDplaL2AAIEzkUgf+x+R0pmTj69Vgw9UBOfhTRKO/oRo7wi2om27sPWTKlC1UYS z0ezgDAY1STIf4Pt/mMLeEpmsbm8cu04PW11Y1vXOz+zj5ADirSMm7dKt5HClMPK4q9k mrbDaUM30HiHJAaVYcaGBfdnPKvxtJfmTxGXalt5kfZyYrgTFv5/X0sOj0BxPpBVpsen URhqdkNF2EnWVB1UEG+8PeZ4YI7OgWBpz13OmQgBvdUrDmsg4m3ukKPphxkJSDuQeswQ PFwA== X-Received: by 10.50.22.67 with SMTP id b3mr18852313igf.39.1381182489694; Mon, 07 Oct 2013 14:48:09 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.64.89.1 with HTTP; Mon, 7 Oct 2013 14:47:28 -0700 (PDT) In-Reply-To: <22543819.20131008012839@serebryakov.spb.ru> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <22543819.20131008012839@serebryakov.spb.ru> From: Igor Mozolevsky Date: Mon, 7 Oct 2013 22:47:28 +0100 X-Google-Sender-Auth: sdinBwRJyBgUREjEjm6uw9DOxj0 Message-ID: Subject: Re: rcs is gone? To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" , Andreas Nilsson X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:48:11 -0000 On 7 October 2013 22:28, Lev Serebryakov wrote: svnlite? :) > Thanks Lev & Glen- it's something to explore albeit that screws up quite a lot of stuff on this end... Cheers, -- Igor M. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:49:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C7328C8D for ; Mon, 7 Oct 2013 21:49:09 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 907FA26D7 for ; Mon, 7 Oct 2013 21:49:09 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa01.fnfis.com (8.14.5/8.14.5) with ESMTP id r97Ln4Ju006369 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 7 Oct 2013 16:49:04 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Mon, 7 Oct 2013 16:49:03 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOw6cJPJPIP8ZCyUiSsjBzr2++AA== Date: Mon, 7 Oct 2013 21:49:03 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC3F623@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> <52532BD8.2070509@allanjude.com> In-Reply-To: <52532BD8.2070509@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-07_04:2013-10-07,2013-10-07,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:49:09 -0000 On Oct 7, 2013, at 2:47 PM, Allan Jude wrote: > On 2013-10-07 17:00, Outback Dingo wrote: >> On Mon, Oct 7, 2013 at 4:54 PM, Allan Jude wrote: >>=20 >>> On 2013-10-07 16:43, Warren Block wrote: >>>> On Mon, 7 Oct 2013, Allan Jude wrote: >>>>=20 >>>>> Additional, it includes some other changes to bsdinstall: >>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>>>> to no >>>> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/162175 . >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@freebsd.org" >>> That is a good idea, I'll add that >>>=20 >>> I've also hit this: >>>=20 >>> http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/00= 0949.html >>> and plan to throw in a fix for that. >>> Which makes more sense, blindly 'killall dhclient' before we try to >>> acquire a new lease, or detect that dhclient is running and try to use >>> the IP that has already been assigned? >>>=20 >>>=20 >>>=20 >> jeeeeeez after i just updated and patched my source tree to do a build, = you >> go and fix things :P >> anyway you can just generate a master diff against the tree that we can >> apply, seems not ive to >> revert the patches and reapply all the newest ones. >>=20 >>=20 >>> -- >>> Allan Jude >>>=20 >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >>>=20 >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g" >=20 > Attached find the patch from last night against a fresh HEAD >=20 > I am working on incorporating Warren's patch now >=20 ... and I'm working to review and validate what Allan is writing ;D A couple of big patches to incorporate within the hour (next 15 minutes). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:53:34 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2BB46E6C for ; Mon, 7 Oct 2013 21:53:34 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EE0F32725 for ; Mon, 7 Oct 2013 21:53:33 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r97LrUBe006835 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 21:53:32 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: rcs is gone? From: David Chisnall In-Reply-To: Date: Mon, 7 Oct 2013 22:53:25 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> To: Lyndon Nerenberg X-Mailer: Apple Mail (2.1508) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:53:34 -0000 On 7 Oct 2013, at 22:14, Lyndon Nerenberg wrote: > "Install from ports" is a non-starter. Our development systems will = never be connected to the internet for a ports upgrade. In this = environment, in-base RCS is a very useful tool. Why is install from packages any harder than installing the base system? = If you need RCS, then put the pkg and rcs packages in your default = installation image. Or do you really only run the base OS and no other software on your = systems, without any of your own code or any customisation? David From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:01:00 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7D1BF481; Mon, 7 Oct 2013 22:01:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E819127AD; Mon, 7 Oct 2013 22:00:59 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id l18so5578064wgh.2 for ; Mon, 07 Oct 2013 15:00:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=jinbu5m924LawumHJ6aDZOYoORfRmPaz6v3TC60ffOM=; b=qu4HNMczWQPCwvLowU2dtXF84lp30V6dw4qFIIJxrkzQjFPuDmizjHBBYtxogqcTi5 71QVshAwHmI51KPexA1VkQBJmJkY/dzGPgFLTZqMI+dXPsva9iWb8pE8zC3IB+ArMXh0 LjxXiKk2D8QEPN8qI+yaWbZPruLCF/MkWdjcxptWv1z6OfA9rtnRifpAJd6XbTlIb7R+ JodN2yqnpWoJQCohoopl6RjCalqqwOZxiBE1aXVDuJGc14KD3jKUI0TxZ7lg3y+IcxYg AZN0QsA4IhB8a24WgWnEtmnVFrvqxyO92Dc0SfkM64atIZ7q47QUz22JLXhQQiwpChyd npyw== MIME-Version: 1.0 X-Received: by 10.180.10.136 with SMTP id i8mr21310444wib.46.1381183258133; Mon, 07 Oct 2013 15:00:58 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.73.133 with HTTP; Mon, 7 Oct 2013 15:00:58 -0700 (PDT) In-Reply-To: <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> Date: Mon, 7 Oct 2013 15:00:58 -0700 X-Google-Sender-Auth: RyANMA_A7OkHFv6_Hk9aIMnbjuQ Message-ID: Subject: Re: rcs is gone? From: Adrian Chadd To: David Chisnall Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" , Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:01:00 -0000 .. don't be surprised how many people do exactly this; then compile what handful of things they need from source in order to make a server. -adrian On 7 October 2013 14:53, David Chisnall wrote: > On 7 Oct 2013, at 22:14, Lyndon Nerenberg wrote: > > > "Install from ports" is a non-starter. Our development systems will > never be connected to the internet for a ports upgrade. In this > environment, in-base RCS is a very useful tool. > > Why is install from packages any harder than installing the base system? > If you need RCS, then put the pkg and rcs packages in your default > installation image. > > Or do you really only run the base OS and no other software on your > systems, without any of your own code or any customisation? > > David > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:14:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4B30ABE for ; Mon, 7 Oct 2013 22:14:15 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AF6B02881 for ; Mon, 7 Oct 2013 22:14:15 +0000 (UTC) Received: by mail-pb0-f44.google.com with SMTP id xa7so7747085pbc.31 for ; Mon, 07 Oct 2013 15:14:15 -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=dtzhhB6eUeDwA1S60Ccu+zzNNHTNdF4qto8dhDjK/Nw=; b=Mk7OfPZ8BM4wD2urL2+7q3XJ8KVJ4AR+pHaPIxEq9mNNippbYd3qsyWaEoZGh007rp KyD5YMQmurXvjtbuNDr1V4RabJBxOtFcZ7W4Q2aVxeXDDmYUWJ4bzR9uKtyafn76OH0t 1ucFYkbOMk6ZJd+a/J58zjWyYg8daVJGoDY3ZcmMpXC2adxNJckcNsMlJP/z3Ni6cFu+ nfaT1OF+K8UEdYdoD5rmm8FIAb780cO8SHMCc/CrvFdfOKjfmD7l7hepX+sZg+P6oIxq aHGaTXROWM8G9ulx/p2cC4S3ezkhWnLo5paxqGK2Ijtwbsx5zyl56W9JJHqPXK4Wpowr oaDw== MIME-Version: 1.0 X-Received: by 10.68.129.40 with SMTP id nt8mr25269309pbb.108.1381184055163; Mon, 07 Oct 2013 15:14:15 -0700 (PDT) Received: by 10.70.23.225 with HTTP; Mon, 7 Oct 2013 15:14:15 -0700 (PDT) In-Reply-To: References: Date: Tue, 8 Oct 2013 02:14:15 +0400 Message-ID: Subject: Re: [Heads Up] RCS removed from base From: Subbsd To: Eitan Adler Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:14:15 -0000 On Mon, Oct 7, 2013 at 6:43 AM, Eitan Adler wrote: > Hey all, > > RCS was removed from the base system in r256095. If you still want to > use RCS please install either devel/rcs or devel/rcs57. If not, be > sure to check out the alternatives (pun stolen and intended). > > rc.subr use rcs in backup_file function which no one uses. Maybe remove backup_f=D1=96le that it does not provoke any errors? From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:15:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 587A3CE7; Mon, 7 Oct 2013 22:15:40 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0570128A8; Mon, 7 Oct 2013 22:15:39 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id c3so5415090qcv.32 for ; Mon, 07 Oct 2013 15:15:39 -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=pHNjOlis3KeZD9SBQX6sH0V8da1dpfJMCuT3FZ9Tf7I=; b=LBzA+LWXYwU7XiZXlZHdIYyZYJ3tnSObP/AP9o6q8vhWhtV9lQ9bWLFiqzoHGYztnh VTcqmAf0u3U37ZFjBSx4RZ//kN5+apHKceRcj03Vq4XbPUoaBYhM+N4soOjXD1VW1QUW LnGOx/fbS4bL/BOFKGc70zu3KndRezd8Iyqg/N7rkC6FLt6WWLzo9QJYEc8SquADqcES w115hFoV5OjkA15c62UaZ729VOpTC2EE/kQvRMUZDa0q+pPfAsUvP2Gq7lUTY/2tWH8u TMWdlqlthlnlDlI6pjURox0uFqFeS8QLdqvDby933fk/pkaxX0m895CDKKj7aaxpiiPF evwg== MIME-Version: 1.0 X-Received: by 10.49.39.39 with SMTP id m7mr39649395qek.60.1381184139147; Mon, 07 Oct 2013 15:15:39 -0700 (PDT) Received: by 10.49.39.33 with HTTP; Mon, 7 Oct 2013 15:15:39 -0700 (PDT) In-Reply-To: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <22543819.20131008012839@serebryakov.spb.ru> Date: Mon, 7 Oct 2013 15:15:39 -0700 Message-ID: Subject: Re: rcs is gone? From: Freddie Cash To: Igor Mozolevsky Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: lev@freebsd.org, Andreas Nilsson , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:15:40 -0000 On Mon, Oct 7, 2013 at 2:47 PM, Igor Mozolevsky wrote: > On 7 October 2013 22:28, Lev Serebryakov wrote: > > svnlite? :) > > > > Thanks Lev & Glen- it's something to explore albeit that screws up quite a > lot of stuff on this end... > Why does that screw up anything? Just include the RCS package on your install media, and add "pkg_add /path/to/rcs.tgz" or "pkg add /path/to/rcs.txz" to the end of your install script. 1 extra tarball, 1 extra line in your install script, and everything carries on as before. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:21:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7C440FFA for ; Mon, 7 Oct 2013 22:21:44 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 444332909 for ; Mon, 7 Oct 2013 22:21:44 +0000 (UTC) Received: by mail-oa0-f43.google.com with SMTP id j10so3935653oah.2 for ; Mon, 07 Oct 2013 15:21:43 -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=eP+SUa7w5VHcmW3KIPBDX81lPY8VN4QSUgs1wvW58eQ=; b=L4f0lPb9Y4KfpkYZ2fKxY4bNqURUUxlJ8bya+qiAIhEpGvGlDI9F6Kqttn/uBl0pBI dqZXSaA1BPtXr+NRR3TFHUg+fWpFA+Vc0bozKjAp9t0nDSsbDwJTlHiSSd3tNyQX1E0e 0erRPydp7g1zfr/9uPvvMG+Uay4MrXwdkn5I1xWfP/MMOPtaigvE1c7J2xAiFLNernao M/IwG0PRgH7JXguBpdcUoZyyjojjAhhNfUwDgAr2ntwDG8NyORSMXMDwY/zbfI0T4SkA GM4IIdsL18ia6E5dRPVcFYAnLQ71Q3qb6jHZmIckgb0prxqQT+ihmUEofcsuaEapd47Z vPOg== MIME-Version: 1.0 X-Received: by 10.60.103.37 with SMTP id ft5mr4500259oeb.45.1381184503463; Mon, 07 Oct 2013 15:21:43 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Mon, 7 Oct 2013 15:21:43 -0700 (PDT) In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC3F623@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> <52532BD8.2070509@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC3F623@LTCFISWMSGMB21.FNFIS.com> Date: Mon, 7 Oct 2013 18:21:43 -0400 Message-ID: Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI From: Outback Dingo To: "Teske, Devin" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "" , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:21:44 -0000 On Mon, Oct 7, 2013 at 5:49 PM, Teske, Devin wrote: > > On Oct 7, 2013, at 2:47 PM, Allan Jude wrote: > > > On 2013-10-07 17:00, Outback Dingo wrote: > >> On Mon, Oct 7, 2013 at 4:54 PM, Allan Jude > wrote: > >> > >>> On 2013-10-07 16:43, Warren Block wrote: > >>>> On Mon, 7 Oct 2013, Allan Jude wrote: > >>>> > >>>>> Additional, it includes some other changes to bsdinstall: > >>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt > >>>>> to no > >>>> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 . > >>>> _______________________________________________ > >>>> freebsd-current@freebsd.org mailing list > >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>> To unsubscribe, send any mail to > >>>> "freebsd-current-unsubscribe@freebsd.org" > >>> That is a good idea, I'll add that > >>> > >>> I've also hit this: > >>> > >>> > http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html > >>> and plan to throw in a fix for that. > >>> Which makes more sense, blindly 'killall dhclient' before we try to > >>> acquire a new lease, or detect that dhclient is running and try to use > >>> the IP that has already been assigned? > >>> > >>> > >>> > >> jeeeeeez after i just updated and patched my source tree to do a build, > you > >> go and fix things :P > >> anyway you can just generate a master diff against the tree that we can > >> apply, seems not ive to > >> revert the patches and reapply all the newest ones. > >> > >> > >>> -- > >>> Allan Jude > >>> > >>> _______________________________________________ > >>> freebsd-current@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > >>> > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > > Attached find the patch from last night against a fresh HEAD > > > > I am working on incorporating Warren's patch now > > > > ... and I'm working to review and validate what Allan is writing ;D > > A couple of big patches to incorporate within the hour (next 15 minutes). > okies dokies guess ill revert it all and wait till you guys give the green light to try again > -- > Devin > > _____________ > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete the > message and all copies; (ii) do not disclose, distribute or use the message > in any manner; and (iii) notify the sender immediately. In addition, please > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:23:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6D43F2E5 for ; Mon, 7 Oct 2013 22:23:10 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (unknown [IPv6:2001:610:1108:5012::107]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 157312924 for ; Mon, 7 Oct 2013 22:23:10 +0000 (UTC) Received: from turtle.stack.nl (turtle.stack.nl [IPv6:2001:610:1108:5010::132]) by mx1.stack.nl (Postfix) with ESMTP id E31671203D8; Tue, 8 Oct 2013 00:22:51 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 1677) id B95DBCB4E; Tue, 8 Oct 2013 00:22:51 +0200 (CEST) Date: Tue, 8 Oct 2013 00:22:51 +0200 From: Jilles Tjoelker To: Eitan Adler Subject: Re: [Heads Up] RCS removed from base Message-ID: <20131007222251.GA541@stack.nl> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:23:10 -0000 On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: > RCS was removed from the base system in r256095. If you still want to > use RCS please install either devel/rcs or devel/rcs57. If not, be > sure to check out the alternatives (pun stolen and intended). Thanks for removing this piece of old GPL software. Perhaps a rewrite of ident(1) should be added, since Subversion still uses this keyword syntax and does not provide a utility to print keywords from a file that is not part of a Subversion checkout. This could be a shell script based on a command like strings "$f" | sed -n -e 's/^.*\(\$[[:alpha:]]*[[:alpha:]]: [^$]*\$\).*$/\1/p' or a C program (like what(1)). Likewise, merge(1) can be useful without RCS itself. However, consensus across operating system integrators appears to be that this functionality is best built into version control systems and not provided separately. -- Jilles Tjoelker From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:25:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E5625441 for ; Mon, 7 Oct 2013 22:25:18 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AE5F12957 for ; Mon, 7 Oct 2013 22:25:18 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa02.fnfis.com (8.14.5/8.14.5) with ESMTP id r97MPFsN030969 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 7 Oct 2013 17:25:15 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.02.0309.002; Mon, 7 Oct 2013 17:25:14 -0500 From: "Teske, Devin" To: Outback Dingo Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOw6cJPJPIP8ZCyUiSsjBzr2++AA== Date: Mon, 7 Oct 2013 22:25:14 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC3F901@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> <52532BD8.2070509@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC3F623@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <8088302A46E9384CA43157F74B1115C2@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-07_04:2013-10-07,2013-10-07,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:25:19 -0000 On Oct 7, 2013, at 3:21 PM, Outback Dingo wrote: >=20 >=20 >=20 > On Mon, Oct 7, 2013 at 5:49 PM, Teske, Devin = wrote: >=20 > On Oct 7, 2013, at 2:47 PM, Allan Jude wrote: >=20 > > On 2013-10-07 17:00, Outback Dingo wrote: > >> On Mon, Oct 7, 2013 at 4:54 PM, Allan Jude wro= te: > >> > >>> On 2013-10-07 16:43, Warren Block wrote: > >>>> On Mon, 7 Oct 2013, Allan Jude wrote: > >>>> > >>>>> Additional, it includes some other changes to bsdinstall: > >>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt > >>>>> to no > >>>> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/162175 . > >>>> _______________________________________________ > >>>> freebsd-current@freebsd.org mailing list > >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>> To unsubscribe, send any mail to > >>>> "freebsd-current-unsubscribe@freebsd.org" > >>> That is a good idea, I'll add that > >>> > >>> I've also hit this: > >>> > >>> http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/= 000949.html > >>> and plan to throw in a fix for that. > >>> Which makes more sense, blindly 'killall dhclient' before we try to > >>> acquire a new lease, or detect that dhclient is running and try to use > >>> the IP that has already been assigned? > >>> > >>> > >>> > >> jeeeeeez after i just updated and patched my source tree to do a build= , you > >> go and fix things :P > >> anyway you can just generate a master diff against the tree that we can > >> apply, seems not ive to > >> revert the patches and reapply all the newest ones. > >> > >> > >>> -- > >>> Allan Jude > >>> > >>> _______________________________________________ > >>> freebsd-current@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd= .org" > >>> > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.= org" > > > > Attached find the patch from last night against a fresh HEAD > > > > I am working on incorporating Warren's patch now > > >=20 > ... and I'm working to review and validate what Allan is writing ;D >=20 > A couple of big patches to incorporate within the hour (next 15 minutes). >=20 > okies dokies guess ill revert it all and wait till you guys give the gree= n light to try again >=20=20 Thanks... you know... Allan is giving me a work-out. He's running like the = wind and I'm trying to catch my breath as he I trail behind him. Go Allan Go! ;D --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:26:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F070F5A1; Mon, 7 Oct 2013 22:26:49 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AD89D2976; Mon, 7 Oct 2013 22:26:49 +0000 (UTC) Received: from [192.168.0.15] (coleburn.home.andric.com [192.168.0.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id A07BA5C5A; Tue, 8 Oct 2013 00:26:47 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_8154AB34-D7D5-4EDE-9369-B144B341F3E6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: CURRENT BUILD FAILURE sys/modules/cxgbe From: Dimitry Andric In-Reply-To: Date: Tue, 8 Oct 2013 00:26:45 +0200 Message-Id: <1B5DCBF6-A6E4-4D34-AB86-0195174296C6@FreeBSD.org> References: <1381179611.1130.19.camel@revolution.hippie.lan> To: Outback Dingo X-Mailer: Apple Mail (2.1510) Cc: "freebsd-current@freebsd.org CURRENT" , Ian Lepore , Paul Webster X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:26:50 -0000 --Apple-Mail=_8154AB34-D7D5-4EDE-9369-B144B341F3E6 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On Oct 7, 2013, at 23:04, Outback Dingo wrote: > On Mon, Oct 7, 2013 at 5:00 PM, Ian Lepore wrote: > >> On Mon, 2013-10-07 at 16:52 -0400, Outback Dingo wrote: >>> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE >> -nostdinc >>> -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe >>> -DHAVE_KERNEL_OPTION_HEADERS -include >>> /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq >>> -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer >>> -I/usr/obj/usr/src/sys/GENERIC -mno-aes -mno-avx -mcmodel=kernel >>> -mno-red-zone -mno-mmx -mno-sse -msoft-float >>> -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector >>> -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall >>> -Wredundant-decls -Wnested-externs -Wstrict-prototypes >>> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef >>> -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs >>> -fdiagnostics-show-option -Wno-error-tautological-compare >>> -Wno-error-empty-body -Wno-error-parentheses-equality -c >>> /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c >>> /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:228:12: >>> error: use of undeclared identifier 'cpu_clflush_line_size' >>> pad = max(cpu_clflush_line_size, 16); >>> ^ >>> /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:273:9: >>> error: use of undeclared identifier 'cpu_clflush_line_size' >>> len = cpu_clflush_line_size > 64 ? 128 : 64; >>> ^ >>> 2 errors generated. >> >> Fixed in r256118. >> > > odd i show that commit in my svn log however, kernel build still fails My bad, the fix for gcc I committed in r256118 does not work on amd64, since the headers work differently there. I will commit a fix ASAP. -Dimitry --Apple-Mail=_8154AB34-D7D5-4EDE-9369-B144B341F3E6 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iEYEARECAAYFAlJTNSUACgkQsF6jCi4glqP76wCg/KOYTzt0XwkgQSckYW9afBxq TdEAnAsc6tqzzA3gY9xSBZaNqIYsYPzB =3a1P -----END PGP SIGNATURE----- --Apple-Mail=_8154AB34-D7D5-4EDE-9369-B144B341F3E6-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:30:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9D44085A for ; Mon, 7 Oct 2013 22:30:21 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 5B0EB29A7 for ; Mon, 7 Oct 2013 22:30:20 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id AEE2B1D608 for ; Mon, 7 Oct 2013 22:30:17 +0000 (UTC) Message-ID: <52533611.1000403@allanjude.com> Date: Mon, 07 Oct 2013 18:30:41 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> <52532BD8.2070509@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC3F623@LTCFISWMSGMB21.FNFIS.com> <13CA24D6AB415D428143D44749F57D720FC3F901@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC3F901@LTCFISWMSGMB21.FNFIS.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:30:21 -0000 On 2013-10-07 18:25, Teske, Devin wrote: > On Oct 7, 2013, at 3:21 PM, Outback Dingo wrote: > >> >> >> On Mon, Oct 7, 2013 at 5:49 PM, Teske, Devin wrote: >> >> On Oct 7, 2013, at 2:47 PM, Allan Jude wrote: >> >>> On 2013-10-07 17:00, Outback Dingo wrote: >>>> On Mon, Oct 7, 2013 at 4:54 PM, Allan Jude wrote: >>>> >>>>> On 2013-10-07 16:43, Warren Block wrote: >>>>>> On Mon, 7 Oct 2013, Allan Jude wrote: >>>>>> >>>>>>> Additional, it includes some other changes to bsdinstall: >>>>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>>>>>> to no >>>>>> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 . >>>>>> _______________________________________________ >>>>>> freebsd-current@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>> To unsubscribe, send any mail to >>>>>> "freebsd-current-unsubscribe@freebsd.org" >>>>> That is a good idea, I'll add that >>>>> >>>>> I've also hit this: >>>>> >>>>> http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html >>>>> and plan to throw in a fix for that. >>>>> Which makes more sense, blindly 'killall dhclient' before we try to >>>>> acquire a new lease, or detect that dhclient is running and try to use >>>>> the IP that has already been assigned? >>>>> >>>>> >>>>> >>>> jeeeeeez after i just updated and patched my source tree to do a build, you >>>> go and fix things :P >>>> anyway you can just generate a master diff against the tree that we can >>>> apply, seems not ive to >>>> revert the patches and reapply all the newest ones. >>>> >>>> >>>>> -- >>>>> Allan Jude >>>>> >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>>>> >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>> Attached find the patch from last night against a fresh HEAD >>> >>> I am working on incorporating Warren's patch now >>> >> ... and I'm working to review and validate what Allan is writing ;D >> >> A couple of big patches to incorporate within the hour (next 15 minutes). >> >> okies dokies guess ill revert it all and wait till you guys give the green light to try again >> > Thanks... you know... Allan is giving me a work-out. He's running like the wind and > I'm trying to catch my breath as he I trail behind him. > > Go Allan Go! > > ;D I make it work, Devin makes it pretty. Then he makes it so it is useful to other people. Then he makes an API out of it, with C style structs in SH. Then he does some other wizardry. It is quite impressive. -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:38:33 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 74572C94; Mon, 7 Oct 2013 22:38:33 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3B48E2AAB; Mon, 7 Oct 2013 22:38:32 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r97McPUY063884; Mon, 7 Oct 2013 18:38:25 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r97McPSv063875; Mon, 7 Oct 2013 22:38:25 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 7 Oct 2013 22:38:25 GMT Message-Id: <201310072238.r97McPSv063875@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on amd64/amd64 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:38:33 -0000 TB --- 2013-10-07 18:40:22 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-07 18:40:22 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-10-07 18:40:22 - starting HEAD tinderbox run for amd64/amd64 TB --- 2013-10-07 18:40:22 - cleaning the object tree TB --- 2013-10-07 18:40:22 - /usr/local/bin/svn stat /src TB --- 2013-10-07 18:40:27 - At svn revision 256119 TB --- 2013-10-07 18:40:28 - building world TB --- 2013-10-07 18:40:28 - CROSS_BUILD_TESTING=YES TB --- 2013-10-07 18:40:28 - MAKEOBJDIRPREFIX=/obj TB --- 2013-10-07 18:40:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-10-07 18:40:28 - SRCCONF=/dev/null TB --- 2013-10-07 18:40:28 - TARGET=amd64 TB --- 2013-10-07 18:40:28 - TARGET_ARCH=amd64 TB --- 2013-10-07 18:40:28 - TZ=UTC TB --- 2013-10-07 18:40:28 - __MAKE_CONF=/dev/null TB --- 2013-10-07 18:40:28 - cd /src TB --- 2013-10-07 18:40:28 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Mon Oct 7 18:40:37 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Oct 7 22:29:10 UTC 2013 TB --- 2013-10-07 22:29:10 - generating LINT kernel config TB --- 2013-10-07 22:29:10 - cd /src/sys/amd64/conf TB --- 2013-10-07 22:29:10 - /usr/bin/make -B LINT TB --- 2013-10-07 22:29:10 - cd /src/sys/amd64/conf TB --- 2013-10-07 22:29:10 - /usr/sbin/config -m LINT TB --- 2013-10-07 22:29:10 - building LINT kernel TB --- 2013-10-07 22:29:10 - CROSS_BUILD_TESTING=YES TB --- 2013-10-07 22:29:10 - MAKEOBJDIRPREFIX=/obj TB --- 2013-10-07 22:29:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-10-07 22:29:10 - SRCCONF=/dev/null TB --- 2013-10-07 22:29:10 - TARGET=amd64 TB --- 2013-10-07 22:29:10 - TARGET_ARCH=amd64 TB --- 2013-10-07 22:29:10 - TZ=UTC TB --- 2013-10-07 22:29:10 - __MAKE_CONF=/dev/null TB --- 2013-10-07 22:29:10 - cd /src TB --- 2013-10-07 22:29:10 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Oct 7 22:29:10 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-body -Wno-error-parentheses-equality -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -DGPROF -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg /src/sys/dev/cxgbe/t4_sge.c -I/src/sys/dev/cxgbe /src/sys/dev/cxgbe/t4_sge.c:228:12: error: use of undeclared identifier 'cpu_clflush_line_size' pad = max(cpu_clflush_line_size, 16); ^ /src/sys/dev/cxgbe/t4_sge.c:273:9: error: use of undeclared identifier 'cpu_clflush_line_size' len = cpu_clflush_line_size > 64 ? 128 : 64; ^ 2 errors generated. *** Error code 1 Stop. bmake[1]: stopped in /obj/amd64.amd64/src/sys/LINT *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-10-07 22:38:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-10-07 22:38:25 - ERROR: failed to build LINT kernel TB --- 2013-10-07 22:38:25 - 11075.36 user 2371.61 system 14282.78 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:45:28 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B3A17D2; Mon, 7 Oct 2013 22:45:28 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 884AA2B51; Mon, 7 Oct 2013 22:45:28 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r97MjOJS025288 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 15:45:26 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> Date: Mon, 7 Oct 2013 15:45:23 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> To: David Chisnall X-Mailer: Apple Mail (2.1510) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:45:28 -0000 On 2013-10-07, at 2:53 PM, David Chisnall wrote: > Or do you really only run the base OS and no other software on your = systems, without any of your own code or any customisation? We install from the base release ISO images burned on DVDs. We are physically air-gapped from the internet, none of the "end users" = of the system have access to USB ports, and there are no electronic = devices allowed into the development shop. We have a scheme for bringing in software from /usr/ports, but it is = painful. And those ports can't necessarily walk on to all the systems = in the shop. (I don't make the rules. Suffice to say the company is = very paranoid about their code getting out into the wild.) Having RCS in the base system is very useful. We use it to track = changes to bits of /etc on the machines where we don't do wholesale = customizations. (Those ones get git, but they also get an install of = /usr/ports with a fully populated /usr/ports/distfiles.) So if nuking RCS is a case of "I don't use it," ... we do. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:55:15 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 144A62C5; Mon, 7 Oct 2013 22:55:15 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (unknown [IPv6:2620:64:0:1:223:7dff:fea2:c8f2]) by mx1.freebsd.org (Postfix) with ESMTP id ED6422BBA; Mon, 7 Oct 2013 22:55:14 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 6471A2AA4A0; Mon, 7 Oct 2013 16:55:12 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id 91F051CC17; Mon, 7 Oct 2013 17:54:44 -0500 (EST) Date: Mon, 7 Oct 2013 17:54:44 -0500 From: Diane Bruce To: Lyndon Nerenberg Subject: Re: rcs is gone? Message-ID: <20131007225444.GA31518@night.db.net> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-current@freebsd.org" , David Chisnall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:55:15 -0000 On Mon, Oct 07, 2013 at 03:45:23PM -0700, Lyndon Nerenberg wrote: > > On 2013-10-07, at 2:53 PM, David Chisnall wrote: > > > Or do you really only run the base OS and no other software on your systems, without any of your own code or any customisation? > > We install from the base release ISO images burned on DVDs. > > We are physically air-gapped from the internet, none of the "end users" of the system have access to USB ports, and there are no electronic devices allowed into the development shop. > > We have a scheme for bringing in software from /usr/ports, but it is painful. And those ports can't necessarily walk on to all the systems in the shop. (I don't make the rules. Suffice to say the company is very paranoid about their code getting out into the wild.) > > Having RCS in the base system is very useful. We use it to track changes to bits of /etc on the machines where we don't do wholesale customizations. (Those ones get git, but they also get an install of /usr/ports with a fully populated /usr/ports/distfiles.) > > So if nuking RCS is a case of "I don't use it," ... we do. > Hey we could imoort SCCS instead. http://sccs.berlios.de - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 22:57:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2473F3F9; Mon, 7 Oct 2013 22:57:18 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A3A1D2BD3; Mon, 7 Oct 2013 22:57:16 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBE81A.dip0.t-ipconnect.de [217.251.232.26]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r97MvEWx047465; Mon, 7 Oct 2013 22:57:14 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r97Mv1ts045210; Tue, 8 Oct 2013 00:57:01 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r97Mug2q017915; Tue, 8 Oct 2013 00:56:48 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310072256.r97Mug2q017915@fire.js.berklix.net> To: Gleb Kurtsou Subject: Re: Committing PEFS to CURRENT From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Mon, 07 Oct 2013 13:26:23 PDT." Date: Tue, 08 Oct 2013 00:56:42 +0200 Sender: jhs@berklix.com Cc: "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 22:57:18 -0000 Gleb Kurtsou wrote: > On Mon, Oct 7, 2013 at 12:58 PM, Julian H. Stacey wrote: > > Hi Gleb & All > > Gleb Kurtsou wrote: > >> Hello, > >> > >> I would like to ask everybody's opinion regarding committing PEFS to > >> CURRENT. > >> > >> PEFS is a stacked cryptographic file system for FreeBSD. Development > >> started as Google Summer of Code project in 2009. It has been in ports > >> since Sept 2011. I maintain the project. > >> > >> Conceptually PEFS is similar to nullfs adding encryption layer on top of > >> it. But it differs technically by not using vop_bypass. Another popular > >> stacked cryptographic file systems include eCryptfs (linux) and encfs > >> (fuse). There is also pam_pefs pam module to allow user authentication > >> with their PEFS-encrypted home directory password. > > > > 2 others are also already in FreeBSD src/ (not just ports) gbde & geli. > > geli and gbde are different concept, they provide encrypted block level devices. Yes, I allocate eg 2 Gig { via dd on a file on UFS or an MBR partition on a USB stick }, [then use mdconfig if a file on UFS] before I gbde, I've always thought I'd have to bite the ZFS bullet to escape fixed sizing, but PEFS offers variable sizing :-) > PEFS transparently encrypts data on existing file system. > > Here is what you can do with PEFS: > % mkdir ~/Private > % pefs mount ~/Private ~/Private > % pefs addkey ~/Private > % echo "Hello WORLD" > ~/Private/test > % ls -Al ~/Private > total 1 > -rw-r--r-- 1 gleb gleb 12 Oct 1 12:55 test > % cat ~/Private/test > Hello WORLD > % pefs unmount ~/Private > % ls -Al ~/Private > total 1 > -rw-r--r-- 1 gleb gleb 12 Oct 1 12:55 .DU6eudxZGtO8Ry_2Z3Sl+tq2hV3O75jq > % hd ~/Private/.DU6eudxZGtO8Ry_2Z3Sl+tq2hV3O75jq > 00000000 7f 1e 1b 05 fc 8a 5c 38 fc d8 2d 5f |......\8..-_| > 0000000c Nice. > Take a look a great article in the BSD Magazine or Downloaded (free) > http://glebkurtsou.blogspot.com/2009/10/encrypting-private-directory-with-pefs.html Will do. > > Whether moved from ports to src or not, either way, > > I sggest add to man section SEE ALSO gbde(8) & geli(8) > > Good point, thanks. > > > > Also, SEE ALSO of gbde & geli should probably ref ports/sysutils/pefs-kmod > > ft: Command not found. Sorry, line above my mouse seems to have caught my mistyped vi !}fmt from elsewhere. > > No pefs yet i SEE ALSO of > > http://www.freebsd.org/cgi/man.cgi?query=gbde&apropos=0&sektion=8&manpath=FreeBSD+9.2-RELEASE&arch=default&format=html > > http://www.freebsd.org/cgi/man.cgi?query=geli&apropos=0&sektion=8&manpath=FreeBSD+9.2-RELEASE&arch=default&format=html > > > > I suggest add an href inside: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html > > Even if just a 1 liner to start, to expand to a section later. > > (None there for 'pefs', I just searched) > > > > Personaly I've been using gbde based on top of a file inside a UFS > > for a long time, I can't remember why I chose gbde rather than geli, > > I guess because it was there first ? > > > > A dummy's guide short notes along the lines of "Which of these 3 should I use?" > > might also later be nice at the top of that web page :-) > > > > There is no answer for the question, each system does it's own thing > and does it differently: > * With PEFS backups are much easier: > - Use regular backup software for backing up encrypted data (lower > level file system), that would allow delta backup only. Sorry, I don't quite understand what's meant. ( I use rdist6 to backup individual changes in one tree to a tree on gbde on an mdconfig'd image on a ufs on a remote host or local USB stick, Easy after set up, all normal tools work, but yes, target size is fixed unlike PEFS. ) > - Create file system snapshots, e.g. zfs, then zfs send/receive, > regardless whether file system is encrypted or not. > * Setting up multiple encrypted file system is much easier -- no need > to preallocate storage and create file system. > * With PEFS it's possible to add key to encrypted home directory > during login (pam_pefs). > * PEFS let's you use multiple key in same file system. Useful, I hope it makes it to src/ I suggest contribute summary above to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html Thanks Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:00:07 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 10635534 for ; Mon, 7 Oct 2013 23:00:07 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C75032BF2 for ; Mon, 7 Oct 2013 23:00:06 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r97N03Gm025364 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 7 Oct 2013 16:00:05 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> Date: Mon, 7 Oct 2013 16:00:02 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> To: "freebsd-current@freebsd.org" X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 23:00:07 -0000 On 2013-10-07, at 3:45 PM, Lyndon Nerenberg wrote: > Having RCS in the base system is very useful. We use it to track = changes to bits of /etc on the machines where we don't do wholesale = customizations. (Those ones get git, but they also get an install of = /usr/ports with a fully populated /usr/ports/distfiles.) To clarify, the git-enabled machines are a small isolated subset of the = development machines. Then comes the test and q/a environment, where we = (by contract) roll nothing beyond the base OS and our application = software. There are other development shops dealing with the same restrictions. = Most of them have to stay quiet about these requirements on account of = the Homeland Security. They are all getting buggered over by the = fallacy that everyone has a gigabit ethernet connection permanently = wired into their ass ...= From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:17:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8EF9DB29; Mon, 7 Oct 2013 23:17:36 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6EE662CFD; Mon, 7 Oct 2013 23:17:36 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r97NHYc7090682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 16:17:34 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r97NHYF8090681; Mon, 7 Oct 2013 16:17:34 -0700 (PDT) (envelope-from jmg) Date: Mon, 7 Oct 2013 16:17:34 -0700 From: John-Mark Gurney To: Gleb Kurtsou Subject: Re: Committing PEFS to CURRENT Message-ID: <20131007231734.GY56872@funkthat.com> Mail-Followup-To: Gleb Kurtsou , freebsd-current@freebsd.org, delphij@freebsd.org, Kris Moore References: <20131007163111.GB1590@reks.swifttest.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131007163111.GB1590@reks.swifttest.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 07 Oct 2013 16:17:34 -0700 (PDT) Cc: freebsd-current@freebsd.org, delphij@freebsd.org, Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 23:17:36 -0000 Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 09:31 -0700: > Patch is available here: > https://github.com/glk/freebsd-head/commit/b4d2c4a5f42f88fdd07cb75feba3467e4d4c043c.patch Is there a reason you are writing your own AES-NI implementation instead of using the OpenCrypto framework? I updated the kernel's AES-NI implementation to have a very fast AES-XTS... Upon looking at your implementation, you have a very slow implementation as you do not pipeline AES-XTS at all... Please switch to using the opencrypto version.. You'll then be able to make use of any accelerators that other platforms may have... Are there plans to add authentication to this scheme? See that as a todo, but w/o authentication, you can't store anything reliably on it.. And w/ XTS, the attacker can take pot shots at your file in 16 byte chuncks... The only reason I'm running zfs on geli w/o authentication is that I'm using a 256bit checksum, so the chances of someone modifing two blocks to fool zfs into decrypting the correct new checksum value for their modified block is very small... In short, I'm trusting zfs to do the authentication for me... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:37:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EEA29FB6 for ; Mon, 7 Oct 2013 23:37:10 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 83CAD2DF4 for ; Mon, 7 Oct 2013 23:37:10 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id cb5so5705363wib.16 for ; Mon, 07 Oct 2013 16:37:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=u9g59Xz+X3MAgkRt9+JNWVOE7zq33aqJYpUs7yZ9AyM=; b=I68e7KzNhi/Gp1R/uSKkU8IeMtS49udT2rZh8ElwJaP5F3HkXLtLNGRGMofQI9aML6 gQQSqAQtitLjr6IXJZGxmbwSAIN1n7c+8PYuyatAcdWDUb86dcsiuAVZtrpEdwYSMy0l ZWTpeWVqrX8fELS16FW8v3ynLb7PLDr+v/aAoGVRTLFyFbQ0V/vvupPE8vGGL9/O1Ggz C0Fc6uCw+GJiySTOlU9PzyRTa4qtBMlFdkniQY7fMwkmi5KeVjPR4ntaClDDouOJn/6i sk/1BaFaO7kwfiUINWgV63Xaat95e8401ZdwlRvacfLId9F5049uKlI7i2RXeHbEKRjD qmHQ== MIME-Version: 1.0 X-Received: by 10.180.107.104 with SMTP id hb8mr21863940wib.0.1381189029009; Mon, 07 Oct 2013 16:37:09 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.73.133 with HTTP; Mon, 7 Oct 2013 16:37:08 -0700 (PDT) In-Reply-To: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> Date: Mon, 7 Oct 2013 16:37:08 -0700 X-Google-Sender-Auth: y5MYhj3bCR5jKT3QFfcIW9aKP3o Message-ID: Subject: Re: rcs is gone? From: Adrian Chadd To: Lyndon Nerenberg Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 23:37:11 -0000 Hi! Then you and others should stand up and provide feedback like this far, far earlier in the development process. If everyone who communicates says "x" and no-one says anything about the other letters "a"->"w", "y", "z", then we as developers don't really have a good cross-section of what people actually need. If you truely are doing things that require this level of service(s), then I encourage you to contact the FreeBSD Foundation and communicate exactly what your requirements are and why. They'll be able to steer things. Thanks! -adrian On 7 October 2013 16:00, Lyndon Nerenberg wrote: > > On 2013-10-07, at 3:45 PM, Lyndon Nerenberg wrote: > > > Having RCS in the base system is very useful. We use it to track > changes to bits of /etc on the machines where we don't do wholesale > customizations. (Those ones get git, but they also get an install of > /usr/ports with a fully populated /usr/ports/distfiles.) > > To clarify, the git-enabled machines are a small isolated subset of the > development machines. Then comes the test and q/a environment, where we > (by contract) roll nothing beyond the base OS and our application software. > > There are other development shops dealing with the same restrictions. > Most of them have to stay quiet about these requirements on account of the > Homeland Security. They are all getting buggered over by the fallacy that > everyone has a gigabit ethernet connection permanently wired into their ass > ... > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:40:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E7276270; Mon, 7 Oct 2013 23:40:33 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A78A72E42; Mon, 7 Oct 2013 23:40:33 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r97NeT1P025492 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 16:40:32 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: Date: Mon, 7 Oct 2013 16:40:28 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> To: Adrian Chadd X-Mailer: Apple Mail (2.1510) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 23:40:34 -0000 On 2013-10-07, at 4:37 PM, Adrian Chadd wrote: > Then you and others should stand up and provide feedback like this = far, far earlier in the development process. So when was this first discussed? I've been on -current for over a = decade. If I missed a prior discussion I truly apologize. --lyndon From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:46:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C9C8156E; Mon, 7 Oct 2013 23:46:49 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7F2512E7C; Mon, 7 Oct 2013 23:46:49 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r97NkiWG034351 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 16:46:46 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <525347DD.5090702@freebsd.org> Date: Tue, 08 Oct 2013 07:46:37 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: rcs is gone? References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 23:46:49 -0000 On 10/8/13 7:37 AM, Adrian Chadd wrote: > Hi! > > Then you and others should stand up and provide feedback like this far, far > earlier in the development process. Adiran this is the first I've heard of removing RCS. I would have screamed about it had I heard anything.. so now that I officially register my request for a backout can we have it back please? > > If everyone who communicates says "x" and no-one says anything about the > other letters "a"->"w", "y", "z", then we as developers don't really have a > good cross-section of what people actually need. > > If you truely are doing things that require this level of service(s), then > I encourage you to contact the FreeBSD Foundation and communicate exactly > what your requirements are and why. They'll be able to steer things. > > Thanks! > > > -adrian > > > > On 7 October 2013 16:00, Lyndon Nerenberg wrote: > >> On 2013-10-07, at 3:45 PM, Lyndon Nerenberg wrote: >> >>> Having RCS in the base system is very useful. We use it to track >> changes to bits of /etc on the machines where we don't do wholesale >> customizations. (Those ones get git, but they also get an install of >> /usr/ports with a fully populated /usr/ports/distfiles.) >> >> To clarify, the git-enabled machines are a small isolated subset of the >> development machines. Then comes the test and q/a environment, where we >> (by contract) roll nothing beyond the base OS and our application software. >> >> There are other development shops dealing with the same restrictions. >> Most of them have to stay quiet about these requirements on account of the >> Homeland Security. They are all getting buggered over by the fallacy that >> everyone has a gigabit ethernet connection permanently wired into their ass >> ... >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:47:05 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 339C567D; Mon, 7 Oct 2013 23:47:05 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-qe0-x22c.google.com (mail-qe0-x22c.google.com [IPv6:2607:f8b0:400d:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C9D3A2E88; Mon, 7 Oct 2013 23:47:04 +0000 (UTC) Received: by mail-qe0-f44.google.com with SMTP id 6so3182493qeb.3 for ; Mon, 07 Oct 2013 16:47:04 -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 :content-type; bh=OzZJcuN9nNcKm2izc1a8vcQpgKgBWtUfHpVY4nls1Iw=; b=fq5/mJrqQMitF44dvVQ13veVBG8ZlSSKiglMHB0BVqPHtxe7mxtqwwhmZcNKuSruXA /mWGHDaDuQAYfmktZwcGah1Pc97CgPLpI1zNUALFo9EFPUTen+/0rEb25z4UR/H4JGux MuELCBV/jS4vkA1dHVfZaRvsGxi4KF72zV2G/OVya6TpcOicUi2fZlPSYt1wBSnooZ4y 99iDggGlCXhyXm010R6Bwn2b+u9GJWMtA2OzFoAKgOPqRs7OE9k4wKA56veq7fyCsay2 4WzwbG+LA1el5oG8nQNw8B753+GtYgg6mIVFpeK4ftNnMBP0He3O6RhcvV4dbM1U9i+c 38iQ== MIME-Version: 1.0 X-Received: by 10.224.60.199 with SMTP id q7mr178408qah.80.1381189624051; Mon, 07 Oct 2013 16:47:04 -0700 (PDT) Received: by 10.229.114.5 with HTTP; Mon, 7 Oct 2013 16:47:03 -0700 (PDT) In-Reply-To: <20131007231734.GY56872@funkthat.com> References: <20131007163111.GB1590@reks.swifttest.com> <20131007231734.GY56872@funkthat.com> Date: Mon, 7 Oct 2013 16:47:03 -0700 Message-ID: Subject: Re: Committing PEFS to CURRENT From: Gleb Kurtsou To: Gleb Kurtsou , freebsd-current@freebsd.org, "delphij@freebsd.org" , Kris Moore Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 23:47:05 -0000 On Mon, Oct 7, 2013 at 4:17 PM, John-Mark Gurney wrote: > Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 09:31 -0700: >> Patch is available here: >> https://github.com/glk/freebsd-head/commit/b4d2c4a5f42f88fdd07cb75feba3467e4d4c043c.patch > > Is there a reason you are writing your own AES-NI implementation instead > of using the OpenCrypto framework? It reuses the same AES-NI implementation used by opencrypto, but code doesn't use opencrypto directly. Main limitation in opencrypto is that is incomplete implementation AES-XTS -- it doesn't implement ciphertext stealing. opencrypto contexts seemed to be too much overhead list time I looked at them especially in the case of multiple keys per file system in PEFS. AES-NI interface is not designed to be used outside of opencrypto thus some minor copy-past. > I updated the kernel's AES-NI implementation to have a very fast > AES-XTS... Upon looking at your implementation, you have a very > slow implementation as you do not pipeline AES-XTS at all... Please > switch to using the opencrypto version.. You'll then be able to make > use of any accelerators that other platforms may have... I was looking into incorporating AES_XTS pipeline changes in PEFS. I'd like to avoid switching to opencrypto at this point. But pipelining is doable without opencrypto and copying code around. > Are there plans to add authentication to this scheme? See that as a > todo, but w/o authentication, you can't store anything reliably on it.. > And w/ XTS, the attacker can take pot shots at your file in 16 byte > chuncks... I have data authentication prototype. It's too far from being complete, and I keep working on it as time permits. There are a few more ideas I'd like to work on while redesigning the file system. Patch also includes hmac and pkcs5v2 implementations which in fact were generic versions to go under sys/crypto until yesterday. Considering we are late in code freeze already I've merged them into PEFS not to touch geli code with the patch. > The only reason I'm running zfs on geli w/o authentication is that I'm > using a 256bit checksum, so the chances of someone modifing two blocks > to fool zfs into decrypting the correct new checksum value for their > modified block is very small... In short, I'm trusting zfs to do the > authentication for me... > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:49:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4CA707C1; Mon, 7 Oct 2013 23:49:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A68CC2EAD; Mon, 7 Oct 2013 23:49:05 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id w62so6100908wes.21 for ; Mon, 07 Oct 2013 16:49:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=1vMiUucIvuzE+FOZ+a0uYyjV1vml85rM7TBDlVlHjVA=; b=y8juO35/J9m7xsTi7G+0m+nghsSNHfa8POmwR+s2OiX+3ZXKHxioGILrgFgVn6wToq 797QbbAjlh/eM8BE1YiJGHTUzLd7FE6AeJMnUBkUOzeGm97mzxJmIMBz9lQkikZtUULQ 8xSCOOMvFwfVdAzwnHjHgoO9C1n5w9Ceqvkyvr5RVJQb86BsU4tp2TNcWODssV86Kxyt p1yDzCNVlFbLL8Qn0xFBMjxdkd6GUz7eMhTUpVdYBYgdsx9g/jw2wxaIkSx9Md7FKBIq jCTxiYH+bke3JaoPgSRs6IrRNudXnI6U80RbyZo5bXrXfwq2fL4wPFtGr9y2t+9gi+Ul 0XPA== MIME-Version: 1.0 X-Received: by 10.180.10.136 with SMTP id i8mr21598019wib.46.1381189744137; Mon, 07 Oct 2013 16:49:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.73.133 with HTTP; Mon, 7 Oct 2013 16:49:04 -0700 (PDT) In-Reply-To: <525347DD.5090702@freebsd.org> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> Date: Mon, 7 Oct 2013 16:49:04 -0700 X-Google-Sender-Auth: aH_TtVewlfdFMmc7b1FgjyzFNys Message-ID: Subject: Re: rcs is gone? From: Adrian Chadd To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" , Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 23:49:06 -0000 I've asked on IRC to figure out when this was first proposed. I'll see if it was announced anywhere or if Eitan snuck it in. -a On 7 October 2013 16:46, Julian Elischer wrote: > On 10/8/13 7:37 AM, Adrian Chadd wrote: > >> Hi! >> >> Then you and others should stand up and provide feedback like this far, >> far >> earlier in the development process. >> > > Adiran this is the first I've heard of removing RCS. > > I would have screamed about it had I heard anything.. > > so now that I officially register my request for a backout > can we have it back please? > > > > >> If everyone who communicates says "x" and no-one says anything about the >> other letters "a"->"w", "y", "z", then we as developers don't really have >> a >> good cross-section of what people actually need. >> >> If you truely are doing things that require this level of service(s), then >> I encourage you to contact the FreeBSD Foundation and communicate exactly >> what your requirements are and why. They'll be able to steer things. >> >> Thanks! >> >> >> -adrian >> >> >> >> On 7 October 2013 16:00, Lyndon Nerenberg wrote: >> >> On 2013-10-07, at 3:45 PM, Lyndon Nerenberg wrote: >>> >>> Having RCS in the base system is very useful. We use it to track >>>> >>> changes to bits of /etc on the machines where we don't do wholesale >>> customizations. (Those ones get git, but they also get an install of >>> /usr/ports with a fully populated /usr/ports/distfiles.) >>> >>> To clarify, the git-enabled machines are a small isolated subset of the >>> development machines. Then comes the test and q/a environment, where we >>> (by contract) roll nothing beyond the base OS and our application >>> software. >>> >>> There are other development shops dealing with the same restrictions. >>> Most of them have to stay quiet about these requirements on account of >>> the >>> Homeland Security. They are all getting buggered over by the fallacy >>> that >>> everyone has a gigabit ethernet connection permanently wired into their >>> ass >>> ... >>> ______________________________**_________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/**mailman/listinfo/freebsd-**current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@** >>> freebsd.org " >>> >>> ______________________________**_________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/**mailman/listinfo/freebsd-**current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@** >> freebsd.org " >> >> >> > From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:58:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7BF2DA2B; Mon, 7 Oct 2013 23:58:07 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3C2272F1E; Mon, 7 Oct 2013 23:58:07 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r97Nw3hc025594 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 16:58:05 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: Date: Mon, 7 Oct 2013 16:58:02 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <1E4D92A9-EB10-4469-AA1F-E70D71405732@orthanc.ca> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> To: Adrian Chadd X-Mailer: Apple Mail (2.1510) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 23:58:07 -0000 On 2013-10-07, at 4:49 PM, Adrian Chadd wrote: > I've asked on IRC to figure out when this was first proposed. Adrian, something to keep in mind is that the majority of your code's = users will never use your preferred communication media. So when you = propose to remove a feature, absence of push-back means nothing, other = than the lack of a communications channel with your 'customers'. We get this a lot with feature manipulation in nmh, and have learned to = tread carefully as a result. This is also why the IETF defines work as being that which takes place = on the mailing lists. Slow and dumb (in the media-rich sense), but = everyone knows what's going on. In that light, if there is a rational argument for pulling RCS out of = the base, propose it here on the -current list and let's all discuss it. --lyndon From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:00:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 84099B57 for ; Tue, 8 Oct 2013 00:00:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1C9102F62 for ; Tue, 8 Oct 2013 00:00:45 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id l18so8172217wgh.16 for ; Mon, 07 Oct 2013 17:00:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5tDI30Q0m+PY52JlnweJXLkfxNmhIoWVyDa+b+SJsrY=; b=U/dI+O86EYNRNXwPHKtcnptGcRUCJQFHKCAkxH86cEUZutjLghzL901Wxc+/jrleJv EvJdhwROWuyFTr3+L1RvFdrZEfBlazDNKzzAJzCGg3C5UXePFWYKmhRvwZMC51viKEbO c3k2ylCDwEIou9pqjudVd4SfYMznuNLmhF+z6PG2wiW0z1iSpk2MvB24tKFoYk9yNFT6 RbEiq86bnFE5iyxDYbMVEhy+ZrKu7/GNoyL10jlkvGwKRRhlZrR2jlXyG1gc0FeOPGr4 7aO+GXAR5/bULXdtbKCvFhsXOG+7xFL9EBQ5lA8cu2gs8AUmiROXFroUohVliE/UJBse LF6Q== MIME-Version: 1.0 X-Received: by 10.180.109.132 with SMTP id hs4mr21111302wib.46.1381190444572; Mon, 07 Oct 2013 17:00:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.73.133 with HTTP; Mon, 7 Oct 2013 17:00:44 -0700 (PDT) In-Reply-To: <1E4D92A9-EB10-4469-AA1F-E70D71405732@orthanc.ca> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1E4D92A9-EB10-4469-AA1F-E70D71405732@orthanc.ca> Date: Mon, 7 Oct 2013 17:00:44 -0700 X-Google-Sender-Auth: fcUCe0jR_0m9dm9DOwYkMYWTFN4 Message-ID: Subject: Re: rcs is gone? From: Adrian Chadd To: Lyndon Nerenberg Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:00:46 -0000 On 7 October 2013 16:58, Lyndon Nerenberg wrote: > > On 2013-10-07, at 4:49 PM, Adrian Chadd wrote: > > > I've asked on IRC to figure out when this was first proposed. > > Adrian, something to keep in mind is that the majority of your code's > users will never use your preferred communication media. So when you > propose to remove a feature, absence of push-back means nothing, other than > the lack of a communications channel with your 'customers'. > > Oh, I know it's an up-hill battle. But I honestly thought that this had been communicated on a list somewhere. It seems.. not. I don't know why. Gah. > We get this a lot with feature manipulation in nmh, and have learned to > tread carefully as a result. > > This is also why the IETF defines work as being that which takes place on > the mailing lists. Slow and dumb (in the media-rich sense), but everyone > knows what's going on. > > In that light, if there is a rational argument for pulling RCS out of the > base, propose it here on the -current list and let's all discuss it. > I still do suggest also getting a relationship with the FreeBSD foundation and airing grievances with them. They're interested in opening up new communication lines with companies who can provide this kind of feedback but don't necessarily want to be public about it. Thanks, -a From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:01:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5D1C6C77; Tue, 8 Oct 2013 00:01:44 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2FC552F77; Tue, 8 Oct 2013 00:01:43 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r9801dUP034420 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 17:01:42 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52534B5E.7010401@freebsd.org> Date: Tue, 08 Oct 2013 08:01:34 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org, core@freebsd.org Subject: Re: [Heads Up] RCS removed from base References: <20131007150658.GA79233@troutmask.apl.washington.edu> In-Reply-To: <20131007150658.GA79233@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:01:44 -0000 On 10/7/13 11:06 PM, Steve Kargl wrote: > On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: >> Hey all, >> >> RCS was removed from the base system in r256095. If you still want to >> use RCS please install either devel/rcs or devel/rcs57. If not, be >> sure to check out the alternatives (pun stolen and intended). >> > Perhaps, a note in src/UPDATING is appropriate? > ok so what is this, the secret cabal to make FreeBSD useless? I'm ccing core as I believe this was not discussed enough in public (in fact not discussed AT ALL in any forum I am watching) and I officially request a backout of the removal of what I consider to be core functionality. My usual way of doing things is on install to ci EVERYTHING in /etc to get a snapsot right the way back to install. now I have to change things in /etc (and other places) BEFORE I can check them in. (i.e. get networking up and ports installed) not a big thing but I believe that a lot of poeple use ci/co on /etc becasue it is "just there" From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:04:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9EE14EA2 for ; Tue, 8 Oct 2013 00:04:31 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0A3482FA6 for ; Tue, 8 Oct 2013 00:04:30 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r9804QPN034434 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 7 Oct 2013 17:04:29 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52534C04.60909@freebsd.org> Date: Tue, 08 Oct 2013 08:04:20 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: rcs is gone? References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> In-Reply-To: <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:04:31 -0000 On 10/8/13 6:45 AM, Lyndon Nerenberg wrote: > On 2013-10-07, at 2:53 PM, David Chisnall wrote: > >> Or do you really only run the base OS and no other software on your systems, without any of your own code or any customisation? > We install from the base release ISO images burned on DVDs. > > We are physically air-gapped from the internet, none of the "end users" of the system have access to USB ports, and there are no electronic devices allowed into the development shop. > > We have a scheme for bringing in software from /usr/ports, but it is painful. And those ports can't necessarily walk on to all the systems in the shop. (I don't make the rules. Suffice to say the company is very paranoid about their code getting out into the wild.) > > Having RCS in the base system is very useful. We use it to track changes to bits of /etc on the machines where we don't do wholesale customizations. (Those ones get git, but they also get an install of /usr/ports with a fully populated /usr/ports/distfiles.) > > So if nuking RCS is a case of "I don't use it," ... we do. +1 > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:06:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BA1C1FC5; Tue, 8 Oct 2013 00:06:15 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qe0-x231.google.com (mail-qe0-x231.google.com [IPv6:2607:f8b0:400d:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 65AB12FBF; Tue, 8 Oct 2013 00:06:15 +0000 (UTC) Received: by mail-qe0-f49.google.com with SMTP id s14so5989741qeb.8 for ; Mon, 07 Oct 2013 17:06:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=0devHjt61U6FLkvdS7xz01F5sPCGFsmTxMAHGLOaE3o=; b=XjVXOQQ3Xeb8NhPTH5qDzTWgpUze84wk6Le1ENeU/IcI3HW4587W4flXKo0P9tqKAs VqPxSOKcp4rWKbFHesg3G0cvCjOPVub+SgtCf3mN2irqtRp1tGD/BOTJTlqiJ3u8LjEy vxOK3yo83vxmRyKGLxbhGlr0Y4nQxdzMse0OE6TIfeIUVSOr/6WjPH+BLimz/XsFT+Um kcYNKulpNM4fO8bXlxj/IFdx9cTQNqJpdXsiV0GK0S2cjUVoGHfOyEquXM+yEz5Mzhlo grwG8wD8nIr+EYhw9ZALYTEXoT6JUMq6G7d/mXKYH4wCnAzSuDxxpsLco0HujGP7Vf8l sF0Q== X-Received: by 10.49.50.232 with SMTP id f8mr39891243qeo.63.1381190774507; Mon, 07 Oct 2013 17:06:14 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Mon, 7 Oct 2013 17:05:34 -0700 (PDT) In-Reply-To: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1E4D92A9-EB10-4469-AA1F-E70D71405732@orthanc.ca> From: Igor Mozolevsky Date: Tue, 8 Oct 2013 01:05:34 +0100 X-Google-Sender-Auth: QQCFxaBBrk_51Kab5sNgOEjA60E Message-ID: Subject: Re: rcs is gone? To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current , Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:06:15 -0000 On 8 October 2013 01:00, Adrian Chadd wrote: [snip] Oh, I know it's an up-hill battle. But I honestly thought that this had > been communicated on a list somewhere. It seems.. not. I don't know why. > Gah. It's been communicated at Sun, 6 Oct 2013 22:43:21 -0400, but that doesn't meed there's been any discussion, let alone any consensus reached- it was communicated as an already made decision... -- Igor M. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:18:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2F9E03D0 for ; Tue, 8 Oct 2013 00:18:21 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D76292076 for ; Tue, 8 Oct 2013 00:18:20 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r980IHtF094713; Mon, 7 Oct 2013 18:18:17 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r980IHDm094710; Mon, 7 Oct 2013 18:18:17 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 7 Oct 2013 18:18:17 -0600 (MDT) From: Warren Block To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI In-Reply-To: <52531F95.6050002@allanjude.com> Message-ID: References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) 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]); Mon, 07 Oct 2013 18:18:17 -0600 (MDT) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:18:21 -0000 On Mon, 7 Oct 2013, Allan Jude wrote: > On 2013-10-07 16:43, Warren Block wrote: >> On Mon, 7 Oct 2013, Allan Jude wrote: >> >>> Additional, it includes some other changes to bsdinstall: >>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>> to no >> >> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 . > That is a good idea, I'll add that > > I've also hit this: > http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html > and plan to throw in a fix for that. > Which makes more sense, blindly 'killall dhclient' before we try to > acquire a new lease, or detect that dhclient is running and try to use > the IP that has already been assigned? killall seems all right. In fact, internally, it's going to do that check. If nothing named dhclient is running, it will return immediately. Although on 10.0, dhclient does not want to die sometimes. Here's another PR for usability: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/161547 From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:21:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3D05654D for ; Tue, 8 Oct 2013 00:21:58 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 06F3420C8 for ; Tue, 8 Oct 2013 00:21:57 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r980LtdH008228 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 7 Oct 2013 19:21:55 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Mon, 7 Oct 2013 19:21:54 -0500 From: "Teske, Devin" To: Warren Block Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOw7xkPJPIP8ZCyUiSsjBzr2++AA== Date: Tue, 8 Oct 2013 00:21:54 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC40159@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <5AD44DC2CEE3EC41B0DC043D3B9D038E@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-07_05:2013-10-08,2013-10-07,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:21:58 -0000 On Oct 7, 2013, at 5:18 PM, Warren Block wrote: > On Mon, 7 Oct 2013, Allan Jude wrote: >=20 >> On 2013-10-07 16:43, Warren Block wrote: >>> On Mon, 7 Oct 2013, Allan Jude wrote: >>>=20 >>>> Additional, it includes some other changes to bsdinstall: >>>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>>> to no >>>=20 >>> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/162175 . >=20 >> That is a good idea, I'll add that >>=20 >> I've also hit this: >> http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000= 949.html >> and plan to throw in a fix for that. >> Which makes more sense, blindly 'killall dhclient' before we try to >> acquire a new lease, or detect that dhclient is running and try to use >> the IP that has already been assigned? >=20 > killall seems all right. In fact, internally, it's going to do that chec= k. If nothing named dhclient is running, it will return immediately. >=20 > Although on 10.0, dhclient does not want to die sometimes. >=20 > Here's another PR for usability: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/161547 Hope you guys aren't rewriting bsdconfig's network.subr --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:23:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2173366E; Tue, 8 Oct 2013 00:23:16 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E943D20E2; Tue, 8 Oct 2013 00:23:15 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r980NEUu091684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 17:23:15 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r980NExM091683; Mon, 7 Oct 2013 17:23:14 -0700 (PDT) (envelope-from jmg) Date: Mon, 7 Oct 2013 17:23:14 -0700 From: John-Mark Gurney To: Gleb Kurtsou Subject: Re: Committing PEFS to CURRENT Message-ID: <20131008002314.GA56872@funkthat.com> Mail-Followup-To: Gleb Kurtsou , Gleb Kurtsou , freebsd-current@freebsd.org, "delphij@freebsd.org" , Kris Moore References: <20131007163111.GB1590@reks.swifttest.com> <20131007231734.GY56872@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 07 Oct 2013 17:23:15 -0700 (PDT) Cc: Gleb Kurtsou , freebsd-current@freebsd.org, "delphij@freebsd.org" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:23:16 -0000 Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 16:47 -0700: > On Mon, Oct 7, 2013 at 4:17 PM, John-Mark Gurney wrote: > > Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 09:31 -0700: > >> Patch is available here: > >> https://github.com/glk/freebsd-head/commit/b4d2c4a5f42f88fdd07cb75feba3467e4d4c043c.patch > > > > Is there a reason you are writing your own AES-NI implementation instead > > of using the OpenCrypto framework? > > It reuses the same AES-NI implementation used by opencrypto, > but code doesn't use opencrypto directly. Main limitation in opencrypto is > that is incomplete implementation AES-XTS -- it doesn't implement ciphertext > stealing. opencrypto contexts seemed to be too much overhead list time I I remember noticing that when I was working on it.. but as there are different modes of packing/padding, I decided not to do anything with that... I also don't like your lack of comments arround xts_lastblock and about why it is accessing dst - 1... To me, you should pass in the previous block as an arg to xts_lastblock instead of doing dst[-1]... You did comment what you're doing (m - 1), but not why it is safe to do that... There is no comment that you're implementing ciphertext stealing w/ the function which makes it even harder to understand that you'd going it properly... It wouldn't be hard to add ciphertext stealing to the opencrypto implementation if that is really all that is missing... but.. > looked at them especially in the case of multiple keys per file system in PEFS. > AES-NI interface is not designed to be used outside of opencrypto thus > some minor copy-past. We have discovered that by the "minor" copy/paste we now have an inferior implementation of AES-XTS... If it performed similar to the one before it, it is over 10x slower than the one that I committed.. > > I updated the kernel's AES-NI implementation to have a very fast > > AES-XTS... Upon looking at your implementation, you have a very > > slow implementation as you do not pipeline AES-XTS at all... Please > > switch to using the opencrypto version.. You'll then be able to make > > use of any accelerators that other platforms may have... > > I was looking into incorporating AES_XTS pipeline changes in PEFS. > I'd like to avoid switching to opencrypto at this point. But pipelining is > doable without opencrypto and copying code around. I really don't like the idea of adding yet anothe AES-XTS implementation to our tree (especially considering how bad both the previous one and this one is)... Even if you do bring over the pipeline changes... It'll be yet another copy of code to maintain and port performance improvements too... We could always refactor the AES-NI code to make it more usable outside the opencrypto framework as a stepping stone to possibly using pjd's improved opencrypto framework... But copy/pasting just because we don't want to do a bit more work isn't good justification... > > Are there plans to add authentication to this scheme? See that as a > > todo, but w/o authentication, you can't store anything reliably on it.. > > And w/ XTS, the attacker can take pot shots at your file in 16 byte > > chuncks... > > I have data authentication prototype. It's too far from being complete, > and I keep working on it as time permits. There are a few more ideas > I'd like to work on while redesigning the file system. > > Patch also includes hmac and pkcs5v2 implementations which in fact > were generic versions to go under sys/crypto until yesterday. > Considering we are late in code freeze already I've merged them > into PEFS not to touch geli code with the patch. Can't you keep them named the same under sys/crypto and just link w/ them as necessary to prevent repo churn when you finally integrate them into sys/crypto? That seems better than moving them arround, though I guess w/ svn, it isn't as big of a deal... Someone w/ a repo hat on should chime in here... > > The only reason I'm running zfs on geli w/o authentication is that I'm > > using a 256bit checksum, so the chances of someone modifing two blocks > > to fool zfs into decrypting the correct new checksum value for their > > modified block is very small... In short, I'm trusting zfs to do the > > authentication for me... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:28:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7A7EB82A; Tue, 8 Oct 2013 00:28:55 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 55C4E210B; Tue, 8 Oct 2013 00:28:55 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r980SsIJ091767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 17:28:54 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r980Ss7n091766; Mon, 7 Oct 2013 17:28:54 -0700 (PDT) (envelope-from jmg) Date: Mon, 7 Oct 2013 17:28:54 -0700 From: John-Mark Gurney To: Julian Elischer Subject: Re: [Heads Up] RCS removed from base Message-ID: <20131008002854.GB56872@funkthat.com> Mail-Followup-To: Julian Elischer , freebsd-current@freebsd.org References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52534B5E.7010401@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 07 Oct 2013 17:28:54 -0700 (PDT) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:28:55 -0000 Julian Elischer wrote this message on Tue, Oct 08, 2013 at 08:01 +0800: > not a big thing but I believe that a lot of poeple use ci/co on /etc > becasue it is "just there" +1 -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:31:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4935965 for ; Tue, 8 Oct 2013 00:31:02 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id AEC27214E for ; Tue, 8 Oct 2013 00:31:02 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id D8B691D816 for ; Tue, 8 Oct 2013 00:31:00 +0000 (UTC) Message-ID: <5253525C.2000701@allanjude.com> Date: Mon, 07 Oct 2013 20:31:24 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC40159@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC40159@LTCFISWMSGMB21.FNFIS.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:31:02 -0000 On 2013-10-07 20:21, Teske, Devin wrote: > On Oct 7, 2013, at 5:18 PM, Warren Block wrote: > >> On Mon, 7 Oct 2013, Allan Jude wrote: >> >>> On 2013-10-07 16:43, Warren Block wrote: >>>> On Mon, 7 Oct 2013, Allan Jude wrote: >>>> >>>>> Additional, it includes some other changes to bsdinstall: >>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>>>> to no >>>> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 . >>> That is a good idea, I'll add that >>> >>> I've also hit this: >>> http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html >>> and plan to throw in a fix for that. >>> Which makes more sense, blindly 'killall dhclient' before we try to >>> acquire a new lease, or detect that dhclient is running and try to use >>> the IP that has already been assigned? >> killall seems all right. In fact, internally, it's going to do that check. If nothing named dhclient is running, it will return immediately. >> >> Although on 10.0, dhclient does not want to die sometimes. >> >> Here's another PR for usability: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/161547 > Hope you guys aren't rewriting bsdconfig's network.subr These changes are in usr.sbin/bsdinstall/scripts/network and usr.sbin/bsdinstall/scripts/network_ipv4 I've not touched bsdconfig's network stuff -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:36:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D2E30BE9; Tue, 8 Oct 2013 00:36:43 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 933F1219A; Tue, 8 Oct 2013 00:36:43 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r980ag0c091960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 17:36:43 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r980agfO091959; Mon, 7 Oct 2013 17:36:42 -0700 (PDT) (envelope-from jmg) Date: Mon, 7 Oct 2013 17:36:42 -0700 From: John-Mark Gurney To: Glen Barber Subject: Re: rcs is gone? Message-ID: <20131008003642.GC56872@funkthat.com> Mail-Followup-To: Glen Barber , Igor Mozolevsky , "freebsd-current@freebsd.org" , Andreas Nilsson References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131007212925.GC2133@glenbarber.us> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 07 Oct 2013 17:36:43 -0700 (PDT) Cc: "freebsd-current@freebsd.org" , Andreas Nilsson , Igor Mozolevsky X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:36:43 -0000 Glen Barber wrote this message on Mon, Oct 07, 2013 at 17:29 -0400: > On Mon, Oct 07, 2013 at 10:26:07PM +0100, Igor Mozolevsky wrote: > > On 7 October 2013 22:15, Andreas Nilsson wrote: > > > > > > > Well, it has been announced, and is available as a port. > > > > > > > So there's no version control in the base at all now?.. When did FreeBSD > > decide to move away from distributing a usable OS? Why not just distribute > > a kernel and a few bits that are barely sufficient for the initial set up, > > and then make users fetch everything from ports? > > > > svnlite? cd /etc svnliteadmin create svn svnlite co file:///etc/svn . svnlite add rc.conf svnlite commit rc.conf instead of: cd /etc ci rc.conf really? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:40:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 53A29D77; Tue, 8 Oct 2013 00:40:17 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 245BA21C7; Tue, 8 Oct 2013 00:40:16 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r980e7D5034565 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 17:40:14 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52535461.3010803@freebsd.org> Date: Tue, 08 Oct 2013 08:40:01 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Glen Barber Subject: Re: rcs is gone? References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> In-Reply-To: <20131007212925.GC2133@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , Andreas Nilsson , Igor Mozolevsky X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:40:17 -0000 On 10/8/13 5:29 AM, Glen Barber wrote: > On Mon, Oct 07, 2013 at 10:26:07PM +0100, Igor Mozolevsky wrote: >> On 7 October 2013 22:15, Andreas Nilsson wrote: >> >> >>> Well, it has been announced, and is available as a port. >>> >> So there's no version control in the base at all now?.. When did FreeBSD >> decide to move away from distributing a usable OS? Why not just distribute >> a kernel and a few bits that are barely sufficient for the initial set up, >> and then make users fetch everything from ports? >> > svnlite? > > Glen > fail From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:41:11 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 81FB3EA1; Tue, 8 Oct 2013 00:41:11 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-qe0-x236.google.com (mail-qe0-x236.google.com [IPv6:2607:f8b0:400d:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 20BD22206; Tue, 8 Oct 2013 00:41:11 +0000 (UTC) Received: by mail-qe0-f54.google.com with SMTP id 1so2131226qec.13 for ; Mon, 07 Oct 2013 17:41:10 -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 :content-type; bh=AJZaK4BmnMe5pnhs8ZgOf2rN3B3FwI+wCftWq0X4Db4=; b=CbxXuh22cmhz9+0aZukPbIERmoy3CQDaB9PO8+ot/gRly4e1N1YeYDwXN9dSg30Ke+ IO4I3rPkP9QBUGVZ7CCdH8tBYNyw0jkjK/a0Zl0wSlcfEpWQR3y/XGrnENrDLOJHhqSM g+sbwvloa2spGfuHYB0v0UTCywf0nsG+KDIJNl6qJsq/fdbH0BoIePAw25zijWnSYMsd xiB7CF7ZTHCKbPapvarozn51or3MRFoHp7SpWnJBJVn4E7pYpv+mYDQdxwEGOf5y9rzb uFomNmdXgV0hRsSK5jGYxccGFUPci5BhOimr6Bo0iGUrT1p0KjhPTEkBKVCLTYJwGAIl s67Q== MIME-Version: 1.0 X-Received: by 10.224.98.200 with SMTP id r8mr435024qan.26.1381192870147; Mon, 07 Oct 2013 17:41:10 -0700 (PDT) Received: by 10.229.114.5 with HTTP; Mon, 7 Oct 2013 17:41:10 -0700 (PDT) In-Reply-To: <20131008002314.GA56872@funkthat.com> References: <20131007163111.GB1590@reks.swifttest.com> <20131007231734.GY56872@funkthat.com> <20131008002314.GA56872@funkthat.com> Date: Mon, 7 Oct 2013 17:41:10 -0700 Message-ID: Subject: Re: Committing PEFS to CURRENT From: Gleb Kurtsou To: Gleb Kurtsou , Gleb Kurtsou , "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:41:11 -0000 On Mon, Oct 7, 2013 at 5:23 PM, John-Mark Gurney wrote: > Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 16:47 -0700: >> On Mon, Oct 7, 2013 at 4:17 PM, John-Mark Gurney wrote: >> > Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 09:31 -0700: >> >> Patch is available here: >> >> https://github.com/glk/freebsd-head/commit/b4d2c4a5f42f88fdd07cb75feba3467e4d4c043c.patch >> > >> > Is there a reason you are writing your own AES-NI implementation instead >> > of using the OpenCrypto framework? >> >> It reuses the same AES-NI implementation used by opencrypto, >> but code doesn't use opencrypto directly. Main limitation in opencrypto is >> that is incomplete implementation AES-XTS -- it doesn't implement ciphertext >> stealing. opencrypto contexts seemed to be too much overhead list time I > > I remember noticing that when I was working on it.. but as there are > different modes of packing/padding, I decided not to do anything with > that... > > I also don't like your lack of comments arround xts_lastblock and about > why it is accessing dst - 1... To me, you should pass in the previous > block as an arg to xts_lastblock instead of doing dst[-1]... You did > comment what you're doing (m - 1), but not why it is safe to do that... > There is no comment that you're implementing ciphertext stealing w/ the > function which makes it even harder to understand that you'd going it > properly... The code comes from University of Tsukuba. The function is internal to the module and is safe to use that way if you look at pefs_xts_block_encrypt and pefs_xts_block_decrypt. > It wouldn't be hard to add ciphertext stealing to the opencrypto > implementation if that is really all that is missing... but.. > >> looked at them especially in the case of multiple keys per file system in PEFS. >> AES-NI interface is not designed to be used outside of opencrypto thus >> some minor copy-past. > > We have discovered that by the "minor" copy/paste we now have an > inferior implementation of AES-XTS... If it performed similar to the > one before it, it is over 10x slower than the one that I committed.. > >> > I updated the kernel's AES-NI implementation to have a very fast >> > AES-XTS... Upon looking at your implementation, you have a very >> > slow implementation as you do not pipeline AES-XTS at all... Please >> > switch to using the opencrypto version.. You'll then be able to make >> > use of any accelerators that other platforms may have... >> >> I was looking into incorporating AES_XTS pipeline changes in PEFS. >> I'd like to avoid switching to opencrypto at this point. But pipelining is >> doable without opencrypto and copying code around. > > I really don't like the idea of adding yet anothe AES-XTS implementation > to our tree (especially considering how bad both the previous one and > this one is)... Even if you do bring over the pipeline changes... > It'll be yet another copy of code to maintain and port performance > improvements too... > > We could always refactor the AES-NI code to make it more usable outside > the opencrypto framework as a stepping stone to possibly using pjd's > improved opencrypto framework... Refactoring AES-NI would be ideal, it would also be great to extract AES-XTS implementation and make it usable outside of opencrypto adding ciphertext stealing. > But copy/pasting just because we don't want to do a bit more work isn't > good justification... It's not that I "don't want to do a bit more work" I never said that, it's rather about avoiding changes after KBI freeze. >> > Are there plans to add authentication to this scheme? See that as a >> > todo, but w/o authentication, you can't store anything reliably on it.. >> > And w/ XTS, the attacker can take pot shots at your file in 16 byte >> > chuncks... >> >> I have data authentication prototype. It's too far from being complete, >> and I keep working on it as time permits. There are a few more ideas >> I'd like to work on while redesigning the file system. >> >> Patch also includes hmac and pkcs5v2 implementations which in fact >> were generic versions to go under sys/crypto until yesterday. >> Considering we are late in code freeze already I've merged them >> into PEFS not to touch geli code with the patch. > > Can't you keep them named the same under sys/crypto and just link w/ them > as necessary to prevent repo churn when you finally integrate them into > sys/crypto? That seems better than moving them arround, though I guess > w/ svn, it isn't as big of a deal... Someone w/ a repo hat on should > chime in here... It won't be possible at least because of pkcs5v2_genkey() (name collision) being defined internally in geli and pkcs5v2 using hmac from geli. Moving them to sys/crypto in 11-CURRENT is a minor issue IMHO. I was pushing those changes to HEAD years ago, but they got stuck somewhere in review process. >> > The only reason I'm running zfs on geli w/o authentication is that I'm >> > using a 256bit checksum, so the chances of someone modifing two blocks >> > to fool zfs into decrypting the correct new checksum value for their >> > modified block is very small... In short, I'm trusting zfs to do the >> > authentication for me... > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:41:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8A83AFB7 for ; Tue, 8 Oct 2013 00:41:45 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 41DB92216 for ; Tue, 8 Oct 2013 00:41:45 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r980fc4v062406 for ; Mon, 7 Oct 2013 20:41:43 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <525354C2.8070807@m5p.com> Date: Mon, 07 Oct 2013 20:41:38 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [Heads Up] RCS removed from base References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008002854.GB56872@funkthat.com> In-Reply-To: <20131008002854.GB56872@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Mon, 07 Oct 2013 20:41:43 -0400 (EDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:41:45 -0000 On 10/07/13 20:28, John-Mark Gurney wrote: > Julian Elischer wrote this message on Tue, Oct 08, 2013 at 08:01 +0800: >> not a big thing but I believe that a lot of poeple use ci/co on /etc >> becasue it is "just there" > > +1 > Folks, this is just plain a major violation of the Principle of Least Amazement. RCS is ideal for keeping track of my configuration files in /etc. What do we gain by removing it? Roughly 640 kilobytes of executable code and 60 kilobytes of compressed man pages. Had the community that hangs our on this mailing list heard about this when it could still have been described as a proposal, as opposed to a fait accompli, I would have described it as the epitome of a Half Baked Idea. -- George From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:42:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4654A15D; Tue, 8 Oct 2013 00:42:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 196852225; Tue, 8 Oct 2013 00:42:58 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 185AE8A94; Tue, 8 Oct 2013 00:42:55 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 185AE8A94 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 7 Oct 2013 20:42:53 -0400 From: Glen Barber To: Igor Mozolevsky , "freebsd-current@freebsd.org" , Andreas Nilsson Subject: Re: rcs is gone? Message-ID: <20131008004253.GG2133@glenbarber.us> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> <20131008003642.GC56872@funkthat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WkfBGePaEyrk4zXB" Content-Disposition: inline In-Reply-To: <20131008003642.GC56872@funkthat.com> X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:42:58 -0000 --WkfBGePaEyrk4zXB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 07, 2013 at 05:36:42PM -0700, John-Mark Gurney wrote: > > > So there's no version control in the base at all now?.. When did Free= BSD > > > decide to move away from distributing a usable OS? Why not just distr= ibute > > > a kernel and a few bits that are barely sufficient for the initial se= t up, > > > and then make users fetch everything from ports? > > >=20 > >=20 > > svnlite? >=20 > cd /etc > svnliteadmin create svn > svnlite co file:///etc/svn . > svnlite add rc.conf > svnlite commit rc.conf >=20 > instead of: > cd /etc > ci rc.conf >=20 > really? >=20 No, not really. # mkdir local # svnadmin create ./local # svn import /etc file:///$PWD/local Glen --WkfBGePaEyrk4zXB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSU1UNAAoJELls3eqvi17QQr4QAIb8ht+pKFomMex8LjKgvuTQ AnmHuOjXluVt06w1nkTyN8Wl6/rY+D31xRLe3ZnhFDHmg8LHR30KEzbe23NA1bzw GdiM/iy0AzuJJWi3FZssBVVpYttlH116PMajwFwYkdo+2yWfpiS3uxtEZOehfiQb 79ZsjJ6gC6q+2V0ZqcsDBgEKsYwBraeSFtUkGuFC0mQdsxpDUk2VuW851GD/FFzq w7TKE5U7NCU9XILtuZs5MJAXpsG8/0z4lbirEZ9JcRR8q8Uq3GmsuO83PT0SwtMB wDKmNenAiv5sZZwP8QpdtTtHKo2dyWbM7h/D0I8LzepaCIkJbmM0tvXAMAfqnZm+ CCkK3wG3kZjHqFr9de9gFhjyT5i9nuXU+6wKIj4MTHNFP2WYevbUKLx9jRDNmNqf m16ETJC+FYWwduDuRCtVvfYvRKeAUqwcwrbL3UMJvG5v4B6mT2CR7f0qxKI76Ho3 T8kRnNqBabonHif+onav50IoNMT3rHol1gkA/mFytHcxON7rgbdfVLcmV9MkcfVf 6N6qMo5JG/JMry4jL2sQl5UIWuWp9MT1RGueSAK2gUIq6Gw2pRaooJq7eGL7A5OO /hdUjdIVgct7SxnKAwTFe5t6qW1pL0zlJd9/b3IOalycSkRJ0dfkZsl8LlbEECsQ Fs7OkZU/rOUFlmMrlbD1 =zZoG -----END PGP SIGNATURE----- --WkfBGePaEyrk4zXB-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:48:20 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C7C7E33A for ; Tue, 8 Oct 2013 00:48:20 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 895CB225B for ; Tue, 8 Oct 2013 00:48:20 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r980mGRN025805 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 7 Oct 2013 17:48:19 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: <52535461.3010803@freebsd.org> Date: Mon, 7 Oct 2013 17:48:16 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> <52535461.3010803@freebsd.org> To: "freebsd-current@freebsd.org" X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:48:20 -0000 On 2013-10-07, at 5:40 PM, Julian Elischer wrote: >> svnlite? >>=20 > fail I won't go that far, immediately. But I need a tool that lets me migrate the history of my RCS files to = the new regime. And the new tools(s) *must* be part of the base system. (Migration = tools included.) And the new scheme should provide something as simple as 'ci -l foo'. = I'm not convinced svn does that. --lyndon From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:49:20 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 37FE04E2; Tue, 8 Oct 2013 00:49:20 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id 0D1E7227B; Tue, 8 Oct 2013 00:49:19 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 693C62F87E; Mon, 7 Oct 2013 20:42:16 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h77SXn4RYLXK; Mon, 7 Oct 2013 20:42:16 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <525354E6.7040506@egr.msu.edu> Date: Mon, 07 Oct 2013 20:42:14 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: Buying recommendation for silent router/fileserver References: <20121011145453.GU69724@acme.spoerlein.net> <20121011160521.GB40357@in-addr.com> <5076F955.8070207@egr.msu.edu> <507833E1.4070505@egr.msu.edu> In-Reply-To: <507833E1.4070505@egr.msu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:49:20 -0000 Finally got around to it, kern/182818. Thanks for the encouragement. On 10/12/12 11:14, Adam McDougall wrote: > I did not, but I put it on my list to try to accomplish. > > On 10/11/12 13:41, Adrian Chadd wrote: >> Did you ever file a PR for the slow SATA behaviour? >> >> >> >> Adrian >> >> >> On 11 October 2012 09:52, Adam McDougall wrote: >>> >>> Be wary of the Soekris net6501, I bought three of the 1.6Ghz net6501-70 >>> model which has an Atom E-680 cpu (E series) and it compiles more >>> than twice >>> as slow as a 1.6Ghz Atom N270 in an older netbook. Someone else >>> running >>> Linux reported similar CPU slowness. As far as practical network >>> throughput, I could only get 100Mbit/sec with a simple HTTP download >>> of a >>> file full of zeros, and OpenVPN could only push about 25Mbit/sec. As a >>> practical example of the CPU slowness, it takes about 1.5 minutes to >>> compile >>> pkg on the N270 netbook and 5 minutes on the 6501 (around 4.5 if I >>> use -j2). >>> A kernel compile took an hour. Unfortunately I had no idea this CPU >>> (possibly implementation?) was so slow before I purchased it, and I >>> could >>> scarcely find evidence of it on google after hours of searching when >>> I had >>> already discovered the issue. I was hoping to find some comparative >>> benchmarks between various Atom series but manufacturers generally >>> don't do >>> that. >>> >>> Additionally, the total AHCI SATA write speed on the net6501 (in BSD >>> only?) >>> has a strange 20MB/sec limitation but reads can go over 100MB/sec. >>> If I >>> write to one disk I get 20MB/sec, if I write to both SATA disks I get >>> 10MB/sec each. Write is equally slow on a SSD. Both someone running >>> OpenBSD and I running FreeBSD reported the same symptoms to the >>> soekris-tech >>> mailing list and received no useful replies towards getting that >>> problem >>> solved. I tested the write speed briefly with Linux and it did not >>> appear >>> to have the 20MB/sec limitation. I did confirm it was using >>> MSI(-X?) with >>> boot -v. I think this hardware would need to fall into Alexander >>> Motin's >>> hands to get anywhere with debugging the SATA speed issue. Since it >>> seems >>> fine in Linux, maybe some day it can be fixed in BSD but I have no >>> clue how >>> that limitation could happen. The disks I tested with are fine in >>> normal >>> computers. >>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:54:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2F499640; Tue, 8 Oct 2013 00:54:25 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E4B0522EA; Tue, 8 Oct 2013 00:54:24 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r980sNGO092244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 17:54:24 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r980sNmH092243; Mon, 7 Oct 2013 17:54:23 -0700 (PDT) (envelope-from jmg) Date: Mon, 7 Oct 2013 17:54:23 -0700 From: John-Mark Gurney To: Glen Barber Subject: Re: rcs is gone? Message-ID: <20131008005423.GD56872@funkthat.com> Mail-Followup-To: Glen Barber , Igor Mozolevsky , "freebsd-current@freebsd.org" , Andreas Nilsson References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> <20131008003642.GC56872@funkthat.com> <20131008004253.GG2133@glenbarber.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131008004253.GG2133@glenbarber.us> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 07 Oct 2013 17:54:24 -0700 (PDT) Cc: "freebsd-current@freebsd.org" , Andreas Nilsson , Igor Mozolevsky X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:54:25 -0000 Glen Barber wrote this message on Mon, Oct 07, 2013 at 20:42 -0400: > On Mon, Oct 07, 2013 at 05:36:42PM -0700, John-Mark Gurney wrote: > > > > So there's no version control in the base at all now?.. When did FreeBSD > > > > decide to move away from distributing a usable OS? Why not just distribute > > > > a kernel and a few bits that are barely sufficient for the initial set up, > > > > and then make users fetch everything from ports? > > > > > > > > > > svnlite? > > > > cd /etc > > svnliteadmin create svn > > svnlite co file:///etc/svn . > > svnlite add rc.conf > > svnlite commit rc.conf > > > > instead of: > > cd /etc > > ci rc.conf > > > > really? > > > > No, not really. > > # mkdir local > # svnadmin create ./local > # svn import /etc file:///$PWD/local besides the s/svn/svnlite/ you forgot... It doesn't work... Sure it imports all of my /etc, but doesn't let me commit my changes to rc.conf: # svnlite commit rc.conf svn: E155007: '/etc/rc.conf' is not a working copy Plus, I was quite reasured that svn isn't smart enough to realize that a path might be a file: url relative to the current working directory... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:58:14 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1B5FA77C; Tue, 8 Oct 2013 00:58:14 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E0FBF2307; Tue, 8 Oct 2013 00:58:13 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VTLcq-000GPP-E6; Tue, 08 Oct 2013 00:58:12 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r980w8CX017941; Mon, 7 Oct 2013 18:58:08 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+EWlnJOWnKMfctzwCmYl7M Subject: Re: rcs is gone? From: Ian Lepore To: Adrian Chadd In-Reply-To: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> Content-Type: text/plain; charset="us-ascii" Date: Mon, 07 Oct 2013 18:58:08 -0600 Message-ID: <1381193888.1130.42.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Lyndon Nerenberg , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:58:14 -0000 On Mon, 2013-10-07 at 16:49 -0700, Adrian Chadd wrote: > I've asked on IRC to figure out when this was first proposed. I'll see if > it was announced anywhere or if Eitan snuck it in. > > > -a It was mentioned briefly on stable@ http://lists.freebsd.org/pipermail/freebsd-stable/2012-August/069252.html And discussed at greater length in the context of removing cvs on arch@ http://lists.freebsd.org/pipermail/freebsd-arch/2012-September/012975.html http://lists.freebsd.org/pipermail/freebsd-arch/2012-September/013077.html I have not re-read those threads to see just how much of the discussion involved rcs, I just spot-checked a few and confirmed my memory that it showed up in some of the messages there. -- Ian From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:59:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 23A328A2; Tue, 8 Oct 2013 00:59:04 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9F4A4231E; Tue, 8 Oct 2013 00:59:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.5/8.14.5) with ESMTP id r980wsc6052995; Tue, 8 Oct 2013 04:58:54 +0400 (MSK) (envelope-from marck@rinet.ru) Date: Tue, 8 Oct 2013 04:58:54 +0400 (MSK) From: Dmitry Morozovsky To: Julian Elischer Subject: Re: rcs is gone? In-Reply-To: <52534C04.60909@freebsd.org> Message-ID: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <52534C04.60909@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (woozle.rinet.ru [0.0.0.0]); Tue, 08 Oct 2013 04:58:54 +0400 (MSK) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:59:04 -0000 On Tue, 8 Oct 2013, Julian Elischer wrote: > > > Or do you really only run the base OS and no other software on your > > > systems, without any of your own code or any customisation? > > We install from the base release ISO images burned on DVDs. > > > > We are physically air-gapped from the internet, none of the "end users" of > > the system have access to USB ports, and there are no electronic devices > > allowed into the development shop. > > > > We have a scheme for bringing in software from /usr/ports, but it is > > painful. And those ports can't necessarily walk on to all the systems in > > the shop. (I don't make the rules. Suffice to say the company is very > > paranoid about their code getting out into the wild.) > > > > Having RCS in the base system is very useful. We use it to track changes to > > bits of /etc on the machines where we don't do wholesale customizations. > > (Those ones get git, but they also get an install of /usr/ports with a fully > > populated /usr/ports/distfiles.) > > > > So if nuking RCS is a case of "I don't use it," ... we do. > > +1 Moreover, IIRC, some key files in FreeBSD own cluster had been archived by RCS... -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 00:59:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3CAEA9B4; Tue, 8 Oct 2013 00:59:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0F5E3232E; Tue, 8 Oct 2013 00:59:55 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 4F54D8C0F; Tue, 8 Oct 2013 00:59:52 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 4F54D8C0F Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 7 Oct 2013 20:59:50 -0400 From: Glen Barber To: John-Mark Gurney Subject: Re: rcs is gone? Message-ID: <20131008005950.GA24985@glenbarber.us> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> <20131008003642.GC56872@funkthat.com> <20131008004253.GG2133@glenbarber.us> <20131008005423.GD56872@funkthat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <20131008005423.GD56872@funkthat.com> X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-current@freebsd.org" , Andreas Nilsson , Igor Mozolevsky X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 00:59:55 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 07, 2013 at 05:54:23PM -0700, John-Mark Gurney wrote: > > No, not really. > >=20 > > # mkdir local > > # svnadmin create ./local > > # svn import /etc file:///$PWD/local >=20 > besides the s/svn/svnlite/ you forgot... It doesn't work... Sure it WITH_SVN in src.conf will install svnlite as svn. > imports all of my /etc, but doesn't let me commit my changes to rc.conf: > # svnlite commit rc.conf > svn: E155007: '/etc/rc.conf' is not a working copy Sure it does. gjb@nucleus:~/svn % mkdir local gjb@nucleus:~/svn % svnadmin create ./local gjb@nucleus:~/svn % cp -rp /usr/local/etc/rc.d fakelocaletc gjb@nucleus:~/svn % svn import ./fakelocaletc file:///$PWD/local -m "Initia= l import." gjb@nucleus:~/svn % svn co --force file:///$PWD/local fakelocaletc Checked out revision 1. gjb@nucleus:~/svn % svn stat !$ svn stat fakelocaletc gjb@nucleus:~/svn % svn info fakelocaletc Path: fakelocaletc Working Copy Root Path: /usr/home/gjb/svn/fakelocaletc URL: file:///home/gjb/svn/local Relative URL: ^/ > Plus, I was quite reasured that svn isn't smart enough to realize that > a path might be a file: url relative to the current working directory... I don't know what you mean by this. Glen --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSU1kGAAoJELls3eqvi17QkIkQAL3n4tfH8V6HC+TkEsaBBNHH 94QJDDbtvC8DZE8UuPdcVGJoDpeT+Ufo+GcZ0VkHADfkdiyavUuWmUfJIJs8w/A5 YdXry2lTiw4/Db7M2vIUV06Vg/3RAPZwt2DH6lz/czabkMTW7JtRd101e4ZegzgV rNaYtJE1K+zPAn6xPRerkTDieTyLVftrzDz4q1R3nlFzGgVMaPplZLZSHrAKZQRg CCx+T0h53VF3aa5J+wu0n20u5gdTDwptcJF2noj3TX3ijHIDuQ0PXNFx8bs4Ta3k PdHRbktmupjgVOYM80MchlKJFhTHEa5Wk2Umne9DNrhgZjJtRMjmhHx6ACwO5HBS Mz284DebQtVduO217Svbx7NU0qAAi6i6g7Cf6XuBQB/WIeivFwbsweEZ7LUYRNRy 58jOGFnXdUXk6udSgjHuhyIMJcw3mKyE5HvA6c5gT0gEHKJ7GdUppUdMcFXM1iVU L6HQQD9iQSU+TnB2lAZ0kviwVsyJOoziFMKpMpY0HXkktLEpIZCI9jRaQibnk6S4 x7HIPnKkiudLbHhGRzq6V84bmAZaGvUtDW2JaUHopP/M/15BirF4NQ+mBjKRfFld 4X5PvxrDdmg1qdQxiIAkScu/xuCoR6+ZootBJK8YPm/CGyMZG/iVTEIc4zQjo8uU jhW+/sXZagfq1+FkkxLL =STSB -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:02:37 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 33D3BADC; Tue, 8 Oct 2013 01:02:37 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C1D9E236D; Tue, 8 Oct 2013 01:02:36 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id k15so3349532qaq.15 for ; Mon, 07 Oct 2013 18:02:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=e+zLZTfMF1zcdgx8lZJ6EcqkmvfFNwpuE6CCYSytD9I=; b=gVVbVjpr8riEm/QuNcOKKSgjy9wG7U5S2nnC6lKT4d6rRt+/R0Ar6acDQZ2ELH1AHj LEqpHIyCAR5UcRNZxtFJNQ8DLg0JDUADlmq53FR4gIwRAoXXUrKPHFiO4+aUe1x0MEb5 3gDFYCVAYMcLrWvKbkoWvRxaPM5ilCko4r7pyc0L3FLsqoqb1xyNzRPd9cVItx/rjbAY IwPuGhctUWy9J1fLKumVMLOF/t6rJWKEiyb4iJJ0a1XriW7nOztDIoLUJTBkVcV6Le+u 489KTT10KPX51cARlUirtsZsj/NsIWXWaJfTRR8r/tcw4jRdw/RlRXGVQa6hY5BKHPI9 8Oxg== X-Received: by 10.229.38.202 with SMTP id c10mr7618659qce.23.1381194155905; Mon, 07 Oct 2013 18:02:35 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Mon, 7 Oct 2013 18:01:55 -0700 (PDT) In-Reply-To: <1381193888.1130.42.camel@revolution.hippie.lan> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1381193888.1130.42.camel@revolution.hippie.lan> From: Igor Mozolevsky Date: Tue, 8 Oct 2013 02:01:55 +0100 X-Google-Sender-Auth: BXGYIHIZjmQbwDJ8NhGPHRqFRdc Message-ID: Subject: Re: rcs is gone? To: Ian Lepore Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Adrian Chadd , "freebsd-current@freebsd.org" , Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:02:37 -0000 On 8 October 2013 01:58, Ian Lepore wrote: > On Mon, 2013-10-07 at 16:49 -0700, Adrian Chadd wrote: > > I've asked on IRC to figure out when this was first proposed. I'll see if > > it was announced anywhere or if Eitan snuck it in. > > > > > > -a > > It was mentioned briefly on stable@ > > http://lists.freebsd.org/pipermail/freebsd-stable/2012-August/069252.html > > And discussed at greater length in the context of removing cvs on arch@ > > http://lists.freebsd.org/pipermail/freebsd-arch/2012-September/012975.html > > http://lists.freebsd.org/pipermail/freebsd-arch/2012-September/013077.html > > I have not re-read those threads to see just how much of the discussion > involved rcs, I just spot-checked a few and confirmed my memory that it > showed up in some of the messages there. > Hold on a SECOND! Those messages had a subject line of "Removing CVS from base", if one is not affected by that why on earth would one think that that discussion might involve RCS??? Perhaps I am different, but I really do lack telepathic abilities... -- Igor M. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:03:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 360ADC89 for ; Tue, 8 Oct 2013 01:03:26 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 00FB02384 for ; Tue, 8 Oct 2013 01:03:25 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id r9812uJo028689 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 7 Oct 2013 20:03:19 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Mon, 7 Oct 2013 20:03:08 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOw7xkPJPIP8ZCyUiSsjBzr2++AA== Date: Tue, 8 Oct 2013 01:03:07 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC40459@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52531F95.6050002@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC40159@LTCFISWMSGMB21.FNFIS.com> <5253525C.2000701@allanjude.com> In-Reply-To: <5253525C.2000701@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <0330077866A9A446986B1D500996817E@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-07_05:2013-10-08,2013-10-07,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:03:26 -0000 On Oct 7, 2013, at 5:31 PM, Allan Jude wrote: > On 2013-10-07 20:21, Teske, Devin wrote: >> On Oct 7, 2013, at 5:18 PM, Warren Block wrote: >>=20 >>> On Mon, 7 Oct 2013, Allan Jude wrote: >>>=20 >>>> On 2013-10-07 16:43, Warren Block wrote: >>>>> On Mon, 7 Oct 2013, Allan Jude wrote: >>>>>=20 >>>>>> Additional, it includes some other changes to bsdinstall: >>>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>>>>> to no >>>>> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/162175 . >>>> That is a good idea, I'll add that >>>>=20 >>>> I've also hit this: >>>> http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/0= 00949.html >>>> and plan to throw in a fix for that. >>>> Which makes more sense, blindly 'killall dhclient' before we try to >>>> acquire a new lease, or detect that dhclient is running and try to use >>>> the IP that has already been assigned? >>> killall seems all right. In fact, internally, it's going to do that ch= eck. If nothing named dhclient is running, it will return immediately. >>>=20 >>> Although on 10.0, dhclient does not want to die sometimes. >>>=20 >>> Here's another PR for usability: >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dbin/161547 >> Hope you guys aren't rewriting bsdconfig's network.subr >=20 > These changes are in usr.sbin/bsdinstall/scripts/network and > usr.sbin/bsdinstall/scripts/network_ipv4 >=20 Correct, but I meant "reinvent" actually. There's an enormous API for dealing with the network. /usr/share/bsdconfig/media/tcpip.subr Is for acquiring/maintaining active TCP connections Meanwhile,... /usr/share/bsdconfig/network/*.subr Is for configuring permanent network settings that stick after a reboot. > I've not touched bsdconfig's network stuff >=20 Probably worth a look. It can probably replace bsdinstall's netconfig. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:04:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1F53FDA7; Tue, 8 Oct 2013 01:04:26 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C06BB239B; Tue, 8 Oct 2013 01:04:25 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id k15so3350569qaq.15 for ; Mon, 07 Oct 2013 18:04:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=d78LhVs6QmvlheXwLP770Bov1XTpL2zsK4qw+cSdJAU=; b=b5j4/hSjiYJrFFY5YC5T5AzljMmQnYC/fpEq+fHTj708Eee7Mxc361pVYcJLi53cUw /+W/Wzegu4av0QAylNKt8vVRu8vVeXanHZvRR3IzVBDK0e1lrmwUbDwipW3l9/tvs89P F/jaQPxxn3rV4mJA1QKD7ELIAhCDL/3zeHe8442kkO3CL7HlEerecbp36E6ontbGHBdL AWuZ6huOVejdiLpZ9Rk7gzaAypVYuwfrTuJkfTRayuZ5XuF81xFXb5W9zs7FgtVg9OcY 4HZVhqTpm5VWQUKOPnc0ZmMTCPbp7wNTxoPTHPRppFkYmNFUN3/mDwqjwmpsaNZxVK+u TlGw== X-Received: by 10.49.47.50 with SMTP id a18mr40326979qen.61.1381194264981; Mon, 07 Oct 2013 18:04:24 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Mon, 7 Oct 2013 18:03:44 -0700 (PDT) In-Reply-To: <20131008005950.GA24985@glenbarber.us> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> <20131008003642.GC56872@funkthat.com> <20131008004253.GG2133@glenbarber.us> <20131008005423.GD56872@funkthat.com> <20131008005950.GA24985@glenbarber.us> From: Igor Mozolevsky Date: Tue, 8 Oct 2013 02:03:44 +0100 X-Google-Sender-Auth: fzqVeqALmUzBIW44IuKQkKwWkQ4 Message-ID: Subject: Re: rcs is gone? To: Glen Barber Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: John-Mark Gurney , "freebsd-current@freebsd.org" , Andreas Nilsson X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:04:26 -0000 On 8 October 2013 01:59, Glen Barber wrote: > On Mon, Oct 07, 2013 at 05:54:23PM -0700, John-Mark Gurney wrote: > [snip] > > Plus, I was quite reasured that svn isn't smart enough to realize that > > a path might be a file: url relative to the current working directory... > > I don't know what you mean by this. I think he means file://./file.conf -- Igor M. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:06:04 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 63533ED9; Tue, 8 Oct 2013 01:06:04 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 23FE123BA; Tue, 8 Oct 2013 01:06:04 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r98160gN025917 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 18:06:02 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: <1381193888.1130.42.camel@revolution.hippie.lan> Date: Mon, 7 Oct 2013 18:05:59 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <7C8EB71B-DBA4-49F3-80F4-D579A596A540@orthanc.ca> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1381193888.1130.42.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1510) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:06:04 -0000 On 2013-10-07, at 5:58 PM, Ian Lepore wrote: > I have not re-read those threads to see just how much of the = discussion > involved rcs, I just spot-checked a few and confirmed my memory that = it > showed up in some of the messages there. I don't see any discussion as to why the code (CVS, in this case) = *needs* to be removed. What, in the current builds of 10.x, is broken by leaving RCS/CVS in = place? And what, as 10.x moves forward towards a public release, will = be broken by leaving this code in the base? From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:10:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 437B8112; Tue, 8 Oct 2013 01:10:41 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 150DB23EC; Tue, 8 Oct 2013 01:10:41 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id C87438CF4; Tue, 8 Oct 2013 01:10:39 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us C87438CF4 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 7 Oct 2013 21:10:37 -0400 From: Glen Barber To: Igor Mozolevsky Subject: Re: rcs is gone? Message-ID: <20131008011037.GB24985@glenbarber.us> References: <20131007212925.GC2133@glenbarber.us> <20131008003642.GC56872@funkthat.com> <20131008004253.GG2133@glenbarber.us> <20131008005423.GD56872@funkthat.com> <20131008005950.GA24985@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wzJLGUyc3ArbnUjN" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: John-Mark Gurney , "freebsd-current@freebsd.org" , Andreas Nilsson X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:10:41 -0000 --wzJLGUyc3ArbnUjN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 08, 2013 at 02:03:44AM +0100, Igor Mozolevsky wrote: > On 8 October 2013 01:59, Glen Barber wrote: >=20 > > On Mon, Oct 07, 2013 at 05:54:23PM -0700, John-Mark Gurney wrote: > > >=20 > [snip] >=20 >=20 > > > Plus, I was quite reasured that svn isn't smart enough to realize that > > > a path might be a file: url relative to the current working directory= =2E.. > > > > I don't know what you mean by this. >=20 >=20 > I think he means file://./file.conf >=20 If so, that does not work. That is why I used 'file:///$PWD/'. Glen --wzJLGUyc3ArbnUjN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSU1uNAAoJELls3eqvi17QSQEP/iWJMWUYvhi2h8bNNs9rAjZw JQr7jYoLB86o2JTOeQeykLehmrAhauzd+NtUVmdFIBsXcVOKzsVKAAoTo0j7pvDk 3L5rN+nfwfkHeenEVQIfaUkWADBl6v4kf7tJJClJd5lCKmydjh6/YnKb/gbraBDP EWE59AY+DYDNANSuWTNd7qUP8GjMzKNhTaoGP9eGRqRebfd4rGwGtjmMRXaGp+bs gRbBMlmvJiBPNdXdcMrkEcXWtdW6X8EwNgIJAU3uQb/5KvC4qBI3Zf2hco6JK8WY QF1wOdrLsoRdoSOvdlorMa9UsRWHC0cVqcf89Wv7MF6ZfAQvQ61/P2LLz9AogBQ7 i7rHwXvn1t7FPPZiS1hj5b2jXIkg0qjzZrE+1nCX5WFyYlhHWyhUEpQVBoFO1I4M 02vE+OCt3CQ5MAhD48EGajBguCl92hcrSUnGqtmyhOofKV4VdUb7Pf91BArYYkpA yeNK/nfoqbqhhO9AtEqIEmQbqcy8utcZZqD7vs/w3xuQh8SBCvHWIcMy45+yfhN9 J1lOvZi+KAiYhxzNSM+eUtVjA5M1jH5xNbphRW2b6ibeDQpKlYHi6NXaK51TNmRl vMzkJYVZKtsx3OkT3GsmF6eHUDFJDqufgTYkFc510f2YzAucYFBvCn/7Y2C8kOE+ /A2JRMFU7CKcv4aMpWEx =xRo+ -----END PGP SIGNATURE----- --wzJLGUyc3ArbnUjN-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:15:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7371624D; Tue, 8 Oct 2013 01:15:41 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4F0FB2431; Tue, 8 Oct 2013 01:15:41 +0000 (UTC) Received: from zeta.ixsystems.com (unknown [69.198.165.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id E15FF29E47; Mon, 7 Oct 2013 18:15:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1381194935; bh=mcBTzPw2TIhtxC6c+wEqMbdVOXxkJ091rf/gqoDisFg=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=jIfYFRINBGfKnOFz5UsliSo+Lv+X0QcZexRASalezOSJaX09P+1tqnW1xGyR7Jg2e rcfTtaanTsUrjNpxKGrjInGVz0vEdJSgomy/y76ULfDYlUqU+5T66tUT9qDIGvsWzq hLDhf1DvzT2gmOP8ZdtiFsBo1X0dSjfnDdjf4F04= Message-ID: <52535CB6.3030906@delphij.net> Date: Mon, 07 Oct 2013 18:15:34 -0700 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Glen Barber , Igor Mozolevsky , "freebsd-current@freebsd.org" , Andreas Nilsson Subject: Re: rcs is gone? References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> <20131008003642.GC56872@funkthat.com> <20131008004253.GG2133@glenbarber.us> In-Reply-To: <20131008004253.GG2133@glenbarber.us> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:15:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 10/07/13 17:42, Glen Barber wrote: > On Mon, Oct 07, 2013 at 05:36:42PM -0700, John-Mark Gurney wrote: >>>> So there's no version control in the base at all now?.. When >>>> did FreeBSD decide to move away from distributing a usable >>>> OS? Why not just distribute a kernel and a few bits that are >>>> barely sufficient for the initial set up, and then make users >>>> fetch everything from ports? >>>> >>> >>> svnlite? >> >> cd /etc svnliteadmin create svn svnlite co file:///etc/svn . >> svnlite add rc.conf svnlite commit rc.conf >> >> instead of: cd /etc ci rc.conf >> >> really? >> > > No, not really. > > # mkdir local # svnadmin create ./local # svn import /etc > file:///$PWD/local There is a feature that is lacking from svn: the permissions is not quite tightened up. With RCS, for instance, a mode 600 file would result in a mode 400 ,v file. With subversion, everything is dependent on the current user's umask. So let's say the root checks in master.passwd, with RCS, the resulting ,v file would be mode 400 but with svn, the local cached copy and the file in the repository would be both world readable. Of course, this can be worked around by chmod'ing all the toplevel directories to 700 or group accessible but it's not quite convenient and can be easily overlooked. However, even when I use RCS pretty often, I don't think it's a good idea to keep it in base system (actually I am supportive in removing it from the base). The version shipped with base was not touched for many years and shipping it with base makes it hard to use a newer version from ports. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iQIcBAEBCgAGBQJSU1y2AAoJEJW2GBstM+nszXkQAKmaSZVELYkQY0i6SqeWXRAd gOONugSTFq1jMS0fd7LVkrrcGsFa1VpMOf4FctS6iWK1cY8ZJhqYizsu4Qb9eP5e DciRRtcB337VX3iBAN9vJEgLYiyj7X6RlvspGVJW00QaJFmgrbLuMjkFGxjs/PYN OVDaIEZCW7FmdHXSbsX7nTiWkWkh/UoMPAzdNNwb+ICKrQB6iWscWBOVQWhufSQZ mEJr/3exbu9We9kBtk8Qa9pnHYw5Xao8jqNyESORRtDnrznK14Dyc2jdr61Bnlc6 nRGioYhViioVt6x3FekKszZ5/zNr39/Wm+Xv/RNLbhB8SlyEcXjSTfIGByostI2B r+GibrjOiIGPwntNQcvbm2gwaDaSoWo/xKCeXPoOAViolIALUTkxKlZ7h9qYuoZp h4rxgENtJlAdKH1SNrSPAaMPnyTzD5GBz2VWN9QGo2TPyxC4NywF/tN0Hz/WEcRN ruEQ+E9bG0JiiffIo1OJQLeaLp2yTStqgPJG9jYg2e7yfK+Wa66U40sWpWhdIvPq K5xDtPb01Q91V+J16V++qJPu9uq4rnO7Rk5Ak1vFGRXYuvPHpMovnKKSDO9SaGb2 DXIfTDl4rWTn/WV9o0lriZJyqP31z4ABN47nMc0/2b2+Z1tKLwbaJ5btOHkxFBL3 dJUp+dP1IeZCeESiVBlL =6X09 -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:16:56 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 94A963DF; Tue, 8 Oct 2013 01:16:56 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 46C6A2456; Tue, 8 Oct 2013 01:16:55 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r981Gosm034738 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 18:16:53 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52535CFC.6010704@freebsd.org> Date: Tue, 08 Oct 2013 09:16:44 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Lyndon Nerenberg Subject: Re: rcs is gone? References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1381193888.1130.42.camel@revolution.hippie.lan> <7C8EB71B-DBA4-49F3-80F4-D579A596A540@orthanc.ca> In-Reply-To: <7C8EB71B-DBA4-49F3-80F4-D579A596A540@orthanc.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , core@freebsd.org, Ian Lepore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:16:56 -0000 On 10/8/13 9:05 AM, Lyndon Nerenberg wrote: > On 2013-10-07, at 5:58 PM, Ian Lepore wrote: > >> I have not re-read those threads to see just how much of the discussion >> involved rcs, I just spot-checked a few and confirmed my memory that it >> showed up in some of the messages there. > I don't see any discussion as to why the code (CVS, in this case) *needs* to be removed. > > What, in the current builds of 10.x, is broken by leaving RCS/CVS in place? And what, as 10.x moves forward towards a public release, will be broken by leaving this code in the base? I have less of a problem with replacing CVS with svnlite than I have with removing RCS. After all CVS's main reason for being in the system has switched to svnlite. And if you are using CVS yourself for other developement, you are probbaly further on with installing a system and are already installing other packages. that's not the case with RCS. I know that people use it as part of their install procedure. Plus RCS is used within other tools. e.g. patch etc. It's also a REALLY SMALL utility, suitable for embedding into scripts etc. (the Unix way(TM)) I consider it a base utility. It does a simple operation on a file. the discussion in arch was A YEAR AGO, was hidden under a differnet title, and DID NOT RESULT in a clear mandate to remove RCS. Please put it back, and inthe mena while while we discuss it properly this time, please revert the commit (official request.. as described in the group rules). > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:24:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 91F2156F; Tue, 8 Oct 2013 01:24:53 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6D63B24BE; Tue, 8 Oct 2013 01:24:53 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r981OpGZ092863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 18:24:52 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r981OpXn092862; Mon, 7 Oct 2013 18:24:51 -0700 (PDT) (envelope-from jmg) Date: Mon, 7 Oct 2013 18:24:51 -0700 From: John-Mark Gurney To: Gleb Kurtsou Subject: Re: Committing PEFS to CURRENT Message-ID: <20131008012451.GE56872@funkthat.com> Mail-Followup-To: Gleb Kurtsou , Gleb Kurtsou , "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore References: <20131007163111.GB1590@reks.swifttest.com> <20131007231734.GY56872@funkthat.com> <20131008002314.GA56872@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 07 Oct 2013 18:24:52 -0700 (PDT) Cc: Gleb Kurtsou , "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:24:53 -0000 Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 17:41 -0700: > On Mon, Oct 7, 2013 at 5:23 PM, John-Mark Gurney wrote: > > Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 16:47 -0700: > >> On Mon, Oct 7, 2013 at 4:17 PM, John-Mark Gurney wrote: > >> > Gleb Kurtsou wrote this message on Mon, Oct 07, 2013 at 09:31 -0700: > >> >> Patch is available here: > >> >> https://github.com/glk/freebsd-head/commit/b4d2c4a5f42f88fdd07cb75feba3467e4d4c043c.patch > >> > > >> > Is there a reason you are writing your own AES-NI implementation instead > >> > of using the OpenCrypto framework? > >> > >> It reuses the same AES-NI implementation used by opencrypto, > >> but code doesn't use opencrypto directly. Main limitation in opencrypto is > >> that is incomplete implementation AES-XTS -- it doesn't implement ciphertext > >> stealing. opencrypto contexts seemed to be too much overhead list time I > > > > I remember noticing that when I was working on it.. but as there are > > different modes of packing/padding, I decided not to do anything with > > that... > > > > I also don't like your lack of comments arround xts_lastblock and about > > why it is accessing dst - 1... To me, you should pass in the previous > > block as an arg to xts_lastblock instead of doing dst[-1]... You did > > comment what you're doing (m - 1), but not why it is safe to do that... > > There is no comment that you're implementing ciphertext stealing w/ the > > function which makes it even harder to understand that you'd going it > > properly... > > The code comes from University of Tsukuba. The function is internal to > the module and is safe to use that way if you look at pefs_xts_block_encrypt > and pefs_xts_block_decrypt. That doesn't make it exempt from good coding style or modification to be easier to review... > > It wouldn't be hard to add ciphertext stealing to the opencrypto > > implementation if that is really all that is missing... but.. > > > >> looked at them especially in the case of multiple keys per file system in PEFS. > >> AES-NI interface is not designed to be used outside of opencrypto thus > >> some minor copy-past. > > > > We have discovered that by the "minor" copy/paste we now have an > > inferior implementation of AES-XTS... If it performed similar to the > > one before it, it is over 10x slower than the one that I committed.. > > > >> > I updated the kernel's AES-NI implementation to have a very fast > >> > AES-XTS... Upon looking at your implementation, you have a very > >> > slow implementation as you do not pipeline AES-XTS at all... Please > >> > switch to using the opencrypto version.. You'll then be able to make > >> > use of any accelerators that other platforms may have... > >> > >> I was looking into incorporating AES_XTS pipeline changes in PEFS. > >> I'd like to avoid switching to opencrypto at this point. But pipelining is > >> doable without opencrypto and copying code around. > > > > I really don't like the idea of adding yet anothe AES-XTS implementation > > to our tree (especially considering how bad both the previous one and > > this one is)... Even if you do bring over the pipeline changes... > > It'll be yet another copy of code to maintain and port performance > > improvements too... > > > > We could always refactor the AES-NI code to make it more usable outside > > the opencrypto framework as a stepping stone to possibly using pjd's > > improved opencrypto framework... > > Refactoring AES-NI would be ideal, it would also be great to extract AES-XTS > implementation and make it usable outside of opencrypto adding ciphertext > stealing. As for making it usable outside of opencrypto, I'd prefer that we figure out if we should use pjd's improvements, or if we really want to make AES-NI a first class citizen in the kernel, and if the later, figuring out a proper API for it... I'm nervous that we are rushing these changes into the tree... I do like the idea of getting PEFS into the kernel, but it doesn't feel like it's been properly reviewed/integrated yet... > > But copy/pasting just because we don't want to do a bit more work isn't > > good justification... > > It's not that I "don't want to do a bit more work" I never said that, > it's rather > about avoiding changes after KBI freeze. But will the work get done to clean it up after the freeze is over? What happens if it doesn't, will it get removed before 10.1 or will we have to live w/ the code? > >> > Are there plans to add authentication to this scheme? See that as a > >> > todo, but w/o authentication, you can't store anything reliably on it.. > >> > And w/ XTS, the attacker can take pot shots at your file in 16 byte > >> > chuncks... > >> > >> I have data authentication prototype. It's too far from being complete, > >> and I keep working on it as time permits. There are a few more ideas > >> I'd like to work on while redesigning the file system. > >> > >> Patch also includes hmac and pkcs5v2 implementations which in fact > >> were generic versions to go under sys/crypto until yesterday. > >> Considering we are late in code freeze already I've merged them > >> into PEFS not to touch geli code with the patch. > > > > Can't you keep them named the same under sys/crypto and just link w/ them > > as necessary to prevent repo churn when you finally integrate them into > > sys/crypto? That seems better than moving them arround, though I guess > > w/ svn, it isn't as big of a deal... Someone w/ a repo hat on should > > chime in here... > > It won't be possible at least because of pkcs5v2_genkey() (name collision) > being defined internally in geli and pkcs5v2 using hmac from geli. Moving > them to sys/crypto in 11-CURRENT is a minor issue IMHO. I was pushing > those changes to HEAD years ago, but they got stuck somewhere in > review process. ok... > >> > The only reason I'm running zfs on geli w/o authentication is that I'm > >> > using a 256bit checksum, so the chances of someone modifing two blocks > >> > to fool zfs into decrypting the correct new checksum value for their > >> > modified block is very small... In short, I'm trusting zfs to do the > >> > authentication for me... As long as we have a plan forward for what needs to be done and what will be done, I'm fine... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:30:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 877F4730; Tue, 8 Oct 2013 01:30:29 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 676592523; Tue, 8 Oct 2013 01:30:29 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r981UN7u031382; Mon, 7 Oct 2013 18:30:23 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r981UNeS031381; Mon, 7 Oct 2013 18:30:23 -0700 (PDT) (envelope-from sgk) Date: Mon, 7 Oct 2013 18:30:23 -0700 From: Steve Kargl To: Julian Elischer Subject: Re: [Heads Up] RCS removed from base Message-ID: <20131008013023.GA31261@troutmask.apl.washington.edu> References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52534B5E.7010401@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org, core@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:30:29 -0000 On Tue, Oct 08, 2013 at 08:01:34AM +0800, Julian Elischer wrote: > On 10/7/13 11:06 PM, Steve Kargl wrote: > > On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: > >> Hey all, > >> > >> RCS was removed from the base system in r256095. If you still want to > >> use RCS please install either devel/rcs or devel/rcs57. If not, be > >> sure to check out the alternatives (pun stolen and intended). > >> > > Perhaps, a note in src/UPDATING is appropriate? > > > ok so what is this, the secret cabal to make FreeBSD useless? I'm unsure why you are using the word 'cabal' here. I have no dog in this fight. I happen to read svn commit emails. I simply noticed that Eitan had removed RCS, and has a service to those that may use RCS I suggested that a note be added to src/UPDATING. PS: As noted, the code is GPL. There has been an effort to remove GPL code from FreeBSD (whether prudent or not). -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:30:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F2765843; Tue, 8 Oct 2013 01:30:45 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B7EA22531; Tue, 8 Oct 2013 01:30:45 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id g10so7946941pdj.16 for ; Mon, 07 Oct 2013 18:30:45 -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=ypoWWnhFIWoaelKQTjhNpOELAZhOkOML9v4+P6OHhIE=; b=cBGIdsiyRAz34OHKSh2F2ITSACr9eLLtY4y6vtvvYlQazLoJcPjex9gkvWO1wi93es 6n19kbX4L9iiWrY4+v3s0Ah4i3M1ZZlkXlZSBeCq+sSOVq1nyWOwLA+IWweKEIctFZdY 1X7WkCM9TOmZixWE8WC+njWe/RP8p7RkZeVG4ImM2kuA1SaRvCrVBKIFO02Z2d5GY32B 1GgBBjMzqAWyo5gkHHF898MoeMmGU0jhJpXp6tk9gbnh+dCn16oOmTK2aVBrnYyKRX7V KUYpIb/iRQVRefX+GwzVTnl1VcOgnGGbZX4dKoiton8HlL59gD7Auc4Azs/RaEtikP+W e1tw== MIME-Version: 1.0 X-Received: by 10.66.25.173 with SMTP id d13mr496738pag.146.1381195845336; Mon, 07 Oct 2013 18:30:45 -0700 (PDT) Received: by 10.70.92.79 with HTTP; Mon, 7 Oct 2013 18:30:45 -0700 (PDT) In-Reply-To: <52535CFC.6010704@freebsd.org> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1381193888.1130.42.camel@revolution.hippie.lan> <7C8EB71B-DBA4-49F3-80F4-D579A596A540@orthanc.ca> <52535CFC.6010704@freebsd.org> Date: Mon, 7 Oct 2013 20:30:45 -0500 Message-ID: Subject: Re: rcs is gone? From: Adam Vande More To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: core@freebsd.org, "freebsd-current@freebsd.org" , Lyndon Nerenberg , Ian Lepore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:30:46 -0000 On Mon, Oct 7, 2013 at 8:16 PM, Julian Elischer wrote: > On 10/8/13 9:05 AM, Lyndon Nerenberg wrote: > >> On 2013-10-07, at 5:58 PM, Ian Lepore wrote: >> >> I have not re-read those threads to see just how much of the discussion >>> involved rcs, I just spot-checked a few and confirmed my memory that it >>> showed up in some of the messages there. >>> >> I don't see any discussion as to why the code (CVS, in this case) *needs* >> to be removed. >> >> What, in the current builds of 10.x, is broken by leaving RCS/CVS in >> place? And what, as 10.x moves forward towards a public release, will be >> broken by leaving this code in the base? >> > I have less of a problem with replacing CVS with svnlite than I have with > removing RCS. > After all CVS's main reason for being in the system has switched to > svnlite. > And if you are using CVS yourself for other developement, you are probbaly > further > on with installing a system and are already installing other packages. > that's not the case with RCS. I know that people use it as part of their > install > procedure. Plus RCS is used within other tools. e.g. patch etc. It's also > a REALLY SMALL > utility, suitable for embedding into scripts etc. (the Unix way(TM)) I > consider it a base utility. > It does a simple operation on a file. > > the discussion in arch was A YEAR AGO, was hidden under a differnet title, > and DID NOT RESULT > in a clear mandate to remove RCS. > > Please put it back, and inthe mena while while we discuss it properly this > time, please revert the commit > (official request.. as described in the group rules). I would like to see RCS remain in base as well. Many enterprise distro still ship it by default too. There is no compelling reason to remove it. -- Adam Vande More From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:32:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3BC67978 for ; Tue, 8 Oct 2013 01:32:24 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 29C5A2553 for ; Tue, 8 Oct 2013 01:32:23 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id ED8601A3D08 for ; Mon, 7 Oct 2013 18:32:21 -0700 (PDT) Message-ID: <525360A5.8010908@mu.org> Date: Mon, 07 Oct 2013 18:32:21 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [Heads Up] RCS removed from base References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008013023.GA31261@troutmask.apl.washington.edu> In-Reply-To: <20131008013023.GA31261@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:32:24 -0000 On 10/7/13 6:30 PM, Steve Kargl wrote: > On Tue, Oct 08, 2013 at 08:01:34AM +0800, Julian Elischer wrote: >> On 10/7/13 11:06 PM, Steve Kargl wrote: >>> On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: >>>> Hey all, >>>> >>>> RCS was removed from the base system in r256095. If you still want to >>>> use RCS please install either devel/rcs or devel/rcs57. If not, be >>>> sure to check out the alternatives (pun stolen and intended). >>>> >>> Perhaps, a note in src/UPDATING is appropriate? >>> >> ok so what is this, the secret cabal to make FreeBSD useless? > I'm unsure why you are using the word 'cabal' here. I have > no dog in this fight. I happen to read svn commit emails. > I simply noticed that Eitan had removed RCS, and has a service > to those that may use RCS I suggested that a note be added to > src/UPDATING. > > PS: As noted, the code is GPL. There has been an effort > to remove GPL code from FreeBSD (whether prudent or not). > That plus the age of the code is good enough reason to ditch it! huzzah! Plus we can make RCSBSD along with it. -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:33:50 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BF46FA93 for ; Tue, 8 Oct 2013 01:33:50 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9EABA256A for ; Tue, 8 Oct 2013 01:33:50 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r981XoZO031437; Mon, 7 Oct 2013 18:33:50 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r981Xore031436; Mon, 7 Oct 2013 18:33:50 -0700 (PDT) (envelope-from sgk) Date: Mon, 7 Oct 2013 18:33:50 -0700 From: Steve Kargl To: George Mitchell Subject: Re: [Heads Up] RCS removed from base Message-ID: <20131008013350.GB31261@troutmask.apl.washington.edu> References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008002854.GB56872@funkthat.com> <525354C2.8070807@m5p.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <525354C2.8070807@m5p.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:33:50 -0000 On Mon, Oct 07, 2013 at 08:41:38PM -0400, George Mitchell wrote: > On 10/07/13 20:28, John-Mark Gurney wrote: > > Julian Elischer wrote this message on Tue, Oct 08, 2013 at 08:01 +0800: > >> not a big thing but I believe that a lot of poeple use ci/co on /etc > >> becasue it is "just there" > > > > +1 > > > Folks, this is just plain a major violation of the Principle of Least > Amazement. RCS is ideal for keeping track of my configuration files > in /etc. What do we gain by removing it? Less GPL code in FreeBSD? -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:37:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9F788BF7; Tue, 8 Oct 2013 01:37:58 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 60AFF2591; Tue, 8 Oct 2013 01:37:58 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id lj1so8134687pab.1 for ; Mon, 07 Oct 2013 18:37:58 -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=+ammdyMoirOhrRNeyRCEkvGjgAu4IdE2DBAgHEhtrTA=; b=vwPZkUW3ummgqgyhDNbr32a7uBYNHMZqa9HqPQnCzYs39J1R536ZvDe9NaT5NA0pu4 m60IZ/6HT3xy0lFly7zM/2Xio+72McUbcedUAPOxdnBl4QYMAdZphAt+wlTgbB645e6R /I0q25CJt1Tvwc5jpZ+E6AbIHziK++zNrb4yv9sZZwPBf4dWSUSqXhxLUcTPiDmfobaO slvJrYJ210SDQMnE2qnmpe43z0tuGvL4iGQJCCrW33jvwYWwaAJvvrAMJ+r7ZbFTbkbC JRdTiKuqA6Z+H7JD4EaQR5RR3AhPXohjnNiXIizPfPoYQ5KvrXLM0SmmYBESlQrZCMoK YA5A== MIME-Version: 1.0 X-Received: by 10.66.121.68 with SMTP id li4mr483945pab.33.1381196277944; Mon, 07 Oct 2013 18:37:57 -0700 (PDT) Received: by 10.70.92.79 with HTTP; Mon, 7 Oct 2013 18:37:57 -0700 (PDT) In-Reply-To: References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1381193888.1130.42.camel@revolution.hippie.lan> <7C8EB71B-DBA4-49F3-80F4-D579A596A540@orthanc.ca> <52535CFC.6010704@freebsd.org> Date: Mon, 7 Oct 2013 20:37:57 -0500 Message-ID: Subject: Re: rcs is gone? From: Adam Vande More To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: core@freebsd.org, "freebsd-current@freebsd.org" , Lyndon Nerenberg , Ian Lepore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:37:58 -0000 On Mon, Oct 7, 2013 at 8:30 PM, Adam Vande More wrote: > > I would like to see RCS remain in base as well. Many enterprise distro > still ship it by default too. There is no compelling reason to remove it. > I sort of retract that statement. I thought the base RCS was already OpenRCS. I support the inclusion of OpenRCS. That functionality is very useful and many admins are used to having it present. -- Adam Vande More From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:42:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B3E61FD3; Tue, 8 Oct 2013 01:42:25 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-qe0-x22d.google.com (mail-qe0-x22d.google.com [IPv6:2607:f8b0:400d:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 531A325FA; Tue, 8 Oct 2013 01:42:25 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id 8so2902400qea.4 for ; Mon, 07 Oct 2013 18:42:24 -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 :content-type; bh=dW+Jb9Zsw2sJBycKksy6wO9uSHt/MgLEs/1WrbvutMk=; b=ySrsRtpZIgsnHgiUPKPwys7W39F7+9YLZSWeHavS/+PfBmVuTG25Q7aQTOKIEY8Ugu mQ7H3zY6sET4Vj0ujbiw6NqEQavDmsE7C/BKGLA4qZy9CiD9IUN1aci72PeXupVN2ciM lwYrwnQ+vTYXLLUCzp3iSaL/t9bjNYPXOUvpRtqP57JVgihH305FGgxpatLCIAEwzIoE /i8+Aw9cmH2tmb/GiE0p78N1XAYrH4m8WWpEsR80H5a9iUwsCINmPHdpIme6z0H4BbzE vHWvJ8Qz8Fq37o/8FXSTqSWQFFRk4U997n9h6s27xpgLtk6Su6/AyXWawmvspaxh/j9/ /npA== MIME-Version: 1.0 X-Received: by 10.49.58.8 with SMTP id m8mr12504067qeq.71.1381196544383; Mon, 07 Oct 2013 18:42:24 -0700 (PDT) Received: by 10.229.114.5 with HTTP; Mon, 7 Oct 2013 18:42:24 -0700 (PDT) In-Reply-To: <20131008012451.GE56872@funkthat.com> References: <20131007163111.GB1590@reks.swifttest.com> <20131007231734.GY56872@funkthat.com> <20131008002314.GA56872@funkthat.com> <20131008012451.GE56872@funkthat.com> Date: Mon, 7 Oct 2013 18:42:24 -0700 Message-ID: Subject: Re: Committing PEFS to CURRENT From: Gleb Kurtsou To: Gleb Kurtsou , Gleb Kurtsou , "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:42:25 -0000 On Mon, Oct 7, 2013 at 6:24 PM, John-Mark Gurney wrote: > > But will the work get done to clean it up after the freeze is over? What > happens if it doesn't, will it get removed before 10.1 or will we have > to live w/ the code? I still hope not to get hit by bus any time soon.. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:44:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4E06F17C; Tue, 8 Oct 2013 01:44:38 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 25631260F; Tue, 8 Oct 2013 01:44:38 +0000 (UTC) Received: from zeta.ixsystems.com (unknown [69.198.165.132]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id C1D4129163; Mon, 7 Oct 2013 18:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1381196677; bh=ieNpDcX0heeZHigy6oUFCrV0W5e9MCyPqKqa3yYZmvo=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=MlS5wftuwJLmcEE/CTGMJvqHDgJNfjbJZlu/EjbW3WW7ncHX4A25p9Q2uisZd3Ncg yLv/KuHEL9lwNWNbKGi7PaNHMuiaRBIUeqwmhuKqmaPK4xdoKgLIvXxsmPuA4mpOcG f7dToXTVzz5Y1iIaY+LiyPlgUfX/eG5hn1LBiaDY= Message-ID: <52536385.4020903@delphij.net> Date: Mon, 07 Oct 2013 18:44:37 -0700 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Adam Vande More , Julian Elischer Subject: Re: rcs is gone? References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1381193888.1130.42.camel@revolution.hippie.lan> <7C8EB71B-DBA4-49F3-80F4-D579A596A540@orthanc.ca> <52535CFC.6010704@freebsd.org> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Lyndon Nerenberg , "freebsd-current@freebsd.org" , core@freebsd.org, Ian Lepore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:44:38 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 10/07/13 18:37, Adam Vande More wrote: > On Mon, Oct 7, 2013 at 8:30 PM, Adam Vande More > wrote: > >> >> I would like to see RCS remain in base as well. Many enterprise >> distro still ship it by default too. There is no compelling >> reason to remove it. >> > > I sort of retract that statement. I thought the base RCS was > already OpenRCS. I support the inclusion of OpenRCS. That > functionality is very useful and many admins are used to having it > present. I thought about this a few years ago but figured out that OpenRCS have many incompatibilities with GNU RCS (and fails GNU RCS regression tests) so if we do it, someone has to sit down and make sure the replacement have at least equal quality. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iQIcBAEBCgAGBQJSU2OFAAoJEJW2GBstM+nskxIQAJtRPwPA2S6FIYyPTsKbVgfE yYI0+yh1MBPssL0OYGLOC4r4Ot/dleCAMJMDSm/yZL4oj2ewLU3TCCq+0g6nvdAn 32ElrfYXKDYLWXManTx6ZUO4EsEPWQTyd9oYQA7x0yWJus4FirR1jUJ0PqHS5TXJ BcDZFO+BAN70wgR0NJZqUjXML+Z/u7lXEGwDZ27PurGtrQUhQ+QpauPTYQxAqkT+ X0GqxRDwt02zDUWo3zitDoMUqRxWXB4AzOaVDhbs8B2aLIIhNHOYjGytE0gVGOb+ GitDib13B5zEFYb+UtTOKv5dfvUMNNa8XIUAX4zD9uNP3ckEy5ZzvS65+n4ClInX 2eyeaVznnntTSNmjzCZSTKYXhxwmUSyeBQWTGVZk/o+m9qeFMv3cHGSXND6WWqJ2 2IYhX1i6Gj1gllIAIJ6PZ9/fScMz7GcZC9940xfnQbgF61A2+Rxrv/B44w6l/xeM sbLBomqozJXJ1d+9qo1x7tgl6EP5grZQGtSdLBlao936/PhzCCgwoHNkMiypl0MD jTlDVyvjUidfavL3rbhmf92x0ih+yNfoNFX5T42mOKEyUesV3uFqypVoAEn9Q9Q1 m7NTunH1t2gJ2EK/mckqU+V5pVXeK4Tfj+QKLddfTzGZyI0VIqsqlm8/x0mXSByd casIsVahiDmGxwztBljE =nH+R -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:49:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E34B63F0; Tue, 8 Oct 2013 01:49:11 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 90FC62672; Tue, 8 Oct 2013 01:49:11 +0000 (UTC) Received: by mail-oa0-f46.google.com with SMTP id k14so7076115oag.19 for ; Mon, 07 Oct 2013 18:49:11 -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=I957880BB3o0yIhfCWY+uxAyUg0DqV5gxSJ33RXDNCs=; b=hqoZe5pmR2LDEUYjVw9VgV9r2P2FwLFaJFAegJzjuBixPLMPDng6m3ZsxNIRn+4fj4 GmPNe0buWYJBAN5Egxvije8rVG2UaHW7RJxIghL3oSZ8pVsdn6Xpp1afaUeom48aIO79 RhrEQ0/hp6/xs27oBtm1Djunp/4566RjOPKGJtFkYktABUQQx6v9FjyChkUHJm59RPi/ RA0S6A1bqvs+OCjk/8CYPO2DsHvLAtXf9GDKrni+MODa6bMvKAK/JA7X8U1HHxDtBZQb B8PvRzNVEJ9zD8UqLWWobN26wOPNJ7QOjrh9UCTHzPHCXacYO/AtyLitHz8rhJ7en/TK dasA== MIME-Version: 1.0 X-Received: by 10.60.78.227 with SMTP id e3mr49298128oex.5.1381196950957; Mon, 07 Oct 2013 18:49:10 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Mon, 7 Oct 2013 18:49:10 -0700 (PDT) In-Reply-To: References: <20131007163111.GB1590@reks.swifttest.com> <20131007231734.GY56872@funkthat.com> <20131008002314.GA56872@funkthat.com> <20131008012451.GE56872@funkthat.com> Date: Mon, 7 Oct 2013 21:49:10 -0400 Message-ID: Subject: Re: Committing PEFS to CURRENT From: Outback Dingo To: Gleb Kurtsou Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Gleb Kurtsou , "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:49:12 -0000 On Mon, Oct 7, 2013 at 9:42 PM, Gleb Kurtsou wrote: > On Mon, Oct 7, 2013 at 6:24 PM, John-Mark Gurney wrote: > > > > But will the work get done to clean it up after the freeze is over? What > > happens if it doesn't, will it get removed before 10.1 or will we have > > to live w/ the code? > > I still hope not to get hit by bus any time soon.. > well, i think we all hope you dont get hit by a bus..... ever........ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:49:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E17E84FF for ; Tue, 8 Oct 2013 01:49:38 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B2F932680 for ; Tue, 8 Oct 2013 01:49:38 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r981nXWI034876 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 18:49:36 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <525364A8.6020300@freebsd.org> Date: Tue, 08 Oct 2013 09:49:28 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Steve Kargl Subject: Re: [Heads Up] RCS removed from base References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008002854.GB56872@funkthat.com> <525354C2.8070807@m5p.com> <20131008013350.GB31261@troutmask.apl.washington.edu> In-Reply-To: <20131008013350.GB31261@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: George Mitchell , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:49:38 -0000 On 10/8/13 9:33 AM, Steve Kargl wrote: > On Mon, Oct 07, 2013 at 08:41:38PM -0400, George Mitchell wrote: >> On 10/07/13 20:28, John-Mark Gurney wrote: >>> Julian Elischer wrote this message on Tue, Oct 08, 2013 at 08:01 +0800: >>>> not a big thing but I believe that a lot of poeple use ci/co on /etc >>>> becasue it is "just there" >>> +1 >>> >> Folks, this is just plain a major violation of the Principle of Least >> Amazement. RCS is ideal for keeping track of my configuration files >> in /etc. What do we gain by removing it? > Less GPL code in FreeBSD? not a problem unless you plan in shipping a changed version of it on your product?? From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:49:47 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3DABC606; Tue, 8 Oct 2013 01:49:47 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F06C12688; Tue, 8 Oct 2013 01:49:46 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r981ni9S026110 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 18:49:45 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs is gone? From: Lyndon Nerenberg In-Reply-To: <7C8EB71B-DBA4-49F3-80F4-D579A596A540@orthanc.ca> Date: Mon, 7 Oct 2013 18:49:44 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <4C72FC4E-009A-4C4E-AF18-96EB2A879D0F@orthanc.ca> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <525347DD.5090702@freebsd.org> <1381193888.1130.42.camel@revolution.hippie.lan> <7C8EB71B-DBA4-49F3-80F4-D579A596A540@orthanc.ca> To: Ian Lepore X-Mailer: Apple Mail (2.1510) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:49:47 -0000 On 2013-10-07, at 6:05 PM, Lyndon Nerenberg wrote: > I don't see any discussion as to why the code (CVS, in this case) = *needs* to be removed. My stupidity: I meant RCS, not CVS.= From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:53:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4473775; Tue, 8 Oct 2013 01:53:44 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qe0-x236.google.com (mail-qe0-x236.google.com [IPv6:2607:f8b0:400d:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8269C26D8; Tue, 8 Oct 2013 01:53:44 +0000 (UTC) Received: by mail-qe0-f54.google.com with SMTP id 1so2123787qec.41 for ; Mon, 07 Oct 2013 18:53:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=81xXabWj6nxLY8ahbnTAYVbDud3trX63qpV6tggizQQ=; b=DrXbaHpjtWIiPILbjqu4xkruRyEljGxHV9hrdKgvNGpc+u1ka/XbpTiS19p0kncJAC JHR8OlQ+E5yM/g6ZRxnBx1uPwafZtu9N0LVtBn1HTwqdK6QWOSpFzlC0EI2lOsf03I7+ Iphbz9vCBgiUikNsEIyaRDXJlyi/N3xzIadx2uVakIEhzHb0pjfxYKVE6PEF2NI2uN4K hh6o+o0hOm7f6BsvWm+iCZA9Vc+EJ79jX24CjHX81KWd1cldwkYC/hY306uIsRhMmIbX /gdrXiqs4boLzNVsN7SfsObXIx4AOh9JcLHFCuYYe1XP9ShW3ggXYeeCTzTUyczfgeDL bnEg== X-Received: by 10.49.47.84 with SMTP id b20mr6483993qen.83.1381197223767; Mon, 07 Oct 2013 18:53:43 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Mon, 7 Oct 2013 18:53:03 -0700 (PDT) In-Reply-To: <525364A8.6020300@freebsd.org> References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008002854.GB56872@funkthat.com> <525354C2.8070807@m5p.com> <20131008013350.GB31261@troutmask.apl.washington.edu> <525364A8.6020300@freebsd.org> From: Igor Mozolevsky Date: Tue, 8 Oct 2013 02:53:03 +0100 X-Google-Sender-Auth: pP8i0IOzb2uIhJtewk2Z-joONWc Message-ID: Subject: Re: [Heads Up] RCS removed from base To: Julian Elischer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: George Mitchell , freebsd-current , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:53:45 -0000 On 8 October 2013 02:49, Julian Elischer wrote: > On 10/8/13 9:33 AM, Steve Kargl wrote: > [snip] > > Less GPL code in FreeBSD? >> > not a problem unless you plan in shipping a changed version of it on your > product?? ... and there's already a WITHOUT_RCS switch if the GPLed RCS is *really* a showstopper... -- Igor M. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:58:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5043E8DC; Tue, 8 Oct 2013 01:58:48 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 04872270F; Tue, 8 Oct 2013 01:58:47 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id aq17so18237126iec.27 for ; Mon, 07 Oct 2013 18:58:47 -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=kWH4GdJb+ZdwhDxl2PYsTGVFhxMbroOQ0jREJprwDn0=; b=jMfh3sPzsDHJf1LYgPMsTee1FVm2znvYnTSgqBHHwzRkrMDcvguJbI7WisXdHi8803 +k8Ofy7vVAaQWZ2sEVkz20iYQBz+tabsPx6RQVuDn6m2Kz8W9Dnei2FV2i7X7ru+v5rh 8LNFW84g28zakTkc40WLeX5mTN53V9WmzzGDSkODcrJRAi1JqiKozq0ZUqX9oFzT/l2g eihiaQnGDI+U90pE72YibdoFfr1Vi+miRh7N4XQi8joA1Sg4HL0kpc72bFzZfEYtsKja NGCKoZKUWZ8TL2x9MvCK+gxtz7ImfBAudLdsQ8tklqGRYz5KGQ2W3E0XR0Cpz6UcdeBm Qs/A== MIME-Version: 1.0 X-Received: by 10.50.30.42 with SMTP id p10mr19339045igh.5.1381197527427; Mon, 07 Oct 2013 18:58:47 -0700 (PDT) Received: by 10.65.14.133 with HTTP; Mon, 7 Oct 2013 18:58:47 -0700 (PDT) In-Reply-To: References: Date: Tue, 8 Oct 2013 09:58:47 +0800 Message-ID: Subject: Re: Changes to UART ns8250 From: Ganbold Tsagaankhuu To: Zbigniew Bodek Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" , freebsd-current@freebsd.org, freebsd-embedded@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:58:48 -0000 Zbigniew, On Tue, Oct 8, 2013 at 3:54 AM, Zbigniew Bodek wrote: > Hello. > > I would like to present a patch for ns8250 serial that I would like to > commit in the near future (if there are no objections). > > The patch is fixing newest DesignWare UART with busy detection. > During frequency divisors configuration when UART is busy transferring or > receiving data, line control register manipulation will not take effect. > Therefore, we will not set divisor latch access bit and we will corrupt LCR > instead of configuring divisors. > It is necessary to wait until UART finishes all transfers to proceed with > the configuration. > > This was detected on Armada XP as UART fails on this issue 100/100 > attempts. > The patch was tested by kevlo@ and me and it works on our Armada XP - > based > systems. > > Please send your comment or remarks if there are any. > I'm trying your patch on r254983. Tried on 2 boards (Cubieboard2 (Allwinner A20 SoC - dual Cortex A7) and Radxa Rock (Rockchip RK3188 - Quad Cortex A9)). Both seem to have some sort of DesignWare uart. 1. It works fine on Cubieboard2. Uart dmesg is like: uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 33 on simplebus0 uart0: console (115200,n,8,1) 2. No any printing on screen in case of Radxa Rock. Without your patch uart dmesg is like: uart0: <16650 or compatible> mem 0x20064000-0x200643ff irq 68 on simplebus0 uart0: console (115200,n,8,1) In case of RK3188 SoC, it seems booting FreeBSD kernel seems very fragile, not sure yet what is causing the problem. Even with stock ns8250 some version later than r254983 didn't show/print anything on serial console few days ago. Only thing so far I know is this r254983 (with some patch) works in my case on RK3188 SoC based board. thanks, Ganbold > > Best regards > Zbigniew Bodek > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 01:59:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A2539A4C; Tue, 8 Oct 2013 01:59:41 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4FC8D271F; Tue, 8 Oct 2013 01:59:41 +0000 (UTC) Received: by mail-ob0-f171.google.com with SMTP id uy5so91244obc.16 for ; Mon, 07 Oct 2013 18:59:40 -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=sCN1dktucPhuZRk0AwOwAhbiC3bLANtMZaTW0CRMMdw=; b=X4lXYhm1Q8+Jfc+EpdIJaGfBJSJg6KTgQ7VjnMs62QtXsE8Av8mEnQaE2ChbucQPWX 08iGnhc4Zjvx3vfYZG6K6DqI2safn8Y6VznZwpuxuBWmKIml8e1WpYAPcoV80WYTkuAL 0FKp0MpQ/d/LCbCLr8R7zXf8af2NBJOTye8DcF3/noVMWBOWlZOVHIRMCcj5B/UOQ9Up V621zeBnL0sl8I4CbEXD2e7FFMrWwAANWOgoTPOLiR15jwgcYPkN5CMO8JuohUg9sg7J 8Kcj/y651HtVP5+E7Wy/CJ15u4jTPt2cTsj8yMNVGjT9+JHUIQ+dIgMGyuvRj7zvZo1N 0t8Q== MIME-Version: 1.0 X-Received: by 10.60.42.234 with SMTP id r10mr6417555oel.40.1381197580589; Mon, 07 Oct 2013 18:59:40 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Mon, 7 Oct 2013 18:59:40 -0700 (PDT) In-Reply-To: References: <20131007163111.GB1590@reks.swifttest.com> <20131007231734.GY56872@funkthat.com> <20131008002314.GA56872@funkthat.com> <20131008012451.GE56872@funkthat.com> Date: Mon, 7 Oct 2013 21:59:40 -0400 Message-ID: Subject: Re: Committing PEFS to CURRENT From: Outback Dingo To: Gleb Kurtsou Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Gleb Kurtsou , "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 01:59:41 -0000 On Mon, Oct 7, 2013 at 9:42 PM, Gleb Kurtsou wrote: > On Mon, Oct 7, 2013 at 6:24 PM, John-Mark Gurney wrote: > > > > But will the work get done to clean it up after the freeze is over? What > > happens if it doesn't, will it get removed before 10.1 or will we have > > to live w/ the code? > > I still hope not to get hit by bus any time soon.. > on a side note, i applied the patch to stable/9 out of curiosity and the kernel failed to build the module however i could install fine from ports. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 02:24:33 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A2EA9122; Tue, 8 Oct 2013 02:24:33 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7A3B6287F; Tue, 8 Oct 2013 02:24:33 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r982OWVq094099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 19:24:33 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r982OWS2094098; Mon, 7 Oct 2013 19:24:32 -0700 (PDT) (envelope-from jmg) Date: Mon, 7 Oct 2013 19:24:32 -0700 From: John-Mark Gurney To: Glen Barber Subject: Re: rcs is gone? Message-ID: <20131008022432.GF56872@funkthat.com> Mail-Followup-To: Glen Barber , Igor Mozolevsky , "freebsd-current@freebsd.org" , Andreas Nilsson References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <20131007212925.GC2133@glenbarber.us> <20131008003642.GC56872@funkthat.com> <20131008004253.GG2133@glenbarber.us> <20131008005423.GD56872@funkthat.com> <20131008005950.GA24985@glenbarber.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131008005950.GA24985@glenbarber.us> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 07 Oct 2013 19:24:33 -0700 (PDT) Cc: "freebsd-current@freebsd.org" , Andreas Nilsson , Igor Mozolevsky X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 02:24:33 -0000 Glen Barber wrote this message on Mon, Oct 07, 2013 at 20:59 -0400: > On Mon, Oct 07, 2013 at 05:54:23PM -0700, John-Mark Gurney wrote: > > > No, not really. > > > > > > # mkdir local > > > # svnadmin create ./local > > > # svn import /etc file:///$PWD/local > > > > besides the s/svn/svnlite/ you forgot... It doesn't work... Sure it > > WITH_SVN in src.conf will install svnlite as svn. > > > imports all of my /etc, but doesn't let me commit my changes to rc.conf: > > # svnlite commit rc.conf > > svn: E155007: '/etc/rc.conf' is not a working copy > > Sure it does. > > gjb@nucleus:~/svn % mkdir local > gjb@nucleus:~/svn % svnadmin create ./local > gjb@nucleus:~/svn % cp -rp /usr/local/etc/rc.d fakelocaletc > gjb@nucleus:~/svn % svn import ./fakelocaletc file:///$PWD/local -m "Initial import." > gjb@nucleus:~/svn % svn co --force file:///$PWD/local fakelocaletc This is the step you forgot to include previously... So, it's still a multistep process before you can revision control the files and clearly not simple since we already have two different ways of doing it... I wouldn't have even thought about the permission issue that someone else brought up... > Checked out revision 1. > gjb@nucleus:~/svn % svn stat !$ > svn stat fakelocaletc > gjb@nucleus:~/svn % svn info fakelocaletc > Path: fakelocaletc > Working Copy Root Path: /usr/home/gjb/svn/fakelocaletc > URL: file:///home/gjb/svn/local > Relative URL: ^/ > > > Plus, I was quite reasured that svn isn't smart enough to realize that > > a path might be a file: url relative to the current working directory... > > I don't know what you mean by this. svn didn't bother trying to figure out if the relative path (or even absolute path) has a valid repo.. it just decided, nope, not a URL, I'll quit now, even though it could have been smart... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 02:31:05 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 10DF53A9 for ; Tue, 8 Oct 2013 02:31:05 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B081728D6 for ; Tue, 8 Oct 2013 02:31:04 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r982V2Ic026267 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 7 Oct 2013 19:31:03 -0700 (PDT) (envelope-from lyndon@orthanc.ca) From: Lyndon Nerenberg Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: rcs Message-Id: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> Date: Mon, 7 Oct 2013 19:31:01 -0700 To: "freebsd-current@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 02:31:05 -0000 Okay folks, can we make a call about keeping the RCS tools in the base? The proponents wanting to remove RCS need to speak up and make their = technical case. --lyndon= From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 02:32:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8BA504C6 for ; Tue, 8 Oct 2013 02:32:24 +0000 (UTC) (envelope-from sr@genyosha.net) Received: from ns0.genyosha.net (ns0.genyosha.net [108.86.149.90]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6556C28F1 for ; Tue, 8 Oct 2013 02:32:24 +0000 (UTC) Received: from dragon.genyosha.home (dragon.genyosha.net [108.86.149.92]) by ns0.genyosha.net (8.14.7/8.14.4) with ESMTP id r98244Rs057400 for ; Mon, 7 Oct 2013 19:04:04 -0700 (PDT) (envelope-from sr@genyosha.net) Received: from dragon.genyosha.home (localhost.localdomain [127.0.0.1]) by dragon.genyosha.home (8.14.4/8.14.4) with ESMTP id r9823wnT026729 for ; Mon, 7 Oct 2013 19:03:58 -0700 Received: (from sr@localhost) by dragon.genyosha.home (8.14.4/8.14.4/Submit) id r9823wc5026727 for freebsd-current@freebsd.org; Mon, 7 Oct 2013 19:03:58 -0700 Date: Mon, 7 Oct 2013 19:03:58 -0700 From: Steve Rikli To: freebsd-current@freebsd.org Subject: Re: [Heads Up] RCS removed from base Message-ID: <20131008020358.GA26639@dragon.genyosha.home> References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008013023.GA31261@troutmask.apl.washington.edu> <525360A5.8010908@mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <525360A5.8010908@mu.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (ns0.genyosha.net [108.86.149.90]); Mon, 07 Oct 2013 19:04:04 -0700 (PDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 02:32:24 -0000 On Mon, Oct 07, 2013 at 06:32:21PM -0700, Alfred Perlstein wrote: > On 10/7/13 6:30 PM, Steve Kargl wrote: > >... > >PS: As noted, the code is GPL. There has been an effort > >to remove GPL code from FreeBSD (whether prudent or not). > > That plus the age of the code is good enough reason to ditch it! huzzah! > Plus we can make RCSBSD along with it. Is such a project underway? I.e. an RCS of some kind from FreeBSD? OpenBSD went through this a while ago and use OpenRCS -- is that even remotely appropriate for use in FreeBSD? >From reading most of both thread(s), it seems there's at least some interest in keeping an RCS in base; whether it's the status quo RCS (w/GPL) doesn't seem to be strictly required, as long as whichever RCS is available in base is (mostly?) compatible with status quo RCS. sr. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 03:11:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DD42FD9E; Tue, 8 Oct 2013 03:11:47 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ACCD52B69; Tue, 8 Oct 2013 03:11:47 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id y13so8144568pdi.33 for ; Mon, 07 Oct 2013 20:11:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=MpzW1/hMQChhcxLDecpWyqj/+L22nWQbMOBoGTftpsQ=; b=kj3OypvPB5e+2AYvNS1Sbe5USUwKUf6kd+kP+fXHBAZHnHCtEGzYy8XWPVEEOFmtbQ P4svmhEzZCswERCxXae+RjfQM7622lDlet1+0uIxB/82Q+7r/p3Vf8lmE4KFh2NnoLhG PGJUgTTV1nGQJeUuLPN1CV7lVPkL5VhtxkwpVxbOwUqE4MoTm7XecSDZSu50joAB2tx0 0VCh2Cfbd2/d+pAOccwX53wCyrv9SaWHobKyASuVuOnWFUzsfOl4XwyLEL7ulcj5jTCR ugjLyIt3Kv8S3zuFuixspiKM0k/Lr7iMu4E0qf4k45t6HGrckw+Wk/K3khQTzPkIdusv 4YLA== X-Received: by 10.66.234.131 with SMTP id ue3mr836706pac.35.1381201907350; Mon, 07 Oct 2013 20:11:47 -0700 (PDT) Received: from localhost (c-76-21-78-151.hsd1.ca.comcast.net. [76.21.78.151]) by mx.google.com with ESMTPSA id ye1sm43451554pab.19.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 20:11:46 -0700 (PDT) Date: Mon, 7 Oct 2013 20:12:25 -0700 From: Gleb Kurtsou To: Outback Dingo Subject: Re: Committing PEFS to CURRENT Message-ID: <20131008031225.GA1320@reks> References: <20131007163111.GB1590@reks.swifttest.com> <20131007231734.GY56872@funkthat.com> <20131008002314.GA56872@funkthat.com> <20131008012451.GE56872@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-current@freebsd.org" , "delphij@freebsd.org" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 03:11:47 -0000 On (07/10/2013 21:59), Outback Dingo wrote: > On Mon, Oct 7, 2013 at 9:42 PM, Gleb Kurtsou wrote: > > > On Mon, Oct 7, 2013 at 6:24 PM, John-Mark Gurney wrote: > > > > > > But will the work get done to clean it up after the freeze is over? What > > > happens if it doesn't, will it get removed before 10.1 or will we have > > > to live w/ the code? > > > > I still hope not to get hit by bus any time soon.. > > > > on a side note, i applied the patch to stable/9 out of curiosity and the > kernel failed to build the module > however i could install fine from ports. Correct, there is no support for old kernels in the patch. Port will be maintained and will provide support for older versions in case PEFS finds its way to 10.0. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 03:15:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D8509F03 for ; Tue, 8 Oct 2013 03:15:18 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9E3172B98 for ; Tue, 8 Oct 2013 03:15:18 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r983FHgh031970; Mon, 7 Oct 2013 20:15:17 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r983FHEA031969; Mon, 7 Oct 2013 20:15:17 -0700 (PDT) (envelope-from sgk) Date: Mon, 7 Oct 2013 20:15:17 -0700 From: Steve Kargl To: Lyndon Nerenberg Subject: Re: rcs Message-ID: <20131008031517.GA31864@troutmask.apl.washington.edu> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 03:15:18 -0000 On Mon, Oct 07, 2013 at 07:31:01PM -0700, Lyndon Nerenberg wrote: > Okay folks, can we make a call about keeping the RCS tools in the base? > > The proponents wanting to remove RCS need to speak up and make their > technical case. > I don't care if rcs stays or goes, but ... There is a 15 year gap in ChangeLog at http://git.savannah.gnu.org/cgit/rcs.git/tree/src/ChangeLog?h=p Maybe there was no development for 15 years. However, the 7364 lines in ChangeLog after 2010-02-04 suggests that there may be few bugs to worry about. -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 03:19:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1AF74318 for ; Tue, 8 Oct 2013 03:19:25 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B85762C2D for ; Tue, 8 Oct 2013 03:19:24 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r983JMFF026452 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 7 Oct 2013 20:19:23 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs From: Lyndon Nerenberg In-Reply-To: <20131008031517.GA31864@troutmask.apl.washington.edu> Date: Mon, 7 Oct 2013 20:19:22 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> To: Steve Kargl X-Mailer: Apple Mail (2.1510) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 03:19:25 -0000 On 2013-10-07, at 8:15 PM, Steve Kargl = wrote: > Maybe there was no development for 15 years. However, the 7364 > lines in ChangeLog after 2010-02-04 suggests that there may=20 > be few bugs to worry about.=20 Dear Troll, Demonstrate one.= From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 04:09:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ABCDFAFB; Tue, 8 Oct 2013 04:09:17 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7BE2C2025; Tue, 8 Oct 2013 04:09:17 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r9849CUL035334 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 21:09:14 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52538562.6030703@freebsd.org> Date: Tue, 08 Oct 2013 12:09:06 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [Heads Up] RCS removed from base References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008013023.GA31261@troutmask.apl.washington.edu> <525360A5.8010908@mu.org> <20131008020358.GA26639@dragon.genyosha.home> In-Reply-To: <20131008020358.GA26639@dragon.genyosha.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: core@freebsd.org, Steve Rikli X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 04:09:17 -0000 On 10/8/13 10:03 AM, Steve Rikli wrote: > On Mon, Oct 07, 2013 at 06:32:21PM -0700, Alfred Perlstein wrote: >> On 10/7/13 6:30 PM, Steve Kargl wrote: >>> ... >>> PS: As noted, the code is GPL. There has been an effort >>> to remove GPL code from FreeBSD (whether prudent or not). >> That plus the age of the code is good enough reason to ditch it! huzzah! >> Plus we can make RCSBSD along with it. > Is such a project underway? I.e. an RCS of some kind from FreeBSD? > > OpenBSD went through this a while ago and use OpenRCS -- is that even > remotely appropriate for use in FreeBSD? > > >From reading most of both thread(s), it seems there's at least some > interest in keeping an RCS in base; whether it's the status quo RCS > (w/GPL) doesn't seem to be strictly required, as long as whichever RCS > is available in base is (mostly?) compatible with status quo RCS. the prudent path is to put the original back before 10 and arange to replace it by 11 I'm officially asking core to allow this to stop what I consider a bad POLA problem. it can not be said that there was no pushback against this change. and it was sprung on us with no real warning. > > sr. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 04:34:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ECBADBE; Tue, 8 Oct 2013 04:34:52 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B26462184; Tue, 8 Oct 2013 04:34:52 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id u16so18237364iet.33 for ; Mon, 07 Oct 2013 21:34:52 -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=MNgSn5vSmeuhNMlFUMOzAZGhNNjwvewGzvfHlQJim5I=; b=HVySmJ+OXYN2q27fC7UKAaLvB7LNYps/bsCgNgd5KEk5YIRfaoOvExQGern4BuWUQt vLycSIAOxKx2Is04+HQJM+bdRgTwHjv6+EOkn+82E5iQQid4oRihEK60E90SxaSLRIVw sBsKFsMz0JLS7lNeM1WbRCAbB2T+3Nf/URDS26aQrKOBlX3llFAPZN9Plz8M4aF1jutC cseB8P3nb2pDgGzQED9Z/l++5ll8tGAcXiouwkJRQPhiwlTlIeiATYUotojUz+lpWtW1 3mETB2Ci8y95GOAt2DJDrKQX2dE/rMVlz8ZDSxUyRfPmc/BL3T2KoJx8iN1G7BRXtitV vNEA== MIME-Version: 1.0 X-Received: by 10.50.114.168 with SMTP id jh8mr19945659igb.6.1381206892185; Mon, 07 Oct 2013 21:34:52 -0700 (PDT) Received: by 10.64.8.244 with HTTP; Mon, 7 Oct 2013 21:34:52 -0700 (PDT) In-Reply-To: <525364A8.6020300@freebsd.org> References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008002854.GB56872@funkthat.com> <525354C2.8070807@m5p.com> <20131008013350.GB31261@troutmask.apl.washington.edu> <525364A8.6020300@freebsd.org> Date: Tue, 8 Oct 2013 00:34:52 -0400 Message-ID: Subject: Re: [Heads Up] RCS removed from base From: Mehmet Erol Sanliturk To: Julian Elischer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: George Mitchell , freebsd-current , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 04:34:53 -0000 On Mon, Oct 7, 2013 at 9:49 PM, Julian Elischer wrote: > On 10/8/13 9:33 AM, Steve Kargl wrote: > >> On Mon, Oct 07, 2013 at 08:41:38PM -0400, George Mitchell wrote: >> >>> On 10/07/13 20:28, John-Mark Gurney wrote: >>> >>>> Julian Elischer wrote this message on Tue, Oct 08, 2013 at 08:01 +0800: >>>> >>>>> not a big thing but I believe that a lot of poeple use ci/co on /etc >>>>> becasue it is "just there" >>>>> >>>> +1 >>>> >>>> Folks, this is just plain a major violation of the Principle of Least >>> Amazement. RCS is ideal for keeping track of my configuration files >>> in /etc. What do we gain by removing it? >>> >> Less GPL code in FreeBSD? >> > not a problem unless you plan in shipping a changed version of it on your > product?? > > Most new versions of GPL licensed code are converted to Version 3 GPL . This is blocking FreeBSD if they keep GPL licensed code in base , because commercial companies usingFreeBSD are not able to use FreeBSD any more if the FreeBSD switches to Version 3 GPL . This obstacle is in the base system GCC : It stayed in an older version , and necessitated to switch to Clang/LLVM . Difficulty of such a switch is apparenly known . Therefore cleaning base from GPL licensed code is a vital requirement for further progress WITH RESPECT TO FreeBSD Project structure . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 04:42:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1086F25F for ; Tue, 8 Oct 2013 04:42:22 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DADE421DC for ; Tue, 8 Oct 2013 04:42:21 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r984g7WF035446 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 21:42:18 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52538D19.8000505@freebsd.org> Date: Tue, 08 Oct 2013 12:42:01 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Mehmet Erol Sanliturk Subject: Re: [Heads Up] RCS removed from base References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008002854.GB56872@funkthat.com> <525354C2.8070807@m5p.com> <20131008013350.GB31261@troutmask.apl.washington.edu> <525364A8.6020300@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: George Mitchell , freebsd-current , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 04:42:22 -0000 On 10/8/13 12:34 PM, Mehmet Erol Sanliturk wrote: > > > > On Mon, Oct 7, 2013 at 9:49 PM, Julian Elischer > wrote: > > On 10/8/13 9:33 AM, Steve Kargl wrote: > > On Mon, Oct 07, 2013 at 08:41:38PM -0400, George Mitchell wrote: > > On 10/07/13 20:28, John-Mark Gurney wrote: > > Julian Elischer wrote this message on Tue, Oct 08, > 2013 at 08:01 +0800: > > not a big thing but I believe that a lot of > poeple use ci/co on /etc > becasue it is "just there" > > +1 > > Folks, this is just plain a major violation of the > Principle of Least > Amazement. RCS is ideal for keeping track of my > configuration files > in /etc. What do we gain by removing it? > > Less GPL code in FreeBSD? > > not a problem unless you plan in shipping a changed version of > it on your product?? > > > > Most new versions of GPL licensed code are converted to Version 3 GPL . > > This is blocking FreeBSD if they keep GPL licensed code in base , > because commercial companies usingFreeBSD are not able to use > FreeBSD any more if the FreeBSD switches to Version 3 GPL . > > This obstacle is in the base system GCC : It stayed in an older > version , and necessitated to switch to Clang/LLVM . > > Difficulty of such a switch is apparenly known . > Therefore cleaning base from GPL licensed code is a vital > requirement for further progress WITH RESPECT TO FreeBSD Project > structure . > > Thank you very much . sure but lets keep the one one in the the tree untill there is a replacement ready to commit. ro 10 will have NO RCS which is a POLA. > > > Mehmet Erol Sanliturk > > > > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 04:49:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EB813448 for ; Tue, 8 Oct 2013 04:49:43 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BC6382211 for ; Tue, 8 Oct 2013 04:49:43 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r984ncGF035476 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 21:49:41 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52538EDC.2080001@freebsd.org> Date: Tue, 08 Oct 2013 12:49:32 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Lyndon Nerenberg Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> In-Reply-To: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 04:49:44 -0000 On 10/8/13 11:19 AM, Lyndon Nerenberg wrote: > On 2013-10-07, at 8:15 PM, Steve Kargl wrote: > >> Maybe there was no development for 15 years. However, the 7364 >> lines in ChangeLog after 2010-02-04 suggests that there may >> be few bugs to worry about. I think the fact is that most direct users of RCS use it in a very simple way, and it works just fine for that. with no real need for any updates or any change. > Dear Troll, > > Demonstrate one. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 04:59:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 934006DB; Tue, 8 Oct 2013 04:59:31 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 57E5D2274; Tue, 8 Oct 2013 04:59:31 +0000 (UTC) Received: by mail-ie0-f171.google.com with SMTP id at1so18641302iec.30 for ; Mon, 07 Oct 2013 21:59:30 -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=3emXRmQtP4eogjypNBquXSnQ5KgvrWjTIR8Qek+9d44=; b=SwNrYpkS4sAhSrnaLcIozsmFxXp8Gkk1XX5ds9xV1+a3Y2ViDJwIYdf44zbMxKhnMb 50SbTN6DbQhnJl1DyN4wBgarrSAxVYN148Mt6ejiLsV+E6JvtJppPH/KFwbM/MNxdw1z 6p8Q3Q5QIoZiaqJPJAw2y3RFsKRaYySu6J7wNyKk2svQl+iG8O0udsImmsHSSWfKmPBd 2x1CoVKtZx7k/3M3t3O1pI36FLA4/wKxKjNMFESjp4VJ+hZ0nn2lUfOlT4/H7XhsXjkb WjZ3xK5tySuSJYBuBj5Ei+JF0WCHLprjfnOeHonO7Jm0/lxKyNN6xmumHilvt600docH 0HuQ== MIME-Version: 1.0 X-Received: by 10.42.51.144 with SMTP id e16mr20177669icg.2.1381208370619; Mon, 07 Oct 2013 21:59:30 -0700 (PDT) Received: by 10.64.8.244 with HTTP; Mon, 7 Oct 2013 21:59:30 -0700 (PDT) In-Reply-To: <52538D19.8000505@freebsd.org> References: <20131007150658.GA79233@troutmask.apl.washington.edu> <52534B5E.7010401@freebsd.org> <20131008002854.GB56872@funkthat.com> <525354C2.8070807@m5p.com> <20131008013350.GB31261@troutmask.apl.washington.edu> <525364A8.6020300@freebsd.org> <52538D19.8000505@freebsd.org> Date: Tue, 8 Oct 2013 00:59:30 -0400 Message-ID: Subject: Re: [Heads Up] RCS removed from base From: Mehmet Erol Sanliturk To: Julian Elischer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: George Mitchell , freebsd-current , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 04:59:31 -0000 On Tue, Oct 8, 2013 at 12:42 AM, Julian Elischer wrote: > On 10/8/13 12:34 PM, Mehmet Erol Sanliturk wrote: > > > > > On Mon, Oct 7, 2013 at 9:49 PM, Julian Elischer wrote: > >> On 10/8/13 9:33 AM, Steve Kargl wrote: >> >>> On Mon, Oct 07, 2013 at 08:41:38PM -0400, George Mitchell wrote: >>> >>>> On 10/07/13 20:28, John-Mark Gurney wrote: >>>> >>>>> Julian Elischer wrote this message on Tue, Oct 08, 2013 at 08:01 +0800: >>>>> >>>>>> not a big thing but I believe that a lot of poeple use ci/co on /etc >>>>>> becasue it is "just there" >>>>>> >>>>> +1 >>>>> >>>>> Folks, this is just plain a major violation of the Principle of Least >>>> Amazement. RCS is ideal for keeping track of my configuration files >>>> in /etc. What do we gain by removing it? >>>> >>> Less GPL code in FreeBSD? >>> >> not a problem unless you plan in shipping a changed version of it on your >> product?? >> >> > > Most new versions of GPL licensed code are converted to Version 3 GPL . > > This is blocking FreeBSD if they keep GPL licensed code in base , > because commercial companies usingFreeBSD are not able to use FreeBSD any > more if the FreeBSD switches to Version 3 GPL . > > This obstacle is in the base system GCC : It stayed in an older version > , and necessitated to switch to Clang/LLVM . > > Difficulty of such a switch is apparenly known . > Therefore cleaning base from GPL licensed code is a vital requirement > for further progress WITH RESPECT TO FreeBSD Project structure . > > Thank you very much . > > > sure but lets keep the one one in the the tree untill there is a > replacement ready to commit. ro 10 will have NO RCS which is a POLA. > > If we approach to the removal problem in the following way , I think such removals will be "transparent" for the users : Assume head iso is Head_A.iso , and it is installed as Head_A.system . We removed a feature and generated Head_B.iso , which installs a Head_B.system . Here Head_A.system and Head_B.system are NOT equivalent in functionality and therefore people should take additional steps to make them equivalent . For automated installs and upgrades this may cause much trouble for some users . Instead of doing the above removal in its present form , apply the following steps : In removal patch , include the following steps also : (1) Modify BSDinstall to install the removed part from ports already stored into CD/DVD . ( This will not require Internet or network connection during install and will be applied automatically . ) (2) Modify upgrade program/configurations to upgrade removed parts from ports . ( Since upgrade will use Internet and / or network , this will not be a problem ) . With the above additions , the new Head_B.iso and Head_B.system will be equivalent to the Head_A.iso and Head_A.system without causing any difficulty with the assumption that new functionality is tested sufficiently and is working correctly . In this way , no one will be affected because new system will not break anything . The nonexistence of the above steps is causing such a large controversy . Thank you very much . > > > Mehmet Erol Sanliturk > > > > > > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 05:06:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BB0678D7 for ; Tue, 8 Oct 2013 05:06:53 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 96D2122F1 for ; Tue, 8 Oct 2013 05:06:51 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id DFBB91DBD1 for ; Tue, 8 Oct 2013 05:06:48 +0000 (UTC) Message-ID: <52539300.50305@allanjude.com> Date: Tue, 08 Oct 2013 01:07:12 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> In-Reply-To: <52531295.7090700@allanjude.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 05:06:53 -0000 On 2013-10-07 15:59, Allan Jude wrote: > Devin Teske and I have been working on a big patch to bsdinstall to > implement installing on a ZFS pool. It supports both GPT and MBR, the 4k > sector gnop trick, and optional GELI encryption. We would like to commit > this in time for 10.0-BETA1 so it needs some testing to work out any > obvious bugs before we send it off to re@ to get it committed. > > It includes a single configuration menu that allows you to select all of > the required details, including which drives to use (gets details from > camcontrol, also includes an inspection utility that presents the > detailed output of camcontrol inquiry/identify, and gpart show), what > ZFS RAID level to use (taking in to consideration the selected number of > drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. > > > Additional, it includes some other changes to bsdinstall: > 1. Change the default to the 'non-standard keyboard mapping' prompt to no > 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 > 3. Remove the dialog asking if you wish to enable crash dumps, this > feature has been combined into the regular 'services to enable' dialog > and enabled by default > > > You can browse the patches here: > http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ > > I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, > available compressed (48 MB) or uncompressed (211 MB): > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso > > > We look forward to your feedback > I've generated a new version of the ISO incorporating all of todays changes and moving up to 10.0-ALPHA5 It includes 2 patches from Warren Block, improving the keymap menu and indicating which network interfaces are wireless http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 05:11:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 55DEAAE6 for ; Tue, 8 Oct 2013 05:11:59 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 20BEA2338 for ; Tue, 8 Oct 2013 05:11:58 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r985Bo6V031733 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 00:11:50 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Tue, 8 Oct 2013 00:11:48 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOw+TjPJPIP8ZCyUiSsjBzr2++AA== Date: Tue, 8 Oct 2013 05:11:47 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC415EA@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52539300.50305@allanjude.com> In-Reply-To: <52539300.50305@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-08_02:2013-10-08,2013-10-08,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 05:11:59 -0000 On Oct 7, 2013, at 10:07 PM, Allan Jude wrote: > On 2013-10-07 15:59, Allan Jude wrote: >> Devin Teske and I have been working on a big patch to bsdinstall to >> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >> sector gnop trick, and optional GELI encryption. We would like to commit >> this in time for 10.0-BETA1 so it needs some testing to work out any >> obvious bugs before we send it off to re@ to get it committed. >>=20 >> It includes a single configuration menu that allows you to select all of >> the required details, including which drives to use (gets details from >> camcontrol, also includes an inspection utility that presents the >> detailed output of camcontrol inquiry/identify, and gpart show), what >> ZFS RAID level to use (taking in to consideration the selected number of >> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>=20 >>=20 >> Additional, it includes some other changes to bsdinstall: >> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >> 2. Replace the 3 separate dialogs to configure an ipv4 address with just= 1 >> 3. Remove the dialog asking if you wish to enable crash dumps, this >> feature has been combined into the regular 'services to enable' dialog >> and enabled by default >>=20 >>=20 >> You can browse the patches here: >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>=20 >> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >> available compressed (48 MB) or uncompressed (211 MB): >>=20 >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>=20 >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>=20 >>=20 >> We look forward to your feedback >>=20 >=20 > I've generated a new version of the ISO incorporating all of todays > changes and moving up to 10.0-ALPHA5 > It includes 2 patches from Warren Block, improving the keymap menu and > indicating which network interfaces are wireless >=20 Excellent. However, I have to say... you opened a can of worms by touching keymap. Eventually I plan to rewrite all of the scripts to the same format that zfs= boot is using. I've already started rewriting keymap to the new format. Of cours= e, this opened up another can of worms... the simple things like: DIALOG_OK DIALOG_CANCEL DIALOG_ESC I feel would be much better off in the `dialog.subr' module. So,... I've st= arted peppering their usage everywhere in bsdconfig to make them "proper". That means they will just be transparent from including `dialog.subr'. > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >=20 > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >=20 Excellent, thanks! --=20 Devin P.S. I have to get apache installed on one of my jails to server you the vi= deo ;) I'll have a URL for you tomorrow morning. Trying to work through all the ch= anges in keymap to get it upgraded. _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 05:20:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1F934CCB; Tue, 8 Oct 2013 05:20:55 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D9A29237D; Tue, 8 Oct 2013 05:20:54 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id ar20so18594964iec.32 for ; Mon, 07 Oct 2013 22:20:54 -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=SRBMcTPZap+nYnZSwPuGrxHPg0LQFxU1wvn+Rv/YO3U=; b=a2xb5th3CHJfPWnTNezeZj3qax8dLh8FJiBnDY7kBC76GsgZxpu5cezPRXihF5wdY4 6q3uFzS4O7FWFkJho2HNwyo7uZg2JnnCnNmd7So6f3pID/SSek+HOar3ihOpbfXteIZA 4EejTQGPqTlJNqwT7aIAGBq0gKnn4n/YGtyITlfSbk/g9Sjyd7NhLEe/7QIf/ygEGn4v fCgSTBKXp4Opo31QBCmO/Rkv55c80xL5R1jeW7ZuF0gNgfNWjrMRG3KJsKVEXT+RWP05 va8ZM/XwztGrsseOFxkni01/6VA5w0V8RZYrgv1+02WALxOhQI3MV27isZtW9bYUMZpZ 2+Pw== MIME-Version: 1.0 X-Received: by 10.42.204.4 with SMTP id fk4mr20226071icb.31.1381209654066; Mon, 07 Oct 2013 22:20:54 -0700 (PDT) Received: by 10.64.8.244 with HTTP; Mon, 7 Oct 2013 22:20:53 -0700 (PDT) In-Reply-To: <20131007225444.GA31518@night.db.net> References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> <20131007225444.GA31518@night.db.net> Date: Tue, 8 Oct 2013 01:20:53 -0400 Message-ID: Subject: Re: rcs is gone? From: Mehmet Erol Sanliturk To: Diane Bruce Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: David Chisnall , "freebsd-current@freebsd.org" , Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 05:20:55 -0000 On Mon, Oct 7, 2013 at 6:54 PM, Diane Bruce wrote: > On Mon, Oct 07, 2013 at 03:45:23PM -0700, Lyndon Nerenberg wrote: > > > > On 2013-10-07, at 2:53 PM, David Chisnall wrote: > > > > > Or do you really only run the base OS and no other software on your > systems, without any of your own code or any customisation? > > > > We install from the base release ISO images burned on DVDs. > > > > We are physically air-gapped from the internet, none of the "end users" > of the system have access to USB ports, and there are no electronic devices > allowed into the development shop. > > > > We have a scheme for bringing in software from /usr/ports, but it is > painful. And those ports can't necessarily walk on to all the systems in > the shop. (I don't make the rules. Suffice to say the company is very > paranoid about their code getting out into the wild.) > > > > Having RCS in the base system is very useful. We use it to track > changes to bits of /etc on the machines where we don't do wholesale > customizations. (Those ones get git, but they also get an install of > /usr/ports with a fully populated /usr/ports/distfiles.) > > > > So if nuking RCS is a case of "I don't use it," ... we do. > > > > Hey we could imoort SCCS instead. > > http://sccs.berlios.de > > > - Diane > -- > - db@FreeBSD.org db@db.net http://www.db.net/~db > _______________________________________________ > > This also contains GPL parts as specified in COPYING within ftp://ftp.berlios.de/pub/schily/schily-2013-07-29.tar.bz2 Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 05:48:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0050B54E for ; Tue, 8 Oct 2013 05:48:02 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id B009224DC for ; Tue, 8 Oct 2013 05:48:02 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 63F6E1DC18 for ; Tue, 8 Oct 2013 05:48:01 +0000 (UTC) Message-ID: <52539C9F.9000400@allanjude.com> Date: Tue, 08 Oct 2013 01:48:15 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52539300.50305@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC415EA@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC415EA@LTCFISWMSGMB21.FNFIS.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 05:48:03 -0000 On 2013-10-08 01:11, Teske, Devin wrote: > On Oct 7, 2013, at 10:07 PM, Allan Jude wrote: > >> On 2013-10-07 15:59, Allan Jude wrote: >>> Devin Teske and I have been working on a big patch to bsdinstall to >>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>> sector gnop trick, and optional GELI encryption. We would like to commit >>> this in time for 10.0-BETA1 so it needs some testing to work out any >>> obvious bugs before we send it off to re@ to get it committed. >>> >>> It includes a single configuration menu that allows you to select all of >>> the required details, including which drives to use (gets details from >>> camcontrol, also includes an inspection utility that presents the >>> detailed output of camcontrol inquiry/identify, and gpart show), what >>> ZFS RAID level to use (taking in to consideration the selected number of >>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>> >>> >>> Additional, it includes some other changes to bsdinstall: >>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>> feature has been combined into the regular 'services to enable' dialog >>> and enabled by default >>> >>> >>> You can browse the patches here: >>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>> >>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>> available compressed (48 MB) or uncompressed (211 MB): >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>> >>> >>> We look forward to your feedback >>> >> I've generated a new version of the ISO incorporating all of todays >> changes and moving up to 10.0-ALPHA5 >> It includes 2 patches from Warren Block, improving the keymap menu and >> indicating which network interfaces are wireless >> > Excellent. > > However, I have to say... you opened a can of worms by touching keymap. > > Eventually I plan to rewrite all of the scripts to the same format that zfsboot > is using. I've already started rewriting keymap to the new format. Of course, > this opened up another can of worms... the simple things like: > > DIALOG_OK > DIALOG_CANCEL > DIALOG_ESC Yeah, after having them, I felt a bit naked not having all of those 'constants' defined. Originally, all I had done was add --defaultno to the dialog command, but Warren's patch makes a lot of sense, allow the user to 'try' the new keymap before trying to do the rest of the install based on it. > I feel would be much better off in the `dialog.subr' module. So,... I've started > peppering their usage everywhere in bsdconfig to make them "proper". > > That means they will just be transparent from including `dialog.subr'. > This is definately something that I think is a good idea, but my focus is on improving the usability and functionality of the installer in time for 10.0. Unifying everything to the bsdconfig style is slightly lower priority. Admittedly, the `bsdconfig networking` stuff is quite nice >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >> >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >> > Excellent, thanks! -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 06:30:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 49777E63 for ; Tue, 8 Oct 2013 06:30:01 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id 15BAF26A0 for ; Tue, 8 Oct 2013 06:30:00 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:54284] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 3F/9A-16944-166A3525; Tue, 08 Oct 2013 06:29:53 +0000 Date: Tue, 08 Oct 2013 06:29:53 +0000 Message-ID: <3F.9A.16944.166A3525@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Unable to installworld after successful buildworld and buildkernel X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 06:30:01 -0000 >From $SRCDIR/UPDATING To cross-install current onto a separate partition -------------------------------------------------- # In this approach we use a separate partition to hold # current's root, 'usr', and 'var' directories. A partition # holding "/", "/usr" and "/var" should be about 2GB in # size. make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installworld DESTDIR=${CURRENT_ROOT} make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd This part seems not to have changed so far from RELENG_9 to HEAD. I failed on "make installworld DESTDIR=/BETA1 |& tee installworld.log" ERROR: Required unbound user is missing, see /usr/src/UPDATING How am I supposed to have an unbound user on a partition where there is no existing FreeBSD installation? Like the job market, where one needs to have two or more years experience, but how to get that first job? I tried mergemaster -p -m /BETA1/usr/src -D /BETA1 on thin air, managed to get a master.passwd that included unbound user, but make installworld DESTDIR=/BETA1 failed immediately for lack of unbound user it couldn't find. I also tried make distribution DESTDIR=/BETA1 (and distributeworld too), no joy: Target directory, either /BETA1/etc or /BETA1/etc/atf, does not exist. There is a bug in $SRCDIR/UPDATING in the part about cross-installing current onto a separate partition. I even tried copying /etc directory from USB stick to /BETA1/etc before running mergemaster, but that also failed. But this was no barrier when I built and installed FreeBSD 9-stable i386 on a USB stick, mounted as /compat/i386. >From https://wiki.freebsd.org/i386-Wine # cd /usr/src # make buildworld TARGET=i386 # make installworld TARGET=i386 DESTDIR=/compat/i386 # make distribution TARGET=i386 DESTDIR=/compat/i386 # mkdir /compat/i386/usr/ports # mount -t devfs devfs /compat/i386/dev # mount -t nullfs /usr/ports /compat/i386/usr/ports but instead of the latter part, after "make distribution ..." I made buildkernel and installkernel, and booted from the USB stick, used ports directory on hard drive. That worked, but wouldn't work for FreeBSD-current now due to unbound and /etc problems? How does one install FreeBSD, building from source, on a partition with no OS installed? Directories on this partition include /netbsd-HEAD, /pkgsrc, and /usr/src, /usr/ports and /usr/doc. I use a USB-stick installation of FreeBSD 9.2 prerelease for building FreeBSD-current, but due to a bug in re driver, could not connect to Internet with Realtek 8111E Ethernet on MSI Z77 MPOWER motherboard. NetBSD-current (6.99.19 updated to 6.99.23) was able to access this Ethernet, so I checked out, by cvs, NetBSD-current source and pkgsrc tree (current, not quarterly), updated NetBSD and packages, and successfully built subversion. Then I used this svn to checkout FreeBSD-current source tree. I believe FreeBSD installation would not touch directories /netbsd-HEAD and /pkgsrc. Tom From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 07:26:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 82CE4E8F for ; Tue, 8 Oct 2013 07:26:02 +0000 (UTC) (envelope-from kolyasir@gmail.com) Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5EC6629C5 for ; Tue, 8 Oct 2013 07:26:02 +0000 (UTC) Received: by mail-pd0-f173.google.com with SMTP id p10so8265031pdj.4 for ; Tue, 08 Oct 2013 00:26:01 -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=wyzKXx+S4AsStoM9M1ytGOuOMVHPpZ3KDca2nLqDJkg=; b=hOsw0j0qSAU0aRFc5KhN/Z2XyisLPd/R5XXJHN/EOx3QbyPwtthqJdJsgUbkhRTzGU hCFHTA551cInuu+ksjb9Nr/nQTjtyyIyai+aeZvJF8hN5+DNjNrpsGEwVkmVUs06gC3H Ee/KW8OlNXHPwVD+ZOd1y+Da7iibTU4gr9LLb8iU850bL/bT8a+Zbys+N+XY5Y/xZ6Yn 7pjEFgxBre0xh1ybAh7+Yy6Unl/s5M6+CG/Zw8i31YWMGfrq8GmEEJi0Hh72JsAH0FCN eLXaoRlJ+9lSPL1r4ocxjwWFOYkIAKJuDntLJc7fz1Fx+VYP8uDOeAHQ5+nm67lcskks loqQ== MIME-Version: 1.0 X-Received: by 10.68.200.200 with SMTP id ju8mr225302pbc.172.1381217161452; Tue, 08 Oct 2013 00:26:01 -0700 (PDT) Received: by 10.70.38.199 with HTTP; Tue, 8 Oct 2013 00:26:01 -0700 (PDT) Date: Tue, 8 Oct 2013 12:26:01 +0500 Message-ID: Subject: brigding between two interfaces From: Yasir hussan To: Current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 07:26:02 -0000 Hi, i am little bit weak in networking concept, i have two network interfaces usb0 and eth0, eth0 is connected to a static ip, which works perfectly fine, now i want that usb0 should be able to access static ip which is connected to eth0, can anyone guide me proper solutionwith command for this which i can test thanks From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 07:45:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BD420444 for ; Tue, 8 Oct 2013 07:45:29 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8A6482B15 for ; Tue, 8 Oct 2013 07:45:29 +0000 (UTC) Received: by mail-oa0-f47.google.com with SMTP id i1so7179926oag.20 for ; Tue, 08 Oct 2013 00:45:28 -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=Q16IOqUY1jb9fEvx5zlBKB7wMbygDwvvvY0Rjht5iPE=; b=ztOJ/C0zjg4Zm1Tj8TLClw/0lzLyR6MFnVYzdyrYcJEz8MBUVpegdJ4P6Oe8rKgrtz JujvCRaXtmmDwgC2rDSNhpw9r4DHBxc6QYE5rTELiENvWJzwfgE3DYiL251JbCMZ9GpC jx8Gwp6n7AS2pw+RX5YFFDz4G5K/jDNl/88EYcKJizwfzZcPbX4RuHbo5KRyzWoK8zkT fBZOS8C9sgcug5d+6GbgtZmSUSivzHq3qoi2bHrLrcQyNq/cpTEHsH2Bl8xJN4/OXLe1 9h7ZHFSyCrIm9PwMrjhhhmBfNsGNR3FljkldRNxqRTknFC5RJCJLaoZbcDwDeV2Zsfp+ rlWw== MIME-Version: 1.0 X-Received: by 10.182.22.5 with SMTP id z5mr128124obe.42.1381218328833; Tue, 08 Oct 2013 00:45:28 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Tue, 8 Oct 2013 00:45:28 -0700 (PDT) Date: Tue, 8 Oct 2013 03:45:28 -0400 Message-ID: Subject: Running i386 CURRENT on an AMD64 platform:: CLang related From: Joe Nosay To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 07:45:29 -0000 I've ran into compiling problems with some ports. World and kernel have not yet been rebuilt. 10.x is a pre-APLHA release. Before I attempt to rebuild any of the system, has anyone else had any problems related to building i386 on AMD64? From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 07:55:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EE30F7C9 for ; Tue, 8 Oct 2013 07:55:19 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward9l.mail.yandex.net (forward9l.mail.yandex.net [IPv6:2a02:6b8:0:1819::9]) by mx1.freebsd.org (Postfix) with ESMTP id B1E4D2BCB for ; Tue, 8 Oct 2013 07:55:19 +0000 (UTC) Received: from smtp13.mail.yandex.net (smtp13.mail.yandex.net [95.108.130.68]) by forward9l.mail.yandex.net (Yandex) with ESMTP id 4959BE60F32; Tue, 8 Oct 2013 11:55:17 +0400 (MSK) Received: from smtp13.mail.yandex.net (localhost [127.0.0.1]) by smtp13.mail.yandex.net (Yandex) with ESMTP id DB1BAE40917; Tue, 8 Oct 2013 11:55:16 +0400 (MSK) Received: from 46.38.32.182.tel.ru (46.38.32.182.tel.ru [46.38.32.182]) by smtp13.mail.yandex.net (nwsmtp/Yandex) with ESMTP id ofzODxLLvk-tGFePQhN; Tue, 8 Oct 2013 11:55:16 +0400 Message-ID: <5253BA63.4080102@passap.ru> Date: Tue, 08 Oct 2013 11:55:15 +0400 From: Boris Samorodov Organization: =?UTF-8?B?0JfQkNCeICLQktCQ0KDQoiI=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130806 Thunderbird/17.0.7 MIME-Version: 1.0 To: Joe Nosay Subject: Re: Running i386 CURRENT on an AMD64 platform:: CLang related References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 07:55:20 -0000 08.10.2013 11:45, Joe Nosay пишет: > I've ran into compiling problems with some ports. World and kernel have not > yet been rebuilt. 10.x is a pre-APLHA release. Please, show diagnostic messages (of failing ports). > Before I attempt to rebuild any of the system, has anyone else had any > problems related to building i386 on AMD64? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 08:01:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 86FECA21; Tue, 8 Oct 2013 08:01:04 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) Received: from mail.made4.biz (unknown [IPv6:2001:41d0:1:7018::1:3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B5AB2C48; Tue, 8 Oct 2013 08:01:04 +0000 (UTC) Received: from [2001:1b48:10b:cafe:225:64ff:febe:589f] (helo=viking.yzserv.com) by mail.made4.biz with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VTSE1-0001iI-WF; Tue, 08 Oct 2013 10:01:02 +0200 Message-ID: <5253BBB3.3040302@FreeBSD.org> Date: Tue, 08 Oct 2013 10:00:51 +0200 From: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: sbruno@freebsd.org, "freebsd-current@freebsd.org" Subject: Re: [patch] Re: drm2/radeon dfixed_trunc() warnings References: <1381095549.1586.7.camel@localhost> <1381172676.3091.0.camel@localhost> In-Reply-To: <1381172676.3091.0.camel@localhost> X-Enigmail-Version: 1.5.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x1ipNtLQLGRRcmH6wabjkab9ME0JGRmKi" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 08:01:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --x1ipNtLQLGRRcmH6wabjkab9ME0JGRmKi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 07.10.2013 21:04, Sean Bruno wrote: > Proposed patch to eliminate this check. If I understand the macro > correctly, there's no way for these checks to ever do anything as bit > shifting an unsigned will simply clear out the value. So, the check fo= r > <0 is completely bogus? Hello! I think you're right. I saw Clang reporting those warnings. Coverity has many more. I didn't want to fix them for now, to ease future merges from Linux. The plan is to submit patches to upstream at some point. Thanks for the patch! I should prepare a branch to store that kind of fix= es. --=20 Jean-S=E9bastien P=E9dron --x1ipNtLQLGRRcmH6wabjkab9ME0JGRmKi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJTu70ACgkQa+xGJsFYOlNkHACgz4Pjn22okp+9A+Foa9lRonzI UfAAn1sc/ENt6smUhtzdGhbv5r8wYJIG =lvmN -----END PGP SIGNATURE----- --x1ipNtLQLGRRcmH6wabjkab9ME0JGRmKi-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 08:11:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 24F73DA1 for ; Tue, 8 Oct 2013 08:11:19 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward3l.mail.yandex.net (forward3l.mail.yandex.net [IPv6:2a02:6b8:0:1819::3]) by mx1.freebsd.org (Postfix) with ESMTP id DB7092D21 for ; Tue, 8 Oct 2013 08:11:18 +0000 (UTC) Received: from smtp2h.mail.yandex.net (smtp2h.mail.yandex.net [84.201.187.145]) by forward3l.mail.yandex.net (Yandex) with ESMTP id 77DAF1500F0C; Tue, 8 Oct 2013 12:11:17 +0400 (MSK) Received: from smtp2h.mail.yandex.net (localhost [127.0.0.1]) by smtp2h.mail.yandex.net (Yandex) with ESMTP id 0BFD01702281; Tue, 8 Oct 2013 12:11:16 +0400 (MSK) Received: from 46.38.32.182.tel.ru (46.38.32.182.tel.ru [46.38.32.182]) by smtp2h.mail.yandex.net (nwsmtp/Yandex) with ESMTP id ifRqdQ7ZOD-BGB8LNeo; Tue, 8 Oct 2013 12:11:16 +0400 Message-ID: <5253BE24.5030806@passap.ru> Date: Tue, 08 Oct 2013 12:11:16 +0400 From: Boris Samorodov Organization: =?UTF-8?B?0JfQkNCeICLQktCQ0KDQoiI=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130806 Thunderbird/17.0.7 MIME-Version: 1.0 To: Joe Nosay Subject: Re: Running i386 CURRENT on an AMD64 platform:: CLang related References: <5253BA63.4080102@passap.ru> In-Reply-To: <5253BA63.4080102@passap.ru> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 08:11:19 -0000 08.10.2013 11:55, Boris Samorodov пишет: > 08.10.2013 11:45, Joe Nosay пишет: >> I've ran into compiling problems with some ports. World and kernel have not >> yet been rebuilt. 10.x is a pre-APLHA release. > > Please, show diagnostic messages (of failing ports). OK, I've seen you have posted them to freebsd-ports@. >> Before I attempt to rebuild any of the system, has anyone else had any >> problems related to building i386 on AMD64? Anyway, I'd say that it's a good idea to update your system since there were many changes you may be interested in. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 09:21:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C8620C05 for ; Tue, 8 Oct 2013 09:21:21 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 93406216E for ; Tue, 8 Oct 2013 09:21:21 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa01.fnfis.com (8.14.5/8.14.5) with ESMTP id r989LFpq007885 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 04:21:15 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Tue, 8 Oct 2013 04:21:14 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOw+TjPJPIP8ZCyUiSsjBzr2++AA== Date: Tue, 8 Oct 2013 09:21:13 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4243D@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52539300.50305@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC415EA@LTCFISWMSGMB21.FNFIS.com> <52539C9F.9000400@allanjude.com> In-Reply-To: <52539C9F.9000400@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-08_05:2013-10-08,2013-10-08,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 09:21:21 -0000 On Oct 7, 2013, at 10:48 PM, Allan Jude wrote: > On 2013-10-08 01:11, Teske, Devin wrote: >> On Oct 7, 2013, at 10:07 PM, Allan Jude wrote: >>=20 >>> On 2013-10-07 15:59, Allan Jude wrote: >>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>> implement installing on a ZFS pool. It supports both GPT and MBR, the = 4k >>>> sector gnop trick, and optional GELI encryption. We would like to comm= it >>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>> obvious bugs before we send it off to re@ to get it committed. >>>>=20 >>>> It includes a single configuration menu that allows you to select all = of >>>> the required details, including which drives to use (gets details from >>>> camcontrol, also includes an inspection utility that presents the >>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>> ZFS RAID level to use (taking in to consideration the selected number = of >>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>=20 >>>>=20 >>>> Additional, it includes some other changes to bsdinstall: >>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to= no >>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with ju= st 1 >>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>> feature has been combined into the regular 'services to enable' dialog >>>> and enabled by default >>>>=20 >>>>=20 >>>> You can browse the patches here: >>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>=20 >>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>> available compressed (48 MB) or uncompressed (211 MB): >>>>=20 >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>=20 >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>=20 >>>>=20 >>>> We look forward to your feedback >>>>=20 >>> I've generated a new version of the ISO incorporating all of todays >>> changes and moving up to 10.0-ALPHA5 >>> It includes 2 patches from Warren Block, improving the keymap menu and >>> indicating which network interfaces are wireless >>>=20 >> Excellent. >>=20 >> However, I have to say... you opened a can of worms by touching keymap. >>=20 >> Eventually I plan to rewrite all of the scripts to the same format that = zfsboot >> is using. I've already started rewriting keymap to the new format. Of co= urse, >> this opened up another can of worms... the simple things like: >>=20 >> DIALOG_OK >> DIALOG_CANCEL >> DIALOG_ESC >=20 > Yeah, after having them, I felt a bit naked not having all of those > 'constants' defined. >=20 The constants are now where they belong... `dialog.subr' I also went through bsdconfig(8) with a fine-tooth comb and made use of the new "constants" everywhere. I think it's a definite improvement. > Originally, all I had done was add --defaultno to the dialog command, > but Warren's patch makes a lot of sense, allow the user to 'try' the new > keymap before trying to do the rest of the install based on it. >=20 I rewrote warren's code into the stateful design and cleaned it up. >> I feel would be much better off in the `dialog.subr' module. So,... I've= started >> peppering their usage everywhere in bsdconfig to make them "proper". >>=20 >> That means they will just be transparent from including `dialog.subr'. >>=20 >=20 > This is definately something that I think is a good idea, but my focus > is on improving the usability and functionality of the installer in time > for 10.0. Unifying everything to the bsdconfig style is slightly lower > priority. Admittedly, the `bsdconfig networking` stuff is quite nice >=20 *nods* I took a look at the bsdinstall networking stuff, and I wanted to run away. Let's push that into the future. It wasn't too hard to get those global exit codes deployed, so I did that, but like you say... I agree we should minimize "extra work" that will be eventually slated for a future release. --=20 Devin >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>=20 >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>=20 >> Excellent, thanks! >=20 >=20 > --=20 > Allan Jude >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 11:03:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 689B08DE for ; Tue, 8 Oct 2013 11:03:57 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 28FA428A7 for ; Tue, 8 Oct 2013 11:03:57 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VTV51-0004kV-F7 for freebsd-current@freebsd.org; Tue, 08 Oct 2013 13:03:55 +0200 Received: from 79-139-19-75.prenet.pl ([79.139.19.75]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 08 Oct 2013 13:03:55 +0200 Received: from jb.1234abcd by 79-139-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 08 Oct 2013 13:03:55 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: jb Subject: Re: brigding between two interfaces Date: Tue, 8 Oct 2013 11:03:36 +0000 (UTC) Lines: 16 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 79.139.19.75 (Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 11:03:57 -0000 Yasir hussan gmail.com> writes: > > Hi, > > i am little bit weak in networking concept, i have two network interfaces > usb0 and eth0, eth0 is connected to a static ip, which works perfectly > fine, now i want that usb0 should be able to access static ip which is > connected to eth0, http://www.freebsd.org/doc/handbook/network-bridging.html jb From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 13:30:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 69909563 for ; Tue, 8 Oct 2013 13:30:01 +0000 (UTC) (envelope-from vsityz@gmail.com) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EB2132395 for ; Tue, 8 Oct 2013 13:30:00 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id ev20so6939829lab.11 for ; Tue, 08 Oct 2013 06:29:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=; b=PM0SklPfnw2MhF5RPWnoHhcUsUmC7oUHXwkZ44YJcU4tuayOIySpf8bbuJ2Rb39Lop Hg6+QQlhkhPEbX4Vq0n4kLyA1mRGRoDtoYGgupAoGROGyhYakQjnaKQqA3P8vhUQt5SA xpUJUM9u1bHJPKcqkeTpFkCv4Wu0Elk9uhJjanVSRoe73L9pyLKrvd1BXxoTqWSg2jSA 3j6WNtzDYXCH+ilSkadzgtcd1wyikG23DPIzBZDLy+/W9fbtLLCv17wcuE3zm+7GfJoo xxHv8/j8o7pyuEG+6a7oCxRT4M9sKhvTjfibC/h1sl4SgcBcXiJmwDkDVfolgrT4eAVX 0H9A== X-Received: by 10.152.203.233 with SMTP id kt9mr1346801lac.29.1381238998954; Tue, 08 Oct 2013 06:29:58 -0700 (PDT) Received: from scorpion.kiev.ua ([78.111.187.210]) by mx.google.com with ESMTPSA id w10sm22606607lbv.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 06:29:56 -0700 (PDT) Message-ID: <525408CC.7000409@gmail.com> Date: Tue, 08 Oct 2013 16:29:48 +0300 From: Alexander Panyushkin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: test Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 13:30:01 -0000 test From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 14:09:05 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D93196D; Tue, 8 Oct 2013 14:09:05 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id C3D1825F0; Tue, 8 Oct 2013 14:09:05 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 1FD701A3D4F; Tue, 8 Oct 2013 07:09:05 -0700 (PDT) Message-ID: <52541202.3010707@mu.org> Date: Tue, 08 Oct 2013 07:09:06 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Julian Elischer Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> In-Reply-To: <52538EDC.2080001@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , Lyndon Nerenberg , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 14:09:05 -0000 On 10/7/13 9:49 PM, Julian Elischer wrote: > On 10/8/13 11:19 AM, Lyndon Nerenberg wrote: >> On 2013-10-07, at 8:15 PM, Steve Kargl >> wrote: >> >>> Maybe there was no development for 15 years. However, the 7364 >>> lines in ChangeLog after 2010-02-04 suggests that there may >>> be few bugs to worry about. > > I think the fact is that most direct users of RCS use it in a very > simple way, and > it works just fine for that. with no real need for any updates or any > change. With all due respect Julian, The more we discuss this more this really points to the problem that FreeBSD appears to be a challenge to install packages into such that a package moving out of base is such a big deal. Can we fix that instead? I mean, this change should really not be a big deal, but yet it is and this speaks to the core of FreeBSD utility. So again, is there a way to make it so adding RCS after install is not a big deal at all? -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 14:15:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8BFFC3AD for ; Tue, 8 Oct 2013 14:15:12 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C62F82650 for ; Tue, 8 Oct 2013 14:15:11 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.7/8.14.7) with ESMTP id r98EF122069181; Tue, 8 Oct 2013 09:15:01 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.7/8.14.7/Submit) id r98EF13W069180; Tue, 8 Oct 2013 09:15:01 -0500 (CDT) (envelope-from brooks) Date: Tue, 8 Oct 2013 09:15:01 -0500 From: Brooks Davis To: Thomas Mueller Subject: Re: Unable to installworld after successful buildworld and buildkernel Message-ID: <20131008141501.GA69028@lor.one-eyed-alien.net> References: <3F.9A.16944.166A3525@cdptpa-oedge02> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: <3F.9A.16944.166A3525@cdptpa-oedge02> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 14:15:12 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 08, 2013 at 06:29:53AM +0000, Thomas Mueller wrote: > From $SRCDIR/UPDATING >=20 > To cross-install current onto a separate partition > -------------------------------------------------- > # In this approach we use a separate partition to hold > # current's root, 'usr', and 'var' directories. A partition > # holding "/", "/usr" and "/var" should be about 2GB in > # size. >=20 > > > make buildworld > make buildkernel KERNCONF=3DYOUR_KERNEL_HERE > > > make installworld DESTDIR=3D${CURRENT_ROOT} > make distribution DESTDIR=3D${CURRENT_ROOT} # if newfs'd > make installkernel KERNCONF=3DYOUR_KERNEL_HERE DESTDIR=3D${CURREN= T_ROOT} > cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if n= ewfs'd > > > > > >=20 > This part seems not to have changed so far from RELENG_9 to HEAD. >=20 > I failed on "make installworld DESTDIR=3D/BETA1 |& tee installworld.log" >=20 > ERROR: Required unbound user is missing, see /usr/src/UPDATING >=20 > How am I supposed to have an unbound user on a partition where there is n= o existing FreeBSD installation? >=20 > Like the job market, where one needs to have two or more years experience= , but how to get that first job? >=20 > I tried > mergemaster -p -m /BETA1/usr/src -D /BETA1 > on thin air, managed to get a master.passwd that included unbound user, b= ut=20 > make installworld DESTDIR=3D/BETA1=20 > failed immediately for lack of unbound user it couldn't find. >=20 > I also tried=20 > make distribution DESTDIR=3D/BETA1 > (and distributeworld too), no joy: > Target directory, either /BETA1/etc or /BETA1/etc/atf, does not exist. >=20 > There is a bug in $SRCDIR/UPDATING in the part about cross-installing cur= rent onto a separate partition. >=20 > I even tried copying /etc directory from USB stick to /BETA1/etc before r= unning mergemaster, but that also failed. >=20 > But this was no barrier when I built and installed FreeBSD 9-stable i386 = on a USB stick, mounted as /compat/i386. >=20 > From https://wiki.freebsd.org/i386-Wine >=20 > # cd /usr/src > # make buildworld TARGET=3Di386 > # make installworld TARGET=3Di386 DESTDIR=3D/compat/i386 > # make distribution TARGET=3Di386 DESTDIR=3D/compat/i386 > # mkdir /compat/i386/usr/ports > # mount -t devfs devfs /compat/i386/dev > # mount -t nullfs /usr/ports /compat/i386/usr/ports >=20 > but instead of the latter part, after "make distribution ..." > I made buildkernel and installkernel, and booted from the USB stick, used= ports directory on hard drive. >=20 > That worked, but wouldn't work for FreeBSD-current now due to unbound and= /etc problems? >=20 > How does one install FreeBSD, building from source, on a partition with n= o OS installed? To cross install FreeBSD on a system without the required users/groups you must either install them on the base system so that install and mtree can use them or use the -DDB_FROM_SRC option when running the installworld/installkernel/distribution targets. -- Brooks --jI8keyz6grp/JLjh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFSVBNkXY6L6fI4GtQRAiXSAKCTzdgT3s1gdyTPywCDj9brCfCVLgCfa3zH ztszWsEhQ9ooUhiW67RCLow= =Prr5 -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 14:17:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0ED6F56C for ; Tue, 8 Oct 2013 14:17:24 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from server.i805.com.br (mailhost.i805.com.br [72.52.97.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EF1982679 for ; Tue, 8 Oct 2013 14:17:23 +0000 (UTC) Received: from i805.com.br (localhost [127.0.0.1]) by server.i805.com.br (8.14.6/8.14.5) with ESMTP id r98EHG5X086222 for ; Tue, 8 Oct 2013 11:17:16 -0300 (BRT) (envelope-from rizzo@i805.com.br) From: "Nilton Jose Rizzo" To: freebsd-current@freebsd.org Subject: Virtual box require LIBCXX Date: Tue, 8 Oct 2013 11:17:16 -0300 Message-Id: <20131008141346.M55461@i805.com.br> X-Mailer: OpenWebMail 3.00_beta4 20121104 671 X-OriginatingIP: 179.218.87.141 (rizzo) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on server.i805.com.br X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 14:17:24 -0000 I finish install a virtual box from ports and it's build ok, look ===> Installing ldconfig configuration file ===> Registering installation for virtualbox-ose-4.2.18_1 Installing virtualbox-ose-4.2.18_1... done ===> SECURITY REPORT: This port has installed the following binaries which execute with increased privileges. /usr/local/lib/virtualbox/VirtualBox /usr/local/lib/virtualbox/VBoxSDL /usr/local/lib/virtualbox/VBoxHeadless /usr/local/lib/virtualbox/VBoxAutostart /usr/local/lib/virtualbox/VBoxBFE /usr/local/lib/virtualbox/VBoxTestOGL /usr/local/lib/virtualbox/VBoxNetAdpCtl /usr/local/lib/virtualbox/VBoxNetDHCP This port has installed the following files which may act as network servers and may therefore pose a remote security risk to the system. /usr/local/lib/virtualbox/vboxwebsrv /usr/local/lib/virtualbox/VBoxXPCOM.so /usr/local/lib/virtualbox/VBoxRT.so /usr/local/lib/virtualbox/VBoxDD.so /usr/local/lib/virtualbox/VBoxOGLhostcrutil.so (USES POSSIBLY INSECURE FUNCTIONS: tmpnam) /usr/local/lib/virtualbox/webtest This port has installed the following startup scripts which may cause these network services to be started at boot time. /usr/local/etc/rc.d/vboxheadless /usr/local/etc/rc.d/vboxwebsrv If there are vulnerabilities in these programs there may be a security risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. For more information, and contact details about the security status of this software, see the following webpage: http://www.virtualbox.org/ ===> Cleaning for dev86-0.16.18 ===> Cleaning for kBuild-0.1.9998 ===> Cleaning for gtar-1.27 ===> Cleaning for gsoap-2.8.10_1 ===> Cleaning for libvncserver-0.9.9_5 ===> Cleaning for virtualbox-ose-kmod-4.2.18 ===> Cleaning for virtualbox-ose-4.2.18_1 root@valfenda:/usr/ports/emulators/virtualbox-ose # kldload vboxdrv root@valfenda:/usr/ports/emulators/virtualbox-ose # but whern I run it, the I got this error message: rizzo@valfenda:~/src/Doutorado/visao/testes % VirtualBox VirtualBox: Error -610 in supR3HardenedMainInitRuntime! VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by /usr/local/lib/virtualbox/VBoxRT.so not found VirtualBox: Tip! It may help to reinstall VirtualBox. rizzo@valfenda:~/src/Doutorado/visao/testes % I update my system and port to last nigth root@valfenda:/home2/rizzo # cd /usr root@valfenda:/usr # svn info src Caminho: src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Raiz do RepositĂłrio: svn://svn.freebsd.org/base UUID do repositĂłrio: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f RevisĂŁo: 256108 Tipo de NĂł: diretĂłrio Agendado: normal Autor da Última Mudança: glebius RevisĂŁo da Última Mudança: 256108 Data da Última Mudança: 2013-10-07 09:07:40 -0300 (Seg, 07 Out 2013) root@valfenda:/usr # svn info ports Caminho: ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Raiz do RepositĂłrio: svn://svn.freebsd.org/ports UUID do repositĂłrio: 35697150-7ecd-e111-bb59-0022644237b5 RevisĂŁo: 329758 Tipo de NĂł: diretĂłrio Agendado: normal Autor da Última Mudança: ak RevisĂŁo da Última Mudança: 329758 Data da Última Mudança: 2013-10-08 02:47:27 -0300 (Ter, 08 Out 2013) root@valfenda:/usr # uname -a FreeBSD valfenda 10.0-ALPHA5 FreeBSD 10.0-ALPHA5 #3 r256108: Tue Oct 8 02:55:04 BRT 2013 rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA amd64 root@valfenda:/usr # What's do I wrong? TIA, Rizzo From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:11:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6D6BF6AF for ; Tue, 8 Oct 2013 15:11:28 +0000 (UTC) (envelope-from sthaug@nethelp.no) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.freebsd.org (Postfix) with SMTP id A78CB2967 for ; Tue, 8 Oct 2013 15:11:27 +0000 (UTC) Received: (qmail 39123 invoked from network); 8 Oct 2013 15:04:44 -0000 Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 8 Oct 2013 15:04:44 -0000 Date: Tue, 08 Oct 2013 17:04:44 +0200 (CEST) Message-Id: <20131008.170444.74714516.sthaug@nethelp.no> To: bright@mu.org Subject: Re: rcs From: sthaug@nethelp.no In-Reply-To: <52541202.3010707@mu.org> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: lyndon@orthanc.ca, freebsd-current@freebsd.org, sgk@troutmask.apl.washington.edu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:11:28 -0000 > > I think the fact is that most direct users of RCS use it in a very > > simple way, and > > it works just fine for that. with no real need for any updates or any > > change. > > With all due respect Julian, The more we discuss this more this really > points to the problem that FreeBSD appears to be a challenge to install > packages into such that a package moving out of base is such a big deal. > > Can we fix that instead? > > I mean, this change should really not be a big deal, but yet it is and > this speaks to the core of FreeBSD utility. Not commenting on RCS here, but on the concept of moving packages out of the base: - For some of us, the attraction of FreeBSD is that it is a tightly integrated system, and the base contains enough useful functionality that we don't *have* to add a lot of packages. - Each package that is moved out of the base system means less useful functionality in the base system - and for me: Less reason to use FreeBSD instead of Linux. I absolutely see the problem of maintaining out-of-date packages in the base system, and the desirability of making the base system less reliant on GPL. I'm mostly troubled by the fact that there seems to be a rather strong tendency the last few years of having steadily less functionality in the base system - and I'm not at all convinced that the right balance has been found here. This discussion is not new, and I don't expect to convince any new persons... Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:15:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 090D580E for ; Tue, 8 Oct 2013 15:15:44 +0000 (UTC) (envelope-from josiaslg@bsd.com.br) Received: from mail-ye0-x22c.google.com (mail-ye0-x22c.google.com [IPv6:2607:f8b0:4002:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BBC9A2998 for ; Tue, 8 Oct 2013 15:15:43 +0000 (UTC) Received: by mail-ye0-f172.google.com with SMTP id r1so1093591yen.31 for ; Tue, 08 Oct 2013 08:15:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=date:from:to:message-id:subject:mime-version:content-type; bh=ctJVUmrkXIbgKTr0Ye2AX3DHH+MFqTxp3E2v/nVhbc4=; b=cAWgYY9UAjX4LjZVN36l+RwQitNJ2TF803v+VNbN2CijfyrLitrzXOgK7YVP4tcc7c ocl0Nqtag31jJAQsQtmH/lh5mZPQQLsbZNe84CfD5trM1Xc1AZeaRoDrMQ7W0jt+Iwtc /OBkVMN8Nt+fhG7CVSRa5Dq+VOsMS0QhXy/UI= 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:message-id:subject:mime-version :content-type; bh=ctJVUmrkXIbgKTr0Ye2AX3DHH+MFqTxp3E2v/nVhbc4=; b=XZw2sUSGlsZ7E65Bc2CGoI+VEBZkMNvmyroYzJPtjTTnj/jMWoMF7lOVEjh+qX6Wim HIVaIQr6R6yOGMVZW7E3IJXR8tpX42kr38Qzeawx7RaqfAaWd8LhEfDH2YeUAqO+nVXa jT8J4oYS3M1u+5hzEkgiRl2+33nRnJVaoPykzkaxdLofgU7Xvmw3oJK+PNWCDj4uj0HN 5FC0AetX5VIAJFTmauMdr/sSnBPTle2go5zPy1Wg83/xtjL8XrDR6V9nIDKO2mU60A4Y on50PfLTs3ul3JoC2D4Vs30e6qlx0zls+NQsDHqtf4wr1c/K37OYy2FQ2SF0YK7clDZo p+0A== X-Gm-Message-State: ALoCoQn/ZUxkn2M2H/pyj/FgghLThscQM/DswCpWKLjr0hHHFBEHR0TAx/3kAm+x2Why5CatlyW+ X-Received: by 10.236.176.67 with SMTP id a43mr1632556yhm.68.1381243512977; Tue, 08 Oct 2013 07:45:12 -0700 (PDT) Received: from MacBook-Pro-de-Josias.local ([177.159.155.80]) by mx.google.com with ESMTPSA id 9sm52558370yhd.19.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 07:45:12 -0700 (PDT) Date: Tue, 8 Oct 2013 11:45:08 -0300 From: "Josias L.G" To: freebsd-current@freebsd.org Message-ID: Subject: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem X-Mailer: Airmail Beta (205) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:15:44 -0000 Problem with Citrix Xen 6.2 and install from ISO.=C2=A0The =22solution=22= was remove cd-rom drive from virtual machine. Not possible now with xen = default in GENERIC kernel. Message error:=C2=A0 run=5Finterrupt=5Fdriven=5Fhooks - still waiting after 300 seconds for xe= nbusb=5Fnop=5Fconfighook=5Fcb panic: run=5Finterrupt=5Fdriven=5Fconfig=5Fhooks: waited too long --=C2=A0 Best Regards, Josias L.G From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:20:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5EB86B61 for ; Tue, 8 Oct 2013 15:20:26 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4C5752A19 for ; Tue, 8 Oct 2013 15:20:26 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 75B691A3D52 for ; Tue, 8 Oct 2013 08:20:20 -0700 (PDT) Message-ID: <525422B6.9040906@mu.org> Date: Tue, 08 Oct 2013 08:20:22 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> In-Reply-To: <20131008.170444.74714516.sthaug@nethelp.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:20:26 -0000 On 10/8/13 8:04 AM, sthaug@nethelp.no wrote: >>> I think the fact is that most direct users of RCS use it in a very >>> simple way, and >>> it works just fine for that. with no real need for any updates or any >>> change. >> With all due respect Julian, The more we discuss this more this really >> points to the problem that FreeBSD appears to be a challenge to install >> packages into such that a package moving out of base is such a big deal. >> >> Can we fix that instead? >> >> I mean, this change should really not be a big deal, but yet it is and >> this speaks to the core of FreeBSD utility. > Not commenting on RCS here, but on the concept of moving packages out > of the base: > > - For some of us, the attraction of FreeBSD is that it is a tightly > integrated system, and the base contains enough useful functionality > that we don't *have* to add a lot of packages. > > - Each package that is moved out of the base system means less useful > functionality in the base system - and for me: Less reason to use > FreeBSD instead of Linux. > > I absolutely see the problem of maintaining out-of-date packages in > the base system, and the desirability of making the base system less > reliant on GPL. I'm mostly troubled by the fact that there seems to > be a rather strong tendency the last few years of having steadily > less functionality in the base system - and I'm not at all convinced > that the right balance has been found here. > > This discussion is not new, and I don't expect to convince any new > persons... > > I'm sure other devs will disagree, but with ~15 years of FreeBSD experience and ~13 years as a dev, my very strong opinion is that this tightly coupled system is actually a boat anchor sinking us. Just because no one else does it a certain way, does not mean that a unique way of doing something is correct and/or sustainable. Maybe in 1995, 1999, or 2005 even, but not today. Especially in the context of add-on tools like rcs. What we need to discuss is lowering the bar to making custom installs. I personally find that installing FreeBSD is useless until I install "screen, zsh, vim-lite, git" why is that so manual for me? Why can't I just register a package set somewhere so that all I have to type in is "alfred.perlstein.devel" into a box during the installer and I get all my packages by default? -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:26:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 60784E1A for ; Tue, 8 Oct 2013 15:26:02 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 222DB2A7D for ; Tue, 8 Oct 2013 15:26:02 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id n4so6180152qcx.27 for ; Tue, 08 Oct 2013 08:26:01 -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=PUoMZHM8zcaNyKRsPHDKf0p8mVuMEV6b9h5bjEl9yeI=; b=AvpMc+2jDduQS7LJHEDgWMKZ+9aisrJT1lS6Tc9fd4Bsz9dS8foZNQh7crLACtKDoV U8Q7+ewT9arafmuD4T2OprX2/Rck/bhigvHu3IZ3b6umRX00X7/Yr9/n+T82Q0/GisXA YBolg+U/PQvG34aAMUYDTGa6FQsRBHtQSwnUzx8TrNRPCi6K68cuoB3hnOYUs5FhgYo0 gguTeeEvkXO+ZR9JGkecRfXf720vW0LEYSR24cPusX/gQMB/YJVL5txAmXK0rd0mth3G sMQAqTd/SKI/CJvAAsT9E7XQAqxcPjJ87iB6NMygnL2c5YcJcrLKeAKFgZr5sbfW21gY 2uYw== MIME-Version: 1.0 X-Received: by 10.224.73.200 with SMTP id r8mr4621068qaj.72.1381245961343; Tue, 08 Oct 2013 08:26:01 -0700 (PDT) Received: by 10.49.29.234 with HTTP; Tue, 8 Oct 2013 08:26:01 -0700 (PDT) In-Reply-To: <525422B6.9040906@mu.org> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> Date: Tue, 8 Oct 2013 17:26:01 +0200 Message-ID: Subject: Re: rcs From: Andreas Nilsson To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Current FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:26:02 -0000 On Tue, Oct 8, 2013 at 5:20 PM, Alfred Perlstein wrote: > On 10/8/13 8:04 AM, sthaug@nethelp.no wrote: > >> I think the fact is that most direct users of RCS use it in a very >>>> simple way, and >>>> it works just fine for that. with no real need for any updates or any >>>> change. >>>> >>> With all due respect Julian, The more we discuss this more this really >>> points to the problem that FreeBSD appears to be a challenge to install >>> packages into such that a package moving out of base is such a big deal. >>> >>> Can we fix that instead? >>> >>> I mean, this change should really not be a big deal, but yet it is and >>> this speaks to the core of FreeBSD utility. >>> >> Not commenting on RCS here, but on the concept of moving packages out >> of the base: >> >> - For some of us, the attraction of FreeBSD is that it is a tightly >> integrated system, and the base contains enough useful functionality >> that we don't *have* to add a lot of packages. >> >> - Each package that is moved out of the base system means less useful >> functionality in the base system - and for me: Less reason to use >> FreeBSD instead of Linux. >> >> I absolutely see the problem of maintaining out-of-date packages in >> the base system, and the desirability of making the base system less >> reliant on GPL. I'm mostly troubled by the fact that there seems to >> be a rather strong tendency the last few years of having steadily >> less functionality in the base system - and I'm not at all convinced >> that the right balance has been found here. >> >> This discussion is not new, and I don't expect to convince any new >> persons... >> >> >> I'm sure other devs will disagree, but with ~15 years of FreeBSD > experience and ~13 years as a dev, my very strong opinion is that this > tightly coupled system is actually a boat anchor sinking us. > > Just because no one else does it a certain way, does not mean that a > unique way of doing something is correct and/or sustainable. Maybe in > 1995, 1999, or 2005 even, but not today. Especially in the context of > add-on tools like rcs. > > What we need to discuss is lowering the bar to making custom installs. > > I personally find that installing FreeBSD is useless until I install > "screen, zsh, vim-lite, git" why is that so manual for me? Why can't I > just register a package set somewhere so that all I have to type in is > "alfred.perlstein.devel" into a box during the installer and I get all my > packages by default? > > -- > Alfred Perlstein > > You technically can. Make your own "meta-port" which depends on the stuff you want. Build package-set with for example poudriere, ship those packages on your install-media. Done. /Andreas > > ______________________________**_________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@** > freebsd.org " > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:33:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 45DD128A for ; Tue, 8 Oct 2013 15:33:42 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 2FA592B16 for ; Tue, 8 Oct 2013 15:33:42 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id D3C131A3D57; Tue, 8 Oct 2013 08:33:41 -0700 (PDT) Message-ID: <525425D8.5040404@mu.org> Date: Tue, 08 Oct 2013 08:33:44 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Andreas Nilsson Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Current FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:33:42 -0000 On 10/8/13 8:26 AM, Andreas Nilsson wrote: > > > > On Tue, Oct 8, 2013 at 5:20 PM, Alfred Perlstein > wrote: > > On 10/8/13 8:04 AM, sthaug@nethelp.no > wrote: > > I think the fact is that most direct users of RCS use > it in a very > simple way, and > it works just fine for that. with no real need for > any updates or any > change. > > With all due respect Julian, The more we discuss this more > this really > points to the problem that FreeBSD appears to be a > challenge to install > packages into such that a package moving out of base is > such a big deal. > > Can we fix that instead? > > I mean, this change should really not be a big deal, but > yet it is and > this speaks to the core of FreeBSD utility. > > Not commenting on RCS here, but on the concept of moving > packages out > of the base: > > - For some of us, the attraction of FreeBSD is that it is a > tightly > integrated system, and the base contains enough useful > functionality > that we don't *have* to add a lot of packages. > > - Each package that is moved out of the base system means less > useful > functionality in the base system - and for me: Less reason to use > FreeBSD instead of Linux. > > I absolutely see the problem of maintaining out-of-date > packages in > the base system, and the desirability of making the base > system less > reliant on GPL. I'm mostly troubled by the fact that there > seems to > be a rather strong tendency the last few years of having steadily > less functionality in the base system - and I'm not at all > convinced > that the right balance has been found here. > > This discussion is not new, and I don't expect to convince any new > persons... > > > I'm sure other devs will disagree, but with ~15 years of FreeBSD > experience and ~13 years as a dev, my very strong opinion is that > this tightly coupled system is actually a boat anchor sinking us. > > Just because no one else does it a certain way, does not mean that > a unique way of doing something is correct and/or sustainable. > Maybe in 1995, 1999, or 2005 even, but not today. Especially in > the context of add-on tools like rcs. > > What we need to discuss is lowering the bar to making custom installs. > > I personally find that installing FreeBSD is useless until I > install "screen, zsh, vim-lite, git" why is that so manual for me? > Why can't I just register a package set somewhere so that all I > have to type in is "alfred.perlstein.devel" into a box during the > installer and I get all my packages by default? > > -- > Alfred Perlstein > > You technically can. Make your own "meta-port" which depends on the > stuff you want. Build package-set with for example poudriere, ship > those packages on your install-media. Done. > Oh I have done that in the past, but why the editing, the makefiles, the etc, etc, etc. Why isn't there a customize.freebsd.org where I just hit a few checkboxes, save and then hit download? -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:34:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4B5333A7 for ; Tue, 8 Oct 2013 15:34:57 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1EE062B2C for ; Tue, 8 Oct 2013 15:34:56 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 71B2021BE4 for ; Tue, 8 Oct 2013 11:34:52 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Tue, 08 Oct 2013 11:34:53 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=M3qGq5nG4zaRGbq2hPFPhxQ/gto=; b=doM fuYWHoH1I0MOnXB6PKgdJcumZSY3hwYl5HuRErapVHMYh7dDyc/I6GHr1wz3aBJ4 tZi7ULETr6cNBR1I48T4DMzTqGbYbBkDqTrVVhaanX5T/KaeLLgHyNQiHsi7FHLK KvHztLH80aT/nFLH3qBvcsFQxJDRo2CeMYdOeKWQ= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 2241C117241; Tue, 8 Oct 2013 11:34:52 -0400 (EDT) Message-Id: <1381246492.15452.31494021.44A7C64D@webmail.messagingengine.com> X-Sasl-Enc: yWgFbDq9KBUbZfBsTa28sa1TPs6jrWWA6x44lVHG9ISG 1381246492 From: Mark Felder To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 In-Reply-To: <525425D8.5040404@mu.org> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> <525425D8.5040404@mu.org> Subject: Re: rcs Date: Tue, 08 Oct 2013 10:34:52 -0500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:34:57 -0000 On Tue, Oct 8, 2013, at 10:33, Alfred Perlstein wrote: > > Oh I have done that in the past, but why the editing, the makefiles, the > etc, etc, etc. Why isn't there a customize.freebsd.org where I just hit > a few checkboxes, save and then hit download? > A metaport builder web service would be really slick, actually... From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:36:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C3DC34E4 for ; Tue, 8 Oct 2013 15:36:41 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::3c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 97F012B4D for ; Tue, 8 Oct 2013 15:36:41 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.5/8.14.5) with ESMTP id r98Fadf8013044 for ; Tue, 8 Oct 2013 11:36:39 -0400 (EDT) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at mail.pix.net Message-ID: <52542687.7000100@pix.net> Date: Tue, 08 Oct 2013 11:36:39 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [Heads Up] RCS removed from base References: <52534B5E.7010401@freebsd.org> In-Reply-To: <52534B5E.7010401@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:36:41 -0000 On 10/8/13, Julian Elischer wrote: > On 10/7/13 11:06 PM, Steve Kargl wrote: >> On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: >>> Hey all, >>> >>> RCS was removed from the base system in r256095. If you still want to >>> use RCS please install either devel/rcs or devel/rcs57. If not, be >>> sure to check out the alternatives (pun stolen and intended). >>> >> Perhaps, a note in src/UPDATING is appropriate? >> > ok so what is this, the secret cabal to make FreeBSD useless? > I'm ccing core as I believe this was not discussed enough in public > (in fact not discussed AT ALL in any forum I am watching) > and I officially request a backout of the removal of what I consider > to be core functionality. > > My usual way of doing things is on install to ci EVERYTHING in /etc > to get a snapsot right the way back to install. > > now I have to change things in /etc (and other places) BEFORE I can > check them in. > (i.e. get networking up and ports installed) > not a big thing but I believe that a lot of poeple use ci/co on /etc > becasue it is "just there" > +1 for keeping a RCS in base. I too use to maintain a bunch of files in /etc - I have for years and years. I don't particularly want the GPL'd version - I'd be happiest with the OpenRCS version (BSD-licensed) from OpenBSD. -Kurt From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:39:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A530A623 for ; Tue, 8 Oct 2013 15:39:51 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-ea0-x230.google.com (mail-ea0-x230.google.com [IPv6:2a00:1450:4013:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3DBAD2B6E for ; Tue, 8 Oct 2013 15:39:51 +0000 (UTC) Received: by mail-ea0-f176.google.com with SMTP id q16so4078748ead.21 for ; Tue, 08 Oct 2013 08:39:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/v/CdltLZnC3JQw3OhSRL66WpiWJDBEy13eoRxXMdyQ=; b=EaMI8gNuf5JlF3saVPrEnG5x7GYk5p6rN8yIMpF/8tuZ9XX95ukno/e2J80ttRUZKj JI8snhkAc57CIHWk4KPw7ZUsRMjl7kxzhULE1WdihM/cqCZ80Tq/MlHnc5svreAsUHlW NuLAlaq18Wj7ZeBVvPjHwObV3qTW4nEP1s6eXRBGliM3tuSP8kCDzCsUd5ykb3urr953 2ggkpHG89FvZNIAiu/0mZlH9ardsP5bxMvXDGpQY+0+r+6DIdZUmgc3ZM3PnTmA/CWB/ 2J2FJR4zazmX/dBiaBblz1mEa75j+MLbov7z/BUpgVfpPZgaNq40aIrvOW+b4nU+y5Ey gakQ== X-Received: by 10.15.98.9 with SMTP id bi9mr3216014eeb.67.1381246789567; Tue, 08 Oct 2013 08:39:49 -0700 (PDT) Received: from [10.10.50.70] (37.10.166.178.rev.vodafone.pt. [178.166.10.37]) by mx.google.com with ESMTPSA id a1sm77275938eem.1.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 08:39:48 -0700 (PDT) Message-ID: <5254273E.5030105@gmail.com> Date: Tue, 08 Oct 2013 16:39:42 +0100 From: "Mike C." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [Heads Up] RCS removed from base References: <52534B5E.7010401@freebsd.org> <52542687.7000100@pix.net> In-Reply-To: <52542687.7000100@pix.net> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:39:51 -0000 On 10/08/13 16:36, Kurt Lidl wrote: > On 10/8/13, Julian Elischer wrote: >> On 10/7/13 11:06 PM, Steve Kargl wrote: >>> On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: >>>> Hey all, >>>> >>>> RCS was removed from the base system in r256095. If you still want to >>>> use RCS please install either devel/rcs or devel/rcs57. If not, be >>>> sure to check out the alternatives (pun stolen and intended). >>>> >>> Perhaps, a note in src/UPDATING is appropriate? >>> >> ok so what is this, the secret cabal to make FreeBSD useless? >> I'm ccing core as I believe this was not discussed enough in public >> (in fact not discussed AT ALL in any forum I am watching) >> and I officially request a backout of the removal of what I consider >> to be core functionality. >> >> My usual way of doing things is on install to ci EVERYTHING in /etc >> to get a snapsot right the way back to install. >> >> now I have to change things in /etc (and other places) BEFORE I can >> check them in. >> (i.e. get networking up and ports installed) >> not a big thing but I believe that a lot of poeple use ci/co on /etc >> becasue it is "just there" >> > > +1 for keeping a RCS in base. I too use to maintain a bunch of > files in /etc - I have for years and years. I don't particularly > want the GPL'd version - I'd be happiest with the OpenRCS version > (BSD-licensed) from OpenBSD. +1 for OpenRCS > > -Kurt > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:40:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C0B6C7DC; Tue, 8 Oct 2013 15:40:25 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1FF1A2BAC; Tue, 8 Oct 2013 15:40:24 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id ea20so7221864lab.27 for ; Tue, 08 Oct 2013 08:40: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; bh=vHvYcGwcndsHAlnf3NpAukEPx2dPzQyHAsPHqOcrNBo=; b=HZf3bGh3C/vdzv2OZ6RIDyQC4q+8fe64EVC7fkZ9sAAhNjxDLl2XUbiIyKIJ+Mhyxg RbGTlRHCT7V9yqednFnJrXOOkGIk9mRy7xhVa78t+TavPONGKDWChtDhW4jnz1FxzPM6 a8oVSTeZatoNImTwsKLEXUvs/NVOKRrfIgKU/eG0t2VNoMQQgN5X5hOVsH58vnhvNTky KL39bBZ7m+dczUUAx+ZDB/UNUOGJt8euWE5HpANp3UWF7YEhU2dpOIffiaFcM58dsEXU lyenMy70vW03IMx/D1L+e/zKQCTU0d4Cw5x/VRKb1PF51zgemDK/TOw1wOQXKdaAnfYs pkhQ== MIME-Version: 1.0 X-Received: by 10.152.28.7 with SMTP id x7mr1871960lag.26.1381246823126; Tue, 08 Oct 2013 08:40:23 -0700 (PDT) Received: by 10.112.155.137 with HTTP; Tue, 8 Oct 2013 08:40:23 -0700 (PDT) In-Reply-To: <52541202.3010707@mu.org> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> Date: Tue, 8 Oct 2013 17:40:23 +0200 Message-ID: Subject: Re: rcs From: Daniel Nebdal To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 Cc: Lyndon Nerenberg , "freebsd-current@freebsd.org" , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:40:25 -0000 On Tue, Oct 8, 2013 at 4:09 PM, Alfred Perlstein wrote: > On 10/7/13 9:49 PM, Julian Elischer wrote: >> >> On 10/8/13 11:19 AM, Lyndon Nerenberg wrote: >>> >>> On 2013-10-07, at 8:15 PM, Steve Kargl >>> wrote: >>> >>>> Maybe there was no development for 15 years. However, the 7364 >>>> lines in ChangeLog after 2010-02-04 suggests that there may >>>> be few bugs to worry about. >> >> >> I think the fact is that most direct users of RCS use it in a very simple >> way, and >> it works just fine for that. with no real need for any updates or any >> change. > > > With all due respect Julian, The more we discuss this more this really > points to the problem that FreeBSD appears to be a challenge to install > packages into such that a package moving out of base is such a big deal. > > Can we fix that instead? > > I mean, this change should really not be a big deal, but yet it is and this > speaks to the core of FreeBSD utility. > > So again, is there a way to make it so adding RCS after install is not a big > deal at all? > > > -- > Alfred Perlstein > If they get the package repositories back up - which I assume will happen before any official releases from 10 - it should just be "pkg install rcs". As challenges go, that doesn't seem too bad? That said, an online meta package builder *is* a nice idea, and seems perfectly doable. -- Daniel Nebdal From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:49:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F1A38DE6 for ; Tue, 8 Oct 2013 15:49:22 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CC0472C20 for ; Tue, 8 Oct 2013 15:49:22 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id xb4so8796744pbc.36 for ; Tue, 08 Oct 2013 08:49:21 -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=MFe9RmSqGXbPpBzUJN4ANcioPn/De7eDJ4+rvCO5pYk=; b=Q5zt7XGlHPy7bokklsDCAuMD3Rcq7Naxh5y2Dctev4D9OmHVXaz4EoQFY9wToqJ0FA sdWxMuP6BACq4MVMI9EsMyCtL/3aw+EwY9WjNj0h9b/vdLNnJSHSeY9RrOf+KQub4eEi cXOxEvDPXwjeeKYvfjdb4zDMB/W/Yd/lGM2gjhyNTHsjWRYFt/nt0XD5BYAD5QRUm1e3 RsCqsU70TIYRJ+qd1wapBsFA+ieyrfyZDVJMy22k76787wXTZPDR3y5u+vtl4rJGPE6/ SatkoPcPneFfyjCJk4jW+DB2EM5hc3/ysFr42mvJOv0dnKiNZxepI/Hdxaf6P+ydLdnm YlXQ== X-Gm-Message-State: ALoCoQlKM0K0B+guy2qfQw7TsCo8FHXvDFbVUkuoTovleE5zb8FQSaJ9R35fnVeQS+GPST4V0gjO MIME-Version: 1.0 X-Received: by 10.68.108.3 with SMTP id hg3mr2703702pbb.91.1381247361826; Tue, 08 Oct 2013 08:49:21 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Tue, 8 Oct 2013 08:49:21 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Tue, 8 Oct 2013 08:49:21 -0700 (PDT) In-Reply-To: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> Date: Tue, 8 Oct 2013 08:49:21 -0700 Message-ID: Subject: Re: rcs From: Jos Backus To: Lyndon Nerenberg Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:49:23 -0000 On Oct 7, 2013 7:31 PM, "Lyndon Nerenberg" wrote: > > Okay folks, can we make a call about keeping the RCS tools in the base? > > The proponents wanting to remove RCS need to speak up and make their technical case. Perhaps slightly off-topic, but how about we move into the 21st century and import the 2-clause BSD-licensed Fossil? http://www.fossil-scm.org/ Not RCS, I know, but vastly more useful. Jos From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:49:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 242FAF65; Tue, 8 Oct 2013 15:49:56 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ECA0C2C31; Tue, 8 Oct 2013 15:49:55 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0269A211E0; Tue, 8 Oct 2013 11:49:55 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Tue, 08 Oct 2013 11:49:54 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=eS2yOJ9L5RnqfI31LG/kIHs7hVI=; b=EED iOwoakqJoaY69Ik76MLHrerTkQkAlkMtrsMKostwap/G3ttm74Y2OhMWGyeSNmFA UkuCNBP7GKiuJRDtCL1jTKdMoxN8oecXgMX+fQXDcwJlpw2wRsk9NKaYPnJNX48+ v2YVuawKdlxhEbLU+agYsVjhIPMZPaernPBquwhc= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id CEDAD1172D2; Tue, 8 Oct 2013 11:49:54 -0400 (EDT) Message-Id: <1381247394.22461.31501241.11EE316E@webmail.messagingengine.com> X-Sasl-Enc: A1cWUKc+G4l6yyWKXvw6hSl8xzHH/f/ulb5INljV1Pjf 1381247394 From: Mark Felder To: freebsd-current@freebsd.org, freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 In-Reply-To: References: Subject: Re: FreeBSD Alpha5 amd64 - Citrix Xen 6.2 problem Date: Tue, 08 Oct 2013 10:49:54 -0500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:49:56 -0000 On Tue, Oct 8, 2013, at 9:45, Josias L.G wrote: > Problem with Citrix Xen 6.2 and install from ISO.=A0The "solution" was > remove cd-rom drive from virtual machine. Not possible now with xen > default in GENERIC kernel. > Message error:=A0 > run_interrupt_driven_hooks - still waiting after 300 seconds for > xenbusb_nop_confighook_cb > panic: run_interrupt_driven_config_hooks: waited too long >=20 I was going to test this soon... but you're right -- you probably can't install FreeBSD 10 from ISO on Citrix XenServer because of this bug. Can someone working on the xen bits test and maybe find a workaround? From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:54:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6981727B for ; Tue, 8 Oct 2013 15:54:42 +0000 (UTC) (envelope-from jonathan.robert.anderson@gmail.com) Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2C40A2CA0 for ; Tue, 8 Oct 2013 15:54:42 +0000 (UTC) Received: by mail-vb0-f50.google.com with SMTP id x14so4532771vbb.9 for ; Tue, 08 Oct 2013 08:54:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:cc:content-type; bh=KKhuVNwthQ8V/OIqBwqY7ZR2xF3V4N4cRXXzgh+Bfxw=; b=iacamuySkL7iTrWhCVX7/eA7WkySHkdWJoigv2CdbyCpSh43uJ+NoQnZYdWDGp60um UxKPug5rGZnXgemZMGuCOoRawupMLJVFMnMurUWdTnflHNGjHyg7tuvs6XUO1AZqz71F VVYR7ipX45k1OO8PlfC5voKMaN8Xuf2MD30D7u73xc6gX3ols4focbPa6989U1yUC6QQ vRsi/NKl0Kw/IXkh20WNnidUEXehjqKgbVL+NlZkBFiFK/DxyvbMbtFW8MJlLGSQ7ws1 XffDq9wchIGQVrlRtXqAvCrca3R4lm4On3OrnAAeafVpwAJaxu6y06SixopEA4neXpqo ZzcA== X-Received: by 10.221.27.73 with SMTP id rp9mr1549521vcb.29.1381247681240; Tue, 08 Oct 2013 08:54:41 -0700 (PDT) MIME-Version: 1.0 Sender: jonathan.robert.anderson@gmail.com Received: by 10.52.180.201 with HTTP; Tue, 8 Oct 2013 08:54:21 -0700 (PDT) From: Jonathan Anderson Date: Tue, 8 Oct 2013 16:54:21 +0100 X-Google-Sender-Auth: YLDOlLye1xmZg8kXOQLCx5QAeOY Message-ID: Subject: The Base System (was: rcs) To: sthaug@nethelp.no Content-Type: text/plain; charset=UTF-8 Cc: bright@mu.org, lyndon@orthanc.ca, sgk@troutmask.apl.washington.edu, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:54:42 -0000 On 8 October 2013 16:04, wrote: > - For some of us, the attraction of FreeBSD is that it is a tightly > integrated system, and the base contains enough useful functionality > that we don't *have* to add a lot of packages. > > - Each package that is moved out of the base system means less useful > functionality in the base system - and for me: Less reason to use > FreeBSD instead of Linux. > > I absolutely see the problem of maintaining out-of-date packages in > the base system, and the desirability of making the base system less > reliant on GPL. I'm mostly troubled by the fact that there seems to > be a rather strong tendency the last few years of having steadily > less functionality in the base system - and I'm not at all convinced > that the right balance has been found here. I think this is the core problem at the root of many discussions besides this one. What is the base system? FreeBSD users tend to agree that we like a self-contained wad of stuff called The Base System but disagree quite strongly about what should be in it. There are several approaches to the problem, ranging from concrete and specific ("exactly what shipped with 4.4BSD", a.k.a. Originalism) to principled but open to interpretation ("what 4.4BSD would ship if it were released today", a.k.a. Founders' Intent). We will never all agree on exactly what should be in base vs ports/packages, but can we perhaps build consensus around principles? When you first take it out of the box, does The Base System need to be: - self-bootstrapping - POSIX-compliant - administerable - with local shell - with local tools (e.g. RCS, vim, git...) - with remote shell (SSH) - with remote tools (e.g. Puppet) - with "enterprise" integration (e.g. Kerberos, LDAP, 802.1x, SMB...) - useful for end-user workloads: - [cross-]building FreeBSD - [cross-]building {program X in language Y} - file server - DNS server - Kerberos server - SVN server - Postgres server - Web server - Hadoop node - X server - desktop - able to install packages / build ports to do the above - able to run Linux binaries ? I think we all agree with the first two items, but where should we draw the line? Suppose we distributed install media with The Base System + some packages tailored to a particular environment; would that change what needs to be in The Base System? If "FreeBSD Enterprise Edition" or "FreeBSD Hacker Edition" shipped with The Base System plus whatever packages you need for that environment/workload, and if the installer knew how to install those packages, could The Base System itself be smaller, e.g. just what we need to bootstrap FreeBSD itself? Jon -- Jonathan Anderson jonathan@FreeBSD.org http://freebsd.org/~jonathan/ From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 15:59:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 19EDD474 for ; Tue, 8 Oct 2013 15:59:15 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E1B4A2CDC; Tue, 8 Oct 2013 15:59:14 +0000 (UTC) Received: from joe.srg.cl.cam.ac.uk (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r98FxBL7027088; Tue, 8 Oct 2013 15:59:12 GMT (envelope-from jonathan@FreeBSD.org) Message-ID: <52542BD4.5070706@FreeBSD.org> Date: Tue, 08 Oct 2013 16:59:16 +0100 From: Jonathan Anderson User-Agent: Postbox 3.0.8 (Macintosh/20130427) MIME-Version: 1.0 To: sthaug@nethelp.no Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> In-Reply-To: <20131008.170444.74714516.sthaug@nethelp.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bright@mu.org, lyndon@orthanc.ca, sgk@troutmask.apl.washington.edu, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 15:59:15 -0000 On 8 October 2013 16:04, wrote: > - For some of us, the attraction of FreeBSD is that it is a tightly > integrated system, and the base contains enough useful functionality > that we don't *have* to add a lot of packages. > > - Each package that is moved out of the base system means less useful > functionality in the base system - and for me: Less reason to use > FreeBSD instead of Linux. > > I absolutely see the problem of maintaining out-of-date packages in > the base system, and the desirability of making the base system less > reliant on GPL. I'm mostly troubled by the fact that there seems to > be a rather strong tendency the last few years of having steadily > less functionality in the base system - and I'm not at all convinced > that the right balance has been found here. I think this is the core problem at the root of many discussions besides this one. What is the base system? FreeBSD users tend to agree that we like a self-contained wad of stuff called The Base System but disagree quite strongly about what should be in it. There are several approaches to the problem, ranging from concrete and specific ("exactly what shipped with 4.4BSD", a.k.a. Originalism) to principled but open to interpretation ("what 4.4BSD would ship if it were released today", a.k.a. Founders' Intent). We will never all agree on exactly what should be in base vs ports/packages, but can we perhaps build consensus around principles? When you first take it out of the box, does The Base System need to be: - self-bootstrapping - POSIX-compliant - administerable - with local shell - with local tools (e.g. RCS, vim, git...) - with remote shell (SSH) - with remote tools (e.g. Puppet) - with "enterprise" integration (e.g. Kerberos, LDAP, 802.1x, SMB...) - useful for end-user workloads: - [cross-]building FreeBSD - [cross-]building {program X in language Y} - file server - DNS server - Kerberos server - SVN server - Postgres server - Web server - Hadoop node - X server - desktop - able to install packages / build ports to do the above - able to run Linux binaries ? I think we all agree with the first two items, but where should we draw the line? Suppose we distributed install media with The Base System + some packages tailored to a particular environment; would that change what needs to be in The Base System? If "FreeBSD Enterprise Edition" or "FreeBSD Hacker Edition" shipped with The Base System plus whatever packages you need for that environment/workload, and if the installer knew how to install those packages, could The Base System itself be smaller, e.g. just what we need to bootstrap FreeBSD itself? Jon -- Jonathan Anderson jonathan@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 16:09:00 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3F0A9134; Tue, 8 Oct 2013 16:09:00 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 1C0EE2DA2; Tue, 8 Oct 2013 16:08:59 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 7B9E31A3D6E; Tue, 8 Oct 2013 09:08:59 -0700 (PDT) Message-ID: <52542E1D.9000000@mu.org> Date: Tue, 08 Oct 2013 09:09:01 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Jonathan Anderson Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> In-Reply-To: <52542BD4.5070706@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, lyndon@orthanc.ca, sgk@troutmask.apl.washington.edu, sthaug@nethelp.no X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 16:09:00 -0000 On 10/8/13 8:59 AM, Jonathan Anderson wrote: > On 8 October 2013 16:04, wrote: > > - For some of us, the attraction of FreeBSD is that it is a tightly > > integrated system, and the base contains enough useful functionality > > that we don't *have* to add a lot of packages. > > > > - Each package that is moved out of the base system means less useful > > functionality in the base system - and for me: Less reason to use > > FreeBSD instead of Linux. > > > > I absolutely see the problem of maintaining out-of-date packages in > > the base system, and the desirability of making the base system less > > reliant on GPL. I'm mostly troubled by the fact that there seems to > > be a rather strong tendency the last few years of having steadily > > less functionality in the base system - and I'm not at all convinced > > that the right balance has been found here. > > I think this is the core problem at the root of many discussions > besides this one. What is the base system? > > FreeBSD users tend to agree that we like a self-contained wad of stuff > called The Base System but disagree quite strongly about what should > be in it. There are several approaches to the problem, ranging from > concrete and specific ("exactly what shipped with 4.4BSD", a.k.a. > Originalism) to principled but open to interpretation ("what 4.4BSD > would ship if it were released today", a.k.a. Founders' Intent). > > We will never all agree on exactly what should be in base vs > ports/packages, but can we perhaps build consensus around principles? > > When you first take it out of the box, does The Base System need to be: > > - self-bootstrapping > - POSIX-compliant > - administerable > - with local shell > - with local tools (e.g. RCS, vim, git...) > - with remote shell (SSH) > - with remote tools (e.g. Puppet) > - with "enterprise" integration (e.g. Kerberos, LDAP, 802.1x, SMB...) > - useful for end-user workloads: > - [cross-]building FreeBSD > - [cross-]building {program X in language Y} > - file server > - DNS server > - Kerberos server > - SVN server > - Postgres server > - Web server > - Hadoop node > - X server > - desktop > - able to install packages / build ports to do the above > - able to run Linux binaries > > ? > > I think we all agree with the first two items, but where should we > draw the line? > > Suppose we distributed install media with The Base System + some > packages tailored to a particular environment; would that change what > needs to be in The Base System? If "FreeBSD Enterprise Edition" or > "FreeBSD Hacker Edition" shipped with The Base System plus whatever > packages you need for that environment/workload, and if the installer > knew how to install those packages, could The Base System itself be > smaller, e.g. just what we need to bootstrap FreeBSD itself? > > Jon, You're right on the money, to be honest this is one of the reasons why I've switched to using OSX as my desktop OS. zsh, vim, screen by default. and upgrades work. At the end of the day I'm spending time doing work, not mucking about my workspace to make it usable for development. I think this was brought up at BSDCan in the discussion about making FreeBSD a more featured development platform. Speaking of... has anyone tried PCBSD? -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 16:24:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 44A8A7EE for ; Tue, 8 Oct 2013 16:24:03 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C779A2ED1 for ; Tue, 8 Oct 2013 16:24:02 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBE0EC.dip0.t-ipconnect.de [217.251.224.236]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r98GO0C5052755 for ; Tue, 8 Oct 2013 16:24:00 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r98GNk6h059787 for ; Tue, 8 Oct 2013 18:23:46 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r98GNeMc052790 for ; Tue, 8 Oct 2013 18:23:46 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310081623.r98GNeMc052790@fire.js.berklix.net> To: freebsd-current@freebsd.org Subject: Customising FreeBSD - Was Re: rcs From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 08 Oct 2013 08:20:22 PDT." <525422B6.9040906@mu.org> Date: Tue, 08 Oct 2013 18:23:40 +0200 Sender: jhs@berklix.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 16:24:03 -0000 [ My sympathies lean toward those who want to retain RCS, but as I dont personaly use it, that's all on that. ] ... > "screen, zsh, vim-lite, git" why is that so manual for me? Why can't I > just register a package set somewhere so that all I have to type in is > "alfred.perlstein.devel" into a box during the installer and I get all > my packages by default? In 1993 I was tired of manually customising generic FreeBSD to what I needed, so I wrote & still use http://berklix.com/~jhs/bin/.csh/customise After cd /usr/src;make install I run customise to apply all my outstanding src/ & ports/ patches & ports preferences etc from my public tree. http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/ & run src install again & then variations of cd /usr/ports ; make BERKLIX_MINIMAL=YES BERKLIX_CLIENT=YES make BERKLIX_SERVER=YES BERKLIX_GATE=YES BERKLIX_AMBITIOUS=YES install I'm doing it on Alpha4 now. (Yup I know 5 is out, but ports/ takes days to build). Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 16:43:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3B9C3F2F; Tue, 8 Oct 2013 16:43:51 +0000 (UTC) (envelope-from vsityz@gmail.com) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 78B56200E; Tue, 8 Oct 2013 16:43:50 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id u14so7105971lbd.16 for ; Tue, 08 Oct 2013 09:43:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:cc:subject:content-type:content-transfer-encoding; bh=H8KvCjs1jl6Jzk2al1qCpiC/quAzSNFP7zNt1eVsYwY=; b=HII3mJGKArtRaH14+n6uDrVU7ceQl0CwJo0WFzfgrtge1sv7VLeAqnM89PirFnYlIS 2D5TA8TdExm4QHEjP13/VSh+xgCOuW4tpJEt3vec/8q6241FvgJMoP4Hmv7QrN56mzPV v/Sc3tt2V6gPtMDEvYCE9+rRNHkvrIsvxKn1lRDOKBMTtDLc/G4cn8GkvZoKR0Wv8H40 INxRc0HcHF/I/47E9TDBqgCiK1S1oFUtClm2Kof4OYNKwoiUQA7lQ7VGVyoOXCSR6Oo9 xtT3gxURjRQG0iy8dnEXG3gEdQrEOgQ0bMXB9x695pbrjSBBlvPa1QJ5iNV5NeMGtAO7 6Dig== X-Received: by 10.152.202.167 with SMTP id kj7mr2006696lac.43.1381250628496; Tue, 08 Oct 2013 09:43:48 -0700 (PDT) Received: from scorpion.kiev.ua ([78.111.187.210]) by mx.google.com with ESMTPSA id u18sm23151779lbp.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 09:43:45 -0700 (PDT) Message-ID: <5254363F.6060700@gmail.com> Date: Tue, 08 Oct 2013 19:43:43 +0300 From: Alexander Panyushkin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: FreeBSD Current Subject: problem to build world Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: postmaster@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 16:43:51 -0000 Hi all. r256148 buildworld gives this error: ===> secure/usr.bin/ssh (all) cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/ssh.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/readconf.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/clientloop.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/sshtty.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/sshconnect.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/sshconnect1.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/sshconnect2.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/mux.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/roaming_common.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/roaming_client.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/secure/usr.bin/ssh/../../../crypto/openssh/gss-genr.c cc -O2 -pipe -march=athlon64-sse3 -mtune=athlon64-sse3 -I/usr/src/secure/usr.bin/ssh/../../../crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -include krb5_config.h -std=gnu99 -Qunused-arguments -fstack-protector -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -L/usr/obj/usr/src/tmp/usr/lib/private -rpath /usr/lib/private -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o sshconnect2.o mux.o roaming_common.o roaming_client.o gss-genr.o -lssh -lutil -lldns -lgssapi -lcrypt -lcrypto -lz /usr/obj/usr/src/tmp/usr/lib/private/libldns.so: undefined reference to `ldns_b64_pton_calculate_size' /usr/obj/usr/src/tmp/usr/lib/private/libldns.so: undefined reference to `ldns_b64_ntop_calculate_size' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[5]: stopped in /usr/src/secure/usr.bin/ssh *** Error code 1 * cat /etc/src.conf * WITHOUT_AMD=YES WITHOUT_ATM=YES WITHOUT_AUDIT=YES WITHOUT_AUTHPF=YES WITHOUT_BLUETOOTH=YES WITHOUT_BSNMP=YES WITHOUT_CTM=YES WITHOUT_FREEBSD_UPDATE=YES WITHOUT_GAMES=YES WITHOUT_INET6=YES WITHOUT_IPFILTER=YES WITHOUT_IPFW=YES WITHOUT_IPX=YES WITHOUT_JAIL=YES WITHOUT_NDIS=YES WITHOUT_NIS=YES WITHOUT_PORTSNAP=YES WITHOUT_PROFILE=YES WITHOUT_QUOTAS=YES WITHOUT_RCMDS=YES WITHOUT_RCS=YES WITHOUT_SVNLITE=YES WITH_CLANG=YES WITH_CLANG_EXTRAS=YES WITH_CLANG_IS_CC=YES WITH_BSD_GREP=YES WITH_ICONV=YES WITH_LIBICONV_COMPAT=YES MALLOC_PRODUCTION=YES * cat /etc/make.conf * PUTYPE?=athlon64-sse3 KERNCONF=Kernel NO_CPU_CFLAGS=false NO_CPU_COPTFLAGS=false NO_FSCHG= NO_WERROR= WERROR= MAKE_JOBS_NUMBER=5 BATCH_DELETE_OLD_FILES=yes # IP6_v WITHOUT_INET6= yes WITHOUT_IPV6= yes WITH_SYSTEM_ICU= yes MALLOC_PRODUCTION= yes WITH_MMX= yes WITH_SSE= yes WITH_SSE2= yes WITH_SSE3= yes WITH_SSE4A= yes WITH_3DNOW= yes WITH_THREADS= yes WITH_PKGNG= yes WITHOUT_PROFILE= yes WITHOUT_DEBUG= yes WITHOUT_MODULES= bktr plip .if ${.CURDIR:M*/usr/src/*} || ${.CURDIR:M*/usr/obj/*} CFLAGS+= -march=athlon64-sse3 -mtune=athlon64-sse3 CPPFLAGS+= -D_FORTIFY_SOURCE=2 CXXFLAGS+= -std=c++11 -stdlib=libc++ WITH_LIBCPLUSPLUS=YES .endif From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 17:33:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C7682E58 for ; Tue, 8 Oct 2013 17:33:15 +0000 (UTC) (envelope-from cochard@gmail.com) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6431C2354 for ; Tue, 8 Oct 2013 17:33:15 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id l18so6742526wgh.4 for ; Tue, 08 Oct 2013 10:33:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=xdlouEgoWrS0lFTd/V4Gh/OFwNEekScBzIqr6A/tDoA=; b=dUySL7vbNwF3FARGJt/bk9PufbEcpvHrCIZUMg1YWZLA1xsJ8gxmEk8OHxTgn/2rI2 8KzwaCI0+PQ6c5gc5WETErciTtnaEuMHWmZb/PXKn/QmdFV5QAvBP71px0aa7/7KNGc1 swdn9+zgORKEaS1zz3RnPv2e+D6XSQnNz6mnsx6WQt11Cc5K0no1or+HSV5mQBIX2MEq TROladSel5/LFDO7qBgTHKLpJ5VgcBUK0gL66RotXPRkY4Bq96lYbxNd2miLDlAge2Wr YSkxi2M1TVQ3wVO0UUhaCSnPuSr2b/PTsz4S3Gbsx9V02x7rL3tuc+YdeWFLR/Wc19DX pLpg== X-Received: by 10.180.79.200 with SMTP id l8mr24921190wix.44.1381253593743; Tue, 08 Oct 2013 10:33:13 -0700 (PDT) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.194.236.131 with HTTP; Tue, 8 Oct 2013 10:32:53 -0700 (PDT) In-Reply-To: References: From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Date: Tue, 8 Oct 2013 19:32:53 +0200 X-Google-Sender-Auth: JyLZpPCUqvAMQyG2PnFrY5KJz6A Message-ID: Subject: Re: unionfs related panic on 10.0-ALPHA4 To: "freebsd-current@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 17:33:15 -0000 For information: It's possible to reproduce this problem using the indication given in kern/121385 (5 years old PR). Regards, Olivier From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 17:42:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8B605256 for ; Tue, 8 Oct 2013 17:42:21 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F3CB723D8 for ; Tue, 8 Oct 2013 17:42:20 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBE0EC.dip0.t-ipconnect.de [217.251.224.236]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r98HgH1H056127; Tue, 8 Oct 2013 17:42:18 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r98Hg4rA061362; Tue, 8 Oct 2013 19:42:04 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r98HfbBV055077; Tue, 8 Oct 2013 19:42:03 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310081742.r98HfbBV055077@fire.js.berklix.net> To: Alfred Perlstein Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sun, 06 Oct 2013 10:24:09 PDT." <52519CB9.8040203@mu.org> Date: Tue, 08 Oct 2013 19:41:37 +0200 Sender: jhs@berklix.com Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 17:42:21 -0000 Hi Alfred & cc current. Alfred Perlstein wrote: > On 10/6/13 8:21 AM, Julian H. Stacey wrote: > > I wrote Thu, 03 Oct 2013 23:28:43 +0200 > >> Rui Paulo wrote: > >>> On 2 Oct 2013, at 16:57, Julian H. Stacey wrote: > >>> > >>>> Hi current@, > >>>> It seems I need if_urtwn driver for a really miniature WLAN USB stick, > >>>> & if_urtwn is only in current ? > >>>> man 4 if_urtwn refers to ports/net/urtwn-firmware-kmod which is missing ? > >>> > >>> This driver was never merged to FreeBSD 9. > >> OK, Thanks for confirmation. > >> > >> > >>> Can you use FreeBSD 10 instead? > >> Yes, easier than building from 9.X I guess (& helps test alpha :-). > >> I'll fetch from local mirror, per > >> http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044951.html > >> > >> > >>> The port reference in the man page is wrong. The firmware is now shipped as part of the base system. > >> Oh nice, easier :-) > > I'm happy to report with 10.0-ALPHA4 /boot/loader.conf if_urtwn_load="YES" > > `ifconfig wlan0 scan` works OK. Thanks :-) > > > > Cheers, > > Julian > > Cool! > > I have a g4 tibook 12in with an if_bwn that doesn't really work at all. > > I got one of these (if_urtwn) and it works enough to download about a > meg or so before the watchdog kicks in and I have to ifconfig down/up it > to get it to respond again. > > I even have a patch pending to add the usb identifier for this. > > Is there someone I can provide debug information for to help resolve this? I too am seeing urtwn0: timeout waiting for checksum report sometimes I can scan & sometimes not, (whereas with a run0: stick I have no problem) I've not got as far as trying to move data. I'd appreciate any patches you have Alfred Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 18:17:32 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 75C9DCD6; Tue, 8 Oct 2013 18:17:32 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2478E25ED; Tue, 8 Oct 2013 18:17:32 +0000 (UTC) Received: by mail-qe0-f50.google.com with SMTP id a11so6970979qen.23 for ; Tue, 08 Oct 2013 11:17: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; bh=Fj7o5scyhD1Oop0Q6QNMl7tt7ly8XP+E6w1V8RT3j0M=; b=lOZ3PXtyDAzpIh5cbYiPZ3JjzE5oyOZuT0jNvo4ifZ1hfBre2gP1skoawnBIsETGhh mLYPTuAaBxTyyih7xkGzVS//Cvm+QuCQtwtGwRy3nSMqiUFhgPq4uFtqXxBD8ONxoYAR 34km2XEVX+hUtecg8yfeuAvTtJSLeYd5PFJ2j+K8AM2kvnKQRuLRiGaY3vGYHRyOHNzn Kav/ljT2q9ES70QZ3KVJInyvz/1CoE5yX52bhUimOVXuDNNKFkvrJyg35YJLW771ETXz 1cQKCMdzu5p88Z8PKNJ4i22bst/BOc8t0SghZjhZ3j2pawIVEL25CGLFyHxohlQaYa1A doaw== MIME-Version: 1.0 X-Received: by 10.224.20.198 with SMTP id g6mr5986674qab.24.1381256251316; Tue, 08 Oct 2013 11:17:31 -0700 (PDT) Received: by 10.49.39.33 with HTTP; Tue, 8 Oct 2013 11:17:31 -0700 (PDT) In-Reply-To: <52541202.3010707@mu.org> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> Date: Tue, 8 Oct 2013 11:17:31 -0700 Message-ID: Subject: Re: rcs From: Freddie Cash To: Alfred Perlstein Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Lyndon Nerenberg , "freebsd-current@freebsd.org" , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 18:17:32 -0000 On Tue, Oct 8, 2013 at 7:09 AM, Alfred Perlstein wrote: > On 10/7/13 9:49 PM, Julian Elischer wrote: > >> On 10/8/13 11:19 AM, Lyndon Nerenberg wrote: >> >>> On 2013-10-07, at 8:15 PM, Steve Kargl >> edu > wrote: >>> >>> Maybe there was no development for 15 years. However, the 7364 >>>> lines in ChangeLog after 2010-02-04 suggests that there may >>>> be few bugs to worry about. >>>> >>> >> I think the fact is that most direct users of RCS use it in a very simpl= e >> way, and >> it works just fine for that. with no real need for any updates or any >> change. >> > > With all due respect Julian, The more we discuss this more this really > points to the problem that FreeBSD appears to be a challenge to install > packages into such that a package moving out of base is such a big deal. > > Can we fix that instead? > > I mean, this change should really not be a big deal, but yet it is and > this speaks to the core of FreeBSD utility. > > So again, is there a way to make it so adding RCS after install is not a > big deal at all? =E2=80=8BI haven't kept up-to-date with all the developments, but isn't thi= s part of the bsdinstall/pkgng plan? Once the pkgng repos are all available and populated, then bsdinstall will be able to install packages from there during the install. And, isn't that part of the plan for the DVD installers, to include an "installer repo" for off-line installs? IOW, theoretically, one could just download the 10.0 DVD, boot, install the base, browse the repo on the DVD, select items to install, install, reboot, and be finished. Without ever needing to touch an Internet connection until after rebooting into FreeBSD, if it's even needed at all. Or was that one of the "pie-in-the-sky" ideas that hasn't materialised yet?= =E2=80=8B --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 18:35:20 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 83DBE5AE for ; Tue, 8 Oct 2013 18:35:20 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 44F3C272E for ; Tue, 8 Oct 2013 18:35:20 +0000 (UTC) Received: by mail-qc0-f172.google.com with SMTP id l13so6372797qcy.17 for ; Tue, 08 Oct 2013 11:35:19 -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=CL7QHQLVhGHPocw9GYr5uvwV20V78acuTzExbhdIjiE=; b=FWRCZKhGBw3hSjbJRq/sAROOzOF8FjLlRxkJyC++jyCvGFIX1sLk3gCTeYzQRd5fZ8 Q/HzIjJGObsX2qoTp+1SuWzeA70lrM5wZVqXiHsOkDOpF/bRfTD07t040w+chEP6Zxwj mDcOMhqBpSgnOPOl+PSBf4TSCPnMURUkUaOtjaH3BIp9bx1EZ+0wROPrbaDcgeUFA/ZJ EMmcg43vPxkyxxbJH+0jPzIr+AXEhvyypY5U6LXsZlzMn2iixgT/wPZRMmhswKr1YPTY 99YPA9jzrsy1d3aNSp5uo88GAKfFe07IZ76DLmFdIi/G0BLsj7VbKl1xsf4/T5raAXYX ErUw== MIME-Version: 1.0 X-Received: by 10.224.125.4 with SMTP id w4mr5772560qar.75.1381257319356; Tue, 08 Oct 2013 11:35:19 -0700 (PDT) Received: by 10.49.39.33 with HTTP; Tue, 8 Oct 2013 11:35:19 -0700 (PDT) In-Reply-To: <52542E1D.9000000@mu.org> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> Date: Tue, 8 Oct 2013 11:35:19 -0700 Message-ID: Subject: Re: rcs From: Freddie Cash To: Alfred Perlstein Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD-Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 18:35:20 -0000 On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein wrote: > You're right on the money, to be honest this is one of the reasons why > I've switched to using OSX as my desktop OS. > > zsh, vim, screen by default. and upgrades work. At the end of the day > I'm spending time doing work, not mucking about my workspace to make it > usable for development. > > I think this was brought up at BSDCan in the discussion about making > FreeBSD a more featured development platform. > > Speaking of... has anyone tried PCBSD? PC-BSD isn't much different from FreeBSD. The installer is GUI and support ZFS, there are some GUI setup tools on first boot for X, there are some GUI tools to select binary drivers for X, and there =E2=80=8B=E2=80=8Bare worki= ng pkgng repos available. I had a lot of issues with PC-BSD 9.0 and 9.1 as I was trying to do things "the FreeBSD way" which broke a lot of things that were done "the PC-BSD way" (aka don't manually edit config files used for booting). =E2=80=8BSwitching to the "rolling-release" (aka PC-BSD 9-STABLE) and movin= g all my config file edits into .conf.local fixed my issues. Things have been running smooth, and I finally understand the beauty and simplicity of freebsd-update + pkg. OS gets updated once per month, packages get updated twice per month, no more compiling things from source. It's like using Ubuntu/Debian but with the power and features of FreeBSD. :) =E2=80=8B --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 18:49:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5699EBE3 for ; Tue, 8 Oct 2013 18:49:51 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DAA5D27F9 for ; Tue, 8 Oct 2013 18:49:50 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBE0EC.dip0.t-ipconnect.de [217.251.224.236]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r98InkAP059817; Tue, 8 Oct 2013 18:49:47 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r98InX0Z062066; Tue, 8 Oct 2013 20:49:33 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r98InKOn057406; Tue, 8 Oct 2013 20:49:27 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310081849.r98InKOn057406@fire.js.berklix.net> to: freebsd-current@freebsd.org Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 08 Oct 2013 19:41:37 +0200." Date: Tue, 08 Oct 2013 20:49:20 +0200 Sender: jhs@berklix.com Cc: Alfred Perlstein X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 18:49:51 -0000 > I too am seeing > urtwn0: timeout waiting for checksum report & urtwn0: at uhub3, port 3, addr 4 (disconnected) (BTW there's no external hub, uhub3 must be inside laptop, & there's no loose connection, laptop was not touched, all work was remote) PS a typical sample comparison of scanned signal strengths of one of the ~15 nets localy: 54M -49:-86 100 EP RSN WPA WME run0 big stick, 54M -69:-95 100 EP RSN WPA WME urtwn0 nano edimax EW-7811Un so the edimax is typically down about 20 on left column on all ~15 local nets. The aerial must be a minute fraction of the wavelength. I suppose wavelengths are is approx: 3 x 10^8 metre/second / 2.4 GHz = 3/2.4 x 10^(8-9) m = 12.5 cm & ~6cm for 5GHz band. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 18:53:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 30854F4D for ; Tue, 8 Oct 2013 18:53:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x236.google.com (mail-qe0-x236.google.com [IPv6:2607:f8b0:400d:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E4792286E for ; Tue, 8 Oct 2013 18:53:34 +0000 (UTC) Received: by mail-qe0-f54.google.com with SMTP id 1so2985997qec.27 for ; Tue, 08 Oct 2013 11:53:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ziUav52S1b7PITLCv737z5PHqPHM60InrLwhhgeAZNY=; b=uV6wBsIB0LGxnF9iYPSKOPV6dgSpRDxHN9JyqhT6WQqq62U0f7S0VlW/WUMkNabKAF aZHyZeAqWQfGlUqNrGU9egM7qdemD2DdQ1TmO6kzgawm8LzFXZLMjcpyPF1fLMQQvlBg ug0C8d//a4Gy0RnaCmViX13tSefZIYRX3RV1MzISgYVSEJODQAMStsG847X/NWk8gCno Gw8UjhBXQIZIIQmguxn9F4pg+r+E3q+1L9Sfokgi4OX6p6vnZxGF3JweivHzcJiD2mRz 9a7icyP9urkqPBUIWAKN2GNfeOTjFSHPLr+cbM67I4XQ+Chd9QtDyfs4CejT9qqzMwXt wegw== MIME-Version: 1.0 X-Received: by 10.229.75.9 with SMTP id w9mr4411996qcj.0.1381258414075; Tue, 08 Oct 2013 11:53:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 8 Oct 2013 11:53:34 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Tue, 8 Oct 2013 11:53:34 -0700 (PDT) In-Reply-To: <201310081849.r98InKOn057406@fire.js.berklix.net> References: <201310081849.r98InKOn057406@fire.js.berklix.net> Date: Tue, 8 Oct 2013 11:53:34 -0700 X-Google-Sender-Auth: 1Z9BvUKfFB8GDvkCv1NCxVasYpg Message-ID: Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter From: Adrian Chadd To: "Julian H. Stacey" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Alfred Perlstein , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 18:53:35 -0000 Hi, Note the noise floor differences.. wonder why that is. Rui ported the uwrtn stuff, right? He may be able to help. The driver is recent and its likely there are bugs to shake out. -adrian On Oct 8, 2013 2:49 PM, "Julian H. Stacey" wrote: > > I too am seeing > > urtwn0: timeout waiting for checksum report > & > urtwn0: at uhub3, port 3, addr 4 (disconnected) > (BTW there's no external hub, uhub3 must be inside laptop, > & there's no loose connection, laptop was not touched, all work was remote) > > PS a typical sample comparison of scanned signal strengths > of one of the ~15 nets localy: > 54M -49:-86 100 EP RSN WPA WME run0 big stick, > 54M -69:-95 100 EP RSN WPA WME urtwn0 nano edimax EW-7811Un > so the edimax is typically down about 20 on left column on all ~15 local > nets. > > The aerial must be a minute fraction of the wavelength. > I suppose wavelengths are is approx: > 3 x 10^8 metre/second / 2.4 GHz = 3/2.4 x 10^(8-9) m = 12.5 cm > & ~6cm for 5GHz band. > > Cheers, > Julian > -- > Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich > http://berklix.com > Reply below not above, like a play script. Indent old text with "> ". > Send plain text. No quoted-printable, HTML, base64, > multipart/alternative. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 18:58:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 69C552E4 for ; Tue, 8 Oct 2013 18:58:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 28CBF289F for ; Tue, 8 Oct 2013 18:58:56 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id c9so6430438qcz.28 for ; Tue, 08 Oct 2013 11:58:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=BUNb+bxfappiACtib8LUlxwfM8rdQoWG9SkMnxs0V1w=; b=Z0EvRYrqimmy4Cde/xWYyjoeUeQgSjtqibihZchns/pGdHgrcn0K9KLIimkIg2dPfW /uxEFkGFDMfVsVi2Z3rXnl/HO1opxXxSom+iicKQnr/90DY5uan/hsrS4en2RUm3RsoN 0XIyhtYb/EK7tKYymQY0IKEM5VTQi+WC+whOeLj8685+aeIE3VOMA9bQ5+GBU6rwqZIX yQNabQuJIn5t8btSfS4upeQnc6nvJLvFLfn8HxInvD5dmBigaJieSKmzwF2ocetBJrpd 5zJUqLdJ1bM6AyJn2PurAG+6FmCA2YYDjmRxWaxpYOvOlHKXuqB4tNpdNd3P9gxcl3aV J1jw== MIME-Version: 1.0 X-Received: by 10.224.114.201 with SMTP id f9mr6112206qaq.4.1381258735326; Tue, 08 Oct 2013 11:58:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 8 Oct 2013 11:58:55 -0700 (PDT) Received: by 10.224.207.66 with HTTP; Tue, 8 Oct 2013 11:58:55 -0700 (PDT) In-Reply-To: <525422B6.9040906@mu.org> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> Date: Tue, 8 Oct 2013 11:58:55 -0700 X-Google-Sender-Auth: gUrnqO9ABr01jWWn5bkmswdAsz8 Message-ID: Subject: Re: rcs From: Adrian Chadd To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 18:58:56 -0000 I think that's great. But, as we are increasingly finding, theres no stable ports snapshot, so unless we as a project change how packages are managed, there may not really be a stable, predictable version of things once they're moved from base to a package. A number of users and companies like that there is a very strict definition of base and that it wont change as the ports tree changes. Eg, you install 10.0 and get the rcs package from that. You then do an install of 10.0 a yeat later and install rcs. If it comes from the 10-stable pkgng set, itll pick up the latest version, not the 10.0 version. Thats the big ports vs base difference. -adrian On Oct 8, 2013 11:20 AM, "Alfred Perlstein" wrote: > On 10/8/13 8:04 AM, sthaug@nethelp.no wrote: > >> I think the fact is that most direct users of RCS use it in a very >>>> simple way, and >>>> it works just fine for that. with no real need for any updates or any >>>> change. >>>> >>> With all due respect Julian, The more we discuss this more this really >>> points to the problem that FreeBSD appears to be a challenge to install >>> packages into such that a package moving out of base is such a big deal. >>> >>> Can we fix that instead? >>> >>> I mean, this change should really not be a big deal, but yet it is and >>> this speaks to the core of FreeBSD utility. >>> >> Not commenting on RCS here, but on the concept of moving packages out >> of the base: >> >> - For some of us, the attraction of FreeBSD is that it is a tightly >> integrated system, and the base contains enough useful functionality >> that we don't *have* to add a lot of packages. >> >> - Each package that is moved out of the base system means less useful >> functionality in the base system - and for me: Less reason to use >> FreeBSD instead of Linux. >> >> I absolutely see the problem of maintaining out-of-date packages in >> the base system, and the desirability of making the base system less >> reliant on GPL. I'm mostly troubled by the fact that there seems to >> be a rather strong tendency the last few years of having steadily >> less functionality in the base system - and I'm not at all convinced >> that the right balance has been found here. >> >> This discussion is not new, and I don't expect to convince any new >> persons... >> >> >> I'm sure other devs will disagree, but with ~15 years of FreeBSD > experience and ~13 years as a dev, my very strong opinion is that this > tightly coupled system is actually a boat anchor sinking us. > > Just because no one else does it a certain way, does not mean that a > unique way of doing something is correct and/or sustainable. Maybe in > 1995, 1999, or 2005 even, but not today. Especially in the context of > add-on tools like rcs. > > What we need to discuss is lowering the bar to making custom installs. > > I personally find that installing FreeBSD is useless until I install > "screen, zsh, vim-lite, git" why is that so manual for me? Why can't I > just register a package set somewhere so that all I have to type in is > "alfred.perlstein.devel" into a box during the installer and I get all my > packages by default? > > -- > Alfred Perlstein > > ______________________________**_________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@** > freebsd.org " > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:01:37 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C54BEAA7 for ; Tue, 8 Oct 2013 20:01:37 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from server.i805.com.br (mailhost.i805.com.br [72.52.97.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AE0462CDB for ; Tue, 8 Oct 2013 20:01:37 +0000 (UTC) Received: from i805.com.br (localhost [127.0.0.1]) by server.i805.com.br (8.14.6/8.14.5) with ESMTP id r98K1Zo5089745; Tue, 8 Oct 2013 17:01:35 -0300 (BRT) (envelope-from rizzo@i805.com.br) From: "Nilton Jose Rizzo" To: "Eric L. Camachat" Subject: Re: Virtual box require LIBCXX Date: Tue, 8 Oct 2013 17:01:35 -0300 Message-Id: <20131008200010.M71841@i805.com.br> In-Reply-To: <52543627.8040301@gmail.com> References: <20131008141346.M55461@i805.com.br> <52543627.8040301@gmail.com> X-Mailer: OpenWebMail 3.00_beta4 20121104 671 X-OriginatingIP: 179.218.87.141 (rizzo) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on server.i805.com.br Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:01:37 -0000 Em Tue, 08 Oct 2013 09:43:19 -0700, Eric L. Camachat escreveu > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 10/08/2013 07:17, Nilton Jose Rizzo wrote: > > root@valfenda:/usr/ports/emulators/virtualbox-ose # kldload vboxdrv > > root@valfenda:/usr/ports/emulators/virtualbox-ose # > > > > but whern I run it, the I got this error message: > > rizzo@valfenda:~/src/Doutorado/visao/testes % VirtualBox > > VirtualBox: Error -610 in supR3HardenedMainInitRuntime! > > VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: > > /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by > > /usr/local/lib/virtualbox/VBoxRT.so not found > > > My box can be fixed by remove misc/compat8x package. In my box it was used by bootstrap jdk, look root@valfenda:/usr # pkg query %ro compat8x-amd64 java/bootstrap-openjdk root@valfenda:/usr # You don't use java? > > Eric > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (FreeBSD) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iF4EAREIAAYFAlJUNicACgkQSfBQu3oOwYxoRwEAgcXGhnbrW6ARTsoOblA7urrc > o/7zf5O+MekTczEWn/YA/23CjxEj22cYcd3A6tHWGa4cBcju5fmL8YWGXv5Yonrc > =xk3B > -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:17:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CB1D6FB5 for ; Tue, 8 Oct 2013 20:17:15 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9A96A2D91 for ; Tue, 8 Oct 2013 20:17:15 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MUD00G009KJV000@smtpauth3.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Tue, 08 Oct 2013 15:17:13 -0500 (CDT) X-Spam-PmxInfo: Server=avs-3, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.10.8.200323, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (unknown [140.105.20.242]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MUD006569OLUX30@smtpauth3.wiscmail.wisc.edu>; Tue, 08 Oct 2013 15:17:11 -0500 (CDT) Message-id: <52546844.2010608@freebsd.org> Date: Tue, 08 Oct 2013 22:17:08 +0200 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 To: Allan Jude , freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> In-reply-to: <52531295.7090700@allanjude.com> X-Enigmail-Version: 1.5.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:17:16 -0000 On 10/07/13 21:59, Allan Jude wrote: > Devin Teske and I have been working on a big patch to bsdinstall to > implement installing on a ZFS pool. It supports both GPT and MBR, the 4k > sector gnop trick, and optional GELI encryption. We would like to commit > this in time for 10.0-BETA1 so it needs some testing to work out any > obvious bugs before we send it off to re@ to get it committed. > > It includes a single configuration menu that allows you to select all of > the required details, including which drives to use (gets details from > camcontrol, also includes an inspection utility that presents the > detailed output of camcontrol inquiry/identify, and gpart show), what > ZFS RAID level to use (taking in to consideration the selected number of > drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. > > > Additional, it includes some other changes to bsdinstall: > 1. Change the default to the 'non-standard keyboard mapping' prompt to no > 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 > 3. Remove the dialog asking if you wish to enable crash dumps, this > feature has been combined into the regular 'services to enable' dialog > and enabled by default > > > You can browse the patches here: > http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ > > I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, > available compressed (48 MB) or uncompressed (211 MB): > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso > > > We look forward to your feedback > Thanks for doing this! I had a few comments: 1. ZFS is not bootable on all architectures. Could you adjust that menu item to only display for i386, amd64, and (I think?) sparc64. Use uname -m, not -p, for this. 1a. The script is broken on sparc64 in any case, which uses VTOC8 instead of GPT. 2. Why are you using camcontrol? That is guaranteed not to work on non-CAM systems. You should use the GEOM ident string if you need an ID. 3. Any plans to integrate this into the regular partition editor? ZFS support is important enough that I will definitely not get in the way, even as a bolt-on, but it would be a shame for it to stay that way. The editor is also designed for ZFS to be added. 4. What is this gnop stuff for? 5. I think some substantial part of the MBR code will blow up if you are reinitalizing a previously formatted disk (the bsdlabel will be retasted and come back from the dead). -Nathan From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:20:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 41E89189; Tue, 8 Oct 2013 20:20:47 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 291A02DDD; Tue, 8 Oct 2013 20:20:46 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id F1A581A3DBE; Tue, 8 Oct 2013 13:20:45 -0700 (PDT) Message-ID: <52546920.8090600@mu.org> Date: Tue, 08 Oct 2013 13:20:48 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Freddie Cash Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Jordan Hubbard , Lyndon Nerenberg , "freebsd-current@freebsd.org" , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:20:47 -0000 oops, sent from my non-subscribed email.. On 10/8/13 11:17 AM, Freddie Cash wrote: > On Tue, Oct 8, 2013 at 7:09 AM, Alfred Perlstein >wrote: > > On 10/7/13 9:49 PM, Julian Elischer wrote: > > On 10/8/13 11:19 AM, Lyndon Nerenberg wrote: > > On 2013-10-07, at 8:15 PM, Steve Kargl > > wrote: > > Maybe there was no development for 15 years. However, > the 7364 > lines in ChangeLog after 2010-02-04 suggests that > there may > be few bugs to worry about. > > > I think the fact is that most direct users of RCS use it in a > very simple way, and > it works just fine for that. with no real need for any > updates or any change. > > > With all due respect Julian, The more we discuss this more this > really points to the problem that FreeBSD appears to be a > challenge to install packages into such that a package moving out > of base is such a big deal. > > Can we fix that instead? > > I mean, this change should really not be a big deal, but yet it is > and this speaks to the core of FreeBSD utility. > > So again, is there a way to make it so adding RCS after install is > not a big deal at all? > > > ​I haven't kept up-to-date with all the developments, but isn't this > part of the bsdinstall/pkgng plan? Once the pkgng repos are all > available and populated, then bsdinstall will be able to install > packages from there during the install. And, isn't that part of the > plan for the DVD installers, to include an "installer repo" for > off-line installs? > > IOW, theoretically, one could just download the 10.0 DVD, boot, > install the base, browse the repo on the DVD, select items to install, > install, reboot, and be finished. Without ever needing to touch an > Internet connection until after rebooting into FreeBSD, if it's even > needed at all. > > Or was that one of the "pie-in-the-sky" ideas that hasn't materialised > yet?​ > I thought sysinstall could do this 13 years ago? -Alfred From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:21:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0A5322A0; Tue, 8 Oct 2013 20:21:21 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from smtp-out-02.shaw.ca (smtp-out-03.shaw.ca [64.59.136.139]) by mx1.freebsd.org (Postfix) with ESMTP id BA0BE2DEF; Tue, 8 Oct 2013 20:21:20 +0000 (UTC) X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=ryrf5q5p6c4dCQYR2lAej91p2ozDt6sfPnRAuS/Q8hc= c=1 sm=1 a=Z9FrMq5ANE4A:10 a=QrugwKR0C_UA:10 a=wAGQQ9Az6v0A:10 a=BLceEmwcHowA:10 a=ICAaq7hcmGcA:10 a=kj9zAlcOel0A:10 a=IbtKDeXwb2+SRU442/pi3A==:17 a=6I5d2MoRAAAA:8 a=BWvPGDcYAAAA:8 a=jSwwas1mrufDlWQ2teUA:9 a=CjuIK1q_8ugA:10 a=SV7veod9ZcQA:10 a=V7tsTZBp22UA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO spqr.komquats.com) ([96.50.7.119]) by smtp-out-02.shaw.ca with ESMTP; 08 Oct 2013 14:21:13 -0600 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTP id D83BED2; Tue, 8 Oct 2013 13:21:12 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.14.7/8.14.7) with ESMTP id r98KLBAx057775; Tue, 8 Oct 2013 13:21:11 -0700 (PDT) (envelope-from Cy.Schubert@komquats.com) Message-Id: <201310082021.r98KLBAx057775@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.5 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Julian Elischer Subject: Re: [Heads Up] RCS removed from base In-Reply-To: Message from Julian Elischer of "Tue, 08 Oct 2013 12:09:06 +0800." <52538562.6030703@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Oct 2013 13:21:11 -0700 Cc: freebsd-current@freebsd.org, core@freebsd.org, Steve Rikli X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:21:21 -0000 In message <52538562.6030703@freebsd.org>, Julian Elischer writes: > On 10/8/13 10:03 AM, Steve Rikli wrote: > > On Mon, Oct 07, 2013 at 06:32:21PM -0700, Alfred Perlstein wrote: > >> On 10/7/13 6:30 PM, Steve Kargl wrote: > >>> ... > >>> PS: As noted, the code is GPL. There has been an effort > >>> to remove GPL code from FreeBSD (whether prudent or not). > >> That plus the age of the code is good enough reason to ditch it! huzzah! > >> Plus we can make RCSBSD along with it. > > Is such a project underway? I.e. an RCS of some kind from FreeBSD? > > > > OpenBSD went through this a while ago and use OpenRCS -- is that even > > remotely appropriate for use in FreeBSD? > > > > >From reading most of both thread(s), it seems there's at least some > > interest in keeping an RCS in base; whether it's the status quo RCS > > (w/GPL) doesn't seem to be strictly required, as long as whichever RCS > > is available in base is (mostly?) compatible with status quo RCS. > > the prudent path is to put the original back > before 10 and arange to replace it by 11 > I'm officially asking core to allow this to stop what I consider a bad > POLA problem. > it can not be said that there was no pushback against this change. > and it was sprung on us with no real warning. Probably a good idea. Though I've put a rcs57 port in place, ports need to be updated and probably a little more warning would have been nice. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:22:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 951333C9 for ; Tue, 8 Oct 2013 20:22:28 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 81FA92E08 for ; Tue, 8 Oct 2013 20:22:28 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 333341A3DA8; Tue, 8 Oct 2013 13:22:28 -0700 (PDT) Message-ID: <52546986.8020903@mu.org> Date: Tue, 08 Oct 2013 13:22:30 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: "Julian H. Stacey" Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter References: <201310081742.r98HfbBV055077@fire.js.berklix.net> In-Reply-To: <201310081742.r98HfbBV055077@fire.js.berklix.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:22:28 -0000 On 10/8/13 10:41 AM, Julian H. Stacey wrote: > Hi Alfred & cc current. > > Alfred Perlstein wrote: >> On 10/6/13 8:21 AM, Julian H. Stacey wrote: >>> I wrote Thu, 03 Oct 2013 23:28:43 +0200 >>>> Rui Paulo wrote: >>>>> On 2 Oct 2013, at 16:57, Julian H. Stacey wrote: >>>>> >>>>>> Hi current@, >>>>>> It seems I need if_urtwn driver for a really miniature WLAN USB stick, >>>>>> & if_urtwn is only in current ? >>>>>> man 4 if_urtwn refers to ports/net/urtwn-firmware-kmod which is missing ? >>>>> This driver was never merged to FreeBSD 9. >>>> OK, Thanks for confirmation. >>>> >>>> >>>>> Can you use FreeBSD 10 instead? >>>> Yes, easier than building from 9.X I guess (& helps test alpha :-). >>>> I'll fetch from local mirror, per >>>> http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044951.html >>>> >>>> >>>>> The port reference in the man page is wrong. The firmware is now shipped as part of the base system. >>>> Oh nice, easier :-) >>> I'm happy to report with 10.0-ALPHA4 /boot/loader.conf if_urtwn_load="YES" >>> `ifconfig wlan0 scan` works OK. Thanks :-) >>> >>> Cheers, >>> Julian >> Cool! >> >> I have a g4 tibook 12in with an if_bwn that doesn't really work at all. >> >> I got one of these (if_urtwn) and it works enough to download about a >> meg or so before the watchdog kicks in and I have to ifconfig down/up it >> to get it to respond again. >> >> I even have a patch pending to add the usb identifier for this. >> >> Is there someone I can provide debug information for to help resolve this? > I too am seeing > urtwn0: timeout waiting for checksum report > sometimes I can scan & sometimes not, > (whereas with a run0: stick I have no problem) > I've not got as far as trying to move data. > I'd appreciate any patches you have Alfred Unfortunately all my time right now is being spent syncing changes to FreeNAS from our commercial product TrueNAS to improve both products. I tried to look at the code but my eyes quickly went cross and I had to get back to build stuff. -Alfred From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:24:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BB085518; Tue, 8 Oct 2013 20:24:40 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from idcmail-mo2no.shaw.ca (idcmail-mo2no.shaw.ca [64.59.134.9]) by mx1.freebsd.org (Postfix) with ESMTP id 7B12A2E33; Tue, 8 Oct 2013 20:24:40 +0000 (UTC) X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=jhVCqOCcONDhIh1w2GEjcBn40ITekX4NlKMVE0oiDkw= c=1 sm=1 a=Z9FrMq5ANE4A:10 a=QrugwKR0C_UA:10 a=wAGQQ9Az6v0A:10 a=BLceEmwcHowA:10 a=ICAaq7hcmGcA:10 a=kj9zAlcOel0A:10 a=IbtKDeXwb2+SRU442/pi3A==:17 a=6I5d2MoRAAAA:8 a=BWvPGDcYAAAA:8 a=mCVjpchEzNlX4KiWFMAA:9 a=CjuIK1q_8ugA:10 a=SV7veod9ZcQA:10 a=V7tsTZBp22UA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO spqr.komquats.com) ([96.50.7.119]) by idcmail-mo2no.shaw.ca with ESMTP; 08 Oct 2013 14:24:39 -0600 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTP id CD07D57; Tue, 8 Oct 2013 13:24:38 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.14.7/8.14.7) with ESMTP id r98KOc5l058011; Tue, 8 Oct 2013 13:24:38 -0700 (PDT) (envelope-from Cy.Schubert@komquats.com) Message-Id: <201310082024.r98KOc5l058011@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.5 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Julian Elischer Subject: Re: [Heads Up] RCS removed from base In-Reply-To: Message from Julian Elischer of "Tue, 08 Oct 2013 12:42:01 +0800." <52538D19.8000505@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Oct 2013 13:24:38 -0700 Cc: George Mitchell , Steve Kargl , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:24:40 -0000 In message <52538D19.8000505@freebsd.org>, Julian Elischer writes: > On 10/8/13 12:34 PM, Mehmet Erol Sanliturk wrote: > > > > > > > > On Mon, Oct 7, 2013 at 9:49 PM, Julian Elischer > > wrote: > > > > On 10/8/13 9:33 AM, Steve Kargl wrote: > > > > On Mon, Oct 07, 2013 at 08:41:38PM -0400, George Mitchell wrote: > > > > On 10/07/13 20:28, John-Mark Gurney wrote: > > > > Julian Elischer wrote this message on Tue, Oct 08, > > 2013 at 08:01 +0800: > > > > not a big thing but I believe that a lot of > > poeple use ci/co on /etc > > becasue it is "just there" > > > > +1 > > > > Folks, this is just plain a major violation of the > > Principle of Least > > Amazement. RCS is ideal for keeping track of my > > configuration files > > in /etc. What do we gain by removing it? > > > > Less GPL code in FreeBSD? > > > > not a problem unless you plan in shipping a changed version of > > it on your product?? > > > > > > > > Most new versions of GPL licensed code are converted to Version 3 GPL . > > > > This is blocking FreeBSD if they keep GPL licensed code in base , > > because commercial companies usingFreeBSD are not able to use > > FreeBSD any more if the FreeBSD switches to Version 3 GPL . > > > > This obstacle is in the base system GCC : It stayed in an older > > version , and necessitated to switch to Clang/LLVM . > > > > Difficulty of such a switch is apparenly known . > > Therefore cleaning base from GPL licensed code is a vital > > requirement for further progress WITH RESPECT TO FreeBSD Project > > structure . > > > > Thank you very much . > > sure but lets keep the one one in the the tree untill there is a > replacement ready to commit. ro 10 will have NO RCS which is a POLA. We do now have an rcs57 port which is the same as what was in base. The port could be made to _optionally_ install into /usr instead of ${LOCALBASE}. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:25:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 66812633; Tue, 8 Oct 2013 20:25:15 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qe0-x22a.google.com (mail-qe0-x22a.google.com [IPv6:2607:f8b0:400d:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1660A2E46; Tue, 8 Oct 2013 20:25:15 +0000 (UTC) Received: by mail-qe0-f42.google.com with SMTP id gc15so2125395qeb.1 for ; Tue, 08 Oct 2013 13:25: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; bh=95HZEAOs8gQ66MfG4cNJmqIOM4Qgixe91W4HL2NiYJo=; b=xRLgC24FPpPrl1shyxaXd4yt4y9Zu8fWtZpZhkPPHTDTK+3kSO5xDZT5uC73b5e3LH yd9LPIHmTc7U/TDrrOhsBe+1yMKl3k1U/b9JpFp3CWvpi+XwQqKPLX/1VVF97S8LAf2Z xQiowD/dN9DITNZI+ndgXjmRKK9dFCDWYryasoe3e3WsFuuUnT0IskaFdSSNlfDtIiWK HiXWSBEeN/iFLEyOLJSCSjvQ1+tEI5xoyGG5S9CMiywgOebX8+5llt4eSg/DqceYTkFI pvsznMtr2FJDdMQ4k7gpm1PEIor42hHMa/Oa+0XpMuxrqyhXCzLf5GRVldhVvOcxtFrK GHBQ== MIME-Version: 1.0 X-Received: by 10.49.131.132 with SMTP id om4mr4937677qeb.2.1381263914220; Tue, 08 Oct 2013 13:25:14 -0700 (PDT) Received: by 10.49.39.33 with HTTP; Tue, 8 Oct 2013 13:25:14 -0700 (PDT) In-Reply-To: <52546844.2010608@freebsd.org> References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> Date: Tue, 8 Oct 2013 13:25:14 -0700 Message-ID: Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI From: Freddie Cash To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD-Current , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:25:15 -0000 On Tue, Oct 8, 2013 at 1:17 PM, Nathan Whitehorn wr= ote: > 4. What is this gnop stuff for? > Can't comment on the rest, but gnop is required to create 4K-aligned vdevs where the minimum block size is 4K (aka ashift=3D12). Without this, ZFS relies on the underlying disk driver providing the correct information, and most don't. Also, if you don't do this, and create a vdev using 512B sectors, the ashift will be set to 9, and replacing the drive down the line with 4K Advanced Format drive will drop your drive performance in the toilet.=E2=80=8B=E2=80=8B Thus, to future-proof your pool, you need to: - set the ashift of the pool to 12 (4 KB) - align the disk/partition on 4 KB boundaries (starting partition at 1 MB works well) Until our ZFS gains the ability to set a minimum ashift for the pool, or to set the ashift at vdev creation, or all drive manufacturers write perfect firmware, than we need to fake it with gnop. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:29:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 42EDC781 for ; Tue, 8 Oct 2013 20:29:10 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from idcmail-mo2no.shaw.ca (idcmail-mo2no.shaw.ca [64.59.134.9]) by mx1.freebsd.org (Postfix) with ESMTP id 11ADC2E6F for ; Tue, 8 Oct 2013 20:29:09 +0000 (UTC) X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=jhVCqOCcONDhIh1w2GEjcBn40ITekX4NlKMVE0oiDkw= c=1 sm=1 a=QrugwKR0C_UA:10 a=wAGQQ9Az6v0A:10 a=BLceEmwcHowA:10 a=ICAaq7hcmGcA:10 a=kj9zAlcOel0A:10 a=IbtKDeXwb2+SRU442/pi3A==:17 a=ZmIiC_jQAAAA:8 a=BWvPGDcYAAAA:8 a=6I5d2MoRAAAA:8 a=mauELU6HDDKesXaICrUA:9 a=CjuIK1q_8ugA:10 a=PXSvYFfLtboA:10 a=V7tsTZBp22UA:10 a=SV7veod9ZcQA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO spqr.komquats.com) ([96.50.7.119]) by idcmail-mo2no.shaw.ca with ESMTP; 08 Oct 2013 14:29:09 -0600 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTP id F291357; Tue, 8 Oct 2013 13:29:08 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.14.7/8.14.7) with ESMTP id r98KT6MQ058038; Tue, 8 Oct 2013 13:29:06 -0700 (PDT) (envelope-from Cy.Schubert@komquats.com) Message-Id: <201310082029.r98KT6MQ058038@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.5 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Alfred Perlstein Subject: Re: rcs In-Reply-To: Message from Alfred Perlstein of "Tue, 08 Oct 2013 08:20:22 -0700." <525422B6.9040906@mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Oct 2013 13:29:06 -0700 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:29:10 -0000 In message <525422B6.9040906@mu.org>, Alfred Perlstein writes: > On 10/8/13 8:04 AM, sthaug@nethelp.no wrote: > >>> I think the fact is that most direct users of RCS use it in a very > >>> simple way, and > >>> it works just fine for that. with no real need for any updates or any > >>> change. > >> With all due respect Julian, The more we discuss this more this really > >> points to the problem that FreeBSD appears to be a challenge to install > >> packages into such that a package moving out of base is such a big deal. > >> > >> Can we fix that instead? > >> > >> I mean, this change should really not be a big deal, but yet it is and > >> this speaks to the core of FreeBSD utility. > > Not commenting on RCS here, but on the concept of moving packages out > > of the base: > > > > - For some of us, the attraction of FreeBSD is that it is a tightly > > integrated system, and the base contains enough useful functionality > > that we don't *have* to add a lot of packages. > > > > - Each package that is moved out of the base system means less useful > > functionality in the base system - and for me: Less reason to use > > FreeBSD instead of Linux. > > > > I absolutely see the problem of maintaining out-of-date packages in > > the base system, and the desirability of making the base system less > > reliant on GPL. I'm mostly troubled by the fact that there seems to > > be a rather strong tendency the last few years of having steadily > > less functionality in the base system - and I'm not at all convinced > > that the right balance has been found here. > > > > This discussion is not new, and I don't expect to convince any new > > persons... > > > > > I'm sure other devs will disagree, but with ~15 years of FreeBSD > experience and ~13 years as a dev, my very strong opinion is that this > tightly coupled system is actually a boat anchor sinking us. > > Just because no one else does it a certain way, does not mean that a > unique way of doing something is correct and/or sustainable. Maybe in > 1995, 1999, or 2005 even, but not today. Especially in the context of > add-on tools like rcs. > > What we need to discuss is lowering the bar to making custom installs. > > I personally find that installing FreeBSD is useless until I install > "screen, zsh, vim-lite, git" why is that so manual for me? Why can't I > just register a package set somewhere so that all I have to type in is > "alfred.perlstein.devel" into a box during the installer and I get all > my packages by default? A Red Hat-like kickstart or Solaris jumpstart possibly? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:33:32 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E932A929 for ; Tue, 8 Oct 2013 20:33:32 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from smtp-out-02.shaw.ca (smtp-out-03.shaw.ca [64.59.136.139]) by mx1.freebsd.org (Postfix) with ESMTP id BBBEB2ED9 for ; Tue, 8 Oct 2013 20:33:32 +0000 (UTC) X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=ryrf5q5p6c4dCQYR2lAej91p2ozDt6sfPnRAuS/Q8hc= c=1 sm=1 a=Z9FrMq5ANE4A:10 a=QrugwKR0C_UA:10 a=wAGQQ9Az6v0A:10 a=BLceEmwcHowA:10 a=ICAaq7hcmGcA:10 a=kj9zAlcOel0A:10 a=IbtKDeXwb2+SRU442/pi3A==:17 a=shYRFTWRAAAA:8 a=BWvPGDcYAAAA:8 a=6I5d2MoRAAAA:8 a=2ELp5fwWTihCoJW1vxcA:9 a=CjuIK1q_8ugA:10 a=Wpccw3uv0jEA:10 a=V7tsTZBp22UA:10 a=SV7veod9ZcQA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO spqr.komquats.com) ([96.50.7.119]) by smtp-out-02.shaw.ca with ESMTP; 08 Oct 2013 14:33:31 -0600 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTP id 797B957; Tue, 8 Oct 2013 13:33:31 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.14.7/8.14.7) with ESMTP id r98KXUgJ058127; Tue, 8 Oct 2013 13:33:31 -0700 (PDT) (envelope-from Cy.Schubert@komquats.com) Message-Id: <201310082033.r98KXUgJ058127@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.5 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Kurt Lidl Subject: Re: [Heads Up] RCS removed from base In-Reply-To: Message from Kurt Lidl of "Tue, 08 Oct 2013 11:36:39 -0400." <52542687.7000100@pix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Oct 2013 13:33:30 -0700 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:33:33 -0000 In message <52542687.7000100@pix.net>, Kurt Lidl writes: > On 10/8/13, Julian Elischer wrote: > > On 10/7/13 11:06 PM, Steve Kargl wrote: > >> On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: > >>> Hey all, > >>> > >>> RCS was removed from the base system in r256095. If you still want to > >>> use RCS please install either devel/rcs or devel/rcs57. If not, be > >>> sure to check out the alternatives (pun stolen and intended). > >>> > >> Perhaps, a note in src/UPDATING is appropriate? > >> > > ok so what is this, the secret cabal to make FreeBSD useless? > > I'm ccing core as I believe this was not discussed enough in public > > (in fact not discussed AT ALL in any forum I am watching) > > and I officially request a backout of the removal of what I consider > > to be core functionality. > > > > My usual way of doing things is on install to ci EVERYTHING in /etc > > to get a snapsot right the way back to install. > > > > now I have to change things in /etc (and other places) BEFORE I can > > check them in. > > (i.e. get networking up and ports installed) > > not a big thing but I believe that a lot of poeple use ci/co on /etc > > becasue it is "just there" > > > > +1 for keeping a RCS in base. I too use to maintain a bunch of > files in /etc - I have for years and years. I don't particularly > want the GPL'd version - I'd be happiest with the OpenRCS version > (BSD-licensed) from OpenBSD. I've started work on a port (not that this was my highest priority but received a private email that I may want to do this instead of rcs57). Would the majority here rather have it in base? Just finished schlepping the OpenBSD source to my laptop (the link to the OpenRCS site returns a TCP RST). I don't mind either way. It's the groups's and the Project's call. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:37:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E829BB73 for ; Tue, 8 Oct 2013 20:37:06 +0000 (UTC) (envelope-from Cy.Schubert@komquats.com) Received: from idcmail-mo2no.shaw.ca (idcmail-mo2no.shaw.ca [64.59.134.9]) by mx1.freebsd.org (Postfix) with ESMTP id B65912F0F for ; Tue, 8 Oct 2013 20:37:06 +0000 (UTC) X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=jhVCqOCcONDhIh1w2GEjcBn40ITekX4NlKMVE0oiDkw= c=1 sm=1 a=QrugwKR0C_UA:10 a=wAGQQ9Az6v0A:10 a=BLceEmwcHowA:10 a=ICAaq7hcmGcA:10 a=kj9zAlcOel0A:10 a=IbtKDeXwb2+SRU442/pi3A==:17 a=NmLr5vD0AAAA:8 a=BWvPGDcYAAAA:8 a=6I5d2MoRAAAA:8 a=s75Rt1T25lYrbdkW2IEA:9 a=CjuIK1q_8ugA:10 a=V7tsTZBp22UA:10 a=SV7veod9ZcQA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 Received: from unknown (HELO spqr.komquats.com) ([96.50.7.119]) by idcmail-mo2no.shaw.ca with ESMTP; 08 Oct 2013 14:37:05 -0600 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTP id 9677E57; Tue, 8 Oct 2013 13:37:05 -0700 (PDT) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.14.7/8.14.7) with ESMTP id r98Kb4JA058190; Tue, 8 Oct 2013 13:37:04 -0700 (PDT) (envelope-from Cy.Schubert@komquats.com) Message-Id: <201310082037.r98Kb4JA058190@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.5 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Jos Backus Subject: Re: rcs In-Reply-To: Message from Jos Backus of "Tue, 08 Oct 2013 08:49:21 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Oct 2013 13:37:04 -0700 Cc: freebsd-current@freebsd.org, Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:37:07 -0000 In message , Jos Backus writes: > On Oct 7, 2013 7:31 PM, "Lyndon Nerenberg" wrote: > > > > Okay folks, can we make a call about keeping the RCS tools in the base? > > > > The proponents wanting to remove RCS need to speak up and make their > technical case. > > Perhaps slightly off-topic, but how about we move into the 21st century and > import the 2-clause BSD-licensed Fossil? > > http://www.fossil-scm.org/ > > Not RCS, I know, but vastly more useful. Bikeshed alert. Let's not let this discussion go sideways. Seriously, it's not the same. To import something different doesn't replace what was removed. We have two options. Put it back, or something like it, e.g. OpenRCS, back, or put it in ports. Personally I don't think it matters where it lives as long as the same functionality is there. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:17:39 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5406152; Tue, 8 Oct 2013 20:17:39 +0000 (UTC) (envelope-from alfred@ixsystems.com) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 90F952DA0; Tue, 8 Oct 2013 20:17:38 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id C1BB3664DF; Tue, 8 Oct 2013 13:17:38 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 79075-07; Tue, 8 Oct 2013 13:17:29 -0700 (PDT) Received: from Alfreds-MacBook-Pro-9.local (unknown [10.8.0.42]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id 822C2664D0; Tue, 8 Oct 2013 13:17:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ixsystems.com; s=newknight0; t=1381263448; bh=ma9kdvZZrwHMT9Xuc8nrbnMFA9dwCWMWHpsOwPxHQhQ=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=EFo2Lgp+b/QbKwEGh5hn2a+yolcBYebR+ce6rjCaFHWiFSLL/cfn3dx5XkexLtEey 1RoX9x2ef6DjFdIwhanYUU53/26QypZ+e0BlfyFAn1qnypAV78POZTyOxfqTax7/2H CE68uWg+NtC3xmfcH647PdK59/6/5D9q+IxoSm9I= Message-ID: <5254685A.1080401@ixsystems.com> Date: Tue, 08 Oct 2013 13:17:30 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Freddie Cash Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> In-Reply-To: X-Mailman-Approved-At: Tue, 08 Oct 2013 20:37:10 +0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Jordan Hubbard , Lyndon Nerenberg , "freebsd-current@freebsd.org" , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:17:39 -0000 On 10/8/13 11:17 AM, Freddie Cash wrote: > On Tue, Oct 8, 2013 at 7:09 AM, Alfred Perlstein >wrote: > > On 10/7/13 9:49 PM, Julian Elischer wrote: > > On 10/8/13 11:19 AM, Lyndon Nerenberg wrote: > > On 2013-10-07, at 8:15 PM, Steve Kargl > > wrote: > > Maybe there was no development for 15 years. However, > the 7364 > lines in ChangeLog after 2010-02-04 suggests that > there may > be few bugs to worry about. > > > I think the fact is that most direct users of RCS use it in a > very simple way, and > it works just fine for that. with no real need for any > updates or any change. > > > With all due respect Julian, The more we discuss this more this > really points to the problem that FreeBSD appears to be a > challenge to install packages into such that a package moving out > of base is such a big deal. > > Can we fix that instead? > > I mean, this change should really not be a big deal, but yet it is > and this speaks to the core of FreeBSD utility. > > So again, is there a way to make it so adding RCS after install is > not a big deal at all? > > > ​I haven't kept up-to-date with all the developments, but isn't this > part of the bsdinstall/pkgng plan? Once the pkgng repos are all > available and populated, then bsdinstall will be able to install > packages from there during the install. And, isn't that part of the > plan for the DVD installers, to include an "installer repo" for > off-line installs? > > IOW, theoretically, one could just download the 10.0 DVD, boot, > install the base, browse the repo on the DVD, select items to install, > install, reboot, and be finished. Without ever needing to touch an > Internet connection until after rebooting into FreeBSD, if it's even > needed at all. > > Or was that one of the "pie-in-the-sky" ideas that hasn't materialised > yet?​ > Man, we used to be able to do that with sysinstall 10 years ago? Is that broken? -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:38:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D50E6DA8 for ; Tue, 8 Oct 2013 20:38:25 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A22322F36 for ; Tue, 8 Oct 2013 20:38:25 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id x13so21128698ief.17 for ; Tue, 08 Oct 2013 13:38:19 -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:in-reply-to:message-id :references:user-agent:mime-version:content-type; bh=698nJ4e/8o+OQeEvyHXycw4AXZDzOFGFogZJRoYZyug=; b=ab2LsJzYbs27EnectveWwj9t4vuQ78+0T1vS8v4T8/SytkCXT9WgQn5xuj4veVMj0J AfmFsX3fC6z8sVugSw6xeourCExni4ysGM40oBlWC9Xk8gMTszeaAeU1GqtLpC0SC/yO 9EdSQdLvRBBpqE1AX4KKLnICxk8dSh6Z7+/JHdTahiy1ZyHrQOq4d6EC69KRQdoHl+8O pXB4zIRuRgcVE4Lzc1tSo8bu61gHWYeDL0mnDIwW2wT+D/yN6bD+4bMooOapV9YN4a0n kJY8w/IxophXUaHCwn3s9nHbSY9/OdLzMnydVajy44LtLSUV8PrNnQmaPlxLqVlTRhpl rVWw== X-Gm-Message-State: ALoCoQkKq5eC6b9gOooI8cNgYemppBcyUN32sXDB4+UdTuFMUnwVMGpTttvFGNzQM52omFStlKtf X-Received: by 10.50.30.9 with SMTP id o9mr2915951igh.0.1381264698901; Tue, 08 Oct 2013 13:38:18 -0700 (PDT) Received: from wawanesa.iciti.ca (CPE0080c8f208a5-CM001371173cf8.cpe.net.cable.rogers.com. [99.246.61.82]) by mx.google.com with ESMTPSA id w4sm4198117igb.5.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 08 Oct 2013 13:38:17 -0700 (PDT) Date: Tue, 8 Oct 2013 16:38:01 -0400 (EDT) From: Graham Todd X-X-Sender: gtodd@wawanesa.iciti.ca To: Adrian Chadd Subject: Re: rcs In-Reply-To: Message-ID: References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Alfred Perlstein , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:38:26 -0000 On Tue, 8 Oct 2013, Adrian Chadd wrote: > I think that's great. But, as we are increasingly finding, theres no stable > ports snapshot, so unless we as a project change how packages are managed, > there may not really be a stable, predictable version of things once > they're moved from base to a package. A number of users and companies like > that there is a very strict definition of base and that it wont change as > the ports tree changes. > > Eg, you install 10.0 and get the rcs package from that. You then do an > install of 10.0 a yeat later and install rcs. If it comes from the > 10-stable pkgng set, itll pick up the latest version, not the 10.0 version. > Thats the big ports vs base difference. Perhaps a perl style "dual life module" set of "core" (errm BASE?) packages/ports will emerge. It could resolve some of the perennial "what is BASE"? debates - or at least make it possible to have those debates in a different way :-) My understanding is that dealing with the GPLv3 issue for BASE is *necessary* for the project. Since the latest rcs releases are licensed using GPLv3, FreeBSD's BASE rcs (GPLv2) would have to be maintained exclusively by the FreeBSD project - which means more developer overhead (the same could be said for gcc I suppose). That seems to be a different type of issue than the size/completeness of BASE itself. Since rcs is a small utility, it's hooked into a script or two via rc.subr, it's useful to a lot of folks, it doesn't face the network and there's a BSD licensed equivalent sort of available, then maybe the best way to go would be to import opencvs's rcs (which is not part in the ports version of opencvs) to replace the GNU version. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:41:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E3C91219 for ; Tue, 8 Oct 2013 20:41:35 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9BC8F2F8A for ; Tue, 8 Oct 2013 20:41:35 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=UTF-8 Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MUD00I00A0CAR00@smtpauth3.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Tue, 08 Oct 2013 15:41:34 -0500 (CDT) X-Spam-PmxInfo: Server=avs-3, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.10.8.203040, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (unknown [140.105.20.242]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MUD006DEAT6UX40@smtpauth3.wiscmail.wisc.edu>; Tue, 08 Oct 2013 15:41:32 -0500 (CDT) Message-id: <52546DFA.4000500@freebsd.org> Date: Tue, 08 Oct 2013 22:41:30 +0200 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 To: Freddie Cash Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> In-reply-to: X-Enigmail-Version: 1.5.2 Cc: FreeBSD-Current , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:41:36 -0000 On 10/08/13 22:25, Freddie Cash wrote: > On Tue, Oct 8, 2013 at 1:17 PM, Nathan Whitehorn > >wrote: > > 4. What is this gnop stuff for? > > > Can't comment on the rest, but gnop is required to create 4K-aligned > vdevs where the minimum block size is 4K (aka ashift=12). Without > this, ZFS relies on the underlying disk driver providing the correct > information, and most don't. Also, if you don't do this, and create a > vdev using 512B sectors, the ashift will be set to 9, and replacing > the drive down the line with 4K Advanced Format drive will drop your > drive performance in the toilet.​​ > > Thus, to future-proof your pool, you need to: > - set the ashift of the pool to 12 (4 KB) > - align the disk/partition on 4 KB boundaries (starting partition at > 1 MB works well) > > Until our ZFS gains the ability to set a minimum ashift for the pool, > or to set the ashift at vdev creation, or all drive manufacturers > write perfect firmware, than we need to fake it with gnop. > Well, that's a disgusting hack, but I see why it's there. Thanks for the explanation! -Nathan From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:42:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BFCC5358 for ; Tue, 8 Oct 2013 20:42:28 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [78.47.114.122]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F30A42FA7 for ; Tue, 8 Oct 2013 20:42:27 +0000 (UTC) Received: (qmail 68058 invoked by uid 89); 8 Oct 2013 20:38:05 -0000 Received: from unknown (HELO ?192.168.1.201?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 8 Oct 2013 20:38:05 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs From: Rainer Duffner In-Reply-To: <201310082029.r98KT6MQ058038@slippy.cwsent.com> Date: Tue, 8 Oct 2013 22:37:58 +0200 Content-Transfer-Encoding: 7bit Message-Id: <6207997D-81FA-4E19-B094-64EAD4C5F65A@ultra-secure.de> References: <201310082029.r98KT6MQ058038@slippy.cwsent.com> To: Cy Schubert X-Mailer: Apple Mail (2.1510) Cc: Alfred Perlstein , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:42:28 -0000 Am 08.10.2013 um 22:29 schrieb Cy Schubert : > > A Red Hat-like kickstart or Solaris jumpstart possibly? > http://blog.hostileadmin.com/2013/04/11/installing-freebsd-via-cobbler/ I wish it was using bsdinstall, though. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:43:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 64E8346E for ; Tue, 8 Oct 2013 20:43:15 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x232.google.com (mail-qe0-x232.google.com [IPv6:2607:f8b0:400d:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2395A2FB7 for ; Tue, 8 Oct 2013 20:43:15 +0000 (UTC) Received: by mail-qe0-f50.google.com with SMTP id a11so7183832qen.37 for ; Tue, 08 Oct 2013 13:43:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=uzASOMwhBipG35qViWbaOEGCAMHFXCADxbY0k9iMAgM=; b=uJo1H3cvYzRKSQMzRk3ACtSh5vBP1lnE6NvtYf+NuH3EfKjEjlun+fMm9R6rgAbbe0 dwRyK7+aUvceeVllfuuAfTc3PeZBHFizXJvPPM6F8IWIxA3UvT5PVY6ykbQZQ+zdDbJt CZzCKWCSVYl4RnRqVr3Xq5mBm7+JqKyjtUsavepM05UxPkKbni6ns3ud3TSntzL1v9Te VdUBfHMCNmJL//5lHABLxDNiWHnDFjMl22LeVcyOjcJvq4idWJW5gt1B//V+2rtMllzT ooEvcRwZbRmv2UVOH2o4FR+fCnfLShJTmQZKrUTDXZDiKpXOOsQVYO4ynEmTjnH7CXSo UU4w== MIME-Version: 1.0 X-Received: by 10.224.51.131 with SMTP id d3mr6759410qag.0.1381264994286; Tue, 08 Oct 2013 13:43:14 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Tue, 8 Oct 2013 13:43:14 -0700 (PDT) In-Reply-To: References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> Date: Tue, 8 Oct 2013 13:43:14 -0700 X-Google-Sender-Auth: TRkg8DUzMvakxpTtenC-E6gV9bM Message-ID: Subject: Re: rcs From: Adrian Chadd To: Graham Todd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Alfred Perlstein , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:43:15 -0000 I've iterated my views on these things a few times. I honestly am not all _that_ interested in trying to build a polished OS. I'd rather participate in building an OS toolkit that let's PCBSD, pfsense, "that storage appliance I keep forgetting the name of (heh)", etc all build OSes on top of it. I'm hoping that some group will take FreeBSD- as 10.x and later evolves, combines it with pkgng and some package development policies, and rolls OSes that people actually want to use and deploy. I don't mind if that's called pc-bsd. I'd be running pcbsd right now if it were doing drops against -head. I believe this may be happening soon. Just saying.. :-) -adrian From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:50:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0DF23700 for ; Tue, 8 Oct 2013 20:50:19 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C27572FFD for ; Tue, 8 Oct 2013 20:50:18 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r98Khm9H046465; Tue, 8 Oct 2013 16:43:48 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Tue, 08 Oct 2013 16:43:48 -0400 (EDT) Date: Tue, 8 Oct 2013 16:43:48 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Cy Schubert Subject: Re: [Heads Up] RCS removed from base In-Reply-To: <201310082033.r98KXUgJ058127@slippy.cwsent.com> Message-ID: References: <201310082033.r98KXUgJ058127@slippy.cwsent.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, Kurt Lidl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:50:19 -0000 On Tue, 8 Oct 2013, Cy Schubert wrote: > > I've started work on a port (not that this was my highest priority but > received a private email that I may want to do this instead of rcs57). > Would the majority here rather have it in base? Just finished schlepping > the OpenBSD source to my laptop (the link to the OpenRCS site returns a TCP > RST). I don't mind either way. It's the groups's and the Project's call. It seems to have ben taken out without much discussion, and we're in the process of releasing 10.0, so I'd say put it back in base. After 10.0 goes out (or is branched), then we can have a proper discussion about how to remove it and what, if any, to replace it with. -- DE From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:50:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2E97A900; Tue, 8 Oct 2013 20:50:40 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EC73E201A; Tue, 8 Oct 2013 20:50:39 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa02.fnfis.com (8.14.5/8.14.5) with ESMTP id r98KoXJs025035 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 15:50:33 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.02.0309.002; Tue, 8 Oct 2013 15:50:31 -0500 From: "Teske, Devin" To: Nathan Whitehorn Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxGgGPJPIP8ZCyUiSsjBzr2++AA== Date: Tue, 8 Oct 2013 20:50:30 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC46255@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> In-Reply-To: <52546844.2010608@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-08_08:2013-10-08,2013-10-08,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:50:40 -0000 On Oct 8, 2013, at 1:17 PM, Nathan Whitehorn wrote: > On 10/07/13 21:59, Allan Jude wrote: >> Devin Teske and I have been working on a big patch to bsdinstall to >> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >> sector gnop trick, and optional GELI encryption. We would like to commit >> this in time for 10.0-BETA1 so it needs some testing to work out any >> obvious bugs before we send it off to re@ to get it committed. >>=20 >> It includes a single configuration menu that allows you to select all of >> the required details, including which drives to use (gets details from >> camcontrol, also includes an inspection utility that presents the >> detailed output of camcontrol inquiry/identify, and gpart show), what >> ZFS RAID level to use (taking in to consideration the selected number of >> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>=20 >>=20 >> Additional, it includes some other changes to bsdinstall: >> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >> 2. Replace the 3 separate dialogs to configure an ipv4 address with just= 1 >> 3. Remove the dialog asking if you wish to enable crash dumps, this >> feature has been combined into the regular 'services to enable' dialog >> and enabled by default >>=20 >>=20 >> You can browse the patches here: >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>=20 >> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >> available compressed (48 MB) or uncompressed (211 MB): >>=20 >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>=20 >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>=20 >>=20 >> We look forward to your feedback >>=20 >=20 > Thanks for doing this! I had a few comments: > 1. ZFS is not bootable on all architectures. Could you adjust that menu > item to only display for i386, amd64, and (I think?) sparc64. Use uname > -m, not -p, for this. I think we can do that no problem. > 1a. The script is broken on sparc64 in any case, which uses VTOC8 > instead of GPT. *nods* we'll have to purloin your VTOC8 code before we offer it to sparc64. > 2. Why are you using camcontrol? That is guaranteed not to work on > non-CAM systems. You should use the GEOM ident string if you need an ID. I imagine we could get the info from many places, and to be honest, I never knew about "diskinfo" until last week (but apparently it's been around since 5.x days). The one place where I suspect camcontrol(8) usage is appropriate is the mini "disk inspector" dialog. The camcontrol inquiry output is specifically helpful if/when you're doing multipathing (and you need to identify which da# devices are duplicates of the same device -- given Serial#). But I gather you mean for "disk description" in the device menu (for picking text to go along with the device name). I'm open to using a different tool... or multiple tools. Do you think it wo= uld be better to just stick to one tool? or to query a few? (which ones win-out?) > 3. Any plans to integrate this into the regular partition editor? ZFS > support is important enough that I will definitely not get in the way, > even as a bolt-on, but it would be a shame for it to stay that way. The > editor is also designed for ZFS to be added. Yes and yes. (and didn't know the editor was designed for ZFS too) > 4. What is this gnop stuff for? Thanks goes to Freddie Cash for his excellent explanation (I had to admit, I didn't understand it at that level) > 5. I think some substantial part of the MBR code will blow up if you are > reinitalizing a previously formatted disk (the bsdlabel will be retasted > and come back from the dead). Will not some combination of "gpart destroy -F" and (insert suggestion) wor= k? --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:54:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7A374B61 for ; Tue, 8 Oct 2013 20:54:24 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5217A20A4 for ; Tue, 8 Oct 2013 20:54:23 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id g10so9169460pdj.26 for ; Tue, 08 Oct 2013 13:54: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:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=sctys5IwB9B/Fml1DbXOawMugxKhzdlVwhS+IoFt5Ww=; b=Ew8exNeDzvG9N2cAzp6hRd3psWIYI6fKOOlDPMpmqKIhnKt481kZTHsVZklDO3Df67 ol0rQP37B+uXTzg7f76Yd15jF4A/t1kQT0N+3ZRbOxrpzlgCXpMMjEagFSPluqoO7Haf Fcmfn4pZTDkUgXZZgtRDOBV6dQTomn/mr2sfdZnb0cBsOa9QRvX3qShaEykE7xhJbCTZ r5LBVLhwydhfF9GO8yxvIKHWOt5FkDLEnzWExZrNIp0OQC1qO2Zm7QNuw6mqEXHnEpkb 7qaM9ygH/yKy4ewFxEkca/5Npt61+z4Id3nKTyts/NpU4WcW2DsL+fJtnTmHKHX75V+r ZJgQ== X-Gm-Message-State: ALoCoQmtHjv8AQCYZN0w2Y1mUju2DsNm6Lg9h833HNypKZisvnwsrpMi69cU1qTvcOLoei40vPXL MIME-Version: 1.0 X-Received: by 10.68.252.68 with SMTP id zq4mr4093895pbc.154.1381265657001; Tue, 08 Oct 2013 13:54:17 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Tue, 8 Oct 2013 13:54:16 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Tue, 8 Oct 2013 13:54:16 -0700 (PDT) In-Reply-To: <201310082037.r98Kb4JA058190@slippy.cwsent.com> References: <201310082037.r98Kb4JA058190@slippy.cwsent.com> Date: Tue, 8 Oct 2013 13:54:16 -0700 Message-ID: Subject: Re: rcs From: Jos Backus To: Cy Schubert Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org, Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:54:24 -0000 On Oct 8, 2013 1:37 PM, "Cy Schubert" wrote: > > In message om> > , Jos Backus writes: > > On Oct 7, 2013 7:31 PM, "Lyndon Nerenberg" wrote: > > > > > > Okay folks, can we make a call about keeping the RCS tools in the base? > > > > > > The proponents wanting to remove RCS need to speak up and make their > > technical case. > > > > Perhaps slightly off-topic, but how about we move into the 21st century and > > import the 2-clause BSD-licensed Fossil? > > > > http://www.fossil-scm.org/ > > > > Not RCS, I know, but vastly more useful. > > Bikeshed alert. Let's not let this discussion go sideways. > > Seriously, it's not the same. To import something different doesn't replace > what was removed. We have two options. Put it back, or something like it, > e.g. OpenRCS, back, or put it in ports. Personally I don't think it matters > where it lives as long as the same functionality is there. Part of the argument seems to be about improving out of the box functionality and experience. Fossil would help there. But I agree, change is hard, and it has a cost for sure. Sorry for the distraction. Jos From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:56:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ACE2AC95 for ; Tue, 8 Oct 2013 20:56:42 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B82820C5 for ; Tue, 8 Oct 2013 20:56:42 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MUD00G009KKV100@smtpauth3.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Tue, 08 Oct 2013 15:56:41 -0500 (CDT) X-Spam-PmxInfo: Server=avs-3, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.10.8.204831, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (unknown [140.105.20.242]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MUD006ZUBIEUX40@smtpauth3.wiscmail.wisc.edu>; Tue, 08 Oct 2013 15:56:40 -0500 (CDT) Message-id: <52547185.2000009@freebsd.org> Date: Tue, 08 Oct 2013 22:56:37 +0200 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 To: "Teske, Devin" Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC46255@LTCFISWMSGMB21.FNFIS.com> In-reply-to: <13CA24D6AB415D428143D44749F57D720FC46255@LTCFISWMSGMB21.FNFIS.com> X-Enigmail-Version: 1.5.2 Cc: "" , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:56:42 -0000 On 10/08/13 22:50, Teske, Devin wrote: > On Oct 8, 2013, at 1:17 PM, Nathan Whitehorn wrote: > >> On 10/07/13 21:59, Allan Jude wrote: >>> Devin Teske and I have been working on a big patch to bsdinstall to >>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>> sector gnop trick, and optional GELI encryption. We would like to commit >>> this in time for 10.0-BETA1 so it needs some testing to work out any >>> obvious bugs before we send it off to re@ to get it committed. >>> >>> It includes a single configuration menu that allows you to select all of >>> the required details, including which drives to use (gets details from >>> camcontrol, also includes an inspection utility that presents the >>> detailed output of camcontrol inquiry/identify, and gpart show), what >>> ZFS RAID level to use (taking in to consideration the selected number of >>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>> >>> >>> Additional, it includes some other changes to bsdinstall: >>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>> feature has been combined into the regular 'services to enable' dialog >>> and enabled by default >>> >>> >>> You can browse the patches here: >>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>> >>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>> available compressed (48 MB) or uncompressed (211 MB): >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>> >>> >>> We look forward to your feedback >>> >> Thanks for doing this! I had a few comments: >> 1. ZFS is not bootable on all architectures. Could you adjust that menu >> item to only display for i386, amd64, and (I think?) sparc64. Use uname >> -m, not -p, for this. > I think we can do that no problem. > > >> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >> instead of GPT. > *nods* we'll have to purloin your VTOC8 code before we offer it to > sparc64. > > > >> 2. Why are you using camcontrol? That is guaranteed not to work on >> non-CAM systems. You should use the GEOM ident string if you need an ID. > I imagine we could get the info from many places, and to be honest, I never > knew about "diskinfo" until last week (but apparently it's been around since > 5.x days). > > The one place where I suspect camcontrol(8) usage is appropriate is the > mini "disk inspector" dialog. The camcontrol inquiry output is specifically > helpful if/when you're doing multipathing (and you need to identify which > da# devices are duplicates of the same device -- given Serial#). > > But I gather you mean for "disk description" in the device menu (for picking > text to go along with the device name). > > I'm open to using a different tool... or multiple tools. Do you think it would be > better to just stick to one tool? or to query a few? (which ones win-out?) Absolutely all information you could possibly want is inside GEOM, including disk serial numbers. It the Correct Place (tm) for whatever information you want to get. > >> 3. Any plans to integrate this into the regular partition editor? ZFS >> support is important enough that I will definitely not get in the way, >> even as a bolt-on, but it would be a shame for it to stay that way. The >> editor is also designed for ZFS to be added. > Yes and yes. (and didn't know the editor was designed for ZFS too) Great! >> 4. What is this gnop stuff for? > Thanks goes to Freddie Cash for his excellent explanation (I had to > admit, I didn't understand it at that level) > > >> 5. I think some substantial part of the MBR code will blow up if you are >> reinitalizing a previously formatted disk (the bsdlabel will be retasted >> and come back from the dead). > Will not some combination of "gpart destroy -F" and (insert suggestion) work? Yes, that will work just fine. -Nathan From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 20:56:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 52A2DD92 for ; Tue, 8 Oct 2013 20:56:49 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::3c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B8A8720C8 for ; Tue, 8 Oct 2013 20:56:48 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.5/8.14.5) with ESMTP id r98Kuk7D016349; Tue, 8 Oct 2013 16:56:46 -0400 (EDT) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at mail.pix.net Message-ID: <5254718E.2000504@pix.net> Date: Tue, 08 Oct 2013 16:56:46 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Cy Schubert Subject: Re: [Heads Up] RCS removed from base References: <201310082033.r98KXUgJ058127@slippy.cwsent.com> In-Reply-To: <201310082033.r98KXUgJ058127@slippy.cwsent.com> Content-Type: multipart/mixed; boundary="------------010106030200050207080903" Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 20:56:49 -0000 This is a multi-part message in MIME format. --------------010106030200050207080903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 10/8/13 4:33 PM, Cy Schubert wrote: > In message <52542687.7000100@pix.net>, Kurt Lidl writes: >> On 10/8/13, Julian Elischer wrote: >>> On 10/7/13 11:06 PM, Steve Kargl wrote: >>>> On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: >>>>> Hey all, >>>>> >>>>> RCS was removed from the base system in r256095. If you still want to >>>>> use RCS please install either devel/rcs or devel/rcs57. If not, be >>>>> sure to check out the alternatives (pun stolen and intended). >>>>> >>>> Perhaps, a note in src/UPDATING is appropriate? >>>> >>> ok so what is this, the secret cabal to make FreeBSD useless? >>> I'm ccing core as I believe this was not discussed enough in public >>> (in fact not discussed AT ALL in any forum I am watching) >>> and I officially request a backout of the removal of what I consider >>> to be core functionality. >>> >>> My usual way of doing things is on install to ci EVERYTHING in /etc >>> to get a snapsot right the way back to install. >>> >>> now I have to change things in /etc (and other places) BEFORE I can >>> check them in. >>> (i.e. get networking up and ports installed) >>> not a big thing but I believe that a lot of poeple use ci/co on /etc >>> becasue it is "just there" >>> >> >> +1 for keeping a RCS in base. I too use to maintain a bunch of >> files in /etc - I have for years and years. I don't particularly >> want the GPL'd version - I'd be happiest with the OpenRCS version >> (BSD-licensed) from OpenBSD. > > I've started work on a port (not that this was my highest priority but > received a private email that I may want to do this instead of rcs57). > Would the majority here rather have it in base? Just finished schlepping > the OpenBSD source to my laptop (the link to the OpenRCS site returns a TCP > RST). I don't mind either way. It's the groups's and the Project's call. > > I did the same thing this afternoon. I grabbed the latest rcs sources from the OpenBSD CVS server, and did a quick and dirty port to FreeBSD. There are some minor formatting diffs in the output of 'rlog', for example. Diff should be attached (well, stripped from the mailing list, but still available through the web interface to the mailing list). -Kurt --------------010106030200050207080903 Content-Type: text/plain; charset=UTF-8; x-mac-type="0"; x-mac-creator="0"; name="rcs.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rcs.diff" diff --git a/Makefile b/Makefile --- a/Makefile +++ b/Makefile @@ -12,9 +12,9 @@ LINKS= ${BINDIR}/rcs ${BINDIR}/ci ${BIND ${BINDIR}/rcs ${BINDIR}/rcsclean ${BINDIR}/rcs ${BINDIR}/rcsdiff \ ${BINDIR}/rcs ${BINDIR}/rcsmerge ${BINDIR}/rcs ${BINDIR}/rlog CPPFLAGS+=-I${.CURDIR} -CFLAGS+=-Wall +CFLAGS+=-Wall -I${.CURDIR} CFLAGS+=-Wstrict-prototypes -Wmissing-prototypes CFLAGS+=-Wmissing-declarations CFLAGS+=-Wshadow -Wpointer-arith -Wcast-qual CFLAGS+=-Wsign-compare diff --git a/ci.c b/ci.c --- a/ci.c +++ b/ci.c @@ -909,9 +909,9 @@ checkin_keywordscan(BUF *data, RCSNUM ** buf_append(buf, start, len); /* XXX - Not binary safe. */ buf_putc(buf, '\0'); - checkin_parsekeyword(buf_get(buf), rev, date, author, state); + checkin_parsekeyword((char *)buf_get(buf), rev, date, author, state); buf_free(buf); loopend:; } if (kwstr == NULL) diff --git a/date.y b/date.y --- a/date.y +++ b/date.y @@ -13,9 +13,9 @@ */ /* SUPPRESS 287 on yaccpar_sccsid *//* Unused static variable */ /* SUPPRESS 288 on yyerrlab *//* Label unused */ -#include +/* #include */ #include #include #include diff --git a/diff.c b/diff.c --- a/diff.c +++ b/diff.c @@ -426,10 +426,10 @@ files_differ(FILE *f1, FILE *f2) static void prepare(int i, FILE *fd, off_t filesize, int flags) { struct line *p; - int j, h; - size_t sz; + int h; + size_t j, sz; rewind(fd); sz = (filesize <= SIZE_MAX ? filesize : SIZE_MAX) / 25; @@ -1141,9 +1141,9 @@ asciifile(FILE *f) cnt = fread(buf, 1, sizeof(buf), f); return (memchr(buf, '\0', cnt) == NULL); } -#define begins_with(s, pre) (strncmp(s, pre, sizeof(pre)-1) == 0) +#define begins_with(s, pre) (strncmp((const char *)s, pre, sizeof(pre)-1) == 0) static char * match_function(const long *f, int pos, FILE *fp) { @@ -1160,9 +1160,9 @@ match_function(const long *f, int pos, F nc = sizeof(buf) - 1; nc = fread(buf, 1, nc, fp); if (nc > 0) { buf[nc] = '\0'; - buf[strcspn(buf, "\n")] = '\0'; + buf[strcspn((const char *)buf, "\n")] = '\0'; if (isalpha(buf[0]) || buf[0] == '_' || buf[0] == '$') { if (begins_with(buf, "private:")) { if (!state) state = " (private)"; @@ -1172,9 +1172,9 @@ match_function(const long *f, int pos, F } else if (begins_with(buf, "public:")) { if (!state) state = " (public)"; } else { - if (strlcpy(lastbuf, buf, + if (strlcpy(lastbuf, (const char *)buf, sizeof(lastbuf)) >= sizeof(lastbuf)) errx(1, "match_function: strlcpy"); lastmatchline = pos; diff --git a/diff3.c b/diff3.c --- a/diff3.c +++ b/diff3.c @@ -455,9 +455,9 @@ ed_patch_lines(struct rcs_lines *dlines, lp->l_line[lp->l_len - 1] = '\0'; /* len - 1 is NUL terminator so we use len - 2 for 'op' */ op = lp->l_line[lp->l_len - 2]; - start = (int)strtol(lp->l_line, &ep, 10); + start = (int)strtol((const char *)lp->l_line, &ep, 10); /* Restore the last byte of the buffer */ lp->l_line[lp->l_len - 1] = tmp; @@ -896,9 +896,10 @@ edit(struct diff *diff, int fdup, int j) /* regurgitate */ static int edscript(int n) { - int j, k; + int k; + size_t j; char block[BUFSIZ+1]; for (; n > 0; n--) { if (!oflag || !overlap[n]) diff --git a/rcs.c b/rcs.c --- a/rcs.c +++ b/rcs.c @@ -802,9 +802,9 @@ rcs_patch_lines(struct rcs_lines *dlines op = *(lp->l_line); /* NUL-terminate line buffer for strtol() safety. */ tmp = lp->l_line[lp->l_len - 1]; lp->l_line[lp->l_len - 1] = '\0'; - lineno = (int)strtol((lp->l_line + 1), &ep, 10); + lineno = (int)strtol((const char *)(lp->l_line + 1), &ep, 10); if (lineno > dlines->l_nblines || lineno < 0 || *ep != ' ') errx(1, "invalid line specification in RCS patch"); ep++; @@ -1050,9 +1050,9 @@ rcs_delta_stats(struct rcs_delta *rdp, i op = *(lp->l_line); /* NUL-terminate line buffer for strtol() safety. */ tmp = lp->l_line[lp->l_len - 1]; lp->l_line[lp->l_len - 1] = '\0'; - (void)strtol((lp->l_line + 1), &ep, 10); + (void)strtol((const char *)(lp->l_line + 1), &ep, 10); ep++; nbln = (int)strtol(ep, &ep, 10); /* Restore the last byte of the buffer */ lp->l_line[lp->l_len - 1] = tmp; diff --git a/rcs.h b/rcs.h --- a/rcs.h +++ b/rcs.h @@ -29,8 +29,9 @@ #include #include +#include #include "buf.h" #define RCS_DIFF_MAXARG 32 diff --git a/rcsparse.c b/rcsparse.c --- a/rcsparse.c +++ b/rcsparse.c @@ -29,8 +29,13 @@ #include "rcs.h" #include "rcsparse.h" #include "xmalloc.h" +#if !defined(_PW_NAME_LEN) +#include +#define _PW_NAME_LEN (MAXLOGNAME-1) +#endif + #define RCS_BUFSIZE 16384 #define RCS_BUFEXTSIZE 8192 /* RCS token types */ @@ -602,9 +607,9 @@ rcsparse_text(RCSFILE *rfp, struct rcs_p return (1); pdp->rp_delta->rd_tlen = pdp->rp_tlen - 1; if (pdp->rp_delta->rd_tlen == 0) { - pdp->rp_delta->rd_text = xstrdup(""); + pdp->rp_delta->rd_text = (u_char *) xstrdup(""); } else { pdp->rp_delta->rd_text = xmalloc(pdp->rp_delta->rd_tlen); memcpy(pdp->rp_delta->rd_text, pdp->rp_buf, pdp->rp_delta->rd_tlen); @@ -1219,9 +1224,9 @@ valid_login(char *login_name) /* The first character cannot be a hyphen */ if (*login_name == '-') return 0; - for (cp = login_name ; *cp ; cp++) { + for (cp = (u_char *)login_name ; *cp ; cp++) { /* We allow '$' as the last character for samba */ if (!isalnum(*cp) && *cp != '.' && *cp != '_' && *cp != '-' && !(*cp == '$' && *(cp + 1) == '\0')) { return 0; @@ -1237,9 +1242,9 @@ valid_commitid(char *commitid) { unsigned char *cp; /* A-Za-z0-9 */ - for (cp = commitid; *cp ; cp++) { + for (cp = (u_char *)commitid; *cp ; cp++) { if (!isalnum(*cp)) return 0; } if ((char *)cp - commitid > RCS_COMMITID_MAXLEN) diff --git a/rlog.c b/rlog.c --- a/rlog.c +++ b/rlog.c @@ -340,9 +340,9 @@ rlog_select_daterev(RCSFILE *rcsfile, ch static void rlog_file(const char *fname, RCSFILE *file) { char numb[RCS_REV_BUFSZ]; - u_int nrev; + int nrev; struct rcs_sym *sym; struct rcs_access *acp; struct rcs_delta *rdp; struct rcs_lock *lkp; @@ -355,10 +355,14 @@ rlog_file(const char *fname, RCSFILE *fi errx(1, "invalid date: %s", rlog_dates); } else nrev = file->rf_ndelta; +#if 0 if ((workfile = basename(fname)) == NULL) err(1, "basename"); +#else + workfile = (char *)fname; +#endif /* * In case they specified 'foo,v' as argument. */ diff --git a/xmalloc.c b/xmalloc.c --- a/xmalloc.c +++ b/xmalloc.c @@ -21,8 +21,12 @@ #include #include "xmalloc.h" +#if !defined(u_long) +#define u_long unsigned long +#endif + void * xmalloc(size_t size) { void *ptr; diff --git a/xmalloc.h b/xmalloc.h --- a/xmalloc.h +++ b/xmalloc.h @@ -18,8 +18,13 @@ #ifndef XMALLOC_H #define XMALLOC_H +#if !defined(SIZE_MAX) +#include +#define SIZE_MAX OFF_MAX +#endif + void *xmalloc(size_t); void *xcalloc(size_t, size_t); void *xrealloc(void *, size_t, size_t); void xfree(void *); --------------010106030200050207080903-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:14:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 22D77473 for ; Tue, 8 Oct 2013 21:14:43 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::3c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CEA5B22CF for ; Tue, 8 Oct 2013 21:14:42 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.5/8.14.5) with ESMTP id r98LEfGb016499 for ; Tue, 8 Oct 2013 17:14:41 -0400 (EDT) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at mail.pix.net Message-ID: <525475C0.4050205@pix.net> Date: Tue, 08 Oct 2013 17:14:40 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52547185.2000009@freebsd.org> In-Reply-To: <52547185.2000009@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:14:43 -0000 >>> 5. I think some substantial part of the MBR code will blow up if you are >>> reinitalizing a previously formatted disk (the bsdlabel will be retasted >>> and come back from the dead). >> Will not some combination of "gpart destroy -F" and (insert suggestion) work? > > Yes, that will work just fine. Actually, it will appear to work, and then viciously hurt (substitute more graphic verb for "hurt") you later, if you happen to repartition, and are using a geom-mirror for your swap space. At least if you manage to get your old geom and new geom on the same physical location of the disk. To be safe, you really need to either zero out the space used by geom before destroying the gpart label when it isn't in use, or run: gmirror deactivate NAME provider1 gmirror deactivate NAME provider2 -Kurt From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:21:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3F1B25FA; Tue, 8 Oct 2013 21:21:10 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F31892338; Tue, 8 Oct 2013 21:21:09 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r98LL4Vw011437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Oct 2013 14:21:04 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r98LL3Ep011436; Tue, 8 Oct 2013 14:21:03 -0700 (PDT) (envelope-from jmg) Date: Tue, 8 Oct 2013 14:21:03 -0700 From: John-Mark Gurney To: "Teske, Devin" Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Message-ID: <20131008212103.GJ56872@funkthat.com> Mail-Followup-To: "Teske, Devin" , Nathan Whitehorn , "" , Allan Jude References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC46255@LTCFISWMSGMB21.FNFIS.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC46255@LTCFISWMSGMB21.FNFIS.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 08 Oct 2013 14:21:04 -0700 (PDT) Cc: "" , Nathan Whitehorn , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:21:10 -0000 Devin Teske wrote this message on Tue, Oct 08, 2013 at 20:50 +0000: > > 2. Why are you using camcontrol? That is guaranteed not to work on > > non-CAM systems. You should use the GEOM ident string if you need an ID. > > I imagine we could get the info from many places, and to be honest, I never > knew about "diskinfo" until last week (but apparently it's been around since > 5.x days). > > The one place where I suspect camcontrol(8) usage is appropriate is the > mini "disk inspector" dialog. The camcontrol inquiry output is specifically > helpful if/when you're doing multipathing (and you need to identify which > da# devices are duplicates of the same device -- given Serial#). > > But I gather you mean for "disk description" in the device menu (for picking > text to go along with the device name). > > I'm open to using a different tool... or multiple tools. Do you think it would be > better to just stick to one tool? or to query a few? (which ones win-out?) diskinfo -v dumps the serial number for you under disk ident.. diskinfo gets it from geom and most geoms properly present that info now... or at least probably anyones support by cam will do it automatically... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:21:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5554C6FF for ; Tue, 8 Oct 2013 21:21:18 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::3c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 12653233E for ; Tue, 8 Oct 2013 21:21:17 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.5/8.14.5) with ESMTP id r98LLGSn016541 for ; Tue, 8 Oct 2013 17:21:16 -0400 (EDT) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at mail.pix.net Message-ID: <5254774C.8030204@pix.net> Date: Tue, 08 Oct 2013 17:21:16 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52546844.2010608@freebsd.org> In-Reply-To: <52546844.2010608@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:21:18 -0000 On 10/8/2013, Nathan Whitehorn wrote: > On 10/07/13 21:59, Allan Jude wrote: >> Devin Teske and I have been working on a big patch to bsdinstall to >> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >> sector gnop trick, and optional GELI encryption. We would like to commit >> this in time for 10.0-BETA1 so it needs some testing to work out any >> obvious bugs before we send it off to re@ to get it committed. >> >> It includes a single configuration menu that allows you to select all of >> the required details, including which drives to use (gets details from >> camcontrol, also includes an inspection utility that presents the >> detailed output of camcontrol inquiry/identify, and gpart show), what >> ZFS RAID level to use (taking in to consideration the selected number of >> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >> >> >> Additional, it includes some other changes to bsdinstall: >> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >> 3. Remove the dialog asking if you wish to enable crash dumps, this >> feature has been combined into the regular 'services to enable' dialog >> and enabled by default >> >> >> You can browse the patches here: >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >> >> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >> available compressed (48 MB) or uncompressed (211 MB): >> >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >> >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >> >> >> We look forward to your feedback >> > > Thanks for doing this! I had a few comments: > 1. ZFS is not bootable on all architectures. Could you adjust that menu > item to only display for i386, amd64, and (I think?) sparc64. Use uname > -m, not -p, for this. > 1a. The script is broken on sparc64 in any case, which uses VTOC8 > instead of GPT. > 2. Why are you using camcontrol? That is guaranteed not to work on > non-CAM systems. You should use the GEOM ident string if you need an ID. > 3. Any plans to integrate this into the regular partition editor? ZFS > support is important enough that I will definitely not get in the way, > even as a bolt-on, but it would be a shame for it to stay that way. The > editor is also designed for ZFS to be added. > 4. What is this gnop stuff for? > 5. I think some substantial part of the MBR code will blow up if you are > reinitalizing a previously formatted disk (the bsdlabel will be retasted > and come back from the dead). > -Nathan I wrote some support for adding ZFS to the partition editor a couple of months ago, around the time that 9.2 was branched. One of the biggest things that I have not done is integrate setting up a zfs mirror between any disks before creating the zpool. Nor did I do the gnop hack to create 4K disk blocks before creating the pool. I more or less changed the partedit program to take an argument when invoked with "ufs" (same as current behavior) or "zfs", which knows about zfs setup stuff. The hookup to the actual scripts was, shall we say, much less intrusive than what has been published here. I guess it's time to dig out the patches and make them available to others. -Kurt From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:25:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 359B888F for ; Tue, 8 Oct 2013 21:25:57 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 01456236C for ; Tue, 8 Oct 2013 21:25:56 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id uz6so942096obc.6 for ; Tue, 08 Oct 2013 14:25:56 -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=NgM37vtSziHGY+gXI2sn2sP/zOqZ3UpGgVwY9mna4LU=; b=OuqOfNCnkbE6dJkMCOnzjG/GxidB8bVxYQH5S2Ci4BqHeSyQf1reZBQGtLpDRe1vpo GnRYc+zTPQk1ewiptUjHaocN7jqlvGXGw7ai2rzb+C1q2nAG7Afu6Z0OgbJRQ1b8gCW9 HPxbFQyCdllKnlh/TefB/K7t0XSyK7/AVdgs32SMIf3hnPZbF7UoUWucso31Za9fP8sD BZS9VR6qHdrzS6gHKVjLgZTQGvt5NquhoB/EGvB1DK55CnvQfD0l060fiNBmg/W0TSnv 79Kx+wwDpULG11v6P4e6pu55IEPpnxw/tWeKld8fqntjC31QRC/rTbryRNCzUtZ2LJxg wK1g== MIME-Version: 1.0 X-Received: by 10.182.29.233 with SMTP id n9mr2869723obh.38.1381267556286; Tue, 08 Oct 2013 14:25:56 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Tue, 8 Oct 2013 14:25:56 -0700 (PDT) In-Reply-To: <525408CC.7000409@gmail.com> References: <525408CC.7000409@gmail.com> Date: Tue, 8 Oct 2013 17:25:56 -0400 Message-ID: Subject: Re: test From: Joe Nosay To: Alexander Panyushkin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:25:57 -0000 /div>
testwrote: > test > ______________________________**_________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@** > freebsd.org " > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:27:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A99519B6 for ; Tue, 8 Oct 2013 21:27:57 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 73A272388 for ; Tue, 8 Oct 2013 21:27:57 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id uz6so944887obc.6 for ; Tue, 08 Oct 2013 14:27:56 -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=w7YIeodIA/QxoHXuugnDLElM8qmydp/xfT3+feiOvvQ=; b=flw9SLSJtQqOULnggm+5mD/c/NX8ZKyrBP4ty3TyMzRc4xQ1l9fTRuD13oHLyQPAnV ozm77LWQR1bll6U6gpZj6Idz8mWBgVh3kKGKmfesolQpU9XUp+RlMMfYWooc61OPetDy +oZNeJMfl62CVwhBzvok4eYl6wv3yOQE6oedkxdNt6W1ZPrL5wbxm0qfdjaBu/68/V2s PUH7ynRFvBaJFBWMtkxwCdHUnGtWt3CnlDmAsnkbPYopAyFSLfYSg506gGn1rvvBkKhW kKQa5MG0cdZC9CgzkVYyFIOifOk7J1wAISs4x/X7cWRlJ6THCOu64DaxpGGBcAK5C7bI 5jkg== MIME-Version: 1.0 X-Received: by 10.182.225.162 with SMTP id rl2mr321633obc.72.1381267676796; Tue, 08 Oct 2013 14:27:56 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Tue, 8 Oct 2013 14:27:56 -0700 (PDT) In-Reply-To: <5253BE24.5030806@passap.ru> References: <5253BA63.4080102@passap.ru> <5253BE24.5030806@passap.ru> Date: Tue, 8 Oct 2013 17:27:56 -0400 Message-ID: Subject: Re: Running i386 CURRENT on an AMD64 platform:: CLang related From: Joe Nosay To: Boris Samorodov Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:27:57 -0000 Which has the latest source? On Tue, Oct 8, 2013 at 4:11 AM, Boris Samorodov wrote: > 08.10.2013 11:55, Boris Samorodov =D0=C9=DB=C5=D4: > > 08.10.2013 11:45, Joe Nosay =D0=C9=DB=C5=D4: > >> I've ran into compiling problems with some ports. World and kernel hav= e > not > >> yet been rebuilt. 10.x is a pre-APLHA release. > > > > Please, show diagnostic messages (of failing ports). > > OK, I've seen you have posted them to freebsd-ports@. > > >> Before I attempt to rebuild any of the system, has anyone else had any > >> problems related to building i386 on AMD64? > > Anyway, I'd say that it's a good idea to update your system since there > were many changes you may be interested in. > > -- > WBR, Boris Samorodov (bsam) > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:28:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 13365AC4 for ; Tue, 8 Oct 2013 21:28:16 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D89542394 for ; Tue, 8 Oct 2013 21:28:15 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MUD00200C1K4A00@smtpauth3.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Tue, 08 Oct 2013 16:28:13 -0500 (CDT) X-Spam-PmxInfo: Server=avs-3, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.10.8.212115, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (unknown [140.105.20.242]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MUD00MOUCYY1N10@smtpauth3.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Tue, 08 Oct 2013 16:28:12 -0500 (CDT) Message-id: <525478EA.8080207@freebsd.org> Date: Tue, 08 Oct 2013 23:28:10 +0200 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52546844.2010608@freebsd.org> <5254774C.8030204@pix.net> In-reply-to: <5254774C.8030204@pix.net> X-Enigmail-Version: 1.5.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:28:16 -0000 On 10/08/13 23:21, Kurt Lidl wrote: > > On 10/8/2013, Nathan Whitehorn wrote: >> On 10/07/13 21:59, Allan Jude wrote: >>> Devin Teske and I have been working on a big patch to bsdinstall to >>> implement installing on a ZFS pool. It supports both GPT and MBR, >>> the 4k >>> sector gnop trick, and optional GELI encryption. We would like to >>> commit >>> this in time for 10.0-BETA1 so it needs some testing to work out any >>> obvious bugs before we send it off to re@ to get it committed. >>> >>> It includes a single configuration menu that allows you to select >>> all of >>> the required details, including which drives to use (gets details from >>> camcontrol, also includes an inspection utility that presents the >>> detailed output of camcontrol inquiry/identify, and gpart show), what >>> ZFS RAID level to use (taking in to consideration the selected >>> number of >>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>> >>> >>> Additional, it includes some other changes to bsdinstall: >>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>> to no >>> 2. Replace the 3 separate dialogs to configure an ipv4 address with >>> just 1 >>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>> feature has been combined into the regular 'services to enable' dialog >>> and enabled by default >>> >>> >>> You can browse the patches here: >>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>> >>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>> available compressed (48 MB) or uncompressed (211 MB): >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>> >>> >>> We look forward to your feedback >>> >> >> Thanks for doing this! I had a few comments: >> 1. ZFS is not bootable on all architectures. Could you adjust that menu >> item to only display for i386, amd64, and (I think?) sparc64. Use uname >> -m, not -p, for this. >> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >> instead of GPT. >> 2. Why are you using camcontrol? That is guaranteed not to work on >> non-CAM systems. You should use the GEOM ident string if you need an ID. >> 3. Any plans to integrate this into the regular partition editor? ZFS >> support is important enough that I will definitely not get in the way, >> even as a bolt-on, but it would be a shame for it to stay that way. The >> editor is also designed for ZFS to be added. >> 4. What is this gnop stuff for? >> 5. I think some substantial part of the MBR code will blow up if you are >> reinitalizing a previously formatted disk (the bsdlabel will be retasted >> and come back from the dead). >> -Nathan > > I wrote some support for adding ZFS to the partition editor a couple of > months ago, around the time that 9.2 was branched. One of the biggest > things that I have not done is integrate setting up a zfs mirror between > any disks before creating the zpool. Nor did I do the gnop hack to > create 4K disk blocks before creating the pool. > > I more or less changed the partedit program to take an argument when > invoked with "ufs" (same as current behavior) or "zfs", which knows > about zfs setup stuff. The hookup to the actual scripts was, shall > we say, much less intrusive than what has been published here. > > I guess it's time to dig out the patches and make them available to > others. That would be great! The original idea was to have a "zfs_ops.c" to go with "gpart_ops.c" and have some fields in the disk item struct that said which to use. Not sure if that's ultimately workable, though. I can hack on it once the patches are there in any case. -Nathan From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:34:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 31B13CB9 for ; Tue, 8 Oct 2013 21:34:36 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id E1FB623FC for ; Tue, 8 Oct 2013 21:34:35 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:402a:9533:e91d:ef08]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPSA id 5D2B14AC2D; Wed, 9 Oct 2013 01:34:28 +0400 (MSK) Date: Wed, 9 Oct 2013 01:34:24 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1893399957.20131009013424@serebryakov.spb.ru> To: Daniel Nebdal Subject: Re: rcs In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Alfred Perlstein , Lyndon Nerenberg , Steve Kargl , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:34:36 -0000 Hello, Daniel. You wrote 8 =D0=BE=D0=BA=D1=82=D1=8F=D0=B1=D1=80=D1=8F 2013 =D0=B3., 19:40:= 23: DN> If they get the package repositories back up - which I assume will DN> happen before any official releases from 10 - it should just be "pkg DN> install rcs". As challenges go, that doesn't seem too bad? Topic starter mentioned, that assumption that everybody has online connection is completely wrong! As far as I understand, it was his main objection -- they have a lot of offline computers at work (something related to Security Theatre by DHS, but who am I to judge them?). And you again says about "pkg install rcs" which needs internet connection! --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:48:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D4BEB102; Tue, 8 Oct 2013 21:48:12 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2B09B24A0; Tue, 8 Oct 2013 21:48:12 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.7/8.14.7) with ESMTP id r98Lm97d071877; Tue, 8 Oct 2013 16:48:09 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.7/8.14.7/Submit) id r98Lm9ah071876; Tue, 8 Oct 2013 16:48:09 -0500 (CDT) (envelope-from brooks) Date: Tue, 8 Oct 2013 16:48:09 -0500 From: Brooks Davis To: Thomas Mueller Subject: Re: Unable to installworld after successful buildworld and buildkernel Message-ID: <20131008214809.GC69269@lor.one-eyed-alien.net> References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> <28.45.16944.64B74525@cdptpa-oedge02> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+g7M9IMkV8truYOl" Content-Disposition: inline In-Reply-To: <28.45.16944.64B74525@cdptpa-oedge02> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org, Brooks Davis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:48:12 -0000 --+g7M9IMkV8truYOl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 08, 2013 at 09:38:14PM +0000, Thomas Mueller wrote: > > To cross install FreeBSD on a system without the required users/groups > > you must either install them on the base system so that install and > > mtree can use them or use the -DDB_FROM_SRC option when running the > > installworld/installkernel/distribution targets. >=20 > -- Brooks >=20 > That worked for installworld, was apparently not needed subsequently for = installkernel. >=20 > But where is DB_FROM_SRC documented? I never saw it anywhere. UPDATING = file needs to be updated for installing FreeBSD on a partition where there = is no OS installed. >=20 It's documented in Makefile.inc1 where the less commonly used options are documented. It should be documented in the Handbook along with the process of cross installation and image creation. I disagree that UPDATING should document the process of installing to other locations. That would be a distraction from it's purpose of letting users update their systems. It's already far too complicated. -- Brooks --+g7M9IMkV8truYOl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFSVH2YXY6L6fI4GtQRAgRtAJ4i+SLz/BolE9YHvuFX55tn18uAxwCdGXya HhU/hTuuey/hyKVC3mg2Z7w= =c69F -----END PGP SIGNATURE----- --+g7M9IMkV8truYOl-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:38:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EF42DDFB for ; Tue, 8 Oct 2013 21:38:21 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id B9AC52423 for ; Tue, 8 Oct 2013 21:38:21 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:26605] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 28/45-16944-64B74525; Tue, 08 Oct 2013 21:38:15 +0000 Date: Tue, 08 Oct 2013 21:38:14 +0000 Message-ID: <28.45.16944.64B74525@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: Unable to installworld after successful buildworld and buildkernel References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-Mailman-Approved-At: Tue, 08 Oct 2013 21:57:57 +0000 Cc: Brooks Davis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:38:22 -0000 > To cross install FreeBSD on a system without the required users/groups > you must either install them on the base system so that install and > mtree can use them or use the -DDB_FROM_SRC option when running the > installworld/installkernel/distribution targets. -- Brooks That worked for installworld, was apparently not needed subsequently for installkernel. But where is DB_FROM_SRC documented? I never saw it anywhere. UPDATING file needs to be updated for installing FreeBSD on a partition where there is no OS installed. I haven't booted yet, will try several ways including grub2, and not including grub2. I installed sysutils/grub2 from FreeBSD ports, also sysutils/xorriso, necessary to run mkrescue. Tom From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 22:00:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3E3084AC for ; Tue, 8 Oct 2013 22:00:13 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 092232558 for ; Tue, 8 Oct 2013 22:00:12 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id wn1so1003435obc.13 for ; Tue, 08 Oct 2013 15:00:12 -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=Ae9uOY82GHP3Q7kcB8SZ6uoqILxKFeN2uccbZY6CmBM=; b=YVhImwUnIsywC3ByBI2zroOmB2OrU55XNsKNuNnIGBnRPEJOP4ef1lFXgTPLqF/D7p crseTPbrEpn2i6zCzhqLqJE3aZl93nWiv0RUFMsnc2yQb1o0jyocFOZ55oWaLsHbn95N Zty995P5ZWkXm/YUAwBa0Hcf7rhGXcfn4cHCvsmteoXruf4vyHdimVrxm9Ef5Ryfn2Lw 6zl0cG1y3/B/7knuZEXM1k8GbvH2n2r9HUwKF+S43So6eVdyyb9D1GRmhhujPzdcGOq0 cHD7fA4HzNeqgd/yIQbDwMsKfKcP3rG6ExFg9WAgUbn2U/BOJ0Db9HOFQnNa8NrKM4pB xbpA== MIME-Version: 1.0 X-Received: by 10.182.113.195 with SMTP id ja3mr2951103obb.46.1381269612287; Tue, 08 Oct 2013 15:00:12 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Tue, 8 Oct 2013 15:00:12 -0700 (PDT) In-Reply-To: References: <525408CC.7000409@gmail.com> Date: Tue, 8 Oct 2013 18:00:12 -0400 Message-ID: Subject: Re: test From: Joe Nosay To: Alexander Panyushkin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 22:00:13 -0000 What were you testing? On Tue, Oct 8, 2013 at 5:25 PM, Joe Nosay wrote: > /div>
test > > > On Tue, Oct 8, 2013 at 9:29 AM, Alexander Panyushkin wr= ote: > >> test >> ______________________________**_________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/**mailman/listinfo/freebsd-**current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@** >> freebsd.org " >> > > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 22:01:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AA3065CB for ; Tue, 8 Oct 2013 22:01:18 +0000 (UTC) (envelope-from ljboiler@gmail.com) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 798AD2593 for ; Tue, 8 Oct 2013 22:01:18 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id qd12so19910211ieb.8 for ; Tue, 08 Oct 2013 15:01:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=+J/KUJLTIAkTq6ZHMckeTneKhOpAmp5lxi/iYeu/wHI=; b=S4462MMr5Yk/sbFfvInavfcCe4SfPEnv+HhCYmoV68zglST9hNH1ExfrKFMbECvb4R BLbS/HgnYM4wOX1aHXxJA+GZrHmPEMFKiIM99E9a64h1VLSu6QjfkVS3ubSFSopQQB8v 5ApvFl9vN6dz8XNuCq9pW35Fx+uJq8KXL5+iK6TM5M9HZ6ZJ2ZolEYmKIgE6gOe+UtU4 jnRW3aURQ1n585kt84IGuGIg8hIxOBugFiAexh9sPvKM0d6uoSTZbRu7yVUMeRnnubpP wWwvddvPvvEK4MKIivDMTRd1wltvNYxlqQkYOB3K82EIbON7ellrtY+cEtv2YadTkuXb sY3A== X-Received: by 10.43.10.198 with SMTP id pb6mr2585411icb.40.1381269677755; Tue, 08 Oct 2013 15:01:17 -0700 (PDT) Received: from jmobile.jimmy.local (71-81-196-43.dhcp.stls.mo.charter.com. [71.81.196.43]) by mx.google.com with ESMTPSA id w4sm4470273igb.5.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Oct 2013 15:01:17 -0700 (PDT) Received: by jmobile.jimmy.local (sSMTP sendmail emulation); Tue, 08 Oct 2013 17:01:14 -0500 Date: Tue, 8 Oct 2013 17:01:14 -0500 From: Jimmy Kelley To: Nilton Jose Rizzo Subject: Re: Virtual box require LIBCXX Message-ID: <20131008220114.GA74373@jmobile.jimmy.localnet> References: <20131008141346.M55461@i805.com.br> <52543627.8040301@gmail.com> <20131008200010.M71841@i805.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131008200010.M71841@i805.com.br> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 22:01:18 -0000 On Tue, Oct 08, 2013 at 05:01:35PM -0300, Nilton Jose Rizzo wrote: > Em Tue, 08 Oct 2013 09:43:19 -0700, Eric L. Camachat escreveu > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > On 10/08/2013 07:17, Nilton Jose Rizzo wrote: > > > root@valfenda:/usr/ports/emulators/virtualbox-ose # kldload vboxdrv > > > root@valfenda:/usr/ports/emulators/virtualbox-ose # > > > > > > but whern I run it, the I got this error message: > > > rizzo@valfenda:~/src/Doutorado/visao/testes % VirtualBox > > > VirtualBox: Error -610 in supR3HardenedMainInitRuntime! > > > VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: > > > /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by > > > /usr/local/lib/virtualbox/VBoxRT.so not found > > > > > My box can be fixed by remove misc/compat8x package. > > In my box it was used by bootstrap jdk, look > > root@valfenda:/usr # pkg query %ro compat8x-amd64 > java/bootstrap-openjdk > root@valfenda:/usr # > > You don't use java? > > bootstrap-openjdk is only needed to BUILD openjdk. You can and should remove it after you have successfully built one of the openjdk packages (see java/bootstrap-openjdk/pkg-message). You can delete misc/compat8x after that. Jimmy From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 22:03:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AC8FB795 for ; Tue, 8 Oct 2013 22:03:13 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 73BF625B9 for ; Tue, 8 Oct 2013 22:03:13 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id wm4so987567obc.22 for ; Tue, 08 Oct 2013 15:03:12 -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=t4oy4MeCAI254JdOyqSvr4zWg2L6q8ieadhp+KFDU2U=; b=y6q7IftRdWeT8l7i+KQsMT6Sck8MddlUyygSV2KoKvc2amNk04BDXX2jR/lHlKqe+0 0F93ihycaMBZR/o5bODrCPf0X1CTdaPWK4ng8+X72pazpcZZBz76ZnrsAW3C1BwNCo/9 Z3WlEJAric8HwggcbKqzNNzA4fFYrWGsvCayVzffQi8WeH99h5Z1KRcUcYQoICRU8Om4 xLDjQ7kigYAJdmy077Wrj2/Y4CIh6ClfDjBxPNfVemhE1yBeq9A3DzRoL+5rMTiHQ7um 7IMX0rHLg70n2pAOXQ3vcLbLd2Y30V85EdVFwrmyEYaG0BxaWr08FIlOdqz0Co8EAh/2 NbNQ== MIME-Version: 1.0 X-Received: by 10.60.133.71 with SMTP id pa7mr2936031oeb.44.1381269792762; Tue, 08 Oct 2013 15:03:12 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Tue, 8 Oct 2013 15:03:12 -0700 (PDT) In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC4243D@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52539300.50305@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC415EA@LTCFISWMSGMB21.FNFIS.com> <52539C9F.9000400@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4243D@LTCFISWMSGMB21.FNFIS.com> Date: Tue, 8 Oct 2013 18:03:12 -0400 Message-ID: Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI From: Outback Dingo To: "Teske, Devin" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "" , Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 22:03:13 -0000 On Tue, Oct 8, 2013 at 5:21 AM, Teske, Devin wrote: > > On Oct 7, 2013, at 10:48 PM, Allan Jude wrote: > > > On 2013-10-08 01:11, Teske, Devin wrote: > >> On Oct 7, 2013, at 10:07 PM, Allan Jude wrote: > >> > >>> On 2013-10-07 15:59, Allan Jude wrote: > >>>> Devin Teske and I have been working on a big patch to bsdinstall to > >>>> implement installing on a ZFS pool. It supports both GPT and MBR, the > 4k > >>>> sector gnop trick, and optional GELI encryption. We would like to > commit > >>>> this in time for 10.0-BETA1 so it needs some testing to work out any > >>>> obvious bugs before we send it off to re@ to get it committed. > >>>> > >>>> It includes a single configuration menu that allows you to select all > of > >>>> the required details, including which drives to use (gets details from > >>>> camcontrol, also includes an inspection utility that presents the > >>>> detailed output of camcontrol inquiry/identify, and gpart show), what > >>>> ZFS RAID level to use (taking in to consideration the selected number > of > >>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. > >>>> > >>>> > >>>> Additional, it includes some other changes to bsdinstall: > >>>> 1. Change the default to the 'non-standard keyboard mapping' prompt > to no > >>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with > just 1 > >>>> 3. Remove the dialog asking if you wish to enable crash dumps, this > >>>> feature has been combined into the regular 'services to enable' dialog > >>>> and enabled by default > >>>> > >>>> > >>>> You can browse the patches here: > >>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ > >>>> > >>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, > >>>> available compressed (48 MB) or uncompressed (211 MB): > >>>> > >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz > >>>> > >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso > >>>> > >>>> > >>>> We look forward to your feedback > >>>> > >>> I've generated a new version of the ISO incorporating all of todays > >>> changes and moving up to 10.0-ALPHA5 > >>> It includes 2 patches from Warren Block, improving the keymap menu and > >>> indicating which network interfaces are wireless > >>> > >> Excellent. > >> > >> However, I have to say... you opened a can of worms by touching keymap. > >> > >> Eventually I plan to rewrite all of the scripts to the same format that > zfsboot > >> is using. I've already started rewriting keymap to the new format. Of > course, > >> this opened up another can of worms... the simple things like: > >> > >> DIALOG_OK > >> DIALOG_CANCEL > >> DIALOG_ESC > > > > Yeah, after having them, I felt a bit naked not having all of those > > 'constants' defined. > > > > The constants are now where they belong... `dialog.subr' > I also went through bsdconfig(8) with a fine-tooth comb and made use of the > new "constants" everywhere. > > I think it's a definite improvement. > > > > > Originally, all I had done was add --defaultno to the dialog command, > > but Warren's patch makes a lot of sense, allow the user to 'try' the new > > keymap before trying to do the rest of the install based on it. > > > > I rewrote warren's code into the stateful design and cleaned it up. > > > > >> I feel would be much better off in the `dialog.subr' module. So,... > I've started > >> peppering their usage everywhere in bsdconfig to make them "proper". > >> > >> That means they will just be transparent from including `dialog.subr'. > >> > > > > This is definately something that I think is a good idea, but my focus > > is on improving the usability and functionality of the installer in time > > for 10.0. Unifying everything to the bsdconfig style is slightly lower > > priority. Admittedly, the `bsdconfig networking` stuff is quite nice > > > > *nods* > > I took a look at the bsdinstall networking stuff, and I wanted to run away. > > Let's push that into the future. > > It wasn't too hard to get those global exit codes deployed, so I did that, > but like you say... I agree we should minimize "extra work" that will be > eventually slated for a future release. > -- > Devin > > > Just noticed that when trying to install root-on-zfs under xen it doesn't recognize the xbd0 virtual block device attached as ada0 so it skips the install screen and goes to configure networking > > >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz > >>> > >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso > >>> > >> Excellent, thanks! > > > > > > -- > > Allan Jude > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > _____________ > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete the > message and all copies; (ii) do not disclose, distribute or use the message > in any manner; and (iii) notify the sender immediately. In addition, please > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 22:04:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5FD718B4 for ; Tue, 8 Oct 2013 22:04:42 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 352C625CA for ; Tue, 8 Oct 2013 22:04:42 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r98M4ceW036677 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 8 Oct 2013 15:04:40 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs From: Lyndon Nerenberg In-Reply-To: Date: Tue, 8 Oct 2013 15:04:37 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <316CC412-A884-4E23-95D5-8565872FC844@orthanc.ca> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> To: Freddie Cash X-Mailer: Apple Mail (2.1510) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 22:04:42 -0000 On 2013-10-08, at 11:17 AM, Freddie Cash wrote: > =E2=80=8BI haven't kept up-to-date with all the developments, but = isn't this part of the bsdinstall/pkgng plan? Once the pkgng repos are = all available and populated, then bsdinstall will be able to install = packages from there during the install. And, isn't that part of the = plan for the DVD installers, to include an "installer repo" for off-line = installs? >=20 > IOW, theoretically, one could just download the 10.0 DVD, boot, = install the base, browse the repo on the DVD, select items to install, = install, reboot, and be finished. Without ever needing to touch an = Internet connection until after rebooting into FreeBSD, if it's even = needed at all. The big issue here is having access to the distfiles. We rarely, if = ever, install pre-compiled packages, because we don't know how they have = been configured. Quite often the packages are built with features or = dependencies we don't want, or are built without features we *do* want. = Instead, we configure and compile the port according to our = requirements, then build a package from that for internal use. For this to work in a disconnected environment, you need a ports tree = with a fully populated distfiles/ directory. The hack we came up with = was to put a FreeBSD host on the external network, on which we ran a = script once a week or so that would do the something like 'portsnap = fetch update; portsclean -DD; for in in /usr/ports/*/*; (cd $i && make = fetch); done'. That would give us a (mostly) populated /usr/ports/distfiles. We would = then rsync /usr/ports from the public machine onto a USB drive. That = drive would then be disconnected from the public machine and attached to = an internal file server, and its /usr/ports rsynced to the file server's = /usr/ports. Not pretty, but it got the job done. But that /usr/ports tree is way = too big to fit on a DVD. In fact, it might even be too large for a = BD-ROM. (I don't have access to the file server right now to check.) --lyndon From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 22:14:37 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1FF1ED1B; Tue, 8 Oct 2013 22:14:37 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E6BB22667; Tue, 8 Oct 2013 22:14:36 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r98MEZ04077646; Tue, 8 Oct 2013 18:14:35 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r98MEZIU077610; Tue, 8 Oct 2013 22:14:35 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 8 Oct 2013 22:14:35 GMT Message-Id: <201310082214.r98MEZIU077610@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on i386/i386 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 22:14:37 -0000 TB --- 2013-10-08 18:40:20 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-08 18:40:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-10-08 18:40:20 - starting HEAD tinderbox run for i386/i386 TB --- 2013-10-08 18:40:20 - cleaning the object tree TB --- 2013-10-08 18:40:20 - /usr/local/bin/svn stat /src TB --- 2013-10-08 18:40:25 - At svn revision 256158 TB --- 2013-10-08 18:40:26 - building world TB --- 2013-10-08 18:40:26 - CROSS_BUILD_TESTING=YES TB --- 2013-10-08 18:40:26 - MAKEOBJDIRPREFIX=/obj TB --- 2013-10-08 18:40:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-10-08 18:40:26 - SRCCONF=/dev/null TB --- 2013-10-08 18:40:26 - TARGET=i386 TB --- 2013-10-08 18:40:26 - TARGET_ARCH=i386 TB --- 2013-10-08 18:40:26 - TZ=UTC TB --- 2013-10-08 18:40:26 - __MAKE_CONF=/dev/null TB --- 2013-10-08 18:40:26 - cd /src TB --- 2013-10-08 18:40:26 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Tue Oct 8 18:40:35 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Oct 8 21:53:03 UTC 2013 TB --- 2013-10-08 21:53:03 - generating LINT kernel config TB --- 2013-10-08 21:53:03 - cd /src/sys/i386/conf TB --- 2013-10-08 21:53:03 - /usr/bin/make -B LINT TB --- 2013-10-08 21:53:03 - cd /src/sys/i386/conf TB --- 2013-10-08 21:53:03 - /usr/sbin/config -m LINT TB --- 2013-10-08 21:53:03 - building LINT kernel TB --- 2013-10-08 21:53:03 - CROSS_BUILD_TESTING=YES TB --- 2013-10-08 21:53:03 - MAKEOBJDIRPREFIX=/obj TB --- 2013-10-08 21:53:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-10-08 21:53:03 - SRCCONF=/dev/null TB --- 2013-10-08 21:53:03 - TARGET=i386 TB --- 2013-10-08 21:53:03 - TARGET_ARCH=i386 TB --- 2013-10-08 21:53:03 - TZ=UTC TB --- 2013-10-08 21:53:03 - __MAKE_CONF=/dev/null TB --- 2013-10-08 21:53:03 - cd /src TB --- 2013-10-08 21:53:03 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Oct 8 21:53:03 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] ^ /src/sys/geom/geom.h:357:8: error: expression result unused [-Werror,-Wunused-value] ("g_free(%p) of live object, type %d", ptr, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /src/sys/geom/geom.h:357:46: error: expression result unused [-Werror,-Wunused-value] ("g_free(%p) of live object, type %d", ptr, ^~~ 3 errors generated. *** Error code 1 Stop. bmake[1]: stopped in /obj/i386.i386/src/sys/LINT *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-10-08 22:14:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-10-08 22:14:35 - ERROR: failed to build LINT kernel TB --- 2013-10-08 22:14:35 - 10217.15 user 1976.65 system 12854.48 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 22:14:37 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D6E30D1C; Tue, 8 Oct 2013 22:14:37 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9DD582669; Tue, 8 Oct 2013 22:14:37 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id r98MEaSg030779 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 8 Oct 2013 17:14:36 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Tue, 8 Oct 2013 17:14:35 -0500 From: "Teske, Devin" To: Nathan Whitehorn Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxHPFPJPIP8ZCyUiSsjBzr2++AA== Date: Tue, 8 Oct 2013 22:14:35 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC46904@LTCFISWMSGMB21.FNFIS.com> References: <52546844.2010608@freebsd.org> <5254774C.8030204@pix.net> <525478EA.8080207@freebsd.org> In-Reply-To: <525478EA.8080207@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <8DD5143031AEDE4E93C15DC8D1DA17D9@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-08_08:2013-10-08,2013-10-08,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 22:14:38 -0000 On Oct 8, 2013, at 2:28 PM, Nathan Whitehorn wrote: > On 10/08/13 23:21, Kurt Lidl wrote: >>=20 >> On 10/8/2013, Nathan Whitehorn wrote: >>> On 10/07/13 21:59, Allan Jude wrote: >>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>> implement installing on a ZFS pool. It supports both GPT and MBR, >>>> the 4k >>>> sector gnop trick, and optional GELI encryption. We would like to >>>> commit >>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>> obvious bugs before we send it off to re@ to get it committed. >>>>=20 >>>> It includes a single configuration menu that allows you to select >>>> all of >>>> the required details, including which drives to use (gets details from >>>> camcontrol, also includes an inspection utility that presents the >>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>> ZFS RAID level to use (taking in to consideration the selected >>>> number of >>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>=20 >>>>=20 >>>> Additional, it includes some other changes to bsdinstall: >>>> 1. Change the default to the 'non-standard keyboard mapping' prompt >>>> to no >>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with >>>> just 1 >>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>> feature has been combined into the regular 'services to enable' dialog >>>> and enabled by default >>>>=20 >>>>=20 >>>> You can browse the patches here: >>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>=20 >>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>> available compressed (48 MB) or uncompressed (211 MB): >>>>=20 >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>=20 >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>=20 >>>>=20 >>>> We look forward to your feedback >>>>=20 >>>=20 >>> Thanks for doing this! I had a few comments: >>> 1. ZFS is not bootable on all architectures. Could you adjust that menu >>> item to only display for i386, amd64, and (I think?) sparc64. Use uname >>> -m, not -p, for this. >>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>> instead of GPT. >>> 2. Why are you using camcontrol? That is guaranteed not to work on >>> non-CAM systems. You should use the GEOM ident string if you need an ID. >>> 3. Any plans to integrate this into the regular partition editor? ZFS >>> support is important enough that I will definitely not get in the way, >>> even as a bolt-on, but it would be a shame for it to stay that way. The >>> editor is also designed for ZFS to be added. >>> 4. What is this gnop stuff for? >>> 5. I think some substantial part of the MBR code will blow up if you are >>> reinitalizing a previously formatted disk (the bsdlabel will be retasted >>> and come back from the dead). >>> -Nathan >>=20 >> I wrote some support for adding ZFS to the partition editor a couple of >> months ago, around the time that 9.2 was branched. One of the biggest >> things that I have not done is integrate setting up a zfs mirror between >> any disks before creating the zpool. Nor did I do the gnop hack to >> create 4K disk blocks before creating the pool. >>=20 >> I more or less changed the partedit program to take an argument when >> invoked with "ufs" (same as current behavior) or "zfs", which knows >> about zfs setup stuff. The hookup to the actual scripts was, shall >> we say, much less intrusive than what has been published here. >>=20 >> I guess it's time to dig out the patches and make them available to >> others. >=20 > That would be great! The original idea was to have a "zfs_ops.c" to go > with "gpart_ops.c" and have some fields in the disk item struct that > said which to use. Not sure if that's ultimately workable, though. I can > hack on it once the patches are there in any case. One of the options presented was to integrate ZFS knowledge into the partedit module. However, another approach that is not being spoken about is in the other direction: rewriting partedit to be in sh(1). What I'd like to see is the --treeview widget of dialog(1) "fixed" before such a transition is made, so the former option may be the best bet for now. For anyone that hasn't run the treeview or treeview2 samples in head/contrib/dialog/samples ... it's not anything we'd want to use to replace dialog(3) with. I've seen much nicer treeview implementations than what is in [c]dialog (currently we're using dialog-1.2-20130925 and the treeview for some reason incorporates a radio-button column which we do _not_ want for a disk partition layout menu). Of course, right now you're all looking at me like I'm crazy. Like a fox. There are real tangible benefits to rewriting the C code of partedit into shell syntax. The value-add is not just perceived. Some of the values obtained are: + Conflated namespace with singular API rather than having to learn how to script each individual blocking-utility which implements a unique method for scripting its input. + Top-down integration of new functionality. We're integrating ZFS right now and that's great that we have a fully-functional libzfs et. al. for doi= ng this stuff in C, but usually the command-line utility functionality precedes programatic functionality; it is in this spirit that we can integrate new functionalities into the installer purely from a base utility standpoint (i= f a utility exists to do something, we can integrate support for it rather than [potentially] having to wait until a C library surfaces). + Easier patching for custom deployments. The more code we write in C the more code has to be custom-built for in-house deployments (versus shell in-which you can patch-and-deploy). + More robust data. While it's true that most data (such as hardware descriptions of disk devices) is accessible from C libraries, we stand to gain more robust access to data if we are forced to get the information from a userland tool. Why? because then we make sure that the data is in some-form available from some tool (and not *only* available from a library requiring you to write a C program to get at that data). In other words, the shell approach promises to expose more central methods of accessing informative data *while* at the same time making it easier to bring that data into the installer. I could go on, but I digress. I think I'm making good arguments. I think also we should be mindful that arguments such as: "What if dialog(1) goes away?" (A: dialog(3) and dialog(1) have always been provided by the same vendor -- for multiple distributions from at least two generations of dialog functionality -- regardless of C-based or utility-based) and "But shell is nasty; slow; and not as powerful as C" (it depends in what context; the first is rhetoric, the second is only true for poor implement- ations, and the third may be true in some contexts, but I consider the answer to "how maintainable is it" to be a factor in the "power" of a language, so don't necessarily consider C to be more powerful than shell as the latter is as-or-more maintainable with fewer LoC and a higher return on investment; see previous [above] arguments). And to that, I say... bsdconfig(8) is 100% shell. Run it; Inspect it; .... Love it? --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 22:48:51 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BD61EBA5; Tue, 8 Oct 2013 22:48:51 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 90DBA285E; Tue, 8 Oct 2013 22:48:51 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r98MmisK061563; Tue, 8 Oct 2013 18:48:44 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r98MmiET061559; Tue, 8 Oct 2013 22:48:44 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 8 Oct 2013 22:48:44 GMT Message-Id: <201310082248.r98MmiET061559@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on amd64/amd64 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 22:48:51 -0000 TB --- 2013-10-08 18:40:20 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-10-08 18:40:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-10-08 18:40:20 - starting HEAD tinderbox run for amd64/amd64 TB --- 2013-10-08 18:40:20 - cleaning the object tree TB --- 2013-10-08 18:40:20 - /usr/local/bin/svn stat /src TB --- 2013-10-08 18:40:25 - At svn revision 256158 TB --- 2013-10-08 18:40:26 - building world TB --- 2013-10-08 18:40:26 - CROSS_BUILD_TESTING=YES TB --- 2013-10-08 18:40:26 - MAKEOBJDIRPREFIX=/obj TB --- 2013-10-08 18:40:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-10-08 18:40:26 - SRCCONF=/dev/null TB --- 2013-10-08 18:40:26 - TARGET=amd64 TB --- 2013-10-08 18:40:26 - TARGET_ARCH=amd64 TB --- 2013-10-08 18:40:26 - TZ=UTC TB --- 2013-10-08 18:40:26 - __MAKE_CONF=/dev/null TB --- 2013-10-08 18:40:26 - cd /src TB --- 2013-10-08 18:40:26 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Tue Oct 8 18:40:35 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Tue Oct 8 22:29:39 UTC 2013 TB --- 2013-10-08 22:29:39 - generating LINT kernel config TB --- 2013-10-08 22:29:39 - cd /src/sys/amd64/conf TB --- 2013-10-08 22:29:39 - /usr/bin/make -B LINT TB --- 2013-10-08 22:29:39 - cd /src/sys/amd64/conf TB --- 2013-10-08 22:29:39 - /usr/sbin/config -m LINT TB --- 2013-10-08 22:29:39 - building LINT kernel TB --- 2013-10-08 22:29:39 - CROSS_BUILD_TESTING=YES TB --- 2013-10-08 22:29:39 - MAKEOBJDIRPREFIX=/obj TB --- 2013-10-08 22:29:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-10-08 22:29:39 - SRCCONF=/dev/null TB --- 2013-10-08 22:29:39 - TARGET=amd64 TB --- 2013-10-08 22:29:39 - TARGET_ARCH=amd64 TB --- 2013-10-08 22:29:39 - TZ=UTC TB --- 2013-10-08 22:29:39 - __MAKE_CONF=/dev/null TB --- 2013-10-08 22:29:39 - cd /src TB --- 2013-10-08 22:29:39 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Oct 8 22:29:39 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] ^ /src/sys/geom/geom.h:357:8: error: expression result unused [-Werror,-Wunused-value] ("g_free(%p) of live object, type %d", ptr, ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /src/sys/geom/geom.h:357:46: error: expression result unused [-Werror,-Wunused-value] ("g_free(%p) of live object, type %d", ptr, ^~~ 3 errors generated. *** Error code 1 Stop. bmake[1]: stopped in /obj/amd64.amd64/src/sys/LINT *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-10-08 22:48:44 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-10-08 22:48:44 - ERROR: failed to build LINT kernel TB --- 2013-10-08 22:48:44 - 11597.42 user 2407.20 system 14903.60 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 23:13:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6B001507 for ; Tue, 8 Oct 2013 23:13:02 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 16D9E29CB for ; Tue, 8 Oct 2013 23:13:00 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 657031E704 for ; Tue, 8 Oct 2013 23:12:56 +0000 (UTC) Message-ID: <52549191.5010400@allanjude.com> Date: Tue, 08 Oct 2013 19:13:21 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> In-Reply-To: <52546844.2010608@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 23:13:02 -0000 On 2013-10-08 16:17, Nathan Whitehorn wrote: > On 10/07/13 21:59, Allan Jude wrote: >> Devin Teske and I have been working on a big patch to bsdinstall to >> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >> sector gnop trick, and optional GELI encryption. We would like to commit >> this in time for 10.0-BETA1 so it needs some testing to work out any >> obvious bugs before we send it off to re@ to get it committed. >> >> It includes a single configuration menu that allows you to select all of >> the required details, including which drives to use (gets details from >> camcontrol, also includes an inspection utility that presents the >> detailed output of camcontrol inquiry/identify, and gpart show), what >> ZFS RAID level to use (taking in to consideration the selected number of >> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >> >> >> Additional, it includes some other changes to bsdinstall: >> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >> 3. Remove the dialog asking if you wish to enable crash dumps, this >> feature has been combined into the regular 'services to enable' dialog >> and enabled by default >> >> >> You can browse the patches here: >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >> >> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >> available compressed (48 MB) or uncompressed (211 MB): >> >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >> >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >> >> >> We look forward to your feedback >> > Thanks for doing this! I had a few comments: > 1. ZFS is not bootable on all architectures. Could you adjust that menu > item to only display for i386, amd64, and (I think?) sparc64. Use uname > -m, not -p, for this. I had not considered that, I'll make that change > 1a. The script is broken on sparc64 in any case, which uses VTOC8 > instead of GPT. I'll disable sparc64 as well > 2. Why are you using camcontrol? That is guaranteed not to work on > non-CAM systems. You should use the GEOM ident string if you need an ID. The GEOM ident string doesn't do enough to help the user identify which drive is which. More data is not exposed anywhere that I could find What we really need, is dev.ada.0.desc% like we have for network interfaces and a slew of other devices. GEOM data is great, but it is not exposed in a shell friendly way any place that I could find, other than the sysctl with DOT and XML data. > 3. Any plans to integrate this into the regular partition editor? ZFS > support is important enough that I will definitely not get in the way, > even as a bolt-on, but it would be a shame for it to stay that way. The > editor is also designed for ZFS to be added. I am a sysadmin, not a programmer. I can't write C. Most people deploying servers can't write C. I agree with Devin Teske, if everything was in shell it would be a lot more usable for non-developers, who probably make up the majority of people who deploy FreeBSD. > 4. What is this gnop stuff for? yeah, we align the partitions and the blocks to ensure optimal performance on 'advanced format' drives, there is no real downside for older drives, and it saves you from headaches in the future. > 5. I think some substantial part of the MBR code will blow up if you are > reinitalizing a previously formatted disk (the bsdlabel will be retasted > and come back from the dead). We try to do what we can here, including creating a fresh GPT and MBR and blowing them away to ensure that anything left over is really dead. We also use zpool labelclear, which doesn't check if there ever was a ZFS label, it just blindly overwrites the spots where the label would go. I'll add some additional napalm to ensure there are no zombie partitions. > -Nathan > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 23:23:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 54393861 for ; Tue, 8 Oct 2013 23:23:21 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (unknown [IPv6:2620:64:0:1:223:7dff:fea2:c8f2]) by mx1.freebsd.org (Postfix) with ESMTP id 3D80C2A4E for ; Tue, 8 Oct 2013 23:23:21 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id D5C032AA4F2; Tue, 8 Oct 2013 17:23:19 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id E6A231CC17; Tue, 8 Oct 2013 18:22:51 -0500 (EST) Date: Tue, 8 Oct 2013 18:22:51 -0500 From: Diane Bruce To: Kurt Lidl Subject: Re: [Heads Up] RCS removed from base Message-ID: <20131008232251.GA47296@night.db.net> References: <201310082033.r98KXUgJ058127@slippy.cwsent.com> <5254718E.2000504@pix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5254718E.2000504@pix.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 23:23:21 -0000 On Tue, Oct 08, 2013 at 04:56:46PM -0400, Kurt Lidl wrote: > On 10/8/13 4:33 PM, Cy Schubert wrote: > > In message <52542687.7000100@pix.net>, Kurt Lidl writes: > >> On 10/8/13, Julian Elischer wrote: > >>> On 10/7/13 11:06 PM, Steve Kargl wrote: > >>>> On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: > >>>>> Hey all, Did it this morning http://people.FreeBSD.org/~db/rcs.tgz Or http://www.db.net/~db/rcs.tgz It's up to core@ to decide what to do. - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 00:13:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C0CAE317 for ; Wed, 9 Oct 2013 00:13:10 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) by mx1.freebsd.org (Postfix) with ESMTP id 784392C8F for ; Wed, 9 Oct 2013 00:13:10 +0000 (UTC) X-AuditID: 1209190e-b7f828e0000009cf-ef-52549e63bd4b Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id EF.2C.02511.36E94525; Tue, 8 Oct 2013 20:08:03 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id r99082Qx015093; Tue, 8 Oct 2013 20:08:03 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r99080nN008332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Oct 2013 20:08:02 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r99080AC029497; Tue, 8 Oct 2013 20:08:00 -0400 (EDT) Date: Tue, 8 Oct 2013 20:07:59 -0400 (EDT) From: Benjamin Kaduk To: "Julian H. Stacey" Subject: Re: FreeBSD 10.0-ALPHA4 now available In-Reply-To: <201310071327.r97DRl9W053828@fire.js.berklix.net> Message-ID: References: <201310071327.r97DRl9W053828@fire.js.berklix.net> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUixCmqrJs8LyTIYN9PPYs5bz4wWexZ+4bd gcnj341jbB4zPs1nCWCK4rJJSc3JLEst0rdL4Mo4+LyPqWAVd8WK38fYGxg7ObsYOTkkBEwk zp3qY4WwxSQu3FvP1sXIxSEksI9RYmLTFnYIZwOjxIfTi1ggnINMEj/3TmcGaRESqJe4+f8m mM0ioCXxYwZEnE1ARWLmm41sILaIgIbEq0OPwGxmAXmJ/1cuM4HYwgL6EvuPnGEHsTkF7CRe vH4JFucVcJRYf+oaK8R8W4k9r16wgNiiAjoSq/dPYYGoEZQ4OfMJC8RMS4lzf66zTWAUnIUk NQtJagEj0ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdY73czBK91JTSTYzgUJXk28H49aDSIUYB DkYlHt4H/CFBQqyJZcWVuYcYJTmYlER5Z/cChfiS8lMqMxKLM+KLSnNSiw8xSnAwK4nw7poD lONNSaysSi3Kh0lJc7AoifPe5LAPEhJITyxJzU5NLUgtgsnKcHAoSfCqzAVqFCxKTU+tSMvM KUFIM3FwggznARq+B2x4cUFibnFmOkT+FKOilDivC0izAEgiozQPrheWSl4xigO9IszrDFLF A0xDcN2vgAYzAQ3WZQ8EGVySiJCSamCc9fB2OnevX9kXxtX1s1WYJCdfzRYXniV0aM2Bbxtd Csvty8KX9SadP30z+HfWeek7t0Xisiy3rJ4yT1ni0O5bAhu/T3DPXV3R2GfzxfH6g6cKoj/N Hq2YGb74EUNm0gXvk3vTWCfoHk7RK8pZvPRNmV9PJdOaQ3v9OEIWaSmxSv8xk9x0wtdWiaU4 I9FQi7moOBEAMPhI1AADAAA= Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 00:13:10 -0000 [-re] On Mon, 7 Oct 2013, Julian H. Stacey wrote: >> The fourth ALPHA build of the 10.0-RELEASE release cycle is now available >> on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and >> sparc64 architectures. >> >> Note: Due to build issues within the head/ branch, ALPHA3 ISO builds >> were skipped. >> >> The 10.0-ALPHA4 builds correlate to svn revision r255933 of the head/ >> branch. > > (After zapping boot on an adjacent parition & repairing,) > I avoided installer, & booted another partition, mounted > FreeBSD-10.0-ALPHA4-amd64-memstick.img & tar'ed to empty partition > > 10.0-ALPHA4 runs, built & ran new generic kernel & ports X11 etc. :-) > > I had supposed an Alpha /usr/src would compile even if it broke at run time. > Not so, 10.0-ALPHA4 src/ is broken (with & without obj & depend). > cd /usr/src ; make -i install > killed the system. To avoid killing, I hacked Makefiles, list below. > Reinstalled & survived. I thought buildworld+installworld was the documented way to build everything. Do you have other documentation I should look at? > I'll try with a newer current later, but Alpha4 src/ needs fixing. > > cd /usr/src ; cp /dev/null ~/tmp/`uname -r`.diffs > foreach i ( `find . -name Makefile\*.pre_jhs | sort`) > echo >> ~/tmp/`uname -r`.diffs > diff -c $i `dirname $i`/`basename $i .pre_jhs` >> ~/tmp/`uname -r`.diffs BTW, unified diffs are preferred. -Ben From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 00:34:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 59729BE3 for ; Wed, 9 Oct 2013 00:34:35 +0000 (UTC) (envelope-from eric.camachat@gmail.com) Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 317892D92 for ; Wed, 9 Oct 2013 00:34:35 +0000 (UTC) Received: by mail-pd0-f176.google.com with SMTP id q10so84314pdj.21 for ; Tue, 08 Oct 2013 17:34:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Ks+spoB4QpFo1BOmbmxwMxcpgJSY7GBh8JHNwBZm7Ws=; b=LXo+WFiNmM1jk+nQSYfk+Wfqdngk2rZObxpW5xNFHHIOtCGwl6QbiCmMKxiw0Ywim6 h8Uf9sY82bC2X9T7TS42u1h8qJXFxQ/dvEaHDBC5wEnnzI7ixaszvXNiQMy8Pq3OAYUU lKZeRAN6RC+MV1bQaqnbaimnfRTIrFHZ9huSqlHjTQDOdZZ1A02vlUuTPdPHzZW1Pb9E XzUURiYTyquGuILPAZVuuPOk0F1Rn/JCxUAzF6EPmhe7wiQSBSpNanJl5IJ09joo8cxX C6sv0vCh9ej7nIOcdAD/gXpljwbMaBScUNts0um6WeesBKmAZd/f5rr/5RCYLGRTq1AS dHbw== X-Received: by 10.66.156.9 with SMTP id wa9mr6451653pab.151.1381278874897; Tue, 08 Oct 2013 17:34:34 -0700 (PDT) Received: from ?IPv6:2601:9:3000:34c:a288:b4ff:fec2:e5d0? ([2601:9:3000:34c:a288:b4ff:fec2:e5d0]) by mx.google.com with ESMTPSA id xn12sm50478786pac.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Oct 2013 17:34:34 -0700 (PDT) Message-ID: <5254A499.1050409@gmail.com> Date: Tue, 08 Oct 2013 17:34:33 -0700 From: "Eric L. Camachat" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Virtual box require LIBCXX References: <20131008141346.M55461@i805.com.br> <52543627.8040301@gmail.com> <20131008200010.M71841@i805.com.br> <20131008220114.GA74373@jmobile.jimmy.localnet> In-Reply-To: <20131008220114.GA74373@jmobile.jimmy.localnet> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 00:34:35 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 10/08/2013 15:01, Jimmy Kelley wrote: > On Tue, Oct 08, 2013 at 05:01:35PM -0300, Nilton Jose Rizzo wrote: >> Em Tue, 08 Oct 2013 09:43:19 -0700, Eric L. Camachat escreveu >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA256 >>> >>> On 10/08/2013 07:17, Nilton Jose Rizzo wrote: >>>> root@valfenda:/usr/ports/emulators/virtualbox-ose # kldload vboxdrv >>>> root@valfenda:/usr/ports/emulators/virtualbox-ose # >>>> >>>> but whern I run it, the I got this error message: >>>> rizzo@valfenda:~/src/Doutorado/visao/testes % VirtualBox >>>> VirtualBox: Error -610 in supR3HardenedMainInitRuntime! >>>> VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: >>>> /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by >>>> /usr/local/lib/virtualbox/VBoxRT.so not found >>>> >>> My box can be fixed by remove misc/compat8x package. >> >> In my box it was used by bootstrap jdk, look >> >> root@valfenda:/usr # pkg query %ro compat8x-amd64 >> java/bootstrap-openjdk >> root@valfenda:/usr # >> >> You don't use java? >> >> > > bootstrap-openjdk is only needed to BUILD openjdk. You can and > should remove it after you have successfully built one of the > openjdk packages (see java/bootstrap-openjdk/pkg-message). > You can delete misc/compat8x after that. > Yes, I have to remove it when every time re-build openjdk Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlJUpJkACgkQSfBQu3oOwYy2oQD/RmsDCLHwn+X5TXyqWvoDPc3M fnwKs779NaDHE8+kVF0BAJ2oMHgvQ6X1Fmhkor9PF0pRlPu586gzsupcJU4sed/a =0MHP -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 00:47:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E92B7E7E for ; Wed, 9 Oct 2013 00:47:00 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6F3372E16 for ; Wed, 9 Oct 2013 00:47:00 +0000 (UTC) Received: from mart.js.berklix.net (pD9FBE0EC.dip0.t-ipconnect.de [217.251.224.236]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r990kvMN079521; Wed, 9 Oct 2013 00:46:58 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r990kico066610; Wed, 9 Oct 2013 02:46:44 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r990kWrn085206; Wed, 9 Oct 2013 02:46:38 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310090046.r990kWrn085206@fire.js.berklix.net> To: Benjamin Kaduk Subject: Re: FreeBSD 10.0-ALPHA4 now available From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 08 Oct 2013 20:07:59 EDT." Date: Wed, 09 Oct 2013 02:46:32 +0200 Sender: jhs@berklix.com Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 00:47:01 -0000 Hi, Reference: > From: Benjamin Kaduk > Date: Tue, 8 Oct 2013 20:07:59 -0400 (EDT) Benjamin Kaduk wrote: > [-re] > > On Mon, 7 Oct 2013, Julian H. Stacey wrote: > > >> The fourth ALPHA build of the 10.0-RELEASE release cycle is now available > >> on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and > >> sparc64 architectures. > >> > >> Note: Due to build issues within the head/ branch, ALPHA3 ISO builds > >> were skipped. > >> > >> The 10.0-ALPHA4 builds correlate to svn revision r255933 of the head/ > >> branch. > > > > (After zapping boot on an adjacent parition & repairing,) > > I avoided installer, & booted another partition, mounted > > FreeBSD-10.0-ALPHA4-amd64-memstick.img & tar'ed to empty partition > > > > 10.0-ALPHA4 runs, built & ran new generic kernel & ports X11 etc. :-) > > > > I had supposed an Alpha /usr/src would compile even if it broke at run time. > > Not so, 10.0-ALPHA4 src/ is broken (with & without obj & depend). > > cd /usr/src ; make -i install > > killed the system. To avoid killing, I hacked Makefiles, list below. > > Reinstalled & survived. > > I thought buildworld+installworld was the documented way to build > everything. Yes, for an evolving current that's true (I'd perhaps forgotten, as I've been away from current & was tired) but in the case of a release (& Alpha4 is intended for a release after fixes) I expect binaries on media to exactly match the identical src they are presumably made from, so as a simple sanity & machine hardware & file corruption etc check I always do the same simple make with any release. If re@ are not shipping a matched set of bins built from src theyre shipped with, I'd be very suprised, & would want to know. > Do you have other documentation I should look at? Sorry, not sure what you want ? > > I'll try with a newer current later, but Alpha4 src/ needs fixing. > > > > cd /usr/src ; cp /dev/null ~/tmp/`uname -r`.diffs > > foreach i ( `find . -name Makefile\*.pre_jhs | sort`) > > echo >> ~/tmp/`uname -r`.diffs > > diff -c $i `dirname $i`/`basename $i .pre_jhs` >> ~/tmp/`uname -r`.diffs > > BTW, unified diffs are preferred. I find context diffs easier to read, & these were just to read, to show where ALPHA4 is broken. I do not want those patches stoed to apply, that would be wrong, they are just temporary to show where ALPHA4 will commit suicide, untill re@ fixes underlying breakages. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 00:55:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5B9CFCE for ; Wed, 9 Oct 2013 00:55:25 +0000 (UTC) (envelope-from rizzo@i805.com.br) Received: from server.i805.com.br (mailhost.i805.com.br [72.52.97.105]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 84A652E6D for ; Wed, 9 Oct 2013 00:55:25 +0000 (UTC) Received: from i805.com.br (localhost [127.0.0.1]) by server.i805.com.br (8.14.6/8.14.5) with ESMTP id r990tMkc093054; Tue, 8 Oct 2013 21:55:22 -0300 (BRT) (envelope-from rizzo@i805.com.br) From: "Nilton Jose Rizzo" To: "Eric L. Camachat" Subject: Re: Virtual box require LIBCXX Date: Tue, 8 Oct 2013 21:55:22 -0300 Message-Id: <20131009005224.M50625@i805.com.br> In-Reply-To: <5254A499.1050409@gmail.com> References: <20131008141346.M55461@i805.com.br> <52543627.8040301@gmail.com> <20131008200010.M71841@i805.com.br> <20131008220114.GA74373@jmobile.jimmy.localnet> <5254A499.1050409@gmail.com> X-Mailer: OpenWebMail 3.00_beta4 20121104 671 X-OriginatingIP: 179.218.87.141 (rizzo) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on server.i805.com.br Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 00:55:25 -0000 Em Tue, 08 Oct 2013 17:34:33 -0700, Eric L. Camachat escreveu > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 10/08/2013 15:01, Jimmy Kelley wrote: > > On Tue, Oct 08, 2013 at 05:01:35PM -0300, Nilton Jose Rizzo wrote: > >> Em Tue, 08 Oct 2013 09:43:19 -0700, Eric L. Camachat escreveu > >>> -----BEGIN PGP SIGNED MESSAGE----- > >>> Hash: SHA256 > >>> > >>> On 10/08/2013 07:17, Nilton Jose Rizzo wrote: > >>>> root@valfenda:/usr/ports/emulators/virtualbox-ose # kldload vboxdrv > >>>> root@valfenda:/usr/ports/emulators/virtualbox-ose # > >>>> > >>>> but whern I run it, the I got this error message: > >>>> rizzo@valfenda:~/src/Doutorado/visao/testes % VirtualBox > >>>> VirtualBox: Error -610 in supR3HardenedMainInitRuntime! > >>>> VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",) failed: > >>>> /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by > >>>> /usr/local/lib/virtualbox/VBoxRT.so not found > >>>> > >>> My box can be fixed by remove misc/compat8x package. > >> > >> In my box it was used by bootstrap jdk, look > >> > >> root@valfenda:/usr # pkg query %ro compat8x-amd64 > >> java/bootstrap-openjdk > >> root@valfenda:/usr # > >> > >> You don't use java? > >> > >> > > > > bootstrap-openjdk is only needed to BUILD openjdk. You can and > > should remove it after you have successfully built one of the > > openjdk packages (see java/bootstrap-openjdk/pkg-message). > > You can delete misc/compat8x after that. > > > Yes, I have to remove it when every time re-build openjdk > > Eric Sorry folks, it's my fault, because I didn't read this message about this ports. Thankx again Rizzo > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (FreeBSD) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iF4EAREIAAYFAlJUpJkACgkQSfBQu3oOwYy2oQD/RmsDCLHwn+X5TXyqWvoDPc3M > fnwKs779NaDHE8+kVF0BAJ2oMHgvQ6X1Fmhkor9PF0pRlPu586gzsupcJU4sed/a > =0MHP > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 01:01:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AEB18243; Wed, 9 Oct 2013 01:01:28 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8479E2EC5; Wed, 9 Oct 2013 01:01:28 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id D87558235; Wed, 9 Oct 2013 01:01:26 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us D87558235 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 8 Oct 2013 21:01:24 -0400 From: Glen Barber To: "Julian H. Stacey" Subject: Re: FreeBSD 10.0-ALPHA4 now available Message-ID: <20131009010124.GA630@glenbarber.us> References: <201310090046.r990kWrn085206@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <201310090046.r990kWrn085206@fire.js.berklix.net> X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org, Benjamin Kaduk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 01:01:28 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 09, 2013 at 02:46:32AM +0200, Julian H. Stacey wrote: > > > I had supposed an Alpha /usr/src would compile even if it broke at ru= n time. > > > Not so, 10.0-ALPHA4 src/ is broken (with & without obj & depend). > > > cd /usr/src ; make -i install > >=20 > > I thought buildworld+installworld was the documented way to build=20 > > everything. >=20 >=20 > Yes, for an evolving current that's true=20 No. That is the documented procedure for any installworld. Why are you running 'make -i install' from /usr/src without buildworld? > If re@ are not shipping a matched set of bins built from src theyre > shipped with, I'd be very suprised, & would want to know. >=20 This is never the case. Glen --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSVKrkAAoJELls3eqvi17QQvoQALgIfwkYGy7BdIAmpqmbTrtx a1AesILPjAyt9ZqRAlW2LKCKowxJwnIdrZu/7ajx9zMUU0QIvs8TFnFa/zXmaTbW NQ7p2bYSlToAtUhp9BDGORKSjW3xZrwcoaL11C4Hc0voYBs3lNRfejjKF9ed7V4Q bm6+hQUU5hCyF/llS9lXDPJlaP31PfRtqsd9sPgFH5rsZMg9WMnLLMq2CI2nHhio vaq1Tc+tmF/kmyl9YV7EFnY+qJtRONHtKi57Y96WuZxkvvcDi/LRxAapgOLbf7Tz yhKFEvcs/aiRDDBEZbC6y6Czw0NpKH1x2c9LQm50d+EcA9eoprseNMnurvxyIDik DhiLua16DH1/8/Sp84LT5sFgUmEm4DlaRABKWwbbYNJpZU0ifYurtHz8s2A1yHPR /lpRSxzcojLGwld8vcLyP1VuaO2yi626fFPPa4fgEqA0Wdaxoj77rUuOJ//Z2bKQ 8zrlgupLZ7H4DFD03P7ZTqCah82dUuYOFER4jw19CxA1Dpj3V4rHwd9nbe+RAbr8 9jZVNPYvOte/94sa41l2u+w2degcurk37ooSdxzblQT8HfXIeK5NvXyvBYHpb0O8 /Uug5Nrzu+HABxxcDW+x6FEG/U+yYGcYAm29RVP6Rkkj/XuvXgYY4IlAwDKmBqxh 4DJzA03yST/tt6TyVsLd =LnMP -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 02:30:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6E12EDAF for ; Wed, 9 Oct 2013 02:30:31 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 34C802275 for ; Wed, 9 Oct 2013 02:30:31 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id uz6so220323obc.34 for ; Tue, 08 Oct 2013 19:30:30 -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=7kiPymjiyjnWo9DHCFksbtWNtfLiXcrrbrCIta3gl/w=; b=vQmMUxbxbImSfW/UQMKiESB8x4Cr1BYCYTkGGGygvv8rNlWu9K3GjoMJCxyN1uBvuF O8DhCSUi5c/IBTropTk4dh2fEYv7TxiOK+ALRip6fNwIB8daieLk2X+B5rSyiW2QDtkG rEX7GGUFgmN3MEVI8KUT+YU9Ol74ZuGakHHtsDZKtFlljsir8MiWHQ/5M/gV7V2bS1cr MFz562SuLYpRSr02gkQe0p4dRUrNzHNchi/lyTyFh+Zi7QjMZnU8t46+C8EwuUBuuEWs zGmZjnzdLm1KzMsE8OyUcs+ZlfrqzyrVqOZAXf5j8m6sft+rjLSIktp9G8PVKp959wn0 5RSQ== MIME-Version: 1.0 X-Received: by 10.182.142.229 with SMTP id rz5mr3728235obb.12.1381285830468; Tue, 08 Oct 2013 19:30:30 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Tue, 8 Oct 2013 19:30:30 -0700 (PDT) In-Reply-To: <52549191.5010400@allanjude.com> References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> Date: Tue, 8 Oct 2013 22:30:30 -0400 Message-ID: Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI From: Outback Dingo To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 02:30:31 -0000 On Tue, Oct 8, 2013 at 7:13 PM, Allan Jude wrote: > On 2013-10-08 16:17, Nathan Whitehorn wrote: > > On 10/07/13 21:59, Allan Jude wrote: > >> Devin Teske and I have been working on a big patch to bsdinstall to > >> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k > >> sector gnop trick, and optional GELI encryption. We would like to commit > >> this in time for 10.0-BETA1 so it needs some testing to work out any > >> obvious bugs before we send it off to re@ to get it committed. > >> > >> It includes a single configuration menu that allows you to select all of > >> the required details, including which drives to use (gets details from > >> camcontrol, also includes an inspection utility that presents the > >> detailed output of camcontrol inquiry/identify, and gpart show), what > >> ZFS RAID level to use (taking in to consideration the selected number of > >> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. > >> > >> > >> Additional, it includes some other changes to bsdinstall: > >> 1. Change the default to the 'non-standard keyboard mapping' prompt to > no > >> 2. Replace the 3 separate dialogs to configure an ipv4 address with > just 1 > >> 3. Remove the dialog asking if you wish to enable crash dumps, this > >> feature has been combined into the regular 'services to enable' dialog > >> and enabled by default > >> > >> > >> You can browse the patches here: > >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ > >> > >> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, > >> available compressed (48 MB) or uncompressed (211 MB): > >> > >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz > >> > >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso > >> > >> > >> We look forward to your feedback > >> > > Thanks for doing this! I had a few comments: > > 1. ZFS is not bootable on all architectures. Could you adjust that menu > > item to only display for i386, amd64, and (I think?) sparc64. Use uname > > -m, not -p, for this. > I had not considered that, I'll make that change > > > 1a. The script is broken on sparc64 in any case, which uses VTOC8 > > instead of GPT. > I'll disable sparc64 as well > > > 2. Why are you using camcontrol? That is guaranteed not to work on > > non-CAM systems. You should use the GEOM ident string if you need an ID. > The GEOM ident string doesn't do enough to help the user identify which > drive is which. > More data is not exposed anywhere that I could find > > What we really need, is dev.ada.0.desc% like we have for network > interfaces and a slew of other devices. GEOM data is great, but it is > not exposed in a shell friendly way any place that I could find, other > than the sysctl with DOT and XML data. > > > 3. Any plans to integrate this into the regular partition editor? ZFS > > support is important enough that I will definitely not get in the way, > > even as a bolt-on, but it would be a shame for it to stay that way. The > > editor is also designed for ZFS to be added. > I am a sysadmin, not a programmer. I can't write C. Most people > deploying servers can't write C. I agree with Devin Teske, if everything > was in shell it would be a lot more usable for non-developers, who > probably make up the majority of people who deploy FreeBSD. > > > 4. What is this gnop stuff for? > yeah, we align the partitions and the blocks to ensure optimal > performance on 'advanced format' drives, there is no real downside for > older drives, and it saves you from headaches in the future. > > > 5. I think some substantial part of the MBR code will blow up if you are > > reinitalizing a previously formatted disk (the bsdlabel will be retasted > > and come back from the dead). > We try to do what we can here, including creating a fresh GPT and MBR > and blowing them away to ensure that anything left over is really dead. > We also use zpool labelclear, which doesn't check if there ever was a > ZFS label, it just blindly overwrites the spots where the label would go. > I'll add some additional napalm to ensure there are no zombie partitions. > > > -Nathan > I can now confirm with the latest patches from 1.5 hours ago applied i can now install and boot into a zfs-on-root system under XEN...... now you seriously ROCK! great work ....... and thanks dmesg Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-ALPHA5 #1 r256169M: Wed Oct 9 01:03:43 EDT 2013 dingo@current.optimcloud.com:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 XEN: Hypervisor version 4.3 detected. CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.38-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x306a9 Family = 0x6 Model = 0x3a Stepping = 9 Features=0x1783fbff Features2=0xffb82203 AMD Features=0x28100800 AMD Features2=0x1 Standard Extended Features=0x200 real memory = 2147483648 (2048 MB) avail memory = 2048917504 (1954 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-47 on motherboard random: initialized kbd1 at kbdmux0 xen_et0: on motherboard Event timer "XENTIMER" frequency 1000000000 Hz quality 950 Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc260-0xc26f at device 1.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 uhci0: port 0xc240-0xc25f irq 23 at device 1.2 on pci0 usbus0: controller did not stop usbus0 on uhci0 pci0: at device 1.3 (no driver attached) vgapci0: mem 0xf0000000-0xf1ffffff,0xf3020000-0xf3020fff at device 2.0 on pci0 xenpci0: port 0xc000-0xc0ff mem 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 xenstore0: on xenpci0 pcm0: port 0xc100-0xc1ff irq 36 at device 5.0 on pci0 pcm0: atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fdc0: No FDOUT register! ppc0: cannot reserve I/O port range ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 10.000 msec usbus0: 12Mbps Full Speed USB v1.0 xenbusb_front0: on xenstore0 ugen0.1: at usbus0 uhub0: on usbus0 xn0: at device/vif/0 on xenbusb_front0 xn0: Ethernet address: 00:16:3e:56:4c:9d xenbusb_back0: on xenstore0 xctrl0: on xenstore0 xn0: backend features: feature-sg feature-gso-tcp4 xbd0: 16384MB at device/vbd/768 on xenbusb_front0 xbd0: attaching as ada0 xbd0: features: flush, write_barrier xbd0: synchronize cache commands enabled. Netvsc initializing... Timecounter "TSC-low" frequency 1247190583 Hz quality 800 Root mount waiting for: usbus0 uhub0: 2 ports with 2 removable, self powered Trying to mount root from zfs:zroot/bootenv/default []... zpool status pool: zroot state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 gptid/0986ae37-3089-11e3-9a23-00163e564c9d ONLINE 0 0 0 errors: No known data errors uname -a FreeBSD zfsroot.xxxxxxxxx.com 10.0-ALPHA5 FreeBSD 10.0-ALPHA5 #1 r256169M: Wed Oct 9 01:03:43 EDT 2013 xxxxxx@current.xxxxxxx.com:/usr/obj/usr/src/sys/GENERIC amd64 > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > > -- > Allan Jude > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 02:32:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 674ADED5 for ; Wed, 9 Oct 2013 02:32:35 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2D7342290 for ; Wed, 9 Oct 2013 02:32:35 +0000 (UTC) Received: by mail-ob0-f174.google.com with SMTP id wm4so224649obc.5 for ; Tue, 08 Oct 2013 19:32:34 -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=MjDT0AWLYX5N5Sqfl7kjVnEcnFns3zpAC2FGBuMl9x4=; b=KPVd1ffI2ro5Ev0JUk+gho8chnDkse1VQEPBInQ5NQcLvhxmf5is0kFV2mHxpcVRiV vMifsKy/CWL7PWBEnEuqJRHutIhIKKkeM1PWO5I3mHLZ/3S76VZzy/vCadiTM6gi1ngi zOE1onjRJW4glhqs4rb40IoBMUW6C9+ybWHa/qVm52O+6e34sMEzPROWeXcIa8Kc+xzZ I4DmDXMbU6uunkIzTUl2nVYugGlqbvRWEv36rXPdQzDSak4bTrf1BJeDVYp5EdQoQhOA YXXPmk0+z/hwn49ioW0i3x0eKAe2sCOd63xAE7v+URECyChL7k6jehkJP4ZRAZkPsZPX aEig== MIME-Version: 1.0 X-Received: by 10.60.62.101 with SMTP id x5mr3786550oer.24.1381285954136; Tue, 08 Oct 2013 19:32:34 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Tue, 8 Oct 2013 19:32:34 -0700 (PDT) In-Reply-To: References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> Date: Tue, 8 Oct 2013 22:32:34 -0400 Message-ID: Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI From: Outback Dingo To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 02:32:35 -0000 On Tue, Oct 8, 2013 at 10:30 PM, Outback Dingo wrote: > > > > On Tue, Oct 8, 2013 at 7:13 PM, Allan Jude wrote: > >> On 2013-10-08 16:17, Nathan Whitehorn wrote: >> > On 10/07/13 21:59, Allan Jude wrote: >> >> Devin Teske and I have been working on a big patch to bsdinstall to >> >> implement installing on a ZFS pool. It supports both GPT and MBR, the >> 4k >> >> sector gnop trick, and optional GELI encryption. We would like to >> commit >> >> this in time for 10.0-BETA1 so it needs some testing to work out any >> >> obvious bugs before we send it off to re@ to get it committed. >> >> >> >> It includes a single configuration menu that allows you to select all >> of >> >> the required details, including which drives to use (gets details from >> >> camcontrol, also includes an inspection utility that presents the >> >> detailed output of camcontrol inquiry/identify, and gpart show), what >> >> ZFS RAID level to use (taking in to consideration the selected number >> of >> >> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >> >> >> >> >> >> Additional, it includes some other changes to bsdinstall: >> >> 1. Change the default to the 'non-standard keyboard mapping' prompt to >> no >> >> 2. Replace the 3 separate dialogs to configure an ipv4 address with >> just 1 >> >> 3. Remove the dialog asking if you wish to enable crash dumps, this >> >> feature has been combined into the regular 'services to enable' dialog >> >> and enabled by default >> >> >> >> >> >> You can browse the patches here: >> >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >> >> >> >> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >> >> available compressed (48 MB) or uncompressed (211 MB): >> >> >> >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >> >> >> >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >> >> >> >> >> >> We look forward to your feedback >> >> >> > Thanks for doing this! I had a few comments: >> > 1. ZFS is not bootable on all architectures. Could you adjust that menu >> > item to only display for i386, amd64, and (I think?) sparc64. Use uname >> > -m, not -p, for this. >> I had not considered that, I'll make that change >> >> > 1a. The script is broken on sparc64 in any case, which uses VTOC8 >> > instead of GPT. >> I'll disable sparc64 as well >> >> > 2. Why are you using camcontrol? That is guaranteed not to work on >> > non-CAM systems. You should use the GEOM ident string if you need an ID. >> The GEOM ident string doesn't do enough to help the user identify which >> drive is which. >> More data is not exposed anywhere that I could find >> >> What we really need, is dev.ada.0.desc% like we have for network >> interfaces and a slew of other devices. GEOM data is great, but it is >> not exposed in a shell friendly way any place that I could find, other >> than the sysctl with DOT and XML data. >> >> > 3. Any plans to integrate this into the regular partition editor? ZFS >> > support is important enough that I will definitely not get in the way, >> > even as a bolt-on, but it would be a shame for it to stay that way. The >> > editor is also designed for ZFS to be added. >> I am a sysadmin, not a programmer. I can't write C. Most people >> deploying servers can't write C. I agree with Devin Teske, if everything >> was in shell it would be a lot more usable for non-developers, who >> probably make up the majority of people who deploy FreeBSD. >> >> > 4. What is this gnop stuff for? >> yeah, we align the partitions and the blocks to ensure optimal >> performance on 'advanced format' drives, there is no real downside for >> older drives, and it saves you from headaches in the future. >> >> > 5. I think some substantial part of the MBR code will blow up if you are >> > reinitalizing a previously formatted disk (the bsdlabel will be retasted >> > and come back from the dead). >> We try to do what we can here, including creating a fresh GPT and MBR >> and blowing them away to ensure that anything left over is really dead. >> We also use zpool labelclear, which doesn't check if there ever was a >> ZFS label, it just blindly overwrites the spots where the label would go. >> I'll add some additional napalm to ensure there are no zombie partitions. >> >> > -Nathan >> > > I can now confirm with the latest patches from 1.5 hours ago applied i can > now install and boot > into a zfs-on-root system under XEN...... now you seriously ROCK! great > work ....... and thanks > > dmesg > Copyright (c) 1992-2013 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 10.0-ALPHA5 #1 r256169M: Wed Oct 9 01:03:43 EDT 2013 > dingo@current.optimcloud.com:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 > XEN: Hypervisor version 4.3 detected. > CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.38-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x306a9 Family = 0x6 Model = 0x3a > Stepping = 9 > > Features=0x1783fbff > > Features2=0xffb82203 > AMD Features=0x28100800 > AMD Features2=0x1 > Standard Extended Features=0x200 > real memory = 2147483648 (2048 MB) > avail memory = 2048917504 (1954 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: > ioapic0: Changing APIC ID to 1 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-47 on motherboard > random: initialized > kbd1 at kbdmux0 > xen_et0: on motherboard > Event timer "XENTIMER" frequency 1000000000 Hz quality 950 > Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > cpu0: on acpi0 > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: port 0x70-0x71 irq 8 on acpi0 > Event timer "RTC" frequency 32768 Hz quality 0 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > isab0: at device 1.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc260-0xc26f at device 1.1 on pci0 > ata0: at channel 0 on atapci0 > ata1: at channel 1 on atapci0 > uhci0: port 0xc240-0xc25f irq 23 at > device 1.2 on pci0 > usbus0: controller did not stop > usbus0 on uhci0 > pci0: at device 1.3 (no driver attached) > vgapci0: mem > 0xf0000000-0xf1ffffff,0xf3020000-0xf3020fff at device 2.0 on pci0 > xenpci0: port 0xc000-0xc0ff mem > 0xf2000000-0xf2ffffff irq 28 at device 3.0 on pci0 > xenstore0: on xenpci0 > pcm0: port 0xc100-0xc1ff irq 36 at device 5.0 on pci0 > pcm0: > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > fdc0: No FDOUT register! > ppc0: cannot reserve I/O port range > ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is > present; > to enable, add "vfs.zfs.prefetch_disable=0" to > /boot/loader.conf. > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > Timecounters tick every 10.000 msec > usbus0: 12Mbps Full Speed USB v1.0 > xenbusb_front0: on xenstore0 > ugen0.1: at usbus0 > uhub0: on usbus0 > xn0: at device/vif/0 on xenbusb_front0 > xn0: Ethernet address: 00:16:3e:56:4c:9d > xenbusb_back0: on xenstore0 > xctrl0: on xenstore0 > xn0: backend features: feature-sg feature-gso-tcp4 > xbd0: 16384MB at device/vbd/768 on xenbusb_front0 > xbd0: attaching as ada0 > xbd0: features: flush, write_barrier > xbd0: synchronize cache commands enabled. > Netvsc initializing... Timecounter "TSC-low" frequency 1247190583 Hz > quality 800 > Root mount waiting for: usbus0 > uhub0: 2 ports with 2 removable, self powered > Trying to mount root from zfs:zroot/bootenv/default []... > > zpool status > pool: zroot > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE > CKSUM > zroot ONLINE 0 0 > 0 > gptid/0986ae37-3089-11e3-9a23-00163e564c9d ONLINE 0 0 > 0 > > errors: No known data errors > > uname -a > FreeBSD zfsroot.xxxxxxxxx.com 10.0-ALPHA5 FreeBSD 10.0-ALPHA5 #1 > r256169M: Wed Oct 9 01:03:43 EDT 2013 xxxxxx@current.xxxxxxx.com:/usr/obj/usr/src/sys/GENERIC > amd64 > I did just notice this....... permissions on sys drwxrwxr-x 57 1000 1000 58 Feb 22 2008 sys and super sweet layout df -h Filesystem Size Used Avail Capacity Mounted on zroot/bootenv/default 12G 778M 12G 6% / devfs 1.0K 1.0K 0B 100% /dev zroot/tmp 12G 176K 12G 0% /tmp zroot/usr/home 12G 184K 12G 0% /usr/home zroot/usr/local 12G 144K 12G 0% /usr/local zroot/usr/obj 12G 144K 12G 0% /usr/obj zroot/usr/ports 12G 811M 12G 6% /usr/ports zroot/usr/ports/distfiles 12G 144K 12G 0% /usr/ports/distfiles zroot/usr/ports/packages 12G 144K 12G 0% /usr/ports/packages zroot/usr/src 12G 547M 12G 4% /usr/src zroot/var 12G 456K 12G 0% /var zroot/var/crash 12G 148K 12G 0% /var/crash zroot/var/db 12G 240K 12G 0% /var/db zroot/var/db/pkg 12G 144K 12G 0% /var/db/pkg zroot/var/empty 12G 144K 12G 0% /var/empty zroot/var/log 12G 196K 12G 0% /var/log zroot/var/mail 12G 144K 12G 0% /var/mail zroot/var/run 12G 236K 12G 0% /var/run zroot/var/tmp 12G 152K 12G 0% /var/tmp > > > > > >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to " >> freebsd-current-unsubscribe@freebsd.org" >> >> >> -- >> Allan Jude >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> > > From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 03:46:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9E5CAFFF; Wed, 9 Oct 2013 03:46:06 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 514A82691; Wed, 9 Oct 2013 03:46:06 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id x13so601922ief.3 for ; Tue, 08 Oct 2013 20:46:05 -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=XtPZjy/1Kwi1+I8ftpQBlTONEY+W3VhrfZUhref5kuQ=; b=FFBMfBWMWGvwMn2N9AI8c0husmATBnDS/SBcR7X13cddLZayBKLCHvS6JO77VZZbQg yZ4T5p68EirtdDmLOIudABIAyEpugh43Fu+qXGZjAbt/VPhJNCiAyJEXeDoPJEU/ruHt wiTwp+8VhV/wk/eQVQm+EvU+BZ1OunJOHvhuy0IvgcUxTLYTiY3FtrFMN3laXQLw+7Zp kMdjRg7lng2WRouuhNbsID82+oAR+OQEA8vJEan7DAR8GUaxpwXntQJX9gD3wFc8Pef1 P2yJdNfxyeK1VRrh5kEEOdLp40vedc08Oi3V2FAn/CN9iyhAsc2fvhW6G66tfpsOVLWQ gLVQ== MIME-Version: 1.0 X-Received: by 10.50.147.65 with SMTP id ti1mr690562igb.12.1381290365554; Tue, 08 Oct 2013 20:46:05 -0700 (PDT) Received: by 10.64.18.14 with HTTP; Tue, 8 Oct 2013 20:46:05 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Oct 2013 11:46:05 +0800 Message-ID: Subject: Re: Changes to UART ns8250 From: Ganbold Tsagaankhuu To: Zbigniew Bodek Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" , freebsd-current@freebsd.org, freebsd-embedded@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 03:46:06 -0000 On Tue, Oct 8, 2013 at 9:58 AM, Ganbold Tsagaankhuu wrote: > Zbigniew, > > > On Tue, Oct 8, 2013 at 3:54 AM, Zbigniew Bodek wrote: > >> Hello. >> >> I would like to present a patch for ns8250 serial that I would like to >> commit in the near future (if there are no objections). >> >> The patch is fixing newest DesignWare UART with busy detection. >> During frequency divisors configuration when UART is busy transferring or >> receiving data, line control register manipulation will not take effect. >> Therefore, we will not set divisor latch access bit and we will corrupt >> LCR >> instead of configuring divisors. >> It is necessary to wait until UART finishes all transfers to proceed with >> the configuration. >> >> This was detected on Armada XP as UART fails on this issue 100/100 >> attempts. >> The patch was tested by kevlo@ and me and it works on our Armada XP - >> based >> systems. >> >> Please send your comment or remarks if there are any. >> > > I'm trying your patch on r254983. > Tried on 2 boards (Cubieboard2 (Allwinner A20 SoC - dual Cortex A7) and > Radxa Rock (Rockchip RK3188 - Quad Cortex A9)). Both seem to have some sort > of DesignWare uart. > > 1. It works fine on Cubieboard2. Uart dmesg is like: > > uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 33 on simplebus0 > > uart0: console (115200,n,8,1) > > 2. No any printing on screen in case of Radxa Rock. Without your patch > uart dmesg is like: > > uart0: <16650 or compatible> mem 0x20064000-0x200643ff irq 68 on > simplebus0 > uart0: console (115200,n,8,1) > > In case of RK3188 SoC, it seems booting FreeBSD kernel seems very fragile, > not sure yet what is causing the problem. > Even with stock ns8250 some version later than r254983 didn't show/print > anything on serial console few days ago. > Only thing so far I know is this r254983 (with some patch) works in my > case on RK3188 SoC based board. > Zbigniew, Just tried again your patch on RK30xx board. I was able to see boot messages on screen. This uart detected as: ... uart0: <16650 or compatible> mem 0x20064000-0x200643ff irq 68 on simplebus0 uart0: console (115200,n,8,1) uart0: fast interrupt ... Can you show me your uart detection log? It seems this DW uart of RK30xx is different than DW uart of A10/A20. Boot simply stops printing "start_init: trying /sbin/init". thanks, Ganbold > > thanks, > > Ganbold > > > > >> >> Best regards >> Zbigniew Bodek >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> > > From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 03:48:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6AE9B21C for ; Wed, 9 Oct 2013 03:48:42 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 303D526AF for ; Wed, 9 Oct 2013 03:48:41 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 620A91E9CE for ; Wed, 9 Oct 2013 03:48:39 +0000 (UTC) Message-ID: <5254D231.5070803@allanjude.com> Date: Tue, 08 Oct 2013 23:49:05 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> In-Reply-To: <52531295.7090700@allanjude.com> Content-Type: multipart/mixed; boundary="------------040306070903020902050706" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 03:48:42 -0000 This is a multi-part message in MIME format. --------------040306070903020902050706 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 2013-10-07 15:59, Allan Jude wrote: > Devin Teske and I have been working on a big patch to bsdinstall to > implement installing on a ZFS pool. It supports both GPT and MBR, the 4k > sector gnop trick, and optional GELI encryption. We would like to commit > this in time for 10.0-BETA1 so it needs some testing to work out any > obvious bugs before we send it off to re@ to get it committed. > > It includes a single configuration menu that allows you to select all of > the required details, including which drives to use (gets details from > camcontrol, also includes an inspection utility that presents the > detailed output of camcontrol inquiry/identify, and gpart show), what > ZFS RAID level to use (taking in to consideration the selected number of > drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. > > > Additional, it includes some other changes to bsdinstall: > 1. Change the default to the 'non-standard keyboard mapping' prompt to no > 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 > 3. Remove the dialog asking if you wish to enable crash dumps, this > feature has been combined into the regular 'services to enable' dialog > and enabled by default > > > You can browse the patches here: > http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ > > I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, > available compressed (48 MB) or uncompressed (211 MB): > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso > > > We look forward to your feedback > We've made more improvements, including corporating most all of the feedback we've gotten so far Outstanding items: 1. Apply the changes to ipv6 config the way we did ipv4 2. improve disk identification (model info and serial # instead of one or the other) 3. Include a helpful message before the GELI step where you have to enter your password many times, the user will be less confused if it is explained why they have to enter their password 3 * number of disks times 4. Validate vdev type choice inside the vdev type menu, and warn the user if they have made an invalid selection, so they can add more disks or chance their selection, without having to try to start the installation first 5. Whatever else you guys find wrong tonight I generated new test images, and attached the patch (which got REALLY big when Devin Teske decided to fix "all of the things": http://www.allanjude.com/bsd/zfsbootonly.2013-10-08.iso.xz http://www.allanjude.com/bsd/zfsbootonly.2013-10-08.iso -- Allan Jude --------------040306070903020902050706 Content-Type: text/plain; charset=windows-1252; name="zfsboot.2013-10-08.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="zfsboot.2013-10-08.patch" Index: usr.sbin/bsdconfig/bsdconfig =================================================================== --- usr.sbin/bsdconfig/bsdconfig (revision 256169) +++ usr.sbin/bsdconfig/bsdconfig (working copy) @@ -300,7 +300,7 @@ dialog_menu_main() f_dialog_menutag_store "$menu_choice" # Only update default-item on success - [ $retval -eq 0 ] && f_dialog_default_store "$menu_choice" + [ $retval -eq $DIALOG_OK ] && f_dialog_default_store "$menu_choice" return $retval } @@ -396,11 +396,10 @@ while :; do f_dialog_menutag_fetch mtag f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" - if [ $retval -eq 2 ]; then - # The Help button was pressed + if [ $retval -eq $DIALOG_HELP ]; then f_show_help "$BSDCONFIG_HELPFILE" continue - elif [ $retval -ne 0 ]; then + elif [ $retval -ne $DIALOG_OK ]; then f_die fi Index: usr.sbin/bsdconfig/console/ttys =================================================================== --- usr.sbin/bsdconfig/console/ttys (revision 256169) +++ usr.sbin/bsdconfig/console/ttys (working copy) @@ -92,7 +92,7 @@ dialog_menu_main() local retval=$? f_dialog_menutag_store -s "$menu_choice" - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then local item item=$( eval f_dialog_menutag2item \ \"\$menu_choice\" $menu_list ) Index: usr.sbin/bsdconfig/mouse/enable =================================================================== --- usr.sbin/bsdconfig/mouse/enable (revision 256169) +++ usr.sbin/bsdconfig/mouse/enable (working copy) @@ -102,7 +102,7 @@ f_dialog_title_restore # Stop the mouse daemon # f_quietly vidcontrol -m off -if [ $retval -eq $SUCCESS ]; then +if [ $retval -eq $DIALOG_OK ]; then f_sysrc_set moused_enable "YES" || f_die ln -fs /dev/sysmouse /dev/mouse || f_die # backwards compat else Index: usr.sbin/bsdconfig/networking/devices =================================================================== --- usr.sbin/bsdconfig/networking/devices (revision 256169) +++ usr.sbin/bsdconfig/networking/devices (working copy) @@ -148,7 +148,7 @@ while :; do "$interface" "$_ipaddr" "$_netmask" "$_options" $dhcp # Return to root menu if above returns success - [ $? -eq $SUCCESS ] && break + [ $? -eq $DIALOG_OK ] && break done exit $SUCCESS Index: usr.sbin/bsdconfig/networking/share/device.subr =================================================================== --- usr.sbin/bsdconfig/networking/share/device.subr (revision 256169) +++ usr.sbin/bsdconfig/networking/share/device.subr (working copy) @@ -125,7 +125,7 @@ f_dialog_menu_netdev() ) if [ ! "$interfaces" ]; then f_show_msg "$msg_no_network_interfaces" - return $FAILURE + return $DIALOG_CANCEL fi # @@ -242,12 +242,10 @@ f_dialog_menu_netdev_edit() local retval=$? f_dialog_data_sanitize tag - if [ $retval -eq 2 ]; then - # The Help button was pressed + if [ $retval -eq $DIALOG_HELP ]; then f_show_help "$TCP_HELPFILE" continue - elif [ $retval -ne $SUCCESS ]; then - # "Cancel" was chosen (-1) or ESC was pressed (255) + elif [ $retval -ne $DIALOG_OK ]; then return $retval else # Only update default-item on success @@ -298,7 +296,7 @@ f_dialog_menu_netdev_edit() ) retval=$? trap 'interrupt' SIGINT - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then dhcp=1 ipaddr=$( f_ifconfig_inet $interface ) netmask=$( f_ifconfig_netmask $interface ) @@ -312,11 +310,11 @@ f_dialog_menu_netdev_edit() fi ;; 3\ *) f_dialog_input_ipaddr "$interface" "$ipaddr" - [ $? -eq $SUCCESS ] && dhcp= ;; + [ $? -eq $DIALOG_OK ] && dhcp= ;; 4\ *) f_dialog_input_netmask "$interface" "$netmask" - [ $? -eq $SUCCESS -a "$_netmask" ] && dhcp= ;; + [ $? -eq $DIALOG_OK -a "$_netmask" ] && dhcp= ;; 5\ *) f_dialog_menu_media_options "$interface" "$options" - [ $? -eq $SUCCESS ] && dhcp= ;; + [ $? -eq $DIALOG_OK ] && dhcp= ;; esac done @@ -383,7 +381,7 @@ f_dialog_menu_netdev_edit() fi fi - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN Index: usr.sbin/bsdconfig/networking/share/hostname.subr =================================================================== --- usr.sbin/bsdconfig/networking/share/hostname.subr (revision 256169) +++ usr.sbin/bsdconfig/networking/share/hostname.subr (working copy) @@ -110,7 +110,7 @@ f_dialog_input_hostname() # while :; do f_dialog_input hostname "$msg" "$hostname" \ - "$hline_alnum_punc_tab_enter" || return + "$hline_alnum_punc_tab_enter" || return $? # Taint-check the user's input f_dialog_validate_hostname "$hostname" && break done @@ -150,7 +150,7 @@ f_dialog_input_hostname() fi fi - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN Index: usr.sbin/bsdconfig/networking/share/ipaddr.subr =================================================================== --- usr.sbin/bsdconfig/networking/share/ipaddr.subr (revision 256169) +++ usr.sbin/bsdconfig/networking/share/ipaddr.subr (working copy) @@ -147,7 +147,7 @@ f_dialog_input_ipaddr() local setting="$( printf "$msg_current_ipaddr" \ "$interface" "$_ipaddr" )" f_noyes "$msg_nfs_mounts_may_cause_hang" "$setting" || - return $FAILURE + return $DIALOG_CANCEL fi local msg="$( printf "$msg_please_enter_new_ip_addr" "$interface" )" @@ -163,11 +163,11 @@ f_dialog_input_ipaddr() # - User has not made any changes to the given value # f_dialog_input _input "$msg" "$_ipaddr" \ - "$hline_num_punc_tab_enter" || return - [ "$_ipaddr" = "$_input" ] && return $FAILURE + "$hline_num_punc_tab_enter" || return $? + [ "$_ipaddr" = "$_input" ] && return $DIALOG_CANCEL # Return success if NULL value was entered - [ "$_input" ] || return $SUCCESS + [ "$_input" ] || return $DIALOG_OK # Take only the first "word" of the user's input _ipaddr="$_input" @@ -208,7 +208,7 @@ f_dialog_input_ipaddr() ipaddr="$_ipaddr" [ "$_netmask" ] && netmask="$_netmask" - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN Index: usr.sbin/bsdconfig/networking/share/media.subr =================================================================== --- usr.sbin/bsdconfig/networking/share/media.subr (revision 256169) +++ usr.sbin/bsdconfig/networking/share/media.subr (working copy) @@ -118,7 +118,7 @@ f_dialog_input_options() local setting="$( printf "$msg_current_options" \ "$interface" "$options" )" f_noyes "$msg_nfs_mounts_may_cause_hang" "$setting" || - return $FAILURE + return $DIALOG_CANCEL fi local msg="$( printf "$msg_please_enter_mediaopts" "$interface" )" @@ -138,7 +138,7 @@ f_dialog_input_options() local retval=$? f_dialog_line_sanitize _options - [ $retval -eq $SUCCESS ] && options="$_options" + [ $retval -eq $DIALOG_OK ] && options="$_options" return $retval } @@ -165,7 +165,7 @@ f_dialog_menu_media_options() local setting="$( printf "$msg_current_options" \ "$interface" "$_options" )" f_noyes "$msg_nfs_mounts_may_cause_hang" "$setting" || - return $FAILURE + return $DIALOG_CANCEL fi # @@ -219,7 +219,7 @@ f_dialog_menu_media_options() local retval=$? f_dialog_data_sanitize tag - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then options=$( eval f_dialog_menutag2item \"\$tag\" \ $supported_media ) case "$options" in Index: usr.sbin/bsdconfig/networking/share/netmask.subr =================================================================== --- usr.sbin/bsdconfig/networking/share/netmask.subr (revision 256169) +++ usr.sbin/bsdconfig/networking/share/netmask.subr (working copy) @@ -97,7 +97,7 @@ f_dialog_input_netmask() local setting="$( printf "$msg_current_subnet" \ "$interface" "$_netmask" )" f_noyes "$msg_nfs_mounts_may_cause_hang" "$setting" || - return $FAILURE + return $DIALOG_CANCEL fi # @@ -111,11 +111,11 @@ f_dialog_input_netmask() # - User has not made any changes to the given value # f_dialog_input _input "$msg" "$_netmask" \ - "$hline_num_punc_tab_enter" || return - [ "$_netmask" = "$_input" ] && return $FAILURE + "$hline_num_punc_tab_enter" || return $? + [ "$_netmask" = "$_input" ] && return $DIALOG_CANCEL # Return success if NULL value was entered - [ "$_input" ] || return $SUCCESS + [ "$_input" ] || return $DIALOG_OK # Take only the first "word" of the user's input _netmask="$_input" Index: usr.sbin/bsdconfig/networking/share/resolv.subr =================================================================== --- usr.sbin/bsdconfig/networking/share/resolv.subr (revision 256169) +++ usr.sbin/bsdconfig/networking/share/resolv.subr (working copy) @@ -195,7 +195,7 @@ f_dialog_resolv_conf_update() # update with our new `domain' and `search' directives. # local tmpfile="$( mktemp -t "$pgm" )" - [ "$tmpfile" ] || return $FAILURE + [ "$tmpfile" ] || return $DIALOG_CANCEL # # Fixup permissions and ownership (mktemp(1) creates the @@ -235,7 +235,8 @@ f_dialog_resolv_conf_update() # Write the temporary file contents and move the temporary # file into place. # - echo "$new_contents" | tail -r > "$tmpfile" || return $FAILURE + echo "$new_contents" | tail -r > "$tmpfile" || + return $DIALOG_CANCEL f_quietly mv "$tmpfile" "$RESOLV_CONF" fi @@ -293,8 +294,8 @@ f_dialog_input_nameserver() # # Perform sanity checks # - f_isinteger "$index" || return $FAILURE - [ $index -ge 0 ] || return $FAILURE + f_isinteger "$index" || return $DIALOG_CANCEL + [ $index -ge 0 ] || return $DIALOG_CANCEL local msg if [ $index -gt 0 ]; then @@ -312,7 +313,7 @@ f_dialog_input_nameserver() # while :; do f_dialog_input new_ns "$msg" "$ns" \ - "$hline_num_punc_tab_enter" || return + "$hline_num_punc_tab_enter" || return $? # Take only the first "word" of the user's input new_ns="${new_ns%%[$IFS]*}" @@ -331,7 +332,7 @@ f_dialog_input_nameserver() if [ $index -eq "0" -a "$new_ns" ]; then f_dialog_info "$msg_saving_nameserver" printf "nameserver\t%s\n" "$new_ns" >> "$RESOLV_CONF" - return $SUCCESS + return $DIALOG_OK elif [ $index -gt 0 -a "$old_ns" != "$new_ns" ]; then if [ "$new_ns" ]; then msg="$msg_saving_nameserver_existing" @@ -344,7 +345,7 @@ f_dialog_input_nameserver() # Create a new temporary file to write our new resolv.conf(5) # local tmpfile="$( mktemp -t "$pgm" )" - [ "$tmpfile" ] || return $FAILURE + [ "$tmpfile" ] || return $DIALOG_CANCEL # # Quietly fixup permissions and ownership @@ -381,7 +382,7 @@ f_dialog_input_nameserver() # Write the temporary file contents and move the temporary # file into place. # - echo "$new_contents" > "$tmpfile" || return $FAILURE + echo "$new_contents" > "$tmpfile" || return $DIALOG_CANCEL f_quietly mv "$tmpfile" "$RESOLV_CONF" fi } @@ -452,7 +453,7 @@ f_dialog_menu_nameservers() f_dialog_data_sanitize tag # Return if "Cancel" was chosen (-1) or ESC was pressed (255) - if [ $retval -ne $SUCCESS ]; then + if [ $retval -ne $DIALOG_OK ]; then return $retval else # Only update default-item on success Index: usr.sbin/bsdconfig/networking/share/routing.subr =================================================================== --- usr.sbin/bsdconfig/networking/share/routing.subr (revision 256169) +++ usr.sbin/bsdconfig/networking/share/routing.subr (working copy) @@ -75,7 +75,7 @@ f_dialog_input_defaultrouter() local setting="$( printf "$msg_current_default_router" \ "$defaultrouter" )" f_noyes "$msg_nfs_mounts_may_cause_hang" "$setting" || - return $FAILURE + return $DIALOG_CANCEL fi # @@ -87,8 +87,8 @@ f_dialog_input_defaultrouter() "$msg_please_enter_default_router" \ "$defaultrouter" "$hline_num_punc_tab_enter" retval=$? - [ "$defaultrouter" ] || return $SUCCESS - [ $retval -eq $SUCCESS ] || return $retval + [ "$defaultrouter" ] || return $DIALOG_OK + [ $retval -eq $DIALOG_OK ] || return $retval # Taint-check the user's input f_dialog_validate_ipaddr "$defaultrouter" && break @@ -112,7 +112,7 @@ f_dialog_input_defaultrouter() f_dialog_clear f_yesno "$msg_activate_default_router" \ "$( f_route_get_default )" "$defaultrouter" - if [ $? -eq $SUCCESS ]; then + if [ $? -eq $DIALOG_OK ]; then local err # Apply the default router/gateway @@ -120,7 +120,7 @@ f_dialog_input_defaultrouter() err=$( route add default "$defaultrouter" 2>&1 ) if [ $? -ne $SUCCESS ]; then f_dialog_msgbox "$err" - return $FAILURE + return $DIALOG_CANCEL fi fi fi Index: usr.sbin/bsdconfig/password/share/password.subr =================================================================== --- usr.sbin/bsdconfig/password/share/password.subr (revision 256169) +++ usr.sbin/bsdconfig/password/share/password.subr (working copy) @@ -114,7 +114,7 @@ f_dialog_input_password() break done - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN Index: usr.sbin/bsdconfig/security/kern_securelevel =================================================================== --- usr.sbin/bsdconfig/security/kern_securelevel (revision 256169) +++ usr.sbin/bsdconfig/security/kern_securelevel (working copy) @@ -131,11 +131,10 @@ while :; do retval=$? f_dialog_menutag_fetch mtag - if [ $retval -eq 2 ]; then - # The Help button was pressed + if [ $retval -eq $DIALOG_HELP ]; then f_show_help "$SECURELEVEL_HELPFILE" continue - elif [ $retval -ne 0 ]; then + elif [ $retval -ne $DIALOG_OK ]; then f_die fi Index: usr.sbin/bsdconfig/security/security =================================================================== --- usr.sbin/bsdconfig/security/security (revision 256169) +++ usr.sbin/bsdconfig/security/security (working copy) @@ -123,7 +123,7 @@ dialog_menu_main() f_dialog_menutag_store "$menu_choice" # Only update default-item on success - [ $retval -eq 0 ] && f_dialog_default_store "$menu_choice" + [ $retval -eq $DIALOG_OK ] && f_dialog_default_store "$menu_choice" return $retval } Index: usr.sbin/bsdconfig/share/common.subr =================================================================== --- usr.sbin/bsdconfig/share/common.subr (revision 256169) +++ usr.sbin/bsdconfig/share/common.subr (working copy) @@ -560,11 +560,12 @@ f_index_file() if [ "$lang" ]; then awk -v keyword="$keyword" "$f_index_file_awk" \ - $BSDCFG_LIBE${BSDCFG_LIBE:+/}*/INDEX.$lang && return + $BSDCFG_LIBE${BSDCFG_LIBE:+/}*/INDEX.$lang && + return $SUCCESS # No match, fall-thru to non-i18n sources fi awk -v keyword="$keyword" "$f_index_file_awk" \ - $BSDCFG_LIBE${BSDCFG_LIBE:+/}*/INDEX && return + $BSDCFG_LIBE${BSDCFG_LIBE:+/}*/INDEX && return $SUCCESS # No match? Fall-thru to `local' libexec sources (add-on modules) @@ -571,7 +572,7 @@ f_index_file() [ "$BSDCFG_LOCAL_LIBE" ] || return $FAILURE if [ "$lang" ]; then awk -v keyword="$keyword" "$f_index_file_awk" \ - $BSDCFG_LOCAL_LIBE/*/INDEX.$lang && return + $BSDCFG_LOCAL_LIBE/*/INDEX.$lang && return $SUCCESS # No match, fall-thru to non-i18n sources fi awk -v keyword="$keyword" "$f_index_file_awk" \ Index: usr.sbin/bsdconfig/share/device.subr =================================================================== --- usr.sbin/bsdconfig/share/device.subr (revision 256169) +++ usr.sbin/bsdconfig/share/device.subr (working copy) @@ -49,6 +49,7 @@ f_struct_define DEVICE \ desc \ devname \ type \ + capacity \ enabled \ init \ get \ @@ -114,7 +115,7 @@ f_device_try() } # f_device_register $name $desc $devname $type $enabled $init_function \ -# $get_function $shutdown_function $private +# $get_function $shutdown_function $private $capacity # # Register a device. A `structure' (see struct.subr) is created with the name # device_$name (so make sure $name contains only alpha-numeric characters or @@ -128,6 +129,7 @@ f_device_register() { local name="$1" desc="$2" devname="$3" type="$4" enabled="$5" local init_func="$6" get_func="$7" shutdown_func="$8" private="$9" + local capacity="${10}" f_struct_new DEVICE "device_$name" || return $FAILURE device_$name set name "$name" @@ -139,6 +141,7 @@ f_device_register() device_$name set get "$get_func" device_$name set shutdown "$shutdown_func" device_$name set private "$private" + device_$name set capacity "$capacity" # Scan our global register to see if it needs ammending local dev found= @@ -196,7 +199,7 @@ f_device_get_all() f_dprintf "Found a network device named %s" "$devname" f_device_register $devname \ "$desc" "$devname" $DEVICE_TYPE_NETWORK 1 \ - f_media_init_network "" f_media_shutdown_network "" + f_media_init_network "" f_media_shutdown_network "" -1 done # Next, try to find all the types of devices one might use @@ -208,6 +211,10 @@ f_device_get_all() n=$(( $n + 1 )) # Get the desc, type, and max (with debugging disabled) # NOTE: Bypassing f_device_name_get() for efficiency + # ASIDE: This would be equivalent to the following: + # debug= f_device_name_get $dev desc + # debug= f_device_name_get $dev type + # debug= f_device_name_get $dev max debug= f_getvar _device_desc$n desc debug= f_getvar _device_type$n type debug= f_getvar _device_max$n max @@ -222,7 +229,8 @@ f_device_get_all() f_device_register "${devname##*/}" "$desc" \ "$devname" $DEVICE_TYPE_CDROM 1 \ f_media_init_cdrom f_media_get_cdrom \ - f_media_shutdown_cdrom "" + f_media_shutdown_cdrom "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a CDROM device for %s" \ "$devname" ;; @@ -232,7 +240,8 @@ f_device_get_all() "$devname" $DEVICE_TYPE_FLOPPY 1 \ f_media_init_floppy \ f_media_get_floppy \ - f_media_shutdown_floppy "" + f_media_shutdown_floppy "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a floppy device for %s" \ "$devname" ;; @@ -241,7 +250,8 @@ f_device_get_all() f_device_register "${devname##*/}" "$desc" \ "$devname" $DEVICE_TYPE_USB 1 \ f_media_init_usb f_media_get_usb \ - f_media_shutdown_usb "" + f_media_shutdown_usb "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a USB disk for %s" "$devname" ;; esac @@ -254,7 +264,8 @@ f_device_get_all() f_device_register "${devname##*/}" "ISO9660 file system" \ "$devname" $DEVICE_TYPE_CDROM 1 \ f_media_init_cdrom f_media_get_cdrom \ - f_media_shutdown_cdrom "" + f_media_shutdown_cdrom "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a CDROM device for %s" "$devname" done @@ -281,7 +292,8 @@ f_device_get_all() "md(4) vnode file system" \ "$devname" $DEVICE_TYPE_CDROM 1 \ f_media_init_cdrom f_media_get_cdrom \ - f_media_shutdown_cdrom "" + f_media_shutdown_cdrom "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a CDROM device for %s" "$devname" ;; esac @@ -313,8 +325,13 @@ f_device_get_all() continue fi - f_device_register "$diskname" "" \ - "/dev/$diskname" $DEVICE_TYPE_DISK 0 + # Try and find its description + f_device_desc "$diskname" $DEVICE_TYPE_DISK desc + + f_device_register "$diskname" "$desc" \ + "/dev/$diskname" $DEVICE_TYPE_DISK 0 \ + "" "" "" "" \ + "$( f_device_capacity "$diskname" )" f_dprintf "Found a disk device named %s" "$diskname" # Look for existing partitions to register @@ -327,7 +344,8 @@ f_device_get_all() f_device_register "$slice" "" \ "/dev/$slice" $DEVICE_TYPE_DOS 1 \ f_media_init_dos f_media_get_dos \ - f_media_shutdown_dos "" + f_media_shutdown_dos "" \ + "$( f_device_capacity "/dev/$slice" )" f_dprintf "Found a DOS partition %s" "$slice" ;; 0xa5) # FreeBSD partition @@ -347,7 +365,9 @@ f_device_get_all() $DEVICE_TYPE_UFS 1 \ f_media_init_ufs \ f_media_get_ufs \ - f_media_shutdown_ufs "" + f_media_shutdown_ufs "" \ + "$( f_device_capacity \ + "$/dev/$part" )" f_dprintf "Found a UFS partition %s" \ "$part" done # parts @@ -379,10 +399,27 @@ f_device_name_get() case "$__prop" in type|desc|max) : good ;; *) return $FAILURE; esac + # + # Attempt to create an alternate-form of $__name that contains the + # first contiguous string of numbers replaced with `%d' for comparison + # against stored pattern names (see MAIN). + # + local __left="${__name%%[0-9]*}" __right="${__name#*[0-9]}" __dname= + if [ "$__left" != "$__name" ]; then + # Chop leading digits from right 'til we hit first non-digit + while :; do + case "$__right" in + [0-9]*) __right="${__right#[0-9]}" ;; + *) break + esac + done + __dname="${__left}%d$__right" + fi + [ "$__type" = "$DEVICE_TYPE_ANY" ] && __type= for __dev in $DEVICE_NAMES; do __n=$(( $__n + 1 )) - [ "$__dev" = "$__name" ] || continue + [ "$__dev" = "$__name" -o "$__dev" = "$__dname" ] || continue f_getvar _device_type$__n __devtype [ "${__type:-$__devtype}" = "$__devtype" ] || continue f_getvar _device_$__prop$__n $__var_to_set @@ -463,6 +500,39 @@ f_device_desc() fi fi + # + # For disks, attempt to return camcontrol(8) descriptions. + # Otherwise fall through to below static list. + # + f_have camcontrol && + [ "${__type:-$DEVICE_TYPE_DISK}" = "$DEVICE_TYPE_DISK" ] && + __cp=$( camcontrol devlist 2> /dev/null | awk -v disk="$__name" ' + $0~"(\\(|,)"disk"(,|\\))" { + if (!match($0, "<[^>]+>")) next + print substr($0, RSTART+1, RLENGTH-2) + found = 1 + exit + } + END { exit ! found } + ' ) && setvar "$__var_to_set" "$__cp" && return $SUCCESS + + # + # Attempt to create an alternate-form of $__name that contains the + # first contiguous string of numbers replaced with `%d' for comparison + # against stored pattern names (see MAIN). + # + local __left="${__name%%[0-9]*}" __right="${__name#*[0-9]}" __dname= + if [ "$__left" != "$__name" ]; then + # Chop leading digits from right 'til we hit first non-digit + while :; do + case "$__right" in + [0-9]*) __right="${__right#[0-9]}" ;; + *) break + esac + done + __dname="${__left}%d$__right" + fi + local __dev __devtype __n=0 for __dev in $DEVICE_NAMES; do __n=$(( $__n + 1 )) @@ -472,11 +542,8 @@ f_device_desc() __devname=$( f_substr "$__name" 0 ${#__dev} ) [ "$__devname" = "$__dev" ] || continue else - __devname="${__name%%[0-9]*}" - __devunit="${__name#$__devname}" - __devunit="${__devunit%%[!0-9]*}" - __devname=$( printf "$__dev" $__devunit ) - [ "$__devname" = "$__name" ] || continue + [ "$__dev" = "$__name" -o "$__dev" = "$__dname" ] || + continue fi debug= f_getvar _device_desc$__n $__var_to_set return $? @@ -552,7 +619,7 @@ f_device_find() f_device_init() { local name="$1" init_func - device_$name get init init_func || return + device_$name get init init_func || return $? ${init_func:-:} $name } @@ -564,7 +631,7 @@ f_device_init() f_device_get() { local name="$1" file="$2" probe="$3" get_func - device_$name get get get_func || return + device_$name get get get_func || return $? ${get_func:-:} $name "$file" ${3+"$probe"} } @@ -575,7 +642,7 @@ f_device_get() f_device_shutdown() { local name="$1" shutdown_func - device_$name get shutdown shutdown_func || return + device_$name get shutdown shutdown_func || return $? ${shutdown_func:-:} $name } @@ -597,7 +664,7 @@ f_device_menu() [ "$devtype" = "$type" ] || continue devs="$devs $dev" done - [ "$devs" ] || return $FAILURE + [ "$devs" ] || return $DIALOG_CANCEL local desc menu_list= for dev in $devs; do @@ -637,7 +704,7 @@ f_device_menu() ) local retval=$? - [ $retval -ne 2 ] && break + [ $retval -ne $DIALOG_HELP ] && break # Otherwise, the Help button was pressed f_show_help "$helpfile" # ...then loop back to menu @@ -646,7 +713,7 @@ f_device_menu() [ "$errexit" ] && set -e - if [ $retval -eq 0 ]; then + if [ $retval -eq $DIALOG_OK ]; then # Clean up the output of [X]dialog(1) and return it f_dialog_data_sanitize mtag echo "$mtag" >&2 @@ -655,7 +722,26 @@ f_device_menu() return $retval } +# f_device_capacity $device [$var_to_set] # +# Return the capacity of $device in bytes. +# +f_device_capacity() +{ + local __dev="$1" __var_to_set="$2" + local __bytes + + __bytes=$( diskinfo -v "$__dev" 2> /dev/null | + awk '/# mediasize in bytes/{print $1}' ) || __bytes=-1 + + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" "$__bytes" + else + echo "$__bytes" + fi +} + +# # Short-hand # f_cdrom() { f_device_name_set $DEVICE_TYPE_CDROM "$1" "$2" "$3"; } @@ -680,6 +766,7 @@ f_disk "ipsd%d" "IBM ServeRAID RAID array" f_disk "mfid%d" "LSI MegaRAID SAS array" 4 f_disk "mlxd%d" "Mylex RAID disk" 4 f_disk "twed%d" "3ware ATA RAID array" 4 +f_disk "vtbd%d" "VirtIO Block Device" 16 f_floppy "fd%d" "Floppy Drive unit A" 4 f_serial "cuau%d" "%s on device %s (COM%d)" 16 f_usb "da%da" "USB Mass Storage Device" 16 Index: usr.sbin/bsdconfig/share/dialog.subr =================================================================== --- usr.sbin/bsdconfig/share/dialog.subr (revision 256169) +++ usr.sbin/bsdconfig/share/dialog.subr (working copy) @@ -74,6 +74,18 @@ unset XDIALOG_FORCE_AUTOSIZE unset XDIALOG_INFOBOX_TIMEOUT # +# Exit codes for [X]dialog(1) +# +DIALOG_OK=${SUCCESS:-0} +DIALOG_CANCEL=${FAILURE:-1} +DIALOG_HELP=2 +DIALOG_ITEM_HELP=2 +DIALOG_EXTRA=3 +DIALOG_ITEM_HELP=4 +export DIALOG_ERROR=254 +DIALOG_ESC=255 + +# # Default behavior is to call f_dialog_init() automatically when loaded. # : ${DIALOG_SELF_INITIALIZE=1} Index: usr.sbin/bsdconfig/share/media/any.subr =================================================================== --- usr.sbin/bsdconfig/share/media/any.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/any.subr (working copy) @@ -113,11 +113,10 @@ f_media_get_type() f_dialog_data_sanitize mtag f_dprintf "retval=%s mtag=[%s]" $retval "$mtag" - if [ $retval -eq 2 ]; then - # The Help button was pressed + if [ $retval -eq $DIALOG_HELP ]; then f_show_help "$MEDIA_HELPFILE" continue - elif [ $retval -ne 0 ]; then + elif [ $retval -ne $DIALOG_OK ]; then return $FAILURE fi Index: usr.sbin/bsdconfig/share/media/cdrom.subr =================================================================== --- usr.sbin/bsdconfig/share/media/cdrom.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/cdrom.subr (working copy) @@ -170,7 +170,7 @@ f_media_shutdown_cdrom() { local dev="$1" err - [ "$CDROM_MOUNTED" ] || return + [ "$CDROM_MOUNTED" ] || return $FAILURE if [ "$CDROM_PREVIOUSLY_MOUNTED" ]; then CDROM_MOUNTED= Index: usr.sbin/bsdconfig/share/media/common.subr =================================================================== --- usr.sbin/bsdconfig/share/media/common.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/common.subr (working copy) @@ -127,7 +127,7 @@ f_media_generic_get() fi [ "$probe_type" ] && return $SUCCESS cat "$path" - return + return $? fi done Index: usr.sbin/bsdconfig/share/media/dos.subr =================================================================== --- usr.sbin/bsdconfig/share/media/dos.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/dos.subr (working copy) @@ -148,7 +148,7 @@ f_media_shutdown_dos() { local dev="$1" err - [ "$DOS_MOUNTED" ] || return + [ "$DOS_MOUNTED" ] || return $FAILURE if ! err=$( umount -f "$MOUNTPOINT" 2>&1 ); then err="${err#umount: }"; err="${err#*: }" Index: usr.sbin/bsdconfig/share/media/floppy.subr =================================================================== --- usr.sbin/bsdconfig/share/media/floppy.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/floppy.subr (working copy) @@ -205,7 +205,7 @@ f_media_shutdown_floppy() { local dev="$1" err mp - [ "$FLOPPY_MOUNTED" ] || return + [ "$FLOPPY_MOUNTED" ] || return $FAILURE device_$dev get private mp if ! err=$( umount -f "${mp:=$MOUNTPOINT}" 2>&1 ); then Index: usr.sbin/bsdconfig/share/media/ftp.subr =================================================================== --- usr.sbin/bsdconfig/share/media/ftp.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/ftp.subr (working copy) @@ -213,7 +213,7 @@ f_dialog_menu_media_ftp() $height $width $rows \ $menu_list \ 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD - ) || return $FAILURE + ) || return $DIALOG_CANCEL f_dialog_data_sanitize mtag case "$mtag" in @@ -224,7 +224,7 @@ f_dialog_menu_media_ftp() setvar $VAR_FTP_PATH "ftp://$value" esac - return $SUCCESS + return $DIALOG_OK } # f_media_set_ftp @@ -740,7 +740,7 @@ f_media_init_ftp() else f_yesno "$msg_cant_find_distribution" \ "$rel" "$ftp_host" - if [ $? -eq $SUCCESS ]; then + if [ $? -eq $DIALOG_OK ]; then unset $VAR_FTP_PATH f_media_set_ftp && continue fi Index: usr.sbin/bsdconfig/share/media/http.subr =================================================================== --- usr.sbin/bsdconfig/share/media/http.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/http.subr (working copy) @@ -101,7 +101,7 @@ f_dialog_menu_media_http() $height $width $rows \ $menu_list \ 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD - ) || return $FAILURE + ) || return $DIALOG_CANCEL f_dialog_data_sanitize mtag case "$mtag" in @@ -112,7 +112,7 @@ f_dialog_menu_media_http() setvar $VAR_HTTP_PATH "http://$value" esac - return $SUCCESS + return $DIALOG_OK } # f_media_set_http Index: usr.sbin/bsdconfig/share/media/nfs.subr =================================================================== --- usr.sbin/bsdconfig/share/media/nfs.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/nfs.subr (working copy) @@ -233,7 +233,7 @@ f_media_shutdown_nfs() { local dev="$1" err - [ "$NFS_MOUNTED" ] || return + [ "$NFS_MOUNTED" ] || return $FAILURE f_dprintf "Unmounting NFS partition on %s" "$MOUNTPOINT" if ! err=$( umount -f "$MOUNTPOINT" 2>&1 ); then Index: usr.sbin/bsdconfig/share/media/options.subr =================================================================== --- usr.sbin/bsdconfig/share/media/options.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/options.subr (working copy) @@ -224,11 +224,10 @@ f_media_options_menu() defaultitem="$mtag" f_dprintf "retval=%s mtag=[%s]" $retval "$mtag" - if [ $retval -eq 2 ]; then - # The Help button was pressed + if [ $retval -eq $DIALOG_HELP ]; then f_show_help "$OPTIONS_HELPFILE" continue - elif [ $retval -ne 0 ]; then + elif [ $retval -ne $DIALOG_OK ]; then break # to success fi Index: usr.sbin/bsdconfig/share/media/tcpip.subr =================================================================== --- usr.sbin/bsdconfig/share/media/tcpip.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/tcpip.subr (working copy) @@ -471,10 +471,10 @@ f_dialog_validate_tcpip() ! f_validate_gateway "$gateway" "$ipaddr" "$netmask"; then f_show_msg "$msg_invalid_gateway_ipv4_address_specified" else - return $SUCCESS + return $DIALOG_OK fi - return $FAILURE + return $DIALOG_CANCEL } # f_ifconfig_inet $interface [$var_to_set] @@ -1102,7 +1102,7 @@ f_device_dialog_tcp() local use_dhcp="" use_rtsol="" local _ipaddr _netmask _extras - [ "$dev" ] || return $FAILURE + [ "$dev" ] || return $DIALOG_CANCEL # Initialize vars from previous device values local private @@ -1125,7 +1125,6 @@ f_device_dialog_tcp() unset $VAR_NONINTERACTIVE fi - # # Try a RTSOL scan if such behavior is desired. # If the variable was configured and is YES, do it. @@ -1321,7 +1320,7 @@ f_device_dialog_tcp() if [ ! "$cp" ]; then # User either chose "Cancel", pressed # ESC, or blanked every form field - return $FAILURE + return $DIALOG_CANCEL else n=$( echo "$cp" | f_number_of_lines ) [ $n -eq 1 ] && case "$cp" in HELP*) @@ -1404,14 +1403,12 @@ f_device_dialog_tcp() f_dialog_data_sanitize cp f_dprintf "retval=%u mtag=[%s]" $retval "$cp" - if [ $retval -eq 2 ]; then - # The Help button was pressed + if [ $retval -eq $DIALOG_HELP ]; then f_show_help "$TCP_HELPFILE" continue - elif [ $retval -ne 0 ]; then - # User chose "Cancel" or pressed ESC + elif [ $retval -ne $DIALOG_OK ]; then f_dialog_title_restore - return $FAILURE + return $DIALOG_CANCEL fi case "$cp" in @@ -1490,7 +1487,7 @@ f_device_dialog_tcp() [ "$use_dhcp" ] || f_config_resolv # XXX this will do it on the MFS copy - return $SUCCESS + return $DIALOG_OK } # f_device_scan_tcp [$var_to_set] @@ -1586,15 +1583,15 @@ f_device_select_tcp() if [ ${cnt:=0} -gt 0 ]; then dev="${devs%%[$IFS]*}" f_device_dialog_tcp $dev - if [ $? -eq $SUCCESS ]; then + if [ $? -eq $DIALOG_OK ]; then setvar $VAR_NETWORK_DEVICE $dev - return $SUCCESS + return $DIALOG_OK fi fi done f_interactive && f_show_msg "$msg_no_network_devices" - return $FAILURE + return $DIALOG_CANCEL fi # $network_dev @@ -1610,7 +1607,7 @@ f_device_select_tcp() if f_dialog_yesno "$msg_assume_network_is_already_configured" then setvar $VAR_NETWORK_DEVICE $dev - return $SUCCESS + return $DIALOG_OK fi fi @@ -1617,11 +1614,11 @@ f_device_select_tcp() local retval=$SUCCESS if [ ${cnt:=0} -eq 0 ]; then f_show_msg "$msg_no_network_devices" - retval=$FAILURE + retval=$DIALOG_CANCEL elif [ $cnt -eq 1 ]; then f_device_dialog_tcp $dev retval=$? - [ $retval -eq $SUCCESS ] && setvar $VAR_NETWORK_DEVICE $dev + [ $retval -eq $DIALOG_OK ] && setvar $VAR_NETWORK_DEVICE $dev else local title="$msg_network_interface_information_required" local prompt="$msg_please_select_ethernet_device_to_configure" @@ -1632,15 +1629,15 @@ f_device_select_tcp() "$NETWORK_DEVICE_HELPFILE" \ 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD ) retval=$? - [ "$dev" ] || return $FAILURE + [ "$dev" ] || return $DIALOG_CANCEL f_device_find "$dev" $DEVICE_TYPE_NETWORK devs - [ "$devs" ] || return $FAILURE + [ "$devs" ] || return $DIALOG_CANCEL dev="${devs%%[$IFS]*}" f_device_dialog_tcp $dev retval=$? - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then f_struct_copy device_$dev device_network setvar $VAR_NETWORK_DEVICE network else @@ -1675,7 +1672,7 @@ f_dialog_menu_select_tcp() "$name" fi fi - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN Index: usr.sbin/bsdconfig/share/media/ufs.subr =================================================================== --- usr.sbin/bsdconfig/share/media/ufs.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/ufs.subr (working copy) @@ -177,7 +177,7 @@ f_media_shutdown_ufs() { local dev="$1" err - [ "$UFS_MOUNTED" ] || return + [ "$UFS_MOUNTED" ] || return $FAILURE if ! err=$( umount -f "$MOUNTPOINT" 2>&1 ); then err="${err#umount: }"; err="${err#*: }" Index: usr.sbin/bsdconfig/share/media/usb.subr =================================================================== --- usr.sbin/bsdconfig/share/media/usb.subr (revision 256169) +++ usr.sbin/bsdconfig/share/media/usb.subr (working copy) @@ -158,7 +158,7 @@ f_media_shutdown_usb() { local dev="$1" err - [ "$USB_MOUNTED" ] || return + [ "$USB_MOUNTED" ] || return $FAILURE if ! err=$( umount -f "$MOUNTPOINT" 2>&1 ); then err="${err#umount: }"; err="${err#*: }" Index: usr.sbin/bsdconfig/share/mustberoot.subr =================================================================== --- usr.sbin/bsdconfig/share/mustberoot.subr (revision 256169) +++ usr.sbin/bsdconfig/share/mustberoot.subr (working copy) @@ -176,9 +176,9 @@ f_become_root_via_sudo() retval=$? # Catch X11-related errors - if [ $retval -eq 255 ]; then + if [ $retval -eq $DIALOG_ESC ]; then f_die $retval "$password" - elif [ $retval -ne 0 ]; then + elif [ $retval -ne $DIALOG_OK ]; then # User cancelled exit $retval fi @@ -316,10 +316,10 @@ f_authenticate_some_user() retval=$? # Catch X11-related errors - [ $retval -eq 255 ] && f_die $retval "$user_pass" + [ $retval -eq $DIALOG_ESC ] && f_die $retval "$user_pass" # Exit if the user cancelled. - [ $retval -eq $SUCCESS ] || exit $retval + [ $retval -eq $DIALOG_OK ] || exit $retval # # Make sure the user exists and is non-root Index: usr.sbin/bsdconfig/share/packages/packages.subr =================================================================== --- usr.sbin/bsdconfig/share/packages/packages.subr (revision 256169) +++ usr.sbin/bsdconfig/share/packages/packages.subr (working copy) @@ -132,7 +132,7 @@ f_package_select() package="$1" shift 1 # package for pkgsel in $SELECTED_PACKAGES; do - [ "$package" = "$pkgsel" ] && return + [ "$package" = "$pkgsel" ] && return $SUCCESS done SELECTED_PACKAGES="$SELECTED_PACKAGES $package" f_dprintf "Added %s to selection list" "$package" @@ -312,7 +312,7 @@ f_package_menu_categories() # creates _{varcat}_ninstalled and _{varcat}_nselected local category_list - debug= f_getvar "$var_to_get" category_list || return $FAILURE + debug= f_getvar "$var_to_get" category_list || return $DIALOG_CANCEL # Accent the category menu list with ninstalled/nselected eval f_package_accent_category_menu category_list $category_list @@ -395,7 +395,7 @@ f_package_menu_select() local defaultitem="$3" local hline="$hline_arrows_tab_punc_enter" - f_isinteger "$page" || return $FAILURE + f_isinteger "$page" || return $DIALOG_CANCEL local varcat f_str2varname "$category" varcat @@ -518,7 +518,7 @@ f_package_menu_select() f_dialog_data_sanitize menu_choice f_dialog_menutag_store "$menu_choice" - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then local item item=$( eval f_dialog_menutag2item${SHOW_DESC:+_with_help} \ \"\$menu_choice\" $menu_list ) @@ -603,7 +603,7 @@ f_package_review() done if [ ! "$menu_list" ]; then f_show_msg "$msg_no_packages_were_selected_for_extraction" - return $FAILURE # They might have selected this by accident + return $DIALOG_CANCEL # Might have selected this by accident fi menu_list=$( echo "$menu_list" | sort ) @@ -660,7 +660,7 @@ f_package_review() f_package_deselect "$package" done - return $SUCCESS + return $DIALOG_OK } # f_package_config @@ -693,7 +693,7 @@ f_package_config() f_dprintf "retval=%u mtag=[%s]" $retval "$category" category_defaultitem="$category" - [ $retval -eq $SUCCESS ] || break + [ $retval -eq $DIALOG_OK ] || break # Maybe the user chose an action (like `Review') case "$category" in @@ -729,14 +729,14 @@ f_package_config() # the Cancel button because stdout will be NULL. # Alternatively, Xdialog(1) will terminate with 1 # if/when Cancel is chosen on any widget. - if [ $retval -eq 255 -o ! "$menu_choice" ]; then - # User pressed ESC or chose Cancel + if [ $retval -eq $DIALOG_ESC -o ! "$menu_choice" ] + then break - elif [ $retval -eq 1 ]; then + elif [ $retval -eq $DIALOG_CANCEL ]; then # Using X11, Xdialog(1) returned 1 for Cancel f_show_msg "%s" "$menu_choice" break - elif [ $retval -ne $SUCCESS ]; then + elif [ $retval -ne $DIALOG_OK ]; then # X11-related error occurred using Xdialog(1) f_show_msg "%s" "$menu_choice" break Index: usr.sbin/bsdconfig/share/strings.subr =================================================================== --- usr.sbin/bsdconfig/share/strings.subr (revision 256169) +++ usr.sbin/bsdconfig/share/strings.subr (working copy) @@ -26,6 +26,11 @@ if [ ! "$_STRINGS_SUBR" ]; then _STRINGS_SUBR=1 # # $FreeBSD$ # +############################################################ INCLUDES + +BSDCFG_SHARE="/usr/share/bsdconfig" +. $BSDCFG_SHARE/common.subr || exit 1 + ############################################################ GLOBALS # @@ -319,6 +324,112 @@ f_shell_unescape() f_replaceall "$__string" "'\\''" "'" "$__var_to_set" } +# f_expand_number $string [$var_to_set] +# +# Unformat $string into a number, optionally to be stored in $var_to_set. This +# function follows the SI power of two convention. +# +# The prefixes are: +# +# Prefix Description Multiplier +# k kilo 1024 +# M mega 1048576 +# G giga 1073741824 +# T tera 1099511627776 +# P peta 1125899906842624 +# E exa 1152921504606846976 +# +# NOTE: Prefixes are case-insensitive. +# +# Upon successful completion, the value 0 is returned (or stored to +# $var_to_set); otherwise -1. Reasons for a -1 return include: +# +# Given $string contains no digits. +# An unrecognized prefix was given. +# Result too large to calculate. +# +f_expand_number() +{ + local __string="$1" __var_to_set="$2" + local __cp __num + + # Remove any leading non-digits + while :; do + __cp="$__string" + __string="${__cp#[!0-9]}" + [ "$__string" = "$__cp" ] && break + done + + # Return `-1' if string didn't contain any digits + if [ ! "$__string" ]; then + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + fi + + # Store the numbers + __num="${__string%%[!0-9]*}" + + # Shortcut + if [ $__num -eq 0 ]; then + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" 0 + else + echo 0 + fi + return $SUCCESS + fi + + # Remove all the leading numbers from the string to get at the prefix + while :; do + __cp="$__string" + __string="${__cp#[0-9]}" + [ "$__string" = "$__cp" ] && break + done + + # Test for invalid prefix + case "$__string" in + ""|[KkMmGgTtPpEe]*) : known prefix ;; + *) + # Unknown prefix + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + esac + + # Multiply the number out + case "$__string" in + [Kk]) __num=$(( $__num * 1024 )) ;; + [Mm]) __num=$(( $__num * 1048576 )) ;; + [Gg]) __num=$(( $__num * 1073741824 )) ;; + [Tt]) __num=$(( $__num * 1099511627776 )) ;; + [Pp]) __num=$(( $__num * 1125899906842624 )) ;; + [Ee]) __num=$(( $__num * 1152921504606846976 )) ;; + esac + if [ $__num -le 0 ]; then + # Arithmetic overflow + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + fi + + # Return the number + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" $__num + else + echo $__num + fi +} + ############################################################ MAIN f_dprintf "%s: Successfully loaded." strings.subr Index: usr.sbin/bsdconfig/startup/misc =================================================================== --- usr.sbin/bsdconfig/startup/misc (revision 256169) +++ usr.sbin/bsdconfig/startup/misc (working copy) @@ -309,10 +309,10 @@ dialog_input_value() f_dialog_title_restore # Return if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || return $retval + [ $retval -eq $DIALOG_OK ] || return $retval value="$_input" - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN @@ -429,7 +429,7 @@ while :; do ;; esac - [ $? -eq $SUCCESS ] || f_dialog_msgbox "$err\n" + [ $? -eq $DIALOG_OK ] || f_dialog_msgbox "$err\n" done exit $SUCCESS Index: usr.sbin/bsdconfig/startup/rcconf =================================================================== --- usr.sbin/bsdconfig/startup/rcconf (revision 256169) +++ usr.sbin/bsdconfig/startup/rcconf (working copy) @@ -195,7 +195,7 @@ dialog_menu_main() f_dialog_menutag_store "$menu_choice" # Only update default-item on success - [ $retval -eq 0 ] && f_dialog_default_store "$menu_choice" + [ $retval -eq $DIALOG_OK ] && f_dialog_default_store "$menu_choice" return $retval } @@ -236,13 +236,13 @@ while :; do f_dialog_input_view_details continue esac - elif [ $retval -eq 2 ]; then + elif [ $retval -eq $DIALOG_HELP ]; then # The ``Help'' button (labeled "Details") was pressed f_dialog_input_view_details continue fi - [ $retval -eq 0 ] || f_die + [ $retval -eq $DIALOG_OK ] || f_die case "$mtag" in "X $msg_exit") break ;; Index: usr.sbin/bsdconfig/startup/rcdelete =================================================================== --- usr.sbin/bsdconfig/startup/rcdelete (revision 256169) +++ usr.sbin/bsdconfig/startup/rcdelete (working copy) @@ -232,7 +232,7 @@ dialog_menu_main() f_dialog_menutag_store "$menu_choice" # Only update default-item on success - [ $retval -eq 0 ] && f_dialog_default_store "$menu_choice" + [ $retval -eq $DIALOG_OK ] && f_dialog_default_store "$menu_choice" return $retval } @@ -249,7 +249,7 @@ dialog_menu_confirm_delete() local menu_list # Calculated below local hline="$hline_arrows_tab_enter" - [ $# -ge 1 ] || return $FAILURE + [ $# -ge 1 ] || return $DIALOG_CANCEL # If asked to delete only one variable, simply ask and return if [ $# -eq 1 ]; then @@ -351,13 +351,13 @@ while :; do f_dialog_input_view_details && dialog_create_main continue esac - elif [ $retval -eq 2 ]; then + elif [ $retval -eq $DIALOG_HELP ]; then # The ``Help'' button (labeled "Details") was pressed f_dialog_input_view_details && dialog_create_main continue fi - [ $retval -eq 0 ] || f_die + [ $retval -eq $DIALOG_OK ] || f_die case "$mtag" in "X $msg_exit_cancel") break ;; Index: usr.sbin/bsdconfig/startup/rcvar =================================================================== --- usr.sbin/bsdconfig/startup/rcvar (revision 256169) +++ usr.sbin/bsdconfig/startup/rcvar (working copy) @@ -158,7 +158,7 @@ dialog_menu_main() f_dialog_menutag_store "$menu_choice" f_dialog_default_store "$menu_choice" - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then local item item=$( eval f_dialog_menutag2item${SHOW_DESC:+_with_help} \ \"\$menu_choice\" $menu_list ) Index: usr.sbin/bsdconfig/startup/share/rcconf.subr =================================================================== --- usr.sbin/bsdconfig/startup/share/rcconf.subr (revision 256169) +++ usr.sbin/bsdconfig/startup/share/rcconf.subr (working copy) @@ -336,7 +336,7 @@ f_dialog_input_view_details() f_dialog_title_restore - [ $retval -eq 0 ] || return $FAILURE + [ $retval -eq $DIALOG_OK ] || return $DIALOG_CANCEL case "$mtag" in "R $msg_reset") @@ -465,7 +465,7 @@ f_dialog_input_rcvar() # Return if user either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_please_enter_rcvar_name" \ - "$_input" "$hline_alnum_tab_enter" || return + "$_input" "$hline_alnum_tab_enter" || return $? # Check for invalid entry (1of2) if ! echo "$_input" | grep -q "^[[:alpha:]_]"; then @@ -486,7 +486,7 @@ f_dialog_input_rcvar() f_dprintf "f_dialog_input_rcvar: rcvar->[%s]" "$rcvar" - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN Index: usr.sbin/bsdconfig/startup/share/rcedit.subr =================================================================== --- usr.sbin/bsdconfig/startup/share/rcedit.subr (revision 256169) +++ usr.sbin/bsdconfig/startup/share/rcedit.subr (working copy) @@ -69,11 +69,11 @@ f_dialog_rcedit() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg" "$_input" \ - "$hline_alnum_punc_tab_enter" || return + "$hline_alnum_punc_tab_enter" || return $? # Return if the value has not changed from current local cur_val="$( f_sysrc_get "$var" )" - [ "$_input" = "$cur_val" ] && return $SUCCESS + [ "$_input" = "$cur_val" ] && return $DIALOG_OK f_dprintf "%s: [%s]->[%s]" "$var" "$cur_val" "$_input" Index: usr.sbin/bsdconfig/timezone/timezone =================================================================== --- usr.sbin/bsdconfig/timezone/timezone (revision 256169) +++ usr.sbin/bsdconfig/timezone/timezone (working copy) @@ -226,7 +226,7 @@ if [ "$_PATH_WALL_CMOS_CLOCK" -a ! "$SKIPUTC" ]; t result=$? fi - if [ $result -eq 0 ]; then + if [ $result -eq $DIALOG_OK ]; then # User chose YES [ "$REALLYDOIT" ] && f_quietly rm -f "$_PATH_WALL_CMOS_CLOCK" @@ -250,7 +250,7 @@ if [ $# -ge 1 ]; then result=$? f_dialog_title_restore - if [ $result -eq 0 ]; then + if [ $result -eq $DIALOG_OK ]; then # User chose YES f_install_zoneinfo_file "$default" result=$? @@ -287,7 +287,7 @@ while :; do retval=$? f_dialog_menutag_fetch mtag - if [ $retval -ne 0 ]; then + if [ $retval -ne $DIALOG_OK ]; then [ "$TZ_OR_FAIL" ] && f_die exit $SUCCESS fi @@ -368,7 +368,7 @@ while :; do f_dialog_data_sanitize tag defaultctry="$tag" - if [ $retval -ne 0 ]; then + if [ $retval -ne $DIALOG_OK ]; then NEED_CONTINENT=1 continue # back to main menu fi @@ -427,7 +427,7 @@ while :; do f_dialog_data_sanitize n defaultzone="$n" - if [ $retval -ne 0 ]; then + if [ $retval -ne $DIALOG_OK ]; then [ $nitems -eq 1 ] && NEED_CONTINENT=1 NEED_COUNTRY=1 continue @@ -441,7 +441,7 @@ while :; do f_confirm_zone "$real_continent/$filename" || continue fi - [ $retval -eq 0 ] || continue # back to main menu + [ $retval -eq $DIALOG_OK ] || continue # back to main menu if ! f_install_zoneinfo "$real_continent/$filename"; then [ $nzones -lt 0 ] && NEED_COUNTRY=1 Index: usr.sbin/bsdconfig/usermgmt/groupdel =================================================================== --- usr.sbin/bsdconfig/usermgmt/groupdel (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/groupdel (working copy) @@ -75,7 +75,7 @@ while :; do f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" defaultitem="$mtag" - [ $retval -eq 0 ] || f_die + [ $retval -eq $DIALOG_OK ] || f_die [ "$mtag" = "X $msg_exit" ] && break Index: usr.sbin/bsdconfig/usermgmt/groupedit =================================================================== --- usr.sbin/bsdconfig/usermgmt/groupedit (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/groupedit (working copy) @@ -75,7 +75,7 @@ while :; do f_dprintf "retval=%s mtag=[%s]" $retval "$mtag" defaultitem="$mtag" - [ $retval -eq 0 ] || f_die + [ $retval -eq $DIALOG_OK ] || f_die [ "$mtag" = "X $msg_exit" ] && break Index: usr.sbin/bsdconfig/usermgmt/groupinput =================================================================== --- usr.sbin/bsdconfig/usermgmt/groupinput (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/groupinput (working copy) @@ -162,9 +162,9 @@ if [ "$mode" = "Add" ]; then f_dialog_noyes "$msg_use_default_values_for_all_account_details" retval=$? - if [ $retval -eq 255 ]; then # User pressed ESC + if [ $retval -eq $DIALOG_ESC ]; then exit $SUCCESS - elif [ $retval -ne $SUCCESS ]; then + elif [ $retval -ne $DIALOG_OK ]; then # # Ask a series of questions to pre-fill the editor screen. # @@ -174,9 +174,9 @@ if [ "$mode" = "Add" ]; then # [ "$passwdtype" = "yes" ] && - { f_dialog_input_group_password || exit 0; } - f_dialog_input_group_gid || exit 0 - f_dialog_input_group_members || exit 0 + { f_dialog_input_group_password || exit $SUCCESS; } + f_dialog_input_group_gid || exit $SUCCESS + f_dialog_input_group_members || exit $SUCCESS fi fi @@ -255,13 +255,11 @@ while :; do f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" # Exit if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || f_die + [ $retval -eq $DIALOG_OK ] || f_die case "$mtag" in X) # Exit - if [ "$save_flag" ]; then - save_changes || continue - fi + [ "$save_flag" ] && { save_changes || continue; } break ;; 1) # Group Name @@ -274,7 +272,7 @@ while :; do f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" # Loop if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || continue + [ $retval -eq $DIALOG_OK ] || continue [ "$mtag" = "X $msg_exit" ] && continue Index: usr.sbin/bsdconfig/usermgmt/share/group_input.subr =================================================================== --- usr.sbin/bsdconfig/usermgmt/share/group_input.subr (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/share/group_input.subr (working copy) @@ -125,15 +125,15 @@ f_dialog_input_group_name() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_group" "$_input" \ - "$hline_alnum_tab_enter" || return + "$hline_alnum_tab_enter" || return $? # Check for no-change - [ "$_input" = "$_name" ] && return $SUCCESS + [ "$_input" = "$_name" ] && return $DIALOG_OK # Check for reversion if [ "$_input" = "$cur_group_name" ]; then group_name="$cur_group_name" - return $SUCCESS + return $DIALOG_OK fi # Check for NULL entry @@ -161,7 +161,7 @@ f_dialog_input_group_name() f_dprintf "group_name: [%s]->[%s]" "$cur_group_name" "$group_name" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_group_password @@ -210,7 +210,7 @@ f_dialog_input_group_password() debug= f_dialog_line_sanitize _password1 # Return if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || return $retval + [ $retval -eq $DIALOG_OK ] || return $retval _password2=$( $DIALOG \ --title "$DIALOG_TITLE" \ @@ -227,7 +227,7 @@ f_dialog_input_group_password() debug= f_dialog_line_sanitize _password2 # Return if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || return $retval + [ $retval -eq $DIALOG_OK ] || return $retval # Check for password mismatch if [ "$_password1" != "$_password2" ]; then @@ -239,9 +239,9 @@ f_dialog_input_group_password() if [ ! "$_password1" ]; then f_dialog_yesno "$msg_disable_password_auth_for_group" local retval=$? - if [ $retval -eq 255 ]; then # ESC was pressed + if [ $retval -eq $DIALOG_ESC ]; then return $retval - elif [ $retval -eq $SUCCESS ]; then + elif [ $retval -eq $DIALOG_OK ]; then pw_group_password_disable=1 else continue # back to password prompt @@ -258,7 +258,7 @@ f_dialog_input_group_password() f_dprintf "group_password: [%s]->[%s]" \ "$cur_group_password" "$group_password" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_group_gid [$group_gid] @@ -273,7 +273,7 @@ f_dialog_input_group_gid() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_group_id_leave_empty_for_default" \ - "$_input" "$hline_num_tab_enter" || return + "$_input" "$hline_num_tab_enter" || return $? group_gid="$_input" save_flag=1 @@ -280,7 +280,7 @@ f_dialog_input_group_gid() f_dprintf "group_gid: [%s]->[%s]" "$cur_group_gid" "$group_gid" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_group_members [$group_members] @@ -329,7 +329,7 @@ f_dialog_input_group_members() f_dprintf "retval=%u menu_choice=[%s]" $retval "$menu_choice" # Return if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || return $retval + [ $retval -eq $DIALOG_OK ] || return $retval local _group_members case "$menu_choice" in @@ -399,7 +399,7 @@ f_dialog_input_group_members() f_dprintf "group_members: [%s]->[%s]" \ "$cur_group_members" "$group_members" - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN Index: usr.sbin/bsdconfig/usermgmt/share/user_input.subr =================================================================== --- usr.sbin/bsdconfig/usermgmt/share/user_input.subr (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/share/user_input.subr (working copy) @@ -206,7 +206,7 @@ f_dialog_input_member_groups() f_dprintf "pw_member_groups: [%s]->[%s]" \ "$cur_pw_member_groups" "$pw_member_groups" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_name [$name] @@ -229,15 +229,15 @@ f_dialog_input_name() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_login" "$_input" \ - "$hline_alnum_tab_enter" || return + "$hline_alnum_tab_enter" || return $? # Check for no-change - [ "$_input" = "$_name" ] && return $SUCCESS + [ "$_input" = "$_name" ] && return $DIALOG_OK # Check for reversion if [ "$_input" = "$cur_pw_name" ]; then pw_name="$cur_pw_name" - return $SUCCESS + return $DIALOG_OK fi # Check for NULL entry @@ -265,7 +265,7 @@ f_dialog_input_name() f_dprintf "pw_name: [%s]->[%s]" "$cur_pw_name" "$pw_name" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_password @@ -336,9 +336,9 @@ f_dialog_input_password() if [ ! "$_password1" ]; then f_dialog_yesno "$msg_disable_password_auth_for_account" local retval=$? - if [ $retval -eq 255 ]; then # ESC was pressed + if [ $retval -eq $DIALOG_ESC ]; then return $retval - elif [ $retval -eq $SUCCESS ]; then + elif [ $retval -eq $DIALOG_OK ]; then pw_password_disable=1 else continue # back to password prompt @@ -354,7 +354,7 @@ f_dialog_input_password() f_dprintf "pw_password: [%s]->[%s]" "$cur_pw_password" "$pw_password" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_gecos [$gecos] @@ -370,7 +370,7 @@ f_dialog_input_gecos() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_full_name" "$_input" \ - "$hline_alnum_punc_tab_enter" || return + "$hline_alnum_punc_tab_enter" || return $? pw_gecos="$_input" save_flag=1 @@ -377,7 +377,7 @@ f_dialog_input_gecos() f_dprintf "pw_gecos: [%s]->[%s]" "$cur_pw_gecos" "$pw_gecos" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_uid [$uid] @@ -392,7 +392,7 @@ f_dialog_input_uid() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_user_id_leave_empty_for_default" \ - "$_input" "$hline_num_tab_enter" || return + "$_input" "$hline_num_tab_enter" || return $? pw_uid="$_input" save_flag=1 @@ -399,7 +399,7 @@ f_dialog_input_uid() f_dprintf "pw_uid: [%s]->[%s]" "$cur_pw_uid" "$pw_uid" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_gid [$gid] @@ -414,7 +414,7 @@ f_dialog_input_gid() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_group_id_leave_empty_for_default" \ - "$_input" "$hline_num_tab_enter" || return + "$_input" "$hline_num_tab_enter" || return $? pw_gid="$_input" save_flag=1 @@ -421,7 +421,7 @@ f_dialog_input_gid() f_dprintf "pw_gid: [%s]->[%s]" "$cur_pw_gid" "$pw_gid" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_class [$class] @@ -436,7 +436,7 @@ f_dialog_input_class() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_login_class" "$_input" \ - "$hline_alnum_tab_enter" || return + "$hline_alnum_tab_enter" || return $? pw_class="$_input" save_flag=1 @@ -443,7 +443,7 @@ f_dialog_input_class() f_dprintf "pw_class: [%s]->[%s]" "$cur_pw_class" "$pw_class" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_expire_password [$seconds] @@ -508,7 +508,7 @@ f_dialog_input_expire_password() f_dprintf "retval=%u date_type=[%s]" $retval "$date_type" # Return if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || return $retval + [ $retval -eq $DIALOG_OK ] || return $retval case "$date_type" in 1) # Password does not expire @@ -538,7 +538,7 @@ f_dialog_input_expire_password() f_dprintf "retval=%u ret_date=[%s]" $retval "$ret_date" # Return to menu if either ESC or Cancel/No - [ $retval -eq $SUCCESS ] || continue + [ $retval -eq $DIALOG_OK ] || continue _input_time= [ "$secs" ] && _input_time=$( date -j \ @@ -559,7 +559,7 @@ f_dialog_input_expire_password() f_dprintf "retval=%u ret_time=[%s]" $retval "$ret_time" # Return to menu if either ESC or Cancel/No - [ $retval -eq $SUCCESS ] || continue + [ $retval -eq $DIALOG_OK ] || continue _input=$( date \ -j -f "%d/%m/%Y %T" \ @@ -627,7 +627,7 @@ f_dialog_input_expire_password() f_dprintf "pw_password_expire: [%s]->[%s]" \ "$cur_pw_password_expire" "$pw_password_expire" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_expire_account [$seconds] @@ -692,7 +692,7 @@ f_dialog_input_expire_account() f_dprintf "retval=%u date_type=[%s]" $retval "$date_type" # Return if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || return $retval + [ $retval -eq $DIALOG_OK ] || return $retval case "$date_type" in 1) # Account does not expire @@ -722,7 +722,7 @@ f_dialog_input_expire_account() f_dprintf "retval=%u ret_date=[%s]" $retval "$ret_date" # Return to menu if either ESC or Cancel/No - [ $retval -eq $SUCCESS ] || continue + [ $retval -eq $DIALOG_OK ] || continue _input_time= [ "$secs" ] && _input_time=$( date -j \ @@ -743,7 +743,7 @@ f_dialog_input_expire_account() f_dprintf "retval=%u ret_time=[%s]" $retval "$ret_time" # Return to menu if either ESC or Cancel/No - [ $retval -eq $SUCCESS ] || continue + [ $retval -eq $DIALOG_OK ] || continue _input=$( date \ -j -f "%d/%m/%Y %T" \ @@ -811,7 +811,7 @@ f_dialog_input_expire_account() f_dprintf "pw_account_expire: [%s]->[%s]" \ "$cur_pw_account_expire" "$pw_account_expire" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_home_dir [$home_dir] @@ -826,7 +826,7 @@ f_dialog_input_home_dir() # Return if user has either pressed ESC or chosen Cancel/No f_dialog_input _input "$msg_home_directory" "$_input" \ - "$hline_alnum_punc_tab_enter" || return + "$hline_alnum_punc_tab_enter" || return $? pw_home_dir="$_input" save_flag=1 @@ -833,7 +833,7 @@ f_dialog_input_home_dir() f_dprintf "pw_home_dir: [%s]->[%s]" "$cur_pw_home_dir" "$pw_home_dir" - return $SUCCESS + return $DIALOG_OK } # f_dialog_input_home_create @@ -850,7 +850,7 @@ f_dialog_input_home_create() f_dialog_yesno "$msg_create_home_directory" retval=$? - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then pw_home_create="$msg_yes" else pw_home_create="$msg_no" @@ -860,7 +860,7 @@ f_dialog_input_home_create() f_dprintf "pw_home_create: [%s]->[%s]" \ "$cur_pw_home_create" "$pw_home_create" - [ $retval -ne 255 ] # return failure if user pressed ESC + [ $retval -ne $DIALOG_ESC ] # return failure if user pressed ESC } # f_dialog_input_group_delete @@ -893,7 +893,7 @@ f_dialog_input_group_delete() fi retval=$? - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then pw_group_delete="$msg_yes" else pw_group_delete="$msg_no" @@ -903,7 +903,7 @@ f_dialog_input_group_delete() f_dprintf "pw_group_delete: [%s]->[%s]" \ "$cur_pw_group_delete" "$pw_group_delete" - [ $retval -ne 255 ] # return failure if user pressed ESC + [ $retval -ne $DIALOG_ESC ] # return failure if user pressed ESC } # f_dialog_input_home_delete @@ -920,7 +920,7 @@ f_dialog_input_home_delete() f_dialog_yesno "$msg_delete_home_directory" retval=$? - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then pw_home_delete="$msg_yes" else pw_home_delete="$msg_no" @@ -930,7 +930,7 @@ f_dialog_input_home_delete() f_dprintf "pw_home_delete: [%s]->[%s]" \ "$cur_pw_home_delete" "$pw_home_delete" - [ $retval -ne 255 ] # return failure if user pressed ESC + [ $retval -ne $DIALOG_ESC ] # return failure if user pressed ESC } # f_dialog_input_dotfiles_create @@ -948,7 +948,7 @@ f_dialog_input_dotfiles_create() f_dialog_yesno "$msg_create_dotfiles" retval=$? - if [ $retval -eq $SUCCESS ]; then + if [ $retval -eq $DIALOG_OK ]; then pw_dotfiles_create="$msg_yes" else pw_dotfiles_create="$msg_no" @@ -958,7 +958,7 @@ f_dialog_input_dotfiles_create() f_dprintf "pw_dotfiles_create: [%s]->[%s]" \ "$cur_pw_dotfiles_create" "$pw_dotfiles_create" - [ $retval -ne 255 ] # return failure if user pressed ESC + [ $retval -ne $DIALOG_ESC ] # return failure if user pressed ESC } # f_dialog_input_shell [$shell] @@ -1015,7 +1015,7 @@ f_dialog_input_shell() f_dprintf "pw_shell: [%s]->[%s]" "$cur_pw_shell" "$pw_shell" - return $SUCCESS + return $DIALOG_OK } ############################################################ MAIN Index: usr.sbin/bsdconfig/usermgmt/userdel =================================================================== --- usr.sbin/bsdconfig/usermgmt/userdel (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/userdel (working copy) @@ -75,7 +75,7 @@ while :; do f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" defaultitem="$mtag" - [ $retval -eq 0 ] || f_die + [ $retval -eq $DIALOG_OK ] || f_die [ "$mtag" = "X $msg_exit" ] && break Index: usr.sbin/bsdconfig/usermgmt/useredit =================================================================== --- usr.sbin/bsdconfig/usermgmt/useredit (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/useredit (working copy) @@ -75,7 +75,7 @@ while :; do f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" defaultitem="$mtag" - [ $retval -eq 0 ] || f_die + [ $retval -eq $DIALOG_OK ] || f_die [ "$mtag" = "X $msg_exit" ] && break Index: usr.sbin/bsdconfig/usermgmt/userinput =================================================================== --- usr.sbin/bsdconfig/usermgmt/userinput (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/userinput (working copy) @@ -257,9 +257,9 @@ if [ "$mode" = "Add" ]; then f_dialog_noyes "$msg_use_default_values_for_all_account_details" retval=$? - if [ $retval -eq 255 ]; then # User pressed ESC + if [ $retval -eq $DIALOG_ESC ]; then exit $SUCCESS - elif [ $retval -ne $SUCCESS ]; then + elif [ $retval -ne $DIALOG_OK ]; then # # Ask a series of questions to pre-fill the editor screen. # @@ -431,7 +431,7 @@ while :; do f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" # Exit if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || f_die + [ $retval -eq $DIALOG_OK ] || f_die case "$mtag" in X) # Exit @@ -450,7 +450,7 @@ while :; do f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" # Loop if user has either pressed ESC or chosen Cancel/No - [ $retval -eq $SUCCESS ] || continue + [ $retval -eq $DIALOG_OK ] || continue [ "$mtag" = "X $msg_exit" ] && continue Index: usr.sbin/bsdconfig/usermgmt/usermgmt =================================================================== --- usr.sbin/bsdconfig/usermgmt/usermgmt (revision 256169) +++ usr.sbin/bsdconfig/usermgmt/usermgmt (working copy) @@ -100,7 +100,7 @@ dialog_menu_main() f_dialog_menutag_store "$menu_choice" # Only update default-item on success - [ $retval -eq 0 ] && f_dialog_default_store "$menu_choice" + [ $retval -eq $DIALOG_OK ] && f_dialog_default_store "$menu_choice" return $retval } @@ -136,11 +136,10 @@ while :; do f_dialog_menutag_fetch mtag f_dprintf "retval=%u mtag=[%s]" $retval "$mtag" - if [ $retval -eq 2 ]; then - # The Help button was pressed + if [ $retval -eq $DIALOG_HELP ]; then f_show_help "$USERMGMT_HELPFILE" continue - elif [ $retval -ne $SUCCESS ]; then + elif [ $retval -ne $DIALOG_OK ]; then f_die fi Index: usr.sbin/bsdinstall/bsdinstall =================================================================== --- usr.sbin/bsdinstall/bsdinstall (revision 256169) +++ usr.sbin/bsdinstall/bsdinstall (working copy) @@ -28,6 +28,7 @@ : ${BSDINSTALL_LOG="/tmp/bsdinstall_log"}; export BSDINSTALL_LOG : ${BSDINSTALL_TMPETC="/tmp/bsdinstall_etc"}; export BSDINSTALL_TMPETC +: ${BSDINSTALL_TMPBOOT="/tmp/bsdinstall_boot"}; export BSDINSTALL_TMPBOOT : ${PATH_FSTAB="$BSDINSTALL_TMPETC/fstab"}; export PATH_FSTAB : ${BSDINSTALL_DISTDIR="/usr/freebsd-dist"}; export BSDINSTALL_DISTDIR : ${BSDINSTALL_CHROOT="/mnt"}; export BSDINSTALL_CHROOT @@ -35,5 +36,6 @@ VERB=${1:-auto}; shift [ -d "$BSDINSTALL_TMPETC" ] || mkdir -p "$BSDINSTALL_TMPETC" +[ -d "$BSDINSTALL_TMPBOOT" ] || mkdir -p "$BSDINSTALL_TMPBOOT" echo "Running installation step: $VERB $@" >> "$BSDINSTALL_LOG" exec "/usr/libexec/bsdinstall/$VERB" "$@" 2>> "$BSDINSTALL_LOG" Index: usr.sbin/bsdinstall/scripts/Makefile =================================================================== --- usr.sbin/bsdinstall/scripts/Makefile (revision 256169) +++ usr.sbin/bsdinstall/scripts/Makefile (working copy) @@ -2,7 +2,7 @@ SCRIPTS= auto adduser checksum config docsinstall hostname jail keymap \ mirrorselect mount netconfig netconfig_ipv4 netconfig_ipv6 rootpass \ - script services time umount wlanconfig + script services time umount wlanconfig zfsboot BINDIR= /usr/libexec/bsdinstall NO_MAN= true Index: usr.sbin/bsdinstall/scripts/auto =================================================================== --- usr.sbin/bsdinstall/scripts/auto (revision 256169) +++ usr.sbin/bsdinstall/scripts/auto (working copy) @@ -93,24 +93,46 @@ fi rm $PATH_FSTAB touch $PATH_FSTAB -dialog --backtitle "FreeBSD Installer" --title "Partitioning" --extra-button \ - --extra-label "Manual" --ok-label "Guided" --cancel-label "Shell" \ - --yesno "Would you like to use the guided partitioning tool (recommended for beginners) or to set up partitions manually (experts)? You can also open a shell and set up partitions entirely by hand." 0 0 +PMODES="\ +Guided \"Partitioning Tool (Recommended for Beginners)\" \ +Manual \"Manually Configure Partitions (Expert)\" \ +Shell \"Open a shell and partition by hand\"" -case $? in -0) # Guided +CURARCH=$( uname -m ) +case $CURARCH in + amd64|i386) # Booting ZFS Supported + PMODES="$PMODES ZFS \"Automatic Root-on-ZFS (Experimental)\"" + ;; + *) # Booting ZFS Unspported + ;; +esac + +exec 3>&1 +PARTMODE=`echo $PMODES | xargs dialog --backtitle "FreeBSD Installer" \ + --title "Partitioning" \ + --menu "How would you like to partition your disk?" \ + 0 0 0 2>&1 1>&3` +if [ $? -eq $DIALOG_CANCEL ]; then exit 1; fi +exec 3>&- + +case "$PARTMODE" in +"Guided") # Guided bsdinstall autopart || error bsdinstall mount || error ;; -1) # Shell +"Shell") # Shell clear echo "Use this shell to set up partitions for the new system. When finished, mount the system at $BSDINSTALL_CHROOT and place an fstab file for the new system at $PATH_FSTAB. Then type 'exit'. You can also enter the partition editor at any time by entering 'bsdinstall partedit'." sh 2>&1 ;; -3) # Manual +"Manual") # Manual bsdinstall partedit || error bsdinstall mount || error ;; +"ZFS") # ZFS + bsdinstall zfsboot || error + bsdinstall mount || error + ;; *) error ;; Index: usr.sbin/bsdinstall/scripts/config =================================================================== --- usr.sbin/bsdinstall/scripts/config (revision 256169) +++ usr.sbin/bsdinstall/scripts/config (working copy) @@ -31,6 +31,11 @@ rm $BSDINSTALL_TMPETC/rc.conf.* cp $BSDINSTALL_TMPETC/* $BSDINSTALL_CHROOT/etc +cat $BSDINSTALL_TMPBOOT/loader.conf.* >> $BSDINSTALL_TMPBOOT/loader.conf +rm $BSDINSTALL_TMPBOOT/loader.conf.* + +cp $BSDINSTALL_TMPBOOT/* $BSDINSTALL_CHROOT/boot + # Set up other things from installed config chroot $BSDINSTALL_CHROOT /usr/bin/newaliases Index: usr.sbin/bsdinstall/scripts/keymap =================================================================== --- usr.sbin/bsdinstall/scripts/keymap (revision 256169) +++ usr.sbin/bsdinstall/scripts/keymap (working copy) @@ -1,6 +1,7 @@ #!/bin/sh #- # Copyright (c) 2011 Nathan Whitehorn +# Copyright (c) 2013 Devin Teske # All rights reserved. # # Redistribution and use in source and binary forms, with or without @@ -25,11 +26,159 @@ # SUCH DAMAGE. # # $FreeBSD$ +# +############################################################ INCLUDES + +BSDCFG_SHARE="/usr/share/bsdconfig" +. $BSDCFG_SHARE/common.subr || exit 1 +f_dprintf "%s: loading includes..." "$0" +f_include $BSDCFG_SHARE/dialog.subr -kbdcontrol -d >/dev/null 2>&1 -if [ $? -eq 0 ]; then - dialog --backtitle "FreeBSD Installer" --title "Keymap Selection" \ - --yesno "Would you like to set a non-default key mapping for your keyboard?" 0 0 || exit 0 - exec 3>&1 - kbdmap 2>&1 1>&3 | grep 'keymap=' > $BSDINSTALL_TMPETC/rc.conf.keymap -fi +############################################################ CONFIGURATION + +# +# Default file to store keymap selection in +# +: ${KEYMAPFILE:=$BSDINSTALL_TMPETC/rc.conf.keymap} + +# +# Default path to keymap INDEX containing descriptions +# +: ${MAPDESCFILE:=/usr/share/syscons/keymaps/INDEX.keymaps} + +############################################################ GLOBALS + +# +# Strings that should be moved to an i18n file and loaded with f_include_lang() +# +msg_change_keymap="Change keymap" +msg_current_keyboard_mapping_is="The current keyboard mapping is:\n%s" +msg_default="default" +msg_freebsd_installer="FreeBSD Installer" +msg_keymap_selection="Keymap Selection" +msg_ok="OK" +msg_test_keymap="Test keymap" +msg_test_the_keymap_by_typing="Test the keymap by typing letters, numbers, and symbols. Characters should match the labels on the keyboard keys.\nPress Enter to stop testing." +msg_use_this_keymap="Use this keymap" + +############################################################ FUNCTIONS + +# dialog_menu_main +# +# Display the dialog(1)-based application main menu. +# +dialog_menu_main() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt= # Calculated below + local hline= + + local mapdesc="$msg_default" keymap + if [ -s "$KEYMAPFILE" ]; then + # Get the current keymap and a description to display + keymap=$( awk '/keymap=/{sub(/^.*=/,"");gsub(/"/,"");print}' \ + "$KEYMAPFILE" ) + mapdesc=$( awk -v keymap="$keymap" len=${#keymap} ' + substr($0,0,len+4)==keymap":en:"{ + if (length($0) < len+5) continue + print substr($0, len+5) " (" keymap ")" + exit + }' "$MAPDESCFILE" ) + fi + prompt=$( printf "$msg_current_keyboard_mapping_is" "$mapdesc" ) + + local height width + f_dialog_buttonbox_size height width \ + "$title" "$btitle" "$prompt" "$hline" + + [ $width -ge 56 ] || width=56 + + $DIALOG \ + --title "$title" \ + --backtitle "$btitle" \ + --ok-label "$msg_use_this_keymap" \ + --cancel-label "$msg_change_keymap" \ + --extra-button \ + --extra-label "$msg_test_keymap" \ + --yesno "$prompt" $height $width \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD +} + +# dialog_keymap_test +# +# Display an input box (without cancel button) for the user to test keyboard +# input and return. Always returns success. +# +dialog_keymap_test() +{ + local title= # Calculated below + local btitle= # Calculated below + local prompt="$msg_test_the_keymap_by_typing" + local hline= + + f_dialog_title "$msg_test_keymap" + title="$DIALOG_TITLE" + btitle="$DIALOG_BACKTITLE" + f_dialog_title_restore + + local height width + f_dialog_inputbox_size height width \ + "$title" "$btitle" "$prompt" "" "$hline" + + $DIALOG \ + --title "$title" \ + --backtitle "$btitle" \ + --hline "$hline" \ + --ok-label "$msg_ok" \ + --no-cancel \ + --inputbox "$prompt" \ + $height $width \ + 2>/dev/null >&$DIALOG_TERMINAL_PASSTHRU_FD + + return $DIALOG_OK +} + +############################################################ MAIN + +# +# Initialize +# +f_dialog_title "$msg_keymap_selection" +f_dialog_backtitle "$msg_freebsd_installer" + +# +# Die immediately if we can't dump the current keyboard map +# +error=$( kbdcontrol -d 2>&1 > /dev/null ) || f_die $FAILURE "%s" "$error" + +# Capture Ctrl-C for clean-up +trap 'rm -f $KEYMAPFILE; exit $FAILURE' SIGINT + +# +# Loop until the user has finalized their selection +# +while :; do + dialog_menu_main + retval=$? + f_dprintf "retval=%u" $retval + + [ $retval -eq $DIALOG_OK ] && break + + case $retval in + $DIALOG_ESC) + rm -f "$KEYMAPFILE" + exit 1 ;; # Exit with an error so bsdinstall restarts + $DIALOG_CANCEL) + # User chose ``Change keymap'' option + kbdmap 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD | + grep 'keymap=' > "$KEYMAPFILE" ;; + $DIALOG_EXTRA) + # User chose ``Test keymap'' option + dialog_keymap_test ;; + esac +done + +################################################################################ +# END +################################################################################ Index: usr.sbin/bsdinstall/scripts/netconfig =================================================================== --- usr.sbin/bsdinstall/scripts/netconfig (revision 256169) +++ usr.sbin/bsdinstall/scripts/netconfig (working copy) @@ -41,11 +41,19 @@ DIALOG_TAGS="" : ${DIALOG_ITEM_HELP=4} : ${DIALOG_ESC=255} +# Do a dirty check to see if this a wireless interface -- there should be a +# better way +is_wireless_if() { + ifconfig $1 | grep -q 'media: IEEE 802.11 Wireless' +} + + for IF in `ifconfig -l`; do test "$IF" = "lo0" && continue (ifconfig -g wlan | egrep -wq $IF) && continue INTERFACES="$INTERFACES $IF" DESC=`sysctl -n dev.$(echo $IF | sed -E 's/([[:alpha:]]*)([[:digit:]]*)/\1.\2/g').%desc` + is_wireless_if $IF && echo $DESC | grep -iqv wireless && DESC="Wireless $DESC" DIALOG_TAGS="$DIALOG_TAGS $IF \"$DESC\"" done @@ -63,10 +71,8 @@ exec 3>&- : > $BSDINSTALL_TMPETC/._rc.conf.net -# Do a dirty check to see if this a wireless interface -- there should be a -# better way IFCONFIG_PREFIX="" -if ifconfig $INTERFACE | grep -q 'media: IEEE 802.11 Wireless'; then +if is_wireless_if $INTERFACE; then NEXT_WLAN_IFACE=wlan0 # XXX echo wlans_$INTERFACE=\"$NEXT_WLAN_IFACE\" >> $BSDINSTALL_TMPETC/._rc.conf.net IFCONFIG_PREFIX="WPA " @@ -90,14 +96,18 @@ case $? in esac if [ ${IPV4_AVAIL} -eq 1 ]; then - dialog --backtitle 'FreeBSD Installer' --title 'Network Configuration' \ - --yesno 'Would you like to configure IPv4 for this interface?' 0 0 - if [ $? -eq $DIALOG_OK ]; then - bsdinstall netconfig_ipv4 ${INTERFACE} "${IFCONFIG_PREFIX}" || \ - exec $0 - else - IPV4_AVAIL=0 - fi + bsdinstall netconfig_ipv4 ${INTERFACE} "${IFCONFIG_PREFIX}" + case $? in + 0) #OK + break + ;; + 3) #No ipv4 + IPV4_AVAIL=0 + ;; + *) #Error + exec $0 + ;; + esac fi # In case wlanconfig left an option and we do not support IPv4 we need to write # it out on its own. We cannot write it out with IPv6 as that suffix. Index: usr.sbin/bsdinstall/scripts/netconfig_ipv4 =================================================================== --- usr.sbin/bsdinstall/scripts/netconfig_ipv4 (revision 256169) +++ usr.sbin/bsdinstall/scripts/netconfig_ipv4 (working copy) @@ -43,32 +43,49 @@ case "${INTERFACE}" in ;; esac -dialog --backtitle 'FreeBSD Installer' --title 'Network Configuration' --yesno 'Would you like to use DHCP to configure this interface?' 0 0 -if [ $? -eq $DIALOG_OK ]; then - echo ifconfig_$INTERFACE=\"${IFCONFIG_PREFIX}DHCP\" >> $BSDINSTALL_TMPETC/._rc.conf.net - - if [ ! -z $BSDINSTALL_CONFIGCURRENT ]; then - dialog --backtitle 'FreeBSD Installer' --infobox "Acquiring DHCP lease..." 0 0 - dhclient $INTERFACE 2>> $BSDINSTALL_LOG - if [ $? -ne 0 ]; then - dialog --backtitle 'FreeBSD Installer' --msgbox "DHCP lease acquisition failed." 0 0 - exec $0 ${INTERFACE} "${IFCONFIG_PREFIX}" - fi - fi - exit 0 -fi - IP_ADDRESS=`ifconfig $INTERFACE inet | awk '/inet/ {printf("%s\n", $2); }'` NETMASK=`ifconfig $INTERFACE inet | awk '/inet/ {printf("%s\n", $4); }'` ROUTER=`netstat -rn -f inet | awk '/default/ {printf("%s\n", $2);}'` exec 3>&1 -IF_CONFIG=$(dialog --backtitle 'FreeBSD Installer' --title 'Network Configuration' --form 'Static Network Interface Configuration' 0 0 0 \ + + +IF_CONFIG=$(dialog --backtitle 'FreeBSD Installer' \ + --title 'Network Configuration' \ + --extra-button --extra-label "No IPv4" --defaultno \ + --cancel-label "DHCP" --ok-label "Static" \ + --form 'Network Interface Configuration' 0 0 0 \ 'IP Address' 1 0 "$IP_ADDRESS" 1 20 16 0 \ 'Subnet Mask' 2 0 "$NETMASK" 2 20 16 0 \ 'Default Router' 3 0 "$ROUTER" 3 20 16 0 \ 2>&1 1>&3) -if [ $? -eq $DIALOG_CANCEL ]; then exit 1; fi +case $? in + 0) # Static + break + ;; + 1) # DHCP + echo ifconfig_$INTERFACE=\"${IFCONFIG_PREFIX}DHCP\" >> \ + $BSDINSTALL_TMPETC/._rc.conf.net + + if [ ! -z $BSDINSTALL_CONFIGCURRENT ]; then + dialog --backtitle 'FreeBSD Installer' \ + --infobox "Acquiring DHCP lease..." 0 0 + dhclient $INTERFACE 2>> $BSDINSTALL_LOG + if [ $? -ne 0 ]; then + dialog --backtitle 'FreeBSD Installer' \ + --msgbox "DHCP lease acquisition failed." 0 0 + exec $0 ${INTERFACE} "${IFCONFIG_PREFIX}" + fi + fi + exit 0 + ;; + 3) # No IPv4 + exit 3 + ;; + *) + error + ;; +esac exec 3>&- echo $INTERFACE $IF_CONFIG | @@ -85,4 +102,3 @@ if [ ! -z $BSDINSTALL_CONFIGCURRENT ]; then route add -inet default $defaultrouter fi fi - Index: usr.sbin/bsdinstall/scripts/services =================================================================== --- usr.sbin/bsdinstall/scripts/services (revision 256169) +++ usr.sbin/bsdinstall/scripts/services (working copy) @@ -46,22 +46,23 @@ DAEMONS=$(dialog --backtitle "FreeBSD Installer" \ moused "PS/2 mouse pointer on console" ${moused_enable:-off} \ ntpd "Synchronize system and network time" ${ntpd_enable:-off} \ powerd "Adjust CPU frequency dynamically if supported" ${powerd_enable:-off} \ + dumpdev "Would you like to enable crash dumps to /var ?" ${dumpdev:-on} \ 2>&1 1>&3) exec 3>&- +local havedump= for daemon in $DAEMONS; do + if [ "$daemon" == "dumpdev" ]; then + havedump=1 + echo \# Set dumpdev to \"AUTO\" to enable crash dumps, \ + \"NO\" to disable >> \ + $BSDINSTALL_TMPETC/rc.conf.services + echo dumpdev=\"AUTO\" >> $BSDINSTALL_TMPETC/rc.conf.services + continue + fi echo ${daemon}_enable=\"YES\" >> $BSDINSTALL_TMPETC/rc.conf.services done -echo \# Set dumpdev to \"AUTO\" to enable crash dumps, \"NO\" to disable >> \ - $BSDINSTALL_TMPETC/rc.conf.services - -dialog --backtitle "FreeBSD Installer" --title "Dumpdev Configuration" \ - --nocancel --yesno \ - "Would you like to enable crash dumps? If you start having problems with the system it can help the FreeBSD developers debug the problem. But the crash dumps can take up a lot of disk space in /var." 0 0 - -if [ $? -eq $DIALOG_OK ]; then - echo dumpdev=\"AUTO\" >> $BSDINSTALL_TMPETC/rc.conf.services -else +if [ ! "$havedump" ]; then echo dumpdev=\"NO\" >> $BSDINSTALL_TMPETC/rc.conf.services fi Index: usr.sbin/bsdinstall/scripts/zfsboot =================================================================== --- usr.sbin/bsdinstall/scripts/zfsboot (revision 0) +++ usr.sbin/bsdinstall/scripts/zfsboot (working copy) @@ -0,0 +1,956 @@ +#!/bin/sh +#- +# Copyright (c) 2013 Allan Jude +# Copyright (c) 2013 Devin Teske +# All rights reserved. +# +# Redistribution and use in source and binary forms, with or without +# modification, are permitted provided that the following conditions +# are met: +# 1. Redistributions of source code must retain the above copyright +# notice, this list of conditions and the following disclaimer. +# 2. Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# +# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. +# +# $FreeBSD$ +# +############################################################ INCLUDES + +BSDCFG_SHARE="/usr/share/bsdconfig" +. $BSDCFG_SHARE/common.subr || exit 1 +f_dprintf "%s: loading includes..." "$0" +f_include $BSDCFG_SHARE/device.subr +f_include $BSDCFG_SHARE/dialog.subr + +############################################################ CONFIGURATION + +# +# Default name of the boot-pool +# +: ${ZFSBOOT_POOL_NAME:=zroot} + +# +# Default name for the boot environment parent dataset +# +: ${ZFSBOOT_BEROOT_NAME:=bootenv} + +# +# Default name for the primany boot environment +# +: ${ZFSBOOT_BOOTFS_NAME:=default} + +# +# Default Virtual Device (vdev) type to create +# +: ${ZFSBOOT_VDEV_TYPE:=stripe} + +# +# Should we use gnop(8) to configure a transparent mapping to 4K sectors? +# +: ${ZFSBOOT_GNOP_4K_FORCE_ALIGN:=1} + +# +# Should we use geli(8) to encrypt the drives? +# +: ${ZFSBOOT_GELI_ENCRYPTION:=} + +# +# Default name the unencrypted pool when using geli(8) to encrypt the drives +# +: ${ZFSBOOT_GELI_POOL_NAME:=bootpool} + +# +# Default size for the unencrypted boot pool when using geli(8) +# +: ${ZFSBOOT_GELI_BOOT_SIZE:=2g} + +# +# Default path to the geli(8) keyfile used in drive encryption +# +: ${ZFSBOOT_GELI_KEY_FILE:=/boot/encryption.key} + +# +# Default disks to use (always empty unless being scripted) +# +: ${ZFSBOOT_DISKS:=} + +# +# Default partitioning scheme to use on disks +# +: ${ZFSBOOT_PARTITION_SCHEME:=GPT} + +# +# How much swap to put on each block device in the boot zpool +# NOTE: Value passed to gpart(8); which supports SI unit suffixes. +# +: ${ZFSBOOT_SWAP_SIZE:=2g} + +# +# Default ZFS layout for root zpool +# +# NOTE: Requires /tmp, /var/tmp, /$ZFSBOOT_BOOTFS_NAME/$ZFSBOOT_BOOTFS_NAME +# NOTE: Anything after pound/hash character [#] is ignored as a comment. +# +f_isset ZFSBOOT_DATASETS || ZFSBOOT_DATASETS=" + # DATASET OPTIONS (comma or space separated; or both) + + # Boot Environment [BE] root and default boot dataset + /$ZFSBOOT_BEROOT_NAME mountpoint=none + /$ZFSBOOT_BEROOT_NAME/$ZFSBOOT_BOOTFS_NAME mountpoint=/ + + # Compress /tmp, allow exec but not setuid + /tmp mountpoint=/tmp,compression=lz4,exec=on,setuid=off + + # Don't mount /usr so that 'base' files go to the BEROOT + /usr mountpoint=/usr,canmount=off + + /usr/local # local files (i.e. from packages) separate from base system + + # Home directories separated so they are common to all BEs + /usr/home setuid=off + + # Ports tree + /usr/ports compression=lz4,setuid=off + /usr/ports/distfiles compression=off,exec=off,setuid=off + /usr/ports/packages compression=off,exec=off,setuid=off + + # Source tree (compressed) + /usr/src compression=lz4,exec=off,setuid=off + /usr/obj # Object files + + # Create /var and friends + /var mountpoint=/var + /var/crash compression=lz4,exec=off,setuid=off + /var/db exec=off,setuid=off + /var/db/pkg compression=lz4,exec=off,setuid=off + /var/empty exec=off,setuid=off + /var/log compression=lz4,exec=off,setuid=off + /var/mail compression=lz4,exec=off,setuid=off + /var/run exec=off,setuid=off + /var/tmp compression=lz4,exec=on,setuid=off +" # END-QUOTE + +############################################################ GLOBALS + +# +# Strings that should be moved to an i18n file and loaded with f_include_lang() +# +hline_alnum_arrows_punc_tab_enter="Use alnum, arrows, punctuation, TAB or ENTER" +hline_arrows_space_tab_enter="Use arrows, SPACE, TAB or ENTER" +hline_arrows_tab_enter="Press arrows, TAB or ENTER" +msg_back="Back" +msg_cancel="Cancel" +msg_configure_options="Configure Options:" +msg_create="Install" +msg_create_desc="Proceed with Installation" +msg_create_help="Create ZFS boot pool with displayed options" +msg_detailed_disk_info="gpart(8) show %s:\n%s\n\ncamcontrol(8) inquiry %s:\n%s\n\n\ncamcontrol(8) identify %s:\n%s\n" +msg_disk_info="Disk Info" +msg_disk_info_help="Get detailed information on disk device(s)" +msg_disks_to_use="Disks To Use" +msg_disks_to_use_help="Choose which disks to use for the Virtual Device (Required)" +msg_force_4k_sectors="Force 4K Sectors?" +msg_force_4k_sectors_help="Use gnop(8) to configure forced 4K sector alignment" +msg_geli_encryption="Encrypt Disks?" +msg_geli_encryption_help="Use geli(8) to encrypt all data partitions" +msg_freebsd_installer="FreeBSD Installer" +msg_invalid_virtual_device_type="Invalid Virtual Device type \`%s'" +msg_last_chance_are_you_sure="Last Chance! Are you sure you want to destroy the current contents of the following disks:\n%s" +msg_last_chance_are_you_sure_color="\\\\ZrLast Chance!\\\\ZR Are you \\\\Z1sure\\\\Zn you want to \\\\Zr\\\\Z1destroy\\\\Zn the current contents of the following disks:\n%s" +msg_mirror_desc="Mirror - n-Way Mirroring" +msg_mirror_help="[2+ Disks] Mirroring provides the best performance, but the least storage" +msg_no="NO" +msg_no_disks_present_to_configure="No disk(s) present to configure" +msg_no_disks_selected="No disks selected." +msg_not_enough_disks_selected="Not enough disks selected (minimum %u)" +msg_ok="OK" +msg_partition_scheme="Partition Scheme" +msg_partition_scheme_help="Toggle between GPT and MBR partitioning schemes" +msg_please_enter_a_name_for_your_zpool="Please enter a name for your zpool:" +msg_please_enter_amount_of_swap_space="Please enter amount of swap space (SI-Unit suffixes\nrecommended; e.g., \`2g' for 2 Gigabytes):" +msg_please_select_one_or_more_disks="Please select one or more disks to create a zpool:" +msg_pool_name="Pool Name" +msg_pool_name_cannot_be_empty="Pool name cannot be empty." +msg_pool_name_help="Customize the name of the zpool to be created (Required)" +msg_raidz1_desc="RAID-Z1 - Single Redundant RAID" +msg_raidz1_help="[3+ Disks] Withstand failure of 1 disk. Recommended for: 3, 5 or 9 disks" +msg_raidz2_desc="RAID-Z2 - Double Redundant RAID" +msg_raidz2_help="[4+ Disks] Withstand failure of 2 disks. Recommended for: 4, 6 or 10 disks" +msg_raidz3_desc="RAID-Z3 - Triple Redundant RAID" +msg_raidz3_help="[5+ Disks] Withstand failure of 3 disks. Recommended for: 5, 7 or 11 disks" +msg_rescan_devices="Rescan Devices" +msg_rescan_devices_help="Scan for device changes" +msg_select="Select" +msg_select_a_disk_device="Select a disk device" +msg_select_virtual_device_type="Select Virtual Device type:" +msg_stripe_desc="Stripe - No Redundancy" +msg_stripe_help="[1+ Disks] Striping provides maximum storage but no redundancy" +msg_swap_size="Swap Size" +msg_swap_size_help="Customize how much swap space is allocated to each selected disk" +msg_yes="YES" +msg_zfs_configuration="ZFS Configuration" +msg_zfs_vdev_type="ZFS VDev Type" +msg_zfs_vdev_type_help="Select type of ZFS Virtual Device to create" + +############################################################ FUNCTIONS + +# dialog_menu_main +# +# Display the dialog(1)-based application main menu. +# +dialog_menu_main() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_configure_options" + local force4k="$msg_no" + local usegeli="$msg_no" + [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ] && force4k="$msg_yes" + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && usegeli="$msg_yes" + local menu_list=" + '>>> $msg_create' '$msg_create_desc' + '$msg_create_help' + '- $msg_rescan_devices' '*' + '$msg_rescan_devices_help' + '- $msg_disk_info' '*' + '$msg_disk_info_help' + '1 $msg_pool_name' '$ZFSBOOT_POOL_NAME' + '$msg_pool_name_help' + '2 $msg_disks_to_use' '$ZFSBOOT_DISKS' + '$msg_disks_to_use_help' + '3 $msg_zfs_vdev_type' '$ZFSBOOT_VDEV_TYPE' + '$msg_zfs_vdev_type_help' + '4 $msg_force_4k_sectors' '$force4k' + '$msg_force_4k_sectors_help' + '5 $msg_geli_encryption' '$usegeli' + '$msg_geli_encryption_help' + '6 $msg_partition_scheme' '$ZFSBOOT_PARTITION_SCHEME' + '$msg_partition_scheme_help' + '7 $msg_swap_size' '$ZFSBOOT_SWAP_SIZE' + '$msg_swap_size_help' + " # END-QUOTE + local defaultitem= # Calculated below + local hline="$hline_alnum_arrows_punc_tab_enter" + + local height width rows + eval f_dialog_menu_with_help_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $menu_list + + # Obtain default-item from previously stored selection + f_dialog_default_fetch defaultitem + + local menu_choice + menu_choice=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --item-help \ + --ok-label \"\$msg_select\" \ + --cancel-label \"\$msg_cancel\" \ + --default-item \"\$defaultitem\" \ + --menu \"\$prompt\" \ + $height $width $rows \ + $menu_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) + local retval=$? + f_dialog_data_sanitize menu_choice + f_dialog_menutag_store "$menu_choice" + + # Only update default-item on success + [ $retval -eq $DIALOG_OK ] && f_dialog_default_store "$menu_choice" + + return $retval +} + +# dialog_edit_disks +# +# Edit the list of disks to be used by the ZFS boot pool. +# +dialog_edit_disks() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_please_select_one_or_more_disks" + local check_list= # Calculated below + local hline="$hline_arrows_space_tab_enter" + local dev vardev disks= + + # + # Get a [new] list of disk devices + # + f_device_find "" $DEVICE_TYPE_DISK disks + if [ ! "$disks" ]; then + f_show_msg "$msg_no_disks_present_to_configure" + return $FAILURE + fi + + # Lets sort the disks array to be more user friendly + disks=$( echo "$disks" | tr ' ' '\n' | sort | tr '\n' ' ' ) + + # + # Loop through the list of selected disks and create temporary local + # variables mapping their status onto an up-to-date list of disks. + # + for dev in $ZFSBOOT_DISKS; do + f_str2varname "$dev" vardev + local _${vardev}_status=on + done + + # + # Create the checklist menu of discovered disk devices + # + local on_off + for dev in $disks; do + local desc= + device_$dev get desc desc + f_shell_escape "$desc" desc + f_str2varname "$dev" vardev + f_getvar _${vardev}_status:-off on_off + check_list="$check_list '$dev' '$desc' $on_off" + done + + # + # Prompt the user to check some disks + # + local height width rows + eval f_dialog_checklist_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $check_list + disks=$( eval $DIALOG \ + --title \"\$DIALOG_TITLE\" \ + --backtitle \"\$DIALOG_BACKTITLE\" \ + --hline \"\$hline\" \ + --ok-label \"\$msg_ok\" \ + --cancel-label \"\$msg_cancel\" \ + --checklist \"\$prompt\" \ + $height $width $rows \ + $check_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) || return $? + # Exit if user either pressed ESC or chose Cancel/No + f_dialog_data_sanitize disks + + ZFSBOOT_DISKS="$disks" + + return $DIALOG_OK +} + +# dialog_menu_vdev +# +# Prompt the user to select a a Virtual Device type. +# +dialog_menu_vdev() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_select_virtual_device_type" + + # Make sure [potentially scripted] selections are real + real_disks= + for disk in $ZFSBOOT_DISKS; do + f_struct device_$disk && real_disks="$real_disks $disk" + done + # Make sure we have at least one real disk selected + ndisks=$( set -- $real_disks; echo $# ) + + local menu_list=" + 'stripe' '$msg_stripe_desc' '$msg_stripe_help' + 'mirror' '$msg_mirror_desc' '$msg_mirror_help' + 'raidz1' '$msg_raidz1_desc' '$msg_raidz1_help' + 'raidz2' '$msg_raidz2_desc' '$msg_raidz2_help' + 'raidz3' '$msg_raidz3_desc' '$msg_raidz3_help' + " # END-QUOTE + + local defaultitem="$ZFSBOOT_VDEV_TYPE" + local hline="$hline_arrows_tab_enter" + + local height width rows + eval f_dialog_menu_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $menu_list + + local menu_choice + menu_choice=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --ok-label \"\$msg_ok\" \ + --cancel-label \"\$msg_cancel\" \ + --item-help \ + --default-item \"\$defaultitem\" \ + --menu \"\$prompt\" \ + $height $width $rows \ + $menu_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) || return $FAILURE + f_dialog_data_sanitize menu_choice + + ZFSBOOT_VDEV_TYPE="$menu_choice" +} + +# zfs_create_diskpart $disk $index +# +# For each block device to be used in the zpool, rather than just create the +# zpool with the raw block devices (e.g., da0, da1, etc.) we create partitions +# so we can have some real swap. This also provides wiggle room incase your +# replacement drivers do not have the exact same sector counts. +# +# NOTE: The MBR layout is more complicated (GPT is preferred). +# +zfs_create_diskpart() +{ + local disk="$1" index="$2" + local funcname=zfs_create_diskpart + local disksize partsize + + # Check arguments + [ "$disk" -a "$index" ] || return $FAILURE + + # + # Destroy whatever partition layout is currently on disk. + # NOTE: `-F' required to destroy if partitions still exist. + # NOTE: Failure is ok here, blank disk will have nothing to destroy. + # + f_quietly gpart destroy -F $disk + f_quietly zpool labelclear -f /dev/$disk # Kill it with fire + + # Make doubly-sure backup GPT is destroyed + f_quietly gpart create -s gpt $disk || return $FAILURE + f_quietly gpart destroy -F $disk || return $FAILURE + + # Calculate partition size given desired amount of swap + device_$disk get capacity disksize || return $FAILURE + partsize=$(( $disksize - $swapsize )) + + # + # Lay down the desired type of partition scheme + # + local bootpart targetpart setsize= + case "$ZFSBOOT_PARTITION_SCHEME" in + ""|GPT) + # + # 1. Create GPT layout using labels + # + gpart create -s gpt $disk || return $FAILURE + + # + # 2. Add small freebsd-boot partition labeled `boot#' + # + gpart add -l gptboot$index -t freebsd-boot -s 512k $disk || + return $FAILURE + gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 $disk || + return $FAILURE + + # zpool will use the `zfs#' GPT labels + bootpart=p2 targetpart=p2 + + # Change things around if we are using GELI + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + bootpart=p2 targetpart=p3 + partsize=$(( $partsize - $gelisize )) + gpart add -l boot$index -t freebsd-zfs \ + -s ${gelisize}b -a 1m $disk || return $FAILURE + zpool labelclear -f /dev/$disk$bootpart # Pedantic + fi + + # + # 3. Add freebsd-zfs partition labeled `zfs#' for zpool + # NOTE: Using above calculated partsize to leave room for swap. + # + [ $swapsize -gt 0 ] && setsize="-s ${partsize}b" + gpart add -l zfs$index -t freebsd-zfs $setsize -a 1m $disk || + return $FAILURE + f_quietly zpool labelclear -f /dev/$disk$targetpart # Pedantic + + # + # 4. Add freebsd-swap partition labeled `swap#' + # + if [ $swapsize -gt 0 ]; then + gpart add -l swap$index -t freebsd-swap -a 1m $disk || + return $FAILURE + # Update fstab(5) + printf "$fstab_fmt" \ + /dev/gpt/swap$index none swap sw 0 0 \ + >> $BSDINSTALL_TMPETC/fstab || return $FAILURE + fi + ;; + + MBR) + # + # 1. Create MBR layout (no labels) + # + gpart create -s mbr $disk || return $FAILURE + gpart bootcode -b /boot/boot0 $disk || return $FAILURE + + # + # 2. Add freebsd slice with all available space + # + gpart add -t freebsd $disk || return $FAILURE + gpart set -a active -i 1 $disk || return $FAILURE + f_quietly gpart destroy -F ${disk}s1 # Pedantic + + # + # 3. Write BSD sceme to the freebsd slice + # + gpart create -s BSD ${disk}s1 || return $FAILURE + + # zpool will use s1a (no labels) + bootpart=s1a targetpart=s1a + + # Change things around if we are using GELI + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + bootpart=s1a targetpart=s1d + partsize=$(( $partsize - $gelisize )) + gpart add -t freebsd-zfs -s ${gelisize}b ${disk}s1 || + return $FAILURE + # Pedantically nuke anything old labels + f_quietly zpool labelclear -f /dev/$disk$bootpart + fi + + # + # 4. Partition the BSD slice for ZFS + # NOTE: Using above calculated partsize to leave room for swap. + # + [ $swapsize -gt 0 ] && setsize="-s ${partsize}b" + gpart add -t freebsd-zfs $setsize ${disk}s1 || return $FAILURE + f_quietly zpool labelclear -f /dev/$disk$targetpart # Pedantic + + # + # 5. Add freebsd-swap partition + # + if [ $swapsize -gt 0 ]; then + gpart add -t freebsd-swap ${disk}s1 || return $FAILURE + # Update fstab(5) + printf "$fstab_fmt" /dev/${disk}s1b none swap sw 0 0 \ + >> $BSDINSTALL_TMPETC/fstab || return $FAILURE + fi + ;; + + *) + printf "%s: %s is an unsupported partition scheme" \ + "$funcname" "$ZFSBOOT_PARTITION_SCHEME" >&2 + return $FAILURE + + esac # $ZFSBOOT_PARTITION_SCHEME + + return $SUCCESS +} + +# zfs_create_boot $poolname $vdev_type $real_disks ... +# +# Creates boot pool and dataset layout. Returns error if something goes wrong. +# Errors are printed to stderr for collection and display. +# +zfs_create_boot() +{ + local poolname="$1" vdev_type="$2" + local fstab_fmt="%s\t\t%s\t%s\t%s\t\t%s\t%s\n" + local funcname=zfs_create_boot + + shift 2 # name vdev_type + + # We may need this later + local realdisks=$* + + # Pedantic checks; should never be seen + if [ ! "$poolname" ]; then + echo "$funcname: NULL poolname" >&2 + return $FAILURE + fi + if [ $# -lt 1 ]; then + echo "$funcname: missing disk arguments" >&2 + return $FAILURE + fi + + # Initialize fstab(5) + printf "$fstab_fmt" \ + "# Device" Mountpoint FStype Options Dump "Pass#" \ + >> $BSDINSTALL_TMPETC/fstab || return $FAILURE + + # Expand SI units in desired sizes + local swapsize gelisize + f_expand_number "$ZFSBOOT_SWAP_SIZE" swapsize || return $FAILURE + f_expand_number "$ZFSBOOT_GELI_BOOT_SIZE" gelisize || return $FAILURE + + # Prepare the disks + local n=0 + for disk in $*; do + zfs_create_diskpart $disk $n || return $FAILURE + n=$(( $n + 1 )) + done + + # MBR boot loader hack part 1 + # We have to do this early because geli gets in the way later + if [ "$ZFSBOOT_PARTITION_SCHEME" = "MBR" ]; then + for disk in $realdisks; do + dd if=/boot/zfsboot of=/dev/${disk}s1 count=1 || + return $FAILURE + done + fi + + # Forced 4k alignment support provided by Geom NOP (see gnop(8)) + local unenc_list= + if [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ]; then + local new_list= + for disk in $*; do + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + # We don't gnop the encrypted partition + # because geli will do this for us + # gnop the unencrypted disk + gnop create -S 4096 $disk$bootpart || + return $FAILURE + unenc_list="$unenc_list $disk$bootpart.nop" + else + gnop create -S 4096 $disk$targetpart || + return $FAILURE + new_list="$new_list $disk$targetpart.nop" + fi + done + set -- $new_list + else + local new_list= + for disk in $*; do + new_list="$new_list $disk$targetpart" + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && + unenc_list="$unenc_list $disk$bootpart" + done + set -- $new_list + fi + + # + # If encryption is enabled, we need to create the GEOMs + # + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + local bootvdev= + local geli_pool="$BSDINSTALL_CHROOT/$ZFSBOOT_GELI_POOL_NAME" + local key="$ZFSBOOT_GELI_KEY_FILE" + + # Create the parent directories for our unencrypted pool + f_quietly umount /mnt + mount -t tmpfs none $BSDINSTALL_CHROOT || return $FAILURE + + # Create mirror across the unencrypted partition on all disks + [ $( set -- $unenc_list; echo $# ) -gt 1 ] && bootvdev=mirror + + zpool create -o altroot=$BSDINSTALL_CHROOT \ + -m "/$ZFSBOOT_GELI_POOL_NAME" -f \ + "$ZFSBOOT_GELI_POOL_NAME" $bootvdev $unenc_list || + return $FAILURE + mkdir -p $geli_pool/boot || return $FAILURE + + # Generate an encryption key using random(4) + dd if=/dev/random of="$geli_pool/$key" bs=4096 count=1 || + return $FAILURE + + # Create the geli(8) GEOMS + local geli_list= + for disk in $realdisks; do + geli init -b -B \ + "$geli_pool/boot/$disk$targetpart.eli" \ + -e AES-XTS -K "$geli_pool/$key" -l 256 \ + -s 4096 $disk$targetpart || return $FAILURE + geli attach -k "$geli_pool/$key" $disk$targetpart || + return $FAILURE + geli_list="$geli_list $disk$targetpart.eli" + done + set -- $geli_list + zfs unmount "$ZFSBOOT_GELI_POOL_NAME" || return $FAILURE + fi + + # + # Create the ZFS pool with desired type and disk devices + # + zpool create -o altroot=$BSDINSTALL_CHROOT -m none -f \ + "$poolname" $vdev_type $* || return $FAILURE + + # Customize the zpool a bit... + zfs set checksum=fletcher4 "$poolname" || return $FAILURE + zfs set atime=off "$poolname" || return $FAILURE + + # + # Create ZFS dataset layout within the new boot pool + # + echo "$ZFSBOOT_DATASETS" | while read dataset options; do + # Skip blank lines and comments + case "$dataset" in "#"*|"") continue; esac + # Remove potential inline comments in options + options="${options%%#*}" + # Replace tabs with spaces + f_replaceall "$options" " " " " foo + # Reduce contiguous runs of space to one single space + oldoptions= + while [ "$oldoptions" != "$options" ]; do + oldoptions="$options" + f_replaceall "$options" " " " " options + done + # Replace both commas and spaces with ` -o ' + f_replaceall "$options" "[ ,]" " -o " options + # Create the dataset with desired options + zfs create ${options:+-o $options} "$poolname$dataset" || + return $FAILURE + done + + # Touch up permissions on the tmp directories + chmod 1777 $BSDINSTALL_CHROOT/tmp || return $FAILURE + chmod 1777 $BSDINSTALL_CHROOT/var/tmp || return $FAILURE + + # Create symlink(s) + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && + { ln -s $ZFSBOOT_GELI_POOL_NAME/boot $BSDINSTALL_CHROOT/boot || + return $FAILURE; } + + # Set bootfs property + zpool set bootfs="$poolname/$ZFSBOOT_BEROOT_NAME/$ZFSBOOT_BOOTFS_NAME" \ + "$poolname" || return $FAILURE + + # Export the pool(s) + zpool export "$poolname" || return $FAILURE + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && + { zpool export "$ZFSBOOT_GELI_POOL_NAME" || return $FAILURE; } + + # Destroy the gnop devices (if enabled) + for disk in ${ZFSBOOT_GNOP_4K_FORCE_ALIGN:+$realdisks}; do + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + f_quietly gnop destroy $disk$bootpart.nop + else + f_quietly gnop destroy $disk$targetpart.nop + fi + done + + # MBR boot loader hack part 2 + if [ "$ZFSBOOT_PARTITION_SCHEME" = "MBR" ]; then + # Stick the ZFS boot loader in the "convienient hole" after + # the ZFS internal metadata + for disk in $realdisks; do + dd if=/boot/zfsboot of=/dev/$disk$bootpart \ + skip=1 seek=1024 || return $FAILURE + done + fi + + # Re-import the ZFS pool(s) + zpool import -o altroot=$BSDINSTALL_CHROOT $poolname || return $FAILURE + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && + { zpool import -o altroot=$BSDINSTALL_CHROOT \ + "$ZFSBOOT_GELI_POOL_NAME" || return $FAILURE; } + + # While this is apparently not needed, it seems to help MBR + mkdir -p $BSDINSTALL_CHROOT/boot/zfs || return $FAILURE + zpool set cachefile=$BSDINSTALL_CHROOT/boot/zfs/zpool.cache \ + "$poolname" || return $FAILURE + + # Last, but not least... add required lines to rc.conf(5) + # NOTE: We later concatenate these into their destination + echo 'zfs_enable="YES"' > $BSDINSTALL_TMPETC/rc.conf.zfs || + return $FAILURE + echo 'zfs_load="YES"' > $BSDINSTALL_TMPBOOT/loader.conf.zfs || + return $FAILURE + + # We're all done unless we should go on to do encryption + [ "$ZFSBOOT_GELI_ENCRYPTION" ] || return $SUCCESS + + # + # Configure geli(8)-based encryption + # + echo 'aesni_load="YES"' \ + > $BSDINSTALL_TMPBOOT/loader.conf.aesni || return $FAILURE + echo 'geom_eli_load="YES"' \ + > $BSDINSTALL_TMPBOOT/loader.conf.geli || return $FAILURE + printf 'vfs.root.mountfrom="zfs:%s/%s/%s"\n' "$poolname" \ + "$ZFSBOOT_BEROOT_NAME" "$ZFSBOOT_BOOTFS_NAME" \ + > $BSDINSTALL_TMPBOOT/loader.conf.root || return $FAILURE + for disk in $realdisks; do + printf 'geli_%s_keyfile0_load="YES"\n' \ + "$disk$targetpart" \ + > $BSDINSTALL_TMPBOOT/loader.conf.$disk$targetpart || + return $FAILURE + printf 'geli_%s_keyfile0_type="%s:geli_keyfile0"\n' \ + "$disk$targetpart" "$disk$targetpart" \ + >> $BSDINSTALL_TMPBOOT/loader.conf.$disk$targetpart || + return $FAILURE + printf 'geli_%s_keyfile0_name="%s"\n' \ + "$disk$targetpart" "$ZFSBOOT_GELI_KEY_FILE" \ + >> $BSDINSTALL_TMPBOOT/loader.conf.$disk$targetpart || + return $FAILURE + done + + return $SUCCESS +} + +# dialog_menu_diskinfo +# +# Prompt the user to select a disk and then provide detailed info on it. +# +dialog_menu_diskinfo() +{ + local disk + + # + # Break from loop when user cancels disk selection + # + while :; do + disk=$( msg_cancel="$msg_back" f_device_menu \ + "$DIALOG_TITLE" "$msg_select_a_disk_device" "" \ + $DEVICE_TYPE_DISK 2>&1 ) || break + + # Show gpart(8) `show' and camcontrol(8) `inquiry' data + f_show_msg "$msg_detailed_disk_info" \ + "$disk" "$( gpart show $disk 2> /dev/null )" \ + "$disk" "$( camcontrol inquiry $disk 2> /dev/null )" \ + "$disk" "$( camcontrol identify $disk 2> /dev/null )" + done + + return $SUCCESS +} + +############################################################ MAIN + +# +# Initialize +# +f_dialog_title "$msg_zfs_configuration" +f_dialog_backtitle "$msg_freebsd_installer" + +# +# Loop over the main menu until we've accomplished what we came here to do +# +while :; do + dialog_menu_main + retval=$? + f_dialog_menutag_fetch mtag + f_dprintf "retval=%u mtag=[%s]" $reval "$mtag" + + [ $retval -eq $DIALOG_OK ] || f_die + + case "$mtag" in + ">>> $msg_create") + # + # First, validate the user's selections + # + + # Make sure they gave us a name for the pool + if [ ! "$ZFSBOOT_POOL_NAME" ]; then + f_show_msg "$msg_pool_name_cannot_be_empty" + continue + fi + # Make sure [potentially scripted] selections are real + real_disks= + for disk in $ZFSBOOT_DISKS; do + f_struct device_$disk && real_disks="$real_disks $disk" + done + # Make sure we have at least one real disk selected + ndisks=$( set -- $real_disks; echo $# ) + if [ $ndisks -lt 1 ]; then + f_show_msg "$msg_no_disks_selected" + continue + fi + # Make sure we have enough disks for the desired vdev type + case "$ZFSBOOT_VDEV_TYPE" in + stripe) want_disks=1 ;; + mirror) want_disks=2 ;; + raidz1) want_disks=3 ;; + raidz2) want_disks=4 ;; + raidz3) want_disks=5 ;; + *) + f_show_msg "$msg_invalid_virtual_device_type" \ + "$ZFSBOOT_VDEV_TYPE" + continue + ;; + esac + if [ $ndisks -lt $want_disks ]; then + f_show_msg "%s: $msg_not_enough_disks_selected" \ + "$ZFSBOOT_VDEV_TYPE" "$want_disks" + continue + fi + + # + # Last Chance! + # + if [ ! "$USE_XDIALOG" ]; then + DIALOG="$DIALOG --colors" f_noyes \ + "$msg_last_chance_are_you_sure_color" \ + "$ZFSBOOT_DISKS" || continue + else + f_noyes "$msg_last_chance_are_you_sure" \ + "$ZFSBOOT_DISKS" || continue + fi + + # + # Let's do this + # + + vdev_type="$ZFSBOOT_VDEV_TYPE" + + # Blank the vdev type for the default layout + [ "$vdev_type" = "stripe" ] && vdev_type= + + if ! error=$( zfs_create_boot "$ZFSBOOT_POOL_NAME" \ + "$vdev_type" $real_disks 2>&1 ) + then + f_dialog_msgbox "$error" + continue + fi + + break # to success + ;; + "- $msg_rescan_devices") f_device_rescan ;; + "- $msg_disk_info") dialog_menu_diskinfo ;; + ?" $msg_pool_name") + # Prompt the user to input/change the name for the new pool + f_dialog_input input \ + "$msg_please_enter_a_name_for_your_zpool" \ + "$ZFSBOOT_POOL_NAME" && + ZFSBOOT_POOL_NAME="$input" + ;; + ?" $msg_disks_to_use") dialog_edit_disks ;; + ?" $msg_zfs_vdev_type") dialog_menu_vdev ;; + ?" $msg_force_4k_sectors") + # Toggle the variable referenced both by the menu and later + if [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ]; then + ZFSBOOT_GNOP_4K_FORCE_ALIGN= + else + ZFSBOOT_GNOP_4K_FORCE_ALIGN=1 + fi + ;; + ?" $msg_geli_encryption") + # Toggle the variable referenced both by the menu and later + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + ZFSBOOT_GELI_ENCRYPTION= + else + ZFSBOOT_GELI_ENCRYPTION=1 + fi + ;; + ?" $msg_partition_scheme") + # Toggle between GPT and MBR + if [ "$ZFSBOOT_PARTITION_SCHEME" = GPT ]; then + ZFSBOOT_PARTITION_SCHEME=MBR + else + ZFSBOOT_PARTITION_SCHEME=GPT + fi + ;; + ?" $msg_swap_size") + # Prompt the user to input/change the swap size for each disk + f_dialog_input input \ + "$msg_please_enter_amount_of_swap_space" \ + "$ZFSBOOT_SWAP_SIZE" && + ZFSBOOT_SWAP_SIZE="$input" + ;; + esac +done + +return $SUCCESS + +################################################################################ +# END +################################################################################ Property changes on: usr.sbin/bsdinstall/scripts/zfsboot ___________________________________________________________________ Added: svn:executable ## -0,0 +1 ## +* \ No newline at end of property --------------040306070903020902050706-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 03:00:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5934748A for ; Wed, 9 Oct 2013 03:00:55 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id 1B66523E0 for ; Wed, 9 Oct 2013 03:00:54 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:15722] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 44/C1-16944-5E6C4525; Wed, 09 Oct 2013 03:00:53 +0000 Date: Wed, 09 Oct 2013 03:00:53 +0000 Message-ID: <44.C1.16944.5E6C4525@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: Unable to installworld after successful buildworld and buildkernel References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> <28.45.16944.64B74525@cdptpa-oedge02> <20131008214809.GC69269@lor.one-eyed-alien.net> X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-Mailman-Approved-At: Wed, 09 Oct 2013 04:22:37 +0000 Cc: Brooks Davis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 03:00:55 -0000 > > But where is DB_FROM_SRC documented? I never saw it anywhere. UPDATING file needs to be updated for installing FreeBSD on a partition where there is no OS installed. > It's documented in Makefile.inc1 where the less commonly used options > are documented. It should be documented in the Handbook along with the > process of cross installation and image creation. > I disagree that UPDATING should document the process of installing to > other locations. That would be a distraction from it's purpose of > letting users update their systems. It's already far too complicated. -- Brooks UPDATING file has a section on cross-installing current into a separate partition. This part ought to be complete, including DB_FROM_SRC, rather than leaving a user lost at sea when a new user (unbound) sneaks in. UPDATING documented when user auditdistd was added, so why not for unbound? Tom From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 05:52:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4357A506; Wed, 9 Oct 2013 05:52:15 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 08D3D2C68; Wed, 9 Oct 2013 05:52:14 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r995qD2S018375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Oct 2013 22:52:13 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r995qDfB018374; Tue, 8 Oct 2013 22:52:13 -0700 (PDT) (envelope-from jmg) Date: Tue, 8 Oct 2013 22:52:13 -0700 From: John-Mark Gurney To: Thomas Mueller Subject: Re: Unable to installworld after successful buildworld and buildkernel Message-ID: <20131009055213.GM56872@funkthat.com> Mail-Followup-To: Thomas Mueller , freebsd-current@freebsd.org, Brooks Davis References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> <28.45.16944.64B74525@cdptpa-oedge02> <20131008214809.GC69269@lor.one-eyed-alien.net> <44.C1.16944.5E6C4525@cdptpa-oedge02> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44.C1.16944.5E6C4525@cdptpa-oedge02> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 08 Oct 2013 22:52:13 -0700 (PDT) Cc: freebsd-current@freebsd.org, Brooks Davis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 05:52:15 -0000 Thomas Mueller wrote this message on Wed, Oct 09, 2013 at 03:00 +0000: > > > But where is DB_FROM_SRC documented? I never saw it anywhere. UPDATING file needs to be updated for installing FreeBSD on a partition where there is no OS installed. > > > It's documented in Makefile.inc1 where the less commonly used options > > are documented. It should be documented in the Handbook along with the > > process of cross installation and image creation. > > > I disagree that UPDATING should document the process of installing to > > other locations. That would be a distraction from it's purpose of > > letting users update their systems. It's already far too complicated. > > -- Brooks > > UPDATING file has a section on cross-installing current into a separate partition. > > This part ought to be complete, including DB_FROM_SRC, rather than leaving a user lost at sea when a new user (unbound) sneaks in. > > UPDATING documented when user auditdistd was added, so why not for unbound? How does this look: Index: UPDATING =================================================================== --- UPDATING (revision 256024) +++ UPDATING (working copy) @@ -1899,7 +1899,7 @@ make buildkernel KERNCONF=YOUR_KERNEL_HERE - make installworld DESTDIR=${CURRENT_ROOT} + make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd I tested distribution and it appears not to need it. P.S. I didn't think this feature even existed yet, but apparently it has since January. Thanks brooks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 07:15:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C371ED4D for ; Wed, 9 Oct 2013 07:15:23 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id 8D78C201E for ; Wed, 9 Oct 2013 07:15:22 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:25582] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id D7/23-16944-88205525; Wed, 09 Oct 2013 07:15:20 +0000 Date: Wed, 09 Oct 2013 07:15:20 +0000 Message-ID: From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: Unable to installworld after successful buildworld and buildkernel References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> <28.45.16944.64B74525@cdptpa-oedge02> <20131008214809.GC69269@lor.one-eyed-alien.net> <44.C1.16944.5E6C4525@cdptpa-oedge02> <20131009055213.GM56872@funkthat.com> X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Cc: John-Mark Gurney , Brooks Davis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 07:15:23 -0000 Quoting without "> " so as not to interfere with the patch: How does this look: Index: UPDATING =================================================================== --- UPDATING (revision 256024) +++ UPDATING (working copy) @@ -1899,7 +1899,7 @@ make buildkernel KERNCONF=YOUR_KERNEL_HERE - make installworld DESTDIR=${CURRENT_ROOT} + make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd I tested distribution and it appears not to need it. P.S. I didn't think this feature even existed yet, but apparently it has since January. Thanks brooks. -- John-Mark Gurney Voice: +1 415 225 5579 (end of quote) That looks better. Thanks, I hope this change will be committed. I don't really know if I need "make distribution ..." in my case. Attempt to boot and I'll find out. I also intend to build for i386 onto a separate partition, booting from 16 GB USB 2.0 stick with FreeBSD 9.1-stable. Then I intend to "make distribution ..." after the other steps. Tom From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 07:19:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 41753EC7 for ; Wed, 9 Oct 2013 07:19:56 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth4.wiscmail.wisc.edu (wmauth4.doit.wisc.edu [144.92.197.145]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 11A222078 for ; Wed, 9 Oct 2013 07:19:55 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth4.wiscmail.wisc.edu by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MUD00A00ZLW6300@smtpauth4.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Wed, 09 Oct 2013 01:19:48 -0500 (CDT) X-Spam-PmxInfo: Server=avs-4, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.10.9.61215, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (unknown [140.105.20.242]) by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MUE004CA1KYSD10@smtpauth4.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Wed, 09 Oct 2013 01:19:48 -0500 (CDT) Message-id: <5254F582.1040406@freebsd.org> Date: Wed, 09 Oct 2013 08:19:46 +0200 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> In-reply-to: <52549191.5010400@allanjude.com> X-Enigmail-Version: 1.5.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 07:19:56 -0000 On 10/09/13 01:13, Allan Jude wrote: > On 2013-10-08 16:17, Nathan Whitehorn wrote: >> On 10/07/13 21:59, Allan Jude wrote: >>> Devin Teske and I have been working on a big patch to bsdinstall to >>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>> sector gnop trick, and optional GELI encryption. We would like to commit >>> this in time for 10.0-BETA1 so it needs some testing to work out any >>> obvious bugs before we send it off to re@ to get it committed. >>> >>> It includes a single configuration menu that allows you to select all of >>> the required details, including which drives to use (gets details from >>> camcontrol, also includes an inspection utility that presents the >>> detailed output of camcontrol inquiry/identify, and gpart show), what >>> ZFS RAID level to use (taking in to consideration the selected number of >>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>> >>> >>> Additional, it includes some other changes to bsdinstall: >>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>> feature has been combined into the regular 'services to enable' dialog >>> and enabled by default >>> >>> >>> You can browse the patches here: >>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>> >>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>> available compressed (48 MB) or uncompressed (211 MB): >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>> >>> >>> We look forward to your feedback >>> >> Thanks for doing this! I had a few comments: >> 1. ZFS is not bootable on all architectures. Could you adjust that menu >> item to only display for i386, amd64, and (I think?) sparc64. Use uname >> -m, not -p, for this. > I had not considered that, I'll make that change > >> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >> instead of GPT. > I'll disable sparc64 as well > >> 2. Why are you using camcontrol? That is guaranteed not to work on >> non-CAM systems. You should use the GEOM ident string if you need an ID. > The GEOM ident string doesn't do enough to help the user identify which > drive is which. > More data is not exposed anywhere that I could find > > What we really need, is dev.ada.0.desc% like we have for network > interfaces and a slew of other devices. GEOM data is great, but it is > not exposed in a shell friendly way any place that I could find, other > than the sysctl with DOT and XML data. This is one of the reasons the partition editor is written in C. There are a few other odd corner-cases where C is much more powerful than the command-line for the GEOM operations that partedit needs to do. I'm not sure how to usefully get it just from the shell. You can see how to do it in C in the boot_disk() routine of partedit/auto_part.c. >> 3. Any plans to integrate this into the regular partition editor? ZFS >> support is important enough that I will definitely not get in the way, >> even as a bolt-on, but it would be a shame for it to stay that way. The >> editor is also designed for ZFS to be added. > I am a sysadmin, not a programmer. I can't write C. Most people > deploying servers can't write C. I agree with Devin Teske, if everything > was in shell it would be a lot more usable for non-developers, who > probably make up the majority of people who deploy FreeBSD. There are some cases the other way too. Devin is probably the most shell-proficient FreeBSD committer. I certainly can't write shell scripts at that level, which means that for me bsdconfig, for example, is effectively read-only (and quite hard to read as well). I suspect the same is true for many other developers. Without any prejudice about the relative merits of the languages, this can cause some significant internal maintenance issues. Something similar happened to sysinstall (which was in C): due to its complexity and high amounts of magic, it had become read-only for basically all committers and as a result fell years and years behind the rest of the project. Hopefully this is paranoia, but I can easily see complex shell scripts engendering the same problem. In any case, this particular comment was just related to the benefits of having one tool, and one UI, rather than duplicating partitioning logic in multiple places. None of this is actually complicated, so the duplication isn't that bad, but doing everything in one place long-term is almost certainly better for the user, no matter what programming language that tool is written in. -Nathan From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 07:22:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A3058DA for ; Wed, 9 Oct 2013 07:22:44 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1641620CE for ; Wed, 9 Oct 2013 07:22:43 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id eo20so320264lab.6 for ; Wed, 09 Oct 2013 00:22:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+F4fOMViLdOsPQZuoAjtVHgJKrz1y3kc5SB2Xg0SvK4=; b=klHWuO4w8o8PWgSgouevCAOwode/C8xpcdw1kcIlG/oLGYL3evIU6UOe/TyucT6it+ kNGr5ov8PinZ/ZCdyo8gPLGKCO0bwm9Ej2BwLzcaWLJQi7GFxNZxY8viRNABScaNs15W F2aRI4gXGlq3/r1afUtBPpvYxSdE2PeFqzYDyGHfd3QmbBeyTuYHkeUI9wZixOE408dZ q0QSVaAxAQEGSGuTiAAtBJhHxhqekE6UxsSQQuwaTNHcz0TxV+E95t3UMLVPqwdM9PB2 FpM/vGjt1iWpwOA4bY3hQeH8NmKGyQ7yeTZqW8qrWLVVA7yJC9glYFEs1f8+vigY/HkQ fOMA== X-Received: by 10.112.154.70 with SMTP id vm6mr5973777lbb.1.1381303362130; Wed, 09 Oct 2013 00:22:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.129.233 with HTTP; Wed, 9 Oct 2013 00:22:12 -0700 (PDT) In-Reply-To: <5254D231.5070803@allanjude.com> References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> From: Matthias Gamsjager Date: Wed, 9 Oct 2013 09:22:12 +0200 Message-ID: Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 07:22:44 -0000 Hi, tried 10-8 iso in Virtualbox but after reboot I was looking at a bootloader with a nice '-' but nothing more. post setup 'gpart list' showed no entries at all. On Wed, Oct 9, 2013 at 5:49 AM, Allan Jude wrote: > On 2013-10-07 15:59, Allan Jude wrote: > > Devin Teske and I have been working on a big patch to bsdinstall to > > implement installing on a ZFS pool. It supports both GPT and MBR, the 4k > > sector gnop trick, and optional GELI encryption. We would like to commit > > this in time for 10.0-BETA1 so it needs some testing to work out any > > obvious bugs before we send it off to re@ to get it committed. > > > > It includes a single configuration menu that allows you to select all of > > the required details, including which drives to use (gets details from > > camcontrol, also includes an inspection utility that presents the > > detailed output of camcontrol inquiry/identify, and gpart show), what > > ZFS RAID level to use (taking in to consideration the selected number of > > drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. > > > > > > Additional, it includes some other changes to bsdinstall: > > 1. Change the default to the 'non-standard keyboard mapping' prompt to no > > 2. Replace the 3 separate dialogs to configure an ipv4 address with just > 1 > > 3. Remove the dialog asking if you wish to enable crash dumps, this > > feature has been combined into the regular 'services to enable' dialog > > and enabled by default > > > > > > You can browse the patches here: > > http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ > > > > I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, > > available compressed (48 MB) or uncompressed (211 MB): > > > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz > > > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso > > > > > > We look forward to your feedback > > > > We've made more improvements, including corporating most all of the > feedback we've gotten so far > > > Outstanding items: > 1. Apply the changes to ipv6 config the way we did ipv4 > 2. improve disk identification (model info and serial # instead of one > or the other) > 3. Include a helpful message before the GELI step where you have to > enter your password many times, the user will be less confused if it is > explained why they have to enter their password 3 * number of disks times > 4. Validate vdev type choice inside the vdev type menu, and warn the > user if they have made an invalid selection, so they can add more disks > or chance their selection, without having to try to start the > installation first > 5. Whatever else you guys find wrong tonight > > I generated new test images, and attached the patch (which got REALLY > big when Devin Teske decided to fix "all of the things": > > http://www.allanjude.com/bsd/zfsbootonly.2013-10-08.iso.xz > > http://www.allanjude.com/bsd/zfsbootonly.2013-10-08.iso > > > -- > Allan Jude > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 07:43:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6382E4C0 for ; Wed, 9 Oct 2013 07:43:03 +0000 (UTC) (envelope-from hans@beastielabs.net) Received: from mail.beastielabs.net (beasties.demon.nl [82.161.3.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ED2B421FD for ; Wed, 9 Oct 2013 07:43:00 +0000 (UTC) Received: from merom.hotsoft.nl (merom.hotsoft.nl [192.168.0.12]) by mail.beastielabs.net (8.14.5/8.14.5) with ESMTP id r997K2MR047629; Wed, 9 Oct 2013 09:20:02 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <525503A2.50002@beastielabs.net> Date: Wed, 09 Oct 2013 09:20:02 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Lyndon Nerenberg , "freebsd-current@freebsd.org" Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> In-Reply-To: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 07:43:03 -0000 On 10/08/13 04:31, Lyndon Nerenberg wrote: > Okay folks, can we make a call about keeping the RCS tools in the base? > > The proponents wanting to remove RCS need to speak up and make their technical case. > Technically it is quite simple: I need RCS to start versioning config files, even before starting any customization. I know about several others who do the same (and have not yet defected to Linux). I would like to see RCS to be put back into the tree for 10.0. If it really -has- to be victimized by the current anti-GPL crusade, it could be replaced by OpenRCS in 11. And as a long time hard-core user I would appreciate if this kind of changes were performed only after at least -some- public discussion. The way this change was sneaked in (though apparently with approval of core@), reminds me more of a Secret Society than of an Open Source project. Regards, Hans From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 08:59:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6DC13595; Wed, 9 Oct 2013 08:59:19 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C1D232625; Wed, 9 Oct 2013 08:59:18 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id ev20so395615lab.25 for ; Wed, 09 Oct 2013 01:59:16 -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=n5297lJaMW9LhKHHpb9rBU3tNGzTmeYarvXI55sXx8M=; b=aEtLy8KUE7YujfTjfbG1ypuQJZKCdiws9DR5QTHDP01iPBW6tIduZ9XqQMN2lmL2sZ luQvtXNKV808UUxR+dH9yLV+Sg2ZOB4MUWR0RrZyRKATRt7SKSasLjVQ2SR9apVkBY6e +cXHQ/tFO3aVSCVPal9kjmuf9M5JjSi4WZ31rBsejep7lfoj2QF0srZLvQgBHWR16chv kBska7ROqoIGU2x3qDJT9qFDjkXBH70QBQa8cgRc+0Z5qkn4pGDC8cd3UV2JsBz2bv6G +diK74QQs+TPFVcaNBXln/kQQXddwG1OizwDKwWI2RAZkwreN4jXm/8ivoRRuxfD/T7T 2NVQ== MIME-Version: 1.0 X-Received: by 10.112.210.136 with SMTP id mu8mr6427108lbc.25.1381309156753; Wed, 09 Oct 2013 01:59:16 -0700 (PDT) Received: by 10.112.155.137 with HTTP; Wed, 9 Oct 2013 01:59:16 -0700 (PDT) In-Reply-To: <1893399957.20131009013424@serebryakov.spb.ru> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> Date: Wed, 9 Oct 2013 10:59:16 +0200 Message-ID: Subject: Re: rcs From: Daniel Nebdal To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Alfred Perlstein , Lyndon Nerenberg , Steve Kargl , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 08:59:19 -0000 On Tue, Oct 8, 2013 at 11:34 PM, Lev Serebryakov wrote: > Hello, Daniel. > You wrote 8 =D0=BE=D0=BA=D1=82=D1=8F=D0=B1=D1=80=D1=8F 2013 =D0=B3., 19:4= 0:23: > > DN> If they get the package repositories back up - which I assume will > DN> happen before any official releases from 10 - it should just be "pkg > DN> install rcs". As challenges go, that doesn't seem too bad? > Topic starter mentioned, that assumption that everybody has online > connection is completely wrong! As far as I understand, it was his main > objection -- they have a lot of offline computers at work (something > related to Security Theatre by DHS, but who am I to judge them?). > > And you again says about "pkg install rcs" which needs internet > connection! > > -- > // Black Lion AKA Lev Serebryakov > I was answering Alfred Perlsteins claim that FreeBSD is "a chore to install packages into". I agree that it won't work without an internet connection (or a local package repository), but that's hardly a problem limited to FreeBSD. Anyway, it seems likely that we'll get OpenRCS in base, hopefully making everyone happy. --=20 Daniel Nebdal From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 09:05:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9845D77E for ; Wed, 9 Oct 2013 09:05:26 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 95ABF268B for ; Wed, 9 Oct 2013 09:05:25 +0000 (UTC) Received: from vhoffman.lon.namesco.net (lon.namesco.net [195.7.254.102]) (authenticated bits=0) by unsane.co.uk (8.14.7/8.14.6) with ESMTP id r9995LXU063416 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 10:05:22 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <52551C50.4050609@unsane.co.uk> Date: Wed, 09 Oct 2013 10:05:20 +0100 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Joe Nosay Subject: Re: test References: <525408CC.7000409@gmail.com> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Alexander Panyushkin , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 09:05:26 -0000 Please use freebsd-test for testing http://lists.freebsd.org/mailman/listinfo/freebsd-test Vince On 08/10/2013 23:00, Joe Nosay wrote: > What were you testing? > > > On Tue, Oct 8, 2013 at 5:25 PM, Joe Nosay wrote: > >> /div>
test> >> >> >> On Tue, Oct 8, 2013 at 9:29 AM, Alexander Panyushkin wrote: >> >>> test >>> ______________________________**_________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/**mailman/listinfo/freebsd-**current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@** >>> freebsd.org " >>> >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 11:03:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8AC977D1 for ; Wed, 9 Oct 2013 11:03:24 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 439502D68 for ; Wed, 9 Oct 2013 11:03:24 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id r99B3Hrl078907 for ; Wed, 9 Oct 2013 07:03:22 -0400 (EDT) (envelope-from george+freebsd@m5p.com) Message-ID: <525537F5.1050100@m5p.com> Date: Wed, 09 Oct 2013 07:03:17 -0400 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> In-Reply-To: <525503A2.50002@beastielabs.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Wed, 09 Oct 2013 07:03:22 -0400 (EDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 11:03:24 -0000 On 10/09/13 03:20, Hans Ottevanger wrote: > On 10/08/13 04:31, Lyndon Nerenberg wrote: >> Okay folks, can we make a call about keeping the RCS tools in the base? >> >> The proponents wanting to remove RCS need to speak up and make their technical case. >> > > Technically it is quite simple: I need RCS to start versioning config > files, even before starting any customization. I know about several > others who do the same (and have not yet defected to Linux). > > I would like to see RCS to be put back into the tree for 10.0. If it > really -has- to be victimized by the current anti-GPL crusade, it could > be replaced by OpenRCS in 11. > > And as a long time hard-core user I would appreciate if this kind of > changes were performed only after at least -some- public discussion. > The way this change was sneaked in (though apparently with approval of > core@), reminds me more of a Secret Society than of an Open Source project. > > Regards, > > Hans > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > +1, enthusiastically. -- George From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 12:39:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6E87A102 for ; Wed, 9 Oct 2013 12:39:36 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-qe0-x22d.google.com (mail-qe0-x22d.google.com [IPv6:2607:f8b0:400d:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3100C238A for ; Wed, 9 Oct 2013 12:39:36 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id 8so504555qea.4 for ; Wed, 09 Oct 2013 05:39:35 -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=NXnalDcla0FDsGPqoPnG2YrrqesnyXJpsXOAUyzufxg=; b=QR/ap4v7qxc3/jWxe8bOAo2d0aKmX34BD9Ej3ISHC//ozyeuzQY097jDfe8WkRtGXf UDVB0uVo5drD5pFWN1rCaEKxGb4LZCa6mPAdXN770yhiZP4lW3vekytIxwdr9ERaWNKi rHqSVdeV5DipWei7EZAHNK9Ql9F3KKCxseI3d8+SZVCOQjQtbu16R1byo2VFwN93INAz iQJHtpbC7rpkU+7mETK0Pw5R8V3SHWkzmruZXj8A3Z8rmU1Kd3x5XChl6F9xLQyKOckH Z5KEc1wdgYXq86HHD3kv5cquH2eixh8fiiBPmPDOgPdbkiV1HwECR24Xcb6jHLfTVveT im6Q== MIME-Version: 1.0 X-Received: by 10.224.32.66 with SMTP id b2mr2769561qad.80.1381322375099; Wed, 09 Oct 2013 05:39:35 -0700 (PDT) Received: by 10.224.204.74 with HTTP; Wed, 9 Oct 2013 05:39:35 -0700 (PDT) In-Reply-To: <525537F5.1050100@m5p.com> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> Date: Wed, 9 Oct 2013 15:39:35 +0300 Message-ID: Subject: Re: rcs From: Kimmo Paasiala To: George Mitchell Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 12:39:36 -0000 On Wed, Oct 9, 2013 at 2:03 PM, George Mitchell wrote: > On 10/09/13 03:20, Hans Ottevanger wrote: >> >> On 10/08/13 04:31, Lyndon Nerenberg wrote: >>> >>> Okay folks, can we make a call about keeping the RCS tools in the base? >>> >>> The proponents wanting to remove RCS need to speak up and make their >>> technical case. >>> >> >> Technically it is quite simple: I need RCS to start versioning config >> files, even before starting any customization. I know about several >> others who do the same (and have not yet defected to Linux). >> >> I would like to see RCS to be put back into the tree for 10.0. If it >> really -has- to be victimized by the current anti-GPL crusade, it could >> be replaced by OpenRCS in 11. >> >> And as a long time hard-core user I would appreciate if this kind of >> changes were performed only after at least -some- public discussion. >> The way this change was sneaked in (though apparently with approval of >> core@), reminds me more of a Secret Society than of an Open Source >> project. >> >> Regards, >> >> Hans >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > > +1, enthusiastically. -- George > +1 also to OpenRCS allthough I hate anything related to RCS/CVS with a passion. I do however recognize the need for a simple revision control system in the base, svnlite would fill the need maybe but it's good to have other options too. -Kimmo From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 13:06:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E77F78EB for ; Wed, 9 Oct 2013 13:06:35 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 27F962532 for ; Wed, 9 Oct 2013 13:06:33 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.7/8.14.7) with ESMTP id r99D6Unt079830; Wed, 9 Oct 2013 08:06:30 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.7/8.14.7/Submit) id r99D6UqE079829; Wed, 9 Oct 2013 08:06:30 -0500 (CDT) (envelope-from brooks) Date: Wed, 9 Oct 2013 08:06:30 -0500 From: Brooks Davis To: Thomas Mueller , freebsd-current@freebsd.org Subject: Re: Unable to installworld after successful buildworld and buildkernel Message-ID: <20131009130630.GB71891@lor.one-eyed-alien.net> References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> <28.45.16944.64B74525@cdptpa-oedge02> <20131008214809.GC69269@lor.one-eyed-alien.net> <44.C1.16944.5E6C4525@cdptpa-oedge02> <20131009055213.GM56872@funkthat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: <20131009055213.GM56872@funkthat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 13:06:36 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 08, 2013 at 10:52:13PM -0700, John-Mark Gurney wrote: > Thomas Mueller wrote this message on Wed, Oct 09, 2013 at 03:00 +0000: > > > > But where is DB_FROM_SRC documented? I never saw it anywhere. UPD= ATING file needs to be updated for installing FreeBSD on a partition where = there is no OS installed. > >=20 > > > It's documented in Makefile.inc1 where the less commonly used options > > > are documented. It should be documented in the Handbook along with t= he > > > process of cross installation and image creation. > >=20 > > > I disagree that UPDATING should document the process of installing to > > > other locations. That would be a distraction from it's purpose of > > > letting users update their systems. It's already far too complicated. > >=20 > > -- Brooks > >=20 > > UPDATING file has a section on cross-installing current into a separate= partition. > >=20 > > This part ought to be complete, including DB_FROM_SRC, rather than leav= ing a user lost at sea when a new user (unbound) sneaks in. > >=20 > > UPDATING documented when user auditdistd was added, so why not for unbo= und? >=20 > How does this look: > Index: UPDATING > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- UPDATING (revision 256024) > +++ UPDATING (working copy) > @@ -1899,7 +1899,7 @@ > make buildkernel KERNCONF=3DYOUR_KERNEL_HERE > > > - make installworld DESTDIR=3D${CURRENT_ROOT} > + make installworld DESTDIR=3D${CURRENT_ROOT} -DDB_FROM_SRC > make distribution DESTDIR=3D${CURRENT_ROOT} # if newfs'd > make installkernel KERNCONF=3DYOUR_KERNEL_HERE DESTDIR=3D${CURREN= T_ROOT} > cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if n= ewfs'd >=20 >=20 > I tested distribution and it appears not to need it. Distribution could easily need it in the future so I'd suggest adding in there as well. If nothing else, if building on a box with a highly non-standard /etc/passwd or /etc/group the results could be bizzare and inconsistant if -DDB_FROM_SRC is not used in both cases. installkernel is probably safe since people who renumber root/wheel will get what they deserve if they don't audit all of the make infrastructure. -- Brooks P.S. This probably shouldn't be documented because it is dangerous in some situations: but for administrators who keep their passwd and group files entirely in sync with FreeBSD's you can skip the whole mergemaster -p annoyance by specifying DESTDIR=3D/ -DDB_FROM_SRC. --jRHKVT23PllUwdXP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFSVVTVXY6L6fI4GtQRAnYEAKC10EJEHdA8tg52t27mzzZELsMK+QCbBu8H phcxRxcAuYm6Y3G+cPo+u78= =xalx -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 13:23:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CB06DE3B for ; Wed, 9 Oct 2013 13:23:07 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 886422631 for ; Wed, 9 Oct 2013 13:23:07 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1VTtj8-000MI9-BM ; Wed, 09 Oct 2013 16:22:58 +0300 Date: Wed, 9 Oct 2013 16:22:58 +0300 From: Vitalij Satanivskij To: freebsd-current@freebsd.org Subject: Assertion in zdb? Message-ID: <20131009132258.GA85485@hell.ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: satan@ukr.net X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 13:23:07 -0000 Hello. System - 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r255173 While trying to get some statistics from zdb zdb -dd disk1 > stat.log get some assertion: Assertion failed: object_count == usedobjs (0x85727 == 0x3aa93d), file /usr/src/cddl/usr.sbin/zdb/../../../cddl/contrib/opensolaris/cmd/zdb/zdb.c, line 1767. zsh: abort (core dumped) zdb -dd disk1 > stat.log Maybe somebody have any idea about what's it's can be and how big problem it's (or not a problem at all)? From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 13:31:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 31B943EA for ; Wed, 9 Oct 2013 13:31:33 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EDBD326C9 for ; Wed, 9 Oct 2013 13:31:32 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r99DVHMN041654 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 06:31:25 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52555A9F.7000609@freebsd.org> Date: Wed, 09 Oct 2013 21:31:11 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Alfred Perlstein Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> In-Reply-To: <525422B6.9040906@mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 13:31:33 -0000 On 10/8/13 11:20 PM, Alfred Perlstein wrote: > On 10/8/13 8:04 AM, sthaug@nethelp.no wrote: >>>> I think the fact is that most direct users of RCS use it in a very >>>> simple way, and >>>> it works just fine for that. with no real need for any updates >>>> or any >>>> change. >>> With all due respect Julian, The more we discuss this more this >>> really >>> points to the problem that FreeBSD appears to be a challenge to >>> install >>> packages into such that a package moving out of base is such a big >>> deal. >>> >>> Can we fix that instead? >>> >>> I mean, this change should really not be a big deal, but yet it is >>> and >>> this speaks to the core of FreeBSD utility. >> Not commenting on RCS here, but on the concept of moving packages out >> of the base: >> >> - For some of us, the attraction of FreeBSD is that it is a tightly >> integrated system, and the base contains enough useful functionality >> that we don't *have* to add a lot of packages. >> >> - Each package that is moved out of the base system means less useful >> functionality in the base system - and for me: Less reason to use >> FreeBSD instead of Linux. >> >> I absolutely see the problem of maintaining out-of-date packages in >> the base system, and the desirability of making the base system less >> reliant on GPL. I'm mostly troubled by the fact that there seems to >> be a rather strong tendency the last few years of having steadily >> less functionality in the base system - and I'm not at all convinced >> that the right balance has been found here. >> >> This discussion is not new, and I don't expect to convince any new >> persons... >> >> > I'm sure other devs will disagree, but with ~15 years of FreeBSD > experience and ~13 years as a dev, my very strong opinion is that > this tightly coupled system is actually a boat anchor sinking us. you are right.. I disagree :-) > > Just because no one else does it a certain way, does not mean that a > unique way of doing something is correct and/or sustainable. Maybe > in 1995, 1999, or 2005 even, but not today. Especially in the > context of add-on tools like rcs. > > What we need to discuss is lowering the bar to making custom installs. > > I personally find that installing FreeBSD is useless until I install > "screen, zsh, vim-lite, git" why is that so manual for me? Why > can't I just register a package set somewhere so that all I have to > type in is "alfred.perlstein.devel" into a box during the installer > and I get all my packages by default? I agree in part.. we should have several levels of packages.. where the highest level is pretty much indistinguishable from what we have now as base utilities.. we maintian the package, but we also maintain the source the package pulls from. it has hte same guarantee of being in sync as currently we have for base utils. under that we have 'highly used and trusted apps' (X11, bind, apache, python etc), and after that there are "the others". but until then I consider rcs a bit like awk.. something I just expect to be there. and use like that... From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 13:34:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2561953B; Wed, 9 Oct 2013 13:34:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CE94E26FF; Wed, 9 Oct 2013 13:34:14 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r99DY7Y5041679 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 06:34:10 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52555B49.1070207@freebsd.org> Date: Wed, 09 Oct 2013 21:34:01 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Graham Todd Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , Alfred Perlstein , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 13:34:15 -0000 On 10/9/13 4:38 AM, Graham Todd wrote: > > On Tue, 8 Oct 2013, Adrian Chadd wrote: > >> I think that's great. But, as we are increasingly finding, theres >> no stable >> ports snapshot, so unless we as a project change how packages are >> managed, >> there may not really be a stable, predictable version of things once >> they're moved from base to a package. A number of users and >> companies like >> that there is a very strict definition of base and that it wont >> change as >> the ports tree changes. >> >> Eg, you install 10.0 and get the rcs package from that. You then do an >> install of 10.0 a yeat later and install rcs. If it comes from the >> 10-stable pkgng set, itll pick up the latest version, not the 10.0 >> version. >> Thats the big ports vs base difference. > > Perhaps a perl style "dual life module" set of "core" (errm BASE?) > packages/ports will emerge. It could resolve some of the perennial > "what is BASE"? debates - or at least make it possible to have those > debates in a different way :-) > > My understanding is that dealing with the GPLv3 issue for BASE is > *necessary* for the project. Since the latest rcs releases are > licensed using GPLv3, FreeBSD's BASE rcs (GPLv2) would have to be > maintained exclusively by the FreeBSD project - which means more > developer overhead (the same could be said for gcc I suppose). That > seems to be a different type of issue than the size/completeness of > BASE itself. but RCS is not GPLv3 and what we have works fine... just leave it alone! > > Since rcs is a small utility, it's hooked into a script or two via > rc.subr, it's useful to a lot of folks, it doesn't face the network > and there's a BSD licensed equivalent sort of available, then maybe > the best way to go would be to import opencvs's rcs (which is not > part in the ports version of opencvs) to replace the GNU version. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 13:41:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0F8447A6 for ; Wed, 9 Oct 2013 13:41:59 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BB81B2773 for ; Wed, 9 Oct 2013 13:41:58 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r99Dfsxe041697 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 06:41:56 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52555D1C.8010407@freebsd.org> Date: Wed, 09 Oct 2013 21:41:48 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Freddie Cash Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Alfred Perlstein , FreeBSD-Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 13:41:59 -0000 On 10/9/13 2:35 AM, Freddie Cash wrote: > On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein wrote: > >> You're right on the money, to be honest this is one of the reasons why >> I've switched to using OSX as my desktop OS. >> >> zsh, vim, screen by default. and upgrades work. At the end of the day >> I'm spending time doing work, not mucking about my workspace to make it >> usable for development. >> >> I think this was brought up at BSDCan in the discussion about making >> FreeBSD a more featured development platform. >> >> Speaking of... has anyone tried PCBSD? > > PC-BSD isn't much different from FreeBSD. The installer is GUI and support > ZFS, there are some GUI setup tools on first boot for X, there are some GUI > tools to select binary drivers for X, and there ​​are working pkgng repos > available. > > I had a lot of issues with PC-BSD 9.0 and 9.1 as I was trying to do things > "the FreeBSD way" which broke a lot of things that were done "the PC-BSD > way" (aka don't manually edit config files used for booting). > > ​Switching to the "rolling-release" (aka PC-BSD 9-STABLE) and moving all my > config file edits into .conf.local fixed my issues. Things have > been running smooth, and I finally understand the beauty and simplicity of > freebsd-update + pkg. OS gets updated once per month, packages get updated > twice per month, no more compiling things from source. It's like using > Ubuntu/Debian but with the power and features of FreeBSD. :) > ​ When they went to a ZFS-only system, using GRUB, with no alternative, then I'm afraid they lost me. I want a root filesystem on UFS for reliabailty and simpleness. I can debug it's media if needed. Before then I really liked it (though ther eis not enough information on how it works interneally if you want to use it. hopefully that will come.. and I LIKE PBIs FreeBSD should adopt PBIs for sure. With PBIs you could make even quite base items separately installable. versioning problems go away. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 13:43:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4DEC98D8; Wed, 9 Oct 2013 13:43:55 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1BE74278F; Wed, 9 Oct 2013 13:43:54 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r99DhnkA041708 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 06:43:52 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52555D8F.1090908@freebsd.org> Date: Wed, 09 Oct 2013 21:43:43 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Daniel Nebdal Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Lyndon Nerenberg , lev@freebsd.org, Alfred Perlstein , Steve Kargl , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 13:43:55 -0000 On 10/9/13 4:59 PM, Daniel Nebdal wrote: > On Tue, Oct 8, 2013 at 11:34 PM, Lev Serebryakov wrote: >> Hello, Daniel. >> You wrote 8 октября 2013 Đł., 19:40:23: >> >> DN> If they get the package repositories back up - which I assume will >> DN> happen before any official releases from 10 - it should just be "pkg >> DN> install rcs". As challenges go, that doesn't seem too bad? >> Topic starter mentioned, that assumption that everybody has online >> connection is completely wrong! As far as I understand, it was his main >> objection -- they have a lot of offline computers at work (something >> related to Security Theatre by DHS, but who am I to judge them?). >> >> And you again says about "pkg install rcs" which needs internet >> connection! >> >> -- >> // Black Lion AKA Lev Serebryakov >> > > I was answering Alfred Perlsteins claim that FreeBSD is "a chore to > install packages into". I agree that it won't work without an internet > connection (or a local package repository), but that's hardly a > problem limited to FreeBSD. > > Anyway, it seems likely that we'll get OpenRCS in base, hopefully > making everyone happy. > if it doesn't make it then we need RCS back.... and it should be back now waiting for OpenRCS... until then there is a hole.. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 13:48:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5925CD3E for ; Wed, 9 Oct 2013 13:48:09 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A9F427D8 for ; Wed, 9 Oct 2013 13:48:08 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r99DltqL041739 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 06:47:58 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52555E86.7010504@freebsd.org> Date: Wed, 09 Oct 2013 21:47:50 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Hans Ottevanger Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> In-Reply-To: <525503A2.50002@beastielabs.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 13:48:09 -0000 On 10/9/13 3:20 PM, Hans Ottevanger wrote: > On 10/08/13 04:31, Lyndon Nerenberg wrote: >> Okay folks, can we make a call about keeping the RCS tools in the base? >> >> The proponents wanting to remove RCS need to speak up and make their technical case. >> > Technically it is quite simple: I need RCS to start versioning config > files, even before starting any customization. I know about several > others who do the same (and have not yet defected to Linux). > > I would like to see RCS to be put back into the tree for 10.0. If it > really -has- to be victimized by the current anti-GPL crusade, it could > be replaced by OpenRCS in 11. > > And as a long time hard-core user I would appreciate if this kind of > changes were performed only after at least -some- public discussion. > The way this change was sneaked in (though apparently with approval of > core@), reminds me more of a Secret Society than of an Open Source project. no, with private approval of a CORE MEMBER.. that is quite a different thing.. Core, AFAIK has not ruled on this sort of topic.. (and actually it's not really it's job to do so unless it's resolving a dispute.) > > Regards, > > Hans > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 14:00:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4C5A6406 for ; Wed, 9 Oct 2013 14:00:22 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1F8FA289C for ; Wed, 9 Oct 2013 14:00:21 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r99E0Cal041797 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 07:00:15 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <52556167.4030206@freebsd.org> Date: Wed, 09 Oct 2013 22:00:07 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Diane Bruce Subject: Re: [Heads Up] RCS removed from base References: <201310082033.r98KXUgJ058127@slippy.cwsent.com> <5254718E.2000504@pix.net> <20131008232251.GA47296@night.db.net> In-Reply-To: <20131008232251.GA47296@night.db.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Kurt Lidl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 14:00:22 -0000 On 10/9/13 7:22 AM, Diane Bruce wrote: > On Tue, Oct 08, 2013 at 04:56:46PM -0400, Kurt Lidl wrote: >> On 10/8/13 4:33 PM, Cy Schubert wrote: >>> In message <52542687.7000100@pix.net>, Kurt Lidl writes: >>>> On 10/8/13, Julian Elischer wrote: >>>>> On 10/7/13 11:06 PM, Steve Kargl wrote: >>>>>> On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: >>>>>>> Hey all, > Did it this morning > > http://people.FreeBSD.org/~db/rcs.tgz > > Or > > http://www.db.net/~db/rcs.tgz > > > It's up to core@ to decide what to do. > > > - Diane I think everyone knows my opinion.. I think we need an in-base *file* versioning tool .. and since many of us have RCS'd our /etc files, or have install scripts that use RCS it should be RCS.. I don't care WHICH RCS it is but it needs to be back in place by 10. and the easiest way of having it there in the mean while is jsut to revert the commit until the new one is ready. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 14:17:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 33A16C06 for ; Wed, 9 Oct 2013 14:17:08 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 1F4FA2A70 for ; Wed, 9 Oct 2013 14:17:07 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 41C2C1A3DE6 for ; Wed, 9 Oct 2013 07:17:07 -0700 (PDT) Message-ID: <52556567.3090309@mu.org> Date: Wed, 09 Oct 2013 07:17:11 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 14:17:08 -0000 On 10/9/13 1:59 AM, Daniel Nebdal wrote: > On Tue, Oct 8, 2013 at 11:34 PM, Lev Serebryakov wrote: >> Hello, Daniel. >> You wrote 8 октября 2013 Đł., 19:40:23: >> >> DN> If they get the package repositories back up - which I assume will >> DN> happen before any official releases from 10 - it should just be "pkg >> DN> install rcs". As challenges go, that doesn't seem too bad? >> Topic starter mentioned, that assumption that everybody has online >> connection is completely wrong! As far as I understand, it was his main >> objection -- they have a lot of offline computers at work (something >> related to Security Theatre by DHS, but who am I to judge them?). >> >> And you again says about "pkg install rcs" which needs internet >> connection! >> >> -- >> // Black Lion AKA Lev Serebryakov >> > > I was answering Alfred Perlsteins claim that FreeBSD is "a chore to > install packages into". I agree that it won't work without an internet > connection (or a local package repository), but that's hardly a > problem limited to FreeBSD. > > Anyway, it seems likely that we'll get OpenRCS in base, hopefully > making everyone happy. > Only a few years ago you could take a dvd or memstick of FreeBSD and have 1000s of packages to choose from during your install. That is broken now? Bummer. -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 14:20:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8CFAAE6F; Wed, 9 Oct 2013 14:20:38 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6122C2AA5; Wed, 9 Oct 2013 14:20:38 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 1402497B3; Wed, 9 Oct 2013 14:20:35 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 1402497B3 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Wed, 9 Oct 2013 10:20:34 -0400 From: Glen Barber To: Alfred Perlstein Subject: Re: rcs Message-ID: <20131009142034.GF630@glenbarber.us> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> <52556567.3090309@mu.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Zi0sgQQBxRFxMTsj" Content-Disposition: inline In-Reply-To: <52556567.3090309@mu.org> X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 14:20:38 -0000 --Zi0sgQQBxRFxMTsj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 09, 2013 at 07:17:11AM -0700, Alfred Perlstein wrote: > Only a few years ago you could take a dvd or memstick of FreeBSD and > have 1000s of packages to choose from during your install. That is > broken now? >=20 memstick.img always had a minimal set of packages (mostly documentation sets). dvd1.iso has packages. Glen --Zi0sgQQBxRFxMTsj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSVWYyAAoJELls3eqvi17QK08QAJX7v92ZfDHXM8yu/oCc2u+x BpVr2oa2/1YIvdxayhowOWw3BQ1zqEVvLy58mTf9Ho1ZcQVJlugaBAytML5Lhv6f C8oPp2hoG3MLEPhiCWt21PDm8AcE42+THgPEP/BvPpflTkSsfcmjskp5LJWdv67y AXqY/IhWQ6pBTaewnz7Q9kpTvocR5F+BhR7tz9+kQ9/Ie3scEDpx8/GwvdDxJPMH wFlu0Z78LyDl1dCTn3bXPcFcsph22s8ZV67+HLwvZ2bdzRSIkH65Jz3ieBzJLM6P TaNeyv5I9D+tRp4dP1ZUeLq0yAO1D8xgZXQT/JcpULGExeYDu/yM5nnEatqACYMx Y7EFXdj2P2LNISYmafShgFTW6ZSRxI4hPM8tg65cXoUKQnbUbctjXob9GvBC6hn7 YNGAgt2bHjghtsufoEu6ZKaASWaPoLOn8N+tsKgm90255u9gko6w6eoWOTaK2AHH 4B0B3X4SV2kT1jv2Suoz/OMhImEpBrvF61Y6Eq56F5mQjILLNxQTfyyCxRZcrt9h x/dtYCUHhmLw2DVIoUZnjrVgRSt+Xm1UwqjtGZVhq9yuliCYfTeTbdSjHf2qxmg0 o79L4DoKEFSsleYarj8UF/e3xfkjWvbkk4R2GMx1aeJTw15JAjvzLjQDwwKP9AHH U0g7drcxlbmQ7MFrYcFA =1FMe -----END PGP SIGNATURE----- --Zi0sgQQBxRFxMTsj-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 14:33:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4250839D for ; Wed, 9 Oct 2013 14:33:42 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) by mx1.freebsd.org (Postfix) with ESMTP id D89092B91 for ; Wed, 9 Oct 2013 14:33:41 +0000 (UTC) X-AuditID: 1209190f-b7fa08e0000009c6-c5-525569454756 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id F7.D0.02502.54965525; Wed, 9 Oct 2013 10:33:41 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r99EXe1R009599; Wed, 9 Oct 2013 10:33:40 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r99EXc8N030349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 9 Oct 2013 10:33:39 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r99EXcB5020639; Wed, 9 Oct 2013 10:33:38 -0400 (EDT) Date: Wed, 9 Oct 2013 10:33:38 -0400 (EDT) From: Benjamin Kaduk To: Lyndon Nerenberg Subject: Re: rcs In-Reply-To: <316CC412-A884-4E23-95D5-8565872FC844@orthanc.ca> Message-ID: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <316CC412-A884-4E23-95D5-8565872FC844@orthanc.ca> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJIsWRmVeSWpSXmKPExsUixCmqreuaGRpkMHEev8WcNx+YLLbMPsLi wOQx49N8Fo+7rz4zBTBFcdmkpOZklqUW6dslcGU0PVcveM1e8XH2J+YGxslsXYwcHBICJhL7 GkW6GDmBTDGJC/fWA4W5OIQE9jFK/Gu7zwySEBLYwCjx+isXROIgk8ShuecYQZqFBOoltk/k BalhEdCSWNuwH6yeTUBFYuabjWwgtoiAhsT06/+YQGxmAXmJ/1cuM4G0CgsISOz8UgUS5hSw k5h4+QcjiM0r4CgxcV07M8Sq60wS6xYuYgdJiAroSKzeP4UFokhQ4uTMJywQMy0lzv25zjaB UXAWktQsJKkFjEyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdE30cjNL9FJTSjcxgkNUkn8H47eD SocYBTgYlXh4O3hDgoRYE8uKK3MPMUpyMCmJ8m6PCQ0S4kvKT6nMSCzOiC8qzUktPsQowcGs JMKblAKU401JrKxKLcqHSUlzsCiJ897ksA8SEkhPLEnNTk0tSC2CycpwcChJ8LJkADUKFqWm p1akZeaUIKSZODhBhvMADf+YDjK8uCAxtzgzHSJ/ilFRSpz3KEhCACSRUZoH1wtLIa8YxYFe Eeb9C1LFA0w/cN2vgAYzAQ3e/j0EZHBJIkJKqoGx+5fMlQb71VrTpl5Zc2W6lGwAN9+phfnX /l8WaWvrWnqyf5IKh6GGyEXz3qRqAfaVZdqaYp5pKguuBhzeEcod8W3t1GUr514+f+nyqvj1 DpIuAep7pnF/sH5+fd9ipkf/Yyf+z1kjF13Kxm57rqu0bdn2rgdWW9fxuTwuv5b+tX/FNL/0 Z8IMSizFGYmGWsxFxYkAi3m2//wCAAA= Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 14:33:42 -0000 Going off on a slight tangent... On Tue, 8 Oct 2013, Lyndon Nerenberg wrote: > > For this to work in a disconnected environment, you need a ports tree > with a fully populated distfiles/ directory. The hack we came up with > was to put a FreeBSD host on the external network, on which we ran a > script once a week or so that would do the something like 'portsnap > fetch update; portsclean -DD; for in in /usr/ports/*/*; (cd $i && make > fetch); done'. I just reviewed a documentation patch which was noting that 'make fetch' can be done in a category directory or even in /usr/ports itself. Maybe a little more reliable than the shell loop. -Ben Kaduk > That would give us a (mostly) populated /usr/ports/distfiles. We would > then rsync /usr/ports from the public machine onto a USB drive. That > drive would then be disconnected from the public machine and attached to > an internal file server, and its /usr/ports rsynced to the file server's > /usr/ports. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 14:58:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 97E8A9DD; Wed, 9 Oct 2013 14:58:45 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 819BB2D1D; Wed, 9 Oct 2013 14:58:44 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 0CDC71A3C2F; Wed, 9 Oct 2013 07:58:44 -0700 (PDT) Message-ID: <52556F28.7080207@mu.org> Date: Wed, 09 Oct 2013 07:58:48 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Glen Barber Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> <52556567.3090309@mu.org> <20131009142034.GF630@glenbarber.us> In-Reply-To: <20131009142034.GF630@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 14:58:45 -0000 On 10/9/13 7:20 AM, Glen Barber wrote: > On Wed, Oct 09, 2013 at 07:17:11AM -0700, Alfred Perlstein wrote: >> Only a few years ago you could take a dvd or memstick of FreeBSD and >> have 1000s of packages to choose from during your install. That is >> broken now? >> > memstick.img always had a minimal set of packages (mostly documentation > sets). > > dvd1.iso has packages. > > Glen > Thanks Glen! I'm just confused as to why this is such a big deal if the packages are available. Do we need a "package memstick" now that memsticks are typically 4 or even 8GB? -- Alfred Perlstein From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 15:04:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EA1ABBB6 for ; Wed, 9 Oct 2013 15:04:02 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::3c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BF72C2D83 for ; Wed, 9 Oct 2013 15:04:02 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.5/8.14.5) with ESMTP id r99F4109025656 for ; Wed, 9 Oct 2013 11:04:01 -0400 (EDT) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at mail.pix.net Message-ID: <52557060.3040304@pix.net> Date: Wed, 09 Oct 2013 11:04:00 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [Heads Up] RCS removed from base References: <20131008232251.GA47296@night.db.net> In-Reply-To: <20131008232251.GA47296@night.db.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 15:04:03 -0000 > On Tue, Oct 08, 2013 at 04:56:46PM -0400, Kurt Lidl wrote: >> On 10/8/13 4:33 PM, Cy Schubert wrote: >> > In message <52542687.7000100 at pix.net>, Kurt Lidl writes: >> >> On 10/8/13, Julian Elischer wrote: >> >>> On 10/7/13 11:06 PM, Steve Kargl wrote: >> >>>> On Sun, Oct 06, 2013 at 10:43:21PM -0400, Eitan Adler wrote: >> >>>>> Hey all, > > Did it this morning > > http://people.FreeBSD.org/~db/rcs.tgz > > Or > > http://www.db.net/~db/rcs.tgz I notice in diff'ing your work vs my work, that I started with newer revisions of some of the files than the ones you have: < .\" $OpenBSD: ci.1,v 1.37 2011/07/14 16:31:34 sobrado Exp $ --- > .\" $OpenBSD: ci.1,v 1.38 2013/08/12 14:19:53 jmc Exp $ < /* $OpenBSD: ci.c,v 1.214 2013/01/18 11:21:09 guenther Exp $ */ --- > /* $OpenBSD: ci.c,v 1.215 2013/04/17 00:20:52 deraadt Exp $ */ < /* $OpenBSD: co.c,v 1.116 2010/12/03 19:44:58 chl Exp $ */ --- > /* $OpenBSD: co.c,v 1.117 2013/04/16 20:24:45 deraadt Exp $ */ < /* $OpenBSD: date.y,v 1.10 2010/07/31 08:54:42 ray Exp $ */ --- > /* $OpenBSD: date.y,v 1.11 2013/04/19 17:28:07 deraadt Exp $ */ < /* $OpenBSD: diff.c,v 1.33 2011/04/20 19:34:16 nicm Exp $ */ --- > /* $OpenBSD: diff.c,v 1.34 2013/05/16 12:44:48 stsp Exp $ */ < .\" $OpenBSD: ident.1,v 1.11 2011/04/19 21:17:30 jmc Exp $ --- > .\" $OpenBSD: ident.1,v 1.12 2013/06/29 09:08:41 jmc Exp $ < /* $OpenBSD: rcs.h,v 1.15 2011/07/06 15:36:52 nicm Exp $ */ --- > /* $OpenBSD: rcs.h,v 1.16 2013/06/03 17:04:35 jcs Exp $ */ < /* $OpenBSD: rcsparse.c,v 1.8 2012/02/04 21:22:32 tobias Exp $ */ --- > /* $OpenBSD: rcsparse.c,v 1.9 2013/06/03 17:04:35 jcs Exp $ */ < /* $OpenBSD: rcsutil.c,v 1.38 2010/12/06 22:52:55 chl Exp $ */ --- > /* $OpenBSD: rcsutil.c,v 1.39 2013/04/16 20:24:45 deraadt Exp $ */ < /* $OpenBSD: rlog.c,v 1.65 2011/07/14 16:38:39 sobrado Exp $ */ --- > /* $OpenBSD: rlog.c,v 1.66 2013/06/03 17:04:35 jcs Exp $ */ -Kurt From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 15:10:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 00A9DD2D; Wed, 9 Oct 2013 15:10:15 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A65202DC1; Wed, 9 Oct 2013 15:10:15 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r99FACs7037163; Wed, 9 Oct 2013 09:10:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r99FACBZ037160; Wed, 9 Oct 2013 09:10:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 9 Oct 2013 09:10:12 -0600 (MDT) From: Warren Block To: Freddie Cash Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI In-Reply-To: Message-ID: References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) 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]); Wed, 09 Oct 2013 09:10:12 -0600 (MDT) Cc: FreeBSD-Current , Nathan Whitehorn X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 15:10:16 -0000 On Tue, 8 Oct 2013, Freddie Cash wrote: > On Tue, Oct 8, 2013 at 1:17 PM, Nathan Whitehorn wrote: > >> 4. What is this gnop stuff for? >> > > Can't comment on the rest, but gnop is required to create 4K-aligned vdevs > where the minimum block size is 4K (aka ashift=12). Right, but to emphasize: the gnop hack forces ZFS to 4K blocks. It does not, by itself, guarantee alignment with 4K native blocks on the drive, that has to be done by making the partitions aligned. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 15:29:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B446D348; Wed, 9 Oct 2013 15:29:03 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 67DD62EE7; Wed, 9 Oct 2013 15:29:03 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r99FT05B037265; Wed, 9 Oct 2013 09:29:00 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r99FT0Ti037262; Wed, 9 Oct 2013 09:29:00 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 9 Oct 2013 09:29:00 -0600 (MDT) From: Warren Block To: "Teske, Devin" Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC46904@LTCFISWMSGMB21.FNFIS.com> Message-ID: References: <52546844.2010608@freebsd.org> <5254774C.8030204@pix.net> <525478EA.8080207@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC46904@LTCFISWMSGMB21.FNFIS.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) 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]); Wed, 09 Oct 2013 09:29:00 -0600 (MDT) Cc: "" , Nathan Whitehorn X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 15:29:03 -0000 On Tue, 8 Oct 2013, Teske, Devin wrote: > "But shell is nasty; slow; and not as powerful as C" (it depends in what > context; the first is rhetoric, the second is only true for poor implement- > ations, and the third may be true in some contexts, but I consider the > answer to "how maintainable is it" to be a factor in the "power" of a > language, so don't necessarily consider C to be more powerful than > shell as the latter is as-or-more maintainable with fewer LoC and a > higher return on investment; see previous [above] arguments). My question would be: why are sh and C the only choices? If the answer is "because that's all we have in base", is that a valid concern? As far as sh, it lacks many high- or even mid-level constructs and has real problems with quoting, parsing, and output (2>&1 >&3, for example). These make it harder to do things (aka, more code to accomplish a task, more code to be maintained, more difficult to modify) than the higher level Perubython languages. In any case, thanks for working on this. A functioning program in any language is better than a non-existent "better" one. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 15:59:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C6BA1CC0 for ; Wed, 9 Oct 2013 15:59:44 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9DD8A2105 for ; Wed, 9 Oct 2013 15:59:44 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id g10so1143873pdj.12 for ; Wed, 09 Oct 2013 08:59:44 -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=ZYc5czi/frAkEleKEUKJbGjpSu0isYJ9r1BWEX/uipc=; b=fjTfBGzunGarA/7CGMSaKuVKvE9MfCTg2qJaOcnpefKOTavMuUsmjSH2+6/V9Lko8F b344sAP6RoDB7kep4VlMWtfkJJ49jam7Y/n1eA8CRexafOhCM79mxRFM3rUwx3VInoGU vOXz24WgBv8/V9BHcS5IQauqJTbJ1fZKMZ8hvFYvWSx37F190yyanCGC0+lJSgFwUKH6 m3sZLZ2hlzPDIuAZ4k0wW3yYjFGFs1wsjO5NHS8vzMaU7kg6x3BlpItf9f05Mloksy+z 9ty+4cG/w8P2rA5trFJTxCieh9DKzljMNgZj3ooWj5gF1qboR09i0oKDIcxUHMGtGtM1 ixlA== X-Gm-Message-State: ALoCoQl09Dr0/CMjeXQdlAzCABe+UYjxqtma/e2ZnsAHIgLyF4CyFwkUuCoHIsNxxaBFFyesFoYK MIME-Version: 1.0 X-Received: by 10.68.182.3 with SMTP id ea3mr8813363pbc.124.1381334383460; Wed, 09 Oct 2013 08:59:43 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Wed, 9 Oct 2013 08:59:43 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Wed, 9 Oct 2013 08:59:43 -0700 (PDT) In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> Date: Wed, 9 Oct 2013 08:59:43 -0700 Message-ID: Subject: Re: rcs From: Jos Backus To: Kimmo Paasiala Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: George Mitchell , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 15:59:44 -0000 On Oct 9, 2013 5:39 AM, "Kimmo Paasiala" wrote: > > On Wed, Oct 9, 2013 at 2:03 PM, George Mitchell wrote: > > On 10/09/13 03:20, Hans Ottevanger wrote: > >> > >> On 10/08/13 04:31, Lyndon Nerenberg wrote: > >>> > >>> Okay folks, can we make a call about keeping the RCS tools in the base? > >>> > >>> The proponents wanting to remove RCS need to speak up and make their > >>> technical case. > >>> > >> > >> Technically it is quite simple: I need RCS to start versioning config > >> files, even before starting any customization. I know about several > >> others who do the same (and have not yet defected to Linux). > >> > >> I would like to see RCS to be put back into the tree for 10.0. If it > >> really -has- to be victimized by the current anti-GPL crusade, it could > >> be replaced by OpenRCS in 11. > >> > >> And as a long time hard-core user I would appreciate if this kind of > >> changes were performed only after at least -some- public discussion. > >> The way this change was sneaked in (though apparently with approval of > >> core@), reminds me more of a Secret Society than of an Open Source > >> project. > >> > >> Regards, > >> > >> Hans > >> > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to " freebsd-current-unsubscribe@freebsd.org" > >> > > > > +1, enthusiastically. -- George > > > > +1 also to OpenRCS allthough I hate anything related to RCS/CVS with a > passion. I do however recognize the need for a simple revision control > system in the base, svnlite would fill the need maybe but it's good to > have other options too. > > -Kimmo OK, but please, can we replace RCS with Fossil in 11 then? That adds a real improvement to FreeBSD while giving people plenty of time to prepare. Jos From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:05:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3EE26F42 for ; Wed, 9 Oct 2013 16:05:16 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id EE61D219C for ; Wed, 9 Oct 2013 16:05:14 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 5D09B1E0FA; Wed, 9 Oct 2013 16:05:11 +0000 (UTC) Message-ID: <52557ED1.5020008@allanjude.com> Date: Wed, 09 Oct 2013 12:05:37 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Matthias Gamsjager Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:05:16 -0000 On 2013-10-09 03:22, Matthias Gamsjager wrote: > Hi, > > tried 10-8 iso in Virtualbox but after reboot I was looking at a > bootloader with a nice '-' but nothing more. > post setup 'gpart list' showed no entries at all. > > > > > On Wed, Oct 9, 2013 at 5:49 AM, Allan Jude > wrote: > > On 2013-10-07 15:59, Allan Jude wrote: > > Devin Teske and I have been working on a big patch to bsdinstall to > > implement installing on a ZFS pool. It supports both GPT and > MBR, the 4k > > sector gnop trick, and optional GELI encryption. We would like > to commit > > this in time for 10.0-BETA1 so it needs some testing to work out any > > obvious bugs before we send it off to re@ to get it committed. > > > > It includes a single configuration menu that allows you to > select all of > > the required details, including which drives to use (gets > details from > > camcontrol, also includes an inspection utility that presents the > > detailed output of camcontrol inquiry/identify, and gpart show), > what > > ZFS RAID level to use (taking in to consideration the selected > number of > > drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. > > > > > > Additional, it includes some other changes to bsdinstall: > > 1. Change the default to the 'non-standard keyboard mapping' > prompt to no > > 2. Replace the 3 separate dialogs to configure an ipv4 address > with just 1 > > 3. Remove the dialog asking if you wish to enable crash dumps, this > > feature has been combined into the regular 'services to enable' > dialog > > and enabled by default > > > > > > You can browse the patches here: > > http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ > > > > I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, > > available compressed (48 MB) or uncompressed (211 MB): > > > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz > > > > http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso > > > > > > We look forward to your feedback > > > > We've made more improvements, including corporating most all of the > feedback we've gotten so far > > > Outstanding items: > 1. Apply the changes to ipv6 config the way we did ipv4 > 2. improve disk identification (model info and serial # instead of one > or the other) > 3. Include a helpful message before the GELI step where you have to > enter your password many times, the user will be less confused if > it is > explained why they have to enter their password 3 * number of > disks times > 4. Validate vdev type choice inside the vdev type menu, and warn the > user if they have made an invalid selection, so they can add more > disks > or chance their selection, without having to try to start the > installation first > 5. Whatever else you guys find wrong tonight > > I generated new test images, and attached the patch (which got REALLY > big when Devin Teske decided to fix "all of the things": > > http://www.allanjude.com/bsd/zfsbootonly.2013-10-08.iso.xz > > http://www.allanjude.com/bsd/zfsbootonly.2013-10-08.iso > > > -- > Allan Jude > > > _______________________________________________ > freebsd-current@freebsd.org > mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org > " > > This was a variable scoping error made by Devin when he refactored some of the code into a subroutine. I have fixed it -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:12:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E4F805C4; Wed, 9 Oct 2013 16:12:43 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 93B1C2244; Wed, 9 Oct 2013 16:12:43 +0000 (UTC) Received: by mail-qe0-f51.google.com with SMTP id q19so796540qeb.10 for ; Wed, 09 Oct 2013 09:12:42 -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=iZ2hKrav6oH6bEEuIT0uOAACtUbHPjTKPUtbKmzvZGc=; b=Mw4SFMu8Tcvh7bSYlJ4wlXLkSfMFGODtoFDBQghS4GzC+pRJdskp+Vsv7HDa2ZRMN2 XXygw8SF28kQe7c+mcU/INELtVCufghTN/L6PgF36Fj2D2c3BdnxhvJzTkpJylZ3S8BQ T+st2pdH+gUi251uua8EfS8zXlO3ZpubjsktUOsBZ0UazmxAVfKGKHmHrWSbkCYoAaoB 91QtlNPyFF7JWjUWAdUVxAe2H5Q6Pvmg9DWRhxQzq90OQuGxk0t080sATJlzA6G7n/qa 4DG1Yp2o/ow6SZuoLEByXMUFQZvu3DU44SFIDrxG/poE+DBgHuMu1UjheGbRFlxK+MZD +fFA== MIME-Version: 1.0 X-Received: by 10.49.109.170 with SMTP id ht10mr10461063qeb.27.1381335162607; Wed, 09 Oct 2013 09:12:42 -0700 (PDT) Received: by 10.49.39.33 with HTTP; Wed, 9 Oct 2013 09:12:42 -0700 (PDT) In-Reply-To: <52555D1C.8010407@freebsd.org> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> Date: Wed, 9 Oct 2013 09:12:42 -0700 Message-ID: Subject: Re: rcs From: Freddie Cash To: Julian Elischer Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Alfred Perlstein , FreeBSD-Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:12:44 -0000 On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer wrote: > On 10/9/13 2:35 AM, Freddie Cash wrote: > >> On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein wrote: >> >> You're right on the money, to be honest this is one of the reasons why >>> I've switched to using OSX as my desktop OS. >>> >>> zsh, vim, screen by default. and upgrades work. At the end of the day >>> I'm spending time doing work, not mucking about my workspace to make it >>> usable for development. >>> >>> I think this was brought up at BSDCan in the discussion about making >>> FreeBSD a more featured development platform. >>> >>> Speaking of... has anyone tried PCBSD? >>> >> >> PC-BSD isn't much different from FreeBSD. The installer is GUI and >> support >> ZFS, there are some GUI setup tools on first boot for X, there are some >> GUI >> tools to select binary drivers for X, and there =E2=80=8B=E2=80=8Bare wo= rking pkgng repos >> available. >> >> I had a lot of issues with PC-BSD 9.0 and 9.1 as I was trying to do thin= gs >> "the FreeBSD way" which broke a lot of things that were done "the PC-BSD >> way" (aka don't manually edit config files used for booting). >> >> =E2=80=8BSwitching to the "rolling-release" (aka PC-BSD 9-STABLE) and mo= ving all >> my >> config file edits into .conf.local fixed my issues. Things ha= ve >> been running smooth, and I finally understand the beauty and simplicity = of >> freebsd-update + pkg. OS gets updated once per month, packages get >> updated >> twice per month, no more compiling things from source. It's like using >> Ubuntu/Debian but with the power and features of FreeBSD. :) >> =E2=80=8B >> > > When they went to a ZFS-only system, using GRUB, with no alternative, the= n > I'm afraid they lost me. > I want a root filesystem on UFS for reliabailty and simpleness. I can > debug it's media if needed. > Before then I really liked it (though ther eis not enough information on > how it works interneally if you want to use it. > hopefully that will come.. and I LIKE PBIs FreeBSD should adopt PBIs for > sure. > With PBIs you could make even quite base items separately installable. > versioning problems go away. > There's no GRUB in a default install of PC-BSD 9.0, 9.1, or 9.2. Even on a ZFS-only setup (which is what I run). It's using the FreeBSD loader, with custom artwork and menus. There's also nothing stopping you from installing / onto UFS. At least, I didn't see anything that would prevent it when I installed it originally. Granted, that was with 9.1, so the installer may be different in 9.2. I tried to use PBIs, but really messed up the system doing so. /usr was just a directory on /, on a USB stick, and ran out of room. Tried various things to get it off / and b0rked the system. Even after moving to ZFS-on-root and getting away from filesystem limits, I still couldn't get PBIs to upgrade properly. Since moving away from PBIs, away from ports, away from pkg_* tools, and sticking strictly with pkg, everything has been running smoothly. The experience with pkg on PC-BSD gives me hope for FreeBSD again (too many issues in the past with ports and pkg_* tools, even when using only portmaster). For desktops, a binary-only system using freebsd-update and pkg is so much nicer. For servers, implementing your own freebsd-update server and pkg repo (via poudriere) is so much nicer. If I never have to compile a port on a remote system again, I will be a happy man. :) To each their own, of course. :) --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:19:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D031091B; Wed, 9 Oct 2013 16:19:51 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 99ACC22BB; Wed, 9 Oct 2013 16:19:51 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id r99GJnxX019638 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 11:19:50 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Wed, 9 Oct 2013 11:19:48 -0500 From: "Teske, Devin" To: Warren Block Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxHPFPJPIP8ZCyUiSsjBzr2++AA== Date: Wed, 9 Oct 2013 16:19:48 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4AFC9@LTCFISWMSGMB21.FNFIS.com> References: <52546844.2010608@freebsd.org> <5254774C.8030204@pix.net> <525478EA.8080207@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC46904@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <2C435C588385274F8812895790825488@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-09_05:2013-10-09,2013-10-09,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" , Nathan Whitehorn X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:19:52 -0000 On Oct 9, 2013, at 8:29 AM, Warren Block wrote: > On Tue, 8 Oct 2013, Teske, Devin wrote: >=20 >> "But shell is nasty; slow; and not as powerful as C" (it depends in what >> context; the first is rhetoric, the second is only true for poor impleme= nt- >> ations, and the third may be true in some contexts, but I consider the >> answer to "how maintainable is it" to be a factor in the "power" of a >> language, so don't necessarily consider C to be more powerful than >> shell as the latter is as-or-more maintainable with fewer LoC and a >> higher return on investment; see previous [above] arguments). >=20 > My question would be: why are sh and C the only choices? If the answer i= s "because that's all we have in base", is that a valid concern? >=20 > As far as sh, it lacks many high- or even mid-level constructs and has re= al problems with quoting, Enter helper functions... dteske@scribe9.vicor.com bsdconfig $ grep '^# f_' /usr/share/bsdconfig/stri= ngs.subr=20 # f_substr "$string" $start [ $length ] # f_snprintf $var_to_set $size $format ... # f_vsnprintf $var_to_set $size $format $format_args # f_longest_line_length # f_number_of_lines # f_isinteger $arg # f_uriencode [$text] # f_uridecode [$text] # f_replaceall $string $find $replace [$var_to_set] # f_str2varname $string [$var_to_set] # f_shell_escape $string [$var_to_set] # f_shell_unescape $string [$var_to_set] # f_expand_number $string [$var_to_set] The ones dealing specifically with quoting are f_shell_escape() and f_shell= _unescape(). With those two helper functions, I consider quoting in sh(1) to be complete= and maleable to handle all situations. > parsing, Surely, a strength. It can take a while to engrain or impart all the expans= ions and at- what stage (and in what context) they are performed, but when you understan= d the mechanics of (for example) in what order each element (escaped-sequences, p= arams, newlines, and sub-shells) is expanded... the parsing becomes an asset, not a hindrance (imho). Not to mention the flexibility afforded by "compound stri= ngs". Take for example, the following syntax (leveraging ordered expansion and co= mpound strings): f_dialog_input bar \ 'Enter *any* text; including globs [*] and shell special chars [$`#'"']..." f_dialog_input baz \ "Enter some *more* non-conforming text please..." f_shell_escape "$bar" bar f_shell_escape "$baz" baz items=3D"'$bar' '$baz'" show=3D"You entered:\n1=3D%s\n2=3D%s\n" eval printf \"\$show\" $items I'd be surprised if you could get anything out but the values you enter. > and output (2>&1 >&3, for example). I think it helps to highlight a technique for solving the general-purpose i= ssue of how you launch a program and have it talk to a parent's maintained file-des= criptor. In C, you'd have to pass special args to posix_spawn(3) to get this functio= nality. Talking about succinctness of syntax... that sequence is likely much shorte= r than any syntax I've ever seen in C for setting up file descriptors. I've interf= aced with dialog(1) from within C and getting the data back from it is non-trivial. ASIDE: You may be asking yourself... why on Earth would you fork-exec an instance of dialog(1) from within C instead of using dialog(3)? There are s= ome rare cases when this is advantageous. Usually when you want to support a dr= op- in replacement (like Xdialog(1)) for a long-running stateful widget (e.g. g= auge). Usually (>=3D99% of the time) a C program _should_ use dialog(3) but in tho= se rare cases ( see http://druidbsd.cvs.sf.net/viewvc/druidbsd/fdpv/ ) thank g= oodness I haven't had to mangle the file descriptors to get back any data (I call o= ut to gauge and just pump it massive amounts of data via stdin through a pipe passed to= the posix_spawn(3) call -- no data to read back. So I don't see the above syntax as anything to point out -- C programs have= more complicated setup for doing the same thing (they just have to do it less of= ten). Oh... and in bsdconfig, you'll notice I don't do that. Upon initialization = I clone the *real* terminal fd's _once_ and then use variables to reference the dup'd f= d. > These make it harder to do things (aka, more code to accomplish a task, m= ore code to be maintained, more difficult to modify) than the higher level = Perubython languages. >=20 Only because those languages have APIs that handle those things. Which I might add that those APIs have to be maintained. In that spirit, bsdconfig(8) provides the API for shell -- and similarly, said API (like mo= st APIs) will be need much less maintenance than the programs using said API (how often do we make changes to posix_spawn(3)? or how often does Perubython change an API call?). It's in that light that the bsdconfig(8) shell API is also treated just lik= e any other API with respect to changes (I treat all the "*.subr" includes as tho= ugh they are an ABI -- changes to function arguments must be well thought out). > In any case, thanks for working on this. A functioning program in any la= nguage is better than a non-existent "better" one. Indeed. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:23:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E336BA90; Wed, 9 Oct 2013 16:23:07 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qe0-x22d.google.com (mail-qe0-x22d.google.com [IPv6:2607:f8b0:400d:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 917FE2317; Wed, 9 Oct 2013 16:23:07 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id 8so783045qea.4 for ; Wed, 09 Oct 2013 09:23:06 -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=/OYtnDc/mxx7OwqXmeEXhupeeQBOMw9R5JwHnMyBsBA=; b=uc9/WkbcWYf5xKhzzbkSBgkkaZU118VPsWIT99rU0YtY4Z80InPj7hW+iDUfr8FV7g B0pWxNQeWrWmucDzvRS8cINDCPZcWfEbK0JiIyXOMWhBzp5l8gF340VJ0aBLcwm/3OId SrF6M1PkzGRTX9jUT6txess87EABfDKTp4bU8JZgX35z0UyNczV3aTs9HxZ1XqX60wDz 5TrEM5kngG0GfmOh5ZfFBSZWx62jNrbZjLPpydUtoTmSG/rk5zFersvRCoBhM3MDPn5C z08tH8m2zw6EjGDcaNFAXWIz7Bt1Pi8Bgp0RWKEOr8CsPSmUOmu1yiZJxIpPZtLFahqm LchQ== MIME-Version: 1.0 X-Received: by 10.224.54.66 with SMTP id p2mr6409681qag.87.1381335784611; Wed, 09 Oct 2013 09:23:04 -0700 (PDT) Received: by 10.49.39.33 with HTTP; Wed, 9 Oct 2013 09:23:04 -0700 (PDT) In-Reply-To: References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> Date: Wed, 9 Oct 2013 09:23:04 -0700 Message-ID: Subject: Re: rcs From: Freddie Cash To: Julian Elischer Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD-Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:23:08 -0000 On Wed, Oct 9, 2013 at 9:12 AM, Freddie Cash wrote: > On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer wrote= : > >> On 10/9/13 2:35 AM, Freddie Cash wrote: >> >>> On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein wrote: >>> >>> You're right on the money, to be honest this is one of the reasons why >>>> I've switched to using OSX as my desktop OS. >>>> >>>> zsh, vim, screen by default. and upgrades work. At the end of the da= y >>>> I'm spending time doing work, not mucking about my workspace to make i= t >>>> usable for development. >>>> >>>> I think this was brought up at BSDCan in the discussion about making >>>> FreeBSD a more featured development platform. >>>> >>>> Speaking of... has anyone tried PCBSD? >>>> >>> >>> PC-BSD isn't much different from FreeBSD. The installer is GUI and >>> support >>> ZFS, there are some GUI setup tools on first boot for X, there are some >>> GUI >>> tools to select binary drivers for X, and there =E2=80=8B=E2=80=8Bare w= orking pkgng repos >>> available. >>> >>> I had a lot of issues with PC-BSD 9.0 and 9.1 as I was trying to do >>> things >>> "the FreeBSD way" which broke a lot of things that were done "the PC-BS= D >>> way" (aka don't manually edit config files used for booting). >>> >>> =E2=80=8BSwitching to the "rolling-release" (aka PC-BSD 9-STABLE) and m= oving all >>> my >>> config file edits into .conf.local fixed my issues. Things >>> have >>> been running smooth, and I finally understand the beauty and simplicity >>> of >>> freebsd-update + pkg. OS gets updated once per month, packages get >>> updated >>> twice per month, no more compiling things from source. It's like using >>> Ubuntu/Debian but with the power and features of FreeBSD. :) >>> =E2=80=8B >>> >> >> When they went to a ZFS-only system, using GRUB, with no alternative, >> then I'm afraid they lost me. >> I want a root filesystem on UFS for reliabailty and simpleness. I can >> debug it's media if needed. >> Before then I really liked it (though ther eis not enough information on >> how it works interneally if you want to use it. >> hopefully that will come.. and I LIKE PBIs FreeBSD should adopt PBIs fo= r >> sure. >> With PBIs you could make even quite base items separately installable. >> versioning problems go away. >> > > There's no GRUB in a default install of PC-BSD 9.0, 9.1, or 9.2. Even on > a ZFS-only setup (which is what I run). It's using the FreeBSD loader, > with custom artwork and menus. > =E2=80=8BHrm, it seems they've changed things with the 9.2 installer. It d= oes use GRUB2 (ewwww!) for the boot loader, and integrates support for ZFS boot environments (via beadm) into it. :( Shame they didn't use the BE support in the FreeBSD loader for this. Wonder if my 9-STABLE-based PC-BSD install will get "upgraded" to GRUB? --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:23:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8FD2EB9E for ; Wed, 9 Oct 2013 16:23:33 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5A5E42326 for ; Wed, 9 Oct 2013 16:23:33 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id r99GNPwB009410 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 11:23:25 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Wed, 9 Oct 2013 11:23:24 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxQvfPJPIP8ZCyUiSsjBzr2++AA== Date: Wed, 9 Oct 2013 16:23:22 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4B002@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> <52557ED1.5020008@allanjude.com> In-Reply-To: <52557ED1.5020008@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <89EB3FA1CA999647B312885908724571@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-09_05:2013-10-09,2013-10-09,1970-01-01 signatures=0 Cc: Matthias Gamsjager , "Teske, Devin" , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:23:33 -0000 On Oct 9, 2013, at 9:05 AM, Allan Jude wrote: > On 2013-10-09 03:22, Matthias Gamsjager wrote: >> Hi, >>=20 >> tried 10-8 iso in Virtualbox but after reboot I was looking at a >> bootloader with a nice '-' but nothing more.=20 >> post setup 'gpart list' showed no entries at all. >>=20 >>=20 >>=20 >>=20 >> On Wed, Oct 9, 2013 at 5:49 AM, Allan Jude > > wrote: >>=20 >> On 2013-10-07 15:59, Allan Jude wrote: >>> Devin Teske and I have been working on a big patch to bsdinstall to >>> implement installing on a ZFS pool. It supports both GPT and >> MBR, the 4k >>> sector gnop trick, and optional GELI encryption. We would like >> to commit >>> this in time for 10.0-BETA1 so it needs some testing to work out any >>> obvious bugs before we send it off to re@ to get it committed. >>>=20 >>> It includes a single configuration menu that allows you to >> select all of >>> the required details, including which drives to use (gets >> details from >>> camcontrol, also includes an inspection utility that presents the >>> detailed output of camcontrol inquiry/identify, and gpart show), >> what >>> ZFS RAID level to use (taking in to consideration the selected >> number of >>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>=20 >>>=20 >>> Additional, it includes some other changes to bsdinstall: >>> 1. Change the default to the 'non-standard keyboard mapping' >> prompt to no >>> 2. Replace the 3 separate dialogs to configure an ipv4 address >> with just 1 >>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>> feature has been combined into the regular 'services to enable' >> dialog >>> and enabled by default >>>=20 >>>=20 >>> You can browse the patches here: >>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>=20 >>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>> available compressed (48 MB) or uncompressed (211 MB): >>>=20 >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>=20 >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>=20 >>>=20 >>> We look forward to your feedback >>>=20 >>=20 >> We've made more improvements, including corporating most all of the >> feedback we've gotten so far >>=20 >>=20 >> Outstanding items: >> 1. Apply the changes to ipv6 config the way we did ipv4 >> 2. improve disk identification (model info and serial # instead of one >> or the other) >> 3. Include a helpful message before the GELI step where you have to >> enter your password many times, the user will be less confused if >> it is >> explained why they have to enter their password 3 * number of >> disks times >> 4. Validate vdev type choice inside the vdev type menu, and warn the >> user if they have made an invalid selection, so they can add more >> disks >> or chance their selection, without having to try to start the >> installation first >> 5. Whatever else you guys find wrong tonight >>=20 >> I generated new test images, and attached the patch (which got REALLY >> big when Devin Teske decided to fix "all of the things": >>=20 >> http://www.allanjude.com/bsd/zfsbootonly.2013-10-08.iso.xz >>=20 >> http://www.allanjude.com/bsd/zfsbootonly.2013-10-08.iso >>=20 >>=20 >> -- >> Allan Jude >>=20 >>=20 >> _______________________________________________ >> freebsd-current@freebsd.org >> mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org >> " >>=20 >>=20 > This was a variable scoping error made by Devin when he refactored some > of the code into a subroutine. I have fixed it >=20 Ouch and apologies. It was too hard to see at 2AM after starting-in on a deeper pathos to the k= eymap patches (which I'm still working on). Allan alerted me to the issue but whe= n I started digging-in, I realized much deeper changes were required. And then I passed= out around 2:30AM (keyboard-faceplant). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:33:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D18BBF25 for ; Wed, 9 Oct 2013 16:33:36 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 8E24C23E3 for ; Wed, 9 Oct 2013 16:33:36 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 5B4501E1A6 for ; Wed, 9 Oct 2013 16:33:32 +0000 (UTC) Message-ID: <52558577.5020401@allanjude.com> Date: Wed, 09 Oct 2013 12:33:59 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:33:37 -0000 On 2013-10-09 12:23, Freddie Cash wrote: > On Wed, Oct 9, 2013 at 9:12 AM, Freddie Cash wrote: > >> On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer wrote: >> >>> On 10/9/13 2:35 AM, Freddie Cash wrote: >>> >>>> On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein wrote: >>>> >>>> You're right on the money, to be honest this is one of the reasons why >>>>> I've switched to using OSX as my desktop OS. >>>>> >>>>> zsh, vim, screen by default. and upgrades work. At the end of the day >>>>> I'm spending time doing work, not mucking about my workspace to make it >>>>> usable for development. >>>>> >>>>> I think this was brought up at BSDCan in the discussion about making >>>>> FreeBSD a more featured development platform. >>>>> >>>>> Speaking of... has anyone tried PCBSD? >>>>> >>>> PC-BSD isn't much different from FreeBSD. The installer is GUI and >>>> support >>>> ZFS, there are some GUI setup tools on first boot for X, there are some >>>> GUI >>>> tools to select binary drivers for X, and there ​​are working pkgng repos >>>> available. >>>> >>>> I had a lot of issues with PC-BSD 9.0 and 9.1 as I was trying to do >>>> things >>>> "the FreeBSD way" which broke a lot of things that were done "the PC-BSD >>>> way" (aka don't manually edit config files used for booting). >>>> >>>> ​Switching to the "rolling-release" (aka PC-BSD 9-STABLE) and moving all >>>> my >>>> config file edits into .conf.local fixed my issues. Things >>>> have >>>> been running smooth, and I finally understand the beauty and simplicity >>>> of >>>> freebsd-update + pkg. OS gets updated once per month, packages get >>>> updated >>>> twice per month, no more compiling things from source. It's like using >>>> Ubuntu/Debian but with the power and features of FreeBSD. :) >>>> ​ >>>> >>> When they went to a ZFS-only system, using GRUB, with no alternative, >>> then I'm afraid they lost me. >>> I want a root filesystem on UFS for reliabailty and simpleness. I can >>> debug it's media if needed. >>> Before then I really liked it (though ther eis not enough information on >>> how it works interneally if you want to use it. >>> hopefully that will come.. and I LIKE PBIs FreeBSD should adopt PBIs for >>> sure. >>> With PBIs you could make even quite base items separately installable. >>> versioning problems go away. >>> >> There's no GRUB in a default install of PC-BSD 9.0, 9.1, or 9.2. Even on >> a ZFS-only setup (which is what I run). It's using the FreeBSD loader, >> with custom artwork and menus. >> > ​Hrm, it seems they've changed things with the 9.2 installer. It does use > GRUB2 (ewwww!) for the boot loader, and integrates support for ZFS boot > environments (via beadm) into it. :( Shame they didn't use the BE support > in the FreeBSD loader for this. Wonder if my 9-STABLE-based PC-BSD install > will get "upgraded" to GRUB? > The reason they went to grub2, is that the way the freebsd loader menus work, it loads the kernel before it draws the menu. This means if there is a problem with your kernel (probably the most valuable time to have boot environments) then the menu never comes up, and you cannot select which BE to boot from. Grub doesn't rely on a FreeBSD kernel until after you select which BE to boot from. Kris and I discussed it at length with Devin Teske, and while he has demonstrated being able to populate a lower menu with the ZFS datasets, I am not sure if the other issue can be resolved. -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:37:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 35F6B1A0; Wed, 9 Oct 2013 16:37:30 +0000 (UTC) (envelope-from hans@beastielabs.net) Received: from mail.beastielabs.net (beasties.demon.nl [82.161.3.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BBA4A241D; Wed, 9 Oct 2013 16:37:29 +0000 (UTC) Received: from merom.hotsoft.nl (merom.hotsoft.nl [192.168.0.12]) by mail.beastielabs.net (8.14.5/8.14.5) with ESMTP id r99GbQPo048918; Wed, 9 Oct 2013 18:37:26 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <52558646.2040004@beastielabs.net> Date: Wed, 09 Oct 2013 18:37:26 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Julian Elischer Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <52555E86.7010504@freebsd.org> In-Reply-To: <52555E86.7010504@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , Lyndon Nerenberg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:37:30 -0000 On 10/09/13 15:47, Julian Elischer wrote: > On 10/9/13 3:20 PM, Hans Ottevanger wrote: >> On 10/08/13 04:31, Lyndon Nerenberg wrote: >>> Okay folks, can we make a call about keeping the RCS tools in the base? >>> >>> The proponents wanting to remove RCS need to speak up and make their >>> technical case. >>> >> Technically it is quite simple: I need RCS to start versioning config >> files, even before starting any customization. I know about several >> others who do the same (and have not yet defected to Linux). >> >> I would like to see RCS to be put back into the tree for 10.0. If it >> really -has- to be victimized by the current anti-GPL crusade, it could >> be replaced by OpenRCS in 11. >> >> And as a long time hard-core user I would appreciate if this kind of >> changes were performed only after at least -some- public discussion. >> The way this change was sneaked in (though apparently with approval of >> core@), reminds me more of a Secret Society than of an Open Source >> project. > > no, with private approval of a CORE MEMBER.. that is quite a different > thing.. > Core, AFAIK has not ruled on this sort of topic.. (and actually it's not > really it's job to do so unless it's resolving a dispute.) > You are probably right, but as a relative outsider I only saw this in the commit message: Log: Good bye RCS. You will be missed. (devel/rcs and devel/rcs57 are available as alternatives) Approved by: core Approved by: re (hrs) which led me to my possibly wrong conclusion about the approval of core@. Kind regards, Hans From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:42:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 68B98310 for ; Wed, 9 Oct 2013 16:42:36 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 44869247A for ; Wed, 9 Oct 2013 16:42:36 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id E107366C80 for ; Wed, 9 Oct 2013 09:42:35 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 67480-04 for ; Wed, 9 Oct 2013 09:42:35 -0700 (PDT) Received: from [192.168.0.51] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id 2F1B866C79 for ; Wed, 9 Oct 2013 09:42:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ixsystems.com; s=newknight0; t=1381336955; bh=N3G2sIcCaVBuNzoEa38NhpnMcQ7VGxHobIHbImRQ6Zo=; h=Date:From:To:Subject:References:In-Reply-To; b=iUQHbtunAf+7tYMqy0LG2f94moZUu8PXbWWGc1hZbLpD1e5TIhPYZA73jXfYQaMF+ AkoNiyS0NQ2aOIP8uU4Y6WQvk7oQpeh63mlOAffylMPIWKMxZftKeIZe3zsoyMh+J7 n25SuJen355jYrP/6ND5y1M1iXmtjVoiI9v0pboI= Message-ID: <52558779.2070203@pcbsd.org> Date: Wed, 09 Oct 2013 12:42:33 -0400 From: Kris Moore User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: rcs References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> In-Reply-To: <52558577.5020401@allanjude.com> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:42:36 -0000 On 10/09/2013 12:33, Allan Jude wrote: > On 2013-10-09 12:23, Freddie Cash wrote: >> On Wed, Oct 9, 2013 at 9:12 AM, Freddie Cash wrote: >> >>> On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer wrote: >>> >>>> On 10/9/13 2:35 AM, Freddie Cash wrote: >>>> >>>>> On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein wrote: >>>>> >>>>> You're right on the money, to be honest this is one of the reasons why >>>>>> I've switched to using OSX as my desktop OS. >>>>>> >>>>>> zsh, vim, screen by default. and upgrades work. At the end of the day >>>>>> I'm spending time doing work, not mucking about my workspace to make it >>>>>> usable for development. >>>>>> >>>>>> I think this was brought up at BSDCan in the discussion about making >>>>>> FreeBSD a more featured development platform. >>>>>> >>>>>> Speaking of... has anyone tried PCBSD? >>>>>> >>>>> PC-BSD isn't much different from FreeBSD. The installer is GUI and >>>>> support >>>>> ZFS, there are some GUI setup tools on first boot for X, there are some >>>>> GUI >>>>> tools to select binary drivers for X, and there ​​are working pkgng repos >>>>> available. >>>>> >>>>> I had a lot of issues with PC-BSD 9.0 and 9.1 as I was trying to do >>>>> things >>>>> "the FreeBSD way" which broke a lot of things that were done "the PC-BSD >>>>> way" (aka don't manually edit config files used for booting). >>>>> >>>>> ​Switching to the "rolling-release" (aka PC-BSD 9-STABLE) and moving all >>>>> my >>>>> config file edits into .conf.local fixed my issues. Things >>>>> have >>>>> been running smooth, and I finally understand the beauty and simplicity >>>>> of >>>>> freebsd-update + pkg. OS gets updated once per month, packages get >>>>> updated >>>>> twice per month, no more compiling things from source. It's like using >>>>> Ubuntu/Debian but with the power and features of FreeBSD. :) >>>>> ​ >>>>> >>>> When they went to a ZFS-only system, using GRUB, with no alternative, >>>> then I'm afraid they lost me. >>>> I want a root filesystem on UFS for reliabailty and simpleness. I can >>>> debug it's media if needed. >>>> Before then I really liked it (though ther eis not enough information on >>>> how it works interneally if you want to use it. >>>> hopefully that will come.. and I LIKE PBIs FreeBSD should adopt PBIs for >>>> sure. >>>> With PBIs you could make even quite base items separately installable. >>>> versioning problems go away. >>>> >>> There's no GRUB in a default install of PC-BSD 9.0, 9.1, or 9.2. Even on >>> a ZFS-only setup (which is what I run). It's using the FreeBSD loader, >>> with custom artwork and menus. >>> >> ​Hrm, it seems they've changed things with the 9.2 installer. It does use >> GRUB2 (ewwww!) for the boot loader, and integrates support for ZFS boot >> environments (via beadm) into it. :( Shame they didn't use the BE support >> in the FreeBSD loader for this. Wonder if my 9-STABLE-based PC-BSD install >> will get "upgraded" to GRUB? >> > The reason they went to grub2, is that the way the freebsd loader menus > work, it loads the kernel before it draws the menu. This means if there > is a problem with your kernel (probably the most valuable time to have > boot environments) then the menu never comes up, and you cannot select > which BE to boot from. Grub doesn't rely on a FreeBSD kernel until after > you select which BE to boot from. > > Kris and I discussed it at length with Devin Teske, and while he has > demonstrated being able to populate a lower menu with the ZFS datasets, > I am not sure if the other issue can be resolved. > Yea, GRUB is not my first choice, but ATM this is the "cleanest" way we can do ZFS BE's. However if you don't like ZFS / GRUB, you can always use regular FreeBSD and just grab our toolchain from sysutils/pcbsd-utils* in ports or use our PKGNG repo: http://wiki.pcbsd.org/index.php/Turn_FreeBSD_into_PC-BSD%C2%AE I'm planning on using GRUB to do UEFI booting for 10.0 as well. But when the FreeBSD loader matures to the point of having support for all these features, I'll gladly move us back. -- Kris Moore PC-BSD Software iXsystems From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:46:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 74A324F9 for ; Wed, 9 Oct 2013 16:46:02 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.31.26]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CD1DB24A5 for ; Wed, 9 Oct 2013 16:46:01 +0000 (UTC) Received: from [78.35.138.113] (helo=fabiankeil.de) by smtprelay03.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1VTwik-0001kQ-6B for freebsd-current@freebsd.org; Wed, 09 Oct 2013 18:34:46 +0200 Date: Wed, 9 Oct 2013 18:34:46 +0200 From: Fabian Keil To: FreeBSD Current Subject: claws-mail deadlocking in iconv Message-ID: <73d40037.635a97ef@fabiankeil.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/nZJzfi+tvHOJV7AttwJY8NG"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:46:02 -0000 --Sig_/nZJzfi+tvHOJV7AttwJY8NG Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable After the iconv import claws-mail started to deadlock in iconv every now and then on my system, which prevented claws-mail from rendering windows or reacting to input. So far I haven't been able to reproduce this intentionally and various rebuilds of ports, kernel and userland (mainly for other reasons) had no effect. When the problem occurs, trying to attach to the process causes gdb and gdb76 to crash which also crashes claws-mail, but sending SIGABRT causes a proper core dump that can be analysed with gdb. The backtraces always show that there is only one thread running and it's trying to lock cm_lock in _citrus_mapper_close(), which apparently is already locked due to a _citrus_mapper_close() recursion. Examples: #0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:= 37 37 RSYSCALL_ERR(_umtx_op) [New Thread 80a806400 (LWP 100487/claws-mail)] (gdb) where #0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:= 37 #1 0x00000008084861a6 in __thr_rwlock_wrlock (rwlock=3D0x80a8a47c0, tsp=3D= ) at /usr/src/lib/libthr/thread/thr_umtx.c:296 #2 0x0000000808489b1d in rwlock_wrlock_common (rwlock=3D, abstime=3D0x0) at /usr/src/lib/libthr/thread/thr_rwlock.c:267 #3 0x0000000808489a8b in _pthread_rwlock_wrlock (rwlock=3D0x80a8a47c0) at = /usr/src/lib/libthr/thread/thr_rwlock.c:289 #4 0x000000080911e848 in _citrus_mapper_close (cm=3D0x80b5a2d80) at /usr/s= rc/lib/libc/iconv/citrus_mapper.c:375 #5 0x000000080d205d18 in _citrus_mapper_serial_mapper_uninit (cm=3D0x80b5a= 2d40) at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/cit= rus_mapper_serial.c:110 #6 0x000000080911e8d7 in mapper_close (cm=3D0x80b5a2d40) at /usr/src/lib/l= ibc/iconv/citrus_mapper.c:188 #7 0x000000080911e88c in _citrus_mapper_close (cm=3D)= at /usr/src/lib/libc/iconv/citrus_mapper.c:384 #8 0x000000080c4e83f3 in close_srcs (sl=3D0x80b591140) at /usr/src/lib/lib= iconv_modules/iconv_std/citrus_iconv_std.c:206 #9 0x000000080c4e7dc9 in _citrus_iconv_std_iconv_uninit_shared (ci=3D) at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_s= td.c:415 #10 0x00000008090f3f95 in release_shared (ci=3D0x80a8ee630) at /usr/src/lib= /libc/iconv/citrus_iconv.c:99 #11 0x00000008090f4002 in _citrus_iconv_close (cv=3D0x80d88d5d0) at /usr/sr= c/lib/libc/iconv/citrus_iconv.c:335 #12 0x00000008090f1ca6 in iconv_close (handle=3D0x80a8a47c0) at /usr/src/li= b/libc/iconv/iconv.c:131 #13 0x000000000046376d in conv_iconv_strdup (inbuf=3D0x7fffffff58b0 "\n", s= rc_code=3D0x80b5b4db0 "Windows-1252", dest_code=3D0x6f03d0 "UTF-8") at code= conv.c:895 #14 0x0000000000463d13 in conv_convert (conv=3D0x80b5a4e80, outbuf=3D0x7fff= ffff3720 "", outlen=3D8192, inbuf=3D0x7fffffff58b0 "\n") at codeconv.c:734 #15 0x00000000005e22ac in textview_write_line (textview=3D0x80a959cc0, str= =3D0x7fffffff58b0 "\n", conv=3D0x80b5a4e80, do_quote_folding=3D1) at textvi= ew.c:1573 #16 0x00000000005df8e4 in textview_write_body (textview=3D0x80a959cc0, mime= info=3D0x80aad2d00) at textview.c:1177 #17 0x00000000005e5363 in textview_add_part (textview=3D0x80a959cc0, mimein= fo=3D0x80aad2d00) at textview.c:826 #18 0x00000000005e4053 in recursive_add_parts (textview=3D0x80a959cc0, node= =3D0x80a826190) at textview.c:839 #19 0x00000000005e4302 in recursive_add_parts (textview=3D0x80a959cc0, node= =3D0x80aa81d20) at textview.c:888 #20 0x00000000005e4302 in recursive_add_parts (textview=3D0x80a959cc0, node= =3D0x80a828890) at textview.c:888 #21 0x00000000005defa1 in textview_add_parts (textview=3D0x80a959cc0, mimei= nfo=3D0x80b610700) at textview.c:898 #22 0x00000000005deb85 in textview_show_part (textview=3D0x80a959cc0, mimei= nfo=3D0x80b610700, fp=3D0x8094319a0) at textview.c:645 [...] #0 0x0000000808491b9c in __error () from /lib/libthr.so.3 #1 0x000000080848bb1d in rwlock_wrlock_common (rwlock=3D, abstime=3D0x0) at /usr/src/lib/libthr/thread/thr_rwlock.c:267 #2 0x000000080848ba8b in _pthread_rwlock_wrlock (rwlock=3D0x80a8ede20) at = /usr/src/lib/libthr/thread/thr_rwlock.c:289 #3 0x000000080911f848 in _citrus_mapper_close (cm=3D0x80a8bfc40) at /usr/s= rc/lib/libc/iconv/citrus_mapper.c:375 #4 0x000000080ce02d18 in _citrus_mapper_serial_mapper_uninit (cm=3D0x80a8b= fc00) at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/cit= rus_mapper_serial.c:110 #5 0x000000080911f8d7 in mapper_close (cm=3D0x80a8bfc00) at /usr/src/lib/l= ibc/iconv/citrus_mapper.c:188 #6 0x000000080911f88c in _citrus_mapper_close (cm=3D)= at /usr/src/lib/libc/iconv/citrus_mapper.c:384 #7 0x000000080c5893f3 in close_srcs (sl=3D0x80a8edda0) at /usr/src/lib/lib= iconv_modules/iconv_std/citrus_iconv_std.c:206 #8 0x000000080c588dc9 in _citrus_iconv_std_iconv_uninit_shared (ci=3D) at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_s= td.c:415 #9 0x00000008090f4f95 in release_shared (ci=3D0x80b408890) at /usr/src/lib= /libc/iconv/citrus_iconv.c:99 #10 0x00000008090f5002 in _citrus_iconv_close (cv=3D0x80b782630) at /usr/sr= c/lib/libc/iconv/citrus_iconv.c:335 #11 0x00000008090f2ca6 in iconv_close (handle=3D0x80a8ede20) at /usr/src/li= b/libc/iconv/iconv.c:131 #12 0x000000000046376d in conv_iconv_strdup ( inbuf=3D0x80b600e00 "[...]"..., src_code=3D0x80b782640 "ISO-8859-15", d= est_code=3D0x80c07ab24 "UTF-8") at codeconv.c:895 #13 0x0000000000463f2f in conv_codeset_strdup ( inbuf=3D0x80b600e00 "[...]"..., src_code=3D0x80b782640 "ISO-8859-15", d= est_code=3D0x80c07ab24 "UTF-8") at codeconv.c:774 #14 0x000000080c07a1a7 in get_part_as_string (mimeinfo=3D0x80aad2d80) at pg= pinline.c:153 #15 0x000000080c078333 in pgpinline_is_encrypted (mimeinfo=3D0x80aad2d80) a= t pgpinline.c:375 [...] #0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:= 37 #1 0x00000008084861a6 in __thr_rwlock_wrlock (rwlock=3D0x80bf93f40, tsp=3D= ) at /usr/src/lib/libthr/thread/thr_umtx.c:296 #2 0x0000000808489b1d in rwlock_wrlock_common (rwlock=3D, abstime=3D0x0) at /usr/src/lib/libthr/thread/thr_rwlock.c:267 #3 0x0000000808489a8b in _pthread_rwlock_wrlock (rwlock=3D0x80bf93f40) at = /usr/src/lib/libthr/thread/thr_rwlock.c:289 #4 0x000000080911e848 in _citrus_mapper_close (cm=3D0x80bfa0b40) at /usr/s= rc/lib/libc/iconv/citrus_mapper.c:375 #5 0x000000080d08ad18 in _citrus_mapper_serial_mapper_uninit (cm=3D0x80bfa= 0b00) at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/cit= rus_mapper_serial.c:110 #6 0x000000080911e8d7 in mapper_close (cm=3D0x80bfa0b00) at /usr/src/lib/l= ibc/iconv/citrus_mapper.c:188 #7 0x000000080911e88c in _citrus_mapper_close (cm=3D)= at /usr/src/lib/libc/iconv/citrus_mapper.c:384 #8 0x000000080ae2c3f3 in close_srcs (sl=3D0x80bf9fbc0) at /usr/src/lib/lib= iconv_modules/iconv_std/citrus_iconv_std.c:206 #9 0x000000080ae2bdc9 in _citrus_iconv_std_iconv_uninit_shared (ci=3D) at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_s= td.c:415 #10 0x00000008090f3f95 in release_shared (ci=3D0x80bd59ac0) at /usr/src/lib= /libc/iconv/citrus_iconv.c:99 #11 0x00000008090f4002 in _citrus_iconv_close (cv=3D0x80dc1a3d0) at /usr/sr= c/lib/libc/iconv/citrus_iconv.c:335 #12 0x00000008090f1ca6 in iconv_close (handle=3D0x80bf93f40) at /usr/src/li= b/libc/iconv/iconv.c:131 #13 0x000000000046376d in conv_iconv_strdup (inbuf=3D0x80bd570c0 "[...]", s= rc_code=3D0x7fffffff5d60 "ISO-8859-2", dest_code=3D0x6f03d0 "UTF-8") at cod= econv.c:895 #14 0x0000000000463f2f in conv_codeset_strdup (inbuf=3D0x80bd570c0 "[...]",= src_code=3D0x7fffffff5d60 "ISO-8859-2", dest_code=3D0x0) at codeconv.c:774 #15 0x00000000005f63f0 in unmime_header (encoded_str=3D0x7fffffff7e94 "[...= ]", addr_field=3D1) at unmime.c:144 #16 0x0000000000464a56 in conv_unmime_header (str=3D0x7fffffff7e94 "[...]",= default_encoding=3D0x0, addr_field=3D1) at codeconv.c:1516 #17 0x000000000059588a in parse_stream (data=3D0x8094319a0, isstring=3D0, f= lags=3D{perm_flags =3D 3, tmp_flags =3D 0}, full=3D0, decrypted=3D0) at pro= cheader.c:558 #18 0x0000000000595234 in procheader_parse_stream (fp=3D0x8094319a0, flags= =3D{perm_flags =3D 3, tmp_flags =3D 0}, full=3D0, decrypted=3D0) at prochea= der.c:461 #19 0x0000000000595195 in procheader_parse_file (file=3D0x80d4202b0 "/home/= fk/.claws-mail/tempfolder/processing/18", flags=3D{perm_flags =3D 3, tmp_fl= ags =3D 0}, full=3D0, decrypted=3D0) at procheader.c:354 [...] This patch: http://www.fabiankeil.de/sourcecode/freebsd/iconv-Let-_citrus_mapper_close-= unlock-cm_lock-before-calli.diff seems to prevent the deadlock, but I'm not 100% sure that it's correct and I'm also a bit surprised by the lack of reports from other claws-mail users. Did anyone else run into this or can comment on the patch or the backtraces? Fabian --Sig_/nZJzfi+tvHOJV7AttwJY8NG Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iEYEARECAAYFAlJVhaYACgkQBYqIVf93VJ365gCfb+1VxEzL8gdNIfpbLwU9/Ijn o3UAoMApW2eZEkbJserHIH66TBoTPIbe =w4KR -----END PGP SIGNATURE----- --Sig_/nZJzfi+tvHOJV7AttwJY8NG-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:55:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A7C727DA; Wed, 9 Oct 2013 16:55:10 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 68A6A2538; Wed, 9 Oct 2013 16:55:10 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id r99Gt9DB022343 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 11:55:09 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Wed, 9 Oct 2013 11:55:08 -0500 From: "Teske, Devin" To: Nathan Whitehorn Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxRBPPJPIP8ZCyUiSsjBzr2++AA== Date: Wed, 9 Oct 2013 16:55:07 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> <5254F582.1040406@freebsd.org> In-Reply-To: <5254F582.1040406@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <94E04C321C77B948977772BE9DF0D204@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-09_05:2013-10-09,2013-10-09,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:55:10 -0000 On Oct 8, 2013, at 11:19 PM, Nathan Whitehorn wrote: > On 10/09/13 01:13, Allan Jude wrote: >> On 2013-10-08 16:17, Nathan Whitehorn wrote: >>> On 10/07/13 21:59, Allan Jude wrote: >>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>> implement installing on a ZFS pool. It supports both GPT and MBR, the = 4k >>>> sector gnop trick, and optional GELI encryption. We would like to comm= it >>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>> obvious bugs before we send it off to re@ to get it committed. >>>>=20 >>>> It includes a single configuration menu that allows you to select all = of >>>> the required details, including which drives to use (gets details from >>>> camcontrol, also includes an inspection utility that presents the >>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>> ZFS RAID level to use (taking in to consideration the selected number = of >>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>=20 >>>>=20 >>>> Additional, it includes some other changes to bsdinstall: >>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to= no >>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with ju= st 1 >>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>> feature has been combined into the regular 'services to enable' dialog >>>> and enabled by default >>>>=20 >>>>=20 >>>> You can browse the patches here: >>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>=20 >>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>> available compressed (48 MB) or uncompressed (211 MB): >>>>=20 >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>=20 >>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>=20 >>>>=20 >>>> We look forward to your feedback >>>>=20 >>> Thanks for doing this! I had a few comments: >>> 1. ZFS is not bootable on all architectures. Could you adjust that menu >>> item to only display for i386, amd64, and (I think?) sparc64. Use uname >>> -m, not -p, for this. >> I had not considered that, I'll make that change >>=20 >>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>> instead of GPT. >> I'll disable sparc64 as well >>=20 >>> 2. Why are you using camcontrol? That is guaranteed not to work on >>> non-CAM systems. You should use the GEOM ident string if you need an ID. >> The GEOM ident string doesn't do enough to help the user identify which >> drive is which. >> More data is not exposed anywhere that I could find >>=20 >> What we really need, is dev.ada.0.desc% like we have for network >> interfaces and a slew of other devices. GEOM data is great, but it is >> not exposed in a shell friendly way any place that I could find, other >> than the sysctl with DOT and XML data. >=20 > This is one of the reasons the partition editor is written in C. There > are a few other odd corner-cases where C is much more powerful than the > command-line for the GEOM operations that partedit needs to do. I'm not > sure how to usefully get it just from the shell. You can see how to do > it in C in the boot_disk() routine of partedit/auto_part.c. >=20 >>> 3. Any plans to integrate this into the regular partition editor? ZFS >>> support is important enough that I will definitely not get in the way, >>> even as a bolt-on, but it would be a shame for it to stay that way. The >>> editor is also designed for ZFS to be added. >> I am a sysadmin, not a programmer. I can't write C. Most people >> deploying servers can't write C. I agree with Devin Teske, if everything >> was in shell it would be a lot more usable for non-developers, who >> probably make up the majority of people who deploy FreeBSD. >=20 > There are some cases the other way too. Devin is probably the most > shell-proficient FreeBSD committer. Well, there's jilles ;D (he writes/maintains the sh(1) implementation itsel= f). > I certainly can't write shell > scripts at that level, which means that for me bsdconfig, for example, > is effectively read-only (and quite hard to read as well). In the past few days of working on the bsdinstall_zfs patch-set with Allan Jude, I learned something new actually. It seems that sh(1) doesn't suffer so much from this "read only" concept. Imagine you're starting a new C project on an operating system that has all new syscalls and all new APIs that you've never seen. Would be pretty hard, no doubt. Now imagine that you're thrown a life-line called POSIX and hey, now you're slinging code in MinGW on Windows when you don't know a lick of M$ syscalls or APIs. In a similar manner, I've witnessed functionality be added that is truly functional *without* using any of the API calls. Then I come in and do a round of optimizations to leverage the existing API. Shell is kinda like that... I'm noticing Allan Jude doesn't know all the API calls yet (who could? other than me of course -- and even I have trouble remembering them _all_) yet this doesn't phase him (or others) from jumping in and lending a hand. No different than C, but the read-only aspect is lessened significantly I believe because there are so many people out there that know enough good shell syntax and are just a stone's throw away from *great* shell syntax (which I must admit jilles helped me cross that boundary). I think in C, the read-only aspect is greater because its harder to parcel-= out the functions for a unit-test; harder to inject new code; and harder to get to a functioning end-state. > I suspect the > same is true for many other developers. Without any prejudice about the > relative merits of the languages, this can cause some significant > internal maintenance issues. Something similar happened to sysinstall > (which was in C): due to its complexity and high amounts of magic, it > had become read-only for basically all committers and as a result fell > years and years behind the rest of the project. Hopefully this is > paranoia, but I can easily see complex shell scripts engendering the > same problem. >=20 I surely hope this doesn't happen to bsdconfig, and I hope the fact that the shell API is completely optional is a huge help. However, I've implemented the following to help demystify the API and make it accessible in a human format (backward compatible with sysinstall(8)'s install.cfg file -- except from within a shell script). http://svnweb.freebsd.org/base/releng/9.2/usr.sbin/bsdconfig/share/script.s= ubr?revision=3D253912&view=3Dmarkup But I didn't stop there... I understand the importance of visual aids. So I made the "dot" module for bsdconfig(8) which has the power to produce an SVG mapping all of the includes, where they get used, how to get to certain modules, and more. I'll save you the reading of "bsdconfig dot -h" (it's long) and inste= ad just give you a pretty picture to look at. Here's how *I* personally keep tabs on the API: http://druidbsd.sourceforge.net/download/bsdconfig/bsdconfig-HEAD-20130506-= 3c.svg NOTE: It helps that I periodically use the instructions documented in "bsdconfig dot -h" to produce a Human-sized poster so I can "get up-close and personal with the API." (both literally and figuratively) But of course, it doesn't stop there... That graphic is generated dynamically. So as people other than me join forces (dear God... please send help!!) the graph will grow without any additional work. So I've tried my darndest to do everything in my power to make the API not read-only... make the API optional (so you can skip it and just start coding like a mad-man if you know shell really well)... And last but not least... You actually don't have to use shell *at all* (that's how optional this stu= ff is). Any module can be C if it wants (you'll just likely end up duplicating a lot of code -- that's why I think the answer should be... write it in shell so = you can leverage an API that can keep your code short and succinct... and if you ne= ed C, write a general purpose tool as a call-out utility). > In any case, this particular comment was just related to the benefits of > having one tool, and one UI, rather than duplicating partitioning logic > in multiple places. I wholly agree with minimizing code duplication. I've been taking to figuri= ng out which parts truly have to be (or can offer above-and-beyond value-add) in C -- and then writing abstract general-purpose utilities to solve those = issues. (and as a bonus, if need-be, creating a library for C-level access). > None of this is actually complicated, so the > duplication isn't that bad, but doing everything in one place long-term > is almost certainly better for the user, no matter what programming > language that tool is written in. (smiles) --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 16:55:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id ACC2F8EC for ; Wed, 9 Oct 2013 16:55:38 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id 958962546 for ; Wed, 9 Oct 2013 16:55:38 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 67BB12AA597; Wed, 9 Oct 2013 10:55:31 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id 57D2A1CC17; Wed, 9 Oct 2013 11:55:03 -0500 (EST) Date: Wed, 9 Oct 2013 11:55:03 -0500 From: Diane Bruce To: Kurt Lidl Subject: Re: [Heads Up] RCS removed from base Message-ID: <20131009165503.GA59319@night.db.net> References: <20131008232251.GA47296@night.db.net> <52557060.3040304@pix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52557060.3040304@pix.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 16:55:38 -0000 ... > > I notice in diff'ing your work vs my work, that I started with > newer revisions of some of the files than the ones you have: I was well aware of that. There is no point doing much more until there is a decision from core. - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 17:05:11 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7D0C2E76; Wed, 9 Oct 2013 17:05:11 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5A6A625D2; Wed, 9 Oct 2013 17:05:11 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r99H54E0027103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Oct 2013 10:05:05 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r99H54eE027102; Wed, 9 Oct 2013 10:05:04 -0700 (PDT) (envelope-from jmg) Date: Wed, 9 Oct 2013 10:05:04 -0700 From: John-Mark Gurney To: Brooks Davis Subject: Re: Unable to installworld after successful buildworld and buildkernel Message-ID: <20131009170504.GQ56872@funkthat.com> Mail-Followup-To: Brooks Davis , Thomas Mueller , freebsd-current@freebsd.org References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> <28.45.16944.64B74525@cdptpa-oedge02> <20131008214809.GC69269@lor.one-eyed-alien.net> <44.C1.16944.5E6C4525@cdptpa-oedge02> <20131009055213.GM56872@funkthat.com> <20131009130630.GB71891@lor.one-eyed-alien.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131009130630.GB71891@lor.one-eyed-alien.net> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Wed, 09 Oct 2013 10:05:05 -0700 (PDT) Cc: Thomas Mueller , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 17:05:11 -0000 Brooks Davis wrote this message on Wed, Oct 09, 2013 at 08:06 -0500: > On Tue, Oct 08, 2013 at 10:52:13PM -0700, John-Mark Gurney wrote: > > Thomas Mueller wrote this message on Wed, Oct 09, 2013 at 03:00 +0000: > > > > > But where is DB_FROM_SRC documented? I never saw it anywhere. UPDATING file needs to be updated for installing FreeBSD on a partition where there is no OS installed. > > > > > > > It's documented in Makefile.inc1 where the less commonly used options > > > > are documented. It should be documented in the Handbook along with the > > > > process of cross installation and image creation. > > > > > > > I disagree that UPDATING should document the process of installing to > > > > other locations. That would be a distraction from it's purpose of > > > > letting users update their systems. It's already far too complicated. > > > > > > -- Brooks > > > > > > UPDATING file has a section on cross-installing current into a separate partition. > > > > > > This part ought to be complete, including DB_FROM_SRC, rather than leaving a user lost at sea when a new user (unbound) sneaks in. > > > > > > UPDATING documented when user auditdistd was added, so why not for unbound? > > > > How does this look: > > Index: UPDATING > > =================================================================== > > --- UPDATING (revision 256024) > > +++ UPDATING (working copy) > > @@ -1899,7 +1899,7 @@ > > make buildkernel KERNCONF=YOUR_KERNEL_HERE > > > > > > - make installworld DESTDIR=${CURRENT_ROOT} > > + make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC > > make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd > > make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} > > cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd > > > > > > I tested distribution and it appears not to need it. > > Distribution could easily need it in the future so I'd suggest adding in > there as well. If nothing else, if building on a box with a highly > non-standard /etc/passwd or /etc/group the results could be bizzare and > inconsistant if -DDB_FROM_SRC is not used in both cases. installkernel > is probably safe since people who renumber root/wheel will get what they > deserve if they don't audit all of the make infrastructure. > > -- Brooks > > P.S. This probably shouldn't be documented because it is dangerous in > some situations: but for administrators who keep their passwd and group > files entirely in sync with FreeBSD's you can skip the whole mergemaster > -p annoyance by specifying DESTDIR=/ -DDB_FROM_SRC. My patch? The reason it should be documented as the original poster pointed out that this is specifically for cross-installing from -stable... So either we document this, or we remove this set of instructions entierly.. Second, this is for a completely new, self consistent system, so the new system will have the proper users (just got installed by make distribution).. If you mount that system on another system, you have the same problem if you mount a normally installed -current on an older -stable... I can only see improvements by documenting -DDB_FROM_SRC here.. P.S. I have done this cross-install myself, but iirc, from -current so the instructions are useful... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 17:05:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 468D6FF9 for ; Wed, 9 Oct 2013 17:05:22 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0F82E25DB for ; Wed, 9 Oct 2013 17:05:21 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r99H5HXO001468 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 12:05:18 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Wed, 9 Oct 2013 12:05:16 -0500 From: "Teske, Devin" To: Kris Moore Subject: BE Loader Menu (was Re: rcs) Thread-Topic: BE Loader Menu (was Re: rcs) Thread-Index: AQHOxRG5GlF59UAvJ06VyRjwWpYzrQ== Date: Wed, 9 Oct 2013 17:05:15 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> <52558779.2070203@pcbsd.org> In-Reply-To: <52558779.2070203@pcbsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="utf-8" Content-ID: <517D65A3D61F684FAE2B2EC2D2DA06C3@fisglobal.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-09_05:2013-10-09,2013-10-09,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 17:05:22 -0000 DQpPbiBPY3QgOSwgMjAxMywgYXQgOTo0MiBBTSwgS3JpcyBNb29yZSB3cm90ZToNCg0KPiBPbiAx MC8wOS8yMDEzIDEyOjMzLCBBbGxhbiBKdWRlIHdyb3RlOg0KPj4gT24gMjAxMy0xMC0wOSAxMjoy MywgRnJlZGRpZSBDYXNoIHdyb3RlOg0KPj4+IE9uIFdlZCwgT2N0IDksIDIwMTMgYXQgOToxMiBB TSwgRnJlZGRpZSBDYXNoIDxmandjYXNoQGdtYWlsLmNvbT4gd3JvdGU6DQo+Pj4gDQo+Pj4+IE9u IFdlZCwgT2N0IDksIDIwMTMgYXQgNjo0MSBBTSwgSnVsaWFuIEVsaXNjaGVyIDxqdWxpYW5AZnJl ZWJzZC5vcmc+d3JvdGU6DQo+Pj4+IA0KPj4+Pj4gT24gMTAvOS8xMyAyOjM1IEFNLCBGcmVkZGll IENhc2ggd3JvdGU6DQo+Pj4+PiANCj4+Pj4+PiBPbiBUdWUsIE9jdCA4LCAyMDEzIGF0IDk6MDkg QU0sIEFsZnJlZCBQZXJsc3RlaW4gPGJyaWdodEBtdS5vcmc+IHdyb3RlOg0KPj4+Pj4+IA0KPj4+ Pj4+IFlvdSdyZSByaWdodCBvbiB0aGUgbW9uZXksIHRvIGJlIGhvbmVzdCB0aGlzIGlzIG9uZSBv ZiB0aGUgcmVhc29ucyB3aHkNCj4+Pj4+Pj4gSSd2ZSBzd2l0Y2hlZCB0byB1c2luZyBPU1ggYXMg bXkgZGVza3RvcCBPUy4NCj4+Pj4+Pj4gDQo+Pj4+Pj4+IHpzaCwgdmltLCBzY3JlZW4gYnkgZGVm YXVsdC4gIGFuZCB1cGdyYWRlcyB3b3JrLiAgQXQgdGhlIGVuZCBvZiB0aGUgZGF5DQo+Pj4+Pj4+ IEknbSBzcGVuZGluZyB0aW1lIGRvaW5nIHdvcmssIG5vdCBtdWNraW5nIGFib3V0IG15IHdvcmtz cGFjZSB0byBtYWtlIGl0DQo+Pj4+Pj4+IHVzYWJsZSBmb3IgZGV2ZWxvcG1lbnQuDQo+Pj4+Pj4+ IA0KPj4+Pj4+PiBJIHRoaW5rIHRoaXMgd2FzIGJyb3VnaHQgdXAgYXQgQlNEQ2FuIGluIHRoZSBk aXNjdXNzaW9uIGFib3V0IG1ha2luZw0KPj4+Pj4+PiBGcmVlQlNEIGEgbW9yZSBmZWF0dXJlZCBk ZXZlbG9wbWVudCBwbGF0Zm9ybS4NCj4+Pj4+Pj4gDQo+Pj4+Pj4+IFNwZWFraW5nIG9mLi4uIGhh cyBhbnlvbmUgdHJpZWQgUENCU0Q/DQo+Pj4+Pj4+IA0KPj4+Pj4+IFBDLUJTRCBpc24ndCBtdWNo IGRpZmZlcmVudCBmcm9tIEZyZWVCU0QuICBUaGUgaW5zdGFsbGVyIGlzIEdVSSBhbmQNCj4+Pj4+ PiBzdXBwb3J0DQo+Pj4+Pj4gWkZTLCB0aGVyZSBhcmUgc29tZSBHVUkgc2V0dXAgdG9vbHMgb24g Zmlyc3QgYm9vdCBmb3IgWCwgdGhlcmUgYXJlIHNvbWUNCj4+Pj4+PiBHVUkNCj4+Pj4+PiB0b29s cyB0byBzZWxlY3QgYmluYXJ5IGRyaXZlcnMgZm9yIFgsIGFuZCB0aGVyZSDigIvigIthcmUgd29y a2luZyBwa2duZyByZXBvcw0KPj4+Pj4+IGF2YWlsYWJsZS4NCj4+Pj4+PiANCj4+Pj4+PiBJIGhh ZCBhIGxvdCBvZiBpc3N1ZXMgd2l0aCBQQy1CU0QgOS4wIGFuZCA5LjEgYXMgSSB3YXMgdHJ5aW5n IHRvIGRvDQo+Pj4+Pj4gdGhpbmdzDQo+Pj4+Pj4gInRoZSBGcmVlQlNEIHdheSIgd2hpY2ggYnJv a2UgYSBsb3Qgb2YgdGhpbmdzIHRoYXQgd2VyZSBkb25lICJ0aGUgUEMtQlNEDQo+Pj4+Pj4gd2F5 IiAoYWthIGRvbid0IG1hbnVhbGx5IGVkaXQgY29uZmlnIGZpbGVzIHVzZWQgZm9yIGJvb3Rpbmcp Lg0KPj4+Pj4+IA0KPj4+Pj4+IOKAi1N3aXRjaGluZyB0byB0aGUgInJvbGxpbmctcmVsZWFzZSIg KGFrYSBQQy1CU0QgOS1TVEFCTEUpIGFuZCBtb3ZpbmcgYWxsDQo+Pj4+Pj4gbXkNCj4+Pj4+PiBj b25maWcgZmlsZSBlZGl0cyBpbnRvIDxmaWxlbmFtZT4uY29uZi5sb2NhbCBmaXhlZCBteSBpc3N1 ZXMuICBUaGluZ3MNCj4+Pj4+PiBoYXZlDQo+Pj4+Pj4gYmVlbiBydW5uaW5nIHNtb290aCwgYW5k IEkgZmluYWxseSB1bmRlcnN0YW5kIHRoZSBiZWF1dHkgYW5kIHNpbXBsaWNpdHkNCj4+Pj4+PiBv Zg0KPj4+Pj4+IGZyZWVic2QtdXBkYXRlICsgcGtnLiAgT1MgZ2V0cyB1cGRhdGVkIG9uY2UgcGVy IG1vbnRoLCBwYWNrYWdlcyBnZXQNCj4+Pj4+PiB1cGRhdGVkDQo+Pj4+Pj4gdHdpY2UgcGVyIG1v bnRoLCBubyBtb3JlIGNvbXBpbGluZyB0aGluZ3MgZnJvbSBzb3VyY2UuICBJdCdzIGxpa2UgdXNp bmcNCj4+Pj4+PiBVYnVudHUvRGViaWFuIGJ1dCB3aXRoIHRoZSBwb3dlciBhbmQgZmVhdHVyZXMg b2YgRnJlZUJTRC4gIDopDQo+Pj4+Pj4g4oCLDQo+Pj4+Pj4gDQo+Pj4+PiBXaGVuIHRoZXkgd2Vu dCB0byBhIFpGUy1vbmx5IHN5c3RlbSwgdXNpbmcgR1JVQiwgd2l0aCBubyBhbHRlcm5hdGl2ZSwN Cj4+Pj4+IHRoZW4gSSdtIGFmcmFpZCB0aGV5IGxvc3QgbWUuDQo+Pj4+PiBJIHdhbnQgYSByb290 IGZpbGVzeXN0ZW0gb24gVUZTIGZvciByZWxpYWJhaWx0eSBhbmQgc2ltcGxlbmVzcy4gIEkgY2Fu DQo+Pj4+PiBkZWJ1ZyBpdCdzIG1lZGlhIGlmIG5lZWRlZC4NCj4+Pj4+IEJlZm9yZSB0aGVuIEkg cmVhbGx5IGxpa2VkIGl0ICh0aG91Z2ggdGhlciBlaXMgbm90IGVub3VnaCBpbmZvcm1hdGlvbiBv bg0KPj4+Pj4gaG93IGl0IHdvcmtzIGludGVybmVhbGx5IGlmIHlvdSB3YW50IHRvIHVzZSBpdC4N Cj4+Pj4+IGhvcGVmdWxseSB0aGF0IHdpbGwgY29tZS4uIGFuZCBJIExJS0UgUEJJcyAgRnJlZUJT RCBzaG91bGQgYWRvcHQgUEJJcyBmb3INCj4+Pj4+IHN1cmUuDQo+Pj4+PiBXaXRoIFBCSXMgeW91 IGNvdWxkIG1ha2UgZXZlbiBxdWl0ZSBiYXNlIGl0ZW1zIHNlcGFyYXRlbHkgaW5zdGFsbGFibGUu DQo+Pj4+PiB2ZXJzaW9uaW5nIHByb2JsZW1zIGdvIGF3YXkuDQo+Pj4+PiANCj4+Pj4gVGhlcmUn cyBubyBHUlVCIGluIGEgZGVmYXVsdCBpbnN0YWxsIG9mIFBDLUJTRCA5LjAsIDkuMSwgb3IgOS4y LiAgRXZlbiBvbg0KPj4+PiBhIFpGUy1vbmx5IHNldHVwICh3aGljaCBpcyB3aGF0IEkgcnVuKS4g IEl0J3MgdXNpbmcgdGhlIEZyZWVCU0QgbG9hZGVyLA0KPj4+PiB3aXRoIGN1c3RvbSBhcnR3b3Jr IGFuZCBtZW51cy4NCj4+Pj4gDQo+Pj4g4oCLSHJtLCBpdCBzZWVtcyB0aGV5J3ZlIGNoYW5nZWQg dGhpbmdzIHdpdGggdGhlIDkuMiBpbnN0YWxsZXIuICBJdCBkb2VzIHVzZQ0KPj4+IEdSVUIyIChl d3d3dyEpIGZvciB0aGUgYm9vdCBsb2FkZXIsIGFuZCBpbnRlZ3JhdGVzIHN1cHBvcnQgZm9yIFpG UyBib290DQo+Pj4gZW52aXJvbm1lbnRzICh2aWEgYmVhZG0pIGludG8gaXQuICA6KCAgU2hhbWUg dGhleSBkaWRuJ3QgdXNlIHRoZSBCRSBzdXBwb3J0DQo+Pj4gaW4gdGhlIEZyZWVCU0QgbG9hZGVy IGZvciB0aGlzLiAgV29uZGVyIGlmIG15IDktU1RBQkxFLWJhc2VkIFBDLUJTRCBpbnN0YWxsDQo+ Pj4gd2lsbCBnZXQgInVwZ3JhZGVkIiB0byBHUlVCPw0KPj4+IA0KPj4gVGhlIHJlYXNvbiB0aGV5 IHdlbnQgdG8gZ3J1YjIsIGlzIHRoYXQgdGhlIHdheSB0aGUgZnJlZWJzZCBsb2FkZXIgbWVudXMN Cj4+IHdvcmssIGl0IGxvYWRzIHRoZSBrZXJuZWwgYmVmb3JlIGl0IGRyYXdzIHRoZSBtZW51LiBU aGlzIG1lYW5zIGlmIHRoZXJlDQo+PiBpcyBhIHByb2JsZW0gd2l0aCB5b3VyIGtlcm5lbCAocHJv YmFibHkgdGhlIG1vc3QgdmFsdWFibGUgdGltZSB0byBoYXZlDQo+PiBib290IGVudmlyb25tZW50 cykgdGhlbiB0aGUgbWVudSBuZXZlciBjb21lcyB1cCwgYW5kIHlvdSBjYW5ub3Qgc2VsZWN0DQo+ PiB3aGljaCBCRSB0byBib290IGZyb20uIEdydWIgZG9lc24ndCByZWx5IG9uIGEgRnJlZUJTRCBr ZXJuZWwgdW50aWwgYWZ0ZXINCj4+IHlvdSBzZWxlY3Qgd2hpY2ggQkUgdG8gYm9vdCBmcm9tLg0K Pj4gDQo+PiBLcmlzIGFuZCBJIGRpc2N1c3NlZCBpdCBhdCBsZW5ndGggd2l0aCBEZXZpbiBUZXNr ZSwgYW5kIHdoaWxlIGhlIGhhcw0KPj4gZGVtb25zdHJhdGVkIGJlaW5nIGFibGUgdG8gcG9wdWxh dGUgYSBsb3dlciBtZW51IHdpdGggdGhlIFpGUyBkYXRhc2V0cywNCj4+IEkgYW0gbm90IHN1cmUg aWYgdGhlIG90aGVyIGlzc3VlIGNhbiBiZSByZXNvbHZlZC4NCj4+IA0KPiANCg0KSSdtIGxhdGUg dG8gdGhlIHBhcnR5IGFnYWluIDtEIChkaWRuJ3QgcmVhbGl6ZSB0aGUgcmNzIHRocmVhZCBoYWQg dHVybmVkIEJFKQ0KDQpCb3RoIHByb2JsZW1zIGNhbiBiZSBzb2x2ZWQuDQpUaGUgbG9hZGluZyBv ZiB0aGUga2VybmVsICphZnRlciogY2hvb3NpbmcgeW91ciBib290IGRldmljZSBpcyB0cml2aWFs Lg0KV2UndmUgYmVlbiBkb2luZyBpdCBhdCAkd29yayBmb3IgKnllYXJzKiAoYWxtb3N0IGEgZGVj YWRlPykNCg0KSSBjYW4gcHV0IHRoYXQgaW4sIHdoZW5ldmVyLiBQcm9iYWJseSBhdCB0aGUgc2Ft ZSB0aW1lIGFzIGltcGxlbWVudGluZw0KdGhlIGxpdmUvZHluYW1pYyBCRSBtZW51cyBmb3Igc2Vs ZWN0aW5nIHRoZSByb290IGRldmljZS4NCg0KDQoNCj4gWWVhLCBHUlVCIGlzIG5vdCBteSBmaXJz dCBjaG9pY2UsIGJ1dCBBVE0gdGhpcyBpcyB0aGUgImNsZWFuZXN0IiB3YXkgd2UNCj4gY2FuIGRv IFpGUyBCRSdzLiBIb3dldmVyIGlmIHlvdSBkb24ndCBsaWtlIFpGUyAvIEdSVUIsIHlvdSBjYW4g YWx3YXlzDQo+IHVzZSByZWd1bGFyIEZyZWVCU0QgYW5kIGp1c3QgZ3JhYiBvdXIgdG9vbGNoYWlu IGZyb20NCj4gc3lzdXRpbHMvcGNic2QtdXRpbHMqIGluIHBvcnRzIG9yIHVzZSBvdXIgUEtHTkcg cmVwbzoNCj4gDQo+IGh0dHA6Ly93aWtpLnBjYnNkLm9yZy9pbmRleC5waHAvVHVybl9GcmVlQlNE X2ludG9fUEMtQlNEJUMyJUFFDQo+IA0KPiBJJ20gcGxhbm5pbmcgb24gdXNpbmcgR1JVQiB0byBk byBVRUZJIGJvb3RpbmcgZm9yIDEwLjAgYXMgd2VsbC4gQnV0IHdoZW4NCj4gdGhlIEZyZWVCU0Qg bG9hZGVyIG1hdHVyZXMgdG8gdGhlIHBvaW50IG9mIGhhdmluZyBzdXBwb3J0IGZvciBhbGwgdGhl c2UNCj4gZmVhdHVyZXMsIEknbGwgZ2xhZGx5IG1vdmUgdXMgYmFjay4NCj4gDQoNCkkgaGFkIG5v dCBiZWVuIHB1c2hpbmcgaGFyZCBvbiBmaW5pc2hpbmcgdGhlIEJFIEZvcnRoIGJlY2F1c2UgSSBr bmV3IHRoYXQNCml0IHdvdWxkIGJlIGEgZ3JlYXRlciB2YWx1ZSBhZGQgaWYgd2UgYWN0dWFsbHkg aGFkICJCb290IGZyb20gWkZTIiBmaW5pc2hlZA0KZmlyc3QuIFdvdWxkIGJlIGVhc2llciB0byB0 ZXN0LCB0aGF0IGlzLCBpZiBJIGFjdHVhbGx5IGhhZCBhIHN5c3RlbSBib290aW5nIGZyb20NClpG UyAtLSB3aGljaCBpcyB3aGF0IEFsbGFuLCBqbWcsIGFuZCBteXNlbGYgYXJlIGhvcGVmdWxseSB3 b3JraW5nIHRvd2FyZA0KZm9yIEZyZWVCU0QgMTAuMC1SLiAoc21pbGVzKQ0KLS0gDQpEZXZpbgoK X19fX19fX19fX19fXwpUaGUgaW5mb3JtYXRpb24gY29udGFpbmVkIGluIHRoaXMgbWVzc2FnZSBp cyBwcm9wcmlldGFyeSBhbmQvb3IgY29uZmlkZW50aWFsLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50 ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2U6IChpKSBkZWxldGUgdGhlIG1lc3NhZ2UgYW5kIGFsbCBj b3BpZXM7IChpaSkgZG8gbm90IGRpc2Nsb3NlLCBkaXN0cmlidXRlIG9yIHVzZSB0aGUgbWVzc2Fn ZSBpbiBhbnkgbWFubmVyOyBhbmQgKGlpaSkgbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHku IEluIGFkZGl0aW9uLCBwbGVhc2UgYmUgYXdhcmUgdGhhdCBhbnkgbWVzc2FnZSBhZGRyZXNzZWQg dG8gb3VyIGRvbWFpbiBpcyBzdWJqZWN0IHRvIGFyY2hpdmluZyBhbmQgcmV2aWV3IGJ5IHBlcnNv bnMgb3RoZXIgdGhhbiB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LiBUaGFuayB5b3UuCg== From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 17:22:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F0ABC965 for ; Wed, 9 Oct 2013 17:22:06 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BC18B270F for ; Wed, 9 Oct 2013 17:22:06 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id r99HM02v023082 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 12:22:00 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Wed, 9 Oct 2013 12:21:59 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxRQPPJPIP8ZCyUiSsjBzr2++AA== Date: Wed, 9 Oct 2013 17:21:58 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4B3F2@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> In-Reply-To: <5254D231.5070803@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-09_07:2013-10-09,2013-10-09,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 17:22:07 -0000 On Oct 8, 2013, at 8:49 PM, Allan Jude wrote: > On 2013-10-07 15:59, Allan Jude wrote: >> Devin Teske and I have been working on a big patch to bsdinstall to >> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >> sector gnop trick, and optional GELI encryption. We would like to commit >> this in time for 10.0-BETA1 so it needs some testing to work out any >> obvious bugs before we send it off to re@ to get it committed. >>=20 >> It includes a single configuration menu that allows you to select all of >> the required details, including which drives to use (gets details from >> camcontrol, also includes an inspection utility that presents the >> detailed output of camcontrol inquiry/identify, and gpart show), what >> ZFS RAID level to use (taking in to consideration the selected number of >> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>=20 >>=20 >> Additional, it includes some other changes to bsdinstall: >> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >> 2. Replace the 3 separate dialogs to configure an ipv4 address with just= 1 >> 3. Remove the dialog asking if you wish to enable crash dumps, this >> feature has been combined into the regular 'services to enable' dialog >> and enabled by default >>=20 >>=20 >> You can browse the patches here: >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>=20 >> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >> available compressed (48 MB) or uncompressed (211 MB): >>=20 >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>=20 >> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>=20 >>=20 >> We look forward to your feedback >>=20 >=20 > We've made more improvements, including corporating most all of the > feedback we've gotten so far >=20 >=20 > Outstanding items: > 1. Apply the changes to ipv6 config the way we did ipv4 > 2. improve disk identification (model info and serial # instead of one > or the other) > 3. Include a helpful message before the GELI step where you have to > enter your password many times, the user will be less confused if it is > explained why they have to enter their password 3 * number of disks times I'm hopeful that we can script the application of a password that we first prompt for. What tool is prompting for a password? Can we not just provide an answer on stdin? (e.g., echo "$pass" | tool_that_needs_pass) > 4. Validate vdev type choice inside the vdev type menu, and warn the > user if they have made an invalid selection, so they can add more disks > or chance their selection, without having to try to start the > installation first This will be done with fanciness ;D (read: ... --and-widget --infobox ... a= nd sundry smartness; retaining as much as possible the ability to do things out of order but never arise at a point of astonishment). > 5. Whatever else you guys find wrong tonight >=20 > I generated new test images, and attached the patch (which got REALLY > big when Devin Teske decided to fix "all of the things": >=20 And then I merged "all of the things" into HEAD, so the patch-set shrunk back to its normal size. Now we have global exit codes which will make merging of code that is based off of Thomas Dickey's samples easier. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 17:46:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 23C8D5CC for ; Wed, 9 Oct 2013 17:46:54 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id F2EBC28E8 for ; Wed, 9 Oct 2013 17:46:53 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 8AA651E2EE; Wed, 9 Oct 2013 17:46:52 +0000 (UTC) Message-ID: <525596A7.2090701@allanjude.com> Date: Wed, 09 Oct 2013 13:47:19 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "Teske, Devin" Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4B3F2@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC4B3F2@LTCFISWMSGMB21.FNFIS.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 17:46:54 -0000 On 2013-10-09 13:21, Teske, Devin wrote: > On Oct 8, 2013, at 8:49 PM, Allan Jude wrote: > >> On 2013-10-07 15:59, Allan Jude wrote: >>> Devin Teske and I have been working on a big patch to bsdinstall to >>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>> sector gnop trick, and optional GELI encryption. We would like to commit >>> this in time for 10.0-BETA1 so it needs some testing to work out any >>> obvious bugs before we send it off to re@ to get it committed. >>> >>> It includes a single configuration menu that allows you to select all of >>> the required details, including which drives to use (gets details from >>> camcontrol, also includes an inspection utility that presents the >>> detailed output of camcontrol inquiry/identify, and gpart show), what >>> ZFS RAID level to use (taking in to consideration the selected number of >>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>> >>> >>> Additional, it includes some other changes to bsdinstall: >>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>> feature has been combined into the regular 'services to enable' dialog >>> and enabled by default >>> >>> >>> You can browse the patches here: >>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>> >>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>> available compressed (48 MB) or uncompressed (211 MB): >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>> >>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>> >>> >>> We look forward to your feedback >>> >> We've made more improvements, including corporating most all of the >> feedback we've gotten so far >> >> >> Outstanding items: >> 1. Apply the changes to ipv6 config the way we did ipv4 >> 2. improve disk identification (model info and serial # instead of one >> or the other) >> 3. Include a helpful message before the GELI step where you have to >> enter your password many times, the user will be less confused if it is >> explained why they have to enter their password 3 * number of disks times > I'm hopeful that we can script the application of a password that we > first prompt for. > > What tool is prompting for a password? Can we not just provide an answer > on stdin? (e.g., echo "$pass" | tool_that_needs_pass) > It is 'geli create' and 'geli attach'. I am not sure if we want to have the password show up in the process list (obviously in the installer this is less of an issue, but) > >> 4. Validate vdev type choice inside the vdev type menu, and warn the >> user if they have made an invalid selection, so they can add more disks >> or chance their selection, without having to try to start the >> installation first > This will be done with fanciness ;D (read: ... --and-widget --infobox ... and > sundry smartness; retaining as much as possible the ability to do things > out of order but never arise at a point of astonishment). > I don't think we need --and-widget, just in the function where we apply the results of the menu selection, we can add a regular --msgbox telling them that their config won't work, and they need to either select more drives or a different vdev type >> 5. Whatever else you guys find wrong tonight >> >> I generated new test images, and attached the patch (which got REALLY >> big when Devin Teske decided to fix "all of the things": >> > And then I merged "all of the things" into HEAD, so the patch-set shrunk > back to its normal size. Now we have global exit codes which will make > merging of code that is based off of Thomas Dickey's samples easier. I am glad to see all of the good ideas, and plans to make everything wonderful, but my biggest concern is getting this over to re@ so it can get in to 10.0-BETA1, the deadline for which is looming (like, tomorrow I think). As such, I have rolled back the patches to netconfig and netconfig_ipv4 (my stuff to reduce the number of dialogs to configure ipv4, it posed some problems with the possible usage of xdialog, and didn't actually offer an option to 'cancel'). I kept Warren's netconfig wireless patch This leaves the only real outstanding problem the keymap thing. I propose changing it from a yes/no/other to a --menu, and hopefully we can find the bug with the display name, or just make it show the keymap name instead. -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 18:14:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 462B012B for ; Wed, 9 Oct 2013 18:14:54 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 074182AE5 for ; Wed, 9 Oct 2013 18:14:53 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id r99IEnIn002437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 13:14:49 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.02.0309.002; Wed, 9 Oct 2013 13:14:48 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxRQPPJPIP8ZCyUiSsjBzr2++AA== Date: Wed, 9 Oct 2013 18:14:48 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4B907@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4B3F2@LTCFISWMSGMB21.FNFIS.com> <525596A7.2090701@allanjude.com> In-Reply-To: <525596A7.2090701@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-09_07:2013-10-09,2013-10-09,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 18:14:54 -0000 On Oct 9, 2013, at 10:47 AM, Allan Jude wrote: > On 2013-10-09 13:21, Teske, Devin wrote: >> On Oct 8, 2013, at 8:49 PM, Allan Jude wrote: >>=20 >>> On 2013-10-07 15:59, Allan Jude wrote: >>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>> implement installing on a ZFS pool. It supports both GPT and MBR, the = 4k >>>> sector gnop trick, and optional GELI encryption. We would like to comm= it >>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>> obvious bugs before we send it off to re@ to get it committed. >>>>=20 >>>> It includes a single configuration menu that allows you to select all = of >>>> the required details, including which drives to use (gets details from >>>> camcontrol, also includes an inspection utility that presents the >>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>> ZFS RAID level to use (taking in to consideration the selected number = of >>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>=20 >>>>=20 >>>> Additional, it includes some other changes to bsdinstall: >>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to= no >>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with ju= st 1 >>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>> feature has been combined into the regular 'services to enable' dialog >>>> and enabled by default >>>>=20 >>>>=20 >>>> You can browse the patches here: >>>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://druidbsd.cvs.sf.ne= t/viewvc/druidbsd/bsdinstall_zfs/&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r= =3DLTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DoPEdrpFUFqEutq%2= B7DHGyBIA0gTt5%2BZ6FWvbN6q4bjm4%3D%0A&s=3D32f69a33d9c98c63ecf3962b89eea0af6= 31f5a2fd6e82b55afb6ec139f3f803d >>>>=20 >>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>> available compressed (48 MB) or uncompressed (211 MB): >>>>=20 >>>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://www.allanjude.com/= bsd/zfsbootonly_2013-10-06.iso.xz&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r= =3DLTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DoPEdrpFUFqEutq%2= B7DHGyBIA0gTt5%2BZ6FWvbN6q4bjm4%3D%0A&s=3Dfd0f3ed623f12c8cb5eee607cf8212252= 3a0800ab9f5624cb3f77ae2646e1b1b >>>>=20 >>>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://www.allanjude.com/= bsd/zfsbootonly_2013-10-06.iso&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=3D= LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DoPEdrpFUFqEutq%2B7D= HGyBIA0gTt5%2BZ6FWvbN6q4bjm4%3D%0A&s=3Dfa49aaa528513a591ac40a2f0c5666abae2d= 7269bd66ac70d7100475a9574300 >>>>=20 >>>>=20 >>>> We look forward to your feedback >>>>=20 >>> We've made more improvements, including corporating most all of the >>> feedback we've gotten so far >>>=20 >>>=20 >>> Outstanding items: >>> 1. Apply the changes to ipv6 config the way we did ipv4 >>> 2. improve disk identification (model info and serial # instead of one >>> or the other) >>> 3. Include a helpful message before the GELI step where you have to >>> enter your password many times, the user will be less confused if it is >>> explained why they have to enter their password 3 * number of disks tim= es >> I'm hopeful that we can script the application of a password that we >> first prompt for. >>=20 >> What tool is prompting for a password? Can we not just provide an answer >> on stdin? (e.g., echo "$pass" | tool_that_needs_pass) >>=20 > It is 'geli create' and 'geli attach'. I am not sure if we want to have > the password show up in the process list (obviously in the installer > this is less of an issue, but) >=20 It won't. echo is a shell built-in. If we're uber paranoid... we prefix the word "builtin"; e.g.,... builtin echo "$pass" | tool_that_needs_pass You'll see the tool in ps, but you won't see the echo (that's part of the shell invocation -- all you see in ps is an instance of sh). >>=20 >>> 4. Validate vdev type choice inside the vdev type menu, and warn the >>> user if they have made an invalid selection, so they can add more disks >>> or chance their selection, without having to try to start the >>> installation first >> This will be done with fanciness ;D (read: ... --and-widget --infobox ..= . and >> sundry smartness; retaining as much as possible the ability to do things >> out of order but never arise at a point of astonishment). >>=20 >=20 > I don't think we need --and-widget, just in the function where we apply > the results of the menu selection, The purpose of --and-widget with an --infobox is to let the user know that validation is occurring each/every time they make a selection. Seeing the infobox before being returned to the previous menu (in the case of selecting a valid vdev_type) is to cement in the mind of the user that t= heir selection was validated. Of course, in the case of an invalid selection, th= ey get a message box. What the message box says depends on: 1. Are they trying to select a vdev_type for which they don't have enough devices? Tell them that they don't have enough devices, and bring them back to the vdev_type menu (to select a different [valid] vdev type *or* cancel and go back to the ZFS menu where they can optionally Rescan for more devices -- allowing that vdev_type to be selected without issue). In the prompt that tells them that they don't have enough disks in their system to select that vdev_type, we sould hint that they can choose cancel and go back to use the "Rescan" option to scan for more devices. 2. Are they trying to select a vdev_type for which they have enough devices but have not yet made enough selections? Drop them back to the ZFS menu so they can go select the appropriate number of devices. Good? > we can add a regular --msgbox telling > them that their config won't work, and they need to either select more > drives or a different vdev type >=20 I agree on the msgbox -- and I still think the temporaneous infobox injected via --and-widget would be value-add. Question is what to do after the msgbox. I posit that if the vdev_type is valid but they don't have enough disks currently selected, that they be tossed back at the ZFS menu. However, if they instead select a vdev_type which couldn't possible be satisfied given the number of devices available to the hardware... keep them in the vdev_type menu.=20 >>> 5. Whatever else you guys find wrong tonight >>>=20 >>> I generated new test images, and attached the patch (which got REALLY >>> big when Devin Teske decided to fix "all of the things": >>>=20 >> And then I merged "all of the things" into HEAD, so the patch-set shrunk >> back to its normal size. Now we have global exit codes which will make >> merging of code that is based off of Thomas Dickey's samples easier. >=20 > I am glad to see all of the good ideas, and plans to make everything > wonderful, but my biggest concern is getting this over to re@ so it can > get in to 10.0-BETA1, the deadline for which is looming (like, tomorrow > I think). >=20 I hate to say it... but it was the netconfig and keymap changes that put us out of our way. If anything, I'd like to see those get dropped and have us focus on ZFS. > As such, I have rolled back the patches to netconfig and netconfig_ipv4 > (my stuff to reduce the number of dialogs to configure ipv4, it posed > some problems with the possible usage of xdialog, and didn't actually > offer an option to 'cancel'). I kept Warren's netconfig wireless patch >=20 Cool. We're thinking along the same lines. > This leaves the only real outstanding problem the keymap thing. I > propose changing it from a yes/no/other to a --menu, and hopefully we > can find the bug with the display name, or just make it show the keymap > name instead. >=20 Last night I started doing what I knew "had to be done". Just as was the case with "bsdconfig timezone" ... I literally went into tzsetup(8) and converted the C code line-by-line to shell. (don't take that *too* literally... swaths of optimization were applied int he process; point being that the shell quite-ably reads the ISO3166 tables and zone files in the same *exact* manner as tzetup). I've gone into kbdmap and looked at how it parses things. No biggie... looks like INDEX.keymaps (whose suffix matches the directory he lives in) is nothing more than a colon-delimited 3-field syntax with lea= ding whitespace chopped and a comment-character of "#". Nothing a trival awk(1) script couldn't handle. To make things cute... I've got the code parsing into a shell structs (the = same way I parse dhclient.leases and other file formats). By having an awk script read the file and generate shell statements that in-turn load the data into= the exigent namespace. I'll see what I can get in ASAP. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 18:28:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4D70F560 for ; Wed, 9 Oct 2013 18:28:29 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0B4FA2B8A for ; Wed, 9 Oct 2013 18:28:28 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 128BFE6DC4 for ; Wed, 9 Oct 2013 19:28:19 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=+8B27GjJhkm2 CmnWIWXoy9+a42Q=; b=tOFGD1WIY7KLLc9TgoYvpX0dqkpquBgf3oUTUwZFLdA/ 4lzrx7UmvJSZ7uMyvb4AUCvq/wZzbyQmUi1eiJO8BF2qhKEdZD+6b0GJOTkSk/1M 0wlHHc4SIO/QjRmEQwKMjIxciUyjwkH1hxMZScwc+q0sFNn4JbMsjuPjGMVAh+E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=PU1loG DAtpb6Mm6r8aalSdJMoHLa7MBiYJH2M0y7KHnvsYJuySc0spALrMmKzrc04pRxGa jzC8mXI5+Vx00OEQBNdyRQIOn0GHIOiIt5JdrQry5ShbQ90AOgEeN2QINjsAa6ao WG76lJ36+bxAktTapSHkyu5X2v3DImUA4qEYc= Received: from [192.168.2.103] (unknown [93.89.81.205]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id E82EBE6DC3 for ; Wed, 9 Oct 2013 19:28:18 +0100 (BST) Message-ID: <5255A041.2080501@cran.org.uk> Date: Wed, 09 Oct 2013 19:28:17 +0100 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 CC: freebsd-current@freebsd.org Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> <52556567.3090309@mu.org> In-Reply-To: <52556567.3090309@mu.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 18:28:29 -0000 On 10/9/2013 3:17 PM, Alfred Perlstein wrote: > Only a few years ago you could take a dvd or memstick of FreeBSD and > have 1000s of packages to choose from during your install. That is > broken now? At some point it was decided that the installer should be as simple as possible and package installation was a post-install task, for once the system was up and running. I think that might be changing with bsdinstall getting pkgng support, but it did seem like a fairly major regression at the time. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 18:52:34 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C91A743C; Wed, 9 Oct 2013 18:52:34 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0D6CC2D08; Wed, 9 Oct 2013 18:52:33 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.7/8.14.7) with ESMTP id r99IqONF083735; Wed, 9 Oct 2013 13:52:24 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.7/8.14.7/Submit) id r99IqOXP083734; Wed, 9 Oct 2013 13:52:24 -0500 (CDT) (envelope-from brooks) Date: Wed, 9 Oct 2013 13:52:24 -0500 From: Brooks Davis To: Brooks Davis , Thomas Mueller , freebsd-current@freebsd.org Subject: Re: Unable to installworld after successful buildworld and buildkernel Message-ID: <20131009185224.GA81032@lor.one-eyed-alien.net> References: <3F.9A.16944.166A3525@cdptpa-oedge02> <20131008141501.GA69028@lor.one-eyed-alien.net> <28.45.16944.64B74525@cdptpa-oedge02> <20131008214809.GC69269@lor.one-eyed-alien.net> <44.C1.16944.5E6C4525@cdptpa-oedge02> <20131009055213.GM56872@funkthat.com> <20131009130630.GB71891@lor.one-eyed-alien.net> <20131009170504.GQ56872@funkthat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline In-Reply-To: <20131009170504.GQ56872@funkthat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 18:52:34 -0000 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 09, 2013 at 10:05:04AM -0700, John-Mark Gurney wrote: > Brooks Davis wrote this message on Wed, Oct 09, 2013 at 08:06 -0500: > > On Tue, Oct 08, 2013 at 10:52:13PM -0700, John-Mark Gurney wrote: > > > Thomas Mueller wrote this message on Wed, Oct 09, 2013 at 03:00 +0000: > > > > > > But where is DB_FROM_SRC documented? I never saw it anywhere. = UPDATING file needs to be updated for installing FreeBSD on a partition wh= ere there is no OS installed. > > > >=20 > > > > > It's documented in Makefile.inc1 where the less commonly used opt= ions > > > > > are documented. It should be documented in the Handbook along wi= th the > > > > > process of cross installation and image creation. > > > >=20 > > > > > I disagree that UPDATING should document the process of installin= g to > > > > > other locations. That would be a distraction from it's purpose of > > > > > letting users update their systems. It's already far too complic= ated. > > > >=20 > > > > -- Brooks > > > >=20 > > > > UPDATING file has a section on cross-installing current into a sepa= rate partition. > > > >=20 > > > > This part ought to be complete, including DB_FROM_SRC, rather than = leaving a user lost at sea when a new user (unbound) sneaks in. > > > >=20 > > > > UPDATING documented when user auditdistd was added, so why not for = unbound? > > >=20 > > > How does this look: > > > Index: UPDATING > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > --- UPDATING (revision 256024) > > > +++ UPDATING (working copy) > > > @@ -1899,7 +1899,7 @@ > > > make buildkernel KERNCONF=3DYOUR_KERNEL_HERE > > > > > > > > > - make installworld DESTDIR=3D${CURRENT_ROOT} > > > + make installworld DESTDIR=3D${CURRENT_ROOT} -DDB_FROM_SRC > > > make distribution DESTDIR=3D${CURRENT_ROOT} # if newfs'd > > > make installkernel KERNCONF=3DYOUR_KERNEL_HERE DESTDIR=3D${CU= RRENT_ROOT} > > > cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # = if newfs'd > > >=20 > > >=20 > > > I tested distribution and it appears not to need it. > >=20 > > Distribution could easily need it in the future so I'd suggest adding in > > there as well. If nothing else, if building on a box with a highly > > non-standard /etc/passwd or /etc/group the results could be bizzare and > > inconsistant if -DDB_FROM_SRC is not used in both cases. installkernel > > is probably safe since people who renumber root/wheel will get what they > > deserve if they don't audit all of the make infrastructure. > >=20 > > -- Brooks > >=20 > > P.S. This probably shouldn't be documented because it is dangerous in > > some situations: but for administrators who keep their passwd and group > > files entirely in sync with FreeBSD's you can skip the whole mergemaster > > -p annoyance by specifying DESTDIR=3D/ -DDB_FROM_SRC. >=20 > My patch? I like your patch other than the fact that you didn't include make distribution. The specific case mentioned in my P.S. should not be well documented as it's potentially dangerous (one somewhat common case leads to suid binaries with the wrong owner). -- Brooks --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFSVaXnXY6L6fI4GtQRAtBcAJ9KxL20/lAe9cX48eUtjXbqsiysGwCfQRv3 ksmEChaJLO7BMU0+EIERusI= =zXcb -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 20:31:14 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AE841211; Wed, 9 Oct 2013 20:31:14 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4D96E239A; Wed, 9 Oct 2013 20:31:14 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBE90F.dip0.t-ipconnect.de [93.203.233.15]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r99KVBjg022544; Wed, 9 Oct 2013 20:31:11 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r99KUxjH076732; Wed, 9 Oct 2013 22:30:59 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r99KUkEP093523; Wed, 9 Oct 2013 22:30:52 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310092030.r99KUkEP093523@fire.js.berklix.net> To: Adrian Chadd , "Kevin Lo" Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 08 Oct 2013 11:53:34 PDT." Date: Wed, 09 Oct 2013 22:30:46 +0200 Sender: jhs@berklix.com Cc: Damien Bergamini , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 20:31:14 -0000 Hi all, Adrian Chadd wrote: > Note the noise floor differences.. wonder why that is. Yes, more measurements etc at: http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/share/man/man4/urtwn.4.REL=current.diff > Rui ported the uwrtn stuff, right? It seems others, so I added them: To: kevlo@freebsd.org cc: damien@openbsd.org to ask if they have newer versions code or firmware to test ? http://svnweb.freebsd.org/base/head/sys/dev/usb/wlan/if_urtwn.c?view=log ] Import Kevin Lo's port of urtwn(4) from OpenBSD. urtwn(4) is a driver for the ] Realtek RTL8188CU/RTL8192CU USB IEEE 802.11b/g/n wireless cards. ] This driver requires microcode which is available in FreeBSD ports: ] net/urtwn-firmware-kmod. ] Hiren ported the urtwn(4) man page from OpenBSD and Glen just commited a port ] for the firmware. ] Tested by: kevlo, hiren, gjb > He may be able to help. The driver is > recent and its likely there are bugs to shake out. http://svnweb.freebsd.org/base/head/share/man/man4/urtwn.4?view=markup The urtwn driver first appeared in OpenBSD 4.9 and FreeBSD 10.0. The urtwn driver was written by Damien Bergamini . Also Re. Thomas Mueller's > I just happened to be browsing man urtwn in NetBSD-current > (6.99.23), and Edimax EW-7811Un is listed as supported by this driver. I See on FreeBSD, OpenBSD, NetBSD: /pub/FreeBSD/branches/-current/src/sys/ dev/usb/wlan/if_urtwn.c dev/usb/wlan/if_urtwnreg.h contrib/dev/urtwn/urtwn-rtl8192cfwT.fw.uu contrib/dev/urtwn/urtwn-rtl8192cfwU.fw.uu http://svnweb.freebsd.org/base/head/sys/dev/usb/wlan/if_urtwn.c?view=markup $OpenBSD: if_urtwn.c,v 1.16 2011/02/10 17:26:40 jakemsr Exp $ http://svnweb.freebsd.org/base/head/sys/dev/usb/wlan/if_urtwnreg.h?view=markup http://svnweb.freebsd.org/base/head/sys/contrib/dev/urtwn/urtwn-rtl8192cfwT.fw.uu?view=markup http://svnweb.freebsd.org/base/head/sys/contrib/dev/urtwn/urtwn-rtl8192cfwU.fw.uu?view=markup http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_urtwn.c http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_urtwn.c?rev=1.32;content-type=text%2Fplain;only_with_tag=MAIN $OpenBSD: if_urtwn.c,v 1.32 2013/09/30 05:18:57 jsg Exp $ http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/if_urtwnreg.h http://www.openbsd.org/cgi-bin/man.cgi?query=urtwn&sektion=4&format=html Can't find firmware BLOB[s] on openbsd.org site http://netbsd.gw.com/cgi-bin/man-cgi?urtwn++NetBSD-current /libdata/firmware/if_urtwn/rtl8192cfw.bin /libdata/firmware/if_urtwn/rtl8192cfwU.bin http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/usb/if_urtwn.c?only_with_tag=MAIN /* $NetBSD: if_urtwn.c,v 1.25 2013/08/10 21:15:26 jnemeth Exp $ */ /* $OpenBSD: if_urtwn.c,v 1.20 2011/11/26 06:39:33 ckuethe Exp $ */ Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 21:16:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9683365A; Wed, 9 Oct 2013 21:16:02 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 24923268B; Wed, 9 Oct 2013 21:15:58 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBE90F.dip0.t-ipconnect.de [93.203.233.15]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r99LFuPF024480; Wed, 9 Oct 2013 21:15:56 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r99LFiVf077510; Wed, 9 Oct 2013 23:15:44 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r99LFWOD094589; Wed, 9 Oct 2013 23:15:38 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310092115.r99LFWOD094589@fire.js.berklix.net> To: Adrian Chadd , "Kevin Lo" , freebsd-current , Damien Bergamini , "Rui Paulo" Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 09 Oct 2013 22:30:46 +0200." Date: Wed, 09 Oct 2013 23:15:32 +0200 Sender: jhs@berklix.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 21:16:02 -0000 > > Rui ported the uwrtn stuff, right? > > It seems others, so I added them: Whoops, I missed "Rui" = "paulo" in commit logs. Added to cc. Sorry. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 21:33:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 60DCFB24; Wed, 9 Oct 2013 21:33:08 +0000 (UTC) (envelope-from zbodek@gmail.com) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9737527C4; Wed, 9 Oct 2013 21:33:07 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id l18so1472513wgh.4 for ; Wed, 09 Oct 2013 14:33:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5gx+w6vLlfeF2eTNwp/7o4G4j3c1PDBJNfpvuuBY7Pg=; b=fD7qF8AQEaYesTEjXBqz61waitJHz5omNrRW08+8+guw0ytEUy9dTWD1JuMlAmTaCz LSA4rl9HiFWSECElNh3W3Xg5asKU1aPqcUIXXTCAmIkliE7AKf+JR/+FV5a2S/+gp5Aa sNYnNKEkpSyY65SrfZsk67vUr5irjP2a7ZkbbMDgJfz9crzPV+p/zFVR09yfD6eJ1ikh EoUGsreK/5MWqkLQBm6Suw/hB5COqMxqo0T3HBjYq4o/SjHNF6j0ePZx9bm82e0FNFtA cF6RgQ5/sa6gRkqVErwJ1g3CtgfNnVmboJpV6/sr1dqa+31eRei5bdICuAwoPsFVm/Oz cTdg== MIME-Version: 1.0 X-Received: by 10.180.83.228 with SMTP id t4mr4619854wiy.12.1381354386070; Wed, 09 Oct 2013 14:33:06 -0700 (PDT) Sender: zbodek@gmail.com Received: by 10.216.160.70 with HTTP; Wed, 9 Oct 2013 14:33:05 -0700 (PDT) In-Reply-To: References: Date: Wed, 9 Oct 2013 23:33:06 +0200 X-Google-Sender-Auth: 3Wv6EEbVnFYOlE8lEdO1cXD-qdI Message-ID: Subject: Re: Changes to UART ns8250 From: Zbigniew Bodek To: Ganbold Tsagaankhuu Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" , freebsd-current , "freebsd-embedded@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 21:33:08 -0000 Hello Ganbold. Thank you for testing the patch and pointing those issue out. My detection log from Armada XP: uart0: <16550 or compatible> mem 0xd0012000-0xd001201f irq 41 on simplebus0 uart0: console (115200,n,8,1) uart1: <16550 or compatible> mem 0xd0012100-0xd001211f irq 42 on simplebus0 uart2: <16550 or compatible> mem 0xd0012200-0xd001221f irq 43 on simplebus0 uart3: <16550 or compatible> mem 0xd0012300-0xd001231f irq 44 on simplebus0 Is there a possibility to download a datasheet for RK30xx so that I could verify what is required for it's UART? The patch is causing that we only wait until UART is not busy anymore. I can't find why would that cause problems if your UART requires busy detection anyway. Best regards Zbigniew Bodek 2013/10/9 Ganbold Tsagaankhuu > > > > On Tue, Oct 8, 2013 at 9:58 AM, Ganbold Tsagaankhuu wrote: > >> Zbigniew, >> >> >> On Tue, Oct 8, 2013 at 3:54 AM, Zbigniew Bodek wrote: >> >>> Hello. >>> >>> I would like to present a patch for ns8250 serial that I would like to >>> commit in the near future (if there are no objections). >>> >>> The patch is fixing newest DesignWare UART with busy detection. >>> During frequency divisors configuration when UART is busy transferring or >>> receiving data, line control register manipulation will not take effect. >>> Therefore, we will not set divisor latch access bit and we will corrupt >>> LCR >>> instead of configuring divisors. >>> It is necessary to wait until UART finishes all transfers to proceed with >>> the configuration. >>> >>> This was detected on Armada XP as UART fails on this issue 100/100 >>> attempts. >>> The patch was tested by kevlo@ and me and it works on our Armada XP - >>> based >>> systems. >>> >>> Please send your comment or remarks if there are any. >>> >> >> I'm trying your patch on r254983. >> Tried on 2 boards (Cubieboard2 (Allwinner A20 SoC - dual Cortex A7) and >> Radxa Rock (Rockchip RK3188 - Quad Cortex A9)). Both seem to have some sort >> of DesignWare uart. >> >> 1. It works fine on Cubieboard2. Uart dmesg is like: >> >> uart0: <16750 or compatible> mem 0x1c28000-0x1c283ff irq 33 on simplebus0 >> >> uart0: console (115200,n,8,1) >> >> 2. No any printing on screen in case of Radxa Rock. Without your patch >> uart dmesg is like: >> >> uart0: <16650 or compatible> mem 0x20064000-0x200643ff irq 68 on >> simplebus0 >> uart0: console (115200,n,8,1) >> >> In case of RK3188 SoC, it seems booting FreeBSD kernel seems very >> fragile, not sure yet what is causing the problem. >> Even with stock ns8250 some version later than r254983 didn't show/print >> anything on serial console few days ago. >> Only thing so far I know is this r254983 (with some patch) works in my >> case on RK3188 SoC based board. >> > > > Zbigniew, > > Just tried again your patch on RK30xx board. I was able to see boot > messages on screen. > This uart detected as: > ... > uart0: <16650 or compatible> mem 0x20064000-0x200643ff irq 68 on > simplebus0 > uart0: console (115200,n,8,1) > > uart0: fast interrupt > ... > Can you show me your uart detection log? > It seems this DW uart of RK30xx is different than DW uart of A10/A20. > Boot simply stops printing "start_init: trying /sbin/init". > > thanks, > > Ganbold > > > >> >> thanks, >> >> Ganbold >> >> >> >> >>> >>> Best regards >>> Zbigniew Bodek >>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to " >>> freebsd-current-unsubscribe@freebsd.org" >>> >> >> > From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 21:48:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B5D0433F for ; Wed, 9 Oct 2013 21:48:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 73B6328DC for ; Wed, 9 Oct 2013 21:48:07 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id ii20so5418320qab.0 for ; Wed, 09 Oct 2013 14:48:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=bHMUl3wnbYDg3yI+IF5IuHeBYjYYB4DO6aWIFweSOg8=; b=FXcsVw2eskPJS4mbJ6veP2MquIlJluGaUVtL4ReDh31yxdBMeH6nwQqUoTbxCd3cWm r9LhrbTOt7upLG0EWU858QKAEU52K8oTAu3OMbrqPkFoedxwLpaey8hQBwlOjb/RHjIH UPnF19RjWomFN0NqAlIscNrz+4l2ATkmLocl5QV5n99ZI+DAz2Z77QTLipXD7v0YcE7p rUtdo1hbk0Z3N5x1Q/med8OZKiu4DTGeZ41kBtT8hfz8DwIwN5WqodZ83EA60uM01DAu xxtZzvneEVwlywAfwMe24g9zDs2hyJKNXiBbteb2DLgVzCZ5Ecs6IEdikKcofYLRfYU3 BD8w== MIME-Version: 1.0 X-Received: by 10.229.118.10 with SMTP id t10mr13133397qcq.5.1381355286543; Wed, 09 Oct 2013 14:48:06 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.207.66 with HTTP; Wed, 9 Oct 2013 14:48:06 -0700 (PDT) In-Reply-To: <5255A041.2080501@cran.org.uk> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> <52556567.3090309@mu.org> <5255A041.2080501@cran.org.uk> Date: Wed, 9 Oct 2013 14:48:06 -0700 X-Google-Sender-Auth: Hp9uFwxdoWBFWzmx-LxFP1j1z8g Message-ID: Subject: Re: rcs From: Adrian Chadd To: Bruce Cran Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 21:48:07 -0000 On 9 October 2013 11:28, Bruce Cran wrote: > On 10/9/2013 3:17 PM, Alfred Perlstein wrote: > >> Only a few years ago you could take a dvd or memstick of FreeBSD and have >> 1000s of packages to choose from during your install. That is broken now? >> > > At some point it was decided that the installer should be as simple as > possible and package installation was a post-install task, for once the > system was up and running. I think that might be changing with bsdinstall > getting pkgng support, but it did seem like a fairly major regression at > the time. I think it was more a "this is a stepping stone to a bigger change.." .. and that didn't happen soon after. The other thing here is the introduction of the uhm, "livefs". It's big and it took up the space once occupied by the first set of packages. Honestly, I'm kinda surprised how big base is these days, but I have other fights to fight right now. -adrian From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 21:54:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B48C5656 for ; Wed, 9 Oct 2013 21:54:12 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4FEBA293B for ; Wed, 9 Oct 2013 21:54:12 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id q58so1599802wes.0 for ; Wed, 09 Oct 2013 14:54:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=UQQPj/JTIxsXz2wZqyaaeCqnys4aIkh9+T/luSw69SE=; b=N7wkqnW2FAYZY1azKmTUYTyMGDXjjrdbTQqnqVRjyypp5SyXso0Qf83tnEGhxSb+Iz XiT7Aqn0jV8YMw2wURGENIs33s8sek2Xa5bKDO1749J5i3A1RV/oRWp+FHfzgpqaoG56 H4NzzC0JJsY/TxxH0hlHYMWVB9BzigEZ8q8E5tcmRJuBjmazjuPTuqcWEvNRkCnYk66y MOjdNdDXx0flAGxArB8HGc2y+3ISOmZ9nzm7Mk/FIt5YuEy83diLJacPrf4yv+nOBHXr rcDs2o/RGad4uQEayE9D6KIUkQQeR3dLril7Zs7FZu2zG7KTevtgMZgp/novqejgWxyg shcA== X-Received: by 10.180.98.105 with SMTP id eh9mr4648628wib.56.1381355650801; Wed, 09 Oct 2013 14:54:10 -0700 (PDT) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk. [87.194.105.247]) by mx.google.com with ESMTPSA id dl10sm19497190wib.1.1969.12.31.16.00.00 (version=SSLv3 cipher=RC4-SHA bits=128/128); Wed, 09 Oct 2013 14:54:10 -0700 (PDT) Date: Wed, 9 Oct 2013 22:54:07 +0100 From: RW To: freebsd-current@freebsd.org Subject: Re: claws-mail deadlocking in iconv Message-ID: <20131009225407.594e5787@gumby.homeunix.com> In-Reply-To: <73d40037.635a97ef@fabiankeil.de> References: <73d40037.635a97ef@fabiankeil.de> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 21:54:12 -0000 On Wed, 9 Oct 2013 18:34:46 +0200 Fabian Keil wrote: > After the iconv import claws-mail started to deadlock in iconv every > now and then on my system, which prevented claws-mail from rendering > windows or reacting to input. > ... > and I'm also a bit surprised by the lack of reports from > other claws-mail users. > > Did anyone else run into this or can comment on the patch or > the backtraces? I can't comment on the rest, but I have recently been seening lock-ups in claws-mail on current. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 22:06:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1C987CE5; Wed, 9 Oct 2013 22:06:03 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D8E3B2A23; Wed, 9 Oct 2013 22:06:02 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id r99M5vKA030832 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 17:05:57 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Wed, 9 Oct 2013 17:05:56 -0500 From: "Teske, Devin" To: Adrian Chadd Subject: Re: rcs Thread-Topic: rcs Thread-Index: AQHOxTu5g7djsM+KPU+NRhFKoPIwlA== Date: Wed, 9 Oct 2013 22:05:55 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4C854@LTCFISWMSGMB21.FNFIS.com> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> <52556567.3090309@mu.org> <5255A041.2080501@cran.org.uk> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <19373F0848F83744859187F3648A5AE7@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-09_07:2013-10-09,2013-10-09,1970-01-01 signatures=0 Cc: Bruce Cran , freebsd-current , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 22:06:03 -0000 On Oct 9, 2013, at 2:48 PM, Adrian Chadd wrote: > On 9 October 2013 11:28, Bruce Cran wrote: >=20 >> On 10/9/2013 3:17 PM, Alfred Perlstein wrote: >>=20 >>> Only a few years ago you could take a dvd or memstick of FreeBSD and ha= ve >>> 1000s of packages to choose from during your install. That is broken n= ow? >>>=20 >>=20 >> At some point it was decided that the installer should be as simple as >> possible and package installation was a post-install task, for once the >> system was up and running. I think that might be changing with bsdinstall >> getting pkgng support, but it did seem like a fairly major regression at >> the time. >=20 That wasn't the rationale. sysinstall was broken and more people wanted a replacement than wanted to see it fixed. bsdinstall is simply coming of age still (sysinstall had a 15 year run). >=20 > I think it was more a "this is a stepping stone to a bigger change.." .. > and that didn't happen soon after. >=20 Adrian is right. It was a "first step" (nobody intended to see functionality get dropped -- it's a matter of finding the time to replace a 15-year code line -- sysinstall). Only a very small handful of us are actively working on it. It's further al= ong than you think. You can always help out by testing. > The other thing here is the introduction of the uhm, "livefs". It's big a= nd > it took up the space once occupied by the first set of packages. Honestly, > I'm kinda surprised how big base is these days, but I have other fights to > fight right now. >=20 The livefs is a bee in my bonnet too. But as you say... more pressing things to worry about right now than break something that is working currently. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Wed Oct 9 23:06:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C505AC73; Wed, 9 Oct 2013 23:06:18 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 526B92D36; Wed, 9 Oct 2013 23:06:18 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBE90F.dip0.t-ipconnect.de [93.203.233.15]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r99N6FI6027931; Wed, 9 Oct 2013 23:06:15 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r99N62nI079258; Thu, 10 Oct 2013 01:06:03 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r99N5oS4097678; Thu, 10 Oct 2013 01:05:56 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310092305.r99N5oS4097678@fire.js.berklix.net> To: "Kevin Lo" , "Rui Paulo" , "Damien Bergamini" Subject: Re: urtwn driver for Edimax EW-7811U WLAN nano USB Adapter From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 09 Oct 2013 23:15:32 +0200." <201310092115.r99LFWOD094589@fire.js.berklix.net> Date: Thu, 10 Oct 2013 01:05:50 +0200 Sender: jhs@berklix.com Cc: Adrian Chadd , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Oct 2013 23:06:18 -0000 Ref. http://lists.freebsd.org/pipermail/freebsd-current/2013-October/045333.html I jhs@ wrote > > > Rui ported the uwrtn stuff, right? > > It seems others, so I added them: > Whoops, I missed "Rui" = "paulo" in commit logs. Added to cc. Sorry. This has header with corrected addresses for "Rui Paulo" (my typo. before) "Damien Bergamini" (after bounced on reason: 550 5.1.1 .. & I pinged @free.fr & got no bounce ) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 00:15:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F3FC9442 for ; Thu, 10 Oct 2013 00:15:07 +0000 (UTC) (envelope-from rmtodd@servalan.servalan.com) Received: from ln.servalan.com (unknown [IPv6:2600:3c00::f03c:91ff:fe96:62f5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CAF5B209D for ; Thu, 10 Oct 2013 00:15:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=servalan.com; s=rsadkim; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:From:References:Cc:Subject:To; bh=gHtlCHI5iSWZ5al48Caz1+OxT+6Vg5BYBa/U4O2N8dI=; b=krU9L/cCMqa9PGUN2GOovKd07fUKjQj3MENlKWDJELkmOwl4wXCi3/m9+jb0ys/iVBiqvPSEakBG90LWjkDxsTzvdCFPOvliEr5TcZ4fP6kEZeMuTF4JkaRqv4PKS/pkA+t0AbfCFM6N9ogePxVNk7rl36UVmeGL4H1OdbT2INM=; Received: from uucp by ln.servalan.com with local-rmail (Exim 4.71) (envelope-from ) id 1VU3uE-0003Rn-QL for freebsd-current@freebsd.org; Wed, 09 Oct 2013 19:15:06 -0500 Received: from rmtodd by servalan.servalan.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VU3sr-000HTn-91; Wed, 09 Oct 2013 19:13:41 -0500 To: Vitalij Satanivskij Subject: Re: Assertion in zdb? References: <20131009132258.GA85485@hell.ukr.net> From: Richard Todd Date: Wed, 09 Oct 2013 19:13:40 -0500 In-Reply-To: <20131009132258.GA85485@hell.ukr.net> (Vitalij Satanivskij's message of "Wed, 9 Oct 2013 16:22:58 +0300") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.5-b28 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 00:15:08 -0000 Vitalij Satanivskij writes: > Hello. > > System - 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r255173 > > While trying to get some statistics from zdb > > zdb -dd disk1 > stat.log > > get some assertion: > > Assertion failed: object_count == usedobjs (0x85727 == 0x3aa93d), file /usr/src/cddl/usr.sbin/zdb/../../../cddl/contrib/opensolaris/cmd/zdb/zdb.c, line 1767. > zsh: abort (core dumped) zdb -dd disk1 > stat.log > > Maybe somebody have any idea about what's it's can be and how big problem it's (or not a problem at all)? Probably not a problem unless it happens reliably when you try it multiple times. Since zdb looks at the raw disks, if the filesystem/zpool is active, zdb can easily read bits of the zpool metadata off the disks at different times and thus see an inconsistent state. Hence trying to get stats out of zdb always carries a certain risk of not working. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 01:00:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 18C916E0 for ; Thu, 10 Oct 2013 01:00:13 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D68EE22BF for ; Thu, 10 Oct 2013 01:00:12 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n5so920087oag.41 for ; Wed, 09 Oct 2013 18:00:12 -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=9J3SaNVKLT3ZVCmmSz1ADQRJZUpqQY3qFQu4r0d51NE=; b=nB+Pov16jqMbnlhHMQfdmWrvT+slFJtC1U3v+225ZWoApXxP2vzFRc9yn4UAkz7Rqq XrZf6eJId7gKFROqLWY6OSXNRzqwm0Clna3TV2Ic6SWnpbtX0+xcDhbgV6ab5n5+g6jI Nh8jDSVO7kKdXp7fKwONjzbH80lcgTCttgnbaxU3WS1H29a10Vg4LdyhEzfIOJMbZpH1 7dThjpMRr8AKEN7RLquam3fKKUC5OlIQccJ4/37iuZqpTG9GFmPju2SsyrVWn4UZQTXm /+BNeJo6mjAQfy0eEcDI0OOyfj7/oEHuNm3LxMasfMZey0nUlqTivjk83tFyGTPHQuu/ c/3A== MIME-Version: 1.0 X-Received: by 10.60.60.5 with SMTP id d5mr8211580oer.0.1381366812039; Wed, 09 Oct 2013 18:00:12 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Wed, 9 Oct 2013 18:00:11 -0700 (PDT) Date: Wed, 9 Oct 2013 21:00:11 -0400 Message-ID: Subject: /usr/src/lib/msun errors From: Joe Nosay To: freebsd-current Content-Type: multipart/mixed; boundary=089e0149c3c022e2c604e8588624 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 01:00:13 -0000 --089e0149c3c022e2c604e8588624 Content-Type: text/plain; charset=ISO-8859-1 Src is from 10/7/13 on i386. Base is from April. --089e0149c3c022e2c604e8588624 Content-Type: text/plain; charset=US-ASCII; name="buildworld-errors.txt" Content-Disposition: attachment; filename="buildworld-errors.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hml7vajn0 Y2MgIC1PMiAtcGlwZSAtbXNzc2UzIC1XYWxsICAtSS91c3Ivc3JjL2xpYi9tc3VuL3g4NiAtSS91 c3Ivc3JjL2xpYi9tc3VuL2xkODAgLUkvdXNyL3NyYy9saWIvbXN1bi9zcmMgLUkvdXNyL3NyYy9s aWIvbXN1bi8uLi9saWJjL2luY2x1ZGUgIC1JL3Vzci9zcmMvbGliL21zdW4vLi4vbGliYy9pMzg2 IC1zdGQ9Z251OTkgLVF1bnVzZWQtYXJndW1lbnRzIC1mc3RhY2stcHJvdGVjdG9yIC1Xc3lzdGVt LWhlYWRlcnMgLVdlcnJvciAtV25vLXBvaW50ZXItc2lnbiAtV25vLWVtcHR5LWJvZHkgLVduby1z dHJpbmctcGx1cy1pbnQgLVduby10YXV0b2xvZ2ljYWwtY29tcGFyZSAtV25vLXVudXNlZC12YWx1 ZSAtV25vLXBhcmVudGhlc2VzLWVxdWFsaXR5IC1Xbm8tdW51c2VkLWZ1bmN0aW9uIC1Xbm8tY29u dmVyc2lvbiAtV25vLXN3aXRjaCAtV25vLXN3aXRjaC1lbnVtIC1Xbm8ta25yLXByb21vdGVkLXBh cmFtZXRlciAtV25vLXBhcmVudGhlc2VzIC1jIC91c3Ivc3JjL2xpYi9tc3VuL3NyYy9lX2owLmMg LW8gZV9qMC5vCi91c3Ivc3JjL2xpYi9tc3VuL3NyYy9lX2owLmM6MjgxOjEwOiBlcnJvcjogdmFy aWFibGUgJ3AnIGlzIHVzZWQgdW5pbml0aWFsaXplZCB3aGVuZXZlciAnaWYnIGNvbmRpdGlvbiBp cyBmYWxzZSBbLVdlcnJvciwtV3NvbWV0aW1lcy11bmluaXRpYWxpemVkXQogICAgICAgIGVsc2Ug aWYoaXg+PTB4NDAwMDAwMDApe3AgPSBwUjI7IHE9IHBTMjt9CiAgICAgICAgICAgICAgICBefn5+ fn5+fn5+fn5+fgovdXNyL3NyYy9saWIvbXN1bi9zcmMvZV9qMC5jOjI4Mzo2OiBub3RlOiB1bmlu aXRpYWxpemVkIHVzZSBvY2N1cnMgaGVyZQogICAgICAgIHIgPSBwWzBdK3oqKHBbMV0reioocFsy XSt6KihwWzNdK3oqKHBbNF0reipwWzVdKSkpKTsKICAgICAgICAgICAgXgovdXNyL3NyYy9saWIv bXN1bi9zcmMvZV9qMC5jOjI4MTo3OiBub3RlOiByZW1vdmUgdGhlICdpZicgaWYgaXRzIGNvbmRp dGlvbiBpcyBhbHdheXMgdHJ1ZQogICAgICAgIGVsc2UgaWYoaXg+PTB4NDAwMDAwMDApe3AgPSBw UjI7IHE9IHBTMjt9CiAgICAgICAgICAgICBefn5+fn5+fn5+fn5+fn5+fn4KL3Vzci9zcmMvbGli L21zdW4vc3JjL2VfajAuYzoyNzM6MTc6IG5vdGU6IGluaXRpYWxpemUgdGhlIHZhcmlhYmxlICdw JyB0byBzaWxlbmNlIHRoaXMgd2FybmluZwogICAgICAgIGNvbnN0IGRvdWJsZSAqcCwqcTsKICAg ICAgICAgICAgICAgICAgICAgICBeCiAgICAgICAgICAgICAgICAgICAgICAgID0gMAovdXNyL3Ny Yy9saWIvbXN1bi9zcmMvZV9qMC5jOjI4MToxMDogZXJyb3I6IHZhcmlhYmxlICdxJyBpcyB1c2Vk IHVuaW5pdGlhbGl6ZWQgd2hlbmV2ZXIgJ2lmJyBjb25kaXRpb24gaXMgZmFsc2UgWy1XZXJyb3Is LVdzb21ldGltZXMtdW5pbml0aWFsaXplZF0KICAgICAgICBlbHNlIGlmKGl4Pj0weDQwMDAwMDAw KXtwID0gcFIyOyBxPSBwUzI7fQogICAgICAgICAgICAgICAgXn5+fn5+fn5+fn5+fn4KL3Vzci9z cmMvbGliL21zdW4vc3JjL2VfajAuYzoyODQ6MTM6IG5vdGU6IHVuaW5pdGlhbGl6ZWQgdXNlIG9j Y3VycyBoZXJlCiAgICAgICAgcyA9IG9uZSt6KihxWzBdK3oqKHFbMV0reioocVsyXSt6KihxWzNd K3oqcVs0XSkpKSk7CiAgICAgICAgICAgICAgICAgICBeCi91c3Ivc3JjL2xpYi9tc3VuL3NyYy9l X2owLmM6MjgxOjc6IG5vdGU6IHJlbW92ZSB0aGUgJ2lmJyBpZiBpdHMgY29uZGl0aW9uIGlzIGFs d2F5cyB0cnVlCiAgICAgICAgZWxzZSBpZihpeD49MHg0MDAwMDAwMCl7cCA9IHBSMjsgcT0gcFMy O30KICAgICAgICAgICAgIF5+fn5+fn5+fn5+fn5+fn5+fgovdXNyL3NyYy9saWIvbXN1bi9zcmMv ZV9qMC5jOjI3MzoyMDogbm90ZTogaW5pdGlhbGl6ZSB0aGUgdmFyaWFibGUgJ3EnIHRvIHNpbGVu Y2UgdGhpcyB3YXJuaW5nCiAgICAgICAgY29uc3QgZG91YmxlICpwLCpxOwogICAgICAgICAgICAg ICAgICAgICAgICAgIF4KICAgICAgICAgICAgICAgICAgICAgICAgICAgPSAwCi91c3Ivc3JjL2xp Yi9tc3VuL3NyYy9lX2owLmM6Mzc2OjEwOiBlcnJvcjogdmFyaWFibGUgJ3AnIGlzIHVzZWQgdW5p bml0aWFsaXplZCB3aGVuZXZlciAnaWYnIGNvbmRpdGlvbiBpcyBmYWxzZSBbLVdlcnJvciwtV3Nv bWV0aW1lcy11bmluaXRpYWxpemVkXQogICAgICAgIGVsc2UgaWYoaXg+PTB4NDAwMDAwMDApe3Ag PSBxUjI7IHE9IHFTMjt9CiAgICAgICAgICAgICAgICBefn5+fn5+fn5+fn5+fgovdXNyL3NyYy9s aWIvbXN1bi9zcmMvZV9qMC5jOjM3ODo2OiBub3RlOiB1bmluaXRpYWxpemVkIHVzZSBvY2N1cnMg aGVyZQogICAgICAgIHIgPSBwWzBdK3oqKHBbMV0reioocFsyXSt6KihwWzNdK3oqKHBbNF0reipw WzVdKSkpKTsKICAgICAgICAgICAgXgovdXNyL3NyYy9saWIvbXN1bi9zcmMvZV9qMC5jOjM3Njo3 OiBub3RlOiByZW1vdmUgdGhlICdpZicgaWYgaXRzIGNvbmRpdGlvbiBpcyBhbHdheXMgdHJ1ZQog ICAgICAgIGVsc2UgaWYoaXg+PTB4NDAwMDAwMDApe3AgPSBxUjI7IHE9IHFTMjt9CiAgICAgICAg ICAgICBefn5+fn5+fn5+fn5+fn5+fn4KL3Vzci9zcmMvbGliL21zdW4vc3JjL2VfajAuYzozNjg6 MTc6IG5vdGU6IGluaXRpYWxpemUgdGhlIHZhcmlhYmxlICdwJyB0byBzaWxlbmNlIHRoaXMgd2Fy bmluZwogICAgICAgIGNvbnN0IGRvdWJsZSAqcCwqcTsKICAgICAgICAgICAgICAgICAgICAgICBe CiAgICAgICAgICAgICAgICAgICAgICAgID0gMAovdXNyL3NyYy9saWIvbXN1bi9zcmMvZV9qMC5j OjM3NjoxMDogZXJyb3I6IHZhcmlhYmxlICdxJyBpcyB1c2VkIHVuaW5pdGlhbGl6ZWQgd2hlbmV2 ZXIgJ2lmJyBjb25kaXRpb24gaXMgZmFsc2UgWy1XZXJyb3IsLVdzb21ldGltZXMtdW5pbml0aWFs aXplZF0KICAgICAgICBlbHNlIGlmKGl4Pj0weDQwMDAwMDAwKXtwID0gcVIyOyBxPSBxUzI7fQog ICAgICAgICAgICAgICAgXn5+fn5+fn5+fn5+fn4KL3Vzci9zcmMvbGliL21zdW4vc3JjL2VfajAu YzozNzk6MTM6IG5vdGU6IHVuaW5pdGlhbGl6ZWQgdXNlIG9jY3VycyBoZXJlCiAgICAgICAgcyA9 IG9uZSt6KihxWzBdK3oqKHFbMV0reioocVsyXSt6KihxWzNdK3oqKHFbNF0reipxWzVdKSkpKSk7 CiAgICAgICAgICAgICAgICAgICBeCi91c3Ivc3JjL2xpYi9tc3VuL3NyYy9lX2owLmM6Mzc2Ojc6 IG5vdGU6IHJlbW92ZSB0aGUgJ2lmJyBpZiBpdHMgY29uZGl0aW9uIGlzIGFsd2F5cyB0cnVlCiAg ICAgICAgZWxzZSBpZihpeD49MHg0MDAwMDAwMCl7cCA9IHFSMjsgcT0gcVMyO30KICAgICAgICAg ICAgIF5+fn5+fn5+fn5+fn5+fn5+fgovdXNyL3NyYy9saWIvbXN1bi9zcmMvZV9qMC5jOjM2ODoy MDogbm90ZTogaW5pdGlhbGl6ZSB0aGUgdmFyaWFibGUgJ3EnIHRvIHNpbGVuY2UgdGhpcyB3YXJu aW5nCiAgICAgICAgY29uc3QgZG91YmxlICpwLCpxOwogICAgICAgICAgICAgICAgICAgICAgICAg IF4KICAgICAgICAgICAgICAgICAgICAgICAgICAgPSAwCjQgZXJyb3JzIGdlbmVyYXRlZC4KKioq IEVycm9yIGNvZGUgMQoKU3RvcC4KbWFrZTogc3RvcHBlZCBpbiAvdXNyL3NyYy9saWIvbXN1bgo= --089e0149c3c022e2c604e8588624-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 01:33:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 89F761FC for ; Thu, 10 Oct 2013 01:33:45 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6978E2443 for ; Thu, 10 Oct 2013 01:33:45 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r9A1XcKh010529; Wed, 9 Oct 2013 18:33:38 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r9A1XcA4010528; Wed, 9 Oct 2013 18:33:38 -0700 (PDT) (envelope-from sgk) Date: Wed, 9 Oct 2013 18:33:38 -0700 From: Steve Kargl To: Joe Nosay Subject: Re: /usr/src/lib/msun errors Message-ID: <20131010013338.GA10499@troutmask.apl.washington.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 01:33:45 -0000 On Wed, Oct 09, 2013 at 09:00:11PM -0400, Joe Nosay wrote: > Src is from 10/7/13 on i386. Base is from April. > cc -O2 -pipe -mssse3 -Wall -I/usr/src/lib/msun/x86 -I/usr/src/lib/msun/ld80 -I/usr/src/lib/msun/src -I/usr/src/lib/msun/../libc/include -I/usr/src/lib/msun/../libc/i386 -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -c /usr/src/lib/msun/src/e_j0.c -o e_j0.o > /usr/src/lib/msun/src/e_j0.c:281:10: error: variable 'p' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized] Are you setting CFLAGS in make.conf? -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 02:01:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EF7E4648 for ; Thu, 10 Oct 2013 02:01:19 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id A957F254A for ; Thu, 10 Oct 2013 02:01:19 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:49555] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 3F/F9-16944-76A06525; Thu, 10 Oct 2013 02:01:12 +0000 Date: Thu, 10 Oct 2013 02:01:11 +0000 Message-ID: <3F.F9.16944.76A06525@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-current@freebsd.org References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <1893399957.20131009013424@serebryakov.spb.ru> <52556567.3090309@mu.org> <5255A041.2080501@cran.org.uk> <13CA24D6AB415D428143D44749F57D720FC4C854@LTCFISWMSGMB21.FNFIS.com> <19373F0848F83744859187F3648A5AE7@fisglobal.com> Subject: Re: rcs X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Cc: Adrian Chadd , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 02:01:20 -0000 from Devin Teske: > That wasn't the rationale. sysinstall was broken and more people wanted a > replacement than wanted to see it fixed. > bsdinstall is simply coming of age still (sysinstall had a 15 year run). Some things I disliked about sysinstall were choosing a type of install from a confusing menu (standard install, developer install, and others not clearly comprehensible). Then there was the breaking up of sets into 1392 KB chunks (base.aa, base.ab, base.ac, ...) as if it were possible to find enough good floppies to write to. Also, the holographic shell was practically impossible to use. More on topic, since so many users depend on rcs, I say leave it in base, at least until OpenRCS or Fossil can replace it. Tom From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 02:33:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 12CAD2A5 for ; Thu, 10 Oct 2013 02:33:43 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id BF82C26D1 for ; Thu, 10 Oct 2013 02:33:42 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:19083] helo=localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id A8/C9-01315-00216525; Thu, 10 Oct 2013 02:33:36 +0000 Date: Thu, 10 Oct 2013 02:33:36 +0000 Message-ID: From: "Thomas Mueller" <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> <52558779.2070203@pcbsd.org> <517D65A3D61F684FAE2B2EC2D2DA06C3@fisglobal.com> <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 Cc: "Teske, Devin" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 02:33:43 -0000 from Devin Teske: > I'm late to the party again ;D (didn't realize the rcs thread had turned BE) > Both problems can be solved. > The loading of the kernel *after* choosing your boot device is trivial. > We've been doing it at $work for *years* (almost a decade?) > I can put that in, whenever. Probably at the same time as implementing > the live/dynamic BE menus for selecting the root device. I'd like to know how to boot FreeBSD >= 9.1 with grub2. Following the instructions under $PORTSDIR/sysutils/grub2 insmod ufs2 set root=(hd0,gpt3) kfreebsd /boot/loader boot stopped working around FreeBSD 9.1-stable. I used Super Grub2 Disk image on the System Rescue CD written to USB stick. Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the System Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but haven't tested that yet. What is the method you or PC-BSD uses? I want to use it on FreeBSD 9.2 and 10-current. I tried visiting pcbsd.org website but couldn't find any details. Tom From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 03:10:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C1EAA8DE for ; Thu, 10 Oct 2013 03:10:23 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 6D62928CD for ; Thu, 10 Oct 2013 03:10:22 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 05AAD1EB1F for ; Thu, 10 Oct 2013 03:10:20 +0000 (UTC) Message-ID: <52561AB6.3030802@allanjude.com> Date: Wed, 09 Oct 2013 23:10:46 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "" Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4B3F2@LTCFISWMSGMB21.FNFIS.com> <525596A7.2090701@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4B907@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC4B907@LTCFISWMSGMB21.FNFIS.com> Content-Type: multipart/mixed; boundary="------------090500090706010405000101" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 03:10:23 -0000 This is a multi-part message in MIME format. --------------090500090706010405000101 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I've built up a fresh image with all of the latest changes. All known bugs are fixed: 1. problems if you restart a GELI based installation (preemptively run geli detach) 2. problem with GELI+MBR resulting in swap partition being in the wrong place (swap ended up as s1d instead of s1b) 3. prompt for the password once, instead of 18 times in the case of a 6 disk array 4. even more preemptive zpool labelclear for MBR to kill zombies 5. fixed the mis-scoping of a variable that resulting in the zpool using the entire device, and making the system unbootable Other Improvements 1. Better vdev type validation, do not allow the user to make an invalid selection, if they do prompt them to either cancel or select again 2. change the default name of the unencrypted pool from 'gelipool' to 'bootpool', since gelipool implies it is encrypted when it is not Attached is a patch against recent head Below are some re-built ALPHA5 .isos that you can use for testing http://www.allanjude.com/bsd/zfsbootonly.2013-10-09.iso.xz http://www.allanjude.com/bsd/zfsbootonly.2013-10-09.iso -- Allan Jude --------------090500090706010405000101 Content-Type: text/plain; charset=windows-1252; name="zfsboot.2013-10-09.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="zfsboot.2013-10-09.patch" Index: usr.sbin/bsdconfig/share/device.subr =================================================================== --- usr.sbin/bsdconfig/share/device.subr (revision 256194) +++ usr.sbin/bsdconfig/share/device.subr (working copy) @@ -49,6 +49,7 @@ f_struct_define DEVICE \ desc \ devname \ type \ + capacity \ enabled \ init \ get \ @@ -114,7 +115,7 @@ f_device_try() } # f_device_register $name $desc $devname $type $enabled $init_function \ -# $get_function $shutdown_function $private +# $get_function $shutdown_function $private $capacity # # Register a device. A `structure' (see struct.subr) is created with the name # device_$name (so make sure $name contains only alpha-numeric characters or @@ -128,6 +129,7 @@ f_device_register() { local name="$1" desc="$2" devname="$3" type="$4" enabled="$5" local init_func="$6" get_func="$7" shutdown_func="$8" private="$9" + local capacity="${10}" f_struct_new DEVICE "device_$name" || return $FAILURE device_$name set name "$name" @@ -139,6 +141,7 @@ f_device_register() device_$name set get "$get_func" device_$name set shutdown "$shutdown_func" device_$name set private "$private" + device_$name set capacity "$capacity" # Scan our global register to see if it needs ammending local dev found= @@ -196,7 +199,7 @@ f_device_get_all() f_dprintf "Found a network device named %s" "$devname" f_device_register $devname \ "$desc" "$devname" $DEVICE_TYPE_NETWORK 1 \ - f_media_init_network "" f_media_shutdown_network "" + f_media_init_network "" f_media_shutdown_network "" -1 done # Next, try to find all the types of devices one might use @@ -208,6 +211,10 @@ f_device_get_all() n=$(( $n + 1 )) # Get the desc, type, and max (with debugging disabled) # NOTE: Bypassing f_device_name_get() for efficiency + # ASIDE: This would be equivalent to the following: + # debug= f_device_name_get $dev desc + # debug= f_device_name_get $dev type + # debug= f_device_name_get $dev max debug= f_getvar _device_desc$n desc debug= f_getvar _device_type$n type debug= f_getvar _device_max$n max @@ -222,7 +229,8 @@ f_device_get_all() f_device_register "${devname##*/}" "$desc" \ "$devname" $DEVICE_TYPE_CDROM 1 \ f_media_init_cdrom f_media_get_cdrom \ - f_media_shutdown_cdrom "" + f_media_shutdown_cdrom "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a CDROM device for %s" \ "$devname" ;; @@ -232,7 +240,8 @@ f_device_get_all() "$devname" $DEVICE_TYPE_FLOPPY 1 \ f_media_init_floppy \ f_media_get_floppy \ - f_media_shutdown_floppy "" + f_media_shutdown_floppy "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a floppy device for %s" \ "$devname" ;; @@ -241,7 +250,8 @@ f_device_get_all() f_device_register "${devname##*/}" "$desc" \ "$devname" $DEVICE_TYPE_USB 1 \ f_media_init_usb f_media_get_usb \ - f_media_shutdown_usb "" + f_media_shutdown_usb "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a USB disk for %s" "$devname" ;; esac @@ -254,7 +264,8 @@ f_device_get_all() f_device_register "${devname##*/}" "ISO9660 file system" \ "$devname" $DEVICE_TYPE_CDROM 1 \ f_media_init_cdrom f_media_get_cdrom \ - f_media_shutdown_cdrom "" + f_media_shutdown_cdrom "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a CDROM device for %s" "$devname" done @@ -281,7 +292,8 @@ f_device_get_all() "md(4) vnode file system" \ "$devname" $DEVICE_TYPE_CDROM 1 \ f_media_init_cdrom f_media_get_cdrom \ - f_media_shutdown_cdrom "" + f_media_shutdown_cdrom "" \ + "$( f_device_capacity "$devname" )" f_dprintf "Found a CDROM device for %s" "$devname" ;; esac @@ -313,8 +325,13 @@ f_device_get_all() continue fi - f_device_register "$diskname" "" \ - "/dev/$diskname" $DEVICE_TYPE_DISK 0 + # Try and find its description + f_device_desc "$diskname" $DEVICE_TYPE_DISK desc + + f_device_register "$diskname" "$desc" \ + "/dev/$diskname" $DEVICE_TYPE_DISK 0 \ + "" "" "" "" \ + "$( f_device_capacity "$diskname" )" f_dprintf "Found a disk device named %s" "$diskname" # Look for existing partitions to register @@ -327,7 +344,8 @@ f_device_get_all() f_device_register "$slice" "" \ "/dev/$slice" $DEVICE_TYPE_DOS 1 \ f_media_init_dos f_media_get_dos \ - f_media_shutdown_dos "" + f_media_shutdown_dos "" \ + "$( f_device_capacity "/dev/$slice" )" f_dprintf "Found a DOS partition %s" "$slice" ;; 0xa5) # FreeBSD partition @@ -347,7 +365,9 @@ f_device_get_all() $DEVICE_TYPE_UFS 1 \ f_media_init_ufs \ f_media_get_ufs \ - f_media_shutdown_ufs "" + f_media_shutdown_ufs "" \ + "$( f_device_capacity \ + "$/dev/$part" )" f_dprintf "Found a UFS partition %s" \ "$part" done # parts @@ -379,10 +399,27 @@ f_device_name_get() case "$__prop" in type|desc|max) : good ;; *) return $FAILURE; esac + # + # Attempt to create an alternate-form of $__name that contains the + # first contiguous string of numbers replaced with `%d' for comparison + # against stored pattern names (see MAIN). + # + local __left="${__name%%[0-9]*}" __right="${__name#*[0-9]}" __dname= + if [ "$__left" != "$__name" ]; then + # Chop leading digits from right 'til we hit first non-digit + while :; do + case "$__right" in + [0-9]*) __right="${__right#[0-9]}" ;; + *) break + esac + done + __dname="${__left}%d$__right" + fi + [ "$__type" = "$DEVICE_TYPE_ANY" ] && __type= for __dev in $DEVICE_NAMES; do __n=$(( $__n + 1 )) - [ "$__dev" = "$__name" ] || continue + [ "$__dev" = "$__name" -o "$__dev" = "$__dname" ] || continue f_getvar _device_type$__n __devtype [ "${__type:-$__devtype}" = "$__devtype" ] || continue f_getvar _device_$__prop$__n $__var_to_set @@ -463,6 +500,39 @@ f_device_desc() fi fi + # + # For disks, attempt to return camcontrol(8) descriptions. + # Otherwise fall through to below static list. + # + f_have camcontrol && + [ "${__type:-$DEVICE_TYPE_DISK}" = "$DEVICE_TYPE_DISK" ] && + __cp=$( camcontrol devlist 2> /dev/null | awk -v disk="$__name" ' + $0~"(\\(|,)"disk"(,|\\))" { + if (!match($0, "<[^>]+>")) next + print substr($0, RSTART+1, RLENGTH-2) + found = 1 + exit + } + END { exit ! found } + ' ) && setvar "$__var_to_set" "$__cp" && return $SUCCESS + + # + # Attempt to create an alternate-form of $__name that contains the + # first contiguous string of numbers replaced with `%d' for comparison + # against stored pattern names (see MAIN). + # + local __left="${__name%%[0-9]*}" __right="${__name#*[0-9]}" __dname= + if [ "$__left" != "$__name" ]; then + # Chop leading digits from right 'til we hit first non-digit + while :; do + case "$__right" in + [0-9]*) __right="${__right#[0-9]}" ;; + *) break + esac + done + __dname="${__left}%d$__right" + fi + local __dev __devtype __n=0 for __dev in $DEVICE_NAMES; do __n=$(( $__n + 1 )) @@ -472,11 +542,8 @@ f_device_desc() __devname=$( f_substr "$__name" 0 ${#__dev} ) [ "$__devname" = "$__dev" ] || continue else - __devname="${__name%%[0-9]*}" - __devunit="${__name#$__devname}" - __devunit="${__devunit%%[!0-9]*}" - __devname=$( printf "$__dev" $__devunit ) - [ "$__devname" = "$__name" ] || continue + [ "$__dev" = "$__name" -o "$__dev" = "$__dname" ] || + continue fi debug= f_getvar _device_desc$__n $__var_to_set return $? @@ -655,7 +722,26 @@ f_device_menu() return $retval } +# f_device_capacity $device [$var_to_set] # +# Return the capacity of $device in bytes. +# +f_device_capacity() +{ + local __dev="$1" __var_to_set="$2" + local __bytes + + __bytes=$( diskinfo -v "$__dev" 2> /dev/null | + awk '/# mediasize in bytes/{print $1}' ) || __bytes=-1 + + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" "$__bytes" + else + echo "$__bytes" + fi +} + +# # Short-hand # f_cdrom() { f_device_name_set $DEVICE_TYPE_CDROM "$1" "$2" "$3"; } @@ -680,6 +766,7 @@ f_disk "ipsd%d" "IBM ServeRAID RAID array" f_disk "mfid%d" "LSI MegaRAID SAS array" 4 f_disk "mlxd%d" "Mylex RAID disk" 4 f_disk "twed%d" "3ware ATA RAID array" 4 +f_disk "vtbd%d" "VirtIO Block Device" 16 f_floppy "fd%d" "Floppy Drive unit A" 4 f_serial "cuau%d" "%s on device %s (COM%d)" 16 f_usb "da%da" "USB Mass Storage Device" 16 Index: usr.sbin/bsdconfig/share/strings.subr =================================================================== --- usr.sbin/bsdconfig/share/strings.subr (revision 256194) +++ usr.sbin/bsdconfig/share/strings.subr (working copy) @@ -26,6 +26,11 @@ if [ ! "$_STRINGS_SUBR" ]; then _STRINGS_SUBR=1 # # $FreeBSD$ # +############################################################ INCLUDES + +BSDCFG_SHARE="/usr/share/bsdconfig" +. $BSDCFG_SHARE/common.subr || exit 1 + ############################################################ GLOBALS # @@ -319,6 +324,112 @@ f_shell_unescape() f_replaceall "$__string" "'\\''" "'" "$__var_to_set" } +# f_expand_number $string [$var_to_set] +# +# Unformat $string into a number, optionally to be stored in $var_to_set. This +# function follows the SI power of two convention. +# +# The prefixes are: +# +# Prefix Description Multiplier +# k kilo 1024 +# M mega 1048576 +# G giga 1073741824 +# T tera 1099511627776 +# P peta 1125899906842624 +# E exa 1152921504606846976 +# +# NOTE: Prefixes are case-insensitive. +# +# Upon successful completion, the value 0 is returned (or stored to +# $var_to_set); otherwise -1. Reasons for a -1 return include: +# +# Given $string contains no digits. +# An unrecognized prefix was given. +# Result too large to calculate. +# +f_expand_number() +{ + local __string="$1" __var_to_set="$2" + local __cp __num + + # Remove any leading non-digits + while :; do + __cp="$__string" + __string="${__cp#[!0-9]}" + [ "$__string" = "$__cp" ] && break + done + + # Return `-1' if string didn't contain any digits + if [ ! "$__string" ]; then + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + fi + + # Store the numbers + __num="${__string%%[!0-9]*}" + + # Shortcut + if [ $__num -eq 0 ]; then + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" 0 + else + echo 0 + fi + return $SUCCESS + fi + + # Remove all the leading numbers from the string to get at the prefix + while :; do + __cp="$__string" + __string="${__cp#[0-9]}" + [ "$__string" = "$__cp" ] && break + done + + # Test for invalid prefix + case "$__string" in + ""|[KkMmGgTtPpEe]*) : known prefix ;; + *) + # Unknown prefix + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + esac + + # Multiply the number out + case "$__string" in + [Kk]) __num=$(( $__num * 1024 )) ;; + [Mm]) __num=$(( $__num * 1048576 )) ;; + [Gg]) __num=$(( $__num * 1073741824 )) ;; + [Tt]) __num=$(( $__num * 1099511627776 )) ;; + [Pp]) __num=$(( $__num * 1125899906842624 )) ;; + [Ee]) __num=$(( $__num * 1152921504606846976 )) ;; + esac + if [ $__num -le 0 ]; then + # Arithmetic overflow + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" -1 + else + echo -1 + fi + return $FAILURE + fi + + # Return the number + if [ "$__var_to_set" ]; then + setvar "$__var_to_set" $__num + else + echo $__num + fi +} + ############################################################ MAIN f_dprintf "%s: Successfully loaded." strings.subr Index: usr.sbin/bsdinstall/bsdinstall =================================================================== --- usr.sbin/bsdinstall/bsdinstall (revision 256194) +++ usr.sbin/bsdinstall/bsdinstall (working copy) @@ -28,6 +28,7 @@ : ${BSDINSTALL_LOG="/tmp/bsdinstall_log"}; export BSDINSTALL_LOG : ${BSDINSTALL_TMPETC="/tmp/bsdinstall_etc"}; export BSDINSTALL_TMPETC +: ${BSDINSTALL_TMPBOOT="/tmp/bsdinstall_boot"}; export BSDINSTALL_TMPBOOT : ${PATH_FSTAB="$BSDINSTALL_TMPETC/fstab"}; export PATH_FSTAB : ${BSDINSTALL_DISTDIR="/usr/freebsd-dist"}; export BSDINSTALL_DISTDIR : ${BSDINSTALL_CHROOT="/mnt"}; export BSDINSTALL_CHROOT @@ -35,5 +36,6 @@ VERB=${1:-auto}; shift [ -d "$BSDINSTALL_TMPETC" ] || mkdir -p "$BSDINSTALL_TMPETC" +[ -d "$BSDINSTALL_TMPBOOT" ] || mkdir -p "$BSDINSTALL_TMPBOOT" echo "Running installation step: $VERB $@" >> "$BSDINSTALL_LOG" exec "/usr/libexec/bsdinstall/$VERB" "$@" 2>> "$BSDINSTALL_LOG" Index: usr.sbin/bsdinstall/scripts/Makefile =================================================================== --- usr.sbin/bsdinstall/scripts/Makefile (revision 256194) +++ usr.sbin/bsdinstall/scripts/Makefile (working copy) @@ -2,7 +2,7 @@ SCRIPTS= auto adduser checksum config docsinstall hostname jail keymap \ mirrorselect mount netconfig netconfig_ipv4 netconfig_ipv6 rootpass \ - script services time umount wlanconfig + script services time umount wlanconfig zfsboot BINDIR= /usr/libexec/bsdinstall NO_MAN= true Index: usr.sbin/bsdinstall/scripts/auto =================================================================== --- usr.sbin/bsdinstall/scripts/auto (revision 256194) +++ usr.sbin/bsdinstall/scripts/auto (working copy) @@ -93,24 +93,46 @@ fi rm $PATH_FSTAB touch $PATH_FSTAB -dialog --backtitle "FreeBSD Installer" --title "Partitioning" --extra-button \ - --extra-label "Manual" --ok-label "Guided" --cancel-label "Shell" \ - --yesno "Would you like to use the guided partitioning tool (recommended for beginners) or to set up partitions manually (experts)? You can also open a shell and set up partitions entirely by hand." 0 0 +PMODES="\ +Guided \"Partitioning Tool (Recommended for Beginners)\" \ +Manual \"Manually Configure Partitions (Expert)\" \ +Shell \"Open a shell and partition by hand\"" -case $? in -0) # Guided +CURARCH=$( uname -m ) +case $CURARCH in + amd64|i386) # Booting ZFS Supported + PMODES="$PMODES ZFS \"Automatic Root-on-ZFS (Experimental)\"" + ;; + *) # Booting ZFS Unspported + ;; +esac + +exec 3>&1 +PARTMODE=`echo $PMODES | xargs dialog --backtitle "FreeBSD Installer" \ + --title "Partitioning" \ + --menu "How would you like to partition your disk?" \ + 0 0 0 2>&1 1>&3` +if [ $? -eq $DIALOG_CANCEL ]; then exit 1; fi +exec 3>&- + +case "$PARTMODE" in +"Guided") # Guided bsdinstall autopart || error bsdinstall mount || error ;; -1) # Shell +"Shell") # Shell clear echo "Use this shell to set up partitions for the new system. When finished, mount the system at $BSDINSTALL_CHROOT and place an fstab file for the new system at $PATH_FSTAB. Then type 'exit'. You can also enter the partition editor at any time by entering 'bsdinstall partedit'." sh 2>&1 ;; -3) # Manual +"Manual") # Manual bsdinstall partedit || error bsdinstall mount || error ;; +"ZFS") # ZFS + bsdinstall zfsboot || error + bsdinstall mount || error + ;; *) error ;; Index: usr.sbin/bsdinstall/scripts/config =================================================================== --- usr.sbin/bsdinstall/scripts/config (revision 256194) +++ usr.sbin/bsdinstall/scripts/config (working copy) @@ -31,6 +31,11 @@ rm $BSDINSTALL_TMPETC/rc.conf.* cp $BSDINSTALL_TMPETC/* $BSDINSTALL_CHROOT/etc +cat $BSDINSTALL_TMPBOOT/loader.conf.* >> $BSDINSTALL_TMPBOOT/loader.conf +rm $BSDINSTALL_TMPBOOT/loader.conf.* + +cp $BSDINSTALL_TMPBOOT/* $BSDINSTALL_CHROOT/boot + # Set up other things from installed config chroot $BSDINSTALL_CHROOT /usr/bin/newaliases Index: usr.sbin/bsdinstall/scripts/keymap =================================================================== --- usr.sbin/bsdinstall/scripts/keymap (revision 256194) +++ usr.sbin/bsdinstall/scripts/keymap (working copy) @@ -1,6 +1,7 @@ #!/bin/sh #- # Copyright (c) 2011 Nathan Whitehorn +# Copyright (c) 2013 Devin Teske # All rights reserved. # # Redistribution and use in source and binary forms, with or without @@ -25,11 +26,195 @@ # SUCH DAMAGE. # # $FreeBSD$ +# +############################################################ INCLUDES + +BSDCFG_SHARE="/usr/share/bsdconfig" +. $BSDCFG_SHARE/common.subr || exit 1 +f_dprintf "%s: loading includes..." "$0" +f_include $BSDCFG_SHARE/dialog.subr -kbdcontrol -d >/dev/null 2>&1 -if [ $? -eq 0 ]; then - dialog --backtitle "FreeBSD Installer" --title "Keymap Selection" \ - --yesno "Would you like to set a non-default key mapping for your keyboard?" 0 0 || exit 0 - exec 3>&1 - kbdmap 2>&1 1>&3 | grep 'keymap=' > $BSDINSTALL_TMPETC/rc.conf.keymap -fi +############################################################ CONFIGURATION + +# +# Default file to store keymap selection in +# +: ${KEYMAPFILE:=$BSDINSTALL_TMPETC/rc.conf.keymap} + +# +# Default path to keymap INDEX containing descriptions +# +: ${MAPDESCFILE:=/usr/share/syscons/keymaps/INDEX.keymaps} + +############################################################ GLOBALS + +# +# Strings that should be moved to an i18n file and loaded with f_include_lang() +# +hline_arrows_space_tab_enter="Use arrows, SPACE, TAB or ENTER" +msg_cancel="Cancel" +msg_change_keymap="Change keymap" +msg_change_keymap_help="Select a different keyboard mapping" +msg_current_keyboard_mapping_is="The current keyboard mapping is:\n%s" +msg_default="default" +msg_freebsd_installer="FreeBSD Installer" +msg_keymap_prompt="Would you like to set a non-default key mapping for your keyboard?" +msg_keymap_selection="Keymap Selection" +msg_ok="OK" +msg_select="Select" +msg_test_keymap="Test" +msg_test_keymap_desc="Try the selected keymap" +msg_test_keymap_help="Test the selected keymap to make sure it is correct" +msg_test_the_keymap_by_typing="Test the keymap by typing letters, numbers, and symbols. Characters should match the labels on the keyboard keys.\nPress Enter to stop testing." +msg_use_this_keymap="Continue" +msg_use_this_keymap_desc="Use this keymap and begin installation" +msg_use_this_keymap_help="Start the install using the currently selected keymap" + +############################################################ FUNCTIONS + +# dialog_menu_main +# +# Display the dialog(1)-based application main menu. +# +dialog_menu_main() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_keymap_prompt" + local hline="$hline_arrows_space_tab_enter" + + local mapdesc="$msg_default" keymap + if [ -s "$KEYMAPFILE" ]; then + # Get the current keymap and a description to display + keymap=$( awk '/keymap=/{sub(/^.*=/,"");gsub(/"/,"");print}' \ + "$KEYMAPFILE" ) + mapdesc=$( awk -v keymap="$keymap" len=${#keymap} ' + substr($0,0,len+4)==keymap":en:"{ + if (length($0) < len+5) continue + print substr($0, len+5) " (" keymap ")" + exit + }' "$MAPDESCFILE" ) + fi + [ "$keymap" ] || keymap='default' + cur_keymap=$( printf "$msg_current_keyboard_mapping_is" "$keymap" ) + + local height width + local menu_list=" + '1 $msg_use_this_keymap' '$msg_use_this_keymap_desc' + '$msg_use_this_keymap_help' + '2 $msg_change_keymap' '$cur_keymap' + '$msg_change_keymap_help' + '3 $msg_test_keymap' '$msg_test_keymap_desc' + '$msg_test_keymap_help' + " # END-QUOTE + + eval f_dialog_menu_with_help_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $menu_list + + local menu_choice + menu_choice=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --item-help \ + --ok-label \"$msg_select\" \ + --cancel-label \"$msg_cancel\" \ + --menu \"\$prompt\" \ + $height $width $rows \ + $menu_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) + local retval=$? + f_dialog_data_sanitize menu_choice + f_dialog_menutag_store "$menu_choice" + + return $retval +} + +# dialog_keymap_test +# +# Display an input box (without cancel button) for the user to test keyboard +# input and return. Always returns success. +# +dialog_keymap_test() +{ + local title= # Calculated below + local btitle= # Calculated below + local prompt="$msg_test_the_keymap_by_typing" + local hline="$hline_arrows_space_tab_enter" + + f_dialog_title "$msg_test_keymap" + title="$DIALOG_TITLE" + btitle="$DIALOG_BACKTITLE" + f_dialog_title_restore + + local height width + f_dialog_inputbox_size height width \ + "$title" "$btitle" "$prompt" "" "$hline" + + $DIALOG \ + --title "$title" \ + --backtitle "$btitle" \ + --hline "$hline" \ + --ok-label "$msg_ok" \ + --no-cancel \ + --inputbox "$prompt" \ + $height $width \ + 2>/dev/null >&$DIALOG_TERMINAL_PASSTHRU_FD + + return $DIALOG_OK +} + +############################################################ MAIN + +# +# Initialize +# +f_dialog_title "$msg_keymap_selection" +f_dialog_backtitle "$msg_freebsd_installer" + +# +# Die immediately if we can't dump the current keyboard map +# +error=$( kbdcontrol -d 2>&1 > /dev/null ) || f_die $FAILURE "%s" "$error" + +# Capture Ctrl-C for clean-up +trap 'rm -f $KEYMAPFILE; exit $FAILURE' SIGINT + +# +# Loop until the user has finalized their selection +# +while :; do + dialog_menu_main + retval=$? + f_dialog_menutag_fetch mtag + f_dprintf "retval=%u mtag=[%s]" $reval "$mtag" + + if [ $retval -ne $DIALOG_OK ]; then + rm -f "$KEYMAPFILE" + exit 1 # Exit with an error so bsdinstall restarts + fi + + case "$mtag" in + ?" $msg_use_this_keymap") + break # User is finished and ready to move on + ;; + ?" $msg_change_keymap") + # User chose ``Change keymap'' option + kbdmap 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD | + grep 'keymap=' > "$KEYMAPFILE" + ;; + ?" $msg_test_keymap") + # User chose ``Test keymap'' option + dialog_keymap_test + ;; + *) # Don't know what happened here + rm -f "$KEYMAPFILE" + exit 1 # Exit with an error so bsdinstall restarts + ;; + esac +done + +################################################################################ +# END +################################################################################ Index: usr.sbin/bsdinstall/scripts/netconfig =================================================================== --- usr.sbin/bsdinstall/scripts/netconfig (revision 256194) +++ usr.sbin/bsdinstall/scripts/netconfig (working copy) @@ -41,11 +41,19 @@ DIALOG_TAGS="" : ${DIALOG_ITEM_HELP=4} : ${DIALOG_ESC=255} +# Do a dirty check to see if this a wireless interface -- there should be a +# better way +is_wireless_if() { + ifconfig $1 | grep -q 'media: IEEE 802.11 Wireless' +} + + for IF in `ifconfig -l`; do test "$IF" = "lo0" && continue (ifconfig -g wlan | egrep -wq $IF) && continue INTERFACES="$INTERFACES $IF" DESC=`sysctl -n dev.$(echo $IF | sed -E 's/([[:alpha:]]*)([[:digit:]]*)/\1.\2/g').%desc` + is_wireless_if $IF && echo $DESC | grep -iqv wireless && DESC="Wireless $DESC" DIALOG_TAGS="$DIALOG_TAGS $IF \"$DESC\"" done @@ -63,10 +71,8 @@ exec 3>&- : > $BSDINSTALL_TMPETC/._rc.conf.net -# Do a dirty check to see if this a wireless interface -- there should be a -# better way IFCONFIG_PREFIX="" -if ifconfig $INTERFACE | grep -q 'media: IEEE 802.11 Wireless'; then +if is_wireless_if $INTERFACE; then NEXT_WLAN_IFACE=wlan0 # XXX echo wlans_$INTERFACE=\"$NEXT_WLAN_IFACE\" >> $BSDINSTALL_TMPETC/._rc.conf.net IFCONFIG_PREFIX="WPA " Index: usr.sbin/bsdinstall/scripts/services =================================================================== --- usr.sbin/bsdinstall/scripts/services (revision 256194) +++ usr.sbin/bsdinstall/scripts/services (working copy) @@ -46,22 +46,23 @@ DAEMONS=$(dialog --backtitle "FreeBSD Installer" \ moused "PS/2 mouse pointer on console" ${moused_enable:-off} \ ntpd "Synchronize system and network time" ${ntpd_enable:-off} \ powerd "Adjust CPU frequency dynamically if supported" ${powerd_enable:-off} \ + dumpdev "Would you like to enable crash dumps to /var ?" ${dumpdev:-on} \ 2>&1 1>&3) exec 3>&- +local havedump= for daemon in $DAEMONS; do + if [ "$daemon" == "dumpdev" ]; then + havedump=1 + echo \# Set dumpdev to \"AUTO\" to enable crash dumps, \ + \"NO\" to disable >> \ + $BSDINSTALL_TMPETC/rc.conf.services + echo dumpdev=\"AUTO\" >> $BSDINSTALL_TMPETC/rc.conf.services + continue + fi echo ${daemon}_enable=\"YES\" >> $BSDINSTALL_TMPETC/rc.conf.services done -echo \# Set dumpdev to \"AUTO\" to enable crash dumps, \"NO\" to disable >> \ - $BSDINSTALL_TMPETC/rc.conf.services - -dialog --backtitle "FreeBSD Installer" --title "Dumpdev Configuration" \ - --nocancel --yesno \ - "Would you like to enable crash dumps? If you start having problems with the system it can help the FreeBSD developers debug the problem. But the crash dumps can take up a lot of disk space in /var." 0 0 - -if [ $? -eq $DIALOG_OK ]; then - echo dumpdev=\"AUTO\" >> $BSDINSTALL_TMPETC/rc.conf.services -else +if [ ! "$havedump" ]; then echo dumpdev=\"NO\" >> $BSDINSTALL_TMPETC/rc.conf.services fi Index: usr.sbin/bsdinstall/scripts/zfsboot =================================================================== --- usr.sbin/bsdinstall/scripts/zfsboot (revision 0) +++ usr.sbin/bsdinstall/scripts/zfsboot (working copy) @@ -0,0 +1,1020 @@ +#!/bin/sh +#- +# Copyright (c) 2013 Allan Jude +# Copyright (c) 2013 Devin Teske +# All rights reserved. +# +# Redistribution and use in source and binary forms, with or without +# modification, are permitted provided that the following conditions +# are met: +# 1. Redistributions of source code must retain the above copyright +# notice, this list of conditions and the following disclaimer. +# 2. Redistributions in binary form must reproduce the above copyright +# notice, this list of conditions and the following disclaimer in the +# documentation and/or other materials provided with the distribution. +# +# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND +# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE +# FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +# SUCH DAMAGE. +# +# $FreeBSD$ +# +############################################################ INCLUDES + +BSDCFG_SHARE="/usr/share/bsdconfig" +. $BSDCFG_SHARE/common.subr || exit 1 +f_dprintf "%s: loading includes..." "$0" +f_include $BSDCFG_SHARE/device.subr +f_include $BSDCFG_SHARE/dialog.subr + +############################################################ CONFIGURATION + +# +# Default name of the boot-pool +# +: ${ZFSBOOT_POOL_NAME:=zroot} + +# +# Default name for the boot environment parent dataset +# +: ${ZFSBOOT_BEROOT_NAME:=bootenv} + +# +# Default name for the primany boot environment +# +: ${ZFSBOOT_BOOTFS_NAME:=default} + +# +# Default Virtual Device (vdev) type to create +# +: ${ZFSBOOT_VDEV_TYPE:=stripe} + +# +# Should we use gnop(8) to configure a transparent mapping to 4K sectors? +# +: ${ZFSBOOT_GNOP_4K_FORCE_ALIGN:=1} + +# +# Should we use geli(8) to encrypt the drives? +# +: ${ZFSBOOT_GELI_ENCRYPTION:=} + +# +# Default name the unencrypted pool when using geli(8) to encrypt the drives +# +: ${ZFSBOOT_GELI_POOL_NAME:=bootpool} + +# +# Default size for the unencrypted boot pool when using geli(8) +# +: ${ZFSBOOT_GELI_BOOT_SIZE:=2g} + +# +# Default path to the geli(8) keyfile used in drive encryption +# +: ${ZFSBOOT_GELI_KEY_FILE:=/boot/encryption.key} + +# +# Default disks to use (always empty unless being scripted) +# +: ${ZFSBOOT_DISKS:=} + +# +# Default partitioning scheme to use on disks +# +: ${ZFSBOOT_PARTITION_SCHEME:=GPT} + +# +# How much swap to put on each block device in the boot zpool +# NOTE: Value passed to gpart(8); which supports SI unit suffixes. +# +: ${ZFSBOOT_SWAP_SIZE:=2g} + +# +# Default ZFS layout for root zpool +# +# NOTE: Requires /tmp, /var/tmp, /$ZFSBOOT_BOOTFS_NAME/$ZFSBOOT_BOOTFS_NAME +# NOTE: Anything after pound/hash character [#] is ignored as a comment. +# +f_isset ZFSBOOT_DATASETS || ZFSBOOT_DATASETS=" + # DATASET OPTIONS (comma or space separated; or both) + + # Boot Environment [BE] root and default boot dataset + /$ZFSBOOT_BEROOT_NAME mountpoint=none + /$ZFSBOOT_BEROOT_NAME/$ZFSBOOT_BOOTFS_NAME mountpoint=/ + + # Compress /tmp, allow exec but not setuid + /tmp mountpoint=/tmp,compression=lz4,exec=on,setuid=off + + # Don't mount /usr so that 'base' files go to the BEROOT + /usr mountpoint=/usr,canmount=off + + /usr/local # local files (i.e. from packages) separate from base system + + # Home directories separated so they are common to all BEs + /usr/home setuid=off + + # Ports tree + /usr/ports compression=lz4,setuid=off + /usr/ports/distfiles compression=off,exec=off,setuid=off + /usr/ports/packages compression=off,exec=off,setuid=off + + # Source tree (compressed) + /usr/src compression=lz4,exec=off,setuid=off + /usr/obj # Object files + + # Create /var and friends + /var mountpoint=/var + /var/crash compression=lz4,exec=off,setuid=off + /var/db exec=off,setuid=off + /var/db/pkg compression=lz4,exec=off,setuid=off + /var/empty exec=off,setuid=off + /var/log compression=lz4,exec=off,setuid=off + /var/mail compression=lz4,exec=off,setuid=off + /var/run exec=off,setuid=off + /var/tmp compression=lz4,exec=on,setuid=off +" # END-QUOTE + +############################################################ GLOBALS + +# +# Strings that should be moved to an i18n file and loaded with f_include_lang() +# +hline_alnum_arrows_punc_tab_enter="Use alnum, arrows, punctuation, TAB or ENTER" +hline_arrows_space_tab_enter="Use arrows, SPACE, TAB or ENTER" +hline_arrows_tab_enter="Press arrows, TAB or ENTER" +msg_back="Back" +msg_cancel="Cancel" +msg_change="Change Selection" +msg_configure_options="Configure Options:" +msg_create="Install" +msg_create_desc="Proceed with Installation" +msg_create_help="Create ZFS boot pool with displayed options" +msg_detailed_disk_info="gpart(8) show %s:\n%s\n\ncamcontrol(8) inquiry %s:\n%s\n\n\ncamcontrol(8) identify %s:\n%s\n" +msg_disk_info="Disk Info" +msg_disk_info_help="Get detailed information on disk device(s)" +msg_disks_to_use="Disks To Use" +msg_disks_to_use_help="Choose which disks to use for the Virtual Device (Required)" +msg_force_4k_sectors="Force 4K Sectors?" +msg_force_4k_sectors_help="Use gnop(8) to configure forced 4K sector alignment" +msg_geli_encryption="Encrypt Disks?" +msg_geli_encryption_help="Use geli(8) to encrypt all data partitions" +msg_geli_password="Enter a strong passphrase, used to protect your encryption keys. You will be required to enter this passphrase each time the system is booted" +msg_freebsd_installer="FreeBSD Installer" +msg_invalid_virtual_device_type="Invalid Virtual Device type \`%s'" +msg_invalid_virtual_device_type_help="Select another Virtual Device type or cancel and return to the ZFS menu. From there you can select more disks or rescan from additional devices" +msg_last_chance_are_you_sure="Last Chance! Are you sure you want to destroy the current contents of the following disks:\n%s" +msg_last_chance_are_you_sure_color="\\\\ZrLast Chance!\\\\ZR Are you \\\\Z1sure\\\\Zn you want to \\\\Zr\\\\Z1destroy\\\\Zn the current contents of the following disks:\n%s" +msg_mirror_desc="Mirror - n-Way Mirroring" +msg_mirror_help="[2+ Disks] Mirroring provides the best performance, but the least storage" +msg_no="NO" +msg_no_disks_present_to_configure="No disk(s) present to configure" +msg_no_disks_selected="No disks selected." +msg_not_enough_disks_selected="Not enough disks selected (minimum %u)" +msg_ok="OK" +msg_partition_scheme="Partition Scheme" +msg_partition_scheme_help="Toggle between GPT and MBR partitioning schemes" +msg_please_enter_a_name_for_your_zpool="Please enter a name for your zpool:" +msg_please_enter_amount_of_swap_space="Please enter amount of swap space (SI-Unit suffixes\nrecommended; e.g., \`2g' for 2 Gigabytes):" +msg_please_select_one_or_more_disks="Please select one or more disks to create a zpool:" +msg_pool_name="Pool Name" +msg_pool_name_cannot_be_empty="Pool name cannot be empty." +msg_pool_name_help="Customize the name of the zpool to be created (Required)" +msg_raidz1_desc="RAID-Z1 - Single Redundant RAID" +msg_raidz1_help="[3+ Disks] Withstand failure of 1 disk. Recommended for: 3, 5 or 9 disks" +msg_raidz2_desc="RAID-Z2 - Double Redundant RAID" +msg_raidz2_help="[4+ Disks] Withstand failure of 2 disks. Recommended for: 4, 6 or 10 disks" +msg_raidz3_desc="RAID-Z3 - Triple Redundant RAID" +msg_raidz3_help="[5+ Disks] Withstand failure of 3 disks. Recommended for: 5, 7 or 11 disks" +msg_rescan_devices="Rescan Devices" +msg_rescan_devices_help="Scan for device changes" +msg_select="Select" +msg_select_a_disk_device="Select a disk device" +msg_select_virtual_device_type="Select Virtual Device type:" +msg_stripe_desc="Stripe - No Redundancy" +msg_stripe_help="[1+ Disks] Striping provides maximum storage but no redundancy" +msg_swap_size="Swap Size" +msg_swap_size_help="Customize how much swap space is allocated to each selected disk" +msg_yes="YES" +msg_zfs_configuration="ZFS Configuration" +msg_zfs_vdev_type="ZFS VDev Type" +msg_zfs_vdev_type_help="Select type of ZFS Virtual Device to create" + +############################################################ FUNCTIONS + +# dialog_menu_main +# +# Display the dialog(1)-based application main menu. +# +dialog_menu_main() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_configure_options" + local force4k="$msg_no" + local usegeli="$msg_no" + [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ] && force4k="$msg_yes" + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && usegeli="$msg_yes" + local menu_list=" + '>>> $msg_create' '$msg_create_desc' + '$msg_create_help' + '- $msg_rescan_devices' '*' + '$msg_rescan_devices_help' + '- $msg_disk_info' '*' + '$msg_disk_info_help' + '1 $msg_pool_name' '$ZFSBOOT_POOL_NAME' + '$msg_pool_name_help' + '2 $msg_disks_to_use' '$ZFSBOOT_DISKS' + '$msg_disks_to_use_help' + '3 $msg_zfs_vdev_type' '$ZFSBOOT_VDEV_TYPE' + '$msg_zfs_vdev_type_help' + '4 $msg_force_4k_sectors' '$force4k' + '$msg_force_4k_sectors_help' + '5 $msg_geli_encryption' '$usegeli' + '$msg_geli_encryption_help' + '6 $msg_partition_scheme' '$ZFSBOOT_PARTITION_SCHEME' + '$msg_partition_scheme_help' + '7 $msg_swap_size' '$ZFSBOOT_SWAP_SIZE' + '$msg_swap_size_help' + " # END-QUOTE + local defaultitem= # Calculated below + local hline="$hline_alnum_arrows_punc_tab_enter" + + local height width rows + eval f_dialog_menu_with_help_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $menu_list + + # Obtain default-item from previously stored selection + f_dialog_default_fetch defaultitem + + local menu_choice + menu_choice=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --item-help \ + --ok-label \"\$msg_select\" \ + --cancel-label \"\$msg_cancel\" \ + --default-item \"\$defaultitem\" \ + --menu \"\$prompt\" \ + $height $width $rows \ + $menu_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) + local retval=$? + f_dialog_data_sanitize menu_choice + f_dialog_menutag_store "$menu_choice" + + # Only update default-item on success + [ $retval -eq $DIALOG_OK ] && f_dialog_default_store "$menu_choice" + + return $retval +} + +# dialog_edit_disks +# +# Edit the list of disks to be used by the ZFS boot pool. +# +dialog_edit_disks() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_please_select_one_or_more_disks" + local check_list= # Calculated below + local hline="$hline_arrows_space_tab_enter" + local dev vardev disks= + + # + # Get a [new] list of disk devices + # + f_device_find "" $DEVICE_TYPE_DISK disks + if [ ! "$disks" ]; then + f_show_msg "$msg_no_disks_present_to_configure" + return $FAILURE + fi + + # Lets sort the disks array to be more user friendly + disks=$( echo "$disks" | tr ' ' '\n' | sort | tr '\n' ' ' ) + + # + # Loop through the list of selected disks and create temporary local + # variables mapping their status onto an up-to-date list of disks. + # + for dev in $ZFSBOOT_DISKS; do + f_str2varname "$dev" vardev + local _${vardev}_status=on + done + + # + # Create the checklist menu of discovered disk devices + # + local on_off + for dev in $disks; do + local desc= + device_$dev get desc desc + f_shell_escape "$desc" desc + f_str2varname "$dev" vardev + f_getvar _${vardev}_status:-off on_off + check_list="$check_list '$dev' '$desc' $on_off" + done + + # + # Prompt the user to check some disks + # + local height width rows + eval f_dialog_checklist_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $check_list + disks=$( eval $DIALOG \ + --title \"\$DIALOG_TITLE\" \ + --backtitle \"\$DIALOG_BACKTITLE\" \ + --hline \"\$hline\" \ + --ok-label \"\$msg_ok\" \ + --cancel-label \"\$msg_cancel\" \ + --checklist \"\$prompt\" \ + $height $width $rows \ + $check_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) || return $? + # Exit if user either pressed ESC or chose Cancel/No + f_dialog_data_sanitize disks + + ZFSBOOT_DISKS="$disks" + + return $DIALOG_OK +} + +# dialog_menu_vdev +# +# Prompt the user to select a a Virtual Device type. +# +dialog_menu_vdev() +{ + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local prompt="$msg_select_virtual_device_type" + + # Make sure [potentially scripted] selections are real + real_disks= + for disk in $ZFSBOOT_DISKS; do + f_struct device_$disk && real_disks="$real_disks $disk" + done + # Make sure we have at least one real disk selected + ndisks=$( set -- $real_disks; echo $# ) + + local menu_list=" + 'stripe' '$msg_stripe_desc' '$msg_stripe_help' + 'mirror' '$msg_mirror_desc' '$msg_mirror_help' + 'raidz1' '$msg_raidz1_desc' '$msg_raidz1_help' + 'raidz2' '$msg_raidz2_desc' '$msg_raidz2_help' + 'raidz3' '$msg_raidz3_desc' '$msg_raidz3_help' + " # END-QUOTE + + local defaultitem="$ZFSBOOT_VDEV_TYPE" + local hline="$hline_arrows_tab_enter" + local error_msg revalidate_choice + + local height width rows + eval f_dialog_menu_size height width rows \ + \"\$title\" \"\$btitle\" \"\$prompt\" \"\$hline\" $menu_list + + local menu_choice + menu_choice=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --ok-label \"\$msg_ok\" \ + --cancel-label \"\$msg_cancel\" \ + --item-help \ + --default-item \"\$defaultitem\" \ + --menu \"\$prompt\" \ + $height $width $rows \ + $menu_list \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) || return $FAILURE + f_dialog_data_sanitize menu_choice + + # Make sure we have enough disks for the desired vdev type + case "$menu_choice" in + stripe) want_disks=1 ;; + mirror) want_disks=2 ;; + raidz1) want_disks=3 ;; + raidz2) want_disks=4 ;; + raidz3) want_disks=5 ;; + *) + f_show_msg "$msg_invalid_virtual_device_type" \ + "$menu_choice" + continue + ;; + esac + if [ $ndisks -lt $want_disks ]; then + error_msg=$( printf "%s: $msg_not_enough_disks_selected\n%s" \ + "$menu_choice" "$want_disks" \ + "$msg_invalid_virtual_device_type_help" ) + eval f_dialog_buttonbox_size height width \"\$title\" \ + \"\$btitle\" \"\$error_msg\" \"\$hline\" + defaultitem=$msg_change revalidate_choice=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --yes-label \"\$msg_change\" \ + --no-label \"\$msg_cancel\" \ + --default-item \"\$defaultitem\" \ + --yesno \"\$error_msg\" \ + $height $width \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) || return $FAILURE + dialog_menu_vdev + else + ZFSBOOT_VDEV_TYPE="$menu_choice" + fi + +} + +# zfs_create_diskpart $disk $index +# +# For each block device to be used in the zpool, rather than just create the +# zpool with the raw block devices (e.g., da0, da1, etc.) we create partitions +# so we can have some real swap. This also provides wiggle room incase your +# replacement drivers do not have the exact same sector counts. +# +# NOTE: The MBR layout is more complicated (GPT is preferred). +# +zfs_create_diskpart() +{ + local disk="$1" index="$2" + local funcname=zfs_create_diskpart + local disksize partsize + + # Check arguments + [ "$disk" -a "$index" ] || return $FAILURE + + # + # Destroy whatever partition layout is currently on disk. + # NOTE: `-F' required to destroy if partitions still exist. + # NOTE: Failure is ok here, blank disk will have nothing to destroy. + # + f_quietly gpart destroy -F $disk + f_quietly zpool labelclear -f /dev/$disk # Kill it with fire + + # Make doubly-sure backup GPT is destroyed + f_quietly gpart create -s gpt $disk || return $FAILURE + f_quietly gpart destroy -F $disk || return $FAILURE + + # Calculate partition size given desired amount of swap + device_$disk get capacity disksize || return $FAILURE + partsize=$(( $disksize - $swapsize )) + + # + # Lay down the desired type of partition scheme + # + local setsize mbrindex + case "$ZFSBOOT_PARTITION_SCHEME" in + ""|GPT) + # + # 1. Create GPT layout using labels + # + gpart create -s gpt $disk || return $FAILURE + + # + # 2. Add small freebsd-boot partition labeled `boot#' + # + gpart add -l gptboot$index -t freebsd-boot -s 512k $disk || + return $FAILURE + gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 $disk || + return $FAILURE + + # zpool will use the `zfs#' GPT labels + bootpart=p2 targetpart=p2 + + # Change things around if we are using GELI + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + bootpart=p2 targetpart=p3 + partsize=$(( $partsize - $gelisize )) + gpart add -l boot$index -t freebsd-zfs \ + -s ${gelisize}b -a 1m $disk || return $FAILURE + # Pedantically nuke any old labels, stop geli + f_quietly zpool labelclear -f /dev/$disk$bootpart + f_quietly geli detach -f /dev/$disk$targetpart + fi + + # + # 3. Add freebsd-zfs partition labeled `zfs#' for zpool + # NOTE: Using above calculated partsize to leave room for swap. + # + [ $swapsize -gt 0 ] && setsize="-s ${partsize}b" + gpart add -l zfs$index -t freebsd-zfs $setsize -a 1m $disk || + return $FAILURE + f_quietly zpool labelclear -f /dev/$disk$targetpart # Pedantic + + # + # 4. Add freebsd-swap partition labeled `swap#' + # + if [ $swapsize -gt 0 ]; then + gpart add -l swap$index -t freebsd-swap -a 1m $disk || + return $FAILURE + # Update fstab(5) + printf "$fstab_fmt" \ + /dev/gpt/swap$index none swap sw 0 0 \ + >> $BSDINSTALL_TMPETC/fstab || return $FAILURE + fi + ;; + + MBR) + # + # 1. Create MBR layout (no labels) + # + gpart create -s mbr $disk || return $FAILURE + gpart bootcode -b /boot/boot0 $disk || return $FAILURE + + # + # 2. Add freebsd slice with all available space + # + gpart add -t freebsd $disk || return $FAILURE + gpart set -a active -i 1 $disk || return $FAILURE + f_quietly zpool labelclear -f /dev/${disk}s1 # Pedantic + f_quietly gpart destroy -F ${disk}s1 # Pedantic + + # + # 3. Write BSD sceme to the freebsd slice + # + gpart create -s BSD ${disk}s1 || return $FAILURE + + # zpool will use s1a (no labels) + bootpart=s1a targetpart=s1a mbrindex=1 + + # Change things around if we are using GELI + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + bootpart=s1a targetpart=s1d + partsize=$(( $partsize - $gelisize )) + mbrindex=4 # If this is s1a then make the zpool s1d + gpart add -t freebsd-zfs -i 1 -s ${gelisize}b ${disk}s1 || + return $FAILURE + # Pedantically nuke any old labels, stop geli + f_quietly zpool labelclear -f /dev/$disk$bootpart + f_quietly geli detach -f /dev/$disk$targetpart + fi + + # + # 4. Partition the BSD slice for ZFS + # NOTE: Using above calculated partsize to leave room for swap. + # + [ $swapsize -gt 0 ] && setsize="-s ${partsize}b" + gpart add -t freebsd-zfs -i $mbrindex $setsize ${disk}s1 || + return $FAILURE + f_quietly zpool labelclear -f /dev/$disk$targetpart # Pedantic + + # + # 5. Add freebsd-swap partition + # + if [ $swapsize -gt 0 ]; then + gpart add -t freebsd-swap -i 2 ${disk}s1 || + return $FAILURE + # Update fstab(5) + printf "$fstab_fmt" /dev/${disk}s1b none swap sw 0 0 \ + >> $BSDINSTALL_TMPETC/fstab || return $FAILURE + fi + ;; + + *) + printf "%s: %s is an unsupported partition scheme" \ + "$funcname" "$ZFSBOOT_PARTITION_SCHEME" >&2 + return $FAILURE + + esac # $ZFSBOOT_PARTITION_SCHEME + + return $SUCCESS +} + +# zfs_create_boot $poolname $vdev_type $real_disks ... +# +# Creates boot pool and dataset layout. Returns error if something goes wrong. +# Errors are printed to stderr for collection and display. +# +zfs_create_boot() +{ + local poolname="$1" vdev_type="$2" + local fstab_fmt="%s\t\t%s\t%s\t%s\t\t%s\t%s\n" + local funcname=zfs_create_boot + local bootpart targetpart + + shift 2 # name vdev_type + + # We may need this later + local realdisks=$* + + # Pedantic checks; should never be seen + if [ ! "$poolname" ]; then + echo "$funcname: NULL poolname" >&2 + return $FAILURE + fi + if [ $# -lt 1 ]; then + echo "$funcname: missing disk arguments" >&2 + return $FAILURE + fi + + # Initialize fstab(5) + printf "$fstab_fmt" \ + "# Device" Mountpoint FStype Options Dump "Pass#" \ + >> $BSDINSTALL_TMPETC/fstab || return $FAILURE + + # Expand SI units in desired sizes + local swapsize gelisize + f_expand_number "$ZFSBOOT_SWAP_SIZE" swapsize || return $FAILURE + f_expand_number "$ZFSBOOT_GELI_BOOT_SIZE" gelisize || return $FAILURE + + # Prepare the disks + local n=0 + for disk in $*; do + zfs_create_diskpart $disk $n || return $FAILURE + n=$(( $n + 1 )) + done + + # MBR boot loader hack part 1 + # We have to do this early because geli gets in the way later + if [ "$ZFSBOOT_PARTITION_SCHEME" = "MBR" ]; then + for disk in $realdisks; do + dd if=/boot/zfsboot of=/dev/${disk}s1 count=1 || + return $FAILURE + done + fi + + # Forced 4k alignment support provided by Geom NOP (see gnop(8)) + local unenc_list= + if [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ]; then + local new_list= + for disk in $*; do + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + # We don't gnop the encrypted partition + # because geli will do this for us + # gnop the unencrypted disk + gnop create -S 4096 $disk$bootpart || + return $FAILURE + unenc_list="$unenc_list $disk$bootpart.nop" + else + gnop create -S 4096 $disk$targetpart || + return $FAILURE + new_list="$new_list $disk$targetpart.nop" + fi + done + set -- $new_list + else + local new_list= + for disk in $*; do + new_list="$new_list $disk$targetpart" + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && + unenc_list="$unenc_list $disk$bootpart" + done + set -- $new_list + fi + + # + # If encryption is enabled, we need to create the GEOMs + # + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + local bootvdev= + local geli_pool="$BSDINSTALL_CHROOT/$ZFSBOOT_GELI_POOL_NAME" + local key="$ZFSBOOT_GELI_KEY_FILE" + + # Create the parent directories for our unencrypted pool + f_quietly umount /mnt + mount -t tmpfs none $BSDINSTALL_CHROOT || return $FAILURE + + # Create mirror across the unencrypted partition on all disks + [ $( set -- $unenc_list; echo $# ) -gt 1 ] && bootvdev=mirror + + zpool create -o altroot=$BSDINSTALL_CHROOT \ + -m "/$ZFSBOOT_GELI_POOL_NAME" -f \ + "$ZFSBOOT_GELI_POOL_NAME" $bootvdev $unenc_list || + return $FAILURE + mkdir -p $geli_pool/boot || return $FAILURE + + # Generate an encryption key using random(4) + dd if=/dev/random of="$geli_pool/$key" bs=4096 count=1 || + return $FAILURE + + # Create the geli(8) GEOMS + local geli_list geli_pass + local title="$DIALOG_TITLE" + local btitle="$DIALOG_BACKTITLE" + local hline="$hline_arrows_tab_enter" + eval f_dialog_buttonbox_size height width \"\$title\" \ + \"\$btitle\" \"\$msg_geli_password\" \"\$hline\" + [ $height -lt 8 ]; height=8 + geli_pass=$( eval $DIALOG \ + --title \"\$title\" \ + --backtitle \"\$btitle\" \ + --hline \"\$hline\" \ + --insecure \ + --passwordbox \"\$msg_geli_password\" \ + $height $width \ + 2>&1 >&$DIALOG_TERMINAL_PASSTHRU_FD + ) || return $FAILURE + for disk in $realdisks; do + echo "$geli_pass" | geli init -b -B \ + "$geli_pool/boot/$disk$targetpart.eli" \ + -e AES-XTS -J - -K "$geli_pool/$key" -l 256 \ + -s 4096 $disk$targetpart || return $FAILURE + echo "$geli_pass" | geli attach -j - \ + -k "$geli_pool/$key" $disk$targetpart || + return $FAILURE + geli_list="$geli_list $disk$targetpart.eli" + done + set -- $geli_list + zfs unmount "$ZFSBOOT_GELI_POOL_NAME" || return $FAILURE + # We don't need this anymore + f_quietly umount /mnt + fi + + # + # Create the ZFS pool with desired type and disk devices + # + zpool create -o altroot=$BSDINSTALL_CHROOT -m none -f \ + "$poolname" $vdev_type $* || return $FAILURE + + # Customize the zpool a bit... + zfs set checksum=fletcher4 "$poolname" || return $FAILURE + zfs set atime=off "$poolname" || return $FAILURE + + # + # Create ZFS dataset layout within the new boot pool + # + echo "$ZFSBOOT_DATASETS" | while read dataset options; do + # Skip blank lines and comments + case "$dataset" in "#"*|"") continue; esac + # Remove potential inline comments in options + options="${options%%#*}" + # Replace tabs with spaces + f_replaceall "$options" " " " " foo + # Reduce contiguous runs of space to one single space + oldoptions= + while [ "$oldoptions" != "$options" ]; do + oldoptions="$options" + f_replaceall "$options" " " " " options + done + # Replace both commas and spaces with ` -o ' + f_replaceall "$options" "[ ,]" " -o " options + # Create the dataset with desired options + zfs create ${options:+-o $options} "$poolname$dataset" || + return $FAILURE + done + + # Touch up permissions on the tmp directories + chmod 1777 $BSDINSTALL_CHROOT/tmp || return $FAILURE + chmod 1777 $BSDINSTALL_CHROOT/var/tmp || return $FAILURE + + # Create symlink(s) + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && + { ln -s $ZFSBOOT_GELI_POOL_NAME/boot $BSDINSTALL_CHROOT/boot || + return $FAILURE; } + + # Set bootfs property + zpool set bootfs="$poolname/$ZFSBOOT_BEROOT_NAME/$ZFSBOOT_BOOTFS_NAME" \ + "$poolname" || return $FAILURE + + # Export the pool(s) + zpool export "$poolname" || return $FAILURE + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && + { zpool export "$ZFSBOOT_GELI_POOL_NAME" || return $FAILURE; } + + # Destroy the gnop devices (if enabled) + for disk in ${ZFSBOOT_GNOP_4K_FORCE_ALIGN:+$realdisks}; do + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + f_quietly gnop destroy $disk$bootpart.nop + else + f_quietly gnop destroy $disk$targetpart.nop + fi + done + + # MBR boot loader hack part 2 + if [ "$ZFSBOOT_PARTITION_SCHEME" = "MBR" ]; then + # Stick the ZFS boot loader in the "convienient hole" after + # the ZFS internal metadata + for disk in $realdisks; do + dd if=/boot/zfsboot of=/dev/$disk$bootpart \ + skip=1 seek=1024 || return $FAILURE + done + fi + + # Re-import the ZFS pool(s) + zpool import -o altroot=$BSDINSTALL_CHROOT $poolname || return $FAILURE + [ "$ZFSBOOT_GELI_ENCRYPTION" ] && + { zpool import -o altroot=$BSDINSTALL_CHROOT \ + "$ZFSBOOT_GELI_POOL_NAME" || return $FAILURE; } + + # While this is apparently not needed, it seems to help MBR + mkdir -p $BSDINSTALL_CHROOT/boot/zfs || return $FAILURE + zpool set cachefile=$BSDINSTALL_CHROOT/boot/zfs/zpool.cache \ + "$poolname" || return $FAILURE + + # Last, but not least... add required lines to rc.conf(5) + # NOTE: We later concatenate these into their destination + echo 'zfs_enable="YES"' > $BSDINSTALL_TMPETC/rc.conf.zfs || + return $FAILURE + echo 'zfs_load="YES"' > $BSDINSTALL_TMPBOOT/loader.conf.zfs || + return $FAILURE + + # We're all done unless we should go on to do encryption + [ "$ZFSBOOT_GELI_ENCRYPTION" ] || return $SUCCESS + + # + # Configure geli(8)-based encryption + # + echo 'aesni_load="YES"' \ + > $BSDINSTALL_TMPBOOT/loader.conf.aesni || return $FAILURE + echo 'geom_eli_load="YES"' \ + > $BSDINSTALL_TMPBOOT/loader.conf.geli || return $FAILURE + printf 'vfs.root.mountfrom="zfs:%s/%s/%s"\n' "$poolname" \ + "$ZFSBOOT_BEROOT_NAME" "$ZFSBOOT_BOOTFS_NAME" \ + > $BSDINSTALL_TMPBOOT/loader.conf.root || return $FAILURE + for disk in $realdisks; do + printf 'geli_%s_keyfile0_load="YES"\n' \ + "$disk$targetpart" \ + > $BSDINSTALL_TMPBOOT/loader.conf.$disk$targetpart || + return $FAILURE + printf 'geli_%s_keyfile0_type="%s:geli_keyfile0"\n' \ + "$disk$targetpart" "$disk$targetpart" \ + >> $BSDINSTALL_TMPBOOT/loader.conf.$disk$targetpart || + return $FAILURE + printf 'geli_%s_keyfile0_name="%s"\n' \ + "$disk$targetpart" "$ZFSBOOT_GELI_KEY_FILE" \ + >> $BSDINSTALL_TMPBOOT/loader.conf.$disk$targetpart || + return $FAILURE + done + + return $SUCCESS +} + +# dialog_menu_diskinfo +# +# Prompt the user to select a disk and then provide detailed info on it. +# +dialog_menu_diskinfo() +{ + local disk + + # + # Break from loop when user cancels disk selection + # + while :; do + disk=$( msg_cancel="$msg_back" f_device_menu \ + "$DIALOG_TITLE" "$msg_select_a_disk_device" "" \ + $DEVICE_TYPE_DISK 2>&1 ) || break + + # Show gpart(8) `show' and camcontrol(8) `inquiry' data + f_show_msg "$msg_detailed_disk_info" \ + "$disk" "$( gpart show $disk 2> /dev/null )" \ + "$disk" "$( camcontrol inquiry $disk 2> /dev/null )" \ + "$disk" "$( camcontrol identify $disk 2> /dev/null )" + done + + return $SUCCESS +} + +############################################################ MAIN + +# +# Initialize +# +f_dialog_title "$msg_zfs_configuration" +f_dialog_backtitle "$msg_freebsd_installer" + +# +# Loop over the main menu until we've accomplished what we came here to do +# +while :; do + dialog_menu_main + retval=$? + f_dialog_menutag_fetch mtag + f_dprintf "retval=%u mtag=[%s]" $reval "$mtag" + + [ $retval -eq $DIALOG_OK ] || f_die + + case "$mtag" in + ">>> $msg_create") + # + # First, validate the user's selections + # + + # Make sure they gave us a name for the pool + if [ ! "$ZFSBOOT_POOL_NAME" ]; then + f_show_msg "$msg_pool_name_cannot_be_empty" + continue + fi + # Make sure [potentially scripted] selections are real + real_disks= + for disk in $ZFSBOOT_DISKS; do + f_struct device_$disk && real_disks="$real_disks $disk" + done + # Make sure we have at least one real disk selected + ndisks=$( set -- $real_disks; echo $# ) + if [ $ndisks -lt 1 ]; then + f_show_msg "$msg_no_disks_selected" + continue + fi + # Make sure we have enough disks for the desired vdev type + case "$ZFSBOOT_VDEV_TYPE" in + stripe) want_disks=1 ;; + mirror) want_disks=2 ;; + raidz1) want_disks=3 ;; + raidz2) want_disks=4 ;; + raidz3) want_disks=5 ;; + *) + f_show_msg "$msg_invalid_virtual_device_type" \ + "$ZFSBOOT_VDEV_TYPE" + continue + ;; + esac + if [ $ndisks -lt $want_disks ]; then + f_show_msg "%s: $msg_not_enough_disks_selected" \ + "$ZFSBOOT_VDEV_TYPE" "$want_disks" + continue + fi + + # + # Last Chance! + # + if [ ! "$USE_XDIALOG" ]; then + DIALOG="$DIALOG --colors" f_noyes \ + "$msg_last_chance_are_you_sure_color" \ + "$ZFSBOOT_DISKS" || continue + else + f_noyes "$msg_last_chance_are_you_sure" \ + "$ZFSBOOT_DISKS" || continue + fi + + # + # Let's do this + # + + vdev_type="$ZFSBOOT_VDEV_TYPE" + + # Blank the vdev type for the default layout + [ "$vdev_type" = "stripe" ] && vdev_type= + + if ! error=$( zfs_create_boot "$ZFSBOOT_POOL_NAME" \ + "$vdev_type" $real_disks 2>&1 ) + then + f_dialog_msgbox "$error" + continue + fi + + break # to success + ;; + "- $msg_rescan_devices") f_device_rescan ;; + "- $msg_disk_info") dialog_menu_diskinfo ;; + ?" $msg_pool_name") + # Prompt the user to input/change the name for the new pool + f_dialog_input input \ + "$msg_please_enter_a_name_for_your_zpool" \ + "$ZFSBOOT_POOL_NAME" && + ZFSBOOT_POOL_NAME="$input" + ;; + ?" $msg_disks_to_use") dialog_edit_disks ;; + ?" $msg_zfs_vdev_type") dialog_menu_vdev ;; + ?" $msg_force_4k_sectors") + # Toggle the variable referenced both by the menu and later + if [ "$ZFSBOOT_GNOP_4K_FORCE_ALIGN" ]; then + ZFSBOOT_GNOP_4K_FORCE_ALIGN= + else + ZFSBOOT_GNOP_4K_FORCE_ALIGN=1 + fi + ;; + ?" $msg_geli_encryption") + # Toggle the variable referenced both by the menu and later + if [ "$ZFSBOOT_GELI_ENCRYPTION" ]; then + ZFSBOOT_GELI_ENCRYPTION= + else + ZFSBOOT_GELI_ENCRYPTION=1 + fi + ;; + ?" $msg_partition_scheme") + # Toggle between GPT and MBR + if [ "$ZFSBOOT_PARTITION_SCHEME" = GPT ]; then + ZFSBOOT_PARTITION_SCHEME=MBR + else + ZFSBOOT_PARTITION_SCHEME=GPT + fi + ;; + ?" $msg_swap_size") + # Prompt the user to input/change the swap size for each disk + f_dialog_input input \ + "$msg_please_enter_amount_of_swap_space" \ + "$ZFSBOOT_SWAP_SIZE" && + ZFSBOOT_SWAP_SIZE="$input" + ;; + esac +done + +return $SUCCESS + +################################################################################ +# END +################################################################################ Property changes on: usr.sbin/bsdinstall/scripts/zfsboot ___________________________________________________________________ Added: svn:executable ## -0,0 +1 ## +* \ No newline at end of property --------------090500090706010405000101-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 03:10:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 44B899F2; Thu, 10 Oct 2013 03:10:53 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 1D76628DE; Thu, 10 Oct 2013 03:10:53 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 53A771EB2E; Thu, 10 Oct 2013 03:10:52 +0000 (UTC) Message-ID: <52561AD6.9070807@allanjude.com> Date: Wed, 09 Oct 2013 23:11:18 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "Teske, Devin" Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4B3F2@LTCFISWMSGMB21.FNFIS.com> <525596A7.2090701@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4B907@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC4B907@LTCFISWMSGMB21.FNFIS.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Devin Teske , "" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 03:10:53 -0000 On 2013-10-09 14:14, Teske, Devin wrote: > On Oct 9, 2013, at 10:47 AM, Allan Jude wrote: > >> On 2013-10-09 13:21, Teske, Devin wrote: >>> On Oct 8, 2013, at 8:49 PM, Allan Jude wrote: >>> >>>> On 2013-10-07 15:59, Allan Jude wrote: >>>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>>>> sector gnop trick, and optional GELI encryption. We would like to commit >>>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>>> obvious bugs before we send it off to re@ to get it committed. >>>>> >>>>> It includes a single configuration menu that allows you to select all of >>>>> the required details, including which drives to use (gets details from >>>>> camcontrol, also includes an inspection utility that presents the >>>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>>> ZFS RAID level to use (taking in to consideration the selected number of >>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>> >>>>> >>>>> Additional, it includes some other changes to bsdinstall: >>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>>> feature has been combined into the regular 'services to enable' dialog >>>>> and enabled by default >>>>> >>>>> >>>>> You can browse the patches here: >>>>> https://urldefense.proofpoint.com/v1/url?u=http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=oPEdrpFUFqEutq%2B7DHGyBIA0gTt5%2BZ6FWvbN6q4bjm4%3D%0A&s=32f69a33d9c98c63ecf3962b89eea0af631f5a2fd6e82b55afb6ec139f3f803d >>>>> >>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>> >>>>> https://urldefense.proofpoint.com/v1/url?u=http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=oPEdrpFUFqEutq%2B7DHGyBIA0gTt5%2BZ6FWvbN6q4bjm4%3D%0A&s=fd0f3ed623f12c8cb5eee607cf82122523a0800ab9f5624cb3f77ae2646e1b1b >>>>> >>>>> https://urldefense.proofpoint.com/v1/url?u=http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=LTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=oPEdrpFUFqEutq%2B7DHGyBIA0gTt5%2BZ6FWvbN6q4bjm4%3D%0A&s=fa49aaa528513a591ac40a2f0c5666abae2d7269bd66ac70d7100475a9574300 >>>>> >>>>> >>>>> We look forward to your feedback >>>>> >>>> We've made more improvements, including corporating most all of the >>>> feedback we've gotten so far >>>> >>>> >>>> Outstanding items: >>>> 1. Apply the changes to ipv6 config the way we did ipv4 >>>> 2. improve disk identification (model info and serial # instead of one >>>> or the other) >>>> 3. Include a helpful message before the GELI step where you have to >>>> enter your password many times, the user will be less confused if it is >>>> explained why they have to enter their password 3 * number of disks times >>> I'm hopeful that we can script the application of a password that we >>> first prompt for. >>> >>> What tool is prompting for a password? Can we not just provide an answer >>> on stdin? (e.g., echo "$pass" | tool_that_needs_pass) >>> >> It is 'geli create' and 'geli attach'. I am not sure if we want to have >> the password show up in the process list (obviously in the installer >> this is less of an issue, but) >> > It won't. > > echo is a shell built-in. > > If we're uber paranoid... we prefix the word "builtin"; e.g.,... > > builtin echo "$pass" | tool_that_needs_pass > > You'll see the tool in ps, but you won't see the echo (that's part of the > shell invocation -- all you see in ps is an instance of sh). > I have implemented this, 'geli init' takes the -J flag, which can be set to - to mean stdin. 'geli attach' is the same except the flag is -j I first prompt for the password with a dialog --passwordbox, so the user only has to enter it once Do we think it makes sense to prompt the user twice, and confirm the two entered passphrases are the same? > >>>> 4. Validate vdev type choice inside the vdev type menu, and warn the >>>> user if they have made an invalid selection, so they can add more disks >>>> or chance their selection, without having to try to start the >>>> installation first >>> This will be done with fanciness ;D (read: ... --and-widget --infobox ... and >>> sundry smartness; retaining as much as possible the ability to do things >>> out of order but never arise at a point of astonishment). >>> >> I don't think we need --and-widget, just in the function where we apply >> the results of the menu selection, > The purpose of --and-widget with an --infobox is to let the user know that > validation is occurring each/every time they make a selection. > > Seeing the infobox before being returned to the previous menu (in the case > of selecting a valid vdev_type) is to cement in the mind of the user that their > selection was validated. Of course, in the case of an invalid selection, they > get a message box. What the message box says depends on: > > 1. Are they trying to select a vdev_type for which they don't have enough > devices? Tell them that they don't have enough devices, and bring them > back to the vdev_type menu (to select a different [valid] vdev type *or* > cancel and go back to the ZFS menu where they can optionally Rescan > for more devices -- allowing that vdev_type to be selected without issue). > In the prompt that tells them that they don't have enough disks in their > system to select that vdev_type, we sould hint that they can choose cancel > and go back to use the "Rescan" option to scan for more devices. > > 2. Are they trying to select a vdev_type for which they have enough devices > but have not yet made enough selections? Drop them back to the ZFS menu > so they can go select the appropriate number of devices. > > Good? > I kind of shortened it a bit. When you make a selection in the vdev submenu, if your selection is invalid you get a --yesno box explaining that 'type requires disks'. And are prompted to either 'choose again' (back to the vdev menu) or 'return to the zfs menu' (to select more disks) >> we can add a regular --msgbox telling >> them that their config won't work, and they need to either select more >> drives or a different vdev type >> > I agree on the msgbox -- and I still think the temporaneous infobox > injected via --and-widget would be value-add. > > Question is what to do after the msgbox. > > I posit that if the vdev_type is valid but they don't have enough disks > currently selected, that they be tossed back at the ZFS menu. However, > if they instead select a vdev_type which couldn't possible be satisfied > given the number of devices available to the hardware... keep them > in the vdev_type menu. > > >>>> 5. Whatever else you guys find wrong tonight >>>> >>>> I generated new test images, and attached the patch (which got REALLY >>>> big when Devin Teske decided to fix "all of the things": >>>> >>> And then I merged "all of the things" into HEAD, so the patch-set shrunk >>> back to its normal size. Now we have global exit codes which will make >>> merging of code that is based off of Thomas Dickey's samples easier. >> I am glad to see all of the good ideas, and plans to make everything >> wonderful, but my biggest concern is getting this over to re@ so it can >> get in to 10.0-BETA1, the deadline for which is looming (like, tomorrow >> I think). >> > I hate to say it... but it was the netconfig and keymap changes that put us > out of our way. If anything, I'd like to see those get dropped and have us > focus on ZFS. > The netconfig changes other than Warren's wireless patch have been backed out The keymap change has been simplied down to just Warren's test system, but implemented as a menu instead of a yes/no/other box This can be redone better later >> As such, I have rolled back the patches to netconfig and netconfig_ipv4 >> (my stuff to reduce the number of dialogs to configure ipv4, it posed >> some problems with the possible usage of xdialog, and didn't actually >> offer an option to 'cancel'). I kept Warren's netconfig wireless patch >> > Cool. We're thinking along the same lines. > > >> This leaves the only real outstanding problem the keymap thing. I >> propose changing it from a yes/no/other to a --menu, and hopefully we >> can find the bug with the display name, or just make it show the keymap >> name instead. >> > Last night I started doing what I knew "had to be done". > > Just as was the case with "bsdconfig timezone" ... I literally went into > tzsetup(8) and converted the C code line-by-line to shell. (don't take > that *too* literally... swaths of optimization were applied int he process; > point being that the shell quite-ably reads the ISO3166 tables and zone > files in the same *exact* manner as tzetup). tzsetup says 'if you are not sure if your CMOS clock is in UTC, choose no', but the default in the dialog menu is not 'no'. This is wrong. I couldn't fix this because tzsetup is C not SH > I've gone into kbdmap and looked at how it parses things. > > No biggie... looks like INDEX.keymaps (whose suffix matches the directory > he lives in) is nothing more than a colon-delimited 3-field syntax with leading > whitespace chopped and a comment-character of "#". Nothing a trival awk(1) > script couldn't handle. > > To make things cute... I've got the code parsing into a shell structs (the same > way I parse dhclient.leases and other file formats). By having an awk script > read the file and generate shell statements that in-turn load the data into the > exigent namespace. > > I'll see what I can get in ASAP. If you can work something out, great. I fixed it 'good enough' for now -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 04:04:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B0D186B6; Thu, 10 Oct 2013 04:04:25 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 72C922B50; Thu, 10 Oct 2013 04:04:25 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa03.fnfis.com (8.14.5/8.14.5) with ESMTP id r9A44HaL022116 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 9 Oct 2013 23:04:17 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Wed, 9 Oct 2013 23:04:16 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxRQPPJPIP8ZCyUiSsjBzr2++AA== Date: Thu, 10 Oct 2013 04:04:15 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4DCD1@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <5254D231.5070803@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4B3F2@LTCFISWMSGMB21.FNFIS.com> <525596A7.2090701@allanjude.com> <13CA24D6AB415D428143D44749F57D720FC4B907@LTCFISWMSGMB21.FNFIS.com> <52561AD6.9070807@allanjude.com> In-Reply-To: <52561AD6.9070807@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-10_01:2013-10-09,2013-10-10,1970-01-01 signatures=0 Cc: Devin Teske , "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 04:04:25 -0000 On Oct 9, 2013, at 8:11 PM, Allan Jude wrote: > On 2013-10-09 14:14, Teske, Devin wrote: >> On Oct 9, 2013, at 10:47 AM, Allan Jude wrote: >>=20 >>> On 2013-10-09 13:21, Teske, Devin wrote: >>>> On Oct 8, 2013, at 8:49 PM, Allan Jude wrote: >>>>=20 >>>>> On 2013-10-07 15:59, Allan Jude wrote: >>>>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>>>> implement installing on a ZFS pool. It supports both GPT and MBR, th= e 4k >>>>>> sector gnop trick, and optional GELI encryption. We would like to co= mmit >>>>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>>>> obvious bugs before we send it off to re@ to get it committed. >>>>>>=20 >>>>>> It includes a single configuration menu that allows you to select al= l of >>>>>> the required details, including which drives to use (gets details fr= om >>>>>> camcontrol, also includes an inspection utility that presents the >>>>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>>>> ZFS RAID level to use (taking in to consideration the selected numbe= r of >>>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>>>=20 >>>>>>=20 >>>>>> Additional, it includes some other changes to bsdinstall: >>>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt = to no >>>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with = just 1 >>>>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>>>> feature has been combined into the regular 'services to enable' dial= og >>>>>> and enabled by default >>>>>>=20 >>>>>>=20 >>>>>> You can browse the patches here: >>>>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>>>=20 >>>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>>>=20 >>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>>>=20 >>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>>>=20 >>>>>>=20 >>>>>> We look forward to your feedback >>>>>>=20 >>>>> We've made more improvements, including corporating most all of the >>>>> feedback we've gotten so far >>>>>=20 >>>>>=20 >>>>> Outstanding items: >>>>> 1. Apply the changes to ipv6 config the way we did ipv4 >>>>> 2. improve disk identification (model info and serial # instead of one >>>>> or the other) >>>>> 3. Include a helpful message before the GELI step where you have to >>>>> enter your password many times, the user will be less confused if it = is >>>>> explained why they have to enter their password 3 * number of disks t= imes >>>> I'm hopeful that we can script the application of a password that we >>>> first prompt for. >>>>=20 >>>> What tool is prompting for a password? Can we not just provide an answ= er >>>> on stdin? (e.g., echo "$pass" | tool_that_needs_pass) >>>>=20 >>> It is 'geli create' and 'geli attach'. I am not sure if we want to have >>> the password show up in the process list (obviously in the installer >>> this is less of an issue, but) >>>=20 >> It won't. >>=20 >> echo is a shell built-in. >>=20 >> If we're uber paranoid... we prefix the word "builtin"; e.g.,... >>=20 >> builtin echo "$pass" | tool_that_needs_pass >>=20 >> You'll see the tool in ps, but you won't see the echo (that's part of the >> shell invocation -- all you see in ps is an instance of sh). >>=20 > I have implemented this, 'geli init' takes the -J flag, which can > be set to - to mean stdin. 'geli attach' is the same except the flag is -j >=20 > I first prompt for the password with a dialog --passwordbox, so the user > only has to enter it once >=20 > Do we think it makes sense to prompt the user twice, and confirm the two > entered passphrases are the same? >=20 I think so. I'm afraid someone could make a typo and then not be able to log into their system because the password that was actually used is different than what the user thinks it is. >=20 >>=20 >>>>> 4. Validate vdev type choice inside the vdev type menu, and warn the >>>>> user if they have made an invalid selection, so they can add more dis= ks >>>>> or chance their selection, without having to try to start the >>>>> installation first >>>> This will be done with fanciness ;D (read: ... --and-widget --infobox = ... and >>>> sundry smartness; retaining as much as possible the ability to do thin= gs >>>> out of order but never arise at a point of astonishment). >>>>=20 >>> I don't think we need --and-widget, just in the function where we apply >>> the results of the menu selection, >> The purpose of --and-widget with an --infobox is to let the user know th= at >> validation is occurring each/every time they make a selection. >>=20 >> Seeing the infobox before being returned to the previous menu (in the ca= se >> of selecting a valid vdev_type) is to cement in the mind of the user tha= t their >> selection was validated. Of course, in the case of an invalid selection,= they >> get a message box. What the message box says depends on: >>=20 >> 1. Are they trying to select a vdev_type for which they don't have enough >> devices? Tell them that they don't have enough devices, and bring them >> back to the vdev_type menu (to select a different [valid] vdev type *or* >> cancel and go back to the ZFS menu where they can optionally Rescan >> for more devices -- allowing that vdev_type to be selected without issue= ). >> In the prompt that tells them that they don't have enough disks in their >> system to select that vdev_type, we sould hint that they can choose canc= el >> and go back to use the "Rescan" option to scan for more devices. >>=20 >> 2. Are they trying to select a vdev_type for which they have enough devi= ces >> but have not yet made enough selections? Drop them back to the ZFS menu >> so they can go select the appropriate number of devices. >>=20 >> Good? >>=20 >=20 > I kind of shortened it a bit. When you make a selection in the vdev > submenu, if your selection is invalid you get a --yesno box explaining > that 'type requires disks'. And are prompted to either > 'choose again' (back to the vdev menu) or 'return to the zfs menu' (to > select more disks) >=20 Nice. >>> we can add a regular --msgbox telling >>> them that their config won't work, and they need to either select more >>> drives or a different vdev type >>>=20 >> I agree on the msgbox -- and I still think the temporaneous infobox >> injected via --and-widget would be value-add. >>=20 >> Question is what to do after the msgbox. >>=20 >> I posit that if the vdev_type is valid but they don't have enough disks >> currently selected, that they be tossed back at the ZFS menu. However, >> if they instead select a vdev_type which couldn't possible be satisfied >> given the number of devices available to the hardware... keep them >> in the vdev_type menu.=20 >>=20 >>=20 >>>>> 5. Whatever else you guys find wrong tonight >>>>>=20 >>>>> I generated new test images, and attached the patch (which got REALLY >>>>> big when Devin Teske decided to fix "all of the things": >>>>>=20 >>>> And then I merged "all of the things" into HEAD, so the patch-set shru= nk >>>> back to its normal size. Now we have global exit codes which will make >>>> merging of code that is based off of Thomas Dickey's samples easier. >>> I am glad to see all of the good ideas, and plans to make everything >>> wonderful, but my biggest concern is getting this over to re@ so it can >>> get in to 10.0-BETA1, the deadline for which is looming (like, tomorrow >>> I think). >>>=20 >> I hate to say it... but it was the netconfig and keymap changes that put= us >> out of our way. If anything, I'd like to see those get dropped and have = us >> focus on ZFS. >>=20 > The netconfig changes other than Warren's wireless patch have been > backed out >=20 > The keymap change has been simplied down to just Warren's test system, > but implemented as a menu instead of a yes/no/other box >=20 > This can be redone better later >=20 Or... how about *now*? I'm committing the completely reworked keymap code as I type this. >>> As such, I have rolled back the patches to netconfig and netconfig_ipv4 >>> (my stuff to reduce the number of dialogs to configure ipv4, it posed >>> some problems with the possible usage of xdialog, and didn't actually >>> offer an option to 'cancel'). I kept Warren's netconfig wireless patch >>>=20 >> Cool. We're thinking along the same lines. >>=20 >>=20 >>> This leaves the only real outstanding problem the keymap thing. I >>> propose changing it from a yes/no/other to a --menu, and hopefully we >>> can find the bug with the display name, or just make it show the keymap >>> name instead. >>>=20 >> Last night I started doing what I knew "had to be done". >>=20 >> Just as was the case with "bsdconfig timezone" ... I literally went into >> tzsetup(8) and converted the C code line-by-line to shell. (don't take >> that *too* literally... swaths of optimization were applied int he proce= ss; >> point being that the shell quite-ably reads the ISO3166 tables and zone >> files in the same *exact* manner as tzetup). > tzsetup says 'if you are not sure if your CMOS clock is in UTC, choose > no', but the default in the dialog menu is not 'no'. This is wrong. I > couldn't fix this because tzsetup is C not SH >=20 Well, no longer the case anymore ;D Does that still need fixing? (maybe not right now; let's stay focused) >> I've gone into kbdmap and looked at how it parses things. >>=20 >> No biggie... looks like INDEX.keymaps (whose suffix matches the directory >> he lives in) is nothing more than a colon-delimited 3-field syntax with = leading >> whitespace chopped and a comment-character of "#". Nothing a trival awk(= 1) >> script couldn't handle. >>=20 >> To make things cute... I've got the code parsing into a shell structs (t= he same >> way I parse dhclient.leases and other file formats). By having an awk sc= ript >> read the file and generate shell statements that in-turn load the data i= nto the >> exigent namespace. >>=20 >> I'll see what I can get in ASAP. > If you can work something out, great. I fixed it 'good enough' for now >=20 Committing now. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 04:42:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 19ED8EBB for ; Thu, 10 Oct 2013 04:42:43 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id D332D2D6F for ; Thu, 10 Oct 2013 04:42:42 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:49945] helo=localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 60/25-01315-14036525; Thu, 10 Oct 2013 04:42:41 +0000 Date: Thu, 10 Oct 2013 04:42:41 +0000 Message-ID: <60.25.01315.14036525@cdptpa-oedge03> From: "Thomas Mueller" <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> <52558779.2070203@pcbsd.org> <517D65A3D61F684FAE2B2EC2D2DA06C3@fisglobal.com> <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 Cc: "Teske, Devin" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 04:42:43 -0000 from Devin Teske: > I'm late to the party again ;D (didn't realize the rcs thread had turned BE) > Both problems can be solved. > The loading of the kernel *after* choosing your boot device is trivial. > We've been doing it at $work for *years* (almost a decade?) > I can put that in, whenever. Probably at the same time as implementing > the live/dynamic BE menus for selecting the root device. I'd like to know how to boot FreeBSD >= 9.1 with grub2. Following the instructions under $PORTSDIR/sysutils/grub2 insmod ufs2 set root=(hd0,gpt3) kfreebsd /boot/loader boot stopped working around FreeBSD 9.1-stable. I used Super Grub2 Disk image on the System Rescue CD written to USB stick. Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the System Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but haven't tested that yet. What is the method you or PC-BSD uses? I want to use it on FreeBSD 9.2 and 10-current. I tried visiting pcbsd.org website but couldn't find any details. Tom From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 04:47:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 14EE191 for ; Thu, 10 Oct 2013 04:47:42 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id CBE9A2D99 for ; Thu, 10 Oct 2013 04:47:41 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:51741] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 59/81-16944-C6136525; Thu, 10 Oct 2013 04:47:41 +0000 Date: Thu, 10 Oct 2013 04:47:40 +0000 Message-ID: <59.81.16944.C6136525@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: BE Loader Menu (was Re: rcs) References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> <52558779.2070203@pcbsd.org> <517D65A3D61F684FAE2B2EC2D2DA06C3@fisglobal.com> <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Cc: "Teske, Devin" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 04:47:42 -0000 Sorry for previous typo in From: line, missing right angle bracket at end. Then, in a finger error, I resent that message just before finding the error and making the needed correction. from Devin Teske: > I'm late to the party again ;D (didn't realize the rcs thread had turned BE) > Both problems can be solved. > The loading of the kernel *after* choosing your boot device is trivial. > We've been doing it at $work for *years* (almost a decade?) > I can put that in, whenever. Probably at the same time as implementing > the live/dynamic BE menus for selecting the root device. I'd like to know how to boot FreeBSD >= 9.1 with grub2. Following the instructions under $PORTSDIR/sysutils/grub2 insmod ufs2 set root=(hd0,gpt3) kfreebsd /boot/loader boot stopped working around FreeBSD 9.1-stable. I used Super Grub2 Disk image on the System Rescue CD written to USB stick. Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the System Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but haven't tested that yet. What is the method you or PC-BSD uses? I want to use it on FreeBSD 9.2 and 10-current. I tried visiting pcbsd.org website but couldn't find any details. Tom From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 07:00:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 97C1D377 for ; Thu, 10 Oct 2013 07:00:57 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth2.wiscmail.wisc.edu (wmauth2.doit.wisc.edu [144.92.197.222]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 66CDF2413 for ; Thu, 10 Oct 2013 07:00:56 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MUF00600XO4EF00@smtpauth2.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Thu, 10 Oct 2013 02:00:49 -0500 (CDT) X-Spam-PmxInfo: Server=avs-2, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.10.10.65114, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (unknown [140.105.20.242]) by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MUF00APBY5B9P20@smtpauth2.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Thu, 10 Oct 2013 02:00:49 -0500 (CDT) Message-id: <5256509E.3000604@freebsd.org> Date: Thu, 10 Oct 2013 09:00:46 +0200 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> <5254F582.1040406@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> In-reply-to: <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> X-Enigmail-Version: 1.5.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 07:00:57 -0000 On 10/09/13 18:55, Teske, Devin wrote: > On Oct 8, 2013, at 11:19 PM, Nathan Whitehorn wrote: > >> On 10/09/13 01:13, Allan Jude wrote: >>> On 2013-10-08 16:17, Nathan Whitehorn wrote: >>>> On 10/07/13 21:59, Allan Jude wrote: >>>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>>>> sector gnop trick, and optional GELI encryption. We would like to commit >>>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>>> obvious bugs before we send it off to re@ to get it committed. >>>>> >>>>> It includes a single configuration menu that allows you to select all of >>>>> the required details, including which drives to use (gets details from >>>>> camcontrol, also includes an inspection utility that presents the >>>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>>> ZFS RAID level to use (taking in to consideration the selected number of >>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>> >>>>> >>>>> Additional, it includes some other changes to bsdinstall: >>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>>> feature has been combined into the regular 'services to enable' dialog >>>>> and enabled by default >>>>> >>>>> >>>>> You can browse the patches here: >>>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>> >>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>> >>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>> >>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>> >>>>> >>>>> We look forward to your feedback >>>>> >>>> Thanks for doing this! I had a few comments: >>>> 1. ZFS is not bootable on all architectures. Could you adjust that menu >>>> item to only display for i386, amd64, and (I think?) sparc64. Use uname >>>> -m, not -p, for this. >>> I had not considered that, I'll make that change >>> >>>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>>> instead of GPT. >>> I'll disable sparc64 as well >>> >>>> 2. Why are you using camcontrol? That is guaranteed not to work on >>>> non-CAM systems. You should use the GEOM ident string if you need an ID. >>> The GEOM ident string doesn't do enough to help the user identify which >>> drive is which. >>> More data is not exposed anywhere that I could find >>> >>> What we really need, is dev.ada.0.desc% like we have for network >>> interfaces and a slew of other devices. GEOM data is great, but it is >>> not exposed in a shell friendly way any place that I could find, other >>> than the sysctl with DOT and XML data. >> This is one of the reasons the partition editor is written in C. There >> are a few other odd corner-cases where C is much more powerful than the >> command-line for the GEOM operations that partedit needs to do. I'm not >> sure how to usefully get it just from the shell. You can see how to do >> it in C in the boot_disk() routine of partedit/auto_part.c. >> >>>> 3. Any plans to integrate this into the regular partition editor? ZFS >>>> support is important enough that I will definitely not get in the way, >>>> even as a bolt-on, but it would be a shame for it to stay that way. The >>>> editor is also designed for ZFS to be added. >>> I am a sysadmin, not a programmer. I can't write C. Most people >>> deploying servers can't write C. I agree with Devin Teske, if everything >>> was in shell it would be a lot more usable for non-developers, who >>> probably make up the majority of people who deploy FreeBSD. >> There are some cases the other way too. Devin is probably the most >> shell-proficient FreeBSD committer. > Well, there's jilles ;D (he writes/maintains the sh(1) implementation itself). > > >> I certainly can't write shell >> scripts at that level, which means that for me bsdconfig, for example, >> is effectively read-only (and quite hard to read as well). > In the past few days of working on the bsdinstall_zfs patch-set with Allan > Jude, I learned something new actually. > > It seems that sh(1) doesn't suffer so much from this "read only" concept. > > Imagine you're starting a new C project on an operating system that has > all new syscalls and all new APIs that you've never seen. Would be pretty > hard, no doubt. Now imagine that you're thrown a life-line called POSIX > and hey, now you're slinging code in MinGW on Windows when you don't > know a lick of M$ syscalls or APIs. > > In a similar manner, I've witnessed functionality be added that is truly > functional *without* using any of the API calls. Then I come in and do > a round of optimizations to leverage the existing API. > > Shell is kinda like that... > > I'm noticing Allan Jude doesn't know all the API calls yet (who could? other > than me of course -- and even I have trouble remembering them _all_) yet > this doesn't phase him (or others) from jumping in and lending a hand. > > No different than C, but the read-only aspect is lessened significantly I > believe because there are so many people out there that know enough > good shell syntax and are just a stone's throw away from *great* shell > syntax (which I must admit jilles helped me cross that boundary). > > I think in C, the read-only aspect is greater because its harder to parcel-out > the functions for a unit-test; harder to inject new code; and harder to get > to a functioning end-state. Look, I have no doubt that in the right hands shell can do amazing things and C can be badly written. That isn't the issue though. My statement was purely that most FreeBSD developers (me included) are more comfortable with C than shell when used at the kind of level involved here. This is not a value judgment but a statement of fact. Whether or not, at some platonic level, shell or C or python or whatever are more or less read-only is not the point here. The point is that I, and I suspect many other developers, cannot write (or read) very advanced levels of shell scripting but can read and write the equivalent programs when written in C in many cases. It's what the rest of the system is written in and what we spend most of our time using. Whether this should be the case or not is immaterial; the fact remains that shell scripting at any but a very basic level does introduce a very large barrier to entry for probably a large majority of committers. This is not always a problem -- especially if using something more obscure allows very active development by the set of people working on it -- but does reduce the set of people who can make modifications substantially. I have no ability to change, or understand, most of bsdconfig, for example. This isn't a problem since you are doing all the work and there is no reason I would need to or want to make changes to it. But it could become a problem in a part of the system to which multiple people needed to contribute. It's about other people's comfort zones and knowledge in the end. -Nathan From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 07:04:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1AB2B6A8; Thu, 10 Oct 2013 07:04:23 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D83D9244B; Thu, 10 Oct 2013 07:04:22 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r9A74Bs1009470 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 10 Oct 2013 02:04:21 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Thu, 10 Oct 2013 02:04:10 -0500 From: "Teske, Devin" To: Nathan Whitehorn Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxRBPPJPIP8ZCyUiSsjBzr2++AA== Date: Thu, 10 Oct 2013 07:04:10 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC4E9E0@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> <5254F582.1040406@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> <5256509E.3000604@freebsd.org> In-Reply-To: <5256509E.3000604@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <15ADE5C3D284424EBFA83AF5953AE14C@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-10_03:2013-10-09,2013-10-10,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 07:04:23 -0000 On Oct 10, 2013, at 12:00 AM, Nathan Whitehorn wrote: > On 10/09/13 18:55, Teske, Devin wrote: >> On Oct 8, 2013, at 11:19 PM, Nathan Whitehorn wrote: >>=20 >>> On 10/09/13 01:13, Allan Jude wrote: >>>> On 2013-10-08 16:17, Nathan Whitehorn wrote: >>>>> On 10/07/13 21:59, Allan Jude wrote: >>>>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>>>> implement installing on a ZFS pool. It supports both GPT and MBR, th= e 4k >>>>>> sector gnop trick, and optional GELI encryption. We would like to co= mmit >>>>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>>>> obvious bugs before we send it off to re@ to get it committed. >>>>>>=20 >>>>>> It includes a single configuration menu that allows you to select al= l of >>>>>> the required details, including which drives to use (gets details fr= om >>>>>> camcontrol, also includes an inspection utility that presents the >>>>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>>>> ZFS RAID level to use (taking in to consideration the selected numbe= r of >>>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>>>=20 >>>>>>=20 >>>>>> Additional, it includes some other changes to bsdinstall: >>>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt = to no >>>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with = just 1 >>>>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>>>> feature has been combined into the regular 'services to enable' dial= og >>>>>> and enabled by default >>>>>>=20 >>>>>>=20 >>>>>> You can browse the patches here: >>>>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>>>=20 >>>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>>>=20 >>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>>>=20 >>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>>>=20 >>>>>>=20 >>>>>> We look forward to your feedback >>>>>>=20 >>>>> Thanks for doing this! I had a few comments: >>>>> 1. ZFS is not bootable on all architectures. Could you adjust that me= nu >>>>> item to only display for i386, amd64, and (I think?) sparc64. Use una= me >>>>> -m, not -p, for this. >>>> I had not considered that, I'll make that change >>>>=20 >>>>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>>>> instead of GPT. >>>> I'll disable sparc64 as well >>>>=20 >>>>> 2. Why are you using camcontrol? That is guaranteed not to work on >>>>> non-CAM systems. You should use the GEOM ident string if you need an = ID. >>>> The GEOM ident string doesn't do enough to help the user identify which >>>> drive is which. >>>> More data is not exposed anywhere that I could find >>>>=20 >>>> What we really need, is dev.ada.0.desc% like we have for network >>>> interfaces and a slew of other devices. GEOM data is great, but it is >>>> not exposed in a shell friendly way any place that I could find, other >>>> than the sysctl with DOT and XML data. >>> This is one of the reasons the partition editor is written in C. There >>> are a few other odd corner-cases where C is much more powerful than the >>> command-line for the GEOM operations that partedit needs to do. I'm not >>> sure how to usefully get it just from the shell. You can see how to do >>> it in C in the boot_disk() routine of partedit/auto_part.c. >>>=20 >>>>> 3. Any plans to integrate this into the regular partition editor? ZFS >>>>> support is important enough that I will definitely not get in the way, >>>>> even as a bolt-on, but it would be a shame for it to stay that way. T= he >>>>> editor is also designed for ZFS to be added. >>>> I am a sysadmin, not a programmer. I can't write C. Most people >>>> deploying servers can't write C. I agree with Devin Teske, if everythi= ng >>>> was in shell it would be a lot more usable for non-developers, who >>>> probably make up the majority of people who deploy FreeBSD. >>> There are some cases the other way too. Devin is probably the most >>> shell-proficient FreeBSD committer. >> Well, there's jilles ;D (he writes/maintains the sh(1) implementation it= self). >>=20 >>=20 >>> I certainly can't write shell >>> scripts at that level, which means that for me bsdconfig, for example, >>> is effectively read-only (and quite hard to read as well). >> In the past few days of working on the bsdinstall_zfs patch-set with All= an >> Jude, I learned something new actually. >>=20 >> It seems that sh(1) doesn't suffer so much from this "read only" concept. >>=20 >> Imagine you're starting a new C project on an operating system that has >> all new syscalls and all new APIs that you've never seen. Would be pretty >> hard, no doubt. Now imagine that you're thrown a life-line called POSIX >> and hey, now you're slinging code in MinGW on Windows when you don't >> know a lick of M$ syscalls or APIs. >>=20 >> In a similar manner, I've witnessed functionality be added that is truly >> functional *without* using any of the API calls. Then I come in and do >> a round of optimizations to leverage the existing API. >>=20 >> Shell is kinda like that... >>=20 >> I'm noticing Allan Jude doesn't know all the API calls yet (who could? o= ther >> than me of course -- and even I have trouble remembering them _all_) yet >> this doesn't phase him (or others) from jumping in and lending a hand. >>=20 >> No different than C, but the read-only aspect is lessened significantly I >> believe because there are so many people out there that know enough >> good shell syntax and are just a stone's throw away from *great* shell >> syntax (which I must admit jilles helped me cross that boundary). >>=20 >> I think in C, the read-only aspect is greater because its harder to parc= el-out >> the functions for a unit-test; harder to inject new code; and harder to = get >> to a functioning end-state. >=20 > Look, I have no doubt that in the right hands shell can do amazing > things and C can be badly written. That isn't the issue though. My > statement was purely that most FreeBSD developers (me included) are more > comfortable with C than shell when used at the kind of level involved > here. This is not a value judgment but a statement of fact. Whether or > not, at some platonic level, shell or C or python or whatever are more > or less read-only is not the point here. The point is that I, and I > suspect many other developers, cannot write (or read) very advanced > levels of shell scripting but can read and write the equivalent programs > when written in C in many cases. It's what the rest of the system is > written in and what we spend most of our time using. Whether this should > be the case or not is immaterial; the fact remains that shell scripting > at any but a very basic level does introduce a very large barrier to > entry for probably a large majority of committers. >=20 > This is not always a problem -- especially if using something more > obscure allows very active development by the set of people working on > it -- but does reduce the set of people who can make modifications > substantially. I have no ability to change, or understand, most of > bsdconfig, for example. This isn't a problem since you are doing all the > work and there is no reason I would need to or want to make changes to > it. But it could become a problem in a part of the system to which > multiple people needed to contribute. It's about other people's comfort > zones and knowledge in the end. I can see that. And well said -- very well spoken. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 07:20:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 06A2CEA3 for ; Thu, 10 Oct 2013 07:20:33 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id D5919257D for ; Thu, 10 Oct 2013 07:20:30 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id F36A71EC7D for ; Thu, 10 Oct 2013 07:20:28 +0000 (UTC) Message-ID: <52565555.8030906@allanjude.com> Date: Thu, 10 Oct 2013 03:20:53 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> <5254F582.1040406@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> <5256509E.3000604@freebsd.org> In-Reply-To: <5256509E.3000604@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 07:20:33 -0000 On 2013-10-10 03:00, Nathan Whitehorn wrote: > On 10/09/13 18:55, Teske, Devin wrote: >> On Oct 8, 2013, at 11:19 PM, Nathan Whitehorn wrote: >> >>> On 10/09/13 01:13, Allan Jude wrote: >>>> On 2013-10-08 16:17, Nathan Whitehorn wrote: >>>>> On 10/07/13 21:59, Allan Jude wrote: >>>>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>>>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>>>>> sector gnop trick, and optional GELI encryption. We would like to commit >>>>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>>>> obvious bugs before we send it off to re@ to get it committed. >>>>>> >>>>>> It includes a single configuration menu that allows you to select all of >>>>>> the required details, including which drives to use (gets details from >>>>>> camcontrol, also includes an inspection utility that presents the >>>>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>>>> ZFS RAID level to use (taking in to consideration the selected number of >>>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>>> >>>>>> >>>>>> Additional, it includes some other changes to bsdinstall: >>>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>>>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>>>> feature has been combined into the regular 'services to enable' dialog >>>>>> and enabled by default >>>>>> >>>>>> >>>>>> You can browse the patches here: >>>>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>>> >>>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>>> >>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>>> >>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>>> >>>>>> >>>>>> We look forward to your feedback >>>>>> >>>>> Thanks for doing this! I had a few comments: >>>>> 1. ZFS is not bootable on all architectures. Could you adjust that menu >>>>> item to only display for i386, amd64, and (I think?) sparc64. Use uname >>>>> -m, not -p, for this. >>>> I had not considered that, I'll make that change >>>> >>>>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>>>> instead of GPT. >>>> I'll disable sparc64 as well >>>> >>>>> 2. Why are you using camcontrol? That is guaranteed not to work on >>>>> non-CAM systems. You should use the GEOM ident string if you need an ID. >>>> The GEOM ident string doesn't do enough to help the user identify which >>>> drive is which. >>>> More data is not exposed anywhere that I could find >>>> >>>> What we really need, is dev.ada.0.desc% like we have for network >>>> interfaces and a slew of other devices. GEOM data is great, but it is >>>> not exposed in a shell friendly way any place that I could find, other >>>> than the sysctl with DOT and XML data. >>> This is one of the reasons the partition editor is written in C. There >>> are a few other odd corner-cases where C is much more powerful than the >>> command-line for the GEOM operations that partedit needs to do. I'm not >>> sure how to usefully get it just from the shell. You can see how to do >>> it in C in the boot_disk() routine of partedit/auto_part.c. >>> >>>>> 3. Any plans to integrate this into the regular partition editor? ZFS >>>>> support is important enough that I will definitely not get in the way, >>>>> even as a bolt-on, but it would be a shame for it to stay that way. The >>>>> editor is also designed for ZFS to be added. >>>> I am a sysadmin, not a programmer. I can't write C. Most people >>>> deploying servers can't write C. I agree with Devin Teske, if everything >>>> was in shell it would be a lot more usable for non-developers, who >>>> probably make up the majority of people who deploy FreeBSD. >>> There are some cases the other way too. Devin is probably the most >>> shell-proficient FreeBSD committer. >> Well, there's jilles ;D (he writes/maintains the sh(1) implementation itself). >> >> >>> I certainly can't write shell >>> scripts at that level, which means that for me bsdconfig, for example, >>> is effectively read-only (and quite hard to read as well). >> In the past few days of working on the bsdinstall_zfs patch-set with Allan >> Jude, I learned something new actually. >> >> It seems that sh(1) doesn't suffer so much from this "read only" concept. >> >> Imagine you're starting a new C project on an operating system that has >> all new syscalls and all new APIs that you've never seen. Would be pretty >> hard, no doubt. Now imagine that you're thrown a life-line called POSIX >> and hey, now you're slinging code in MinGW on Windows when you don't >> know a lick of M$ syscalls or APIs. >> >> In a similar manner, I've witnessed functionality be added that is truly >> functional *without* using any of the API calls. Then I come in and do >> a round of optimizations to leverage the existing API. >> >> Shell is kinda like that... >> >> I'm noticing Allan Jude doesn't know all the API calls yet (who could? other >> than me of course -- and even I have trouble remembering them _all_) yet >> this doesn't phase him (or others) from jumping in and lending a hand. >> >> No different than C, but the read-only aspect is lessened significantly I >> believe because there are so many people out there that know enough >> good shell syntax and are just a stone's throw away from *great* shell >> syntax (which I must admit jilles helped me cross that boundary). >> >> I think in C, the read-only aspect is greater because its harder to parcel-out >> the functions for a unit-test; harder to inject new code; and harder to get >> to a functioning end-state. > Look, I have no doubt that in the right hands shell can do amazing > things and C can be badly written. That isn't the issue though. My > statement was purely that most FreeBSD developers (me included) are more > comfortable with C than shell when used at the kind of level involved > here. This is not a value judgment but a statement of fact. Whether or > not, at some platonic level, shell or C or python or whatever are more > or less read-only is not the point here. The point is that I, and I > suspect many other developers, cannot write (or read) very advanced > levels of shell scripting but can read and write the equivalent programs > when written in C in many cases. It's what the rest of the system is > written in and what we spend most of our time using. Whether this should > be the case or not is immaterial; the fact remains that shell scripting > at any but a very basic level does introduce a very large barrier to > entry for probably a large majority of committers. > > This is not always a problem -- especially if using something more > obscure allows very active development by the set of people working on > it -- but does reduce the set of people who can make modifications > substantially. I have no ability to change, or understand, most of > bsdconfig, for example. This isn't a problem since you are doing all the > work and there is no reason I would need to or want to make changes to > it. But it could become a problem in a part of the system to which > multiple people needed to contribute. It's about other people's comfort > zones and knowledge in the end. > -Nathan > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I definately see your point, but the code going in to the zfsboot part in particular, is not that advanced. I started this project two weeks ago with a well below average knowledge of shell script, a minor bit of experience in php, and no real programming experience to speak of. I wrote most of the code that actually does things, Devin just cleaned it up (I didn't know anything about shstyle or the rules) and pointed me at some handy subroutines he had written to avoid writing out 20 lines of code every time I wanted to display a dialog box I wouldn't say any of what is in the proposed patches to bsdinstall is unmaintainable, and it definately makes it much more approachable for sysadmins who are the ones that actually need to be able to script bsdinstall, and generate various methods of automated deployment. This is a very important feature if we want FreeBSD to be taken seriously for deployment in mass virtualization environments (do not make my say cloud. we saw a great sign in Malta at some street festival "what is cloud?") -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 07:22:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D09FEFD8 for ; Thu, 10 Oct 2013 07:22:04 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 67BDB259B for ; Thu, 10 Oct 2013 07:22:03 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1VUAZN-001iXK-HP>; Thu, 10 Oct 2013 09:22:01 +0200 Received: from g231191004.adsl.alicedsl.de ([92.231.191.4] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1VUAZN-0035KF-Bl>; Thu, 10 Oct 2013 09:22:01 +0200 Date: Thu, 10 Oct 2013 09:21:55 +0200 From: "O. Hartmann" To: Fabian Keil Subject: Re: claws-mail deadlocking in iconv Message-ID: <20131010092155.2cadb667@thor.walstatt.dyndns.org> In-Reply-To: <73d40037.635a97ef@fabiankeil.de> References: <73d40037.635a97ef@fabiankeil.de> Organization: FU Berlin X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/ZoMOI=M2qjSYT8l3U6hGz19"; protocol="application/pgp-signature" X-Originating-IP: 92.231.191.4 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 07:22:04 -0000 --Sig_/ZoMOI=M2qjSYT8l3U6hGz19 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 9 Oct 2013 18:34:46 +0200 Fabian Keil wrote: > After the iconv import claws-mail started to deadlock in iconv every > now and then on my system, which prevented claws-mail from rendering > windows or reacting to input. >=20 > So far I haven't been able to reproduce this intentionally and various > rebuilds of ports, kernel and userland (mainly for other reasons) had > no effect. >=20 > When the problem occurs, trying to attach to the process causes > gdb and gdb76 to crash which also crashes claws-mail, but sending > SIGABRT causes a proper core dump that can be analysed with gdb. >=20 > The backtraces always show that there is only one thread running and > it's trying to lock cm_lock in _citrus_mapper_close(), which > apparently is already locked due to a _citrus_mapper_close() > recursion. Examples: >=20 > #0 _umtx_op_err () > at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 37 > RSYSCALL_ERR(_umtx_op) [New Thread 80a806400 (LWP 100487/claws-mail)] > (gdb) where > #0 _umtx_op_err () > at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 #1 > 0x00000008084861a6 in __thr_rwlock_wrlock (rwlock=3D0x80a8a47c0, > tsp=3D) > at /usr/src/lib/libthr/thread/thr_umtx.c:296 #2 0x0000000808489b1d > in rwlock_wrlock_common (rwlock=3D, abstime=3D0x0) > at /usr/src/lib/libthr/thread/thr_rwlock.c:267 #3 0x0000000808489a8b > in _pthread_rwlock_wrlock (rwlock=3D0x80a8a47c0) > at /usr/src/lib/libthr/thread/thr_rwlock.c:289 #4 0x000000080911e848 > in _citrus_mapper_close (cm=3D0x80b5a2d80) > at /usr/src/lib/libc/iconv/citrus_mapper.c:375 #5 0x000000080d205d18 > in _citrus_mapper_serial_mapper_uninit (cm=3D0x80b5a2d40) > at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/citrus_= mapper_serial.c:110 > #6 0x000000080911e8d7 in mapper_close (cm=3D0x80b5a2d40) > at /usr/src/lib/libc/iconv/citrus_mapper.c:188 #7 0x000000080911e88c > in _citrus_mapper_close (cm=3D) > at /usr/src/lib/libc/iconv/citrus_mapper.c:384 #8 0x000000080c4e83f3 > in close_srcs (sl=3D0x80b591140) > at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_std.c:206 #9 > 0x000000080c4e7dc9 in _citrus_iconv_std_iconv_uninit_shared > (ci=3D) > at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_std.c:415 #10 > 0x00000008090f3f95 in release_shared (ci=3D0x80a8ee630) > at /usr/src/lib/libc/iconv/citrus_iconv.c:99 #11 0x00000008090f4002 > in _citrus_iconv_close (cv=3D0x80d88d5d0) > at /usr/src/lib/libc/iconv/citrus_iconv.c:335 #12 0x00000008090f1ca6 > in iconv_close (handle=3D0x80a8a47c0) > at /usr/src/lib/libc/iconv/iconv.c:131 #13 0x000000000046376d in > conv_iconv_strdup (inbuf=3D0x7fffffff58b0 "\n", src_code=3D0x80b5b4db0 > "Windows-1252", dest_code=3D0x6f03d0 "UTF-8") at codeconv.c:895 #14 > 0x0000000000463d13 in conv_convert (conv=3D0x80b5a4e80, > outbuf=3D0x7fffffff3720 "", outlen=3D8192, inbuf=3D0x7fffffff58b0 "\n") at > codeconv.c:734 #15 0x00000000005e22ac in textview_write_line > (textview=3D0x80a959cc0, str=3D0x7fffffff58b0 "\n", conv=3D0x80b5a4e80, > do_quote_folding=3D1) at textview.c:1573 #16 0x00000000005df8e4 in > textview_write_body (textview=3D0x80a959cc0, mimeinfo=3D0x80aad2d00) at > textview.c:1177 #17 0x00000000005e5363 in textview_add_part > (textview=3D0x80a959cc0, mimeinfo=3D0x80aad2d00) at textview.c:826 #18 > 0x00000000005e4053 in recursive_add_parts (textview=3D0x80a959cc0, > node=3D0x80a826190) at textview.c:839 #19 0x00000000005e4302 in > recursive_add_parts (textview=3D0x80a959cc0, node=3D0x80aa81d20) at > textview.c:888 #20 0x00000000005e4302 in recursive_add_parts > (textview=3D0x80a959cc0, node=3D0x80a828890) at textview.c:888 #21 > 0x00000000005defa1 in textview_add_parts (textview=3D0x80a959cc0, > mimeinfo=3D0x80b610700) at textview.c:898 #22 0x00000000005deb85 in > textview_show_part (textview=3D0x80a959cc0, mimeinfo=3D0x80b610700, > fp=3D0x8094319a0) at textview.c:645 [...] >=20 > #0 0x0000000808491b9c in __error () from /lib/libthr.so.3 > #1 0x000000080848bb1d in rwlock_wrlock_common (rwlock=3D optimized out>, abstime=3D0x0) > at /usr/src/lib/libthr/thread/thr_rwlock.c:267 #2 0x000000080848ba8b > in _pthread_rwlock_wrlock (rwlock=3D0x80a8ede20) > at /usr/src/lib/libthr/thread/thr_rwlock.c:289 #3 0x000000080911f848 > in _citrus_mapper_close (cm=3D0x80a8bfc40) > at /usr/src/lib/libc/iconv/citrus_mapper.c:375 #4 0x000000080ce02d18 > in _citrus_mapper_serial_mapper_uninit (cm=3D0x80a8bfc00) > at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/citrus_= mapper_serial.c:110 > #5 0x000000080911f8d7 in mapper_close (cm=3D0x80a8bfc00) > at /usr/src/lib/libc/iconv/citrus_mapper.c:188 #6 0x000000080911f88c > in _citrus_mapper_close (cm=3D) > at /usr/src/lib/libc/iconv/citrus_mapper.c:384 #7 0x000000080c5893f3 > in close_srcs (sl=3D0x80a8edda0) > at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_std.c:206 #8 > 0x000000080c588dc9 in _citrus_iconv_std_iconv_uninit_shared > (ci=3D) > at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_std.c:415 #9 > 0x00000008090f4f95 in release_shared (ci=3D0x80b408890) > at /usr/src/lib/libc/iconv/citrus_iconv.c:99 #10 0x00000008090f5002 > in _citrus_iconv_close (cv=3D0x80b782630) > at /usr/src/lib/libc/iconv/citrus_iconv.c:335 #11 0x00000008090f2ca6 > in iconv_close (handle=3D0x80a8ede20) > at /usr/src/lib/libc/iconv/iconv.c:131 #12 0x000000000046376d in > conv_iconv_strdup ( inbuf=3D0x80b600e00 "[...]"..., > src_code=3D0x80b782640 "ISO-8859-15", dest_code=3D0x80c07ab24 "UTF-8") at > codeconv.c:895 #13 0x0000000000463f2f in conv_codeset_strdup > ( inbuf=3D0x80b600e00 "[...]"..., src_code=3D0x80b782640 "ISO-8859-15", > dest_code=3D0x80c07ab24 "UTF-8") at codeconv.c:774 #14 > 0x000000080c07a1a7 in get_part_as_string (mimeinfo=3D0x80aad2d80) at > pgpinline.c:153 #15 0x000000080c078333 in pgpinline_is_encrypted > (mimeinfo=3D0x80aad2d80) at pgpinline.c:375 [...] >=20 > #0 _umtx_op_err () > at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37 #1 > 0x00000008084861a6 in __thr_rwlock_wrlock (rwlock=3D0x80bf93f40, > tsp=3D) > at /usr/src/lib/libthr/thread/thr_umtx.c:296 #2 0x0000000808489b1d > in rwlock_wrlock_common (rwlock=3D, abstime=3D0x0) > at /usr/src/lib/libthr/thread/thr_rwlock.c:267 #3 0x0000000808489a8b > in _pthread_rwlock_wrlock (rwlock=3D0x80bf93f40) > at /usr/src/lib/libthr/thread/thr_rwlock.c:289 #4 0x000000080911e848 > in _citrus_mapper_close (cm=3D0x80bfa0b40) > at /usr/src/lib/libc/iconv/citrus_mapper.c:375 #5 0x000000080d08ad18 > in _citrus_mapper_serial_mapper_uninit (cm=3D0x80bfa0b00) > at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/citrus_= mapper_serial.c:110 > #6 0x000000080911e8d7 in mapper_close (cm=3D0x80bfa0b00) > at /usr/src/lib/libc/iconv/citrus_mapper.c:188 #7 0x000000080911e88c > in _citrus_mapper_close (cm=3D) > at /usr/src/lib/libc/iconv/citrus_mapper.c:384 #8 0x000000080ae2c3f3 > in close_srcs (sl=3D0x80bf9fbc0) > at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_std.c:206 #9 > 0x000000080ae2bdc9 in _citrus_iconv_std_iconv_uninit_shared > (ci=3D) > at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv_std.c:415 #10 > 0x00000008090f3f95 in release_shared (ci=3D0x80bd59ac0) > at /usr/src/lib/libc/iconv/citrus_iconv.c:99 #11 0x00000008090f4002 > in _citrus_iconv_close (cv=3D0x80dc1a3d0) > at /usr/src/lib/libc/iconv/citrus_iconv.c:335 #12 0x00000008090f1ca6 > in iconv_close (handle=3D0x80bf93f40) > at /usr/src/lib/libc/iconv/iconv.c:131 #13 0x000000000046376d in > conv_iconv_strdup (inbuf=3D0x80bd570c0 "[...]", src_code=3D0x7fffffff5d60 > "ISO-8859-2", dest_code=3D0x6f03d0 "UTF-8") at codeconv.c:895 #14 > 0x0000000000463f2f in conv_codeset_strdup (inbuf=3D0x80bd570c0 "[...]", > src_code=3D0x7fffffff5d60 "ISO-8859-2", dest_code=3D0x0) at > codeconv.c:774 #15 0x00000000005f63f0 in unmime_header > (encoded_str=3D0x7fffffff7e94 "[...]", addr_field=3D1) at unmime.c:144 > #16 0x0000000000464a56 in conv_unmime_header (str=3D0x7fffffff7e94 > "[...]", default_encoding=3D0x0, addr_field=3D1) at codeconv.c:1516 #17 > 0x000000000059588a in parse_stream (data=3D0x8094319a0, isstring=3D0, > flags=3D{perm_flags =3D 3, tmp_flags =3D 0}, full=3D0, decrypted=3D0) at > procheader.c:558 #18 0x0000000000595234 in procheader_parse_stream > (fp=3D0x8094319a0, flags=3D{perm_flags =3D 3, tmp_flags =3D 0}, full=3D0, > decrypted=3D0) at procheader.c:461 #19 0x0000000000595195 in > procheader_parse_file (file=3D0x80d4202b0 > "/home/fk/.claws-mail/tempfolder/processing/18", flags=3D{perm_flags =3D > 3, tmp_flags =3D 0}, full=3D0, decrypted=3D0) at procheader.c:354 [...] >=20 > This patch: > http://www.fabiankeil.de/sourcecode/freebsd/iconv-Let-_citrus_mapper_clos= e-unlock-cm_lock-before-calli.diff > seems to prevent the deadlock, but I'm not 100% sure that it's > correct and I'm also a bit surprised by the lack of reports from > other claws-mail users. >=20 > Did anyone else run into this or can comment on the patch or > the backtraces? >=20 > Fabian Hello Fabian, I can not go that sophisticated deep into the details like you. But I'm running claws-mail on a cutting-edge 10.0-CURRENT and I can confirm, that claws-mail starts locking up from time to time in the way you described. The frequency of such a non-rendering locked up window of claws-mail correlates with the frequency I use the client. I'll try the patch. Oliver --Sig_/ZoMOI=M2qjSYT8l3U6hGz19 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJSVlWYAAoJEOgBcD7A/5N8dQUIAJpvCskF8/sW0+nuu6YzkrOm cWdVeIifq1rzpPNGkgtHStaoYumB5a4d1D/PasUfcrwAiyYqZmQgJNt8Su+DN/Dz 0szGaEqJ6M35f+H9iDZ5GUxnHGhXoBxB3n89ZCWk7sEp/A0vxez1ognmmJA4zwKK ulj4hM0Pb5w4Tr6jf9Tmy8wXM2kqvWdqxcbiUJCze1nFCpB6XXO9HFyi6oOl9mC3 3VjUYv9F4WcALjdIRY4BL+DCtduhJ0LDa70Q9h40DW0KF/bFrt1Zwj4fhp3RET2U y/fmVt41OEnvxUjXhKxHlo9nPqR7PpJjknKkdEPmzTjJ7iNiKavLqlDVSswFPUU= =o1ak -----END PGP SIGNATURE----- --Sig_/ZoMOI=M2qjSYT8l3U6hGz19-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 07:49:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 290CBA9C for ; Thu, 10 Oct 2013 07:49:49 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E749D271D for ; Thu, 10 Oct 2013 07:49:48 +0000 (UTC) Received: by mail-oa0-f43.google.com with SMTP id i3so1149569oag.16 for ; Thu, 10 Oct 2013 00:49:48 -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=+HY6uBVzIPDSt3HUnGoUjgyzUED07oGa8UhDN1okbLU=; b=RPtVRb9rYFbfpjyeT3ldhJWcNob5z/XhojuOXnNbC0USIELm9vW8Xu05yJ19xD0dFx 97KuDdYE9by2qfrLKYgE4pKxwhoTw+8d/hvEHciWsmnvL4xXKHwx/R8FWrLh8bq3FGfT Xg3pOG7GYjRdEt1xpPY7JKV8Y6xLr+jiDqzv23fgIkX+Hw3/B3EELtrtTh1ejojKJeEf /w3O597tGaDmCJscZel/661o6mRZSaGbUZh3SSL+FHbSqvp3g3avP8zBNYCWamqG9+a5 6bXJWq6q2qnkg7Yb0Caq0jyRR+84tudVf+iqD/bS+hvRZP1cOBsU1ZiEeixyGhbCQdMa xSHQ== MIME-Version: 1.0 X-Received: by 10.60.68.34 with SMTP id s2mr9376oet.105.1381391388243; Thu, 10 Oct 2013 00:49:48 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Thu, 10 Oct 2013 00:49:48 -0700 (PDT) In-Reply-To: <20131010013338.GA10499@troutmask.apl.washington.edu> References: <20131010013338.GA10499@troutmask.apl.washington.edu> Date: Thu, 10 Oct 2013 03:49:48 -0400 Message-ID: Subject: Re: /usr/src/lib/msun errors From: Joe Nosay To: Steve Kargl Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 07:49:49 -0000 Yes, I did. To what extent did I screw up? # added by use.perl 2013-03-03 23:39:20 PERL_VERSION=5.16.2 RUBY_DEFAULT_VER=1.9 ALLOW_SHARED_TEXTREL=1 CFLAGS+= -mssse3 -Wall CXXFLAGS+= -mssse3 On Wed, Oct 9, 2013 at 9:33 PM, Steve Kargl < sgk@troutmask.apl.washington.edu> wrote: > On Wed, Oct 09, 2013 at 09:00:11PM -0400, Joe Nosay wrote: > > Src is from 10/7/13 on i386. Base is from April. > > > cc -O2 -pipe -mssse3 -Wall -I/usr/src/lib/msun/x86 > -I/usr/src/lib/msun/ld80 -I/usr/src/lib/msun/src > -I/usr/src/lib/msun/../libc/include -I/usr/src/lib/msun/../libc/i386 > -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror > -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum > -Wno-knr-promoted-parameter -Wno-parentheses -c > /usr/src/lib/msun/src/e_j0.c -o e_j0.o > > /usr/src/lib/msun/src/e_j0.c:281:10: error: variable 'p' is used > uninitialized whenever 'if' condition is false > [-Werror,-Wsometimes-uninitialized] > > Are you setting CFLAGS in make.conf? > > -- > Steve > From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 08:14:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7ED8BBC for ; Thu, 10 Oct 2013 08:14:22 +0000 (UTC) (envelope-from andrnils@gmail.com) 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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 491082897 for ; Thu, 10 Oct 2013 08:14:22 +0000 (UTC) Received: by mail-ob0-f178.google.com with SMTP id uz6so1515247obc.9 for ; Thu, 10 Oct 2013 01:14:21 -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=dJbVkLb6iE521T+wUmJGMMBsusZaYIEJjYIzVa3z+Ks=; b=z/AUd+KtbDTR+EjcNYzKHyz+o5POF24W+D2zynA6C5hKpO6VxIWl3tI+tYVzdehuAD mW3qefdOsh+ZcoRKTdrdmHOIcOyiZBz6n9m97JLC2bUqF8NYrKH+T8AEP3A7nrOhPmGt X6LEau53/0GKHX8hAR4gqN1k415lOZEeRde35I8GdHWAL3br6q0u4teXHqG8fXKw8anK GeHNlNzosR6V0RP9M8is5KYTMKyB3PJHvkOKIVqk8dKZS2OvRrFApByZh2q7TlqJZ4Ni CyPNLaTM5W7Buc8akkm7Qesco8dEC3YSQ6d/sH5vYJrME1nw/g1bsxFn8G9n0wtgsTlV VIog== MIME-Version: 1.0 X-Received: by 10.60.93.67 with SMTP id cs3mr9445433oeb.12.1381392861345; Thu, 10 Oct 2013 01:14:21 -0700 (PDT) Received: by 10.76.91.34 with HTTP; Thu, 10 Oct 2013 01:14:21 -0700 (PDT) In-Reply-To: References: <20131010013338.GA10499@troutmask.apl.washington.edu> Date: Thu, 10 Oct 2013 10:14:21 +0200 Message-ID: Subject: Re: /usr/src/lib/msun errors From: Andreas Nilsson To: Joe Nosay Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 08:14:22 -0000 Since there is -Wall in your CFALGS there will be quite a few warnings, which combined with -Werror which promotes warnings to errors makes it fail. Try removing -Wall and see if it works. Also -mssse3 can trigger more subtle stuff. Best regards Andreas On Thu, Oct 10, 2013 at 9:49 AM, Joe Nosay wrote: > Yes, I did. To what extent did I screw up? > > # added by use.perl 2013-03-03 23:39:20 > PERL_VERSION=5.16.2 > RUBY_DEFAULT_VER=1.9 > ALLOW_SHARED_TEXTREL=1 > > CFLAGS+= -mssse3 -Wall > CXXFLAGS+= -mssse3 > > > > > On Wed, Oct 9, 2013 at 9:33 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > On Wed, Oct 09, 2013 at 09:00:11PM -0400, Joe Nosay wrote: > > > Src is from 10/7/13 on i386. Base is from April. > > > > > cc -O2 -pipe -mssse3 -Wall -I/usr/src/lib/msun/x86 > > -I/usr/src/lib/msun/ld80 -I/usr/src/lib/msun/src > > -I/usr/src/lib/msun/../libc/include -I/usr/src/lib/msun/../libc/i386 > > -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror > > -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int > > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality > > -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum > > -Wno-knr-promoted-parameter -Wno-parentheses -c > > /usr/src/lib/msun/src/e_j0.c -o e_j0.o > > > /usr/src/lib/msun/src/e_j0.c:281:10: error: variable 'p' is used > > uninitialized whenever 'if' condition is false > > [-Werror,-Wsometimes-uninitialized] > > > > Are you setting CFLAGS in make.conf? > > > > -- > > Steve > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 08:47:41 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1EE0F8BB for ; Thu, 10 Oct 2013 08:47:41 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6E83E2A35 for ; Thu, 10 Oct 2013 08:47:39 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA18173 for ; Thu, 10 Oct 2013 11:47:38 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VUBuE-00036E-Au for freebsd-current@FreeBSD.org; Thu, 10 Oct 2013 11:47:38 +0300 Message-ID: <52566972.3090204@FreeBSD.org> Date: Thu, 10 Oct 2013 11:46:42 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: FreeBSD Current Subject: (bsd)patch vs file removal X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 08:47:41 -0000 The following is from patch -C -p1: Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |diff --git a/sys/cddl/compat/opensolaris/sys/taskq.h b/sys/cddl/compat/opensolaris/sys/taskq.h |deleted file mode 100644 |index ffe70ca..0000000 |--- a/sys/cddl/compat/opensolaris/sys/taskq.h |+++ /dev/null -------------------------- Patching file sys/cddl/compat/opensolaris/sys/taskq.h using Plan A... Empty context always matches. Hunk #1 failed at 0. 1 out of 1 hunks failed while patching sys/cddl/compat/opensolaris/sys/taskq.h -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 09:22:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 514B8279 for ; Thu, 10 Oct 2013 09:22:27 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0C4152C26 for ; Thu, 10 Oct 2013 09:22:26 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1VUCRr-0007xF-L2 ; Thu, 10 Oct 2013 12:22:23 +0300 Date: Thu, 10 Oct 2013 12:22:23 +0300 From: Vitalij Satanivskij To: Vitalij Satanivskij Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173 Message-ID: <20131010092223.GA28347@hell.ukr.net> References: <1381166916.122992963.5h9ygiri@frv45.ukr.net> <1381170764.32684.31088349.343931EE@webmail.messagingengine.com> <20131007185032.GA82932@hell.ukr.net> <20131007211201.GA89306@hell.ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131007211201.GA89306@hell.ukr.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 09:22:27 -0000 Same situation hapend yesterday again :( What's confuse me while trying to understend where I'm wrong Firt some info. We have zfs pool "POOL" and one more zfs on it "POOL/zfs" POOL - have only primarycache enabled "ALL" POOL/zfs - have both primay and secondary for "ALL" POOL have compression=lz4 POOL/zfs have none POOL - have around 9TB data POOL/zfs - have 1TB Secondary cache have configuration - cache gpt/cache0 ONLINE 0 0 0 gpt/cache1 ONLINE 0 0 0 gpt/cache2 ONLINE 0 0 0 gpt/cache0-2 it's intel sdd SSDSC2BW180A4 180gb So full real size for l2 is 540GB (realy 489gb) First question - data on l2arc will be compressed on not? Second in stats we see L2 ARC Size: (Adaptive) 2.08 TiB eary it was 1.1 1.4 ... So a) how cache can be biger than zfs it self b) in case it's not compressed (answer for first question) how it an be biger than real ssd size? one more coment if l2 arc size grove above phisical sizes I se next stats kstat.zfs.misc.arcstats.l2_cksum_bad: 50907344 kstat.zfs.misc.arcstats.l2_io_error: 4547377 and growing. System is r255173 with patch from rr255173 At last maybe somebody have any ideas what's realy hapend... Vitalij Satanivskij wrote: VS> VS> One more question - VS> VS> we have two counter - VS> VS> kstat.zfs.misc.arcstats.l2_size: 1256609410560 VS> kstat.zfs.misc.arcstats.l2_asize: 1149007667712 VS> VS> can anybody explain how to understand them i.e. l2_asize - real used space on l2arc an l2_size - uncompressed size, VS> VS> or maybe something else ? VS> VS> VS> VS> Vitalij Satanivskij wrote: VS> VS> VS> VS> Data on pool have compressratio around 1.4 VS> VS> VS> VS> On diferent servers with same data type and load L2 ARC Size: (Adaptive) can be diferent VS> VS> VS> VS> for example 1.04 TiB vs 1.45 TiB VS> VS> VS> VS> But it's all have same porblem - grow in time. VS> VS> VS> VS> VS> VS> More stange for us - VS> VS> VS> VS> ARC: 80G Total, 4412M MFU, 5040M MRU, 76M Anon, 78G Header, 2195M Other VS> VS> VS> VS> 78G header size and ubnormal - VS> VS> VS> VS> kstat.zfs.misc.arcstats.l2_cksum_bad: 210920592 VS> VS> kstat.zfs.misc.arcstats.l2_io_error: 7362414 VS> VS> VS> VS> sysctl's growing avery second. VS> VS> VS> VS> All part's of server (as hardware part's) in in normal state. VS> VS> VS> VS> After reboot no problem's for some period untile cache size grow to some limit. VS> VS> VS> VS> VS> VS> VS> VS> Mark Felder wrote: VS> VS> MF> On Mon, Oct 7, 2013, at 13:09, Dmitriy Makarov wrote: VS> VS> MF> > VS> VS> MF> > How can L2 ARC Size: (Adaptive) be 1.44 TiB (up) with total physical size VS> VS> MF> > of L2ARC devices 490GB? VS> VS> MF> > VS> VS> MF> VS> VS> MF> http://svnweb.freebsd.org/base?view=revision&revision=251478 VS> VS> MF> VS> VS> MF> L2ARC compression perhaps? VS> VS> MF> _______________________________________________ VS> VS> MF> freebsd-current@freebsd.org mailing list VS> VS> MF> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> VS> MF> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" VS> VS> _______________________________________________ VS> VS> freebsd-current@freebsd.org mailing list VS> VS> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> VS> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" VS> _______________________________________________ VS> freebsd-current@freebsd.org mailing list VS> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 09:32:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 46CFD481 for ; Thu, 10 Oct 2013 09:32:29 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 049772CB4 for ; Thu, 10 Oct 2013 09:32:28 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1VUCbZ-00086J-Cq ; Thu, 10 Oct 2013 12:32:25 +0300 Date: Thu, 10 Oct 2013 12:32:25 +0300 From: Vitalij Satanivskij To: Richard Todd Subject: Re: Assertion in zdb? Message-ID: <20131010093225.GA30981@hell.ukr.net> References: <20131009132258.GA85485@hell.ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Vitalij Satanivskij , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 09:32:29 -0000 Hello. Yes, load on machine (on fs) is very extensive. Ok thank you for usefull information Richard Todd wrote: RT> Vitalij Satanivskij writes: RT> RT> > Hello. RT> > RT> > System - 10.0-CURRENT FreeBSD 10.0-CURRENT #2 r255173 RT> > RT> > While trying to get some statistics from zdb RT> > RT> > zdb -dd disk1 > stat.log RT> > RT> > get some assertion: RT> > RT> > Assertion failed: object_count == usedobjs (0x85727 == 0x3aa93d), file /usr/src/cddl/usr.sbin/zdb/../../../cddl/contrib/opensolaris/cmd/zdb/zdb.c, line 1767. RT> > zsh: abort (core dumped) zdb -dd disk1 > stat.log RT> > RT> > Maybe somebody have any idea about what's it's can be and how big problem it's (or not a problem at all)? RT> RT> Probably not a problem unless it happens reliably when you try it multiple RT> times. Since zdb looks at the raw disks, if the filesystem/zpool is active, RT> zdb can easily read bits of the zpool metadata off the disks at different RT> times and thus see an inconsistent state. Hence trying to get stats out of RT> zdb always carries a certain risk of not working. RT> RT> _______________________________________________ RT> freebsd-current@freebsd.org mailing list RT> http://lists.freebsd.org/mailman/listinfo/freebsd-current RT> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 10:01:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2565DF64 for ; Thu, 10 Oct 2013 10:01:15 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D597F2E9A for ; Thu, 10 Oct 2013 10:01:14 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1VUD3Q-000F6O-SF ; Thu, 10 Oct 2013 13:01:12 +0300 Date: Thu, 10 Oct 2013 13:01:12 +0300 From: Vitalij Satanivskij To: Vitalij Satanivskij Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173 Message-ID: <20131010100112.GA57736@hell.ukr.net> References: <1381166916.122992963.5h9ygiri@frv45.ukr.net> <1381170764.32684.31088349.343931EE@webmail.messagingengine.com> <20131007185032.GA82932@hell.ukr.net> <20131007211201.GA89306@hell.ukr.net> <20131010092223.GA28347@hell.ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131010092223.GA28347@hell.ukr.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 10:01:15 -0000 Hm, another strange thing's on another server - zfs-stats -L ------------------------------------------------------------------------ ZFS Subsystem Report Thu Oct 10 12:56:54 2013 ------------------------------------------------------------------------ L2 ARC Summary: (DEGRADED) Passed Headroom: 8.34m Tried Lock Failures: 145.66m IO In Progress: 9.76m Low Memory Aborts: 526 Free on Write: 1.70m Writes While Full: 29.28k R/W Clashes: 341.30k Bad Checksums: 865.91k IO Errors: 44.19k SPA Mismatch: 32.03m L2 ARC Size: (Adaptive) 189.28 GiB Header Size: 4.88% 9.24 GiB Looks like size have nothing similar with IO errors. So question is - when error's like Bad Checksums and IO Errors can hapend? Look's like no hardware problem's. All ssd atached to onboard intel sata controler (Motherboard is Supermicro X9SRL-F) Vitalij Satanivskij wrote: VS> Same situation hapend yesterday again :( VS> VS> What's confuse me while trying to understend where I'm wrong VS> VS> VS> Firt some info. VS> VS> We have zfs pool "POOL" and one more zfs on it "POOL/zfs" VS> VS> POOL - have only primarycache enabled "ALL" VS> POOL/zfs - have both primay and secondary for "ALL" VS> VS> POOL have compression=lz4 VS> VS> POOL/zfs have none VS> VS> VS> POOL - have around 9TB data VS> VS> POOL/zfs - have 1TB VS> VS> Secondary cache have configuration - VS> VS> cache VS> gpt/cache0 ONLINE 0 0 0 VS> gpt/cache1 ONLINE 0 0 0 VS> gpt/cache2 ONLINE 0 0 0 VS> VS> gpt/cache0-2 it's intel sdd SSDSC2BW180A4 180gb VS> VS> So full real size for l2 is 540GB (realy 489gb) VS> VS> First question - data on l2arc will be compressed on not? VS> VS> Second in stats we see VS> VS> L2 ARC Size: (Adaptive) 2.08 TiB VS> VS> eary it was 1.1 1.4 ... VS> VS> So a) how cache can be biger than zfs it self VS> b) in case it's not compressed (answer for first question) how it an be biger than real ssd size? VS> VS> VS> one more coment if l2 arc size grove above phisical sizes I se next stats VS> VS> kstat.zfs.misc.arcstats.l2_cksum_bad: 50907344 VS> kstat.zfs.misc.arcstats.l2_io_error: 4547377 VS> VS> and growing. VS> VS> VS> System is r255173 with patch from rr255173 VS> VS> VS> At last maybe somebody have any ideas what's realy hapend... VS> VS> VS> VS> VS> VS> Vitalij Satanivskij wrote: VS> VS> VS> VS> One more question - VS> VS> VS> VS> we have two counter - VS> VS> VS> VS> kstat.zfs.misc.arcstats.l2_size: 1256609410560 VS> VS> kstat.zfs.misc.arcstats.l2_asize: 1149007667712 VS> VS> VS> VS> can anybody explain how to understand them i.e. l2_asize - real used space on l2arc an l2_size - uncompressed size, VS> VS> VS> VS> or maybe something else ? VS> VS> VS> VS> VS> VS> VS> VS> Vitalij Satanivskij wrote: VS> VS> VS> VS> VS> VS> Data on pool have compressratio around 1.4 VS> VS> VS> VS> VS> VS> On diferent servers with same data type and load L2 ARC Size: (Adaptive) can be diferent VS> VS> VS> VS> VS> VS> for example 1.04 TiB vs 1.45 TiB VS> VS> VS> VS> VS> VS> But it's all have same porblem - grow in time. VS> VS> VS> VS> VS> VS> VS> VS> VS> More stange for us - VS> VS> VS> VS> VS> VS> ARC: 80G Total, 4412M MFU, 5040M MRU, 76M Anon, 78G Header, 2195M Other VS> VS> VS> VS> VS> VS> 78G header size and ubnormal - VS> VS> VS> VS> VS> VS> kstat.zfs.misc.arcstats.l2_cksum_bad: 210920592 VS> VS> VS> kstat.zfs.misc.arcstats.l2_io_error: 7362414 VS> VS> VS> VS> VS> VS> sysctl's growing avery second. VS> VS> VS> VS> VS> VS> All part's of server (as hardware part's) in in normal state. VS> VS> VS> VS> VS> VS> After reboot no problem's for some period untile cache size grow to some limit. VS> VS> VS> VS> VS> VS> VS> VS> VS> VS> VS> VS> Mark Felder wrote: VS> VS> VS> MF> On Mon, Oct 7, 2013, at 13:09, Dmitriy Makarov wrote: VS> VS> VS> MF> > VS> VS> VS> MF> > How can L2 ARC Size: (Adaptive) be 1.44 TiB (up) with total physical size VS> VS> VS> MF> > of L2ARC devices 490GB? VS> VS> VS> MF> > VS> VS> VS> MF> VS> VS> VS> MF> http://svnweb.freebsd.org/base?view=revision&revision=251478 VS> VS> VS> MF> VS> VS> VS> MF> L2ARC compression perhaps? VS> VS> VS> MF> _______________________________________________ VS> VS> VS> MF> freebsd-current@freebsd.org mailing list VS> VS> VS> MF> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> VS> VS> MF> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" VS> VS> VS> _______________________________________________ VS> VS> VS> freebsd-current@freebsd.org mailing list VS> VS> VS> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> VS> VS> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" VS> VS> _______________________________________________ VS> VS> freebsd-current@freebsd.org mailing list VS> VS> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> VS> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" VS> _______________________________________________ VS> freebsd-current@freebsd.org mailing list VS> http://lists.freebsd.org/mailman/listinfo/freebsd-current VS> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 10:05:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EE0721F8 for ; Thu, 10 Oct 2013 10:05:56 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C81652ED4 for ; Thu, 10 Oct 2013 10:05:56 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id xb4so2322330pbc.22 for ; Thu, 10 Oct 2013 03:05:50 -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=pEb+gkS1rvb8k3Tj8dwu+a1xAs7Ftph1mMU7AmH1R74=; b=cXqNXpuEnbygWm16Cuao6aPNzSgMWyxtiVnPSKoA09xc1Ve8VyaAt0GIubbrmpphwC 50my21csJiv8UGgptEoDsO+iYg7YAgu1lkQB8Ib2QlLKTfO0qYh/pdRzxM/1zLtLtI/i NABl+Ss6A3BAuGCnkA/PUnDRlzpFY+/RAcna+BaNUyAJWy0/3YEy2RXO2lKCZhXTMNv/ i1jZSn7TYtaCAKW5vjBzWDEUxHJJkhILIl27TfieunOA1l2OjK0Exej+G8Cec6rYIU38 lkt4diK8+WI/1HFAq4aYv7NdRfhmcGX+JmocJRffHNYcOm0Qg2t8AilinbdQNS3IhWBc 0q8Q== X-Gm-Message-State: ALoCoQmTGFY9jsbTYU0AYC1lS5z/57Na+uKMQkq6IB6DxfPe4tGDg07hg2hor6F48pBSCSUR5w9q MIME-Version: 1.0 X-Received: by 10.68.6.170 with SMTP id c10mr12926419pba.101.1381399550204; Thu, 10 Oct 2013 03:05:50 -0700 (PDT) Received: by 10.68.250.196 with HTTP; Thu, 10 Oct 2013 03:05:50 -0700 (PDT) X-Originating-IP: [93.221.173.86] In-Reply-To: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> Date: Thu, 10 Oct 2013 12:05:50 +0200 Message-ID: Subject: Re: rcs From: "C. P. Ghost" To: Lyndon Nerenberg Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 10:05:57 -0000 On Tue, Oct 8, 2013 at 4:31 AM, Lyndon Nerenberg wrote: > Okay folks, can we make a call about keeping the RCS tools in the base? > > The proponents wanting to remove RCS need to speak up and make their > technical case. > Still using RCS here and there, esp. managing /etc. Having to install it separately on machines that are not or seldom connected would be a pain. On a more general note: *if* you absolutely have to kill functionality and move it into ports, please do create a ports/freebsd category, and move to it stuff like net/freebsd-uucp etc... This way, all code that was previously in /usr/src would be availabel at one place. Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 14:15:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7C083B83 for ; Thu, 10 Oct 2013 14:15:16 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 540182F4A for ; Thu, 10 Oct 2013 14:15:16 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id 1801966CA4; Thu, 10 Oct 2013 07:15:16 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 63619-05; Thu, 10 Oct 2013 07:15:15 -0700 (PDT) Received: from [192.168.0.51] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id CDD9E66C9C; Thu, 10 Oct 2013 07:15:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ixsystems.com; s=newknight0; t=1381414515; bh=L62SmDpQOM3Ah3U7XW6KHMoZf279trJ+r8Fitf5/fwA=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=LIvXmShxcvOAAVsp5LNodExXuttbQxJl9RtgYGCj3vZRRkv5H7LBaCJC/IIa/SKiH jMxO9S8fSvGcgzUcdd/J3zX7LtLr9Jq4DlVJZ6Ypl3ngSPOikGuqL22v1oWUKEv7En dqt3vyiFAxz9QUSJNS5/zBuHNSj+KciXjBuzQBzU= Message-ID: <5256B671.2040105@pcbsd.org> Date: Thu, 10 Oct 2013 10:15:13 -0400 From: Kris Moore User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-current@freebsd.org Subject: Re: BE Loader Menu (was Re: rcs) References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> <52558779.2070203@pcbsd.org> <517D65A3D61F684FAE2B2EC2D2DA06C3@fisglobal.com> <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> <59.81.16944.C6136525@cdptpa-oedge02> In-Reply-To: <59.81.16944.C6136525@cdptpa-oedge02> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 14:15:16 -0000 On 10/10/2013 00:47, Thomas Mueller wrote: > Sorry for previous typo in From: line, missing right angle bracket at end. > Then, in a finger error, I resent that message just before finding the error and making the needed correction. > > from Devin Teske: > >> I'm late to the party again ;D (didn't realize the rcs thread had turned BE) >> Both problems can be solved. >> The loading of the kernel *after* choosing your boot device is trivial. >> We've been doing it at $work for *years* (almost a decade?) >> I can put that in, whenever. Probably at the same time as implementing >> the live/dynamic BE menus for selecting the root device. > I'd like to know how to boot FreeBSD >= 9.1 with grub2. > > Following the instructions under $PORTSDIR/sysutils/grub2 > > insmod ufs2 > set root=(hd0,gpt3) > kfreebsd /boot/loader > boot > > stopped working around FreeBSD 9.1-stable. > > I used Super Grub2 Disk image on the System Rescue CD written to USB stick. > > Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the System Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but haven't tested that yet. > > What is the method you or PC-BSD uses? > > I want to use it on FreeBSD 9.2 and 10-current. > > I tried visiting pcbsd.org website but couldn't find any details. > > Tom > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" We use the same port, but have some custom grub.d/ scripts which builds our /boot/grub/grub.cfg files. https://github.com/pcbsd/pcbsd/tree/master/src-sh/pc-extractoverlay/ports-overlay/usr/local/etc/grub.d The scripts do basic stuff like parsing output of "beadm" and creating a list of Boot-Environment menus to build. Along with parsing /boot/loader.conf, /boot/device.hints and friends. Lastly it even has code to mount each of your BEs and copy the resulting grub.cfg file into each, so that you have a unified menu regardless of which BE you are currently booting. One thing that I really want to fix is detecting which kernel modules have what depends. Currently I have to ensure that /boot/loader.conf has both the target module + depends in order for GRUB to load them properly. If anybody wants to help hack on these and make them more "FreeBSD generic" I think it could eventually go into the ports tree for everybody. When grub-mkconfig is run, it generates a ZFS / BE specific boot-script, with entries that look like this: --------------------------------------------------------------- submenu "PC-BSD (default) - 2013-08-27 14:23" { menuentry "Normal Bootup" { insmod zfs search -s -l tank1 kfreebsd /ROOT/default/@/boot/kernel/kernel kfreebsd_module /ROOT/default/@/boot/zfs/zpool.cache type=/boot/zfs/zpool.cache set kFreeBSD.vfs.root.mountfrom=zfs:tank1/ROOT/default kfreebsd_module_elf /ROOT/default/@/boot/kernel/siis.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/sdhci.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/geom_journal.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/geom_mirror.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/geom_eli.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/aesni.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/zfs.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/tmpfs.ko kfreebsd_module_elf /ROOT/default/@/boot/modules/nvidia.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/dummynet.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/ipfw_nat.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/ipdivert.ko kfreebsd_module_elf /ROOT/default/@/boot/modules/vboxdrv.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/zlib.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/opensolaris.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/linux.ko kfreebsd_module_elf /ROOT/default/@/boot/kernel/crypto.ko set kFreeBSD.hint.fdc.0.at=isa set kFreeBSD.hint.fdc.0.port=0x3F0 set kFreeBSD.hint.fdc.0.irq=6 set kFreeBSD.hint.fdc.0.drq=2 set kFreeBSD.hint.fd.0.at=fdc0 set kFreeBSD.hint.fd.0.drive=0 set kFreeBSD.hint.fd.1.at=fdc0 set kFreeBSD.hint.fd.1.drive=1 set kFreeBSD.hint.atkbdc.0.at=isa set kFreeBSD.hint.atkbdc.0.port=0x060 set kFreeBSD.hint.atkbd.0.at=atkbdc set kFreeBSD.hint.atkbd.0.irq=1 set kFreeBSD.hint.psm.0.at=atkbdc set kFreeBSD.hint.psm.0.irq=12 set kFreeBSD.hint.sc.0.at=isa set kFreeBSD.hint.sc.0.flags=0x100 set kFreeBSD.hint.uart.0.at=isa set kFreeBSD.hint.uart.0.port=0x3F8 set kFreeBSD.hint.uart.0.flags=0x10 set kFreeBSD.hint.uart.0.irq=4 set kFreeBSD.hint.uart.1.at=isa set kFreeBSD.hint.uart.1.port=0x2F8 set kFreeBSD.hint.uart.1.irq=3 set kFreeBSD.hint.ppc.0.at=isa set kFreeBSD.hint.ppc.0.irq=7 set kFreeBSD.hint.atrtc.0.at=isa set kFreeBSD.hint.atrtc.0.port=0x70 set kFreeBSD.hint.atrtc.0.irq=8 set kFreeBSD.hint.attimer.0.at=isa set kFreeBSD.hint.attimer.0.port=0x40 set kFreeBSD.hint.attimer.0.irq=0 set kFreeBSD.hint.wbwd.0.at=isa set kFreeBSD.hint.psm.0.flags=0x1000 set kFreeBSD.kern.ipc.shmseg=1024 set kFreeBSD.kern.ipc.shmmni=1024 set kFreeBSD.kern.maxproc=10000 set kFreeBSD.legal.intel_ipw.license_ack=1 set kFreeBSD.legal.intel_iwi.license_ack=1 set kFreeBSD.vfs.zfs.prefetch_disable=1 set kFreeBSD.hint.acpi_throttle.0.disabled=1 set kFreeBSD.machdep.disable_mtrrs=1 set kFreeBSD.kern.geom.eli.visible_passphrase=2 } -- Kris Moore PC-BSD Software iXsystems From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 14:19:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BB31BE62 for ; Thu, 10 Oct 2013 14:19:15 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 57F142FA5 for ; Thu, 10 Oct 2013 14:19:15 +0000 (UTC) Received: by mail-we0-f173.google.com with SMTP id u57so2596522wes.4 for ; Thu, 10 Oct 2013 07:19:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=ceFWosDrMmn6W8YnZCOGwVqGcSB7Jheg+eWT5NIEiik=; b=UpcN4APB/SPg85A3WNVEC4IOsMxxkzbxAwex4taOHxZ3+Y9qzIGj+y5gNVvssIDnjN SE1agU6gvydgsmtg40xnvIWgDQCbDHqSvNgI4xncTYz0GOAOwusYkQIaIQS1oJDBAiXm T3WRS4ykp70KhobZpL/RhOV6Ep+tTiQ2Jn/Z7NBnjZ/3WQFLn5SwT2JiMTmBQHEWeRMD zMiEhcFXQmFjSS7NJn8FbyksG/dznJLNHJOjnKK4QRMycOmDlRlX1leGRZ5IQ2UFeAN0 jGruFFDzdphc4jyPxezWwGjTbBmx5CUw20fDZw+TaBIof340bJpuit+rpjWS9dhI8iT8 WJYQ== X-Received: by 10.180.160.178 with SMTP id xl18mr8072566wib.61.1381414753670; Thu, 10 Oct 2013 07:19:13 -0700 (PDT) Received: from [192.168.1.129] ([193.173.55.180]) by mx.google.com with ESMTPSA id gp9sm25907266wib.8.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 07:19:13 -0700 (PDT) Message-ID: <5256B761.4050301@gmail.com> Date: Thu, 10 Oct 2013 16:19:13 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: FreeBSD Subject: FreeBSD 10 and zfsd Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 14:19:15 -0000 When i started using ZFS on FreeBSD I quickly found out that hot spares are not possible on FreeBSD. I was told that with zfsd it should be possible and that it would be included in FreeBSD 10. Is there some info about the zfsd function and how it could be used? regards Johan Hendriks From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 14:25:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 25F79328 for ; Thu, 10 Oct 2013 14:25:01 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from smtpauth4.wiscmail.wisc.edu (wmauth4.doit.wisc.edu [144.92.197.145]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E8F38201A for ; Thu, 10 Oct 2013 14:25:00 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from avs-daemon.smtpauth4.wiscmail.wisc.edu by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) id <0MUG00200INF9H00@smtpauth4.wiscmail.wisc.edu> for freebsd-current@freebsd.org; Thu, 10 Oct 2013 09:24:56 -0500 (CDT) X-Spam-PmxInfo: Server=avs-4, Version=6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.10.10.141214, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from wanderer.tachypleus.net (unknown [140.105.20.242]) by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPSA id <0MUG0052UBSUPJ10@smtpauth4.wiscmail.wisc.edu>; Thu, 10 Oct 2013 06:55:45 -0500 (CDT) Message-id: <525695BD.7060706@freebsd.org> Date: Thu, 10 Oct 2013 13:55:41 +0200 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 To: Allan Jude , freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> <5254F582.1040406@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> <5256509E.3000604@freebsd.org> <52565555.8030906@allanjude.com> In-reply-to: <52565555.8030906@allanjude.com> X-Enigmail-Version: 1.5.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 14:25:01 -0000 On 10/10/13 09:20, Allan Jude wrote: > On 2013-10-10 03:00, Nathan Whitehorn wrote: >> On 10/09/13 18:55, Teske, Devin wrote: >>> On Oct 8, 2013, at 11:19 PM, Nathan Whitehorn wrote: >>> >>>> On 10/09/13 01:13, Allan Jude wrote: >>>>> On 2013-10-08 16:17, Nathan Whitehorn wrote: >>>>>> On 10/07/13 21:59, Allan Jude wrote: >>>>>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>>>>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>>>>>> sector gnop trick, and optional GELI encryption. We would like to commit >>>>>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>>>>> obvious bugs before we send it off to re@ to get it committed. >>>>>>> >>>>>>> It includes a single configuration menu that allows you to select all of >>>>>>> the required details, including which drives to use (gets details from >>>>>>> camcontrol, also includes an inspection utility that presents the >>>>>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>>>>> ZFS RAID level to use (taking in to consideration the selected number of >>>>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>>>> >>>>>>> >>>>>>> Additional, it includes some other changes to bsdinstall: >>>>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>>>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>>>>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>>>>> feature has been combined into the regular 'services to enable' dialog >>>>>>> and enabled by default >>>>>>> >>>>>>> >>>>>>> You can browse the patches here: >>>>>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>>>> >>>>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>>>> >>>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>>>> >>>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>>>> >>>>>>> >>>>>>> We look forward to your feedback >>>>>>> >>>>>> Thanks for doing this! I had a few comments: >>>>>> 1. ZFS is not bootable on all architectures. Could you adjust that menu >>>>>> item to only display for i386, amd64, and (I think?) sparc64. Use uname >>>>>> -m, not -p, for this. >>>>> I had not considered that, I'll make that change >>>>> >>>>>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>>>>> instead of GPT. >>>>> I'll disable sparc64 as well >>>>> >>>>>> 2. Why are you using camcontrol? That is guaranteed not to work on >>>>>> non-CAM systems. You should use the GEOM ident string if you need an ID. >>>>> The GEOM ident string doesn't do enough to help the user identify which >>>>> drive is which. >>>>> More data is not exposed anywhere that I could find >>>>> >>>>> What we really need, is dev.ada.0.desc% like we have for network >>>>> interfaces and a slew of other devices. GEOM data is great, but it is >>>>> not exposed in a shell friendly way any place that I could find, other >>>>> than the sysctl with DOT and XML data. >>>> This is one of the reasons the partition editor is written in C. There >>>> are a few other odd corner-cases where C is much more powerful than the >>>> command-line for the GEOM operations that partedit needs to do. I'm not >>>> sure how to usefully get it just from the shell. You can see how to do >>>> it in C in the boot_disk() routine of partedit/auto_part.c. >>>> >>>>>> 3. Any plans to integrate this into the regular partition editor? ZFS >>>>>> support is important enough that I will definitely not get in the way, >>>>>> even as a bolt-on, but it would be a shame for it to stay that way. The >>>>>> editor is also designed for ZFS to be added. >>>>> I am a sysadmin, not a programmer. I can't write C. Most people >>>>> deploying servers can't write C. I agree with Devin Teske, if everything >>>>> was in shell it would be a lot more usable for non-developers, who >>>>> probably make up the majority of people who deploy FreeBSD. >>>> There are some cases the other way too. Devin is probably the most >>>> shell-proficient FreeBSD committer. >>> Well, there's jilles ;D (he writes/maintains the sh(1) implementation itself). >>> >>> >>>> I certainly can't write shell >>>> scripts at that level, which means that for me bsdconfig, for example, >>>> is effectively read-only (and quite hard to read as well). >>> In the past few days of working on the bsdinstall_zfs patch-set with Allan >>> Jude, I learned something new actually. >>> >>> It seems that sh(1) doesn't suffer so much from this "read only" concept. >>> >>> Imagine you're starting a new C project on an operating system that has >>> all new syscalls and all new APIs that you've never seen. Would be pretty >>> hard, no doubt. Now imagine that you're thrown a life-line called POSIX >>> and hey, now you're slinging code in MinGW on Windows when you don't >>> know a lick of M$ syscalls or APIs. >>> >>> In a similar manner, I've witnessed functionality be added that is truly >>> functional *without* using any of the API calls. Then I come in and do >>> a round of optimizations to leverage the existing API. >>> >>> Shell is kinda like that... >>> >>> I'm noticing Allan Jude doesn't know all the API calls yet (who could? other >>> than me of course -- and even I have trouble remembering them _all_) yet >>> this doesn't phase him (or others) from jumping in and lending a hand. >>> >>> No different than C, but the read-only aspect is lessened significantly I >>> believe because there are so many people out there that know enough >>> good shell syntax and are just a stone's throw away from *great* shell >>> syntax (which I must admit jilles helped me cross that boundary). >>> >>> I think in C, the read-only aspect is greater because its harder to parcel-out >>> the functions for a unit-test; harder to inject new code; and harder to get >>> to a functioning end-state. >> Look, I have no doubt that in the right hands shell can do amazing >> things and C can be badly written. That isn't the issue though. My >> statement was purely that most FreeBSD developers (me included) are more >> comfortable with C than shell when used at the kind of level involved >> here. This is not a value judgment but a statement of fact. Whether or >> not, at some platonic level, shell or C or python or whatever are more >> or less read-only is not the point here. The point is that I, and I >> suspect many other developers, cannot write (or read) very advanced >> levels of shell scripting but can read and write the equivalent programs >> when written in C in many cases. It's what the rest of the system is >> written in and what we spend most of our time using. Whether this should >> be the case or not is immaterial; the fact remains that shell scripting >> at any but a very basic level does introduce a very large barrier to >> entry for probably a large majority of committers. >> >> This is not always a problem -- especially if using something more >> obscure allows very active development by the set of people working on >> it -- but does reduce the set of people who can make modifications >> substantially. I have no ability to change, or understand, most of >> bsdconfig, for example. This isn't a problem since you are doing all the >> work and there is no reason I would need to or want to make changes to >> it. But it could become a problem in a part of the system to which >> multiple people needed to contribute. It's about other people's comfort >> zones and knowledge in the end. >> -Nathan >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > I definately see your point, but the code going in to the zfsboot part > in particular, is not that advanced. I started this project two weeks > ago with a well below average knowledge of shell script, a minor bit of > experience in php, and no real programming experience to speak of. > > I wrote most of the code that actually does things, Devin just cleaned > it up (I didn't know anything about shstyle or the rules) and pointed me > at some handy subroutines he had written to avoid writing out 20 lines > of code every time I wanted to display a dialog box > > I wouldn't say any of what is in the proposed patches to bsdinstall is > unmaintainable, and it definately makes it much more approachable for > sysadmins who are the ones that actually need to be able to script > bsdinstall, and generate various methods of automated deployment. This > is a very important feature if we want FreeBSD to be taken seriously for > deployment in mass virtualization environments (do not make my say > cloud. we saw a great sign in Malta at some street festival "what is > cloud?") Sorry, I think you misunderstood me. I really appreciate your work, and the ZFS stuff, as I said, is not that complex so there's no problem there. Aside from a couple of issues I mentioned (with sparc, etc.), it seems like a very good step forward. What I *was* trying to do was discourage you from rewriting partedit as a shell script and to encourage unifying the ZFS backend into partedit at some point in the future significantly different from now. I also wanted to mention that bsdinstall is completely scriptable (although not the new ZFS code, I guess...) and has been for some time. Only the initial release that shipped with 9.0 was not. There's a lengthy discussion of how this works in the man page. The scripting support is extremely flexible (you can run an arbitrary shell script in addition to the usual installation steps) and lets installations from PXE or media operate completely unattended. -Nathan From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 15:24:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 03507660 for ; Thu, 10 Oct 2013 15:24:58 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BA5BD245D for ; Thu, 10 Oct 2013 15:24:57 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id v2so1898265qcr.6 for ; Thu, 10 Oct 2013 08:24:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=yBxRuZHcK1yyz0iQeNVArfWZ4ChVpuV8SlxSdRJW/tI=; b=Jqx0z/APouDfkvLMGVimDjoiNbuc8Xc7LCiEyOi6NxT6Imqm3ykmObEMoKtNV5Y9sy FZCNTivxAic7fM/mBZJJFUHQOacy0xZjCQj3auPIQ1TrNpVYHp000ZCuT/ZbzIx9Gb/v VUXQ2Gm09agmxEUbaid/A55ZfISesGQmIW4ov90DV6ZXB3Whm6/XaIKDZFG2yPlvBfx4 HzIohEbT+lhcWcBDBlF5HXkeQot+dviIBzM/Z8GDauMg0Wf9cqYGxeU77pmbHVDtI8ld D8RPgVmlGMkTd/0BPLakqKThIC8QQbteW6jZEjk5siQjZX4sDu0eozspqXXhD0Hi8Y5o yIRQ== MIME-Version: 1.0 X-Received: by 10.49.107.226 with SMTP id hf2mr13999217qeb.17.1381418696839; Thu, 10 Oct 2013 08:24:56 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.49.39.97 with HTTP; Thu, 10 Oct 2013 08:24:56 -0700 (PDT) In-Reply-To: <5256B761.4050301@gmail.com> References: <5256B761.4050301@gmail.com> Date: Thu, 10 Oct 2013 09:24:56 -0600 X-Google-Sender-Auth: 03h1i5QXF4Pro_YaWm_0ITzT_as Message-ID: Subject: Re: FreeBSD 10 and zfsd From: Alan Somers To: Johan Hendriks Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 15:24:58 -0000 On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks wrote: > When i started using ZFS on FreeBSD I quickly found out that hot spares are > not possible on FreeBSD. > I was told that with zfsd it should be possible and that it would be > included in FreeBSD 10. > > Is there some info about the zfsd function and how it could be used? zfsd is currently not in FreeBSD/head and won't make it into 10, but you can still get the source code from its project branch. It's being used in production by at least two companies. http://svnweb.freebsd.org/base/projects/zfsd/head/ > > regards > Johan Hendriks > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 15:30:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3316C9A3; Thu, 10 Oct 2013 15:30:48 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E396224D6; Thu, 10 Oct 2013 15:30:47 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa03.fnfis.com (8.14.5/8.14.5) with ESMTP id r9AFUTT9024458 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 10 Oct 2013 10:30:29 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.02.0309.002; Thu, 10 Oct 2013 10:30:28 -0500 From: "Teske, Devin" To: Nathan Whitehorn Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxRBPPJPIP8ZCyUiSsjBzr2++AA== Date: Thu, 10 Oct 2013 15:30:28 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC508BE@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> <5254F582.1040406@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> <5256509E.3000604@freebsd.org> <52565555.8030906@allanjude.com> <525695BD.7060706@freebsd.org> In-Reply-To: <525695BD.7060706@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-10_04:2013-10-10,2013-10-10,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 15:30:48 -0000 On Oct 10, 2013, at 4:55 AM, Nathan Whitehorn wrote: > On 10/10/13 09:20, Allan Jude wrote: >> On 2013-10-10 03:00, Nathan Whitehorn wrote: >>> On 10/09/13 18:55, Teske, Devin wrote: >>>> On Oct 8, 2013, at 11:19 PM, Nathan Whitehorn wrote: >>>>=20 >>>>> On 10/09/13 01:13, Allan Jude wrote: >>>>>> On 2013-10-08 16:17, Nathan Whitehorn wrote: >>>>>>> On 10/07/13 21:59, Allan Jude wrote: >>>>>>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>>>>>> implement installing on a ZFS pool. It supports both GPT and MBR, = the 4k >>>>>>>> sector gnop trick, and optional GELI encryption. We would like to = commit >>>>>>>> this in time for 10.0-BETA1 so it needs some testing to work out a= ny >>>>>>>> obvious bugs before we send it off to re@ to get it committed. >>>>>>>>=20 >>>>>>>> It includes a single configuration menu that allows you to select = all of >>>>>>>> the required details, including which drives to use (gets details = from >>>>>>>> camcontrol, also includes an inspection utility that presents the >>>>>>>> detailed output of camcontrol inquiry/identify, and gpart show), w= hat >>>>>>>> ZFS RAID level to use (taking in to consideration the selected num= ber of >>>>>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> Additional, it includes some other changes to bsdinstall: >>>>>>>> 1. Change the default to the 'non-standard keyboard mapping' promp= t to no >>>>>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address wit= h just 1 >>>>>>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>>>>>> feature has been combined into the regular 'services to enable' di= alog >>>>>>>> and enabled by default >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> You can browse the patches here: >>>>>>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>>>>>=20 >>>>>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>>>>>=20 >>>>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>>>>>=20 >>>>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> We look forward to your feedback >>>>>>>>=20 >>>>>>> Thanks for doing this! I had a few comments: >>>>>>> 1. ZFS is not bootable on all architectures. Could you adjust that = menu >>>>>>> item to only display for i386, amd64, and (I think?) sparc64. Use u= name >>>>>>> -m, not -p, for this. >>>>>> I had not considered that, I'll make that change >>>>>>=20 >>>>>>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>>>>>> instead of GPT. >>>>>> I'll disable sparc64 as well >>>>>>=20 >>>>>>> 2. Why are you using camcontrol? That is guaranteed not to work on >>>>>>> non-CAM systems. You should use the GEOM ident string if you need a= n ID. >>>>>> The GEOM ident string doesn't do enough to help the user identify wh= ich >>>>>> drive is which. >>>>>> More data is not exposed anywhere that I could find >>>>>>=20 >>>>>> What we really need, is dev.ada.0.desc% like we have for network >>>>>> interfaces and a slew of other devices. GEOM data is great, but it is >>>>>> not exposed in a shell friendly way any place that I could find, oth= er >>>>>> than the sysctl with DOT and XML data. >>>>> This is one of the reasons the partition editor is written in C. There >>>>> are a few other odd corner-cases where C is much more powerful than t= he >>>>> command-line for the GEOM operations that partedit needs to do. I'm n= ot >>>>> sure how to usefully get it just from the shell. You can see how to do >>>>> it in C in the boot_disk() routine of partedit/auto_part.c. >>>>>=20 >>>>>>> 3. Any plans to integrate this into the regular partition editor? Z= FS >>>>>>> support is important enough that I will definitely not get in the w= ay, >>>>>>> even as a bolt-on, but it would be a shame for it to stay that way.= The >>>>>>> editor is also designed for ZFS to be added. >>>>>> I am a sysadmin, not a programmer. I can't write C. Most people >>>>>> deploying servers can't write C. I agree with Devin Teske, if everyt= hing >>>>>> was in shell it would be a lot more usable for non-developers, who >>>>>> probably make up the majority of people who deploy FreeBSD. >>>>> There are some cases the other way too. Devin is probably the most >>>>> shell-proficient FreeBSD committer. >>>> Well, there's jilles ;D (he writes/maintains the sh(1) implementation = itself). >>>>=20 >>>>=20 >>>>> I certainly can't write shell >>>>> scripts at that level, which means that for me bsdconfig, for example, >>>>> is effectively read-only (and quite hard to read as well). >>>> In the past few days of working on the bsdinstall_zfs patch-set with A= llan >>>> Jude, I learned something new actually. >>>>=20 >>>> It seems that sh(1) doesn't suffer so much from this "read only" conce= pt. >>>>=20 >>>> Imagine you're starting a new C project on an operating system that has >>>> all new syscalls and all new APIs that you've never seen. Would be pre= tty >>>> hard, no doubt. Now imagine that you're thrown a life-line called POSIX >>>> and hey, now you're slinging code in MinGW on Windows when you don't >>>> know a lick of M$ syscalls or APIs. >>>>=20 >>>> In a similar manner, I've witnessed functionality be added that is tru= ly >>>> functional *without* using any of the API calls. Then I come in and do >>>> a round of optimizations to leverage the existing API. >>>>=20 >>>> Shell is kinda like that... >>>>=20 >>>> I'm noticing Allan Jude doesn't know all the API calls yet (who could?= other >>>> than me of course -- and even I have trouble remembering them _all_) y= et >>>> this doesn't phase him (or others) from jumping in and lending a hand. >>>>=20 >>>> No different than C, but the read-only aspect is lessened significantl= y I >>>> believe because there are so many people out there that know enough >>>> good shell syntax and are just a stone's throw away from *great* shell >>>> syntax (which I must admit jilles helped me cross that boundary). >>>>=20 >>>> I think in C, the read-only aspect is greater because its harder to pa= rcel-out >>>> the functions for a unit-test; harder to inject new code; and harder t= o get >>>> to a functioning end-state. >>> Look, I have no doubt that in the right hands shell can do amazing >>> things and C can be badly written. That isn't the issue though. My >>> statement was purely that most FreeBSD developers (me included) are more >>> comfortable with C than shell when used at the kind of level involved >>> here. This is not a value judgment but a statement of fact. Whether or >>> not, at some platonic level, shell or C or python or whatever are more >>> or less read-only is not the point here. The point is that I, and I >>> suspect many other developers, cannot write (or read) very advanced >>> levels of shell scripting but can read and write the equivalent programs >>> when written in C in many cases. It's what the rest of the system is >>> written in and what we spend most of our time using. Whether this should >>> be the case or not is immaterial; the fact remains that shell scripting >>> at any but a very basic level does introduce a very large barrier to >>> entry for probably a large majority of committers. >>>=20 >>> This is not always a problem -- especially if using something more >>> obscure allows very active development by the set of people working on >>> it -- but does reduce the set of people who can make modifications >>> substantially. I have no ability to change, or understand, most of >>> bsdconfig, for example. This isn't a problem since you are doing all the >>> work and there is no reason I would need to or want to make changes to >>> it. But it could become a problem in a part of the system to which >>> multiple people needed to contribute. It's about other people's comfort >>> zones and knowledge in the end. >>> -Nathan >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >> I definately see your point, but the code going in to the zfsboot part >> in particular, is not that advanced. I started this project two weeks >> ago with a well below average knowledge of shell script, a minor bit of >> experience in php, and no real programming experience to speak of. >>=20 >> I wrote most of the code that actually does things, Devin just cleaned >> it up (I didn't know anything about shstyle or the rules) and pointed me >> at some handy subroutines he had written to avoid writing out 20 lines >> of code every time I wanted to display a dialog box >>=20 >> I wouldn't say any of what is in the proposed patches to bsdinstall is >> unmaintainable, and it definately makes it much more approachable for >> sysadmins who are the ones that actually need to be able to script >> bsdinstall, and generate various methods of automated deployment. This >> is a very important feature if we want FreeBSD to be taken seriously for >> deployment in mass virtualization environments (do not make my say >> cloud. we saw a great sign in Malta at some street festival "what is >> cloud?") >=20 > Sorry, I think you misunderstood me. I really appreciate your work, and > the ZFS stuff, as I said, is not that complex so there's no problem > there. Aside from a couple of issues I mentioned (with sparc, etc.), it > seems like a very good step forward. What I *was* trying to do was > discourage you from rewriting partedit as a shell script and to > encourage unifying the ZFS backend into partedit at some point in the > future significantly different from now. >=20 > I also wanted to mention that bsdinstall is completely scriptable > (although not the new ZFS code, I guess...) Oh, but it is. The following variables have sensible defaults and are designed to be exported in a bsdinstall script to customize the actions performed by the zfsboot script: dteske@scribe9.vicor.com scripts $ grep '^: ' zfsboot=20 : ${ZFSBOOT_POOL_NAME:=3Dzroot} : ${ZFSBOOT_BEROOT_NAME:=3Dbootenv} : ${ZFSBOOT_BOOTFS_NAME:=3Ddefault} : ${ZFSBOOT_VDEV_TYPE:=3Dstripe} : ${ZFSBOOT_GNOP_4K_FORCE_ALIGN:=3D1} : ${ZFSBOOT_GELI_ENCRYPTION:=3D} : ${ZFSBOOT_GELI_POOL_NAME:=3Dbootpool} : ${ZFSBOOT_GELI_BOOT_SIZE:=3D2g} : ${ZFSBOOT_GELI_KEY_FILE:=3D/boot/encryption.key} : ${ZFSBOOT_DISKS:=3D} : ${ZFSBOOT_PARTITION_SCHEME:=3DGPT} : ${ZFSBOOT_SWAP_SIZE:=3D2g} Notice the ZFSBOOT_ prefix matching the script name. These may not be the final names used as an overall effort is made (given time) to conflate the scripting variables and general namespace. > and has been for some time. The type of scripting set forth by bsdinstall is not the same kind of scripting set forth by bsdconfig. That being said, I've not yet made an effort to close the gap on bsdinstall scripting (to make it like bsdconfig scripting). In bsdconfig, we can literally load a sysinstall "install.cfg" file and there is no need to for a complicated embedding system such as bsdinstall has (wherein the "script" is actually a multi-part file). A lot of people have scoffed at backward compatibility because it would not be easy. However, I see a pretty big carrot dangling in front of the backward compatibility effort... It's not the act of implementing the individual reswords that's going to bring the biggest value-add, but instead the bringing back of the process-flow to deployment that will see the greatest gain in functionality. By this, I mean that currently you invoke bsdinstall and it runs through a UX given a set of values set in variables. This is sub-optimal if you don't like the UX choices -- better to instead allow the script to take the reigns and do things by way of having the script drive (in sysinstall, this amounts to the fact that if "install.cfg" doesn't call diskPartitionWrite or doesn't call distExtractAll, then those steps are not performed). In bsdinstall, a change in focus to allow the script to drive *could* be done by requiring the user to fork-exec to a bunch of scripts -- and in-turn then requiring each/every custom setting to be *export*ed... but ultimately the best bang-for-your-buck is going to come from (I'll say it again) namespace conflation (writing the functionality as a series of includable functions that are run in the same namespace as the script that is driving). Naturally, a bunch of functions can be lost if you don't know where to look for them, and that comes back full-circle to `script.subr' and `variable.subr' as the "points of discovery" (besides a man-page; which is where sys- install documented its own reswords). > Only the initial release that shipped with 9.0 was not. There's a > lengthy discussion of how this works in the man page. *nods* > The scripting > support is extremely flexible (you can run an arbitrary shell script in > addition to the usual installation steps) and lets installations from > PXE or media operate completely unattended. Yes, but I've been taking to simply creating /etc/installerconf and completely bypassing the scripting that's documented in the man-page *because* I abhor multi-part file which requires a split-architecture approach to installation (no like). Sysinstall often required me to do the same thing. Whereas in sysinstall the problem was that you couldn't speak native shell in the install.cfg file (requiring you to call out to a "system" resword to execute a script which generates a side "install.cfg" later brought back in with the "loadConfig" resword, bsdinstall instead requires me to have -- in the multi-part script it loads -- a preamble and a setup script and this causes a similar dichotomy in passing information between the stages). In bsdconfig, I worked extremely hard to solve that issue. The end- result is that both problems are solved. The problem of sysinstall is gone because the "install.cfg" file becomes a shell script so you can then start speaking native shell in it. The multi-part problem is gone when you provide all the reswords in the native language (conflated namespace). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 15:36:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6D3FCBFB; Thu, 10 Oct 2013 15:36:58 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2A8732527; Thu, 10 Oct 2013 15:36:58 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n5so1492584oag.41 for ; Thu, 10 Oct 2013 08:36:57 -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=DVvfA+xagTfANZNgBuyx3oBsteT2/DkI5kp0HWiwz1k=; b=KdQwUhIt6dXCQh5Ls/EiSY8EdPyHXLwLSBTzANzANdh0RtwgDsozVUzOb+bUcsMx/j UyL8FltHmbHXCNsQ4mf1av07IVYHKJmz+44Oim+z01cGG3JpXN8W/0jc/dUKQjmZlwBQ blw+OjlAFVhIXZUi4QQpgOpwcf6vv+byIai2dZwaCBbhpqB4rFXqBu9Nv0SKJGlpHK6G a3VPpjnv8RAu8HXZY14+d4mDXSM4fhRezPE+vrKVE/R9ilPFRgnCHBZY4PL9L4BNl6/F /yVFaVxhMoS3EF291cgEt0taci/jVdDDGoCYraDIuYBRhuGtnAZV496atd4O4Iync4Y4 KzQA== MIME-Version: 1.0 X-Received: by 10.60.134.51 with SMTP id ph19mr540773oeb.122.1381419417314; Thu, 10 Oct 2013 08:36:57 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Thu, 10 Oct 2013 08:36:57 -0700 (PDT) In-Reply-To: References: <5256B761.4050301@gmail.com> Date: Thu, 10 Oct 2013 11:36:57 -0400 Message-ID: Subject: Re: FreeBSD 10 and zfsd From: Outback Dingo To: Alan Somers Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Johan Hendriks , FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 15:36:58 -0000 On Thu, Oct 10, 2013 at 11:24 AM, Alan Somers wrote: > On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks > wrote: > > When i started using ZFS on FreeBSD I quickly found out that hot spares > are > > not possible on FreeBSD. > > I was told that with zfsd it should be possible and that it would be > > included in FreeBSD 10. > > > > Is there some info about the zfsd function and how it could be used? > > zfsd is currently not in FreeBSD/head and won't make it into 10, but > you can still get the source code from its project branch. It's being > used in production by at least two companies. > > http://svnweb.freebsd.org/base/projects/zfsd/head/ > > might be easier to just cut a diff of it, as it 2+ months behind CURRENT as it is in this branch, be nice to review and do some testing on, but getting a diff from that to CURRENT might prove a bit difficult unless the branch was updated > > > > regards > > Johan Hendriks > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 16:07:19 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3A2A58C7 for ; Thu, 10 Oct 2013 16:07:19 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 079722767 for ; Thu, 10 Oct 2013 16:07:18 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r9AG6fZ8046851 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 10 Oct 2013 09:06:45 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5256D08F.5060101@freebsd.org> Date: Fri, 11 Oct 2013 00:06:39 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: "Teske, Devin" Subject: Re: BE Loader Menu (was Re: rcs) References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> <52558779.2070203@pcbsd.org> <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 16:07:19 -0000 On 10/10/13 1:05 AM, Teske, Devin wrote: > > I'm late to the party again ;D (didn't realize the rcs thread had turned BE) > > Both problems can be solved. > The loading of the kernel *after* choosing your boot device is trivial. > We've been doing it at $work for *years* (almost a decade?) > > I can put that in, whenever. Probably at the same time as implementing > the live/dynamic BE menus for selecting the root device. yeah it always pisses me of when the menu comes up after the kernel is loaded because 99% of the time, I'm in the menu because I want to boot a DIFFERENT kernel.. > > > From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 16:11:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6349CA8F for ; Thu, 10 Oct 2013 16:11:08 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 188C527CF for ; Thu, 10 Oct 2013 16:11:08 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r9AGB0r2046886 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 10 Oct 2013 09:11:03 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5256D192.8010902@freebsd.org> Date: Fri, 11 Oct 2013 00:10:58 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Jos Backus Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kimmo Paasiala , George Mitchell , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 16:11:08 -0000 On 10/9/13 11:59 PM, Jos Backus wrote: > On Oct 9, 2013 5:39 AM, "Kimmo Paasiala" wrote: >> On Wed, Oct 9, 2013 at 2:03 PM, George Mitchell > wrote: >>> On 10/09/13 03:20, Hans Ottevanger wrote: >>>> On 10/08/13 04:31, Lyndon Nerenberg wrote: >>>>> Okay folks, can we make a call about keeping the RCS tools in the > base? >>>>> The proponents wanting to remove RCS need to speak up and make their >>>>> technical case. >>>>> >>>> Technically it is quite simple: I need RCS to start versioning config >>>> files, even before starting any customization. I know about several >>>> others who do the same (and have not yet defected to Linux). >>>> >>>> I would like to see RCS to be put back into the tree for 10.0. If it >>>> really -has- to be victimized by the current anti-GPL crusade, it could >>>> be replaced by OpenRCS in 11. >>>> >>>> And as a long time hard-core user I would appreciate if this kind of >>>> changes were performed only after at least -some- public discussion. >>>> The way this change was sneaked in (though apparently with approval of >>>> core@), reminds me more of a Secret Society than of an Open Source >>>> project. >>>> >>>> Regards, >>>> >>>> Hans >>>> >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" >>> +1, enthusiastically. -- George >>> >> +1 also to OpenRCS allthough I hate anything related to RCS/CVS with a >> passion. I do however recognize the need for a simple revision control >> system in the base, svnlite would fill the need maybe but it's good to >> have other options too. >> >> -Kimmo > OK, but please, can we replace RCS with Fossil in 11 then? That adds a real > improvement to FreeBSD while giving people plenty of time to prepare. can fossil read rcs files? and how big is it compared to RCS? > > Jos > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 16:13:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 87740F69 for ; Thu, 10 Oct 2013 16:13:17 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5C3522810 for ; Thu, 10 Oct 2013 16:13:17 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 36E3920907 for ; Thu, 10 Oct 2013 12:13:03 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Thu, 10 Oct 2013 12:13:05 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=Jks5wJNgGacpiQjiT9ULzC+gbTI=; b=o0x Vtb58nqS/YFysw9P0Hr4/uhXOpVpK82w60xEUAdBIaYMR+9NicI7ARqsP5k7Kc1a 6wYN1tPibau42i4Rue5i34w8V+9NqpSX5UhrQu1ZntDimf0B98Bd/GTEt9/WZ64T NtAeOumJx2pOA2VcgXYRkHoL5AL+wdgJjIBcVi6I= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 50CF511BC17; Thu, 10 Oct 2013 12:13:03 -0400 (EDT) Message-Id: <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> X-Sasl-Enc: +FsoLlmEGFggMeX6HIUBi/pqnknD7uEkOmSdlQq8/1HK 1381421583 From: Mark Felder To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 In-Reply-To: References: <5256B761.4050301@gmail.com> Subject: Re: FreeBSD 10 and zfsd Date: Thu, 10 Oct 2013 11:13:03 -0500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 16:13:17 -0000 On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: > On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks > wrote: > > When i started using ZFS on FreeBSD I quickly found out that hot spares are > > not possible on FreeBSD. > > I was told that with zfsd it should be possible and that it would be > > included in FreeBSD 10. > > > > Is there some info about the zfsd function and how it could be used? > > zfsd is currently not in FreeBSD/head and won't make it into 10, but > you can still get the source code from its project branch. It's being > used in production by at least two companies. > So FreeBSD is going to have inferior ZFS management compared to Solaris/Illumos/etc for another 2+ years? Why are things like this allowed to miss releases? From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 16:38:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7FF84B36 for ; Thu, 10 Oct 2013 16:38:58 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 595F529B9 for ; Thu, 10 Oct 2013 16:38:58 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r9AGcqrf046990 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 10 Oct 2013 09:38:55 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5256D819.6060500@freebsd.org> Date: Fri, 11 Oct 2013 00:38:49 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Jos Backus Subject: Re: rcs References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 16:38:58 -0000 On 10/11/13 12:34 AM, Jos Backus wrote: > On Thu, Oct 10, 2013 at 9:10 AM, Julian Elischer > wrote: > > On 10/9/13 11:59 PM, Jos Backus wrote: > > [snip] > > OK, but please, can we replace RCS with Fossil in 11 then? > That adds a real > improvement to FreeBSD while giving people plenty of time to > prepare. > > can fossil read rcs files? and how big is it compared to RCS? > > > It seems there's some thought on importing CVS repos but according > to 'fossil help import', only the git fast-export format is supported. > In practice this means you'd loose history, yes. But it's not hard > to keep the old RCS files somewhere else in case that history is needed. > > http://www.fossil-scm.org/fossil/wiki?name=Import+CVS+Repositories > > I just built devel/fossil and it yields a single binary, > /usr/local/bin/fossil which clocks in at 1.8M. Given all the > functionality it provides (plus it is in a similar class as git, see > http://www.fossil-scm.org/index.html/doc/tip/www/fossil-v-git.wiki), > I think that's a steal. > > It was started by the author of SQlite. If we require some kind of > version control system in the base that's powerful, well-maintained > and BSD-licensed, this really seems like a no-brainer. well since people expect RCS.. it is not a no brainer. you are asking people to learn a whole new tool for functionality that is currently very simple.. edit file ci -l file add comment. > > Jos > -- > Jos Backus > jos at catnook.com From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 16:39:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AA125C68; Thu, 10 Oct 2013 16:39:16 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6D9A229C5; Thu, 10 Oct 2013 16:39:16 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id r9AGdF2D010888 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 10 Oct 2013 11:39:15 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Thu, 10 Oct 2013 11:39:14 -0500 From: "Teske, Devin" To: Julian Elischer Subject: Re: BE Loader Menu (was Re: rcs) Thread-Topic: BE Loader Menu (was Re: rcs) Thread-Index: AQHOxRG5GlF59UAvJ06VyRjwWpYzrQ== Date: Thu, 10 Oct 2013 16:39:13 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC50D64@LTCFISWMSGMB21.FNFIS.com> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> <52558779.2070203@pcbsd.org> <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> <5256D08F.5060101@freebsd.org> In-Reply-To: <5256D08F.5060101@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-10_06:2013-10-10,2013-10-10,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 16:39:16 -0000 On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: > On 10/10/13 1:05 AM, Teske, Devin wrote: >>=20 >> I'm late to the party again ;D (didn't realize the rcs thread had turned= BE) >>=20 >> Both problems can be solved. >> The loading of the kernel *after* choosing your boot device is trivial. >> We've been doing it at $work for *years* (almost a decade?) >>=20 >> I can put that in, whenever. Probably at the same time as implementing >> the live/dynamic BE menus for selecting the root device. >=20 > yeah it always pisses me of when the menu comes up after the kernel is lo= aded because 99% of the time, I'm in the menu because I want to boot a DIFF= ERENT kernel.. >=20 Same thought I had about 7 years ago. After hearing that others (especially you, Julian) think the same thoughts... I'm happily ready to merge a patch from VICOR to achieve this. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 16:42:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4DFCAE76 for ; Thu, 10 Oct 2013 16:42:26 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1B3462A2E for ; Thu, 10 Oct 2013 16:42:25 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-246-96.lns20.per2.internode.on.net [121.45.246.96]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r9AGgKvT047009 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 10 Oct 2013 09:42:22 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5256D8E9.10200@freebsd.org> Date: Fri, 11 Oct 2013 00:42:17 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: "Teske, Devin" Subject: Re: BE Loader Menu (was Re: rcs) References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <52542BD4.5070706@FreeBSD.org> <52542E1D.9000000@mu.org> <52555D1C.8010407@freebsd.org> <52558577.5020401@allanjude.com> <52558779.2070203@pcbsd.org> <13CA24D6AB415D428143D44749F57D720FC4B2A3@LTCFISWMSGMB21.FNFIS.com> <5256D08F.5060101@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC50D64@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC50D64@LTCFISWMSGMB21.FNFIS.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "" , Kris Moore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 16:42:26 -0000 On 10/11/13 12:39 AM, Teske, Devin wrote: > On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: > >> On 10/10/13 1:05 AM, Teske, Devin wrote: >>> I'm late to the party again ;D (didn't realize the rcs thread had turned BE) >>> >>> Both problems can be solved. >>> The loading of the kernel *after* choosing your boot device is trivial. >>> We've been doing it at $work for *years* (almost a decade?) >>> >>> I can put that in, whenever. Probably at the same time as implementing >>> the live/dynamic BE menus for selecting the root device. >> yeah it always pisses me of when the menu comes up after the kernel is loaded because 99% of the time, I'm in the menu because I want to boot a DIFFERENT kernel.. >> > Same thought I had about 7 years ago. After hearing that others > (especially you, Julian) think the same thoughts... > > I'm happily ready to merge a patch from VICOR to achieve this. PLEASE!.. put it up for review somewhere... I wonder if we can we get a reviewboard instance for the project some time? From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 16:45:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EF1A01E2 for ; Thu, 10 Oct 2013 16:45:52 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id C978A2A6C for ; Thu, 10 Oct 2013 16:45:52 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id C9D7821759 for ; Thu, 10 Oct 2013 16:45:49 +0000 (UTC) Message-ID: <5256D9D4.2030308@allanjude.com> Date: Thu, 10 Oct 2013 12:46:12 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173 References: <1381166916.122992963.5h9ygiri@frv45.ukr.net> <1381170764.32684.31088349.343931EE@webmail.messagingengine.com> <20131007185032.GA82932@hell.ukr.net> <20131007211201.GA89306@hell.ukr.net> <20131010092223.GA28347@hell.ukr.net> In-Reply-To: <20131010092223.GA28347@hell.ukr.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 16:45:53 -0000 On 2013-10-10 05:22, Vitalij Satanivskij wrote: > Same situation hapend yesterday again :( > > What's confuse me while trying to understend where I'm wrong > > > Firt some info. > > We have zfs pool "POOL" and one more zfs on it "POOL/zfs" > > POOL - have only primarycache enabled "ALL" > POOL/zfs - have both primay and secondary for "ALL" > > POOL have compression=lz4 > > POOL/zfs have none > > > POOL - have around 9TB data > > POOL/zfs - have 1TB > > Secondary cache have configuration - > > cache > gpt/cache0 ONLINE 0 0 0 > gpt/cache1 ONLINE 0 0 0 > gpt/cache2 ONLINE 0 0 0 > > gpt/cache0-2 it's intel sdd SSDSC2BW180A4 180gb > > So full real size for l2 is 540GB (realy 489gb) > > First question - data on l2arc will be compressed on not? > > Second in stats we see > > L2 ARC Size: (Adaptive) 2.08 TiB > > eary it was 1.1 1.4 ... > > So a) how cache can be biger than zfs it self > b) in case it's not compressed (answer for first question) how it an be biger than real ssd size? > > > one more coment if l2 arc size grove above phisical sizes I se next stats > > kstat.zfs.misc.arcstats.l2_cksum_bad: 50907344 > kstat.zfs.misc.arcstats.l2_io_error: 4547377 > > and growing. > > > System is r255173 with patch from rr255173 > > > At last maybe somebody have any ideas what's realy hapend... > > > > > > Vitalij Satanivskij wrote: > VS> > VS> One more question - > VS> > VS> we have two counter - > VS> > VS> kstat.zfs.misc.arcstats.l2_size: 1256609410560 > VS> kstat.zfs.misc.arcstats.l2_asize: 1149007667712 > VS> > VS> can anybody explain how to understand them i.e. l2_asize - real used space on l2arc an l2_size - uncompressed size, > VS> > VS> or maybe something else ? > VS> > VS> > VS> > VS> Vitalij Satanivskij wrote: > VS> VS> > VS> VS> Data on pool have compressratio around 1.4 > VS> VS> > VS> VS> On diferent servers with same data type and load L2 ARC Size: (Adaptive) can be diferent > VS> VS> > VS> VS> for example 1.04 TiB vs 1.45 TiB > VS> VS> > VS> VS> But it's all have same porblem - grow in time. > VS> VS> > VS> VS> > VS> VS> More stange for us - > VS> VS> > VS> VS> ARC: 80G Total, 4412M MFU, 5040M MRU, 76M Anon, 78G Header, 2195M Other > VS> VS> > VS> VS> 78G header size and ubnormal - > VS> VS> > VS> VS> kstat.zfs.misc.arcstats.l2_cksum_bad: 210920592 > VS> VS> kstat.zfs.misc.arcstats.l2_io_error: 7362414 > VS> VS> > VS> VS> sysctl's growing avery second. > VS> VS> > VS> VS> All part's of server (as hardware part's) in in normal state. > VS> VS> > VS> VS> After reboot no problem's for some period untile cache size grow to some limit. > VS> VS> > VS> VS> > VS> VS> > VS> VS> Mark Felder wrote: > VS> VS> MF> On Mon, Oct 7, 2013, at 13:09, Dmitriy Makarov wrote: > VS> VS> MF> > > VS> VS> MF> > How can L2 ARC Size: (Adaptive) be 1.44 TiB (up) with total physical size > VS> VS> MF> > of L2ARC devices 490GB? > VS> VS> MF> > > VS> VS> MF> > VS> VS> MF> http://svnweb.freebsd.org/base?view=revision&revision=251478 > VS> VS> MF> > VS> VS> MF> L2ARC compression perhaps? > VS> VS> MF> _______________________________________________ > VS> VS> MF> freebsd-current@freebsd.org mailing list > VS> VS> MF> http://lists.freebsd.org/mailman/listinfo/freebsd-current > VS> VS> MF> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > VS> VS> _______________________________________________ > VS> VS> freebsd-current@freebsd.org mailing list > VS> VS> http://lists.freebsd.org/mailman/listinfo/freebsd-current > VS> VS> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > VS> _______________________________________________ > VS> freebsd-current@freebsd.org mailing list > VS> http://lists.freebsd.org/mailman/listinfo/freebsd-current > VS> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Some background on L2ARC compression for you: http://wiki.illumos.org/display/illumos/L2ARC+Compression http://svnweb.freebsd.org/base?view=revision&revision=251478 Are you sure that compression on pool/zfs is off? it would normally inherit from the parent, so double check with: zfs get compression pool/zfs Is the data on pool/zfs related to the data on the root pool? if pool/zfs were a clone, and the data is actually used in both places, the newer 'single copy ARC' feature may come in to play: https://www.illumos.org/issues/3145 -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 17:01:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7C8BBB73 for ; Thu, 10 Oct 2013 17:01:42 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 539302B97 for ; Thu, 10 Oct 2013 17:01:42 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id ro12so2867130pbb.27 for ; Thu, 10 Oct 2013 10:01:35 -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=hE9TUxwyl1EVuEPM/7+9VzFoyyVL3fNHv8/cunLf+cw=; b=mIx/U83MSqB29XPIgSiZNijuFV75OJf0rNCJVJzAOOQlFjYJLryA1cSInSYzH+bDGy 0fy5/BosuGzEUpDN+cNbePfYtWeuNnKNiveMgojSFFwVlxA/hvpcIcwFH4BwMmj1l4eI BX95ogdBiaZXOwbrLpNc3oJ53z3TU18y+76A1paU2H3e/BG99JZBI+Rsq2ElxQ9fAf9q mo0jzOwc3jY3hKAfTrDGhlEyAbXjK5lZqD3yXb2Z6Fy3KnfMSM1QfHGlzIjCatppueNC 3dL17uWFb6ndw4krhFJYjDFa53Es5/mjfMuA4tRx8ypfPbMeT3QyubO+6hGgkvIn16Oe 3mGw== X-Gm-Message-State: ALoCoQl3cs7KEgtzZbkvmK4q8ZvJJJNLVI5LTqL0D82LCG/vKcmbwSB+ZQj04YesGcSWLyQK5xjW MIME-Version: 1.0 X-Received: by 10.68.185.36 with SMTP id ez4mr15228440pbc.144.1381422877368; Thu, 10 Oct 2013 09:34:37 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 09:34:37 -0700 (PDT) In-Reply-To: <5256D192.8010902@freebsd.org> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> Date: Thu, 10 Oct 2013 09:34:37 -0700 Message-ID: Subject: Re: rcs From: Jos Backus To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:01:42 -0000 On Thu, Oct 10, 2013 at 9:10 AM, Julian Elischer wrote: > On 10/9/13 11:59 PM, Jos Backus wrote: [snip] > OK, but please, can we replace RCS with Fossil in 11 then? That adds a real >> improvement to FreeBSD while giving people plenty of time to prepare. >> > can fossil read rcs files? and how big is it compared to RCS? > >> It seems there's some thought on importing CVS repos but according to 'fossil help import', only the git fast-export format is supported. In practice this means you'd loose history, yes. But it's not hard to keep the old RCS files somewhere else in case that history is needed. http://www.fossil-scm.org/fossil/wiki?name=Import+CVS+Repositories I just built devel/fossil and it yields a single binary, /usr/local/bin/fossil which clocks in at 1.8M. Given all the functionality it provides (plus it is in a similar class as git, see http://www.fossil-scm.org/index.html/doc/tip/www/fossil-v-git.wiki), I think that's a steal. It was started by the author of SQlite. If we require some kind of version control system in the base that's powerful, well-maintained and BSD-licensed, this really seems like a no-brainer. Jos -- Jos Backus jos at catnook.com From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 17:03:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3F643D1D for ; Thu, 10 Oct 2013 17:03:45 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EDC042BBB for ; Thu, 10 Oct 2013 17:03:44 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1VUJeB-000Iim-0A ; Thu, 10 Oct 2013 20:03:35 +0300 Date: Thu, 10 Oct 2013 20:03:34 +0300 From: Vitalij Satanivskij To: Allan Jude Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173 Message-ID: <20131010170334.GA71635@hell.ukr.net> References: <1381166916.122992963.5h9ygiri@frv45.ukr.net> <1381170764.32684.31088349.343931EE@webmail.messagingengine.com> <20131007185032.GA82932@hell.ukr.net> <20131007211201.GA89306@hell.ukr.net> <20131010092223.GA28347@hell.ukr.net> <5256D9D4.2030308@allanjude.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5256D9D4.2030308@allanjude.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:03:45 -0000 AJ> Some background on L2ARC compression for you: AJ> AJ> http://wiki.illumos.org/display/illumos/L2ARC+Compression I'm alredy see it. AJ> http://svnweb.freebsd.org/base?view=revision&revision=251478 AJ> AJ> Are you sure that compression on pool/zfs is off? it would normally AJ> inherit from the parent, so double check with: zfs get compression pool/zfs Yes, compression turned off on pool/zfs, it's was may time rechecked. AJ> Is the data on pool/zfs related to the data on the root pool? if AJ> pool/zfs were a clone, and the data is actually used in both places, the AJ> newer 'single copy ARC' feature may come in to play: AJ> https://www.illumos.org/issues/3145 No, both pool and pool/zfs have diferent type of data, pool/zfs was created as new empty zfs (zfs create pool/zfs) and data was writed to it from another server. Right now one machine work fine with l2arc. This machine without patch for corecting ashift on cache devices. At last 3 day's working with zero errors. Another servers with same config similar data, load and so on after 2 day work began report abouy errors. AJ> AJ> AJ> AJ> -- AJ> Allan Jude AJ> AJ> _______________________________________________ AJ> freebsd-current@freebsd.org mailing list AJ> http://lists.freebsd.org/mailman/listinfo/freebsd-current AJ> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 16:45:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E07141CA for ; Thu, 10 Oct 2013 16:45:29 +0000 (UTC) (envelope-from Eric_Van_Gyzen@dell.com) Received: from aussmtpmrkpc120.us.dell.com (aussmtpmrkpc120.us.dell.com [143.166.82.159]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A54322A67 for ; Thu, 10 Oct 2013 16:45:29 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.90,1073,1371099600"; d="scan'208,217";a="48275654" Message-ID: <5256D9A1.6050605@dell.com> Date: Thu, 10 Oct 2013 11:45:21 -0500 From: Eric van Gyzen Organization: Dell, Inc. User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: make universe fails, apparently in lib/clang/include (all) X-Mailman-Approved-At: Thu, 10 Oct 2013 17:17:53 +0000 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Eric van Gyzen X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 16:45:29 -0000 "make universe" is consistently failing in the following way. "_.amd64.amd64.buildworld" contains: ======== ===> lib/clang/libllvmx86desc (all) ===> lib/clang/libllvmx86disassembler (all) ===> lib/clang/libllvmx86info (all) ===> lib/clang/libllvmx86instprinter (all) ===> lib/clang/libllvmx86utils (all) ===> lib/clang/include (all) 1 error make[3]: stopped in /home/freebsd *** [everything] Error code 2 make[2]: stopped in /home/freebsd 1 error make[2]: stopped in /home/freebsd *** [buildworld] Error code 2 make[1]: stopped in /home/freebsd 1 error make[1]: stopped in /home/freebsd ======== I'm running it from bash with: nice -n 20 make JFLAG=-j4 MAKEOBJDIRPREFIX=/home/obj universe > /tmp/universe.log 2>&1 < /dev/null & "/tmp/universe.log" contains: -------------------------------------------------------------- >>> make universe started on Thu Oct 10 07:59:02 CDT 2013 -------------------------------------------------------------- >> amd64 started on Thu Oct 10 07:59:02 CDT 2013 >> amd64.amd64 buildworld started on Thu Oct 10 07:59:02 CDT 2013 amd64.amd64 buildworld failed, check _.amd64.amd64.buildworld for details /home/freebsd is a git repo, cloned from github, tracking the master branch, at commit 0b5457bf, corresponding to Subversion head r256251. I have no local changes. Am I doing something wrong? Is this working for everyone else? Thanks in advance, Eric -- *Eric van Gyzen* Senior Software Development Engineer *Dell* | Compellent *office* +1 952 562 3197 Cube J-732, 7615 Smetana Lane Eden Prairie, MN 55344 eric_van_gyzen@dell.com From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 17:18:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9CF38621 for ; Thu, 10 Oct 2013 17:18:08 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 74FD62CB4 for ; Thu, 10 Oct 2013 17:18:07 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 4D0A521809; Thu, 10 Oct 2013 17:18:04 +0000 (UTC) Message-ID: <5256E163.80100@allanjude.com> Date: Thu, 10 Oct 2013 13:18:27 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "Teske, Devin" Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> <5254F582.1040406@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> <5256509E.3000604@freebsd.org> <52565555.8030906@allanjude.com> <525695BD.7060706@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC508BE@LTCFISWMSGMB21.FNFIS.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D720FC508BE@LTCFISWMSGMB21.FNFIS.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:18:08 -0000 On 2013-10-10 11:30, Teske, Devin wrote: > On Oct 10, 2013, at 4:55 AM, Nathan Whitehorn wrote: > >> On 10/10/13 09:20, Allan Jude wrote: >>> On 2013-10-10 03:00, Nathan Whitehorn wrote: >>>> On 10/09/13 18:55, Teske, Devin wrote: >>>>> On Oct 8, 2013, at 11:19 PM, Nathan Whitehorn wrote: >>>>> >>>>>> On 10/09/13 01:13, Allan Jude wrote: >>>>>>> On 2013-10-08 16:17, Nathan Whitehorn wrote: >>>>>>>> On 10/07/13 21:59, Allan Jude wrote: >>>>>>>>> Devin Teske and I have been working on a big patch to bsdinstall to >>>>>>>>> implement installing on a ZFS pool. It supports both GPT and MBR, the 4k >>>>>>>>> sector gnop trick, and optional GELI encryption. We would like to commit >>>>>>>>> this in time for 10.0-BETA1 so it needs some testing to work out any >>>>>>>>> obvious bugs before we send it off to re@ to get it committed. >>>>>>>>> >>>>>>>>> It includes a single configuration menu that allows you to select all of >>>>>>>>> the required details, including which drives to use (gets details from >>>>>>>>> camcontrol, also includes an inspection utility that presents the >>>>>>>>> detailed output of camcontrol inquiry/identify, and gpart show), what >>>>>>>>> ZFS RAID level to use (taking in to consideration the selected number of >>>>>>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>>>>>> >>>>>>>>> >>>>>>>>> Additional, it includes some other changes to bsdinstall: >>>>>>>>> 1. Change the default to the 'non-standard keyboard mapping' prompt to no >>>>>>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address with just 1 >>>>>>>>> 3. Remove the dialog asking if you wish to enable crash dumps, this >>>>>>>>> feature has been combined into the regular 'services to enable' dialog >>>>>>>>> and enabled by default >>>>>>>>> >>>>>>>>> >>>>>>>>> You can browse the patches here: >>>>>>>>> http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/ >>>>>>>>> >>>>>>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>>>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>>>>>> >>>>>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz >>>>>>>>> >>>>>>>>> http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso >>>>>>>>> >>>>>>>>> >>>>>>>>> We look forward to your feedback >>>>>>>>> >>>>>>>> Thanks for doing this! I had a few comments: >>>>>>>> 1. ZFS is not bootable on all architectures. Could you adjust that menu >>>>>>>> item to only display for i386, amd64, and (I think?) sparc64. Use uname >>>>>>>> -m, not -p, for this. >>>>>>> I had not considered that, I'll make that change >>>>>>> >>>>>>>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>>>>>>> instead of GPT. >>>>>>> I'll disable sparc64 as well >>>>>>> >>>>>>>> 2. Why are you using camcontrol? That is guaranteed not to work on >>>>>>>> non-CAM systems. You should use the GEOM ident string if you need an ID. >>>>>>> The GEOM ident string doesn't do enough to help the user identify which >>>>>>> drive is which. >>>>>>> More data is not exposed anywhere that I could find >>>>>>> >>>>>>> What we really need, is dev.ada.0.desc% like we have for network >>>>>>> interfaces and a slew of other devices. GEOM data is great, but it is >>>>>>> not exposed in a shell friendly way any place that I could find, other >>>>>>> than the sysctl with DOT and XML data. >>>>>> This is one of the reasons the partition editor is written in C. There >>>>>> are a few other odd corner-cases where C is much more powerful than the >>>>>> command-line for the GEOM operations that partedit needs to do. I'm not >>>>>> sure how to usefully get it just from the shell. You can see how to do >>>>>> it in C in the boot_disk() routine of partedit/auto_part.c. >>>>>> >>>>>>>> 3. Any plans to integrate this into the regular partition editor? ZFS >>>>>>>> support is important enough that I will definitely not get in the way, >>>>>>>> even as a bolt-on, but it would be a shame for it to stay that way. The >>>>>>>> editor is also designed for ZFS to be added. >>>>>>> I am a sysadmin, not a programmer. I can't write C. Most people >>>>>>> deploying servers can't write C. I agree with Devin Teske, if everything >>>>>>> was in shell it would be a lot more usable for non-developers, who >>>>>>> probably make up the majority of people who deploy FreeBSD. >>>>>> There are some cases the other way too. Devin is probably the most >>>>>> shell-proficient FreeBSD committer. >>>>> Well, there's jilles ;D (he writes/maintains the sh(1) implementation itself). >>>>> >>>>> >>>>>> I certainly can't write shell >>>>>> scripts at that level, which means that for me bsdconfig, for example, >>>>>> is effectively read-only (and quite hard to read as well). >>>>> In the past few days of working on the bsdinstall_zfs patch-set with Allan >>>>> Jude, I learned something new actually. >>>>> >>>>> It seems that sh(1) doesn't suffer so much from this "read only" concept. >>>>> >>>>> Imagine you're starting a new C project on an operating system that has >>>>> all new syscalls and all new APIs that you've never seen. Would be pretty >>>>> hard, no doubt. Now imagine that you're thrown a life-line called POSIX >>>>> and hey, now you're slinging code in MinGW on Windows when you don't >>>>> know a lick of M$ syscalls or APIs. >>>>> >>>>> In a similar manner, I've witnessed functionality be added that is truly >>>>> functional *without* using any of the API calls. Then I come in and do >>>>> a round of optimizations to leverage the existing API. >>>>> >>>>> Shell is kinda like that... >>>>> >>>>> I'm noticing Allan Jude doesn't know all the API calls yet (who could? other >>>>> than me of course -- and even I have trouble remembering them _all_) yet >>>>> this doesn't phase him (or others) from jumping in and lending a hand. >>>>> >>>>> No different than C, but the read-only aspect is lessened significantly I >>>>> believe because there are so many people out there that know enough >>>>> good shell syntax and are just a stone's throw away from *great* shell >>>>> syntax (which I must admit jilles helped me cross that boundary). >>>>> >>>>> I think in C, the read-only aspect is greater because its harder to parcel-out >>>>> the functions for a unit-test; harder to inject new code; and harder to get >>>>> to a functioning end-state. >>>> Look, I have no doubt that in the right hands shell can do amazing >>>> things and C can be badly written. That isn't the issue though. My >>>> statement was purely that most FreeBSD developers (me included) are more >>>> comfortable with C than shell when used at the kind of level involved >>>> here. This is not a value judgment but a statement of fact. Whether or >>>> not, at some platonic level, shell or C or python or whatever are more >>>> or less read-only is not the point here. The point is that I, and I >>>> suspect many other developers, cannot write (or read) very advanced >>>> levels of shell scripting but can read and write the equivalent programs >>>> when written in C in many cases. It's what the rest of the system is >>>> written in and what we spend most of our time using. Whether this should >>>> be the case or not is immaterial; the fact remains that shell scripting >>>> at any but a very basic level does introduce a very large barrier to >>>> entry for probably a large majority of committers. >>>> >>>> This is not always a problem -- especially if using something more >>>> obscure allows very active development by the set of people working on >>>> it -- but does reduce the set of people who can make modifications >>>> substantially. I have no ability to change, or understand, most of >>>> bsdconfig, for example. This isn't a problem since you are doing all the >>>> work and there is no reason I would need to or want to make changes to >>>> it. But it could become a problem in a part of the system to which >>>> multiple people needed to contribute. It's about other people's comfort >>>> zones and knowledge in the end. >>>> -Nathan >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >>> I definately see your point, but the code going in to the zfsboot part >>> in particular, is not that advanced. I started this project two weeks >>> ago with a well below average knowledge of shell script, a minor bit of >>> experience in php, and no real programming experience to speak of. >>> >>> I wrote most of the code that actually does things, Devin just cleaned >>> it up (I didn't know anything about shstyle or the rules) and pointed me >>> at some handy subroutines he had written to avoid writing out 20 lines >>> of code every time I wanted to display a dialog box >>> >>> I wouldn't say any of what is in the proposed patches to bsdinstall is >>> unmaintainable, and it definately makes it much more approachable for >>> sysadmins who are the ones that actually need to be able to script >>> bsdinstall, and generate various methods of automated deployment. This >>> is a very important feature if we want FreeBSD to be taken seriously for >>> deployment in mass virtualization environments (do not make my say >>> cloud. we saw a great sign in Malta at some street festival "what is >>> cloud?") >> Sorry, I think you misunderstood me. I really appreciate your work, and >> the ZFS stuff, as I said, is not that complex so there's no problem >> there. Aside from a couple of issues I mentioned (with sparc, etc.), it >> seems like a very good step forward. What I *was* trying to do was >> discourage you from rewriting partedit as a shell script and to >> encourage unifying the ZFS backend into partedit at some point in the >> future significantly different from now. >> >> I also wanted to mention that bsdinstall is completely scriptable >> (although not the new ZFS code, I guess...) > Oh, but it is. > > The following variables have sensible defaults and are designed > to be exported in a bsdinstall script to customize the actions > performed by the zfsboot script: > > dteske@scribe9.vicor.com scripts $ grep '^: ' zfsboot > : ${ZFSBOOT_POOL_NAME:=zroot} > : ${ZFSBOOT_BEROOT_NAME:=bootenv} > : ${ZFSBOOT_BOOTFS_NAME:=default} > : ${ZFSBOOT_VDEV_TYPE:=stripe} > : ${ZFSBOOT_GNOP_4K_FORCE_ALIGN:=1} > : ${ZFSBOOT_GELI_ENCRYPTION:=} > : ${ZFSBOOT_GELI_POOL_NAME:=bootpool} > : ${ZFSBOOT_GELI_BOOT_SIZE:=2g} > : ${ZFSBOOT_GELI_KEY_FILE:=/boot/encryption.key} > : ${ZFSBOOT_DISKS:=} > : ${ZFSBOOT_PARTITION_SCHEME:=GPT} > : ${ZFSBOOT_SWAP_SIZE:=2g} > > Notice the ZFSBOOT_ prefix matching the script name. > These may not be the final names used as an overall > effort is made (given time) to conflate the scripting variables > and general namespace. > > > >> and has been for some time. > The type of scripting set forth by bsdinstall is not the same kind of > scripting set forth by bsdconfig. > > That being said, I've not yet made an effort to close the gap on > bsdinstall scripting (to make it like bsdconfig scripting). > > In bsdconfig, we can literally load a sysinstall "install.cfg" file and > there is no need to for a complicated embedding system such as > bsdinstall has (wherein the "script" is actually a multi-part file). > > A lot of people have scoffed at backward compatibility because it > would not be easy. However, I see a pretty big carrot dangling in > front of the backward compatibility effort... > > It's not the act of implementing the individual reswords that's going > to bring the biggest value-add, but instead the bringing back of the > process-flow to deployment that will see the greatest gain in > functionality. By this, I mean that currently you invoke bsdinstall > and it runs through a UX given a set of values set in variables. > This is sub-optimal if you don't like the UX choices -- better to > instead allow the script to take the reigns and do things by way > of having the script drive (in sysinstall, this amounts to the fact that > if "install.cfg" doesn't call diskPartitionWrite or doesn't call > distExtractAll, then those steps are not performed). In bsdinstall, a > change in focus to allow the script to drive *could* be done by > requiring the user to fork-exec to a bunch of scripts -- and in-turn > then requiring each/every custom setting to be *export*ed... but > ultimately the best bang-for-your-buck is going to come from > (I'll say it again) namespace conflation (writing the functionality > as a series of includable functions that are run in the same > namespace as the script that is driving). Naturally, a bunch of > functions can be lost if you don't know where to look for them, and > that comes back full-circle to `script.subr' and `variable.subr' as the > "points of discovery" (besides a man-page; which is where sys- > install documented its own reswords). > > > >> Only the initial release that shipped with 9.0 was not. There's a >> lengthy discussion of how this works in the man page. > *nods* > > > >> The scripting >> support is extremely flexible (you can run an arbitrary shell script in >> addition to the usual installation steps) and lets installations from >> PXE or media operate completely unattended. > Yes, but I've been taking to simply creating /etc/installerconf and > completely bypassing the scripting that's documented in the man-page > *because* I abhor multi-part file which requires a split-architecture > approach to installation (no like). > > Sysinstall often required me to do the same thing. Whereas in > sysinstall the problem was that you couldn't speak native shell in the > install.cfg file (requiring you to call out to a "system" resword to > execute a script which generates a side "install.cfg" later brought > back in with the "loadConfig" resword, bsdinstall instead requires me > to have -- in the multi-part script it loads -- a preamble and a setup > script and this causes a similar dichotomy in passing information > between the stages). > > In bsdconfig, I worked extremely hard to solve that issue. The end- > result is that both problems are solved. The problem of sysinstall > is gone because the "install.cfg" file becomes a shell script so you > can then start speaking native shell in it. The multi-part problem is > gone when you provide all the reswords in the native language > (conflated namespace). Devin, we should make a note to talk to Rick Miller (Verisign, host of vBSDCon) while we are there. They still use sysinstall, and having bsdinstall understand their sysinstall configs may be of great value to them. -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 17:21:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D8080865 for ; Thu, 10 Oct 2013 17:21:36 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8B7782D14 for ; Thu, 10 Oct 2013 17:21:36 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa06.fnfis.com (8.14.5/8.14.5) with ESMTP id r9AHLVpa006846 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 10 Oct 2013 12:21:31 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.02.0309.002; Thu, 10 Oct 2013 12:21:30 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxRBPPJPIP8ZCyUiSsjBzr2++AA== Date: Thu, 10 Oct 2013 17:21:30 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC51061@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52546844.2010608@freebsd.org> <52549191.5010400@allanjude.com> <5254F582.1040406@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC4B1F4@LTCFISWMSGMB21.FNFIS.com> <5256509E.3000604@freebsd.org> <52565555.8030906@allanjude.com> <525695BD.7060706@freebsd.org> <13CA24D6AB415D428143D44749F57D720FC508BE@LTCFISWMSGMB21.FNFIS.com> <5256E163.80100@allanjude.com> In-Reply-To: <5256E163.80100@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-10_06:2013-10-10,2013-10-10,1970-01-01 signatures=0 Cc: "" , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:21:37 -0000 On Oct 10, 2013, at 10:18 AM, Allan Jude wrote: > On 2013-10-10 11:30, Teske, Devin wrote: >> On Oct 10, 2013, at 4:55 AM, Nathan Whitehorn wrote: >>=20 >>> On 10/10/13 09:20, Allan Jude wrote: >>>> On 2013-10-10 03:00, Nathan Whitehorn wrote: >>>>> On 10/09/13 18:55, Teske, Devin wrote: >>>>>> On Oct 8, 2013, at 11:19 PM, Nathan Whitehorn wrote: >>>>>>=20 >>>>>>> On 10/09/13 01:13, Allan Jude wrote: >>>>>>>> On 2013-10-08 16:17, Nathan Whitehorn wrote: >>>>>>>>> On 10/07/13 21:59, Allan Jude wrote: >>>>>>>>>> Devin Teske and I have been working on a big patch to bsdinstall= to >>>>>>>>>> implement installing on a ZFS pool. It supports both GPT and MBR= , the 4k >>>>>>>>>> sector gnop trick, and optional GELI encryption. We would like t= o commit >>>>>>>>>> this in time for 10.0-BETA1 so it needs some testing to work out= any >>>>>>>>>> obvious bugs before we send it off to re@ to get it committed. >>>>>>>>>>=20 >>>>>>>>>> It includes a single configuration menu that allows you to selec= t all of >>>>>>>>>> the required details, including which drives to use (gets detail= s from >>>>>>>>>> camcontrol, also includes an inspection utility that presents the >>>>>>>>>> detailed output of camcontrol inquiry/identify, and gpart show),= what >>>>>>>>>> ZFS RAID level to use (taking in to consideration the selected n= umber of >>>>>>>>>> drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc. >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Additional, it includes some other changes to bsdinstall: >>>>>>>>>> 1. Change the default to the 'non-standard keyboard mapping' pro= mpt to no >>>>>>>>>> 2. Replace the 3 separate dialogs to configure an ipv4 address w= ith just 1 >>>>>>>>>> 3. Remove the dialog asking if you wish to enable crash dumps, t= his >>>>>>>>>> feature has been combined into the regular 'services to enable' = dialog >>>>>>>>>> and enabled by default >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> You can browse the patches here: >>>>>>>>>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://druidbsd.cvs= .sf.net/viewvc/druidbsd/bsdinstall_zfs/&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3= D%0A&r=3DLTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DckXs2H5TEc= KdiN%2F9l%2FClInsMys9LmTwEbElzzrBchMU%3D%0A&s=3D6361ad5ccc04a6d8401158a3ee1= b3d8df9fcd2ef47ff6ad6365a57b907cceaec >>>>>>>>>>=20 >>>>>>>>>> I've built a bootonly.iso (10.0-ALPHA4) to make testing easier, >>>>>>>>>> available compressed (48 MB) or uncompressed (211 MB): >>>>>>>>>>=20 >>>>>>>>>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://www.allanjud= e.com/bsd/zfsbootonly_2013-10-06.iso.xz&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3= D%0A&r=3DLTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DckXs2H5TEc= KdiN%2F9l%2FClInsMys9LmTwEbElzzrBchMU%3D%0A&s=3D570daea25d9e629788c76c2b5a6= eae19d32050363986a1004a6434c3466965c2 >>>>>>>>>>=20 >>>>>>>>>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://www.allanjud= e.com/bsd/zfsbootonly_2013-10-06.iso&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0= A&r=3DLTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DckXs2H5TEcKdi= N%2F9l%2FClInsMys9LmTwEbElzzrBchMU%3D%0A&s=3Df52d604a2503a48b409f92f8376bb7= 73de4dbc469d1e74b16d051a20ad894820 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> We look forward to your feedback >>>>>>>>>>=20 >>>>>>>>> Thanks for doing this! I had a few comments: >>>>>>>>> 1. ZFS is not bootable on all architectures. Could you adjust tha= t menu >>>>>>>>> item to only display for i386, amd64, and (I think?) sparc64. Use= uname >>>>>>>>> -m, not -p, for this. >>>>>>>> I had not considered that, I'll make that change >>>>>>>>=20 >>>>>>>>> 1a. The script is broken on sparc64 in any case, which uses VTOC8 >>>>>>>>> instead of GPT. >>>>>>>> I'll disable sparc64 as well >>>>>>>>=20 >>>>>>>>> 2. Why are you using camcontrol? That is guaranteed not to work on >>>>>>>>> non-CAM systems. You should use the GEOM ident string if you need= an ID. >>>>>>>> The GEOM ident string doesn't do enough to help the user identify = which >>>>>>>> drive is which. >>>>>>>> More data is not exposed anywhere that I could find >>>>>>>>=20 >>>>>>>> What we really need, is dev.ada.0.desc% like we have for network >>>>>>>> interfaces and a slew of other devices. GEOM data is great, but it= is >>>>>>>> not exposed in a shell friendly way any place that I could find, o= ther >>>>>>>> than the sysctl with DOT and XML data. >>>>>>> This is one of the reasons the partition editor is written in C. Th= ere >>>>>>> are a few other odd corner-cases where C is much more powerful than= the >>>>>>> command-line for the GEOM operations that partedit needs to do. I'm= not >>>>>>> sure how to usefully get it just from the shell. You can see how to= do >>>>>>> it in C in the boot_disk() routine of partedit/auto_part.c. >>>>>>>=20 >>>>>>>>> 3. Any plans to integrate this into the regular partition editor?= ZFS >>>>>>>>> support is important enough that I will definitely not get in the= way, >>>>>>>>> even as a bolt-on, but it would be a shame for it to stay that wa= y. The >>>>>>>>> editor is also designed for ZFS to be added. >>>>>>>> I am a sysadmin, not a programmer. I can't write C. Most people >>>>>>>> deploying servers can't write C. I agree with Devin Teske, if ever= ything >>>>>>>> was in shell it would be a lot more usable for non-developers, who >>>>>>>> probably make up the majority of people who deploy FreeBSD. >>>>>>> There are some cases the other way too. Devin is probably the most >>>>>>> shell-proficient FreeBSD committer. >>>>>> Well, there's jilles ;D (he writes/maintains the sh(1) implementatio= n itself). >>>>>>=20 >>>>>>=20 >>>>>>> I certainly can't write shell >>>>>>> scripts at that level, which means that for me bsdconfig, for examp= le, >>>>>>> is effectively read-only (and quite hard to read as well). >>>>>> In the past few days of working on the bsdinstall_zfs patch-set with= Allan >>>>>> Jude, I learned something new actually. >>>>>>=20 >>>>>> It seems that sh(1) doesn't suffer so much from this "read only" con= cept. >>>>>>=20 >>>>>> Imagine you're starting a new C project on an operating system that = has >>>>>> all new syscalls and all new APIs that you've never seen. Would be p= retty >>>>>> hard, no doubt. Now imagine that you're thrown a life-line called PO= SIX >>>>>> and hey, now you're slinging code in MinGW on Windows when you don't >>>>>> know a lick of M$ syscalls or APIs. >>>>>>=20 >>>>>> In a similar manner, I've witnessed functionality be added that is t= ruly >>>>>> functional *without* using any of the API calls. Then I come in and = do >>>>>> a round of optimizations to leverage the existing API. >>>>>>=20 >>>>>> Shell is kinda like that... >>>>>>=20 >>>>>> I'm noticing Allan Jude doesn't know all the API calls yet (who coul= d? other >>>>>> than me of course -- and even I have trouble remembering them _all_)= yet >>>>>> this doesn't phase him (or others) from jumping in and lending a han= d. >>>>>>=20 >>>>>> No different than C, but the read-only aspect is lessened significan= tly I >>>>>> believe because there are so many people out there that know enough >>>>>> good shell syntax and are just a stone's throw away from *great* she= ll >>>>>> syntax (which I must admit jilles helped me cross that boundary). >>>>>>=20 >>>>>> I think in C, the read-only aspect is greater because its harder to = parcel-out >>>>>> the functions for a unit-test; harder to inject new code; and harder= to get >>>>>> to a functioning end-state. >>>>> Look, I have no doubt that in the right hands shell can do amazing >>>>> things and C can be badly written. That isn't the issue though. My >>>>> statement was purely that most FreeBSD developers (me included) are m= ore >>>>> comfortable with C than shell when used at the kind of level involved >>>>> here. This is not a value judgment but a statement of fact. Whether or >>>>> not, at some platonic level, shell or C or python or whatever are more >>>>> or less read-only is not the point here. The point is that I, and I >>>>> suspect many other developers, cannot write (or read) very advanced >>>>> levels of shell scripting but can read and write the equivalent progr= ams >>>>> when written in C in many cases. It's what the rest of the system is >>>>> written in and what we spend most of our time using. Whether this sho= uld >>>>> be the case or not is immaterial; the fact remains that shell scripti= ng >>>>> at any but a very basic level does introduce a very large barrier to >>>>> entry for probably a large majority of committers. >>>>>=20 >>>>> This is not always a problem -- especially if using something more >>>>> obscure allows very active development by the set of people working on >>>>> it -- but does reduce the set of people who can make modifications >>>>> substantially. I have no ability to change, or understand, most of >>>>> bsdconfig, for example. This isn't a problem since you are doing all = the >>>>> work and there is no reason I would need to or want to make changes to >>>>> it. But it could become a problem in a part of the system to which >>>>> multiple people needed to contribute. It's about other people's comfo= rt >>>>> zones and knowledge in the end. >>>>> -Nathan >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> https://urldefense.proofpoint.com/v1/url?u=3Dhttp://lists.freebsd.org= /mailman/listinfo/freebsd-current&k=3D%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r= =3DLTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D%0A&m=3DckXs2H5TEcKdiN%2= F9l%2FClInsMys9LmTwEbElzzrBchMU%3D%0A&s=3D229c04e0b0ce43bcdc88819dc4a9cba8f= fa47ef43ec9ad5352019bd7c850feff >>>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd= .org" >>>> I definately see your point, but the code going in to the zfsboot part >>>> in particular, is not that advanced. I started this project two weeks >>>> ago with a well below average knowledge of shell script, a minor bit of >>>> experience in php, and no real programming experience to speak of. >>>>=20 >>>> I wrote most of the code that actually does things, Devin just cleaned >>>> it up (I didn't know anything about shstyle or the rules) and pointed = me >>>> at some handy subroutines he had written to avoid writing out 20 lines >>>> of code every time I wanted to display a dialog box >>>>=20 >>>> I wouldn't say any of what is in the proposed patches to bsdinstall is >>>> unmaintainable, and it definately makes it much more approachable for >>>> sysadmins who are the ones that actually need to be able to script >>>> bsdinstall, and generate various methods of automated deployment. This >>>> is a very important feature if we want FreeBSD to be taken seriously f= or >>>> deployment in mass virtualization environments (do not make my say >>>> cloud. we saw a great sign in Malta at some street festival "what is >>>> cloud?") >>> Sorry, I think you misunderstood me. I really appreciate your work, and >>> the ZFS stuff, as I said, is not that complex so there's no problem >>> there. Aside from a couple of issues I mentioned (with sparc, etc.), it >>> seems like a very good step forward. What I *was* trying to do was >>> discourage you from rewriting partedit as a shell script and to >>> encourage unifying the ZFS backend into partedit at some point in the >>> future significantly different from now. >>>=20 >>> I also wanted to mention that bsdinstall is completely scriptable >>> (although not the new ZFS code, I guess...) >> Oh, but it is. >>=20 >> The following variables have sensible defaults and are designed >> to be exported in a bsdinstall script to customize the actions >> performed by the zfsboot script: >>=20 >> dteske@scribe9.vicor.com scripts $ grep '^: ' zfsboot=20 >> : ${ZFSBOOT_POOL_NAME:=3Dzroot} >> : ${ZFSBOOT_BEROOT_NAME:=3Dbootenv} >> : ${ZFSBOOT_BOOTFS_NAME:=3Ddefault} >> : ${ZFSBOOT_VDEV_TYPE:=3Dstripe} >> : ${ZFSBOOT_GNOP_4K_FORCE_ALIGN:=3D1} >> : ${ZFSBOOT_GELI_ENCRYPTION:=3D} >> : ${ZFSBOOT_GELI_POOL_NAME:=3Dbootpool} >> : ${ZFSBOOT_GELI_BOOT_SIZE:=3D2g} >> : ${ZFSBOOT_GELI_KEY_file:///=3D/boot/encryption.key} >> : ${ZFSBOOT_DISKS:=3D} >> : ${ZFSBOOT_PARTITION_SCHEME:=3DGPT} >> : ${ZFSBOOT_SWAP_SIZE:=3D2g} >>=20 >> Notice the ZFSBOOT_ prefix matching the script name. >> These may not be the final names used as an overall >> effort is made (given time) to conflate the scripting variables >> and general namespace. >>=20 >>=20 >>=20 >>> and has been for some time. >> The type of scripting set forth by bsdinstall is not the same kind of >> scripting set forth by bsdconfig. >>=20 >> That being said, I've not yet made an effort to close the gap on >> bsdinstall scripting (to make it like bsdconfig scripting). >>=20 >> In bsdconfig, we can literally load a sysinstall "install.cfg" file and >> there is no need to for a complicated embedding system such as >> bsdinstall has (wherein the "script" is actually a multi-part file). >>=20 >> A lot of people have scoffed at backward compatibility because it >> would not be easy. However, I see a pretty big carrot dangling in >> front of the backward compatibility effort... >>=20 >> It's not the act of implementing the individual reswords that's going >> to bring the biggest value-add, but instead the bringing back of the >> process-flow to deployment that will see the greatest gain in >> functionality. By this, I mean that currently you invoke bsdinstall >> and it runs through a UX given a set of values set in variables. >> This is sub-optimal if you don't like the UX choices -- better to >> instead allow the script to take the reigns and do things by way >> of having the script drive (in sysinstall, this amounts to the fact that >> if "install.cfg" doesn't call diskPartitionWrite or doesn't call >> distExtractAll, then those steps are not performed). In bsdinstall, a >> change in focus to allow the script to drive *could* be done by >> requiring the user to fork-exec to a bunch of scripts -- and in-turn >> then requiring each/every custom setting to be *export*ed... but >> ultimately the best bang-for-your-buck is going to come from >> (I'll say it again) namespace conflation (writing the functionality >> as a series of includable functions that are run in the same >> namespace as the script that is driving). Naturally, a bunch of >> functions can be lost if you don't know where to look for them, and >> that comes back full-circle to `script.subr' and `variable.subr' as the >> "points of discovery" (besides a man-page; which is where sys- >> install documented its own reswords). >>=20 >>=20 >>=20 >>> Only the initial release that shipped with 9.0 was not. There's a >>> lengthy discussion of how this works in the man page. >> *nods* >>=20 >>=20 >>=20 >>> The scripting >>> support is extremely flexible (you can run an arbitrary shell script in >>> addition to the usual installation steps) and lets installations from >>> PXE or media operate completely unattended. >> Yes, but I've been taking to simply creating /etc/installerconf and >> completely bypassing the scripting that's documented in the man-page >> *because* I abhor multi-part file which requires a split-architecture >> approach to installation (no like). >>=20 >> Sysinstall often required me to do the same thing. Whereas in >> sysinstall the problem was that you couldn't speak native shell in the >> install.cfg file (requiring you to call out to a "system" resword to >> execute a script which generates a side "install.cfg" later brought >> back in with the "loadConfig" resword, bsdinstall instead requires me >> to have -- in the multi-part script it loads -- a preamble and a setup >> script and this causes a similar dichotomy in passing information >> between the stages). >>=20 >> In bsdconfig, I worked extremely hard to solve that issue. The end- >> result is that both problems are solved. The problem of sysinstall >> is gone because the "install.cfg" file becomes a shell script so you >> can then start speaking native shell in it. The multi-part problem is >> gone when you provide all the reswords in the native language >> (conflated namespace). > Devin, we should make a note to talk to Rick Miller (Verisign, host of > vBSDCon) while we are there. They still use sysinstall, and having > bsdinstall understand their sysinstall configs may be of great value to > them. That's the plan ;D Been working with ol' Rick for years now on that journey. We keep in- touch and I keep apprising him of how things are going. Also, I've been sharing with him recipes for /etc/installerconf that used the legacy reswords but branch out to the couple parts of bsdinstall that are needed to do the disk management and dist extraction. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 17:24:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DA573AFB for ; Thu, 10 Oct 2013 17:24:16 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id B64B52D41 for ; Thu, 10 Oct 2013 17:24:15 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id DD40F21853 for ; Thu, 10 Oct 2013 17:24:14 +0000 (UTC) Message-ID: <5256E2D5.4060101@allanjude.com> Date: Thu, 10 Oct 2013 13:24:37 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: FreeBSD 10 and zfsd References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> In-Reply-To: <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:24:16 -0000 On 2013-10-10 12:13, Mark Felder wrote: > On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: >> On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks >> wrote: >>> When i started using ZFS on FreeBSD I quickly found out that hot spares are >>> not possible on FreeBSD. >>> I was told that with zfsd it should be possible and that it would be >>> included in FreeBSD 10. >>> >>> Is there some info about the zfsd function and how it could be used? >> zfsd is currently not in FreeBSD/head and won't make it into 10, but >> you can still get the source code from its project branch. It's being >> used in production by at least two companies. >> > So FreeBSD is going to have inferior ZFS management compared to > Solaris/Illumos/etc for another 2+ years? Why are things like this > allowed to miss releases? > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev summit (3 weeks ago). There is a lot of collaboration going on, to bring in some work done by vendors like SpectraLogics. This is the type of feature that can be assed in 10.1, it won't have to wait for 11. You can see Robert Watsons talk "How FreeBSD Works" to see why releases are based on date, rather than on feature completion (because things are never "finished") -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 17:27:00 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E263ECA7 for ; Thu, 10 Oct 2013 17:26:59 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-qc0-x231.google.com (mail-qc0-x231.google.com [IPv6:2607:f8b0:400d:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A49E42D64 for ; Thu, 10 Oct 2013 17:26:59 +0000 (UTC) Received: by mail-qc0-f177.google.com with SMTP id x12so2027760qcv.8 for ; Thu, 10 Oct 2013 10:26:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=QegusdKC5qAwY1THgwAvpqt4O09hUKGa50yia6HPF/M=; b=PPmsXVKqtYuCxbu1FH61J4FgKIhOB+TvU7XtDPpkK86613kYdTVCX+ngzJGPdobRlD 4CTOODh2+TtUpeLaoWXa2YVNZ56E76kkQ07nKWWG8L7EgjTxAyWsShEYkMbTQb0E7pBE RGCfLiVlThq+wsobXyORh6BWFHunQ+x4upyzd/3QT2BYX4xUrq58/kYxy1p2fvM8daFC R7jufHAuFeaJondC3BN1bJMJu0v7meLEoISxxh9m+Ns0ZELkxfC6N5Af7ertnd+LQBC9 Hd3uMGf2NGOfE1j3s+3cl+1DlyUP5waC8pVf7IrXIzXHh0xGA+NWiokNWEAQrDnAY0uF icsg== MIME-Version: 1.0 X-Received: by 10.229.251.201 with SMTP id mt9mr12370811qcb.26.1381426018382; Thu, 10 Oct 2013 10:26:58 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.49.39.97 with HTTP; Thu, 10 Oct 2013 10:26:58 -0700 (PDT) In-Reply-To: <5256E2D5.4060101@allanjude.com> References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> <5256E2D5.4060101@allanjude.com> Date: Thu, 10 Oct 2013 11:26:58 -0600 X-Google-Sender-Auth: k5TygSMEq4i7J3Kpj5MQxTzuFcA Message-ID: Subject: Re: FreeBSD 10 and zfsd From: Alan Somers To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:27:00 -0000 On Thu, Oct 10, 2013 at 11:24 AM, Allan Jude wrote: > On 2013-10-10 12:13, Mark Felder wrote: >> On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: >>> On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks >>> wrote: >>>> When i started using ZFS on FreeBSD I quickly found out that hot spares are >>>> not possible on FreeBSD. >>>> I was told that with zfsd it should be possible and that it would be >>>> included in FreeBSD 10. >>>> >>>> Is there some info about the zfsd function and how it could be used? >>> zfsd is currently not in FreeBSD/head and won't make it into 10, but >>> you can still get the source code from its project branch. It's being >>> used in production by at least two companies. >>> >> So FreeBSD is going to have inferior ZFS management compared to >> Solaris/Illumos/etc for another 2+ years? Why are things like this >> allowed to miss releases? >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev summit (3 > weeks ago). There is a lot of collaboration going on, to bring in some > work done by vendors like SpectraLogics. This is the type of feature > that can be assed in 10.1, it won't have to wait for 11. > > You can see Robert Watsons talk "How FreeBSD Works" to see why releases > are based on date, rather than on feature completion (because things are > never "finished") > > > > -- > Allan Jude > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Due to popular demand, I have located a round toit. I'm currently working on rebasing the zfsd project branch to head, after which I'll push SpectraLogic's recent changes. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 17:39:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F2B2E331; Thu, 10 Oct 2013 17:39:55 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id CD6772E42; Thu, 10 Oct 2013 17:39:53 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 0CF9D218FD; Thu, 10 Oct 2013 17:39:52 +0000 (UTC) Message-ID: <5256E680.4000008@allanjude.com> Date: Thu, 10 Oct 2013 13:40:16 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Alan Somers Subject: Re: FreeBSD 10 and zfsd References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> <5256E2D5.4060101@allanjude.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:39:56 -0000 On 2013-10-10 13:26, Alan Somers wrote: > On Thu, Oct 10, 2013 at 11:24 AM, Allan Jude wrote: >> On 2013-10-10 12:13, Mark Felder wrote: >>> On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: >>>> On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks >>>> wrote: >>>>> When i started using ZFS on FreeBSD I quickly found out that hot spares are >>>>> not possible on FreeBSD. >>>>> I was told that with zfsd it should be possible and that it would be >>>>> included in FreeBSD 10. >>>>> >>>>> Is there some info about the zfsd function and how it could be used? >>>> zfsd is currently not in FreeBSD/head and won't make it into 10, but >>>> you can still get the source code from its project branch. It's being >>>> used in production by at least two companies. >>>> >>> So FreeBSD is going to have inferior ZFS management compared to >>> Solaris/Illumos/etc for another 2+ years? Why are things like this >>> allowed to miss releases? >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev summit (3 >> weeks ago). There is a lot of collaboration going on, to bring in some >> work done by vendors like SpectraLogics. This is the type of feature >> that can be assed in 10.1, it won't have to wait for 11. >> >> You can see Robert Watsons talk "How FreeBSD Works" to see why releases >> are based on date, rather than on feature completion (because things are >> never "finished") >> >> >> >> -- >> Allan Jude >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Due to popular demand, I have located a round toit. I'm currently > working on rebasing the zfsd project branch to head, after which I'll > push SpectraLogic's recent changes. See, all you have to do is complain loudly enough :p -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 17:54:14 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 292C1B4C for ; Thu, 10 Oct 2013 17:54:14 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 047A62F48 for ; Thu, 10 Oct 2013 17:54:13 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id DDA2D21948 for ; Thu, 10 Oct 2013 17:54:10 +0000 (UTC) Message-ID: <5256E9D9.6060302@allanjude.com> Date: Thu, 10 Oct 2013 13:54:33 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: FreeBSD Current Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52531295.7090700@allanjude.com> <52539300.50305@allanjude.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:54:14 -0000 On 2013-10-10 13:21, Warren Block wrote: > [off-list reply] > > I have not tested the new version yet. Is there any chance it > supports setting up a gmirror? > > Something I've been meaning to discuss with Devin is the concept of > presets. The user would be able to choose from a list of presets: > > Filesystem Layout > ----------------- > Merged / filesystem > Split /, /var, /tmp, /usr filesystems > > then > > Filesystem Type > --------------- > UFS > ZFS > > then > > Disk Layout > ----------- > Plain disk > Mirror > RAID > > Those choices might change depending on earlier ones, like if they had > chosen ZFS earlier they would get a choice of Mirror, RAID-Z1, > RAID-Z2, and so on. > > All this would build up a configuration, and at the end the user can > edit it (filesystem sizes, for instance), then pick Go and walk away. All of the UFS stuff is in C, so is read-only for me. It is something I'd like to do, but it is really iffy if that can be done in time for 10.0 In general, gmirror support could be added to the ZFS section (renamed to something else). So in our current 'zfs' menu, would become the 'new partition manager' menu. Add an extra option for ZFS or UFS, and then the vdev menu would context switch between zfs vdevs and ufs options like gmirror and gstripe or something Adding an extra option for / or / /var /tmp /usr is not a bad idea either, maybe even for ZFS, offering a simpler set of datasets that might be some people's preference (especially if I can't do the following in time:) In a future revision of the zfsboot stuff, I'd like to offer a dialog where users can actually adjust the ZFS datasets. provide a menu listing the created dataset, with option to add more, and when you select a dataset, you can adjust its options or delete it (some really scary validation needs to happen here so you can't delete /usr if you have /usr/local) If the UFS stuff took the form of the current ZFS stuff (give me the entire disk, and i'll run with it), it would be fairly easy to implement, and could probably be done between 10.0-BETA1 and 10.0-BETA2 The more powerful features of the current partedit code, where it actually shows what is on your disk already, and allows you to just adjust it, and in general manage dual booting etc, that is a lot more complicated. -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 18:07:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 67E44547 for ; Thu, 10 Oct 2013 18:07:07 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 323972051 for ; Thu, 10 Oct 2013 18:07:07 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id r9AI6w12023447 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 10 Oct 2013 13:06:58 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.103]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Thu, 10 Oct 2013 13:06:57 -0500 From: "Teske, Devin" To: Allan Jude Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Topic: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI Thread-Index: AQHOxeOBPJPIP8ZCyUiSsjBzr2++AA== Date: Thu, 10 Oct 2013 18:06:57 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D720FC5142A@LTCFISWMSGMB21.FNFIS.com> References: <52531295.7090700@allanjude.com> <52539300.50305@allanjude.com> <5256E9D9.6060302@allanjude.com> In-Reply-To: <5256E9D9.6060302@allanjude.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.121] Content-Type: text/plain; charset="us-ascii" Content-ID: <217CF7AA49C4FB4E89C0FBFE32B3E1A6@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-10-10_06:2013-10-10,2013-10-10,1970-01-01 signatures=0 Cc: FreeBSD Current , "Teske, Devin" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 18:07:07 -0000 On Oct 10, 2013, at 10:54 AM, Allan Jude wrote: > On 2013-10-10 13:21, Warren Block wrote: >> [off-list reply] >>=20 >> I have not tested the new version yet. Is there any chance it >> supports setting up a gmirror? >>=20 >> Something I've been meaning to discuss with Devin is the concept of >> presets. The user would be able to choose from a list of presets: >>=20 >> Filesystem Layout >> ----------------- >> Merged / filesystem >> Split /, /var, /tmp, /usr filesystems >>=20 >> then >>=20 >> Filesystem Type >> --------------- >> UFS >> ZFS >>=20 >> then >>=20 >> Disk Layout >> ----------- >> Plain disk >> Mirror >> RAID >>=20 >> Those choices might change depending on earlier ones, like if they had >> chosen ZFS earlier they would get a choice of Mirror, RAID-Z1, >> RAID-Z2, and so on. >>=20 >> All this would build up a configuration, and at the end the user can >> edit it (filesystem sizes, for instance), then pick Go and walk away. >=20 > All of the UFS stuff is in C, so is read-only for me. >=20 > It is something I'd like to do, but it is really iffy if that can be > done in time for 10.0 >=20 > In general, gmirror support could be added to the ZFS section (renamed > to something else). So in our current 'zfs' menu, would become the 'new > partition manager' menu. Add an extra option for ZFS or UFS, and then > the vdev menu would context switch between zfs vdevs and ufs options > like gmirror and gstripe or something >=20 > Adding an extra option for / or / /var /tmp /usr is not a bad idea > either, maybe even for ZFS, offering a simpler set of datasets that > might be some people's preference (especially if I can't do the > following in time:) >=20 > In a future revision of the zfsboot stuff, I'd like to offer a dialog > where users can actually adjust the ZFS datasets. provide a menu listing > the created dataset, with option to add more, and when you select a > dataset, you can adjust its options or delete it (some really scary > validation needs to happen here so you can't delete /usr if you have > /usr/local) >=20 > If the UFS stuff took the form of the current ZFS stuff (give me the > entire disk, and i'll run with it), it would be fairly easy to > implement, and could probably be done between 10.0-BETA1 and 10.0-BETA2 >=20 > The more powerful features of the current partedit code, where it > actually shows what is on your disk already, and allows you to just > adjust it, and in general manage dual booting etc, that is a lot more > complicated. >=20 But the API exists (and we get a taste of the API in zfsboot). Specifically= , a script would mangle a disk and then call f_device_rescan to get the menus to popul= ate new entries. That aside, one of my plans for diskmgmt was to essentially let the user pe= rform free-wheeling adhoc configurations. Here's an extreme example of what I mean**: 1. Boot a box with naked disks 2. Create some gmultipath labels 3. Put a GPT scheme on the disk with one BSD partition 4. Put some UFS labels in the partition 5. Build a zpool out of a secondary label of each multipath'd disk ** Because afterall, FreeBSD shouldn't prevent you from doing something lik= e that. I think that if we try to tackle scenarios like that, then we'll really com= e up with a winning diskmgmt module (because right now I can't go do some UFS setup and then shove the products into a zpool). _When_ the ZFS management stuff is all integrated (which I plan on integrat= ing bits from pjd's zfsconf too), I think it should be agnostic about what you = give it as a device *and* allow you to configure many types of things without being fo= rced into an "either-or" situation (because often it can be a "I want both" situ= ation). (tuppence) --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 18:40:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6634E883 for ; Thu, 10 Oct 2013 18:40:44 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-pa0-f52.google.com (mail-pa0-f52.google.com [209.85.220.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3B3612307 for ; Thu, 10 Oct 2013 18:40:44 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id kl14so3129339pab.39 for ; Thu, 10 Oct 2013 11:40:43 -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=FkSnsIp6iiGnGHDLIUYXSgKOKSW8ZVWSuhObKsB4WB8=; b=czrmN6fNBfZsFOZqleK6fZkd6MMpik6x4DLV/b++Qr1w3avaehT9xcTpcG5IshmpTp gHVTiq2WYSqw8oBSlh3LX8QJZydVw8lpkxYqZ8EXXbWjQ1YAbIoajJR7+tkVgdS5eedn L1wCuhsMqv3WVXnk5DJ9JlNYvfY4y3FIM0GLsysrn2jjNdzNYfze0+XI/oIZRhK3XeHI o5zxz6Gk+Ys5fzwAsG9FAo4AgOSccxraEXlOBJmY4uxFKVWB05KMcdau+S6NL4JtlRr+ z0JTsnDECjNU21tDcsIoJjOwJvqNtrJszIj2tAfzUgB0mC2N1rwQW1YMvFBJ08uhPOVt ES7Q== X-Gm-Message-State: ALoCoQkkfb7FCqujANSoyHgeu8YzgYYyfz3i6n0wPiZRM0IENrzatOV3N3yTE/of9IdX48grItbl MIME-Version: 1.0 X-Received: by 10.68.108.3 with SMTP id hg3mr15382922pbb.91.1381428942414; Thu, 10 Oct 2013 11:15:42 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 11:15:42 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 11:15:42 -0700 (PDT) In-Reply-To: <5256D819.6060500@freebsd.org> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> Date: Thu, 10 Oct 2013 11:15:42 -0700 Message-ID: Subject: Re: rcs From: Jos Backus To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 18:40:44 -0000 On Oct 10, 2013 9:38 AM, "Julian Elischer" wrote: > > On 10/11/13 12:34 AM, Jos Backus wrote: >> >> On Thu, Oct 10, 2013 at 9:10 AM, Julian Elischer wrote: >>> >>> On 10/9/13 11:59 PM, Jos Backus wrote: >> >> [snip] >>>> >>>> OK, but please, can we replace RCS with Fossil in 11 then? That adds a real >>>> improvement to FreeBSD while giving people plenty of time to prepare. >>> >>> can fossil read rcs files? and how big is it compared to RCS? >> >> >> It seems there's some thought on importing CVS repos but according to 'fossil help import', only the git fast-export format is supported. >> In practice this means you'd loose history, yes. But it's not hard to keep the old RCS files somewhere else in case that history is needed. >> >> http://www.fossil-scm.org/fossil/wiki?name=Import+CVS+Repositories >> >> I just built devel/fossil and it yields a single binary, /usr/local/bin/fossil which clocks in at 1.8M. Given all the functionality it provides (plus it is in a similar class as git, see http://www.fossil-scm.org/index.html/doc/tip/www/fossil-v-git.wiki), I think that's a steal. >> >> It was started by the author of SQlite. If we require some kind of version control system in the base that's powerful, well-maintained and BSD-licensed, this really seems like a no-brainer. > > > well since people expect RCS.. it is not a no brainer. > you are asking people to learn a whole new tool for functionality that is currently very simple.. > edit file > ci -l file > add comment. Such is the price of progress. I envy people who don't have to learn anything new in order to stay employed :-) Jos > > > >> >> Jos >> -- >> Jos Backus >> jos at catnook.com > > From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 18:41:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6B3959CB for ; Thu, 10 Oct 2013 18:41:08 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 270C9231D for ; Thu, 10 Oct 2013 18:41:08 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1465A2154C for ; Thu, 10 Oct 2013 14:41:07 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Thu, 10 Oct 2013 14:41:07 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=K3CIbfmXqj5OZAvKFe4W1JKtUnk=; b=aHtbd Qw35UEm8F4lR8s/62kChnVA4TvS5S5IqtHAi4A1TSCg71PzdvIZBGQsodHsoI82m 2J4Zod7CpgtJEtjb7aIU72SUemtbh5S0mJryfG6gn9y+DaWKPa/7KcPcwfZrCYRp z1Pq65EEMD99FtH3Qh6hQQ85gY7/ne5xOtCMfc= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id E3D0D11C28A; Thu, 10 Oct 2013 14:41:06 -0400 (EDT) Message-Id: <1381430466.14387.32509497.13949CED@webmail.messagingengine.com> X-Sasl-Enc: lS83cRp10GJwwYLGcVFRIsHvqsNYAd26mj/dh82uAZ7j 1381430466 From: Mark Felder To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 Subject: Re: FreeBSD 10 and zfsd Date: Thu, 10 Oct 2013 13:41:06 -0500 In-Reply-To: <5256E680.4000008@allanjude.com> References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> <5256E2D5.4060101@allanjude.com> <5256E680.4000008@allanjude.com> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 18:41:08 -0000 On Thu, Oct 10, 2013, at 12:40, Allan Jude wrote: > On 2013-10-10 13:26, Alan Somers wrote: > > On Thu, Oct 10, 2013 at 11:24 AM, Allan Jude wrote: > >> On 2013-10-10 12:13, Mark Felder wrote: > >>> On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: > >>>> On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks > >>>> wrote: > >>>>> When i started using ZFS on FreeBSD I quickly found out that hot spares are > >>>>> not possible on FreeBSD. > >>>>> I was told that with zfsd it should be possible and that it would be > >>>>> included in FreeBSD 10. > >>>>> > >>>>> Is there some info about the zfsd function and how it could be used? > >>>> zfsd is currently not in FreeBSD/head and won't make it into 10, but > >>>> you can still get the source code from its project branch. It's being > >>>> used in production by at least two companies. > >>>> > >>> So FreeBSD is going to have inferior ZFS management compared to > >>> Solaris/Illumos/etc for another 2+ years? Why are things like this > >>> allowed to miss releases? > >>> _______________________________________________ > >>> freebsd-current@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >> ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev summit (3 > >> weeks ago). There is a lot of collaboration going on, to bring in some > >> work done by vendors like SpectraLogics. This is the type of feature > >> that can be assed in 10.1, it won't have to wait for 11. > >> > >> You can see Robert Watsons talk "How FreeBSD Works" to see why releases > >> are based on date, rather than on feature completion (because things are > >> never "finished") > >> > >> > >> > >> -- > >> Allan Jude > >> > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > Due to popular demand, I have located a round toit. I'm currently > > working on rebasing the zfsd project branch to head, after which I'll > > push SpectraLogic's recent changes. > See, all you have to do is complain loudly enough :p > I was sad more than anything. I'd been waiting for zfsd since the project was announced. :-) I'm glad to know we won't have to wait until 11.0. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 18:41:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 62E18AC7 for ; Thu, 10 Oct 2013 18:41:12 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DD85F231F for ; Thu, 10 Oct 2013 18:41:11 +0000 (UTC) Received: from pepe.smoke.local ([88.74.248.219]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MSMKx-1VNNHP2TKl-00TSoY for ; Thu, 10 Oct 2013 20:41:04 +0200 Message-ID: <5256F4BA.80209@gmx.net> Date: Thu, 10 Oct 2013 20:40:58 +0200 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: undefined reference to xenpci_alloc_space Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:awTGScDSfWobphpdriGyLzjj+DvBwRJZXrPO5mswDVG2qEj6Dpq uXHwpjIgrIWSV/Lk75UlV56vkwsgikIul0QnFWDOZ1ukH+A+3Wpy/W3xDScgCil5O18gXx4 +JMMYAk2Gs88SGE9ou5+skopokN8XcGwIAY1xoP7s+NK4a8Lu9t8FDgs3xX+h+QnRBAKUXH hEqUcLZGXuhrN8GKgxTAg== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 18:41:12 -0000 Hi List, is it intended that kernel does not build if device xenpci is omitted in the kernel config? I get the following error: linking kernel gnttab.o: In function `gnttab_resume': /usr/src/sys/xen/gnttab.c:(.text+0xe47): undefined reference to `xenpci_alloc_space' Thanks, Michael From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 18:52:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 895A71E9; Thu, 10 Oct 2013 18:52:08 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6DDDE23E5; Thu, 10 Oct 2013 18:52:08 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id C2BCA2AA4A3; Thu, 10 Oct 2013 12:52:01 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id 9465C1CC17; Thu, 10 Oct 2013 13:51:33 -0500 (EST) Date: Thu, 10 Oct 2013 13:51:33 -0500 From: Diane Bruce To: Jos Backus Subject: Re: rcs Message-ID: <20131010185133.GA74598@night.db.net> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Kimmo Paasiala , George Mitchell , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 18:52:08 -0000 ... > >>>> OK, but please, can we replace RCS with Fossil in 11 then? That adds a > real > >>>> improvement to FreeBSD while giving people plenty of time to prepare. Fossil was showing promise the last time I tried it. Quite frankly > > well since people expect RCS.. it is not a no brainer. > > you are asking people to learn a whole new tool for functionality that > is currently very simple.. > > edit file > > ci -l file > > add comment. pfft as long as any SCS can read my old rcs files this old fart does not mind. - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 18:54:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D584638F; Thu, 10 Oct 2013 18:54:31 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 817202419; Thu, 10 Oct 2013 18:54:31 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id c9so2234013qcz.28 for ; Thu, 10 Oct 2013 11:54:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=5MyfyENuJmEBRLuJ7tkyJiE3XoRDPSLqYLSqt1CBDvM=; b=GLeyHvG5QvZ/2c27g1fGatlGEd6B8oeLtrppCtLfUakr8ZJ6CsabVWTgDa/4zPJFeP X+K2RhTmS5U8QSCRiw3h71HsPOpomIfNwerMvom6LbMZUwVSLSc3ZCSnaRm6BBLN5/yH ZDziZDRWcKJyqp6A4+js4UDaA7g4GVj2flaCiTPSlWQKQWEi0bC4ZCB0uCiz+xxsh/6t Q2h/OAf28Aq2QfwjL7MJ+zXMtVt6oBWlmja55qKLYZQyySfYINK9D1Zf3vrNdeeuMiWv f7id+AA91TXLcXJn1cQ6WOQ7V0CNous8klD7k16Mh3xpQd5Lp75WqPBpFtpnDgRfmHvt bc2g== X-Received: by 10.229.38.202 with SMTP id c10mr13172674qce.23.1381431270644; Thu, 10 Oct 2013 11:54:30 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Thu, 10 Oct 2013 11:53:50 -0700 (PDT) In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> From: Igor Mozolevsky Date: Thu, 10 Oct 2013 19:53:50 +0100 X-Google-Sender-Auth: 3N6UzG42RdxyEfRko0F_luGH6OQ Message-ID: Subject: Re: rcs To: Jos Backus Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 18:54:32 -0000 On 10 October 2013 19:15, Jos Backus wrote: > On Oct 10, 2013 9:38 AM, "Julian Elischer" wrote: > [snip] > > well since people expect RCS.. it is not a no brainer. > > you are asking people to learn a whole new tool for functionality that > is currently very simple.. > > edit file > > ci -l file > > add comment. > > Such is the price of progress. I envy people who don't have to learn > anything new in order to stay employed :-) > So your definition of progress is "doing more work to achieve the same result"?.. -- Igor M. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 19:06:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6BA6E942 for ; Thu, 10 Oct 2013 19:06:15 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2B76924F7 for ; Thu, 10 Oct 2013 19:06:15 +0000 (UTC) Received: from [192.168.2.2] (ip4da3063d.direct-adsl.nl [77.163.6.61]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 695325C5A; Thu, 10 Oct 2013 21:06:08 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_5BD9F0B5-1069-4AC1-B8DE-BF8C5D0819F7"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: make universe fails, apparently in lib/clang/include (all) From: Dimitry Andric In-Reply-To: <5256D9A1.6050605@dell.com> Date: Thu, 10 Oct 2013 21:02:53 +0200 Message-Id: <3AB373DA-55AB-4D93-A1C5-36701C757A45@FreeBSD.org> References: <5256D9A1.6050605@dell.com> To: Eric van Gyzen X-Mailer: Apple Mail (2.1510) Cc: freebsd-current@freebsd.org, Eric van Gyzen X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 19:06:15 -0000 --Apple-Mail=_5BD9F0B5-1069-4AC1-B8DE-BF8C5D0819F7 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On Oct 10, 2013, at 18:45, Eric van Gyzen wrote: > "make universe" is consistently failing in the following way. > "_.amd64.amd64.buildworld" contains: > > ======== > > ===> lib/clang/libllvmx86desc (all) > ===> lib/clang/libllvmx86disassembler (all) > ===> lib/clang/libllvmx86info (all) > ===> lib/clang/libllvmx86instprinter (all) > ===> lib/clang/libllvmx86utils (all) > ===> lib/clang/include (all) > 1 error > > make[3]: stopped in /home/freebsd > *** [everything] Error code 2 Hi Eric, Can you please upload the full _.amd64.amd64.buildworld file somewhere? The actual error will have occurred earlier in the build, and it is not directly visible in the last few lines. -Dimitry --Apple-Mail=_5BD9F0B5-1069-4AC1-B8DE-BF8C5D0819F7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iEYEARECAAYFAlJW+ecACgkQsF6jCi4glqN2gACgkbV+K2OC5/gkJi6cfabYeSSy 6W0An0mzdDxXKnzNuTkt1Dk1P7oHyaCJ =pN1C -----END PGP SIGNATURE----- --Apple-Mail=_5BD9F0B5-1069-4AC1-B8DE-BF8C5D0819F7-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 19:11:39 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 89360D7D; Thu, 10 Oct 2013 19:11:39 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3DA4D2576; Thu, 10 Oct 2013 19:11:39 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.90,1074,1371099600"; d="scan'208";a="56385214" Message-ID: <5256FBE2.7060503@vangyzen.net> Date: Thu, 10 Oct 2013 14:11:30 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: make universe fails, apparently in lib/clang/include (all) References: <5256D9A1.6050605@dell.com> <3AB373DA-55AB-4D93-A1C5-36701C757A45@FreeBSD.org> In-Reply-To: <3AB373DA-55AB-4D93-A1C5-36701C757A45@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Eric van Gyzen , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 19:11:39 -0000 On 10/10/2013 14:02, Dimitry Andric wrote: > On Oct 10, 2013, at 18:45, Eric van Gyzen wrote: >> "make universe" is consistently failing in the following way. >> "_.amd64.amd64.buildworld" contains: >> >> ======== >> >> ===> lib/clang/libllvmx86desc (all) >> ===> lib/clang/libllvmx86disassembler (all) >> ===> lib/clang/libllvmx86info (all) >> ===> lib/clang/libllvmx86instprinter (all) >> ===> lib/clang/libllvmx86utils (all) >> ===> lib/clang/include (all) >> 1 error >> >> make[3]: stopped in /home/freebsd >> *** [everything] Error code 2 > Hi Eric, > > Can you please upload the full _.amd64.amd64.buildworld file somewhere? > The actual error will have occurred earlier in the build, and it is not > directly visible in the last few lines. Dimitry, Will do. I looked back many lines, and didn't see any errors. Maybe another pair of eyes will help. Eric From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 19:37:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7BE316A1 for ; Thu, 10 Oct 2013 19:37:55 +0000 (UTC) (envelope-from maciej@suszko.eu) Received: from archeo.suszko.eu (archeo.unixguru.pl [IPv6:2001:41d0:1:f47a::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3AF442700 for ; Thu, 10 Oct 2013 19:37:54 +0000 (UTC) Received: from archeo (localhost [127.0.0.1]) by archeo.suszko.eu (Postfix) with ESMTP id 538D0206381C; Thu, 10 Oct 2013 21:37:45 +0200 (CEST) X-Virus-Scanned: amavisd-new at archeo.local Received: from archeo.suszko.eu ([127.0.0.1]) by archeo (archeo.local [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id U4Z_-qMTgXIP; Thu, 10 Oct 2013 21:37:45 +0200 (CEST) Received: from arsenic (89-79-234-160.dynamic.chello.pl [89.79.234.160]) by archeo.suszko.eu (Postfix) with ESMTPSA id A9518206381B; Thu, 10 Oct 2013 21:37:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=suszko.eu; s=dkim; t=1381433864; bh=Qk2TVskY2g4ovrzisSXiju3Tsr8+8GvlX9NdZ8+FIHQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=PQHO6y93Ufrp/S9qKTCjw0RiCnWnIF1gZWH6Csy6/a4pOjSHqkCyde5ilrMnh6lLn m+X9T4mWg1y8N6kTDWTiG2QKgCcSzZz0KpxrlEuQ+h5cSs0OdqkAYfHMIc/73gCpyo 2ZmVGc1FOOwh8v/9TqAlTfuxYFD4FIOM6adFQm3I= Date: Thu, 10 Oct 2013 21:37:39 +0200 From: Maciej Suszko To: Fabian Keil Subject: Re: claws-mail deadlocking in iconv Message-ID: <20131010213739.19272554@arsenic> In-Reply-To: <73d40037.635a97ef@fabiankeil.de> References: <73d40037.635a97ef@fabiankeil.de> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/=f7XmLIyPcMGNb83o0DAfL3"; protocol="application/pgp-signature" Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 19:37:55 -0000 --Sig_/=f7XmLIyPcMGNb83o0DAfL3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Fabian Keil wrote: > After the iconv import claws-mail started to deadlock in iconv every > now and then on my system, which prevented claws-mail from rendering > windows or reacting to input. >=20 > So far I haven't been able to reproduce this intentionally and various > rebuilds of ports, kernel and userland (mainly for other reasons) had > no effect. >=20 > When the problem occurs, trying to attach to the process causes > gdb and gdb76 to crash which also crashes claws-mail, but sending > SIGABRT causes a proper core dump that can be analysed with gdb. >=20 > The backtraces always show that there is only one thread running and > it's trying to lock cm_lock in _citrus_mapper_close(), which > apparently is already locked due to a _citrus_mapper_close() > recursion. Examples: [...] > This patch: > http://www.fabiankeil.de/sourcecode/freebsd/iconv-Let-_citrus_mapper_clos= e-unlock-cm_lock-before-calli.diff > seems to prevent the deadlock, but I'm not 100% sure that it's > correct and I'm also a bit surprised by the lack of reports from > other claws-mail users. >=20 > Did anyone else run into this or can comment on the patch or > the backtraces? In my case Claws Mail was hanging everytime I tried to access one of my bigger IMAP folders (50k+ messages). It was 100% reproducible. The patch seems to solve the problem for me - Claws is running now smooth, without any locks. --=20 regards, Maciej Suszko. --Sig_/=f7XmLIyPcMGNb83o0DAfL3 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iEYEARECAAYFAlJXAgcACgkQCikUk0l7iGrGCQCdGKNj7YMGqLuNKmB65RXaA8FA 7LwAn1SgDZgmNcE0QOjAxYDqBc0EsSt+ =fg2I -----END PGP SIGNATURE----- --Sig_/=f7XmLIyPcMGNb83o0DAfL3-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 19:43:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A48B8A2A for ; Thu, 10 Oct 2013 19:43:21 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 786D42770 for ; Thu, 10 Oct 2013 19:43:21 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id rr4so3065170pbb.34 for ; Thu, 10 Oct 2013 12:43:15 -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=WhrK8/8Ib1PeCAE7znc/FoYN15HNBynm5huiITTGLqM=; b=lgaw5fBm2rP4OKS1ZEmnMHcfiN7SuF1GABU+NDcMBU6N9mq8/4gT27QP1omUKwUPg8 zYkWMXl+UsKnHhgRLDSKLUgDoeCDLZmRJV3lu78kTeF+VJbSceec7NNHYx8Qz0pfCisI b1dgsCl5Dg4Hv8o6PaqjFUFmgaYVYJTZlx+//AL6bh83SLdI6oUn/iWwTJU3Weje3wWu 33yysdvMymFczw/3WmwlwgIp7uqFu/KdLwuxADsOKb21nc47ypsuv0TnvHPFpj0PDqZr MQA/zUtMddmS/zELnGpLNH4wFPMHlyTqKLUislI1DrqUlrGJFzQqXws4RKJ8TTDdJonm SZyg== X-Gm-Message-State: ALoCoQkhDIkjUUIkSS0HVtf6eH09ilBHkCzv7VOXCbwI6VcZafLPd+cR52ggrTJIpbfB6Fn7O2d3 MIME-Version: 1.0 X-Received: by 10.67.24.7 with SMTP id ie7mr17155117pad.112.1381433760280; Thu, 10 Oct 2013 12:36:00 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 12:36:00 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 12:36:00 -0700 (PDT) In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> Date: Thu, 10 Oct 2013 12:36:00 -0700 Message-ID: Subject: Re: rcs From: Jos Backus To: Igor Mozolevsky Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 19:43:21 -0000 On Oct 10, 2013 11:54 AM, "Igor Mozolevsky" wrote: > > > > > On 10 October 2013 19:15, Jos Backus wrote: >> >> On Oct 10, 2013 9:38 AM, "Julian Elischer" wrote: > > > [snip] > >> >> > well since people expect RCS.. it is not a no brainer. >> > you are asking people to learn a whole new tool for functionality that >> is currently very simple.. >> > edit file >> > ci -l file >> > add comment. >> >> Such is the price of progress. I envy people who don't have to learn >> anything new in order to stay employed :-) > > > So your definition of progress is "doing more work to achieve the same result"?.. That would only be true if they were equivalent, and we didn't care about the extra features. You may not, but many people do, as the popularity of git and other distributed version control systems proves. Jos > > -- > Igor M. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 19:52:34 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A47FBF90; Thu, 10 Oct 2013 19:52:34 +0000 (UTC) (envelope-from tijl@coosemans.org) Received: from mailrelay010.isp.belgacom.be (mailrelay010.isp.belgacom.be [195.238.6.177]) by mx1.freebsd.org (Postfix) with ESMTP id AD5EC280A; Thu, 10 Oct 2013 19:52:33 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlQGAC0FV1JbsWpC/2dsb2JhbABRCIMHOMIBgSQXdIIlAQEFViMQCw4KCSUPKh4GiB0Iui2OCgSBOQeEIwOQK4dZkgODJjqBNQ Received: from 66.106-177-91.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([91.177.106.66]) by relay.skynet.be with ESMTP; 10 Oct 2013 21:52:14 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.7/8.14.7) with ESMTP id r9AJqCOn006360; Thu, 10 Oct 2013 21:52:13 +0200 (CEST) (envelope-from tijl@coosemans.org) Date: Thu, 10 Oct 2013 21:52:06 +0200 From: Tijl Coosemans To: Fabian Keil Subject: Re: claws-mail deadlocking in iconv Message-ID: <20131010215206.2e0896df@kalimero.tijl.coosemans.org> In-Reply-To: <73d40037.635a97ef@fabiankeil.de> References: <73d40037.635a97ef@fabiankeil.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA512; boundary="Sig_/Jj6CG1SxWjQpcL54frLwbB3"; protocol="application/pgp-signature" Cc: freebsd-current@freebsd.org, peter@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 19:52:34 -0000 --Sig_/Jj6CG1SxWjQpcL54frLwbB3 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 9 Oct 2013 18:34:46 +0200 Fabian Keil wrote: > After the iconv import claws-mail started to deadlock in iconv every now > and then on my system, which prevented claws-mail from rendering windows > or reacting to input. >=20 > So far I haven't been able to reproduce this intentionally and various > rebuilds of ports, kernel and userland (mainly for other reasons) had > no effect. >=20 > When the problem occurs, trying to attach to the process causes > gdb and gdb76 to crash which also crashes claws-mail, but sending > SIGABRT causes a proper core dump that can be analysed with gdb. >=20 > The backtraces always show that there is only one thread running and > it's trying to lock cm_lock in _citrus_mapper_close(), which apparently > is already locked due to a _citrus_mapper_close() recursion. Examples: >=20 > #0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.= S:37 > 37 RSYSCALL_ERR(_umtx_op) > [New Thread 80a806400 (LWP 100487/claws-mail)] > (gdb) where > #0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.= S:37 > #1 0x00000008084861a6 in __thr_rwlock_wrlock (rwlock=3D0x80a8a47c0, tsp= =3D) at /usr/src/lib/libthr/thread/thr_umtx.c:296 > #2 0x0000000808489b1d in rwlock_wrlock_common (rwlock=3D, abstime=3D0x0) at /usr/src/lib/libthr/thread/thr_rwlock.c:267 > #3 0x0000000808489a8b in _pthread_rwlock_wrlock (rwlock=3D0x80a8a47c0) a= t /usr/src/lib/libthr/thread/thr_rwlock.c:289 > #4 0x000000080911e848 in _citrus_mapper_close (cm=3D0x80b5a2d80) at /usr= /src/lib/libc/iconv/citrus_mapper.c:375 > #5 0x000000080d205d18 in _citrus_mapper_serial_mapper_uninit (cm=3D0x80b= 5a2d40) at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/c= itrus_mapper_serial.c:110 > #6 0x000000080911e8d7 in mapper_close (cm=3D0x80b5a2d40) at /usr/src/lib= /libc/iconv/citrus_mapper.c:188 > #7 0x000000080911e88c in _citrus_mapper_close (cm=3D) at /usr/src/lib/libc/iconv/citrus_mapper.c:384 > #8 0x000000080c4e83f3 in close_srcs (sl=3D0x80b591140) at /usr/src/lib/l= ibiconv_modules/iconv_std/citrus_iconv_std.c:206 > #9 0x000000080c4e7dc9 in _citrus_iconv_std_iconv_uninit_shared (ci=3D) at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv= _std.c:415 > #10 0x00000008090f3f95 in release_shared (ci=3D0x80a8ee630) at /usr/src/l= ib/libc/iconv/citrus_iconv.c:99 > #11 0x00000008090f4002 in _citrus_iconv_close (cv=3D0x80d88d5d0) at /usr/= src/lib/libc/iconv/citrus_iconv.c:335 > #12 0x00000008090f1ca6 in iconv_close (handle=3D0x80a8a47c0) at /usr/src/= lib/libc/iconv/iconv.c:131 > #13 0x000000000046376d in conv_iconv_strdup (inbuf=3D0x7fffffff58b0 "\n",= src_code=3D0x80b5b4db0 "Windows-1252", dest_code=3D0x6f03d0 "UTF-8") at co= deconv.c:895 > #14 0x0000000000463d13 in conv_convert (conv=3D0x80b5a4e80, outbuf=3D0x7f= ffffff3720 "", outlen=3D8192, inbuf=3D0x7fffffff58b0 "\n") at codeconv.c:734 > #15 0x00000000005e22ac in textview_write_line (textview=3D0x80a959cc0, st= r=3D0x7fffffff58b0 "\n", conv=3D0x80b5a4e80, do_quote_folding=3D1) at textv= iew.c:1573 > #16 0x00000000005df8e4 in textview_write_body (textview=3D0x80a959cc0, mi= meinfo=3D0x80aad2d00) at textview.c:1177 > #17 0x00000000005e5363 in textview_add_part (textview=3D0x80a959cc0, mime= info=3D0x80aad2d00) at textview.c:826 > #18 0x00000000005e4053 in recursive_add_parts (textview=3D0x80a959cc0, no= de=3D0x80a826190) at textview.c:839 > #19 0x00000000005e4302 in recursive_add_parts (textview=3D0x80a959cc0, no= de=3D0x80aa81d20) at textview.c:888 > #20 0x00000000005e4302 in recursive_add_parts (textview=3D0x80a959cc0, no= de=3D0x80a828890) at textview.c:888 > #21 0x00000000005defa1 in textview_add_parts (textview=3D0x80a959cc0, mim= einfo=3D0x80b610700) at textview.c:898 > #22 0x00000000005deb85 in textview_show_part (textview=3D0x80a959cc0, mim= einfo=3D0x80b610700, fp=3D0x8094319a0) at textview.c:645 > [...] >=20 > #0 0x0000000808491b9c in __error () from /lib/libthr.so.3 > #1 0x000000080848bb1d in rwlock_wrlock_common (rwlock=3D, abstime=3D0x0) at /usr/src/lib/libthr/thread/thr_rwlock.c:267 > #2 0x000000080848ba8b in _pthread_rwlock_wrlock (rwlock=3D0x80a8ede20) a= t /usr/src/lib/libthr/thread/thr_rwlock.c:289 > #3 0x000000080911f848 in _citrus_mapper_close (cm=3D0x80a8bfc40) at /usr= /src/lib/libc/iconv/citrus_mapper.c:375 > #4 0x000000080ce02d18 in _citrus_mapper_serial_mapper_uninit (cm=3D0x80a= 8bfc00) at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/c= itrus_mapper_serial.c:110 > #5 0x000000080911f8d7 in mapper_close (cm=3D0x80a8bfc00) at /usr/src/lib= /libc/iconv/citrus_mapper.c:188 > #6 0x000000080911f88c in _citrus_mapper_close (cm=3D) at /usr/src/lib/libc/iconv/citrus_mapper.c:384 > #7 0x000000080c5893f3 in close_srcs (sl=3D0x80a8edda0) at /usr/src/lib/l= ibiconv_modules/iconv_std/citrus_iconv_std.c:206 > #8 0x000000080c588dc9 in _citrus_iconv_std_iconv_uninit_shared (ci=3D) at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv= _std.c:415 > #9 0x00000008090f4f95 in release_shared (ci=3D0x80b408890) at /usr/src/l= ib/libc/iconv/citrus_iconv.c:99 > #10 0x00000008090f5002 in _citrus_iconv_close (cv=3D0x80b782630) at /usr/= src/lib/libc/iconv/citrus_iconv.c:335 > #11 0x00000008090f2ca6 in iconv_close (handle=3D0x80a8ede20) at /usr/src/= lib/libc/iconv/iconv.c:131 > #12 0x000000000046376d in conv_iconv_strdup ( > inbuf=3D0x80b600e00 "[...]"..., src_code=3D0x80b782640 "ISO-8859-15",= dest_code=3D0x80c07ab24 "UTF-8") at codeconv.c:895 > #13 0x0000000000463f2f in conv_codeset_strdup ( > inbuf=3D0x80b600e00 "[...]"..., src_code=3D0x80b782640 "ISO-8859-15",= dest_code=3D0x80c07ab24 "UTF-8") at codeconv.c:774 > #14 0x000000080c07a1a7 in get_part_as_string (mimeinfo=3D0x80aad2d80) at = pgpinline.c:153 > #15 0x000000080c078333 in pgpinline_is_encrypted (mimeinfo=3D0x80aad2d80)= at pgpinline.c:375 > [...] >=20 > #0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.= S:37 > #1 0x00000008084861a6 in __thr_rwlock_wrlock (rwlock=3D0x80bf93f40, tsp= =3D) at /usr/src/lib/libthr/thread/thr_umtx.c:296 > #2 0x0000000808489b1d in rwlock_wrlock_common (rwlock=3D, abstime=3D0x0) at /usr/src/lib/libthr/thread/thr_rwlock.c:267 > #3 0x0000000808489a8b in _pthread_rwlock_wrlock (rwlock=3D0x80bf93f40) a= t /usr/src/lib/libthr/thread/thr_rwlock.c:289 > #4 0x000000080911e848 in _citrus_mapper_close (cm=3D0x80bfa0b40) at /usr= /src/lib/libc/iconv/citrus_mapper.c:375 > #5 0x000000080d08ad18 in _citrus_mapper_serial_mapper_uninit (cm=3D0x80b= fa0b00) at /usr/src/lib/libiconv_modules/mapper_parallel/../mapper_serial/c= itrus_mapper_serial.c:110 > #6 0x000000080911e8d7 in mapper_close (cm=3D0x80bfa0b00) at /usr/src/lib= /libc/iconv/citrus_mapper.c:188 > #7 0x000000080911e88c in _citrus_mapper_close (cm=3D) at /usr/src/lib/libc/iconv/citrus_mapper.c:384 > #8 0x000000080ae2c3f3 in close_srcs (sl=3D0x80bf9fbc0) at /usr/src/lib/l= ibiconv_modules/iconv_std/citrus_iconv_std.c:206 > #9 0x000000080ae2bdc9 in _citrus_iconv_std_iconv_uninit_shared (ci=3D) at /usr/src/lib/libiconv_modules/iconv_std/citrus_iconv= _std.c:415 > #10 0x00000008090f3f95 in release_shared (ci=3D0x80bd59ac0) at /usr/src/l= ib/libc/iconv/citrus_iconv.c:99 > #11 0x00000008090f4002 in _citrus_iconv_close (cv=3D0x80dc1a3d0) at /usr/= src/lib/libc/iconv/citrus_iconv.c:335 > #12 0x00000008090f1ca6 in iconv_close (handle=3D0x80bf93f40) at /usr/src/= lib/libc/iconv/iconv.c:131 > #13 0x000000000046376d in conv_iconv_strdup (inbuf=3D0x80bd570c0 "[...]",= src_code=3D0x7fffffff5d60 "ISO-8859-2", dest_code=3D0x6f03d0 "UTF-8") at c= odeconv.c:895 > #14 0x0000000000463f2f in conv_codeset_strdup (inbuf=3D0x80bd570c0 "[...]= ", src_code=3D0x7fffffff5d60 "ISO-8859-2", dest_code=3D0x0) at codeconv.c:7= 74 > #15 0x00000000005f63f0 in unmime_header (encoded_str=3D0x7fffffff7e94 "[.= ..]", addr_field=3D1) at unmime.c:144 > #16 0x0000000000464a56 in conv_unmime_header (str=3D0x7fffffff7e94 "[...]= ", default_encoding=3D0x0, addr_field=3D1) > at codeconv.c:1516 > #17 0x000000000059588a in parse_stream (data=3D0x8094319a0, isstring=3D0,= flags=3D{perm_flags =3D 3, tmp_flags =3D 0}, full=3D0, decrypted=3D0) at p= rocheader.c:558 > #18 0x0000000000595234 in procheader_parse_stream (fp=3D0x8094319a0, flag= s=3D{perm_flags =3D 3, tmp_flags =3D 0}, full=3D0, decrypted=3D0) at proche= ader.c:461 > #19 0x0000000000595195 in procheader_parse_file (file=3D0x80d4202b0 "/hom= e/fk/.claws-mail/tempfolder/processing/18", flags=3D{perm_flags =3D 3, tmp_= flags =3D 0}, full=3D0, decrypted=3D0) at procheader.c:354 > [...] >=20 > This patch: > http://www.fabiankeil.de/sourcecode/freebsd/iconv-Let-_citrus_mapper_clos= e-unlock-cm_lock-before-calli.diff > seems to prevent the deadlock, but I'm not 100% sure that it's correct and > I'm also a bit surprised by the lack of reports from other claws-mail use= rs. >=20 > Did anyone else run into this or can comment on the patch or > the backtraces? I've been using the patch all day now and the deadlocks seem to have disappeared. I've CCed Peter Wemm who worked on the locking in libc iconv. Besides the case in the patch there's a _mapper_close call on line 350 in the same file that should be looked at as well. --Sig_/Jj6CG1SxWjQpcL54frLwbB3 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (FreeBSD) iF4EAREKAAYFAlJXBWsACgkQfoCS2CCgtivhAAD/TyqkK2uiBd+EWJ0r2MqZCDmX IhaLdbYk8KHe6n8bMMYA/0resZEYwPuDHVvsRmtJEW18YZ75aIsqTPUWWM3p8WbE =RAuk -----END PGP SIGNATURE----- --Sig_/Jj6CG1SxWjQpcL54frLwbB3-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:00:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E9D8B432 for ; Thu, 10 Oct 2013 20:00:03 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A098F2877 for ; Thu, 10 Oct 2013 20:00:03 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1VUMOp-000jQV-6h>; Thu, 10 Oct 2013 21:59:55 +0200 Received: from g226176073.adsl.alicedsl.de ([92.226.176.73] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1VUMOp-000ADP-0s>; Thu, 10 Oct 2013 21:59:55 +0200 Date: Thu, 10 Oct 2013 21:59:49 +0200 From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: Re: FreeBSD 10 and zfsd Message-ID: <20131010215949.3214f4c2@thor.walstatt.dyndns.org> In-Reply-To: <1381430466.14387.32509497.13949CED@webmail.messagingengine.com> References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> <5256E2D5.4060101@allanjude.com> <5256E680.4000008@allanjude.com> <1381430466.14387.32509497.13949CED@webmail.messagingengine.com> Organization: FU Berlin X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/N1_XIULFj4LrssVhhs2rUzG"; protocol="application/pgp-signature" X-Originating-IP: 92.226.176.73 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 20:00:04 -0000 --Sig_/N1_XIULFj4LrssVhhs2rUzG Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 10 Oct 2013 13:41:06 -0500 Mark Felder wrote: >=20 >=20 > On Thu, Oct 10, 2013, at 12:40, Allan Jude wrote: > > On 2013-10-10 13:26, Alan Somers wrote: > > > On Thu, Oct 10, 2013 at 11:24 AM, Allan Jude > > > wrote: > > >> On 2013-10-10 12:13, Mark Felder wrote: > > >>> On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: > > >>>> On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks > > >>>> wrote: > > >>>>> When i started using ZFS on FreeBSD I quickly found out that > > >>>>> hot spares are not possible on FreeBSD. > > >>>>> I was told that with zfsd it should be possible and that it > > >>>>> would be included in FreeBSD 10. > > >>>>> > > >>>>> Is there some info about the zfsd function and how it could > > >>>>> be used? > > >>>> zfsd is currently not in FreeBSD/head and won't make it into > > >>>> 10, but you can still get the source code from its project > > >>>> branch. It's being used in production by at least two > > >>>> companies. > > >>>> > > >>> So FreeBSD is going to have inferior ZFS management compared to > > >>> Solaris/Illumos/etc for another 2+ years? Why are things like > > >>> this allowed to miss releases? > > >>> _______________________________________________ > > >>> freebsd-current@freebsd.org mailing list > > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > > >>> To unsubscribe, send any mail to > > >>> "freebsd-current-unsubscribe@freebsd.org" > > >> ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev > > >> summit (3 weeks ago). There is a lot of collaboration going on, > > >> to bring in some work done by vendors like SpectraLogics. This > > >> is the type of feature that can be assed in 10.1, it won't have > > >> to wait for 11. > > >> > > >> You can see Robert Watsons talk "How FreeBSD Works" to see why > > >> releases are based on date, rather than on feature completion > > >> (because things are never "finished") > > >> > > >> > > >> > > >> -- > > >> Allan Jude > > >> > > >> _______________________________________________ > > >> freebsd-current@freebsd.org mailing list > > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > > >> To unsubscribe, send any mail to > > >> "freebsd-current-unsubscribe@freebsd.org" > > > Due to popular demand, I have located a round toit. I'm currently > > > working on rebasing the zfsd project branch to head, after which > > > I'll push SpectraLogic's recent changes. > > See, all you have to do is complain loudly enough :p > >=20 >=20 > I was sad more than anything. I'd been waiting for zfsd since the > project was announced. :-) I'm glad to know we won't have to wait > until 11.0. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" Ha! Very funny. I created a RAIDZ1 pool and by reading the man page for zpool, which states precisely how to create a hot spare for a given pool. I wasn't aware until now that this action was useless, and even dangerous. Well, bravo, I must admit, the man page does not give any kind of warning that one can not rely on a hot spare. oh --Sig_/N1_XIULFj4LrssVhhs2rUzG Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJSVwc5AAoJEOgBcD7A/5N85bQIAMfeBgJikS2PhK0m+/zU4wLa Xtlnv/YTPl+bJ4UssgF4J6G/dorHD6nKocc1hJzAmohkBPkqgdP4nx+r2sOYGJuA kPNJvcAmHaCAnPZgMhUYLMSCi/MVDVDOD7KzMTtkVyOeM/BPXyXxAR7wqGbvXlU+ +UkLca3feYQ/O2gozbdTfaBmfBnUCITleVMGQV4dxTTce0rh3ZZKVHW5iIoD9XeX 5og1/XC6C/ZDLi9sIQuruDdjEduKAQq4K/t9WPHz4/btZ1ZBBsRkQfExswcK3kWL hQMYfK1V4suPlbz1yRcZeOhyNZAK4xxSrhEC3my60GnZsVndk4TOGyHy7L2CIUU= =dC9b -----END PGP SIGNATURE----- --Sig_/N1_XIULFj4LrssVhhs2rUzG-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:07:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2BB75CC2; Thu, 10 Oct 2013 20:07:31 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qe0-x22a.google.com (mail-qe0-x22a.google.com [IPv6:2607:f8b0:400d:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA4572925; Thu, 10 Oct 2013 20:07:30 +0000 (UTC) Received: by mail-qe0-f42.google.com with SMTP id gc15so2462468qeb.15 for ; Thu, 10 Oct 2013 13:07:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=wAHegIc+RSA7xcuyCtNSue3AD0OGEnFak36Uu8v2U9k=; b=e5+7xM141X1SoUH++FWORwOUrZIfOFLe3w9nfURGxS5LCPmD3/5It4rQA2+asMABo9 FVbESN23gAqIhVioMMCPvpsRvB6JRgq5IDH6HrSTRiXaVnQ95x+VWrtn9WfH07AIL0Uo tWWHL1xC3VmlCUoY0Giy8Rt3mQ/ogpZrLRe1m9mVFOypTP2oCfc1SS/0fj+lU3q8jAoq ldFaRZICTDZKeMd/VcGwhyNNYbBWAddocCIWoOmCwHpN2GbYsiPJvgsni56ALq0JCY3/ Npny5lL9AKRuBGJywDuCzLxJx2wMi2CJAeygmtFE8amx1JKVnYB9fDcMM7KcsfhTz1WF O4Iw== X-Received: by 10.49.116.210 with SMTP id jy18mr3579918qeb.65.1381435649886; Thu, 10 Oct 2013 13:07:29 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Thu, 10 Oct 2013 13:06:48 -0700 (PDT) In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> From: Igor Mozolevsky Date: Thu, 10 Oct 2013 21:06:48 +0100 X-Google-Sender-Auth: AO3-aFSexQ_jGdkC6wcdu2dgZIc Message-ID: Subject: Re: rcs To: Jos Backus Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 20:07:31 -0000 On 10 October 2013 20:36, Jos Backus wrote: > > On Oct 10, 2013 11:54 AM, "Igor Mozolevsky" wrote: > > > > On 10 October 2013 19:15, Jos Backus wrote: > >> > >> On Oct 10, 2013 9:38 AM, "Julian Elischer" wrote: > > > > > > [snip] > > > >> > >> > well since people expect RCS.. it is not a no brainer. > >> > you are asking people to learn a whole new tool for functionality > that > >> is currently very simple.. > >> > edit file > >> > ci -l file > >> > add comment. > >> > >> Such is the price of progress. I envy people who don't have to learn > >> anything new in order to stay employed :-) > > > > > > So your definition of progress is "doing more work to achieve the same > result"?.. > > That would only be true if they were equivalent, and we didn't care about > the extra features. You may not, but many people do, as the popularity of > git and other distributed version control systems proves. > You're missing the point- the requirement is "provide a way to keep track of changes for file X" not "have many fancy and unnecessary features"... -- Igor M. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:18:55 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DA71235B for ; Thu, 10 Oct 2013 20:18:55 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com [209.85.192.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AC7AC29E1 for ; Thu, 10 Oct 2013 20:18:55 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id y13so3152865pdi.19 for ; Thu, 10 Oct 2013 13:18:49 -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=03p1YJlpq2hnyKwPpzwGnPQwCxdFBmfXxKl/uhHIZWA=; b=Novzvvzpfp0giG1yTmxC2LpXebocENsz64izdSOZpZdksW0fUgDkUzciKWXwezupIe aV409ZNAv9/iojn5YrHL3e1CcqLQF8rjTPccXN/keDuFoS/SrMn482jCUOk9+5HyIyDo s36LMKkpEfVVh2K0y15fCmxe2f/2cG7REzbrIcqn5Z1t8U/47QCDLol8QLHuJpcRaBtB pzreZ3dV0nSLdFx5YDS1Rt0J+Fjdbo884VDNndsUO/YDdhbfHO5KAG3JDL/hZqDrqsaG 6HSFdjYqXAgPPsYCauIwgireFMfTch7bymBFheWhWm7WV/fQYfaCrauhFRzdk/SqCUi4 Tynw== X-Gm-Message-State: ALoCoQnbxsOy07qXfLfjtQ2zNGLYvs1tII0U41m/NDAidk2sIcCjjhr8o19hpHXvKv2p4Td+IYD1 MIME-Version: 1.0 X-Received: by 10.68.135.100 with SMTP id pr4mr16284040pbb.62.1381436328921; Thu, 10 Oct 2013 13:18:48 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 13:18:48 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 13:18:48 -0700 (PDT) In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> Date: Thu, 10 Oct 2013 13:18:48 -0700 Message-ID: Subject: Re: rcs From: Jos Backus To: Igor Mozolevsky Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 20:18:56 -0000 On Oct 10, 2013 1:07 PM, "Igor Mozolevsky" wrote: > > > > > On 10 October 2013 20:36, Jos Backus wrote: >> >> >> On Oct 10, 2013 11:54 AM, "Igor Mozolevsky" wrote: >> > >> > On 10 October 2013 19:15, Jos Backus wrote: >> >> >> >> On Oct 10, 2013 9:38 AM, "Julian Elischer" wrote: >> > >> > >> > [snip] >> > >> >> >> >> > well since people expect RCS.. it is not a no brainer. >> >> > you are asking people to learn a whole new tool for functionality that >> >> is currently very simple.. >> >> > edit file >> >> > ci -l file >> >> > add comment. >> >> >> >> Such is the price of progress. I envy people who don't have to learn >> >> anything new in order to stay employed :-) >> > >> > >> > So your definition of progress is "doing more work to achieve the same result"?.. >> >> That would only be true if they were equivalent, and we didn't care about the extra features. You may not, but many people do, as the popularity of git and other distributed version control systems proves. > > > You're missing the point- the requirement is "provide a way to keep track of changes for file X" not "have many fancy and unnecessary features"... That may have been the requirement at the time of the RCS import but the world has changed in my view. Feel free to use the old tools though, nobody is saying you can't. Anyway, why not change this for 11? Do we feel RCS is superior simply because we are familiar with it? What about all the extra features modern version control offers? Sounds like people think it's all a step backwards, all we need is manage separate files. No need for changesets or any other modern features. I don't really understand the resistance. We're okay with importing Subversion which has less functionally and more dependencies but a single Fossil binary is too intrusive? Jos > > -- > Igor M. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:34:11 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2D054A92 for ; Thu, 10 Oct 2013 20:34:11 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0162F2B11 for ; Thu, 10 Oct 2013 20:34:10 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id y10so3141798pdj.39 for ; Thu, 10 Oct 2013 13:34:10 -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=SyUmqFngNQP661X4cTinweO/ARN1H2itksRUIVfdTpQ=; b=F6dmP/gsposNfpYBBrtUB9UoSga5vL5eMQJZSPKGzSVcXVxrIHsxEkSc3uQ0eiJI3K EiQQsW332IrmjtRAMl2nLKZLWf3NnmiFfT4KQwRxpZPcaJcEl0jfowXeXIdUD0ip0g0W sYjInaCsURtQzFh7pnlrU/Yf7gntEOwmSv52KdB9cubrALtyV8sb5qGOE8QIX9GL13ET H6VP/R6KEJ3jN4DbbKCc/S4UNkeKLUziw5t/XnYYx6qR5BntE3mUw14ec3GOc+K715KP fX3yDbjdKjJw+y3iEkSxRJlhIsbq6QB131DMLmnPmTY5LzdfmVxlE/WG/Tp06+oBBKxu 2PGg== X-Gm-Message-State: ALoCoQkJ3v4JkH4zaeaISdUWUO8MsoYDJw6rkvlGsPcVBK8N+QgThz9baEtEUjY7EcnCrMPPApCs MIME-Version: 1.0 X-Received: by 10.66.216.129 with SMTP id oq1mr17939335pac.75.1381436890637; Thu, 10 Oct 2013 13:28:10 -0700 (PDT) Received: by 10.68.250.196 with HTTP; Thu, 10 Oct 2013 13:28:10 -0700 (PDT) X-Originating-IP: [93.221.173.86] In-Reply-To: <20131010185133.GA74598@night.db.net> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> <20131010185133.GA74598@night.db.net> Date: Thu, 10 Oct 2013 22:28:10 +0200 Message-ID: Subject: Re: rcs From: "C. P. Ghost" To: Diane Bruce Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: George Mitchell , FreeBSD-Current , Kimmo Paasiala X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 20:34:11 -0000 On Thu, Oct 10, 2013 at 8:51 PM, Diane Bruce wrote: > ... > > >>>> OK, but please, can we replace RCS with Fossil in 11 then? That > adds a > > real > > >>>> improvement to FreeBSD while giving people plenty of time to > prepare. > > Fossil was showing promise the last time I tried it. Quite frankly > > > > well since people expect RCS.. it is not a no brainer. > > > you are asking people to learn a whole new tool for functionality > that > > is currently very simple.. > > > edit file > > > ci -l file > > > add comment. > > pfft as long as any SCS can read my old rcs files this old fart does > not mind. > Same here. Don't care about the tool, as long as it can provide backward compatibility to the RCS format, and provides the familiar command interface (ci, co, ...) somehow. -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:35:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 34011C03 for ; Thu, 10 Oct 2013 20:35:38 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D1E5F2B2E for ; Thu, 10 Oct 2013 20:35:37 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.7/8.14.7) with ESMTP id r9AKZYPK011260 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 10 Oct 2013 13:35:35 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs From: Lyndon Nerenberg In-Reply-To: Date: Thu, 10 Oct 2013 13:35:33 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <97203F19-A5F5-40A9-9DEE-C73C8C9F51CB@orthanc.ca> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> To: "freebsd-current@freebsd.org" X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 20:35:38 -0000 On 2013-10-10, at 1:06 PM, Igor Mozolevsky = wrote: > You're missing the point- the requirement is "provide a way to keep = track > of changes for file X" not "have many fancy and unnecessary = features"... The point is to put back the specific RCS commands that were recently = removed. Those of us using RCS do so because it's in the base system. If we = wanted/needed another SCM, we would install it from ports. But many of = us use RCS specifically because installing a port is not an option. = *Why* it's not an option is not relevant. RCS is not broken, and is very low maintenance code. = /usr/src/gnu/usr.bin/rcs has been modified four times in the last = decade. Two of those changes were sweeping Makefile updates that = affected much more than RCS. Of the other two, only one update touched = the actual code, and that was a one line change to a .h. --lyndon From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:35:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5A021D0C; Thu, 10 Oct 2013 20:35:47 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0EEA12B34; Thu, 10 Oct 2013 20:35:46 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.90,1075,1371099600"; d="scan'208";a="56428308" Message-ID: <52570F9E.2080402@vangyzen.net> Date: Thu, 10 Oct 2013 15:35:42 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: Subject: Re: make universe fails, apparently in lib/clang/include (all) References: <5256D9A1.6050605@dell.com> <3AB373DA-55AB-4D93-A1C5-36701C757A45@FreeBSD.org> In-Reply-To: <3AB373DA-55AB-4D93-A1C5-36701C757A45@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Eric van Gyzen , Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 20:35:47 -0000 On 10/10/2013 14:02, Dimitry Andric wrote: > On Oct 10, 2013, at 18:45, Eric van Gyzen wrote: >> "make universe" is consistently failing in the following way. >> "_.amd64.amd64.buildworld" contains: >> >> ======== >> >> ===> lib/clang/libllvmx86desc (all) >> ===> lib/clang/libllvmx86disassembler (all) >> ===> lib/clang/libllvmx86info (all) >> ===> lib/clang/libllvmx86instprinter (all) >> ===> lib/clang/libllvmx86utils (all) >> ===> lib/clang/include (all) >> 1 error >> >> make[3]: stopped in /home/freebsd >> *** [everything] Error code 2 > Hi Eric, > > Can you please upload the full _.amd64.amd64.buildworld file somewhere? > The actual error will have occurred earlier in the build, and it is not > directly visible in the last few lines. http://www.vangyzen.net/FreeBSD/tmp/_.amd64.amd64.buildworld.xz Now I see the error around line 114311. Any ideas? I failed to mention, /etc/make.conf only has a PERL_VERSION, and I have no /etc/src.conf. Eric From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:43:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 69B7C10D; Thu, 10 Oct 2013 20:43:07 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3B74A2BDD; Thu, 10 Oct 2013 20:43:07 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 142517D54; Thu, 10 Oct 2013 20:43:05 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 142517D54 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 10 Oct 2013 16:43:04 -0400 From: Glen Barber To: Lyndon Nerenberg Subject: Re: rcs Message-ID: <20131010204304.GX44375@glenbarber.us> References: <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> <97203F19-A5F5-40A9-9DEE-C73C8C9F51CB@orthanc.ca> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="BtNCO5h84ExDStzY" Content-Disposition: inline In-Reply-To: <97203F19-A5F5-40A9-9DEE-C73C8C9F51CB@orthanc.ca> X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 20:43:07 -0000 --BtNCO5h84ExDStzY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 10, 2013 at 01:35:33PM -0700, Lyndon Nerenberg wrote: >=20 > On 2013-10-10, at 1:06 PM, Igor Mozolevsky wrote: >=20 > > You're missing the point- the requirement is "provide a way to keep tra= ck > > of changes for file X" not "have many fancy and unnecessary features"... >=20 > The point is to put back the specific RCS commands that were recently rem= oved. >=20 http://lists.freebsd.org/pipermail/svn-src-head/2013-October/052106.html Glen --BtNCO5h84ExDStzY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSVxFYAAoJELls3eqvi17QVoEP/0rae5LvJMBQcNkvH85A4ZpR D5jBXrRY2Rfy3v74DE9Dr5iFvR2h//nr+16OKFpHRMnR0RYzSqjPL4fzF/KZWFue 41dUiFHuoyxiL+T52vvqCwMd02YV058U+7VOP05s/ujHTZ1R08vEKsSuFz6GdO3s Nh/oNbq1MCehnUozLn9yPaAjgHZj4LXXRnUjMouRdFRcTa5NU3aXZv9UgkJ3C05D qU5RUV6qUaHgnD6oMtI4O+lXgqElPmLWYw73hrKYm6hWxVjbJh7ZpKAaoKLTT+EE NK0yb2VwkH4k2O8K/fRxE6pGM0IBl9Qn/K6FHYxUlEiR4OA8xNTWVsVOHj660RWd y9UsvCsqDDD6PsaLDfgv10FdtVsU8JAlM+upNen12mIZjFlY6ZzPEc9N0fhMY8oa RafvJfLgtBZcY7xel76mzSzroJmmywiz18/iZl5QkgER6+tnexqTz9Z5ckrKuj3f ELGQNUHG7bZ0ZPY3iPh9KdM8nKkT/Tjb/dMeof1p0hOynxSy4QeN3as/AVQM/bYs JXVecrfP85LsDwr0IKV9D45a/lwCbBr+VN+bG8fMAqN5nL3DIIphH+vgQ0nBbj48 V6RFNneEezBJ7clzhhyE5Jbbcw1B1N/4imHDHzZQWOcRqoIpCgPWtdbthX5+m1Al RElC7DMXXfAs+7nCRfjj =XVB/ -----END PGP SIGNATURE----- --BtNCO5h84ExDStzY-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 21:13:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B0571FB8; Thu, 10 Oct 2013 21:13:02 +0000 (UTC) (envelope-from universite@ukr.net) Received: from otrada.od.ua (universite-1-pt.tunnel.tserv24.sto1.ipv6.he.net [IPv6:2001:470:27:140::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2129A2E5A; Thu, 10 Oct 2013 21:13:01 +0000 (UTC) Received: from [10.0.0.10] ([10.0.0.10]) (authenticated bits=0) by otrada.od.ua (8.14.4/8.14.5) with ESMTP id r9ALCsMB057126; Fri, 11 Oct 2013 00:12:55 +0300 (EEST) (envelope-from universite@ukr.net) Message-ID: <52571856.1020302@ukr.net> Date: Fri, 11 Oct 2013 00:12:54 +0300 From: "Vladislav V. Prodan" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Prompt Live-CD/DVD with support for ZFS v.5000 References: <524DF430.1040504@ukr.net> <20131004135655.GA89251@roberto02-aw.eurocontrol.fr> In-Reply-To: <20131004135655.GA89251@roberto02-aw.eurocontrol.fr> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (otrada.od.ua [89.209.81.54]); Fri, 11 Oct 2013 00:12:55 +0300 (EEST) X-Spam-Status: No, score=-101.0 required=5.0 tests=ALL_TRUSTED, FREEMAIL_FROM, T_TO_NO_BRKTS_FREEMAIL, USER_IN_WHITELIST autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mary-teresa.otrada.od.ua Cc: Martin Matuska X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 21:13:02 -0000 04.10.2013 16:56, Ollivier Robert wrote: > According to Vladislav V. Prodan on Fri, Oct 04, 2013 at 01:48:16AM +0300: >> You want to add such a liveCD for automatic loading on PXE. >> MfsBSD built with ZFS v.28 :( > > mfsbsd will be updated soon I guess but in the meantime it is very easy to generate your own. Just get the code from github, modify a few config files if needed and make. > Thanks. In the latest build no libiconv.so.3 root@mfsbsd:/tmp/oldpool/var/db/mysql # rsync -a /tmp/oldpool/var/db/mysql/ /tmp/newpool/var/db/mysql/ Shared object "libiconv.so.3" not found, required by "rsync" -- Vladislav V. Prodan System & Network Administrator http://support.od.ua +380 67 4584408, +380 99 4060508 VVP88-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 21:20:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 96C203C0; Thu, 10 Oct 2013 21:20:03 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qe0-x22f.google.com (mail-qe0-x22f.google.com [IPv6:2607:f8b0:400d:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 408B62EB5; Thu, 10 Oct 2013 21:20:03 +0000 (UTC) Received: by mail-qe0-f47.google.com with SMTP id b4so2537312qen.20 for ; Thu, 10 Oct 2013 14:20:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=OUzJmFiItqR749sJm2G1DSoF/VdM1lkgziwOHki+4tw=; b=VUkZJh4azV5YRaqqs2QZxENTNMz6WieZw0Dwalb/96m+7rxnel+q4hzeS/wrq8Znq8 TqLwfdYGqmudIuTKuGIB3tuZuHAFeqoWuPXlrW2mzJz8UFdlGHk/ffcPxWeOyGoy/i7g j1Igc9Z/A1SASbRpAgOOC5wplFq1G1/pFSGnkzHN4LxGFrG32Co/2kxzEOqC8kbPNy8+ 18+nuZjPJHxKqVOa7K91OZNsgrfXegxjG16SlZjDyLo+qQrLodmHE5nrFIRTH1UWdpls 2a3HcjjMJuhl8f5YYMCowgSr/GHaPmToaJYvvcYQgHrOR55HUz1XWCbdgSsJBpRbCwv6 /wjw== X-Received: by 10.49.104.5 with SMTP id ga5mr3743605qeb.53.1381440002458; Thu, 10 Oct 2013 14:20:02 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Thu, 10 Oct 2013 14:19:22 -0700 (PDT) In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> From: Igor Mozolevsky Date: Thu, 10 Oct 2013 22:19:22 +0100 X-Google-Sender-Auth: 1n7oKK6AWi3gWrA_8cUvmFuxYq0 Message-ID: Subject: Re: rcs To: Jos Backus Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 21:20:03 -0000 On 10 October 2013 21:18, Jos Backus wrote: > > On Oct 10, 2013 1:07 PM, "Igor Mozolevsky" wrote: > > > [snip] > > You're missing the point- the requirement is "provide a way to keep > track of changes for file X" not "have many fancy and unnecessary > features"... > > That may have been the requirement at the time of the RCS import but the > world has changed in my view. Feel free to use the old tools though, nobody > is saying you can't. > > Anyway, why not change this for 11? Do we feel RCS is superior simply > because we are familiar with it? What about all the extra features modern > version control offers? Sounds like people think it's all a step backwards, > all we need is manage separate files. No need for changesets or any other > modern features. > RCS is a tool that does it's job. It's been in base since time immemoriam, and is more likely than not to be found in other flavours of Unix(TM). Moreover, RCS commands are integrated into a lot of scripts that sysadmins use (it'd be naive to think otherwise), so in terms of $$$ not having RCS in base (yup, I know the change's been reverted) has a real cost to business! I don't really understand the resistance. We're okay with importing > Subversion which has less functionally and more dependencies but a single > Fossil binary is too intrusive? > SVN is the necessary evil, the project uses it and until the project switches to something else we're "stuck with it". What's the case for Fossil?.. -- Igor M. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 21:25:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3DAD46FF for ; Thu, 10 Oct 2013 21:25:36 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 18C142F20 for ; Thu, 10 Oct 2013 21:25:35 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id B1F0821DCA for ; Thu, 10 Oct 2013 21:25:34 +0000 (UTC) Message-ID: <52571B63.5050403@allanjude.com> Date: Thu, 10 Oct 2013 17:25:55 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Prompt Live-CD/DVD with support for ZFS v.5000 References: <524DF430.1040504@ukr.net> <20131004135655.GA89251@roberto02-aw.eurocontrol.fr> <52571856.1020302@ukr.net> In-Reply-To: <52571856.1020302@ukr.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 21:25:36 -0000 On 2013-10-10 17:12, Vladislav V. Prodan wrote: > 04.10.2013 16:56, Ollivier Robert wrote: >> According to Vladislav V. Prodan on Fri, Oct 04, 2013 at 01:48:16AM +0300: >>> You want to add such a liveCD for automatic loading on PXE. >>> MfsBSD built with ZFS v.28 :( >> mfsbsd will be updated soon I guess but in the meantime it is very easy to generate your own. Just get the code from github, modify a few config files if needed and make. >> > Thanks. > > In the latest build no libiconv.so.3 > > root@mfsbsd:/tmp/oldpool/var/db/mysql # rsync -a > /tmp/oldpool/var/db/mysql/ /tmp/newpool/var/db/mysql/ > Shared object "libiconv.so.3" not found, required by "rsync" > > > > First time seeing this thread, but Devin Teske and I have just finished integrated support for root-on-zfs installs in bsdinstall, should land in head today -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 19:51:56 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2646BF5F for ; Thu, 10 Oct 2013 19:51:56 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: from mail-bk0-x22d.google.com (mail-bk0-x22d.google.com [IPv6:2a00:1450:4008:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B31322801 for ; Thu, 10 Oct 2013 19:51:55 +0000 (UTC) Received: by mail-bk0-f45.google.com with SMTP id mx11so1176302bkb.18 for ; Thu, 10 Oct 2013 12:51:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; bh=u2Rf5LiDnwGKMDpEfaguuN5BwATQMaDYvUxEWWPnufo=; b=ZCy2I3tF66Phc1xsdpBFhOh9XSY2cjKvBW9Es8WIpvQLiFSlCIIBf8CT1QcaQu5SM4 QM9gvz0OrKSyGa3KySltpzfxRHGRiDzW6OiETEWaE2eu5Gic1wZZPDwn0vBGDd5o6K10 YRzc4JDxw1Za+gn/nP5g55Z8ahdv7iSa3qAKPNDvXmGxI4wncYO2vYHFLxVK9ZgIdkee Qf2UPbqL7+tI0VCkrra72PtlVllk6z+oeLlii3XIiIxrYCMEKinn0Nm4+21DzMnBLiJw zCAVpR4bFmev77xwIqrHwnnXFFdFvWxOzyVqW8+r4KDHau8xJLrLL/Lx+HIpSU69k/ki IUBA== X-Received: by 10.204.123.199 with SMTP id q7mr14444559bkr.10.1381434713964; Thu, 10 Oct 2013 12:51:53 -0700 (PDT) Received: from ubm.strangled.net (g230221219.adsl.alicedsl.de. [92.230.221.219]) by mx.google.com with ESMTPSA id jt14sm28268498bkb.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 12:51:52 -0700 (PDT) Date: Thu, 10 Oct 2013 21:51:48 +0200 From: Marc UBM To: current@freebsd.org Subject: /usr/local/lib /usr/bin/ld: =?ISO-8859-1?Q?=F8:?= invalid DSO for symbol Message-Id: <20131010215148.6d4e724952052b8833133264@gmail.com> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 10 Oct 2013 21:28:11 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 19:51:56 -0000 Hiho! :-) Trying to compile several ports in the wake of the recent iconv change yields the following error that I could not get rid of yet: ---- libtool: link: cc -O2 -pipe -fno-strict-aliasing -Wall -I/usr/local/include -Wl,-rpath=3D/usr/local/lib -Wl,-rpath=3D/usr/local/lib -o irssi gui-entry.o gui-expandos.o gui-printtext.o gui-readline.o gui-windows.o lastlog.o mainwindows.o mainwindow-activity.o mainwindows-layout.o statusbar.o statusbar-config.o statusbar-items.o term.o term-dummy.o tparm.o term-terminfo.o terminfo-core.o textbuffer.o textbuffer-commands.o textbuffer-view.o irssi.o module-formats.o -Wl,-R/usr/local/lib/perl5/5.14/mach/CORE -pthread -Wl,-E -fstack-protector -Wl,--export-dynamic -pthread -Wl,--export-dynamic ../fe-common/irc/libfe_common_irc.a ../fe-common/irc/= dcc/libfe_irc_dcc.a ../fe-common/irc/notifylist/libfe_irc_notifylist.a ../f= e-common/core/libfe_common_core.a ../irc/libirc.a ../irc/core/libirc_core.a= ../irc/dcc/libirc_dcc.a ../irc/flood/libirc_flood.a ../irc/notifylist/libi= rc_notifylist.a ../core/libcore.a ../lib-config/libirssi_config.a ../perl/.= libs/libperl_core_static.a ../perl/.libs/libfe_perl_static.a -L/usr/local/lib -L/usr/local/lib/perl5/5.14/mach/CORE -lperl -lm -lcrypt -lutil /usr/local/lib/libgmodule-2.0.so /usr/local/lib/libglib-2.0.so /usr/= local/lib/libpcre.so /usr/local/lib/libintl.so -lssl -lcrypto -lncurses -pthread -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib /usr/bin/ld: =F8: invalid DSO for symbol `tgetnum' definition /usr/local/lib/libtinfo.so.5.9: could not read symbols: Bad value ---- Any ideas how to solve that one / if I am doing something wrong? Bye Marc --=20 Marc "UBM" Bocklet From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 21:39:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 802A2C99; Thu, 10 Oct 2013 21:39:15 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3BB442010; Thu, 10 Oct 2013 21:39:15 +0000 (UTC) Received: by mail-ob0-f176.google.com with SMTP id wo20so2152373obc.21 for ; Thu, 10 Oct 2013 14:39: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; bh=T9IVkDerlDyuNrvOXkCQmPq76joPVkzHNMNUt6xQ9uo=; b=VVI4F8UZj2G3PK0u2wjETDZqN1mB7OOFIdxb14oPKyTNK4fwk7A+K5lGqwdXdTR+oG XsdXoDrmsAY26BxnUfCDIvxn+Jg3frK3Q9lu1MJGD3fHLwjtOEstxcc/1iEJZLmG7lyG l5ZbreW/UXhr5GU1uL5Lr4uKr+S2Daragk/nnTCMdYKd0J4F3G6RPiThKqWsYY1mJHiO /3yo+u4ixVH3j4PT86rT7lyPnAAK/Rj2TvNMorrEK16KZpprtb3dfLWKsHJUbcW6TYG3 AijQVOaCOMvlLOd3FbHX5ffxmtRlrizwApsytqMoPQJoow40taA9P27yB9NwXLEwrve8 kuYA== MIME-Version: 1.0 X-Received: by 10.182.34.194 with SMTP id b2mr7182323obj.41.1381441154522; Thu, 10 Oct 2013 14:39:14 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Thu, 10 Oct 2013 14:39:14 -0700 (PDT) In-Reply-To: References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> <5256E2D5.4060101@allanjude.com> Date: Thu, 10 Oct 2013 17:39:14 -0400 Message-ID: Subject: Re: FreeBSD 10 and zfsd From: Outback Dingo To: Alan Somers Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 21:39:15 -0000 On Thu, Oct 10, 2013 at 1:26 PM, Alan Somers wrote: > On Thu, Oct 10, 2013 at 11:24 AM, Allan Jude > wrote: > > On 2013-10-10 12:13, Mark Felder wrote: > >> On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: > >>> On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks < > joh.hendriks@gmail.com> > >>> wrote: > >>>> When i started using ZFS on FreeBSD I quickly found out that hot > spares are > >>>> not possible on FreeBSD. > >>>> I was told that with zfsd it should be possible and that it would be > >>>> included in FreeBSD 10. > >>>> > >>>> Is there some info about the zfsd function and how it could be used? > >>> zfsd is currently not in FreeBSD/head and won't make it into 10, but > >>> you can still get the source code from its project branch. It's being > >>> used in production by at least two companies. > >>> > >> So FreeBSD is going to have inferior ZFS management compared to > >> Solaris/Illumos/etc for another 2+ years? Why are things like this > >> allowed to miss releases? > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev summit (3 > > weeks ago). There is a lot of collaboration going on, to bring in some > > work done by vendors like SpectraLogics. This is the type of feature > > that can be assed in 10.1, it won't have to wait for 11. > > > > You can see Robert Watsons talk "How FreeBSD Works" to see why releases > > are based on date, rather than on feature completion (because things are > > never "finished") > > > > > > > > -- > > Allan Jude > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > Due to popular demand, I have located a round toit. I'm currently > working on rebasing the zfsd project branch to head, after which I'll > push SpectraLogic's recent changes. > Sweeeeeet....... something to play with the next few days and see how stable it is. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 21:41:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 200F4E11 for ; Thu, 10 Oct 2013 21:41:18 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B08722070 for ; Thu, 10 Oct 2013 21:41:17 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hn3so150482wib.17 for ; Thu, 10 Oct 2013 14:41:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=jDIjbX0U1PFWiDqagb7Vjy3rbD4kNhlbjVrEYMQlOYI=; b=BxxNYQ5MXx+ufFjUIrpt67wA1bNOvWy1dgb3YQ/gCg1b/vqMvY5pZXeYecOlJ1UCW5 C51Q/2L0G0cpOVpnORgHo+GxHcgIXi4eL/aS73AqxxdWdm3zzVj9CJhqT3iO6zkojX2n 3pvTpyjmc3JpGnhbPBPOKARsW2qTwnvgqmc9snJ/IzxUqmHsn3Oxwq2OQIXgdqiJXHY/ aF+/YPz4VAO9PIsUTDHLNAwKMncx8pV7dFihm6Gh+S/Pog6sZFPiHcQ7x/z6uNBlIO23 avEJPKrTQuqlvQxM2jsBXybLhyP1guFav1aWazVx975orl6ylC1sqmIlUvoclTp12KIu t1Ug== X-Received: by 10.194.63.228 with SMTP id j4mr14088739wjs.34.1381441276001; Thu, 10 Oct 2013 14:41:16 -0700 (PDT) Received: from [192.168.1.5] (a89-152-175-125.cpe.netcabo.pt. [89.152.175.125]) by mx.google.com with ESMTPSA id e1sm29299857wij.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 14:41:15 -0700 (PDT) Message-ID: <52571EF6.8010703@gmail.com> Date: Thu, 10 Oct 2013 22:41:10 +0100 From: "Mike C." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current Subject: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2 X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 21:41:18 -0000 Hi, I'm running Alpha-2 and wanted to test with iscsi but it seems I can't start iscsid. $ sudo service iscsid onerestart kldload: can't load iscsi: Exec format error /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid dmesg shows: interface icl.1 already present in the KLD 'kernel'! linker_load_file: Unsupported file type And also it seems that iscsi is actually already loaded: sudo kldstat -v | grep isci 470 pci/isci Any help is appreciated. -- Melhores Cumprimentos // Best Regards ------------------------------------------------------------------------ Miguel Clara *nix Sys Admin Freelance From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 21:50:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A4F812D3 for ; Thu, 10 Oct 2013 21:50:15 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 81E04210E for ; Thu, 10 Oct 2013 21:50:15 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 4BE3421EDB for ; Thu, 10 Oct 2013 21:50:11 +0000 (UTC) Message-ID: <52572129.8020007@allanjude.com> Date: Thu, 10 Oct 2013 17:50:33 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2 References: <52571EF6.8010703@gmail.com> In-Reply-To: <52571EF6.8010703@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 21:50:15 -0000 On 2013-10-10 17:41, Mike C. wrote: > Hi, > > I'm running Alpha-2 and wanted to test with iscsi but it seems I can't > start iscsid. > > > $ sudo service iscsid onerestart > kldload: can't load iscsi: Exec format error > /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi > /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid > > > dmesg shows: > interface icl.1 already present in the KLD 'kernel'! > linker_load_file: Unsupported file type > > > And also it seems that iscsi is actually already loaded: > > sudo kldstat -v | grep isci > 470 pci/isci > > > Any help is appreciated. > > > isci is the intel SAS driver, not iscsi (confusing name) The problem appears to be that the iscsi module you have is not the same version as your kernel, try updating to ALPHA5 -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 21:54:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E1C5A4C6 for ; Thu, 10 Oct 2013 21:54:06 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 9F4EF213D for ; Thu, 10 Oct 2013 21:54:06 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 65B3E21EF8 for ; Thu, 10 Oct 2013 21:54:05 +0000 (UTC) Message-ID: <52572213.2050307@allanjude.com> Date: Thu, 10 Oct 2013 17:54:27 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: FreeBSD 10 and zfsd References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> <5256E2D5.4060101@allanjude.com> <5256E680.4000008@allanjude.com> <1381430466.14387.32509497.13949CED@webmail.messagingengine.com> <20131010215949.3214f4c2@thor.walstatt.dyndns.org> In-Reply-To: <20131010215949.3214f4c2@thor.walstatt.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 21:54:07 -0000 On 2013-10-10 15:59, O. Hartmann wrote: > On Thu, 10 Oct 2013 13:41:06 -0500 > Mark Felder wrote: > >> >> On Thu, Oct 10, 2013, at 12:40, Allan Jude wrote: >>> On 2013-10-10 13:26, Alan Somers wrote: >>>> On Thu, Oct 10, 2013 at 11:24 AM, Allan Jude >>>> wrote: >>>>> On 2013-10-10 12:13, Mark Felder wrote: >>>>>> On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote: >>>>>>> On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks >>>>>>> wrote: >>>>>>>> When i started using ZFS on FreeBSD I quickly found out that >>>>>>>> hot spares are not possible on FreeBSD. >>>>>>>> I was told that with zfsd it should be possible and that it >>>>>>>> would be included in FreeBSD 10. >>>>>>>> >>>>>>>> Is there some info about the zfsd function and how it could >>>>>>>> be used? >>>>>>> zfsd is currently not in FreeBSD/head and won't make it into >>>>>>> 10, but you can still get the source code from its project >>>>>>> branch. It's being used in production by at least two >>>>>>> companies. >>>>>>> >>>>>> So FreeBSD is going to have inferior ZFS management compared to >>>>>> Solaris/Illumos/etc for another 2+ years? Why are things like >>>>>> this allowed to miss releases? >>>>>> _______________________________________________ >>>>>> freebsd-current@freebsd.org mailing list >>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>>> To unsubscribe, send any mail to >>>>>> "freebsd-current-unsubscribe@freebsd.org" >>>>> ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev >>>>> summit (3 weeks ago). There is a lot of collaboration going on, >>>>> to bring in some work done by vendors like SpectraLogics. This >>>>> is the type of feature that can be assed in 10.1, it won't have >>>>> to wait for 11. >>>>> >>>>> You can see Robert Watsons talk "How FreeBSD Works" to see why >>>>> releases are based on date, rather than on feature completion >>>>> (because things are never "finished") >>>>> >>>>> >>>>> >>>>> -- >>>>> Allan Jude >>>>> >>>>> _______________________________________________ >>>>> freebsd-current@freebsd.org mailing list >>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>>> To unsubscribe, send any mail to >>>>> "freebsd-current-unsubscribe@freebsd.org" >>>> Due to popular demand, I have located a round toit. I'm currently >>>> working on rebasing the zfsd project branch to head, after which >>>> I'll push SpectraLogic's recent changes. >>> See, all you have to do is complain loudly enough :p >>> >> I was sad more than anything. I'd been waiting for zfsd since the >> project was announced. :-) I'm glad to know we won't have to wait >> until 11.0. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" > Ha! > > Very funny. I created a RAIDZ1 pool and by reading the man page for > zpool, which states precisely how to create a hot spare for a given > pool. I wasn't aware until now that this action was useless, and even > dangerous. Well, bravo, I must admit, the man page does not give any > kind of warning that one can not rely on a hot spare. > > oh The ZFS spare functinality basically just marks the drive as a spare, so you as the admin know what drive to use when replacement time comes I've been working on the handbook section on ZFS and made certain to mention that, I'll have to look at improving the man page as well, but as far as I know, the man page is imported from IllumOS, where spares do work. ZFSd is important and I hope to see more movement on it soon. -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 21:59:11 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2A5CA76D for ; Thu, 10 Oct 2013 21:59:11 +0000 (UTC) (envelope-from agh@fastmail.fm) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EEBCC217B for ; Thu, 10 Oct 2013 21:59:10 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1399821D85; Thu, 10 Oct 2013 17:59:04 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 10 Oct 2013 17:59:04 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:content-transfer-encoding:in-reply-to; s=mesmtp; bh=pdUGOuak5OIqqmG2n06OoYBIJs8=; b=Gsj5NOaGXCDahLGmAbqOu04fs00F eDakmrdvBUToDSMGgKWsK6iyPlmK2O34KmTA+/RWc4/bAkA/2v//ByWjsD24dp2R Aztdt56YlTEB2/3STQEypKlbFCSTZPcCsXeCzhqfk3NkhUyEOMenqBsXDaeZV5ln tCTMw4uJv7GBy7I= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:content-transfer-encoding :in-reply-to; s=smtpout; bh=pdUGOuak5OIqqmG2n06OoYBIJs8=; b=oAAg rqh3+6G3Pz/XPFMMuzNHB5BheKj/+0WaYatplGlu4Uc8vExV0nFwHhB/2ldF8X0q p9AjSI6mJowcpU6/0nhf71FnftMvGoohvQmkChQL2rISUPoM78BHe3brOP0zL8PH nCFu/XpZ2JatT1vmxwP/+drBI5NSLtDvF4zm2Oo= X-Sasl-enc: MDOKarVWg/Gfl6Rnsvd5/WKGZQRq8BfOtPLH3knfH6Uk 1381442343 Received: from direwolf.aux.io (unknown [203.59.221.16]) by mail.messagingengine.com (Postfix) with ESMTPA id 9545C6800BF; Thu, 10 Oct 2013 17:59:02 -0400 (EDT) Date: Fri, 11 Oct 2013 05:58:56 +0800 From: Alastair Hogge To: Marc UBM Subject: Re: /usr/local/lib =?iso-8859-1?B?L3Vzci9i?= =?iso-8859-1?B?aW4vbGQ6IPg6?= invalid DSO for symbol Message-ID: <20131010215855.GA90129@direwolf.aux.io> References: <20131010215148.6d4e724952052b8833133264@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20131010215148.6d4e724952052b8833133264@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 21:59:11 -0000 On 2013-10-10 Thu 21:51:48 +0200, Marc UBM wrote: > > Hiho! :-) Hi > Trying to compile several ports in the wake of the recent iconv change > yields the following error that I could not get rid of yet: > > ---- > libtool: link: cc -O2 -pipe -fno-strict-aliasing -Wall > -I/usr/local/include -Wl,-rpath=/usr/local/lib > -Wl,-rpath=/usr/local/lib -o irssi gui-entry.o gui-expandos.o > gui-printtext.o gui-readline.o gui-windows.o lastlog.o mainwindows.o > mainwindow-activity.o mainwindows-layout.o statusbar.o > statusbar-config.o statusbar-items.o term.o term-dummy.o tparm.o > term-terminfo.o terminfo-core.o textbuffer.o textbuffer-commands.o > textbuffer-view.o irssi.o module-formats.o > -Wl,-R/usr/local/lib/perl5/5.14/mach/CORE -pthread -Wl,-E > -fstack-protector -Wl,--export-dynamic -pthread > -Wl,--export-dynamic ../fe-common/irc/libfe_common_irc.a ../fe-common/irc/dcc/libfe_irc_dcc.a ../fe-common/irc/notifylist/libfe_irc_notifylist.a ../fe-common/core/libfe_common_core.a ../irc/libirc.a ../irc/core/libirc_core.a ../irc/dcc/libirc_dcc.a ../irc/flood/libirc_flood.a ../irc/notifylist/libirc_notifylist.a ../core/libcore.a ../lib-config/libirssi_config.a ../perl/.libs/libperl_core_static.a ../perl/.libs/libfe_perl_static.a > -L/usr/local/lib -L/usr/local/lib/perl5/5.14/mach/CORE -lperl -lm > -lcrypt > -lutil /usr/local/lib/libgmodule-2.0.so /usr/local/lib/libglib-2.0.so /usr/local/lib/libpcre.so /usr/local/lib/libintl.so > -lssl -lcrypto -lncurses -pthread -Wl,-rpath -Wl,/usr/local/lib > -Wl,-rpath -Wl,/usr/local/lib /usr/bin/ld: ř: invalid DSO for symbol > `tgetnum' definition /usr/local/lib/libtinfo.so.5.9: could not read > symbols: Bad value > ---- > > > Any ideas how to solve that one / if I am doing something wrong? Add the following to the offending ports' Makefile (I am upto 6): LDFLAGS+= -ltinfow > Bye > Marc Salud alastair -- Imagine there's no heaven... it's easy if you try. -- John Lennon, "Imagine" From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 22:17:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 78A2BEF7 for ; Thu, 10 Oct 2013 22:17:15 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:150:6101::4]) by mx1.freebsd.org (Postfix) with ESMTP id 39C0222B7 for ; Thu, 10 Oct 2013 22:17:15 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.2]) by mail.vx.sk (Postfix) with ESMTP id D08A7423EB; Fri, 11 Oct 2013 00:17:13 +0200 (CEST) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk by core.vx.sk (amavisd-new, unix socket) with LMTP id WD9ao-xk5XX8; Fri, 11 Oct 2013 00:17:12 +0200 (CEST) Received: from [192.168.2.108] (dslb-092-078-050-209.pools.arcor-ip.net [92.78.50.209]) by mail.vx.sk (Postfix) with ESMTPSA id 49798423DF; Fri, 11 Oct 2013 00:17:12 +0200 (CEST) Message-ID: <52572767.9080409@FreeBSD.org> Date: Fri, 11 Oct 2013 00:17:11 +0200 From: Martin Matuska User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "Vladislav V. Prodan" , freebsd-current@freebsd.org Subject: Re: Prompt Live-CD/DVD with support for ZFS v.5000 References: <524DF430.1040504@ukr.net> <20131004135655.GA89251@roberto02-aw.eurocontrol.fr> <52571856.1020302@ukr.net> In-Reply-To: <52571856.1020302@ukr.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 22:17:15 -0000 I have updated the amd64 images with rsync without iconv linking. Please re-download. On 2013-10-10 23:12, Vladislav V. Prodan wrote: > 04.10.2013 16:56, Ollivier Robert wrote: >> According to Vladislav V. Prodan on Fri, Oct 04, 2013 at 01:48:16AM +0300: >>> You want to add such a liveCD for automatic loading on PXE. >>> MfsBSD built with ZFS v.28 :( >> mfsbsd will be updated soon I guess but in the meantime it is very easy to generate your own. Just get the code from github, modify a few config files if needed and make. >> > Thanks. > > In the latest build no libiconv.so.3 > > root@mfsbsd:/tmp/oldpool/var/db/mysql # rsync -a > /tmp/oldpool/var/db/mysql/ /tmp/newpool/var/db/mysql/ > Shared object "libiconv.so.3" not found, required by "rsync" From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 22:22:32 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9004027C for ; Thu, 10 Oct 2013 22:22:32 +0000 (UTC) (envelope-from jos@catnook.com) Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 608902330 for ; Thu, 10 Oct 2013 22:22:32 +0000 (UTC) Received: by mail-pa0-f46.google.com with SMTP id fa1so3418266pad.19 for ; Thu, 10 Oct 2013 15:22:26 -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=wH0+UZXxT3fm/tGKKqDXzcjODWma1xMwMavtdhEwIOs=; b=cAIn7HUoDbSURfXuZjCm/dmGXZ0y4nKkMOG+YHH+WqClZ8ZdrzxY7HY/C8QHrvjnfE sFw9yw9mPyKk2iQvGZpS8mjkzpUXpwUVhg5woLRdfdlmn+KAnoVQZmCRBmTgdSX9kRWG 79kTOMJyWRA7Q88Hml4Bre9kw5oGTyyoBHHvY7J9GRxXM7G1wHb5LF+c8eHgHvSOVyXx cVjP5qF6+J8ZCsMi6Y+VXxaSxlG1ioYxztZnwGi3G+oy9AE2iAG206LFW9UI4LSzVzJi JoSeQRuW1Yef9a9p7FI5DJqwF3x+JUrs336OZwbBaheQG7dR36T3DNx10iSYrPISMo0E ZJzg== X-Gm-Message-State: ALoCoQlpM15Z7F1RHNL90kYZFTd+p+OaDCxewwQlPhgQ9/E3yt1EjhHCn7jYtAramtQgP96U+QRn MIME-Version: 1.0 X-Received: by 10.68.232.74 with SMTP id tm10mr16632996pbc.64.1381443746315; Thu, 10 Oct 2013 15:22:26 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 15:22:26 -0700 (PDT) Received: by 10.70.49.36 with HTTP; Thu, 10 Oct 2013 15:22:26 -0700 (PDT) In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> Date: Thu, 10 Oct 2013 15:22:26 -0700 Message-ID: Subject: Re: rcs From: Jos Backus To: Igor Mozolevsky Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kimmo Paasiala , George Mitchell , freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 22:22:32 -0000 On Oct 10, 2013 2:20 PM, "Igor Mozolevsky" wrote: > > > > > On 10 October 2013 21:18, Jos Backus wrote: >> >> >> On Oct 10, 2013 1:07 PM, "Igor Mozolevsky" wrote: >> > > > [snip] >> >> > You're missing the point- the requirement is "provide a way to keep track of changes for file X" not "have many fancy and unnecessary features"... >> >> That may have been the requirement at the time of the RCS import but the world has changed in my view. Feel free to use the old tools though, nobody is saying you can't. >> >> Anyway, why not change this for 11? Do we feel RCS is superior simply because we are familiar with it? What about all the extra features modern version control offers? Sounds like people think it's all a step backwards, all we need is manage separate files. No need for changesets or any other modern features. > > > RCS is a tool that does it's job. It's been in base since time immemoriam, and is more likely than not to be found in other flavours of Unix(TM). Moreover, RCS commands are integrated into a lot of scripts that sysadmins use (it'd be naive to think otherwise), so in terms of $$$ not having RCS in base (yup, I know the change's been reverted) has a real cost to business! Like I said, change is hard. I'm not going to argue this any further, you clearly have no interest in using better tools. Fine. >> I don't really understand the resistance. We're okay with importing Subversion which has less functionally and more dependencies but a single Fossil binary is too intrusive? > > > SVN is the necessary evil, the project uses it and until the project switches to something else we're "stuck with it". What's the case for Fossil?.. To replace RCS. But you're not interested, so I'll stop here. I have enough trouble with Luddites at $work :-) Jos > -- > Igor M. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 22:42:37 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6D86E831 for ; Thu, 10 Oct 2013 22:42:37 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B77B2481 for ; Thu, 10 Oct 2013 22:42:36 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VUOwA-0000X9-93 for freebsd-current@freebsd.org; Thu, 10 Oct 2013 15:42:30 -0700 Date: Thu, 10 Oct 2013 15:42:30 -0700 (PDT) From: Jakub Lach To: freebsd-current@freebsd.org Message-ID: <1381444950273-5850951.post@n5.nabble.com> In-Reply-To: References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> Subject: Re: rcs MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 22:42:37 -0000 I have similar views. There is abundance of be-everything-for-everybody Linuxes and not enough lean and mean Unix-style kits... -- View this message in context: http://freebsd.1045724.n5.nabble.com/rcs-tp5850096p5850951.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 23:20:20 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E7D1B4C3 for ; Thu, 10 Oct 2013 23:20:20 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 840942679 for ; Thu, 10 Oct 2013 23:20:20 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id t61so3420464wes.34 for ; Thu, 10 Oct 2013 16:20:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AS4vIVrhtRfv7OzNAN8CG+9tTONBA2Q7QxL7ylHtGwA=; b=Daysf7/hs8o5+cTqsqY9mwWK1+SPMg+Cwctx9wmpRCcExnivvu2v3LFIvCPYABSAy9 wLFumDs0BedYcnnktaDF1US9qDMu1xFphRUnKgr3hJ7xt7V3qm3VbWEt6457whWAfxtV 7EIIUjN5O68AOz86NsgJCVGStM53AAOIZR0397Pi9k4nBZ/rYb2KcShm6sE7KCfAWHyS NjG+wn808WKt1aUjWN5J0dySH99tsalqxRBZ1xHQzJUlQOZReaNUFbee1Wc9dnMBI4VO xxNbwkU+biS0epZibcNhnd7+fgLo0A5LMcWk7mXrTGW5kJzgzUN/P9LjN6cUv9mVSw8r ClGg== X-Received: by 10.180.20.46 with SMTP id k14mr527291wie.39.1381447218801; Thu, 10 Oct 2013 16:20:18 -0700 (PDT) Received: from [10.10.50.70] (52.91.249.5.rev.vodafone.pt. [5.249.91.52]) by mx.google.com with ESMTPSA id dl10sm568384wib.1.2013.10.10.16.20.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 16:20:18 -0700 (PDT) Message-ID: <5257362D.2020803@gmail.com> Date: Fri, 11 Oct 2013 00:20:13 +0100 From: "Mike C." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2 References: <52571EF6.8010703@gmail.com> <52572129.8020007@allanjude.com> In-Reply-To: <52572129.8020007@allanjude.com> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 23:20:21 -0000 On 10/10/13 22:50, Allan Jude wrote: > On 2013-10-10 17:41, Mike C. wrote: >> Hi, >> >> I'm running Alpha-2 and wanted to test with iscsi but it seems I can't >> start iscsid. >> >> >> $ sudo service iscsid onerestart >> kldload: can't load iscsi: Exec format error >> /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi >> /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid >> >> >> dmesg shows: >> interface icl.1 already present in the KLD 'kernel'! >> linker_load_file: Unsupported file type >> >> >> And also it seems that iscsi is actually already loaded: >> >> sudo kldstat -v | grep isci >> 470 pci/isci >> >> >> Any help is appreciated. >> >> >> > isci is the intel SAS driver, not iscsi (confusing name) Opps, you're right about that sorry. > > The problem appears to be that the iscsi module you have is not the same > version as your kernel, try updating to ALPHA5 > Hum, doesn't seems to be the case, but I doesn't hurt trying ALPHA 5 I guess/hope! From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 23:28:00 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 44BCE68A for ; Thu, 10 Oct 2013 23:28:00 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 14FB526F1 for ; Thu, 10 Oct 2013 23:28:00 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.7/8.14.7) with ESMTP id r9ANRteZ011987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Oct 2013 16:27:56 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: multipart/mixed; boundary="Apple-Mail=_C497258F-6A46-4B82-9FAD-98E4838ABE2F" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: FreeBSD 10 and zfsd From: Lyndon Nerenberg In-Reply-To: <52572213.2050307@allanjude.com> Date: Thu, 10 Oct 2013 16:27:54 -0700 Message-Id: References: <5256B761.4050301@gmail.com> <1381421583.19140.32451849.084D8E32@webmail.messagingengine.com> <5256E2D5.4060101@allanjude.com> <5256E680.4000008@allanjude.com> <1381430466.14387.32509497.13949CED@webmail.messagingengine.com> <20131010215949.3214f4c2@thor.walstatt.dyndns.org> <52572213.2050307@allanjude.com> To: Allan Jude X-Mailer: Apple Mail (2.1510) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 23:28:00 -0000 --Apple-Mail=_C497258F-6A46-4B82-9FAD-98E4838ABE2F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 2013-10-10, at 2:54 PM, Allan Jude wrote: > I've been working on the handbook section on ZFS and made certain to > mention that, I'll have to look at improving the man page as well, but > as far as I know, the man page is imported from IllumOS, where spares = do > work. This is probably worthy of an in-tree man page update. FreeBSD has a = reputation for having highly accurate man pages, therefore people tend = to take what they read as gospel. Right now zpool(8) clearly spells out = that hot spare substitution works. When 10.0 goes live, people are = going to believe that, and unknowingly put themselves in a position = where Bad Things could happen. Until zfsd goes into the tree, zpool(8) = should have a warning that the hot spare functionality is not available = under FreeBSD. Proposed diff attached. --lyndon --Apple-Mail=_C497258F-6A46-4B82-9FAD-98E4838ABE2F Content-Disposition: attachment; filename=zpool.diff.txt Content-Type: text/plain; name="zpool.diff.txt" Content-Transfer-Encoding: quoted-printable Index: zpool.8 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- zpool.8 (revision 255198) +++ zpool.8 (working copy) @@ -283,6 +283,7 @@ For more information, see the .Qq Sx Hot Spares section. +.Sy "(The hot spare functionality is not currently implemented on = FreeBSD.)" .It Sy log A separate-intent log device. If more than one log device is specified, = then writes are load-balanced between devices. Log devices can be mirrored. = However, @@ -425,6 +426,8 @@ attempts to put the device online automatically. Device attach = detection is hardware-dependent and might not be supported on all platforms. .Ss Hot Spares +.Sy "(The hot spare functionality is not currently implemented on = FreeBSD.)" +.Pp .Tn ZFS allows devices to be associated with pools as .Qq hot spares . @@ -1946,3 +1949,6 @@ .Xr mdoc 7 implementation of this manual page was initially written by .An Martin Matuska Aq mm@FreeBSD.org . +.Sh BUGS +Hot spare substitution awaits the import of +.Xr zfsd 8 . --Apple-Mail=_C497258F-6A46-4B82-9FAD-98E4838ABE2F Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii --Apple-Mail=_C497258F-6A46-4B82-9FAD-98E4838ABE2F-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 03:39:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B287C78C for ; Fri, 11 Oct 2013 03:39:04 +0000 (UTC) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (mail.scsiguy.com [70.89.174.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 734CE2281 for ; Fri, 11 Oct 2013 03:39:04 +0000 (UTC) Received: from [192.168.0.99] (macbook.scsiguy.com [192.168.0.99]) (authenticated bits=0) by aslan.scsiguy.com (8.14.7/8.14.5) with ESMTP id r9B3d3XD024512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Oct 2013 21:39:03 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Content-Type: multipart/mixed; boundary="Apple-Mail=_C263034D-6B06-4F6C-95A3-5C9D2C086C9F" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: undefined reference to xenpci_alloc_space From: "Justin T. Gibbs" In-Reply-To: <5256F4BA.80209@gmx.net> Date: Thu, 10 Oct 2013 21:39:03 -0600 Message-Id: <3E0575B1-D8F9-49B6-85C1-6594F03A26B2@scsiguy.com> References: <5256F4BA.80209@gmx.net> To: Michael Schmiedgen X-Mailer: Apple Mail (2.1510) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (aslan.scsiguy.com [70.89.174.89]); Thu, 10 Oct 2013 21:39:03 -0600 (MDT) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 03:39:04 -0000 --Apple-Mail=_C263034D-6B06-4F6C-95A3-5C9D2C086C9F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Oct 10, 2013, at 12:40 PM, Michael Schmiedgen = wrote: > Hi List, >=20 > is it intended that kernel does not build if >=20 > device xenpci >=20 > is omitted in the kernel config? I get the following error: >=20 > linking kernel > gnttab.o: In function `gnttab_resume': > /usr/src/sys/xen/gnttab.c:(.text+0xe47): undefined reference to = `xenpci_alloc_space' >=20 > Thanks, > Michael > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" >=20 XENHVM depends on xenpci, so you must remove XENHVM if you remove xenpci. Perhaps we should make a change similar to the attached patch in order to make this clear? -- Justin --Apple-Mail=_C263034D-6B06-4F6C-95A3-5C9D2C086C9F Content-Disposition: attachment; filename=GENERIC.diff Content-Type: application/octet-stream; name="GENERIC.diff" Content-Transfer-Encoding: 7bit Index: amd64/conf/GENERIC =================================================================== --- amd64/conf/GENERIC (revision 256304) +++ amd64/conf/GENERIC (working copy) @@ -72,7 +72,6 @@ options KDTRACE_FRAME # Ensure frames are compil options KDTRACE_HOOKS # Kernel DTrace hooks options DDB_CTF # Kernel ELF linker loads CTF data options INCLUDE_CONFIG_FILE # Include this file in kernel -options XENHVM # Include Xen support # Debugging support. Always need this: options KDB # Enable kernel debugger support. @@ -345,8 +344,10 @@ device virtio_balloon # VirtIO Memory Balloon dev # HyperV drivers device hyperv # HyperV drivers -# Xen support -device xenpci # Generic Xen bus +# Xen HVM Guest Optimizations +# NOTE: XENHVM depends on xenpci. They must be added or removed together. +options XENHVM # Xen HVM kernel infrastructure +device xenpci # Xen HVM Hypervisor services driver # VMware support device vmx # VMware VMXNET3 Ethernet Index: i386/conf/GENERIC =================================================================== --- i386/conf/GENERIC (revision 256304) +++ i386/conf/GENERIC (working copy) @@ -72,7 +72,6 @@ options MAC # TrustedBSD MAC Framework options KDTRACE_HOOKS # Kernel DTrace hooks options DDB_CTF # Kernel ELF linker loads CTF data options INCLUDE_CONFIG_FILE # Include this file in kernel -options XENHVM # Include Xen support # Debugging support. Always need this: options KDB # Enable kernel debugger support. @@ -356,8 +355,10 @@ device virtio_blk # VirtIO Block device device virtio_scsi # VirtIO SCSI device device virtio_balloon # VirtIO Memory Balloon device -# Xen support -device xenpci # Generic Xen bus +# Xen HVM Guest Optimizations +# NOTE: XENHVM depends on xenpci. They must be added or removed together. +options XENHVM # Xen HVM kernel infrastructure +device xenpci # Xen HVM Hypervisor services driver # VMware support device vmx # VMware VMXNET3 Ethernet --Apple-Mail=_C263034D-6B06-4F6C-95A3-5C9D2C086C9F-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 06:24:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 200C7335 for ; Fri, 11 Oct 2013 06:24:12 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EBEDD2AB5 for ; Fri, 11 Oct 2013 06:24:11 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id y13so3719733pdi.5 for ; Thu, 10 Oct 2013 23:24:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PORJZqs2YZ+WZMvOvWPewg+KWBbqqRizd1Q0TJTG5do=; b=SnLzogIXQuEfIZEfFEFADPInongzIZ2DbZa9onAXoPem/+n7JLYc26GXNuDMLocZRC QcpUzsnj6O6KKnzA/ktEX1hRy/72yB5F+tdcnhL363lwBEKW6hJK3LdBhvrcf/Y4+ooJ i0v8+My+d/uedW4YdPjGJ5zcJc0ewIyc5GAkSPpJRhd3i40gAJ4Ei7JyEerQrQL8AkyF LAU8I/JINEP/LqWDlH78q7YRK/aOMWcCbzbZT75I8IreEgqANXsC6EJesabbPaBnIIDP c8UZR36Ay/b7qiU0DGEzWIvWUD6GX7CYXa5w26d7z8GvE59FeqYR3ur44dN/k+RcIEZp fvtg== MIME-Version: 1.0 X-Received: by 10.68.244.168 with SMTP id xh8mr17906036pbc.3.1381472651586; Thu, 10 Oct 2013 23:24:11 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Thu, 10 Oct 2013 23:24:11 -0700 (PDT) In-Reply-To: References: <1381098538.1683.1.camel@localhost> <1381099002.1683.2.camel@localhost> <20131006232913.GA50021@troutmask.apl.washington.edu> Date: Thu, 10 Oct 2013 23:24:11 -0700 X-Google-Sender-Auth: CrqZ-UUJJoRqLMKIFb8S8sHMtKc Message-ID: Subject: Re: X related ports not finding version strings and hanging From: Kevin Oberman To: Warren Block Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-current@freebsd.org" , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 06:24:12 -0000 On Mon, Oct 7, 2013 at 1:34 PM, Warren Block wrote: > On Sun, 6 Oct 2013, Kevin Oberman wrote: > > As usual with such upgrades, pkg_libchk is your friend. Assuming you have >> updated pixman: >> portmaster graphics/libGL graphics/dri >> pkg_libchk -o | grep pixman | cut -d: -f1 | sort | uniq > pixman-files.txt >> portmaster =D `cat pixman-files.txt` >> portmaster -aD >> portmaster -y -clean-distfiles >> > > pkg_libchk -q > /tmp/to-be-rebuilt.txt > portmaster `cat /tmp/to-be-rebuilt.txt` > > worked for me, although I did it after following the pixman instructions > in /usr/ports/UPDATING. > Cool! I have somehow missed the real value of the '-q' option. Thanks! -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 06:31:15 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CF914640 for ; Fri, 11 Oct 2013 06:31:15 +0000 (UTC) (envelope-from schmiedgen@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6C3E62B17 for ; Fri, 11 Oct 2013 06:31:15 +0000 (UTC) Received: from pepe.smoke.local ([88.74.248.219]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Mh9cj-1V8IRR2EXh-00MID3 for ; Fri, 11 Oct 2013 08:31:08 +0200 Message-ID: <52579B2B.1070903@gmx.net> Date: Fri, 11 Oct 2013 08:31:07 +0200 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "Justin T. Gibbs" Subject: Re: undefined reference to xenpci_alloc_space References: <5256F4BA.80209@gmx.net> <3E0575B1-D8F9-49B6-85C1-6594F03A26B2@scsiguy.com> In-Reply-To: <3E0575B1-D8F9-49B6-85C1-6594F03A26B2@scsiguy.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:CJOMrqZWZZVS3Sr3rYoASsYt9XiLxKUzRojFqj3fmP6NVOiMLFO eZNme/8+2iPITX+7/bDZySLDZt6S4Bty2cBg0mEprPTIw6DWU56d5VaXiyYfKTny4xHH675 tm9FPAmMuJZthLNjuFCSZxGubqBpgAP+f5Qdf/gD4+406miv8uLGoitWjksqPJuNpsnCrAW zQ4D6B5grpxkX4qCgxhfw== Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 06:31:15 -0000 On 10/11/13 05:39, Justin T. Gibbs wrote: > On Oct 10, 2013, at 12:40 PM, Michael Schmiedgen wrote: >> >> is it intended that kernel does not build if >> >> device xenpci >> >> is omitted in the kernel config? I get the following error: >> >> linking kernel >> gnttab.o: In function `gnttab_resume': >> /usr/src/sys/xen/gnttab.c:(.text+0xe47): undefined reference to `xenpci_alloc_space' >> >> Thanks, >> Michael > > XENHVM depends on xenpci, so you must remove XENHVM if you remove > xenpci. Perhaps we should make a change similar to the attached > patch in order to make this clear? > Arghh, my fault. I did not inspect changes to kernel config carefully enough. Thanks for the hint. Michael From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 07:02:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BB6F6D54 for ; Fri, 11 Oct 2013 07:02:30 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 565B72C72 for ; Fri, 11 Oct 2013 07:02:30 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id t60so3696372wes.2 for ; Fri, 11 Oct 2013 00:02:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=MWbmIGyoT/i29rFLLYv2pgNn6l+8zGTQtN1CwiaPy2g=; b=bE7KYCM1avstQnEG6i4Sv0YXd5FMFBnOaUaKIuKHZolBpcni9orbgYCeTTdcGTlsAS YUOIJsfzB6K7GQ3QMKv2JRDyk8DFFtotc8kAQGqCrnwx6s1PO0LfxkZkFDBcPIv8wy51 GTpLnZJuOz/5uXPG42iNii80CfRSWniJzuoEJC0ZY2K7K6dXqqVKlb4cNprfzZUcG7kI ljIf8ObJPWyaEHnErfsaHQMXGYJm3gAQTSqO3pRx2p7oGGEgGzVfPh3aW8mdiXPlyZfa zc9+UuImjwClYC7QDOBzJlkg27GSr2iH5jxAful/IfiP+twtdc5E2BZUwAty2IR3eut8 MlXw== X-Received: by 10.180.20.177 with SMTP id o17mr1865387wie.38.1381474948026; Fri, 11 Oct 2013 00:02:28 -0700 (PDT) Received: from [192.168.1.129] ([193.173.55.180]) by mx.google.com with ESMTPSA id ft19sm2739916wic.5.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 00:02:27 -0700 (PDT) Message-ID: <5257A284.2040406@gmail.com> Date: Fri, 11 Oct 2013 09:02:28 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: FreeBSD Subject: Re: FreeBSD 10 and zfsd. References: <5256B761.4050301@gmail.com> In-Reply-To: <5256B761.4050301@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 07:02:30 -0000 Johan Hendriks wrote: > When i started using ZFS on FreeBSD I quickly found out that hot > spares are not possible on FreeBSD. > I was told that with zfsd it should be possible and that it would be > included in FreeBSD 10. > > Is there some info about the zfsd function and how it could be used? > > regards > Johan Hendriks > Thanks all for the explanation and your time A notice in the handbook may be a good thing to let new FreeBSD users know that you can add spares, but that it is not a hot spare. So human action is required to activate the spare. regards Johan Hendriks From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 07:23:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 52A74FD for ; Fri, 11 Oct 2013 07:23:49 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 196962D4B for ; Fri, 11 Oct 2013 07:23:49 +0000 (UTC) Received: by mail-oa0-f43.google.com with SMTP id i3so2150526oag.2 for ; Fri, 11 Oct 2013 00:23:48 -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 :content-type; bh=i87NTfl/WGlJyLbpL+IlCeaMandAL+yzHCJ750pcsss=; b=MrY/Xv4SyBcMctlw8au+GLzAL1oYWt78qsXJHTzK+GhrL0B35PWYW6rhzrcgugkxCI NECMQPyhEqfOpY+csXeLYf0M+PyQN+wuJtUbJTHiPANNsaEpHyZLJB1QZISXAInFnWMI Hq0uXwhnipoAZklQCtngeWgg5XNxm6zZGLe5lbAkGtiieiodxKuZBQ9CF0AlChyIK7lj uj1yF/oGCxWaDBCmxumcpdrEplRloEPaxfJwBxmMgNGRmhn4P5XU8uP8MOn4bwTSX3HY 4IHlK0poZpxql2wNKv6tSeiB6WO4wwc+mdiZnFdhS7EiyGe9hdc09F9l8TH+o+/1QKJW GEyQ== MIME-Version: 1.0 X-Received: by 10.60.103.37 with SMTP id ft5mr745053oeb.45.1381476228352; Fri, 11 Oct 2013 00:23:48 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Fri, 11 Oct 2013 00:23:48 -0700 (PDT) In-Reply-To: References: <20131010013338.GA10499@troutmask.apl.washington.edu> Date: Fri, 11 Oct 2013 03:23:48 -0400 Message-ID: Subject: Re: /usr/src/lib/msun errors From: Joe Nosay To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 07:23:49 -0000 I did. Looks like I hosed part of the system but I am using it now. I'm getting libiconv errors. Vi has been replaced with nvi. Neat. I need to extract /base over /base. So, um, time to use the CD and set up a new system,right? On Thu, Oct 10, 2013 at 4:14 AM, Andreas Nilsson wrote: > Since there is -Wall in your CFALGS there will be quite a few warnings, > which combined with -Werror which promotes warnings to errors makes it fail. > > Try removing -Wall and see if it works. Also -mssse3 can trigger more > subtle stuff. > > Best regards > Andreas > > > On Thu, Oct 10, 2013 at 9:49 AM, Joe Nosay wrote: > >> Yes, I did. To what extent did I screw up? >> >> # added by use.perl 2013-03-03 23:39:20 >> PERL_VERSION=5.16.2 >> RUBY_DEFAULT_VER=1.9 >> ALLOW_SHARED_TEXTREL=1 >> >> CFLAGS+= -mssse3 -Wall >> CXXFLAGS+= -mssse3 >> >> >> >> >> On Wed, Oct 9, 2013 at 9:33 PM, Steve Kargl < >> sgk@troutmask.apl.washington.edu> wrote: >> >> > On Wed, Oct 09, 2013 at 09:00:11PM -0400, Joe Nosay wrote: >> > > Src is from 10/7/13 on i386. Base is from April. >> > >> > > cc -O2 -pipe -mssse3 -Wall -I/usr/src/lib/msun/x86 >> > -I/usr/src/lib/msun/ld80 -I/usr/src/lib/msun/src >> > -I/usr/src/lib/msun/../libc/include -I/usr/src/lib/msun/../libc/i386 >> > -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror >> > -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int >> > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality >> > -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum >> > -Wno-knr-promoted-parameter -Wno-parentheses -c >> > /usr/src/lib/msun/src/e_j0.c -o e_j0.o >> > > /usr/src/lib/msun/src/e_j0.c:281:10: error: variable 'p' is used >> > uninitialized whenever 'if' condition is false >> > [-Werror,-Wsometimes-uninitialized] >> > >> > Are you setting CFLAGS in make.conf? >> > >> > -- >> > Steve >> > >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> > > From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 07:24:37 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 24E6121A for ; Fri, 11 Oct 2013 07:24:37 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 021512D60 for ; Fri, 11 Oct 2013 07:24:36 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 793FA2D2C6 for ; Fri, 11 Oct 2013 07:24:29 +0000 (UTC) Message-ID: <5257A7C3.8080004@allanjude.com> Date: Fri, 11 Oct 2013 03:24:51 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: FreeBSD 10 and zfsd. References: <5256B761.4050301@gmail.com> <5257A284.2040406@gmail.com> In-Reply-To: <5257A284.2040406@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 07:24:37 -0000 On 2013-10-11 03:02, Johan Hendriks wrote: > Johan Hendriks wrote: >> When i started using ZFS on FreeBSD I quickly found out that hot >> spares are not possible on FreeBSD. >> I was told that with zfsd it should be possible and that it would be >> included in FreeBSD 10. >> >> Is there some info about the zfsd function and how it could be used? >> >> regards >> Johan Hendriks >> > Thanks all for the explanation and your time > A notice in the handbook may be a good thing to let new FreeBSD users > know that you can add spares, but that it is not a hot spare. > So human action is required to activate the spare. > > regards > Johan Hendriks > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" That bit is in the zfs handbook project branch, it just isn't published yet -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 08:24:50 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1DFD1C9E for ; Fri, 11 Oct 2013 08:24:50 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ee0-x22e.google.com (mail-ee0-x22e.google.com [IPv6:2a00:1450:4013:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A9DB32057 for ; Fri, 11 Oct 2013 08:24:49 +0000 (UTC) Received: by mail-ee0-f46.google.com with SMTP id c13so1674341eek.19 for ; Fri, 11 Oct 2013 01:24:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OsV2w8NjH2UhUas+IxmPxcZ3ilzP0YZaZa/8T/L1whI=; b=y2nBEFWVXB4K5A3vVCK7tvh4aH9V/b5vKTOjtjdWZjbEwDmoMUOwxXm5ogP70iYKwk Ao02r3NSIfZVB0rUSgBi+SGw5D0+3mi9zWOmPFz0xjIZe9+WXjErdHGYAhHgDgI4WwFQ Ec9kWKR9HpfyG14pruG+QcXXigSYAhAK267h2iKQ9Bc5gV2P34Z4qgMMcp0SgDIDXWAf nc70cdIROSDix63n5J0wvVbv+aMmxnsH7IApQlJ28Ci4YyhEIkOC1agf76Qf7HMXhXk7 TEB0np4nday9gMowT3yNt8DhqsKMesfKSLRvbzzC6HqztfBYfdMkrLD0FtYMk2ITRxTJ THdQ== X-Received: by 10.15.94.201 with SMTP id bb49mr27700447eeb.23.1381479887933; Fri, 11 Oct 2013 01:24:47 -0700 (PDT) Received: from strashydlo.home (adga102.neoplus.adsl.tpnet.pl. [79.184.130.102]) by mx.google.com with ESMTPSA id n48sm111940173eeg.17.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 01:24:46 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2 Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: <52571EF6.8010703@gmail.com> Date: Fri, 11 Oct 2013 10:24:39 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <52571EF6.8010703@gmail.com> To: Mike C. X-Mailer: Apple Mail (2.1283) Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 08:24:50 -0000 Wiadomo=B6=E6 napisana przez Mike C. w dniu 10 pa=BC 2013, o godz. = 23:41: > Hi, >=20 > I'm running Alpha-2 and wanted to test with iscsi but it seems I can't > start iscsid. >=20 >=20 > $ sudo service iscsid onerestart > kldload: can't load iscsi: Exec format error > /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi > /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid >=20 >=20 > dmesg shows: > interface icl.1 already present in the KLD 'kernel'! > linker_load_file: Unsupported file type Do you have "device ctl" in your kernel config? If so, either remove it (ctl.ko module is automatically loaded by ctladm), or add "device iscsi". The problem here is that part of the code (icl) is shared between the target (which is part of CTL) and initiator (iscsi.ko); compiling CTL into the kernel pulls that part in, and the iscsi.ko can't get loaded because, well, "icl is already present in the kernel", as the error message says. Let me know how it works for you. --=20 If you cut off my head, what would I say? Me and my head, or me and my = body? From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 08:27:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 21E5FDDE for ; Fri, 11 Oct 2013 08:27:47 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D4CE9207D for ; Fri, 11 Oct 2013 08:27:46 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1VUY4W-003JQQ-1o>; Fri, 11 Oct 2013 10:27:44 +0200 Received: from g231220250.adsl.alicedsl.de ([92.231.220.250] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1VUY4V-000pq4-TS>; Fri, 11 Oct 2013 10:27:44 +0200 Date: Fri, 11 Oct 2013 10:27:42 +0200 From: "O. Hartmann" To: Allan Jude Subject: Re: FreeBSD 10 and zfsd. Message-ID: <20131011102742.581fa352@thor.walstatt.dyndns.org> In-Reply-To: <5257A7C3.8080004@allanjude.com> References: <5256B761.4050301@gmail.com> <5257A284.2040406@gmail.com> <5257A7C3.8080004@allanjude.com> Organization: FU Berlin X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/sU=lHrT.XaOjWkrJ_1.phnw"; protocol="application/pgp-signature" X-Originating-IP: 92.231.220.250 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 08:27:47 -0000 --Sig_/sU=lHrT.XaOjWkrJ_1.phnw Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 11 Oct 2013 03:24:51 -0400 Allan Jude wrote: > On 2013-10-11 03:02, Johan Hendriks wrote: > > Johan Hendriks wrote: > >> When i started using ZFS on FreeBSD I quickly found out that hot > >> spares are not possible on FreeBSD. > >> I was told that with zfsd it should be possible and that it would > >> be included in FreeBSD 10. > >> > >> Is there some info about the zfsd function and how it could be > >> used? > >> > >> regards > >> Johan Hendriks > >> > > Thanks all for the explanation and your time > > A notice in the handbook may be a good thing to let new FreeBSD > > users know that you can add spares, but that it is not a hot spare. > > So human action is required to activate the spare. > > > > regards > > Johan Hendriks > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" > That bit is in the zfs handbook project branch, it just isn't > published yet >=20 ... so it isn't visible to the "normal" users. I would also appreciate a hint in the man page of zpool(8). Like=20 "Be aware: A spare declared vdev is not (yet) automatically replacing a faulty rendered drive. Human action is still required." It could save some trouble in prevention. Oliver --Sig_/sU=lHrT.XaOjWkrJ_1.phnw Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJSV7Z+AAoJEOgBcD7A/5N8dgEH/3b0VS8DH9cL3ryEvHCN60/N qWIoLsZ1kDsYkab+EnzHISNbkdpvIcUK6K5Rc1sZMDgcEr3BoxNL5cRNnns0aoPT GyQCKF02oH3K7Tq7aI91d26QnUqOVexvzVFpOwcLCJ+4N7WpD3mmz2Ws27WemCb1 08z9gtTDQ0SlQipyzdF1LdtSO7wDyp38iWLxHh9noPjG4+e2eb3Xw4qA+btR/Sd0 sz8HRBd8h9NkRnJCrHkGsjroJ2IcKutjTsUxM7wm/UwlQh1mgmbIJxCKcO8hNBIr rTKwGGyGGo7mCZ8UndMdQIWp/hbXZ3kvf2VngibQKOiJFbmJ2evBJjQUwIkPQ2E= =+vRr -----END PGP SIGNATURE----- --Sig_/sU=lHrT.XaOjWkrJ_1.phnw-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 09:27:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 012B07BF for ; Fri, 11 Oct 2013 09:27:28 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from eu1sys200aog121.obsmtp.com (eu1sys200aog121.obsmtp.com [207.126.144.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5853C23A9 for ; Fri, 11 Oct 2013 09:27:28 +0000 (UTC) Received: from mail-wg0-f52.google.com ([74.125.82.52]) (using TLSv1) by eu1sys200aob121.postini.com ([207.126.147.11]) with SMTP ID DSNKUlfEY6bWPyWx6spKHU3mWREajH/5g/uB@postini.com; Fri, 11 Oct 2013 09:27:28 UTC Received: by mail-wg0-f52.google.com with SMTP id m15so3916412wgh.7 for ; Fri, 11 Oct 2013 02:26:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:message-id:to:subject:cc :reply-to:in-reply-to; bh=7ASDhr6yfnCsdcyoMD+iOCxFGvegsDNRQtwKs3UmZYE=; b=YBMVR+ktS95z2I2FfmWberVyFObMy6h0tkKTwbIfD5FWVS9h68fJKVv7aZA4YZ5+xI NwBpi5FziEiF9X9cDFmT+BOiE3n83moPRqXP1yp6pSaAzI7XcEXo+K/AOk9+U4gxxrHL B2T25oni5c40k8lSUvYCOyosHZOg1fdrFFwBoCpSp0nwMmMCUnrl1BJQVVlS7egK5+qQ GgVrVoBZnPJu9SFZVW4sOR4A56EI54wkZsgMav7437xGeIx3PrWCWitoiVX/+meyjB3K e2dR2XWQyY1FaXZe4p4ZqJ/7HxpoME29+0K8T3gsn0+57z8a950ex0eDEtbTZiEVxkp0 V70w== X-Gm-Message-State: ALoCoQln0hXJa4iTg+PdCaTUgTM51wp82LQsK6N5jDvraTXsZxYtgLtmZcs1TC7hJop9HavMudiSkP9leIgvHMHHyhDVxMMzrt52Qo9N44s7XSWIAch/rTT5UwvT5x4SKd2BupTKOxi4WkJY15NGOnLlnP0gAhWLpUhl+bFMXz+Td4fWz/fMurI= X-Received: by 10.180.101.134 with SMTP id fg6mr2386006wib.9.1381483618896; Fri, 11 Oct 2013 02:26:58 -0700 (PDT) X-Received: by 10.180.101.134 with SMTP id fg6mr2385998wib.9.1381483618831; Fri, 11 Oct 2013 02:26:58 -0700 (PDT) Received: from mech-cluster241.men.bris.ac.uk (mech-cluster241.men.bris.ac.uk. [137.222.187.241]) by mx.google.com with ESMTPSA id dl10sm4296334wib.1.2013.10.11.02.26.56 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Oct 2013 02:26:57 -0700 (PDT) Sender: Anton Shterenlikht Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6) with ESMTP id r9B9QtCA080268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 11 Oct 2013 10:26:55 +0100 (BST) (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.7/8.14.6/Submit) id r9B9Qt4d080267; Fri, 11 Oct 2013 10:26:55 +0100 (BST) (envelope-from mexas) Date: Fri, 11 Oct 2013 10:26:55 +0100 (BST) From: Anton Shterenlikht Message-Id: <201310110926.r9B9Qt4d080267@mech-cluster241.men.bris.ac.uk> To: davide@freebsd.org, mexas@bris.ac.uk Subject: Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks In-Reply-To: Cc: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bris.ac.uk List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 09:27:29 -0000 >From davide.italiano@gmail.com Thu Sep 26 13:12:30 2013 >On Thu, Sep 26, 2013 at 12:23 PM, Anton Shterenlikht wrote: >> >> Regarding textdump(4), I'm not clear where the following >> "scripts" should be located and used: >> > >[snip] > >> Are these ddb(8) commands? Or do I set these in /etc/rc.conf? >> > >The scripts (quotes unneeded) should be located in /etc/ddb.conf. >I think you want ddb_enable="YES" in your /etc/rc.conf I've set textdump following the man page. I've got several more deadlocks, but it seems savecore causes deadlock too! # savecore savecore: reboot after panic: deadlkres: possible deadlock detected for 0xe0000000129d2000, blocked for 902608 ticks savecore: writing core to ./vmcore.5 When the size of vmcore.x file gets to about 9GB, I get a deadlock again. What can I do now? Thanks Anton From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 11:15:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3E4823E2; Fri, 11 Oct 2013 11:15:38 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A95222B6E; Fri, 11 Oct 2013 11:15:37 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id hm2so909327wib.10 for ; Fri, 11 Oct 2013 04:15:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ofVH28r88WxSLZxkIRL/9pKVCtZUX4nxInJnhIWrkfQ=; b=JHmgLmD/qC1ZPwGvDoVp0RuJ4yumEQrfJQ+a5yzALdNwR2a8dP5flyCl3sUzpJVs2o L3zaSKW67JdUjlAU+Ri2ZCLxztWBojpXmU5bedxYMXuR8FVsm7RYF/Qit/C284qZJtFu rFMOqyrkhV6sDUT3cC+21p2S+0iIDrzjkFm2Bk1FnR7DCyhj7WLF3sT5NiDz4oUZt4LU OVmItr6lmQsvtNMVHvXD4SDat6RtcvLWw5zJa5lSfSv1zLpw8+4WyIZPv4QuFu+LOcQ3 057yrT6IJzupNtLnW9H5utQBdmyoYCxy89NlyrHgy6GM4DFsyqyF62Q/6mAsi7f/WSqE 3xdQ== X-Received: by 10.180.208.2 with SMTP id ma2mr2765463wic.52.1381490136060; Fri, 11 Oct 2013 04:15:36 -0700 (PDT) Received: from [10.10.50.70] (52.91.249.5.rev.vodafone.pt. [5.249.91.52]) by mx.google.com with ESMTPSA id y20sm4117642wib.0.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 04:15:35 -0700 (PDT) Message-ID: <5257DDD1.4070403@gmail.com> Date: Fri, 11 Oct 2013 12:15:29 +0100 From: "Mike C." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: =?ISO-8859-2?Q?Edward_Tomasz_Napiera=B3a?= Subject: Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2 References: <52571EF6.8010703@gmail.com> In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 11:15:38 -0000 On 10/11/13 09:24, Edward Tomasz Napierała wrote: > Wiadomość napisana przez Mike C. w dniu 10 paź 2013, o godz. 23:41: >> Hi, >> >> I'm running Alpha-2 and wanted to test with iscsi but it seems I can't >> start iscsid. >> >> >> $ sudo service iscsid onerestart >> kldload: can't load iscsi: Exec format error >> /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi >> /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid >> >> >> dmesg shows: >> interface icl.1 already present in the KLD 'kernel'! >> linker_load_file: Unsupported file type > > Do you have "device ctl" in your kernel config? If so, > either remove it (ctl.ko module is automatically loaded > by ctladm), or add "device iscsi". device ctl # CAM Target Layer Seems that GENERIC has it by default! I'll remove and recompile! Thanks > > The problem here is that part of the code (icl) is shared > between the target (which is part of CTL) and initiator > (iscsi.ko); compiling CTL into the kernel pulls that part > in, and the iscsi.ko can't get loaded because, well, "icl > is already present in the kernel", as the error message > says. > > Let me know how it works for you. > From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 05:30:09 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 171169C0 for ; Fri, 11 Oct 2013 05:30:09 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.upper.net (mail.upper.net [62.75.224.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 823222743 for ; Fri, 11 Oct 2013 05:30:07 +0000 (UTC) Received: from ubm.strangled.net (mail.upper.net [62.75.224.33]) (authenticated bits=0) by mail.upper.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id r9B55vDE016923; Fri, 11 Oct 2013 07:05:57 +0200 Received: from ubm.strangled.net ([92.230.221.219] helo=ubm.strangled.net) by ASSP.nospam.UpPeRnEt; 11 Oct 2013 07:05:57 +0200 Date: Fri, 11 Oct 2013 07:05:56 +0200 From: Marc "UBM" Bocklet To: current@freebsd.org Subject: Re: /usr/local/lib /usr/bin/ld: =?ISO-8859-1?Q?=F8:?= invalid DSO for symbol Message-Id: <20131011070556.e31c63fce9d60266c23bda9e@u-boot-man.de> In-Reply-To: <20131010215855.GA90129@direwolf.aux.io> References: <20131010215148.6d4e724952052b8833133264@gmail.com> <20131010215855.GA90129@direwolf.aux.io> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Fri, 11 Oct 2013 11:22:43 +0000 Cc: agh@fastmail.fm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 05:30:09 -0000 On Fri, 11 Oct 2013 05:58:56 +0800 Alastair Hogge wrote: > On 2013-10-10 Thu 21:51:48 +0200, Marc UBM wrote: > > > > Hiho! :-) >=20 > Hi >=20 > > Trying to compile several ports in the wake of the recent iconv change > > yields the following error that I could not get rid of yet: > > > > ---- > > libtool: link: cc -O2 -pipe -fno-strict-aliasing -Wall > > -I/usr/local/include -Wl,-rpath=3D/usr/local/lib > > -Wl,-rpath=3D/usr/local/lib -o irssi gui-entry.o gui-expandos.o > > gui-printtext.o gui-readline.o gui-windows.o lastlog.o mainwindows.o > > mainwindow-activity.o mainwindows-layout.o statusbar.o > > statusbar-config.o statusbar-items.o term.o term-dummy.o tparm.o > > term-terminfo.o terminfo-core.o textbuffer.o textbuffer-commands.o > > textbuffer-view.o irssi.o module-formats.o > > -Wl,-R/usr/local/lib/perl5/5.14/mach/CORE -pthread -Wl,-E > > -fstack-protector -Wl,--export-dynamic -pthread > > -Wl,--export-dynamic ../fe-common/irc/libfe_common_irc.a ../fe-common/= irc/dcc/libfe_irc_dcc.a ../fe-common/irc/notifylist/libfe_irc_notifylist.a = ../fe-common/core/libfe_common_core.a ../irc/libirc.a ../irc/core/libirc_co= re.a ../irc/dcc/libirc_dcc.a ../irc/flood/libirc_flood.a ../irc/notifylist/= libirc_notifylist.a ../core/libcore.a ../lib-config/libirssi_config.a ../pe= rl/.libs/libperl_core_static.a ../perl/.libs/libfe_perl_static.a > > -L/usr/local/lib -L/usr/local/lib/perl5/5.14/mach/CORE -lperl -lm > > -lcrypt > > -lutil /usr/local/lib/libgmodule-2.0.so /usr/local/lib/libglib-2.0.so /= usr/local/lib/libpcre.so /usr/local/lib/libintl.so > > -lssl -lcrypto -lncurses -pthread -Wl,-rpath -Wl,/usr/local/lib > > -Wl,-rpath -Wl,/usr/local/lib /usr/bin/ld: =F8: invalid DSO for symbol > > `tgetnum' definition /usr/local/lib/libtinfo.so.5.9: could not read > > symbols: Bad value > > ---- > > > > > > Any ideas how to solve that one / if I am doing something wrong? >=20 > Add the following to the offending ports' Makefile (I am upto 6): > LDFLAGS+=3D -ltinfow That worked perfectly, going to try it out on the other six offenders thus evening. Thanks a lot! Bye Marc From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 12:37:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 146A4441; Fri, 11 Oct 2013 12:37:06 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 94581221E; Fri, 11 Oct 2013 12:37:05 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id o17so2367014oag.32 for ; Fri, 11 Oct 2013 05:37:04 -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=qRAJ5+Fweq5riYSRWT0qVTvhYUPEfYkCMziahkj9NlM=; b=YR40qGcOOht/xw6ImDaWTWq+6ytzcmhRIfdAca+CNUnsZSay8h4Y6evpADYOLtloYx 6hPF+PhFOj5RRVF5hwOozEEUKfaWhPRyA+wcIG+0Qs43LOI7wXgMh5X4jZ6Be6bfL5HZ EHclXyDvUuMLb2DaCmsyg+UOdHud4+RpntYppoPYmfsrbU9UpO/78Mt3GtTiLP+PsJoF +xZ6z1k9e4ShYmr5axM/8Sw7BBVrAKCMQiP3niJU6/BW/awixNNmUPbinn6ZCaRkOkRN gjW/mzxgEwQeNY/8mCjoxcu8P3MQepiCt7GTmdXgSgECFU0MV7baLUg1TrREO6UK5dhv RB7w== MIME-Version: 1.0 X-Received: by 10.60.63.9 with SMTP id c9mr14133184oes.35.1381495024552; Fri, 11 Oct 2013 05:37:04 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Fri, 11 Oct 2013 05:37:04 -0700 (PDT) In-Reply-To: References: <522A1C73.9030402@mu.org> Date: Fri, 11 Oct 2013 08:37:04 -0400 Message-ID: Subject: Re: New iSCSI stack. From: Outback Dingo To: =?ISO-8859-2?Q?Edward_Tomasz_Napiera=B3a?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-scsi@freebsd.org, "freebsd-arch@freebsd.org" , Alfred Perlstein , "freebsd-current@FreeBSD.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 12:37:06 -0000 On Wed, Sep 11, 2013 at 5:14 PM, Edward Tomasz Napiera=C5=82a wrote: > I'm working on last few minor nits to get this into the tree. Give me fe= w > days, > I'll prepare a patch against 9-STABLE. > > Quick question, is there a specific reason why ctld doesnt create the file / device for iscsi, or fc ? the previous iscsi would read the config file and create the file / device ... it now appears to be a manual process. From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 13:06:00 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6D64EB17 for ; Fri, 11 Oct 2013 13:06:00 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [IPv6:2a01:4f8:141:5ffd::25]) by mx1.freebsd.org (Postfix) with ESMTP id 131FA23E2 for ; Fri, 11 Oct 2013 13:06:00 +0000 (UTC) Received: from [10.0.2.17] (a44084.upc-a.chello.nl [62.163.44.84]) by mail.jr-hosting.nl (Postfix) with ESMTPSA id 77C4538B108A for ; Fri, 11 Oct 2013 15:05:50 +0200 (CEST) From: Remko Lodder Content-Type: multipart/signed; boundary="Apple-Mail=_8B29B1C1-0A0F-4A84-9A78-BBFD0355D024"; protocol="application/pgp-signature"; micalg=pgp-sha1 Subject: Fwd: svn commit: r256256 - in head: . etc etc/defaults etc/rc.d share/man/man5 usr.sbin/jail Date: Fri, 11 Oct 2013 15:05:51 +0200 References: <04E9979E-1D97-4AA2-A7AE-F9D8457B3599@FreeBSD.org> To: current@FreeBSD.org Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 13:06:00 -0000 --Apple-Mail=_8B29B1C1-0A0F-4A84-9A78-BBFD0355D024 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear Current readers, Please find issues that I have with the latest /etc/rc.d/jail changes = and the use of ezjail. Thanks remko Begin forwarded message: > From: Remko Lodder > Subject: Re: svn commit: r256256 - in head: . etc etc/defaults = etc/rc.d share/man/man5 usr.sbin/jail > Date: October 11, 2013 3:04:12 PM GMT+02:00 > To: Hiroki Sato > Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, = svn-src-head@freebsd.org >=20 >=20 > Hi Hiroki, >=20 > On Oct 10, 2013, at 11:32 AM, Hiroki Sato wrote: >=20 >> Author: hrs >> Date: Thu Oct 10 09:32:27 2013 >> New Revision: 256256 >> URL: http://svnweb.freebsd.org/changeset/base/256256 >>=20 >> Log: >> - Update rc.d/jail to use a jail(8) configuration file instead of >> command line options. The "jail__*" rc.conf(5) variables = for >> per-jail configuration are automatically converted to >> /var/run/jail..conf before the jail(8) utility is invoked. >> This is transparently backward compatible. >>=20 >> - Fix a minor bug in jail(8) which prevented it from returning false >> when jail -r failed. >>=20 >=20 > Thanks for doing such a massive update. However it seems to break the = ezjail utility. > My jails didn't restart after I upgraded to the most recent -head = version=20 >=20 > FreeBSD nakur.elvandar.org 10.0-ALPHA6 FreeBSD 10.0-ALPHA6 #7 r256311: = Fri Oct 11 13:27:54 CEST 2013 = root@nakur.elvandar.org:/usr/obj/usr/src/sys/NAKUR amd64 >=20 > If I replace this with an older version, the utility starts and = complains about certain things not being done properly. The > system does not mount devfs nodes anylonger and thus is basically out = of function. >=20 > I was not expecting this much fallout from this change, others that = will be upgrading will loose the ability to start their jails until they = can > resolve this by hand. >=20 > Thanks > Remko >=20 >> Approved by: re (glebius) >>=20 >> Modified: >> head/UPDATING >> head/etc/defaults/rc.conf >> head/etc/rc.d/jail >> head/etc/rc.subr >> head/share/man/man5/rc.conf.5 >> head/usr.sbin/jail/jail.c >>=20 >> Modified: head/UPDATING >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >> --- head/UPDATING Thu Oct 10 07:41:11 2013 (r256255) >> +++ head/UPDATING Thu Oct 10 09:32:27 2013 (r256256) >> @@ -31,6 +31,25 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 10 >> disable the most expensive debugging functionality run >> "ln -s 'abort:false,junk:false' /etc/malloc.conf".) >>=20 >> +20131010: >> + The rc.d/jail script has been updated to support jail(8) >> + configuration file. The "jail__*" rc.conf(5) variables >> + for per-jail configuration are automatically converted to >> + /var/run/jail..conf before the jail(8) utility is = invoked. >> + This is transparently backward compatible. See below about some >> + incompatibilities and rc.conf(5) manual page for more details. >> + >> + These variables are now deprecated in favor of jail(8) = configuration >> + file. One can use "rc.d/jail config " command to = generate >> + a jail(8) configuration file in /var/run/jail..conf = without >> + running the jail(8) utility. The default pathname of the >> + configuration file is /etc/jail.conf and can be specified by >> + using $jail_conf or $jail__conf variables. >> + >> + Please note that jail_devfs_ruleset accepts an integer at >> + this moment. Please consider to rewrite the ruleset name >> + with an integer. >> + >> 20130930: >>=20 --=20 /"\ With kind regards, | remko@elvandar.org \ / Remko Lodder | remko@FreeBSD.org X FreeBSD | = http://www.evilcoder.org / \ The Power to Serve | Quis custodiet ipsos custodes --Apple-Mail=_8B29B1C1-0A0F-4A84-9A78-BBFD0355D024 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJSV/evAAoJEKjD27JZ84ywUvEQAKlsVBXvQgA1Lat+ohD7UTcF S5f5LhciXnlHUxkgsvPZngTMtYiPxXrjwbmfHPHNjDpiHyAIEZapMd13CLaMQPZl xTl+7OOPCgN4FWeZMYEu6oGWNLi97sJqhpArf9xejoYhUnH80YHnP6WhY9cobzep X+LVRAWFDwnxWRqKBgQccWsniM+TWjo/LQCs4rkWXOT3EsrkM71B9MwzjLRhyzC1 7uQIuVUjmeda5Ed8dzuNWcJVgbjUgbF3zoGLq4THDe9XysatLo1JJIm9k8Low41K DbFN3DW0uaahyj8bGnQ4s/7DGe0TN65Cn55qH1hOiNG8WBuh2Y/NGGpKdckhZREQ 7zgk3yaLsoqI/LGWO5sow9T1OpAFMyoOD7BXjhWcGoKN4YuPd1UwXJDtxdzC/nQD Ugd4CJ0UdyicNI0QQnhdcUO4046PAtU/hTZTspSWrFyz6EorsVh2WBNlJAUvCUX9 LVNuTp/8A89nn3w8d36blWQNwtQWkS3V+DLhPRGvvAFl1oAoON3OUWuTDU9HQ4TM AbfaK3/Z8ZYo+KsFhQzr7jTJHahOYrTgeW/zFyhaBvNwUHAN2f3LhKlsYk0NMQ7f DxlLzlWGrTn6pePeuqWxIIeze3RwmHgHGxknhlrAhY5ONqH49VWA9kuos+x7Q+RY G64lkkveITjrC1qXc49J =A2vn -----END PGP SIGNATURE----- --Apple-Mail=_8B29B1C1-0A0F-4A84-9A78-BBFD0355D024-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 13:17:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DAC83DBA; Fri, 11 Oct 2013 13:17:44 +0000 (UTC) (envelope-from davide.italiano@gmail.com) Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 875732477; Fri, 11 Oct 2013 13:17:44 +0000 (UTC) Received: by mail-vc0-f177.google.com with SMTP id hv10so2780129vcb.36 for ; Fri, 11 Oct 2013 06:17:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=35ncyOzpSqVUu2VTB6fYyOiVcHa0AiafyMHz/TTeVCo=; b=UQ2NsdzLOa+jw+/jY/9DNm/0TDl80eaQ9nbTtBGdoiy4DSDEcSGLwcnrz4mr/jIdib apV/K2zJgSudcnulZdU2CJu7Czymst8VXUsZ121Xu7+8/PQHbZPhbrwDERcgS35uQjje XxQdVlt/QKiDQnefn+DM4y9ZcSfntNOaJrSQbc4LOHCZdQe3zKDwTXwA6vqJ/7PGsNtB WbafZq7e+cT4PwDP4CPbDLWnT5steDr4y/rrEoTp++zRP9O3oC3eeiA4cww96ZDO4IQM ai3adE/hbH5iACyRlULbCM0IMT8Iq06anC9O6e6laBcZhtk9QL2kVqeSlUD/bGb4ndD4 gSEQ== MIME-Version: 1.0 X-Received: by 10.52.244.15 with SMTP id xc15mr345807vdc.52.1381497463457; Fri, 11 Oct 2013 06:17:43 -0700 (PDT) Sender: davide.italiano@gmail.com Received: by 10.220.94.71 with HTTP; Fri, 11 Oct 2013 06:17:43 -0700 (PDT) In-Reply-To: <201310110926.r9B9Qt4d080267@mech-cluster241.men.bris.ac.uk> References: <201310110926.r9B9Qt4d080267@mech-cluster241.men.bris.ac.uk> Date: Fri, 11 Oct 2013 15:17:43 +0200 X-Google-Sender-Auth: _1OWfGH8Vwqhfcgu5zrsPpUZ4ro Message-ID: Subject: Re: panic: ia64 r255811: deadlkres: possible deadlock detected for 0xe000000012d07b00, blocked for 902743 ticks From: Davide Italiano To: mexas@bris.ac.uk Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current , freebsd-ia64@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 13:17:44 -0000 On Fri, Oct 11, 2013 at 11:26 AM, Anton Shterenlikht wrote: > >From davide.italiano@gmail.com Thu Sep 26 13:12:30 2013 >>On Thu, Sep 26, 2013 at 12:23 PM, Anton Shterenlikht wrote: >>> >>> Regarding textdump(4), I'm not clear where the following >>> "scripts" should be located and used: >>> >> >>[snip] >> >>> Are these ddb(8) commands? Or do I set these in /etc/rc.conf? >>> >> >>The scripts (quotes unneeded) should be located in /etc/ddb.conf. >>I think you want ddb_enable="YES" in your /etc/rc.conf > > I've set textdump following the man page. > > I've got several more deadlocks, but > it seems savecore causes deadlock too! > > # savecore > savecore: reboot after panic: deadlkres: possible deadlock detected for 0xe0000000129d2000, blocked for 902608 ticks > savecore: writing core to ./vmcore.5 > > When the size of vmcore.x file gets to about 9GB, > I get a deadlock again. > > What can I do now? > > Thanks > > Anton > If you're not able to get a full dump, a textdump would be enough. In your DDB scripts just remove the 'call doadump' step and you should be done, unless I'm missing something. Please adjust the script as well to include all the informations requested as mentioned in my previous link, e.g. 'show lockedvnods' is not mentioned on the example section of textdump(4) manpage but it could be useful to ease debugging. Thanks for your time, -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri Poincare From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 13:43:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BD8C71D5 for ; Fri, 11 Oct 2013 13:43:27 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ea0-x230.google.com (mail-ea0-x230.google.com [IPv6:2a00:1450:4013:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 55CD125DD for ; Fri, 11 Oct 2013 13:43:27 +0000 (UTC) Received: by mail-ea0-f176.google.com with SMTP id q16so1858644ead.7 for ; Fri, 11 Oct 2013 06:43:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=eYSRh9IAUOmZLn92J3568lp7XjtviFe9TzMgZ/r4bII=; b=QeeZwDUEy5k8SRVokPR+CAVt2Zb0Ho7KJkxTworpOg9n7NFwz9iZcZm9nWQxPrqy5R vK6VT3FMgX0GCJhWVORNeGEEGOsb4I3GB7WLzTCEqkUZiWbbfvWynvXHAWJDfV8GNydU jGAwaHx0Urg4ccV/Loh1C98N/wWe0VEk/XSOFfh2ZXjiVX/MQqoglYsuY5mdF1Cysxm1 HPMaf2whsmeAyHdpIxogSp07LIfqxqGTegY1rowVVS9DXt6Ce3LrGrp3P4QSfotv6Tqs IK7l6GoD/v3m7cT4JU1wObSMJ0P0JgPSZfQD9mhQREyFCf9TxJKnYAoT/JklnxnedNRq cVvQ== X-Received: by 10.14.208.194 with SMTP id q42mr29254276eeo.31.1381499005669; Fri, 11 Oct 2013 06:43:25 -0700 (PDT) Received: from [46.169.90.181] (apn-46-169-90-181.dynamic.gprs.plus.pl. [46.169.90.181]) by mx.google.com with ESMTPSA id z12sm114898575eev.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 06:43:24 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= References: <52571EF6.8010703@gmail.com> <5257DDD1.4070403@gmail.com> Mime-Version: 1.0 (1.0) In-Reply-To: <5257DDD1.4070403@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <08D4D879-C866-4BEB-BB1D-9579A32F1975@FreeBSD.org> X-Mailer: iPhone Mail (11A501) From: =?utf-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2 Date: Fri, 11 Oct 2013 15:43:21 +0200 To: "Mike C." Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 13:43:27 -0000 Dnia 11 pa=C5=BA 2013 o godz. 13:15 "Mike C." napis= a=C5=82(a): >=20 >> On 10/11/13 09:24, Edward Tomasz Napiera=C5=82a wrote: >>> Wiadomo=C5=9B=C4=87 napisana przez Mike C. w dniu 10 pa=C5=BA 2013, o go= dz. 23:41: >>> Hi, >>>=20 >>> I'm running Alpha-2 and wanted to test with iscsi but it seems I can't >>> start iscsid. >>>=20 >>>=20 >>> $ sudo service iscsid onerestart >>> kldload: can't load iscsi: Exec format error >>> /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi >>> /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid >>>=20 >>>=20 >>> dmesg shows: >>> interface icl.1 already present in the KLD 'kernel'! >>> linker_load_file: Unsupported file type >>=20 >> Do you have "device ctl" in your kernel config? If so, >> either remove it (ctl.ko module is automatically loaded >> by ctladm), or add "device iscsi". >=20 > device ctl # CAM Target Layer >=20 > Seems that GENERIC has it by default! I'll remove and recompile! Actually, it got removed from GENERIC in 10 some time ago. From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 14:12:27 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DF284219; Fri, 11 Oct 2013 14:12:27 +0000 (UTC) (envelope-from swills@mouf.net) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 88EEB281E; Fri, 11 Oct 2013 14:12:27 +0000 (UTC) Received: from mouf.net (swills@mouf [199.48.129.64]) by mouf.net (8.14.5/8.14.5) with ESMTP id r9BECGJn018634 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 11 Oct 2013 14:12:21 GMT (envelope-from swills@mouf.net) Received: (from swills@localhost) by mouf.net (8.14.5/8.14.5/Submit) id r9BECGgP018633; Fri, 11 Oct 2013 14:12:16 GMT (envelope-from swills) Date: Fri, 11 Oct 2013 14:12:16 +0000 From: Steve Wills To: Remko Lodder Subject: Re: Fwd: svn commit: r256256 - in head: . etc etc/defaults etc/rc.d share/man/man5 usr.sbin/jail Message-ID: <20131011141214.GA91989@mouf.net> References: <04E9979E-1D97-4AA2-A7AE-F9D8457B3599@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Fri, 11 Oct 2013 14:12:21 +0000 (UTC) X-Spam-Status: No, score=0.0 required=4.5 tests=none autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.8 at mouf.net X-Virus-Status: Clean Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 14:12:27 -0000 I'm having the same issue. Steve On Fri, Oct 11, 2013 at 03:05:51PM +0200, Remko Lodder wrote: > > Dear Current readers, > > Please find issues that I have with the latest /etc/rc.d/jail changes and the use of ezjail. > > Thanks > remko > > > Begin forwarded message: > > > From: Remko Lodder > > Subject: Re: svn commit: r256256 - in head: . etc etc/defaults etc/rc.d share/man/man5 usr.sbin/jail > > Date: October 11, 2013 3:04:12 PM GMT+02:00 > > To: Hiroki Sato > > Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org > > > > > > Hi Hiroki, > > > > On Oct 10, 2013, at 11:32 AM, Hiroki Sato wrote: > > > >> Author: hrs > >> Date: Thu Oct 10 09:32:27 2013 > >> New Revision: 256256 > >> URL: http://svnweb.freebsd.org/changeset/base/256256 > >> > >> Log: > >> - Update rc.d/jail to use a jail(8) configuration file instead of > >> command line options. The "jail__*" rc.conf(5) variables for > >> per-jail configuration are automatically converted to > >> /var/run/jail..conf before the jail(8) utility is invoked. > >> This is transparently backward compatible. > >> > >> - Fix a minor bug in jail(8) which prevented it from returning false > >> when jail -r failed. > >> > > > > Thanks for doing such a massive update. However it seems to break the ezjail utility. > > My jails didn't restart after I upgraded to the most recent -head version > > > > FreeBSD nakur.elvandar.org 10.0-ALPHA6 FreeBSD 10.0-ALPHA6 #7 r256311: Fri Oct 11 13:27:54 CEST 2013 root@nakur.elvandar.org:/usr/obj/usr/src/sys/NAKUR amd64 > > > > If I replace this with an older version, the utility starts and complains about certain things not being done properly. The > > system does not mount devfs nodes anylonger and thus is basically out of function. > > > > I was not expecting this much fallout from this change, others that will be upgrading will loose the ability to start their jails until they can > > resolve this by hand. > > > > Thanks > > Remko > > > >> Approved by: re (glebius) > >> > >> Modified: > >> head/UPDATING > >> head/etc/defaults/rc.conf > >> head/etc/rc.d/jail > >> head/etc/rc.subr > >> head/share/man/man5/rc.conf.5 > >> head/usr.sbin/jail/jail.c > >> > >> Modified: head/UPDATING > >> ============================================================================== > >> --- head/UPDATING Thu Oct 10 07:41:11 2013 (r256255) > >> +++ head/UPDATING Thu Oct 10 09:32:27 2013 (r256256) > >> @@ -31,6 +31,25 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 10 > >> disable the most expensive debugging functionality run > >> "ln -s 'abort:false,junk:false' /etc/malloc.conf".) > >> > >> +20131010: > >> + The rc.d/jail script has been updated to support jail(8) > >> + configuration file. The "jail__*" rc.conf(5) variables > >> + for per-jail configuration are automatically converted to > >> + /var/run/jail..conf before the jail(8) utility is invoked. > >> + This is transparently backward compatible. See below about some > >> + incompatibilities and rc.conf(5) manual page for more details. > >> + > >> + These variables are now deprecated in favor of jail(8) configuration > >> + file. One can use "rc.d/jail config " command to generate > >> + a jail(8) configuration file in /var/run/jail..conf without > >> + running the jail(8) utility. The default pathname of the > >> + configuration file is /etc/jail.conf and can be specified by > >> + using $jail_conf or $jail__conf variables. > >> + > >> + Please note that jail_devfs_ruleset accepts an integer at > >> + this moment. Please consider to rewrite the ruleset name > >> + with an integer. > >> + > >> 20130930: > >> > > -- > /"\ With kind regards, | remko@elvandar.org > \ / Remko Lodder | remko@FreeBSD.org > X FreeBSD | http://www.evilcoder.org > / \ The Power to Serve | Quis custodiet ipsos custodes > From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 14:16:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 32FCA377 for ; Fri, 11 Oct 2013 14:16:03 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 0DECC2850 for ; Fri, 11 Oct 2013 14:16:02 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 07B0E2D803; Fri, 11 Oct 2013 14:15:59 +0000 (UTC) Message-ID: <52580837.4020301@allanjude.com> Date: Fri, 11 Oct 2013 10:16:23 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "O. Hartmann" Subject: Re: FreeBSD 10 and zfsd. References: <5256B761.4050301@gmail.com> <5257A284.2040406@gmail.com> <5257A7C3.8080004@allanjude.com> <20131011102742.581fa352@thor.walstatt.dyndns.org> In-Reply-To: <20131011102742.581fa352@thor.walstatt.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 14:16:03 -0000 On 2013-10-11 04:27, O. Hartmann wrote: > On Fri, 11 Oct 2013 03:24:51 -0400 > Allan Jude wrote: > >> On 2013-10-11 03:02, Johan Hendriks wrote: >>> Johan Hendriks wrote: >>>> When i started using ZFS on FreeBSD I quickly found out that hot >>>> spares are not possible on FreeBSD. >>>> I was told that with zfsd it should be possible and that it would >>>> be included in FreeBSD 10. >>>> >>>> Is there some info about the zfsd function and how it could be >>>> used? >>>> >>>> regards >>>> Johan Hendriks >>>> >>> Thanks all for the explanation and your time >>> A notice in the handbook may be a good thing to let new FreeBSD >>> users know that you can add spares, but that it is not a hot spare. >>> So human action is required to activate the spare. >>> >>> regards >>> Johan Hendriks >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >> That bit is in the zfs handbook project branch, it just isn't >> published yet >> > ... so it isn't visible to the "normal" users. > > I would also appreciate a hint in the man page of zpool(8). Like > "Be aware: A spare declared vdev is not (yet) automatically replacing a > faulty rendered drive. Human action is still required." > > It could save some trouble in prevention. > > Oliver Lyndon Nerenberg attached a patch for the man page earlier in the thread, and I have forwarded that to the docs team -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 13:55:10 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AD8016D2 for ; Fri, 11 Oct 2013 13:55:10 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.upper.net (mail.upper.net [62.75.224.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2EAFD26E4 for ; Fri, 11 Oct 2013 13:55:09 +0000 (UTC) Received: from ubm.strangled.net (mail.upper.net [62.75.224.33]) (authenticated bits=0) by mail.upper.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id r9BDt4wK007534 for ; Fri, 11 Oct 2013 15:55:04 +0200 Received: from ubm.strangled.net ([92.230.221.219] helo=ubm.strangled.net) by ASSP.nospam.UpPeRnEt; 11 Oct 2013 15:55:04 +0200 Date: Fri, 11 Oct 2013 15:55:03 +0200 From: Marc "UBM" Bocklet To: current@freebsd.org Subject: Re: /usr/local/lib /usr/bin/ld: =?ISO-8859-1?Q?=F8:?= invalid DSO for symbol Message-Id: <20131011155503.1ec20b4aa70920beca4b7f98@u-boot-man.de> In-Reply-To: <20131011070556.e31c63fce9d60266c23bda9e@u-boot-man.de> References: <20131010215148.6d4e724952052b8833133264@gmail.com> <20131010215855.GA90129@direwolf.aux.io> <20131011070556.e31c63fce9d60266c23bda9e@u-boot-man.de> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 11 Oct 2013 15:19:40 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 13:55:10 -0000 On Fri, 11 Oct 2013 07:05:56 +0200 Marc "UBM" Bocklet wrote: > > Add the following to the offending ports' Makefile (I am upto 6): > > LDFLAGS+= -ltinfow > > That worked perfectly, going to try it out on the other six offenders > thus evening. Thanks a lot! I am wondering though as to why that workaround is needed now? Bye Marc From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 18:17:27 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1CF47806 for ; Fri, 11 Oct 2013 18:17:27 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 557AC28D8 for ; Fri, 11 Oct 2013 18:17:26 +0000 (UTC) Received: by mail-we0-f180.google.com with SMTP id q59so4538018wes.39 for ; Fri, 11 Oct 2013 11:17:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=qlC8Fvr9azVEuhzWTrOrw9oAoojmgo5wegyxjc+SbYU=; b=BN6B3nca9srUpkCE35blOKzP/0Il6AXKuOsgRWtoru3LC0rLrk3L+ljk2Xpd/+1v8P 8P2iY27cpwkydOOFZdWdpsaHxLpzf6luNTtEuo/zM/MS5rq85U339pZql888kp2MU4q9 p/xEDjzWyZYrEKdTBDSAUwKfpv9MZ+t4rU3XjRJm498ZAsYW9iitsl/I7ZwMGwaWjTkX 7ze8Z7ixAZFsEsVOlLdom9Rb6CGRRI2nGM14aCscuKYGgJH9bof25ikGSwLNqf7OYB90 C731WXQlA5iee/bNvmsXZSVqRlefEh3ajercDjVSrqATsZHlxrro7Y1CCdnbbw+mOomz Pl9A== MIME-Version: 1.0 X-Received: by 10.180.73.109 with SMTP id k13mr4167885wiv.35.1381515444246; Fri, 11 Oct 2013 11:17:24 -0700 (PDT) Sender: maksim.yevmenkin@gmail.com Received: by 10.227.207.129 with HTTP; Fri, 11 Oct 2013 11:17:23 -0700 (PDT) Date: Fri, 11 Oct 2013 11:17:23 -0700 X-Google-Sender-Auth: VLn6r8wS3pVOB9JDH4E_TdriWaw Message-ID: Subject: [rfc] small bioq patch From: Maksim Yevmenkin To: "current@freebsd.org" Content-Type: multipart/mixed; boundary=f46d043891d94e72d404e87b2195 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 18:17:27 -0000 --f46d043891d94e72d404e87b2195 Content-Type: text/plain; charset=ISO-8859-1 hello, i would like to submit the attached bioq patch for review and comments. this is proof of concept. it helps with smoothing disk read service times and arrear to eliminates outliers. please see attached pictures (about a week worth of data) - c034 "control" unmodified system - c044 patched system graphs show max/avg disk read service times for both systems across 36 spinning drives. both systems are relatively busy serving production traffic (about 10 Gbps at peak). grey shaded areas on the graphs represent time when systems are refreshing their content, i.e. disks are both reading and writing at the same time. thanks, max --f46d043891d94e72d404e87b2195 Content-Type: text/plain; charset=US-ASCII; name="bioq.patch.txt" Content-Disposition: attachment; filename="bioq.patch.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hmnqjknu0 SW5kZXg6IGJyYW5jaGVzL2ZyZWVic2QxMC9zcmMvc3lzL2tlcm4vc3Vicl9kaXNrLmMKPT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PQpkaWZmIC11IC1OIC1yMjI4NCAtcjI2OTgKLS0tIGJyYW5jaGVzL2ZyZWVic2QxMC9zcmMv c3lzL2tlcm4vc3Vicl9kaXNrLmMJKC4uLi9zdWJyX2Rpc2suYykJKHJldmlzaW9uIDIyODQpCisr KyBicmFuY2hlcy9mcmVlYnNkMTAvc3JjL3N5cy9rZXJuL3N1YnJfZGlzay5jCSguLi4vc3Vicl9k aXNrLmMpCShyZXZpc2lvbiAyNjk4KQpAQCAtMjEsOCArMjEsMTMgQEAKICNpbmNsdWRlIDxzeXMv YmlvLmg+CiAjaW5jbHVkZSA8c3lzL2NvbmYuaD4KICNpbmNsdWRlIDxzeXMvZGlzay5oPgorI2lu Y2x1ZGUgPHN5cy9zeXNjdGwuaD4KICNpbmNsdWRlIDxnZW9tL2dlb21fZGlzay5oPgogCitzdGF0 aWMgaW50IGJpb3FfYmF0Y2hzaXplID0gMTI4OworU1lTQ1RMX0lOVChfZGVidWcsIE9JRF9BVVRP LCBiaW9xX2JhdGNoc2l6ZSwgQ1RMRkxBR19SVywKKyAgICAmYmlvcV9iYXRjaHNpemUsIDAsICJC SU9RIGJhdGNoIHNpemUiKTsKKwogLyotCiAgKiBEaXNrIGVycm9yIGlzIHRoZSBwcmVmYWNlIHRv IHBsYWludGl2ZSBlcnJvciBtZXNzYWdlcwogICogYWJvdXQgZmFpbGluZyBkaXNrIHRyYW5zZmVy cy4gIEl0IHByaW50cyBtZXNzYWdlcyBvZiB0aGUgZm9ybQpAQCAtMTUwLDYgKzE1NSw4IEBACiAJ VEFJTFFfSU5JVCgmaGVhZC0+cXVldWUpOwogCWhlYWQtPmxhc3Rfb2Zmc2V0ID0gMDsKIAloZWFk LT5pbnNlcnRfcG9pbnQgPSBOVUxMOworCWhlYWQtPnRvdGFsID0gMDsKKwloZWFkLT5iYXRjaGVk ID0gMDsKIH0KIAogdm9pZApAQCAtMTYzLDYgKzE3MCw3IEBACiAJCWhlYWQtPmluc2VydF9wb2lu dCA9IE5VTEw7CiAKIAlUQUlMUV9SRU1PVkUoJmhlYWQtPnF1ZXVlLCBicCwgYmlvX3F1ZXVlKTsK KwloZWFkLT50b3RhbC0tOwogfQogCiB2b2lkCkBAIC0xODEsMTMgKzE4OSwxNiBAQAogCWlmICho ZWFkLT5pbnNlcnRfcG9pbnQgPT0gTlVMTCkKIAkJaGVhZC0+bGFzdF9vZmZzZXQgPSBicC0+Ymlv X29mZnNldDsKIAlUQUlMUV9JTlNFUlRfSEVBRCgmaGVhZC0+cXVldWUsIGJwLCBiaW9fcXVldWUp OworCWhlYWQtPnRvdGFsKys7CiB9CiAKIHZvaWQKIGJpb3FfaW5zZXJ0X3RhaWwoc3RydWN0IGJp b19xdWV1ZV9oZWFkICpoZWFkLCBzdHJ1Y3QgYmlvICpicCkKIHsKIAogCVRBSUxRX0lOU0VSVF9U QUlMKCZoZWFkLT5xdWV1ZSwgYnAsIGJpb19xdWV1ZSk7CisJaGVhZC0+dG90YWwrKzsKKwloZWFk LT5iYXRjaGVkID0gMDsKIAloZWFkLT5pbnNlcnRfcG9pbnQgPSBicDsKIAloZWFkLT5sYXN0X29m ZnNldCA9IGJwLT5iaW9fb2Zmc2V0OwogfQpAQCAtMjQ2LDYgKzI1NywxMSBAQAogCQlyZXR1cm47 CiAJfQogCisJaWYgKGJpb3FfYmF0Y2hzaXplID4gMCAmJiBoZWFkLT5iYXRjaGVkID4gYmlvcV9i YXRjaHNpemUpIHsKKwkJYmlvcV9pbnNlcnRfdGFpbChoZWFkLCBicCk7CisJCXJldHVybjsKKwl9 CisKIAlwcmV2ID0gTlVMTDsKIAlrZXkgPSBiaW9xX2Jpb19rZXkoaGVhZCwgYnApOwogCWN1ciA9 IFRBSUxRX0ZJUlNUKCZoZWFkLT5xdWV1ZSk7CkBAIC0yNjQsNCArMjgwLDcgQEAKIAkJVEFJTFFf SU5TRVJUX0hFQUQoJmhlYWQtPnF1ZXVlLCBicCwgYmlvX3F1ZXVlKTsKIAllbHNlCiAJCVRBSUxR X0lOU0VSVF9BRlRFUigmaGVhZC0+cXVldWUsIHByZXYsIGJwLCBiaW9fcXVldWUpOworCisJaGVh ZC0+dG90YWwrKzsKKwloZWFkLT5iYXRjaGVkKys7CiB9CkluZGV4OiBicmFuY2hlcy9mcmVlYnNk MTAvc3JjL3N5cy9zeXMvYmlvLmgKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpkaWZmIC11IC1OIC1yMjI4NCAtcjI2OTgK LS0tIGJyYW5jaGVzL2ZyZWVic2QxMC9zcmMvc3lzL3N5cy9iaW8uaAkoLi4uL2Jpby5oKQkocmV2 aXNpb24gMjI4NCkKKysrIGJyYW5jaGVzL2ZyZWVic2QxMC9zcmMvc3lzL3N5cy9iaW8uaAkoLi4u L2Jpby5oKQkocmV2aXNpb24gMjY5OCkKQEAgLTEyOSw2ICsxMjksOCBAQAogCVRBSUxRX0hFQUQo YmlvX3F1ZXVlLCBiaW8pIHF1ZXVlOwogCW9mZl90IGxhc3Rfb2Zmc2V0OwogCXN0cnVjdAliaW8g Kmluc2VydF9wb2ludDsKKwlpbnQgdG90YWw7CisJaW50IGJhdGNoZWQ7CiB9OwogCiBleHRlcm4g c3RydWN0IHZtX21hcCAqYmlvX3RyYW5zaWVudF9tYXA7Cg== --f46d043891d94e72d404e87b2195-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 19:25:08 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 407A2A5B; Fri, 11 Oct 2013 19:25:08 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) by mx1.freebsd.org (Postfix) with ESMTP id 19D792CC4; Fri, 11 Oct 2013 19:25:08 +0000 (UTC) Received: from latitude.home.vangyzen.net (173-20-209-204.client.mchsi.com [173.20.209.204]) by smtp.vangyzen.net (Postfix) with ESMTP id D58025641F; Fri, 11 Oct 2013 14:25:06 -0500 (CDT) Message-ID: <52585093.1090609@vangyzen.net> Date: Fri, 11 Oct 2013 14:25:07 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Maksim Yevmenkin Subject: Re: [rfc] small bioq patch References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 19:25:08 -0000 Maksim, The graphs were not attached. Perhaps the list stripped them. Could you post them on the web instead? Thanks, Eric On 10/11/2013 01:17 PM, Maksim Yevmenkin wrote: > hello, > > i would like to submit the attached bioq patch for review and > comments. this is proof of concept. it helps with smoothing disk read > service times and arrear to eliminates outliers. please see attached > pictures (about a week worth of data) > > - c034 "control" unmodified system > - c044 patched system > > graphs show max/avg disk read service times for both systems across 36 > spinning drives. both systems are relatively busy serving production > traffic (about 10 Gbps at peak). grey shaded areas on the graphs > represent time when systems are refreshing their content, i.e. disks > are both reading and writing at the same time. > > thanks, > max > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 19:33:32 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F4158DA0 for ; Fri, 11 Oct 2013 19:33:31 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9258D2D7B for ; Fri, 11 Oct 2013 19:33:31 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id m15so1377452wgh.3 for ; Fri, 11 Oct 2013 12:33:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=4HRNfk+AfvxHZrST2tnFbn7yF2dbCIkGVuDualeUDyY=; b=zZFWscYmeMlkzMbZpYBFq4bGC5vmNynXdzm5FzxqecW/AD82rqw2LSliQdfqf/cyof SsjbaQuiyF2MLyMOx9R18YTrai/2JpWL6McqHpvUFMLiUBOcwI+r9bYYzXe1wNBlJYIA zdy/rj5o4TAPU3loPHqswxnlmu4w51h8Jg62+nOupArQ4HQWVC8Gqp2UxMBrBg39ZR5q jSkWviOxRrAldekKQj3PIE55Qotgx82YiPSKhJQPQ9HUJGIjmn74WBFXBhMMiU3Lj9vZ DimRxo2Ww3nlokw9yiRWHm0KAahFULWecQs6bQuJZBJ6FKYh2tzz3QzmPMabIcVp5gWI mt0A== MIME-Version: 1.0 X-Received: by 10.180.189.49 with SMTP id gf17mr4477809wic.23.1381520009988; Fri, 11 Oct 2013 12:33:29 -0700 (PDT) Sender: maksim.yevmenkin@gmail.com Received: by 10.227.207.129 with HTTP; Fri, 11 Oct 2013 12:33:29 -0700 (PDT) In-Reply-To: <52585093.1090609@vangyzen.net> References: <52585093.1090609@vangyzen.net> Date: Fri, 11 Oct 2013 12:33:29 -0700 X-Google-Sender-Auth: o9mejv6Dcd9TWxizDgF6XBL0Dyo Message-ID: Subject: Re: [rfc] small bioq patch From: Maksim Yevmenkin To: Eric van Gyzen Content-Type: text/plain; charset=ISO-8859-1 Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 19:33:32 -0000 On Fri, Oct 11, 2013 at 12:25 PM, Eric van Gyzen wrote: > Maksim, > > The graphs were not attached. Perhaps the list stripped them. Could you > post them on the web instead? err... sorry about it.. please try http://people.freebsd.org/~emax/c034.png http://people.freebsd.org/~emax/c044.png thanks max >> hello, >> >> i would like to submit the attached bioq patch for review and >> comments. this is proof of concept. it helps with smoothing disk read >> service times and arrear to eliminates outliers. please see attached >> pictures (about a week worth of data) >> >> - c034 "control" unmodified system >> - c044 patched system >> >> graphs show max/avg disk read service times for both systems across 36 >> spinning drives. both systems are relatively busy serving production >> traffic (about 10 Gbps at peak). grey shaded areas on the graphs >> represent time when systems are refreshing their content, i.e. disks >> are both reading and writing at the same time. >> >> thanks, >> max From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 19:57:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 42735595 for ; Fri, 11 Oct 2013 19:57:23 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0BFC52F0A for ; Fri, 11 Oct 2013 19:57:22 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id h16so2748446oag.24 for ; Fri, 11 Oct 2013 12:57:21 -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=PDBMFgC5jDsvv+ftcXRwfXWS/mAL/Qy6+H89GDhEB4g=; b=ClXvn85qS+HSYjPuzS/J94G4/PvHrkmPagsG4+hRuD8smvkwd0jCOcERUfBvzFw3nh SS3gznyaX2XD2CC8q7g/PR6ZpJIL6Z6ix+SSgaF0GXTqnZlGbK3hdR5TxBi60Ohav67Q BBFP/yhhKVQscbR70IlmQMaGCwRAIK9B+16fbHEYVXG2unw/Z/j8P4QF5F8EK8wn0+Qf 5n65fVODx9yTvLFuCKhUgqAhDWJ8E/j4MRD/b938wbkh1bQvrUKhdIs7vF6qVmVhRi4j CNx6QJRGuabgbD8ApccH4KRaIsLIrQytb4ce2Zl1uKstlFExpVASQ/Aqqj89KadipBNM dJIw== MIME-Version: 1.0 X-Received: by 10.60.63.116 with SMTP id f20mr15677679oes.29.1381521441666; Fri, 11 Oct 2013 12:57:21 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Fri, 11 Oct 2013 12:57:21 -0700 (PDT) In-Reply-To: <52580837.4020301@allanjude.com> References: <5256B761.4050301@gmail.com> <5257A284.2040406@gmail.com> <5257A7C3.8080004@allanjude.com> <20131011102742.581fa352@thor.walstatt.dyndns.org> <52580837.4020301@allanjude.com> Date: Fri, 11 Oct 2013 15:57:21 -0400 Message-ID: Subject: Re: FreeBSD 10 and zfsd. From: Outback Dingo To: Allan Jude Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org, "O. Hartmann" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 19:57:23 -0000 On Fri, Oct 11, 2013 at 10:16 AM, Allan Jude wrote: > On 2013-10-11 04:27, O. Hartmann wrote: > > On Fri, 11 Oct 2013 03:24:51 -0400 > > Allan Jude wrote: > > > >> On 2013-10-11 03:02, Johan Hendriks wrote: > >>> Johan Hendriks wrote: > >>>> When i started using ZFS on FreeBSD I quickly found out that hot > >>>> spares are not possible on FreeBSD. > >>>> I was told that with zfsd it should be possible and that it would > >>>> be included in FreeBSD 10. > >>>> > >>>> Is there some info about the zfsd function and how it could be > >>>> used? > >>>> > >>>> regards > >>>> Johan Hendriks > >>>> > >>> Thanks all for the explanation and your time > >>> A notice in the handbook may be a good thing to let new FreeBSD > >>> users know that you can add spares, but that it is not a hot spare. > >>> So human action is required to activate the spare. > >>> > >>> regards > >>> Johan Hendriks > >>> _______________________________________________ > >>> freebsd-current@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> To unsubscribe, send any mail to > >>> "freebsd-current-unsubscribe@freebsd.org" > >> That bit is in the zfs handbook project branch, it just isn't > >> published yet > >> > > ... so it isn't visible to the "normal" users. > > > > I would also appreciate a hint in the man page of zpool(8). Like > > "Be aware: A spare declared vdev is not (yet) automatically replacing a > > faulty rendered drive. Human action is still required." > > > > It could save some trouble in prevention. > > > > Oliver > Lyndon Nerenberg attached a patch for the man page earlier in the > thread, and I have forwarded that to the docs team > > I was under the impression rc_setvar was dropped from rc.d scripts i believe it should be rcvar=`zfsd` for /etc/rc.d/zfsd > -- > Allan Jude > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 20:10:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6373CEF7 for ; Fri, 11 Oct 2013 20:10:49 +0000 (UTC) (envelope-from supportme@ukr.net) Received: from frv199.fwdcdn.com (frv199.fwdcdn.com [212.42.77.199]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 097B42017 for ; Fri, 11 Oct 2013 20:10:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-Id:To:Subject:From:Date; bh=pCOPLQasDBCevanZBjVeYBkmneO9OkZITGvmLelrOiA=; b=EejQRynQ+PAxm31IKcwQTz+qn4zZ3a0j5HKQUmYGr/wdVLAM9fX7ZJhrbBesw2TrufVx86gSdT6/IRx6CLq3fn/jZkFPjCMG6JmBo9KqEtmqq7Jjvi5MvDuPyymfntthS+KEiiA7HNUIL8TL3oehU/bwt9443QVcpNr3hUguHQA=; Received: from [10.10.10.45] (helo=frv45.ukr.net) by frv199.fwdcdn.com with smtp ID 1VUj2p-0006gJ-5t for freebsd-current@freebsd.org; Fri, 11 Oct 2013 23:10:43 +0300 Date: Fri, 11 Oct 2013 23:10:36 +0300 From: Dmitriy Makarov Subject: vmstat -z: zfs related failures on r255173 To: freebsd-current@freebsd.org X-Mailer: freemail.ukr.net 5.0 Message-Id: <1381521443.74219922.8eyuscyw@frv45.ukr.net> MIME-Version: 1.0 Received: from supportme@ukr.net by frv45.ukr.net; Fri, 11 Oct 2013 23:10:40 +0300 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 20:10:49 -0000 Hi all On CURRENT r255173 we have some interesting values from vmstat -z : REQ = FAIL [server]# vmstat -z ITEM                   SIZE  LIMIT     USED     FREE      REQ FAIL SLEEP ....... skipped.... NCLNODE:                528,      0,       0,       0,       0,   0,   0 space_seg_cache:         64,      0,  289198,  299554,25932081,25932081,   0 zio_cache:              944,      0,   37512,   50124,1638254119,1638254119,   0 zio_link_cache:          48,      0,   50955,   38104,1306418638,1306418638,   0 sa_cache:                80,      0,   63694,      56,  198643,198643,   0 dnode_t:                864,      0,  128813,       3,  184863,184863,   0 dmu_buf_impl_t:         224,      0, 1610024,  314631,157119686,157119686,   0 arc_buf_hdr_t:          216,      0,82949975,   56107,156352659,156352659,   0 arc_buf_t:               72,      0, 1586866,  314374,158076670,158076670,   0 zil_lwb_cache:          192,      0,    6354,    7526, 2486242,2486242,   0 zfs_znode_cache:        368,      0,   63694,      16,  198643,198643,   0 ..... skipped ...... Can anybody explain this strange failures in zfs related parameters in vmstat, can we do something with this and is this really bad signal? Thanks! From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 20:27:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0BA48CF1 for ; Fri, 11 Oct 2013 20:27:44 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-qe0-x235.google.com (mail-qe0-x235.google.com [IPv6:2607:f8b0:400d:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C081B215F for ; Fri, 11 Oct 2013 20:27:43 +0000 (UTC) Received: by mail-qe0-f53.google.com with SMTP id cy11so3560246qeb.40 for ; Fri, 11 Oct 2013 13:27:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HM4X6LdlMMB8UHzNzhj9A56O+aSxGw2V6QwBEwsIzfM=; b=xauP9T9aOYOiAigZ91UtxcWmCbeHaC4e8GIIxNTOpGMYiqfZ1avdIQ5FNzCUsjlfPr bi/mEl+3ZxeV3vjgzN6yJj8O4bVsUcFcRMRfhkEVgyomsshnbd4/PPBib8ayECg25Nor UANxnF58UUEKIYS5nauDlaHFDecpsw7cFvWEJleSjdE0TuzDQ15ju6lQozwdimcqNEjH AtLw5Tr9BD+rRqrQHIw/q50sB08yPc63avW9+Xn5tJbUcL5JKeGP+/z7Clc/91ooaMWh IXxI81HVU06SZfDinPn9ni2nfDG9d1oqSxyg6l2QUHLrTnOFWixV2nAT2jxjgqJ8wI4K A1qg== MIME-Version: 1.0 X-Received: by 10.49.50.232 with SMTP id f8mr10420075qeo.63.1381523262876; Fri, 11 Oct 2013 13:27:42 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.49.39.97 with HTTP; Fri, 11 Oct 2013 13:27:42 -0700 (PDT) In-Reply-To: References: <5256B761.4050301@gmail.com> <5257A284.2040406@gmail.com> <5257A7C3.8080004@allanjude.com> <20131011102742.581fa352@thor.walstatt.dyndns.org> <52580837.4020301@allanjude.com> Date: Fri, 11 Oct 2013 14:27:42 -0600 X-Google-Sender-Auth: T6VbZUIZgBfU0SdE-fbHS1IIaD8 Message-ID: Subject: Re: FreeBSD 10 and zfsd. From: Alan Somers To: Outback Dingo Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD CURRENT , "O. Hartmann" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 20:27:44 -0000 On Fri, Oct 11, 2013 at 1:57 PM, Outback Dingo wrote: > On Fri, Oct 11, 2013 at 10:16 AM, Allan Jude wrote: > >> On 2013-10-11 04:27, O. Hartmann wrote: >> > On Fri, 11 Oct 2013 03:24:51 -0400 >> > Allan Jude wrote: >> > >> >> On 2013-10-11 03:02, Johan Hendriks wrote: >> >>> Johan Hendriks wrote: >> >>>> When i started using ZFS on FreeBSD I quickly found out that hot >> >>>> spares are not possible on FreeBSD. >> >>>> I was told that with zfsd it should be possible and that it would >> >>>> be included in FreeBSD 10. >> >>>> >> >>>> Is there some info about the zfsd function and how it could be >> >>>> used? >> >>>> >> >>>> regards >> >>>> Johan Hendriks >> >>>> >> >>> Thanks all for the explanation and your time >> >>> A notice in the handbook may be a good thing to let new FreeBSD >> >>> users know that you can add spares, but that it is not a hot spare. >> >>> So human action is required to activate the spare. >> >>> >> >>> regards >> >>> Johan Hendriks >> >>> _______________________________________________ >> >>> freebsd-current@freebsd.org mailing list >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> >>> To unsubscribe, send any mail to >> >>> "freebsd-current-unsubscribe@freebsd.org" >> >> That bit is in the zfs handbook project branch, it just isn't >> >> published yet >> >> >> > ... so it isn't visible to the "normal" users. >> > >> > I would also appreciate a hint in the man page of zpool(8). Like >> > "Be aware: A spare declared vdev is not (yet) automatically replacing a >> > faulty rendered drive. Human action is still required." >> > >> > It could save some trouble in prevention. >> > >> > Oliver >> Lyndon Nerenberg attached a patch for the man page earlier in the >> thread, and I have forwarded that to the docs team >> >> > I was under the impression rc_setvar was dropped from rc.d scripts > > i believe it should be > > > rcvar=`zfsd` > > for /etc/rc.d/zfsd Good catch. I obviously still have a lot of merging to do. > > >> -- >> Allan Jude >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 20:35:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 863C51C6; Fri, 11 Oct 2013 20:35:48 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 40CFC21F7; Fri, 11 Oct 2013 20:35:48 +0000 (UTC) Received: by mail-ob0-f174.google.com with SMTP id wm4so3169848obc.33 for ; Fri, 11 Oct 2013 13:35:47 -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=so3TUb2n+uz20/+Gk2VRk6ugAPGLUqKOAhU8LTTbO7s=; b=vmNQOjN2TKCe1BA2R6xeHbTGmhy30VFSLGEUsKxDco6x33FrVKL8a+7sFbQnmDCqzU zPgJeJX/5RZmOgSSxUT+oiMNQcI5egY3teNv29FcDwNdWcHwYu/zW2i5fWV2RmqMengR a0LpP3K7SlIDus63LcGVwDPwXD449FNywESTWm8Fob6ZaMKcN7T8rjuuV13D4W4Vhz5K 6gfDeC1fKLJYMmvuNLz8Fxvp0KyzXtNH25MEjC3AcMHSWKuNSssvPnARtrPtOKM613ka lfLxpU+tFyYqViuEY44aeIxEFbx2Hced0kJjT/1+RtGLtNTd40Iw/oCsiBR77OkVTHjK cAHw== MIME-Version: 1.0 X-Received: by 10.60.45.65 with SMTP id k1mr3149473oem.48.1381523747485; Fri, 11 Oct 2013 13:35:47 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Fri, 11 Oct 2013 13:35:47 -0700 (PDT) In-Reply-To: References: <5256B761.4050301@gmail.com> <5257A284.2040406@gmail.com> <5257A7C3.8080004@allanjude.com> <20131011102742.581fa352@thor.walstatt.dyndns.org> <52580837.4020301@allanjude.com> Date: Fri, 11 Oct 2013 16:35:47 -0400 Message-ID: Subject: Re: FreeBSD 10 and zfsd. From: Outback Dingo To: Alan Somers Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD CURRENT , "O. Hartmann" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 20:35:48 -0000 On Fri, Oct 11, 2013 at 4:27 PM, Alan Somers wrote: > On Fri, Oct 11, 2013 at 1:57 PM, Outback Dingo > wrote: > > On Fri, Oct 11, 2013 at 10:16 AM, Allan Jude > wrote: > > > >> On 2013-10-11 04:27, O. Hartmann wrote: > >> > On Fri, 11 Oct 2013 03:24:51 -0400 > >> > Allan Jude wrote: > >> > > >> >> On 2013-10-11 03:02, Johan Hendriks wrote: > >> >>> Johan Hendriks wrote: > >> >>>> When i started using ZFS on FreeBSD I quickly found out that hot > >> >>>> spares are not possible on FreeBSD. > >> >>>> I was told that with zfsd it should be possible and that it would > >> >>>> be included in FreeBSD 10. > >> >>>> > >> >>>> Is there some info about the zfsd function and how it could be > >> >>>> used? > >> >>>> > >> >>>> regards > >> >>>> Johan Hendriks > >> >>>> > >> >>> Thanks all for the explanation and your time > >> >>> A notice in the handbook may be a good thing to let new FreeBSD > >> >>> users know that you can add spares, but that it is not a hot spare. > >> >>> So human action is required to activate the spare. > >> >>> > >> >>> regards > >> >>> Johan Hendriks > >> >>> _______________________________________________ > >> >>> freebsd-current@freebsd.org mailing list > >> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> >>> To unsubscribe, send any mail to > >> >>> "freebsd-current-unsubscribe@freebsd.org" > >> >> That bit is in the zfs handbook project branch, it just isn't > >> >> published yet > >> >> > >> > ... so it isn't visible to the "normal" users. > >> > > >> > I would also appreciate a hint in the man page of zpool(8). Like > >> > "Be aware: A spare declared vdev is not (yet) automatically replacing > a > >> > faulty rendered drive. Human action is still required." > >> > > >> > It could save some trouble in prevention. > >> > > >> > Oliver > >> Lyndon Nerenberg attached a patch for the man page earlier in the > >> thread, and I have forwarded that to the docs team > >> > >> > > I was under the impression rc_setvar was dropped from rc.d scripts > > > > i believe it should be > > > > > > rcvar=`zfsd` > > > > for /etc/rc.d/zfsd > > Good catch. I obviously still have a lot of merging to do. > > also in my diff against CURRENT from your updated SVN, i found the patch created a /usr/src/rc.d/zfsd instead of /usr/src/etc/rc.d.... a bit odd.... and /usr/src/sbin/zfsd instead of /usr/src/cddl/sbin ... however the Makefiles were correctly patched for both in the proper locations... though IMHO i was tired... might have been me.... i moved them to the proper places when i realized they were built on the first make world kernel :P might want to double check..... for others sanity.... > > > > > >> -- > >> Allan Jude > >> > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > >> > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 21:52:11 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C61D2118; Fri, 11 Oct 2013 21:52:11 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8A7C026C1; Fri, 11 Oct 2013 21:52:11 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r9BLqAMA067462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Oct 2013 14:52:10 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r9BLqAOs067461; Fri, 11 Oct 2013 14:52:10 -0700 (PDT) (envelope-from jmg) Date: Fri, 11 Oct 2013 14:52:10 -0700 From: John-Mark Gurney To: Maksim Yevmenkin Subject: Re: [rfc] small bioq patch Message-ID: <20131011215210.GY56872@funkthat.com> Mail-Followup-To: Maksim Yevmenkin , "current@freebsd.org" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Fri, 11 Oct 2013 14:52:10 -0700 (PDT) Cc: "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 21:52:11 -0000 Maksim Yevmenkin wrote this message on Fri, Oct 11, 2013 at 11:17 -0700: > i would like to submit the attached bioq patch for review and > comments. this is proof of concept. it helps with smoothing disk read > service times and arrear to eliminates outliers. please see attached > pictures (about a week worth of data) > > - c034 "control" unmodified system > - c044 patched system Can you describe how you got this data? Were you using the gstat code or some other code? Also, was your control system w/ the patch, but w/ the sysctl set to zero to possibly eliminate any code alignment issues? > graphs show max/avg disk read service times for both systems across 36 > spinning drives. both systems are relatively busy serving production > traffic (about 10 Gbps at peak). grey shaded areas on the graphs > represent time when systems are refreshing their content, i.e. disks > are both reading and writing at the same time. Can you describe why you think this change makes an improvement? Unless you're running 10k or 15k RPM drives, 128 seems like a large number.. as that's about halve number of IOPs that a normal HD handles in a second.. I assume you must be regularly seeing queue depths of 128+ for this code to make a difference, do you see that w/ gstat? Also, do you see a similar throughput of the system? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 22:10:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 12C8776B for ; Fri, 11 Oct 2013 22:10:28 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id D11DE2794 for ; Fri, 11 Oct 2013 22:10:27 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:40206] helo=localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 0E/82-01315-25778525; Fri, 11 Oct 2013 22:10:26 +0000 Date: Fri, 11 Oct 2013 22:10:26 +0000 Message-ID: <0E.82.01315.25778525@cdptpa-oedge03> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: What happened to nslookup? X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 22:10:28 -0000 I thought I sent this message yesterday, but couldn't find it in the downloaded list messages, so maybe I forgot. Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one supposed to use in its place? I see nslookup is in FreeBSD 9.2, but why not in -current? There has been plenty of dispute in recent days on removing rcs from base, subsequently resolved in keeping rcs, but no publicity on removing nslookup. There was no reference to nslookup in $SRCDIR/UPDATING for FreeBSD-current. I looked in $SRCDIR/usr.bin for both 9.2 and current, and nslookup was in 9.2 but not current. Tom From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 22:13:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 114EA8B9 for ; Fri, 11 Oct 2013 22:13:06 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CD92127E3 for ; Fri, 11 Oct 2013 22:13:05 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.7/8.14.7) with ESMTP id r9BMD2XP044468; Fri, 11 Oct 2013 15:13:02 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.7/8.14.7/Submit) id r9BMD2Yq044467; Fri, 11 Oct 2013 15:13:02 -0700 (PDT) (envelope-from david) Date: Fri, 11 Oct 2013 15:13:02 -0700 From: David Wolfskill To: Thomas Mueller Subject: Re: What happened to nslookup? Message-ID: <20131011221302.GH1611@albert.catwhisker.org> References: <0E.82.01315.25778525@cdptpa-oedge03> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MT9P10dJYE2MyE4L" Content-Disposition: inline In-Reply-To: <0E.82.01315.25778525@cdptpa-oedge03> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 22:13:06 -0000 --MT9P10dJYE2MyE4L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 11, 2013 at 10:10:26PM +0000, Thomas Mueller wrote: > ... > Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is on= e supposed to use in its place? > .... Use "host." nslookup was part of BIND, and has been deprecated for years (IIRC). Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --MT9P10dJYE2MyE4L Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEUEARECAAYFAlJYd+4ACgkQmprOCmdXAD3ORwCY+wIGvQXXOfIZz2FfRR2tm9Tj PgCeOI2m81gShf1uH6V+B2/Qaw3p3tE= =r8Vl -----END PGP SIGNATURE----- --MT9P10dJYE2MyE4L-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 22:39:56 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 42AD9F9B; Fri, 11 Oct 2013 22:39:56 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 153F428FC; Fri, 11 Oct 2013 22:39:56 +0000 (UTC) Received: by mail-pb0-f51.google.com with SMTP id jt11so4882568pbb.10 for ; Fri, 11 Oct 2013 15:39:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=OMHKXy4+Q/EKfFE134rwlvY3yKQoyC7YOyJoEtDkF2M=; b=ebcCR5kuCNvLrya8tXm1zwdG1mW+lpyhtpzKTW2df4UDGG7e4eY/QptM4slh+7C//u OPELdQ55IGCpTBYEY98pJYeeF4rna6lkGy/eVxWKrVMudja0GazdWO+E5fiB2J4uD6I7 eVhoD3uCUIGoVcYIxYAym1PygRULESRXvDLwG4fNbksXD7wexVqpFF02JwhxlEgDxxB5 RGAWCdmrBrayVidQqJsW0JYW8KwJfWTxrlyAg4GUREtxV3ibnQYS99lqW06vjsdl2Sae QlOjmaKsai+ic6jZeywzcil/Z3U1bmD0Kz2Ofl950in+6PKeghUtIgykmoko5OgC+hDS TpSQ== X-Received: by 10.68.131.165 with SMTP id on5mr17683199pbb.165.1381531195557; Fri, 11 Oct 2013 15:39:55 -0700 (PDT) Received: from [192.168.1.4] (pool-71-118-241-194.lsanca.fios.verizon.net. [71.118.241.194]) by mx.google.com with ESMTPSA id ye1sm72875874pab.19.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 15:39:54 -0700 (PDT) References: <20131011215210.GY56872@funkthat.com> Mime-Version: 1.0 (1.0) In-Reply-To: <20131011215210.GY56872@funkthat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <72DA2C4F-44F0-456D-8679-A45CE617F8E6@gmail.com> X-Mailer: iPad Mail (11A501) From: Maksim Yevmenkin Subject: Re: [rfc] small bioq patch Date: Fri, 11 Oct 2013 15:39:53 -0700 To: John-Mark Gurney Cc: Maksim Yevmenkin , "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 22:39:56 -0000 > On Oct 11, 2013, at 2:52 PM, John-Mark Gurney wrote: >=20 > Maksim Yevmenkin wrote this message on Fri, Oct 11, 2013 at 11:17 -0700: >> i would like to submit the attached bioq patch for review and >> comments. this is proof of concept. it helps with smoothing disk read >> service times and arrear to eliminates outliers. please see attached >> pictures (about a week worth of data) >>=20 >> - c034 "control" unmodified system >> - c044 patched system >=20 > Can you describe how you got this data? Were you using the gstat > code or some other code? Yes, it's basically gstat data.=20 > Also, was your control system w/ the patch, but w/ the sysctl set to > zero to possibly eliminate any code alignment issues? Both systems use the same code base and build. Patched system has patch incl= uded, "control" system does not have the patch. I can rerun my tests with sy= sctl set to zero and use it as "control". So, the answer to your question is= "no".=20 >> graphs show max/avg disk read service times for both systems across 36 >> spinning drives. both systems are relatively busy serving production >> traffic (about 10 Gbps at peak). grey shaded areas on the graphs >> represent time when systems are refreshing their content, i.e. disks >> are both reading and writing at the same time. >=20 > Can you describe why you think this change makes an improvement? Unless > you're running 10k or 15k RPM drives, 128 seems like a large number.. as > that's about halve number of IOPs that a normal HD handles in a second.. Our (Netflix) load is basically random disk io. We have tweaked the system t= o ensure that our io path is "wide" enough, I.e. We read 1mb per disk io for= majority of the requests. However offsets we read from are all over the pla= ce. It appears that we are getting into situation where larger offsets are g= etting delayed because smaller offsets are "jumping" ahead of them. Forcing b= ioq insert tail operation and effectively moving insertion point seems to he= lp avoiding getting into this situation. And, no. We don't use 10k or 15k dr= ives. Just regular enterprise 7200 sata drives.=20 > I assume you must be regularly seeing queue depths of 128+ for this > code to make a difference, do you see that w/ gstat? No, we don't see large (128+) queue sizes in gstat data. The way I see it, w= e don't have to have deep queue here. We could just have a steady stream of i= o requests where new, smaller, offsets consistently "jumping" ahead of older= , larger offset. In fact gstat data show shallow queue of 5 or less items. > Also, do you see a similar throughput of the system? Yes. We do see almost identical throughput from both systems. I have not pu= shed the system to its limit yet, but having much smoother disk read service= time is important for us because we use it as one of the components of syst= em health metrics. We also need to ensure that disk io request is actually d= ispatched to the disk in a timely manner.=20 Thanks Max From owner-freebsd-current@FreeBSD.ORG Fri Oct 11 23:23:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E7BC89A5 for ; Fri, 11 Oct 2013 23:23:48 +0000 (UTC) (envelope-from sean_bruno@yahoo.com) Received: from nm27-vm1.bullet.mail.bf1.yahoo.com (nm27-vm1.bullet.mail.bf1.yahoo.com [98.139.213.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 87D312AF7 for ; Fri, 11 Oct 2013 23:23:48 +0000 (UTC) Received: from [66.196.81.171] by nm27.bullet.mail.bf1.yahoo.com with NNFMP; 11 Oct 2013 23:23:47 -0000 Received: from [68.142.230.73] by tm17.bullet.mail.bf1.yahoo.com with NNFMP; 11 Oct 2013 23:23:47 -0000 Received: from [127.0.0.1] by smtp230.mail.bf1.yahoo.com with NNFMP; 11 Oct 2013 23:23:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1381533827; bh=uKi7sRfLxIsEM8Y3+R+2PISxo4/8jJOy0++6edAvD54=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Subject:From:Reply-To:To:Content-Type:Date:Message-ID:Mime-Version:X-Mailer; b=hLXBx/ahW+InV5sqSWxv9R8txDIWWCyKEpy7km3z1c6QESlw4hNPfT3M1xnvBAUe7KVi0BGXTliYZI0no87Ed5NJWP2RAZBBYcKetDfMrKfKD4s5A8weZeTQ5DQSA2WcRm1M/0lQYvTqywBraDGjL8H4AOi5QrDdSsXItobtK5s= X-Yahoo-Newman-Id: 125736.37121.bm@smtp230.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: pbBradcVM1kxYRN7jhs.R39mjwR9gKqNu1u5uY0Zw7dFlsG hXc81Ntkz6Y8SxqJETMpVhMjSFft2D1DRfkzvorq7KYWWxghIVGnjqcUPsle vwMXXV1hZu6BJlpkMYNChU8K_wrEru6KFTqTzZ1ZrqAYaidUMponNQ_AZ2eX arJyBPCzSKF416nuc3xxwQkVt6fsneZer3P_sGSbSTFudrJBBZsCCTf1IejQ ain84MOQdSLZMSOOpoJEZmu2_aCbxqu3P3RSoqlD763JsZG7SaHfGw52XWpE Zpxv5ycwSTjki2Dff5ZkpB9nlHPCgTSQwZzFghFr_zWP_eO2wagYYEjMiL0q f4zjO3TlwKurnTKwv4UHa0MQylh8qxFnaDs5lp6uSIDT4v41L_iNLoYpjWyh pKnwOrHoH6JqOPo5bGYLDEqI26aVYSC_iSFI3xylycO1r6W2SR8JSRQc57YH dhB3k5Xuln4pEtuD5GWM_8JSKGvC0iVFs7Al5Q3oPycrjoB4MHfuVXldri7m hZCOV1JFHwcBm.nk3ZQvftiZGq.hxuYjrCPH.tV894gfPidT8OK8qwfmw0nT sU5Q_ryATVAcOdP5o5v27zEZy.9tw6qxX411n0ThmQ23tleCQcBJdXiPaoBa GFJf36kax3U6gJAqtvg-- X-Yahoo-SMTP: u5BKR6OswBC_iZJVfGRoMkTIpc8pEA4- X-Rocket-Received: from [10.73.160.242] (sean_bruno@209.131.62.116 with ) by smtp230.mail.bf1.yahoo.com with SMTP; 11 Oct 2013 23:23:47 +0000 UTC Subject: i386-wine + 10.0 From: Sean Bruno To: "freebsd-current@freebsd.org" Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-QNET/fjk60dgsGCL49lb" Date: Fri, 11 Oct 2013 16:23:45 -0700 Message-ID: <1381533825.2273.0.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: sbruno@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 23:23:49 -0000 --=-QNET/fjk60dgsGCL49lb Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I think I built everything according to https://wiki.freebsd.org/i386-Wine and got a package out of it. I think I missed something obvious here. When I try to run simple windows things I get: err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": /usr/local/lib/libXext.so.6: unsupported file layout Application tried to create a window, but no driver could be loaded. Unknown error (127). Application tried to create a window, but no driver could be loaded. Unknown error (127). err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": /usr/local/lib/libXext.so.6: unsupported file layout Application tried to create a window, but no driver could be loaded. Unknown error (127). err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": / FreeBSD powernoodle 10.0-ALPHA3 FreeBSD 10.0-ALPHA3 #26 r255930M: Sat Sep 28 12:22:28 PDT 2013 sbruno@powernoodle:/usr/obj/usr/src/sys/POWERNOODLE amd64 --=-QNET/fjk60dgsGCL49lb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (FreeBSD) iQEcBAABAgAGBQJSWIh6AAoJEBkJRdwI6BaHmS4H/3rhkMHCcwgcyb3iqi/74h3c vYGr8ocKwASEBNeEDodwu5oLlbyWiCO0uTx3cPfn/PytPExSDgVKFcumAs08YYQz 4bygO7T6XFPaACPqdz7gJOz8CZCFa5BYpSAzZWWhe8Aa8U26pi7ilcyaR3m2kEdm oNN2Uhim1ZyqQ9ku9NdBxSIrWeOM66V064gOQrKTv3wjuA/Twdg7vJz8mWZ+4Ga9 cQ3YdCxKgZYOTSt1YJE2UUGh6HlHzKw3PmJUVW5WqxY6SjALnxnmw1U6FavU1w+g pXg/BnADtBBcp4wyb5IflX8/z0UT34stKNTyxdbPpqWAnFJaa0Q63q6n840GV6o= =ulU1 -----END PGP SIGNATURE----- --=-QNET/fjk60dgsGCL49lb-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 00:14:13 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 11F26F1B; Sat, 12 Oct 2013 00:14:13 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DB15E2D1A; Sat, 12 Oct 2013 00:14:12 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r9C0EB1P069513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Oct 2013 17:14:11 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r9C0EBai069512; Fri, 11 Oct 2013 17:14:11 -0700 (PDT) (envelope-from jmg) Date: Fri, 11 Oct 2013 17:14:10 -0700 From: John-Mark Gurney To: Maksim Yevmenkin Subject: Re: [rfc] small bioq patch Message-ID: <20131012001410.GA56872@funkthat.com> Mail-Followup-To: Maksim Yevmenkin , Maksim Yevmenkin , "current@freebsd.org" References: <20131011215210.GY56872@funkthat.com> <72DA2C4F-44F0-456D-8679-A45CE617F8E6@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <72DA2C4F-44F0-456D-8679-A45CE617F8E6@gmail.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Fri, 11 Oct 2013 17:14:11 -0700 (PDT) Cc: Maksim Yevmenkin , "current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 00:14:13 -0000 Maksim Yevmenkin wrote this message on Fri, Oct 11, 2013 at 15:39 -0700: > > On Oct 11, 2013, at 2:52 PM, John-Mark Gurney wrote: > > > > Maksim Yevmenkin wrote this message on Fri, Oct 11, 2013 at 11:17 -0700: > >> i would like to submit the attached bioq patch for review and > >> comments. this is proof of concept. it helps with smoothing disk read > >> service times and arrear to eliminates outliers. please see attached > >> pictures (about a week worth of data) > >> > >> - c034 "control" unmodified system > >> - c044 patched system > > > > Can you describe how you got this data? Were you using the gstat > > code or some other code? > > Yes, it's basically gstat data. The reason I ask this is that I don't think the data you are getting from gstat is what you think you are... It accumulates time for a set of operations and then divides by the count... So I'm not sure if the stat improvements you are seeing are as meaningful as you might think they are... > > Also, was your control system w/ the patch, but w/ the sysctl set to > > zero to possibly eliminate any code alignment issues? > > Both systems use the same code base and build. Patched system has patch included, "control" system does not have the patch. I can rerun my tests with sysctl set to zero and use it as "control". So, the answer to your question is "no". I don't believe the code would make a difference, but more wanted to know what control was... > >> graphs show max/avg disk read service times for both systems across 36 > >> spinning drives. both systems are relatively busy serving production > >> traffic (about 10 Gbps at peak). grey shaded areas on the graphs > >> represent time when systems are refreshing their content, i.e. disks > >> are both reading and writing at the same time. > > > > Can you describe why you think this change makes an improvement? Unless > > you're running 10k or 15k RPM drives, 128 seems like a large number.. as > > that's about halve number of IOPs that a normal HD handles in a second.. > > Our (Netflix) load is basically random disk io. We have tweaked the system to ensure that our io path is "wide" enough, I.e. We read 1mb per disk io for majority of the requests. However offsets we read from are all over the place. It appears that we are getting into situation where larger offsets are getting delayed because smaller offsets are "jumping" ahead of them. Forcing bioq insert tail operation and effectively moving insertion point seems to help avoiding getting into this situation. And, no. We don't use 10k or 15k drives. Just regular enterprise 7200 sata drives. I assume that the 1mb reads are then further broken up into 8 128kb reads? so it's more like every 16 reads in your work load that you insert the "ordered" io... I want to make sure that we choose the right value for this number.. What number of IOPs are you seeing? > > I assume you must be regularly seeing queue depths of 128+ for this > > code to make a difference, do you see that w/ gstat? > > No, we don't see large (128+) queue sizes in gstat data. The way I see it, we don't have to have deep queue here. We could just have a steady stream of io requests where new, smaller, offsets consistently "jumping" ahead of older, larger offset. In fact gstat data show shallow queue of 5 or less items. Sorry, I miss read the patch the first time... After rereading it, the short summary is that if there hasn't been an ordered bio (bioq_insert_tail) after 128 requests, the next request will be "ordered"... > > Also, do you see a similar throughput of the system? > > Yes. We do see almost identical throughput from both systems. I have not pushed the system to its limit yet, but having much smoother disk read service time is important for us because we use it as one of the components of system health metrics. We also need to ensure that disk io request is actually dispatched to the disk in a timely manner. Per above, have you measured at the application layer that you are getting better latency times on your reads? Maybe by doing a ktrace of the io, and calculating times between read and return or something like that... Have you looked at the geom disk schedulers work that Luigi did a few years back? There have been known issues w/ our io scheduler for a long time... If you search the mailing lists, you'll see lots of reports from some processes starving out others, probably due to a similar issue... I've seen similar unfair behavior between processes, but spend time tracking it down... It does look like a good improvement though... Thanks for the work! -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 02:05:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4AA4024B for ; Sat, 12 Oct 2013 02:05:57 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 13BA42155 for ; Sat, 12 Oct 2013 02:05:57 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n5so2994368oag.41 for ; Fri, 11 Oct 2013 19:05:56 -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 :content-type; bh=pndDsnUx5WlmQFNAENo4glumDW8GwkUFrI6GXxvvoLI=; b=IUQZ+zNFXAj1n3soePEouJKm6ybPLOCl/jQ+dRDjvpG0BZzHF6r8uzw8IoWgW0XPIB 0nRD5bzgxRQW1GMemtPyEo1AXwAsMyfg7QSf72B1p8WGWWEFqbGdHElSgKQFLQr8vCtE X/s7iGDZdWfiiIEOh1JnXDdJWPLdtmaToCifVKQN7uZQx7k8+CmKjMxzHTWwMkXPbdQD G0ePIwk5S5qnNO2RuXKH3u3RdPnCPxS3IN+9ZD9BuGPsiADkSvzgmbJ+sQrQIJb2TcC0 bA9DJg+mvCIcad30WmJFvG5cyn+rmvWnY1moDp2IKtDbxGBMskyRP5Mt2NWvW2aakpSQ hqHA== MIME-Version: 1.0 X-Received: by 10.60.70.134 with SMTP id m6mr16795957oeu.14.1381543556422; Fri, 11 Oct 2013 19:05:56 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Fri, 11 Oct 2013 19:05:56 -0700 (PDT) In-Reply-To: References: <20131010013338.GA10499@troutmask.apl.washington.edu> Date: Fri, 11 Oct 2013 22:05:56 -0400 Message-ID: Subject: Re: /usr/src/lib/msun errors From: Joe Nosay To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 02:05:57 -0000 Is the ALPHA base stable enough to do porting of applications? On Fri, Oct 11, 2013 at 3:23 AM, Joe Nosay wrote: > > I did. Looks like I hosed part of the system but I am using it now. I'm > getting libiconv errors. Vi has been replaced with nvi. Neat. I need to > extract /base over /base. So, um, time to use the CD and set up a new > system,right? > > > On Thu, Oct 10, 2013 at 4:14 AM, Andreas Nilsson wrote: > >> Since there is -Wall in your CFALGS there will be quite a few warnings, >> which combined with -Werror which promotes warnings to errors makes it fail. >> >> Try removing -Wall and see if it works. Also -mssse3 can trigger more >> subtle stuff. >> >> Best regards >> Andreas >> >> >> On Thu, Oct 10, 2013 at 9:49 AM, Joe Nosay wrote: >> >>> Yes, I did. To what extent did I screw up? >>> >>> # added by use.perl 2013-03-03 23:39:20 >>> PERL_VERSION=5.16.2 >>> RUBY_DEFAULT_VER=1.9 >>> ALLOW_SHARED_TEXTREL=1 >>> >>> CFLAGS+= -mssse3 -Wall >>> CXXFLAGS+= -mssse3 >>> >>> >>> >>> >>> On Wed, Oct 9, 2013 at 9:33 PM, Steve Kargl < >>> sgk@troutmask.apl.washington.edu> wrote: >>> >>> > On Wed, Oct 09, 2013 at 09:00:11PM -0400, Joe Nosay wrote: >>> > > Src is from 10/7/13 on i386. Base is from April. >>> > >>> > > cc -O2 -pipe -mssse3 -Wall -I/usr/src/lib/msun/x86 >>> > -I/usr/src/lib/msun/ld80 -I/usr/src/lib/msun/src >>> > -I/usr/src/lib/msun/../libc/include -I/usr/src/lib/msun/../libc/i386 >>> > -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers >>> -Werror >>> > -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int >>> > -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality >>> > -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum >>> > -Wno-knr-promoted-parameter -Wno-parentheses -c >>> > /usr/src/lib/msun/src/e_j0.c -o e_j0.o >>> > > /usr/src/lib/msun/src/e_j0.c:281:10: error: variable 'p' is used >>> > uninitialized whenever 'if' condition is false >>> > [-Werror,-Wsometimes-uninitialized] >>> > >>> > Are you setting CFLAGS in make.conf? >>> > >>> > -- >>> > Steve >>> > >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to " >>> freebsd-current-unsubscribe@freebsd.org" >>> >> >> > From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 02:14:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4C17B38E for ; Sat, 12 Oct 2013 02:14:31 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id 095B121AA for ; Sat, 12 Oct 2013 02:14:30 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:51816] helo=localhost) by cdptpa-oedge02 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 54/9B-16944-480B8525; Sat, 12 Oct 2013 02:14:29 +0000 Date: Sat, 12 Oct 2013 02:14:28 +0000 Message-ID: <54.9B.16944.480B8525@cdptpa-oedge02> From: "Thomas Mueller" To: freebsd-current@freebsd.org References: <0E.82.01315.25778525@cdptpa-oedge03> <20131011221302.GH1611@albert.catwhisker.org> Subject: Re: What happened to nslookup? X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 02:14:31 -0000 > On Fri, Oct 11, 2013 at 10:10:26PM +0000, Thomas Mueller wrote: > ... > > Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one supposed to use in its place? > .... > Use "host." > nslookup was part of BIND, and has been deprecated for years (IIRC). > Peace, > david -- > David H. Wolfskill david@catwhisker.org Thanks for info! I saw that bind was removed from the current branch because of security problems, but didn't know nslookup was part of BIND. Now I see in $PORTSDIR/dns/bind-tools/pkg-plist bin/dig bin/host bin/nslookup so host is also part of BIND? I will remember to use "host" in the future. Tom From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 02:28:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 929EC650 for ; Sat, 12 Oct 2013 02:28:28 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 57169222D for ; Sat, 12 Oct 2013 02:28:27 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.7/8.14.7) with ESMTP id r9C2SPRg045567; Fri, 11 Oct 2013 19:28:25 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.7/8.14.7/Submit) id r9C2SPpa045566; Fri, 11 Oct 2013 19:28:25 -0700 (PDT) (envelope-from david) Date: Fri, 11 Oct 2013 19:28:25 -0700 From: David Wolfskill To: Thomas Mueller Subject: Re: What happened to nslookup? Message-ID: <20131012022825.GJ1611@albert.catwhisker.org> References: <0E.82.01315.25778525@cdptpa-oedge03> <20131011221302.GH1611@albert.catwhisker.org> <54.9B.16944.480B8525@cdptpa-oedge02> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="p+SyGXcYc+aq/C8k" Content-Disposition: inline In-Reply-To: <54.9B.16944.480B8525@cdptpa-oedge02> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 02:28:28 -0000 --p+SyGXcYc+aq/C8k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 12, 2013 at 02:14:28AM +0000, Thomas Mueller wrote: > ... > Thanks for info! Glad to help. > I saw that bind was removed from the current branch because of security p= roblems, It was removed, but I believe that there was a bit more to it than "security problems." > but didn't know nslookup was part of BIND. >=20 > Now I see in $PORTSDIR/dns/bind-tools/pkg-plist >=20 > bin/dig > bin/host > bin/nslookup >=20 > so host is also part of BIND? :-} The version of host we had when BIND was part of base was part of BIND, yes. Looking in src/usr.bin/host/Makefile, I see: # $FreeBSD: head/usr.bin/host/Makefile 255949 2013-09-30 17:23:45Z des $ LDNSDIR=3D ${.CURDIR}/../../contrib/ldns LDNSHOSTDIR=3D ${.CURDIR}/../../contrib/ldns-host =2E.. which indicates that this is a re-implementation of "host" as provided by contrib/ldns. > I will remember to use "host" in the future. I have found it generally easy to use (easier by far than nslookup). Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --p+SyGXcYc+aq/C8k Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlJYs8gACgkQmprOCmdXAD1amgCeKXDOgZR9/buvYtUgzXUksvup RLMAnRVIpibr6o2Xs3IU4rDDwgsYqRTV =RLTL -----END PGP SIGNATURE----- --p+SyGXcYc+aq/C8k-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 03:17:05 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D8B9499 for ; Sat, 12 Oct 2013 03:17:05 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from rush.bluerosetech.com (rush.bluerosetech.com [IPv6:2607:fc50:1000:9b00::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9BC5124C6 for ; Sat, 12 Oct 2013 03:17:05 +0000 (UTC) Received: from chombo.houseloki.net (unknown [IPv6:2601:7:1680:365:21c:c0ff:fe7f:96ee]) by rush.bluerosetech.com (Postfix) with ESMTPSA id 34DC111437; Fri, 11 Oct 2013 20:17:03 -0700 (PDT) Received: from [IPv6:2601:7:1680:365:e014:714:9e41:4c79] (unknown [IPv6:2601:7:1680:365:e014:714:9e41:4c79]) by chombo.houseloki.net (Postfix) with ESMTPSA id 7B648590; Fri, 11 Oct 2013 20:16:58 -0700 (PDT) Message-ID: <5258BF23.5090005@bluerosetech.com> Date: Fri, 11 Oct 2013 20:16:51 -0700 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Thomas Mueller , freebsd-current@freebsd.org Subject: Re: What happened to nslookup? References: <0E.82.01315.25778525@cdptpa-oedge03> <20131011221302.GH1611@albert.catwhisker.org> <54.9B.16944.480B8525@cdptpa-oedge02> In-Reply-To: <54.9B.16944.480B8525@cdptpa-oedge02> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 03:17:05 -0000 On 10/11/2013 7:14 PM, Thomas Mueller wrote: >> On Fri, Oct 11, 2013 at 10:10:26PM +0000, Thomas Mueller wrote: >> ... >>> Whatever happened to /usr/bin/nslookup in FreeBSD-current, and >>> what is one supposed to use in its place? >> .... > >> Use "host." > >> nslookup was part of BIND, and has been deprecated for years >> (IIRC). > >> Peace, david > -- >> David H. Wolfskill >> david@catwhisker.org > > Thanks for info! > > I saw that bind was removed from the current branch because of > security problems, but didn't know nslookup was part of BIND. That one caught me as well when I did make check-old with WITHOUT_BIND=YES. I installed dns/bind-tools to replace them (and got much newer versions in the process). From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 03:22:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8181A22C for ; Sat, 12 Oct 2013 03:22:59 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5EABD2529 for ; Sat, 12 Oct 2013 03:22:59 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r9C3Mwgc098820; Fri, 11 Oct 2013 20:22:58 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r9C3MwYS098819; Fri, 11 Oct 2013 20:22:58 -0700 (PDT) (envelope-from sgk) Date: Fri, 11 Oct 2013 20:22:58 -0700 From: Steve Kargl To: Joe Nosay Subject: Re: /usr/src/lib/msun errors Message-ID: <20131012032258.GA98799@troutmask.apl.washington.edu> References: <20131010013338.GA10499@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 03:22:59 -0000 On Fri, Oct 11, 2013 at 10:05:56PM -0400, Joe Nosay wrote: > Is the ALPHA base stable enough to do porting of applications? > Huh? What do you mean? People have been running freebsd-current for years and porting applications to FreeBSD. Alpha is simply a point in time for freebsd-current. -- Steve From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 03:49:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 280035F4 for ; Sat, 12 Oct 2013 03:49:17 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E39D22629 for ; Sat, 12 Oct 2013 03:49:16 +0000 (UTC) Received: by mail-oa0-f41.google.com with SMTP id n10so3072612oag.28 for ; Fri, 11 Oct 2013 20:49:16 -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=nvv/GFL6WAOmnByeyv65ZXKTAUa7GM8JaKRvjeBsggQ=; b=FWZViCgwtMGRZeHK4nd8a7ssaKF3xurhucoutHSbKoJ9GyJLo6ONFHbFnhvVi8UyHR U8n1tr/s4U1SFCnY34a1OxXoXg13fMedzCCWdqGCmE8/dpv/IG8JUrMwx/ukdG4o7oFC j+gEv5EuviBxCz1S1MneJHVegcYmN7gdPhnmk6VPnXXU75GucsSm5M0pv/vANmx6oIqX m+TnL7IIt/QR6JfmgALb0MP56mC4/4bVPGl9KkgYPZkTP7xhF5KvBFS/pw00NMs/tlS1 7PrerwbrqGa3rfFqd8AfSpCUvCp/oSx+DNRE4PZs1lKXu3Sh/oTyubciSqBqwx1asm+G bZ/Q== MIME-Version: 1.0 X-Received: by 10.60.42.234 with SMTP id r10mr334121oel.40.1381549756099; Fri, 11 Oct 2013 20:49:16 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Fri, 11 Oct 2013 20:49:15 -0700 (PDT) In-Reply-To: <1381444950273-5850951.post@n5.nabble.com> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <20131008031517.GA31864@troutmask.apl.washington.edu> <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> <1381444950273-5850951.post@n5.nabble.com> Date: Fri, 11 Oct 2013 23:49:15 -0400 Message-ID: Subject: Re: rcs From: Outback Dingo To: Jakub Lach Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 03:49:17 -0000 On Thu, Oct 10, 2013 at 6:42 PM, Jakub Lach wrote: > I have similar views. There is abundance of be-everything-for-everybody > Linuxes > and not enough lean and mean Unix-style kits... > > > > however did we neglect to realize that even some ports need rcs => clog-1.6.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch http://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/clog-1.6.tar.gz clog-1.6.tar.gz 100% of 17 kB 59 kBps 00m00s ===> Fetching all distfiles required by clog-1.6 for building ===> Extracting for clog-1.6 => SHA256 Checksum OK for clog-1.6.tar.gz. ===> Patching for clog-1.6 ===> Applying FreeBSD patches for clog-1.6 rcsdiff: not found patch: **** can't check out file clog.c: differs from default RCS version => Patch patch-clog.c failed to apply cleanly. *** Error code 1 Stop. uname -a FreeBSD zfsroot.xxxxxxx.com 10.0-ALPHA5 FreeBSD 10.0-ALPHA5 #0: Fri Oct 11 22:41:25 EDT 2013 me@zfsroot.xxxxxxx.com:/usr/obj/usr/src/sys/GENERIC amd64 > > > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/rcs-tp5850096p5850951.html > Sent from the freebsd-current mailing list archive at Nabble.com. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 03:52:46 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4C9CB72A; Sat, 12 Oct 2013 03:52:46 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1ECF02671; Sat, 12 Oct 2013 03:52:46 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 4D806A6E7; Sat, 12 Oct 2013 03:52:43 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 4D806A6E7 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Fri, 11 Oct 2013 23:52:41 -0400 From: Glen Barber To: Outback Dingo Subject: Re: rcs Message-ID: <20131012035241.GL44375@glenbarber.us> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> <1381444950273-5850951.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rPdL5sOQ4GFWV+a5" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-ALPHA4 amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org, Jakub Lach X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 03:52:46 -0000 --rPdL5sOQ4GFWV+a5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 11, 2013 at 11:49:15PM -0400, Outback Dingo wrote: > On Thu, Oct 10, 2013 at 6:42 PM, Jakub Lach wrot= e: >=20 > > I have similar views. There is abundance of be-everything-for-everybody > > Linuxes > > and not enough lean and mean Unix-style kits... > > > > > > > > > however did we neglect to realize that even some ports need rcs >=20 >=20 > =3D> clog-1.6.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > =3D> Attempting to fetch > http://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/clog-1.6.= tar.gz > clog-1.6.tar.gz 100% of 17 kB 59 kBps > 00m00s > =3D=3D=3D> Fetching all distfiles required by clog-1.6 for building > =3D=3D=3D> Extracting for clog-1.6 > =3D> SHA256 Checksum OK for clog-1.6.tar.gz. > =3D=3D=3D> Patching for clog-1.6 > =3D=3D=3D> Applying FreeBSD patches for clog-1.6 > rcsdiff: not found gjb@nucleus:~ % make -C /usr/ports/net-mgmt/clog -V PATCH_DEPENDS rcsdiff:/usr/ports/devel/rcs Glen --rPdL5sOQ4GFWV+a5 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJSWMeJAAoJELls3eqvi17Q71sP/icxinHekCVK1TIE6kvsGrkd +YRaRvhWQVe53BfA33iQL6tCp/H2ggm1eHi4BmRKWrzsYH+WVt3eXNz2VFl7IFqG PmA/+J2A4Ahy3MPRhrYGge2wmKoar5J4uG0xMphhUS7/e0GYIgWPJf1ZbCoZN7KC aRvSVVVORGgL9V20iKFQ9OsVGnATjZydlqOKj4jq8kw9k0MGuIYYtDB2jiu3CGTj KQd9WSlFKJi5R4XG3QVWk4K4uE5V4fynYzOAPk+3zFM8C7SpkLCUMO4a6QpFJ9UB Q4UnttjnSIPPfd2Q34nYvsQDCOUhqGMBfRBfZvYtbeyzRUDDpU9RR7DccpmukIfA UbbGQaoI+YfyjzxI+r7BfLBw0CSQvj1GaDdQ/pPdDPU4RGdzYoQkC3xhs+q3m/Qt vKZK06tF86z1lR5E+Ycix+3Tb3Vjuvh5NYUXTtWUzEaJ8xaRu+hcfa8C7TVJfSsX MYsCPMvgb1yAfneNyXjLw//OpG7CxTCBGhtYJsz9N6IlQsdzkOosDfe9H79mFmdw 65hzWle2DC5QTyD/bQk7eFSKPt4tycZGpFgO7747seS9pPZrejhrpKUgdt7vqKJY LGAhGXZNWmLBUJKQ13ZgYN95HBAk/r6cRayd67LTvohhZQkfEPOnYoZbSZWno5q8 AIbZ3daWZk6Vu2zaqs5y =3/Dr -----END PGP SIGNATURE----- --rPdL5sOQ4GFWV+a5-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 03:52:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 35A0084F; Sat, 12 Oct 2013 03:52:53 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9FD642675; Sat, 12 Oct 2013 03:52:52 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id h11so1006487wiv.13 for ; Fri, 11 Oct 2013 20:52:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:in-reply-to:references:mime-version:content-type :content-transfer-encoding:subject:from:date:to:cc:message-id; bh=YpsGJcGYOlDLh4yiT3LZKHRRIR+KaeRqK+jh6c5/WUM=; b=d2A18X5VsppSFdNDSbGtnBvrph9ExDSvt380F1k/hKREQnDmVmzsbFBMRWAp83N8HZ jwl5StA1KVbsk1dq+sKvLgXaMITR20+9ZXEe+QmEB7IxPbYj1lZ9FqeN+KubDTzUGuSB 1sj7p9v0WUqGQLgxigvmbmshwGGRtjeFwv0yDzgIti2+CacF8wNI7xBsRrO6+AMiDF9d 3gwPUa+bOvFjpTAK/HNO0msRA+lhSMwe5rMT7Ce6f9NkaxOqvJWaeNA138S296DIaI+D 95QHR04dypDQRZQDOnmyI+So4geRnGm0qU+I4oIZcQa7B4ReCsAw5LD/T379qs/QD3os LUXw== X-Received: by 10.180.221.38 with SMTP id qb6mr5794701wic.8.1381549969047; Fri, 11 Oct 2013 20:52:49 -0700 (PDT) Received: from android-7378cca9a7882e13.geek.lan (52.91.249.5.rev.vodafone.pt. [5.249.91.52]) by mx.google.com with ESMTPSA id d11sm11417304wic.4.2013.10.11.20.52.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 11 Oct 2013 20:52:48 -0700 (PDT) User-Agent: K-9 Mail for Android In-Reply-To: <08D4D879-C866-4BEB-BB1D-9579A32F1975@FreeBSD.org> References: <52571EF6.8010703@gmail.com> <5257DDD1.4070403@gmail.com> <08D4D879-C866-4BEB-BB1D-9579A32F1975@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: [SOLVED] Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2 From: "Miguel C." Date: Sat, 12 Oct 2013 04:52:45 +0100 To: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Message-ID: <7c50c939-bfe7-4fcb-b3ef-5c51d4ae8a9c@email.android.com> Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 03:52:53 -0000 I updated to alpha5 it is indeed removed. Thanks "Edward Tomasz Napierała" wrote: >Dnia 11 paĹş 2013 o godz. 13:15 "Mike C." >napisał(a): > >> >>> On 10/11/13 09:24, Edward Tomasz Napierała wrote: >>>> Wiadomość napisana przez Mike C. w dniu 10 paĹş 2013, o godz. 23:41: >>>> Hi, >>>> >>>> I'm running Alpha-2 and wanted to test with iscsi but it seems I >can't >>>> start iscsid. >>>> >>>> >>>> $ sudo service iscsid onerestart >>>> kldload: can't load iscsi: Exec format error >>>> /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi >>>> /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid >>>> >>>> >>>> dmesg shows: >>>> interface icl.1 already present in the KLD 'kernel'! >>>> linker_load_file: Unsupported file type >>> >>> Do you have "device ctl" in your kernel config? If so, >>> either remove it (ctl.ko module is automatically loaded >>> by ctladm), or add "device iscsi". >> >> device ctl # CAM Target Layer >> >> Seems that GENERIC has it by default! I'll remove and recompile! > >Actually, it got removed from GENERIC in 10 some time ago. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 04:00:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 34BB89B4; Sat, 12 Oct 2013 04:00:41 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E392726D8; Sat, 12 Oct 2013 04:00:40 +0000 (UTC) Received: by mail-oa0-f53.google.com with SMTP id i7so3039886oag.40 for ; Fri, 11 Oct 2013 21:00:40 -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=vAWLPE2SXEa+pMeW17sK7aGtfPjgL1f4UC4nl+qafM0=; b=jEgvSL6piOacCvXOHkb8FxAWH2XlrCHVxkRuHfqlcOQJ3PPFWjYglZEWU2gDHZqQE2 D4lle6rNmwZAek8r+oKAsf4lGCNO4hJy+5DnNUxXT8GvJs8lvseNLXbzqBTQ5aCKeel0 A61HDwj9gKDDa1R3IfmJV1vi7eKTegiYwGbcEKBpdSgkrjRsTdWcnQmi/IN2lQGz3Jdd lopDq3kXrQaq7pppmgFu353ewhfws0Li6AXceH2YjyJLRDZt3SJZev1yOPvuTXWgSFgH d5PYKj08ihd5Z0ujwRkBQbU6H/wahOV93KXqdYIjAjFrqRx2kKzJtsdjpc35tFxLbKHg j9wA== MIME-Version: 1.0 X-Received: by 10.60.52.244 with SMTP id w20mr17236141oeo.30.1381550440158; Fri, 11 Oct 2013 21:00:40 -0700 (PDT) Received: by 10.76.13.228 with HTTP; Fri, 11 Oct 2013 21:00:39 -0700 (PDT) In-Reply-To: <20131012035241.GL44375@glenbarber.us> References: <60177810-8DC4-4EA3-8040-A834B79039D2@orthanc.ca> <52538EDC.2080001@freebsd.org> <52541202.3010707@mu.org> <20131008.170444.74714516.sthaug@nethelp.no> <525422B6.9040906@mu.org> <1381444950273-5850951.post@n5.nabble.com> <20131012035241.GL44375@glenbarber.us> Date: Sat, 12 Oct 2013 00:00:39 -0400 Message-ID: Subject: Re: rcs From: Outback Dingo To: Glen Barber Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current@freebsd.org, Jakub Lach X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 04:00:41 -0000 On Fri, Oct 11, 2013 at 11:52 PM, Glen Barber wrote: > On Fri, Oct 11, 2013 at 11:49:15PM -0400, Outback Dingo wrote: > > On Thu, Oct 10, 2013 at 6:42 PM, Jakub Lach > wrote: > > > > > I have similar views. There is abundance of be-everything-for-everybody > > > Linuxes > > > and not enough lean and mean Unix-style kits... > > > > > > > > > > > > > > however did we neglect to realize that even some ports need rcs > > > > > > => clog-1.6.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > > => Attempting to fetch > > > http://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/clog-1.6.tar.gz > > clog-1.6.tar.gz 100% of 17 kB 59 kBps > > 00m00s > > ===> Fetching all distfiles required by clog-1.6 for building > > ===> Extracting for clog-1.6 > > => SHA256 Checksum OK for clog-1.6.tar.gz. > > ===> Patching for clog-1.6 > > ===> Applying FreeBSD patches for clog-1.6 > > rcsdiff: not found > > gjb@nucleus:~ % make -C /usr/ports/net-mgmt/clog -V PATCH_DEPENDS > rcsdiff:/usr/ports/devel/rcs > > Yupp just found it, i got it done, but thanks > Glen > > From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 06:17:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DC11CD23 for ; Sat, 12 Oct 2013 06:17:23 +0000 (UTC) (envelope-from zf@ancientrocklab.com) Received: from relay.ox.registrar-servers.com (relay.ox.registrar-servers.com [199.188.203.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 79D862C33 for ; Sat, 12 Oct 2013 06:17:22 +0000 (UTC) Received: (qmail 15378 invoked by uid 89); 12 Oct 2013 06:10:40 -0000 Received: from unknown (HELO imap3-1.ox.registrar-servers.com) (198.187.29.241) by relay.ox.registrar-servers.com with SMTP; 12 Oct 2013 06:10:40 -0000 Received: from localhost (localhost [127.0.0.1]) by oxmail.registrar-servers.com (Postfix) with ESMTP id 182392A007B for ; Sat, 12 Oct 2013 02:10:34 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap3.ox.registrar-servers.com Received: from oxmail.registrar-servers.com ([127.0.0.1]) by localhost (imap3.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WuqDIibTwUw2 for ; Sat, 12 Oct 2013 02:10:34 -0400 (EDT) Received: from [192.168.88.51] (unknown [192.184.94.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oxmail.registrar-servers.com (Postfix) with ESMTPSA id 696CA2A007D for ; Sat, 12 Oct 2013 02:10:33 -0400 (EDT) From: zhifeng hu Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: May you please add alias for nslookup? Message-Id: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> Date: Sat, 12 Oct 2013 14:10:30 +0800 To: freebsd-current@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 06:17:23 -0000 I am noticed that the nslookup will not appear by default in freebsd 10. but this is a very basic tools, we need it very much more than you think. would you please add alias for nslookup ? such as alias nslookup="host -v" NOT FORCE USER TO INSTALL dns/bind-tool It's not good for human use experiences. zhifeng hu From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 08:45:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 19ACC1A4 for ; Sat, 12 Oct 2013 08:45:17 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C9194215A for ; Sat, 12 Oct 2013 08:45:16 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VUuou-0006rq-Pp for freebsd-current@freebsd.org; Sat, 12 Oct 2013 10:45:08 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 12 Oct 2013 10:45:08 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 12 Oct 2013 10:45:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Subject: Re: May you please add alias for nslookup? Date: Sat, 12 Oct 2013 10:44:56 +0200 Lines: 43 Message-ID: References: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kXrPrqLnM19S0aq5mhQ0ADrb3SfV8P8Rl" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 In-Reply-To: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> X-Enigmail-Version: 1.5.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 08:45:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --kXrPrqLnM19S0aq5mhQ0ADrb3SfV8P8Rl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12/10/2013 08:10, zhifeng hu wrote: > I am noticed that the nslookup will not appear by default in freebsd 10= =2E > but this is a very basic tools, we need it very much more than you thin= k. > would you please add alias for nslookup ? such as=20 > alias nslookup=3D"host -v" >=20 > NOT FORCE USER TO INSTALL dns/bind-tool=20 >=20 > It's not good for human use experiences. nslookup is a very different tool, it has an interactive mode which is not available in e.g. the "host" utility and a specific output format (scripts will break if they attempt to parse the output of host -v as if it is coming from nslookup). But I agree that something should be done - maybe a script which checks if /usr/local/bin/nslookup exists, then executes it, and if it doesn't exist then outputs a message explaning the user what has happened and optionally invoking "host" or "dig". --kXrPrqLnM19S0aq5mhQ0ADrb3SfV8P8Rl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iKYEARECAGYFAlJZDAlfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDYxNDE4MkQ3ODMwNDAwMDJFRUIzNDhFNUZE MDhENTA2M0RGRjFEMkMACgkQ/QjVBj3/HSxUlgCgpA5ijlAiQZFllilt9ujuj/sb CB8AnRIhQ+/zQRhkFR+JeM3vFTgn6XmG =8ho+ -----END PGP SIGNATURE----- --kXrPrqLnM19S0aq5mhQ0ADrb3SfV8P8Rl-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 09:09:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 451C260D; Sat, 12 Oct 2013 09:09:07 +0000 (UTC) (envelope-from zf@ancientrocklab.com) Received: from imap3-1.ox.registrar-servers.com (imap3-1.ox.registrar-servers.com [198.187.29.241]) by mx1.freebsd.org (Postfix) with ESMTP id 1C85D2246; Sat, 12 Oct 2013 09:09:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by oxmail.registrar-servers.com (Postfix) with ESMTP id E59A42A007A; Sat, 12 Oct 2013 05:09:05 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap3.ox.registrar-servers.com Received: from oxmail.registrar-servers.com ([127.0.0.1]) by localhost (imap3.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9GBcYf7Tnd1H; Sat, 12 Oct 2013 05:09:05 -0400 (EDT) Received: from [192.168.88.50] (unknown [192.184.94.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by oxmail.registrar-servers.com (Postfix) with ESMTPSA id ED1EA2A006A; Sat, 12 Oct 2013 05:09:04 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: May you please add alias for nslookup? From: zhifeng hu In-Reply-To: Date: Sat, 12 Oct 2013 17:09:01 +0800 Content-Transfer-Encoding: quoted-printable Message-Id: <6AED7CCF-6A89-422D-9411-3AE6F26227CE@ancientrocklab.com> References: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> To: Ivan Voras X-Mailer: Apple Mail (2.1510) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 09:09:07 -0000 OK=EF=BC=8C I am system administrator, I manage a server cluster for = years, i really need nslookup tools to diagnostic the network health. i = thought there be many more people here will be in trouble. Who will be affected by this change, may be the system administrators. = may be the normal users. After upgraded their system or reinstall system, they found their lovely = tools disappeared. Every changes should be clear and help people out the trouble. No trouble,no Suffering please. On Oct 12, 2013, at 4:44 PM, Ivan Voras wrote: > On 12/10/2013 08:10, zhifeng hu wrote: >> I am noticed that the nslookup will not appear by default in freebsd = 10. >> but this is a very basic tools, we need it very much more than you = think. >> would you please add alias for nslookup ? such as=20 >> alias nslookup=3D"host -v" >>=20 >> NOT FORCE USER TO INSTALL dns/bind-tool=20 >>=20 >> It's not good for human use experiences. >=20 > nslookup is a very different tool, it has an interactive mode which is > not available in e.g. the "host" utility and a specific output format > (scripts will break if they attempt to parse the output of host -v as = if > it is coming from nslookup). But I agree that something should be done = - > maybe a script which checks if /usr/local/bin/nslookup exists, then > executes it, and if it doesn't exist then outputs a message explaning > the user what has happened and optionally invoking "host" or "dig". >=20 zhifeng hu From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 09:15:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2E18877A for ; Sat, 12 Oct 2013 09:15:25 +0000 (UTC) (envelope-from mihamina@rktmb.org) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [IPv6:2001:4b98:c:538::195]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E017822BF for ; Sat, 12 Oct 2013 09:15:24 +0000 (UTC) Received: from mfilter2-d.gandi.net (mfilter2-d.gandi.net [217.70.178.140]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id 65825A80B0 for ; Sat, 12 Oct 2013 11:15:22 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter2-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter2-d.gandi.net (mfilter2-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id G-ogBn6ZtGRX for ; Sat, 12 Oct 2013 11:15:20 +0200 (CEST) X-Originating-IP: 41.188.46.121 Received: from localhost.localdomain (unknown [41.188.46.121]) (Authenticated sender: out@rktmb.org) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 94A8BA80CB for ; Sat, 12 Oct 2013 11:15:19 +0200 (CEST) Message-ID: <52591323.7050801@rktmb.org> Date: Sat, 12 Oct 2013 12:15:15 +0300 From: Mihamina RKTMB Organization: RKTMB User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: May you please add alias for nslookup? References: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> <6AED7CCF-6A89-422D-9411-3AE6F26227CE@ancientrocklab.com> In-Reply-To: <6AED7CCF-6A89-422D-9411-3AE6F26227CE@ancientrocklab.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 09:15:25 -0000 On 10/12/2013 12:09 PM, zhifeng hu wrote: > Every changes should be clear and help people out the trouble. > No trouble,no Suffering please. And aliasing the "real nslookup" with host is driving into errors. -- +261 34 81 738 69 From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 11:12:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2D9119A0; Sat, 12 Oct 2013 11:12:49 +0000 (UTC) (envelope-from kowalczfbsd@gmail.com) Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9928627B4; Sat, 12 Oct 2013 11:12:48 +0000 (UTC) Received: by mail-ea0-f177.google.com with SMTP id f15so2336414eak.8 for ; Sat, 12 Oct 2013 04:12:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:content-type; bh=LyRQMBxaKdBUTIXSY6flnc807ftXiO769iMwc2VlCnE=; b=R0+7Bie8vAnN2UuboXHWwoLgszrA9gkGi8/W0HpetWeU7n7YmZTrVk/01EaUBRJdXK 1dRQD3PSx+pLnMNn1zM6BjzL+aKjLC7rq7uFMDdrGgH2UVoXCxShDMaxnjji+fWAD1Ek jbfgH65TA1XToE7yZZgdWUuILPw2AQOK+a0fcSy2tG+P92BIfS6eUODrSaxyT47B6qGq 1oAZcAobDPmpWWD/MWTfzvDiNwq+DTCT04g5KRpU27aAVBmVwxSqzqqf164RwNZPw64L 9TZKEGCTF4WJ4oOnK7hYs6JAfsACNjkCU4YqqMVSyC4kEbVDDMfviFw21XthS2ZK2HMx Kv4Q== X-Received: by 10.14.5.3 with SMTP id 3mr3440750eek.49.1381576367071; Sat, 12 Oct 2013 04:12:47 -0700 (PDT) Received: from tyson.x64.me (87-206-163-14.dynamic.chello.pl. [87.206.163.14]) by mx.google.com with ESMTPSA id f49sm126360689eec.7.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 12 Oct 2013 04:12:46 -0700 (PDT) From: Tomasz Kowalczyk To: freebsd-current@freebsd.org, sbruno@freebsd.org Subject: Re: i386-wine + 10.0 Date: Sat, 12 Oct 2013 13:12:45 +0200 Message-ID: <4954264.LLnWvSthtt@tyson.x64.me> User-Agent: KMail/4.11.2 (FreeBSD/10.0-ALPHA5; KDE/4.11.2; amd64; ; ) In-Reply-To: <1381533825.2273.0.camel@localhost> References: <1381533825.2273.0.camel@localhost> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 11:12:49 -0000 On Friday, October 11, 2013 04:23:45 PM Sean Bruno wrote: > I think I built everything according to > https://wiki.freebsd.org/i386-Wine and got a package out of it. I think > I missed something obvious here. > > When I try to run simple windows things I get: > err:module:load_builtin_dll failed to load .so lib for builtin > L"winex11.drv": /usr/local/lib/libXext.so.6: unsupported file layout Think I had to add: /usr/local/lib /usr/local/lib32 to /etc/libmap32.conf, but I don't have i386-wine installed atm, so I cant check this. Anyway something isnt working right. Every file from wine set up LD_32_LIBRARY_PATH correctly, but this just wont work. From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 11:22:17 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 223CFC82 for ; Sat, 12 Oct 2013 11:22:17 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B27CD283B for ; Sat, 12 Oct 2013 11:22:16 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id m15so1948566wgh.1 for ; Sat, 12 Oct 2013 04:22:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=N5+V/y4e89uV09SO3kFfuFKT21iTI0LynxQ5YqJeSw0=; b=vh4mOd/y7uORTt9yhJ5ZRq3qEAxZyFT5yCzTaJAWiM2/F7BPAhjPjAWoRsDM4Y9cTx rHqcACdxBcbIgfjN6mD+G/CtFPzNuRAlCTPuBhd3u8oxO8MyphJhnc9xHELojrN87v4a KvG1go7XlIhqBnhRpLveQQVQ2F7Eg393FsBSX0vLPA0T8BawfpfhjurGcJdQ0FnHOoSI zfNjrlo0sHwsikCvz2KC3GPnZ6ccCtGsAP6ALA7kI1wyNpagbL+KU+Dz1/8bXqF1Se+g OGQrhKXdZBCwHuxCnKEK21CUAkZMotwqWiBWIdxCRogQJkW43ZE50IcmvqAwTjDuTSrl QPEg== X-Received: by 10.180.160.203 with SMTP id xm11mr6947125wib.17.1381576935261; Sat, 12 Oct 2013 04:22:15 -0700 (PDT) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk. [87.194.105.247]) by mx.google.com with ESMTPSA id q17sm14261062wiv.10.1969.12.31.16.00.00 (version=SSLv3 cipher=RC4-SHA bits=128/128); Sat, 12 Oct 2013 04:22:14 -0700 (PDT) Date: Sat, 12 Oct 2013 12:22:13 +0100 From: RW To: freebsd-current@freebsd.org Subject: Re: May you please add alias for nslookup? Message-ID: <20131012122213.3b21123a@gumby.homeunix.com> In-Reply-To: References: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 11:22:17 -0000 On Sat, 12 Oct 2013 10:44:56 +0200 Ivan Voras wrote: > explaning the user what has happened and optionally invoking "host" > or "dig". Actually dig has gone and has been replaced by the unbound utility drill. From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 11:29:21 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2BE6CE87 for ; Sat, 12 Oct 2013 11:29:21 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.upper.net (mail.upper.net [62.75.224.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BCFA8287D for ; Sat, 12 Oct 2013 11:29:20 +0000 (UTC) Received: from ubm.strangled.net (mail.upper.net [62.75.224.33]) (authenticated bits=0) by mail.upper.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id r9CBT8Eb002241 for ; Sat, 12 Oct 2013 13:29:08 +0200 Received: from ubm.strangled.net ([92.229.23.139] helo=ubm.strangled.net) by ASSP.nospam.UpPeRnEt; 12 Oct 2013 13:29:08 +0200 Date: Sat, 12 Oct 2013 13:29:08 +0200 From: Marc "UBM" Bocklet To: current@freebsd.org Subject: Possible iconv fallout? Message-Id: <20131012132908.a122b1b3f85d9936b87fb4f3@u-boot-man.de> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 12 Oct 2013 11:44:58 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 11:29:21 -0000 Hiho! :-) Compilation of sylpheed-3.3.0_2 fails with (last three lines show the error): ---- /bin/sh ../libtool --mode=link cc -O2 -pipe -fno-strict-aliasing -I/usr/local/include -I/usr/local/include/gtkspell-2.0 -I/usr/local/include/gtk-2.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pixman-1 -D_THREAD_SAFE -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/libpng15 -I/usr/local/include/pango-1.0 -pthread -I/usr/local/include/glib-2.0 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include/harfbuzz -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 -I/usr/local/include -pthread -I/usr/local/include/glib-2.0 -I/usr/local/include -ltinfow -Wl,-rpath=/usr/local/lib -o libsylph-0.la -rpath /usr/local/lib -version-info 2:0:1 -export-dynamic account.lo base64.lo codeconv.lo customheader.lo displayheader.lo filter.lo folder.lo html.lo imap.lo mbox.lo md5.lo md5_hmac.lo mh.lo news.lo nntp.lo pop.lo prefs.lo prefs_account.lo prefs_common.lo procheader.lo procmime.lo procmsg.lo quoted-printable.lo recv.lo session.lo smtp.lo socket.lo socks.lo ssl.lo stringtable.lo sylmain.lo unmime.lo utils.lo uuencode.lo virtual.lo xml.lo syl-marshal.lo -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -L/usr/local/lib -lglib-2.0 -lintl -L/usr/local/lib -pthread -L/usr/local/lib -lssl -lcrypto -lgtkspell -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lXfixes -lX11 -latk-1.0 -lcairo -pthread -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lintl -lfontconfig -L/usr/local/lib -lfreetype -lenchant -lgmodule-2.0 -pthread -L/usr/local/lib -lglib-2.0 -lintl -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -L/usr/local/lib -lglib-2.0 -lintl -lgthread-2.0 -pthread -L/usr/local/lib -lglib-2.0 -lintl grep: /usr/local/lib/libiconv.la: No such file or directory sed: /usr/local/lib/libiconv.la: No such file or directory libtool: link: `/usr/local/lib/libiconv.la' is not a valid libtool archive --- Is that the ports failure or am I doing something wrong (I'm pretty sure I followed the procedure described in ports/UPDATING)? Bye Marc From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 12:11:37 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5FBED8B7 for ; Sat, 12 Oct 2013 12:11:37 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id 1E5952A91 for ; Sat, 12 Oct 2013 12:11:36 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3cxlJ21blkzFTXL; Sat, 12 Oct 2013 14:11:30 +0200 (CEST) X-Virus-Scanned: amavisd-new at madpilot.net Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrLUttw3j5Am; Sat, 12 Oct 2013 14:11:28 +0200 (CEST) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by winston.madpilot.net (Postfix) with ESMTPSA; Sat, 12 Oct 2013 14:11:28 +0200 (CEST) Message-ID: <52593C6F.6080709@madpilot.net> Date: Sat, 12 Oct 2013 14:11:27 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: "Marc \"UBM\" Bocklet" , current@freebsd.org Subject: Re: Possible iconv fallout? References: <20131012132908.a122b1b3f85d9936b87fb4f3@u-boot-man.de> In-Reply-To: <20131012132908.a122b1b3f85d9936b87fb4f3@u-boot-man.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 12:11:37 -0000 On 10/12/13 13:29, Marc UBM Bocklet wrote: > > Hiho! :-) > > Compilation of sylpheed-3.3.0_2 fails with (last three lines show the > error): > > ---- > /bin/sh ../libtool --mode=link cc -O2 -pipe -fno-strict-aliasing > -I/usr/local/include -I/usr/local/include/gtkspell-2.0 > -I/usr/local/include/gtk-2.0 -I/usr/local/include/gio-unix-2.0/ > -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo > -I/usr/local/include/pixman-1 -D_THREAD_SAFE > -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/libpng15 > -I/usr/local/include/pango-1.0 -pthread -I/usr/local/include/glib-2.0 > -I/usr/local/include/freetype2 -I/usr/local/include > -I/usr/local/include/harfbuzz -I/usr/local/include/dbus-1.0 > -I/usr/local/include/dbus-1.0/include -I/usr/local/include/glib-2.0 > -I/usr/local/include -pthread -I/usr/local/include/glib-2.0 > -I/usr/local/include -ltinfow -Wl,-rpath=/usr/local/lib -o > libsylph-0.la -rpath /usr/local/lib -version-info 2:0:1 > -export-dynamic account.lo base64.lo codeconv.lo customheader.lo > displayheader.lo filter.lo folder.lo html.lo imap.lo mbox.lo md5.lo > md5_hmac.lo mh.lo news.lo nntp.lo pop.lo prefs.lo prefs_account.lo > prefs_common.lo procheader.lo procmime.lo procmsg.lo > quoted-printable.lo recv.lo session.lo smtp.lo socket.lo socks.lo > ssl.lo stringtable.lo sylmain.lo unmime.lo utils.lo uuencode.lo > virtual.lo xml.lo syl-marshal.lo -lgobject-2.0 -Wl,--export-dynamic > -lgmodule-2.0 -pthread -L/usr/local/lib -lglib-2.0 -lintl > -L/usr/local/lib -pthread -L/usr/local/lib -lssl -lcrypto -lgtkspell > -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -lXext -lXrender > -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lXfixes > -lX11 -latk-1.0 -lcairo -pthread -lgdk_pixbuf-2.0 -lgio-2.0 > -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lintl -lfontconfig > -L/usr/local/lib -lfreetype -lenchant -lgmodule-2.0 -pthread > -L/usr/local/lib -lglib-2.0 -lintl -ldbus-glib-1 -ldbus-1 > -lgobject-2.0 -L/usr/local/lib -lglib-2.0 -lintl -lgthread-2.0 > -pthread -L/usr/local/lib -lglib-2.0 -lintl > > grep: /usr/local/lib/libiconv.la: No such file or directory > sed: /usr/local/lib/libiconv.la: No such file or directory libtool: > link: `/usr/local/lib/libiconv.la' is not a valid libtool archive > --- > > Is that the ports failure or am I doing something wrong (I'm pretty > sure I followed the procedure described in ports/UPDATING)? It most probably is some libtool ".la" file still referencing the libiconv .la file. Please run the following command: find /usr/local/lib -name '*.la' -exec grep -n libiconv.la {} \; -print | xargs -n 1 pkg which -qo | sort -u This will give you a list of ports still having reference to libiconv.la, which does not exist anymore. These ports need to be reinstalled. I hope there are not many! :) -- Guido Falsi From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 13:29:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CF9B0804 for ; Sat, 12 Oct 2013 13:29:29 +0000 (UTC) (envelope-from john@potato.growveg.org) Received: from potato.growveg.org (growveg-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:3d2::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8DDD62D84 for ; Sat, 12 Oct 2013 13:29:29 +0000 (UTC) Received: from john by potato.growveg.org with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1VUzG1-0004Tf-8o for freebsd-current@freebsd.org; Sat, 12 Oct 2013 14:29:25 +0100 Date: Sat, 12 Oct 2013 14:29:25 +0100 From: John To: freebsd-current@freebsd.org Subject: stable-10 or head? Message-ID: <20131012132925.GB97901@potato.growveg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: John X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: john@potato.growveg.org X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 13:29:29 -0000 Hello currents, I have a 9.2-R vm and I'd like to bring it up to 10 (i.e what will eventually be 10-RELEASE). So, do I svn 10-STABLE or HEAD? I think 10-STABLE but I just want to check. thanks, -- John From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 13:37:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5C32FA6D for ; Sat, 12 Oct 2013 13:37:43 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from winston.madpilot.net (winston.madpilot.net [78.47.75.155]) by mx1.freebsd.org (Postfix) with ESMTP id 1BCA82DF5 for ; Sat, 12 Oct 2013 13:37:42 +0000 (UTC) Received: from winston.madpilot.net (localhost [127.0.0.1]) by winston.madpilot.net (Postfix) with ESMTP id 3cxnCT67mxzFTXL; Sat, 12 Oct 2013 15:37:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at madpilot.net Received: from winston.madpilot.net ([127.0.0.1]) by winston.madpilot.net (winston.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o661QvwGUwET; Sat, 12 Oct 2013 15:37:40 +0200 (CEST) Received: from tommy.madpilot.net (micro.madpilot.net [88.149.173.206]) by winston.madpilot.net (Postfix) with ESMTPSA; Sat, 12 Oct 2013 15:37:40 +0200 (CEST) Message-ID: <525950A3.6080208@madpilot.net> Date: Sat, 12 Oct 2013 15:37:39 +0200 From: Guido Falsi User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: John , freebsd-current@freebsd.org Subject: Re: stable-10 or head? References: <20131012132925.GB97901@potato.growveg.org> In-Reply-To: <20131012132925.GB97901@potato.growveg.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 13:37:43 -0000 On 10/12/13 15:29, John wrote: > Hello currents, > > I have a 9.2-R vm and I'd like to bring it up to 10 (i.e what will > eventually be 10-RELEASE). So, do I svn 10-STABLE or HEAD? > > I think 10-STABLE but I just want to check. You are correct. branch stable/10 on subversion. It's labelled as ALPHA6 at present. -- Guido Falsi From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 14:29:55 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5526D181; Sat, 12 Oct 2013 14:29:55 +0000 (UTC) (envelope-from remko@freebsd.org) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [78.47.69.234]) by mx1.freebsd.org (Postfix) with ESMTP id CBD732FC8; Sat, 12 Oct 2013 14:29:54 +0000 (UTC) Received: from [IPv6:2001:470:d701::c092:f153:404c:9be7] (unknown [IPv6:2001:470:d701:0:c092:f153:404c:9be7]) by mail.jr-hosting.nl (Postfix) with ESMTPSA id D4D3838B108A; Sat, 12 Oct 2013 16:29:51 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_95E24EFA-909E-4591-A04C-B7807ECE4BAF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: svn commit: r256256 - in head: . etc etc/defaults etc/rc.d share/man/man5 usr.sbin/jail From: Remko Lodder In-Reply-To: <20131011141214.GA91989@mouf.net> Date: Sat, 12 Oct 2013 16:29:47 +0200 Message-Id: <4B2ECC28-4F63-448A-B99E-DC5215C5FFD0@freebsd.org> References: <04E9979E-1D97-4AA2-A7AE-F9D8457B3599@FreeBSD.org> <20131011141214.GA91989@mouf.net> To: Steve Wills X-Mailer: Apple Mail (2.1510) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 14:29:55 -0000 --Apple-Mail=_95E24EFA-909E-4591-A04C-B7807ECE4BAF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Oct 11, 2013, at 4:12 PM, Steve Wills wrote: > I'm having the same issue. I am working with Hiroki to resolve this. So far his work seems to fix = this, he will commit that as soon as we can reasonable think that this is OK (and it looks that way :)) Thanks Hiroki! Remko >=20 > Steve >=20 > On Fri, Oct 11, 2013 at 03:05:51PM +0200, Remko Lodder wrote: >>=20 >> Dear Current readers, >>=20 >> Please find issues that I have with the latest /etc/rc.d/jail changes = and the use of ezjail. >>=20 >> Thanks >> remko >>=20 >>=20 >> Begin forwarded message: >>=20 >>> From: Remko Lodder >>> Subject: Re: svn commit: r256256 - in head: . etc etc/defaults = etc/rc.d share/man/man5 usr.sbin/jail >>> Date: October 11, 2013 3:04:12 PM GMT+02:00 >>> To: Hiroki Sato >>> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, = svn-src-head@freebsd.org >>>=20 >>>=20 >>> Hi Hiroki, >>>=20 >>> On Oct 10, 2013, at 11:32 AM, Hiroki Sato wrote: >>>=20 >>>> Author: hrs >>>> Date: Thu Oct 10 09:32:27 2013 >>>> New Revision: 256256 >>>> URL: http://svnweb.freebsd.org/changeset/base/256256 >>>>=20 >>>> Log: >>>> - Update rc.d/jail to use a jail(8) configuration file instead of >>>> command line options. The "jail__*" rc.conf(5) variables = for >>>> per-jail configuration are automatically converted to >>>> /var/run/jail..conf before the jail(8) utility is invoked. >>>> This is transparently backward compatible. >>>>=20 >>>> - Fix a minor bug in jail(8) which prevented it from returning = false >>>> when jail -r failed. >>>>=20 >>>=20 >>> Thanks for doing such a massive update. However it seems to break = the ezjail utility. >>> My jails didn't restart after I upgraded to the most recent -head = version=20 >>>=20 >>> FreeBSD nakur.elvandar.org 10.0-ALPHA6 FreeBSD 10.0-ALPHA6 #7 = r256311: Fri Oct 11 13:27:54 CEST 2013 = root@nakur.elvandar.org:/usr/obj/usr/src/sys/NAKUR amd64 >>>=20 >>> If I replace this with an older version, the utility starts and = complains about certain things not being done properly. The >>> system does not mount devfs nodes anylonger and thus is basically = out of function. >>>=20 >>> I was not expecting this much fallout from this change, others that = will be upgrading will loose the ability to start their jails until they = can >>> resolve this by hand. >>>=20 >>> Thanks >>> Remko >>>=20 >>>> Approved by: re (glebius) >>>>=20 >>>> Modified: >>>> head/UPDATING >>>> head/etc/defaults/rc.conf >>>> head/etc/rc.d/jail >>>> head/etc/rc.subr >>>> head/share/man/man5/rc.conf.5 >>>> head/usr.sbin/jail/jail.c >>>>=20 >>>> Modified: head/UPDATING >>>> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D >>>> --- head/UPDATING Thu Oct 10 07:41:11 2013 (r256255) >>>> +++ head/UPDATING Thu Oct 10 09:32:27 2013 (r256256) >>>> @@ -31,6 +31,25 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 10 >>>> disable the most expensive debugging functionality run >>>> "ln -s 'abort:false,junk:false' /etc/malloc.conf".) >>>>=20 >>>> +20131010: >>>> + The rc.d/jail script has been updated to support jail(8) >>>> + configuration file. The "jail__*" rc.conf(5) variables >>>> + for per-jail configuration are automatically converted to >>>> + /var/run/jail..conf before the jail(8) utility is = invoked. >>>> + This is transparently backward compatible. See below about some >>>> + incompatibilities and rc.conf(5) manual page for more details. >>>> + >>>> + These variables are now deprecated in favor of jail(8) = configuration >>>> + file. One can use "rc.d/jail config " command to = generate >>>> + a jail(8) configuration file in /var/run/jail..conf = without >>>> + running the jail(8) utility. The default pathname of the >>>> + configuration file is /etc/jail.conf and can be specified by >>>> + using $jail_conf or $jail__conf variables. >>>> + >>>> + Please note that jail_devfs_ruleset accepts an integer at >>>> + this moment. Please consider to rewrite the ruleset name >>>> + with an integer. >>>> + >>>> 20130930: >>>>=20 >>=20 >> --=20 >> /"\ With kind regards, | remko@elvandar.org >> \ / Remko Lodder | remko@FreeBSD.org >> X FreeBSD | = http://www.evilcoder.org >> / \ The Power to Serve | Quis custodiet ipsos custodes >>=20 >=20 >=20 --=20 /"\ With kind regards, | remko@elvandar.org \ / Remko Lodder | remko@FreeBSD.org X FreeBSD | = http://www.evilcoder.org / \ The Power to Serve | Quis custodiet ipsos custodes --Apple-Mail=_95E24EFA-909E-4591-A04C-B7807ECE4BAF Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJSWVzbAAoJEKjD27JZ84ywD4cQAJ0KKhWnNylLmAeMpET/gBjQ RvICjTPdE1SWf8DUY5zzsT86Qi0LbYPxjCbaqbzyF1/byFFbWsmO8Of7xE7UjvCz 1zsW5WkbsaAIJBnrTvq2JD+Uvi6vkuoc2LBLpA8EHGrk4q2QvQOJM5h+wjqefS4a 1tnUXFBks9OVuS22C0ytb4bXkOycUJQI0Fa2wwdatG0b/1dwbAJef2Iyi38rDemB JQVTGk0Ex+XeB8hKFU0oeVUP5Il2odeobti5GTE8WoMjuZdUqlHMC3/osc8K4LWW Y6EyO7SQBY28yD6WpOeDo1ApZuk1meatGTQ/YdTMpcfVtRqRT9q+ISv5F9jQqCI6 gKwXl0nEXc25Wd4/6B7teiPvcfMei4GgNfVfb/zFs4fruh20Q16HRAc6bqkb4qmW v7hVmv95N/nj1H4gGopG6oFTa3bIGDckNvBOaKfENVgWM40LM/D5g5VLndfqnq1e nMtS7udRXF0FXsTFj3tyVs3I72341SFjjMFuw5XyPPUDiDR3MOD/Ekfpv3JF/XP1 MBvY1tpvMm/naIzzM2UaRMdXAx25FfTvbQdgeuomcEQqFjwLA3og9RLHZBpZ1tcS OEMb1Zi9AUOtIbjKzPSinrmxCtPjuBl4ybGk908bgcYwSrZLM/FiZ3Dvwiw+WnTx y2uQXpIhZ5c4GZDMhCuH =Zfx1 -----END PGP SIGNATURE----- --Apple-Mail=_95E24EFA-909E-4591-A04C-B7807ECE4BAF-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 16:35:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 40A30AFD for ; Sat, 12 Oct 2013 16:35:12 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C4BFB2596 for ; Sat, 12 Oct 2013 16:35:11 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBD11D.dip0.t-ipconnect.de [93.203.209.29]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r9CGZ9uj062805; Sat, 12 Oct 2013 16:35:09 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id r9CGYqmp013835; Sat, 12 Oct 2013 18:34:57 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r9CGYQRD053340; Sat, 12 Oct 2013 18:34:46 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201310121634.r9CGYQRD053340@fire.js.berklix.net> To: freebsd-current@freebsd.org Subject: Re: May you please add alias for nslookup? From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sat, 12 Oct 2013 12:22:13 BST." <20131012122213.3b21123a@gumby.homeunix.com> Date: Sat, 12 Oct 2013 18:34:26 +0200 Sender: jhs@berklix.com Cc: RW X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 16:35:12 -0000 RW wrote: > On Sat, 12 Oct 2013 10:44:56 +0200 > Ivan Voras wrote: > > > explaning the user what has happened and optionally invoking "host" > > or "dig". > > Actually dig has gone Rather cryptic for me so I looked: dig has gone from current src/usr.bin/dig nslookup & dig & host are all installed by either of current ports/dns/bind99 or ports/dns/bind-tools > and has been replaced by the unbound utility > drill. src/usr.bin/drill/ I agree with O.P. Zhifeng Hu's "this is a very basic tools". Removing src/contrib/bind9 from FreeBSD-10 will get criticised as: "Calls itself a server OS, but no name server out of the box!" Please resist periodic urges to strip src/ towards just a tool set capable of rebuilding itself. Tossing expected tools (even if a port is more up to date & secure) will annoy users, & potential immigrants from other Unixes may try then toss FreeBSD. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Interleave replies below like a play script. Indent old text with "> ". Send plain text, not quoted-printable, HTML, base64, or multipart/alternative. From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 17:41:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 32BF4F24 for ; Sat, 12 Oct 2013 17:41:04 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 061A028A9 for ; Sat, 12 Oct 2013 17:41:03 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D16AB213E2 for ; Sat, 12 Oct 2013 13:40:56 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute5.internal (MEProxy); Sat, 12 Oct 2013 13:40:56 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=uobnQf4CvtRT+Ssfz1WPTAN5AYk=; b=Seu hbWOvhh9UIEePErfSmmRgdOhxfQT/oqgDLp5qbxEq0qjfQKw3OBxO5sF/sKwxwvD QiLr9+9BimNeRbBuVZQoTSZHNqRTQ2jN+eMz01upffAeMT5kc29Rb3vdpP6IK9MM SbRTV1aAafteucMweE4VWX4lGCplzYSWFdbpjYFQ= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id AA62911FC04; Sat, 12 Oct 2013 13:40:56 -0400 (EDT) Message-Id: <1381599656.13750.33215025.2D6F9352@webmail.messagingengine.com> X-Sasl-Enc: Zm176oTvuM5/ViRq10q4rX/V6hRNcN7EtNvspISuZnBO 1381599656 From: Mark Felder To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 In-Reply-To: <201310121634.r9CGYQRD053340@fire.js.berklix.net> References: <201310121634.r9CGYQRD053340@fire.js.berklix.net> Subject: Re: May you please add alias for nslookup? Date: Sat, 12 Oct 2013 12:40:56 -0500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 17:41:04 -0000 On Sat, Oct 12, 2013, at 11:34, Julian H. Stacey wrote: > RW wrote: > > On Sat, 12 Oct 2013 10:44:56 +0200 > > Ivan Voras wrote: > > > > > explaning the user what has happened and optionally invoking "host" > > > or "dig". > > > > Actually dig has gone > > Rather cryptic for me so I looked: > > dig has gone from current src/usr.bin/dig > nslookup & dig & host > are all installed by either of current > ports/dns/bind99 or ports/dns/bind-tools > > > > and has been replaced by the unbound utility > > drill. > > src/usr.bin/drill/ > > > I agree with O.P. Zhifeng Hu's "this is a very basic tools". > > Removing src/contrib/bind9 from FreeBSD-10 will get criticised as: > "Calls itself a server OS, but no name server out of the box!" > > Please resist periodic urges to strip src/ towards just a tool set > capable of rebuilding itself. Tossing expected tools (even if a > port is more up to date & secure) will annoy users, & potential > immigrants from other Unixes may try then toss FreeBSD. > > Cheers, > Julian > -- > Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich > http://berklix.com > Interleave replies below like a play script. Indent old text with "> ". > Send plain text, not quoted-printable, HTML, base64, or > multipart/alternative. > I don't think anyone can explain this better than the last post DES put on his blog about it http://blog.des.no/2013/09/dns-again-a-clarification/ From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 17:57:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D7151990 for ; Sat, 12 Oct 2013 17:57:51 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9799C2947 for ; Sat, 12 Oct 2013 17:57:51 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id q4so3905374qcx.12 for ; Sat, 12 Oct 2013 10:57:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=EuqHYJJhW0BffxrE3Hz4jiMNY+5bik19uhsWZYihkpg=; b=tTM+CNyaB1robDHgpJBb6LEWv/QNXtAJf/+xQOenoZfTI56IsJPL+CMqpNFx1Vg9Cw PHKFXQERJQqoDy1UMNjsaugiGA7G1mey0PtlPCcJghQCXXYwd4WW2Jngjge8xbN+yqRx MZ57wbvhDLaXV/drnzsyLAML9cmfJ4oRs6JtF1i5EvCLHSxShTBE0BgS9ofyZ9oWe96T y3HdOA9iMrvQovNcscI4Jn+TVgkOrSn/4ovdw4Dhwvo823JzXviBKdxXUKr7D9NOiiC6 W0mo6sRKerT2RbJlWXLG1HXTLElPMtj2nilMI5NkN4jjY4dMZPHDLBYz+F3T2BeEWGni eEjQ== X-Received: by 10.224.36.146 with SMTP id t18mr2513023qad.111.1381600670816; Sat, 12 Oct 2013 10:57:50 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Sat, 12 Oct 2013 10:57:10 -0700 (PDT) In-Reply-To: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> References: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> From: Igor Mozolevsky Date: Sat, 12 Oct 2013 18:57:10 +0100 X-Google-Sender-Auth: SF7c3zSrcJ5dIZCLU6tsjYikMvM Message-ID: Subject: Re: May you please add alias for nslookup? To: zhifeng hu Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 17:57:51 -0000 On 12 October 2013 07:10, zhifeng hu wrote: > I am noticed that the nslookup will not appear by default in freebsd 10. > but this is a very basic tools, we need it very much more than you think. > would you please add alias for nslookup ? such as > alias nslookup="host -v" > > NOT FORCE USER TO INSTALL dns/bind-tool > > It's not good for human use experiences. > Hasn't nslookup been deprecated by ISC a long time ago?.. I remember a long time ago when I installed ISC's bind &c that every time I ran nslookup I got a massive notice stating that nslookup's been deprecated and I should use dig instead.... -- Igor M. From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 17:59:38 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 328E1B91 for ; Sat, 12 Oct 2013 17:59:38 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E84202965 for ; Sat, 12 Oct 2013 17:59:37 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id v1so1245552qcw.19 for ; Sat, 12 Oct 2013 10:59:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=8DQVrBezrYznyAzW5aHeDH88KnMCda3ZWkd39BE29kY=; b=kPX6OdGJbHRMj+m8g5TYvfgNR0bcT6sSbZafQpsU59T8lKUY2sK/sPrRDWp86ZzSfH O7SCIHtvpxv4GlbPSSs0GdIYL97Y9xY+p55KQw+Xj/x8u7XmF8z7zzle/bcKK/WEuScX U6lLMHiwMP8X5i7Gjmtt9nrqK78flUBl1hDDB77c3YcK5Jv4tyyXaWQ8y2fjAqci+czk C7YoBTLdY7+g48rAoi+1FfgSfoqQCtVVgiC0fX2duKFsxqqT3/txaNuBpmyrEjVYoe59 HSCdoMoeSS6Y9YpKcUparlwArgXAgSEuWzCmLUEnCBBbGoBvHcSZPSMQoqDlgga2aSyU hFAA== X-Received: by 10.224.165.12 with SMTP id g12mr11827612qay.89.1381600776679; Sat, 12 Oct 2013 10:59:36 -0700 (PDT) MIME-Version: 1.0 Sender: mozolevsky@gmail.com Received: by 10.224.112.138 with HTTP; Sat, 12 Oct 2013 10:58:56 -0700 (PDT) In-Reply-To: References: <52DAE42E-7A58-4A38-9FF4-3DF51866057D@ancientrocklab.com> From: Igor Mozolevsky Date: Sat, 12 Oct 2013 18:58:56 +0100 X-Google-Sender-Auth: nAhuYw24FlGgiSh1u909AaTx9jA Message-ID: Subject: Re: May you please add alias for nslookup? To: zhifeng hu Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 17:59:38 -0000 On 12 October 2013 18:57, Igor Mozolevsky wrote: > > > > On 12 October 2013 07:10, zhifeng hu wrote: > >> I am noticed that the nslookup will not appear by default in freebsd 10. >> but this is a very basic tools, we need it very much more than you think. >> would you please add alias for nslookup ? such as >> alias nslookup="host -v" >> >> NOT FORCE USER TO INSTALL dns/bind-tool >> >> It's not good for human use experiences. >> > > Hasn't nslookup been deprecated by ISC a long time ago?.. I remember a > long time ago when I installed ISC's bind &c that every time I ran nslookup > I got a massive notice stating that nslookup's been deprecated and I should > use dig instead.... > This is the message: Note: nslookup is deprecated and may be removed from future releases. Consider using the 'dig' or 'host' programs instead. Run nslookup with the '-sil[ent]' option to prevent this message from appearing. -- Igor M. From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 18:18:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3AB423C5 for ; Sat, 12 Oct 2013 18:18:06 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 17CB92A3D for ; Sat, 12 Oct 2013 18:18:05 +0000 (UTC) Received: from [192.168.1.105] (S01060015e9b562c7.hm.shawcable.net [50.70.17.171]) (Authenticated sender: roleaccount@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id B168031F31 for ; Sat, 12 Oct 2013 18:18:04 +0000 (UTC) Message-ID: <5259925C.4030709@allanjude.com> Date: Sat, 12 Oct 2013 14:18:04 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: May you please add alias for nslookup? References: <201310121634.r9CGYQRD053340@fire.js.berklix.net> In-Reply-To: <201310121634.r9CGYQRD053340@fire.js.berklix.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 18:18:06 -0000 On 2013-10-12 12:34, Julian H. Stacey wrote: > RW wrote: >> On Sat, 12 Oct 2013 10:44:56 +0200 >> Ivan Voras wrote: >> >>> explaning the user what has happened and optionally invoking "host" >>> or "dig". >> Actually dig has gone > Rather cryptic for me so I looked: > > dig has gone from current src/usr.bin/dig > nslookup & dig & host > are all installed by either of current > ports/dns/bind99 or ports/dns/bind-tools > > >> and has been replaced by the unbound utility >> drill. > src/usr.bin/drill/ > > > I agree with O.P. Zhifeng Hu's "this is a very basic tools". > > Removing src/contrib/bind9 from FreeBSD-10 will get criticised as: > "Calls itself a server OS, but no name server out of the box!" > > Please resist periodic urges to strip src/ towards just a tool set > capable of rebuilding itself. Tossing expected tools (even if a > port is more up to date & secure) will annoy users, & potential > immigrants from other Unixes may try then toss FreeBSD. > > Cheers, > Julian It is easier to keep bind up to date from ports. If you want DNSSEC support in 9, you have to replace the bind in base anyway.... bind is replaced with unbound, which providers most of the functionality required in most instances. I forget the exact numbers, but when I looked about 20 of the security advisories over the last 10 years have been because of bind. That is over 12% of all vulnerabilities. -- -- Allan Jude From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 18:25:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B95A473E for ; Sat, 12 Oct 2013 18:25:13 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 967112AA1 for ; Sat, 12 Oct 2013 18:25:12 +0000 (UTC) Received: from [192.168.1.105] (S01060015e9b562c7.hm.shawcable.net [50.70.17.171]) (Authenticated sender: roleaccount@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id D101731F5E for ; Sat, 12 Oct 2013 18:25:11 +0000 (UTC) Message-ID: <52599408.7060306@allanjude.com> Date: Sat, 12 Oct 2013 14:25:12 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: May you please add alias for nslookup? References: <201310121634.r9CGYQRD053340@fire.js.berklix.net> <5259925C.4030709@allanjude.com> In-Reply-To: <5259925C.4030709@allanjude.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 18:25:13 -0000 On 2013-10-12 14:18, Allan Jude wrote: > On 2013-10-12 12:34, Julian H. Stacey wrote: >> RW wrote: >>> On Sat, 12 Oct 2013 10:44:56 +0200 >>> Ivan Voras wrote: >>> >>>> explaning the user what has happened and optionally invoking "host" >>>> or "dig". >>> Actually dig has gone >> Rather cryptic for me so I looked: >> >> dig has gone from current src/usr.bin/dig >> nslookup & dig & host >> are all installed by either of current >> ports/dns/bind99 or ports/dns/bind-tools >> >> >>> and has been replaced by the unbound utility >>> drill. >> src/usr.bin/drill/ >> >> >> I agree with O.P. Zhifeng Hu's "this is a very basic tools". >> >> Removing src/contrib/bind9 from FreeBSD-10 will get criticised as: >> "Calls itself a server OS, but no name server out of the box!" >> >> Please resist periodic urges to strip src/ towards just a tool set >> capable of rebuilding itself. Tossing expected tools (even if a >> port is more up to date & secure) will annoy users, & potential >> immigrants from other Unixes may try then toss FreeBSD. >> >> Cheers, >> Julian > It is easier to keep bind up to date from ports. If you want DNSSEC > support in 9, you have to replace the bind in base anyway.... > > bind is replaced with unbound, which providers most of the functionality > required in most instances. > > I forget the exact numbers, but when I looked about 20 of the security > advisories over the last 10 years have been because of bind. That is > over 12% of all vulnerabilities. > des@'s blog adds another important point, bind10 required python. FreeBSD doesn't want to ship with python in base, so keeping bind wasn't really an option From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 19:42:19 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4C961D4; Sat, 12 Oct 2013 19:42:19 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B9D582DC9; Sat, 12 Oct 2013 19:42:18 +0000 (UTC) Received: from alph.d.allbsd.org (p4181-ipbf1307funabasi.chiba.ocn.ne.jp [123.225.173.181]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r9CJg0el099188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 13 Oct 2013 04:42:10 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.7/8.14.5) with ESMTP id r9CJfxf9093932; Sun, 13 Oct 2013 04:42:00 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sun, 13 Oct 2013 04:40:58 +0900 (JST) Message-Id: <20131013.044058.1382656329747589715.hrs@allbsd.org> To: current@FreeBSD.org Subject: Problems with rc.d/jail change (Re: svn commit: r256256 - in head: . etc etc/defaults etc/rc.d share/man/man5 usr.sbin/jail) From: Hiroki Sato In-Reply-To: <4B2ECC28-4F63-448A-B99E-DC5215C5FFD0@freebsd.org> References: <20131011141214.GA91989@mouf.net> <4B2ECC28-4F63-448A-B99E-DC5215C5FFD0@freebsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart0(Sun_Oct_13_04_40_58_2013_802)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Sun, 13 Oct 2013 04:42:10 +0900 (JST) X-Spam-Status: No, score=-97.1 required=13.0 tests=CONTENT_TYPE_PRESENT, ONLY1HOPDIRECT,SAMEHELOBY2HOP,SPF_SOFTFAIL,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: swills@FreeBSD.org, remko@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 19:42:19 -0000 ----Security_Multipart0(Sun_Oct_13_04_40_58_2013_802)-- Content-Type: Multipart/Mixed; boundary="--Next_Part(Sun_Oct_13_04_40_58_2013_119)--" Content-Transfer-Encoding: 7bit ----Next_Part(Sun_Oct_13_04_40_58_2013_119)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Remko Lodder wrote in <4B2ECC28-4F63-448A-B99E-DC5215C5FFD0@freebsd.org>: re> re> On Oct 11, 2013, at 4:12 PM, Steve Wills wrote: re> re> > I'm having the same issue. re> re> I am working with Hiroki to resolve this. So far his work seems to fix re> this, he will commit that as soon as we can reasonable think re> that this is OK (and it looks that way :)) Let me summarize what I noticed so far: (1) A jail with jail_fdescfs_enable="YES" fails to start. (2) A jail with multiple parameters in jail_parameters="..." fails to start. (1) was fixed in r256385. The attached patch should fix (2). Please try it if you still have a problem. Jail configurations can be complex, so there may be some more cases which break the old behaviors. Please send me your report if you have differences between before and after the rc.d/jail change. -- Hiroki ----Next_Part(Sun_Oct_13_04_40_58_2013_119)-- Content-Type: Text/X-Patch; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="jail_20131013-1.diff" Index: etc/rc.d/jail =================================================================== --- etc/rc.d/jail (revision 256385) +++ etc/rc.d/jail (working copy) @@ -94,7 +94,7 @@ # parse_options() { - local _j + local _j _p _j=$1 _confwarn=0 @@ -234,7 +234,9 @@ "\"procfs ${_rootdir%/}/proc procfs rw 0 0\";" fi - echo " ${_parameters};" + for _p in $_parameters; do + echo " ${_p%\;};" + done eval : \${jail_${_j}_mount_enable:=${jail_mount_enable:-NO}} if checkyesno jail_${_j}_mount_enable; then ----Next_Part(Sun_Oct_13_04_40_58_2013_119)---- ----Security_Multipart0(Sun_Oct_13_04_40_58_2013_802)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlJZpcoACgkQTyzT2CeTzy3EsACfX+GXWCd2KLwXnY81fpLJAyDv dvQAoLHiNhZtA1zFWHbmqCOTCzkGtK/m =OsnO -----END PGP SIGNATURE----- ----Security_Multipart0(Sun_Oct_13_04_40_58_2013_802)---- From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 20:05:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7FD4E889 for ; Sat, 12 Oct 2013 20:05:28 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 477422EB5 for ; Sat, 12 Oct 2013 20:05:28 +0000 (UTC) Received: by mail-ob0-f179.google.com with SMTP id wp18so3754969obc.38 for ; Sat, 12 Oct 2013 13:05:27 -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=WDlQkQAgOH1QHOOC1M81Lv+k+fEnp8w3gnYmsdKrKqE=; b=C0KXkktKlYfUHxbAvCd7JgOTdHkv6pIPhzhwNc4MpZkJANGfczhRc7I5flp8uPilIX xafpj/YNGmcNzrcGrF5mXe1XCe0swT7EJptjWGPoQlTEhJ0jKxDlMr3BJBxALrVk3SzR oVhtZY8b3+rmOAfA/uU5F3TnAt2P9nLJnuDO7jO9rwvZSPn1xomRzNcbwnnBzuOZrokQ kB1YbFf7ocTmBE2GGppCEstEAZ0vHzH+Crl4NmQVwgH8EGWbR/Iz5E+L0OAQdB4eLAay 3jIJHVcDqU+vVbxiCxcLOekh6vRbyeTDGJQ1nmOf3rLZDV2HZMGs7nMkkkk0NiHoonNo iaiA== MIME-Version: 1.0 X-Received: by 10.182.18.9 with SMTP id s9mr12851404obd.15.1381608327358; Sat, 12 Oct 2013 13:05:27 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Sat, 12 Oct 2013 13:05:27 -0700 (PDT) In-Reply-To: <20131012032258.GA98799@troutmask.apl.washington.edu> References: <20131010013338.GA10499@troutmask.apl.washington.edu> <20131012032258.GA98799@troutmask.apl.washington.edu> Date: Sat, 12 Oct 2013 16:05:27 -0400 Message-ID: Subject: Re: /usr/src/lib/msun errors From: Joe Nosay To: Steve Kargl Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 20:05:28 -0000 I was rebuilding world using an older CURRENT base and the src from 10/07/13. The build kept breaking with libiconv, msun, and a few others. This affected both the base and 3rd party. The system is still usable but it isn't stable enough for building a 3rd party application. If I reinstall the base with CURRENT from 10/07/13 to present, will it be stable enough for building 3rd party? I had tried to extract /base and others to the system while running it. I did not extract from an ISO/img to a cleanly formatted system. On Fri, Oct 11, 2013 at 11:22 PM, Steve Kargl < sgk@troutmask.apl.washington.edu> wrote: > On Fri, Oct 11, 2013 at 10:05:56PM -0400, Joe Nosay wrote: > > Is the ALPHA base stable enough to do porting of applications? > > > > Huh? What do you mean? People have been running freebsd-current > for years and porting applications to FreeBSD. Alpha is simply > a point in time for freebsd-current. > > -- > Steve > From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 21:27:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 37E97732 for ; Sat, 12 Oct 2013 21:27:22 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F09722189 for ; Sat, 12 Oct 2013 21:27:21 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id wn1so3716998obc.25 for ; Sat, 12 Oct 2013 14:27:21 -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=v+pGDkWBePeGQ/QFzA3orYFtEp410ylrYyUvjIY/iUU=; b=GIqFOKjGkmEs5YiVT6dnA75objVdCBGd+ZmQ4mKJF+REGSH5CEgy0o1JJDYOQs/ouA QygIAcxlfD1hpIIteMtb0Z5MybrRetgcze1kjGDdhE9cw56MLcNiIzRyN6HWrSTkoE54 GUjScrXyeCrTwrLY9ddU00QyeBu2DN6XAQpg1Ew5+7/5fNgCKq8/mUIPsuG1k/fyoUJo 9rCRkosTyUAPTc150vM7UR+BAk6PBZEo0rhsAhj2p94ZSaRfXuiGDvwcz1PmYmMprFmV UbzIwUY78aKzz1WVJNOZ2eJqV+C4e7r73cvtivto/RdhiBojVPDMggNwWo3F387lz7zE 968A== MIME-Version: 1.0 X-Received: by 10.60.116.230 with SMTP id jz6mr20923442oeb.21.1381613241250; Sat, 12 Oct 2013 14:27:21 -0700 (PDT) Received: by 10.76.106.83 with HTTP; Sat, 12 Oct 2013 14:27:21 -0700 (PDT) In-Reply-To: References: <20131010013338.GA10499@troutmask.apl.washington.edu> <20131012032258.GA98799@troutmask.apl.washington.edu> Date: Sat, 12 Oct 2013 17:27:21 -0400 Message-ID: Subject: Re: /usr/src/lib/msun errors From: Joe Nosay To: Steve Kargl Content-Type: multipart/mixed; boundary=089e0115e84a76391d04e891e6d0 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 21:27:22 -0000 --089e0115e84a76391d04e891e6d0 Content-Type: text/plain; charset=ISO-8859-1 There. On Sat, Oct 12, 2013 at 4:05 PM, Joe Nosay wrote: > I was rebuilding world using an older CURRENT base and the src from > 10/07/13. The build kept breaking with libiconv, msun, and a few others. > This affected both the base and 3rd party. The system is still usable but > it isn't stable enough for building a 3rd party application. If I reinstall > the base with CURRENT from 10/07/13 to present, will it be stable enough > for building 3rd party? I had tried to extract /base and others to the > system while running it. I did not extract from an ISO/img to a cleanly > formatted system. > > > On Fri, Oct 11, 2013 at 11:22 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > >> On Fri, Oct 11, 2013 at 10:05:56PM -0400, Joe Nosay wrote: >> > Is the ALPHA base stable enough to do porting of applications? >> > >> >> Huh? What do you mean? People have been running freebsd-current >> for years and porting applications to FreeBSD. Alpha is simply >> a point in time for freebsd-current. >> >> -- >> Steve >> > > --089e0115e84a76391d04e891e6d0 Content-Type: text/plain; charset=US-ASCII; name="CURRENT-errrors.txt" Content-Disposition: attachment; filename="CURRENT-errrors.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_hmpal0a10 JCBseW54Ci91c3IvbG9jYWwvbGliL2xpYmludGwuc28uOTogVW5kZWZpbmVkIHN5bWJvbCAibGli aWNvbnZfc2V0X3JlbG9jYXRpb25fcHJlZml4IgokIAokIGZpcmVmb3gKWFBDT01HbHVlTG9hZCBl cnJvciBmb3IgZmlsZSAvdXNyL2xvY2FsL2xpYi9maXJlZm94L2xpYnhwY29tLnNvOgovdXNyL2xv Y2FsL2xpYi9saWJnbGliLTIuMC5zby4wOiBVbmRlZmluZWQgc3ltYm9sICJsaWJpY29udiIKQ291 bGRuJ3QgbG9hZCBYUENPTS4KJCAKCg== --089e0115e84a76391d04e891e6d0-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 21:34:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 64A5B867 for ; Sat, 12 Oct 2013 21:34:03 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1D02721D8 for ; Sat, 12 Oct 2013 21:34:03 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::5b6:2bc4:207a:ab3b] (unknown [IPv6:2001:7b8:3a7:0:5b6:2bc4:207a:ab3b]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 8B3945C44; Sat, 12 Oct 2013 23:33:57 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_370759FB-35D0-4B5F-A203-F3A90747D393"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: /usr/src/lib/msun errors From: Dimitry Andric In-Reply-To: Date: Sat, 12 Oct 2013 23:33:45 +0200 Message-Id: References: <20131010013338.GA10499@troutmask.apl.washington.edu> <20131012032258.GA98799@troutmask.apl.washington.edu> To: Joe Nosay X-Mailer: Apple Mail (2.1510) Cc: freebsd-current , Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 21:34:03 -0000 --Apple-Mail=_370759FB-35D0-4B5F-A203-F3A90747D393 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On Oct 12, 2013, at 23:27, Joe Nosay wrote: > $ lynx > /usr/local/lib/libintl.so.9: Undefined symbol = "libiconv_set_relocation_prefix" > $=20 > $ firefox > XPCOMGlueLoad error for file /usr/local/lib/firefox/libxpcom.so: > /usr/local/lib/libglib-2.0.so.0: Undefined symbol "libiconv" > Couldn't load XPCOM. Please read the 20130904 entry in /usr/ports/UPDATING. --Apple-Mail=_370759FB-35D0-4B5F-A203-F3A90747D393 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) iEYEARECAAYFAlJZwD8ACgkQsF6jCi4glqOCMQCePbClaUzEX9i+GehU36PCMp25 kD4Anj6EQccFNIO+iRCdKCLMIj95b5LV =MfAM -----END PGP SIGNATURE----- --Apple-Mail=_370759FB-35D0-4B5F-A203-F3A90747D393-- From owner-freebsd-current@FreeBSD.ORG Sat Oct 12 21:57:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id B94FAD85 for ; Sat, 12 Oct 2013 21:57:35 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 94B6722C9 for ; Sat, 12 Oct 2013 21:57:35 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.7/8.14.7) with ESMTP id r9CLvTaC002958; Sat, 12 Oct 2013 14:57:29 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.7/8.14.7/Submit) id r9CLvTln002957; Sat, 12 Oct 2013 14:57:29 -0700 (PDT) (envelope-from sgk) Date: Sat, 12 Oct 2013 14:57:29 -0700 From: Steve Kargl To: Joe Nosay Subject: Re: /usr/src/lib/msun errors Message-ID: <20131012215729.GA2932@troutmask.apl.washington.edu> References: <20131010013338.GA10499@troutmask.apl.washington.edu> <20131012032258.GA98799@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Oct 2013 21:57:35 -0000 Please, do not top post. It loses context. On Sat, Oct 12, 2013 at 04:05:27PM -0400, Joe Nosay wrote: > > On Fri, Oct 11, 2013 at 11:22 PM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > On Fri, Oct 11, 2013 at 10:05:56PM -0400, Joe Nosay wrote: > > > Is the ALPHA base stable enough to do porting of applications? > > > > > > > Huh? What do you mean? People have been running freebsd-current > > for years and porting applications to FreeBSD. Alpha is simply > > a point in time for freebsd-current. > > I was rebuilding world using an older CURRENT base and the src from > 10/07/13. The build kept breaking with libiconv, msun, and a few others. The problem you had with msun was caused by you adding additional options to CFLAGS in make.conf without actually understand what those options may do. > This affected both the base and 3rd party. The system is still usable but > it isn't stable enough for building a 3rd party application. Yes, it is stable enough. Remove your custom CFLAG options. > If I reinstall the base with CURRENT from 10/07/13 to present, will > it be stable enough for building 3rd party? Of course. But, you need to read src/UPDATING and ports/UPDATING. -- Steve