These 2 commands replace the old “tazlito iso2flavor” command (which can't be used any more). ![]() You can probably also reinclude these changes finally into your flavor file by means of the # tazlito extract-iso command, combined with the tazlito pack-flavor command. ![]() Voilà! Your first LiveCD ISO image is generated in /home/slitaz/distro!Īs mentioned above, you can add some last changes (that require modification from inside slitaz like changing appearance, modifying the taskbar, …) by simply making an additional rootfs file with a usb stick made with the iso of the slitaz version you just made (using the # tazusb writefs lzma command), and then adding it to the extracted iso (using the hacker account). It is then compressed and added to a CD ISO image with booting information. This is not unlike chroot-ing in to another system from a LiveCD. This is the distro tree and contains the whole of the LiveCD's operating system. Tazlito uses the distro-packages.list file to download each package and 'install' it into a pseudo-file-system. It must be run as root and be in the same directory as the list and the configuration file. All dependencies will be fulfilled automatically, just as with normal package installation. The gen-distro command generates an ISO image with all the packages on the list. When you are comfortable with the process, you can start to delete or add packages as required. The dependency information in each package will take effect so these will be automatically included, even if they are not specified in the package list.įor your first ISO, we advise you re-build the default LiveCD without modifying the list. My intention is to make a dualboot with Kali-Linux and SliTaz.When generating a distro, there are some essential base-system packages that must be included. Please no blame for kali-linux, I do tests and stuff on my own network or virtualised machines, and I like that many programming stuff that I use with python (gtk, pyside, scapy etc) is preinstalled there. And finally, how can I get my usb stick to be bootable with the iso? So, how can I fix all this? How did this loop0 stuff come up and some letters changed down in the alphabet. "unable to mount iso or to find a filesystem on it rootfs.gz" If I use the SliTaz program to create a bootable USB stick I get: Output of fdisk -l is Disk /dev/loop0: 2444 MB, 2444689408 bytesġ46 heads, 32 sectors/track, 1022 cylinders : /dev/sdc1 Filesystem NTFS Mountpoint: /media/disk-1 Size 30gb dev/sdc #at the beginning it was /dev/sdb I think, only sure that it was changed. GParted shows: /dev/sda1 Filesystem: ext2 #(this is SliTaz, everything is fine here, I think) dev/loop0 Mounted on: /media/cdrom read only dev/sdc1 30gb Mounted on: /media/disk-1 #(should be usb stick, but the mounted folder was different at the beginning) Umounted dev: /dev/loop0p1 Hidden HPSF/NTFS Boot yes #What is loop0p1? Now if I go into mountbox(SliTaz program for mounting), I get some weird things: But it never booted from the iso at startup. When it was an ext3 partition and I wanted to copy files on the drive I got "permission denied"(but worked with root user in the console). Then I played around a bit and deleted again the usb partition and then made it an ext3 partition, FAT32 partition on finaly back to NTFS.īut nothing worked. But now I can't make it bootable, when I use the "make bootable in a linux os" installation guide from kali-linux, which says, do dd if=kali.iso of=/dev/sdb bs=512k (at first, the partition was at sdb1), and I got "no such file, directory"but I already renamed the file to kali.iso. Now I wanted to boot into another Linux OS, so I downloaded the iso(kali-linux), then copied it to the drive. So I made a new NTFS partition (on the USB stick of course) with GParted. But then I found out that my USB stick didn't get discovered if I plug it in. Then I created a partition with SliTaz which I'm currently on. ![]() I deleted every partition on my system, even the partition on my USB stick.
0 Comments
Leave a Reply. |