SliTaz Forum

Slitaz won't allow me to login as user tux

(7 posts) (2 voices)

• Started 12 years ago by namT
• Latest reply from namT
• This topic is resolved

Tags:

No tags yet.

1. 

   namT
   

   offline

   Member

   Hello, upon creating a frugal install to my hard-drive, user tux no longer works.
   I tried removing the /tux/.Xauthority file, but then when I log in as tux, all I get is an orange screen and nothing else.

   It logs in as root okay, so I can still use Slitaz (4.0 RC3).
   I am wondering does anyone know of a solution to the "tux" problem?
   If not, then how can I remove user tux and create a new username?

   Posted 12 years ago #
2. 

   mojo
   

   offline

   Key Master

   You must use home=UUID of a partition that is formated with ext3 filesystem.
   If you try to use fat32 or NTFS filesystem for persistent /home logins for regular users will fail.

   Posted 12 years ago #
3. 

   namT
   

   offline

   Member

   thanks for the reply mojo,

   My hard-drive is an ext3. I tried the uuid and it booted but, tux still won't work.
   It's getting late here so I am signing off. I will try a reinstall again tommorrow and report back.

   Posted 12 years ago #
4. 

   namT
   

   offline

   Member

   Okay, I did some fooling around with different configurations for grub4dos, and conclude that the problem for tux not working is that I am not setting up the menu.lst options properly.

   I altered my bios to give my hard-disk boot priority over my usb-drives to do some experimenting.
   Next I added the following code to my (sda1) grub4dos menu.lst file:

   title SilTaz 4.0 RC3 - on 1GB USB
   uuid bf51365a-086e-4401-aa5b-88d2762d5f23
   kernel /boot/bzImage rw root=/dev/null home=uuid bf51365a-086e-4401-aa5b-88d2762d5f23 lang=en kmap=en
   initrd /boot/rootfs.gz

   With that option, grub4dos booted slitaz on my USB but it would only allow me to login as root and not "tux"...the same problem with the frugal install on my hard-drive.

   Then I used the following option in the grub4dos menu.lst :

   title SilTaz 4.0 RC3 - on 1GB USB
   uuid bf51365a-086e-4401-aa5b-88d2762d5f23
   chainloader +1

   This just passes on the bootloading duties to extlinux and my was able to boot as root and tux, as it should.

   I assume I have set the wrong parameters for "home" in the first configuration, but haven't figured out the correct setting. Until then, I can take the easy way out by doing a usb-reinstall to my hard-drive and use the "chainloader +1" option.

   Posted 12 years ago #
5. 

   mojo
   

   offline

   Key Master

   Replace home=uuid with home=bf51365a-086e-4401-5b-88d2762d5f23

   Change this:

   title SilTaz 4.0 RC3 - on 1GB USB
   uuid bf51365a-086e-4401-aa5b-88d2762d5f23
   kernel /boot/bzImage rw root=/dev/null home=uuid bf51365a-086e-4401-5b-88d2762d5f23 lang=en kmap=en
   initrd /boot/rootfs.gz

   To this:

   title SilTaz 4.0 RC3 - on 1GB USB
   uuid bf51365a-086e-4401-aa5b-88d2762d5f23
   kernel /boot/bzImage rw root=/dev/null home=bf51365a-086e-4401-aa5b-88d2762d5f23 lang=en kmap=en
   initrd /boot/rootfs.gz

   Posted 12 years ago #
6. 

   namT
   

   offline

   Member

   mojo,

   Once again I thank, you. With your fix to the "home" settings, Slitaz4 booted in tux.
   Now I know how to do a true frugal install with Slitaz, meaning no need for a second bootloader. =)

   Posted 12 years ago #
7. 

   namT
   

   offline

   Member

   UPDATE:
   =====

   For anyone following this thread, I found that freezing occurs with the above Grub4dos menu entry AFTER you try and save your settings. To fix this issue, you need to remove the part that says "lang=en kmap=en".

   I have discovered that those settings only work if you don't save anything with "tazusb writefs gzip"

   Posted 12 years ago #

RSS feed for this topic

Reply

You must log in to post.