Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: P5music on November 05, 2010, 12:00:57 PM
-
Hello,
I symlinked /mnt/sda1/home/pc/.wine folder of another linux system to .wine folder in tinycore system but now tinycore says that .wine is not owned by itself.
So I ask how to regain ownership on the .wine folder and recurse it without make the other linux system lose its own.
Thanks
-
You can't.
What you might do is create a new group in TC to match the wine group, and add the tc user to the wine group.
You could also try to add the wine user to tc and login as that user.
-
is it possible to tell mint to "open" that folder to everyone?
if not, how can I create a new user on tinycore or new group? I mean the commands line instructions.
-
To add a user, run adduser.
User and group information are stored in
/etc/passwd
/etc/shadow
/etc/group
/etc/gshadow
Be sure to add these 4 files to the .filetool.lst so they are backed up.
-
Hello,
I need to start jack in real-time mode but it cannot and I get an error message about permissions.
But grep audio /etc/group says that tc is in audio group.
I can start real-time mode with sudo prefix but then I cannot access .wine applications because .wine is not owned by sudo.
Which are the possible solutions?
Thanks in advance for your response, very useful so far.
-
.wine is not owned by sudo.
That does not make any sense at all.
Best to read up about the 'sudo' command ;)
-
ok,
I can start jack in real-time mode with
sudo qjackctl (then I press "play" button)
then I run Reaper DAW with
wine reaper
but Reaper cannot see wineasio inputs and outputs
so I think I have to type
sudo wine reaper
but I get
/home/tc/.wine is not owned by you.
Any hint?
-
http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014
http://wiki.jswindle.com/index.php/Tips_and_Tricks_Page#A_brief_FAQ
-
but why cannot I start jack in real-time mode if I'm not root?
-
Hi,
I made a symlink in root directory and then put
root
line in .filetool.lst to make it persistent (along with other things made with root).
After rebooting, root permission on that symlink is lost so I guess that tc saves those files with its own permission.
How to solve this?
Thanks in advance.
-
What I would try first, is making a new extension for those things you want to save in root, then not saving it in backup.
To make an extension, the squashfs-tools-4.0 extension needs to be installed.
Begin by creating directories. Open the Root Terminal and type:
mkdir -p /home/myext/root
Put everything you want saved in root.
To make a extension called "myrootfiles.tcz," open the Root Terminal, and type:
cd /home/myext
mksquashfs root/ myrootfiles.tcz
Put the new extension in the /tce/optional directory. Keep a copy somewhere else, as if you run Update Apps, it may be lost.
Add the name of the new extension to the .dep file of the program that uses these files. (Another option is to add it to On Boot.)
I don't use backup at all. I use persistent /home and /opt, and make extensions for anything else I want saved.
-
I just made such a root:root simlink in /root and backed up. It worked just fine, permissions and ownership restored correctly.
-
Have you searched the forum for "realtime" and read everything possibly related?
-
root permission on that symlink is lost
symlinks do not have permissions.
-
This is what I do:
Part I
1 - as root, create "wine" folder in home/tc (not ".wine" : .wine is already there)
2 - as root, copy .wine content in "wine"
Part II
3 - run wine as root so it creates its .wine folder in /root
4 - delete .wine folder in /root
5 - as root, create a .wine symlink in /root to home/tc/wine (see Part I)
6 - I execute programs in root/.wine/drive_c/Program Files and everything is fine, no errors
7 - reboot
8 - check /root folder: .wine symlink is still there
9 - I try to execute programs again in root/.wine/drive_c/Program Files but I get: .wine is not owned by you.
Why this after rebooting?
Thanks
-
Hello,
I need to know where wine permissions are written in regard to users.
That is:
if I run wine with a particolar user it creates its directories and I can execute programs installed with that wine just with that user. If I change user, I have to do the same.
But If I create a symlink to .wine, wine does not recognize its user and the terminal says ".wine is not owned by you".
How to make that wine recall what's its user? Which file I have to edit?
Thanks