Laser

@Laser@feddit.de

This profile is from a federated server and may be incomplete. Browse more on the original instance.

Laser,

I’m Windows-free for about 18 years.

It’s basically the same time I started using Linux somewhat more. I didn’t go Windows-free until 2007 though and then returned to Windows because I needed it for something with my Master’s thesis. I kind of shudder at the thought how my old setups looked under the hood. You learn a lot in 18 years… Probably copy-pasted a lot of shell commands back then. But UT2k4 in its OpenGL glory was worth it

Laser,

Nobody mentioned Olive yet, that one is very good, though I’m always concerned about the continuation of its development.

Laser,

Really looking forward to this release! Good stuff, another (minor) possible improvement for wine would be native pipewire support. But this is definitely more interesting

Laser,

Unfortunately this only affects boot messages, not normal system operation, for that you still get core dumps and kernel panics / oops

Laser,

Simplified, there’s two layers to data protection, physical and logical. Linux or basically any correctly configured modern operating system provides logical protection, i.e. access under the running OS is only granted to authorized users. Granted you can still put holes in here, e.g. a webserver is misconfigured and allows access to any user to all files it can read. However, from the OS perspective, everything is fine, as the webserver can still only read what it’s allowed to.

Data encryption protects data at rest, i.e. when no operating system enforcing the logical protection is running. The case has already been described so I’m not gonna repeat that here.

It’s important to understand that in general, these two measures are completely seperate from each other. Device encryption won’t help against logical attacks, and logical protection won’t help against offline attacks. You need both if you can’t rule out an attack vector completely (i.e. your server sits in a secure safe that can’t be opened by anyone not authorized to, then encryption might not be necessary).

Laser,

I’m a bit confused about what you actually want? Do you just want to update your packages, but stay on the same NixOS version? Just continue like before. Do you want to stay on your current version, but use some packages from the next version? That should also be possible if you somehow include that channel in your configuration.nix (though I don’t know how this would work in practice).

Personally, I just run with unstable though, then the releases aren’t that important.

Laser,

I think unstable and the fixed versions use the same Firefox package, so you wouldn’t gain anything. The difference is rather in libraries that get used and how the distribution does things. For example, the changes listed in nixos.org/manual/nixos/stable/release-notes#sec-r… just appeared mostly one by one for me; one day, I wanted to update my system and got the error that the fonts option got renamed, so I had to change my configuration.

The fonts.fonts and fonts.enableDefaultFonts options have been renamed to fonts.packages and fonts.enableDefaultPackages respectively.

While when using a fixed point release, these changes won’t happen. Only when you switch releases. That’s what “unstable” refers to.

Laser,

When not using flakes, nixos-rebuild switch --upgrade is equivalent to apt update; apt upgrade. The equivalent to dist-upgrade is nix-channel add $NEW-CHANNEL-URL nixos and then performing a regular update.

Laser,

I assume you’re talking about X over SSH? That’s possible with Wayland via Waypipe. Also I’m not sure why RDP would require X, just a compositor being able to forward the video over network (which is perfectly possible with Wayland) and accepting inputs over network as well, which to my knowledge isn’t part of Wayland. Quick check says Gnome already offers RDP and that’s Red Hat’s DE.

Laser,

Most interesting development. This is obviously still into the future but I also always had the impression that Redhat did a lot of work on the XOrg server. With this I think it’s actually dead once they no longer support RHEL 9 and older.

I won’t miss it, granted it’s not a bad implementation, but the design is showing its age. Apart from Wayland that I use, I’m also looking at Arcan’s progress from time to time. Obviously rather niche at the moment but projects like these make the ecosystem interesting.

Laser,

Thanks, I corrected it

Laser, (edited )

As pointed out, they don’t use it. However, there are loose plan for KWin to migrate to wlroots one day, and in fact a hostile fork exists that is exactly that (KWinFT). So a compositor can make use of wlroots to implement Wayland functionality, sway for example does exactly that, unsurprisingly since they’re sister projects by the same author.

It should be noted that libwayland (mentioned in the patch notes) also exist, and wlroot actually depends on it, so I guess libwayland is like the lower level stuff while wlroots saves you some work to integrate libwayland into your compositor; the motto is “Pluggable, composable, unopinionated modules for building a Wayland compositor; or about 60,000 lines of code you were going to write anyway.”

Laser,

Why would they ditch NetworkManager though? What’s everyone’s issue with it?

Laser,

I mean traditionally NetworkManager uses wpa_supplicant anyways though there is the option for iwd. So it will stay available for quite some time.

Laser,

What’s broken? I just added a vpnc connection on my machine (granted can’t test it since I have nothing to connect to) but there was a vpnc connection profile until I deleted it.

Laser,

From my point of view, nothing else but NetworkManager makes sense to ship by default for a distribution aimed at desktop use. So I fully understand distributions doing this. My point was rather that this is not related to any particular WM / DE.

Laser,

Neither GNOME nor Plasma depend on NetworkManager, do they? Plasma will happily show information about connections managed by something else than NetworkManager, but won’t be able to manage them itself. But desktop distributions will most likely ship it as it covers basically all use cases.

Laser,

She’s a rookie, left row cigarette number 5 isn’t lit. Are you even smoking at this point or just pretending? Take a lesson from this fella 1.bp.blogspot.com/…/StefanSigmondWorldRecord.jpg

Laser,

I always want to try Plan 9 or one of its successors but actually never do. So many interesting concepts but nothing really to apply them to.

Laser,

It’s a good question what I really want. I’m very satisfied with my current system (NixOS) but in the end it’s still Linux and stuff like the 9P filesystem just intrigues me. So it’s not like I’d need to switch or anything. But a playground to apply the concepts to some problems would be nice. Maybe I’ll try 9front some day and see what I can do with it

Are movie and show file sizes more efficient than they were years ago?

This may be a stupid question, but I just got back into pirating some shows and movies and realize that many of the QxR files are much smaller than what I downloaded in the past. Is it likely that I am sacrificing a noticeable amount of quality if I replace my files with the smaller QxR ones?...

Laser,

Nothing, the licenses are for content providers and equipment manufacturers, obviously in the end you pay the license when purchasing the goods but the amount is small.

Laser,

I think your workflow is not optimal. Are you using software like Radarr and Sonarr? They do the renaming for you and come with Kodi integration. Or is this not feasible?

Laser,

I’m daily driving Firefox with Wayland on KDE Plasma since years, not on Xwayland, and can’t remember it not working well. This on two different distributions (Arch and NixOS). Not saying this is your fault but your experience is not representative for everyone

Laser,

That can be easily done with AOSP, to my knowledge there’s no Google stuff in there. Which is exactly what they’re using right now

Laser,

yEnc isn’t a cipher, but rather an encoding for mapping binary to text, similar to base64 (but much more effective). So this denotes yEncc encoding.

The files you’re seeing are PAR2 files, which are used for repairing. They’re useless without the base file. The file in your example contains 32 recovery blocks. That means if your base file has 32 or less damaged blocks, this parity file can repair it.

Usually, you’d download all files belonging together in a single download and let your downloader do the rest. This is normally done by loading an NZB file that you either get from a Usenet search engine or an indexer.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #