From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 24 00:30:59 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31E9A1065673 for ; Sun, 24 Apr 2011 00:30:59 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mta31.charter.net (mta31.charter.net [216.33.127.82]) by mx1.freebsd.org (Postfix) with ESMTP id D5ADB8FC17 for ; Sun, 24 Apr 2011 00:30:58 +0000 (UTC) Received: from imp10 ([10.20.200.15]) by mta31.charter.net (InterMail vM.7.09.02.04 201-2219-117-106-20090629) with ESMTP id <20110424003057.HHJA7341.mta31.charter.net@imp10>; Sat, 23 Apr 2011 20:30:57 -0400 Received: from [192.168.1.110] ([75.138.215.209]) by imp10 with smtp.charter.net id bCWx1g00B4XeuP705CWxwd; Sat, 23 Apr 2011 20:30:57 -0400 X-Authority-Analysis: v=1.1 cv=67PPgUc0CtgM8E27DXTM5SVmNQEiZYYnqhTvr1M71DI= c=1 sm=1 a=Vf9Zk9rDW_cA:10 a=yUnIBFQkZM0A:10 a=XrFk8IW1Pep/MeV13so3Wg==:17 a=7Qk2ozbKAAAA:8 a=hOpmn2quAAAA:8 a=GKysJfYJAAAA:8 a=6I5d2MoRAAAA:8 a=lYsx03trEwWQKqjgyMUA:9 a=yRaEaUQNxcob4a_pRsQA:7 a=QEXdDO2ut3YA:10 a=HNhVPpsFFhwA:10 a=prh60fsrXhQA:10 a=kaza6-i1AqsA:10 a=cvZW9r6VXHAA:10 a=hUswqBWy9Q8A:10 a=SV7veod9ZcQA:10 a=EKh8xn4X__2sKFqm3dsA:9 a=Xho2MPDvzEkVtha_ygMA:7 a=XrFk8IW1Pep/MeV13so3Wg==:117 Message-ID: <4DB36F41.7070307@charter.net> Date: Sat, 23 Apr 2011 20:30:57 -0400 From: Andrew Lankford User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.16) Gecko/20101210 Thunderbird/3.0.11 MIME-Version: 1.0 To: imp@bsdimp.com, perryh@pluto.rain.com X-Mailman-Approved-At: Sun, 24 Apr 2011 04:34:54 +0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org Subject: Fwd: Re: scd and mcd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 00:30:59 -0000 My last desktop machine had an ASUS Pentium-3 (no ISA slots), USB1 only. It has outlived the original hard drive, CDROM, and power supply, but I think it makes more sense these days to throw these systems out rather than "future-proof" them, especially if a fanless SoC could be less power-hungry and noisy. It seems to me that people who want to get more life out 10yr old hardware need to be part of some sort of trimmed down "LegacyBSD" project that caters to their special needs. You all know more than I do about the orgs that are following the stable-6 or stable-7 branches, but are they using ancient CDROMS with a limited life span? -------- Original Message -------- From: - Sat Apr 23 19:53:48 2011 X-Account-Key: account2 X-UIDL: X-Mozilla-Status: 0011 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: Received: from imp04 ([10.20.200.4]) by mta52.charter.net (InterMail vM.7.09.02.04 201-2219-117-106-20090629) with ESMTP id <20110423234226.QAAM13475.mta52.charter.net@imp04> for ; Sat, 23 Apr 2011 19:42:26 -0400 Received: from harmony.bsdimp.com ([199.45.160.85]) by imp04 with charter.net id bBiR1g01x1qqkgf04BiSRj; Sat, 23 Apr 2011 19:42:26 -0400 X-Chzlrs: ?? X-Authority-Analysis: v=1.1 cv=ACdvlZsxPtp6/8rt9ATxQxe5eelQ5vQqaf1LwcbVAy0= c=1 sm=1 a=Ucbx8mQ_rlYA:10 a=MV1VDysopeJvYeH43xkbGw==:17 a=GKysJfYJAAAA:8 a=7Qk2ozbKAAAA:8 a=VHkpZ49OhpeKkUvcBWkA:9 a=ABrYPtnIPbQqMp5bbigA:7 a=CjuIK1q_8ugA:10 a=cvZW9r6VXHAA:10 a=aNaW_GFDrTlh0hGR9xgA:9 a=P0Ne2a3NTbHX3BCDdCkA:7 a=MV1VDysopeJvYeH43xkbGw==:117 Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p3NNbvwt006040 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Sat, 23 Apr 2011 17:37:59 -0600 (MDT) (envelope-from imp@bsdimp.com) Subject: Re: scd and mcd Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-4-1024646444 From: Warner Losh In-Reply-To: <4db35e8a.R5LDMfg8cygIRbfF%perryh@pluto.rain.com> Date: Sat, 23 Apr 2011 17:37:57 -0600 Cc: hackers@FreeBSD.org, lankfordandrew@charter.net Message-Id: References: <4DB3142A.4000807@charter.net> <1E3F5B85-5A1A-4118-A9D8-932F46619C79@bsdimp.com> <4db35e8a.R5LDMfg8cygIRbfF%perryh@pluto.rain.com> To: perryh@pluto.rain.com X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Sat, 23 Apr 2011 17:37:59 -0600 (MDT) On Apr 23, 2011, at 5:19 PM, perryh@pluto.rain.com wrote: > Warner Losh wrote: > >> mcd and scd are ISA-only devices ... They were important for the >> 386 (now not supported) and 486 machines. Since the 486 machines >> in question maxed out at 32MB, and 8.x has trouble running in 32MB >> on x86, I'm guessing there aren't too many 486 SX/DX machines >> running 8.x. > > 486 were the last for which ISA was the primary bus, but ISA was > still present (bridged from PCI) on most Pentium systems and common > at least as recently as Pentium-II. (I don't have a disassembled > P-III handy to check whether it has an ISA slot.) Most Pentium II and newer systems had IDE connectors on the motherboard. Many of the Pentium I ones did too. Only if you didn't have IDE connectors on mobo would you be likely to consider one of these CD's. Also, I think they topped out at 4x or 8x speed since they had a custom interface. Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 24 13:20:37 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 5A5E31065670; Sun, 24 Apr 2011 13:20:37 +0000 (UTC) Date: Sun, 24 Apr 2011 13:20:37 +0000 From: Alexander Best To: freebsd-hackers@freebsd.org Message-ID: <20110424132037.GA14286@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline Subject: [RFC] a few kldstat(8) improvements X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 13:20:37 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hi there, i hacked up kldstat(8) a bit. just wanted to hear what people think of it. the changes are as follows: - make -i , -m and -n flags mutually exclusive - when iterating through kernel files and kernel modules, don't bail out when an error occurs, but hand down the error via "int error" - improve handling of -q and -v flags and call usage() when used improperly - use errx(3) and warnx(3) rather than err(3) and warn(3) in order to keep stderr at a sensible user information level - adjust white space handling in order to improve formating - a few kldstat(8) man page improvements cheers. alex -- a13x --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="kldstat.diff" diff --git a/sbin/kldstat/kldstat.8 b/sbin/kldstat/kldstat.8 index 6f040e2..10b8fd5 100644 --- a/sbin/kldstat/kldstat.8 +++ b/sbin/kldstat/kldstat.8 @@ -25,7 +25,7 @@ .\" .\" $FreeBSD$ .\" -.Dd September 23, 2005 +.Dd April 24, 2011 .Dt KLDSTAT 8 .Os .Sh NAME @@ -35,10 +35,12 @@ .Nm .Op Fl v .Op Fl i Ar id -.Op Fl n Ar filename .Nm .Op Fl q .Op Fl m Ar modname +.Nm +.Op Fl v +.Op Fl n Ar filename .Sh DESCRIPTION The .Nm @@ -47,16 +49,17 @@ kernel. .Pp The following options are available: .Bl -tag -width indentXX -.It Fl v -Be more verbose. + .It Fl i Ar id Display the status of only the file with this ID. +.It Fl m Ar modname +Display the status of only the module with this name. .It Fl n Ar filename -Display the status of only the file with this filename. +Display the status of only the file with this name. .It Fl q -Only check if module is loaded or compiled into the kernel. -.It Fl m Ar modname -Display the status of only the module with this modname. +Only check if the module is loaded or compiled into the kernel. +.It Fl v +Be more verbose. .El .Sh EXIT STATUS .Ex -std diff --git a/sbin/kldstat/kldstat.c b/sbin/kldstat/kldstat.c index 575fca8..0b73f74 100644 --- a/sbin/kldstat/kldstat.c +++ b/sbin/kldstat/kldstat.c @@ -39,38 +39,42 @@ __FBSDID("$FreeBSD$"); #define POINTER_WIDTH ((int)(sizeof(void *) * 2 + 2)) static void -printmod(int modid) +printmod(int modid, int error) { struct module_stat stat; stat.version = sizeof(struct module_stat); - if (modstat(modid, &stat) < 0) - warn("can't stat module id %d", modid); + if (modstat(modid, &stat) < 0) { + warnx("can't stat module id %d", modid); + error = 1; + } else - printf("\t\t%2d %s\n", stat.id, stat.name); + printf(" %-4d %s\n", stat.id, stat.name); } static void -printfile(int fileid, int verbose) +printfile(int fileid, int verbose, int error) { struct kld_file_stat stat; int modid; stat.version = sizeof(struct kld_file_stat); - if (kldstat(fileid, &stat) < 0) - err(1, "can't stat file id %d", fileid); + if (kldstat(fileid, &stat) < 0) { + warnx("can't stat file id %d", fileid); + error = 1; + } else - printf("%2d %4d %p %-8zx %s", - stat.id, stat.refs, stat.address, stat.size, + printf("%-3d %4d %p %-8zx %s", + stat.id, stat.refs, stat.address, stat.size, stat.name); if (verbose) { printf(" (%s)\n", stat.pathname); - printf("\tContains modules:\n"); - printf("\t\tId Name\n"); + printf(" Contains modules:\n"); + printf(" Id Name\n"); for (modid = kldfirstmod(fileid); modid > 0; modid = modfnext(modid)) - printmod(modid); + printmod(modid, error); } else printf("\n"); } @@ -78,21 +82,20 @@ printfile(int fileid, int verbose) static void usage(void) { - fprintf(stderr, "usage: kldstat [-v] [-i id] [-n filename]\n"); + fprintf(stderr, "usage: kldstat [-v] [-i id]\n"); fprintf(stderr, " kldstat [-q] [-m modname]\n"); + fprintf(stderr, " kldstat [-v] [-n filename]\n"); exit(1); } int main(int argc, char** argv) { - int c; - int verbose = 0; - int fileid = 0; - int quiet = 0; - char* filename = NULL; - char* modname = NULL; - char* p; + int c, error, fileid, quiet, verbose; + char *filename, *modname, *p; + + error = fileid = quiet = verbose = 0; + filename = modname = NULL; while ((c = getopt(argc, argv, "i:m:n:qv")) != -1) switch (c) { @@ -122,13 +125,21 @@ main(int argc, char** argv) if (argc != 0) usage(); + if ((*p == '\0' && modname != NULL) || (*p == '\0' && filename != NULL) || + (modname != NULL && filename != NULL)) + errx(1, "-i, -m and -n flags are mutually exclusive"); + + if ((*p == '\0' && quiet) || (modname != NULL && verbose) || + (filename != NULL && quiet)) + usage(); + if (modname != NULL) { int modid; struct module_stat stat; if ((modid = modfind(modname)) < 0) { if (!quiet) - warn("can't find module %s", modname); + warnx("can't find module %s", modname); return 1; } else if (quiet) { return 0; @@ -136,10 +147,10 @@ main(int argc, char** argv) stat.version = sizeof(struct module_stat); if (modstat(modid, &stat) < 0) - warn("can't stat module id %d", modid); + errx(1, "can't stat module id %d", modid); else { printf("Id Refs Name\n"); - printf("%3d %4d %s\n", stat.id, stat.refs, stat.name); + printf("%-3d %4d %s\n", stat.id, stat.refs, stat.name); } return 0; @@ -147,15 +158,15 @@ main(int argc, char** argv) if (filename != NULL) { if ((fileid = kldfind(filename)) < 0) - err(1, "can't find file %s", filename); + errx(1, "can't find file %s", filename); } - printf("Id Refs Address%*c Size Name\n", POINTER_WIDTH - 7, ' '); + printf("Id Refs Address%*c Size Name\n", POINTER_WIDTH - 7, ' '); if (fileid != 0) - printfile(fileid, verbose); + printfile(fileid, verbose, error); else for (fileid = kldnext(0); fileid > 0; fileid = kldnext(fileid)) - printfile(fileid, verbose); + printfile(fileid, verbose, error); - return 0; + return error; } --jI8keyz6grp/JLjh-- From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 24 13:31:53 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id BBD31106566B; Sun, 24 Apr 2011 13:31:53 +0000 (UTC) Date: Sun, 24 Apr 2011 13:31:53 +0000 From: Alexander Best To: freebsd-hackers@freebsd.org Message-ID: <20110424133153.GA16850@freebsd.org> References: <20110424132037.GA14286@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110424132037.GA14286@freebsd.org> Subject: Re: [RFC] a few kldstat(8) improvements X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 13:31:53 -0000 On Sun Apr 24 11, Alexander Best wrote: > hi there, > > i hacked up kldstat(8) a bit. just wanted to hear what people think of it. the > changes are as follows: > > - make -i , -m and -n flags mutually exclusive > - when iterating through kernel files and kernel modules, don't bail out when > an error occurs, but hand down the error via "int error" > - improve handling of -q and -v flags and call usage() when used improperly > - use errx(3) and warnx(3) rather than err(3) and warn(3) in order to keep > stderr at a sensible user information level > - adjust white space handling in order to improve formating > - a few kldstat(8) man page improvements > > cheers. > alex > > -- > a13x > diff --git a/sbin/kldstat/kldstat.8 b/sbin/kldstat/kldstat.8 > index 6f040e2..10b8fd5 100644 > --- a/sbin/kldstat/kldstat.8 > +++ b/sbin/kldstat/kldstat.8 > @@ -25,7 +25,7 @@ > .\" > .\" $FreeBSD$ > .\" > -.Dd September 23, 2005 > +.Dd April 24, 2011 > .Dt KLDSTAT 8 > .Os > .Sh NAME > @@ -35,10 +35,12 @@ > .Nm > .Op Fl v > .Op Fl i Ar id > -.Op Fl n Ar filename > .Nm > .Op Fl q > .Op Fl m Ar modname > +.Nm > +.Op Fl v > +.Op Fl n Ar filename > .Sh DESCRIPTION > The > .Nm > @@ -47,16 +49,17 @@ kernel. > .Pp > The following options are available: > .Bl -tag -width indentXX > -.It Fl v > -Be more verbose. > + ^^ my bad > .It Fl i Ar id > Display the status of only the file with this ID. > +.It Fl m Ar modname > +Display the status of only the module with this name. > .It Fl n Ar filename > -Display the status of only the file with this filename. > +Display the status of only the file with this name. > .It Fl q > -Only check if module is loaded or compiled into the kernel. > -.It Fl m Ar modname > -Display the status of only the module with this modname. > +Only check if the module is loaded or compiled into the kernel. > +.It Fl v > +Be more verbose. > .El > .Sh EXIT STATUS > .Ex -std > diff --git a/sbin/kldstat/kldstat.c b/sbin/kldstat/kldstat.c > index 575fca8..0b73f74 100644 > --- a/sbin/kldstat/kldstat.c > +++ b/sbin/kldstat/kldstat.c > @@ -39,38 +39,42 @@ __FBSDID("$FreeBSD$"); > #define POINTER_WIDTH ((int)(sizeof(void *) * 2 + 2)) > > static void > -printmod(int modid) > +printmod(int modid, int error) > { > struct module_stat stat; > > stat.version = sizeof(struct module_stat); > - if (modstat(modid, &stat) < 0) > - warn("can't stat module id %d", modid); > + if (modstat(modid, &stat) < 0) { > + warnx("can't stat module id %d", modid); > + error = 1; > + } > else > - printf("\t\t%2d %s\n", stat.id, stat.name); > + printf(" %-4d %s\n", stat.id, stat.name); > } > > static void > -printfile(int fileid, int verbose) > +printfile(int fileid, int verbose, int error) > { > struct kld_file_stat stat; > int modid; > > stat.version = sizeof(struct kld_file_stat); > - if (kldstat(fileid, &stat) < 0) > - err(1, "can't stat file id %d", fileid); > + if (kldstat(fileid, &stat) < 0) { > + warnx("can't stat file id %d", fileid); > + error = 1; > + } > else > - printf("%2d %4d %p %-8zx %s", > - stat.id, stat.refs, stat.address, stat.size, > + printf("%-3d %4d %p %-8zx %s", > + stat.id, stat.refs, stat.address, stat.size, > stat.name); > > if (verbose) { > printf(" (%s)\n", stat.pathname); > - printf("\tContains modules:\n"); > - printf("\t\tId Name\n"); > + printf(" Contains modules:\n"); > + printf(" Id Name\n"); > for (modid = kldfirstmod(fileid); modid > 0; > modid = modfnext(modid)) > - printmod(modid); > + printmod(modid, error); > } else > printf("\n"); > } > @@ -78,21 +82,20 @@ printfile(int fileid, int verbose) > static void > usage(void) > { > - fprintf(stderr, "usage: kldstat [-v] [-i id] [-n filename]\n"); > + fprintf(stderr, "usage: kldstat [-v] [-i id]\n"); > fprintf(stderr, " kldstat [-q] [-m modname]\n"); > + fprintf(stderr, " kldstat [-v] [-n filename]\n"); > exit(1); > } > > int > main(int argc, char** argv) > { > - int c; > - int verbose = 0; > - int fileid = 0; > - int quiet = 0; > - char* filename = NULL; > - char* modname = NULL; > - char* p; > + int c, error, fileid, quiet, verbose; > + char *filename, *modname, *p; > + > + error = fileid = quiet = verbose = 0; > + filename = modname = NULL; > > while ((c = getopt(argc, argv, "i:m:n:qv")) != -1) > switch (c) { > @@ -122,13 +125,21 @@ main(int argc, char** argv) > if (argc != 0) > usage(); > > + if ((*p == '\0' && modname != NULL) || (*p == '\0' && filename != NULL) || > + (modname != NULL && filename != NULL)) > + errx(1, "-i, -m and -n flags are mutually exclusive"); > + > + if ((*p == '\0' && quiet) || (modname != NULL && verbose) || > + (filename != NULL && quiet)) > + usage(); > + > if (modname != NULL) { > int modid; > struct module_stat stat; > > if ((modid = modfind(modname)) < 0) { > if (!quiet) > - warn("can't find module %s", modname); > + warnx("can't find module %s", modname); > return 1; > } else if (quiet) { > return 0; > @@ -136,10 +147,10 @@ main(int argc, char** argv) > > stat.version = sizeof(struct module_stat); > if (modstat(modid, &stat) < 0) > - warn("can't stat module id %d", modid); > + errx(1, "can't stat module id %d", modid); > else { > printf("Id Refs Name\n"); > - printf("%3d %4d %s\n", stat.id, stat.refs, stat.name); > + printf("%-3d %4d %s\n", stat.id, stat.refs, stat.name); > } > > return 0; > @@ -147,15 +158,15 @@ main(int argc, char** argv) > > if (filename != NULL) { > if ((fileid = kldfind(filename)) < 0) > - err(1, "can't find file %s", filename); > + errx(1, "can't find file %s", filename); > } > > - printf("Id Refs Address%*c Size Name\n", POINTER_WIDTH - 7, ' '); > + printf("Id Refs Address%*c Size Name\n", POINTER_WIDTH - 7, ' '); > if (fileid != 0) > - printfile(fileid, verbose); > + printfile(fileid, verbose, error); > else > for (fileid = kldnext(0); fileid > 0; fileid = kldnext(fileid)) > - printfile(fileid, verbose); > + printfile(fileid, verbose, error); > > - return 0; > + return error; > } -- a13x From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 24 17:44:42 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 3F9DB1065670; Sun, 24 Apr 2011 17:44:42 +0000 (UTC) Date: Sun, 24 Apr 2011 17:44:42 +0000 From: Alexander Best To: freebsd-hackers@freebsd.org Message-ID: <20110424174442.GA45573@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: exit(3) and sysexits(3) style policy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 17:44:42 -0000 hi there, i was wondering about this for some time now: various documents decribe different policies regarding exit(3)'s return values. style(9) e.g. recommends using exit(0), while other man pages such as err(3) recommend using the sysexits(3) return values. i think i read some time ago on the mailinglists that it was decided that exit(3) should return integers rathers than sysexits(3) values. is this correct? shouldn't then all references such as in err(3) be removed and a note added to sysexits(3) that returnings its values via exit(3) does not according to current FreeBSD programming style? cheers. alex -- a13x From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 24 17:52:01 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 333021065670; Sun, 24 Apr 2011 17:52:01 +0000 (UTC) (envelope-from dnaeon@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id AD0448FC17; Sun, 24 Apr 2011 17:52:00 +0000 (UTC) Received: by vxc34 with SMTP id 34so1896814vxc.13 for ; Sun, 24 Apr 2011 10:51:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=kVlSMsOvsphl4b/zsR0mGX7ryWe3AGRTD8GAeh5jeTA=; b=oJjgUEwtlG+hcx/mddZALYZUCHBRpigpDyO3S/RKDJvPb18FkVHth3Dz6jrQu4DLd9 eDp5CGyYGF4CEY92MUtCx01JIovlOoxJ/YXOjvx1qgVmGwSIv+0S1E61l1M7wIZWo1Ys y7UUcVLGxhD+RUO01+qoo5JKYqvxyugeDbw/g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hFRqtengf0nbdmnEphpi5f0ADMG4QYVPAsWYIzQFuhnLdBlOFsLqKARzBG4eWSdfL1 p3f3m2Qd0hWpfnc6bfqxue6G6BXXFpAtokeWW4hRyEV1SNW3isZon4InAmVJlK8J8y+A BTI/Tiumo7z5FR/ZhW+NXD3uCI7eiytOs7SaY= MIME-Version: 1.0 Received: by 10.52.98.39 with SMTP id ef7mr60342vdb.145.1303665779282; Sun, 24 Apr 2011 10:22:59 -0700 (PDT) Received: by 10.52.160.226 with HTTP; Sun, 24 Apr 2011 10:22:59 -0700 (PDT) Date: Sun, 24 Apr 2011 20:22:59 +0300 Message-ID: From: Marin Atanasov Nikolov To: freebsd-ports@freebsd.org, ml-freebsd-stable , freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Configuration Management with Cfengine 3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 17:52:01 -0000 Hello, Recently I've been working on automating my FreeBSD systems, as much as possible and the viable solution was to try out Cfengine 3. Currently I'm running most of my hosts and jails under Cfengine 3 control, and wanted to share this you, because I think some might find it useful. Therefore I've created a little documentation that explains how to setup Cfengine 3 on your systems and use it for managing your hosts and jails - starting from simple configuration deployments and daemon processes control, and package management with Cfengine 3. Anyway the document can be found here: - http://unix-heaven.org/node/50 Hope you find it useful. Regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org http://www.unix-heaven.org/ From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 25 01:53:14 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 882ED1065670 for ; Mon, 25 Apr 2011 01:53:14 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 4C7208FC14 for ; Mon, 25 Apr 2011 01:53:13 +0000 (UTC) Received: from sbhfislrext01.fnfis.com ([192.168.249.167]) by SCSFISLTC01 (8.14.3/8.14.3) with ESMTP id p3P1rDXU023971 for ; Sun, 24 Apr 2011 20:53:13 -0500 Received: from SBHFISLTCGW04.FNFIS.COM (Not Verified[10.132.248.123]) by sbhfislrext01.fnfis.com with MailMarshal (v6, 5, 4, 7535) id ; Sun, 24 Apr 2011 20:53:12 -0500 Received: from SBHFISLTCGW04.FNFIS.COM ([10.132.248.123]) by SBHFISLTCGW04.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Sun, 24 Apr 2011 20:53:13 -0500 Received: from [10.0.0.102] ([10.132.254.136]) by SBHFISLTCGW04.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sun, 24 Apr 2011 20:53:12 -0500 From: Devin Teske Date: Sun, 24 Apr 2011 18:53:11 -0700 Message-Id: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> To: FreeBSD Hackers Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-OriginalArrivalTime: 25 Apr 2011 01:53:12.0671 (UTC) FILETIME=[890B96F0:01CC02EB] Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Devin Teske Subject: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 01:53:14 -0000 Hello fellow hackers, I'd love to finally release (under the BSD license) my code for the revampe= d FreeBSD boot loader menu. Here's a detailed discussion of the release complete with pictures: http://devinteske.com/new-freebsd-boot-loader-menu Here's the download: http://druidbsd.sourceforge.net/download/loader_menu-1.0.tgz The download is a FreeBSD package. You can execute: fetch [aboveURL] pkg_add loader_menu-1.0.tgz reboot And upon your next boot will use the new loader menu. A feature-complete so= phisticated boot menu designed from the ground up. --=20 Cheers, Devin Teske P.S. This code has been developed since 2006 and has been booted on hundred= s of machines thousands of times by a group of more than two dozen field en= gineers trained to install, trouble-shoot, and maintain FreeBSD. It is only= after this success that we are so happy to release this to the general pub= lic under the BSD license. Should it make its way into the base distributio= n, we would be honored, but that is not a necessity. -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> FUN STUFF <- -----BEGIN GEEK CODE BLOCK----- Version 3.12 GAT/CS/B/CC/E/IT/MC/M/MU/P/S/TW d+(++) s: a- C+++@$ UB++++$ P++++@$ L++++$ = E- W+++ N? o? K? w@ O M++$ V- PS+>++ PE@ Y+ PGP-> t(+) 5? X(+) R(-) tv+ b+>++ = DI+ D+(++) G++ e>++++ h r+++ z+++ ------END GEEK CODE BLOCK------ http://www.geekcode.com/ -> END TRANSMISSION <- _____________ 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-hackers@FreeBSD.ORG Mon Apr 25 02:16:19 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC174106566C for ; Mon, 25 Apr 2011 02:16:19 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id AD6148FC08 for ; Mon, 25 Apr 2011 02:16:19 +0000 (UTC) Received: from SBHFISLREXT03 ([10.132.254.62]) by SCSFISLTC02 (8.14.3/8.14.3) with ESMTP id p3P2GJfX026904; Sun, 24 Apr 2011 21:16:19 -0500 Received: from sbhfisltcgw02.FNFIS.COM (Not Verified[10.132.248.122]) by SBHFISLREXT03 with MailMarshal (v6, 5, 4, 7535) id ; Sun, 24 Apr 2011 21:16:49 -0500 Received: from sbhfisltcgw01.FNFIS.COM ([10.132.248.121]) by sbhfisltcgw02.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Sun, 24 Apr 2011 21:16:18 -0500 Received: from [10.0.0.102] ([10.132.254.136]) by sbhfisltcgw01.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sun, 24 Apr 2011 21:16:17 -0500 Mime-Version: 1.0 (Apple Message framework v1084) From: Devin Teske In-Reply-To: <4D907951.6020804@freebsd.org> Date: Sun, 24 Apr 2011 19:16:16 -0700 Message-Id: <0FD3E833-6FD2-400F-90B4-1C3A137AB304@vicor.com> References: <16FA7C02-86B0-46E6-A923-BC61357478FA@vicor.com> <4D907951.6020804@freebsd.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1084) X-OriginalArrivalTime: 25 Apr 2011 02:16:17.0777 (UTC) FILETIME=[C2A1FE10:01CC02EE] Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Hackers , Devin Teske Subject: Re: New Boot-Loader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 02:16:20 -0000 On Mar 28, 2011, at 5:04 AM, Andriy Gapon wrote: >=20 > Would also be cool to have an option to boot "something else" (like e.g. > memtest86). Maybe a special directory with loadable binaries and a speci= al menu > entry to select one of them. As surprising as this release is, I've actually got plans to one day releas= e our ISOLINUX based boot loader configuration that we use to do this very = thing. We use the vesamenu.c32 module to present a menu containing memtest8= 6 and many many other tools and at the top of that menu is our entry for ch= ain-loading to FreeBSD (as a default). >=20 > Probably even better to have a mechanism for pluggable menu entries like = a special > directory that would have .4th files each of which would represent one ex= tra menu > option. So instead of hacking system .4th files, one could easily extend= main > menu with custom entries. My menu.4th module (that I released today -- see druidbsd.sf.net) does prov= ide you with what you need to create not only an extended menu of your own = design, but to create multiple menus through a system of separate .4th file= s. I in-fact actually used it to that very end in one of our custom boot me= nus. Each .4th file would call "menu-clear" and then set the appropriate "m= enu_caption[N]" variables, forming an array of values of 1-9 for N (9 is th= e maximum), before finally calling menu-create (which then read in the vari= ables set in the environment and generating the menu). This is precisely on= e of the intended designs of my menu. It also has hooks for providing not o= nly toggle-state menu options but cycle-state options (for example, setting= "kernel[0]", "kernel[1]", and "kernel[2]", then having a menu item that up= on keypress would allow cycling between the three (or more) options. Though these advanced features and topics are not used in the distributed c= ode, I did not remove the underlying functions that are required/used to en= able such extended functionality. For example, you'll still find "cycle_men= uitem" in menu.4th, though it's not used by anything (waiting for some ente= rprising soul like yourself to put it to use -- though on a side-note, we'r= e still using these functions in our custom boot menus on our automated ins= tallers where we change out the logos, mascots, colors, and use the higher = level functions not required in the standard FreeBSD boot process). >=20 > Just a dream... Not a dream. I somehow think you were channeling our progress. That or grea= t minds think alike. --=20 Devin > --=20 > Andriy Gapon --=20 Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.teske@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> END TRANSMISSION <- _____________ 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-hackers@FreeBSD.ORG Mon Apr 25 02:19:03 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E93EF106566B; Mon, 25 Apr 2011 02:19:03 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id B03068FC0A; Mon, 25 Apr 2011 02:19:03 +0000 (UTC) Received: by pzk27 with SMTP id 27so1310822pzk.13 for ; Sun, 24 Apr 2011 19:19:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; bh=wUWsPRYeXuB+u7z15SCBO/S8OnL0xU3LAehWEHlqfSc=; b=cTJBZIwpeeiwnV+qCc5tllXAFI6wdqNcSccgbquM8vqd8BC+pVuGHlHSmNro9xVe7O 0iTvlFFd1COqwc1OJGUk5lo8Aud4+8KNbEbaVxT3yGumP4xRVufvGba0AwgQAuh0Myoi 3iG5RB3XHcTMn9QCQkcjhCJxLMHrP4k0p9GuU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; b=kWROkU9fNpV31pFYG1VPLAsbX29YCLec1Rt1ewUKuEA2mpng0l4vUga4fjYza/DMmW 66bWRscUAwk0zheD8cd2pOO8iwhEauPL7oA53iSXGcDUbpohnsb18BYuSke8+ouUISFJ tGgKEjT5xAf0RqvW54bRNC7V+0HCxd3xlBz5o= Received: by 10.68.56.130 with SMTP id a2mr5683984pbq.3.1303697943298; Sun, 24 Apr 2011 19:19:03 -0700 (PDT) Received: from [10.7.231.114] ([166.205.140.137]) by mx.google.com with ESMTPS id x8sm1270962pbp.27.2011.04.24.19.19.00 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 24 Apr 2011 19:19:02 -0700 (PDT) References: <20110424174442.GA45573@freebsd.org> In-Reply-To: <20110424174442.GA45573@freebsd.org> Mime-Version: 1.0 (iPhone Mail 8C148) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: X-Mailer: iPhone Mail (8C148) From: Garrett Cooper Date: Sun, 24 Apr 2011 19:18:51 -0700 To: Alexander Best Cc: "freebsd-hackers@freebsd.org" Subject: Re: exit(3) and sysexits(3) style policy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 02:19:04 -0000 On Apr 24, 2011, at 10:44 AM, Alexander Best wrote: > hi there, >=20 > i was wondering about this for some time now: >=20 > various documents decribe different policies regarding exit(3)'s return va= lues. > style(9) e.g. recommends using exit(0), while other man pages such as err(= 3) > recommend using the sysexits(3) return values. >=20 > i think i read some time ago on the mailinglists that it was decided that > exit(3) should return integers rathers than sysexits(3) values. is this > correct? shouldn't then all references such as in err(3) be removed and a > note added to sysexits(3) that returnings its values via exit(3) does not > according to current FreeBSD programming style? Bruce Evans was very anti-sysexits a while ago, and I personally agree -- in= part because they're not necessarily portable and their application isn't c= onsistent.=20= From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 25 09:09:36 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07B4B106566B for ; Mon, 25 Apr 2011 09:09:36 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 8AAAC8FC08 for ; Mon, 25 Apr 2011 09:09:35 +0000 (UTC) Received: by wwc33 with SMTP id 33so1952227wwc.31 for ; Mon, 25 Apr 2011 02:09:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:x-mailer:mime-version:content-type :content-transfer-encoding; bh=kFZrFA6g1KiwWI2u+vGn6qpoqugb2FCk6sDS16qRHZU=; b=ufnz1Ct650mHspORC2yldjoynCQ6tTGsQXw4NkTQni12Zjjdd1GeFYBFTFXVwixG9i oM8CY/f+MkbTcyPgoqyzm+MZBnal6as0HRSRf/4Uk1gw5h1VbkM2gKXm8zVVkhHfSG6x PFtKelt1juOMs5a4ekUC590RBMfQJkcsrwQeg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=AI5CLJktO5QTDfZdHb++9fC7AtpHjgPfuBmfP+3D28badKaI+wY2YSA9H9m63LdLEa U6QQwANuelTrVRB2eXz/QTh7F7VVuzo1IUUVPcsVmLqyCQkQOU7zgm5m7Gp+cvTlw7ek idmSF2mhrMGxY/NTp5miw4+QyBoKmnPlKYAPs= Received: by 10.216.59.147 with SMTP id s19mr3237605wec.25.1303720707731; Mon, 25 Apr 2011 01:38:27 -0700 (PDT) Received: from ernst.jennejohn.org (p578E3302.dip.t-dialin.net [87.142.51.2]) by mx.google.com with ESMTPS id y12sm3143587wby.59.2011.04.25.01.38.25 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 25 Apr 2011 01:38:26 -0700 (PDT) Date: Mon, 25 Apr 2011 10:38:24 +0200 From: Gary Jennejohn To: Devin Teske Message-ID: <20110425103824.5f36e5f2@ernst.jennejohn.org> In-Reply-To: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 09:09:36 -0000 On Sun, 24 Apr 2011 18:53:11 -0700 Devin Teske wrote: > I'd love to finally release (under the BSD license) my code for the > revamped FreeBSD boot loader menu. > > Here's a detailed discussion of the release complete with pictures: > http://devinteske.com/new-freebsd-boot-loader-menu > > Here's the download: > http://druidbsd.sourceforge.net/download/loader_menu-1.0.tgz > > The download is a FreeBSD package. You can execute: > > fetch [aboveURL] pkg_add loader_menu-1.0.tgz reboot > > And upon your next boot will use the new loader menu. A > feature-complete sophisticated boot menu designed from the ground up. > Although I personally never use the boot menu it's nice to see someone trying to make it more usable for the average FreeBSD user. -- Gary Jennejohn From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 25 15:39:05 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDCA51065670 for ; Mon, 25 Apr 2011 15:39:05 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id A7DD08FC1D for ; Mon, 25 Apr 2011 15:39:05 +0000 (UTC) Received: from sbhfislrext02.fnfis.com ([192.168.249.140]) by SCSFISLTC01 (8.14.3/8.14.3) with ESMTP id p3PFd3DN031186; Mon, 25 Apr 2011 10:39:03 -0500 Received: from SBHFISLTCGW04.FNFIS.COM (Not Verified[10.132.248.123]) by sbhfislrext02.fnfis.com with MailMarshal (v6, 5, 4, 7535) id ; Mon, 25 Apr 2011 10:39:02 -0500 Received: from sbhfisltcgw01.FNFIS.COM ([10.132.248.121]) by SBHFISLTCGW04.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Mon, 25 Apr 2011 10:39:02 -0500 Received: from [10.0.0.102] ([10.132.254.136]) by sbhfisltcgw01.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 25 Apr 2011 10:39:02 -0500 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Devin Teske In-Reply-To: Date: Mon, 25 Apr 2011 08:39:00 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> To: Eitan Adler X-Mailer: Apple Mail (2.1084) X-OriginalArrivalTime: 25 Apr 2011 15:39:02.0279 (UTC) FILETIME=[E6E9C170:01CC035E] Cc: FreeBSD Hackers Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 15:39:05 -0000 On Apr 25, 2011, at 8:30 AM, Eitan Adler wrote: >> I'd love to finally release (under the BSD license) my code for the reva= mped FreeBSD boot loader menu. >=20 > Woot! Community contributions under a useful license :-) >=20 >> Here's the download: >> http://druidbsd.sourceforge.net/download/loader_menu-1.0.tgz >=20 > Painless installation - thanks! >=20 >>> And upon your next boot will use the new loader menu. A feature-complet= e sophisticated boot menu designed from the ground up. >=20 > The delay "loading boot menu" seems longer than it used to be. Perhaps > this is because I never paid attention or maybe because the "progress > bar" with the dots draws attention to it. Regardless this loader makes > a lot more sense to me than the original. I've always wanted to be > able to be into SUM && verbose logging or other combinations. >=20 > I tested this on a Lenovo G530 laptop and it seems to work fine with a > few different combinations as well as at the prompt. >=20 >=20 > Thanks for your work! double-w00t! Time for the cake and punch! Thank you for trying my work. --=20 Devin >=20 >=20 >=20 > --=20 > Eitan Adler _____________ 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-hackers@FreeBSD.ORG Mon Apr 25 15:55:18 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F089D106566C for ; Mon, 25 Apr 2011 15:55:18 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id A57978FC1D for ; Mon, 25 Apr 2011 15:55:18 +0000 (UTC) Received: by vxc34 with SMTP id 34so2573500vxc.13 for ; Mon, 25 Apr 2011 08:55:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=rhBUu7DEIPuKWSCC9RrOPON3JK7J6zFbeWO3w8UU7hk=; b=ZwA8+Ney5Cw3Ki4YrykeC3143Y/jnqCyHO2idVhGcDrnT+Mi1MU4C4MD0/pMgixw00 v/r3kzaXIG4RxGCyi4Ofq22uENeirYmLz/FuKygvCE6ySmPbpv/5q2duOFwGdBTE26J1 /Ch7WRxY0SXlZzgf60RgtmPnHdeXOlpv7gO8o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=H/GntqKlcYXy5vnI9TMdk9ksaR1ZsZ4P3Zy/ujLJS4ZDtoi25Id37DoK2tNC9MTUpe 7Jboaj+QjJE/UaOHrTv3ABVdzFyNZVQbOeP31TRy3NczVQbIgPnue28e6MKvVh08zJam lS2baL6bSrMEhALH6D/wAa5stHGz0I/5oMisE= Received: by 10.52.98.3 with SMTP id ee3mr6131494vdb.140.1303745511039; Mon, 25 Apr 2011 08:31:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.181.202 with HTTP; Mon, 25 Apr 2011 08:30:24 -0700 (PDT) In-Reply-To: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> From: Eitan Adler Date: Mon, 25 Apr 2011 11:30:24 -0400 Message-ID: To: Devin Teske Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Hackers Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2011 15:55:19 -0000 > I'd love to finally release (under the BSD license) my code for the revamped FreeBSD boot loader menu. Woot! Community contributions under a useful license :-) > Here's the download: > http://druidbsd.sourceforge.net/download/loader_menu-1.0.tgz Painless installation - thanks! >> And upon your next boot will use the new loader menu. A feature-complete sophisticated boot menu designed from the ground up. The delay "loading boot menu" seems longer than it used to be. Perhaps this is because I never paid attention or maybe because the "progress bar" with the dots draws attention to it. Regardless this loader makes a lot more sense to me than the original. I've always wanted to be able to be into SUM && verbose logging or other combinations. I tested this on a Lenovo G530 laptop and it seems to work fine with a few different combinations as well as at the prompt. Thanks for your work! -- Eitan Adler From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 10:11:39 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1718E106566C for ; Tue, 26 Apr 2011 10:11:39 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id D3AAC8FC08 for ; Tue, 26 Apr 2011 10:11:38 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 07440188606E for ; Tue, 26 Apr 2011 11:53:16 +0200 (CEST) Message-ID: <4DB695DB.1080505@chillt.de> Date: Tue, 26 Apr 2011 11:52:27 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 10:11:39 -0000 Hi list I am trying to move a device driver out from under Giant on 8-STABLE. The driver has the usual probe/attach/detach and open/close/read/ioctl/poll/purge methods. So far, all were protected by each other by Giant. With that disabled, I am wondering whether I need to guard against scenarios like the following: 1. attach() is running and executes make_dev(). Before attach() has finished, someone calls open() on the newly created device node and tries to read from a device that is not fully instantiated. 2. read() is running when the device is suddenly pulled (this is a USB device) so that detach() gets run. Thus, detach() starts tearing down data structures that read() may still be accessing. 3. attach() is running when the device is pulled again, triggering detach(). Now, attach() and detach() are running concurrently, the first one initializing data structures and the second one tearing them down again. Obviously, I can avoid races under these conditions by protecting each of the above functions with a mutex. What puzzles is me is that no other device seems to be doing this. There never is a mutex involved in any attach(), detach(), open() methods... Is there some kind of implicit locking going on that I am not aware of? Are DEVMETHODs automatically protected from each other and the world? Are methods referenced by a struct cdevsw similarly protected from each other somehow? - Bartosz From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 10:18:30 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FDD3106564A for ; Tue, 26 Apr 2011 10:18:30 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.c2i.net [212.247.154.66]) by mx1.freebsd.org (Postfix) with ESMTP id 997438FC1E for ; Tue, 26 Apr 2011 10:18:29 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=0KkIQGagYCvnrzE3Z2Lmid87OPdbX6VLcZYwAuLMZ50= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=NSgU13EpIVMA:10 a=WQU8e4WWZSUA:10 a=IkcTkHD0fZMA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=Lt6ckGUMipCv9aN9IDUA:9 a=QEXdDO2ut3YA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 118961641; Tue, 26 Apr 2011 12:18:20 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Tue, 26 Apr 2011 12:17:23 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <4DB695DB.1080505@chillt.de> In-Reply-To: <4DB695DB.1080505@chillt.de> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq,NwSZ4V" =?iso-8859-1?q?=7CLR=2E+tj=7Dg5=0A=09=25V?=,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( =?iso-8859-1?q?=0A=09=3AAuzV9=3A=2EhESm-x4h240C=609=3Dw?= MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104261217.23858.hselasky@c2i.net> Cc: Bartosz Fabianowski Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 10:18:30 -0000 On Tuesday 26 April 2011 11:52:27 Bartosz Fabianowski wrote: > 1. attach() is running and executes make_dev(). Before attach() has > finished, someone calls open() on the newly created device node and > tries to read from a device that is not fully instantiated. > > 2. read() is running when the device is suddenly pulled (this is a USB > device) so that detach() gets run. Thus, detach() starts tearing down > data structures that read() may still be accessing. Hi, You need to handle all cases in your driver. Fortunately there exists a solution for this already, called USB cdev. See serial/ulpt.c for example. --HPS From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 12:39:22 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2ABB81065673 for ; Tue, 26 Apr 2011 12:39:22 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id E47B88FC25 for ; Tue, 26 Apr 2011 12:39:21 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 28D00188606E; Tue, 26 Apr 2011 14:39:20 +0200 (CEST) Message-ID: <4DB6BCC6.5050001@chillt.de> Date: Tue, 26 Apr 2011 14:38:30 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Hans Petter Selasky References: <4DB695DB.1080505@chillt.de> <201104261217.23858.hselasky@c2i.net> In-Reply-To: <201104261217.23858.hselasky@c2i.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 12:39:22 -0000 > You need to handle all cases in your driver. Fortunately there exists a > solution for this already, called USB cdev. See I went through all the USB drivers with a fine comb (the driver I am porting was based on the old USB stack and so I needed to adjust it for the new stack). Drivers like ulpt seem to be based around usb_fifo_* structures. If I understand usb_fifo_* right, it gives you a single device with FIFO semantics. This is not sufficient in my case. My device is opened for reading by several processes in parallel and needs to keep a separate FIFO per process. I implemented this via device cloning - and I could not see how to integrate that with usb_fifo_*. Thus, I based my driver on the raw cdev framework. Am I missing something obvious and making my life unnecessarily hard? - Bartosz From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 12:44:14 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6ED4A106564A for ; Tue, 26 Apr 2011 12:44:14 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id E200E8FC19 for ; Tue, 26 Apr 2011 12:44:13 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p3QCi3dk051887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Apr 2011 15:44:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p3QCi35r084042; Tue, 26 Apr 2011 15:44:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p3QCi3xg084041; Tue, 26 Apr 2011 15:44:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 26 Apr 2011 15:44:03 +0300 From: Kostik Belousov To: Bartosz Fabianowski Message-ID: <20110426124403.GQ48734@deviant.kiev.zoral.com.ua> References: <4DB695DB.1080505@chillt.de> <201104261217.23858.hselasky@c2i.net> <4DB6BCC6.5050001@chillt.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WeAyUrhnD1IdQdNw" Content-Disposition: inline In-Reply-To: <4DB6BCC6.5050001@chillt.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_20, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 12:44:14 -0000 --WeAyUrhnD1IdQdNw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 26, 2011 at 02:38:30PM +0200, Bartosz Fabianowski wrote: > >You need to handle all cases in your driver. Fortunately there exists a > >solution for this already, called USB cdev. See >=20 > I went through all the USB drivers with a fine comb (the driver I am=20 > porting was based on the old USB stack and so I needed to adjust it for= =20 > the new stack). Drivers like ulpt seem to be based around usb_fifo_*=20 > structures. If I understand usb_fifo_* right, it gives you a single=20 > device with FIFO semantics. This is not sufficient in my case. My device= =20 > is opened for reading by several processes in parallel and needs to keep= =20 > a separate FIFO per process. I implemented this via device cloning - and= =20 > I could not see how to integrate that with usb_fifo_*. Thus, I based my= =20 > driver on the raw cdev framework. Am I missing something obvious and=20 > making my life unnecessarily hard? If you needs per-file private data for cdev, you would be better served by cdevpriv(9) KPI. Cloning is too hard to use correctly for such task. --WeAyUrhnD1IdQdNw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk22vhMACgkQC3+MBN1Mb4jq/ACgh7bEvUdwzsQyqdmlB0VAILBZ jmcAniztTn+VDRY8pitGjQ/F2RDTvHsI =noOB -----END PGP SIGNATURE----- --WeAyUrhnD1IdQdNw-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 13:42:05 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DA3E1065670 for ; Tue, 26 Apr 2011 13:42:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 649F68FC16 for ; Tue, 26 Apr 2011 13:42:05 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id A961D46B39; Tue, 26 Apr 2011 09:42:04 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 052DF8A01B; Tue, 26 Apr 2011 09:42:04 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 26 Apr 2011 09:42:03 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DB695DB.1080505@chillt.de> In-Reply-To: <4DB695DB.1080505@chillt.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104260942.03543.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 26 Apr 2011 09:42:04 -0400 (EDT) Cc: Bartosz Fabianowski Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 13:42:05 -0000 On Tuesday, April 26, 2011 5:52:27 am Bartosz Fabianowski wrote: > Hi list > > I am trying to move a device driver out from under Giant on 8-STABLE. > The driver has the usual probe/attach/detach and > open/close/read/ioctl/poll/purge methods. So far, all were protected by > each other by Giant. With that disabled, I am wondering whether I need > to guard against scenarios like the following: > > 1. attach() is running and executes make_dev(). Before attach() has > finished, someone calls open() on the newly created device node and > tries to read from a device that is not fully instantiated. > > 2. read() is running when the device is suddenly pulled (this is a USB > device) so that detach() gets run. Thus, detach() starts tearing down > data structures that read() may still be accessing. > > 3. attach() is running when the device is pulled again, triggering > detach(). Now, attach() and detach() are running concurrently, the first > one initializing data structures and the second one tearing them down again. > > Obviously, I can avoid races under these conditions by protecting each > of the above functions with a mutex. What puzzles is me is that no other > device seems to be doing this. There never is a mutex involved in any > attach(), detach(), open() methods... Is there some kind of implicit > locking going on that I am not aware of? Are DEVMETHODs automatically > protected from each other and the world? Are methods referenced by a > struct cdevsw similarly protected from each other somehow? The probe/attach/detach stuff is still under Giant. However, you will have to do your own locking to handle races. Many of these races can be handled without locks however: - Don't call make_dev() until your device is fully ready in attach() (e.g. at the end.. NIC drivers tend to call ether_ifattach() as the very last thing for this same reason). - Call destroy_dev() as the first thing in detach. destroy_dev() will block until any calls to your cdevsw routines return (so if a thread is in read() when detach happens, destroy_dev() will hang until your read() call returns). Note that if you need to wake up waiting threads when destroy_dev() is called, you can provide a d_purge method in your cdevsw. This function is called from destroy_dev() every 100 milliseconds in a loop while there are waiting threads. - The Giant protection for new-bus should prevent attach/detach from running concurrently I believe (either that or the USB bus itself should ensure that the two instances of your device have seperate device_t instances with separate softc's, so current attach/detach should not matter except that they may both try to talk to the same hardware perhaps? In that case that is something the USB bus driver should fix by prevent a device from attaching at an existing address until any existing device at that address is fully detached). -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 14:31:06 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 344DE106564A; Tue, 26 Apr 2011 14:31:06 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id E722A8FC1D; Tue, 26 Apr 2011 14:31:05 +0000 (UTC) Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p3QERE61034182 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 26 Apr 2011 08:27:14 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <201104260942.03543.jhb@freebsd.org> Date: Tue, 26 Apr 2011 08:27:14 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <5627117D-499B-4FD7-BF84-BE4BE6F583D7@bsdimp.com> References: <4DB695DB.1080505@chillt.de> <201104260942.03543.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Tue, 26 Apr 2011 08:27:14 -0600 (MDT) Cc: freebsd-hackers@freebsd.org, Bartosz Fabianowski Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 14:31:06 -0000 On Apr 26, 2011, at 7:42 AM, John Baldwin wrote: > - The Giant protection for new-bus should prevent attach/detach from = running > concurrently I believe (either that or the USB bus itself should = ensure > that the two instances of your device have seperate device_t = instances with > separate softc's, so current attach/detach should not matter except = that > they may both try to talk to the same hardware perhaps? In that = case that > is something the USB bus driver should fix by prevent a device from > attaching at an existing address until any existing device at that = address > is fully detached). I thought that if we held Giant when we're about to go to sleep that we = drop it as a special case. So if any newbus-releated function sleeps, = we can have a situation where attach is running and detach gets called. = There is (or was) some code to cope with this in CardBus, iirc. I'm = surprised there isn't any in USB, since Hans was the one that alerted me = to this issue. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 14:37:19 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7ABCD106564A for ; Tue, 26 Apr 2011 14:37:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4DEBA8FC08 for ; Tue, 26 Apr 2011 14:37:19 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id E09AF46B32; Tue, 26 Apr 2011 10:37:18 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5C61A8A027; Tue, 26 Apr 2011 10:37:18 -0400 (EDT) From: John Baldwin To: Warner Losh Date: Tue, 26 Apr 2011 10:37:17 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DB695DB.1080505@chillt.de> <201104260942.03543.jhb@freebsd.org> <5627117D-499B-4FD7-BF84-BE4BE6F583D7@bsdimp.com> In-Reply-To: <5627117D-499B-4FD7-BF84-BE4BE6F583D7@bsdimp.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104261037.17893.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 26 Apr 2011 10:37:18 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, Bartosz Fabianowski Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 14:37:19 -0000 On Tuesday, April 26, 2011 10:27:14 am Warner Losh wrote: > > On Apr 26, 2011, at 7:42 AM, John Baldwin wrote: > > - The Giant protection for new-bus should prevent attach/detach from running > > concurrently I believe (either that or the USB bus itself should ensure > > that the two instances of your device have seperate device_t instances with > > separate softc's, so current attach/detach should not matter except that > > they may both try to talk to the same hardware perhaps? In that case that > > is something the USB bus driver should fix by prevent a device from > > attaching at an existing address until any existing device at that address > > is fully detached). > > I thought that if we held Giant when we're about to go to sleep that we drop > it as a special case. So if any newbus-releated function sleeps, we can > have a situation where attach is running and detach gets called. There is > (or was) some code to cope with this in CardBus, iirc. I'm surprised there > isn't any in USB, since Hans was the one that alerted me to this issue. Yes, Giant doesn't really provide too much help here. However, the real fix should be in the USB bus, and USB peripheral drivers should not have to worry about handling concurrent attach/detach (they can't really handle it safely anyway). -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 14:41:19 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 985C4106566C; Tue, 26 Apr 2011 14:41:19 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id E7F108FC12; Tue, 26 Apr 2011 14:41:18 +0000 (UTC) Received: by fxm11 with SMTP id 11so657801fxm.13 for ; Tue, 26 Apr 2011 07:41:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LQ4toyM4O4av3Ts7Guh7WqelFJU4C0Q8xZer+j5PmGw=; b=Ugy6GB/UzAVEKg+UsOa/SOBJ0B74HTjmtOZ/ug/jKLtghK+MPmruMc97D47iAD0cOu rT8sC1NtP2wdyukvZzmxKIERR/lbYT1jljW7QCG3aoOmX6bVMRBKOqqEtFLAeut4Qi1m VitTgbqshQLCBzdd4DXQCSICqsMzR004nttq0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=CAYLOxyJ9UdCgylEmDjS9Fk4zq7KViGjfgqPcjlmBtnJYNUJM9SHmolUVwuqhS4YM2 bepY/Cje847fAHHx7iySxTGLhZUCjksZCamdnULZuaHPQn72iHN6mBMjeH1VlaFivY1w IEg4zYMOXXERF38UT4hyhTnmLVOkG9VIT39Zo= Received: by 10.223.30.82 with SMTP id t18mr899246fac.106.1303827001775; Tue, 26 Apr 2011 07:10:01 -0700 (PDT) Received: from localhost.localdomain ([213.152.137.45]) by mx.google.com with ESMTPS id k5sm2013816faa.39.2011.04.26.07.09.57 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 07:09:59 -0700 (PDT) Message-ID: <4DB6D264.2060209@gmail.com> Date: Tue, 26 Apr 2011 18:10:44 +0400 From: Vladimir Laskov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9 MIME-Version: 1.0 To: Sergey Kandaurov References: <4D553027.5040606@gmail.com> <201102111531.00915.jhb@freebsd.org> <4D5E5476.5010107@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: problem with build mcelog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 14:41:19 -0000 On 02/18/2011 03:11 PM, Sergey Kandaurov wrote: > On 18 February 2011 14:13, venom wrote: >> On 02/11/2011 11:31 PM, John Baldwin wrote: >>> On Friday, February 11, 2011 7:48:39 am venom wrote: >>>> Hello. >>>> >>>> i am trying build mcelog >>>> >>>> >>>> FreeBSD XXXX 8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #0: Fri Jan 14 >>>> 04:15:56 >>>> UTC 2011 root@freebsd:/usr/obj/usr/src/sys/GENERIC amd64 >>>> >>>> >>>> # fetch >>>> http://ftp2.pl.freebsd.org/pub/FreeBSD/distfiles/mcelog-1.0pre2.tar.gz >>>> # tar -xf mcelog-1.0pre2.tar.gz >>>> # cd mcelog-1.0pre2 >>>> # fetch http://people.freebsd.org/~jhb/mcelog/mcelog.patch >>>> # fetch http://people.freebsd.org/~jhb/mcelog/memstream.c >>> Oops, I just updated mcelog.patch and it should work fine now. >>> >> |--- //depot/vendor/mcelog/tsc.c 2010-03-05 20:24:22.000000000 0000 >> |+++ //depot/projects/mcelog/tsc.c 2010-03-05 21:09:24.000000000 0000 >> -------------------------- >> Patching file tsc.c using Plan A... >> Hunk #1 succeeded at 15. >> Hunk #2 succeeded at 52. >> Hunk #3 succeeded at 75. >> Hunk #4 succeeded at 156. >> done >> 12:12:46 ~/temp/MCE/mcelog-1.0pre2 >> # gmake FREEBSD=yes >> Makefile:92: .depend: No such file or directory >> cc -MM -I. p4.c k8.c mcelog.c dmi.c tsc.c core2.c bitfield.c intel.c >> nehalem.c dunnington.c tulsa.c config.c memutil.c msg.c eventloop.c >> leaky-bucket.c memdb.c server.c client.c cache.c rbtree.c memstream.c> >> .depend.X&& mv .depend.X .depend >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o mcelog.o mcelog.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o p4.o p4.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o k8.o k8.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o dmi.o dmi.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o tsc.o tsc.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o core2.o core2.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o bitfield.o >> bitfield.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o intel.o intel.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o nehalem.o nehalem.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o dunnington.o >> dunnington.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o tulsa.o tulsa.c >> cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers >> -Wno-unused-parameter -Wstrict-prototypes -Wformat-security >> -Wmissing-declarations -Wdeclaration-after-statement -o config.o config.c >> config.c:135: error: static declaration of 'getline' follows non-static >> declaration >> /usr/include/stdio.h:370: error: previous declaration of 'getline' was here >> gmake: *** [config.o] Error 1 >> > A local getline() needs the FreeBSD version check. > > %%% > --- config.c.olg 2011-02-18 14:57:52.000000000 +0300 > +++ config.c 2011-02-18 15:07:59.000000000 +0300 > @@ -18,6 +18,9 @@ > Author: Andi Kleen > */ > #define _GNU_SOURCE 1 > +#ifdef __FreeBSD__ > +# include > +#endif > #include > #include > #include > @@ -126,7 +129,7 @@ > return s; > } > > -#ifdef __FreeBSD__ > +#if (defined __FreeBSD__)&& (__FreeBSD_version< 800067) > /* > * Newer versions do have getline(), so this should use a version test > * at some point. > %%% > thanks on amd64 it work fine # gmake FREEBSD=yes Makefile:92: .depend: No such file or directory cc -MM -I. p4.c k8.c mcelog.c dmi.c tsc.c core2.c bitfield.c intel.c nehalem.c dunnington.c tulsa.c config.c memutil.c msg.c eventloop.c leaky-bucket.c memdb.c server.c client.c cache.c rbtree.c memstream.c > .depend.X && mv .depend.X .depend cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o mcelog.o mcelog.c *** server.c: In function 'server_ping': server.c:339: warning: passing argument 2 of 'connect' from incompatible pointer type cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o client.o client.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o cache.o cache.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o rbtree.o rbtree.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o memstream.o memstream.c memstream.c:111: warning: no previous declaration for 'open_memstream' cc mcelog.o p4.o k8.o dmi.o tsc.o core2.o bitfield.o intel.o nehalem.o dunnington.o tulsa.o config.o memutil.o msg.o eventloop.o leaky-bucket.o memdb.o server.o client.o cache.o rbtree.o memstream.o /usr/lib/libkvm.so -o mcelog # have problem for i386 ============================================== # gmake FREEBSD=yes i386=yes Makefile:92: .depend: No such file or directory cc -MM -I. p4.c k8.c mcelog.c dmi.c tsc.c core2.c bitfield.c intel.c nehalem.c dunnington.c tulsa.c config.c memutil.c msg.c eventloop.c leaky-bucket.c memdb.c server.c client.c cache.c rbtree.c memstream.c > .depend.X && mv .depend.X .depend cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o mcelog.o mcelog.c In file included from mcelog.c:52: mcelog.h:112: error: expected identifier before numeric constant mcelog.c: In function 'bankname': mcelog.c:138: error: 'CPU_NEHALEM' undeclared (first use in this function) mcelog.c:138: error: (Each undeclared identifier is reported only once mcelog.c:138: error: for each function it appears in.) mcelog.c:138: error: 'CPU_DUNNINGTON' undeclared (first use in this function) mcelog.c:138: error: 'CPU_TULSA' undeclared (first use in this function) mcelog.c: In function 'mce_filter': mcelog.c:163: error: 'CPU_NEHALEM' undeclared (first use in this function) mcelog.c:163: error: 'CPU_DUNNINGTON' undeclared (first use in this function) mcelog.c:163: error: 'CPU_TULSA' undeclared (first use in this function) mcelog.c: At top level: mcelog.c:218: error: 'CPU_NEHALEM' undeclared here (not in a function) mcelog.c:218: error: array index in initializer not of integer type mcelog.c:218: error: (near initialization for 'cputype_name') mcelog.c:219: error: 'CPU_DUNNINGTON' undeclared here (not in a function) mcelog.c:219: error: array index in initializer not of integer type mcelog.c:219: error: (near initialization for 'cputype_name') mcelog.c:220: error: 'CPU_TULSA' undeclared here (not in a function) mcelog.c:220: error: array index in initializer not of integer type mcelog.c:220: error: (near initialization for 'cputype_name') mcelog.c: In function 'decodefatal': mcelog.c:835: warning: integer constant is too large for 'long' type mcelog.c:838: warning: integer constant is too large for 'long' type mcelog.c:921: warning: integer constant is too large for 'long' type mcelog.c:923: warning: integer constant is too large for 'long' type gmake: *** [mcelog.o] Error 1 -- Vladimir Laskov From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 14:43:26 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E41E106566B; Tue, 26 Apr 2011 14:43:26 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id B5E9D8FC16; Tue, 26 Apr 2011 14:43:25 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=NvrFngl24Vvwb7eBef0tfsytOWEnP/WlkqxQrRnklhk= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=NSgU13EpIVMA:10 a=WQU8e4WWZSUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=8bDjwUAGVKT74-45mFsA:9 a=wPNLvfGTeEIA:10 a=M8q0rZJ2Y_bfsept:21 a=pHEeH1OnV-vjp8f0:21 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 118131955; Tue, 26 Apr 2011 16:43:14 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Tue, 26 Apr 2011 16:42:17 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <4DB695DB.1080505@chillt.de> <5627117D-499B-4FD7-BF84-BE4BE6F583D7@bsdimp.com> <201104261037.17893.jhb@freebsd.org> In-Reply-To: <201104261037.17893.jhb@freebsd.org> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104261642.17569.hselasky@c2i.net> Cc: Bartosz Fabianowski Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 14:43:26 -0000 On Tuesday 26 April 2011 16:37:17 John Baldwin wrote: > On Tuesday, April 26, 2011 10:27:14 am Warner Losh wrote: > > On Apr 26, 2011, at 7:42 AM, John Baldwin wrote: > > > - The Giant protection for new-bus should prevent attach/detach from > > > running > > > > > > concurrently I believe (either that or the USB bus itself should > > > ensure that the two instances of your device have seperate device_t > > > instances with separate softc's, so current attach/detach should not > > > matter except that they may both try to talk to the same hardware > > > perhaps? In that case that is something the USB bus driver should > > > fix by prevent a device from attaching at an existing address until > > > any existing device at that address is fully detached). > > > > I thought that if we held Giant when we're about to go to sleep that we > > drop it as a special case. So if any newbus-releated function sleeps, > > we can have a situation where attach is running and detach gets called. > > There is (or was) some code to cope with this in CardBus, iirc. I'm > > surprised there isn't any in USB, since Hans was the one that alerted me > > to this issue. > > Yes, Giant doesn't really provide too much help here. However, the real > fix should be in the USB bus, and USB peripheral drivers should not have > to worry about handling concurrent attach/detach (they can't really handle > it safely anyway). Hi, All detach/attach/suspend/resume functions on a device tree belonging to the same USB controller are executed from a single thread, which is called the root HUB thread. --HPS From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 15:43:02 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CFCA106566C for ; Tue, 26 Apr 2011 15:43:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 303728FC0C for ; Tue, 26 Apr 2011 15:43:02 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id ACC6646B43; Tue, 26 Apr 2011 11:43:01 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 22E2C8A02A; Tue, 26 Apr 2011 11:43:01 -0400 (EDT) From: John Baldwin To: Vladimir Laskov Date: Tue, 26 Apr 2011 11:43:00 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4D553027.5040606@gmail.com> <4DB6D264.2060209@gmail.com> In-Reply-To: <4DB6D264.2060209@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104261143.00644.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 26 Apr 2011 11:43:01 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, Sergey Kandaurov Subject: Re: problem with build mcelog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 15:43:02 -0000 On Tuesday, April 26, 2011 10:10:44 am Vladimir Laskov wrote: > have problem for i386 > ============================================== > > # gmake FREEBSD=yes i386=yes > Makefile:92: .depend: No such file or directory > cc -MM -I. p4.c k8.c mcelog.c dmi.c tsc.c core2.c bitfield.c intel.c > nehalem.c dunnington.c tulsa.c config.c memutil.c msg.c eventloop.c > leaky-bucket.c memdb.c server.c client.c cache.c rbtree.c memstream.c > > .depend.X && mv .depend.X .depend > cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers > -Wno-unused-parameter -Wstrict-prototypes -Wformat-security > -Wmissing-declarations -Wdeclaration-after-statement -o mcelog.o mcelog.c > In file included from mcelog.c:52: > mcelog.h:112: error: expected identifier before numeric constant > mcelog.c: In function 'bankname': > mcelog.c:138: error: 'CPU_NEHALEM' undeclared (first use in this function) > mcelog.c:138: error: (Each undeclared identifier is reported only once > mcelog.c:138: error: for each function it appears in.) > mcelog.c:138: error: 'CPU_DUNNINGTON' undeclared (first use in this > function) > mcelog.c:138: error: 'CPU_TULSA' undeclared (first use in this function) > mcelog.c: In function 'mce_filter': > mcelog.c:163: error: 'CPU_NEHALEM' undeclared (first use in this function) > mcelog.c:163: error: 'CPU_DUNNINGTON' undeclared (first use in this > function) > mcelog.c:163: error: 'CPU_TULSA' undeclared (first use in this function) > mcelog.c: At top level: > mcelog.c:218: error: 'CPU_NEHALEM' undeclared here (not in a function) > mcelog.c:218: error: array index in initializer not of integer type > mcelog.c:218: error: (near initialization for 'cputype_name') > mcelog.c:219: error: 'CPU_DUNNINGTON' undeclared here (not in a function) > mcelog.c:219: error: array index in initializer not of integer type > mcelog.c:219: error: (near initialization for 'cputype_name') > mcelog.c:220: error: 'CPU_TULSA' undeclared here (not in a function) > mcelog.c:220: error: array index in initializer not of integer type > mcelog.c:220: error: (near initialization for 'cputype_name') > mcelog.c: In function 'decodefatal': > mcelog.c:835: warning: integer constant is too large for 'long' type > mcelog.c:838: warning: integer constant is too large for 'long' type > mcelog.c:921: warning: integer constant is too large for 'long' type > mcelog.c:923: warning: integer constant is too large for 'long' type > gmake: *** [mcelog.o] Error 1 Oops, please try this additional patch: --- //depot/projects/mcelog/mcelog.c 2010-08-25 11:41:19.000000000 0000 +++ /home/jhb/work/p4/mcelog/mcelog.c 2010-08-25 11:41:19.000000000 0000 @@ -29,6 +29,10 @@ #include #include #include +#ifdef __i386__ +/* Conflicts with 'enum cputype' in . */ +#undef CPU_P4 +#endif #include #include #include -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 26 15:46:41 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC184106566B for ; Tue, 26 Apr 2011 15:46:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 46D6E8FC08 for ; Tue, 26 Apr 2011 15:46:41 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id D59AA46B09; Tue, 26 Apr 2011 11:46:40 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 49AD38A027; Tue, 26 Apr 2011 11:46:40 -0400 (EDT) From: John Baldwin To: Hans Petter Selasky Date: Tue, 26 Apr 2011 11:43:32 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DB695DB.1080505@chillt.de> <201104261037.17893.jhb@freebsd.org> <201104261642.17569.hselasky@c2i.net> In-Reply-To: <201104261642.17569.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104261143.32591.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 26 Apr 2011 11:46:40 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, Bartosz Fabianowski Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 15:46:41 -0000 On Tuesday, April 26, 2011 10:42:17 am Hans Petter Selasky wrote: > On Tuesday 26 April 2011 16:37:17 John Baldwin wrote: > > On Tuesday, April 26, 2011 10:27:14 am Warner Losh wrote: > > > On Apr 26, 2011, at 7:42 AM, John Baldwin wrote: > > > > - The Giant protection for new-bus should prevent attach/detach from > > > > running > > > > > > > > concurrently I believe (either that or the USB bus itself should > > > > ensure that the two instances of your device have seperate device_t > > > > instances with separate softc's, so current attach/detach should not > > > > matter except that they may both try to talk to the same hardware > > > > perhaps? In that case that is something the USB bus driver should > > > > fix by prevent a device from attaching at an existing address until > > > > any existing device at that address is fully detached). > > > > > > I thought that if we held Giant when we're about to go to sleep that we > > > drop it as a special case. So if any newbus-releated function sleeps, > > > we can have a situation where attach is running and detach gets called. > > > There is (or was) some code to cope with this in CardBus, iirc. I'm > > > surprised there isn't any in USB, since Hans was the one that alerted me > > > to this issue. > > > > Yes, Giant doesn't really provide too much help here. However, the real > > fix should be in the USB bus, and USB peripheral drivers should not have > > to worry about handling concurrent attach/detach (they can't really handle > > it safely anyway). > > Hi, > > All detach/attach/suspend/resume functions on a device tree belonging to the > same USB controller are executed from a single thread, which is called the > root HUB thread. Ok, that should work fine then to serialize the detach and attach. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 00:18:01 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 467C8106564A for ; Wed, 27 Apr 2011 00:18:01 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 07F108FC0A for ; Wed, 27 Apr 2011 00:18:00 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 087251886072; Wed, 27 Apr 2011 02:17:58 +0200 (CEST) Message-ID: <4DB76085.4000402@chillt.de> Date: Wed, 27 Apr 2011 02:17:09 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Kostik Belousov References: <4DB695DB.1080505@chillt.de> <201104261217.23858.hselasky@c2i.net> <4DB6BCC6.5050001@chillt.de> <20110426124403.GQ48734@deviant.kiev.zoral.com.ua> In-Reply-To: <20110426124403.GQ48734@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 00:18:01 -0000 > If you needs per-file private data for cdev, you would be better served > by cdevpriv(9) KPI. Cloning is too hard to use correctly for such task. Thanks, I just got that working. To help those going down a similar path in the future, I would like to note quickly that the following must be added to the cdevsw structure to ensure proper clean-up: .d_flags = D_TRACKCLOSE I just spent hours debugging panics until I realized only the last close() was triggering a call to my .d_close method. - Bartosz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 04:58:19 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7162A1065670 for ; Wed, 27 Apr 2011 04:58:19 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 2E76B8FC16 for ; Wed, 27 Apr 2011 04:58:19 +0000 (UTC) Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p3R4qbmr041966 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Tue, 26 Apr 2011 22:52:38 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <4DB76085.4000402@chillt.de> Date: Tue, 26 Apr 2011 22:52:37 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <52F5A9FB-8771-4002-B6C0-563679CCB355@bsdimp.com> References: <4DB695DB.1080505@chillt.de> <201104261217.23858.hselasky@c2i.net> <4DB6BCC6.5050001@chillt.de> <20110426124403.GQ48734@deviant.kiev.zoral.com.ua> <4DB76085.4000402@chillt.de> To: Bartosz Fabianowski X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Tue, 26 Apr 2011 22:52:39 -0600 (MDT) Cc: Kostik Belousov , freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 04:58:19 -0000 On Apr 26, 2011, at 6:17 PM, Bartosz Fabianowski wrote: >> If you needs per-file private data for cdev, you would be better = served >> by cdevpriv(9) KPI. Cloning is too hard to use correctly for such = task. >=20 > Thanks, I just got that working. To help those going down a similar = path in the future, I would like to note quickly that the following must = be added to the cdevsw structure to ensure proper clean-up: >=20 > .d_flags =3D D_TRACKCLOSE >=20 > I just spent hours debugging panics until I realized only the last = close() was triggering a call to my .d_close method. Traditional BSD behavior... Warner From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 07:40:24 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA90E106564A; Wed, 27 Apr 2011 07:40:24 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 319188FC0C; Wed, 27 Apr 2011 07:40:23 +0000 (UTC) Received: by ewy1 with SMTP id 1so563101ewy.13 for ; Wed, 27 Apr 2011 00:40:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=CLBibcWE9q9vMa0jD8JMQEOAr97YJlGq9Ex70T5RHic=; b=GNHBThMQLRXA0+S4EKhXhT3WnwK2SZfVfXoaavWXZjO8DDBLjr4oMP+lHz/fz3Rcq0 XVYijfyq6efZhKXaT83nRlI9vfL+eCR31yBjoj/JxTeawrtuGk0Qp6PUVkUfUyIWZhoS 7eogPM4dEChOz/3DN45Q6cMzYetNgpaTkdAKk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=TqQoHJ8uV7Fslg+6Iapv63P5RuwqrLh5utvS87QxlTszVB2uQu4RjYCBxeiezL76kU i9PI5r7kOWLALiNlJfFVJpJLRjH1glBx8Ut2uVQZLGYWinyTLmSbr1Z1vdzAVzppVQ3n Op9kN5r4lJkhtIPWgmSGrfp8u2H2q2Pq0SSeE= Received: by 10.213.19.141 with SMTP id a13mr2272382ebb.130.1303890023108; Wed, 27 Apr 2011 00:40:23 -0700 (PDT) Received: from localhost.localdomain ([213.152.137.45]) by mx.google.com with ESMTPS id s49sm361394eei.5.2011.04.27.00.40.20 (version=SSLv3 cipher=OTHER); Wed, 27 Apr 2011 00:40:21 -0700 (PDT) Message-ID: <4DB7C893.9050903@gmail.com> Date: Wed, 27 Apr 2011 11:41:07 +0400 From: Vladimir Laskov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9 MIME-Version: 1.0 To: John Baldwin References: <4D553027.5040606@gmail.com> <4DB6D264.2060209@gmail.com> <201104261143.00644.jhb@freebsd.org> In-Reply-To: <201104261143.00644.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Sergey Kandaurov Subject: Re: problem with build mcelog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 07:40:24 -0000 On 04/26/2011 07:43 PM, John Baldwin wrote: > --- //depot/projects/mcelog/mcelog.c 2010-08-25 11:41:19.000000000 0000 > +++ /home/jhb/work/p4/mcelog/mcelog.c 2010-08-25 11:41:19.000000000 0000 > @@ -29,6 +29,10 @@ > #include > #include > #include > +#ifdef __i386__ > +/* Conflicts with 'enum cputype' in. */ > +#undef CPU_P4 > +#endif > #include > #include > #include > thanks, it work ====================================== # gmake FREEBSD=yes i386=yes Makefile:92: .depend: No such file or directory cc -MM -I. p4.c k8.c mcelog.c dmi.c tsc.c core2.c bitfield.c intel.c nehalem.c dunnington.c tulsa.c config.c memutil.c msg.c eventloop.c leaky-bucket.c memdb.c server.c client.c cache.c rbtree.c memstream.c > .depend.X && mv .depend.X .depend cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o mcelog.o mcelog.c mcelog.c: In function 'decodefatal': mcelog.c:839: warning: integer constant is too large for 'long' type mcelog.c:842: warning: integer constant is too large for 'long' type mcelog.c:925: warning: integer constant is too large for 'long' type mcelog.c:927: warning: integer constant is too large for 'long' type cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o p4.o p4.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o k8.o k8.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o dmi.o dmi.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o tsc.o tsc.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o core2.o core2.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o bitfield.o bitfield.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o intel.o intel.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o nehalem.o nehalem.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o dunnington.o dunnington.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o tulsa.o tulsa.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o config.o config.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o memutil.o memutil.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o msg.o msg.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o eventloop.o eventloop.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o leaky-bucket.o leaky-bucket.c leaky-bucket.c: In function 'bucket_age': leaky-bucket.c:33: warning: comparison between signed and unsigned cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o memdb.o memdb.c memdb.c: In function 'memdb_trigger': memdb.c:166: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'time_t' cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o server.o server.c server.c: In function 'server_ping': server.c:339: warning: passing argument 2 of 'connect' from incompatible pointer type cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o client.o client.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o cache.o cache.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o rbtree.o rbtree.c cc -c -g -Os -Wall -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wstrict-prototypes -Wformat-security -Wmissing-declarations -Wdeclaration-after-statement -o memstream.o memstream.c memstream.c:111: warning: no previous declaration for 'open_memstream' cc mcelog.o p4.o k8.o dmi.o tsc.o core2.o bitfield.o intel.o nehalem.o dunnington.o tulsa.o config.o memutil.o msg.o eventloop.o leaky-bucket.o memdb.o server.o client.o cache.o rbtree.o memstream.o /usr/lib/libkvm.so -o mcelog ============================================= my questions: - how to work mcelog without mcelogdevice ? - Is it possible to use mcelog in daemon mode in FreeBSD? -- Vladimir Laskov From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 10:58:24 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E12E106582B; Wed, 27 Apr 2011 10:58:24 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 494C58FC12; Wed, 27 Apr 2011 10:58:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p3RAwOAe062697; Wed, 27 Apr 2011 10:58:24 GMT (envelope-from danger@freefall.freebsd.org) Received: (from danger@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p3RAwO7G062696; Wed, 27 Apr 2011 10:58:24 GMT (envelope-from danger) Date: Wed, 27 Apr 2011 10:58:24 +0000 From: Daniel Gerzo To: current@freebsd.org Message-ID: <20110427105824.GA62682@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, hackers@freebsd.org Subject: FreeBSD Status Report January-March, 2011 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 10:58:24 -0000 FreeBSD Quarterly Status Report January-March, 2011 Introduction This report covers FreeBSD-related projects between January and March 2011. It is the first of the four reports planned for 2011. During this quarter, the work was focused on releasing the new minor versions of FreeBSD, 7.4 and 8.2, which were released in February 2011. Currently, the project is starting to work on the next major version, 9.0. Thanks to all the reporters for the excellent work! This report contains 34 entries and we hope you enjoy reading it. Please note that the deadline for submissions covering the period between April and June 2011 is July 15th, 2011. __________________________________________________________________ Projects * Bringing up OMAP3 * GEOM-based ataraid(4) Replacement -- geom_raid. * HAST (Highly Available Storage) * New FreeBSD Installer * OpenAFS Port * pfSense * RCTL, aka Resource Containers * ZFSv28 available in FreeBSD 9-CURRENT FreeBSD Team Reports * FreeBSD Bugbusting Team * FreeBSD NYI Admins Status Report * The FreeBSD Foundation Status Report Network Infrastructure * DIstributed Firewall and Flow-shaper Using Statistical Evidence (DIFFUSE) * Five New TCP Congestion Control Algorithms for FreeBSD Kernel * Journaled Soft Updates * Linux Compatibility Layer - DVB and V4L2 Support Documentation * New FreeBSD Handbook Section Covering HAST * The FreeBSD German Documentation Project Status Report * The FreeBSD Japanese Documentation Project * Webcam and DVB Compatibility List Architectures * FreeBSD/arm on Marvell Raid-on-Chip * FreeBSD/EC2 * FreeBSD/powerpc on Freescale QorIQ * MIPS/Octeon Support and bootinfo Ports * FreeBSD as Home Theater PC * FreeBSD Chromium * FreeBSD Haskell Ports * KDE-FreeBSD * Linux Emulation Ports * Portmaster * Ports Collection * www/apache22 Default Miscellaneous * BSDCan Google Summer of Code * Extfs Status Report * Google Summer of Code 2011 __________________________________________________________________ Bringing up OMAP3 Contact: Warner Losh Contact: Mohammed Farrag OMAP3 Emulation: * Step #1: qemu-omap3 isn't ported to FreeBSD yet. So, * Step #2: Use qemu-omap3 on Gentoo Host .. * Step #3: Is the end reached ?! No, bcz qemu-omap3 is not full. So, go to step #4. * Step #4: Use Meego >> Download Ubuntu 10.10 >> Install it, and * Step #5: Compile FreeBSD kernel, Create root file system, mkimage, Emulate using Meego. Open tasks: 1. Device Drivers for OMAP3 Processors. __________________________________________________________________ BSDCan URL: http://www.bsdcan.org/2011/ Contact: Dan Langille Our list of talks has been settled, and the schedule is pretty much finalized. There is still time to get into the Works In Progress session. Best to book your on-campus accommodation now. Or stay at one of the nearby hotels. Open tasks: 1. Show up. Enjoy. Profit. __________________________________________________________________ DIstributed Firewall and Flow-shaper Using Statistical Evidence (DIFFUSE) URL: http://caia.swin.edu.au/urp/diffuse/ URL: http://caia.swin.edu.au/urp/diffuse/downloads.html Contact: Sebastian Zander Contact: Grenville Armitage DIFFUSE is a system enabling FreeBSD's IPFW firewall subsystem to classify IP traffic based on statistical traffic properties. With DIFFUSE, IPFW computes statistics (such as packet lengths or inter-packet time intervals) for observed flows, and uses ML (machine learning) to classify flows into classes. In addition to traditional packet inspection rules, IPFW rules may now also be expressed in terms of traffic statistics or classes identified by ML classification. This can be helpful when direct packet inspection is problematic (perhaps for administrative reasons, or because port numbers do not reliably identify applications). DIFFUSE also enables one instance of IPFW to send flow information and classes to other IPFW instances, which then can act on such traffic (e.g. prioritise, accept, deny, etc.) according to its class. This allows for distributed architectures, where classification at one location in your network is used to control fire-walling or rate-shaping actions at other locations. DIFFUSE is a set of patches for FreeBSD-CURRENT. It can be downloaded from the project's web site. The web site also contains a more comprehensive introduction, including application examples, links to related work and documentation. In February 2011 we released DIFFUSE v0.2.2. This release contains a number of bug fixes and new features. Most notably since version 0.2 there is a tool to build classifier models, and there is a feature module and classifier model to classify Skype traffic. We hope to release DIFFUSE v0.3 soon. Keep an eye on the freebsd-ipfw and freebsd-net mailing lists for project-related announcements. __________________________________________________________________ Extfs Status Report URL: http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2010/extfs/src/sy s/fs/&c=rFV@//depot/projects/soc2010/extfs/src/sys/fs/ext2fs/?ac=83 URL: http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2010/ext4fs/src/s ys/fs/&c=cc4@//depot/projects/soc2010/ext4fs/src/sys/fs/ext4fs/?ac=83 Contact: Zheng Liu I have implemented a reallocblks in ext2fs, like in ffs, and submitted a patch file to mailing list. Next I will try to implement htree directory index in ext2fs. __________________________________________________________________ Five New TCP Congestion Control Algorithms for FreeBSD URL: http://caia.swin.edu.au/freebsd/5cc/ URL: http://caia.swin.edu.au/urp/newtcp/ URL: http://www.FreeBSDFoundation.org/projects.shtml URL: http://FreeBSDfoundation.blogspot.com/2011/03/summary-of-five-new-tcp-c ongestion.html URL: http://people.FreeBSD.org/~lstewart/patches/5cc/ Contact: David Hayes Contact: Lawrence Stewart Contact: Grenville Armitage Contact: Rui Paulo Contact: Bjoern Zeeb The project is now complete, with the following code available in the svn head branch: * Modular congestion control framework. * Khelp (Kernel Helper) and Hhook (Helper Hook) frameworks. * Basic Khelp/Hhook integration with the TCP stack. * Enhanced Round Trip Time (ERTT) Khelp module. * Modularised implementations of NewReno, CUBIC, H-TCP, Vegas, Hamilton-Delay and CAIA-Hamilton-Delay congestion control algorithms. In addition to the code, a large set of documentation was committed (see the following man pages: cc(4), cc_newreno(4), cc_cubic(4), cc_htcp(4), cc_vegas(4), cc_hd(4), cc_chd(4), h_ertt(4), cc(9), khelp(9), hhook(9)) and a technical report was released which evaluates the computational overhead associated with TCP before and after the project's changes. A candidate patch to MFC the modular congestion control framework to the 8-STABLE branch is ready for testing here. If you try the patch, please send a note detailing your experience (positive or negative) to Lawrence Stewart. Thanks go to the FreeBSD Foundation for funding this work, to the project's technical reviewers for providing detailed feedback, and to all FreeBSD users who have provided testing feedback thus far. Open tasks: 1. Test 8-STABLE MFC candidate patch and do the merge in time for 8.3-RELEASE. __________________________________________________________________ FreeBSD as Home Theater PC URL: http://wiki.FreeBSD.org/HTPC Contact: Bernhard Froehlich Contact: Juergen Lock FreeBSD could be a much better platform for a Home Theater PC than it currently is. We are focusing on improving support for media center applications by extending the major ports (MythTV, VDR, XBMC) and creating some documentation to guide interested people. In the last months we continued to work on HTPC relevant ports, improved lirc and multimedia/webcamd remote control support. The last missing major HTPC application VDR (Video Disk Recorder) has finally been committed to the portstree as multimedia/vdr including 17 vdr plugin ports. Open tasks: 1. Improve remote control support in webcamd and with lirc. 2. Port more Media Center applications (Enna, me-tv, ...) 3. Create a small guide on how to build a great FreeBSD Home Theater PC. __________________________________________________________________ FreeBSD Bugbusting Team URL: http://www.FreeBSD.org/support.html#gnats URL: http://wiki.FreeBSD.org/BugBusting URL: http://people.FreeBSD.org/~linimon/studies/prs/ Contact: Gavin Atkinson Contact: Mark Linimon Contact: Remko Lodder Contact: Volker Werth The bugmeister team is happy to welcome Eitan Adler (eadler@) as the newest GNATS-only contributor. Eitan has been helping triage new bugs as they come in, as well as making good progress on many of the older bugs, closing duplicates and obsolete bugs and contacting submitters for extra information where necessary. For the first time in a long time we managed to get below 6000 open PRs, in no small part due to Eitan's efforts. Welcome aboard! PRs continue to be classified as they arrive, by adding 'tags' to the subject lines corresponding to the kernel subsystem involved, or man page references for userland PRs. Reports are generated from these nightly, grouping related PRs into one place, sorted by tag or man page. This allows an interested party working in one area or on one subsystem to easily find related bugs and issues in the same area, which has proven quite effective in getting some of the older bug reports closed. These reports can all be found by following the third link above. We continue to look for ideas for other reports that may help improve the PR closure rate. If you have any suggestions for reports which would contribute positively to the way you work, please email bugmeister@ and we shall try to produce such a report. Our clearance rate of PRs, especially in kern and bin, seems to be improving. The number of non-ports PRs has stayed almost constant since the last status report. As always, anybody interested in helping out with the PR queue is welcome to join us in #freebsd-bugbusters on EFnet. We are always looking for additional help, whether your interests lie in triaging incoming PRs, generating patches to resolve existing problems, or simply helping with the database housekeeping (identifying duplicate PRs, ones that have already been resolved, etc). This is a great way of getting more involved with FreeBSD! Open tasks: 1. Try to find ways to get more committers helping us with closing PRs that the team has already analyzed. __________________________________________________________________ FreeBSD Chromium URL: http://trillian.chruetertee.ch/chromium URL: http://lists.FreeBSD.org/mailman/listinfo/freebsd-chromium URL: http://www.chromium.org/Home Contact: FreeBSD Chromium Team Thanks to a great collaborative effort from the FreeBSD community, the OpenBSD community, and the Chromium developers, Chromium has been updated in the Ports tree. In the spirit of release early and release often, updates to Chromium happen frequently. The contributors of the FreeBSD Chromium team have demonstrated great agility in keeping pace with updates in the development repository hosted at http://trillian.chruetertee.ch/chromium. Open tasks: 1. A task that lies ahead is working with the Chromium developers at integrating the FreeBSD patches into the codebase. Volunteers are welcome. __________________________________________________________________ FreeBSD Haskell Ports URL: http://wiki.FreeBSD.org/Haskell URL: https://github.com/freebsd-haskell/freebsd-haskell URL: http://haskell.org/mailman/listinfo/freebsd-haskell/ Contact: Gábor János PÁLI Contact: Ashish SHUKLA Contact: Giuseppe Pilichi We are proud to announce that the FreeBSD Haskell team has updated GHC to 7.0.3, and all other existing Haskell ports to the latest stable versions, as well as added new ports. The total number of Haskell ports in the FreeBSD repository is now more than 200. These ports are still waiting to be committed. At the moment, they are available from FreeBSD Haskell ports repository. Any users who would like to get early access to them, please refer to the FreeBSD Haskell ports Call For Testing. Open tasks: 1. Create a metaport for Haskell Platform. 2. Create a port for Happstack. 3. Create a port for gitit. __________________________________________________________________ FreeBSD NYI Admins Status Report Contact: NYI Admins Team The FreeBSD.org site at New York Internet is progressing, though more slowly than we had hoped. Due to problems with the old power controllers and serial console servers, new equipment has been bought by the FreeBSD Foundation. Installing the new equipment required re-racking all the existing servers which was done by the local FreeBSD team (Steven Kreuzer and John Baldwin). For basic infrastructure at the site (such as DHCP, DNS, console etc.) the FreeBSD Foundation bought some new servers which are in the process of being configured. The FreeBSD Ports team are currently using 9 of the NYI servers for package building. Open tasks: 1. We are looking for a storage system (15TB+) for keeping replicas of all the main FreeBSD.org systems, a full ftp-archive mirror, site local files etc. __________________________________________________________________ FreeBSD/arm on Marvell Raid-on-Chip Contact: Grzegorz Bernacki Contact: Rafal Jaworowski Marvell 88RC8180 is an integrated RAID-on-Chip controller, based on the Feroceon 88FR331 CPU core (ARMv5TE). The 88RC9580 is a next generation version, based on the Sheeva 88SV581 CPU core (ARMv6) of this system-on-chip devices family. Current FreeBSD suppport for 88RC8180 and 88RC9580 includes: * Booting via U-Boot bootloader * L1, L2 cache * Serial console support (UART) * Interrupt controller * Integrated timers * PCI Express (root complex and endpoint modes) * Doorbells and messages * Ethernet controller Open tasks: 1. Complete, clean up, merge with HEAD. __________________________________________________________________ FreeBSD/EC2 URL: http://www.daemonology.net/freebsd-on-ec2/ Contact: Colin Percival FreeBSD is now able to run on t1.micro and cc1.4xlarge instances in the Amazon EC2 cloud. FreeBSD 8.2-RELEASE is stable subject to the limitations of the instance type (e.g., running ZFS on a micro instance with only 600 MB of RAM doesn't work very well), but FreeBSD 9.0 has significant stability issues. A list of available FreeBSD AMIs (EC2 machine images) appears on the FreeBSD/EC2 status page. Open tasks: 1. Bring FreeBSD to a wider range of EC2 instance types. 2. Completely rework the locking in head/sys/i386/xen/pmap.c to eliminate races and make 9.0-CURRENT stable under paravirtualization. 3. Track down several possibly-related problems with scheduling and timekeeping. 4. Fix other issues shown on the FreeBSD/EC2 status page. __________________________________________________________________ FreeBSD/powerpc on Freescale QorIQ Contact: Michal Dubiel Contact: Rafal Jaworowski QorIQ is a brand of Power Architecture-based communications microprocessors from Freescale. It is an evolutionary step from the PowerQUICC platform (MPC85xx) and is built around one or more Power Architecture e500/e500mc cores. This work is bringing up FreeBSD on these system-on-chip devices along with device drivers for integrated peripherials. Current FreeBSD QorIQ support includes: * QorIQ P2020 support * Booting via U-Boot bootloader * L1, L2 cache * Serial console (UART) * Interrupt controller * Ethernet (TSEC, SGMII mode) * I2C * EHCI controller (no Transaction Translation Unit) * Security Engine (SEC) 3.1 * PCI Express controller (host mode) * Enhanced SDHC (no MMC support) * Dual-core (SMP) support __________________________________________________________________ GEOM-based ataraid(4) Replacement -- geom_raid. Contact: Alexander Motin Contact: M. Warner Losh A new RAID GEOM class (geom_raid) was added to FreeBSD 9-CURRENT, to replace ataraid(4) in supporting various BIOS-based software RAIDs. Unlike ataraid(4) this implementation does not depend on legacy ata(4) subsystem and can be used with any disk drivers, including new CAM-based ones (ahci(4), siis(4), mvs(4) and ata(4) with `options ATA_CAM`). To make code more readable and extensible, this implementation follows modular design, including a core part and two sets of modules, implementing support for different metadata formats and RAID levels. Support for such popular metadata formats is now implemented: Intel, JMicron, NVIDIA, Promise (also used by AMD/ATI) and SiliconImage. Such RAID levels are now supported: RAID0, RAID1, RAID1E, RAID10, SINGLE, CONCAT. For any all of these RAID levels and metadata formats this class supports full cycle of volume operations: reading, writing, creation, deletion, disk removal and insertion, rebuilding, dirty shutdown detection and resynchronization, bad sector recovery, faulty disks tracking, hot-spare disks. For Intel and Promise formats there is support for multiple volumes per disk set. See the graid(8) manual page for additional details. Sponsored by: Cisco Systems, Inc. and iXsystems, Inc. Open tasks: 1. Implement metadata modules for other formats (DDF, Highpoint, VIA, ...). 2. Implement transformation modules for other RAID levels (RAID5, ...). __________________________________________________________________ Google Summer of Code 2011 URL: http://www.google-melange.com/gsoc/org/google/gsoc2011/freebsd URL: http://wiki.freebsd.org/SummerOfCode2011 Contact: Brooks Davis Contact: Robert Watson FreeBSD is proud to be participating in our seventh year of Google Summer of Code. On Monday, April 25th we accepted 17 proposals from an overall excellent field. A full list of accepted proposals can be found on the GSoC website. We look forward to working with these students over the summer. As we did last year we plan to ask students to submit weekly status reports to the soc-status mailing list. Those wishing to keep up with the work in progress and offer review may wish to subscribe. __________________________________________________________________ HAST (Highly Available Storage) Contact: Pawel Jakub Dawidek Contact: Mikolaj Golub HAST development is progressing nicely. Mikolaj Golub who contributes to HAST is now a FreeBSD src committer. Some changes worth noting since the last report: * Compression of the data being sent over the network. This can speed up especially synchronization process. * Optional checksuming for the data being send over the network. * Capsicum sandboxing for secondary node and hastctl. * Chroot+setuid+setgid sandboxing for primary node. * Allow administrators to specify source IP address for connections. * When changing role wait for a while for the other node to switch from primary to secondary to avoid split-brain. * Many bug fixes. __________________________________________________________________ Journaled Soft Updates Contact: Jeff Roberson Contact: Kirk McKusick All known problems with journaled soft updates have been fixed in head. If you have any problems while running with journaled soft updates, please report them to us. We have addressed several performance issues that have been brought to our attention. If you have any performance problems while running with journaled soft updates, please report them to us. We have improved the recovery of resources when running with soft updates on small (root) filesystems. We anticipate being able to use soft updates for root filesystems in the 9.0 system. We expect to have journaled soft updates default to enabled in the 9.0 system. We encourage users of -CURRENT to enable journaled soft updates to help shake out any remaining performance problems and bugs. __________________________________________________________________ KDE-FreeBSD URL: http://FreeBSD.kde.org Contact: KDE FreeBSD The KDE on FreeBSD team have continued to improve the experience of KDE and Qt under FreeBSD. The latest round of improvements include: * Improved shared resources (i.e. pixmaps for KDE) * Improved file monitoring (using kevent) * Improved KSysGuard support (new and refined sensors) The team have also made many releases and upstreamed many fixes and patches. The latest round of releases include: * Qt: 4.7.2 * KDE: 4.5.5; 4.6.1; 4.6.2 * KOffice: 2.3.3 * KDevelop: 4.2.0; 4.2.2 (KDevPlatform: 1.2.0; 1.2.2) * many smaller ports The team needs more testers and porters so please visit us at kde-freebsd@kde.org Open tasks: 1. Continue improvements of KSysGuard. 2. General maintenance. 3. General testing. 4. Porting. __________________________________________________________________ Linux Compatibility Layer - DVB and V4L2 Support URL: http://people.FreeBSD.org/~nox/dvb/ Contact: Juergen Lock Following (separate) discussions on the mailing lists I have made patches to add DVB and V4L2 ioctl translation support to the Linux compatibility layer, allowing Linux apps like SageTV, Skype, and Flash to use DVB/ATSC tuners and webcams that previously only worked for native FreeBSD apps. (Most of this hardware uses Linux drivers via the multimedia/webcamd port.) Open tasks: 1. Handle the remaining ioctls that (I think) are not used by DVB tuners/cameras supported by webcamd (it only supports USB devices, the unhandled ioctls mostly have to do with video overlays and hardware MPEG2 decoding on analog or DVB tuners, features that AFAIK don't exist on USB hardware.) 2. Make the DVB support a port because there were concerns putting it in base due to the LGPL in one of the header files even though I already separated out the code into an extra kld. (linux_dvbwrapper.ko) 3. Get the patches polished and committed. :) (Until they are you can check my DVB page and the freebsd-emulation@ mailing list for updates.) __________________________________________________________________ Linux Emulation Ports URL: http://www.leidinger.net/blog/2011/02/25/howto-creating-your-own-update d-linux-rpm-for-the-freebsd-linuxulator/ Contact: Alexander Leidinger Contact: Emulation Mailinglist Old linux_base ports (all which are not used by default in some release) where marked as deprecated with a short expiration period. The reason is that all those ports are long past their end of life and do not receive security updates anymore. Unfortunately this is also true for the linux_base ports which are still used by default in the releases, but no replacement is available ATM (see open tasks). The linux-f10-pango port was updated to a more recent version whoch does not have a security problem by generating a linux-RPM in a VM with "FreeBSD" as the vendor (see the links section for a HOWTO). Open tasks: 1. Decide which RPM based linux distribution+version to track next for the linux_base ports, create ports for it and test for compatibility with our kernel code. __________________________________________________________________ MIPS/Octeon Support and bootinfo Contact: Andrew Duane Working on improving support for Octeon processors and integrating with other MIPS processor families. Currently working on support for the standard MIPS bootinfo structure as a boot API (to supplement/replace the Caviums-specific structure). Other Octeon improvements including cleanups to CF and USB drivers to come. __________________________________________________________________ New FreeBSD Handbook Section Covering HAST URL: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/disks-hast.ht ml Contact: Daniel Gerzo A new FreeBSD Handbook section covering the Highly Available STorage, or HAST developed by Pawel Jakub Dawidek has been recently added. In this section, you will learn what HAST is, how it works, which features it provides and how to set it up. It also includes a working example on how it can be used together with devd(8) and CARP. Enjoy your reading. __________________________________________________________________ New FreeBSD Installer URL: http://wiki.FreeBSD.org/BSDInstall URL: http://wiki.FreeBSD.org/PCBSDInstallMerge Contact: Nathan Whitehorn On March 14th, sysinstall was replaced on the 9.0 snapshot media by a new, modular installer called BSDInstall. This adds support for a wide variety of new features while simplifying the installation process. Testing before the 9.0 release will be very much appreciated -- CD and memory stick images for a variety of platforms are linked from the BSDInstall wiki page. Interesting features: * Install CD media are always live CDs * Installations spanning multiple disks * Wireless setup * GPT disk formatting * Virtualization friendly: can install from a live system onto disk images * Easily hackable and more modular than sysinstall * Greater flexibility: shells available throughout the installation Work is presently ongoing to integrate this installer with the backend provided by pc-sysinstall (second wiki link). Open tasks: 1. ZFS installation support. 2. IA64 disk setup. __________________________________________________________________ OpenAFS Port URL: http://openafs.org URL: http://web.mit.edu/freebsd/openafs/openafs.shar Contact: Benjamin Kaduk Contact: Derrick Brashear AFS is a distributed network filesystem that originated from the Andrew Project at Carnegie-Mellon University. The OpenAFS client implementation has not been particularly useful on FreeBSD since the FreeBSD 4.X releases. Work covered in previous reports brought the OpenAFS client to a useful form on 9.0-CURRENT, though with some rough edges. Since our last report, we have fixed several bugs that were impacting usability, and we expect the upcoming 1.6.0 release to be usable for regular client workloads (though not heavy load). Accordingly, we have submitted packaging for inclusion in the Ports Collection (PR ports/152467). There are several known outstanding issues that are being worked on, but detailed bug reports are welcome at port-freebsd@openafs.org. Open tasks: 1. Update VFS locking to allow the use of disk-based client caches as well as memory-based caches. 2. Track down races and deadlocks that may appear under load. 3. Integrate with the bsd.kmod.mk kernel-module build infrastructure. 4. Eliminate a moderate memory leak from the kernel module. 5. PAG (Process Authentication Group) support is not functional. __________________________________________________________________ pfSense URL: www.pfsense.org Contact: Scott Ullrich Contact: Chris Buechler Contact: Ermal Luci Work on 2.0 is rapidly coming to an end. We released RC1 around Feb 25 2011 and so far it seems to be rather stable. 2.0 is our first major release in 2 years and almost all limitations of the previous version has been overcome. Open tasks: 1. Finish testing RC1 and certify for release. __________________________________________________________________ Portmaster URL: http://dougbarton.us/portmaster-proposal.html Contact: Doug Barton The latest version of portmaster contains numerous improvements aimed at large-scale enterprise users. Particularly, support for the --index-only/--packages-only code has been significantly improved. Some of the highlights include: * New --update-if-newer option which takes a list of ports and/or a glob pattern on the command line and only updates those that are out of date. This feature is very useful for ensuring that the packages needed for updating a system are all available and up to date on the package building system. * The portmaster.rc file can now be stored in the same directory as the script itself, which aids in shared access to the script (for example over an NFS mount) * More features now work (or work better) with --index-only, including --check-depends Open tasks: 1. I have received some support for items E.2 and E.3 on the web page listed above so I will be putting some effort into those areas in the coming months. I also have in mind to split out the "fetch" code to be its own script, in part to support goal E.2, and to allow for more efficient parallelization when downloading multiple distfiles (especially for multiple ports that download the same distfile). This will also allow me to set a global limit for the number of parallel fetches which should aid users on slow links. __________________________________________________________________ Ports Collection URL: http://www.FreeBSD.org/ports/ URL: http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/ URL: http://portsmon.FreeBSD.org/index.html URL: http://www.FreeBSD.org/portmgr/index.html URL: http://blogs.FreeBSDish.org/portmgr/ URL: http://www.twitter.com/freebsd_portmgr/ URL: http://www.facebook.com/group.php?gid=135441496471197 URL: http://tinderbox.marcuscom.com/ Contact: Thomas Abthorpe Contact: Port Management Team The ports tree slowly moves up closer to 23,000. The PR count still remains at about 1000. In Q1 we added 2 new committers, and took in 4 commit bits for safe keeping. After a year of serving as the team secretary, Thomas Abthorpe's membership was upgraded to full voting status. The Ports Management team have been running -exp runs on an ongoing basis, verifying how base system updates may affect the ports tree, as well as providing QA runs for major ports updates. Of note, -exp runs were done for: * erwin did a clang -exp run, and sent results to interested parties * kde@ requested an -exp run for KDE 4.6.1 and Qt 4.7.2 * linimon -exp for update of default zope version to 3.2 * miwi performed the following -exp runs, make fetch-original, xorg, cmake, pear, kde4 / py-qt / sip, and python2.7 * mm requested an -exp run to test the last GPLv2 version of gcc 4.2.2 * pav completed open-motif and mono -exp runs for respective submitters * ports/127214, -exp run to make copy/paste of portaudit user friendly * ports/144482, -exp run to fix package depends * ports/152102, -exp run to make dirrmtry more friendly * ports/152268, -exp run to update binutils * ports/153539, -exp run to allow checking STRIP when WITH_DEBUG is defined * ports/153547, -exp run to remove NO_SIZE * ports/153625, -exp run to pass CPPFLAGS to MAKE/CONFIGURE_ENV * ports/153634, -exp run to remove redundant PKGNAMEPREFIX for localised ports * ports/154121, -exp run to use --title for new libdialog * ports/154122, -exp run to update libtool to 2.4 * ports/154186, -exp to allow using linux 2.4 emulation on FreeBSD 8+ * ports/154390, -exp run to make fetching output copy/paste friendly * ports/154653, -exp run to remove superfluous slash * ports/154799, -exp run to update glib + gtk * ports/154994, -exp run for MASTER_SITE_PERL_CPAN enhancements * ports/155502, -exp run to remove sanity check for X_WINDOW_SYSTEM * ports/155504, -exp run to remove USE_XPM from b.p.m. * ports/155505, -exp run to update GNU m4 Open tasks: 1. Looking for help fixing ports broken on CURRENT. 2. Looking for help with Tier-2 architectures. 3. Most ports PRs are assigned, we now need to focus on testing, committing and closing. __________________________________________________________________ RCTL, aka Resource Containers Contact: Edward Tomasz Napierala Most of the code has already been merged into CURRENT. There are two remaining problems I would like to solve before 9.0-RELEASE - see below - but otherwise, the code is stable; please test and report any problems. You will need to rebuild the kernel with "options RACCT" and "options RCTL". The rctl(8) manual page should be a good introduction on how to use it. This project was sponsored by The FreeBSD Foundation. Open tasks: 1. Reimplementing %CPU accounting and CPU throttling. 2. Making jail rules persistent - right now, one cannot add jail rule before that jail is created, which makes it impossible to put them into /etc/rctl.conf; also, rules disappear when jail gets destroyed. __________________________________________________________________ The FreeBSD Foundation Status Report URL: http://www.FreeBSDfoundation.org Contact: Deb Goodkin We created our 2011 budget. Some of our plans for 2011 include spending $125,000 on project development and $75,000 on equipment to build up FreeBSD facilities in three locations. We were proud to be a sponsor for AsiaBSDCon 2011 in Tokyo. We also committed to sponsoring BSDCan 2011 in May, and EuroBSDCon 2011 in October. The Foundation was also represented at SCALE in Los Angeles, Indiana LinuxFest in Indianapolis, and Flourish in Chicago. Completed Foundation-funded projects: Five New TCP Congestion Control Algorithms project by Swinburne University and Resource Containers project by Edward Napierala. In February we visited companies in the Bay Area that use FreeBSD. Our goal was to promote FreeBSD, better understand their interests and needs, and help facilitate stronger relationships between these companies and the Project. The presentations we gave included the benefits of FreeBSD, Project road-map, potential areas of collaboration, case studies, and how the Foundation supports the project. By visiting in person we were able to show our commitment to the Project and respond directly to questions and concerns they may have had. We were pleased with the positive responses we received and plan on visiting more companies in the future. We are funding two new projects. The first project is Implementing Support of GEM, KMS, and DRI for Intel Drivers by Konstantin Belousov. The second is Improving the Maturity of IPv6 Support of FreeBSD and PC-BSD by Bjoern Zeeb. We continued our work on infrastructure projects to beef up hardware for package-building, network-testing, etc. This includes purchasing equipment as well as managing equipment donations. Stop by and visit with us at BSDCan (May 13-14) and SouthEast LinuxFest (June 10-12). The work above as well as many other tasks we do for the project, couldn't be done without donations. Please help us by making a donation or asking your company to make a donation. We would be happy to send marketing literature to you or your company. Find out how to make a donation at http://www.FreeBSDfoundation.org/donate/. __________________________________________________________________ The FreeBSD German Documentation Project Status Report URL: http://doc.bsdgroup.de Contact: Johann Kois Contact: Benedict Reuschling Benedict Reuschling contributed the translation of the new handbook section about HAST, while Benjamin Lukas was working on the first translation of the firewall chapter of the handbook. The committers to the German Documentation Project were busy with keeping the existing German documentation up-to-date. The website translations were also kept in sync with the ones on FreeBSD.org. We tried to re-activate committers who did not contribute for some time but most of them are currently unable to free up enough time. We hope to gain fresh contributor blood as we are getting occasional reports about bugs and grammar in the german translation. Open tasks: 1. Submit grammar, spelling or other errors you find in the german documents and the website. 2. Translate more articles and other open handbook sections. __________________________________________________________________ The FreeBSD Japanese Documentation Project URL: http://www.FreeBSD.org/ja/ URL: http://www.jp.FreeBSD.org/doc-jp/ Contact: Hiroki Sato Contact: Ryusuke Suzuki The www/ja and doc/ja_JP.eucJP/books/handbook have constantly been updated. During this period, translation of the handbook installation page was finished. The following chapters are now synchronized with the English version: * introduction * install * ports * x11 * desktop * multimedia * mirrors * pgpkeys Merging translation results from the www tree on a separate repository for the translation work into the main tree was also finished. Since outdated and/or non-translated documents also remain in both doc/ja_JP.eucJP and www, further translation work is still needed. Some progress has been made in the Porter's Handbook as well in this period. __________________________________________________________________ Webcam and DVB Compatibility List URL: http://wiki.FreeBSD.org/WebcamCompat Contact: Matthias Apitz Webcam and DVB Compatibility List This is the FreeBSD Webcam, DVB, and Remote Control Compatibility List. The main goal of this page is to give an exact answer about which application works with a given cam or DVB. Combinations of the hardware and software mentioned in this table are known to work. Please add more lines to the table or ask me to do so by just sending a mail with your Cam/DVB information. Please note: you should only add information you have seen working and not you may think of or imagine that they could work. The contact information (name and/or email addr) is optional. Open tasks: 1. Move this to a real database in where FreeBSD enduser could self insert their gadgets, like the FreeBSD Laptop Compat List. __________________________________________________________________ www/apache22 Default URL: http://people.FreeBSD.org/~pgollucci/FreeBSD/prs/maintainers.html#apach e URL: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/147009 URL: http://wiki.FreeBSD.org/Apache URL: http://lists.FreeBSD.org/pipermail/freebsd-apache/2011-March/002174.htm l Contact: Philip Gollucci Contact: Olli Hauer Contact: Apache Apache 95% done, pending final -exp run, and pulling the switch. HEADS-UP announcement already sent to relevant lists. This will be for 8.3/9.0. __________________________________________________________________ ZFSv28 available in FreeBSD 9-CURRENT Contact: Pawel Jakub Dawidek Contact: Martin Matuska ZFS v28 is now in HEAD! Test, test, test and test. Pretty please. New features include: * Data deduplication. * Triple parity RAIDZ (RAIDZ3). * zfs diff. * zpool split. * Snapshot holds. * zpool import -F. Allows to rewind corrupted pool to earlier transaction group. * Possibility to import pool in read-only mode. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 15:01:03 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24473106566C for ; Wed, 27 Apr 2011 15:01:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id EAF748FC19 for ; Wed, 27 Apr 2011 15:01:02 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 8D2F346B51; Wed, 27 Apr 2011 11:01:02 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 0AA248A027; Wed, 27 Apr 2011 11:01:02 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 27 Apr 2011 10:19:31 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DB695DB.1080505@chillt.de> <20110426124403.GQ48734@deviant.kiev.zoral.com.ua> <4DB76085.4000402@chillt.de> In-Reply-To: <4DB76085.4000402@chillt.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104271019.31844.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 27 Apr 2011 11:01:02 -0400 (EDT) Cc: Kostik Belousov , Bartosz Fabianowski , Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:01:03 -0000 On Tuesday, April 26, 2011 8:17:09 pm Bartosz Fabianowski wrote: > > If you needs per-file private data for cdev, you would be better served > > by cdevpriv(9) KPI. Cloning is too hard to use correctly for such task. > > Thanks, I just got that working. To help those going down a similar path > in the future, I would like to note quickly that the following must be > added to the cdevsw structure to ensure proper clean-up: > > .d_flags = D_TRACKCLOSE > > I just spent hours debugging panics until I realized only the last > close() was triggering a call to my .d_close method. Err, if you use cdevpriv you shouldn't even have a d_close method. All your d_close logic should be in the cdevpriv destructor, and the kernel will call your destructor when all references to an open file descriptor go away (i.e. it is closed). -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 15:01:04 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57D951065675 for ; Wed, 27 Apr 2011 15:01:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2B8BE8FC14 for ; Wed, 27 Apr 2011 15:01:04 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id C2F5946B42; Wed, 27 Apr 2011 11:01:03 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E06348A02A; Wed, 27 Apr 2011 11:01:02 -0400 (EDT) From: John Baldwin To: Vladimir Laskov Date: Wed, 27 Apr 2011 10:21:43 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4D553027.5040606@gmail.com> <201104261143.00644.jhb@freebsd.org> <4DB7C893.9050903@gmail.com> In-Reply-To: <4DB7C893.9050903@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201104271021.43315.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 27 Apr 2011 11:01:03 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, Sergey Kandaurov Subject: Re: problem with build mcelog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:01:04 -0000 On Wednesday, April 27, 2011 3:41:07 am Vladimir Laskov wrote: > On 04/26/2011 07:43 PM, John Baldwin wrote: > > --- //depot/projects/mcelog/mcelog.c 2010-08-25 11:41:19.000000000 0000 > > +++ /home/jhb/work/p4/mcelog/mcelog.c 2010-08-25 11:41:19.000000000 0000 > > @@ -29,6 +29,10 @@ > > #include > > #include > > #include > > +#ifdef __i386__ > > +/* Conflicts with 'enum cputype' in. */ > > +#undef CPU_P4 > > +#endif > > #include > > #include > > #include > > > thanks, it work > > my questions: > > - how to work mcelog without mcelogdevice ? > - Is it possible to use mcelog in daemon mode in FreeBSD? mcelog uses the hw.mca sysctls, not a device in /dev in FreeBSD. The daemon mode is not currently supported. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 15:22:46 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A9B4106564A for ; Wed, 27 Apr 2011 15:22:46 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 03E9B8FC0C for ; Wed, 27 Apr 2011 15:22:45 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 77FF41886005; Wed, 27 Apr 2011 17:22:44 +0200 (CEST) Message-ID: <4DB818A3.1020104@chillt.de> Date: Wed, 27 Apr 2011 15:22:43 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: John Baldwin References: <4DB695DB.1080505@chillt.de> <20110426124403.GQ48734@deviant.kiev.zoral.com.ua> <4DB76085.4000402@chillt.de> <201104271019.31844.jhb@freebsd.org> In-Reply-To: <201104271019.31844.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:22:46 -0000 > Err, if you use cdevpriv you shouldn't even have a d_close method. All your > d_close logic should be in the cdevpriv destructor I see. There is no documentation for any of this, so I just implemented it in the way I *thought* it should work: .d_close = drv_close, int drv_close(...) { devfs_clear_cdevpriv(); } static void cdevpriv_dtr(void *data) { free(data, M_USBDEV); } If I understand you correctly, I can leave out the drv_close() method. When close() is called, devfs_clear_cdevpriv() will be executed implcitly for me and my dstructor will run - right? - Bartosz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 15:30:22 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E280106566C; Wed, 27 Apr 2011 15:30:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 7C6A38FC13; Wed, 27 Apr 2011 15:30:20 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p3RFUCxJ093989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Apr 2011 18:30:12 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p3RFUCYJ085597; Wed, 27 Apr 2011 18:30:12 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p3RFUCt3085596; Wed, 27 Apr 2011 18:30:12 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 27 Apr 2011 18:30:12 +0300 From: Kostik Belousov To: Bartosz Fabianowski Message-ID: <20110427153012.GX48734@deviant.kiev.zoral.com.ua> References: <4DB695DB.1080505@chillt.de> <20110426124403.GQ48734@deviant.kiev.zoral.com.ua> <4DB76085.4000402@chillt.de> <201104271019.31844.jhb@freebsd.org> <4DB818A3.1020104@chillt.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ElEgulhWJDonIdTi" Content-Disposition: inline In-Reply-To: <4DB818A3.1020104@chillt.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_05, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:30:22 -0000 --ElEgulhWJDonIdTi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 27, 2011 at 03:22:43PM +0200, Bartosz Fabianowski wrote: > >Err, if you use cdevpriv you shouldn't even have a d_close method. All= =20 > >your > >d_close logic should be in the cdevpriv destructor >=20 > I see. There is no documentation for any of this, so I just implemented= =20 > it in the way I *thought* it should work: >=20 > .d_close =3D drv_close, >=20 > int drv_close(...) { > devfs_clear_cdevpriv(); > } >=20 > static void cdevpriv_dtr(void *data) { > free(data, M_USBDEV); > } >=20 > If I understand you correctly, I can leave out the drv_close() method.=20 > When close() is called, devfs_clear_cdevpriv() will be executed=20 > implcitly for me and my dstructor will run - right? You are mixing the global 'last close', that is performed when last file opened over the device node is closed, and the last filedescriptor close which causes the file to be decomissioned. The global kind of last close is communicated to cdev by calling cdevsw close method. It is known to be not quite reliable, and esp. hard in relation to the forced unmounts of devfs mount points. The close of file (when no other file descriptors referencing the file are left) ends in cdevpriv destructor call. --ElEgulhWJDonIdTi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk24NoQACgkQC3+MBN1Mb4gJtgCgyPUGE00LSBdBF6y7FdXXGnhy nPYAoIgNV2gDCEBPDKvXm+JmJT3ux8sA =h1Oa -----END PGP SIGNATURE----- --ElEgulhWJDonIdTi-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 15:35:27 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95AD1106566C for ; Wed, 27 Apr 2011 15:35:27 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 57FAA8FC0A for ; Wed, 27 Apr 2011 15:35:27 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 1B34518860EE; Wed, 27 Apr 2011 17:35:26 +0200 (CEST) Message-ID: <4DB81B9D.1070306@chillt.de> Date: Wed, 27 Apr 2011 15:35:25 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Kostik Belousov References: <4DB695DB.1080505@chillt.de> <20110426124403.GQ48734@deviant.kiev.zoral.com.ua> <4DB76085.4000402@chillt.de> <201104271019.31844.jhb@freebsd.org> <4DB818A3.1020104@chillt.de> <20110427153012.GX48734@deviant.kiev.zoral.com.ua> In-Reply-To: <20110427153012.GX48734@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 15:35:27 -0000 > The global kind of last close is communicated to cdev by calling cdevsw > close method. It is known to be not quite reliable, and esp. hard in > relation to the forced unmounts of devfs mount points. > > The close of file (when no other file descriptors referencing the file are > left) ends in cdevpriv destructor call. Thanks. That confirms my understanding of the mechanism after John's clarification. I will move my code to the cdevpriv destructor and do away with the d_close method entirely. - Bartosz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 19:44:50 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2671A1065673 for ; Wed, 27 Apr 2011 19:44:50 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id EF9598FC18 for ; Wed, 27 Apr 2011 19:44:49 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 8E8B546B35; Wed, 27 Apr 2011 15:44:49 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 13A258A027; Wed, 27 Apr 2011 15:44:49 -0400 (EDT) From: John Baldwin To: Bartosz Fabianowski Date: Wed, 27 Apr 2011 13:34:07 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DB695DB.1080505@chillt.de> <201104271019.31844.jhb@freebsd.org> <4DB818A3.1020104@chillt.de> In-Reply-To: <4DB818A3.1020104@chillt.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201104271334.07170.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 27 Apr 2011 15:44:49 -0400 (EDT) Cc: Kostik Belousov , freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 19:44:50 -0000 On Wednesday, April 27, 2011 9:22:43 am Bartosz Fabianowski wrote: > > Err, if you use cdevpriv you shouldn't even have a d_close method. All your > > d_close logic should be in the cdevpriv destructor > > I see. There is no documentation for any of this, so I just implemented > it in the way I *thought* it should work: > > .d_close = drv_close, > > int drv_close(...) { > devfs_clear_cdevpriv(); > } > > static void cdevpriv_dtr(void *data) { > free(data, M_USBDEV); > } > > If I understand you correctly, I can leave out the drv_close() method. > When close() is called, devfs_clear_cdevpriv() will be executed > implcitly for me and my dstructor will run - right? Yes, if you only care about cleaning up per-fd data. If you have some sort of state that needs to get created on first open and then removed on last close, you may still want to use a d_close() method, but there are actually edge cases where that can still not be called. So, for that sort of data I would still depend on the cdevpriv destructor and use a reference count between open() and the destructor to know when to cleanup shared state. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 19:57:33 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5641A106564A; Wed, 27 Apr 2011 19:57:33 +0000 (UTC) (envelope-from rdivacky@vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [46.28.110.116]) by mx1.freebsd.org (Postfix) with ESMTP id 1F95D8FC16; Wed, 27 Apr 2011 19:57:32 +0000 (UTC) Received: by vlakno.cz (Postfix, from userid 1002) id 83E657F3ACC; Wed, 27 Apr 2011 21:39:46 +0200 (CEST) Date: Wed, 27 Apr 2011 21:39:46 +0200 From: Roman Divacky To: harti@freebsd.org Message-ID: <20110427193946.GA41659@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: hackers@freebsd.org Subject: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 19:57:33 -0000 hi harti! You seem to have messed with bsd make so I have a question for you :) When a job is about to be executed in JobStart() a pipe is created with its ends connected to job->inPipe/job->outPipe. When the job is actually created in JobExec() the ps.out is set to job->outPipe so that in JobDoOutput() we can read from that pipe and basically just parse the output for shell->noPrint and leaving it out from the output. This is meant (I think) for supressing the "filter" thing. Ie. that if we do some @command the restoration of setting of quiet mode is filtered out. In -B mode we do it differently, as we invoke one shell per command we don't have to insert quiet/verbose commands and thus avoid all the piping/parsing dance. So my question is - why don't we invoke one shell per command by default and avoid the piping/parsing? Is this because of performance? I think that the piping/parsing of the output can have worse impact than invoking a shell for every command. Especially given that most targets consists of just one command. Thank you for the answer! Roman From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 20:30:56 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD7D91065672; Wed, 27 Apr 2011 20:30:56 +0000 (UTC) (envelope-from chris.richardson.bsd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 1634B8FC0C; Wed, 27 Apr 2011 20:30:55 +0000 (UTC) Received: by wwc33 with SMTP id 33so2137296wwc.31 for ; Wed, 27 Apr 2011 13:30:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=54P7zxmqJZQm2QPDkt1MQbhUuOXHM2bHKL5WQNF/T7g=; b=hcq6hM7kBYGk+w4C+PsLTp7lhY+JWRIjn0KNJonC0OPz0O2jFVebssaFgXkeP4irIo AgI/brLJ2GZe9l5oxHqVDrjoBkbQSdUjCqKNACcV2qkRveFTohDPj7ruCVRjEQL31qcI dunW56o+wEq8q8DFf0vACA+wyjYPm/QcqXN4k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=BjUsT3b3/n0vSJg+dZ1oihdgHofLEZJ3VqtrZCtXTjCVUHYb38R0wjRZsc/cznrZWT 7APH7ebk7xCvtALhx6vygjrNWmTmzu6mKqOwBeGGpGuCcZYSA3GxtaPg6IAJ9SXR4DyU +KXNRDRr3HmhzZMJNhZb/2SIzUa6I8MSEvauM= MIME-Version: 1.0 Received: by 10.227.208.207 with SMTP id gd15mr2678180wbb.93.1303936254922; Wed, 27 Apr 2011 13:30:54 -0700 (PDT) Received: by 10.227.134.210 with HTTP; Wed, 27 Apr 2011 13:30:54 -0700 (PDT) Date: Wed, 27 Apr 2011 22:30:54 +0200 Message-ID: From: Chris Richardson To: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: OMAP3 Question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 20:30:56 -0000 Hi Community, I wanna emulate OMAP3 Processor. Is it approach I can use to emulate OMAP3 without the need to any hardware? Wishes From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 21:07:52 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51488106566B for ; Wed, 27 Apr 2011 21:07:52 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id D8D8D8FC0C for ; Wed, 27 Apr 2011 21:07:51 +0000 (UTC) Received: by ywf7 with SMTP id 7so1008560ywf.13 for ; Wed, 27 Apr 2011 14:07:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oVpy7SMDPiRKlfgrkDC21UihllJrcKMy4yshDX5JG+I=; b=OoU0MvQDMoA/FNkRju6je2ghAAP8bYuKXOM6FtttK4v/vnTGZjRuGYwfaLbTpO6JP3 oRuXYx2AvZmZPiAti+avQIkaGso7C5ejgs9GMuT6TN5O7E0pJeTxjK3d4GtNYi7us1Bz YyxZQreJM88L7K8G/Z13/v5Y7PBh+h3MdYK/A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=BCsEDvy+2yJWzKgbp7UWhqLaOS8JUWa8XnjGVBLdzDVtzC4KPhxE8BS3DlFDk6p7fw AeF+tJl1d/1PiyHauGYrmVY+GPoBNErzcvao1Aaa830fTQLU2rcyU/ZeqgO5WYpsMGNH X9fgrKJTrQXMh7NFccuJFHHw2VIFc1JPs1dkU= MIME-Version: 1.0 Received: by 10.91.32.6 with SMTP id k6mr2377197agj.123.1303938471069; Wed, 27 Apr 2011 14:07:51 -0700 (PDT) Received: by 10.90.70.18 with HTTP; Wed, 27 Apr 2011 14:07:51 -0700 (PDT) In-Reply-To: References: Date: Wed, 27 Apr 2011 14:07:51 -0700 Message-ID: From: Freddie Cash To: Chris Richardson Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, freebsd-arm@freebsd.org Subject: Re: OMAP3 Question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 21:07:52 -0000 On Wed, Apr 27, 2011 at 1:30 PM, Chris Richardson wrote: > =C2=A0 =C2=A0I wanna emulate OMAP3 Processor. Is it approach I can use to= emulate > OMAP3 without the need to any hardware? Qemu has some basic support for this: http://code.google.com/p/qemu-omap3/ No idea how good it is, or if it's even usuable. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 21:14:39 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 981E71065670; Wed, 27 Apr 2011 21:14:39 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 58C258FC19; Wed, 27 Apr 2011 21:14:39 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 5B3D2188603F; Wed, 27 Apr 2011 23:14:37 +0200 (CEST) Message-ID: <4DB8873C.5020608@chillt.de> Date: Wed, 27 Apr 2011 23:14:36 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: John Baldwin References: <4DB695DB.1080505@chillt.de> <201104271019.31844.jhb@freebsd.org> <4DB818A3.1020104@chillt.de> <201104271334.07170.jhb@freebsd.org> In-Reply-To: <201104271334.07170.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 21:14:39 -0000 > If you have some sort of state that needs to get created on first > open and then removed on last close [...] I would still depend on the > cdevpriv destructor and use a reference count between open() and the > destructor to know when to cleanup shared state. Yes, this is what I am doing. I am maintaining a list of all file descriptors open on the device. Once the length of that list reaches zero, I do global clean-up in the cdevpriv destructor. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 21:52:41 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 411D4106566B; Wed, 27 Apr 2011 21:52:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id A2C3F8FC0C; Wed, 27 Apr 2011 21:52:40 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p3RLqSHw025278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Apr 2011 00:52:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p3RLqSSS088234; Thu, 28 Apr 2011 00:52:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p3RLqScN088233; Thu, 28 Apr 2011 00:52:28 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 28 Apr 2011 00:52:28 +0300 From: Kostik Belousov To: Bartosz Fabianowski Message-ID: <20110427215228.GY48734@deviant.kiev.zoral.com.ua> References: <4DB695DB.1080505@chillt.de> <201104271019.31844.jhb@freebsd.org> <4DB818A3.1020104@chillt.de> <201104271334.07170.jhb@freebsd.org> <4DB8873C.5020608@chillt.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AMNVzrRY61gDOMe/" Content-Disposition: inline In-Reply-To: <4DB8873C.5020608@chillt.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 21:52:41 -0000 --AMNVzrRY61gDOMe/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 27, 2011 at 11:14:36PM +0200, Bartosz Fabianowski wrote: > >If you have some sort of state that needs to get created on first > >open and then removed on last close [...] I would still depend on the > >cdevpriv destructor and use a reference count between open() and the > >destructor to know when to cleanup shared state. >=20 > Yes, this is what I am doing. I am maintaining a list of all file=20 > descriptors open on the device. Once the length of that list reaches=20 > zero, I do global clean-up in the cdevpriv destructor. You are mixing things, and do repeat the work (probably buggy) that is already done by devfs. You should understand the relationship between basic concepts first. File descriptor !=3D opened file !=3D cdev node. Driver indeed may get notifications on all open(2) syscalls performed on the node, but is has absolutely no way to enumerate filedescriptors referencing that files. cdevpriv is per file, not per node. cdevpriv is cleaned automatically when last filedescriptor referencing the file is gone, not when the last file referencing the node is closed. The later is approximated by d_close(). --AMNVzrRY61gDOMe/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk24kBwACgkQC3+MBN1Mb4iVHACguKtBZiISUM/bFpYerbzTCliT zzwAoMmnQszeDh27mxADSSmYx53Yfk2E =Zzpo -----END PGP SIGNATURE----- --AMNVzrRY61gDOMe/-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 22:14:52 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8695B106566B; Wed, 27 Apr 2011 22:14:52 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 446F08FC0C; Wed, 27 Apr 2011 22:14:52 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 8EC8B188603F; Thu, 28 Apr 2011 00:14:50 +0200 (CEST) Message-ID: <4DB89559.3080008@chillt.de> Date: Thu, 28 Apr 2011 00:14:49 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Kostik Belousov References: <4DB695DB.1080505@chillt.de> <201104271019.31844.jhb@freebsd.org> <4DB818A3.1020104@chillt.de> <201104271334.07170.jhb@freebsd.org> <4DB8873C.5020608@chillt.de> <20110427215228.GY48734@deviant.kiev.zoral.com.ua> In-Reply-To: <20110427215228.GY48734@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:14:52 -0000 Indeed, I may have mixed up terminology. Sorry about that. What I am doing (or trying to do) is very simple: There is a single physical USB device. I have a single device node representing it. This device can be opened for reading, concurrently, any number of times. Everyone who open()s the device can read() it at their own pace. I implemented this by maintaining an individual queue of incoming data for each open() call. This queue resides in cdevpriv. So open() instantiates a queue and adds it to the driver's global list of queues. Whenever a packet arrives from the device, it is placed in all the queues (I have a linked list of all queues for that purpose). When the open() is eventually followed by a close(), the cdevpriv destructor removes the queue from the global list and frees its memory. In addition to this, I need to start the USB transfer when the first open() occurs and stop it again when the last close() occurs. I am doing this by checking the length of the global list. When the list is zero-length on open(), I start the transfer. When the list i zero-length in the cdevpriv destructor, I stop the transfer. I cannot see how else to achieve this behavior (other than device cloning which I was using before but which is more complicated and probably more error-prone). If I am doing something wrong and there is a more correct way to do it, I would love to hear about it. - Bartosz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 22:38:19 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2616E1065670; Wed, 27 Apr 2011 22:38:19 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id AF2DA8FC0A; Wed, 27 Apr 2011 22:38:18 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p3RMcBFk029319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 28 Apr 2011 01:38:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p3RMcBHn088447; Thu, 28 Apr 2011 01:38:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p3RMcB2Q088446; Thu, 28 Apr 2011 01:38:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 28 Apr 2011 01:38:11 +0300 From: Kostik Belousov To: Bartosz Fabianowski Message-ID: <20110427223811.GA48734@deviant.kiev.zoral.com.ua> References: <4DB695DB.1080505@chillt.de> <201104271019.31844.jhb@freebsd.org> <4DB818A3.1020104@chillt.de> <201104271334.07170.jhb@freebsd.org> <4DB8873C.5020608@chillt.de> <20110427215228.GY48734@deviant.kiev.zoral.com.ua> <4DB89559.3080008@chillt.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hImnF3KMhyKrbB+/" Content-Disposition: inline In-Reply-To: <4DB89559.3080008@chillt.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_05, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:38:19 -0000 --hImnF3KMhyKrbB+/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 28, 2011 at 12:14:49AM +0200, Bartosz Fabianowski wrote: > Indeed, I may have mixed up terminology. Sorry about that. What I am=20 > doing (or trying to do) is very simple: >=20 > There is a single physical USB device. I have a single device node=20 > representing it. This device can be opened for reading, concurrently,=20 > any number of times. Everyone who open()s the device can read() it at=20 > their own pace. I implemented this by maintaining an individual queue of= =20 > incoming data for each open() call. This queue resides in cdevpriv. >=20 > So open() instantiates a queue and adds it to the driver's global list=20 > of queues. Whenever a packet arrives from the device, it is placed in=20 > all the queues (I have a linked list of all queues for that purpose).=20 > When the open() is eventually followed by a close(), the cdevpriv=20 > destructor removes the queue from the global list and frees its memory. >=20 > In addition to this, I need to start the USB transfer when the first=20 > open() occurs and stop it again when the last close() occurs. I am doing= =20 > this by checking the length of the global list. When the list is=20 > zero-length on open(), I start the transfer. When the list i zero-length= =20 > in the cdevpriv destructor, I stop the transfer. >=20 > I cannot see how else to achieve this behavior (other than device=20 > cloning which I was using before but which is more complicated and=20 > probably more error-prone). If I am doing something wrong and there is a= =20 > more correct way to do it, I would love to hear about it. This is a strange architecture, esp. amusing is the kernel-mode traffic multiplier. Without knowing the details, and really not wanting to know it, I could make two suggestions out of thin air: - use usermode daemon that multiplies traffic for all connected clients; - or, implement a ring buffer that cyclically stores the received data, and keep only the current read pointer in the cdevpriv. You need to handle the overflow case (eq. to the stuck reader) somehow in the current scheme anyway. Reader may now read from its current read position in the buffer up to the fill point. If the buffer wrapped for the reader, it should get some error. --hImnF3KMhyKrbB+/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk24mtIACgkQC3+MBN1Mb4i5GQCfV+389ZZ9qk3HcxpdKFPCu0Uo dYkAn0kMKW/F+xqu2KcWKoefadqjNU1Y =P07P -----END PGP SIGNATURE----- --hImnF3KMhyKrbB+/-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 27 22:46:14 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C09B01065673; Wed, 27 Apr 2011 22:46:14 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd16434.kasserver.com (dd16434.kasserver.com [85.13.137.111]) by mx1.freebsd.org (Postfix) with ESMTP id 7CD0F8FC12; Wed, 27 Apr 2011 22:46:14 +0000 (UTC) Received: from taiko.lan (ppp-197-43.21-151.libero.it [151.21.43.197]) by dd16434.kasserver.com (Postfix) with ESMTPSA id 4467A18860EE; Thu, 28 Apr 2011 00:46:13 +0200 (CEST) Message-ID: <4DB89C9E.1070004@chillt.de> Date: Thu, 28 Apr 2011 00:45:50 +0200 From: Bartosz Fabianowski User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110309 Thunderbird/3.1.9 MIME-Version: 1.0 To: Kostik Belousov References: <4DB695DB.1080505@chillt.de> <201104271019.31844.jhb@freebsd.org> <4DB818A3.1020104@chillt.de> <201104271334.07170.jhb@freebsd.org> <4DB8873C.5020608@chillt.de> <20110427215228.GY48734@deviant.kiev.zoral.com.ua> <4DB89559.3080008@chillt.de> <20110427223811.GA48734@deviant.kiev.zoral.com.ua> In-Reply-To: <20110427223811.GA48734@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Hans Petter Selasky Subject: Re: Is there some implicit locking of device methods? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 22:46:14 -0000 > This is a strange architecture, esp. amusing is the kernel-mode > traffic multiplier. This mimics the Linux input events framework. The architecture is not mine, I am just implementing it under FreeBSD. > - use usermode daemon that multiplies traffic for all connected > clients; A better architecture for sure - but I want to stay compatible with code written for Linux and so must provide concurrent access via a single device node. > - or, implement a ring buffer that cyclically stores the received > data, and keep only the current read pointer in the cdevpriv. Good idea. This will save a few kilobytes of memory. > You need to handle the overflow case (eq. to the stuck reader) > somehow in the current scheme anyway. Reader may now read from its > current read position in the buffer up to the fill point. If the > buffer wrapped for the reader, it should get some error. Yes, of course. I am checking the queue fill state and making sure not to overflow it. - Bartosz From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 28 07:21:12 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id EA9CA1065798; Thu, 28 Apr 2011 07:21:12 +0000 (UTC) Date: Thu, 28 Apr 2011 07:21:12 +0000 From: Alexander Best To: Garrett Cooper Message-ID: <20110428072112.GA66450@freebsd.org> References: <20110424174442.GA45573@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: "freebsd-hackers@freebsd.org" Subject: Re: exit(3) and sysexits(3) style policy X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 07:21:13 -0000 On Sun Apr 24 11, Garrett Cooper wrote: > On Apr 24, 2011, at 10:44 AM, Alexander Best wrote: > > > hi there, > > > > i was wondering about this for some time now: > > > > various documents decribe different policies regarding exit(3)'s return values. > > style(9) e.g. recommends using exit(0), while other man pages such as err(3) > > recommend using the sysexits(3) return values. > > > > i think i read some time ago on the mailinglists that it was decided that > > exit(3) should return integers rathers than sysexits(3) values. is this > > correct? shouldn't then all references such as in err(3) be removed and a > > note added to sysexits(3) that returnings its values via exit(3) does not > > according to current FreeBSD programming style? > > Bruce Evans was very anti-sysexits a while ago, and I personally agree -- in part because they're not necessarily portable and their application isn't consistent. thanks for the hint. i'll try to find bruce's mail regarding this issue in the mailinglist archives. -- a13x From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 28 07:27:03 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 70C8E106567B; Thu, 28 Apr 2011 07:27:03 +0000 (UTC) Date: Thu, 28 Apr 2011 07:27:03 +0000 From: Alexander Best To: Devin Teske Message-ID: <20110428072703.GC66450@freebsd.org> References: <02a701cc006a$887da210$9978e630$@vicor.com> <20110422145518.GA16734@freebsd.org> <20110422154146.GA26083@freebsd.org> <20110422173509.000077ba@unknown> <039f01cc010d$b476d0f0$1d6472d0$@vicor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <039f01cc010d$b476d0f0$1d6472d0$@vicor.com> Cc: 'Bruce Cran' , freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, "'Teske, Devin'" Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 07:27:03 -0000 On Fri Apr 22 11, Devin Teske wrote: > > -----Original Message----- > > From: Bruce Cran [mailto:bruce@cran.org.uk] > > Sent: Friday, April 22, 2011 9:35 AM > > To: Alexander Best > > Cc: Devin Teske; freebsd-hackers@freebsd.org; freebsd-questions@freebsd.org; > > 'Teske, Devin' > > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring > > FreeBSD > > > > On Fri, 22 Apr 2011 15:41:46 +0000 > > Alexander Best wrote: > > > > > FreeBSD 9.0-CURRENT amd64 > > > > A new version of dialog was imported a few days ago - maybe something broke? > > Looks like `--hline' is not supported anymore. Thinking this should either be > patched or documented in ERRATA/UPGRADING. what would be the equivalent to --hline in the new dialog(1) package? > > > > > -- > > Bruce Cran > > _____________ > > 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. > _____________ -- a13x From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 28 16:04:19 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 812D8106566C; Thu, 28 Apr 2011 16:04:19 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by mx1.freebsd.org (Postfix) with ESMTP id 186DE8FC13; Thu, 28 Apr 2011 16:04:19 +0000 (UTC) Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by mailhost.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.1.270.2; Thu, 28 Apr 2011 17:52:53 +0200 Received: from beagle.kn.op.dlr.de (129.247.178.136) by smtp.dlr.de (172.21.152.151) with Microsoft SMTP Server (TLS) id 14.1.270.2; Thu, 28 Apr 2011 17:52:57 +0200 Date: Thu, 28 Apr 2011 17:52:58 +0200 From: Hartmut Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Roman Divacky In-Reply-To: <20110427193946.GA41659@freebsd.org> Message-ID: <20110428174523.I61666@beagle.kn.op.dlr.de> References: <20110427193946.GA41659@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [129.247.178.136] Cc: hackers@freebsd.org Subject: Re: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 16:04:19 -0000 Hi Roman, On Wed, 27 Apr 2011, Roman Divacky wrote: RD>You seem to have messed with bsd make so I have a question for you :) Yeah, that was some time ago ... RD>When a job is about to be executed in JobStart() a pipe is created with RD>its ends connected to job->inPipe/job->outPipe. When the job is actually RD>created in JobExec() the ps.out is set to job->outPipe so that in RD>JobDoOutput() we can read from that pipe and basically just parse the output RD>for shell->noPrint and leaving it out from the output. This is meant (I think) RD>for supressing the "filter" thing. Ie. that if we do some @command the RD>restoration of setting of quiet mode is filtered out. RD> RD> RD>In -B mode we do it differently, as we invoke one shell per command we don't RD>have to insert quiet/verbose commands and thus avoid all the piping/parsing RD>dance. RD> RD>So my question is - why don't we invoke one shell per command by default RD>and avoid the piping/parsing? Is this because of performance? I think that RD>the piping/parsing of the output can have worse impact than invoking a shell RD>for every command. Especially given that most targets consists of just one RD>command. The answer is in /usr/share/doc/psd/12.make. This is so one can write something like debug: DEBUG_FLAGS=-g for i in $(SUBDIR); do $(MAKE) -C $$i all done instead of: debug: DEBUG_FLAGS=-g \ for i in $(SUBDIR); do \ $(MAKE) -C $$i all ; \ done -B means 'backward compatible' and does what the original v7 make did: one shell per command. This means you don't have to write the backslashes and the shell variable will be seen in the sub-makes and programs. I think we can change this, because it would break makefiles that assume that the entire script is given to the shell in one piece. harti From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 28 17:27:03 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 216F91065670; Thu, 28 Apr 2011 17:27:03 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id D883A8FC12; Thu, 28 Apr 2011 17:27:02 +0000 (UTC) Received: from sbhfislrext02.fnfis.com ([192.168.249.140]) by SCSFISLTC01 (8.14.3/8.14.3) with ESMTP id p3SHQwFb018835; Thu, 28 Apr 2011 12:26:58 -0500 Received: from SBHFISLTCGW04.FNFIS.COM (Not Verified[10.132.248.123]) by sbhfislrext02.fnfis.com with MailMarshal (v6, 5, 4, 7535) id ; Thu, 28 Apr 2011 12:26:58 -0500 Received: from SBHFISLTCGW07.FNFIS.COM ([10.132.248.135]) by SBHFISLTCGW04.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Thu, 28 Apr 2011 12:26:58 -0500 Received: from dtwin ([10.132.254.135]) by SBHFISLTCGW07.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 28 Apr 2011 12:26:57 -0500 From: "Devin Teske" To: "'Alexander Best'" References: <02a701cc006a$887da210$9978e630$@vicor.com> <20110422145518.GA16734@freebsd.org> <20110422154146.GA26083@freebsd.org> <20110422173509.000077ba@unknown> <039f01cc010d$b476d0f0$1d6472d0$@vicor.com> <20110428072703.GC66450@freebsd.org> In-Reply-To: <20110428072703.GC66450@freebsd.org> Date: Thu, 28 Apr 2011 10:26:52 -0700 Organization: Vicor, Inc. Message-ID: <009501cc05c9$77611c00$66235400$@vicor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHbf51LIKsKPgssf99P131HkrB38wGbPSlTAgK1w+gCwVx/+gErfQdlAchwAK8Bxi4JRJP7vjdw Content-Language: en-us X-OriginalArrivalTime: 28 Apr 2011 17:26:57.0982 (UTC) FILETIME=[79F8DDE0:01CC05C9] Cc: 'Bruce Cran' , freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, "'Teske, Devin'" Subject: RE: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 17:27:03 -0000 > -----Original Message----- > From: Alexander Best [mailto:arundel@freebsd.org] > Sent: Thursday, April 28, 2011 12:27 AM > To: Devin Teske > Cc: 'Bruce Cran'; freebsd-hackers@freebsd.org; freebsd-questions@freebsd.org; > 'Teske, Devin' > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring > FreeBSD > > On Fri Apr 22 11, Devin Teske wrote: > > > -----Original Message----- > > > From: Bruce Cran [mailto:bruce@cran.org.uk] > > > Sent: Friday, April 22, 2011 9:35 AM > > > To: Alexander Best > > > Cc: Devin Teske; freebsd-hackers@freebsd.org; > > > freebsd-questions@freebsd.org; 'Teske, Devin' > > > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for > > > configuring FreeBSD > > > > > > On Fri, 22 Apr 2011 15:41:46 +0000 > > > Alexander Best wrote: > > > > > > > FreeBSD 9.0-CURRENT amd64 > > > > > > A new version of dialog was imported a few days ago - maybe something > broke? > > > > Looks like `--hline' is not supported anymore. Thinking this should > > either be patched or documented in ERRATA/UPGRADING. > > what would be the equivalent to --hline in the new dialog(1) package? There are no equivalents to either the `--hline' or `--hfile' options. Compare the 8.2-RELEASE manual to the 9-CURRENT manual: 8.2-RELEASE: http://www.freebsd.org/cgi/man.cgi?query=dialog&apropos=0&sektion=0&manpath=Free BSD+8.2-RELEASE&format=html 9-CURRENT: http://www.freebsd.org/cgi/man.cgi?query=dialog&apropos=0&sektion=0&manpath=Free BSD+9-current&format=html When comparing the above man-pages, issues include: OLD SYNTAX: --hline line NEW SYNTAX: Not available anymore?! ISSUE: No longer capable of setting string to be displayed at bottom of dialog box (exact opposite of --title). OLD SYNTAX: --hfile file NEW SYNTAX: Not available anymore?! ISSUE: No longer capable of setting a file to be displayed by pressing either ? or F1. OLD SYNTAX: --yesno text height width [yes|no] NEW SYNTAX: --yesno text height width ISSUE: Optional fourth argument to change default selection no longer accepted?! DISCUSS: Without fourth argument to change default selection, is the programmer expected to finagle this by using common-options `--no-label YES' and `--yes-label NO' and change logic to treat NO as YES and vice-versa? OLD SYNTAX: --prgbox command height width NEW SYNTAX: Not available anymore?! ISSUE: No longer capable of displaying output of command in dialog box? DISCUSS: As an alternative, I guess we could output the text to a temporary file and then use --textbox OLD SYNTAX: --ftree file FS text height width menu-height NEW SYNTAX: Not available anymore?! ISSUE: No longer capable of displaying a tree described by the data from `file' (which should contain find(1) output). DISCUSS: There appears to be no analog (this is an informational dialog that takes no user input opposed to --dselect and --fselect which are for taking user input in the new dialog; guess we're just out of luck on these ones). OLD SYNTAX: --tree FS text height width menu-height [ item ] ... NEW SYNTAX: Not available anymore?! ISSUE: No longer capable of displaying a tree described by a series of arguments? DISCUSS: Like --ftree, there appears to be no analog. Don't get me wrong... the new dialog *adds* more options than it takes away (or breaks). However, it's frustrating that backward compatibility is not being retained. On a side-note, I notice that my CentOS 4.7 system is running a dialog that matches syntax exactly with what was imported into RELENG_9 (this is a great thing -- meaning I can write dialog(1) based scripts that are compatible with both Linux and FreeBSD with very little effort). Though I'd still like to see the gaps filled so that we could also run legacy dialog(1) based scripts designed for the [8.x and] older dialog(1). -- Devin > > > > > > > > > -- > > > Bruce Cran > > > > _____________ > > > > 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. > > _____________ > > -- > a13x _____________ 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. _____________ From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 28 17:42:38 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF8C7106566C for ; Thu, 28 Apr 2011 17:42:38 +0000 (UTC) (envelope-from rdivacky@vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [46.28.110.116]) by mx1.freebsd.org (Postfix) with ESMTP id 85BF98FC15 for ; Thu, 28 Apr 2011 17:42:38 +0000 (UTC) Received: by vlakno.cz (Postfix, from userid 1002) id 2E1B37F3AF3; Thu, 28 Apr 2011 19:36:13 +0200 (CEST) Date: Thu, 28 Apr 2011 19:36:13 +0200 From: Roman Divacky To: Hartmut Brandt Message-ID: <20110428173613.GA31077@freebsd.org> References: <20110427193946.GA41659@freebsd.org> <20110428174523.I61666@beagle.kn.op.dlr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110428174523.I61666@beagle.kn.op.dlr.de> User-Agent: Mutt/1.4.2.3i Cc: hackers@freebsd.org Subject: Re: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 17:42:38 -0000 On Thu, Apr 28, 2011 at 05:52:58PM +0200, Hartmut Brandt wrote: > Hi Roman, > > On Wed, 27 Apr 2011, Roman Divacky wrote: > > RD>You seem to have messed with bsd make so I have a question for you :) > > Yeah, that was some time ago ... > > RD>When a job is about to be executed in JobStart() a pipe is created with > RD>its ends connected to job->inPipe/job->outPipe. When the job is actually > RD>created in JobExec() the ps.out is set to job->outPipe so that in > RD>JobDoOutput() we can read from that pipe and basically just parse the output > RD>for shell->noPrint and leaving it out from the output. This is meant (I think) > RD>for supressing the "filter" thing. Ie. that if we do some @command the > RD>restoration of setting of quiet mode is filtered out. > RD> > RD> > RD>In -B mode we do it differently, as we invoke one shell per command we don't > RD>have to insert quiet/verbose commands and thus avoid all the piping/parsing > RD>dance. > RD> > RD>So my question is - why don't we invoke one shell per command by default > RD>and avoid the piping/parsing? Is this because of performance? I think that > RD>the piping/parsing of the output can have worse impact than invoking a shell > RD>for every command. Especially given that most targets consists of just one > RD>command. > > The answer is in /usr/share/doc/psd/12.make. This is so one can write > something like > > debug: > DEBUG_FLAGS=-g > for i in $(SUBDIR); do > $(MAKE) -C $$i all > done > > instead of: > > debug: > DEBUG_FLAGS=-g \ > for i in $(SUBDIR); do \ > $(MAKE) -C $$i all ; \ > done > > -B means 'backward compatible' and does what the original v7 make did: one > shell per command. This means you don't have to write the backslashes and > the shell variable will be seen in the sub-makes and programs. > > I think we can change this, because it would break makefiles that assume > that the entire script is given to the shell in one piece. I think you answered the question why we parse the target. But I asked why we parse the output from it. Anyway, so you think it would be ok to change it to one shell per command and avoid the shell output parsing or not? I am interested in this so that "make -j*" lets the command know that the output is a TTY, eg. clang can emit coloured warnings. Thank you, roman From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 28 18:50:53 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6A96106564A; Thu, 28 Apr 2011 18:50:53 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by mx1.freebsd.org (Postfix) with ESMTP id 19E218FC1A; Thu, 28 Apr 2011 18:50:52 +0000 (UTC) Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by mailhost.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.1.270.2; Thu, 28 Apr 2011 20:50:25 +0200 Received: from beagle.kn.op.dlr.de (129.247.178.136) by smtp.dlr.de (172.21.152.151) with Microsoft SMTP Server (TLS) id 14.1.270.2; Thu, 28 Apr 2011 20:50:29 +0200 Date: Thu, 28 Apr 2011 20:50:27 +0200 From: Hartmut Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Roman Divacky In-Reply-To: <20110428173613.GA31077@freebsd.org> Message-ID: <20110428203709.M62691@beagle.kn.op.dlr.de> References: <20110427193946.GA41659@freebsd.org> <20110428174523.I61666@beagle.kn.op.dlr.de> <20110428173613.GA31077@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [129.247.178.136] Cc: hackers@freebsd.org Subject: Re: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 18:50:53 -0000 On Thu, 28 Apr 2011, Roman Divacky wrote: RD>On Thu, Apr 28, 2011 at 05:52:58PM +0200, Hartmut Brandt wrote: RD>> Hi Roman, RD>> RD>> On Wed, 27 Apr 2011, Roman Divacky wrote: RD>> RD>> RD>You seem to have messed with bsd make so I have a question for you :) RD>> RD>> Yeah, that was some time ago ... RD>> RD>> RD>When a job is about to be executed in JobStart() a pipe is created with RD>> RD>its ends connected to job->inPipe/job->outPipe. When the job is actually RD>> RD>created in JobExec() the ps.out is set to job->outPipe so that in RD>> RD>JobDoOutput() we can read from that pipe and basically just parse the output RD>> RD>for shell->noPrint and leaving it out from the output. This is meant (I think) RD>> RD>for supressing the "filter" thing. Ie. that if we do some @command the RD>> RD>restoration of setting of quiet mode is filtered out. RD>> RD> RD>> RD> RD>> RD>In -B mode we do it differently, as we invoke one shell per command we don't RD>> RD>have to insert quiet/verbose commands and thus avoid all the piping/parsing RD>> RD>dance. RD>> RD> RD>> RD>So my question is - why don't we invoke one shell per command by default RD>> RD>and avoid the piping/parsing? Is this because of performance? I think that RD>> RD>the piping/parsing of the output can have worse impact than invoking a shell RD>> RD>for every command. Especially given that most targets consists of just one RD>> RD>command. RD>> RD>> The answer is in /usr/share/doc/psd/12.make. This is so one can write RD>> something like RD>> RD>> debug: RD>> DEBUG_FLAGS=-g RD>> for i in $(SUBDIR); do RD>> $(MAKE) -C $$i all RD>> done RD>> RD>> instead of: RD>> RD>> debug: RD>> DEBUG_FLAGS=-g \ RD>> for i in $(SUBDIR); do \ RD>> $(MAKE) -C $$i all ; \ RD>> done RD>> RD>> -B means 'backward compatible' and does what the original v7 make did: one RD>> shell per command. This means you don't have to write the backslashes and RD>> the shell variable will be seen in the sub-makes and programs. RD>> RD>> I think we can change this, because it would break makefiles that assume RD>> that the entire script is given to the shell in one piece. RD> RD>I think you answered the question why we parse the target. But I asked why RD>we parse the output from it. My intention was to say why we use one shell for all commands for a given rule. If we'd use one shell per line the above would not work, because the first shell would see just the environment variable assignment (which would be completly useless). The next shell would see a partial 'for' statement and complain, and would not have the environment variable and so on. So this is not so much about parsing, but about execution. I suppose that the tricky point is with @-lines in the middle of a multi-line script. RD>Anyway, so you think it would be ok to change it to one shell per command and RD>avoid the shell output parsing or not? Unless I misunderstand the question I would say no, because this would certainly render makefiles invalid that rely on the multi-line scripts beeing handled by a single shell. RD>I am interested in this so that "make -j*" lets the command know that the RD>output is a TTY, eg. clang can emit coloured warnings. Hmm. I see. Just a wild guess: couldn't we use a pty to talk to the shell? If that could work the question is of course what one would expect from something like: make 2>&1 >make.out harti From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 02:01:51 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CEB11065672; Fri, 29 Apr 2011 02:01:51 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1984F8FC15; Fri, 29 Apr 2011 02:01:50 +0000 (UTC) Received: by iyj12 with SMTP id 12so3827160iyj.13 for ; Thu, 28 Apr 2011 19:01:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=o635z74EcfW7C3G1yczAw7eSV1YK0OO10bnL8qUDdOA=; b=o1/KUwPqpyT4Vvec8GmUsLr5cTGX9z+FRvxZIfu2T9hb37DGNMW3TEIU6Q8AjqoKxp +lQzkMA/DI6Eiuh4LBq3YpkGBWJ4DrI9VpX7dVQqRE+AymbfoLHYB7/znlg5GO4XnO1p 59YUEHiGjkcoWuUlFrfP1y7s0+MiyjHbSpwao= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=mtYafn0T8i7PsZVLrs8b1HrpDlkzX0MprIP3INXGcq0+XPK+MtGm2nK736RnkFM5ja /nrznQ7RSc/quK8EvWslWaX6QxO8673py8TrOAkyQsWhDVxTCBWvvTps1oupA5SXfNd4 HF9yHkMr5Ij6e5nEZ9pJszoIQJh9xXErz1wLg= MIME-Version: 1.0 Received: by 10.43.44.6 with SMTP id ue6mr5312819icb.69.1304041022019; Thu, 28 Apr 2011 18:37:02 -0700 (PDT) Received: by 10.42.165.132 with HTTP; Thu, 28 Apr 2011 18:37:01 -0700 (PDT) In-Reply-To: <20110428174523.I61666@beagle.kn.op.dlr.de> References: <20110427193946.GA41659@freebsd.org> <20110428174523.I61666@beagle.kn.op.dlr.de> Date: Thu, 28 Apr 2011 21:37:01 -0400 Message-ID: From: Arnaud Lacombe To: Hartmut Brandt Content-Type: text/plain; charset=ISO-8859-1 Cc: Roman Divacky , hackers@freebsd.org Subject: Re: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 02:01:51 -0000 Hi, On Thu, Apr 28, 2011 at 11:52 AM, Hartmut Brandt wrote: > I think we can change this, because it would break makefiles that assume > that the entire script is given to the shell in one piece. > I'm not sure to parse that. "We can change it because it would break stuff". That said, if something was to be broken, it would already shows up when using "-j N", and thus should be considered as a bug. - Arnaud From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 06:40:50 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD7C2106566B; Fri, 29 Apr 2011 06:40:50 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (unknown [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 9AE9A8FC17; Fri, 29 Apr 2011 06:40:50 +0000 (UTC) Received: from [10.0.0.63] (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p3T6XTNa087141 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Fri, 29 Apr 2011 00:33:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Fri, 29 Apr 2011 00:33:29 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <19A0E2B5-54A9-4929-A4DB-3E0DCC251DFA@bsdimp.com> References: <20110427193946.GA41659@freebsd.org> <20110428174523.I61666@beagle.kn.op.dlr.de> To: Arnaud Lacombe X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Fri, 29 Apr 2011 00:33:32 -0600 (MDT) Cc: Hartmut Brandt , hackers@freebsd.org, Roman Divacky Subject: Re: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 06:40:50 -0000 On Apr 28, 2011, at 7:37 PM, Arnaud Lacombe wrote: > On Thu, Apr 28, 2011 at 11:52 AM, Hartmut Brandt = wrote: >> I think we can change this, because it would break makefiles that = assume >> that the entire script is given to the shell in one piece. >>=20 > I'm not sure to parse that. "We can change it because it would break = stuff". >=20 > That said, if something was to be broken, it would already shows up > when using "-j N", and thus should be considered as a bug. There's bugs in the code which does the output which makes it wrong = often... So there's bugs both ways... There's archival history here in = hackers@. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 07:09:31 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 248FB106566C for ; Fri, 29 Apr 2011 07:09:31 +0000 (UTC) (envelope-from rdivacky@vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [46.28.110.116]) by mx1.freebsd.org (Postfix) with ESMTP id A23438FC0C for ; Fri, 29 Apr 2011 07:09:30 +0000 (UTC) Received: by vlakno.cz (Postfix, from userid 1002) id EE5E67F3B02; Fri, 29 Apr 2011 09:09:28 +0200 (CEST) Date: Fri, 29 Apr 2011 09:09:28 +0200 From: Roman Divacky To: Hartmut Brandt Message-ID: <20110429070928.GA83618@freebsd.org> References: <20110427193946.GA41659@freebsd.org> <20110428174523.I61666@beagle.kn.op.dlr.de> <20110428173613.GA31077@freebsd.org> <20110428203709.M62691@beagle.kn.op.dlr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110428203709.M62691@beagle.kn.op.dlr.de> User-Agent: Mutt/1.4.2.3i Cc: hackers@freebsd.org Subject: Re: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 07:09:31 -0000 On Thu, Apr 28, 2011 at 08:50:27PM +0200, Hartmut Brandt wrote: > On Thu, 28 Apr 2011, Roman Divacky wrote: > > RD>On Thu, Apr 28, 2011 at 05:52:58PM +0200, Hartmut Brandt wrote: > RD>> Hi Roman, > RD>> > RD>> On Wed, 27 Apr 2011, Roman Divacky wrote: > RD>> > RD>> RD>You seem to have messed with bsd make so I have a question for you :) > RD>> > RD>> Yeah, that was some time ago ... > RD>> > RD>> RD>When a job is about to be executed in JobStart() a pipe is created with > RD>> RD>its ends connected to job->inPipe/job->outPipe. When the job is actually > RD>> RD>created in JobExec() the ps.out is set to job->outPipe so that in > RD>> RD>JobDoOutput() we can read from that pipe and basically just parse the output > RD>> RD>for shell->noPrint and leaving it out from the output. This is meant (I think) > RD>> RD>for supressing the "filter" thing. Ie. that if we do some @command the > RD>> RD>restoration of setting of quiet mode is filtered out. > RD>> RD> > RD>> RD> > RD>> RD>In -B mode we do it differently, as we invoke one shell per command we don't > RD>> RD>have to insert quiet/verbose commands and thus avoid all the piping/parsing > RD>> RD>dance. > RD>> RD> > RD>> RD>So my question is - why don't we invoke one shell per command by default > RD>> RD>and avoid the piping/parsing? Is this because of performance? I think that > RD>> RD>the piping/parsing of the output can have worse impact than invoking a shell > RD>> RD>for every command. Especially given that most targets consists of just one > RD>> RD>command. > RD>> > RD>> The answer is in /usr/share/doc/psd/12.make. This is so one can write > RD>> something like > RD>> > RD>> debug: > RD>> DEBUG_FLAGS=-g > RD>> for i in $(SUBDIR); do > RD>> $(MAKE) -C $$i all > RD>> done > RD>> > RD>> instead of: > RD>> > RD>> debug: > RD>> DEBUG_FLAGS=-g \ > RD>> for i in $(SUBDIR); do \ > RD>> $(MAKE) -C $$i all ; \ > RD>> done > RD>> > RD>> -B means 'backward compatible' and does what the original v7 make did: one > RD>> shell per command. This means you don't have to write the backslashes and > RD>> the shell variable will be seen in the sub-makes and programs. > RD>> > RD>> I think we can change this, because it would break makefiles that assume > RD>> that the entire script is given to the shell in one piece. > RD> > RD>I think you answered the question why we parse the target. But I asked why > RD>we parse the output from it. > > My intention was to say why we use one shell for all commands for a given > rule. If we'd use one shell per line the above would not work, because the > first shell would see just the environment variable assignment (which > would be completly useless). The next shell would see a partial 'for' > statement and complain, and would not have the environment variable and so > on. So this is not so much about parsing, but about execution. > > I suppose that the tricky point is with @-lines in the middle of a > multi-line script. Unless I am reading the code wrong the "one shell per command" is the default mode. see in main.c: /* * Be compatible if user did not specify -j and did not explicitly * turned compatibility on */ if (!compatMake && !forceJobs) compatMake = TRUE; You have to specify -j to turn off the compat mode. > RD>Anyway, so you think it would be ok to change it to one shell per command and > RD>avoid the shell output parsing or not? > > Unless I misunderstand the question I would say no, because this would > certainly render makefiles invalid that rely on the multi-line scripts > beeing handled by a single shell. I think the chances of this breakage are pretty low as this is the default mode. > RD>I am interested in this so that "make -j*" lets the command know that the > RD>output is a TTY, eg. clang can emit coloured warnings. > > Hmm. I see. Just a wild guess: couldn't we use a pty to talk to the shell? > If that could work the question is of course what one would expect from > something like: make 2>&1 >make.out I looked at what gnu make does and I think they do pretty much the same what I suggested. Ie. one shell per command with no parsing of output by printing directly to stdout. Thus they have no problem with the process detecting stdout being a tty. From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 07:49:38 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EB1C106566B; Fri, 29 Apr 2011 07:49:38 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.33]) by mx1.freebsd.org (Postfix) with ESMTP id D89C08FC1C; Fri, 29 Apr 2011 07:49:37 +0000 (UTC) Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by mailhost.dlr.de (172.21.163.101) with Microsoft SMTP Server (TLS) id 14.1.270.2; Fri, 29 Apr 2011 09:49:09 +0200 Received: from DLREXMBX02.intra.dlr.de ([fe80::8cc6:b83e:ddc1:4e8b]) by dlrexhub02.intra.dlr.de ([::1]) with mapi id 14.01.0270.002; Fri, 29 Apr 2011 09:49:15 +0200 From: To: Thread-Topic: make question Thread-Index: AQHMBb37I4dDzUCVuES92kZ/L5vEm5Rz7tyAgACJb9A= Date: Fri, 29 Apr 2011 07:49:15 +0000 Message-ID: <611243783F62AF48AFB07BC25FA4B1060BDA03CE@dlrexmbx02.intra.dlr.de> References: <20110427193946.GA41659@freebsd.org> <20110428174523.I61666@beagle.kn.op.dlr.de>, In-Reply-To: Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.18.136.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: rdivacky@freebsd.org, hackers@freebsd.org Subject: RE: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 07:49:38 -0000 s/can/can't/=0A= =0A= harti=0A= ________________________________________=0A= From: Arnaud Lacombe [lacombar@gmail.com]=0A= Sent: Friday, April 29, 2011 3:37 AM=0A= To: Brandt, Hartmut=0A= Cc: Roman Divacky; hackers@freebsd.org=0A= Subject: Re: make question=0A= =0A= Hi,=0A= =0A= On Thu, Apr 28, 2011 at 11:52 AM, Hartmut Brandt wr= ote:=0A= > I think we can change this, because it would break makefiles that assume= =0A= > that the entire script is given to the shell in one piece.=0A= >=0A= I'm not sure to parse that. "We can change it because it would break stuff"= .=0A= =0A= That said, if something was to be broken, it would already shows up=0A= when using "-j N", and thus should be considered as a bug.=0A= =0A= - Arnaud=0A= From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 08:05:40 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D790106566C; Fri, 29 Apr 2011 08:05:40 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.32]) by mx1.freebsd.org (Postfix) with ESMTP id EB2788FC13; Fri, 29 Apr 2011 08:05:39 +0000 (UTC) Received: from DLREXHUB02.intra.dlr.de (172.21.152.140) by mailhost.dlr.de (172.21.163.100) with Microsoft SMTP Server (TLS) id 14.1.270.2; Fri, 29 Apr 2011 10:05:11 +0200 Received: from beagle.kn.op.dlr.de (129.247.178.136) by smtp.dlr.de (172.21.152.151) with Microsoft SMTP Server (TLS) id 14.1.270.2; Fri, 29 Apr 2011 10:05:17 +0200 Date: Fri, 29 Apr 2011 10:05:18 +0200 From: Hartmut Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Roman Divacky In-Reply-To: <20110429070928.GA83618@freebsd.org> Message-ID: <20110429095947.J64684@beagle.kn.op.dlr.de> References: <20110427193946.GA41659@freebsd.org> <20110428174523.I61666@beagle.kn.op.dlr.de> <20110428173613.GA31077@freebsd.org> <20110428203709.M62691@beagle.kn.op.dlr.de> <20110429070928.GA83618@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Originating-IP: [129.247.178.136] Cc: hackers@freebsd.org Subject: Re: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 08:05:40 -0000 On Fri, 29 Apr 2011, Roman Divacky wrote: RD>On Thu, Apr 28, 2011 at 08:50:27PM +0200, Hartmut Brandt wrote: RD>> On Thu, 28 Apr 2011, Roman Divacky wrote: RD>> RD>> RD>On Thu, Apr 28, 2011 at 05:52:58PM +0200, Hartmut Brandt wrote: RD>> RD>> Hi Roman, RD>> RD>> RD>> RD>> On Wed, 27 Apr 2011, Roman Divacky wrote: RD>> RD>> RD>> RD>> RD>You seem to have messed with bsd make so I have a question for you :) RD>> RD>> RD>> RD>> Yeah, that was some time ago ... RD>> RD>> RD>> RD>> RD>When a job is about to be executed in JobStart() a pipe is created with RD>> RD>> RD>its ends connected to job->inPipe/job->outPipe. When the job is actually RD>> RD>> RD>created in JobExec() the ps.out is set to job->outPipe so that in RD>> RD>> RD>JobDoOutput() we can read from that pipe and basically just parse the output RD>> RD>> RD>for shell->noPrint and leaving it out from the output. This is meant (I think) RD>> RD>> RD>for supressing the "filter" thing. Ie. that if we do some @command the RD>> RD>> RD>restoration of setting of quiet mode is filtered out. RD>> RD>> RD> RD>> RD>> RD> RD>> RD>> RD>In -B mode we do it differently, as we invoke one shell per command we don't RD>> RD>> RD>have to insert quiet/verbose commands and thus avoid all the piping/parsing RD>> RD>> RD>dance. RD>> RD>> RD> RD>> RD>> RD>So my question is - why don't we invoke one shell per command by default RD>> RD>> RD>and avoid the piping/parsing? Is this because of performance? I think that RD>> RD>> RD>the piping/parsing of the output can have worse impact than invoking a shell RD>> RD>> RD>for every command. Especially given that most targets consists of just one RD>> RD>> RD>command. RD>> RD>> RD>> RD>> The answer is in /usr/share/doc/psd/12.make. This is so one can write RD>> RD>> something like RD>> RD>> RD>> RD>> debug: RD>> RD>> DEBUG_FLAGS=-g RD>> RD>> for i in $(SUBDIR); do RD>> RD>> $(MAKE) -C $$i all RD>> RD>> done RD>> RD>> RD>> RD>> instead of: RD>> RD>> RD>> RD>> debug: RD>> RD>> DEBUG_FLAGS=-g \ RD>> RD>> for i in $(SUBDIR); do \ RD>> RD>> $(MAKE) -C $$i all ; \ RD>> RD>> done RD>> RD>> RD>> RD>> -B means 'backward compatible' and does what the original v7 make did: one RD>> RD>> shell per command. This means you don't have to write the backslashes and RD>> RD>> the shell variable will be seen in the sub-makes and programs. RD>> RD>> RD>> RD>> I think we can change this, because it would break makefiles that assume RD>> RD>> that the entire script is given to the shell in one piece. RD>> RD> RD>> RD>I think you answered the question why we parse the target. But I asked why RD>> RD>we parse the output from it. RD>> RD>> My intention was to say why we use one shell for all commands for a given RD>> rule. If we'd use one shell per line the above would not work, because the RD>> first shell would see just the environment variable assignment (which RD>> would be completly useless). The next shell would see a partial 'for' RD>> statement and complain, and would not have the environment variable and so RD>> on. So this is not so much about parsing, but about execution. RD>> RD>> I suppose that the tricky point is with @-lines in the middle of a RD>> multi-line script. RD> RD>Unless I am reading the code wrong the "one shell per command" is the default RD>mode. RD> RD>see in main.c: RD> RD> /* RD> * Be compatible if user did not specify -j and did not explicitly RD> * turned compatibility on RD> */ RD> if (!compatMake && !forceJobs) RD> compatMake = TRUE; RD> RD>You have to specify -j to turn off the compat mode. Wow. This breakage was introduced in our make in 1996 by an import from NetBSD (I did not check why they introduced it). I fail to see the logic in this handling of the -B option (if the user doesn't provide it, I (make) do it, unless the user said -j). But, the good side is, we can probably change the behavior of the non-compat mode, because the probability of there beeing makefiles that rely on it is now rather low. In any case I recommend to check what is the performance implication of executing a lot more shells in -j mode. I expect this to be in the noise level, but a check would not hurt... harti From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 11:14:58 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E758E106566B; Fri, 29 Apr 2011 11:14:58 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by mx1.freebsd.org (Postfix) with ESMTP id 68A278FC0A; Fri, 29 Apr 2011 11:14:58 +0000 (UTC) Received: from rbpbp.gid.co.uk (80-46-130-69.static.dsl.as9105.com [80.46.130.69]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id p3TAxiwB078373; Fri, 29 Apr 2011 11:59:45 +0100 (BST) (envelope-from rb@gid.co.uk) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Bob Bishop In-Reply-To: <20110429095947.J64684@beagle.kn.op.dlr.de> Date: Fri, 29 Apr 2011 11:59:39 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20110427193946.GA41659@freebsd.org> <20110428174523.I61666@beagle.kn.op.dlr.de> <20110428173613.GA31077@freebsd.org> <20110428203709.M62691@beagle.kn.op.dlr.de> <20110429070928.GA83618@freebsd.org> <20110429095947.J64684@beagle.kn.op.dlr.de> To: Hartmut Brandt X-Mailer: Apple Mail (2.1084) Cc: Roman Divacky , hackers@freebsd.org Subject: Re: make question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 11:14:59 -0000 Hi, This whole area is quite a mess. See for instance bin/10985 on = interactions between -j, -B and .NOTPARALLEL -- Bob Bishop rb@gid.co.uk From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 16:03:13 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E392C106564A for ; Fri, 29 Apr 2011 16:03:13 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 790288FC16 for ; Fri, 29 Apr 2011 16:03:13 +0000 (UTC) Received: by wwc33 with SMTP id 33so4025624wwc.31 for ; Fri, 29 Apr 2011 09:03:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:content-type :content-transfer-encoding:x-mailer; bh=2u0epBUn6EfXxsOzRF49irxNrtyDmD88uDLZ9r+2RiQ=; b=I399Ni3qnF0SaSAwRjCU8nzByEtynHKA2QqrdpHTkJr6r7jZthGi0qOpMTufxFcIPk wWhFBwQN+9gfLL3/OOtw7ea/nVmlo7qrZzmtvEm95poTDz4Q3SSiNsumFFNgZlx34pSy GiHfeOEFDgbzZp412WxSsVujLEAMifiuohdt0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:content-type :content-transfer-encoding:x-mailer; b=Gx64Yq1vkkgODCrprcK1rZ10WAWodq+Wij9FjbW/EEZZxErdAFn9L0bLU5E/VHB7YN ZfXBVAPAH/6Zio9sxs9/BdNNIl6HtsG4zZhTRZHYupgi2GvkXzqpbgA+oDhye+zcHnH+ rFq7DZfDu//68mTbZNMI1FrYZgHq5yCNnmB64= Received: by 10.227.130.78 with SMTP id r14mr1040313wbs.101.1304092991839; Fri, 29 Apr 2011 09:03:11 -0700 (PDT) Received: from DEV ([82.193.208.173]) by mx.google.com with ESMTPS id x1sm1787232wbh.53.2011.04.29.09.03.07 (version=SSLv3 cipher=OTHER); Fri, 29 Apr 2011 09:03:10 -0700 (PDT) Message-ID: <20110429.160309.656.1@DEV> From: rank1seeker@gmail.com To: freebsd-hackers@freebsd.org Date: Fri, 29 Apr 2011 18:03:09 +0200 Content-Type: text/plain; charset="Windows-1250" Content-Transfer-Encoding: quoted-printable X-Mailer: POP Peeper (3.7.0.0) Subject: Look of boot2, on HDD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 16:03:14 -0000 /boot/boot2 STAGE 2 bootstrap file=0D=0AUnderstands the FreeBSD file = system enough, to find files on it, and can provide a simple interface to = choose the kernel or loader to run.=0D=0A=0D=0AOnce sys is fully booted, = HDD is 'ada0'.=0D=0AHowever, STAGE 2, sees it, as a 'ad4', at boot = process, which is same seen, by booted sys, when I turn off = AHCI.=0D=0A=0D=0ASo, here is the riddle ...=0D=0AOn fully booted sys, how = do I query STAGE 2, to tell me, how it'll see, my 'ada0' = HDD?=0D=0A=0D=0A=0D=0ADomagoj Smol=E8i=E6=0D=0A From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 17:08:24 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFE3C106564A for ; Fri, 29 Apr 2011 17:08:24 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id AAD128FC16 for ; Fri, 29 Apr 2011 17:08:24 +0000 (UTC) Received: by yie12 with SMTP id 12so1968492yie.13 for ; Fri, 29 Apr 2011 10:08:24 -0700 (PDT) Received: by 10.236.105.169 with SMTP id k29mr1083645yhg.332.1304096903411; Fri, 29 Apr 2011 10:08:23 -0700 (PDT) Received: from bhuda.mired.org (h239.199.28.71.dynamic.ip.windstream.net [71.28.199.239]) by mx.google.com with ESMTPS id u50sm1395753yhn.50.2011.04.29.10.08.22 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Apr 2011 10:08:23 -0700 (PDT) Date: Fri, 29 Apr 2011 13:08:20 -0400 From: Mike Meyer To: Devin Teske Message-ID: <20110429130820.5056390e@bhuda.mired.org> In-Reply-To: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> Organization: Meyer Consulting X-Mailer: Claws Mail 3.7.7 (GTK+ 2.22.1; amd64-portbld-freebsd8.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 17:08:25 -0000 On Sun, 24 Apr 2011 18:53:11 -0700 Devin Teske wrote: > Hello fellow hackers, > > I'd love to finally release (under the BSD license) my code for the revamped FreeBSD boot loader menu. > > Here's a detailed discussion of the release complete with pictures: > http://devinteske.com/new-freebsd-boot-loader-menu Got it, nice simple install (as promised), and it worked like a charm. I'd like to revisit the numbers vs. letters for menu options. IIRC (and I may not), an earlier version used letters for the menu options, and people objected to that change. Since we're changing the menus, we ought to look at which is best for the end user, as opposed to just doing what feels comfortable to us as old users. In particular, there was a study done around '80 (I tried to find it but couldn't; I know of someone who can probably provide a reference if someone really wants it) that showed that menu selection with letters assigned mnemonically are easiest for users to memorize. Not really a major issue - you shouldn't be booting FreeBSD systems all that often, so it's not something I care very much about. However, I figure someone ought to at least speak up for using system that's better for new users rather than quietly doing it the old way since we're making a change anyway. http://www.mired.org/consulting.html Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 18:10:40 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91B69106566B for ; Fri, 29 Apr 2011 18:10:40 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (unknown [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 333368FC19 for ; Fri, 29 Apr 2011 18:10:40 +0000 (UTC) Received: from [10.30.101.54] ([209.117.142.2]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p3TI93U9096545 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Fri, 29 Apr 2011 12:09:04 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20110429130820.5056390e@bhuda.mired.org> Date: Fri, 29 Apr 2011 12:08:58 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <67529807-EAF5-4DEB-8B61-BD84ED8F2A5D@bsdimp.com> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> To: Mike Meyer X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Fri, 29 Apr 2011 12:09:05 -0600 (MDT) Cc: FreeBSD Hackers , Devin Teske Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 18:10:40 -0000 Why not both? Warner On Apr 29, 2011, at 11:08 AM, Mike Meyer wrote: > On Sun, 24 Apr 2011 18:53:11 -0700 > Devin Teske wrote: >=20 >> Hello fellow hackers, >>=20 >> I'd love to finally release (under the BSD license) my code for the = revamped FreeBSD boot loader menu. >>=20 >> Here's a detailed discussion of the release complete with pictures: >> http://devinteske.com/new-freebsd-boot-loader-menu >=20 > Got it, nice simple install (as promised), and it worked like a charm. >=20 > I'd like to revisit the numbers vs. letters for menu options. IIRC > (and I may not), an earlier version used letters for the menu options, > and people objected to that change. >=20 > Since we're changing the menus, we ought to look at which is best for > the end user, as opposed to just doing what feels comfortable to us as > old users. >=20 > In particular, there was a study done around '80 (I tried to find it > but couldn't; I know of someone who can probably provide a reference > if someone really wants it) that showed that menu selection with > letters assigned mnemonically are easiest for users to memorize. >=20 > Not really a major issue - you shouldn't be booting FreeBSD systems > all that often, so it's not something I care very much about. However, > I figure someone ought to at least speak up for using system that's > better for new users rather than quietly doing it the old way since > we're making a change anyway. >=20 > --=20 > Mike Meyer = http://www.mired.org/consulting.html > Independent Software developer/SCM consultant, email for more = information. >=20 > O< ascii ribbon campaign - stop html mail - www.asciiribbon.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >=20 >=20 From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 18:19:38 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D19A1065673 for ; Fri, 29 Apr 2011 18:19:38 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2CE528FC12 for ; Fri, 29 Apr 2011 18:19:37 +0000 (UTC) Received: by gyg13 with SMTP id 13so1985502gyg.13 for ; Fri, 29 Apr 2011 11:19:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TxxIRJ2iGxihc1ZI2r7ZcL2acfNxt7V3pd44MAWWaqA=; b=P7j9OpOPcFbjlKKhG7zpq1nn9lGlCKnwbvholrjrIwGxdthG0vDRu8jIy9TrI1z8Tx A357fjtbBbhE9H2+2Q/pMuHiDYTasVwMa5XV1WAixPw2k9wzCZ2V0m/LS4mctSWu+3cy cCRes+SJbY634jY6LNSzdNhgJuuKpctx2DCr0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=CK3TDKrQZYpiZTXdrn/X0ASW3PvQZIYCGKeZ7BAFQ4vK277MhaoCIvyxIU//Q8cCHp MQGVgw4+L8Io/meBXasqikAoZCTm0yxSCESfdG03xWWTrR65JuqXeTevLXh14ucrocF4 Ai4ZHNaCmMLGMEceGWQl7sD9JRUTi2D3KZYhI= MIME-Version: 1.0 Received: by 10.91.73.33 with SMTP id a33mr4654630agl.69.1304101177150; Fri, 29 Apr 2011 11:19:37 -0700 (PDT) Received: by 10.90.70.18 with HTTP; Fri, 29 Apr 2011 11:19:37 -0700 (PDT) In-Reply-To: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> Date: Fri, 29 Apr 2011 11:19:37 -0700 Message-ID: From: Freddie Cash To: Devin Teske Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Hackers Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 18:19:38 -0000 Very nice and functional, without adding a lot of extra verbosity or steps. I really appreciated the clean install via binary package. Well done. Only question I have is whether it's possible to use the Beastie ASCII image instead of the pointy-eared blob? The beastie.4th file is still present under /boot, but I don't know how to hook it into the new menu. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 19:02:08 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0DEA1065673 for ; Fri, 29 Apr 2011 19:02:08 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id BAFD18FC0C for ; Fri, 29 Apr 2011 19:02:07 +0000 (UTC) Received: from SBHFISLREXT03 ([10.132.254.62]) by SCSFISLTC01 (8.14.3/8.14.3) with ESMTP id p3TJ2716023170; Fri, 29 Apr 2011 14:02:07 -0500 Received: from sbhfisltcgw02.FNFIS.COM (Not Verified[10.132.248.122]) by SBHFISLREXT03 with MailMarshal (v6, 5, 4, 7535) id ; Fri, 29 Apr 2011 14:02:43 -0500 Received: from sbhfisltcgw02.FNFIS.COM ([10.132.248.122]) by sbhfisltcgw02.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 14:02:06 -0500 Received: from dtwin ([10.132.254.135]) by sbhfisltcgw02.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 14:02:05 -0500 From: "Devin Teske" To: "'Mike Meyer'" References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> In-Reply-To: <20110429130820.5056390e@bhuda.mired.org> Date: Fri, 29 Apr 2011 12:02:03 -0700 Organization: Vicor, Inc. Message-ID: <000301cc069f$edf8bd10$c9ea3730$@vicor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQF9G/AhblsjpgWTQkLl7e1bA9mQcAGd6pailQYOoYA= Content-Language: en-us X-OriginalArrivalTime: 29 Apr 2011 19:02:05.0941 (UTC) FILETIME=[EE980A50:01CC069F] Cc: 'FreeBSD Hackers' Subject: RE: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 19:02:09 -0000 > -----Original Message----- > From: Mike Meyer [mailto:mwm@mired.org] > Sent: Friday, April 29, 2011 10:08 AM > To: Devin Teske > Cc: FreeBSD Hackers > Subject: Re: [RELEASE] New Boot-Loader Menu > > On Sun, 24 Apr 2011 18:53:11 -0700 > Devin Teske wrote: > > > Hello fellow hackers, > > > > I'd love to finally release (under the BSD license) my code for the revamped > FreeBSD boot loader menu. > > > > Here's a detailed discussion of the release complete with pictures: > > http://devinteske.com/new-freebsd-boot-loader-menu > > Got it, nice simple install (as promised), and it worked like a charm. > > I'd like to revisit the numbers vs. letters for menu options. IIRC (and I may not), > an earlier version used letters for the menu options, and people objected to that > change. Looking at the CVS history of the Forth code that renders the menu, I'm noticing: a. FreeBSD-4.x and earlier didn't have a menu (after loading the kernel, the loader simply drops to autoboot). b. FreeBSD-5.x introduced the menu that is currently in-use today (rendered by `beastie.4th'). c. The current menu uses numbers, not letters. If there was an earlier version of the menu that used letters, I'm not seeing it in CVS. > > Since we're changing the menus, we ought to look at which is best for the end > user, as opposed to just doing what feels comfortable to us as old users. > I was thinking that what we ought to do is support *both* numbers *and* letters. I envision the menuitem numbers remaining unchanged (1-7), allowing those familiar with the numbers to use them. However, as for the letters, I'm thinking that we *BOLD* the mnemonic in the menuitem. For example (showing bolded items between asterisks): 1. Boot *[ENTER]* 2. *A*CPI Support: Enabled 3. Boot Safe Mode: NO 4. Boot *S*ingle User: NO 5. Boot *V*erbose: NO 6. *Esc*ape to loader prompt 7. *R*eboot This should indicate to the user, for example if they see that the "V" in "Verbose" is bolded, that they can press that key to activate that menuitem. In addition, represented above, the only non-numeric keys that do anything would be: ENTER to boot A to toggle ACPI support S to toggle Single User mode V to toggle Verbose boot Esc to escape to the loader prompt R to reboot Looking at a standard QWERTY keyboard, A and S are close to each other, but since the new menu is stateful (meaning that pressing the key merely changes the state of that option) rather than stateless (wherein pressing a key would immediately boot with that option), if you jam the wrong key, no worries (just jam it again to return it to its pre-toggled state). I'm open to discussion as to what the keys should be, though I'm pretty hard-set on "S" for single-user, and "V" for verbose (the others, besides ENTER-to-boot, are open for debate -- personally I think I'd be happy with nothing more than just ENTER, "S" and "V" and no others). > In particular, there was a study done around '80 (I tried to find it but couldn't; I > know of someone who can probably provide a reference if someone really wants > it) that showed that menu selection with letters assigned mnemonically are > easiest for users to memorize. I can believe that quite easily. However, currently the boot menu does not support such letters. I think this new loader menu is the perfect place to implement them. On another note, I have one other change that I'd like to get in... I noticed that (in CVS) the menu currently blanks-out option #2 if booting on a system where ACPI is disabled or unavailable. In my boot loader, I'd like to display "ACPI Support: N/A" rather than simply blanking out the menu item. -- Devin > > Not really a major issue - you shouldn't be booting FreeBSD systems all that > often, so it's not something I care very much about. However, I figure someone > ought to at least speak up for using system that's better for new users rather > than quietly doing it the old way since we're making a change anyway. > > -- > Mike Meyer > http://www.mired.org/consulting.html > Independent Software developer/SCM consultant, email for more information. > > O< ascii ribbon campaign - stop html mail - www.asciiribbon.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. _____________ From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 19:16:47 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26AF4106566B for ; Fri, 29 Apr 2011 19:16:47 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id E4BCE8FC1D for ; Fri, 29 Apr 2011 19:16:46 +0000 (UTC) Received: from sbhfislrext02.fnfis.com ([192.168.249.140]) by SCSFISLTC02 (8.14.3/8.14.3) with ESMTP id p3TJGkMp032154; Fri, 29 Apr 2011 14:16:46 -0500 Received: from sbhfisltcgw01.FNFIS.COM (Not Verified[10.132.248.121]) by sbhfislrext02.fnfis.com with MailMarshal (v6, 5, 4, 7535) id ; Fri, 29 Apr 2011 14:16:48 -0500 Received: from SBHFISLTCGW07.FNFIS.COM ([10.132.248.135]) by sbhfisltcgw01.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 14:16:46 -0500 Received: from dtwin ([10.132.254.135]) by SBHFISLTCGW07.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 14:16:42 -0500 From: "Devin Teske" To: "'Freddie Cash'" References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> In-Reply-To: Date: Fri, 29 Apr 2011 12:16:39 -0700 Organization: Vicor, Inc. Message-ID: <002001cc06a1$f8a18ce0$e9e4a6a0$@vicor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQF9G/AhblsjpgWTQkLl7e1bA9mQcAIRP0ELlQJ+YtA= Content-Language: en-us X-OriginalArrivalTime: 29 Apr 2011 19:16:43.0025 (UTC) FILETIME=[F9607010:01CC06A1] Cc: 'FreeBSD Hackers' Subject: RE: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 19:16:47 -0000 > -----Original Message----- > From: Freddie Cash [mailto:fjwcash@gmail.com] > Sent: Friday, April 29, 2011 11:20 AM > To: Devin Teske > Cc: FreeBSD Hackers > Subject: Re: [RELEASE] New Boot-Loader Menu >=20 > Very nice and functional, without adding a lot of extra verbosity or step= s. I really > appreciated the clean install via binary package. > Well done. >=20 > Only question I have is whether it's possible to use the Beastie ASCII im= age > instead of the pointy-eared blob? The beastie.4th file is still present = under /boot, > but I don't know how to hook it into the new menu. Glad you asked. This couldn't be easier. Open up `/boot/menu.rc' and look for the following lines (LINE 9-10): \ Customizations set logo=3D"orb" Feel free to play with any of the following drop-in replacements: set logo=3D"beastie" set logo=3D"beastiebw" set logo=3D"fbsdbw" set logo=3D"orb" set logo=3D"orbbw" Simply deleting the line or comment it out (by adding "\ " -- backslash-spa= ce -- to the beginning of the line) is equivalent to setting logo to "beast= ie". Here's a short explanation of each value: NAME DESCRIPTION beastie Color ``Helper Daemon'' mascot (19 rows x 34 columns) beastiebw B/W ``Helper Daemon'' mascot (19 rows x 34 columns) fbsdbw "FreeBSD" logo in B/W (13 rows x 21 columns) orb Color ``Orb'' mascot (15 rows x 30 columns) orbbw B/W ``Orb'' mascot (15 rows x 30 columns) I'm not sure what you meant by "Beastie ASCII" image, but I think you're ei= ther looking for "beastie" or "fbsdbw". You should have to, but if you need to, you can add: set logoX=3DX set logoY=3DY to force the row/column placement of beastie. --=20 Devin >=20 > -- > Freddie Cash > fjwcash@gmail.com _____________ 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-hackers@FreeBSD.ORG Fri Apr 29 19:24:28 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 558FA106566C for ; Fri, 29 Apr 2011 19:24:28 +0000 (UTC) (envelope-from mwm@mired.org) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0F1D38FC15 for ; Fri, 29 Apr 2011 19:24:27 +0000 (UTC) Received: by gwb15 with SMTP id 15so2020826gwb.13 for ; Fri, 29 Apr 2011 12:24:27 -0700 (PDT) Received: by 10.236.122.130 with SMTP id t2mr6672046yhh.367.1304105067139; Fri, 29 Apr 2011 12:24:27 -0700 (PDT) Received: from bhuda.mired.org (h239.199.28.71.dynamic.ip.windstream.net [71.28.199.239]) by mx.google.com with ESMTPS id x75sm1456394yhn.24.2011.04.29.12.24.26 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Apr 2011 12:24:26 -0700 (PDT) Date: Fri, 29 Apr 2011 15:24:23 -0400 From: Mike Meyer To: "Devin Teske" Message-ID: <20110429152423.11736f82@bhuda.mired.org> In-Reply-To: <000301cc069f$edf8bd10$c9ea3730$@vicor.com> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> <000301cc069f$edf8bd10$c9ea3730$@vicor.com> Organization: Meyer Consulting X-Mailer: Claws Mail 3.7.7 (GTK+ 2.22.1; amd64-portbld-freebsd8.1) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAG1BMVEXguIzRkGnhyaz069mXhW0WHRnbrnR9WCQ6LB0CchNMAAACSUlEQVQ4jV2TQW7jMAxFGaPQOgQEdZaGMsgBrAvUA03dCxj1Uu4U2gfwQD7AGNax51NK07RcxXz6/CSl0Ij450vkPG1jzpIZM1UwDCl/xB14TWnNX8A00Qj5a0mnVFVbVUz4MeErea2HikSRqZzY894zwg9p2+/AtO8LzxFED+tNAUFeU29iFOLRxlZAcdo9A8wi8ZBMV4BKPde82Oxrvs6BTkulQIClte0DLFzzsKk9j1MBex8iUaP00Bd78S/muyFScrTXz6zLkEUxJp+SabQfNOs4f4Jpx5qSZ/304PWwlEWP1cOn/mJQR7EOD+uKhjcBLziuL7xoY5Xm+VFAUSw/LwwwsHEHxihpwV4EJH0xXRkbw1PkRw+X4pEuSJwBggqk+HEYKkiL5/74/nQkogigzQsAFrakxZyfw3wMIEEZPv4AWMfxwqE5GNxGaERjmH+PG8AE0L4/w9g0lsp1raLYAN5azQa+AOoO9NwcpFkTrG2VKNMNEL5UKUUAw34tha0z7onUG0oBoNtczE04GwFE3wCHc0ChezAJ6A1WMV81AtY7wDAJSlXwV+4cwBvsOsrQMRawfQEBz0deEZ7WNpV2szckIKo5VpDHDSDvF1GItwqqAlG01Hh50BGtVhuUkjkasg/14bYFGCgWg1fSWHvmOoJck2xdp9ZvZBHzDVTzX23TkrOn7qe5U2COEw5D4Vx3qEQpFY2Z/3QFnJxzp7YCmSMG19nOUoe869zZfOQb5ywQuWu0yCn5+8gxZz+BE7vG3j4/wbf4D/sXN9Wug1s7AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: 'FreeBSD Hackers' Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 19:24:28 -0000 On Fri, 29 Apr 2011 12:02:03 -0700 "Devin Teske" wrote: > > -----Original Message----- > > From: Mike Meyer [mailto:mwm@mired.org] > > I'd like to revisit the numbers vs. letters for menu options. IIRC (and I may > not), > > an earlier version used letters for the menu options, and people objected to > that > > change. > > Looking at the CVS history of the Forth code that renders the menu, I'm > noticing: > > If there was an earlier version of the menu that used letters, I'm not seeing it > in CVS. I was referring to your code, not the historical FreeBSD code. Didn't you originally propose using letters, not numbers, to toggle the boot options? If not, then possibly I'm remembering another proposal. > > In particular, there was a study done around '80 (I tried to find it but > couldn't; I > > know of someone who can probably provide a reference if someone really wants > > it) that showed that menu selection with letters assigned mnemonically are > > easiest for users to memorize. > > I can believe that quite easily. However, currently the boot menu does not > support such letters. I think this new loader menu is the perfect place to > implement them. This seemed like a good time to change it if we were going to to me. > On another note, I have one other change that I'd like to get in... I noticed > that (in CVS) the menu currently blanks-out option #2 if booting on a system > where ACPI is disabled or unavailable. In my boot loader, I'd like to display > "ACPI Support: N/A" rather than simply blanking out the menu item. That would certainly make the numbers make more sense. Thanks, http://www.mired.org/consulting.html Independent Software developer/SCM consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 19:30:43 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2D81106566B; Fri, 29 Apr 2011 19:30:43 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 93E3C8FC19; Fri, 29 Apr 2011 19:30:43 +0000 (UTC) Received: by vws18 with SMTP id 18so3986440vws.13 for ; Fri, 29 Apr 2011 12:30:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=9DnFjZ7z/uzuVweI7JXdH7FGXg6cTjorJn63Ot59oHI=; b=ewppn1uPdLUL6CbFuCUkKaAnYFgceVVJo0aL0TerTK63PoG33cj3yz6XuE/4t5gjlQ Py/rqrDBjIMmhyixKoLe9+FNNP7/j0CvHhPTioOOEo3dCMnCv3bJOyDS0EbF8qNjC3Gp qO0QSDqRFM03Mk5Xgw3Ut7xHKs7XEsWVvwyOA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Vd/961triADUG9UMqv2rXNHn/muuefsNb0cJfXS2CsJRhRLNfg6MRlkC6JpDsFX1Wz jkl45ECPhmqi1DodrJIze+ZqANOh3uGnH+vow/jC0OYuXBci89j1Phi6smJTHnTWl/oj QsbMeZe32rNJTRxADXBE7cGPLkhFtE8bD+mhk= MIME-Version: 1.0 Received: by 10.220.112.138 with SMTP id w10mr809921vcp.46.1304105442373; Fri, 29 Apr 2011 12:30:42 -0700 (PDT) Received: by 10.220.58.5 with HTTP; Fri, 29 Apr 2011 12:30:42 -0700 (PDT) Date: Fri, 29 Apr 2011 15:30:42 -0400 Message-ID: From: Super Bisquit To: FreeBSD Hackers , gnome@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Bugzilla file reported. gnome developers want freebsd help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 19:30:44 -0000 https://bugzilla.gnome.org/show_bug.cgi?id=648430 It doesn't seem that there was any before this willing to submit a bug report about networking. The gnome developers are willing to work with the freebsd project. From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 20:00:38 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 4EAB5106564A; Fri, 29 Apr 2011 20:00:38 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 5167B14E1D8; Fri, 29 Apr 2011 20:00:25 +0000 (UTC) Message-ID: <4DBB18CB.2040203@FreeBSD.org> Date: Sat, 30 Apr 2011 00:00:11 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10 MIME-Version: 1.0 To: Super Bisquit References: In-Reply-To: X-Enigmail-Version: 1.1.2 OpenPGP: id=10C8A17A Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7D4EBFB9556E4B22E27115CA" Cc: gnome@freebsd.org, FreeBSD Hackers , alert.ntkiller@gmail.com Subject: Re: Bugzilla file reported. gnome developers want freebsd help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 20:00:38 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7D4EBFB9556E4B22E27115CA Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On 29.04.2011 23:30, Super Bisquit wrote: > https://bugzilla.gnome.org/show_bug.cgi?id=3D648430 >=20 > It doesn't seem that there was any before this willing to submit a bug > report about networking. >=20 > The gnome developers are willing to work with the freebsd project. Also there is approved GSoC Project "FreeBSD port of Network Manager", so i think things may be changed soon. --=20 WBR, Andrey V. Elsukov --------------enig7D4EBFB9556E4B22E27115CA 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.17 (FreeBSD) iQEcBAEBAgAGBQJNuxjPAAoJEAHF6gQQyKF6BZYIAKnTex7ZmbQiSdu1EUiTo8L2 qyDhBvNsLkHzfDLPAsnG6yATYiT6dxiUzV1onLZD8pBqgGrNMfZR6bf3KEqWdVzx 5KWV0mJbV/lc75DDKkQVKBvoowtB62m83OJ+INavynSZk6+RbJfA1bQdXI9+KhkP BpKqVqdnYQIiAdKuGReg5pTWunvy9dWmMisBfv6CUPr9BnJmpiCzqjN61cX1ktTN tPslCZKESEGZWDQpBQi1dNievItCGNYknBTaZBHQm93fRTrfJaidlllN8VaUqVCF JgFA+C0RbIfahdZ8m4I4wFPI7HsqNk7P0KK679i+ICg6S9EcR7+IUev04Oeb/KI= =xGyo -----END PGP SIGNATURE----- --------------enig7D4EBFB9556E4B22E27115CA-- From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 20:19:31 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E2E71065672; Fri, 29 Apr 2011 20:19:31 +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]) by mx1.freebsd.org (Postfix) with ESMTP id 2A98B8FC13; Fri, 29 Apr 2011 20:19:29 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.4/8.14.4) with ESMTP id p3TCiiOE080664; Fri, 29 Apr 2011 07:44:44 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.4/8.14.4/Submit) id p3TCiiuc080663; Fri, 29 Apr 2011 07:44:44 -0500 (CDT) (envelope-from brooks) Date: Fri, 29 Apr 2011 07:44:44 -0500 From: Brooks Davis To: Super Bisquit Message-ID: <20110429124444.GC79653@lor.one-eyed-alien.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ALfTUftag+2gvp1h" 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.2.6 (lor.one-eyed-alien.net [127.0.0.1]); Fri, 29 Apr 2011 07:44:44 -0500 (CDT) Cc: gnome@freebsd.org, FreeBSD Hackers Subject: Re: Bugzilla file reported. gnome developers want freebsd help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 20:19:31 -0000 --ALfTUftag+2gvp1h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 29, 2011 at 03:30:42PM -0400, Super Bisquit wrote: > https://bugzilla.gnome.org/show_bug.cgi?id=3D648430 >=20 > It doesn't seem that there was any before this willing to submit a bug > report about networking. >=20 > The gnome developers are willing to work with the freebsd project. FYI, we've got a Google Summer of Code student who is planning to work on porting NetworkManager. http://www.google-melange.com/gsoc/project/google/gsoc2011/kulakovad/4001 We're just getting spun up, but hopefully he will post more plans soon. -- Brooks --ALfTUftag+2gvp1h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFNurK7XY6L6fI4GtQRAkULAJ9H901TtGzNJTQxNgrD5fDrobtUVwCg4ik3 bVguDisBDZ59TNNIflEeEgY= =X/7s -----END PGP SIGNATURE----- --ALfTUftag+2gvp1h-- From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 20:21:22 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71948106564A for ; Fri, 29 Apr 2011 20:21:22 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 38A668FC1C for ; Fri, 29 Apr 2011 20:21:21 +0000 (UTC) Received: from SBHFISLREXT03 ([10.132.254.62]) by SCSFISLTC02 (8.14.3/8.14.3) with ESMTP id p3TKLLCQ001796; Fri, 29 Apr 2011 15:21:21 -0500 Received: from SBHFISLTCGW04.FNFIS.COM (Not Verified[10.132.248.123]) by SBHFISLREXT03 with MailMarshal (v6, 5, 4, 7535) id ; Fri, 29 Apr 2011 15:21:58 -0500 Received: from sbhfisltcgw02.FNFIS.COM ([10.132.248.122]) by SBHFISLTCGW04.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 15:21:21 -0500 Received: from dtwin ([10.132.254.135]) by sbhfisltcgw02.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 15:21:20 -0500 From: "Devin Teske" To: "'Mike Meyer'" , "'Paul Schenkeveld'" References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> <000301cc069f$edf8bd10$c9ea3730$@vicor.com> <20110429152423.11736f82@bhuda.mired.org> In-Reply-To: <20110429152423.11736f82@bhuda.mired.org> Date: Fri, 29 Apr 2011 13:21:17 -0700 Organization: Vicor, Inc. Message-ID: <003b01cc06ab$0002a790$0007f6b0$@vicor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQF9G/AhblsjpgWTQkLl7e1bA9mQcAGd6paiAm37VRoBMTEP4ZTpKvSg Content-Language: en-us X-OriginalArrivalTime: 29 Apr 2011 20:21:20.0488 (UTC) FILETIME=[00865680:01CC06AB] Cc: 'FreeBSD Hackers' Subject: RE: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 20:21:22 -0000 > -----Original Message----- > From: Mike Meyer [mailto:mwm@mired.org] > Sent: Friday, April 29, 2011 12:24 PM > To: Devin Teske > Cc: 'FreeBSD Hackers' > Subject: Re: [RELEASE] New Boot-Loader Menu > > On Fri, 29 Apr 2011 12:02:03 -0700 > "Devin Teske" wrote: > > > -----Original Message----- > > > From: Mike Meyer [mailto:mwm@mired.org] I'd like to revisit the > > > numbers vs. letters for menu options. IIRC (and I may > > not), > > > an earlier version used letters for the menu options, and people > > > objected to > > that > > > change. > > > > Looking at the CVS history of the Forth code that renders the menu, > > I'm > > noticing: > > > > If there was an earlier version of the menu that used letters, I'm not > > seeing it in CVS. > > I was referring to your code, not the historical FreeBSD code. Didn't you originally > propose using letters, not numbers, to toggle the boot options? If not, then > possibly I'm remembering another proposal. You're recalling a response to the thread that I started on March 28th, 2011 (last month): THREAD-HEAD: http://lists.freebsd.org/pipermail/freebsd-hackers/2011-March/034824.html The "letters not numbers" post that you're recalling was by Paul S. (below): http://lists.freebsd.org/pipermail/freebsd-hackers/2011-March/034830.html Although Paul makes a point that the letters would be helpful, his complaint about the numbers being changed is a red-herring (he saw the unreleased mock-up image of my boot-loader -- in the thread-head URL above -- presenting different numbers and complained that if the numbers change that sysadmins would be confused). However, the reality is that [a] the final release indeed matches the numbers with the existing boot loader and [b] the numbers have not changed in 7 years). Paul, ... supporting evidence to show that the numbers (1-7) have never changed since their initial commit to CVS on May 30th, 2003 (see the "beastie-menu" forth word in version 1.1 of beastie.4th circa RELENG_5_0): http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/forth/beastie.4th The case is merely that Paul would like to see this additional feature added (letters as mnemonics). I couldn't find any claims that any previous version (either of my code or official FreeBSD code) ever supported it in the past. So, I think that the grand-total comes to 5 people now that have requested hot-keys for the single-user and verbose menu items: Paul S. (msg #034830) Zhihao Y. (msg #034831) Damien F. (msg #034841) Yourself (Mike M.) (msg #035192 & msg #035197) and Myself (Devin T. msg #035195) Let's see if we can't get that list a little higher. Keep in-mind, the proposal (at least for right now) is to have me extend my code to bold the "S" in "Single User", bold the "V" in "Verbose", and accept the S/V key as toggles for these features, all the while maintaining the current number scheme. NOTE: I'm going to wait a couple weeks before starting on this, as I've currently got a couple of other companies evaluating the boot loader in its current form and would like their feedback before moving forward on the next revision. > > > > In particular, there was a study done around '80 (I tried to find it > > > but > > couldn't; I > > > know of someone who can probably provide a reference if someone > > > really wants > > > it) that showed that menu selection with letters assigned > > > mnemonically are easiest for users to memorize. > > > > I can believe that quite easily. However, currently the boot menu does > > not support such letters. I think this new loader menu is the perfect > > place to implement them. > > This seemed like a good time to change it if we were going to to me. I couldn't agree more. -- Devin > > > On another note, I have one other change that I'd like to get in... I > > noticed that (in CVS) the menu currently blanks-out option #2 if > > booting on a system where ACPI is disabled or unavailable. In my boot > > loader, I'd like to display "ACPI Support: N/A" rather than simply blanking out > the menu item. > > That would certainly make the numbers make more sense. > > Thanks, > -- > Mike Meyer > http://www.mired.org/consulting.html > Independent Software developer/SCM consultant, email for more information. > > O< ascii ribbon campaign - stop html mail - www.asciiribbon.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. _____________ From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 20:40:40 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFFA61065672; Fri, 29 Apr 2011 20:40:40 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 816C98FC18; Fri, 29 Apr 2011 20:40:40 +0000 (UTC) Received: by vws18 with SMTP id 18so4045788vws.13 for ; Fri, 29 Apr 2011 13:40:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JvLPGvNwHb0HIrRy/Ml+imCwOOnFwGDNdkVEz+D/fYo=; b=urHYGZ4yLKuMXU7P6wQPYmy3yP+9CvOf0LLWGkORGg44xDTfeBlZyl3TgHd25xk8uI 4lpKhIOTI0UBmooPTKQ73gE0AoISGQElsmvhtfARZNuDGJCYzx3vVPcbTbKlRfJImNst huoavVlWhwUnzIoxPg2+q4bb5QPrYwKFqkHas= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=apwsI8Ozmk7r7KEomLLjst38d8B2s8kt2rdCrRcZvHmaO6atx4lMfHt8/y1/GM4thJ g8Ezdsg1u9Y8SvwOLtvzIxkw9zE1sQ1KBpk/KOTSuN7R+GceK/MW3nznaFeh47mOzKqa QOarVhm9B+vKsWMMqwZaBLX5AgvvzWlpbO+lE= MIME-Version: 1.0 Received: by 10.52.100.10 with SMTP id eu10mr476669vdb.208.1304109639703; Fri, 29 Apr 2011 13:40:39 -0700 (PDT) Received: by 10.220.58.5 with HTTP; Fri, 29 Apr 2011 13:40:39 -0700 (PDT) In-Reply-To: <4DBB18CB.2040203@FreeBSD.org> References: <4DBB18CB.2040203@FreeBSD.org> Date: Fri, 29 Apr 2011 16:40:39 -0400 Message-ID: From: Super Bisquit To: "Andrey V. Elsukov" Content-Type: text/plain; charset=ISO-8859-1 Cc: gnome@freebsd.org, FreeBSD Hackers , alert.ntkiller@gmail.com, desktop-devel-list@gnome.org Subject: Re: Bugzilla file reported. gnome developers want freebsd help X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 20:40:41 -0000 Let the individual know that the gnome developers are willing to work with him. For gnome desktop devel, here's the link and project: http://www.google-melange.com/gsoc/project/google/gsoc2011/kulakovad/4001 On 4/29/11, Andrey V. Elsukov wrote: > On 29.04.2011 23:30, Super Bisquit wrote: >> https://bugzilla.gnome.org/show_bug.cgi?id=648430 >> >> It doesn't seem that there was any before this willing to submit a bug >> report about networking. >> >> The gnome developers are willing to work with the freebsd project. > > Also there is approved GSoC Project "FreeBSD port of Network Manager", > so i think things may be changed soon. > > -- > WBR, Andrey V. Elsukov > > From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 20:42:11 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6981E106564A for ; Fri, 29 Apr 2011 20:42:11 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 23A798FC18 for ; Fri, 29 Apr 2011 20:42:10 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAEEiu02DaFvO/2dsb2JhbACEUKI4pi6NApEEgSmDVIEBBI5ohniHPg X-IronPort-AV: E=Sophos;i="4.64,289,1301889600"; d="scan'208";a="119124297" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 29 Apr 2011 16:42:10 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 6E0A9793A7 for ; Fri, 29 Apr 2011 16:42:10 -0400 (EDT) Date: Fri, 29 Apr 2011 16:42:10 -0400 (EDT) From: Rick Macklem To: freebsd-hackers Message-ID: <384344635.793652.1304109730387.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Subject: should I use a SYSCTL_STRUCT? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 20:42:11 -0000 Hi, I am at the point where I need to fix the "-z" option of nfsstat. Currently the stats are acquired/zeroed for the old NFS subsystem via sysctl. The setup in the kernel is: SYSCTL_STRUCT(_vfs_nfs, NFS_NFSSTATS, nfsstats, CTLFLAG_RW, &nfsstats, nfsstats, "S,nfsstats"); The new NFS subsystem currently gets the contents of the structure via a flag on nfssvc(2). So, I could either: - add another flag for nfssvc(2) to zero the structure OR - switch the new NFS subsystem over to using a SYSCTL_STRUCT() like the above. Which do you think would be preferable? Thanks in advance for any info, rick ps: I got completely lost on the SYSCTL thread in Jan. and would rather not start another one like it:-) From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 22:37:23 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C16F2106564A for ; Fri, 29 Apr 2011 22:37:23 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 70B718FC08 for ; Fri, 29 Apr 2011 22:37:22 +0000 (UTC) Received: by vws18 with SMTP id 18so4125200vws.13 for ; Fri, 29 Apr 2011 15:37:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fYVnc1VtvNeA98bm7e+5AgTuC/d3UKmtyy3tmeUeMgQ=; b=li9JzMRtclXFVvY+gW1KXTmDhLPWvIW4EjSEDnj/2bXeCjtpTdm9AQOg0u0FJmRUAB RAFmWy4eVaA7R2dx1FnKu5cFXONhmptGRZaPCwa0AzMFiBIdB30Z0Uf0ZX92Xx9JWf8/ QzcC3fOH9lvYG4w8vMCl/wW4NrpHI+ZRXNZhg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DP1IHF5Qju9FXfIPGshWcVWXKkvRGzWW8ilV/bHbIw9RyBb029/BU930iWPIcSm8MB kWTHnkGlGY2nGu3HZf3f7x3kzqh24oMHlo+nUwuhU+H4S+Kiz+n+01dET9UMe6myVEa0 7rSjWy7MG7TpPdvn3zPsGf2tuM6BdLUCPolDo= MIME-Version: 1.0 Received: by 10.220.112.138 with SMTP id w10mr854070vcp.46.1304116642281; Fri, 29 Apr 2011 15:37:22 -0700 (PDT) Received: by 10.220.199.130 with HTTP; Fri, 29 Apr 2011 15:37:22 -0700 (PDT) In-Reply-To: <20110429.160309.656.1@DEV> References: <20110429.160309.656.1@DEV> Date: Fri, 29 Apr 2011 15:37:22 -0700 Message-ID: From: Garrett Cooper To: rank1seeker@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Look of boot2, on HDD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 22:37:23 -0000 2011/4/29 : > /boot/boot2 =A0 =A0STAGE 2 bootstrap file > Understands the FreeBSD file system enough, to find files on it, and can = provide a simple interface to choose the kernel or loader to run. > > Once sys is fully booted, HDD is 'ada0'. > However, STAGE 2, sees it, as a 'ad4', at boot process, which is same see= n, by booted sys, when I turn off AHCI. > > So, here is the riddle ... > On fully booted sys, how do I query STAGE 2, to tell me, how it'll see, m= y 'ada0' HDD? This is a very interesting catch: /usr/src/sys/boot/pc98/boot2/boot2.c:static const char *const dev_nm[NDEV] =3D {"ad", "da", "fd"}; /usr/src/sys/boot/i386/boot2/boot2.c:static const char *const dev_nm[NDEV] =3D {"ad", "da", "fd"}; It probably will be a no-op soon because of some of the compatibility changes Alex made, but still a potential point of confusion nonetheless. Thanks! -Garrett From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 23:09:18 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E83C106566C for ; Fri, 29 Apr 2011 23:09:18 +0000 (UTC) (envelope-from olivier@gid0.org) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E22498FC1A for ; Fri, 29 Apr 2011 23:09:17 +0000 (UTC) Received: by pwj8 with SMTP id 8so2578789pwj.13 for ; Fri, 29 Apr 2011 16:09:17 -0700 (PDT) Received: by 10.68.41.9 with SMTP id b9mr5995292pbl.436.1304118556852; Fri, 29 Apr 2011 16:09:16 -0700 (PDT) References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <002001cc06a1$f8a18ce0$e9e4a6a0$@vicor.com> From: Olivier SMEDTS In-Reply-To: <002001cc06a1$f8a18ce0$e9e4a6a0$@vicor.com> Mime-Version: 1.0 (iPhone Mail 8G4) Date: Sat, 30 Apr 2011 01:08:57 +0200 Message-ID: <-1333653504495558701@unknownmsgid> To: Devin Teske Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 23:09:18 -0000 Le 29 avr. 2011 =E0 21:17, Devin Teske a =E9crit : >> -----Original Message----- >> From: Freddie Cash [mailto:fjwcash@gmail.com] >> Sent: Friday, April 29, 2011 11:20 AM >> To: Devin Teske >> Cc: FreeBSD Hackers >> Subject: Re: [RELEASE] New Boot-Loader Menu >> >> Very nice and functional, without adding a lot of extra verbosity or ste= ps. I really >> appreciated the clean install via binary package. >> Well done. >> >> Only question I have is whether it's possible to use the Beastie ASCII i= mage >> instead of the pointy-eared blob? The beastie.4th file is still present= under /boot, >> but I don't know how to hook it into the new menu. > > Glad you asked. This couldn't be easier. > > Open up `/boot/menu.rc' and look for the following lines (LINE 9-10): > > \ Customizations > set logo=3D"orb" > > Feel free to play with any of the following drop-in replacements: > > set logo=3D"beastie" > set logo=3D"beastiebw" > set logo=3D"fbsdbw" > set logo=3D"orb" > set logo=3D"orbbw" Would it be possible to support the curent loader settings present in /boot/loader.conf ? I've got something like : loader_logo=3D"beastie" autoboot_delay=3D"0" And while the pre-menu delay of 2 seconds is great, is it possible to turn it off or adjust it ? Thanks ! > Simply deleting the line or comment it out (by adding "\ " -- backslash-s= pace -- to the beginning of the line) is equivalent to setting logo to "bea= stie". Here's a short explanation of each value: > > NAME DESCRIPTION > beastie Color ``Helper Daemon'' mascot (19 rows x 34 columns) > beastiebw B/W ``Helper Daemon'' mascot (19 rows x 34 columns) > fbsdbw "FreeBSD" logo in B/W (13 rows x 21 columns) > orb Color ``Orb'' mascot (15 rows x 30 columns) > orbbw B/W ``Orb'' mascot (15 rows x 30 columns) > > I'm not sure what you meant by "Beastie ASCII" image, but I think you're = either looking for "beastie" or "fbsdbw". > > You should have to, but if you need to, you can add: > > set logoX=3DX > set logoY=3DY > > to force the row/column placement of beastie. > -- > Devin > >> >> -- >> Freddie Cash >> fjwcash@gmail.com > > _____________ > > The information contained in this message is proprietary and/or confident= ial. 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 awa= re that any message addressed to our domain is subject to archiving and rev= iew by persons other than the intended recipient. Thank you. > _____________ > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 23:55:16 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 818E9106566B for ; Fri, 29 Apr 2011 23:55:16 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 44D7F8FC12 for ; Fri, 29 Apr 2011 23:55:15 +0000 (UTC) Received: from SBHFISLREXT03 ([10.132.254.62]) by SCSFISLTC01 (8.14.3/8.14.3) with ESMTP id p3TNtFIo026348; Fri, 29 Apr 2011 18:55:15 -0500 Received: from sbhfisltcgw01.FNFIS.COM (Not Verified[10.132.248.121]) by SBHFISLREXT03 with MailMarshal (v6, 5, 4, 7535) id ; Fri, 29 Apr 2011 18:55:52 -0500 Received: from sbhfisltcgw02.FNFIS.COM ([10.132.248.122]) by sbhfisltcgw01.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 18:55:14 -0500 Received: from dtwin ([10.132.254.135]) by sbhfisltcgw02.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 18:55:14 -0500 From: "Devin Teske" To: "'Alexander Leidinger'" References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> <000301cc069f$edf8bd10$c9ea3730$@vicor.com> <20110429223355.00004ab0@unknown> In-Reply-To: <20110429223355.00004ab0@unknown> Date: Fri, 29 Apr 2011 16:55:12 -0700 Organization: Vicor, Inc. Message-ID: <007201cc06c8$e1d99260$a58cb720$@vicor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQF9G/AhblsjpgWTQkLl7e1bA9mQcAGd6paiAm37VRoBdxPBBZTnFYIA Content-Language: en-us X-OriginalArrivalTime: 29 Apr 2011 23:55:14.0515 (UTC) FILETIME=[E2337230:01CC06C8] Cc: 'FreeBSD Hackers' , 'Mike Meyer' Subject: RE: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 23:55:16 -0000 > -----Original Message----- > From: Alexander Leidinger [mailto:Alexander@Leidinger.net] > Sent: Friday, April 29, 2011 1:34 PM > To: Devin Teske > Cc: 'Mike Meyer'; 'FreeBSD Hackers' > Subject: Re: [RELEASE] New Boot-Loader Menu >=20 > On Fri, 29 Apr 2011 12:02:03 -0700 "Devin Teske" > wrote: >=20 > > I was thinking that what we ought to do is support *both* numbers > > *and* letters. >=20 > Sounds good to me. >=20 > > I envision the menuitem numbers remaining unchanged (1-7), allowing > > those familiar with the numbers to use them. > > > > However, as for the letters, I'm thinking that we *BOLD* the mnemonic > > in the menuitem. For example (showing bolded items between asterisks): > > > > 1. Boot *[ENTER]* > > 2. *A*CPI Support: Enabled > > 3. Boot Safe Mode: NO > > 4. Boot *S*ingle User: NO > > 5. Boot *V*erbose: NO > > 6. *Esc*ape to loader prompt > > 7. *R*eboot > > > > This should indicate to the user, for example if they see that the "V" > > in "Verbose" is bolded, that they can press that key to activate that > > menuitem. >=20 Your below points are all valid arguments. However, I think they are a bit reaching. The types of people that know what it means to boot into Single-User and/or Verbose mode would not be prone to thinking in those ways. And, even if they were, let's look at the consequences for each: > Presented like this a naive first interpretion could be that the letters = have to be > entered as upper-case. I do not think someone wants to press shift there.= .. > Scenario: Na=EFve User presses Shift-V. Nothing happens. They then press "v" ... the = menu toggles to "YES". They press ENTER. Success -- the na=EFve user has managed= to boot with the desired options. > Having the characters in bold but the numbers not could also let someone = think > that only the characters matter. >=20 Scenario: Na=EFve user thinks that only the letters matter, and the only bold items o= n the menu are "[ENTER]", "S", and "V". Na=EFve user is left wondering how to act= ivate menuitems 2, 3, 6, and 7 for which there are no bolded letters. Na=EFve use= r never figures out that the numbers are usable and eventually presses ENTER. The machine boots. Ok... you got me on this one ... this hypothetical [extremely] na=EFve user= may not figure out how to use options 2, 3, 6, and 7, and thus cannot disable A= CPI, cannot boot in Safe Mode (disabling both ACPI and APIC, etc.), nor escape t= o the loader prompt, nor reboot (assuming they don't know how the three-finger-so= lute or where the power button is). My concession to this user would be to bold the numbers to the left of each menuitem. The user would have to be beyond na=EFvet=E9 if they couldn't fig= ure it out with bold numbers, IMHO. > Having a text which tells that the numbers and lower-case characters work= for > chosing something, may be a solution here. Another solution is maybe > 1/[ENTER]. Boot 2/a. ACPI Support... > ... > but I have to admit that the second solution is ugly. > A third solution could be to have the numbers and the characters in bold. >=20 Yeah, that's no good. Too ugly. I'm still leaning toward just making the "V" in "Verbose" and "S" in "Single User" bolded. --=20 Devin > Bye, > Alexander. >=20 > -- > http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 _____________ 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-hackers@FreeBSD.ORG Sat Apr 30 00:11:52 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16CB5106564A for ; Sat, 30 Apr 2011 00:11:52 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id CEFB18FC0C for ; Sat, 30 Apr 2011 00:11:51 +0000 (UTC) Received: from sbhfislrext01.fnfis.com ([192.168.249.167]) by SCSFISLTC02 (8.14.3/8.14.3) with ESMTP id p3U0Bpqw019765; Fri, 29 Apr 2011 19:11:51 -0500 Received: from sbhfisltcgw02.FNFIS.COM (Not Verified[10.132.248.122]) by sbhfislrext01.fnfis.com with MailMarshal (v6, 5, 4, 7535) id ; Fri, 29 Apr 2011 19:11:51 -0500 Received: from sbhfisltcgw01.FNFIS.COM ([10.132.248.121]) by sbhfisltcgw02.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 19:11:51 -0500 Received: from dtwin ([10.132.254.135]) by sbhfisltcgw01.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 29 Apr 2011 19:11:50 -0500 From: "Devin Teske" To: "'Olivier SMEDTS'" References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <002001cc06a1$f8a18ce0$e9e4a6a0$@vicor.com> <-1333653504495558701@unknownmsgid> In-Reply-To: <-1333653504495558701@unknownmsgid> Date: Fri, 29 Apr 2011 17:11:48 -0700 Organization: Vicor, Inc. Message-ID: <007401cc06cb$33914d30$9ab3e790$@vicor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQF9G/AhblsjpgWTQkLl7e1bA9mQcAIRP0ELAbe4k5UAbO/P1pTxqrlw Content-Language: en-us X-OriginalArrivalTime: 30 Apr 2011 00:11:50.0318 (UTC) FILETIME=[33BEECE0:01CC06CB] Cc: 'FreeBSD Hackers' Subject: RE: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 00:11:52 -0000 > -----Original Message----- > From: Olivier SMEDTS [mailto:olivier@gid0.org] > Sent: Friday, April 29, 2011 4:09 PM > To: Devin Teske > Cc: Freddie Cash; FreeBSD Hackers > Subject: Re: [RELEASE] New Boot-Loader Menu >=20 > Le 29 avr. 2011 =E0 21:17, Devin Teske a =E9crit : >=20 > >> -----Original Message----- > >> From: Freddie Cash [mailto:fjwcash@gmail.com] > >> Sent: Friday, April 29, 2011 11:20 AM > >> To: Devin Teske > >> Cc: FreeBSD Hackers > >> Subject: Re: [RELEASE] New Boot-Loader Menu > >> > >> Very nice and functional, without adding a lot of extra verbosity or > >> steps. I really appreciated the clean install via binary package. > >> Well done. > >> > >> Only question I have is whether it's possible to use the Beastie > >> ASCII image instead of the pointy-eared blob? The beastie.4th file > >> is still present under /boot, but I don't know how to hook it into the= new > menu. > > > > Glad you asked. This couldn't be easier. > > > > Open up `/boot/menu.rc' and look for the following lines (LINE 9-10): > > > > \ Customizations > > set logo=3D"orb" > > > > Feel free to play with any of the following drop-in replacements: > > > > set logo=3D"beastie" > > set logo=3D"beastiebw" > > set logo=3D"fbsdbw" > > set logo=3D"orb" > > set logo=3D"orbbw" >=20 > Would it be possible to support the curent loader settings present in > /boot/loader.conf ? I've got something like : > loader_logo=3D"beastie" > autoboot_delay=3D"0" >=20 Yeah, that's definitely possible. The new code already supports /boot/loader.conf, however I don't support loader_logo in that way (you'd h= ave to use "logo=3D" instead of "loader_logo=3D" and you'd have to remove the "= set logo=3D" line from /boot/menu.rc). I'll have to make the following modifications in the next version so that y= ou can use loader_logo from /boot/loader.conf: 1. Change the default logo in /boot/beastie.4th from "beastie" to "orb" 2. Change /boot/menu.rc to remove the line: set logo=3D"orb" 3. Change /boot/beastie.4th to read the "loader_logo" environment variable instead of "logo" > And while the pre-menu delay of 2 seconds is great, is it possible to tur= n it off or > adjust it ? > Right now, if you want to disable the 2 second delay, open up /boot/loader.= rc and change the following line: set dc_seconds=3D2 to: set dc_seconds=3D0 In the next release, I'll rewrite it so that you add something to /boot/loader.conf to disable the delay. --=20 Devin > Thanks ! >=20 > > Simply deleting the line or comment it out (by adding "\ " -- backslash-space -- > to the beginning of the line) is equivalent to setting logo to "beastie". Here's a > short explanation of each value: > > > > NAME DESCRIPTION > > beastie Color ``Helper Daemon'' mascot (19 rows x 34 columns) > > beastiebw B/W ``Helper Daemon'' mascot (19 rows x 34 columns) > > fbsdbw "FreeBSD" logo in B/W (13 rows x 21 columns) > > orb Color ``Orb'' mascot (15 rows x 30 columns) > > orbbw B/W ``Orb'' mascot (15 rows x 30 columns) > > > > I'm not sure what you meant by "Beastie ASCII" image, but I think you're either > looking for "beastie" or "fbsdbw". > > > > You should have to, but if you need to, you can add: > > > > set logoX=3DX > > set logoY=3DY > > > > to force the row/column placement of beastie. > > -- > > Devin > > > >> > >> -- > >> Freddie Cash > >> fjwcash@gmail.com > > > > _____________ > > > > 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 (i= ii) notify > the sender immediately. In addition, please be aware that any message > addressed to our domain is subject to archiving and review by persons oth= er than > the intended recipient. Thank you. > > _____________ > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" _____________ 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-hackers@FreeBSD.ORG Fri Apr 29 20:19:35 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDFED106566C for ; Fri, 29 Apr 2011 20:19:35 +0000 (UTC) (envelope-from lgj@usenix.org) Received: from lonestar.usenix.org (lonestar.usenix.org [131.106.3.102]) by mx1.freebsd.org (Postfix) with ESMTP id C7F538FC0C for ; Fri, 29 Apr 2011 20:19:35 +0000 (UTC) Received: from negroni.usenix.org (negroni.usenix.org [131.106.3.145]) (authenticated bits=0) by lonestar.usenix.org (8.14.2/8.14.2) with ESMTP id p3TKIl3d027386 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 29 Apr 2011 13:19:35 -0700 (PDT) From: Lionel Garth Jones Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 29 Apr 2011 13:19:35 -0700 Message-Id: To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-DCC-USENIX-Metrics: lonestar; whitelist X-Spam-Status: No, score=0.7 required=6.0 tests=ALL_TRUSTED, FH_DATE_PAST_20XX autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lonestar X-Mailman-Approved-At: Sat, 30 Apr 2011 02:02:05 +0000 Subject: 2011 USENIX Federated Conferences Week Registration Now Open X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 20:19:35 -0000 Join us in Portland, OR, June 14-17, 2011, for the 2011 USENIX Federated Conferences Week. http://www.usenix.org/fcw11/proga We know that keeping up with technology can be costly and time-consuming. USENIX Federated Conferences Week makes it easier than ever to stay ahead of the game. By attending FCW '11, you'll get: - Cost-Effective Learning FCW '11 offers the unique opportunity to meet and learn from top researchers, practitioners, and authors all in one place, at one time. It's the most cost-effective and timely way to gain insight into the latest trends, rather than spending months reading books and articles, or browsing Web sites. - Information and Connections to Keep Your Career on Track Maintaining your career path is especially challenging when facing today's IT realities. Attending FCW '11 can make this daunting task easier by offering an in-depth look into many of the hottest topics comprising the industry today. Your access to leading researchers and industry experts will not only provide answers to your most difficult questions, but also will help you build lasting connections across multiple disciplines. Don't miss out on this opportunity to create the conference experience that meets your unique needs. USENIX Federated Conferences Week includes: - HotCloud '11: 3rd USENIX Workshop on Hot Topics in Cloud Computing Tuesday-Wednesday, June 14-15, 2011 http://www.usenix.org/events/hotcloud11 HotCloud '11 will discuss challenges in the design, implementation, and deployment of cloud computing. It will be a forum for academics and practitioners to share their experiences and identify emerging trends. - HotStorage '11: 3rd USENIX Workshop on Hot Topics in Storage and File Systems Tuesday, June 14, 2011 http://www.usenix.org/events/hotstorage11 HotStorage '11 will discuss the new opportunities presented by the increase in the volume and variety of digital data, "big data," the proliferation of consumer-electronics storage devices, and more. - WIOV '11: 3rd Workshop on I/O Virtualization Tuesday, June 14, 2011 http://www.usenix.org/events/wiov11 The focus of WIOV '11 is on the interplay of I/O with virtualization and cloud technologies. Our goal is to provide a forum to discuss the impact and challenges of I/O virtualization along multiple dimensions. - Tutorial: Securing Linux Servers Tuesday, June 14, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#t1 This class for Linux sysadmins and security managers shows you how to maintain a strong security posture by minimizing risks through careful configuration and proper use of Linux tools and services. - USENIX ATC '11: 2011 USENIX Annual Technical Conference Wednesday-Friday, June 15-17, 2011 http://www.usenix.org/events/atc11 USENIX ATC '11 offers you cutting-edge systems research and insights into a variety of topics--virtualization, cloud computing, storage, security, distributed systems, personal devices, scheduling, and more. - WebApps '11: 2nd USENIX Conference on Web Application Development Wednesday-Thursday, June 15-16, 2011 http://www.usenix.org/events/webapps11 WebApps '11 is designed to bring together experts in all aspects of developing and deploying Web applications. The program includes refereed papers, posters, invited talks, and a panel. - Tutorial: SELinux (Security-Enhanced Linux) Wednesday, June 15, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#w1 Learn to work with SELinux: how to determine if SELinux is blocking an application and how to adjust policy to move beyond problems. This class is intended for Linux sysadmins and security managers. - Tutorial: VMware vCloud Overview and Design Considerations Wednesday, June 15, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#w2 Sysadmins and architects, get the knowledge you need to deploy a VMware cloud for use as an enterprise private cloud by learning how to implement and manage VMware vCloud technologies. - Tutorial: Linux Performance Tuning Thursday, June 16, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#r1 Intended for intermediate and advanced sysadmins, this class will cover the tools that can be used to monitor and analyze a Linux system, plus key tuning parameters to optimize Linux for server applications. - Tutorial: SANS Security 464: Hacker Detection for Systems Administrators Thursday-Friday, June 16-17, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#r2 This 2-day course is designed to help sysadmins better understand what is required by security teams and auditors and to turn into the human sensors for malicious activity. - Tutorial: Introduction to Automating System Administration with Cfengine 3 Friday, June 17, 2011 http://www.usenix.org/events/fcw11/training/tutonefile.html#f1 This is your opportunity to get a thorough grounding in automated system administration and configuration using Cfengine v3, and the ability to implement configuration policies on your systems. Whether you are interested in the latest systems computing breakthroughs or want to get the low-down on Web application development, this week in June will have everything you need to stay ahead of the curve. See you in Portland! From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 29 20:34:13 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F22A91065673 for ; Fri, 29 Apr 2011 20:34:13 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id AE4868FC0A for ; Fri, 29 Apr 2011 20:34:13 +0000 (UTC) Received: from outgoing.leidinger.net (p5B154887.dip.t-dialin.net [91.21.72.135]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 69DDF84400D; Fri, 29 Apr 2011 22:34:00 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.2.110]) by outgoing.leidinger.net (Postfix) with ESMTP id B374F1184; Fri, 29 Apr 2011 22:33:57 +0200 (CEST) Date: Fri, 29 Apr 2011 22:33:55 +0200 From: Alexander Leidinger To: "Devin Teske" Message-ID: <20110429223355.00004ab0@unknown> In-Reply-To: <000301cc069f$edf8bd10$c9ea3730$@vicor.com> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> <000301cc069f$edf8bd10$c9ea3730$@vicor.com> X-Mailer: Claws Mail 3.7.8cvs47 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 69DDF84400D.AF804 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1304714040.65065@PCNNobLe+g1bwDwVL2P7Bw X-EBL-Spam-Status: No X-Mailman-Approved-At: Sat, 30 Apr 2011 02:09:24 +0000 Cc: 'FreeBSD Hackers' , 'Mike Meyer' Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 20:34:14 -0000 On Fri, 29 Apr 2011 12:02:03 -0700 "Devin Teske" wrote: > I was thinking that what we ought to do is support *both* numbers > *and* letters. Sounds good to me. > I envision the menuitem numbers remaining unchanged (1-7), allowing > those familiar with the numbers to use them. > > However, as for the letters, I'm thinking that we *BOLD* the mnemonic > in the menuitem. For example (showing bolded items between asterisks): > > 1. Boot *[ENTER]* > 2. *A*CPI Support: Enabled > 3. Boot Safe Mode: NO > 4. Boot *S*ingle User: NO > 5. Boot *V*erbose: NO > 6. *Esc*ape to loader prompt > 7. *R*eboot > > This should indicate to the user, for example if they see that the > "V" in "Verbose" is bolded, that they can press that key to activate > that menuitem. Presented like this a naive first interpretion could be that the letters have to be entered as upper-case. I do not think someone wants to press shift there... Having the characters in bold but the numbers not could also let someone think that only the characters matter. Having a text which tells that the numbers and lower-case characters work for chosing something, may be a solution here. Another solution is maybe 1/[ENTER]. Boot 2/a. ACPI Support... ... but I have to admit that the second solution is ugly. A third solution could be to have the numbers and the characters in bold. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 03:34:24 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11D0D106566C for ; Sat, 30 Apr 2011 03:34:24 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id C5D638FC14 for ; Sat, 30 Apr 2011 03:34:23 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.4/8.14.4) with ESMTP id p3U3YMFn097185; Fri, 29 Apr 2011 21:34:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.4/8.14.4/Submit) with ESMTP id p3U3YM6v097182; Fri, 29 Apr 2011 21:34:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 29 Apr 2011 21:34:22 -0600 (MDT) From: Warren Block To: Devin Teske In-Reply-To: <007201cc06c8$e1d99260$a58cb720$@vicor.com> Message-ID: References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> <000301cc069f$edf8bd10$c9ea3730$@vicor.com> <20110429223355.00004ab0@unknown> <007201cc06c8$e1d99260$a58cb720$@vicor.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.2.7 (wonkity.com [127.0.0.1]); Fri, 29 Apr 2011 21:34:22 -0600 (MDT) Cc: 'Alexander Leidinger' , 'Mike Meyer' , 'FreeBSD Hackers' Subject: RE: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 03:34:24 -0000 On Fri, 29 Apr 2011, Devin Teske wrote: > I'm still leaning toward just making the "V" in "Verbose" and "S" in "Single > User" bolded. Why not just underline hotkey characters? That's already a well-known standard in lots of places. From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 03:37:09 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 56993106564A for ; Sat, 30 Apr 2011 03:37:09 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 65-241-43-5.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 9C9C214DAA5; Sat, 30 Apr 2011 03:37:07 +0000 (UTC) Message-ID: <4DBB83E2.5060403@FreeBSD.org> Date: Fri, 29 Apr 2011 20:37:06 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110429 Thunderbird/3.1.10 MIME-Version: 1.0 To: Warren Block References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> <000301cc069f$edf8bd10$c9ea3730$@vicor.com> <20110429223355.00004ab0@unknown> <007201cc06c8$e1d99260$a58cb720$@vicor.com> In-Reply-To: X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 'Alexander Leidinger' , 'Mike Meyer' , Devin Teske , 'FreeBSD Hackers' Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 03:37:09 -0000 On 04/29/2011 20:34, Warren Block wrote: > On Fri, 29 Apr 2011, Devin Teske wrote: > >> I'm still leaning toward just making the "V" in "Verbose" and "S" in >> "Single >> User" bolded. > > Why not just underline hotkey characters? That's already a well-known > standard in lots of places. Agreed, that's a much more standard UI. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 05:27:49 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A37FD106564A for ; Sat, 30 Apr 2011 05:27:49 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 42B298FC16 for ; Sat, 30 Apr 2011 05:27:49 +0000 (UTC) Received: by qwc9 with SMTP id 9so2533730qwc.13 for ; Fri, 29 Apr 2011 22:27:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Y7zFTuWSvV0BUgzYkxw8eWIbIp/B/Vc/CjAtLRO4/7c=; b=Z4ur5/gbAUyV2EyM7r6ZqsVdtle+JEqTyYo+Lyi/poTVrNTDYXXfAgo0URvRiXCVEP jg2oIRldGisTISLoWfNhJX5zbHy8TQSIbP/b4zijWCN/3rk/StgNG9o4JFF1b9HsPkN1 DtkT41JwRDKEU42N7Le7hrmD74PxDZuX0CqtA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=VVHMXzi1b/BJg1AWFK06jmVOSf+J8eZHsPIzAmthGeN24RpqLDKdXzMmBgGmKlVmso Y/jlh+i+skNmrEUdHcqMSAYhz+s+uTPnm5uSfJeI34mTgsGSzDTLZ64KRb3o10CFyCxa 4j+H/aZi5jqJAPnjKoQ1qwTVMHnxEopFPVgjc= MIME-Version: 1.0 Received: by 10.229.102.165 with SMTP id g37mr4477531qco.120.1304141268604; Fri, 29 Apr 2011 22:27:48 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.229.95.140 with HTTP; Fri, 29 Apr 2011 22:27:48 -0700 (PDT) In-Reply-To: <4DBB83E2.5060403@FreeBSD.org> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> <000301cc069f$edf8bd10$c9ea3730$@vicor.com> <20110429223355.00004ab0@unknown> <007201cc06c8$e1d99260$a58cb720$@vicor.com> <4DBB83E2.5060403@FreeBSD.org> Date: Fri, 29 Apr 2011 22:27:48 -0700 X-Google-Sender-Auth: YWwNiWrGsZVkINXBbQcLCQXvTd4 Message-ID: From: Artem Belevich To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: Alexander Leidinger , Mike Meyer , Devin Teske , FreeBSD Hackers Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 05:27:49 -0000 On Fri, Apr 29, 2011 at 8:37 PM, Doug Barton wrote: > On 04/29/2011 20:34, Warren Block wrote: >> >> On Fri, 29 Apr 2011, Devin Teske wrote: >> >>> I'm still leaning toward just making the "V" in "Verbose" and "S" in >>> "Single >>> User" bolded. >> >> Why not just underline hotkey characters? That's already a well-known >> standard in lots of places. > > Agreed, that's a much more standard UI. I hope that works for serial console. VT100 may be a reasonable default in that case, but it would be good to make sure that menu works even on a dumb terminal. Perhaps we should put 'key' letter in brackets then? --Artem From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 06:51:57 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81E13106564A for ; Sat, 30 Apr 2011 06:51:57 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3CC768FC0A for ; Sat, 30 Apr 2011 06:51:57 +0000 (UTC) Received: from outgoing.leidinger.net (p5B1548CE.dip.t-dialin.net [91.21.72.206]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id D731F844016; Sat, 30 Apr 2011 08:51:42 +0200 (CEST) Received: from unknown (IO.Leidinger.net [192.168.2.110]) by outgoing.leidinger.net (Postfix) with ESMTP id 04004118F; Sat, 30 Apr 2011 08:51:39 +0200 (CEST) Date: Sat, 30 Apr 2011 08:51:37 +0200 From: Alexander Leidinger To: "Devin Teske" Message-ID: <20110430085137.00005dbc@unknown> In-Reply-To: <007201cc06c8$e1d99260$a58cb720$@vicor.com> References: <9AD2C0D5-F2A7-4F20-B04A-AF9BFC5918F7@vicor.com> <20110429130820.5056390e@bhuda.mired.org> <000301cc069f$edf8bd10$c9ea3730$@vicor.com> <20110429223355.00004ab0@unknown> <007201cc06c8$e1d99260$a58cb720$@vicor.com> X-Mailer: Claws Mail 3.7.8cvs47 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: D731F844016.AE7CF X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1, required 6, autolearn=disabled, ALL_TRUSTED -1.00) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1304751103.83539@kvwr2lCYWO0b0OeqE4PI7Q X-EBL-Spam-Status: No X-Mailman-Approved-At: Sat, 30 Apr 2011 11:19:55 +0000 Cc: 'FreeBSD Hackers' , 'Mike Meyer' Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 06:51:57 -0000 On Fri, 29 Apr 2011 16:55:12 -0700 "Devin Teske" wrote: > > -----Original Message----- > > From: Alexander Leidinger [mailto:Alexander@Leidinger.net] > > Sent: Friday, April 29, 2011 1:34 PM > > To: Devin Teske > > Cc: 'Mike Meyer'; 'FreeBSD Hackers' > > Subject: Re: [RELEASE] New Boot-Loader Menu > > > > On Fri, 29 Apr 2011 12:02:03 -0700 "Devin Teske" > > wrote: > > > > > I was thinking that what we ought to do is support *both* numbers > > > *and* letters. > > > > Sounds good to me. > > > > > I envision the menuitem numbers remaining unchanged (1-7), > > > allowing those familiar with the numbers to use them. > > > > > > However, as for the letters, I'm thinking that we *BOLD* the > > > mnemonic in the menuitem. For example (showing bolded items > > > between asterisks): > > > > > > 1. Boot *[ENTER]* > > > 2. *A*CPI Support: Enabled > > > 3. Boot Safe Mode: NO > > > 4. Boot *S*ingle User: NO > > > 5. Boot *V*erbose: NO > > > 6. *Esc*ape to loader prompt > > > 7. *R*eboot > > > > > > This should indicate to the user, for example if they see that > > > the "V" in "Verbose" is bolded, that they can press that key to > > > activate that menuitem. > > > > Your below points are all valid arguments. However, I think they are > a bit reaching. > > The types of people that know what it means to boot into Single-User > and/or Verbose mode would not be prone to thinking in those ways. Maybe not single user, but maybe verbose. For me the first question is not how to improve this, my first question is if we need to improve this. > I'm still leaning toward just making the "V" in "Verbose" and "S" in > "Single User" bolded. Your initial proposal about the characters looked fine for me. Only making those two in bold looks looks like a step backwards to me. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 16:31:37 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5770106564A for ; Sat, 30 Apr 2011 16:31:37 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id 74EC38FC08 for ; Sat, 30 Apr 2011 16:31:37 +0000 (UTC) Received: (qmail 11687 invoked by uid 0); 30 Apr 2011 16:31:36 -0000 Received: from 67.206.164.233 by rms-us003.v300.gmx.net with HTTP Date: Sat, 30 Apr 2011 16:31:30 +0000 From: "Dieter BSD" Message-ID: <20110430163133.287270@gmx.com> MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: VAuaZR7XiDz7blSaAW9p/zprZml1ZFgi Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 16:31:37 -0000 From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 16:48:55 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7217C106564A for ; Sat, 30 Apr 2011 16:48:55 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id E792A8FC0A for ; Sat, 30 Apr 2011 16:48:54 +0000 (UTC) Received: by bwz12 with SMTP id 12so5402580bwz.13 for ; Sat, 30 Apr 2011 09:48:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:references:in-reply-to:x-enigmail-version :content-type:content-transfer-encoding; bh=K2WsDdKdkGjgD/6hItoDFIZaLu+otooFsCsOlyU8iRw=; b=cFEK6siO4LEZgS+MOq5jfQ3liemKZTfgLKiGO3riSxyQ/lBCb/WmYLHkuqlxsIAHdY s4q9DMj6bRxFx3NO6WHIciNrXh1TjV/IAXUwNWrEkPqk8s42lgTqyFKrp3NdqH58cPIS tB3fZf+s6plAQel0BnIAgQSJWL9i1IONWEAgg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=NUgiKZmBVwooX3qJdbjK2+aQ4xZNHUecMd+9m9I6E2GiNDkFeShj3uolCHzJnXQjFl t3krlW1JRcNNAdsLwi4VmHqLLxfWCFoCb9ujDDGrT8C4fg2CXQ+Ae8ax1Wo+6ZB7Nlf/ pERWXQuDiQ53Of/b9Ug5l+QsCIoq1vGgFx6K8= Received: by 10.204.19.19 with SMTP id y19mr1650598bka.164.1304182133759; Sat, 30 Apr 2011 09:48:53 -0700 (PDT) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id u15sm2252449bkf.16.2011.04.30.09.48.52 (version=SSLv3 cipher=OTHER); Sat, 30 Apr 2011 09:48:53 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DBC3D63.6020508@FreeBSD.org> Date: Sat, 30 Apr 2011 19:48:35 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20110429.160309.656.1@DEV> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Look of boot2, on HDD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 16:48:55 -0000 Garrett Cooper wrote: > 2011/4/29 : >> /boot/boot2 STAGE 2 bootstrap file >> Understands the FreeBSD file system enough, to find files on it, and can provide a simple interface to choose the kernel or loader to run. >> >> Once sys is fully booted, HDD is 'ada0'. >> However, STAGE 2, sees it, as a 'ad4', at boot process, which is same seen, by booted sys, when I turn off AHCI. >> >> So, here is the riddle ... >> On fully booted sys, how do I query STAGE 2, to tell me, how it'll see, my 'ada0' HDD? > > This is a very interesting catch: > > /usr/src/sys/boot/pc98/boot2/boot2.c:static const char *const > dev_nm[NDEV] = {"ad", "da", "fd"}; > /usr/src/sys/boot/i386/boot2/boot2.c:static const char *const > dev_nm[NDEV] = {"ad", "da", "fd"}; > > It probably will be a no-op soon because of some of the > compatibility changes Alex made, but still a potential point of > confusion nonetheless. Pardon my ignorance, but could somebody shed some light for me on this list of names? Why much more sophisticated loader(8) operates disks as diak0/1/..., while boot2 tries to mimic something he has no any idea about, using very limited information from random sources? Does this names important for anything? Even with old ATA names didn't match on my laptop: boot2 reports ad0, while system - ad4. Also we have a lot of drivers who's disk names don't fit into this set of ad, da and fd. -- Alexander Motin From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 17:14:34 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E601D106564A for ; Sat, 30 Apr 2011 17:14:34 +0000 (UTC) (envelope-from moeller.akt@googlemail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6F0E88FC14 for ; Sat, 30 Apr 2011 17:14:34 +0000 (UTC) Received: by bwz12 with SMTP id 12so5415572bwz.13 for ; Sat, 30 Apr 2011 10:14:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:message-id :thread-topic:thread-index:mime-version:content-type; bh=WfWQdCeXa4TUcupgk3o1ZAknu9Swz7iU07cWs4Oznrs=; b=I3ZVSaYNqba8H70TG+buzQml8MBM4koOIq2PqNzWH+JDPRGRxPEVKKBtRKug8oMAJ1 6TWbIiR4xvzS3Tnmln5++0CScrjrTVCzACrxjgXzzJN9+Omsuxu/pbuPvVkUYmuXSL6y Qgn6UrLCKysR/0FsTXK6CXo9EFVSuz9FxwJIU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:mime-version:content-type; b=U4ZbnODMLCjgr+Ja5L0uMBcx7aS95HxTfT82LIpBZ3JU5vzVC0e4jcfSu+ZU8ti0mO 3Nk1fFhxCFJVsIMEr/WyfPg2Q+SZ+3QZU0pyGQwtabn8bXaU7ZUgUDYtNiG2Kr1/zVsI g646jmTr41EOSYtdUgVFnECBfJiAb91M7ncTc= Received: by 10.204.84.27 with SMTP id h27mr1207787bkl.158.1304181888497; Sat, 30 Apr 2011 09:44:48 -0700 (PDT) Received: from [192.168.0.108] (p5B24FE9D.dip.t-dialin.net [91.36.254.157]) by mx.google.com with ESMTPS id 16sm2253551bkm.6.2011.04.30.09.44.46 (version=SSLv3 cipher=OTHER); Sat, 30 Apr 2011 09:44:47 -0700 (PDT) User-Agent: Microsoft-Entourage/12.0.0.071130 Date: Sat, 30 Apr 2011 18:44:43 +0200 From: Martin =?ISO-8859-1?B?TfZsbGVy?= To: Message-ID: Thread-Topic: [LIBC] Modfied Version of sscanf Thread-Index: AcwHVefUJi7s0TZeTtSqUVBU0xZ4Vg== Mime-version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: [LIBC] Modfied Version of sscanf X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 17:14:35 -0000 Hi to all, This is my first email to this list, so hello to all members. The current version of sscanf, stops when a whitespace characters occurs in a string when the =8C%s=B9 (string) type is used. The following code: char name [20], value [20]; sscanf (=B3Test 2->Test 3=B2, =B3%s->%s=B2, name, value) printf (=B3%s->%s\n=B2, name, value); outputs total garbage on my FreeBSD-7.0-RELEASE #0 amd64. Is there already a way to do this or should we release a new version of sscanf, e.g. called sscanfWS. This modified version would output: Test 2->Test 3. With regards, Martin From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 17:39:12 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 481B41065670 for ; Sat, 30 Apr 2011 17:39:12 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id CE84D8FC15 for ; Sat, 30 Apr 2011 17:39:11 +0000 (UTC) Received: by wyf23 with SMTP id 23so4508012wyf.13 for ; Sat, 30 Apr 2011 10:39:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:content-type :content-transfer-encoding:in-reply-to:references:x-mailer; bh=oRn+L4+rWnTyIS5Uugd37lT9K7OhfyiU0VvrLxvHzvI=; b=qm8zl+NGPr0NiqyzvUVdfGeNxiCsIJwDpNUQvS6O4QccokgsP8x8UJ3xbnzLZ15cAX /ztCgJV3GTE+ld4QvgR6WSv2C02xsharvH9W4VmpTtedeE+9foBGhkv+ZBQurI8oW7tN UVee1XKLQSjVMvS8c57kee/eIak+6fvY2Uqto= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:content-type :content-transfer-encoding:in-reply-to:references:x-mailer; b=eM46jY43XCPXZ3z0RpfEJ1oJpItOMFEh9HfT4s+9N95bG1skH19g8oVI2bdMP5xHoM ZnLjcShi/3zEDonAUQawAB9XMYeuOCWEmw2bFjKx+OzaNZUJKXqjjr8ybjz3u7HIiL5U 8cdUPPMWVMzLg6LMyLTQYZqgjAkG+i91ZCBtg= Received: by 10.227.203.13 with SMTP id fg13mr814644wbb.95.1304185150642; Sat, 30 Apr 2011 10:39:10 -0700 (PDT) Received: from DEV ([82.193.208.173]) by mx.google.com with ESMTPS id h11sm2373069wbc.60.2011.04.30.10.39.01 (version=SSLv3 cipher=OTHER); Sat, 30 Apr 2011 10:39:09 -0700 (PDT) Message-ID: <20110430.173909.578.1@DEV> From: rank1seeker@gmail.com To: freebsd-hackers@freebsd.org Date: Sat, 30 Apr 2011 19:39:09 +0200 Content-Type: text/plain; charset="Windows-1250" Content-Transfer-Encoding: quoted-printable In-Reply-To: <4DBC3D63.6020508@FreeBSD.org> References: <20110429.160309.656.1@DEV> <4DBC3D63.6020508@FreeBSD.org> X-Mailer: POP Peeper (3.7.0.0) Subject: Re: Look of boot2, on HDD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 17:39:12 -0000 ----- Original Message -----=0D=0AFrom: Alexander Motin = =0D=0ATo: freebsd-hackers@freebsd.org=0D=0ADate: Sat, 30 = Apr 2011 19:48:35 +0300=0D=0ASubject: Re: Look of boot2, on = HDD=0D=0A=0D=0A> Garrett Cooper wrote:=0D=0A> > 2011/4/29 = :=0D=0A> >> /boot/boot2 STAGE 2 bootstrap = file=0D=0A> >> Understands the FreeBSD file system enough, to find files = on it, and can provide a simple interface to choose the kernel or loader = to run.=0D=0A> >>=0D=0A> >> Once sys is fully booted, HDD is = 'ada0'.=0D=0A> >> However, STAGE 2, sees it, as a 'ad4', at boot process, = which is same seen, by booted sys, when I turn off AHCI.=0D=0A> >>=0D=0A> = >> So, here is the riddle ...=0D=0A> >> On fully booted sys, how do I = query STAGE 2, to tell me, how it'll see, my 'ada0' HDD?=0D=0A> > =0D=0A> = > This is a very interesting catch:=0D=0A> > =0D=0A> > = /usr/src/sys/boot/pc98/boot2/boot2.c:static const char *const=0D=0A> > = dev_nm[NDEV] =3D {"ad", "da", "fd"};=0D=0A> > = /usr/src/sys/boot/i386/boot2/boot2.c:static const char *const=0D=0A> > = dev_nm[NDEV] =3D {"ad", "da", "fd"};=0D=0A> > =0D=0A> > It probably = will be a no-op soon because of some of the=0D=0A> > compatibility = changes Alex made, but still a potential point of=0D=0A> > confusion = nonetheless.=0D=0A> =0D=0A> Pardon my ignorance, but could somebody shed = some light for me on this=0D=0A> list of names? Why much more = sophisticated loader(8) operates disks as=0D=0A> diak0/1/..., while boot2 = tries to mimic something he has no any idea=0D=0A> about, using very = limited information from random sources? Does this=0D=0A> names important = for anything?=0D=0A> =0D=0A> Even with old ATA names didn't match on my = laptop: boot2 reports ad0,=0D=0A> while system - ad4. Also we have a lot = of drivers who's disk names don't=0D=0A> fit into this set of ad, da and = fd.=0D=0A> =0D=0A> -- =0D=0A> Alexander Motin=0D=0A=0D=0AWell ..., ATM, I = say lets NOT touch/edit boot2 nor loader.=0D=0ALet them continue to see = devices, the way they "like" ...=0D=0A=0D=0ANOW, all I would like, is to = find a way of ASKING them, how will they see "$target" device, at theirs = boot step/time.=0D=0A"Asking" is done, on a fully booted sys and I am = interested in asking STAGE 2 (boot2).=0D=0A=0D=0A=0D=0ADomagoj = Smol=E8i=E6=0D=0A From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 19:03:44 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D4371065674 for ; Sat, 30 Apr 2011 19:03:44 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 124168FC12 for ; Sat, 30 Apr 2011 19:03:43 +0000 (UTC) Received: by bwz12 with SMTP id 12so5467539bwz.13 for ; Sat, 30 Apr 2011 12:03:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/3KsWsP/+6k2OzBoaiq6Zbd3zq//bWfOmUayOdvdUzE=; b=muE2ZMaimm2/J0npa6Fnb9HH+1WP9rHABM/l2JgZG6mUQ6A44paT1TfAScwfvGxZcy F3du4UwbEdk8Z+i4wbH8OXMU6Twt+KEHybVHlG/UgWb31wRauyPGVaugh81VGS2qSGx7 mE9l4ZYkW6nbkFO4/8UU1krjVyQ9aXUJnpB7w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=nuwALHcOJCra77gR10EjpTKagzO74nzKOQ00AOHfJAmnQSpOOENms3T859O1raKIEw tnfBnexllyb0Gy0P1p6hF87RT6IIHLNpXAnICD7zP+fQPlkGNGtYc5jBG+v3tYB5QrQl pfIrfk+ptvWLahjaf4hKJSws/DxkMtgCbVgjs= Received: by 10.204.84.203 with SMTP id k11mr3923654bkl.10.1304190222881; Sat, 30 Apr 2011 12:03:42 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id x6sm2306318bkv.12.2011.04.30.12.03.41 (version=SSLv3 cipher=OTHER); Sat, 30 Apr 2011 12:03:42 -0700 (PDT) Sender: Alexander Motin Message-ID: <4DBC5D0A.3080008@FreeBSD.org> Date: Sat, 30 Apr 2011 22:03:38 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110310 Thunderbird/3.1.9 MIME-Version: 1.0 To: rank1seeker@gmail.com References: <4DBC3D63.6020508@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Look of boot2, on HDD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 19:03:44 -0000 On 30.04.2011 20:39, rank1seeker@gmail.com wrote: >> Garrett Cooper wrote: >>> 2011/4/29: >>>> /boot/boot2 STAGE 2 bootstrap file >>>> Understands the FreeBSD file system enough, to find files on it, and can provide a simple interface to choose the kernel or loader to run. >>>> >>>> Once sys is fully booted, HDD is 'ada0'. >>>> However, STAGE 2, sees it, as a 'ad4', at boot process, which is same seen, by booted sys, when I turn off AHCI. >>>> >>>> So, here is the riddle ... >>>> On fully booted sys, how do I query STAGE 2, to tell me, how it'll see, my 'ada0' HDD? >>> >>> This is a very interesting catch: >>> >>> /usr/src/sys/boot/pc98/boot2/boot2.c:static const char *const >>> dev_nm[NDEV] = {"ad", "da", "fd"}; >>> /usr/src/sys/boot/i386/boot2/boot2.c:static const char *const >>> dev_nm[NDEV] = {"ad", "da", "fd"}; >>> >>> It probably will be a no-op soon because of some of the >>> compatibility changes Alex made, but still a potential point of >>> confusion nonetheless. >> >> Pardon my ignorance, but could somebody shed some light for me on this >> list of names? Why much more sophisticated loader(8) operates disks as >> diak0/1/..., while boot2 tries to mimic something he has no any idea >> about, using very limited information from random sources? Does this >> names important for anything? >> >> Even with old ATA names didn't match on my laptop: boot2 reports ad0, >> while system - ad4. Also we have a lot of drivers who's disk names don't >> fit into this set of ad, da and fd. > > Well ..., ATM, I say lets NOT touch/edit boot2 nor loader. > Let them continue to see devices, the way they "like" ... League for the robots rights? :) > NOW, all I would like, is to find a way of ASKING them, how will they see "$target" device, at theirs boot step/time. > "Asking" is done, on a fully booted sys and I am interested in asking STAGE 2 (boot2). I think it may be impossible. It is up to each controller's BIOS to report device or not. And some controllers may just have no/disabled BIOS to report anything. Artificial separation between ad and da in boot2 also doesn't makes thinks easier. -- Alexander Motin From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 19:27:39 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 314F1106564A for ; Sat, 30 Apr 2011 19:27:39 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id CAF058FC08 for ; Sat, 30 Apr 2011 19:27:38 +0000 (UTC) Received: (qmail 24881 invoked by uid 0); 30 Apr 2011 19:27:37 -0000 Received: from 67.206.161.16 by rms-us012.v300.gmx.net with HTTP Content-Type: text/plain; charset="utf-8" Date: Sat, 30 Apr 2011 19:27:35 +0000 From: "Dieter BSD" Message-ID: <20110430192737.287270@gmx.com> MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: zQvZDFkE23y0M0bkHGFoudhudmllcgUP Subject: Re: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 19:27:39 -0000 [ attempt #2 - grumble - sorry about the blank message, hope it works this time - grumble- ] > I hope that works for serial console.  VT100 may be a reasonable > default in that case, but it would be good to make sure that menu > works even on a dumb terminal. Perhaps we should put 'key' letter > in brackets then? This needs to work, correctly, everywhere.  This needs to be easy to understand by a stressed out user whose machine is having problems. Therefore: Thou shalt not assume graphics. Thou shalt not assume color. Thou shalt not assume VT100 or any specific terminal. Thou shalt not assume ability to display bold. Thou shalt not assume ability to underline text. Thou shalt not assume availability of multiple fonts. Thou shalt not assume more than 24x80 chars. Thou shalt not assume scrollback. Thou shalt not assume fancy cursor movements. Thou shalt not assume presence of function keys. Thou shalt not assume presence of arrow keys. Thou shalt not assume a fast interface. Thou shalt not assume the three-finger-salute works. Putting brackets around letters (and numbers) sounds good. If there is room, perhaps add a message explaining that the user should enter one of the choices in brackets. A help option would be useful, giving a reminder of what things like ACPI and APIC stand for, what "safe" mode does, etc. Would be nice: "uname -v" of the kernel it will boot. Would be nice: a user friendly way to boot from a different disk/partition/kernel.  Without the user having to know the mapping between what the firmware calls disks and what FreeBSD calls disks.  And without writing anything to disk. Would be nice: a fix for having to lean on a key autorepeating for a couple seconds. From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 22:53:56 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D232106564A for ; Sat, 30 Apr 2011 22:53:56 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (unknown [IPv6:2001:44b8:7c07:5581:266:e1ff:fe0c:8f16]) by mx1.freebsd.org (Postfix) with ESMTP id 257A68FC1C for ; Sat, 30 Apr 2011 22:53:54 +0000 (UTC) Received: from ur.dons.net.au (ppp208-121.lns1.adl2.internode.on.net [203.122.208.121] (may be forged)) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id p3UMrpDT087130 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 1 May 2011 08:23:52 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=iso-8859-1 From: "Daniel O'Connor" In-Reply-To: Date: Sun, 1 May 2011 08:23:50 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: <6ACFC545-73B5-49FA-A97F-BC500F9AFE40@gsoft.com.au> References: To: =?iso-8859-1?Q?Martin_M=F6ller?= X-Mailer: Apple Mail (2.1084) X-Spam-Score: -0.272 () BAYES_00,RDNS_NONE X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-hackers@freebsd.org Subject: Re: [LIBC] Modfied Version of sscanf X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 22:53:56 -0000 On 01/05/2011, at 2:14, Martin M=F6ller wrote: > outputs total garbage on my FreeBSD-7.0-RELEASE #0 amd64. > Is there already a way to do this or should we release a new version = of > sscanf, e.g. called sscanfWS. >=20 > This modified version would output: Test 2->Test 3. I think it does what it should.. %s is supposed to stop at whitespace. You probably really want.. #include #include #include int main(int argc, char **argv) { char name [20], value [20]; int i; i =3D sscanf("Test 2->Test 3", "%[^-]->%[^-]", name, value); printf("%d %s->%s\n", i, name, value); exit(0); } -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 30 23:00:53 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B567810657A5 for ; Sat, 30 Apr 2011 23:00:53 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 79D088FC19 for ; Sat, 30 Apr 2011 23:00:53 +0000 (UTC) Received: from sbhfislrext01.fnfis.com ([192.168.249.167]) by SCSFISLTC01 (8.14.3/8.14.3) with ESMTP id p3UN0q7R013949; Sat, 30 Apr 2011 18:00:52 -0500 Received: from SBHFISLTCGW07.FNFIS.COM (Not Verified[10.132.248.135]) by sbhfislrext01.fnfis.com with MailMarshal (v6, 5, 4, 7535) id ; Sat, 30 Apr 2011 18:00:53 -0500 Received: from sbhfisltcgw02.FNFIS.COM ([10.132.248.122]) by SBHFISLTCGW07.FNFIS.COM with Microsoft SMTPSVC(6.0.3790.4675); Sat, 30 Apr 2011 18:00:52 -0500 Received: from lummox ([10.132.254.136]) by sbhfisltcgw02.FNFIS.COM over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sat, 30 Apr 2011 18:00:51 -0500 From: "Devin Teske" To: "'Dieter BSD'" , References: <20110430192737.287270@gmx.com> Date: Sat, 30 Apr 2011 16:00:47 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20110430192737.287270@gmx.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 Thread-Index: AcwHbMf8el2kjbuUQ5mszvGGLX1DeAAGt1DA X-OriginalArrivalTime: 30 Apr 2011 23:00:51.0356 (UTC) FILETIME=[739EA5C0:01CC078A] Cc: Subject: RE: [RELEASE] New Boot-Loader Menu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2011 23:00:53 -0000 > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > hackers@freebsd.org] On Behalf Of Dieter BSD > Sent: Saturday, April 30, 2011 12:28 PM > To: freebsd-hackers@freebsd.org > Subject: Re: [RELEASE] New Boot-Loader Menu >=20 > [ attempt #2 - grumble - sorry about the blank message, hope it > works this time - grumble- ] >=20 > > I hope that works for serial console.=A0 VT100 may be a reasonable > > default in that case, but it would be good to make sure that menu > > works even on a dumb terminal. Perhaps we should put 'key' letter > > in brackets then? >=20 > This needs to work, correctly, everywhere.=A0 This needs to be easy to > understand by a stressed out user whose machine is having problems. >=20 > Therefore: >=20 > Thou shalt not assume graphics. > Thou shalt not assume color. > Thou shalt not assume VT100 or any specific terminal. > Thou shalt not assume ability to display bold. > Thou shalt not assume ability to underline text. > Thou shalt not assume availability of multiple fonts. > Thou shalt not assume more than 24x80 chars. > Thou shalt not assume scrollback. > Thou shalt not assume fancy cursor movements. > Thou shalt not assume presence of function keys. > Thou shalt not assume presence of arrow keys. > Thou shalt not assume a fast interface. > Thou shalt not assume the three-finger-salute works. >=20 I agree with all those decrees. I'll make the next version will meet all those requirements in its "out of the box" configuration. If users want to make it colorized, I'll provide a knob that can be added to loader.conf(5) (how about ``loader_color=3D1'' ??). Already on the to-do list is to support ``loader_logo=3D...'' in /boot/loader.conf > Putting brackets around letters (and numbers) sounds good. > If there is room, perhaps add a message explaining that > the user should enter one of the choices in brackets. >=20 I think I'm going to have to play with this and see what we come up with. I don't want to make it too "busy" if you know what I mean. That's with respect to the brackets. As for adding a messages... things are a bit tight and again, I'm afraid of making it too cluttered. I'll post some screenshots of some mock-ups tomorrow, incorporating the various requests. > A help option would be useful, giving a reminder of what > things like ACPI and APIC stand for, what "safe" mode does, etc. >=20 This is not altogether infeasible. Since this menu (unlike the current one) has the ability to be wiped from screen and then recalled completely in the original state is was left in ... implementing an F1 feature that reads text from a file would be very do-able. I was at one time experimenting with reading a "version.inf" file from disk to be displayed at the bottom-right of the screen (under beastie logo) ... a way of indicating the version of either loader, OS, both, or more (could be auto-generated as part of release(7) for each/every release). > Would be nice: "uname -v" of the kernel it will boot. >=20 That's a bit more technically challenging. I'll have another look at the FICL words available, but I don't recall if there was a way to crawl the object space of the items loaded with ``load'' (looking for the uname). I'm open to suggestions if you had an idea of how to do this in Forth -- else I'd think this would need to be a loader(8) modification. > Would be nice: a user friendly way to boot from a different > disk/partition/kernel.=A0 Without the user having to know the > mapping between what the firmware calls disks and what FreeBSD > calls disks.=A0 And without writing anything to disk. >=20 That's also a bit technically challenging in Forth, I think. Open to suggestions, but again would likely be best implemented as a change to loader(8), no? > Would be nice: a fix for having to lean on a key autorepeating > for a couple seconds. >=20 Could you explain? I don't follow. --=20 Devin > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-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. _____________