SliTaz Forum
You are not logged in.
Pages: 1
I don't know what actually doing. I worked with slitaz-base-files using mercurial. When I install this project to my regular SliTaz installation, I loose my tux user.
[c]
tux@slitaz:/home/hg/slitaz-base-files$ su
Password:
root@slitaz:/home/hg/slitaz-base-files# make install
Compiling fr mo file...
Compiling ru mo file...
install -m 0755 -d /usr/share/locale
cp -a po/mo/* /usr/share/locale
cp -a rootfs/* /
install -m 0755 -d /usr/share/doc/slitaz
cp -a doc/* /usr/share/doc/slitaz
chown -R root.root /usr/share/doc/slitaz
root@slitaz:/home/hg/slitaz-base-files# exit
@slitaz:/home/hg/slitaz-base-files$ whoami
whoami: unknown uid 1000
@slitaz:/home/hg/slitaz-base-files$ cd
@slitaz:/home/tux$
[/c]
If I log out from system, then I can't log in as tux, only as root.
Thanks I have not "full" install, and all worked as usually after rebooting from my USB-SliTaz.
Offline
Sounds like you had a similar day to me yesterday. Never use leafpad to edit /boot/grub/menu.lst - It wiped it and I had to boot SliTaz by hand using grub's command line. The upside? I now know how to do that if I need to and I also now know why it sometimes throws the tainted kernel error (no root= specified), but it was a real pain rewriting the menu.lst from scratch...
Anyway, I have to ask. Why is it chown /usr/share/doc/slitaz to root.root (should be root:root) recursively and why change the user and group to root? Shouldn't all users have access to SliTaz's docs?
Offline
Invaluable experience 
In a few words, I think that my trouble is a result of meeting stable system with "cooking" "package". Maybe, I need to switch to cooking 'coz I'm always at the edge with my coding.
I want to see diff between stable system and new installed files, but have no time.
Shouldn't all users have access to SliTaz's docs?
You mean read access?
Offline
Yes, read access. Forcing user and group to root tends to break access for normal users 
Use cooking at your own risk. Incidentally, don't use irqpoll - it breaks avi video rendering speed for high pixel count videos for some reason. Disabling it fixes it again.
Offline
I think chmod 644 solves system documentation read needs of users.
Code with "root.root" is not mine, it's very old. I fix it now, thanks!
I find root of my trouble with installing "slitaz-base-files" from hg. I attached main differences from this file sets.
I'll just not install these "very system " files and still on 4.0.
PS: I think, the most right way is to create .tazpkg from this repo and then install it. But, time, time... Always lack of it.
Offline
Hi Aleksej,
Ther is nothing wrong with slitaz-base-files but you should NEVER do a 'make install' directly, it will owerwrite /etc/passwd and other system settings so no root or user account anymore (it install some radicaly minimal auth files), make install is only used for packaging and on upgrade it'a the packages manager who backup/restore any config files.
In slitaz-base-files you can do a 'make install-libtaz' or libpkg but not much more.
Offline
Hopefully you mentioned that in the README file.
Offline
Nope I did not :-) Because Aleksej is the first guy who did a 'make install' from the slitaz-base-files Hg repo! But I will and set DESTDIR automaticaly so even with make install it dont break anything...
Offline
Pages: 1
[ Generated in 0.024 seconds, 11 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]