SliTaz Forum

dysmas

Member

Registered: 2013-01-12

Posts: 5

TazUSB bug in Fat32

This is not a support question but a bug report.

With Slitaz 4.0 when a live USB is built by tazUSB, the first option (Slitaz live) does not run, and when running the second option (Slitaz core) the autologin fails. The login dialog appears with tux as login, but I don't know which password I must use. The only option is to run with root / root but this is not a good idea.

Can developpers see what happens with syslinux, because the problem does not come from the formatting itself, but from the differences between syslinux and extlinux.

I really need to run Slitaz on a fat32 key to be able to write data on it from Windows (sorry).

Thanks if someone could check this issue I am not able to solve.

dysmas

Member

Registered: 2013-01-12

Posts: 5

Re: TazUSB bug in Fat32

P.S. As far as I know when running Slitaz core in root mode everything is normal. The anomalies you may encounter come from the root mode.

Trixar_za

Administrator

Registered: 2011-03-29

Posts: 1,506

Re: TazUSB bug in Fat32

http://www.ext2fsd.com/

christophe

Member

Registered: 2011-04-17

Posts: 432

Re: TazUSB bug in Fat32

/home/tux has to be on an ext2 or ext3 fs

you can however partition your key with a small ext3 FS and then mount the rest of the key, fat32, as eg /home/tux/document

I have used other ext driver for windows, i recommend you read carefully about them before using them, some have know bug or restrictions in functionnalities that i would consider a problem (eg not able to support accentued characters in file names)

While on the other hand i would consider accessing a fat fs from linux as very safe, since fat has been around for a long time

dysmas

Member

Registered: 2013-01-12

Posts: 5

Re: TazUSB bug in Fat32

Thanks for the answer Christophe. What is misleading is that the Tazusb official doc says :

TazUSB supports FAT32/EXT3/EXT2 formatted drives using SYSLINUX and EXTLINUX respectively.

Thank you Trixar, I tried the driver, I think it is good. I still would prefer a Fat32 USB key, but this is a valuable workaround.

Reading my post I notice that I didn't mention the bug is present only with a Fat32 formatted key. But this should have been clear from the title. Working with an etx3 formatted key, I still had troubles when using uncompressed rootfs.gz (sometimes login problem and sometimes lots of errors and the gui does not run). Presently with gzip compression my last update is OK.