Mark Murray wrote:
> Terry Lambert writes:
> > Since I have patches to make dlopen work with static binaries, and
> [ snip ]
> > As to inevitable "where are the patches?", please check the -current
> > list archives, you will find at least one set there.
>
Marcel Moolenaar wrote:
> > Ether way, you still need to deal with the linker changes necessary
> > to export the symbol set for all statically linked objects, and to
> > force the inclusion of all archive members when statically linking,
> > if one of the linked libraries is libdl, if you wanted a
David Rhodus wrote:
> Terry Lambert wrote:
> >FWIW, even though I support the idea of dynamically linking
> >everything, the flipping of the switch there followed this
> >same pattern.
First, a disclaimer: this is me speaking for me; I do not speak
for Apple.
> Ter
Robert Watson wrote:
> On Thu, 27 Nov 2003, David Rhodus wrote:
> > what are some of the changes that Apple made to have everything
> > dynamically linked in darwin ? Has anyone done timed runs lately on
> > dynamically vers. static linking on darwin ? Or did they find just
> > cleaning up the dlop
Marcel Moolenaar wrote:
> On Thu, Nov 27, 2003 at 03:41:14AM -0800, Terry Lambert wrote:
> > > If you can get gcc and binutils to add the necessary support, then
> > > we can talk further. Until then it's academic.
> >
> > I think there are political reasons f
Peter Wemm wrote:
> What this shows is that vfork() is 3 times faster than fork() on static
> binaries, and 9 times faster on dynamic binaries. If people are
> worried about a 40% slowdown, then perhaps they'd like to investigate
> a speedup that works no matter whether its static or dynamic? The
the RFFDG flag set.
> I address this to you because you seem to be listed in the
> man page as the author of the man page (although it looks
> like John Dyson has the copyright on the source code?)
John did the code. I did the man page because I wanted to
use it with some test code, but th
idn't have this bug, either, and it was
4.3 based.
I think it's an artifact of the way the struct file is used
on a list to create the system open file table in BSD 4.4 based
systems (I checked BSDI; it has the bug).
-- Terry Lambert
-- Whistle Communications, Inc.
-- te...@whistle.com
Nuno Teixeira wrote:
> I understand the basic concept of the folowing techs: softupdates, disk
> write cache and ata tags.
>
> My question is:
>
> It is safe to use softupdates + write cache + ata tags (IBM disk)?
>
> I read someware that it not safe to use softupdate + write cache
> (wi
Nuno Teixeira wrote:
> sendmail_enable="NONE" doesn't appear in /etc/defaults/rc.conf. Can
> anyone update this file to include "NONE" option?
Do you mean you want it to default to "NONE", or do you mean
that you want the option documented in this file? If the former,
then it's not going to happe
Garrett Wollman wrote:
> `#if __GNUC__' wouldn't help matters; every preprocessor has to read
> and interpret every preprocessor directive (so that `#else' and
> `#endif' can be recognized).
I thought that the other discussion had concluded that:
#if 0
...
#else
Or:
"Daniel C. Sobral" wrote:
> > "device cloning" is really a wrong name for this, and I regret that
> > I every used that term. "On demand device creation" is closer,
> > but it doesn't have any sort of ring to it.
>
> Worst of all, "device cloning" is one of Terry's buzzwords. :-)
Actually, it's
Derek Tattersall wrote:
> I see several instances of this in /var/log/messages after cvsup'ing
> Monday evening and rebuilding world and kernel. I haven't seen any
> messages about this, so I figured I'd ask here.
>
> Message:
> Mar 11 17:33:30 lorne kernel: malloc() of "64" with the following
>
Derek Tattersall wrote:
> Mar 10 20:55:09 lorne kernel: malloc() of "64" with the following non-sleepablelocks
> held:
The only malloc of 64 bytes in this code path should be the
transient template structure malloc (FWIW).
John: did you look at my patch for the locking?
-- Terry
To Unsubscribe
Terry Lambert wrote:
> Derek Tattersall wrote:
> > Mar 10 20:55:09 lorne kernel: malloc() of "64" with the following
> > non-sleepablelocks held:
>
> The only malloc of 64 bytes in this code path should be the
> transient template structure malloc (FWIW).
>
Craig Rodrigues wrote:
> In , I see:
>
> #if __GNUC__
> #warning "No user-serviceable parts inside."
> #endif
>
> Does the use of #warning need to be protected by
> #if __GNUC__ in FreeBSD header files?
Yes. It is a preprocessor directive specific the GCC preprocessor.
This was discussed in gre
Petri Helenius wrote:
> Terry Lambert wrote:
> >Ah. You are receiver livelocked. Try enabling polling; it will
> >help up to the first stall barrier (NETISR not getting a chance
> >to run protocol processing to completion because of interrupt
> >overhead); there a
Petri Helenius wrote:
> > This also has the desirable side effect that stack processing will
> > occur on the same CPU as the interrupt processing occurred. This
> > avoids inter-CPU memory bus arbitration cycles, and ensures that
> > you won't engage in a lot of unnecessary L1 cache busting. Hen
Petri Helenius wrote:
[ ... Citeseer earch terms for professional strength networking ... ]
> These seem quite network-heavy, I was more interested in references
> of SMP stuff and how the coherency is maintained and what is
> the overhead of maintaining the coherency in read/write operations
> an
"Andrew P. Lentvorski, Jr." wrote:
> The dump doesn't seem to be attached. However, I note that the request
> being sent is SETLKW which is a blocking wait until lock is granted. If
> the server thinks the file is already locked, it will hang *and* that is
> the proper behavior.
It is, to ensure
Bakul Shah wrote:
> UFS is the real problem here, not fsck. Its tradeoffs for
> improving normal access latencies may have been right in the
> past but not for modern big disks. The seek time & RPM have
> not improved very much in the past 20 years while disk
> capacity has increased by a factor
Julian Elischer wrote:
> The problem space is
>
> Fsck of UFS/FFS partitions is too slow for 200GB+ filesystems.
>
> The solution space can not contain any answer that includes redefining
> UFS/FFS. Welcome to the real world. :-)
"Use smaller than 200GB+ filesystems".
8-).
-- Terry
To Unsubsc
Bakul Shah wrote:
> > I have been tending UNIX computers of all sorts for many years and
> > there is one bit of wisdom that has yet to fail me:
> >
> > Every now and then, boot in single-user and run full fsck
> > on all filesystems.
> >
> > If this had failed to be productive, I would
Jeff Roberson wrote:
> On Mon, 17 Mar 2003, Brooks Davis wrote:
> > I am still intrested in improvements to fsck since I'm planning to buy
> > several systems with two 1.4TB IDE RAID5 arrays in them soon.
>
> For these types of systems doing a block caching layer with a prefetch
> that understands
Jeff Roberson wrote:
> On Mon, 17 Mar 2003, Terry Lambert wrote:
> > Jeff Roberson wrote:
> > > On Mon, 17 Mar 2003, Brooks Davis wrote:
> > > > I am still intrested in improvements to fsck since I'm planning to buy
> > > > several syste
Bakul Shah wrote:
> > Sorry, but the track-to-track seek latency optimizations you
> > are referring to are turned off, given the newfs defaults, and
> > have been for a very long time.
>
> I was thinking of the basic idea of cylinder groups as good
> for normal load, not so good for fsck when you
Steve Sizemore wrote:
> Thanks for the explanation. If I were a programmer, it would be very
> useful. As it is, it's still interesting. I have no way of judging the
> quality of the code in question, other than the empirical result that
> it works in most cases.
Well, then you are stuck with the
David Schultz wrote:
> This is because floating point
> support on Alpha is broken unless you specifically tell gcc to
> unbreak it by specifying -mieee.
Sounds like the ability to turn "-mieee" off at all, let alone
making it the default, is bad? If so, why is that the way it
is configured?
> I
"Andrew P. Lentvorski, Jr." wrote:
> On Mon, 17 Mar 2003, Terry Lambert wrote:
> Please don't speculate without having reviewed the code. It works because
> I rewrote rpc.lockd so that it does the required housekeeping itself.
> The FreeBSD lockd is the only open
Brad Knowles wrote:
> At 10:49 PM -0800 2003/03/17, Terry Lambert wrote:
> > Yes, I know. I'm aware. He has a lot of data to transfer in
> > from the disk in order to do the reverse lookup, with that much
> > data on the disk.
>
> I'm confused
Steve Sizemore wrote:
> I don't see now it could be "inter-program", since I've gone to great
> lengths to simplify it to a single program failing on a brand new file.
Is the file ever open by a program on the NFS server itself?
If so, this can cause the behaviour you are seeing (if you are
inter
Brad Knowles wrote:
> At 2:42 PM -0800 2003/03/18, Terry Lambert wrote:
> > Make sense now?
>
> No.
>
> However, I am now convinced that I don't understand enough of how
> the filesystem works to even be able to ask the simplest of questions
&g
"Andrew P. Lentvorski, Jr." wrote:
> On Tue, 18 Mar 2003, Steve Sizemore wrote:
>
> > root 399 0.0 0.1 263496 1000 ?? Is9:11AM 0:00.00 /usr/sbin/rpc.sta
> > root 402 0.0 0.1 1512 1156 ?? Ss9:11AM 0:00.00 /usr/sbin/rpc.loc
> > daemon 405 0.0 0.1 1484 117
[EMAIL PROTECTED] wrote:
> Mensaje citado por "M. Warner Losh" <[EMAIL PROTECTED]>:
> | I had a working Linux world on my laptop. I upgraded my kernel and
> | acroread4 stopped working. Now all I get is:
> |
> | Exited with error code: 0x400e0009.
> |
> | after a whole lot of disk access when I t
Alexander Langer wrote:
> I had several panics related to background fsck now. Once I disabled
> background fsck, all went ok.
>
> It began when I pressed the reset buttons on several boots while the
> system was still doing fscks.
Disable write caching on your ATA drive. You should be able to
Alexander Langer wrote:
> Thus spake Terry Lambert ([EMAIL PROTECTED]):
> > Disable write caching on your ATA drive. You should be able to
> > "safely" reset after that.
>
> Good idea, thanks. Nevertheless: I don't think the system should
> panic on backg
Alexander Langer wrote:
> Actually I don't care _where_ the panic happened. If I hadn't manually
> interupted the boot process, this kernel would have booted and paniced
> on that error for the next three years. I could fix that by simply
> doing a manual (background_fsck=NO), so something is "br
The Anarcat wrote:
> > When you killed the power on your system and reset it, you
> > lost the cached data sitting in the ATA disk. This is due
> > to the fact that the ATA disk lied, and claimed that it had
> > committed some writes to stable storage, when in fact it had
> > only copied them to t
Kevin Oberman wrote:
>
> I've been seeing this for a couple of weeks since I updated my laptop to
> CURRENT. I do a normal shutdown (-p or -r) and reboot. The shutdown
> looked normal, with no problems reported with the sync, but, when the
> system is rebooted, the partitions are all shown as poss
Ian Dowse wrote:
> In message <[EMAIL PROTECTED]>, Patric Mrawek writes:
> >On several clients (-DP1, -DP2, 4-stable) mounting a nfs-share
> >(mount_nfs -i -U -3 server:/nfs /mnt) and then copying data from that
> >share to the local disk (find -x -d /mnt | cpio -pdumv /local) results
> >in lost NF
Dan Nelson wrote:
> UDP works just fine on a switched network. On my NFS servers I use an
> 8k rsize/wsize and UDP mounts on everything and have relatively few
> dropped fragments.
I'm not sure Ian's network is as reliable. 8-).
Nevertheless, you really do not want to use UDP for NFS with
a pac
Steve Sizemore wrote:
> On Wed, Mar 26, 2003 at 12:18:11AM -0800, Terry Lambert wrote:
> > In fact, the only legitimate argument I have ever heard for UDP
> > has been "I have an old Linux install that can't talk TCP, as
> > only UDP was implemented at the time
Glenn Johnson wrote:
> I can not login to a box with FreeBSD 5 -current via ssh because I get
> the following error from ypserv:
>
> Mar 28 12:48:15 node1 ypserv[317]: access to master.passwd.byuid denied -- client
> 192.168.1.1:49344 not privileged
>
> Any ideas? I wanted to move to 5.0 on my
David Schultz wrote:
> Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> > o Put a counter in the first superblock; it would be
> > incremented when the BG fsck is started, and reset
> > to zero when it completes. If the counter reaches
> >
Makoto Matsushita wrote:
> It seems that kern.flp for FreeBSD/alpha is flooded (tested on FreeBSD/i386).
> Maybe several kbytes should be removed from the kernel:
[ ... ]
> -r-xr-xr-x 1 root wheel 1223388 Mar 28 00:57 kernel.gz
> -r-xr-xr-x 1 root wheel 200864 Mar 28 00:57 loader
[ ... ]
> An
Jos Backus wrote:
> On Sat, Mar 29, 2003 at 11:02:53AM -0800, Peter Wemm wrote:
> > Mike Barcroft wrote:
> >
> > > >>> stage 4: building everything..
> > > --
> > > ===> share/man/man9
> > > make: don't know how to make bus_Activate_resour
Dane Butler wrote:
> I have been a Linux user for a few years and have been trying out FreeBSD
> 5.0, but there is a problem. I edited the /etc/ttys file as instructed to
> make kdm (and xdm) boot, but as soon as i login, x crashes and reboots, how
> do i get around this?
1) Belongs on questi
Ventsislav Velkov wrote:
>
> Does anybody have an idea ?
option DISABLE_PSE
option DISABLE_PG_G
-- Terry
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Jun Su wrote:
>
[ ... 1:1 kernel threads implementation ... ]
>
> A benchmark would be interested.
This request doesn't make sense.
The primary performance reasoning behind a 1:1 kernel threading
implementation, relative to the user space single kernel entry
scheduler in the libc_r implementati
Stijn Hoop wrote:
> On Mon, Mar 31, 2003 at 10:54:45PM -0500, Jeff Roberson wrote:
> > I have commited libthr. To try this out you'll need to do the following
>
> I know very very little about threads, but I'm interested as to what the
> purpose is of this library. Is there a document available s
Alexander Leidinger wrote:
> On Tue, 01 Apr 2003 23:28:01 -0800
> Terry Lambert <[EMAIL PROTECTED]> wrote:
> > The primary performance reasoning behind a 1:1 kernel threading
> > implementation, relative to the user space single kernel entry
> > scheduler in th
Peter Schultz wrote:
> Hi,
>
> I hope that core will approve removing sendmail from FreeBSD-CURRENT.
I'm pretty sure they will, just as soon as someone provides
patches to make installed base system components like sendmail
into "preinstalled packages", and then steps up and makes some
other MTA
Sheldon Hearn wrote:
> On (2003/04/02 06:05), Terry Lambert wrote:
> > > Do I misremember this? If not, does it not apply to UP systems as well?
> >
> > FWIW: the libc_r reentrancy isn't fixed by a 1:1 model for
> > anything but calls for which there are no non-b
Peter Schultz wrote:
> Why not just have these logged by default instead? Like /var/log/daily,
> and whatnot. Anyone with half a care about this stuff can easily make
> their own modifications, those who don't care will never know the
> difference.
Because syslog is unreliable. See "BUGS" secti
Robert Watson wrote:
> You should notice marked interactivity and UI latency improvements with
> threaded GUI apps over libc_r because GUI threads will generally no longer
> be blocked when disk I/O and blocking I/O occurs. For example,
> applications like Open Office, Netscape, et al, really get
Sheldon Hearn wrote:
> On (2003/04/02 07:38), Terry Lambert wrote:
> > Is the disk I/O really that big of an issue? All writes will
> > be on underlying non-blocking descriptors; I guess you are
> > saying that the interleaved I/O is more important, further
> > down the
Dan Naumov wrote:
> Terry Lambert wrote:
> > Because syslog is unreliable. See "BUGS" section of the man page.
>
> Don't you think that if syslog is unreliable, then it should be fixed ?
Sure. You should definitely fix it; you'll need to figure out
a way to
Jens Rehsack wrote:
> John Baldwin wrote:
> > First, core@ is not the appropriate body for that type of request.
> > Both current@ and arch@ are much better targets. Second, is
> > NO_SENDMAIL + the postfix port inadequate?
>
> The problem I see with that is, that even a minimalistic base install
leafy wrote:
> On Wed, Apr 02, 2003 at 07:38:14AM -0800, Terry Lambert wrote:
> > Has anyone tried compiling X11 to use libthr?
>
> Someone reported success with KDE, so it should serve as a sign of working X11.
Not X11 clients.
The X11 se
Peter Schultz wrote:
> Terry Lambert wrote:
> > If you look over the historical cases of this discussion,
> > you'll see that the answer always comes down to "make the
> > system more modular, so people can replace XXX with YYY and
> > quit bothering us; please
Note: This should have been posted to -questions, not -current.
Evan Dower wrote:
> Sendmail has not been working on my system for some time now. I can't say
> exactly how long, but my guess is that it broke when I upgraded to
> RELENG_5_0. This is how sendmail is invoked (by default) and it's ou
Robert Watson wrote:
> On Wed, 2 Apr 2003, Terry Lambert wrote:
> > Is the disk I/O really that big of an issue? All writes will be on
> > underlying non-blocking descriptors; I guess you are saying that the
> > interleaved I/O is more important, further down the system ca
John Baldwin wrote:
> On 02-Apr-2003 Jens Rehsack wrote:
> > I really think splitting the base in some sub-parts would it make much
> > easier to do NO_SENDMAIL on my own. So I had to remove each not required
> > file separately. That's no good solution.
>
> [stepping back a bit ]
>
> I find an
"Cagle, John (ISS-Houston)" wrote:
> I'm having a problem with -current on a ProLiant BL10e blade server. On
> the blade server, we use a serial console on sio0/COM1. This works
> perfectly with 4.8, but for some reason, the sio driver doesn't see COM1
> at all, and assigns COM2 resources to sio0
Jeff Roberson wrote:
> On Wed, 2 Apr 2003, Terry Lambert wrote:
> > Is the disk I/O really that big of an issue? All writes will
> > be on underlying non-blocking descriptors; I guess you are
> > saying that the interleaved I/O is more important, further
> > down the
Juli Mallett wrote:
> * De: Jeff Roberson <[EMAIL PROTECTED]> [ Data: 2003-04-02 ]
> > On Wed, 2 Apr 2003, Terry Lambert wrote:
> > > Also, any ETA on the per process signal mask handing bug in
> > > libthr? Might not be safe to convert everything up front, in
Jeff Roberson wrote:
> Perhaps I should start quoting posix. I wonder what my legal rights
> are given the copyright. hm..
Educational use.
FWIW, my reading of POSIX.1 says "Per process mask, per threads
masks".
The real question is "What happens when I kill -9/-15 a libthr
process with a lot o
Peter Wemm wrote:
> No. It gives the ability for a thread to block on a syscall without
> stalling the entire system. Just try using mysqld on a system using libc_r
> and heavy disk IO. You can't select() on a read() from disk. Thats the
> ultimate reason to do it. The SMP parallelism is a bon
Peter Wemm wrote:
> Terry Lambert wrote:
>
> > KSE mailing list, starting Monday or so:
> > ] We still haven't heard from jeff with regard to the process
> > ] signal mask removal.
>
> We can add new mailing lists really easily now - it takes about 20-30 se
Jeff Roberson wrote:
> On Wed, 2 Apr 2003, Terry Lambert wrote:
> > Peter Wemm wrote:
> > > No. It gives the ability for a thread to block on a syscall without
> > > stalling the entire system. Just try using mysqld on a system using libc_r
> > > and heavy di
Peter Wemm wrote:
> Terry Lambert wrote:
> > Peter Wemm wrote:
> > > No. It gives the ability for a thread to block on a syscall without
> > > stalling the entire system. Just try using mysqld on a system using libc_r
> > > and heavy disk IO. You can't s
Matthew Dillon wrote:
>Peter Wemm wrote:
> :Terry Lambert wrote:
> :> > No. It gives the ability for a thread to block on a syscall without
> :> > stalling the entire system. Just try using mysqld on a system using libc_r
> :> > and heavy disk IO. You can
Matthew Dillon wrote:
> :How does this break the read() API? The read() API, when called
> :on a NBIO fd is *supposed* to return EAGAIN, if the request cannot
> :be immediately satisfied, but could be satisfied later. Right now,
> :it blocks. This looks like breakage of disk I/O introducing a
>
Kris Kennaway wrote:
> On Fri, Apr 04, 2003 at 11:52:15AM +0200, Stephan M?ck wrote:
> > I want to use imon inode monitor to watch file activity. Is it possible to
> > do that with FreeBSD?
>
> I don't see imon in the ports collection. However there are other
> tools like l0pht-watch and fam in p
Jeff Roberson wrote:
> On Tue, 3 Jun 2003, Terry Lambert wrote:
> > Scott Long wrote:
> > > Bryan Liesner wrote:
> > > It's very hard to imagine Jeff's patches causing a problem at the point
> > > that the PR mentions. Have you confirmed the problem
"David P. Reese Jr." wrote:
> > > A snip of code from sys/dev/pci/pci.c:pci_enable_io_method():
> > >
> > > pci_set_command_bit(dev, child, bit);
> > > command = PCI_READ_CONFIG(dev, child, PCIR_COMMAND, 2);
> > > if (command & bit)
> > > return (0);
> > >
Bryan Liesner wrote:
> On Thu, 5 Jun 2003, Terry Lambert wrote:
> > As I said: I still think there is a lost serialization here
> > that's at the root of the problem. I can't really dedicate
> > the equipment I have here to reproducing the issue at this
> &g
Bryan Liesner wrote:
> A non disclosure agreement is a non disclosure agreement, so no crap
> from me.
>
> I'll give that a try and see if it makes a difference. I don't
> remember off of the top of my head from the previous posts on this
> subject, but does this bug apply to an Athlon XP as well?
Alexander Leidinger wrote:
> is there a way to teach our ACPI implementation about
>
> [EMAIL PROTECTED]:7:4: class=0x068000 card=0x chip=0x30571106 rev=0x40
> hdr=0x00
> vendor = 'VIA Technologies Inc'
> device = 'VT82C686A/B ACPI Power Management Controller'
> class=
Paul Richards wrote:
> On Wed, Jun 04, 2003 at 02:43:20PM +0100, Doug Rabson wrote:
> > On Wed, 2003-06-04 at 14:16, Paul Richards wrote:
> > > How can you add an interface at runtime?
> >
> > By loading a kernel module. If I load e.g. the agp kernel module, I add
> > the agp_if interface to the ke
Alexander Leidinger wrote:
> Terry Lambert <[EMAIL PROTECTED]> wrote:
> > Be aware that if your machine is a "B" (82C686B), then you have
>
> It is.
>
> > the buggy version of the chip; you need to eiter not use the
> > second IDE channel for an
Alexander Leidinger wrote:
> On Thu, 05 Jun 2003 11:33:13 -0400 (EDT)
> John Baldwin <[EMAIL PROTECTED]> wrote:
> > It doesn't really need to know about it. Perhaps acpi should include
> > a dummy driver similar to the 'hostb' driver to "eat" such devices.
>
> Does this mean it should already dis
Alexander Leidinger wrote:
> Isn't this "the famous VIA bug" which every computer magazine reported
> about? I thought we already have a fix in the tree for this:
>
> (2) [EMAIL PROTECTED] # dmesg |grep south
> atapci0: Correcting VIA config for southbridge data corruption bug
It's not the "VIA c
Alexander Kabaev wrote:
> Wilko Bulte <[EMAIL PROTECTED]> wrote:
> > Yes, see for example the GPL_ed floating point emulator.
Aside: I thought the license had been changed on this?
> I and no doubt many others will insist on keeping GPLed drivers out of
> the tree. I have no objections for this d
David Leimbach wrote:
> IANAL but I think the GPL has provisions for binaries that contain code that is
> not necessarily dependant but merely aggregated into one package.
Linking is not "mere agregation". If you can cite the section
of the GPL you are talking about, it would be useful (this is
a
Q wrote:
> I have been burnt by this in the past also. I think that it would be
> useful if you could allow kernel modules to be bound to a particular
> kernel "version/date/whatever", and have external modules refuse to load
> and/or complain if the kernel is upgraded. This should prevent
> unnece
Bryan Liesner wrote:
>
> Is anyone going to look at this before the next release?
> Of course, if more info is needed, I'll send it along. No dump is
> available - it panics during boot.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=52718
This was caused by rev. 1.3 of a commit by Jeff Roberts
David Xu wrote:
> > This was caused by rev. 1.3 of a commit by Jeff Robertson to
> > kern_utmx.c. The problem is that the proc struct is not locked
> > for:
> >
> > FOREACH_THREAD_IN_PROC(td->td_proc, td0)
> >
> > in the lock and unlock.
> >
> > Either lock the proc before and unlock it af
Hiten Pandya wrote:
> My fingers have been itching to do this since the day phk@ planted this
> idea in my brain (re: cdevsw initialisations). Basically, it changes
> the vfsops to use C99 sparse format, just like cdevsw. It removes a lot
> of junk default initialisations, and duplication.
I rea
Hiten Pandya wrote:
> > Consider this going forward: someone adds a new VFSOP to the
> > list of allowable VFSOPs, and the vfs_init() doesn't have any
> > specific code for it.
>
> Considered. Now consider this, would you argue this about the
> sparse cdevsw initialisation in make
Hiten Pandya wrote:
> On Mon, Jun 02, 2003 at 09:28:05AM -0700, Terry Lambert wrote:
> > This is a different thing entirely... you are not adding
> > elements in the cdevsw case.
>
> Er, huh? Did you read Poul's HEADSUP mail for cdevsw sparse
> init?
Martin Blapp wrote:
>
> Hi,
>
> > -frtti is required for dynamic_cast(expr) to work. so if it is
> > broken, then you've got big problems.
>
> Lokks like you are definitly right:
>
> grep dynamic `find ./ -name "*.c*"`
> ./source/ary/cpp/c_class.cxx:ary::cpp::Display * pD = dynamic_cast<
Terry Lambert wrote:
> Martin Blapp wrote:
> > > -frtti is required for dynamic_cast(expr) to work. so if it is
> > > broken, then you've got big problems.
> >
> > Lokks like you are definitly right:
> >
> > grep dynamic `find ./ -name &qu
h -- a one time thing.
> >
> > On Mon, Jun 02, 2003 at 08:17:03AM -0700, Terry Lambert wrote:
> > > Consider this going forward: someone adds a new VFSOP to the
> > > list of allowable VFSOPs, and the vfs_init() doesn't have any
> > > specific code for it.
"Sebastian Yepes [ESN]" wrote:
> I have made some Benchmark on my inspiron 8500 (Intel 82801DB (ICH4) -
> UDMA100)
> and i am geting very Bad results on the 5.1, i have got beter results on 5.0
>
> dmesg
> --
> 5.0R --> http://www.x123.info/src/i8500/dmesg.5.0R
> 5.1B2 --> http://www.x123.info
Scott Long wrote:
> Bryan Liesner wrote:
> It's very hard to imagine Jeff's patches causing a problem at the point
> that the PR mentions. Have you confirmed the problem in a kernel that
> was build in a totally clean environment?
The changed code is not protecting a traversal of a proc
struct me
John Baldwin wrote:
> On 14-May-2003 Terry Lambert wrote:
> > The DISABLE_PG_G, as I said in a previous posting, works around
> > an order of operation problem that needs to clear PG in %CR0
> > while it does it's thing, after which there's no problem with
>
Ian Freislich wrote:
> Alas make buildworld fails for the past few days:
> ===> usr.sbin/config
>
> In file included from config.c:1:
> /usr/include/stdlib.h:102: conflicting types for `restrict'
> /usr/include/stdlib.h:102: previous declaration of `restrict'
> /usr/include/stdlib.h:102: warning:
Ian Freislich wrote:
> Terry Lambert wrote:
> > > > Short term, cd /usr/src/sbin/ipfw; make depend && make all install ought
> > > > to fix it.
> > >
> > > I tried that as well, but the new binary also dumps core, but works
> > > wel
Ian Freislich wrote:
> Andre Guibert de Bruet wrote:
> > Ian,
> >
> > The new ipfw binary will work with an up-to-date kernel. What you need to
> > do is boot this new kernel and only then try out the new ipfw binary.
>
> That doesn't really explain why the new ipfw binary core dumped
> with the n
701 - 800 of 1618 matches
Mail list logo
