Browse Source

Complete rewriting

tags/v7.8.10
Piero Proietti 1 year ago
parent
commit
27ab526f72
100 changed files with 4107 additions and 7729 deletions
  1. +56
    -0
      .circleci/config.yml
  2. +4
    -7
      .editorconfig
  3. +1
    -0
      .eslintignore
  4. +6
    -0
      .eslintrc
  5. +25
    -25
      .gitignore
  6. +0
    -339
      LICENSE
  7. +0
    -110
      README.it_IT.md
  8. +129
    -185
      README.md
  9. +0
    -197
      applications/calamares.desktop
  10. +0
    -7
      applications/penguins-eggs.desktop
  11. BIN
      assets/assistenza-remota.png
  12. +0
    -12
      assets/dwagent-sh.desktop
  13. BIN
      assets/eggs.png
  14. BIN
      assets/netboot.xyz-undionly.kpxe
  15. BIN
      assets/netboot.xyz.iso
  16. BIN
      assets/netboot.xyz.kpxe
  17. BIN
      assets/penguins-eggs-1-syslinux.png
  18. BIN
      assets/penguins-eggs-2-syslinux.png
  19. BIN
      assets/penguins-eggs-3-syslinux.png
  20. +0
    -8
      assets/penguins-eggs.desktop
  21. BIN
      assets/penguins-eggs.png
  22. BIN
      assets/turtle.png
  23. BIN
      assets/undionly.kpxe
  24. +0
    -9
      assistant/assistant.desktop
  25. +0
    -72
      assistant/assistant.html
  26. +0
    -93
      assistant/assistant.sh
  27. +0
    -2
      bin/g4artisan
  28. +0
    -3
      bin/gclone
  29. +0
    -4
      bin/install-desktop
  30. +0
    -1
      bin/mount-remote
  31. +5
    -0
      bin/run
  32. +3
    -0
      bin/run.cmd
  33. +0
    -1
      bin/umount-remote
  34. +0
    -20
      developer.md
  35. +0
    -21
      documents/calamares.md
  36. +0
    -72
      documents/livecd.md
  37. +0
    -124
      documents/proxmox-ve.md
  38. +1
    -3
      eggs
  39. +2707
    -2712
      package-lock.json
  40. +60
    -56
      package.json
  41. +0
    -3
      scripts/disk_get_size.sh
  42. +0
    -6
      scripts/disk_prepare.sh
  43. +0
    -7
      scripts/disk_prepare_partition_boot.sh
  44. +0
    -8
      scripts/disk_prepare_partition_lvm.sh
  45. +0
    -56
      scripts/disk_prepare_pve.sh
  46. +0
    -39
      scripts/hatch_exclude.list
  47. +0
    -9
      scripts/is_calamares.sh
  48. +0
    -10
      scripts/is_live.sh
  49. +0
    -6
      scripts/is_mounted.sh
  50. +0
    -6
      scripts/lvmremove.sh
  51. +0
    -13
      scripts/prerequisites.sh
  52. +0
    -3
      scripts/prerequisites_calamares.sh
  53. +0
    -17
      scripts/prerequisites_sterilize.sh
  54. +0
    -99
      scripts/spawn_exclude.list
  55. +0
    -355
      src/classes/Calamares.ts
  56. +0
    -908
      src/classes/Iso.ts
  57. +0
    -332
      src/classes/Oses.ts
  58. +0
    -41
      src/classes/Prerequisites.ts
  59. +0
    -21
      src/classes/Update.ts
  60. +619
    -0
      src/classes/hatching.ts
  61. +218
    -0
      src/classes/utils.ts
  62. +36
    -0
      src/commands/info.ts
  63. +50
    -0
      src/commands/install.ts
  64. +29
    -0
      src/commands/kill.ts
  65. +47
    -0
      src/commands/prerequisites.ts
  66. +51
    -0
      src/commands/produce.ts
  67. +31
    -0
      src/commands/sterilize.ts
  68. +28
    -0
      src/commands/update.ts
  69. +1
    -211
      src/index.ts
  70. +0
    -18
      src/interfaces/IDevices.ts
  71. +0
    -10
      src/interfaces/IDistro.ts
  72. +0
    -26
      src/interfaces/IDriveList.ts
  73. +0
    -10
      src/interfaces/INet.ts
  74. +0
    -18
      src/interfaces/IOses.ts
  75. +0
    -8
      src/interfaces/IPackage.ts
  76. +0
    -40
      src/interfaces/IQuestions.ts
  77. +0
    -5
      src/interfaces/IUser.ts
  78. +0
    -10
      src/interfaces/index.ts
  79. +0
    -616
      src/lib/hatch.ts
  80. +0
    -328
      src/lib/utils.ts
  81. +0
    -6
      src/types/drivelist/index.d.ts
  82. +0
    -7
      src/types/network/index.d.ts
  83. +0
    -1
      templates/branding/eggs/branding.desc
  84. BIN
      templates/branding/eggs/eggs-logo.png
  85. +0
    -203
      templates/branding/eggs/show.qml
  86. BIN
      templates/branding/eggs/slide1.png
  87. BIN
      templates/branding/eggs/slide2.png
  88. BIN
      templates/branding/eggs/slide3.png
  89. BIN
      templates/branding/eggs/slide4.png
  90. BIN
      templates/branding/eggs/slide5.png
  91. BIN
      templates/branding/eggs/slide6.png
  92. BIN
      templates/branding/eggs/slide7.png
  93. BIN
      templates/branding/eggs/welcome.png
  94. +0
    -24
      templates/distros/bionic/calamares/modules/README.md
  95. +0
    -28
      templates/distros/bionic/calamares/modules/displaymanager.conf
  96. +0
    -97
      templates/distros/bionic/calamares/modules/locale.conf
  97. +0
    -14
      templates/distros/bionic/calamares/modules/packages.conf
  98. +0
    -2
      templates/distros/bionic/calamares/modules/removeuser.conf
  99. +0
    -1
      templates/distros/bionic/calamares/settings.conf
  100. +0
    -24
      templates/distros/buster/calamares/modules/README.md

+ 56
- 0
.circleci/config.yml View File

@@ -0,0 +1,56 @@
---
version: 2
jobs:
node-latest: &test
docker:
- image: node:latest
working_directory: ~/cli
steps:
- checkout
- restore_cache: &restore_cache
keys:
- v1-npm-{{checksum ".circleci/config.yml"}}-{{checksum "package-lock.json"}}
- v1-npm-{{checksum ".circleci/config.yml"}}
- run:
name: Install dependencies
command: npm ci
- run: ./bin/run --version
- run: ./bin/run --help
- run:
name: Testing
command: npm test
node-12:
<<: *test
docker:
- image: node:12
node-10:
<<: *test
docker:
- image: node:10
cache:
<<: *test
steps:
- checkout
- run:
name: Install dependencies
command: npm ci
- save_cache:
key: v1-npm-{{checksum ".circleci/config.yml"}}-{{checksum "package-lock.json"}}
paths:
- ~/cli/node_modules
- ~/.npm
- /usr/local/lib/node_modules

workflows:
version: 2
"penguins-eggs":
jobs:
- node-latest
- node-12
- node-10
- cache:
filters:
tags:
only: /^v.*/
branches:
ignore: /.*/

+ 4
- 7
.editorconfig View File

@@ -1,14 +1,11 @@

# editorconfig.org
root = true

[*.ts]
[*]
indent_style = space
indent_size = 2
charset = utf-8
end_of_line = lf
insert_final_newline = true
trim_trailing_whitespace = true
indent_style = tab
indent_size = 2
insert_final_newline = true

[*.md]
trim_trailing_whitespace = false

+ 1
- 0
.eslintignore View File

@@ -0,0 +1 @@
/lib

+ 6
- 0
.eslintrc View File

@@ -0,0 +1,6 @@
{
"extends": [
"oclif",
"oclif-typescript"
]
}

+ 25
- 25
.gitignore View File

@@ -1,33 +1,33 @@
# Coverage directory used by tools like istanbul
# Dependency directories
# Directory for instrumented libs generated by jscoverage/JSCover
# Logs
logs
*.log
npm-debug.log*

# Optional REPL history
# Optional eslint cache
# Optional npm cache directory
# Runtime data
pids
*-debug.log
*-error.log
*.log
*.pid
*.seed
*.pid.lock

# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov

# Coverage directory used by tools like istanbul
coverage

# Dependency directories
node_modules/

# Optional npm cache directory
.npm
.rpt2_cache/

# Optional eslint cache
*.seed
.eslintcache

# Optional REPL history
.node_repl_history

esnext/
.npm
.rpt2_cache/
/.nyc_output
/dist
/lib
/tmp
/yarn.lock
built/
coverage
esnext/
lib-cov
lib/
logs
node_modules
node_modules/
npm-debug.log*
pids

+ 0
- 339
LICENSE View File

@@ -1,339 +0,0 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc., <http://fsf.org/>
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and
modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.

10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

{description}
Copyright (C) {year} {fullname}

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.

{signature of Ty Coon}, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.

+ 0
- 110
README.it_IT.md View File

@@ -1,110 +0,0 @@

![penguins-eggs](https://github.com/pieroproietti/penguins-eggs/blob/master/assets/penguins-eggs.png?raw=true)
# penguin's eggs

[![NPM Package](https://img.shields.io/npm/v/penguins-eggs.svg?style=flat)](https://npmjs.org/package/penguins-eggs "View this project on npm")
[![Build Status](https://travis-ci.org/pieroproietti/penguins-eggs.svg?branch=master)](https://travis-ci.org/pieroproietti/penguins-eggs)
[![MIT license](http://img.shields.io/badge/license-MIT-brightgreen.svg)](http://opensource.org/licenses/MIT)
[![Join the chat at https://gitter.im/penguins-eggs/Lobby](https://badges.gitter.im/pieroproietti/penguins-eggs.svg)](https://gitter.im/penguins-eggs/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
&nbsp;[gitbook](https://penguin-s-eggs.gitbook.io/project/) &nbsp;[leggimi](./README.it_IT.md)&nbsp;[trends](https://www.npmtrends.com/penguins-eggs) &nbsp;[sourceforge](https://sourceforge.net/projects/penguins-eggs/) &nbsp;[notes](https://github.com/pieroproietti/penguins-eggs/blob/master/developer.md)

## Presentazione
penguins-eggs è uno strumento a riga di comando, in sviluppo attivo, che vi permette di rimasterizzare il vostro sistema e redistribuirlo come una immagine iso.

Il progetto è pensato non solo per la creazione dell'immagine ISO del sistema (l'uovo di pinguino) ma anche per includere tutti i necessari servizi (dhcp, dhcp-proxy, tftp e https) per realizzare un server PXE veloce e potente che può lavorare da solo, o integrarsi in una rete preesistente all'interno della tua azienda o in casa.

Essendo scritto in puro javascript, può essere idealmente utilizzato per distribuzioni Linux differenti. Al momento, è testato su Debian 10 Buster (in sviluppo), Debian 9 Stretch (stable), Debian 8 Jessie (old stable), Ubuntu 19.04, 18.10 etc, LMDE 2 e LMDE 3, Linux Mint 19.1. Vorremmo estendere il supporto ad altre versioni di Linux, in particolare a Fedora (per ragioni di diffusione) ed ad Arch, ma abbiamo bisogno di aiuto.

penguins-eggs, al momento "aprile 2019" è in uno stato maturo, anche se può presentare qualche problema con persone senza sufficienti capacità di gestione di Linux. D'altra parte, per sua natura, penguins-eggs non è adatto ad un utente finale ma è sostanzialmente uno strumento tecnico per tecnici.

Con esso potrete facilmente creare la propria distribuzione Linux per la scuola, l'azienda, financo il proprio gruppo di amici, distribuendolo attraverso le immagini iso su chiavetta o su internet. Mentre il processo di creazione dell'immagine ISO è sostanzialmente un processo cli, per quanto riguarda l'installazione si può procedere in due modalità: modalità cli o gui. Difatti, grazie alla integrazione con calamares, l'installazione del vostro sistema live sarà professionale, allo stesso livello se non superiore, al sistema di installazione originale.


## Installazione di penguins-eggs
Ok, è venuto il momento di provare penguin's eggs!
Per prima cosa è necessario installare nodejs e npm, si consiglia l'installazione a partire dalla repository di [nodesource](https://github.com/nodesource/distributions/blob/master/README.md#deb).

A questo punto potremo installare penguins-eggs con i comandi:

```sudo npm config set unsafe-perm true```

```sudo npm i penguins-egg -g```

## Installazione dei prerequisiti
penguins-eggs per il suo funzionamento ha bisogno di alcuni programmi, che dovremo istallare. Potete procedere semplicemente con il comando:

```sudo eggs prerequisites```


## Comandi
Su eggs potete agire con i seguenti comandi:
* prerequisites
* spawn
* info
* kill
* calamares
* hatch

### spawn
La funzione di spawm è la "deposizione" dell'uovo ovvero la creazione della Iso contenente l'immagine del sistema. Il comando spawn accetta il parametro ```-d``` o ```--distroname``` che definisce il nome della distro.

```sudo eggs spawn -d mydistroname```

### info
Ottiene le principali informazione sul vostro sistema installato. Queste informazioni sono utilizzate per il processo di spawn e per la configurazione del programma di installazione calamares.

```sudo eggs info```


### kill
Si intende l'operazione di cancellazione dell'uovo creato con l'operazione di spawn. Pulisce il sistema e recupera lo spazio.

```sudo eggs kill```

### calamares (configurazione calamares)
Questo comando è utile soprattutto in fase di sviluppo e debugging, genera la configurazione di calamares anche "al volo" permettendo così di correggere errori presenti nell'immagine stessa.

```sudo eggs calamares```

### hatch (avvio installazione cli)
Un uovo per diventare un pinguino necessita del processo di "cova" hatch! Nel nostro caso avremo bisogno semplicemente di definire all'uovo le informazioni necessarie e, in pochi minuti, avremo un nuovo pinguino installato.

```sudo eggs hatch```

Verranno proposti alcuni parametri come: username, password, hostname,
domain, networking, installation device and type. Normalmente potrete accettare i default.

#### Opzioni
* -d --distroname <distroname>

Se non usate questa opzione, il nome dell'host (hostname) verrà utilizzato come nome della distro. L'immagine generata verrà quindi denominata hostname will us dove-YYYY-MM-DD_HHMM-ZZ.

esempio: host ``penguin`` will produce an iso called ``penguin-2017-10-22_2047_02.iso``

**Attenzione**: Non impauritevi, ma fate attenzione, l'operazione di hatch è distruttiva ed irreversibile, verrà formattato i vostro disco rigido e gli eventuali dati presenti. **Assicuratevi di avere il backup dei vostri dati prima di operare**.

### calamares (installazione gui)
Probabilmente preferirete l'installatore grafico per le vostre esigenze, anche se a volte scoprirete la praticità del sistema cli. Per avviare l'installer grafico, date il seguente comando:

```sudo calamares```

calamares è un programma di installazione grafico molto avanzato. Eggs lo installa con i prerequisites ed esegue la configurazione di esso con l'opzione calamares.

## Sviluppo
Fate riferimento a quanto riportato nella versione in inglese.

## Altre informazioni
Per altre informazioni, potete consultare [Piero Proietti's blog](http://pieroproietti.github.com), contattarmi o aprire una [issue](https://github.com/pieroproietti/penguins-eggs/issues) su github.

* facebook group:  [Penguin's Eggs](https://www.facebook.com/groups/128861437762355/)
* twitter: [@pieroproietti](https://twitter.com/pieroproietti)
* google+: [PieroProietti](https://plus.google.com/+PieroProietti)
* mail: piero.proietti@gmail.com

**artisan**

## Copyright and licenses
Copyright (c) 2017, [Piero Proietti](http://pieroproietti.github.com), dual licensed under the MIT or GPL Version 2 licenses.


+ 129
- 185
README.md View File

@@ -1,225 +1,169 @@
penguins-eggs
=============

remaster your system and distribuite it

[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![Version](https://img.shields.io/npm/v/penguins-eggs.svg)](https://npmjs.org/package/penguins-eggs)
[![CircleCI](https://circleci.com/gh/pieroproietti/penguins-eggs/tree/master.svg?style=shield)](https://circleci.com/gh/pieroproietti/penguins-eggs/tree/master)
[![Downloads/week](https://img.shields.io/npm/dw/penguins-eggs.svg)](https://npmjs.org/package/penguins-eggs)
[![License](https://img.shields.io/npm/l/penguins-eggs.svg)](https://github.com/pieroproietti/penguins-eggs/blob/master/package.json)

<!-- toc -->
* [Usage](#usage)
* [Commands](#commands)
<!-- tocstop -->
# Usage
<!-- usage -->
```sh-session
$ npm install -g penguins-eggs
$ eggs COMMAND
running command...
$ eggs (-v|--version|version)
penguins-eggs/7.1.0 linux-x64 node-v12.15.0
$ eggs --help [COMMAND]
USAGE
$ eggs COMMAND
...
```
<!-- usagestop -->
# Commands
<!-- commands -->
* [`eggs help [COMMAND]`](#eggs-help-command)
* [`eggs info [FILE]`](#eggs-info-file)
* [`eggs install [FILE]`](#eggs-install-file)
* [`eggs kill [FILE]`](#eggs-kill-file)
* [`eggs prerequisites [FILE]`](#eggs-prerequisites-file)
* [`eggs produce [FILE]`](#eggs-produce-file)
* [`eggs sterilize [FILE]`](#eggs-sterilize-file)
* [`eggs update [FILE]`](#eggs-update-file)

## `eggs help [COMMAND]`

display help for eggs

![penguins-eggs](https://github.com/pieroproietti/penguins-eggs/blob/master/assets/penguins-eggs.png?raw=true)
# penguin's eggs

[![NPM Package](https://img.shields.io/npm/v/penguins-eggs.svg?style=flat)](https://npmjs.org/package/penguins-eggs "View this project on npm")
[![Build Status](https://travis-ci.org/pieroproietti/penguins-eggs.svg?branch=master)](https://travis-ci.org/pieroproietti/penguins-eggs)
[![MIT license](http://img.shields.io/badge/license-MIT-brightgreen.svg)](http://opensource.org/licenses/MIT)
[![Join the chat at https://gitter.im/penguins-eggs/Lobby](https://badges.gitter.im/pieroproietti/penguins-eggs.svg)](https://gitter.im/penguins-eggs/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
&nbsp;[gitbook](https://penguin-s-eggs.gitbook.io/project/) &nbsp;[leggimi](./README.it_IT.md)&nbsp;[trends](https://www.npmtrends.com/penguins-eggs) &nbsp;[sourceforge](https://sourceforge.net/projects/penguins-eggs/) &nbsp;[notes](https://github.com/pieroproietti/penguins-eggs/blob/master/developer.md)


## Presentation
penguins-eggs is a console utility, in active development, who let you to
remaster your system and redistribuite it as iso images or from the lan via PXE
remote boot.

The scope of this project is to implement the process of remastering your
version of Linux, generate it as ISO image to burn on a CD/DVD or copy to a usb
key to boot your system. You can also boot your egg - via remote boot - on your
LAN.

All it is written in pure nodejs, so ideally can be used with differents Linux
distros. At the moment it is tested with Debian 10 Buster, Debian 9 Stretch, Debian 8 Jessie,
Ubuntu 19.04 and derivates as Linux Mint and Bunsenlabs Helium.
For others distros we need to find collaborations.

penguins-eggs, at the moment 2019 september 20 is in a beta state, and can have again
same troubles for people not in confidence with Linux system administration, but
can be already extremely usefull, You can easily create your organization/school
version of Linux and deploy it on your LAN, give it to your friends as usb key
or publish eggs in the internet!

You can try now penguins-eggs, it is a console utility - no GUI - but don't be
scared, penguins-eggs is a console command - really very simple usage - if you
are able to open a terminal, you can use it.

## Install penguins-eggs
Well, it is time to try it!

### Prerequisites
penguins-eggs need nodejs installed, use the version on the nodesource [repository](https://github.com/nodesource/distributions/blob/master/README.md#deb). You can install version 12 for AMD64, or the version 8 for i386 (i386 is not available for Node.js 10 and later) according your computer architecture.

If not already installed, You need also to install the ``build-essential`` package too.

```apt-get install build-essential```

penguins-eggs depend on various packages too, you must install them using once the options
prerequisites-cli and prerequisites-calamares, if you want to use the GUI installer.

### Installation penguins-eggs via npm

After You have installed nodejs, you can install penguins-eggs with the utility npm (node package manager).
Simply copy and past the following lines:

```sudo npm config set unsafe-perm true```

```sudo npm i penguins-eggs -g```

### Intel 386
The last version is Node.js v8.x:

#### Ubuntu
```curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -```
```sudo apt-get install -y nodejs```

#### Debian

```curl -sL https://deb.nodesource.com/setup_8.x | bash -```

```apt-get install -y nodejs```

and finally, we check the nodejs version:

```apt-cache policy nodejs ```

```nodejs: ```
``` Installato: 8.16.1-1nodesource1 ```
``` Candidato: 8.16.1-1nodesource1 ```
``` Tabella versione: ```
``` *** 8.16.1-1nodesource1 100 ```
``` 100 /var/lib/dpkg/status ```

and install it:

```apt install nodejs=8.16.1-1nodesource1```


### Installation penguins-eggs from source

You need a functional installation of Linux Debian version 10, 9 or 8, LinuxMint, LMDE,
Ubuntu 19.04 or derivates and install all the prerequisites plus the ``build-essential`` package.

```apt-get install build-essential```
```
USAGE
$ eggs help [COMMAND]

At this point You can download last version on github.com. Copy and past the
following lines:
ARGUMENTS
COMMAND command to show help for

```
git clone https://github.com/pieroproietti/penguins-eggs
cd penguins-eggs
npm i
OPTIONS
--all see all commands in CLI
```

You can launch egg, in developer mode, in this way:
_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v2.2.3/src/commands/help.ts)_

```cd penguins-eggs```
## `eggs info [FILE]`

```sudo npm run ts-start spawn```
describe the command here

or, in short:
```./eggs spawn```
```
USAGE
$ eggs info [FILE]

Of course, you can build it or link it.
OPTIONS
-f, --force
-h, --help show CLI help
-n, --name=name name to print
```

_See code: [src/commands/info.ts](https://github.com/pieroproietti/penguins-eggs/blob/v7.1.0/src/commands/info.ts)_

## `eggs install [FILE]`

## Commands
On the eggs you can do same actions:
* produce
* info
* install
* prerequisites-cli
* prerequisites-calamares
* update
* kill
describe the command here

### spawn/produce (preparazione dell'uovo/creazione ISO)
The function of spawn is to generate the egg. Your system is copied and packaged
as an iso file. This is a live system version of your real system, and you can
masterize it or put in a USB key and use, and install your version of linux on
everyone computer. The command spawn accept the parameter ```-d``` or
```--distroname``` who, as the name implies is the name and, also, the hostname
of your live system.
```
USAGE
$ eggs install [FILE]

```sudo eggs produce -d mydistroname```
OPTIONS
-f, --force
-h, --help show CLI help
-n, --name=name name to print
```

### info
You will get the main information about your system. This information will be used in the process of spawn and configure the installer.
_See code: [src/commands/install.ts](https://github.com/pieroproietti/penguins-eggs/blob/v7.1.0/src/commands/install.ts)_

```sudo eggs info```
## `eggs kill [FILE]`

### hatch/install (cova dell'uovo/installazione)
An egg to became penguin need to be hatched! In our case we simply need to give
to the egg the informations for installation and - in few minuts - (far
before the fatitical 21 days) we will have a new penguin.
describe the command here

```sudo eggs hatch```
```
USAGE
$ eggs kill [FILE]

You will be prompted to various parameters like: username, password, hostname,
domain, networking, installation device and type. Usually, you can accept the
defaults.
OPTIONS
-f, --force
-h, --help show CLI help
-n, --name=name name to print
```

If is installed the package calamares, you can use it to install the system.
Calamares is a GUI installer, pretty good and pratical.
_See code: [src/commands/kill.ts](https://github.com/pieroproietti/penguins-eggs/blob/v7.1.0/src/commands/kill.ts)_

**Attention**: Don't be scared, but be attent to that you are doing here,
the operation of hatch is destructive and irreversible, and will format your
disk and destroy your data to prepare the machine for the installation of your
new penguin. **Be sure to have backup of your data before**.
## `eggs prerequisites [FILE]`

### prerequisites
You must use it once before to use eggs, it will install various Debian packages needing for the process of building iso.
describe the command here

### calamares
On Debian Buster and other distros where the package calamares exist,this option install calamares and configure it.
```
USAGE
$ eggs prerequisites [FILE]

### update (aggiornamento di penguin's eggs)
You can update your version of penguins-eggs with the last version published.
OPTIONS
-f, --force
-h, --help show CLI help
-n, --name=name name to print
```

```sudo eggs update```
_See code: [src/commands/prerequisites.ts](https://github.com/pieroproietti/penguins-eggs/blob/v7.1.0/src/commands/prerequisites.ts)_

### sterilize (remove live packages)
When you decide your system is ok, you can remove the live packages and sterilize your penguin.
## `eggs produce [FILE]`

### kill (libera lo spazio occupato)
As the name say is the operation of break and kill the egg created. You will
free your system from the egg.
describe the command here

```sudo eggs kill```
```
USAGE
$ eggs produce [FILE]

OPTIONS
-f, --force
-h, --help show CLI help
-n, --name=name name to print
```

## Options
* -d --distroname <distroname>
* -b --branding <branding>
_See code: [src/commands/produce.ts](https://github.com/pieroproietti/penguins-eggs/blob/v7.1.0/src/commands/produce.ts)_

If you dont use this option, the computer hostname will used as distroname.
The image iso generated, will be called distroname-YYYY-MM-DD_HHMM-ZZ
Where YYYY-MM-DD-HHMM is year, MM mount, DD day. HHMM is your local time and
ZZ the difference betwen your local time and the greenwich one.
## `eggs sterilize [FILE]`

eg: host ``penguin`` will produce an iso called ``penguin-2017-10-22_2047_02.iso``
describe the command here

```
USAGE
$ eggs sterilize [FILE]

## Development
I build and test penguins-eggs on a customized version of
[Proxmox VE](https://pve.proxmox.com/wiki/Main_Page) who let me to create/destroy
a lot of virtual PCs with different configurations: one or more net cards,
processor, memory and so on. It is easy to have, install Debian Stretch
with your preferedd GUI, I use cinnamon, and follow this
[howto](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch) in their site.
OPTIONS
-f, --force
-h, --help show CLI help
-n, --name=name name to print
```

# Distributions supported
At the moment penguins-eggs is working on:
* Debian 10, 9, 8 and sid
* Ubuntu 19.04
* Linux Mint 19.2, LMDE 3
* Busenlabs helium (all versions)
_See code: [src/commands/sterilize.ts](https://github.com/pieroproietti/penguins-eggs/blob/v7.1.0/src/commands/sterilize.ts)_

# That's all Folks!
No need other configurations, penguins-eggs are battery included or better, as in the real, the live is inside! :-D
## `eggs update [FILE]`

## More informations
For other informations, look at [Piero Proietti's blog](http://pieroproietti.github.com),
contact me, or open an [issue](https://github.com/pieroproietti/penguins-eggs/issues) on github.
describe the command here

* facebook group:  [Penguin's Eggs](https://www.facebook.com/groups/128861437762355/)
* twitter: [@pieroproietti](https://twitter.com/pieroproietti)
* google+: [PieroProietti](https://plus.google.com/+PieroProietti)
* mail: piero.proietti@gmail.com
```
USAGE
$ eggs update [FILE]

**sarcazzo**
OPTIONS
-f, --force
-h, --help show CLI help
-n, --name=name name to print
```

## Copyright and licenses
Copyright (c) 2017, 2019 [Piero Proietti](http://pieroproietti.github.com), dual licensed under the MIT or GPL Version 2 licenses.
_See code: [src/commands/update.ts](https://github.com/pieroproietti/penguins-eggs/blob/v7.1.0/src/commands/update.ts)_
<!-- commandsstop -->

+ 0
- 197
applications/calamares.desktop View File

@@ -1,197 +0,0 @@
#!/usr/bin/env xdg-open
[Desktop Entry]
Type=Application
Version=1.0
Name=Install System
GenericName=System Installer
Keywords=calamares;system;installer
TryExec=calamares
#Exec=pkexec /usr/bin/calamares
Exec=sudo -H /usr/bin/calamares
Comment=Calamares — System Installer
Icon=calamares
Terminal=false
StartupNotify=true
Categories=Qt;System;
X-AppStream-Ignore=true

Name[ar]=تثبيت النظام
Icon[ar]=كالامارس
GenericName[ar]=مثبت النظام
Comment[ar]=كالامارس - مثبت النظام
Name[be]=Усталяваць сістэму
Icon[be]=calamares
GenericName[be]=Усталёўшчык сістэмы
Comment[be]=Calamares — усталёўшчык сістэмы
Name[bg]=Инсталирай системата
Icon[bg]=calamares
GenericName[bg]=Системен Инсталатор
Comment[bg]=Calamares — Системен Инсталатор
Name[ca]=Instal·la el sistema
Icon[ca]=calamares
GenericName[ca]=Instal·lador de sistema
Comment[ca]=Calamares — Instal·lador de sistema
Name[da]=Installér system
Icon[da]=calamares
GenericName[da]=Systeminstallationsprogram
Comment[da]=Calamares — Systeminstallationsprogram
Name[de]=System installieren
Icon[de]=calamares
GenericName[de]=Installation des Betriebssystems
Comment[de]=Calamares - Installation des Betriebssystems
Name[el]=Εγκατάσταση συστήματος
Icon[el]=calamares
GenericName[el]=Εγκατάσταση συστήματος
Comment[el]=Calamares — Εγκατάσταση συστήματος
Name[en_GB]=Install System
Icon[en_GB]=calamares
GenericName[en_GB]=System Installer
Comment[en_GB]=Calamares — System Installer
Name[es]=Instalar Sistema
Icon[es]=calamares
GenericName[es]=Instalador del Sistema
Comment[es]=Calamares — Instalador del Sistema
Name[et]=Paigalda süsteem
Icon[et]=calamares
GenericName[et]=Süsteemipaigaldaja
Comment[et]=Calamares — süsteemipaigaldaja
Name[eu]=Sistema instalatu
Icon[eu]=calamares
GenericName[eu]=Sistema instalatzailea
Comment[eu]=Calamares - sistema instalatzailea
Name[es_PR]=Instalar el sistema
Name[fr]=Installer le système
Icon[fr]=calamares
GenericName[fr]=Installateur système
Comment[fr]=Calamares - Installateur système
Name[gl]=Instalación do Sistema
Icon[gl]=calamares
GenericName[gl]=Instalador de sistemas
Comment[gl]=Calamares — Instalador de sistemas
Name[he]=התקנת מערכת
Icon[he]=calamares
GenericName[he]=אשף התקנה
Comment[he]=Calamares - אשף התקנה
Name[hi]=सिस्टम इंस्टॉल करें
Icon[hi]=calamares
GenericName[hi]=सिस्टम इंस्टॉलर
Comment[hi]=Calamares — सिस्टम इंस्टॉलर
Name[hr]=Instaliraj sustav
Icon[hr]=calamares
GenericName[hr]=Instalacija sustava
Comment[hr]=Calamares — Instalacija sustava
Name[hu]=Rendszer telepítése
Icon[hu]=calamares
GenericName[hu]=Rendszertelepítő
Comment[hu]=Calamares – Rendszertelepítő
Name[id]=Instal Sistem
Icon[id]=calamares
GenericName[id]=Pemasang
Comment[id]=Calamares — Pemasang Sistem
Name[is]=Setja upp kerfið
Icon[is]=calamares
GenericName[is]=Kerfis uppsetning
Comment[is]=Calamares — Kerfis uppsetning
Name[cs_CZ]=Nainstalovat
Icon[cs_CZ]=calamares
GenericName[cs_CZ]=Instalátor systému
Comment[cs_CZ]=Calamares – instalátor operačních systémů
Name[ja]=システムをインストール
Icon[ja]=calamares
GenericName[ja]=システムインストーラー
Comment[ja]=Calamares — システムインストーラー
Name[ko]=시스템 설치
Icon[ko]=깔라마레스
GenericName[ko]=시스템 설치 관리자
Comment[ko]=깔라마레스 — 시스템 설치 관리자
Name[lt]=Įdiegti Sistemą
Icon[lt]=calamares
GenericName[lt]=Sistemos diegimas į kompiuterį
Comment[lt]=Calamares — Sistemos diegimo programa
Name[it_IT]=Installa il sistema
Icon[it_IT]=calamares
GenericName[it_IT]=Programma d'installazione del sistema
Comment[it_IT]=Calamares — Programma d'installazione del sistema
Name[mk]=Инсталирај го системот
Icon[mk]=calamares
GenericName[mk]=Системен Инсталер
Comment[mk]=Calamares - Системен Инсталер
Name[nb]=Installer System
Icon[nb]=calamares
GenericName[nb]=Systeminstallatør
Comment[nb]=Calamares-systeminstallatør
Name[nl]=Installeer systeem
Icon[nl]=calamares
GenericName[nl]=Installatieprogramma
Comment[nl]=Calamares — Installatieprogramma
Name[pl]=Zainstaluj system
Icon[pl]=calamares
GenericName[pl]=Instalator systemu
Comment[pl]=Calamares — Instalator systemu
Name[pt_BR]=Sistema de Instalação
Icon[pt_BR]=calamares
GenericName[pt_BR]=Instalador de Sistema
Comment[pt_BR]=Calamares — Instalador de Sistema
Name[ro]=Instalează sistemul
Icon[ro]=calamares
GenericName[ro]=Instalator de sistem
Comment[ro]=Calamares — Instalator de sistem
Name[ru]=Установить систему
Icon[ru]=calamares
GenericName[ru]=Установщик системы
Comment[ru]=Calamares - Установщик системы
Name[sk]=Inštalovať systém
Icon[sk]=calamares
GenericName[sk]=Inštalátor systému
Comment[sk]=Calamares — Inštalátor systému
Name[sl]=Namesti sistem
Name[sq]=Instalo Sistemin
Icon[sq]=calamares
GenericName[sq]=Instalues Sistemi
Comment[sq]=Calamares — Instalues Sistemi
Name[fi_FI]=Asenna Järjestelmä
Icon[fi_FI]=calamares
GenericName[fi_FI]=Järjestelmän Asennusohjelma
Comment[fi_FI]=Calamares — Järjestelmän Asentaja
Name[sr@latin]=Instaliraj sistem
Name[sr]=Инсталирај систем
Name[sv]=Installera system
Icon[sv]=calamares
GenericName[sv]=Systeminstallerare
Comment[sv]=Calamares — Systeminstallerare
Name[th]=ติดตั้งระบบ
Name[uk]=Встановити Систему
GenericName[uk]=Встановлювач системи
Comment[uk]=Calamares - Встановлювач системи
Name[zh_CN]=安装系统
Icon[zh_CN]=calamares
GenericName[zh_CN]=系统安装程序
Comment[zh_CN]=Calamares — 系统安装程序
Name[zh_TW]=安裝系統
Icon[zh_TW]=calamares
GenericName[zh_TW]=系統安裝程式
Comment[zh_TW]=Calamares ── 系統安裝程式
Name[ast]=Instalar el sistema
Icon[ast]=calamares
GenericName[ast]=Instalador del sistema
Comment[ast]=Calamares — Instalador del sistema
Name[eo]=Instali Sistemo
Icon[eo]=calamares
GenericName[eo]=Sistema Instalilo
Comment[eo]=Calamares — Sistema Instalilo
Name[ne_NP]= सिस्टम इन्स्टल गर्नुहोस्
Icon[ne_NP]=Calamares
GenericName[ne_NP]=सिस्टम इन्स्टलर
Comment[ne_NP]=Calamares - सिस्टम इन्स्टलर
Name[es_MX]=Instalar el Sistema
Icon[es_MX]=calamares
GenericName[es_MX]=Instalador del sistema
Comment[es_MX]=Calamares - Instalador del sistema
Name[pt_PT]=Instalar Sistema
Icon[pt_PT]=calamares
GenericName[pt_PT]=Instalador de Sistema
Comment[pt_PT]=Calamares - Instalador de Sistema
Name[tr_TR]=Sistemi Yükle
Icon[tr_TR]=calamares
GenericName[tr_TR]=Sistem Yükleyici
Comment[tr_TR]=Calamares — Sistem Yükleyici

+ 0
- 7
applications/penguins-eggs.desktop View File

@@ -1,7 +0,0 @@
[Desktop Entry]
Encoding=UTF-8
Name=Collegamento a Introduzione - Penguin's eggs
Type=Link
URL=https://penguin-s-eggs.gitbook.io/project/
Icon=/usr/share/icons/eggs.png
Name[it_IT]=Penguin's eggs

BIN
assets/assistenza-remota.png View File

Before After
Width: 256  |  Height: 256  |  Size: 48 KiB

+ 0
- 12
assets/dwagent-sh.desktop View File

@@ -1,12 +0,0 @@
#!/usr/bin/env xdg-open
[Desktop Entry]
Encoding=UTF-8
Name=Assistenza remota
Type=Application
Icon=assistenza-remota
Name[it_IT]=Assistenza remota
Categories=GNOME;GTK;Network
TryExec=dwagent.sh
Exec=dwagent.sh
Comment=Richiesta assistenza remota
Terminal=false

BIN
assets/eggs.png View File

Before After
Width: 48  |  Height: 48  |  Size: 3.6 KiB

BIN
assets/netboot.xyz-undionly.kpxe View File


BIN
assets/netboot.xyz.iso View File


BIN
assets/netboot.xyz.kpxe View File


BIN
assets/penguins-eggs-1-syslinux.png View File

Before After
Width: 640  |  Height: 480  |  Size: 237 KiB

BIN
assets/penguins-eggs-2-syslinux.png View File

Before After
Width: 640  |  Height: 480  |  Size: 225 KiB

BIN
assets/penguins-eggs-3-syslinux.png View File

Before After
Width: 640  |  Height: 429  |  Size: 290 KiB

+ 0
- 8
assets/penguins-eggs.desktop View File

@@ -1,8 +0,0 @@
#!/usr/bin/env xdg-open
[Desktop Entry]
Encoding=UTF-8
Name=Penguin's eggs book
Type=Application
Exec=firefox https://penguin-s-eggs.gitbook.io/project
Icon=eggs
Categories=GNOME;GTK;Utility;

BIN
assets/penguins-eggs.png View File

Before After
Width: 200  |  Height: 144  |  Size: 46 KiB

BIN
assets/turtle.png View File

Before After
Width: 640  |  Height: 480  |  Size: 156 KiB

BIN
assets/undionly.kpxe View File


+ 0
- 9
assistant/assistant.desktop View File

@@ -1,9 +0,0 @@
[Desktop Entry]
Name=Aiuto installazione
Comment=Assistente scelta installazione
GenericName=Aiuto installazione
Exec=/usr/lib/node_modules/penguins-eggs/assistant/assistant.sh
Terminal=false
Type=Application
Icon=calamares
Categories=system

+ 0
- 72
assistant/assistant.html View File

@@ -1,72 +0,0 @@
<html>
<title>Assistant Penguin's eggs</title>
<body>
<h1>Penguin's eggs</h1>
<p>Questa remix può essere utilizzata così com'è - live -oppure installata
sul vostro computer.</p>
<h3>Utenti</h3>
<p>Sia l'utente live che l'utente root, se non diversamente
specificato sono impostati come user/password:
<li>live/evolution</li>
<li>root/evolution</li>
</p>

<h2>Utilizzo della remix come live</h2>
<p>L'utilizzo di questo sistema in forma live non comporta, -
di massima - pericoli per i dati sul disco rigido.</p>
<p>Fate naturalmente attenzione a non cancellare i vostri dati!</p>

<h1>Installazione</h1>
<p>L'installazione può essere fatta con l'installer grafico,
(opzione consigliata) oppure può avvenire da
terminale.</p>

</p>
<h2>Calamares - installer grafico</h2>
<p><a href="https://calamares.io/">Calamares</a> è un programma
di installazione GUI molto sofisticato, sicuro ed è l'opzione
consigliata per la maggior parte degli utenti.</p>

<h2>Eggs hatch - Installazione da terminale</h2>
<p><a href="https://penguin-s-eggs.gitbook.io/project/">eggs hatch</a>
è un installatore da terminale molto semplice e
scarno, non permette l'installazione del sistema a fianco
di un altro preesistente, anzi CANCELLA il sistema
precedente e lo sostituisce. Fate quindi molta attenzione.</p>
<p>Il vantaggio di eggs hatch è che funzionando
senza interfaccia grafica è molto più versatile
e veloce su macchine poco potenti. </p>
<p>E' consigliato solo per i casi in cui Calamares
risultasse eccessivamente lento e non usabile.</p>

<h2>Licenza</h2>
<p>Penguin's eggs è rilasciato sotto licenza MIT.</p>

<pre>
Copyright (c) 2018/2019 Piero Proietti <piero.proietti@gmail.com>

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following
conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
</pre>

</body>
</html>

+ 0
- 93
assistant/assistant.sh View File

@@ -1,93 +0,0 @@
#!/bin/bash
# Script author: Piero Proietti
# Script site: https://github.com/pieroproietti/penguins-eggs
# Script date: 28/9/2019
# Script per scegliere l'installer per eggs

##
function conferma(){
zenity \
--title="Assistente di Penguin's eggs" \
--question \
--text "L'installazione si è conclusa. \
Puoi riavviare il tuo sistema o continuare ad usare la versione live" \
--ok-label="Continua con la live" \
--cancel-label="Reboot" \
--width=400 \
--height=100
case $? in
0)
;;
1)
sudo reboot
;;
esac
}




zenity --title="Assistente Penguin's eggs" \
--text-info \
--html \
--filename=/usr/lib/node_modules/penguins-eggs/assistant/assistant.html \
--width=700 \
--height=500

ans=$(zenity --list \
--title="Assistente di Penguin's eggs" \
--text "Puoi selezionare: \
<i>calamares</i> installer grafico,\
<i>hatch</i> installazione da terminale"\
--radiolist \
--column "Scelta" \
--column "Opzioni" \
FALSE "calamares" \
FALSE "hatch" \
TRUE "live" --separator=":" \
--width=700 \
--height=200)


case "$ans" in
calamares)
zenity \
--title="Assistente di Penguin's eggs" \
--question \
--text "E' stato selezionato l'installer grafico <b>calamares</b>\
<i>Questo installer può cancellare il vostro disco rigido!</i>"\
--ok-label="Si, continua con Calamares" \
--cancel-label="No"\
--width=400 \
--height=100
case $? in
0)
xterm -title "Assistant GUI installer" -e sudo calamares
;;
1)
;;
esac
;;

hatch)
zenity \
--title="Assistente di Penguin's eggs" \
--question \
--text "E' stato selezionato l'installer da terminale <b>eggs hatch</b>. \
<i>Attenzione, questo installer può cancellare il vostro disco rigido</i> \
Sicuri di voler continuare?"\
--ok-label="Si, installa con eggs hatch" \
--cancel-label="No" \
--width=400 \
--height=100
case $? in
0)
xterm -title "Assistant CLI installer" -e sudo eggs hatch
conferma
;;
1)
;;
esac
;;
esac


+ 0
- 2
bin/g4artisan View File

@@ -1,2 +0,0 @@
git config --global user.email "piero.proietti@gmail.com"
git config --global user.name "Piero Proietti"

+ 0
- 3
bin/gclone View File

@@ -1,3 +0,0 @@
git clone http://github.com/pieroproietti/$1
#cd $1
#git checkout develop

+ 0
- 4
bin/install-desktop View File

@@ -1,4 +0,0 @@
xdg-user-dirs-update
xdg-desktop-icon install --novendor /usr/share/applications/calamares.desktop
xdg-desktop-icon install --novendor /usr/share/applications/dwagent-sh.desktop
xdg-desktop-icon install --novendor /usr/share/applications/penguins-eggs.desktop

+ 0
- 1
bin/mount-remote View File

@@ -1 +0,0 @@
sshfs artisan@$1:/home/artisan ~/remote

+ 5
- 0
bin/run View File

@@ -0,0 +1,5 @@
#!/usr/bin/env node

require('@oclif/command').run()
.then(require('@oclif/command/flush'))
.catch(require('@oclif/errors/handle'))

+ 3
- 0
bin/run.cmd View File

@@ -0,0 +1,3 @@
@echo off

node "%~dp0\run" %*

+ 0
- 1
bin/umount-remote View File

@@ -1 +0,0 @@
echo fusermount -u /home/artisan/devel

+ 0
- 20
developer.md View File

@@ -1,20 +0,0 @@
![penguins-eggs](https://github.com/pieroproietti/penguins-eggs/blob/master/assets/penguins-eggs.png?raw=true)
# penguin's eggs

[![NPM Package](https://img.shields.io/npm/v/penguins-eggs.svg?style=flat)](https://npmjs.org/package/penguins-eggs "View this project on npm")
[![Build Status](https://travis-ci.org/pieroproietti/penguins-eggs.svg?branch=master)](https://travis-ci.org/pieroproietti/penguins-eggs)
[![MIT license](http://img.shields.io/badge/license-MIT-brightgreen.svg)](http://opensource.org/licenses/MIT)
[![Join the chat at https://gitter.im/penguins-eggs/Lobby](https://badges.gitter.im/pieroproietti/penguins-eggs.svg)](https://gitter.im/penguins-eggs/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
&nbsp;[gitbook](https://penguin-s-eggs.gitbook.io/project/) &nbsp;[Leggimi](./README.it_IT.md)&nbsp;[trends](https://www.npmtrends.com/penguins-eggs)


## Versione 5.X.X
Ho tolto tutti i riferimenti a babel6 e babel7, rispettivamente precedentemente utilizzata e presa in esame per la compilazione. Alla fine sto utilizzando esclusivamente typescript, spero di essere nel giusto.

Ho avuto problemi ultimamente e questo ha portato ad azzerare e, quindi a ripristinare la repository penguins-eggs, al momento è stata ricomposta.

Per questa versione sono stati completamente rivisti i file
* package.json
* tslint.json
* tsconfig.json
* /src/types per i tipi locali

+ 0
- 21
documents/calamares.md View File

@@ -1,21 +0,0 @@
= Compilazione di calamares

## Installare

```apt-get install qtdeclarative5-dev qttools5-dev libyaml-cpp-dev libpolkit-qt5-1-dev extra-cmake-modules libkf5parts-dev qtwebengine5-dev libparted-dev qt5-default qtscript5-dev qttools5-dev qttools5-dev-tools qtmultimedia5-dev libqt5svg5-dev libqt5webkit5-dev libsdl2-dev libasound2 libxmu-dev libxi-dev freeglut3-dev libasound2-dev libjack-jackd2-dev libxrandr-dev libqt5xmlpatterns5-dev libqt5xmlpatterns5 libkpmcore4-dev gettext```

```apt-get install python3-dev libboost-dev libboost-python-dev libpythonqt-dev libkf5plasma-dev libkf5package-data libkf5config-bin```

apt-get install libkf5activities-dev
```apt-get install cmake```

## Scaricare sorgenti
```git clone https://github.com/calamares/calamares```

## Selezionare la versione 3.1.x-stable
```git checkout 3.1.x-stable```

```mkdir calamares/build```
```cd calamares/build```
```cmake -DCMAKE_BUILD_TYPE=Debug ..```
```make```

+ 0
- 72
documents/livecd.md View File

@@ -1,72 +0,0 @@
# LiveCD

From https://live-team.pages.debian.net/live-manual/html/live-manual/the-basics.en.html


With live systems, it's an operating system, built for one of the supported architectures (currently amd64 and i386). It is made from the following parts:

* Linux kernel image, usually named vmlinuz
* Initial RAM disk image (initrd): a RAM disk set up for the Linux boot, containing modules possibly needed to mount the System image and some scripts to do it.
* System image: The operating system's filesystem image. Usually, a SquashFS compressed filesystem is used to minimize the live system image size. Note that it is read-only. So, during boot the live system will use a RAM disk and 'union' mechanism to enable writing files within the running system. However, all modifications will be lost upon shutdown unless optional persistence is used (see Persistence).
* Bootloader: A small piece of code crafted to boot from the chosen medium, possibly presenting a prompt or menu to allow selection of options/configuration. It loads the Linux kernel and its initrd to run with an associated system filesystem. Different solutions can be used, depending on the target medium and format of the filesystem containing the previously mentioned components: isolinux to boot from a CD or DVD in ISO9660 format, syslinux for HDD or USB drive booting from a VFAT partition, extlinux for ext2/3/4 and btrfs partitions, pxelinux for PXE netboot, GRUB for ext2/3/4 partitions, etc.

La creazione di initramfs (initrd) in Debian è initramfs-update, mentre in Fedora è fatta con dracut.

```mkinitramfs -o ~/tmp/initramfs-$(uname -r)```

FILES
* /etc/initramfs-tools/initramfs.conf

The default configuration file for the script. See initramfs.conf(5) for a description of the available configuration parameter.

* /etc/initramfs-tools/modules

Specified modules will be put in the generated image and loaded when the system boots. The format - one per line - is identical to that of /etc/modules, which is described in modules(5).

* /etc/initramfs-tools/conf.d

The conf.d directory allows one to hardcode bootargs at initramfs build time via config snippets. This allows one to set ROOT or RESUME. This is especially useful for bootloaders, which do not pass an root bootarg.

* /etc/initramfs-tools/DSDT.aml

If this file exists, it will be appended to the initramfs in a way that causes it to be loaded by ACPI.



[https://francoconidi.it/creare-una-debian-stretch-live-custom-persistente-sicura/](Creare una Debian Stretch Live Custom persistente Sicura)

## Pacchetti da installare
``` sudo apt install -y debootstrap grub-common grub-pc-bin grub-efi-amd64-bin efibootmgr syslinux squashfs-tools cryptsetup```

## Creazione Environment:

* sudo mkdir $HOME/debian_live
* sudo debootstrap --arch=amd64 --variant=minbase stretch $HOME/debian_live/chroot

cd
* sudo mount -o /dev /root/debian_live/chroot/dev
* sudo mount -o /dev/pts /root/debian_live/chroot/dev/pts
* sudo mount -o /proc /root/debian_live/chroot/proc
* sudo mount -o /sys /root/debian_live/chroot/sys
* sudo mount -o /run /root/debian_live/chroot/run

* sudo chroot $HOME/debian_live/chroot
* echo "debian-live" > /etc/hostname
* echo 'deb https://ftp.it.debian.org/debian/ stretch main contrib non-free' > /etc/apt/sources.list
* apt update

## Installazione kernel:

``` apt-cache search linux-image```
``` apt install -y linux-image-4.9.0-4-amd64 linux-headers-4.9.0-4-amd64 ```

## Installazione dei pacchetti personalizzat

Password per root:

Comprimere il tutto in uno squash filesystem:

Copiare kernel e initramfs fuori chroot:

Preparazione chiavetta usb: (nel mio caso /dev/sda di 16G)


+ 0
- 124
documents/proxmox-ve.md View File

@@ -1,124 +0,0 @@
# Proxmox ve

Non è semplice per me descrivere Proxmox VE, vi lascio alla loro [presentazione](https://pve.proxmox.com/wiki/Main_Page) ed alla loro [guida](https://pve.proxmox.com/pve-docs/pve-admin-guide.html), non prima però di aver spiegato che è l'unica tecnologia di virtualizzazione che ho utilizzato in questi anni.

Diciamo che fornisce un servizio di virtualizzazione, come vmware o virtualbox, gestibile sia in locale che attraverso il web. L'indirizzo del sito è https://node-della-macchina-o-ip:8006

Da questo, interamente con interfaccia grafica, è possibile creare, cancellare, gestire le macchine virtuali.

Solo una nota, installate - se potete - proxmox ve su una macchina con almeno 4 GB di RAM, preferibilmente 8 GB o 16 per un utilizzo "reale" e per poter assegnare alle macchine virtuali un conguo spazio di memoria 2/4 GB di RAM.


## Installazione

``ATTENZIONE:`` L'utilizzo dell'installazione da CLI con il comando ```sudo eggs hatch``` è distruttivo, nel senso che cancellerà completamente il vostro disco rigido.


Per installare LMDE+Proxmox VE utilizzare il comando ```eggs hatch``` (tenuto conto di quanto riportato sopra) che creerà su /dev/sda:

* una partizione LVM (```/dev/sda2```);
* un gruppo di volumi di nome penguin e tre differenti device:
* ```/dev/penguin/root``` partizione di root (formattata ext4);
* ```/dev/penguin/data``` partizione mountata sotto /var/lib/vz (formattata ext4);
* ```/dev/penguin/swap``` partizione di swap.

Inoltre, in /dev/sda1 verrà creata una piccola partizione di boot per l'avvio del sistema.

### Networking
Nel corso dell'installazione, verranno poste alcune domande ed opzioni, ad esempio nome utente, password utente, password root, etc. Accettare SEMPRE i valori di default.

Per quanto riguarda la rete, a fine installazione, si potrà modificare il tutto copiando il presente file in /etc/network/interfaces, avendo cura di inserire gli indirizzi adeguati alla propria rete.

```
iface enp0s31f6 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.61.2
netmask 255.255.255.0
gateway 192.168.61.1
bridge-ports enp0s31f6
bridge-stp off
bridge-fd 0

```
### Sistemazione dei log di pveproxy
Per qualche ragione, non viene creata in /var/log/pveproxi la directory dove il daemon possa registrare i log e, di conseguenza, l'avvio del servizio fallisce. E' possibile sistemare il tutto con le seguenti istruzioni:

```sudo mkdir /var/log/pveproxy```

```sudo touch /var/log/pveproxy/access.log```

```sudo chown www-data:www-data /var/log/pveproxy -R```

```sudo chmod 0664 /var/log/pveproxy/access.log ```

e riavviare il servizio.

```sudo service pveproxy restart```

### Password di root

Ricordarsi, se non è stata assegnata una password di root precedentemente, di assegnarla. Altrimenti non ci si potrà loggare sull'interfaccia grafica.


## Proxmox VE - Una vecchia presentazione

Il giorno 22 marzo 2017 è stata rilasciata la prima beta di Proxmox VE 5 basata su Debian Stretch. Oggi il 28 aprile approfittando del fatto di dover fare pulizia sull’installazione domestica ho deciso di tentarne l’installazione tanto per anticiparmi e scoprire le novità.

Ci sono stati alcuni problemi, il primo è che occorre partire da un disco pulito oppure scegliere, come ho fatto l’installazione zfs, dopo di questo e, sino a questo momento tutto sta procedendo regolarmente, visto che sto scrivendo dallo stesso computer.

Ho iniziato il passaggio rimuovendo le macchine virtuali non più utilizzate e, quindi salvandomi le altre man mano su un disco esterno. Proxmox utilizza per il backup il nome vzdum-quemu-XXX-AAAA-MM-GG.vma.lz, per non confondermi ho ridenominato i vari dump con il [NomeMacchina]-vzdump… etc.

Finito il backup che, ha richiesto un certo lasso di tempo, ho provveduto a scaricare la iso di proxmox ed a riversarla su una chiavetta usb per avviare l’installazione.

sudo su

dd if=proxmox…iso of=/dev/sdb;sync

Attenzione naturalmente a sceglie il giusto /dev, nel mio caso /dev/sdb, altrimenti si rischia di cancellare tutto.

Finita la registrazione dell’immagine sulla chiavetta, possiamo senz’altro partire con l’installazione, di per sè molto semplice e comunque asssistita da grafica. Le cose da scegliere riguardano essenzialmente la formattazione del disco, nel mio caso ho optato per zfs – ma questo perchè non avevo provveduto a cancellare a priori il disco, altrimenti avrei potuto scegliere LVM2 con una partizione ext4, modalità alla quale sono più abituato. Non sono pentito al momento di zfs, qualche tempo mi fa dava dei problemi con il boot e per questo avevo iniziato a non utilizzarlo. Direi che al momento va bene e, l’impressione è un aumento delle prestazioni.

Aggiunta dell’interfaccia grafica, utenti e degli strumenti desktop
Una volta riavviato, abbiamo una bella distribuzione Debia Stretch nuova, nuova e con Proxmox installato, ma ahimè accedibile solamente da un’altra macchina in rete. Con scelta comprensibile, perchè parliamo di un virtualizzatore la sola interfaccia disponibile è la riga di comando o l’interfaccia web per la gestione. Naturalmente, per una installazione domestica o per sviluppo, questo è improponibile andremo quendi ad installare una GUI, ho scelto cinnamon-core ed un desktop manager lightdm.

Per prima cosa aggiorniamo le repository:

```apt-get update```

```apt-get install lightdm cinnamon-core```

Una volta installato il desktop manager e l’ambiente grafico, possiamo crearci un utente con i diritti di amministrazione che utilizzeremo normalmente, invece di root.

```adduser artisan```

```addgroup sudo artisan```

A questo punto, possiamo riavviare la macchina e loggarci direttamente, nellìambiente grafico con artisan. Per fare operazioni di sistema utilizzeremo sudo.

Manca ancora un browser, anzi due, visto che normalmente utilizzo sia firefox che google chrome. Andiamo ad installare Firefox, nella versione firefox-esr per Debian

```apt-get install firefox-esr```

Una volta installato firefox, possiamo utilizzarlo per scaricarci le altre applicazioni scelte. Nel mio caso atom come editor e Google Chrome come browser.

Scaricati i pacchetti, andiamo ad installarlo con il comendo dpkg -i nome pacchetto.

```dpkg -i```

Per il ripristino che sto effettuando mentre scrivo queste note, la procedura è:

```qmrestore cholitos- -s local-zfs cholitos-bk-vzdump-qemu-104-2017_04_28-13_15_17.vma.lzo```

a qyesto punto, controllato che la macchina funzioni, provvedo a cancellare il dump.

Attenzione, una volta creato un disco zfs, se per qualche ragione, come mi è successo poco fa è necessario cancellarlo singolarmente, dobbiamo intervenire con zfs

```zfs destroy rpool/data/vm-100-disk-1```

```zfs destroy rpool/data/vm-100-disk-2```

A questo punto possiamo riprendere l’importazione precedente che abbiamo abortito, senza avere la costruzione di un data/vm-100-disk-3 ed andando a recuperare lo spazio occupato dalle immagini parziali precedenti.

Finalmente, stiamo caricando l’ultima macchina

+ 1
- 3
eggs View File

@@ -1,3 +1 @@
npm run build
sudo node lib/index.js $1

./bin/run $1 $2 $3 $4 $5 $6 $7 $8

+ 2707
- 2712
package-lock.json
File diff suppressed because it is too large
View File


+ 60
- 56
package.json View File

@@ -1,66 +1,70 @@
{
"name": "penguins-eggs",
"version": "7.0.82",
"author": "Piero Proietti",
"mail": "piero.proietti@gmail.com",
"description": "remaster your system and distribuite it by ISO or via PXE",
"license": "MIT",
"homepage": "http://pieroproietti.github.io",
"repository": {
"type": "git",
"url": "https://github.com/pieroproietti/penguins-eggs"
"description": "remaster your system and distribuite it",
"version": "7.1.0",
"author": "Piero Proietti @pieroproietti",
"bin": {
"eggs": "./bin/run"
},
"bugs": "https://github.com/pieroproietti/penguins-eggs/issues",
"dependencies": {
"@oclif/command": "^1.5.19",
"@oclif/config": "^1.14.0",
"@oclif/plugin-help": "^2.2.3",
"@types/shelljs": "^0.8.6",
"drivelist": "^8.0.9",
"pjson": "^1.0.9",
"shelljs": "^0.8.3",
"tslib": "^1.10.0"
},
"devDependencies": {
"@oclif/dev-cli": "^1.22.2",
"@oclif/test": "^1.2.5",
"@types/chai": "^4.2.8",
"@types/drivelist": "^6.4.1",
"@types/mocha": "^5.2.7",
"@types/node": "^10.17.14",
"chai": "^4.2.0",
"eslint": "^5.16.0",
"eslint-config-oclif": "^3.1.0",
"eslint-config-oclif-typescript": "^0.1.0",
"globby": "^10.0.2",
"mocha": "^5.2.0",
"nyc": "^14.1.1",
"ts-node": "^8.6.2",
"typescript": "^3.7.5"
},
"engines": {
"node": ">=8.0.0"
},
"files": [
"/bin",
"/lib",
"/npm-shrinkwrap.json",
"/oclif.manifest.json"
],
"homepage": "https://github.com/pieroproietti/penguins-eggs",
"keywords": [
"remastering",
"pxe-server",
"pxe-boot",
"iso",
"backup",
"systemback"
"oclif"
],
"bin": {
"eggs": "./lib/index.js"
"license": "MIT",
"main": "lib/index.js",
"oclif": {
"commands": "./lib/commands",
"bin": "eggs",
"plugins": [
"@oclif/plugin-help"
]
},
"main": "./src/index.ts",
"repository": "pieroproietti/penguins-eggs",
"scripts": {
"start": "ts-node src/index.ts",
"produce": "ts-node src/index.ts produce -d eggs -b debian",
"info": "ts-node src/index.ts info",
"calamares": "ts-node src/index.ts calamares",
"kill": "ts-node src/index.ts kill",
"create": "npm run build",
"docs": "rm docs -rf && npx typedoc src --out docs",
"build": "tsc -p .",
"refresh": "rm -rf ./node_modules ./package-lock.json && npm install"
},
"dependencies": {
"commander": "^3.0.1",
"date-fns": "^1.29.0",
"drivelist": "^5.2.12",
"inquirer": "^5.2.0",
"io": "^0.1.10",
"ip": "^1.1.5",
"js-yaml": "^3.13.1",
"netmask": "^1.0.6",
"network": "^0.4.1",
"pjson": "^1.0.9",
"shelljs": "^0.8.2",
"xml2js": "^0.4.22"
"postpack": "rm -f oclif.manifest.json",
"posttest": "eslint . --ext .ts --config .eslintrc",
"prepack": "rm -rf lib && tsc -b && oclif-dev manifest && oclif-dev readme",
"test": "nyc --extension .ts mocha --forbid-only \"test/**/*.test.ts\"",
"version": "oclif-dev readme && git add README.md"
},
"config": {
"unsafe-perm": true
},
"devDependencies": {
"@types/inquirer": "0.0.41",
"@types/ip": "0.0.30",
"@types/js-yaml": "^3.12.1",
"@types/netmask": "^1.0.30",
"@types/node": "^12.7.5",
"@types/shelljs": "^0.7.9",
"@types/source-map-support": "^0.4.2",
"ts-loader": "^4.5.0",
"nodemon": "^1.18.7",
"ts-node": "^7.0.1",
"tslint": "^5.11.0",
"typescript": "^3.6.3"
}
"types": "lib/index.d.ts"
}

+ 0
- 3
scripts/disk_get_size.sh View File

@@ -1,3 +0,0 @@
#!/bin/bash
get_size_dev=`parted -s $1 unit b print free | grep Free | awk '{print $3}' | cut -d "M" -f1`
echo $get_size_dev

+ 0
- 6
scripts/disk_prepare.sh View File

@@ -1,6 +0,0 @@
#!/bin/bash
#
# parameter: $1 device example: /dev/sda
#
lvremove pve
parted --script $1 mklabel msdos

+ 0
- 7
scripts/disk_prepare_partition_boot.sh View File

@@ -1,7 +0,0 @@
#!/bin/bash
#
# parameter: $1 partition example: /dev/sda
#
parted --script $1 mkpart primary ext4 1 512
parted --script --align optimal $1 set 1 boot on
sleep 1

+ 0
- 8
scripts/disk_prepare_partition_lvm.sh View File

@@ -1,8 +0,0 @@
#!/bin/bash
#
# parameter: $1 partition example: /dev/sda $2 size in mb
# example: scripts/partition_prepare_lvm.sh /dev/sda 68719
#parted --script --align optimal $1 mkpart primary ext2 512 $2
parted --script --align optimal $1 mkpart primary ext2 512 100%
parted --script $1 set 2 lvm on
sleep 1

+ 0
- 56
scripts/disk_prepare_pve.sh View File

@@ -1,56 +0,0 @@
#!/bin/bash
#
# parameter: $1 disk example: /dev/sda
#
LVM_PARTNAME=`fdisk $1 -l | grep 8e | awk '{print $1}' | cut -d "/" -f3`
LVM_SIZE=`cat /proc/partitions | grep $LVM_PARTNAME| awk '{print $3}' | grep "[0-9]"`
echo "LVM_SIZE=$LVM_SIZE"
LVM_SIZE=$(($LVM_SIZE/1024))
echo "LVM_SIZE=$LVM_SIZE"

PENGUIN_SWAP="/dev/penguin/swap"
PENGUIN_ROOT="/dev/penguin/root"
PENGUIN_DATA="dev/penguin/data"

# La partizione di root viene posta ad 1/4 della partizione LVM.
# Viene limitata fino ad un massimo di 100 GB

LVM_SWAP_SIZE=$((4*1024))
echo "LVM_SWAP_SIZE=$LVM_SWAP_SIZE"

LVM_ROOT_SIZE=$(($LVM_SIZE/8))
LVM_ROOT_SIZE_MINIMUN=20480
if [ $LVM_ROOT_SIZE -le $LVM_ROOT_SIZE_MINIMUN ]; then
LVM_ROOT_SIZE=$LVM_ROOT_SIZE_MINIMUN
fi
echo "LVM_ROOT_SIZE=$LVM_ROOT_SIZE"

LVM_DATA_SIZE=$(($LVM_SIZE-$LVM_SWAP_SIZE-$LVM_ROOT_SIZE))
echo "LVM_DATA_SIZE=$LVM_DATA_SIZE"

LVM_DATA_SIZE=$(($LVM_SIZE-$LVM_SWAP_SIZE-$LVM_ROOT_SIZE))
echo "LVM_DATA_SIZE=$LVM_DATA_SIZE"
GB=1048576
GB=1024

echo "LVM_SIZE=$(($LVM_SIZE/$GB)) GB, $LVM_SIZE"
echo "LVM_SWAP_SIZE=$(($LVM_SWAP_SIZE/$GB)) GB, $LVM_SWAP_SIZE"
echo "LVM_ROOT_SIZE=$(($LVM_ROOT_SIZE/$GB)) GB, $LVM_ROOT_SIZE"
echo "LVM_DATA_SIZE=$(($LVM_DATA_SIZE/$GB)) GB, $LVM_DATA_SIZE"


echo "pvcreate /dev/$LVM_PARTNAME"
echo "vgcreate penguin /dev/$LVM_PARTNAME"
echo "vgchange -an"
echo "lvcreate -L $LVM_SWAP_SIZE -nswap penguin"
echo "lvcreate -L $LVM_ROOT_SIZE -nroot penguin"
echo "lvcreate -l 100%FREE -ndata penguin"
echo "vgchange -a y penguin"

pvcreate /dev/$LVM_PARTNAME
vgcreate penguin /dev/$LVM_PARTNAME
vgchange -an
lvcreate -L $LVM_SWAP_SIZE -nswap penguin
lvcreate -L $LVM_ROOT_SIZE -nroot penguin
lvcreate -l 100%FREE -ndata penguin
vgchange -a y penguin

+ 0
- 39
scripts/hatch_exclude.list View File

@@ -1,39 +0,0 @@
# install/hatch rsync excludes file

- /dev/*
- /cdrom/*
- /media/*
- /TARGET
- /swapfile
- /mnt/*
- /sys/*
- /proc/*
- /tmp/*
- /live
- /boot/grub/grub.cfg
- /boot/grub/menu.lst
- /boot/grub/device.map
- /etc/udev/rules.d/70-persistent-cd.rules
- /etc/udev/rules.d/70-persistent-net.rules
- /etc/fstab
- /etc/fstab.d/*
- /etc/mtab
- /etc/PolicyKit/PolicyKit.conf
- /var/lib/dbus/machine-id
- /var/lib/polkit-1/localauthority/10-vendor.d/10-live-cd.pkla
- /etc/PolicyKit/PolicyKit.conf
- /etc/popularity-contest.conf

# Added for newer version of live-config/live-boot
# in sid (to become Jessie)
- /lib/live/overlay
- /lib/live/image
- /lib/live/rootfs
- /lib/live/mount
- /run/*

# Added for symlink /lib
- /usr/lib/live/overlay
- /usr/lib/live/image
- /usr/lib/live/rootfs
- /usr/lib/live/mount

+ 0
- 9
scripts/is_calamares.sh View File

@@ -1,9 +0,0 @@
#!/bin/bash
IS_CALAMARES=$(dpkg -l|grep calamares)
if [[ -z $IS_CALAMARES ]]; then
echo "0"
else
echo "1"
fi



+ 0
- 10
scripts/is_live.sh View File

@@ -1,10 +0,0 @@
#!/bin/bash
#
# parameter: none
#
IS_LIVE=$(ls /lib/live|grep mount)