Re: Trying to build CURRENT
On Wed, Dec 19, 2001 at 09:12:18PM -0600, Joe Halpin wrote: I'm getting the following error when running 'make buildworld' perl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/des/asm:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/perlasm /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/bf/asm/bf-586.pl elf 386 bf-586.cmt /usr/libexec/ld-elf.so.1: Shared object libperl.so.3 not found *** Error code 1 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I'm running 4.4-RELEASE right now, and trying to go to -CURRENT. I did a cvsup to get the source, and ran make buildworld I just updated the source tree tonight. Should I wait to try again, or am I doing something wrong? I've got the complete make output in a file if that would help. Your host environment is screwed, you lost /usr/lib/libperl.so.3. Watch ``ldd /usr/bin/perl'' output. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Buildworld broken on _FBSDID in xinstall.c ??
Thats what I did yesterday, and buildworld/installworld worked fine after that :)) Warner Losh [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED] Mike Barcroft writes: : Any suggestions? : : I would recommend removing the __FBSD() line locally until this has : been resolved. cvsup might be better :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message __ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Object now: man(1) -m option is going away
Ruslan Ermilov wrote: I'd like to drop the support for the man(1)'s -m option, which is almost undocumented and is of little interest. Unless I hear any valid objections, I am going to nuke it on Friday. How do you propose we look at Alpha specific man pages on x86 boxes, after this change? Thanks, -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Object now: man(1) -m option is going away
On Tue, Dec 18, 2001 at 11:32:48AM -0800, Terry Lambert wrote: Ruslan Ermilov wrote: I'd like to drop the support for the man(1)'s -m option, which is almost undocumented and is of little interest. Unless I hear any valid objections, I am going to nuke it on Friday. How do you propose we look at Alpha specific man pages on x86 boxes, after this change? I suppose you have them installed in standard places, like /usr/share/man/man4/alpha/. If so, use the MACHINE environment variable, as documented in the man(1) manpage. If you have then installed in a separate tree, use the MANPATH environment variable, or the -M option to man(1). Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Trying to build CURRENT
Ruslan Ermilov wrote: On Wed, Dec 19, 2001 at 09:12:18PM -0600, Joe Halpin wrote: I'm getting the following error when running 'make buildworld' perl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/des/asm:/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/perlasm /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/bf/asm/bf-586.pl elf 386 bf-586.cmt /usr/libexec/ld-elf.so.1: Shared object libperl.so.3 not found *** Error code 1 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 Stop in /usr/src/secure/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I'm running 4.4-RELEASE right now, and trying to go to -CURRENT. I did a cvsup to get the source, and ran make buildworld I just updated the source tree tonight. Should I wait to try again, or am I doing something wrong? I've got the complete make output in a file if that would help. Your host environment is screwed, you lost /usr/lib/libperl.so.3. Watch ``ldd /usr/bin/perl'' output. Yep. See my response to Mike. I got going again by manually copying it from the build directory. Thanks Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Intel 82544GC Gigabit support?
hi does anyone know if this is/will be supported? roy -- Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA Computers are like air conditioners. They stop working when you open Windows. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Merry Christmas and Happy New Year
Hi, I know, this is not the right place, but my best wishes to the whole freebsd community for doing such a great job. To all of you *** merry christmas and happy new year *** regards, -- Jean Louis Ntakpe Texas Instruments - Freising [EMAIL PROTECTED] Wafer Fab Automation Group [EMAIL PROTECTED] Haggerty Str. 1 85350 Freising Telefon +49 (8161) 80-3816 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
__stdoutp causing hassle ;)
Heyas After upgrading directly to CURRENT from 4.3- RELEASE I've been presented with a rather loud and whiney bug (I thought it at first to be my ex- girlfriend somehow manifested via `festival` but thk god it was not). Every shared library on the system drops via ld-elf.so.1 regarding the symbol __stdoutp. This pretty much kills everything as I m sure u can imagine :) Does anyone have any idea why the libs arent being pointed to libc.so.5 properly? (That is where __stdoutp should be (and is) defined.) Any input is appreciated. north_ http://blessedchildren.virtualave.net/ __ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: __stdoutp causing hassle ;)
Date: Thu, 20 Dec 2001 06:14:14 -0800 (PST) From: north star [EMAIL PROTECTED] After upgrading directly to CURRENT from 4.3- RELEASE I've been presented with a rather loud and whiney bug (I thought it at first to be my ex- girlfriend somehow manifested via `festival` but thk god it was not). Every shared library on the system drops via ld-elf.so.1 regarding the symbol __stdoutp I suspect that you failed to include COMPAT4X= yes in /etc/make.conf (as a review of the -current archives should have indicated). Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CD-ROM installation of -CURRENT broken?
On Wed, 19 Dec 2001, Brian Fundakowski Feldman wrote: Does anyone know when installation of -CURRENT from CD-ROM got broken or a solution thereof? We end up having two problems: the fixit shell doesn't work, but before that an actual installation doesn't work because sysinstall's attempt to mount /dev/acd0c on /dist returns ENOENT. I havne't determined yet why this could be; anyone have clues? The 'c' partition of acd0 devices was broken for the non-DEVFS case in rev.104 of atapi-cd.c. (The errno for this is ENXIO.) DEVFS is not in GENERIC and make release doesn't seem to add it. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Dropping bsd.man.mk support from bsd.kmod.mk
Hi! I'd like to drop bsd.man.mk support from bsd.kmod.mk, because I was told by someone (peter?) that this is the right direction. :-) Objections? Cheers, -- Ruslan Ermilov Oracle Developer/DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CD-ROM installation of -CURRENT broken?
Bruce Evans [EMAIL PROTECTED] wrote: On Wed, 19 Dec 2001, Brian Fundakowski Feldman wrote: Does anyone know when installation of -CURRENT from CD-ROM got broken or a solution thereof? We end up having two problems: the fixit shell doesn't work, but before that an actual installation doesn't work because sysinstall's attempt to mount /dev/acd0c on /dist returns ENOENT. I havne't determined yet why this could be; anyone have clues? The 'c' partition of acd0 devices was broken for the non-DEVFS case in rev.104 of atapi-cd.c. (The errno for this is ENXIO.) DEVFS is not in GENERIC and make release doesn't seem to add it. Well, really, all we should care about is the devfs case since anything else is meant to be deprecated; I'd rather fix this at the source... DEVFS is no longer optional, so it is in GENERIC for certain. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CD-ROM installation of -CURRENT broken?
On Thu, 20 Dec 2001, Brian F. Feldman wrote: Bruce Evans [EMAIL PROTECTED] wrote: The 'c' partition of acd0 devices was broken for the non-DEVFS case in rev.104 of atapi-cd.c. (The errno for this is ENXIO.) DEVFS is not in GENERIC and make release doesn't seem to add it. Well, really, all we should care about is the devfs case since anything else is meant to be deprecated; I'd rather fix this at the source... DEVFS is no longer optional, so it is in GENERIC for certain. Oops, DEVFS is in GENERIC, but not because it isn't optional. It is controlled by a bogus negative option (NODEVFS). The NODEVFS case has rotted a bit, but it isn't as broken as DEVFS yet. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vm_zeropage priority problems.
Luigi Rizzo wrote:
[Cc peter because he introduced this code]
Hi,
i was trying the following code in -current (basically copied from
vm_zeropage.c), to implement device polling in the idle loop, and
noticed that the process would take all of the CPU time. Being
suspicious that something was wrong with priorities, I added a
couple of printfs, and to my surprise, the priority of the process
(pri_level) after the first tsleep() becomes 104 instead of staying
at 255 as it was originally initialized.
A quick scan of the files in sys/sys shows that 104 is PPAUSE,
and this is the source of the problem.
Excellent catch! This particular problem was one of the main reasons
why this is still defaulting to 'off'. I have a couple of other changes
to it pending commit to fix some of Bruce's complaints, but I hadn't
noticed the cause of this.
Part of the problem is that tsleep temporarily elevates the priority for
wakeup, and it is normally returned back to normal level when the process
returns to userland (see the *_userpri stuff).
Changing the tlseep PPAUSE value isn't necessarily the right thing either
because the priority propagation mechanism will elevate us if we hold a lock
that something else *needs*. (This is so that when it yields, we will run
and do what we need to do and presumably release the lock.)
I guess this is a bug in vm_zeropage.c, the second parameter
in tsleep should be td-td_ksegrp-kg_pri.pri_level instead
of PPAUSE, or at least the priority should be reset to the
original value after returning from the tsleep ?
Possibly both of these. Let me do some checking.
cheers
luigi
static void
poll_idle(void)
{
struct thread *td = curthread;
struct rtprio rtp;
rtp.prio = RTP_PRIO_MAX;/* lowest priority */
rtp.type = RTP_PRIO_IDLE;
mtx_lock_spin(sched_lock);
rtp_to_pri(rtp, td-td_ksegrp-kg_pri);
mtx_unlock_spin(sched_lock);
printf(idlepoll start and sleep, pri is %d native %d user %d\n,
td-td_ksegrp-kg_pri.pri_level,
td-td_ksegrp-kg_pri.pri_native,
td-td_ksegrp-kg_pri.pri_user);
for (;;) {
if (poll_in_idle poll_handlers 0) {
idlepoll_sleeping = 0;
mtx_lock(Giant);
ether_poll(poll_each_burst);
mtx_unlock(Giant);
mtx_assert(Giant, MA_NOTOWNED);
mtx_lock_spin(sched_lock);
setrunqueue(td);
td-td_proc-p_stats-p_ru.ru_nvcsw++;
mi_switch();
mtx_unlock_spin(sched_lock);
} else {
printf(idlepoll goes to sleep,
pri is %d native %d user %d\n,
td-td_ksegrp-kg_pri.pri_level,
td-td_ksegrp-kg_pri.pri_native,
td-td_ksegrp-kg_pri.pri_user);
idlepoll_sleeping = 1;
tsleep(idlepoll_sleeping, PPAUSE, pollid, hz * 3);
}
}
}
static struct proc *idlepoll;
static struct kproc_desc idlepoll_kp = {
idlepoll,
poll_idle,
idlepoll
};
SYSINIT(idlepoll, SI_SUB_KTHREAD_VM, SI_ORDER_ANY, kproc_start, idlepoll_kp)
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: vm_zeropage priority problems.
On Thu, Dec 20, 2001 at 11:13:27AM -0800, Peter Wemm wrote: ... Excellent catch! This particular problem was one of the main reasons why this is still defaulting to 'off'. I have a couple of other changes to it pending commit to fix some of Bruce's complaints, but I hadn't noticed the cause of this. Part of the problem is that tsleep temporarily elevates the priority for wakeup, and it is normally returned back to normal level when the process returns to userland (see the *_userpri stuff). ah, ok, kernel threads never return to userland... so, i presume one should also make sure that after the process is scheduled, the priority is restored to the 'native' level; this should also solve the problem with the priority propagation mechanism (though... I have the feeling that if you have nested locks, this cannot scale...) cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vm_zeropage priority problems.
On 20-Dec-01 Luigi Rizzo wrote: On Thu, Dec 20, 2001 at 11:13:27AM -0800, Peter Wemm wrote: ... Excellent catch! This particular problem was one of the main reasons why this is still defaulting to 'off'. I have a couple of other changes to it pending commit to fix some of Bruce's complaints, but I hadn't noticed the cause of this. Part of the problem is that tsleep temporarily elevates the priority for wakeup, and it is normally returned back to normal level when the process returns to userland (see the *_userpri stuff). ah, ok, kernel threads never return to userland... so, i presume one should also make sure that after the process is scheduled, the priority is restored to the 'native' level; this should also solve the problem with the priority propagation mechanism (though... I have the feeling that if you have nested locks, this cannot scale...) Priority propagation will already handle things ok. We drop to pri_native after we drop a lock (although if we still hold a contested lock we bump our priority to the min(nativepri, highest priority of threads on contested locks we hold and drop to nativepri after dropping the last contested lock). However, kthreads should tsleep() with their current priority, not PPAUSE. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vm_zeropage priority problems.
On Thu, Dec 20, 2001 at 12:16:03PM -0800, John Baldwin wrote: ... Priority propagation will already handle things ok. We drop to pri_native after we drop a lock (although if we still hold a contested lock we bump our priority to the min(nativepri, highest priority of threads on contested locks we hold and drop to nativepri after dropping the last contested lock). ok, thanks for the clarification However, kthreads should tsleep() with their current priority, not PPAUSE. current meaning pri_level or pri_native ? What if one tries to tsleep() while holding a lock and so its pri_level is raised ? In the device polling code i did a tsleep on the original pri_level, but maybe pri_native is good enough. cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vm_zeropage priority problems.
On 20-Dec-01 Luigi Rizzo wrote: On Thu, Dec 20, 2001 at 12:16:03PM -0800, John Baldwin wrote: ... Priority propagation will already handle things ok. We drop to pri_native after we drop a lock (although if we still hold a contested lock we bump our priority to the min(nativepri, highest priority of threads on contested locks we hold and drop to nativepri after dropping the last contested lock). ok, thanks for the clarification However, kthreads should tsleep() with their current priority, not PPAUSE. current meaning pri_level or pri_native ? What if one tries to tsleep() while holding a lock and so its pri_level is raised ? pri_level. Calling tsleep() while holding a lock is a bug though. :) Unless you are calling msleep() with a lock that will be released. In the device polling code i did a tsleep on the original pri_level, but maybe pri_native is good enough. pri_level is more correct. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: My naive addendum to Matt's recommended dev/test env
On Fri, Dec 14, 2001 at 12:06:24PM -0500, Peter Dufault wrote: ... # cd /FreeBSD/FreeBSD-stable/src # make installworld (Lot's of noise as the stable kernel installs the stable world. Then reboot) You've missed a critical step here: Before you reboot you need to run mergemaster. You might be lucky and not need it for the -RELEASE to -STABLE upgrade, but you can be certain that the one time you don't bother, it'll come back and bite you in some obscure manner. # sync The sync isn't necessary (and has never been necessary for FreeBSD). # reboot Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: __stdoutp causing hassle ;)
I suspect that you failed to include COMPAT4X= yes in /etc/make.conf (as a review of the -current archives should have indicated). Cheers, david Ah, worked beautifully! Thanks, David, I appreciate it. I did look at the mail archives quickly but usually if I don't see anything within the past week or so I assume either I'm being ignorant of something or there is a new bug. I don't mind admitting when its my ignorance at fault :) north_ http://blessedchildren.virtualave.net/ __ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
y ahora que
;EL PUEBLO TENDRA QUE VOLVER A SALIR A LA CALLE AHORA COMIENZA EL REPARTO DE LA TORTA SE FUE CAVALLO Y de la RUA, AHORA EMPIEZA LA VERDADERA BATALLA ENTRE LOS UD. NO VOTO.- AHORA ES EL MOMENTO EN QUE PUERTA NO SABE DURANTE CUANTO TIEMPO GOBERNARA AHORA ES EL MOMENTO EN QUE RUCKAUFT, DUHALDE, de la SOTA, RODRIGUEZ SAA, REUTEMAN Y DEMAS CON LA COMPLACENCIA DE LOS CORRUPTOS Y CILENTELISTAS DIPUTADOS Y SENADORES DEBEN DECIDIR CUANDO SE LLAMA A ELECCIONES: EN UN MES; DOS MESES; SEIS MESES; UN AO O RECIEN EN EL 2003??? Y EN TANTO EL PUEBLO QUE HACE? MIRA, USADO Y ESPERA A VER SI LE DEVALUAN EL PESO Y EN CONSECUENCIA LE DEVALUAN EL SALARIO PORQUE YA ESTAN NEGOCIANDO LOS LEGISLADORES JUSITICIALISTAS CON LA UNION INDUSTRIAL.- LA BOLSA SOLO HOY SUBE MAS DEL 17 %.- CUAL ES EL FUTURO SI NO HAY UN PROYECTO DE PAIS MIENTRAS NO SE REUNA UNA NUEVA CONVENCION CONSTITUYENTE CON DIRIGENTES NUEVOS A NIVEL NACIONAL Y DE CADA PROVINCIA; MIENTRAS NO SE IMPLEMENTE UN SISTEMA DE GOBIERNO PALAMENTARIO; MIENTRAS NO SE RECONFIGURE LA DISTRIBUICION GEOPOLITICA CON MENOS DE PROVINCIAS; MIENTRAS NO SE DISMINUYAN LA CANTIDAD DE MUNICIPIOS Y OTRAS MUCHAS CUESTIONES MAS EL PUEBLO DEBERA NECESARIAMENTE SALIR A LAS PLAZAS CON SUS CACEROLAS FUTURO ARGENTINO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Broken at share/colldef
=== share === share/colldef colldef -I /usr/src/share/colldef -o bg_BG.CP1251.out /usr/src/share/colldef/bg_BG.CP1251.src ... /sv_SE.ISO8859-1.src colldef -I /usr/src/share/colldef -o uk_UA.ISO8859-5.out /usr/src/share/colldef/uk_UA.ISO8859-5.src colldef: Char 0xcd duplicated near line 36 *** Error code 69 Stop in /usr/src/share/colldef. *** Error code 1 Stop in /usr/src/share. *** Error code 1 -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. [EMAIL PROTECTED] // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
spam
I'm starting to get spam since I joined this list, and the spam is coming from freebsd.org. If I'm reading the headers right, it's coming in through a freebsd.org mail server. Return-Path: [EMAIL PROTECTED] Received: from mx2.freebsd.org ([216.136.204.119]) by rwcrgwc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id [EMAIL PROTECTED]; Fri, 21 Dec 2001 02:02:19 + Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 2BD2E559AE; Thu, 20 Dec 2001 18:02:16 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Received: by hub.freebsd.org (Postfix, from userid 538) id E83FF37B405; Thu, 20 Dec 2001 18:02:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 3319E2E8209; Thu, 20 Dec 2001 18:02:08 -0800 (PST) Received: by hub.freebsd.org (bulk_mailer v1.12); Thu, 20 Dec 2001 18:02:08 -0800 Delivered-To: [EMAIL PROTECTED] Received: from infoviaplus.net.ar (adv18.infoviaplus.net.ar [200.9.212.60]) by hub.freebsd.org (Postfix) with ESMTP id 0319A37B416; Thu, 20 Dec 2001 18:02:02 -0800 (PST) Received: from Windows ([200.63.137.113]) by infoviaplus.net.ar (Tid InfoMail Exchanger v2.20) with SMTP id #1008898760.080420001; Thu, 20 Dec 2001 22:39:20 -0300 From: rssa [EMAIL PROTECTED] To: Y ahora que. [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] X-Mailer: MultiMailer (3.1.0) Subject: y ahora que Mime-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable X-Infomail-Spawn: [EMAIL PROTECTED] a 200 destinos X-Infomail-Id: 1008898761.1F6A01AC1E039F.58761 Message-Id: [EMAIL PROTECTED] Date: Thu, 20 Dec 2001 18:02:02 -0800 (PST) Sender: [EMAIL PROTECTED] List-ID: freebsd-current.FreeBSD.ORG List-Archive: http://docs.freebsd.org/mail/ (Web Archive) List-Help: mailto:[EMAIL PROTECTED]?subject=help (List Instructions) List-Subscribe: mailto:[EMAIL PROTECTED]?subject=subscribe%20freebsd-current List-Unsubscribe: mailto:[EMAIL PROTECTED]?subject=unsubscribe%20freebsd-current X-Loop: FreeBSD.ORG Precedence: bulk X-Mozilla-Status: 8001 X-Mozilla-Status2: X-UIDL: [EMAIL PROTECTED] Is this just a normal part of being on the list? Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: spam
On Thu, 20 Dec 2001, Joe Halpin wrote: I'm starting to get spam since I joined this list, and the spam is coming from freebsd.org. If I'm reading the headers right, it's coming in through a freebsd.org mail server. headers snipped Is this just a normal part of being on the list? You're not getting the spam directly. The spam is sent to the mailing list and then sent to you as a subscriber. This is an unfortunate side effect of the fact that the mailing lists are open to posting from non-subscribers. Brandon D. Valentine -- Iam mens praetrepidans avet vagari. - G. Valerius Catullus, Carmina, XLVI To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
spam
On Thu, 20 Dec 2001 20:46:16 -0600, Joe Halpin [EMAIL PROTECTED] said: Is this just a normal part of being on the list? Yes, lots of spammers spew at FreeBSD mailing-lists. If you can identify a persistent source of spam, the postmaster is fairly responsive in filtering them. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Intel 82544GC Gigabit support?
In article [EMAIL PROTECTED], Roy Sigurd Karlsbakk [EMAIL PROTECTED] wrote: does anyone know if this is/will be supported? I believe it is supported by the em driver, which has been in -current for a few weeks and was recently merged into -stable. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: spam
:I'm starting to get spam since I joined this list, and the spam is :coming from freebsd.org. If I'm reading the headers right, it's coming :in through a freebsd.org mail server. Ha. In the last two weeks the amount of personal spam I receive has gone up exponentially. I'm getting around 60 a day now. I'm not surprised that the list is seeing a big increase. I can only hope that our illustrious congress has grown as tired of spam as I have and will fix the law to simply ban it. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
