similar to: wpa_supplicant and wi

Displaying 10 results from an estimated 10 matches similar to: "wpa_supplicant and wi"

2007 Mar 09
0
Wireless fails with Netgear MA401 card.
Alle, I have recently installed CentOS4.4 on an old Fujitsu E7110 laptop. I'm trying to get a Netgear MA401 card installed for wireless access but when I configure the card and start the network I get: Mar 9 09:03:20 localhost network: Setting network parameters: succeeded Mar 9 09:03:20 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team Mar 9 09:03:20 localhost network:
2004 Jan 14
5
* For Call Center
Hi Everyone ;) I have posted something like this before but yeilded no solid help as of yet. I am new to * and havent even setup a box for it yet as to I have no clue what I should go ahead and buy before wasting a few $k. Im looking to setup * for my office with outbound calling only with some call agents, and also remote agents so they can work from home. At this time im not looking to
2009 Jun 11
5
Problems with Broadcom 4312 wireless
I'm migrating my son's Dell laptop from Vista to CentOS 5.3. He came back from each of his first two years of college loaded with virii and trojans. This year he said "Dad, can you give me Linux?" 5.3 went onto the laptop easily and after doing some research, I applied the guidance for getting multimedia working and got the nvidia driver loaded. That works great. Last
2010 Aug 15
24
Xen patches merged to upstream Linux 2.6.36, plans for 2.6.37?
Hello, It looks like upstream linux-2.6.git contains at least the following xen related new features for Linux 2.6.36: - Xen-SWIOTLB support (required for Xen PCI passthru and dom0) - Xen PV-on-HVM drivers - Xen VBD online dynamic resize of guest disks (xvd*) Congratulations! What are the plans for 2.6.37 merge window? I believe at least: - Xen PCI frontend Others? I''m going to
2008 May 13
1
Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7
I seem to be able to lock my machine by going into wpa_cli and asking it to 'reassoc'. The reason for question mark after "hard" is that debug information (caused by wlandebug and athdebug) is being printed on the console. The only way to get machine's attention is to hold power button for 8 seconds. Note: manual reassociation is just the handy way to reproduce the problem
2006 Jul 26
5
linux-2.6-xen.hg
Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2020 Jun 16
3
[PATCH v5 0/2] mm, treewide: Rename kzfree() to kfree_sensitive()
v5: - Break the btrfs patch out as a separate patch to be processed independently. - Update the commit log of patch 1 to make it less scary. - Add a kzfree backward compatibility macro in patch 2. v4: - Break out the memzero_explicit() change as suggested by Dan Carpenter so that it can be backported to stable. - Drop the "crypto: Remove unnecessary
2020 Jun 16
14
[PATCH v4 0/3] mm, treewide: Rename kzfree() to kfree_sensitive()
v4: - Break out the memzero_explicit() change as suggested by Dan Carpenter so that it can be backported to stable. - Drop the "crypto: Remove unnecessary memzero_explicit()" patch for now as there can be a bit more discussion on what is best. It will be introduced as a separate patch later on after this one is merged. This patchset makes a global rename of the kzfree()
2020 Jun 16
14
[PATCH v4 0/3] mm, treewide: Rename kzfree() to kfree_sensitive()
v4: - Break out the memzero_explicit() change as suggested by Dan Carpenter so that it can be backported to stable. - Drop the "crypto: Remove unnecessary memzero_explicit()" patch for now as there can be a bit more discussion on what is best. It will be introduced as a separate patch later on after this one is merged. This patchset makes a global rename of the kzfree()
2020 Apr 13
10
[PATCH 0/2] mm, treewide: Rename kzfree() to kfree_sensitive()
This patchset makes a global rename of the kzfree() to kfree_sensitive() to highlight the fact buffer clearing is only needed if the data objects contain sensitive information like encrpytion key. The fact that kzfree() uses memset() to do the clearing isn't totally safe either as compiler may compile out the clearing in their optimizer. Instead, the new kfree_sensitive() uses