Ïðåäëàãàþ ðàáîòó â èíòåðíåòå (50000$ çà 3 ìåñÿöà)
Title: ÍÅ ÓÄÀËßÉÒÅ ÝÒÎ, ÎÒÏÅ×ÀÒÀÉÒÅ ÝÒÎ, ÏÐÎ×ÈÒÀÉÒÅ ÝÒÎ ÎÒÏÅ×ÀÒÀÉÒÅ ÝÒÎ, ÏÎÆÀËÓÉÑÒÀ, È ÑÏÎÊÎÉÍÎ ÏÐÎ×ÈÒÀÉÒÅ ! ÂÛ ÇÀÐÀÁÎÒÀÅÒÅ ÌÍÎÃÎ ÄÅÍÅÃ! ÝÒÎÒ ÁÈÇÍÅÑ ÐÀÁÎÒÀÅÒ ÏÐÎÑÒÎ ÂÅËÈÊÎËÅÏÍÎ!!! ß ÐÀÁÎÒÀÞ ÏÎ ÝÒÎÉ ÏÐÎÃÐÀÌÌÅ ÎÄÈÍ - ÄÂÀ ×ÀÑÀ  ÄÅÍÜ, ÂÊËÞ×Àß ÎÁÐÀÁÎÒÊÓ ÇÀÊÀÇÎÂ È ÄÎÐÎÃÓ Â ÁÀÍÊ!!! Íà÷íèòå ðàáîòàòü ñ íàìè è óâèäèòå, ÷òî áóäåòå ðàäû òîìó, ÷òî òàê ñäåëàëè!!! ÇÀÐÀÁÎÒÀÉÒÅ 100.000,- USD ÇÀ ÃÎÄ ÍÀ ÐÅÊËÀÌÅ Â ÈÍÒÅÐÍÅÒÅ È ÐÀÑÑÛËÊÅ E-MAIL!!! Óâàæàåìûå äðóçüÿ è ïîäðóãè, Âû ìîæåòå çàðàáîòàòü 50.000,- USD è áîëüøå â òå÷åíèå ñëåäóþùèõ 90 äíåé íà ðàññûëêå e-mail. ÊÀÆÅÒÑß ÍÅÂÎÇÌÎÆÍÛÌ?? Ïðî÷èòàéòå äåòàëè, â ýòîì íåò íèêàêîé êàâåðçû èëè îáìàíà, ïðîñòî äåëàéòå ñåáå ðåêëàìó â Èíòåðíåò, ðàññûëàéòå e-mail è ðàçìåùàéòå ðåêëàìíûå îáúÿâëåíèÿ, è ÂÛ âñòàíåòå íà ïóòü ê ôèíàíñîâîé íåçàâèñèìîñòè è ÑÂÎÁÎÄÅ!! "AS SEEN ON NATIONAL TELEVISION" Ñïàñèáî çà Âàøå âðåìÿ è èíòåðåñ. Îá ýòîì ïèñüìå íåäàâíî áûëî íàïèñàíî â àìåðèêàíñêèõ ãàçåòàõ. Òàêæå, ââèäó åãî ïîïóëÿðíîñòè â Èíòåðíåòå, ãëàâíàÿ íî÷íàÿ èíôîðìàöèîííàÿ ïðîãðàììà ïîñâåòèëà åìó öåëóþ ïåðåäà÷ó íà îáúÿñíåíèå è âûÿñíåíèå, äåéñòâèòåëüíî ëè íèæå îïèñàííàÿ ïðîãðàììà ìîæåò ïðèíåñòè ëþäÿì äåíüãè. Òàêæå ïðîâåäåíî èññëåäîâàíèå ëåãàëüíîñòè äàííîé ïðîãðàììû.  ðåçóëüòàòå êîòîðîãî, ðàç è íàâñåãäà ïîäòâåðäèëîñü, ÷òî íå íàðóøàþòñÿ íèêàêèå çàêîíû è ïîñòàíîâëåíèÿ. Ýòî ïîìîãëî ïîêàçàòü ëþäÿì, ÷òî ýòî ïðîñòîé, áåçâðåäíûé è èíòåðåñíûé ñïîñîá çàðàáîòêà äåíåã íà äîìó. Âû ïîéìåòå ñóòü, êàê òîëüêî ïðî÷èòàåòå ýòî ðóêîâîäñòâî. Íàïå÷àòàéòå ýòîò äîêóìåíò ñåé÷àñ, äëÿ ïîñëåäóþùåãî ÷òåíèÿ. (Èíôîðìàöèÿ òðåáóåò âíèìàòåëüíîãî ïðî÷òåíèÿ) Ñëåäóþùàÿ âîçìîæíîñòü, ïðèíîñèò äîõîä , è ìîæåò Âàñ çàèíòåðåñîâàòü. Åñòü âîçìîæíîñòü åå íà÷àòü ñ ìèíèìàëüíûìè èíâåñòèöèÿìè, à äîõîä ïðîñòî ÏÎÐÀÇÈÒÅËÜÍÛÉ! Õîòèòå çàðàáîòàòü 50.000,- USD ìåíüøå ÷åì çà 90 äíåé!? Ïîæàëóéñòà, ïðî÷èòàéòå äàííóþ ïðîãðàììó, ñíà÷àëà ÿ ýòîìó òîæå íå âåðèë, îäíàêî ýòî òàê!!! À ïîòîì ïðî÷èòàéòå ýòî ÅÙÅ ÐÀÇ! ÝÒÎ ËÅÃÀËÜÍÀß ÂÎÇÌÎÆÍÎÑÒÜ ÇÀÐÀÁÎÒÀÒÜ ÄÅÍÜÃÈ !!! !!! Ýòî íå òðåáóåò, ÷òîáû âû âñòðå÷àëèñü ñ ëþäüìè (êàê âî ìíîãèõ äðóãèõ ïîäîáíûõ ïðåäëîæåíèÿõ)!!! Ìîæåòå ðàáîòàòü ñâîèì òåìïîì. Ñàìîå ëó÷øåå ýòî òî, ÷òî íåò íåîáõîäèìîñòè ïîêèäàòü ñâîé äîì. Åñëè âû âåðèòå, ÷òî êîãäà-íèáóäü, â îäèí ïðåêðàñíûé äåíü, ó Âàñ ïîÿâèòüñÿ âîçìîæíîñòü äîëãî îòäûõàòü, òàê ýòo, èìåííî, è åñòü òàêàÿ ÂÎÇÌÎÆÍÎÑÒÜ! Ïðîñòî, ñëåäóéòå äàííîé èíñòðóêöèè, è Âàø ñîí èñïîëíèòñÿ. Ýòîò áèçíåñ - Multi-level-E-MAIL òîðãîâëÿ ïî çàêàçàì, ïðîãðàììà äåéñòâóåò ïðåâîñõîäíî íà 100% è êîãäà è ãäå óãîäíî. E-mail ÿâëÿåòñÿ òîðãîâûì èíñòðóìåíòîì áóäóùåãî!!! Èñïîëüçóéòå ýòîò íåêîììåð÷åñêèé ìåòîä ðåêëàìû. Ñäåëàéòå ýòî ñåé÷àñ!!! ×åì äîëüøå áóäåòå æäàòü, òåì áîëüøå ëþäåé áóäåò äåëàòü ýòîò áèçíåññ. Âîçüìèòå ñåáå ÷àñòü ÝÒÎÉ ÀÊÖÈÈ!! MULTI-LEVEL-MARKETING (MLM) íàêîíåö-òî äîñòèã óâàæåíèÿ. Îí ïðåïîäàåòñÿ â Ãàðâàðäñêîé òîðãîâîé øêîëå. Ñòýíôîðäñêèé èññëåäîâàòåëüñêèé èíñòèòóò è æóðíàë Wall Street çàÿâèëè, ÷òî 50-65% âñåõ òîâàðîâ è óñëóã äî êîíöà òûñÿ÷åëåòèÿ áóäóò ïðîäàâàòüñÿ ïîñðåäñòâîì multi-level ìåòîäîâ. Ýòî ìíîãî ìèëëèàðäíàÿ äîëëàðîâàÿ èíäóñòðèÿ, è òîëüêî èç 500,000 ìèëëèîíåðîâ â ÑØÀ, öåëûõ 20% (100.000 ÷åëîâåê) ñäåëàëè ñâîå ñîñòîÿíèå çà ïîñëåäíèå ïàðó ëåò áëàãîäàðÿ MLM. À åùå, ñòàòèñòèêà ïîêàçûâàåò, ÷òî 45 ÷åëîâåê êàæäûé äåíü ñòàíîâÿòñÿ ìèëëèîíåðàìè áëàãîäàðÿ Multi-Level-Marketing. Âîçìîæíî, ÷òî âû óæå ñëûøàëè èñòîðèþ, êàê Äîíàëüä Òðàìï ëåòîì íàâåñòèë øîó Äåâèäà Ëåòòåðìàíà. Äåâèä ñïðîñèë åãî, ÷òîáû îí äåëàë åñëè áû ïîòåðÿë âñå ñâîå ñîñòîÿíèå è âûíóæäåí áûë íà÷àòü âñå ñ íà÷àëà. Äîíàëüä áåç êîëåáàíèÿ îòâåòèë, ÷òî íàøåë áû õîðîøóþ MLM ôèðìó è íà÷àë ðàáîòàòü. Ïóáëèêà íà÷àëà ñâèñòåòü âûðàæàÿ íåñîãëàñèå. Äîíàëüä ïîñìîòðåë íà çðèòåëüíûé çàë è ñåðüåçíî ïðîèçíåñ: "Áëàãîäàðÿ ýòîìó ÿ çäåñü íàâåðõó, à âû òàì, âíèçó!" Ñ ñåòåâûì ìàðêåòèíãîì âû èìååòå äâà èñòî÷íèêà ïðèáûëè: Ïðÿìàÿ ïðèáûëü ñ ïðîäàæè, êîòîðóþ ïðîâîäèòå Âû ñàìè è ïðèáûëü ñ îáîðîòà ëþäåé, êîòîðûõ ïðèâåäåòå â áèçíåñ. Áåñêîíå÷íàÿ ïðèáûëü ÿâëÿåòñÿ òàéíîé áîãàòñòâà. Ýòî çíà÷èò îäèí ðàç èíâåñòèðîâàòü âðåìÿ èëè äåíüãè à ïîòîì ïîëó÷àòü äåíüãè ñíîâà è ñíîâà.  ñåòåâîì ìàðêåòèíãå ýòî òàêæå îçíà÷àåò ïîëó÷àòü äåíüãè çà ðàáîòó äðóãèõ. Ê ñîæàëåíèþ, ïðî÷èòàâ ýòî ïèñüìî âïåðâûå, ÿ ïðàêòè÷åñêè ïðîïóñòèë òàêóþ âîçìîæíîñòü ñêâîçü ïàëüöû, è äàæå íå ñòàë ÷èòàòü äàëüøå, íî âñêîðå ÿ ïåðå÷èòàë âñå çàíîâî. Çàäóìàëñÿ è ïîíÿë âñþ ñèëó ýòîãî ïðåäëîæåíèÿ. È òåïåðü ÿ áîãàò è ñâîáîäåí. ß ìîãó äóõîâíî ðàçâèâàòüñÿ, îòäûõàòü, íàäî ìíîé íåò ãíåòà íà÷àëüñòâà, ìîåé ñåìüå è ìíå íå ìåøàåò óíèçèòåëüíàÿ áåäíîñòü è áîðüáà çà êóñîê õëåáà, ìåøàÿ ÷åëîâå÷åñêîé æèçíè... Íàïðèìåð, âîò ÷òî ãîâîðèò ìèñòåð Äæåðè Ïðîêòîð, àìåðèêàíñêèé ìèëëèîíåð. Äâà ãîäà íàçàä áûëà óïðàçäíåíà ìîÿ äîëæíîñòü â ôèðìå, â êîòîðîé ÿ ðàáîòàë ïîñëåäíèõ ïÿòíàäöàòü ëåò. Ïîñëå íåñêîëüêèõ íåóñïåøíûõ ñîáåñåäîâàíèé ÿ ðåøèë íà÷àòü ñâîé ñîáñòâåííûé áèçíåñ.  òå÷åíèè ïðîøëûõ ëåò ÿ ïðîøåë ìíîãî ôèíàíñîâûõ çàòðóäíåíèé. ß
Re: i586 FP optimizations hosed.
On Tue, 3 Apr 2001, John Baldwin wrote: On 03-Apr-01 Bruce Evans wrote: There are many other possibilities: ... - don't attempt to save the FPU state reentrantly, since this doesn't work with preemptive context switchiing unless interrupt handlers also save the state reentrantly, which they shouldn't do because it is too wasteful. Instead, save the state in the pcb as is already done in copy{in,out} so that cpu_switch() handles it. This may be too wasteful too. - as in previous possibility, but avoid switching the entire state. For the FPU, the entire state must be switched, but for SSE individual registers can be saved and restored. Saving and restoring individual registers reentrantly would be easy but no longer works for the SMP case. Switching a subset of the state would not be so easy. Hm. I think I'm liking the next to last. Even if there is additional overhead, it should still outperform generic_bcopy and friends on the CPU's in question, right? Not clear. We now have heavyweight context switches that switch the FPU for every interrupt. If we make switching the FPU for ithreads fundamental instead of a just source of bugs, then it will be harder to implement lightweight context switches for ithreads (context switches won't be lightweight if they switch the FPU, and we might have to do extra work to avoid them). Also, if the FPU is actually used a lot, then it will have to be switched a lot. Bruce 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
Re: pppoe, userland ppp
Leif, I have written an article on how to set up PPPOE under FreeBSD using userland PPP and Netgraph. The url is http://pandaemonium.newmillennium.net.au. Hope this helps. -- Alastair D'Silva (mob: 0413 485 733) Networking Consultant New Millennium Networking (web: http://www.newmillennium.net.au) - Original Message - From: "Leif Neland" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 04, 2001 6:03 AM Subject: pppoe, userland ppp I'd like to try pppoe to connect to poptop (on a linuxbox). The port is forbidden; I should use ng_pppoe. I haven't done netgraph stuff before; afaiu I should attach ng_pppoe to a node which is the physical device. But I'm doing userland ppp, and tun0 is not a node. ngctl list shows this: There are 10 total nodes: Name: ngctl3349 Type: socket ID: 000b Num hooks: 0 Name: ipr3Type: ether ID: 0009 Num hooks: 0 Name: ipr2Type: ether ID: 0008 Num hooks: 0 Name: ipr1Type: ether ID: 0007 Num hooks: 0 Name: ipr0Type: ether ID: 0006 Num hooks: 0 Name: isp3Type: ether ID: 0005 Num hooks: 0 Name: isp2Type: ether ID: 0004 Num hooks: 0 Name: isp1Type: ether ID: 0003 Num hooks: 0 Name: isp0Type: ether ID: 0002 Num hooks: 0 Name: ed0 Type: ether ID: 0001 Num hooks: 0 If my local network is 192.168.5.0, inside ip 192.168.5.11, outside ip dynamic, the remote internal network 192.168.0.0, the gateway running poptop is 192.168.0.1 internal, 194.1.2.3 outside, how do I setup ng_pppoe? When my ADSL gets installed, it will be on ed1. Same question as above. Leif 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
newbus driver code
Could someone point me to a device that is well-written, follows newbus, and would be a good example of how a device driver should be written? thanks, jm -- --- Jonathon McKitrick -- [EMAIL PROTECTED] "It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here." --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel fails with random device
On Wed, Apr 04, 2001 at 11:57:05AM +1000, Andrew Newlands wrote: Do you have the src-sys-crypto collection? I fixed this last night; solution was to get the contents of /usr/src/sys/crypto via ftp rather than using cvsup. Slightly surprising since src-crypto is in my cvsupfile.intl along with src-secure (which did arrive btw). Please reread what I wrote: src-crypto != src-sys-crypto. This is all documented in the example cvsupfiles. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
*HEADS UP* libposix1e is integrated into libc
src/lib/libposix1e was repocopied to src/lib/libc/posix1e, and I'll start to commit the necessary patches now and will then activate the build. World may be broken during a short interval due to the switch. You will also need to rebuild anything that uses libposix1e. In the base system, those are src/bin/getfacl and src/bin/setfacl for now. I'm not aware of any ports using it, so normally you should be fine after a buildworld. Please let me know of any problems. - thomas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: More xl0 watchdog timeout probs
Johny/others, Actually that was w/o pccard option in the config. I also tried it with it on but no luck still. I am not sure what the problem is. People have hinted it could also be a cable problem but it seems to work fine, and this card worked fine in Windows (I believe so). Oh well, maybe I just need to wait longer till someone fixes this in the CVS. Heres my config file: machine i386 cpu I586_CPU ident mums maxusers32 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INCLUDE_CONFIG_FILE #Include this file in kernel options MATH_EMULATE#Support for x87 emulation options INET#InterNETworking #optionsINET6 #IPv6 communications protocols #options IPSEC #IP security #options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options FFS #Berkeley Fast Filesystem options MSDOSFS options SOFTUPDATES #Enable FFS soft updates support options NFS #Network Filesystem #optionsNFS_ROOT#NFS usable as root device, NFS requiredoptions MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem #optionsDEVFS options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev # Security options #options IPFILTER#ipfilter support #options IPFILTER_LOG#ipfilter logging #options IPSTEALTH #support for stealth forwarding #options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN device isa device pci #device pccard options PCI_QUIET # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device ahc # AHA2940 and onboard AIC7xxx devices # SCSI peripherals #device scbus # SCSI bus (required) #device da # Direct Access (disks) #device cd # CD #device pass# Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 options SC_HISTORY_SIZE=1000 # Floating point support - do not disable. device npx # Power management support (see LINT for more options) device apm device pmtimer # Audio support device pcm device smbus device intpm device smb #optionsPCIC_RESUME_RESET #optionsPOWERFAIL_NMI # Pcmcia and cardbus bridge support #device pcic# pcmcia bridge #device card# pccard slots device pccbb # cardbus (yenta) bridge device cardbus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port #device ppc #device ppbus # Parallel port bus (required) #device lpt # Printer #device ppi # Parallel port interface device # PCI Ethernet NICs that use the common MII bus controller code. device miibus # MII bus support device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices - the number indicates how many units to allocated. device loop# Network loopback device random # Entropy device device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device speaker #pseudo-device gif 4 # IPv6 and IPv4
Re: *HEADS UP* libposix1e is integrated into libc
On Wed, Apr 04, 2001 at 07:23:18PM +0200, Thomas Moestl wrote: src/lib/libposix1e was repocopied to src/lib/libc/posix1e, and I'll start to commit the necessary patches now and will then activate the build. World may be broken during a short interval due to the switch. You will also need to rebuild anything that uses libposix1e. In the base system, those are src/bin/getfacl and src/bin/setfacl for now. I'm not aware of any ports using it, so normally you should be fine after a buildworld. The changes are complete now, so any possible breakage should be over. - thomas 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
fstab weirdness / UPDATING
My understanding is that there have been some changes regarding fstab, fsck, etc. recently. On boot, I find that only first two filesystems are listed as "clean", and on a recent un-clean shutdown only the first two were properly fsck'd (although the system was allowed to boot and mount read-write the unclean filesystems). I can only assume that some change to the boot procedure was made, since I made no changes. Are we going to see an UPDATING entry regarding this? I can't seem to find any explicit instructions in the mailing lists either. It worries me a bit when unclean filesystems are being mounted rw. WNM -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Anyone able to extract Apple Airport Firmare from the 1.3 software?
Hi, Anyone out there able to extract the firmware for the apple airport that is embedded in the 1.3 version of the software? Perhaps someone with a MAC could send me the file? Thanks, Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fstab weirdness / UPDATING
I've had that problem on one box also -- when the boot occurs, my /var partition is not fsck'd. It's the second pass-two file system, which means that it *should* be checked :-). I suspect a nit in the recent fsck cleanup, so I'm CC'ing phk, whose mailbox is obviously too empty. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services On Wed, 4 Apr 2001, Wesley Morgan wrote: My understanding is that there have been some changes regarding fstab, fsck, etc. recently. On boot, I find that only first two filesystems are listed as "clean", and on a recent un-clean shutdown only the first two were properly fsck'd (although the system was allowed to boot and mount read-write the unclean filesystems). I can only assume that some change to the boot procedure was made, since I made no changes. Are we going to see an UPDATING entry regarding this? I can't seem to find any explicit instructions in the mailing lists either. It worries me a bit when unclean filesystems are being mounted rw. WNM -- _ __ ___ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ [EMAIL PROTECTED] _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! 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
Re: fstab weirdness / UPDATING
* Robert Watson [EMAIL PROTECTED] [010404 22:04] wrote: I've had that problem on one box also -- when the boot occurs, my /var partition is not fsck'd. It's the second pass-two file system, which means that it *should* be checked :-). I suspect a nit in the recent fsck cleanup, so I'm CC'ing phk, whose mailbox is obviously too empty. I think I'm seeing the same thins... At boot I see a kernel printf "warning: /var was not properly dismounted" then /var mounts. If I unmount it and fsck it it's dirty. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message