Skip to main content

Linux 字体安装外一篇

之前提到过我在Linux安装字体的方法,就是在~里建个文件夹,然后跑到/usr/share/fonts里建一个链接,最后执行三个命令,其中最后一个是fc-cache

不过今天给同学弄,一开始没弄好,fc-cache似乎不大管用(mkfontdir和mkfontscale都正常工作),然后用 -v 选项发现它根本没有扫描我在/usr/share/fonts里面建的链接。不过仔细阅读发现它会扫描~/.fonts,于是把/usr/share/fonts里新建的链接删掉,然后把~里的字体文件夹改为.fonts,再运行一次fc-cache就ok了.

想反观我的安装过程,却发现首先fc-cache就有问题。manpage是正常的,可是fc-cache不管怎么运行都是直接退出,-v选项不管用。想看版本,-V不管用,然后用fc-cache --help发现可以用--version,但是显示程序名为'true',而且/usr/bin/fc-cache是个指向/bin/true的链接。最后man一看,竟然是'true - do nothing, successfully'. 一开始认为是package没装好,用aptitude重装不管用。而且fontconfig这个package的其他命令如fc-list可以使用。最后没办法了,直接打fc-然后tab匹配,发现个fc-cache.distrib,一运行,竟然是fc-cache,估计这个是重名问题,只是不知道true是干什么用的。

这样说来当时我运行的fc-cache很可能就是这个true -- 什么都不工作,竟然还能装上字体,很神奇。

我在我的机器上运行fc-cache.distrib -v发现它确实会扫描我在/usr/share/fonts/里建的链接(也会扫描~/.fonts)。但同学的不会。后来看一下版本,我的是2.3.2,他的是2.4.2,估计跟版本有关。不过他的fc-cache没有manpage,所以具体原因就不得而知了。

总之,装好了也就行了。

Comments

Popular posts from this blog

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...

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 ...

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...