From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 21 20:11:22 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E25D0DE9 for ; Sun, 21 Apr 2013 20:11:22 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com [209.85.217.173]) by mx1.freebsd.org (Postfix) with ESMTP id 6E736114D for ; Sun, 21 Apr 2013 20:11:21 +0000 (UTC) Received: by mail-lb0-f173.google.com with SMTP id 10so660975lbf.32 for ; Sun, 21 Apr 2013 13:11:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=kq6L/+PZuX7RKYCtZQRjV/PqkfESm2HuAeyCJyMwkig=; b=FHq6LpWaqV7HetzTR4zN75u19dDT34IpSFH5nREr9hGd60lLuz/tGv8RqexRX+tl6i E0nNX3MO2wpHdrLJ+zaMFh89C33DysdA/ARXKkigLxY+58wnZGn3JgDY994LUP+hiilq d8VAti2rJVT4A6EnBrHUjzuoRXjJv+AZmtjhpxWhfwrmHHVMi8jjlGTYKg61PA+QayRT WhHR2SE59pQ8dJbGFyg2ebXzOsm0+YBy04RJijp8W+SFYXSOwR/h3Kf+Yf10va+6mjat jZO0eaOZ5Rkt5gmIJ7uX9uhhsq4aUXzk8JHnCSFk9zlwwf2aLZCFOmQGBy6GYC4Sy+ny BIeg== MIME-Version: 1.0 X-Received: by 10.112.125.167 with SMTP id mr7mr11914433lbb.19.1366575079994; Sun, 21 Apr 2013 13:11:19 -0700 (PDT) Received: by 10.112.135.229 with HTTP; Sun, 21 Apr 2013 13:11:19 -0700 (PDT) Date: Sun, 21 Apr 2013 16:11:19 -0400 Message-ID: Subject: GSOC: Qt front-ends From: Justin Edward Muniz To: freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQnZtGgViTg/v9Z0N45bhhL/0dAv8GgMMKNtsVNud3sq5ysXw92h2UFQHE7npSb6dSMNmVe6 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2013 20:11:22 -0000 Hello everyone once again, I decided to split this from my previous thread because the nature of my questions has changed. I benefited from the last thread, and I am grateful to those who responded to it. For me Google Summer of Code is a big opportunity, and my interest in contributing to the open source community is fairly limited to FreeBSD for many reasons. I know that my application may have a better chance of being approved if I have a mentor to help me with my endeavors. I currently have three project ideas in mind; however I need to understand which one would be the most beneficial, and try to find a mentor, before I create my proposal. Eventually I would like to develop each application and release them along with a meta-package that comprises of them all. For now, I need to focus on just one of the three. Originally I was interested in developing a Qt front-end for freebsd-update; indeed most of my research has been for that project. However, I am also interested in furthering kports -- which seems to be notoriously buggy, has broken package functionality, and is a mammoth of an application; the last development for kports was in 2009. I also am interested in developing a graphical application to customize the FreeBSD kernel. I have compiled a list of features that I would like to concentrate on for each project. Some of the features are far less important than others, so my actual application may omit some of them, or consider them optional. If it would be appropriate I will certainly share my lists, but since the lists are long I don't want to spam the mailing-list. I am new to this community after all! If anyone is interested in discussing these possibilities or just one of them in particular, I will greatly appreciate any advice, insight, concerns, criticism, or ideas. Ideally I am also looking to talk with anyone who might be interested in mentoring my Google Summer of Code project. Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 21 21:02:46 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0557E3E0 for ; Sun, 21 Apr 2013 21:02:46 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id A468A1233 for ; Sun, 21 Apr 2013 21:02:45 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id CF3043592DE for ; Sun, 21 Apr 2013 23:02:43 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id B0D042848C; Sun, 21 Apr 2013 23:02:43 +0200 (CEST) Date: Sun, 21 Apr 2013 23:02:43 +0200 From: Jilles Tjoelker To: freebsd-hackers@freebsd.org Subject: [patch] pipe2 Message-ID: <20130421210243.GA10436@stack.nl> References: <20130419224839.GA69212@stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130419224839.GA69212@stack.nl> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Apr 2013 21:02:46 -0000 On Sat, Apr 20, 2013 at 12:48:39AM +0200, Jilles Tjoelker wrote: > I'm also working on pipe2() (using linuxulator work) and dup3() (patch > from Jukka A. Ukkonen). This is an implementation of pipe2. As with the accept4 patch, make sysent needs to be run in sys/kern and sys/compat/freebsd32. As a bonus, new architectures might implement pipe(p) as pipe2(p, 0) avoiding the need for assembler (but behaviour is different if the pointer is invalid). I will do a __FreeBSD_version bump once these are in. commit 256ab750c5e70db85d87c884994eb13038b182a2 Author: Jilles Tjoelker Date: Sat Mar 30 23:32:34 2013 +0100 Add pipe2() system call. diff --git a/include/unistd.h b/include/unistd.h index dabf178..9df0777 100644 --- a/include/unistd.h +++ b/include/unistd.h @@ -533,6 +533,7 @@ char *mktemp(char *); #endif int nfssvc(int, void *); int nlm_syscall(int, int, int, char **); +int pipe2(int *, int); int profil(char *, size_t, vm_offset_t, int); int rcmd(char **, int, const char *, const char *, const char *, int *); int rcmd_af(char **, int, const char *, diff --git a/lib/libc/sys/Makefile.inc b/lib/libc/sys/Makefile.inc index 105f469..8e918bf 100644 --- a/lib/libc/sys/Makefile.inc +++ b/lib/libc/sys/Makefile.inc @@ -352,6 +352,7 @@ MLINKS+=pathconf.2 lpathconf.2 MLINKS+=pdfork.2 pdgetpid.2\ pdfork.2 pdkill.2 \ pdfork.2 pdwait4.2 +MLINKS+=pipe.2 pipe2.2 MLINKS+=read.2 pread.2 \ read.2 preadv.2 \ read.2 readv.2 diff --git a/lib/libc/sys/Symbol.map b/lib/libc/sys/Symbol.map index 149fa41..24f4621 100644 --- a/lib/libc/sys/Symbol.map +++ b/lib/libc/sys/Symbol.map @@ -393,6 +393,7 @@ FBSD_1.3 { ffclock_getcounter; ffclock_getestimate; ffclock_setestimate; + pipe2; posix_fadvise; wait6; }; diff --git a/lib/libc/sys/pipe.2 b/lib/libc/sys/pipe.2 index 92d137f..bb3db51 100644 --- a/lib/libc/sys/pipe.2 +++ b/lib/libc/sys/pipe.2 @@ -28,7 +28,7 @@ .\" @(#)pipe.2 8.1 (Berkeley) 6/4/93 .\" $FreeBSD$ .\" -.Dd January 30, 2006 +.Dd March 31, 2013 .Dt PIPE 2 .Os .Sh NAME @@ -40,6 +40,8 @@ .In unistd.h .Ft int .Fn pipe "int fildes[2]" +.Ft int +.Fn pipe2 "int fildes[2]" "int flags" .Sh DESCRIPTION The .Fn pipe @@ -50,6 +52,29 @@ which is an object allowing bidirectional data flow, and allocates a pair of file descriptors. .Pp +The +.Fn pipe2 +system call allows control over the attributes of the file descriptors +via the +.Fa flags +argument. +Values for +.Fa flags +are constructed by a bitwise-inclusive OR of flags from the following +list, defined in +.In fcntl.h : +.Bl -tag -width ".Dv O_NONBLOCK" +.It Dv O_CLOEXEC +Set the close-on-exec flag for the new file descriptors. +.It Dv O_NONBLOCK +Set the non-blocking flag for the ends of the pipe. +.El +.Pp +If the +.Fa flags +argument is 0, the behavior is identical to a call to +.Fn pipe . +.Pp By convention, the first descriptor is normally used as the .Em read end of the pipe, @@ -88,7 +113,9 @@ pipe in one direction. .Sh ERRORS The .Fn pipe -system call will fail if: +and +.Fn pipe2 +system calls will fail if: .Bl -tag -width Er .It Bq Er EMFILE Too many descriptors are active. @@ -97,6 +124,16 @@ The system file table is full. .It Bq Er ENOMEM Not enough kernel memory to establish a pipe. .El +.Pp +The +.Fn pipe2 +system call will also fail if: +.Bl -tag -width Er +.It Bq Er EINVAL +The +.Fa flags +argument is invalid. +.El .Sh SEE ALSO .Xr sh 1 , .Xr fork 2 , @@ -111,3 +148,8 @@ function appeared in .Pp Bidirectional pipes were first used on .At V.4 . +.Pp +The +.Fn pipe2 +function appeared in +.Fx 10.0 . diff --git a/sys/compat/freebsd32/syscalls.master b/sys/compat/freebsd32/syscalls.master index 2cbdf31..be245be 100644 --- a/sys/compat/freebsd32/syscalls.master +++ b/sys/compat/freebsd32/syscalls.master @@ -1026,3 +1026,4 @@ struct sockaddr * __restrict name, \ __socklen_t * __restrict anamelen, \ int flags); } +542 AUE_PIPE NOPROTO { int pipe2(int *fildes, int flags); } diff --git a/sys/kern/capabilities.conf b/sys/kern/capabilities.conf index 0b64503..d2fa51c 100644 --- a/sys/kern/capabilities.conf +++ b/sys/kern/capabilities.conf @@ -490,6 +490,7 @@ pdkill ## Allow pipe(2). ## pipe +pipe2 ## ## Allow poll(2), which will be scoped by capability rights. diff --git a/sys/kern/sys_pipe.c b/sys/kern/sys_pipe.c index 90c3022..493fee5e 100644 --- a/sys/kern/sys_pipe.c +++ b/sys/kern/sys_pipe.c @@ -477,6 +477,24 @@ sys_pipe(struct thread *td, struct pipe_args *uap) return (0); } +int +sys_pipe2(struct thread *td, struct pipe2_args *uap) +{ + int error, fildes[2]; + + if (uap->flags & ~(O_CLOEXEC | O_NONBLOCK)) + return (EINVAL); + error = kern_pipe2(td, fildes, uap->flags); + if (error) + return (error); + error = copyout(fildes, uap->fildes, 2 * sizeof(int)); + if (error) { + (void)kern_close(td, fildes[0]); + (void)kern_close(td, fildes[1]); + } + return (error); +} + /* * Allocate kva for pipe circular buffer, the space is pageable * This routine will 'realloc' the size of a pipe safely, if it fails diff --git a/sys/kern/syscalls.master b/sys/kern/syscalls.master index 922db30..8668943 100644 --- a/sys/kern/syscalls.master +++ b/sys/kern/syscalls.master @@ -976,5 +976,6 @@ struct sockaddr * __restrict name, \ __socklen_t * __restrict anamelen, \ int flags); } +542 AUE_PIPE STD { int pipe2(int *fildes, int flags); } ; Please copy any additions and changes to the following compatability tables: ; sys/compat/freebsd32/syscalls.master From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 02:22:33 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E44A559C for ; Mon, 22 Apr 2013 02:22:33 +0000 (UTC) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id D57A71AF6 for ; Mon, 22 Apr 2013 02:22:33 +0000 (UTC) Received: from xyf.my.dom (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r3M2MVHF087938 for ; Mon, 22 Apr 2013 02:22:33 GMT (envelope-from davidxu@freebsd.org) Message-ID: <51749F00.6070403@freebsd.org> Date: Mon, 22 Apr 2013 10:22:56 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130416 Thunderbird/17.0.5 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: NUMA, cpuset and malloc References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 02:22:34 -0000 On 2013/04/21 06:43, Robert Waksmundzki wrote: > On NUMA systems allocated memory is striped across local and non-local banks in order to have consistent performance in case the task is rescheduled to a different CPU socket. > When a process is pinned to a single CPU socket with cpuset having the memory allocator prefer local banks would probably improve performance. Default system behavior would stay the same and the optimization would only be triggered on big multi socket systems when administrator used cpuset (command mostly used for performance optimization anyway). > > Is this something currently implemented in FreeBSD? Is this even a good idea? Do you mean linux like numactl ? AFAIK, there is no such feature in the FreeBSD. Regards, David Xu From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 08:43:54 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E7D31FF7; Mon, 22 Apr 2013 08:43:54 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw12.york.ac.uk (mail-gw12.york.ac.uk [144.32.129.162]) by mx1.freebsd.org (Postfix) with ESMTP id B5A1D17D9; Mon, 22 Apr 2013 08:43:54 +0000 (UTC) Received: from ury.york.ac.uk ([144.32.64.162]:21941) by mail-gw12.york.ac.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1UUCLp-0006qq-Lz; Mon, 22 Apr 2013 09:43:53 +0100 Date: Mon, 22 Apr 2013 09:43:53 +0100 (BST) From: Gavin Atkinson X-X-Sender: gavin@thunderhorn.york.ac.uk To: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org Subject: FreeBSD is participating in Google Summer of Code Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: soc-admins@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 08:43:55 -0000 Hi all, FreeBSD is pleased to announce that once again we have been selected to participate in the Google Summer of Code program. This gives University students the opportunity to earn a $5000 USD stipend in exchange for working on Open Source software over their Summer break. Students have around 12 weeks to work on their project, and will be mentored by existing FreeBSD committers. Participating organisations will earn $500 USD per student mentored. FreeBSD's organisation page may be found at http://www.google-melange.com/gsoc/org/google/gsoc2013/freebsd and a list of possible project ideas may be found at https://wiki.freebsd.org/IdeasPage . Please note that projects do not have to come from the ideas list, and indeed students are encouraged to produce their own project ideas - the majority of past projects have been thought up by the particpants themselves. Students are also encouraged to visit http://www.google-melange.com/ to view more details of the program, including eligibility requirements, and a list of other participating organisations. Thanks, Gavin From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 09:12:12 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7B916924 for ; Mon, 22 Apr 2013 09:12:12 +0000 (UTC) (envelope-from sreenathbh@rocketmail.com) Received: from nm22-vm0.bullet.mail.ne1.yahoo.com (nm22-vm0.bullet.mail.ne1.yahoo.com [98.138.91.60]) by mx1.freebsd.org (Postfix) with ESMTP id 157951A4E for ; Mon, 22 Apr 2013 09:12:11 +0000 (UTC) Received: from [98.138.226.179] by nm22.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2013 09:08:46 -0000 Received: from [98.138.87.6] by tm14.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2013 09:08:46 -0000 Received: from [127.0.0.1] by omp1006.mail.ne1.yahoo.com with NNFMP; 22 Apr 2013 09:08:46 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 664343.58569.bm@omp1006.mail.ne1.yahoo.com Received: (qmail 58133 invoked by uid 60001); 22 Apr 2013 09:08:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rocketmail.com; s=s1024; t=1366621726; bh=vRB8MKjb924uT1qOdtre2y1h+H2/TmJXzCdmcpV7fuk=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=dzp0W0GoU4aodFvggyxbqmyztU6hYza1NzBdMYZdVQ9RAjZV19/dnXZq5E15H2rizf/OlbqZx+/aGTf/+t0sjacOr5QpwquwyMkW4dYAv5l1CX7UnbjSsKij12yoM2BYYavMm8oULffuwtusH10dWoUQBxI0PBuotbKhS9Q+uqU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rocketmail.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=kgujkyu4B05rLKdFB6DxOIHYYAKnZvgt7ZE8JLJFMDdSIYymk+imJuhwJmaMSoUcaFvVf7fgXYfQlQ+dzj2wPQUBJ6sLZUKQmljYYnCiTCH6hnpGGaAYqv5qjYY9DGOHlILjJLQUIInZDOGGLmjdIKRw39MyPW+NRjS21IRttIQ=; X-YMail-OSG: 39LrHH4VM1mvKsssdKHv0kAlSJ3Hqa3imeIAvptyJvorC_6 N3n8JUTx_HSdwdg6pbvWZqHkV47FefN410ms19jjxyKhsdRGmlx3_Skch6Xf G4ZKCaplVHUdDpecVTX0wr1L1xbkTv3Rj8AF_idolUnt51V9Y6z.hkrbBjIN kvtXuZw.PhKqagEJefHy.sQl.9HDatZrwFl4xQbM3tCMMOsom5s.01I1JZHB _6aSA4AVgrMT13lN3p4UrkCyDhFkk7gQH37MHWS_lVOarom9CcVh0WXSmanK ZYiN4WfZK_ygex_vq_aGQKjRLtZMD6dPh5GRtIZV.YIryzq_pQ9gVewkderH SLMLmC.P3HyNHdkhTpWrOcoXckwp0ENSIz.9_mO970akgQUWa7XrUgmGOV7X 33lcT_hNUCbG0VBw7F0Cok.HgqRgN96dznjtcy1TgQ8ocigKDLSnKr3Dz2Nl EM5XM3OkvHWWyC03l3n0FIp_IWC2BQNEam2qja9gPwDvPIsGXt0prvYBSz8i YhgIFohhhg1iHX0XQI3ixgYhklORWaTGCpp1oJhK_Mnikq0bIyrfxZwyl9A- - Received: from [59.92.222.58] by web122203.mail.ne1.yahoo.com via HTTP; Mon, 22 Apr 2013 02:08:46 PDT X-Rocket-MIMEInfo: 002.001, QWxsLAoKSSBhbSBuZXcgbWVtYmVyIHRvIHRoaXMgbGlzdC4KClRoZSAnUHJvamVjdCBJZGVhcycgcGFnZSBvbiBmcmVlYnNkLm9yZyBsaXN0cyBIRlMgc3VwcG9ydCBhcyBhIHBvc3NpYmxlIHByb2plY3QsIGFuZCBzdWdnZXN0ZWQgdGhhdCBhbnlvbmUgaW50ZXJlc3RlZCBzaG91bGQgY2hlY2sgd2l0aCBmcmVlYnNkIGhhY2tlcnMgbWFpbGluZyBsaXN0IGZpcnN0LgoKSSBhbSBpbnRlcmVzdGVkIGluIHRha2luZyB1cCB0aGUgd29yay4gV2FudGVkIHRvIGtub3cgaWYgYW55b25lIGlzIGFscmVhZHkgd29ya2kBMAEBAQE- X-Mailer: YahooMailClassic/15.1.7 YahooMailWebService/0.8.141.536 Message-ID: <1366621726.56948.YahooMailClassic@web122203.mail.ne1.yahoo.com> Date: Mon, 22 Apr 2013 02:08:46 -0700 (PDT) From: Sreenath Battalahalli Subject: Status of HFS support on FreeBSD To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 09:12:12 -0000 All, I am new member to this list. The 'Project Ideas' page on freebsd.org lists HFS support as a possible project, and suggested that anyone interested should check with freebsd hackers mailing list first. I am interested in taking up the work. Wanted to know if anyone is already working on this. -Sreenath From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 15:34:37 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 457C849A for ; Mon, 22 Apr 2013 15:34:37 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm39-vm7.bullet.mail.bf1.yahoo.com (nm39-vm7.bullet.mail.bf1.yahoo.com [72.30.239.151]) by mx1.freebsd.org (Postfix) with ESMTP id E358D11C2 for ; Mon, 22 Apr 2013 15:34:36 +0000 (UTC) Received: from [98.139.215.141] by nm39.bullet.mail.bf1.yahoo.com with NNFMP; 22 Apr 2013 15:34:30 -0000 Received: from [98.139.213.11] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 22 Apr 2013 15:34:30 -0000 Received: from [127.0.0.1] by smtp111.mail.bf1.yahoo.com with NNFMP; 22 Apr 2013 15:34:30 -0000 X-Yahoo-Newman-Id: 110988.84568.bm@smtp111.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: yha.sJMVM1lCwSonbjtnrWbLuBrJG19ZDLOa29ERiO2Im7S V7zkHyBAmdWCHqmZ2T78zX_NZxpXixkACs0Co_Jw2JGlzYR.JZx6CP.jOc2i 6pbZTspLbJjNCHRCy65piZe8M33R0jKDBiJloNLsOKxtpf2sP8LUYs7NPNJz jQ7JKWU.Qv4_blfziH7ueV2BAYdzuW5OJUMvIsr4aDFkrzKKM2roHOc7VYWe fjxir8Dfd9gnbnxb31dgQTmFm0OieLVLrN1hzdGm2EgaGWz4AzoEiUOHs3yB H1.P4KVmA6mWd9YVu6aiNlVsACZmPOSbAd_.7kjx1o4_5Gc8BQjFkPb_pQvP J2QKrRVkCnmORVsfCNhiJhVGvdOfTaAN9f.Bqgy.J8p3G2BGXo_VeuG6OIrX VI1RfrGVtfphb7KteSfE3g.wa2sngDaObhNT91VTAzk0JbDOvZVhKzKHfQu_ myqKTcKm3XoC51no_BUPJcZuvkPj8Ze.Md1HJyEc6WLl6WtEu6_tUe9Tb.3a x8Kmm0zPbZNlqPxIGNB02ew-- X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf X-Rocket-Received: from [192.168.0.102] (pfg@190.157.126.109 with plain) by smtp111.mail.bf1.yahoo.com with SMTP; 22 Apr 2013 08:34:30 -0700 PDT Message-ID: <51755884.1080202@FreeBSD.org> Date: Mon, 22 Apr 2013 10:34:28 -0500 From: Pedro Giffuni Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Sreenath Battalahalli , freebsd-hackers@freebsd.org Subject: Re: Status of HFS support on FreeBSD Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 15:34:37 -0000 Hello Sreenath; Thank you for your interest in the HFS+ port. Around 2004-2005 there was an initial port done but the developer behind it lost interest and no one picked it up. Apparently the Apple code was very clean and a lot stuff just worked. Since then the Apple driver has advanced a lot though. My recommendation is to take a look at the webarchive link referred by in the wiki: https://wiki.freebsd.org/HFS Start from the newest XNU sources but take a look at the previous code for reference. Do try to keep some version control system (github, bitbucket, google code, etc) so that the effort can be picked up if you later lose interest. Note that this project is not tagged GSoC as it may take more dedication than just a Summer, however if we see there is interest, that the project is well planned, and even that some coding has started we would be likely to find a mentor. Pedro. From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 16:07:05 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6EA34FA for ; Mon, 22 Apr 2013 16:07:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4CF681348 for ; Mon, 22 Apr 2013 16:07:05 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 86155B96C; Mon, 22 Apr 2013 12:07:04 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: NUMA, cpuset and malloc Date: Mon, 22 Apr 2013 11:32:08 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201304221132.08194.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 22 Apr 2013 12:07:04 -0400 (EDT) Cc: Robert Waksmundzki X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 16:07:05 -0000 On Saturday, April 20, 2013 6:43:26 pm Robert Waksmundzki wrote: > On NUMA systems allocated memory is striped across local and non-local banks in order to have consistent performance in case the task is rescheduled to a different CPU socket. > When a process is pinned to a single CPU socket with cpuset having the memory allocator prefer local banks would probably improve performance. Default system behavior would stay the same and the optimization would only be triggered on big multi socket systems when administrator used cpuset (command mostly used for performance optimization anyway). > > Is this something currently implemented in FreeBSD? Is this even a good idea? You can get something sort of like this by enabling NUMA in your kernel (9.0 and later) and always pinning your processes with cpuset. (The simple NUMA bits always allocate memory in the memory domain the current thread is running in at the time of the fault.) -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 16:07:05 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 82BF8FB for ; Mon, 22 Apr 2013 16:07:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 574D21349 for ; Mon, 22 Apr 2013 16:07:05 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5D9C4B94C; Mon, 22 Apr 2013 12:07:02 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation Date: Mon, 22 Apr 2013 11:29:42 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <20130419162834.GA90217@icarus.home.lan> <20130420014821.GA98555@icarus.home.lan> <5172812A.10309@gmail.com> In-Reply-To: <5172812A.10309@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201304221129.43119.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 22 Apr 2013 12:07:02 -0400 (EDT) Cc: Jeremy Chadwick , Joshua Isom X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 16:07:05 -0000 On Saturday, April 20, 2013 7:51:06 am Joshua Isom wrote: > On 4/19/2013 8:48 PM, Jeremy Chadwick wrote: > > I'm happy to open up a ticket with VMware about the issue as I'm a > > customer, but I find it a little odd that other operating systems do not > > exhibit this problem, including another BSD. Ones which reboot just > > fine from their bootloaders: > > > > - Linux -- so many that I don't know where to begin: ArchLinux > > 2012.10.06, CentOS 6.3, Debian 6.0.7, Finnix 1.0.5, Knoppix 7.0.4, > > Slackware 14.0, and Ubuntu 11.10 > > - OpenBSD 5.2 > > - OpenIndiana -- build 151a7 (server version) > > > > So when you say "Blame VMware", I'd be happy to, except there must be > > something FreeBSD's bootstraps are doing differently than everyone else > > that causes this oddity. Would you not agree? > > A triple fault is standard practice as a fail safe guarantee of reboot. > It's used either as a reboot, switch to real mode(IBM OS/2), or > catastrophic unrecoverable failure. > > By the looks of grub(Linux and Solaris), it either jumps to it's own > instruction, hoping the bios catches it("tell the BIOS a boot failure, > which may result in no effect"), or jumps to a location that I can't yet > determine what code exists there. I can't seem to find OpenBSD's reboot > method from OpenBSD's cvsweb, only an exit but not where that exit leads > to. The native operating system is irrelevant, only the boot loader so > all the Linux distributions and Solaris forks all count as "grub." Many > other bootloaders don't even have the reboot option, just "fail." > Here's barebox, a Das U-Boot fork: > > /** How to reset the machine? */ > while(1) > > In any case, it's a bag of tricks, finding something that works and is > "nice." We're talking 30 years of legacy. A triple fault, assuming the > mbr and loader ignores or zeroes previous memory, is guaranteed and > doesn't hang. Actually, the traditional reboot method in real-mode (e.g. in DOS) is to jump to 0xffff:0. The BIOS is supposed to have a restart routine at that location. I've also seen jumps to 0xf000:fff0. For example, BTX (the mini-kernel that "hosts" the loader and boot2) uses the latter: /* * Reboot or await reset. */ sti # Enable interrupts testb $0x1,btx_hdr+0x7 # Reboot? exit.3: jz exit.3 # No movw $0x1234, BDA_BOOT # Do a warm boot ljmp $0xf000,$0xfff0 # reboot the machine And in fact, when the loader calls __exit() that is precisely where it ends up. The int 0x30 ends up here in btx.S: /* * System calls. */ .set SYS_EXIT,0x0 # Exit .set SYS_EXEC,0x1 # Exec ... /* * System Call. */ intx30: cmpl $SYS_EXEC,%eax # Exec system call? jne intx30.1 # No ... intx30.1: orb $0x1,%ss:btx_hdr+0x7 # Flag reboot jmp exit # Exit And the 'exit' label eventually ends up at the 'exit.3' code I quoted above. If the BIOS VMWare exports a reboot routine VMWare doesn't like then VMWare needs to fix its BIOS. :) The operations we try on x86 to shutdown from protected mode is quite a bit longer (not including the ACPI bits). You can look at cpu_reset_real() in sys/i386/i386/vm_machdep.c. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 16:29:30 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6FB62E32; Mon, 22 Apr 2013 16:29:30 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by mx1.freebsd.org (Postfix) with ESMTP id 258F41531; Mon, 22 Apr 2013 16:29:30 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id t2so2265784qcq.14 for ; Mon, 22 Apr 2013 09:29:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=tLdbe5jRS2NUe7wD4tu+1O9YH8ZpdOqsb0UVwJhn2VM=; b=RE6CJXQ1Kb7c4EjJnPtz8jbhwOtKHGF3ypOKGcO7rUV0d340G9/K6/HrluCTyHdSGf spkSdwtUsUdWOLU0RPbUn7SSLaZbDCZa7JPT6iR2974veia0qOpfMlexp96xIy8j937f uSNuTYi+B9lHUgWZHqCrdAHhMNUQJ20TSh3UDdYWRXNo2w1zsKMO6nUE0pVQeOaWUH4D SCHTFLUzAAqsEMobQxDBjgGhB6CueJnZqp7kyG5PmArQ9+dPV2nVXFugLOAxzYJeDF56 y++bvbBbwld8YafCQBU8TrEavxqEDMMZtikDrpnXi+1ZNhAEJD7AfE/NOdTSzYD0j3Lw ShWw== MIME-Version: 1.0 X-Received: by 10.49.35.132 with SMTP id h4mr11671842qej.29.1366648169687; Mon, 22 Apr 2013 09:29:29 -0700 (PDT) Received: by 10.49.51.9 with HTTP; Mon, 22 Apr 2013 09:29:29 -0700 (PDT) In-Reply-To: <201304221132.08194.jhb@freebsd.org> References: <201304221132.08194.jhb@freebsd.org> Date: Mon, 22 Apr 2013 09:29:29 -0700 Message-ID: Subject: Re: NUMA, cpuset and malloc From: Freddie Cash To: John Baldwin Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Robert Waksmundzki X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 16:29:30 -0000 On Mon, Apr 22, 2013 at 8:32 AM, John Baldwin wrote: > On Saturday, April 20, 2013 6:43:26 pm Robert Waksmundzki wrote: > > On NUMA systems allocated memory is striped across local and non-local > banks > in order to have consistent performance in case the task is rescheduled to > a > different CPU socket. > > When a process is pinned to a single CPU socket with cpuset having the > memory allocator prefer local banks would probably improve performance. > Default system behavior would stay the same and the optimization would > only be > triggered on big multi socket systems when administrator used cpuset > (command > mostly used for performance optimization anyway). > > > > Is this something currently implemented in FreeBSD? Is this even a good > idea? > > You can get something sort of like this by enabling NUMA in your kernel > (9.0 > and later) and always pinning your processes with cpuset. (The simple NUMA > bits always allocate memory in the memory domain the current thread is > running in at the time of the fault.) > How does one enable NUMA? A "grep -i numa /usr/src/sys/conf/NOTES /usr/src/sys/amd64/conf/NOTES" turns up 0 hits for both 9-STABLE r248547 and 10-CURRENT (April 11, used svnup so no way to get the exact revision number, that I know of). Or, is it enabled automatically? -- Freddie Cash fjwcash@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 17:31:23 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 51D2FC56 for ; Mon, 22 Apr 2013 17:31:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id BE674182B for ; Mon, 22 Apr 2013 17:31:22 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r3MHVIFP012780; Mon, 22 Apr 2013 20:31:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.2 kib.kiev.ua r3MHVIFP012780 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r3MHVIq5012779; Mon, 22 Apr 2013 20:31:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 22 Apr 2013 20:31:18 +0300 From: Konstantin Belousov To: Jilles Tjoelker Subject: Re: [patch] pipe2 Message-ID: <20130422173118.GQ67273@kib.kiev.ua> References: <20130419224839.GA69212@stack.nl> <20130421210243.GA10436@stack.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ngPZezdD7QsvFaqQ" Content-Disposition: inline In-Reply-To: <20130421210243.GA10436@stack.nl> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 17:31:23 -0000 --ngPZezdD7QsvFaqQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 21, 2013 at 11:02:43PM +0200, Jilles Tjoelker wrote: > On Sat, Apr 20, 2013 at 12:48:39AM +0200, Jilles Tjoelker wrote: > > I'm also working on pipe2() (using linuxulator work) and dup3() (patch > > from Jukka A. Ukkonen). >=20 > This is an implementation of pipe2. As with the accept4 patch, make > sysent needs to be run in sys/kern and sys/compat/freebsd32. >=20 > As a bonus, new architectures might implement pipe(p) as pipe2(p, 0) > avoiding the need for assembler (but behaviour is different if the > pointer is invalid). I do not see anything wrong with the patch. That said, I prefer the pipe(2) approach of delegating the access to the usermode memory to usermode, which avoids the need of the calls to kern_close(). --ngPZezdD7QsvFaqQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRdXPlAAoJEJDCuSvBvK1B+B8P/RgbZEipYkGxEyqHwsL4sglx J/tspDO8mx+SZN0xS4zYBggt/APsZWlRiEWdLPvVi2y0C3ZdckKFR1eY0pNIcJ3J SDGO5MmW757jXnRHWvjD5Y6RTPOIP5dfaCOCK8des/YStTyHTZoDAlwTRnIE9S2c h04uianGAiDfcSKNNKG6KVVFFUXoDEkP5o/CcIMyqNWyfJZ4CKQIxbObtcBU1uy7 FZCNVpNY/qVFW5V3Hu8AfrBkv4xe/yyKhar5NuQV5EYbA3Kl6rTGrpPgxEIpHDkC xSULMfYk+sXzYls0NCQh+Ymr7FoCxhlQmuWxBkuw5B68rzC+HN+iH0Sxgy1juJ1B rNzumE0M6NOvHPfZLFYoNACl6IBou4mJ+Dqi1z69iJkNGjqjAD/xOczDF9Yqz+d6 hgpr4HZ+6umatPbzn5FWw9Uk3rXg1eW/dtGTnlfuClca55y4iWBZT/H3Po8dTrb+ 8tH3TCyxusOzP4pCQ0ObqYO03OQWE5qQV/E0VTPWCHgrTWSddJ4AM6yx5WDpji/i iOjSls4UDFA6diGlLWhaHCtT3al+Ftf3XFVIPJOX7qdqP69b2IwXYqKLrsfyBgB7 YDXW1qKSpHUNOmhsB3qecMHW/rP/LyWjMhqWLC5QPbM46c1KZkHuHoMIEbW38qCu lnLwiZgEE5perqqdDBiX =uFnG -----END PGP SIGNATURE----- --ngPZezdD7QsvFaqQ-- From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 19:17:45 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8B5A751B for ; Mon, 22 Apr 2013 19:17:45 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 682BD1F80 for ; Mon, 22 Apr 2013 19:17:45 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 54793B962; Mon, 22 Apr 2013 15:17:42 -0400 (EDT) From: John Baldwin To: Freddie Cash Subject: Re: NUMA, cpuset and malloc Date: Mon, 22 Apr 2013 13:17:10 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <201304221132.08194.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201304221317.10722.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 22 Apr 2013 15:17:42 -0400 (EDT) Cc: FreeBSD Hackers , Robert Waksmundzki X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 19:17:45 -0000 On Monday, April 22, 2013 12:29:29 pm Freddie Cash wrote: > On Mon, Apr 22, 2013 at 8:32 AM, John Baldwin wrote: > > > On Saturday, April 20, 2013 6:43:26 pm Robert Waksmundzki wrote: > > > On NUMA systems allocated memory is striped across local and non-local > > banks > > in order to have consistent performance in case the task is rescheduled to > > a > > different CPU socket. > > > When a process is pinned to a single CPU socket with cpuset having the > > memory allocator prefer local banks would probably improve performance. > > Default system behavior would stay the same and the optimization would > > only be > > triggered on big multi socket systems when administrator used cpuset > > (command > > mostly used for performance optimization anyway). > > > > > > Is this something currently implemented in FreeBSD? Is this even a good > > idea? > > > > You can get something sort of like this by enabling NUMA in your kernel > > (9.0 > > and later) and always pinning your processes with cpuset. (The simple NUMA > > bits always allocate memory in the memory domain the current thread is > > running in at the time of the fault.) > > > > How does one enable NUMA? > > A "grep -i numa /usr/src/sys/conf/NOTES /usr/src/sys/amd64/conf/NOTES" > turns up 0 hits for both 9-STABLE r248547 and 10-CURRENT (April 11, used > svnup so no way to get the exact revision number, that I know of). > > Or, is it enabled automatically? You have to chagne the VM_NDOMAIN setting. In recent HEAD and 9-stable you can do it in the kernel config (options VM_NDOMAIN=4 for example). In older HEAD and 9 you have to edit sys/amd64/include/vmparam.h or sys/i386/include/vmparam.h and change VM_NDOMAIN before building your kernel. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 22 22:49:07 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2099986B for ; Mon, 22 Apr 2013 22:49:07 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (unknown [IPv6:2001:610:1108:5012::107]) by mx1.freebsd.org (Postfix) with ESMTP id E0E6C1B61 for ; Mon, 22 Apr 2013 22:49:06 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 88FC8120207; Tue, 23 Apr 2013 00:48:51 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 7209F2848C; Tue, 23 Apr 2013 00:48:51 +0200 (CEST) Date: Tue, 23 Apr 2013 00:48:51 +0200 From: Jilles Tjoelker To: Konstantin Belousov Subject: Re: [patch] pipe2 Message-ID: <20130422224851.GA29525@stack.nl> References: <20130419224839.GA69212@stack.nl> <20130421210243.GA10436@stack.nl> <20130422173118.GQ67273@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130422173118.GQ67273@kib.kiev.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 22:49:07 -0000 On Mon, Apr 22, 2013 at 08:31:18PM +0300, Konstantin Belousov wrote: > On Sun, Apr 21, 2013 at 11:02:43PM +0200, Jilles Tjoelker wrote: > > On Sat, Apr 20, 2013 at 12:48:39AM +0200, Jilles Tjoelker wrote: > > > I'm also working on pipe2() (using linuxulator work) and dup3() (patch > > > from Jukka A. Ukkonen). > > This is an implementation of pipe2. As with the accept4 patch, make > > sysent needs to be run in sys/kern and sys/compat/freebsd32. > > As a bonus, new architectures might implement pipe(p) as pipe2(p, 0) > > avoiding the need for assembler (but behaviour is different if the > > pointer is invalid). > I do not see anything wrong with the patch. That said, I prefer the > pipe(2) approach of delegating the access to the usermode memory to > usermode, which avoids the need of the calls to kern_close(). Delegating the access gives better semantics (a signal instead of an [EFAULT] error) but I don't like adding architecture-specific assembler wrappers like pipe.S. Also, different calling conventions than expected from the C level prototype may make things harder to understand. Perhaps the wrapper can be implemented in C with the below declarations but it is quite likely that this is not fully portable. struct pipereturn { register_t a, b; }; struct pipereturn __sys_pipe(void); -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 14:36:40 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 38F3C8B7; Tue, 23 Apr 2013 14:36:40 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id D804916F2; Tue, 23 Apr 2013 14:36:39 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::106e:515:ef78:2c64] (unknown [IPv6:2001:7b8:3a7:0:106e:515:ef78:2c64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 3A6BA5C45; Tue, 23 Apr 2013 16:36:36 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation From: Dimitry Andric In-Reply-To: <201304221129.43119.jhb@freebsd.org> Date: Tue, 23 Apr 2013 16:36:24 +0200 Content-Transfer-Encoding: 7bit Message-Id: <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> References: <20130419162834.GA90217@icarus.home.lan> <20130420014821.GA98555@icarus.home.lan> <5172812A.10309@gmail.com> <201304221129.43119.jhb@freebsd.org> To: John Baldwin X-Mailer: Apple Mail (2.1503) Cc: Jeremy Chadwick , freebsd-hackers@freebsd.org, Joshua Isom X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 14:36:40 -0000 On Apr 22, 2013, at 17:29, John Baldwin wrote: > On Saturday, April 20, 2013 7:51:06 am Joshua Isom wrote: >> On 4/19/2013 8:48 PM, Jeremy Chadwick wrote: >>> I'm happy to open up a ticket with VMware about the issue as I'm a >>> customer, but I find it a little odd that other operating systems do not >>> exhibit this problem, including another BSD. Ones which reboot just >>> fine from their bootloaders: >>> >>> - Linux -- so many that I don't know where to begin: ArchLinux >>> 2012.10.06, CentOS 6.3, Debian 6.0.7, Finnix 1.0.5, Knoppix 7.0.4, >>> Slackware 14.0, and Ubuntu 11.10 >>> - OpenBSD 5.2 >>> - OpenIndiana -- build 151a7 (server version) >>> >>> So when you say "Blame VMware", I'd be happy to, except there must be >>> something FreeBSD's bootstraps are doing differently than everyone else >>> that causes this oddity. Would you not agree? >> >> A triple fault is standard practice as a fail safe guarantee of reboot. >> It's used either as a reboot, switch to real mode(IBM OS/2), or >> catastrophic unrecoverable failure. >> >> By the looks of grub(Linux and Solaris), it either jumps to it's own >> instruction, hoping the bios catches it("tell the BIOS a boot failure, >> which may result in no effect"), or jumps to a location that I can't yet >> determine what code exists there. I can't seem to find OpenBSD's reboot >> method from OpenBSD's cvsweb, only an exit but not where that exit leads >> to. The native operating system is irrelevant, only the boot loader so >> all the Linux distributions and Solaris forks all count as "grub." Many >> other bootloaders don't even have the reboot option, just "fail." >> Here's barebox, a Das U-Boot fork: >> >> /** How to reset the machine? */ >> while(1) >> >> In any case, it's a bag of tricks, finding something that works and is >> "nice." We're talking 30 years of legacy. A triple fault, assuming the >> mbr and loader ignores or zeroes previous memory, is guaranteed and >> doesn't hang. > > Actually, the traditional reboot method in real-mode (e.g. in DOS) is > to jump to 0xffff:0. The BIOS is supposed to have a restart routine > at that location. I've also seen jumps to 0xf000:fff0. > > For example, BTX (the mini-kernel that "hosts" the loader and boot2) > uses the latter: > > /* > * Reboot or await reset. > */ > sti # Enable interrupts > testb $0x1,btx_hdr+0x7 # Reboot? > exit.3: jz exit.3 # No > movw $0x1234, BDA_BOOT # Do a warm boot > ljmp $0xf000,$0xfff0 # reboot the machine I have tried to ascertain it actually arrives at this code when rebooting from the loader, but it does not seem to ever make it there, at least not to the jump to f000:fff0. Maybe VMware intercepts the switching back to real mode in the previous part, and dies on that, I am not sure. It is of course rather tricky to print off any debug messages at that point. :-) From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 16:05:09 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 69D2D4BE for ; Tue, 23 Apr 2013 16:05:09 +0000 (UTC) (envelope-from benjamin.villain@gmail.com) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by mx1.freebsd.org (Postfix) with ESMTP id 01BE21D90 for ; Tue, 23 Apr 2013 16:05:08 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id f11so373068wgh.27 for ; Tue, 23 Apr 2013 09:05:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=81OUYyjWC06m32TESAcH6J9mYVMSzQc+JeHu4u+DF3M=; b=ovLnUGIeKjiyKTaYnYc3vydhyIQ82aZ7Fiw2Onqz9FuwzD8lt7NTlb9EBjlxkRtowg yQTvfl1Jm/pwdyGJkVHxieM2CrVh2D/w8yszjCO0t2hK6iIZeVpSYQ99z3X2u2KW/LgZ dn2ijXP3C7GI9eJDWz1LfuCg5Q1T8PMz1APF3AOpwAUw2dDss5h58m9jjjoG784KAcCl 2ta7gClqWt5pWjQ6ehoAvLfBQvKIwrYbYJTx4YZA0ujefBWefuQ2WpHLpFD9bF1fSOWH EQzTDWhJza/y1epSObQOhS6GiR9TuubSi+mC74MzQUXS2dEPjsTOmeAzsA746KsRwkVf /R3g== MIME-Version: 1.0 X-Received: by 10.194.119.33 with SMTP id kr1mr62310424wjb.36.1366733108104; Tue, 23 Apr 2013 09:05:08 -0700 (PDT) Received: by 10.194.236.129 with HTTP; Tue, 23 Apr 2013 09:05:08 -0700 (PDT) In-Reply-To: <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> References: <20130419162834.GA90217@icarus.home.lan> <20130420014821.GA98555@icarus.home.lan> <5172812A.10309@gmail.com> <201304221129.43119.jhb@freebsd.org> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> Date: Tue, 23 Apr 2013 18:05:08 +0200 Message-ID: Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation From: Benjamin VILLAIN To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Jeremy Chadwick X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 16:05:09 -0000 A little more information in that subject, rebooting from the FreeBSD bootloader doesn't work on VirtualBox either (version 4.2). It juste enter an infinite loop without any error message (Grub does reboot). Hope this could help understanding what's going on here :) -- Ben On Tue, Apr 23, 2013 at 4:36 PM, Dimitry Andric wrote: > On Apr 22, 2013, at 17:29, John Baldwin wrote: > > On Saturday, April 20, 2013 7:51:06 am Joshua Isom wrote: > >> On 4/19/2013 8:48 PM, Jeremy Chadwick wrote: > >>> I'm happy to open up a ticket with VMware about the issue as I'm a > >>> customer, but I find it a little odd that other operating systems do > not > >>> exhibit this problem, including another BSD. Ones which reboot just > >>> fine from their bootloaders: > >>> > >>> - Linux -- so many that I don't know where to begin: ArchLinux > >>> 2012.10.06, CentOS 6.3, Debian 6.0.7, Finnix 1.0.5, Knoppix 7.0.4, > >>> Slackware 14.0, and Ubuntu 11.10 > >>> - OpenBSD 5.2 > >>> - OpenIndiana -- build 151a7 (server version) > >>> > >>> So when you say "Blame VMware", I'd be happy to, except there must be > >>> something FreeBSD's bootstraps are doing differently than everyone else > >>> that causes this oddity. Would you not agree? > >> > >> A triple fault is standard practice as a fail safe guarantee of reboot. > >> It's used either as a reboot, switch to real mode(IBM OS/2), or > >> catastrophic unrecoverable failure. > >> > >> By the looks of grub(Linux and Solaris), it either jumps to it's own > >> instruction, hoping the bios catches it("tell the BIOS a boot failure, > >> which may result in no effect"), or jumps to a location that I can't yet > >> determine what code exists there. I can't seem to find OpenBSD's reboot > >> method from OpenBSD's cvsweb, only an exit but not where that exit leads > >> to. The native operating system is irrelevant, only the boot loader so > >> all the Linux distributions and Solaris forks all count as "grub." Many > >> other bootloaders don't even have the reboot option, just "fail." > >> Here's barebox, a Das U-Boot fork: > >> > >> /** How to reset the machine? */ > >> while(1) > >> > >> In any case, it's a bag of tricks, finding something that works and is > >> "nice." We're talking 30 years of legacy. A triple fault, assuming the > >> mbr and loader ignores or zeroes previous memory, is guaranteed and > >> doesn't hang. > > > > Actually, the traditional reboot method in real-mode (e.g. in DOS) is > > to jump to 0xffff:0. The BIOS is supposed to have a restart routine > > at that location. I've also seen jumps to 0xf000:fff0. > > > > For example, BTX (the mini-kernel that "hosts" the loader and boot2) > > uses the latter: > > > > /* > > * Reboot or await reset. > > */ > > sti # Enable interrupts > > testb $0x1,btx_hdr+0x7 # Reboot? > > exit.3: jz exit.3 # No > > movw $0x1234, BDA_BOOT # Do a warm boot > > ljmp $0xf000,$0xfff0 # reboot the machine > > I have tried to ascertain it actually arrives at this code when > rebooting from the loader, but it does not seem to ever make it there, > at least not to the jump to f000:fff0. Maybe VMware intercepts the > switching back to real mode in the previous part, and dies on that, I am > not sure. It is of course rather tricky to print off any debug messages > at that point. :-) > > _______________________________________________ > 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 Tue Apr 23 16:09:33 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4512FA08; Tue, 23 Apr 2013 16:09:33 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 27C7B1E2F; Tue, 23 Apr 2013 16:09:31 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA19010; Tue, 23 Apr 2013 19:09:29 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <5176B238.7030306@FreeBSD.org> Date: Tue, 23 Apr 2013 19:09:28 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5 MIME-Version: 1.0 To: Dimitry Andric , John Baldwin Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation References: <20130419162834.GA90217@icarus.home.lan> <20130420014821.GA98555@icarus.home.lan> <5172812A.10309@gmail.com> <201304221129.43119.jhb@freebsd.org> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> In-Reply-To: <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Jeremy Chadwick , freebsd-hackers@FreeBSD.org, Joshua Isom X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 16:09:33 -0000 on 23/04/2013 17:36 Dimitry Andric said the following: > I have tried to ascertain it actually arrives at this code when > rebooting from the loader, but it does not seem to ever make it there, > at least not to the jump to f000:fff0. Maybe VMware intercepts the > switching back to real mode in the previous part, and dies on that, I am > not sure. It is of course rather tricky to print off any debug messages > at that point. :-) For the inquisitive minds here how last instructions (and CPU state) look according to qemu log: IN: 0x000000000000a030: xor %eax,%eax 0x000000000000a032: int $0x30 ---------------- IN: 0x00000000000093e0: cmp $0x1,%eax 0x00000000000093e3: jne 0x93ff ---------------- IN: 0x00000000000093ff: orb $0x1,%ss:0x9007 0x0000000000009407: jmp 0x90d2 ---------------- IN: 0x00000000000090d2: cli 0x00000000000090d3: mov $0x1800,%esp 0x00000000000090d8: mov %cr0,%eax 0x00000000000090db: and $0x7fffffff,%eax 0x00000000000090e0: mov %eax,%cr0 ---------------- IN: 0x00000000000090e3: xor %ecx,%ecx 0x00000000000090e5: mov %ecx,%cr3 ---------------- IN: 0x00000000000090e8: lgdtl 0x95d0 0x00000000000090ef: ljmpw $0x18,$0x90f5 Triple fault CPU Reset (CPU 0) ESI=0004503c EDI=3fe50968 EBP=00094a80 ESP=00001800 EIP=000090ef EFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] CS =0008 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] DS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] FS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] GS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT TR =0038 00005f98 00002067 00008900 DPL=0 TSS32-avl GDT= ff85c789 00000000 IDT= 00005e00 00000197 CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 CCS=00000001 CCD=00000000 CCO=LOGICL EFER=0000000000000000 -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 17:32:37 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E69291D2; Tue, 23 Apr 2013 17:32:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CD50512B5; Tue, 23 Apr 2013 17:32:36 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA19803; Tue, 23 Apr 2013 20:32:35 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <5176C5B2.3050409@FreeBSD.org> Date: Tue, 23 Apr 2013 20:32:34 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5 MIME-Version: 1.0 To: Dimitry Andric , John Baldwin Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation References: <20130419162834.GA90217@icarus.home.lan> <20130420014821.GA98555@icarus.home.lan> <5172812A.10309@gmail.com> <201304221129.43119.jhb@freebsd.org> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> <5176B238.7030306@FreeBSD.org> In-Reply-To: <5176B238.7030306@FreeBSD.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 17:32:38 -0000 on 23/04/2013 19:09 Andriy Gapon said the following: > ---------------- > IN: > 0x00000000000090d2: cli > 0x00000000000090d3: mov $0x1800,%esp > 0x00000000000090d8: mov %cr0,%eax > 0x00000000000090db: and $0x7fffffff,%eax > 0x00000000000090e0: mov %eax,%cr0 > > ---------------- > IN: > 0x00000000000090e3: xor %ecx,%ecx > 0x00000000000090e5: mov %ecx,%cr3 > > ---------------- > IN: > 0x00000000000090e8: lgdtl 0x95d0 > 0x00000000000090ef: ljmpw $0x18,$0x90f5 Perhaps the problem is that lgdt is called after disabling paging? > Triple fault > CPU Reset (CPU 0) > ESI=0004503c EDI=3fe50968 EBP=00094a80 ESP=00001800 > EIP=000090ef EFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 > ES =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > CS =0008 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-] > SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] > DS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > FS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > GS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT > TR =0038 00005f98 00002067 00008900 DPL=0 TSS32-avl > GDT= ff85c789 00000000 > IDT= 00005e00 00000197 > CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000 > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 > DR6=00000000ffff0ff0 DR7=0000000000000400 > CCS=00000001 CCD=00000000 CCO=LOGICL > EFER=0000000000000000 > -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 17:34:32 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 78BD52F3; Tue, 23 Apr 2013 17:34:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 524CF12D9; Tue, 23 Apr 2013 17:34:32 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 54E80B926; Tue, 23 Apr 2013 13:34:30 -0400 (EDT) From: John Baldwin To: Andriy Gapon Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation Date: Tue, 23 Apr 2013 12:31:38 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <20130419162834.GA90217@icarus.home.lan> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> <5176B238.7030306@FreeBSD.org> In-Reply-To: <5176B238.7030306@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201304231231.38765.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 23 Apr 2013 13:34:30 -0400 (EDT) Cc: Jeremy Chadwick , freebsd-hackers@freebsd.org, Joshua Isom , Dimitry Andric X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 17:34:32 -0000 On Tuesday, April 23, 2013 12:09:28 pm Andriy Gapon wrote: > on 23/04/2013 17:36 Dimitry Andric said the following: > > I have tried to ascertain it actually arrives at this code when > > rebooting from the loader, but it does not seem to ever make it there, > > at least not to the jump to f000:fff0. Maybe VMware intercepts the > > switching back to real mode in the previous part, and dies on that, I am > > not sure. It is of course rather tricky to print off any debug messages > > at that point. :-) > > For the inquisitive minds here how last instructions (and CPU state) look > according to qemu log: > > IN: > 0x000000000000a030: xor %eax,%eax > 0x000000000000a032: int $0x30 > > ---------------- > IN: > 0x00000000000093e0: cmp $0x1,%eax > 0x00000000000093e3: jne 0x93ff > > ---------------- > IN: > 0x00000000000093ff: orb $0x1,%ss:0x9007 > 0x0000000000009407: jmp 0x90d2 > > ---------------- > IN: > 0x00000000000090d2: cli > 0x00000000000090d3: mov $0x1800,%esp > 0x00000000000090d8: mov %cr0,%eax > 0x00000000000090db: and $0x7fffffff,%eax > 0x00000000000090e0: mov %eax,%cr0 > > ---------------- > IN: > 0x00000000000090e3: xor %ecx,%ecx > 0x00000000000090e5: mov %ecx,%cr3 > > ---------------- > IN: > 0x00000000000090e8: lgdtl 0x95d0 > 0x00000000000090ef: ljmpw $0x18,$0x90f5 > > Triple fault > CPU Reset (CPU 0) > ESI=0004503c EDI=3fe50968 EBP=00094a80 ESP=00001800 > EIP=000090ef EFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 > ES =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > CS =0008 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-] > SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] > DS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > FS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > GS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT > TR =0038 00005f98 00002067 00008900 DPL=0 TSS32-avl > GDT= ff85c789 00000000 This seems wrong (address is way too high). I wonder if the gdtdesc was trashed by something? Can you dump memory before the lgdtl instruction at the 0x95d0 address? -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 17:52:30 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5BC3DA07 for ; Tue, 23 Apr 2013 17:52:30 +0000 (UTC) (envelope-from vijju.singh@gmail.com) Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47]) by mx1.freebsd.org (Postfix) with ESMTP id EC66413CB for ; Tue, 23 Apr 2013 17:52:29 +0000 (UTC) Received: by mail-ee0-f47.google.com with SMTP id b57so384173eek.6 for ; Tue, 23 Apr 2013 10:52:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=cwoJB8yI68udH27zgNVqpCZBclNqUofD/Fu+8eVvLXo=; b=E77pVzldBYHbj93AWDcEliD2m2Fa+/KXMhsqUJ3MSTT4cq4Y79kW0KRWoUSm2U4aHZ MsmaKwoTUELcc4auOMwC+PQXL7AqssaLnuEpJWHpv32ojBORtDzjgX+HyUbe4ZL9hUlf rJJC4UpJmiSwglr33X/qxXVmlCnEg2FRi4ZVS/2/UaMH/24C2iw3YHKOBtCsTviPe5Vq Z0RKCPedgZEEjntvShpr0a1stIhMXjUVaU8fNtCYxOrIO6kxIPlH75g45aXbrLDXKByB fAWIfW8pzF3AH7vg8hTPbc2zL34lati7UJGH/GIHEvJpn59RGVaHy2rfjVE8j/69HTJH MjDQ== MIME-Version: 1.0 X-Received: by 10.14.173.71 with SMTP id u47mr18136004eel.24.1366739096589; Tue, 23 Apr 2013 10:44:56 -0700 (PDT) Received: by 10.223.202.137 with HTTP; Tue, 23 Apr 2013 10:44:56 -0700 (PDT) Date: Tue, 23 Apr 2013 10:44:56 -0700 Message-ID: Subject: vmspace_fork() From: Vijay Singh To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 17:52:30 -0000 Hackers, what does hitting the following assert in vmspace_fork() imply? 3101 new_map = &vm2 ->vm_map ; 3102 locked = vm_map_trylock (new_map); */* trylock to silence WITNESS */* 3103 KASSERT (locked , (*"vmspace_fork: lock failed"*)); I am hitting the assert in line 3103 and it seems like the assumption is that the trylock will always get the lock? -vijay From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 18:15:40 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A669314C; Tue, 23 Apr 2013 18:15:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 8288115AB; Tue, 23 Apr 2013 18:15:40 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F1969B948; Tue, 23 Apr 2013 14:15:39 -0400 (EDT) From: John Baldwin To: Andriy Gapon Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation Date: Tue, 23 Apr 2013 14:15:31 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <20130419162834.GA90217@icarus.home.lan> <5176B238.7030306@FreeBSD.org> <5176C5B2.3050409@FreeBSD.org> In-Reply-To: <5176C5B2.3050409@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201304231415.31935.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 23 Apr 2013 14:15:40 -0400 (EDT) Cc: freebsd-hackers@freebsd.org, Dimitry Andric X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 18:15:40 -0000 On Tuesday, April 23, 2013 1:32:34 pm Andriy Gapon wrote: > on 23/04/2013 19:09 Andriy Gapon said the following: > > ---------------- > > IN: > > 0x00000000000090d2: cli > > 0x00000000000090d3: mov $0x1800,%esp > > 0x00000000000090d8: mov %cr0,%eax > > 0x00000000000090db: and $0x7fffffff,%eax > > 0x00000000000090e0: mov %eax,%cr0 > > > > ---------------- > > IN: > > 0x00000000000090e3: xor %ecx,%ecx > > 0x00000000000090e5: mov %ecx,%cr3 > > > > ---------------- > > IN: > > 0x00000000000090e8: lgdtl 0x95d0 > > 0x00000000000090ef: ljmpw $0x18,$0x90f5 > > Perhaps the problem is that lgdt is called after disabling paging? That should be fine. Generally speaking paging shouldn't be enabled anyway (it only is if the i386 kernel panics before it has setup its own IDT). With paging disabled that should load the gdt from that physical address which looks correct (the GDT descriptor is stored just after the static gdt in btx.S itself). > > Triple fault > > CPU Reset (CPU 0) > > ESI=0004503c EDI=3fe50968 EBP=00094a80 ESP=00001800 > > EIP=000090ef EFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 > > ES =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > > CS =0008 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-] > > SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] > > DS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > > FS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > > GS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] > > LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT > > TR =0038 00005f98 00002067 00008900 DPL=0 TSS32-avl > > GDT= ff85c789 00000000 > > IDT= 00005e00 00000197 > > CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000 > > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 > > DR6=00000000ffff0ff0 DR7=0000000000000400 > > CCS=00000001 CCD=00000000 CCO=LOGICL > > EFER=0000000000000000 > > > > > -- > Andriy Gapon > -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 18:48:31 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 38D8B894 for ; Tue, 23 Apr 2013 18:48:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id BE3171705 for ; Tue, 23 Apr 2013 18:48:30 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.6/8.14.6) with ESMTP id r3NImQpq055822; Tue, 23 Apr 2013 21:48:26 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.2 kib.kiev.ua r3NImQpq055822 Received: (from kostik@localhost) by tom.home (8.14.6/8.14.6/Submit) id r3NImQEc055821; Tue, 23 Apr 2013 21:48:26 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 23 Apr 2013 21:48:26 +0300 From: Konstantin Belousov To: Vijay Singh Subject: Re: vmspace_fork() Message-ID: <20130423184826.GD67273@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xOS8do0ZRfB5pORP" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 18:48:31 -0000 --xOS8do0ZRfB5pORP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 23, 2013 at 10:44:56AM -0700, Vijay Singh wrote: > Hackers, what does hitting the following assert in vmspace_fork() imply? >=20 > 3101 > new_map =3D &vm2 ->vm_map > ; > 3102 > locked =3D > vm_map_trylock (new_map); > */* trylock to silence WITNESS */* > 3103 > KASSERT (locked > , (*"vmspace_fork: lock > failed"*)); I have hard time reading this html. >=20 > I am hitting the assert in line 3103 and it seems like the assumption > is that the trylock will > always get the lock? Assuming you are referencing line 3103 of the sys/vm/vm_map.c, yes, the try lock operation must always succeed. The reason is that the new_map AKA vm2 is freshly allocated and its pointer is not yet published for other threads to see. So nothing could own the lock. The try is done to silence the witness warning about the same lock type, as indicated by the comment. --xOS8do0ZRfB5pORP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAEBAgAGBQJRdtd5AAoJEJDCuSvBvK1Bhv0QAIWOzg3zq54VQuEZMfifzdk5 c3T/5h4qrEDBG5djZXj9uCJLLnYxzeS5DCLaloNyKpK6j3dWqWRMeCRgvDnEcI3u zInQTzTOOpojw1+k8fbIgDkOrwusLjBCCwxSN0xIz0n0E0xb22LovQz18mpoccOS E7XvkxpEHTZkX4ed2IFkCYbSSHpG2UXPRPqQPYudcq/LwxJmPRu5LhFY1JKcbWCz 7GMdNfVmN3kz9wCdd8VTW+P+J8D2CEeUnUXWAqZX9dfuTEacI82G9SzpGGah/EP0 Z3+jTYf16iXXvQ6qda4o5FbFrmXxSWpH6nxvcI1XyqK1gqMkEbzgz6VhZ5g0ilJZ dyoV8BC8PrLDo8+s8i0+rYBnOhj05ADNkviDJZ7vNtpJSQifRH5tz31dtf6N0eF0 XXgjdImDNn0iFhloz4YxyGTrQR06M5nN/eSoYXExOHUK5Zm/Na29nuqZ0BFm66/m /t6JNY9tqTXSNvgK3SUilof+xn/PvL3O0C1vHqh+mEZv5sd7+utDicMA+pjEMaVV 74ACQBO7MQrkF5RREO8Fidfsqutfvzd/OV0F4FfA+N7D1OeSFsZkJmISqcZbd20J vTGrRBcNAjCevBsJjewAOZ8b43FGukcQIRZDcsva/+zhGoIMkO+0/uITu60CKLjr yRNs9oNDQBMb7Nwp/EJt =5COm -----END PGP SIGNATURE----- --xOS8do0ZRfB5pORP-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 21:46:55 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C73BF8CE; Tue, 23 Apr 2013 21:46:55 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8BC241109; Tue, 23 Apr 2013 21:46:54 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA22008; Wed, 24 Apr 2013 00:46:52 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1UUl36-000Hck-EV; Wed, 24 Apr 2013 00:46:52 +0300 Message-ID: <51770149.6020802@FreeBSD.org> Date: Wed, 24 Apr 2013 00:46:49 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: John Baldwin Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation References: <20130419162834.GA90217@icarus.home.lan> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> <5176B238.7030306@FreeBSD.org> <201304231231.38765.jhb@freebsd.org> In-Reply-To: <201304231231.38765.jhb@freebsd.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jeremy Chadwick , freebsd-hackers@FreeBSD.org, Joshua Isom , Dimitry Andric X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 21:46:55 -0000 on 23/04/2013 19:31 John Baldwin said the following: > On Tuesday, April 23, 2013 12:09:28 pm Andriy Gapon wrote: >> on 23/04/2013 17:36 Dimitry Andric said the following: >>> I have tried to ascertain it actually arrives at this code when >>> rebooting from the loader, but it does not seem to ever make it there, >>> at least not to the jump to f000:fff0. Maybe VMware intercepts the >>> switching back to real mode in the previous part, and dies on that, I am >>> not sure. It is of course rather tricky to print off any debug messages >>> at that point. :-) >> >> For the inquisitive minds here how last instructions (and CPU state) look >> according to qemu log: >> >> IN: >> 0x000000000000a030: xor %eax,%eax >> 0x000000000000a032: int $0x30 >> >> ---------------- >> IN: >> 0x00000000000093e0: cmp $0x1,%eax >> 0x00000000000093e3: jne 0x93ff >> >> ---------------- >> IN: >> 0x00000000000093ff: orb $0x1,%ss:0x9007 >> 0x0000000000009407: jmp 0x90d2 >> >> ---------------- >> IN: >> 0x00000000000090d2: cli >> 0x00000000000090d3: mov $0x1800,%esp >> 0x00000000000090d8: mov %cr0,%eax >> 0x00000000000090db: and $0x7fffffff,%eax >> 0x00000000000090e0: mov %eax,%cr0 >> >> ---------------- >> IN: >> 0x00000000000090e3: xor %ecx,%ecx >> 0x00000000000090e5: mov %ecx,%cr3 >> >> ---------------- >> IN: >> 0x00000000000090e8: lgdtl 0x95d0 >> 0x00000000000090ef: ljmpw $0x18,$0x90f5 >> >> Triple fault >> CPU Reset (CPU 0) >> ESI=0004503c EDI=3fe50968 EBP=00094a80 ESP=00001800 >> EIP=000090ef EFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 >> ES =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] >> CS =0008 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-] >> SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] >> DS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] >> FS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] >> GS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] >> LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT >> TR =0038 00005f98 00002067 00008900 DPL=0 TSS32-avl >> GDT= ff85c789 00000000 > > This seems wrong (address is way too high). I wonder if the gdtdesc was > trashed by something? Can you dump memory before the lgdtl instruction at the > 0x95d0 address? Looks correct: Breakpoint 1, 0x000090e8 in ?? () (gdb) x/i $eip 0x90e8: lgdtl 0x95d0 (gdb) x/3xh 0x95d0 0x95d0: 0x003f 0x9590 0x0000 (gdb) x/16xh 0x9590 0x9590: 0x0000 0x0000 0x0000 0x0000 0xffff 0x0000 0x9a00 0x00cf 0x95a0: 0xffff 0x0000 0x9300 0x00cf 0xffff 0x0000 0x9a00 0x0000 Nevertheless doing stepi leads to exactly the same triple fault. -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 22:03:14 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CF933D98; Tue, 23 Apr 2013 22:03:14 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id 96F3011B3; Tue, 23 Apr 2013 22:03:14 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::106e:515:ef78:2c64] (unknown [IPv6:2001:7b8:3a7:0:106e:515:ef78:2c64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id EB4415C45; Wed, 24 Apr 2013 00:03:10 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation From: Dimitry Andric In-Reply-To: <51770149.6020802@FreeBSD.org> Date: Wed, 24 Apr 2013 00:03:08 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <650A4439-B258-4FDA-BD5C-C9DEF5DC81ED@FreeBSD.org> References: <20130419162834.GA90217@icarus.home.lan> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> <5176B238.7030306@FreeBSD.org> <201304231231.38765.jhb@freebsd.org> <51770149.6020802@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1503) Cc: Jeremy Chadwick , freebsd-hackers@FreeBSD.org, Joshua Isom X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 22:03:14 -0000 On Apr 23, 2013, at 23:46, Andriy Gapon wrote: > on 23/04/2013 19:31 John Baldwin said the following: >> On Tuesday, April 23, 2013 12:09:28 pm Andriy Gapon wrote: ... >>> 0x00000000000090e8: lgdtl 0x95d0 >>> 0x00000000000090ef: ljmpw $0x18,$0x90f5 >>>=20 >>> Triple fault >>> CPU Reset (CPU 0) >>> ESI=3D0004503c EDI=3D3fe50968 EBP=3D00094a80 ESP=3D00001800 >>> EIP=3D000090ef EFL=3D00000046 [---Z-P-] CPL=3D0 II=3D0 A20=3D1 SMM=3D0= HLT=3D0 >>> ES =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>> CS =3D0008 00000000 ffffffff 00cf9a00 DPL=3D0 CS32 [-R-] >>> SS =3D0010 00000000 ffffffff 00cf9300 DPL=3D0 DS [-WA] >>> DS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>> FS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>> GS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>> LDT=3D0000 00000000 0000ffff 00008200 DPL=3D0 LDT >>> TR =3D0038 00005f98 00002067 00008900 DPL=3D0 TSS32-avl >>> GDT=3D ff85c789 00000000 >>=20 >> This seems wrong (address is way too high). I wonder if the gdtdesc = was=20 >> trashed by something? Can you dump memory before the lgdtl = instruction at the=20 >> 0x95d0 address? >=20 > Looks correct: > Breakpoint 1, 0x000090e8 in ?? () > (gdb) x/i $eip > 0x90e8: lgdtl 0x95d0 > (gdb) x/3xh 0x95d0 > 0x95d0: 0x003f 0x9590 0x0000 > (gdb) x/16xh 0x9590 > 0x9590: 0x0000 0x0000 0x0000 0x0000 0xffff 0x0000 0x9a00 0x00cf > 0x95a0: 0xffff 0x0000 0x9300 0x00cf 0xffff 0x0000 0x9a00 0x0000 >=20 > Nevertheless doing stepi leads to exactly the same triple fault. Is it because lgdt loads the GDT from the ds segment, and ds is now 33, not 0 (or equal to CS, I'm not sure which is correct here)? From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 22:21:04 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EB6E81BB for ; Tue, 23 Apr 2013 22:21:03 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com [209.85.220.171]) by mx1.freebsd.org (Postfix) with ESMTP id AD40F1273 for ; Tue, 23 Apr 2013 22:21:03 +0000 (UTC) Received: by mail-vc0-f171.google.com with SMTP id ha11so1207987vcb.30 for ; Tue, 23 Apr 2013 15:20:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=fPqGGggix1OBe6yFL1sWciVMn5kd4BQdmPpvs4Y+2rc=; b=PCWPVeCUzMdhuwU3VYZMXmpU2Y729wApzTiefpeOVSJ+EpS6UPs3qrTuWBwvkF6xmi n4McA8VYW++oLnNOFKPCTPbVgw2DFzjW0LkvRiuLA2x3ri2coT5os0h1j1rFe33fWri9 Zeix7qqERcbHRJ2qPN3uayYKkXtn2ZJsLZfTn741eQTDu0qEYSWZepdKwiMZCEQ2nw71 kK5/H/XsKCx5NGhSjrjzgtkBgwm8swwhqdUlKgc8Q4z3rXswVD2OUJ16F2tNMVaTdxQa RJC3lVSvatxRTT/t8c4jTLOD5oPxs3x5Iupdkwkypr2UnfwczRtCA1o+XmtC3H3hIYS2 zFPw== X-Received: by 10.52.164.139 with SMTP id yq11mr20514922vdb.36.1366755657567; Tue, 23 Apr 2013 15:20:57 -0700 (PDT) Received: from [97.251.37.249] (249.sub-97-251-37.myvzw.com. [97.251.37.249]) by mx.google.com with ESMTPSA id l6sm319222vdh.3.2013.04.23.15.20.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 23 Apr 2013 15:20:56 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> X-Mailer: iPhone Mail (10B329) From: Mark Saad Subject: Re: GSOC: Qt front-ends Date: Tue, 23 Apr 2013 18:20:51 -0400 To: Justin Edward Muniz X-Gm-Message-State: ALoCoQmUVwsFe5E2JBvLK+7hL+k9hwTY2MbGLUpqD8gg8H3GL9ByXARKpn3n+E0fQCZoaWqJvtmb Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 22:21:04 -0000 On Apr 21, 2013, at 4:11 PM, Justin Edward Muniz wr= ote: > Hello everyone once again, >=20 > I decided to split this from my previous thread because the nature of > my questions has changed. I benefited from the last thread, and I am > grateful to those who responded to it. >=20 > For me Google Summer of Code is a big opportunity, and my interest in > contributing to the open source community is fairly limited to FreeBSD for= > many reasons. I know that my application may have a better chance of being= > approved if I have a mentor to help me with my endeavors. >=20 > I currently have three project ideas in mind; however I need to > understand which one would be the most beneficial, and try to find a > mentor, before I create my proposal. Eventually I would like to develop > each application and release them along with a meta-package that comprises= > of them all. For now, I need to focus on just one of the three. >=20 > Originally I was interested in developing a Qt front-end for > freebsd-update; indeed most of my research has been for that project. > However, I am also interested in furthering kports -- which seems to be > notoriously buggy, has broken package functionality, and is a mammoth of a= n > application; the last development for kports was in 2009. I also am > interested in developing a graphical application to customize the FreeBSD > kernel. >=20 > I have compiled a list of features that I would like to concentrate on= > for each project. Some of the features are far less important than others,= > so my actual application may omit some of them, or consider them optional.= > If it would be appropriate I will certainly share my lists, but since the > lists are long I don't want to spam the mailing-list. I am new to this > community after all! >=20 > If anyone is interested in discussing these possibilities or just one > of them in particular, I will greatly appreciate any advice, insight, > concerns, criticism, or ideas. Ideally I am also looking to talk with > anyone who might be interested in mentoring my Google Summer of Code > project. >=20 > Justin Muniz > ______________________________ Justin I say stick to FreeBSD-update . My reason is, as Pkgng becomes more p= opular , a front end for ports will be less useful as binary packages become= more popular . Kports is a monster program , you should set a reasonable go= al ,and target dates; which may be hard with a cleanup project . Also a up= date notifier for kde that handles FreeBSD update would be very useful .=20 My 2cents . --- Mark saad | mark.saad@longcount.org From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 23:03:38 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 58AD0C51; Tue, 23 Apr 2013 23:03:38 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id 0A3B713BD; Tue, 23 Apr 2013 23:03:38 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::106e:515:ef78:2c64] (unknown [IPv6:2001:7b8:3a7:0:106e:515:ef78:2c64]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id DB1FD5C45; Wed, 24 Apr 2013 01:03:34 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation From: Dimitry Andric In-Reply-To: <650A4439-B258-4FDA-BD5C-C9DEF5DC81ED@FreeBSD.org> Date: Wed, 24 Apr 2013 01:03:31 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <4735123C-E912-4D32-80D4-D057E2821626@FreeBSD.org> References: <20130419162834.GA90217@icarus.home.lan> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> <5176B238.7030306@FreeBSD.org> <201304231231.38765.jhb@freebsd.org> <51770149.6020802@FreeBSD.org> <650A4439-B258-4FDA-BD5C-C9DEF5DC81ED@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1503) Cc: Jeremy Chadwick , freebsd-hackers@FreeBSD.org, Joshua Isom X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 23:03:38 -0000 On Apr 24, 2013, at 00:03, Dimitry Andric wrote: > On Apr 23, 2013, at 23:46, Andriy Gapon wrote: >> on 23/04/2013 19:31 John Baldwin said the following: >>> On Tuesday, April 23, 2013 12:09:28 pm Andriy Gapon wrote: > ... >>>> 0x00000000000090e8: lgdtl 0x95d0 >>>> 0x00000000000090ef: ljmpw $0x18,$0x90f5 >>>>=20 >>>> Triple fault >>>> CPU Reset (CPU 0) >>>> ESI=3D0004503c EDI=3D3fe50968 EBP=3D00094a80 ESP=3D00001800 >>>> EIP=3D000090ef EFL=3D00000046 [---Z-P-] CPL=3D0 II=3D0 A20=3D1 = SMM=3D0 HLT=3D0 >>>> ES =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>>> CS =3D0008 00000000 ffffffff 00cf9a00 DPL=3D0 CS32 [-R-] >>>> SS =3D0010 00000000 ffffffff 00cf9300 DPL=3D0 DS [-WA] >>>> DS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>>> FS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>>> GS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>>> LDT=3D0000 00000000 0000ffff 00008200 DPL=3D0 LDT >>>> TR =3D0038 00005f98 00002067 00008900 DPL=3D0 TSS32-avl >>>> GDT=3D ff85c789 00000000 >>>=20 >>> This seems wrong (address is way too high). I wonder if the gdtdesc = was=20 >>> trashed by something? Can you dump memory before the lgdtl = instruction at the=20 >>> 0x95d0 address? >>=20 >> Looks correct: >> Breakpoint 1, 0x000090e8 in ?? () >> (gdb) x/i $eip >> 0x90e8: lgdtl 0x95d0 >> (gdb) x/3xh 0x95d0 >> 0x95d0: 0x003f 0x9590 0x0000 >> (gdb) x/16xh 0x9590 >> 0x9590: 0x0000 0x0000 0x0000 0x0000 0xffff 0x0000 0x9a00 = 0x00cf >> 0x95a0: 0xffff 0x0000 0x9300 0x00cf 0xffff 0x0000 0x9a00 = 0x0000 >>=20 >> Nevertheless doing stepi leads to exactly the same triple fault. >=20 >=20 > Is it because lgdt loads the GDT from the ds segment, and ds is now = 33, > not 0 (or equal to CS, I'm not sure which is correct here)? Indeed, the DS segment was incorrect, the GDT should be loaded from the CS segment instead. This diff fixes the issue for me (and now "reboot" command from loader nicely reboots in VMware): Index: sys/boot/i386/btx/btx/btx.S =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/boot/i386/btx/btx/btx.S (revision 248910) +++ sys/boot/i386/btx/btx/btx.S (working copy) @@ -248,7 +248,7 @@ exit: cli = # Disable interrupts /* * Restore the GDT in case we caught a kernel trap. */ - lgdt gdtdesc # Set GDT + lgdt %cs:gdtdesc # Set GDT /* * To 16 bits. */ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 23 23:11:24 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A964CD93; Tue, 23 Apr 2013 23:11:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-x22b.google.com (mail-da0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 78F1C1437; Tue, 23 Apr 2013 23:11:24 +0000 (UTC) Received: by mail-da0-f43.google.com with SMTP id u36so575329dak.30 for ; Tue, 23 Apr 2013 16:11:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UpOSoI/f7aU3ztHUzBoayNpLR0/nrqsrBjsNaHA6hfo=; b=ajpFHw8BGS2Ss5ey3499bdnJfAZ4aZFZVr79wemGbNcxEuSRDxObfEQGLqkW5nkQpD 23uWJM0Fc0wh64rA7fGC15mxuJct9WfQvEFALO+mLd5IbXEVd8TAwjuX3DdDgyEr3qlG Ts3UK951eThkZ9KcyHzcw7ELFWjP3naQXcnhncF8ZjaGVZ3Oh/gtkaJgZZa/zBm5SDJn qIpNn89PGNbf2Nomb7Z1bhseUnpTPhWwXquNEcvUygvkMwqQIznZaw5OCIiY4GBxmHdW mYzFP2A9hGjbfPHXxxlQE+/rKKT96g2ZeUkhlSaQK0SyxLhdF8g4KcAV/zxaQuE+2pLi bDsw== MIME-Version: 1.0 X-Received: by 10.69.0.200 with SMTP id ba8mr45260374pbd.4.1366758684311; Tue, 23 Apr 2013 16:11:24 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.37.234 with HTTP; Tue, 23 Apr 2013 16:11:24 -0700 (PDT) In-Reply-To: <4735123C-E912-4D32-80D4-D057E2821626@FreeBSD.org> References: <20130419162834.GA90217@icarus.home.lan> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> <5176B238.7030306@FreeBSD.org> <201304231231.38765.jhb@freebsd.org> <51770149.6020802@FreeBSD.org> <650A4439-B258-4FDA-BD5C-C9DEF5DC81ED@FreeBSD.org> <4735123C-E912-4D32-80D4-D057E2821626@FreeBSD.org> Date: Tue, 23 Apr 2013 16:11:24 -0700 X-Google-Sender-Auth: 47fpOoGi4UIARhQ5EyOiW6yIuys Message-ID: Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation From: Adrian Chadd To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 Cc: Jeremy Chadwick , freebsd-hackers@freebsd.org, Joshua Isom , Andriy Gapon X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 23:11:24 -0000 Hah, nice catch! You guys rock. Scratch one less weird shit thing with FreeBSD on VMWARE. Adrian On 23 April 2013 16:03, Dimitry Andric wrote: > > On Apr 24, 2013, at 00:03, Dimitry Andric wrote: > >> On Apr 23, 2013, at 23:46, Andriy Gapon wrote: >>> on 23/04/2013 19:31 John Baldwin said the following: >>>> On Tuesday, April 23, 2013 12:09:28 pm Andriy Gapon wrote: >> ... >>>>> 0x00000000000090e8: lgdtl 0x95d0 >>>>> 0x00000000000090ef: ljmpw $0x18,$0x90f5 >>>>> >>>>> Triple fault >>>>> CPU Reset (CPU 0) >>>>> ESI=0004503c EDI=3fe50968 EBP=00094a80 ESP=00001800 >>>>> EIP=000090ef EFL=00000046 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 >>>>> ES =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] >>>>> CS =0008 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-] >>>>> SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA] >>>>> DS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] >>>>> FS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] >>>>> GS =0033 0000a000 ffffffff 00cff300 DPL=3 DS [-WA] >>>>> LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT >>>>> TR =0038 00005f98 00002067 00008900 DPL=0 TSS32-avl >>>>> GDT= ff85c789 00000000 >>>> >>>> This seems wrong (address is way too high). I wonder if the gdtdesc was >>>> trashed by something? Can you dump memory before the lgdtl instruction at the >>>> 0x95d0 address? >>> >>> Looks correct: >>> Breakpoint 1, 0x000090e8 in ?? () >>> (gdb) x/i $eip >>> 0x90e8: lgdtl 0x95d0 >>> (gdb) x/3xh 0x95d0 >>> 0x95d0: 0x003f 0x9590 0x0000 >>> (gdb) x/16xh 0x9590 >>> 0x9590: 0x0000 0x0000 0x0000 0x0000 0xffff 0x0000 0x9a00 0x00cf >>> 0x95a0: 0xffff 0x0000 0x9300 0x00cf 0xffff 0x0000 0x9a00 0x0000 >>> >>> Nevertheless doing stepi leads to exactly the same triple fault. >> >> >> Is it because lgdt loads the GDT from the ds segment, and ds is now 33, >> not 0 (or equal to CS, I'm not sure which is correct here)? > > Indeed, the DS segment was incorrect, the GDT should be loaded from the > CS segment instead. This diff fixes the issue for me (and now "reboot" > command from loader nicely reboots in VMware): > > Index: sys/boot/i386/btx/btx/btx.S > =================================================================== > --- sys/boot/i386/btx/btx/btx.S (revision 248910) > +++ sys/boot/i386/btx/btx/btx.S (working copy) > @@ -248,7 +248,7 @@ exit: cli # Disable interrupts > /* > * Restore the GDT in case we caught a kernel trap. > */ > - lgdt gdtdesc # Set GDT > + lgdt %cs:gdtdesc # Set GDT > /* > * To 16 bits. > */ > > _______________________________________________ > 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 Tue Apr 23 23:18:25 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 36D2BECD; Tue, 23 Apr 2013 23:18:25 +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 F38C51475; Tue, 23 Apr 2013 23:18:24 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa02.fnfis.com (8.14.5/8.14.5) with ESMTP id r3NNIOot032032 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 23 Apr 2013 18:18:24 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Tue, 23 Apr 2013 18:18:23 -0500 From: "Teske, Devin" To: Adrian Chadd Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation Thread-Topic: Rebooting from loader causes a "fault" in VMware Workstation Thread-Index: AQHOPS1WWmBkfRUB50CGHSMu4rHLhJjeeckAgAAx9ICAAKhoAIADYb0AgAGDcACAABoBAIAABjIAgABYD4CAAASPAIAAEN+AgAACNACAAAH0gA== Date: Tue, 23 Apr 2013 23:18:23 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201F1CB34@ltcfiswmsgmb21> References: <20130419162834.GA90217@icarus.home.lan> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> <5176B238.7030306@FreeBSD.org> <201304231231.38765.jhb@freebsd.org> <51770149.6020802@FreeBSD.org> <650A4439-B258-4FDA-BD5C-C9DEF5DC81ED@FreeBSD.org> <4735123C-E912-4D32-80D4-D057E2821626@FreeBSD.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="Windows-1252" Content-ID: <0CB19E95BCFF2545A70F2A5516523A3C@fisglobal.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-04-23_09:2013-04-23,2013-04-23,1970-01-01 signatures=0 Cc: Jeremy Chadwick , "freebsd-hackers@freebsd.org" , Dimitry Andric , Andriy Gapon , Joshua Isom , Devin Teske X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2013 23:18:25 -0000 +1 you rock. I was silently watching this thread from the start, thinking=85 Oh gawd, please don't let this be associated with the massive Forth changes= I've rolled in (this much I had doubted heavily, but kept a watchful eye j= ust in-case). --=20 Devin On Apr 23, 2013, at 4:11 PM, Adrian Chadd wrote: > Hah, nice catch! You guys rock. >=20 > Scratch one less weird shit thing with FreeBSD on VMWARE. >=20 >=20 >=20 > Adrian >=20 > On 23 April 2013 16:03, Dimitry Andric wrote: >>=20 >> On Apr 24, 2013, at 00:03, Dimitry Andric wrote: >>=20 >>> On Apr 23, 2013, at 23:46, Andriy Gapon wrote: >>>> on 23/04/2013 19:31 John Baldwin said the following: >>>>> On Tuesday, April 23, 2013 12:09:28 pm Andriy Gapon wrote: >>> ... >>>>>> 0x00000000000090e8: lgdtl 0x95d0 >>>>>> 0x00000000000090ef: ljmpw $0x18,$0x90f5 >>>>>>=20 >>>>>> Triple fault >>>>>> CPU Reset (CPU 0) >>>>>> ESI=3D0004503c EDI=3D3fe50968 EBP=3D00094a80 ESP=3D00001800 >>>>>> EIP=3D000090ef EFL=3D00000046 [---Z-P-] CPL=3D0 II=3D0 A20=3D1 SMM= =3D0 HLT=3D0 >>>>>> ES =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>>>>> CS =3D0008 00000000 ffffffff 00cf9a00 DPL=3D0 CS32 [-R-] >>>>>> SS =3D0010 00000000 ffffffff 00cf9300 DPL=3D0 DS [-WA] >>>>>> DS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>>>>> FS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>>>>> GS =3D0033 0000a000 ffffffff 00cff300 DPL=3D3 DS [-WA] >>>>>> LDT=3D0000 00000000 0000ffff 00008200 DPL=3D0 LDT >>>>>> TR =3D0038 00005f98 00002067 00008900 DPL=3D0 TSS32-avl >>>>>> GDT=3D ff85c789 00000000 >>>>>=20 >>>>> This seems wrong (address is way too high). I wonder if the gdtdesc = was >>>>> trashed by something? Can you dump memory before the lgdtl instructi= on at the >>>>> 0x95d0 address? >>>>=20 >>>> Looks correct: >>>> Breakpoint 1, 0x000090e8 in ?? () >>>> (gdb) x/i $eip >>>> 0x90e8: lgdtl 0x95d0 >>>> (gdb) x/3xh 0x95d0 >>>> 0x95d0: 0x003f 0x9590 0x0000 >>>> (gdb) x/16xh 0x9590 >>>> 0x9590: 0x0000 0x0000 0x0000 0x0000 0xffff 0x0000 0x9a00 0x00cf >>>> 0x95a0: 0xffff 0x0000 0x9300 0x00cf 0xffff 0x0000 0x9a00 0x0000 >>>>=20 >>>> Nevertheless doing stepi leads to exactly the same triple fault. >>>=20 >>>=20 >>> Is it because lgdt loads the GDT from the ds segment, and ds is now 33, >>> not 0 (or equal to CS, I'm not sure which is correct here)? >>=20 >> Indeed, the DS segment was incorrect, the GDT should be loaded from the >> CS segment instead. This diff fixes the issue for me (and now "reboot" >> command from loader nicely reboots in VMware): >>=20 >> Index: sys/boot/i386/btx/btx/btx.S >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- sys/boot/i386/btx/btx/btx.S (revision 248910) >> +++ sys/boot/i386/btx/btx/btx.S (working copy) >> @@ -248,7 +248,7 @@ exit: cli = # Disable interrupts >> /* >> * Restore the GDT in case we caught a kernel trap. >> */ >> - lgdt gdtdesc # Set GDT >> + lgdt %cs:gdtdesc # Set GDT >> /* >> * To 16 bits. >> */ >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.or= g" > _______________________________________________ > 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. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 04:36:46 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E9ADFB5C for ; Wed, 24 Apr 2013 04:36:46 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 729211E5A for ; Wed, 24 Apr 2013 04:36:46 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id fd20so1201509lab.11 for ; Tue, 23 Apr 2013 21:36:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=HyrXsG6oKq4/CSm0XZKqC30yHELpt1dSg80EGkCbfhM=; b=hGGbXBu3M2UgLLoRbLiwsqA6XN113x/pU+HHGwWydewidxVyZulUfdEcczsA86JaYP g0RfZgLyACAoW6xPxsUBJpdcaimLLL7zLkUaVJ/Yo4qdNrNeIQUEZ8NKOs06YYaXD+FX 1hIaXYu1xnjObR7B/y/ybcrEQp/+FI1WEjfGWcQCMtdzyiOtuPTpMwaFHMLkDmwkDYmQ 9w+Z1i/8P4uZ89IXtddFbATKAmY7RzQzkfMnzdtuDeCmq8zWK+t4EOvdJVJMF83Kom2S qcbOFqdKKpmZ1zw9syG+v6A1gwhfUkzdYt41uikSmB7r8UDDJ5yag1pbR1PU1KOWdbkM l6yA== MIME-Version: 1.0 X-Received: by 10.112.59.103 with SMTP id y7mr16625576lbq.16.1366778204307; Tue, 23 Apr 2013 21:36:44 -0700 (PDT) Received: by 10.112.135.229 with HTTP; Tue, 23 Apr 2013 21:36:44 -0700 (PDT) In-Reply-To: References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> Date: Wed, 24 Apr 2013 00:36:44 -0400 Message-ID: Subject: Fwd: GSOC: Qt front-ends From: Justin Edward Muniz To: freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQmP1WoHNpYSG0gDYEhWuAe4OLo1H7ZcOsLKSdUIjp1eAXtE1nJqiDH8nCrGa+cuAJBYucdk Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 04:36:47 -0000 > > Justin I say stick to FreeBSD-update . My reason is, as Pkgng becomes > more popular , a front end for ports will be less useful as binary packages > become more popular . Kports is a monster program , you should set a > reasonable goal ,and target dates; which may be hard with a cleanup project > . Also a update notifier for kde that handles FreeBSD update would be > very useful . > > My 2cents . > --- > Mark saad | mark.saad@longcount.org > Thank you very much Mark, I was definitely hoping to get community feedback on this, and I value you voicing your opinion. I agree that kports is a mammoth, and also that a system updater GUI should have a way to notify the user of new updates. Any other perspectives are welcome, as well as support for a freebsd-update approach. I am working to refine my proposal, which as you've pointed out is very important. Eventually I would like to help in all three mentioned areas, but for now I must focus on one application. Does anyone think that a custom kernel configuration and management GUI utility would be desirable? I will shape my goals to meet the needs of the community. Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 05:46:12 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1541A39A; Wed, 24 Apr 2013 05:46:12 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id EF1BE1FF1; Wed, 24 Apr 2013 05:46:10 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id IAA26338; Wed, 24 Apr 2013 08:46:09 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1UUsWu-000LCG-OI; Wed, 24 Apr 2013 08:46:08 +0300 Message-ID: <5177719D.5050507@FreeBSD.org> Date: Wed, 24 Apr 2013 08:46:05 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: Dimitry Andric , John Baldwin Subject: Re: Rebooting from loader causes a "fault" in VMware Workstation References: <20130419162834.GA90217@icarus.home.lan> <006B20F1-F67B-4E9D-B0DF-D4ED843F7E8E@FreeBSD.org> <5176B238.7030306@FreeBSD.org> <201304231231.38765.jhb@freebsd.org> <51770149.6020802@FreeBSD.org> <650A4439-B258-4FDA-BD5C-C9DEF5DC81ED@FreeBSD.org> <4735123C-E912-4D32-80D4-D057E2821626@FreeBSD.org> In-Reply-To: <4735123C-E912-4D32-80D4-D057E2821626@FreeBSD.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 05:46:12 -0000 on 24/04/2013 02:03 Dimitry Andric said the following: > Indeed, the DS segment was incorrect, the GDT should be loaded from the > CS segment instead. Very good catch! Indeed the segments at this point were set up for "user" data while the "supervisor" data is needed. Thank you! -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 11:44:56 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 11566302 for ; Wed, 24 Apr 2013 11:44:56 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id DA3201FFB for ; Wed, 24 Apr 2013 11:44:55 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id 10so1884045ied.19 for ; Wed, 24 Apr 2013 04:44:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DkYxrvnn9xkZxxA/o+BA/OfI1p7W4CObJPfkBHs65LU=; b=JMPTAGb9BQZoPbtmAdK6q/LOdWGx7vy2eiHdaYYdLHphY56Q5kqAIXMO30fSHa9WMn hRF76f7pSh4jVT2MPNdg1pTN+JPsex2hWCVNv9ZE9PNV1pdjR3AaTvyAtgecXGxlZks+ 6E1p+Od7hg69l5ZANWAHbpNa5ikHdIf5F6v2PmuzPeEXm3lKr4fm1y34dy8XfQHMRlTy es+Qa+LeSn6e7AR6z4GCGgFw4b0eESXYIWDqPuqkHwCbcy5WgQ+auaTPAyjno9zKw7mh LRmWs+e2ke+fVMdA6dSRKQbebJ/8r7SWC55OVnFq1l8Hry9O4Tt9t/o6JRus7jaMX4id DvnQ== MIME-Version: 1.0 X-Received: by 10.43.47.5 with SMTP id uq5mr18340408icb.0.1366803895606; Wed, 24 Apr 2013 04:44:55 -0700 (PDT) Received: by 10.64.58.52 with HTTP; Wed, 24 Apr 2013 04:44:55 -0700 (PDT) Received: by 10.64.58.52 with HTTP; Wed, 24 Apr 2013 04:44:55 -0700 (PDT) In-Reply-To: References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> Date: Wed, 24 Apr 2013 12:44:55 +0100 Message-ID: Subject: Re: Fwd: GSOC: Qt front-ends From: Chris Rees To: Justin Edward Muniz Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 11:44:56 -0000 On 24 Apr 2013 05:36, "Justin Edward Muniz" wrote: > > > > > Justin I say stick to FreeBSD-update . My reason is, as Pkgng becomes > > more popular , a front end for ports will be less useful as binary packages > > become more popular . Kports is a monster program , you should set a > > reasonable goal ,and target dates; which may be hard with a cleanup project > > . Also a update notifier for kde that handles FreeBSD update would be > > very useful . > > > > My 2cents . > > --- > > Mark saad | mark.saad@longcount.org > > > > > Thank you very much Mark, > > I was definitely hoping to get community feedback on this, and I value > you voicing your opinion. I agree that kports is a mammoth, and also that a > system updater GUI should have a way to notify the user of new updates. > > Any other perspectives are welcome, as well as support for a > freebsd-update approach. I am working to refine my proposal, which as > you've pointed out is very important. Eventually I would like to help in > all three mentioned areas, but for now I must focus on one application. > Does anyone think that a custom kernel configuration and management GUI > utility would be desirable? > > I will shape my goals to meet the needs of the community. Our kernel is actually very easy to configure, so I'm not convinced that it's needed; you may be thinking of Linux's menuconfig, but I think that is because of the complexity. Chris From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 12:24:19 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B182EE63 for ; Wed, 24 Apr 2013 12:24:19 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 4932A11CE for ; Wed, 24 Apr 2013 12:24:19 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id m15so2150321wgh.1 for ; Wed, 24 Apr 2013 05:24:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=r0b2dzpIgTU0d5InONsxIgouwV20QvnR/YmcjiXMghg=; b=uH+DYY60lLbkbKQwzdb0D7Q8Xvs1ZWGlk3Xw5/gs/JUv1eb4nUGA6H0JzPbnZ4qJP4 1tEcNbry1iiU1YzUdlMCYRzHwh/Vl98b42xvKFAwkiyG9U87Qs7f4Ex+4noq7E1druk4 Ui5loYLMTwKIQJG6ejGrULE3W2k0hcuZhcbz17Uy76inCDsFxW4QivAJcfNyCHYquGRr wTfVWrINMG8gh59IOQIp7aJuobW4HdJLSEobzqM5Q+cZOFQUXF9YpT8zPzl/9w9TMEA+ sVi7stbsdsX3N7aSzv+yGnU9h45Bl7Aqhpo28G5PxM8u67cFzayEclgohLN/PCXd22sN fg0A== MIME-Version: 1.0 X-Received: by 10.180.83.199 with SMTP id s7mr43642123wiy.19.1366806255150; Wed, 24 Apr 2013 05:24:15 -0700 (PDT) Received: by 10.180.100.130 with HTTP; Wed, 24 Apr 2013 05:24:15 -0700 (PDT) Received: by 10.180.100.130 with HTTP; Wed, 24 Apr 2013 05:24:15 -0700 (PDT) In-Reply-To: References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> Date: Wed, 24 Apr 2013 14:24:15 +0200 Message-ID: Subject: Re: Fwd: GSOC: Qt front-ends From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: Chris Rees Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Justin Edward Muniz X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 12:24:19 -0000 El 24/04/2013 13:45, "Chris Rees" escribi=F3: > > On 24 Apr 2013 05:36, "Justin Edward Muniz" wrote: > > > > > > > > Justin I say stick to FreeBSD-update . My reason is, as Pkgng become= s > > > more popular , a front end for ports will be less useful as binary > packages > > > become more popular . Kports is a monster program , you should set a > > > reasonable goal ,and target dates; which may be hard with a cleanup > project > > > . Also a update notifier for kde that handles FreeBSD update would be > > > very useful . > > > > > > My 2cents . > > > --- > > > Mark saad | mark.saad@longcount.org > > > > > > > > > Thank you very much Mark, > > > > I was definitely hoping to get community feedback on this, and I > value > > you voicing your opinion. I agree that kports is a mammoth, and also that > a > > system updater GUI should have a way to notify the user of new updates. > > > > Any other perspectives are welcome, as well as support for a > > freebsd-update approach. I am working to refine my proposal, which as > > you've pointed out is very important. Eventually I would like to help i= n > > all three mentioned areas, but for now I must focus on one application. > > Does anyone think that a custom kernel configuration and management GUI > > utility would be desirable? > > > > I will shape my goals to meet the needs of the community. > > Our kernel is actually very easy to configure, so I'm not convinced that > it's needed; you may be thinking of Linux's menuconfig, but I think that is > because of the complexity. I agree. Also, the kind of people who compile their kernels probably feel more comfortable in console mode :) The frontend for pkgng and freebsd-update might have a bigger user base. > > Chris > _______________________________________________ > 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 Wed Apr 24 12:43:10 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8CDD64F5 for ; Wed, 24 Apr 2013 12:43:10 +0000 (UTC) (envelope-from lars.engels@0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id 579A012AB for ; Wed, 24 Apr 2013 12:43:10 +0000 (UTC) Received: from 0x20.net (0x20.net [217.69.76.212]) (Authenticated sender: lala) by mail.0x20.net (Postfix) with ESMTPA id C56546A6001 for ; Wed, 24 Apr 2013 14:43:07 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 24 Apr 2013 14:43:07 +0200 From: Lars Engels To: Subject: Re: Fwd: GSOC: Qt front-ends In-Reply-To: References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> Message-ID: <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> X-Sender: lars.engels@0x20.net User-Agent: Roundcube Webmail/0.7 X-Mailman-Approved-At: Wed, 24 Apr 2013 13:13:00 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 12:43:10 -0000 Am 24.04.2013 13:44, schrieb Chris Rees: > On 24 Apr 2013 05:36, "Justin Edward Muniz" > wrote: >> >>> >>> Justin I say stick to FreeBSD-update . My reason is, as Pkgng >>> becomes >>> more popular , a front end for ports will be less useful as binary > packages >>> become more popular . Kports is a monster program , you should set a >>> reasonable goal ,and target dates; which may be hard with a cleanup > project >>> . Also a update notifier for kde that handles FreeBSD update would >>> be >>> very useful . >>> >>> My 2cents . >>> --- >>> Mark saad | mark.saad@longcount.org >>> >> >> >> Thank you very much Mark, >> >> I was definitely hoping to get community feedback on this, and I > value >> you voicing your opinion. I agree that kports is a mammoth, and also >> that > a >> system updater GUI should have a way to notify the user of new >> updates. >> >> Any other perspectives are welcome, as well as support for a >> freebsd-update approach. I am working to refine my proposal, which as >> you've pointed out is very important. Eventually I would like to help >> in >> all three mentioned areas, but for now I must focus on one >> application. >> Does anyone think that a custom kernel configuration and management >> GUI >> utility would be desirable? >> >> I will shape my goals to meet the needs of the community. > > Our kernel is actually very easy to configure, so I'm not convinced > that > it's needed; you may be thinking of Linux's menuconfig, but I think > that is > because of the complexity. It _is_ easy. But having a nice graphical tool which draws a pretty table of GENERIC and NOTES together with useful information about the possible options and devices would be a handy thing to have IMHO. Let's make FreeBSD userfriendly :-) From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 13:33:03 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 48973B77 for ; Wed, 24 Apr 2013 13:33:03 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-da0-x22a.google.com (mail-da0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 253CC1569 for ; Wed, 24 Apr 2013 13:33:03 +0000 (UTC) Received: by mail-da0-f42.google.com with SMTP id n15so887741dad.29 for ; Wed, 24 Apr 2013 06:33:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1wOcEiXjrw5O1t5RXLNEppZ0vUN+cueRp7PdazIkeLA=; b=TYLnE1W+0zbzK1RECa1hJXQ5jcwG0Ppn/CQv+7M8OMGmF8h9Al0uwmi2T1UOvtchHa OhjI1mLD7h5MKlX2+l6fnwugMh8u3aVIYcrzWxurODG18ELyH6dM0uGhDZKW6CqP3XQ2 EjrWr33wbtMMKqtMsOD7jxyZCgOv1eg5tFct0wQAVR84yC3TQ9nGQfS5+LjCPbEVws+o xdOk+fklF6gotKoNY2PvfZdjRFtR7wWex27SEMased9gei/bqBooeY0yB+v+7CgpStL3 vBdPCh4dVRcd8+DIAAc/YoDyxsmfmpOkkvDvStQjgjf1olm/0JRm6aVMCgLDYEDGtafD nFEw== MIME-Version: 1.0 X-Received: by 10.68.184.100 with SMTP id et4mr41371547pbc.48.1366810382928; Wed, 24 Apr 2013 06:33:02 -0700 (PDT) Received: by 10.68.230.233 with HTTP; Wed, 24 Apr 2013 06:33:02 -0700 (PDT) In-Reply-To: <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> Date: Wed, 24 Apr 2013 16:33:02 +0300 Message-ID: Subject: Re: Fwd: GSOC: Qt front-ends From: Alexander Yerenkow To: Lars Engels Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 13:33:03 -0000 During some tests with cut down kernels one can easily make unbuildable kernel, for example include option A, while omit hiddenly required B. If there could be framework at least with deps tracking/checking, what could be good for begin. Both for configuring, and code clean up. If this will come up in GUI - that would be awesome. -- Regards, Alexander Yerenkow From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 16:18:19 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BC7DD814 for ; Wed, 24 Apr 2013 16:18:19 +0000 (UTC) (envelope-from tony.li@tony.li) Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by mx1.freebsd.org (Postfix) with ESMTP id A11081E4F for ; Wed, 24 Apr 2013 16:18:19 +0000 (UTC) Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta01.emeryville.ca.mail.comcast.net with comcast id TqF31l00D0b6N64A1sJKzk; Wed, 24 Apr 2013 16:18:19 +0000 Received: from [192.168.2.111] ([98.248.36.188]) by omta03.emeryville.ca.mail.comcast.net with comcast id TsJH1l00943ZcXW8PsJHly; Wed, 24 Apr 2013 16:18:18 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: GSOC: Qt front-ends From: Tony Li In-Reply-To: <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> Date: Wed, 24 Apr 2013 09:18:17 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> To: Lars Engels X-Mailer: Apple Mail (2.1503) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1366820299; bh=1WMAasgiakaZ3RMyY/hLx/J0IpLYrCJ9uOnid7ZKssg=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=UNRINxm99lCIi+qPPulx8VtGzCphgtCnEWeP2Egz+SaH1KFCe2511ltlpDJs/soYR +L6/4eLKTMfI01DAFuK+DvqWyPW/TUjixODs7Nv6YSO9+0EwyVfzoByQ5OoR3PTJ2m acHNjZUfAWs7IJh5gq+ngbwuDm35RAeLCHR64yUPhBzL8JzxqWH3Mj7X7LuPMaCSEf YqCsKV7JvHUCIEtzOWUwQ5HEJxRKeoqMMOmAfya+DB1pUO6AaN+7TnKSRQ+jE7zdxG O7h+3Qy1zB7xSOrGTAczkNsk1uqtrqa8MAVlqE92y38pUFmBZc0qupIou1l+56uckQ U7kM6DYANvfig== Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 16:18:19 -0000 On Apr 24, 2013, at 5:43 AM, Lars Engels wrote: > It _is_ easy. But having a nice graphical tool which draws a pretty = table of > GENERIC and NOTES together with useful information about the possible = options > and devices would be a handy thing to have IMHO. > Let's make FreeBSD userfriendly :-) Side note: I agree that we would really, really like FreeBSD more user = friendly. =20 However, is kernel configuration where we really want to start? Just = how much of the user base reconfigures their kernels, anyway? Wouldn't = effort be better spent on making normal installation, maintenance and = deployment clean and easy? Regards, Tony From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 17:28:40 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B38377EF for ; Wed, 24 Apr 2013 17:28:40 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qe0-f45.google.com (mail-qe0-f45.google.com [209.85.128.45]) by mx1.freebsd.org (Postfix) with ESMTP id 78B7A1202 for ; Wed, 24 Apr 2013 17:28:40 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id 1so1407427qee.18 for ; Wed, 24 Apr 2013 10:28:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Ac88KaEXnbqsSFrFvG7mMPFru//o1HYgoJ0stzhJ06c=; b=H9wZIJorjHAKG9JT3BCcishPlA5ZGNnOd/Qx5Tm3POuuXSoxZVTpkBwT71Oo/VHhGp OZYNWQl+yLhrwEaawffIeengjhYDWzDsxEcbF9Zv+dtiH2gOajl4exZauPoc/qNwZfEn 7pHvlgU31va4WCjJHiMEekET+NZg1yG7rU0nbF6ZdUlCNGkPoblVG/licW8rE+Cm2/ld RgU7H80uZxVhdz1t8+VzWGrp+VU+tq8np6LBgowylPZsPy86Ft1WJHj+tZ1c61By9ZH6 qlLTMUEPttl3PXa1fDs2I4XB3DwMCjXXbNE5DjCiH0vrbixHlhMMhfR3BmNjWlkKTXIt NetQ== MIME-Version: 1.0 X-Received: by 10.224.55.140 with SMTP id u12mr31604148qag.77.1366824514066; Wed, 24 Apr 2013 10:28:34 -0700 (PDT) Received: by 10.49.51.9 with HTTP; Wed, 24 Apr 2013 10:28:33 -0700 (PDT) In-Reply-To: <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> Date: Wed, 24 Apr 2013 10:28:33 -0700 Message-ID: Subject: Re: Fwd: GSOC: Qt front-ends From: Freddie Cash To: Lars Engels Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 17:28:40 -0000 On Wed, Apr 24, 2013 at 5:43 AM, Lars Engels wrote: > Am 24.04.2013 13:44, schrieb Chris Rees: > > Our kernel is actually very easy to configure, so I'm not convinced that >> it's needed; you may be thinking of Linux's menuconfig, but I think that >> is >> because of the complexity. >> > > > It _is_ easy. But having a nice graphical tool which draws a pretty table > of > GENERIC and NOTES together with useful information about the possible > options > and devices would be a handy thing to have IMHO. > Let's make FreeBSD userfriendly :-) > Especially if it handles dependencies! For example, check USB Disk Support, and have scbus, da, etc enabled automatically. Or having the LIBICONV stuff enabled if you add MSDOSFS support. And so on. That part of kernel configuration (keeping track of what devices require which options and other devices) is currently the hardest part for newbies (and even for some seasoned kernel compilers!). Yes, the output of "config KERNELNAME" or "buildkernel KERNCONF=KERNELNAME" will tell you about missing dependencies, but it breaks automated compile/install processes. Having the "create kernel config file" step take care of dependencies would be nice. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 17:30:03 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 528A59DF for ; Wed, 24 Apr 2013 17:30:03 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by mx1.freebsd.org (Postfix) with ESMTP id CFDB6121C for ; Wed, 24 Apr 2013 17:30:02 +0000 (UTC) Received: by mail-la0-f45.google.com with SMTP id em20so720311lab.18 for ; Wed, 24 Apr 2013 10:30:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=Dz+1hTRE/vo6iQWemILkbjl0yeaHGMTqJ9J7y+vjOu4=; b=n8CADVcSIiEvdk7ZC3wr7GRB6A5UOrWn+P8J7gJR0qzPlJIbakIqmcj4z11qObHrkj 9nfrIDYlryBu889NQvyA9VtkxHJahkDNGWMHTICD9WU4u4WOfop4jrkt0ycSLMnm77H0 eci1WaSvvxmwdY1nf/k+9QpV9D/2Wv9HiY39E4leOWNMN05w9g7PtRG5SmmUuFli2V0X q1br2fj/PqLIbA9lpiJIVQjOPbk4aaaG3OoREkelDkktfZR1gHqx9APqla+IvInfFxhN yCspFwTIbVFRIhfIeENxYJpQeCiZ93zDZCvUFOz7e6aKAyY6YoswYC93MezkLJUMUPjq /lfQ== MIME-Version: 1.0 X-Received: by 10.152.18.164 with SMTP id x4mr18568383lad.38.1366824601724; Wed, 24 Apr 2013 10:30:01 -0700 (PDT) Received: by 10.112.135.229 with HTTP; Wed, 24 Apr 2013 10:30:01 -0700 (PDT) In-Reply-To: References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> Date: Wed, 24 Apr 2013 13:30:01 -0400 Message-ID: Subject: Re: Fwd: GSOC: Qt front-ends From: Justin Edward Muniz To: Chris Rees , freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQlbz8FquOy74Wfsqyb72RDLLuUDEeKhLxBcyxrX4x6Ih0vOY9QQT45X33mvIIvy38ve4+WG Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 17:30:03 -0000 > > Our kernel is actually very easy to configure, so I'm not convinced that > it's needed; you may be thinking of Linux's menuconfig, but I think that is > because of the complexity. > > Chris > While configuring the kernel may be trivial to someone who understands the process and their systems needs, I am thinking of a software tool that goes beyond the scope of the occasional generating of a kernel configuration file. Imagine that you have a number of systems and you want to run kernels that are lighter weight than the generic kernel but each system has its own individual needs. A GUI could help manage a large number of custom kernels, and provide access to convenient access to features such as specifying a kernel to load on the next boot only for testing. You could even configure the custom kernel profiles to be built from separate source directories. That is not to say of course that everyone else using x11 couldn't benefit from it as well. The application could help avoid compatibility issues during kernel installation by comparing the kernel's version to the version of world. Some helpful aids would be visual categorization of options as well as option descriptions, caveats, and hyperlinks to more in depth information. As for its place in Google Summer of Code, you could be right, it may not be enough to dedicate such resources. I know however that I would use it, maybe others would as well? Thank you for your advice once again Chris! What do you think about the other utilities? Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 17:32:12 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C58EEAE6 for ; Wed, 24 Apr 2013 17:32:12 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id 89FEE1233 for ; Wed, 24 Apr 2013 17:32:12 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id a22so1076954qcs.40 for ; Wed, 24 Apr 2013 10:32:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=PVrZRBsGYD9wg+dWGehTO49SoWj9XBemU0T93KGjdwQ=; b=L7CrFZBnJlEhDk/XEwmE5fCWN9l6WOa9ktSogirg2595OgGUiJ8LtgZwYdyyZ4L0tY v3K2OGrIYImTLlasvqm8JLAsUtu6quh6jB0D5vS+wWbZwlWC0AngwWPBQgOZXhELP5bB ILy4LnRGUgddLnwmpPOB5clg2R3M5cH7bFpcwnKP3SXf4e3nJmQlLGBInKZ25+C8zhH+ aGdI04G9NSUjRAhdGg9EJxsc4rfRPz1a2qK1oUXUN3ccYIlwZr1XK/VtZBUxiWqAbJ9x vgXgp9Rj0MGtrqB+kBj+94dTEA4DY6DCxTMWCMIVr2L2xb33/NjwEy6XaATzJ2VTWADl V98A== MIME-Version: 1.0 X-Received: by 10.224.147.83 with SMTP id k19mr12886670qav.72.1366824732016; Wed, 24 Apr 2013 10:32:12 -0700 (PDT) Received: by 10.49.51.9 with HTTP; Wed, 24 Apr 2013 10:32:11 -0700 (PDT) In-Reply-To: <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> Date: Wed, 24 Apr 2013 10:32:11 -0700 Message-ID: Subject: Re: GSOC: Qt front-ends From: Freddie Cash To: Tony Li Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Lars Engels X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 17:32:12 -0000 On Wed, Apr 24, 2013 at 9:18 AM, Tony Li wrote: > > On Apr 24, 2013, at 5:43 AM, Lars Engels wrote: > > > It _is_ easy. But having a nice graphical tool which draws a pretty > table of > > GENERIC and NOTES together with useful information about the possible > options > > and devices would be a handy thing to have IMHO. > > Let's make FreeBSD userfriendly :-) > > > Side note: I agree that we would really, really like FreeBSD more user > friendly. > > However, is kernel configuration where we really want to start? Just how > much of the user base reconfigures their kernels, anyway? Wouldn't effort > be better spent on making normal installation, maintenance and deployment > clean and easy? > Mostly off-topic for this thread, but improving the boot process to auto-detect hardware and auto-load kernel modules would be really nice. That way, GENERIC would be very small, with just the basic frameworks required (CAM, USB, PCI, TCP/IP, etc), and all the actual drivers would be loaded from modules. That would remove almost all requirements to compile a custom kernel in the first place. :) Granted, changing "options" in the kernel would require recompilation, but general use and hardware changes wouldn't. Most likely not a GSoC project. But it's still a nice dream. :) -- Freddie Cash fjwcash@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 17:43:37 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 06828FD0 for ; Wed, 24 Apr 2013 17:43:37 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id CF12912B7 for ; Wed, 24 Apr 2013 17:43:36 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id c12so2490722ieb.3 for ; Wed, 24 Apr 2013 10:43:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=aG1FWFKNA9wEj+gbrHduClpP7VIlF1BH0FknMlBHWFM=; b=vwf5rRx3sbAUzlQgQFauSTIcQwSZPuRrBud5p6ahHncal2ff6CFZMf+L5tQV+lugMz qRQI+L6QaMdb+y8Wa7O8tm9GSPXw3K25lYZOB7ZWLM9FTWe2CPnsgBRBsgPJhgOEMtoQ k/4Tq4X8dWnb2ZtISHZlBS4gf8gBUYP3t9Jl+F9fkO3V/pN8X9Tw2Moh1DXuXgzj63p5 yx5CIwrmGc8/tixZstDF04TnaOVDHVFKFXS99oFF0k8y034m8aZwkZz8qQ8WCgbXm1Gc ucURFRipgq90AfF3JJIly3r6gJ0kPkwv/d2GnubFWUFDaa3BGmdNZVUPE/O1I9Bfn0Ky sVDg== X-Received: by 10.50.47.10 with SMTP id z10mr15884632igm.15.1366825416596; Wed, 24 Apr 2013 10:43:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.58.52 with HTTP; Wed, 24 Apr 2013 10:43:06 -0700 (PDT) In-Reply-To: References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> From: Chris Rees Date: Wed, 24 Apr 2013 18:43:06 +0100 Message-ID: Subject: Re: Fwd: GSOC: Qt front-ends To: Justin Edward Muniz , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 17:43:37 -0000 On 24 April 2013 18:30, Justin Edward Muniz wrote: >> Our kernel is actually very easy to configure, so I'm not convinced that >> it's needed; you may be thinking of Linux's menuconfig, but I think that is >> because of the complexity. >> >> Chris > > > > While configuring the kernel may be trivial to someone who understands the > process and their systems needs, I am thinking of a software tool that goes > beyond the scope of the occasional generating of a kernel configuration > file. > > Imagine that you have a number of systems and you want to run kernels that > are lighter weight than the generic kernel but each system has its own > individual needs. A GUI could help manage a large number of custom kernels, > and provide access to convenient access to features such as specifying a > kernel to load on the next boot only for testing. You could even configure > the custom kernel profiles to be built from separate source directories. > > That is not to say of course that everyone else using x11 couldn't benefit > from it as well. The application could help avoid compatibility issues > during kernel installation by comparing the kernel's version to the version > of world. Some helpful aids would be visual categorization of options as > well as option descriptions, caveats, and hyperlinks to more in depth > information. > > As for its place in Google Summer of Code, you could be right, it may not be > enough to dedicate such resources. I know however that I would use it, maybe > others would as well? Thank you for your advice once again Chris! What do > you think about the other utilities? I think the interface to pkgng and freebsd-update are still interesting; at least more worthwhile than the kernel configuration one. I think the pkgng one has the edge, since packages are updated far more often than base, and it's easier to track base. Now you are at a stage where you should make your own decision; which one looks the most interesting to you? Once you decide on an area of interest, you can just start hacking :) Chris From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 17:57:49 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9B158539 for ; Wed, 24 Apr 2013 17:57:49 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by mx1.freebsd.org (Postfix) with ESMTP id 28C381338 for ; Wed, 24 Apr 2013 17:57:48 +0000 (UTC) Received: by mail-lb0-f172.google.com with SMTP id u10so2035502lbi.3 for ; Wed, 24 Apr 2013 10:57:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=TwoMMbDeVOquKYrinSgjqsKrK2b4NVoCNX8qImgc/V4=; b=e2/tJ//sgD666Vkf1SRH7MlHAg2NDZ/155EwNARWHuDQDGo7MbevcbwzuHokGOF/Lx r1QSDQGbU/fbCZCm3uC9VtiGnWQTn+Is//aESm8FMr78qSSo/6rWyQiAmxX7cUD5Rtwf DWC430Eh63X4BPci2RvCx8KAnmpo3mOjpnbnmjJDUBqls9j+lyjRXKuPDVn5xUH9QgiA ERPeRNgMLlTNJEJzK1vHiNbgSQhgTXozQEMmPthEfqRttzdLOA8ibZ+S0c+Rjv1y1Zn4 IKY5+w0sJxXCjqwCqx9zhxvLpK/Ceg4E81VtGIFRhAPR6cR7pFceiouCkVyF0sRquMBr VKgQ== MIME-Version: 1.0 X-Received: by 10.112.173.169 with SMTP id bl9mr17738316lbc.37.1366826267651; Wed, 24 Apr 2013 10:57:47 -0700 (PDT) Received: by 10.112.135.229 with HTTP; Wed, 24 Apr 2013 10:57:47 -0700 (PDT) Date: Wed, 24 Apr 2013 13:57:47 -0400 Message-ID: Subject: Fwd: GSOC: Qt front-ends From: Justin Edward Muniz To: freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQnLxmkYbZT1KHr4oBsiqqowD1jka5vhVm5RXa+IjNwy3/RbGuETAtjWjc/DhMSCGZ+CWXS8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 17:57:49 -0000 > > I agree. Also, the kind of people who compile their kernels probably > feel more comfortable in console mode :) > > The frontend for pkgng and freebsd-update might have a bigger user base. > Hello Fernando, thank you for pointing me towards kports earlier. I appreciate your help. It is starting to seem that there is more interest in the GUI pkgng and freebsd-update utilities at present. I do intend to pursue two out of three of them on my time eventually; I'd like to use them all, and see others benefit from them as well. GUI is my fort=E9. Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 17:59:45 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 774EE63A for ; Wed, 24 Apr 2013 17:59:45 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) by mx1.freebsd.org (Postfix) with ESMTP id 03F501352 for ; Wed, 24 Apr 2013 17:59:44 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id eo20so1863257lab.21 for ; Wed, 24 Apr 2013 10:59:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=28PZTgL0d34l73ncUd9t0jxHEGnDCWddRAHQPjkwUSo=; b=MzqICgHs06GB+gQ5Fse7giJ4RfdTh7h7+a1peHPFbxYxJ0MGhub3DtXTe3I28A4FMa KzNcJcnTd3pgXORFbIDhyFEB+72/R0OQxN95ZEOtPzoSKnDgbYk2F8bIIZcaOWbNWs8w k9fYxJ6cEw0qEMTu2+3gbL+ojBmwLKuDU6Xraw3KFW09Z0F/ks/aP0hgTcgfNUL6c8GS FgHn5qfMPVl9YCcM2jegDONraEYg4Wsb1XD/DJ5iyqXmPtINizHpaudChWT6dKv+gD67 6snbE8c9PIhbK4nT2qgm63nvlmIPgNDl8Syww0c5qGSWu88vzh/DlfBcXYcvKGEwl9CC B3cA== MIME-Version: 1.0 X-Received: by 10.152.111.67 with SMTP id ig3mr18530366lab.41.1366826383915; Wed, 24 Apr 2013 10:59:43 -0700 (PDT) Received: by 10.112.135.229 with HTTP; Wed, 24 Apr 2013 10:59:43 -0700 (PDT) Date: Wed, 24 Apr 2013 13:59:43 -0400 Message-ID: Subject: Re: GSOC: Qt front-ends From: Justin Edward Muniz To: freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQnUV9/lKP1kKHH7Rcsuu2JNuZVDpD4rHxgTQ8K4X1LyKFQn7/5ADVW8vvT0YfcNd8+C/p9B Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 17:59:45 -0000 > > Mostly off-topic for this thread, but improving the boot process to > auto-detect hardware and auto-load kernel modules would be really nice. > That way, GENERIC would be very small, with just the basic frameworks > required (CAM, USB, PCI, TCP/IP, etc), and all the actual drivers would be > loaded from modules. That would remove almost all requirements to compile > a custom kernel in the first place. :) > > Granted, changing "options" in the kernel would require recompilation, but > general use and hardware changes wouldn't. > > Most likely not a GSoC project. But it's still a nice dream. :) > -- > Freddie Cash > fjwcash@gmail.com > I really like that idea. If I remember correctly some folks over at PC-BSD have started creating scripts to load sound and graphics drivers. Your idea may be closer to reality than you think! Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 18:03:58 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 417F2A13 for ; Wed, 24 Apr 2013 18:03:58 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by mx1.freebsd.org (Postfix) with ESMTP id C33F8139A for ; Wed, 24 Apr 2013 18:03:57 +0000 (UTC) Received: by mail-la0-f49.google.com with SMTP id ei20so1848404lab.8 for ; Wed, 24 Apr 2013 11:03:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=6iAgZ5XKy5tN1xOQ6ZSacv0gWwFm2znptz2v6xa+goI=; b=hH1sw9ODt/oAACYDJQhK5g1kbtfJ0lRItQ00VuxNN909a3dc8dIGgy63tocPgmNdCL QWxxz8ouTHR9sO9Ue6GgoLUO/NKYUOvckvd+Jj0Xue0K91BUS/DmAtcT00wgktg4k9Sw Rho3yeB5iO955G2WDdggaOUnPiHVgD/GQHXXwOGfmScm54cM/GffaOD6oRszis1CMFV0 FQ8qjeUoBXy0WaJ3VtxhQnrRJDFrB+srXbjTN4rbFdgfTYzgftp1zgjqNxrPq+yyFNlB AB8mnc7Dymvn4BL9YAQ6BWkRaE7RmAxYrllUMwJF8wLBNeI4dA8F6fNxdVfiP9FSSf03 cU6A== MIME-Version: 1.0 X-Received: by 10.152.18.164 with SMTP id x4mr18631472lad.38.1366826636551; Wed, 24 Apr 2013 11:03:56 -0700 (PDT) Received: by 10.112.135.229 with HTTP; Wed, 24 Apr 2013 11:03:56 -0700 (PDT) Date: Wed, 24 Apr 2013 14:03:56 -0400 Message-ID: Subject: Fwd: GSOC: Qt front-ends From: Justin Edward Muniz To: freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQkDVgq5NfDsEBMzk3Z9i6P2Nl/Q6aHU2zEIc5AuMt0EetPMnyk+beDWZBoPUW/ndey7Y69S Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:03:58 -0000 > > I think the interface to pkgng and freebsd-update are still > interesting; at least more worthwhile than the kernel configuration > one. > > I think the pkgng one has the edge, since packages are updated far > more often than base, and it's easier to track base. > > Now you are at a stage where you should make your own decision; which > one looks the most interesting to you? Once you decide on an area of > interest, you can just start hacking :) > > Chris > That's good to hear. I am sure that you are right, a pkgng GUI would probably see more use in general. I am definitely close to making my decision, but this thread has been so much help, I am glad for the insight. The coding is what I look forward to the most :D Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 18:10:41 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4FD4EDB3 for ; Wed, 24 Apr 2013 18:10:41 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by mx1.freebsd.org (Postfix) with ESMTP id 173CB1443 for ; Wed, 24 Apr 2013 18:10:40 +0000 (UTC) Received: by mail-qe0-f46.google.com with SMTP id nd7so1187844qeb.33 for ; Wed, 24 Apr 2013 11:10:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=za/FGH4eFJIsiUDUfk7ltRIpXIUaKlftsn36L4srRSg=; b=YvIizFYfjpmrnrIEgqv223v33agNrJmfeAs1Mvy7znePqErplDihZNdTCeoim9HHQR Ah7kczLu+DZqhAiklrgYfhxPaV+ZypaXy5pg4KEbkYwJ38caDOz96toMFvebTP/e8MJZ CdtpbJ9mgHBLkkbna3LRvThCfmwa6amcAeaBY8ox/pCwWsrSxr1v7US9plVYjact8z53 WIs6Pc4LcateScuDcJJ5yQNyNDpGQyuWTuXrffc/CfdYbyLEqN2pRIKhHidWuyUKyMZ2 QJWQ04Jj/ctO9Hgxeh6GMtq/dt6+cqTfVLETJrxv24zrFohNa5AVgmG548UeYEs6G1bF Ae3A== MIME-Version: 1.0 X-Received: by 10.224.192.196 with SMTP id dr4mr31335008qab.80.1366827040225; Wed, 24 Apr 2013 11:10:40 -0700 (PDT) Received: by 10.49.51.9 with HTTP; Wed, 24 Apr 2013 11:10:40 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Apr 2013 11:10:40 -0700 Message-ID: Subject: Re: GSOC: Qt front-ends From: Freddie Cash To: Justin Edward Muniz Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:10:41 -0000 On Wed, Apr 24, 2013 at 11:03 AM, Justin Edward Muniz < justin.muniz@maine.edu> wrote: > > > > I think the interface to pkgng and freebsd-update are still > > interesting; at least more worthwhile than the kernel configuration > > one. > > > > I think the pkgng one has the edge, since packages are updated far > > more often than base, and it's easier to track base. > > > > Now you are at a stage where you should make your own decision; which > > one looks the most interesting to you? Once you decide on an area of > > interest, you can just start hacking :) > > > > Chris > > > > > That's good to hear. > > I am sure that you are right, a pkgng GUI would probably see more use in > general. I am definitely close to making my decision, but this thread has > been so much help, I am glad for the insight. > > The coding is what I look forward to the most :D > You'll probably want to get in touch with the PC-BSD folks. As they are moving to pkgng for everything, they are updating their Python-based GUIs to work with it. Might be a possibility to work together, or to build off what they have, or to get ideas/inspiration for a more general tool. For example, (going from memory of my home PC-BSD install) the System Update or System Manager tool uses pkgng behind the scenes, and provides a tree-based view of PC-BSD-specific packages that can be installed via simply ticking checkboxes and hitting Install button. And, they have a ports-based GUI tool as well, although I have not used it as yet so couldn't tell you what it supports. I do my ports-based installs via a terminal. :) -- Freddie Cash fjwcash@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 18:13:19 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B646F1E8 for ; Wed, 24 Apr 2013 18:13:19 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 3D107149B for ; Wed, 24 Apr 2013 18:13:19 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id fd20so1877434lab.39 for ; Wed, 24 Apr 2013 11:13:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=0+bfEh4qkXZIuRNxO3bgHNUQECntfU8zAdJo0FtM348=; b=KQtfklV+L9/9pszAbphYPqC8q0dKhWBr/6BvUop7tBCj+LSS3UgQg0/12F7FxRdwqi 8aaeMw11qmolimFCAPOD0Lo8plROSIbvYB9QDJjOSJc9zjEdaiPhjeGlBqWfEQv5L3KO ePE2XfNtCosYi8rsygojHFEOn6R17docPoqx1R3rPM8gTJiKcF5GzOg1x1FEmZwNaIGX GpN6V9mz2gRkG61UbB7bMnlYOwOrDlsTQkCuMuzQGpgJMNdz1qKN+9hG9n7+Rf3tc3rR NNVLZmWk3y/HuBP1DP5yMvk2ON9l3SJELSTHvDVdWbtXzNwfeqozzcSEIRYRwPaZn4es cefA== MIME-Version: 1.0 X-Received: by 10.112.125.167 with SMTP id mr7mr18250315lbb.19.1366827198124; Wed, 24 Apr 2013 11:13:18 -0700 (PDT) Received: by 10.112.135.229 with HTTP; Wed, 24 Apr 2013 11:13:17 -0700 (PDT) In-Reply-To: <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> Date: Wed, 24 Apr 2013 14:13:17 -0400 Message-ID: Subject: Re: Fwd: GSOC: Qt front-ends From: Justin Edward Muniz To: Lars Engels , yerenkow@gmail.com, Freddie Cash , freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQnQGxBEfAe+2ifDr2VeS8GDw5+dtVxeumqtA8O9cdjjz4iZCxXhHeoDLi17dGI49DLzQx24 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:13:19 -0000 > > It _is_ easy. But having a nice graphical tool which draws a pretty table > of > GENERIC and NOTES together with useful information about the possible > options > and devices would be a handy thing to have IMHO. > Let's make FreeBSD userfriendly :-) I agree completely, hopefully we can make that happen. I imagine that the people using a kernel management utility would probably have configured it by hand before, but could benefit from a GUI in some way. Quick access to information is a good benefit to any GUI. Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 18:19:33 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 78264497 for ; Wed, 24 Apr 2013 18:19:33 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by mx1.freebsd.org (Postfix) with ESMTP id F3D7D14DF for ; Wed, 24 Apr 2013 18:19:32 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id fq13so1896252lab.28 for ; Wed, 24 Apr 2013 11:19:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=LORsBcRndlFDZnzumBelHS8WXB02dmzzw1NNvrBmVp0=; b=bFBw2JSBxRAgU+8EfLKE25KfmxnSA+g0yO3K6WuR5p8kdWUIFAyoYRVv7vC5e3J/Tx 8Nr0x0PJZCHPyprhila0YABoZ6DQAYl7JePfvtRG0u+pKXbvwPuyZZ8zJSGV3tx9m0Db HS9tSEbroIVGVm1R8wXJXQO3PuYzFZC67XLQbmi7nTtTuueHflqIaoijvuxfLAINgb1I EGMdRe+HkFC+bgIHtogS8U50uCmxBmhNvS8l+24JwHc9grf0JuIwC+tu9NV6C4jLs4d+ 3bieLeb4CjzgyKlgg7mcYheBdNH3sGG4t1DcIqd9X/tPa97JBIWozRMugqHVp/O6aHx3 u8FA== MIME-Version: 1.0 X-Received: by 10.112.147.170 with SMTP id tl10mr17911012lbb.100.1366827571677; Wed, 24 Apr 2013 11:19:31 -0700 (PDT) Received: by 10.112.135.229 with HTTP; Wed, 24 Apr 2013 11:19:31 -0700 (PDT) In-Reply-To: References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> Date: Wed, 24 Apr 2013 14:19:31 -0400 Message-ID: Subject: Re: Fwd: GSOC: Qt front-ends From: Justin Edward Muniz To: Alexander Yerenkow , Freddie Cash , freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQm4ehC3EluNdfIvVhORV6hD3npGpSgR9Tr1UiXpZ5AFRDXkG4EFi7XJRE5I96x7VydDnOAf Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:19:33 -0000 > > During some tests with cut down kernels one can easily make unbuildable > kernel, for example include option A, while omit hiddenly required B. > If there could be framework at least with deps tracking/checking, what > could be good for begin. > Both for configuring, and code clean up. > If this will come up in GUI - that would be awesome. > Especially if it handles dependencies! For example, check USB Disk > Support, and have scbus, da, etc enabled automatically. Or having the > LIBICONV stuff enabled if you add MSDOSFS support. And so on. Dependency checking and resolution is a really great idea. Thank you both for voicing your thoughts! From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 18:22:43 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AD2455BE for ; Wed, 24 Apr 2013 18:22:43 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by mx1.freebsd.org (Postfix) with ESMTP id 6E8831506 for ; Wed, 24 Apr 2013 18:22:43 +0000 (UTC) Received: by mail-ve0-f177.google.com with SMTP id cy12so882870veb.22 for ; Wed, 24 Apr 2013 11:22:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=Zm6679YimlDyUS2/RzC+T2wfT1Pjl6sk2ILxory4oes=; b=ejksG35bPvZW+w4mEGQ4BkxKUg044876+ePxoDPhLy2SqyyryKsOFJA6rXtGqHRUZp G5keZmEjZ14sqqKtD4cRvBqAuqn816Zj4WSbEXGa+SCdP2SFCdu9Kvfc6/OJdvSygCQ8 0XATL1Tlxmxb5CWf15lt2Dn+R1Mi0LbivyIC/eNpYNd0/MR5sZuEtTcmxzNjFWDBhv2L eayZ7Q0AGjVttMrFsfOD4fLjeBnzkVT6kmj8p/g0ThaKpVlP7zZKPwDbCvwrIMnbscAj vYm9RDJTlf/Rwi9VebmuQRyg47iWjkNZ0/AOaAn7AZvoWs5v3SVCJb+SIkn54ONIpq8X 9GGg== MIME-Version: 1.0 X-Received: by 10.220.57.197 with SMTP id d5mr10282648vch.47.1366827762457; Wed, 24 Apr 2013 11:22:42 -0700 (PDT) Received: by 10.58.28.242 with HTTP; Wed, 24 Apr 2013 11:22:42 -0700 (PDT) In-Reply-To: <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> Date: Wed, 24 Apr 2013 14:22:42 -0400 Message-ID: Subject: Re: GSOC: Qt front-ends From: Justin Edward Muniz To: Tony Li , freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQkAtdRklHewEI5J1YiHUSct8D1sw+MtmHC/orEa4mHUBIJMwQP6eIkzpkUKoMzigOzraxEq Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:22:43 -0000 > > Side note: I agree that we would really, really like FreeBSD more user > friendly. > > However, is kernel configuration where we really want to start? Just how > much of the user base reconfigures their kernels, anyway? Wouldn't effort > be better spent on making normal installation, maintenance and deployment > clean and easy? > > Regards, > Tony > What you say makes a lot of sense. I am feeling confident that the kernel GUI should be a lower priority, and not used for the GSoC proposal. Thank you for your time. Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 18:51:20 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 88998134 for ; Wed, 24 Apr 2013 18:51:20 +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 467C21672 for ; Wed, 24 Apr 2013 18:51:19 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa04.fnfis.com (8.14.5/8.14.5) with ESMTP id r3OIpJM4005570 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Apr 2013 13:51:19 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT04.FNFIS.com ([10.132.206.15]) with mapi id 14.02.0309.002; Wed, 24 Apr 2013 13:51:18 -0500 From: "Teske, Devin" To: Freddie Cash Subject: Re: GSOC: Qt front-ends Thread-Topic: GSOC: Qt front-ends Thread-Index: AQHOQRYWxsB+iV3pY0ycE6XibIPBvpjl/7MAgAALWYA= Date: Wed, 24 Apr 2013 18:51:17 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201F1E0E0@ltcfiswmsgmb21> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-04-24_08:2013-04-24,2013-04-24,1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Justin Edward Muniz , "Teske, Devin" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:51:20 -0000 On Apr 24, 2013, at 11:10 AM, Freddie Cash wrote: On Wed, Apr 24, 2013 at 11:03 AM, Justin Edward Muniz < justin.muniz@maine.edu> wrote: I think the interface to pkgng and freebsd-update are still interesting; at least more worthwhile than the kernel configuration one. I think the pkgng one has the edge, since packages are updated far more often than base, and it's easier to track base. Now you are at a stage where you should make your own decision; which one looks the most interesting to you? Once you decide on an area of interest, you can just start hacking :) Chris That's good to hear. I am sure that you are right, a pkgng GUI would probably see more use in general. I am definitely close to making my decision, but this thread has been so much help, I am glad for the insight. The coding is what I look forward to the most :D You'll probably want to get in touch with the PC-BSD folks. As they are moving to pkgng for everything, they are updating their Python-based GUIs to work with it. Might be a possibility to work together, or to build off what they have, or to get ideas/inspiration for a more general tool. For example, (going from memory of my home PC-BSD install) the System Update or System Manager tool uses pkgng behind the scenes, and provides a tree-based view of PC-BSD-specific packages that can be installed via simply ticking checkboxes and hitting Install button. And, they have a ports-based GUI tool as well, although I have not used it as yet so couldn't tell you what it supports. I do my ports-based installs via a terminal. :) I've been planning a pkgng management tool in base for a while now (and am = closing in on that goal). The tool is bsdconfig It's relevant to this discussion because it supports running both in GUI an= d in TUI. This is accomplished by using dialog(1) for TUI and Xdialog(1) (from ports)= for GUI. One code base, two modes. The package management is being implemented as a bsdconfig(8) module in HEA= D (see usr.sbin/bsdconfig). Executing "bsdconfig packages" produces something inspired by sysinstall bu= t greatly improved (faster, cleaner, more efficient, and provides more data= ). Here's a screenshot: http://twitpic.com/ci2rid Sorry, no screenshot of the X11 side yet. Executing "bsdconfig -X packages" or "bsdconfig packages -X" gives you the = X11 GUI. Is it the flashiest GUI you've ever seen? Far from it. But when I've demo'd= the code, people have been generally positive about the approach. Just wanted to let you know what my plans are. Feel free to go full-boar with a Qt-based front-end, just wanted to let you= know what I'm cooking in HEAD. -- Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 18:54:58 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2BB5F279 for ; Wed, 24 Apr 2013 18:54:58 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-ea0-x235.google.com (mail-ea0-x235.google.com [IPv6:2a00:1450:4013:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id B5DC716AC for ; Wed, 24 Apr 2013 18:54:57 +0000 (UTC) Received: by mail-ea0-f181.google.com with SMTP id a11so919461eae.40 for ; Wed, 24 Apr 2013 11:54:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=j6Iyfs93YYucUmLkpe+vtS9NnaZDFnIx1Yv8DNTWqpw=; b=PPzf0wtDOlCX+Yu9HjaR12wYngOedDiJ7zPEVQfdz6114k+x4CTpY1d7pr8OSy2zLi HhnBXLPw6xAyBEtXARIjhRwn5d7OkuRls6PawVoQzmw3wnn/ldlAv+Wf4hiptKFoZ+TF 7LKqJLSy2SUgL+1KkoPk4FhyeNDPUWvvBgsj9q5ZLkky6w4KSLr1di09rXHKtx+ifIuL S7wfbGudm9+7+V1atX3pNax4izdOfuz74zNHzlYkbWLBGHJF0ExdboMiKCfrt83hDNyJ a0O8ch7CErq82BixtBpfq2MUAD9FUIlxzLISN428qTUVa0u5c1knxWCB5mGkd4Mp8WuO QSUQ== X-Received: by 10.14.104.6 with SMTP id h6mr21717114eeg.5.1366829696930; Wed, 24 Apr 2013 11:54:56 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id k43sm6015908een.2.2013.04.24.11.54.55 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 24 Apr 2013 11:54:55 -0700 (PDT) Sender: Baptiste Daroussin Date: Wed, 24 Apr 2013 20:54:53 +0200 From: Baptiste Daroussin To: Justin Edward Muniz Subject: Re: Fwd: GSOC: Qt front-ends Message-ID: <20130424185452.GA50182@ithaqua.etoilebsd.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:54:58 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote: > > > > I think the interface to pkgng and freebsd-update are still > > interesting; at least more worthwhile than the kernel configuration > > one. > > > > I think the pkgng one has the edge, since packages are updated far > > more often than base, and it's easier to track base. > > > > Now you are at a stage where you should make your own decision; which > > one looks the most interesting to you? Once you decide on an area of > > interest, you can just start hacking :) > > > > Chris > > >=20 >=20 > That's good to hear. >=20 > I am sure that you are right, a pkgng GUI would probably see more use in > general. I am definitely close to making my decision, but this thread has > been so much help, I am glad for the insight. >=20 > The coding is what I look forward to the most :D imho a pkgng frontend should be done via packagekit, just write a pkgng bac= kend for packagekit and you will gain for FreeBSD a KDE frontend and a GTK front= end. That said any frontend at convenience to contributor will be anyway good :) regards, Bapt --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlF4KnwACgkQ8kTtMUmk6ExYKQCgktP2SBIJvbbAoTtGCIOCPdCO o2oAoLlYiSarPJocRDzljMxJ2To8uUMq =fglU -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV-- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 19:17:19 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B428FA2 for ; Wed, 24 Apr 2013 19:17: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 795381803 for ; Wed, 24 Apr 2013 19:17:19 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.17]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id r3OJHIj8031075 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Apr 2013 14:17:18 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT06.FNFIS.com ([10.132.206.17]) with mapi id 14.02.0309.002; Wed, 24 Apr 2013 14:17:18 -0500 From: "Teske, Devin" To: Freddie Cash Subject: Re: GSOC: Qt front-ends Thread-Topic: GSOC: Qt front-ends Thread-Index: AQHOQRYWxsB+iV3pY0ycE6XibIPBvpjl/7MAgAALWYCAAAdEgA== Date: Wed, 24 Apr 2013 19:17:17 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201F1E2A0@ltcfiswmsgmb21> References: <13CA24D6AB415D428143D44749F57D7201F1E0E0@ltcfiswmsgmb21> In-Reply-To: <13CA24D6AB415D428143D44749F57D7201F1E0E0@ltcfiswmsgmb21> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-04-24_08:2013-04-24,2013-04-24,1970-01-01 signatures=0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Justin Edward Muniz , "Teske, Devin" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 19:17:19 -0000 On Apr 24, 2013, at 11:51 AM, Teske, Devin wrote: On Apr 24, 2013, at 11:10 AM, Freddie Cash wrote: On Wed, Apr 24, 2013 at 11:03 AM, Justin Edward Muniz < justin.muniz@maine.edu> wrote: I think the interface to pkgng and freebsd-update are still interesting; at least more worthwhile than the kernel configuration one. I think the pkgng one has the edge, since packages are updated far more often than base, and it's easier to track base. Now you are at a stage where you should make your own decision; which one looks the most interesting to you? Once you decide on an area of interest, you can just start hacking :) Chris That's good to hear. I am sure that you are right, a pkgng GUI would probably see more use in general. I am definitely close to making my decision, but this thread has been so much help, I am glad for the insight. The coding is what I look forward to the most :D You'll probably want to get in touch with the PC-BSD folks. As they are moving to pkgng for everything, they are updating their Python-based GUIs to work with it. Might be a possibility to work together, or to build off what they have, or to get ideas/inspiration for a more general tool. For example, (going from memory of my home PC-BSD install) the System Update or System Manager tool uses pkgng behind the scenes, and provides a tree-based view of PC-BSD-specific packages that can be installed via simply ticking checkboxes and hitting Install button. And, they have a ports-based GUI tool as well, although I have not used it as yet so couldn't tell you what it supports. I do my ports-based installs via a terminal. :) I've been planning a pkgng management tool in base for a while now (and am = closing in on that goal). The tool is bsdconfig It's relevant to this discussion because it supports running both in GUI an= d in TUI. This is accomplished by using dialog(1) for TUI and Xdialog(1) (from ports)= for GUI. One code base, two modes. The package management is being implemented as a bsdconfig(8) module in HEA= D (see usr.sbin/bsdconfig). Clarification: The module is being *implemented* in HEAD, but is being *developed* on SF.n= et (URL Below): http://druidbsd.sf.net/download/bsdconfig/ Right now, if you download the latest tarball from that directory (bsdconfi= g.YYMMDD-#.tgz) and replace "usr.sbin/bsdconfig" in your checked-out tree, = you'll have ~1500 lines more than HEAD (at the time of this writing). My plan is to (before the next BAFUG) commit the packages module in one swi= ft action (hence why I'm developing it outside of the main tree). -- Devin Executing "bsdconfig packages" produces something inspired by sysinstall bu= t greatly improved (faster, cleaner, more efficient, and provides more data= ). Here's a screenshot: http://twitpic.com/ci2rid Sorry, no screenshot of the X11 side yet. Executing "bsdconfig -X packages" or "bsdconfig packages -X" gives you the = X11 GUI. Is it the flashiest GUI you've ever seen? Far from it. But when I've demo'd= the code, people have been generally positive about the approach. Just wanted to let you know what my plans are. Feel free to go full-boar with a Qt-based front-end, just wanted to let you= know what I'm cooking in HEAD. -- Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 19:18:24 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1B4A11B4; Wed, 24 Apr 2013 19:18:24 +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 DFDFE1813; Wed, 24 Apr 2013 19:18:23 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r3OJINiY025944 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Apr 2013 14:18:23 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.02.0309.002; Wed, 24 Apr 2013 14:18:23 -0500 From: "Teske, Devin" To: Baptiste Daroussin Subject: Re: GSOC: Qt front-ends Thread-Topic: GSOC: Qt front-ends Thread-Index: AQHOQSB8u/vZWZWEYUqzrBrXPDCeHg== Date: Wed, 24 Apr 2013 19:18:21 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201F1E2BB@ltcfiswmsgmb21> References: <20130424185452.GA50182@ithaqua.etoilebsd.net> In-Reply-To: <20130424185452.GA50182@ithaqua.etoilebsd.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-04-24_08:2013-04-24,2013-04-24,1970-01-01 signatures=0 Cc: FreeBSD Hackers , Justin Edward Muniz , "Teske, Devin" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 19:18:24 -0000 On Apr 24, 2013, at 11:54 AM, Baptiste Daroussin wrote: > On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote: >>>=20 >>> I think the interface to pkgng and freebsd-update are still >>> interesting; at least more worthwhile than the kernel configuration >>> one. >>>=20 >>> I think the pkgng one has the edge, since packages are updated far >>> more often than base, and it's easier to track base. >>>=20 >>> Now you are at a stage where you should make your own decision; which >>> one looks the most interesting to you? Once you decide on an area of >>> interest, you can just start hacking :) >>>=20 >>> Chris >>>=20 >>=20 >>=20 >> That's good to hear. >>=20 >> I am sure that you are right, a pkgng GUI would probably see more use in >> general. I am definitely close to making my decision, but this thread has >> been so much help, I am glad for the insight. >>=20 >> The coding is what I look forward to the most :D >=20 > imho a pkgng frontend should be done via packagekit, just write a pkgng b= ackend > for packagekit and you will gain for FreeBSD a KDE frontend and a GTK fro= ntend. >=20 > That said any frontend at convenience to contributor will be anyway good = :) >=20 If you could pardon my ignorance=85 but what is packagekit again (for the b= enefit of others)? --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 19:45:05 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DB6AA55D for ; Wed, 24 Apr 2013 19:45:05 +0000 (UTC) (envelope-from justin.muniz@maine.edu) Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by mx1.freebsd.org (Postfix) with ESMTP id 9E0601A91 for ; Wed, 24 Apr 2013 19:45:05 +0000 (UTC) Received: by mail-vc0-f181.google.com with SMTP id hr11so842281vcb.40 for ; Wed, 24 Apr 2013 12:44:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=r00rze3eVWEun9jJIX+strN32l6vgptqaCh9/URQTZg=; b=fKzRRtDjOJqsnby3kEd2FMuFKbt4cVSKt6nS7NjRnKHsqk88QUL6MEpsLtUY6qybw/ 8AFalbX0+aw0iQNWJ8CXGEroKHvjLBCzBmwlXvhZBJwOgJE7BH91gw5cF0QjU3ilAj9a NlLE8ecMd5Daq2vXXwKNJE7k3UjgyY9qJYxyR7AtNzVONEYW2KbxF27R1a50Ls2/+2K3 DWRwEbZgQhzcO2fDg5UDJvzf/tY3pS8dP2m1JpkRbsUELl8c9aCKfIB1cz7uZuIeUSvi S8Qp/cWNAPHilzqdahYB/JzbjprjjViEH8xJh3wM4C2PsXMo+x00pPw57Ta9LKqQd2aH T6+w== MIME-Version: 1.0 X-Received: by 10.220.168.202 with SMTP id v10mr25539935vcy.71.1366832699058; Wed, 24 Apr 2013 12:44:59 -0700 (PDT) Received: by 10.58.28.242 with HTTP; Wed, 24 Apr 2013 12:44:58 -0700 (PDT) In-Reply-To: <13CA24D6AB415D428143D44749F57D7201F1E2BB@ltcfiswmsgmb21> References: <20130424185452.GA50182@ithaqua.etoilebsd.net> <13CA24D6AB415D428143D44749F57D7201F1E2BB@ltcfiswmsgmb21> Date: Wed, 24 Apr 2013 15:44:58 -0400 Message-ID: Subject: Re: GSOC: Qt front-ends From: Justin Edward Muniz To: "Teske, Devin" , Baptiste Daroussin , Freddie Cash , freebsd-hackers@freebsd.org X-Gm-Message-State: ALoCoQm1FPQ35lwS1t5l6InJWhjpaFKZTP0z6KN0ZUdbOes11wetWYYby0LrDgki3H7OOoEx/RpC Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 19:45:05 -0000 > You'll probably want to get in touch with the PC-BSD folks. As they are > moving to pkgng for everything, they are updating their Python-based GUIs > to work with it. Might be a possibility to work together, or to build off what > they have, or to get ideas/inspiration for a more general tool. I will definitely contact them with any questions I have. I have just been reading through the script called pc-updatemanager and it is a nice aid for developing a pkgng back-end with. > If you could pardon my ignorance=85 but what is packagekit again (for the > benefit of others)? I've just looked into this myself, it is an api and daemon that together allow you to create a package manager while not worrying about the abstract inner workings. The benefit is that one back-end (for pkgng in this case) could be programmed, but it would work with both the gtk and qt packagekit clients. On top of everything it offers some really cool advanced features. (http://www.packagekit.org/) > imho a pkgng frontend should be done via packagekit, just write a pkgng > backend for packagekit and you will gain for FreeBSD a KDE frontend and > a GTK frontend. I really like this suggestion, I am looking in to this now and it is very, very cool. I still need to learn more about it but I appreciate the recommendation. I had never heard about packagekit before today. > The tool is bsdconfig I checked out your Web site, and I want to say congratulations on your progress. It is quite an accomplishment. I think that a modern GUI could however appeal to a different crowd. If FreeBSD comes with bsdconfig, perhaps a qt GUI could be an alternative. I like qt compared to xdialog because you can have a more persistent interface with more options available to you at any one time. There is less navigating through menus. Thank you for letting me know about your work, I will take it in consideration when trying to develop the strongest proposal I can. Justin Muniz From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 24 21:33:09 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DBE34AE0; Wed, 24 Apr 2013 21:33:09 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id 4E8211F5D; Wed, 24 Apr 2013 21:33:09 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id s43so2028271wey.27 for ; Wed, 24 Apr 2013 14:33:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ucmda0IRAuvse64XNeo49C1tu15h1zCxWnYDC9P2p3g=; b=BxyjW8mnOo2y++OebVvrhBLije4TC7yy6FmV1zoRMDB12r9PQtYunh9Y1PIy23WZ8D PREV0ojsfZQASSrxZ0NBi/u0l6oR+VMtVpNbfc5uuzV+OAJA3qjX2GptS9GoGVZcAZs7 beyaHmxdEvqk5TQPqNm5145/oXd6JEULe3UcNlcKVbckWPAZYS6pnmGFK4BF5GeAJAf1 e/31qrP9lc7AbETwYjaFaAlxKw38JRa9DR3cfIObo8ocXn++D2wqMuphxEkcYFzOjP2T RM+xggMv8P74JEz123HZL2GspsQK2ufCLHGIM0UoiLLzJaeCK2+mZHJdxzvULaCWWuzB 1AzQ== MIME-Version: 1.0 X-Received: by 10.180.83.199 with SMTP id s7mr46786529wiy.19.1366839188275; Wed, 24 Apr 2013 14:33:08 -0700 (PDT) Received: by 10.180.100.130 with HTTP; Wed, 24 Apr 2013 14:33:07 -0700 (PDT) Received: by 10.180.100.130 with HTTP; Wed, 24 Apr 2013 14:33:07 -0700 (PDT) In-Reply-To: <13CA24D6AB415D428143D44749F57D7201F1E2BB@ltcfiswmsgmb21> References: <20130424185452.GA50182@ithaqua.etoilebsd.net> <13CA24D6AB415D428143D44749F57D7201F1E2BB@ltcfiswmsgmb21> Date: Wed, 24 Apr 2013 23:33:07 +0200 Message-ID: Subject: Re: GSOC: Qt front-ends From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: "Teske, Devin" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Baptiste Daroussin , Justin Edward Muniz X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 21:33:09 -0000 El 24/04/2013 21:18, "Teske, Devin" escribi=F3: > > > On Apr 24, 2013, at 11:54 AM, Baptiste Daroussin wrote: > > > On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote: > >>> > >>> I think the interface to pkgng and freebsd-update are still > >>> interesting; at least more worthwhile than the kernel configuration > >>> one. > >>> > >>> I think the pkgng one has the edge, since packages are updated far > >>> more often than base, and it's easier to track base. > >>> > >>> Now you are at a stage where you should make your own decision; which > >>> one looks the most interesting to you? Once you decide on an area of > >>> interest, you can just start hacking :) > >>> > >>> Chris > >>> > >> > >> > >> That's good to hear. > >> > >> I am sure that you are right, a pkgng GUI would probably see more use in > >> general. I am definitely close to making my decision, but this thread has > >> been so much help, I am glad for the insight. > >> > >> The coding is what I look forward to the most :D > > > > imho a pkgng frontend should be done via packagekit, just write a pkgng backend > > for packagekit and you will gain for FreeBSD a KDE frontend and a GTK frontend. > > > > That said any frontend at convenience to contributor will be anyway good :) > > > > If you could pardon my ignorance=85 but what is packagekit again (for the benefit of others)? It's an application to manage packages. It is developed in a way that it's easy to add new backends keeping the same interface. See[1] for the general information and this[2] page for the currently supported back ends. [1] http://www.packagekit.org [2] http://www.packagekit.org/pk-matrix.html > -- > Devin > > _____________ > The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. > _______________________________________________ > freebsd-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 Wed Apr 24 22:07:32 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9BD0F7AC; Wed, 24 Apr 2013 22:07:32 +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 679AA10BF; Wed, 24 Apr 2013 22:07:32 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id r3OM7VZE031913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 24 Apr 2013 17:07:31 -0500 Received: from LTCFISWMSGMB21.FNFIS.com ([10.132.99.23]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.02.0309.002; Wed, 24 Apr 2013 17:07:31 -0500 From: "Teske, Devin" To: =?Windows-1252?Q?Fernando_Apestegu=EDa?= Subject: Re: GSOC: Qt front-ends Thread-Topic: GSOC: Qt front-ends Thread-Index: AQHOQSB8u/vZWZWEYUqzrBrXPDCeHpjmOC+AgAAJmwA= Date: Wed, 24 Apr 2013 22:07:30 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201F1E794@ltcfiswmsgmb21> References: <20130424185452.GA50182@ithaqua.etoilebsd.net> <13CA24D6AB415D428143D44749F57D7201F1E2BB@ltcfiswmsgmb21> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-04-24_08:2013-04-24,2013-04-24,1970-01-01 signatures=0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Hackers , Baptiste Daroussin , Devin Teske , Justin Edward Muniz X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 22:07:32 -0000 On Apr 24, 2013, at 2:33 PM, Fernando Apestegu=EDa wrote: El 24/04/2013 21:18, "Teske, Devin" > escribi=F3: > > > On Apr 24, 2013, at 11:54 AM, Baptiste Daroussin wrote: > > > On Wed, Apr 24, 2013 at 02:03:56PM -0400, Justin Edward Muniz wrote: > >>> > >>> I think the interface to pkgng and freebsd-update are still > >>> interesting; at least more worthwhile than the kernel configuration > >>> one. > >>> > >>> I think the pkgng one has the edge, since packages are updated far > >>> more often than base, and it's easier to track base. > >>> > >>> Now you are at a stage where you should make your own decision; which > >>> one looks the most interesting to you? Once you decide on an area of > >>> interest, you can just start hacking :) > >>> > >>> Chris > >>> > >> > >> > >> That's good to hear. > >> > >> I am sure that you are right, a pkgng GUI would probably see more use = in > >> general. I am definitely close to making my decision, but this thread = has > >> been so much help, I am glad for the insight. > >> > >> The coding is what I look forward to the most :D > > > > imho a pkgng frontend should be done via packagekit, just write a pkgng= backend > > for packagekit and you will gain for FreeBSD a KDE frontend and a GTK f= rontend. > > > > That said any frontend at convenience to contributor will be anyway goo= d :) > > > > If you could pardon my ignorance=85 but what is packagekit again (for the= benefit of others)? It's an application to manage packages. It is developed in a way that it's = easy to add new backends keeping the same interface. See[1] for the general= information and this[2] page for the currently supported back ends. [1] http://www.packagekit.org [2] http://www.packagekit.org/pk-matrix.html Cool. Kinda reminds me of "SANE" for interfacing with scanners. -- Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 08:11:44 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E18EF793 for ; Thu, 25 Apr 2013 08:11:44 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.net (cl-90.mrs-01.fr.sixxs.net [IPv6:2a01:240:fe00:59::2]) by mx1.freebsd.org (Postfix) with ESMTP id A490014A5 for ; Thu, 25 Apr 2013 08:11:44 +0000 (UTC) Received: from roberto02-aw.erc.corp.eurocontrol.int (aran.keltia.net [88.191.250.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.net (Postfix) with ESMTPSA id 2FD2552AD; Thu, 25 Apr 2013 10:11:41 +0200 (CEST) Date: Thu, 25 Apr 2013 10:12:50 +0200 From: Ollivier Robert To: freebsd-hackers@freebsd.org, Lars Engels Subject: Re: GSOC: Qt front-ends Message-ID: <20130425081250.GA9042@roberto02-aw.erc.corp.eurocontrol.int> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7.2 / Dell D820 SMP User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 08:11:44 -0000 According to Freddie Cash on Wed, Apr 24, 2013 at 10:32:11AM -0700: > Mostly off-topic for this thread, but improving the boot process to > auto-detect hardware and auto-load kernel modules would be really nice. > That way, GENERIC would be very small, with just the basic frameworks > required (CAM, USB, PCI, TCP/IP, etc), and all the actual drivers would be > loaded from modules. That would remove almost all requirements to compile > a custom kernel in the first place. :) > > Granted, changing "options" in the kernel would require recompilation, but > general use and hardware changes wouldn't. That's what Solaris has been doing for years and yes, it does make a lot of sense. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/ From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 08:25:48 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0A61AB23 for ; Thu, 25 Apr 2013 08:25:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 96C53154E for ; Thu, 25 Apr 2013 08:25:47 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id l13so8833001wie.3 for ; Thu, 25 Apr 2013 01:25:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=jF++lKB92hvmX/BqOs8US80FbYLOCKtCHK8KnXG2JS8=; b=gs9whjJqovABHvG3h/qPLyr7yxj5KWlKr4lvFPTGCS3iNTqksGK+yCc+/4o+45mtqy Ke6zvoQWaMr2P0DIdROVNnkos6MHlASCbaMG8Rt+AGLTDKftwpwue23/6KllEtTQVzzQ zkOUPGANjqiWYfpI636PAzenBKISY5Fhn5vdPo60pW8Mqc6JQmv2gwyNBNUA+RWgVyvh JnRfb/FN0KBg0k3iMq4+BQBRgXZqvkzJ/+QVSo5xoXVkoEuCPayDpyFvAUIkjcKGw1ea 1wfufz8dErM6l+ABVQWzSElE5RivBKI0dqMJpqoH9yr+/rW3ieF80eqf7hpFUgIwH/E3 hkOg== MIME-Version: 1.0 X-Received: by 10.180.87.170 with SMTP id az10mr2363449wib.3.1366878346687; Thu, 25 Apr 2013 01:25:46 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Thu, 25 Apr 2013 01:25:46 -0700 (PDT) In-Reply-To: <20130425081250.GA9042@roberto02-aw.erc.corp.eurocontrol.int> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> <20130425081250.GA9042@roberto02-aw.erc.corp.eurocontrol.int> Date: Thu, 25 Apr 2013 01:25:46 -0700 X-Google-Sender-Auth: zoG9YL_7GDxI8R8xy_TjFpYqx8U Message-ID: Subject: Re: GSOC: Qt front-ends From: Adrian Chadd To: Ollivier Robert Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, Lars Engels X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 08:25:48 -0000 .. or we could just bite the bullet and split GENERIC into GENERIC (which would have modules for everything) and GENERIC_NOMODULES. Then just populate a default module list that goes into /boot/loader.conf. If you're even more evil, you could populate a module list that goes into /boot//module.conf.default, and then allow that to be overridden. Point is - a modular kernel works, right now. What we're missing is a way to load them at boot time by the bootloader. Well, enough of them to bring up the system so the rest can be autoloaded as needed. _That_ whole mess would be a great GSoC project. Adrian From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 08:38:21 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 23E8F4D0; Thu, 25 Apr 2013 08:38:21 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id D7B4915F2; Thu, 25 Apr 2013 08:38:20 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 3E2256A6001; Thu, 25 Apr 2013 10:38:19 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id r3P8cJiS001078; Thu, 25 Apr 2013 10:38:19 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id r3P8cIlt000822; Thu, 25 Apr 2013 10:38:18 +0200 (CEST) (envelope-from lars) Date: Thu, 25 Apr 2013 10:38:18 +0200 From: Lars Engels To: Adrian Chadd Subject: Re: GSOC: Qt front-ends Message-ID: <20130425083818.GO65341@e-new.0x20.net> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> <20130425081250.GA9042@roberto02-aw.erc.corp.eurocontrol.int> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i0LFOk513GRb+T2w" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p5 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 08:38:21 -0000 --i0LFOk513GRb+T2w Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 25, 2013 at 01:25:46AM -0700, Adrian Chadd wrote: > .. or we could just bite the bullet and split GENERIC into GENERIC > (which would have modules for everything) and GENERIC_NOMODULES. >=20 > Then just populate a default module list that goes into /boot/loader.conf. No, the list must be in kld_list=3D"" in rc.conf. If you add all the modules to loader.conf you can drink a coffee while the system boots. >=20 > If you're even more evil, you could populate a module list that goes > into /boot//module.conf.default, and then allow that to be > overridden. >=20 > Point is - a modular kernel works, right now. What we're missing is a > way to load them at boot time by the bootloader. Well, enough of them > to bring up the system so the rest can be autoloaded as needed. >=20 > _That_ whole mess would be a great GSoC project. +1 --i0LFOk513GRb+T2w Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlF463oACgkQKc512sD3afjA/wCgzFvtNc2PT4pw9FZZ7MnuIg8X mikAoMJekij9FFCJd6b6xHSNzqYMxDz5 =uUO8 -----END PGP SIGNATURE----- --i0LFOk513GRb+T2w-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 08:57:51 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EBBF7BC6; Thu, 25 Apr 2013 08:57:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 5B4DD16A1; Thu, 25 Apr 2013 08:57:51 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id l13so8871397wie.1 for ; Thu, 25 Apr 2013 01:57:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=v9y5cdiYy8OhAmAgctQcg8R4e94GleeCQoDVQWjw5JU=; b=jtRacBYGF5bdjm5E18htNolEDRHnSWVIQm1EEZQS+fH3X14JOPdwgwq1jFRWTquZNv 2/EniGBu6a/6OS+sgokzLimNSBrOszWFaCExRlebhzTBgghVgetdTsq2NCHHZWwxXD0t BWYafJ+8SgL1wO1IH8Dgx26EtDHDXUOMeyFU2Nbg+ZAV+VsOvr11zAP3WNoXgjEASGC3 GJZsP352ZRGw8JSkq4l5CGbyJd2vgrU993yLdvQq16o8uecnWzgv3Q4Bh6MYQvFRomxs +FuvnkMNAE9f5X2v5YmrO7BX6Pho186ZFAv1k81ooXR3hRYVSUt7v3au+LERFHUKE7qr scAw== MIME-Version: 1.0 X-Received: by 10.194.93.133 with SMTP id cu5mr74205481wjb.56.1366880270467; Thu, 25 Apr 2013 01:57:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Thu, 25 Apr 2013 01:57:50 -0700 (PDT) In-Reply-To: <20130425083818.GO65341@e-new.0x20.net> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> <20130425081250.GA9042@roberto02-aw.erc.corp.eurocontrol.int> <20130425083818.GO65341@e-new.0x20.net> Date: Thu, 25 Apr 2013 01:57:50 -0700 X-Google-Sender-Auth: pJ4NR8bA0agpaIwLWdocfXAdReI Message-ID: Subject: Re: GSOC: Qt front-ends From: Adrian Chadd To: Lars Engels Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 08:57:52 -0000 On 25 April 2013 01:38, Lars Engels wrote: > On Thu, Apr 25, 2013 at 01:25:46AM -0700, Adrian Chadd wrote: >> .. or we could just bite the bullet and split GENERIC into GENERIC >> (which would have modules for everything) and GENERIC_NOMODULES. >> >> Then just populate a default module list that goes into /boot/loader.conf. > > No, the list must be in kld_list="" in rc.conf. > If you add all the modules to loader.conf you can drink a coffee while > the system boots. .. so improve loader so that doesn't suck so hard. Adrian From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 09:24:03 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6B9EB179; Thu, 25 Apr 2013 09:24:03 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.net (cl-90.mrs-01.fr.sixxs.net [IPv6:2a01:240:fe00:59::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2B79017F8; Thu, 25 Apr 2013 09:24:03 +0000 (UTC) Received: from roberto02-aw.erc.corp.eurocontrol.int (aran.keltia.net [88.191.250.24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.net (Postfix) with ESMTPSA id 2E18952AD; Thu, 25 Apr 2013 11:24:02 +0200 (CEST) Date: Thu, 25 Apr 2013 11:25:14 +0200 From: Ollivier Robert To: Adrian Chadd Subject: Re: GSOC: Qt front-ends Message-ID: <20130425092514.GB9042@roberto02-aw.erc.corp.eurocontrol.int> References: <60A4F968-60A4-4C71-AD53-BA1BC6CBAB5F@longcount.org> <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> <20130425081250.GA9042@roberto02-aw.erc.corp.eurocontrol.int> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: MacOS X / Macbook Pro - FreeBSD 7.2 / Dell D820 SMP User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org, Lars Engels X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 09:24:03 -0000 According to Adrian Chadd on Thu, Apr 25, 2013 at 01:25:46AM -0700: > If you're even more evil, you could populate a module list that goes > into /boot//module.conf.default, and then allow that to be > overridden. > > Point is - a modular kernel works, right now. What we're missing is a > way to load them at boot time by the bootloader. Well, enough of them > to bring up the system so the rest can be autoloaded as needed. > > _That_ whole mess would be a great GSoC project. I completely agree. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/ From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 09:24:04 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 10FDB17B; Thu, 25 Apr 2013 09:24:04 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mx1.freebsd.org (Postfix) with ESMTP id C264A17F9; Thu, 25 Apr 2013 09:24:03 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 0AA396A6001; Thu, 25 Apr 2013 11:24:02 +0200 (CEST) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.5/8.14.5) with ESMTP id r3P9O1Gc032132; Thu, 25 Apr 2013 11:24:01 +0200 (CEST) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.5/8.14.5/Submit) id r3P9O15X030950; Thu, 25 Apr 2013 11:24:01 +0200 (CEST) (envelope-from lars) Date: Thu, 25 Apr 2013 11:24:01 +0200 From: Lars Engels To: Adrian Chadd Subject: Re: GSOC: Qt front-ends Message-ID: <20130425092401.GP65341@e-new.0x20.net> References: <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> <20130425081250.GA9042@roberto02-aw.erc.corp.eurocontrol.int> <20130425083818.GO65341@e-new.0x20.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9+VnUxDxRuy97YQ+" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.3-RELEASE-p5 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Lars Engels , freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 09:24:04 -0000 --9+VnUxDxRuy97YQ+ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 25, 2013 at 01:57:50AM -0700, Adrian Chadd wrote: > On 25 April 2013 01:38, Lars Engels wrote: > > On Thu, Apr 25, 2013 at 01:25:46AM -0700, Adrian Chadd wrote: > >> .. or we could just bite the bullet and split GENERIC into GENERIC > >> (which would have modules for everything) and GENERIC_NOMODULES. > >> > >> Then just populate a default module list that goes into /boot/loader.c= onf. > > > > No, the list must be in kld_list=3D"" in rc.conf. > > If you add all the modules to loader.conf you can drink a coffee while > > the system boots. >=20 > .. so improve loader so that doesn't suck so hard. Sure, but the rc.conf solution is the lower hanging fruit. :) --9+VnUxDxRuy97YQ+ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlF49jEACgkQKc512sD3afjfGACfWWIwU97CI5phu4gTDhlSBnEJ m7kAn24Hcq9ctGQx+iWPkecLkJ1xublZ =N5XZ -----END PGP SIGNATURE----- --9+VnUxDxRuy97YQ+-- From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 20:06:41 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CD3F5A3D; Thu, 25 Apr 2013 20:06:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by mx1.freebsd.org (Postfix) with ESMTP id 3DECD1773; Thu, 25 Apr 2013 20:06:41 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id c10so3865087wiw.14 for ; Thu, 25 Apr 2013 13:06:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wp92cE14tQ1PxMCC2vgjKQK0SNtCJqgc6nxVj44VPRw=; b=YkTJjHLDS1AkrkQdvJLA0YcA5tlMy5euPLUuNYqnXwi+sJxjgNA6Z1/bcIzahO/IL0 rzp3EVYbJjrquNtBnqXoagIqjryrmN1PCOhL4aIYcxSxHxQ26XbO/9OPapczD6oS6Pc8 di4+ICvry0qewFOItUzm7hIXojilQhlEDB763rTgGmjrPaB2NCI+eIc5+1s5IN/ldNpA 6I4nY/SOdE+gw8uKzYmRGOIidoZaI2h2dFtQWybYEwhrV1DlST7aKGrUf079RyMKTcQ+ in+n3QaVR6h1lmC+sDfljnURBfPOoCkoGGATwCm/f9AYulJapG4eKIJNj5v0e8ZHGAV8 izLw== MIME-Version: 1.0 X-Received: by 10.180.93.134 with SMTP id cu6mr37604wib.8.1366920400400; Thu, 25 Apr 2013 13:06:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Thu, 25 Apr 2013 13:06:39 -0700 (PDT) In-Reply-To: <20130425092401.GP65341@e-new.0x20.net> References: <8af7c4b114d6f1a44cf157a64fee3a7f@mail.0x20.net> <578CB1FA-C223-4872-B681-7EC0C280E611@tony.li> <20130425081250.GA9042@roberto02-aw.erc.corp.eurocontrol.int> <20130425083818.GO65341@e-new.0x20.net> <20130425092401.GP65341@e-new.0x20.net> Date: Thu, 25 Apr 2013 13:06:39 -0700 X-Google-Sender-Auth: 0OEd0u_co9Y1PRQEmwMBSU26SjM Message-ID: Subject: Re: GSOC: Qt front-ends From: Adrian Chadd To: Lars Engels Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 20:06:41 -0000 On 25 April 2013 02:24, Lars Engels wrote: > Sure, but the rc.conf solution is the lower hanging fruit. :) No it's not; think about it. You need to have a few modules loaded in order to boot. * usb * maybe atkbd * da/scsi * ata / scsi block device drivers * perhaps network * perhaps vga/vesa * perhaps acpi_* for your laptop device .. those can't be in rc.conf . Adrian From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 20:35:22 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CF23639A for ; Thu, 25 Apr 2013 20:35:22 +0000 (UTC) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:bd2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9F0FF190F for ; Thu, 25 Apr 2013 20:35:22 +0000 (UTC) Received: from webmail.tucs-beachin-obx-house.com (www@vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by vjofn.tucs-beachin-obx-house.com (8.14.2/8.14.2) with ESMTP id r3PKZLoV074066 for ; Thu, 25 Apr 2013 16:35:22 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 25 Apr 2013 16:35:21 -0400 From: Tuc To: Subject: Botched 7->8 upgrade, thoughts how to =?UTF-8?Q?recover=3F?= Message-ID: <9e3c6c0c1a72dd9c7977103e891e77b1@vjofn.tucs-beachin-obx-house.com> X-Sender: ml@t-b-o-h.net User-Agent: Roundcube Webmail/0.8-svn X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 20:35:22 -0000 Hi, Figured this might be a bit more than -questions worthy... I was following some instructions online about upgrading 7 to 8... And... Well... Something went horribly wrong during "make installworld". I lost my ssh session (Mistake 1 - Console dummy!) and now in multiuser I can't log in. I logged in single user and commands are iffy about working. "ls" is fine, but "ls -l" coredumps. I tried to redo the installworld, but it seems to get somewhere in libc man pages and then quits. Could be that "ln" is screwed. Any thoughts on how to recover? I did an rsync of the system elsewhere beforehand, so if it works I probably could just get it all back that way. I was HOPING to go forward to 8. Is there some way I can do the equiv of a "make installworld&&make installkernel" off some media so I don't overwrite config, password, group, etc. Thanks, Tuc From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 25 21:54:49 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A8F1E2FF for ; Thu, 25 Apr 2013 21:54:49 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ia0-x22b.google.com (mail-ia0-x22b.google.com [IPv6:2607:f8b0:4001:c02::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 7DB411E4E for ; Thu, 25 Apr 2013 21:54:49 +0000 (UTC) Received: by mail-ia0-f171.google.com with SMTP id r13so3043460iar.2 for ; Thu, 25 Apr 2013 14:54:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=F2MVLnBBy7fJi/ePm/I+jJb8NIzv2CPNfeT5dBuGy1w=; b=P5bEph1opKCWSNbmzD5QlELOdWRFvKdVfv75B2xGcqAVVXgYDOvWQ1nU+O1zmLxB3I oeJP0hxU5/OhIwbHIxsaI8YAEZD0YlyAAftotIMvY+Vdce67Ch0MCHzdiXOfZQwIiptm NQOMqgV30i79lqbZ6RB+BgLtR+axr2GjBaHjoGiW2IB+ct8yYQfI1NDdwrSactU2QPYG B4l4XI2VOJ/TUleBUkuQZZLxiszhDU323xy+FqhVM27jSlVemKrgbYbGUS9UJ6lG4e7/ /MLZAa+Lxk1BLUM5CEmMJYAkhRYuiEH5VvE/aaXWVaWTWZUk4T/HIy2chfpy3Rknxe8k kfyg== X-Received: by 10.50.15.166 with SMTP id y6mr154092igc.83.1366926889263; Thu, 25 Apr 2013 14:54:49 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPSA id q3sm15073029igw.0.2013.04.25.14.54.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 25 Apr 2013 14:54:48 -0700 (PDT) Message-ID: <5179A61E.4060600@gmail.com> Date: Thu, 25 Apr 2013 16:54:38 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Botched 7->8 upgrade, thoughts how to recover? References: <9e3c6c0c1a72dd9c7977103e891e77b1@vjofn.tucs-beachin-obx-house.com> In-Reply-To: <9e3c6c0c1a72dd9c7977103e891e77b1@vjofn.tucs-beachin-obx-house.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 21:54:49 -0000 On 4/25/2013 3:35 PM, Tuc wrote: > Hi, > > Figured this might be a bit more than -questions worthy... > > I was following some instructions online about upgrading 7 to 8... > And... Well... Something went horribly wrong during "make installworld". > I lost my ssh session (Mistake 1 - Console dummy!) and now in multiuser > I can't log in. I logged in single user and commands are iffy about > working. "ls" is fine, but "ls -l" coredumps. I tried to redo the > installworld, but it seems to get somewhere in libc man pages and then > quits. Could be that "ln" is screwed. > > Any thoughts on how to recover? I did an rsync of the system elsewhere > beforehand, so if it works I probably could just get it all back that > way. I was HOPING to go forward to 8. Is there some way I can do the > equiv of a "make installworld&&make installkernel" off some media so I > don't overwrite config, password, group, etc. > > Thanks, Tuc Try logging in and rebuilding world. First set your path to include /rescue before /bin. You can rebuild in single user mode without a problem, probably. When you install, don't use -j. If it fails, just document where it fails and post back. If you have another FreeBSD system available, you can use a flash drive to install to and from, just set MAKEOBJDIRPREFIX to the mount location. Don't forget the final mergemaster. Also, did you remember `mergemaster -p` beforehand? From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 02:17:03 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8945F439 for ; Fri, 26 Apr 2013 02:17:03 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by mx1.freebsd.org (Postfix) with ESMTP id 675801646 for ; Fri, 26 Apr 2013 02:17:03 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id w11so159618pde.37 for ; Thu, 25 Apr 2013 19:17:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=SVY9/FCttx9VqFqIA5szO2PVeVmi93JQUwj5QiB6Da8=; b=KkyfuRw2XVKJvuYt+uGzn5U4hikFerpGNUY6pi1deeoisb9va3nrECXCGQj97BvR1+ cjAhZ2STQI7nJibeZbFZXMVGWA6dPeNxKezdyQ2mUhjL3X2HAz6/MuSWgsrZ8/Enlnhn nHAlRqVS/M2Q8nrlHL1DCuFf+jBvmRgelyim8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=SVY9/FCttx9VqFqIA5szO2PVeVmi93JQUwj5QiB6Da8=; b=i4zuCD/1cIZUyV1WdnqI3B0ZxPH3odppjmYQojDCFAZGr19/IXTIbyfIqWij+T5hiW npJWOCtGiO00N1tgupVcBVB5gCUPhuIgIDAR0Jx1YQCWXrNXrbHQBg85oI5Hdpr1mNy3 ofWNSUMmXZ6BC0364s/b6jaBh4++Ja/i2Vqb4+W7dmolz3lsDIT1wpDA4Z+batUOPv5K 0iblITVkPl+6mz2WfGfWgDP1XEhyXf725gfoEBtrLA2Fth0uMHhy9bIfygdcWUHUi6ik KtBQivA/kSFhW5lkC5K1X1jYwLKKIvbrg2fMFULvdfkEWgHFVwLUeer9INL/wqoVlnTz B5mA== X-Received: by 10.66.102.65 with SMTP id fm1mr43650073pab.164.1366942622630; Thu, 25 Apr 2013 19:17:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.159.97 with HTTP; Thu, 25 Apr 2013 19:16:32 -0700 (PDT) From: Eitan Adler Date: Thu, 25 Apr 2013 22:16:32 -0400 Message-ID: Subject: Some improvements to rm(1) To: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkyNWNlhenQK+VrGYJ81V73/yyA410Cdx5LdbXJoP8RBXaTC8VdKz6vTM7DMTzbstUpN/kE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 02:17:03 -0000 Anyone have thoughts on the following? commit 82c78ba923d8ce4a1bfbb309658c49021c8bb384 Author: Eitan Adler Date: Thu Apr 25 22:14:49 2013 -0400 Take some improvements from DragonFlyBSD: - add const where appropriate - add static where appropriate - fix a whitespace issues Obtained from: DragonFlyBSD diff --git a/bin/rm/rm.c b/bin/rm/rm.c index 1014921..660042b 100644 --- a/bin/rm/rm.c +++ b/bin/rm/rm.c @@ -63,15 +63,15 @@ static int rflag, Iflag, xflag; static uid_t uid; static volatile sig_atomic_t info; -int check(char *, char *, struct stat *); -int check2(char **); -void checkdot(char **); -void checkslash(char **); -void rm_file(char **); -int rm_overwrite(char *, struct stat *); -void rm_tree(char **); +static int check(const char *, const char *, struct stat *); +static int check2(char **); +static void checkdot(char **); +static void checkslash(char **); +static void rm_file(char **); +static int rm_overwrite(const char *, struct stat *); +static void rm_tree(char **); static void siginfo(int __unused); -void usage(void); +static void usage(void); /* * rm -- @@ -173,7 +173,7 @@ main(int argc, char *argv[]) exit (eval); } -void +static void rm_tree(char **argv) { FTS *fts; @@ -418,7 +418,7 @@ rm_file(char **argv) * have kernel support. */ int -rm_overwrite(char *file, struct stat *sbp) +rm_overwrite(const char *file, struct stat *sbp) { struct stat sb, sb2; struct statfs fsb; @@ -484,8 +484,8 @@ err: eval = 1; } -int -check(char *path, char *name, struct stat *sp) +static int +check(const char *path, const char *name, struct stat *sp) { int ch, first; char modep[15], *flagsp; @@ -496,7 +496,7 @@ check(char *path, char *name, struct stat *sp) else { /* * If it's not a symbolic link and it's unwritable and we're - * talking to a terminal, ask. Symbolic links are excluded + * talking to a terminal, ask. Symbolic links are excluded * because their permissions are meaningless. Check stdin_ok * first because we may not have stat'ed the file. */ @@ -529,7 +529,7 @@ check(char *path, char *name, struct stat *sp) } #define ISSLASH(a) ((a)[0] == '/' && (a)[1] == '\0') -void +static void checkslash(char **argv) { char **t, **u; @@ -549,7 +549,7 @@ checkslash(char **argv) } } -int +static int check2(char **argv) { struct stat st; @@ -600,7 +600,7 @@ check2(char **argv) } #define ISDOT(a) ((a)[0] == '.' && (!(a)[1] || ((a)[1] == '.' && !(a)[2]))) -void +static void checkdot(char **argv) { char *p, **save, **t; @@ -624,7 +624,7 @@ checkdot(char **argv) } } -void +static void usage(void) { commit 4799c480694b379f73483998e11341bffd3ffa3e Author: Eitan Adler Date: Thu Apr 25 22:03:28 2013 -0400 Add -x option to avoid crossing mount points when removing a hierarchy. Inspired by: DragonflyBSD diff --git a/bin/rm/rm.1 b/bin/rm/rm.1 index 3588f38..824b627 100644 --- a/bin/rm/rm.1 +++ b/bin/rm/rm.1 @@ -32,7 +32,7 @@ .\" @(#)rm.1 8.5 (Berkeley) 12/5/94 .\" $FreeBSD$ .\" -.Dd March 15, 2013 +.Dd April 25, 2013 .Dt RM 1 .Os .Sh NAME @@ -42,7 +42,7 @@ .Sh SYNOPSIS .Nm .Op Fl f | i -.Op Fl dIPRrvW +.Op Fl dIPRrvWx .Ar .Nm unlink .Ar file @@ -132,6 +132,8 @@ Attempt to undelete the named files. Currently, this option can only be used to recover files covered by whiteouts in a union file system (see .Xr undelete 2 ) . +.It Fl x +When removing a hierarchy, do not cross mount points. .El .Pp The diff --git a/bin/rm/rm.c b/bin/rm/rm.c index a450057..1014921 100644 --- a/bin/rm/rm.c +++ b/bin/rm/rm.c @@ -59,7 +59,7 @@ __FBSDID("$FreeBSD$"); #include static int dflag, eval, fflag, iflag, Pflag, vflag, Wflag, stdin_ok; -static int rflag, Iflag; +static int rflag, Iflag, xflag; static uid_t uid; static volatile sig_atomic_t info; @@ -106,8 +106,8 @@ main(int argc, char *argv[]) exit(eval); } - Pflag = rflag = 0; - while ((ch = getopt(argc, argv, "dfiIPRrvW")) != -1) + Pflag = rflag = xflag = 0; + while ((ch = getopt(argc, argv, "dfiIPRrvWx")) != -1) switch(ch) { case 'd': dflag = 1; @@ -136,6 +136,9 @@ main(int argc, char *argv[]) case 'W': Wflag = 1; break; + case 'x': + xflag = 1; + break; default: usage(); } @@ -196,6 +199,8 @@ rm_tree(char **argv) flags |= FTS_NOSTAT; if (Wflag) flags |= FTS_WHITEOUT; + if (xflag) + flags |= FTS_XDEV; if (!(fts = fts_open(argv, flags, NULL))) { if (fflag && errno == ENOENT) return; @@ -624,7 +629,7 @@ usage(void) { (void)fprintf(stderr, "%s\n%s\n", - "usage: rm [-f | -i] [-dIPRrvW] file ...", + "usage: rm [-f | -i] [-dIPRrvWx] file ...", " unlink file"); exit(EX_USAGE); } -- Eitan Adler From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 02:50:48 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 729C235D for ; Fri, 26 Apr 2013 02:50:48 +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 A0A891742 for ; Fri, 26 Apr 2013 02:50:46 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.5/8.14.5) with ESMTP id r3Q2onGX050834; Thu, 25 Apr 2013 21:50:49 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.5/8.14.5/Submit) id r3Q2onhC050833; Thu, 25 Apr 2013 21:50:49 -0500 (CDT) (envelope-from brooks) Date: Thu, 25 Apr 2013 21:50:49 -0500 From: Brooks Davis To: Eitan Adler Subject: Re: Some improvements to rm(1) Message-ID: <20130426025049.GC50623@lor.one-eyed-alien.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UHN/qo2QbUvPLonB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 02:50:48 -0000 --UHN/qo2QbUvPLonB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 25, 2013 at 10:16:32PM -0400, Eitan Adler wrote: > Anyone have thoughts on the following? >=20 > commit 82c78ba923d8ce4a1bfbb309658c49021c8bb384 > Author: Eitan Adler > Date: Thu Apr 25 22:14:49 2013 -0400 >=20 > Take some improvements from DragonFlyBSD: > - add const where appropriate > - add static where appropriate > - fix a whitespace issues The no-op changes look more correct to me. I think the -x option seems a bit odd. What is the use case? At a first thought, it seems to raise more questions than it resolves. -- Brooks > Obtained from: DragonFlyBSD >=20 > diff --git a/bin/rm/rm.c b/bin/rm/rm.c > index 1014921..660042b 100644 > --- a/bin/rm/rm.c > +++ b/bin/rm/rm.c > @@ -63,15 +63,15 @@ static int rflag, Iflag, xflag; > static uid_t uid; > static volatile sig_atomic_t info; >=20 > -int check(char *, char *, struct stat *); > -int check2(char **); > -void checkdot(char **); > -void checkslash(char **); > -void rm_file(char **); > -int rm_overwrite(char *, struct stat *); > -void rm_tree(char **); > +static int check(const char *, const char *, struct stat *); > +static int check2(char **); > +static void checkdot(char **); > +static void checkslash(char **); > +static void rm_file(char **); > +static int rm_overwrite(const char *, struct stat *); > +static void rm_tree(char **); > static void siginfo(int __unused); > -void usage(void); > +static void usage(void); >=20 > /* > * rm -- > @@ -173,7 +173,7 @@ main(int argc, char *argv[]) > exit (eval); > } >=20 > -void > +static void > rm_tree(char **argv) > { > FTS *fts; > @@ -418,7 +418,7 @@ rm_file(char **argv) > * have kernel support. > */ > int > -rm_overwrite(char *file, struct stat *sbp) > +rm_overwrite(const char *file, struct stat *sbp) > { > struct stat sb, sb2; > struct statfs fsb; > @@ -484,8 +484,8 @@ err: eval =3D 1; > } >=20 >=20 > -int > -check(char *path, char *name, struct stat *sp) > +static int > +check(const char *path, const char *name, struct stat *sp) > { > int ch, first; > char modep[15], *flagsp; > @@ -496,7 +496,7 @@ check(char *path, char *name, struct stat *sp) > else { > /* > * If it's not a symbolic link and it's unwritable and we're > - * talking to a terminal, ask. Symbolic links are excluded > + * talking to a terminal, ask. Symbolic links are excluded > * because their permissions are meaningless. Check stdin_ok > * first because we may not have stat'ed the file. > */ > @@ -529,7 +529,7 @@ check(char *path, char *name, struct stat *sp) > } >=20 > #define ISSLASH(a) ((a)[0] =3D=3D '/' && (a)[1] =3D=3D '\0') > -void > +static void > checkslash(char **argv) > { > char **t, **u; > @@ -549,7 +549,7 @@ checkslash(char **argv) > } > } >=20 > -int > +static int > check2(char **argv) > { > struct stat st; > @@ -600,7 +600,7 @@ check2(char **argv) > } >=20 > #define ISDOT(a) ((a)[0] =3D=3D '.' && (!(a)[1] || ((a)[1] =3D=3D '.' &&= !(a)[2]))) > -void > +static void > checkdot(char **argv) > { > char *p, **save, **t; > @@ -624,7 +624,7 @@ checkdot(char **argv) > } > } >=20 > -void > +static void > usage(void) > { >=20 >=20 > commit 4799c480694b379f73483998e11341bffd3ffa3e > Author: Eitan Adler > Date: Thu Apr 25 22:03:28 2013 -0400 >=20 > Add -x option to avoid crossing mount points when removing a hierarch= y. >=20 > Inspired by: DragonflyBSD >=20 > diff --git a/bin/rm/rm.1 b/bin/rm/rm.1 > index 3588f38..824b627 100644 > --- a/bin/rm/rm.1 > +++ b/bin/rm/rm.1 > @@ -32,7 +32,7 @@ > .\" @(#)rm.1 8.5 (Berkeley) 12/5/94 > .\" $FreeBSD$ > .\" > -.Dd March 15, 2013 > +.Dd April 25, 2013 > .Dt RM 1 > .Os > .Sh NAME > @@ -42,7 +42,7 @@ > .Sh SYNOPSIS > .Nm > .Op Fl f | i > -.Op Fl dIPRrvW > +.Op Fl dIPRrvWx > .Ar > .Nm unlink > .Ar file > @@ -132,6 +132,8 @@ Attempt to undelete the named files. > Currently, this option can only be used to recover > files covered by whiteouts in a union file system (see > .Xr undelete 2 ) . > +.It Fl x > +When removing a hierarchy, do not cross mount points. > .El > .Pp > The > diff --git a/bin/rm/rm.c b/bin/rm/rm.c > index a450057..1014921 100644 > --- a/bin/rm/rm.c > +++ b/bin/rm/rm.c > @@ -59,7 +59,7 @@ __FBSDID("$FreeBSD$"); > #include >=20 > static int dflag, eval, fflag, iflag, Pflag, vflag, Wflag, stdin_ok; > -static int rflag, Iflag; > +static int rflag, Iflag, xflag; > static uid_t uid; > static volatile sig_atomic_t info; >=20 > @@ -106,8 +106,8 @@ main(int argc, char *argv[]) > exit(eval); > } >=20 > - Pflag =3D rflag =3D 0; > - while ((ch =3D getopt(argc, argv, "dfiIPRrvW")) !=3D -1) > + Pflag =3D rflag =3D xflag =3D 0; > + while ((ch =3D getopt(argc, argv, "dfiIPRrvWx")) !=3D -1) > switch(ch) { > case 'd': > dflag =3D 1; > @@ -136,6 +136,9 @@ main(int argc, char *argv[]) > case 'W': > Wflag =3D 1; > break; > + case 'x': > + xflag =3D 1; > + break; > default: > usage(); > } > @@ -196,6 +199,8 @@ rm_tree(char **argv) > flags |=3D FTS_NOSTAT; > if (Wflag) > flags |=3D FTS_WHITEOUT; > + if (xflag) > + flags |=3D FTS_XDEV; > if (!(fts =3D fts_open(argv, flags, NULL))) { > if (fflag && errno =3D=3D ENOENT) > return; > @@ -624,7 +629,7 @@ usage(void) > { >=20 > (void)fprintf(stderr, "%s\n%s\n", > - "usage: rm [-f | -i] [-dIPRrvW] file ...", > + "usage: rm [-f | -i] [-dIPRrvWx] file ...", > " unlink file"); > exit(EX_USAGE); > } >=20 >=20 > --=20 > Eitan Adler > _______________________________________________ > 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 --UHN/qo2QbUvPLonB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFReeuJXY6L6fI4GtQRApQZAJ4hmN3sT7xF22MhOK+JBnyevk3zlACgm0Ir il9I1z9sY2t9q818gPKNvf0= =N366 -----END PGP SIGNATURE----- --UHN/qo2QbUvPLonB-- From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 02:56:47 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EE386640 for ; Fri, 26 Apr 2013 02:56:47 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) by mx1.freebsd.org (Postfix) with ESMTP id C9B1B1775 for ; Fri, 26 Apr 2013 02:56:47 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id kp14so2242480pab.36 for ; Thu, 25 Apr 2013 19:56:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=5ii5YXQVLoqSKzTw/Ykr/np3H75onVdVTrXpVe++aE0=; b=cyq4Dln4EwJ557Fcg7ZB8sTkWd/6SHclxNs1Ft12e05roBQDUGgvGz5Q9vi8aTWQop K0P9lRW9uPai63m11swjH3MtxQZhewJxGQri2MhxjnR78UFenREtPZKtCOn1CFqB+lyq UZ50xPuP1KAWxLYqWzF4OmWItpBb/KuzGKmkE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=5ii5YXQVLoqSKzTw/Ykr/np3H75onVdVTrXpVe++aE0=; b=EScTM5WGy2l8SMRRmckiRBNtc52gjE07hGItdMChMn2jWr+chBoHdvnBkJJjvujkX0 kdl3IsxYTV/T5iZUYKDG+0mX/RP5soP9Zx29HVyGDNKFbBj16j2Ho7FJ+exenE5fY2h8 08gDdW/cF0/zI4jESNBPN8yZjZolsNj878Ila4WSx0aKVRWvEoz6BiBfqJ5q68sKqo5i srq4mEUU/X+K8fWcL7VYhE6fgTwpt52C/d8Y+4nR4UZxsqdCbIYOK9WXvv456k5VbUZc 1y9OT3wy2t1viCWFbIeg2+bduW9ef3xa/xsRIj4GdWzUSyGoukPUtd1jnPtiEAY+Apy0 bGzw== X-Received: by 10.66.118.142 with SMTP id km14mr27667302pab.129.1366945000871; Thu, 25 Apr 2013 19:56:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.159.97 with HTTP; Thu, 25 Apr 2013 19:56:10 -0700 (PDT) In-Reply-To: <20130426025049.GC50623@lor.one-eyed-alien.net> References: <20130426025049.GC50623@lor.one-eyed-alien.net> From: Eitan Adler Date: Thu, 25 Apr 2013 22:56:10 -0400 Message-ID: Subject: Re: Some improvements to rm(1) To: Brooks Davis Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkh8gj4Ajccb3yWs9R62CUCJDjv2V6sqQ+BBtdRye8wGR3p6fmK4LUQa2+ruLGyZSmkEBCI Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 02:56:48 -0000 On 25 April 2013 22:50, Brooks Davis wrote: > On Thu, Apr 25, 2013 at 10:16:32PM -0400, Eitan Adler wrote: >> Anyone have thoughts on the following? >> >> commit 82c78ba923d8ce4a1bfbb309658c49021c8bb384 >> Author: Eitan Adler >> Date: Thu Apr 25 22:14:49 2013 -0400 >> >> Take some improvements from DragonFlyBSD: >> - add const where appropriate >> - add static where appropriate >> - fix a whitespace issues > > The no-op changes look more correct to me. > > I think the -x option seems a bit odd. What is the use case? At a > first thought, it seems to raise more questions than it resolves. It goes along with cp -x, find -x, and others. Quick example #1: You have /usr/ports /usr/ports/distfiles as different mount points it lets you wipe /usr/ports without wiping your distfile cache. Quick example #2: You have /usr/src/ null mounted in every user's /home/ and you want to wipe one home directory. -- Eitan Adler From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 03:22:21 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 100E9251 for ; Fri, 26 Apr 2013 03:22:21 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by mx1.freebsd.org (Postfix) with ESMTP id DE260192F for ; Fri, 26 Apr 2013 03:22:20 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id xa7so1004435pbc.19 for ; Thu, 25 Apr 2013 20:22:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=jowX2TvQSpP2q6RzUSdAhz76hSF1SHmb0HkX8gHrMQ4=; b=tTrztXokclEq4bYS7nwQ+yNQsn4Z7MJOO3rJXx1X132dgHyk0C9qRFgifoYikO2jYi wy3kCmOwhxWn0CQoH/HYlfqAgc/JUpUzfqTkMtyAK0qidY+LqOuqsE+AzWMppRXxkNBO lUUvMla7UtGlCBj/xFIeyHxGm5TL2eNChQrw8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=jowX2TvQSpP2q6RzUSdAhz76hSF1SHmb0HkX8gHrMQ4=; b=cJ/jnnYROMRudqh/5QCP8LLhC8COVOChycQDELXdw6R9/u+28m30pOtwrmZ3b6n2FB XXlgK5nuASKIHQXv7fqg4o3GPw0sEcAfyC+GFYsyPbWoyoJJhCeNaGTg6JysNf6fpt+i ytAreEpfYjdIRf6I5vyue06/VgeLvXYDq4HlRrsUNbvo7PlRj5/NJcDIww4bAgtbHB2w YK85OgRpUwl8pe0jK1KP3Z4jO4FX3oa655lq/4pHd6MtXYGrkeDzverM0MWd9X5te3dQ ChtQxiKQYpc3pTIUToSNYqC8uGlwtqfNJjjyIvIw8zL/KIwVAF259N5/H8b45GYhSYin CaIA== X-Received: by 10.66.144.170 with SMTP id sn10mr28262330pab.42.1366946540587; Thu, 25 Apr 2013 20:22:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.159.97 with HTTP; Thu, 25 Apr 2013 20:21:50 -0700 (PDT) In-Reply-To: References: <20130426025049.GC50623@lor.one-eyed-alien.net> From: Eitan Adler Date: Thu, 25 Apr 2013 23:21:50 -0400 Message-ID: Subject: Re: Some improvements to rm(1) To: Brooks Davis Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnl7sqnj6jsoWgbv3VlzcyFLN89UH6vTnKtmB7Yc0/fJfmXg+LmsGpeaPUwlwNvuZpT/13M Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 03:22:21 -0000 On 25 April 2013 22:56, Eitan Adler wrote: > On 25 April 2013 22:50, Brooks Davis wrote: >> On Thu, Apr 25, 2013 at 10:16:32PM -0400, Eitan Adler wrote: >>> Anyone have thoughts on the following? >>> >>> commit 82c78ba923d8ce4a1bfbb309658c49021c8bb384 >>> Author: Eitan Adler >>> Date: Thu Apr 25 22:14:49 2013 -0400 >>> >>> Take some improvements from DragonFlyBSD: >>> - add const where appropriate >>> - add static where appropriate >>> - fix a whitespace issues >> >> The no-op changes look more correct to me. >> >> I think the -x option seems a bit odd. What is the use case? At a >> first thought, it seems to raise more questions than it resolves. > > It goes along with cp -x, find -x, and others. > > Quick example #1: You have /usr/ports /usr/ports/distfiles as > different mount points it lets you wipe /usr/ports without wiping your > distfile cache. > > Quick example #2: You have /usr/src/ null mounted in every user's > /home/ and you want to wipe one home directory. I just realized that this is a poor example because /usr/src/ is likely read-only, but the idea stands. -- Eitan Adler From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 08:02:03 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A6670A0C for ; Fri, 26 Apr 2013 08:02:03 +0000 (UTC) (envelope-from mikemandarine@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6E2971477 for ; Fri, 26 Apr 2013 08:02:03 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id ht11so3608670vcb.27 for ; Fri, 26 Apr 2013 01:02:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=x8EU1MYUhwrpczvYATAuQqMT6GsWHef4bSSyHFWwJ6c=; b=IgBMqQYB6cm5Ta4dg329v16ny+Q/AlnZQhqD1J5gH8TfIjkLnnb5OMN87cLQwvhJxw qwSkmA2x33Jvo2GwUQ4+lOrfI4Hki0XEMqm46MDreJrXsrXpmaxL5dApeOgF2cJbOkTP 1Euy5fWj/SDDI8MEnz9xgjwddLkyHm+dI4C8R8/iFglOjOkSBDSbEMcz3zNsWcCI6Iko kKyJ4pjjOFUPtEqpxKhKaGI9oBrDFO9+wCq1a+UF6aH52LFoJvF1oAzic5E+qNc3rAJ3 tecAo7iTzw/IHEBsWeMslZxVcokjNNaEa/ErKWTYRlvg2YV7lJL7wXaVJPWn/t41Jiq3 6oVg== MIME-Version: 1.0 X-Received: by 10.220.9.3 with SMTP id j3mr28514599vcj.56.1366963322731; Fri, 26 Apr 2013 01:02:02 -0700 (PDT) Received: by 10.220.31.207 with HTTP; Fri, 26 Apr 2013 01:02:02 -0700 (PDT) Date: Fri, 26 Apr 2013 10:02:02 +0200 Message-ID: Subject: Port GlusterFS as a GSoC 2013 project From: Mike Ma To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 08:02:03 -0000 Hi there, I'm now a student and trying to get involved in GSoC this year. I found the proposal of about GlusterFS in the idea list wiki page very interesting to me, possibly it will be porting from NetBSD implementation. As I'm quite distant from idea owner so there's a big time difference, he also suggested me to try to find some folks that are physically closer to me to help mentoring. So I'm writing to ask if there's any folk in Europe is interested helping me with the project in any way, it could be easier for communication and discussion. Thanks a lot. Regards, Mike From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 07:48:14 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E8C26D90 for ; Fri, 26 Apr 2013 07:48:14 +0000 (UTC) (envelope-from mikemandarine@gmail.com) Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id AE6E51316 for ; Fri, 26 Apr 2013 07:48:14 +0000 (UTC) Received: by mail-ve0-f180.google.com with SMTP id pb11so1668140veb.25 for ; Fri, 26 Apr 2013 00:48:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=CwrFT53ZQSnvaCX7kiDfs9bXk0H/cVghWQmfpDMVjW4=; b=QfWo0ovUcaDxK/dGcacXGQb6rZo3PagiKvTzGAMguYA9lwnazw4COlSsRZmRcZHKzV r83VV7YcnSm6SXS4rVEz+pLHYaubQ2ZZIap4L1wghXnK5USqjNLIQTiBhwIRBs+vj3Br bc4+6unZU74vgSjcHZHDSTiY/HJSv7k1pyxJpqlwj/3KUeEeer6l3YjCSGNIfszRIrIr I1pN66ErkIS1NN7mOR6AAFLslYZaQDlFx0e6MrU6EpHfiVbA57xY3xMHJz8x6g6ioGxB w4EvoenQZW3l3lkrIgl7PAOPzgH8E+gayzERHnMmD01fhxqKMT0w9IR2ZwdkPAChKAQE lOLQ== MIME-Version: 1.0 X-Received: by 10.52.71.4 with SMTP id q4mr24191790vdu.8.1366962494146; Fri, 26 Apr 2013 00:48:14 -0700 (PDT) Received: by 10.220.31.207 with HTTP; Fri, 26 Apr 2013 00:48:14 -0700 (PDT) Date: Fri, 26 Apr 2013 09:48:14 +0200 Message-ID: Subject: Port GlusterFS as a GSoC project From: Mike Ma To: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Fri, 26 Apr 2013 11:26:06 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 07:48:15 -0000 Hi there, I'm now a student and trying to get involved in GSoC this year. I found the proposal of about GlusterFS in the idea list wiki page very interesting to me, possibly it will be porting from NetBSD implementation. As I'm quite distant from idea owner, he also suggested me to try to find some folks that are physically closer to me to help mentoring. So I'm writing to ask if there's any folk in Europe is interested helping me with the project in any way, it could be easier for communication and discussion. Thanks a lot. Regards, Mike From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 12:22:30 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 19D644CB; Fri, 26 Apr 2013 12:22:30 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (unknown [IPv6:2001:610:1108:5012::107]) by mx1.freebsd.org (Postfix) with ESMTP id D615D15EC; Fri, 26 Apr 2013 12:22:29 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 963621203DB; Fri, 26 Apr 2013 14:22:14 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 72E9728493; Fri, 26 Apr 2013 14:22:14 +0200 (CEST) Date: Fri, 26 Apr 2013 14:22:14 +0200 From: Jilles Tjoelker To: Eitan Adler Subject: Re: Some improvements to rm(1) Message-ID: <20130426122214.GA9086@stack.nl> References: <20130426025049.GC50623@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Hackers , Brooks Davis X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 12:22:30 -0000 On Thu, Apr 25, 2013 at 10:56:10PM -0400, Eitan Adler wrote: > On 25 April 2013 22:50, Brooks Davis wrote: > > On Thu, Apr 25, 2013 at 10:16:32PM -0400, Eitan Adler wrote: > >> Anyone have thoughts on the following? > >> commit 82c78ba923d8ce4a1bfbb309658c49021c8bb384 > >> Author: Eitan Adler > >> Date: Thu Apr 25 22:14:49 2013 -0400 > >> Take some improvements from DragonFlyBSD: > >> - add const where appropriate > >> - add static where appropriate > >> - fix a whitespace issues > > > > The no-op changes look more correct to me. > > I think the -x option seems a bit odd. What is the use case? At a > > first thought, it seems to raise more questions than it resolves. > It goes along with cp -x, find -x, and others. > Quick example #1: You have /usr/ports /usr/ports/distfiles as > different mount points it lets you wipe /usr/ports without wiping your > distfile cache. > Quick example #2: You have /usr/src/ null mounted in every user's > /home/ and you want to wipe one home directory. Hmm, isn't this already possible using find -x DIR -delete ? There will be an error message 'Device busy' about attempting to delete the mount point but this does not even affect the exit status and all files not under the mount point are removed. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 12:23:41 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 83F156C0 for ; Fri, 26 Apr 2013 12:23:41 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by mx1.freebsd.org (Postfix) with ESMTP id 5DD38160C for ; Fri, 26 Apr 2013 12:23:41 +0000 (UTC) Received: by mail-pd0-f172.google.com with SMTP id 4so2427865pdd.31 for ; Fri, 26 Apr 2013 05:23:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=A89oRx1Sp/TbHdEkhLeGN+/9W+ryzOvrcsB+XrtaLG4=; b=ppEw2grR7DYeCmnyUwh4eFBpvFfzS2MLixh9T2fwLUwF0zdhUwspmhtz0RZ11kG9IS yxTMWGvbnYR5TmaXoAvDJyJReW0ltrxP7WTIXdNm3QhNQltPicvIEViOn0d8IlY2HoL0 Ok1wYbhg6WRz4mVqfA9qhlSoe7h66Y6QjSsNY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=A89oRx1Sp/TbHdEkhLeGN+/9W+ryzOvrcsB+XrtaLG4=; b=eMa/zH7rNDOdl+nwlDHFg5OSRHraJwuZwrZb3Cmt/G+6vj7MhJZSYBza5ZB6F/mZcY AjapGfPYhii70AVaNIA8MR83Ov3BGM5JJqGgA+EbB7PlXoKuUburKL8GcAZASARKs8A4 Bj1ICj/79jz/LRpak4sFqlDmO+Dj3xcrHuCpXGgv/85kIT9sNbC6CuiPv8LVkAml1SBD Jp0+e8s4ZbJCemFtS004EfJP2uEf8Fyjma4eNVCZA3L4AV/glk8UuQEUMt2LriRGDu5O x1r7KmNwPocu+9Ih0LYZw9B3B0dJXbjniwHR+BD5JvB/os2qG4wj3bgUeSjk7z9YChFf wzpQ== X-Received: by 10.68.253.232 with SMTP id ad8mr57368050pbd.164.1366979015672; Fri, 26 Apr 2013 05:23:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.159.97 with HTTP; Fri, 26 Apr 2013 05:23:05 -0700 (PDT) In-Reply-To: <20130426122214.GA9086@stack.nl> References: <20130426025049.GC50623@lor.one-eyed-alien.net> <20130426122214.GA9086@stack.nl> From: Eitan Adler Date: Fri, 26 Apr 2013 08:23:05 -0400 Message-ID: Subject: Re: Some improvements to rm(1) To: Jilles Tjoelker Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkhXU72ry/cxup3CQ1IByURTlCXd+/Aos/u/r7AaaAF+y2QxJs5ImC8wP4TCBK9hy3huJwm Cc: FreeBSD Hackers , Brooks Davis X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 12:23:41 -0000 On 26 April 2013 08:22, Jilles Tjoelker wrote: > On Thu, Apr 25, 2013 at 10:56:10PM -0400, Eitan Adler wrote: >> On 25 April 2013 22:50, Brooks Davis wrote: >> > On Thu, Apr 25, 2013 at 10:16:32PM -0400, Eitan Adler wrote: >> >> Anyone have thoughts on the following? > >> >> commit 82c78ba923d8ce4a1bfbb309658c49021c8bb384 >> >> Author: Eitan Adler >> >> Date: Thu Apr 25 22:14:49 2013 -0400 > >> >> Take some improvements from DragonFlyBSD: >> >> - add const where appropriate >> >> - add static where appropriate >> >> - fix a whitespace issues >> > >> > The no-op changes look more correct to me. > >> > I think the -x option seems a bit odd. What is the use case? At a >> > first thought, it seems to raise more questions than it resolves. > >> It goes along with cp -x, find -x, and others. > >> Quick example #1: You have /usr/ports /usr/ports/distfiles as >> different mount points it lets you wipe /usr/ports without wiping your >> distfile cache. > >> Quick example #2: You have /usr/src/ null mounted in every user's >> /home/ and you want to wipe one home directory. > > Hmm, isn't this already possible using find -x DIR -delete ? Yes, rm's functionality can be fully replicated by find. -- Eitan Adler From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 13:34:12 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 63EBF88D for ; Fri, 26 Apr 2013 13:34:12 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 37243192C for ; Fri, 26 Apr 2013 13:34:12 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id 10so4833163ied.5 for ; Fri, 26 Apr 2013 06:34:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=NozcSU/AyQIJqnI/7TSUroC3POaLz0f3jEGBKkpOeU8=; b=qYE+IUNKN7xdab4GTJH2MfBDcYfpAo/KthVBOd+HIgqJjnDgsWSsE4nVHq31P6IBEB leQFv5ICa94iduKfvahphiPLYhrcntaijQSjf6bD4p4SF04nkfAyE8PKAScwl5P/x8tv YvOYbe6OsMiv5aoRRXmwgvKCRftEx9xVjNvLSU3gObjYrW0JC+uJ5V59iFre4MQmjm67 ho6M+nqoJdN+vrfUVo4PAffkg7mhuPswZDzpNdFx+UWWeyQh2baPCu1r2MKP8Ltl8vKv ED1pFh4X1dLkm00Q9kvWpWlaFGHjlObnvn0TtMYMlKhT/6h55Jrk68rGknxAIDxhTK4M 1RWw== X-Received: by 10.50.32.4 with SMTP id e4mr1752532igi.95.1366983246228; Fri, 26 Apr 2013 06:34:06 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPSA id xf4sm2855079igb.8.2013.04.26.06.34.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Apr 2013 06:34:05 -0700 (PDT) Message-ID: <517A8242.6090509@gmail.com> Date: Fri, 26 Apr 2013 08:33:54 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Some improvements to rm(1) References: <20130426025049.GC50623@lor.one-eyed-alien.net> <20130426122214.GA9086@stack.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 13:34:12 -0000 On 4/26/2013 7:23 AM, Eitan Adler wrote: > Yes, rm's functionality can be fully replicated by find. > > As well as anything using -R. From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 14:14:51 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BDCDA487 for ; Fri, 26 Apr 2013 14:14:51 +0000 (UTC) (envelope-from drue@therub.org) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) by mx1.freebsd.org (Postfix) with ESMTP id 8419D1BD4 for ; Fri, 26 Apr 2013 14:14:51 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id dx4so210174qab.2 for ; Fri, 26 Apr 2013 07:14:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=n/81wZK+H4UY9UGrbzhz4Fx0RncLJifwHTTxWwkPurs=; b=inWYGM3o6i6bYHkTF9shbmugMDRA6W6JhGjBQPltwK+0+vwcv1cvtazKcY+UYlxHTK AjRXzwRkuwJ8Eu0YdUOZ9k7DlapTci0blR4C4halLf8zFkt1yujMpLcmi7xZlisEQ4IZ rpmKk3R+v0m1swPHEnQCR+1gaLKq2OOgmUMIV4OxLLHt7mJWl7wzurBY0pOIlEBO5Ayv DmX/C0xCntL6nplu5F4fBo9MJJBSJzvCZNOayRj7gxIkQpsDUZn2VzxldOsK5YneawrN 7+RJVW9LxezqZXkiKgqoaP6Zul95g6dJmmuJKtMTfkAK2+ZuuP8xhj55r6ApVlb/8g0H rIJw== MIME-Version: 1.0 X-Received: by 10.229.67.4 with SMTP id p4mr965802qci.44.1366985690570; Fri, 26 Apr 2013 07:14:50 -0700 (PDT) Received: by 10.49.87.134 with HTTP; Fri, 26 Apr 2013 07:14:50 -0700 (PDT) In-Reply-To: <20130426025049.GC50623@lor.one-eyed-alien.net> References: <20130426025049.GC50623@lor.one-eyed-alien.net> Date: Fri, 26 Apr 2013 09:14:50 -0500 Message-ID: Subject: Re: Some improvements to rm(1) From: Dan Rue To: Brooks Davis X-Gm-Message-State: ALoCoQnpNOVBYn/hA/cumynQynDt4meiiKYynirSu/JRt8PsXH8DLL+vTI6qBWH/b5F/ZCPDnuDy Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Eitan Adler , FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 14:14:51 -0000 On Thu, Apr 25, 2013 at 9:50 PM, Brooks Davis wrote: > I think the -x option seems a bit odd. What is the use case? At a > first thought, it seems to raise more questions than it resolves. > I was cleaning up a system a year ago and I had an "rm -rf" traverse into a production NFS mountpoint.. oops. I only realized it when it was taking longer than I expected so I stopped it to investigate. Had to restore a bunch of data from backups. Thank you for proposing the patch, I hope it gets committed. Dan From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 26 14:17:29 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 21B80747 for ; Fri, 26 Apr 2013 14:17:29 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id DC9281BEE for ; Fri, 26 Apr 2013 14:17:28 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 346BF3592E7; Fri, 26 Apr 2013 16:17:27 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 1B4AF28493; Fri, 26 Apr 2013 16:17:27 +0200 (CEST) Date: Fri, 26 Apr 2013 16:17:27 +0200 From: Jilles Tjoelker To: Joshua Isom Subject: Re: Some improvements to rm(1) Message-ID: <20130426141726.GA85955@stack.nl> References: <20130426025049.GC50623@lor.one-eyed-alien.net> <20130426122214.GA9086@stack.nl> <517A8242.6090509@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <517A8242.6090509@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 14:17:29 -0000 On Fri, Apr 26, 2013 at 08:33:54AM -0500, Joshua Isom wrote: > On 4/26/2013 7:23 AM, Eitan Adler wrote: > > Yes, rm's functionality can be fully replicated by find. > As well as anything using -R. Emulating other -R things using find becomes quite slow when you don't want to impose {PATH_MAX} limits or open up symlink-based race windows because the only safe option is -execdir UTILITY {} \;. Any find command based on -exec, -print or -print0 passes pathnames which are subject to {PATH_MAX} limits and directories concurrently replaced with symlinks. The construct -execdir ... {} + is unusably broken in older FreeBSD versions and gives no advantage compared to -execdir ... {} \; in recent -CURRENT. With -L, this is not a new problem because symlinks are followed anyway and the underlying code (fts(3)) always imposes the {PATH_MAX} limit in that case. The -delete primary is safe like -execdir. I'm not entirely sure about this because the rm(1) patch is simple and the new syntax is fairly clear. -- Jilles Tjoelker From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 00:06:22 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 49E4B564 for ; Sat, 27 Apr 2013 00:06:22 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-da0-x229.google.com (mail-da0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) by mx1.freebsd.org (Postfix) with ESMTP id 264C014C2 for ; Sat, 27 Apr 2013 00:06:22 +0000 (UTC) Received: by mail-da0-f41.google.com with SMTP id p8so572163dan.14 for ; Fri, 26 Apr 2013 17:06:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=ywjXby8fiNHrSCShxuXHDFki+7dtOKs8BF7ZeiinsMQ=; b=Ais332loMivcXD4VWHO97o4yJ2Zf45DWIwaQPk83DF8+R5xSDCYKBhLp4jCngBT6ZU bdxJtBETzalne5HXWitjErEFrapAigq7+wSfltCCCO0i37YK1piQ/lwAWqR2HG8O3Ra1 NPy+5zNS/VOua2Kq3YrbXT3yApfCN3AjaBbwo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=ywjXby8fiNHrSCShxuXHDFki+7dtOKs8BF7ZeiinsMQ=; b=Rh4db1SUtjm+alc/eylJRhCT7mzRWEcGTpV9JVhE+F2LpfN9zYbGXoYqhVDajsgP+e tCzJhuAktVPiTOWNAXBzMZWxzjd0+16z9D+Q3Inp1I/fCW98hKVFxBjXY6HFop9Zqa3U Gr10UYAWNqXcAfF2oPuU1qjZx7PvIzU92U32GPEBHug24mQa96B1ir/TA8/VvJB4g1z0 XWwV/edByEg2CUMHDpRUZxJCzwbbXIDjEam1cKX5Id602r7ipYFl/fA+GJxH1vtHs89N oq9dFhVCnpGEMQc74Ec8s1pkITZYc76Z/eXujq/LfiSyHCzNxDPzF5902vDyb9Av/N13 3VHA== X-Received: by 10.68.253.232 with SMTP id ad8mr60052465pbd.164.1367021181942; Fri, 26 Apr 2013 17:06:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.159.97 with HTTP; Fri, 26 Apr 2013 17:05:50 -0700 (PDT) From: Eitan Adler Date: Fri, 26 Apr 2013 20:05:50 -0400 Message-ID: Subject: makeman issues To: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnQMDiUlqwLQVTNHJ71wb3e4FH1hj5qhnaIIu/heLjXoQ9D74YT7UPL68MuEwIZRmSMmcI+ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 00:06:22 -0000 I'm trying to regenerate src.conf.5 after my recent WITH*_IDEA removal but the diff shows: Does anyone know why WITHOUT_BIND_UTILS is showing up a bazillion times? diff --git a/share/man/man5/src.conf.5 b/share/man/man5/src.conf.5 index 17afca2..54b63db 100644 --- a/share/man/man5/src.conf.5 +++ b/share/man/man5/src.conf.5 @@ -1,7 +1,7 @@ .\" DO NOT EDIT-- this file is automatically generated. -.\" from FreeBSD: head/tools/build/options/makeman 236279 2012-05-30 02:37:20Z gjb +.\" from FreeBSD$ .\" $FreeBSD$ -.Dd February 15, 2013 +.Dd April 26, 2013 .Dt SRC.CONF 5 .Os .Sh NAME @@ -78,57 +78,117 @@ The following list provides a name and short description for variables that can be used for source builds. .Bl -tag -width indent .It Va WITHOUT_ACCT -.\" from FreeBSD: head/tools/build/options/WITHOUT_ACCT 223201 2011-06-17 20:47:44Z ed +.\" $FreeBSD$ Set to not build process accounting tools such as .Xr accton 8 and .Xr sa 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_ACPI -.\" from FreeBSD: head/tools/build/options/WITHOUT_ACPI 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr acpiconf 8 , .Xr acpidump 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_AMD -.\" from FreeBSD: head/tools/build/options/WITHOUT_AMD 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr amd 8 , and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_APM -.\" from FreeBSD: head/tools/build/options/WITHOUT_APM 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr apm 8 , .Xr apmd 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_ARM_EABI -.\" from FreeBSD: head/tools/build/options/WITH_ARM_EABI 245539 2013-01-17 05:56:28Z andrew +.\" $FreeBSD$ Set the ARM ABI to EABI. .It Va WITHOUT_ASSERT_DEBUG -.\" from FreeBSD: head/tools/build/options/WITHOUT_ASSERT_DEBUG 162215 2006-09-11 13:55:27Z ru +.\" $FreeBSD$ Set to compile programs and libraries without the .Xr assert 3 checks. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_AT -.\" from FreeBSD: head/tools/build/options/WITHOUT_AT 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr at 1 and related utilities. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_ATF -.\" from FreeBSD: head/tools/build/options/WITHOUT_ATF 241823 2012-10-22 01:18:41Z marcel +.\" $FreeBSD$ Set to not build programs and libraries related to the ATF testing framework. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_ATM -.\" from FreeBSD: head/tools/build/options/WITHOUT_ATM 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build programs and libraries related to ATM networking. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_AUDIT -.\" from FreeBSD: head/tools/build/options/WITHOUT_AUDIT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build audit support into system programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_AUTHPF -.\" from FreeBSD: head/tools/build/options/WITHOUT_AUTHPF 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr authpf 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_BIND -.\" from FreeBSD: head/tools/build/options/WITHOUT_BIND 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Setting this variable will prevent any part of BIND from being built. When set, it also enforces the following options: .Pp @@ -149,31 +209,49 @@ When set, it also enforces the following options: .Va WITHOUT_BIND_UTILS .El .It Va WITHOUT_BIND_DNSSEC -.\" from FreeBSD: head/tools/build/options/WITHOUT_BIND_DNSSEC 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to avoid building or installing the DNSSEC related binaries, .Xr dnssec-keygen 8 and .Xr dnssec-signzone 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_BIND_ETC -.\" from FreeBSD: head/tools/build/options/WITHOUT_BIND_ETC 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to avoid installing the default files to .Pa /var/named/etc/namedb . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_BIND_IDN -.\" from FreeBSD: head/tools/build/options/WITH_BIND_IDN 193280 2009-06-01 21:58:59Z dougb +.\" $FreeBSD$ Set to enable IDN support for dig, host, and nslookup. This requires ports/dns/idnkit to be installed in /usr/local. .It Va WITH_BIND_LARGE_FILE -.\" from FreeBSD: head/tools/build/options/WITH_BIND_LARGE_FILE 193280 2009-06-01 21:58:59Z dougb +.\" $FreeBSD$ Set to enable 64-bit file support. .It Va WITH_BIND_LIBS -.\" from FreeBSD: head/tools/build/options/WITH_BIND_LIBS 193280 2009-06-01 21:58:59Z dougb +.\" $FreeBSD$ Set to install BIND libraries and include files. .It Va WITHOUT_BIND_LIBS_LWRES -.\" from FreeBSD: head/tools/build/options/WITHOUT_BIND_LIBS_LWRES 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to avoid installing the lightweight resolver library in .Pa /usr/lib . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_BIND_MTREE -.\" from FreeBSD: head/tools/build/options/WITHOUT_BIND_MTREE 157717 2006-04-13 10:37:29Z ru +.\" $FreeBSD$ Set to avoid running .Xr mtree 8 to create the chroot directory structure under @@ -186,9 +264,11 @@ When set, it also enforces the following options: .Bl -item -compact .It .Va WITHOUT_BIND_ETC +.It +.Va WITHOUT_BIND_UTILS .El .It Va WITHOUT_BIND_NAMED -.\" from FreeBSD: head/tools/build/options/WITHOUT_BIND_NAMED 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to avoid building or installing .Xr named 8 , .Xr named.reload 8 , @@ -197,11 +277,17 @@ Set to avoid building or installing .Xr rndc 8 , and .Xr rndc-confgen 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_BIND_SIGCHASE -.\" from FreeBSD: head/tools/build/options/WITH_BIND_SIGCHASE 193280 2009-06-01 21:58:59Z dougb +.\" $FreeBSD$ Set to enable DNSSEC validation support for dig, host, and nslookup. .It Va WITHOUT_BIND_UTILS -.\" from FreeBSD: head/tools/build/options/WITHOUT_BIND_UTILS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to avoid building or installing the BIND userland utilities, .Xr dig 1 , .Xr host 1 , @@ -209,22 +295,34 @@ Set to avoid building or installing the BIND userland utilities, and .Xr nsupdate 8 . .It Va WITH_BIND_XML -.\" from FreeBSD: head/tools/build/options/WITH_BIND_XML 193280 2009-06-01 21:58:59Z dougb +.\" $FreeBSD$ Set to enable the http statistics interface for named. This requires ports/textproc/libxml2 to be installed in /usr/local. .It Va WITHOUT_BINUTILS -.\" from FreeBSD: head/tools/build/options/WITHOUT_BINUTILS 235342 2012-05-12 16:12:36Z gjb +.\" $FreeBSD$ Set to not install binutils (as, c++-filt, gconv, gnu-ar, gnu-randlib, ld, nm, objcopy, objdump, readelf, size and strip). .Bf -symbolic The option does not generally work for build targets, unless some alternative toolchain is enabled. .Ef +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_BLUETOOTH -.\" from FreeBSD: head/tools/build/options/WITHOUT_BLUETOOTH 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build Bluetooth related kernel modules, programs and libraries. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_BMAKE -.\" from FreeBSD: head/tools/build/options/WITH_BMAKE 241279 2012-10-06 19:19:21Z marcel +.\" $FreeBSD$ Build and install the portable BSD make (bmake) as .Xr make 1 instead of the traditional FreeBSD make. @@ -233,28 +331,46 @@ It allows developers to switch to bmake in order to work out any remaining kinks or issues. This option will be removed in due time. .It Va WITHOUT_BOOT -.\" from FreeBSD: head/tools/build/options/WITHOUT_BOOT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build the boot blocks and loader. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_BSDCONFIG -.\" from FreeBSD: head/tools/build/options/WITH_BSDCONFIG 238448 2012-07-14 10:17:47Z zeising +.\" $FreeBSD$ Set to install bsdconfig(8), a BSD-licensed configuration/management utility. .It Va WITHOUT_BSD_CPIO -.\" from FreeBSD: head/tools/build/options/WITHOUT_BSD_CPIO 179813 2008-06-16 05:48:15Z dougb +.\" $FreeBSD$ Set to not build the BSD licensed version of cpio based on .Xr libarchive 3 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_BSD_GREP -.\" from FreeBSD: head/tools/build/options/WITH_BSD_GREP 222273 2011-05-25 01:04:12Z obrien +.\" $FreeBSD$ Install BSD-licensed grep as '[ef]grep' instead of GNU grep. .It Va WITH_BSD_PATCH -.\" from FreeBSD: head/tools/build/options/WITH_BSD_PATCH 246074 2013-01-29 17:03:18Z gabor +.\" $FreeBSD$ Install BSD-licensed patch as 'patch' instead of GNU patch. .It Va WITHOUT_BSNMP -.\" from FreeBSD: head/tools/build/options/WITHOUT_BSNMP 183306 2008-09-23 16:15:42Z sam +.\" $FreeBSD$ Set to not build or install .Xr bsnmpd 1 and related libraries and data files. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_BZIP2 -.\" from FreeBSD: head/tools/build/options/WITHOUT_BZIP2 174550 2007-12-12 16:43:17Z ru +.\" $FreeBSD$ Set to not build contributed bzip2 software as a part of the base system. .Bf -symbolic The option has no effect yet. @@ -263,31 +379,53 @@ When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_BZIP2_SUPPORT .El .It Va WITHOUT_BZIP2_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_BZIP2_SUPPORT 166255 2007-01-26 10:19:08Z delphij +.\" $FreeBSD$ Set to build some programs without optional bzip2 support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_CALENDAR -.\" from FreeBSD: head/tools/build/options/WITHOUT_CALENDAR 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr calendar 1 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_CAPSICUM -.\" from FreeBSD: head/tools/build/options/WITHOUT_CAPSICUM 229319 2012-01-02 21:57:58Z rwatson +.\" $FreeBSD$ Set to not build Capsicum support into system programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_CDDL -.\" from FreeBSD: head/tools/build/options/WITHOUT_CDDL 163861 2006-11-01 09:02:11Z jb +.\" $FreeBSD$ Set to not build code licensed under Sun's CDDL. When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_CTF .It .Va WITHOUT_ZFS .El .It Va WITHOUT_CLANG -.\" from FreeBSD: head/tools/build/options/WITHOUT_CLANG 208971 2010-06-10 06:20:26Z ed +.\" $FreeBSD$ Set to not build the Clang C/C++ compiler. .Pp It is a default setting on @@ -296,31 +434,45 @@ When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_CLANG_EXTRAS .It .Va WITHOUT_CLANG_FULL .It .Va WITHOUT_CLANG_IS_CC .El +.It Va WITH_CLANG +.\" $FreeBSD$ +Set to build the Clang C/C++ compiler. +.Pp +It is a default setting on +amd64/amd64, arm/arm, arm/armv6, i386/i386, pc98/i386, powerpc/powerpc and powerpc/powerpc64. .It Va WITH_CLANG_EXTRAS -.\" from FreeBSD: head/tools/build/options/WITH_CLANG_EXTRAS 231057 2012-02-05 23:56:22Z dim +.\" $FreeBSD$ Set to build additional clang and llvm tools, such as bugpoint. .It Va WITHOUT_CLANG_FULL -.\" from FreeBSD: head/tools/build/options/WITHOUT_CLANG_FULL 246259 2013-02-02 22:28:29Z dim +.\" $FreeBSD$ Set to avoid building the ARCMigrate, Rewriter and StaticAnalyzer components of the Clang C/C++ compiler. .Pp It is a default setting on arm/arm, arm/armeb, arm/armv6, arm/armv6eb, ia64/ia64, mips/mipsel, mips/mips, mips/mips64el, mips/mips64, mips/mipsn32 and sparc64/sparc64. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_CLANG_FULL -.\" from FreeBSD: head/tools/build/options/WITH_CLANG_FULL 246259 2013-02-02 22:28:29Z dim +.\" $FreeBSD$ Set to build the ARCMigrate, Rewriter and StaticAnalyzer components of the Clang C/C++ compiler. .Pp It is a default setting on amd64/amd64, i386/i386, pc98/i386, powerpc/powerpc and powerpc/powerpc64. .It Va WITHOUT_CLANG_IS_CC -.\" from FreeBSD: head/tools/build/options/WITHOUT_CLANG_IS_CC 242629 2012-11-05 21:53:23Z brooks +.\" $FreeBSD$ Set to install the GCC compiler as .Pa /usr/bin/cc , .Pa /usr/bin/c++ @@ -328,9 +480,15 @@ and .Pa /usr/bin/cpp . .Pp It is a default setting on -arm/arm, arm/armeb, arm/armv6, arm/armv6eb, ia64/ia64, mips/mipsel, mips/mips, mips/mips64el, mips/mips64, mips/mipsn32, powerpc/powerpc, powerpc/powerpc64 and sparc64/sparc64. +arm/armeb, arm/armv6eb, ia64/ia64, mips/mipsel, mips/mips, mips/mips64el, mips/mips64, mips/mipsn32, powerpc/powerpc, powerpc/powerpc64 and sparc64/sparc64. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_CLANG_IS_CC -.\" from FreeBSD: head/tools/build/options/WITH_CLANG_IS_CC 235342 2012-05-12 16:12:36Z gjb +.\" $FreeBSD$ Set to install the Clang C/C++ compiler as .Pa /usr/bin/cc , .Pa /usr/bin/c++ @@ -338,18 +496,26 @@ and .Pa /usr/bin/cpp . .Pp It is a default setting on -amd64/amd64, i386/i386 and pc98/i386. +amd64/amd64, arm/arm, arm/armv6, i386/i386 and pc98/i386. .It Va WITHOUT_CPP -.\" from FreeBSD: head/tools/build/options/WITHOUT_CPP 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr cpp 1 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_CRYPT -.\" from FreeBSD: head/tools/build/options/WITHOUT_CRYPT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build any crypto code. When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_KERBEROS .It .Va WITHOUT_KERBEROS_SUPPORT @@ -368,20 +534,32 @@ When set, the following options are also in effect: is set explicitly) .El .It Va WITH_CTF -.\" from FreeBSD: head/tools/build/options/WITH_CTF 228159 2011-11-30 18:22:44Z fjoe +.\" $FreeBSD$ Set to compile with CTF (Compact C Type Format) data. CTF data encapsulates a reduced form of debugging information similar to DWARF and the venerable stabs and is required for DTrace. .It Va WITHOUT_CTM -.\" from FreeBSD: head/tools/build/options/WITHOUT_CTM 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr ctm 1 and related utilities. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_CVS -.\" from FreeBSD: head/tools/build/options/WITHOUT_CVS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build CVS. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_CXX -.\" from FreeBSD: head/tools/build/options/WITHOUT_CXX 220402 2011-04-06 20:19:07Z uqs +.\" $FreeBSD$ Set to not build .Xr g++ 1 and related libraries. @@ -393,6 +571,8 @@ When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_CLANG .It .Va WITHOUT_CLANG_EXTRAS @@ -404,68 +584,153 @@ When set, it also enforces the following options: .Va WITHOUT_GROFF .El .It Va WITHOUT_DICT -.\" from FreeBSD: head/tools/build/options/WITHOUT_DICT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build the Webster dictionary files. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_DYNAMICROOT -.\" from FreeBSD: head/tools/build/options/WITHOUT_DYNAMICROOT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set this if you do not want to link .Pa /bin and .Pa /sbin dynamically. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_ED_CRYPTO -.\" from FreeBSD: head/tools/build/options/WITHOUT_ED_CRYPTO 235660 2012-05-19 20:05:27Z marcel +.\" $FreeBSD$ Set to build .Xr ed 1 without support for encryption/decryption. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_EXAMPLES -.\" from FreeBSD: head/tools/build/options/WITHOUT_EXAMPLES 156938 2006-03-21 09:06:24Z ru +.\" $FreeBSD$ Set to avoid installing examples to .Pa /usr/share/examples/ . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_FDT -.\" from FreeBSD: head/tools/build/options/WITHOUT_FDT 221539 2011-05-06 19:10:27Z ru +.\" $FreeBSD$ Set to not build Flattened Device Tree support as part of the base system. This includes the device tree compiler (dtc) and libfdt support library. .Pp It is a default setting on amd64/amd64, i386/i386, ia64/ia64, pc98/i386 and sparc64/sparc64. -.It Va WITHOUT_FLOPPY -.\" from FreeBSD: head/tools/build/options/WITHOUT_FLOPPY 221540 2011-05-06 19:13:03Z ru +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El +.It Va WITH_FDT +.\" $FreeBSD$ +Set to build Flattened Device Tree support as part of the base system. +This includes the device tree compiler (dtc) and libfdt support library. +.Pp +It is a default setting on +arm/arm, arm/armeb, arm/armv6, arm/armv6eb, mips/mipsel, mips/mips, mips/mips64el, mips/mips64, mips/mipsn32, powerpc/powerpc and powerpc/powerpc64. +.It Va WITHOUT_FLOPPY +.\" $FreeBSD$ Set to not build or install programs for operating floppy disk driver. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_FORTH -.\" from FreeBSD: head/tools/build/options/WITHOUT_FORTH 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to build bootloaders without Forth support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_FP_LIBC -.\" from FreeBSD: head/tools/build/options/WITHOUT_FP_LIBC 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to build .Nm libc without floating-point support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_FREEBSD_UPDATE -.\" from FreeBSD: head/tools/build/options/WITHOUT_FREEBSD_UPDATE 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr freebsd-update 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_GAMES -.\" from FreeBSD: head/tools/build/options/WITHOUT_GAMES 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build games. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_GCC -.\" from FreeBSD: head/tools/build/options/WITHOUT_GCC 222090 2011-05-19 05:13:25Z imp +.\" $FreeBSD$ Set to not install gcc and g++. .Bf -symbolic The option does not generally work for build targets, unless some alternative toolchain is enabled. .Ef +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_GCOV -.\" from FreeBSD: head/tools/build/options/WITHOUT_GCOV 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build the .Xr gcov 1 tool. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_GDB -.\" from FreeBSD: head/tools/build/options/WITHOUT_GDB 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr gdb 1 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_GNU -.\" from FreeBSD: head/tools/build/options/WITHOUT_GNU 174550 2007-12-12 16:43:17Z ru +.\" $FreeBSD$ Set to not build contributed GNU software as a part of the base system. This option can be useful if the system built must not contain any code covered by the GNU Public License due to legal reasons. @@ -476,88 +741,147 @@ When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_GNU_SUPPORT .El .It Va WITHOUT_GNU_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_GNU_SUPPORT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to build some programs without optional GNU support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_GPIB -.\" from FreeBSD: head/tools/build/options/WITHOUT_GPIB 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build GPIB bus support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_GPIO -.\" from FreeBSD: head/tools/build/options/WITHOUT_GPIO 228081 2011-11-28 17:54:34Z dim +.\" $FreeBSD$ Set to not build .Xr gpioctl 8 as part of the base system. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_GPL_DTC -.\" from FreeBSD: head/tools/build/options/WITH_GPL_DTC 246262 2013-02-02 22:42:46Z dim +.\" $FreeBSD$ Set to build the GPL'd version of the device tree compiler from elinux.org, instead of the BSD licensed one. .It Va WITHOUT_GROFF -.\" from FreeBSD: head/tools/build/options/WITHOUT_GROFF 218941 2011-02-22 08:13:49Z uqs +.\" $FreeBSD$ Set to not build .Xr groff 1 and .Xr vgrind 1 . You should consider installing the textproc/groff port to not break .Xr man 1 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_GSSAPI -.\" from FreeBSD: head/tools/build/options/WITHOUT_GSSAPI 174548 2007-12-12 16:39:32Z ru +.\" $FreeBSD$ Set to not build libgssapi. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_HESIOD -.\" from FreeBSD: head/tools/build/options/WITH_HESIOD 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to build Hesiod support. .It Va WITHOUT_HTML -.\" from FreeBSD: head/tools/build/options/WITHOUT_HTML 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build HTML docs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_ICONV -.\" from FreeBSD: head/tools/build/options/WITH_ICONV 219020 2011-02-25 00:10:26Z gabor +.\" $FreeBSD$ Set to build iconv as part of libc. -.It Va WITH_IDEA -.\" from FreeBSD: head/tools/build/options/WITH_IDEA 156932 2006-03-21 07:50:50Z ru -Set to build the IDEA encryption code. -This code is patented in the USA and many European countries. -It is -.Em "YOUR RESPONSIBILITY" -to determine if you can legally use IDEA. .It Va WITHOUT_INET -.\" from FreeBSD: head/tools/build/options/WITHOUT_INET 221266 2011-04-30 17:58:28Z bz +.\" $FreeBSD$ Set to not build programs and libraries related to IPv4 networking. When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_INET_SUPPORT .El .It Va WITHOUT_INET6 -.\" from FreeBSD: head/tools/build/options/WITHOUT_INET6 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build programs and libraries related to IPv6 networking. When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_INET6_SUPPORT .El .It Va WITHOUT_INET6_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_INET6_SUPPORT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to build libraries, programs, and kernel modules without IPv6 support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_INET_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_INET_SUPPORT 221266 2011-04-30 17:58:28Z bz +.\" $FreeBSD$ Set to build libraries, programs, and kernel modules without IPv4 support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_INFO -.\" from FreeBSD: head/tools/build/options/WITHOUT_INFO 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not make or install .Xr info 5 files. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_INSTALLLIB -.\" from FreeBSD: head/tools/build/options/WITHOUT_INSTALLLIB 174497 2007-12-09 21:56:21Z dougb +.\" $FreeBSD$ Set this if you do not want to install optional libraries. For example when creating a .Xr nanobsd 8 image. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_INSTALL_AS_USER -.\" from FreeBSD: head/tools/build/options/WITH_INSTALL_AS_USER 238021 2012-07-02 20:24:01Z marcel +.\" $FreeBSD$ Set to make install targets succeed for non-root users by installing files with owner and group attributes set to that of the user running the @@ -567,40 +891,74 @@ The user still has to set the .Va DESTDIR variable to point to a directory where the user has write permissions. .It Va WITHOUT_IPFILTER -.\" from FreeBSD: head/tools/build/options/WITHOUT_IPFILTER 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build IP Filter package. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_IPFW -.\" from FreeBSD: head/tools/build/options/WITHOUT_IPFW 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build IPFW tools. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_IPX -.\" from FreeBSD: head/tools/build/options/WITHOUT_IPX 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build programs and libraries related to IPX networking. When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_IPX_SUPPORT .El .It Va WITHOUT_IPX_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_IPX_SUPPORT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to build some programs without IPX support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_JAIL -.\" from FreeBSD: head/tools/build/options/WITHOUT_JAIL 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build tools for the support of jails; e.g. .Xr jail 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_KDUMP -.\" from FreeBSD: head/tools/build/options/WITHOUT_KDUMP 240690 2012-09-19 11:38:37Z zeising +.\" $FreeBSD$ Set to not build .Xr kdump 1 and .Xr truss 1 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_KERBEROS -.\" from FreeBSD: head/tools/build/options/WITHOUT_KERBEROS 174549 2007-12-12 16:42:03Z ru +.\" $FreeBSD$ Set this if you do not want to build Kerberos 5 (KTH Heimdal). When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_KERBEROS_SUPPORT .El .Pp @@ -613,7 +971,7 @@ When set, the following options are also in effect: is set explicitly) .El .It Va WITHOUT_KERBEROS_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_KERBEROS_SUPPORT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to build some programs without Kerberos support, like .Xr cvs 1 , .Xr ssh 1 , @@ -621,14 +979,26 @@ Set to build some programs without Kerberos support, like .Xr sshd 8 , and .Xr telnetd 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_KERNEL_SYMBOLS -.\" from FreeBSD: head/tools/build/options/WITHOUT_KERNEL_SYMBOLS 222189 2011-05-22 18:23:17Z imp +.\" $FreeBSD$ Set to not install kernel symbol files. .Bf -symbolic This option is recommended for those people who have small root partitions. .Ef +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_KVM -.\" from FreeBSD: head/tools/build/options/WITHOUT_KVM 174550 2007-12-12 16:43:17Z ru +.\" $FreeBSD$ Set to not build the .Nm libkvm library as a part of the base system. @@ -639,15 +1009,23 @@ When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_KVM_SUPPORT .El .It Va WITHOUT_KVM_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_KVM_SUPPORT 170644 2007-06-13 02:08:04Z sepotvin +.\" $FreeBSD$ Set to build some programs without optional .Nm libkvm support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_LDNS -.\" from FreeBSD: head/tools/build/options/WITHOUT_LDNS 246827 2013-02-15 13:44:18Z des +.\" $FreeBSD$ Setting this variable will prevent LDNS from being built. When set, it also enforces the following options: .Pp @@ -656,7 +1034,7 @@ When set, it also enforces the following options: .Va WITHOUT_LDNS_UTILS .El .It Va WITH_LDNS_UTILS -.\" from FreeBSD: head/tools/build/options/WITH_LDNS_UTILS 246830 2013-02-15 13:57:51Z des +.\" $FreeBSD$ Setting this variable will enable the LDNS-based versions of .Xr dig 1 and @@ -665,23 +1043,38 @@ When set, the following options are also in effect: .Pp .Bl -inset -compact .It Va WITHOUT_BIND_UTILS +(unless +.Va WITH_BIND_UTILS +is set explicitly) .El .It Va WITHOUT_LEGACY_CONSOLE -.\" from FreeBSD: head/tools/build/options/WITHOUT_LEGACY_CONSOLE 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build programs that support a legacy PC console; e.g. .Xr kbdcontrol 8 and .Xr vidcontrol 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_LIB32 -.\" from FreeBSD: head/tools/build/options/WITHOUT_LIB32 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ On amd64, set to not build 32-bit library set and a .Nm ld-elf32.so.1 runtime linker. -.It Va WITHOUT_LIBCPLUSPLUS -.\" from FreeBSD: head/tools/build/options/WITHOUT_LIBCPLUSPLUS 246262 2013-02-02 22:42:46Z dim -Set to avoid building libcxxrt and libc++. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El +.It Va WITH_LIBCPLUSPLUS +.\" $FreeBSD$ +Set to build libcxxrt and libc++. .It Va WITHOUT_LIBPTHREAD -.\" from FreeBSD: head/tools/build/options/WITHOUT_LIBPTHREAD 188848 2009-02-20 11:09:55Z mtm +.\" $FreeBSD$ Set to not build the .Nm libpthread providing library, @@ -709,7 +1102,7 @@ When set, it also enforces the following options: .Va WITHOUT_LIBTHR .El .It Va WITHOUT_LIBTHR -.\" from FreeBSD: head/tools/build/options/WITHOUT_LIBTHR 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build the .Nm libthr (1:1 threading) @@ -735,48 +1128,93 @@ When set, it also enforces the following options: .Va WITHOUT_BIND_UTILS .El .It Va WITHOUT_LOCALES -.\" from FreeBSD: head/tools/build/options/WITHOUT_LOCALES 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build localization files; see .Xr locale 1 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_LOCATE -.\" from FreeBSD: head/tools/build/options/WITHOUT_LOCATE 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr locate 1 and related programs. -.It Va WITHOUT_LPR -.\" from FreeBSD: head/tools/build/options/WITHOUT_LPR 156932 2006-03-21 07:50:50Z ru -Set to not build -.Xr lpr 1 -and related programs. -.It Va WITHOUT_LS_COLORS -.\" from FreeBSD: head/tools/build/options/WITHOUT_LS_COLORS 235660 2012-05-19 20:05:27Z marcel -Set to build -.Xr ls 1 -without support for colors to distinguish file types. -.It Va WITHOUT_MAIL -.\" from FreeBSD: head/tools/build/options/WITHOUT_MAIL 183242 2008-09-21 22:02:26Z sam -Set to not build any mail support (MUA or MTA). When set, it also enforces the following options: .Pp .Bl -item -compact .It -.Va WITHOUT_MAILWRAPPER -.It +.Va WITHOUT_BIND_UTILS +.El +.It Va WITHOUT_LPR +.\" $FreeBSD$ +Set to not build +.Xr lpr 1 +and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El +.It Va WITHOUT_LS_COLORS +.\" $FreeBSD$ +Set to build +.Xr ls 1 +without support for colors to distinguish file types. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El +.It Va WITHOUT_MAIL +.\" $FreeBSD$ +Set to not build any mail support (MUA or MTA). +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.It +.Va WITHOUT_MAILWRAPPER +.It .Va WITHOUT_SENDMAIL .El .It Va WITHOUT_MAILWRAPPER -.\" from FreeBSD: head/tools/build/options/WITHOUT_MAILWRAPPER 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build the .Xr mailwrapper 8 MTA selector. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_MAKE -.\" from FreeBSD: head/tools/build/options/WITHOUT_MAKE 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not install .Xr make 1 and related support files. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_MAN -.\" from FreeBSD: head/tools/build/options/WITHOUT_MAN 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build manual pages. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El +.Pp When set, the following options are also in effect: .Pp .Bl -inset -compact @@ -786,7 +1224,7 @@ When set, the following options are also in effect: is set explicitly) .El .It Va WITHOUT_MAN_UTILS -.\" from FreeBSD: head/tools/build/options/WITHOUT_MAN_UTILS 208322 2010-05-20 00:07:21Z jkim +.\" $FreeBSD$ Set to not build utilities for manual pages, .Xr apropos 1 , .Xr catman 1 , @@ -795,20 +1233,38 @@ Set to not build utilities for manual pages, .Xr whatis 1 , .Xr manctl 8 , and related support files. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_NAND -.\" from FreeBSD: head/tools/build/options/WITH_NAND 235537 2012-05-17 10:11:18Z gber +.\" $FreeBSD$ Set to build the NAND Flash components. .It Va WITHOUT_NDIS -.\" from FreeBSD: head/tools/build/options/WITHOUT_NDIS 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build programs and libraries related to NDIS emulation support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_NETCAT -.\" from FreeBSD: head/tools/build/options/WITHOUT_NETCAT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr nc 1 utility. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_NETGRAPH -.\" from FreeBSD: head/tools/build/options/WITHOUT_NETGRAPH 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build applications to support .Xr netgraph 4 . When set, it also enforces the following options: @@ -817,15 +1273,23 @@ When set, it also enforces the following options: .It .Va WITHOUT_ATM .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_BLUETOOTH .It .Va WITHOUT_NETGRAPH_SUPPORT .El .It Va WITHOUT_NETGRAPH_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_NETGRAPH_SUPPORT 183305 2008-09-23 16:11:15Z sam +.\" $FreeBSD$ Set to build libraries, programs, and kernel modules without netgraph support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_NIS -.\" from FreeBSD: head/tools/build/options/WITHOUT_NIS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr NIS 8 support and related programs. @@ -834,15 +1298,33 @@ If set, you might need to adopt your and remove .Sq nis entries. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_NLS -.\" from FreeBSD: head/tools/build/options/WITHOUT_NLS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build NLS catalogs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_NLS_CATALOGS -.\" from FreeBSD: head/tools/build/options/WITHOUT_NLS_CATALOGS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build NLS catalog support for .Xr csh 1 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_NMTREE -.\" from FreeBSD: head/tools/build/options/WITH_NMTREE 245435 2013-01-14 20:38:32Z brooks +.\" $FreeBSD$ Set to install .Xr nmtree 8 as @@ -852,28 +1334,46 @@ By default is installed as .Xr mtree 8 . .It Va WITHOUT_NS_CACHING -.\" from FreeBSD: head/tools/build/options/WITHOUT_NS_CACHING 172803 2007-10-19 14:01:25Z ru +.\" $FreeBSD$ Set to disable name caching in the .Pa nsswitch subsystem. The generic caching daemon, .Xr nscd 8 , will not be built either if this option is set. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_NTP -.\" from FreeBSD: head/tools/build/options/WITHOUT_NTP 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr ntpd 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_OFED -.\" from FreeBSD: head/tools/build/options/WITH_OFED 228081 2011-11-28 17:54:34Z dim +.\" $FreeBSD$ Set to build the .Dq "OpenFabrics Enterprise Distribution" Infiniband software stack. .It Va WITHOUT_OPENSSH -.\" from FreeBSD: head/tools/build/options/WITHOUT_OPENSSH 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build OpenSSH. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_OPENSSH_NONE_CIPHER -.\" from FreeBSD: head/tools/build/options/WITH_OPENSSH_NONE_CIPHER 245527 2013-01-17 01:51:04Z bz +.\" $FreeBSD$ Set to include the "None" cipher support in OpenSSH and its libraries. Additional adjustments may need to be done to system configuration files, such as @@ -883,12 +1383,14 @@ Please see .Pa /usr/src/crypto/openssh/README.hpn for full details. .It Va WITHOUT_OPENSSL -.\" from FreeBSD: head/tools/build/options/WITHOUT_OPENSSL 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build OpenSSL. When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_KERBEROS .It .Va WITHOUT_KERBEROS_SUPPORT @@ -905,7 +1407,7 @@ When set, the following options are also in effect: is set explicitly) .El .It Va WITHOUT_PAM -.\" from FreeBSD: head/tools/build/options/WITHOUT_PAM 174550 2007-12-12 16:43:17Z ru +.\" $FreeBSD$ Set to not build PAM library and modules. .Bf -symbolic This option is deprecated and does nothing. @@ -914,63 +1416,121 @@ When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_PAM_SUPPORT .El .It Va WITHOUT_PAM_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_PAM_SUPPORT 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to build some programs without PAM support, particularly .Xr ftpd 8 and .Xr ppp 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_PC_SYSINSTALL -.\" from FreeBSD: head/tools/build/options/WITHOUT_PC_SYSINSTALL 245606 2013-01-18 15:57:09Z eadler +.\" $FreeBSD$ Set to not build .Xr pc-sysinstall 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_PF -.\" from FreeBSD: head/tools/build/options/WITHOUT_PF 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build PF firewall package. When set, it also enforces the following options: .Pp .Bl -item -compact .It .Va WITHOUT_AUTHPF +.It +.Va WITHOUT_BIND_UTILS .El .It Va WITHOUT_PKGBOOTSTRAP -.\" from FreeBSD: head/tools/build/options/WITHOUT_PKGBOOTSTRAP 238023 2012-07-02 20:26:11Z marcel +.\" $FreeBSD$ Set to not build .Xr pkg 1 bootstrap tool +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_PKGTOOLS -.\" from FreeBSD: head/tools/build/options/WITHOUT_PKGTOOLS 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr pkg_add 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_PMC -.\" from FreeBSD: head/tools/build/options/WITHOUT_PMC 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr pmccontrol 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_PORTSNAP -.\" from FreeBSD: head/tools/build/options/WITHOUT_PORTSNAP 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build or install .Xr portsnap 8 and related files. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_PPP -.\" from FreeBSD: head/tools/build/options/WITHOUT_PPP 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr ppp 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_PROFILE -.\" from FreeBSD: head/tools/build/options/WITHOUT_PROFILE 228196 2011-12-02 09:09:54Z fjoe +.\" $FreeBSD$ Set to avoid compiling profiled libraries. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_QUOTAS -.\" from FreeBSD: head/tools/build/options/WITHOUT_QUOTAS 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr quota 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_RCMDS -.\" from FreeBSD: head/tools/build/options/WITHOUT_RCMDS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Disable building of the .Bx r-commands. @@ -978,98 +1538,192 @@ This includes .Xr rlogin 1 , .Xr rsh 1 , etc. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_RCS -.\" from FreeBSD: head/tools/build/options/WITHOUT_RCS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr rcs 1 and related utilities. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_RESCUE -.\" from FreeBSD: head/tools/build/options/WITHOUT_RESCUE 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr rescue 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_ROUTED -.\" from FreeBSD: head/tools/build/options/WITHOUT_ROUTED 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr routed 8 utility. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_SENDMAIL -.\" from FreeBSD: head/tools/build/options/WITHOUT_SENDMAIL 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr sendmail 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_SETUID_LOGIN -.\" from FreeBSD: head/tools/build/options/WITHOUT_SETUID_LOGIN 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set this to disable the installation of .Xr login 1 as a set-user-ID root program. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_SHAREDOCS -.\" from FreeBSD: head/tools/build/options/WITHOUT_SHAREDOCS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build the .Bx 4.4 legacy docs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITH_SHARED_TOOLCHAIN -.\" from FreeBSD: head/tools/build/options/WITH_SHARED_TOOLCHAIN 235342 2012-05-12 16:12:36Z gjb +.\" $FreeBSD$ Set to build the toolchain binaries shared. The set includes .Xr cc 1 , .Xr make 1 and necessary utilities like assembler, linker and library archive manager. .It Va WITHOUT_SOURCELESS -.\" from FreeBSD: head/tools/build/options/WITHOUT_SOURCELESS 230972 2012-02-04 00:54:43Z rmh +.\" $FreeBSD$ Set to not build kernel modules that include sourceless code (either microcode or native code for host CPU). When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_SOURCELESS_HOST .It .Va WITHOUT_SOURCELESS_UCODE .El .It Va WITHOUT_SOURCELESS_HOST -.\" from FreeBSD: head/tools/build/options/WITHOUT_SOURCELESS_HOST 230972 2012-02-04 00:54:43Z rmh +.\" $FreeBSD$ Set to not build kernel modules that include sourceless native code for host CPU. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_SOURCELESS_UCODE -.\" from FreeBSD: head/tools/build/options/WITHOUT_SOURCELESS_UCODE 230972 2012-02-04 00:54:43Z rmh +.\" $FreeBSD$ Set to not build kernel modules that include sourceless microcode. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_SSP -.\" from FreeBSD: head/tools/build/options/WITHOUT_SSP 180012 2008-06-25 21:33:28Z ru +.\" $FreeBSD$ Set to not build world with propolice stack smashing protection. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_SYMVER -.\" from FreeBSD: head/tools/build/options/WITHOUT_SYMVER 169649 2007-05-17 05:03:24Z deischen +.\" $FreeBSD$ Set to disable symbol versioning when building shared libraries. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_SYSCONS -.\" from FreeBSD: head/tools/build/options/WITHOUT_SYSCONS 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build .Xr syscons 4 support files such as keyboard maps, fonts, and screen output maps. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_SYSINSTALL -.\" from FreeBSD: head/tools/build/options/WITHOUT_SYSINSTALL 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr sysinstall 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_TCSH -.\" from FreeBSD: head/tools/build/options/WITHOUT_TCSH 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build and install .Pa /bin/csh (which is .Xr tcsh 1 ) . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_TELNET -.\" from FreeBSD: head/tools/build/options/WITHOUT_TELNET 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build .Xr telnet 8 and related programs. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_TEXTPROC -.\" from FreeBSD: head/tools/build/options/WITHOUT_TEXTPROC 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build programs used for text processing. When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_GROFF .El .It Va WITHOUT_TOOLCHAIN -.\" from FreeBSD: head/tools/build/options/WITHOUT_TOOLCHAIN 174550 2007-12-12 16:43:17Z ru +.\" $FreeBSD$ Set to not install programs used for program development, compilers, debuggers etc. @@ -1080,6 +1734,8 @@ When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_BINUTILS .It .Va WITHOUT_CLANG @@ -1095,10 +1751,16 @@ When set, it also enforces the following options: .Va WITHOUT_GDB .El .It Va WITHOUT_USB -.\" from FreeBSD: head/tools/build/options/WITHOUT_USB 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Set to not build USB-related programs and libraries. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_UTMPX -.\" from FreeBSD: head/tools/build/options/WITHOUT_UTMPX 231530 2012-02-11 20:28:42Z ed +.\" $FreeBSD$ Set to not build user accounting tools such as .Xr last 1 , .Xr users 1 , @@ -1107,8 +1769,14 @@ Set to not build user accounting tools such as .Xr lastlogin 8 and .Xr utx 8 . +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_WIRELESS -.\" from FreeBSD: head/tools/build/options/WITHOUT_WIRELESS 183242 2008-09-21 22:02:26Z sam +.\" $FreeBSD$ Set to not build programs used for 802.11 wireless networks; especially .Xr wpa_supplicant 8 and @@ -1117,25 +1785,51 @@ When set, it also enforces the following options: .Pp .Bl -item -compact .It +.Va WITHOUT_BIND_UTILS +.It .Va WITHOUT_WIRELESS_SUPPORT .El .It Va WITHOUT_WIRELESS_SUPPORT -.\" from FreeBSD: head/tools/build/options/WITHOUT_WIRELESS_SUPPORT 183305 2008-09-23 16:11:15Z sam +.\" $FreeBSD$ Set to build libraries, programs, and kernel modules without 802.11 wireless support. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_WPA_SUPPLICANT_EAPOL -.\" from FreeBSD: head/tools/build/options/WITHOUT_WPA_SUPPLICANT_EAPOL 156932 2006-03-21 07:50:50Z ru +.\" $FreeBSD$ Build .Xr wpa_supplicant 8 without support for the IEEE 802.1X protocol and without support for EAP-PEAP, EAP-TLS, EAP-LEAP, and EAP-TTLS protocols (usable only via 802.1X). +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_ZFS -.\" from FreeBSD: head/tools/build/options/WITHOUT_ZFS 168409 2007-04-06 02:13:30Z pjd +.\" $FreeBSD$ Set to not build ZFS file system. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .It Va WITHOUT_ZONEINFO -.\" from FreeBSD: head/tools/build/options/WITHOUT_ZONEINFO 235342 2012-05-12 16:12:36Z gjb +.\" $FreeBSD$ Set to not build the timezone database. +When set, it also enforces the following options: +.Pp +.Bl -item -compact +.It +.Va WITHOUT_BIND_UTILS +.El .El .Sh FILES .Bl -tag -compact -width Pa -- Eitan Adler From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 00:45:55 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 21697BAE; Sat, 27 Apr 2013 00:45:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id ECC5915B0; Sat, 27 Apr 2013 00:45:54 +0000 (UTC) Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 5CCB423F804; Fri, 26 Apr 2013 20:45:53 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.2 onyx.glenbarber.us 5CCB423F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Fri, 26 Apr 2013 20:45:51 -0400 From: Glen Barber To: Eitan Adler Subject: Re: makeman issues Message-ID: <20130427004551.GD1611@glenbarber.us> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4zI0WCX1RcnW9Hbu" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 00:45:55 -0000 --4zI0WCX1RcnW9Hbu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 26, 2013 at 08:05:50PM -0400, Eitan Adler wrote: > I'm trying to regenerate src.conf.5 after my recent WITH*_IDEA removal > but the diff shows: >=20 > Does anyone know why WITHOUT_BIND_UTILS is showing up a bazillion times? >=20 Looks like DES already spotted this too. ------------------------------------------------------------------------ r246838 | des | 2013-02-15 10:09:24 -0500 (Fri, 15 Feb 2013) | 4 lines Manually add the correct text for the LDNS and LDNS_UTILS options. There seems to be a bug in makeman that causes it to misunderstand the relationship between LDNS_UTILS and BIND_UTILS. ------------------------------------------------------------------------ Glen --4zI0WCX1RcnW9Hbu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRex+/AAoJEFJPDDeguUajkd4H/3pMFmMi6U3vVrRixOyCvsvn lnGcbAlNuhL33JzkOXP/A//yMT3GKcC3ewVToBxPCDn5nJWMjgnDuODxlpgzYTyu W9H74CDDYHhK7ptIQgFEn6eI4xy1Lg3UJvvqOZ+ihvGOhpJoLZ4Up+EyzvMdHkFH zNV6dvkYJbBO+QL+5Scw3AEZV2/L3oTak1QBHGevAwWYpSBDsnxZWnmS5jrOP0UI SSNxkn9LQYwB4lOp1ROd+U8CkwEY2IzKnFrL1MRywA2Q2rSyqNoK8PZ+ulUpGchH lpVo1NK0hAnBkDf7RsQEsXNKl+ZCXkKgh6X/5A7GUNsgmJ4Iut1qULnmehWrr1E= =xE4o -----END PGP SIGNATURE----- --4zI0WCX1RcnW9Hbu-- From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 09:08:04 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 05269B36 for ; Sat, 27 Apr 2013 09:08:04 +0000 (UTC) (envelope-from coco@executive-computing.de) Received: from mail.moehre.org (mail.moehre.org [195.96.35.7]) by mx1.freebsd.org (Postfix) with ESMTP id BE9241399 for ; Sat, 27 Apr 2013 09:08:03 +0000 (UTC) Received: from mail.moehre.org (unknown [195.96.35.7]) by mail.moehre.org (Postfix) with ESMTP id 17E118B143B; Sat, 27 Apr 2013 11:07:57 +0200 (CEST) X-Spam-Flag: NO X-Spam-Score: -100.963 X-Spam-Level: X-Spam-Status: No, score=-100.963 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, AWL=0.037, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mail.moehre.org ([195.96.35.7]) by mail.moehre.org (mail.moehre.org [195.96.35.7]) (amavisd-new, port 10024) with ESMTP id i8cukUVLX8GU; Sat, 27 Apr 2013 11:07:55 +0200 (CEST) Received: from probsd.c0c0.intra (p54B08026.dip0.t-ipconnect.de [84.176.128.38]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: coco@executive-computing.de) by mail.moehre.org (Postfix) with ESMTPSA id 8422A8B1420; Sat, 27 Apr 2013 11:07:55 +0200 (CEST) Date: Sat, 27 Apr 2013 11:07:54 +0200 (CEST) From: Marco Steinbach X-X-Sender: coco@probsd.c0c0.intra To: Mike Ma Subject: Re: Port GlusterFS as a GSoC project In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 09:08:04 -0000 On Fri, 26 Apr 2013, Mike Ma wrote: > Hi there, > > I'm now a student and trying to get involved in GSoC this year. > I found the proposal of about GlusterFS in the idea list wiki page very > interesting to me, possibly it will be porting from NetBSD implementation. > As I'm quite distant from idea owner, he also suggested me to try to find > some folks that are physically closer to me to help mentoring. > So I'm writing to ask if there's any folk in Europe is interested helping > me with the project in any way, it could be easier for communication and > discussion. > > Thanks a lot. [...] I am very interested in this effort and could help with testing and the occassional odd line of code. I wouldn't be of much help for mentoring, though. MfG CoCo From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 10:09:35 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E489C83B for ; Sat, 27 Apr 2013 10:09:35 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-bk0-x22a.google.com (mail-bk0-x22a.google.com [IPv6:2a00:1450:4008:c01::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 7C5EB1588 for ; Sat, 27 Apr 2013 10:09:35 +0000 (UTC) Received: by mail-bk0-f42.google.com with SMTP id jf3so228631bkc.15 for ; Sat, 27 Apr 2013 03:09:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:from:to:subject:date:content-type :content-transfer-encoding:x-mailer; bh=4orFstq0NYWhcnF/jGKUU/8iwwwJb4xZktQyGFSjC/E=; b=d17memw1wKwiT7l5bi/JZXAM2PPTrW2tWsR+JdFzzR8NEr2MsMI1vI4Ea6SRfrii/D HyR/D7ROFawOmLnkoNM9JJmVF/WH/P+XuSvs2Vgt2q/xYDXqWudUwXTzBWtnLo+qNtYV c+qU68G9vveIUs8faB3CcV5wxf+Y297jAmYzkxBTRv8Rbw9qXAs83yzSzr3jraZoOtBQ dySp03LVueKfQNJRVqbFtJ5qIpPsv0p+A+4yapC1dgiqNc/nthuYDyHfEq9Wgf+BxOeO 2BRWkTQY0GqZoMaXwue7JmvXh8uqNXLjjsxnoMpUIYnJEEMgMyS94pAY6kbnPovAZy8b jXJA== X-Received: by 10.204.71.12 with SMTP id f12mr1830796bkj.32.1367057374339; Sat, 27 Apr 2013 03:09:34 -0700 (PDT) Received: from DOMYPC ([82.193.208.225]) by mx.google.com with ESMTPSA id fh8sm4261433bkc.10.2013.04.27.03.09.32 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 27 Apr 2013 03:09:33 -0700 (PDT) Message-ID: <20130427.100935.861.1@DOMY-PC> From: rank1seeker@gmail.com To: hackers@freebsd.org Subject: How to sabotage 9.*-RELEASE worldbuilds? Date: Sat, 27 Apr 2013 12:09:35 +0200 Content-Type: text/plain; charset="Windows-1250" Content-Transfer-Encoding: quoted-printable X-Mailer: POP Peeper (3.8.1.0) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 10:09:36 -0000 Just do this:=0D=0A# echo 'FORMATS=3D"html txt"' >> = /etc/make.conf=0D=0A=0D=0Abuildworld fails, at the SAME point for ALL = 9.*-RELEASE-es:=0D=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0A=3D=3D=3D> = lib/libauditd (all)=0D=0A=3D=3D=3D> lib/libcom_err (all)=0D=0Agzip -cn = /usr/src/lib/libcom_err/../../contrib/com_err/com_err.3 > = com_err.3.gz=0D=0A=3D=3D=3D> lib/libcom_err/doc (all)=0D=0AGraph cycles = through com_err.'html=0D=0A=0D=0Amake: don't know how to make txt'. = Stop=0D=0A*** Error code 2=0D=0A=0D=0AStop in = /usr/src/lib/libcom_err.=0D=0A*** Error code 1=0D=0A=0D=0AStop in = /usr/src/lib.=0D=0A*** Error code 1=0D=0A=0D=0AStop in /usr/src.=0D=0A*** = Error code 1=0D=0A=0D=0AStop in /usr/src.=0D=0A*** Error code = 1=0D=0A=0D=0AStop in = /usr/src.=0D=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0A=0D=0A=0D=0AIf you = aren't in a mood, to wait for a buildworld to fail, you can see errors = faster:=0D=0A# cd /usr/src && make cleandir > = /dev/null=0D=0A---=0D=0A"/usr/src/share/mk/bsd.info.mk", line 140: = warning: duplicate script for target "txt".gz" = ignored=0D=0A...=0D=0A---=0D=0A=0D=0A=0D=0AFor /usr/doc builds, in = /etc/make.conf, I have:=0D=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0A# For = port = textproc/docproj=0D=0AWITH_JADETEX=3DYES=0D=0ADOC_LANG=3D"en_US.ISO8859-1"=0D=0AFORMATS=3D"html = txt"=0D=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0A=0D=0A=0D=0ADomagoj = Smol=E8i=E6 From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 10:11:26 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D555995C for ; Sat, 27 Apr 2013 10:11:26 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ia0-x235.google.com (mail-ia0-x235.google.com [IPv6:2607:f8b0:4001:c02::235]) by mx1.freebsd.org (Postfix) with ESMTP id AC9F2159E for ; Sat, 27 Apr 2013 10:11:26 +0000 (UTC) Received: by mail-ia0-f181.google.com with SMTP id k38so4276803iah.40 for ; Sat, 27 Apr 2013 03:11:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=uh1lHvZJMyPU10f1NkVV3L1tuPCApnG0IHE5Duy8zRA=; b=Nd/stxgFOQdK9x6pSqrbcFu8hq8Z8dQanVySZn9crviGN2OdseLbgonORU41F7/XVE 2ELmb8khPmn1bJOYNoPmBg/0FykpsB3ulHGh3zMPm+0SOiYmTV5bQ5dr73Xxy/oUbFyT IP1DdWLA7rlf9qYbc8lgvntsucoy7W696LpBJHO/LJA4ofMOQiUImKemGPLZlla48kfm BpIS8W8px4SiFoWId7thhRZGRWadXXJM0P+C5kBvtqDJR0QS5w9+HTi4iOzGE/90LmVO GzzLCaDrYr0wdo0KbDCYbKtvuWYwCnh5O1U6cvQQLp6FvChVqMrv0IFoQxbgz5XpnEsC NrJw== MIME-Version: 1.0 X-Received: by 10.50.114.3 with SMTP id jc3mr1325013igb.75.1367057485793; Sat, 27 Apr 2013 03:11:25 -0700 (PDT) Received: by 10.64.58.52 with HTTP; Sat, 27 Apr 2013 03:11:25 -0700 (PDT) Received: by 10.64.58.52 with HTTP; Sat, 27 Apr 2013 03:11:25 -0700 (PDT) In-Reply-To: <20130427.100935.861.1@DOMY-PC> References: <20130427.100935.861.1@DOMY-PC> Date: Sat, 27 Apr 2013 11:11:25 +0100 Message-ID: Subject: Re: How to sabotage 9.*-RELEASE worldbuilds? From: Chris Rees To: rank1seeker@gmail.com Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 10:11:26 -0000 On 27 Apr 2013 11:09, wrote: > > Just do this: > # echo 'FORMATS="html txt"' >> /etc/make.conf > > buildworld fails, at the SAME point for ALL 9.*-RELEASE-es: > =========== > ===> lib/libauditd (all) > ===> lib/libcom_err (all) > gzip -cn /usr/src/lib/libcom_err/../../contrib/com_err/com_err.3 > com_err.3.gz > ===> lib/libcom_err/doc (all) > Graph cycles through com_err.'html > > make: don't know how to make txt'. Stop > *** Error code 2 > > Stop in /usr/src/lib/libcom_err. > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > =========== > > > If you aren't in a mood, to wait for a buildworld to fail, you can see errors faster: > # cd /usr/src && make cleandir > /dev/null > --- > "/usr/src/share/mk/bsd.info.mk", line 140: warning: duplicate script for target "txt".gz" ignored > ... > --- > > > For /usr/doc builds, in /etc/make.conf, I have: > =========== > # For port textproc/docproj > WITH_JADETEX=YES > DOC_LANG="en_US.ISO8859-1" > FORMATS="html txt" And yet another example of misunderstanding how quotes in Makefiles breaks things :) If in doubt, leave quotes out! (This only applies to make) Chris From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 15:54:13 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A43C2CEF; Sat, 27 Apr 2013 15:54:13 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id E80551EE4; Sat, 27 Apr 2013 15:54:12 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id j13so2671751wgh.2 for ; Sat, 27 Apr 2013 08:54:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=q3kuv3cKSM65IsCNMRJAQjKlvarEuu7jY9eF9FH3xJg=; b=kmfDXuIaH+bpX2/2Op7m3P5cguMOhvZl6divzRlYgnDhIr/ju5pNgsiVAi0UCfpAbg k6zjPmcsHoNXxp8zhKmc9BJ8l00o3ukgenxGKUnzbcILI/+YghEF8GsefXlmp8ugCfFb aqhtbJif6aewIqBJKEJSm18KvBUsu9/ia4VjzMmD57vn99nllP/W1bvDY3xXbcpM28ZO zHX9kAsTu4cWH982iRuTJbBgCw21UbgIUhhD1hOO486QY+8ahMN1aylPzudlgG0BVM7o bVqIhzIkwhRH5aXXAijDqvhidgtcbeCbM2/licfvmnI1CcZQ+buGt5qIYF+8sGR79wE3 ROTQ== MIME-Version: 1.0 X-Received: by 10.194.236.169 with SMTP id uv9mr6843526wjc.42.1367078052040; Sat, 27 Apr 2013 08:54:12 -0700 (PDT) Received: by 10.216.139.72 with HTTP; Sat, 27 Apr 2013 08:54:11 -0700 (PDT) Date: Sat, 27 Apr 2013 18:54:11 +0300 Message-ID: Subject: config(8) -x headscratcher From: Kimmo Paasiala To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, FreeBSD current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 15:54:13 -0000 I'm getting a core dump on 'config -x /boot/kernel/kernel' on 9.1-RELEASE i386. Assertion failed: (r != '\0' && ("Char present in the configuration " "string mustn't be equal to 0")), function kernconfdump, file /usr/src/usr.sbin/config/main.c, line 710. I have double checked that my config file is sane and does not have any funny characters anywhere. The system is i386 9.1-RELEASE r249856. The world and kernel are built with clang and I'm suspecting that the use of clang has something to do with this segfault. Looking at the kernel files I can see one very obvious difference. This is the 'elfdump -c kernel | grep -A 8 kern_conf' output (what config -x seems to use for finding out the config file from the kernel image) for the GENERIC kernel from the stock installation: sh_name: kern_conf sh_type: SHT_PROGBITS sh_flags: SHF_ALLOC sh_addr: 0xc1039f80 sh_offset: 12820352 sh_size: 3771 sh_link: 0 sh_info: 0 sh_addralign: 32 And this is from the kernel I have built myself using clang and a custom config file: sh_name: kern_conf sh_type: SHT_PROGBITS sh_flags: SHF_ALLOC sh_addr: 0xc09aee9c sh_offset: 5959324 sh_size: 1994 sh_link: 0 sh_info: 0 sh_addralign: 1 The align field looks suspicious, config -x seems to use it to check for padding but to me it looks like the logic may not work if the alignment is 1. This the relevant bit from main.c of config(8) if (r == '\0' && (size - i) < align) break; assert(r != '\0' && ("Char present in the configuration " "string mustn't be equal to 0")); fputc(r, stdout); -Kimmo From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 16:20:37 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 063997C9 for ; Sat, 27 Apr 2013 16:20:37 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-bk0-x22e.google.com (mail-bk0-x22e.google.com [IPv6:2a00:1450:4008:c01::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 90FF81FF2 for ; Sat, 27 Apr 2013 16:20:36 +0000 (UTC) Received: by mail-bk0-f46.google.com with SMTP id e19so1714021bku.33 for ; Sat, 27 Apr 2013 09:20:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:from:to:subject:date:in-reply-to:references :x-mailer; bh=A5ni8vqRw4RBxgRga4ipisd9mMUbuGZSRcCP0vToPuk=; b=lJxlOboHBEdhSgPI2MuI1DGgJJV3CcqVOFKP/RPdlub5KpY2iS2mWPeOUPM6nV+uqv wHblwgWscnXzEviDDCdfg52+MyLFjKgzvm+WD/2Jg0U4yRQEDB49LdZKw23CCTQpBI6l yPr1Xl+XpI/b1K6hgZIKJcB9ojr2sJoo05AeMmoRzRiFIdRAjox8ESXow9vdqRjRU68k MCkppdXytzl/zKXaEB1SGzt+yPxhEv/GZ4HPP1OIZJ7NVUhNqmGGMBKcdsHGr8Unr4gN W9+3WXs9FQIM9CkwpUm2rqJXXGSs///zoWaj0DazH6vQnEcYGvC6DwDXt197IpYGFCgs 325Q== X-Received: by 10.205.108.137 with SMTP id ec9mr19917309bkc.6.1367079634827; Sat, 27 Apr 2013 09:20:34 -0700 (PDT) Received: from DOMYPC ([82.193.208.225]) by mx.google.com with ESMTPSA id jz9sm4673136bkb.1.2013.04.27.09.20.32 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 27 Apr 2013 09:20:33 -0700 (PDT) Message-ID: <20130427.162036.752.2@DOMY-PC> From: rank1seeker@gmail.com To: "Chris Rees" , freebsd-hackers@freebsd.org Subject: Re: How to sabotage 9.*-RELEASE worldbuilds? Date: Sat, 27 Apr 2013 18:20:36 +0200 In-Reply-To: References: <20130427.100935.861.1@DOMY-PC> X-Mailer: POP Peeper (3.8.1.0) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 16:20:37 -0000 > > Just do this: > > # echo 'FORMATS="html txt"' >> /etc/make.conf > > > > buildworld fails, at the SAME point for ALL 9.*-RELEASE-es: > > =========== > > ===> lib/libauditd (all) > > ===> lib/libcom_err (all) > > gzip -cn /usr/src/lib/libcom_err/../../contrib/com_err/com_err.3 > > com_err.3.gz > > ===> lib/libcom_err/doc (all) > > Graph cycles through com_err.'html > > > > make: don't know how to make txt'. Stop > > *** Error code 2 > > > > Stop in /usr/src/lib/libcom_err. > > *** Error code 1 > > > > Stop in /usr/src/lib. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > =========== > > > > > > If you aren't in a mood, to wait for a buildworld to fail, you can see > errors faster: > > # cd /usr/src && make cleandir > /dev/null > > --- > > "/usr/src/share/mk/bsd.info.mk", line 140: warning: duplicate script for > target "txt".gz" ignored > > ... > > --- > > > > > > For /usr/doc builds, in /etc/make.conf, I have: > > =========== > > # For port textproc/docproj > > WITH_JADETEX=YES > > DOC_LANG="en_US.ISO8859-1" > > FORMATS="html txt" > > And yet another example of misunderstanding how quotes in Makefiles breaks > things :) > > If in doubt, leave quotes out! > > (This only applies to make) > > Chris > I see. So now I've used this: ========== # For port textproc/docproj WITH_JADETEX=YES DOC_LANG=en_US.ISO8859-1 FORMATS=html txt ========== buildworld failed again, but with different error: ========== gzip -cn /usr/src/lib/libbsm/../../contrib/openbsm/man/setauid.2 > setauid.2.gz ===> lib/libauditd (all) ===> lib/libcom_err (all) gzip -cn /usr/src/lib/libcom_err/../../contrib/com_err/com_err.3 > com_err.3.gz ===> lib/libcom_err/doc (all) makeinfo --no-split -I /usr/src/lib/libcom_err/doc -I /usr/src/lib/libcom_err/doc /usr/src/lib/libcom_err/doc/com_err.texinfo - o com_err.info /usr/src/lib/libcom_err/doc/com_err.texinfo:377: warning: unlikely character ( in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:377: warning: unlikely character ) in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:384: warning: unlikely character ( in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:384: warning: unlikely character ) in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:577: warning: unlikely character ( in @var. /usr/src/lib/libcom_err/doc/com_err.texinfo:577: warning: unlikely character ) in @var. info2html com_err.info info2html: No such file or directory *** [com_err.html] Error code 1 Stop in /usr/src/lib/libcom_err/doc. *** [all] Error code 1 Stop in /usr/src/lib/libcom_err. *** [all] Error code 1 Stop in /usr/src/lib. *** [lib.all__D] Error code 1 Stop in /usr/src. *** [everything] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. ========== However: # cd /usr/src && make cleandir > /dev/null , now doesn't emit any errors. Domagoj From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 19:06:02 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BFFDCFA4 for ; Sat, 27 Apr 2013 19:06:02 +0000 (UTC) (envelope-from wkoszek@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [212.87.224.105]) by mx1.freebsd.org (Postfix) with ESMTP id 3F7B515FE for ; Sat, 27 Apr 2013 19:06:02 +0000 (UTC) Received: from freebsd.czest.pl (freebsd.czest.pl [212.87.224.105]) by freebsd.czest.pl (8.14.5/8.14.5) with ESMTP id r3RJ5FBl085935; Sat, 27 Apr 2013 19:05:15 GMT (envelope-from wkoszek@freebsd.czest.pl) Received: (from wkoszek@localhost) by freebsd.czest.pl (8.14.5/8.14.5/Submit) id r3RJ5Fp3085934; Sat, 27 Apr 2013 19:05:15 GMT (envelope-from wkoszek) Date: Sat, 27 Apr 2013 19:05:15 +0000 From: "Wojciech A. Koszek" To: Kimmo Paasiala Subject: Re: config(8) -x headscratcher Message-ID: <20130427190514.GA85673@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-0.4 required=5.0 tests=RP_MATCHES_RCVD, SPF_HELO_PASS, SPF_PASS autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on freebsd.czest.pl X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (freebsd.czest.pl [212.87.224.105]); Sat, 27 Apr 2013 19:05:19 +0000 (UTC) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 19:06:02 -0000 On Sat, Apr 27, 2013 at 06:54:11PM +0300, Kimmo Paasiala wrote: > I'm getting a core dump on 'config -x /boot/kernel/kernel' on 9.1-RELEASE i386. > > Assertion failed: (r != '\0' && ("Char present in the configuration " > "string mustn't be equal to 0")), function kernconfdump, file > /usr/src/usr.sbin/config/main.c, line 710. > > I have double checked that my config file is sane and does not have > any funny characters anywhere. > > The system is i386 9.1-RELEASE r249856. The world and kernel are built > with clang and I'm suspecting that the use of clang has something to > do with this segfault. > > Looking at the kernel files I can see one very obvious difference. > This is the 'elfdump -c kernel | grep -A 8 kern_conf' output (what > config -x seems to use for finding out the config file from the kernel > image) for the GENERIC kernel from the stock installation: > > sh_name: kern_conf > sh_type: SHT_PROGBITS > sh_flags: SHF_ALLOC > sh_addr: 0xc1039f80 > sh_offset: 12820352 > sh_size: 3771 > sh_link: 0 > sh_info: 0 > sh_addralign: 32 > > And this is from the kernel I have built myself using clang and a > custom config file: > > sh_name: kern_conf > sh_type: SHT_PROGBITS > sh_flags: SHF_ALLOC > sh_addr: 0xc09aee9c > sh_offset: 5959324 > sh_size: 1994 > sh_link: 0 > sh_info: 0 > sh_addralign: 1 > > The align field looks suspicious, config -x seems to use it to check > for padding but to me it looks like the logic may not work if the > alignment is 1. > > This the relevant bit from main.c of config(8) > Kimmo, Lets keep discussion on hackers@ only. I do agree with you that config(8) internal implementation might have its issues. Can you make your kernel configuration file, faulty kernel image and exact build instructions available to me? -- Wojciech A. Koszek wkoszek@FreeBSD.czest.pl http://FreeBSD.czest.pl/~wkoszek/ From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 20:38:48 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 723AC26B for ; Sat, 27 Apr 2013 20:38:48 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 37F671886 for ; Sat, 27 Apr 2013 20:38:47 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAMU2fFGDaFvO/2dsb2JhbABTFoMngze7EYEZdIImIwSBFhkCBFWILwyeZY5UkG2OZhkigjyBEwOPaYc1gSaIZYcfgy0ggWw X-IronPort-AV: E=Sophos;i="4.87,564,1363147200"; d="scan'208";a="25793614" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 27 Apr 2013 16:38:46 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id BEE3CB408A for ; Sat, 27 Apr 2013 16:38:46 -0400 (EDT) Date: Sat, 27 Apr 2013 16:38:46 -0400 (EDT) From: Rick Macklem To: freebsd-hackers@freebsd.org Message-ID: <1513398963.1192605.1367095126723.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1589161980.1192602.1367095122855.JavaMail.root@erie.cs.uoguelph.ca> Subject: review of patches for the gssd that handle getpwXX_r ERANGE return MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1192604_1659352415.1367095126720" X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 20:38:48 -0000 ------=_Part_1192604_1659352415.1367095126720 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi, I have attached two patches, which can also be found at: http://people.freebsd.org/~rmacklem/getpw.patch1 and getpw.patch2 They are almost identical and handle the ERANGE error return from getpw[nam|uid]_r() when buf[128] isn't large enough. Is anyone interested in reviewing these? (This has been discussed some time ago, but the patch was never reviewed. Actually I reviewed a patch similar to this, but the submitter subsequently requested that I not use their patch, so I wrote similar ones.) Thanks in advance for any review, rick ------=_Part_1192604_1659352415.1367095126720 Content-Type: text/x-patch; name=getpw.patch1 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=getpw.patch1 LS0tIHVzci5zYmluL2dzc2QvZ3NzZC5jLnNhdgkyMDEzLTA0LTI2IDIwOjM4OjQ1LjAwMDAwMDAw MCAtMDQwMAorKysgdXNyLnNiaW4vZ3NzZC9nc3NkLmMJMjAxMy0wNC0yNiAyMDozODo1My4wMDAw MDAwMDAgLTA0MDAKQEAgLTM3LDYgKzM3LDcgQEAgX19GQlNESUQoIiRGcmVlQlNEOiBoZWFkL3Vz ci5zYmluL2dzc2QvZwogI2luY2x1ZGUgPGN0eXBlLmg+CiAjaW5jbHVkZSA8ZGlyZW50Lmg+CiAj aW5jbHVkZSA8ZXJyLmg+CisjaW5jbHVkZSA8ZXJybm8uaD4KICNpZm5kZWYgV0lUSE9VVF9LRVJC RVJPUwogI2luY2x1ZGUgPGtyYjUuaD4KICNlbmRpZgpAQCAtNTU3LDggKzU1OCwxMSBAQCBnc3Nk X3BuYW1lX3RvX3VpZF8xX3N2YyhwbmFtZV90b191aWRfYXJnCiB7CiAJZ3NzX25hbWVfdCBuYW1l ID0gZ3NzZF9maW5kX3Jlc291cmNlKGFyZ3AtPnBuYW1lKTsKIAl1aWRfdCB1aWQ7Ci0JY2hhciBi dWZbMTI4XTsKKwljaGFyIGJ1ZlsxMDI0XSwgKmJ1ZnA7CiAJc3RydWN0IHBhc3N3ZCBwd2QsICpw dzsKKwlzaXplX3QgYnVmbGVuOworCWludCBlcnJvcjsKKwlzdGF0aWMgc2l6ZV90IGJ1Zmxlbl9o aW50ID0gMTAyNDsKIAogCW1lbXNldChyZXN1bHQsIDAsIHNpemVvZigqcmVzdWx0KSk7CiAJaWYg KG5hbWUpIHsKQEAgLTU2Nyw3ICs1NzEsMjQgQEAgZ3NzZF9wbmFtZV90b191aWRfMV9zdmMocG5h bWVfdG9fdWlkX2FyZwogCQkJICAgIG5hbWUsIGFyZ3AtPm1lY2gsICZ1aWQpOwogCQlpZiAocmVz dWx0LT5tYWpvcl9zdGF0dXMgPT0gR1NTX1NfQ09NUExFVEUpIHsKIAkJCXJlc3VsdC0+dWlkID0g dWlkOwotCQkJZ2V0cHd1aWRfcih1aWQsICZwd2QsIGJ1Ziwgc2l6ZW9mKGJ1ZiksICZwdyk7CisJ CQlidWZsZW4gPSBidWZsZW5faGludDsKKwkJCWZvciAoOzspIHsKKwkJCQlwdyA9IE5VTEw7CisJ CQkJYnVmcCA9IGJ1ZjsKKwkJCQlpZiAoYnVmbGVuID4gc2l6ZW9mKGJ1ZikpCisJCQkJCWJ1ZnAg PSBtYWxsb2MoYnVmbGVuKTsKKwkJCQlpZiAoYnVmcCA9PSBOVUxMKQorCQkJCQlicmVhazsKKwkJ CQllcnJvciA9IGdldHB3dWlkX3IodWlkLCAmcHdkLCBidWZwLCBidWZsZW4sCisJCQkJICAgICZw dyk7CisJCQkJaWYgKGVycm9yICE9IEVSQU5HRSkKKwkJCQkJYnJlYWs7CisJCQkJaWYgKGJ1Zmxl biA+IHNpemVvZihidWYpKQorCQkJCQlmcmVlKGJ1ZnApOworCQkJCWJ1ZmxlbiArPSAxMDI0Owor CQkJCWlmIChidWZsZW4gPiBidWZsZW5faGludCkKKwkJCQkJYnVmbGVuX2hpbnQgPSBidWZsZW47 CisJCQl9CiAJCQlpZiAocHcpIHsKIAkJCQlpbnQgbGVuID0gTkdSUFM7CiAJCQkJaW50IGdyb3Vw c1tOR1JQU107CkBAIC01ODQsNiArNjA1LDggQEAgZ3NzZF9wbmFtZV90b191aWRfMV9zdmMocG5h bWVfdG9fdWlkX2FyZwogCQkJCXJlc3VsdC0+Z2lkbGlzdC5naWRsaXN0X2xlbiA9IDA7CiAJCQkJ cmVzdWx0LT5naWRsaXN0LmdpZGxpc3RfdmFsID0gTlVMTDsKIAkJCX0KKwkJCWlmIChidWZwICE9 IE5VTEwgJiYgYnVmbGVuID4gc2l6ZW9mKGJ1ZikpCisJCQkJZnJlZShidWZwKTsKIAkJfQogCX0g ZWxzZSB7CiAJCXJlc3VsdC0+bWFqb3Jfc3RhdHVzID0gR1NTX1NfQkFEX05BTUU7Cg== ------=_Part_1192604_1659352415.1367095126720 Content-Type: text/x-patch; name=getpw.patch2 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=getpw.patch2 LS0tIGtlcmJlcm9zNS9saWIvbGliZ3NzYXBpX2tyYjUvcG5hbWVfdG9fdWlkLmMuc2F2CTIwMTMt MDQtMjYgMjA6Mzc6NDUuMDAwMDAwMDAwIC0wNDAwCisrKyBrZXJiZXJvczUvbGliL2xpYmdzc2Fw aV9rcmI1L3BuYW1lX3RvX3VpZC5jCTIwMTMtMDQtMjcgMTY6MjU6MTQuMDAwMDAwMDAwIC0wNDAw CkBAIC0yNiw2ICsyNiw3IEBACiAgKi8KIC8qICRGcmVlQlNEOiBoZWFkL2tlcmJlcm9zNS9saWIv bGliZ3NzYXBpX2tyYjUvcG5hbWVfdG9fdWlkLmMgMTgxMzQ0IDIwMDgtMDgtMDYgMTQ6MDI6MDVa IGRmciAkICovCiAKKyNpbmNsdWRlIDxlcnJuby5oPgogI2luY2x1ZGUgPHB3ZC5oPgogCiAjaW5j bHVkZSAia3JiNS9nc3NrcmI1X2xvY2wuaCIKQEAgLTM3LDggKzM4LDEyIEBAIF9nc3NrcmI1X3Bu YW1lX3RvX3VpZChPTV91aW50MzIgKm1pbm9yX3MKIAlrcmI1X2NvbnRleHQgY29udGV4dDsKIAlr cmI1X2NvbnN0X3ByaW5jaXBhbCBuYW1lID0gKGtyYjVfY29uc3RfcHJpbmNpcGFsKSBwbmFtZTsK IAlrcmI1X2Vycm9yX2NvZGUga3JldDsKLQljaGFyIGxuYW1lW01BWExPR05BTUUgKyAxXSwgYnVm WzEyOF07CisJY2hhciBsbmFtZVtNQVhMT0dOQU1FICsgMV0sIGJ1ZlsxMDI0XSwgKmJ1ZnA7CiAJ c3RydWN0IHBhc3N3ZCBwd2QsICpwdzsKKwlzaXplX3QgYnVmbGVuOworCWludCBlcnJvcjsKKwlP TV91aW50MzIgcmV0OworCXN0YXRpYyBzaXplX3QgYnVmbGVuX2hpbnQgPSAxMDI0OwogCiAJR1NT QVBJX0tSQjVfSU5JVCAoJmNvbnRleHQpOwogCkBAIC00OSwxMSArNTQsMzAgQEAgX2dzc2tyYjVf cG5hbWVfdG9fdWlkKE9NX3VpbnQzMiAqbWlub3JfcwogCX0KIAogCSptaW5vcl9zdGF0dXMgPSAw OwotCWdldHB3bmFtX3IobG5hbWUsICZwd2QsIGJ1Ziwgc2l6ZW9mKGJ1ZiksICZwdyk7CisJYnVm bGVuID0gYnVmbGVuX2hpbnQ7CisJZm9yICg7OykgeworCQlwdyA9IE5VTEw7CisJCWJ1ZnAgPSBi dWY7CisJCWlmIChidWZsZW4gPiBzaXplb2YoYnVmKSkKKwkJCWJ1ZnAgPSBtYWxsb2MoYnVmbGVu KTsKKwkJaWYgKGJ1ZnAgPT0gTlVMTCkKKwkJCWJyZWFrOworCQllcnJvciA9IGdldHB3bmFtX3Io bG5hbWUsICZwd2QsIGJ1ZnAsIGJ1ZmxlbiwgJnB3KTsKKwkJaWYgKGVycm9yICE9IEVSQU5HRSkK KwkJCWJyZWFrOworCQlpZiAoYnVmbGVuID4gc2l6ZW9mKGJ1ZikpCisJCQlmcmVlKGJ1ZnApOwor CQlidWZsZW4gKz0gMTAyNDsKKwkJaWYgKGJ1ZmxlbiA+IGJ1Zmxlbl9oaW50KQorCQkJYnVmbGVu X2hpbnQgPSBidWZsZW47CisJfQogCWlmIChwdykgewogCQkqdWlkcCA9IHB3LT5wd191aWQ7Ci0J CXJldHVybiAoR1NTX1NfQ09NUExFVEUpOworCQlyZXQgPSBHU1NfU19DT01QTEVURTsKIAl9IGVs c2UgewotCQlyZXR1cm4gKEdTU19TX0ZBSUxVUkUpOworCQlyZXQgPSBHU1NfU19GQUlMVVJFOwog CX0KKwlpZiAoYnVmcCAhPSBOVUxMICYmIGJ1ZmxlbiA+IHNpemVvZihidWYpKQorCQlmcmVlKGJ1 ZnApOworCXJldHVybiAocmV0KTsKIH0K ------=_Part_1192604_1659352415.1367095126720-- From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 20:42:20 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1CD3E412; Sat, 27 Apr 2013 20:42:20 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by mx1.freebsd.org (Postfix) with ESMTP id 87E7118B4; Sat, 27 Apr 2013 20:42:19 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id l13so1661234wie.12 for ; Sat, 27 Apr 2013 13:42:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=tZTdlDQ/uM7zHr4oV2M/gc2TEMffBgAEGLS8Ngh4mrg=; b=H+Tp9awk0Wv/OGhDUDw0BzF3uokmm+zcwp9YCaMEyLow3zf7tA0ebJc4QFo34wwLNT CeBLVq7XDL98jkcce5W7QaMrGvLkq4FWIwZvpkQC4vcBDqCzYTpwA439P/aUifvDVnyB PsEZ8I8Wg5QwJmng5e8OXnOSzz7nqsHmM3ox8HZXd1BKC6puKbSQR5i78Nnl+C1/mTM1 ZB97Kxoz9ce2QwkTjayRGfRV5UyNbhz/grk9lgpcuZrzADwUX0hCWSk3GKJVM2/v1ImS f5g7852EcY+HHK7IC5rJ5yYaLQrRZtCKXUbrWkoW5jFnBr16A3iXq7LRiMTO2v/BLclc Na4Q== MIME-Version: 1.0 X-Received: by 10.194.59.106 with SMTP id y10mr7040148wjq.28.1367095338770; Sat, 27 Apr 2013 13:42:18 -0700 (PDT) Received: by 10.216.139.72 with HTTP; Sat, 27 Apr 2013 13:42:18 -0700 (PDT) In-Reply-To: <20130427190514.GA85673@FreeBSD.org> References: <20130427190514.GA85673@FreeBSD.org> Date: Sat, 27 Apr 2013 23:42:18 +0300 Message-ID: Subject: Re: config(8) -x headscratcher From: Kimmo Paasiala To: "Wojciech A. Koszek" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 20:42:20 -0000 On Sat, Apr 27, 2013 at 10:05 PM, Wojciech A. Koszek wrote: > On Sat, Apr 27, 2013 at 06:54:11PM +0300, Kimmo Paasiala wrote: >> I'm getting a core dump on 'config -x /boot/kernel/kernel' on 9.1-RELEASE i386. >> >> Assertion failed: (r != '\0' && ("Char present in the configuration " >> "string mustn't be equal to 0")), function kernconfdump, file >> /usr/src/usr.sbin/config/main.c, line 710. >> >> I have double checked that my config file is sane and does not have >> any funny characters anywhere. >> >> The system is i386 9.1-RELEASE r249856. The world and kernel are built >> with clang and I'm suspecting that the use of clang has something to >> do with this segfault. >> >> Looking at the kernel files I can see one very obvious difference. >> This is the 'elfdump -c kernel | grep -A 8 kern_conf' output (what >> config -x seems to use for finding out the config file from the kernel >> image) for the GENERIC kernel from the stock installation: >> >> sh_name: kern_conf >> sh_type: SHT_PROGBITS >> sh_flags: SHF_ALLOC >> sh_addr: 0xc1039f80 >> sh_offset: 12820352 >> sh_size: 3771 >> sh_link: 0 >> sh_info: 0 >> sh_addralign: 32 >> >> And this is from the kernel I have built myself using clang and a >> custom config file: >> >> sh_name: kern_conf >> sh_type: SHT_PROGBITS >> sh_flags: SHF_ALLOC >> sh_addr: 0xc09aee9c >> sh_offset: 5959324 >> sh_size: 1994 >> sh_link: 0 >> sh_info: 0 >> sh_addralign: 1 >> >> The align field looks suspicious, config -x seems to use it to check >> for padding but to me it looks like the logic may not work if the >> alignment is 1. >> >> This the relevant bit from main.c of config(8) >> > > Kimmo, > > Lets keep discussion on hackers@ only. I do agree with you that config(8) > internal implementation might have its issues. > > Can you make your kernel configuration file, faulty kernel image and exact > build instructions available to me? > > -- > Wojciech A. Koszek > wkoszek@FreeBSD.czest.pl > http://FreeBSD.czest.pl/~wkoszek/ The kernel config file: http://pastebin.com/j0J9NPCi My /etc/make.conf: http://pastebin.com/HYudWCA9 And /etc/src.conf: http://pastebin.com/ZAKq6ABT I'll see how I can make the kernel image available. -Kimmo From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 27 20:53:37 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B60BD683; Sat, 27 Apr 2013 20:53:37 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 2CD6A19F5; Sat, 27 Apr 2013 20:53:37 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id i48so1338037wef.6 for ; Sat, 27 Apr 2013 13:53:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=VKx3HDwhFn1fyxrk4VDBbvP0/fDVdcDtZ5tY7ud6VXM=; b=AYEwF52WpV3UMja683qV7zTyMxPCJiNSxlKQ9VVKkQVcqHiGeuAxECMF/+URJODQ4G h+I+rFl2VsSiLYyb0wCOW1mfxcQFxna2eeWuy37ropHBjNjKWQCMD7dVBMWMsNKBs7T7 HC+Q7LS3+O6K/RQ/3cHxWdLUoKlWRulv4U+D2bB7zEAGQXE+NfwFS2jOd3mrR29VEPX9 9ea3Bup6x/kgb8rJ3xyKoWD1b++vuAyIwu2ujCKo6QIGvRqr54ZwnPRrhad9rO+fZK2H A73CuImbkXFWP9qgMzsTj0z1MvBFU9/spAcl0e9fVkqd6YJB8ZmlbVwgIa1CaoucQvqP aFiw== MIME-Version: 1.0 X-Received: by 10.194.236.169 with SMTP id uv9mr7690667wjc.42.1367096016232; Sat, 27 Apr 2013 13:53:36 -0700 (PDT) Received: by 10.216.139.72 with HTTP; Sat, 27 Apr 2013 13:53:36 -0700 (PDT) In-Reply-To: References: <20130427190514.GA85673@FreeBSD.org> Date: Sat, 27 Apr 2013 23:53:36 +0300 Message-ID: Subject: Re: config(8) -x headscratcher From: Kimmo Paasiala To: "Wojciech A. Koszek" Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 20:53:37 -0000 On Sat, Apr 27, 2013 at 11:42 PM, Kimmo Paasiala wrote: > On Sat, Apr 27, 2013 at 10:05 PM, Wojciech A. Koszek > wrote: >> On Sat, Apr 27, 2013 at 06:54:11PM +0300, Kimmo Paasiala wrote: >>> I'm getting a core dump on 'config -x /boot/kernel/kernel' on 9.1-RELEASE i386. >>> >>> Assertion failed: (r != '\0' && ("Char present in the configuration " >>> "string mustn't be equal to 0")), function kernconfdump, file >>> /usr/src/usr.sbin/config/main.c, line 710. >>> >>> I have double checked that my config file is sane and does not have >>> any funny characters anywhere. >>> >>> The system is i386 9.1-RELEASE r249856. The world and kernel are built >>> with clang and I'm suspecting that the use of clang has something to >>> do with this segfault. >>> >>> Looking at the kernel files I can see one very obvious difference. >>> This is the 'elfdump -c kernel | grep -A 8 kern_conf' output (what >>> config -x seems to use for finding out the config file from the kernel >>> image) for the GENERIC kernel from the stock installation: >>> >>> sh_name: kern_conf >>> sh_type: SHT_PROGBITS >>> sh_flags: SHF_ALLOC >>> sh_addr: 0xc1039f80 >>> sh_offset: 12820352 >>> sh_size: 3771 >>> sh_link: 0 >>> sh_info: 0 >>> sh_addralign: 32 >>> >>> And this is from the kernel I have built myself using clang and a >>> custom config file: >>> >>> sh_name: kern_conf >>> sh_type: SHT_PROGBITS >>> sh_flags: SHF_ALLOC >>> sh_addr: 0xc09aee9c >>> sh_offset: 5959324 >>> sh_size: 1994 >>> sh_link: 0 >>> sh_info: 0 >>> sh_addralign: 1 >>> >>> The align field looks suspicious, config -x seems to use it to check >>> for padding but to me it looks like the logic may not work if the >>> alignment is 1. >>> >>> This the relevant bit from main.c of config(8) >>> >> >> Kimmo, >> >> Lets keep discussion on hackers@ only. I do agree with you that config(8) >> internal implementation might have its issues. >> >> Can you make your kernel configuration file, faulty kernel image and exact >> build instructions available to me? >> >> -- >> Wojciech A. Koszek >> wkoszek@FreeBSD.czest.pl >> http://FreeBSD.czest.pl/~wkoszek/ > > The kernel config file: > > http://pastebin.com/j0J9NPCi > > My /etc/make.conf: > > http://pastebin.com/HYudWCA9 > > And /etc/src.conf: > > http://pastebin.com/ZAKq6ABT > > I'll see how I can make the kernel image available. > > -Kimmo The kernel file: https://www.dropbox.com/s/07mjk6j4ditbl9r/kernel -Kimmo