I hope you'll forgive my dummy question, but i would like to upgrade the java sdk (PE7.2 comes with bundled sdk ver. 1.1.8 and i would love to the 1.3.x_) and i would like to know how to link the shell commands "java", "javac" and so on with new binaries. Best regards and thanx since now. L.N.
Le Mardi 9 Octobre 2001 16:49, vous avez écrit :
I hope you'll forgive my dummy question, but i would like to upgrade the java sdk (PE7.2 comes with bundled sdk ver. 1.1.8 and i would love to the 1.3.x_) and i would like to know how to link the shell commands "java", "javac" and so on with new binaries.
Best regards and thanx since now.
L.N.
Actually SuSE 7.2 Pro comes with the IBM Jdk, so you might want to try to download that from the SuSE ftp server. The other options is to get the tarball of JDK 1.3.1_01 from java.sun.com (prefer the tarball (.bin) to the RPM !). Then you can unpack the file in the /usr/lib/ directory by moving this file to this directory and then running: $ sh j2dsk_something.bin In the Pro edition, the java directory in usr/lib/include is actually a symbolic link to the jdk, so you should remove this link using : $ rm java and recreate it using: $ ln -s jdk1.3.1.xx java Finally, make sure that everything is correct by running: $ java -version Best regards, David Garnier
In the Pro edition, the java directory in usr/lib/include is actually a symbolic link to the jdk, so you should remove this link using : $ rm java and recreate it using: $ ln -s jdk1.3.1.xx java
Finally, make sure that everything is correct by running: $ java -version
I should add that Yast2 has the nasty habit of recreating (therefore nullifying your work) the link to java because the java package is compulsory and it can't understand that you have installed your own version. If somebody knows how to teach Yast2 out of this habit, please share! Best regards, David Garnier
On Tuesday 09 October 2001 11:23 am, David Garnier wrote:
In the Pro edition, the java directory in usr/lib/include is actually a symbolic link to the jdk, so you should remove this link using : $ rm java and recreate it using: $ ln -s jdk1.3.1.xx java
Finally, make sure that everything is correct by running: $ java -version
I should add that Yast2 has the nasty habit of recreating (therefore nullifying your work) the link to java because the java package is compulsory and it can't understand that you have installed your own version. If somebody knows how to teach Yast2 out of this habit, please share!
Best regards, David Garnier
I can help! :-) In the file /etc/rc.config, look for the following lines: # # SuSEconfig can automatically create the links /usr/lib/java and /usr/lib/jre # that point to a suitable JDK or JRE respectively if you set CREATE_JAVALINK # to "yes" # If you are not satisfied with the choice it makes, set CREATE_JAVALINK to # "no" and set the link manually. # CREATE_JAVALINK="yes" Change that "yes" to "no" and you should fix the problem. Scott -- -----------------------+------------------------------------------------------ Scott Courtney | "I don't mind Microsoft making money. I mind them courtney@4th.com | having a bad operating system." -- Linus Torvalds http://www.4th.com/ | ("The Rebel Code," NY Times, 21 February 1999)
On Tuesday 09 October 2001 11:23, David Garnier wrote:
I should add that Yast2 has the nasty habit of recreating (therefore nullifying your work) the link to java because the java package is compulsory and it can't understand that you have installed your own version. If somebody knows how to teach Yast2 out of this habit, please share!
I did not have any problems with this. First in Yast2 I uninstalled all the old java files that came with the distro. It did give me a warning something like "other things depend on this. do you still want to uninstall?" However, I went ahead and uninstalled, then installed the 1.3 from java.sun.com. Everything is fine as far as I can tell. *************************************************** Powered by SuSE Linux 7.2 Professional KDE 2.1.2 KMail 1.2 Bryan S. Tyson bryantyson@earthlink.net ***************************************************
Hi, I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed? Cheers, Tom _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Tue, Oct 09, 2001 at 06:33:27PM +0100, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
Well ping has got to find something that translates the hostname into an IP! Usually it will get this from /etc/hosts, a local nameserver, NIS, LDAP .. you name it. This depends on what is in your /etc/resolv.conf. Someone other than me can tell you how you go about this if your DHCP setup does not have a fixed mapping of a particular host to a particular IP address. It can be done, but I have never done it ! -- Regards Cliff
On Tuesday 09 October 2001 8:35 pm, Cliff Sarginson wrote:
On Tue, Oct 09, 2001 at 06:33:27PM +0100, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
Well ping has got to find something that translates the hostname into an IP! Usually it will get this from /etc/hosts, a local nameserver, NIS, LDAP .. you name it. This depends on what is in your /etc/resolv.conf. Someone other than me can tell you how you go about this if your DHCP setup does not have a fixed mapping of a particular host to a particular IP address. It can be done, but I have never done it !
Any takers? I can't set up /etc/hosts. This machines all use dhcp, so they change. How can this be set up? Cheers, Tom _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Tom Wesley writes:
On Tuesday 09 October 2001 8:35 pm, Cliff Sarginson wrote:
On Tue, Oct 09, 2001 at 06:33:27PM +0100, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
Well ping has got to find something that translates the hostname into an IP! Usually it will get this from /etc/hosts, a local nameserver, NIS, LDAP .. you name it. This depends on what is in your /etc/resolv.conf. Someone other than me can tell you how you go about this if your DHCP setup does not have a fixed mapping of a particular host to a particular IP address. It can be done, but I have never done it !
Any takers? I can't set up /etc/hosts. This machines all use dhcp, so they change. How can this be set up?
If your local network is resolved via DNS, then the problem will lie there. Make sure /etc/resolv.conf looks okay. You should have something like: nameserver 156.676.998.1 search your.domain If you want to temporarily make it work then you can add hostname ip combinations in /etc/hosts. I think it will try this file first to resolve and then do whatever is in /etc/resolv.conf next. You can also try nslookup. This will allow you to talk to the namserver and perform queries. Are all the machines using NT? They may not have the need to do local network DNS. Just a thought. I think SMB uses a different mechanism for translating host names.
Cheers, Tom
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Tuesday 09 October 2001 10:50 pm, Jesse Marlin wrote:
Tom Wesley writes:
On Tuesday 09 October 2001 8:35 pm, Cliff Sarginson wrote:
On Tue, Oct 09, 2001 at 06:33:27PM +0100, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
Well ping has got to find something that translates the hostname into an IP! Usually it will get this from /etc/hosts, a local nameserver, NIS, LDAP .. you name it. This depends on what is in your /etc/resolv.conf. Someone other than me can tell you how you go about this if your DHCP setup does not have a fixed mapping of a particular host to a particular IP address. It can be done, but I have never done it !
Any takers? I can't set up /etc/hosts. This machines all use dhcp, so they change. How can this be set up?
If your local network is resolved via DNS, then the problem will lie there. Make sure /etc/resolv.conf looks okay. You should have something like:
nameserver 156.676.998.1 search your.domain
If you want to temporarily make it work then you can add hostname ip combinations in /etc/hosts. I think it will try this file first to resolve and then do whatever is in /etc/resolv.conf next.
You can also try nslookup. This will allow you to talk to the namserver and perform queries. Are all the machines using NT? They may not have the need to do local network DNS. Just a thought. I think SMB uses a different mechanism for translating host names.
You could well have it here. Maybe, thinking about it, this is done by the old Novell sitting in the corner. Never needed to check :) Anyway, anyone know where I'm meant to start if this is done by the dreaded SMB? Cheers, Tom _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Hello, Tom. Ooh, this sounds like a job for DDNS or WINS. If I remember rightly, BIND9 does dynamic DNS, but this may be going a bit far for your needs. If you configure SAMBA on the Linux machine, you can configure it to use an existing WINS server. This will then be able to resolve the names of the Windows boxes for you since they announce themselves to it with their new IP every time they boot. It is also possible to set up DHCP to give out the same address to each machine every time. This would allow you to use your hosts file for name resolution, since the addresses would always be the same. You give no indication in your original message as to the scale of your "work", or your level of influence over network operations. Without that, it is hard to recommend any one solution as the best for your situation. Your server must have a static IP address, yes ? If you can ping that by name, then your internal DNS is working OK on the Linux box. It sounds like your issue is solely with the NetBIOS names that MS uses on its windows machines, which are dealt with by WINS, not DNS. Bye for now, Stuart. -----Original Message----- From: suse-linux-e-return-75100-stuart=yorkshirepudding.com@suse.com [mailto:suse-linux-e-return-75100-stuart=yorkshirepudding.com@suse.com]O n Behalf Of Tom Wesley Sent: 09 October 2001 22:22 To: suse-linux-e@suse.com Subject: Re: [SLE] NT Networking problems On Tuesday 09 October 2001 8:35 pm, Cliff Sarginson wrote:
On Tue, Oct 09, 2001 at 06:33:27PM +0100, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
Well ping has got to find something that translates the hostname into an IP! Usually it will get this from /etc/hosts, a local nameserver, NIS, LDAP .. you name it. This depends on what is in your /etc/resolv.conf. Someone other than me can tell you how you go about this if your DHCP setup does not have a fixed mapping of a particular host to a particular IP address. It can be done, but I have never done it !
Any takers? I can't set up /etc/hosts. This machines all use dhcp, so they change. How can this be set up? Cheers, Tom _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Tuesday 09 October 2001 11:13 pm, Stuart Powell wrote:
Hello, Tom.
Ooh, this sounds like a job for DDNS or WINS. If I remember rightly, BIND9 does dynamic DNS, but this may be going a bit far for your needs.
If you configure SAMBA on the Linux machine, you can configure it to use an existing WINS server. This will then be able to resolve the names of the Windows boxes for you since they announce themselves to it with their new IP every time they boot.
It is also possible to set up DHCP to give out the same address to each machine every time. This would allow you to use your hosts file for name resolution, since the addresses would always be the same.
You give no indication in your original message as to the scale of your "work", or your level of influence over network operations. Without that, it is hard to recommend any one solution as the best for your situation. Your server must have a static IP address, yes ? If you can ping that by name, then your internal DNS is working OK on the Linux box. It sounds like your issue is solely with the NetBIOS names that MS uses on its windows machines, which are dealt with by WINS, not DNS.
This is only a small, 5 PC network. With a Win98 Fax server, a Novell server, an NT, a Win2000 and the Linux. Plus the 5 workstations. We design computer software and networks, so level of influence isn't an issue. We just need to make it work!
Bye for now, Stuart.
-----Original Message----- From: suse-linux-e-return-75100-stuart=yorkshirepudding.com@suse.com [mailto:suse-linux-e-return-75100-stuart=yorkshirepudding.com@suse.com]O n Behalf Of Tom Wesley Sent: 09 October 2001 22:22 To: suse-linux-e@suse.com Subject: Re: [SLE] NT Networking problems
On Tuesday 09 October 2001 8:35 pm, Cliff Sarginson wrote:
On Tue, Oct 09, 2001 at 06:33:27PM +0100, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
Well ping has got to find something that translates the hostname into an IP! Usually it will get this from /etc/hosts, a local nameserver, NIS, LDAP .. you name it. This depends on what is in your /etc/resolv.conf. Someone other than me can tell you how you go about this if your DHCP setup does not have a fixed mapping of a particular host to a particular IP address. It can be done, but I have never done it !
Any takers? I can't set up /etc/hosts. This machines all use dhcp, so they change. How can this be set up?
Cheers, Tom _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Tuesday 09 October 2001 05:21 pm, Tom Wesley wrote:
On Tuesday 09 October 2001 8:35 pm, Cliff Sarginson wrote:
On Tue, Oct 09, 2001 at 06:33:27PM +0100, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
Well ping has got to find something that translates the hostname into an IP! Usually it will get this from /etc/hosts, a local nameserver, NIS, LDAP .. you name it. This depends on what is in your /etc/resolv.conf. Someone other than me can tell you how you go about this if your DHCP setup does not have a fixed mapping of a particular host to a particular IP address. It can be done, but I have never done it !
Any takers? I can't set up /etc/hosts. This machines all use dhcp, so they change. How can this be set up?
The short answer: You may need dynamic DNS (DDNS). What DDNS does is (conceptually) to couple DHCP's allocation of IP addresses with the desired hostnames of particular machines. The long answer: Starting with Windows 2000, Micro$oft has implemented DDNS natively in their servers. Unfortunately, the did a Microsoft with it. That is to say, they made it so that their Windows clients "prefer" and will work better with a Microsoft DDNS server. Even though DDNS itself is an IETF standard (RFC 2136, 2137, and 3007, among others), Microsoft has chosen to try to push their servers onto the "top" of the pyramid. This has to do with their Active Directory (which I affectionately refer to as "Captive Directory"), itself a bastardized flavor of LDAP. I'm not enough of a Microsoft expert to give detailed suggestions on what to do about this, but I'm aware of the problems. Win2K workstations *will* work with standard DDNS and LDAP servers, but Microsoft doesn't support some of their domain and security features in this mode. Perhaps there is a Windows guru on the list who can either enlighten all of us with a recommended workaround, or who can respond to your query by private mail since this isn't a Win2K list. I hope this is at least helpful in defining the problem for you. Scott -- -----------------------+------------------------------------------------------ Scott Courtney | "I don't mind Microsoft making money. I mind them courtney@4th.com | having a bad operating system." -- Linus Torvalds http://www.4th.com/ | ("The Rebel Code," NY Times, 21 February 1999)
On Tuesday 09 October 2001 11:23 pm, Scott Courtney wrote:
On Tuesday 09 October 2001 05:21 pm, Tom Wesley wrote:
On Tuesday 09 October 2001 8:35 pm, Cliff Sarginson wrote:
On Tue, Oct 09, 2001 at 06:33:27PM +0100, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
Well ping has got to find something that translates the hostname into an IP! Usually it will get this from /etc/hosts, a local nameserver, NIS, LDAP .. you name it. This depends on what is in your /etc/resolv.conf. Someone other than me can tell you how you go about this if your DHCP setup does not have a fixed mapping of a particular host to a particular IP address. It can be done, but I have never done it !
Any takers? I can't set up /etc/hosts. This machines all use dhcp, so they change. How can this be set up?
The short answer:
You may need dynamic DNS (DDNS). What DDNS does is (conceptually) to couple DHCP's allocation of IP addresses with the desired hostnames of particular machines.
The long answer:
Starting with Windows 2000, Micro$oft has implemented DDNS natively in their servers. Unfortunately, the did a Microsoft with it. That is to say, they made it so that their Windows clients "prefer" and will work better with a Microsoft DDNS server. Even though DDNS itself is an IETF standard (RFC 2136, 2137, and 3007, among others), Microsoft has chosen to try to push their servers onto the "top" of the pyramid. This has to do with their Active Directory (which I affectionately refer to as "Captive Directory"), itself a bastardized flavor of LDAP.
I'm not enough of a Microsoft expert to give detailed suggestions on what to do about this, but I'm aware of the problems. Win2K workstations *will* work with standard DDNS and LDAP servers, but Microsoft doesn't support some of their domain and security features in this mode. Perhaps there is a Windows guru on the list who can either enlighten all of us with a recommended workaround, or who can respond to your query by private mail since this isn't a Win2K list.
I hope this is at least helpful in defining the problem for you.
Scott
I'm not at all in a position to do so, but I think that this is far more than is needed. The setup will allow me to ping my Windows machine (called "TOM") from any other machine on the network. Today it had the ip 10.0.0.6. To ping my machine from the Linux box I need to type the ip itself. The probably being of course that this will probably be changed by the morning... _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Hello, Tom. The way DHCP works is that a machine will request an IP when it boots up for the first time. It gets an IP which it leases for a period specified by the server configuration. Let's say for the sake of argument that this period is 8 days. At half the lease period (4 days) the client will try to renew its lease. If successful, the lease period goes back up to being 8 days, and the clock starts over. If it fails to renew the lease, the client will keep the IP address, and wait another half period (2 more days) and try again. If successful, the clock starts again at 8 days. If not, it will wait another half period. This does not go on indefinitely. I can't remember at exactly what point the client gives up (since it can't keep waiting for half periods forever, it must eventually give up the lease) but as long as it can continue to renew that lease, it will keep that address. At one place I worked recently, the lease period was set to 4 hours. As you can imagine, this would mean a lot of DHCP traffic over the network. If we had any problems with the DHCP server, every client machine would quickly expire the lease and stop talking to the rest of the network. We extended this lease to 30 days, and never had trouble with it again. Maybe if you could set up fixed IPs via DHCP or extend the lease period, your PCs won't get different IPs every morning. DHCP is simply a delivery mechanism for IP addresses. If set up well, it will be your friend, not your enemy. With only a short lease of 4hrs, it behaved more like RandomHCP, which is not the goal. If you have Netware 4.1x or above it may well be doing your DNS etc. If it is still running 3.x, then it is less likely as that required a rather expensive add-on to do those jobs. Linux and NT/W2K Server are both capable of doing DNS/DHCP/WINS, although W2K requires Active Directory to do DNS and DHCP, which is a step many people are, quite rightly, still shy of. Bye for now, Stuart. -----Original Message----- <snip> To ping my machine from the Linux box I need to type the ip itself. The probably being of course that this will probably be changed by the morning... </snip>
Tom, Did you set up DNS and add your local machine names to the DNS server? Mark On Tuesday 09 October 2001 13:33, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
I think it was a NetBIOS cockup on our network that is now sorted fine. Cheers for all the help though people... :) On Friday 12 October 2001 5:38 am, Mark Halegua wrote:
Tom,
Did you set up DNS and add your local machine names to the DNS server?
Mark
On Tuesday 09 October 2001 13:33, Tom Wesley wrote:
Hi,
I've just installed a SuSE 7.0 box onto our work nt network. All the machines on the network us dhcp to get their ip info and all works fine for them. With the linux machine it gets it's ip and nameserver, so all the external www works fine. In fact the whole network connection works, all but one thing. If I try to ping a local machine by it's hostname then it cannot be found. But if I try using their IP it all works ok. Anyone know what I've missed?
Cheers, Tom
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
The Sun java sdk includes instructions on how to do this. Typically you should put something like JAVA_HOME=/usr/local/jdk1.3 export JAVA_HOME PATH=$PATH:/usr/local/tmake-1.7/bin:$JAVA_HOME/bin in your .profile JDL linux newbie wrote:
I hope you'll forgive my dummy question, but i would like to upgrade the java sdk (PE7.2 comes with bundled sdk ver. 1.1.8 and i would love to the 1.3.x_) and i would like to know how to link the shell commands "java", "javac" and so on with new binaries.
Best regards and thanx since now.
L.N.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Tuesday 09 October 2001 10:49, linux newbie wrote:
I hope you'll forgive my dummy question, but i would like to upgrade the java sdk (PE7.2 comes with bundled sdk ver. 1.1.8 and i would love to the 1.3.x_) and i would like to know how to link the shell commands "java", "javac" and so on with new binaries.
Why not just uninstall the old sdk? That's what I did on my system. *************************************************** Powered by SuSE Linux 7.2 Professional KDE 2.1.2 KMail 1.2 Bryan S. Tyson bryantyson@earthlink.net ***************************************************
participants (10)
-
Bryan Tyson -
Cliff Sarginson -
David Garnier -
Jesse Marlin -
John D Lamb -
linux newbie -
Mark Halegua -
Scott Courtney -
Stuart Powell -
Tom Wesley