Tmux allows you to reconnect to a session, and helps guarantee that you will always be able to get back to your long running processes. For important long running processes, I still use tmux with mosh, because if the mosh client is killed (or you’re trying to “re-attach” from a different device, mosh won’t let you “re-attach” to that “session”.
Mosh allows you to roam, and suspend your machine, and whenever you resume it again, whatever network you’re now on, the connection is basically instantly re-established. You can often roam from WiFi to cellular data without even noticing. (Great when working from a phone, or just a laptop)
In my opinion, they are mostly orthogonal (and complementary).
Here’s the list of features from the home page. I’ve added my own comments after ‘’. If there is no ‘’, then the feature doesn’t exist for tmux (because it’s outside the scope of tmux):
Change IP. Stay connected. Mosh automatically roams as you move between Internet connections. Use Wi-Fi on the train, Ethernet in a hotel, and LTE on a beach: you’ll stay logged in. Most network programs lose their connections after roaming, including SSH and Web apps like Gmail. Mosh is different.
Makes for sweet dreams. With Mosh, you can put your laptop to sleep and wake it up later, keeping your connection intact. If your Internet connection drops, Mosh will warn you — but the connection resumes when network service comes back.
Get rid of network lag. SSH waits for the server’s reply before showing you your own typing. That can make for a lousy user interface. Mosh is different: it gives an instant response to typing, deleting, and line editing. It does this adaptively and works even in full-screen programs like emacs and vim. On a bad connection, outstanding predictions are underlined so you won’t be misled.
No privileged code. No daemon. * Same for tmux, but that’s less interesting since tmux is not a network service You don’t need to be the superuser to install or run Mosh. The client and server are executables run by an ordinary user and last only for the life of the connection.
Same login method. * Not really relevant to tmux, which doesn’t handle auth Mosh doesn’t listen on network ports or authenticate users. The mosh client logs in to the server via SSH, and users present the same credentials (e.g., password, public key) as before. Then Mosh runs the mosh-server remotely and connects to it over UDP.
Runs inside your terminal, but better. * This is common to both Mosh is a command-line program, like ssh. You can use it inside xterm, gnome-terminal, urxvt, Terminal.app, iTerm, emacs, screen, or tmux. But mosh was designed from scratch and supports just one character set: UTF-8. It fixes Unicode bugs in other terminals and in SSH.
Control-C works great. * Tmux can help with this too Unlike SSH, mosh’s UDP-based protocol handles packet loss gracefully, and sets the frame rate based on network conditions. Mosh doesn’t fill up network buffers, so Control-C always works to halt a runaway process.
The main reason that I piled on Canonical was that they kept on spreading FUD about Wayland to try to promote / justify Mir rather than discussing in good faith.
Not quite running in userspace. To the best of my own understanding:
The new kernel feature is to allow writing schedulers in eBPF, a “language” the kernel runs in kernelspace that is heavily restricted.
For example, all eBPF programs must complete in bounded time, and the kernel’s static checker must be able to verify that before the program can even begin executing. eBPF is a rare language that is not touring complete.
“For scx_simple, suspending the scheduler process doesn’t affect scheduling behavior because all that the userspace component does is print statistics. This doesn’t hold for all schedulers.”
So, it may be that eBPF also makes it easier to write a truly userspace scheduler, but that’s not the primary purpose, and it’s not what is being done with scx_simple.
For anyone unfamiliar and wanting more background, and an explanation of why you may see Jewish people add ((( ))) around their own names on social media,
If you can take multiple large, failed, risks without ending up on the street then you have immense privilege.
It’s hard for most people to “learn from their failures” and keep taking “big” risks, unless the risk to their own life circumstances was never actually that “big”.
Well known KDE developer Nate Graham is out with a blog post today outlining his latest Wayland thoughts, how X11 is a bad platform, and the recent topic of “Wayland breaking everything” isn’t really accurate....
Nvidia will feel enough pressure (likely from the ML / HPC space?) to provide open kernelspace support that they’ll actually make that happen.
Which… Has already happened.
Nvidia took a lot of the kernelspace logic that used to be in their proprietary driver, re-architected their GPUs to move that logic into a firmware blob (GSP).
And last year they released a completely Free driver that intefaces with GSP.
This allowed Nouveau developers to finally access critical features like power management (which were basically behind a wall of DRM, as Nvidia used legal and technical measures to lock Nouveau out of their firmware).
Now Nouveau has a new shader compiler, Vulcan support is growing rapidly, and people like me will soon prefer the Mesa stack for Nvidia over Nvidia’s own drivers.
And you can bet that Nouveau will work great with all of the Wayland compositors.
This is really the exact wrong point in history to be making the argument you’re trying to make 🤣.
I’ve always just used konsole or gnome terminal. Never really looked into what else is available. Tried cool-retro-term the other day, but the novelty wore off pretty fast for me....
Every “terminal app” is a terminal emulator, because non-emulated terminals are physical pieces of hardware.
So you are already using a terminal emulator, I’d guess Gnome Terminal, and it’s a fairly full featured modern terminal emulator (in my opinion at least).
I was running KDE Neon on ThinkBook 15 G2 and had deep sleep working after adding mem_sleep_default=deep to GRUB_CMDLINE. It worked for a while until it didn’t. I didn’t do anything other than running regulat updates. Since couple weeks back, when going to sleep, it shows BIOS Recovery progress bar or something and restarts....
So far the worst outcome for landlords that you have posed is that they “realize that their investment was a poor one”.
And yes, I want that landlord’s grandchildren to be able to afford college (which I think should be free for all, paid for by tax increases on the rich).
But you have to admit that we’re talking about vastly different worlds here, right?
What percentage of renters live paycheck to paycheck and are at risk of living on the street?
What percentage of landlords are at risk of living on the street?
What percentage of renters expect to be able to leave enough in money and assets to their children, so that those children can afford to pay college tuition for the renter’s grandchildren?
I agree with you that dehumanizing people is wrong. I agree that landlords can struggle too.
I agree that there are worse people / entities that could own apartment complexes and houses.
But you haven’t really convinced me that I should worry about the general well-being of the landlord class, or that it’s worth my time and energy to chide renters who say mean things about them online.
Ok, now what conclusions do you want people to take away from this information?
Possible takeaway: There are worse people / entities that could own the apartments and houses that are being rented out.
If that’s the only takeaway, it’s still not going to make me feel sad for landlords.
If they created an LLC, then whatever happens to their business, they can always just get a different job and their own housing situation will remain stable.
If they didn’t, maybe because they couldn’t get a large enough loan to buy property without putting up their own collateral, that was presumably their choice.
I don’t want anyone to lose access to housing (or food, or healthcare), but I’m much more worried about renters ending up unhoused than landlords.
Trump may or may not eventually end up in prison, but it’s naïve after the past 8 years to assume that there are only two ways this could all shake out, and that you can predict them.
A possibility that will almost certainly be less absurd than whatever actually happens:
Trump wins a second term, manages to get the FedSoc 6 to rule that a sitting president can’t be imprisoned because it would violate separation of powers. So multiple states are just waiting for his term to end so they can actually arrest him. (Feds can’t arrest him because he has pardoned himself for all past, present, and future crimes)
Then in the last month of his presidency he takes a diplomatic trip to Russia and just never comes back.
Sure it is (lemmy.world)
Mosh: Like ssh, but better (e.g. local echo and persistent sessions across sleeps / network changes) (mosh.org)
Thoughts on this? (futurology.today)
Society (lemmy.world)
Rust-Written Linux Scheduler Showing Promising Results For Gaming Performance (nitter.net)
Phoronix
Gitlab now requires phone number/credit card verification (lemmy.world)
Looks like gitlab now requires account verification for new accounts in addition to email. Either phone number or credit card....
Class War > Culture War (lemmy.ml)
In Germany we say "Arbeitnehmerrechte" and I think that's beautiful (swg-empire.de)
Get Bread Get Dead (lemmy.ml)
KDE's Nate Graham On X11 Being A Bad Platform & The Wayland Future (www.phoronix.com)
Well known KDE developer Nate Graham is out with a blog post today outlining his latest Wayland thoughts, how X11 is a bad platform, and the recent topic of “Wayland breaking everything” isn’t really accurate....
Which terminal emulator do you use?
I’ve always just used konsole or gnome terminal. Never really looked into what else is available. Tried cool-retro-term the other day, but the novelty wore off pretty fast for me....
Did deep sleep broke for anyone else recently or is it just me?
I was running KDE Neon on ThinkBook 15 G2 and had deep sleep working after adding mem_sleep_default=deep to GRUB_CMDLINE. It worked for a while until it didn’t. I didn’t do anything other than running regulat updates. Since couple weeks back, when going to sleep, it shows BIOS Recovery progress bar or something and restarts....
oh no a kid somewhere is saying 'rizz' what will I possibly do (i.imgur.com)
I thought this meme was funny though...
No one can stop me (lemmy.ml)
He'll be the death of us all. (lemmy.world)
It’s not like any candidate was actually good but they did pick the worst one.
Dont be fooled by cable news (lemmy.world)