From owner-freebsd-arch Sun Sep 2 12:21:29 2001 Delivered-To: freebsd-arch@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id EEEEA37B406; Sun, 2 Sep 2001 12:21:25 -0700 (PDT) Date: Sun, 2 Sep 2001 12:21:25 -0700 From: David O'Brien To: Cy Schubert - ITSD Open Systems Group Cc: Alfred Perlstein , John Polstra , arch@FreeBSD.ORG Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) Message-ID: <20010902122125.A80825@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <20010901134303.X81307@elvis.mu.org> <200109011855.f81ItpL00748@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109011855.f81ItpL00748@cwsys.cwsent.com>; from Cy.Schubert@uumail.gov.bc.ca on Sat, Sep 01, 2001 at 11:55:04AM -0700 X-Operating-System: FreeBSD 4.3-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 01, 2001 at 11:55:04AM -0700, Cy Schubert - ITSD Open Systems Group wrote: > In message <20010901134303.X81307@elvis.mu.org>, Alfred Perlstein > writes: > > Any AMD gurus in the house? > > > > Alfred Perlstein wrote: > > > > > > Using UDP is usually a bad idea, I would use tcp, I find that these > > > flags make for a decent mount point that's quite fast: > > > rw,tcp,intr,nfsv3,-w=32768,-r=32768 > > I'm far from being an amd guru, however I've been running > am-utils-6.0[79] on FreeBSD for the past few months. Am-utils >= 6.07 > does support rdirplus. If you want to try it yourself download a copy > of am-utils-6.09 Where is 6.09?? The latest on the am-utils ftp site is 6.0.7. > I can send you a patch that will > update some makefiles in the source tree to allow am-utils-6.09 to > compile. Unfortunatly your patch does not go any where near far enough. How well did you test the resulting Amd? Are you saying that all the changes in src/contrib/amd can be tossed? (cd /usr/src/contrib/amd && cvs -q diff -r amd_6_0_7) -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Sep 2 13:16:30 2001 Delivered-To: freebsd-arch@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id 9FF1C37B409; Sun, 2 Sep 2001 13:16:13 -0700 (PDT) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.11.5/8.11.5) with ESMTP id f82KFFo71687; Sun, 2 Sep 2001 16:15:17 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Message-Id: <200109022015.f82KFFo71687@aldan.algebra.com> Date: Sun, 2 Sep 2001 16:15:14 -0400 (EDT) From: Mikhail Teterin Subject: Re: proctitle progress reporting for dump(8) To: asmodai@wxs.nl Cc: current@freebsd.org, arch@freebsd.org In-Reply-To: <20010901194706.C33712@daemon.ninth-circle.org> MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-999461719=:969" Content-Transfer-Encoding: BINARY Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --0-1804289383-999461719=:969 Content-Type: TEXT/plain; charset=us-ascii Ok, attached is the patch addding a function, which sets the proctitle to the last output message and several calls to this function in places, where it looked useful to me. May be, I added too many, and/or skipped some... Note, that I intentially did not put this functionality into the msg() function itself -- not all messages need to be placed into the title. But a call to my new title(void) function can be placed whereever deemed useful. Only those, that can be followed by a long wait... The only tricks here are to replace the \n with the \0 in the lastmsg and to restore the title to the original before forking. The SIGINFO handling seemed to be as simple as: --- main.c 2001/07/09 03:06:56 1.26 +++ main.c 2001/09/02 19:58:21 @@ -274,2 +274,4 @@ + if (signal(SIGINFO, SIG_IGN) != SIG_IGN) + signal(SIGHUP, sig); if (signal(SIGHUP, SIG_IGN) != SIG_IGN) @@ -527,2 +536,5 @@ switch(signo) { + case SIGINFO: + timeest(); + break; case SIGALRM: But it just does not work :( I tried Ctrl-T and I tried killall -- no output, besides the usual: load: 0.11 cmd: dump 69089 [running] 0.00u 0.00s 0% 392k Any suggestions? Thanks! I'm only a ports committer, so if the proctitle patch is found acceptable (wow!) -- could someone please commit it? Or tell me to send-pr it... -mi --0-1804289383-999461719=:969 Content-Type: TEXT/plain; name=p-title Content-Description: let dump update its process title with the last output message Content-Disposition: attachment; filename=p-title Index: dump.h =================================================================== RCS file: /home/ncvs/src/sbin/dump/dump.h,v retrieving revision 1.9 diff -U1 -r1.9 dump.h --- dump.h 2001/08/10 23:12:10 1.9 +++ dump.h 2001/09/02 19:58:20 @@ -104,2 +104,3 @@ void timeest __P((void)); +void title __P((void)); time_t unctime __P((char *str)); Index: main.c =================================================================== RCS file: /home/ncvs/src/sbin/dump/main.c,v retrieving revision 1.26 diff -U1 -r1.26 main.c --- main.c 2001/07/09 03:06:56 1.26 +++ main.c 2001/09/02 19:58:21 @@ -332,2 +334,3 @@ } + title(); sync(); @@ -358,2 +361,3 @@ msg("mapping (Pass I) [regular files]\n"); + title(); anydirskipped = mapfiles(maxino, &tapesize); @@ -361,2 +365,3 @@ msg("mapping (Pass II) [directories]\n"); + title(); while (anydirskipped) { @@ -410,2 +415,3 @@ } + title(); @@ -423,2 +429,3 @@ msg("dumping (Pass III) [directories]\n"); + title(); dirty = 0; /* XXX just to get gcc to shut up */ @@ -441,2 +448,3 @@ msg("dumping (Pass IV) [regular files]\n"); + title(); for (map = dumpinomap, ino = 1; ino < maxino; ino++) { @@ -478,2 +486,3 @@ spcl.c_tapea / (tend_writing - tstart_writing)); + title(); @@ -536,2 +548,3 @@ msg("Rewriting attempted as response to unknown signal.\n"); + title(); (void)fflush(stderr); Index: optr.c =================================================================== RCS file: /home/ncvs/src/sbin/dump/optr.c,v retrieving revision 1.12 diff -U1 -r1.12 optr.c --- optr.c 2001/01/29 09:45:51 1.12 +++ optr.c 2001/09/02 19:58:21 @@ -203,2 +203,3 @@ + setproctitle(NULL); /* restore the proctitle modified by title() */ switch (pid = fork()) { @@ -305,2 +306,3 @@ deltat / 3600, (deltat % 3600) / 60); + title(); } @@ -333,2 +335,28 @@ va_end(ap); +} + +/* + * This function can be called to place, what msg() above pushed to + * stderr, into the process title, viewable with the ps-command. + * A side effect of this function, is it replaces the final '\n' (if any) + * with the '\0' in the global variable lastmsg -- to avoid the literal + * "\n" being put into the proctitle. + * So, if the lastmsg needs to be output elsewhere, that should happen + * before calling title(). + */ +void title() +{ + int lastlen; + + lastlen = strlen(lastmsg); + if (lastmsg[lastlen-1] == '\n') + lastmsg[lastlen-1] = '\0'; + + /* + * It would be unwise to run multiple dumps of same disk at + * same time. So ``disk'' is sufficient for identifying, to + * which family of dump processes this one belongs -- the + * other processes continue to have the original titles + */ + setproctitle("%s: %s", disk, lastmsg); } Index: tape.c =================================================================== RCS file: /home/ncvs/src/sbin/dump/tape.c,v retrieving revision 1.13 diff -U1 -r1.13 tape.c --- tape.c 2001/01/28 21:21:37 1.13 +++ tape.c 2001/09/02 19:58:22 @@ -533,2 +533,3 @@ */ + setproctitle(NULL); /* restore the proctitle modified by title() */ childpid = fork(); --0-1804289383-999461719=:969-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Sep 2 15:44:21 2001 Delivered-To: freebsd-arch@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 015EB37B405; Sun, 2 Sep 2001 15:43:59 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id PAA11091; Sun, 2 Sep 2001 15:43:58 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda11089; Sun Sep 2 15:43:58 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.6/8.9.1) id f82Mhvn05106; Sun, 2 Sep 2001 15:43:57 -0700 (PDT) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdgw5104; Sun Sep 2 15:43:23 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.6/8.9.1) id f82MhQt03149; Sun, 2 Sep 2001 15:43:26 -0700 (PDT) Message-Id: <200109022243.f82MhQt03149@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdNn3146; Sun Sep 2 15:43:10 2001 X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: obrien@FreeBSD.ORG Cc: Cy Schubert - ITSD Open Systems Group , Alfred Perlstein , John Polstra , arch@FreeBSD.ORG Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) In-reply-to: Your message of "Sun, 02 Sep 2001 12:21:25 PDT." <20010902122125.A80825@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Sep 2001 15:43:10 -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010902122125.A80825@hub.freebsd.org>, "David O'Brien" writes: > On Sat, Sep 01, 2001 at 11:55:04AM -0700, Cy Schubert - ITSD Open Systems Gro > up wrote: > > In message <20010901134303.X81307@elvis.mu.org>, Alfred Perlstein > > writes: > > > Any AMD gurus in the house? > > > > > > Alfred Perlstein wrote: > > > > > > > > Using UDP is usually a bad idea, I would use tcp, I find that these > > > > flags make for a decent mount point that's quite fast: > > > > rw,tcp,intr,nfsv3,-w=32768,-r=32768 > > > > I'm far from being an amd guru, however I've been running > > am-utils-6.0[79] on FreeBSD for the past few months. Am-utils >= 6.07 > > does support rdirplus. If you want to try it yourself download a copy > > of am-utils-6.09 > > Where is 6.09?? The latest on the am-utils ftp site is 6.0.7. I was mistaken. I've been running 6.0.5 and 6.0.7 since March on all of the FreeBSD systems I manage. I haven't looked at it since I last updated it back in March. You can't expect me to remember everything since then, which considering the events (sports injuries) since then is a virtual eternity in my life. (So much for excuses). :) > > > I can send you a patch that will > > update some makefiles in the source tree to allow am-utils-6.09 to > > compile. > > Unfortunatly your patch does not go any where near far enough. > How well did you test the resulting Amd? Are you saying that all the > changes in src/contrib/amd can be tossed? > (cd /usr/src/contrib/amd && cvs -q diff -r amd_6_0_7) I've been using the stock am-utils with the patch I sent you since March on all of the FreeBSD (12 + an unspecified number deployed at customer sites through a friend's ISP) systems I work on without any problems. Could I have used the existing patches? In some cases, maybe. In the spirit of trying to help as best I can, here is a version of my patch you can use when importing 6.0.7 into the FreeBSD CVS tree. It fixes all conflicts and compiles cleanly. --- usr.sbin/amd/include/config.h.orig Fri Nov 5 04:34:00 1999 +++ usr.sbin/amd/include/config.h Sun Sep 2 14:38:53 2001 @@ -1,13 +1,5 @@ -/* - * $FreeBSD: src/usr.sbin/amd/include/config.h,v 1.15 1999/11/05 12:34:00 obrien Exp $ - * - * portions derived from - * $NetBSD: config.h,v 1.11 1998/08/08 22:33:37 christos Exp $ - * - */ - /* config.h. Generated automatically by configure. */ -/* aux/config.h.in. Generated automatically from ./aux/configure.in by autoheader. */ +/* config.h.in. Generated automatically from configure.in by autoheader. */ /* * Start of am-utils-6.x config.h file. * Erez Zadok @@ -25,40 +17,40 @@ */ /* Define if have automount filesystem */ -#define HAVE_AM_FS_AUTO 1 +#define HAVE_AMU_FS_AUTO 1 /* Define if have direct automount filesystem */ -#define HAVE_AM_FS_DIRECT 1 +#define HAVE_AMU_FS_DIRECT 1 /* Define if have "top-level" filesystem */ -#define HAVE_AM_FS_TOPLVL 1 +#define HAVE_AMU_FS_TOPLVL 1 /* Define if have error filesystem */ -#define HAVE_AM_FS_ERROR 1 +#define HAVE_AMU_FS_ERROR 1 /* Define if have inheritance filesystem */ -#define HAVE_AM_FS_INHERIT 1 +#define HAVE_AMU_FS_INHERIT 1 /* Define if have program filesystem */ -#define HAVE_AM_FS_PROGRAM 1 +#define HAVE_AMU_FS_PROGRAM 1 /* Define if have symbolic-link filesystem */ -#define HAVE_AM_FS_LINK 1 +#define HAVE_AMU_FS_LINK 1 /* Define if have symlink with existence check filesystem */ -#define HAVE_AM_FS_LINKX 1 +#define HAVE_AMU_FS_LINKX 1 /* Define if have NFS host-tree filesystem */ -#define HAVE_AM_FS_HOST 1 +#define HAVE_AMU_FS_HOST 1 /* Define if have nfsl (NFS with local link check) filesystem */ -#define HAVE_AM_FS_NFSL 1 +#define HAVE_AMU_FS_NFSL 1 /* Define if have multi-NFS filesystem */ -#define HAVE_AM_FS_NFSX 1 +#define HAVE_AMU_FS_NFSX 1 /* Define if have union filesystem */ -#define HAVE_AM_FS_UNION 1 +#define HAVE_AMU_FS_UNION 1 /* @@ -142,13 +134,13 @@ /* #undef HAVE_FS_CACHEFS */ /* Define if have NULLFS (loopback on bsd44) filesystem */ -#define HAVE_FS_NULLFS 1 +#define HAVE_FS_NULLFS /* Define if have UNIONFS filesystem */ #define HAVE_FS_UNIONFS 1 /* Define if have UMAPFS (uid/gid mapping) filesystem */ -#define HAVE_FS_UMAPFS 1 +#define HAVE_FS_UMAPFS /* @@ -209,7 +201,7 @@ #define MOUNT_TYPE_UNIONFS "union" /* Mount(2) type/name for UMAPFS (uid/gid mapping) filesystem */ -#define MOUNT_TYPE_UMAPFS "umap" +/* #undef MOUNT_TYPE_UMAPFS */ /* @@ -438,6 +430,9 @@ /* Mount Table option string: max groups */ /* #undef MNTTAB_OPT_MAXGROUPS */ +/* Mount Table option string: support property lists (ACLs) */ +/* #undef MNTTAB_OPT_PROPLIST */ + /* * Generic mount(2) options (hex numbers) */ @@ -478,13 +473,13 @@ /* nocache (what?) */ /* #undef MNT2_GEN_OPT_NOCACHE */ -/* not a device */ +/* do not interpret special device files */ #define MNT2_GEN_OPT_NODEV 0x10 /* no exec calls allowed */ #define MNT2_GEN_OPT_NOEXEC 0x4 -/* not a device */ +/* do not interpret special device files */ /* #undef MNT2_GEN_OPT_NONDEV */ /* Disallow mounts beneath this mount */ @@ -496,6 +491,9 @@ /* Return ENAMETOOLONG for long filenames */ /* #undef MNT2_GEN_OPT_NOTRUNC */ +/* Pass mount option string to kernel */ +/* #undef MNT2_GEN_OPT_OPTIONSTR */ + /* allow overlay mounts */ /* #undef MNT2_GEN_OPT_OVERLAY */ @@ -575,6 +573,9 @@ /* allow interrupts on hard mount */ #define MNT2_NFS_OPT_INT 0x40 +/* allow interrupts on hard mount */ +/* #undef MNT2_NFS_OPT_INTR */ + /* Bits set internally */ /* #undef MNT2_NFS_OPT_INTERNAL */ @@ -620,6 +621,9 @@ /* Get lease for lookup */ /* #undef MNT2_NFS_OPT_NQLOOKLEASE */ +/* Don't use locking */ +/* #undef MNT2_NFS_OPT_NONLM */ + /* Use Nqnfs protocol */ #define MNT2_NFS_OPT_NQNFS 0x100 @@ -632,9 +636,18 @@ /* Do lookup with readdir (nqnfs) */ /* #undef MNT2_NFS_OPT_RDIRALOOK */ +/* allow property list operations (ACLs over NFS) */ +/* #undef MNT2_NFS_OPT_PROPLIST */ + +/* Use Readdirplus for NFSv3 */ +#define MNT2_NFS_OPTS_RDIRPLUS 0x10000 + /* set read ahead */ #define MNT2_NFS_OPT_READAHEAD 0x2000 +/* Set readdir size */ +#define MNT2_NFS_OPT_READDIRSIZE 0x20000 + /* Allocate a reserved port */ #define MNT2_NFS_OPT_RESVPORT 0x8000 @@ -668,6 +681,9 @@ /* use TCP for mounts */ /* #undef MNT2_NFS_OPT_TCP */ +/* linux NFSv3 */ +#define MNT2_NFS_OPT_VER3 0x200 + /* Wait for authentication */ /* #undef MNT2_NFS_OPT_WAITAUTH */ @@ -689,6 +705,9 @@ /* paging threshold */ /* #undef MNT2_NFS_OPT_PGTHRESH */ +/* 32<->64 dir cookie translation */ +/* #undef MNT2_NFS_OPT_XLATECOOKIE */ + /* * CDFS-specific mount(2) options (hex numbers) */ @@ -824,7 +843,7 @@ #define HAVE_FIELD_STRUCT_IFREQ_IFR_ADDR 1 /* does struct ifaddrs have field ifa_next? */ -/* #undef HAVE_FIELD_STRUCT_IFADDRS_IFA_NEXT */ +#define HAVE_FIELD_STRUCT_IFADDRS_IFA_NEXT 1 /* does struct sockaddr have field sa_len? */ #define HAVE_FIELD_STRUCT_SOCKADDR_SA_LEN 1 @@ -839,110 +858,9 @@ /* should signal handlers be reinstalled? */ /* #undef REINSTALL_SIGNAL_HANDLER */ - -/********************************************************************** ****/ -/*** Everything above this line is part of the "TOP" of acconfig.h. ***/ -/********************************************************************** ****/ - - -/* Define if on AIX 3. - System headers sometimes define this. - We just want to avoid a redefinition error message. */ -#ifndef _ALL_SOURCE -/* #undef _ALL_SOURCE */ -#endif - -/* Define if using alloca.c. */ -/* #undef C_ALLOCA */ - -/* Define to empty if the keyword does not work. */ -/* #undef const */ - -/* Define to one of _getb67, GETB67, getb67 for Cray-2 and Cray-YMP systems. - This function is required for alloca.c support on those systems. */ -/* #undef CRAY_STACKSEG_END */ - -/* Define to the type of elements in the array set by `getgroups'. - Usually this is either `int' or `gid_t'. */ -#define GETGROUPS_T gid_t - -/* Define to `int' if doesn't define. */ -/* #undef gid_t */ - -/* Define if you have alloca, as a function or macro. */ -#define HAVE_ALLOCA 1 - -/* Define if you have and it should be used (not on Ultrix). */ -/* #undef HAVE_ALLOCA_H */ - -/* Define if you support file names longer than 14 characters. */ -#define HAVE_LONG_FILE_NAMES 1 - -/* Define if system calls automatically restart after interruption - by a signal. */ -#define HAVE_RESTARTABLE_SYSCALLS 1 - -/* Define if your struct stat has st_rdev. */ -#define HAVE_ST_RDEV 1 - -/* Define if you have that is POSIX.1 compatible. */ -#define HAVE_SYS_WAIT_H 1 - -/* Define if you have . */ -/* #undef HAVE_VFORK_H */ - -/* Define if you have the wait3 system call. */ -#define HAVE_WAIT3 1 - -/* Define as __inline if that's what the C compiler calls it. */ -/* #undef inline */ - -/* Define if your C compiler doesn't accept -c and -o together. */ -/* #undef NO_MINUS_C_MINUS_O */ - -/* Define if you need to in order for stat and other things to work. */ -/* #undef _POSIX_SOURCE */ - -/* Define as the return type of signal handlers (int or void). */ -#define RETSIGTYPE void - -/* If using the C implementation of alloca, define if you know the - direction of stack growth for your system; otherwise it will be - automatically deduced at run-time. - STACK_DIRECTION > 0 => grows toward higher addresses - STACK_DIRECTION < 0 => grows toward lower addresses - STACK_DIRECTION = 0 => direction of growth unknown +/* + * More definitions that depend on configure options. */ -/* #undef STACK_DIRECTION */ - -/* Define if the `S_IS*' macros in do not work properly. */ -/* #undef STAT_MACROS_BROKEN */ - -/* Define if you have the ANSI C header files. */ -#define STDC_HEADERS 1 - -/* Define if you can safely include both and . */ -#define TIME_WITH_SYS_TIME 1 - -/* Define if your declares struct tm. */ -/* #undef TM_IN_SYS_TIME */ - -/* Define to `int' if doesn't define. */ -/* #undef uid_t */ - -/* Define vfork as fork if vfork does not work. */ -/* #undef vfork */ - -/* Define if your processor stores words with the most significant - byte first (like Motorola and SPARC, unlike Intel and VAX). */ -/* #undef WORDS_BIGENDIAN */ -#include -#if BYTE_ORDER == BIG_ENDIAN -#define WORDS_BIGENDIAN -#endif - -/* Define if lex declares yytext as a char * by default, not a char[]. */ -#define YYTEXT_POINTER 1 /* Turn off general debugging by default */ /* #undef DEBUG */ @@ -950,18 +868,15 @@ /* Turn off memory debugging by default */ /* #undef DEBUG_MEM */ -/* Enable "amq -M" remote mount code (insecure due to IP spoofing) */ -/* #undef ENABLE_AMQ_MOUNT */ - /* Define package name (must be defined by configure.in) */ #define PACKAGE "am-utils" -/* Define version of package (must be defined by configure.in) */ -#define VERSION "6.0.3s1" - /* We [FREEBSD-NATIVE] pick some parameters from our local config file */ #include "config_local.h" +/* Define version of package (must be defined by configure.in) */ +#define VERSION "6.0.7" + /* Define name of host machine's cpu (eg. sparc) */ /* #define HOST_CPU "i386" */ @@ -995,6 +910,9 @@ /* what type of network transport type is in use? TLI or sockets? */ /* #undef HAVE_TRANSPORT_TYPE_TLI */ +/* Define to `long' if doesn't define time_t */ +/* #undef time_t */ + /* Define to "void *" if compiler can handle, otherwise "char *" */ #define voidp void * @@ -1002,7 +920,10 @@ #define am_nfs_fh nfs_fh /* Define a type/structure for an NFS V3 filehandle */ -#define am_nfs_fh3 nfs_fh3 +#define am_nfs_fh3 nfs_fh3_freebsd3 + +/* define if the host has NFS protocol headers in system headers */ +/* #undef HAVE_NFS_PROT_HEADERS */ /* define name of am-utils' NFS protocol header */ #define AMU_NFS_PROTOCOL_HEADER "./conf/nfs_prot/nfs_prot_freebsd3.h" @@ -1034,9 +955,6 @@ /* Define if have struct nfs_args in one of the standard nfs headers */ #define HAVE_STRUCT_NFS_ARGS 1 -/* Define if have struct nfs_mount_data in one of the standard nfs headers */ -/* #undef HAVE_STRUCT_NFS_MOUNT_DATA */ - /* Define if have struct nfs_gfs_mount in one of the standard nfs headers */ /* #undef HAVE_STRUCT_NFS_GFS_MOUNT */ @@ -1099,6 +1017,112 @@ /* define if must NOT use NFS "noconn" option */ #define USE_CONNECTED_NFS_SOCKETS 1 +/********************************************************************** ****/ +/*** Everything above this line is part of the "TOP" of acconfig.h. ***/ +/********************************************************************** ****/ + + +/* Define if on AIX 3. + System headers sometimes define this. + We just want to avoid a redefinition error message. */ +#ifndef _ALL_SOURCE +/* #undef _ALL_SOURCE */ +#endif + +/* Define if using alloca.c. */ +/* #undef C_ALLOCA */ + +/* Define to empty if the keyword does not work. */ +/* #undef const */ + +/* Define to one of _getb67, GETB67, getb67 for Cray-2 and Cray-YMP systems. + This function is required for alloca.c support on those systems. */ +/* #undef CRAY_STACKSEG_END */ + +/* Define to the type of elements in the array set by `getgroups'. + Usually this is either `int' or `gid_t'. */ +#define GETGROUPS_T gid_t + +/* Define to `int' if doesn't define. */ +/* #undef gid_t */ + +/* Define if you have alloca, as a function or macro. */ +#define HAVE_ALLOCA 1 + +/* Define if you have and it should be used (not on Ultrix). */ +/* #undef HAVE_ALLOCA_H */ + +/* Define if you support file names longer than 14 characters. */ +#define HAVE_LONG_FILE_NAMES 1 + +/* Define if system calls automatically restart after interruption + by a signal. */ +#define HAVE_RESTARTABLE_SYSCALLS 1 + +/* Define if you have that is POSIX.1 compatible. */ +#define HAVE_SYS_WAIT_H 1 + +/* Define if you have . */ +/* #undef HAVE_VFORK_H */ + +/* Define if you have the wait3 system call. */ +#define HAVE_WAIT3 1 + +/* Define as __inline if that's what the C compiler calls it. */ +/* #undef inline */ + +/* Define to `int' if doesn't define. */ +/* #undef mode_t */ + +/* Define if your C compiler doesn't accept -c and -o together. */ +/* #undef NO_MINUS_C_MINUS_O */ + +/* Define to `int' if doesn't define. */ +/* #undef pid_t */ + +/* Define if you need to in order for stat and other things to work. */ +/* #undef _POSIX_SOURCE */ + +/* Define as the return type of signal handlers (int or void). */ +#define RETSIGTYPE void + +/* Define to `unsigned' if doesn't define. */ +/* #undef size_t */ + +/* If using the C implementation of alloca, define if you know the + direction of stack growth for your system; otherwise it will be + automatically deduced at run-time. + STACK_DIRECTION > 0 => grows toward higher addresses + STACK_DIRECTION < 0 => grows toward lower addresses + STACK_DIRECTION = 0 => direction of growth unknown + */ +/* #undef STACK_DIRECTION */ + +/* Define if the `S_IS*' macros in do not work properly. */ +/* #undef STAT_MACROS_BROKEN */ + +/* Define if you have the ANSI C header files. */ +#define STDC_HEADERS 1 + +/* Define if you can safely include both and . */ +#define TIME_WITH_SYS_TIME 1 + +/* Define if your declares struct tm. */ +/* #undef TM_IN_SYS_TIME */ + +/* Define to `int' if doesn't define. */ +/* #undef uid_t */ + +/* Define vfork as fork if vfork does not work. */ +/* #undef vfork */ + +/* Define if your processor stores words with the most significant + byte first (like Motorola and SPARC, unlike Intel and VAX). */ +/* #undef WORDS_BIGENDIAN */ + +/* Define if lex declares yytext as a char * by default, not a char[]. */ +#define YYTEXT_POINTER 1 + /* Define if you have the __seterr_reply function. */ /* #undef HAVE___SETERR_REPLY */ @@ -1126,6 +1150,9 @@ /* Define if you have the clnt_sperrno function. */ #define HAVE_CLNT_SPERRNO 1 +/* Define if you have the clock_gettime function. */ +#define HAVE_CLOCK_GETTIME 1 + /* Define if you have the cnodeid function. */ /* #undef HAVE_CNODEID */ @@ -1163,7 +1190,7 @@ #define HAVE_GETHOSTNAME 1 /* Define if you have the getifaddrs function. */ -/* #undef HAVE_GETIFADDRS */ +#define HAVE_GETIFADDRS 1 /* Define if you have the getmntinfo function. */ #define HAVE_GETMNTINFO 1 @@ -1253,7 +1280,7 @@ #define HAVE_SETITIMER 1 /* Define if you have the setresuid function. */ -/* #undef HAVE_SETRESUID */ +#define HAVE_SETRESUID 1 /* Define if you have the setsid function. */ #define HAVE_SETSID 1 @@ -1520,7 +1547,7 @@ /* #undef HAVE_HSFS_HSFS_H */ /* Define if you have the header file. */ -/* #undef HAVE_IFADDRS_H */ +#define HAVE_IFADDRS_H 1 /* Define if you have the header file. */ /* #undef HAVE_IRS_H */ @@ -1535,7 +1562,7 @@ /* #undef HAVE_LDAP_H */ /* Define if you have the header file. */ -/* #undef HAVE_LIBGEN_H */ +#define HAVE_LIBGEN_H 1 /* Define if you have the header file. */ /* #undef HAVE_LINUX_AUTO_FS_H */ @@ -1543,6 +1570,12 @@ /* Define if you have the header file. */ /* #undef HAVE_LINUX_FS_H */ +/* Define if you have the header file. */ +/* #undef HAVE_LINUX_KDEV_T_H */ + +/* Define if you have the header file. */ +/* #undef HAVE_LINUX_LIST_H */ + /* Define if you have the header file. */ /* #undef HAVE_LINUX_NFS_H */ @@ -1886,7 +1919,7 @@ #define HAVE_UFS_UFS_UFSMOUNT_H 1 /* Define if you have the header file. */ -#define HAVE_UFS_UFS_MOUNT_H 1 +/* #undef HAVE_UFS_UFS_MOUNT_H */ /* Define if you have the header file. */ #define HAVE_UNISTD_H 1 @@ -1894,9 +1927,6 @@ /* Define if you have the header file. */ #define HAVE_VARARGS_H 1 -/* Define if you have the header file. */ -/* #undef HAVE_VFORK_H */ - /* Define if you have the gdbm library (-lgdbm). */ /* #undef HAVE_LIBGDBM */ @@ -1915,20 +1945,14 @@ /* Define if you have the rpcsvc library (-lrpcsvc). */ #define HAVE_LIBRPCSVC 1 -/* Define to `int' if does not define. */ -/* #undef pid_t */ +/* Define if you have the rt library (-lrt). */ +/* #undef HAVE_LIBRT */ -/* Define to `int' if does not define. */ -/* #undef mode_t */ - -/* Define to `int' if does not define. */ -/* #undef pid_t */ - -/* Define to `unsigned' if does not define. */ -/* #undef size_t */ +/* Name of package */ +#define PACKAGE "am-utils" -/* Define to `long' if does not define. */ -/* #undef time_t */ +/* Version number of package */ +#define VERSION "6.0.7" /********************************************************************** ****/ Please don't take this note as inflammatory. I do not mean to ruffle any feathers or to insult anyone. I am trying to help as best I can. If I have offended anyone with any of my comments I apologise. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD Ministry of Management Services Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Sep 2 19: 8:48 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 03EA537B407 for ; Sun, 2 Sep 2001 19:08:46 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f8328iX12979; Sun, 2 Sep 2001 20:08:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f8328hh22382; Sun, 2 Sep 2001 20:08:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109030208.f8328hh22382@harmony.village.org> To: Kris Kennaway Subject: Re: cvs commit: src/share/mk sys.mk Cc: arch@FreeBSD.ORG In-reply-to: Your message of "Fri, 31 Aug 2001 13:16:27 PDT." <20010831131627.A86427@xor.obsecurity.org> References: <20010831131627.A86427@xor.obsecurity.org> <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> Date: Sun, 02 Sep 2001 20:08:43 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010831131627.A86427@xor.obsecurity.org> Kris Kennaway writes: : I couldn't figure out how to do this without adding in .include : "../Makefile.inc" on a couple hundred directories to tie them into one : big tree so they all have an include path back to /usr/src/world.conf : or whatever you want to call it. Having the file only read by make : world isn't really acceptible because building parts of the source : tree is a common developer activity and needs to use the same file. I've invested about 50 hours at work trying to figure this out. I wound up using Makefile.up (in place of Makefile.inc) and that one could easily find the top of the tree. It works well in our small tree at work, but I don't think that it would work well in FreeBSD's tree. We also have a symbolic link for all the various copies of Makefile.up in the repo... If there's an easier way to deal, then I'd love to know :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Sep 2 19:11:16 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id A790B37B401 for ; Sun, 2 Sep 2001 19:11:13 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f832BCX12989; Sun, 2 Sep 2001 20:11:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f832BCh22404; Sun, 2 Sep 2001 20:11:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109030211.f832BCh22404@harmony.village.org> To: Kris Kennaway Subject: Re: cvs commit: src/share/mk sys.mk Cc: arch@FreeBSD.ORG In-reply-to: Your message of "Fri, 31 Aug 2001 13:16:27 PDT." <20010831131627.A86427@xor.obsecurity.org> References: <20010831131627.A86427@xor.obsecurity.org> <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> Date: Sun, 02 Sep 2001 20:11:12 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Actually, now that I think about this, I think that it would be *EASY* to support in make. .include-up "conf/world.conf" and make would look in ., .., ../.., etc until it finds conf/world.conf. It would then set some variable so conf/world.conf would know where the top of the tree was (which would make things in the tree a little easier). Of course, this also requires changing all Makefiles in the tree, but that's easy to do. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Sep 2 19:47:55 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B8F6537B401; Sun, 2 Sep 2001 19:47:53 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.5/8.11.5) with SMTP id f832lhP36719; Sun, 2 Sep 2001 22:47:43 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 2 Sep 2001 22:47:43 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "David O'Brien" Cc: Cy Schubert - ITSD Open Systems Group , Alfred Perlstein , John Polstra , arch@FreeBSD.ORG Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) In-Reply-To: <20010901182608.A51464@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 1 Sep 2001, David O'Brien wrote: > am-utils until recently[*] did not properly configure and build on a > FreeBSD host. I had offers from the am-utils maintainer to fix this if > given an account on a reference box. FreeBSD Core has shown their > inability to follow thru and make this happen. Thus I have refused to > update src/contrib/amd for quite sometime. As I told you in person at USENIX, core@ approved an account for Erez. You need to send appropriate information to admins@ so that his account can be created. Jordan has also offered to create a third party developer box using one of the usw machines, which I think is a great idea, and hope he follows through on sometime. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Sep 2 19:54: 6 2001 Delivered-To: freebsd-arch@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 1B5D837B401; Sun, 2 Sep 2001 19:54:03 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f832rfT88084; Sun, 2 Sep 2001 19:53:56 -0700 (PDT) (envelope-from jkh@freebsd.org) To: rwatson@freebsd.org Cc: obrien@freebsd.org, Cy.Schubert@uumail.gov.bc.ca, bright@mu.org, jdp@polstra.com, arch@freebsd.org Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) In-Reply-To: References: <20010901182608.A51464@dragon.nuxi.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010902195341S.jkh@freebsd.org> Date: Sun, 02 Sep 2001 19:53:41 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 37 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG We (unfurl and I) are right now fixing up usw7 for general habitation. Hopefully it will be finished soon, though it's certainly not helping that my connectivity to usw* is lighthousing like mad and getting a connection to stay up for more than 5 minutes is a real challenge... As to Erez, I must confess to having no recollection whatsoever of him or his request for an account. Does anyone else in core remember this or am I the only one with advanced alzheimers around here? :) - Jordan From: Robert Watson Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) Date: Sun, 2 Sep 2001 22:47:43 -0400 (EDT) > > On Sat, 1 Sep 2001, David O'Brien wrote: > > > am-utils until recently[*] did not properly configure and build on a > > FreeBSD host. I had offers from the am-utils maintainer to fix this if > > given an account on a reference box. FreeBSD Core has shown their > > inability to follow thru and make this happen. Thus I have refused to > > update src/contrib/amd for quite sometime. > > As I told you in person at USENIX, core@ approved an account for Erez. > You need to send appropriate information to admins@ so that his account > can be created. Jordan has also offered to create a third party developer > box using one of the usw machines, which I think is a great idea, and hope > he follows through on sometime. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sun Sep 2 23: 7:38 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (discworld.nanolink.com [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id 188CF37B401 for ; Sun, 2 Sep 2001 23:07:34 -0700 (PDT) Received: (qmail 73229 invoked by uid 1000); 3 Sep 2001 06:04:50 -0000 Date: Mon, 3 Sep 2001 09:04:50 +0300 From: Peter Pentchev To: Warner Losh Cc: Kris Kennaway , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903090450.C72833@ringworld.oblivion.bg> Mail-Followup-To: Warner Losh , Kris Kennaway , arch@FreeBSD.ORG References: <20010831131627.A86427@xor.obsecurity.org> <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831131627.A86427@xor.obsecurity.org> <200109030211.f832BCh22404@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109030211.f832BCh22404@harmony.village.org>; from imp@harmony.village.org on Sun, Sep 02, 2001 at 08:11:12PM -0600 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 02, 2001 at 08:11:12PM -0600, Warner Losh wrote: > Actually, now that I think about this, I think that it would be *EASY* > to support in make. > > .include-up "conf/world.conf" > > and make would look in ., .., ../.., etc until it finds > conf/world.conf. It would then set some variable so conf/world.conf > would know where the top of the tree was (which would make things in > the tree a little easier). > > Of course, this also requires changing all Makefiles in the tree, but > that's easy to do. And then neither make(1), nor the other bootstrap tools could use it, since that would break an upgrade path :( Other than that, this sounds like a great idea. G'luck, Peter -- What would this sentence be like if pi were 3? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 0:22:24 2001 Delivered-To: freebsd-arch@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id A3FCC37B401; Mon, 3 Sep 2001 00:22:14 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f837L2N52557; Mon, 3 Sep 2001 10:21:02 +0300 (EEST) (envelope-from ru) Date: Mon, 3 Sep 2001 10:21:02 +0300 From: Ruslan Ermilov To: Kris Kennaway Cc: Alexander Langer , "David O'Brien" , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903102102.A49997@sunbay.com> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831131627.A86427@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010831131627.A86427@xor.obsecurity.org>; from kris@obsecurity.org on Fri, Aug 31, 2001 at 01:16:27PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 31, 2001 at 01:16:27PM -0700, Kris Kennaway wrote: > On Fri, Aug 31, 2001 at 07:39:47PM +0200, Alexander Langer wrote: > > > - Teach /usr/src/Makefile's $(MAKE) variable about a world.conf file > > which is included for /usr/src builds. This needs extensive testing. > > I couldn't figure out how to do this without adding in .include > "../Makefile.inc" on a couple hundred directories to tie them into one > big tree so they all have an include path back to /usr/src/world.conf > or whatever you want to call it. Having the file only read by make > world isn't really acceptible because building parts of the source > tree is a common developer activity and needs to use the same file. > Include world.conf from sys.mk. That way, it will be read before make(1) even reads the ${.CURDIR}/Makefile. This is documented in the manpage. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 0:29:35 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 75B9637B403; Mon, 3 Sep 2001 00:29:31 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.5/8.11.1) id f837TR142379; Mon, 3 Sep 2001 00:29:27 -0700 (PDT) (envelope-from obrien) Date: Mon, 3 Sep 2001 00:29:26 -0700 From: "David O'Brien" To: Ruslan Ermilov Cc: Kris Kennaway , Alexander Langer , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903002926.A42260@dragon.nuxi.com> Reply-To: alpha@FreeBSD.ORG References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831131627.A86427@xor.obsecurity.org> <20010903102102.A49997@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010903102102.A49997@sunbay.com>; from ru@FreeBSD.ORG on Mon, Sep 03, 2001 at 10:21:02AM +0300 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 03, 2001 at 10:21:02AM +0300, Ruslan Ermilov wrote: > > > - Teach /usr/src/Makefile's $(MAKE) variable about a world.conf file > > > which is included for /usr/src builds. This needs extensive testing. > > > > I couldn't figure out how to do this without adding in .include > > "../Makefile.inc" on a couple hundred directories to tie them into one > > big tree so they all have an include path back to /usr/src/world.conf > > or whatever you want to call it. Having the file only read by make > > world isn't really acceptible because building parts of the source > > tree is a common developer activity and needs to use the same file. > > > Include world.conf from sys.mk. That way, it will be read before make(1) > even reads the ${.CURDIR}/Makefile. This is documented in the manpage. Uh, and how would a world.conf then be an improvement over make.conf? -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 1:15:40 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 1F4D137B405 for ; Mon, 3 Sep 2001 01:15:35 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f838FUX13818; Mon, 3 Sep 2001 02:15:30 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f838FTh24586; Mon, 3 Sep 2001 02:15:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109030815.f838FTh24586@harmony.village.org> To: Peter Pentchev Subject: Re: cvs commit: src/share/mk sys.mk Cc: Kris Kennaway , arch@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Sep 2001 09:04:50 +0300." <20010903090450.C72833@ringworld.oblivion.bg> References: <20010903090450.C72833@ringworld.oblivion.bg> <20010831131627.A86427@xor.obsecurity.org> <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831131627.A86427@xor.obsecurity.org> <200109030211.f832BCh22404@harmony.village.org> Date: Mon, 03 Sep 2001 02:15:29 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010903090450.C72833@ringworld.oblivion.bg> Peter Pentchev writes: : On Sun, Sep 02, 2001 at 08:11:12PM -0600, Warner Losh wrote: : > Actually, now that I think about this, I think that it would be *EASY* : > to support in make. : > : > .include-up "conf/world.conf" : > : > and make would look in ., .., ../.., etc until it finds : > conf/world.conf. It would then set some variable so conf/world.conf : > would know where the top of the tree was (which would make things in : > the tree a little easier). : > : > Of course, this also requires changing all Makefiles in the tree, but : > that's easy to do. : : And then neither make(1), nor the other bootstrap tools could use it, : since that would break an upgrade path :( : : Other than that, this sounds like a great idea. Actaully, only MAKE would be affected. We build make the first thing and then use that make for the rest of the build process. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 2:42:16 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id A961F37B407; Mon, 3 Sep 2001 02:42:09 -0700 (PDT) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id LAA23899; Mon, 3 Sep 2001 11:42:08 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f839gGM27037; Mon, 3 Sep 2001 11:42:16 +0200 (CEST) (envelope-from alex) Date: Mon, 3 Sep 2001 11:42:14 +0200 From: Alexander Langer To: alpha@FreeBSD.ORG Cc: Ruslan Ermilov , Kris Kennaway , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903114214.A27026@fump.kawo2.rwth-aachen.de> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831131627.A86427@xor.obsecurity.org> <20010903102102.A49997@sunbay.com> <20010903002926.A42260@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010903002926.A42260@dragon.nuxi.com>; from dev-null@NUXI.com on Mon, Sep 03, 2001 at 12:29:26AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake David O'Brien (dev-null@NUXI.com): > > Include world.conf from sys.mk. That way, it will be read before make(1) > > even reads the ${.CURDIR}/Makefile. This is documented in the manpage. > Uh, and how would a world.conf then be an improvement over make.conf? It's at least seperated. :-) (no real improvement). But if there was a way to determine from sys.mk, if we are building world or parts of the world (I just don't know yet, how this could be done), we could include world.conf from sys.mk only in this case. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 3:14:45 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (Postfix) with ESMTP id A90BC37B40E for ; Mon, 3 Sep 2001 03:14:42 -0700 (PDT) Received: from symnt3.Cadence.COM (symnt3.Cadence.COM [194.32.101.100]) by mailgate.Cadence.COM (8.9.3/8.9.3) with ESMTP id DAA00170; Mon, 3 Sep 2001 03:14:32 -0700 (PDT) Received: from pc598cam (pc598-cam.cadence.com [194.32.96.198]) by symnt3.Cadence.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id SACH5MLK; Mon, 3 Sep 2001 11:13:29 +0100 Message-ID: <005401c13461$37b78290$c66020c2@pc598cam> From: "Duncan Barclay" To: "Warner Losh" Cc: References: <20010831131627.A86427@xor.obsecurity.org> <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200109030211.f832BCh22404@harmony.village.org> Subject: Re: cvs commit: src/share/mk sys.mk Date: Mon, 3 Sep 2001 11:13:55 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Received: By mailgate.Cadence.COM as DAA00170 at Mon Sep 3 03:14:32 2001 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This can be done in make already but you do need code stuff in a Makefile.inc to support it: http://www.ragnet.demon.co.uk/RM/RM.makefile This walks up a tree until it finds a toplevel. ----- Original Message ----- From: "Warner Losh" To: "Kris Kennaway" Cc: Sent: Monday, September 03, 2001 3:11 AM Subject: Re: cvs commit: src/share/mk sys.mk > Actually, now that I think about this, I think that it would be *EASY* > to support in make. > > .include-up "conf/world.conf" > > and make would look in ., .., ../.., etc until it finds > conf/world.conf. It would then set some variable so conf/world.conf > would know where the top of the tree was (which would make things in > the tree a little easier). > > Of course, this also requires changing all Makefiles in the tree, but > that's easy to do. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 9: 5:48 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 445F337B40A for ; Mon, 3 Sep 2001 09:05:45 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f83G5hX15147; Mon, 3 Sep 2001 10:05:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f83G5gh26417; Mon, 3 Sep 2001 10:05:43 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109031605.f83G5gh26417@harmony.village.org> To: "Duncan Barclay" Subject: Re: cvs commit: src/share/mk sys.mk Cc: arch@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Sep 2001 11:13:55 BST." <005401c13461$37b78290$c66020c2@pc598cam> References: <005401c13461$37b78290$c66020c2@pc598cam> <20010831131627.A86427@xor.obsecurity.org> <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200109030211.f832BCh22404@harmony.village.org> Date: Mon, 03 Sep 2001 10:05:42 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <005401c13461$37b78290$c66020c2@pc598cam> "Duncan Barclay" writes: : This can be done in make already but you do need code stuff in a : Makefile.inc to support it: : http://www.ragnet.demon.co.uk/RM/RM.makefile : This walks up a tree until it finds a toplevel. I don't want to code every Makefile.inc in the tree to do that. I do that at work right now and it is a huge pita... Why not take it to the next level and support it more directly. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 10:41:59 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 34B7A37B405 for ; Mon, 3 Sep 2001 10:41:43 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.4/8.11.4) with ESMTP id f83Hfg600706; Mon, 3 Sep 2001 10:41:42 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.11.6/8.11.3) id f83Hfff01002; Mon, 3 Sep 2001 10:41:41 -0700 (PDT) (envelope-from marcel) Date: Mon, 3 Sep 2001 10:41:41 -0700 From: Marcel Moolenaar To: Duncan Barclay Cc: Warner Losh , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903104141.E554@dhcp01.pn.xcllnt.net> References: <20010831131627.A86427@xor.obsecurity.org> <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200109030211.f832BCh22404@harmony.village.org> <005401c13461$37b78290$c66020c2@pc598cam> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005401c13461$37b78290$c66020c2@pc598cam> User-Agent: Mutt/1.3.21i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 03, 2001 at 11:13:55AM +0100, Duncan Barclay wrote: > This can be done in make already but you do need code stuff in a > Makefile.inc to support it: > http://www.ragnet.demon.co.uk/RM/RM.makefile > This walks up a tree until it finds a toplevel. Why not revert the problem. Instead of having a source tree find it's own root and pull in configuration files, why not have the user specify roots by means of a "searchpath". This concept is extensible by specify which config file to pull in depending on the search path. The top-level makefile can define the searchpath for it knows the root (obviously) so that it doesn't impact people who only build from the toplevel. Developers building directly in subdirectories need to define the "searchpath" themselves. There's is a one-time inconvenience for people who need to setup their searchpath, but it avoids the NxM-time inconvenience of having every makefile try to find the root of the tree for every build that is initiated. The whole idea of finding one's root sounds too costly. Just a thought... > ----- Original Message ----- > From: "Warner Losh" > To: "Kris Kennaway" > Cc: > Sent: Monday, September 03, 2001 3:11 AM > Subject: Re: cvs commit: src/share/mk sys.mk > > > > Actually, now that I think about this, I think that it would be *EASY* > > to support in make. > > > > .include-up "conf/world.conf" > > > > and make would look in ., .., ../.., etc until it finds > > conf/world.conf. It would then set some variable so conf/world.conf > > would know where the top of the tree was (which would make things in > > the tree a little easier). > > > > Of course, this also requires changing all Makefiles in the tree, but > > that's easy to do. > > > > Warner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-arch" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 10:46:18 2001 Delivered-To: freebsd-arch@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 169F637B40B for ; Mon, 3 Sep 2001 10:46:16 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f83Hjkh65993; Mon, 3 Sep 2001 12:45:46 -0500 (CDT) (envelope-from jlemon) Date: Mon, 3 Sep 2001 12:45:46 -0500 From: Jonathan Lemon To: Marcel Moolenaar Cc: Duncan Barclay , Warner Losh , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903124546.B64607@prism.flugsvamp.com> References: <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200109030211.f832BCh22404@harmony.village.org> <005401c13461$37b78290$c66020c2@pc598cam> <20010903104141.E554@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20010903104141.E554@dhcp01.pn.xcllnt.net> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 03, 2001 at 10:41:41AM -0700, Marcel Moolenaar wrote: > On Mon, Sep 03, 2001 at 11:13:55AM +0100, Duncan Barclay wrote: > > This can be done in make already but you do need code stuff in a > > Makefile.inc to support it: > > http://www.ragnet.demon.co.uk/RM/RM.makefile > > This walks up a tree until it finds a toplevel. > > Why not revert the problem. Instead of having a source tree find > it's own root and pull in configuration files, why not have the > user specify roots by means of a "searchpath". This concept is > extensible by specify which config file to pull in depending on > the search path. The top-level makefile can define the searchpath > for it knows the root (obviously) so that it doesn't impact people > who only build from the toplevel. Developers building directly in > subdirectories need to define the "searchpath" themselves. I don't particularly like this; I would prefer that things are self contained. Having the developer specify a searchpath themselves is error prone, especially when dealing with multiple source trees. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 11: 8:40 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id CE01F37B403 for ; Mon, 3 Sep 2001 11:08:32 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.4/8.11.4) with ESMTP id f83I8W600808; Mon, 3 Sep 2001 11:08:32 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.11.6/8.11.3) id f83I8WR01153; Mon, 3 Sep 2001 11:08:32 -0700 (PDT) (envelope-from marcel) Date: Mon, 3 Sep 2001 11:08:32 -0700 From: Marcel Moolenaar To: Jonathan Lemon Cc: Duncan Barclay , Warner Losh , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903110832.F554@dhcp01.pn.xcllnt.net> References: <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200109030211.f832BCh22404@harmony.village.org> <005401c13461$37b78290$c66020c2@pc598cam> <20010903104141.E554@dhcp01.pn.xcllnt.net> <20010903124546.B64607@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010903124546.B64607@prism.flugsvamp.com> User-Agent: Mutt/1.3.21i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 03, 2001 at 12:45:46PM -0500, Jonathan Lemon wrote: > > > > Why not revert the problem. Instead of having a source tree find > > it's own root and pull in configuration files, why not have the > > user specify roots by means of a "searchpath". This concept is > > extensible by specify which config file to pull in depending on > > the search path. The top-level makefile can define the searchpath > > for it knows the root (obviously) so that it doesn't impact people > > who only build from the toplevel. Developers building directly in > > subdirectories need to define the "searchpath" themselves. > > I don't particularly like this; I would prefer that things are > self contained. Having the developer specify a searchpath themselves > is error prone, especially when dealing with multiple source trees. I agree with this when you depend on it for proper functioning. In this case it's just for configuration options, right? Also, putting configuration options in the source tree makes it hard, and in cases impossible, to share the source tree between machines. Lastly, working with "searchpaths" makes it easier for the developer to experiment with different options. You only have to start each build with a different "searchpath" and it allows you to run the builds concurrently. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 14:17:24 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id E349337B40B for ; Mon, 3 Sep 2001 14:17:21 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f83LHKX15974; Mon, 3 Sep 2001 15:17:20 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f83LHJh28175; Mon, 3 Sep 2001 15:17:19 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109032117.f83LHJh28175@harmony.village.org> To: Jonathan Lemon Subject: Re: cvs commit: src/share/mk sys.mk Cc: Marcel Moolenaar , Duncan Barclay , arch@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Sep 2001 12:45:46 CDT." <20010903124546.B64607@prism.flugsvamp.com> References: <20010903124546.B64607@prism.flugsvamp.com> <200108311118.f7VBIO124920@freefall.freebsd.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200109030211.f832BCh22404@harmony.village.org> <005401c13461$37b78290$c66020c2@pc598cam> <20010903104141.E554@dhcp01.pn.xcllnt.net> Date: Mon, 03 Sep 2001 15:17:19 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : I don't particularly like this; I would prefer that things are : self contained. Having the developer specify a searchpath themselves : is error prone, especially when dealing with multiple source trees. I agree. I've tried the searchpath solution before, and it has exactly the problem that Jonathan describes. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 14:19:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-54.dsl.lsan03.pacbell.net [63.207.60.54]) by hub.freebsd.org (Postfix) with ESMTP id EC49137B40C for ; Mon, 3 Sep 2001 14:19:21 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8A33066D0A; Mon, 3 Sep 2001 14:19:21 -0700 (PDT) Date: Mon, 3 Sep 2001 14:19:21 -0700 From: Kris Kennaway To: Warner Losh Cc: Peter Pentchev , Kris Kennaway , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903141921.A36886@xor.obsecurity.org> References: <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831131627.A86427@xor.obsecurity.org> <200109030211.f832BCh22404@harmony.village.org> <20010903090450.C72833@ringworld.oblivion.bg> <200109030815.f838FTh24586@harmony.village.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109030815.f838FTh24586@harmony.village.org>; from imp@harmony.village.org on Mon, Sep 03, 2001 at 02:15:29AM -0600 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 03, 2001 at 02:15:29AM -0600, Warner Losh wrote: > : And then neither make(1), nor the other bootstrap tools could use it, > : since that would break an upgrade path :( > :=20 > : Other than that, this sounds like a great idea. >=20 > Actaully, only MAKE would be affected. We build make the first thing > and then use that make for the rest of the build process. Are you sure? I ran into this when doing CPUTYPE and my recollection is that it isn't. Kris --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7k/PZWry0BWjoQKURAhETAKChGDBLgDgPJ8FbGYDVYRcZS8geHQCeJNeE Dqhq9S+LCsqAQ7aBB5kHvnI= =tZ5q -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 14:21:18 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 60DA737B40C for ; Mon, 3 Sep 2001 14:21:15 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f83LLEX16017; Mon, 3 Sep 2001 15:21:14 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f83LLDh28282; Mon, 3 Sep 2001 15:21:13 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109032121.f83LLDh28282@harmony.village.org> To: Kris Kennaway Subject: Re: cvs commit: src/share/mk sys.mk Cc: Peter Pentchev , arch@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Sep 2001 14:19:21 PDT." <20010903141921.A36886@xor.obsecurity.org> References: <20010903141921.A36886@xor.obsecurity.org> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <20010831131627.A86427@xor.obsecurity.org> <200109030211.f832BCh22404@harmony.village.org> <20010903090450.C72833@ringworld.oblivion.bg> <200109030815.f838FTh24586@harmony.village.org> Date: Mon, 03 Sep 2001 15:21:13 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010903141921.A36886@xor.obsecurity.org> Kris Kennaway writes: : > Actaully, only MAKE would be affected. We build make the first thing : > and then use that make for the rest of the build process. : : Are you sure? I ran into this when doing CPUTYPE and my recollection : is that it isn't. At one point, this was definitely the case, but maybe things have changed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 17:36:21 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id D204D37B40B; Mon, 3 Sep 2001 17:36:13 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f840gRn03534; Mon, 3 Sep 2001 17:42:30 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109040042.f840gRn03534@mass.dis.org> To: Jordan Hubbard Cc: arch@freebsd.org Subject: Re: AMD defaults? (was: Re: Tuning UDP for NFS) In-Reply-To: Message from Jordan Hubbard of "Sun, 02 Sep 2001 19:53:41 PDT." <20010902195341S.jkh@freebsd.org> Date: Mon, 03 Sep 2001 17:42:27 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > As to Erez, I must confess to having no recollection whatsoever of him > or his request for an account. Does anyone else in core remember this > or am I the only one with advanced alzheimers around here? :) Check the minutes. 8) But as Robert has observed, David is the real Alzheimers' case here; he was told at Usenix that Erez' account had been approved. I suspect that David's subsequent worryload had simply buried the fact. For general reference, since people are likely to be interested, the delay within -core over approving another "external developer" account was related to lengthy discussion over the risks and tradeoffs related to the entire "external developer" model. There are a number of distinct opinions within core, and concerns regarding the security of the repository are likely to drive some more changes in the future. Regardless, we still need to provide external developers with resources, thus Erez was approved. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 17:46:36 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id 3366737B405 for ; Mon, 3 Sep 2001 17:46:27 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.4/8.11.4) with ESMTP id f840kNA00359; Mon, 3 Sep 2001 17:46:23 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.11.6/8.11.3) id f840kMq03318; Mon, 3 Sep 2001 17:46:22 -0700 (PDT) (envelope-from marcel) Date: Mon, 3 Sep 2001 17:46:22 -0700 From: Marcel Moolenaar To: Warner Losh Cc: Jonathan Lemon , Duncan Barclay , arch@FreeBSD.ORG Subject: Re: cvs commit: src/share/mk sys.mk Message-ID: <20010903174621.A3146@dhcp01.pn.xcllnt.net> References: <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200109030211.f832BCh22404@harmony.village.org> <005401c13461$37b78290$c66020c2@pc598cam> <20010903104141.E554@dhcp01.pn.xcllnt.net> <200109032117.f83LHJh28175@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200109032117.f83LHJh28175@harmony.village.org> User-Agent: Mutt/1.3.21i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 03, 2001 at 03:17:19PM -0600, Warner Losh wrote: > : I don't particularly like this; I would prefer that things are > : self contained. Having the developer specify a searchpath themselves > : is error prone, especially when dealing with multiple source trees. > > I agree. I've tried the searchpath solution before, and it has > exactly the problem that Jonathan describes. I don't have the experience, so I'm going to assume that it is error prone, but I don't want to abandon it completely. Me, stubborn? :-) Suggestion: We treat build-options as policy. We provide the mechanics to allow people to set options (ie implement policy), but we do not hardcode how. Instead we define a generic "interface". Something like the following (forget the names, I'm making this up while I type): The make variable POLICY_FILE, when defined, holds the filename of a makefile fragment to include. The intend is that the fragment defines whatever needs to be defined to (partly) implement the policy. The make variable POLICY_FILE_LOCATE, when defined, holds the name of a script to run in case POLICY_FILE is undefined. The script can select the makefile fragment in anyway it wants, based on any condition it needs. The POLICY_FILE variable, once set, avoids any expensive work in locating or determining the include file. It's passed down while recursing. Users can define it on the commandline or it can be synthesized automaticly. We basicly don't care what the value is and how it's been set. If POLICY_FILE is not defined, but POLICY_FILE_LOCATE is defined, make(1) will run the script and assigns the output to POLICY_FILE. Thus, the script is only run once and we basicly don't care what the script does. It may be an expensive operation, because we only run it once at build invocation. The script is assumed to be the same for all source trees, but it's output can differ depending on whatever it needs to depend. Everybody can implement build options the way they want it and thus fits the idea that /usr/share/mk is for everybody to use. We can provide one or more "sample" implementations for people's convenience. Thoughts? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 17:50:39 2001 Delivered-To: freebsd-arch@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CF3F737B406 for ; Mon, 3 Sep 2001 17:50:34 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f840oTX16496; Mon, 3 Sep 2001 18:50:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f840oSh29477; Mon, 3 Sep 2001 18:50:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200109040050.f840oSh29477@harmony.village.org> To: Marcel Moolenaar Subject: Re: cvs commit: src/share/mk sys.mk Cc: Jonathan Lemon , Duncan Barclay , arch@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 Sep 2001 17:46:22 PDT." <20010903174621.A3146@dhcp01.pn.xcllnt.net> References: <20010903174621.A3146@dhcp01.pn.xcllnt.net> <20010831142958.A60910@sunbay.com> <20010831141746.A1809@zerogravity.kawo2.rwth-aachen.d> <20010831084811.B95710@dragon.nuxi.com> <20010831184945.A16872@fump.kawo2.rwth-aachen.de> <20010831100216.A17397@dragon.nuxi.com> <20010831193947.A17086@fump.kawo2.rwth-aachen.de> <200109030211.f832BCh22404@harmony.village.org> <005401c13461$37b78290$c66020c2@pc598cam> <20010903104141.E554@dhcp01.pn.xcllnt.net> <200109032117.f83LHJh28175@harmony.village.org> Date: Mon, 03 Sep 2001 18:50:28 -0600 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010903174621.A3146@dhcp01.pn.xcllnt.net> Marcel Moolenaar writes: : Thoughts? Hmmm, I think I might like it. I'll have to think about that. However, I'll note that your suggestion and mine aren't mutually exclusive. :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 23: 3:41 2001 Delivered-To: freebsd-arch@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 6674C37B403; Mon, 3 Sep 2001 23:03:36 -0700 (PDT) Received: from mindspring.com (dialup-209.247.140.38.Dial1.SanJose1.Level3.net [209.247.140.38]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA22702; Mon, 3 Sep 2001 23:03:30 -0700 (PDT) Message-ID: <3B946EDE.616F7EDC@mindspring.com> Date: Mon, 03 Sep 2001 23:04:14 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: Yar Tikhiy , arch@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: brk(2) manpage seems erroneous and confusing References: <20010901204223.K1753-100000@besplex.bde.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bruce Evans wrote: > > I'd suggest taking the brk(2) page from NetBSD, which language > > looks much better. If noone minds, I'll do that. Of course, I'll > > change the function prototypes in the manpage to match our unistd.h > > unless we decide to fix the latter, too. > > Better change unistd.h. The kernel returns int. Ugh. sizeof(int) != sizeof(void *) everywhere... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 23:17:44 2001 Delivered-To: freebsd-arch@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 3E9D037B408; Mon, 3 Sep 2001 23:17:39 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id F21B781D05; Tue, 4 Sep 2001 01:17:33 -0500 (CDT) Date: Tue, 4 Sep 2001 01:17:33 -0500 From: Alfred Perlstein To: Terry Lambert Cc: Bruce Evans , Yar Tikhiy , arch@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: brk(2) manpage seems erroneous and confusing Message-ID: <20010904011733.V81307@elvis.mu.org> References: <20010901204223.K1753-100000@besplex.bde.org> <3B946EDE.616F7EDC@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B946EDE.616F7EDC@mindspring.com>; from tlambert2@mindspring.com on Mon, Sep 03, 2001 at 11:04:14PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Terry Lambert [010904 01:04] wrote: > Bruce Evans wrote: > > > I'd suggest taking the brk(2) page from NetBSD, which language > > > looks much better. If noone minds, I'll do that. Of course, I'll > > > change the function prototypes in the manpage to match our unistd.h > > > unless we decide to fix the latter, too. > > > > Better change unistd.h. The kernel returns int. > > Ugh. sizeof(int) != sizeof(void *) everywhere... Oy, well, we can fuzz it by having a newbrk or something that takes a void ** argument and trick it out in libc. Anyone think that's a good idea? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' '"Java" developer, like "special" Olympics, right?' - Bill Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Mon Sep 3 23:28:53 2001 Delivered-To: freebsd-arch@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 7B8A737B407; Mon, 3 Sep 2001 23:28:48 -0700 (PDT) Received: from mindspring.com (dialup-209.247.140.38.Dial1.SanJose1.Level3.net [209.247.140.38]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA15274; Mon, 3 Sep 2001 23:28:22 -0700 (PDT) Message-ID: <3B9474B1.18EC6692@mindspring.com> Date: Mon, 03 Sep 2001 23:29:05 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mikhail Teterin Cc: asmodai@wxs.nl, current@freebsd.org, arch@freebsd.org Subject: Re: proctitle progress reporting for dump(8) References: <200109012258.f81MwAo84783@aldan.algebra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > On 1 Sep, Jeroen Ruigrok/Asmodai wrote: > > -On [20010901 19:00], Mikhail Teterin (mi@aldan.algebra.com) wrote: > >>79240 ?? S 0:06,85 dump: /dev/da0h(0): 92.44% done, finished > >>in 0:43 (dump) > > > > > Looks nice. Would definately be an improvement. > > > > I would like it. How often does it update the proctitle? > > Whenever it outputs a line to the stderr -- I personally find no > regularity in that :(. SIGINFO handling is a different thing, though. > I'll look at that too. Thanks, It would be nice to have in a SIGINFO handler as well, but since your application is dump run by Amanda as a background process, a SIGINFO is not very useful, unless it was being suggested that the setproctitle() be called from a SIGINFO handler? I'm pretty sure that this would not be a valid thing to do; SIGINFO itself is also problematic, since if you redirect output to a file, etc., you'd really need to call fflush() in the signal handler, which is not supposed to be done, as it is not one of the permitted calls. Also, printf() allocates memory for floating point, so if that percentage is a floating point calculation, then you are in double trouble, since you are not allowed to call malloc() in a signal handler. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Sep 4 8:46:11 2001 Delivered-To: freebsd-arch@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 1FEC137B401; Tue, 4 Sep 2001 08:45:55 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f84FiXU08347; Tue, 4 Sep 2001 18:44:33 +0300 (EEST) (envelope-from ru) Date: Tue, 4 Sep 2001 18:44:33 +0300 From: Ruslan Ermilov To: Mikhail Teterin Cc: asmodai@wxs.nl, current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: proctitle progress reporting for dump(8) Message-ID: <20010904184433.C1669@sunbay.com> References: <20010901194706.C33712@daemon.ninth-circle.org> <200109022015.f82KFFo71687@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109022015.f82KFFo71687@aldan.algebra.com>; from mi@aldan.algebra.com on Sun, Sep 02, 2001 at 04:15:14PM -0400 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 02, 2001 at 04:15:14PM -0400, Mikhail Teterin wrote: [...] > The SIGINFO handling seemed to be as simple as: > --- main.c 2001/07/09 03:06:56 1.26 > +++ main.c 2001/09/02 19:58:21 > @@ -274,2 +274,4 @@ > > + if (signal(SIGINFO, SIG_IGN) != SIG_IGN) > + signal(SIGHUP, sig); ^^^^^^ that should be SIGINFO. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Sep 4 10: 3:55 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 3535837B401 for ; Tue, 4 Sep 2001 10:03:50 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.5/8.11.5) with SMTP id f84H3hP56149 for ; Tue, 4 Sep 2001 13:03:43 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 4 Sep 2001 13:03:43 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: arch@FreeBSD.org Subject: ucred -> cred, cr_[ug]id Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Earlier this year, I merged the 'pcred' and 'ucred' structures into a single 'ucred' structure, recognizing that in practice our use of pcred and ucred was such that the costs of the change were low, but the clarity associated with the change was relatively high. This simplified things from a variety of perspective, including reference counting and synchronization. This is a change also performed on a number of other UNIX platforms, including Solaris and IRIX. However, on those platforms, the single structure is called 'cred' and not 'ucred'. As such, I'd like to propose that we do the following: o Replace all references to struct ucred with struct cred o Repo-copy src/sys/ucred.h to src/sys/cred.h I don't feel all that strongly about this change, but do think it would make sense given the use of the structure, and the evolution of other platforms making similar classes of changes. On a similar note, when I merged ucred and pcred, I maintained cr_uid as the effective uid: other platforms typically stick an 'e' in front to get cr_euid, making it consistent with other variables in the structure. If I were to make the 'cred' change, I'd also improve consistency by adding the 'e' to the effective uid and gid structures. Any strong reasons not to do this? Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Sep 4 10: 7:10 2001 Delivered-To: freebsd-arch@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 95D9437B403; Tue, 4 Sep 2001 10:07:08 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f84H78592607; Tue, 4 Sep 2001 10:07:08 -0700 (PDT) (envelope-from dillon) Date: Tue, 4 Sep 2001 10:07:08 -0700 (PDT) From: Matt Dillon Message-Id: <200109041707.f84H78592607@earth.backplane.com> To: Robert Watson Cc: arch@FreeBSD.ORG Subject: Re: ucred -> cred, cr_[ug]id References: Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Earlier this year, I merged the 'pcred' and 'ucred' structures into a :single 'ucred' structure, recognizing that in practice our use of pcred :and ucred was such that the costs of the change were low, but the clarity :associated with the change was relatively high. This simplified things :from a variety of perspective, including reference counting and :synchronization. This is a change also performed on a number of other :UNIX platforms, including Solaris and IRIX. However, on those platforms, :the single structure is called 'cred' and not 'ucred'. As such, I'd like :to propose that we do the following: : :o Replace all references to struct ucred with struct cred :o Repo-copy src/sys/ucred.h to src/sys/cred.h : :I don't feel all that strongly about this change, but do think it would :make sense given the use of the structure, and the evolution of other :platforms making similar classes of changes. : :On a similar note, when I merged ucred and pcred, I maintained cr_uid as :the effective uid: other platforms typically stick an 'e' in front to get :cr_euid, making it consistent with other variables in the structure. If I :were to make the 'cred' change, I'd also improve consistency by adding the :'e' to the effective uid and gid structures. : :Any strong reasons not to do this? : :Robert N M Watson FreeBSD Core Team, TrustedBSD Project :robert@fledge.watson.org NAI Labs, Safeport Network Services This sounds like a good idea to me. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Sep 4 11:50:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id EA35A37B401; Tue, 4 Sep 2001 11:50:08 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 013E081D01; Tue, 4 Sep 2001 13:50:08 -0500 (CDT) Date: Tue, 4 Sep 2001 13:50:08 -0500 From: Alfred Perlstein To: Robert Watson Cc: arch@FreeBSD.org Subject: Re: ucred -> cred, cr_[ug]id Message-ID: <20010904135008.Z81307@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.org on Tue, Sep 04, 2001 at 01:03:43PM -0400 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Robert Watson [010904 12:03] wrote: > > Earlier this year, I merged the 'pcred' and 'ucred' structures into a > single 'ucred' structure, recognizing that in practice our use of pcred > and ucred was such that the costs of the change were low, but the clarity > associated with the change was relatively high. This simplified things > from a variety of perspective, including reference counting and > synchronization. This is a change also performed on a number of other > UNIX platforms, including Solaris and IRIX. However, on those platforms, > the single structure is called 'cred' and not 'ucred'. As such, I'd like > to propose that we do the following: > > o Replace all references to struct ucred with struct cred > o Repo-copy src/sys/ucred.h to src/sys/cred.h > > I don't feel all that strongly about this change, but do think it would > make sense given the use of the structure, and the evolution of other > platforms making similar classes of changes. > > On a similar note, when I merged ucred and pcred, I maintained cr_uid as > the effective uid: other platforms typically stick an 'e' in front to get > cr_euid, making it consistent with other variables in the structure. If I > were to make the 'cred' change, I'd also improve consistency by adding the > 'e' to the effective uid and gid structures. > > Any strong reasons not to do this? I like how you've merged it into one structure, kudos on doing that, however I really must object to another wholesale massive commit for asthetic/stylistic reasons just to rename a structure. Please keep it as ucred, at least until KSE is done, ideally I'd like to see the changeover (ucred -> cred) happen a couple of weeks before we actually release 5.0 to reduce the maintaince factor on deltas not yet committed. thanks, -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' '"Java" developer, like "special" Olympics, right?' - Bill Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Sep 4 11:52:46 2001 Delivered-To: freebsd-arch@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id C32B537B425; Tue, 4 Sep 2001 11:52:37 -0700 (PDT) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.11.5/8.11.5) with ESMTP id f84Ipfo55193; Tue, 4 Sep 2001 14:51:42 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Message-Id: <200109041851.f84Ipfo55193@aldan.algebra.com> Date: Tue, 4 Sep 2001 14:51:38 -0400 (EDT) From: Mikhail Teterin Subject: Re: proctitle progress reporting for dump(8) To: tlambert2@mindspring.com Cc: asmodai@wxs.nl, current@freebsd.org, arch@freebsd.org In-Reply-To: <3B9474B1.18EC6692@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 3 Sep, Terry Lambert wrote: >> > >> > I would like it. How often does it update the proctitle? >> >> Whenever it outputs a line to the stderr -- I personally find no >> regularity in that :(. SIGINFO handling is a different thing, though. >> I'll look at that too. Thanks, > It would be nice to have in a SIGINFO handler as well, but since your > application is dump run by Amanda as a background process, a > SIGINFO is not very useful, unless it was being suggested that the > setproctitle() be called from a SIGINFO handler? Yes that's what is being suggested. The output line will be the same, so no dump-output-parsing scripts should break (including Amanda's). Please, read the patches. > I'm pretty sure that this would not be a valid thing to do; Mmm, why? > SIGINFO itself is also problematic, since if you redirect output to a > file, etc., you'd really need to call fflush() Why? The line will eventually be saved without an explicit fflush(), but the proctitle will be set immediately... Besides, in case of dump, it is the stderr, that has no buffering, AFAIK :) > Also, printf() allocates memory for floating point, so if that > percentage is a floating point calculation, then you are in double > trouble, since you are not allowed to call malloc() in a signal > handler. That's interesting... I can modify it a bit, to round the percentage to fit the %d if called as a signal handler. Thanks. Anything else? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Tue Sep 4 13:32:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B65CF37B408 for ; Tue, 4 Sep 2001 13:32:09 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.5/8.11.5) with SMTP id f84KW3P57822 for ; Tue, 4 Sep 2001 16:32:03 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 4 Sep 2001 16:32:02 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-arch@FreeBSD.org Subject: discrepancies between /etc/defaults/rc.conf and sysinstall Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Currently, there are some differences between the defaults specified in /etc/defaults/rc.conf and those set in rc.conf under sysinstall. This is probably counter-intuitive, and should be fixed. The place where I primarily noticed the difference was with regards to settings for sendmail--my recommendation would be that if changes are made to /etc/defaults/rc.conf, they be propagated to sysinstall shortly there-after. This might mean placing a note in defaults/rc.conf to remind developers making changes to do that. If no one else syncs up settings in the next few days, I'll probably get around to it sometime next week--this message is more intended as a reminder :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Sep 5 0:59: 1 2001 Delivered-To: freebsd-arch@freebsd.org Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 05EC637B403; Wed, 5 Sep 2001 00:58:57 -0700 (PDT) Received: from mindspring.com (dialup-209.245.138.192.Dial1.SanJose1.Level3.net [209.245.138.192]) by swan.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA03365; Wed, 5 Sep 2001 00:58:30 -0700 (PDT) Message-ID: <3B95DB53.13AE8B42@mindspring.com> Date: Wed, 05 Sep 2001 00:59:15 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mikhail Teterin Cc: asmodai@wxs.nl, current@freebsd.org, arch@freebsd.org Subject: Re: proctitle progress reporting for dump(8) References: <200109041851.f84Ipfo55193@aldan.algebra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > > Also, printf() allocates memory for floating point, so if that > > percentage is a floating point calculation, then you are in double > > trouble, since you are not allowed to call malloc() in a signal > > handler. > > That's interesting... I can modify it a bit, to round the percentage to > fit the %d if called as a signal handler. Thanks. Anything else? If setproctitle() calls malloc/strsave/etc., it is not safe to call in a signal handler. I'm not saying it does, I'm saying I haven't looked at the code in libc for the function, and you should, before using it in a signal handler... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Sep 5 3:33:23 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 637E837B408; Wed, 5 Sep 2001 03:33:15 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA27348; Wed, 5 Sep 2001 20:33:02 +1000 Date: Wed, 5 Sep 2001 20:32:35 +1000 (EST) From: Bruce Evans X-X-Sender: To: Terry Lambert Cc: Mikhail Teterin , , , Subject: Re: proctitle progress reporting for dump(8) In-Reply-To: <3B95DB53.13AE8B42@mindspring.com> Message-ID: <20010905201754.U22592-100000@alphplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 5 Sep 2001, Terry Lambert wrote: > Mikhail Teterin wrote: > > > Also, printf() allocates memory for floating point, so if that > > > percentage is a floating point calculation, then you are in double > > > trouble, since you are not allowed to call malloc() in a signal > > > handler. > > > > That's interesting... I can modify it a bit, to round the percentage to > > fit the %d if called as a signal handler. Thanks. Anything else? > > If setproctitle() calls malloc/strsave/etc., it is not safe > to call in a signal handler. Neither is setproctitle() (since it is not in the list of functions that are safe to call in a signal handler), so this is moot. > I'm not saying it does, I'm saying I haven't looked at the > code in libc for the function, and you should, before using > it in a signal handler... setproctitle() directly calls the following functions that are not safe to call in a signal handler (since they are not in the magic list). snprintf, strlen, vsnprintf, sysctl, sysctlbyname I think all of these are safe in practice. It also accesses some variables that are not safe to access in a signal handler (non-auto ones that are not of type "volatile sig_atomic_t" or are accessed by reads). This is unsafe in practice. E.g., concurrent calls to setproctitle() might corrupt the state of the ps_strings variable. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Sep 5 6:23: 2 2001 Delivered-To: freebsd-arch@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id 1DAAF37B408; Wed, 5 Sep 2001 06:22:49 -0700 (PDT) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.11.5/8.11.5) with ESMTP id f85DLSo63141; Wed, 5 Sep 2001 09:21:32 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Message-Id: <200109051321.f85DLSo63141@aldan.algebra.com> Date: Wed, 5 Sep 2001 09:21:25 -0400 (EDT) From: Mikhail Teterin Subject: Re: proctitle progress reporting for dump(8) To: bde@zeta.org.au Cc: tlambert2@mindspring.com, asmodai@wxs.nl, current@FreeBSD.ORG, arch@FreeBSD.ORG In-Reply-To: <20010905201754.U22592-100000@alphplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 5 Sep, Bruce Evans wrote: > snprintf, strlen, vsnprintf, sysctl, sysctlbyname > > I think all of these are safe in practice. > > It also accesses some variables that are not safe to access in > a signal handler (non-auto ones that are not of type "volatile > sig_atomic_t" or are accessed by reads). This is unsafe in practice. > E.g., concurrent calls to setproctitle() might corrupt the state of > the ps_strings variable. Mmm, I don't know what those strings are used for -- what's the worst, that could happen here -- corrupted PS output, or worse? In any case, it seems, like a simple lock -- a static variable in the signal handler would work: static signal_handling; ... if (signal_handling) return; if (signal) signal_handling = 1; ... signal_handling = 0; Or is this not safe enough -- race of both signal handlers checking for the signal_handling at the same time? What would be the right way to do this generally? Thanks. In this particular case, timeest is called fairly often, but simply returns if not enough time elapsed since last report. I can make the signal handler set the flag, which will make timeest report things the next time it is called, even if 5 minutes did not elapse. This way, signal handler will only deal with a variable assignment -- all of the reporting (including proctitle update) will happen shortly afterwards -- on a normal stack. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Sep 5 17:32:54 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 6322F37B409 for ; Wed, 5 Sep 2001 17:32:51 -0700 (PDT) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id CAA10178 for ; Thu, 6 Sep 2001 02:32:50 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 77D4714B0E; Thu, 6 Sep 2001 02:32:48 +0200 (CEST) Date: Thu, 6 Sep 2001 02:32:47 +0200 From: Alexander Langer To: arch@FreeBSD.org Subject: libh src/ import Message-ID: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! How are peoples feelings about an import of libh into our src tree, in order to push the development? The past has shown that many people are actually interested in libh once they hear about it, but most people just don't know about it. For those of you, who still don't know: http://people.FreeBSD.org/~alex/libh/ (WWW) http://people.FreeBSD.org/~alex/libh/libh-2001-09-06.tar.gz (CVS snap) I do believe that libh will only benefit from this, and so will FreeBSD. Note that libh is still under heavy development, but we can easily bring it to production quality until 5.0-RELEASE (thank god for the shift!) I like to see it in src/release/, next to picoBSD and the release-notes. They all require, so does "make release", software from the ports collection in order to build. Every committer is encouraged to help with libh, of course. Thanks Alex PS: The name "libh" is a development name. It will be changed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Sep 5 18:50:15 2001 Delivered-To: freebsd-arch@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 387AD37B401 for ; Wed, 5 Sep 2001 18:50:13 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 421ED81D05; Wed, 5 Sep 2001 20:50:08 -0500 (CDT) Date: Wed, 5 Sep 2001 20:50:08 -0500 From: Alfred Perlstein To: Alexander Langer Cc: arch@FreeBSD.org Subject: Re: libh src/ import Message-ID: <20010905205008.Q81307@elvis.mu.org> References: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d>; from alex@big.endian.de on Thu, Sep 06, 2001 at 02:32:47AM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Alexander Langer [010905 19:33] wrote: > Hi! > > How are peoples feelings about an import of libh into our src tree, > in order to push the development? Yes, please do it. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Sep 5 19: 3:11 2001 Delivered-To: freebsd-arch@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 505B237B405 for ; Wed, 5 Sep 2001 19:03:09 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f8623SZ91775; Wed, 5 Sep 2001 21:03:28 -0500 (CDT) (envelope-from jlemon) Date: Wed, 5 Sep 2001 21:03:28 -0500 From: Jonathan Lemon To: Alexander Langer Cc: arch@FreeBSD.ORG Subject: Re: libh src/ import Message-ID: <20010905210328.B91111@prism.flugsvamp.com> References: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Sep 06, 2001 at 02:32:47AM +0200, Alexander Langer wrote: > Hi! > > How are peoples feelings about an import of libh into our src tree, > in order to push the development? As long as it goes somwehere under src/contrib please. I don't think this is appropriate to put in src/release. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Wed Sep 5 23:43:15 2001 Delivered-To: freebsd-arch@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id F004737B401 for ; Wed, 5 Sep 2001 23:43:08 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f866fpT30832; Wed, 5 Sep 2001 23:41:54 -0700 (PDT) (envelope-from jkh@freebsd.org) To: jlemon@flugsvamp.com Cc: alex@big.endian.de, arch@freebsd.org Subject: Re: libh src/ import In-Reply-To: <20010905210328.B91111@prism.flugsvamp.com> References: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> <20010905210328.B91111@prism.flugsvamp.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010905234151J.jkh@freebsd.org> Date: Wed, 05 Sep 2001 23:41:51 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 23 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What's wrong with src/release? src/contrib is generally for "3rd party" software such as gdb or tcpdump. libh was developed entirely within the FreeBSD project and is only really applicable to release management. - Jordan From: Jonathan Lemon Subject: Re: libh src/ import Date: Wed, 5 Sep 2001 21:03:28 -0500 > On Thu, Sep 06, 2001 at 02:32:47AM +0200, Alexander Langer wrote: > > Hi! > > > > How are peoples feelings about an import of libh into our src tree, > > in order to push the development? > > As long as it goes somwehere under src/contrib please. I don't think > this is appropriate to put in src/release. > -- > Jonathan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 9: 8:37 2001 Delivered-To: freebsd-arch@freebsd.org Received: from enigma.jaded.net (enigma.jaded.net [216.94.132.9]) by hub.freebsd.org (Postfix) with ESMTP id DC35B37B405 for ; Thu, 6 Sep 2001 09:08:32 -0700 (PDT) Received: from spirit.jaded.net (unknown [24.141.6.76]) by enigma.jaded.net (Postfix) with ESMTP id 09E8F66B09 for ; Thu, 6 Sep 2001 12:08:32 -0400 (EDT) Received: (from dan@localhost) by spirit.jaded.net (8.11.6/8.11.4) id f86G7kQ09858 for arch@freebsd.org; Thu, 6 Sep 2001 12:07:46 -0400 (EDT) (envelope-from dan) Date: Thu, 6 Sep 2001 12:06:25 -0400 From: Dan Moschuk To: arch@freebsd.org Subject: [arun@sharmas.dhs.org: POSIX compatibility issue] Message-ID: <20010906120625.C9605@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can anyone see a reason why this shouldn't be commited? ----- Forwarded message from Arun Sharma ----- Date: Wed, 5 Sep 2001 23:22:38 -0700 From: Arun Sharma To: FreeBSD Hackers Subject: POSIX compatibility issue Can someone take a look at this PR ? http://www.freebsd.org/cgi/query-pr.cgi?pr=30317 It's necessary to fix compilation issues for a POSIX compliant Java VM, that uses sockets. There are similar open bug reports against NetBSD too, without any comments on why this change can not be made. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message ----- End forwarded message ----- -- There is nothing wrong with Southern California that a rise in the ocean level wouldn't cure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 11:21:54 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 983CE37B401; Thu, 6 Sep 2001 11:21:51 -0700 (PDT) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id UAA22170; Thu, 6 Sep 2001 20:21:51 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id E686314B0E; Thu, 6 Sep 2001 20:21:51 +0200 (CEST) Date: Thu, 6 Sep 2001 20:21:51 +0200 From: Alexander Langer To: Dan Moschuk Cc: arch@FreeBSD.ORG Subject: Re: [arun@sharmas.dhs.org: POSIX compatibility issue] Message-ID: <20010906202151.A4070@zerogravity.kawo2.rwth-aachen.d> References: <20010906120625.C9605@spirit.jaded.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010906120625.C9605@spirit.jaded.net>; from dan@FreeBSD.ORG on Thu, Sep 06, 2001 at 12:06:25PM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Dan Moschuk (dan@FreeBSD.ORG): > Can anyone see a reason why this shouldn't be commited? If POSIX doesn't allow u_* types, sys/socket.h has to be fixed, and not sys/types.h. Anyone with POSIX specs should look up, how the datatypes in socket.h should be defined. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 12: 5:47 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 6845837B401 for ; Thu, 6 Sep 2001 12:05:44 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id MAA06462; Thu, 6 Sep 2001 12:05:40 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> Date: Thu, 06 Sep 2001 12:05:37 -0700 (PDT) From: John Baldwin To: Alexander Langer Subject: RE: libh src/ import Cc: arch@FreeBSD.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 06-Sep-01 Alexander Langer wrote: > Hi! > > How are peoples feelings about an import of libh into our src tree, > in order to push the development? As I said on IRC in an opinion that no one else seems to share, libh is useful in a wider regard than just FreeBSD, and I think it should be a separate project that gets vendor imported into src/contrib. Let's face it guys, FreeBSD doesn't have a lot of GUI people running around, and if libh is going to fly, it needs developers. IMHO, the best way to get developers for it is to not make it look like some FreeBSD-only thing, but instead to make it inviting to other developers. To that end, I think libh really belongs on Sourceforge as its own project, and something that goes in src/contrib along with Turbo Vision and Tcl when the time comes for it to replace sysinstall and hte package system. If it is imported directly into the tree and not into src/contrib, then it shouldn't go in src/release. Sysinstall didn't belong there, and no other code does either. It's a utility not only for installation, but also post-install configuration, thus the libs would need to be in src/lib/ and the binaries in src/usr.sbin or wherever. src/release would be the absolute worst place to put it. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 13:53: 4 2001 Delivered-To: freebsd-arch@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-54.dsl.lsan03.pacbell.net [63.207.60.54]) by hub.freebsd.org (Postfix) with ESMTP id 1AF3C37B405; Thu, 6 Sep 2001 13:53:00 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BC69E66D0A; Thu, 6 Sep 2001 13:52:59 -0700 (PDT) Date: Thu, 6 Sep 2001 13:52:59 -0700 From: Kris Kennaway To: Jordan Hubbard Cc: jlemon@flugsvamp.com, alex@big.endian.de, arch@freebsd.org Subject: Re: libh src/ import Message-ID: <20010906135259.C18784@xor.obsecurity.org> References: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> <20010905210328.B91111@prism.flugsvamp.com> <20010905234151J.jkh@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="2/5bycvrmDh4d1IB" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010905234151J.jkh@freebsd.org>; from jkh@freebsd.org on Wed, Sep 05, 2001 at 11:41:51PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2/5bycvrmDh4d1IB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Sep 05, 2001 at 11:41:51PM -0700, Jordan Hubbard wrote: > What's wrong with src/release? src/contrib is generally for "3rd party" > software such as gdb or tcpdump. libh was developed entirely within the > FreeBSD project and is only really applicable to release management. Perhaps I don't know enough about what libh does (I thought it was a GUI library), but is it really beyond the realms of possibility that someone might want to use this for another purpose than the installer? Kris --2/5bycvrmDh4d1IB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7l+IrWry0BWjoQKURAjfmAKDpk5bFE2njNnHur3EMtyNDoaV0TwCcDji5 xGlr9s/8KP/QEgfT4z6qn4E= =Y0JT -----END PGP SIGNATURE----- --2/5bycvrmDh4d1IB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 14:11:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id E52CC37B408; Thu, 6 Sep 2001 14:11:21 -0700 (PDT) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id XAA30107; Thu, 6 Sep 2001 23:11:18 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 5EE7814B4E; Thu, 6 Sep 2001 23:11:18 +0200 (CEST) Date: Thu, 6 Sep 2001 23:11:17 +0200 From: Alexander Langer To: Kris Kennaway Cc: Jordan Hubbard , jlemon@flugsvamp.com, arch@FreeBSD.ORG Subject: Re: libh src/ import Message-ID: <20010906231117.A1435@zerogravity.kawo2.rwth-aachen.d> References: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> <20010905210328.B91111@prism.flugsvamp.com> <20010905234151J.jkh@freebsd.org> <20010906135259.C18784@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="x+6KMIRAuhnl3hBn" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010906135259.C18784@xor.obsecurity.org>; from kris@obsecurity.org on Thu, Sep 06, 2001 at 01:52:59PM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --x+6KMIRAuhnl3hBn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Thus spake Kris Kennaway (kris@obsecurity.org): > Perhaps I don't know enough about what libh does (I thought it was a > GUI library), but is it really beyond the realms of possibility that > someone might want to use this for another purpose than the installer? Yes, replacing dialog(1) calls in the ports tree for example. Alex --x+6KMIRAuhnl3hBn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iQEVAwUBO5fmdLRIIUSeqRcRAQEbuAgAriG4CPipukJmXPh40CbY1xsDhBcVenR3 cClmGLivDI56d90xWQpyG1vvrMSWFMR4oAHUVLOB8vl+Y/SowQk/JabVumW5oVHa 8vwfow2CmDU+ig6a3VLDVWvaXCgDtdBwsGR6SUvqJaatXsudqdiMl11GNMrJSVsm Z/7c5I/sMLHj551igie1hX5xGdo0R2R61WW5K0rNNhTl8+rTBhO5YVR52oYNf24u pU+ghDce8Dkog5tLdQpDQ0WifUIkSlqFjjjIghVLq84P8a7H+Q3aidvcg84kfGrD L2GnneUW/oXzzdwgXLOvvhdG6E3eztvszllvxRKbvAeqkXVDFVAD5w== =v4qs -----END PGP SIGNATURE----- --x+6KMIRAuhnl3hBn-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 14:20:40 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 1DDC937B412; Thu, 6 Sep 2001 14:20:23 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA06062; Thu, 6 Sep 2001 14:20:19 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010906135259.C18784@xor.obsecurity.org> Date: Thu, 06 Sep 2001 14:20:15 -0700 (PDT) From: John Baldwin To: Kris Kennaway Subject: Re: libh src/ import Cc: arch@FreeBSD.org, alex@big.endian.de, jlemon@flugsvamp.com, Jordan Hubbard Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 06-Sep-01 Kris Kennaway wrote: > On Wed, Sep 05, 2001 at 11:41:51PM -0700, Jordan Hubbard wrote: >> What's wrong with src/release? src/contrib is generally for "3rd party" >> software such as gdb or tcpdump. libh was developed entirely within the >> FreeBSD project and is only really applicable to release management. > > Perhaps I don't know enough about what libh does (I thought it was a > GUI library), but is it really beyond the realms of possibility that > someone might want to use this for another purpose than the installer? A nice interface for binary updating when it comes. Imagine a window'ed/ graphical mergemaster. :) You write a simple Tcl script and libh does the rest. It's a general purpose tool that happens to be very useful for the new installer. > Kris -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 14:21:22 2001 Delivered-To: freebsd-arch@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-54.dsl.lsan03.pacbell.net [63.207.60.54]) by hub.freebsd.org (Postfix) with ESMTP id 3345D37B409; Thu, 6 Sep 2001 14:21:17 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C5CD266D0A; Thu, 6 Sep 2001 14:21:16 -0700 (PDT) Date: Thu, 6 Sep 2001 14:21:16 -0700 From: Kris Kennaway To: Alexander Langer Cc: Kris Kennaway , Jordan Hubbard , jlemon@flugsvamp.com, arch@FreeBSD.ORG Subject: Re: libh src/ import Message-ID: <20010906142116.A20692@xor.obsecurity.org> References: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> <20010905210328.B91111@prism.flugsvamp.com> <20010905234151J.jkh@freebsd.org> <20010906135259.C18784@xor.obsecurity.org> <20010906231117.A1435@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010906231117.A1435@zerogravity.kawo2.rwth-aachen.d>; from alex@big.endian.de on Thu, Sep 06, 2001 at 11:11:17PM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 06, 2001 at 11:11:17PM +0200, Alexander Langer wrote: > Thus spake Kris Kennaway (kris@obsecurity.org): >=20 > > Perhaps I don't know enough about what libh does (I thought it was a > > GUI library), but is it really beyond the realms of possibility that > > someone might want to use this for another purpose than the installer? >=20 > Yes, replacing dialog(1) calls in the ports tree for example. That seems to settle the issue of whether it should go in release/, then. Kris --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7l+jMWry0BWjoQKURAs/aAJ0f9uQyr1clyw8n62P8TrNs64BgWwCeOLyH DWil2LgOeSn5jKEumV28FBs= =YyRt -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 14:49:16 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 515A737B408; Thu, 6 Sep 2001 14:49:12 -0700 (PDT) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id XAA31736; Thu, 6 Sep 2001 23:49:10 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id C526114B50; Thu, 6 Sep 2001 23:49:09 +0200 (CEST) Date: Thu, 6 Sep 2001 23:49:09 +0200 From: Alexander Langer To: John Baldwin Cc: Kris Kennaway , arch@FreeBSD.org, jlemon@flugsvamp.com, Jordan Hubbard Subject: Re: libh src/ import Message-ID: <20010906234909.A3447@zerogravity.kawo2.rwth-aachen.d> References: <20010906135259.C18784@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Sep 06, 2001 at 02:20:15PM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake John Baldwin (jhb@FreeBSD.org): > A nice interface for binary updating when it comes. Imagine a window'ed/ > graphical mergemaster. :) You write a simple Tcl script and libh does the > rest. It's a general purpose tool that happens to be very useful for the new > installer. Indeed :) I'm just building a new make infrastructure. I can do the following: src/lib/libh Makefile /include /common /database /disk /file /hui /sysinstall /tcl src/usr.bin/ This "world" version builds only TVision support, and is not connected to buildworld until we know what to do with TVision and Tcl. This are also the first things I'd like to import. Later, we can add: src/usr.bin/diskedit libh diskeditor written in Tcl src/usr.bin/ libh Tcl package system scripts then, for releases, we do src/release/libh none <- no GUI support, for pkg-stuff (if needed) graphics <- Qt only (if needed) text <- TVision (trimmed for floppy-installs) text+graphics <- Qt + TVision (CD-ROM installs) scripts <- installation scripts, aka sysinstall2 We need to build these different versions since the libs either have support for Qt/TVision or not. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 14:49:57 2001 Delivered-To: freebsd-arch@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id E5FF037B408 for ; Thu, 6 Sep 2001 14:49:53 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f86Ln8T33992; Thu, 6 Sep 2001 14:49:08 -0700 (PDT) (envelope-from jkh@freebsd.org) To: kris@obsecurity.org Cc: jlemon@flugsvamp.com, alex@big.endian.de, arch@freebsd.org Subject: Re: libh src/ import In-Reply-To: <20010906135259.C18784@xor.obsecurity.org> References: <20010905210328.B91111@prism.flugsvamp.com> <20010905234151J.jkh@freebsd.org> <20010906135259.C18784@xor.obsecurity.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010906144908K.jkh@freebsd.org> Date: Thu, 06 Sep 2001 14:49:08 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 20 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It's not beyond the realm of possibility, no. I guess I don't really care that much about it, upon further reflection, and it should be imported wherever Alex wants to import it. :) - Jordan From: Kris Kennaway Subject: Re: libh src/ import Date: Thu, 6 Sep 2001 13:52:59 -0700 > On Wed, Sep 05, 2001 at 11:41:51PM -0700, Jordan Hubbard wrote: > > What's wrong with src/release? src/contrib is generally for "3rd party" > > software such as gdb or tcpdump. libh was developed entirely within the > > FreeBSD project and is only really applicable to release management. > > Perhaps I don't know enough about what libh does (I thought it was a > GUI library), but is it really beyond the realms of possibility that > someone might want to use this for another purpose than the installer? > > Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 15:19:22 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id DA06637B405; Thu, 6 Sep 2001 15:19:14 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f86MJDn153916; Thu, 6 Sep 2001 18:19:13 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 6 Sep 2001 18:19:10 -0400 To: John Baldwin , Alexander Langer From: Garance A Drosihn Subject: RE: libh src/ import Cc: arch@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 12:05 PM -0700 9/6/01, John Baldwin wrote: >On 06-Sep-01 Alexander Langer wrote: >> Hi! >> >> How are peoples feelings about an import of libh into our src tree, >> in order to push the development? > >As I said on IRC in an opinion that no one else seems to share, libh >is useful in a wider regard than just FreeBSD, and I think it should >be a separate project that gets vendor imported into src/contrib. I agree it should be somewhere better than src/release. I don't like the idea of a project that we have complete control over would end up in src/contrib, however. I understand that it could have a wider audience than just FreeBSD, but src/contrib is supposed to be for those things that we "keep our hands off of, unless we really really have to change something, and even then we have to get the maintainer's explicit permission and a 2/3 majority of the house of representatives (and every country's equivalent) before we make a change". It's bad enough that we have other things which SHOULD fit that definition and are NOT in src/contrib. I think it will only make matters worse too add things in src/contrib which do not fit that definition. Let me go so far as to say that maybe we should consider some other parts of the system in the same manner as JohnB has described libh. Something definitely part of the default freebsd system, and yet maybe detachable for use in other systems. Let's call these "standalone" systems, and put them in some other (new) directory. Then let's think if we have other things we could also put in that directory. I'm not too worked up about this idea, I'm just trying to trigger a few alternate ideas by suggesting this one. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 15:31: 1 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id CE86F37B401; Thu, 6 Sep 2001 15:30:43 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA18182; Thu, 6 Sep 2001 15:30:39 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010906234909.A3447@zerogravity.kawo2.rwth-aachen.d> Date: Thu, 06 Sep 2001 15:30:36 -0700 (PDT) From: John Baldwin To: Alexander Langer Subject: Re: libh src/ import Cc: Jordan Hubbard , jlemon@flugsvamp.com, arch@FreeBSD.org, Kris Kennaway Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 06-Sep-01 Alexander Langer wrote: > then, for releases, we do > > src/release/libh > none <- no GUI support, for pkg-stuff (if needed) > graphics <- Qt only (if needed) > text <- TVision (trimmed for floppy-installs) > text+graphics <- Qt + TVision (CD-ROM installs) > > scripts <- installation scripts, aka sysinstall2 > > We need to build these different versions since the libs either > have support for Qt/TVision or not. These don't belong in src/release either. They are also used for post install configuration. sysinstall is in src/usr.sbin now. > Alex -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 15:31: 1 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id EFB2037B407 for ; Thu, 6 Sep 2001 15:30:44 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA18191; Thu, 6 Sep 2001 15:30:41 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 06 Sep 2001 15:30:38 -0700 (PDT) From: John Baldwin To: Garance A Drosihn Subject: RE: libh src/ import Cc: arch@FreeBSD.org, Alexander Langer Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 06-Sep-01 Garance A Drosihn wrote: > At 12:05 PM -0700 9/6/01, John Baldwin wrote: >>On 06-Sep-01 Alexander Langer wrote: >>> Hi! >>> >>> How are peoples feelings about an import of libh into our src tree, >>> in order to push the development? >> >>As I said on IRC in an opinion that no one else seems to share, libh >>is useful in a wider regard than just FreeBSD, and I think it should >>be a separate project that gets vendor imported into src/contrib. > > I agree it should be somewhere better than src/release. > > I don't like the idea of a project that we have complete control > over would end up in src/contrib, however. I understand that it > could have a wider audience than just FreeBSD, but src/contrib > is supposed to be for those things that we "keep our hands off of, > unless we really really have to change something, and even then we > have to get the maintainer's explicit permission and a 2/3 majority > of the house of representatives (and every country's equivalent) > before we make a change". You are making an erroneous assumption that all libh developers are FreeBSD developers. At least one libh committer is _not_ a FreeBSD committer. GUI's and OS's are two different things and draw from different developer communities (albeit communities that intersect at points). A similar idea would be if we decided to write our own C compiler and make it part of the FreeBSD project instead of being its own project. Or our own graphical system that is a replacement for X. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 15:45:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 3159C37B401; Thu, 6 Sep 2001 15:45:20 -0700 (PDT) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id AAA01562; Fri, 7 Sep 2001 00:45:16 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id A403E14B52; Fri, 7 Sep 2001 00:45:16 +0200 (CEST) Date: Fri, 7 Sep 2001 00:45:16 +0200 From: Alexander Langer To: John Baldwin Cc: Jordan Hubbard , jlemon@flugsvamp.com, arch@FreeBSD.org, Kris Kennaway Subject: Re: libh src/ import Message-ID: <20010907004516.A8187@zerogravity.kawo2.rwth-aachen.d> References: <20010906234909.A3447@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Sep 06, 2001 at 03:30:36PM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake John Baldwin (jhb@FreeBSD.org): > These don't belong in src/release either. They are also used for post install > configuration. sysinstall is in src/usr.sbin now. These libs can't co-exist, and do we want a check for Qt in "make world"? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 15:46:42 2001 Delivered-To: freebsd-arch@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id 2977E37B403; Thu, 6 Sep 2001 15:46:39 -0700 (PDT) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id AAA01607; Fri, 7 Sep 2001 00:46:38 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id C1D9D14B52; Fri, 7 Sep 2001 00:46:38 +0200 (CEST) Date: Fri, 7 Sep 2001 00:46:38 +0200 From: Alexander Langer To: John Baldwin Cc: Garance A Drosihn , arch@FreeBSD.ORG Subject: Re: libh src/ import Message-ID: <20010907004638.A8345@zerogravity.kawo2.rwth-aachen.d> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Thu, Sep 06, 2001 at 03:30:38PM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake John Baldwin (jhb@FreeBSD.ORG): > decided to write our own C compiler and make it part of the FreeBSD project > instead of being its own project. Or our own graphical system that is a > replacement for X. How's OpenSSH developed in the OpenBSD tree? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 15:50: 7 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 0BE8637B403; Thu, 6 Sep 2001 15:50:03 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f86MuDo03899; Thu, 6 Sep 2001 15:56:13 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200109062256.f86MuDo03899@mass.dis.org> To: Kris Kennaway Cc: Alexander Langer , Jordan Hubbard , jlemon@flugsvamp.com, arch@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: libh src/ import In-Reply-To: Message from Kris Kennaway of "Thu, 06 Sep 2001 14:21:16 PDT." <20010906142116.A20692@xor.obsecurity.org> Date: Thu, 06 Sep 2001 15:56:13 -0700 From: Mike Smith Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > Perhaps I don't know enough about what libh does (I thought it was a > > > GUI library), but is it really beyond the realms of possibility that > > > someone might want to use this for another purpose than the installer? > >=20 > > Yes, replacing dialog(1) calls in the ports tree for example. > > That seems to settle the issue of whether it should go in release/, > then. FWIW, I think that putting libh in the base system is a Very Bad Idea. It should be a port, like sysinstall should be a port. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 16:20:23 2001 Delivered-To: freebsd-arch@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 2A4D337B407; Thu, 6 Sep 2001 16:20:20 -0700 (PDT) Received: by tao.org.uk (Postfix, from userid 100) id 5484C232; Fri, 7 Sep 2001 00:20:17 +0100 (BST) Date: Fri, 7 Sep 2001 00:20:17 +0100 From: Josef Karthauser To: Mike Smith Cc: Kris Kennaway , Alexander Langer , Jordan Hubbard , jlemon@flugsvamp.com, arch@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: libh src/ import Message-ID: <20010907002017.A8285@tao.org.uk> References: <200109062256.f86MuDo03899@mass.dis.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109062256.f86MuDo03899@mass.dis.org>; from msmith@freebsd.org on Thu, Sep 06, 2001 at 03:56:13PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 06, 2001 at 03:56:13PM -0700, Mike Smith wrote: > FWIW, I think that putting libh in the base system is a Very Bad Idea. >=20 > It should be a port, like sysinstall should be a port. But mergemaster shouldn't be. Joe --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjuYBLAACgkQXVIcjOaxUBZu8ACg3a8Ssnns5f8ybZps/HoKLgpa th4An3soBO2otEHg4UH0TjIYoM2kvjg8 =ukM6 -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 16:52:14 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 3115037B403; Thu, 6 Sep 2001 16:52:11 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f86Nq8n60734; Thu, 6 Sep 2001 19:52:08 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 6 Sep 2001 19:52:03 -0400 To: John Baldwin From: Garance A Drosihn Subject: RE: libh src/ import Cc: arch@FreeBSD.org, Alexander Langer Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 3:30 PM -0700 9/6/01, John Baldwin wrote: >On 06-Sep-01 Garance A Drosihn wrote: > > > > I agree it should be somewhere better than src/release. >> >> I don't like the idea of a project that we have complete control >> over would end up in src/contrib, however. I understand that it >> could have a wider audience than just FreeBSD, but src/contrib > > is supposed to be for those things that we "keep our hands off of..." > >You are making an erroneous assumption that all libh developers are >FreeBSD developers. At least one libh committer is _not_ a FreeBSD >committer. GUI's and OS's are two different things and draw from >different developer communities (albeit communities that intersect >at points). A similar idea would be if we decided to write our own >C compiler and make it part of the FreeBSD project instead of being >its own project. Or our own graphical system that is a >replacement for X. You are making an erroneous assumption about what assumptions I am making about the developers on libh... :-) I am just saying that libh (even with it's ONE non-freebsd committer on it), does not strike me as something which belongs in src/contrib. Some of the other things that libh needs (eg: tcl) obviously do belong in src/contrib. I suggested an alternate directory for this, one which we might move other "parts of freebsd" into. This alternate directory might very well be one which is a different CVS repository than the rest of the freebsd project, but it isn't "unrelated" to freebsd in the same sense as 'gcc' is "unrelated" to freebsd (or at least, I HOPE libh won't be that "unrelated"!). My understanding is that src/contrib is supposed to be for "freebsd hands-off" projects, and I do not think libh should fit that description. If the gcc gang wants to make a change which causes trouble for freebsd, well, they're going to make the change and we will just have to deal with it. If the libh guys make changes which are a PROBLEM for freebsd, then in my opinion something will have gone seriously wrong. That's just my opinion, but it's the opinion I'm sticking with... Please note that I'm not as worked up about pushing everyone to *agree* with my opinion as I may seem to be in this message. I'm only trying to make sure everyone understands the suggestion I am making. The thing is, I'm not quite sure what that "new directory" should be. Perhaps maybe even something as weird-sounding as ports/freebsd or sys/ports. I think we could find some other parts of the base freebsd system which would merit the same treatment that we are envisioning for libh. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 16:57: 9 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 0E43F37B406; Thu, 6 Sep 2001 16:57:07 -0700 (PDT) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f86Nv4n91962; Thu, 6 Sep 2001 19:57:04 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010907004638.A8345@zerogravity.kawo2.rwth-aachen.d> References: <20010907004638.A8345@zerogravity.kawo2.rwth-aachen.d> Date: Thu, 6 Sep 2001 19:57:02 -0400 To: Alexander Langer , John Baldwin From: Garance A Drosihn Subject: Re: libh src/ import Cc: arch@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 12:46 AM +0200 9/7/01, Alexander Langer wrote: >Thus spake John Baldwin (jhb@FreeBSD.ORG): > > > decided to write our own C compiler and make it part of the FreeBSD > > project instead of being its own project. Or our own graphical system > > that is a replacement for X. > >How's OpenSSH developed in the OpenBSD tree? In some sense there are really two openSSH projects. One which is directly welded into openbsd, and the other which is "portable OpenSSH", and which has all the #ifdef's and stuff to be cross-platform in it. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 18:19:14 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 847B937B403 for ; Thu, 6 Sep 2001 18:19:09 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id SAA23951; Thu, 6 Sep 2001 18:19:06 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010907004638.A8345@zerogravity.kawo2.rwth-aachen.d> Date: Thu, 06 Sep 2001 18:19:03 -0700 (PDT) From: John Baldwin To: Alexander Langer Subject: Re: libh src/ import Cc: arch@FreeBSD.org, Garance A Drosihn Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 06-Sep-01 Alexander Langer wrote: > Thus spake John Baldwin (jhb@FreeBSD.ORG): > >> decided to write our own C compiler and make it part of the FreeBSD project >> instead of being its own project. Or our own graphical system that is a >> replacement for X. > > How's OpenSSH developed in the OpenBSD tree? Backwards. :) It is a separate project that belongs on its own turf. As Garance points out, it basically requires them to maintain two versions rather than one, thus increasing their headache and the overhead. > Alex -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 18:19:15 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 51DB237B405; Thu, 6 Sep 2001 18:19:10 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id SAA23899; Thu, 6 Sep 2001 18:19:04 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010907004516.A8187@zerogravity.kawo2.rwth-aachen.d> Date: Thu, 06 Sep 2001 18:19:01 -0700 (PDT) From: John Baldwin To: Alexander Langer Subject: Re: libh src/ import Cc: Kris Kennaway , arch@FreeBSD.org, jlemon@flugsvamp.com, Jordan Hubbard Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 06-Sep-01 Alexander Langer wrote: > Thus spake John Baldwin (jhb@FreeBSD.org): > >> These don't belong in src/release either. They are also used for post >> install >> configuration. sysinstall is in src/usr.sbin now. > > These libs can't co-exist, and do we want a check for Qt in > "make world"? No, the QT part should be a port. The release makefile can build stripped versions of these binaries for /stand just as it does now for sysinstall, but that doesn't require the source to be in src/release, just tweaks to Makefiles. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 18:36: 5 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 56F6037B403; Thu, 6 Sep 2001 18:36:03 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id SAA01979; Thu, 6 Sep 2001 18:36:01 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200109062256.f86MuDo03899@mass.dis.org> Date: Thu, 06 Sep 2001 18:35:58 -0700 (PDT) From: John Baldwin To: Mike Smith Subject: Re: libh src/ import Cc: msmith@mass.dis.org, arch@FreeBSD.org, jlemon@flugsvamp.com, Jordan Hubbard , Alexander Langer , Kris Kennaway Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 06-Sep-01 Mike Smith wrote: >> > > Perhaps I don't know enough about what libh does (I thought it was a >> > > GUI library), but is it really beyond the realms of possibility that >> > > someone might want to use this for another purpose than the installer? >> >=20 >> > Yes, replacing dialog(1) calls in the ports tree for example. >> >> That seems to settle the issue of whether it should go in release/, >> then. > > FWIW, I think that putting libh in the base system is a Very Bad Idea. > > It should be a port, like sysinstall should be a port. Well, I think it should be src/contrib because we will need it for post-install config and managing packages, but I agree not in src/lib, src/usr.bin, etc. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 19:16: 9 2001 Delivered-To: freebsd-arch@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id 2544D37B407; Thu, 6 Sep 2001 19:16:04 -0700 (PDT) Received: (from mike@localhost) by coffee.q9media.com (8.11.2/8.11.3) id f872IWJ07951; Thu, 6 Sep 2001 22:18:32 -0400 (EDT) (envelope-from mike) Date: Thu, 6 Sep 2001 22:18:31 -0400 From: Mike Barcroft To: John Baldwin Cc: Alexander Langer , arch@FreeBSD.ORG Subject: Re: libh src/ import Message-ID: <20010906221831.A7899@coffee.q9media.com> Mail-Followup-To: Mike Barcroft , John Baldwin , Alexander Langer , arch@FreeBSD.ORG References: <20010906023247.A11776@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Thu, Sep 06, 2001 at 12:05:37PM -0700 Organization: The FreeBSD Project Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin writes: > On 06-Sep-01 Alexander Langer wrote: > > Hi! > > > > How are peoples feelings about an import of libh into our src tree, > > in order to push the development? > > As I said on IRC in an opinion that no one else seems to share, libh is useful > in a wider regard than just FreeBSD, and I think it should be a separate > project that gets vendor imported into src/contrib. Let's face it guys, > FreeBSD doesn't have a lot of GUI people running around, and if libh is going > to fly, it needs developers. IMHO, the best way to get developers for it is to > not make it look like some FreeBSD-only thing, but instead to make it inviting > to other developers. [snip] FreeBSD is more than just a kernel, you know. I don't think we should artificially limit ourselves by your imagination. Obviously Alex wants to get libh to work as FreeBSD's installer before meeting the world's needs, so I think a fully intregrated (lib, usr.sbin) approach is probably best. If at a latter time, Alex feels libh's goals would be better served outside the resources of the FreeBSD project, we can certainly start vendor importing it then. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 19:59:38 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 04A7F37B401; Thu, 6 Sep 2001 19:59:33 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id TAA28968; Thu, 6 Sep 2001 19:59:32 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010906221831.A7899@coffee.q9media.com> Date: Thu, 06 Sep 2001 19:59:28 -0700 (PDT) From: John Baldwin To: Mike Barcroft Subject: Re: libh src/ import Cc: arch@FreeBSD.org, Alexander Langer Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Sep-01 Mike Barcroft wrote: > John Baldwin writes: >> On 06-Sep-01 Alexander Langer wrote: >> > Hi! >> > >> > How are peoples feelings about an import of libh into our src tree, >> > in order to push the development? >> >> As I said on IRC in an opinion that no one else seems to share, libh is >> useful >> in a wider regard than just FreeBSD, and I think it should be a separate >> project that gets vendor imported into src/contrib. Let's face it guys, >> FreeBSD doesn't have a lot of GUI people running around, and if libh is >> going >> to fly, it needs developers. IMHO, the best way to get developers for it is >> to >> not make it look like some FreeBSD-only thing, but instead to make it >> inviting >> to other developers. > [snip] > > FreeBSD is more than just a kernel, you know. I don't think we should > artificially limit ourselves by your imagination. Yes, I'm well aware, and I've been involved with libh (mostly earlier on) for about a year (not much since then) and I can appreciate it's design and it's role. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Thu Sep 6 23:25:39 2001 Delivered-To: freebsd-arch@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id 105DD37B401; Thu, 6 Sep 2001 23:25:32 -0700 (PDT) Received: by sharmas.dhs.org (Postfix, from userid 500) id DD2D65E37A; Thu, 6 Sep 2001 23:28:13 -0700 (PDT) Date: Thu, 6 Sep 2001 23:28:13 -0700 From: Arun Sharma To: Alexander Langer Cc: Dan Moschuk , arch@FreeBSD.ORG Subject: Re: [arun@sharmas.dhs.org: POSIX compatibility issue] Message-ID: <20010906232813.A12058@sharmas.dhs.org> References: <20010906120625.C9605@spirit.jaded.net> <20010906202151.A4070@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010906202151.A4070@zerogravity.kawo2.rwth-aachen.d>; from alex@big.endian.de on Thu, Sep 06, 2001 at 08:21:51PM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Sep 06, 2001 at 08:21:51PM +0200, Alexander Langer wrote: > Thus spake Dan Moschuk (dan@FreeBSD.ORG): > > > Can anyone see a reason why this shouldn't be commited? > > If POSIX doesn't allow u_* types, sys/socket.h has to be fixed, > and not sys/types.h. Anyone with POSIX specs should look up, > how the datatypes in socket.h should be defined. As many others suggested, I changed socket.h, instead of types.h. The diff below makes my program happy. -Arun --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="socket.diff.txt" --- /usr/include/sys/socket.h- Thu Sep 6 23:19:43 2001 +++ /usr/include/sys/socket.h Thu Sep 6 23:20:29 2001 @@ -49,7 +49,7 @@ /* * Data types. */ -typedef u_char sa_family_t; +typedef unsigned char sa_family_t; #ifdef _BSD_SOCKLEN_T_ typedef _BSD_SOCKLEN_T_ socklen_t; #undef _BSD_SOCKLEN_T_ @@ -161,7 +161,7 @@ * addresses. */ struct sockaddr { - u_char sa_len; /* total length */ + unsigned char sa_len; /* total length */ sa_family_t sa_family; /* address family */ char sa_data[14]; /* actually longer; address value */ }; @@ -172,8 +172,8 @@ * information in raw sockets. */ struct sockproto { - u_short sp_family; /* address family */ - u_short sp_protocol; /* protocol */ + unsigned short sp_family; /* address family */ + unsigned short sp_protocol; /* protocol */ }; /* @@ -181,12 +181,12 @@ */ #define _SS_MAXSIZE 128 #define _SS_ALIGNSIZE (sizeof(int64_t)) -#define _SS_PAD1SIZE (_SS_ALIGNSIZE - sizeof(u_char) - sizeof(sa_family_t)) -#define _SS_PAD2SIZE (_SS_MAXSIZE - sizeof(u_char) - sizeof(sa_family_t) - \ +#define _SS_PAD1SIZE (_SS_ALIGNSIZE - sizeof(unsigned char) - sizeof(sa_family_t)) +#define _SS_PAD2SIZE (_SS_MAXSIZE - sizeof(unsigned char) - sizeof(sa_family_t) - \ _SS_PAD1SIZE - _SS_ALIGNSIZE) struct sockaddr_storage { - u_char ss_len; /* address length */ + unsigned char ss_len; /* address length */ sa_family_t ss_family; /* address family */ char __ss_pad1[_SS_PAD1SIZE]; int64_t __ss_align; /* force desired structure storage alignment */ @@ -345,7 +345,7 @@ socklen_t cmsg_len; /* data byte count, including hdr */ int cmsg_level; /* originating protocol */ int cmsg_type; /* protocol-specific type */ -/* followed by u_char cmsg_data[]; */ +/* followed by unsigned char cmsg_data[]; */ }; /* @@ -372,7 +372,7 @@ }; /* given pointer to struct cmsghdr, return pointer to data */ -#define CMSG_DATA(cmsg) ((u_char *)(cmsg) + \ +#define CMSG_DATA(cmsg) ((unsigned char *)(cmsg) + \ _ALIGN(sizeof(struct cmsghdr))) /* given pointer to struct cmsghdr, return pointer to next cmsghdr */ @@ -403,7 +403,7 @@ * 4.3 compat sockaddr, move to compat file later */ struct osockaddr { - u_short sa_family; /* address family */ + unsigned short sa_family; /* address family */ char sa_data[14]; /* up to 14 bytes of direct address */ }; --fUYQa+Pmc3FrFX/N-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 1:40:25 2001 Delivered-To: freebsd-arch@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id CA85437B408; Fri, 7 Sep 2001 01:40:22 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f878eNc02826; Fri, 7 Sep 2001 10:40:23 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/5) with ESMTP id f878eNu02822; Fri, 7 Sep 2001 10:40:23 +0200 (MEST) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id KAA21655; Fri, 7 Sep 2001 10:40:21 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 82AF914B52; Fri, 7 Sep 2001 10:40:20 +0200 (CEST) Date: Fri, 7 Sep 2001 10:40:20 +0200 From: Alexander Langer To: Arun Sharma Cc: Dan Moschuk , arch@FreeBSD.ORG Subject: Re: [arun@sharmas.dhs.org: POSIX compatibility issue] Message-ID: <20010907104020.A1223@zerogravity.kawo2.rwth-aachen.d> References: <20010906120625.C9605@spirit.jaded.net> <20010906202151.A4070@zerogravity.kawo2.rwth-aachen.d> <20010906232813.A12058@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010906232813.A12058@sharmas.dhs.org>; from arun@sharmas.dhs.org on Thu, Sep 06, 2001 at 11:28:13PM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Arun Sharma (arun@sharmas.dhs.org): > -typedef u_char sa_family_t; > +typedef unsigned char sa_family_t; You forgot to remove a tab almost everywhere. Alex -- WELCOME DATACOMP! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 4:45:58 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id B728037B401; Fri, 7 Sep 2001 04:45:55 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA17002; Fri, 7 Sep 2001 21:45:50 +1000 Date: Fri, 7 Sep 2001 21:45:09 +1000 (EST) From: Bruce Evans X-X-Sender: To: Mike Smith Cc: Kris Kennaway , Alexander Langer , Jordan Hubbard , , , Subject: Re: libh src/ import In-Reply-To: <200109062256.f86MuDo03899@mass.dis.org> Message-ID: <20010907214019.P38516-100000@alphplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 6 Sep 2001, Mike Smith wrote: > FWIW, I think that putting libh in the base system is a Very Bad Idea. I agree (because it depends on GUI bloat). > It should be a port, like sysinstall should be a port. But there needs to be a some way of installing the system using only tools in the system. I normally use tar(1). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 7:12:59 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4065237B407; Fri, 7 Sep 2001 07:12:53 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA25228; Sat, 8 Sep 2001 00:12:41 +1000 Date: Sat, 8 Sep 2001 00:11:59 +1000 (EST) From: Bruce Evans X-X-Sender: To: Mikhail Teterin Cc: , , , Subject: Re: proctitle progress reporting for dump(8) In-Reply-To: <200109051321.f85DLSo63141@aldan.algebra.com> Message-ID: <20010907235013.G39239-100000@alphplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 5 Sep 2001, Mikhail Teterin wrote: > On 5 Sep, Bruce Evans wrote: > > snprintf, strlen, vsnprintf, sysctl, sysctlbyname > > > > I think all of these are safe in practice. > > > > It also accesses some variables that are not safe to access in > > a signal handler (non-auto ones that are not of type "volatile > > sig_atomic_t" or are accessed by reads). This is unsafe in practice. > > E.g., concurrent calls to setproctitle() might corrupt the state of > > the ps_strings variable. > > Mmm, I don't know what those strings are used for -- what's the worst, > that could happen here -- corrupted PS output, or worse? Probably security holes from buffer overruns. strlen() on the static buffer may give a result larger than the buffer size if it is called concurrently with an snprintf() that is modifying the buffer. Then vsnprintf(buf + len, sizeof(buf) - len, fmt, ap) gives a buffer overrun. > In any case, it seems, like a simple lock -- a static variable in the > signal handler would work: > > static signal_handling; > ... > if (signal_handling) > return; > if (signal) > signal_handling = 1; > ... > signal_handling = 0; > > Or is this not safe enough -- race of both signal handlers checking for > the signal_handling at the same time? What would be the right way to do > this generally? Thanks. The signal mask would normally prevent concurrent calls from the SIGINFO handler, but in general you need more than the above (an atomic test-and- set of `signal_handling'). setproctitle() is a library function so it should do this generally or not at all. But it can't do this, since it has no way to handle the `signal_handling' case. It can't just return, because its spec doesn't permit it to fail, and it can't give up control in non-threaded programs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 9:24:58 2001 Delivered-To: freebsd-arch@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id ACE9B37B405; Fri, 7 Sep 2001 09:24:53 -0700 (PDT) Received: by sharmas.dhs.org (Postfix, from userid 500) id 43E745E379; Fri, 7 Sep 2001 09:27:46 -0700 (PDT) Date: Fri, 7 Sep 2001 09:27:46 -0700 From: Arun Sharma To: Alexander Langer Cc: Dan Moschuk , arch@FreeBSD.ORG Subject: Re: [arun@sharmas.dhs.org: POSIX compatibility issue] Message-ID: <20010907092746.A15457@sharmas.dhs.org> References: <20010906120625.C9605@spirit.jaded.net> <20010906202151.A4070@zerogravity.kawo2.rwth-aachen.d> <20010906232813.A12058@sharmas.dhs.org> <20010907104020.A1223@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <20010907104020.A1223@zerogravity.kawo2.rwth-aachen.d>; from alex@big.endian.de on Fri, Sep 07, 2001 at 10:40:20AM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Sep 07, 2001 at 10:40:20AM +0200, Alexander Langer wrote: > Thus spake Arun Sharma (arun@sharmas.dhs.org): > > > -typedef u_char sa_family_t; > > +typedef unsigned char sa_family_t; > > You forgot to remove a tab almost everywhere. Take 2. -Arun --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="socket.diff.txt" --- socket.h- Thu Sep 6 23:19:43 2001 +++ socket.h Fri Sep 7 09:21:09 2001 @@ -49,7 +49,7 @@ /* * Data types. */ -typedef u_char sa_family_t; +typedef unsigned char sa_family_t; #ifdef _BSD_SOCKLEN_T_ typedef _BSD_SOCKLEN_T_ socklen_t; #undef _BSD_SOCKLEN_T_ @@ -161,7 +161,7 @@ * addresses. */ struct sockaddr { - u_char sa_len; /* total length */ + unsigned char sa_len; /* total length */ sa_family_t sa_family; /* address family */ char sa_data[14]; /* actually longer; address value */ }; @@ -172,8 +172,8 @@ * information in raw sockets. */ struct sockproto { - u_short sp_family; /* address family */ - u_short sp_protocol; /* protocol */ + unsigned short sp_family; /* address family */ + unsigned short sp_protocol; /* protocol */ }; /* @@ -181,12 +181,12 @@ */ #define _SS_MAXSIZE 128 #define _SS_ALIGNSIZE (sizeof(int64_t)) -#define _SS_PAD1SIZE (_SS_ALIGNSIZE - sizeof(u_char) - sizeof(sa_family_t)) -#define _SS_PAD2SIZE (_SS_MAXSIZE - sizeof(u_char) - sizeof(sa_family_t) - \ +#define _SS_PAD1SIZE (_SS_ALIGNSIZE - sizeof(unsigned char) - sizeof(sa_family_t)) +#define _SS_PAD2SIZE (_SS_MAXSIZE - sizeof(unsigned char) - sizeof(sa_family_t) - \ _SS_PAD1SIZE - _SS_ALIGNSIZE) struct sockaddr_storage { - u_char ss_len; /* address length */ + unsigned char ss_len; /* address length */ sa_family_t ss_family; /* address family */ char __ss_pad1[_SS_PAD1SIZE]; int64_t __ss_align; /* force desired structure storage alignment */ @@ -345,7 +345,7 @@ socklen_t cmsg_len; /* data byte count, including hdr */ int cmsg_level; /* originating protocol */ int cmsg_type; /* protocol-specific type */ -/* followed by u_char cmsg_data[]; */ +/* followed by unsigned char cmsg_data[]; */ }; /* @@ -372,7 +372,7 @@ }; /* given pointer to struct cmsghdr, return pointer to data */ -#define CMSG_DATA(cmsg) ((u_char *)(cmsg) + \ +#define CMSG_DATA(cmsg) ((unsigned char *)(cmsg) + \ _ALIGN(sizeof(struct cmsghdr))) /* given pointer to struct cmsghdr, return pointer to next cmsghdr */ @@ -403,8 +403,9 @@ * 4.3 compat sockaddr, move to compat file later */ struct osockaddr { - u_short sa_family; /* address family */ - char sa_data[14]; /* up to 14 bytes of direct address */ + unsigned short sa_family; /* address family */ + char sa_data[14]; /* up to 14 bytes of direct + address */ }; /* --qDbXVdCdHGoSgWSk-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 9:33:28 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 4EC6B37B403; Fri, 7 Sep 2001 09:33:26 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f87GXPG86154; Fri, 7 Sep 2001 09:33:25 -0700 (PDT) (envelope-from obrien) Date: Fri, 7 Sep 2001 09:33:25 -0700 From: "David O'Brien" To: John Baldwin Cc: Garance A Drosihn , arch@FreeBSD.org, Alexander Langer Subject: Re: libh src/ import Message-ID: <20010907093325.A85914@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Sep 06, 2001 at 03:30:38PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Sep 06, 2001 at 03:30:38PM -0700, John Baldwin wrote: > You are making an erroneous assumption that all libh developers are FreeBSD > developers. At least one libh committer is _not_ a FreeBSD committer. Who is that? I explicitly asked Alex on IRC if all libh committers were FreeBSD people. I meant committers, maybe he ment something else. Alex? -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 10: 7:50 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id C9CD437B403 for ; Fri, 7 Sep 2001 10:07:45 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 618734CE0B for ; Fri, 7 Sep 2001 13:07:45 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id NAA03391 for ; Fri, 7 Sep 2001 13:07:44 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id KAA21161; Fri, 7 Sep 2001 10:07:44 -0700 (PDT) Message-Id: <200109071707.KAA21161@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: arch@freebsd.org Subject: Causing to depend on Date: Fri, 7 Sep 2001 10:07:43 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'd like to import these IGMPv3 patches from KPN/ICSI ( http://home.hetnet.nl/~wilbertdg/igmpv3.html ), but I'm wary of one problem: the IGMPv3 API requires that depends on , due to the use of struct sockaddr_storage in structs that are past to setsockopt(). The easy solution is to #include in (perhaps protected with #ifndef _SYS_SOCKET_H_), but I've got the feeling that'll get some pushback. The API is still being specified (although it's also been implemented a couple of places, so changes will have to be well-justified); the current draft is available at http://www.ietf.org/internet-drafts/draft-ietf-idmr-msf-api-02.txt I'm open to any comments. Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 10:48:58 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 729D637B403 for ; Fri, 7 Sep 2001 10:48:56 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id B095C1E0DD for ; Fri, 7 Sep 2001 13:48:55 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id NAA05038 for ; Fri, 7 Sep 2001 13:48:55 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id KAA21991; Fri, 7 Sep 2001 10:48:55 -0700 (PDT) Message-Id: <200109071748.KAA21991@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: arch@freebsd.org Subject: Re: Causing to depend on Date: Fri, 7 Sep 2001 10:48:54 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Er, I think I take back my own objection. IEEE Std 1003.1-200x says SYNOPSIS #include ... Inclusion of the header may also make visible all symbols from and . Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 11: 6:45 2001 Delivered-To: freebsd-arch@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id C3F6D37B405; Fri, 7 Sep 2001 11:06:40 -0700 (PDT) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f87I6ec07298; Fri, 7 Sep 2001 20:06:40 +0200 (MEST) Received: from kawoserv.kawo2.rwth-aachen.de (root@kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/5) with ESMTP id f87I6eu07294; Fri, 7 Sep 2001 20:06:40 +0200 (MEST) Received: from fump.kawo2.rwth-aachen.de (root@fump.kawo2.rwth-aachen.de [134.130.181.148]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id UAA12859; Fri, 7 Sep 2001 20:06:38 +0200 Received: (from alex@localhost) by fump.kawo2.rwth-aachen.de (8.11.3/8.11.3) id f87I6iN49202; Fri, 7 Sep 2001 20:06:44 +0200 (CEST) (envelope-from alex) Date: Fri, 7 Sep 2001 20:06:43 +0200 From: Alexander Langer To: "David O'Brien" Cc: John Baldwin , Garance A Drosihn , arch@FreeBSD.org Subject: Re: libh src/ import Message-ID: <20010907200643.A49171@fump.kawo2.rwth-aachen.de> References: <20010907093325.A85914@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010907093325.A85914@dragon.nuxi.com>; from obrien@FreeBSD.org on Fri, Sep 07, 2001 at 09:33:25AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake David O'Brien (obrien@FreeBSD.org): > Who is that? I explicitly asked Alex on IRC if all libh committers were > FreeBSD people. I meant committers, maybe he ment something else. Alex? Nathan Ahlstrom . Note that he has an account, but not a commit-bit. He maintains the libh-port as well, so I really consider him a FreeBSD guy :) His lack of commit-bit shouldn't be the problem: Nathan has submitted the patches to me before he got his libh commit bit, and I think he also mentioned due to private reasons he has not that much time at the moment. So there is only once active developer left (me). Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 12:11:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 4365637B403 for ; Fri, 7 Sep 2001 12:11:10 -0700 (PDT) Received: from mindspring.com (dialup-209.247.142.57.Dial1.SanJose1.Level3.net [209.247.142.57]) by falcon.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f87JB8325985; Fri, 7 Sep 2001 12:11:08 -0700 (PDT) Message-ID: <3B991BF8.5BF2E5E2@mindspring.com> Date: Fri, 07 Sep 2001 12:11:52 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fenner Cc: arch@freebsd.org Subject: Re: Causing to depend on References: <200109071748.KAA21991@windsor.research.att.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Fenner wrote: > > Er, I think I take back my own objection. IEEE Std 1003.1-200x says > > SYNOPSIS > #include > ... > Inclusion of the header may also make > visible all symbols from and . ... and it MAY not. You should just include both yourself, and be done with it. By forcing inclusion of socket.h, you break the layering abstraction. If this is done with pointers, rather than instances or member references, in the API code, just forward declare the structure, and use it as an opaque type, e.g.: struct socket; struct foo { struct socket *mysock; ... }; As long as it's a pointer, the compiler will not balk at it being an incomplete type, unless you attempt to dereference it. Since that should only ever happen in code, and code does not belong in header files, problem solved. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 12:43:34 2001 Delivered-To: freebsd-arch@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id BAC9937B401 for ; Fri, 7 Sep 2001 12:43:31 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f87JhbL78871; Fri, 7 Sep 2001 14:43:37 -0500 (CDT) (envelope-from jlemon) Date: Fri, 7 Sep 2001 14:43:37 -0500 From: Jonathan Lemon To: Terry Lambert Cc: Bill Fenner , arch@FreeBSD.ORG Subject: Re: Causing to depend on Message-ID: <20010907144337.Z20137@prism.flugsvamp.com> References: <200109071748.KAA21991@windsor.research.att.com> <3B991BF8.5BF2E5E2@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <3B991BF8.5BF2E5E2@mindspring.com> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Sep 07, 2001 at 12:11:52PM -0700, Terry Lambert wrote: > Bill Fenner wrote: > > > > Er, I think I take back my own objection. IEEE Std 1003.1-200x says > > > > SYNOPSIS > > #include > > ... > > Inclusion of the header may also make > > visible all symbols from and . > > ... and it MAY not. > > You should just include both yourself, and be done with it. > > By forcing inclusion of socket.h, you break the layering > abstraction. No. already knows about socket addresses, just in a slightly different form. These are called 'struct sockaddr_in'. > If this is done with pointers, rather than instances or > member references, in the API code, just forward declare > the structure, and use it as an opaque type, e.g.: Uhm. Please go look at the definition of sockaddr_storage in . See RFC 2553 for more information. Not speaking for Bill, but my guess he needs to use this to allocate storage in a protocol-independent fashion. The other alternative may be to create 'sockaddr_storage46' in , but that probably is equally yucky. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 14: 5:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 5A26437B403 for ; Fri, 7 Sep 2001 14:05:43 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 45F751E050; Fri, 7 Sep 2001 17:05:42 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id RAA10536; Fri, 7 Sep 2001 17:05:41 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id OAA24949; Fri, 7 Sep 2001 14:05:41 -0700 (PDT) Message-Id: <200109072105.OAA24949@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: tlambert2@mindspring.com Subject: Re: Causing to depend on Cc: fenner@research.att.com, arch@freebsd.org References: <200109071748.KAA21991@windsor.research.att.com> <3B991BF8.5BF2E5E2@mindspring.com> Date: Fri, 7 Sep 2001 14:05:40 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG They are not pointers. That's why I included a reference to the API spec; it says that the structure is, e.g.: struct group_source_req { uint32_t gsr_interface; /* interface index */ struct sockaddr_storage gsr_group; /* group address */ struct sockaddr_storage gsr_source; /* source address */ }; That's why I said the API makes a prerequisite for . Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 14:10:23 2001 Delivered-To: freebsd-arch@freebsd.org Received: from redrock.eng.bsdi.com (redrock.eng.bsdi.com [206.196.45.2]) by hub.freebsd.org (Postfix) with ESMTP id AC2EA37B401 for ; Fri, 7 Sep 2001 14:10:16 -0700 (PDT) Received: from redrock.eng.bsdi.com (karels@localhost.BSDI.COM [127.0.0.1]) by redrock.eng.bsdi.com (8.11.2/8.10.1) with ESMTP id f87LADX15133; Fri, 7 Sep 2001 16:10:13 -0500 (CDT) Message-Id: <200109072110.f87LADX15133@redrock.eng.bsdi.com> To: Bill Fenner Cc: arch@FreeBSD.ORG From: Mike Karels Reply-To: karels@BSDI.COM Subject: Re: Causing to depend on In-reply-to: Your message of Fri, 07 Sep 2001 10:48:54 -0700. <200109071748.KAA21991@windsor.research.att.com> Date: Fri, 07 Sep 2001 16:10:13 -0500 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Er, I think I take back my own objection. IEEE Std 1003.1-200x says > SYNOPSIS > #include > ... > Inclusion of the header may also make > visible all symbols from and . I haven't seen that version of the networking stuff yet. However, if you are solving the problem I think you are, types like sa_family_t, I can tell you what we do in BSD/OS: we created a , and include it from both and . Hope this helps, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Fri Sep 7 14:25: 8 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 5931837B403 for ; Fri, 7 Sep 2001 14:25:05 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id AB0CE1E0ED; Fri, 7 Sep 2001 17:25:04 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id RAA10935; Fri, 7 Sep 2001 17:25:03 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id OAA25298; Fri, 7 Sep 2001 14:25:03 -0700 (PDT) Message-Id: <200109072125.OAA25298@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: karels@bsdi.com Subject: Re: Causing to depend on Cc: arch@freebsd.org Date: Fri, 7 Sep 2001 14:25:02 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry for making people guess what I was talking about. Concretely, http://www.ietf.org/internet-drafts/draft-ietf-idmr-msf-api-02.txt requires that #including results in definitions like the following: struct group_req { uint32_t gr_interface; /* interface index */ struct sockaddr_storage gr_group; /* group address */ }; struct group_source_req { uint32_t gsr_interface; /* interface index */ struct sockaddr_storage gsr_group; /* group address */ struct sockaddr_storage gsr_source; /* source address */ }; struct group_filter { uint32_t gf_interface; /* interface index */ struct sockaddr_storage gf_group; /* multicast address */ uint32_t gf_fmode; /* filter mode */ uint32_t gf_numsrc; /* number of sources */ struct sockaddr_storage gf_slist[1]; /* source address */ }; Since they're not pointers, forward struct declarations don't work. Since "struct sockaddr_storage" is defined in , the easy thing to do is to pull in . Mike, I guess the point of your would be to include only the common elements and so a) limit the namespace pollution when not #including b) limit the size of the header that's re-parsed (smaller sys/sockettypes.h instead of larger sys/socket.h when a source file includes netinet/in.h followed by sys/socket.h) ? Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 5:28:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 2CC9437B408 for ; Sat, 8 Sep 2001 05:28:47 -0700 (PDT) Received: from mindspring.com (dialup-209.245.142.217.Dial1.SanJose1.Level3.net [209.245.142.217]) by snipe.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f88CSeW16413; Sat, 8 Sep 2001 05:28:41 -0700 (PDT) Message-ID: <3B9A0F21.305F77B1@mindspring.com> Date: Sat, 08 Sep 2001 05:29:21 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Lemon Cc: Bill Fenner , arch@FreeBSD.ORG Subject: Re: Causing to depend on References: <200109071748.KAA21991@windsor.research.att.com> <3B991BF8.5BF2E5E2@mindspring.com> <20010907144337.Z20137@prism.flugsvamp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jonathan Lemon wrote: > > If this is done with pointers, rather than instances or > > member references, in the API code, just forward declare > > the structure, and use it as an opaque type, e.g.: > > Uhm. Please go look at the definition of sockaddr_storage in > . See RFC 2553 for more information. Not speaking > for Bill, but my guess he needs to use this to allocate storage > in a protocol-independent fashion. You mean like "not dependent on IPv4/IPv6, OK for use with IPX and XNS and AppleTalk" because it's not wedged into an ``in'' specific header file? > The other alternative may be to create 'sockaddr_storage46' > in , but that probably is equally yucky. or sockaddr_storage_in, which would be more in keeping with the current style and implementation. Really, we went through *HELL* and a lot of bitching and moaning to _get rid_ of #include files that bring in #include files; this proposal intends to undo all that fine work, from what I can see... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 5:32:45 2001 Delivered-To: freebsd-arch@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 2783137B405 for ; Sat, 8 Sep 2001 05:32:43 -0700 (PDT) Received: from mindspring.com (dialup-209.245.142.217.Dial1.SanJose1.Level3.net [209.245.142.217]) by snipe.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f88CWfW23418; Sat, 8 Sep 2001 05:32:41 -0700 (PDT) Message-ID: <3B9A1015.55FBA110@mindspring.com> Date: Sat, 08 Sep 2001 05:33:25 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fenner Cc: arch@freebsd.org Subject: Re: Causing to depend on References: <200109071748.KAA21991@windsor.research.att.com> <3B991BF8.5BF2E5E2@mindspring.com> <200109072105.OAA24949@windsor.research.att.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Fenner wrote: > > They are not pointers. That's why I included a reference to the > API spec; it says that the structure is, e.g.: > > struct group_source_req { > uint32_t gsr_interface; /* interface index */ > struct sockaddr_storage gsr_group; /* group address */ > struct sockaddr_storage gsr_source; /* source address */ > }; > > That's why I said the API makes a prerequisite for > . The quick answer: put it in ; this will avoid the implied dependency, and avoid trashing all the code with another include or trashing the include with an implied include after all the hard work to get rid of the ugly things. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 5:37:34 2001 Delivered-To: freebsd-arch@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 411B737B405 for ; Sat, 8 Sep 2001 05:37:32 -0700 (PDT) Received: from mindspring.com (dialup-209.245.142.217.Dial1.SanJose1.Level3.net [209.245.142.217]) by snipe.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f88CbLW01492; Sat, 8 Sep 2001 05:37:25 -0700 (PDT) Message-ID: <3B9A112D.5909ECE@mindspring.com> Date: Sat, 08 Sep 2001 05:38:05 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: karels@BSDI.COM Cc: Bill Fenner , arch@FreeBSD.ORG Subject: Re: Causing to depend on References: <200109072110.f87LADX15133@redrock.eng.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Karels wrote: > > Inclusion of the header may also make > > visible all symbols from and . > > I haven't seen that version of the networking stuff yet. However, if > you are solving the problem I think you are, types like sa_family_t, > I can tell you what we do in BSD/OS: we created a , > and include it from both and . This is MUCH cleaner; however, it's still really, really ugly, in that it makes one include file include another, and thus crams a whole bunch of unexpected crap into the implementation space. I haven't seen where the sockaddr_storage type is used, yet (no one has posted anything), but it seems to me that if, when it is used, it is used as an opaque pointer type, where possible, then this avoids the need to pollute the namespace unless someone is referencing members of the structure, which means they are actually using it, which means that they can darn well include a header file to get the non-opaque version of the structure declaration so that they can instance the thing. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 5:46:31 2001 Delivered-To: freebsd-arch@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 343FC37B403 for ; Sat, 8 Sep 2001 05:46:28 -0700 (PDT) Received: from mindspring.com (dialup-209.245.142.217.Dial1.SanJose1.Level3.net [209.245.142.217]) by snipe.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f88CkOW19170; Sat, 8 Sep 2001 05:46:24 -0700 (PDT) Message-ID: <3B9A134D.3B31C443@mindspring.com> Date: Sat, 08 Sep 2001 05:47:09 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fenner Cc: karels@bsdi.com, arch@freebsd.org Subject: Re: Causing to depend on References: <200109072125.OAA25298@windsor.research.att.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Fenner wrote: > > Sorry for making people guess what I was talking about. > > Concretely, http://www.ietf.org/internet-drafts/draft-ietf-idmr-msf-api-02.txt > requires that #including results in definitions like > the following: > > struct group_req { > uint32_t gr_interface; /* interface index */ > struct sockaddr_storage gr_group; /* group address */ > }; > > struct group_source_req { > uint32_t gsr_interface; /* interface index */ > struct sockaddr_storage gsr_group; /* group address */ > struct sockaddr_storage gsr_source; /* source address */ > }; > > struct group_filter { > uint32_t gf_interface; /* interface index */ > struct sockaddr_storage gf_group; /* multicast address */ > uint32_t gf_fmode; /* filter mode */ > uint32_t gf_numsrc; /* number of sources */ > struct sockaddr_storage gf_slist[1]; /* source address */ > }; > > Since they're not pointers, forward struct declarations don't work. So... we didn't need these before, why do we now? Why do they go in in.h? Aren't they generic to all types of sockaddr's, not just sockaddr_in's? I don't see anyone using the things. Unless they are being used as other than a pointer, they don't need to have a real type. Also: this is a DRAFT RFC... if it requires this type of thing, then it should probably be revised so that it _doesn't_ require this type of thing in "draft-ietf-idmr-msf-api-03.txt" or whatever the next version is... the thing expires in 3 months, so it's arguable that it shouldn't be hitting anything other than an experimentor's repository until it gets ratified as experimental, and then makes it to standard's track, anyway. I REALLY object to turning our header files into Linux's header files, where if you include , all other include files in the whole freaking system are dragged into your poor compilation unit. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 10:39: 8 2001 Delivered-To: freebsd-arch@freebsd.org Received: from femail12.sdc1.sfba.home.com (femail12.sdc1.sfba.home.com [24.0.95.108]) by hub.freebsd.org (Postfix) with ESMTP id 5905237B406 for ; Sat, 8 Sep 2001 10:39:05 -0700 (PDT) Received: from aztec ([65.9.230.50]) by femail12.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010908173905.VWEA556.femail12.sdc1.sfba.home.com@aztec> for ; Sat, 8 Sep 2001 10:39:05 -0700 From: "Lou Palladino" To: Subject: platforms Date: Sat, 8 Sep 2001 13:40:10 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0000_01C1386B.C7B81270" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C1386B.C7B81270 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello. Don't laugh at me, but are there any plans for BSD on the good old VAX chip? Lou Palladino ------=_NextPart_000_0000_01C1386B.C7B81270 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello.
 
Don't = laugh at me,=20 but are there any plans for BSD on the good old VAX = chip?
 
Lou=20 Palladino
------=_NextPart_000_0000_01C1386B.C7B81270-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 10:45:14 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 9888B37B40E for ; Sat, 8 Sep 2001 10:45:12 -0700 (PDT) Received: (qmail 82211 invoked from network); 8 Sep 2001 17:45:12 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Sep 2001 17:45:12 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 08 Sep 2001 10:45:08 -0700 (PDT) From: John Baldwin To: Lou Palladino Subject: RE: platforms Cc: freebsd-arch@FreeBSD.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 08-Sep-01 Lou Palladino wrote: > Hello. > > Don't laugh at me, but are there any plans for BSD on the good old VAX chip? > > Lou Palladino NetBSD has a VAX port. It's rumored to support SMP even. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 11:58:56 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 20C0337B407 for ; Sat, 8 Sep 2001 11:58:53 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 8F1271E0E7; Sat, 8 Sep 2001 14:58:42 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id OAA25707; Sat, 8 Sep 2001 14:58:24 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id LAA12165; Sat, 8 Sep 2001 11:58:24 -0700 (PDT) Message-Id: <200109081858.LAA12165@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: tlambert2@mindspring.com Subject: Re: Causing to depend on Cc: karels@bsdi.com, arch@freebsd.org References: <200109072125.OAA25298@windsor.research.att.com> <3B9A134D.3B31C443@mindspring.com> Date: Sat, 8 Sep 2001 11:58:23 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >So... we didn't need these before, why do we now? uh... to introduce new functionality that we didn't have before? We didn't need kernel threads before, why do we now? >Why do they go in in.h? Aren't they generic to all types of >sockaddr's, not just sockaddr_in's? The structures in question are part of an IP protocol independent API for multicast group membership. They use the struct sockaddr_storage that was introduced by the IPv6 API to provide for forward compatability. Since these structs are used as parameters to setsockopt(), it introduces more complexity to pass pointers. >I don't see anyone using the things. I guess I'm missing what things you mean. If you mean the new API that's not in the system yet, that's because it's not in the system yet. If you mean sockaddr_storage, then you haven't looked particularly hard. >Also: this is a DRAFT RFC... if it requires this type of thing, >then it should probably be revised so that it _doesn't_ require >this type of thing The people who have already implemented the API (Microsoft is shipping it) might not like that idea. >I REALLY object to turning our header files into [polluting junk] Well, how hard do you object to Mike's suggestion? Especially since it's POSIX-sanctioned pollution? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 12:10:10 2001 Delivered-To: freebsd-arch@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id E13B737B403 for ; Sat, 8 Sep 2001 12:10:07 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f88JA6Y24963; Sat, 8 Sep 2001 14:10:06 -0500 (CDT) (envelope-from jlemon) Date: Sat, 8 Sep 2001 14:10:05 -0500 From: Jonathan Lemon To: Bill Fenner Cc: tlambert2@mindspring.com, karels@bsdi.com, arch@FreeBSD.ORG Subject: Re: Causing to depend on Message-ID: <20010908141005.R20137@prism.flugsvamp.com> References: <200109072125.OAA25298@windsor.research.att.com> <3B9A134D.3B31C443@mindspring.com> <200109081858.LAA12165@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200109081858.LAA12165@windsor.research.att.com> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Sep 08, 2001 at 11:58:23AM -0700, Bill Fenner wrote: > > >So... we didn't need these before, why do we now? > > uh... to introduce new functionality that we didn't have before? > > We didn't need kernel threads before, why do we now? > > >Why do they go in in.h? Aren't they generic to all types of > >sockaddr's, not just sockaddr_in's? > > The structures in question are part of an IP protocol independent > API for multicast group membership. They use the struct sockaddr_storage > that was introduced by the IPv6 API to provide for forward compatability. > Since these structs are used as parameters to setsockopt(), it introduces > more complexity to pass pointers. It seems that the real problem here is that sockaddr_storage is supposed to be protocol-neutral (used for appletalk, IPX, etc), but what your code really wants is IP-specific sockaddr_storage. Something like: struct sockaddr_storage_in { union { struct sockaddr_in sin4; struct sockaddr_in6 sin6; } ssin; }; This could be placed at the end of , the way things stand now. However, I'm not sure if this approach is better or worse than just moving sockaddr_storage into . -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 13:22: 4 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id F331637B406 for ; Sat, 8 Sep 2001 13:22:01 -0700 (PDT) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 4E92D4CE3E; Sat, 8 Sep 2001 16:22:01 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id QAA27824; Sat, 8 Sep 2001 16:22:00 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id NAA13321; Sat, 8 Sep 2001 13:22:00 -0700 (PDT) Message-Id: <200109082022.NAA13321@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jlemon@flugsvamp.com Subject: Re: Causing to depend on Cc: arch@freebsd.org References: <200109072125.OAA25298@windsor.research.att.com> <3B9A134D.3B31C443@mindspring.com> <200109081858.LAA12165@windsor.research.att.com> <20010908141005.R20137@prism.flugsvamp.com> Date: Sat, 8 Sep 2001 13:21:59 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >It seems that the real problem here is that sockaddr_storage is supposed >to be protocol-neutral (used for appletalk, IPX, etc), but what your >code really wants is IP-specific sockaddr_storage. Well, sockaddr_storage was introduced to support IPv6; it was defined to be "at least large enough to accommodate sockaddr_in and sockaddr_in6 and possibly other protocol specific socket addresses too." [RFC 2553 section 3.10]. I guess the "and possibly other..." part is what's not working out, especially since IEEE Std 1003.1-200x gets rid of the "possibly" part. The advantage of sockaddr_storage is that it's already standard, in widespread use, and was defined for exactly this purpose. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 13:38:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 2BD7237B401 for ; Sat, 8 Sep 2001 13:38:09 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 0897E81D05; Sat, 8 Sep 2001 15:38:04 -0500 (CDT) Date: Sat, 8 Sep 2001 15:38:04 -0500 From: Alfred Perlstein To: Bill Fenner Cc: jlemon@flugsvamp.com, arch@freebsd.org Subject: Re: Causing to depend on Message-ID: <20010908153803.I2965@elvis.mu.org> References: <200109072125.OAA25298@windsor.research.att.com> <3B9A134D.3B31C443@mindspring.com> <200109081858.LAA12165@windsor.research.att.com> <20010908141005.R20137@prism.flugsvamp.com> <200109082022.NAA13321@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200109082022.NAA13321@windsor.research.att.com>; from fenner@research.att.com on Sat, Sep 08, 2001 at 01:21:59PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Bill Fenner [010908 15:22] wrote: > > >It seems that the real problem here is that sockaddr_storage is supposed > >to be protocol-neutral (used for appletalk, IPX, etc), but what your > >code really wants is IP-specific sockaddr_storage. > > Well, sockaddr_storage was introduced to support IPv6; it was defined > to be "at least large enough to accommodate sockaddr_in and sockaddr_in6 > and possibly other protocol specific socket addresses too." [RFC 2553 > section 3.10]. I guess the "and possibly other..." part is what's not > working out, especially since IEEE Std 1003.1-200x gets rid of the "possibly" > part. > > The advantage of sockaddr_storage is that it's already standard, in > widespread use, and was defined for exactly this purpose. I know hindsight is 20/20, and it was before my time, but... I wish we (free unix) had adopted a form of TLI/XTI :( (of course without the entire streams fiasco). -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message From owner-freebsd-arch Sat Sep 8 22:37:27 2001 Delivered-To: freebsd-arch@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-54.dsl.lsan03.pacbell.net [63.207.60.54]) by hub.freebsd.org (Postfix) with ESMTP id 8D79C37B401 for ; Sat, 8 Sep 2001 22:37:23 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 36F6166D0A; Sat, 8 Sep 2001 22:37:23 -0700 (PDT) Date: Sat, 8 Sep 2001 22:37:23 -0700 From: Kris Kennaway To: arch@FreeBSD.org Subject: Moving UUCP to ports Message-ID: <20010908223722.A47449@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, I would like to move the UUCP suite from the base system into ports. The UUCP utilities have a security hole which yields user uucp access, which can currently be leverage to obtain root access by trojaning the uucp binaries. This security hole is believed to be basically unfixable due to the design of UUCP: we can limit its impact, but not eliminate it for all users. We can limit the vulnerability on the majority of FreeBSD installations by making the uucp-owned binaries schg, but there are corner cases where these flags cannot be set or have no effect (/usr mounted on a non-FreeBSD NFS server, installworld run onto a remote NFS filesystem, or into a jail, etc), in which case the local root exploit remains. Since UUCP isn't in widespread use today, I'd prefer not to have these vulnerable edge cases in the FreeBSD base system. Given these security issues, I believe this is sufficient reason to compartmentalize UUCP away from the rest of the system, so that it only affects those who need it and accept the risks. Since the cu binary isn't known to have security problems at this time and it's widely considered useful, I propose to leave it in the base system. I recognize that there are a number of people who still use UUCP, which is why I've tried to make the transition process to using a port as painless as possible. Please check out the freebsd-uucp port and provide feedback on any problems. You'll probably want to remove the following files which are duplicated by the port (e.g. the /etc/periodic files will otherwise be executed twice): /usr/bin/uucp /usr/bin/uulog /usr/bin/uuname /usr/bin/uupick /usr/bin/uusched /usr/bin/uustat /usr/bin/uuto /usr/bin/uux /etc/periodic/daily/340.uucp /etc/periodic/daily/410.status-uucp /etc/periodic/weekly/300.uucp /etc/uucp/call.sample /etc/uucp/config.sample /etc/uucp/dial.sample /etc/uucp/dialcode.sample /etc/uucp/passwd.sample /etc/uucp/port.sample /etc/uucp/sys1.sample /etc/uucp/sys2.sample /usr/share/info/uucp.info.gz /usr/libexec/uucp/uucico /usr/libexec/uucp/uuxqt /usr/sbin/uuchk /usr/sbin/uuconv Kris P.S. Please at least try using the port before you send flames :) --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7mwASWry0BWjoQKURArySAJ4ilISoYpyfPgpsEBJFoJvTW7f0zACfTSIA 9PLYNMoX3YR2SkKAVAZRb+c= =2eK5 -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message