Re: libedit replacement for libreadline

2001-07-17 Thread Garance A Drosihn
At 3:19 AM -0700 7/16/01, Kris Kennaway wrote: >Hmm. We could easily provide a libreadline port for ports to >use, as long as libedit does everything that's needed for the >in-tree users (are there any others apart from bc and gdb?) >The only danger is if future versions of those grow the need >t

Re: Latest version of mega header file POSIX update

2001-07-14 Thread Garance A Drosihn
Back on March 15/2001, Garrett Wollman wrote: >I have finally produced another version of the big header file patch >for people to look at. I'm still running an older (January) kernel >and world based on these changes. I have verified that these still >build on i386-architecture systems. I'm lo

Re: cannot print to remote printer

2001-07-13 Thread Garance A Drosihn
At 12:18 PM +0200 7/12/01, Anton Berezin wrote: >I would also propose to guard printjob.c wait calls from this sort of >error in the future; after all, it *was* an action at a distance, and >it was not strictly easy to find the culprit. Here's a patch which I think covers all the bases mentione

Re: cannot print to remote printer

2001-07-12 Thread Garance A Drosihn
At 8:45 AM +0200 7/12/01, Joerg Wunsch wrote: >Anton Berezin <[EMAIL PROTECTED]> wrote: > >> if (fork() == 0) { >> - signal(SIGCHLD, SIG_IGN); >> + signal(SIGCHLD, SIG_DFL); > >This is unportable. His change is pretty portable, as I have been run

Re: unified pwutil library - thoughts?

2001-07-11 Thread Garance A Drosihn
At 11:36 AM -0500 7/2/01, Damieon Stark wrote: >Below is the message I sent about a unified libpwutil, and >possibly integrating it into FreeBSD. _ANY_ feedback, positive >or negitive would be appreciated as it will help to validate my >existance ;) I like the idea, but I must admit to not havin

Re: cannot print to remote printer

2001-07-11 Thread Garance A Drosihn
At 9:43 PM +0200 7/11/01, Anton Berezin wrote: > At 2:55 PM +0200 7/11/01, Georg-W. Koltermann wrote: > > With current as of June 20 I can no longer print to a remote > > printer. Syslog says "filter 'f' exited (retcode=108)". > > > > I added a "set -x" to the filter which is a shell program

Re-thinking WARNS?=2 a bit, wrt multiple platforms

2001-07-06 Thread Garance A Drosihn
In the freebsd-current mailing list there is a debate raging under "chgrp broken on alpha systems", which is much larger than the minute little chgrp command. It also strikes me as something larger than freebsd-current. Let me continue my trend of being an idiot by claiming it is a "freebsd deve

Re: cannot print to remote printer

2001-06-22 Thread Garance A Drosihn
At 2:42 PM +0200 6/22/01, Georg-W. Koltermann wrote: >Hi, > >with current as of June 20 I can no longer print to a remote printer. >Syslog says "filter 'f' exited (retcode=108)". Looking at that section of code, lpd is just doing: if (ifilter < 0) status.w_retcode = 100;

Re: cannot print to remote printer

2001-06-22 Thread Garance A Drosihn
At 2:42 PM +0200 6/22/01, Georg-W. Koltermann wrote: >Hi, > >with current as of June 20 I can no longer print to a remote printer. >Syslog says "filter 'f' exited (retcode=108)". > >I added a "set -x" to the filter which is a shell program, and sure >enough the last action it does is an "exit 0".

Re: symlink(2) [Was: Re: tcsh.cat]

2001-06-17 Thread Garance A Drosihn
At 2:28 PM -0700 6/17/01, Matt Dillon wrote: >:On Sun, Jun 17, 2001 at 11:31:41 -0700, Jordan Hubbard wrote: >:> It seems your argument to disallow null symlinks got somehow taken >:> as an argument to disallow all "invalid" symlinks then. >: >: >:To say it more clear: now I even not against ""-sy

Re: HEADS UP: doc/ tree frozen (was Re: HEADS UP for/usr/src/release/doc & /usr/doc)

2001-06-11 Thread Garance A Drosihn
At 1:18 AM +0400 6/12/01, Andrey A. Chernov wrote: >I understand now. That info you can provide from the beginning >to minimize messages exchange. I am open to discuss how to fix it. I think it is probably best to let Bruce Mah figure out why it has broken, and let him provide the best "immediate

Re: Updated: cp -t patch (w/ commentary)

2001-04-26 Thread Garance A Drosihn
At 6:08 PM -0700 4/25/01, Dima Dorfman wrote: >Garance A Drosihn <[EMAIL PROTECTED]> writes: > > Dimi has written one or two different patches to xargs. Did > ^^^ <-- should be 'a', but that's okay. :-) Note that I also wrote: > > If you need

Re: Updated: cp -t patch (w/ commentary)

2001-04-25 Thread Garance A Drosihn
At 10:01 AM -0400 4/25/01, John W. De Boskey wrote: >Hi David, Brian, > >Thank you for taking the time to reply. I hope you were >able to review the patch also. Every time you have asked for people's opinions, they have said that it seems wrong to made add a specific option to the 'cp' comman

Re: cp -d dir patch for review (or 'xargs'?)

2001-04-22 Thread Garance A Drosihn
At 1:19 PM -0700 4/21/01, Dima Dorfman wrote: >Does that mean everyone is blind and missed my arrogant >cross-post of the amazingly short patch to do this, or >are we just interested in discussing it and not testing >the implementation? ;-) Well, I'm in the middle of a massive reorganization of a

Re: cp -d dir patch for review (or 'xargs'?)

2001-04-19 Thread Garance A Drosihn
At 10:08 PM -0700 4/19/01, Dima Dorfman wrote: >Garance A Drosihn <[EMAIL PROTECTED]> writes: > > Or maybe something to indicate where the list of arguments >> should go in a command. Hrm. Let's say '-Y replstr' or >> '-y[replstr]' (no blan

Re: cp -d dir patch for review (or 'xargs'?)

2001-04-19 Thread Garance A Drosihn
At 3:39 PM -0400 4/19/01, John W. De Boskey wrote: >I have added a -d dir option to cp. This allows the target >directory to be specified at the head of the command line >instead of the tail. This makes cp work much more nicely with >tools like xargs... (allowing for major performance improvem

Re: sysinstall option for softupdates

2001-03-10 Thread Garance A Drosihn
At 11:51 AM -0800 3/10/01, Jordan Hubbard wrote: >H. OK, you intrigued me enough by this that I just went >ahead and did it in -current. :) Let me know what you think, >come tomorrow's snapshot. Ooo. Might this be MFC-able before 4.3 goes out the door? -- Garance Alistair Drosehn

RE: Anybody else seeing a broken /dev/lpt with SMP on -current?

2001-01-13 Thread Garance A Drosihn
At 6:55 PM -0800 1/12/01, John Baldwin wrote: >On 13-Jan-01 Jordan Hubbard wrote: > > If anybody wants a fuller traceback then I'll compile up a kernel > > with debugging symbols, but it's going to be pretty sparse anyway > > since it basically only shows the trap() from the page fault and > >

Re: status of http://www.freebsd.org/handbook/makeworld.html

2000-11-27 Thread Garance A Drosihn
At 7:57 PM -0800 11/27/00, Kent Stewart wrote: >Garance A Drosihn wrote: > > I would think that somewhere along the line we would update >> the information in the handbook, just out of courtesy. If >> we have no intention of ever updating this web page, then

Re: status of http://www.freebsd.org/handbook/makeworld.html

2000-11-27 Thread Garance A Drosihn
At 10:37 PM -0500 11/27/00, Andrew Partan wrote: >On Mon, Nov 27, 2000 at 10:18:55PM -0500, Garance A Drosihn wrote: >> That disclaimer also does not explain why the web page itself >> THINKS that it has a section on mergemaster, but it has no >> such section. > >

Re: status of http://www.freebsd.org/handbook/makeworld.html

2000-11-27 Thread Garance A Drosihn
At 6:39 PM -0800 11/27/00, Kent Stewart wrote: >Garance A Drosihn wrote: >> >> Unless I'm missing something, which is certainly possible, it >> seems to me that >> http://www.freebsd.org/handbook/makeworld.html >> >> is missing some in

status of http://www.freebsd.org/handbook/makeworld.html

2000-11-27 Thread Garance A Drosihn
Unless I'm missing something, which is certainly possible, it seems to me that http://www.freebsd.org/handbook/makeworld.html is missing some information that it used to have. There is no section on mergemaster, for instance, even though there IS a link to that section, and that link thinks

Re: new rc.network6 and rc.firewall6

2000-10-24 Thread Garance A Drosihn
At 2:58 PM -0700 10/24/00, Jordan Hubbard wrote: > > The scripts themselves have the ordering dependencies. The > > startup system runs them in the proper order. I don't know > > if this is pre-computed or redone each boot. > >I'm really curious about this, myself. One of the reasons the SYSV >

Re: Fdescfs updates--coming to a devfs near you!

2000-09-14 Thread Garance A Drosihn
At 11:48 AM +0200 9/14/00, Poul-Henning Kamp wrote: >I must admit that I think in general that /dev/std{in,out,err} >and /dev/fd is bogus. It looks like something which happened >"because we can" more than something which has a legitimate need. > >If anything I would propose we ditch it... I thi

Re: AFS.

2000-08-30 Thread Garance A Drosihn
At 11:30 AM -0400 8/30/00, Thomas David Rivers wrote: >Just F.Y.I > > I understand that, today, IBM is announcing it will open-source >AFS via the IBM Public Source license.. > > Some quotes I've seen: > >"IBM announced today the open source contribution of a >high-performance file system tech

Re: ACPI project progress report (final?)

2000-08-09 Thread Garance A Drosihn
At 12:30 AM +0900 8/10/00, Mitsuru IWASAKI wrote: >Hi, here is the latest (and maybe final?) report on our ACPI >project's progress. > >We are ready now to merge our work on ACPI into main source tree! > >[...skipping...] >Folks, there are a lot of exciting and cool things, like Processor >and Dev

Re: Request for review (LPDEST vs PRINTER)

2000-08-02 Thread Garance A Drosihn
At 10:39 PM +0100 8/2/00, Mark Ovens wrote: >I originally sent this to -committers but was advised that the >maintainers and -hackers or -current was more appropriate. > >I've posted some patches for PR 14682 which include some changes >to the source code for lpr(1), lprm(1) etc. > >Could someone

Re: *** HEADS UP *** rc.conf changes (security)

2000-07-28 Thread Garance A Drosihn
At 12:41 AM +0200 7/29/00, Eivind Eklund wrote: >After discussion with obrien, jhb, and dwithe (and non-protests from >the other committers present), I'm changing the defaults for remote >services in /etc/defaults/rc.conf to the least dangerous >configuration, and making sysinstall write out overr

Re: Request for comments: new `lpd' suite feature

2000-07-16 Thread Garance A Drosihn
At 12:09 AM -0400 7/15/00, Louis A. Mamakos wrote: >I almost hate to bring this up, but I think the unnamed-here >proposed replacement for our lpd allows you to set your PRINTER >environment variable to something like > > [EMAIL PROTECTED] > >louie For what it's worth, I think that feature

Re: Request for comments: new `lpd' suite feature

2000-07-16 Thread Garance A Drosihn
At 9:25 PM -0700 7/14/00, Thomas D. Dean wrote: >How would this work with printers on local networks? > >Say, a print server 192.168.1.73? > If you do not have a special DNS entry for that printer, then this new synthetic-printcap option would do nothing for you. In other words, you would contin

Re: Request for comments: new `lpd' suite feature

2000-07-14 Thread Garance A Drosihn
At 5:39 PM -0400 7/14/00, Garrett Wollman wrote: >Around here, we have a convention that each printer has a record >in the DNS for printername.lpd-spooler which points to the print >server for that printer. It occurred to me that, if there are no >local printers, no additional information is need

Re: subtle problem du jour....

2000-07-06 Thread Garance A Drosihn
At 12:50 AM -0600 7/6/00, John Galt wrote: >Is there a quick and dirty way for the label editor to detect if >a BIOS is using LBA? This actually sounds like a setup in which >the error condition should be alerted on placing / on a cylinder >higher than 1024 rather than long after you can do anyth

Re: subtle problem du jour....

2000-07-05 Thread Garance A Drosihn
At 3:18 PM -0700 7/5/00, Mike Smith wrote: >someone else wrote: > > The only time this showed up as problem was that when I reinstalled > > the loader (and related forth files), loader silently was not able > > to read /boot or /modules- the key word here is "silently". > > > > There ought to be a

Re: bug: "device ether" no longer optional

2000-06-29 Thread Garance A Drosihn
At 1:10 PM -0700 6/29/00, Kris Kennaway wrote: >On Thu, 29 Jun 2000, Archie Cobbs wrote: > > > Luckily I happened to have seen -current in the past couple of days. > > Trying to search -current on the web site for the appropriate keywords > > yeilded only articles from the years 1997 through 1999,

Re: Gnome INSANE shared memory usage

2000-06-23 Thread Garance A Drosihn
At 4:00 PM -0400 6/23/00, Kelly Yancey wrote: >On Fri, 23 Jun 2000, Shawn Halpenny wrote: > > > I have not had any of the problems he's describing. I have never > > modified my shared memory settings in my kernel config either. If > > the problem is indeed Xfree 4.0, then I guess it must be a dr

Re: VMware detection code in boot loader

2000-06-11 Thread Garance A Drosihn
At 10:47 AM -0700 6/11/00, Mike Smith wrote: >It's not a port, it's a platform. We probably want to add extra >words to detect other platform features, eg. i386, alpha, ia64, >etc. but that doesn't invalidate the basic idea. For instance, I might be running the vmware program itself under linux,

Re: mktemp() patch

2000-06-10 Thread Garance A Drosihn
>It's probably better to just get rid of the PID and use randomness >throughout the name than to use 72 characters. 64^6 vs. 2*(72^3) . I seem to be in the minority on this, but in general I *like* the idea that the tempfiles include the pid. It's bad because it makes it easier for an evil-perso

Re: mktemp() patch

2000-06-08 Thread Garance A Drosihn
At 12:07 AM -0500 6/9/00, Dan Nelson wrote: >I still suggest not using symbols at all, since I'd like to >be able to quickly remove tempfiles by hand without worrying >if I have to escape # or ^, etc. Uh, if I understand the update, the '#' is ALREADY used for this, in the current implementation.

Re: mktemp() patch

2000-06-08 Thread Garance A Drosihn
At 8:47 PM -0700 6/8/00, Kris Kennaway wrote: >On Fri, 9 Jun 2000, Boris Popov wrote: > > > Count both, nwfs and smbfs, because any program can > > attempt to create temporary file on these filesystems. Files > > with an invalid file name will be rejected, and this will > > cost an additional

Re: mktemp() patch

2000-06-08 Thread Garance A Drosihn
At 12:51 PM +0200 6/8/00, Samuel Tardieu wrote: >On 8/06, Jeroen Ruigrok van der Werven wrote: >| -On [2608 03:12], Kris Kennaway ([EMAIL PROTECTED]) wrote: >| >Instead of using only alphabetic characters, the patch uses the following >| >character set: >| > >| >0123456789ABCDEFGHIJKLMNOPQRST

Re: Dual-booting: FreeBSD, NetBSD and OpenBSD

2000-05-28 Thread Garance A Drosihn
At 10:34 AM -0600 5/28/00, Warner Losh wrote: >I need to setup a machine that will boot FreeBSD, NetBSD and >OpenBSD. Assume I have an insane amount of disk space. What's >the best way to accomplish this? Last time I tried it, the >partition ID numbers were all the same, making this difficult >

Re: HEADS UP Re: cvs commit: ... Change to queue(3)

2000-05-24 Thread Garance A Drosihn
At 2:25 PM -0700 5/23/00, Jake Burkholder wrote: > > jake2000/05/23 13:41:02 PDT > > Log: > > Change the way that the queue(3) structures are declared; > > don't assume that the type argument to *_HEAD and *_ENTRY > > is a struct. > > > > Suggested by: phk > > Reviewed by:

Re: Wide-char support and libc

2000-05-22 Thread Garance A Drosihn
On May 21/2000, Clive Lin wrote to -current&-i18n: > > The only way i found to link motif programs is by using > > > > http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz > >This seems the solution of wc* routines in FreeBSD. > >Could any one tell us, is this project dead ? Last I knew, D

Re: Wide-char support and libc

2000-05-17 Thread Garance A Drosihn
At 2:41 AM -0400 5/17/00, Thimble Smith wrote: >On Tue, May 16, 2000 at 11:52:32PM -0400, Donn Miller wrote: > > Anyone like the idea of adding wide char support to our libc? Maybe > > we could port it over from {Net,Open}BSD or BSDi. This would add the > > header file , etc. > >There's a mailin

Re: Motif is now Open Source 8)

2000-05-16 Thread Garance A Drosihn
At 9:35 AM -0600 5/16/00, Nate Williams wrote: > > If this Open Motif can be distributed as a port or package for FreeBSD > > itself (and it seems to me that it can), then what hassle is that for > > JDK on FreeBSD? > >It requires two downloads to get a working JDK system. No other OS >requires m

Re: Motif is now Open Source 8)

2000-05-16 Thread Garance A Drosihn
> > I think that you no longer have to include Motif with the JDK. > > Just let the distribution of Motif come from freebsd.org , i.e., > > a port or a package. > >Too much hassle IMO. I'd *much* rather distribute it as part of the >package, and I'm looking into how feasible it would be to distri

Re: OpenSSH 2.1

2000-05-15 Thread Garance A Drosihn
At 10:52 PM -0700 5/14/00, Kris Kennaway wrote: >* No longer a dependency on RSA (and therefore rsaref for US folks): > SSH2 can handle DSA keys which have no patent or usage restrictions. > This means we could now enable SSH2 out of the box in a crypto > installation, with no post-installation

Re: One more question (different now)

2000-05-09 Thread Garance A Drosihn
At 7:08 PM -0400 5/9/00, Simon Shapiro wrote: >Given: > >typedef struct junk { >... >} junk_t > >volatile junk_t trash; > >What I want to do is zero out trash. > >bzero(trash, sizeof(junk_t)); > >produces a warning about loss of volatility. >So, how do I make everyone happy? Write a 'bzer

Re: db 1.85 --> 2.x or 3.x?

2000-05-02 Thread Garance A Drosihn
At 1:05 PM +0200 5/2/00, Brad Knowles wrote: > A thread on news.software.nntp got me checking into this, >and now I've gotten very curious. From what I can determine, it >looks like what is integrated into FreeBSD is Berkeley db 1.85 >(in /usr/src/libc/db), although there is a port for 2.7.

Re: Archive pruning

2000-04-28 Thread Garance A Drosihn
At 1:21 PM -0400 4/28/00, Garrett Wollman wrote: ><<[EMAIL PROTECTED]> said: > > > I've wanted to do this on occasion. Where are these pre-FreeBSD > > history records available? > >You can buy them on CD-ROM, IIRC. In order to do so, however, you >must first take out a SCO ``Historical UNIX Vers

Re: Recent commit changes extattr backing file format, usersbeware

2000-04-19 Thread Garance A Drosihn
At 3:41 AM -0400 4/19/00, Robert Watson wrote: >I hope not to change the format any further. I've been considering >introducing a backing file header version number of some sort, but >this is only necessary if we think the backing file format will >change much more. > >Comments welcome. If you'r

Re: Snapshot building machines back on line.

2000-04-06 Thread Garance A Drosihn
At 11:13 AM -0700 4/6/00, Jordan K. Hubbard wrote: >For the latest 4.0-STABLE snapshots: >ftp://releng4.freebsd.org/pub/FreeBSD > I can get to the above machine just fine, but it does not seem to let me use anonymous-ftp login's... --- Garance Alistair Drosehn = [EMAIL PROTECTED

Re: periodic daily output (passwd diffs)

2000-03-28 Thread Garance A Drosihn
At 6:33 PM -0500 3/28/00, Thimble Smith wrote: >On Tue, Mar 28, 2000 at 07:49:23PM +0300, Giorgos Keramidas wrote: > >At first glimpse, everything seems identical.. so, where is the > >difference? I realized that I had changed ONLY the password, and this > >was shown in the diffs in this strange

Re: Experts only please! (was Re: Preliminary SMP/BGL patch)

2000-03-24 Thread Garance A Drosihn
At 10:01 AM -0800 3/24/00, Matthew Dillon wrote: >This is not a 'normal Matt patch' that 'just works'. Ok, it seems to >just work, but it's not a normal Matt patch. If there were a >designation before 'early alpha' this patch would get it. "Rough-draft proposal for early alpha versi

Re: when is 4.0 up for release ?

2000-03-07 Thread Garance A Drosihn
>On 2000-Mar-08 10:38:23 +1100, Dan Potter <[EMAIL PROTECTED]> wrote: > > Has anyone thought about the problem I posted a few days ago > >(getcwd() breaks on unionfs in some conditions)? That seems like > >a pretty big problem to me... maybe not too many people use unionfs > >though, I don't know.

Re: openssh question

2000-03-06 Thread Garance A Drosihn
At 10:37 PM +0100 3/6/00, Christian Weisgerber wrote: >William Woods <[EMAIL PROTECTED]> wrote: > > How do we update it, ie, when a updated version comes out. > >OpenSSH doesn't really have releases. The upstream version is >straight out of the OpenBSD repository. I assume several of our >develope

Re: openssh question

2000-03-06 Thread Garance A Drosihn
At 11:29 AM +0100 3/6/00, Edwin Kremer wrote: >On a side note: last week, Tatu Ylonen, principal author of SSH, posted a >message on the SSH mailing-list (in the thread about the new SSH2 license) >saying that: > > " OpenSSH is based on my version from back in 1995 or 1996. The > " OpenSSH fo

Re: oddness in -current

2000-03-06 Thread Garance A Drosihn
At 12:17 AM -0700 3/6/00, Chris Wasser wrote: >I was just watching a buildworld happen when I noticed (specifically >in gcc, and a few other places) the following warning several times: > >warning: mktemp() possibly used unsafely; consider using mkstemp() > >I'm not sure if it's a big deal or not,

Re: ssh strangeness in -current...

2000-03-06 Thread Garance A Drosihn
At 11:23 PM -0500 3/5/00, John Baldwin wrote: >On 06-Mar-00 Kris Kennaway wrote: > > On Mon, 6 Mar 2000, Oliver Fromme wrote: > > > >> the ports (yeah, stupid me), to no avail. It complained about some > >> RSA library missing. > > > > Did you read the error message? Perhaps you should. Perhaps r

Re: which(1), rewritten in C?

2000-03-03 Thread Garance A Drosihn
At 10:36 PM -0500 3/2/00, Laurence Berland wrote: >Which is also a perl script, which sh uses (since it's not a builtin >there). It does the same thing as the 'which' that's built in to bash >and tcsh and csh If you do a 'type -a which' or 'help which' in bash, you'll find that 'which' is not a

Re: Please review: fdisk -e -> -I

2000-03-02 Thread Garance A Drosihn
At 10:29 AM +1030 3/3/00, Greg Lehey wrote: >On Thursday, 2 March 2000 at 13:43:17 -0700, Warner Losh wrote: > > I hate to follow up my own post. It would appear that -e was added > > before 3.3R went out the door. Given that, I think the patch should > > look more like the following: > >I'm st

Re: current.freebsd.org (FTP)

2000-02-29 Thread Garance A Drosihn
At 6:53 PM +0100 2/29/00, Dave Boers wrote: >It is rumoured that Forrest Aldrich had the courage to say: > > No, it allows you to log in, but will not accept anonymous logins. > > Login Incorrect > >This has been going on for nearly 20 hours now. About 20 hours >ago the machine was briefly unreach

Re: openssh uses /etc (bad)

2000-02-25 Thread Garance A Drosihn
At 1:51 PM +0100 2/25/00, Ollivier Robert wrote: >I just saw that openssh (thanks Mark!) is using /etc/ for its configuration >file. As the author of the "--with-etcdir" option of SSH (back in '96) and >for the sake of consistency, I'd like to create a /etc/ssh directory and >move everything there

Re: Heads up! OpenSSH is about to enter the tree.

2000-02-24 Thread Garance A Drosihn
At 11:37 PM -0800 2/23/00, Jordan K. Hubbard wrote: >Since it came down to making openssl actually useful for something or >taking it out of the tree, we accelerated progress somewhat on the >openssh integration work. Sounds like a good idea. >I will also be delaying -current's release date unti

Re: "Fixing" init.

2000-02-21 Thread Garance A Drosihn
At 11:45 AM -0800 2/19/00, Alfred Perlstein wrote: >* Alfred Perlstein <[EMAIL PROTECTED]> [000219 02:22] wrote: > > I remeber being a newbie and getting burned by the need to explicitly > > turn a line 'off' in my /etc/ttys file instead of simply deleting it. > > > > This fixes it using a trivial

Re: Things to consider in CURRENT

2000-02-21 Thread Garance A Drosihn
At 4:47 PM +0100 2/21/00, Morten Seeberg wrote: >Hi, I just installed: FreeBSD fw.home 4.0-2208-CURRENT and have a few >comments: > >It seems that BASH in 4.x needs Combat 3.x, but why cant BASH work this out >for it self? One day when installing BSD without X (which automatically >installs Co

Re: openssl in -current

2000-02-19 Thread Garance A Drosihn
At 10:31 PM -0800 2/19/00, Kris Kennaway wrote: > > if 4.0 is delayed, I want it delayed for things which are actually busted, > > and not to move features from the ports collection to the base system. > >No-one's talking about delaying 4.0. Not directly, but all the work trying to figure this ou

Re: openssl in -current

2000-02-19 Thread Garance A Drosihn
At 8:09 PM -0800 2/19/00, Jordan K. Hubbard wrote: > > Having _a_ general-purpose cryptography toolkit in the base system allows > > us to add in all sorts of cool things to FreeBSD (https support for fetch, > > openssh, random cryptographic enhancements elsewhere). OpenSSL just > > happens to be

Re: rpc.lockd

2000-02-12 Thread Garance A Drosihn
At 5:41 AM +0100 2/12/00, Ferdinand Goldmann wrote: >On Fri, 11 Feb 2000, Jordan K. Hubbard wrote: > > > Well, I'd first be very interested to know if anyone has even seen > > this work. :) > >Well, will the 4.0 lockd also work with a 3.3 system? I could need >a working lockd, but I do not want to

Re: 4.0 CODE FREEZE vs patches to lpr/lpc

2000-01-24 Thread Garance A Drosihn
>On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > > > On the 29th of January, I'll be freezing the -current branch (well, > > OK, the trunk). That means NO commits without my review first ... Could someone commit the 2-line bug fix in bin/15728 before yet another system release goes out the door?

Re: bzip2 in src tree

2000-01-24 Thread Garance A Drosihn
At 9:54 AM -0800 1/24/00, David O'Brien wrote: >On Mon, Jan 24, 2000 at 12:16:32PM +0100, Oliver Fromme wrote: > > > And just how do I increase the space on a CDROM??? > > > > Include another CD-ROM. > >You are missing the point. The installation CDROM only shows >you the packages on that CDROM,

Re: Please help spread the CVSup mirror load more evenly

2000-01-21 Thread Garance A Drosihn
At 9:42 PM +0100 1/21/00, Jesper Skriver wrote: >On Fri, Jan 21, 2000 at 03:34:42PM -0500, Garance A Drosihn wrote: > > At 10:43 AM -0800 1/21/00, John Polstra wrote: > > >This is another in my series of occasional nags to try to get > > >people to use some of th

Re: Please help spread the CVSup mirror load more evenly

2000-01-21 Thread Garance A Drosihn
At 10:43 AM -0800 1/21/00, John Polstra wrote: >This is another in my series of occasional nags to try to get people >to use some of the less heavily loaded CVSup mirrors. In the US >alone, we have 8 mirror sites now, named (duh) cvsup[1-8].FreeBSD.org. >The newest, cvsup8, is a very high-capacit

Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test

2000-01-12 Thread Garance A Drosihn
Back on December 27, 1999, Garance A Drosihn wrote: >At 8:55 AM -0500 12/24/99, Robert Watson wrote: >>For example, imagine that the user has a >>number of hard links to the file in question. > > Okay, here's my newer version of the code, which takes > into account

Re: Additional option to ls -l for large files

2000-01-12 Thread Garance A Drosihn
At 4:51 PM -0500 1/12/00, Garrett Wollman wrote: >< said: > > > In 'ls' we are not talking about a block count, we are talking about > > a byte-count. > >ls -s Hmm, valid point. 'ls -l' is not using a block count though, and so all of my previous comments still make sense for 'ls -l' and the new

Re: Additional option to ls -l for large files

2000-01-12 Thread Garance A Drosihn
At 6:01 PM -0800 1/11/00, Rodney W. Grimes wrote: >Garance wrote: > > personally, I'd just as soon use K, M, and G and have it mean > > the base-10 values. If I'm looking at a decimal number for one > > file (because it's small enough), I don't want a base-2 version > > of the similar number for

Re: Additional option to ls -l for large files

2000-01-11 Thread Garance A Drosihn
At 2:49 PM -0800 1/11/00, Rodney W. Grimes wrote: > > >Another thing that ``works for me''. Only make it ki, mi, and gi > > >to fit with the new binary mode international appreviation standards, > > >unless of cource you use base 10 divisors. > > > > Why not KB, MB or GB, since that's what you're

Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test

1999-12-27 Thread Garance A Drosihn
At 8:55 AM -0500 12/24/99, Robert Watson wrote: >For example, imagine that the user has a >number of hard links to the file in question. Okay, here's my newer version of the code, which takes into account multiple hard links, and also makes it so the spooled data file is owned by daemon instead o

Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test

1999-12-27 Thread Garance A Drosihn
At 8:55 AM -0500 12/24/99, Robert Watson wrote: >... keep in mind that this optimization does not produce behavior >behavior in some cases. For example, imagine that the user has a >number of hard links to the file in question. If the file is copied and >then deleted, then the link count is decr

Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test

1999-12-23 Thread Garance A Drosihn
At 2:33 AM -0800 12/10/99, Alfred Perlstein wrote: >Can someone take a look at this? > >Basically, it makes the link to the file, if it can unlink the original >it will then chown the spool file if it can't delete or read the original >then the user didn't have permission and it backs out. Okay,

Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test

1999-12-10 Thread Garance A Drosihn
At 7:24 PM +0100 12/10/99, Andre Albsmeier wrote: >On Fri, 10-Dec-1999 at 13:16:16 -0500, Garance A Drosihn wrote: > > I'm thinking you'd what to add an lstat call after creating the > > hardlink. Check the new file to see if it's a symlink, and if it > >Can

Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test

1999-12-10 Thread Garance A Drosihn
At 2:33 AM -0800 12/10/99, Alfred Perlstein wrote: >Can someone take a look at this? > >Basically, it makes the link to the file, if it can unlink the original >it will then chown the spool file if it can't delete or read the original >then the user didn't have permission and it backs out. I'm th

[PATCHES] Two fixes for lpd/lpc for review and test

1999-12-07 Thread Garance A Drosihn
oling partition. That may not seem like much of an issue when you're printing 10-Kbyte files, but when you're throwing around 200-Meg files (for color plotters, for instance), then it can be very nice. The text from my previous attempts follow. - - - - - - - - - - - - - - - - - - - - - -

Re: ps on 4.0-current

1999-11-24 Thread Garance A Drosihn
At 8:03 AM + 11/24/99, Brian Somers wrote: > > This was discussed close to death before the changes were committed, > > and the current behaviour (restricted access) has been agreed by > > general consensus to be the most appropriate. > >My reading of the thread was ``I'm going to cache ps arg

Fixes for lpd/lpc (printing), before 3.4?

1999-11-20 Thread Garance A Drosihn
bin/13549, is also confirmed in bin/14975. >Date: Mon, 6 Sep 1999 18:14:55 -0500 >To: [EMAIL PROTECTED] >From: Garance A Drosihn <[EMAIL PROTECTED]> >Subject: Two fixes for lpd/lpc (printing) >Cc: [EMAIL PROTECTED] > >I noticed problem-report bin/9362, which reported that

Re: PATCH for testing

1999-11-15 Thread Garance A Drosihn
At 6:22 PM -0800 11/15/99, Matthew Dillon wrote: >Well, I think there is an issue in the proc struct bloat but I disagree >strongly about modifying argv - any worthwhile code uses setproctitle() >now simply because the argv space is highly dependant on the number of >arguments pass

Re: ps -e

1999-11-15 Thread Garance A Drosihn
At 3:48 PM -0700 11/15/99, Lyndon Nerenberg wrote: > > "Matthew" == Matthew Dillon <[EMAIL PROTECTED]> writes: > >Matthew> Why don't we get rid of the 'e' option to ps while we >Matthew> are at it considering how much of a security hole it is. > >I wouldn't nuke it completely. Make

Re: Network booting, I'm off to work (was Re: GENERIC buildbroken)

1999-11-03 Thread Garance A Drosihn
At 11:09 AM -0800 11/3/99, Mike Smith wrote: >I can either spend more time trying to deal with what I see >as FUD, or actually do the work, and I'm picking the latter. > >[...snip...]. We need to keep ourselves focussed on where we're >going, and right now, in this context, it means that we need

Re: GENERIC build broken

1999-11-03 Thread Garance A Drosihn
At 12:17 PM -0700 11/3/99, Nate Williams wrote: > > BOOTP in > > the kernel will go _when_there_is_an_acceptable_alternative_. > >You've already stated *THERE IS AN ACCEPTABLE ALTERNATIVE*, and it's >PXE. (I can use all caps instead of underscores to make a point too :) I thought he was saying t

Re: minor heads up - /etc/make.conf{,.local} being moved

1999-11-02 Thread Garance A Drosihn
At 9:10 AM -0800 11/2/99, Doug Barton wrote: >Matthew Dillon wrote: > > I think it is necessary to make it exit for now, because what we are > > really doing is a net-0 gain in files... turning what used to be > > functionality in /etc/make.conf.local into /etc/make.conf. The > >

Re: request for review: move of /var/cron/log to /var/log/cron.log

1999-09-06 Thread Garance A Drosihn
At 8:09 PM +0200 9/6/99, Andreas Klemm wrote: >On Sun, Sep 05, 1999 at 11:32:35AM +0200, Nick Hibma wrote: > > -/var/cron/log 600 3 100 * Z > > +/var/log/cron.log 600 3 100 * Z > > /var/log/amd.log 664 7 100

Two fixes for lpd/lpc (printing)

1999-09-06 Thread Garance A Drosihn
I noticed problem-report bin/9362, which reported that the 'lpc start' command no longer works. (it claims to start the queue, but it doesn't actually start it). I came up with a two or three line fix for that bug, and sent it in as problem-report bin/13549. This patch should work on both freeb

Re: Any chances to solve bin/7973?

1999-08-24 Thread Garance A Drosihn
At 8:44 AM +0200 8/24/99, Cejka Rudolf wrote: >Garance A Drosihn wrote (1999/08/23): > > > Why would the filter be reading the control file? It is just a > > filter, supposedly reading from stdin and writing to stdout... > >Yes and not. > >You can look into apsfi

Re: Any chances to solve bin/7973?

1999-08-23 Thread Garance A Drosihn
At 10:37 PM +0200 8/23/99, Cejka Rudolf wrote: >Is anybody capable to solve or fix bin/7973 in lpd? I have found the >problem is still there (FreeBSD-3.2). Or am I anything missing/doing wrong? > >bin/7973: Bad control file owner in case of remote printing. The problem >is that print filters ("if"

Re: VMware X11 and -current

1999-08-03 Thread Garance A Drosihn
At 3:08 PM -0400 8/3/99, Ayan George wrote: >I've been wondering -- are there any plans for a FreeBSD version >of VMware? The makers of VMware are probably wondering if they would sell enough copies of a FreeBSD-based version. If you would buy such a product, then let them know. Check www.vmwa

Re: net.inet.tcp.always_keepalive on as default ?

1999-06-04 Thread Garance A Drosihn
At 11:24 AM -0700 6/4/99, David Greenman wrote: > someone else wrote: >> >> I still think the right thing is: >> default to keepalives. >> set the timeout to a week. > > I don't support increasing the default timeout. That would cause > problems for a lot of server systems that rely on

Re: Which DHCP client

1999-02-09 Thread Garance A Drosihn
At 9:25 AM -0800 2/9/99, David O'Brien wrote: > I already have a bmaked ISC v2 dhclient. I bmaked both so I would > more informated about how easy either would be to add to the tree. > > I will spend some time today and reflect on which client I still > prefer in import. Does anyone have a good f

Re: adding DHCP client to src/contrib/

1999-02-08 Thread Garance A Drosihn
At 6:02 PM -0800 2/8/99, Steve Kargl wrote: >Mike Holling wrote: >> ... What's the problem? It's not like putting emacs in the base >> install or anything. I still run FreeBSD on a 386/40 with a 40M MFM >> main drive, and even so I'm not worried about the "bloat" of adding >> DHCP. > > Bloat by

<    1   2   3