Off-and-on trying out an account over at @tal@oleo.cafe due to scraping bots bogging down lemmy.today to the point of near-unusability.

  • 1 Post
  • 135 Comments
Joined 2 years ago
cake
Cake day: October 4th, 2023

help-circle
  • From my /etc/resolv.conf on Debian trixie, which isn’t using openresolv:

    # Third party programs should typically not access this file directly, but only
    # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
    # different way, replace this symlink by a static file or a different symlink.
    

    I mean, if you want to just write a static resolv.conf, I don’t think that you normally need to have it flagged immutable. You just put the text file you want in place of the symlink.


  • Also, when you talk about fsck, what could be good options for this to check the drive?

    I’ve never used proxmox, so I can’t advise how to do so via the UI it provides. As a general Linux approach, though, if you’re copying from a source Linux filesystem, it should be possible to unmount it — or boot from a live boot Linux CD, if that filesystem is required to run the system — and then just run fsck /dev/sda1 or whatever the filesystem device is.


  • I’d suspect that too. Try just reading from the source drive or just writing to the destination drive and see which causes the problems. Could also be a corrupt filesystem; probably not a bad idea to try to fsck it.

    IME, on a failing disk, you can get I/O blocking as the system retries, but it usually won’t freeze the system unless your swap partition/file is on that drive. Then, as soon as the kernel goes to pull something from swap on the failing drive, everything blocks. If you have a way to view the kernel log (e.g. you’re looking at a Linux console or have serial access or something else that keeps working), you’ll probably see kernel log messages. Might try swapoff -a before doing the rsync to disable swap.

    At first I was under suspicion was temperature.

    I’ve never had it happen, but it is possible for heat to cause issues for hard drives; I’m assuming that OP is checking CPU temperature. If you’ve ever copied the contents of a full disk, the case will tend to get pretty toasty. I don’t know if the firmware will slow down operation to keep temperature sane — all the rotational drives I’ve used in the past have had temperature sensors, so I’d think that it would. Could try aiming a fan at the things. I doubt that that’s it, though.














  • tal@lemmy.todaytoProgramming@programming.devUsing Vim is Amazing
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    27 days ago

    when I started using vim mode in zsh.

    I’m an emacs user myself, but if you’re not aware, readline — which handles a considerable portion of the “prompt for text” stuff in many terminal programs, like input for bash and such — can be put into vi mode.

    https://tiswww.case.edu/php/chet/readline/rluserman.html#Readline-vi-Mode

    In order to switch interactively between emacs and vi editing modes, use the command M-C-j (bound to emacs-editing-mode when in vi mode and to vi-editing-mode in emacs mode). The Readline default is emacs mode.

    When you enter a line in vi mode, you are already placed in ‘insertion’ mode, as if you had typed an ‘i’. Pressing ESC switches you into ‘command’ mode, where you can edit the text of the line with the standard vi movement keys, move to previous history lines with ‘k’ and subsequent lines with ‘j’, and so forth.

    Or, in ~/.inputrc:

    set editing-mode vi
    

    To set the default.


  • I use emacs’s magit for git stuff (the bulk of things) and emacs’s ediff for most other things.

    Good if you know emacs, but hard to recommend using it for someone who doesn’t.

    EDIT: Oh, one exotic utility that’s useful for some rare cases, not really for interactive merging of code — wdiff for word-level diffing. Most code can reasonably be diffed on a line-by-line basis, but that’s not true for some text formats, which can have very long lines. Human, natural language in text format, is one good example.





  • https://en.wikipedia.org/wiki/Analog_hole

    The analog hole (also known as the analog loophole or analog gap) is a perceived fundamental and inevitable vulnerability in copy protection schemes for noninteractive works in digital formats which can be exploited to duplicate copy-protected works using analog means. Once digital information is converted to a human-perceptible (analog) form, it is a relatively simple matter to digitally recapture that analog reproduction in an unrestricted form, thereby fundamentally circumventing any and all restrictions placed on copyrighted digitally distributed work. Media publishers who use digital rights management (DRM), to restrict how a work can be used, perceive the necessity to make it visible or audible as a “hole” in the control that DRM otherwise affords them.[1]

    EDIT: I don’t know if I’d say that it’s fundamental, as Wikipedia did — I can think of a couple of approaches to try and address it — but it is quite substantial.