BBFW's explanations looked good (the few I read), but Ill go ahead and throw out what I know
inetd.conf -The configuration file for inetd. inetd runs network servers. When a user connects to ftp port 21, inetd starts up ftp. ftp does not always run in the background, instead inetd starts it up. Not sure why this is the way they chose to do this, but its pretty standard.
Tcp port -This is a big one. There are 65536(?) tcp ports. When a program tries to access the internet it needs to use a port. The port is where it is coming from. If it is a non-root program, it comes from a port above 1023. When the program tries to access a service, it hits a specific port. Port 80 is httpd. If you want/need more of an explanation than that read tcp/ip illustrated.
Tcpserver -Its a program that is part of a tool package written by Dan Bernstein. Its a replacement for inetd. I use it for a couple of things.
Kernel -This is the core of the OS.
The kernel is the essential center of a computer operating system, the core that provides basic services for all other parts of the operating system. A synonym is nucleus. (taken from whatis.com)
NameD -The service that provides dns resolutions. Look at BIND. named is the name of the process BIND runs.
Ipchains -Old Linux firewalling stuff. Replaced with IPTables.
Port 1024 -Just another non-privledged port
Ports below 1024 -Only root processes are supposed to be able to bind to these ports. Many of the ports have services that are supposed to run on them (80 = http, 666 = DOOM)
Ports after 1024 -unprivledged ports. Anyone can bind to them. When you run a bnc you should choose a port above 1024 so that you can run it as a non-root user.
Chroot -You basically setup an OS within your OS. For example, in OpenBSD I have linux emulation. Part of what happens is a chroot is setup at /usr/local/emul/redhat. Within that directory, a fulle system tree (basically). I have /bin, /usr/bin, /sbin, etc. When something in that chroot is run it thinks /usr/local/emul/redhat/ is the root (/) of the file system and it should be contained to that area. Its a good idea to chroot as many services as you can. BIND has this ability built in.
Bind -see named earlier
Daemon -Basically a service. Each service you connect to is a daemon. httpd, named, etc are all daemons. They offer services and whatnot for users to connect to.
UDP -unreliable(?) data protocol. Its a fast protocol, but has no built in error checking or authentication or state. Its fast, but unreliable (unless the program adds in reliability).
Buffer overflow bugs -When input isnt regulated correctly, users can input too much data, overwrite data in the memory stack, and possibly run malicious programs. If a program can handle 255 bytes of data, a user could input 300 bytes and possibly cause problems like crashing the program, or getting it to run something malicious.
Buffer overflow attacks -See above.
X -X Windowing system. Its a gui for UNIX and UNIX-like OSes.
Netstat -You can view routing and open ports with this. It will show ports you are connected to and from.
IP of 0.0.0.0 -Nothing
IP of 127.0.0.1 -loopback. Thats the machine you are on.
IP of 169.254.225.239 -explained above by Sinister (sorry about the caps, too lazy to look how you do it )
IP of 10.11.12.13 -An ip address that falls under RFC 1819.
Xdm port -No clue
Lpd -Printing daemon.
Source ports in the range of 721-731 -
http://www.iana.org/assignments/port-numbers
# 712-728 Unassigned
netviewdm1 729/tcp IBM NetView DM/6000 Server/Client
netviewdm1 729/udp IBM NetView DM/6000 Server/Client
netviewdm2 730/tcp IBM NetView DM/6000 send/tcp
netviewdm2 730/udp IBM NetView DM/6000 send/tcp
netviewdm3 731/tcp IBM NetView DM/6000 receive/tcp
netviewdm3 731/udp IBM NetView DM/6000 receive/tcp
Pdq -No clue
NFS -Network File System. Its a way to mount file systems over the network and use them like they were local. I think its similar to CIFs and SMB.
Localhost.localdomain -loopback basically.
Sandboxing -Limiting the damage something can do. Similar to chroot in thought. Keep the program sandboxed so the damage it could do to the rest of the system is limited.
Ping of Death -Old DoS that I dont think works anymore. It sent pings that were larger than 65536 bytes(?) crashing the OS.
Proxying firewall -A firewall that proxies data. What do you really want to know about this? The name is very self explanatory.
Masquerading -NAT by another name.
/tmp directory -For temporary stuff
/bin directory -Binary directories
/var directory -Logs and other various stuff
/usr directory -user stuff. Mostly just the things the users would need.
/lib -Libraries for dynamically linked binary executables go here (and in other lib directories)
other important directories???
SUID -Set UID. This usually allows programs to run with root privledges. I think this is a bad idea and should be used as infrequently as possible.
World executable - ??1. Anyone on the system can run it.
Public port -A port accessible from the internet?
LIDS -Linux Intrusion Detection Software. Its a NIDS that runs on Linux. Havent used it though, but Ive heard good things about it.
Openwall patches -More security patches to limit what users do.
Bastille hardening Script -See above +firewall stuff I think
Swap partition -duh
Grep -BBFW has a great explanation for this one.
NIS -Cant explain it. whatis.com
Sniffing -Taking a look at all packets reaching an interface whether they are supposed to be seen by that interface or not. Easiest way is by putting the interface in promiscuous mode.
Ssh -is a secure rsh (not telnet )
Wheel group -Group of users allowed to su to root on BSD machines (maybe some other systems too)
.rhosts -Dont worry about it.
.netrc -Dunno, probably a config file for a program you are using.
/etc/hosts.equiv -Dont know, but I think it has something to do with the r commands.
the r commands -Delete them, never use them. They are junk.
touch -update/change timestamp on a file and create files if the file does not already exist.
MD5 hashes -used for checking the integrity of a file or for encrypting files. Its a one way hash.
/etc/shadow -Stores encrypted files on Linux machines
PAM ? Pluggable Authentic Modules -self explanatory (basically, anything more than modifying authentication I dont know)
LILO -duh
/etc/hosts.allow -used with tcpwrappers to allow connections to programs started by inetd from the hosts listed here. There is also a library with tcpwrappers or something that allows non-inetd programs to use these files.
/etc/hosts.deny -denies in the same way the last file allows
TCP wrapper -explained it above
SMB -Windows networking protocol. Used by SAMBA to provide Windows file sharing from other platforms.
COI scripts -No clue
FTP bounce attack -I will not explain this on here.
NISNuke Attack -Again, I will not explain this here (even if I knew what this particular attack is for).
Chargen -Character generation. Its an almost useless service and should *NOT* be run.
Discard -Probably has to do with firewalling and discarding packets instead of rejecting.
Inetd -explained above.
Different port states -listening/open, closed, connected. Tells you what is going on on that port.
Shadow passwords -encrypted passwords
System binaries -binaries necessary for the operation of the system. Or something like that.
SUDO -Allows one user to run programs as another user.
Shell escape -No clue
Absolute path to the binary -Start with / and go all the way to the file ie /usr/local/bin/nmap instead of (if you are in /usr) local/bin/nmap
IPSEC -vpn stuff.
SATAN -Old out of date vulnerability scanner. SAINT is the newer version I think.
Nessus -Vulnerability scanner.
Trinux -small floppy based linux distro I think.
Tripwire -HIDS. Checks file integrity and other things.
TCP connections -Connections using the tcp protocol.
UDP connections -Do not exist (correct me if Im wrong).
ICMP connections -Do not exist.
Append-only -Append to the end of the file instead of being able to modify/delete/whatever the file. chattr in linux and chflags in OpenBSD will allow you to set this.
Immutable -File may not be modified or deleted at all.
Chattr command -see above.
Lsattr command -BBFW gave an explanation I hope is right
Tar file -Tape ARchive. Kind of like zipping a bunch of files in Windows, but without the compression.
Nonexecutable stack -No clue right off.
/tmp race condition -I wont be explaining that here.
StackGuard -Dont know right off, but it sounds like something that protects the kernel/memory/tcpip/whatever stack in a Linux machine to prevent some exploits.
Stack smashing buffer overflow -Above.
Socket -Couldnt explain it.
Raw socket -Again, cant explain it.
Rule based access control -Sounds like firewall type of thing.
Stateful inspection packet filter -Checks the state on tcp connections before applying rules.
Abacus Port Sentry -I know of a port sentry program for UNIX-like systems. It basically looks for scans on the system.
Parallel scan -I wont explain that here (if what I think it means is really what it means).
Ipfwadm facility -An Administration application for IPFW I think.
Syslog service -A way of sending log files to a syslog machine. The syslogd recieves the logs and places them in the log file.
Ssyslog secure syslog -No clue.
Syslog-ng -No clue.
Kerberos -Authentication method.
Adaptive filtering -No clue really, but it sounds like automatic responses to firewall alarms.
So are you trying to crack someone? There are some very fishy questions here. And 99% of these could have been answered through a quick
http://www.google.com/linux search.