SystemDFree.org SystemDFree Mastodon Instanz SystemDFree PeerTube Instanz SystemDFree Mattermost Instanz SystemDFree SearX Instanz SystemDFree PrivateBin Instanz SystemDFree PrivateBin Instanz SystemDFree PrivateBin Instanz

0 Mitglieder und 1 Gast betrachten dieses Thema.

*

Daemon

  • Administrator
  • *****
  • 895
  • Geschlecht: Männlich
Project Trident benutzt nun Void
09. Januar 2020, 16:51:16
Zitat
The Project Trident team have published their second development snapshot which uses Void as its base. Past versions of Project Trident have been based on TrueOS and this new beta snapshot expands the features Trident can provide on its new base. "What is new since the alpha image? Boot environment support for fully-separate datasets and snapshot rollback for boot environments. This is provided by the new zfsbootmenu utility created by Zack Dykstra. It is only configured for EFI-based bootloader support. Legacy-boot systems cannot use boot environments at the present time. User accounts - A single user account is created at installation. For EFI-booted systems, this user home directory is encrypted. It is configured so that logging in to the user account also decrypts the dataset for that user. Logging out locks the user dataset. Encrypted datasets are not supported on legacy-boot systems. Encrypting any ZFS datasets breaks the ability for GRUB to support booting the ZFS pool. A new trident-mkuser utility has been created for making additional user accounts. This utility supports creating encrypted home directories and will be included later as part of the trident-core package. Installer changes... lots of them." Additional information on the new snapshot can be found in the project's release announcement
Quelle: https://www.distrowatch.com/?newsid=10788

Zitat
What is new since the ALPHA image?
  • Boot Environment support for fully-separate datasets and snapshot rollback for boot environments.
    • This is provided by the new zfsbootmenu utility created by Zach Dykstra. It is only configured for EFI-based bootloader support. Legacy-boot systems cannot use boot environments at the present time.
  • User accounts.
    • A single user account is created at installation.
    • For EFI-booted systems, this user home directory is encrypted. It is configured so that logging in to the user account also decrypts the dataset for that user. Logging out locks the user dataset.
    • Encrypted datasets are NOT supported on legacy-boot systems. Encrypting any ZFS datasets breaks the ability for GRUB to support booting the zfs pool.
    • A new “trident-mkuser” utility has been created for making additional user accounts. This utility supports creating encrypted home directories and will be included later as part of the “trident-core” package.
  • Installer changes… lots of them.
    • The network status detection routine has been overhauled and now works on networks that block “ping”.
    • Installation status is now properly detected (fail/success) with a menu option to browse the log file if one is available.
    • For EFI installs, rebooting after completing the installation automatically ignores the ISO and boots the installed system. This allows more time to remove the ISO install device after the real system is already running.
    • The installation logfile is copied over to the newly-installed system, to /var/log/trident-install.log.
    • To maintain a BSD-style system layout, the “home” dataset is mounted at /usr/home, and /home is a symlink to /usr/home.
    • The ZFS pool layout has been tweaked a bit after testing boot environment functionality.
    • Additional input checking has been integrated into the installer to help ensure successful installs.
    • The installer provides four different “levels” of installation. This governs which packages get installed and configured:
      • Void : Only the base-system from Void Linux and ZFS-related bootloader packages are installed.
      • Server : A CLI-based system with additional services and utilities installed from Project Trident (firewall, cron, autofs, wireguard, additional shells, etc.)
      • Lite Desktop : (Experimental) A minimal desktop installation with the Lumina desktop.
      • Full Desktop : (Experimental) A Lumina desktop install with additional end-user utilities (office suite, Telegram, multimedia apps, etc).
      • Note that installation levels provide pre-defined lists of packages to install for user convenience. The installed system can be easily be changed using the built-in package system.
Quelle: https://project-trident.org/post/void-beta-available/

Linkback: https://systemdfree.de/index.php?topic=531.0
I'm worse at what I do best and for this gift I feel blessed

*

Josef_K

  • Mitglied
  • ***
  • 51
  • Geschlecht: Männlich
Re: Project Trident benutzt nun Void
10. Januar 2020, 19:31:19
Dieses Lumina ist absolut nicht mein Fall und wenn ich Void will, dann nehme ich das Original  mit dem DE meiner Wahl.
Zitat
Wir installieren das aktuelle Lumina-Desktop-Paket von Void standardmäßig, und eine Sammlung von anderen Desktop-Paketen, aber keine der Trident-Dienstprogramme sind portiert oder noch nicht installiert.
Falls man sich dieses OS installieren will, dann muss man dafür eine ganze FP opfern:
Zitat
WARNUNG: Dieses Installationsprogramm erwartet, dass eine einzige, dedizierte Festplatte für die Installation bereitgestellt wird. Das Installationsprogramm löscht diese gesamte Festplatte und stellt sie wieder her, wobei alle auf der Festplatte gespeicherten Daten gelöscht werden.
https://project-trident.org/post/void-beta-available/

Aktuell Void und MX auf PC und Laptop