1

I want to check out Nitrux which you can deploy using znx (how to here).

znx does not seem to open correctly in Fedora, which is why I would like to deploy it using the terminal. The how-to says that I should install it on a partition that has at least 4 GB.

I have one big free partition on my computer which has about 200 GB. Do you know if the entire partition will be "blocked" by Nitrux, if I will deploy it on that partition? Or will znx assign it 4 GB of that partition and let me use the rest?

Thanks!

  • If you give a -1, please also give an answer – User12547645 Dec 9 '18 at 22:46
1

znx does not seem to open correctly in Fedora, which is why I would like to deploy it using the terminal. The how-to says that I should install it on a partition that has at least 4 GB.

It looks like you're confusing znx with znx-gui.

znx is a command-line AppImage program. znx-gui is a temporary and straightforward user interface that we made using KDialog for znx for users that don't want to touch the Terminal.

The commands in the Compendium are examples to guide users on how to use znx to deploy Nitrux, and just like the example shows, you are meant to deploy the ISO file to a target device, i.e. /dev/sdX and not to a partition i.e. /dev/sdXn where X is the device and n is the partition.

The 4GB that you mention is an example of the output of the command sudo fdisk -l it's not a recommendation, that's why it's in a different color too.

I have one big free partition on my computer which has about 200 GB. Do you know if the entire partition will be "blocked" by Nitrux, if I will deploy it on that partition? Or will znx assign it 4 GB of that partition and let me use the rest?

One of the features of znx is that you can deploy multiple operating systems at once without the need to create multiple partitions. With znx, you only need two partitions, one for the ESP and one for your data where it will keep it when you update the system and znx will create both of them automatically.

After znx creates its two partitions, the data partition will be of the size of the free space in the device that you initialized minus the ESP, for example, if it's a 10GB storage device znx will create a 131MB ESP and a 9.9GB data partition. Inside the data partition, you will find the home folders and the ISO files of the operating systems that you have deployed.


Back to your question, being an AppImage all that you need to do is download the file there's no installation involved, there's also no installation involved with Nitrux either.

If you downloaded znx first you have to make it executable, then you can execute the AppImage from the Terminal using sudo ./znx [command]

image1

  • If you download the AppImage and this message pops up, it's because it's not executable.

image

  • Once it's made executable, you can use sudo ./znx --help to display the help.

Now you need to type the commands for znx in the correct order like the help shows and like the Compendium shows.


I want to check out Nitrux which you can deploy using znx (how to here).

So, let's assume that you have two storage devices one would be /dev/sda, and the other would be /dev/sdb, and you want to deploy Nitrux to /dev/sdb.

First, you initialize the device. This will wipe the device.

  1. sudo ./znx init /dev/sdb

Second, to deploy Nitrux, you need the ISO image, so we download it and proceed accordingly, let's assume that the file is in your Home folder.

  1. Download ISO from openDesktop, Sourceforge, OSDN, Torrent.
  2. sudo ./znx deploy /dev/sdb nitrux/v1-1-1 nitrux_release_stable-v1-1-1.iso
  3. Wait for the write cache buffers to empty, use sync for this, note that this will depend on the speed of the target storage device.

And that's it. Reboot and select the second drive to boot into Nitrux.


We have explained what znx is and what it does in several articles at our Blog, the wiki and we recently added an FAQ (which summarizes the topics from the blog).

If you or anyone else wants to know how znx works or how Nitrux makes use of znx, I suggest creating more questions.

  • One of the features of znx is that you can deploy multiple operating systems at once without the need to create multiple partitions. - given that the installation procedure involves a command (sudo ./znx init /dev/sdx) that will wipe out the device sdx, how will the second OS be installed next to the first on the same device? can Nitrux be installed along a preexisting OS on the same device sdx? Am I expected to simply wipe out all my data in order to install Nitrux Linux? – cipricus Mar 13 at 18:31
  • With znx, you only need two partitions: in other Linux I need only one; and can I keep my old partition (60% of my drive, with no OS on it, meant to stay accessible from both Linux and Windows) that I don't want touched by newly installed OSes? – cipricus Mar 13 at 18:41
  • @cipricus There's plenty of information about znx, and how it works. Given that this is a Q&A website you could, instead, ask a question where we can provide you with a full-length answer. – Uri Herrera Mar 14 at 7:48
2

No, the entire partition will not be used by Nitrux:

The first thing you have to do in order to use znx is to initialize the device. znx will wipe the device and create a new GPT partition table on it, with two partitions. One of those partitions stores the bootloader data, while the other stores user data (including the images). Those partitions are then formatted with the FAT32 and the BTRFS filesystems respectively. After that, znx creates some directories on both partitions, as well as copying some files to the boot partition. Once those things are done, the device is considered initialized.

Furthermore...

Images are stored on the /boot_images directory of the data partition. Inside that directory, a hierarchy of subdirectories that match the name of the image are created. So, when you, for example, deploy your_distro/rolling, a directory /boot_images/your_distro/rolling is created in the data partition. Then, the image is stored in that directory.

The 4G recommendation by Nitrux is not for the partition but for the entire device; This is very important. znx essentially takes over an entire disk, as described in the first quotation above. Maybe you can get it to work with with your 200GB partition, but that's not how the znx documentation describes it.

You can read the nitty-gritty in the znx Wiki.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.