Re: jiffy.
In article [EMAIL PROTECTED], Wilkinson,Alex [EMAIL PROTECTED] writes erm...what are jiffies ? http://dictionary.reference.com/search?q=jiffy The last definition on the page starts: jiffy n. 1. The duration of one tick of the system clock on your computer (see tick). Often one AC cycle time (1/60 second in the U.S. and Canada, 1/50 most other places), but more recently 1/100 sec has become common. ... The Commodore PET, for example, called its 1/60 second clock tick a jiffy. Used for timing relatively short intervals. ttfn, Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: jiffy.
In article [EMAIL PROTECTED], Evan S. [EMAIL PROTECTED] writes Hello, I'm wondering if FreeBSD-current has anything similar to Linux jiffies? This level of question is probably best asked on freebsd-questions. That said, probably want you is: man 2 gettimeofday Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ax88172 vs FreeBSD USB stack
In article [EMAIL PROTECTED], Bill Paul [EMAIL PROTECTED] writes So. I picked up a Linksys USB200M USB 2.0 ethernet adapter that uses the ASIX Electronics AX88172 chip, and I started cobbling together a driver. This chip uses a series of vendor specific commands to do things like read/write the MII management interface on the MAC, read/write the SROM, set the RX filter, multicast hash table, etc. I can do all this no problem. The Linksys NIC uses a RealTek 8201L PHY, and I can attach it and negotiate a link. I have a Netgear FA120, also following ASIX's 'demonstration design', (i.e. reference design), of AX88172 and Realtek 8201L phy. I've not tried it with FreeBSD yet, but I had in mind to use NetBSD's uax driver for the AX88172 as the starting point! uax man page: http://netbsd.gw.com/cgi-bin/man-cgi/man?uax+4+NetBSD-current Netbsd cvs web: http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/usb/if_uax.c Hope this helps! Tony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lexmark Z12
In article [EMAIL PROTECTED], Nikolai Georgiev [EMAIL PROTECTED] writes Is there somebody /smth/ that can make my Lexmark Z12 work? The following is how remember a previous look at this. I can't get past a page with lots printer pictures at www.lexmark.com, i.e. to some tech specs for this model. This is an example of the printer equivalent of a winmodem. The printer is very stupid and all the work is done by the printer driver, it will not even print ASCII on its own. As far as I know Lexmark only have drivers for windows, and they do not (openly) publish documentation for a clone to be made for BSD. Linux is also stumped by this cheap nasty printer, according to: http://www.linuxdoc.org/HOWTO/Hardware-HOWTO/incompatible.html Sorry, unless you can hang this off a win box it is little more than a doorstop. You could, as a customer, write to Lexmark and ask them for help connecting it to FreeBSD. Tony To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Super Block
[Emailed to questioner, cc'd to FreeBSD lists only] In article [EMAIL PROTECTED], Wilkinson,Alex [EMAIL PROTECTED] writes Howdy Crew, I am wanting to find out the significance of the Super Block, whether FreeBSD, Linux, Solaris... whatever. I know: * The Super Block contains critical data for the device's filesystem [but what ??]. * It is located on sectors 16 through 31 at the beggining of the device. I think these vary with the file system. * FreeBSD keeps an alternate SuperBlock at the begging of every cylinder group. * The first alternate Super block on FBSD is at block 32. This is all the info I could scrounge up. What does the SuperBlock actually do ? Why is the SuperBlock so critical ? When the file system driver starts it reads the SuperBlock to confirm that the driver can recognise the disk. E.g. checking for magic numbers. The SuperBlock contains information on the disk area allocated to the partition, free/used blocks, where to find the root directory, block size, inode size, etc... It also indicates whether the disk has been modified, which can force fsck to run, this is cleared when the volume is unmounted. It is hard to say much more without knowing more about your interest in it. Cheers, Tony To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Oh my god, Google has a USENET archive going back to 1981!
In article [EMAIL PROTECTED], Danny Horne [EMAIL PROTECTED] writes Oooohh!! Those model numbers bring back memories!! I remember drooling over the first Commodore Pet (the one with the rectangular keyboard) in one of the many computer shops that were springing up at the time. When my school bought its 3016 (1980?) it was a revelation. I had seen the big orange ICL mainframe where my dad worked, a room full of big cabinets and whirring disks tapes, but this was a computer on a desk! If anyone's interested, I've got a 2nd edition of Nick Hampshire's 'The Pet Revealed' That, and Zaks' book on programming the 6502, certainly fuelled my enthusiasm and many hours with a switch connected to the NMI line and the MLM. I'm still fascinated by computer schematics, and dabbling with the hardware. ;-) Thankfully Google is missing many of my early postings. Tony To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Need PCI/VIA chipset help (was Re: 4.4-STABLE crashes - suspects new ata-driver over wd-drivers)
In article 005101c18ee1$9b5d66e0$fa01a8c0@ABERRATION, Predius [EMAIL PROTECTED] writes There are a couple known issues going on with the VIA Chipset line (Some acknowledge by VIA partially, some not.) beyond just the 686B bug. Here's a couple sites with details. Myself, I think it's a BIOS writer's problem as well, but unfortunatly with most VIA boards, their goal is performance over stability, leaving people like us SOL. http://www.networking.tzo.com/net/software/ http://www.tecchannel.de/hardware/813/1.html - In german, bring your fish This story, about all VIA chipsets having poor throughput with Ultra-ATA/133 controllers and other fast PCI adapters is available in English: http://www.tecchannel.de/hardware/817/index.html The links are largely German. Follow the [Weiter ] links to page through the story, or download the PDF version. Cheers, Tony (with a VIA 686A on my system board) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Found NFS data corruption bug... (was Re: NFS: How to make FreeBSD fall on its face in one easy step )
In article [EMAIL PROTECTED], Sergey Babkin [EMAIL PROTECTED] writes By the way the journaling filesystems don't neccessary guarantee that you won't need fsck: for example, if VXFS crashes at a particularly bad moment, it will require you to do fsck -o full which is as slow as the fsck on traditional UFS. JFS still scores against traditional Unix file systems on large volumes, (e.g. Terabytes), as it requires very small amounts of virtual memory during a full fsck. ttfn, Tony To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
