I updated the manual today - only in italian and english, brasilianautomatic and revised translation - and tried for the first time eggs with Ubuntu groovy gorilla. It seems to be going apart from a little problem with the calamares displaymanager module that at the moment I simply removed. (It only serves to manage the possible autologin).
I tested the day realease on a UEFI machine, both iso production and install the system.
Eggs of course is not a package that is part of a distribution, moreover it is still relatively young. Waiting for it to end up in a repository would be long - not so much in truth - is present in the repository of ufficiozero.org, why not think about an autoupdate through this site?
It would be enough to provide the package with the list of versions, the text of the changelog to allow the user to decide and the download url.
It shouldn’t be too difficult, nodejs is used for this purpose.
The idea, therefore, is to create a microservice that queries, provides:
Does anyone want to cooperate? Any suggestions? contact me
Lately, before releasing version 7.6.47-1, I had a strong but constructive discussion with one of my users. I noticed that they tend not to trust software in general and eggs in particular, due to the numerous versions and the lack of knowledge of its mysteries.
The main reason is the lack of understanding of what happens behind the scenes. I decided, therefore, to rewrite more clearly what happens during the installation and removal of prerequisites. It is, in fact, nothing magical, but only a series of apt install or apt remove, the various software that serve as eggs for its operation.
I still have some problems, but you will see in detail the operations performed.
Not always I have time to update this site, but the last versions, expecially 7.48.1 are well tested and working, so I think it’s better to present them.
added a beutifull new theme for ufficiozero thanx to Julian Del Vecchio.
changed flags in produce and calamares. just added flag –final to make the final version of your project: all the packages relative to the “reproduction” will be removed during the installation with the gui installer; module packages in calamares now work in accord with the flag –final, if present will build the remove section in packages.conf (you can check this file in /etc/calamares/modules) if not, only section try-install will be build. This section is ideal for international packages, languages, etc.
buxfix: there was a little problem with links in the previus version.
improvement: patch per bionic in calamares module grubcf, added check plymouth from successive version of calamares (in bionic calamares is quite old and not mantained); improvment: actually is possible to use directly produce after the installation, eggs will propose the necessary operations to install prerequisites, calamares and so on; bugfix: the previous version I put distro.versionId as productName in calamares, but due the fact who was used ad EFI name too, Debian refuse to boot. So I changed in branding.ts the line bootloaderEntryName=productName to bootloaderEntryName = distro.distroId.
I resolved a lot of bugs, from the previos release 7.6.34.
This is an important version, in which a lot of work is completed, the reasons are the following:
Just finished the rewriting work. Well now we have officially Debian buster, Devual beowulf, Ubuntu focal and Ubuntu bionic fully supported, both for standard BIOS installation and UEFI installation, both on i386 and amd64 architecture.
Of course it follows that other derived distros can also be easily remastered: Linux Mint 20.20, Linux Mint 19.3, etc.
I also tried Deepin 20, which works perfectly, but only on standard BIOS machines
UfficioZero is in the process of adopting Penguin’s eggs as a tool for creating its own Debian and Devuan-based systems.
We are very proud with UfficioZero’s staff of the new collaboration that will allow us both to grow, and is also the first time that eggs will be included in an official repository.
This is a short presentation of UfficioZero Linux, but I recommend you to follow their site.
UfficioZero Linux is an open source operating system designed by SIITE SRLS, which has acquired the historical domain and provides various virtual servers to host web services, mail services, repositories and sharing servers for the development team.
The project is aimed at freelancers, professionals, private and state agencies who want to use a free, useful and easy to understand tool.
Currently Office Zero Linux comes in three versions:
Ufficio Zero Linux codename Roma 2.0.1 for pc with 32bit processor, based on Devuan 3 Beowulf and with desktop manager Xfce
Office Zero Linux codename Mantova 2.0.1 for pc with 64bit processors, based on PCLinuxOS and with desktop manager Mate
Office Zero Linux codename Vieste 2.0.1 for pc with 64bit processor, based on Linux Mint 19.3 and with desktop manager Mate
Eggs compatible with Debian 10, Ubuntu 20.20, Ubuntu 18.04, Linux Mint 20 and Linux Mint 19.3
At the beginning of June, after a Brazilian magazine sempreUpdate reviewed eggs, I had pleasure but also a bit of fear. The article suggested to use eggs both to make your own Linux version on modern comuters and to run old pc (i386). So in order to try to satisfy the intentions and the users, I set to work to make eggs usable again on i386. So now eggs allows you to remaster your system to 32 or 64 bits and, not only that, you can use the graphical installer calamares both for Debian Buster and on all the following distributions and derivatives:
Ho scelto di installare nodebb come motore per il forum del sito. La ragione della scelta è stata soprattutto l’eventuale possibilità di integrazione con il blog che è sempre basato su nodejs.
I prequisiti sono ovviamente nodejs, mongo come database ed un proxy nginx o apache2.
Per prima cosa ho dovuto installare mongodb, il database che sta dietro la maggioranza dei siti realizzati con nodejs, un po’ come mysql è dietro lampp. Magari sarebbe il caso di creare qualche altro acronimo!
SSLEngine on # This directory contains your keys and certificates.
# `privkey.pem` : the private key for your certificate. # `fullchain.pem`: the certificate file used in most server software. # `chain.pem` : used for OCSP stapling in Nginx >=1.3.7. #`cert.pem` : will break many server configurations, and should not be used # without reading further documentation (see link below).