SliTaz Forum
You are not logged in.
Pages: 1
Reference: http://doc.slitaz.org/en:guides:faq-login
Laptop environment
512M RAM (fixed); No optical drive; Grub4Dos; SliTaz 3.0
Linux environment
All packages updated; tazpkg upgrade
Create new rootfs; tazusb writefs gzip
tazlito writeiso not an option as (1) no optical drive (2) tazlito does not recognize external usb cdrom
Manually replace old rootfs with newly created rootfs
Boot; Cannot Login to Desktop as tux, root only login
mktux.sh output follows
----------
root@slitaz:/media/test# cat mktux.sh
#!/bin/sh
mkdir /home/tux
cd /home/tux
shopt -s dotglob
cp -r /etc/skel/* /home/tux
chown -R tux:SliTaz /home/tux/*
shopt -u dotglob
shopt -u dotglob
chown -R tux:SliTaz /home/tux/.[a-zA-Z0-9]*
root@slitaz:/media/test# ./mktux.sh
mkdir: cannot create directory '/home/tux': File exists
./mktux.sh: line 6: shopt: not found
chown: unknown user/group tux:SliTaz
./mktux.sh: line 9: shopt: not found
./mktux.sh: line 10: shopt: not found
chown: unknown user/group tux:SliTaz
root@slitaz:/mediatest# exit
----------
COMMENTS:
No /home/tux exists, yet cannot create the directory
chown -R USERNAME:USERGROUP /home/USERNAME/*
?What USERGROUP should be used?
Offline
shopt is not a valid Busybox command. prompts the question, what is missing from the faq that is required to resolve the Cannot Login to Desktop problem?
Offline
looking for the same answer. subscribing.
Offline
I have the same problem here too!
Offline
Try the following and remember to replace tux with your username - mine is brenton which makes my chown brenton:brenton and my path is /home/brenton:
1. Open a terminal window like xterm or sakura
2. Type su and press the enter/return key
3. Type your root password and press the enter/return key (default for the LiveCD is root)
4. Type cp -af /etc/skel/* /home/tux
5. Type cp -af /root/* /home/tux
6. Type chown -R tux:tux /home/tux
Offline
Trixar_za,
Many thanks. Add line 3a; Type mkdir /home.tux
Your suggestion creates /home/tux with no preferences (understandable). Now, this gives rise to 3 questions.
#1. After I set my preferences for tux, a reasonable thought is to compress the entire tux directory so I don't keep doing this over and over. ?Can I add a script in the boot process and, before the tux signon appears, to un-compress the file?
#2 On the other end, where can I insert a script that will compress the entire tux directory so I keep all of my stuff?
#3 Do you know if there is anyone amongst the skilled, capable group supporting SliTaz that could correct the tazlito program or, preferably, adapt the usb tool that allows you to create a new rootfs on exit?
Been battling this very issue since 2009. Sincerely appreciate your support. Again, thanks.
Offline
Trixar_za,
Spoke too quickly. Used SliTaz Control Box to set pw for newly created tux. Still cannot login to desktop as tux ...
thoughts?
Offline
This error normally came up for me after the installing SliTaz from older cooking versions or a corrupt iso.This is why I assumed that the user was already created. If the LiveCD doesn't have a tux user then it might be that the iso is corrupted. Check out the md5 hash of the iso with the command md5sum slitaz-3.0.iso and visually compare the numbers it generates with the one found in http://mirror.slitaz.org/iso/3.0/slitaz-3.0.md5 (open it in a text editor). If the two numbers do not match, then you have a corrupt copy of the iso.
I have noticed a trend though. If I download the iso with a download manager that splits up the iso into bits, then it tends to get corrupted. Which is why I download isos with Firefox's default download manager.
You also might want to read this guide: http://doc.slitaz.org/en:guides:uncommoninst
It explains the various (strange) ways to install SliTaz. Notably the part of mounting the iso in a loop to /dev/cdrom might be useful:
[c]mount -o loop,ro slitaz-3.iso /media/cdrom[/c]
Offline
Trixar_za
Thanks for the input, what I get back from your 4. is cp: can't preserve ownwership of '/home/tux/.....' operation not permitted. I get the same for the new user I created as well, although I ought to check back in the old forum because I can remember user set up problems anyway....
pobda
Offline
Trixar_za,
The iso file is not the problem.
Here's the net; if a frugal install is 'uncommoninst' or 'strange', so be it. Remastering SliTaz, however, should be a straight-forward process irrespective of whether the installation is 'uncommoninst' or 'strange'.
In v1, there was a manual, step by step process, to remaster the iso. Regrettably, my HDD went South and took my files/notes on that process. To have them back ...
Anyone know how to manually remaster SliTaz from RAM or has the old documentation?
Offline
After some effort and actually trying to create another user (tux in this example) I came up to the same error. I did however discover a method that works as highlighted below:
[c]brenton@trixarian:~$ su
Password:
root@trixarian:/home/brenton# adduser tux
Changing password for tux
New password:
Retype password:
Password for tux changed by root
root@trixarian:/home/brenton# cd /etc/skel
root@trixarian:/etc/skel# cp -af * /home/tux
root@trixarian:/etc/skel# cp -af . /home/tux
root@trixarian:/etc/skel# cd
root@trixarian:~# cp -af * /home/tux
root@trixarian:~# cp -af . /home/tux
root@trixarian:~# chmod -R 777 /home/tux
root@trixarian:~# chown -R tux:tux /home/tux[/c]
First I used su to set myself as root, then I used the adduser command to create the /home/tux directory and set the password. The trouble with this command is that it creates an EMPTY directory. I knew that I could login in with root, so I figured I need it's files to work with the optional extras provided by /etc/skel. So first I cd to /etc/skel and then copy the files within with TWO cp commands. One to move the visible files and directories and one to move the invisible ones. Hence the use of * (star) and . (full stop) in the above commands. Then I cd to the root user's directory - since I was root at the time all I had to type was cd. I yet again use the two cp commands to copy the visible and invisible files.
Ok, now we have /home/tux folder with working copy of the files it needs to login and boot properly. Now I have to set the permissions correctly. So first I chmod /home/tux recursively so that every file is set as 777 (I tried it another way and I got an error, so leave it as 777) and I changed the owner and group to tux:tux with chown recursively as well. So now all that's left is to logout and try it. Which I did and surprise, it works!
Offline
Trixar_za,
Thank you! Appreciate your stick-to-it-ness! Especially appreciate that you actually tried things out.
Will try your recommendations shortly. If you can attach your final .sh, would appreciate it. No worries, if not.
If successful, this will be a significant step forward.
Next steps; #1 compress the entire /tux so I keep all of my changes/stuff before shut down then, #2, put /tux back auto-magically on next boot, before the login screen.
Again, especially appreciate that you actually tried things out.
Offline
Trixar_za,
Background: grub4dos/boot into updated frugal SliTaz (see above), get to the Login screen with tux autofilled. When enter pw tux, get the dreaded "Cannot Login to Desktop". Can only login as root.
Interesting thing learned when starting on your recommendations. /tux is in use even though there is no /tux in RAM. The following is output of my work captured with the script command.
root@slitaz:~# adduser tux
adduser: login 'tux' is in use
root@slitaz:~# ls -al /home
drwxr-xr-x 2 root root 40 May 26 2010 [1;34m.[0m
drwxrwxrwt 16 root root 340 Apr 20 18:49 [1;34m..[0m
root@slitaz:~# exit
?thoughts?
Offline
Seems with yours the user account was created, but not the directory. Maybe try deluser tux before the adduser tux step.
Offline
Trixar_za,
Success! Lots of funky things happened along the way, but in the end, your fix worked.
Can we take it to the next step? compress /tux on exiting so as to retain my changes/stuff, then rebuild /tux on boot?
tikbalang; if you want a copy of my .sh scripts, happy to send via email
Thanks Trixar_za! Thanks!
Offline
All,
Passing on a few things learned in the course of this journey.
Apparently tux is hard coded into the SliTaz login screen; 'deluser tux', logout, login and there she blows ...
'adduser tux' continue to get error msg, bad pw too short, no matter the length of the pw entered ...
'adduser tux' creates a Linux user whereas original tux is a SliTaz user; have no idea if this makes any difference ...
?WHO CORRECTS faulty documentation; Reference: http://doc.slitaz.org/en:guides:faq-login?
would still prefer a step-by-step method to manually remaster an iso that captures the full RAM environment
Offline
The adduser tux error happens. If you write a password too similar to your other one, it calls the password insecure. Just continue entering the password again for it to set.
Offline
Trixar_za,
Hey, how are you?
For the last week, I tried your recommendations. They work perfectly. Many thanks.
However, I lose all docs, settings, bookmarks, EVERYTHING, when I exit the system. Additionally, there seems to be a problem with permissions as I cannot access my hdd.
I created a separate post asking if anyone had the old docs (step-by-step) on remastering, no responses, so I am stuck. Thoughts, or is this just a waste of time? Do you have any sense whether this problem will be corrected, or even addressed in v4?
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]