what is nfs
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 124
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
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
HA/FST 3.0.1
HA/FST is a high availability clustering tool for up to four Solaris nodes. more>>
HA/FST is a high availability clustering tool for up to four Solaris nodes. HA/FST project supports any application that can be managed from the command line.
HA/FST works similar to other HA tools. Heartbeats sent across a private network are monitored. If these heartbeats fail and subsequent checks across the public network fail then a failover can occur.
Additionally, each application is monitored at configurable intervals for soundness. Application failovers can trigger a restart or a failover.
HA/FST comes pre-equipped to support:
- Up to 4 nodes in cluster
- Application Fallback to Preferred Node
- Application Failover to a Preferred Node
- Remote Node Application Monitoring
- Event Notifications
- Network Interface Failover
- Apache
- NFS
- Oracle
- Samba
Enhancements:
Bug Fixes:
- Syntax error parsing -t option of fstmodapp prevented proper creation of application agents.
<<lessHA/FST works similar to other HA tools. Heartbeats sent across a private network are monitored. If these heartbeats fail and subsequent checks across the public network fail then a failover can occur.
Additionally, each application is monitored at configurable intervals for soundness. Application failovers can trigger a restart or a failover.
HA/FST comes pre-equipped to support:
- Up to 4 nodes in cluster
- Application Fallback to Preferred Node
- Application Failover to a Preferred Node
- Remote Node Application Monitoring
- Event Notifications
- Network Interface Failover
- Apache
- NFS
- Oracle
- Samba
Enhancements:
Bug Fixes:
- Syntax error parsing -t option of fstmodapp prevented proper creation of application agents.
Download (2.5MB)
Added: 2006-01-13 License: GPL (GNU General Public License) Price:
1380 downloads
Feather Linux 0.7.5
Feather Linux is a Linux distribution which runs completely off a CD or a USB pendrive and takes up under 115Mb of space. more>>
Feather Linux is a Linux distribution which runs completely off a CD or a USB pendrive and takes up under 115Mb of space.
Feather Linux is a Knoppix remaster (based on Debian), and tries to include software which most people would use every day on their desktop.
As of version 0.7.3, it includes:
Kernel 2.4.27, Abiword, siag, Dillo, Firefox, Captive-NTFS, gaim, ethereal, Thunderbird, XMMS and plugins, Imposter, IceWM, wavplay, mpg321, FreeNX, John the Ripper, Tcl, qemu, kismet, abcde, macchanger, screen, paketto, ogg123 and other Ogg Vorbis tools, axyFTP, fireftp, rox-filer, cdrecord, mkisofs, rdesktop, tcpdump, parted, partimage, dsniff, aircrack, madwifi, dnsmasq, foremost, antiword, e2undel, iftop, bbpager, utelnetd, minicom, index, gpart, socat, traceroute, SciTE, prozilla, Midnight Commander, Samba, elmo, tmsnc, apsfilter, gmplayer, mount.app, chntpw, zile, tinycc, nano, Xpaint, Xzgv, Xpdf, naim, hdparm, usbview, index, recoverdm, mtr, cdparanoia, betaftpd, Chipmunk Basic, gqcam, e3, lua, Ruby, cdparanoia, giFTcurs, mtools, emelfm2, vncdec, elhttp, quagga, ettercap, wavemon, iptables, recover, amap, hping2, cabextract, splitvt, pciutils, LinNeighborhood, nmap and nmapfe, portmap and nfs-common, aumix, CTorrent, VNCviewer, sqlite, SSH and SCP, DHCP client, xtdesktop, PPP and PPPoE support, NTFS resize support, an RSS reader, stress, cpuburn, the Monkey webserver, Xcalc, Fluxbox, evilwm, the XBase apps, and the various standard console and system tools.
Enhancements:
- Fixed HD install script
- Updated Gaim and Firefox
<<lessFeather Linux is a Knoppix remaster (based on Debian), and tries to include software which most people would use every day on their desktop.
As of version 0.7.3, it includes:
Kernel 2.4.27, Abiword, siag, Dillo, Firefox, Captive-NTFS, gaim, ethereal, Thunderbird, XMMS and plugins, Imposter, IceWM, wavplay, mpg321, FreeNX, John the Ripper, Tcl, qemu, kismet, abcde, macchanger, screen, paketto, ogg123 and other Ogg Vorbis tools, axyFTP, fireftp, rox-filer, cdrecord, mkisofs, rdesktop, tcpdump, parted, partimage, dsniff, aircrack, madwifi, dnsmasq, foremost, antiword, e2undel, iftop, bbpager, utelnetd, minicom, index, gpart, socat, traceroute, SciTE, prozilla, Midnight Commander, Samba, elmo, tmsnc, apsfilter, gmplayer, mount.app, chntpw, zile, tinycc, nano, Xpaint, Xzgv, Xpdf, naim, hdparm, usbview, index, recoverdm, mtr, cdparanoia, betaftpd, Chipmunk Basic, gqcam, e3, lua, Ruby, cdparanoia, giFTcurs, mtools, emelfm2, vncdec, elhttp, quagga, ettercap, wavemon, iptables, recover, amap, hping2, cabextract, splitvt, pciutils, LinNeighborhood, nmap and nmapfe, portmap and nfs-common, aumix, CTorrent, VNCviewer, sqlite, SSH and SCP, DHCP client, xtdesktop, PPP and PPPoE support, NTFS resize support, an RSS reader, stress, cpuburn, the Monkey webserver, Xcalc, Fluxbox, evilwm, the XBase apps, and the various standard console and system tools.
Enhancements:
- Fixed HD install script
- Updated Gaim and Firefox
Download (119.4MB)
Added: 2005-07-04 License: GPL (GNU General Public License) Price:
937 downloads
NATting SOHO firewall
NATting SOHO firewall is a firewall script for iptables. more>>
NATting SOHO firewall is a firewall script for iptables.
# Model NATting SOHO firewall for SP article
# by Jay Beale (jay@bastille-linux.org)
#
# Warning: youre going to have to hack this for your own purposes.
#
# Assumptions:
# your internal network is 192.168.1.0/24 on eth1
# your internet IP is 10.0.0.1 on eth0
# your internal network IP on eth1 is 192.168.1.1
#
# Additonally:
# you have another internal network, a DMZ: 192.168.2.0/24 on eth2
$INTERNAL_IP = 192.168.1.1
$INTERNAL_NET = 192.168.1.0/24
$INTERNET = 10.0.0.1
$DMZ = 192.168.2.0/24
# Insert the required kernel modules
modprobe iptable_nat
modprobe ip_conntrack
modprobe ip_conntrack_ftp
# Set default policies for packets going through this firewall box
iptables -t nat -P PREROUTING DROP
iptables -t nat -P POSTROUTING DROP
iptables -P FORWARD DROP
# Set default policies for packet entering this box
iptables -P OUTPUT ALLOW
iptables -P INPUT ALLOW
# Kill spoofed packets
for f in /proc/sys/net/ipv4/conf/*/rp_filter; do
echo 1 > $f
done
# Anything coming from our internal network should have only our addresses!
iptables -A FORWARD -i eth1 -s ! $INTERNAL_NET -j DROP
# Anything coming from the Internet should have a real Internet address
iptables -A FORWARD -i eth0 -s 192.168.0.0/16 -j DROP
iptables -A FORWARD -i eth0 -s 172.16.0.0/12 -j DROP
iptables -A FORWARD -i eth0 -s 10.0.0.0/8 -j DROP
# Note:There are more "reserved" networks, but these are the classical ones.
# Block outgoing network filesharing protocols that arent designed
# to leave the LAN
# SMB / Windows filesharing
iptables -A FORWARD -p tcp --sport 137:139 -j DROP
iptables -A FORWARD -p udp --sport 137:139 -j DROP
# NFS Mount Service (TCP/UDP 635)
iptables -A FORWARD -p tcp --sport 635 -j DROP
iptables -A FORWARD -p udp --sport 635 -j DROP
# NFS (TCP/UDP 2049)
iptables -A FORWARD -p tcp --sport 2049 -j DROP
iptables -A FORWARD -p udp --sport 2049 -j DROP
# Portmapper (TCP/UDP 111)
iptables -A FORWARD -p tcp --sport 111 -j DROP
iptables -A FORWARD -p udp --sport 111 -j DROP
# Block incoming syslog, lpr, rsh, rexec...
iptables -A FORWARD -i eth0 -p udp --dport syslog -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 515 -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 514 -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 512 -j DROP
###
# Transparently proxy all web-surfing through Squid box
$SQUID = 192.168.1.2:8080
$SQUIDSSL = 192.168.1.2:443
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 80 -j DNAT --to $SQUID
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 443 -j DNAT --to $SQUIDSSL
# Transparently forward all outgoing mail to a relay host
$SMTP = 192.168.1.3
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 25 -j DNAT --to $SMTP
# Transparently redirect web connections from outside to the DMZ web
# server
$DMZ_WEB = 192.168.2.2
iptables -t nat -A PREROUTING -i eth0 -d 192.168.1.1 -dport 80 -j DNAT --to $DMZ_WEB
# Source NAT to get Internet traffic through
iptables -t nat -A POSTROUTING -o eth1 -j SNAT --to $INTERNET
# Activate the forwarding!
echo 1 >/proc/sys/net/ipv4/ip_forward
<<less# Model NATting SOHO firewall for SP article
# by Jay Beale (jay@bastille-linux.org)
#
# Warning: youre going to have to hack this for your own purposes.
#
# Assumptions:
# your internal network is 192.168.1.0/24 on eth1
# your internet IP is 10.0.0.1 on eth0
# your internal network IP on eth1 is 192.168.1.1
#
# Additonally:
# you have another internal network, a DMZ: 192.168.2.0/24 on eth2
$INTERNAL_IP = 192.168.1.1
$INTERNAL_NET = 192.168.1.0/24
$INTERNET = 10.0.0.1
$DMZ = 192.168.2.0/24
# Insert the required kernel modules
modprobe iptable_nat
modprobe ip_conntrack
modprobe ip_conntrack_ftp
# Set default policies for packets going through this firewall box
iptables -t nat -P PREROUTING DROP
iptables -t nat -P POSTROUTING DROP
iptables -P FORWARD DROP
# Set default policies for packet entering this box
iptables -P OUTPUT ALLOW
iptables -P INPUT ALLOW
# Kill spoofed packets
for f in /proc/sys/net/ipv4/conf/*/rp_filter; do
echo 1 > $f
done
# Anything coming from our internal network should have only our addresses!
iptables -A FORWARD -i eth1 -s ! $INTERNAL_NET -j DROP
# Anything coming from the Internet should have a real Internet address
iptables -A FORWARD -i eth0 -s 192.168.0.0/16 -j DROP
iptables -A FORWARD -i eth0 -s 172.16.0.0/12 -j DROP
iptables -A FORWARD -i eth0 -s 10.0.0.0/8 -j DROP
# Note:There are more "reserved" networks, but these are the classical ones.
# Block outgoing network filesharing protocols that arent designed
# to leave the LAN
# SMB / Windows filesharing
iptables -A FORWARD -p tcp --sport 137:139 -j DROP
iptables -A FORWARD -p udp --sport 137:139 -j DROP
# NFS Mount Service (TCP/UDP 635)
iptables -A FORWARD -p tcp --sport 635 -j DROP
iptables -A FORWARD -p udp --sport 635 -j DROP
# NFS (TCP/UDP 2049)
iptables -A FORWARD -p tcp --sport 2049 -j DROP
iptables -A FORWARD -p udp --sport 2049 -j DROP
# Portmapper (TCP/UDP 111)
iptables -A FORWARD -p tcp --sport 111 -j DROP
iptables -A FORWARD -p udp --sport 111 -j DROP
# Block incoming syslog, lpr, rsh, rexec...
iptables -A FORWARD -i eth0 -p udp --dport syslog -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 515 -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 514 -j DROP
iptables -A FORWARD -i eth0 -p tcp --dport 512 -j DROP
###
# Transparently proxy all web-surfing through Squid box
$SQUID = 192.168.1.2:8080
$SQUIDSSL = 192.168.1.2:443
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 80 -j DNAT --to $SQUID
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 443 -j DNAT --to $SQUIDSSL
# Transparently forward all outgoing mail to a relay host
$SMTP = 192.168.1.3
iptables -t nat -A PREROUTING -i eth1 -tcp --dport 25 -j DNAT --to $SMTP
# Transparently redirect web connections from outside to the DMZ web
# server
$DMZ_WEB = 192.168.2.2
iptables -t nat -A PREROUTING -i eth0 -d 192.168.1.1 -dport 80 -j DNAT --to $DMZ_WEB
# Source NAT to get Internet traffic through
iptables -t nat -A POSTROUTING -o eth1 -j SNAT --to $INTERNET
# Activate the forwarding!
echo 1 >/proc/sys/net/ipv4/ip_forward
Download (MB)
Added: 2007-02-13 License: GPL (GNU General Public License) Price:
987 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
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
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
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
wminet 3.0.0
wminet is a very useful dock app for monitoring internet connections to and from your computer. more>>
wminet is a very useful dock app for monitoring internet connections to and from your computer.
The number of connections can be filtered based on local and remote addresses and ports, on either tcp or udp. It can also display hostname and number of processes.
This new version uses a lot less CPU and allows greater configuration. The original program can be found here. However, I have removed the ability to monitor httpd and ftpd processes, nfs mounts and lpd queues.
<<lessThe number of connections can be filtered based on local and remote addresses and ports, on either tcp or udp. It can also display hostname and number of processes.
This new version uses a lot less CPU and allows greater configuration. The original program can be found here. However, I have removed the ability to monitor httpd and ftpd processes, nfs mounts and lpd queues.
Download (0.046MB)
Added: 2006-10-26 License: GPL (GNU General Public License) Price:
1093 downloads
ThinTUX 0.21
ThinTUX is a small Linux distribution for thin clients. more>>
ThinTUX is a small Linux distribution for thin clients. It has support for all major remote access protocols like ICA, RDP, XDM, telnet, ssh, and more.
The distribution can be booted from the network using a network card with PXE-support or from standard media storage devices like floppy, CD, hard disk, or disk-on-chip.
The configuration is stored on a DHCP server to simplify terminal management.
Main features:
- Automatic hardware discovery and centralized configuration using DHCP
- Single point of administration
- Small footprint
- Fully self-contained
- No NFS mounted root filesystem
- Web based configuration tool
- One boot image fits all computers
- No previous Linux knowledge required
Enhancements:
- Reduced startup time.
- Reduced RAM footprint.
- Added support for glibc programs.
- Updated kernel
- Updated to rdesktop 1.4.1
- Updated the configuration tool(ThinTUX web tool).
- Renamed configuration variables
<<lessThe distribution can be booted from the network using a network card with PXE-support or from standard media storage devices like floppy, CD, hard disk, or disk-on-chip.
The configuration is stored on a DHCP server to simplify terminal management.
Main features:
- Automatic hardware discovery and centralized configuration using DHCP
- Single point of administration
- Small footprint
- Fully self-contained
- No NFS mounted root filesystem
- Web based configuration tool
- One boot image fits all computers
- No previous Linux knowledge required
Enhancements:
- Reduced startup time.
- Reduced RAM footprint.
- Added support for glibc programs.
- Updated kernel
- Updated to rdesktop 1.4.1
- Updated the configuration tool(ThinTUX web tool).
- Renamed configuration variables
Download (13MB)
Added: 2005-09-29 License: GPL (GNU General Public License) Price:
1492 downloads
Squashfs 3.2
Squashfs is a compressed read-only filesystem for Linux. more>>
Squashfs project is a compressed read-only filesystem for Linux. Squashfs is intended for general read-only filesystem use, for archival use (i.e. in cases where a .tar.gz file may be used), and in constrained block device/memory systems (e.g. embedded systems) where low overhead is needed.
The filesystem is currently stable, and has been tested on PowerPC, i586, Sparc and ARM architectures.
Main features:
- Data, inodes and directories are compressed.
- Squashfs stores full uid/gids (32 bits), and file creation time.
- Files up to 2^32 bytes are supported. Filesystems can be up to 2^32 bytes.
- Inode and directory data are highly compacted, and packed on byte boundaries. Each compressed inode is on average 8 bytes in length (the exact length varies on file type, i.e. regular file, directory, symbolic link, and block/char device inodes have different sizes).
- Squashfs can use block sizes up to 64K (the default size is 64K). Using 64K blocks achieves greater compression ratios than the normal 4K block size.
- File duplicates are detected and removed.
- Both big and little endian architectures are supported. The mksquashfs program can generate filesystems for different endian architectures for cases where the host byte ordering is different to the target. This is useful for embedded systems.
Enhancements:
- This release is a major improvement, and Squashfs filesystems can now be exported via NFS.
- Squashfs-tools have also seen some improvements: Unsquashfs can now extract 2.x filesystems; and Mksquashfs now displays a progress bar.
- There are other smaller improvements and bugfixes.
<<lessThe filesystem is currently stable, and has been tested on PowerPC, i586, Sparc and ARM architectures.
Main features:
- Data, inodes and directories are compressed.
- Squashfs stores full uid/gids (32 bits), and file creation time.
- Files up to 2^32 bytes are supported. Filesystems can be up to 2^32 bytes.
- Inode and directory data are highly compacted, and packed on byte boundaries. Each compressed inode is on average 8 bytes in length (the exact length varies on file type, i.e. regular file, directory, symbolic link, and block/char device inodes have different sizes).
- Squashfs can use block sizes up to 64K (the default size is 64K). Using 64K blocks achieves greater compression ratios than the normal 4K block size.
- File duplicates are detected and removed.
- Both big and little endian architectures are supported. The mksquashfs program can generate filesystems for different endian architectures for cases where the host byte ordering is different to the target. This is useful for embedded systems.
Enhancements:
- This release is a major improvement, and Squashfs filesystems can now be exported via NFS.
- Squashfs-tools have also seen some improvements: Unsquashfs can now extract 2.x filesystems; and Mksquashfs now displays a progress bar.
- There are other smaller improvements and bugfixes.
Download (0.22MB)
Added: 2007-01-04 License: GPL (GNU General Public License) Price:
615 downloads
mlocate 0.17
mlocate is a new locate implementation. more>>
mlocate is a new locate implementation. The m stands for "merging": updatedb reuses the existing database to avoid rereading most of the file system, which makes updatedb faster and does not trash the system caches as much.
The locate(1) utility is intended to be completely compatible to slocate.
Eeach time, a computer was booted into single-user mode and after one updatedb run data was collected using slabtop and free. The measurement method is admittedly crude, but I think the numbers represent reality quite well.
slocate 1m32.84 0.704 2.045 134337 170778 85972 8268
mlocate, 1st 1m11.65 0.214 0.908 17766 15642 78452 21340
mlocate, 2nd 37.64 0.105 0.289 17776 15639 33996 21336
real, user, system
as reported by time
dentry, inode
number of active objects in dentry_cache and ext3_inode_cache, as reported by slabtop
buffers, cached
size of disk buffers and page cache, as reported by free
mlocate has two rows because the first run needs to rescan the whole file system, while the subsequent runs can reuse most of the original database.
Enhancements:
- This release avoids a hang if an NFS filesystem within an excluded subtree is unavailable.
<<lessThe locate(1) utility is intended to be completely compatible to slocate.
Eeach time, a computer was booted into single-user mode and after one updatedb run data was collected using slabtop and free. The measurement method is admittedly crude, but I think the numbers represent reality quite well.
slocate 1m32.84 0.704 2.045 134337 170778 85972 8268
mlocate, 1st 1m11.65 0.214 0.908 17766 15642 78452 21340
mlocate, 2nd 37.64 0.105 0.289 17776 15639 33996 21336
real, user, system
as reported by time
dentry, inode
number of active objects in dentry_cache and ext3_inode_cache, as reported by slabtop
buffers, cached
size of disk buffers and page cache, as reported by free
mlocate has two rows because the first run needs to rescan the whole file system, while the subsequent runs can reuse most of the original database.
Enhancements:
- This release avoids a hang if an NFS filesystem within an excluded subtree is unavailable.
Download (0.27MB)
Added: 2007-04-26 License: GPL (GNU General Public License) Price:
914 downloads
openQRM Plug-ins 0.9
openQRM Plug-ins is a collection of community-supported plug-ins that enable openQRM to manage other enterprise software. more>>
openQRM Plug-ins is a collection of community-supported plug-ins that enable openQRM to manage other enterprise and open source software.
openQRM is designed to deal with all sorts of failures automatically, thus preventing interrupts because of unexpected events.
Implementing openQRM greatly improves the reliability of the x86 data-center.
openQRM is an open source systems management platform which integrates with existing components in enterprise data centers to create scalable, highly available and customizable infrastructures.
openQRM is derived from a proven commercial product and distributed as an open source project through SourceForge, using a modified Mozilla Public License.
openQRMs architecture extends to and embraces other existing data center technologies through "plug-ins."The openQRM project team has created a number of plug-ins for broadly-used open source projects and proprietary solutions, and seeks to recruit community members to assist in additional plug-ins.
openQRM leverages the proven technologies of PXE and NFS along with storing images on central storage to effectively manage the data center.
The project team aims to set the standard in data center management by continuing to provide a "premiere" enterprise-grade project for automating IT infrastructure, and by embracing other technologies through increasing our offering of plug-ins.
OpenQRM.org is the best destination for our projects community to share ideas and innovations. Contributed by Qlusters, openQRM.org offers a range of support and information services to benefit all users of openQRM, including implementation advice, user forums and customer feedback.
<<lessopenQRM is designed to deal with all sorts of failures automatically, thus preventing interrupts because of unexpected events.
Implementing openQRM greatly improves the reliability of the x86 data-center.
openQRM is an open source systems management platform which integrates with existing components in enterprise data centers to create scalable, highly available and customizable infrastructures.
openQRM is derived from a proven commercial product and distributed as an open source project through SourceForge, using a modified Mozilla Public License.
openQRMs architecture extends to and embraces other existing data center technologies through "plug-ins."The openQRM project team has created a number of plug-ins for broadly-used open source projects and proprietary solutions, and seeks to recruit community members to assist in additional plug-ins.
openQRM leverages the proven technologies of PXE and NFS along with storing images on central storage to effectively manage the data center.
The project team aims to set the standard in data center management by continuing to provide a "premiere" enterprise-grade project for automating IT infrastructure, and by embracing other technologies through increasing our offering of plug-ins.
OpenQRM.org is the best destination for our projects community to share ideas and innovations. Contributed by Qlusters, openQRM.org offers a range of support and information services to benefit all users of openQRM, including implementation advice, user forums and customer feedback.
Download (18.4MB)
Added: 2006-05-03 License: MPL (Mozilla Public License) Price:
1270 downloads
Other version of openQRM Plug-ins
openQRM is derived from a proven commercial product and distributed as an open source project ... openQRM leverages the proven technologies of PXE and NFS along with storing images on centralLicense:MPL (Mozilla Public License)
License:MPL (Mozilla Public License)
License:MPL (Mozilla Public License)
License:GPL (GNU General Public License)
License:MPL (Mozilla Public License)
License:MPL (Mozilla Public License)
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 what is nfs 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
