Re: convert libgmp to a port?

2001-06-16 Thread Peter Wemm
Steve Kargl wrote: > On Sun, Jun 17, 2001 at 05:48:48AM +0300, Giorgos Keramidas wrote: > > > > I dont seem to be able to find some part of the base system that > > actually *does* use libgmp. Being out of date as it is, do you think > > it's proper to remove it from the base system and make it

Re: ps 'D' state - ?

2001-06-16 Thread Valentin Nechayev
Sat, Jun 16, 2001 at 23:21:33, Tor.Egge ([EMAIL PROTECTED]) wrote about "Re: ps 'D' state - ?": > > Are `select' and `nanosleep' disk uninterruptable waits? ;| > No. The ps command gave wrong output. > flag = k->ki_p->ki_flag; > - sflag = k->ki_p->ki_flag; > + sflag = k->ki_p->

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

2001-06-16 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Steve O'Hara-Smith" writes: : I would argue loud and long that changing that *would* be broken. There : is never a guarantee (or even an implication) that a symlink points to a : valid directory entry (think unmounted filesystems, NFS ...). I find it hard : to

Re: tcsh.cat

2001-06-16 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Karsten W. Rohrbach" writes: : > lrwxrwxr-x 1 david wheel 13 Jun 15 06:40 .netscape/lock -> 1.0.0.127:6= : 12 : this is actually more performant than writing ascii text into a file and : checking the file by opening and parsing it. you simply do not have to : fop

Re: PCCARD and -current

2001-06-16 Thread Warner Losh
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes: : I make a short patch to sharing IRQ between a PCIC and a PC Card when using : PCI IRQ routing. : #Does this patch help you? Yes. I've made a larger patch and committed it that mostly works without changes (you still need to add -I, but n

lock order reversal

2001-06-16 Thread Jun Kuriyama
I got message below with WITNESS option. Is this safe to ignore? lock order reversal 1st 0xc044c6a0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:478 2nd 0xca35efec vnode interlock @ ../../kern/vfs_subr.c:1926 -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. <[EMAIL PROTECTED]> /

Re: convert libgmp to a port?

2001-06-16 Thread Steve Kargl
On Sun, Jun 17, 2001 at 05:48:48AM +0300, Giorgos Keramidas wrote: > > I dont seem to be able to find some part of the base system that > actually *does* use libgmp. Being out of date as it is, do you think > it's proper to remove it from the base system and make it a port? > It is a port. Se

convert libgmp to a port?

2001-06-16 Thread Giorgos Keramidas
I was looking at PR/9233 from Dec 1998 the other day, and I saw that the version of libgmp thats included in the base-system seems to be very outdated (version 2.x in our tree, while version 3.x is available at the homepage of libgmp). After discussing this with [EMAIL PROTECTED] about it through

Re: ps 'D' state - ?

2001-06-16 Thread Tor . Egge
> netch@iv:~>ps 218 -l > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > 0 218 1 0 8 0 1120 176 nanslp DWs ??0:02.31 diskcheckd: > > Are `select' and `nanosleep' disk uninterruptable waits? ;| No. The ps command gave wrong output. - Tor Egge

ps 'D' state - ?

2001-06-16 Thread Valentin Nechayev
root@iv:~##ps 4986 PID TT STAT TIME COMMAND 4986 ?? DWs0:01.01 /usr/sbin/sshd root@iv:~##ps 4986 -l UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 4986 1 52 102 0 2292 430 select DWs ??0:01.01 /usr/sbin/ss netch@iv:~>ps 218 -l UID

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

2001-06-16 Thread Matt Dillon
:... :> :>True. It would break phk's malloc debugging features to disable this, :>for example. : :Not only that, but considerning that a symlink can point into a :different filesystem even in normal use, there is no simple way to :validate the valididty of the name. ... or be associated with

Re: The PR db is not for -current problems, right?

2001-06-16 Thread Dima Dorfman
Jens Schweikhardt <[EMAIL PROTECTED]> writes: > Hello fellow PR drivers, > > just before I hit more people over the head that have submitted PRs > against problems on -current: my understanding is that -current users > know what they are doing, especially that they're living on the bleeding > edg

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

2001-06-16 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Jordan Hubbard writes: >From: Matt Dillon <[EMAIL PROTECTED]> >Subject: Re: symlink(2) [Was: Re: tcsh.cat] >Date: Fri, 15 Jun 2001 22:01:47 -0700 (PDT) > >> Symlinks do not have to contain paths. People use them for all sorts >> of things so it would be tot

The PR db is not for -current problems, right?

2001-06-16 Thread Garrett Wollman
< said: > against problems on -current: my understanding is that -current users > know what they are doing, especially that they're living on the bleeding > edge and that they must be subscribed to current@ where they shall > discuss -current-related malfunctions. Right? Wrong. -current users

Re: New Mbuf Allocator (some graphs)

2001-06-16 Thread Bosko Milekic
On Sat, Jun 16, 2001 at 03:11:21AM -0400, Alfred Perlstein wrote: > It would be better if we could allocate/free clusters+mbufs+refcounts > under a single lock. It would simplify the API and save a boatload > of cycles and i-cache by avoiding the mutex operations. > > Not that I object to the c

Re: The PR db is not for -current problems, right?

2001-06-16 Thread Szilveszter Adam
Hello, On Sat, Jun 16, 2001 at 02:51:38PM +0200, Jens Schweikhardt wrote: > Hello fellow PR drivers, > > just before I hit more people over the head that have submitted PRs > against problems on -current: my understanding is that -current users > know what they are doing, especially that they're

The PR db is not for -current problems, right?

2001-06-16 Thread Jens Schweikhardt
Hello fellow PR drivers, just before I hit more people over the head that have submitted PRs against problems on -current: my understanding is that -current users know what they are doing, especially that they're living on the bleeding edge and that they must be subscribed to current@ where they

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

2001-06-16 Thread Steve O'Hara-Smith
On Sat, 16 Jun 2001 22:30:58 +1000 (EST) Bruce Evans <[EMAIL PROTECTED]> wrote: BE> cp always did this (except in the broken case of a broken symlink). POSIX BE> just clarifies it. From the FreeBSD manpage for cp(1): Ignore me, I think I must be going temporarily insane. -- Direc

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

2001-06-16 Thread Bruce Evans
On Sat, 16 Jun 2001, Steve O'Hara-Smith wrote: > On Sat, 16 Jun 2001 17:27:00 +1000 (EST) > Bruce Evans <[EMAIL PROTECTED]> wrote: > > > BE> > This is correct behaviour IMHO - why on earth should it fail. If I > BE> > copy a directory containing symlinks I don't want them do vanish just

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

2001-06-16 Thread Steve O'Hara-Smith
On Sat, 16 Jun 2001 17:27:00 +1000 (EST) Bruce Evans <[EMAIL PROTECTED]> wrote: BE> > This is correct behaviour IMHO - why on earth should it fail. If I BE> > copy a directory containing symlinks I don't want them do vanish just because BE> > the target is unavailable. BE> BE> Because cp copi

support Pentium3 SSE

2001-06-16 Thread NAKAMURA Kazushi
--- Forwarded Message Date: Thu, 14 Jun 2001 04:20:46 +0900 (JST) Message-Id: <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: support Pentium3 SSE From: [EMAIL PROTECTED] (NAKAMURA Kazushi) Hello! Don't lose to Linux2.4.x! I use FreeBSD as graphic workstation. I made a patch for support

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

2001-06-16 Thread Bruce Evans
On Sat, 16 Jun 2001, Steve O'Hara-Smith wrote: > On Sat, 16 Jun 2001 14:34:07 +1000 (EST) > Bruce Evans <[EMAIL PROTECTED]> wrote: > BE> cp is also broken for symlinks to valid pathnames for nonexistent files; > BE> > BE> $ rm -f foo > BE> $ ln -s /nonesuch foo > BE> $ cp foo bar >