Skip to main content

杂记 20130401

  • 之前evince的快捷键乱套了，使用
    rm ~/.config/evince/accels
    复位
  • 定义了变量var又不用的话，gcc会报warning"unused variable"，解法是
    (void)var;
  • VirtualBox中DNS不工作：运行
    VBoxManage modifyvm "VM name" --natdnshostresolver1 on
    Ref 
  • 一个讲c++11右值引用的link：http://thbecker.net/articles/rvalue_references/section_01.html 
  • Linux清除disk cache: 
    sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'
    Ref
  •  遇到错误screen-256color not found需要支持新的终端类型：找一台支持screen-256color的机器执行
    infocmp xterm-256color > screen-256color.ti
    把文件拷贝到目标机器后执行
    tic screen-256color.ti
    Ref
  •  最近从ibus换到了fcitx，起初是由于sogou发布了，不过后来还是卸掉了。anran主题不错。fcitx在firefox中光标跟随有点问题，按官方wiki说法打开preedit后就没事了。
  •  最近在vim里折腾youcompleteme这个补全插件，挺好用。顺便也装了vundle来管理插件，很不错
  •  vim更新.vimrc后想直接应用，执行
    so %
Labels:

Comments

Post a Comment

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Post a Comment
Read More »

mkosi: First Impressions

I stumbled upon the Gentoo wiki page for systemd-nspawn , which in turn led me to nspawn.org , mkosi , and later systemd-sysupdate . mkosi quickly caught my eye because it's almost exactly what I wanted to build myself, as mentioned in a previous post . So, I decided to spend my "sysadmin fun quota" on it. Overview mkosi is similar to docker build or podman build , but it's designed for creating full OS images. It focuses on development and testing. For example, much like nix-shell , mkosi can quickly launch a sandboxed shell with a specific distribution and selected packages installed. The systemd project itself uses mkosi for testing across different distros. The re-introduction article  is a great read. Speed Note that this is by no means a rigid benchmark. My setup is an SSD with LUKS and an ext4 filesystem (without reflink support). Building Container Images mkosi is pretty fast. A simple mkosi command creates a fresh Debian image. I used the --incrementa...
Post a Comment
Read More »