Just did a cli installation endeavour. I am missing the xfce default endeavour button in the welcome screen.
I am aware that i can install it from github, however it is easy to install from the welcome button.
Is it possible to re-enable the button ?
Just to clarify, there is no such thing as a CLI installation of EOS. If you manually install Arch or some other Arch-based distro and then add the endeavouros repo, what you are left with is different than a real EOS install because the installer creates files and does configuration.
You should expect things to be different than they would be with a real EOS install.
1 Like
Thanks dalto i know that, however when i install endeavour manually it is because i want to use btrfs with subvols and make a seperate zfs pool. I don’t know if calamares already has those options. Once setup i only need a minimal xfce desktop.
You can do this in Calamares, yes. If you want different subvols than the ones made by default, you can edit mount.conf and define whatever you want.
Do you need this as part of the install? If you do, it is possible to make Calamares do this but I would need more information to tell you how.
Seems you have done an Arch install using the 
ISO.
You can archive this by using the GUI installer and using the manual petitioner.
If you have pulled an Archway installation then you won’t get the logo in the XFCE menu button. If I’m correct you might have installed vanilla XFCE. You can get the image from here if you want.
@stormschip
I assume you are referring to the buttons that changed the Xfce theme to vanilla or EndeavourOS theme.
The underlying theming implementation has changed, and now we have package endeavouros-skel-xfce4 that makes the EndeavourOS theme for Xfce.
So, to change to Xfce vanilla, simply run command
rm -rf ~/.config/{xfce4,Thunar}
and reboot (or re-login).
Or, to change from vanilla to EndeavourOS Xfce theme:
rm -rf ~/.config/{xfce4,Thunar}
cp -r /etc/skel/.config/{xfce4,Thunar} ~/.config/
and reboot.
Note that if you have a previous theming with your changes, they will be deleted with the commands above. So if you want to save your changes, rename those folders instead of deleting them.
2 Likes
Information on what i am doing. In virtualbox i make a boot/efi 512M and a root of 50 GB.
also add three disks of 20 GB for the zfs pool. After booting eos iso from terminal
create partitions
cfdisk --zero /dev/sda
format filesystems btrfs and set subvols
mkfs.vfat /dev/sda1;mkfs.btrfs /dev/sda2
btrfs subvolume create .. all the subvols
pacstrap
pacstrap /mnt base base-devel
chroot
set time, locals, users, services and grub install
shutdown and boot from disk
check fstab
all subvols must have unique id and options defaults,discard=async,noatime,compress=zstd:3 except boot/efi umask=0077 0 0
get yay
git clone https://aur.archlinux.org/yay;cd yay/;makepkg -si PKGBUILD
sudo vim /etc/pacman.conf
[endeavouros]
SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist
configure zram with zram-generator
get timeshift
zfs arch kernel
sudo pacman -S --noconfirm zfs-dkms
zfs arch hook (arch wiki)
sudo mkdir /etc/pacman.d/hooks;sudo vim /etc/pacman.d/hooks/90-mkinitcpio-dkms-linux.hook
create zfs pool with three configured disks in VB
sudo zpool create <pool name> raidz1 -f /dev/sdb /dev/sdc /dev/sdd
create datasets
sudo zfs create <pool name>/<name dataset>
that is the basic arch configurtion
Desktop
git clone https://github.com/endeavouros-team/EndeavourOS-packages-lists.git;cd EndeavourOS-packages-lists
sudo pacman -S --needed - < xfce4
sudo pacman -S --noconfirm xfce4-systemload-plugin
sudo pacman -S --noconfirm xorg
sudo systemctl enable lightdm.service
Where are you mounting the zfs datasets?
enable zfs.target, zfs-import-cache, zfs-mount, zfs-import.target with systemctl and add the pool for automount
add pool for automount
sudo zpool set cachefile=/etc/zfs/zpool.cache <poolname>
Don’t know if you mean if i do anything with fstab, the answer is no
I mean where in the filesystem are you mounting the datasets.
I am creating a zfs pool named storage
sudo zpool create storage raidz1 -f /dev/sdb /dev/sdc /dev/sdd
sudo zfs create storage/data and whatever dataset you want.
Because of the pool i see them with a df -BG like this where backup paccache and data are datasets.
storage 38G 1G 38G 1% /storage
storage/backup 38G 1G 38G 1% /storage/backup
storage/paccache 39G 2G 38G 4% /storage/paccache
storage/data 38G 1G 38G 1% /storage/data
Hope you mean this ?
So it looks like the only thing the installer would care about is paccache. I guess you are symlinking that to /var/cache/pacman/pkg? (As a side note, it makes no sense to do this, just mount the zfs dataset to that location directly.)
You could use the installer in this case. You don’t really need zfs in place to do the install. You could run the installer to get your system setup on btrfs with whatever subvolumes you want and then add zfs post-install.
I am not symlinking the var/cache/pacman/pkg, just keeping one generation there and make a copy to the zfs /storage/paccache with a copy script for the three generations. The root filesystem is not growing too fast.
Will there be minimal future installations ISO’s for endeavourOS ?
Is there a possibility to test endeavourOS like manjaro does with testing and unstable repo’s ?
Just to help the developers ?
This morning i noticed that the default theming button returned in “welcome” so thanks to the developer who did this.
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.