From owner-freebsd-current Sun Dec 22 01:22:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA24485 for current-outgoing; Sun, 22 Dec 1996 01:22:03 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA24478 for ; Sun, 22 Dec 1996 01:22:00 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA24418; Sun, 22 Dec 1996 10:21:20 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA21100; Sun, 22 Dec 1996 10:21:19 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id KAA12649; Sun, 22 Dec 1996 10:19:22 +0100 (MET) From: J Wunsch Message-Id: <199612220919.KAA12649@uriah.heep.sax.de> Subject: Re: successful build of 2.2-snap to current To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 22 Dec 1996 10:19:22 +0100 (MET) Cc: ggm@connect.com.au (George Michaelson) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612220213.MAA27466@broon.off.connect.com.au> from George Michaelson at "Dec 22, 96 12:13:33 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As George Michaelson wrote: > -L/usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib -lcvs -lgnuregex -lmd > -lcrypt > > logmsg.o: Undefined symbol `_Popen' referenced from text segment > release.o: Undefined symbol `_Popen' referenced from text segment > error.o: Undefined symbol `_cvs_outerr' referenced from text segment > watch.o: Undefined symbol `_send_to_server' referenced from text segment > watch.o: Undefined symbol `_lock_tree_for_write' referenced from text segment > watch.o: Undefined symbol `_lock_tree_cleanup' referenced from text segment > watch.o: Undefined symbol `_send_to_server' referenced from text segment This looks as if your cvs library (-lcvs) is broken or empty for some reasons. It's in -L/usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Dec 22 07:59:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA08649 for current-outgoing; Sun, 22 Dec 1996 07:59:24 -0800 (PST) Received: from veda.is (adam@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA08637 for ; Sun, 22 Dec 1996 07:59:17 -0800 (PST) Received: (from adam@localhost) by veda.is (8.8.4/8.7.3) id QAA21531; Sun, 22 Dec 1996 16:04:34 GMT Date: Sun, 22 Dec 1996 16:04:34 GMT From: Adam David Message-Id: <199612221604.QAA21531@veda.is> To: wpaul@skynet.ctr.columbia.EDU (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: Plan for integrating Secure RPC -- comments wanted Newsgroups: list.freebsd.current References: <199612152152.OAA24022@phaeton.artisoft.com> <199612152351.SAA05656@skynet.ctr.columbia.edu> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry: >> Is there a reason you have not considered just taking the step of >> linking these programs shared (option 4?)? This would resolve all >> of the problems simply and effectively. Bill: >Yes: I _like_ the fact that /bin and /sbin are linked static (/bin >mostly). The commands there keep working in the face of a corrupted >or deleted libc.so. I'm not in a hurry to change this. >> I believe the reasons for not running with a shared world are now >> largely irrelevant: the shared library dirty page library clobber >> bug seems to have died more than a year ago, and there is no real >> good reason for it. >That depends on your opinion. Again, I like having some purely static >binaries around to help deal in a shared lib crisis. Also, consider >fsck, which needs to be run on /usr (if /usr is not on the rootfs) >before /usr is mounted. We would have to move libc.so to the rootfs >in order for fsck to work if it was linked dynamic. Put static executables in /bin and /sbin, but mount directories of dynamic executables over them at a later stage. This offers the possibility of conserving memory at the expense of a little more disk space. The static copies could even be accessed later on via an alternative path if necessary. -- Adam David From owner-freebsd-current Sun Dec 22 16:22:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA28261 for current-outgoing; Sun, 22 Dec 1996 16:22:12 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA28247 for ; Sun, 22 Dec 1996 16:22:08 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA17171; Mon, 23 Dec 1996 01:21:10 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA05358; Mon, 23 Dec 1996 01:21:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id BAA20781; Mon, 23 Dec 1996 01:07:38 +0100 (MET) From: J Wunsch Message-Id: <199612230007.BAA20781@uriah.heep.sax.de> Subject: Making an option `supported' To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 23 Dec 1996 01:07:38 +0100 (MET) Cc: toor@dyson.iquest.net (John S. Dyson) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612222341.SAA00651@dyson.iquest.net> from "John S. Dyson" at "Dec 22, 96 06:41:37 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (I dare to send this in public, since i don't assume i'd violate any privacy... but think there's public demand for it.) As John S. Dyson wrote: (regarding how to make a kernel option `supported') > Thanks, I didn't even know what was necessary to do it. Well, fairly simple: First, edit sys/conf/options (or sys/i386/conf/options.i386), and select an opt_foo.h file where your new option would best go into. If there's already something that comes close to the purpose of the new option, pick this. As for the MAXDSIZ option, i felt that opt_rlimit.h was a good choice (the OPEN_MAX and CHILD_MAX options already went there). If there's no opt_foo.h already available for the intended new option, invent a new name. Make it meaningful, and comment the new section in the options[.i386] file. config(8) will automagically pick up the change, and create that file next time it is run. Packing too many options into a single opt_foo.h will cause too many kernel files to be rebuilt when one of the options has been changed in the config file, while creating too many opt_foo.h's does apparently no good either. Finally, find out which kernel files depend on the new option. find /sys -name type f | xargs fgrep NEW_OPTION is your friend in finding them. Go and edit all those files, and add #include "opt_foo.h" _on top_, before all the #include stuff. The sequence is most important in case the options will override some defaults from the regular include files, where the defaults are protected by #ifndef NEW_OPTION #define NEW_OPTION (something) #endif in the regular header. The purpose of all this procedure is that we can eventually kill the ugly removal of the compile directory again in the next release, since changing any supported option in the config file will be automatically picked up again during the compilation by all the dependencies. Of course: "Don't forget to do a ``make depend''." :-) (Right now, the options UFS etc. are the worst offenders.) p.s.: Where in the docs would this notice go best into? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sun Dec 22 18:09:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA03926 for current-outgoing; Sun, 22 Dec 1996 18:09:11 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA03920 for ; Sun, 22 Dec 1996 18:09:09 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id SAA12083; Sun, 22 Dec 1996 18:06:28 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@freebsd.org (FreeBSD-current users), toor@dyson.iquest.net (John S. Dyson) Subject: Re: Making an option `supported' In-reply-to: Your message of "Mon, 23 Dec 1996 01:07:38 +0100." <199612230007.BAA20781@uriah.heep.sax.de> Date: Sun, 22 Dec 1996 18:06:28 -0800 Message-ID: <12079.851306788@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > p.s.: Where in the docs would this notice go best into? Handbook -> Advanced Topics -> Adding New Kernel Configuration Options From owner-freebsd-current Sun Dec 22 18:17:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA04439 for current-outgoing; Sun, 22 Dec 1996 18:17:48 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA04434 for ; Sun, 22 Dec 1996 18:17:44 -0800 (PST) Received: by sovcom.kiae.su id AA05065 (5.65.kiae-1 ); Mon, 23 Dec 1996 05:05:37 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 23 Dec 96 05:05:37 +0300 Received: from localhost (nagual.ru [127.0.0.1]) by nagual.ru (8.8.4/8.8.4) with SMTP id EAA01398; Mon, 23 Dec 1996 04:50:41 +0300 (MSK) Date: Mon, 23 Dec 1996 04:50:41 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= To: David Nugent Cc: freebsd-current@freebsd.org Subject: Re: Confused about locale In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Dec 1996, David Nugent wrote: > > About idea: > > I dislike idea of "system default" locale, I like idea of "user > > default" locale instead! > > Ok. There will be a way of achieving this shortly via login.conf. Not so quick, it will be nice if user can change his preferences easily. > > There must be some field into passwd which indicates current user > > startup locale which must be changeable by user via chpass. > > The last part is more difficult. But the field is already there > in "class". What is difficult here? As man says "class" is pointer to termcap-style attributes. Do you mean that they must be unchangeable by user? -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sun Dec 22 18:17:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA04468 for current-outgoing; Sun, 22 Dec 1996 18:17:55 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA04454 for ; Sun, 22 Dec 1996 18:17:52 -0800 (PST) Received: by sovcom.kiae.su id AA05063 (5.65.kiae-1 ); Mon, 23 Dec 1996 05:05:37 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 23 Dec 96 05:05:36 +0300 Received: from localhost (nagual.ru [127.0.0.1]) by nagual.ru (8.8.4/8.8.4) with SMTP id EAA01342; Mon, 23 Dec 1996 04:46:23 +0300 (MSK) Date: Mon, 23 Dec 1996 04:46:23 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= To: Joerg Wunsch Cc: FreeBSD-current users Subject: Re: sytem's default locale In-Reply-To: <199612211843.TAA11963@uriah.heep.sax.de> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Dec 1996, J Wunsch wrote: > As [?KOI8-R?] wrote: > > > It is no purpose to keep "system default" locale, all daemons must run > > at standard "C" locale. > > While i basically agree: Why that? Suppose we had a bunch of language > catalogs (like AIX), and our daemons would understand where to use > setlocale() and where not (unlike AIX :). There's IMHO no reason why > a particular system administrator should not express his wish to see > the syslog messages in his language -- after all, he is supposed to > read them. I not disagree in general, I mean _existen_ daemons. Do you try to login to "internationalized" ftpd f.e.? It is lot of fun when its locale have nothing common with your environment. Usualy daemos are the doors to the outer world, so they must not be language-dependend. While syslog messages can be... (or not?) F.e. you can't send your i18n'ed syslog messages to international discussion forum, if something is wrong happens with your daemon. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sun Dec 22 22:24:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA20575 for current-outgoing; Sun, 22 Dec 1996 22:24:45 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA20562 for ; Sun, 22 Dec 1996 22:24:24 -0800 (PST) Received: from localhost (davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) with SMTP id RAA24574; Mon, 23 Dec 1996 17:19:40 +1100 (EST) Date: Mon, 23 Dec 1996 17:19:39 +1100 (EST) From: David Nugent Reply-To: davidn@blaze.net.au To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= cc: freebsd-current@freebsd.org Subject: Re: Confused about locale In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by freefall.freebsd.org id WAA20569 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Dec 1996, [KOI8-R] áÎÄÒÅÊ þÅÒÎÏ×, Andrey Chernov wrote: >> > I dislike idea of "system default" locale, I like idea of "user >> > default" locale instead! >> >> Ok. There will be a way of achieving this shortly via login.conf. > >Not so quick, it will be nice if user can change his preferences >easily. The user can, by overriding the standard environment variables in his or her .login or .profile, just as they do now. The only thing the lang= and charset= entries in the login class affects are the defaults set by login in the user's environment. Editing startup files is no more difficult than running, say, chpass et al. >> The last part is more difficult. But the field is already there >> in "class". > >What is difficult here? As man says "class" is pointer to termcap-style >attributes. Do you mean that they must be unchangeable by user? Not at all. Only that "class" is a pointer to /many/ parameters that (1) set administrative restrictions and (2) sets up the *default* login environment for a set of users. For a shell account, most of the environment setup remains changeable, just as it is now. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Sun Dec 22 23:21:40 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA22702 for current-outgoing; Sun, 22 Dec 1996 23:21:40 -0800 (PST) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA22694 for ; Sun, 22 Dec 1996 23:21:36 -0800 (PST) Received: by sovcom.kiae.su id AA18411 (5.65.kiae-1 ); Mon, 23 Dec 1996 09:33:14 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 23 Dec 96 09:33:14 +0300 Received: from localhost (nagual.ru [127.0.0.1]) by nagual.ru (8.8.4/8.8.4) with ESMTP id JAA00669; Mon, 23 Dec 1996 09:32:38 +0300 (MSK) Date: Mon, 23 Dec 1996 09:32:38 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= To: davidn@blaze.net.au Cc: freebsd-current@freebsd.org Subject: Re: Confused about locale In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Dec 1996, David Nugent wrote: > On Mon, 23 Dec 1996, [KOI8-R] áÎÄÒÅÊ þÅÒÎÏ×, Andrey Chernov wrote: > > >> > I dislike idea of "system default" locale, I like idea of "user > >> > default" locale instead! > >> > >> Ok. There will be a way of achieving this shortly via login.conf. > > > >Not so quick, it will be nice if user can change his preferences > >easily. > > The user can, by overriding the standard environment variables in > his or her .login or .profile, just as they do now. The only > thing the lang= and charset= entries in the login class affects > are the defaults set by login in the user's environment. Editing > startup files is no more difficult than running, say, chpass et > al. Excepting one small thing: command interpreter itself started with system locale, not user defined one and user can change it only later (if ever can!). Shell f.e. understand on-the-fly locale changes only very recently (my fix). It is why I insist on locale setting _prior_ to command interpreter start, i.e. at login stage. > >> The last part is more difficult. But the field is already there > >> in "class". > > > >What is difficult here? As man says "class" is pointer to termcap-style > >attributes. Do you mean that they must be unchangeable by user? > > Not at all. Only that "class" is a pointer to /many/ parameters > that (1) set administrative restrictions and (2) sets up the > *default* login environment for a set of users. For a shell > account, most of the environment setup remains changeable, just > as it is now. Why not use "tc=" modifier to point to default class? I.e. example entry will looks like: la=ru_SU.KOI8-R:ch=KOI8-R:tc=def_class -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sun Dec 22 23:47:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA23840 for current-outgoing; Sun, 22 Dec 1996 23:47:54 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA23830 for ; Sun, 22 Dec 1996 23:47:48 -0800 (PST) Received: from localhost (davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) with SMTP id SAA25479; Mon, 23 Dec 1996 18:46:57 +1100 (EST) Date: Mon, 23 Dec 1996 18:46:57 +1100 (EST) From: David Nugent Reply-To: davidn@blaze.net.au To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= cc: freebsd-current@freebsd.org Subject: Re: Confused about locale In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by freefall.freebsd.org id XAA23835 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 23 Dec 1996, [KOI8-R] áÎÄÒÅÊ þÅÒÎÏ×, Andrey Chernov wrote: >> The user can, by overriding the standard environment variables in >> his or her .login or .profile, just as they do now. The only >> thing the lang= and charset= entries in the login class affects >> are the defaults set by login in the user's environment. Editing >> startup files is no more difficult than running, say, chpass et >> al. > >Excepting one small thing: command interpreter itself started >with system locale, not user defined one and user can change it >only later (if ever can!). Will "exec $SHELL" at the end of .profile solve this at all? Yes, I know it is a kludge. :) The other thing is that login.conf (BSDI's anyway, and no doubt ours when we get to implement it) will provide a way of execing an alternate program instead of a shell when the user logs in, but $SHELL is still set as per the passwd->pw_dir field. It would be a very simple matter to have this alternate pick up a $HOME/.language file or similar, then exec the shell as a login shell (as an alternate may have to do anyway). >Shell f.e. understand on-the-fly locale changes >only very recently (my fix). Yes, I understand that problem well enough. ;) >> Not at all. Only that "class" is a pointer to /many/ parameters >> that (1) set administrative restrictions and (2) sets up the >> *default* login environment for a set of users. For a shell >> account, most of the environment setup remains changeable, just >> as it is now. > >Why not use "tc=" modifier to point to default class? >I.e. example entry will looks like: > >la=ru_SU.KOI8-R:ch=KOI8-R:tc=def_class That's precisely how /etc/login.conf is formatted, yes. And a typical setup will involve a bunch of top-level defaults together with tc= entries to string them together. But this doesn't solve the user being able to modify them. [Pie in the sky idea] what could be done is to read $HOME/.login.env (name is only a suggestion) to pick up these things, but only *after* the setuid()/initgroups(), and with only some subset of keywords allowed in user mode. Some, like setting max-rlimits, only have meaning if running as root anyway. That would at least close all of the main holes and means of circumventing administrative policy this might otherwise allow. This doesn't much appeal to my sense of asthetics though, but it is similar to .termcap style user-configuration. Comments? [Incidently, getcap(3) doesn't have termcap's liminations with respect to two character identifiers - fortunately. :-) Files tend to be a lot more readable that way.] Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Mon Dec 23 01:51:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA26429 for current-outgoing; Mon, 23 Dec 1996 01:51:25 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA26421 for ; Mon, 23 Dec 1996 01:50:59 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA19696 for ; Mon, 23 Dec 1996 10:50:56 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA10405 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 10:50:55 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id KAA02149 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 10:39:09 +0100 (MET) From: J Wunsch Message-Id: <199612230939.KAA02149@uriah.heep.sax.de> Subject: Re: Confused about locale To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 23 Dec 1996 10:39:09 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "[?KOI8-R?]" at "Dec 23, 96 04:50:41 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As [?KOI8-R?] wrote: > > > I dislike idea of "system default" locale, I like idea of "user > > > default" locale instead! > > > > Ok. There will be a way of achieving this shortly via login.conf. > > Not so quick, it will be nice if user can change his preferences > easily. Yes. > > > There must be some field into passwd which indicates current user > > > startup locale which must be changeable by user via chpass. > > > > The last part is more difficult. But the field is already there > > in "class". > > What is difficult here? As man says "class" is pointer to termcap-style > attributes. Do you mean that they must be unchangeable by user? We should either extend chpass(1) to support more user-changeable options (preferred, since it's got a nice interface), or make pw(8) able to do this on behalf of the user (which also requires a user- usable frontend then). It's not only that certain parts of the login class should be changeable by the user, but e.g. for a site that maintains a `one group per user, and put them all into secondary groups' policy, the user should also be able to enable or disable people's access to `his' group without asking the sysadmin. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 23 01:53:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA26536 for current-outgoing; Mon, 23 Dec 1996 01:53:48 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id BAA26529 for ; Mon, 23 Dec 1996 01:53:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA19700 for ; Mon, 23 Dec 1996 10:50:57 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA10406 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 10:50:57 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id KAA02174 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 10:46:26 +0100 (MET) From: J Wunsch Message-Id: <199612230946.KAA02174@uriah.heep.sax.de> Subject: Re: sytem's default locale To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 23 Dec 1996 10:46:26 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "[?KOI8-R?]" at "Dec 23, 96 04:46:23 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Andrey wrote: > > While i basically agree: Why that? Suppose we had a bunch of language > > catalogs (like AIX), and our daemons would understand where to use > > setlocale() and where not (unlike AIX :). There's IMHO no reason why > > a particular system administrator should not express his wish to see > > the syslog messages in his language -- after all, he is supposed to > > read them. > > I not disagree in general, I mean _existen_ daemons. > Do you try to login to "internationalized" ftpd f.e.? It is lot > of fun when its locale have nothing common with your environment. That's why i mentioned AIX above: they apparently dumped a setlocale(LC_ALL, "") into each and any program back in AIX 3.x.x, causing the effect you're describing. You could indeed get German SMTP error mails from their sendmail... Even worse, some version of AIX is said that double pi = 3.1415926; caused a syntax error if your $LANG was set to German, since the compiler stupidly expected it to look like: double pi = 3,1415926; then. :-) Our programs do not suffer from this problem since you've been careful enough to not make the same mistake. All the daemons would start up in the C locale even if there were already a system's default locale, since they don't call setlocale() yet. If they ever start doing this, they must be careful where this is appropriate and where not. > While syslog messages can be... (or not?) > F.e. you can't send your i18n'ed syslog messages to international > discussion forum, if something is wrong happens with your daemon. But that's the administrator's will then. Nobody tells him that he _must_ set a system's default locale, but it would probably be nice if he _can_ do it. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 23 01:59:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA26724 for current-outgoing; Mon, 23 Dec 1996 01:59:20 -0800 (PST) Received: from jalopeno.nixu.fi (jalopeno.nixu.fi [194.197.118.20]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA26719 for ; Mon, 23 Dec 1996 01:59:16 -0800 (PST) Received: from flauta.nixu.fi (flauta.nixu.fi [194.197.118.35]) by jalopeno.nixu.fi (8.8.3/8.8.3) with ESMTP id LAA06483 for ; Mon, 23 Dec 1996 11:58:38 +0200 (EET) Date: Mon, 23 Dec 1996 11:58:39 +0200 (EET) From: Marko Lamminen Reply-To: Marko Lamminen Subject: Re: How many worldstones ? To: FreeBSD-current@FreeBSD.ORG In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The make world run has been taking about 4.5 hours including everything, > no arguments supplied to make, how does this compare with others ? 3 hours 20 minutes to compile world.(from scratch) btw. Is anyone else here using the Hayes ESP card? It works ok except that when I try to close the port it totally hangs the system, which is is pretty annoying (having to hard reset everytime I hang up). The two regular sio's work just fine. - Marko From owner-freebsd-current Mon Dec 23 02:23:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA27797 for current-outgoing; Mon, 23 Dec 1996 02:23:42 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA27791 for ; Mon, 23 Dec 1996 02:23:36 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id VAA18449; Mon, 23 Dec 1996 21:19:37 +1100 Date: Mon, 23 Dec 1996 21:19:37 +1100 From: Bruce Evans Message-Id: <199612231019.VAA18449@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, j@uriah.heep.sax.de Subject: Re: Making an option `supported' Cc: toor@dyson.iquest.net Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >(regarding how to make a kernel option `supported') > >> Thanks, I didn't even know what was necessary to do it. > >Well, fairly simple: > >First, edit sys/conf/options (or sys/i386/conf/options.i386), and >select an opt_foo.h file where your new option would best go into. > >If there's already something that comes close to the purpose of the >new option, pick this. As for the MAXDSIZ option, i felt that >opt_rlimit.h was a good choice (the OPEN_MAX and CHILD_MAX options >already went there). > >If there's no opt_foo.h already available for the intended new option, >invent a new name. Make it meaningful, and comment the new section in >the options[.i386] file. config(8) will automagically pick up the >change, and create that file next time it is run. Most options should go in a header file by themself. Then the option file is automatically given a name related to the option if the file name is not given explicitly: option BAR -> file name opt_bar.h. >Packing too many options into a single opt_foo.h will cause too many >kernel files to be rebuilt when one of the options has been changed in >the config file, Right. opt_rlimit.h isn't all that good a choice for the new options. This header now has to be included in lots of places that have nothing to do with the OPEN_MAX and CHILD_MAX options. This defeats the point of defining the options in separate files. >while creating too many opt_foo.h's does apparently >no good either. It just increases the compilation overheads a little. It may force you to edit more files when you add a related option. This is an advantage :-). >Finally, find out which kernel files depend on the new option. > > find /sys -name type f | xargs fgrep NEW_OPTION > >is your friend in finding them. Go and edit all those files, and >add > >#include "opt_foo.h" You forgot the most important point :-): if a system header needs to be edited, then don't add the option. E.g., the CHILD_MAX and OPEN_MAX options should never have existed, because they break . The MAXDSIZ and DFLDSIZ options should not exist, since they break . "opt_foo.h" can't be included since it would break the headers more seriously, but if it isn't included, then places that include it may get an inconsistent value for the option. Bugs in config related to this: when an option is removed from conf/options [.machine], the option isn't removed from the opt_foo.h file. Bruce From owner-freebsd-current Mon Dec 23 02:51:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA28608 for current-outgoing; Mon, 23 Dec 1996 02:51:33 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA28601 for ; Mon, 23 Dec 1996 02:51:28 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA28572 for ; Mon, 23 Dec 1996 11:50:56 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA11083 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 11:50:55 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id LAA02881 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 11:27:56 +0100 (MET) From: J Wunsch Message-Id: <199612231027.LAA02881@uriah.heep.sax.de> Subject: Re: Confused about locale To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 23 Dec 1996 11:27:56 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from David Nugent at "Dec 23, 96 06:46:57 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As David Nugent wrote: > Will "exec $SHELL" at the end of .profile solve this at all? Yes, > I know it is a kludge. :) It's a crock: the shell will no longer recognize itself as a login shell, since its argv[0] does no longer start with a dash then. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 23 04:08:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA00488 for current-outgoing; Mon, 23 Dec 1996 04:08:43 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA00475 for ; Mon, 23 Dec 1996 04:08:11 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA09443 for ; Mon, 23 Dec 1996 13:08:06 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA13491 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 13:08:06 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id MAA03543 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 12:59:29 +0100 (MET) From: J Wunsch Message-Id: <199612231159.MAA03543@uriah.heep.sax.de> Subject: Re: Making an option `supported' To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 23 Dec 1996 12:59:29 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612231019.VAA18449@godzilla.zeta.org.au> from Bruce Evans at "Dec 23, 96 09:19:37 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > Most options should go in a header file by themself. Then the option > file is automatically given a name related to the option if the file > name is not given explicitly: option BAR -> file name opt_bar.h. > You forgot the most important point :-): if a system header needs to be > edited, then don't add the option. E.g., the CHILD_MAX and OPEN_MAX > options should never have existed, because they break . (etc.) Ok, i've merged this with my original posting, and are about adding it to the handbook right now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 23 04:47:17 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA02611 for current-outgoing; Mon, 23 Dec 1996 04:47:17 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA02601 for ; Mon, 23 Dec 1996 04:47:14 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id EAA09969 for ; Mon, 23 Dec 1996 04:30:44 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id XAA21961 for current@freebsd.org; Mon, 23 Dec 1996 23:30:33 +1100 Date: Mon, 23 Dec 1996 23:30:33 +1100 From: Bruce Evans Message-Id: <199612231230.XAA21961@godzilla.zeta.org.au> To: current@freebsd.org Subject: cxconfig bits rotting Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why is cxconfig `#NOTYET' in /usr/src/sbin/i386/Makefile? It no longer compiles now that doesn't include . Bruce From owner-freebsd-current Mon Dec 23 05:06:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA03080 for current-outgoing; Mon, 23 Dec 1996 05:06:18 -0800 (PST) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA03073 for ; Mon, 23 Dec 1996 05:06:14 -0800 (PST) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id NAA22479 for ; Mon, 23 Dec 1996 13:06:17 GMT Date: Mon, 23 Dec 1996 13:06:16 +0000 (GMT) From: Developer To: freebsd-current@freebsd.org Subject: Wine on Freebsd Current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone got any ideas why the new version of Wine does not work with the freebsd-current kernel? I get an error saying: i386_set_ldt: Invalid argument Did you reconfigure the kernel with "options USER_LDT"? But USER_LDT is enabled in the kernel, along with linux emulation?? Regards, Trefor S. From owner-freebsd-current Mon Dec 23 09:18:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA10511 for current-outgoing; Mon, 23 Dec 1996 09:18:18 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA10505 for ; Mon, 23 Dec 1996 09:18:11 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-9.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA00465 (5.67b/IDA-1.5 for ); Mon, 23 Dec 1996 18:17:47 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id OAA01479; Mon, 23 Dec 1996 14:56:27 +0100 (CET) Message-Id: Date: Mon, 23 Dec 1996 14:55:07 +0100 From: se@freebsd.org (Stefan Esser) To: dev@fgate.flevel.co.uk (Developer) Cc: freebsd-current@freebsd.org Subject: Re: Wine on Freebsd Current References: X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 In-Reply-To: ; from Developer on Dec 23, 1996 13:06:16 +0000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Dec 23, dev@fgate.flevel.co.uk (Developer) wrote: > > Has anyone got any ideas why the new version of Wine does not work with > the freebsd-current kernel? > > I get an error saying: > > i386_set_ldt: Invalid argument > Did you reconfigure the kernel with "options USER_LDT"? > > But USER_LDT is enabled in the kernel, along with linux emulation?? You need to put back the following file contents into /usr/ports/emulators/wine/patches/patch-an: ---- 8< cut here ---- 8< cut here ---- 8< cut here ---- 8< cut here ---- *** memory/selector.c~ Fri Sep 13 18:47:32 1996 --- memory/selector.c Tue Oct 1 19:51:10 1996 *************** *** 14,18 **** --- 14,22 ---- + #ifdef __FreeBSD__ + #define FIRST_LDT_ENTRY_TO_ALLOC 17 + #else #define FIRST_LDT_ENTRY_TO_ALLOC 6 + #endif ---- 8< cut here ---- 8< cut here ---- 8< cut here ---- 8< cut here ---- Since this was no longer necessary under -current, but reduces the number of usable LDT entries, I had removed it, but had not considered that it is still required for older FreeBSD kernes. Sorry for the inconvenience caused by this! I will add this patch back when I commit the upgrade to Wine-96.12.22 to the ports tree, later this week ... Regards, STefan From owner-freebsd-current Mon Dec 23 10:50:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA14955 for current-outgoing; Mon, 23 Dec 1996 10:50:41 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA14949 for ; Mon, 23 Dec 1996 10:50:38 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA09106 for ; Mon, 23 Dec 1996 19:50:34 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA19651 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 19:50:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id TAA05349 for freebsd-current@FreeBSD.org; Mon, 23 Dec 1996 19:28:48 +0100 (MET) From: J Wunsch Message-Id: <199612231828.TAA05349@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/i386/conf LINT To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 23 Dec 1996 19:28:48 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612231716.EAA28322@godzilla.zeta.org.au> from Bruce Evans at "Dec 24, 96 04:16:06 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (Time to move it to -current now.) As Bruce Evans wrote: > It would be nice to specify the limit per user, but doing it with > sysctl ... ...is a crock. Nope, don't do it. David Nugent has the prototype implementation of login classes ready. That's the way where you could put up per-user(class) initial limits. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 23 11:19:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA17589 for current-outgoing; Mon, 23 Dec 1996 11:19:16 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA17545; Mon, 23 Dec 1996 11:19:10 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id LAA10438 ; Mon, 23 Dec 1996 11:06:45 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id LAA06190; Mon, 23 Dec 1996 11:06:05 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.ORG (FreeBSD-current users), sef@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf LINT In-reply-to: Your message of "Mon, 23 Dec 1996 19:28:48 +0100." <199612231828.TAA05349@uriah.heep.sax.de> Date: Mon, 23 Dec 1996 11:06:04 -0800 Message-ID: <6159.851367964@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > David Nugent has the prototype implementation of login classes ready. > That's the way where you could put up per-user(class) initial limits. Didn't sef also have something he was doing which would also be BSD/OS compatible? Or am I thinking of a different type of login class extention here? Jordan From owner-freebsd-current Mon Dec 23 11:23:25 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA18001 for current-outgoing; Mon, 23 Dec 1996 11:23:25 -0800 (PST) Received: from kithrup.com (kithrup.com [205.179.156.40]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA17996 for ; Mon, 23 Dec 1996 11:23:17 -0800 (PST) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id LAA28922; Mon, 23 Dec 1996 11:23:17 -0800 Date: Mon, 23 Dec 1996 11:23:17 -0800 From: Sean Eric Fagan Message-Id: <199612231923.LAA28922@kithrup.com> To: jkh@time.cdrom.com, joerg_wunsch@uriah.heep.sax.de Subject: Re: cvs commit: src/sys/i386/conf LINT Cc: freebsd-current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I did the login class library stuff... it was bsd/os compatible. Keith, however, told me that they would be releasing their code once it settled down, so I dropped the project. (I was never able to get anyone interested in changing the necessary utilities, and writing the per-class authentication programs. Well, Guido for s/key, but that was about it ;).) I can make the code available if anyone wants. BTW, I'm going to be unavailable for email for a week, starting tomorrow. Sean. From owner-freebsd-current Mon Dec 23 11:52:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA19264 for current-outgoing; Mon, 23 Dec 1996 11:52:21 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA19251; Mon, 23 Dec 1996 11:52:09 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA18168; Mon, 23 Dec 1996 20:51:18 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA20553; Mon, 23 Dec 1996 20:51:17 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id UAA05988; Mon, 23 Dec 1996 20:36:04 +0100 (MET) From: J Wunsch Message-Id: <199612231936.UAA05988@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/i386/conf LINT To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 23 Dec 1996 20:36:03 +0100 (MET) Cc: sef@FreeBSD.org, davidn@blaze.net.au (David Nugent) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <6159.851367964@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 23, 96 11:06:04 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > David Nugent has the prototype implementation of login classes ready. > > That's the way where you could put up per-user(class) initial limits. > > Didn't sef also have something he was doing which would also be BSD/OS > compatible? Or am I thinking of a different type of login class > extention here? To quote David (without his permission) on this: > I have > attempted to contact SEF about this, as I was told he was > working on an implementation for FreeBSD there, but have not > be able to raise a response, and I needed this facility now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Mon Dec 23 12:44:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA21764 for current-outgoing; Mon, 23 Dec 1996 12:44:49 -0800 (PST) Received: from kithrup.com (kithrup.com [205.179.156.40]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA21759 for ; Mon, 23 Dec 1996 12:44:47 -0800 (PST) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id MAA02354; Mon, 23 Dec 1996 12:44:43 -0800 Date: Mon, 23 Dec 1996 12:44:43 -0800 From: Sean Eric Fagan Message-Id: <199612232044.MAA02354@kithrup.com> To: jkh@time.cdrom.com Subject: Re: cvs commit: src/sys/i386/conf LINT Newsgroups: kithrup.freebsd.current In-Reply-To: <6159.851367964.kithrup.freebsd.current@time.cdrom.com> References: Your message of "Mon, 23 Dec 1996 19:28:48 +0100." <199612231828.TAA05349@uriah.heep.sax.de> Organization: Kithrup Enterprises, Ltd. Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Okay, I placed the code on freefall, in ~sef. (Uh... login_classes.tgz.) Please feel free to examine, use, rewrite, or trash it ;). As I said, any comments to me after today will have to wait a week. Sean. From owner-freebsd-current Mon Dec 23 13:46:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA24693 for current-outgoing; Mon, 23 Dec 1996 13:46:53 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA24686; Mon, 23 Dec 1996 13:46:48 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16233(8)>; Mon, 23 Dec 1996 13:46:14 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177712>; Mon, 23 Dec 1996 13:46:03 -0800 To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= cc: FreeBSD-current , fenner@freebsd.org Subject: Re: mtest: overloaded name, name change request In-reply-to: Your message of "Fri, 20 Dec 96 23:38:45 PST." Date: Mon, 23 Dec 1996 13:45:52 PST From: Bill Fenner Message-Id: <96Dec23.134603pst.177712@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This particular mtest has been publically available and named mtest since 1989; so a new name will certainly take some adjustment. It's possible that a man page alias would be enough, since mtest isn't used often it might be acceptable to make people look its new name up every time they want to use it. Bill From owner-freebsd-current Mon Dec 23 15:31:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA28778 for current-outgoing; Mon, 23 Dec 1996 15:31:45 -0800 (PST) Received: from uhura.my.domain (slip3.edvz.uni-linz.ac.at [140.78.5.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA28769 for ; Mon, 23 Dec 1996 15:31:41 -0800 (PST) Received: from spock.my.domain (spock [192.168.1.3]) by uhura.my.domain (8.8.4/8.6.9) with ESMTP id AAA00174 for ; Tue, 24 Dec 1996 00:30:05 +0100 (MET) Received: (from cg@localhost) by spock.my.domain (8.8.4/8.7.3) id AAA00191; Tue, 24 Dec 1996 00:28:31 +0100 (CET) Date: Tue, 24 Dec 1996 00:28:31 +0100 (CET) From: Christian Gusenbauer Reply-To: cg@archimedia.khs-linz.ac.at To: freebsd-current@freebsd.org Subject: DAT: reading with blocksize=256K Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! I just got a DAT cartridge with a tar backup. It seems that the backup was made with a blocksize of 256K. Isn't it possible to get the data into my pc with current (it looks like there's a limit of 64K)?? I tried "tar tvb 512" but that failed. Any clues? Many thanks, Christian. -- Christian Gusenbauer "It's easier to change the specification cg@archimedia.khs-linz.ac.at to fit the program than vice versa." From owner-freebsd-current Mon Dec 23 23:52:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA13836 for current-outgoing; Mon, 23 Dec 1996 23:52:15 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA13828 for ; Mon, 23 Dec 1996 23:52:10 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA15798; Tue, 24 Dec 1996 08:52:02 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA29603; Tue, 24 Dec 1996 08:52:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id IAA10234; Tue, 24 Dec 1996 08:47:35 +0100 (MET) From: J Wunsch Message-Id: <199612240747.IAA10234@uriah.heep.sax.de> Subject: Re: DAT: reading with blocksize=256K To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Tue, 24 Dec 1996 08:47:35 +0100 (MET) Cc: cg@archimedia.khs-linz.ac.at Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Christian Gusenbauer at "Dec 24, 96 00:28:31 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Christian Gusenbauer wrote: > I just got a DAT cartridge with a tar backup. It seems that the backup > was made with a blocksize of 256K. Isn't it possible to get the data into > my pc with current (it looks like there's a limit of 64K)?? This has been discussed at lenth already: it's currently limited by physio(9) to chunks of at most 64 KB size, due to the limitations in the scatter/gather list of some SCSI controllers that don't allow for more than 16 scatter/gather segments. A better scheme needs to be worked out. Right now, you gotta tell your friends at the SGI machine (i bet that's where your tape came from, they are the only system with such a braindead default) to write with a better suited blocksize, like the 10 KB that tar(1) defaults to on any other system in the world. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Dec 24 03:33:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA19072 for current-outgoing; Tue, 24 Dec 1996 03:33:11 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA19067 for ; Tue, 24 Dec 1996 03:33:06 -0800 (PST) Received: from localhost (davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) with SMTP id WAA06634 for ; Tue, 24 Dec 1996 22:32:59 +1100 (EST) Date: Tue, 24 Dec 1996 22:32:58 +1100 (EST) From: David Nugent Reply-To: davidn@blaze.net.au To: FreeBSD-current Mailing List Subject: Problems with sshd and -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Over the last few days I've noticed an oddity. One time it was a little more than that in that it caused memory/cpu starvation on the system it affected, and subsequently resulted in a crash. :-( Anyway, this is using -current (as of the today). ssh into the box shows: root 16004 0.0 2.4 308 716 ?? Is 10:16PM 0:01.83 /usr/local/sbin/sshd root 16007 0.0 3.1 340 936 ?? S 10:16PM 0:00.33 /usr/local/sbin/sshd Looks reasonable. Logout, ssh back in: root 16007 71.3 29.9 8404 9080 ?? R 10:16PM 0:26.32 /usr/local/sbin/sshd root 16004 0.0 2.3 308 684 ?? Is 10:16PM 0:01.83 /usr/local/sbin/sshd root 16076 0.6 3.0 340 900 ?? S 10:19PM 0:00.33 /usr/local/sbin/sshd Yow, 8 meg! Top shows: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 16007 root 92 0 8404K 9080K RUN 1:00 93.16% 93.15% sshd So it has gone into CPU tailspin as well. Does anyone have any ideas before I recompile with debugging info and see what in hell it is doing? ssh to a box running 2.2-ALPHA sitting right alongside works fine, without exhibiting this behaviour, and another remote box I often use running 2.1.5 also works fine (not to mentione freebsd.org's 2.1.6). The version of ssh in all cases is 1.2.17. Merry Christmas or happy holidays to everyone, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Tue Dec 24 03:46:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA19705 for current-outgoing; Tue, 24 Dec 1996 03:46:49 -0800 (PST) Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA19700 for ; Tue, 24 Dec 1996 03:46:42 -0800 (PST) Received: from localhost (davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) with SMTP id WAA06759 for ; Tue, 24 Dec 1996 22:46:37 +1100 (EST) Date: Tue, 24 Dec 1996 22:46:37 +1100 (EST) From: David Nugent Reply-To: davidn@blaze.net.au To: FreeBSD-current Mailing List Subject: Re: Problems with sshd and -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Dec 1996, David Nugent wrote: >Yow, 8 meg! Top shows: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND >16007 root 92 0 8404K 9080K RUN 1:00 93.16% 93.15% sshd > >So it has gone into CPU tailspin as well. A quick attach shows that it is in a signal handling loop: #5 0x80c9490 in fstat () #6 0x80ca76f in malloc () #7 0x80c8937 in __smakebuf () #8 0x80c88c7 in __swsetup () #9 0x80c3b53 in vfprintf () #10 0x80c3631 in fprintf () #11 0x1b1f6 in signal_handler (sig=6) at signals.c:49 #12 0xefbfdfdc in end () #13 0x80c9441 in fstat () #14 0x80c9490 in fstat () #15 0x80ca76f in malloc () #16 0x80c8937 in __smakebuf () #17 0x80c88c7 in __swsetup () #18 0x80c3b53 in vfprintf () #19 0x80c3631 in fprintf () #20 0x1b1f6 in signal_handler (sig=6) at signals.c:49 #21 0xefbfdfdc in end () .. and so on. Uh, I just noticed that removing /etc/malloc.conf "fixes" the problem (which answers the question as to why it works elsewhere. :-)).. Ok, looks like an sshd bug, not -current. We now return you to your usual program or droll Christmas classics... Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Tue Dec 24 16:16:34 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA14924 for current-outgoing; Tue, 24 Dec 1996 16:16:34 -0800 (PST) Received: from fools.ecpnet.com (root@fools.ecpnet.com [204.246.64.101]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA14918 for ; Tue, 24 Dec 1996 16:16:31 -0800 (PST) Received: from localhost (root@localhost) by fools.ecpnet.com (8.8.4/8.8.4) with SMTP id SAA00215 for ; Tue, 24 Dec 1996 18:15:03 -0600 (CST) Date: Tue, 24 Dec 1996 18:15:00 -0600 (CST) From: Charlie ROOT To: freebsd-current@freebsd.org Subject: options ASYNCH Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The ASYNCH define to fix the keyboard lockups when switching vty's appears to be gone in 2.2 and 3.0. So now when I switch vty's my keyboard locks and I need to reset it by unplugging it, then plugging it back in. Is there another work around? I tried patching in the 2.1.6 asynch stuff but syscons and related files have changed to much. From owner-freebsd-current Tue Dec 24 16:44:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA17823 for current-outgoing; Tue, 24 Dec 1996 16:44:18 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA17809 for ; Tue, 24 Dec 1996 16:44:09 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-18.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA24399 (5.67b/IDA-1.5 for ); Wed, 25 Dec 1996 01:44:04 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id BAA01001; Wed, 25 Dec 1996 01:44:02 +0100 (CET) Message-Id: Date: Wed, 25 Dec 1996 01:44:01 +0100 From: se@freebsd.org (Stefan Esser) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org (FreeBSD-current users), cg@archimedia.khs-linz.ac.at Subject: Re: DAT: reading with blocksize=256K References: <199612240747.IAA10234@uriah.heep.sax.de> X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 In-Reply-To: <199612240747.IAA10234@uriah.heep.sax.de>; from J Wunsch on Dec 24, 1996 08:47:35 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Dec 24, j@uriah.heep.sax.de (J Wunsch) wrote: > As Christian Gusenbauer wrote: > > > I just got a DAT cartridge with a tar backup. It seems that the backup > > was made with a blocksize of 256K. Isn't it possible to get the data into > > my pc with current (it looks like there's a limit of 64K)?? > > This has been discussed at lenth already: it's currently limited by > physio(9) to chunks of at most 64 KB size, due to the limitations in > the scatter/gather list of some SCSI controllers that don't allow for > more than 16 scatter/gather segments. I can't talk for any other driver, but in case of the NCR driver, a simple rebuild of the kernel with MAX_SCATTER (in /sys/pci/ncr.c) set to 129 will allow to read 256KB tape blocks. (I guess the same is true for most other SCSI host adapters, that don't have a lower adapter firmware limit.) The drivers may be sub-optimal for typical (shorter) transfers, then, but if you just need to read THAT tape ... Regards, STefan From owner-freebsd-current Tue Dec 24 17:08:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA19454 for current-outgoing; Tue, 24 Dec 1996 17:08:24 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA19416; Tue, 24 Dec 1996 17:07:47 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id UAA01427; Tue, 24 Dec 1996 20:06:28 -0500 (EST) From: "John S. Dyson" Message-Id: <199612250106.UAA01427@dyson.iquest.net> Subject: Re: DAT: reading with blocksize=256K To: se@freebsd.org (Stefan Esser) Date: Tue, 24 Dec 1996 20:06:23 -0500 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org, cg@archimedia.khs-linz.ac.at In-Reply-To: from "Stefan Esser" at Dec 25, 96 01:44:01 am X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Dec 24, j@uriah.heep.sax.de (J Wunsch) wrote: > > As Christian Gusenbauer wrote: > > > > > I just got a DAT cartridge with a tar backup. It seems that the backup > > > was made with a blocksize of 256K. Isn't it possible to get the data into > > > my pc with current (it looks like there's a limit of 64K)?? > > > > This has been discussed at lenth already: it's currently limited by > > physio(9) to chunks of at most 64 KB size, due to the limitations in > > the scatter/gather list of some SCSI controllers that don't allow for > > more than 16 scatter/gather segments. > > I can't talk for any other driver, but in case of the NCR driver, > a simple rebuild of the kernel with MAX_SCATTER (in /sys/pci/ncr.c) > set to 129 will allow to read 256KB tape blocks. > Since it is that simple in the driver level for at least one of our SCSI interfaces, then it might be desirable to start supporting larger physio's. I have a bit of technology in mind to support bigger I/O. Since I use NCR controllers, I'll look into it soon. It would be neat to also support larger than 64K clustered reads/writes. Thanks for the info!!! John dyson@freebsd.org From owner-freebsd-current Tue Dec 24 21:24:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA27975 for current-outgoing; Tue, 24 Dec 1996 21:24:43 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA27970 for ; Tue, 24 Dec 1996 21:24:40 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA09841; Tue, 24 Dec 1996 22:20:58 -0700 (MST) Date: Tue, 24 Dec 1996 22:20:58 -0700 (MST) Message-Id: <199612250520.WAA09841@rocky.mt.sri.com> From: Nate Williams To: Charlie ROOT Cc: freebsd-current@freebsd.org Subject: Re: options ASYNCH In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The ASYNCH define to fix the keyboard lockups when switching vty's appears > to be gone in 2.2 and 3.0. So now when I switch vty's my keyboard locks > and I need to reset it by unplugging it, then plugging it back in. Is > there another work around? Try using 2.2-Beta and see if it helps. Nate From owner-freebsd-current Tue Dec 24 22:25:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA29808 for current-outgoing; Tue, 24 Dec 1996 22:25:20 -0800 (PST) Received: from fools.ecpnet.com (moke@fools.ecpnet.com [204.246.64.101]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id WAA29802 for ; Tue, 24 Dec 1996 22:25:17 -0800 (PST) Received: from localhost (moke@localhost) by fools.ecpnet.com (8.8.4/8.8.4) with SMTP id AAA00218; Wed, 25 Dec 1996 00:23:49 -0600 (CST) Date: Wed, 25 Dec 1996 00:23:48 -0600 (CST) From: Jimbo Bahooli To: Nate Williams cc: Charlie ROOT , freebsd-current@freebsd.org Subject: Re: options ASYNCH In-Reply-To: <199612250520.WAA09841@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 24 Dec 1996, Nate Williams wrote: > > The ASYNCH define to fix the keyboard lockups when switching vty's appears > > to be gone in 2.2 and 3.0. So now when I switch vty's my keyboard locks > > and I need to reset it by unplugging it, then plugging it back in. Is > > there another work around? > > Try using 2.2-Beta and see if it helps. > > > Nate > I'm tracking the RELENG_2_2 branch, and I made world the day 2.2-BETA came out so I'm running its equal. Possibly even with a few more fixes, so that didn't help. :) From owner-freebsd-current Wed Dec 25 04:02:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA06710 for current-outgoing; Wed, 25 Dec 1996 04:02:07 -0800 (PST) Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA06704 for ; Wed, 25 Dec 1996 04:01:54 -0800 (PST) Received: by nasu.utsunomiya-u.ac.jp (5.57/ULTRIX-940302) id AA21570; Wed, 25 Dec 96 20:58:27 +0900 Received: by outmail.utsunomiya-u.ac.jp (5.57/ULTRIX-940909) id AA13010; Wed, 25 Dec 96 20:58:25 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id VAA07663; Wed, 25 Dec 1996 21:01:41 +0900 (JST) Message-Id: <199612251201.VAA07663@zodiac.mech.utsunomiya-u.ac.jp> To: Jimbo Bahooli Cc: Nate Williams , freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: options ASYNCH In-Reply-To: Your message of "Wed, 25 Dec 1996 00:23:48 CST." References: Date: Wed, 25 Dec 1996 21:01:38 +0900 From: Kazutaka YOKOTA Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Tue, 24 Dec 1996, Nate Williams wrote: > >> > The ASYNCH define to fix the keyboard lockups when switching vty's appears >> > to be gone in 2.2 and 3.0. So now when I switch vty's my keyboard locks >> > and I need to reset it by unplugging it, then plugging it back in. Is >> > there another work around? >> >> Try using 2.2-Beta and see if it helps. >> >> >> Nate >> > >I'm tracking the RELENG_2_2 branch, and I made world the day 2.2-BETA came >out so I'm running its equal. Possibly even with a few more fixes, so that >didn't help. :) I think we need more details to diagnose your problem. Does lockup happen when switching between the X server and vty's? Do you have a PS/2 mouse and `psm' enabled? If so, does the X server access the mouse via `moused'? Is there any error message on the console or in `/var/log/messages'? Kazu From owner-freebsd-current Wed Dec 25 07:38:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA14583 for current-outgoing; Wed, 25 Dec 1996 07:38:35 -0800 (PST) Received: from scrooge.ee.swin.oz.au (scrooge.ee.swin.oz.au [136.186.4.20]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA14578 for ; Wed, 25 Dec 1996 07:38:32 -0800 (PST) Received: (from dtc@localhost) by scrooge.ee.swin.oz.au (8.6.9/8.6.9) id CAA19656 for current@FreeBSD.org; Thu, 26 Dec 1996 02:40:32 +1100 From: Douglas Thomas Crosher Message-Id: <199612251540.CAA19656@scrooge.ee.swin.oz.au> Subject: Invalid Argument error writing to closed socket. To: current@FreeBSD.org Date: Thu, 26 Dec 1996 02:40:32 +1100 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I've been tracking a problem which occcurs when writing to a TCP socket for which the remote end has closed the connection - a write returns an Invalid Argument error, however I suspect that it should signal SIGPIPE. The relevant parts of a ktrace are included below. If anyone has any ideas I'd be grateful for some help. This is for a http server which persistent connections. Trouble occurs because the server thinks the connection is still live - I'm currently using getpeername to check. Is there a better more reliable way to determine if the connection is still live? Running FreeBSD-current 24/12/96. Regards Douglas Crosher -=-=-=- >From a ktrace log: At this point file descriptor 6 is a TCP socket, and the other end has closed the connection. A read returns 0 bytes i.e. EOF. 198 lisp CALL read(0x6,0x803b000,0x1000) 198 lisp GIO fd 6 read 0 bytes "" 198 lisp RET read 0 getpeername is not aware the connection is closed yet. 198 lisp CALL getpeername(0x6,0xefbfd8b0,0xefbfd8ac) 198 lisp RET getpeername 0 The next write returns an Invalid Argument error. However I'm confident that all the arguments are valid. Since the remote connection has closed the connection I expected a SIGPIPE error. 198 lisp CALL write(0x6,0x8040000,0x8d) 198 lisp RET write -1 errno 22 Invalid argument <<<<<<< The next write does give a SIGPIPE: 198 lisp CALL write(0x6,0x8040000,0x14) 198 lisp PSIG SIGPIPE caught handler=0x5564 mask=0x0 code=0x0 198 lisp RET write -1 errno 32 Broken pipe -=-=-=-=- From owner-freebsd-current Wed Dec 25 13:35:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23154 for current-outgoing; Wed, 25 Dec 1996 13:35:52 -0800 (PST) Received: from isua1.iastate.edu (isua1.iastate.edu [129.186.1.132]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA23149 for ; Wed, 25 Dec 1996 13:35:50 -0800 (PST) From: ccsanady@iastate.edu Received: by isua1.iastate.edu with sendmail-5.65 id ; Wed, 25 Dec 1996 15:35:50 -0600 Date: Wed, 25 Dec 1996 15:35:50 -0600 Message-Id: <9612252135.AA04491@isua1.iastate.edu> To: current@freebsd.org Subject: ps/2 mouse problems in 2.2-BETA.. Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been experiencing some problems with mouse in this beta. What seems to happen is when the system is hevily swapping, and there is a lot of mouse movement, the cursor goes insane. It will zip around the screen, click randomly and such for a while. The thing is, I know its not just queued requests, because I see actions that I know I never performed with the mouse. It's almost as though the buffer was filled with junk, very odd. Anyone else had, or seen this? I figured it was due to the recent ps/2 mouse/console problems.. is this possible? thanks, chris btw, please cc me, im not on the lists over break.. From owner-freebsd-current Wed Dec 25 17:16:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA29785 for current-outgoing; Wed, 25 Dec 1996 17:16:20 -0800 (PST) Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA29772 for ; Wed, 25 Dec 1996 17:16:08 -0800 (PST) Received: by nasu.utsunomiya-u.ac.jp (5.57/ULTRIX-940302) id AA22651; Thu, 26 Dec 96 09:33:27 +0900 Received: by outmail.utsunomiya-u.ac.jp (5.57/ULTRIX-940909) id AA14287; Thu, 26 Dec 96 09:33:25 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA20114; Thu, 26 Dec 1996 09:36:43 +0900 (JST) Message-Id: <199612260036.JAA20114@zodiac.mech.utsunomiya-u.ac.jp> To: ccsanady@iastate.edu Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: ps/2 mouse problems in 2.2-BETA.. In-Reply-To: Your message of "Wed, 25 Dec 1996 15:35:50 CST." <9612252135.AA04491@isua1.iastate.edu> References: <9612252135.AA04491@isua1.iastate.edu> Date: Thu, 26 Dec 1996 09:36:41 +0900 From: Kazutaka YOKOTA Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have been experiencing some problems with mouse in this beta. What >seems to happen is when the system is hevily swapping, and there is a >lot of mouse movement, the cursor goes insane. It will zip around the >screen, click randomly and such for a while. The thing is, I know its not >just queued requests, because I see actions that I know I never performed >with the mouse. It's almost as though the buffer was filled with junk, >very odd. The most likely explanation is that the mouse and the X server have become out of sync due to a lost interrupt. Assuming you are using XFree86 and the X server is not accessing the mouse via `moused', you can switch away from X to a vty then come back to the X, and they will re-sync. This should work because the XFree86 server opens the mouse device only when it is in the foreground; it closes the mouse device when the user switches away from the X server, thus, flipping between the X server and a vty should close and re-open the device and give the X and the mouse a chance to re-sync. Unlike serial mice, it is not easy to ensure the PS/2 mouse and the driver are synchronized ;-< By default, the `psm' driver does not check the header byte of the 3-byte status data packet from the PS/2 mouse (in order to support the ALPS GlidePoint device). You may put `options PSM_CHECKSYNC' in the kernel configuration file to enable the minimal sync check feature in the `psm' driver. But, the check is minimal; you may still see the problem. When you do, click any mouse button without moving the mouse and the driver will find the header byte. The trick should work even when the mouse is accessed via `moused'. The `psm' driver in 2.2-BETA shares a common set of routines (kbdio) with the `syscons' driver to access the keyboard controller to which the PS/2 mouse port is wired. Because the routines are new, they need extensive testing. Please try the tricks above and tell me if they work. By the way, the `psm' driver in 2.1.X does not check the header byte either, and can easily go out of sync with the mouse. Did your system have the same problem under 2.1.X? If so, was the problem better or worse than now? Kazu >Anyone else had, or seen this? I figured it was due to the recent ps/2 >mouse/console problems.. is this possible? > >thanks, >chris > >btw, please cc me, im not on the lists over break.. From owner-freebsd-current Wed Dec 25 17:28:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA00395 for current-outgoing; Wed, 25 Dec 1996 17:28:05 -0800 (PST) Received: from fools.ecpnet.com (moke@fools.ecpnet.com [204.246.64.101]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA00371 for ; Wed, 25 Dec 1996 17:27:59 -0800 (PST) Received: from localhost (moke@localhost) by fools.ecpnet.com (8.8.4/8.8.4) with SMTP id TAA00418; Wed, 25 Dec 1996 19:24:24 -0600 (CST) Date: Wed, 25 Dec 1996 19:24:24 -0600 (CST) From: Jimbo Bahooli To: Kazutaka YOKOTA cc: Nate Williams , freebsd-current@freebsd.org Subject: Re: options ASYNCH In-Reply-To: <199612251201.VAA07663@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Dec 1996, Kazutaka YOKOTA wrote: > > >On Tue, 24 Dec 1996, Nate Williams wrote: > > > >> > The ASYNCH define to fix the keyboard lockups when switching vty's appears > >> > to be gone in 2.2 and 3.0. So now when I switch vty's my keyboard locks > >> > and I need to reset it by unplugging it, then plugging it back in. Is > >> > there another work around? > >> > >> Try using 2.2-Beta and see if it helps. > >> > >> > >> Nate > >> > > > >I'm tracking the RELENG_2_2 branch, and I made world the day 2.2-BETA came > >out so I'm running its equal. Possibly even with a few more fixes, so that > >didn't help. :) > > I think we need more details to diagnose your problem. > > Does lockup happen when switching between the X server and vty's? > > Do you have a PS/2 mouse and `psm' enabled? If so, does the X server > access the mouse via `moused'? > > Is there any error message on the console or in `/var/log/messages'? > > Kazu > 1. It locks up when switching vty's. The X server is not involved in this equation. 2. Its a microsoft 2-button serial mouse, psm is not even compiled in the kernel. 3. And there are no messages in /var/log/messages, or any other logfiles. Hope that helps... From owner-freebsd-current Wed Dec 25 23:28:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA11840 for current-outgoing; Wed, 25 Dec 1996 23:28:21 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA11835 for ; Wed, 25 Dec 1996 23:28:19 -0800 (PST) From: alexj@motaba.tmc.edu.tw Received: from motaba.tmc.edu.tw (motaba.tmc.edu.tw [203.64.48.253]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id XAA15091 for ; Wed, 25 Dec 1996 23:26:56 -0800 (PST) Received: from [203.64.48.13] by motaba.tmc.edu.tw (AIX 3.2/UCB 5.64/4.03) id AA38371; Thu, 26 Dec 1996 15:27:36 +0800 Date: Thu, 26 Dec 1996 15:27:36 +0800 Message-Id: <3.0.32.19961226152502.00dd3260@mail.tmc.edu.tw> X-Sender: alexj@mail.tmc.edu.tw X-Mailer: Windows Eudora Pro Version 3.0 (32) To: freebsd-current@freebsd.org Subject: FreeBSD 2.2-BETA Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I got your FreeBSD 2.2-BETA yesterday. I met a problem when installing it. There is no "INDEX" file in 2.2-BETA/packages. Without the file, I can not install the packages by means of /stand/sysinstall. Could you ftp the file to all your mirror sites ? The Taiwan's sites are: NCTUCCCA.edu.tw ftp.nctu.edu.tw freebsd.csie.nctu.edu.tw Thanks ======================================================== = Reading this letter thorugh ffff,0000,0000Eudora Pro 3, = = You will find that the world of e-mail can also be ffff,0000,ffffco0000,0000,fffflo0000,ffff,ffffrf0000,ffff,0000ul = ======================================================== From owner-freebsd-current Thu Dec 26 00:09:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA13277 for current-outgoing; Thu, 26 Dec 1996 00:09:26 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA13272 for ; Thu, 26 Dec 1996 00:09:23 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id AAA26385; Thu, 26 Dec 1996 00:07:49 -0800 (PST) To: alexj@motaba.tmc.edu.tw cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 2.2-BETA In-reply-to: Your message of "Thu, 26 Dec 1996 15:27:36 +0800." <3.0.32.19961226152502.00dd3260@mail.tmc.edu.tw> Date: Thu, 26 Dec 1996 00:07:49 -0800 Message-ID: <26380.851587669@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > There is no "INDEX" file in 2.2-BETA/packages. Fixed. Jordan From owner-freebsd-current Thu Dec 26 03:38:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA17889 for current-outgoing; Thu, 26 Dec 1996 03:38:30 -0800 (PST) Received: from david.siemens.de (david.siemens.de [146.254.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA17884 for ; Thu, 26 Dec 1996 03:38:27 -0800 (PST) Received: from salomon.mchp.siemens.de (salomon.mchp.siemens.de [139.23.33.13]) by david.siemens.de (8.8.3/8.8.0) with ESMTP id MAA24094 for ; Thu, 26 Dec 1996 12:34:29 +0100 (MET) Received: from curry.mchp.siemens.de (root@curry.zfe.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.2/8.8.0) with ESMTP id MAA27239 for ; Thu, 26 Dec 1996 12:38:15 +0100 (MET) Received: from server.us.tld (server.us.tld [192.168.16.33]) by curry.mchp.siemens.de (8.8.4/8.8.4) with ESMTP id MAA06164 for ; Thu, 26 Dec 1996 12:38:12 +0100 (MET) Received: (from andre@localhost) by server.us.tld (8.8.4/8.8.4) id MAA18967 for freebsd-current@freebsd.org; Thu, 26 Dec 1996 12:38:13 +0100 (MET) From: Andre Albsmeier Message-Id: <199612261138.MAA18967@server.us.tld> Subject: Quota-Bug on 2.2-Beta, can't boot To: freebsd-current@freebsd.org Date: Thu, 26 Dec 1996 12:38:13 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am running 2 Quantum Atlas 4GB Harddrives concatenated together to a big 8GB virtual disk. I have enabled userquotas on this drive and used edquota to configure it. This seems to work for a few days when suddenly booting stops at the line "Checking quotas". You see the drive's LEDs flickering for a while and then the machine seems to stop. However, pressing CTRL-C works, and the normal boot procedure continues. When looking in the root directory of the affected filesystems we find that the quota file has grown extremly: -rw-r----- 1 root operator 4294967264 Dec 2 09:30 quota.user It does not appear to occupy the space really. Maybe someone can tell me what's going on here... Thanks Andre From owner-freebsd-current Thu Dec 26 08:21:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA26389 for current-outgoing; Thu, 26 Dec 1996 08:21:22 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA26378 for ; Thu, 26 Dec 1996 08:21:17 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA11357 for ; Thu, 26 Dec 1996 17:21:16 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA12855 for freebsd-current@FreeBSD.org; Thu, 26 Dec 1996 17:21:15 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA11237 for freebsd-current@FreeBSD.org; Thu, 26 Dec 1996 17:03:22 +0100 (MET) From: J Wunsch Message-Id: <199612261603.RAA11237@uriah.heep.sax.de> Subject: Re: cvs commit: ports/x11/XFree86 Makefile ports/x11/XFree86/patches patch-ac To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 26 Dec 1996 17:03:21 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Ollivier Robert at "Dec 25, 96 11:11:57 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (Moved to -current, since this is nothing the ports team could solve.) As Ollivier Robert wrote: > There is worse: the binaries for FreeBSD-current (at the time of release of > 3.2) are referencing libc.so.3.0 but they're not compatible anymore with > the current libc due to the utmp changes. Only a recompilation works. Note that this is basically unrelated to the libc interface, but rather happens since there is _no_ official library interface for the utmp/wtmp handling, at least nothing xterm and xdm know about. Even bumping the shared lib major # wouldn't help in this case: if you've got an old xterm binary, and still have the libc.so.3 around, this xterm will happily run away and trash the wtmp file again. Perhaps we should rip out all the utmp/wtmp handling code out of xterm and xdm while we are at it, and offer the XFree86 people a patch. Moving it to libutil would solve the matter once and for all, so changing utmp.h next time will only require a minor version number bump for the shared libutil. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Dec 26 09:51:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA00324 for current-outgoing; Thu, 26 Dec 1996 09:51:41 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA00317 for ; Thu, 26 Dec 1996 09:51:38 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id SAA19503; Thu, 26 Dec 1996 18:51:10 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA14726; Thu, 26 Dec 1996 18:51:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id SAA20527; Thu, 26 Dec 1996 18:23:44 +0100 (MET) From: J Wunsch Message-Id: <199612261723.SAA20527@uriah.heep.sax.de> Subject: Re: `make world` won't To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 26 Dec 1996 18:23:44 +0100 (MET) Cc: SimsS@IBM.Net Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612261641.QAA300214@smtp-gw01.ny.us.ibm.net> from Steve Sims at "Dec 26, 96 11:39:59 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (Moved to -current, where this is more appropriate.) As Steve Sims wrote: > ===> lib/libcom_err > pwd: No such file or directory > *** Error code 2 That's an old story. Do a cd /usr/src/bin/sh cvs update make all install first. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Dec 26 10:14:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA01106 for current-outgoing; Thu, 26 Dec 1996 10:14:20 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA01100 for ; Thu, 26 Dec 1996 10:14:12 -0800 (PST) Received: from cantina.clinet.fi (root@cantina.clinet.fi [194.100.0.15]) by hauki.clinet.fi (8.8.2/8.6.4) with ESMTP id UAA00542; Thu, 26 Dec 1996 20:14:03 +0200 (EET) Received: (hsu@localhost) by cantina.clinet.fi (8.8.4/8.6.4) id UAA03704; Thu, 26 Dec 1996 20:14:02 +0200 (EET) Date: Thu, 26 Dec 1996 20:14:02 +0200 (EET) Message-Id: <199612261814.UAA03704@cantina.clinet.fi> From: Heikki Suonsivu To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-current@freebsd.org In-reply-to: J Wunsch's message of 24 Dec 1996 10:06:00 +0200 Subject: Re: DAT: reading with blocksize=256K Organization: Clinet Ltd, Espoo, Finland References: <199612240747.IAA10234@uriah.heep.sax.de> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199612240747.IAA10234@uriah.heep.sax.de> J Wunsch writes: > I just got a DAT cartridge with a tar backup. It seems that the backup > was made with a blocksize of 256K. Isn't it possible to get the data into > my pc with current (it looks like there's a limit of 64K)?? This has been discussed at lenth already: it's currently limited by physio(9) to chunks of at most 64 KB size, due to the limitations in the scatter/gather list of some SCSI controllers that don't allow for more than 16 scatter/gather segments. I have been able to read my old backups written with 1024k blocksize. They secret was to use ddd instead of dd. Not debugger interface ddd, but the old streaming dd by jtv@hut.fi, it is available somewhere in nic.funet.fi, and I think team might be similar. I do not know what happens. ddd certainly does not do anything smart. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 From owner-freebsd-current Thu Dec 26 10:28:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA01633 for current-outgoing; Thu, 26 Dec 1996 10:28:54 -0800 (PST) Received: from intrepid.leaky.com (shaffer-s.nosc.mil [128.49.236.16]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA01625 for ; Thu, 26 Dec 1996 10:28:44 -0800 (PST) Received: (admin@localhost) by intrepid.leaky.com (8.8.4/8.6.5) id KAA13350 for ; Thu, 26 Dec 1996 10:20:09 -0800 (PST) Message-Id: <199612261820.KAA13350@intrepid.leaky.com> X-Authentication-Warning: intrepid.leaky.com: admin set sender to using -f Received: from localhost(127.0.0.1) by intrepid.leaky.com via smap (V1.3) id sma013339; Thu Dec 26 10:19:56 1996 X-Mailer: exmh version 1.6.7 5/3/96 To: freebsd-current@freebsd.org Subject: Can't Make World Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Dec 1996 10:19:55 -0800 From: Charlie & Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tried to make world today and got the following error. My source tree is current as of this morning (cvs-cur 2857). Any help would be appriciated. Greg -------------------------------------------------------------- Rebuilding bootstrap tools -------------------------------------------------------------- cd /home/FreeBSD-current/src && make bootstrap cd /home/FreeBSD-current/src/usr.bin/make && make depend && make -DNOMAN -DNOPROFILE all install cleandir obj rm -f .depend [deleted] cc -O2 -m486 -pipe -I/home/FreeBSD-current/src/usr.bin/make -o make arch.o buf.o compat.o cond.o dir.o for.o hash.o job.o main.o make.o parse.o str.o suff.o targ.o var.o util.o lstAppend.o lstAtEnd.o lstAtFront.o lstClose.o lstConcat.o lstDatum. o lstDeQueue.o lstDestroy.o lstDupl.o lstEnQueue.o lstFind.o lstFindFrom.o lstFirst.o lstForEach.o lstForEachFrom.o lstInit. o lstInsert.o lstIsAtEnd.o lstIsEmpty.o lstLast.o lstMember.o lstNext.o lstOpen.o lstRemove.o lstReplace.o lstSucc.o install -c -s -o bin -g bin -m 555 make /usr/bin pwd: No such file or directory *** Error code 2 Stop. *** Error code 1 From owner-freebsd-current Thu Dec 26 10:40:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA02067 for current-outgoing; Thu, 26 Dec 1996 10:40:39 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA02051 for ; Thu, 26 Dec 1996 10:40:34 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA23985 for ; Thu, 26 Dec 1996 19:40:32 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA16425 for freebsd-current@FreeBSD.org; Thu, 26 Dec 1996 19:40:31 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id TAA03226 for freebsd-current@FreeBSD.org; Thu, 26 Dec 1996 19:27:12 +0100 (MET) From: J Wunsch Message-Id: <199612261827.TAA03226@uriah.heep.sax.de> Subject: Re: DAT: reading with blocksize=256K To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 26 Dec 1996 19:27:11 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612261814.UAA03704@cantina.clinet.fi> from Heikki Suonsivu at "Dec 26, 96 08:14:02 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Heikki Suonsivu wrote: > I have been able to read my old backups written with 1024k blocksize. They > secret was to use ddd instead of dd. This must be unrelated to the other problem. If they were written with 1024 K blocksize on a FreeBSD machine, they were actually written with 64 KB instead. The limit is in physio(9) (UTSL), and could not be changed by whatever trickery from a userland program. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Dec 26 10:59:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA03439 for current-outgoing; Thu, 26 Dec 1996 10:59:42 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id KAA03430 for ; Thu, 26 Dec 1996 10:59:37 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA25714; Thu, 26 Dec 1996 19:59:30 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA16720; Thu, 26 Dec 1996 19:59:29 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id TAA22850; Thu, 26 Dec 1996 19:57:09 +0100 (MET) From: J Wunsch Message-Id: <199612261857.TAA22850@uriah.heep.sax.de> Subject: Re: Can't Make World To: root@intrepid.leaky.com (Charlie &) Date: Thu, 26 Dec 1996 19:57:09 +0100 (MET) Cc: freebsd-current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612261820.KAA13350@intrepid.leaky.com> from Charlie & at "Dec 26, 96 10:19:55 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Charlie & wrote: > Tried to make world today and got the following error. My source tree is > current as of this morning (cvs-cur 2857). > install -c -s -o bin -g bin -m 555 make /usr/bin > pwd: No such file or directory > *** Error code 2 Please, read the mailing lists. This has been discussed at length last week, and i've just answered the question 3 hours ago. You gotta rebuild your shell first. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Dec 26 11:21:09 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA04252 for current-outgoing; Thu, 26 Dec 1996 11:21:09 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA04246 for ; Thu, 26 Dec 1996 11:21:02 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id LAA28364; Thu, 26 Dec 1996 11:15:56 -0800 (PST) Message-ID: <32C2CEAD.794BDF32@whistle.com> Date: Thu, 26 Dec 1996 11:14:53 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Joerg Wunsch CC: FreeBSD-current users Subject: Re: DAT: reading with blocksize=256K References: <199612261827.TAA03226@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Heikki Suonsivu wrote: > > > I have been able to read my old backups written with 1024k blocksize. They > > secret was to use ddd instead of dd. > > This must be unrelated to the other problem. If they were written > with 1024 K blocksize on a FreeBSD machine, they were actually written > with 64 KB instead. The limit is in physio(9) (UTSL), and could not > be changed by whatever trickery from a userland program. > OR the drive is in fixed block mode. in FIXED block mode what is actually written to tape is fixed blocks and many are written at a time for a large read/write thus you can read and write differnt blocksizes because it always ends up a multiple of hte smaller blocksize anyway.. julian From owner-freebsd-current Thu Dec 26 11:24:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA04384 for current-outgoing; Thu, 26 Dec 1996 11:24:54 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA04374 for ; Thu, 26 Dec 1996 11:24:51 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA28563 for ; Thu, 26 Dec 1996 20:24:48 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA17288 for freebsd-current@FreeBSD.org; Thu, 26 Dec 1996 20:24:48 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id UAA27137 for freebsd-current@FreeBSD.org; Thu, 26 Dec 1996 20:23:39 +0100 (MET) From: J Wunsch Message-Id: <199612261923.UAA27137@uriah.heep.sax.de> Subject: Re: DAT: reading with blocksize=256K To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 26 Dec 1996 20:23:38 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <32C2CEAD.794BDF32@whistle.com> from Julian Elischer at "Dec 26, 96 11:14:53 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Julian Elischer wrote: > the drive is in fixed block mode. > in FIXED block mode what is actually written to tape is fixed blocks > and many are written at a time for a large read/write But, you can't do 1 MB fixed blocks, right? :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Dec 26 12:29:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA06215 for current-outgoing; Thu, 26 Dec 1996 12:29:58 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA06210 for ; Thu, 26 Dec 1996 12:29:55 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id MAA29432; Thu, 26 Dec 1996 12:24:44 -0800 (PST) Message-ID: <32C2DECD.41C67EA6@whistle.com> Date: Thu, 26 Dec 1996 12:23:41 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Joerg Wunsch CC: FreeBSD-current users Subject: Re: DAT: reading with blocksize=256K References: <199612261923.UAA27137@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Julian Elischer wrote: > > > the drive is in fixed block mode. > > in FIXED block mode what is actually written to tape is fixed blocks > > and many are written at a time for a large read/write > > But, you can't do 1 MB fixed blocks, right? :-) > no, but if you do a write of a 1MB block (e.g. dd bs=1M), physio will do 16 writes of 64K which will each be written as 64 x 1K blocks onto the media. This appears on tape as 1024 x 1K blocks which is indistinguishable from 1020 x 1K blocks written in one hit by (say) and SGI. and you can read the data back using (say) 4K reads in which case you'll get 4 1K blocks at each read, and you will get valid data for 256 reads. From owner-freebsd-current Thu Dec 26 13:15:37 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA07938 for current-outgoing; Thu, 26 Dec 1996 13:15:37 -0800 (PST) Received: from nic.follonett.no (nic.follonett.no [194.198.43.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA07918; Thu, 26 Dec 1996 13:15:30 -0800 (PST) Received: (from uucp@localhost) by nic.follonett.no (8.8.3/8.8.3) with UUCP id WAA01833; Thu, 26 Dec 1996 22:14:09 +0100 (MET) Received: from oo7 (oo7.dimaga.com [192.0.0.65]) by dimaga.com (8.7.5/8.7.2) with SMTP id NAA18447; Tue, 24 Dec 1996 13:40:37 +0100 (MET) Message-Id: <3.0.32.19961224133847.009c3920@dimaga.com> X-Sender: eivind@dimaga.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 24 Dec 1996 13:38:48 +0100 To: Nate Williams From: Eivind Eklund Subject: Re: User ppp not hanging up modem. Cc: freebsd-questions@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 10:51 AM 12/21/96 -0700, Nate Williams wrote: >That's *NOT* the correct thing. What happens when for some reason >PPP happens to send the sequence '+++' to the modem? All of a sudden >it'll drop into command mode and you're screwed. User-PPP (as well as >all other PPP/SLIP implementations I've worked with) assumes that you've >disabled the escape sequence at least temporarily. Eh? This is not a problem. The HAYES protocol (which is the main protocol for most modems since at least the mid-80s) requires a pause between the +'es. The length of this pause is usually (always?) user-settable, with a default of about .2 seconds (?). A +++ stream as data will not drop the modem to command mode. I'm also having problems with my modem not ALWAYS dropping the connection on a PPP exit (userland PPP on FreeBSD 2.1.0 and 2.1.6), and would consider it a Good Thing if the PPP program sent +\w+\w+\w\wATH0\cr on a close/exit. This modem respect DTR, but it seems that PPP doesn't always clear that line. Eivind Eklund / perhaps@yes.no / http://maybe.yes.no/perhaps/ From owner-freebsd-current Thu Dec 26 14:47:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA14004 for current-outgoing; Thu, 26 Dec 1996 14:47:49 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id OAA13974 for ; Thu, 26 Dec 1996 14:47:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA21890; Thu, 26 Dec 1996 23:46:27 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA20371; Thu, 26 Dec 1996 23:46:24 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id XAA00324; Thu, 26 Dec 1996 23:31:09 +0100 (MET) From: J Wunsch Message-Id: <199612262231.XAA00324@uriah.heep.sax.de> Subject: Re: User ppp not hanging up modem. To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Thu, 26 Dec 1996 23:31:09 +0100 (MET) Cc: eivind@dimaga.com (Eivind Eklund) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3.0.32.19961224133847.009c3920@dimaga.com> from Eivind Eklund at "Dec 24, 96 01:38:48 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Eivind Eklund wrote: > This modem respect DTR, but it seems that PPP doesn't always clear > that line. It does, since it doesn't do it. :-) The kernel is responsible to drop DTR at the last close of the device. Of course, you should set HUPCL. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Dec 26 15:01:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA15089 for current-outgoing; Thu, 26 Dec 1996 15:01:50 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA15074 for ; Thu, 26 Dec 1996 15:01:43 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id AAA02597 for ; Fri, 27 Dec 1996 00:01:36 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id AAA13160 for freebsd-current@freebsd.org; Fri, 27 Dec 1996 00:01:22 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id XAA06081; Thu, 26 Dec 1996 23:48:29 +0100 (CET) Message-ID: Date: Thu, 26 Dec 1996 23:48:28 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org (FreeBSD-current users) Subject: Re: cvs commit: ports/x11/XFree86 Makefile ports/x11/XFree86/patches patch-ac References: <199612261603.RAA11237@uriah.heep.sax.de> X-Mailer: Mutt 0.55.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: <199612261603.RAA11237@uriah.heep.sax.de>; from J Wunsch on Dec 26, 1996 17:03:21 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > Note that this is basically unrelated to the libc interface, but > rather happens since there is _no_ official library interface for the > utmp/wtmp handling, at least nothing xterm and xdm know about. I agree. > Perhaps we should rip out all the utmp/wtmp handling code out of xterm > and xdm while we are at it, and offer the XFree86 people a patch. > Moving it to libutil would solve the matter once and for all, so > changing utmp.h next time will only require a minor version number > bump for the shared libutil. I always thought one of the purposes of login(3), logwtmp(3) and logout(3) in libutil was precisely that. I'm surprised xterm/xdm don't use them. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #33: Sat Dec 21 12:57:17 CET 1996 From owner-freebsd-current Thu Dec 26 15:34:27 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA17212 for current-outgoing; Thu, 26 Dec 1996 15:34:27 -0800 (PST) Received: from rs1.rrz.Uni-Koeln.DE (0@rs1.rrz.Uni-Koeln.DE [134.95.100.208]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA17155 for ; Thu, 26 Dec 1996 15:34:07 -0800 (PST) Received: from pc1.scs-koeln.de ([134.95.30.183]) by rs1.rrz.Uni-Koeln.DE with SMTP id AA107415 (5.67b/IDA-1.5 for ); Fri, 27 Dec 1996 00:33:59 +0100 Message-Id: <1.5.4.32.19961226233251.006a2a1c@mail.rrz.uni-koeln.de> X-Sender: afr04@mail.rrz.uni-koeln.de X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 27 Dec 1996 00:32:51 +0100 To: freebsd-current@freebsd.org From: Ralf Luettgen Subject: LFS? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Is there anyone, who could say me if the LFS-Filesystems works on his machine? I try it on a 2.1.5 based machine and it fails. I want to use it for building a cluster of FreeBSD machines. So I'm looking forward to any help. Ralf From owner-freebsd-current Thu Dec 26 23:54:38 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id XAA09019 for current-outgoing; Thu, 26 Dec 1996 23:54:38 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA09014 for ; Thu, 26 Dec 1996 23:54:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id XAA09724; Thu, 26 Dec 1996 23:52:45 -0800 (PST) Message-Id: <199612270752.XAA09724@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Ralf Luettgen cc: freebsd-current@freebsd.org Subject: Re: LFS? In-reply-to: Your message of "Fri, 27 Dec 1996 00:32:51 +0100." <1.5.4.32.19961226233251.006a2a1c@mail.rrz.uni-koeln.de> From: David Greenman Reply-To: dg@root.com Date: Thu, 26 Dec 1996 23:52:45 -0800 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Is there anyone, who could say me if the LFS-Filesystems works on his machine? >I try it on a 2.1.5 based machine and it fails. I want to use it for >building a cluster of FreeBSD machines. So I'm looking forward to any help. LFS is not working in FreeBSD. We do have plans to fix it, however, but it will likely be at least another few months. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Dec 27 02:13:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA13177 for current-outgoing; Fri, 27 Dec 1996 02:13:15 -0800 (PST) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA13172; Fri, 27 Dec 1996 02:13:07 -0800 (PST) Received: by sequent.kiae.su id AA14985 (5.65.kiae-2 ); Fri, 27 Dec 1996 12:55:51 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Fri, 27 Dec 96 12:55:49 +0300 Received: from localhost (nagual.ru [127.0.0.1]) by nagual.ru (8.8.4/8.8.4) with SMTP id MAA01301; Fri, 27 Dec 1996 12:54:21 +0300 (MSK) Date: Fri, 27 Dec 1996 12:54:20 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7=2C_Andrey_Chernov?= To: FreeBSD-current , Bruce Evans Cc: jdp@freebsd.org Subject: Activate nanoseconds in struct stat: please review! Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The problem is that st->st_*timespec.tv_nsec is always zero, this patch fix it. *** ufs/ufs/inode.h.orig Fri Sep 20 01:39:32 1996 --- ufs/ufs/inode.h Fri Dec 27 12:31:54 1996 *************** *** 147,169 **** /* * XXX this is too long to be a macro, and isn't used in any time-critical ! * place; in fact it is only used in ufs_vnops.c so it shouldn't be in a ! * header file. */ #define ITIMES(ip, t1, t2) { \ - long tv_sec = time.tv_sec; \ if ((ip)->i_flag & (IN_ACCESS | IN_CHANGE | IN_UPDATE)) { \ (ip)->i_flag |= IN_MODIFIED; \ ! if ((ip)->i_flag & IN_ACCESS) \ ! (ip)->i_atime.tv_sec \ ! = ((t1) == &time ? tv_sec : (t1)->tv_sec); \ if ((ip)->i_flag & IN_UPDATE) { \ ! (ip)->i_mtime.tv_sec \ ! = ((t2) == &time ? tv_sec : (t2)->tv_sec); \ (ip)->i_modrev++; \ } \ if ((ip)->i_flag & IN_CHANGE) \ ! (ip)->i_ctime.tv_sec = tv_sec; \ (ip)->i_flag &= ~(IN_ACCESS | IN_CHANGE | IN_UPDATE); \ } \ } --- 147,172 ---- /* * XXX this is too long to be a macro, and isn't used in any time-critical ! * place. */ #define ITIMES(ip, t1, t2) { \ if ((ip)->i_flag & (IN_ACCESS | IN_CHANGE | IN_UPDATE)) { \ + struct timeval *tv, now; \ + int s = splclock(); \ + now = time; \ + splx(s); \ (ip)->i_flag |= IN_MODIFIED; \ ! if ((ip)->i_flag & IN_ACCESS) { \ ! tv = ((t1) == &time) ? &now : (t1); \ ! TIMEVAL_TO_TIMESPEC(tv, &((ip)->i_atime)); \ ! } \ if ((ip)->i_flag & IN_UPDATE) { \ ! tv = ((t2) == &time) ? &now : (t2); \ ! TIMEVAL_TO_TIMESPEC(tv, &((ip)->i_mtime)); \ (ip)->i_modrev++; \ } \ if ((ip)->i_flag & IN_CHANGE) \ ! TIMEVAL_TO_TIMESPEC(&now, &((ip)->i_ctime)); \ (ip)->i_flag &= ~(IN_ACCESS | IN_CHANGE | IN_UPDATE); \ } \ } *** ufs/ffs/ffs_inode.c.orig Thu Nov 7 02:55:57 1996 --- ufs/ffs/ffs_inode.c Fri Dec 27 12:38:30 1996 *************** *** 90,96 **** struct buf *bp; struct inode *ip; int error; - time_t tv_sec; ip = VTOI(ap->a_vp); if (ap->a_vp->v_mount->mnt_flag & MNT_RDONLY) { --- 90,95 ---- *************** *** 109,130 **** * same copy of `time'. This is not as good. Some callers forget * to make a copy; others make a copy too early (before the i/o * has completed)... - * - * XXX there should be a function or macro for reading the time - * (e.g., some machines may require splclock()). */ ! tv_sec = time.tv_sec; ! if (ip->i_flag & IN_ACCESS) ! ip->i_atime.tv_sec = ! (ap->a_access == &time ? tv_sec : ap->a_access->tv_sec); ! if (ip->i_flag & IN_UPDATE) { ! ip->i_mtime.tv_sec = ! (ap->a_modify == &time ? tv_sec : ap->a_modify->tv_sec); ! ip->i_modrev++; ! } ! if (ip->i_flag & IN_CHANGE) ! ip->i_ctime.tv_sec = tv_sec; ! ip->i_flag &= ~(IN_ACCESS | IN_CHANGE | IN_MODIFIED | IN_UPDATE); fs = ip->i_fs; /* * Ensure that uid and gid are correct. This is a temporary --- 108,116 ---- * same copy of `time'. This is not as good. Some callers forget * to make a copy; others make a copy too early (before the i/o * has completed)... */ ! ITIMES(ip, ap->a_access, ap->a_modify); ! ip->i_flag &= ~IN_MODIFIED; fs = ip->i_fs; /* * Ensure that uid and gid are correct. This is a temporary -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Fri Dec 27 02:47:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA14109 for current-outgoing; Fri, 27 Dec 1996 02:47:33 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id CAA14102 for ; Fri, 27 Dec 1996 02:47:29 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id LAA03368 for ; Fri, 27 Dec 1996 11:47:12 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id LAA00731 for freebsd-current@freebsd.org; Fri, 27 Dec 1996 11:47:12 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id BAA06868; Fri, 27 Dec 1996 01:31:12 +0100 (CET) Message-ID: Date: Fri, 27 Dec 1996 01:31:11 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@freebsd.org Subject: Re: LFS? References: <1.5.4.32.19961226233251.006a2a1c@mail.rrz.uni-koeln.de> X-Mailer: Mutt 0.55.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: <1.5.4.32.19961226233251.006a2a1c@mail.rrz.uni-koeln.de>; from Ralf Luettgen on Dec 27, 1996 00:32:51 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Ralf Luettgen: > I try it on a 2.1.5 based machine and it fails. I want to use it for > building a cluster of FreeBSD machines. So I'm looking forward to any help. Don't try it on anything later than 2.0 (or anything post the great VM/buffer cache unification to be exact) or risk panic or worse data corruption. John said he 'd try to fix it for LFS but don't hold your breath. 2.2 is too near I think. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #33: Sat Dec 21 12:57:17 CET 1996 From owner-freebsd-current Fri Dec 27 10:18:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA01752 for current-outgoing; Fri, 27 Dec 1996 10:18:43 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA01740 for ; Fri, 27 Dec 1996 10:18:26 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.4/8.8.3) id UAA02679 for freebsd-current@freebsd.org; Fri, 27 Dec 1996 20:18:21 +0200 (EET) From: mika ruohotie Message-Id: <199612271818.UAA02679@shadows.aeon.net> Subject: weird w/who on -current To: freebsd-current@freebsd.org Date: Fri, 27 Dec 1996 20:18:21 +0200 (EET) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hmm... my w and who arent working right, i've changed the whole system twice now... shadows# w w: /dev//3: No such file or directory shadows# who mickey ttyv0 Dec 27 17:44 ey 3 Feb 3 19:52 root ttyp8 Jan 1 02:00 :0:S.3 root Jan 1 02:00 (ÒðÃ2ttypa) shadows# the proggies do compile... i log the make world and i had no errors (i use -k nowadays), and the kernels compiled fine too... (two different sup sets, over a week apart) mickey -- mika@aeon.net mika ruohotie From owner-freebsd-current Fri Dec 27 10:42:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA02926 for current-outgoing; Fri, 27 Dec 1996 10:42:31 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA02920 for ; Fri, 27 Dec 1996 10:42:29 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id KAA00806 for ; Fri, 27 Dec 1996 10:43:09 -0800 (PST) Received: (qmail 18931 invoked by uid 110); 27 Dec 1996 18:42:07 -0000 Message-ID: <19961227184207.18930.qmail@suburbia.net> Subject: Re: weird w/who on -current In-Reply-To: <199612271818.UAA02679@shadows.aeon.net> from mika ruohotie at "Dec 27, 96 08:18:21 pm" To: bsdcur@shadows.aeon.net (mika ruohotie) Date: Sat, 28 Dec 1996 05:42:07 +1100 (EST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > hmm... > > my w and who arent working right, i've changed the whole system twice now... > > shadows# w > w: /dev//3: No such file or directory > shadows# who > mickey ttyv0 Dec 27 17:44 > ey 3 Feb 3 19:52 > root ttyp8 Jan 1 02:00 > :0:S.3 root Jan 1 02:00 (ÒðÃ2ttypa) > shadows# > > the proggies do compile... > > i log the make world and i had no errors (i use -k nowadays), and the > kernels compiled fine too... (two different sup sets, over a week apart) > > > mickey > -- > mika@aeon.net mika ruohotie > don't forget to rebuild xterm, rxvt, screen etc From owner-freebsd-current Fri Dec 27 11:35:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA04722 for current-outgoing; Fri, 27 Dec 1996 11:35:24 -0800 (PST) Received: from venus.GAIANET.NET (vince@venus.GAIANET.NET [206.171.98.27]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA04717 for ; Fri, 27 Dec 1996 11:35:21 -0800 (PST) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.8.3/8.8.3) with SMTP id LAA11290; Fri, 27 Dec 1996 11:37:47 -0800 (PST) Date: Fri, 27 Dec 1996 11:37:45 -0800 (PST) From: Vincent Poy To: mika ruohotie cc: freebsd-current@freebsd.org Subject: Re: weird w/who on -current In-Reply-To: <199612271818.UAA02679@shadows.aeon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by freefall.freebsd.org id LAA04718 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 27 Dec 1996, mika ruohotie wrote: > hmm... > > my w and who arent working right, i've changed the whole system twice now... > > shadows# w > w: /dev//3: No such file or directory > shadows# who > mickey ttyv0 Dec 27 17:44 > ey 3 Feb 3 19:52 > root ttyp8 Jan 1 02:00 > :0:S.3 root Jan 1 02:00 (ÒðÃ2ttypa) > shadows# > > the proggies do compile... > > i log the make world and i had no errors (i use -k nowadays), and the > kernels compiled fine too... (two different sup sets, over a week apart) Kill all screen sessions and recompile screen. Cheers, Vince GaiaNet Corporation - Beverly Hills, California 90210 USA From owner-freebsd-current Fri Dec 27 14:46:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA12318 for current-outgoing; Fri, 27 Dec 1996 14:46:22 -0800 (PST) Received: from mailhost.transarc.com (mailhost.transarc.com [158.98.16.250]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA12313 for ; Fri, 27 Dec 1996 14:46:21 -0800 (PST) Received: from unix3.transarc.com (unix3.transarc.com [158.98.16.103]) by mailhost.transarc.com (8.8.0/8.8.0) with SMTP id RAA24741 for ; Fri, 27 Dec 1996 17:45:48 -0500 (EST) Date: Fri, 27 Dec 1996 17:45:48 -0500 (EST) From: Pat Barron To: freebsd-current@freebsd.org Subject: Confused about cvsup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can someone please help me get with the program? I decided to become modern and sync with current via cvsup instead of sup (mostly because the one machine that was answering to sup?.freebsd.org has stopped accepting sup connections). I have cvsup-14.0, but it's missing all kinds of shared shared libraries that I can't identify. Some of them seem to be the Modula 3 runtime (Modula 3? I really would rather not have to install Modula 3 on my system in order to sync with the current source tree.), but I can't identify the others. Can someone clue me in on what other pieces I need to fetch before cvsup will work? (In case you can't tell, I'd *really* rather continue to use sup, but c'est la vie, I guess....) --Pat. From owner-freebsd-current Fri Dec 27 15:43:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA14129 for current-outgoing; Fri, 27 Dec 1996 15:43:19 -0800 (PST) Received: from moonpie.w8hd.org (root@moonpie.w8hd.org [198.252.159.14]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA14122 for ; Fri, 27 Dec 1996 15:43:16 -0800 (PST) Received: from moonpie.w8hd.org (kimc@moonpie.w8hd.org [198.252.159.14]) by moonpie.w8hd.org (8.8.4/8.8.2) with SMTP id SAA14493; Fri, 27 Dec 1996 18:43:03 -0500 (EST) Date: Fri, 27 Dec 1996 18:43:02 -0500 (EST) From: Kim Culhan To: Pat Barron cc: freebsd-current@freebsd.org Subject: Re: Confused about cvsup In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 27 Dec 1996, Pat Barron wrote: > Can someone please help me get with the program? I decided to become > modern and sync with current via cvsup instead of sup (mostly because > the one machine that was answering to sup?.freebsd.org has stopped > accepting sup connections). I have cvsup-14.0, but it's missing all kinds > of shared shared libraries that I can't identify. Some of them seem to be > the Modula 3 runtime (Modula 3? I really would rather not have to install > Modula 3 on my system in order to sync with the current source tree.), > but I can't identify the others. ftp://ftp.freebsd.org/pub/FreeBSD/packages-current/net/cvsup-14.0.tgz >From a recent announcement: The FreeBSD package now depends only on the "modula-3-lib" package, a subset of the Modula-3 installation consisting of only the shared libraries. Because of this, you can now install and use the "cvsup" package in a reasonable amount of disk space. The package is much smaller than the statically linked binary distribution, so updates to new versions of CVSup should be more convenient now. The package is the recommended distribution for binary-only users. cvsup is as easy to use as sup; cvsup [name of cvsupfile] It can run on a character-based display but will open a window if it determines you have the display variable set. regards kim -- kimc@w8hd.org From owner-freebsd-current Fri Dec 27 15:49:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA14500 for current-outgoing; Fri, 27 Dec 1996 15:49:48 -0800 (PST) Received: from dreamlabs.dreaming.org (mitayai@dreamlabs.dreaming.org [207.107.8.200]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA14492 for ; Fri, 27 Dec 1996 15:49:45 -0800 (PST) Received: from localhost (mitayai@localhost) by dreamlabs.dreaming.org (8.8.4/8.6.12) with SMTP id SAA16525; Fri, 27 Dec 1996 18:49:35 -0500 (EST) Date: Fri, 27 Dec 1996 18:49:32 -0500 (EST) From: Will Mitayai Keeso Rowe To: Pat Barron cc: freebsd-current@freebsd.org Subject: Re: Confused about cvsup In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Pat... I think you grabbed the cvsup source, right? I grabbed the bnary out of /packages-current, and everything was cool. (I too didn't want to install modula3 [ick]). If you are going to run it on a FreeBSD machine that's reatively current, you should be ok. Good luck (and trust me, i felt the same way about sup, but i changed my tune.. cvsup is *so* much nicer in many different ways... check out /usr/share/examples/cvsup/ for the equivalent to the supfiles, and the comments explain how best to use it) -Mit mitayai@dreamlabs.com On Fri, 27 Dec 1996, Pat Barron wrote: > Can someone please help me get with the program? I decided to become > modern and sync with current via cvsup instead of sup (mostly because > the one machine that was answering to sup?.freebsd.org has stopped > accepting sup connections). I have cvsup-14.0, but it's missing all kinds > of shared shared libraries that I can't identify. Some of them seem to be > the Modula 3 runtime (Modula 3? I really would rather not have to install > Modula 3 on my system in order to sync with the current source tree.), > but I can't identify the others. > > Can someone clue me in on what other pieces I need to fetch before cvsup > will work? > > (In case you can't tell, I'd *really* rather continue to use sup, but > c'est la vie, I guess....) > > --Pat. > > > Will Mitayai Keeso Rowe The DreamLabs Network http://www.dreaming.org (705)741-1089 From owner-freebsd-current Fri Dec 27 16:01:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA15484 for current-outgoing; Fri, 27 Dec 1996 16:01:06 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA15468 for ; Fri, 27 Dec 1996 16:01:02 -0800 (PST) Received: (from jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) id QAA01051; Fri, 27 Dec 1996 16:00:54 -0800 (PST) To: freebsd-current@freebsd.org Path: not-for-mail From: jdp@polstra.com (John Polstra) Newsgroups: polstra.freebsd.current Subject: Re: Confused about cvsup Date: 27 Dec 1996 16:00:53 -0800 Organization: Polstra & Co., Seattle, WA Lines: 38 Distribution: local Message-ID: <5a1nvl$10o@austin.polstra.com> References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Pat Barron wrote: > I have cvsup-14.0, but it's missing all kinds > of shared shared libraries that I can't identify. Some of them seem to be > the Modula 3 runtime (Modula 3? I really would rather not have to install > Modula 3 on my system in order to sync with the current source tree.), > but I can't identify the others. If you don't want to install the Modula-3 libraries, then get the static binary release instead. From the announcement: Where to Get CVSup ------------------ CVSup is free software. It is available from the following FTP sites: ftp://freefall.freebsd.org/pub/CVSup/ ftp://ftp.polstra.com/pub/FreeBSD/CVSup/ (slow; avoid if possible) Full sources as well as FreeBSD binaries are available: cvsup-bin-14.0.tar.gz FreeBSD static binaries for the client cvsupd-bin-14.0.tar.gz FreeBSD static binaries for the server cvsup-14.0.tar.gz Sources ** MD5 signatures for these files are: MD5 (cvsup-bin-14.0.tar.gz) = 7a5cef5919d28979d6e33dcf7b2898c0 MD5 (cvsupd-bin-14.0.tar.gz) = 5c29e36e339582693f2bc2db23254449 MD5 (cvsup-14.0.tar.gz) = 331bb5c114bac2053eeaa46eaa8f19c3 You just need the client, "cvsup-bin-14.0.tar.gz". It will run under FreeBSD-2.1.5 and later, maybe even -2.1.0. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Dec 28 04:36:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA10984 for current-outgoing; Sat, 28 Dec 1996 04:36:41 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA10972; Sat, 28 Dec 1996 04:36:29 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id XAA17631; Sat, 28 Dec 1996 23:35:34 +1100 Date: Sat, 28 Dec 1996 23:35:34 +1100 From: Bruce Evans Message-Id: <199612281235.XAA17631@godzilla.zeta.org.au> To: bde@freefall.freebsd.org, current@freefall.freebsd.org Subject: Re: i586-optimized copyin/out still broken Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >bde 96/12/28 04:18:46 > > Modified: sys/i386/isa npx.c > Log: > Disabled i586-optimized copyin and copyout again. The fault handler > is still broken - it doesn't restore the floating point state. > > 2.2-BETA users should disable it using npx0 flags 0x04 the same as > 2.2-ALPHA users should have. > > Revision Changes Path > 1.35 +3 -1 src/sys/i386/isa/npx.c Already disabled in in 2.2 too. Bruce From owner-freebsd-current Sat Dec 28 06:29:59 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA13441 for current-outgoing; Sat, 28 Dec 1996 06:29:59 -0800 (PST) Received: from mule1.mindspring.com (mule1.mindspring.com [204.180.128.167]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA13436 for ; Sat, 28 Dec 1996 06:29:57 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by mule1.mindspring.com (8.8.2/8.7.3) with SMTP id OAA89156 for ; Sat, 28 Dec 1996 14:29:53 GMT Message-ID: <32C52EE0.167EB0E7@mindspring.com> Date: Sat, 28 Dec 1996 09:29:52 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: current libmd md5c.c compile fails Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In today's current 12-28-96 08:30 EST the libmd/md5c.c fails compilation due to missing the correct md5.h. I searched for all md5.h files and found none that will work with this C module. Ron cc -O -I/usr/src/lib/libmd -c /usr/src/lib/libmd/md5c.c -o md5c.o /usr/src/lib/libmd/md5c.c:40: sys/md5.h: No such file or directory *** Error code 1 -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** From owner-freebsd-current Sat Dec 28 06:39:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA13647 for current-outgoing; Sat, 28 Dec 1996 06:39:13 -0800 (PST) Received: from mule1.mindspring.com (mule1.mindspring.com [204.180.128.167]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA13642 for ; Sat, 28 Dec 1996 06:39:11 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by mule1.mindspring.com (8.8.2/8.7.3) with SMTP id OAA81924 for ; Sat, 28 Dec 1996 14:39:08 GMT Message-ID: <32C5310B.2781E494@mindspring.com> Date: Sat, 28 Dec 1996 09:39:07 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: cvsup standard-supfile for current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed the the standard cvsup file changed around 12-15-96 and no longer works with cvsup 13.5. Did I miss something, I had to use an old version of the supfile to get it to work. The new file has a new format with only single entries for release, host, etc, instead of entries for each source tree A.K.A. src-base, src-bin. etc. Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** From owner-freebsd-current Sat Dec 28 07:12:56 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA14647 for current-outgoing; Sat, 28 Dec 1996 07:12:56 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA14640 for ; Sat, 28 Dec 1996 07:12:54 -0800 (PST) Received: from critter.dk.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0ve0Qw-0003wRC; Sat, 28 Dec 96 07:12 PST Received: from critter.dk.tfs.com (localhost.dk.tfs.com [127.0.0.1]) by critter.dk.tfs.com (8.8.2/8.8.2) with ESMTP id QAA03520; Sat, 28 Dec 1996 16:15:26 +0100 (MET) To: Ron Bolin cc: freebsd-current@freebsd.org Subject: Re: current libmd md5c.c compile fails In-reply-to: Your message of "Sat, 28 Dec 1996 09:29:52 EST." <32C52EE0.167EB0E7@mindspring.com> Date: Sat, 28 Dec 1996 16:15:25 +0100 Message-ID: <3518.851786125@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <32C52EE0.167EB0E7@mindspring.com>, Ron Bolin writes: >In today's current 12-28-96 08:30 EST the libmd/md5c.c fails compilation >due to missing the correct md5.h. I searched for all md5.h files and >found none that will work with this C module. > >Ron >cc -O -I/usr/src/lib/libmd -c /usr/src/lib/libmd/md5c.c -o md5c.o >/usr/src/lib/libmd/md5c.c:40: sys/md5.h: No such file or directory >*** Error code 1 > You probably need to: cd /usr/src make includes or something similar. Your /usr/include/sys should be a symlink to /sys/sys where you will find md5.h (I hope :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Sat Dec 28 08:54:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA17234 for current-outgoing; Sat, 28 Dec 1996 08:54:15 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA17229 for ; Sat, 28 Dec 1996 08:54:12 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA00274; Sat, 28 Dec 1996 17:53:50 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA04610; Sat, 28 Dec 1996 17:53:49 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id RAA13103; Sat, 28 Dec 1996 17:34:28 +0100 (MET) From: J Wunsch Message-Id: <199612281634.RAA13103@uriah.heep.sax.de> Subject: Re: weird w/who on -current To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 28 Dec 1996 17:34:27 +0100 (MET) Cc: bsdcur@shadows.aeon.net (mika ruohotie) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612271818.UAA02679@shadows.aeon.net> from mika ruohotie at "Dec 27, 96 08:18:21 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As mika ruohotie wrote: > my w and who arent working right, i've changed the whole system twice now... ...but you haven't been following the -current list very closely, didya? Recompile your xterm and xdm. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Dec 28 10:25:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA20202 for current-outgoing; Sat, 28 Dec 1996 10:25:14 -0800 (PST) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA20197 for ; Sat, 28 Dec 1996 10:25:04 -0800 (PST) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.4/8.8.3) id UAA13539; Sat, 28 Dec 1996 20:20:54 +0200 (EET) From: mika ruohotie Message-Id: <199612281820.UAA13539@shadows.aeon.net> Subject: utils/screen misc/screen ??? To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 28 Dec 1996 20:20:54 +0200 (EET) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199612281634.RAA13103@uriah.heep.sax.de> from J Wunsch at "Dec 28, 96 05:34:27 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > As mika ruohotie wrote: > > my w and who arent working right, i've changed the whole system twice now... > ...but you haven't been following the -current list very closely, > didya? i believe i have... :\ > Recompile your xterm and xdm. *blush* will do... and the topic, well, when i started to compile different things, i noticed there's two different versions of screen, what's the difference? looks to me other is just older... DISTNAME= screen-3.7.2 CATEGORIES= misc and DISTNAME= screen-3.6.2 CATEGORIES+= utilities > cheers, J"org mickey From owner-freebsd-current Sat Dec 28 15:47:43 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA02403 for current-outgoing; Sat, 28 Dec 1996 15:47:43 -0800 (PST) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA02390 for ; Sat, 28 Dec 1996 15:47:41 -0800 (PST) Received: (from jdp@localhost) by austin.polstra.com (8.8.3/8.8.3) id PAA08810; Sat, 28 Dec 1996 15:47:30 -0800 (PST) To: freebsd-current@freebsd.org Path: not-for-mail From: jdp@polstra.com (John Polstra) Newsgroups: polstra.freebsd.current Subject: Re: cvsup standard-supfile for current Date: 28 Dec 1996 15:47:29 -0800 Organization: Polstra & Co., Seattle, WA Lines: 17 Distribution: local Message-ID: <5a4bih$8j7@austin.polstra.com> References: <32C5310B.2781E494@mindspring.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <32C5310B.2781E494@mindspring.com>, Ron Bolin wrote: > I noticed the the standard cvsup file changed around 12-15-96 and no > longer works with cvsup 13.5. Did I miss something, I had to use an old > version of the supfile to get it to work. Yes, what you missed was CVSup-14.0. :-) I'll add comments to the example cvsupfiles mentioning that they only work with version 14.0 and later. You can still use the older style of cvsupfile with any version. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Dec 28 16:36:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA05423 for current-outgoing; Sat, 28 Dec 1996 16:36:42 -0800 (PST) Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA05418 for ; Sat, 28 Dec 1996 16:36:38 -0800 (PST) Received: from baloon.mimi.com (sjx-ca56-03.ix.netcom.com [205.186.122.67]) by dfw-ix10.ix.netcom.com (8.6.13/8.6.12) with ESMTP id QAA26548; Sat, 28 Dec 1996 16:32:12 -0800 Received: (from asami@localhost) by baloon.mimi.com (8.8.4/8.6.12) id QAA16276; Sat, 28 Dec 1996 16:32:08 -0800 (PST) Date: Sat, 28 Dec 1996 16:32:08 -0800 (PST) Message-Id: <199612290032.QAA16276@baloon.mimi.com> To: bsdcur@shadows.aeon.net CC: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG In-reply-to: <199612281820.UAA13539@shadows.aeon.net> (message from mika ruohotie on Sat, 28 Dec 1996 20:20:54 +0200 (EET)) Subject: Re: utils/screen misc/screen ??? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * CATEGORIES+= utilities That category ceased to exist a long time ago. :) I don't know where you picked it up from, but you can delete your /usr/ports/utils safely, as all the ports in there have been moved out to other places more than a year ago! Satoshi From owner-freebsd-current Sat Dec 28 16:51:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA06075 for current-outgoing; Sat, 28 Dec 1996 16:51:07 -0800 (PST) Received: from mule0.mindspring.com (mule0.mindspring.com [204.180.128.166]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA06066 for ; Sat, 28 Dec 1996 16:51:04 -0800 (PST) Received: from rlb.users.mindspring.com (user-168-121-25-139.dialup.mindspring.com [168.121.25.139]) by mule0.mindspring.com (8.8.2/8.7.3) with SMTP id AAA18810 for ; Sun, 29 Dec 1996 00:51:02 GMT Message-ID: <32C5C074.41C67EA6@mindspring.com> Date: Sat, 28 Dec 1996 19:51:00 -0500 From: Ron Bolin X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Todays Build 12-28 ypserv and libc depend ?? Content-Type: multipart/mixed; boundary="------------446B9B3D2781E494167EB0E7" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------446B9B3D2781E494167EB0E7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit In building todays current 12-28. I found that building usr.sbin/ypserv required me to build and install libc b4 I could build ypserv. Is this intentional, if so fine. Otherwise, under my configuration, I could not complete a make world because ypserv depended on __dns_getanswer being linked and as far as I could see it was in libc, which had not been installed yet. Once I did a cd lib;make install, then make world and ypserv linked fine and the complete source tree finished the build. Seems odd to have to break out of the world and do a partial install. Just checking sanity here and my configuration. Ron -- **************************************************************************** Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: 770-992-8877 **************************************************************************** --------------446B9B3D2781E494167EB0E7 Content-Type: text/plain; charset=us-ascii; name="bug" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bug" cc -O -o ypset ypset.o ===> usr.sbin/ypserv cc -O -I. -DDB_CACHE -c yp_svc.c cc -O -I. -DDB_CACHE -c /usr/src/usr.sbin/ypserv/yp_server.c cc -O -I. -DDB_CACHE -c /usr/src/usr.sbin/ypserv/yp_dblookup.c cc -O -I. -DDB_CACHE -c /usr/src/usr.sbin/ypserv/yp_dnslookup.c cc -O -I. -DDB_CACHE -c ypxfr_clnt.c cc -O -I. -DDB_CACHE -c /usr/src/usr.sbin/ypserv/yp_main.c cc -O -I. -DDB_CACHE -c /usr/src/usr.sbin/ypserv/yp_access.c cc -O -I. -DDB_CACHE -c /usr/src/usr.sbin/ypserv/yp_svc_udp.c cc -O -I. -DDB_CACHE -o ypserv yp_svc.o yp_server.o yp_dblookup.o yp_dnslooku p.o ypxfr_clnt.o yp_main.o yp_error.o yp_access.o yp_svc_udp.o yp_dnslookup.o: Undefined symbol `___dns_getanswer' referenced from text segment *** Error code 1 --------------446B9B3D2781E494167EB0E7-- From owner-freebsd-current Sat Dec 28 17:52:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA07859 for current-outgoing; Sat, 28 Dec 1996 17:52:33 -0800 (PST) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id RAA07852 for ; Sat, 28 Dec 1996 17:52:28 -0800 (PST) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA27960; Sat, 28 Dec 1996 20:50:29 -0500 From: Bill Paul Message-Id: <199612290150.UAA27960@skynet.ctr.columbia.edu> Subject: Re: Todays Build 12-28 ypserv and libc depend ?? To: rlb@mindspring.com (Ron Bolin) Date: Sat, 28 Dec 1996 20:50:28 -0500 (EST) Cc: current@freebsd.org In-Reply-To: <32C5C074.41C67EA6@mindspring.com> from "Ron Bolin" at Dec 28, 96 07:51:00 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Ron Bolin had to walk into mine and say: > This is a multi-part message in MIME format. > > --------------446B9B3D2781E494167EB0E7 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > In building todays current 12-28. I found that building usr.sbin/ypserv > required me to build and install libc b4 I could build ypserv. Is this > intentional, if so fine. Otherwise, under my configuration, I could not > complete a make world because ypserv depended on __dns_getanswer being > linked > and as far as I could see it was in libc, which had not been installed > yet. Yes, this is intentional. I know it sucks. The alternative is to chop out the part of the resolver code that ypserv now needs and duplicate it in the ypserv sources. This would require both sets of sources to be updated if a new BIND release is merged into the system. The reason that ypserv needs this __dns_getanswer() function is that it now supports async DNS lookups. ypserv will do a DNS lookup is a client searches the host.byname or hosts.byaddr maps for a non-local hostname or address, and the maps were built with the YP_INTERDOMAIN flag (or if ypserv was started with the -n flag). The problem is that DNS lookups can take a long time; this could cause ypserv to block for a long time waiting for the nameserver to respond, which in turn could cause other NIS clients to block, which sucks. The old solution for this was to fork() a child ypserv process to handle the lookup; this lets the parent proceed and handle other requests, but a fork() is expensive and if you have a lot of clients you can swamp the server. With the async resolver, ypserv assembles and transmits DNS requests itself using UDP and saves the request in a queue. It can then go back to what it was doing. When the reply arrives, it select() will notice the data pending on the resolver socket and process the reply. This way you don't block while waiting for DNS replies, and you don't have to fork(). However, once you get the reply datagram, you have to parse it into a hostent structure in order to do anything with it. There's a function called gethostanswer() in src/lib/libc/net/gethostbydns.c, but it's declared static which prevents other programs from calling it. I wanted to use gethostanswer() but I didn't want to duplicate the code, so I added a wrapper called __dns_getanswer() that could be used to call the gethostanswer() routine from ypserv. ypserv used to depend on __gethostbydnsname() and __gethostbydnsaddr() instead of __dns_getanswer(), but the former two functions were there long before I wrote ypserv so nobody noticed. > Once I did a cd lib;make install, then make world and ypserv linked fine > and the complete source tree finished the build. > > Seems odd to have to break out of the world and do a partial install. > Just checking sanity here and my configuration. Your configuration is fine. I'm not qualified to judge your sanity. Hell, I'm not even qualified to judge mine. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-current Sat Dec 28 18:47:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA09936 for current-outgoing; Sat, 28 Dec 1996 18:47:22 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA09928 for ; Sat, 28 Dec 1996 18:47:19 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id VAA00985 for current@freebsd.org; Sat, 28 Dec 1996 21:47:17 -0500 (EST) From: "John S. Dyson" Message-Id: <199612290247.VAA00985@dyson.iquest.net> Subject: MUST REBUILD LKM'S To: current@freebsd.org Date: Sat, 28 Dec 1996 21:47:16 -0500 (EST) Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The latest VFS clustering improvements require rebuilding all your LKM's. Don't mess around thinking that they will work without rebuilding. They won't!!! John dyson@freebsd.org