From owner-freebsd-arch@FreeBSD.ORG Sun Oct 1 10:11:48 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77E1E16A412 for ; Sun, 1 Oct 2006 10:11:48 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BED843D46 for ; Sun, 1 Oct 2006 10:11:47 +0000 (GMT) (envelope-from matteo@freebsd.org) Received: from kaiser.sig11.org (87.2.178.234) by vsmtp3.tin.it (7.2.072.1) id 451BEC08001FFC1E for freebsd-arch@freebsd.org; Sun, 1 Oct 2006 12:11:46 +0200 Received: from kaiser.sig11.org (localhost [127.0.0.1]) by kaiser.sig11.org (8.13.8/8.13.7) with ESMTP id k91ABi8M094720 for ; Sun, 1 Oct 2006 12:11:45 +0200 (CEST) (envelope-from matteo@freebsd.org) Received: (from rionda@localhost) by kaiser.sig11.org (8.13.8/8.13.7/Submit) id k91ABhVJ094719 for freebsd-arch@freebsd.org; Sun, 1 Oct 2006 12:11:43 +0200 (CEST) (envelope-from matteo@freebsd.org) X-Authentication-Warning: kaiser.sig11.org: rionda set sender to matteo@freebsd.org using -f Date: Sun, 1 Oct 2006 12:11:43 +0200 From: Matteo Riondato To: freebsd-arch@freebsd.org Message-ID: <20061001101143.GB94004@kaiser.sig11.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pZs/OQEoSSbxGlYw" Content-Disposition: inline User-Agent: Mutt/1.5.12-2006-07-14 Subject: RFC: use of mdmfs "new" options in fstab X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Oct 2006 10:11:48 -0000 --pZs/OQEoSSbxGlYw Content-Type: multipart/mixed; boundary="JWEK1jqKZ6MHAcjA" Content-Disposition: inline --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, I'm writing to ask for comments about the following proposal. During the years, mdmfs(8) has got many options which are not available in the "mount_mfs" compatibility mode (activated by specifing -C on the command line or by calling mount_mfs). This means that it's impossible to use mdmfs "new" option in fstab, which is quite limiting. I think there are two possibilities to solve this: 1) install mdmfs as mount_md (or mount_$something) and teach mount to recognize it. See attached mdmfsmakefile_mount.c.diff . This will allow to specify the following line in fstab (the -P option is not available in compatability mode): md /usr/jail/jail1 md ro,-P,-F/usr/jailmd/jail1.md 0 0 2)disable bug-for-bug compatibility with mount_mfs when the program name is "mount_mfs" or "mfs". The "-C" otion will still be available for those who want compatibility. See attached mdmfs.c.diff . I would prefer option #2, but any comment is really appreciated. Thanks in advance Best regards --=20 Matteo Riondato FreeBSD Committer (http://www.freebsd.org) G.U.F.I. Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org) --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mdmfsmakefile_mount.c.diff" Content-Transfer-Encoding: quoted-printable Index: mdmfs/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/rionda/branch/ncvs/src/sbin/mdmfs/Makefile,v retrieving revision 1.6 diff -u -r1.6 Makefile --- mdmfs/Makefile 25 Jan 2005 14:28:31 -0000 1.6 +++ mdmfs/Makefile 1 Oct 2006 09:03:47 -0000 @@ -2,8 +2,10 @@ =20 PROG=3D mdmfs LINKS=3D ${BINDIR}/${PROG} ${BINDIR}/mount_mfs +LINKS+=3D ${BINDIR}/${PROG} ${BINDIR}/mount_md MAN=3D mdmfs.8 MLINKS+=3D mdmfs.8 mount_mfs.8 +MLINKS+=3D mdmfs.8 mount_md.8 WARNS?=3D 6 =20 .include Index: mount/mount.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 RCS file: /home/rionda/branch/ncvs/src/sbin/mount/mount.c,v retrieving revision 1.88 diff -u -r1.88 mount.c --- mount/mount.c 12 Jul 2006 16:05:51 -0000 1.88 +++ mount/mount.c 1 Oct 2006 08:47:09 -0000 @@ -132,7 +132,7 @@ */ unsigned int i; const char *fs[] =3D { - "cd9660", "mfs", "msdosfs", "nfs", "nfs4", "ntfs", + "cd9660", "md", "mfs", "msdosfs", "nfs", "nfs4", "ntfs", "nwfs", "nullfs", "portalfs", "smbfs", "udf", "umapfs", "unionfs", NULL --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mdmfs.c.diff" Content-Transfer-Encoding: quoted-printable Index: mdmfs.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 RCS file: /home/rionda/branch/ncvs/src/sbin/mdmfs/mdmfs.c,v retrieving revision 1.27 diff -u -r1.27 mdmfs.c --- mdmfs.c 16 Feb 2006 21:28:54 -0000 1.27 +++ mdmfs.c 1 Oct 2006 10:08:31 -0000 @@ -117,11 +117,6 @@ newfs_arg =3D strdup(""); mount_arg =3D strdup(""); =20 - /* If we were started as mount_mfs or mfs, imply -C. */ - if (strcmp(getprogname(), "mount_mfs") =3D=3D 0 || - strcmp(getprogname(), "mfs") =3D=3D 0) - compat =3D true; - while ((ch =3D getopt(argc, argv, "a:b:Cc:Dd:E:e:F:f:hi:LlMm:Nn:O:o:Pp:Ss:t:Uv:w:X")) !=3D -1) switch (ch) { --JWEK1jqKZ6MHAcjA-- --pZs/OQEoSSbxGlYw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFH5Rf2Mp4pR7Fa+wRAoM8AKDFO7P3OB5HXXL4Fsx6Dx9meXbl9QCfTTOq VQRfLuLWiN4jU9cQyc7+tKE= =FeFT -----END PGP SIGNATURE----- --pZs/OQEoSSbxGlYw-- From owner-freebsd-arch@FreeBSD.ORG Mon Oct 2 07:46:42 2006 Return-Path: X-Original-To: arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3762B16A407 for ; Mon, 2 Oct 2006 07:46:42 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx0.rink.nu (thunderstone.rink.nu [80.112.228.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4AC343D53 for ; Mon, 2 Oct 2006 07:46:41 +0000 (GMT) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx0.rink.nu (Postfix) with ESMTP id 3A4A317011 for ; Mon, 2 Oct 2006 09:47:03 +0200 (CEST) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx0.rink.nu ([127.0.0.1]) by localhost (thunderstone.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9m1zigjfDLN0 for ; Mon, 2 Oct 2006 09:47:00 +0200 (CEST) Received: by mx0.rink.nu (Postfix, from userid 1000) id E1AA717072; Mon, 2 Oct 2006 09:46:59 +0200 (CEST) Date: Mon, 2 Oct 2006 09:46:59 +0200 From: Rink Springer To: arch@FreeBSD.org Message-ID: <20061002074659.GA26895@rink.nu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: [RFC] mountd(8) patch to prevent flag removal X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Oct 2006 07:46:42 -0000 --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, At work, we recently moved our local webserver storage (which was plain UFS along with the SUIDDIR mount option) to a separate NFS server. However, upon NFS-exporting the filesystem from the NFS server (where it was mounted usin= g -o suiddir as well), this flag would vanish. It turns out that this is due to a refactoring in mountd(8). I initially ma= iled Craig Rodrigues about this, who did the refactoring, but I haven't received= any reply. The problem is introduced in usr.sbin/mountd/mountd.c revision 1.81.2.2; it uses nmount(2) with a flags argument of 0 to remount the filesystem. Unfortunately, this means any specific mount-flags are removed from the filesystem. The patch to fix this is at http://rink.nu/tmp/mountd.c.diff; which I'd like to commit to -HEAD and MFC later on. Would anyone be so kind to review this? Thanks, --=20 Rink P.W. Springer - http://rink.nu "When will the internet move from 64Kb max .com domains to .exe domains which can use much more memory?" - Edwin Groothuis --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFIMPzb3O60uztv/8RAp1CAJ45TaNLQsPR9NN8tPJl8IFGgfPY1ACgsksl 6tioGlPzSUan1uO3hXGhd3o= =l+UN -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- From owner-freebsd-arch@FreeBSD.ORG Tue Oct 3 23:27:20 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B8B216A403 for ; Tue, 3 Oct 2006 23:27:20 +0000 (UTC) (envelope-from thompsa@freebsd.org) Received: from grunt5.ihug.co.nz (grunt5.ihug.co.nz [203.109.254.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 381AB43D49 for ; Tue, 3 Oct 2006 23:27:19 +0000 (GMT) (envelope-from thompsa@freebsd.org) Received: from 203-109-251-39.static.bliink.ihug.co.nz (heff.fud.org.nz) [203.109.251.39] by grunt5.ihug.co.nz with esmtp (Exim 3.35 #1 (Debian)) id 1GUtfR-0002vU-00; Wed, 04 Oct 2006 12:27:17 +1300 Received: by heff.fud.org.nz (Postfix, from userid 1001) id DF9A21CC25; Wed, 4 Oct 2006 12:27:16 +1300 (NZDT) Date: Wed, 4 Oct 2006 12:27:16 +1300 From: Andrew Thompson To: arch@freebsd.org Message-ID: <20061003232716.GJ21444@heff.fud.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: where to put extra RSTP info X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2006 23:27:20 -0000 Hi, The new RSTP code I have been working on has more info that can be shown and tweaked by the network admin when setting up the layer2 topo. I now have the problem of what utility to stuff it into. a) ifconfig b) netstat c) some new util like bridgestat I realise that ifconfig is for setting the interface config and should not be abused. I am tempted to add a new util, here is an example of what I need to show. Spanning Tree Parameters for bridge0 Protocol : IEEE 802.1W (Rapid STP), Priority : 32768 (0x8000), Bridge ID : 8000-00:d0:95:8e:56:7e, Designated Root : 8000-00:04:75:d1:f8:98, Cost to Root Bridge : 0, Root Port : None, Next Best Root Cost : 100, Next Best Root Port : 8000-00:d0:95:aa:bb:cc, Hold Time : 1, Topology Changes : 98, Topology age : 5:02:36 Interface 1 Role : Designated Link type : Point to Point ... Interface 2 Role : Alternate Link type : Shared ... Any suggestions? Andrew From owner-freebsd-arch@FreeBSD.ORG Tue Oct 3 23:47:12 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E7BB16A412; Tue, 3 Oct 2006 23:47:12 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4F5243D7B; Tue, 3 Oct 2006 23:46:58 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.186.220] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis), id 0MKwh2-1GUtyT1qxW-000138; Wed, 04 Oct 2006 01:46:57 +0200 From: Max Laier Organization: FreeBSD To: Andrew Thompson Date: Wed, 4 Oct 2006 01:46:50 +0200 User-Agent: KMail/1.9.4 References: <20061003232716.GJ21444@heff.fud.org.nz> In-Reply-To: <20061003232716.GJ21444@heff.fud.org.nz> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6171035.DySEkAkHLK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200610040146.56246.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-arch@freebsd.org Subject: Re: where to put extra RSTP info X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2006 23:47:12 -0000 --nextPart6171035.DySEkAkHLK Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 04 October 2006 01:27, Andrew Thompson wrote: > The new RSTP code I have been working on has more info that can be > shown and tweaked by the network admin when setting up the layer2 topo. > I now have the problem of what utility to stuff it into. > > a) ifconfig > b) netstat > c) some new util like bridgestat > > I realise that ifconfig is for setting the interface config and should > not be abused. I don't think this is true anymore. Our ifconfig has moved to a more=20 complex management app since the merge with wicontrol (or since we=20 imported wicontrol functionality into ifconfig) - and I think this is a=20 good trend. Instead of having many different config apps for each type=20 of interface. You could hide the less interesting information behind -v=20 or a new switch in order to not pollute ifconfig's default use case too=20 much. > I am tempted to add a new util, here is an example of > what I need to show. > > Spanning Tree Parameters for bridge0 > Protocol : IEEE 802.1W (Rapid STP), > Priority : 32768 (0x8000), > Bridge ID : 8000-00:d0:95:8e:56:7e, > Designated Root : 8000-00:04:75:d1:f8:98, > Cost to Root Bridge : 0, > Root Port : None, > Next Best Root Cost : 100, > Next Best Root Port : 8000-00:d0:95:aa:bb:cc, > Hold Time : 1, > Topology Changes : 98, > Topology age : 5:02:36 > > Interface 1 > Role : Designated > Link type : Point to Point > ... > > Interface 2 > Role : Alternate > Link type : Shared > ... At least the short per-interface status certainly belongs into ifconfig's=20 default output - IMHO. > Any suggestions? I'd go for a new switch to ifconfig, that takes an interface name as=20 (optional) argument and then prints above information (for the bridge=20 specified in the argument). =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart6171035.DySEkAkHLK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFIvZwXyyEoT62BG0RAoaPAJ9RrWXCGKWf4MEX/EirmQ9lunY14gCcDwjK 39+DaaNylErKY4iDriXyjqY= =kRY0 -----END PGP SIGNATURE----- --nextPart6171035.DySEkAkHLK-- From owner-freebsd-arch@FreeBSD.ORG Wed Oct 4 02:47:00 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F6DA16A403; Wed, 4 Oct 2006 02:47:00 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1238343D4C; Wed, 4 Oct 2006 02:46:59 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k942kxof035445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Oct 2006 19:46:59 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <452320A2.9070103@errno.com> Date: Tue, 03 Oct 2006 19:46:58 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: Andrew Thompson References: <20061003232716.GJ21444@heff.fud.org.nz> In-Reply-To: <20061003232716.GJ21444@heff.fud.org.nz> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org Subject: Re: where to put extra RSTP info X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2006 02:47:00 -0000 Andrew Thompson wrote: > Hi, > > > The new RSTP code I have been working on has more info that can be shown > and tweaked by the network admin when setting up the layer2 topo. I now > have the problem of what utility to stuff it into. > > a) ifconfig > b) netstat > c) some new util like bridgestat > > I realise that ifconfig is for setting the interface config and should > not be abused. I am tempted to add a new util, here is an example of > what I need to show. > > Spanning Tree Parameters for bridge0 > Protocol : IEEE 802.1W (Rapid STP), > Priority : 32768 (0x8000), > Bridge ID : 8000-00:d0:95:8e:56:7e, > Designated Root : 8000-00:04:75:d1:f8:98, > Cost to Root Bridge : 0, > Root Port : None, > Next Best Root Cost : 100, > Next Best Root Port : 8000-00:d0:95:aa:bb:cc, > Hold Time : 1, > Topology Changes : 98, > Topology age : 5:02:36 > > Interface 1 > Role : Designated > Link type : Point to Point > ... > > Interface 2 > Role : Alternate > Link type : Shared > ... > > > Any suggestions? Tweaking parameters definitely belongs in ifconfig. If the information to report falls into the area of "status" then it too belongs in ifconfig. Other stuff is a hard call. I stuck a bunch of 802.11-related status display that could also go someplace like netstat into ifconfig and noone's complained so I guess it's been acceptable. I've been working to unify network interface-related manipulation work under a single application (ifconfig) so people don't need to search for the appropriate program. I did this after getting frustrated with tool sets in other os's (e.g. linux's iw* apps). However dynamic status reporting kinda feels like it belongs elsewhere (e.g. netstat). Some things like "list stations" and "list scan" that are present in ifconfig may not belong but were stuck there because it's a natural spot for folks coming from linux and the structure minimized code duplication. Sam From owner-freebsd-arch@FreeBSD.ORG Wed Oct 4 08:41:52 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3778B16A403 for ; Wed, 4 Oct 2006 08:41:52 +0000 (UTC) (envelope-from eirikald@pvv.ntnu.no) Received: from decibel.pvv.ntnu.no (decibel.pvv.ntnu.no [129.241.210.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89C5543D4C for ; Wed, 4 Oct 2006 08:41:50 +0000 (GMT) (envelope-from eirikald@pvv.ntnu.no) Received: from decibel.pvv.ntnu.no ([129.241.210.179] helo=litenbug.ycoll.com ident=eirikald) by decibel.pvv.ntnu.no with esmtp (Exim 4.60) (envelope-from ) id 1GV2K2-0007Mr-VK; Wed, 04 Oct 2006 10:41:48 +0200 Date: Wed, 4 Oct 2006 10:41:44 +0200 From: "Eirik A. Nygaard" To: Alexander Leidinger Message-ID: <20061004084144.GA673@litenbug.ycoll.com> References: <29073890609261304o777fd0fajecf43d10fc181177@mail.gmail.com> <20060927101733.pejhm56h0ks4cssk@webmail.leidinger.net> <20060927194837.GA14902@stud.ntnu.no> <20060928072349.0009n2tr9cwskswc@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060928072349.0009n2tr9cwskswc@webmail.leidinger.net> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-arch@freebsd.org Subject: Re: Compiling kernel and userland with Intel C Compiler X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Eirik A. Nygaard" List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2006 08:41:52 -0000 On Thu, Sep 28, 2006 at 07:23:49AM +0200, Alexander Leidinger wrote: > You are aware that any stuff needs to get committed to -current first? > And I don't see a _strong_ reason why this should be MFCed to 6-stable > when it is in 7-current. For this reasons it would be better to add > support to -current instead to 6.x. Yes, I am aware of this. FreeBSD 6.x is what I have access to these days. So that is what I have been using. There are still some troubles we need to work out. When that is done I will start working on it and -CURRENT. -- Eirik A. Nygaard From owner-freebsd-arch@FreeBSD.ORG Wed Oct 4 14:42:49 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9104916A52D for ; Wed, 4 Oct 2006 14:42:49 +0000 (UTC) (envelope-from rnsanchez@wait4.org) Received: from spunkymail-a9.dreamhost.com (sd-green-bigip-98.dreamhost.com [208.97.132.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4FB143E00 for ; Wed, 4 Oct 2006 14:42:21 +0000 (GMT) (envelope-from rnsanchez@wait4.org) Received: from sauron.lan.box (unknown [200.180.164.226]) by spunkymail-a9.dreamhost.com (Postfix) with ESMTP id 00BC8209C5 for ; Wed, 4 Oct 2006 07:42:17 -0700 (PDT) Date: Wed, 4 Oct 2006 10:50:33 -0300 From: Ricardo Nabinger Sanchez To: freebsd-arch@freebsd.org Message-Id: <20061004105033.b52bb860.rnsanchez@wait4.org> Organization: SYS_WAIT4 X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: PRNG on FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2006 14:42:49 -0000 Hello, Snooping around Wikipedia, I got curious about if it'd worth the effort going from Yarrow [1] to Fortuna [2] algorithm, as the authors (seems to) claim that the latter is better/more secure. As someone (me) who knows very little on how to effectively compromise a PRNG, what are the tradeoffs? Yarrow is simpler/faster than Fortuna? Regards. [1] http://en.wikipedia.org/wiki/Yarrow_algorithm [2] http://en.wikipedia.org/wiki/Fortuna_%28PRNG%29 -- Ricardo Nabinger Sanchez Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." From owner-freebsd-arch@FreeBSD.ORG Wed Oct 4 17:24:36 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF62316A40F for ; Wed, 4 Oct 2006 17:24:36 +0000 (UTC) (envelope-from freebsd-arch@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7680543D58 for ; Wed, 4 Oct 2006 17:24:35 +0000 (GMT) (envelope-from freebsd-arch@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GVAOd-0003A1-HH for freebsd-arch@freebsd.org; Wed, 04 Oct 2006 19:19:04 +0200 Received: from 83-131-171-55.adsl.net.t-com.hr ([83.131.171.55]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Oct 2006 19:19:03 +0200 Received: from ivoras by 83-131-171-55.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 04 Oct 2006 19:19:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-arch@freebsd.org From: Ivan Voras Date: Wed, 04 Oct 2006 19:15:00 +0200 Lines: 13 Message-ID: References: <20061004105033.b52bb860.rnsanchez@wait4.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 83-131-171-55.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) In-Reply-To: <20061004105033.b52bb860.rnsanchez@wait4.org> Sender: news Subject: Re: PRNG on FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Oct 2006 17:24:37 -0000 Ricardo Nabinger Sanchez wrote: > Hello, > > Snooping around Wikipedia, I got curious about if it'd worth the effort going > from Yarrow [1] to Fortuna [2] algorithm, as the authors (seems to) claim that > the latter is better/more secure. > > As someone (me) who knows very little on how to effectively compromise a > PRNG, what are the tradeoffs? Yarrow is simpler/faster than Fortuna? Maybe you'll want to ask this question on sci.crypt newsgroup (usenet). (the standard caveat: Wikipedia entries are not always correct) From owner-freebsd-arch@FreeBSD.ORG Thu Oct 5 12:14:04 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5DB116A403; Thu, 5 Oct 2006 12:14:04 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C094243D5E; Thu, 5 Oct 2006 12:13:51 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 2AB4C46D39; Thu, 5 Oct 2006 08:13:51 -0400 (EDT) Date: Thu, 5 Oct 2006 13:13:51 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ricardo Nabinger Sanchez In-Reply-To: <20061004105033.b52bb860.rnsanchez@wait4.org> Message-ID: <20061005131248.R46123@fledge.watson.org> References: <20061004105033.b52bb860.rnsanchez@wait4.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: markm@FreeBSD.org, freebsd-arch@freebsd.org Subject: Re: PRNG on FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 12:14:04 -0000 On Wed, 4 Oct 2006, Ricardo Nabinger Sanchez wrote: > Snooping around Wikipedia, I got curious about if it'd worth the effort > going from Yarrow [1] to Fortuna [2] algorithm, as the authors (seems to) > claim that the latter is better/more secure. > > As someone (me) who knows very little on how to effectively compromise a > PRNG, what are the tradeoffs? Yarrow is simpler/faster than Fortuna? Yarrow is an older PRNG algorithm, and Fortuna is (as I understand it) generally considered its successor. Mark Murray (CC'd), who implemented our current /dev/random and Yarrow code, has been working on a Fortuna implementation for FreeBSD. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-arch@FreeBSD.ORG Thu Oct 5 13:54:57 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.ORG Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3A7816A412; Thu, 5 Oct 2006 13:54:56 +0000 (UTC) (envelope-from mark@grondar.org) Received: from storm.uk.FreeBSD.org (storm.uk.FreeBSD.org [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7026B43D46; Thu, 5 Oct 2006 13:54:56 +0000 (GMT) (envelope-from mark@grondar.org) Received: from storm.uk.FreeBSD.org (uucp@localhost [127.0.0.1]) by storm.uk.FreeBSD.org (8.13.8/8.13.8) with ESMTP id k95Dsmpb034014; Thu, 5 Oct 2006 14:54:48 +0100 (BST) (envelope-from mark@grondar.org) Received: (from uucp@localhost) by storm.uk.FreeBSD.org (8.13.8/8.12.11/Submit) with UUCP id k95Dsmgk034013; Thu, 5 Oct 2006 14:54:48 +0100 (BST) (envelope-from mark@grondar.org) Received: from greatest.grondar.org (localhost [127.0.0.1]) by greatest.grondar.org (8.13.8/8.13.8) with ESMTP id k95Dsd3A047400; Thu, 5 Oct 2006 14:54:39 +0100 (BST) (envelope-from mark@greatest.grondar.org) Message-Id: <200610051354.k95Dsd3A047400@greatest.grondar.org> To: Robert Watson From: Mark Murray Date: Thu, 05 Oct 2006 14:54:39 +0100 Sender: mark@grondar.org Cc: Ricardo Nabinger Sanchez , freebsd-arch@FreeBSD.ORG Subject: Re: PRNG on FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 13:54:57 -0000 Robert Watson writes: > > On Wed, 4 Oct 2006, Ricardo Nabinger Sanchez wrote: > > > Snooping around Wikipedia, I got curious about if it'd worth the > > effort going from Yarrow [1] to Fortuna [2] algorithm, as the > > authors (seems to) claim that the latter is better/more secure. > > > > As someone (me) who knows very little on how to effectively > > compromise a PRNG, what are the tradeoffs? Yarrow is simpler/faster > > than Fortuna? > > Yarrow is an older PRNG algorithm, and Fortuna is (as I understand > it) generally considered its successor. Mark Murray (CC'd), who > implemented our current /dev/random and Yarrow code, has been working > on a Fortuna implementation for FreeBSD. Indeed. Fortuna is also looking like it is going to be a significant resource hog WRT memory, particularly on small/embedded devices. I'm stalled right now (exam mode for two weeks) but its top of my TODO list to get Fortuna off my chest once I'm done. I think I'm going to need a hand with the kernel bits; I keep running into problems I can't think of decent questions for. M -- Mark R V Murray - Cert APS(Open) Dip Phys(Open) BSc Open(Open) What is the most interesting question you have asked? What, if any, was the answer? From owner-freebsd-arch@FreeBSD.ORG Thu Oct 5 16:33:37 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.ORG Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC7C716A403; Thu, 5 Oct 2006 16:33:37 +0000 (UTC) (envelope-from rnsanchez@wait4.org) Received: from spunkymail-a16.dreamhost.com (sd-green-bigip-177.dreamhost.com [208.97.132.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E01343DDC; Thu, 5 Oct 2006 16:31:53 +0000 (GMT) (envelope-from rnsanchez@wait4.org) Received: from sauron.lan.box (unknown [200.180.163.9]) by spunkymail-a16.dreamhost.com (Postfix) with ESMTP id AD97F7B957; Thu, 5 Oct 2006 09:31:48 -0700 (PDT) Date: Thu, 5 Oct 2006 13:31:33 -0300 From: Ricardo Nabinger Sanchez To: Mark Murray Message-Id: <20061005133133.9e22d222.rnsanchez@wait4.org> In-Reply-To: <200610051354.k95Dsd3A047400@greatest.grondar.org> References: <200610051354.k95Dsd3A047400@greatest.grondar.org> Organization: SYS_WAIT4 X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Robert Watson , freebsd-arch@FreeBSD.ORG Subject: Re: PRNG on FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 16:33:38 -0000 On Thu, 05 Oct 2006 14:54:39 +0100 Mark Murray wrote: > Robert Watson writes: > > > > Yarrow is an older PRNG algorithm, and Fortuna is (as I understand > > it) generally considered its successor. Mark Murray (CC'd), who > > implemented our current /dev/random and Yarrow code, has been working > > on a Fortuna implementation for FreeBSD. Nice! > > Indeed. Fortuna is also looking like it is going to be a significant > resource hog WRT memory, particularly on small/embedded devices. Apart from the higher memory usage which can hurt modest devices, what are the CPU requirements? Proportional (higher?) from SHA-1 to SHA-256? When the patches are ready, I can test under RELENG_6 and also under a low-end CURRENT box, if its hard-drive doesn't explode soon. :) Thanks. -- Ricardo Nabinger Sanchez Powered by FreeBSD "Left to themselves, things tend to go from bad to worse." From owner-freebsd-arch@FreeBSD.ORG Fri Oct 6 09:18:31 2006 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A274F16A407; Fri, 6 Oct 2006 09:18:31 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE88743D46; Fri, 6 Oct 2006 09:18:30 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c58-107-94-118.belrs4.nsw.optusnet.com.au [58.107.94.118]) by mail01.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k969ISwx029956 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Oct 2006 19:18:28 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id k969IRO2001325; Fri, 6 Oct 2006 19:18:27 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id k969IRuk001324; Fri, 6 Oct 2006 19:18:27 +1000 (EST) (envelope-from peter) Date: Fri, 6 Oct 2006 19:18:27 +1000 From: Peter Jeremy To: Robert Watson Message-ID: <20061006091827.GA941@turion.vk2pj.dyndns.org> References: <20061004105033.b52bb860.rnsanchez@wait4.org> <20061005131248.R46123@fledge.watson.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <20061005131248.R46123@fledge.watson.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: Ricardo Nabinger Sanchez , freebsd-arch@freebsd.org Subject: Re: PRNG on FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Oct 2006 09:18:31 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 2006-Oct-05 13:13:51 +0100, Robert Watson wrote: >On Wed, 4 Oct 2006, Ricardo Nabinger Sanchez wrote: >>As someone (me) who knows very little on how to effectively compromise a= =20 >>PRNG, what are the tradeoffs? Yarrow is simpler/faster than Fortuna? > >Yarrow is an older PRNG algorithm, and Fortuna is (as I understand it)=20 >generally considered its successor. Of course, in the crypto world, "newer" and "better" are closer to antonyms than synonyms. Looking around on the net, I can't find anything that looks like an analysis of it. I respect the authors but it would be interesting to see the views of someone else. --=20 Peter Jeremy --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFJh9j/opHv/APuIcRAqVGAKC7LWS974VS9pEQaIl9lLLqUQiP9QCgtAtW GcScuG2C2WZRNZ+0Br++jSc= =k+gv -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc--