penguins-eggs 9.6.23 → 9.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (128) hide show
  1. package/.oclif.manifest.json +1458 -1
  2. package/README.md +1527 -201
  3. package/addons/eggs/theme/livecd/grub.main.cfg +4 -4
  4. package/addons/eggs/theme/livecd/isolinux.main.cfg +5 -5
  5. package/bin/dev.js +6 -0
  6. package/bin/run +0 -0
  7. package/bin/run.js +7 -0
  8. package/conf/derivatives.yaml +23 -3
  9. package/conf/distros/README.md +25 -0
  10. package/conf/distros/bionic/calamares/calamares-modules/sources-yolk/module.yml +8 -0
  11. package/conf/distros/bionic/calamares/calamares-modules/sources-yolk/sources-yolk.sh +82 -0
  12. package/conf/distros/bionic/calamares/modules/packages.yml +6 -0
  13. package/conf/distros/{rolling/calamares-32 → bionic/calamares}/modules/removeuser.yml +2 -3
  14. package/conf/distros/bionic/calamares/modules/unpackfs.yml +6 -0
  15. package/conf/distros/buster/calamares/calamares-modules/bootloader-config/bootloader-config.sh +3 -3
  16. package/conf/distros/buster/calamares/calamares-modules/sources-yolk/sources-yolk.sh +1 -1
  17. package/conf/distros/buster/calamares/modules/bootloader.yml +2 -1
  18. package/conf/distros/buster/calamares/modules/fstab.yml +1 -1
  19. package/conf/distros/buster/calamares/modules/mount.yml +2 -2
  20. package/conf/distros/focal/calamares/modules/after_bootloader_context.yml +10 -1
  21. package/conf/distros/focal/calamares/modules/before_bootloader_mkdirs_context.yml +4 -4
  22. package/conf/distros/focal/calamares/modules/fstab.yml +1 -1
  23. package/conf/distros/focal/calamares/modules/mount.yml +2 -2
  24. package/conf/distros/focal/calamares/modules/shellprocess_bug-LP#1829805.yml +1 -1
  25. package/conf/distros/focal/calamares/modules/shellprocess_logs.yml +1 -1
  26. package/conf/distros/stretch/krill/krill-modules/bootloader-config/bootloader-config.sh +28 -0
  27. package/conf/distros/stretch/krill/krill-modules/bootloader-config/module.yml +8 -0
  28. package/conf/distros/stretch/krill/krill-modules/remove-link/module.yml +9 -0
  29. package/conf/distros/stretch/krill/krill-modules/remove-link/remove-link.sh +5 -0
  30. package/conf/distros/stretch/krill/krill-modules/sources-yolk/module.yml +8 -0
  31. package/conf/distros/stretch/krill/krill-modules/sources-yolk/sources-yolk.sh +75 -0
  32. package/conf/distros/stretch/krill/krill-modules/sources-yolk-unmount/module.yml +8 -0
  33. package/conf/distros/stretch/krill/modules/partitions.yml +8 -0
  34. package/conf/distros/stretch/krill/modules/removeuser.yml +15 -0
  35. package/conf/distros/{rolling/calamares-32 → stretch/krill}/settings.yml +50 -11
  36. package/conf/eggs.yaml +2 -9
  37. package/conf/{exclude.list.homes → exclude.list.d/home.list} +6 -1
  38. package/conf/{exclude.list.template → exclude.list.d/master.list} +16 -26
  39. package/conf/{exclude.list.usr → exclude.list.d/usr.list} +2 -2
  40. package/conf/exclude.list.d/var.list +21 -0
  41. package/conf/tools.yaml +1 -3
  42. package/dist/classes/compressors.js +11 -13
  43. package/dist/classes/daddy.js +1 -3
  44. package/dist/classes/distro.js +23 -4
  45. package/dist/classes/families/archlinux.js +7 -9
  46. package/dist/classes/families/debian.js +1 -1
  47. package/dist/classes/families/fedora.js +1 -1
  48. package/dist/classes/families/suse.js +1 -1
  49. package/dist/classes/incubation/branding.js +9 -3
  50. package/dist/classes/incubation/distros/bionic.js +8 -3
  51. package/dist/classes/incubation/distros/buster.js +8 -3
  52. package/dist/classes/incubation/distros/focal.js +8 -3
  53. package/dist/classes/incubation/distros/jessie.js +6 -3
  54. package/dist/classes/incubation/distros/rolling.js +8 -4
  55. package/dist/classes/incubation/fisherman-helper/packages.js +5 -2
  56. package/dist/classes/incubation/fisherman.js +18 -3
  57. package/dist/classes/incubation/incubator.js +7 -2
  58. package/dist/classes/incubation/installer.js +3 -1
  59. package/dist/classes/initrd.js +5 -5
  60. package/dist/classes/keyboards.js +4 -4
  61. package/dist/classes/network.js +7 -7
  62. package/dist/classes/ovary.js +136 -176
  63. package/dist/classes/pacman.js +12 -14
  64. package/dist/classes/pve-live.js +1 -1
  65. package/dist/classes/pxe.js +10 -12
  66. package/dist/classes/settings.js +19 -18
  67. package/dist/classes/systemctl.js +1 -1
  68. package/dist/classes/tailor.js +6 -6
  69. package/dist/classes/tools.js +4 -6
  70. package/dist/classes/users.js +10 -0
  71. package/dist/classes/utils.js +30 -0
  72. package/dist/classes/xdg.js +21 -8
  73. package/dist/classes/yolk.js +3 -5
  74. package/dist/commands/adapt.js +8 -8
  75. package/dist/commands/analyze.js +9 -12
  76. package/dist/commands/calamares.js +20 -23
  77. package/dist/commands/config.js +13 -13
  78. package/dist/commands/cuckoo.js +7 -7
  79. package/dist/commands/dad.js +12 -12
  80. package/dist/commands/export/deb.js +20 -25
  81. package/dist/commands/export/iso.js +11 -11
  82. package/dist/commands/install.js +41 -37
  83. package/dist/commands/kill.js +12 -15
  84. package/dist/commands/mom.js +7 -7
  85. package/dist/commands/produce.js +71 -47
  86. package/dist/commands/status.js +8 -8
  87. package/dist/commands/syncfrom.js +34 -40
  88. package/dist/commands/syncto.js +142 -202
  89. package/dist/commands/tools/clean.js +9 -9
  90. package/dist/commands/tools/ppa.js +12 -12
  91. package/dist/commands/tools/skel.js +10 -10
  92. package/dist/commands/tools/stat.js +11 -11
  93. package/dist/commands/tools/yolk.js +9 -9
  94. package/dist/commands/update.js +8 -8
  95. package/dist/commands/wardrobe/get.js +13 -10
  96. package/dist/commands/wardrobe/list.js +15 -13
  97. package/dist/commands/wardrobe/show.js +16 -13
  98. package/dist/commands/wardrobe/wear.js +16 -14
  99. package/dist/components/summary.js +5 -2
  100. package/dist/interfaces/i-analyze.js +8 -10
  101. package/dist/interfaces/{i-filters.js → i-excludes.js} +0 -1
  102. package/dist/krill/krill-prepare.js +23 -11
  103. package/dist/krill/krill-sequence.js +72 -73
  104. package/dist/krill/modules/fstab.js +59 -32
  105. package/dist/krill/modules/mkfs.js +29 -16
  106. package/dist/krill/modules/network-cfg.js +22 -21
  107. package/dist/krill/modules/partition.js +3 -3
  108. package/dist/lib/dependencies.js +1 -0
  109. package/dist/lib/select_filesystem_type.js +6 -1
  110. package/manpages/doc/man/eggs.1.gz +0 -0
  111. package/manpages/doc/man/eggs.html +128 -74
  112. package/mkinitcpio/biglinux/live.conf +74 -0
  113. package/mkinitcpio/biglinux/mkinitcpio.conf +73 -0
  114. package/package.json +43 -41
  115. package/scripts/_eggs +17 -14
  116. package/scripts/eggs.bash +6 -6
  117. package/conf/distros/rolling/calamares-32/modules/displaymanager.yml +0 -23
  118. package/conf/distros/rolling/calamares-32/modules/finished.yml +0 -6
  119. package/conf/distros/rolling/calamares-32/modules/fstab.yml +0 -14
  120. package/conf/distros/rolling/calamares-32/modules/locale.yml +0 -11
  121. package/conf/distros/rolling/calamares-32/modules/mount.yml +0 -39
  122. package/conf/distros/rolling/calamares-32/modules/packages.yml +0 -11
  123. package/conf/distros/rolling/calamares-32/modules/partition.yml +0 -283
  124. package/conf/distros/rolling/calamares-32/modules/shellprocess_removelink.yml +0 -8
  125. package/conf/distros/rolling/calamares-32/modules/unpackfs.yml +0 -7
  126. package/conf/distros/rolling/calamares-32/modules/users.yml +0 -20
  127. package/conf/exclude.list.custom +0 -3
  128. package/manpages/doc/man/README.md +0 -0
package/README.md CHANGED
@@ -15,193 +15,380 @@ penguins-eggs
15
15
  # Index
16
16
  <!-- toc -->
17
17
  * [Index](#index)
18
- * [Presentation](#presentation)
18
+ * [Introduction](#introduction)
19
19
  * [Technology](#technology)
20
20
  * [Features](#features)
21
21
  * [Packages](#packages)
22
22
  * [Usage](#usage)
23
23
  * [Commands](#commands)
24
- * [Penguins' eggs official guide](https://penguins-eggs.net/docs/Tutorial/eggs-users-guide)
25
- * [That's all Folks!](#thats-all-folks)
24
+ * [Penguins' eggs official guide](#penguins-eggs-official-guide)
25
+ * [Copyright and licenses](#copyright-and-licenses)
26
26
  <!-- tocstop -->
27
27
 
28
- # Presentation
29
- **penguins-eggs** is a console tool, under continuous development, that allows you to remaster your system and redistribute it as live images on usb sticks or via PXE.
30
28
 
31
- The default behavior is total removal of the system's data and users, but it is also possible to remaster the system including the data and accounts of present users, using flag **--clone**. It is also possible to keep the users and files present under an encrypted LUKS file within the same resulting iso file, flag **--cryptedclone**.
29
+ # Introduction
30
+ penguins-eggs is a console tool, under continuous development, that allows you to remaster your system and redistribute it as live images on USB sticks or via PXE. The concept behind Penguins’ Eggs stems from the idea of “reproduction” and “population selection” applied to operating systems. During the era of popular remastering programs like Remastersys and Systemback, both of which experienced maintenance issues and were eventually abandoned, the need for a new, modern tool became evident. The inspiration for Penguins’ Eggs led to the development of a new tool written in a modern, cross-distribution language, utilizing its own packaging system. Initially built with node.js and later transitioning to Typescript as the primary development language, the tool’s design resembles an egg production process, consisting of operations such as “produce” for creating the eggs, “hatch” for installation, and other commands like “kill” for removing produced ISOs, “update” for software updates, and “install” for configuring the graphical installer. It also has prerequisites to install the .deb packages necessary for the process, namely, calamares.
32
31
 
33
- You can easily install the resulting live system with the calamares installer or the internal TUI krill installer.
32
+ > Considered a work-in-progress, the ultimate goal for Penguins’ Eggs is to implement a PXE server for local network distribution, drawing inspiration from the behavior of the cuckoo bird, which relies on others to hatch its eggs. Written primarily in TypeScript, Penguins’ Eggs is designed to be compatible with various Linux distributions, despite differences in package managers, file paths, and more. The tool currently supports Debian, Devuan, Ubuntu, Arch, Manjaro, and their derivatives, across multiple architectures including amd64, i386, and arm64. With the release of version 9.6.x, Penguins’ Eggs is now available as a Debian package, catering to a wide range of systems including PCs, older machines, and single-board ARM systems like the Raspberry Pi, across amd64, i386, and arm64 architectures. For more information and updates, visit the Penguins’ Eggs official website.
34
33
 
35
- It is possible to have also unattended installation using **--unattended** flag.
36
34
 
37
- Thanks to the wardrobe, you can create or use scripts to switch from a **naked** version - with only a CLI interface - and `wear` it with a full GUI or server configurations.
35
+ > [!TIP]
36
+ > "Penguins-eggs" is an actively developed console tool designed to help you customize and distribute your system as live images on USB sticks or through PXE. By using this tool, you can remaster your system according to your preferences.
38
37
 
39
- See [penguins-wardrobe](https://github.com/pieroproietti/penguins-wardrobe), fork it and adapt to yours needs.
38
+ > [!TIP]
39
+ > By default, "penguins-eggs" completely removes the system's data and users. However, it also offers the option to remaster the system while including the data and accounts of existing users. This can be done using the "--clone" flag. Additionally, you can preserve the users and files by storing them in an encrypted LUKS file within the resulting ISO file, which can be achieved with the "--cryptedclone" flag.
40
40
 
41
- # Technology
41
+ > [!TIP]
42
+ > The resulting live system can be easily installed using either the Calamares installer or the internal TUI Krill installer. Furthermore, if you prefer an unattended installation, you can utilize the "--unattended" flag.
43
+
44
+ > [!TIP]
45
+ > One interesting feature of "penguins-eggs" is its integration with the "penguins-wardrobe." This allows you to create or utilize scripts to switch between different configurations. For example, you can start with a bare version of the system, featuring only a command-line interface (CLI), and then easily transition to a full graphical user interface (GUI) or server configurations.
46
+
47
+ > [!NOTE]
48
+ > For more information and customization options, you can explore "penguins-wardrobe," a related project. You can fork it and adapt it to meet your specific needs.
49
+
50
+ See [penguins-wardrobe](https://github.com/pieroproietti/penguins-wardrobe), fork it, and adapt it to your needs.
42
51
 
43
- eggs is written mostly in typescript and ideally can be used with different Linux distributions. Yes, there are big differences in terms of package manager used, path, etc, but basically the various programs used to build the live are the same.
52
+ # Technology
53
+ "eggs" is primarily written in TypeScript and is designed to be compatible with various Linux distributions. While there may be differences in package managers, paths, and other aspects, the underlying programs used to build the live system are generally the same.
54
+ Currently, "eggs" supports several Linux distributions, including [Debian](https://www.debian.org/), [Devuan](https://www.devuan.org/), [Ubuntu](https://ubuntu.com/), [Arch](https://archlinux.org/), [Manjaro](https://manjaro.org/) and [derivatives](./conf/derivatives.yaml); and their derivatives. It also caters to different architectures, namely amd64, i386, and arm64.
55
+ Starting from version 9.6.x, "Penguins' eggs" is released as a Debian package, available for amd64, i386, and arm64 architectures. This allows it to support a wide range of PCs, including older machines, as well as single-board ARM systems like the Raspberry Pi. You can learn more about this release in the article titled Triple Somersault! [Triple somersault!](https://penguins-eggs.net/blog/triple-somersault).
56
+ For more information on the supported distributions and architectures, you can visit the blog [blog](https://penguins-eggs.net/blog/distros-that-can-be-remastered-with-eggs). Additionally, you can find examples of remastered ISO images created with "eggs" on the project's SourceForge page [sourceforge page of the project](https://sourceforge.net/projects/penguins-eggs/files/ISOS/).
44
57
 
45
- Currently eggs supports: [Debian](https://www.debian.org/), [Devuan](https://www.devuan.org/), [Ubuntu](https://ubuntu.com/), [Arch](https://archlinux.org/), [Manjaro](https://manjaro.org/) and [derivatives](./conf/derivatives.yaml); regarding architectures eggs currently support amd64, i386 and arm64.
46
58
 
47
- Since version `9.6.x` Penguins' eggs is released - as Debian package - for: `amd64`, `i386` and `arm64` architectures, supporting the majority of PCs, old ones and single board ARM systems like Raspberry Pi. Read more on the article [Triple somersault!](https://penguins-eggs.net/blog/triple-somersault).
59
+ **penGUI take cure of eggs!**
48
60
 
49
- You can get more informations on the [blog](https://penguins-eggs.net/blog/distros-that-can-be-remastered-with-eggs), some examples of iso images remastered with eggs are in the [sourceforge page of the project](https://sourceforge.net/projects/penguins-eggs/files/ISOS/).
61
+ ![icon](https://github.com/pieroproietti/pengui/blob/main/assets/pengui.png?raw=true)
50
62
 
63
+ The development of a GUI for "penguins-eggs" with the penGUI project sounds promising. It's exciting to see that work on the GUI has started and is progressing rapidly. GUIs can greatly enhance the user experience and make it more accessible to a wider range of users. I hope the penGUI [penGUI](https://github.com/pieroproietti/pengui) project continues to thrive and brings a user-friendly interface to "penguins-eggs". If you have any specific questions or need further information about the penGUI project, feel free to ask!
51
64
 
52
65
  # Features
66
+ Penguins-eggs is a versatile tool that offers an array of features and benefits for Linux users. Whether you want to create an installable ISO from your current Linux system or explore various customization options, Penguins-eggs has got you covered. To get started with Penguins-eggs, you'll need to install it on your Linux distribution. The tool supports a wide range of Linux distributions and their major derivatives, including Arch, Debian, Devuan, Manjaro, Ubuntu, and more. Additionally, you can easily add support for additional derivatives, expanding the tool's capabilities even further.
67
+
68
+ 1. fast and efficient
69
+ Penguins-eggs is designed to be fast and efficient. Unlike traditional methods that involve copying the entire file system, Penguins-eggs utilizes livefs, which allows for instant acquisition of the live system. By default, the tool.
70
+
71
+ 2. Supports Compression Algorithm
72
+ Employs the zstd compression algorithm, significantly reducing the time required for the process, often up to 10 times faster. When creating an installable ISO.
73
+
74
+ 3. Supports Clone
75
+ Penguins-eggs provides various options to suit your needs. With the --clone flag, you can preserve the data and accounts of unencrypted users, ensuring a seamless experience for users accessing the live system. Moreover, you can opt for a crypted clone, where user data and accounts are saved in an encrypted LUKS volume within the ISO image, enhancing security and privacy.
53
76
 
54
- ## wardrobe, themes and addons
77
+ 4. Cuckoo and PXE boot
78
+ In addition to ISO creation, Penguins-eggs offers a unique feature called Cuckoo. By starting Cuckoo from the live system, you can set up a PXE boot server, making it accessible to all computers on the network. This functionality opens up possibilities for network booting and streamlined deployment. Penguins Eggs Linux ushers in a new era of innovation and convenience with its groundbreaking default feature, Cuckoo live network boot, which transforms any computer running Penguins Eggs into a PXE (Preboot eXecution Environment) boot server. This revolutionary paradigm of network booting and seamless deployment underscores Penguins Eggs Linux’s commitment to redefining the parameters of accessibility and efficiency within the realm of Linux distributions.
55
79
 
56
- wardrobe was added to eggs on april 2022. It is a way to guide and consolidate the process of creating a custom version of Linux, starting from a CLI system. All my personal editions are passed to use wardrobe for their convenience, in that way I can organize, consolidate and manage better my work. I used birds names for my customizations, except for naked, we have: colibri, eagle, duck, owl and chicks under [bookworm](https://sourceforge.net/projects/penguins-eggs/files/ISOS/debian/bookworm/) and [plastilinux](https://sourceforge.net/projects/penguins-eggs/files/ISOS/plastilinux/), wagtail, warbier under [waydroid](https://sourceforge.net/projects/penguins-eggs/files/ISOS/waydroid/) on eggs' sourceforge page.
80
+ 5. Supports Both TUI/GUI Installer
81
+ To simplify the installation process, Penguins-eggs provides its own system installer called krill. This installer is particularly useful when a GUI (Graphical User Interface) is not available, allowing for installation in various situations. However, if you are using a desktop system, Penguins-eggs recommends and configures the calamares GUI installer, ensuring a seamless and user-friendly experience.
82
+ Penguins Eggs Linux spearheads a transformative revolution in the realm of system installation with the incorporation of its TUI (Text-based User Interface) / GUI (Graphical User Interface) installer, setting a new standard of versatility and accessibility within the landscape of Linux distributions.
57
83
 
58
- I hope peoples will be interested in wardrobe and you will end to fork the main repository and add your customizations: together will be possibile to make great steps impossible for a single developer. You can read more in wardrobe on [Penguins' eggs blog](https://penguins-eggs.net/blog/wardrobe-colibri-duck-eagle-and-owl/).
84
+ 6. repository lists
85
+ One of the key advantages of Penguins-eggs is its commitment to utilizing only the original distro's packages. This means that no modifications are made to your repository lists, ensuring a safe and reliable environment. Penguins-eggs prioritizes maintaining the integrity and authenticity of your Linux distribution.
59
86
 
60
- Addons, mostly themes have been grouped under `vendors` folder in the penguins-wardrobe, try to use wardrobe for all your customizations.
87
+ 7. Wardrobe
88
+ To enhance customization options, Penguins-eggs introduces the concept of Wardrobe. With Wardrobe and its various components, such as costumes, you can easily organize and manage your customizations, samples, and more. This feature enables a streamlined and efficient workflow, allowing you to tailor your Linux system to your preferences.
61
89
 
62
- Consult [wardrobe users' guide](https://penguins-eggs.net/docs/Tutorial/wardrobe-users-guide).
90
+ 8. supporting multiple distributions
91
+ Eggs supporting multiple distributions and their derivatives
92
+ Supports: Arch, Debian, Devuan, Manjaro, Ubuntu,
93
+ and major derivatives: Linuxmint, KDE neon, EndeavourOS, Garuda, etc. You can easily add more derivatives.
63
94
 
64
- ## clone/cryptedclone
65
- You can create your live to distribute it - the default mode - or with datas using clone and clonecrypted:
95
+ 10. supports hardware architectures
96
+ supports a wide range of hardware architectures.
97
+ Supports: i386, amd64 and arm64 architecture, from old PCs, and common PCs to single board computers like Raspberry Pi 4/5
66
98
 
67
- ```eggs produce```
99
+ 11. Supports privacy and security
100
+ Safe: only use the original distro's packages, without any modification in your repository lists. Penguins Eggs Linux embarks on a steadfast commitment to user security and system integrity through its default practice of exclusively utilizing original distributions’ packages without any modifications in the repository lists. This resolute dedication to maintaining the pristine authenticity of packages reinforces Penguins Eggs’ fundamental ethos of safety and reliability, fostering an environment characterized by unwavering trust in the integrity of the software ecosystem.
68
101
 
69
- Completely removes user data from live, this is the preset mode
102
+ ## more features
103
+ [More feautures](https://github.com/pieroproietti/penguins-eggs/tree/master/changelog.d).
70
104
 
71
- ```eggs produce --clone```
72
105
 
73
- Saves our users and our data directly in the generated iso. The data will be visible directly from the live and accessible to anyone who gets a copy.
106
+ ## Wardrobe, Themes, and Addons
107
+ In April 2022, the "wardrobe" feature was introduced to "eggs." This addition serves as a comprehensive tool to assist and streamline the process of creating a customized version of Linux, starting from a command-line interface (CLI) system. I have embraced wardrobe for all my editions to enhance convenience, enabling me to better organize, consolidate, and manage my work effectively.
108
+ To add a unique touch to my customizations, I have assigned bird names to each edition. Except for the "naked" edition, there are various options available, including "Colibri," "eagle," "duck," "owl," and "chicks" under the bookworm and plastilinux distributions. [bookworm](https://sourceforge.net/projects/penguins-eggs/files/ISOS/debian/bookworm/) and [plastilinux](https://sourceforge.net/projects/penguins-eggs/files/ISOS/plastilinux/),.Furthermore, under Waydroid on the eggs' SourceForge page, you can find "wagtail" and "warbier."
109
+ I have high hopes that people will take an interest in wardrobe and consider forking the main repository to incorporate their own customizations. By collaborating, we can achieve significant progress that would be challenging for a single developer to accomplish. If you would like to delve deeper into the wardrobe, I recommend reading the Penguins' eggs blog [Penguins' eggs blog](https://penguins-eggs.net/blog/wardrobe-colibri-duck-eagle-and-owl/). post titled Wardrobe: Colibri, Duck, Eagle, and Owl, which provides further insights into its features and benefits.
110
+ Furthermore, addons, predominantly themes, have been organized under the vendor's folder in the penguin's wardrobe. I encourage utilizing your wardrobe for all your customization needs to maintain consistency and organization throughout your work.
74
111
 
75
- ```eggs produce --cryptedclone```
112
+ > [!NOTE]
113
+ > For detailed instructions on using a wardrobe, please consult the wardrobe users' guide [wardrobe users' guide](https://penguins-eggs.net/docs/Tutorial/wardrobe-users-guide).
76
114
 
77
- Saves our data within the generated iso using a LUKS volume. Our data will NOT be visible in the live system but can be reinstalled automatically with krill installer. Even having the generated image available, our data will be protected by the LUKS passphrase.
78
115
 
79
- * ```eggs produce``` this is the default: all private data are removed on the live.
80
- * ```eggs produce --clone``` include all users data UNCRYPTED directly on the live.
81
- * ```eggs produce --cryptedclone``` include all users data CRYPTED on a LUKS volume inside the iso.
116
+ ## Clone/Cryptedclone
117
+ When creating a live distribution of your system, you have different options to consider: the default mode, clone, and cryptedclone.
118
+ • The default mode, achieved by using the command "eggs produce," completely removes user data from the live distribution. This ensures that no private data remains in the live system.
119
+
120
+ • The "eggs produce --clone" command allows you to save both user data and system data directly in the generated ISO. This means that if someone obtains a copy of the ISO, they will be able to see and access the
121
+ user data directly from the live system. It's important to note that this data is not encrypted, so it may not be suitable for sensitive information.
122
+
123
+ • On the other hand, the "eggs produce --cryptedclone" command saves the data within the generated ISO using a LUKS (Linux Unified Key Setup) volume. With this option, the user data will not be visible in the live system. However, it can be automatically reinstalled during the system installation process using the "krill" installer. Even if someone has the generated ISO, they won't be able to access the user data without the LUKS passphrase. This ensures that your data remains protected.
124
+
125
+ To summarize the available options:
126
+
127
+ • "eggs produce" (default): All private data is removed from the live system.
128
+
129
+ • "eggs produce --clone": All user data is included unencrypted directly in the live system.
130
+
131
+ • "eggs produce --cryptedclone": All user data is included encrypted within a LUKS volume inside the ISO.
132
+ > [!TIP]
133
+ > During the installation process, you can use the "krill" installer to restore your crypted data automatically. By running the command "sudo eggs install" with the "krill" installer, your encrypted data will be securely transferred and made available in the installed system.
82
134
 
83
- Using krill: ```sudo eggs install``` will automaticaly restore your CRYPTED data during the installation.
84
135
 
85
136
  ## calamares and krill
86
- eggs was developed to use [calamares](https://calamares.io) as the system installer and allows its customization with themes. It also includes its own installer, called krill, which allows you to produce and install CLI systems such as servers. krill uses a CLI interface that mimics calamares and uses the same configuration files created by eggs for calamares. This provides a "roughly similar" installation experience for both desktop and server installations. With krill it is also possible to have unattended installations, simply by adding the ``--unattended`` flag, the configuration values can be changed in ``/etc/penguins-eggs.d/krill.yaml`` and will then be used for automatic installation.
137
+ Calamares and Krill are powerful tools in the Eggs project [calamares](https://calamares.io), offering versatile installation options for Linux systems. The Eggs project was specifically designed to utilize Calamares as the default system installer, providing users with the flexibility to customize their installations using themes. However, Eggs goes beyond Calamares by introducing its own installer called Krill, which focuses on command-line interface (CLI) installations, particularly for server environments.
87
138
 
88
- ## cuckoo
89
- The cuckoo lays its eggs in the nests of other birds, and the eggs are hatched by the latter. Similarly eggs can start a self-configuring PXE service to allow you to boot and install your iso on third party networked computers. Command cuckoo can be used either to deploy a newly created iso on an installed system or by live booting the iso itself.
139
+ Krill, like Calamares, adopts a CLI interface that closely resembles Calamares, ensuring a consistent user experience. Leveraging the same configuration files created by Eggs for Calamares, Krill maintains compatibility and allows for seamless transitions between desktop and server installations. By simply adding the flag during installation, Krill enables unattended installations, streamlining the process for system administrators. Fine-tuning installation parameters becomes effortless as the configuration values can be modified in the ```/etc/penguins-eggs.d/krill.yaml``` file, facilitating automated deployments.
140
+
141
+ > [!TIP]
142
+ > Thanks to the Eggs project's integration of Calamares and the introduction of Krill, users can enjoy a comprehensive installation toolkit. Whether one prefers the graphical interface of Calamares or the command-line efficiency of Krill, Eggs caters to diverse installation needs, making Linux setup a breeze.
143
+
144
+ ## cuckoo
145
+ ust like the cuckoo bird lays its eggs in the nests of other birds, the Eggs project introduces a similar concept in the form of a self-configuring PXE service. This service allows you to boot and install your ISO on networked computers that are not originally configured for your specific ISO.
146
+ With the command "cuckoo," you can deploy a newly created ISO on an already installed system, or you can live to boot the ISO itself. This means that you can either install your ISO on existing systems or directly run the ISO without the need for a permanent installation.
147
+
148
+ > [!TIP]
149
+ > By leveraging the cuckoo command, the Eggs project provides a convenient method for deploying and testing your ISO on a variety of networked computers, expanding the possibilities for system installations and evaluations.
90
150
 
91
151
  ## mom and dad
92
- I added two built-in assistants with eggs: mom and dad. While mom is a script based on [easybashgui](https://github.com/BashGui/easybashgui) that explains the various commands and documentation, dad started as a shortcut to properly configure eggs: just type ```sudo eggs dad``` and follow simple instructions. Even faster, using ```sudo eggs dad -d``` you will resets the configuration, loads defaults, deletes created isos. At this point, with eggs configured, just type ```sudo produce``` to generate your live.
152
+ I have introduced two helpful built-in assistants: Mom and Dad. Mom, based on the easybashgui [easybashgui](https://github.com/BashGui/easybashgui) script, serves as a comprehensive guide, providing explanations of various commands and documentation. This ensures that users have access to clear instructions and information as they navigate through Eggs' functionalities.
153
+ On the other hand, Dad serves as a convenient shortcut for properly configuring Eggs. By simply typing ```sudo eggs dad``` and following the straightforward instructions, users can quickly configure Eggs to meet their specific requirements. For even faster configuration, utilizing the command ```sudo eggs dad -d``` allows for a complete reset of the configuration, loading default settings, and deleting any created ISOs.
154
+ Once Eggs is properly configured, generating your live environment becomes a breeze. Just type ```sudo produce``` to effortlessly generate your live ISO. With this streamlined workflow, Eggs empowers users to efficiently create customized live environments tailored to their needs. Whether you rely on Mom's guidance or Dad's configuration shortcuts, Eggs offers a user-friendly experience for ISO creation and customization.
93
155
 
94
156
  ## yolk
95
- yolk - so called staying on the subject of eggs - is a local repository included in the livecd that contains a minimum of indispensable packages during installation. Thanks to yolk, you can safely install your system without the need of an active internet connection.
157
+ Yolk is a local repository that is bundled within the LiveCD of Eggs. This repository contains a carefully curated selection of essential packages required for installation. Yolk serves as a valuable resource, as it allows you to install your system confidently, even without an active internet connection.
158
+ By including Yolk in the LiveCD, Eggs ensures that all the necessary packages are readily available during the installation process. This eliminates the dependency on an internet connection, making it possible to install your system in offline environments or situations where internet access is limited or unavailable.
159
+ Yolk acts as a safety net, providing the minimum set of indispensable packages required for a successful installation. This guarantees a smooth and reliable installation experience, regardless of the availability of an internet connection. With Yolk by your side, you can confidently proceed with system installations, knowing that the essential packages are at your disposal.
96
160
 
97
161
  # Packages
98
- Supporting various distributions, we need to have different packages. Debian, Devuan and Ubuntu share the .deb packages for amd_64 and i386 architecture, while Arch and ManjaroLinux use their own PKGBUILDs.
162
+ Eggs offers support for a variety of packages. Specifically, for Debian, Devuan, and Ubuntu, Eggs utilizes .deb packages that are compatible with both amd_64 and i386 architectures. This ensures seamless integration with these distributions, allowing users to easily install and utilize Eggs' features.
163
+ On the other hand, Arch and ManjaroLinux have their own packaging system known as PKGBUILDs. Eggs is designed to work harmoniously with these distributions, leveraging the specific packaging structure provided by PKGBUILDs. This ensures that Eggs can seamlessly integrate into Arch and ManjaroLinux environments, providing users with a consistent and optimized experience.
164
+ By adapting to the packaging systems used by different distributions, Eggs ensures compatibility and ease of use across a wide range of Linux environments. Whether you're using Debian, Devuan, Ubuntu, Arch, or ManjaroLinux, Eggs is equipped to support your preferred distribution, enabling you to make the most of its features and functionalities.
165
+
99
166
 
100
167
  ## Debian families
101
- eggs is released as a deb package for amd64, i386 and arm64 too.
168
+ Eggs caters to the Debian family of distributions, offering a seamless installation experience through deb packages. These deb packages are available for multiple architectures, including amd64, i386, and arm64.The availability of Eggs as a deb package simplifies the installation process for users of Debian-based distributions. Whether you are running a 64-bit (amd64) or 32-bit (i386) architecture, or even an arm64 architecture, Eggs has you covered. This ensures that users across a wide range of Debian-based systems can easily download, install, and utilize Eggs' features.
169
+ By providing deb packages for various architectures, Eggs promotes accessibility and inclusivity, allowing users on different hardware platforms to benefit from its functionality. Whether you're using a traditional desktop computer or an ARM-based device, Eggs ensures compatibility and a consistent experience across the Debian family of distributions.
102
170
 
103
- Because of eggs' features, the packages can be installed in Debian, Devuan, or Ubuntu-based distros without worrying about exact version (buster, bullseye, bookworm, trixie, chimaera, daedalus, bionic, focal and jammy) are reported to work, of course respect the processor architecture.
171
+ The packages can be installed on Debian, Devuan, or Ubuntu-based distributions without the need to worry about the specific version. Whether you're using Buster, Bullseye, Bookworm, Trixie, Chimaera, Daedalus, Bionic, Focal, or Jammy, Eggs is reported to work across these versions. However, it's important to ensure compatibility with the respective processor architecture.
172
+ The packages provided by Eggs include standard scripts for preinst, postinst, prerm, and postrm. These scripts play a crucial role in the installation and management of the packages. The preinst script is executed before the package is installed, allowing for any necessary preparations or configurations. The postinst script is executed after the package installation, enabling additional setup or customization. Similarly, the prerm script is executed before the package is removed, while the postrm script is executed after the package removal.
173
+ In addition to the scripts, Eggs packages also include man pages. These man pages serve as documentation for the installed packages, providing detailed information on their usage, configuration options, and other relevant details. The inclusion of man pages ensures that users have access to comprehensive documentation, enabling them to effectively utilize and manage the Eggs packages.
174
+ Overall, Eggs' packages offer a comprehensive and user-friendly experience, with standard scripts and detailed documentation, making installation and management hassle-free on Debian, Devuan, and Ubuntu-based distributions.
104
175
 
105
- The packages includes standard scripts for preinst, postinst, prerm and postrm and man pages.
106
176
 
107
177
  ### Install eggs
108
- There are more than a way to install eggs as .deb package, the most practical is to add and use penguins-eggs-ppa.
178
+ there are multiple methods available, but one of the most practical approaches is to utilize the penguins-eggs-ppa repository.
179
+ The penguins-eggs-ppa repository provides a convenient and reliable way to access and install Eggs on your system. By adding this repository to your package manager's sources list, you gain access to the latest versions of Eggs and can easily install or update it with a few simple commands.Adding the penguins-eggs-ppa repository ensures that you have a trusted and official source for Eggs, which simplifies the installation process and ensures that you receive updates and security patches on time.By leveraging the penguins-eggs-ppa repository, you can enjoy the benefits of a streamlined installation process, convenient updates, and a reliable source for Eggs. It's a practical solution that allows you to effortlessly install and manage Eggs as a .deb package, enhancing your overall experience with this powerful software.
109
180
 
110
- #### Download the package and install with dpkg
111
181
 
112
- The simplest way to install eggs is download the [package eggs](https://sourceforge.net/projects/penguins-eggs/files/DEBS/) from [sourceforge page of the project](https://sourceforge.net/projects/penguins-eggs/) and install it
182
+ #### Download the package and install it with dpkg
113
183
 
184
+ To install Eggs, the simplest method is to download the package from the project's SourceForge page [package eggs](https://sourceforge.net/projects/penguins-eggs/files/DEBS/) and install it on your system. You can find the Eggs package on the SourceForge page here.
185
+ After downloading the appropriate package based on your system's architecture, you can proceed with the installation. If you are using an amd64 system, run the following command in the terminal:
186
+ ```sudo dpkg -i eggs_9.6.24_amd64.deb```
187
+ For i386 systems, the command would be:
188
+ ```sudo dpkg -i eggs_9.6.24_i386.deb```
189
+ Executing these commands will initiate the installation process and install Eggs on your system.
190
+ Once Eggs is successfully installed, you have the option to enhance its functionality by adding the penguins-eggs-ppa repository. This repository provides additional tools and features for Eggs. To add the penguins-eggs-ppa repository, run the following command in the terminal:
191
+ ```sudo eggs tools ppa --install```
192
+ This command will add the penguins-eggs-ppa repository to your system, allowing you to access updated versions of Eggs and additional tools provided by the repository.
193
+ By following these steps, you can easily install Eggs, add the penguins-eggs-ppa repository, [penguins-eggs-ppa](https://pieroproietti.github.io/penguins-eggs-ppa), and unlock further capabilities and enhancements for your Eggs installation.
194
+
195
+ #### Using penguins-eggs-ppa (stable version)
196
+ To simplify the process of using the penguins-eggs-ppa repository and installing Eggs, you can utilize a utility called `get-eggs`. Follow these steps to use `get-eggs`:
197
+ 1. Clone the `get-eggs` repository by running the following command:
114
198
  ```
115
- sudo dpkg -i eggs_9.6.23_amd64.deb
199
+ git clone https://github.com/pieroproietti/get-eggs
116
200
  ```
117
201
 
118
- or, on a i386 system:
202
+ 2. Navigate into the `get-eggs` directory:
119
203
  ```
120
- sudo dpkg -i eggs_9.6.23_i386.deb
204
+ cd get-eggs
121
205
  ```
122
206
 
123
- Once eggs is installed you can add the [penguins-eggs-ppa](https://pieroproietti.github.io/penguins-eggs-ppa) repository with the command: ```sudo eggs tools ppa --install```
124
-
125
- #### Using penguins-eggs-ppa (stable version)
126
-
127
- You can use a little utility I wrote: `get-eggs`. Use it in this way:
128
-
129
- * `git clone https://github.com/pieroproietti/get-eggs`
130
- * `cd get-eggs`
131
- * `sudo ./get-eggs`
132
-
133
- On Debian, Devuan and Ubuntu get-eggs will add the ppa and install eggs.
207
+ 3. Execute the utility with root privileges:
208
+ ```
209
+ sudo ./get-eggs
210
+ ```
134
211
 
135
- For derivatives of Debian, Devuan and Ubuntu, like Linuxmint, LMDE, etc, get-eggs will normally work but You can again copy and paste the following two lines in a terminal:
212
+ On Debian, Devuan, and Ubuntu, running `get-eggs` will add the penguins-eggs-ppa repository and install Eggs seamlessly.
213
+ > [!TIP]
214
+ > For derivatives of Debian, Devuan, and Ubuntu, such as Linuxmint, LMDE, etc., `get-eggs` will typically work as well. However, if needed, you can manually add the penguins-eggs-ppa repository by copying and pasting the following two lines into a terminal:
136
215
 
137
216
  ```
138
217
  curl -fsSL https://pieroproietti.github.io/penguins-eggs-ppa/KEY.gpg | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/penguins-eggs.gpg
139
218
  echo "deb [arch=$(dpkg --print-architecture)] https://pieroproietti.github.io/penguins-eggs-ppa ./" | sudo tee /etc/apt/sources.list.d/penguins-eggs.list > /dev/null
140
219
  ```
141
220
 
142
- Update your repositories and install eggs:
221
+ After adding the repository, update your package repositories and install Eggs by running the following command:
143
222
 
144
223
  ```
145
224
  sudo apt update && sudo apt install eggs
146
225
  ```
147
226
 
227
+ Executing these commands will update your package sources and install Eggs on your system.
228
+
229
+ > [!TIP]
230
+ > By using the `get-eggs` utility or manually adding the penguins-eggs-ppa repository, you can easily install Eggs on various Debian, Devuan, and Ubuntu-based distributions, including their derivatives, ensuring a smooth and hassle-free installation process.
231
+
232
+
148
233
  ### Upgrade eggs
149
- If you are using penguins-eggs-ppa You can upgrade eggs as others packages just: **sudo apt upgrade**, else simply download new versions of eggs from [sourgeforge page](https://sourceforge.net/projects/penguins-eggs/files/DEBS/) and install it with the standard command **sudo gdebi eggs_9.6.23_amd64.deb** or **sudo dpkg -i eggs_9.6.23_i386.deb** and **sudo apt install -f**.
234
+ To upgrade Eggs, the process will vary depending on whether you are using the penguins-eggs-ppa repository or not. Here's how you can upgrade Eggs with both approaches:
235
+ If you have already added the penguins-eggs-ppa repository, you can upgrade Eggs alongside other packages on your system by running the following command:
236
+ ```
237
+ sudo apt upgrade
238
+ ```
239
+ > [!TIP]
240
+ > This command will check for updates for all installed packages, including Eggs, and upgrade them to their latest versions if available.
241
+
242
+ > [!NOTE]
243
+ > On the other hand, if you have not added the penguins-eggs-ppa repository, you can manually upgrade Eggs by downloading the new version from the SourceForge page [here](https://sourceforge.net/projects/penguins-eggs/files/DEBS/). Once you have downloaded the appropriate package for your system architecture, follow these steps:
244
+
245
+ 1. Install the package using the `gdebi` command (assuming you have `gdebi` installed):
246
+ ```
247
+ sudo gdebi eggs_9.6.24_amd64.deb
248
+ ```
249
+ or for i386 systems:
250
+ ```
251
+ sudo dpkg -i eggs_9.6.24_i386.deb
252
+ ```
253
+
254
+ 2. In case of any missing dependencies, you can resolve them by running the following command:
255
+ ```
256
+ sudo apt install -f
257
+ ```
258
+ This will automatically install any required dependencies for Eggs.
259
+ > [!TIP]
260
+ > By following these instructions, you can upgrade Eggs either through the penguins-eggs-ppa repository or by manually downloading and installing the latest version from the SourceForge page. Ensure that you choose the appropriate method based on your current setup to keep Eggs up to date with the latest enhancements and bug fixes.
150
261
 
151
262
  ## Arch families
152
- eggs has been present in [AUR](https://aur.archlinux.org/) for a long time, even without my knowledge thanks the support of Arch peoples. I am currently directly maintaining the AUR version of [penguins-eggs](https://aur.archlinux.org/packages/penguins-eggs) and I'm participating in the [Manjaro Community Repository](https://gitlab.manjaro.org/packages/community/penguins-eggs).
263
+ Eggs have been available in the Arch User Repository (AUR) for quite some time, thanks to the support of the Arch Linux community. Although I was initially unaware of its presence, I am now directly maintaining the AUR version of [penguins-eggs](https://aur.archlinux.org/packages/penguins-eggs). Additionally, I am actively participating in the Manjaro Community Repository, specifically for the [penguins-eggs](https://gitlab.manjaro.org/packages/community/penguins-eggs) package.
264
+
265
+ Being present in the AUR signifies that Eggs is available for Arch Linux users to easily install and manage through their package managers. The AUR is a community-driven repository that allows users to contribute and maintain packages that are not officially supported by Arch Linux. By maintaining the AUR version of penguins-eggs, I can ensure that Arch Linux users have access to the latest updates and improvements for Eggs.
266
+
267
+ > [!TIP]
268
+ > Furthermore, my participation in the Manjaro Community Repository demonstrates my commitment to providing support for Eggs on the Manjaro distribution. Manjaro is a popular Arch-based Linux distribution known for its user-friendly approach and community-driven development. By actively contributing to the Manjaro Community Repository, I can ensure that Eggs remains compatible and well-integrated with the Manjaro ecosystem.
269
+
270
+ > [!TIP]
271
+ > In summary, Eggs is available in the AUR and is directly maintained by me. Additionally, I am actively involved in the Manjaro Community Repository to provide support for Eggs on the Manjaro distribution. This ensures that users of Arch Linux and its derivatives, such as Manjaro, can easily access and benefit from using Eggs in their systems.
153
272
 
154
- The development versions of penguins eggs and other PKGBUILDs are instead in my [eggs-pkgbuilds](https://github.com/pieroproietti/eggs-pkgbuilds) repository.
155
273
 
156
274
  ### Arch
157
- It's possible to install penguins-eggs from [AUR](https://aur.archlinux.org/packages/penguins-eggs) adding repo [Chaotic-AUR](https://aur.chaotic.cx/) and using `sudo pacman -Sy penguins-eggs`.
275
+ To install penguins-eggs on Arch Linux, there are multiple methods available. One option is to install it directly from the Arch User Repository (AUR) by adding the Chaotic-AUR repository. Here's how you can do it:
276
+
277
+ 1. Add the Chaotic-AUR repository to your system. You can find the repository at [https://aur.chaotic.cx/](https://aur.chaotic.cx/).
278
+
279
+ 2. After adding the Chaotic-AUR repository, open a terminal and run the following command to install penguins-eggs using `pacman`:
280
+ ```
281
+ sudo pacman -Sy penguins-eggs
282
+ ```
283
+ This command will synchronize the package databases and install penguins-eggs on your system.
284
+
285
+ Alternatively, you can use a utility called `get-eggs` that I have written. Here's how to use it:
286
+
287
+ 1. Clone the `get-eggs` repository by running the following command:
288
+ ```
289
+ git clone https://github.com/pieroproietti/get-eggs
290
+ ```
158
291
 
159
- You can use a little utility I wrote: `get-eggs`. Use it in this way:
292
+ 2. Change to the `get-eggs` directory:
293
+ ```
294
+ cd get-eggs
295
+ ```
160
296
 
161
- * `git clone https://github.com/pieroproietti/get-eggs`
162
- * `cd get-eggs`
163
- * `sudo ./get-eggs`
297
+ 3. Run the `get-eggs` script with sudo privileges:
298
+ ```
299
+ sudo ./get-eggs
300
+ ```
301
+ This script will add the AUR repository and install penguins-eggs on your system.
164
302
 
165
- get-eggs will add AUR repository and install penguins-eggs.
303
+ Additionally, you have the option to use the popular AUR helper tool called `yay`. Simply run the following command:
304
+ ```
305
+ yay penguins-eggs
306
+ ```
307
+ `yay` will handle the installation process for you, including any necessary dependencies.
166
308
 
167
- Of course you can also use yay: `yay penguins-eggs` or download the sources and run makepkg:
309
+ If you prefer to build from source, you can download the sources from the AUR repository. Here are the steps:
168
310
 
311
+ 1. Clone the `penguins-eggs` repository from the AUR:
169
312
  ```
170
313
  git clone https://aur.archlinux.org/packages/penguins-eggs
314
+ ```
315
+
316
+ 2. Change to the `penguins-eggs` directory:
317
+ ```
171
318
  cd penguins-eggs
319
+ ```
320
+
321
+ 3. Build and install the package using `makepkg`:
322
+ ```
172
323
  makepkg -srcCi
173
324
  ```
325
+ > [!TIP]
326
+ > This command will compile the source code, create a package, and install it on your system.
327
+ These methods provide various ways to install penguins-eggs on Arch Linux, allowing you to choose the one that suits your preferences and workflow.
328
+
329
+
174
330
  ### Manjaro
175
- From penguins-eggs v9.4.3 the package is part of the [Manjaro community](https://gitlab.manjaro.org/packages/community/penguins-eggs) repo and can be installed with `pamac install penguins-eggs`.
331
+ Starting from version 9.4.3, penguins-eggs is now included in the Manjaro community repository, making it even easier to install on Manjaro Linux. To install penguins-eggs on Manjaro, you can use the `pamac` package manager with the following command:
332
+ ```
333
+ pamac install penguins-eggs
334
+ ```
335
+ This command will fetch the package from the Manjaro community repository and install it on your system.
176
336
 
177
- Alternatively you can clone the package, and:
337
+ Alternatively, if you prefer to manually manage the installation process, you can clone the penguins-eggs package from the Manjaro community repository and build it from source. Here are the steps:
338
+
339
+ 1. Clone the penguins-eggs package from the Manjaro community repository:
178
340
  ```
179
341
  git clone https://gitlab.manjaro.org/packages/community/penguins-eggs/
180
- cd penguins-eggs
181
- makepkg -srcCi
182
342
  ```
183
343
 
184
- # Usage
344
+ 2. Change to the penguins-eggs directory:
345
+ ```
346
+ cd penguins-eggs
347
+ ```
185
348
 
186
- Once the package has been installed, you can have the new ```eggs``` command. Typing ```eggs``` will get the list of commands, typing ```eggs produce --help``` will get the eggs produce command help screen. You can also use the command autocomplete with the TABS key, you will get the possible choices for each command. In addition, there is a man page, so by typing ```man eggs``` you will get that help as well. You can also use the ```eggs mom``` command that interactively allows you to consult the help for all commands and online documentation.
349
+ 3. Build and install the package using `makepkg`:
350
+ ```
351
+ makepkg -srcCi
352
+ ```
353
+ > [!TIP]
354
+ > This command will compile the source code, create a package, and install it on your system.
187
355
 
188
- ## Examples
356
+ By including penguins-eggs in the Manjaro community repository, Manjaro Linux users can easily access and install the package using their preferred package manager. The Manjaro community repository is specifically dedicated to packages that are supported by the Manjaro community, ensuring that penguins-eggs is well-integrated and compatible with the Manjaro distribution.
189
357
 
190
- * Create a live system without user data:
358
+ > [!TIP]
359
+ > Whether you choose to install penguins-eggs using `pamac` or by manually building it from source, you can enjoy the benefits of this package on your Manjaro Linux system.
191
360
 
192
- ```sudo eggs produce ```
193
361
 
194
- * Create a live system with user data uncrypted.
362
+ # Usage
363
+ Once the package has been installed, you can have the new ```eggs``` command. Typing ```eggs``` will get the list of commands, and typing ```eggs produce --help``` will get the eggs produce command help screen. You can also use the command autocomplete with the TABS key, you will get the possible choices for each command. In addition, there is a man page, so by typing ```man eggs``` you will get that help as well. You can also use the ```eggs mom``` command that interactively allows you to consult the help for all commands and online documentation.
195
364
 
196
- ```sudo eggs produce --clone```
365
+ ## Examples
366
+ Here are some examples of how to use penguins-eggs to create live systems with different configurations:
197
367
 
198
- * Create a live system with the encrypted user data.
368
+ 1. To create a live system without user data, run the following command with `sudo`:
369
+ ```
370
+ sudo eggs produce
371
+ ```
372
+ This command will generate a live system without any user data included.
199
373
 
200
- ```sudo eggs produce --cryptedclone```
374
+ 2. To create a live system with user data that is not encrypted, use the `--clone` flag:
375
+ ```
376
+ sudo eggs produce --clone
377
+ ```
378
+ This command will produce a live system that includes user data without encryption.
201
379
 
202
- At the moment eggs uses the default fast compression, which provides a faster compression speed, for the final compression it is worth using the ```--max``` flag to get more compressed ISOs.
380
+ 3. If you want to create a live system with encrypted user data, use the `--cryptedclone` flag:
381
+ ```
382
+ sudo eggs produce --cryptedclone
383
+ ```
384
+ This command will generate a live system with encrypted user data.
203
385
 
204
- In addition to the description of the commands in this README, you can consult the [Penguins' eggs official guide](https://penguins-eggs.net/docs/Tutorial/eggs-users-guide).
386
+ By default, penguins-eggs uses fast compression for efficiency during the creation process. However, if you want a more compressed ISO file, you can use the `--max` flag during the final compression step. For example:
387
+ ```
388
+ sudo eggs produce --max
389
+ ```
390
+ > [!TIP]
391
+ > This command will apply maximum compression to the ISO file, resulting in a smaller file size. In addition to the command descriptions provided in this README, you can refer to the [Penguins' eggs official guide](https://penguins-eggs.net/docs/Tutorial/eggs-users-guide) for more detailed information on how to use penguins-eggs and its various features. The official guide offers comprehensive documentation to help you make the most out of this tool.
205
392
 
206
393
  # Commands
207
394
  <!-- commands -->
@@ -217,6 +404,7 @@ In addition to the description of the commands in this README, you can consult t
217
404
  * [`eggs help [COMMAND]`](#eggs-help-command)
218
405
  * [`eggs install`](#eggs-install)
219
406
  * [`eggs kill`](#eggs-kill)
407
+ * [`eggs krill`](#eggs-krill)
220
408
  * [`eggs mom`](#eggs-mom)
221
409
  * [`eggs produce`](#eggs-produce)
222
410
  * [`eggs status`](#eggs-status)
@@ -230,9 +418,9 @@ In addition to the description of the commands in this README, you can consult t
230
418
  * [`eggs update`](#eggs-update)
231
419
  * [`eggs version`](#eggs-version)
232
420
  * [`eggs wardrobe get [REPO]`](#eggs-wardrobe-get-repo)
233
- * [`eggs wardrobe list [WARDROBE]`](#eggs-wardrobe-list-wardrobe)
234
- * [`eggs wardrobe show [COSTUME]`](#eggs-wardrobe-show-costume)
235
- * [`eggs wardrobe wear [COSTUME]`](#eggs-wardrobe-wear-costume)
421
+ * [`eggs wardrobe list [REPO]`](#eggs-wardrobe-list-repo)
422
+ * [`eggs wardrobe show [REPO]`](#eggs-wardrobe-show-repo)
423
+ * [`eggs wardrobe wear [REPO]`](#eggs-wardrobe-wear-repo)
236
424
 
237
425
  ## `eggs adapt`
238
426
 
@@ -253,7 +441,7 @@ EXAMPLES
253
441
  $ eggs adapt
254
442
  ```
255
443
 
256
- _See code: [src/commands/adapt.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/adapt.ts)
444
+ _See code: [src/commands/adapt.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/adapt.ts)_
257
445
 
258
446
  ## `eggs analyze`
259
447
 
@@ -274,24 +462,24 @@ EXAMPLES
274
462
  sudo eggs analyze
275
463
  ```
276
464
 
277
- _See code: [src/commands/analyze.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/analyze.ts)_
465
+ _See code: [src/commands/analyze.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/analyze.ts)_
278
466
 
279
467
  ## `eggs autocomplete [SHELL]`
280
468
 
281
- display autocomplete installation instructions
469
+ Display autocomplete installation instructions.
282
470
 
283
471
  ```
284
472
  USAGE
285
473
  $ eggs autocomplete [SHELL] [-r]
286
474
 
287
475
  ARGUMENTS
288
- SHELL shell type
476
+ SHELL (zsh|bash|powershell) Shell type
289
477
 
290
478
  FLAGS
291
479
  -r, --refresh-cache Refresh cache (ignores displaying instructions)
292
480
 
293
481
  DESCRIPTION
294
- display autocomplete installation instructions
482
+ Display autocomplete installation instructions.
295
483
 
296
484
  EXAMPLES
297
485
  $ eggs autocomplete
@@ -300,10 +488,12 @@ EXAMPLES
300
488
 
301
489
  $ eggs autocomplete zsh
302
490
 
491
+ $ eggs autocomplete powershell
492
+
303
493
  $ eggs autocomplete --refresh-cache
304
494
  ```
305
495
 
306
- _See code: [@oclif/plugin-autocomplete](https://github.com/oclif/plugin-autocomplete/blob/v1.3.8/src/commands/autocomplete/index.ts)_
496
+ _See code: [@oclif/plugin-autocomplete](https://github.com/oclif/plugin-autocomplete/blob/v3.0.18/src/commands/autocomplete/index.ts)_
307
497
 
308
498
  ## `eggs calamares`
309
499
 
@@ -311,7 +501,7 @@ configure calamares or install or configure it
311
501
 
312
502
  ```
313
503
  USAGE
314
- $ eggs calamares [-h] [-i] [-n] [-r] [--remove] [--theme <value>] [-v]
504
+ $ eggs calamares [-h] [-i] [-n] [-p] [-r] [--remove] [--theme <value>] [-v]
315
505
 
316
506
  FLAGS
317
507
  -h, --help Show CLI help.
@@ -320,8 +510,8 @@ FLAGS
320
510
  -p, --policies configure calamares policies
321
511
  -r, --release release: remove calamares and all its dependencies after the installation
322
512
  -v, --verbose
323
- --remove remove calamares and its dependencies
324
- --theme=<value> theme/branding for eggs and calamares
513
+ --remove remove calamares and its dependencies
514
+ --theme=<value> theme/branding for eggs and calamares
325
515
 
326
516
  DESCRIPTION
327
517
  configure calamares or install or configure it
@@ -336,7 +526,7 @@ EXAMPLES
336
526
  sudo eggs calamares --remove
337
527
  ```
338
528
 
339
- _See code: [src/commands/calamares.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/calamares.ts)_
529
+ _See code: [src/commands/calamares.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/calamares.ts)_
340
530
 
341
531
  ## `eggs config`
342
532
 
@@ -344,13 +534,14 @@ Configure and install prerequisites deb packages to run it
344
534
 
345
535
  ```
346
536
  USAGE
347
- $ eggs config [-c] [-h] [-n] [-v]
537
+ $ eggs config [-c] [-h] [-n] [-N] [-v]
348
538
 
349
539
  FLAGS
540
+ -N, --noicons no icons
350
541
  -c, --clean remove old configuration before to create new one
351
542
  -h, --help Show CLI help.
352
543
  -n, --nointeractive no user interaction
353
- -N, --noicons no icons
544
+ -v, --verbose verbose
354
545
 
355
546
  DESCRIPTION
356
547
  Configure and install prerequisites deb packages to run it
@@ -363,7 +554,7 @@ EXAMPLES
363
554
  sudo eggs config --clean --nointeractive
364
555
  ```
365
556
 
366
- _See code: [src/commands/config.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/config.ts)_
557
+ _See code: [src/commands/config.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/config.ts)_
367
558
 
368
559
  ## `eggs cuckoo`
369
560
 
@@ -383,7 +574,7 @@ EXAMPLES
383
574
  sudo eggs cuckoo
384
575
  ```
385
576
 
386
- _See code: [src/commands/cuckoo.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/cuckoo.ts)_
577
+ _See code: [src/commands/cuckoo.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/cuckoo.ts)_
387
578
 
388
579
  ## `eggs dad`
389
580
 
@@ -410,7 +601,7 @@ EXAMPLES
410
601
  sudo dad --default
411
602
  ```
412
603
 
413
- _See code: [src/commands/dad.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/dad.ts)_
604
+ _See code: [src/commands/dad.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/dad.ts)_
414
605
 
415
606
  ## `eggs export deb`
416
607
 
@@ -437,7 +628,7 @@ EXAMPLES
437
628
  $ eggs export deb --all
438
629
  ```
439
630
 
440
- _See code: [src/commands/export/deb.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/export/deb.ts)_
631
+ _See code: [src/commands/export/deb.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/export/deb.ts)_
441
632
 
442
633
  ## `eggs export iso`
443
634
 
@@ -445,13 +636,13 @@ export iso in the destination host
445
636
 
446
637
  ```
447
638
  USAGE
448
- $ eggs export iso [-c] [-h] [-v]
639
+ $ eggs export iso [-c] [-C] [-h] [-v]
449
640
 
450
641
  FLAGS
451
- -c, --clean delete old ISOs before to copy
452
642
  -C, --checksum export checksums md5 and sha256
453
- -h, --help Show CLI help.
454
- -v, --verbose verbose
643
+ -c, --clean delete old ISOs before to copy
644
+ -h, --help Show CLI help.
645
+ -v, --verbose verbose
455
646
 
456
647
  DESCRIPTION
457
648
  export iso in the destination host
@@ -462,7 +653,7 @@ EXAMPLES
462
653
  $ eggs export iso --clean
463
654
  ```
464
655
 
465
- _See code: [src/commands/export/iso.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/export/iso.ts)_
656
+ _See code: [src/commands/export/iso.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/export/iso.ts)_
466
657
 
467
658
  ## `eggs help [COMMAND]`
468
659
 
@@ -470,10 +661,10 @@ Display help for eggs.
470
661
 
471
662
  ```
472
663
  USAGE
473
- $ eggs help [COMMAND] [-n]
664
+ $ eggs help [COMMAND...] [-n]
474
665
 
475
666
  ARGUMENTS
476
- COMMAND Command to show help for.
667
+ COMMAND... Command to show help for.
477
668
 
478
669
  FLAGS
479
670
  -n, --nested-commands Include all nested commands in the output.
@@ -482,20 +673,21 @@ DESCRIPTION
482
673
  Display help for eggs.
483
674
  ```
484
675
 
485
- _See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v5.1.23/src/commands/help.ts)_
676
+ _See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v6.0.22/src/commands/help.ts)_
486
677
 
487
- ## `eggs install` or `eggs krill`
678
+ ## `eggs install`
488
679
 
489
680
  krill: the CLI system installer - the egg became a penguin!
490
681
 
491
682
  ```
492
683
  USAGE
493
- $ eggs install [-k] [-c <value>] [-d <value>] [-H] [-h] [-i] [-n] [-N] [-p] [-r] [-s] [-S] [-u] [-v]
684
+ $ eggs install [-b] [-k] [-c <value>] [-d <value>] [-H] [-h] [-i] [-n] [-N] [-p] [-r] [-s] [-S] [-u] [-v]
494
685
 
495
686
  FLAGS
496
687
  -H, --halt Halt the system after installation
497
688
  -N, --none Swap none: 256M
498
689
  -S, --suspend Swap suspend: RAM x 2
690
+ -b, --btrfs Format btrfs
499
691
  -c, --custom=<value> custom unattended configuration
500
692
  -d, --domain=<value> Domain name, defult: .local
501
693
  -h, --help Show CLI help.
@@ -511,15 +703,18 @@ FLAGS
511
703
  DESCRIPTION
512
704
  krill: the CLI system installer - the egg became a penguin!
513
705
 
706
+ ALIASES
707
+ $ eggs krill
708
+
514
709
  EXAMPLES
515
710
  sudo eggs install
516
711
 
517
- sudo eggs install --unattended
712
+ sudo eggs install --unattended --halt
518
713
 
519
714
  sudo eggs install --custom it
520
715
  ```
521
716
 
522
- _See code: [src/commands/install.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/install.ts)_
717
+ _See code: [src/commands/install.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/install.ts)_
523
718
 
524
719
  ## `eggs kill`
525
720
 
@@ -527,7 +722,7 @@ kill the eggs/free the nest
527
722
 
528
723
  ```
529
724
  USAGE
530
- $ eggs kill [-h] [-n] [-v]
725
+ $ eggs kill [-h] [-n] [-i] [-v]
531
726
 
532
727
  FLAGS
533
728
  -h, --help Show CLI help.
@@ -542,7 +737,46 @@ EXAMPLES
542
737
  sudo eggs kill
543
738
  ```
544
739
 
545
- _See code: [src/commands/kill.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands//kill.ts)_
740
+ _See code: [src/commands/kill.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/kill.ts)_
741
+
742
+ ## `eggs krill`
743
+
744
+ krill: the CLI system installer - the egg became a penguin!
745
+
746
+ ```
747
+ USAGE
748
+ $ eggs krill [-b] [-k] [-c <value>] [-d <value>] [-H] [-h] [-i] [-n] [-N] [-p] [-r] [-s] [-S] [-u] [-v]
749
+
750
+ FLAGS
751
+ -H, --halt Halt the system after installation
752
+ -N, --none Swap none: 256M
753
+ -S, --suspend Swap suspend: RAM x 2
754
+ -b, --btrfs Format btrfs
755
+ -c, --custom=<value> custom unattended configuration
756
+ -d, --domain=<value> Domain name, defult: .local
757
+ -h, --help Show CLI help.
758
+ -i, --ip hostname as ip, eg: ip-192-168-1-33
759
+ -k, --crypted Crypted CLI installation
760
+ -n, --nointeractive no user interaction
761
+ -p, --pve Proxmox VE install
762
+ -r, --random Add random to hostname, eg: colibri-ay412dt
763
+ -s, --small Swap small: RAM
764
+ -u, --unattended Unattended installation
765
+ -v, --verbose Verbose
766
+
767
+ DESCRIPTION
768
+ krill: the CLI system installer - the egg became a penguin!
769
+
770
+ ALIASES
771
+ $ eggs krill
772
+
773
+ EXAMPLES
774
+ sudo eggs install
775
+
776
+ sudo eggs install --unattended --halt
777
+
778
+ sudo eggs install --custom it
779
+ ```
546
780
 
547
781
  ## `eggs mom`
548
782
 
@@ -562,7 +796,7 @@ EXAMPLES
562
796
  $ eggs mom
563
797
  ```
564
798
 
565
- _See code: [src/commands/mom.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/mom.ts)_
799
+ _See code: [src/commands/mom.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/mom.ts)_
566
800
 
567
801
  ## `eggs produce`
568
802
 
@@ -570,27 +804,28 @@ produce a live image from your system whithout your data
570
804
 
571
805
  ```
572
806
  USAGE
573
- $ eggs produce [--addons <value>] [--basename <value>] [-c] [-C] [-h] [-m] [-n] [-p <value>] [--release]
574
- [-s] [-f] [--theme <value>] [-v] [-y]
807
+ $ eggs produce [--addons <value>] [--basename <value>] [-c] [-C] [--excludes <value>] [-h] [--links
808
+ <value>] [-m] [-N] [-n] [-p <value>] [--release] [-s] [-f] [--theme <value>] [-u] [-v] [-y]
575
809
 
576
810
  FLAGS
577
- -C, --cryptedclone crypted clone
578
- -c, --clone clone
579
- -f, --standard standard compression
580
- -h, --help Show CLI help.
581
- -m, --max max compression
582
- -N, --noicons no icons
583
- -n, --nointeractive no user interaction
584
- -p, --prefix=<value> prefix
585
- -s, --script script mode. Generate scripts to manage iso build
586
- -u, --unsecure include /home/* and full /root contents on live
587
- -v, --verbose verbose
588
- -y, --yolk force yolk renew
589
- --addons=<value>... addons to be used: adapt, ichoice, pve, rsupport
590
- --basename=<value> basename
591
- --filters=<value>... filters to be used: custom. dev, homes, usr
592
- --release release: max compression, remove penguins-eggs and calamares after installation
593
- --theme=<value> theme for livecd, calamares branding and partitions
811
+ -C, --cryptedclone crypted clone
812
+ -N, --noicons no icons on desktop
813
+ -c, --clone clone
814
+ -f, --standard standard compression
815
+ -h, --help Show CLI help.
816
+ -m, --max max compression
817
+ -n, --nointeractive no user interaction
818
+ -p, --prefix=<value> prefix
819
+ -s, --script script mode. Generate scripts to manage iso build
820
+ -u, --unsecure /root contents are included on live
821
+ -v, --verbose verbose
822
+ -y, --yolk force yolk renew
823
+ --addons=<value>... addons to be used: adapt, ichoice, pve, rsupport
824
+ --basename=<value> basename
825
+ --excludes=<value>... use: custom, home, mine, usr, var
826
+ --links=<value>... desktop links
827
+ --release release: max compression, remove penguins-eggs and calamares after installation
828
+ --theme=<value> theme for livecd, calamares branding and partitions
594
829
 
595
830
  DESCRIPTION
596
831
  produce a live image from your system whithout your data
@@ -598,20 +833,26 @@ DESCRIPTION
598
833
  EXAMPLES
599
834
  sudo eggs produce
600
835
 
836
+ sudo eggs produce --standard
837
+
601
838
  sudo eggs produce --max
602
839
 
840
+ sudo eggs produce --max --basename=colibri
841
+
842
+ sudo eggs produce --cryptedclone 4G
843
+
603
844
  sudo eggs produce --clone
604
-
605
- sudo eggs produce --clone --max
606
-
845
+
607
846
  sudo eggs produce --basename=colibri
608
847
 
609
- sudo eggs produce --filters custom homes usr
848
+ sudo eggs produce --basename=colibri --theme theme --addons adapt
610
849
 
611
- sudo eggs produce --theme /path/to/theme --addons adapt
850
+ sudo eggs produce --excludes=usr var
851
+
852
+ sudo eggs produce --excludes=static
612
853
  ```
613
854
 
614
- _See code: [src/commands/produce.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/produce.ts)_
855
+ _See code: [src/commands/produce.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/produce.ts)_
615
856
 
616
857
  ## `eggs status`
617
858
 
@@ -632,7 +873,7 @@ EXAMPLES
632
873
  $ eggs status
633
874
  ```
634
875
 
635
- _See code: [src/commands/status.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/status.ts)_
876
+ _See code: [src/commands/status.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/status.ts)_
636
877
 
637
878
  ## `eggs syncfrom`
638
879
 
@@ -643,11 +884,11 @@ USAGE
643
884
  $ eggs syncfrom [--delete <value>] [-f <value>] [-h] [-r <value>] [-v]
644
885
 
645
886
  FLAGS
646
- -f, --file=<value> file LUKS volume encrypted
887
+ -f, --file=<value> file containing luks-volume encrypted
647
888
  -h, --help Show CLI help.
648
889
  -r, --rootdir=<value> rootdir of the installed system, when used from live
649
890
  -v, --verbose verbose
650
- --delete=<value> rsync --delete delete extraneous files from dest dirs
891
+ --delete=<value> rsync --delete delete extraneous files from dest dirs
651
892
 
652
893
  DESCRIPTION
653
894
  restore users and user data from a LUKS volumes
@@ -655,35 +896,37 @@ DESCRIPTION
655
896
  EXAMPLES
656
897
  sudo eggs syncfrom
657
898
 
658
- sudo eggs syncfrom --file /path/to/fileLUKS
899
+ sudo eggs syncfrom --file /path/to/luks-volume
659
900
  ```
660
901
 
661
- _See code: [src/commands/syncfrom.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/syncfrom.ts)_
902
+ _See code: [src/commands/syncfrom.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/syncfrom.ts)_
662
903
 
663
904
  ## `eggs syncto`
664
905
 
665
- saves users and user data in a LUKS volume inside the iso
906
+ Save users and users' data ENCRYPTED
666
907
 
667
908
  ```
668
909
  USAGE
669
- $ eggs syncto [--delete <value>] [-f <value>] [-h] [-v]
910
+ $ eggs syncto [-f <value>] [-e] [-h] [-v]
670
911
 
671
912
  FLAGS
672
- -f, --file=<value> file LUKS volume encrypted
913
+ -e, --excludes use: exclude.list.d/home.list
914
+ -f, --file=<value> file luks-volume encrypted
673
915
  -h, --help Show CLI help.
674
916
  -v, --verbose verbose
675
- --delete=<value> rsync --delete delete extraneous files from dest dirs
676
917
 
677
918
  DESCRIPTION
678
- saves users and user data in a LUKS volume inside the iso
919
+ Save users and users' data ENCRYPTED
679
920
 
680
921
  EXAMPLES
681
922
  sudo eggs syncto
682
923
 
683
- sudo eggs syncto --file /path/to/fileLUKS
924
+ sudo eggs syncto --file /path/to/luks-volume
925
+
926
+ sudo eggs syncto --excludes
684
927
  ```
685
928
 
686
- _See code: [src/commands/syncto.js](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/syncto.ts)_
929
+ _See code: [src/commands/syncto.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/syncto.ts)_
687
930
 
688
931
  ## `eggs tools clean`
689
932
 
@@ -705,11 +948,11 @@ EXAMPLES
705
948
  sudo eggs tools clean
706
949
  ```
707
950
 
708
- _See code: [src/commands/tools/clean.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/clean.ts)_
951
+ _See code: [src/commands/tools/clean.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/tools/clean.ts)_
709
952
 
710
953
  ## `eggs tools ppa`
711
954
 
712
- add/remove PPA repositories (Debian family)
955
+ add/remove repo
713
956
 
714
957
  ```
715
958
  USAGE
@@ -723,14 +966,15 @@ FLAGS
723
966
  -v, --verbose verbose
724
967
 
725
968
  DESCRIPTION
726
- add/remove PPA repositories (Debian family)
969
+ add/remove repo
727
970
 
728
971
  EXAMPLES
729
972
  sudo eggs tools ppa --add
730
973
 
731
974
  sudo eggs tools ppa --remove
732
975
  ```
733
- _See code: [src/commands/tools/ppa.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/ppa.ts)_
976
+
977
+ _See code: [src/commands/tools/ppa.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/tools/ppa.ts)_
734
978
 
735
979
  ## `eggs tools skel`
736
980
 
@@ -753,8 +997,8 @@ EXAMPLES
753
997
 
754
998
  sudo eggs tools skel --user user-to-be-copied
755
999
  ```
756
- _See code: [src/commands/tools/skel.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/skel.ts)_
757
1000
 
1001
+ _See code: [src/commands/tools/skel.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/tools/skel.ts)_
758
1002
 
759
1003
  ## `eggs tools stat`
760
1004
 
@@ -780,8 +1024,7 @@ EXAMPLES
780
1024
  $ eggs tools stat --year
781
1025
  ```
782
1026
 
783
- _See code: [src/commands/tools/stat.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/stat.ts)_
784
-
1027
+ _See code: [src/commands/tools/stat.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/tools/stat.ts)_
785
1028
 
786
1029
  ## `eggs tools yolk`
787
1030
 
@@ -801,8 +1044,8 @@ DESCRIPTION
801
1044
  EXAMPLES
802
1045
  sudo eggs tools yolk
803
1046
  ```
804
- _See code: [src/commands/tools/yolk.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/yolk.ts)_
805
1047
 
1048
+ _See code: [src/commands/tools/yolk.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/tools/yolk.ts)_
806
1049
 
807
1050
  ## `eggs update`
808
1051
 
@@ -823,7 +1066,7 @@ EXAMPLES
823
1066
  $ eggs update
824
1067
  ```
825
1068
 
826
- _See code: [src/update.js](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands//update.ts)_
1069
+ _See code: [src/commands/update.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/update.ts)_
827
1070
 
828
1071
  ## `eggs version`
829
1072
 
@@ -843,7 +1086,7 @@ FLAG DESCRIPTIONS
843
1086
  Additionally shows the architecture, node version, operating system, and versions of plugins that the CLI is using.
844
1087
  ```
845
1088
 
846
- _See code: [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/v1.1.4/src/commands/version.ts)_
1089
+ _See code: [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/v2.1.2/src/commands/version.ts)_
847
1090
 
848
1091
  ## `eggs wardrobe get [REPO]`
849
1092
 
@@ -869,22 +1112,22 @@ EXAMPLES
869
1112
  $ eggs wardrobe get your-wardrobe
870
1113
  ```
871
1114
 
872
- _See code: [src/commands/wardrobe/get.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/wardrobe/get.ts)_
873
-
1115
+ _See code: [src/commands/wardrobe/get.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/wardrobe/get.ts)_
874
1116
 
875
- ## `eggs wardrobe list [WARDROBE]`
1117
+ ## `eggs wardrobe list [REPO]`
876
1118
 
877
1119
  list costumes and accessoires in wardrobe
878
1120
 
879
1121
  ```
880
1122
  USAGE
881
- $ eggs wardrobe list [WARDROBE] [-h] [-v]
1123
+ $ eggs wardrobe list [REPO] [-h] [-d <value>] [-v]
882
1124
 
883
1125
  ARGUMENTS
884
- WARDROBE wardrobe
1126
+ REPO wardrobe to get
885
1127
 
886
1128
  FLAGS
887
- -h, --help Show CLI help.
1129
+ -d, --distro=<value> distro
1130
+ -h, --help Show CLI help.
888
1131
  -v, --verbose
889
1132
 
890
1133
  DESCRIPTION
@@ -894,21 +1137,22 @@ EXAMPLES
894
1137
  $ eggs wardrobe list
895
1138
 
896
1139
  $ eggs wardrobe list your-wardrobe
897
- ```
898
1140
 
899
- _See code: [src/commands/wardrobe/list.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/wardrobe/list.ts)_
1141
+ $ eggs wardrobe list --distro arch
1142
+ ```
900
1143
 
1144
+ _See code: [src/commands/wardrobe/list.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/wardrobe/list.ts)_
901
1145
 
902
- ## `eggs wardrobe show [COSTUME]`
1146
+ ## `eggs wardrobe show [REPO]`
903
1147
 
904
1148
  show costumes/accessories in wardrobe
905
1149
 
906
1150
  ```
907
1151
  USAGE
908
- $ eggs wardrobe show [COSTUME] [-h] [-j] [-v] [-w <value>]
1152
+ $ eggs wardrobe show [REPO] [-h] [-j] [-v] [-w <value>]
909
1153
 
910
1154
  ARGUMENTS
911
- COSTUME costume
1155
+ REPO costume to show
912
1156
 
913
1157
  FLAGS
914
1158
  -h, --help Show CLI help.
@@ -926,24 +1170,24 @@ EXAMPLES
926
1170
 
927
1171
  $ eggs wardrobe show accessories/
928
1172
  ```
929
- _See code: [src/commands/wardrobe/show.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/wardrobe/show.ts)_
930
1173
 
931
- ## `eggs wardrobe wear [COSTUME]`
1174
+ _See code: [src/commands/wardrobe/show.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/wardrobe/show.ts)_
1175
+
1176
+ ## `eggs wardrobe wear [REPO]`
932
1177
 
933
1178
  wear costume/accessories from wardrobe
934
1179
 
935
1180
  ```
936
1181
  USAGE
937
- $ eggs wardrobe wear [COSTUME] [-h] [-a] [-f] [-s] [-v] [-w <value>]
1182
+ $ eggs wardrobe wear [REPO] [-h] [-a] [-f] [-v] [-w <value>]
938
1183
 
939
1184
  ARGUMENTS
940
- COSTUME costume
1185
+ REPO costume to wear
941
1186
 
942
1187
  FLAGS
943
1188
  -a, --no_accessories not install accessories
944
1189
  -f, --no_firmwares not install firmwares
945
1190
  -h, --help Show CLI help.
946
- -s, --silent
947
1191
  -v, --verbose
948
1192
  -w, --wardrobe=<value> wardrobe
949
1193
 
@@ -958,33 +1202,1115 @@ EXAMPLES
958
1202
  sudo eggs wardrobe wear wagtail/waydroid
959
1203
  ```
960
1204
 
961
- _See code: [src/commands/wardrobe/wear.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/wardrobe/wear.ts)_
962
-
1205
+ _See code: [src/commands/wardrobe/wear.ts](https://github.com/pieroproietti/penguins-eggs/blob/v9.8.1/src/commands/wardrobe/wear.ts)_
963
1206
  <!-- commandsstop -->
1207
+ * [`eggs adapt`](#eggs-adapt)
1208
+ * [`eggs analyze`](#eggs-analyze)
1209
+ * [`eggs autocomplete [SHELL]`](#eggs-autocomplete-shell)
1210
+ * [`eggs calamares`](#eggs-calamares)
1211
+ * [`eggs config`](#eggs-config)
1212
+ * [`eggs cuckoo`](#eggs-cuckoo)
1213
+ * [`eggs dad`](#eggs-dad)
1214
+ * [`eggs export deb`](#eggs-export-deb)
1215
+ * [`eggs export iso`](#eggs-export-iso)
1216
+ * [`eggs help [COMMAND]`](#eggs-help-command)
1217
+ * [`eggs install`](#eggs-install)
1218
+ * [`eggs kill`](#eggs-kill)
1219
+ * [`eggs mom`](#eggs-mom)
1220
+ * [`eggs produce`](#eggs-produce)
1221
+ * [`eggs status`](#eggs-status)
1222
+ * [`eggs syncfrom`](#eggs-syncfrom)
1223
+ * [`eggs syncto`](#eggs-syncto)
1224
+ * [`eggs tools clean`](#eggs-tools-clean)
1225
+ * [`eggs tools ppa`](#eggs-tools-ppa)
1226
+ * [`eggs tools skel`](#eggs-tools-skel)
1227
+ * [`eggs tools stat`](#eggs-tools-stat)
1228
+ * [`eggs tools yolk`](#eggs-tools-yolk)
1229
+ * [`eggs update`](#eggs-update)
1230
+ * [`eggs version`](#eggs-version)
1231
+ * [`eggs wardrobe get [REPO]`](#eggs-wardrobe-get-repo)
1232
+ * [`eggs wardrobe list [WARDROBE]`](#eggs-wardrobe-list-wardrobe)
1233
+ * [`eggs wardrobe show [COSTUME]`](#eggs-wardrobe-show-costume)
1234
+ * [`eggs wardrobe wear [COSTUME]`](#eggs-wardrobe-wear-costume)
1235
+
1236
+ ## `eggs adapt`
1237
+ The `eggs adapt` command is used to adjust the monitor resolution specifically for virtual machines (VMs). It provides a convenient way to optimize the display settings within a VM environment.
1238
+ Here is the usage information for the `eggs adapt` command:
1239
+
1240
+ ```
1241
+ USAGE
1242
+ $ eggs adapt [-h] [-v]
1243
+
1244
+ FLAGS
1245
+ -h, --help Show CLI help.
1246
+ -v, --verbose
1247
+
1248
+ DESCRIPTION
1249
+ adapt monitor resolution for VM only
1250
+ ```
1251
+
1252
+ To use the command, you simply need to run `eggs adapt` in the terminal. There are also two optional flags you can include:
1253
+
1254
+ - `-h` or `--help`: This flag displays the help information for the `eggs adapt` command, providing a brief description of its usage and available flags.
1255
+ - `-v` or `--verbose`: Including this flag enables verbose mode, which provides more detailed output during the resolution adaptation process.
1256
+
1257
+ > [!NOTE]
1258
+ > Here is an example of how to use the `eggs adapt` command:
1259
+
1260
+ ```
1261
+ $ eggs adapt
1262
+ ```
1263
+ > [!TIP]
1264
+ > By running this command, the monitor resolution will be adjusted specifically for the virtual machine environment. The `eggs adapt` command is particularly useful when working with VMs, as it allows you to optimize the display settings to match your specific requirements. Whether you need to adjust the resolution for better readability or to ensure compatibility with certain applications, the `eggs adapt` command provides a straightforward way to achieve the desired monitor configuration within your VM.
1265
+
1266
+ _See code: [src/commands/adapt.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/adapt.ts)
1267
+
1268
+
1269
+ ## `eggs analyze`
1270
+ The `eggs analyze` command is used to perform an analysis specifically for the syncto feature. It provides a way to examine and gather information related to the syncto functionality in the penguins-eggs tool. Here is the usage information for the `eggs analyze` command:
1271
+
1272
+ ```
1273
+ USAGE
1274
+ $ eggs analyze [-h] [-v]
1275
+
1276
+ FLAGS
1277
+ -h, --help Show CLI help.
1278
+ -v, --verbose verbose
1279
+
1280
+ DESCRIPTION
1281
+ analyze for syncto
1282
+ ```
1283
+ To use the command, you can simply run `eggs analyze` in the terminal. There are also two optional flags you can include:
1284
+
1285
+ - `-h` or `--help`: This flag displays the help information for the `eggs analyze` command, providing a brief description of its usage and available flags.
1286
+ - `-v` or `--verbose`: Including this flag enables verbose mode, which provides more detailed output during the analysis process.
1287
+
1288
+ Here is an example of how to use the `eggs analyze` command:
1289
+
1290
+ ```
1291
+ sudo eggs analyze
1292
+ ```
1293
+
1294
+ By running this command with `sudo`, you initiate the analysis process specifically for the syncto feature. The `eggs analyze` command is a powerful tool for examining and gathering information related to syncto in penguins-eggs. It allows you to gain insights into the synchronization mechanism and analyze its behavior within your system. The analysis can help identify potential issues, optimize performance, and ensure the smooth operation of the syncto feature.
1295
+
1296
+ > [!TIP]
1297
+ > To explore the code implementation of the `eggs analyze` command, you can refer to the [src/commands/analyze.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/analyze.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs analyze` functionality, providing a deeper understanding of how the command is implemented and executed.
1298
+
1299
+
1300
+ ## `eggs autocomplete [SHELL]`
1301
+ The `eggs autocomplete` command is used to display installation instructions for setting up autocomplete functionality with the penguins-eggs tool in your preferred shell. Autocomplete allows you to conveniently auto-fill commands and options as you type, enhancing your productivity and reducing errors.
1302
+
1303
+ > [!TIP]
1304
+ > Here is the usage information for the `eggs autocomplete` command:
1305
+
1306
+ ```
1307
+ USAGE
1308
+ $ eggs autocomplete [SHELL] [-r]
1309
+
1310
+ ARGUMENTS
1311
+ SHELL shell type
1312
+
1313
+ FLAGS
1314
+ -r, --refresh-cache Refresh cache (ignores displaying instructions)
1315
+
1316
+ DESCRIPTION
1317
+ display autocomplete installation instructions
1318
+ ```
1319
+
1320
+ To use the command, you can run `eggs autocomplete` in the terminal. There is also an optional `SHELL` argument that you can provide to specify your shell type. The available shell options include bash and zsh. If no shell is specified, general autocomplete installation instructions will be displayed.
1321
+ > [!TIP]
1322
+ > Additionally, there is an optional `-r` or `--refresh-cache` flag. When included, this flag refreshes the cache and ignores displaying the installation instructions.
1323
+
1324
+ Here are some examples of how to use the `eggs autocomplete` command:
1325
+
1326
+ ```
1327
+ $ eggs autocomplete
1328
+ ```
1329
+ This command displays general installation instructions for autocomplete functionality.
1330
+
1331
+ ```
1332
+ $ eggs autocomplete bash
1333
+ ```
1334
+ This command provides installation instructions specifically for the bash shell.
1335
+
1336
+ ```
1337
+ $ eggs autocomplete zsh
1338
+ ```
1339
+ This command provides installation instructions specifically for the zsh shell.
1340
+
1341
+ ```
1342
+ $ eggs autocomplete --refresh-cache
1343
+ ```
1344
+ This command refreshes the cache for autocomplete, without displaying any installation instructions.
1345
+ > [!TIP]
1346
+ > To explore the code implementation of the `eggs autocomplete` command, you can refer to the [@oclif/plugin-autocomplete](https://github.com/oclif/plugin-autocomplete/blob/v1.3.8/src/commands/autocomplete/index.ts) repository. This repository contains the source code responsible for the autocomplete functionality, providing a deeper understanding of its implementation and how it integrates with the penguins-eggs tool.
1347
+
1348
+ ## `eggs calamares`
1349
+ The `eggs calamares` command is used to configure, install, or remove the Calamares tool. Calamares is a powerful installation framework that simplifies the process of setting up operating systems on various platforms. With the `eggs calamares` command, you can easily manage Calamares and its associated tasks.
1350
+
1351
+ Here is the usage information for the `eggs calamares` command:
1352
+
1353
+ ```
1354
+ USAGE
1355
+ $ eggs calamares [-h] [-i] [-n] [-r] [--remove] [--theme <value>] [-v]
1356
+
1357
+ FLAGS
1358
+ -h, --help Show CLI help.
1359
+ -i, --install install calamares and its dependencies
1360
+ -n, --nointeractive no user interaction
1361
+ -p, --policies configure calamares policies
1362
+ -r, --release release: remove calamares and all its dependencies after the installation
1363
+ -v, --verbose
1364
+ --remove remove calamares and its dependencies
1365
+ --theme=<value> theme/branding for eggs and calamares
1366
+
1367
+ DESCRIPTION
1368
+ configure calamares or install or configure it
1369
+ ```
1370
+ > [!NOTE]
1371
+ > To use the command, you can run `eggs calamares` in the terminal. The command supports several flags and options:
1372
+
1373
+ - `-h` or `--help`: This flag displays the help information for the `eggs calamares` command, providing a brief description of its usage and available flags.
1374
+ - `-i` or `--install`: Including this flag installs Calamares and its dependencies on your system.
1375
+ - `-n` or `--nointeractive`: This flag enables non-interactive mode, where no user interaction is required during the Calamares configuration process.
1376
+ - `-p` or `--policies`: Including this flag allows you to configure Calamares policies.
1377
+ - `-r` or `--release`: This flag triggers the removal of Calamares and all its dependencies after the installation.
1378
+ - `-v` or `--verbose`: Enabling this flag provides more detailed output.
1379
+
1380
+ There are two additional flags related to removing Calamares:
1381
+ - `--remove`: Including this flag removes Calamares and its dependencies from your system.
1382
+ - `--theme=<value>`: This option allows you to specify a theme or branding for both the `eggs` tool and Calamares.
1383
+
1384
+ Here are some examples of how to use the `eggs calamares` command:
1385
+
1386
+ ```
1387
+ sudo eggs calamares
1388
+ ```
1389
+ This command configures Calamares without installing or removing it.
1390
+
1391
+ ```
1392
+ sudo eggs calamares --install
1393
+ ```
1394
+ This command installs Calamares and its dependencies on your system.
1395
+
1396
+ ```
1397
+ sudo eggs calamares --install --theme=/path/to/theme
1398
+ ```
1399
+ This command installs Calamares and applies a specific theme or branding to both the `eggs` tool and Calamares.
1400
+
1401
+ ```
1402
+ sudo eggs calamares --remove
1403
+ ```
1404
+ This command removes Calamares and its dependencies from your system.
1405
+
1406
+ > [!TIP]
1407
+ > To explore the code implementation of the `eggs calamares` command, you can refer to the [src/commands/calamares.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/calamares.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs calamares` functionality, providing a deeper understanding of how the command is implemented and executed.
1408
+
1409
+ ## `eggs config`
1410
+ The `eggs config` command is used to configure and install the necessary Debian packages required to run the `eggs` tool. The `eggs` tool is a versatile utility that helps manage various tasks related to system configuration and administration. By running the `eggs config` command, you can easily set up the prerequisites and dependencies needed for the smooth execution of the `eggs` tool.
1411
+
1412
+ Here is the usage information for the `eggs config` command:
1413
+
1414
+ ```
1415
+ USAGE
1416
+ $ eggs config [-c] [-h] [-n] [-v]
1417
+
1418
+ FLAGS
1419
+ -c, --clean remove old configuration before to create new one
1420
+ -h, --help Show CLI help.
1421
+ -n, --nointeractive no user interaction
1422
+ -N, --noicons no icons
1423
+
1424
+ DESCRIPTION
1425
+ Configure and install prerequisites deb packages to run it
1426
+ ```
1427
+ > [!NOTE]
1428
+ > To use the command, you can run `eggs config` in the terminal. The command supports several flags and options:
1429
+
1430
+ - `-c` or `--clean`: Including this flag will remove the old configuration before creating a new one. This allows for a fresh setup of the `eggs` tool.
1431
+ - `-h` or `--help`: This flag displays the help information for the `eggs config` command, providing a brief description of its usage and available flags.
1432
+ - `-n` or `--nointeractive`: This flag enables non-interactive mode, where no user interaction is required during the configuration process.
1433
+ - `-N` or `--noicons`: Including this flag disables the display of icons during the configuration process.
1434
+
1435
+ The `eggs config` command is primarily responsible for configuring and installing the required Debian packages needed to run the `eggs` tool. It ensures that the necessary dependencies are in place, allowing for seamless execution of subsequent `eggs` commands.
1436
+
1437
+ Here are some examples of how to use the `eggs config` command:
1438
+
1439
+ ```
1440
+ sudo eggs config
1441
+ ```
1442
+ This command configures and installs the prerequisite Debian packages without removing any old configuration.
1443
+
1444
+ ```
1445
+ sudo eggs config --clean
1446
+ ```
1447
+ This command removes the old configuration before creating a new one, ensuring a fresh setup of the `eggs` tool.
1448
+
1449
+ ```
1450
+ sudo eggs config --clean --nointeractive
1451
+ ```
1452
+ This command removes the old configuration and performs a fresh setup without requiring any user interaction.
1453
+ > [!TIP]
1454
+ > To explore the code implementation of the `eggs config` command, you can refer to the [src/commands/config.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/config.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs config` functionality, providing a deeper understanding of how the command is implemented and executed.
1455
+
1456
+
1457
+ ## `eggs cuckoo`
1458
+ The `eggs cuckoo` command is used to initiate a PXE start with proxy-dhcp using the `eggs` tool. PXE (Preboot Execution Environment) is a technology that allows computers to boot and install an operating system over a network connection. The `eggs` tool leverages this functionality to facilitate the PXE start process with the help of a proxy-dhcp server.
1459
+
1460
+ Here is the usage information for the `eggs cuckoo` command:
1461
+
1462
+ ```
1463
+ USAGE
1464
+ $ eggs cuckoo [-h]
1465
+
1466
+ FLAGS
1467
+ -h, --help Show CLI help.
1468
+
1469
+ DESCRIPTION
1470
+ PXE start with proxy-dhcp
1471
+ ```
1472
+
1473
+ > [!NOTE]
1474
+ > To use the command, you can run `eggs cuckoo` in the terminal. The command supports a single flag:
1475
+
1476
+ - `-h` or `--help`: This flag displays the help information for the `eggs cuckoo` command, providing a brief description of its usage.
1477
+
1478
+ The primary purpose of the `eggs cuckoo` command is to initiate a PXE start process with the assistance of a proxy-dhcp server. This allows the system to boot and install an operating system using network resources. By running this command, you can initiate the PXE start process seamlessly with the necessary configurations in place.
1479
+
1480
+ Here is an example of how to use the `eggs cuckoo` command:
1481
+
1482
+ ```
1483
+ sudo eggs cuckoo
1484
+ ```
1485
+
1486
+ This command initiates the PXE start process with proxy-dhcp by leveraging the `eggs` tool. It ensures that the necessary configurations are in place to facilitate the booting and installation of an operating system over the network.
1487
+ > [!TIP]
1488
+ > To explore the code implementation of the `eggs cuckoo` command, you can refer to the [src/commands/cuckoo.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/cuckoo.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs cuckoo` functionality, providing a deeper understanding of how the command is implemented and executed.
1489
+
1490
+ ## `eggs dad`
1491
+ The `eggs dad` command is used to seek assistance from a "daddy" figure, acting as a TUI (Text User Interface) configuration helper within the `eggs` tool. This command allows users to get guidance and support for configuring their system settings and options. By running the `eggs dad` command, users can interact with the TUI configuration helper to receive help and make necessary changes.
1492
+
1493
+ Here is the usage information for the `eggs dad` command:
1494
+
1495
+ ```
1496
+ USAGE
1497
+ $ eggs dad [-c] [-d] [-h] [-v]
1498
+
1499
+ FLAGS
1500
+ -c, --clean remove old configuration before to create
1501
+ -d, --default remove old configuration and force default
1502
+ -h, --help Show CLI help.
1503
+ -v, --verbose
1504
+
1505
+ DESCRIPTION
1506
+ ask help from daddy - TUI configuration helper
1507
+ ```
1508
+ > [!NOTE]
1509
+ > To use the command, you can run `eggs dad` in the terminal. The command supports several flags and options:
1510
+
1511
+ - `-c` or `--clean`: Including this flag will remove the old configuration before creating a new one. This allows for a fresh setup of the configuration settings.
1512
+ - `-d` or `--default`: Including this flag will remove the old configuration and enforce the default settings. This can be useful when reverting back to the default configuration.
1513
+ - `-h` or `--help`: This flag displays the help information for the `eggs dad` command, providing a brief description of its usage and available flags.
1514
+ - `-v` or `--verbose`: Including this flag enables verbose mode, providing more detailed information during the configuration process.
1515
+
1516
+ The `eggs dad` command acts as a TUI configuration helper, allowing users to seek assistance from the "daddy" figure. It provides guidance and support for configuring system settings, ensuring a smooth and user-friendly experience.
1517
+
1518
+ Here are some examples of how to use the `eggs dad` command:
1519
+
1520
+ ```
1521
+ sudo eggs dad
1522
+ ```
1523
+ This command initiates the TUI configuration helper, allowing users to seek help and guidance for configuring system settings.
1524
+
1525
+ ```
1526
+ sudo eggs dad --clean
1527
+ ```
1528
+ This command removes the old configuration before creating a new one, ensuring a fresh setup of the configuration settings.
1529
+
1530
+ ```
1531
+ sudo eggs dad --default
1532
+ ```
1533
+ This command removes the old configuration and enforces the default settings, reverting back to the default configuration.
1534
+ > [!TIP]
1535
+ > To explore the code implementation of the `eggs dad` command, you can refer to the [src/commands/dad.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/dad.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs dad` functionality, providing a deeper understanding of how the command is implemented and executed.
1536
+
1537
+ ## `eggs export deb`
1538
+ The `eggs export deb` command is used to export Debian packages (`deb`), documentation files (`docs`), or ISO images to a specified destination host using the `eggs` tool. This command enables users to transfer these files from one system to another conveniently. By running the `eggs export deb` command, users can export the desired files to the destination host.
1539
+
1540
+ Here is the usage information for the `eggs export deb` command:
1541
+
1542
+ ```
1543
+ USAGE
1544
+ $ eggs export deb [-a] [-c] [-h] [-v]
1545
+
1546
+ FLAGS
1547
+ -a, --all export all archs
1548
+ -c, --clean remove old .deb before to copy
1549
+ -h, --help Show CLI help.
1550
+ -v, --verbose verbose
1551
+
1552
+ DESCRIPTION
1553
+ export deb/docs/iso to the destination host
1554
+ ```
1555
+ > [!NOTE]
1556
+ > To use the command, you can run `eggs export deb` in the terminal. The command supports several flags and options:
1557
+
1558
+ - `-a` or `--all`: Including this flag will export all available architectures. This allows for exporting files for multiple architectures simultaneously.
1559
+ - `-c` or `--clean`: Including this flag will remove the old `.deb` files before copying the new ones. This ensures a clean transfer of files to the destination host.
1560
+ - `-h` or `--help`: This flag displays the help information for the `eggs export deb` command, providing a brief description of its usage and available flags.
1561
+ - `-v` or `--verbose`: Including this flag enables verbose mode, providing more detailed information during the export process.
1562
+
1563
+ The `eggs export deb` command facilitates the export of Debian packages, documentation files, or ISO images to the destination host. This allows users to transfer these files conveniently and efficiently.
1564
+ Here are some examples of how to use the `eggs export deb` command:
1565
+
1566
+ ```
1567
+ eggs export deb
1568
+ ```
1569
+ This command exports the specified Debian packages, documentation files, or ISO images to the destination host.
1570
+
1571
+ ```
1572
+ eggs export deb --clean
1573
+ ```
1574
+ This command removes the old `.deb` files before copying the new ones, ensuring a clean transfer of files to the destination host.
1575
+
1576
+ ```
1577
+ eggs export deb --all
1578
+ ```
1579
+ This command exports the files for all available architectures, facilitating the transfer of files for multiple architectures simultaneously.
1580
+ > [!TIP]
1581
+ > To explore the code implementation of the `eggs export deb` command, you can refer to the [src/commands/export/deb.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/export/deb.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs export deb` functionality, providing a deeper understanding of how the command is implemented and executed.
1582
+
1583
+ ## `eggs export iso`
1584
+ The `eggs export iso` command is used to export ISO images to a specified destination host using the `eggs` tool. This command allows users to transfer ISO images from one system to another conveniently. By running the `eggs export iso` command, users can export the desired ISO image to the destination host.
1585
+
1586
+ Here is the usage information for the `eggs export iso` command:
1587
+
1588
+ ```
1589
+ USAGE
1590
+ $ eggs export iso [-c] [-h] [-v]
1591
+
1592
+ FLAGS
1593
+ -c, --clean delete old ISOs before to copy
1594
+ -C, --checksum export checksums md5 and sha256
1595
+ -h, --help Show CLI help.
1596
+ -v, --verbose verbose
1597
+
1598
+ DESCRIPTION
1599
+ export iso in the destination host
1600
+ ```
1601
+ > [!NOTE]
1602
+ > To use the command, you can run `eggs export iso` in the terminal. The command supports several flags and options:
1603
+
1604
+ - `-c` or `--clean`: Including this flag will delete the old ISO images before copying the new ones. This ensures a clean transfer of ISO images to the destination host.
1605
+ - `-C` or `--checksum`: Including this flag will export the checksums (md5 and sha256) for the ISO images. This provides additional verification for the integrity of the transferred ISO images.
1606
+ - `-h` or `--help`: This flag displays the help information for the `eggs export iso` command, providing a brief description of its usage and available flags.
1607
+ - `-v` or `--verbose`: Including this flag enables verbose mode, providing more detailed information during the export process.
1608
+
1609
+ The `eggs export iso` command facilitates the export of ISO images to the destination host. This allows users to conveniently transfer ISO images from one system to another.
1610
+
1611
+ Here are some examples of how to use the `eggs export iso` command:
1612
+
1613
+ ```
1614
+ eggs export iso
1615
+ ```
1616
+ This command exports the specified ISO image to the destination host.
1617
+
1618
+ ```
1619
+ eggs export iso --clean
1620
+ ```
1621
+ This command deletes the old ISO images before copying the new ones, ensuring a clean transfer of ISO images to the destination host.
1622
+
1623
+ > [!TIP]
1624
+ > To explore the code implementation of the `eggs export iso` command, you can refer to the [src/commands/export/iso.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/export/iso.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs export iso` functionality, providing a deeper understanding of how the command is implemented and executed.
1625
+
1626
+ ## `eggs help [COMMAND]`
1627
+ The `eggs help [COMMAND]` command is used to display help information for the `eggs` tool. This command provides users with detailed instructions and explanations on how to use specific commands or the `eggs` tool in general. By running the `eggs help [COMMAND]` command, users can access comprehensive documentation and guidance.
1628
+
1629
+ Here is the usage information for the `eggs help [COMMAND]` command:
1630
+
1631
+ ```
1632
+ USAGE
1633
+ $ eggs help [COMMAND] [-n]
1634
+
1635
+ ARGUMENTS
1636
+ COMMAND Command to show help for.
1637
+
1638
+ FLAGS
1639
+ -n, --nested-commands Include all nested commands in the output.
1640
+
1641
+ DESCRIPTION
1642
+ Display help for eggs.
1643
+ ```
1644
+ > [!NOTE]
1645
+ > To use the command, you can run `eggs help [COMMAND]` in the terminal. The command supports the following arguments and flags:
1646
+
1647
+ - `COMMAND`: This is an optional argument that specifies the particular command for which you want to view help information. By providing a command name, you can access detailed instructions and explanations for that specific command.
1648
+ - `-n` or `--nested-commands`: Including this flag will include all nested commands in the output. This means that not only the specified command's help information will be displayed but also the help information for any sub-commands or nested commands associated with it.
1649
+
1650
+ The primary purpose of the `eggs help [COMMAND]` command is to provide users with detailed guidance and documentation for the `eggs` tool. It allows users to access comprehensive information about commands, their usage, and available options.
1651
+ > [!TIP]
1652
+ > To explore the code implementation of the `eggs help [COMMAND]` command, you can refer to the [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v5.1.23/src/commands/help.ts) file in the plugin-help GitHub repository. This file contains the source code responsible for the `eggs help [COMMAND]` functionality, providing a deeper understanding of how the command is implemented and executed.
1653
+
1654
+ ## `eggs install` or `eggs krill`
1655
+ The `eggs install` or `eggs krill` command is used to install the CLI system installer called "krill" using the `eggs` tool. This command allows users to conveniently install the krill CLI system installer, which is represented metaphorically as an egg transforming into a penguin. The installation process provides various options and configurations to cater to different installation requirements.
1656
+
1657
+ Here is the usage information for the `eggs install` or `eggs krill` command:
1658
+
1659
+ ```
1660
+ USAGE
1661
+ $ eggs install [-k] [-c <value>] [-d <value>] [-H] [-h] [-i] [-n] [-N] [-p] [-r] [-s] [-S] [-u] [-v]
1662
+
1663
+ FLAGS
1664
+ -H, --halt Halt the system after installation
1665
+ -N, --none Swap none: 256M
1666
+ -S, --suspend Swap suspend: RAM x 2
1667
+ -c, --custom=<value> custom unattended configuration
1668
+ -d, --domain=<value> Domain name, default: .local
1669
+ -h, --help Show CLI help.
1670
+ -i, --ip hostname as IP, e.g., ip-192-168-1-33
1671
+ -k, --crypted Crypted CLI installation
1672
+ -n, --nointeractive no user interaction
1673
+ -p, --pve Proxmox VE install
1674
+ -r, --random Add random to hostname, e.g., colibri-ay412dt
1675
+ -s, --small Swap small: RAM
1676
+ -u, --unattended Unattended installation
1677
+ -v, --verbose Verbose
1678
+
1679
+ DESCRIPTION
1680
+ krill: the CLI system installer - the egg became a penguin!
1681
+ ```
1682
+ > [!NOTE]
1683
+ > To use the command, you can run `eggs install` or `eggs krill` in the terminal. The command supports numerous flags and options to customize the installation process:
1684
+
1685
+ - `-H` or `--halt`: Including this flag will halt the system after installation.
1686
+ - `-N` or `--none`: Including this flag will configure no swap memory allocation (256M).
1687
+ - `-S` or `--suspend`: Including this flag will configure swap memory allocation as double the RAM size.
1688
+ - `-c` or `--custom=<value>`: This option allows users to provide a custom unattended configuration for the installation.
1689
+ - `-d` or `--domain=<value>`: This option specifies the domain name for the installation. The default is set to `.local`.
1690
+ - `-h` or `--help`: This flag displays the help information for the `eggs install` or `eggs krill` command, providing a brief description of its usage and available flags.
1691
+ - `-i` or `--ip`: Including this flag will use the hostname as an IP address, such as `ip-192-168-1-33`.
1692
+ - `-k` or `--crypted`: Including this flag enables crypted CLI installation.
1693
+ - `-n` or `--nointeractive`: Including this flag ensures a non-interactive installation process, without requiring any user interaction.
1694
+ - `-p` or `--pve`: Including this flag specifies a Proxmox VE installation.
1695
+ - `-r` or `--random`: Including this flag adds a random string to the hostname, such as `colibri-ay412dt`.
1696
+ - `-s` or `--small`: Including this flag configures swap memory allocation based on the RAM size.
1697
+ - `-u` or `--unattended`: Including this flag enables unattended installation.
1698
+ - `-v` or `--verbose`: Including this flag enables verbose mode, providing more detailed information during the installation process.
1699
+
1700
+ The primary purpose of the `eggs install` or `eggs krill` command is to install the krill CLI system installer. This allows users to configure and customize the installation process based on their specific requirements.
1701
+
1702
+ Here are some examples of how to use the `eggs install` or `eggs krill` command:
1703
+
1704
+ ```
1705
+ sudo eggs install
1706
+ ```
1707
+ This command installs the krill CLI system installer.
1708
+
1709
+ ```
1710
+ sudo eggs install --unattended
1711
+ ```
1712
+ This command performs an unattended installation of the krill CLI system installer.
1713
+
1714
+ ```
1715
+ sudo eggs install --custom it
1716
+ ```
1717
+ This command installs the krill CLI system installer using a custom unattended configuration named "it".
1718
+ > [!TIP]
1719
+ > To explore the code implementation of the `eggs install` or `eggs krill` command, you can refer to the [src/commands/install.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/install.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs install` or `eggs krill` functionality, providing a deeper understanding of how the command is implemented and executed.
1720
+
1721
+ ## `eggs kill`
1722
+ The `eggs kill` command is used to terminate and remove eggs, metaphorically representing freeing the nest. This command allows users to delete eggs and perform additional actions related to the nest.
1723
+
1724
+ Here is the usage information for the `eggs kill` command:
1725
+
1726
+ ```
1727
+ USAGE
1728
+ $ eggs kill [-h] [-n] [-v]
1729
+
1730
+ FLAGS
1731
+ -h, --help Show CLI help.
1732
+ -i, --isos Erase all ISOs on remote mount
1733
+ -n, --nointeractive No user interaction
1734
+ -v, --verbose Verbose
1735
+
1736
+ DESCRIPTION
1737
+ Kill the eggs/free the nest
1738
+ ```
1739
+ > [!NOTE]
1740
+ > To use the command, you can run `eggs kill` in the terminal. The command supports several flags to customize the process:
1741
+
1742
+ - `-h` or `--help`: This flag displays the help information for the `eggs kill` command, providing a brief description of its usage and available flags.
1743
+ - `-i` or `--isos`: Including this flag will erase all ISOs on the remote mount.
1744
+ - `-n` or `--nointeractive`: Including this flag ensures a non-interactive execution, without requiring any user interaction.
1745
+ - `-v` or `--verbose`: Including this flag enables verbose mode, providing more detailed information during the execution.
1746
+
1747
+ The primary purpose of the `eggs kill` command is to terminate and remove eggs, symbolizing the act of freeing the nest. It offers additional options, such as erasing ISOs on the remote mount.
1748
+
1749
+ Here is an example of how to use the `eggs kill` command:
1750
+
1751
+ ```
1752
+ sudo eggs kill
1753
+ ```
1754
+ This command terminates and removes eggs, freeing the nest.
1755
+
1756
+ > [!TIP]
1757
+ > To explore the code implementation of the `eggs kill` command, you can refer to the [src/commands/kill.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/kill.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for the `eggs kill` functionality, providing a deeper understanding of how the command is implemented and executed.
1758
+
1759
+ ## `eggs mom`
1760
+ The `eggs mom` command is a feature that allows users to seek assistance from a "mommy" helper in a TUI (Text-based User Interface) environment. By invoking this command, users can request help and guidance from the "mommy" helper, who is specifically designed to provide support and aid within the TUI context.
1761
+
1762
+ Here is the usage information for the `eggs mom` command:
1763
+
1764
+ ```
1765
+ USAGE
1766
+ $ eggs mom [-h]
1767
+
1768
+ FLAGS
1769
+ -h, --help Show CLI help.
1770
+
1771
+ DESCRIPTION
1772
+ Ask help from mommy - TUI helper
1773
+ ```
1774
+
1775
+ To utilize this command, you simply need to execute `eggs mom` in the terminal. The command includes a single flag:
1776
+
1777
+ - `-h` or `--help`: This flag displays the help information for the `eggs mom` command, providing a brief description of its usage and available flags.
1778
+
1779
+ The primary purpose of the `eggs mom` command is to seek assistance from the "mommy" helper, who is specifically designed as a TUI helper. This implies that the "mommy" helper is equipped to provide guidance, support, and help within a text-based user interface environment.
1780
+
1781
+ Here is an example of how to use the `eggs mom` command:
1782
+
1783
+ ```
1784
+ $ eggs mom
1785
+ ```
1786
+
1787
+ Executing this command allows users to seek help and guidance from the "mommy" helper within the TUI environment.
1788
+ > [!TIP]
1789
+ > If you are interested in exploring the code implementation of the `eggs mom` command, you can refer to the [src/commands/mom.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/mom.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for implementing the functionality of the `eggs mom` command. By examining this code, you can gain a deeper understanding of how the command interacts with the "mommy" helper and facilitates user assistance within the TUI.
1790
+
1791
+
1792
+ ## `eggs produce`
1793
+ The `eggs produce` command is a powerful feature that allows users to generate a live image from their system, excluding their personal data. This command enables users to create a self-contained image of their system, which can be used for various purposes such as system backup, distribution, or testing.
1794
+
1795
+ Here is the usage information for the `eggs produce` command:
1796
+
1797
+ ```
1798
+ USAGE
1799
+ $ eggs produce [--addons <value>] [--basename <value>] [-c] [-C] [-h] [-m] [-n] [-p <value>] [--release]
1800
+ [-s] [-f] [--theme <value>] [-v] [-y]
1801
+
1802
+ FLAGS
1803
+ -C, --cryptedclone Enable crypted clone
1804
+ -c, --clone Enable clone
1805
+ -f, --standard Use standard compression
1806
+ -h, --help Show CLI help.
1807
+ -m, --max Use max compression
1808
+ -N, --noicons Exclude icons
1809
+ -n, --nointeractive Disable user interaction
1810
+ -p, --prefix=<value> Set prefix
1811
+ -s, --script Enable script mode. Generate scripts to manage ISO build
1812
+ -u, --unsecure Include /home/* and full /root contents in the live image
1813
+ -v, --verbose Enable verbose mode
1814
+ -y, --yolk Force yolk renew
1815
+ --addons=<value>... Specify addons to be used: adapt, ichoice, pve, rsupport
1816
+ --basename=<value> Set the basename
1817
+ --filters=<value>... Specify filters to be used: custom, dev, homes, usr
1818
+ --release Use max compression and remove penguins-eggs and calamares after installation
1819
+ --theme=<value> Set the theme for livecd, calamares branding, and partitions
1820
+
1821
+ DESCRIPTION
1822
+ Generate a live image from your system without including your personal data.
1823
+
1824
+ EXAMPLES
1825
+ sudo eggs produce
1826
+
1827
+ sudo eggs produce --max
1828
+
1829
+ sudo eggs produce --clone
1830
+
1831
+ sudo eggs produce --clone --max
1832
+
1833
+ sudo eggs produce --basename=colibri
1834
+
1835
+ sudo eggs produce --filters custom homes usr
1836
+
1837
+ sudo eggs produce --theme /path/to/theme --addons adapt
1838
+ ```
1839
+
1840
+ > [!NOTE]
1841
+ > To use the `eggs produce` command, you can run it with various options and flags depending on your requirements. Here are some notable options and flags:
1842
+
1843
+ - `--addons`: Specify additional addons to be included in the live image, such as `adapt`, `ichoice`, `pve`, or `rsupport`.
1844
+ - `--basename`: Set a custom basename for the live image.
1845
+ - `-c` or `--clone`: Enable cloning functionality, allowing the live image to replicate the system's configuration.
1846
+ - `-m` or `--max`: Use maximum compression for the live image.
1847
+ - `-s` or `--script`: Enable script mode, which generates scripts to manage the ISO build process.
1848
+ - `-u` or `--unsecure`: Include `/home/*` and the full contents of `/root` in the live image.
1849
+ - `--theme`: Set a specific theme for the live CD, Calamares branding, and partitions.
1850
+ - `--filters`: Specify filters to be applied during the live image generation, such as `custom`, `dev`, `homes`, or `usr`.
1851
+ - `--release`: Use maximum compression, and remove `penguins-eggs` and `calamares` after installation.
1852
+
1853
+ The `eggs produce` command is highly customizable and offers flexibility in generating live images according to specific needs. It provides a comprehensive set of options and flags to tailor the output image and its behavior.
1854
+ > [!TIP]
1855
+ > If you are interested in exploring the code implementation of the `eggs produce` command, you can refer to the [src/commands/produce.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/produce.ts) file in the penguins-eggs GitHub repository. This file contains the source code responsible for implementing the functionality of the `eggs produce` command. Examining this code can provide further insights into the inner workings of the command and its interaction with the system to generate the live image.
1856
+
1857
+ ## `eggs status`
1858
+ The `eggs status` command provides information about the status of eggs. It is a command-line interface (CLI) command that can be executed with various options. Here is a breakdown of the command's usage:
1859
+
1860
+ **USAGE**
1861
+ ```
1862
+ eggs status [-h] [-v]
1863
+ ```
1864
+
1865
+ **FLAGS**
1866
+ - `-h, --help`: Shows help information for the command.
1867
+ - `-v, --verbose`: Enables verbose mode, which provides more detailed output.
1868
+
1869
+ **DESCRIPTION**
1870
+ The `eggs status` command provides information about the status of eggs. It likely retrieves and displays information such as the number of eggs, their condition, or any relevant details about their status.
1871
+
1872
+ **EXAMPLES**
1873
+ ```
1874
+ eggs status
1875
+ ```
1876
+ This example executes the `eggs status` command without any additional options.
1877
+
1878
+ To learn more about the implementation and source code of the `eggs status` command, you can visit the following link: [src/commands/status.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/status.ts)
1879
+ ## `eggs syncfrom`
1880
+ The `eggs syncfrom` command is used to restore users and user data from a LUKS (Linux Unified Key Setup) volume. It is a command-line interface (CLI) command that can be executed with various options. Here is a breakdown of the command's usage:
1881
+
1882
+ **USAGE**
1883
+ ```
1884
+ eggs syncfrom [--delete <value>] [-f <value>] [-h] [-r <value>] [-v]
1885
+ ```
1886
+
1887
+ **FLAGS**
1888
+ - `-f, --file=<value>`: Specifies the file path of the LUKS volume that is encrypted.
1889
+ - `-h, --help`: Shows help information for the command.
1890
+ - `-r, --rootdir=<value>`: Specifies the root directory of the installed system when used from a live environment.
1891
+ - `-v, --verbose`: Enables verbose mode, which provides more detailed output.
1892
+ - `--delete=<value>`: Uses `rsync --delete` to delete extraneous files from the destination directories.
1893
+
1894
+ **DESCRIPTION**
1895
+ The `eggs syncfrom` command is used to restore users and user data from a LUKS volume. It likely performs operations such as decrypting the LUKS volume, copying user data, and restoring user accounts on the system.
1896
+
1897
+ **EXAMPLES**
1898
+ ```
1899
+ sudo eggs syncfrom
1900
+ ```
1901
+ This example executes the `eggs syncfrom` command with default options.
1902
+
1903
+ ```
1904
+ sudo eggs syncfrom --file /path/to/fileLUKS
1905
+ ```
1906
+ This example executes the `eggs syncfrom` command while specifying the file path of the LUKS volume to restore from.
1907
+ > [!TIP]
1908
+ > To learn more about the implementation and source code of the `eggs syncfrom` command, you can visit the following link: [src/commands/syncfrom.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/syncfrom.ts)
1909
+
1910
+ ## `eggs syncto`
1911
+ The `eggs syncto` command is designed to save users and user data in a LUKS (Linux Unified Key Setup) volume located inside the iso. It is a command-line interface (CLI) command that can be executed with various options. Here is an expanded and rewritten explanation of the command:
1912
+
1913
+ **USAGE**
1914
+ ```
1915
+ eggs syncto [--delete <value>] [-f <value>] [-h] [-v]
1916
+ ```
1917
+
1918
+ **FLAGS**
1919
+ - `-f, --file=<value>`: Specifies the file path of the LUKS volume that will be encrypted.
1920
+ - `-h, --help`: Displays help information for the command.
1921
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
1922
+ - `--delete=<value>`: Utilizes `rsync --delete` to delete extraneous files from the destination directories.
1923
+
1924
+ **DESCRIPTION**
1925
+ The `eggs syncto` command allows users to save users and user data within a LUKS volume that is located inside the iso. This command is typically used to create a secure and encrypted storage space within the iso, where user-related information can be stored and protected.
1926
+
1927
+ > [!NOTE]
1928
+ > By executing this command, the user data is encrypted and stored in a LUKS volume, ensuring the confidentiality and security of the information. The LUKS volume is embedded within the iso, making it portable and self-contained.
1929
+
1930
+ **EXAMPLES**
1931
+ ```
1932
+ sudo eggs syncto
1933
+ ```
1934
+ This example executes the `eggs syncto` command with default options.
1935
+
1936
+ ```
1937
+ sudo eggs syncto --file /path/to/fileLUKS
1938
+ ```
1939
+ This example executes the `eggs syncto` command while specifying the file path of the LUKS volume to create and save the user data.
1940
+ > [!TIP]
1941
+ > To gain a deeper understanding of the implementation and view the source code of the `eggs syncto` command, you can refer to the following link: [src/commands/syncto.js](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/syncto.ts)
1942
+
1943
+ ## `eggs tools clean`
1944
+ The `eggs tools clean` command is used to clean various system logs, apt cache, and other unnecessary files. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
1945
+
1946
+ **USAGE**
1947
+ ```
1948
+ eggs tools clean [-h] [-n] [-v]
1949
+ ```
1950
+ **FLAGS**
1951
+ - `-h, --help`: Displays help information for the command.
1952
+ - `-n, --nointeractive`: Performs the cleaning process without any user interaction.
1953
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
1954
+
1955
+ **DESCRIPTION**
1956
+ The `eggs tools clean` command is designed to remove unnecessary files and clean up system logs and apt cache. By executing this command, you can free up disk space and improve system performance by removing temporary files, log files, and cached package files. The cleaning process may include deleting system logs, which contain records of system events and activities. It may also involve cleaning up the apt cache, which stores downloaded package files. By removing these files, you can reclaim disk space and ensure that your system operates more efficiently.
1957
+
1958
+ **EXAMPLES**
1959
+ ```
1960
+ sudo eggs tools clean
1961
+ ```
1962
+ This example executes the `eggs tools clean` command with default options.
1963
+
1964
+ **To gain a deeper understanding of the implementation and view the source code of the `eggs tools clean` command, you can refer to the following link:** [src/commands/tools/clean.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/clean.ts)
1965
+
1966
+ ## `eggs tools ppa`
1967
+ The `eggs tools ppa` command is used to add or remove PPA (Personal Package Archive) repositories in the Debian family of operating systems. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
1968
+
1969
+ **USAGE**
1970
+ ```
1971
+ eggs tools ppa [-a] [-h] [-n] [-r] [-v]
1972
+ ```
1973
+
1974
+ **FLAGS**
1975
+ - `-a, --add`: Adds the penguins-eggs PPA repository.
1976
+ - `-h, --help`: Displays help information for the command.
1977
+ - `-n, --nointeractive`: Performs the operation without any user interaction.
1978
+ - `-r, --remove`: Removes the penguins-eggs PPA repository.
1979
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
1980
+
1981
+ **DESCRIPTION**
1982
+ The `eggs tools ppa` command allows users to manage PPA repositories in the Debian family of operating systems. PPA repositories are external software repositories that provide additional packages and updates not found in the official Debian repositories. By adding or removing PPA repositories, users can access a wider range of software packages and ensure their system stays up to date. To add a PPA repository, you can use the `-a` or `--add` flag. This will add the penguins-eggs PPA repository to your system, allowing you to install software packages from that repository. To remove a PPA repository, you can use the `-r` or `--remove` flag. This will remove the penguins-eggs PPA repository from your system, preventing you from installing or updating packages from that repository.
1983
+
1984
+ **EXAMPLES**
1985
+ ```
1986
+ sudo eggs tools ppa --add
1987
+ ```
1988
+ This example adds the penguins-eggs PPA repository to the system.
1989
+
1990
+ ```
1991
+ sudo eggs tools ppa --remove
1992
+ ```
1993
+ This example removes the penguins-eggs PPA repository from the system.
1994
+ > [!TIP]
1995
+ > **To gain a deeper understanding of the implementation and view the source code of the `eggs tools ppa` command, you can refer to the following link:** [src/commands/tools/ppa.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/ppa.ts)
1996
+
1997
+ ## `eggs tools skel`
1998
+ The `eggs tools skel` command is used to update the "skel" directory with the configuration files from the user's home directory. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
1999
+
2000
+ **USAGE**
2001
+ ```
2002
+ eggs tools skel [-h] [-u <value>] [-v]
2003
+ ```
2004
+
2005
+ **FLAGS**
2006
+ - `-h, --help`: Displays help information for the command.
2007
+ - `-u, --user=<value>`: Specifies the user whose home directory configuration files will be used to update the "skel" directory.
2008
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
2009
+
2010
+ **DESCRIPTION**
2011
+ The `eggs tools skel` command is designed to update the "skel" directory with configuration files from a user's home directory. The "skel" directory, short for "skeleton," is a directory in Linux systems that contains default configuration files and directories used as templates when creating new user accounts.By executing the `eggs tools skel` command, you can update the "skel" directory with the latest configuration files from a specified user's home directory. This ensures that new user accounts created on the system will have the same configuration settings as the specified user.
2012
+
2013
+ **EXAMPLES**
2014
+ ```
2015
+ sudo eggs tools skel
2016
+ ```
2017
+ This example updates the "skel" directory with the configuration files from the current user's home directory.
2018
+
2019
+ ```
2020
+ sudo eggs tools skel --user user-to-be-copied
2021
+ ```
2022
+ This example updates the "skel" directory with the configuration files from the specified user's home directory (`user-to-be-copied`).
2023
+ > [!TIP]
2024
+ > **To gain a deeper understanding of the implementation and view the source code of the `eggs tools skel` command, you can refer to the following link:** [src/commands/tools/skel.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/skel.ts)
2025
+
2026
+
2027
+ ## `eggs tools stat`
2028
+ The `eggs tools stat` command is used to retrieve statistics from SourceForge. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
2029
+
2030
+ **USAGE**
2031
+ ```
2032
+ eggs tools stat [-h] [-m] [-y]
2033
+ ```
2034
+
2035
+ **FLAGS**
2036
+ - `-h, --help`: Displays help information for the command.
2037
+ - `-m, --month`: Retrieves statistics for the current month.
2038
+ - `-y, --year`: Retrieves statistics for the current year.
2039
+
2040
+ **DESCRIPTION**
2041
+ The `eggs tools stat` command allows users to obtain statistics from SourceForge, a web-based service that provides version control, collaboration, and distribution tools for software development projects. By executing this command, users can retrieve various metrics and data related to their projects hosted on SourceForge.
2042
+
2043
+ **EXAMPLES**
2044
+ ```
2045
+ eggs tools stat
2046
+ ```
2047
+ This example retrieves general statistics from SourceForge, which may include information such as the number of downloads, active users, or project popularity.
2048
+
2049
+ ```
2050
+ eggs tools stat --month
2051
+ ```
2052
+ This example retrieves statistics specifically for the current month, providing more detailed insights into the project's performance during that period.
2053
+
2054
+ ```
2055
+ eggs tools stat --year
2056
+ ```
2057
+ This example retrieves statistics specifically for the current year, allowing users to analyze the project's overall progress and growth over time.
2058
+ > [!TIP]
2059
+ > **To gain a deeper understanding of the implementation and view the source code of the `eggs tools stat` command, you can refer to the following link:** [src/commands/tools/stat.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/stat.ts)
2060
+
2061
+ ## `eggs tools yolk`
2062
+ The `eggs tools yolk` command is used to configure the "eggs" tool to enable installation without an internet connection. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
2063
+
2064
+ **USAGE**
2065
+ ```
2066
+ eggs tools yolk [-h] [-v]
2067
+ ```
2068
+
2069
+ **FLAGS**
2070
+ - `-h, --help`: Displays help information for the command.
2071
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
2072
+
2073
+ **DESCRIPTION**
2074
+ The `eggs tools yolk` command allows users to configure the "eggs" tool to enable installation without requiring an internet connection. The "eggs" tool is a software package manager or installer that is designed to simplify the process of installing and managing software packages on a computer system. By executing the `eggs tools yolk` command with the appropriate options, users can set up the "eggs" tool to work in an offline mode. This means that it will be able to install software packages from local sources, such as a local repository or package cache, without needing to connect to the internet.
2075
+
2076
+ **EXAMPLES**
2077
+ ```
2078
+ sudo eggs tools yolk
2079
+ ```
2080
+ This example configures the "eggs" tool to install software packages without an internet connection. The `sudo` command is used to run the command with administrative privileges.
2081
+ > [!TIP]
2082
+ > **To gain a deeper understanding of the implementation and view the source code of the `eggs tools yolk` command, you can refer to the following link:** [src/commands/tools/yolk.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/tools/yolk.ts)
2083
+
2084
+ ## `eggs update`
2085
+ The `eggs update` command is used to update the Penguins' eggs tool. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
2086
+
2087
+ **USAGE**
2088
+ ```
2089
+ eggs update [-h] [-v]
2090
+ ```
2091
+
2092
+ **FLAGS**
2093
+ - `-h, --help`: Displays help information for the command.
2094
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
2095
+
2096
+ **DESCRIPTION**
2097
+ The `eggs update` command allows users to update the Penguins' eggs tool to the latest version. The Penguins' eggs tool is a software utility or package manager that is specifically designed for managing and installing software packages related to the Penguins project. By executing the `eggs update` command, users can check for updates to the Penguins' eggs tool and install the latest version if available. This ensures that users have the most up-to-date features, bug fixes, and improvements for the Penguins' eggs tool.
2098
+
2099
+ **EXAMPLES**
2100
+ ```
2101
+ eggs update
2102
+ ```
2103
+ This example checks for updates to the Penguins' eggs tool and installs the latest version if available.
2104
+ > [!TIP]
2105
+ > **To gain a deeper understanding of the implementation and view the source code related to the `eggs update` command, you can refer to the following link:** [src/update.js](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/update.ts)
2106
+
2107
+
2108
+ ## `eggs version`
2109
+ The `eggs version` command is used to retrieve information about the version of the "eggs" command-line interface (CLI). It is a command-line command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
2110
+
2111
+ **USAGE**
2112
+ ```
2113
+ eggs version [--json] [--verbose]
2114
+ ```
2115
+
2116
+ **FLAGS**
2117
+ - `--verbose`: Shows additional information about the CLI.
2118
+ - `--json`: Formats the output as JSON.
2119
+
2120
+ **GLOBAL FLAGS**
2121
+ - `--json`: Formats the output as JSON.
2122
+
2123
+ **FLAG DESCRIPTIONS**
2124
+ - `--verbose`: Shows additional information about the CLI. This includes details such as the architecture, Node.js version, operating system, and versions of plugins used by the CLI.
2125
+
2126
+ The `eggs version` command retrieves information about the version of the "eggs" CLI. By default, it provides basic version information. However, you can use the `--verbose` flag to get more detailed information, including the architecture, Node.js version, operating system, and versions of plugins used by the CLI.
2127
+
2128
+ Additionally, you can use the `--json` flag to format the output as JSON, which can be useful for automated processing or integration with other tools.
2129
+ > [!TIP]
2130
+ > **To gain a deeper understanding of the implementation and view the source code related to the `eggs version` command, you can refer to the following link:** [@oclif/plugin-version](https://github.com/oclif/plugin-version/blob/v1.1.4/src/commands/version.ts)
2131
+
2132
+
2133
+ ## `eggs wardrobe get [REPO]`
2134
+ The `eggs wardrobe get [REPO]` command is used to retrieve a wardrobe from a repository. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
2135
+
2136
+ **USAGE**
2137
+ ```
2138
+ eggs wardrobe get [REPO] [-h] [-v]
2139
+ ```
2140
+
2141
+ **ARGUMENTS**
2142
+ - `REPO`: The repository from which to retrieve the wardrobe.
2143
+
2144
+ **FLAGS**
2145
+ - `-h, --help`: Displays help information for the command.
2146
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
2147
+
2148
+ **DESCRIPTION**
2149
+ The `eggs wardrobe get [REPO]` command allows users to retrieve a wardrobe from a repository. A wardrobe, in this context, refers to a collection of clothing items that are stored and managed in a repository. By executing the `eggs wardrobe get [REPO]` command, users can specify the repository from which they want to retrieve the wardrobe. This allows users to access and view the clothing items stored in the specified repository.
2150
+
2151
+ **EXAMPLES**
2152
+ ```
2153
+ eggs wardrobe get
2154
+ ```
2155
+ This example retrieves a wardrobe from a default repository.
2156
+
2157
+ ```
2158
+ eggs wardrobe get your-wardrobe
2159
+ ```
2160
+ This example retrieves a wardrobe from a specific repository called "your-wardrobe".
2161
+ > [!TIP]
2162
+ > **To gain a deeper understanding of the implementation and view the source code related to the `eggs wardrobe get [REPO]` command, you can refer to the following link:** [src/commands/wardrobe/get.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/wardrobe/get.ts)
2163
+
2164
+ ## `eggs wardrobe list [WARDROBE]`
2165
+ The `eggs wardrobe list [WARDROBE]` command is used to list costumes and accessories stored in a wardrobe. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
2166
+
2167
+ **USAGE**
2168
+ ```
2169
+ eggs wardrobe list [WARDROBE] [-h] [-v]
2170
+ ```
2171
+
2172
+ **ARGUMENTS**
2173
+ - `WARDROBE`: The specific wardrobe to list costumes and accessories from.
2174
+
2175
+ **FLAGS**
2176
+ - `-h, --help`: Displays help information for the command.
2177
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
2178
+
2179
+ **DESCRIPTION**
2180
+ The `eggs wardrobe list [WARDROBE]` command allows users to view a list of costumes and accessories stored in a wardrobe. A wardrobe, in this context, is a collection of clothing items and accessories that can be used for various purposes, such as dressing up or creating outfits.
2181
+
2182
+ > [!NOTE]
2183
+ > By executing the `eggs wardrobe list [WARDROBE]` command, users can specify the wardrobe they want to list costumes and accessories from. This command provides a convenient way to view the items available in a specific wardrobe.
2184
+
2185
+ **EXAMPLES**
2186
+ ```
2187
+ eggs wardrobe list
2188
+ ```
2189
+ This example lists costumes and accessories from a default wardrobe.
2190
+
2191
+ ```
2192
+ eggs wardrobe list your-wardrobe
2193
+ ```
2194
+ This example lists costumes and accessories from a specific wardrobe called "your-wardrobe".
2195
+ > [!TIP]
2196
+ > **To gain a deeper understanding of the implementation and view the source code related to the `eggs wardrobe list [WARDROBE]` command, you can refer to the following link:** [src/commands/wardrobe/list.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/wardrobe/list.ts)
2197
+
2198
+
2199
+ ## `eggs wardrobe show [COSTUME]`
2200
+ The `eggs wardrobe show [COSTUME]` command is used to display costumes and accessories stored in a wardrobe. It is a command-line interface (CLI) command that can be executed with different options. Here is an expanded and rewritten explanation of the command:
2201
+
2202
+ **USAGE**
2203
+ ```
2204
+ eggs wardrobe show [COSTUME] [-h] [-j] [-v] [-w <value>]
2205
+ ```
2206
+
2207
+ **ARGUMENTS**
2208
+ - `COSTUME`: The specific costume or accessory to show.
2209
+
2210
+ **FLAGS**
2211
+ - `-h, --help`: Displays help information for the command.
2212
+ - `-j, --json`: Outputs the result in JSON format.
2213
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
2214
+ - `-w, --wardrobe=<value>`: Specifies the wardrobe to show costumes and accessories from.
2215
+
2216
+ **DESCRIPTION**
2217
+ The `eggs wardrobe show [COSTUME]` command allows users to view details and information about specific costumes and accessories stored in a wardrobe. A wardrobe, in this context, is a collection of clothing items and accessories.
2218
+
2219
+ > [!NOTE]
2220
+ > By executing the `eggs wardrobe show [COSTUME]` command, users can specify the costume or accessory they want to view. This command provides a way to retrieve information about a particular item in the wardrobe.
2221
+
2222
+ **EXAMPLES**
2223
+ ```
2224
+ eggs wardrobe show colibri
2225
+ ```
2226
+ This example shows details about the "colibri" costume.
2227
+
2228
+ ```
2229
+ eggs wardrobe show accessories/firmwares
2230
+ ```
2231
+ This example shows details about the "firmwares" accessory within the "accessories" category.
2232
+
2233
+ ```
2234
+ eggs wardrobe show accessories/
2235
+ ```
2236
+ This example shows all available costumes and accessories within the "accessories" category.
2237
+ > [!TIP]
2238
+ > **To gain a deeper understanding of the implementation and view the source code related to the `eggs wardrobe show [COSTUME]` command, you can refer to the following link:** [src/commands/wardrobe/show.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/wardrobe/show.ts)
2239
+
2240
+
2241
+ ## `eggs wardrobe wear [COSTUME]`
2242
+ The `eggs wardrobe wear [COSTUME]` command is used to wear costumes and accessories from a wardrobe. It is a command-line interface (CLI) command that can be executed with various options. Here is an expanded and rewritten explanation of the command:
2243
+
2244
+ **USAGE**
2245
+ ```
2246
+ eggs wardrobe wear [COSTUME] [-h] [-a] [-f] [-s] [-v] [-w <value>]
2247
+ ```
2248
+
2249
+ **ARGUMENTS**
2250
+ - `COSTUME`: The specific costume or accessory to wear.
2251
+
2252
+ **FLAGS**
2253
+ - `-a, --no_accessories`: Specifies not to install accessories when wearing the costume.
2254
+ - `-f, --no_firmwares`: Specifies not to install firmwares when wearing the costume.
2255
+ - `-h, --help`: Displays help information for the command.
2256
+ - `-s, --silent`: Enables silent mode, suppressing unnecessary output.
2257
+ - `-v, --verbose`: Enables verbose mode, providing more detailed output.
2258
+ - `-w, --wardrobe=<value>`: Specifies the wardrobe to wear costumes and accessories from.
2259
+
2260
+ **DESCRIPTION**
2261
+ The `eggs wardrobe wear [COSTUME]` command allows users to wear specific costumes and accessories from a wardrobe. By executing this command, users can choose a costume or accessory they want to wear, and it will be applied or installed accordingly.
2262
+
2263
+ The command provides flexibility with the following options:
2264
+ - The `-a, --no_accessories` flag can be used to exclude installing accessories when wearing the costume.
2265
+ - The `-f, --no_firmwares` flag can be used to exclude installing firmwares when wearing the costume.
2266
+ - The `-s, --silent` flag enables silent mode, reducing unnecessary output.
2267
+ - The `-v, --verbose` flag enables verbose mode, providing more detailed output.
2268
+ > [!NOTE]
2269
+ > Users can also specify the wardrobe to wear the costumes and accessories by using the `-w, --wardrobe=<value>` option.
2270
+
2271
+ **EXAMPLES**
2272
+ ```
2273
+ sudo eggs wardrobe wear duck
2274
+ ```
2275
+ This example wears the "duck" costume from the wardrobe.
2276
+
2277
+ ```
2278
+ sudo eggs wardrobe wear accessories/firmwares
2279
+ ```
2280
+ This example wears the "firmwares" accessory within the "accessories" category.
2281
+
2282
+ ```
2283
+ sudo eggs wardrobe wear wagtail/waydroid
2284
+ ```
2285
+ This example wears the "waydroid" costume from the "wagtail" category.
2286
+ > [!TIP]
2287
+ > **To gain a deeper understanding of the implementation and view the source code related to the `eggs wardrobe wear [COSTUME]` command, you can refer to the following link:** [src/commands/wardrobe/wear.ts](https://github.com/pieroproietti/penguins-eggs/blob/master/src/commands/wardrobe/wear.ts)
2288
+
2289
+
2290
+ # Penguins' eggs official guide
2291
+ **Penguins' Eggs Official Guide and Resources**
2292
+
2293
+ Welcome to the Penguins' Eggs Official Guide! This comprehensive manual provides detailed instructions on using Penguins' Eggs, a software tool designed to facilitate various tasks. Initially released in Italian, the guide can be translated into other languages using machine translation for wider accessibility.
2294
+
2295
+ To access the guide, click [here](https://penguins-eggs.net/docs/Tutorial/eggs-users-guide). It offers valuable information and step-by-step tutorials to help users navigate through the software's features. However, please note that some of the terminal samples in the guide may need updating.
2296
+
2297
+ For a visual demonstration of Penguins' Eggs in action, check out these helpful [terminal samples](https://github.com/pieroproietti/penguins-eggs/blob/master/documents/terminal-lessons/eggs_help.gif?raw=true). They provide a practical overview of how to use the tool effectively.
964
2298
 
965
- # Penguins' eggs official guide
966
- The original edition of the eggs manual is released in Italian, of course other languages can be accessed using machine translation:
967
2299
 
968
- [Penguins' eggs official guide](https://penguins-eggs.net/docs/Tutorial/eggs-users-guide)
2300
+ ## That's all, Folks!
969
2301
 
970
- A nice thing to do to help users could be to make terminal samples, I did this some time ago, but they should be updated.
2302
+ One of the standout features of Penguins' Eggs is its hassle-free setup. It comes with all the necessary configurations, making it a convenient choice for users. Just like in real life, the magic of Penguins' Eggs lies within - no additional setup required!
971
2303
 
972
- ![terminal samples](https://github.com/pieroproietti/penguins-eggs/blob/master/documents/terminal-lessons/eggs_help.gif?raw=true)
2304
+ ## More Information
973
2305
 
974
- # That's all Folks!
975
- No need other configurations, penguins-eggs are battery included or better, as in the real, live is inside! :-D
2306
+ In addition to the official guide, there are other resources available for Penguins' Eggs users, particularly developers. These resources can be found in the [penguins-eggs repository](https://github.com/pieroproietti/penguins-eggs) under the [documents](https://github.com/pieroproietti/penguins-eggs/tree/master/documents) section.
976
2307
 
977
- # More informations
978
- There is a [Penguins' eggs official guide](https://penguins-eggs.net/docs/Tutorial/eggs-users-guide) and same other documentation - mostly for developers - on the repository [penguins-eggs](https://github.com/pieroproietti/penguins-eggs) under [documents](https://github.com/pieroproietti/penguins-eggs/tree/master/documents). I want to point out [hens, differents species](https://github.com/pieroproietti/penguins-eggs/blob/master/documents/hens-different-species.md) a brief how to use eggs in Debian. Arch and Manjaro, and the post [Arch-naked](https://penguins-eggs.net/docs/Tutorial/archlinux-naked.html) on the blog which describes how to create an Arch naked live, install it, then dress the resulting system with a graphics development station.
2308
+ Some noteworthy documents include:
2309
+ - [Hens: Different Species](https://github.com/pieroproietti/penguins-eggs/blob/master/documents/hens-different-species.md): A brief guide on using Penguins' Eggs in Debian, Arch, and Manjaro.
2310
+ - [Arch-naked](https://penguins-eggs.net/docs/Tutorial/archlinux-naked.html): A blog post detailing how to create an Arch naked live, install it, and customize the resulting system into a graphics development station.
2311
+
2312
+ If you have any questions or need further assistance, feel free to contact me via email at pieroproietti@gmail.com. You can also stay updated by following my blog [here](https://penguins-eggs.net) or connecting with me on [Facebook](https://www.facebook.com/groups/128861437762355/), [GitHub](https://github.com/pieroproietti/penguins-krill), [Jitsi](https://meet.jit.si/PenguinsEggsMeeting), [Reddit](https://www.reddit.com/user/Artisan61), [Telegram](https://t.me/penguins_eggs), or [Twitter](https://twitter.com/pieroproietti).
979
2313
 
980
- You can contact me by [mail](mailto://pieroproietti@gmail.com) or follow me on
981
- [blog](https://penguins-eggs.net),
982
- [facebook](https://www.facebook.com/groups/128861437762355/),
983
- [github](https://github.com/pieroproietti/penguins-krill),
984
- [jtsi](https://meet.jit.si/PenguinsEggsMeeting),
985
- [reddit](https://www.reddit.com/user/Artisan61),
986
- [telegram](https://t.me/penguins_eggs),
987
- [twitter](https://twitter.com/pieroproietti).
988
2314
 
989
2315
  # Copyright and licenses
990
2316
  Copyright (c) 2017, 2023 [Piero Proietti](https://penguins-eggs.net/about-me.html), dual licensed under the MIT or GPL Version 2 licenses.