No downvote here my friend. I love arch, but that doesn’t mean it’s for everyone. Plug-and-play distros are great too, they just have different strong points.
Haha, I’ve been daily driving slackware since the late 90s. I like to tinker and install a lot of stuff. I seem to break anything with an automated package manager and dependency resolution.
Nah, I’m just a hobbyist. I’m a n00b compared to all the regulars in the slackware channel on IRC. But I love tinkering and learning. I’d need your help to install vanilla arch, just like you’d probably need mine to get started on slackware. (The slackware install is actually super easy).
I’ve been trying to distrohop the past couple months, see what else is out there. I wasn’t paying attention installing Garuda and borked my EFI partition. I did manage to chroot into my still working slackware partition, but I couldn’t figure out how to re-install grub. So I formatted and did a fresh slackware install.
NixOS… for now. I was on Fedora and was looking for something new. Thought I’d try these new „immutable” distros. Then realised I didn’t know enough about normal ones yet, so I switched to Arch instead. Plus, Nix’ docs are horrendous imo
I tried NixOS too, and their docs are horrible for new users. I found myself looking for anything but the docs to get started. I decided to stay with my EndeavorOS install.
just go zorin os. it attempts to simulate the look and feel of windows while also having a lot of pre installed applications including playonlinux/wine sot that once its installed you can just go.
Sorry, but Debian stable is a terrible recommendation! They don’t even ship bugfix releases of KDE Plasma… It’s stuck with a months old version that has lots of known and long fixed bugs in it
Get into the “variety is good” mindset. Having options is always better than not having options, even if it feels overwhelming at first. It’ll get easier with time
One of the great things about Linux is that you can almost always just run whatever distro from the USB drive before installing (and just reboot without the USB drive to get back into Windows) So you can download a few ISOs and try each one for a bit before committing to anything.
This is nice if there’s anything specific that you need to work, you can try it and make sure it’s usable for you before making any permanent changes.
For example, I’m legally blind and use a screen magnifier. I tried a few distros to compare the built-in magnifiers before settling on one.
I’d also recommend using Ventoy on your USB. That lets you just plop ISO files on the drive and choose which one at boot.
I made the dive into Linux mint last night. If you already have windows installed you can side load so you don’t have to completely commit right out of the box. I play games that would require windows so this was necessary for me but so far outside of hating middle mouse click to paste and some troubleshooting for my headset (I could hear myself quietly through my headphones when speaking into mic) Linux has been preferable to win11
You’re right, but the point I was trying to get across to another layman is you can have windows already installed and not break anything with another install of Linux. Rather than get into partitioning and dual booting.
Sideloading an app on a phone doesn’t have the potential to wipe everything else off the phone. It’s bad advice to call dual booting that because you might cause someone to go into it without understanding the risks involved. In fact, the best facsimile, which doesn’t even require knowing how to get into the boot menu, would be to run a Virtual Machine instead. That way there actually isn’t any risk of erasing Windows. It’s also really simple these days, here’s some guides from ubuntu and fedora:
Or if you don’t want to go through the hassle of installing Linux inside the VM yourself, you can download pre-built VMs for most major distros from here:
Sure, I’ll do that. But you’ve lost 99% of average people when you mention “virtual machine”.
Also at least for mint which I was directly talking about you actually boot via live USB first and have to install from an icon on the desktop so there really is no risk for erasing windows until your well into making decisions. Which again you have to choose to erase windows.
For me the difference between a cli and a gui is like asking someone to do something speaking in a language they can understand and doing it just by pointing at things and doing gestures. It's enough for ordering at a restaurant, but for more complex tasks it gets ridiculous, even at a restaurant you'll get better results if you can ask for some information and understand what the server says
That would probably be the most elegant solution overall and I appreciate the suggestion, but a new drive costs money that I don’t currently have an abundance of and I already have empty drives that aren’t being used, which I had accumulated over time and had already paid for ages ago. If I’m being honest, the reason I want to do it this way is because I don’t really see the value of using a brand new drive for an offline backup of personal data where the drive will be plugged in at best once a month before being stored in a drawer. If I buy a brand new drive I’d rather actually use it as part of the active storage in my server and keep it running to get the most utility out of it.
Debian version is the only one that seems reliable enough but, again, it is Debian, the packages are “old”.
Install Debian, then install all the software you might need using Flatpak. There you go, solid and stable OS with the latest of with little to no effort. Bonus extra security.
In first you need understand what type of suspend you use:
Suspend to RAM (aka suspend, aka sleep) The S3 sleeping state as defined by ACPI. Works by cutting off power to most parts of the machine aside from the RAM, which is required to restore the machine’s state. Because of the large power savings, it is advisable for laptops to automatically enter this mode when the computer is running on batteries and the lid is closed (or the user is inactive for some time). Suspend to disk (aka hibernate) The S4 sleeping state as defined by ACPI. Saves the machine’s state into swap space and completely powers off the machine. When the machine is powered on, the state is restored. Until then, there is zero power consumption. Hybrid suspend (aka hybrid sleep) A hybrid of suspending and hibernating, sometimes called suspend to both. Saves the machine’s state into swap space, but does not power off the machine. Instead, it invokes the default suspend. Therefore, if the battery is not depleted, the system can resume instantly. If the battery is depleted, the system can be resumed from disk, which is much slower than resuming from RAM, but the machine’s state has not been lost.
I think you use Hybrid suspend. Hybrid suspend store memory to disk (20 seconds lag) and then lost battery for memory renew. Need you Suspend to RAM maybe? 20 Seconds lag will fixed with that.
<span style="color:#323232;">[s2idle] shallow deep
</span>
check first if your UEFI advertises some settings for it, generally under Power or Sleep state or similar wording, with options named Windows 10, Windows and Linux or S3/Modern standby support for S0ix, and Legacy, Linux, Linux S3 or S3 enabled for S3 sleep.
If you don’t see anything you can swap sleep mode to Suspend to disk. That slow but don’t use any power. Or try fix sleep status.
Hibernation or suspend? 2 different things. For hibernation you need a swap space at least the size of your RAM, and then the laptop is powered off after this.
For suspend, in your dmesg, see if you have:
ACPI: PM: (supports S0 S3 S4 S5)
if you have S3 your laptop should lost only a few percent.
do a:
cat /sys/power/mem_sleep
what does it says?
New CPU/BIOS/PC/Laptop only support something called “s0 idle” meaning it is like a cellphone, everything is running, and each drivers/components/os should enter low power themselves, if they do not, well, your battery is draining.
S3 means “suspend to RAM”, only RAM is powered and everything else is off, your laptop can stay like this for days. I don’t know who decided that this is bad and your laptop should be like your cellphone, always running?!?
Modern Fedora doesn’t enable swap by default and configures zram instead. Of course, you can’t hibernate to zram, so getting basic hibernation to work involves either disabling zram and configuring swap, or using callbacks to temporarily disable zram and enable swap right before suspending.
Not spesifically a tool to put on a USB stick, but Ventoy is worth checking. I’ve had a bit mixed results with it on older hardware but when it works it’s pretty easy to manage your carry-on-tools.
So they’re building a whole complex text editor just for the desktop environment? seems like a weird priority or is the text editor a separate project?
As is often the case with scientific research which many people believe to be pointless, technological innovations aren’t always made by achieving the end goal, but through the technologies developed to reach that goal.
Development on COSMIC Edit has lead towards improvements to the cosmic-text library, which is used by many GUI libraries in the Rust ecosystem now. Similarly, the UX designs for the text editor improves the COSMIC interface guidelines, and puts design theories to practice. Likewise, widgets that are necessary for the editor are added to the COSMIC platform toolkit, and existing widgets and features are improved to improve the development experience for applications like this.
No one would want to build applications for a platform that lacks widgets capable of properly displaying, formatting, and editing text. Many would also find it debilitating to have a desktop environment without a text editor preinstalled. Imagine if GNOME didn’t have Gedit, and KDE didn’t have Kate.
Besides, this is a default text editor for a desktop environment. It is really not that complex. The goal is not to develop an IDE, but a text editor that anyone would feel comfortable using as their default editor on the COSMIC platform.
No one would want to build applications for a platform that lacks widgets capable of properly displaying, formatting, and editing text.
Is the idea that people are only going to be running Iced applications in COSMIC? It feels to me like the realistic option would be that, if COSMIC ever becomes daily-drivable, people would still be using GTK applications with it, at least at first. Might as well use a GTK text editor then? Then System76 could focus on building a text editor after COSMIC is a thing, and COSMIC would hopefully arrive sooner (or even at all - this looks like the path to burnout).
You are heavily overestimating how much effort is required to develop a text editor. It’s a single person project using components that had to be developed for use in multiple applications; regardless of whether there is a text editor or not. Components that you’d be silly not to develop through a text editor project.
You are trying too hard to justify that we not make a text editor. It feels like you don’t want us to make a text editor at all. No one is on a path to burnout. Everyone is paid a full time salary to work on their respective areas. COSMIC development is doing really well.
I mean, I don't really mind - I'm pretty happy with GNOME. All I'm saying is that if I were the project manager, I'd worry about delivering something and not burning people out ("focus is choosing what not to do" and all that, and the last 20% of the work taking 80% of the time). But in the end I'm just a random person ranting on the internet, of course - I do actually hope that I'm wrong.
But a diff viewer in the text editor... It just sounds like folks are eager to jump on shiny new things rather than finishing something, from the outside 🤷 Looking forward to be proven wrong!
COSMIC Edit is being developed by our manager through personal motivation; who also developed cosmic-text, so this is the perfect playground for simultaneously advanced cosmic-text, and developing useful real world software with it. The git diff view was not yet part of planned designs, but it took only a portion of a day to implement. It adds a useful test case for the cosmic-text library, and improved cosmic-text as a result.
We’re all paid a full time salary to work on COSMIC and Pop!_OS. Each person on the team is going to spend a full day writing software, regardless of what they’re working on, so concerns about burnout are somewhat silly. Burnout is typically caused by working overtime for extended periods of time. System76 has never required developers to work overtime to meet a deadline, and variety of workload can alleviate mental fatigue, so burnout is not a thing here.
Yeah, that's fair enough. It's not just working overtime though - endless toil on never-ending projects, especially when at a certain point, you're not really making visible progress but rather are just working on a seemingly endless list of bugs and papercuts, is also terrible for motivation. The good news, of course, is that the Pop!_OS GNOME extension also got delivered, which, though a lot smaller than COSMIC DE, I'm sure also wasn't a small undertaking.
In my experience, that has never been an issue with any Rust-based projects. It’s quite the opposite. 80% of time is spent completing the first 20% of the project, and then the remaining 80% is quickly finished as everything fits into place. Most of our time is spent in foundational work getting widgets created that we can use with our theme system, and then the actual implementation of the interface in the application is stupid easy.
What you describe is what I felt developing the GNOME extensions. There’s very little you can do to resolve issues that you encounter there.
That being said I can imagine if KDE didn’t have Kate or Konsole or any of that - there’s plenty of text editors and Terminals that already exist out there.
GNOME users wouldn’t be happy having to install KDE dependencies to use a KDE text editor which doesn’t have a consistent look and feel on their desktop. Same applies for KDE users.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.