Maybe we can also hardcode the alias rm='rm -i', just in case.
Your intentions are nice, but that are too much lines for a naive test
that a serious 'root' would have hit with a simple -and mandatory-
'pfctl -s rules'.
El 02/01/2012 18:59, Stephane A. Sezer escribis:
On Mon, 2 Jan 2012
On Fri, Dec 30, 2011 at 05:55:27PM +0100, Ariane van der Steldt wrote:
- it's only a 3^W 10494 line diff :P
Wow, you weren't kidding.
I'll need testing on any and all architectures.
I'm now running this on my sparc64, macppc and amd64 boxes, the amd64 is the
only one i currently actually use,
hello tech@
mfi(4) diff to support MegaRAID 9240-4i (from kravchuk...@gmail.com).
2:0:0: Symbios Logic MegaRAID SAS2008
0x: Vendor ID: 1000 Product ID: 0073
0x0004: Command: 0147 Status ID: 0010
0x0008: Class: 01 Subclass: 04 Interface: 00 Revision: 03
0x000c:
Grrr, so the vendor changed the device without changing any IDs that we
currently use for matching (main/subsystem device/vendor IDs) or revision
number - so somebody is going to need a custom kernel to get the device
working.
Anyone know which is the more common card? I note there are *no*
Switching to IDE mode on the Asus P5SD2-VM activates
a weird chipset known as the SiS 1183.
pciide1 at pci0 dev 5 function 0 vendor SiS, unknown product 0x1183 rev 0x03:
DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI
pciide1: using apic 1 int 17 for native-PCI
Check for valid ACPI _PSS object before doing the MSR read, fixes KVM brokeness
as reported/tested by Walter Haidinger.
It could also potentially avoid a general protection fault on theoretically
real (..yet so far not witnessed) systems.
I'm still open to doing the CPUID check, but as I
On Tue, Jan 3, 2012 at 17:05, Stuart Henderson st...@openbsd.org wrote:
Anyone know which is the more common card? I note there are *no*
8-port sunix 40xx in dmesglog at all.
Apart from it being shamelessly at 4.3, does the following dmesg help
you in any way? Excerpt for an 8-port puc(4) at
On my system, the patch causes wpi to timeout during firmware upload,
resulting in a non-working WiFi card.
The dmesg doesn't say anything more besides that. Is there anything I
can do to provide more useful data?
--
Gregor Best
[demime 1.01d removed an attachment of type
On 01/03/2012 01:28 PM, Gregor Best wrote:
On my system, the patch causes wpi to timeout during firmware upload,
resulting in a non-working WiFi card.
The dmesg doesn't say anything more besides that. Is there anything I
can do to provide more useful data?
--
Gregor Best
[demime 1.01d
On 01/03/2012 01:28 PM, Gregor Best wrote:
On my system, the patch causes wpi to timeout during firmware upload,
resulting in a non-working WiFi card.
The dmesg doesn't say anything more besides that. Is there anything I
can do to provide more useful data?
--
Gregor Best
On Sat, Dec 31, 2011 at 11:49:13PM -0500, Geoff wrote:
These patches are submitted for your amusement.
Nice catch below (but why hide a good bugfix in so many lines?) :)
Index: uvm/uvm_pmemrange.c
===
RCS file:
Loganaden Velvindron [logana...@devio.us] wrote:
The SiS 1183 is weird in the sense that it shows as an
IDE device when in fact, it's a SATA controller. I don't
see any reason why this is necessary.
The physical interface is unimportant. The software interface is the same,
unless you
On Tue, Jan 03, 2012 at 12:56:46PM -0500, Loganaden Velvindron wrote:
Switching to IDE mode on the Asus P5SD2-VM activates
a weird chipset known as the SiS 1183.
pciide1 at pci0 dev 5 function 0 vendor SiS, unknown product 0x1183 rev
0x03: DMA (unsupported), channel 0 wired to native-PCI,
On Mon, Jan 02, 2012 at 04:35:39PM -0500, Loganaden Velvindron wrote:
Attaching any CDROM/DVDRIVE causes this error message
when mouting a disk.
cd0(pciide0:0:1): timeout
type: atapi
c_bcount : 2048
c_skip : 0
The machine then freezes and a hard reboot is necessary.
This issue has
14 matches
Mail list logo
