ge to be combined into a single write, with a
good likely hood of a speed increase.
Thus, MTRR is GOOD.
- Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:
# Suck in the configuration variables.
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
fi
if [ -r /etc/rc.conf ]; then
. /etc/rc.conf
fi
-jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
I didn't know here to send this, but I thought that other people trying
to keep current might have had this problem before:
When I run cvsup with the default cvsup file from
/usr/share/examples/cvsup/cvs-supfile (after putting in the correct cvsup
server address) it crashes:
bash-2.03# cvsup cvs
I searched the archives, found a few similair problems, and possible
resolutions, but none have worked for me.
In windows, it is shown as an Alps Glidepoint on irq12, however fbsd
refuses to find it.
The device.hints file shows the correct info. I ran acpidump, but was not
quite sure what to loo
ep: compile failed
*** Error code 1
Stop in /usr/src/gnu/usr.bin/cc/cc1plus.
*** Error code 1
Stop in /usr/src/gnu/usr.bin/cc.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
regards,
Jason
--
=
I have had problems finishing buildworld and the problem is the same
each time the build fails. It has failed 4 times at
file:///usr/src/gnu/usr.bin/cvs/doc/. I have cvsuped 3 times in 2
days. I am running 5.1. Any info you might have would be helpful.
Thanks,
Jason
matti k wrote:
On Sun, 09 Nov 2003 00:36:57 -0500
Jason <[EMAIL PROTECTED]> wrote:
I have had problems finishing buildworld and the problem is the same
each time the build fails. It has failed 4 times at
file:///usr/src/gnu/usr.bin/cvs/doc/. I have cvsuped 3 times in 2
days. I am r
Doug White wrote:
On Sun, 9 Nov 2003, Jason wrote:
I have had problems finishing buildworld and the problem is the same
each time the build fails. It has failed 4 times at
file:///usr/src/gnu/usr.bin/cvs/doc/. I have cvsuped 3 times in 2
days. I am running 5.1. Any info you might have
pe type of new feature is now supported in freebsd? In
win98 it stays FF and I know win98 does not support all of the board
functions because it is an old os and the nvidia drivers did not help to
support all the features ether.
Thanks,
Jason
___
[E
ut it seems it might just make the os unstable
for me.
Thanks,
Jason
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
. But it always stops at this point, so it must be something
specific to the cvs/doc files. I have emailed the maintiner listed in
the make files and have gotten no response. Anyone else have this
experience?
Thanks,
Jason
===> gnu/usr.bin/cvs/doc
makeinfo --no-split -I /usr/src/gnu/usr.bin/
* Process 512 using kernel context 0
Now are there any suggestions on what is causing this or how to fix
this? I have a nforce2 epox 8rda, freebsd 5.1, and cvsuped and did a
buildworld today.
Thanks,
Jason
___
[EMAIL PROTECTED] mailing list
http
John Baldwin wrote:
On 11-Nov-2003 Jason wrote:
I just wanted to let someone know that my buildworld fails at
/usr/src/sys/boot/i386/boot2/boot2.c at line 362. I get an undefined
error for RB_BOOTINFO, by adding #define RB_BOOTINFO 0x1f it worked.
Also it failed at sendmail.fc or something, I
John Baldwin wrote:
On 11-Nov-2003 Jason wrote:
I just wanted to let someone know that my buildworld fails at
/usr/src/sys/boot/i386/boot2/boot2.c at line 362. I get an undefined
error for RB_BOOTINFO, by adding #define RB_BOOTINFO 0x1f it worked.
Also it failed at sendmail.fc or something, I
Eric Anholt wrote:
On Mon, 2003-11-10 at 21:10, Jason wrote:
Here is the error:
drm0: port 0xa000-0xa0ff mem
0xec02-0xec02,0xe000-0xe7ff irq 10 at device 0.0 on pci2
info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
error: [drm:radeon_cp_init] *ERROR* radeon_cp_init
pdate and have problems.
Thanks,
Jason
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Steve Kargl wrote:
On Mon, Nov 17, 2003 at 11:12:20PM -0500, Jason wrote:
I cvsuped an hour or so ago, now when I finish make buildworld I get:
===> usr.sbin/boot0cfg
cc -O -pipe -march=athlon-xp -Wsystem-headers -Werror -Wall
-Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/boot0
Dag-Erling Smørgrav wrote:
Jason <[EMAIL PROTECTED]> writes:
I cvsuped an hour or so ago, now when I finish make buildworld I get:
===> usr.sbin/boot0cfg
cc -O -pipe -march=athlon-xp -Wsystem-headers -Werror -Wall
-Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/boot0cfg/boot
Aleksander Rozman - Andy wrote:
Hi !
I have been running named for few years now, and I never had any
problem with it. Few days ago I upgraded system to 5.1 (Release) and
named has gone beserk. It shows errors in named.root file. Error go
something like this:
check_hints: no A record for addre
This is the last snip of output. What I did was get the patch from
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/57198 to fix the
problem I have with the new ata driver not recongizing some deprecated
ioctl. Anyone have any suggestions? I am running current.
Thanks,
Jason
cc
On Fri, Jun 04, 2010 at 05:00:25PM +0200, Dimitry Andric thus spake:
On 2010-06-04 01:24, David Rhodus wrote:
Anyone have a SUJ patch set for 8.x ?
http://www.andric.com/freebsd/suj/suj-stable8-r208287-1.diff.bz2
This backports SUJ from head to stable/8 (at r208799), by cherry-picking
the fol
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
sparky#
regards,
Jason
--
Coincidence, n.:
You weren't paying attention to the other half of what was
going on.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apout_procs while vmdaemon is running.
>>
>>Anyone else getting this?
>>
>>
>
>I'm amazed you've got a dual Pentium running -CURRENT at all.
>
>both of mine haven't worked with SMP kernels for months. (dual P54C and
>dual P55C).
>
>
>
Wi
hen nothing, it just sits there, 3 finger salute does not work. I have no
way to disable anything in the bios unfortunately.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ldunload it, it also dropped
me to db>
And that is pretty much where I am at.. No idea where to go now except
send off what I know and wait for someone to hopefully fix it :)
Jason
Ps, I also noted a few of these, not sure what they are
unknown: can't assign resources (port)
ldunload it, it also dropped
me to db>
And that is pretty much where I am at.. No idea where to go now except
send off what I know and wait for someone to hopefully fix it :)
Jason
Ps, I also noted a few of these, not sure what they are
unknown: can't assign resources (port)
below, sorry if anyone started looking into the problem.
Will try different machine and see what happens
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Jason
Sent: Friday, April 12, 2002 7:38 AM
To: Freebsd Current
Subject: WI Driver issues, compi
data etc to the swap
file)
Jason
KERNEL
machine i386
cpu I586_CPU
cpu I686_CPU
ident GENERIC
maxusers0
#To statically compile in device wiring instead of /boot/device.hints
#hints "
U using latest version of -current, in fact even the original 5.0 DR1
iso release supported the card, kernel needed some minor modification,
but I am using the dlink dwl 520 in my box right now without any
problems. And Brooks Davis was correct, with shows up as a linksys
device on my machines.
orks great, well no
real diff as far as I can tell.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of M. Warner Losh
Sent: Saturday, April 27, 2002 3:08 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: d-link dwl520 wireles
Look at the man pages for acpi, acpicontrol and acpidump.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Krzysztof
Parzyszek
Sent: Sunday, April 28, 2002 7:24 PM
To: [EMAIL PROTECTED]
Subject: Using laptop with lid closed
Is there any way to
on the x86?
3) Where is the stack on the Alpha?
4) Where is the code that I should have read instead of bothering you? The
rtld-elf code mentions the expectation that the "SVR4 ABI specification,
Intel 386 Processor Supplement" is adhered to, but I couldn't find
anything more
ems which haven't yet been converted to
the UBC interface).
-- Jason R. Thorpe <[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
amount of overhead". Whereas the
Mach object chains may be of arbitrary length (think about a program which
forks often), involving a potentially hash computation for each object
in the chain, the UVM case is always, at the most, two layers (in the
current amap implementation, the looku
tem, you
need to specify them all on one line with one options set. Like this:
/home/doogie /home/joebob /home/luser -maproot=0:0 testbox.accessus.net
Jason Young
accessUS Chief Network Engineer
PS: I just realized the manpage disagrees with this; it has multiple
exports lines for the same files
The card is also available in a 16-bit version (it has a PC Card logo on the
back, I don't know if the Cardbus one does or not). It's important to note
that the 575 (not the 574) is CardBus. I used to have one, but
semi-thankfully, it got blown up by lightning and the replacement was 16-bit
and t
> You can pull rev. 1.87 of if_ep.c out of the Attic from cvsweb:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/Attic/if_ep.c
>
> And it will drop directly into your tree in /sys/i386/isa.
> Make sure you
> have 1.23.2.1 or later of if_epreg.h.
Argh, I thought I was talking on t
two files without the -g flag, the linker error goes away.
In summary, it seems that using the -g flag to gcc can cause inline
functions to be ignored.
Can anyone shed some light on this?
Thanks,
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
}
> >
> It doesn't make much sense to have an "extern" inline function, gcc probably
> was confused by this, change "extern" to "static" and try again.
Yep, that fixed it. Thanks!
I just committed the change.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
#x27;re
primarily stuck in the kernel, or if some userland utility is sucking it up
(like natd, but your ipfw rules tend to rule out accidentally running
ethernet traffic through natd).
Jason Young
accessUS Chief Network Engineer
> -Original Message-
> From: james [mailto:[EMAIL PROT
d early this morning. The thing is, I successfully built the world
with those changes in place. It may be that you got a partial update of
the ~150 files that the changes touched in libc and libc_r.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ned reference to `_libc_open'
> *** Error code 1
> Stop in /usr/src/gnu/usr.bin/cc/cpp.
> *** Error code 1
Yes, three others have reported it as well. On the surface, it looks like
my fault, but I'm still in the process of trying to reproduce it (my most
recent buildworld went of
On Wed, Jan 12, 2000 at 11:16:38AM -0800, Jason Evans wrote:
> On Wed, Jan 12, 2000 at 02:57:41PM +0100, Pascal Hofstee wrote:
> > With my CURRENT-tre updated within an hour ago ... Buildworld is broken.
> >
> > cc -O -pipe -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H
> &g
1
libc successfully builds on Alpha with the changes I committed, though the
bootstrapping problem issue is the same. As noted in another email I just
sent, do:
cd /usr/src/lib/libc
make
make install
before doing a buildworld. This probably isn't the correct way of
resolving such bootstrapping issues, but it works.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote:
> On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote:
> > On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
> > > On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
> > > > H
On Thu, Jan 13, 2000 at 12:16:31AM +0100, Wilko Bulte wrote:
> On Wed, Jan 12, 2000 at 01:22:25PM -0800, Jason Evans wrote:
> > On Wed, Jan 12, 2000 at 10:07:25PM +0100, Wilko Bulte wrote:
> > > On Wed, Jan 12, 2000 at 09:56:22PM +0200, Mark Murray wrote:
> > > > H
at
stage can be linked against. This looks cleanest to me, but adds
substantially to build time and may be difficult to implement.
Suggestions are welcome.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Jan 13, 2000 at 08:35:16PM +0100, Wilko Bulte wrote:
> I resurrected things by grabbing an 'old' .4 library from another Alpha.
> Now things work again.
In case you missed it, I checked in a probable fix for the bug that got you
last time around. You might try again
as is
until our grand new threads library is realized. However, I agree that in
the end we will want to simplify the libc symbol naming.
I'm planning on checking in libc_r cancellation changes today that use the
current libc symbol naming setup. As soon as we're not using libc_r
anymore
re to remove _libc_open() and use open() instead inside of libc, we
would incorrectly propagate cancellation points (as is the case right now,
since _libc_open() and open() are the same in libc_r).
If we were to remove _libc_open() and use _open() instead inside of libc,
then we would have the problem
or will occur. I did a 'make includes' during my testing, so I didn't
have this problem.
It's my understanding that the build system is supposed to be sophisticated
enough to avoid such bootstrapping issues, but I don't understand it all
that well. Can someone explain whether
On Fri, Jan 21, 2000 at 03:47:27PM -0800, David O'Brien wrote:
> On Fri, Jan 21, 2000 at 02:22:51PM -0800, Jason Evans wrote:
> >
> > I did a 'make includes' during my testing, so I didn't have this
> > problem.
> ...
> >
> > In any case,
tmode. In keeping with these flags_to_string
has been renamed getflags and string_to_flags to setflags.
This is the same kind of breakage I caused when moving some definitions
into unistd.h. I would call it bootstrapping breakage, but others who know
the build syste
side of secure/. I've verified twice it's up-to-date with CVS..
I'm still trying to test this patch before committing.
Jason
Index: SYS.h
===
RCS file: /home/ncvs/src/lib/libc/alpha/SYS.h,v
retrieving revision 1.9
diff -u
?
>
> After a longtime disk check, I login again, Server Reset again
>
> Don't things realy strage ?
> Everything wroks fine if 1th-4th PCI slot is empty, no device
> attached.
> Same kernel, Same Applications its running
aren't pci slots 1
verflow. Trying to always catch stack overflow is not practical. Since
this is a heuristic error detection technique, I'm not sure how much
work/complexity it's worth to paramaterize the number of guard pages for
each mapping.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
) (one region
per thread), so this applies there as well.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, Feb 16, 2000 at 02:13:39PM -0800, Jason Evans wrote:
> On Wed, Feb 16, 2000 at 01:18:13PM -0800, Matthew Dillon wrote:
> > This deals with a mmap+fork bomb that can cause the kernel to
> > eat all of KVM in vm_map_entry structures. The default limit
> &
fications
> are actually quite minor.
I would really like to see this change happen, and will happily make the
necessary libc_r and linuxthreads changes to use the functionality, but
we're well into the code freeze right now, which IMO makes this more
appropriate for 4.1.
Jason
To Unsub
s, it looks like use of the last three should be removed from pthread.h.
I'll submit a patch to Jordan.
Thanks,
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, Mar 01, 2000 at 09:30:43AM -0500, Daniel M. Eischen wrote:
> I haven't run any other regression tests. I'll do that when I get
> some more time. Jason, can you also take a look at these changes and
> run some tests on them?
I just moved a couple of days ago and al
I just installed the latest 4.0 snap off of ftp2.freebsd.org. Didn't
install the DES libraries...
I get this when trying to run tcpdump on the system:
unstable# tcpdump
/usr/libexec/ld-elf.so.1: Shared object "libcrypto.so.1" not found
enjoy
-
On Mon, Mar 13, 2000 at 06:12:22PM +1100, John Birrell wrote:
> I deleted the weak definitions in the _THREAD_SAFE PRSYSCALL in
> lib/libc/i386/SYS.h and the problem goes away. I don't understand why
> Jason needed to add them in the first place.
I didn't need to add them. A
oesn't
interact with the static linker well. This is almost surely the reason
you're having problems. I'm very close (an hour, maybe) to checking a fix
into the RELENG_4 branch, as well as the head.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
test network.
See also http://www.canet3.net for further info.
Apologies if this message has screwy formatting.
--Jason
[EMAIL PROTECTED]
[EMAIL PROTECTED]
7. Who will benefit from CA*net 3?
CA*net 3 will be available to researchers at universities, and
government laboratories engaged in res
t of I couldn't figure out how to set the flag. This
is the "I'm probably doing this wrong" part.
2) Addition of the 574B's product ID.
3) Output of some more useful info when booting verbosely.
Jason Young
accessUS Chief Network Engineer
*** /home/doogie/if_ep.c
I'm not certain what the problem is, but the ep0 changes that generated
the HEADS UP messages affect _only_ PC Cards. The other sections of code
are untouched. Further, I'm 99% sure the only card that could possibly
have been broken by the probe change is the 3C574 PC Card (not 3C574B
ough
> freebsd-current a few days ago asking for any problem reports with ep0.
> My mistake - sorry - I shall return to lurking.
I think David was joking with you, hence the \begin{wpaul} statement. Bill
Paul is of course our resident Ethernet driver guy, and he is not known
for his patience
to the
new ATA driver.
I wonder if Soren (sorry, I don't know how to persuade my machine to spell
your name correctly) would be interested in one so that he could work on
supporting it? I would be happy to send one.. email me privately.
Jason Young
accessUS Chief Network Engineer
On Mon, 27
ic C-A-Esc doesn't drop me into kdb. I don't have my motherboard
specifications handy, but does anybody know of why this might be occuring.
thanks
-jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
disable on install disk, or get a 4.0 floppy that doesn't freeze on
'unknown0', of course, not having it detected at all would be preferable
:)..
Thanks in advance,
Jason DiCioccio
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I use visual_userconfig set ed0 to 0x240 and irq 7 and it detects it
I dont need the PnP probe on ISA bus.
On Sat, 9 Oct 1999, Daniel C. Sobral wrote:
> Jason DiCioccio wrote:
> >
> > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
> > in
I shall try again :)
On Sat, 9 Oct 1999, Doug Rabson wrote:
> On Sat, 9 Oct 1999, Jason DiCioccio wrote:
>
> >
> > Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
> > insists on detecting my ethernet card PnP at installation even though Id
&
as i've said, because it freezes my machine when it detects it PnP..
And, as you can imagine, I do not want my installation freezing on me :)
On Sun, 10 Oct 1999, Daniel C. Sobral wrote:
> Jason DiCioccio wrote:
> >
> > I use visual_userconfig set ed0 to 0x240 and irq
mething to
that effect? I told it to probe 0x240 @ IRQ 7 which is where it is.. all
my bios settings etc have no changed since last time I used floppy (the
one that froze but still found ed0) ..
Thanks in advance,
Jason DiCioccio
On Sat, 9 Oct 1999, Doug Rabson wrote:
> On Sat, 9 Oct 1999, Jas
Oct 1999, Doug Rabson wrote:
> On Sun, 10 Oct 1999, Jason DiCioccio wrote:
>
> > I just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old
> > floppy, I could set the parameters for ed0 and it would find ed0.. now it
> > doesn't find ed0 at all although it
Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while
it should be on irq 7
On Sun, 10 Oct 1999, Doug Rabson wrote:
> On Sun, 10 Oct 1999, Jason DiCioccio wrote:
>
> > Sorry I can't get pnpinfo, I can tell you though that dmesg does not even
> > s
It worked when it was probed non-pnp :-).. As long as I set the params..
DId you get my email with pnpinfo and dmesg?
On Sun, 10 Oct 1999, Doug Rabson wrote:
> On Sun, 10 Oct 1999, Jason DiCioccio wrote:
>
> > Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3)
ying on the -pthread linker
magic. This is high on Daniel Eischen's wish list, so maybe he already
has something in the works. =)
If you know of other outstanding issues that have a prayer of being
addressed before 4.0 ships, please speak up.
Jason
Jason Evans <[EMAIL PROTECTED]>
h
w for replying to my message. I'll get the boot messages
this morning.
Jason
- Original Message -
From: Greg Lehey <[EMAIL PROTECTED]>
To: Jason Craig <[EMAIL PROTECTED]>; Jason Craig <[EMAIL PROTECTED]>; Jason
<[EMAIL PROTECTED]>
Cc: FreeBSD current users <[EMA
. Is there anything wrong with simply
adding:
CFLAGS+=-I${.CURDIR}/../../include
to lib/libc_r/Makefile? It fixes such build problems.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
_POSIX_THREADS without defining
> _POSIX_THREAD_SAFE_FUNCTIONS, but either way we're non-compliant, so I'm
> leaving _POSIX_THREADS defined.
>
> They're not in unistd.h either. This is a FreeBSD bug.
They're in sys/unistd.h, which is included by unistd.h. That should be
just fine, and that location appears to be consistent with our other POSIX
macro definitions.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
pci/amd.c:857: warning: `amd_reset' defined but not used
*** Error code 1
Stop in /usr/src/sys/compile/JASONLAP.
--
Jason Garman http://web.wedgie.org/
Student, University of Maryland [EMAIL PROTECTED]
>From fortune(1):
../../pci/amd.c:175: warning: (near initialization for `amd_device')
../../pci/amd.c:899: warning: `amd_timeout' defined but not used
../../pci/amd.c:857: warning: `amd_reset' defined but not used
--
Jason Garman http
this was
necessitated due to the i386 packages-5-current tree appearing.
as there are a number of downstream mirrors of our freebsd area,
it is likely the alpha packages will no longer be carried by them
either.
-jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
That should get your soundcard to appear as soundcard #0. There's an
astounding array of other cruft in your conf file that needs to go, but if
you're just puttering around and experimenting, do what you like.
BTW, "cat /dev/sndstat" is your friend.
Jason Young
Access US(t
natd.conf file, I'm lost. The closest I've found is the tutorial at
http://freebsd.peon.net, but that doesn't quite cover enough.
Thanks in advance,
Jason Mitchell
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
work on this in
relative peace.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
he BSD/OS code in this case; I'm
just looking for clarification.
Thanks,
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
m on a web page. This will also
happen in the next couple of days.
> Audio ?
>
> Video ?
Greg Lehey has a PAL recording of much of the meeting. If you want to get
ahold of a copy, talk to him privately to see what arrangements you can
make.
Jason
To Unsubscribe: send mail to [E
On Sun, Aug 20, 2000 at 12:14:05PM +, Nik Clayton wrote:
> On Mon, Jun 19, 2000 at 11:53:30AM -0700, Jason Evans wrote:
> > Summary: -current will be destabilized for an extended period (on the order
> > of months). A tag (not a branch) will be laid down before the initial
&
mutex operations last time I
> checked, and there is a descriptor for each file and each file descriptor.
Note that additional locking with witness turned on can drastically affect
performance. Chances are that Alfred's changes in combination with witness
are what caused the slowdo
c: In function `main':
gcctest.c:5: warning: implicit declaration of function `foo'
gcctest.c:9: warning: implicit declaration of function `printf'
gcctest.c:12: warning: control reaches end of non-void function
RedHat (8 ~): ./gcctest
hello, stupid compiler!
Terry Lambert wrote:
>
> Jason Andresen wrote:
> > Odd, I can't reproduce that under RedHat:
>
> I guess you are saying there is a conspiracy to make GCC work
> only on RedHat?
>
> I could believe that... 8-) 8-) 8-).
>
> Actually, that was against 3.
ng
by cvsuping to 4-STABLE and installing that system first, then upgrading
to -CURRENT.
Jason Rhodes
>
> Should -current work under vmware by default, or are there steps i
> should take to make it work?
>
> thanks
>
> thomas
To Unsubscribe: send mail to [EMAIL PROTECTED]
ests; otherwise they wouldn't have
gone to the trouble of implementing speculative writes.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I am trying to install one of the -current snapshots, but
current.freebsd.org doesn't seem to want to let me log in as anonymous
(some problem saying it cannot set guest access). Has the procedure
changed to get -current?
thanks
-j
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taken from: http://www.deadly.org/article.php3?sid=20010408202512
Aaron Campbell writes : "Two aspects of the FFS filesystem in OpenBSD
have received significant improvements since 2.8, increasing
performance dramatically. Thanks to art, gluk, csapu
I had exactly the same thing happen to /var on an SMP test box using
-current as of 16 May. It happened once out of about a half dozen panics.
Jason
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ed in your
license?
Thanks in advance,
-JD-
--
Jason DiCioccio - [EMAIL PROTECTED] - PGP Key @ http://bsd.st/~geniusj/pgpkey.asc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
1 - 100 of 293 matches
Mail list logo
