Typically the user group is identical to the username but not always. For example a name containing uppercase letters may be transformed to be all lowercase for the user but contain both cases in the group.
Thus you should get the user group in scripting separate from $USER
Ubuntu is a fine “nice to meet you” distro – the criticisms I’ve gathered happen a few months in. Nvidia+Xorg updates dropping GUI to TUI, MDADM shitting the bed and dropping RAID, the awkward 6 month upgrades where you go from old weird issues in apps to new weird issues – thou snap and flatpak improve this a lot over stock.
Canonical NIH, Canonical CLA agreement, history of charging forward only to abandon in house tech over and again after users get comfy.
Then there are inner politics and the occasional hankyness inside, or discourteousness like when they shit the bed dropping lib32 without talking to partnrrs like Valve on how this would effect their business after they made Ubuntu their target.
Criticisms typically are based in something. I had started using Ubuntu since 2004 IIRC and its been an interesting ride.
Oh also, PPA’s, avoid those, they’re not stock and don’t be surprised if your OS doesn’t boot with the less than stellar ones not staying in sync with the latest kernel updates.
YMMV and this is by no means advice on your personal fit.
Personally I am not fond of most casual user low barrier distros but I still recommend them. Manjaro, PopOS, LinuxMint, Endless, are all fine options depending on what kind of user.
I recently recommended one to a GameDev and considering SteamOS is Arch he decided on Manjaro over Debian.
YMMV, and its important to listen first to people to see what they want their machine to do.
One last criticism of Canonical and Ubuntu. Their HQ is UK based and I honestly wonder how the culture effects development. Germany, UK, California all have different “feels”, its hard to be more specific.
Choice is good, always keep your data backed up and the @home on a different partition. The differences across distros are largely not a big deal like they used to be. People find solus in being captain of their Linux adventure and even Ubuntu will do just fine at the basics, just know if you hit a snag it may not be like that on every distro.
RPI print server + sshfs?
instead of curly brackets if statements are closed with fi
https://stackoverflow.com/questions/7010830/bash-whats-the-use-of-fi
This is a fascinating concept.
If files are removed from the Index it would only seem natural that they can be undeleted until their physical address is recycled and overwritten.
In fact I remember something like this pre Windows 95 era where files were crossed out. Undeleting them was like magic.
This is why the windows term “Recycle” is more appropriate because the data remains until the space is reused or zero’d out.
This is the kind of reexamining we need, does our current iteration make sense from an engineering perspective or is it just a evolution of a bunch of archaic stuff from a time that doesn’t represent the present tech world at all.
I would be okay with replacing rm with recycle and shred as their function is more clear in the name.
True, I still think it’s fair to criticize the package managers and distros for not anticipating this common scenario and having the ability to roll back easily. How many millions of Linux users have experienced this issue? I’ll bet a few.
Debian, Gentoo come from another generation and sometimes it shows, I mean snapshots weren’t even a thing yet AFAIK.
This was definitely one of my least favorite things when I used Debian.
It shows that we need to think about how users are performing tasks and how to intuitively make their usage more successful. The OS should try to get out of the way and always have the ability to easily revert in the case of platform failure.
I’ve looked, are there any clear winners I might have missed?
12.1" Damn. I would have gotten excited if it was a 6-8" device
It was a PITA on Arch because the Debian roots didn’t play well.
I canned all usage many years ago.
Is it me or is source forge just the mark of dead things.
I always avoid that place. It feels like where you go to get broken stuff.
They’re gonna take me out back and shoot me for saying it but Launchpad too. Like I’m glad it works for you but it feels like when Debian had a website in 2015 that looked like 1997. How are we going to attract new talent when the rift between the average developers and the old guard widens over time. All the git VCS modernization supercharged development. Like bugzilla was “fine”, but " fine" was the problem in a world of better when you couldn’t even upload a > 250kb jpeg and other legacy hold us back stuff.
I was incorrect about the aspect ratio it’s 3:2 not 16:9 and I think 3:2 is fine especially at 2160x1440p.
Still with the dialogs on the left and right anything except minimal would make the drawing area small taking the left and right.
I did notice it on sale, maybe if you have humble expectations it would be okay for sketching, but if you are used to better quality things or larger draw surfaces you might not be easily impressed.
Excellent, did my test config last month for a friend, I was having trouble on bare metal even though I typically prefer, and in this sense it was nice to have a image I could turn on and off as needed easily.
I was kind of turned off by the keeb* being sold separately, also wasnt the aspect ratio meh.
Rule of thumb larger screen or surface means more fluid strokes, thus smaller screen means more fine motor skills and more tension in the hand and less* fluidity in the work.
Assume I’m an amature and bad at this ;P
In any case you might try a docker-compose.yml
version: "3.8"
# Compose file build variables set in .env
services:
supervisor:
platform: linux/amd64
build:
context: ./build
args:
PYTHON_VERSION: ${PYTHON_VERSION:-3.10}
PYTORCH_VERSION: ${PYTORCH_VERSION:-2.2.2}
WEBUI_TAG: ${WEBUI_TAG:-}
IMAGE_BASE: ${IMAGE_BASE:-ghcr.io/ai-dock/python:${PYTHON_VERSION:-3.10}-cuda-11.8.0-base-22.04}
tags:
- "ghcr.io/ai-dock/stable-diffusion-webui:${IMAGE_TAG:-cuda-11.8.0-base-22.04}"
image: ghcr.io/ai-dock/stable-diffusion-webui:${IMAGE_TAG:-cuda-11.8.0-base-22.04}
devices:
- "/dev/dri:/dev/dri"
# For AMD GPU
#- "/dev/kfd:/dev/kfd"
volumes:
# Workspace
- ./workspace:${WORKSPACE:-/workspace/}:rshared
# You can share /workspace/storage with other non-WEBUI containers. See README
#- /path/to/common_storage:${WORKSPACE:-/workspace/}storage/:rshared
# Will echo to root-owned authorized_keys file;
# Avoids changing local file owner
- ./config/authorized_keys:/root/.ssh/authorized_keys_mount
- ./config/provisioning/default.sh:/opt/ai-dock/bin/provisioning.sh
ports:
# SSH available on host machine port 2222 to avoid conflict. Change to suit
- ${SSH_PORT_HOST:-2222}:${SSH_PORT_LOCAL:-22}
# Caddy port for service portal
- ${SERVICEPORTAL_PORT_HOST:-1111}:${SERVICEPORTAL_PORT_HOST:-1111}
# WEBUI web interface
- ${WEBUI_PORT_HOST:-7860}:${WEBUI_PORT_HOST:-7860}
# Jupyter server
- ${JUPYTER_PORT_HOST:-8888}:${JUPYTER_PORT_HOST:-8888}
# Syncthing
- ${SYNCTHING_UI_PORT_HOST:-8384}:${SYNCTHING_UI_PORT_HOST:-8384}
- ${SYNCTHING_TRANSPORT_PORT_HOST:-22999}:${SYNCTHING_TRANSPORT_PORT_HOST:-22999}
environment:
# Don't enclose values in quotes
- DIRECT_ADDRESS=${DIRECT_ADDRESS:-127.0.0.1}
- DIRECT_ADDRESS_GET_WAN=${DIRECT_ADDRESS_GET_WAN:-false}
- WORKSPACE=${WORKSPACE:-/workspace}
- WORKSPACE_SYNC=${WORKSPACE_SYNC:-false}
- CF_TUNNEL_TOKEN=${CF_TUNNEL_TOKEN:-}
- CF_QUICK_TUNNELS=${CF_QUICK_TUNNELS:-true}
- WEB_ENABLE_AUTH=${WEB_ENABLE_AUTH:-true}
- WEB_USER=${WEB_USER:-user}
- WEB_PASSWORD=${WEB_PASSWORD:-password}
- SSH_PORT_HOST=${SSH_PORT_HOST:-2222}
- SSH_PORT_LOCAL=${SSH_PORT_LOCAL:-22}
- SERVICEPORTAL_PORT_HOST=${SERVICEPORTAL_PORT_HOST:-1111}
- SERVICEPORTAL_METRICS_PORT=${SERVICEPORTAL_METRICS_PORT:-21111}
- SERVICEPORTAL_URL=${SERVICEPORTAL_URL:-}
- WEBUI_BRANCH=${WEBUI_BRANCH:-}
- WEBUI_FLAGS=${WEBUI_FLAGS:-}
- WEBUI_PORT_HOST=${WEBUI_PORT_HOST:-7860}
- WEBUI_PORT_LOCAL=${WEBUI_PORT_LOCAL:-17860}
- WEBUI_METRICS_PORT=${WEBUI_METRICS_PORT:-27860}
- WEBUI_URL=${WEBUI_URL:-}
- JUPYTER_PORT_HOST=${JUPYTER_PORT_HOST:-8888}
- JUPYTER_METRICS_PORT=${JUPYTER_METRICS_PORT:-28888}
- JUPYTER_URL=${JUPYTER_URL:-}
- SERVERLESS=${SERVERLESS:-false}
- SYNCTHING_UI_PORT_HOST=${SYNCTHING_UI_PORT_HOST:-8384}
- SYNCTHING_TRANSPORT_PORT_HOST=${SYNCTHING_TRANSPORT_PORT_HOST:-22999}
- SYNCTHING_URL=${SYNCTHING_URL:-}
#- PROVISIONING_SCRIPT=${PROVISIONING_SCRIPT:-}
sudo pacman -S docker
sudo pacman -S docker-compose
#!/bin/bash
# https://stackoverflow.com/questions/49316462/how-to-update-existing-images-with-docker-compose
sudo docker-compose pull
sudo docker-compose up --force-recreate --build -d
sudo docker image prune -f
#!/bin/bash
sudo docker-compose down --remove-orphans && sudo docker-compose up
Docker seemed the easiest
Will there be a big party where we can be baked
TCPIP stacks hate this one trick
Wow that’s so cool, yes this is very similar to what I’m trying to do, copy to a predesignated “register” and then recall it, be it A B C or 1 2 3 …
Sometimes it’s nice to put the ADHD away and just have simple fucking interfaces without all the stupid distractions.
This was my exact experience browsing the Social Media on gemini:// – it was glorious how less can actually be more.