9/21/2023 0 Comments Slitaz usb overdrive![]() ![]() ![]() What is the goal of your SliTaz installation on USB Flash? Portability? SliTaz in not designed for it. Will keep discussion open a day or two before "close/sink" Respects to all work on Slitaz but sorry cannot use. I not change X config but X will not start. See some error about Xorg but boot too fast to read. Now I copy another file? So I copy file and reboot again. Lexeii: I see U say "/home/boot/bzImage" but don't see that. Not yet trying GRUB because saving settings to USB should U all say.so why make problem worse trying something else? Run "tazpkg list" as "root" and as "tux" and see many "xorg" packages in list. ![]() Choose "xorg" but get screen say "Install Xorg" and only choice "quit". X not configured for "tux" so "Configure X" screen come up. Try to "startx" but get error about missing ".xsession" file. See error message "failed to execute login." Type "ctrl-alt-F1" to get CLI. 'tux" login work with blank pass but X not start. Change "home=" to UUID of "/home" part of USB. Mount bootable part of USB to edit "syslinux.cfg". ![]() Someone need to add to FAQ U need "bash" to run "shopt". Setup "/home/tux" as link prev mentioned say. Create directories in "/home" for 'boot" and "tux". Strange.Ĭreate second part on USB for "/home". First try on "tazusb" fail on "syslinux". Use "tazusb" to create bootable USB.had to repeat twice. Kernel (hd0,1)/boot/bzImage rw root=/dev/null home=/dev/sda2 vga=789 lang=ru_RU kmap=ru laptopĬhanged to Slitaz 3.0 ISO. This is lines of /home/menu.lst in my netbook (GRUB4DOS installed on ntfs partition): Kernel /boot/bzImage rw root=/dev/null vga=791 lang=ru_RU kmap=ru home=/dev/hda1 This is lines of /home/boot/grub/menu.lst in my old machine (ordinary GRUB installed): Rootfs.gz (from '/') -> rootfs.gz -> previous.gz -> rootfs.gz.1279365956 (this number is date-time) If file '/home/boot/bzImage' exists, then echo "Moving." and move files in /home/boot like this: Mv /home/boot/rootfs.gz /home/boot/previous.gz Mv /home/boot/previous.gz /home/boot/rootfs.gz.$(date +%s) # Move the old filesystem with the unix timestamp for reference # If the bootable medium is where it should be, copy acrossĮcho "Moving rootfs.gz to media. There is the lines (509-522) of /usr/bin/tazusb: Cooking is not alpha, it's not stable, some like beta :) Unfortunately, my weak & cost net connection don't let me experiment with cooking one. Slitaz look nice and have packages I like but cannot save setup make Slitaz useless to me. I spend many many hour on this and reading Slitaz web and forum but cannot make work. All previous settings do not show up but "/home" is mounted and 'rootfs.gz" is there.same file I save. So I "mv /rootfs.gz /home" and prove file exist in "/home" using "ls -al". Then I use "tazusb writefs gzip" to create "rootfs.gz" which is found in "/", not "/home" as some forum writing say even though I mount "/dev/sde2" as "/home" and "mount" say I do that. I make changes to environment, install new packages, remove other packages. Strange? What is "tux" password? When I make USB from "pendrivelinux" USB tool all boot "ok" and "tux" login work "ok". I boot from USB made from "tazusb gen-liveusb" command, all boot "ok" but autologin "tux" not work so I login as "root". I use "tazusb gen-liveusb" to create bootable Slitaz on USB. I'll relate results in a new post.I use "slitaz-cooking.iso 20100314" from download on Slitaz site. Now I am going to try a different route: I try to make a true installation of Slitaz on my usb. This could be related to the bug mentioned in I try to summarize the results of my experience:ġ) there is no difference in results using Unebootin and fat32 file system or TazUsb Installer and ext3 file system: in both cases writefs doesn't work and doesn't save current configuration to usb running writefs produce a rootfs.gz on root directory in ram and this file is not copied anyway to boot directory in usb: in order to do it, you have to manually copy file from / to /media/diskĢ) in order to save configuration automatically, you have to run writefs as root user, not as tux ordinary user: in this case rootfs.gz is created correctly in usb and also a backup copy is generated on the same drive ģ) the problem is that creating rootfs.gz apparently delete Tux user configuration: in fact, after creating it, it is impossible to login as tux (it is only possible to log in as root). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |