how to unlock the gt3rs in nfs carbon
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 481
Pocket Linux 2.51
Pocket Linux is an almost minimal, one floppy linux system designed to quickly convert PC workstation into a secure linux. more>>
Pocket Linux is an almost minimal, one floppy linux system designed to quickly convert PC workstation into secure linux-based workstation using ssh to connect to remote host (other networking clients are also supported).
It supports bootp for determining host IP and other network parameters (theres also manual configuration possible, but bootp is recommended).
In addition to workstations equipped with a network card (ethernet or arcnet), you can also use Pocket Linux on a PC equipped with a modem. Modem is automatically detected and then PPP connection is made.
The idea came up some time in 1996 or so. The distribution then was not perfect, but still it shown it was a great idea. It wasnt maintained for about year or so, until I took it up again in the early January 1998. After a complete rebuild Pocket Linux 2.00 was released. It soon gained a huge number of happy users, whose ideas helped its development.
The aim is to provide a small and efficient workstation that autoconfigures as much as possible and lets securely use the network from almost everywhere.
Current version is a nice attempt and future ones will enhance the automation and support for various network equipment and protocols, becoming a total solution. Future plans also include side projects like one floppy router.
In order to understand some of the config options its useful to know something about operations that are done during bootup (in order to automatically configure the network). These are, in order (the later attempts are made if the earlier ones dont set-up the network):
- attempt to setup the network using BOOTP
- attempt to reuse previous manual configuration
- modem detection
- attempt to setup modem conection
Most of the config options switches these operations on and off.
Main menu
You can choose the following network configuration commands from the main menu (only the ones that make sense in the present context are displayed):
- Options - allows setting few binary parameters controlling automatic network configuration and modem handling.
- BOOTP query - attempts to configure network (ethernet or arcnet) using BOOTP. Normally its automatically done during bootup, but this can be switched off.
- Manual configuration - allows manual setting of network configuration parameters (ethernet or arcnet).
- Detect modem - detects serial port the modem is on and its parameters (transfer rate, initialization commands).
- Dial PPP using predefined configuration - creates modem connection (PPP) using one of (up to ten) remembered configurations. By default only TPSA (0202122) configuration is remembered.
- Dial PPP using new configuration - creates new PPP configuration and sets up a modem connection using the newly created config.
- Disconnect PPP - disconnects modem connection.
- Mount /usr via NFS - mounts remote /usr filesystem via NFS. It will be automatically mounted during each Pocket Linux bootup if its turned on in configuration options.
- Exit - Do not config the network - exits the program without configuring the network.
Configuration options
There are following options available:
- Probe network with BOOTP - switches automatic BOOTP probing during bootup on and off. On by default.
- Reuse manual network configs - if on, an attempt is made to restore network configuration during bootup. Netconf remembers 10 most recent manual configurations along with network cards MAC addresses. If cards MAC address matches one of the remembered ones, assigned configuration is used. On by default.
- Automatically setup PPP - switches automatic attempt to create modem connection during bootup on and off. Its made with the first config on PPP configs list. On by default.
- Reuse modem configuration - if on, modem detection is not performed during bootup - instead most recently used modem configuration is used. Off by default.
- Pulse dialing - switches dialing mode used for modem connections between tone dialing (DTMF) and pulse dialing. Default is off (that is tone dialing).
- Automount disk partitions - switches on and off automatical disk partitions mounting (ext2 and vfat filesystems) and swap partition activation during bootup. On by default.
- Add swap file if low memory - switches on and off automatical swap file creation during bootup. Swap file is created if, and only if, theres less than 16 MB memory available (including potentially activated swap partitions) and theres a disk partition on which it could be created available. On by default.
- Automount NFS /usr - switches on and off /usr filestem mounting via NFS during bootup. NFS path to the filestem must be set using "Mount /usr filesystem via NFS" command in main menu. Off by default.
Manual network card configuration
You can enter network configuration parameters in this window:
- This machines IP - enter IP number for this computer here
- Network mask - enter netmask here. If omitted, mask will be calculated based on IP (which will not necessarily be right).
- Broadcast address - enter network broadcast address here. If omitted broadcast address will be calculated based on IP (not mask! - which will not necessarily be right).
- Default gateway - enter IP address of default network gateway (router) here.
- Nameserver IP(s) - enter one or more (separated by spaces) name servers IP addresses here. Can be omitted, but then domain names couldnt be used.
- Default domain(s) - you can enter one or more (separated by spaces) domain names to search host if incomplete domain names will be used. Its optional.
PPP configuration
You can enter modem connection configuration parameters in this window:
- Config name - config name (used in existing configuration selection menu).
- Phone number - phone number to dial (eg. 0w202122 for TPSA access modems).
- Username - username to send to remote server
- Password - password to send to remote server
- Nameserver IP(s) - enter one or more (separated by spaces) name servers IP addresses here. Can be omitted, but then domain names couldnt be used.
- Default domain(s) - you can enter one or more (separated by spaces) domain names to search host if incomplete domain names will be used. Its optional.
Because of permanent configuration that is kept on the floppy you should remember to:
- dont write protect the floppy
- dont remove the floppy from the drive (at least during network configuration)
Enhancements:
- bugfixes in netconf reuse code
- disk partitions automounting, swap partitions autoactivating
- automatic swap file creation
- extended support for NFS mountable /usr
- PS/2 mouse support
- new startup logo
<<lessIt supports bootp for determining host IP and other network parameters (theres also manual configuration possible, but bootp is recommended).
In addition to workstations equipped with a network card (ethernet or arcnet), you can also use Pocket Linux on a PC equipped with a modem. Modem is automatically detected and then PPP connection is made.
The idea came up some time in 1996 or so. The distribution then was not perfect, but still it shown it was a great idea. It wasnt maintained for about year or so, until I took it up again in the early January 1998. After a complete rebuild Pocket Linux 2.00 was released. It soon gained a huge number of happy users, whose ideas helped its development.
The aim is to provide a small and efficient workstation that autoconfigures as much as possible and lets securely use the network from almost everywhere.
Current version is a nice attempt and future ones will enhance the automation and support for various network equipment and protocols, becoming a total solution. Future plans also include side projects like one floppy router.
In order to understand some of the config options its useful to know something about operations that are done during bootup (in order to automatically configure the network). These are, in order (the later attempts are made if the earlier ones dont set-up the network):
- attempt to setup the network using BOOTP
- attempt to reuse previous manual configuration
- modem detection
- attempt to setup modem conection
Most of the config options switches these operations on and off.
Main menu
You can choose the following network configuration commands from the main menu (only the ones that make sense in the present context are displayed):
- Options - allows setting few binary parameters controlling automatic network configuration and modem handling.
- BOOTP query - attempts to configure network (ethernet or arcnet) using BOOTP. Normally its automatically done during bootup, but this can be switched off.
- Manual configuration - allows manual setting of network configuration parameters (ethernet or arcnet).
- Detect modem - detects serial port the modem is on and its parameters (transfer rate, initialization commands).
- Dial PPP using predefined configuration - creates modem connection (PPP) using one of (up to ten) remembered configurations. By default only TPSA (0202122) configuration is remembered.
- Dial PPP using new configuration - creates new PPP configuration and sets up a modem connection using the newly created config.
- Disconnect PPP - disconnects modem connection.
- Mount /usr via NFS - mounts remote /usr filesystem via NFS. It will be automatically mounted during each Pocket Linux bootup if its turned on in configuration options.
- Exit - Do not config the network - exits the program without configuring the network.
Configuration options
There are following options available:
- Probe network with BOOTP - switches automatic BOOTP probing during bootup on and off. On by default.
- Reuse manual network configs - if on, an attempt is made to restore network configuration during bootup. Netconf remembers 10 most recent manual configurations along with network cards MAC addresses. If cards MAC address matches one of the remembered ones, assigned configuration is used. On by default.
- Automatically setup PPP - switches automatic attempt to create modem connection during bootup on and off. Its made with the first config on PPP configs list. On by default.
- Reuse modem configuration - if on, modem detection is not performed during bootup - instead most recently used modem configuration is used. Off by default.
- Pulse dialing - switches dialing mode used for modem connections between tone dialing (DTMF) and pulse dialing. Default is off (that is tone dialing).
- Automount disk partitions - switches on and off automatical disk partitions mounting (ext2 and vfat filesystems) and swap partition activation during bootup. On by default.
- Add swap file if low memory - switches on and off automatical swap file creation during bootup. Swap file is created if, and only if, theres less than 16 MB memory available (including potentially activated swap partitions) and theres a disk partition on which it could be created available. On by default.
- Automount NFS /usr - switches on and off /usr filestem mounting via NFS during bootup. NFS path to the filestem must be set using "Mount /usr filesystem via NFS" command in main menu. Off by default.
Manual network card configuration
You can enter network configuration parameters in this window:
- This machines IP - enter IP number for this computer here
- Network mask - enter netmask here. If omitted, mask will be calculated based on IP (which will not necessarily be right).
- Broadcast address - enter network broadcast address here. If omitted broadcast address will be calculated based on IP (not mask! - which will not necessarily be right).
- Default gateway - enter IP address of default network gateway (router) here.
- Nameserver IP(s) - enter one or more (separated by spaces) name servers IP addresses here. Can be omitted, but then domain names couldnt be used.
- Default domain(s) - you can enter one or more (separated by spaces) domain names to search host if incomplete domain names will be used. Its optional.
PPP configuration
You can enter modem connection configuration parameters in this window:
- Config name - config name (used in existing configuration selection menu).
- Phone number - phone number to dial (eg. 0w202122 for TPSA access modems).
- Username - username to send to remote server
- Password - password to send to remote server
- Nameserver IP(s) - enter one or more (separated by spaces) name servers IP addresses here. Can be omitted, but then domain names couldnt be used.
- Default domain(s) - you can enter one or more (separated by spaces) domain names to search host if incomplete domain names will be used. Its optional.
Because of permanent configuration that is kept on the floppy you should remember to:
- dont write protect the floppy
- dont remove the floppy from the drive (at least during network configuration)
Enhancements:
- bugfixes in netconf reuse code
- disk partitions automounting, swap partitions autoactivating
- automatic swap file creation
- extended support for NFS mountable /usr
- PS/2 mouse support
- new startup logo
Download (1.44MB)
Added: 2005-05-11 License: GPL (GNU General Public License) Price:
1640 downloads
The Revisionist 0.02b
The Revisionist is a tool for extracting and indexing hidden metadata. more>>
The Revisionist is a tool for extracting and indexing hidden metadata (such as deleted or modified text) from large collections of MS Word files.
It can operate whole Web sites or SMB or NFS directories. The Revisionist project is handy for pen-testing, or it can be used just to spot embarrassing secrets.
My primary goal is to provide pen-testers and content administrators with a handy tool to detect hidden data in all documents available at a specific location (be it a locally mounted network share, a HTTP site, or whatnot), and easily review it all.
Right now, the tool only detects and indexes deleted text in documents with "change tracking" enabled, and can also index usernames and hardware addresses embedded in documents (to facilitate external assessment of company structure); future versions should be able to recover other goodies, too.
Usage:
To run the tool against a local directory, a mounted SMB or NFS directory, or such, simply issue the following command (after doing make, that is):
./therev @/path/to/directory
After the tool completes, you should be able to view master.html in current directory using your favourite browser (Lynx, Netscape, etc). Cached copies of documents would be placed in subdirectories named document.XXXXXX, where X is a random digit; hence, it is recommended to run the tool in a separate directory.
Note that you may also instruct the tool to look for specific substring and only choose those documents that contain it (strict checking, no regexp available):
./therev linux @/path/to/directory
To run the program against a specific site or top-level domain, do the following:
./therev site.com
Note that com, gov, gov.pl, www.microsoft.com are all a valid site name. The first parameter works similar to the previous case:
./therev homeland security gov
As a special bonus, when running the script against multilinguinal sites, you might want to specify a third parameter - desired language (using a two-letter code: en, pl, etc). NOTE: DO NOT USE LANGUAGE QUALIFIER UNLESS NECESSARY:
./therev linux microsoft.com en
The HTTP search mode uses Google.com to locate all matching Word documents on a specific site. For a document to be found, it must be indexable (that is, not excluded in robots.txt) and be in the first 1000 of results for a specific site. If there are more than 1000 documents at some website, consider sub-searches with keywords.
Enhancements:
- This release was fixed to work with the new Google page layout.
- Some other minor fixes were made.
<<lessIt can operate whole Web sites or SMB or NFS directories. The Revisionist project is handy for pen-testing, or it can be used just to spot embarrassing secrets.
My primary goal is to provide pen-testers and content administrators with a handy tool to detect hidden data in all documents available at a specific location (be it a locally mounted network share, a HTTP site, or whatnot), and easily review it all.
Right now, the tool only detects and indexes deleted text in documents with "change tracking" enabled, and can also index usernames and hardware addresses embedded in documents (to facilitate external assessment of company structure); future versions should be able to recover other goodies, too.
Usage:
To run the tool against a local directory, a mounted SMB or NFS directory, or such, simply issue the following command (after doing make, that is):
./therev @/path/to/directory
After the tool completes, you should be able to view master.html in current directory using your favourite browser (Lynx, Netscape, etc). Cached copies of documents would be placed in subdirectories named document.XXXXXX, where X is a random digit; hence, it is recommended to run the tool in a separate directory.
Note that you may also instruct the tool to look for specific substring and only choose those documents that contain it (strict checking, no regexp available):
./therev linux @/path/to/directory
To run the program against a specific site or top-level domain, do the following:
./therev site.com
Note that com, gov, gov.pl, www.microsoft.com are all a valid site name. The first parameter works similar to the previous case:
./therev homeland security gov
As a special bonus, when running the script against multilinguinal sites, you might want to specify a third parameter - desired language (using a two-letter code: en, pl, etc). NOTE: DO NOT USE LANGUAGE QUALIFIER UNLESS NECESSARY:
./therev linux microsoft.com en
The HTTP search mode uses Google.com to locate all matching Word documents on a specific site. For a document to be found, it must be indexable (that is, not excluded in robots.txt) and be in the first 1000 of results for a specific site. If there are more than 1000 documents at some website, consider sub-searches with keywords.
Enhancements:
- This release was fixed to work with the new Google page layout.
- Some other minor fixes were made.
Download (0.016MB)
Added: 2006-01-30 License: LGPL (GNU Lesser General Public License) Price:
1363 downloads
Ultimate Edition Theme Pack Final 2.3 Pre-release
Ultimate Edition Theme Pack Final brings you Ultimate Edition themes, login screens, wallpapers and more... more>> Ultimate Edition Theme Pack Final 2.3 Pre-release brings you extremely nice themes, login screens, wallpapers and more... Ultimate Edition Theme Pack Final contains 2 Themes (Carbon gold default), 2 Login (GDMs), 10 Wallpapers, 2 icons set, 1 Usplash (x86 and x64), Ultimate Edition Cursor set, and sound scheme used in Ultimate Edition 2.1.
How to install?
- Right click on your desktop and select Change Desktop Background
- Click on the first tab: Theme
- Drag and drop the themes archive in the Appearance Preferences window.
- If everything is OK, you will receive a confirmation message and you can activate the theme just by clicking on it.
Requirements: GNOME
Added: 2009-06-26 License: GPL Price: FREE
1 downloads
Linux on the WRT54G 0.61
Linux on the WRT54G is a mini-distribution for the router and access point Linksys wrt54g 802.11b/g more>>
Linux on the WRT54G is a mini-distribution for the router and access point Linksys wrt54g 802.11b/g
It includes basic tools such as sh, syslog, telnetd, httpd (with cgi-bin support), vi, snort, mount, insmod, rmmod, top, grep, find, nfs modules, etc.
The installation script runs in about 20 seconds and installs strictly to the RAM disk. If you mess anything up, simply reset the box.
After installing the distribution youll be able to telnet in, add Web pages, change iptable rules, change routing, configure snort, etc.
Quick Install:
Modify the IP and password in wrt54g.sh and run it. For more
information, See README, and the details in wrt54g.sh.
Make sure that the WAN port on the box is configured. To verify that your box
is set up properly, test the stanard Linksys ping diagostic. If you can "ping"
something on the Internet using this screen, you should be good to go.
<<lessIt includes basic tools such as sh, syslog, telnetd, httpd (with cgi-bin support), vi, snort, mount, insmod, rmmod, top, grep, find, nfs modules, etc.
The installation script runs in about 20 seconds and installs strictly to the RAM disk. If you mess anything up, simply reset the box.
After installing the distribution youll be able to telnet in, add Web pages, change iptable rules, change routing, configure snort, etc.
Quick Install:
Modify the IP and password in wrt54g.sh and run it. For more
information, See README, and the details in wrt54g.sh.
Make sure that the WAN port on the box is configured. To verify that your box
is set up properly, test the stanard Linksys ping diagostic. If you can "ping"
something on the Internet using this screen, you should be good to go.
Download (2.4MB)
Added: 2007-01-04 License: GPL (GNU General Public License) Price:
1033 downloads
Tao Linux 4-update2
Tao Linux is one of several projects to build a free Linux distribution from the sources used in the Red Hat Enterprise. more>>
Tao Linux (pronounced dow Linux) is a project to build a free Linux distribution from the sources used in the Red Hat Enterprise Linux product line.
The target market is either experienced system administrators who would like freely available binaries of this code, or end users who are interested in experimenting with enterprise functionality.
Besides being mostly compatible with Red Hat Enterprise Linux 3, it also includes software packages such as Eclipse and clustering tools not found in the base RHEL products.
Main features:
- Includes gcj-compiled Eclipse IDE
- Includes clustering tools
- Yum with protectbase patch for safer use of 3rd-party repos
- Supports ACLs in ext3, nfs and Samba
- Many packages for Red Hat Enterprise Linux also run on Tao Linux
- Free as in speech and beer
- Security updates (in SRPM form, at least) available into 2008
<<lessThe target market is either experienced system administrators who would like freely available binaries of this code, or end users who are interested in experimenting with enterprise functionality.
Besides being mostly compatible with Red Hat Enterprise Linux 3, it also includes software packages such as Eclipse and clustering tools not found in the base RHEL products.
Main features:
- Includes gcj-compiled Eclipse IDE
- Includes clustering tools
- Yum with protectbase patch for safer use of 3rd-party repos
- Supports ACLs in ext3, nfs and Samba
- Many packages for Red Hat Enterprise Linux also run on Tao Linux
- Free as in speech and beer
- Security updates (in SRPM form, at least) available into 2008
Download (2033MB)
Added: 2005-10-27 License: GPL (GNU General Public License) Price:
1458 downloads
Hyperic SIGAR 1.4
Hyperic SIGAR is a System Information Gatherer and Reporter. more>>
Hyperic SIGAR (System Information Gatherer and Reporter) is a cross-platform, cross-language library and command-line tool for accessing operating system and hardware level information in Java, Perl and .NET.
Hyperic developed SIGAR to overcome the lack of portable access to low-level hardware and operating system metrics found in the Java platform. Its now a key component of the Hyperic HQ management platform since it provides HQ with visibility into things that are otherwise impossible to get to through the standard Java API.
Over the last four years of development, weve enhanced SIGAR to support multiple language bindings and operate on more than 10 OS/hardware combinations.
We think other applications would benefit from the type of information SIGAR provides. We also want to create and foster a community of users who will help us push this technology forward and incorporate it into both open source and commercial applications. So we decided to make this technology open source to give others the ability to enhance their applications.
Main features:
- System memory statistics - total, free, shared
- CPU statistics - load averages, user cpu, system cpu
- Process level statistics - process arguments, memory consumption, cpu consumption, credential info, state, environment, open file descriptors
- File system level statistics - local and remote mounted file systems (NTFS, ext, SMB, NFS, etc), capacity, utilization
- Network interface level statistics - all available network interfaces detected and monitored for bytes received/transmitted, packets received/transmitted, collisions, errors, dropped packets
Enhancements:
- Improved performance and efficiency.
- A bug with User Mode Linux VMs where SIGAR acquired incorrect CPU info has been fixed.
<<lessHyperic developed SIGAR to overcome the lack of portable access to low-level hardware and operating system metrics found in the Java platform. Its now a key component of the Hyperic HQ management platform since it provides HQ with visibility into things that are otherwise impossible to get to through the standard Java API.
Over the last four years of development, weve enhanced SIGAR to support multiple language bindings and operate on more than 10 OS/hardware combinations.
We think other applications would benefit from the type of information SIGAR provides. We also want to create and foster a community of users who will help us push this technology forward and incorporate it into both open source and commercial applications. So we decided to make this technology open source to give others the ability to enhance their applications.
Main features:
- System memory statistics - total, free, shared
- CPU statistics - load averages, user cpu, system cpu
- Process level statistics - process arguments, memory consumption, cpu consumption, credential info, state, environment, open file descriptors
- File system level statistics - local and remote mounted file systems (NTFS, ext, SMB, NFS, etc), capacity, utilization
- Network interface level statistics - all available network interfaces detected and monitored for bytes received/transmitted, packets received/transmitted, collisions, errors, dropped packets
Enhancements:
- Improved performance and efficiency.
- A bug with User Mode Linux VMs where SIGAR acquired incorrect CPU info has been fixed.
Download (1.7MB)
Added: 2007-04-20 License: GPL (GNU General Public License) Price:
920 downloads
Linux NFS Utilities 1.1.0
Linux NFS Utilities is NFS utilities for Linux NFS clients and servers. more>>
Linux NFS Utilities are NFS utilities for Linux NFS clients and servers.
Main features:
- NFS Versions 2, 3, and 4 are supported on 2.6 and later kernels.
- NFS over UDP and TCP on IPv4 are supported on the latest 2.4 and 2.6 kernels.
- Linux NFS clients and servers have been tested against many non-Linux implementations.
- Since version 1.0.1 of the NFS utilities tarball has changed the server export default to "sync", then, if no behavior is specified in the export list (thus assuming the default behavior), a warning will be generated at export time.
- If you plan to deploy NFS extensively, consider subscribing to one of these mailing lists: NFS Mailing List, or the AutoFS Mailing List. Before reporting problems, you should search for similar issues in the searchable mail archive. Another searchable archive for NFS, supported by Google, is here. The searchable mail archive for AutoFS is here.
- A useful set of generic NFS references includes the following:
- - "NFS Illustrated," by Brent Callaghan; Addison-Wesley, 2000.
- - "Managing NFS and NIS, 2nd edition," by Hal Stern, Mike Eisler, Ricardo Labiaga; OReilly, 2001.
- - "Linux NFS and Automounter Administration," by Erez Zadok; Sybex, 2001.
- - "Using the Linux NFS Client with Network Appliance Filers," by Charles Lever; Netapp TR-3183, 2004.
- - "Mike Eislers NFS blog."
- - "Eric Kustarzs blog."
- - "NFS version 4 home page."
- - Finally, the "linux.org online library" has many references.
Quick setup client guide
1. Acquire and install a recent distribution of Linux.
2. Set up your /etc/exports file (man exports for details).
3. Consult your distributions documentation to determine which /etc/init.d start-up script is used to start your server. Start NFS services by invoking this script as root, using the "start" parameter. Consider adding this script to the list of scripts that are automatically run at system start-up. (Red Hat uses the chkconfig command for this purpose).
4. Read the NFS How-To for advice on tuning and securing your server.
Quick Client Setup Guide
1. Acquire and install a recent distribution of Linux. To enable NLM lock recovery, ensure your clients host name, as returned by uname -n, matches the host name returned by DNS.
2. The NLM protocol is handled by an in-kernel service in modern kernels, but the user-level rpc.statd program must be running to enable NLM lock recovery. Consult your distributions documentation to determine which /etc/init.d start-up script is used to start it. Start the NSM daemon by invoking this script as root, using the "start" parameter. Consider adding this script to the list of scripts that are automatically run at system start-up. (Red Hat uses the chkconfig command for this purpose).
3. Create the directories on your client where you will mount the NFS shares.
4. Add entries in /etc/fstab corresponding to your mount points (man nfs for details).
5. Use mount -a -t nfs to mount the NFS shares.
6. During system boot-up, most distributions automatically mount NFS shares that are listed in /etc/fstab. If yours doesnt, check your distributions documentation for instructions on how to configure your client to do this.
Enhancements:
- The "mount.nfs" command was added, since the nfs mount functionality is being migrated from util-linux to nfs-utils.
- Substantial changes to were made statd. Various pieces of old code were removed.
- Lots of bugfixes and improvements were made.
<<lessMain features:
- NFS Versions 2, 3, and 4 are supported on 2.6 and later kernels.
- NFS over UDP and TCP on IPv4 are supported on the latest 2.4 and 2.6 kernels.
- Linux NFS clients and servers have been tested against many non-Linux implementations.
- Since version 1.0.1 of the NFS utilities tarball has changed the server export default to "sync", then, if no behavior is specified in the export list (thus assuming the default behavior), a warning will be generated at export time.
- If you plan to deploy NFS extensively, consider subscribing to one of these mailing lists: NFS Mailing List, or the AutoFS Mailing List. Before reporting problems, you should search for similar issues in the searchable mail archive. Another searchable archive for NFS, supported by Google, is here. The searchable mail archive for AutoFS is here.
- A useful set of generic NFS references includes the following:
- - "NFS Illustrated," by Brent Callaghan; Addison-Wesley, 2000.
- - "Managing NFS and NIS, 2nd edition," by Hal Stern, Mike Eisler, Ricardo Labiaga; OReilly, 2001.
- - "Linux NFS and Automounter Administration," by Erez Zadok; Sybex, 2001.
- - "Using the Linux NFS Client with Network Appliance Filers," by Charles Lever; Netapp TR-3183, 2004.
- - "Mike Eislers NFS blog."
- - "Eric Kustarzs blog."
- - "NFS version 4 home page."
- - Finally, the "linux.org online library" has many references.
Quick setup client guide
1. Acquire and install a recent distribution of Linux.
2. Set up your /etc/exports file (man exports for details).
3. Consult your distributions documentation to determine which /etc/init.d start-up script is used to start your server. Start NFS services by invoking this script as root, using the "start" parameter. Consider adding this script to the list of scripts that are automatically run at system start-up. (Red Hat uses the chkconfig command for this purpose).
4. Read the NFS How-To for advice on tuning and securing your server.
Quick Client Setup Guide
1. Acquire and install a recent distribution of Linux. To enable NLM lock recovery, ensure your clients host name, as returned by uname -n, matches the host name returned by DNS.
2. The NLM protocol is handled by an in-kernel service in modern kernels, but the user-level rpc.statd program must be running to enable NLM lock recovery. Consult your distributions documentation to determine which /etc/init.d start-up script is used to start it. Start the NSM daemon by invoking this script as root, using the "start" parameter. Consider adding this script to the list of scripts that are automatically run at system start-up. (Red Hat uses the chkconfig command for this purpose).
3. Create the directories on your client where you will mount the NFS shares.
4. Add entries in /etc/fstab corresponding to your mount points (man nfs for details).
5. Use mount -a -t nfs to mount the NFS shares.
6. During system boot-up, most distributions automatically mount NFS shares that are listed in /etc/fstab. If yours doesnt, check your distributions documentation for instructions on how to configure your client to do this.
Enhancements:
- The "mount.nfs" command was added, since the nfs mount functionality is being migrated from util-linux to nfs-utils.
- Substantial changes to were made statd. Various pieces of old code were removed.
- Lots of bugfixes and improvements were made.
Download (0.77MB)
Added: 2007-05-11 License: GPL (GNU General Public License) Price:
910 downloads
TCFS 3.0b2
TCFS is a transparent cryptographic file system. more>>
TCFS project is a cryptographic network file system featuring group sharing of encrypted files. TCFS will encrypt your files before sending them to the file server and will decrypt them before they are read by the requesting application.
Because the encryption/decryption process takes place on the client host, no clean data will travel the network. This is particularly valid for the encryption key.
Recent advances in hardware and communication technologies have made possible and cost effective to share a file system among several machines over a local (but possibly also a wide) area network.
One of the most successful and widely used such applications is Suns Network File System (NFS).
NFS is very simple in structure but assumes a very strong trust model: the user trusts the remote file system server (which might be running on a machine in different country) and a network with his/her data. It is easy to see that neither assumption is a very realistic one.
The server (or anybody with superuser privileges) might very well read the data on its local filesytem and it is well known that the Internet or any local area network (e.g, Ethernet) is very easy to tap (see for example, Berkeleys tcpdump application program).
Impersonification of users is also another security drawback of NFS.
In fact, most of the permission checking over NFS are performed in the kernel of the client. In such a context a pirate can temporarely assign to his own workstation the Internet address of victim. Without secure RPC no further authentication procedure is requested. From here on, the pirate can issue NFS requests presenting himself with any (false) uid and therefore accessing for reading and writing any private data on the server, even protected data.
Given the above, a user seeking a certain level of security should take some measures. We propose a new cryptographic file system, which we call TCFS, as a suitable solution to the problem of privacy for distributed file system.
Dynamic Encryption Modules in TCFS:
The dynamic encryption module feature of TCFS allows a user to specify the encryption engine of his/her choiche to be used by TCFS. So you are not forced anymore to use what us (the developer) consider the best (i.e., more secure and efficient) encryption algorithm. The encryption engine must be given in the form of a Linux module and must conform to (the very simple) TCFS API for encryption module. Essentially, it must specify four functions:
1. An initialization function that is called by TCFS when the user pushes her key into TCFS.
Typically the initialization function takes as input the key and returns a pointer to a struct containing a the result of a preprocessing of the key to be used for the encryption and the decryption.
For the specific case of DES the initialization function computes the 16 48-bit subkeys, one for each round of DES.
2. An encryption function which takes a block of data, the length of the block in bytes and the result of the initialization function and encrypts the data.
3. A decryption function which takes a block of data, the length of the block in bytes and the result of the initialization function and decrypts the data.
The encryption and the decryption functions are called each time TCFS needs to read/write a block of data.
4. A cleanup function which performs whatever operation is needed before the key removed by TCFS.
Our work improves on Matt Blazes CFS by providing deeper integration between the encryption service and the file system which results in a complete transparency of use to the user applications.
Release 2.2 of TCFS includes the possibility of threshold sharing files among users. Threshold sharing consists in specifying a minimum number of members (the threshold) that need to be ``active for the files owned by the group to become available.
TCFS enforces the threshold sharing by generating an encryption key for each group and giving each member of the group a share using a Threshold Secret Sharing Scheme. The group encryption key can be reconstructed by any set of at least threshold keys.
A member of the group that intends to become active does so by pushing her/his share of the group key into the kernel. The TCFS module checks if the number of shares available is above the threshold and, if it is so, it attempts to reconstruct the group encryption key. By the properties of the Threshold Secret Sharing Scheme, it is guaranteed that, if enough shares are available, the group encryption key is correctly reconstructed.
Once the group encryption key has been reconstructed, the files owned by the group become accessible. Each time a member decides to become inactive, her share of the group encryption key is removed. The TCFS module checks if the number of shares available has gone under the threshold. In this case, the group encryption key is removed from the TCFS module and files owned by the group become unaccessible.
The current TCFS implementation of the group sharing facility requires each memeber to trust the kernel of the machine that reconstructs the key to actually remove the key once the number of active users goes below the threshold. Future implementations will remove this requirement by performing the reconstruction of the key in a distributed manner.
<<lessBecause the encryption/decryption process takes place on the client host, no clean data will travel the network. This is particularly valid for the encryption key.
Recent advances in hardware and communication technologies have made possible and cost effective to share a file system among several machines over a local (but possibly also a wide) area network.
One of the most successful and widely used such applications is Suns Network File System (NFS).
NFS is very simple in structure but assumes a very strong trust model: the user trusts the remote file system server (which might be running on a machine in different country) and a network with his/her data. It is easy to see that neither assumption is a very realistic one.
The server (or anybody with superuser privileges) might very well read the data on its local filesytem and it is well known that the Internet or any local area network (e.g, Ethernet) is very easy to tap (see for example, Berkeleys tcpdump application program).
Impersonification of users is also another security drawback of NFS.
In fact, most of the permission checking over NFS are performed in the kernel of the client. In such a context a pirate can temporarely assign to his own workstation the Internet address of victim. Without secure RPC no further authentication procedure is requested. From here on, the pirate can issue NFS requests presenting himself with any (false) uid and therefore accessing for reading and writing any private data on the server, even protected data.
Given the above, a user seeking a certain level of security should take some measures. We propose a new cryptographic file system, which we call TCFS, as a suitable solution to the problem of privacy for distributed file system.
Dynamic Encryption Modules in TCFS:
The dynamic encryption module feature of TCFS allows a user to specify the encryption engine of his/her choiche to be used by TCFS. So you are not forced anymore to use what us (the developer) consider the best (i.e., more secure and efficient) encryption algorithm. The encryption engine must be given in the form of a Linux module and must conform to (the very simple) TCFS API for encryption module. Essentially, it must specify four functions:
1. An initialization function that is called by TCFS when the user pushes her key into TCFS.
Typically the initialization function takes as input the key and returns a pointer to a struct containing a the result of a preprocessing of the key to be used for the encryption and the decryption.
For the specific case of DES the initialization function computes the 16 48-bit subkeys, one for each round of DES.
2. An encryption function which takes a block of data, the length of the block in bytes and the result of the initialization function and encrypts the data.
3. A decryption function which takes a block of data, the length of the block in bytes and the result of the initialization function and decrypts the data.
The encryption and the decryption functions are called each time TCFS needs to read/write a block of data.
4. A cleanup function which performs whatever operation is needed before the key removed by TCFS.
Our work improves on Matt Blazes CFS by providing deeper integration between the encryption service and the file system which results in a complete transparency of use to the user applications.
Release 2.2 of TCFS includes the possibility of threshold sharing files among users. Threshold sharing consists in specifying a minimum number of members (the threshold) that need to be ``active for the files owned by the group to become available.
TCFS enforces the threshold sharing by generating an encryption key for each group and giving each member of the group a share using a Threshold Secret Sharing Scheme. The group encryption key can be reconstructed by any set of at least threshold keys.
A member of the group that intends to become active does so by pushing her/his share of the group key into the kernel. The TCFS module checks if the number of shares available is above the threshold and, if it is so, it attempts to reconstruct the group encryption key. By the properties of the Threshold Secret Sharing Scheme, it is guaranteed that, if enough shares are available, the group encryption key is correctly reconstructed.
Once the group encryption key has been reconstructed, the files owned by the group become accessible. Each time a member decides to become inactive, her share of the group encryption key is removed. The TCFS module checks if the number of shares available has gone under the threshold. In this case, the group encryption key is removed from the TCFS module and files owned by the group become unaccessible.
The current TCFS implementation of the group sharing facility requires each memeber to trust the kernel of the machine that reconstructs the key to actually remove the key once the number of active users goes below the threshold. Future implementations will remove this requirement by performing the reconstruction of the key in a distributed manner.
Download (0.085MB)
Added: 2007-04-12 License: GPL (GNU General Public License) Price:
927 downloads
Hard Token Management Framework 1.0 Beta 2
Hard Token Management Framework is used to manage the complete livecycle of an organizations Smartcard and/or USB dongles. more>>
Hard Token Management Framework is used to manage the complete livecycle of an organizations Smartcard and/or USB dongles.
It communicates with the tokens through a PKCS11 interface so it is possible to change hardware as long as they supply it with a good implementation of PKCS11.
It comes along quite with a few ready made modules that can be composed to fit the need of the organization. The Hard Token Management Framework is an Add-on to EJBCA Certificate Authority (see http://www.ejbca.org).
Main features:
- Support of Setec 4.3.1 and 4.4.1 cards (TODO check)
- Issuing cards with 1 or more certificates
- Support for 2 PIN, basic and signature
- Contains a Card Analyser that analyses the card for the card administrator to give a suggestion of what is wrong with the card
- Possibilty to issue ordinary, temporary and project cards with different validities
- When a ordinary or project card is generated is all previous cards revoked
- When a temporary card is issued is the ordinary card set on hold until the ordinary card is reactivated
- Userdata is fetched from existing user data source.
- Possibility to unlock cards without exposing the PUK. The PUK is stored encrypted in EJBCA database.
- Easy to renew an expiring card
- Cards not used anymore can be revoked and ereased.
- It is also possible for a card administrator to do some management remotely (without having the card) such as revoking and activating a ordinary card.
- For 24/7 working environments where a card administrator might not be available it is possible for a colleague to issue a card unlock or issue temporary card request that is sent to a central support unit for approval
- TaLiMa also have error reporting functionality where unexpected error can be sent to the technical administrators for analysis
Enhancements:
Bug:
- [HTMF-2] - Wrong error message analysing card
- [HTMF-10] - Applet works badly when closing and reloading the page
- [HTMF-11] - Only jdk 1.6 can be used to build, Arrays method used not supported in 1.5
Improvement:
- [HTMF-8] - Support certificates generated by other CAs
New Feature:
- [HTMF-12] - Check if card data is uploaded to DB during analysis
<<lessIt communicates with the tokens through a PKCS11 interface so it is possible to change hardware as long as they supply it with a good implementation of PKCS11.
It comes along quite with a few ready made modules that can be composed to fit the need of the organization. The Hard Token Management Framework is an Add-on to EJBCA Certificate Authority (see http://www.ejbca.org).
Main features:
- Support of Setec 4.3.1 and 4.4.1 cards (TODO check)
- Issuing cards with 1 or more certificates
- Support for 2 PIN, basic and signature
- Contains a Card Analyser that analyses the card for the card administrator to give a suggestion of what is wrong with the card
- Possibilty to issue ordinary, temporary and project cards with different validities
- When a ordinary or project card is generated is all previous cards revoked
- When a temporary card is issued is the ordinary card set on hold until the ordinary card is reactivated
- Userdata is fetched from existing user data source.
- Possibility to unlock cards without exposing the PUK. The PUK is stored encrypted in EJBCA database.
- Easy to renew an expiring card
- Cards not used anymore can be revoked and ereased.
- It is also possible for a card administrator to do some management remotely (without having the card) such as revoking and activating a ordinary card.
- For 24/7 working environments where a card administrator might not be available it is possible for a colleague to issue a card unlock or issue temporary card request that is sent to a central support unit for approval
- TaLiMa also have error reporting functionality where unexpected error can be sent to the technical administrators for analysis
Enhancements:
Bug:
- [HTMF-2] - Wrong error message analysing card
- [HTMF-10] - Applet works badly when closing and reloading the page
- [HTMF-11] - Only jdk 1.6 can be used to build, Arrays method used not supported in 1.5
Improvement:
- [HTMF-8] - Support certificates generated by other CAs
New Feature:
- [HTMF-12] - Check if card data is uploaded to DB during analysis
Download (12.5MB)
Added: 2007-08-10 License: LGPL (GNU Lesser General Public License) Price:
808 downloads
Volume Sharing Manager 1.35
Volume Sharing Manager (Vsman) is a utility that has been designed for volume (directory) sharing management on the server side. more>>
Volume Sharing Manager (Vsman) is a utility that has been designed for volume (directory) sharing management on the server side. So far, it manages NFS v3 and V4, but can be extended to others volume sharing systems.
You can select a NFS v4 server interface in the preferences dialog box. Otherwise, invoke vsman with the flag -4 in order to display the NFS v4 specific mounting options when needed.
Vsman must be run as root. It displays on the left a tree view of known directories with their possible accesses, i.e. client hosts that can mount directories from the server where vsman is running.
Each directory is displayed with a green, yellow or red spot.
Green if the directory is exported but not mounted.
Yellow when exported and mounted.
Red when unexported.
When you double-click on an access, the left side shows its mounting options.
You can obviously declare a new volume. Vsman just asks you the name of the corresponding directory. You can of course create or delete accesses for the current volume. When you create one, a dialog box appears, that asks you the suitable host name, network
name or address, or netgroup name.
If the host filed is empty, the networks field is then tested, and if empty again, the netgroup is selected.
If you select "NIS" instead of "Files" in the preferences dialog box, the hosts, networks, users and groups will be fetched from the given NIS domain name. For more info about NIS, read the corresponding HOWTO documentation.
Selecting the Reexport menu will reexport all and synchronize vsman with the exported volumes declared in /etc/exports.
Double-click on a mounting host and select Unexport Host in the Action menu, and the current volume will be unexported from the corresponding volume.
Unexport whole volume will do the same thing, but for all the mounting hosts.
The Start / Stop menu will stop or restart the NFS server.
The Save menu will write the NFS /etc/exports file and reexport all volumes.
This tool has been written in Ada 95, using gtkada 2.4 as the toolkit. Dont forget to install gnat 4.1.x or later. Gnat is now a component of the gcc suite.
Enhancements:
- A few important bugs were fixed.
- Hostname lookup was added.
- The compilation and installation process was improved.
<<lessYou can select a NFS v4 server interface in the preferences dialog box. Otherwise, invoke vsman with the flag -4 in order to display the NFS v4 specific mounting options when needed.
Vsman must be run as root. It displays on the left a tree view of known directories with their possible accesses, i.e. client hosts that can mount directories from the server where vsman is running.
Each directory is displayed with a green, yellow or red spot.
Green if the directory is exported but not mounted.
Yellow when exported and mounted.
Red when unexported.
When you double-click on an access, the left side shows its mounting options.
You can obviously declare a new volume. Vsman just asks you the name of the corresponding directory. You can of course create or delete accesses for the current volume. When you create one, a dialog box appears, that asks you the suitable host name, network
name or address, or netgroup name.
If the host filed is empty, the networks field is then tested, and if empty again, the netgroup is selected.
If you select "NIS" instead of "Files" in the preferences dialog box, the hosts, networks, users and groups will be fetched from the given NIS domain name. For more info about NIS, read the corresponding HOWTO documentation.
Selecting the Reexport menu will reexport all and synchronize vsman with the exported volumes declared in /etc/exports.
Double-click on a mounting host and select Unexport Host in the Action menu, and the current volume will be unexported from the corresponding volume.
Unexport whole volume will do the same thing, but for all the mounting hosts.
The Start / Stop menu will stop or restart the NFS server.
The Save menu will write the NFS /etc/exports file and reexport all volumes.
This tool has been written in Ada 95, using gtkada 2.4 as the toolkit. Dont forget to install gnat 4.1.x or later. Gnat is now a component of the gcc suite.
Enhancements:
- A few important bugs were fixed.
- Hostname lookup was added.
- The compilation and installation process was improved.
Download (0.25MB)
Added: 2006-12-03 License: GPL (GNU General Public License) Price:
1057 downloads
Termlock 1.0.1
Termlock project blanks a curses compatible character terminal (e.g. xterm, eterm, PuTTY, konsole, dtterm, etc ...) and locks it more>>
Termlock project blanks a curses compatible character terminal (e.g. xterm, eterm, PuTTY, konsole, dtterm, etc ...) and locks it. To unlock the terminal a password must be entered. The password, or rather the password hash, is stored in ~/.termlock.
Basically its like a password protected screensaver for character terminals. Written in pure Python it should be immediately usable on any machine with Python and curses (or a compatible library such as ncurses) installed.
Usage:
termlock [-p | --password]
The password switch prompts the user for a password (which must be confirmed) and uses this to create the ~/.termlock hash file.
To lock the screen simply call termlock with no options. If no ~/.termlock file can be found then an error prompting the user to create it will be displayed
Install:
Termlock uses the standard Python distribution utilities. So it should just be a case of uncompressing the archive and running:
./setup.py install
Obviously the user running this must have sufficient permissions to create a file in the install directory.
<<lessBasically its like a password protected screensaver for character terminals. Written in pure Python it should be immediately usable on any machine with Python and curses (or a compatible library such as ncurses) installed.
Usage:
termlock [-p | --password]
The password switch prompts the user for a password (which must be confirmed) and uses this to create the ~/.termlock hash file.
To lock the screen simply call termlock with no options. If no ~/.termlock file can be found then an error prompting the user to create it will be displayed
Install:
Termlock uses the standard Python distribution utilities. So it should just be a case of uncompressing the archive and running:
./setup.py install
Obviously the user running this must have sufficient permissions to create a file in the install directory.
Download (0.010MB)
Added: 2007-04-11 License: GPL (GNU General Public License) Price:
927 downloads
Etherboot 5.4.3
Etherboot is a source code for making IP boot ROMs to boot Linux and other OSes. more>>
Etherboot project is a software package for creating ROM images that can download code over an Ethernet network to be executed on an x86 computer.
Many network adapters have a socket where a ROM chip can be installed. Etherboot is code that can be put in such a ROM. Etherboot is normally used for for booting PCs diskless. This is useful in various situations, for example:
- An X-terminal.
- Clusters of compute servers.
- Routers.
- Various kinds of remote servers, e.g. a tape drive server that can be accessed with the RMT protocol.
- Machines doing tasks in environments unfriendly to disks.
- A user platform where remote partitions are mounted over the network and you are willing to accept the lower speed compared to disk.
- Maintaining software for a cluster of equally configured workstations centrally.
Etherboot can boot computers faster than from a disk because there are no delays in spinning up disks, etc. A moments calculation will show that even with a 10Mbit Ethernet, sending a 500kB kernel will take only a couple of seconds typically. With 100Mbit Ethernet it gets even better.
Compared to booting from solid-state devices, e.g. Flash disks, Etherboot has the advantage of centralising software adminstration, the tradeoff being the dependence on a server. This can be partly alleviated by providing redundant servers.
Etherboot can work with RAM disks, NFS filesystems, or even local disks, if desired. Its a component technology and can be combined with other technologies to do things the way you want.
Etherboot is usually used to load Linux, FreeBSD or DOS. However the protocol and boot file formats are general, so there is no reason why it could not be used to load arbitrary images to a PC, including other OSes.
Etherboot is Open Source under the GNU General Public License Version 2 (GPL2).
The components needed by Etherboot are:
- A bootstrap loader, usually in an EPROM on a network card, or installed in the flash BIOS, but could be put anywhere in the address space the BIOS probes in. For testing this could be put on a floppy disk or a hard disk partition. Some configurations may even be always run from a floppy disk (e.g. temporary testing setups or pedagogic uses).
- A DHCP or bootp server, for returning an IP address and other information when sent a MAC (Ethernet card) address.
- A tftp server, for sending the kernel images and other files required in the boot process. Alternatively, Etherboot can boot from an NFS mount.
- A Linux or FreeBSD kernel.
- Optionally, a NFS server, for providing the disk partitions that will be mounted if Linux or FreeBSD is being booted.
- Optionally, a RAM disk contained in the loaded image. This can be the initial RAM disk if desired.
- Software tools for building the download image, and tools for debugging.
Enhancements:
- This production release should now compile with gcc 4.x.
- In addition, a number of drivers have been updated, including e1000, MCP51 and MCP55 (nvidia), pcnet32, natsemi, sis900, and tg3.
- NetXtreme II cards are now supported.
<<lessMany network adapters have a socket where a ROM chip can be installed. Etherboot is code that can be put in such a ROM. Etherboot is normally used for for booting PCs diskless. This is useful in various situations, for example:
- An X-terminal.
- Clusters of compute servers.
- Routers.
- Various kinds of remote servers, e.g. a tape drive server that can be accessed with the RMT protocol.
- Machines doing tasks in environments unfriendly to disks.
- A user platform where remote partitions are mounted over the network and you are willing to accept the lower speed compared to disk.
- Maintaining software for a cluster of equally configured workstations centrally.
Etherboot can boot computers faster than from a disk because there are no delays in spinning up disks, etc. A moments calculation will show that even with a 10Mbit Ethernet, sending a 500kB kernel will take only a couple of seconds typically. With 100Mbit Ethernet it gets even better.
Compared to booting from solid-state devices, e.g. Flash disks, Etherboot has the advantage of centralising software adminstration, the tradeoff being the dependence on a server. This can be partly alleviated by providing redundant servers.
Etherboot can work with RAM disks, NFS filesystems, or even local disks, if desired. Its a component technology and can be combined with other technologies to do things the way you want.
Etherboot is usually used to load Linux, FreeBSD or DOS. However the protocol and boot file formats are general, so there is no reason why it could not be used to load arbitrary images to a PC, including other OSes.
Etherboot is Open Source under the GNU General Public License Version 2 (GPL2).
The components needed by Etherboot are:
- A bootstrap loader, usually in an EPROM on a network card, or installed in the flash BIOS, but could be put anywhere in the address space the BIOS probes in. For testing this could be put on a floppy disk or a hard disk partition. Some configurations may even be always run from a floppy disk (e.g. temporary testing setups or pedagogic uses).
- A DHCP or bootp server, for returning an IP address and other information when sent a MAC (Ethernet card) address.
- A tftp server, for sending the kernel images and other files required in the boot process. Alternatively, Etherboot can boot from an NFS mount.
- A Linux or FreeBSD kernel.
- Optionally, a NFS server, for providing the disk partitions that will be mounted if Linux or FreeBSD is being booted.
- Optionally, a RAM disk contained in the loaded image. This can be the initial RAM disk if desired.
- Software tools for building the download image, and tools for debugging.
Enhancements:
- This production release should now compile with gcc 4.x.
- In addition, a number of drivers have been updated, including e1000, MCP51 and MCP55 (nvidia), pcnet32, natsemi, sis900, and tg3.
- NetXtreme II cards are now supported.
Download (1.1MB)
Added: 2007-02-25 License: GPL (GNU General Public License) Price:
993 downloads
Autofs NG 0.4.1
Autofs NG is an autofs automounter for Linux that strives to be interoperable. more>>
Autofs NG is a Linux automounter that is intended to be completely interoperable with autofs implementations on other Unix platforms. As such, it supports some features that the current Linux automounters do not.
This includes direct mounts, /net (--hosts access), lazy mounting and unmounting of hierarchical multimounts, and browsing. Autofsng also supports the usual indirect map support available elsewhere.
Maps are supported from flat files, executable maps, NIS maps, NIS+ maps, LDAP maps, and hesiod (DNS) filsys namespace.
AutofsNG was originally developed at Sun Microsystems, but has been cancelled as a project. Fortunately, it has been released as GPL, so I am continuing its development in my spare time.
Enhancements:
- Initscript fixup for path to /proc/mounts
- We no longer update /etc/mtab because the kernel does all unmounting. Current recommendation is to symlink /proc/mounts to /etc/mtab if you want to see the what is actually mounted with calling mount
- Fixed SuSE/LSB initscript issue where ypbind wasnt neccesarily started before autofsng.
- Added an RPM .spec file to the tree.
- Fixed initscript install
- Fixed possible crash when using the -hosts map.
- Redimentary mount option translation. Currently translates the common Solaris NFS mount options to Linux specific ones. Hard-coded.
- Initscript fixups for unknown systems (Debian in particular)
- Fixed a bug where the -hosts map would return duplicate map offsets, which is a semantic error for usual entries.
<<lessThis includes direct mounts, /net (--hosts access), lazy mounting and unmounting of hierarchical multimounts, and browsing. Autofsng also supports the usual indirect map support available elsewhere.
Maps are supported from flat files, executable maps, NIS maps, NIS+ maps, LDAP maps, and hesiod (DNS) filsys namespace.
AutofsNG was originally developed at Sun Microsystems, but has been cancelled as a project. Fortunately, it has been released as GPL, so I am continuing its development in my spare time.
Enhancements:
- Initscript fixup for path to /proc/mounts
- We no longer update /etc/mtab because the kernel does all unmounting. Current recommendation is to symlink /proc/mounts to /etc/mtab if you want to see the what is actually mounted with calling mount
- Fixed SuSE/LSB initscript issue where ypbind wasnt neccesarily started before autofsng.
- Added an RPM .spec file to the tree.
- Fixed initscript install
- Fixed possible crash when using the -hosts map.
- Redimentary mount option translation. Currently translates the common Solaris NFS mount options to Linux specific ones. Hard-coded.
- Initscript fixups for unknown systems (Debian in particular)
- Fixed a bug where the -hosts map would return duplicate map offsets, which is a semantic error for usual entries.
Download (0.085MB)
Added: 2005-04-08 License: GPL (GNU General Public License) Price:
1659 downloads
File::NFSLock 1.20
File::NFSLock is a Perl module to do NFS (or not) locking. more>>
File::NFSLock is a Perl module to do NFS (or not) locking.
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
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
Download (0.018MB)
Added: 2007-04-27 License: Perl Artistic License Price:
912 downloads
Pam_smbmount 0.3.1
Pam_smbmount is software that mounts file systems for user sessions. more>>
Pam_smbmount is software that mounts file systems for user sessions. The project consists of a pluggable authentication module, daemon psmd and a psmount utility. Pam_smbmount is intended for servers with simultaneously working users. Currently it supports following file systems:
smbfs
any file systems that does not require user password for mounting (ext3, ntfs, nfs ...)
Main features:
- mount volumes when user starts session
- unmount volumes when user exits from system
- configure users that are allowed to mount particular volume(s) in configuration file
- exclude any part of user name when mounting volumes
- use special variables in configuration file in volume arguments
Advantages of pam_smbmount:
- Uses utmp database to decide whether user has logged off
- Hold database of mounted volumes per user. This feature permits usage of pam_smbmount on multi-user servers
- Mounts any amount of volumes without essential delay of authentication process
- Tries to remount volume if first attempt failed. You can set amount of tries in configuration file
- Doesnt stop unmounting volume if first attempt failed
<<lesssmbfs
any file systems that does not require user password for mounting (ext3, ntfs, nfs ...)
Main features:
- mount volumes when user starts session
- unmount volumes when user exits from system
- configure users that are allowed to mount particular volume(s) in configuration file
- exclude any part of user name when mounting volumes
- use special variables in configuration file in volume arguments
Advantages of pam_smbmount:
- Uses utmp database to decide whether user has logged off
- Hold database of mounted volumes per user. This feature permits usage of pam_smbmount on multi-user servers
- Mounts any amount of volumes without essential delay of authentication process
- Tries to remount volume if first attempt failed. You can set amount of tries in configuration file
- Doesnt stop unmounting volume if first attempt failed
Download (MB)
Added: 2007-03-27 License: GPL (GNU General Public License) Price:
942 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above how to unlock the gt3rs in nfs carbon search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
