• 0 Posts
  • 24 Comments
Joined 8 months ago
cake
Cake day: November 7th, 2023

help-circle





  • Tuxedo also offers products with an aluminum body, and while they do import the hardware from China, you get the local service and warranty guarantees any company in the EU must provide, so that’s fine by me.

    Also, honest question: what do you think a unique laptop is, in particular when buying from a mass consumer brand like Lenovo? I really can’t figure out what that’s supposed to mean.


  • Oh, that makes everything a lot easier. The majority of the relevant settings will be in your home folder then, i. e. in the ${HOME}./.config folder, while some might also be in ${HOME}/.local/share etc.

    You probably want to backup the whole home folder anyway, so that would pickup most of your settings. In order to make that work on a different system, you would have to install all applications you were using on the tablet as well. Luckily, software installation in Linux is pretty easy, so you can export a list of installed applications from the Surface and then re-install them on your target system before migrating your home folder. The software list should become part of your backup. See e. g. https://unix.stackexchange.com/questions/82880/how-to-replicate-installed-package-selection-from-one-fedora-instance-to-another for an idea of how to perform this.

    I have used this approach in the past and it will get you 95% there. There might be some global system settings that you’d like to also transfer to your new system, but you can add those as you discover you miss them on the target system.


  • In general, no, this won’t work. In your case, you’re lucky since at least the Surface Go is using an x86 CPU, so it’s not completely out of the question, but transferring the image as-is to a completely different device typically does not work without modification.

    Simple example: your target device might not refer to existing hardware (let’s say a storage medium) in the same manner as your old device, so the existing references in your cloned image won’t work. There are other issues of course, e. g. missing drivers for different hardware present on the target device.

    It’s possible to modify the image so it would boot, but given the Surface runs Windows, that’s going to be a chore. I’d consider this an interesting project if bored on a slow weekend, but I’d most likely just do a filesystem backup of relevant data and call it a day.


  • Honestly, that just seems like you’re treating dd as some kind of arcanum. dd works just fine and I’ve been doing 1:1, full system backups for decades with it, no issues. Honorary mention for ddrescue / dd_rescue for recovery options, i. e. re-trying bad sector reads etc.

    In fact, when Clonezilla doesn’t know your filesystem, it will simply employ dd to copy the data sector by sector.

    I’d argue that Clonezilla (due to its use of partclone) is actually a less complete form of backup, since it will only copy used blocks, you don’t really end up with a clone of your devices, just a copy of what partclone believes to be your data. Don’t get me wrong, that is fine in most use cases, but there are some cases where this doesn’t cut it, e. g. wanting to backup / restore a storage device from a PLC where the vendor had the glorious idea to store licensing data in unused sectors, or when you want to create a forensic disk image, might want it look into d3dd then, although it absolutely works using regular old dd as well, d3dd just adds some amenities.

    All I want to say is: dd is an absolutely reliable tool and can be a one stop solution for device backups. Also, I have absolutely no quarrels with Clonezilla, if it fits what you’re trying to do and it works, great.


  • scrion@lemmy.worldtoMemes@lemmy.mlWhen I was young
    link
    fedilink
    arrow-up
    16
    ·
    24 days ago

    Yikes. If the second sentence of your ad reads So instead of blaming him […] she should question herself, we’re in for a good time. And that’s not even touching the idea that his many neglects can be explained away by what exactly, pussy odor?

    Not a doctor here, but I’m being told applying a disinfectant might not be the best idea, although the medical details are by far not the bleakest thing about this ad.

    To be fair, before it was promoted like this, it was actually used in Germany to combat Cholera. This dystopian marketing we see here is a US invention.

    Fun fact: early Lysol was really poisonous and was used as the suicide poison in the beginning of the 20th century, readily available and all. It was also used for homemade abortions.


  • The best way would in fact be testing it with an electronic load that applies a precise and well known load to the battery and integrates capacity until a matching shutoff condition is reached.

    However, the majority of people do not happen to have access to such an instrument, so I’d say your suggestion is a close approximation of the best way, which could be augmented by adding simple measurements, which can be done by most people at home for a reasonable, quantifiable judgment.



  • I am aware of what you are saying, however, I do not agree with your conclusions. Just for the sake of providing context for our discussion, I wrote plenty of code in statically typed languages, starting in a professional capacity some 33 years ago when switching from pure TASM to AT&T C++ 2, so there is no need to convince me of the benefits :)

    That being said, I think we’re talking about different use cases here. When I’m talking configuration, I’m talking runtime settings provided by a customer, or service tech in the field - that hardly maps to a compiler error as you mentioned. It’s also better (more flexible / higher abstraction) than simply checking a JSON schema, and I’m personally encountering multiple new, custom JSON documents every week where it has proven to be a real timesaver.

    I also do not believe that all data validation can be boiled down to simple type checking - libraries like pydantic handle complex validation cases with interdependencies between attributes, initialization order, and fields that need to be checked by a finite automaton, regex or even custom code. Sure, you can graft that on after the fact, but what the library does is provide a standardized way of handling these cases with (IMHO) minimal clutter. I know you basically made that point, but the example you gave is oversimplified - at least in what I do, I rarely encounter data that can be properly validated by simple type checking. If business logic and domain knowledge has to be part of the validation, I can save a ton of boilerplate code by writing my validations using pydantic.

    Type annotations are a completely orthogonal case and I’ll be the first to admit that Python’s type situation is not ideal.




  • Your USB ethernet adapter is down according to this output.

    In case Ubuntu server comes with e. g. dhclient installed, you should be able to get a working network connection by ensuring a cable is properly plugged into your USB ethernet adapter and running

    sudo dhclient -v enx949aa9857457

    You might want to post the output of that command here. Alternatively, configure the USB adapter using one of the management tools mentioned in this thread already.




  • Nice, I did not know such a connector existed - that will be useful for completely different and unrelated use cases.

    While I had toyed with the idea of a portable, Japanese - made DAC for a while, I switched to Bluetooth headphones years ago. Started out with a cheap Philips headset for $50, later on got the Bose QC 35 II (still my daily driver when outside) and finally worked my way up to the Sony WH-1000XM5.

    I did not realize how nice active noise cancelation is. Plus, the frequency reproduction of the XM5 with LDAC enabled is absolutely fine.

    On the cons side, you’re walking around with $300 - $400 on your head, which is an absolutely luxury, plus you’ll get headphones that perform equally well in the sound department (minus the excellent ANC and freedom from cables) for a lot less.