=0x0037168c
rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
class = network
Is this card supported by FreeBSD? If yes, by which driver?
mfg sam
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
Hi
That's a shame. But I look forward to test it, if you get the time, to
work on it.
mfg sam
Am 20.06.2012, 23:09 Uhr, schrieb Adrian Chadd adr...@freebsd.org:
Hi,
On 20 June 2012 14:02, sam samira@gmail.com wrote:
or if you prefer pciconf:
none12@pci0:8:0:0: class
Folks, I hate to be snotty, but gosh, I don't think this thread really
belongs in a discussion about -stable. Bad enough that the sendmail
created so many me too's but wouldn't -chat be a better place for
california laws?
Sam
--
Just because you're moving fast | BURMA SHAVE
Buildkernel dies without device bpf in the config file.
I think this is due to Sam's commit on 11-14 changing
sys/net/bpf.c and bpf.h.
Anyone else seeing this?
Yup, I'll fix it. Thanks.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
the bus_dma routines) and quickly
aborts when it can't get the memory. Something else must be going on in
acpi.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
duplication are in for a surprise. We need to re-implement the packet
header copying code so that it can generate a failure (because it
involves allocation), and separate the duplicate and move abstractions
to get clean semantics. I exchanged some e-mail with Sam Leffler on
the topic
);
m = n;
}
Something is wrong with your tree:
ebb% grep aux ../sys/mbuf.h
ebb%
The above code is correct in the repo as is the m_getcl code.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Nov 25, 2002 at 10:46:00AM -0800, Sam Leffler wrote:
I don't see this problem; looutput looks to do the right thing.
FWIW
I've
passed mbufs w/ mtags through the loopback interface.
This refers specifically to the following code snippet:
if (m m-m_next
this? I'm tempted to point the finger at GEOM, but hate to say anything
like that.
Same problem hit me yesterday. Haven't figured out the cause yet.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Try the dc driver instead of xe. I have the same card and it worked once I
added the cardbus glop to read the MAC address from the CIS.
Sam
- Original Message -
From: Ari Suutari [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, December 03, 2002 4:41 AM
Subject: Xircom
attach method (typical) then you'll get this complaint.
Fixing it, and some other similar stuff, requires some care since the code
assumes malloc will not fail.
I decided to leave it until after 5.0.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
.
On the back of the card is says realport ethernet 10/100+modem 56
and REM56G-100.
You're correct, I have the RBEM56G-100 and it has vendor id 0x115d.
Sorry.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
and won't settle for the
status quo.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
PFIL_HOOKS when using ipfilter
#endif
Unfortunately there's no way that I know to express this if ipfilter is
loaded as a module.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
specify PFIL_HOOKS when using ipfilter
#endif
Unfortunately there's no way that I know to express this if ipfilter is
loaded as a module.
Duh, there'll probably be unresolved symbols if you try to load ipl.ko w/o
PFIL_HOOKS defined in the kernel.
Sam
To Unsubscribe: send mail to [EMAIL
stored in socket buffers so that
the data value returned by kevent()'s EVFILT_READ filter on non-TCP
sockets accurately reflects the amount of data that can be read from the
sockets by applications.
What are non-data characters?
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
On Fri, 10 Jan 2003, Sam Leffler wrote:
unless the mbufs are specifically tagged as such. I'm not clear on
exactly
what sb_ctl is supposed to count; the comment in the cvs log is unclear:
Track the number of non-data chararacters stored in socket buffers so
that
the data value returned
ion 1
DH_generate_key"
What is wrong and how to fix it?
Any help will be gratefull!
Thanks!
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
om
driver, OpenSSL (and consequently lots of crypto tools (like SSH))
will fail with strange errors.
/suggestion
Thanks!
--
Mark Murray
It works! Thanks for your help!
sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
device drivers bpf0, bpf1, bpf2, and bpf3 are in /dev.
I don't know whatelse I should configure. Can someone help me?
My OS is FreeBSD 5.0-CURRENT #21.
Thanks!
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, 6 Aug 2003, Sam Leffler wrote:
Shouldn't that be 0.9.5.2? I run the latest current, and
hw.ath.hal.version is 0.9.5.2.
You're right; I committed a slightly older version to FreeBSD than to
Linux.
Any chance that you could commit the newer version? Or are the
differences too marginal
As to dstumbler, it is intimately tied to the wi driver at the moment. I
have a version that works w/ wi and ath drivers but it's a major rewrite
and incomplete. If someone wants to pick it up I'd be happy to pass the
(incomplete) work on...
Sam
___
[EMAIL
on
cardbus1 FreeBSD 5.1-CURRENT #0: Wed Aug 20 16:59:24 CEST 2003
Any solution for that Sam? I can remember you mentioned you have fix for
that a couple of weeks ago and that you will submit it in a week time or
so.
I have seen the problem but have been unable to resolve it. Grab a copy of
/usr/src
due to this change or others.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
, no separate module.
Thanks, will fix it.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
I've committed a number of changes to lock the middlware parts of the
network subsystem. There's still more to come; I'm moving slowly to insure
each batch gets exposure. All the pending changes can be found at:
http://www.freebsd.org/~sam
The major changes that will go in next week
Is the ath(4) driver, like the wi(4) driver, incapable of performing
bridging?
Yes. Bridging happens outside the operation of the driver.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
to
do.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
. The bridge manual page is
wrong and I will fix it.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
, 11a, 11b, 11g).
Also try sysctl debug.ieee80211=1 and/or ifconfig ath0 debug and look at
the debug messages.
Obviously stuff worked for me before I committed (and I tested all types of
cards).
Sam
___
[EMAIL PROTECTED] mailing list
http
Yes, I was referring to bridging two wireless interfaces.
David Young (of netbsd) has plans for WDS support that should fit into the
existing 802.11 layer. With his design you should be able to bridge WDS
links using the standard bridge support. No ETA.
Sam
I just committed changes to bridge, ipfw, and dummynet. I've been running
these for a while but beware. I'm aware of two LOR issues that I want to
sort out later, after some more changes have gone in. Regardless, if you
encounter problems let me know...
Sam
On Tue, Sep 16, 2003 at 09:29:07AM -0700, Sam Leffler wrote:
Please send me your kernel config and tell me again exactly what fails.
I will try to reproduce your problem.
Sam
After your yesterday/today commits, I got panic while doing netstat -an.
On the kernel from about two days
throughput was identical to the
non-turbo setup. I'm asking Atheros folks for clarification on this--I may
need to do some additional setup work to enable turbo operation. This is
actually the first time I've tried turbo mode...
Sam
___
[EMAIL PROTECTED
.
It seems to see the base station in turbo mode now, but I'm still getting
the authentication failed (reason 13) errors.
Are you using WEP? As I explained WEP doesn't work right now.
Sam
___
[EMAIL PROTECTED] mailing list
http
The following changes should be transparent but just in case they are not
please be aware...
Sam
sam 2003/09/23 10:54:04 PDT
FreeBSD src repository
Modified files:
sys/net bridge.c pfil.h pfil.c
sys/netinet ip_input.c ip_output.c
Could we add PFIL_HOOKS to GENERIC, while we're at it? Please?
Eventually this will happen. Almost certainly in time for 5.2.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
Sam Leffler wrote:
Could we add PFIL_HOOKS to GENERIC, while we're at it? Please?
Eventually this will happen. Almost certainly in time for 5.2.
It was due for 5.0-RELEASE, it hasn't made it in for 5.1-RELEASE and post
5.1-R reminders have been ignored on this list as well
After cvsup, buildworld error in usr.sbin/ipftest
[snip]
Dang, my bad. Will deal with it.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
disassociation problems on the laptop
seem to have cured (associating with other access points) ...
So I need help with this really large bug in the wi code.
Please send me your config. I'll deal with it.
Sam
___
[EMAIL PROTECTED] mailing
I'm looking into it. Everything built+ran fine with the last commit...
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
. Guess I need to update NOTES and add something to
UPDATING.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Tonight's current breaks compiling IPFILTER. It complains that it
can't find the 'PFIL_OUT' symbol.
Read UPDATING; you need PFIL_HOOKS in your kernel config file.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
. I think it's been busted for 1 week. I
tried to pinpoint the commit but ran out of time.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
. When
I issue a 'continue' command, I lose control of the system, but it
doesn't continue running. Has anybody else seen this?
It works as well as it did a few months ago here. (Not very well
compared with ddb. E.g., calling a function is usually fatal.)
Hmm, that's not what Sam
the
5.2 release. The most likely one you'll see is when ejecting a network card
from a laptop.
Please contact me directly if you see any problems that look related to these
changes.
Sam
___
[EMAIL PROTECTED] mailing list
http
of whether it conflicts with style(9).
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Apparently adhoc mode is currently busted. It's at the top of my todo list
and I may even get to it this week...
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
at that point.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
, ATA_A_IDS);
-DELAY(1);
+DELAY(10);
+ATA_IDX_INB(ch, ATA_ERROR);
/* wait for BUSY to go inactive */
for (timeout = 0; timeout 310; timeout++) {
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
uma_zone_slab
uma_zalloc_bucket
uma_zalloc_arg
uma_zalloc_arg
ffs_vget
ufs_lookup
ufs_vnoperate
vfs_cache_lookup
ufs_voperate
lookup
nfs_namei
nfsrv_lookup
nfssvc_nfsd
nfssvc
Contact me for more details. This really needs to be fixed.
Sam
___
[EMAIL
be the problem but w/o more
info I can't really help.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
for the WEP problem; let me know if
you have any more trouble. I verified 40-, 104-, and 128-bit WEP keys work
for me. As a bonus I also sped up WEP traffic through the driver.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org
. Thank you.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
this is fallout from the multicast code reorg that bms has been
working on.
Yup; it's on my list of bugs to look at.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
This fixes adhoc mode for wi devices. Adhoc mode is still not working
correctly for ath devices. No eta on fixing it.
Sam
---BeginMessage---
sam 2003/10/17 14:54:59 PDT
FreeBSD src repository
Modified files:
sys/net80211 ieee80211_output.c ieee80211_var.h
will not cause a system crash. If a LOR causes a problem it will likely
deadlock your system.
The two LORs shown above are known and should not be a problem.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo
can get a stack trace the next time this happens? The LOR by
itself is hard to go from...
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
.
The following drivers are marked MPSAFE:
ath, em, ep, fxp, sn, wi, sis
I've got changes coming for bge. Other drivers probably can be marked MPSAFE
but I'm only doing it for those drivers that I can test.
Sam
---BeginMessage---
sam 2003/10/29 10:29:50 PST
FreeBSD src
On Thursday 30 October 2003 01:22 am, Pawel Jakub Dawidek wrote:
On Wed, Oct 29, 2003 at 11:52:48AM -0700, Sam Leffler wrote:
+ I'm committing changes to mark various network drivers' interrupt
handlers + MPSAFE. To insure folks have a way to backout if they hit
problems I've also + added
was next on my list...
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
at each end. If you've got a swtch in the middle make sure it
does the right thing.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
+0x147
in6_update_ifa(c200,c8f45a1c,0,0,20080fe) at in6_update_ifa+0x500
in6_ifadd(c8f45b34,0,40,0,0) at in6_ifadd+0x22a
I've got fixes for almost all the outstanding LOR's and recursive lock
problems. I'm doing more testing before I committing them.
Sam
of their manifestations is that SMP kernels always
panic in sbdrop() on shutdown.
I'm looking at something similar now. If you have a stack trace please send
it to me (along with any other info). You might also try booting
debug.mpsafenet=0.
Sam
.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
response
- ASSOC response
and then the client retries again ad infinitum.
If you've got an AP running with recent source and a wi card please contact
me.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
soon. I'm hoping to resolve the problem.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
the Atheros driver w/o
patching the tree. man ath(4) for info on the driver.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
.
Sam
*First by a few days--there is also a Linux version of this software
available at http://sourceforge.net/projects/madwifi/.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
. SGI's XFS implementation is all new work.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
. This is a bug in the HAL that I've got fixed but is
taking forever to verify correctness. With luck I'll have new stuff
committed this week (but that's what I thought last week...).
Sorry, it was my bad :(
Sam
___
[EMAIL PROTECTED] mailing list
http
of the firmware update tools. How did you
upgrade your firmware? If anyone has the bits+pieces to rev firmware I'd
like it so I can test the wi driver w/ different firmware revs.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
to Linux.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
these as modules, install them, and do
kldload ath
Module dependencies will do the rest.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
know what M_NOTIFICATION is used for but if it's applied sparingly
it might be better to use an m_tag instead.
Sam
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL
I just have to ask: is this in any way related to the a/b/g network
card in my laptop that shows up as:
[EMAIL PROTECTED]:3:0: class=0x028000 card=0x00011028 chip=0x432414e4 rev=0x02
hdr=0x00 vendor = 'Broadcom Corporation'
class= network
if (broadcom == atheros)
use ath
problems please contact me (or Warner).
This work is the first step towards significant improvements in the wireless
support.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Sorry, for the new wi driver you need to add:
device wlan
to your config files. This probably belongs in UPDATING.
Sam
- Original Message -
From: Matt Haught [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 15, 2003 9:59 PM
Subject: Re: HEADS UP: new wi driver
I
On Thu, 16 Jan 2003, Sam Leffler wrote:
...
to your config files. This probably belongs in UPDATING.
NB the new wi(4) is probably also an issue for ports/net/bsd-airtools,
to be resolved or documented before MFC. (copied maintainer)
Why, did they not work/build after the commit? I
with:
ifconfig wi0 debug link2
Setting the sysctl value to 1 will give more verbose output which is
unlikely to be useful. I have to commit some mods to tcpdump and bpf before
you can use tcpdump to tap packets at the 802.11 link layer.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED
in hostap mode). You can get 1.4.9
firmware at http://www.netgate.com/support/prism_firmware/.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sun, Jan 19, 2003 at 07:46:11PM -0800, Sam Leffler wrote:
Finally, you may want to try different station firmware in your Dlink
card. I run 1.4.9 in my Senao (Prism 2.5) cards with good success. I
don't recall whether there were issues with 1.3.6 (I know some of the
intermediate
info,
just drop me a message.
I have no answer for you. There's just not that much difference between
adhoc and hostap mode to explain this. If you were using wep and it was
being offloaded to the host I could understand a noticeable difference in
performance.
Sam
To Unsubscribe: send
to a prims/wavelan/symbol card
so was replaced by WI_RID_SCAN_APS which provides a device-independent
interface. I changed wicontrol to deal with this; it would be good if
dstumbler did likewise. Otherwise I can look at adding a backwards
compatibility entry for WI_RID_SCAN_REQ.
Sam
About benchmarks...
FWIW, the reiserfs people were excited about SCO's
release of AIM:
http://caldera.com/developers/community/contrib/aim.html
but the announcement went rather unnoticed in
freebsd-fs.
Thanks. I've worked with AIM. Wasn't aware it had been released.
Sam
looking for
good benchmarks. lmbench, rawio, and bonniee are rather micro in nature
(not bad, just limited in their usefulness).
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Thursday 13 February 2003 11:28 pm, Sam Leffler wrote:
At 4:36 PM -0800 2003/02/13, Scott Long wrote:
- the classic 'worldstone'
- webstone - /usr/ports/www/webstone
- Fstress - http://www.cs.duke.edu/ari/fstress
- ApacheBench - /usr/ports/www/p5
At 9:47 PM -0800 2003/02/13, Sam Leffler wrote:
SpecFS (NFS ops/sec benchmark)
List price on SPEC SFS97 R1 is $900. And my recollection is that it
was
involved to setup and run.
$450 for educational organizations. Wouldn't the FreeBSD
Foundation qualify?
The point
This may affect your ipfw/ipf rules. If you are happy with the current
behaviour then add IPSEC_FILTERGIF to your kernel config file.
Sam
- Original Message -
From: Sam Leffler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Saturday, February 22
I'm getting a LOT of these.
ether_input: drop bdg packet, bif 0x5
This was a stray debugging printf I forgot to remove. Update your system.
wi0: tx failed, retry limit exceeded
If this happens again show the output of sysctl hw.wi.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED
* De: Sam Leffler [EMAIL PROTECTED] [ Data: 2003-02-25 ]
[ Subjecte: Re: Errors with wireless ]
wi0: tx failed, retry limit exceeded
If this happens again show the output of sysctl hw.wi.
I get those constantly when doing e.g. an interactive FTP session.
([EMAIL PROTECTED]:~)10
committed a fix.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, ebp=0 ---
Fixed last night.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
accelerate
doing the commit? The assert is actually just bogus (if_start can be called
under certain conditions with IFF_OACTIVE set.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
bug. Anyone seen this with other NIC's?
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
tell if it was really a cpp0 bug or just memory getting trashed
(possibly by the OS). I was eventually able to work around it modifying the
source code.
Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Please take a minute to review the attachment. Thank you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Any good reason why the the patch in this PR hasn't yet been
committed to the tree?
Thanks for your consideration.
Take care,
--Sam
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, Aug 17, 2001 at 10:07:29AM -0600, Warner Losh wrote:
In message [EMAIL PROTECTED] Sam Habash writes:
: Any good reason why the the patch in this PR hasn't yet been
: committed to the tree?
lack of time on my part.
I see you've been busy lately with necessary good stuff, so
where uname -m and uname -p arent the same.
To do with the new installer I imagine.
Vince
When this came up in another conversation, I found:
http://lists.freebsd.org/pipermail/freebsd-hubs/2011-September/002380.html
--
Sam Cassiba s...@cassiba.com
1 - 100 of 197 matches
Mail list logo
