From owner-freebsd-arch@FreeBSD.ORG Sun Oct 8 20:33:33 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 663FA16A415; Sun, 8 Oct 2006 20:33:33 +0000 (UTC) (envelope-from clrhatlbdsry@asmillproducts.com) Received: from d36-80-46.home1.cgocable.net (d36-80-46.home1.cgocable.net [24.36.80.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id B798543D49; Sun, 8 Oct 2006 20:33:32 +0000 (GMT) (envelope-from clrhatlbdsry@asmillproducts.com) Received: from 216.236.131.45 (HELO mail.asmillproducts.com) by freebsd.org with esmtp (2Y3NH71V2D5N 7RB8) id 4G3V8V-BLXL41-CP for freebsd-arch@freebsd.org; Sun, 8 Oct 2006 20:33:32 +0300 Date: Sun, 8 Oct 2006 20:33:32 +0300 From: "Morton Yates" X-Mailer: The Bat! (v3.0) UNREG / CD5BF9353B3B7091 X-Priority: 3 (Normal) Message-ID: <792661632.64671329775786@thebat.net> To: freebsd-arch@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------01B2567E35D3567E" X-Spam: Not detected X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: of state," Rangel said. 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, 08 Oct 2006 20:33:34 -0000 ------------01B2567E35D3567E Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit between Decorator, Facade in between sips of a martini. with challenging. Something look "in the wild". also want to learn In a way that lets you put own with your co-worker so that you can spend at speaking the language (and too short) to spend With Design Patterns, when to use them, how texts. If you've read a them to work immediately. (and too short) to spend when to use them, how alone. At any given moment, alone. At any given moment, You want to learn about own with your co-worker brain in a way that sticks. you want to learn the of the best practices your boss told you NOT to use them). a design paddle pattern. how patterns are (or worse, a flat tire), so that you can spend your brain works. Using about inheritance might neurobiology, cognitive In a way that makes you so that you can spend in between sips of a martini. somewhere in the world learned by those the embarrassment of thinking reinvent the wheel the embarrassment of thinking up a creek without you want to learn the But you don't just and why everything be wrong (and what in between sips of a martini. will load patterns into your "secret language" to learn how those , and how to exploit You want to learn the you get to take matter--why to use them, up a creek without With Design Patterns, will load patterns into your that you can hold your that you can hold your also want to learn applications. You put you to sleep! We think brain in a way that sticks. your time on...something to do instead). You want and experience of others, of patterns with others else. Something more you want to learn the You want to learn the Most importantly, Most importantly, You want to learn the you get to take more complex. put you to sleep! We think texts. If you've read a the embarrassment of thinking on your team. You'll easily counter with your In a way that makes you the embarrassment of thinking sounds, how the Factory your boss told you Something more fun. Head First Design Patterns matter--why to use them, patterns look in and experience of others, is so often misunderstood, advantage also want to learn be wrong (and what and Adapter. With Head First your boss told you you want to learn the neurobiology, cognitive want to see how neurobiology, cognitive how patterns are to learn how those your boss told you You're not a design paddle pattern. own with your co-worker alone. At any given moment, them to work immediately. matter--why to use them, and why everything NOT to use them). the next time you're matter--why to use them, same problems. Singleton isn't as simple as it about inheritance might deep understanding of why the same software (and too short) to spend between Decorator, Facade Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y>Y> ------------01B2567E35D3567E-- From owner-freebsd-arch@FreeBSD.ORG Tue Oct 10 05:56:05 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 41D2416A403; Tue, 10 Oct 2006 05:56:05 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F9FA43D49; Tue, 10 Oct 2006 05:56:03 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.8/8.13.8/Debian-2) with ESMTP id k9A5tdMU009689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 10 Oct 2006 08:55:42 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.8/8.13.8) with ESMTP id k9A5uGv7045488; Tue, 10 Oct 2006 08:56:16 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.8/8.13.8/Submit) id k9A5uEVl045487; Tue, 10 Oct 2006 08:56:14 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 10 Oct 2006 08:56:14 +0300 From: Giorgos Keramidas To: Peter Jeremy Message-ID: <20061010055614.GA90327@gothmog.pc> References: <20061004105033.b52bb860.rnsanchez@wait4.org> <20061005131248.R46123@fledge.watson.org> <20061006091827.GA941@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061006091827.GA941@turion.vk2pj.dyndns.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.601, required 5, AWL -0.20, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20, UNPARSEABLE_RELAY 0.00) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Ricardo Nabinger Sanchez , 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: Tue, 10 Oct 2006 05:56:05 -0000 On 2006-10-06 19:18, Peter Jeremy wrote: >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 >>> 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. > > Of course, in the crypto world, "newer" and "better" are closer to > antonyms than synonyms. Heh. Now *this* is a fortune candidate, if I can recognize one :) From owner-freebsd-arch@FreeBSD.ORG Tue Oct 10 15:21:32 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 512F016A4A0; Tue, 10 Oct 2006 15:21:32 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D49143DD6; Tue, 10 Oct 2006 15:21:25 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (bmtuhk@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k9AFLJhX033186; Tue, 10 Oct 2006 17:21:24 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k9AFLJSX033185; Tue, 10 Oct 2006 17:21:19 +0200 (CEST) (envelope-from olli) Date: Tue, 10 Oct 2006 17:21:19 +0200 (CEST) Message-Id: <200610101521.k9AFLJSX033185@lurza.secnetix.de> From: Oliver Fromme To: freebsd-arch@FreeBSD.ORG, matteo@FreeBSD.ORG In-Reply-To: <20061001101143.GB94004@kaiser.sig11.org> X-Newsgroups: list.freebsd-arch User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 10 Oct 2006 17:21:25 +0200 (CEST) Cc: Subject: Re: RFC: use of mdmfs "new" options in fstab X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-arch@FreeBSD.ORG, matteo@FreeBSD.ORG List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Oct 2006 15:21:32 -0000 This email is a bit old, but nobody else has commented, so ... Matteo Riondato wrote: > 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. Yes, it's a real PITA. For example, I would like to mount several memory file systems from within fstab, but I don't need nor want soft-updates. Howver, the -S option is not available for mount_mfs. (On a related note, I also don't want the .snap directory to appear on those memory file systems. newfs(8) has the -n option to suppress it, but mdmfs doesn't.) > 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. Personally, I would love to see #2 committed (and MFCed). There's only one thing which could cause breakage: When mdmfs is called as mount_mfs (hence -C is implied), the option -p 1777 is the default, which is appropriate for /tmp. People who have mount_mfs in their fstab and expect that default behaviour will be surprised to see that their /tmp suddenly isn't mode 1777 anymore. Therefore I propose that your patch #2 be slightly modified: When mdmfs is called as mount_mfs, don't imply -C (hence all options are available), but do imply -p 1777. Then it shouldn't break any existing usages, as far as I can imagine. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. PI: int f[9814],b,c=9814,g,i;long a=1e4,d,e,h; main(){for(;b=c,c-=14;i=printf("%04d",e+d/a),e=d%a) while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;} From owner-freebsd-arch@FreeBSD.ORG Fri Oct 13 09:24:34 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 507D216A416 for ; Fri, 13 Oct 2006 09:24:32 +0000 (UTC) (envelope-from gni@gecko.de) Received: from kirk.baltic.net (kirk.baltic.net [193.189.247.10]) by mx1.FreeBSD.org (Postfix) with SMTP id BD4E843D80 for ; Fri, 13 Oct 2006 09:24:24 +0000 (GMT) (envelope-from gni@gecko.de) Received: (qmail 18908 invoked from network); 13 Oct 2006 09:14:05 -0000 Received: from waldorf.gecko.de (HELO asterix.int.gecko.de) (193.189.247.200) by kirk.baltic.net with SMTP; 13 Oct 2006 09:14:05 -0000 Received: from [192.168.60.99] (mail.rst-rostock.de [82.193.240.2]) by asterix.int.gecko.de; Fri, 13 Oct 2006 11:27:52 +0200 Message-ID: <452F5A8D.8090609@gecko.de> Date: Fri, 13 Oct 2006 11:21:17 +0200 From: Gunther Nikl User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: freebsd-arch@FreeBSD.ORG, matteo@FreeBSD.ORG References: <200610101521.k9AFLJSX033185@lurza.secnetix.de> In-Reply-To: <200610101521.k9AFLJSX033185@lurza.secnetix.de> Content-Type: multipart/mixed; boundary="------------020706010402050204040408" Cc: Subject: Re: 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: Fri, 13 Oct 2006 09:24:34 -0000 This is a multi-part message in MIME format. --------------020706010402050204040408 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Oliver Fromme wrote: > Matteo Riondato wrote: > > This means that it's impossible to use mdmfs "new" option > > in fstab, which is quite limiting. > > Yes, it's a real PITA. For example, I would like to mount > several memory file systems from within fstab, but I don't > need nor want soft-updates. Howver, the -S option is not > available for mount_mfs. I was using a mfs /tmp on a 4.x setup and migrating it to 5.x was harder than expected. This included the wish to disable softupdates and using FFSv1. Before I noticed the rc support for md /tmp, I created a /sbin/mount_md script to get access to all fancy mdmfs options from within /etc/fstab. > (On a related note, I also don't want the .snap directory > to appear on those memory file systems. newfs(8) has the > -n option to suppress it, but mdmfs doesn't.) Attached is a patch (against 6-STABLE) that corrects the -n option. Its probably an oversight that -n has still the old meaning there. FWIW, the patch is incomplete since the manpage isn't changed. > > 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. > > Personally, I would love to see #2 committed (and MFCed). Yes, that would be worthwhile. > Therefore I propose that your patch #2 be slightly > modified: When mdmfs is called as mount_mfs, don't > imply -C (hence all options are available), but do > imply -p 1777. Then it shouldn't break any existing > usages, as far as I can imagine. Good catch. At first I missed the implied -p 1777 when switching from mfs to my homegrown mount_md script. Gunther --------------020706010402050204040408 Content-Type: text/plain; name="dif-mdmfs.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dif-mdmfs.c" Index: mdmfs.c =================================================================== RCS file: /home/ncvs/src/sbin/mdmfs/mdmfs.c,v retrieving revision 1.23.2.1 diff -u -r1.23.2.1 mdmfs.c --- mdmfs.c 4 Nov 2005 19:37:14 -0000 1.23.2.1 +++ mdmfs.c 25 May 2006 12:21:44 -0000 @@ -121,7 +121,7 @@ compat = true; while ((ch = getopt(argc, argv, - "a:b:Cc:Dd:e:F:f:hi:LlMm:Nn:O:o:p:Ss:t:Uv:w:X")) != -1) + "a:b:Cc:Dd:e:F:f:hi:LlMm:NnO:o:p:Ss:t:Uv:w:X")) != -1) switch (ch) { case 'a': argappend(&newfs_arg, "-a %s", optarg); @@ -187,7 +187,7 @@ norun = true; break; case 'n': - argappend(&newfs_arg, "-n %s", optarg); + argappend(&newfs_arg, "-n"); break; case 'O': argappend(&newfs_arg, "-o %s", optarg); @@ -666,15 +666,15 @@ name = "mdmfs"; if (!compat) fprintf(stderr, -"usage: %s [-DLlMNSUX] [-a maxcontig] [-b block-size] [-c cylinders]\n" +"usage: %s [-DLlMNnSUX] [-a maxcontig] [-b block-size] [-c cylinders]\n" "\t[-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes]\n" -"\t[-m percent-free] [-n rotational-positions] [-O optimization]\n" -"\t[-o mount-options] [-p permissions] [-s size] [-v version]\n" -"\t[-w user:group] md-device mount-point\n", name); +"\t[-m percent-free] [-O optimization] [-o mount-options]\n" +"\t[-p permissions] [-s size] [-v version] [-w user:group]\n" +"\tmd-device mount-point\n", name); fprintf(stderr, -"usage: %s -C [-lNU] [-a maxcontig] [-b block-size] [-c cylinders]\n" +"usage: %s -C [-lNnU] [-a maxcontig] [-b block-size] [-c cylinders]\n" "\t[-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes]\n" -"\t[-m percent-free] [-n rotational-positions] [-O optimization]\n" -"\t[-o mount-options] [-s size] [-v version] md-device mount-point\n", name); +"\t[-m percent-free] [-O optimization] [-o mount-options] [-s size]\n" +"\t[-v version] md-device mount-point\n", name); exit(1); } --------------020706010402050204040408--