cultural reviewer and dabbler in stylistic premonitions

  • 2 Posts
  • 24 Comments
Joined 4 years ago
Cake day: January 17th, 2022
  • Arthur Besse@lemmy.mltolinuxmemes@lemmy.world•Command line tip of the dayEnglish
    2·
    12 days ago

    I can’t really imagine a benefit to --autoremove except for keeping old packages a bit longer before removing them.

    Eg, if you run apt --update --autoremove upgrade -y once a day you’ll keep your prior-to-currently-running-version kernel packages a day longer than if you ran autoremove immediately after each upgrade.

    To make things more confusing: the new-ish apt full-upgrade command seems to remove most of what apt autoremove wants to… but not quite everything. 🤷

  • Arthur Besse@lemmy.mltolinuxmemes@lemmy.world•Highlight of my MorningEnglish
    121·
    3 months ago

    sudo apt --update --autoremove upgrade -y

    note

    this doesn’t actually do the same thing as the previous comment running autoremove afterwards does; the former will remove things which were rendered removable by the upgrade while the latter will only remove things which were already autoremovable prior the upgrade.

  • Arthur Besse@lemmy.mltolinuxmemes@lemmy.world•I never had problems with permission again after I know the real power of sudoEnglish
    33·
    8 months ago

    Why memorize a different command? I assume sudoedit just looks up the system’s EDITOR environment variable and uses that. Is there any other benefit?

    I don’t use it, but, sudoedit is a little more complicated than that.

    details

    from man sudo:

    When invoked as sudoedit, the -e option (described below), is implied.

           -e, --edit
               Edit one or more files instead of running a command.   In  lieu
               of  a  path name, the string "sudoedit" is used when consulting
               the security policy.  If the user is authorized by the  policy,
               the following steps are taken:

               1.   Temporary  copies  are made of the files to be edited with
                    the owner set to the invoking user.

               2.   The editor specified by the policy is run to edit the tem‐
                    porary files.  The sudoers policy  uses  the  SUDO_EDITOR,
                    VISUAL  and  EDITOR environment variables (in that order).
                    If none of SUDO_EDITOR, VISUAL  or  EDITOR  are  set,  the
                    first  program  listed  in the editor sudoers(5) option is
                    used.

               3.   If they have been modified, the temporary files are copied
                    back to their original location and the temporary versions
                    are removed.

               To help prevent the editing of unauthorized files, the  follow‐
               ing  restrictions are enforced unless explicitly allowed by the
               security policy:

                •  Symbolic links  may  not  be  edited  (version  1.8.15  and
                   higher).

                •  Symbolic links along the path to be edited are not followed
                   when  the parent directory is writable by the invoking user
                   unless that user is root (version 1.8.16 and higher).

                •  Files located in a directory that is writable by the invok‐
                   ing user may not be edited unless that user is  root  (ver‐
                   sion 1.8.16 and higher).

               Users are never allowed to edit device special files.

               If  the specified file does not exist, it will be created.  Un‐
               like most commands run by sudo, the editor is run with the  in‐
               voking  user's  environment  unmodified.  If the temporary file
               becomes empty after editing, the user will be  prompted  before
               it is installed.  If, for some reason, sudo is unable to update
               a file with its edited version, the user will receive a warning
               and the edited copy will remain in a temporary file.

    tldr: it makes a copy of the file-to-be-edited in a temp directory, owned by you, and then runs your $EDITOR as your normal user (so, with your normal editor config)

    note that sudo also includes a similar command which is specifically for editing /etc/sudoers, called visudo 🤪

  • Arthur Besse@lemmy.mltolinuxmemes@lemmy.world•the perfect browserEnglish
    14·
    9 months ago

    The three currently-maintained engines which (at their feature intersection) effectively define what “the web” is today are Mozilla’s Gecko, Apple’s WebKit, and Google’s Blink.

    The latter two are both descended from KHTML, which came from the Konquerer browser which was first released as part of KDE 2.0 in 2000, and thus both are LGPL licensed.

    After having their own proprietary engine for over two decades, Microsoft stopped developing it and switched to Google’s fork of Apple’s fork of KDE’s free software web engine.

    Probably Windows will replace its kernel with Linux eventually too, for better or worse :)

    How else are Chrome, Edge, Brave, Arc, Vivaldi and co getting away with building proprietary layers on top of a copyleft dependency?

    They’re allowed to because the LGPL (unlike the normal GPL) is a weak copyleft license.