Re: -current build fails
On Sun, 31 Oct 1999, David O'Brien wrote: > On Sat, Oct 30, 1999 at 02:43:47PM -0700, Vincent Poy wrote: > > > > Yes, I am still running -current. I read the -current mailing > > list on a more regular basis than most of the people out there. > > By what measure? I think you've shown the opposite. I guess I better say that I'll read the lists more slowly next time. > > I have always read the -current mailing list but you have to > > remember that by the time I do the update, the known problem should > > already have been gone. > > Hum... From E-day and C-day you didn't learn that not all things are > "problems"? I never said they were. > > I did read the UPDATING file and search the list as soon as I posted > > and fixed the problem on my own. I was just worried that rebooting > > with a new kernel before a world build might actually render the system > > bootless. > > Aren't you enough of a FreeBSD sysadmin to know your previous kernel is > available as /kernel.old and that you can specify the kernel used at the > boot prompt? That would work if you were sitting in front of the machines. All my machines are over 500 miles away. Cheers, Vince - [EMAIL PROTECTED] - [EMAIL PROTECTED] __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current build fails
On Sat, Oct 30, 1999 at 02:43:47PM -0700, Vincent Poy wrote: > > Yes, I am still running -current. I read the -current mailing > list on a more regular basis than most of the people out there. By what measure? I think you've shown the opposite. > I have always read the -current mailing list but you have to > remember that by the time I do the update, the known problem should > already have been gone. Hum... From E-day and C-day you didn't learn that not all things are "problems"? > I did read the UPDATING file and search the list as soon as I posted > and fixed the problem on my own. I was just worried that rebooting > with a new kernel before a world build might actually render the system > bootless. Aren't you enough of a FreeBSD sysadmin to know your previous kernel is available as /kernel.old and that you can specify the kernel used at the boot prompt? -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VESA module breaks USB?
On Sun, Oct 31, 1999 at 09:39:33PM -0700, Nick Hibma wrote: > > > ohci0: irq 9 at device 11.0 on pci0 > > > +ohci_waitintr: timeout > > > > IRQ 9 is shared with the VGA controller. Perhaps calling the VESA > > BIOS caused it to do something strange that interfered with the > > delivery of this interrupt on your motherboard. > > No, this has something to do with soft resetting vs. hard > resetting. It might be that this is related to soft rebooting out of > Windows. Try switching off and on your machine. I don't have Windows, but I can try a hard boot at some point and see if it helps. I can also try to fiddle with the IRQs just in case, but they are after all being assigned by FreeBSD. For now I've just turned off VESA, but I think it is going to become non-optional at some point and I'd hate to see my USB go away. -- Christopher Masto Senior Network Monkey NetMonger Communications [EMAIL PROTECTED][EMAIL PROTECTED]http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VESA module breaks USB?
> > ohci0: irq 9 at device 11.0 on pci0 > > +ohci_waitintr: timeout > > IRQ 9 is shared with the VGA controller. Perhaps calling the VESA > BIOS caused it to do something strange that interfered with the > delivery of this interrupt on your motherboard. No, this has something to do with soft resetting vs. hard resetting. It might be that this is related to soft rebooting out of Windows. Try switching off and on your machine. I've seen this before but not yet spent the time to fix it. Nick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linksys LNE100TX
On Thu, 30 Sep 1999, Edwin Culp wrote: > Did it and got these messages: > > mx0: at device 16.0 on pci0 > mx0: couldn't map ports/memory > device_probe_and_attach: mx0 attach returned 6 > > I must be missing something else. Tell your computer you're not using a PnP OS (it's a BIOS thing). Otherwise it won't assign stuff and FreeBSD can't really do much then. - alex Experience something different With our new imported dolly She's lovely, warm, inflatable And we guarantee her joy - The Police To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Strange atapi active state, ending in ATA_IGNORE_INTR?
My box has got three ata disks and one atapi cdrom drive(on secondary slave). Since a few weeks ago the cdrom drive does not get probed. Oct 30 19:31:46 silver /kernel: ata-pci0: at device 4.1 on pci0 Oct 30 19:31:46 silver /kernel: ata-pci0: Busmastering DMA supported Oct 30 19:31:46 silver /kernel: ata0: iobase=0x01f0 altiobase=0x03f6 Oct 30 19:31:46 silver /kernel: ata0: mask=03 status0=50 status1=50 Oct 30 19:31:46 silver /kernel: ata0: mask=03 status0=50 status1=50 Oct 30 19:31:46 silver /kernel: ata0: devices = 0x3 Oct 30 19:31:46 silver /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Oct 30 19:31:46 silver /kernel: ata1: iobase=0x0170 altiobase=0x0376 Oct 30 19:31:46 silver /kernel: ata1: mask=03 status0=50 status1=50 Oct 30 19:31:47 silver /kernel: ata1: mask=03 status0=50 status1=00 Oct 30 19:31:47 silver /kernel: ata1: devices = 0x9 Oct 30 19:31:47 silver /kernel: ata1 at 0x0170 irq 15 on ata-pci0 (snip) Oct 30 19:31:49 silver /kernel: ata0: master: success setting up UDMA2 mode on PIIX4 chip Oct 30 19:31:49 silver /kernel: ad0: piomode=4 dmamode=2 udmamode=2 Oct 30 19:31:49 silver /kernel: ad0: ATA-3 disk at ata0 as master Oct 30 19:31:49 silver /kernel: ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S Oct 30 19:31:49 silver /kernel: ad0: 16 secs/int, 0 depth queue, UDMA33 Oct 30 19:31:49 silver /kernel: Creating DISK ad0 Oct 30 19:31:49 silver /kernel: Creating DISK wd0 Oct 30 19:31:49 silver /kernel: ata0: slave: success setting up UDMA2 mode on PIIX4 chip Oct 30 19:31:49 silver /kernel: ad1: piomode=4 dmamode=2 udmamode=2 Oct 30 19:31:49 silver /kernel: ad1: ATA-4 disk at ata0 as slave Oct 30 19:31:49 silver /kernel: ad1: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S Oct 30 19:31:49 silver /kernel: ad1: 16 secs/int, 0 depth queue, UDMA33 Oct 30 19:31:49 silver /kernel: Creating DISK ad1 Oct 30 19:31:49 silver /kernel: Creating DISK wd1 Oct 30 19:31:49 silver /kernel: ata1: master: success setting up UDMA2 mode on PIIX4 chip Oct 30 19:31:49 silver /kernel: ad2: piomode=4 dmamode=2 udmamode=2 Oct 30 19:31:49 silver /kernel: ad2: ATA-4 disk at ata1 as master Oct 30 19:31:49 silver /kernel: ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S Oct 30 19:31:49 silver /kernel: ad2: 16 secs/int, 0 depth queue, UDMA33 Oct 30 19:31:49 silver /kernel: Creating DISK ad2 Oct 30 19:31:49 silver /kernel: Creating DISK wd2 Oct 30 19:31:49 silver /kernel: DANGER wait_intr active=ATA_IGNORE_INTR The active state after disk probe does not get back to ATA_IDLE, resulting atapi_getparam() to fail on atapi_wait(). Calling atapi_getparam() twice continuously in atapi_attach() helped me, although it is not a proper fix at all. Below is the dmesg. Oct 30 19:36:39 silver /kernel: ata1-slave: piomode=3 dmamode=1 udmamode=-1 dmaflag=1 Oct 30 19:36:39 silver /kernel: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=04 Oct 30 19:36:39 silver /kernel: atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=28 ascq=00 error=04 Oct 30 19:36:39 silver /kernel: acd0: CDROM drive at ata1 as slave Oct 30 19:36:39 silver /kernel: acd0: read 2755KB/s (2755KB/s), 128KB buffer, PIO Oct 30 19:36:39 silver /kernel: acd0: supported read types: CD-DA Oct 30 19:36:39 silver /kernel: acd0: Audio: play, 16 volume levels Oct 30 19:36:39 silver /kernel: acd0: Mechanism: ejectable tray Oct 30 19:36:39 silver /kernel: acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked Seigo Tanimura <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linksys conflicts with NE2000
Today Jonathan M. Bresler wrote: > okay i have changed the order in which we test for NE1000, NE2000, and > the Linksys (dl10016c ? ethernet controller). > > pleazse test and let me know how this patch does. > hopefully the problem will be solved. Works with my NE2000 clone. Thanks Jonathan. -- Jack O'NeillSystems Administrator / Systems Analyst [EMAIL PROTECTED] Crystal Wind Communications, Inc. Finger [EMAIL PROTECTED] for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linksys conflicts with NE2000
Hi, At 10:52 am -0800 31/10/99, Jonathan M. Bresler wrote: >okay i have changed the order in which we test for NE1000, NE2000, and >the Linksys (dl10016c ? ethernet controller). > >pleazse test and let me know how this patch does.[etc] OK the patch fixes the problem here. [Thanks for the context diff] -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ESS sound drivers and 4.0-current
I believe the ESS drivers weren't committed to 4.0-current yet. When I grep ' ESS ' in /sys/i386/isa/sound, the only thing I can come up with is the ESS support that was in the old voxware sound code. Sanpei, who is developing the ESS sound drivers, says they were committed to the newpcm drivers. I believe they were not added yet. >From http://home.jp.freebsd.org/~sanpei/: tarball for 4-current --> our ESS(ISA) code was commited to newpcm driver in 4.0-current(1999/09/04) - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linksys conflicts with NE2000
On Sun, 31 Oct 1999, Jonathan M. Bresler wrote: > > okay i have changed the order in which we test for NE1000, NE2000, and > the Linksys (dl10016c ? ethernet controller). > > pleazse test and let me know how this patch does. > hopefully the problem will be solved. > I tried it, I could boot, and I'm doing a installworld over nfs as I write this. Thanks, now I can continue my plans for letting the isdncard reject calls from callers hiding their CLID... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Discussions starting on -arch.
p.s. this should not be in -current but in -arch On Sun, 31 Oct 1999, Julian Elischer wrote: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Discussions starting on -arch.
yes it is a possibility.. see terry's thread model (coming up soon). (at least lurk) On Sun, 31 Oct 1999, Amancio Hasty wrote: > > I am not that really interested on threads.. > > > Is there a possibility of having an async call gate for which the kernel > can do the scheduling whether be for a uni processor or a multi processor > enviroment. > > > -- > > Amancio Hasty > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sv: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot)
> > > > > The LinkSys probe code (in particular the checksum at the start of > > ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine > > up. I guess you have the same problem. > > > > ouch! not goodwhat is the ethernet address of your ne2000 > clone? ed0 at port 0x340-0x35f iomem 0xd8000 irq 10 on isa0 ed0: address 00:80:c8:18:9c:c2, type NE2000 (16 bit) leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Discussions starting on -arch.
I am not that really interested on threads.. Is there a possibility of having an async call gate for which the kernel can do the scheduling whether be for a uni processor or a multi processor enviroment. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sv: copy-on-write optimized faults
On Sun, 31 Oct 1999, Louis A. Mamakos wrote: > And my mine... I get zero COW optimized faults. THE E-MAIL EXPLICITLY SAID ONLY TO POST IF YOU HAVE MORE THEN 0 FAULTS I hope one day the people who don't read this list carefully miss something really important and it eats your system as a result. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Discussions starting on -arch.
I am going to try host the following discussions on -arch over the next week. 1/ which direction (maybe multiple) are we going with threads. 2/ SMP. how to go about it from here.. 3/ In what ways should the VFS and the filesystems be changed/cleaned-up 4/ what about posix extensions such as scheduler classes... I will be doing them SERIALLY, by which I mean that While talking about #1 we don't wander off into #2 unless it directly affects #1. I will try add 'reminders of upcoming topics' regularly so people can hold off, knowing that their topic is on the way.. The first discussion will be on THREADS. A hot topic these days. and I will be posting a stating note on the topic in a short while.. If you are not on Arch, or think you are but don't get a small note from me om it (similar to this one) in a short time, then subscribe by: echo "subscribe FreeBSD-arch" |mail [EMAIL PROTECTED] should do it. This note will not be reposted on -current. julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI CD errors
In message <[EMAIL PROTECTED]>, Brian Fun dakowski Feldman wrote: >Have you either tried disabling DMA on the drive? This is easily achieved >by the following (whitespace mangled): > >--- atapi-all.c 1999/10/10 18:08:38 1.19 >+++ atapi-all.c 1999/10/23 16:51:12 >@@ -135,7 +135,8 @@ > udmamode(atp->atapi_parm), > atp->atapi_parm->dmaflag); >- if (!(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && >+ if (atp->atapi_parm->device_type != ATAPI_TYPE_CDROM && >+ !(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && >!ata_dmainit(atp->controller, atp->unit, > (apiomode(atp->atapi_parm) < 0) ? > (atp->atapi_parm->dmaflag ? 4 : 0) : > This patch allows me to mount the cdrom... The probes show PIO mode i.s.o. DMA. So it looks like DMA is broken for this drive.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Linksys conflicts with NE2000
okay i have changed the order in which we test for NE1000, NE2000, and
the Linksys (dl10016c ? ethernet controller).
pleazse test and let me know how this patch does.
hopefully the problem will be solved.
does *ANYONE* have an NE1000, the can test?
before adding in teh Linksys we tested: NE1000 then NE2000.
NE1000 worked
NE2000 worked
Linksys we mistaken for an NE1000
after adding the Linksys we tested: Linksys, NE1000, NE2000.
NE1000 worked (?? no reports for failure ??)
NE2000 failed
Linksys worked
try the patch in http://www.freebsd.org/~jmb/if_ed.c.patch
the order there is:
if (NE1000-like)
test Linksys, test NE1000
else test for NE2000
else
unknown
return ENXIO
jmb
ps. not crazy about the form of the code
if () {
} else {
if () {
} else {
}
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: /usr/share/calendar/calendar.freebsd ?
According to Satoshi - Ports Wraith - Asami: > let her commit things. Ok, not without me watching over her shoulder Experience shows that even this is not enough to prevent accidents (Hi Greg!). :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep 9 00:20:51 CEST 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot)
I also get this lock up on a machine with a ISA NE2000 clone: ed0 at 0x300-0x31f irq 9 on isa ed0: address 00:40:33:23:6b:c1, type NE2000 (16 bit) I have every other NIC driver removed, but a -CURRENT kernel with ed0 enabled on it will cause it to lock hard. Disabling the device in the kernel config will let me boot. On Sun, 31 Oct 1999, Bob Bishop wrote: > >> The LinkSys probe code (in particular the checksum at the start of > >> ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine > >> up. I guess you have the same problem. > >> > > > > ouch! not goodwhat is the ethernet address of your ne2000 > >clone? > > ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 > ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot)
On Sun, Oct 31, 1999 at 05:55:56PM +0100, Kjetil Svenheim wrote: > I have the same problem with my NE2000 clone, so for now I have to use > an old kernel that I made 2 weeks ago. > > My NE2000-clone uses port 300, irq 11 > > > Yes, I added a return(0) at the beginning of ed_get_linksys(); and now I'm > > up. But now is the question how to fix if_ed permanently... Perhaps a > > reordering could help. If ed_get_linksys was called later than my card was > > detected... > > Ehm, if I was to do this to fix the problem, what file would I edit? > > And yeah, I am interested in a permanent solution as well. :) /sys/dev/ed/if_ed.c:902. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot)
I have the same problem with my NE2000 clone, so for now I have to use an old kernel that I made 2 weeks ago. My NE2000-clone uses port 300, irq 11 > Yes, I added a return(0) at the beginning of ed_get_linksys(); and now I'm > up. But now is the question how to fix if_ed permanently... Perhaps a > reordering could help. If ed_get_linksys was called later than my card was > detected... Ehm, if I was to do this to fix the problem, what file would I edit? And yeah, I am interested in a permanent solution as well. :) - Kjetil Svenheim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI CD errors
It seems Doug Rabson wrote: > On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote: > > > Have you either tried disabling DMA on the drive? This is easily achieved > > by the following (whitespace mangled): > > I'll try it on Monday. Hmm, as well as DMA might be the reason, it only applies to reads/writes all other communication with the drive is non-DMA. So if the drive doesn't even probe right, there are other reasons -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI CD errors
On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote: > Have you either tried disabling DMA on the drive? This is easily achieved > by the following (whitespace mangled): I'll try it on Monday. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATAPI tape drive not probed
I've had an ATAPI CDROM as master and an HP Colorado tape as slave set up on my system for quite some time now. I recently migrated to 4.0 and I'm using the new ATA drivers. Below is a snip from my kernel config: controller ata0 device atadisk0 device atapicd0 device atapist0 At boot time, the messages show that there are two devices on the channel, but only the CDROM is configured. Any ideas? ata0: Aladdin: two atapi devices on this channel, DMA disabled atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata0 as master acd0: read 687KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED] Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI CD errors
Have you either tried disabling DMA on the drive? This is easily achieved by the following (whitespace mangled): --- atapi-all.c 1999/10/10 18:08:38 1.19 +++ atapi-all.c 1999/10/23 16:51:12 @@ -135,7 +135,8 @@ udmamode(atp->atapi_parm), atp->atapi_parm->dmaflag); - if (!(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && + if (atp->atapi_parm->device_type != ATAPI_TYPE_CDROM && + !(atp->atapi_parm->drqtype == ATAPI_DRQT_INTR) && !ata_dmainit(atp->controller, atp->unit, (apiomode(atp->atapi_parm) < 0) ? (atp->atapi_parm->dmaflag ? 4 : 0) : -- 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: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot)
Hi, At 7:03 am -0800 31/10/99, Jonathan M. Bresler wrote: >> >> The LinkSys probe code (in particular the checksum at the start of >> ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine >> up. I guess you have the same problem. >> > > ouch! not goodwhat is the ethernet address of your ne2000 >clone? ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sv: copy-on-write optimized faults
And my mine... I get zero COW optimized faults. louie@whizzo[20] $ vmstat -s 47312081 cpu context switches 89421468 device interrupts 30438305 software interrupts 16214761 traps 244593116 system calls 1546 swap pager pageins 5124 swap pager pages paged in 4185 swap pager pageouts 22164 swap pager pages paged out 13486 vnode pager pageins 86761 vnode pager pages paged in 217 vnode pager pageouts 217 vnode pager pages paged out 1151 page daemon wakeups 7505975 pages examined by the page daemon 23256 pages reactivated 663440 copy-on-write faults 0 copy-on-write optimized faults 7306697 zero fill pages zeroed 4185272 zero fill pages prezeroed 1801 intransit blocking page faults 8604076 total VM faults taken 8804200 pages freed 20 pages freed by daemon 2300440 pages freed by exiting processes 16937 pages active 6580 pages inactive 1268 pages in VM cache 6594 pages wired down 245 pages free 4096 bytes per page 20885389 total name lookups cache hits (84% pos + 0% neg) system 4% per-directory deletions 0%, falsehits 0%, toolong 0% louie@whizzo[21] $ uname -a FreeBSD whizzo.transsys.com 4.0-CURRENT FreeBSD 4.0-CURRENT #8: Tue Oct 26 22:55:45 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/WHIZZO i386 louie@whizzo[22] $ uptime 10:06AM up 4 days, 10:17, 0 users, load averages: 0.04, 0.03, 0.00 louie@whizzo[23] $ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot)
> > The LinkSys probe code (in particular the checksum at the start of > ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine > up. I guess you have the same problem. > ouch! not goodwhat is the ethernet address of your ne2000 clone? jmb To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot)
Hi, At 2:56 pm +0100 31/10/99, Leif Neland wrote: >[...]If ed_get_linksys was called later than my card was >detected... I guess it's an ordering thing, but I don't have a LinkSys card here for testing. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot)
On Sun, 31 Oct 1999, Bob Bishop wrote: > Hi, > > At 12:33 pm +0100 31/10/99, Leif Neland wrote: > >current, cvsupped around 3:00 GMT 31 oct. > > > >When trying to boot a new kernel, the machine simply hangs. > >I have narrowed it down to ed0[etc] > > The LinkSys probe code (in particular the checksum at the start of > ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine > up. I guess you have the same problem. > Yes, I added a return(0) at the beginning of ed_get_linksys(); and now I'm up. But now is the question how to fix if_ed permanently... Perhaps a reordering could help. If ed_get_linksys was called later than my card was detected... My card is a dlink 250. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/share/calendar/calendar.freebsd ?
[Redirecting to -chat] On Sun, Oct 31, 1999 at 02:05:14AM -0700, fifi -- hamster of Satoshi wrote: > * From: Brian Fundakowski Feldman <[EMAIL PROTECTED]> > > * Cool idea! Let's just limit it to the committer birthdays and not > * pets' birthdays too (sorry Asami's hamster and Jordan's cats, but it > > Why not? Discrimination! I've committed things too! Isn't this a breach of some "You shall not share your account and password with anyone else rule?" If it isn't, it should be :-) N -- A different "distribution" of Linux is really a different operating system. They just refuse to call it that because it's bad press. But that's what the shoe fits. -- Tom Christiansen, <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current build fails
Vincent Poy wrote: > I have always read the -current mailing list but you have to > remember that by the time I do the update, the known problem should > already have been gone. I assume you have a lousy way of expressing yourself (in this case) and that you don't actually mean what you wrote... -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI CD errors
In message <[EMAIL PROTECTED]>, Paul van der Zwan wrote: > >I switched to the 'new' atapi driver and I am having trouble with my cdrom >which worked fine using the old wd driver. > >I have the following in my config file : > >controller ata0 >device atadisk0 >device atapicd0 > >The device exists: >$ ls -l /dev/acd0* >brw-r- 1 root operator 31, 0 Oct 31 11:06 /dev/acd0a >brw-r- 1 root operator 31, 2 Oct 31 11:06 /dev/acd0c > >Booting gives the following : >ad0: ATA-3 disk at ata0 as master >ad0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S >ad0: 16 secs/int, 0 depth queue, UDMA33 >Creating DISK ad0 >Creating DISK wd0 >atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 >acd0: CDROM drive at ata0 as slave >acd0: read 171KB/s (4125KB/s), 128KB buffer, UDMA33 >acd0: supported read types: CD-DA >acd0: Audio: play, 255 volume levels >acd0: Mechanism: ejectable tray >acd0: Medium: no/blank disc inside, unlocked > >But when I try to mount the CD I get the following error : >atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00 >atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00 > >Anybody any idea or hint ?? I hate to followup on my own messages , but I made a 'small' error. The message above was cause by an empty drive ( wrong PC ;-() The real message I get is : $ sudo mount /cdrom cd9660: Operation not permitted And dmesg gives the following: atapi: PREVENT_ALLOW - UNIT ATTENTION skey=6 asc=28 ascq=00 error=08 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 atapi: READ_BIG - NO SENSE skey=0 asc=00 ascq=00 error=01 BTW this is on a -current cvsupped and built last night. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LinkSys probe locks up some NE2000 clones (was: ed0 hangs at boot)
Hi, At 12:33 pm +0100 31/10/99, Leif Neland wrote: >current, cvsupped around 3:00 GMT 31 oct. > >When trying to boot a new kernel, the machine simply hangs. >I have narrowed it down to ed0[etc] The LinkSys probe code (in particular the checksum at the start of ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine up. I guess you have the same problem. -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/share/calendar/calendar.freebsd ?
* From: [EMAIL PROTECTED] (fifi -- hamster of Satoshi) * Why not? Discrimination! I've committed things too! * * -fifi Oops, I left the cage door open! Sorry folks! No, I honestly have no idea what fifi was talking about. I've never let her commit things. Ok, not without me watching over her shoulder Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sv: copy-on-write optimized faults
[EMAIL PROTECTED] wrote: > > > I get high numbers too: > > > > FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun > > Jun 13 20:31:43 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys > > /compile/mailtoaster1 i386 > > Read the original message. It says: > > > > I would appreciate it if people running -current would run a "vmstat -s" > > Notice "people running -current". The numbers for people running -stable > are not interesting. Sorry, I got it too late... Here comes my -current vmstat -s: FreeBSD opi.flirtbox.ch 4.0-CURRENT FreeBSD 4.0-CURRENT #25: Fri Oct 15 18:51:55 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/opi i386 2276542 cpu context switches 190670731 device interrupts 842992 software interrupts 2635334 traps 17743991 system calls 16 swap pager pageins 20 swap pager pages paged in 10 swap pager pageouts 14 swap pager pages paged out 3900 vnode pager pageins 14335 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 345 page daemon wakeups 137481 pages examined by the page daemon 7730 pages reactivated 867915 copy-on-write faults 0 copy-on-write optimized faults 1295449 zero fill pages zeroed 1106142 zero fill pages prezeroed 56 intransit blocking page faults 2560858 total VM faults taken 2706144 pages freed 2 pages freed by daemon 1819076 pages freed by exiting processes 1773 pages active 3016 pages inactive 501 pages in VM cache 1903 pages wired down 268 pages free 4096 bytes per page 5426026 total name lookups cache hits (54% pos + 4% neg) system 18% per-directory deletions 0%, falsehits 0%, toolong 0% -- Andre To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ed0 hangs at boot.
current, cvsupped around 3:00 GMT 31 oct. When trying to boot a new kernel, the machine simply hangs. I have narrowed it down to ed0, by removing other devices with visual config at boot. However, nothing is shown regarding ed0, so the hang probably occurs early in the probing. Therefore I see no reason to type a dmesg from the hang; but I enclose a normal dmesg.boot with the old kernel. I have my ed0 at a non-standard 0x340. The hang happens both with my custom kernel with this adress, and with a generic kernel, with this adress changed at visual config. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Sun Jul 18 12:00:53 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ARNOLD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P5 (59.97-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x515 Stepping = 5 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 6336 (60764K bytes) Preloaded elf kernel "kernel" at 0xc02c2000. Intel Pentium detected, installing workaround for F00F bug Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 ncr0: irq 11 at device 1.0 on pci0 isab0: at device 2.0 on pci0 vga-pci0: at device 6.0 on pci0 isa0: on motherboard ed0 at port 0x340-0x35f irq 10 on isa0 ed0: address 00:80:c8:18:9c:c2, type NE2000 (16 bit) atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA (mono) <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16450 sio2: configured irq 5 not in bitmap of probed irqs 0 sio3: configured irq 9 not in bitmap of probed irqs 0 ppc0 at port 0x378-0x37f on isa0 ppc0: PC87332 chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 ppi0: on ppbus 0 ppc1 at port 0x278-0x27f irq 5 on isa0 ppc1: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt1: on ppbus 1 lpt1: Interrupt-driven port ppi1: on ppbus 1 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver Waiting 5 seconds for SCSI devices to settle da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) changing root device to da0s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [88765 x 2048 byte records] machine i386 cpu I586_CPU ident ARNOLD maxusers32 options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor controller isa0 controller pnp0# PnP support for ISA controller eisa0 controller pci0 controller ncr0 controller scbus0 device da0 #Only need one of these, the code dynamically grows device pass0 device cd0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? conflicts pseudo-device splash device sc0 at isa? device npx0at nexus? port IO_NPX irq 13 device apm0at nexus? disable flags 0x31 # Advanced Power Management device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device sio2at isa? port IO_COM3 irq 5 device sio3at isa? port IO_COM4 irq 9 device ed0 at isa? port 0x340 irq 10 iomem 0xd8000 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 2 pseudo-device pty 16 pseudo-device gzip# Exec gzipped a.out's options KTRACE #kernel tracing options SYSVSHM options SYSVMSG options SYSVSEM pseudo-de
new kernel, old userland -> signal 12?
I run pre-signal-change-current on my gateway-apache-squid-imap-sendmail-mysql-roxen server and post-signal-change-current on my other box. I have compiled a new kernel on the post-signal-change machine, and installed it (as kernel.new) on the old machine. But I get a panic, trap 12 while in kernel mode after a few minutes. Is this to be expected, and am I just supposed to upgrade userland too, or is it a serious problem which should be solved before I upgrade? I don't want to break this box, as this is my connection to the world... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sv: copy-on-write optimized faults
> I get high numbers too: > > FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun > Jun 13 20:31:43 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys > /compile/mailtoaster1 i386 Read the original message. It says: > > I would appreciate it if people running -current would run a "vmstat -s" Notice "people running -current". The numbers for people running -stable are not interesting. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATAPI CD errors
On Sun, 31 Oct 1999, Paul van der Zwan wrote: > > I switched to the 'new' atapi driver and I am having trouble with my cdrom > which worked fine using the old wd driver. > > I have the following in my config file : > > controller ata0 > device atadisk0 > device atapicd0 > > The device exists: > $ ls -l /dev/acd0* > brw-r- 1 root operator 31, 0 Oct 31 11:06 /dev/acd0a > brw-r- 1 root operator 31, 2 Oct 31 11:06 /dev/acd0c > > Booting gives the following : > ad0: ATA-3 disk at ata0 as master > ad0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue, UDMA33 > Creating DISK ad0 > Creating DISK wd0 > atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 > acd0: CDROM drive at ata0 as slave > acd0: read 171KB/s (4125KB/s), 128KB buffer, UDMA33 > acd0: supported read types: CD-DA > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > > But when I try to mount the CD I get the following error : > atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00 > atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00 > > Anybody any idea or hint ?? I get this on a machine at work which I recently put FreeBSD on. I moved it back to the wdc driver for now. If any extra information would help to debug this, I'm happy to test things. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATAPI CD errors
I switched to the 'new' atapi driver and I am having trouble with my cdrom which worked fine using the old wd driver. I have the following in my config file : controller ata0 device atadisk0 device atapicd0 The device exists: $ ls -l /dev/acd0* brw-r- 1 root operator 31, 0 Oct 31 11:06 /dev/acd0a brw-r- 1 root operator 31, 2 Oct 31 11:06 /dev/acd0c Booting gives the following : ad0: ATA-3 disk at ata0 as master ad0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata0 as slave acd0: read 171KB/s (4125KB/s), 128KB buffer, UDMA33 acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked But when I try to mount the CD I get the following error : atapi: TEST_UNIT_READY - NOT READY skey=2 asc=3a ascq=00 error=00 atapi: READ_TOC - NOT READY skey=2 asc=3a ascq=00 error=00 Anybody any idea or hint ?? TIA Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sv: copy-on-write optimized faults
Leif Neland wrote: > > > I would appreciate it if people running -current would run a "vmstat -s" > > and tell me if they see a NON-ZERO value for copy-on-write optimized > > faults. About six months ago, I implemented a simpler and more general > > optimization at an earlier "fork in the road". (In effect, I avoid > > the creation of the redundant vm object that "copy-on-write > > optimized faults" applies to.) > > > FreeBSD ns.internet.dk 3.3-STABLE FreeBSD 3.3-STABLE #6: Fri Oct 1 16:06:46 CEST >1999 [EMAIL PROTECTED]:/usr/src/sys/compile/DK i386 > > 9272885 copy-on-write faults > 2062637 copy-on-write optimized faults < > I must have something configured wrong, or??? I get high numbers too: FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun Jun 13 20:31:43 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys /compile/mailtoaster1 i386 11:40AM up 137 days, 23:26, 1 user, load averages: 0.00, 0.00, 0.00 64598649 cpu context switches 2745071057 device interrupts 32328669 software interrupts 43110463 traps 296791454 system calls 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 22418 vnode pager pageins 46048 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 122 page daemon wakeups 188111 pages examined by the page daemon 2100 pages reactivated 10358286 copy-on-write faults 693663 copy-on-write optimized faults 20699423 zero fill pages zeroed 15663587 zero fill pages prezeroed 252 intransit blocking page faults 41725673 total VM faults taken 43325585 pages freed 112 pages freed by daemon 25621561 pages freed by exiting processes 17199 pages active 35325 pages inactive 1922 pages in VM cache 8481 pages wired down 1067 pages free 4096 bytes per page 85804588 total name lookups cache hits (67% pos + 5% neg) system 7% per-directory deletions 1%, falsehits 0%, toolong 0% FreeBSD proxy.pipeline.ch 3.3-STABLE FreeBSD 3.3-STABLE #3: Fri Oct 8 11:08:16 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ proxy i386 11:38AM up 22 days, 14:59, 2 users, load averages: 0.00, 0.00, 0.00 16661677 cpu context switches 46793 device interrupts 12164983 software interrupts 11257840 traps 120776685 system calls 6941 swap pager pageins 7483 swap pager pages paged in 725 swap pager pageouts 2821 swap pager pages paged out 4196 vnode pager pageins 12204 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 1885 page daemon wakeups 457 pages examined by the page daemon 4850 pages reactivated 449499 copy-on-write faults 30784 copy-on-write optimized faults 555925 zero fill pages zeroed 312825 zero fill pages prezeroed 576 intransit blocking page faults 1619807 total VM faults taken 1826533 pages freed 1817 pages freed by daemon 703761 pages freed by exiting processes 22101 pages active 2977 pages inactive 1520 pages in VM cache 4868 pages wired down 224 pages free 4096 bytes per page 18695799 total name lookups cache hits (51% pos + 4% neg) system 31% per-directory deletions 0%, falsehits 0%, toolong 0% -- Andre To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/share/calendar/calendar.freebsd ?
* From: Brian Fundakowski Feldman <[EMAIL PROTECTED]> * Cool idea! Let's just limit it to the committer birthdays and not * pets' birthdays too (sorry Asami's hamster and Jordan's cats, but it Why not? Discrimination! I've committed things too! -fifi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
