[opensuse] what networking file system to use for our home office?
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me 1. it is easy to set up NFS server on dynamic IP address (fixed FQDN) with fixed IP address clients, 2. but not possible to set up NFS server on fixed IP address with dynamic IP address (fixed FQDN) clients. In detail, the FQDN in /etc/exports are checked by 1. first comparing its IP address with client's IP address, 2. then, by comparing client's IP address' reverse lookup FQDN with what is writen in /etc/exports, the latter check kills dynamic IP address client possibility. NFS document says it is for security concern against man-in-the-middle, which I don't mind much, as we work on non-profit and open-to-public documents on the NFS share. I read if I want to have dynamic IP address client with write writes, I need to set up kerberos, whose learning curve make me feel it overkill, since we only have a small home office with a single client (my wife) and I don't expect the number of users to grow. My friends told me: NFS is for corporate environment. For loose security and easy set up requirement, like in my home office, I should use Windows File Sharing service instead. Should I switch to Windows File Sharing? Does it handle UTF8 well (many files have Chinese name)? Does it handle execution bit well (as we sometimes use it)? What about special characters like column symbol and question marks as we use it in some filenames? By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it. Best regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 21/02/10 16:23, Zhang Weiwu wrote:
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
[pruned]
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
Best regards
Forgive me for asking, but you appear to be associated with the Chinese company- http://www.realss.com/ Your speciality is Ubuntu (with gnome DT) so have you asked your question(s) in the Ubuntu "help desk" or forum? Or are you simply spreading your question(s) to see who may reply the quickest? Just asking.... and no offence meant, especially as you are asking the question(s) "so that [you are able] to concentrate on [your] non-IT profession." BC -- A hole has been found in the nudist camp wall. Police are looking into it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin worte:
Forgive me for asking, but you appear to be associated with the Chinese company-
Your speciality is Ubuntu (with gnome DT) so have you asked your question(s) in the Ubuntu "help desk" or forum? Or are you simply spreading your question(s) to see who may reply the quickest?
Just asking.... and no offence meant, especially as you are asking the question(s) "so that [you are able] to concentrate on [your] non-IT profession."
Ah, so you looked at the company profile. Well, in fact I myself is an IT consultant, but working on a very different sector as others on OpenSUSE list. I work on requirement identification, documentation, clearify business workflow so that IT systems can be adopted, training for user tool (not training developers or administrators), bug reporting, IT contractual issues, identify which report is needed form databse to give to which manager etc, and project management. However in opensource technical forums I learned to be aware everybody else expect IT professionals to be coding expert or system administrators. I spent most of my time working on business requirements, my working is closely related to IT but I don't produce software code, I produce slideshows, workflow charts, documents in ODT, project resources charts and so like. I even don't very frequently uses command line. Many other coding friend consider me not so different than the lusers, that is, "stupid" non-IT professional users. I am frustrated as much as the lusers if you throw me a few hundreds lines of configuration options and expect me to consume all. In the end, I found it is easier to describe myself as "a stuipd management guy" to local coding club etc, so I did the same when asking openSUSE list. We have brilliant coding staff but I also wishes to avoid using their working hours for my home office especially at now the Chinese new year. And, in the company we offer Ubuntu support but not OpenSUSE, however my wife don't have to follow company policy when she choose openSuSE to run, I had to follow her and support her. I am sorry if my behavior of describe myself non-IT considered not good on the list, but you might understand if you are willing to consider that most Linux professionals I know consider being IT professional /is/ to work with server administration, command line and writing software code. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 February 2010 01:21:47 Zhang Weiwu wrote: <snipped>
now the Chinese new year.
Hello and Happy New Year, Zhang Weiwu! Good to see you here again. I hope all is well with you and your family. [ Please give your dog a biscuit for me! :-) ]
And, in the company we offer Ubuntu support but not OpenSUSE, however my wife don't have to follow company policy when she choose openSuSE to run, I had to follow her and support her.
Yes, it is very important to support one's significant other!
I am sorry if my behavior of describe myself non-IT considered not good on the list, but you might understand if you are willing to consider that most Linux professionals I know consider being IT professional /is/ to work with server administration, command line and writing software code.
Very few of us knows all there is to know about Linux, in general, or openSUSE, specifically (it is a moving target, anyway) which I thought was the original purpose for this very friendly list to exist. In any case, I think you asked good questions in a proper way. I think there has just been a small miscommunication (a 'hiccup') in the process of understanding your requirement which appears now to have been quickly ironed out. Take care and regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carl Hartung 写道:
On Sunday 21 February 2010 01:21:47 Zhang Weiwu wrote: <snipped>
now the Chinese new year.
Hello and Happy New Year, Zhang Weiwu!
You too!
Good to see you here again.
I hope all is well with you and your family. [ Please give your dog a biscuit for me! :-) ]
Oh thank you very much for still remembering my dog! Thanks to you as always:) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
On 21/02/10 16:23, Zhang Weiwu wrote:
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
[pruned]
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
Best regards
Forgive me for asking, but you appear to be associated with the Chinese company-
Your speciality is Ubuntu (with gnome DT) so have you asked your question(s) in the Ubuntu "help desk" or forum? Or are you simply spreading your question(s) to see who may reply the quickest?
I'm curious... Why do you think someone should have to justify why they are asking a question on this forum?
Just asking.... and no offence meant, especially as you are asking the question(s) "so that [you are able] to concentrate on [your] non-IT profession."
It has been my experience that when people say "no offence" or "I don't want to interrupt...but" they are doing exactly that. Especially when their claim of "non offence" is followed by a snide remark. Besides that, the question being asked is a general question with no distro specific component. You seem to have spent more time doing research on the poster so you can be contrary rather than putting any effort into helping. -- 葛斯克 愛德華 / 台北市八德路四段 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 21/02/10 18:38, Ed Greshko wrote:
Basil Chupin wrote:
On 21/02/10 16:23, Zhang Weiwu wrote:
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
[pruned]
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
Best regards
Forgive me for asking, but you appear to be associated with the Chinese company-
Your speciality is Ubuntu (with gnome DT) so have you asked your question(s) in the Ubuntu "help desk" or forum? Or are you simply spreading your question(s) to see who may reply the quickest?
I'm curious... Why do you think someone should have to justify why they are asking a question on this forum?
Just asking.... and no offence meant, especially as you are asking the question(s) "so that [you are able] to concentrate on [your] non-IT profession."
It has been my experience that when people say "no offence" or "I don't want to interrupt...but" they are doing exactly that. Especially when their claim of "non offence" is followed by a snide remark.
Besides that, the question being asked is a general question with no distro specific component. You seem to have spent more time doing research on the poster so you can be contrary rather than putting any effort into helping.
OK, so how much have you helped in answering his question? What was* your* motivation to respond to my post the way you did? BC -- She was only a whisky maker but I loved her still. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
On 21/02/10 18:38, Ed Greshko wrote:
Basil Chupin wrote:
On 21/02/10 16:23, Zhang Weiwu wrote:
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
[pruned]
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
Best regards
Forgive me for asking, but you appear to be associated with the Chinese company-
Your speciality is Ubuntu (with gnome DT) so have you asked your question(s) in the Ubuntu "help desk" or forum? Or are you simply spreading your question(s) to see who may reply the quickest?
I'm curious... Why do you think someone should have to justify why they are asking a question on this forum?
Just asking.... and no offence meant, especially as you are asking the question(s) "so that [you are able] to concentrate on [your] non-IT profession."
It has been my experience that when people say "no offence" or "I don't want to interrupt...but" they are doing exactly that. Especially when their claim of "non offence" is followed by a snide remark.
Besides that, the question being asked is a general question with no distro specific component. You seem to have spent more time doing research on the poster so you can be contrary rather than putting any effort into helping.
OK, so how much have you helped in answering his question?
Not yet.
What was* your* motivation to respond to my post the way you did?
To point out, even though it is obvious, that all you seem to do is create a hostile environment. -- 葛斯克 愛德華 / 台北市八德路四段 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Zhang Weiwu wrote:
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
1. it is easy to set up NFS server on dynamic IP address (fixed FQDN) with fixed IP address clients, 2. but not possible to set up NFS server on fixed IP address with dynamic IP address (fixed FQDN) clients.
In detail, the FQDN in /etc/exports are checked by
1. first comparing its IP address with client's IP address, 2. then, by comparing client's IP address' reverse lookup FQDN with what is writen in /etc/exports,
the latter check kills dynamic IP address client possibility. NFS document says it is for security concern against man-in-the-middle, which I don't mind much, as we work on non-profit and open-to-public documents on the NFS share.
I read if I want to have dynamic IP address client with write writes, I need to set up kerberos, whose learning curve make me feel it overkill, since we only have a small home office with a single client (my wife) and I don't expect the number of users to grow.
My friends told me: NFS is for corporate environment. For loose security and easy set up requirement, like in my home office, I should use Windows File Sharing service instead.
Should I switch to Windows File Sharing? Does it handle UTF8 well (many files have Chinese name)? Does it handle execution bit well (as we sometimes use it)? What about special characters like column symbol and question marks as we use it in some filenames?
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
I reread the above several times and I'm still not sure I fully grasp the environment related to your file sharing question. You talk about a home network, but then you also talking about your wife working from Starbucks. Is one of your needs to share files across the internet? I would be more inclined to set up a VPN and when I needed access to files on my home network connect in. When that happens the VPN client would have a fixed IP address on the VPN. In my NFS network at home shares to an entire subnet. Like.... /home/egreshko/kdas 192.168.0.0/255.255.255.0(rw,fsid=0) I don't have my home network set up for VPN since for me sftp is sufficient. But that is how I connect to one of my customer's environments. I make a VPN connection, become a part of their network, and have access to all shares. Both NFS and Windows. As for windows file share handling UFT-8, no problem. I have files with Chinese names on my Linux systems and they present themselves correctly on my Vista and XP systems. -- 葛斯克 愛德華 / 台北市八德路四段 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 21/02/10 20:50, Ed Greshko wrote:
Zhang Weiwu wrote:
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
1. it is easy to set up NFS server on dynamic IP address (fixed FQDN) with fixed IP address clients, 2. but not possible to set up NFS server on fixed IP address with dynamic IP address (fixed FQDN) clients.
In detail, the FQDN in /etc/exports are checked by
1. first comparing its IP address with client's IP address, 2. then, by comparing client's IP address' reverse lookup FQDN with what is writen in /etc/exports,
the latter check kills dynamic IP address client possibility. NFS document says it is for security concern against man-in-the-middle, which I don't mind much, as we work on non-profit and open-to-public documents on the NFS share.
I read if I want to have dynamic IP address client with write writes, I need to set up kerberos, whose learning curve make me feel it overkill, since we only have a small home office with a single client (my wife) and I don't expect the number of users to grow.
My friends told me: NFS is for corporate environment. For loose security and easy set up requirement, like in my home office, I should use Windows File Sharing service instead.
Should I switch to Windows File Sharing? Does it handle UTF8 well (many files have Chinese name)? Does it handle execution bit well (as we sometimes use it)? What about special characters like column symbol and question marks as we use it in some filenames?
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
I reread the above several times and I'm still not sure I fully grasp the environment related to your file sharing question.
You talk about a home network, but then you also talking about your wife working from Starbucks.
Aaah, I see that you are getting there..... But why do you ask such leading questions of the OP? What matters why he is asking the questions? He seeks answers. Are you creating a hostile environment? BC -- She was only a whisky maker but I loved her still. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
On 21/02/10 20:50, Ed Greshko wrote:
Zhang Weiwu wrote:
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
1. it is easy to set up NFS server on dynamic IP address (fixed FQDN) with fixed IP address clients, 2. but not possible to set up NFS server on fixed IP address with dynamic IP address (fixed FQDN) clients.
In detail, the FQDN in /etc/exports are checked by
1. first comparing its IP address with client's IP address, 2. then, by comparing client's IP address' reverse lookup FQDN with what is writen in /etc/exports,
the latter check kills dynamic IP address client possibility. NFS document says it is for security concern against man-in-the-middle, which I don't mind much, as we work on non-profit and open-to-public documents on the NFS share.
I read if I want to have dynamic IP address client with write writes, I need to set up kerberos, whose learning curve make me feel it overkill, since we only have a small home office with a single client (my wife) and I don't expect the number of users to grow.
My friends told me: NFS is for corporate environment. For loose security and easy set up requirement, like in my home office, I should use Windows File Sharing service instead.
Should I switch to Windows File Sharing? Does it handle UTF8 well (many files have Chinese name)? Does it handle execution bit well (as we sometimes use it)? What about special characters like column symbol and question marks as we use it in some filenames?
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
I reread the above several times and I'm still not sure I fully grasp the environment related to your file sharing question.
You talk about a home network, but then you also talking about your wife working from Starbucks.
Aaah, I see that you are getting there.....
But why do you ask such leading questions of the OP?
You don't know what a leading question is.... The questions that have been snipped seek clarification so as to fully understand what is the actual environment.
What matters why he is asking the questions?
That isn't what I asked...and you know it. There is no "why" in my question...and you know it.
He seeks answers.
And in order to provide answers one has to seek to understand the situation. I had already said I didn't understand it from what was said to this point and I'm asking follow-up questions to gain a better understanding. And you know that.
Are you creating a hostile environment?
You know that isn't the case. -- 葛斯克 愛德華 / 台北市八德路四段 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 21/02/10 22:31, Ed Greshko wrote:
Basil Chupin wrote:
On 21/02/10 20:50, Ed Greshko wrote:
Zhang Weiwu wrote:
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
1. it is easy to set up NFS server on dynamic IP address (fixed FQDN) with fixed IP address clients, 2. but not possible to set up NFS server on fixed IP address with dynamic IP address (fixed FQDN) clients.
In detail, the FQDN in /etc/exports are checked by
1. first comparing its IP address with client's IP address, 2. then, by comparing client's IP address' reverse lookup FQDN with what is writen in /etc/exports,
the latter check kills dynamic IP address client possibility. NFS document says it is for security concern against man-in-the-middle, which I don't mind much, as we work on non-profit and open-to-public documents on the NFS share.
I read if I want to have dynamic IP address client with write writes, I need to set up kerberos, whose learning curve make me feel it overkill, since we only have a small home office with a single client (my wife) and I don't expect the number of users to grow.
My friends told me: NFS is for corporate environment. For loose security and easy set up requirement, like in my home office, I should use Windows File Sharing service instead.
Should I switch to Windows File Sharing? Does it handle UTF8 well (many files have Chinese name)? Does it handle execution bit well (as we sometimes use it)? What about special characters like column symbol and question marks as we use it in some filenames?
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
I reread the above several times and I'm still not sure I fully grasp the environment related to your file sharing question.
You talk about a home network, but then you also talking about your wife working from Starbucks.
Aaah, I see that you are getting there.....
But why do you ask such leading questions of the OP?
You don't know what a leading question is....
The questions that have been snipped seek clarification so as to fully understand what is the actual environment.
What matters why he is asking the questions?
That isn't what I asked...and you know it. There is no "why" in my question...and you know it.
He seeks answers.
And in order to provide answers one has to seek to understand the situation. I had already said I didn't understand it from what was said to this point and I'm asking follow-up questions to gain a better understanding. And you know that.
Are you creating a hostile environment?
You know that isn't the case.
Well, if yo have to reread something to see what it is all about - fine. I've had to do it myself sometimes. *BUT*!....I love that Chocolate Point! Had 2 Seal Points of my own. Damn lovely animals....lovely. A third turned up at our front door one night (and we had 2 German Shorthaired Pointers at the time). We let her in, fed her. She came back every night for the next 3 nights. Then, on the night Gough Whitlam's Labor government was elected, December 1972, (and we were having a poker night to celebrate the impending victory) the "Meow" at the door saw Samantha - which is what we called her - bring in her 4 kittens from wherever she was hiding them while she checked us out. All the kittens went to good homes and Samantha went to one person from work - who said that Samantha was absolutely most caring for the 3 young children that he had. She died at a great age for a cat. BC -- She was only a whisky maker but I loved her still. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ed Greshko 写道:
I reread the above several times and I'm still not sure I fully grasp the environment related to your file sharing question.
You talk about a home network, but then you also talking about your wife working from Starbucks. Is one of your needs to share files across the internet?
This is a true conclusion. Sometime across the Internet, yes. Sometimes from her office or at home network (192.168.1.x).
I would be more inclined to set up a VPN and when I needed access to files on my home network connect in.
VPN is okay. In fact I think I am going to use it if there are other no better solution. By "better" I mean it requires a dial up connection set up first, a little bit troublesome. For sure the dial up to VPN offered better security.
As for windows file share handling UFT-8, no problem. I have files with Chinese names on my Linux systems and they present themselves correctly on my Vista and XP systems.
Thanks for this compatibility information. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
May bee I missed something, but it seems to me the easiest way to launch SSH server on Your "server" and from Your clients connect using SFTP or FISH. It is easily done and very safe. You can login using SSH certificates or just let clients' computers to remember passwords. Using ACL or proper group settings You can get also advanced sharing. Best regards, Vojtěch Zeisek Dne Ne 21. února 2010 06:23:52 Zhang Weiwu napsal(a):
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
1. it is easy to set up NFS server on dynamic IP address (fixed FQDN) with fixed IP address clients, 2. but not possible to set up NFS server on fixed IP address with dynamic IP address (fixed FQDN) clients.
In detail, the FQDN in /etc/exports are checked by
1. first comparing its IP address with client's IP address, 2. then, by comparing client's IP address' reverse lookup FQDN with what is writen in /etc/exports,
the latter check kills dynamic IP address client possibility. NFS document says it is for security concern against man-in-the-middle, which I don't mind much, as we work on non-profit and open-to-public documents on the NFS share.
I read if I want to have dynamic IP address client with write writes, I need to set up kerberos, whose learning curve make me feel it overkill, since we only have a small home office with a single client (my wife) and I don't expect the number of users to grow.
My friends told me: NFS is for corporate environment. For loose security and easy set up requirement, like in my home office, I should use Windows File Sharing service instead.
Should I switch to Windows File Sharing? Does it handle UTF8 well (many files have Chinese name)? Does it handle execution bit well (as we sometimes use it)? What about special characters like column symbol and question marks as we use it in some filenames?
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
Best regards -- Vojtěch Zeisek
Komunita openSUSE GNU/Linuxu / Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://web.natur.cuni.cz/~zeisek/
Or You could use SSHFS, http://en.wikipedia.org/wiki/SSHFS Dne Ne 21. února 2010 12:23:50 Vojtěch Zeisek napsal(a):
May bee I missed something, but it seems to me the easiest way to launch SSH server on Your "server" and from Your clients connect using SFTP or FISH. It is easily done and very safe. You can login using SSH certificates or just let clients' computers to remember passwords. Using ACL or proper group settings You can get also advanced sharing. Best regards, Vojtěch Zeisek
Dne Ne 21. února 2010 06:23:52 Zhang Weiwu napsal(a):
Hello. I have been using NFS for a few years for all networking file system needs and only knows how to make that work. Now we have a special problem. Usually our NFS clients who have write access also have fixed IP addresses, this time she doesn't. Looks as if to me
1. it is easy to set up NFS server on dynamic IP address (fixed FQDN) with fixed IP address clients, 2. but not possible to set up NFS server on fixed IP address with dynamic IP address (fixed FQDN) clients.
In detail, the FQDN in /etc/exports are checked by
1. first comparing its IP address with client's IP address, 2. then, by comparing client's IP address' reverse lookup FQDN with what is writen in /etc/exports,
the latter check kills dynamic IP address client possibility. NFS document says it is for security concern against man-in-the-middle, which I don't mind much, as we work on non-profit and open-to-public documents on the NFS share.
I read if I want to have dynamic IP address client with write writes, I need to set up kerberos, whose learning curve make me feel it overkill, since we only have a small home office with a single client (my wife) and I don't expect the number of users to grow.
My friends told me: NFS is for corporate environment. For loose security and easy set up requirement, like in my home office, I should use Windows File Sharing service instead.
Should I switch to Windows File Sharing? Does it handle UTF8 well (many files have Chinese name)? Does it handle execution bit well (as we sometimes use it)? What about special characters like column symbol and question marks as we use it in some filenames?
By the way fixing my wife's IP address is not possible because she might work everywhere, starbucks for example. She is using OpenSUSE 11.0. And, real mount is preferred over gnome virtual file system which is not compatible with some of her tools. I also want to avoid unnecessary learning curve so that to concentrate on my non-IT profession, thus would choose known system (nfs) unless I have to dump it.
Best regards
-- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu / Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://web.natur.cuni.cz/~zeisek/
On Sun, 2010-02-21 at 12:26 +0100, Vojtěch Zeisek wrote:
Or You could use SSHFS, http://en.wikipedia.org/wiki/SSHFS
Or nfs4 with kerberos... this url: http://www.novell.com/coolsolutions/feature/17581.html might be old and about sles, but usefull anyway -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Vojtěch Zeisek 写道:
May bee I missed something, but it seems to me the easiest way to launch SSH server on Your "server" and from Your clients connect using SFTP or FISH. It is easily done and very safe. You can login using SSH certificates or just let clients' computers to remember passwords. Using ACL or proper group settings You can get also advanced sharing. Before I try it, I always cannot forget my previous experience working with ssh remote access with vim (by using vim scp://xxx). It halts 10 to 20 seconds every time I want to save the document on good (I think somewhat >30KBps and ping delay < 200ms) connection. I believe because it tries to establish tcp connection and do key exchange things every time when I want to save it, thus I regard it second best solution than my good old nfs. Besides it require application support sftp protocol or gnome virtual filesystem.
Since you mention sshfs in the following post, I wonder does it maintain a tcp connection? If not, what about save delay (or connection overhead), and if so, can it endure broken tcp connection? My evil ICP (sorry about the wording but no better thing I can think of) cuts low-bandwidth TCP connection at their will and I cannot replace ICP (monoplay business here). Do you endure from slow saving when using sshfs? Thanks in advance. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dne Ne 21. února 2010 14:17:28 Zhang Weiwu napsal(a):
Vojtěch Zeisek 写道:
May bee I missed something, but it seems to me the easiest way to launch SSH server on Your "server" and from Your clients connect using SFTP or FISH. It is easily done and very safe. You can login using SSH certificates or just let clients' computers to remember passwords. Using ACL or proper group settings You can get also advanced sharing.
Before I try it, I always cannot forget my previous experience working with ssh remote access with vim (by using vim scp://xxx). It halts 10 to 20 seconds every time I want to save the document on good (I think somewhat >30KBps and ping delay < 200ms) connection. I believe because
I usually sit at university, so I have good connection, but even from home (using ISDN) it is enough quick.
it tries to establish tcp connection and do key exchange things every time when I want to save it, thus I regard it second best solution than my good old nfs. Besides it require application support sftp protocol or gnome virtual filesystem.
I use KDE, where SFTP is widely supported, I think You can also add network folder using SFTP in Nautilus, or You can use GFTP. SFTP is IMHO widely and very well supported protocol, so I would not be afraid about it. On Windows for example WinSCP.
Since you mention sshfs in the following post, I wonder does it maintain a tcp connection? If not, what about save delay (or connection
I'm not big expert about it, but I think it uses SSH daemon, so it should basically behave same as normal SSH connection. So I would trust it. :-)
overhead), and if so, can it endure broken tcp connection? My evil ICP (sorry about the wording but no better thing I can think of) cuts low-bandwidth TCP connection at their will and I cannot replace ICP (monoplay business here).
Do you endure from slow saving when using sshfs?
I have good experience with it (I use it to connect several computers within local network).
Thanks in advance.
Best regards -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu / Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://web.natur.cuni.cz/~zeisek/
On Sun, 21 Feb 2010 23:47:28 Zhang Weiwu wrote:
Vojtěch Zeisek 写道:
May bee I missed something, but it seems to me the easiest way to launch SSH server on Your "server" and from Your clients connect using SFTP or FISH. It is easily done and very safe. You can login using SSH certificates or just let clients' computers to remember passwords. Using ACL or proper group settings You can get also advanced sharing.
Before I try it, I always cannot forget my previous experience working with ssh remote access with vim (by using vim scp://xxx). It halts 10 to 20 seconds every time I want to save the document on good (I think somewhat >30KBps and ping delay < 200ms) connection. I believe because it tries to establish tcp connection and do key exchange things every time when I want to save it, thus I regard it second best solution than my good old nfs. Besides it require application support sftp protocol or gnome virtual filesystem.
Since you mention sshfs in the following post, I wonder does it maintain a tcp connection? If not, what about save delay (or connection overhead), and if so, can it endure broken tcp connection? My evil ICP (sorry about the wording but no better thing I can think of) cuts low-bandwidth TCP connection at their will and I cannot replace ICP (monoplay business here).
Do you endure from slow saving when using sshfs?
Thanks in advance.
Zhang, I have used sshfs to remotely mount shares on my father's computer from my home. He has a slow connection and it works fine, as long as you don't expect it to be as fast as if the remote end was directly connected on the lan). It is not quite as straightforward to set up the connection as an nfs share; in my experience, it does required a command line instruction to mount and unmount the remote share (but then, I never tried to do it any other way). It does mount the drive locally, like nfs or samba, and thus using it is exactly the same as a drive mounted by any other means. It doesn't require defining specific shares on the server side (unlike nfs or samba); all it requires is that the person logging in via ssh has the appropriate permissions to the path that they want to mount remotely. File ownership can be a minor issue; it helps with sshfs (as with nfs) if the userid/groupid are synchronized on the server and the client. Regarding Samba/Windows File Sharing, it works best with Windows clients. Since your wife is also running Linux remotely, I'd be looking at setting up a VPN tunnel as previously suggested and running nfs over that or trying sshfs. Regards, Rodney. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (7)
-
Basil Chupin -
Carl Hartung -
Ed Greshko -
Hans Witvliet -
Rodney Baker -
Vojtěch Zeisek -
Zhang Weiwu