How about a used Thinkpad? Like the X280. 12.5". Touch. Depending on your region you can get a pretty good deal if you are OK with some scratches or other faults
Dell inspiron 15, unfortunately. Going for about $300 the last time I checked, add in another stick of RAM and an SSD, perfect linux machine right there
I’m using docker packages for Doom Emacs. The main one is docker.el. On top of being faster and easier to use than the cli, you can also do some pretty neat stuff like use dired+tramp to browse files and open them in Emacs.
As of next month, I’ve been using Chromebooks for 10 years however I also came to the same conclusion re: Google/ChromeOS over the summer.
Initially, I bought a Windows laptop but the keyboard layout (specifically the function keys) felt absolutely foreign, even after I wiped it and installed Debian. In retrospect, my theory is that a $500 Chromebook has worse internals but a much better keyboard/trackpad than a Windows equivalent, and that the keyboard layout is more user-friendly in a browser-first world. Eventually, I went back to my Chromebook but with a twist.
I’m biased, but since you seem like you know your way around Linux and tinkering, one suggestion that hasn’t been mentioned is that you buy a new Chromebook and turn it into a Chrultrabook (aka a Chromebook w/ ChromeOS completely wiped & replaced w/ Linux).
I’ve been running one of the last few months and it’s been an overall pleasant experience. Perhaps most important for me is that the tutorial includes keyd to reprogram the keyboard shortcuts to mirror the Chromebook layout. The community is growing and responsive, especially on the Linux side.
Thanks for the resources. I think this could be the way forward. I’ll do some research first, as I need something super stable, since I won’t be the final user. So if it breaks, I’m on the hook.
Do you have any suggestions on possible candidate Chromebooks?
I just did some digging on Best Buy and Amazon for sales, but mostly came across larger models or models that were MediaTek/Snapdragon (the chrultrabook team almost exclusively works on intel devices).
I’d say your best bet is to go to the supported devices list, and Ctrl + F for ‘13’ or ‘11’ to highlight the smaller-sized chromebooks and then check to see what’s available, or to jump in the Discord and pose the question to those in the linux channel
Nice. That’s the move. I am finding it more and more difficult to find smaller laptops/chromebooks these days. If I want a big screen, I’ll sit down at my desktop!
Those instructions are from the official docs, and install.sh comes from the source repo. It’s an annoying script (it basically runs apt, npm, make, on your behalf…thanks, I can do that myself), but if you’re trusting the repo source to begin with, I don’t think it’s any less secure.
I use systemd mount files instead of fstab, that way I can specify a network dependency in the off chance there’s no network connection. Plus I can have other services like jellyfin depend on that mount file so it starts after the share is available.
Well, for one, it’s network attached storage. If it’s not present in the network for one reason or another, guess what, your OS doesn’t boot… or it errors during boot, depending on how the kernel was compiled and what switches your bootloader sends to the kernel during boot. Second, this is an easy way for malware to spread, especially if it’s set to run after user logon.
I agree, for most cases just mount it via your File Manager of choice. If you’re using it as a backing storage for another server, then that’s a use case where fstab is fine.
It has to have a mount point somewhere. Just double click the desktop entry, that will mount it wherever you told it to and then you can copy to that location, easy peasy 😉.
In Nautilus, you can right click anywhere and click Open in Console, at which point it will open up a terminal leading to a gvfs mount directory.
In KDE, it is slightly more annoying because there’s no right click option to quickly open it in terminal, but like gvfs, there’s a mount directory that you can access at /run/user//kio-fuse-/smb/.
Wayland is just a protocol. The WMs, compositors and applications need to implement the features the X server used to provide.
Those that don’t will become useless when X is gone.
Right so I guess I should have over specified that I hope ALL the other bits that actually make it function the same will also catch up and for example something as basic as forwarding GUI programs will simply work without jumping through a bunch of tedious flaming hoops with pitfalls on either side. It doesn’t really matter to me that Wayland has decided it’s somebody else problem.
For many uses, Wayland has feature parity now or is even the superior option. That is how it can be the default on so many systems ( including RHEL9 as per the article ).
Compositors that do not provide the features that uses want will fail to compete ( what you mean by become useless I assume ).
That said, different users will want different things and, unlike X, Wayland allows competing compositors to address different communities. Some compositors will lack features some users want while offering features that other users need. A composite targeting embedded use cases may not need multi-monitor or fractional scaling features for example. A security focussed option may think that global hot-keys and external lock-screens are anti-features. I think the Wayland world could be quite interesting.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.