wireless pc lock
Gnome Wireless PC Lock 0.2
Gnome Wireless PC Lock is a Gnome applet that locks your desktop when you walk away from your desk. more>>
A small gnome program that locks your desktop when you walk away from your desk. It is tested with a Sitecom cn-129 Wireless PC Lock.
Wireless Applet 1.0
Wireless Applet is a gnome-panel applet that shows up the status of your wireless card. more>>
This applet used to be in the default Gnome releases before it was replaced around v2.10 or so. Some users prefer it over the new one, so we decided to post it here for easy access to it.
Wireless Tools 27
The Wireless Tools is a set of tools allowing to manipulate the Linux Wireless Extensions. more>>
The Wireless Extension (WE) is a generic API allowing a driver to expose to the user space configuration and statistics specific to common Wireless LANs. The beauty of it is that a single set of tool can support all the variations of Wireless LANs, regardless of their type (as long as the driver support Wireless Extension).
Another advantage is these parameters may be changed on the fly without restarting the driver (or Linux).
The Wireless Tools (WT) is a set of tools allowing to manipulate the Wireless Extensions. They use a textual interface and are rather crude, but aim to support the full Wireless Extension. There are many other tools you can use with Wireless Extensions, however Wireless Tools is the reference implementation.
iwconfig manipulate the basic wireless parameters
iwlist allow to initiate scanning and list frequencies, bit-rates, encryption keys...
iwspy allow to get per node link quality
iwpriv allow to manipulate the Wireless Extensions specific to a driver (private)
ifrename allow to name interfaces based on various static criteria
Most Linux distributions also have integrated Wireless Extensions support in their networking initialisation scripts, for easier boot-time configuration of wireless interfaces. They also include Wireless Tools as part of their standard packages.
Wireless configuration can also be done using the Hotplug scripts and distribution specific support, this enable the proper support of any removable wireless interface (Pcmcia, CardBus, USB...).
Any versions of the Pcmcia package offer the possibility to do wireless configuration of Pcmcia and Cardbus card through thefile wireless.opts. This allow to fully integrate wireless settings in the Pcmcia scheme mechansism. However, this method is now deprecated in favor of distribution specific methods.
Please note that the Wireless Tools (starting with version 19) supports fully IEEE 802.11 parameters and devices, support older style of devices and most proprietary protocols, and are prepared to handle HiperLan as well. More recent versions of course adds more 802.11 support.
But, unfortunately not all drivers support all these features...
PyWireless 3.3
PyWireless is a basic wireless connection monitor with DCOP support. more>>
This is written because:
- KWifiManager seems like disaster (sorry guys!),
- Karamba eats my CPU,
- And there is no (or i cant find) KDE integrated wifi monitor tool
Enhancements:
- Program crashes at Shutdown problem solved.
GWireless 0.0.3
GWireless is a simplist utility for managing wifi 802.11x wireless connections on FreeBSD. more>>
GWireless enables you to connect to available networks without touching the ifconfig command by hand.
Asumptions:
- sudo available without pass
- wireless is ipw0 (if not, "ifconfig yours0 name ipw0")
wireless-applet 0.0.2
wireless-applet is an applet for the GNOME Panel displaying available wireless networks. more>>
Brings the comfort of NetworkManager to wpa_supplicant users. Supports WEP, WPA-PSK, and open wireless networks.
Linux Wireless LAN Project 0.2.3
The goal of the Linux WLAN project is to develop a complete, standards based, wireless LAN system. more>>
The linux-wlan package is a linux device driver and subsystem package that is intended to provide the full range of IEEE 802.11 MAC management capabilities for use in user-mode utilities and scripts. The package currently supports the Intersil 802.11b Prism2, Prism2.5, and Prism3 reference designs for PCMCIA, PCI, and USB.
The package includes support for PLX9052 based PCI to PCMCIA adapter
with a few different PCMCIA cards.
Wireless Assistant 0.5.7
Wireless Assistant is a small application allowing you to scan for wireless networks and connect to them. more>>
Wireless Assistant uses wireless-tools as its backend, so they need to be installed.
All feedback as well as hints and good advice are appreciated!
Installation:
make -f Makefile.cvs
./configure
make
su -c "make install"
Enhancements:
- NOTE: This release includes some brand new or rewritten features. Please submit bugs to sf.net page and comments/votes here. Thanks!
- NEW: Finally WPA-PSK support (WPA/WPA2, please test and report in case of problems!)
- NEW/FIX: Rewritten, completely new connection state detection (please comment!)
- NEW: Optional grouping of APs with the same ESSID
- FIX: UI refinements
- FIX: hide encryption keys in console output and edit dialogs
- FIX: Connection using dhclient fails
- FIX: dont check for connection while wizard is running
- FIX: remove default gateway upon disconnection if not managed by DHCP client
- FIX: updated Polish translation (with help from riklaunim)
- FIX: Many internal changes, more stable
File::NFSLock 1.20
File::NFSLock is a Perl module to do NFS (or not) locking. more>>
SYNOPSIS
use File::NFSLock qw(uncache);
use Fcntl qw(LOCK_EX LOCK_NB);
my $file = "somefile";
### set up a lock - lasts until object looses scope
if (my $lock = new File::NFSLock {
file => $file,
lock_type => LOCK_EX|LOCK_NB,
blocking_timeout => 10, # 10 sec
stale_lock_timeout => 30 * 60, # 30 min
}) {
### OR
### my $lock = File::NFSLock->new($file,LOCK_EX|LOCK_NB,10,30*60);
### do write protected stuff on $file
### at this point $file is uncached from NFS (most recent)
open(FILE, "+<<less
File::BasicFlock 98.1202
File::BasicFlock is a Perl module for file locking with flock. more>>
SYNOPSIS
use File::BasicFlock;
lock($filename);
lock($filename, shared);
lock($filename, undef, nonblocking);
lock($filename, shared, nonblocking);
unlock($filename);
Lock files using the flock() call. The file to be locked must already exist. This is a very thing interface.
Ovlada? USB Wireless adapter Atmel 1.6
Driver for USB Wireless LAN adapter based on the Atmel AT76C503/505A chipsets. more>>
Currently, the driver has some limitations:
no promiscous, monitor or station mode and no support for libpcap, i.e. it does not work with Kismet or Airsnort and it cannot act as an WLAN access point. This is a restriction imposed by the currently firmware
The firmware for Intersil radios is old (Atmel doesnt update it anymore) and has more restrictions. See the chipsets page for more information.
Support for 2.6.x kernels is now in main tree (versions 0.13+).
It has been tested with the usb host controller drivers usb-uhci, uhci and usb-ohci. It also works with more than one adapter on one
Enhancements:
- added switch to cope with Intersil firmware 0.84.0 which does not send FCS in rx data
- new module at76c503-rfmd-acc.o for SMC2664W, which got RMFD radio, but need a special firmware (Accton OEM products).
- added regulatory domains MKK1 and Israel
- added rudimentary ethtool support for SuSEs future hotplug
- added nickname ioctl for iwconfig
- added test of valid channel in reg. domain
- added big endian patch (by Kevin Cernekee), changed defines in ieee802_11.h
- supress unsupported iwconfig modes (monitor, master) - patch by Pavel Roskin
File::lockf 0.20
File::lockf is a Perl module interface to the lockf system call. more>>
SYNOPSIS
use File::lockf;
File-Lockf is an interface to the lockf system call. Perl supports the flock system call natively, but that does not acquire network locks. Perl also supports the fcntl system call, but that is somewhat ugly to use. There are other locking modules available for Perl, but none of them provided what I wanted -- a simple, clean interface to the lockf system call, without any bells or whistles getting in the way.
File-Lockf contains four functions which map directly to the four modes of lockf, and an OO wrapper class that encapulates the basic locking functionality along with an additional utility method that iteratively attempts to acquire a lock.
Lock functions
The following functions return 0 (zero) on success, and the system error number from errno on failure. They each take an open file handle as the first argument, and optionally a size parameter. Please see your system lockf man page for more details about lockf functionality on your system.
$status = File::lockf::lock(FH, size = 0)
This function maps to the F_LOCK mode of lockf.
$status = File::lockf::tlock(FH, size = 0)
This function maps to the F_TLOCK mode of lockf.
$status = File::lockf::ulock(FH, size = 0)
This function maps to the F_ULOCK mode of lockf.
$status = File::lockf::test(FH, size = 0)
This function maps to the F_TEST mode of lockf.
OO wrapper
File-Lockf also provides a simple OO wrapper class around the locking functionality, which allows you to create a lock object for a file handle and then perform lock operations with it. All of the methods return 0 (zero) on success, and the system error number from errno on failure.
$lock = new File::lockf(*FH)
This function returns a new lock object bound to the given file handle. Note that you need to pass a reference to the file handle to the constructor, not the file handle itself.
$status = $lock->lock(size = 0)
This method calls File::lockf::lock on the bound file handle.
$status = $lock->tlock(size = 0)
This method calls File::lockf::tlock on the bound file handle.
$status = $lock->ulock(size = 0)
This method calls File::lockf::ulock on the bound file handle.
$status = $lock->test(size = 0)
This method calls File::lockf::test on the bound file handle.
$status = $lock->slock(count = 5, delay = 2, size = 0)
This method will attempt to lock the bound file handle < count > times, sleeping < delay > seconds after each try. It will return 0 if the lock succeeded, or the system error number from errno if all attempts fail.
KWifiSelector 0.8
KWifiSelector is a KDE tool to display all available wireless networks (WLAN). more>>
KWifiSelector also allows the user to connect to and disconnect from a selected network.
Enhancements:
- The root elevation mechanism was changed from using kdesu to sudo.
- This allows avoiding giving everyone the root password.
File::LockDir 0.01
File::LockDir is a Perl basic filename-level lock utility. more>>
SYNOPSIS
use File::LockDir;
INTERFACE
new
Initializes the class. Returns the singleton object.
nflock($file, $nap_till, $locker, $lockhost)
Locks the supplied filename. Only $file is required.
$file is the file to be locked; $nap_till is the total amount of time to wait before giving up; $locker is a name identifying the locker; $lockhost is the host requesting the lock.
nunflock($file)
Unlocks the supplied file.
nlock_state($file)
Checks the state of the lock for the supplied file. Returns a list: the first item is true if the file is unlocked, and false if not; the second item is undef if the file is unlocked, and the identity (name and host) is it is locked.
DIAGNOSTICS
%s already locked
Seen when youve already locked the requested pathname. Informational only.
No pathname to be locked
You didnt supply a pathname to be locked to nflock. Fatal.
cant write to directory of %s
The directory where the file resides cant be written, so the lockfile cant be created.
cant get %s: %s
The named lock cant be gotten: the reason is supplied. Failure occurs after ten tries to get the lock.
%s %s[%s]: lock on %s held by %s
The lock on the specified file is help by the noted locker. Informatory message, printed only when debugging is on.
close failed for %s: %s
The file containing the lock information couldnt be closed for the reason shown.
releasing lock on %s
Debug message; notes that the lock on the specified file was successfully released.
record_locking 0.01
This product offers PHP/Ajax method of implementing dynamic application level record locking. more>>
record_locking 0.01 is yet another powerful package for web developers. It actually offers PHP/Ajax method of implementing dynamic application level record locking.
There has been a lot of effort to create enterprise grade multiuser LAMP applications, since this approach promises to solve a lot of major problems - such as platform independence, eliminating the overhead of maintaining software on the user's workstation, etc.
However, one of the dirty secrets of LAMP apps is that the record locking provided by the database server only functions for the duration of the transaction - which in the case of a browser based UI is only during a single html request/event. There isn't any established means of maintaining a record lock over multiple html "interactions" with the user - i.e: during the time while the user has the record in his browser window for editing.
A true multi-user app requires "application level" record locking to ensure that only one user can change a record at a time. Enabling members to change (parts of) their own records creates a non-zero possibility of race conflicts with the office manager or other authorized admins attempting to change the same record.
Each status check updates the lock timestamp, confirming that the user is still connected and actively editing the record. Locks are normally released when the user saves the record or navigates to a different screen. If the user fails to properly close/release the record - abandons the record or his browser crashes - locks go stale if not updated for 5 minutes. The next status request or attempt to lock the record will delete or overwrite any stale lock.
Saving a record requires a current lock owned by the user. This protects against obsolete cached data being resubmitted to the database. The user must remain in effectively continuous contact with the database in order to successfully change a record - emulating the behavior of a conventional "closely linked" application.
The user's background javascript process requests a special php file that manages the lock directory and generates a minimal html response back to the calling javascript process with the current lock status. The javascript process parses this returned html message and updates the lock status window. In order to avoid hammering the hard disk with lock traffic, the special php file and lock directory are loaded into a ramdrive mounted as the lock/ directory tree.