If you resize the partition? No, the UUID gets allocated when the partition is created and stays the same for the lifetime of the partition. It only changes if you explicitly change it manually. Which is something that’s only needed very rarely.
For example I had to do it when I migrated my root disk to a larger SSD by cat-ing the entire disk to the new one and I wanted to keep both connected for a while (so I can boot into the old one in case anything went wrong). I had to change the UUID of the partition on the new disk but I still ran into some obscure grub issues and had to boot a system rescue live stick into the new disk to update grub properly. Overall it’s not a very good idea, in the future I think I’ll stick to rsync -avx root into the new partition.
In my case it actually changed after i resized it. It was unexpected and broke my system. After i adjusted the UUID in the boot config it worked again.
I currently have a System76 laptop, and sincerely regret my purchase. When I purchased it, the Framework was not out yet - I wanted to support a company that supports right-to-repair, and figured since they controlled the hardware, firmware, and software (Pop!_OS), it would be a good, stable experience. It has not been, and support has generally been poor. I know other people have had better experiences than I have, but personally, I won’t be buying from them again.
I haven’t personally used Purism, but former co-workers spoke really poorly of them. They were trying to buy a big batch for work, and said the build quality was awful. Additionally: youtu.be/wKegmu0V75s
I have one problem with my s76, the usb c port rly sucks. Other than that the laptop runs very well but something so simple shouldnt be an issue imo there are some build quality issues going on…
My usb-c ports can be a little touchy, too. The SD card slot is also really bad - the card has to be positioned perfectly to slide in, or it jams. I’m also upset that the usb-c port can only be used for charging after a full boot. It cannot be used to perform firmware updates, or even to do a ram test. This means day-to-day, usb-c can be used, but I have to keep track of the barrel charger, just in case. This, of course, was not specified on the product details page (nor, I think, that only one of the two usb-c ports could be used for charging - it’s possible I overlooked that, but still frustrating on an expensive laptop that lists usb-c charging as a feature).
Dang, I did not even realize that about the usb c port only being usable after a full boot, since I just got it. I need to find out where I put that barrel charger. Haven’t tested the sd card slot yet but will try and report back.
You might get lucky. Based on support.system76.com/articles/system-firmware/, it doesn’t seem to be all models. Note however that the list is out-of-date; my galp5 is not listed, but does not work. Fortunately, I found this out doing a RAM check, and not a firmware upgrade.
The lack of VRR in GNOME is what had me change to KDE. I prefer GNOME in many ways, but I was tired of having to use the vrr patches to keep the functionality.
I thought its an entire different desktop. Especially itd not possible to run gamescope while a X11 Desktop is running so I guess you are wrong with “bypassing”. Its just switching to gamescope. Its a Wayland compositor. It does even less than a Window Manager (is this right?)
I assume as this is a Gaming mode, its purpose is not to avoid waiting for features. But close the entire desktop which may use up to 1GB RAM and a by of CPU. Which definetly impacts the game by some fraction. Doesnt matter how tiny, its just what gaming modes are having as focus I assume.
The next thing I would never see on a desktop is FSR which gamescope has.
They intentionally removed this feature years ago. It was possible to reenable via a dconf setting for a while but I believe that was also eventually removed.
So annoying.
What do you mean with “copy path to file”? Do you mean “copy to clipboard”, as in, store the absolute path of a file to the clipboard?
Last time I needed this, all I needed to to was copy a file/folder and paste it in a text editor. Drag and drop also worked for most programs, though some tools weren’t d&d aware and don’t accept input that way.
I don’t use this feature often, though, so it may have changed since I last tried. It also tended to prepend protocols like dav:// or smb:// when copying files from shares rather than copying the path to the place these shares were mounted.
Yes, Gnome is context aware if you ctrl+c a an image file, and you paste it to a text editor it will paste it as a path, if you paste it in an image editor it will be pasted as an image, if the program supports it (e.g. it works in Krita, but not in Pinta)
Drag and drop is not working because of Wayland. Between 2 windows of the same app, e.g. Nautilus it’s working.
Putting the following with executable permissions inside ~/.local/share/nautilus/scripts/SCRIPTNAME adds a right click menu to Nautilus that serves the same purpose:
The ‘notify-send’ bit isn’t necessary; it just puts up a notification.
Mentioning only because it’s a simple demonstration of a pretty easy way to extend Nautilus for all kinds of purposes; w/o messing around with the pygobject interface. (There’s supposed to be an xdg standard for file manager extensions like this, but managers use their own custom folders, syntax, etc. for such extensions. I think pcmanfm adheres to the standard; Dolphin requires a .desktop file somewhere; Thunar, Caja, & Nemo work similar to Nautilus.)
While I’m yet to do it myself, I would suggest getting a Thinkpad T480 and upgrading its RAM. The reason you want a T480 is because it was the last Thinkpad to have user removable parts. One tip: when using eBay, make sure you filter out the T480s. The T480s is not the same as the T480 since it doesn’t have user removable parts.
Thanks for the tip. I know a lot of people are going for Thinkpads and you’re specific recommendation may seem interesting but I’d like to support other companies like the ones I bought from so far (Toshiba, Lenovo, Dell, Vaio, Acer, PB, Razer) and I’d also like to build my own laptop from the start.
Yeah it is but it’s a pretty capable laptop. I’ve replaced mine with a Framework 11th gen for my daily use but my T480 is currently hosting 10 VMs for my homelab. It’s got the base CPU, i5-8250U, 64GB of RAM and a 4TB SSD and is plenty of horsepower. I really only got the Framework because I was excited about the product and company, not because I was unsatisfied with the T480. I highly recommend it.
What parts other than one stick of RAM aren’t upgradeable on the t480s? The processor? I’ve seen screen swaps, touchpad swaps, keyboard, just about everything. I got one back in the summer, added a stick of RAM to get up to 16gb, it’s running at 3200mhz like the other one, and swapped in a new OEM battery. It’s been great. I also recently bought a e495 for around 60 bucks, it’s thicker and plastic-ey, but also a solid Linux machine running an AMD CPU. Are the newer t14s really that crippled in repairability?
It would be if it wasn’t for NVIDIA, as usual. On Intel/AMD, you assign the seats, the displays light up and you’re good to go, pretty much works out of the box, especially on Wayland.
But for NVIDIA yeah maybe a VM is less pain since NVIDIA works well with VFIO.
I tried installing Debian recently as well but didn’t get too far into it. I was annoyed at the base configuration* though. I wasn’t able to use sudo, so I went to add myself to the sudo group and it told me the command didn’t exist… I looked it up and realised that /usr/sbin* wasn’t on terminal path. Extremely fixable but something I never ran into on other distros, made me nervous how many other tweaks I may have to do.
I was simultaneously testing Lubuntu and ended up sticking with that after following install instructions for another app kept complaining about bookworm errors. Perhaps the Debian version was too new?..
Edited a couple of details to make them more accurate.
I suppose it depends on a lot of things. Errors are pretty common once you start installing a lot of apps in any distro imo. Especially unstable and sid are more up to date but as the name suggests less stable.
beside op’s bashrc fud, it’s a common newbie misconception that testing and sid are not stable like some kind of exotic experimentation would make them so. It is more a stabilization process in respect to the project’s policy/processes and you will definitely find /usr/bin in pathh in either testing and sid rofl
Thats stable atm. No clue what it was back then. It took me a bit to add myself to the sudo group since sudo visudo doesn’t work. No idea what the use of that is.
you obviously can’t use sudo visudo if you’re not already in the sudoers file LOL - is the same security, which you also desire, as having a spare set of keys in the bowl at the entrance to your house, where, however, no one comes unless they already have a key to open the door
I made a mistake, fine. Visudo doesnt work either from my recent experience. At the very least, it should say „dont use sudo as root“ instead of „the command doesnt exist“.
You could have explained it without the elitist touch. Tyvm
I added my user to the sudo group and rebooted (as relogging doesnt work either).
So, debian is cool but you can definitely see how fanboiism keeps it from being great.
and instead you needed a slap on the wrist so the next time you come to lemmy you’ll think twice about pointing out a community, whatever it is, as idiotic to the point of making a trivial mistake that only you know how to fix with a more-than-trivial workaround. It’s not a matter of being a debian fanboy, in this case the distro packages the vanilla behaviour of an upstream present everywhere, which does exactly the same thing everywhere
I have no idea what you‘re talking about. I didnt point out anything and surely didnt need a slap on the wrist. Whatever bdsm fantasy you‘re having atm.
I was nice enough to admit my mistake, whereas you were a jerk enough to make fun about it you sad person. Now go away.
Well, I don’t know what to tell you when I had just installed and the system tells me the command does not exist, so I look up the error and adding the path to bashrc fixed the issue. The only PATH export in that bashrc file is the one I added after searching the issue.
Well, I don’t know what kind of mess you made on your machine, nonetheless I find it mind-boggling your assumption that one of the most used/derived distros in the world exits the installation with such an error without anyone noticing/fixing it. That said, glad you fixed it, and for the affection I feel for the Debian project, even happier that you are not a user of it :P
You don’t need to be defensive about this. I’m just sharing my experience, I’m not trying to insult Debian or it’s maintainers. And yes I believe anything can happen considering the crazy bugs I have seen get shipped. Windows wiping One Drive files, multiple Steam bugs on Linux that can wipe your system, etc. Or it may be my choices during install, but it is still unusual compared to all of my Ubuntu installs.
Anyway, I took another shot at it and it still happened. I downloaded the 12.4.0 net install that is on the front page of debian.org. Installed two different times in Virtualbox, once using the graphical and once using the CLI install, using two different mirrors. I unchecked Gnome and ticked LXDE during installation (as I did before), because that is the DE I wanted. I would hope that would not change bashrc settings. Tried sudoing and got the exact same error. https://i.imgur.com/dhFnLgc.png
Here’s the generated .bashrc which I have not touched.
.bashrc`# ~/.bashrc: executed by bash(1) for non-login shells. # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) # for examples # If not running interactively, don’t do anything case $- in i) ;; ) return;; esac # don’t put duplicate lines or lines starting with space in the history. # See bash(1) for more options HISTCONTROL=ignoreboth # append to the history file, don’t overwrite it shopt -s histappend # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) HISTSIZE=1000 HISTFILESIZE=2000 # check the window size after each command and, if necessary, # update the values of LINES and COLUMNS. shopt -s checkwinsize # If set, the pattern “**” used in a pathname expansion context will # match all files and zero or more directories and subdirectories. #shopt -s globstar # make less more friendly for non-text input files, see lesspipe(1) #[ -x /usr/bin/lesspipe ] && eval “$(SHELL=/bin/sh lesspipe)” # set variable identifying the chroot you work in (used in the prompt below) if [ -z “${debian_chroot:-}” ] && [ -r /etc/debian_chroot ]; then debian_chroot=$(cat /etc/debian_chroot) fi # set a fancy prompt (non-color, unless we know we “want” color) case “$TERM” in xterm-color|-256color) color_prompt=yes;; esac # uncomment for a colored prompt, if the terminal has the capability; turned # off by default to not distract the user: the focus in a terminal window # should be on the output of commands, not on the prompt #force_color_prompt=yes if [ -n “$force_color_prompt” ]; then if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then # We have color support; assume it’s compliant with Ecma-48 # (ISO/IEC-6429). (Lack of such support is extremely rare, and such # a case would tend to support setf rather than setaf.) color_prompt=yes else color_prompt= fi fi if [ “$color_prompt” = yes ]; then PS1=‘${debian_chroot:+($debian_chroot)}[
lol I’m not defensive at all, I swear I don’t need that :D. The theme here is that you keep thinking you don’t have an ass because you’re looking for it on your forehead instead of between your butt cheeks :D
What we can already see:
sudo is indeed installed, and in path
bash is running since system is newly installed => /usr/bin is obviously in path (bash lives in /usr/bin/bash)
set | grep ^PATH will show that /usr/bin is indeed in path, also the fact that grep runs tell it path is correct, since grep lives in /usr/bin/grep :)
that said, your user isn’t in the sudoers file because you choose to give login access to root during install (which is strange, because no sudo package get installed if you choose that, so you probably made some other strange not-obvious thing), and no, groupadd can’t be run by the user you keep being after a failed sudo invocation (of course you can invoke it w/ the fully qualified path which is /usr/sbin/groupadd w/ /usr/sbin not in user’s path because the binary here usually require high permissions).
now you have a chance to learn something: where is PATH env var configured? Is it in your home or outside? Why and how it gets parsed?
cmon, let’s explore a bit my good boy, let’s be curious about the world that is not wrong by default and only we are right ;) let’s learn stuff, for real
I never said sudo was not installed, I said I wasn’t able to use sudo, which I wasn’t. This is why I went to run groupadd, which is when I discovered that it is not on PATH, which it isn’t. You’re right I shouldn’t have run groupadd as an unpriviledged user, that is fair, although it also isn’t on my root PATH. https://i.imgur.com/xJsXMVX.png
You’re also correct that /usr/bin is on PATH, so my initial statement is not correct: /usr/sbin is not on PATH. Forgive me mixing up the two, it didn’t seem like an important disctinction earlier when I recalled the experience off memory.
Going back to my original post though, I was simply stating that every Ubuntu variant I have used sets me up with all this out of the box, meanwhile Debian immediately required more set up. It felt more “raw”. I can see the logic behind these changes, but as a new user it was off-putting as compared with every other distro I had used. That is all my point was. I got around the issue, it was not world-ending, but, to quote earlier me, I “was annoyed”. Simple as. I was sharing my experience with Debian because the pitfalls I encountered seemed relevant to the thread title: coming from Ubuntu to Debian.
now you have a chance to learn something
cmon, let’s explore a bit my good boy, let’s be curious about the world that is not wrong by default and only we are right ;) let’s learn stuff, for real
I am not averse to learning and I have learned a couple of new things, yes. Thank you for the insight. It doesn’t change my initial statement.
your user isn’t in the sudoers file because you choose to give login access to root during install
This makes sense, thanks. I don’t really mind not having sudo from install though, I mentioned it because it is what started me down the “groupadd” road.
so you probably made some other strange not-obvious thing
I followed the graphical install and used default options except for LXDE.
as you wish my friend, I see no value in insisting you’re doing something wrong. Good luck with your distro of choice which, I repeat, I’m glad isn’t debian :D (still PEBKAC, but really, no value in insisting :PPP)
/usr/sbin not being included in PATH by default is definitely annoying, but I understand why it is that way. It’s because they’re infrequently accessed admin tools.
If it was my decision, I’d include them in PATH though.
and I understand you reason that way because you have no clue and THAT’S OK (to some extent). Go ahead and be free, all of this shit is ultimately about that and I’m glad too because I know I’ll keep having a predictable, understandable system so yay for us my friend :)
also, there is not a “specific default”, I don’t care about debian and even if I’m not using since longtime in this thread stupidity has been expressed :P
I read your entire comment and responded to everything relevant. I didn’t break down every sentence word by word because most people don’t enjoy reading those sorts of replies, so I kept it to the bits that required a response. I don’t know what you are talking about at this point, but considering I had the attention span to spend an hour re-installing Debian twice to verify, I don’t think that is the issue here. I have been exceedingly pleasant considering your condescending tone, so your repeated quips and assumptions of the worst are uncalled for.
I stated an experience I had that I disliked. You stated my experience didn’t happen, and I have laid out how it occured and explained what my initial issue was. I am allowed to dislike how a distro does things while acknowledging it is doing those things intentionally. I thank you for the bits of wisdom amongst your snark, but I’m going to go do more enjoyable things now. And maybe I’ll use Debian on my next server, sorry to disappoint you since you are so determined to gatekeep it (or why else are you so glad I’m not using it?).
sure you’re right! Go ahead, not that I care a lot :P
probably belonging to a divine elite, or maybe one of assholes, it’s enough for me to pay my bills knowing how to use the systems and after a quarter of a century I don’t give a shit if on lemmy some pirate comes along and tells me otherwise, my bills keep paying so ciaoooo :)
also let’s be curious about the things we copy-paste in order to prove whatever theory: in literally the first line of your bashrc non-login shells are named. What are those non-login? If we need to defined them like that, do also we have a non-non-login ones? How do they get executed? How do they get initialized? Let’s explore and understand some new stuff (that we should have learned already, but who cares, it’s not our job!)
It was probably /usr/sbin you’re thinking of rather than /usr/bin. IIRC – don’t quote me on this – Red Hat puts it in non-root user paths by default, and Debian doesn’t.
You’re correct. That’s one of the few useful things superbirra mentioned, and I’ve updated the parent comment to correct my initial error. I was recalling from memory and just remembered it was a “bin” folder.
I’ve had a framework for 2 years now. It’s run fedora, manjaro (arch based) and Debian with no major issues. Manjaro had some problems with KDE and the high DPI screen. Sometimes the scaling was inconsistent between apps. Fedora just works.
Only hardware issue is the battery life is just not that great. And the trackpad doesn’t always work property, but I think that was a first generation issue that’s been resolved since.
I’m going to add my +1 for framework, I got the batch 5 original framework 13 with pop os on it and a windows 10 copy on a 250gb expansion card. Its been my main work and play laptop and I enen replaced the main chassis after it got smashed (long story) involving the sidewalk. Anyway I love what framework is doing and the decision has arguably already paid off within these last two years.
Don’t know if you plan to use another Arch-based distro on this laptop in the future but I came across this page which has some tips to adjust the Framework 13 including one that may be related to what you mention. They recommend to use 1,5 scaling factor. More details can be found here.
I recommend next time to use btrfs. With / and /home (at least) as separate subvolumes. Each subvolume will use the space it needs, and no more. If you have a 500Gb SSD with 300Gb in /home, and 20 in / they both have 180Gb they can use.
And when you manage to fill the 500Gb, it’s easy to just add another drive to the volume.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.