Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Gerald Jansen on September 28, 1999, 04:15:17 AM
-
I am attempting to load the Windows 2000 server extensions on to a e-smith server. I download the necessary tar file using an NT Workstation. I put the tar file in a folder on the e-smith server. The folder |root appears on the Samba server. However wwhen I attempt to find the file in "root" on e-smith, it isn't there when I attempt to find it while in "telnet" Why? Question. Is the folder "root" as viewed while under Samba, the same directory as "root" as viewed under telnet. If not why not?
Best Regards,
Jerry
-
Gerald Jansen wrote:
> "telnet" Why? Question. Is the
> folder "root" as viewed while
> under Samba, the same directory as
> "root" as viewed under telnet. If
> not why not?
The e-smith server and gateway, like any Unix system, has a single hierarchical namespace for files. When you telnet into the system as "root", you start in the root home directory (/root) and from there you have the run of the system. You can change to any directory in the entire hierarchy.
Samba presents portions of that filesystem hierarchy to other Windows machines over the network. The Samba configuration file /etc/smb.conf specifies which parts of the filesystem are presented over the network.
We've tried to make the e-smith file hierarchy as logical and as easy to understand as possible. On an e-smith server and gateway, all files that are accessible over the network are located in:
/home/e-smith/files
If you have copied the file to one of the primary directories using Samba, you'll find it in:
/home/e-smith/files/primary
If you stored it in an ibay, you'll find the file in:
/home/e-smith/ibays
Or if you stored it in a user's home directory, the file will be somewhere in:
/home/e-smith/users
To get a complete list of the filesystem hierarchy starting from /home/e-smith, type the command:
find /home/e-smith
Hope this helps clear things up. Best regards,
- Joe
-
Thank you for the explanation. My inexperience with Linux was the real problem. I knew about the file structure and did poke arround a bit and used "whereis" to no avail. Now that I know where to look I should be on my way to solving the delima.
Thanks again
-
Gerald Jansen wrote:
> Thank you for the explanation.
You're welcome! Actually, in rereading my response I see that I made a couple of typographical errors. I meant to write the following:
If you stored it in an ibay, you'll find the file in:
/home/e-smith/files/ibays
Or if you stored it in a user's home directory, the file will be somewhere in:
/home/e-smith/files/users
In my previous posting I omitted the "files" part of the pathname, but you got the gist of it anyway :-)
Best regards,
- Joe
-
A note......when you download a *Unix* file using NT it can alter the file name by replacing "excess" dots with an underscore. So when you run the install_spt file and it cannot find the extensions file this is the reason why. renaming the file to it's correct name will allow the script to find it.