Stijn Hoop wrote:
> This is due to the Dell laptops having an invalid ACPI table in the BIOS.
> The only way to avoid these messages is to tell FreeBSD ACPI to override
> the vendor supplied table with a correct one.
Alternately, since Microsoft works just peachy with this
thing, it's somewhat app
Orion Hodson wrote:
> It looks like the pci configuration space state has been lost during
> the suspend and resume. This may be because the bus has removed power
> from the devices attached to it on suspend.
>
> I've been through a cross section of drivers this morning and some
> explicitly save
David Leimbach wrote:
> Interesting. I don't believe it needs to be in the source tree.
>
> I am not saying its bad code or isn't useful... I just don't understand
> what it has to do with FreeBSD. Does any of the other base code need this
> library?
>
> If so it would already be there wouldn't
Antony T Curtis wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> I'm trying to install 5.1-R onto a Compaq Amarda V300 series laptop.
> If I allow ACPI to be loaded, it hangs pretty quick right after trying to
> mount the memory disk.
>
> However, in safe mode, it works until during the
Evan Dower wrote:
> I am highly interested in getting nvidia-driver to work well for FBSD, and
> in particular my own computer. I do not have the expertise to hack on either
> it or the kernel (yet), but I am eager to provide debugging information.
> nvidia-driver frequently crashes my machine, so
Evan Dower wrote:
> >NVIDIA is handling everything to do with the driver. Expect a new
> >release "shortly" *cough*.
>
> I was afraid that might be the case :-(
The only thing you care about is entry and exit through driver
entry points... and maybe interrupts. It would be easy enough
to wrapper
Samy Al Bahra wrote:
> I think Terry is jumping to conclusions on what Evan's problem could be.
> I have this seen this cause application to crash at exit (if using
> OpenGL) but never a crash in kernel-space from the nVidia drivers.
1) It works with libc_r, but not with libthr and not
Samy Al Bahra wrote:
> Daniel Eischen Wrote:
> > No, I don't think Terry is jumping to conclusion. Read
> > the archives of this problem. The Nvidia drivers and OpenGL
> > for FreeBSD won't work with -current and any threading
> > library other than libc_r.
>
> I didn't deal with any users havin
Bruno Afonso wrote:
> Holger Kipp wrote:
> > Isn't someone working on integrating ALTQ and pf - similar to what
> > has been done for OpenBSD?
>
> here you go:
>
> http://pf4freebsd.love2party.net/index.html
>
> I'd love freebsd to have altq and pf or ipf integration on base system..
If it can
John Hay wrote:
> On a 5.1-RELEASE machine I have been able to cause a panic like this:
> panic: kmem_malloc(4096): kmem_map too small: 28610560 total allocated
Manually tune your system. This panic results from the fact
that zone allocations with fixed limits don't really do the
right thing any
Bernd Walter wrote:
> Note: we are strictly USB1.x at this time.
There was a recent PCI attach patch that I thought fixed this?
I know it hasn't been integrated yet (for God knows why), but
it seemed to fix the problems.
-- Terry
___
[EMAIL PROTECTED]
Kris Kennaway wrote:
> There's a bogus implementation of gethostbyaddr_r() in
> lib/libc/net/gethostnamadr.c that was committed 6 years and nine
> months ago:
[...]
> What's the deal here? Despite the fact that this is not prototyped in
> a header, some ports are detecting this, and -- one assumes
John-Mark Gurney wrote:
> Terry Lambert wrote this message on Sun, Jun 15, 2003 at 19:40 -0700:
> > Bernd Walter wrote:
> > > Note: we are strictly USB1.x at this time.
> >
> > There was a recent PCI attach patch that I thought fixed this?
>
> Are you
Don Lewis wrote:
> Actually, something seems broken. I modified my little test program to
> actually read the data, which works just fine, but select() still blocks
> when the writer closes the fifo, so there doesn't seem to be a way to
> detect the EOF.
I think this should be covered under the "
Wiktor Niesiobedzki wrote:
> On Tue, Jun 17, 2003 at 03:51:32PM -0400, Jeff Roberson wrote:
> > I am still not able to reproduce this. Can you update your sources? I
> > commited some code just now that removed an external dependency from
> > sched_nice(). This should make it more robust.
> Got
[ ... BG fsck ... ]
> > I haven't got softupdates enabled, but I didn't want to enable it,
> > because I've heard that it isn't 100% reliable and I didn't want to lose
> > data
>
> Theer have been no problems with softupdates in regard to data
> integrity in either 5.0 or 5.1 release. I do re
I love English!
Maxime Henrion wrote:
> Giant is the big lock that protects the whole kernel that everyone is
> trying to get rid of :-).
We should just delete Giant. Then we can get rid of the whole kernel
that everyone is trying to get rid of, since Ginat will no longer be
protecting it... 8-)
[EMAIL PROTECTED] wrote:
> I removed /usr/include/sys/bitypes.h, and now it works! thanks for the tip.
> (hm, are there other .h files that are not used anymore?)
There are other headers which are no longer installed during the
build process. Whether they are still used or not is between
you and
Hiten Pandya wrote:
> On Thu, Jun 19, 2003 at 03:17:03PM -0700, John-Mark Gurney wrote:
> > I am running FreeBSD 5.1-R on a sparc64 machine, and am getting warnings
> > about mallocing data w/ a lock aquired.
> >
> > dmesg output:
> > malloc() of "64" with the following non-sleepablelocks held:
> >
David Syphers wrote:
> I recently forgot my root password, rebooted single-user and changed it,
> and immediately afterwards the computer denied the existence of any
> non-root users (home directories still there for those that had them,
> they still have login shells, etc.). This was the only chan
Mike Silbersack wrote:
> I could probably grep for this, but what's the best way to get a hold of
> the # of pages (or MB of ram) that max KVA is set to? I'm adding another
> autosize option, and I want to base it on min (KVA, ram) so that it
> doesn't balloon on boxes where ram >> KVA.
I posted
M-Trade wrote:
> Has anyone had any success installing 5.1 release on a 486
> w/ 8MB RAM? I can't install.
>
> avail memory = (245760) 0 MB
>
> Is this expected behavior?
Until you build a skinnier kernel, you only have 240K of memory
in which to run processes.
Normally, the install process us
John-Mark Gurney wrote:
> So, now the question is, do we fix xargs to deal with unexpected
> children? Or fix the shells in question? (tcsh and zsh seem to suffer
> this problem)
>
> To me, fixing xargs is correct since it prevents another possible
> future abusers of this "feature".
Fixing the
"Simon L. Nielsen" wrote:
> On 2003.06.25 12:10:42 +0200, Michael Nottebrock wrote:
> > FWIW, the last FreeBSD release I managed to install on an 8mb machine from
> > CD-ROM+bootfloppies was 4.1.1.
>
> Can anybody else confirm this ? It seems like the documetation need to
> be updated to state th
"Cagle, John (ISS-Houston)" wrote:
> Terry Lambert [mailto:[EMAIL PROTECTED]
> > Mike Silbersack wrote:
> > > I could probably grep for this, but what's the best way to get a hold
> > > of the # of pages (or MB of ram) that max KVA is set to? I'm a
"M. Warner Losh" wrote:
> In message: <[EMAIL PROTECTED]>
> M-Trade <[EMAIL PROTECTED]> writes:
> : Has anyone had any success installing 5.1 release on a 486
> : w/ 8MB RAM? I can't install.
> :
> : avail memory = (245760) 0 MB
> :
> : Is this expected behavior?
>
> Yes. The generic
John-Mark Gurney wrote:
> Tim Kientzle wrote this message on Wed, Jun 25, 2003 at 09:51 -0700:
> > Why do exec-ed processes inherit the children of the former
> > process, anyway? That doesn't entirely sound right to me.
> > Is that behavior mandated by some standard? If not, this
> > could argua
Mike Silbersack wrote:
> I found the thread in question, but I didn't see a patch.
ARGH. There was a simultaneous off-list discussion; here is
the scrubbed part of what I sent; it's a patch, but it's not a
diff; sorry for the confusion.
-- Terry
--
David Schultz wrote:
> On Tue, Jun 24, 2003, Jay Kuri wrote:
> > Does changing this affect memory available to user programs if it's unused
> > by the kernel?
>
> No, KVA_PAGES affects the memory available to user programs. (You
> have a 4 GB address space on i386 to split between user programs
>
John Birrell wrote:
> On Wed, Jun 25, 2003 at 10:15:19PM -0700, Terry Lambert wrote:
> > There *are* other ways to install than booting a CDROM; they are
> > just more labor intensive, and require FreeBSD running on a more
> > poswerful machine to set up the install
Julian Elischer wrote:
> One thing to do would be to do the buildworld in a 4.x jail/chroot
> on a 5.x system..
FWIW: The only way I could get this to work reliably required
that I copy in certain files from the host environment, which
included the kernel, and anything that linked against libkvm.
Soeren Schmidt wrote:
> I do have problems with the wording you use in the comments
> in that patch mentioned below, I will even say that I will remove
> that as soon as it appears *and* shoot the committer so it doesn't
> happen again to use your choice of wording..
While you are making those cha
Glenn Johnson wrote:
> Thanks. I had read the smp manual page. I know _how_ to enable HTT; I
> was wondering whether I _should_ enable it. It seems the answer is that
> it is not beneficial in its current state because the scheduler does not
> yet differentiate between physical and logical proce
Eivind Hestnes wrote:
> Is XFS ported to FreeBSD? If not, what's the status?
[ Let's assume this isn't the usual XFS troll. Here is all the
historical information about all previous discussions. If you
want to discuss this yet again because you are unwilling to
take this at face value, and
"M. Warner Losh" wrote:
> In message: <[EMAIL PROTECTED]>
> Nate Lawson <[EMAIL PROTECTED]> writes:
> : On Wed, 2 Jul 2003, Florian Smeets wrote:
> : > I set hw.acpi.ec.burst_mode=0 in loader.conf but when i was trying to
> : > chek if it was set to 0 with sysctl hw.acpi.ec.burst_mode i
Marcin Dalecki wrote:
> Thomas Dickey wrote:
> > On Mon, Jul 07, 2003 at 02:23:25PM +0200, Marcin Dalecki wrote:
> >>You know that file system name lookup is one of the most
> >>expensive system calls under UNIX?
> >
> > stating the obvious is a clumsy rhetorical ploy (asking for agreement without
Andy Farkas wrote:
> On 7 Jul 2003, Lanny Baron wrote:
> > A load of 3 is pretty high. I think you have more going on.
>
> Not for my box. Its only running at 75% cpu power. Its got four
> processors, so a load of 4 is when its running flat out. And I also said
> that the box is idle other than th
Dan Nelson wrote:
> In the last episode (Jul 08), Andy Farkas said:
> > If setiathome is making lots of syscalls, then running the 3 instanses
> > should already show a problem, no?
>
> Not if it's ssh that's holding Giant for longer than it should. The
> setiathome processes may be calling some
John Baldwin wrote:
> This is why HLT is not enabled in SMP by default (or at least was,
> it may be turned on now). Given that the clock interrupts are
> effectively broadcast to all CPU's one way or another for all
> arch's (that I know of), you will never halt more than the interval
> between c
Julian Elischer wrote:
> It looks tp me that if we make a thread runnable
> and there is a processor in the idle loop, the idle processor should be
> kicked in some way to make it go get the newly runnable thread.
>
> If the processors are halting in the idle loop however, it may take
> quite a wh
Andy Farkas wrote:
> On Tue, 8 Jul 2003, Julian Elischer wrote:
> > It looks tp me that if we make a thread runnable
> > and there is a processor in the idle loop, the idle processor should be
> > kicked in some way to make it go get the newly runnable thread.
>
> Is this what's happenning to me a
Kevin Oberman wrote:
> > PS : is this an indication of bug in the p-III or in the chipset ?
> > (ISTR these options could be used to get around unnamed errata of
> > the p-IV)
>
> Terry has never been specific (due to non-disclosure), but adding
> options DISABLE_PSE to the kernel of my P4 system
Steve Kargl wrote:
> > PS : is this an indication of bug in the p-III or in the chipset ?
> > (ISTR these options could be used to get around unnamed errata of the p-IV)
>
> You'll need to search the mailing list archive for vague ramblings
> by Terry Lambert about
John Baldwin wrote:
> On 09-Jul-2003 Terry Lambert wrote:
> > I thought that there was either a SPARC or Alpha box where Poul
> > had to mess with the divider because they were delivered round
> > robin, instead?
>
> No. The only anomaly I know of is that on Alpha 21
Wilko Bulte wrote:
> On Wed, Jul 09, 2003 at 10:14:47AM -0500, Thomas T. Veldhouse wrote:
>
> I can confirm my 2.4G P4 does have HTT:
This is unfortunately not definitive for CPUs other than your
own. The "Intel Extends..." announcement that was quoted really
means two things:
o Parts wit
Kenneth Culver wrote:
> > Just as an experiment, try setting "net.inet.tcp.newreno" to 0 using
> > sysctl(8). It might help; it might not. Please let us know.
>
> It didn't help. I also tried setting several other sysctl OID's in
> net.inet.tcp, but nothing helped. I'm totally out of ideas for w
Jens Rehsack wrote:
> How can I found out whether a board supports HTT or not?
> I haven't seen it in none description I checked. Are some
> chipsets (865, 875) always ready or is the bios programmer
> the guy who must activate this feature?
One non-obvious-at-first-glance thing that springs to mi
Luigi Rizzo wrote:
> in several places in ipfw2.c i have to move pointers across
> structures of variable length (lists of ipfw2 instructions
> returned by the getsockopt()), and i use the following type of code:
>
> void *next;
> foo *p;
> next = (void *)p + len;
>
Kenneth Culver wrote:
> > You should visit the FreeBSD -performance list archives for a
> > (fairly) recent discussion on network performance (I believe
> > between a couple of us, we were able to come up with tuning
> > parameters that improved someone's file transfer performance by
> > about a fa
Luigi Rizzo wrote:
> > I don't understand the second one. The first one blows up because
> > you aren't parenthesizing, e.g.:
> >
> > next = (void *)(p + len);
> >
> > The compiler is complaining because it doesn't know sizeof(*((void *)0))
>
> ok, it actually evaluates to 1 and i thought i
David Leimbach wrote:
> I always feel better when I convert void * to char * but that's probably
> because C++ doesn't allow pointer arithmetic on void *'s. The argument
> being that you don't know the size of what's being pointed to with a void *
> and therefore can't know how far to seek the th
Marcel Moolenaar wrote:
> On Thu, Jul 10, 2003 at 03:03:41PM -0700, Julian Elischer wrote:
> > it comes I think from the fact that some hardware treats things as
> > bitmaps. (?)
>
> I have to guess that a bitmap is a natural way to represent sets
> when the sets aren't large and that this is why
Marcel Moolenaar wrote:
> I'd say: upgrade gdb(1) and add support for ia64 and amd64, as well
> as make sure we fix any known showstopper bugs we know of.
[ ... ]
> Thoughts?
Will remote source level kernel debugging continue to work?
-- Terry
___
[EMAI
Tim Kientzle wrote:
> Andrey Elperin wrote:
> > Tell me, please, is it a possible to "make release" of CURRENT on 4.7 box
> > at present ?
> >
> > I see that make release stops with a such messages for a couple of days :
> > ===> include
> > cd /usr/src/include; /usr/obj/usr/src/make.i386/make b
David Leimbach wrote:
> This is a good policy in general, however, one could easily argue that
> what is trying to be determined with signedness and such being
> less-than-compared
> to 0 isn't really a big deal and possibly the only way to implement this
> numeric_limits::digits thing without any
Guenter Doerrhoefer wrote:
> According to the release note the Belkin F5U103 should be supported. I
> could not get it to operate, the device is recognized but cannot be
> configured. Anyone got the Belkin to cooperate with 5.2-current?
>
> We tried several other adapters (not mentioned in the rel
Tom Parquette wrote:
>
> Hi. I'm not sure if this belongs somewhere else but I'm starting here
> since these are 5.x systems.
> Please CC me on any replies. I subscribe to the digest format (makes
> replying difficult.) TIA.
>
> I have DDNS running between my house server and what will become
Thorsten Greiner wrote:
> As far as I understand it, this variable is set by the session management
> of the respective desktop (KDE in your case, GNOME in mine). Maybe you
> can workaround the problem by using a small shell script which unsets
> SESSION_MANAGER and than calls gvim?
Probably it wo
Mark Murray wrote:
> Mikhail Teterin writes:
> > Every once in a while, a vi-session dies on me with:
> >
> > input: Resource temporarily unavailable
> >
> > What does it mean, why does it happen, and how can I prevent it?
>
> I'm seeing this on current. I use bash, and the machine is not
>
David Leimbach wrote:
> >Gcc needs a #pragma to disable specific warnings as a one-shot.
> >
> >This was discussed in detail on the GCC mailing list.
>
> True... but I don't think I was talking about a one-shot disabling
> of the message.
>
> I was thinking more about how a compliant C++ compiler
S³awek ¯ak wrote:
> I guess there is something wrong with exporting iso9660 CD's over NFS. I've added
>
> /cdrom -ro -mapall=root
>
> to /etc/exports, restarted mountd and after mounting the CD on Solaris 8. All the
> files are 0-sized, dates are set back to the epoch and directories are seen a
S³awek ¯ak wrote:
> Now I guess it's Solaris specific. If you want some more details, let me know.
Wish you'd said "Solaris" first; but of course, we probably would
have told you "Go ask on the Solaris-current mailing list at
Solaris.org -- oops, sorry, Sun charges for support" 8-).
As someone el
Alexander Kabaev wrote:
> On Thu, 17 Jul 2003 14:02:20 -0700
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
> >
> > Sorry, I missed the patch in your email. I'm not certain about your
> > approach...can someone who understands the issues comment on it?
>
> I'd rather see all varargs.h consumers be co
Harald Schmalzbauer wrote:
> Please forget that. It was because for convinience reasons I had turned the
> 80-pin ATA cables upside down. So the black was at the controller and the
> blue at the drive.
> I can't imagine that this makes any technical difference (as long as no
> slave drive is connec
Doug Barton wrote:
> On Thu, 6 Jun 2002, Giorgos Keramidas wrote:
> > Here's a patch that removes all trails of Perl usage from mergemaster.
>
> Your work looks good, but I wish you'd asked before embarking on it. My
> current plan is actually to import netbsd's stat(1), which will solve this
> p
Martin Blapp wrote:
> What is the status here ? In my CURRENT system, these compat
> libs are still the old ones :-(
>
> I've now updated the libs manually to be able to run OO
> on CURRENT. And yes - it works. Yes :-))
>
> -r--r--r-- 1 root wheel 725012 Jun 7 02:36 libc.so.4
> -r--r--r-- 1
Dan Nelson wrote:
> Tar 1.13 is 3 years old, and has many bugs (incremental backups are
> unusable, for example).
On the flip side, I hear it respects the umask when running as root...
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
Martin Blapp wrote:
> > Why is it linked against a hacked 4.x libc, instead of an
> > unhacked 5.x libc?
>
> Because gcc31 and libstd++ and stlport are unusable for OpenOffice
> to build. Exceptions are broken. Optimazations are broken.
I think that if this is going to result in MFC's of things
Martin Blapp wrote:
> > I also think that it may mean another major version number change,
> > since there's aren't real minor version numbers any more. 8-(.
>
> That surly not necessary. We only have major version number change
> if we change from Releng Majors 3->4, 4->5. This is just compat
>
Kris Kennaway wrote:
> On Fri, Jun 07, 2002 at 06:05:06PM +0200, Martin Blapp wrote:
> > This is very interesting ...
> >
> > diff -ruN /usr/ports/lang/gcc31/work/gcc-20020527/libstdc++-v3
> > /usr/src/contrib/libstdc++ | more
> >
> > I guess this issues has been fixed in the ports version, and is
Brooks Davis wrote:
> In addition to the dump problem I've reported, I'm also seeing issues
> with df output. The following is obviously wrong:
>
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/ad0s2a254063 -246047 479785 -105%/
It's probably just really anxious
Doug Barton wrote:
> Anton Berezin wrote:
> > On Sun, Jun 09, 2002 at 02:39:45AM -0700, Doug Barton wrote:
> > > Per discussion with various folks, including Mark, I've moved the
> > > NO_PERL knob over to NO_PERL_WRAPPER, and documented same. Given that
> > > this is a fundamentally different thi
Maksim Yevmenkin wrote:
> The problem is that as soon as i open isochronous pipe and
> start incoming isochronous transfer, the isochronous callback
> gets called over and over again. Both isoc. pipe and isoc.
> transfer have USBD_NO_SHORT_XFER flag set. I also set
> configuration #5 for interface
Stanislav Grozev wrote:
> actually that is a problem with the autoconf version used by postgresql.
> the new gcc 3.1 gives out a warning if one of the system include directories
> is also given as a -I argument (in this case -I/usr/include).
> the autoconf, when compiling the test program, mistake
David O'Brien wrote:
> *sigh*, why not a *real* fix?
Feel free to submit this to the Postgres project... they may
even incorporate it.
> You'll note that they bother with this kind of check for other headers,
> but for some reason didn't consider it for openssl headers.
Mostly the reason that
"Vladimir B. Grebenschikov" wrote:
> As far as I understand _key_ word is "open", each new instance appears
> on open(), but fork() and dup() only do regular work. dup'ed or fork'ed
> descriptors will be same from driver's point of view, but each new
> open() will create new instance.
No.
The pr
Shizuka Kudo wrote:
>
> --- David O'Brien <[EMAIL PROTECTED]> wrote:
> >
> > *sigh*, why not a *real* fix?
[ ... ]
> Which version of postgresql that you are using? I have
> cvsupped the postgresql7 ports and didn't find what
> you referred here. However, I didn't manage to patch
> "configure"
Shizuka Kudo wrote:
> I don't think autoconf was called in postgresql7 port,
> and patching configure is necessary.
It's derived data, and the patches will likely not remain valid
after the next release/upgrade. That basically means that the
way to correct your complaint about autoconf not being
Harti Brandt wrote:
> In MHO this idea is based on a fundamental misunderstanding of what a
> device is under unix. If you need such a behaviour you should put another
> abstraction on top of you devices (as the filesystem is put on top of
> disks and sockets on top of network devices), that handl
Harti Brandt wrote:
> I was talking about real devices, not pseudo devices that you can get out
> of thin air. Device driver for real devices should be just what they are:
> device drivers. If you take a disk driver, then there is no code there
> that tries to present multiple contexts to multiple
Harti Brandt wrote:
> TL>For a sound device, it would be nice if multiple instances to the
> TL>devices were mux'ed. I've had cases where the program I was using
> TL>was using a smaller number that the total available channels, and
> TL>it would have been nice if the next open instance got the r
Juli Mallett wrote:
> > |-omniNames---omniNames---3*[omniNames]
>
> That seems frighteningly useless to me though. Seems a bit like a number of
> utilities I've seen from the Linux camp which take useful functionality and
> mask it behind something that looks good. What exactly can you get
Juli Mallett wrote:
> > Piping commands through other commands seems icky?
>
> Relying on reasonable output from ps(1) seems icky when you can extract the
> data yourself and not have to worry about formatting getting in the way of
> processing data properly.
This is just wrong on so many levels
Maksim Yevmenkin wrote:
> I'm sorry people :) I should have been more specific. Here is
> what i meant. I'm working on Bluetooth stack for FreeBSD. Everything
> is implemented in Netgraph. The real device driver nodes are connected
> to HCI layer. You can talk to any Bluetooth device via HCI layer
Maksim Yevmenkin wrote:
> Well, HCI _IS_NOT_ a network protocol like TCP or even UDP. It is a
> predefined set of control messages and events that user might send
> to the device. L2CAP which is runs over HCI _IS_ a network protocol
> and it is implemented in AF_BLUETOOTH protocol family. So appli
"Paul S. Puth" wrote:
> I am looking for a tool that will email to the user if his/her account
> (more specifically email box) is approaching quota limit. I've searched
> everywhere for such a tool but to no avail.
>
> On Linux, there is a tool called "warnquota" that fits my need but I am
> runn
Harti Brandt wrote:
> You just don't know what you are talking about. This is exactly the
> difference between the current Linux sound (1 device) and FreeBSD (1
> device/channel). In FreeBSD I can use N channels with different audio
> formats and speeds, in Linux I'm stuck to using all the channel
David Taylor wrote:
> > FWIW: It's kind of a dumb idea to send email warning about a
> > condition which is caused by having too much email. We did
> > this on the InterJet, and it was actually a pretty dumb thing
> > to do; you end up with a recursive problem that's unsolvable
> > -- you basical
Terry Lambert wrote:
> For this to work, you would have to serialize access to maildrops
> by receiver SMTPs (this is an intractable problem), AND you would
> need to reject mail sent without the "SIZE" extension, or mail
> whose actual size exceeded that specified by the &
Alex Zepeda wrote:
> On Thu, Jun 13, 2002 at 12:26:05PM +1000, Bruce Evans wrote:
> > rtld still uses asms with the old, broken/fragile "0" constraint. This
> > constraint is especially broken/fragile if things are pessimized by
> > compiling without optimizations.
>
> D'oh!
>
> Is there any ch
Juli Mallett wrote:
> Errr, it was with 0 level optimisation that is the problem, not a real
> level. Read carefully what bde said, and look at hte warnings and how
> GCC deals with the code in question.
>
> Also, your example is very wrong, read make(1)'s section on dealing with
> variables.
Julian Elischer wrote:
> So the question is: what information can PS show
> for a KSE threaded process?
The same thing "ps" shows for a threaded process with user space
threads today.
Why confuse every "ps"-using shell script or perl script ever
written?
> so for a process you can show:
>
Mike Makonnen wrote:
> Danny Braniss <[EMAIL PROTECTED]> wrote:
> > in amd,
> > # REQUIRE: rpcbind mountall ypbind nfsclient
> > **
> > since i don't use yp, how can i override this?
> >
> > or in other words, can REQUIRE be configurable too?
>
> The RE
Bruce Evans wrote:
> This is a bug in bsd.kern.mk. -ffreestanding never belonged there, since
> it is also needed for modules and perhaps for boot programs and libstand.
> Module makefiles still include , but Makefiles for boot
> programs have regressed.
>
> Your x86 box must be out of date. x8
David O'Brien wrote:
> On Fri, Jun 14, 2002 at 03:30:19PM -0700, Terry Lambert wrote:
> > I.e. if "REQUIRE" describes soft dependency ordering, what
> > describes hard dependency ordering?
>
> Why the need to distingish?
Otherwise circular dependencies.
--
Maxime Henrion wrote:
> Terry Lambert wrote:
> > What exactly does this do, besides implying "-fno-builtin"?
> >
> > The documentation says "and implies main has no special requirements"...
> >
> > Neither the kernel nor modules have a &quo
"M. Warner Losh" wrote:
> In message: <[EMAIL PROTECTED]>
> "David W. Chapman Jr." <[EMAIL PROTECTED]> writes:
> : pcm0: irq 5 at device 14.0 on pci0
> : pcm0: unable to map register space
> : device_probe_and_attach: pcm0 attach returned 6
>
> FreeBSD should, but isn't, assign resou
Mike Makonnen wrote:
> On Sat, 15 Jun 2002 12:49:52 -0700
> Terry Lambert <[EMAIL PROTECTED]> wrote:
> > David O'Brien wrote:
> > > On Fri, Jun 14, 2002 at 03:30:19PM -0700, Terry Lambert wrote:
> > > > I.e. if "REQUIRE" describes soft depen
"M. Warner Losh" wrote:
> : > FreeBSD should, but isn't, assign resources to PCI devices. In the
> : > past, the BIOS has done this, but MS has migrated this functionality
> : > into the OS. That's why you see a lot of these sorts of failures with
> : > various kludges in the FreeBSD tree. That
"David W. Chapman Jr." wrote:
> > That was kind of my point to David: blaming MS doesn't make FreeBSD
> > work. At some point, you have to accept that the problem is yours,
> > rather than being caused by some outside agency.
>
> I'm not sure I understand if you're referring to me. I haven't
>
801 - 900 of 1618 matches
Mail list logo
