Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Sharing with whom? With which os? Are you maybe trying to share something installed with wine with Windows machines?
If so, you should reconsider completely dropping the idea, because:
There might be license issues, most licenses are for personal (1 user, one machine) usage.
Windows programs do not install everything into a single directory, they spread a lot of files around many system directories, and they also make changes to the registry, some of which might be needed to operate, whatever you installed in wine will change the wine registry, and not the Windows one obviously.
Some programs will simply fail to operate because they are designed based on silly assumptions.
If you want to share the wine installation amongst many linux machines, you will at least find one problem: permissions.
Wine installs the files of a given program in subdirectories under ~/.wine/drive_c/, being '~' the home directory of the user that did the install. This means that under wine, installations are *local* to a single user, and not *system wide*. I never did this, but sharing an install should be just a matter of moving the relevant ~/.wine/ directory wherever you want it to be, fixing the permissions and then setting the WINEPREFFIX conveniently to that directory.
However even then you are gonna have issues, because any file created or modified by this app will probably be created using the permissions for whatever user is currently using the program, which means that later when a different user comes will probably not be able to read from and/or write to that file.
If you manage to overcome that problem, then local vs. network is mostly irrelevant.
If you don't meant either of these two things, please, explain better what are you trying to do.
im trying to share an application that i can only install using wine since it is microsoft relevant, no licensing issues when it comes to sharing as its a network program with 10 user license only need to use 8
I am trying to network to 8 winxp pro machines
The program only sits in one folder and its that folder i need to share, the problem is i cant find that folder, and wine just says not yet implemented. the file need to have read and write facilites, and if its password protected then even better but not nessary
Wine installs the stuff in ~/.wine/, as said on my previous post, being ~ the home directory of the relevant user. For example, if your user is called "foo", his wine directory will be /home/foo/.wine/drive_c/. There you will find subdirectories like "windows", "program files", etc. Just like you would have in a regular Windows installation.
I have no idea what that "not implemented" that you say mean. When and where do you read that? Has the program an installer that you run using wine or is just self contained in a directory, a zip file or something like that? If it has an installer, it surely will install in /home/<youruser>/.wine/drive_c/, maybe under "Program Files" (or the equivalent depending on your locale settings), but not necessarily.
If you are using the root user, it will be installed under /root/.wine/drive_c/, but really, I wouldn't *Ever* use wine as root. If you are doing that, better just run windows and be root all the time.
You can take the program directory and just copy it to your samba or nfs share, so every computer having access to that share will be able to see the files. Samba can handle the permissions and password stuff as well. If your program is really able to run from a single directory and don't require anything from the registry or the windows directory (meaning it's truly self-contained) then you can put it in the share just like you would do with any other file.
the not yet implemented was in wine if u go through the menu you can find something that says "share as" whenever i click on that or as a matter of fact pretty much anything in the menu when clicked on to start, comes up with that error if you try to run it
i used the smb.conf file and added the root into there for the share, only way i could find the file, samba wont acces .wine as its a hidden folder and niether will the terminal.
so now i shared it, now i can see it on my network, but now i am back to where i started with all my fustrations with samba, i cant share a file that was not created by me, i can see it on a network but i cant access it from the network. i give the file the same access details and everything as my first shares that i can access that i created but all it comes up with when i try to access it is the network name cannot be found.
in wine if you go applications - wine - wine file you get a graphical user interface for windows file structure not wine itself, sorry for the lack of imformation on my part, im still getting used to this full information full answer syndrom, as for the program its a special program developed by the head office of our Schools curriculim, you could say we run a school that is run like a franchise
The prgram itself teaches kids to read and learn maths and other things, this program uses of all things windows access as its primary database. now i know for a fact that i cant run this program in linux, and i dont need to, i just need to share it so that the xp machines can run it, i was running it in nt4 but the problem i had there was the virus problem, i get one virus and thats my program gone. hence trying to use linux, now if its a lost cause i will quit now, but as file servers go, linux is the best, or so i am told, first time trying to install and i suppose fedora may not have been my best choice but it looked good
AFAIK winefile is just the wine port of windows explorer (filemanager) fom windows 3.1
It is as far as I can see, no different than the filemanager you already have.
The only thing you can't see from there - it seems from a quick look - is the ~/.wine directory, where all the windows programs are installed.
As was said: the structure inside the .wine directory is similar to windows.
in ~/.wine/drive_c/ you will find your program files
You don't need wine to share that .exe file for that program. It is just a file and can be shared with e.g. samba.
(given that you know where it is)
If you don't want to actually run it in wine, it can be stored anywhere you like and shared from there.
It has nothing to do with wine just because it is a windows program - its just a file.
it is just a folder that needs to be shared, once shared everyone can access it and write to it, only problem is in group u must make the username the same as guest so that you can access it from outside, otherwise you dont have file permission to share the file using samba, it seems that samba shares and files shares affect each other.
I haven't all the info, I don't know the degree of skill of whomever even suggested you this approach (I certainly would not). But if you are doing this simply to host the files, hoping that they will be safer than they are in Windows (from viruses and malware in general) you are simply complicating your life for nothing.
Think about it: a virus is just a windows program. If you, from Windows, can use your app and instruct it to write the db files, modify them, etc. etc. etc., tell me, what in the worl will stop a Windows virus working in your machine from doing the same? The virus will have the same permissions over the samba share than your user has, so... What's the whole point of this?
good point, i suppose i never really thought about it, but it works all the same, and now i will use this knowledge towards bettering my own experience in linux, since from all this i did learn one valuable thing, linux is an awesome operating system.
and the point you ask is that i now dont need to go buy windows server 2003 or xp to waste as a server that is going to sit there and do nothing but share a silly folder in a school,
i do already have this setup as explained, but the machine is so badly infected i cant clean it, short of formatting and starting again, so thought lets try linux, less chance of it getting infected, the problem i had was not the virus infecting it from outside, but rather inside the machine, now i dont know enough as to whether linux can get infected like that, but it certainly saves me when its time to upgrade in the future as i just have to pull out an old pentium 3 or whatever i have lying around and using that. and as i have to go through this whole procedure with either nt4 or linux, why not linux, if it worked i have less chance of it crashing on me and less maintance, so in that sense linux outways microsoft