KDE Plasma + Brave on Debian

  This is the “how do I make Brave do what I want” note --- especially when Brave profile UI is broken and KDE is strict about .desktop launchers. 1) Know what you’re running. Check where Brave comes from. which brave-browser If it returns /usr/bin/brave-browser , you’re on the APT-installed build (good, predictable). Also note that on Debian you often have both commands available. brave-browser is commonly a wrapper. brave-browser-stable is commonly the actual binary. 2) Where Brave stores its data. Default Brave user-data root (APT install). ~/.config/BraveSoftware/Brave-Browser/ If you only see Default/ , then you effectively have a single Brave “profile” in that directory. 3) Multiple isolated Brave sessions without Brave profiles. This is the clean workaround: run separate user-data directories . Create a new isolated environment. mkdir -p ~/.config/BraveSoftware/Brave-RDT Launch Brave using that directory. brave-browser-stable --user-data-dir= ...
0

Backing Up and compressing

BACKING UP

$ rsync source-file target:destination-path
where target can be in the form of someone@host. The someone@ part is optional and used if the remote user is different from the local user.

rsync copies the content of the file into another file.

  • Automatically checks if the destination file exists
  • If there is no change in size and modification time, it avoids the copy
  • It copy only the modified part of the file, not the whole file 
  • It can copy to a remote destination
Example:
$ rsync -r project-X archive-machine:archives/project-X

dd
Makes a raw copy of an hard disk to another.
Very dangerous if used inappropriately.


COMPRESSING

Efficiency compression max to min and speed compression min to max:

  1. xzip
  2. bzip2 (deprecated, no longer maintained)
  3. gzip
  4. tar (most an archiver than a compressor)

Comments

Post a Comment