Subject: Mail::Internet test subject
This is a test message that was sent by the test suite of
Mail::Internet.
Testing.
one
>From foo
four
>From bar
seven
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Little tip for would-be grub users... I had to play with the compiler
flags quite a bit to get a bootable image. I suggest taking the flags used
to compile the FreeBSD boot loaders and using them.
On Thu, 30 Mar 2000, Vladik wrote:
> Hi, for now I am doing this every time (but I also do not
> r
| Can someone please update the examples in /usr/share/examples/kld?
|
| It's a bit confusing when it doesn't even compile.
i just submitted a patch to get the kld/cdev module to compile
(and work too ;). i tested this on a -stable box.. but it
should still work for -current.
i used the vn dev
On Friday, 31 March 2000 at 0:23:04 -0500, Systems Administrator wrote:
>
> panic: lockmgr: pid -2, exclusive lock holder 5 unlocking
>
> Syncing disks... Timedout SCB handled by another timeout
> Timedout handled by another timeout
>
> That is what I get when doing a 'du -k' on an NFS mount from
panic: lockmgr: pid -2, exclusive lock holder 5 unlocking
Syncing disks... Timedout SCB handled by another timeout
Timedout handled by another timeout
That is what I get when doing a 'du -k' on an NFS mount from a remote
machine.. THe machine I am speaking of is the actual nfs server, i'm using
In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: Async should not be used unless you really like restoring crashed
: filesystems from tape :-). Oh, and perhaps when one is doing an
: initial OS install from CDRom :-). Async itself will not cause a crash,
: but if your mac
Hi, for now I am doing this every time (but I also do not
reboot too often).
GRUB has a curses-like based menu thing where you
can specify what to boot and how. You have to
set the config file during the compilation. And then
compile, and then build the floppy with that or install
on to the MBR.
:>:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote:
:>[...]
:>6 minutes 20 seconds (about 7%).
:
:I'm seeing the same order of improvement still.
:
:--
:Bob Bishop (0118) 977 4017 international code +44 118
:[EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK
:In message <[EMAIL PROTECTED]> "Matthew D. Fuller" writes:
:: The question at task is, is buildworld one of them? I don't think that
:: situation comes up a lot in buildworld, but I'm not exactly an authority
:: on it...
:
:About 6 months ago, softupdates made things about 5% faster than async
>:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote:
>[...]
>6 minutes 20 seconds (about 7%).
I'm seeing the same order of improvement still.
--
Bob Bishop (0118) 977 4017 international code +44 118
[EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK
To
See UPDATING:
2319:
The ISA and PCI compatability shims have been connected to the
options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
include the appropriate option in your kernel config. Dr
In message <[EMAIL PROTECTED]> "Matthew D. Fuller" writes:
: The question at task is, is buildworld one of them? I don't think that
: situation comes up a lot in buildworld, but I'm not exactly an authority
: on it...
About 6 months ago, softupdates made things about 5% faster than async
for mak
On Wed, 29 Mar 2000, Brad Knowles wrote:
> At 4:28 PM -0800 2000/3/28, Matthew Jacob wrote:
> > Yes, we very much has considered this. What's your issue about this, per se?
> Myself, I just need to be able to tell the system that SCSI ID x
> LUN y is actually the same logical device as
You moved tcpdump into the crypto distribution with revision 1.25 of
its Makefile. I am still scratching my head and trying to figure out
why, however, since most people expect tcpdump to be in the bin
distribution where it's always been. Did you have some really good
reason for this which we're
I cvsup'ed and compiled my kernel with the options shown below in my
config file.
device isa0
device atkbdc0 at isa? port IO_KBD
device atkbd0 at atkbdc? irq 1
device psm0at atkbdc? irq 12
device vga0at
On Thu, Mar 30, 2000 at 04:00:43PM -0800, a little birdie told me
that David O'Brien remarked
> On Thu, Mar 30, 2000 at 05:44:53PM -0600, Matthew D. Fuller wrote:
> > Does softupdates provide faster performance than async/noatime?
>
> In general it depends. Softupdates is faster on creating a fi
On Thu, Mar 30, 2000 at 05:44:53PM -0600, Matthew D. Fuller wrote:
> Does softupdates provide faster performance than async/noatime?
In general it depends. Softupdates is faster on creating a file and then
deleteing it before both hit the disk. Softupdates nulifies out the
creation. Async woul
On Wed, Mar 29, 2000 at 10:04:17PM -0800, a little birdie told me
that Matthew Dillon remarked
>
> Ha! I found it. Kirk gets the credit --- softupdates was turned on
> in one of the machine's /usr/obj's and off on the other machine's.
>
> So softupdates improves buildworld times by
NEVER send test messages to any FreeBSD mailing list but
freebsd-test. doing so can result in you being filtered from all the
freebsd mailing lists.
jmb
> From: [EMAIL PROTECTED] (Yellow Dog Communications Inc)
> Sender: [EMAIL PROTECTED]
> X-Loop: FreeBSD.ORG
> Precedence: bulk
>
>
I'm still using old voxware driver on 5.0 current system because it is
only way to get support for my Pro Audio Spectrum card. But there is
one problem on playback. It's 5% too fast and it sounds annoying.
If I play these same mp3 files through pcm/sbc driver everything is
ok. It's also easy t
In message <[EMAIL PROTECTED]> Julian
Elischer writes:
: I did a make world, so THEORETICALLY all teh system libraries should be in
: sync .. right?
Did you also rebuild kde after doing the make world? If not, you
missed one of the entries in UPDATING talking about needing to
recompile all C++
IPSEC is hard-defined into the Makefile...not good, especially for
PicoBSD.
-- snip --
--- /usr/src/usr.sbin/traceroute/Makefile.orig Thu Mar 30 14:16:52 2000
+++ /usr/src/usr.sbin/traceroute/Makefile Thu Mar 30 14:23:28 2000
@@ -5,4 +5,11 @@
BINMODE=4555
+
+.ifndef (NOIPSEC)
CFLAGS+=-DH
Subject: Mail::Internet test subject
This is a test message that was sent by the test suite of
Mail::Internet.
Testing.
one
>From foo
four
>From bar
seven
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Sometime recently (in the last month or so a lot of my kde stuff stopped
> working.
>
> they all complain about:
> jules# kpanel
> /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol
> "_vt$9exception"
> jules#
You should be reading -current; this changed before the 4.0 releas
Sometime recently (in the last month or so a lot of my kde stuff stopped
working.
they all complain about:
jules# kpanel
/usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol
"_vt$9exception"
jules#
Not being a library specialist..
does anyone know offhand who's got out of step wi
> > > >Only the i8254 timecounter hardware currently needs interrupt-disabling,
> > > >but it is hopefully never used on SMP machines.
> > >
> > > Worse. It is used by default on SMP machines which don't sport the
> > > PIIX timecounter.
> >
> > ie. anything using the PIIX3 or older (think 440F
On Thu, Mar 30, 2000 at 10:05:26AM -0800, Mike Smith wrote:
> > >> Just following on from this, one thing that I can see immediately being
> > >> very important to me at least is a spinlock in the timecounter structure.
> > >> Calcru and various other things call microtime(), and we're going to
> >> Just following on from this, one thing that I can see immediately being
> >> very important to me at least is a spinlock in the timecounter structure.
> >> Calcru and various other things call microtime(), and we're going to want
> >> to lock out updates and parallel accesses to the timeco
In message <[EMAIL PROTECTED]> Matthew Dillon writes:
: The general problem with the timecounter is that not only is the hardware
: indeterminant, but the timecounter structure itself is *NOT* MP safe,
: at least not by my read of it.
:
: It also doesn't appear to be interrupt saf
KAMIL MUHD wrote:
> Hi everyone...
>
> I got this error evrytime I try to make world no matter how often I
> cvsup'ed. I don't know what it is, what is Error code 2 anyway? Is my cc
> version is out-of-date? I'm using the GNU gcc-2.95.1. My box is running
on
> 4.0-CURRENT. Any idea? Is it
:In message <[EMAIL PROTECTED]>, Bruce Ev
:ans writes:
:>On Wed, 29 Mar 2000, Mike Smith wrote:
:>
:>> Just following on from this, one thing that I can see immediately being
:>> very important to me at least is a spinlock in the timecounter structure.
:>> Calcru and various other things call m
Oops.. some of us are using i8254 on SMP machines. This motherboard is a
Intel PR440FX.
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-STABLE #5: Mon Mar 27 20:39:24 ES
HI, all.
I've just committed new feature for pccardd, but default pccard
configuration file is still /etc/pccard.conf.sample because I'd like
to see how things go and test them more for about a week. Test
version of /etc/defaults/pccard.conf, /etc/pccard.conf are available at
http://www.freebsd
:At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote:
:
:> So softupdates improves buildworld times by a significant margin.
:
: Uh, I think we've known this for a while now. ;-)
:
: Still, I'm looking forward to finding out what the new timings
:are for SMP builds with the new c
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Do you do this everytime or just to get things started?
If it's everytime, man that's a pain, if it's just to get things
started it's easier than what I did. (but now I get a list of what I
want to boot from the NT bootloader, and I just hit the arrow down to
FreeBSD and go.)
-Charlie
On Wed, M
Well, it looks as if some changes were made to pcm. Specifically, it
looks as if changes were made to address the problem of RealPlayer not
stopping the clip immediately after pressing stop. Before the
changes, RealPlayer (all versions) would keep playing the clip ~ 3
secs after pressing stop.
I just rebuilt by kernel this morning at around 2:00 AM from a fresh
cvsup. Now, the sound driver doesn't perform as well as it used to.
For example, playing audio clips in realplayer sometimes skips or cuts
out when I open up windows, etc. My Mar 28 build of the kernel
doesn't have this behavi
[Charset koi8-r unsupported, filtering to ASCII...]
> Hi,
>
> Does anybody can clarify what is current status of the mmap support in the pcm
> driver? I'm trying to get sound in the quakeforge working, but only managed to
> get famous "dsp_mmap." message in kernel logs instead of sound :(.
not p
Adrian Chadd <[EMAIL PROTECTED]> writes:
> I agree that vnode_if.h needs to be in the sys/ tree for this, but I
> don't think it needs to be checked into CVS. It means any time
> someone modifies vnode_if.src a whole new vnode_if.h could possibly
> be generated, causing unnecessary repobloat.
Rig
Hi,
Does anybody can clarify what is current status of the mmap support in the pcm
driver? I'm trying to get sound in the quakeforge working, but only managed to
get famous "dsp_mmap." message in kernel logs instead of sound :(.
-Maxim
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
In message <[EMAIL PROTECTED]>, Bruce Ev
ans writes:
>On Wed, 29 Mar 2000, Mike Smith wrote:
>
>> Just following on from this, one thing that I can see immediately being
>> very important to me at least is a spinlock in the timecounter structure.
>> Calcru and various other things call microtime
On Thu, Mar 30, 2000, Assar Westerlund wrote:
> I would appreciate some feedback (in the form of commits also works)
> on two small issues (I've also opened PR's on these).
>
> 1. Due to vnode_if.h not getting installed, you need to have kernel
>source (namely vnode_if.src and vnode_if.pl) to
On Wed, 29 Mar 2000, Mike Smith wrote:
> Just following on from this, one thing that I can see immediately being
> very important to me at least is a spinlock in the timecounter structure.
> Calcru and various other things call microtime(), and we're going to want
> to lock out updates and par
I would appreciate some feedback (in the form of commits also works)
on two small issues (I've also opened PR's on these).
1. Due to vnode_if.h not getting installed, you need to have kernel
source (namely vnode_if.src and vnode_if.pl) to build any file
system to be loaded as a kernel modul
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I'm aware of this, the problem is that tz may move in either
> direction.
Why not just ignore the timezone argument? That hasn't been relevant
for a long time. The timezone information is kept in user-space.
>From gettimeofday(2):
Note: time
At 10:04 PM -0800 2000/3/29, Matthew Dillon wrote:
> So softupdates improves buildworld times by a significant margin.
Uh, I think we've known this for a while now. ;-)
Still, I'm looking forward to finding out what the new timings
are for SMP builds with the new code (bo
At 9:45 PM -0500 2000/3/29, Chuck Robey wrote:
>> Difference: 19 minutes, or a 21% improvement. Bob Bishop got 7% with an
>> earlier patch (hopefully his system is no longer locking up and he can
>> repeat his test with the current stuff).
>
> Goddamn. That's significant! Congratulations,
On Mar 20, 11:00am, Archie Cobbs wrote:
} Subject: Re: kern/8324
} Don Lewis writes:
} > This patch (vs the 3.4-STABLE version of tty.c) causes SIGIO to be
} > sent when a regular or pseudo tty becomes writeable.
} >
} >
} > --- tty.c.orig Sun Aug 29 09:26:09 1999
} > +++ tty.c Sat Mar 1
build breakage due to libobjc has been fixed.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
50 matches
Mail list logo
