We wouldn't have problems like the one I've been having, where a segfaulted server can't re-bind its socket for up to a minute because Linux (2.6.9) didn't clear out the file descriptor tables (all the BSDs do it immediately after program termination in *any* way).
Perhaps I haven't expressed myself clearly. I meant the Free/OpenSource drivers for ATI and NVidia cards under MIT/X11 licence. I have an NVidia card and use the 'nv' driver from XFree86. It doesn't support 3D acceleration but it's rock stable in constrast to the proprietary NVidia's driver.
Yes, it is really firmware. It is loaded from disk as a block of data and passed to the card. The system CPU doesn't execute anything out of the firmware, nor does the firmware know anything about the kernel.
I don't know but doesn't the driver labelled "Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)" work with your card? I think that more wireless drivers will get merged into 2.6. For example just yesterday the driver for my mini-PCI Cisco card was included.
Well, you can still use the ide-scsi emulation in 2.6, although it's not optimal. Recently there have been some fixes to ide-scsi in 2.6, that have made it usable again.
Slashdot Mirror
What's wrong with: dd if=/dev/hdb1 of=/mnt/hdh1/path/to/desired/backup/image/here.iso
The fact that you call the resulting file *.iso even when it's highly improbable that it contains an ISO9660 filesystem.Perhaps I haven't expressed myself clearly. I meant the Free/OpenSource drivers for ATI and NVidia cards under MIT/X11 licence. I have an NVidia card and use the 'nv' driver from XFree86. It doesn't support 3D acceleration but it's rock stable in constrast to the proprietary NVidia's driver.
There are free drivers for ATI and NVidia cards in XFree86. Using a generic VGA driver would be silly.
It is a real Firefox bug. See bug #217527 in the Bugzilla. There are some minimal testcases, which are standards compliant and still exhibit this bug.
Yes, I'm seeing this on Linux.
I'm seeing it quite often. This is bug #217527 in Bugzilla. When it happens, you can workaround it with CTRL+PLUS and CTRL+MINUS.
Yes, it uses the wireless extensions.
In a post to LKML James Ketrenos said this:
Yes, it is really firmware. It is loaded from disk as a block of data and passed to the card. The system CPU doesn't execute anything out of the firmware, nor does the firmware know anything about the kernel.
That's interesting because the original announcement was sent to LKML by James Ketrenos from the address jketreno at linux.co.intel.com.
WEP is weak. Use OpenVPN if you can.
I don't know but doesn't the driver labelled "Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)" work with your card?
I think that more wireless drivers will get merged into 2.6. For example just yesterday the driver for my mini-PCI Cisco card was included.
Well, you can still use the ide-scsi emulation in 2.6, although it's not optimal. Recently there have been some fixes to ide-scsi in 2.6, that have made it usable again.
It's a fact that 99% (possibly more) of BSOD's in modern day Windows operating systems are caused by bad hardware or bad drivers. Third party drivers.
I agree.
At least for Windows, I can find drivers for _all_ my hardware.
At least in Linux, I can FIX the bad drivers.
Try putting it into script leds.sh and running it like this: /dev/console
leds.sh <