Jump to content

danboid

Members
  • Posts

    68
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for that c0rnelius! I was unaware that u-boot (probably still) doesn't support BTRFS subvols. Hopefully they can add that so we'd be able to avoid the extra boot partition. I will look into that today. EDIT It looks like it does have subvol support : https://github.com/u-boot/u-boot/blob/master/fs/btrfs/subvolume.c
  2. Under Ubuntu when you install using BTRFS and Debian when you install to BTRFS using the Calamares live GUI installer, both installers create a subvolume called @home for the /home directory and another subvol called @ for the rest of the filesystem. This layout enables users to use timeshift to easily (and automatically with timeshift-autosnap-apt) create BTRFS snapshots and restore them using the command line or the timeshift GUI and restore their OS whilst optionally keeping users files stored under /home intact. I would like to see the armbian installation script configure BTRFS in this same manner.
  3. I wpouldn't want Armbian to do anything because Ubuntu is. I'm moving away from Ubuntu after 22.04 because Canonical are turning more apps into snaps which is destroying performance. I don't care about sandboxing or any other supposed benefit of snaps - having to wait 10x longer for apps to load is not acceptable.
  4. I know Ubuntu uses netplan by default but I prefer NetworkManager. The files are easier to configure by hand than netplans awful yaml plus netplan doesn't have alternatives to nmtui, nmcli and the GUI app. Everything has to be done by hand with netplan.
  5. I'll give a good example of this causing a problem. I have an Armbian machine that only uses wifi. I set the wifi up using the included nmtui but there is an almost 2 minute boot delay caused by the default Armbian /etc/network/interfaces (ifupdown) config for eth0. Remove or comment this config and Armbian boots almost 2 minutes faster if eth0 isn't connected at boot.
  6. Why does Armbian include both include ifupdown AND NetworkManager by default? I'm not aware of anything that ifupdown can do that NM cannot and ifupdown doesn't have a TUI/GUI like NM so as far as I'm concerned ifupdown is just clutter that causes config clashes and boot delays. Isn't it time to strip ifupdown from Armbian? On a related note, I've never got any of the (ifupdown) network config options in armbian-config to work.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines