re-installing t470p, and updating along the way

This commit is contained in:
committer@tuxwarrior
2026-03-13 16:42:08 -05:00
parent 0b1819a486
commit d6c438cb89

View File

@@ -40,7 +40,7 @@ Primary key fingerprint: 3E80 CA1A 8B89 F69C BA57 D98A 76A5 EF90 5444 9A5C
- boot the target system using the arch iso, and prepare for a [guided install](https://archinstall.archlinux.page/installing/guided.html) - boot the target system using the arch iso, and prepare for a [guided install](https://archinstall.archlinux.page/installing/guided.html)
- tuxwarrior: `F2` for BIOS - tuxwarrior: `F2` for BIOS
- thinkpad: `F12` for boot options (`F1` for BIOS) - t470p: `Enter` for boot options (`F2` or `F10` or `F12` for other options)
- select `ArchLinux install medium (x86_64, x64 UEFI)` - select `ArchLinux install medium (x86_64, x64 UEFI)`
- troubleshooting - troubleshooting
- grub error - grub error
@@ -64,32 +64,30 @@ please note, this step is only needed when arch is to be installed on a new host
- keyboard `us` - keyboard `us`
- loc lang `en_AU.UTF-8` - loc lang `en_AU.UTF-8`
- loc enc `UTF-8` - loc enc `UTF-8`
- mirrors and repositories ➔ `colombia`, `united states`, `worldwide` - mirrors and repositories ➔ select regions ➔ `colombia`, `united states`, `worldwide`
- (Optional repositories ➔ leave blank (default)) [obsolete?] - (Optional repositories ➔ leave blank (default)) [obsolete?]
- disk config ➔ partitioning ➔ use a best-effort default partition layout ➔ pick main hd ➔ `ext4` ➔ separate partition for /home: `no` - disk config ➔ partitioning ➔ use a best-effort default partition layout ➔ pick main hd ➔ `ext4` ➔ separate partition for /home: `no`
- bootloader ➔ `systemd-boot` (default) [might not be in the right order]
- (disk encryption ➔ `no` (default)) [obsolete?]
- swap: `True` (default) - swap: `True` (default)
- unified kernel image: `Disabled` (default) - bootloader ➔ `systemd-boot` (default)
- hostname: `tuxwarrior` - kernels: `Linux` (default)
- root password: leave blank (default) - hostname: `tuxwarrior` / `t470p`
- user account: leave empty (default) - authentication: do nothing
- profile ➔ type ➔ `minimal` - profile: do nothing (previously `➔ type ➔ `minimal`)
- audio ➔ `pipewire` - applications: do nothing
- kernels ➔ `linux` (default) - network configuration ➔ `Use NetworkManager (default backend)`
- network configuration ➔ `Use NetworkManager`
- additional packages ➔ `git nano tree wget` - additional packages ➔ `git nano tree wget`
- `/` to search - `/` to search
- timezone ➔ `America/Panama` - timezone ➔ `America/Panama`
- automatic time sync ➔ `True` (default) - automatic time sync ➔ `Enabled` (default)
- ---
- ➔ Save configuration - ➔ Save configuration
- ➔ Save user configuration (inc disk layout) - ➔ Save user configuration (including disk layout)
- Save directory: `/tmp``yes` ➔ answer `no` when asked if you want to encrypt - Save directory: `/tmp``yes` ➔ answer `no` when asked if you want to encrypt
- then `abort` to exit archinstall - then `abort` to exit archinstall
- `curl -F'file=@user_configuration.json' https://0x0.st` - `curl -F'file=@user_configuration.json' https://0x0.st`
- on **existing host / alternative host**: - on an **alternative computer**:
- for this repo, inside `dots/archinstall` create folder for new host (use hostname as folder name) - for this (`lnx-arch`) repo, inside `dots/archinstall` create folder for new host (use hostname as folder name)
- open page given above, like `https://0x0.st/Xbov.json` - open page given as a result from the above curl commend (like `https://0x0.st/Xbov.json`)
- save raw content as `user_configuration.json` - save raw content as `user_configuration.json`
- save file - save file
- from a pre-existing host directory, copy over and modify (if needed) `options.sh`, `packages.txt` and `services.txt`. this should be copied to new host directory - from a pre-existing host directory, copy over and modify (if needed) `options.sh`, `packages.txt` and `services.txt`. this should be copied to new host directory
@@ -120,13 +118,12 @@ please note, this step is only needed when arch is to be installed on a new host
- check datestamp shown at the end when running the script [260225_comment: why?] - check datestamp shown at the end when running the script [260225_comment: why?]
- `archinstall --config user_configuration.json --creds user_credentials.json` - `archinstall --config user_configuration.json --creds user_credentials.json`
- Install - Install
- ➔ Would you like to chroot into ... perform post-installation config? - takes about six minutes
- `no`
- `reboot` - `reboot`
## step five :: setup dot files and install software ## step five :: setup dot files and install software
- note: it might be handy to comment out ALL packages in `packages.txt`, and only be installing one package at a time. this way obsolete packages, no longer needed, will not be installed on the new system - note: it might be handy to comment out ALL packages in `packages.txt`, and only be installing one package at a time. this way packages no longer needed will not be installed on the "fresh host"
- log in as `poq` - log in as `poq`
- `nmtui` (activate internet connection) - `nmtui` (activate internet connection)
- set up ct (caretaker - system management tool) - set up ct (caretaker - system management tool)
@@ -138,45 +135,53 @@ please note, this step is only needed when arch is to be installed on a new host
- `sudo ct yay` (install yay, which is used to install aur packages) - `sudo ct yay` (install yay, which is used to install aur packages)
- `sudo ct uf` (full update, install packages) - `sudo ct uf` (full update, install packages)
- same as running the two commands `sudo ct s` (software) and `sudo ct d h` (dots inc hyprland cfg) - same as running the two commands `sudo ct s` (software) and `sudo ct d h` (dots inc hyprland cfg)
- note that depending on your internet speed this operation can take a lot of time. often longer than an hour (two-three hours at skogro).
- `sudo ct dots+` (download wallpapers, fonts++) - `sudo ct dots+` (download wallpapers, fonts++)
- loop install - until all programs are successfully installed, as i have experiences not all being installed at once - loop install - until all programs are successfully installed (unfortuantely, all packages does not get install the first time around. reason unknown.)
- note that some packages (in `packages.txt`) might have to be removed, as they might no longer be active / be working
- `sudo ct s` - `sudo ct s`
- note: normally two loops / extra installs (in addition to the main `ct uf`) is needed
- note that some packages (in `packages.txt`) might have to be removed, as they might no longer be active / be working
- `sudo ufw enable` (enable firewall) - `sudo ufw enable` (enable firewall)
- `reboot` & re-login - `reboot` & re-login
- `hypr.sh` (start hyperland) - `hypr.sh` (start hyperland)
- several windows will start - several windows will start
- in the background there might will be a window where you are asked to set password for the gnome keyring - (SEEMS OBSOLETE: if it pops up a window where you are asked to set password for the gnome keyring:)
- the gnome keyring window will always be in focus, and there is no way to close the other windows while this is happening - (the gnome keyring window will always be in focus, and there is no way to close the other windows while this is happening)
- press `escape` to close the keyring window - (press `escape` to close the keyring window)
- ignore the pCloudDrive, Nextcloud and other windows - ignore the pCloudDrive, Nextcloud and other windows
- switch to a new workspace, like workspace 2, and start a terminal
- run `firstBoot.sh` - run `firstBoot.sh`
- this will start and close librewolf, for having the browser's profile directory being created, as well as creating a directory for nextcloud - this will start and close librewolf, for having the browser's profile directory being created, as well as creating a directory for nextcloud
- error "Exiting due to channel error" will occure.
- `ct dots` (the re-run of dots will deploy librewolf settings) - `ct dots` (the re-run of dots will deploy librewolf settings)
- `ct services` (enable services) - `ct services` (enable services)
- `reboot` & re-login - `reboot` & re-login
- once again, press esc to close the gnome keyring window - (SEEMS OBSOLETE: once again, press esc to close the gnome keyring window, if it pops up)
- leave the other windows open - several programs start, that at this stage can be ignored
- set up nextcloud - set up nextcloud
- log in - log in
- using the credentials found at <https://vault.bitwarden.com/#/vault?folderId=aab7655a-38a5-4a6d-92e6-acdc00ff63b6> - using the credentials found at <https://vault.bitwarden.com/#/vault?folderId=aab7655a-38a5-4a6d-92e6-acdc00ff63b6>
- otp found in "ente auth" and pwd manager
- server address: `https://nx.op.fo` - server address: `https://nx.op.fo`
- at this point the gnome keyring manager will pop up again, and ask for a password - (OBSOLETE: at this point the gnome keyring manager will pop up again, and ask for a password)
- leave both (password and confirm) fields blank, and press continue, and chose to store passwords unencrypted - (leave both (password and confirm) fields blank, and press continue, and chose to store passwords unencrypted)
- _"To use automatic unlocking with automatic login, you can set a blank password for the default keyring. Note that the contents of the keyring are stored unencrypted in this case."_ - (_"To use automatic unlocking with automatic login, you can set a blank password for the default keyring. Note that the contents of the keyring are stored unencrypted in this case."_)
- https://wiki.archlinux.org/title/GNOME/Keyring - (https://wiki.archlinux.org/title/GNOME/Keyring)
- pick local folder `/home/poq/nextcloud` and - pick local folder `/home/poq/nextcloud` (notice: all lowercase letters!) and
- choose `Synchronize everything from server` and - choose `Synchronize everything from server` and
- disable the two options `Ask before syncing folders larger than xxx` and `Ask before syncing external storages` - disable the two options `Ask before syncing folders larger than xxx` and `Ask before syncing external storages`
- click `Connect` - click `Connect`
- wait for nextcloud to complete syncronisation - wait for nextcloud to complete syncronisation
- this will likely take some time. how long depends on the internet speed and the amount of data stored with nextcloud. - this will likely take several hours. exactly how long depends on the internet speed and the amount of data stored with nextcloud.
- when the sync is complete, continue with the next step - when the sync is complete, continue with the next step
## step six :: post syncronisation tasks ## step six :: post syncronisation tasks
- `syncDirSetup.sh` (will set up `~/syncDir`) - `syncDirSetup.sh` (will set up `~/syncDir`)
- `deploySshKeys.sh` (deployment of ssh keys) - `deploySshKeys.sh` (deployment of ssh keys)
<!><!><!> THIS CAN NOT WORK, AS WE ARE TRYING TO USE GPG BEFORE KEYS ARE INSTALLED. TO BE COPIED FROM CRYPTOMATOR? <!><!><!>
- `importGnupgKeys.sh` (deployment of gpg keys) - `importGnupgKeys.sh` (deployment of gpg keys)
- `gitReposSoftlinker.sh` (create softlinks to all repos at `~/syncDir/gitRepos/`) - `gitReposSoftlinker.sh` (create softlinks to all repos at `~/syncDir/gitRepos/`)
- `chmodAllSh.sh` (fixes mode change from 14001 to 217 errors in repo) - `chmodAllSh.sh` (fixes mode change from 14001 to 217 errors in repo)
@@ -281,7 +286,7 @@ please note, this step is only needed when arch is to be installed on a new host
- edit ➔ preferences > - edit ➔ preferences >
- layout ➔ show in places ➔ unselect all but "trash can" - layout ➔ show in places ➔ unselect all but "trash can"
- **REAPER** - **REAPER**
- ! UPDATE OF THIS SECTION IS NEEDED ! - ! AN UPDATE OF THIS SECTION IS NEEDED !
- NOTE: much of this can very likey be omitted, as the settings can be imported from: - NOTE: much of this can very likey be omitted, as the settings can be imported from:
- `/home/poq/syncDir/gitRepos/gitlab.com/dotsplus/reaper/config/` - `/home/poq/syncDir/gitRepos/gitlab.com/dotsplus/reaper/config/`
- --- - ---
@@ -325,7 +330,7 @@ please note, this step is only needed when arch is to be installed on a new host
- also located in protonmail under the 'licence' label - also located in protonmail under the 'licence' label
- extra: ? - extra: ?
- **PRINTING** - **PRINTING**
- ! UPDATE OF THIS SECTION IS NEEDED ! - ! AN UPDATE OF THIS SECTION IS NEEDED !
- remove services cups.socket and cups.path - remove services cups.socket and cups.path
- `$ sudo systemctl disable cups.path` - `$ sudo systemctl disable cups.path`
- `$ sudo systemctl disable cups.socket` - `$ sudo systemctl disable cups.socket`