Re: panic in get_next_dirent

d with -jN. > I am upgrading kernel to the latest revision as of today. > > Could this be something that you accidentally broke and then fixed while > pursuing your NFS issue? > > -- > Andriy Gapon > -- Brian Somers

Re: make install failed on XFree86-4-client (with 6/10 -current)

Well, this has been happening for about a year on my dev box. It's not gcc 3.1 specific. I've never gotten around to figuring out why it works on some machines. On Sat, 29 Jun 2002 19:41:51 -0700, David O'Brien wrote: > On Sat, Jun 29, 2002 at 11:30:48PM +0100, Brian Som

Re: make install failed on XFree86-4-client (with 6/10 -current)

I've been seing this problem for ages on my dev box, but it doesn't happen on other boxes. The problem is because the glxinfo program uses CCLINK to link, but it's a c++ program. Changing the CCLINK to CXXLINK works. I have no idea why there's no problem on some machines. On Mon, 17 Jun 2002 1

Re: loader failure

> > Brian Somers <[EMAIL PROTECTED]> writes: > > > This was fixed an hour or so ago. Phk backed out the daddr_t size > > > change pending investigation. > > > > Does that fix the loader too, or just the kernel? > > I'm not sure, I'm ju

Re: loader failure

> Brian Somers <[EMAIL PROTECTED]> writes: > > This was fixed an hour or so ago. Phk backed out the daddr_t size > > change pending investigation. > > Does that fix the loader too, or just the kernel? I'm not sure, I'm just rebuilding now. Remember, /bo

Re: loader failure

> > no matter which kernel I try to boot. Booting my new kernel with the > > old loader (from the DP1 dist) works fine until it tries to start > > init(8): > > > > spec_getpages: preposterous offset 0xfff8f446 > > exec /sbin/init: error 5 > > spec_getpages: preposterous offset 0xfff8

Re: CURRENT and P-IV problems

> On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote: > > Try disabling -pipe when building the compiler. This seems to make > > things more stable here (CFLAGS=-O in /etc/make.conf) - as if > > building the kernel with -pipe sometimes produces a kernel that >

Re: CURRENT and P-IV problems

Hi, Try disabling -pipe when building the compiler. This seems to make things more stable here (CFLAGS=-O in /etc/make.conf) - as if building the kernel with -pipe sometimes produces a kernel that subsequently murders the compiler with sig11/sig4 all the time. This is just marginally more th

Re: ipfilter not broken for me

> On Sat, Apr 27, 2002 at 04:01:28PM +1000, Darren Reed wrote: > > In some email I received from Doug Barton, sie wrote: > > > On Fri, 26 Apr 2002, Ruslan Ermilov wrote: > > >=20 > > > > I tested this on i386 only with 2 days old -CURRENT (today's is > > > > broken due to the import of latest IPFi

Re: Revision 1.88 of kern_linker.c breaks module loading for diskless

> On Fri, 26 Apr 2002, Brian Somers wrote: > > BS>The intent is to discover whether there's a filesystem yet (vn_open() > BS>will die horribly otherwise). > BS> > BS>My use of rootdev is (obviously) flawed. AFAICT, either rootvp > BS>or rootvnode should

Re: Revision 1.88 of kern_linker.c breaks module loading for diskless

> In message <[EMAIL PROTECTED]>, Harti Brandt write > s: > >the check for rootdev != NODEV introduced in rev 1.88 breaks loading of > >kernel modules from an NFS mounted root in diskless configurations. > >Dropping in gdb and printing rootdev shows -1 which is, I assume, NODEV. > > Ah, that woul

Re: cvs commit: src/usr.sbin/ppp Makefile async.c async.h atm.c bundle.c ccp.c ccp.h chap.c chap.h chat.c command.c datalink.c datalink.h defs.c defs.h ether.c exec.c i4b.c lcp.c lcp.h main.c mppe.c netgraph.c netgraph.h physical.c physical.h route.c tcp.c ...

> Hello. > > > brian 2002/03/30 04:30:11 PST > > > Modified files: > > usr.sbin/ppp Makefile async.c async.h atm.c bundle.c > > ccp.c ccp.h chap.c chap.h chat.c > > command.c datalink.c datalink.h defs.c > >

Re: mktime() doesn't fix deadzones...

Hi, I've cc'd -standards as I think this would be of interest there. IMHO the SQL code you quote in the PR should fail with an ``invalid time'' error. Personally I like the fact that mktime() returns -1 - it allows date's -v option to act sanely, although I must admit it was a PITA to get ri

Re: segfault in getpwuid()?

Yes, I think I can ! I'll bet the binary in question is using libc.so.4 *AND* libc.so.5 because of a third library that has a libc.so.4 dependency. This confused me for quite some time with apache. for f in /usr/local/lib/*.so do objdump -x $f 2>/dev/null | grep -q NEEDED.*libc.so.4 && echo

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

> >As discussed at BSDCon, the release engineers are committed to > > releasing a relatively stable snapshot of FreeBSD -CURRENT on or > > around April 1, 2002. Obviously, a lot of major components are still > > in progress, but a great deal of work has already been accomplished, > > and coul

Re: HEADS UP: Be nice to -CURRENT ( "1 week Feature Slush" )

> > To this end, we would like to request that commits for the next 7 > > days to HEAD be made with special care. -CURRENT is in pretty good > > shape right now, so we're not requiring approval for all commits. > > I have a Perl-5.6.1 upgrade. Is that too risky? Apart from the perl > stuff its

Re: PPP Dial of External Modem Fails in 'Current'

> > I rebuilt 'Current' over the weekend with a make buildworld/install world > and make buildkernel/install kernel and 'ppp -ddial papchap' gives the > following error(s) when trying to dial an external modem: > > Warning set ifadr: Invalid command > Warning set ifadr: Falied 1 > > > Doe

Re: rev 1.61 of /sys/netinet/in.c breaks ISDN

> Hi, > > with rev 1.61 of in.c I4B directly hangs up after dialing out. At the > moment I run a current kernel as of yesterday with a netinet directory > as of today except for in.c (which is at rev 1.60 here) and everything > works fine. Hi, Can you give me more details about the failure - er

Re: rm -rf /usr/obj/usr/src/usr.bin/tip helps build -CURRENT

> On Tue, Nov 27, 2001 at 04:20:54PM +0000, Brian Somers wrote: > > > > A ``rm -fr /usr/obj; make -DNOCLEAN buildworld'' is quicker than > > ``make buildworld'' anyway :*) > > > > Really? Is this recommended? Yes, except I meant ``rm

Re: rm -rf /usr/obj/usr/src/usr.bin/tip helps build -CURRENT

> On Tue, 27 Nov 2001 18:03:45 +0200, Ruslan Ermilov wrote: > > | > Did you do a component build without `make obj'? That would leave > | > turds, and I'm pretty sure the buildworld target doesn't repeat the > | > cleandir target. > | > > | depend is included by make(1) automatically, before a

Re: rm -rf /usr/obj/usr/src/usr.bin/tip helps build -CURRENT

> On Tue, Nov 27, 2001 at 06:35:49AM -0800, David Wolfskill wrote: > > Found this to be helpful after seeing: > > > > >>> stage 2: cleaning up the object tree > > ... > > ===> usr.bin/tip > > ".depend", line 886: Inconsistent operator for tip > > make: fatal errors encountered -- cannot continue

Re: cvsup-devel port build problem (pm3-base)

John Polstra <[EMAIL PROTECTED]> wrote: > In article <[EMAIL PROTECTED]>, > Brian Somers <[EMAIL PROTECTED]> wrote: > > I sent John Polstra a similar patch some time ago Any news about > > getting this committed John (P) ? > > There is already an

Re: cvsup-devel port build problem (pm3-base)

I sent John Polstra a similar patch some time ago Any news about getting this committed John (P) ? > Hi, > > I ran into some problems building the cvsup-devel > port. In one of it's dependants, the c file is attempting > to include which is nolonger valid. > > /usr/ports/lang/pm3-bas

ACPI panic at boot time in -current

Hi, I was wondering if anybody has any suggestions about why this might be happening in -current: Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x32f34 data=0xf9c+0x1028 syms=[0x4+0x49c0+0x4+0x61a]- Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 198

Re: Anyone had luck with 3Com HomeConnect ADSL Modem Dual Link???

> Hi... > > Has anyone on this list had any luck dealing with 3Com HomeConnect ADSL > Modem Dual Link? > I am stuck with this peace of hardware and please don't flame me ;) > > I connect the modem to an xl card sitting on the PC. > > I am running a fairly recent -CURRENT system. Here is my /etc

Re: stdio change, other libraries needs bumping too!

> "Andrey A. Chernov" wrote: > > On Thu, Sep 20, 2001 at 18:32:57 +0400, Andrey A. Chernov wrote: > > > After stdio changes 4.4 binaries linked with libtermcap/libcurses refuse > > > to work: > > > > > > /usr/libexec/ld-elf.so.1: /usr/lib/libcurses.so: Undefined symbol "__stdout > p" > > >

More SIG4s during make world

Hi, Just a quick note to say that my -current box has started dropping cores during make world again. I have a kernel from August 11 that works ok, and had one from August 18 that was causing sig 4 at random places. I accidently overwrote my Aug 18 kernel.old, but Aug 25, 27 and 28 are still

Re: another panic (mix ppp and usb to taste)

> As I was trying to let the Palm Pilot connect to my desktop > through usb using PPP, I tried to run > > /usr/sbin/ppp -quiet -direct -nat < /dev/ugen0 FWIW, that should be: /usr/sbin/ppp -quiet -direct -nat <>/dev/ugen0 as ppp -direct needs to be able to write to descriptor 0 t

Re: Copyright Contradiction in libalias

> +---[ Brian Somers ]-- > | > Check with Charles to see if he really wants to abandon copyright claims > | > to his code, or whether he was really implying some really liberal open source > | > license. > | > | With the BSD Copyright (only

Re: Copyright Contradiction in libalias

> Check with Charles to see if he really wants to abandon copyright claims > to his code, or whether he was really implying some really liberal open source > license. With the BSD Copyright (only) he keeps the intellectual copyright on the original. That's what I've changed it to (as per his a

Re: Copyright Contradiction in libalias

This is my fault. Charles gave me permission to change these files to a BSD license a while ago. It looks like I got it wrong :-/ I'll fix it now. > I was doing some things in libalias when something caught my eye, > > $ cat alias.c > /* -*- mode: c; tab-width: 8; c-basic-indent: 4; -*-

Re: Syntax change in ppp?

> Brian Somers schrieb: > > > > > Hi, > > > > > > after the latest updates I just noticed a different behaviour of ppp. > > > > > > in /etc/ppp/ppp.linkup I had an additional line > > > iface clear > > > for my profile to

Re: Syntax change in ppp?

> Hi, > > after the latest updates I just noticed a different behaviour of ppp. > > in /etc/ppp/ppp.linkup I had an additional line > iface clear > for my profile to get rid of stuffed up IP pairs. After the latest update > this entry also clears my defaultroute, but only after redialing. > >

Should developers run current ? (was: XDM and X)

I've cc'd freebsd-current here. This is a followup to a small thread on the UK user group list about the stability of -stable. Joe Karthauser <[EMAIL PROTECTED]> wrote: > On Sat, Aug 04, 2001 at 02:42:44PM +0100, Nik Clayton wrote: > >=20 > > This hasn't suddenly changed in FreeBSD -- the -curr

Re: /home: mount pending error: blocks 14 files 3

> > On 02-Aug-01 Sheldon Hearn wrote: > > > > > > On Thu, 02 Aug 2001 09:33:41 MST, John Baldwin wrote: > > > >> I get these messages when I reboot or crash before the background > >> fsck finishes sometimes. Sometimes I get them when the filesystems > >> are clean, too. They always happen w

Re: /home: mount pending error: blocks 14 files 3

> On Thu, 02 Aug 2001 10:42:29 +0100, Brian Somers wrote: > > > If the error keeps turning up, I would guess that you have a 0 or > > empty fsck field in /etc/fstab and fsck -s therefore not fixing the > > problem. > > Nope. I have passno set for the filesyste

Re: /home: mount pending error: blocks 14 files 3

The error means that your machine crashed with soft-updates enabled, leaving 14 blocks and 3 files still allocated on disk (using up blocks & inodes). If the error keeps turning up, I would guess that you have a 0 or empty fsck field in /etc/fstab and fsck -s therefore not fixing the problem.

Re: Userbase of -current

> In message <[EMAIL PROTECTED]> Vincent Poy >writes: > : Somehow I always thought there were more than 50 people who are > : "really running" current. We do stress test it though and it had > : performed flawlessly over the past 8 years. Question though, does anyone > : happen to know what

Re: panic from May

A current world with a May 23 kernel works ok, so you may be lucky :) > I get the following panic on a GENERIC kernel from around May 23: > > (copied by hand) > > /usr/src/sys/kern/kern_synch.c:385: sleeping with "vm" locked from >/usr/src/sys/vm/vm_pager.c:428 > panic: sleeping process owns a

Re: tcsh.cat

> < said: > > > Here's an example of a complication: what is the semantics of /tmp/foo/bar > > where foo is a symlink to ""? I think the pathname resolves to > > /tmp//bar and then to /tmp/bar, but this is surprising since foo doesn't > > point anywhere. > > But this is at least consistent with

Re: trouble with glob patch (ftp exploit)

> In message <[EMAIL PROTECTED]>, "default013 - > subscriptio > ns" writes: > > Hi, thanks for the tip, but I attempted the new instructions and got this > > error... > > It seemed like it went a bit farther but... > > > > [/usr/src/lib/libc]# make all install > > Warning: Object directory not c

Re: PPP modem dial is completely broken

> With new PPP I can't dial to my provider anymore. Two variants: > > 1) PPP says "Clearing choked output queue" and connection stuck forever > with carrier on. Nothing else happens. > > 2) PPP says "Too many IPCP NAKs sent - abandoning negotiation" and drop > carrier forever without further red

Re: PCCARD and -current

I got the same results as you. It eventually worked when I copied the entry matching my card into /etc/pccard.conf and hard-wired the irq as the same as the pcic device (9 in my case): $ cat /etc/pccard.conf irq 9 card "Lucent Technologies" "WaveLAN/IEEE" config auto "wi" 9

Re: Unrecognised CBCP packet [strange problems with ppp(8)]

> Brian Somers wrote: > > > I've had reports of this in the past. The other end is sending a > > ``code 5'' packet - something that doesn't appear in the spec :( > > > > ppp(8) just ignores these (emitting a warning), they shouldn't

this mornings installkernel is bad

Hi all, It looks like this mornings buildkernel/installkernel is not a good thing to install. Trying to buildworld with it produces sig4s (and I think some sig6s) from the compiler: May 30 12:58:39 dev /boot/kernel/kernel: pid 20690 (cc1), uid 0: exited on signal 4 (core dumped) May 30 13:00

Re: cvs commit: src UPDATING

> In message Michael Reifenberger >writes: > : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using > : whine? > > Nope. vmware does the job too, and I believe star-office. > Warner -- Brian <[EMAIL PROTECTED]>

Re: softupdates related problem in -current

> On Sun, May 27, 2001 at 10:18:43PM -0700, Doug Barton wrote: > > Another problem I'm having in -current right now is with softupdates. Wh= > en > > the system panic'ed the first time, it came up ok and fsck'ed fine with no > > apparent loss of data. However, during the fsck it complained bit

Re: Unrecognised CBCP packet [strange problems with ppp(8)]

I've had reports of this in the past. The other end is sending a ``code 5'' packet - something that doesn't appear in the spec :( ppp(8) just ignores these (emitting a warning), they shouldn't be causing any problems themselves (even if CBCP is actually being used). Try enabling IPCP logging.

Re: ** HEADS UP **: sys/miscfs file systems moved

> On Wed, May 23, 2001 at 12:52:40PM +0100, Brian Somers wrote: > > > Dear -CURRENT users, > > > > > > Please note that: > > > > > > - FDESC, FIFO, NULL, PORTAL, PROC, UMAP and UNION file > > > systems were repo-copied from sys/mi

Re: ** HEADS UP **: sys/miscfs file systems moved

> Dear -CURRENT users, > > Please note that: > > - FDESC, FIFO, NULL, PORTAL, PROC, UMAP and UNION file > systems were repo-copied from sys/miscfs to sys/fs. > > - Renamed the following file systems and their modules: > fdesc -> fdescfs, portal -> portalfs, union -> unionfs. > > - Renamed

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

John/peter, could you repo-copy src/sys/dev/digi/digiio.h to src/sys/sys/digiio.h ? Ta. > On Fri, 18 May 2001, Brian Somers wrote: > > > > On Thu, 17 May 2001, Warner Losh wrote: > > > I quite like the fact that the programming interface is > > > separat

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

> On Thu, 17 May 2001, Warner Losh wrote: > > > In message <[EMAIL PROTECTED]> Brian > > Somers writes: > > : Solaris calls it's ioctl files /usr/include/sys/_io.h so I'd > > : spell digiio.h /usr/include/sys/digi_io.h. > > > > Actually

Re: background fsck

This happens to me ``almost all the time'' on my dev box: Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a 25406382600 15113835%/ devfs110 100%/dev procfs 440 100%/

Re: Where to put include files (was: cvs commit: src Makefile.inc1)

he question is ``where to put them ?''. Warner wrote: > In message <[EMAIL PROTECTED]> Brian > Somers writes: > : Solaris calls it's ioctl files /usr/include/sys/_io.h so I'd > : spell digiio.h /usr/include/sys/digi_io.h. > > Actually, the more I think

Where to put include files (was: cvs commit: src Makefile.inc1)

> > Most headers that define ioctls are in . I think there should > > be at most one directory for ioctl headers and it shouldn't be a subdir > > of /usr/include/sys (/usr/include/sys/dev doesn't even reflect the > > kernel tree). > > > Might I guess it should probably be called /usr/include/sys

Re: cvs commit: src Makefile.inc1

> On Wed, 16 May 2001, Warner Losh wrote: > > > In message <[EMAIL PROTECTED]> Brian Somers writes: > > : How should this be done - and where should I install digiio.h if > > : that's what's required ? > > > > I think that ppi device sets t

Re: cvs commit: src Makefile.inc1

> On Wed, 16 May 2001, Warner Losh wrote: > > > In message <[EMAIL PROTECTED]> Ruslan Ermilov writes: > > : FWIW, my gross hack to usr.sbin/kbdcontrol also worked: > > > > I tend to dislike adding ../../sys to the includes list since they > > might not be compatible with the host's sys files use

Re: Huh??!? xterm: Error 14, errno 2: No such file or directory

Have you got v1.23 of sys/fs/devfs/devfs_vnops.c and are you running as non-root ? > On Tue, May 15, 2001 at 01:34:27AM -0700, Peter Wemm wrote: > > David Wolfskill wrote: > > > > > Built -CURRENT & rebooted after mergemaster as usual, and some X > > > applications (xbattbar; xlockmore; oclock)

Re: Huh??!? xterm: Error 14, errno 2: No such file or directory

This makes xterm work again. Any objections to a commit ? > David Wolfskill wrote: > > > Built -CURRENT & rebooted after mergemaster as usual, and some X > > applications (xbattbar; xlockmore; oclock) work OK, but no xterm. At > > least, not from X (XF86-4.0.3). I tried using Ctl-Alt-F2 to ge

Re: cp -u patch

> On Mon, 7 May 2001 10:18:38 -0700 > [EMAIL PROTECTED] wrote: > > Lets try another realistic example: > > > > cp -uvp ab* cde*.f* g? h/*.i? j/kl /m > > What's the find | cpio invocation for that? When you come up with it, it > > echo ab* cde*.f* g? h/*.i? j/kl /m | cpio ... > >

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

> It is inconceivable that the proposed patch to 'xargs' would > increase your running time. I don't mean the standard '-I' > change, which would certainly destroy performance, but the > proposed patch to 'xargs' which solves your specific problem > in a general way. > > I'm still curious as to

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

[.] > The "xargs weenies" have also offered an explicit patch that > could be tried, but that patch is being ignored by you. It > is not a matter of talking ourselves to death, it's a matter > that we're looking for feedback from anyone who wants to > respond to the proposed xargs changes. >

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

> On Mon, Apr 23, 2001 at 11:33:24AM -0700, John W. De Boskey wrote: > >After some feedback, I have changed the patch slightly. Rename > > -d to -t and remove the requirement for the option to have a > > value. > > I thought people generally agreed the right fix was to add functionality > to

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

> Rodney W. Grimes <[EMAIL PROTECTED]> wrote: > > > Before anyone starts writing scripts, consider that {} will be > > > replaced by xargs with (roughly) ARG_MAX - 10 characters worth of the > > > stuff coming off the pipe. If your combined arguments plus > > > environment exceeds ARG_MAX

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

> No rain here, it is ARG_MAX - 2048: > -s size > Set the maximum number of bytes for the command line length pro- > vided to utility. The sum of the length of the utility name and > the arguments passed to utility (including NULL terminators) will >

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

> On Sun, 22 Apr 2001 13:16:31 +0100, Brian Somers wrote: > > > On Sat, 21 Apr 2001 20:04:31 +0100, Brian Somers wrote: > > > > > Sorry for butting in. Adding new non-portable functionality to solve the >problem > > > > > which could be adequitel

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

> On Sat, 21 Apr 2001 20:04:31 +0100, Brian Somers wrote: > > > Sorry for butting in. Adding new non-portable functionality to solve the problem > > > which could be adequitely taken care of using existing and well known > > > techniquies is not appropriate, I com

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

> Brian Somers <[EMAIL PROTECTED]> writes: > > I looked at your patches and immediately thought ``these patches > > can't be right'' as I was expecting it to deal with things such as > > > > xargs -I [] echo args are [], duplicated are [] >

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

> Dima Dorfman <[EMAIL PROTECTED]> wrote: > > I don't have a copy of SuSv2 or anything else that defines -I and -i, > > http://www.secnetix.de/~olli/susv2/xcu/xargs.html > > > but from what I can gather, -i is the same as "-I {}" and -I allows > > things like this: > > Not exactly. The diff

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

> Putting that option into cp seems rather GNUish to me, but > not very UNIXish. :-) Yes. I think most people agree that changing cp is not good. > Just my 2 Euro cents. > > Regards >Oliver > > -- > Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München > Any opinions expr

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

I looked at your patches and immediately thought ``these patches can't be right'' as I was expecting it to deal with things such as xargs -I [] echo args are [], duplicated are [] I'm also dubious about the patches working for large volumes on standard input. At this point I scrapped the e

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

> So we have two problems: > > 1) Calling cp(1) repetitively is inefficient. > > 2) The argument list is too big for cp(1). > > Extending cp(1) will not solve (2). Extending xargs(1) will solve both. > So why is an extension to cp(1) being proposed? I wasn't proposing that cp should be change

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

> Sorry for butting in. Adding new non-portable functionality to solve the problem > which could be adequitely taken care of using existing and well known > techniquies is not appropriate, I completely agree with you on that. And I'm still waiting to see those well known techniques. > --

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

> On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote: > > > How do you do this in a script: > > > > cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/. > > for i in `find /path/to/source -type f`; do > cp $i /path/to/dest/ > done >

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

> > On Fri, Apr 20, 2001 at 07:26:18PM -0700, Rodney W. Grimes wrote: > > > > > > (cat bigfilelist; echo destdir) | xargs cp > > > > > > I like this version of the patch!! It's much much cleaner than > > > hacking up cp or xargs, it even follows the unix principle of > > > using simple tools an

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

> 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 blank after -y). If no [replstr] is > > given on -y, it defaults to the two characters '[]'. > > Then o

Re: sysctl optimisations (was: Filesystem gets a huge performance boost)

> OK... this brings up the question of what other cool optimizations are > there that may have been disabled in the past for reasons that are no > longer pertinent? It might be worthwhile to create an /etc/sysctl.conf file > with commented out examples of configurations for various systems.

Re: FW: Filesystem gets a huge performance boost

> Why VMIO dir works better if directories are placed close to each other? I > think it only makes the cache data of an individual directory stay in the > memory longer. Is there a way to measure the effectiveness of the disk > drive's cache? The real performance gain is seen when doing stuff wi

Re: FW: Filesystem gets a huge performance boost

[.] > > The second improvement, contributed by > > [EMAIL PROTECTED], is a new directory allocation policy (codenamed > > "dirpref"). Coupled with soft updates, the new dirpref code offers up > > to a 60x speed increase in gluk's tests, documented here:" > > > > >ht

Re: FW: Filesystem gets a huge performance boost

> Another important change is that it is no longer necessary to run > tunefs in single user mode to activate soft updates. All that is > needed is to add the "softdep" mount option to the partitions you > want soft updates enabled on in /etc/fstab." [.] > I especially like not having to run tu

Re: make release broken in telnetd

Hi, I'm not convinced that the patch will help. It looks like the error is because it's using the ppp.lo that was built with crypto support but without the mppe bits. Maybe other objects (such as ccp.o in this case - which seems to be built with HAVE_DES and therefore includes MPPEAlgorithm

Re: Recent interface/routing changes breaks on-demand PPP

> On Sun, Mar 25, 2001 at 02:46:22AM +0100, Brian Somers wrote: > > > > On Fri, Mar 23, 2001 at 23:11:56 +0000, Brian Somers wrote: > > > > > 1. Ppp is in -auto mode (or a ``set mode auto'' has been done). > > > > >Here, pp

Re: Problem with tun device and trafshow/tcpdump?

I found this message in one of my inboxs - I forgot to reply :*) I believe this was fixed last October (at BSDCon)... can you confirm ? > Hi everyone. > > Ok apologies first to anyone who has been asked this question before, I've > searched the mail lists and cannot find anything like this rece

Re: Recent interface/routing changes breaks on-demand PPP

> > On Fri, Mar 23, 2001 at 23:11:56 +, Brian Somers wrote: > > > 1. Ppp is in -auto mode (or a ``set mode auto'' has been done). > > >Here, ppp configures the interface as soon as it sees the ``set > > >ifaddr'' line and never

Re: Recent interface/routing changes breaks on-demand PPP

> On Fri, Mar 23, 2001 at 23:11:56 +0000, Brian Somers wrote: > > 1. Ppp is in -auto mode (or a ``set mode auto'' has been done). > >Here, ppp configures the interface as soon as it sees the ``set > >ifaddr'' line and never undoes that configura

Re: Recent interface/routing changes breaks on-demand PPP

> > Do you mean that "add" PPP command now intentionally broken for any > > address excepting *ADDR? Then, what is the reason to have numeric argument > > there? Or do you mean that PPP must be fixed now? Where is the fix? > > > I mean that: > > 1. If you use HISADDR, ppp(8) will automatically

Re: Proposal to mergemaster

> > Hi, > > After 100erts of mergemaster sessions, I'm looking for a way to improve > mergemaster. > > 1st thing, mergemaster displays per default all in changed files. That's > ok for the first time, but if you maintain many hosts, this is annoying a > lot. > > There should be an options to d

Re: cp MAKEDEV /dev - on a system with devfs

> Brian Somers <[EMAIL PROTECTED]> wrote: > > > >I thought only sysv kept non-startup executables in /etc. > > There's one real oddity in FreeBSD: > > [EMAIL PROTECTED]:/etc > :; ll rmt > lrwxrwxrwx 1 root wheel 13 Jan 28 13:42 rmt

Re: cp MAKEDEV /dev - on a system with devfs

> In message <[EMAIL PROTECTED]>, Jean Louis Ntakpe writes: > >Hi, > > > >In /usr/src/etc/Makefile: > > > >"make distribution" is still trying to copy MAKEDEV to /dev > >on a system with devfs mounted to /dev. > >Since devfs is default, is this behaviour correct or my > >/etc/make.conf is missin

Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)

> I suggest you take a look at > > >http://www.usenix.org/publications/library/proceedings/als2000/full_papers/browndavid/browndavid_html/ Thank you ! This confused the hell out of me when I first bumped into it on Solaris ! Something to read in the morning -- Brian <[EMAIL PROTECTED]

Re: Strange fopen() behaviour

Just to follow up, this was fixed with v1.9 of src/lib/libc/stdio/findfp.c Thanks Maxim ! > > I've cc'd -current as I think something more sinister is going on. > > To recap, I'm having trouble running xsane on -current from about two > > days ago. fopen() is failing... > > > > The attached

Re: What's changed recently with vmware/linuxemu/file I/O

> On Thu, Feb 08, 2001 at 04:58:17AM -0800, Julian Elischer wrote: > >=20 > > Looks like some way of clustering this might achieve a lot. > >=20 > > what does systat -vmstat or vmstat 1 > > show? > > Better still, I guess we could do a linux-truss > > and see what it's doing... > > I believe that

Re: [Fwd: cvs commit: src/lib/libc/stdio findfp.c]

Yes, at least half way through an installworld, xsane works again :-) Thanks. > Hi, > > Please check to see if it would solve your problems with fopen(). > > -Maxim > Original Message > Subject: cvs commit: src/lib/libc/stdio findfp.c > Date: Wed, 7 Feb 2001 09:34:50 -0800 (P

Re: What's changed recently with vmware/linuxemu/file I/O

> Bruce Evans wrote: > > > > On Tue, 6 Feb 2001, Josef Karthauser wrote: > > > > > I'm wondering what's changed recently to cause vmware2 running on > > > the linuxemu to lose a lot of performance with disk I/O. > > > > Use of cmpxchg and possibly other SMP pessimizations. > > > > > A couple o

Re: Strange fopen() behaviour

> I've cc'd -current as I think something more sinister is going on. > To recap, I'm having trouble running xsane on -current from about two > days ago. fopen() is failing... > > The attached patch exposes more about what's wrong. Interestingly > enough, the file it's trying to create is in

Strange fopen() behaviour (was: xsane patch to maintainer)

> Hi, > > Would you mind if I commit the attached patch for the xsane port ? > It makes sense - rather than dropping a core when fopen() fails (and > fclose() is called with a NULL arg). It happens when your home > directory isn't writable :-/ I've cc'd -current as I think something more si

Re: pcm driver and DEVFS

> On Fri, Feb 02, 2001 at 04:11:29PM +0900, Yoshihiro Koya wrote: > > Hello, > > > > I did make world a couple days ago. The system was built from cvsup'd > > source on Jan 30: > > >-- > > elf make world started on Tue Jan 30 06:2

Re: ppp/samba (configuration?) question

You should get away with adding your ``set ifaddr'' line to ppp.linkdown (you can remove the ``iface clear'' too). > If this isn't the right place for this, I apologize. Feel free to set > followups appropriately. > > I'm running ppp on a -current system (12/7/2000 vintage) named `moran'. > I'

Re: weird cvs update problem

> Brian Somers <[EMAIL PROTECTED]> wrote: > > > ISTR Christian Weisgerber <[EMAIL PROTECTED]> was having this problem > > too. > > Sorry, you're misremembering. I've never seen anything like this. You're right you know - m

Re: weird cvs update problem

ISTR Christian Weisgerber <[EMAIL PROTECTED]> was having this problem too. I don't know if there was any fix as such > I have a -current system from Dec. 7 on which I'm trying to do > a cvs update in preparation of make world, and am seeing wierd > stuff like this: > > > cvs server: Updati

  1   2   3   >