Found out the hard way that if you edit /etc/sudoers with anything other than visudo you best be absolutely sure the syntax is correct, otherwise sudo will refuse to read it and you’ll be locked out.
Also learned to add -rf to the rm command at the end, after I re-read it to make sure it does what it should do. Something like rm /path -rf instead of rm -fr /path. That protects you from your fat fingers hitting the enter key half way through.
Been there with sudo. Fortunately, su still works, as well as going to another tty and logging in as root. Well, as long as the root login is enabled; otherwise that old hack with init=/bin/bash may work, unless you’ve prohibited editing kernel cmdline in the boitloader or decided on efistub
Before installing Arch on a USB flash drive, I disabled ext4 journaling in order to reduce disk reads and writes, being fully aware of the implications (file corruption after unexpected power loss). I was confident that I would never have to pull the plug or the drive without issuing a normal shutdown first. Unfortunately, there was one possibility I hadn’t considered: sometimes, there’s that one service preventing your PC from turning off, and at that stage there’s no way to kill it (besides waiting for systemd to time out, but I was impatient).
So I pulled the plug. The system booted fine, but was missing some binaries. Unfortunately, I couldn’t use pacman to restore them because some of the files it relied on were also destroyed.
This was not the last time I went through this. Luckily I’ve learned my lesson by now
Ubuntu: It’s not a lack of features that pushed me away; it’s more about the way things are going. I am not a fan of snap packages. I have run into odd issues trying to use them. I used Ubuntu server for my Dell Poweredge and I shut it down until I can find a suitable replacement. I struggled with it respecting my DNS settings which in turn killed my reverse proxy setup.
Manjaro: While I love Arch and some of its derivatives, I can’t stand by Manjaro. I thought it would have been a good OS to use since I was familiar with Arch, but it had enough dependency issues where updates broke them. Funny enough, never have I had a dependency issue with just plain old Arch.
I use Arch btw. But besides the meme on it, I legitimately eo use arch and couldn’t be happier.
Same. Both started out good but kept becoming more and more… not good. If nothing else Manjaro taught me how to chroot from a live distro to fix catastrophic failures. Ubuntu really ruined my week when they decided to try becoming a smart phone with the very touch centric looking UI at the time when I didn’t have time to revert or change distros, which is what finally pushed me to run servers headless and use ssh. Last I tried none of the phone like de’s are particularly intuitive as touch interfaces either.
I use KDE on Arch on my Lenovo Yoga 7i, and I don’t particularly use the touchscreen as much as I would have thought. Though for Waydroid it does work fairly nicely.
Oh, just invest in adobe and get it developed for Linux - easy, why didnt anyone think of this before. And better yet, if they do invest they could make it a PopOS exclusive!!?!?!! \s
It wont work because Adobe does not care and there is not enough market share in Linux for them to bother with it. No amount of money that PopOS has will be able to convince Adobe to develop it for Linux and there is no way in hell Adobe will give them access to their source to develop it for Linux. That whole argument is just a non-starter.
Same thing happened to me. Moved to pop!_os.I have zero regrets. I’ve learned a ton. I use tons of apps off f-droid and foss Ubuntu apps. I have degoogled most of my life. I’m also developing an Firefox addon for lemmy. It’s usable as a user script addon now. It’s called lemmytools. It’s my small contribution. All because Reddit got stupid. I don’t even browse reddit for answers usually about tech/programming stuff anymore because they block my VPN.
There are literally dozens of us! I’m running Zorin. The Reddit debacle really hit home for me that free alternatives to commercial projects work best when everyone pitches in a little.
X is old and works for the most part but fixing stuff or adding features is hard.
Wayland is new and is supposed to be a successor to X, do what it couldn’t do and don’t repeat the mistakes from it. It should be a drop-in replacement like pipewire but isn’t. Features take long time to develop as devs are engrossed thinking of the best solution to make it happen. A lot of proposed solutions are dismissed as well.
I think the drama around Wayland can be explained by the sentence “it should be a drop-in replacement like pipewire but isn’t”.
Without taking a side on that issue, I will point out that this was not a goal for the Wayland designers ( in their own words - I do not have time to go find a quote but have read this sentiment many times ). Wayland detractors agree with your sentence and, given that expectation, are legitimately upset and even confused that Wayland continues to gain mind and market share against X11.
If you feel that Wayland needs to be a drop-in replacement for X11, it is not ready and may never be. By that metric, some people see Wayland as a failed technology and perceive Wayland users as shills and zealots.
If you are interested in a display server that addresses some of the core design problems in X11 and do not mind moving to something new, Wayland is starting to look ready for prime-time.
If you are non-technical and / or unopinionated the debate is probably irrelevant. Wayland will most likely become the default on whatever Linux distribution you use sometime in 2024 or 2025. You will be a Wayland user. Maybe you already are.
If you are willing to step outside the mainstream, using X11 without Wayland is going to be possible for at least another decade. That said, I am saying “outside the mainstream” because not only will popular Linux distributions and desktop environments start to become Wayland only but the innovation is all going to move to Wayland. There will be many Wayland-only compositors, apps, and features. 5 years from now, not using Wayland is going to really limit the desktop experience. I expect some toolkits ( GTK, Qt, and maybe even WINE ) to drop X11 support at some point ( maybe not soon but sooner than 10 years maybe ). 5 - 10 years may seem like a long time but it will likely come faster than X11 stalwarts expect.
Your i3 is too old. Perhaps your distro’s repository has a package called “i3-gaps” which was the former fork that implemented this feature. i3-gaps was merged back into i3 in the meantime.
In a certain light, you could argue that Linus doesn’t really have any control at all. He doesn’t write any code for Linux (hasn’t in many years), doesn’t do any real planning or commanding or managing. “All” he does is coordinate merges and maintain his own personal git branch. (And he’s not alone in that: a lot of people maintain their own Linux branches). He has literally no formal authority at all in Linux development.
It just so happens that, by a very large margin, his own personal git branch is the most popular and trusted in the world. People trust his judgment for what goes in and doesn’t go in.
It’s not like Linux development is stopped because Linus goes offline (or goes on vacation or whatever). People keep writing code and discussing and testing and whatnot. It’s just that without Linus’s discerning eye casting judgment on their work, it doesn’t enter the mainstream.
Nothing will really get slowed down. Whether something officially gets labelled by Linus as “6.8” or “6.whatever” doesn’t really matter in the big picture of Linux development.
If you hate job boards then you need to find individual company “Careers” pages and go from there.
How you go about this varies a lot by skillset and industry, but I’ll just throw out a random example: lots of Linux jobs exist in the DevOps space (think Kubernetes, Ansible, Chef, NixOps). It just so happens that lots of medium-sized software companies need DevOps people, so you can pretty easily find companies looking for DevOps hires just by browsing Y Combinator’s Startup Directory
With that being said, I get the impression from the way your post is worded that you’re looking to break into a new career without having yet established a concrete plan. My advice would be to step back and consider specific options first. Almost all jobs like these require industry-specific certifications (e.g.: CompTIA, ITIL, AWS, Azure, Cisco, etc.). You need to look at your options, pick a certification, earn it, then go job hunting. Certifications are great for securing entry level jobs and the standards body issuing these will often provide an online directory of partner companies who are currently hiring.
I find it pretty easy to use when building my 3d print adapters, brackets, containers and very simple objects. But if, like me, spaghetti code is your natural language… OpenSCAD does you no favors.
AFAIK openSCAD is a code driven mesh format. So if you want to import openSCAD models into any other CAD software you have to convert the mesh to STEP or some other actual 3d object format during which there can be lots of error if the model is complex. I don’t have a lot of experience doing this but I just tried a model I had lying around from the dactyl keyboard project and converting it resulted in a lot of really broken surfaces.
This is a cool alternative that makes 3d objects instead of meshes (at least it says it does). zalo.github.io/CascadeStudio/ . Also open source but web based.
EDIT: I should mention that CascadeStudio seems to be abandoned, just a cool concept of a different way of doing code driven CAD.
Basically a long time ago Linux/Unix was run on big machines in a separate room with all the fancy graphics hardware, and you’d have a dumb little machine at your desk that could barely draw pixels on a screen. So X11 was designed with all these fantastic neat server-client mechanisms that made it great for running on a mainframe.
Fast forward 30 years and all that stuff is useless now that everyone has built in graphics (as well as several other issues with X11’s archaic design). So some smart people who didn’t know any better made a new thing that everything has to be rewritten for (because they were smart, but didn’t know any better). Then someone who did know a little better was like, what if we take the old bloated one and rewrite it for the new lean one. So now everything runs in an X11 session inside a Wayland server, which has to be rewritten for everything because Wayland is a protocol, not a server.
But one of the really nice things about it is that everything has to be rewritten, so we can make newer, fancier bugs.
Edit: I don’t want you to take the impression that I think Wayland is bad. Wayland is way better than X, it just sucks that we have to rewrite a bunch of stuff for it and figure out new ways of doing things that were dead simple in X, but very insecure.
Also window managers started compositing which moved 1/3 of what X was doing to the window manager. Then applications started doing their own rendering which moved another 1/3 of what X was doing to the applications. All that is left over is basically the low-level IO which had gotten greatly simpler over the years and could basically be packaged into a few libraries (mesa and libinput primarily) and some complex mutli-hop IPC which was completely unnecessary.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.