No Subject
OK, I;ve looked and looked and can't seem to figure out how to set hw.ata.wc to enabled. I've put and a few other things in /etc/sysctl.conf, the others get set, hw.ata.wc doesn't. You can't change it by hand either as sysctl tells you it's readonly. Grepping in /sys/i386/conf has turned up nothing and neither has grepping /boot. Have you tried specifying it in /boot/loader.conf ? hw.ata.wc=1 HTH (and have as much fun as possible :-), Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
unsubscribe freebsd-current end To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
i cd rom is locked what can I do instead trying cd until unlocked is there any command to do ?
No Subject
No Subject
subscribe freebsd-current subscribe cvs-all -- Pascal Filipovicz --- IUT 'A' Nancy-Verdun - S.C.I. 2ter, bd Charlemagne CS 5227 54000 Nancy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Title: subscribe freebsd-stable
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
unsubscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
unsubscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (no subject)
On Mon, Mar 05, 2001 at 11:27:24AM +0530, some SMTP stream spewed forth: unsubscribe freebsd-current You need to send messages like this to [EMAIL PROTECTED] By the way, we tell you this at the bottom of every mail from the list. ;-) dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
unsubscribe freebsd-current unsubscribe freebsd-security unsubscribe freebsd-stable To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe
No Subject
Title: 8 You are invited to become a VIP member of www.eVIPlist.com, the Robb Report of urban events. Where membership certainly has it's privileges. This exclusive list is opt-in only and you will not receive any further correspondence from eVIPlist.com if you do not register. At www.eVIPlist.com you can find the hottest parties and special events going on in your city and around country. This week we have a special feature on the hottest parties and special events at NBA All-Star Weekend 2001 in Washington, DC. In addition we offer you news, reviews and interviews on some of the biggest movers and shakers in urban America. If you enjoy www.eVIPlist.com please feel free to forward the site to all co-workers, family, frats/soros and friends. Thank you for your time. Respectfully yours, eVIPlist Staff [EMAIL PROTECTED] "Providing progressive entertainment for progressive people To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscrive [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Here's a report, that you may ignore if needed... I'm building news machines with two partitions for OSen, to allow me to boot into my choice, where my choice has been FreeBSD-STABLE or FreeBSD-CURRENT to see how the two compare, and if there are any significant improvements in -CURRENT. I know, ``don't do that'' but hey... Anyway, using the performance with -STABLE as a reference on this system with currently a single CPU, I built a freshly cvsup'ed -CURRENT just under 24 hours ago and then ran it in production for about ten hours before reverting back to -STABLE. First of all, after building a custom kernel and mounting several disks with softupdates, I then gave a command to cp -pR /news/dir to /news/FreeBSD-STABLE-dir , where the /news disk is mounted with both softupdates and noatime. Quickly I got a panic: ffs_valloc: dup alloc and everything froze solid. I didn't attempt to repeat this to see if it is repeatable. I disabled the softupdates, remounted the disk (just noatime) and again gave the cp -pR command, which succeesed. In fact, for the next ten hours, I attempted to pump a full newsfeed through this machine with no problems and stable operation. A few other drives are mounted with both noatime and softupdates, but without the file creation activity one gets with the command I gave. Also, I was sort of running low on inodes, although I never actually ran out, if that would make any difference. Now, as far as performance goes, after running for ten hours and getting a feel for how well it was doing, I rebooted back into -STABLE and restarted things. However, I see a huge performance increase with -STABLE compared to -CURRENT. That is, I'm able to take in many more times the number of articles with -STABLE than the machine running -CURRENT could handle. Like by a factor of ten. Basically, apart from the current/stable switch, the machine is identical in both OSen, and there shoulr be no difference in the news software proper. The kernel configs should be comparable too. Yeah, I know, -current is in a state of transition, but I didn't expect its performance to be quite *this* bad... These are just some observations, in the hope they might be useful. thanks, barry bouwsma, putting hardware to waste since 1997 (use reply-to header if this message is worthy of comment best kept off the list) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Doug Barton wrote:
: Pending Mark's approval, I'd like to suggest we add a cron job to
: dump X k of data from /dev/random to a file (/boot/.periodic_entropy
: maybe?) and use that, AND ${entropy_file:/var/db/entropy} to reseed at
: boot, and only do the "long, annoying" failover process if neither file
: exists. The only remaining questions would be how many k of data to dump
: how often.
How about skipping the "long, annoying failover process" altogether and
simply logging to the console that the entropy reseeding process was
incomplete? Forcing an indeterminate delay to gather entropy is more
than a little paternalistic.
I've little doubt of /dev/random's theoretical soundness. But a
theoretical boost in security won't justify an actual reduction in
availability to many folks.
-Ed
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
No Subject
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe
(no subject)
unsubscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe [EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
GET YOUR OWN 100 MEG WEBSITE FOR ONLY $11.95 PER MONTH TODAY! STOP PAYING $19.95 or more TODAY for your web site, WHEN YOU CAN GET ONE FOR ONLY $11.95 PER MONTH! DO YOU ALREADY HAVE A WEBSITE? ALL YOU HAVE TO DO IS TRANSFER THE DOMAIN TO OUR SERVERS AND UPLOAD YOUR DATA AND YOU ARE READY TO GO! YOUR NEW WEB SPACE CAN BE CREATED INSTANTLY WITH JUST A SIMPLE PHONE CALL TO OUR OFFICE. YOU CAN CHANGE THE DESIGN OF YOUR SITE AS MUCH AS YOU WANT with no extra charge! UNLIMITED TRAFFIC -- no extra charge! FRONT PAGE EXTENSIONS are FULLY SUPPORTED. A SET UP FEE OF $40.00 APPLIES for FIRST TIME CUSTOMERS. ALL FEES PREPAID IN ADVANCE FOR THE YEAR PLUS A $40.00 SET UP CHARGE. FOR DETAILS CALL 1 888 248 0765 Webhosting International To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current
No Subject
suscribe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Justin Ovens ([EMAIL PROTECTED]) System/Network Administrator http://www.lostworld.net http://resume.lostworld.net -- Personal Resume. "I dread success. To have succeeded is to have finished one's business on earth, like the male spider, who is killed by the female the moment he has succeeded in his courtship. I like a state of continual becoming, with a goal in front and not behind." "Every time I think I know where it's at, they move it." -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Dear Sirs, JOINT VENTURE OPPORTUNITY INFOPAC Software (India) is interested in a business relationship with your company in the area of ERP / software projects and solutions: Our capability profile includes: Software projects (offshore / onshore development) ERP development Internet, e-commerce based development Manpower services Wet lease / incubation service for projects We are visiting your country shortly and would like to meet you to discuss the opportunity further. We are a 55 people company specializing in ERP and E Commerce. Please do visit our web site www.infopac-erp.com Looking forward to hearing from you, Yours Sincerely, for INFOPAC SOFTWARE LTD Ms.Bhagya Nair Intl. Business Division Infopac Software Limited, No.67, Rustam Bagh, Bangalore-560017, India, Ph:+91-80-5250767/5255461 Fax:+91-80-5262180, E mail: [EMAIL PROTECTED]
No Subject
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Not sure if this is related to the recent commit of DEVFS code, but a build of both the GERNERIC kernel and a custom kernel from a very recent (last few hours) cvsup of -current failed during the 'make depend' with an error trying to include "opt_devfs.h". The following following is the ouput from a custom kernel (/usr/local/src/freebsd/src is the base of my src): === md @ - /usr/local/src/freebsd/src/sys machine - /usr/local/src/freebsd/src/sys/i386/include touch opt_mfs.h touch opt_md.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../includ e -I/usr/include /usr/local/src/freebsd/src/sys/modules/md/../../dev/md/md.c /usr/local/src/freebsd/src/sys/modules/md/../../dev/md/md.c:15: opt_devfs.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/local/src/freebsd/src/sys/modules/md. *** Error code 1 Commenting out the line: #include "opt_devfs.h" from src/sys/dev/md/md.c got rid of this error, although I am not sure that this is the correct fix. Tony. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth 76254f08 unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth 0ad9305e unsubscribe freebsd-current [EMAIL PROTECTED]
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
unsubscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
ab 15.6.2000 auf CD-ROM: blackbook 2000 ch - die 1.Datenbank zum leichten und umfassenden Aufbau von** Newslettern** Kundeninformationsbriefen** Produktankuendigungen** Marketingaktionen** Offerten einholen/stellen** konzipiert für den Business to Business-Einsatz Schweiz- die Informationsdatenbank mit+ 450'000 Business-Emails der Schweiz+ 170'000 Business-Websites der Schweiz (Registrar, weitere Domains des Registrars, Kontaktinfo)+ 160'000 Kontaktadressen mit Telefon, Fax, Homepage, Email, Beruf- Suchmoeglichkeiten Homepage/Adressen nach Kanton - Beruf - Stichworten Alle Daten exportierbar in Outlook 2000 oder Textfiles zur Weiterverarbeitung.Eigene Daten importieren aus Outlook 2000 oder Textfiles. Backup/Restore eigener Daten.Lieferumfang:Datenbankprogramm - "How to's" - Groupmailprogramme - Internetmetasearchengine.(10'000 CD's zum Preis von jeweils SFr. 194.-- inklusive Porto und NN, anschliessend SFr. 364.-- --- dieses Einführungsangebot gilt nurin der Schweiz und fuer die ersten 10'000 CD's)More infos and order online onwww.eurodirector.com www.carfashop.com www.eu-sales.comwww.iq-u.com See you there!
No Subject
No Subject
auth f28c66a8 subscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth b614398f subscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Subject: Re: high CPU usage by xmms
Ok, I have some *gasp* actual usefull info about this. Backing /src/sys/dev/sound up by 10 days via anoncvs makes the "feature" go away. That narrows it down to kernel issues. I'm in the process of narowing it down to the specific diff, but if I had to cast a bet, i'd go for the massive change to pcm/dsp.c on the 23rd. More to come. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth 6df833c4 unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current -- - G Douglas Davidson | CityNet, Inc. [EMAIL PROTECTED]| Pittsburgh, PA voice: 412.481.5406 | fax: 412.431.1315 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
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
No Subject
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
No Subject
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 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
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
No Subject
subscribe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
This error occured during "make installworld" on a 5.0 Current systemscvsuped from late afternoon Saturday March 18. ln -s curses.h /usr/include/ncurses.h 1 error *** Error code 2 1 error
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
I notice someone posted this the other day Never have not seen a response...so...this is 5.0 CURRENT make world from cvsup March 15. ys/boot/i386/libi386/biosdisk.c -o biosdisk.o/usr/src/sys/boot/i386/libi386/biosdisk.c: In function `bd_print':/usr/src/sys/boot/i386/libi386/biosdisk.c:242: syntax error before `,'/usr/src/sys/boot/i386/libi386/biosdisk.c:289: case label not within a switch statement/usr/src/sys/boot/i386/libi386/biosdisk.c:293: default label not within a switchstatement/usr/src/sys/boot/i386/libi386/biosdisk.c: At top level:/usr/src/sys/boot/i386/libi386/biosdisk.c:301: syntax error before `}'/usr/src/sys/boot/i386/libi386/biosdisk.c:103: warning: `bd_printslice' used butnever defined/usr/src/sys/boot/i386/libi386/biosdisk.c:106: warning: `bd_strategy' used but never defined/usr/src/sys/boot/i386/libi386/biosdisk.c:108: warning: `bd_open' used but neverdefined/usr/src/sys/boot/i386/libi386/biosdisk.c:109: warning: `bd_close' used but never defined/usr/src/sys/boot/i386/libi386/biosdisk.c:103: warning: `bd_printslice' used butnever defined/usr/src/sys/boot/i386/libi386/biosdisk.c:106: warning: `bd_strategy' used but never defined/usr/src/sys/boot/i386/libi386/biosdisk.c:108: warning: `bd_open' used but neverdefined/usr/src/sys/boot/i386/libi386/biosdisk.c:109: warning: `bd_close' used but never defined/usr/src/sys/boot/i386/libi386/biosdisk.c:123: warning: `bd_opendisk' used but never defined/usr/src/sys/boot/i386/libi386/biosdisk.c:124: warning: `bd_closedStop in /usr/src/sys/boot/i386.*** Error code 1Stop in /usr/src/sys/boot.*** Error code 1Stop in /usr/src/sys.*** Error code 1Stop in /usr/src.*** Error code 1Stop in /usr/src.*** Error code 1Stop in /usr/src.
No Subject
I notice someone posted this the other day Never have not seen a = response...so...this is 5.0 CURRENT make world from cvsup March 15. Hi, Please check your version of /usr/src/sys/boot/i386/libi386/biosdisk.c. This was fixed yesterday. welpje:[sys/boot/i386/libi386] % grep '$FreeBSD:' biosdisk.c * $FreeBSD: src/sys/boot/i386/libi386/biosdisk.c,v 1.28 2000/03/15 16:36:55 jhb Exp $ - marcel ys/boot/i386/libi386/biosdisk.c -o biosdisk.o /usr/src/sys/boot/i386/libi386/biosdisk.c: In function `bd_print': /usr/src/sys/boot/i386/libi386/biosdisk.c:242: syntax error before `,' /usr/src/sys/boot/i386/libi386/biosdisk.c:289: case label not within a = switch st atement /usr/src/sys/boot/i386/libi386/biosdisk.c:293: default label not within = a switch statement /usr/src/sys/boot/i386/libi386/biosdisk.c: At top level: /usr/src/sys/boot/i386/libi386/biosdisk.c:301: syntax error before `}' /usr/src/sys/boot/i386/libi386/biosdisk.c:103: warning: `bd_printslice' = used but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:106: warning: `bd_strategy' = used but n ever defined /usr/src/sys/boot/i386/libi386/biosdisk.c:108: warning: `bd_open' used = but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:109: warning: `bd_close' used = but neve r defined /usr/src/sys/boot/i386/libi386/biosdisk.c:103: warning: `bd_printslice' = used but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:106: warning: `bd_strategy' = used but n ever defined /usr/src/sys/boot/i386/libi386/biosdisk.c:108: warning: `bd_open' used = but never defined /usr/src/sys/boot/i386/libi386/biosdisk.c:109: warning: `bd_close' used = but neve r defined /usr/src/sys/boot/i386/libi386/biosdisk.c:123: warning: `bd_opendisk' = used but n ever defined /usr/src/sys/boot/i386/libi386/biosdisk.c:124: warning: `bd_closed Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. =20 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
auth e96ad1c2 subscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
auth cdf95649 subscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
But now, I prefer to use pam_ssh.so with wdm. Wdm doesn't support PAM session. So, I merged the code from XFree86-3.3.6 of xdm. Hmmm. I see that /usr/ports/x11/wdm has merged in support for FreeBSD's login classes, but not PAM. Are you planning to merge these changes of yours into the port so that the rest of us can play too? :-) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth ceff744c subscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth 17836b14 unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Return-Path: [EMAIL PROTECTED] Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by tiberius.accn.org (8.9.3/8.9.3) with ESMTP id VAA19104 for [EMAIL PROTECTED]; Sat, 8 Jan 2000 21:30:36 -0500 (EST) Received: by hub.freebsd.org (Postfix, from userid 538) id A62CD151BB; Sat, 8 Jan 2000 18:31:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id D53701CD829; Sat, 8 Jan 2000 18:31:28 -0800 (PST) (envelope-from owner-freebsd-security) Received: by hub.freebsd.org (bulk_mailer v1.12); Sat, 8 Jan 2000 18:31:27 -0800 Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id E6F9515003; Sat, 8 Jan 2000 18:31:20 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Received: from pld ([EMAIL PROTECTED] [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id SAA70561; Sat, 8 Jan 2000 18:31:19 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Subject: RE: load spike strangeness Date: Sat, 8 Jan 2000 18:31:19 -0800 Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: [EMAIL PROTECTED] X-Loop: FreeBSD.org Precedence: bulk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Return-Path: [EMAIL PROTECTED] Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by tiberius.accn.org (8.9.3/8.9.3) with ESMTP id VAA19691 for [EMAIL PROTECTED]; Sat, 8 Jan 2000 21:41:42 -0500 (EST) Received: by hub.freebsd.org (Postfix, from userid 538) id A54E11529C; Sat, 8 Jan 2000 18:41:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id BF8B21CD82C; Sat, 8 Jan 2000 18:41:50 -0800 (PST) (envelope-from owner-freebsd-security) Received: by hub.freebsd.org (bulk_mailer v1.12); Sat, 8 Jan 2000 18:41:49 -0800 Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 721BE14EB3; Sat, 8 Jan 2000 18:41:41 -0800 (PST) (envelope-from [EMAIL PROTECTED]) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA14565; Sat, 8 Jan 2000 18:41:30 -0800 (PST) (envelope-from dillon) Date: Sat, 8 Jan 2000 18:41:30 -0800 (PST) Message-Id: [EMAIL PROTECTED] "freebsd-security@FreeBSD. ORG" [EMAIL PROTECTED] Subject: Re: RE: load spike strangeness References: [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] X-Loop: FreeBSD.org Precedence: bulk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
No Subject
unsubscribe freebsd-current To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
unsubscribe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
No Subject
auth 2583e54c unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
unsubscribe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Whilst on the subject of man pages...
... it looks like only a small subset of the man pages for bind 8.2.2P5 (in /usr/src/contrib) gets installed. In particular, we are missing the man page for nsupdate. Any reasons for not installing the whole bunch, since we do install the binaries? PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
DATA From: [EMAIL PROTECTED] To: Date: Sat, 11 Dec 1999 17:16:58 PST Subject: SKIN BECOMES DRAMATICALLY EVEN-TONED AND CLEAR... SKIN PROBLEMS? LET "DERMACURE" SOLVE THEM! Hello. We have good news for you. "DERMACURE" IS MADE FOR YOUR SKIN. If you suffer from any form of skin discolorations, such as dark marks, acne or pimple marks, scars, under-eye circles, razor bump marks, spots, freckles, uneven skin tone, shaving scars, shavers shadow, stretch-marks, dark areas of skin, or any other skin imperfections, you owe it to yourself to learn more about DERMACURE. Your skin can become dramatically even-toned and clear. "Dermacure" was first created in 1975. It has been thoroughly researched and perfected, has had many case studies conducted and has been improved many times over the past 24 years. This truly remarkable cosmetic treatment will eliminate your skin problems once and for all. "DERMACURE" IS MADE FOR YOUR SKIN. It's formula has been found by The U. S. Food and Drug Administration to be both safe and effective. DERMACURE is just as effective for males as it is for females, and is completely safe and gentle to sensitive skin. Our skin treatments are for all races, shades and ages of skin. If you wish to receive free additional information about "Dermacure", or If you have any questions, please email them to... [EMAIL PROTECTED] We will answer you quickly. ALSO...if you have acne or pimple problems, or blackheads, whiteheads, or shaving bumps on your face or anywhere on your body, email us at [EMAIL PROTECTED]for information about a remarkable acne and pimple Eliminator. ...If you suffer from stretch-marks, please let us know also. We have a stretch mark treatment made for this skin condition. Email us at [EMAIL PROTECTED] ...Do you have psoriasis or eczema? We can help.. email us at [EMAIL PROTECTED] We are an international company. You can be assured of fast, reliable delivery. Our elaborate shipping facilities and expert staff assure you of the highest quality service, whether you are here in the USA, or anywhere in the world. Respectfully and Sincerely, Mrs. Christine Yang, Mrs. Brenda Boykin and Mr. John Shigira P. S. It is never our intention to offend or annoy or disrespect anyone. If you do not appreciate receiving this message, please let us know by simply clicking REPLY and typing the word "REMOVE" IN THE SUBJECT LINE. (Not The Body) You will then be promptly and permanently removed from our list. We humbly apologize if you are in any way offended by receiving this email. " SKIN IS OUR BUSINESS...OUR ONLY BUSINESS". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
DATA From: [EMAIL PROTECTED] To: Date: Thu, 09 Dec 1999 03:20:11 PST Subject: SKIN BECOMES DRAMATICALLY EVEN-TONED AND CLEAR... SKIN PROBLEMS? LET "DERMACURE" SOLVE THEM! Hello. We have good news for you. "DERMACURE" IS MADE FOR YOUR SKIN. If you suffer from any form of skin discolorations, such as dark marks, acne or pimple marks, scars, under-eye circles, razor bump marks, spots, freckles, uneven skin tone, shaving scars, shavers shadow, stretch-marks, dark areas of skin, or any other skin imperfections, you owe it to yourself to learn more about DERMACURE. Your skin can become dramatically even-toned and clear. "Dermacure" was first created in 1975. It has been thoroughly researched and perfected, has had many case studies conducted and has been improved many times over the past 24 years. This truly remarkable cosmetic treatment will eliminate your skin problems once and for all. "DERMACURE" IS MADE FOR YOUR SKIN. It's formula has been found by The U. S. Food and Drug Administration to be both safe and effective. DERMACURE is just as effective for males as it is for females, and is completely safe and gentle to sensitive skin. Our skin treatments are for all races, shades and ages of skin. If you wish to receive free additional information about "Dermacure", or If you have any questions, please email them to... [EMAIL PROTECTED] We will answer you quickly. ALSO...if you have acne or pimple problems, or blackheads, whiteheads, or shaving bumps on your face or anywhere on your body, email us at [EMAIL PROTECTED]for information about a remarkable acne and pimple Eliminator. ...If you suffer from stretch-marks, please let us know also. We have a stretch mark treatment made for this skin condition. Email us at [EMAIL PROTECTED] ...Do you have psoriasis or eczema? We can help.. email us at [EMAIL PROTECTED] We are an international company. You can be assured of fast, reliable delivery. Our elaborate shipping facilities and expert staff assure you of the highest quality service, whether you are here in the USA, or anywhere in the world. Respectfully and Sincerely, Mrs. Christine Yang, Mrs. Brenda Boykin and Mr. John Shigira P. S. It is never our intention to offend or annoy or disrespect anyone. If you do not appreciate receiving this message, please let us know by simply clicking REPLY and typing the word "REMOVE" IN THE SUBJECT LINE. (Not The Body) You will then be promptly and permanently removed from our list. We humbly apologize if you are in any way offended by receiving this email. " SKIN IS OUR BUSINESS...OUR ONLY BUSINESS". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
In message [EMAIL PROTECTED] Nick Hibma writes: : The system freezes on powering down a PCCARD slot. From memory the : location is putb1 called from pcic_disable. The freeze is easy to : reproduce, just remove the card. When stepping through the code, even : the debugger prompt does not return after the outb for PCIC_POWER on : line 698 of pcic.c. My first guess was that the driver was getting interrupts at this point. This is true as far as it goes. This likely means that the driver hasn't detached by this point. You might try looking down that path to see if the device_delete_children is really being called, and if so on what. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
In message [EMAIL PROTECTED] Nick Hibma writes: : pcic: polling, can't alloc 0 : pcic: polling, can't alloc 0 This isn't your problem, but you might want to assign an interrupt line to these devices. Another problem is that I didn't implement the logic in the right way for the nbk. In many places I treat things as having one pccard device, when there is one per child. The pcic should tell the pccard child that an eject/socket power off has occurred and the pccard child should then detach all its children at that point. I was in a hurry and didn't do this like I should have. That might be an easier road to a fix as well. I'm *STILL* waiting for the returned laptop to come back. Grump. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
From some very brief testing here, the problem is that the card's interrupt handler hasn't yet been disconected. When you power the card down, you get an edge on the interrupt pin, and then the driver interrupt handler spins madly because the card hardware is gone and thus doesn't behave. If you have an ethernet card, try suspending with just it in the slot and then break into DDB; I'll warrant that you end up inside the relevant driver's interrupt handler. If I'm correct, this is just an ordering issue; the driver has to be shut down _before_ the slot, not afterwards. The system freezes on powering down a PCCARD slot. From memory the location is putb1 called from pcic_disable. The freeze is easy to reproduce, just remove the card. When stepping through the code, even the debugger prompt does not return after the outb for PCIC_POWER on line 698 of pcic.c. This is on CURRENT as of yesterday evening, but other CURRENTs of the last month have the same problem. I've not been able to find a possible culprit in recent commits to pcic.c or pccard.c. Do you have any hint on how to debug this or what version of pcic.c I should take to get rid of this problem? pcic-pci0: TI PCI-1131 PCI-CardBus Bridge irq 9 at device 19.0 on pci0 pcic-pci1: TI PCI-1131 PCI-CardBus Bridge irq 9 at device 19.1 on pci0 ... pcic: polling, can't alloc 0 pcic: polling, can't alloc 0 pcic0: VLSI 82C146 on isa0 pccard0: PC Card bus -- kludge version on pcic0 pccard1: PC Card bus -- kludge version on pcic0 Thanks for the work being done. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
In message [EMAIL PROTECTED] Mike Smith writes: : If I'm correct, this is just an ordering issue; the driver has to be shut : down _before_ the slot, not afterwards. Right. The code that is doing the shutdown is trying to shutdown the driver, but that doesn't seem to be happening. The other possibility is that it is happening, but the interrupt handler isn't getting removed due to a bug in that code. I sure miss my laptop.. :-. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
No Subject
help subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth a73d5537 unsubscribe freebsd-current [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth 80b21ad8 unsubscribe freebsd-security [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
auth fdfda9f6 unsubscribe freebsd-current [EMAIL PROTECTED] auth 8a3cc747 unsubscribe cvs-all [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
unsubscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
