Re: network freebsd computers
On Tue, Sep 22, 2009 at 8:18 PM, Carmel NY carmel...@hotmail.com wrote: On Tue, 22 Sep 2009 20:52:47 +0300 Peter peterp...@aboutsupport.com wrote: [snip] Maybe you are looking for this ? http://www.freebsddiary.org/nfs.php That article is quite dated. However, I will investigate it ASAP. Thanks! Compared to the world of Microsoft you'd be surprise how stable the general operation of a UNIX system is. Just cause it was written a while ago doesn't mean its out of date and/or irrelevant NFS on UNIX like systems is a relatively standard task and no real reason has existed for a while to change anything in the way that this is accomplished. Unlike the world of Microsoft things aren't changed for no rational reason in the world of UNIX-like systems. -- Opportunity is most often missed by people because it is dressed in overalls and looks like work. Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
Ross Cameron wrote: On Tue, Sep 22, 2009 at 8:18 PM, Carmel NY carmel...@hotmail.com wrote: On Tue, 22 Sep 2009 20:52:47 +0300 Peter peterp...@aboutsupport.com wrote: [snip] Maybe you are looking for this ? http://www.freebsddiary.org/nfs.php That article is quite dated. However, I will investigate it ASAP. Thanks! Compared to the world of Microsoft you'd be surprise how stable the general operation of a UNIX system is. Just cause it was written a while ago doesn't mean its out of date and/or irrelevant NFS on UNIX like systems is a relatively standard task and no real reason has existed for a while to change anything in the way that this is accomplished. Your statement would have had just as much relevance and impact if you had left the comparison out ;) Unlike the world of Microsoft things aren't changed for no rational reason in the world of UNIX-like systems. I think that you are missing something here. It is unfair to say that a commercial entity makes changes for no rational reason. Understand that there is *always* a reason for change. It may appear that a commercial entity makes drastic changes that _seem_ irrational to many people, but in reality, change is necessary. These changes are completely relevant to the shareholders who own the company. If there is no change, there is no growth. Revenue is a great motivator for change, and therefore change is very, very relevant. Getting back to the point, many of my personal docs/notes regarding FBSD dating back to 2000 are still relevant, but many aren't. The nice thing is, is that we have this list (and the other FBSD lists), it's archives, and numerous thousands of websites and documents freely available to us on any given day. I like to look at it this way... each day that a change in FreeBSD is made, is equal to someone, somewhere asking a question about the change, someone else responding to that question, and then information being fed into the global system of knowledge for everyone to see. In my time (w/FBSD), I can't recall one instance of a situation that I wasn't either able to solve via the lists, the archives, Google, or the documentation. When that ran out, a decent writeup of your issue is generally enough to entice the developers themselves to provide you feedback. iow, there is no such thing as an irrational change. Everything happens for a reason. If you must compare, the changes in FreeBSD or any of it's subsystems or 3rd party applications generally happen for reasons other than financial gain (afaik). My .02 Steve smime.p7s Description: S/MIME Cryptographic Signature
Re: network freebsd computers
Carmel NY wrote: Most of my networking experience is based on a Windows. Networking two or more PCs together in a Window's environment is easy. I find it easier to network machines using FreeBSD :) I am not getting anywhere accomplishing the same with multiple FreeBSD machines. I can get them networked with Window's machines; however, not with each other. Where can I find a go How-To on how to accomplish this? In what sense are you trying to 'network' them? Via the likes of Windows file sharing? Steve smime.p7s Description: S/MIME Cryptographic Signature
Re: network freebsd computers
On Tue, Sep 22, 2009 at 12:39 PM, Carmel NY carmel...@hotmail.com wrote: Most of my networking experience is based on a Windows. Networking two or more PCs together in a Window's environment is easy. Unfortunately, I am not getting anywhere accomplishing the same with multiple FreeBSD machines. I guess that depends on perspective as I would say the opposite is true, or at least truer. I can get them networked with Window's machines; however, not with each other. You need to provide more details. What do you mean by networked? Filesharing? NAT? Same subnet? Where can I find a go How-To on how to accomplish this? -- Carmel car...@hotmail.com It is common sense to take a method and try it. If it fails, admit it frankly and try another. But above all, try something. Franklin D. Roosevelt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Sep 22, 2009, at 1:39 PM, Carmel NY wrote: Most of my networking experience is based on a Windows. Networking two or more PCs together in a Window's environment is easy. Unfortunately, I am not getting anywhere accomplishing the same with multiple FreeBSD machines. I can get them networked with Window's machines; however, not with each other. Where can I find a go How-To on how to accomplish this? -- Carmel car...@hotmail.com Carmel, Could you perhaps describe what it is you want to accomplish? I might be able to direct you to a nice how-to or even walk you through it... Regards, Mikel King CEO, Olivent Technologies Senior Editor, BSD News Network Columnist, BSD Magazine 6 Alpine Court, Medford, NY 11763 o: 631.627.3055 skype:mikel.king http://olivent.com http://mikelking.com http://twitter.com/mikelking ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
Carmel NY wrote: Most of my networking experience is based on a Windows. Networking two or more PCs together in a Window's environment is easy. Unfortunately, I am not getting anywhere accomplishing the same with multiple FreeBSD machines. I can get them networked with Window's machines; however, not with each other. Where can I find a go How-To on how to accomplish this? Hi, Maybe you are looking for this ? http://www.freebsddiary.org/nfs.php Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, 22 Sep 2009 13:46:53 -0400 Mikel King mikel.k...@olivent.com wrote: On Sep 22, 2009, at 1:39 PM, Carmel NY wrote: Most of my networking experience is based on a Windows. Networking two or more PCs together in a Window's environment is easy. Unfortunately, I am not getting anywhere accomplishing the same with multiple FreeBSD machines. I can get them networked with Window's machines; however, not with each other. Where can I find a go How-To on how to accomplish this? -- Carmel car...@hotmail.com Carmel, Could you perhaps describe what it is you want to accomplish? I might be able to direct you to a nice how-to or even walk you through it... Sorry, I should have been more informative. Presently, I have Samba set up on my FreeBSD machines. Windows can access the shared directories without any problems. I also have Putty installed on the Windows machines so I can directly access the FreeBSD boxes when required. I want the same functionality between the FreeBSD boxes. Eventually, at least one of them will be run headless; the mail server in particular. I can find a virtual cornucopia of information on networking Windows machines; Microsoft even includes a wizard to accomplish it. However, there does not seem to be as much information regarding non-Windows products. At present, all machines are connected, either wired or wireless, through a linksys router. -- Carmel car...@hotmail.com Syntactic sugar causes cancer of the semicolon. Epigrams in Programming, ACM SIGPLAN Sept. 1982 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, 22 Sep 2009 20:52:47 +0300 Peter peterp...@aboutsupport.com wrote: [snip] Maybe you are looking for this ? http://www.freebsddiary.org/nfs.php That article is quite dated. However, I will investigate it ASAP. Thanks! -- Carmel car...@hotmail.com BLISS is ignorance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 1:12 PM, Carmel NY carmel...@hotmail.com wrote: On Tue, 22 Sep 2009 13:46:53 -0400 Mikel King mikel.k...@olivent.com wrote: On Sep 22, 2009, at 1:39 PM, Carmel NY wrote: Most of my networking experience is based on a Windows. Networking two or more PCs together in a Window's environment is easy. Unfortunately, I am not getting anywhere accomplishing the same with multiple FreeBSD machines. I can get them networked with Window's machines; however, not with each other. Where can I find a go How-To on how to accomplish this? -- Carmel car...@hotmail.com Carmel, Could you perhaps describe what it is you want to accomplish? I might be able to direct you to a nice how-to or even walk you through it... Sorry, I should have been more informative. Presently, I have Samba set up on my FreeBSD machines. Windows can access the shared directories without any problems. I also have Putty installed on the Windows machines so I can directly access the FreeBSD boxes when required. I want the same functionality between the FreeBSD boxes. Eventually, at least one of them will be run headless; the mail server in particular. I can find a virtual cornucopia of information on networking Windows machines; Microsoft even includes a wizard to accomplish it. However, there does not seem to be as much information regarding non-Windows products. At present, all machines are connected, either wired or wireless, through a linksys router. -- Carmel car...@hotmail.com http://www.freebsd.org/cgi/man.cgi?query=mount_smbfsapropos=0sektion=0manpath=FreeBSD+8-currentformat=html -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, 22 Sep 2009, Carmel NY wrote: Presently, I have Samba set up on my FreeBSD machines. Windows can access the shared directories without any problems. I also have Putty installed on the Windows machines so I can directly access the FreeBSD boxes when required. I want the same functionality between the FreeBSD boxes. Eventually, at least one of them will be run headless; the mail server in particular. It's still a little unclear. If you want the FreeBSD systems to participate in the Windows networking, look at mount_smbfs and Samba. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 02:18:24PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 20:52:47 +0300 Peter peterp...@aboutsupport.com wrote: [snip] Maybe you are looking for this ? http://www.freebsddiary.org/nfs.php That article is quite dated. However, I will investigate it ASAP. This isn't Windows where everything changes between every new release. The fundamentals of NFS haven't changed much in 10 years. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 02:12:48PM -0400, Carmel NY wrote: I can find a virtual cornucopia of information on networking Windows machines; Microsoft even includes a wizard to accomplish it. However, there does not seem to be as much information regarding non-Windows products. Perhaps because it is *harder* to network Windows than Unix? Skimming this thread something I would suggest that may be falling through the cracks is to unify your user accounts across all the machines. No matter that user joe isn't supposed to be using a particular machine do not reuse joe's userid on that machine. Also reconsider the need to share all filesystems across all machines. A typical Windows network application often runs client-fileserver rather than client-server. When one can not remotely login to a single-user Windows machine, filesharing band-aids that issue. Multi-user Unix systems trivially allow remote logins including ftp and scp file copying. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, 22 Sep 2009 12:25:38 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: [snip] It's still a little unclear. If you want the FreeBSD systems to participate in the Windows networking, look at mount_smbfs and Samba. I want to be able to access a FreeBSD box from another FreeBSD box. I rarely access a Windows machine from FreeBSD as it is just easier to do it the other way around. Anyway, I have been given a few ideas to follow upon. Thanks! -- Carmel car...@hotmail.com SAFETY I can live without Someone I love But not without Someone I need. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 02:12:48PM -0400, Carmel NY wrote: Presently, I have Samba set up on my FreeBSD machines. Windows can access the shared directories without any problems. I also have Putty installed on the Windows machines so I can directly access the FreeBSD boxes when required. I want the same functionality between the FreeBSD boxes. Eventually, at least one of them will be run headless; the mail server in particular. You can connect from one FreeBSD machine to another via the 'telnet' or 'ssh' programs, where telnet is frowned upon because it sends passwords over the network as plain text. You can mount a shared resource from a SMB file server via mount_smbfs(8). [http://www.freebsd.org/cgi/man.cgi?query=mount_smbfsapropos=0sektion=0manpath=FreeBSD+5.2-RELEASE+and+Portsformat=html] I can find a virtual cornucopia of information on networking Windows machines; Microsoft even includes a wizard to accomplish it. However, there does not seem to be as much information regarding non-Windows products. OpenSSH, the implementation that FreeBSD uses is covered (both client and server) in ยง 14.11 of the FreeBSD Handbook: [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/openssh.html] Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpCXqylOZc2I.pgp Description: PGP signature
Re: network freebsd computers
On Tue, Sep 22, 2009 at 1:48 PM, Carmel NY carmel...@hotmail.com wrote: On Tue, 22 Sep 2009 12:25:38 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: [snip] It's still a little unclear. If you want the FreeBSD systems to participate in the Windows networking, look at mount_smbfs and Samba. I want to be able to access a FreeBSD box from another FreeBSD box. I rarely access a Windows machine from FreeBSD as it is just easier to do it the other way around. Anyway, I have been given a few ideas to follow upon. Thanks! -- Carmel car...@hotmail.com If you're doing stuff on a LAN, and you want semi-permanent shares the easiest method is to use sshfs. NFS works fine it, it's a better solution than Samba considering you're new requires. one time transfers or backups are best handles by some combination of scp/rsync/rdiff-backup -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 02:48:58PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 12:25:38 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: [snip] It's still a little unclear. If you want the FreeBSD systems to participate in the Windows networking, look at mount_smbfs and Samba. I want to be able to access a FreeBSD box from another FreeBSD box. I rarely access a Windows machine from FreeBSD as it is just easier to do it the other way around. Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? jerry Anyway, I have been given a few ideas to follow upon. Thanks! -- Carmel car...@hotmail.com SAFETY I can live without Someone I love But not without Someone I need. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 02:53:17PM -0400, Jerry McAllister wrote: On Tue, Sep 22, 2009 at 02:48:58PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 12:25:38 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: [snip] It's still a little unclear. If you want the FreeBSD systems to participate in the Windows networking, look at mount_smbfs and Samba. I want to be able to access a FreeBSD box from another FreeBSD box. I rarely access a Windows machine from FreeBSD as it is just easier to do it the other way around. Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? It would, but he's approaching the problem with Windows-colored glasses. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 01:39:53PM -0400, Carmel NY wrote: Most of my networking experience is based on a Windows. Networking two or more PCs together in a Window's environment is easy. Unfortunately, I am not getting anywhere accomplishing the same with multiple FreeBSD machines. I can get them networked with Window's machines; however, not with each other. FYI, syncronizing files between FreeBSD and other UNIX-like systems is quite easy with rsync [http://www.samba.org/rsync/]. This is also quite easy to automate (e.g. running rsync from cron). For simple and fast data exchange, nothing beats netcat. [nc(1)] For remote backups I tend to pipe the output of dump(8) through netcat on one machine, and pipe the output from a listening netcat on another machine to a file. Suppose I want to backup machine 'foo' to machine 'bar'. On 'bar' I would start the following command: 'nc -l 65000 |bzip2 -c foo-root-20090922.dump.bz2'. On 'foo' I would then start the following command as root: 'dump -0 -a -C 8 -L -u -f - /|nc bar 65000' Typically I would be doing this sitting behind one of those machines with the X window system running and a local terminal and a terminal running ssh to the other machine open. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpm87CJEgLmr.pgp Description: PGP signature
Re: network freebsd computers
On Tue, 22 Sep 2009 14:53:17 -0400 Jerry McAllister jerr...@msu.edu wrote: [snip] Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? -- Carmel car...@hotmail.com Lady Luck brings added income today. Lady friend takes it away tonight. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
Carmel NY carmel...@hotmail.com writes: On Tue, 22 Sep 2009 14:53:17 -0400 Jerry McAllister jerr...@msu.edu wrote: [snip] Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? Of course. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 2:27 PM, Carmel NY carmel...@hotmail.com wrote: On Tue, 22 Sep 2009 14:53:17 -0400 Jerry McAllister jerr...@msu.edu wrote: [snip] Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? Yes. But, before this thread turns into your personal tutorial, have a look at the documentation on freebsd.org. -- Carmel car...@hotmail.com Lady Luck brings added income today. Lady friend takes it away tonight. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, 22 Sep 2009 14:08:21 -0500 David Kelly dke...@hiwaay.net wrote: [snip] It would, but he's approaching the problem with Windows-colored glasses. I am not sure what that is even suppose to mean, so I'll just ignore it. -- Carmel car...@hotmail.com Beware of friends who are false and deceitful. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, 22 Sep 2009 21:08:44 +0200 Roland Smith rsm...@xs4all.nl wrote: On Tue, Sep 22, 2009 at 01:39:53PM -0400, Carmel NY wrote: Most of my networking experience is based on a Windows. Networking two or more PCs together in a Window's environment is easy. Unfortunately, I am not getting anywhere accomplishing the same with multiple FreeBSD machines. I can get them networked with Window's machines; however, not with each other. FYI, syncronizing files between FreeBSD and other UNIX-like systems is quite easy with rsync [http://www.samba.org/rsync/]. This is also quite easy to automate (e.g. running rsync from cron). I use rsync quite often. It is not relevant to this discussion however. For simple and fast data exchange, nothing beats netcat. [nc(1)] For remote backups I tend to pipe the output of dump(8) through netcat on one machine, and pipe the output from a listening netcat on another machine to a file. Suppose I want to backup machine 'foo' to machine 'bar'. On 'bar' I would start the following command: 'nc -l 65000 |bzip2 -c foo-root-20090922.dump.bz2'. On 'foo' I would then start the following command as root: 'dump -0 -a -C 8 -L -u -f - /|nc bar 65000' Useful information; however, not relevant. Typically I would be doing this sitting behind one of those machines with the X window system running and a local terminal and a terminal running ssh to the other machine open. I have not experimented with that yet. If needed, would I be able to run a program that required a GUI on the remote machine, or would I need to install and load all the X programs also? -- Carmel car...@hotmail.com The person who marries for money usually earns every penny of it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 03:35:44PM -0400, Carmel NY wrote: Typically I would be doing this sitting behind one of those machines with the X window system running and a local terminal and a terminal running ssh to the other machine open. I have not experimented with that yet. If needed, would I be able to run a program that required a GUI on the remote machine, or would I need to install and load all the X programs also? You can run a program on the remote machine and have it display on your local machine. If you set the DISPLAY variable on the remote machine to point to your local machine it should work, provided that you are not blocking the ports used by X (6000-6063, IIRC). You can also use xon(1) to start an X program on a remote machine. Keep in mind that not all X protocol extensions are supported over the network, though. You will need the X11 libraries on the remote machine, but not the server. If you are connecting via ssh, you can also configure that to allow X11 forwarding, if you want to keep the connection secure. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpN3a6NW5BnV.pgp Description: PGP signature
Re: network freebsd computers
On Sep 22, 2009, at 3:27 PM, Carmel NY wrote: On Tue, 22 Sep 2009 14:53:17 -0400 Jerry McAllister jerr...@msu.edu wrote: [snip] Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? -- Carmel car...@hotmail.com Absolutely. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 03:29:43PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 14:08:21 -0500 David Kelly dke...@hiwaay.net wrote: [snip] It would, but he's approaching the problem with Windows-colored glasses. I am not sure what that is even suppose to mean, so I'll just ignore it. It means you are trying to make Unix conform to your Windows habits. For security, simplicity, and security (yes, security twice) we are not in the habit of wantonly sharing our file systems. Historically remote login has been difficult on Windows systems while file(system) sharing has been relatively easy so Windows Administrators learned how to manage systems by pushing files around on shared file systems. I'm saying it sounds an awful lot like that is what you are trying to do. If so then you will quickly find Unix doesn't like to let root (Administrator) easily cross system boundaries. Meanwhile others have listed a multitude of utilities for shooting files across multiple machines, including simple terminal login and more advanced GUI X11 login. None of which use shared file systems as their core connection method. Expanding on what I said earlier, if joe is userid 1001, do not reuse 1001 on any other machine unless joe has an account there too. Unix file ownership is by userid and groupid *numbers*. The number doesn't have to be defined in the password or group databases to be used. Most file sync and archivers only use the numbers. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 03:40:41PM -0500, David Kelly wrote: On Tue, Sep 22, 2009 at 03:29:43PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 14:08:21 -0500 David Kelly dke...@hiwaay.net wrote: [snip] It would, but he's approaching the problem with Windows-colored glasses. I am not sure what that is even suppose to mean, so I'll just ignore it. It means you are trying to make Unix conform to your Windows habits. For security, simplicity, and security (yes, security twice) we are not in the habit of wantonly sharing our file systems. Historically remote login has been difficult on Windows systems while file(system) sharing has been relatively easy so Windows Administrators learned how to manage systems by pushing files around on shared file systems. I'm saying it sounds an awful lot like that is what you are trying to do. If so then you will quickly find Unix doesn't like to let root (Administrator) easily cross system boundaries. Really, it sounds like this guy is a candidate for AFS. Actually probably serious over-kill for his situation, but it does wonders.I think there is now (again) an OpenAFS for FreeBSD. AFS plus X-windows would more than do it. jerry Meanwhile others have listed a multitude of utilities for shooting files across multiple machines, including simple terminal login and more advanced GUI X11 login. None of which use shared file systems as their core connection method. Expanding on what I said earlier, if joe is userid 1001, do not reuse 1001 on any other machine unless joe has an account there too. Unix file ownership is by userid and groupid *numbers*. The number doesn't have to be defined in the password or group databases to be used. Most file sync and archivers only use the numbers. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 03:27:35PM -0400, Carmel NY wrote: On Tue, 22 Sep 2009 14:53:17 -0400 Jerry McAllister jerr...@msu.edu wrote: [snip] Am I missing something or would ssh, scp and directing your Xwindows display from the headless machine to a desktop X server cover everything you are asking for? I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? It will put a key there for every place you go to with ssh. The only annoyance is when you upgrade a machine, or otherwise cause the key for a machine to change, you may have to go in to that file and manually delete the old key before it will store another one for the same address. That is easy, but I always forget to do it until the key is refused, and of course, I am in a hurry. jerry -- Carmel car...@hotmail.com Lady Luck brings added income today. Lady friend takes it away tonight. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 04:46:49PM -0400, Jerry McAllister wrote: On Tue, Sep 22, 2009 at 03:27:35PM -0400, Carmel NY wrote: I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? It will put a key there for every place you go to with ssh. I think this is the place one puts the public key of accounts (not the host) from which one is *coming* from that one wishes to accept login without further challenge. ~/.ssh/known_hosts automatically (prompted first time) records the host public key of places you have been so as to warn you that the connection is not to a previously known machine. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 4:22 PM, David Kelly dke...@hiwaay.net wrote: On Tue, Sep 22, 2009 at 04:46:49PM -0400, Jerry McAllister wrote: On Tue, Sep 22, 2009 at 03:27:35PM -0400, Carmel NY wrote: I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? It will put a key there for every place you go to with ssh. I think this is the place one puts the public key of accounts (not the host) from which one is *coming* from that one wishes to accept login without further challenge. ~/.ssh/known_hosts automatically (prompted first time) records the host public key of places you have been so as to warn you that the connection is not to a previously known machine. While this is correct, as I said before, let's not let this thread be a regurgitation of the documentation. I think the M$/OP dude has been lead down the right path and needs to reach the end (more or less) on his own. Our bandwidth should be devoted to more important things, like . . . . well . . . anything else. (Yes, yes . . . I took up bandwidth to make this silly comment. Nip-it-in-the-bud, so to speak) -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 04:22:54PM -0500, David Kelly wrote: On Tue, Sep 22, 2009 at 04:46:49PM -0400, Jerry McAllister wrote: On Tue, Sep 22, 2009 at 03:27:35PM -0400, Carmel NY wrote: I was just playing around with ssh. Would it be possible to store multiple keys in the ~/.ssh/authorized_keys file? It will put a key there for every place you go to with ssh. I think this is the place one puts the public key of accounts (not the host) from which one is *coming* from that one wishes to accept login without further challenge. ~/.ssh/known_hosts automatically (prompted first time) records the host public key of places you have been so as to warn you that the connection is not to a previously known machine. You are right. I didn't look at the file name closely. You can still have more than one. jerry -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: network freebsd computers
On Tue, Sep 22, 2009 at 02:12:48PM -0400, Carmel NY wrote: Presently, I have Samba set up on my FreeBSD machines. Windows can access the shared directories without any problems. I also have Putty installed on the Windows machines so I can directly access the FreeBSD boxes when required. I want the same functionality between the FreeBSD boxes. Eventually, at least one of them will be run headless; the mail server in particular. I can find a virtual cornucopia of information on networking Windows machines; Microsoft even includes a wizard to accomplish it. However, there does not seem to be as much information regarding non-Windows products. At present, all machines are connected, either wired or wireless, through a linksys router. Okay, so it sounds like you want to be able to do two things between your FreeBSD systems: 1. You want to be able to log into them remotely, as you do from MS Windows machines using PuTTY. This is trivially accomplished using a tool that is already installed on all your FreeBSD machines, unless you have a very abnormal install. It's called OpenSSH. Assuming you have either DHCP managing hostname resolution on your network or all the appropriate entries in your /etc/hosts file, you can log into remote machine bar as username foo like so: ssh f...@bar 2. You want to be able to access the remote filesystem as an extension of however you browse local filesystems (using Dolphin, Konqueror, the shell, whatever). To do this, you must mount the remote filesystem on the local system. To do *that*, you must have some kind of network filesystem software running -- a server on the remote machine, and a client on the local machine. NFS is the generally accepted normal way to do so on Unix systems. If you're using Samba on your FreeBSD machines anyway, you should be able to use Samba to do so between FreeBSD machines as well (and others in this discussion have mentioned some starting points for doing so). Another option is to use sshfs, which is a network filesystem tool that uses the SSH protocol to let you mount remote filesystems locally. Of course, depending on what you *actually* want to do from one moment to the next with your remote filesystem, you could use SCP and SFTP (part of the OpenSSH suite of remote access utilities) to transfer files back and forth. I use SSH and SCP quite extensively, and occasionally use sshfs (for things like using Herrie to play music on the local machine from a directory on a remote fileserver). I haven't had need for Samba for several years, because I just interact with MS Windows that much. Your mileage may vary. I hope this helps get you on the track to solving the problem. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpoi1uW3xZGH.pgp Description: PGP signature
Re: network freebsd computers
On Tue, Sep 22, 2009 at 09:51:42PM +0200, Roland Smith wrote: On Tue, Sep 22, 2009 at 03:35:44PM -0400, Carmel NY wrote: Typically I would be doing this sitting behind one of those machines with the X window system running and a local terminal and a terminal running ssh to the other machine open. I have not experimented with that yet. If needed, would I be able to run a program that required a GUI on the remote machine, or would I need to install and load all the X programs also? You can run a program on the remote machine and have it display on your local machine. If you set the DISPLAY variable on the remote machine to point to your local machine it should work, provided that you are not blocking the ports used by X (6000-6063, IIRC). You can also use xon(1) to start an X program on a remote machine. Keep in mind that not all X protocol extensions are supported over the network, though. You will need the X11 libraries on the remote machine, but not the server. If you are connecting via ssh, you can also configure that to allow X11 forwarding, if you want to keep the connection secure. I keep X forwarding disabled in configuration and, when necessary, enable it for one specific connection using the -X option for SSH. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpD3pmBpJtpC.pgp Description: PGP signature
