I tried Manjaro after not understanding enough about building Armbian. I am new to both. Been around Linux since 1.2.13 came out. Been around UN*X since 1984.
I have a 1TB NVMe SSD (Intel 660p ?) in the PBP (Pinebook Pro) that I eventually want to use as the device/partition that is my root filesystem. I am not in a hurry.
The biggest annoyance has been the USB/ethernet dongle that I got with my Pinebook Pro. I gather it is going into suspend mode to save energy, and never comes back. I've tried blacklisting in /etc/default/tlp, in /etc/udev/rules.d and both. I've called the product a 8152 and a 8153 (and had rules for both), and while I can get the ethernet to stay up longer, it does eventually die. Someone created a bash script to toggle some command states which I used for the most part. It makes use of the nmcli (?) command. To run the script, it never returns to a prompt. Appears to hang on the nmcli command. I've never used the nmcli command and never looked for a man page.
But for the moment, if I boot, I can use the ethernet enough to do some things like install or update software.
I can understand that not everyone like emacs, but there are times where the psychoanalyst is needed. Emacs is not perfect, I have never run across emacs doing coffee properly.
No vi/vim surprised me.
I have done some package addition/update, and had the machine refuse to boot, so I started again. I have also done an update, and I am hoping things boot.
Being a dinosaur, I like to use multiple partitions to compartmentalize problems. On my NVMe, I have /, /tmp, /usr, /usr/local, /var, /var/log and /home. I've been using rsync to keep the NVMe in sync with the microSD (64GB, so lots of room for now).
This latest upgrade attempt, flashed a couple of messages about uboot, and I tracked down a log file for pacman which allowed me to see those messages again. I gather I probably don't have to copy the two uboot files to offsets in the 30 or so MB of (supposedly) unused space at the beginning of the microSD. The message to me is a little ambiguous, in that it could either be talking about the microSD device, or if "X" is allowed to be multiple characters, to the first partition of that device. Maybe nobody else gets this?
I ran gdisk -l /dev/mmc... (whatever it is for a microSD, sorry I haven't memorized it yet), and gdisk comes back and says there is a 33 block overlap between the end of the filesystem on the microSD, and the spare partition table stored at the end of the device.
I wasn't sure what the messages about uboot were, so I remounted and rsynced things, and I was going to append the partition names, devices, labels and UUIDs to etc/fstab. Just in case what needed to be done with uboot (which as mentioned above, probably doesn't) might also involve this new boot device (in the future). But, the message was just a couple of dd copies, and I never did them. But, I noticed that etc/fstab is empty.
I can see that uboot can provide the device for the root filesystem (and maybe the filesystem for the kernel, which I normally see in /boot as partition on its own). And lots of people only run single partition Linux systems. Should I fill in etc/fstab on the NVMe in preparation for booting to the NVMe in the future?